json document loader can handle more complex json

Hi @MaximeThoonsen thanks for this, would it be possible to do this all inside the existing JSONLoader, by changing that one to accept either one JSONPointer or an array of multiple JSONPointer?

Hey @nfcampos.
Sure I can add the handling of arrays of JSONpointer.
On top of that, in this version of the code, the JSONpointer loader is for use case where you want exact match of the path of the data you want to retrieve. And the JSON loader can handle more unstructured JSON file to retrieve strings from matching keys in any level of the JSON object. I did it to be able to handle Corrado's use case on discord.
I see 3 options if I move everything in the JSON loader:

I remove the logic I implemented around what I call "keys".
I can make the JSON pointer follows quite the same behaviour (ie not looking for exact match from the root node)
I add an argument to the constructor of the JSONLoader class to handle both cases (strict and not strict)

I see value of both usage but I understand there is a tradeoff with simplicity of documentation.
Tell me what you prefer.

Hey @nfcampos,
I chose to do 2). It should be ok for most use of json use case including the one from Corrado.
(I am AFK until Sunday evening)


Keep go.opentelemetry.io/otel versions in sync with BuildKit

https://github.com/moby/buildkit/blob/v0.10.3/go.mod#L62-L68
Otherwise we can introduce data races and other weird behaviour:

(jaeger v1.6.0) data races https://github.com/dagger/dagger/runs/7359366602?check_suite_focus=true#step:8:1433
(jaeger v1.8.0) conflicting Schema URLs https://github.com/dagger/dagger/runs/7358945187?check_suite_focus=true#step:8:2066

Also mentioned in https://github.com/dagger/dagger/pull/2446#issuecomment-1126377411

Noticed that react-scripts keeps failing randomly, pretty sure that we have a flaky test on our hands.

Leaving this with you @aluzzardi, after we shared context synchronously.

In an ideal world this should never be a problem (otel is meant for tracing across micro services, version mismatch is OK) but I'd rather we don't spend too much time on this.
Let's go ahead with this as is, we can revisit someday
/cc @sipsma

Needs a LGTM before it can be merged. Any 👍 will do: @helderco @sipsma @aluzzardi


Initial Implementation for display_segment update_method replace

config_spec.yaml:
changed default from not_set to off, left not_set in enum though I believe it can be removed. I couldn't see why not_set is a good default. If really needed for the changes in update_method replace I can add code to exchange not_set for off.
segment_display:
Only changed code for update_method replace, stack should behave like before. I tested with various segment displays shows and it seems to behave well. Note:

for replace the priority parameter is not used (and doesn't make sense if you don't have a stack)
my shows work with replace, but completely misbehave if using stack
I would propose (but have not done it since unsure about consequences for others) to change the default to replace in here https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L139
I am not able to test color changes since my display is single color (though would believe it should work if it works for stack)
flashing, transition, transition_out, expire parameter tested (and working)

If the PR gets accepted I would do some additons to mpf-docs 0.80. Just would need to know how to contribute version specific changes.

In regards to the last commit fixed and clean up of color handling in segment displays
In general there are some issues when defining segment display shows due to the fact how colors are being handled and how that is being known to user and if that is perceived as a logical definition flow.
In segment display the default color (white) is used
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L90
to expand the given color array to the right until the length of the segment display is being filled up. So for a 4 digit display, specified as default color "blue, yellow" this would end up as "blue, yellow, white, white".
During initlize an empty string is sent to the segment display
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L101
, each string is colored
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display_text.py#L94
Since the length is 0, the left_pad_color is used to set the color. So it is not the default color being used, the color set now for this example is "blue, blue, blue, blue". Which on the first view doesn't matter since the display is blank, but at later points in time the code prefers to use the current_state color and not the default_color if no color is being sent, for example
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L303
if the other digits cannot display blue they will simply stay blank.
In other parts of the code, if you start a transition the given colors are being expanded
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L186, where expanded could as well mean shortend to the length of the text and not the length of the display, so later the empty places are being padded with a
color again (see above). If the colors need to be expanded then this
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/segment_display.py#L230
is done by taking the most right color and reuse it for all the other text to the right of this position (so no default color being used).
If a transition text is being used and no color is specified, then the color of the first character of the new text is being used (again not the default color).
https://github.com/missionpinball/mpf/blob/35a84ba29c54acc6ce1afab28bb0e9edca07e301/mpf/devices/segment_display/transitions.py#L139
In general we have default color, sometimes padded to the left and sometimes padded to the right. Question is if the user can follow that behavior or if it is over complicated and thus introduces user mistakes.
The PR will change some of the behavior to make it more consistent

unchanged is that rather the current_state is used and not the default_color
changed is that if color information is missing that the as the default color white will be used, padded to the left, that ensure that at least something is

visible and not that because of a wrong color invisible text is shown and confuses the user. But the PR not only makes the handling more consistent but I would consider it a bug if a color is used for padding which might be able to be used for the digits of that segment display.
Once the PR is accepted I will update the documentation to explain the color handling in detail for the users.


Prevent global and local config paths to clash

Fix #32.
Currently, calling netlify commands from within the home directory will crash because netlify first saves the global config at ~/.netlify/config (so ~/.netlify/ is a directory) and then try to save the local config at ~/.netlify (as a file).
With this PR, if the CLI detects that the command is ran from the home directory, it will save the local config as .netlify.local instead of .netlify to prevent the names from clashing. In any other cases, it keeps the existing .netlify to allow backward compatibility.
Another approach would be to allow the local config file name to be overwritten via environment variable (e.g. LOCAL_CONFIG_FILENAME), the same way it is already possible some other options. Note that it would mean that the user has to first encounter the error, learn about such setting and then use it. On the other hand, with the change from this PR, the CLI will work automatically.

@biilmann @calavera: Is there anything I should do to get this merged? Maybe you'd prefer another approach?

Hi - sorry to inform you (and that we didn't earlier) but this project is no longer supported (noted in the readme).
Please use: https://github.com/netlify/netlifyctl

Oh, I can see now that the deprecation warning got merged on the same day I created the PR so I missed it. Anyway, thanks for the answer @rybit.


Ileum CD Fibroblasts vs CD Control Fibroblasts

Hello,
I came across this excellent website. I see that there are comparisons between colonic fibroblasts in CD and in control samples. I did not see the same option for ileum-derived fibroblasts in CD. Is that data available and if not can it possible be added? Thank you!
Best,
-JJ

Hi JJ,
this analysis has been completed and the data available is intended to remain as it is. If the group will perform a new analysis (with new data), will be published in a new platform.
Thanks for writing,
Luigi


Update for form-urlencoded v5

Related: #139
The specific issue there is fixed, but by making the current affjax error at compile time with the new form-urlencoded.

From what I gather, there's a bit of a design challenge here in that the request signature doesn't currently have a way to surface an error that might occur when constructing a request. Are there any ideas about what such an API should look like?

I think it's ok - the problem would occur before request, since it's when constructing the value for content that this failure would occur - the appropriate constructor for RequestBody expects a FormURLEncoded typed value, it doesn't take a string and encode that or anything.
I'll try doing the update now, I meant to do it ages ago but have had various things going on. Will find out quickly enough if it is a problem or not!

Ok, I'm not very good at reading comprehension obviously, since there's a line right there that says FormURLEncoded.encode 😄. I'll figure something out though, only just started looking.

I think I'm going to change the design a bit in a way that will help with a footgun affjax has right now: when an error occurs making the XHR request, it explodes using the Aff error channel (like in #128). So I'm going to make a Result ADT for request than can encompass a couple of different possibilities:

Request content error (for this new case)
XHR error (for catching throws when making the XHR request - bad URLs, things like that)
Response format error (this is captured as a Response (Either ...) right now - it will still have the response attached, but with a Foreign body since decoding it failed)
Success

It means there'll be a bit more ceremony to handling results, but at least it will cover all the possible failure states now, and won't have to fall back on silently disappearing request content that is bad or something.

Thanks for looking into this @garyb. I'm sorry that the changes I made to form-urlencoded created more work for you, but I do think that the new interface you have described is a definite improvement considering the things that can go wrong.

Resolved by #145 🙂

Awesome, thanks @garyb!


Spiral Conveyors

For example:

@MatthewReed303 has added a spiral conveyor model, but it needs scripting.

Hey ! I will maybe give it a try , this project interests me and i'd like to contribute


Please update KB Article with latest Agent Information.

Hello,
As usual, the KB is not updated even though there is a new AVD Agent version released (1.0.6129.9100).
As per typical development, these KBs should be updated AT the release time, or just prior to help us understand what changes have been implemented. In the past, we have had issues in regard to the AVD Agent - and knowing what's been released to our production environment would be extremely helpful.
KB In question: https://learn.microsoft.com/en-us/azure/virtual-desktop/whats-new-agent
Kind Regards.

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

ID: 3cb10266-d3ca-31b1-31a0-bd4952e6736b
Version Independent ID: 9adcd5ff-db9f-44f9-27f6-7c689839267b
Content: What's new in the Azure Virtual Desktop Agent? - Azure
Content Source: articles/virtual-desktop/whats-new-agent.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

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

@adcadminaccount
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

@Heidilohr
Can you please check and add your comments on this doc update request as applicable.


PowerToys Run needs a redesign!!

Description of the new feature / enhancement
It would be cool to have a redesign to PowerToys Run
Mica effect and more modern design will make it very cool
Also, the scrolling is so bad and does not have animations at all which is inconvenient.
Scenario when this would be used?
.
Supporting information
No response

Thanks for your message. This is a Duplicate of an other issue. Additional comments may be added there. /dup #23591


How to use with webjars ?

Hello,
I am trying to test this plugin with angular2 webjar dependency but the typescript compiler never found lib files.
Perhaps there is missing some paths like they have in sbt-less plugin :
"paths" -> JsArray(         (sourceDirectories.value             ++ resourceDirectories.value             ++ webModuleDirectories.value             ++ nodeModuleDirectories.value)           .map(f => JsString(f.getAbsolutePath)).toVector       )
any ideas ?

wassertim told me, that this is a known issue.
Would be a very useful feature though

Guys, this is now in master you can checkout and give it a try


posts not sorting correctly on listposts view

Mission posts don't maintain the correct sorting on sim/listposts/mission/1
Posts listed under listposts view should be sorted according to the order method selected in the control panel.
Unless order option is default the timeline should also display the correct Mission Day or Date Time values.

fixed in v1.1.1


Engineering Checklist for Onboarding Claire - Assignee please modify as appropriate for Dashboard team

New Engineer Onboarding Checklist
Special Notes

[ ] Paste a link to the general onboarding ticket, which includes the onboarding authorization, here:

Complete additional cloud.gov trainings

    Federal employees and staff contractors, expand this section. Not applicable to project contractors.

Engineers who are federal employees or staff contractors have a Contingency Plan role and may participate in Incident Response, so they must complete the CP and IR trainings. Project contractors do not need to complete these trainings. Check one of the following:

[ ] Coordinate with your onboarding buddy to schedule Contingency Planning training within 60 days. (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Contingency Plan.

[ ] Coordinate with your onboarding buddy to schedule Incident Response Training within 60 days of joining the team (and annually after that). This will cover the following document, which you should also review before or after training:

[ ] Read the Incident Response Guide.

Slack channels
Project contractors: Your buddy will add you to the private channel for your project.

    Federal employees and staff contractors, expand this section:

Your onboarding buddy will add you to these Slack channels:

[ ] #cg-aws-security - private channel where bots post security notices
[ ] #cg-billing - private business development channel (if applicable)
[ ] #cg-incidents - private channel for incident response
[ ] #cg-ops-banter - private channel for operations/engineering banter
[ ] #cg-priv-compliance - private channel for security and compliance discussions

Google Groups

    Federal employees and staff contractors, expand this section:

[ ] cloud.gov AWS
[ ] cloud.gov Notifications (🗣)
[ ] cloud.gov Operations
[ ] cloud.gov Security
[ ] cloud.gov Support (🗣)

Channels marked with (🗣) receive a lot of messages, either from customers or bots, and you may want to mute them.

Learn our policies and procedures
In addition to the topics in the trainings section, review the following documents:

[ ] Review the cloud.gov open source policy guidance about protecting sensitive information.
[ ] Read the Continuous Monitoring Strategy, particularly the cloud.gov team responsibilities.
[ ] Read the Configuration Management Plan.
[ ] Read the cloud.gov Security Policies and Procedures. These documents explain the high-level policies and procedures we must comply with while running cloud.gov, sorted into security control "families" They explain that we follow GSA IT security policy, and they provide a summary of the procedures in our System Security Plan.
[ ] Review the System Security Plan (the latest version lives on Google Drive; look for "cloud.gov System Security Plan (SSP)" as a .docx file). Of particular note for onboarding: Section 9 (System Description) and Section 10 (System Environment)
[ ] Review the team's Engineering Practices. Some of these are mandatory because they fulfill FedRAMP requirements.

Getting to know cloud.gov
Resources on cloud.gov:

[ ] View the video: A Technical Overview of cloud.gov
[ ] Read the Delivery Process document to learn about how we work.
[ ] Read our service disruption guide to learn how we handle customer-facing service disruptions.

Resources on CloudFoundry/BOSH:

[ ] Look at Opensourced content for cloud foundry training classes: zero to hero (beginner), bosh/operator, and microservices
[ ] Here is some training materials: GitHub - CloudCredo/training-operating-the-foundry: Training materials for Operating a Platform: BOSH and Everything Else
[ ] Very thorough documentation on BOSH: Ultimate Guide to BOSH
[ ] BOSH 101 presentation recording and slides

Getting hands-on with cloud.gov:

[ ] Sign up for a cloud.gov sandbox using your GSA email address and start experimenting to get familiar with the basics of the PaaS from a user's perspective.

This is also required in order to make you a platform admin once you've completed the Cybersecurity and Privacy training.

Engineering-specific items
Machine admin rights

[ ] In order to install development tools on your Mac, you will need to request local admin rights by submitting a ServiceDesk ticket using this justification. If you're unable to create a ticket for yourself, your onboarding buddy can create one for you.

Engineering account management
Before starting this section, you must complete:

GSA IT Security & Privacy Awareness Training
Role-based trainings listed under Learn our policies and procedures

AWS user names should be identical across accounts so that permissions can be correctly managed by Terraform.

[ ] Create AWS Accounts by following these instructions. These accounts should be setup as read-only at the start, and once the 3 mandatory cloud.gov trainings are complete they will be switched to full admin accounts and added to the audit input file:

[ ] AWS Commercial accounts
[ ] AWS GovCloud accounts
[ ] Ensure new person creates a 55-day Google Calendar reminder to update passwords, which expire every 60 days

[ ] Add them to Nessus Manager via the GUI

[ ] Add them to the ScanAdmins team in Settings > Groups

    Federal employees and staff contractors, expand this section:

You are a member of the Cloud Operations team, which means you have additional administrative permissions:

[ ] Make them an admin of the platform.
[ ] Add them to the platform-ops team in GitHub.
[ ] Add them as an admin on the cg-django-uaa docs
[ ] Add them to our dockerhub org and ensure we're not over our license count
[ ] Add them as an agent to the cloud.gov support Zendesk (Ask a cloud.gov member with admin access to Zendesk to add them).
[ ] Add them as Technical users to Ubuntu Advantage (Admin users for leads and supervisors)

Additional compliance setup/review

[ ] Install caulking git leak prevention by following the README
[ ] Verify caulking by running make audit and pasting a screenshot as a comment on this GitHub issue
[ ] Set GPG signing set up for GitHub (instructions here) and paste the output of git config commit.gpgsign as a comment on this GitHub issue

Install a development environment for cloud.gov

Note: Make sure you have followed the instructions in Machine admin rights at the top of this section to get local admin rights on your machine before moving forward

[ ] Install Homebrew (brew)
[ ] Clone the product repo, cd into it, and run brew bundle install to install everything in Brewfile.
[ ] Verify CloudFoundry installation via the CLI (once an existing cloud.gov teammate has made your cloud.gov admin account)

cf login -a api.fr.cloud.gov --sso
cf orgs

As a cloud.gov team member, you should have a long list of organizations
If you have none or one (e.g. sandbox) org, please reach out to your onboarding buddy

[ ] Configure aws-vault by following our directions
[ ] Fix fly, the Concourse CLI, by running xattr -d com.apple.quarantine $(brew --prefix)/bin/fly. Concourse does not sign fly with an Apple Developer account, so you must use xattr to manually remove the binary from quarantine. Verify by running fly -h in your command line.
[ ] Install cloud.gov dev tools by cloning the cg-scripts repo: run git clone https://github.com/cloud-gov/cg-scripts.git in your command line

Figure out your first tasks
Project contractors: Check in with your project lead about first tasks.

    Federal employees and staff contractors, expand this for instructions:

The engineering team currently contains the following squads, each with their own projects:

Assurance, which focuses on security and compliance
Platform, which maintains and improves cloud.gov, focusing on internals like our AWS architecture and Cloud Foundry
Customer Success, which focuses on customer-facing features like service brokers and observability tools

If you are not already assigned to a particular squad, work with your onboarding buddy to join squad standups and learn what each squad is working on.

Assurance-specific items
These items are only mandatory for someone stepping into an Assurance squad role, but you are welcome to subscribe even if you are on another squad:

[ ] Subscribe to CISA alerts/updates: https://www.cisa.gov/about/contact-us/subscribe-updates-cisa
[ ] Subscribe to FedRAMP mailing lists: https://public.govdelivery.com/accounts/USGSA/subscriber/topics?qsp=USGSA_2224
[ ] Read Compliance Lead documents at root of the Google Drive Security and Compliance folder

Using the General Checklist for project contractors: https://github.com/cloud-gov/product/issues/3104


Added Kitematic blog post

Not sure when this should be published, but take a look and see if it needs any corrections.

I have updated with more Crate details. After reading this you may feel that Kitematic isn't particularly suited to Crate!
That's a fair assessment and maybe we don't want to publish the post… or maybe we do, I leave it up to team decision.

I think that we should reach out to the Docker folks and see what their road map for it is. Maybe if they are fixing some of the blockers we can time releasing our post with their launch and get more PR out of it.

I think we close this for now @spanktar it's too late and doesn't work that well with Crate anyway.


This plugin threw an error from the characteristic....

Hi, i'm getting various errors on the Log-File....
Versions
Homebridge v1.3.4
Node v14.17.0
homebridge-roomba2 v1.2.0
Homebridge Log / Command Output
[12.6.2021, 11:06:33] [homebridge-roomba2] This plugin threw an error from the characteristic 'Status Low Battery': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://git.io/JtMGR for more info.
[12.6.2021, 11:07:04] [Joey] Running status requested
[12.6.2021, 11:07:04] [Joey] Using expired status
[12.6.2021, 11:07:04] [homebridge-roomba2] This plugin threw an error from the characteristic 'On': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://git.io/JtMGR for more info.
[12.6.2021, 11:07:04] [Joey] Docked status requested
[12.6.2021, 11:07:04] [Joey] Using expired status
[12.6.2021, 11:07:04] [homebridge-roomba2] This plugin threw an error from the characteristic 'Contact Sensor State': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://git.io/JtMGR for more info.
[12.6.2021, 11:07:04] [Joey] Running status requested
[12.6.2021, 11:07:04] [Joey] Using expired status
[12.6.2021, 11:07:04] [homebridge-roomba2] This plugin threw an error from the characteristic 'Contact Sensor State': Unhandled error thrown inside read handler for characteristic: This callback function has already been called by someone else; it can only be called one time.. See https://git.io/JtMGR for more info.

@Althir81
Can you still reproduce this with the latest version of the plugin? (It's 1.2.2 as I write this.) I remember seeing the same thing a while ago, but I didn't see it in 1.2.2 a few days ago.
If you're still seeing it, would you be willing to try the beta? Lots of fixes and improvements (including some options for additional sensors). 1.3.0-beta.6 is the latest as of this moment. You can install it using the wrench icon > Install Previous Version.


ppci-cc: cpp stringify operator # expansions too simplistic

The preprocessor stringify operator # is supported but the resulting expansions are not always correct.
(behaviour for 0.5.7)

#define S(a) #a
S(word) => "word"            // correct
S("string") => ""string""    // instead of ""string"" (double quotes should be escaped)
S('a') => "'a'"                      // correct
S("aa\tbb") => ""aa\tbb"    // instead of  ""aa\tbb"" (backslashes should be escaped)
S(  1) =>> "  1" au lieu de "1"    // leading and trailing blanks should be ignored
S(  1  2      3  ) => "  1  2  3" au lieu de "1 2 3"    // only one separator is kept between tokens

Wow, nice catch. The preprocessor never ceases to amaze me :).
Implemented a fix in 26239aad6fec269b2aa34724dece80351da63761

The fix looks good.
is tricky but ## is even worse!

Closing this issue, since it seems to operate properly.


jni.h not found

Checklist

My GCC is 6.2.0(minGW on windows 10)
linter-gcc is 0.6.15
C Source Code is here.

#include <jni.h>
// This line makes an error. This header file is in "C:\Program Files\Java\jdk1.8.0_111\include"
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "CheckIntegrity.h"
// Implementation of native method checkItem() of CheckIntegrity class
JNIEXPORT jstring JNICALL Java_CheckIntegrity_checkItem
(JNIEnv *env, jobject thisObj, jstring inJNIStr)
{
// Get a class reference for java.lang.Integer
jclass cls = NULL;
jmethodID mtdID = NULL;
jobject newObj = NULL;
// Step 1: Convert the JNI String (jstring) into C-String (char*)
const char *inCStr = (*env)->GetStringUTFChars(env, inJNIStr, NULL);
if (NULL == inCStr) return NULL;
// Step 2: Perform its intended operations
printf("In C, the received string is: %s\n", inCStr);
(*env)->ReleaseStringUTFChars(env, inJNIStr, inCStr);  // release resources
// Prompt user for a C-string
char outCStr[128];
printf("Enter a Line: ");
gets(outCStr);    // not more than 127 characters
if (strcmp(outCStr, inCStr) != 0) {
printf("Different Strings : %s %s\n", inCStr, outCStr);
exit(0);
}
else {
printf("Same Strings : %s %s\n", inCStr, outCStr);
}
cls = (*env)->FindClass(env, "AnotherFunction");
if (cls == NULL) {
printf("Class Not Found");
exit(0);
}
mtdID = (*env)->GetMethodID(env, cls, "printInput", "(Ljava/lang/String;)V");
if (mtdID == NULL) {
printf("Method Not Found");
exit(0);
}
newObj = (*env)-> AllocObject(env, cls);
(*env)->CallObjectMethod(env, newObj, mtdID, inJNIStr);
// Step 3: Convert the C-string (char*) into JNI String (jstring) and return
return (*env)->NewStringUTF(env, outCStr);
}
Issue (including debugging messages):
My log messages are like  belows. I set my configuration to have "C:\Program Files\Java\jdk1.8.0_111\include" and "C:\Program Files\Java\jdk1.8.0_111\include\win32" as additional include path.
The situation is:

If I type Ctrl-S to invoke linter-gcc, it says jni.h: No such file or directory at line 1 col 17
If I copy the real command from console and try to run it in DOS command prompt, it compiles normally.

I can't solve this problem for now. That is why I raise an issue to you.
linter-gcc: Using configuration page settings
linter-gcc config: {"execPath":"gcc.exe","gccIncludePaths":""C:\Program Files\Java\jdk1.8.0_111\include","C:\Program Files\Java\jdk1.8.0_111\include\win32"","gccSuppressWarnings":false,"gccDefaultCFlags":"-c -Wall -fsyntax-only","gccDefaultCppFlags":"-c -Wall -std=c++11 -fsyntax-only","gccErrorLimit":0,"gccErrorString":"error","gccWarningString":"warning","gccNoteString":"note"}
linter-gcc: C:\Program Files\mingw-w64\x86_64-6.2.0-posix-seh-rt_v5-rev1\mingw64\bin\gcc.exe -c -Wall -fsyntax-only -fmax-errors=0 -I"C:\Program Files\Java\jdk1.8.0_111\include" -I"C:\Program Files\Java\jdk1.8.0_111\include\win32" D:\test\CheckIntegrity.c

I think this problem is related to System Policy, which does not allow ordinary programs to do something in Program Files Directory to make it possible to clean up windows itself without clean-install. Atom seems to search some virtual store and jni.h is not there.  I came to this conclusion and just copied original Java include directory to C;\jni_dev, which worked. I want to know what has really happened while trying to access C:\Program Files\Java\jdk1.8.0_111\include\jni.h.

You can turn on the debugging option of linter-gcc, then open the Developer Console by pressing Ctrl+Shift+I or Cmd+Shift+I, then clicking on 'Console'. All linter-gcc config and the entire command should be visible in the console.


NetBox-synced: Orphaned tag colour being reverted

The plugin always overwrites the auto-generated orphaned object tag colour with gray (607d8b) with each sync. Is this intentional? I'd like to give that particular tag a more prominent colour, so would be nice if it were allowed to survive. Changed colours already persist for other plugin-generated tags, but for some reason not this one.

Hi, sorry, that is a bug. Will fix this in the next release.

Cheers

Hey, just pushed a new commit to the development branch which should fix the issue.
would you be able to test it? thank you

Yes, just tested it and the colouring persists. Thank you!

great, thank you for testing it


docs: add instructions for updating deprecated resources

About this change—what it does
Adds deprecation notices to the aiven_project_user and aiven_organization_group_project resources. Consolidates existing migration guides into one and adds instructions for migrating these deprecated resources to aiven_organization_permission.

LGTM 👍🏼


I don't see the task and the run botton and i can not submitted the assignment

ADD ISSUE DESCRIPTION HERE
Version: 1.87.2
Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 Edg/<IP_ADDRESS>
Embedder: codespaces

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Add simplified Chinese translation

Many Chinese players and I really like your Mod! But it has no Chinese translation yet. So I added a Chinese translation! :D
(Not using Google Translate. All translations have been proofread. Thanks!)

Sorry it took so long to merge


Line manager UI updates

https://uktrade.atlassian.net/browse/JMLL-1102
https://uktrade.atlassian.net/browse/JMLL-1111
https://uktrade.atlassian.net/browse/JMLL-1112
https://uktrade.atlassian.net/browse/JMLL-1115
https://uktrade.atlassian.net/browse/JMLL-1117
https://uktrade.atlassian.net/browse/JMLL-1118
https://uktrade.atlassian.net/browse/JMLL-1119

Codecov Report
Base: 72.32% // Head: 71.06% // Decreases project coverage by -1.25% :warning:

Coverage data is based on head (2b1f430) compared to base (ffc7c3a).
Patch coverage: 40.77% of modified lines in pull request are covered.

Additional details and impacted files
@@                     Coverage Diff                     @@
##           feature/leaver-ui-forms     #243      +/-   ##
===========================================================
- Coverage                    72.32%   71.06%   -1.26%
===========================================================
  Files                          206      207       +1
  Lines                         7721     7779      +58
===========================================================
- Hits                          5584     5528      -56
- Misses                        2137     2251     +114

Impacted Files
Coverage Δ

core/staff_search/forms.py
55.00% <ø> (ø)

leavers/forms/leaver.py
73.42% <ø> (ø)

leavers/tests/views/test_line_manager.py
100.00% <ø> (ø)

leavers/urls.py
100.00% <ø> (ø)

leavers/views/line_manager.py
41.39% <21.12%> (-14.04%)
:arrow_down:

core/staff_search/views.py
42.10% <50.00%> (+1.03%)
:arrow_up:

leavers/types.py
96.77% <66.66%> (-1.54%)
:arrow_down:

leavers/forms/line_manager.py
53.96% <85.00%> (-20.63%)
:arrow_down:

...ns/0067_alter_leavingrequest_leaver_paid_unpaid.py
100.00% <100.00%> (ø)

leavers/utils/emails.py
79.87% <100.00%> (+0.38%)
:arrow_up:

... and 3 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


PORT problems again :(

Sorry, but I'm still struggling with PORT problems, though I did get past #81, which is great!
When I scale my web app to 2, here's what gets created for the second node:
cat /etc/systemd/system/onebody-web-2.service

[Unit]
StopWhenUnneeded=true
Requires=onebody-web.service
After=onebody-web.service

[Service]
Environment=PORT=3001
ExecStart=/usr/bin/onebody run web
Restart=always
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=%n

[Install]
WantedBy=onebody-web.service

The PORT is set in the environment as I expected, great!
However, when I start the service, this second node thinks the PORT is set to 3000. 😣
sudo systemctl status onebody-web-2

● onebody-web-2.service
   Loaded: loaded (/etc/systemd/system/onebody-web-2.service; enabled)
   Active: active (running) since Thu 2015-09-24 22:37:29 CDT; 293ms ago
 Main PID: 11433 (ruby)
   CGroup: /system.slice/onebody-web-2.service
           └─11433 ruby /opt/onebody/vendor/bundle/ruby/2.2.0/bin/thin start -p 3000

I've tracked the problem down (I think) to line 300 of the binary generated by pkgr, which reads:
exec chroot --userspec ${APP_USER}:${APP_GROUP} "/" sh -c "cd $(_p ${APP_HOME}) && $runnable"

This line doesn't seem to transfer the environment over? I'm a bash n00b, so I don't really know how to fix this.
But I did verify the PORT is read properly if I change this line to read:
exec chroot --userspec ${APP_USER}:${APP_GROUP} "/" sh -c "cd $(_p ${APP_HOME}) && PORT=3001 $runnable"

(I know that's lame, but just wanted to confirm where the environment isn't getting transferred over.)
Any thoughts on how to fix?

OK, some more debugging, and I'm way off of course. 😜
If I echo $PORT >> /tmp/port.txt from within the pkgr-generated /usr/bin/onebody binary, it writes 3000 to the file for both processes. So PORT isn't getting set by this time either. So maybe it's a problem with how the systemd service file is set up??
At least I have some more stuff to google now. 😀

I think I found it!
In the binary, the /etc/onebody/conf.d/other file is read, and it contains export PORT=3000 because that's what I set it to when I ran onebody config:set PORT=3000.
https://github.com/crohr/pkgr/blob/master/data/cli/cli.sh.erb#L51-L55
for file in $(_p "/etc/${APP_NAME}/conf.d")/*; do
  if [ -f $file ]; then . $file; fi
done

Here is a patch that "fixes" the issue:
diff --git a/data/cli/cli.sh.erb b/data/cli/cli.sh.erb
index a6d213a..e39adea 100644
--- a/data/cli/cli.sh.erb
+++ b/data/cli/cli.sh.erb
@@ -50,6 +50,7 @@ fi

 # Source all environment variables for the app. This must be done as
 # privileged user since the config variables are only readable by root.
+PORT_WAS=$PORT
 for file in $(_p "/etc/${APP_NAME}/conf.d")/*; do
   if [ -f $file ]; then . $file; fi
 done
@@ -293,6 +294,9 @@ while : ; do
         runnable="${runnable}$(printf " %q" ${COMMAND} "$@")"
       fi

+      # fix port
+      export PORT=$PORT_WAS
+
       # Do not use su, to avoid creating a new process. Note: chroot version
       # is too old on Ubuntu Lucid, so this will fail. It works on Debian
       # Squeeze though (and later).

I'm sure this isn't the right way to fix this issue, though. If you care to direct me, I'll be happy to make a PR.

@seven1m you're right, environment variables declared in /etc/app/conf.d/* will overwrite anything set in the init scripts. Since PORT is the only variable that needs special treatment, maybe something similar to your fix could be used. I'll think about it.


Installation instructions - and the LSL.xml file

In the installation instructions at:
In these installation instructions:
https://www.jetbrains.com/help/pycharm/directories-used-by-the-ide-to-store-settings-caches-plugins-and-logs.html#plugins-directory
I am attempting to run this LSL plugin in PyCharm. In PyCharm's "Plugins" tab there is an option to install the "Linden Script (LSL)" plugin. No mention of this way to install this plugin is in the instructions. This raised the question whether it is sufficient to use the Plugins tab to install "Linden Script (LSL)" only, whether the LSL.xml file should also be installed, or whether the LSL.xml file installation is mutually exclusive with installation using the Plugins tab.
Because the instructions do not state that a project must be created before it is possible to navigate to "File > Settings > Editor > Files types" there was confusion as to how to navigate to there. It appeared only after creating a Python project. There I found "*.lsl" already present due to, I believe, the use of the Plugins tab to install the "Linden Script (LSL) language plugin".
I tested this LSL plugin without installing LSL.xml and it does seem to work.

The correct way to install the plugin is using plugins repository in IDE settings.
But ok, I will write better documentation later.


Use SPDX license expression in project metadata

As a downstream user it is desirable to be able to programmatically determine the precise licenses used by our dependencies. The emerging convention for this is the SPDX License List. SPDX License Expressions are already used in the JavaScript (npm) and Rust (crates.io) ecosystems, for example.
In Python, there is PEP 639 which would add a standard 'License-Expression' metadata field. The discussion around this PEP seems to have gone stale in 2021.
This merge request is in lieu of that PEP coming soon. Unless you as project maintainers think the proposed change in this PR has downsides (which you are entitled to!), I would ask that you accept this change so that it's possible for users to attempt to parse your license metadata as an SPDX License Expression.
In particular, it disambiguates which BSD license it is.

@asottile-sentry please sanitycheck

imo we shouldn't manually set this field and have something like setup-cfg-fmt control the fields for us


[Bug]: Improve the login/signup page.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Current login/signup page do not have proper styling and no proper alignment, due to which the page is not much attractive.
Expected behavior
Assign this task to me and I can add styling on this page to make it attractive.
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a VSOC'24 contributor
[X] I have starred the repository

Hey @meetarora10, can you please checkout the page again cause I am seeing a proper page with a good UI

Yes thank you for commenting @itsekta


Multiple identically-named targets are built via Carthage in a non-deterministic order

New Issue Checklist

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

Issue Info
N/A
Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.

Currently, Lumberjack.xcworkspace has two targets that build a framework named CocoaLumberjack.framework and support the iphoneos architecture:

The universal CocoaLumberjack target
The iOS-specific CocoaLumberjack-iOS target

When CocoaLumberjack is built via Carthage, the build ordering is nondeterministic. As such, depending on the order that carthage builds in, you will either end up with the universal or platform-specific framework in your Carthage/Build directory.
Ideally, to resolve this, there would not be multiple targets that produce identically-named products that support the same architecture.
Here's some logs from two invocations of carthage build on Carthage 0.18:
➜ carthage build CocoaLumberjack --platform ios
*** xcodebuild output can be found in /var/folders/9s/rl0z7g591cs9frc53y6cbpzm0000gp/T/carthage-xcodebuild.aUzRnB.log
*** Building scheme "CocoaLumberjack" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjack-iOS" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjackSwift-iOS" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjackSwift" in Lumberjack.xcworkspace

➜  carthage build CocoaLumberjack --platform iOS
*** xcodebuild output can be found in /var/folders/9s/rl0z7g591cs9frc53y6cbpzm0000gp/T/carthage-xcodebuild.8atmBi.log
*** Building scheme "CocoaLumberjackSwift-iOS" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjack" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjack-iOS" in Lumberjack.xcworkspace
*** Building scheme "CocoaLumberjackSwift" in Lumberjack.xcworkspace

You can see above that the frameworks are being built in a nondeterministic ordering, which will end up with it being undefined whether you get the universal or iOS-specific framework in your Carthage/Build/iOS directory.

Should be fixed by #819.
Right, @sushichop?

@bpoplauschi
Yes, that's right! Thanks to @erichoracek's great suggestion, I was able to fix this😁
@erichoracek
Thanks!


repository setup tracking issue

This issue is to track the things need to be done for completely setup our repository.

[ ] add fossa checker for licenses checking
[x] add prowbot support for auto merging pr etc.
[ ] update docker image repo
[ ] add e2e testcases, current empty

progress:
finish to add prowbot support by adding kubeedge-bot to this project.

for the issue:

update the container image repo of installation doc


Standardize time library used across IF repositories

Rationale
We currently use multiple time libraries across multiple plugins - in particular dayjs in mockobservations, luxon in time-sync, and we still have momentjs in our package-lock.json in if-unofficial-models. We need to standardize across our repos to improve maintainability and minimize the risk of bugs.
Implementation details
Migrate all date-time handling to Luxon
Priority
3/5
Size
1 - 1.5 days
What does "done" look like?
All current behaviours are maintained but only one time library is used.
Does this require updates to documentation or other materials??
Documentation updates are not expected to be required
Deadline
n/a
Acceptance criteria
All unit and integration tests pass
Dayjs and momentjs are removed from all repositories

watt-time plugin done
mockobservations done
will check for more requirements before closing issue

Closing as complete


Add missing blob type to load methods

Encountered this pretty quickly as I was working on downstream types >.>

Alright, will merge later this week.


Chrome window

To maximize the chrome window as firefox does it by default but not chrome.
1st time pulling a request please let me know of the wrong done.

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

Thank you and congratulations on your first PR!
I'm not sure I want to change the default behavior. I suspect Selenium / ChromeDriver has a reason for not starting maximized. For example, it is probably useful while developing, because then you can have a console window open next to the browser.
So I'm not going to merge this PR. But I want to take it as an opportunity to give you a few suggestions:
First, the following line:
if headless == False:

This can be shortened to:
if not headless:

What's more, the two are actually not the same. In Python, values other than False can make an if check fail. For example:
my_str = "" # empty string
if my_str: # checks whether the string is not empty

By comparing == False, you are changing the general expectation in Python, which is that values other than False can also represent a condition not being True. So I'd advise to always use if not my_variable instead of if my_variable == False.
Second, commit messages should usually be in imperative. You have:

To maximize the window size of Chrome browser
To open Chrome in maximized window

Easier to read would (for me) be:

Make start_chrome(...) maximize the Chrome window

Hope this helps :-)


Add Option to select Firewall SKU

Overview/Summary
Replace this with a brief description of what this Pull Request fixes, changes, etc.
This PR fixes/adds/changes/removes

Adds Option to select Firewall SKU

Breaking Changes

None

Testing Evidence

As part of this Pull Request I have

[x] Checked for duplicate Pull Requests
[x] Associated it with relevant issues, for tracking and closure.
[x] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x] Performed testing and provided evidence.
[x] Updated relevant and associated documentation.
[x] Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)

Apart from above comment - tested deployments for both vWAN and H&S and works well! 👏


automatic including order adjustment should ignore pch.h

automatic including order adjustment should ignore some special head files(tipically pch.h), otherwise, it will always causes comlilation errors.

Hi @3roman,
Unfortunately, we don't have support for that, and we don't have in plan to make some changes in the near future.
But I recommend something that we are using too, disable format on a piece of code
Clang-format understands also special comments that switch formatting in a delimited range. The code between a comment // clang-format off or /* clang-format off */ up to a comment // clang-format on or /* clang-format on */ will not be formatted.
Best regards,
Marina


Job queue for global entities

Need a job queue to control request rate globally. Otherwise, the API will deny the request:
{
	"ok": false,
	"error_code": 429,
	"description": "Too Many Requests: retry after 33",
	"parameters": {
		"retry_after": 33
	}
}

According to the official document, limit rate is once per second.

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

https://core.telegram.org/bots/faq#my-bot-is-hitting-limits-how-do-i-avoid-this

Summary, two way to solve that:

Build-in rate limit function decorator

The defult rate is one post per second (user-transparent)

Allow to add multiple bot tokens.

Add new bot token at the top of program.
from telegram_news.template import NewsPostman
NewsPostman.add_bot_token(os.getenv("TOKEN2"))


Winds of Change

Suggest 2 different style guides for Hexa.

https://xd.adobe.com/view/d79f719e-c1ad-405f-9eec-eaca155430dd-82cc/


Release note for BitRound input mutation fix

Adds a release note for PR: https://github.com/zarr-developers/numcodecs/pull/608
TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] Tests pass locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] Docs build locally
[ ] GitHub Actions CI passes
[ ] Test coverage to 100% (Codecov passes)

Thanks!


Custom next function

I have been trying saga pattern in cloud workflows, since it is workflow orchestration error handling and rollback is important thing here so i have been trying this, but i needed a feature request on passing custom next functions on sub workflows in order to achieve this pattern to work, otherwise it would have more bloated code to do this same without that feature.
---
main:
  steps:
    - book-flight:
        call: post
        result: flightData
        args:
            url: https://***.ngrok.io/book-flight
            next: cancel-flight
    - book-hotel:
        call: post
        result: hotelData
        args:
             url: https://***.ngrok.io/book-hotel
             next: cancel-hotel
    - book-taxi:
        call: post
        result: taxiData
        args:
          url: https://***.ngrok.io/book-taxi
          next: cancel-taxi
    - cancel-flight:
        call: post
        result: flightCancelData
        args:
          url: https://***.ngrok.io/cancel-flight
          next: returnData
    - cancel-hotel:
        call: post
        result: hotelCancelData
        args:
          url: https://***.ngrok.io/cancel-hotel
          next: returnData
    - cancel-taxi:
        call: post
        result: taxiCancelData
        args:
          url: https://***.ngrok.io/cancel-taxi
          next: returnData
    - returnData:
        return: ${"Flight Res "+flightData.body.message+" Hotel Res "+ hotelData.body.message+ " Tax Res "+taxiData.body.message}
post:
  params: [url, next]
  steps:
    - postAPI:
        try:
          call: http.post
          args:
            url: ${url}
            headers:
              Content-Type: text/plain
              Content-Accept: text/plain
            query: {}
          result: data
        retry: "${http.default_retry_non_idempotent}"
        except:
          as: e
          steps:
            - callNext:
                next: ${next}
    - returnData:
        return: ${data}

When i deploy this workflow i get a error message failed to build: error calculating label indices: attempt to jump to non-existing step ${next}.

Jumping between subworkflows is not allowed. In other words, the following is invalid:

callNext:
next: ${next}

Consider putting book-* and cancel-* steps under subworkflow post.


Fix common uses of INSERT AFTER with .bss and .text

Fixes #267
Fixes #266
This fixes two related issues.

Named sections are often inserted after .bss or .text in order to have them handled as if they were part of that section. Defining the start/end symbols outside of the section allows this to work.
Uninitialized C statics will end up as common symbols which end up in the COMMON input section. If this section is orphaned, it will likely end up placed after .bss. C code often expects these statics to be zero initialized. The first change would cause these symbols to be placed before __ebss so they will get zeroed by the reset handler. Explicitly placing the common symbols into .bss ensures this happens. Users who want uninitialized symbols should use the .uninit section.

See https://github.com/rust-embedded/cortex-m-rt/pull/287#issuecomment-677743856

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @therealprof (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

I'm a bit confused why the label placement inside the section doesn't have the same effect.  Is this known linker behaviour causing the label _ebss to be calculated too early?
Anyway this looks fine to me. Any objections @jonas-schievink @adamgreig ?

I'm sure this linker script is the most touched file in the repo and I'm always worried a simple PR will cause some undetected bug in six month's time, especially trying to support gcc and lld simultaneously.  This looks fine but I also don't understand why it's needed exactly. @mattico, could you elaborate on the motivation for this change?
It looks like maybe the common use of INSERT AFTER to add extra sections from memory.x could cause those sections to be added after .bss and therefore also after _ebss, whereas with it defined outside that block those extra sections are added between .bss and _ebss?

It looks like maybe the common use of INSERT AFTER to add extra sections from memory.x could cause those sections to be added after .bss and therefore also after _ebss, whereas with it defined outside that block those extra sections are added between .bss and _ebss?

I believe this is correct. Also my GCC is doing something like INSERT AFTER for statics for some reason.
I'll try to get a more thorough understanding of the issue.

Alright so.
https://sourceware.org/binutils/docs/ld/Miscellaneous-Commands.html

INSERT [ AFTER | BEFORE ] output_section
This command is typically used in a script specified by '-T' to augment the default SECTIONS with, for example, overlays. It inserts all prior linker script statements after (or before) output_section, and also causes `-T' to not override the default linker script. The exact insertion point is as for orphan sections. See Location Counter. The insertion happens after the linker has mapped input sections to output sections. Prior to the insertion, since '-T' scripts are parsed before the default linker script, statements in the '-T' script occur before the default linker script statements in the internal linker representation of the script. In particular, input section assignments will be made to '-T' output sections before those in the default script. Here is an example of how a '-T' script using INSERT might look:

Not overriding the default linker script was an unexpected turn. However my reading of the rest is that it doesn't matter since our definitions come first for things we care about. As far as where things get inserted...
https://sourceware.org/binutils/docs/ld/Orphan-Sections.html

Orphan sections are sections present in the input files which are not explicitly placed into the output file by the linker script. The linker will still copy these sections into the output file, but it has to guess as to where they should be placed. The linker uses a simple heuristic to do this. It attempts to place orphan sections after non-orphan sections of the same attribute, such as code vs data, loadable vs non-loadable, etc. If there is not enough room to do this then it places at the end of the file.

Along with https://reviews.llvm.org/D42482
Seem to indicate that the linker will place INSERT AFTER somewhere after but not necessarily immediately after.
https://sourceware.org/binutils/docs/ld/Location-Counter.html

If the linker needs to place some input section, e.g. .rodata, not mentioned in the script, it might choose to place that section between .text and .data. You might think the linker should place .rodata on the blank line in the above script, but blank lines are of no particular significance to the linker. As well, the linker doesn't associate the above symbol names with their sections. Instead, it assumes that all assignments or other statements belong to the previous output section, except for the special case of an assignment to .. I.e., the linker will place the orphan .rodata section as if the script was written as follows:

SECTIONS
{
    start_of_text = . ;
    .text: { *(.text) }
    end_of_text = . ;

    start_of_data = . ;
    .rodata: { *(.rodata) }
    .data: { *(.data) }
    end_of_data = . ;
}

This may or may not be the script author's intention for the value of start_of_data. One way to influence the orphan section placement is to assign the location counter to itself, as the linker assumes that an assignment to . is setting the start address of a following output section and thus should be grouped with that section. So you could write:

SECTIONS
{
    start_of_text = . ;
    .text: { *(.text) }
    end_of_text = . ;

    . = . ;
    start_of_data = . ;
    .data: { *(.data) }
    end_of_data = . ;
}

Now, the orphan .rodata section will be placed between end_of_text and start_of_data.

This indicates that when the start/end symbols are outside of the section, the linker may place orphan sections between them, which may not be desirable.
Looking at the default linker script from arm-none-eabi-ld --verbose:
  . = .;
  __bss_start = .;
  __bss_start__ = .;
  .bss            :
  {
   *(.dynbss)
   *(.bss .bss.* .gnu.linkonce.b.*)
   *(COMMON)
   /* Align here to ensure that the .bss section occupies space up to
      _end.  Align after .bss to ensure correct alignment even if the
      .bss section disappears because there are no input sections.
      FIXME: Why do we need it? When there is no .bss section, we do not
      pad the .data section.  */
   . = ALIGN(. != 0 ? 32 / 8 : 1);
  }
  _bss_end__ = .; __bss_end__ = .;
  . = ALIGN(32 / 8);
  . = SEGMENT_START("ldata-segment", .);
  . = ALIGN(32 / 8);
  __end__ = .;
  _end = .; PROVIDE (end = .);

It uses the . = .; trick and defines the symbols outside of the section. I can only assume this is done for the benefit of INSERT BEFORE/AFTER, none of the other symbols are defined this way other than _etext.
However for my case, that *(COMMON) directive is the important bit. It turns out that C compilers will sometimes not put uninitialized statics in any input section but instead mark them as common. These common symbols end up in a pseudo-input-section which, if orphaned, may get inserted after .bss. So by moving __ebss out of the section I was accidentally moving it after the common symbols. This was confusing because the common symbols were said to be in .bss by objdump though they were after __ebss and well after start+size for the section.
My conclusion is that linker behavior is rather poorly specified. I think we should follow the default linker script here because it seems to work. However, the only thing I really want now is to add *(COMMON) for the benefit of C static libraries.

That's a very strange CI failure
 + cargo rustc --target thumbv7m-none-eabi --example alignment --
...
  = note: rust-lld: error:
          BUG(cortex-m-rt): the LMA of .data is not 4-byte aligned

I can't see how .data is affected at all by the changes. The error only occurs with rustc 1.39.0. Maybe a bug in the included version of lld?

The issue was the alignment of the sections when stored in flash. It seems that old lld had a bug when dealing with aligned sections  and > RAM AT>FLASH causing the sections to overlap.
I added . = ALIGN(4); back into both sections which works round that bug and is more in line with the default linker script. It ensures the actual sections are padded out to the alignment.
We still want the align directives before the end symbols. Sections inserted before them might not have aligned ends and our zero_bss routine needs the symbols to be aligned.

I can confirm this change works to fix the issues, I haven't noticed any bad effects from it either. (I have been using a custom linker script with this change for a while).
Also, the same issue is present with __edata and __erodata. I think all the __e* symbols should be defined after the section, not inside it.

I'm always worried a simple PR will cause some undetected bug in six month's time

ha ha!
We document that if you want to add new memory sections you can put them in memory.x and then use INSERT AFTER .bss. A main reason to do this is adding sections like CCMRAM, USB RAM, or other bits of RAM that are at weird places in the address map and you'd like to store things in. However as I just found out, this PR of course means __ebss will now point to after those far away sections. So we hardfault at reset! Oops.
I'm not immediately sure what the best remedy is, but if nothing else this will (when released) break anyone with INSERT AFTER .bss in their memory.x for sections that actually shouldn't go after BSS in the memory map. I feel like there's a reason to put INSERT AFTER (to stop the new section going right at the top?), but I can't remember it for sure. It doesn't seem like there's anything else we can suggest as a later "AFTER" target, either, since all our sections now have their end flags after the section body. Anyone have any ideas?

I'm always worried a simple PR will cause some undetected bug in six month's time

ha ha!
We document that if you want to add new memory sections you can put them in memory.x and then use INSERT AFTER .bss. A main reason to do this is adding sections like CCMRAM, USB RAM, or other bits of RAM that are at weird places in the address map and you'd like to store things in. However as I just found out, this PR of course means __ebss will now point to after those far away sections. So we hardfault at reset! Oops.
I'm not immediately sure what the best remedy is, but if nothing else this will (when released) break anyone with INSERT AFTER .bss in their memory.x for sections that actually shouldn't go after BSS in the memory map. I feel like there's a reason to put INSERT AFTER (to stop the new section going right at the top?), but I can't remember it for sure. It doesn't seem like there's anything else we can suggest as a later "AFTER" target, either, since all our sections now have their end flags after the section body. Anyone have any ideas?

Leaving the __[es].* symbols outside their sections is indeed risky. It also interferes with the implicit LMA region and offset behavior of the surrounding sections (see https://releases.llvm.org/11.0.0/tools/lld/docs/ELF/linker_script.html#output-section-lma).
INSERT BEFORE .uninit or INSERT BEFORE .data works for some use cases (specifically disabled-on-reset RAMs that are NOLOAD and can't be bss and also loading into ITCM in pre_init) as long as #286 is applied. The complex behavior described and changed in https://reviews.llvm.org/D81986 may also be related.

@jordens, do you think we should move the __[es]* symbols back inside the sections, then? If we do that, there's no way for user-defined sections to be placed inside bss, though?

The intention behind __[es]* outside their link.x sections seems to be to allow users to inject sections in memory.x and have them handled through the bss zeroing and data loading mechanisms. This seems to specifically occur with linking external binary libs. E.g. and specifically #267
I'm unsure why one would need to do that for the other sections (.text, .rodata. etc) that don't need any loading/zeroing and can just be pushed into whatever output region the user wants (and also where the user wants, but only if the link between section and __[es]* symbols and the very implicit LMA stuff isn't easily broken by INSERT as it is now). Specifically #266.
Maybe the compromise is to have (a) all __s* inside the sections as there appears to be no use case that requires a user-defined section to be before the default ones within the bss or data mechanism, (b) __ebss and __edata outside to support the injection use cases above, and (c) all the other start end symbols inside the sections. That would remove lots of footguns and unnecessary hurdles for various DTCMs/ITCMs/CCRAMs/SRAMs and their custom pre_init configuration and  bss/data handlers.
I just tried the current ram2bss example (like #281) after #286 and it would happily extend __ebss to zero everything up to and including the disabled-on-reset RAM2 regardless of its NOLOAD thus breaking.
I suspect that #266 (from the top issue) and maybe also #267 (by extension) was in fact addressed by #268.
And looking through link.x.in, I'm unsure about the need for the address restriction in https://github.com/rust-embedded/cortex-m-rt/blob/8c90451a13fe21313bdde7ade0bb3b753ff519e8/link.x.in#L104
Lot's of speculation and little hard data, I know.


Adding 'go' as the release type makes changes to 'CHANGES.md' instead of CHANGELOG.md

https://github.com/googleapis/release-please/pull/890
I noticed a recent pull request adds a generic go release type and the documentation is not up to date to reflect the same.

It also seems like the go release-type creates CHANGES.md instead of updating an existing CHANGELOG.md
Is there any way to override this behaviour?

@codyoss is it common for go to use CHANGES.md rather than CHANGELOG.md? or was this design decision specific to how we were doing things on our team?

@bcoe CHANGES was a pre-existing pattern that our team Go libraries had used. I think in general CHANGELOG is more prevalent, but even then I don't actually see most projects use them as they seem to just favor using Github releases.

@codyoss I think we use go-yoshi everywhere for our internal stuff now? wondering if we could make the go releaser use CHANGELOG, and address @atreya2011's hiccup.

@codyoss Yup, we are fully migrated. That sounds good to me!

Any update on this? Would be great if the changelogPath option actually worked but even just changing the go releaser to CHANGELOG.md would already be good!

@abeMedia @atreya2011 this should be working now 👍 sorry it took a little while to get to.

Awesome, thanks!

Thank you 🙏🏼


Framework prebuilding stops unexpectedly without error reporting

Framework prebuilding stops unexpectedly without error reporting
Investigation and debugging shows that the reason is
xcodebuild: error: Unable to find a destination matching the provided destination specifier: 		{ id:A755F822-6CBD-44E5-A701-B3BF9213C2DE }
xcodebuild exit code: 70
Full xcodebuild log:
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project /Users/user/Pods/_Prebuild/Pods.xcodeproj -scheme GBVersionTracking -configuration Release -sdk iphonesimulator -destination id=A755F822-6CBD-44E5-A701-B3BF9213C2DE BITCODE_GENERATION_MODE=bitcode ARCHS=x86_64 ONLY_ACTIVE_ARCH=NO

Build settings from command line:
    ARCHS = x86_64
    BITCODE_GENERATION_MODE = bitcode
    ONLY_ACTIVE_ARCH = NO
    SDKROOT = iphonesimulator13.5

2020-06-05 17:27:45.489 xcodebuild[94241:3238393]  DTDeviceKit: deviceType from b11a830596972c49185e47df904d1244fb1800d5 was NULL
2020-06-05 17:27:45.977 xcodebuild[94241:3238328] [MT] DTDeviceKit: deviceType from b11a830596972c49185e47df904d1244fb1800d5 was NULL
2020-06-05 17:27:45.990 xcodebuild[94241:3238328] [MT] DTDeviceKit: deviceType from b11a830596972c49185e47df904d1244fb1800d5 was NULL
xcodebuild: error: Unable to find a destination matching the provided destination specifier:
		{ id:A755F822-6CBD-44E5-A701-B3BF9213C2DE }

	Available destinations for the "GBVersionTracking" scheme:
		{ platform:macOS, arch:x86_64, variant:Mac Catalyst, id:73DA9669-1F3D-5946-951B-97B3A80AA16C }
		{ platform:iOS, id:00008020-000665510252002E, name:DKPhone }
		{ platform:iOS Simulator, id:6E64AE4B-62A5-44DC-BE05-B9920E2C9B7A, OS:10.3.1, name:iPad (5th generation) }
		{ platform:iOS Simulator, id:8D35D392-AAD1-409D-975E-628EDCD59A8F, OS:13.5, name:iPad (7th generation) }
		{ platform:iOS Simulator, id:456C8A71-95EA-4B14-8582-A52F998FF0D5, OS:10.3.1, name:iPad Air }
		{ platform:iOS Simulator, id:8AD6C236-B1A4-4A90-8B70-61178C29DD02, OS:13.5, name:iPad Air (3rd generation) }
		{ platform:iOS Simulator, id:3B8A5B74-AE14-4649-96EF-C3D618DD67B2, OS:10.3.1, name:iPad Air 2 }
		{ platform:iOS Simulator, id:7BA9C36D-F193-4AAE-8337-9B67B7F7789F, OS:10.3.1, name:iPad Pro (9.7-inch) }
		{ platform:iOS Simulator, id:A1C2E6C3-AE6B-4AF3-9667-4E60756A105E, OS:13.5, name:iPad Pro (9.7-inch) }
		{ platform:iOS Simulator, id:75A03C8D-77FB-4269-8805-5F43F81E9040, OS:10.3.1, name:iPad Pro (10.5-inch) }
		{ platform:iOS Simulator, id:898E469F-3FC9-43C5-93E6-A479B65C990B, OS:13.5, name:iPad Pro (11-inch) (2nd generation) }
		{ platform:iOS Simulator, id:588C6850-07D0-4EFB-A6DC-4159DB78C961, OS:10.3.1, name:iPad Pro (12.9-inch) }
		{ platform:iOS Simulator, id:6680A122-CA8F-4BAB-BF88-E228B63BF85A, OS:10.3.1, name:iPad Pro (12.9-inch) (2nd generation) }
		{ platform:iOS Simulator, id:01673B54-7A94-4C1E-B80E-B6154201C6AE, OS:13.5, name:iPad Pro (12.9-inch) (4th generation) }
		{ platform:iOS Simulator, id:B6EFF8B2-CAC8-4BCA-9EE7-9957C4E63D81, OS:10.3.1, name:iPhone 5s iOS 10.3.1 }
		{ platform:iOS Simulator, id:E735C16F-24EC-4B77-BAD4-9ED3A7BAD17D, OS:10.3.1, name:iPhone 6 }
		{ platform:iOS Simulator, id:9F33F30C-1D0A-4FB4-9564-F8C47E297214, OS:10.3.1, name:iPhone 6 Plus }
		{ platform:iOS Simulator, id:A773802B-63A5-41B2-B08A-13F61C6E7E1F, OS:10.3.1, name:iPhone 6s }
		{ platform:iOS Simulator, id:086C0173-1E38-414E-9EA4-5D762AE1D5E4, OS:10.3.1, name:iPhone 6s Plus }
		{ platform:iOS Simulator, id:9355FFFC-B01B-4E4D-BFF6-1A9C52769D18, OS:10.3.1, name:iPhone 7 }
		{ platform:iOS Simulator, id:825908D5-10F5-454A-868F-3863735FE9CC, OS:10.3.1, name:iPhone 7 Plus }
		{ platform:iOS Simulator, id:2FE01C57-837B-4C02-ABFE-886EBF9A9CC9, OS:13.5, name:iPhone 8 }
		{ platform:iOS Simulator, id:B5682CDD-502F-4272-8F85-E22AD51A5DEC, OS:13.5, name:iPhone 8 Plus }
		{ platform:iOS Simulator, id:C9E0FC1A-2227-4265-A21E-B0E769E8958F, OS:13.5, name:iPhone 11 }
		{ platform:iOS Simulator, id:2ED5A3FD-D3F1-4FFE-AE83-15E040543C9B, OS:13.5, name:iPhone 11 Pro }
		{ platform:iOS Simulator, id:7ED3CAFC-8577-4FA7-A885-D9C4CB823F21, OS:13.5, name:iPhone 11 Pro Max }
		{ platform:iOS Simulator, id:D4E28590-1D7C-4DB6-B860-7F7EA9E1A9E6, OS:10.3.1, name:iPhone SE (1st generation) }
		{ platform:iOS Simulator, id:DF6A1913-8A12-40CA-9FF1-D6970F869C6F, OS:13.5, name:iPhone SE (2nd generation) }
		{ platform:iOS Simulator, id:57753763-695D-41E4-B300-882B6C89F71C, OS:12.4, name:iPhone Xs iOS 12.4 }

	Ineligible destinations for the "GBVersionTracking" scheme:
		{ platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Generic iOS Device }
		{ platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Generic iOS Simulator Device }
-project /Users/user/Pods/_Prebuild/Pods.xcodeproj -scheme GBVersionTracking -configuration Release -sdk iphonesimulator -destination id=A755F822-6CBD-44E5-A701-B3BF9213C2DE BITCODE_GENERATION_MODE=bitcode ARCHS=x86_64 ONLY_ACTIVE_ARCH=NO

   CocoaPods : 1.9.3
       Xcode : 11.5 (11E608c)
cocoapods-binary      : 0.4.4
  plugin 'cocoapods-binary'

Manual workaround: Open and delete excess Simulators without sdk's Xcode->Window->Devices and Simulators->Simulators

I tried to create a request with fix and discovered that this bug already fixed in master branch but not released(

This happened to me because my project was located in a path with a space in it.
E.g Documents/iOS Projects/MyProject/.
Moving it to a different location without a space fixed everything.
E.g Documents/iOSProjects/MyProject/.
Noob mistake by me, but I think it should give a better result than just coming to "Prebuilding AWKAuthCore..." then simply stopping the entire command without any message.
It should be able to precompile everything successfully, but if not, then it should give an error saying exactly why it couldn't. Or say anything at all. To me, it looked like a success, not a single error in sight, except that nothing worked.
Not gonna lie, this took me a couple of days to resolve. I didn't realize that there was a space in my path.

This happened to me because my project was located in a path with a space in it.
E.g Documents/iOS Projects/MyProject/.
Moving it to a different location without a space fixed everything.
E.g Documents/iOSProjects/MyProject/.
Noob mistake by me, but I think it should give a better result than just coming to "Prebuilding AWKAuthCore..." then simply stopping the entire command without any message.
It should be able to precompile everything successfully, but if not, then it should give an error saying exactly why it couldn't. Or say anything at all. To me, it looked like a success, not a single error in sight, except that nothing worked.
Not gonna lie, this took me a couple of days to resolve. I didn't realize that there was a space in my path.

@sfla Thanks, but this is not the reason in my case.
In my case the reason is https://github.com/leavez/cocoapods-binary/issues/127#issuecomment-639565885

I know, but seeing as I ended up in this thread after googling around for a fix yesterday, I though I should leave my solution in case others have the same as me:) Your title describes what happened to me perfectly.

I have the same issue (pre-build stopping without error being reported).
@navartis Where do I find the build log files to troubleshoot this?

@pocketpixels I found this by adding debug logging using Ruby puts func in to installed gem.


🌱 test/e2e/virtual/apiexport: make authorizer test self-contained

Summary
This makes the e2e test for virtual apiexport authorizer self-contained. The apply method will be used to add new e2e tests asserting existing issues.
Related issue(s)

All remaining comments are minor and can be tackled in follow-ups.
/lgtm
/approve

/refresh


Redesign vote status & refine LP mechanic to update market

Note - vote status also appears here: https://explorer.vega.xyz/governance
Story
As a user
I want to immediately understand the status of the vote for or against a proposal and how I can cast my own vote
So that I understand what's going to happen to this proposal, and can more obviously see the impact of governance at vega in action
Acceptance Criteria
All Votes excl. Market Updates

[ ] I can see two vote status bars showing all the information in sketch 1
[ ] When majority is reached (network param, currently 66%) the Votes For bar changes green to indicate this and the majority indicator above it turns green too
[ ] When the participation bar reaches 100% graph goes green and so does the indicator above
[ ] If the number of votes exceeds the required amount continue to show the full number, and express the %age as usual even if above 100%, but the bar should continue to just be full
[ ] I can still see whether the proposal is currently set to pass / fail (ensure we use the word "Set to" ... I have never liked expected
[ ] I can see how long is left to vote
[ ] The "Vote Breakdown" section has been removed as this is now all covered elsewhere
[ ] The "Cast Vote" section is now shown after the description and market / asset details sections
[ ] The "Full proposal JSON" section is now shown at the end after "Cast Vote"

Market Update votes

[ ] When the vote is a market update I can see an additional set of 2 graphs that capture the LP vote, with the information sourced from the relevant place on the API as shown in sketch 2
[ ] The main indicators for majority / participation should turn green based on the logic below:
[ ] If LP participation is met, then the LP participation graph should turn green, the header participation indicator should turn green, and the text in it should change to "Liquidity provider min. participation reached"
[ ] If the LP majority is reached, the LP votes for graph should turn green, the header majority indicator should turn green, and the text in it should change to "66% Liquidity provider majority voted for this proposal"
[ ] If the Token holder participation is met, then the token holder participation graph should turn green, the header participation indicator should turn green, and the text in it should change to "Token holder min. participation reached" (This should override the above).
[ ] If the Token Holder majority is reached, the Token holder votes for graph should turn green, BUT the header majority indicator should remain unchanged UNLESS token holder participation is met as above. ie. unless token holder participation is met we defer to the outcome of the LP majority as already outlined above.

N.B. Get some feedback on whether greying out the LP vote is desirable.  It might be useful to show it has been ignored, but might raise questions.   Personally I think its better with grey, Sam thinks the opposite.... we need a tie breaker! I have included sketches of the set of scenarios with greying, and also an example without to see how that looks.  I have included the blue info box component from console since we had it, but we could just have this as normal white / grey text too.
Sketches

Tasks

[x] Explore and sketch
[ ] Design - and tighten the design of the page as a whole so this fits in context
[ ] Team and stakeholder review
[ ] Team review
[ ] Etc.

Additional details / background info
Original sketches

Snapshot have an established pattern https://snapshot.org/#/aave.eth/proposal/0xb477feee6d506be940154bc84278654f2863044854f80fca825b236253a97778
Generally ours is difficult to understand - participants (who work on the project) were left unsure what was being said in the participation section.

Updated to include Barnet;s feedback, namely
1 Wanting something to indicate the association between  the bars and the labels at the top ... so I've added a little box to group them so its more obvious
2 Wanting to have the red in the no votes ... which I'm personally not sold on but for now I'm including
I've also tried sort of fading out the bar that has been overrulled in the case of the market update.  His preference was for some way of de-emphasising that but how we didnt really decide. Fading maybe is better than turning it grey?  Dont know.

Now updated with Barney's changes so think this is good to go.

Many changes to this since the sketches were last updated because Sam had a nice idea. So ignore those.


zinc15

http://zinc15.docking.org/
"respond to the question: ""are there compounds for these genes that i can go buy?""
a free database of commercially-available compounds for virtual screening.   ZINC contains over 35 million purchasable compounds in ready-to-dock, 3D formats. "

ZINC15 is logged in the 'Data Source Backlog' on Google Drive.


Prototype design for pre-run liquid set up for Python protocols

Related to PD setup, but separate design. Python version not tied to MVP
- MVP: User will have to go into PD and do export, zip it and put it in
    - 1. See if it works
    - 2. Trial with apps eng

Closing this since we have a new liquid setup epic


UpdateDependencies should skip already processed dependencies

If you run UpdateDependencies with multiple Github dependencies, you can get duplication of dependencies via recursion.  For example:
project:
   dependencies:
       - github: 'https://github.com/SalesforceFoundation/Cumulus'
       - github: 'https://github.com/SFDO-Community/OutboundFundsNPSP'

In this case, OutboundFundsNPSP defines a dependency on the Cumulus repo in its cumulusci.yml.  UpdateDependencies should be smart enough to know it's already processed the Cumulus repository when it gets to the second reference to Cumulus from OutboundFundsNPSP and just skip that reference.

This should no longer be an issue since the dependency refactor


fix: temporary to temporarily and url fix

temporary to temporarily

not sure if the gap in swappy. one was deliberate? I had to remove it to get the og:image to render in my tweet preview

p.s. I LOVE THIS APP!

Previously I couldn't get twitter to write swappy.one (not sure why)
But thank you for PR!


hola i need some explanation.

i would love if u can add me in discord and talk here. anyway so with this client i can open differents account at the same time, and with different proxy as client and in game? so for gameforge they can't associate the 2 accs right? could u explain how to do?

When you add an account to the launcher you can set up your proxy settings there. This proxy settings will be used to make the http requests to gameforge servers but once you launch the game it will run on your usual IP. To redirect the traffic of your game to the same proxy server you need to use an external software like Proxifier and make a copy of NostaleClientX.exe and rename it to something else, for example "NostaleClientX_proxy.exe". In Proxifier you add the rules to redirect the network traffic of that client to the desired proxy. Also make sure to add the path of the custom executable when you add the account to the launcher.


Migrate Command: !seen

Implement via a service that watches all messages and updates a database with information. Service can be used in any module (but probably most often in the general module for boop / hug spam control)


Firefox 46: onaddstream is deprecated! Use peerConnection.ontrack instead.

Browsers and versions affected
Description
Steps to reproduce
Expected results
Actual results

Fixed


select stream based on RTSP Extra parameter

Hi, is possible to select the stream based on RTSP extra parameter like ?channel=X?
I have a Dahua indoor unit that automatically generate the URL based on IP/PORT/channel ID configuration, the idea is to referer different streams in go2rtc based on channel ID.
The URL used by the Dahua unit is in the form: rtsp://USER:PASSWORD@IP/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
Actually I was able to show only one stream by configuring a stream called cam/realmonitor in go2rtc:
cam/realmonitor: ffmpeg:camera.giardino_sub#video=h264#width=1280#height=720#audio=copy#hardware

I don't understand you. You probably refer to some Hass entity camera.giardino_sub. How does it set the URL?

Sorry for the confusion, let me try to explain better...
Here is part of my go2rtc configuration:
streams:
  camera.cancello_sub: rtsp://XXX:XXX@<IP_ADDRESS>:554/cam/realmonitor?channel=1\u0026subtype=1
  camera.garage_sub: rtsp://XXX:XXX@<IP_ADDRESS>:554/Preview_01_sub
  camera.giardino_sub: rtsp://XXX:XX@<IP_ADDRESS>:554/Preview_01_sub

  cam/realmonitor: ffmpeg:camera.giardino_sub#video=h264#width=1280#height=720#audio=copy#hardware/

Streams named camera.XX are provided by different cams. I would like to view these streams in a Dahua indoor unit (since this unit support camera visualization) but, unfortunately these streams are not in the correct format for the Dahua indoor unit, so I used ffmpeg to transcode video to correct resolution and here comes the stream cam/realmonitor.
In the Dahua indoor unit I configured a RTSP cam that points to the go2rtc server, since the URL used by the indoor unit is rtsp://USER:PASSWORD@go2rtc server IP/cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif I obtained  the transcoded stream cam/realmonitor provided by go2rtc (this is great 🥇 ).
I would like to visualize also the other cams, but unfortunately I cannot customize the URL provided by the Dahua indoor unit, I can only customize the channel that the unit provide as URL parameter ?channel=X to go2rtc.
So the idea was to obtain different stream in go2rtc based on ?channel=X parameter of the request... something like:
streams:
camera.cancello_sub: rtsp://XXX:XXX@<IP_ADDRESS>:554/cam/realmonitor?channel=1\u0026subtype=1
camera.garage_sub: rtsp://XXX:XXX@<IP_ADDRESS>:554/Preview_01_sub
camera.giardino_sub: rtsp://XXX:XX@<IP_ADDRESS>:554/Preview_01_sub
cam/realmonitor**?channel=1**: ffmpeg:camera.giardino_sub#video=h264#width=1280#height=720#audio=copy#hardware/
cam/realmonitor**?channel=2**: ffmpeg:camera.garage_sub#video=h264#width=1280#height=720#audio=copy#hardware/
cam/realmonitor**?channel=3**: ffmpeg:camera.cancello_sub#video=h264#width=1280#height=720#audio=copy#hardware/
I have already tried something as above without success...
Thank you for your attention and your hard work on this great project.

It's not an easy task. I'll think about it


Documentation On How To Upgrade Antrea CNI

Can someone help me in finding the document that describes the procedure to upgrade Antrea CNI.
I find only documentation regarding its installation.
I think it is only a matter to run kubectl apply -f .... as the installation but I've a doubt if it must be preceded by a deletion with the same yaml file that was used during the cluster's installation.
Thank you.

Hi @gbonazzoli you can check this section https://github.com/antrea-io/antrea/blob/main/docs/versioning.md#antrea-upgrade-and-supported-version-skew to see if this can help you or not. Could you let us know what's the old version and new version for your upgrade? Antrea didn't support "graceful" upgrades if the versions gap are large.
cc @tnqn @antoninbas @jianjuns

I guess we could rename this section from Installation to Installation and Upgrade.
But yes, the steps are the same for installation and upgrade.
For production workloads for which it may be important to minimize disruptions, we would recommend upgrading the Controller first and the Agent last, as described in the documentation. However, we do not provide "split" manifests to do that.

@antoninbas @luolanzone
Thanks a lot, I upgraded Antrea CNI with the following:
govc snapshot.create -vm=vm.kube.master bonaz-snapshot
kubectl apply -f https://github.com/antrea-io/antrea/releases/download/v1.13.2/antrea.yml
govc snapshot.remove -vm=vm.kube.master bonaz-snapshot

Looking at the upgrade process I was lucky. It was first upgraded the controller and then, one by one, the agents on the three node cluster.

Looking at the upgrade process I was lucky. It was first upgraded the controller and then, one by one, the agents on the three node cluster.

I believe the controller and the "first" agent will usually upgrade concurrently. But once again, as far as we know, nothing breaks when some agents upgrade after the controller, which is why we haven't provided separate manifests. When using the Helm chart to install / upgrade, there is no specific order being enforced either.

The version I was coming was 1.13-dev-something and I was only worried by the "dev" string.

That doesn't sound right. Where do you get this version string? This should only happen if you use the current dev version of Antrea and apply https://raw.githubusercontent.com/antrea-io/antrea/main/build/yamls/antrea.yml.


super fast getting started

This is an idea for users who just want to see Weave GitOps in action quickly. We could provide a quick start based on a demo repo so that the user simply needs to run flux bootstrap and voila. A potential downside would be the (continued) use of a non-secure password. But this would offer an alternative to the getting started guide where we gradually introduce each element to explain it, here we could get things up and running, then explain later.
The repo could contain:
readme.md
To quickly see Weave GitOps in action:

Fork this repo
Download the Flux CLI
Run:

flux bootstrap github \
  --owner=<your-username> \
  --repository=weave-gitops-demo \
  --branch=main \
  --personal

This will install Flux and Weave GitOps on to your Kubernetes cluster, as well as a sample application - podinfo - so you can explore Weave GitOps.
To access the dashboard, run:
kubectl port-forward svc/ww-gitops-weave-gitops -n flux-system 9001:9001

and open http://localhost:9001/
The admin user credentials have been set to:
username=admin
password=password
To change this, follow the guidance here and update the value in ww-gitops-helmrelease.yaml
(then add some screenshots of the UI)
ww-gitops-helmrelease.yaml
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: ww-gitops
  namespace: flux-system
spec:
  chart:
    spec:
      chart: weave-gitops
      reconcileStrategy: ChartVersion
      sourceRef:
        kind: HelmRepository
        name: ww-gitops
  interval: 1m0s
  values:
    adminUser:
      create: true
      passwordHash: $2a$10$ns6c.prXZVQb1Ud.RB7/2e5anzMZmjrmn5ETAU893n2gQVM5P3/aG
      username: admin

ww-gitops-helmrepository.yaml
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  name: ww-gitops
  namespace: flux-system
spec:
  interval: 1m0s
  url: https://helm.gitops.weave.works

podinfo-source.yaml
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: GitRepository
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 30m0s
  ref:
    branch: master
  url: https://github.com/stefanprodan/podinfo

podinfo-kustomization.yaml
---
apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
kind: Kustomization
metadata:
  name: podinfo
  namespace: flux-system
spec:
  interval: 5m0s
  path: ./kustomize
  prune: true
  sourceRef:
    kind: GitRepository
    name: podinfo
  targetNamespace: default

I'll leave this open but we have a few avenues now that we are taking to simplify getting started.  I like the approach here and @ozamosi had recommended something similar in the past with a --geting-started flag if/when we add back in gitops install.

closed as wont fix


Revert "Log autovouching flow on sentry."

Reverts mozilla/mozillians#1684

Let's remove the debug statements from the codebase.

Coverage decreased (-0.003%) to 92.212% when pulling 54f77508015c8815eac790e9649851732500ca6d on revert-1684-debug-sentry-autovouch into d426127089ba2b2df5ce499c4b2f6da0f6e2eaf2 on master.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

/close
replaced by #1385


[#5815] Change the http protocol for Google Analytics

Change the http protocol in the access url from http to https for Google Analytics

Codecov Report

Merging #5816 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #5816      +/-   ##
==========================================
+ Coverage   40.68%   40.69%   +0.01%
==========================================
  Files        2935     2935
  Lines       88158    88158
  Branches    11589    11589
==========================================
+ Hits        35870    35880      +10
+ Misses      49192    49185       -7
+ Partials     3096     3093       -3

Impacted Files
Coverage Δ

...p/pinpoint/rpc/stream/StreamChannelRepository.java
75% <0%> (-10%)
:arrow_down:

...cluster/zookeeper/ZookeeperClusterDataManager.java
52.9% <0%> (-1.94%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.4% <0%> (+0.32%)
:arrow_up:

...ollector/cluster/zookeeper/ZookeeperJobWorker.java
82.32% <0%> (+1.39%)
:arrow_up:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
59.57% <0%> (+2.12%)
:arrow_up:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
85.36% <0%> (+2.43%)
:arrow_up:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
83.58% <0%> (+2.98%)
:arrow_up:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
73.33% <0%> (+3.33%)
:arrow_up:

...p/pinpoint/rpc/client/WriteFailFutureListener.java
75% <0%> (+18.75%)
:arrow_up:

Continue to review full report at Codecov.

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


Get approval from spaceduck creator to add theme to vs code marketplace & open vsx registry

Hey, I'm sorry to bother you, but I am interested in this too, is there something I can do, or can you give a status update on this?

Hey @yylian no apologies needed!
I added the theme to the marketplace: https://marketplace.visualstudio.com/items?itemName=spaceduck-vscode.spaceduck
for other things that need to be done, I may be a little slower, e.g. terminal colors. You are welcome to create a PR for those type of things if you are interested.


Typo "Azure SQL database"→"Azure SQL Database"

https://docs.microsoft.com/en-us/azure/azure-sql/migration-guides/database/sql-server-to-sql-database-assessment-rules
#PingMSFTDocs

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


Fix: Unbound namespaced record field error

Closes #201
This is what this PR does:

Add namespaced record field names in the formatted output of the UnboundRecordField errors

Fix existing parsing/regex
Add corresponding test

Fixes the existing failing tests

Looks good to me, @jordwalke @kyldvs any idea on why these tests were failing? My guess is ocaml version inconsistency with our (soon to be deprecated) internal setup introduced in https://github.com/facebookexperimental/reason-native/commit/c7503be91527653488dfa96ad7f67370cbaadd9a ?


added eli.li to sites.js

Seems interesting. Warm welcome to the ring!

@kodedninja haha we must be on a similar schedule. I literally just sat down and was looking through this!

@ckipp01 haha sorry!

Hey! @eli-oat it looks like there is a CORS issue with fetching your feed for the hallway, which is why you aren't seeing your posts. If you're not sure how to fix it, you can see an example in the readme here.
Let us know if you need any help!

Ah! I should have guessed as much.
I’ll probs just migrate my twtxt file from tilde.town to my own domain to resolve this.
Thanks so much for the heads up!

On Jul 25, 2019, at 4:32 PM, Chris<EMAIL_ADDRESS>wrote:
Hey! @eli-oat it looks like there is a CORS issue with fetching your feed for the hallway, which is why you aren't seeing your posts. If you're not sure how to fix it, you can see an example in the readme here.
Let us know if you need any help!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Feature/stage damage histograms

@rtle76 my latest test demonstrates that we are calculating damage with uncertainty correctly, yet 2.0 stage damage functions do not match with 1.4.3 functions. I think this demonstrates that our stage damage functions are correct, and you can hold off spending further time on the muncie stage damage integration test. I think we'll probably need to spend some time working through some examples and documenting in the release notes so that we can advise the field on what to expect.


Add Shared Library Tool

Added a tool to link and produce .dll/.so outputs.
I'm planning on using this in SwiftPM for linking Windows Swift code since Windows Swift currently doesn't support static linking. It currently works for that purpose and produces .dlls and import libs on Windows which I've used to (partially) compile SwiftPM.

Huh, so turns out detecting what compiler you've been given is... somewhat difficult... to say the least. Rather than trying to guess the compiler by its executable name or determining what it is by running it. I've just added a "compiler-style" field when can be specified to be "cl, clang, or swiftc".

@swift-ci please test

@swift-ci please smoke test

rebased and addressed feedback
@swift-ci please smoke test

@jakepetroules Re I believe I've addressed your requested changes.


feat: Automatic retrieval of repo name added

I did some research on automatic retrieval of WEBSITE_URL data. However, I could not find a good result.

@LeoDog896 I think the WEBSITE URL needs to be removed because there is no need for .env.example anymore.

I usually would, but I left it there in case someone needs to change its casing — they can always modify the workflow in their fork! (and the .env.example is mainly there for local development reference)

It makes more sense the way you say. Thanks.


Cursor "pointer" flashes to default style after navigation

Describe the bug
I have noticed that when you hover over an element with cursor: pointer style and perform any type of router navigation, the cursor momentarily switches to cursor: default and then back to cursor: pointer.
For instance, this occurs every time you click a <Link /> component to perform a navigation. But this also happens on any element with cursor: pointer  when you use other mechanism to navigate somewhere. For example, you can hover over a regular button and use your keyboard to focus a link, and by pressing Enter  multiple times you can observe the same behavior.
This can be reproduced using official examples.
Your Example Website or App
https://stackblitz.com/github/tanstack/router/tree/main/examples/react/basic?embed=1&theme=dark
Steps to Reproduce the Bug or Issue

Hover over any link that will perform router navigation.
Observe that the mouse cursor has cursor: pointer style.
Click the link to perform navigation.
Observe that the mouse cursor flashes with cursor: default style.

Expected behavior
As a user, I expect that the mouse cursor styles remains consistent with the element style when hovering over it and performing navigation.
Screenshots or Videos
https://github.com/TanStack/router/assets/34657799/248a5c73-1d52-493a-aaa0-448d0bad33f3
Platform

OS: Linux
Browser: Chrome
Version: 120.0

Additional context
No response

Does not happen in Chrome on macOS:
https://github.com/TanStack/router/assets/6340397/ddaa41b5-6567-4864-aea6-74bb7270d7d9

Yeah, I might've been to hasty with opening an issue for this. It seems like this is common when doing client-side routing in React. I've got the same behavior in other apps that aren't using TanStack router. And also on a Windows machine.
For some reason, the example in the docs was just particularly egregious for me. Will close this for now.


Add bitcode option

Jenkins Linux s390x Build #961 [push] Add bitcode option (#680... started at 17:03

Jenkins Linux ppc64le Build #114 [push] Add bitcode option (#680... started at 17:03

Jenkins Linux amd64 Build #963 [push] Add bitcode option (#680... started at 16:03

Jenkins Linux s390x Build #961 [push] Add bitcode option (#680... passed after 46 min

Jenkins Linux amd64 Build #963 [push] Add bitcode option (#680... passed after 53 min

Jenkins Linux ppc64le Build #114 [push] Add bitcode option (#680... passed after 1 hr 15 min


Generate user-friendly packages

Generate user-friendly packages for main distribution systems :

apt
homebrew
nugget
... ?

Maybe the first step would be to upload it through PyPi : http://peterdowns.com/posts/first-time-with-pypi.html

Done ! https://pypi.python.org/pypi/automergetool/0.2.0


Pr434 tweaks

pep8
docstring tweaks
clearer variable names
return a Figure instead of nothing
move plot_convergence to plotting.py

@pgkirsch, ready for review and merging.

All looks good to me, thanks!