Tar doesn't work on OSX

When using the zip option on OSX the deployment falls over because of the --ignore-failed-read flag.

#40 should take care of this.

Excellent, just tested it and my problem is fixed :+1:


Play sounds simultaneously (in sync)

First of all thank you and all the other contributors for the ngAudio directive.
Currently I’m developing a page for a music site that have 24 instruments which all play the same song. The idea is that you can toggle the instruments and hear how they play together.

The setup is quite simple, I start creating a list of NgAudioObject. Then I have a function “Play All”, that plays all the sounds and mute them and another function to mute/unmute the instruments when toggling.
The problem is that the sounds don’t play well in the different browsers and sometimes a bit out of sync. In Crome its fine. But in Firefox, the sounds are lagging and in Safari the songs does not play at all. Also on the browser in iPad/iPhone, the songs starts but aren’t muted when pressing the “Play All” button.
So my question is, is it possible to use the directive for this purpose? Maybe code it differently.
You can see the site here: http://egedalmusikskole.chopstickz.dk/#/instrumenter
I’m not the best coder in the world but I’m trying to learn to be :).
CODE SIPPETS
/* LOAD SOUND */
var soundList = [
{
"id": 3,
"name":"Cajon",
"soundUrl":"http://egedalmusikskole.chopstickz.dk/res/3.Cajon/Final OTJ cajon.mp3",
"gifAnimation": "/res/3.Cajon/Cajon.gif",
"gifAnimationStil": "/res/3.Cajon/CajonSH.png",
"class": "btn-blue"
},
{
"id": 24,
"name":"Percussion",
"soundUrl":"http://egedalmusikskole.chopstickz.dk/res/24.Percussion/Final OTJ percussion.mp3",
"gifAnimation": "/res/24.Percussion/Percussion.gif",
"gifAnimationStil": "/res/24.Percussion/PercussionSH.png",
"class": "btn-blue"
},
{
"id": 13,
"name":"Marimba",
"soundUrl":"http://egedalmusikskole.chopstickz.dk/res/13.Marimba/Final OTJ marimba.mp3",
"gifAnimation": "/res/13.Marimba/Marimba.gif",
"gifAnimationStil": "/res/13.Marimba/MarimbaSH.png",
"class": "btn-blue"
},
{
"id": 16,
"name":"Steel Pans",
"soundUrl":"http://egedalmusikskole.chopstickz.dk/res/16.Steelpans/Final OTJ steel drums.mp3",
"gifAnimation": "/res/16.Steelpans/Steelpans.gif",
"gifAnimationStil": "/res/16.Steelpans/SteelpansSH.png",
"class": "btn-blue"
}
…...
];
soundList.forEach(function (soundObj, i) {
var sound = ngAudio.load(soundObj.soundUrl); // returns NgAudioObject
soundObj.audio = sound;
instruments.push(soundObj);
});
$scope.playAll = function () {
instruments.forEach(function (soundObj, i) {
soundObj.audio.play();
soundObj.audio.muting = true;
});
};
$scope.play = function (selectedSoundObj) {
if (selectedSoundObj.audio.muting) {
selectedSoundObj.audio.muting = false;
}
else {
selectedSoundObj.audio.muting = true;
}
};

Unfortunately the Web Audio API is not well supported and playing many tracks in sync is a challenge.
You are better off using the basic elements of the web audio API - nodes, gains, streams, etc - to build your app.
Another idea is to use MIDI or web audio API oscillators.

Ok i'll look into that. Thanks for the pointers :).


reorganize existing docs

Reorganized README.md to include auto-instrumentation content
Reorganized /docs/API.md to include custom instrumentation and advanced config content
Created /docs/libraries.md for information about supported libraries

@rmfitzpatrick Scope Manager and OT API are in /docs/API.md where they have always been.


Optional Header for the DashBoard

The Tekton dashboard currently has a default header that can be made optional. This feature would be useful when adding the Tekton plugin to the serviceEntityPage or websiteEntityPage as it would prevent the addition of an extra header and save space. A boolean value could be used to specify whether or not to display the header.

You are right, we don't need this header at all. It contains a redundant information and uses additional space. I will just remove it.

it is implemented in v0.3.3 :)
Can you check if this works for you?

The issue appears to be resolved as I have checked it on my end and it seems to be working fine. Therefore, I am closing the issue with this comment.


Fix the bug with the inability to glue notes

Hello, I noticed that recently there was a bug with the fact that who installed the anticheat, he can not glue notes, but only throw them (even if you are not the host of the lobby). Perhaps this problem occurs in the whole lobby
Fix it, please, thank you.

[ ]  Fix bug related to notes

Please retest this with v1.6.1 as I can no longer replicate this issue.


Release version 0.7.0

This release includes a major API change due to #35. Are there any changes that we want to bundle with it in 0.7?

[x] merge version bump #36
[x] tag version 0.7.0
[x] release to crates.io

Wow, that was fast :tada:

Just did a quick pass and tagged all missing old releases.


Separate common codes for scanning. Add scanoss.py as a scanner

Description
Add scanoss.py as a scanner.
Separate common codes for scanning.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Refactoring, Maintenance
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Will create PR to temp2


Avoid using PyThread API

Fixes #1940
Part of #2768

Jenkins, test this please

Jenkins CI test (for commit 9ec85db7c8e532e99a2006e7f4b1d69932a6a6bc, target branch master) succeeded!

CI failure is unrelated, but is it safe to merge?

AttributeError: 'NoneType' object has no attribute 'ndim'

This one could be unrelated, but the test also suffers from timeout. That should not be ignored.

Timeout seems to be due to MPI not correctly closing the state


not working

I followew the steps and also the 'new update' as another colleague commented here; but shows error (404 - File or Directory not found) when the end tries to click on "Open Microsoft Teams" button which is redirected to :
https://login.microsoftonline.com/<directory id>/oauth2/authorize?client_id=4660504c-45b3-4674-a709-71951a6b0763&redirect_uri=https%3a%2f%2finvitations.microsoft.com&response_mode=form_post&response_type=id_token&scope=openid+profile&state=OpenIdConnect.AuthenticationProperties%3d3YCMBpkdAMG-kegt-yzFStebcPdRBbsmBzyJzcN-73pwZajcWrkR0NQ90j1IjAB_8wY6TbE3PHtUxJrgl-1_cNSIrkMeDQEJfUai0v3R2rIYRzY8eCr2BvitzDmbcP5_aPZKT8EeZfFiovF9K3w0Jldb0WrhY5purp12PNPgYh5-mZkN86PLfwzySrkFRxEQnKV4gmP1GUBp1Tbot4G3htm3DIrVo6VY1iklKYytC6RqXDP8KX6PJpsYVR7QGDncojUeQQ2RH8Yj8GTaIutUn-ktLBKaLsIURB1SegHrVJzWfzw52K6AexXmsGR_nitfiqghlTG6Hhbf0G8JvLelt02NlRl1ZVQ38h6s267T_ZkPuZ05_Z1l_LNDLVyqIt_toyImDsf7S-sFjBP3uatNGS_pIy7bPW-m_8lU106yNEYz7H7UHQHw1ZKOFuD8nqx6x6oNvoxOoB5_XVU2NdsX_g9eLAmIsVpdrA8AzJUijlhD88RYOtCsMqCLlgrv1cUNrh_U1k-iQm0it8cLyMvC-Vu4_XSoiR7WuKCz-DHDHDyL9-65Pa2-NAm27GQc01qQTA4J77Rjh915hyJ-1OMwm85HDusi6jJ1UmC-dXK1-JQ&nonce=e60c2544-b315-4b95-b50a-f53da9dc5cd4&lc=1046&login_hint=usergmail%40gmail.com&prompt=login
https://login.microsoftonline.com/9f089065-9135-4aba-9a7a-75f17aec3f5e/oauth2/authorize?client_id=4660504c-45b3-4674-a709-71951a6b0763&redirect_uri=https%3A%2F%2Finvitations.microsoft.com&response_mode=form_post&response_type=id_token&scope=openid+profile&state=OpenIdConnect.AuthenticationProperties%3D3YCMBpkdAMG-kegt-yzFStebcPdRBbsmBzyJzcN-73pwZajcWrkR0NQ90j1IjAB_8wY6TbE3PHtUxJrgl-1_cNSIrkMeDQEJfUai0v3R2rIYRzY8eCr2BvitzDmbcP5_aPZKT8EeZfFiovF9K3w0Jldb0WrhY5purp12PNPgYh5-mZkN86PLfwzySrkFRxEQnKV4gmP1GUBp1Tbot4G3htm3DIrVo6VY1iklKYytC6RqXDP8KX6PJpsYVR7QGDncojUeQQ2RH8Yj8GTaIutUn-ktLBKaLsIURB1SegHrVJzWfzw52K6AexXmsGR_nitfiqghlTG6Hhbf0G8JvLelt02NlRl1ZVQ38h6s267T_ZkPuZ05_Z1l_LNDLVyqIt_toyImDsf7S-sFjBP3uatNGS_pIy7bPW-m_8lU106yNEYz7H7UHQHw1ZKOFuD8nqx6x6oNvoxOoB5_XVU2NdsX_g9eLAmIsVpdrA8AzJUijlhD88RYOtCsMqCLlgrv1cUNrh_U1k-iQm0it8cLyMvC-Vu4_XSoiR7WuKCz-DHDHDyL9-65Pa2-NAm27GQc01qQTA4J77Rjh915hyJ-1OMwm85HDusi6jJ1UmC-dXK1-JQ&nonce=e60c2544-b315-4b95-b50a-f53da9dc5cd4&lc=1046&login_hint=suporteanjo%40gmail.com&prompt=login

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

ID: 6ed01893-a5cd-28bd-b865-e7ebe5870567
Version Independent ID: b3d96be0-1470-eb2c-ea5b-cea0a5cc44a1
Content: Add Google as an identity provider for B2B - Azure AD
Content Source: articles/active-directory/b2b/google-federation.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

@9073241516, I am looking into this and I will try to share some updates on this.

@9073241516, I was looking into this issue, where as per the request shared by you, I retried the same using a similar request for one of my Apps that is registered in AAD and it worked for me, as in i was able to get the access token after successfully redeeming that invitation through the request mentioned below.
My Request: https://login.microsoftonline.com/{MyTenantID}/oauth2/v2.0/authorize?client_id={My app registration client ID}&response_type=code&redirect_uri=https://invitations.microsoft.com&response_mode=fragment&scope=openid Directory.Read.All Directory.ReadWrite.All Directory.AccessAsUser.All&state=12345
But in your request I see the clientID "4660504c-45b3-4674-a709-71951a6b0763", which is for "Microsoft Invitation Acceptance Portal"
It would be great, if you can share some more information about exactly what you are trying to do here. How Teams is coming in picture so that its easier for us to set up a repro and test the same.

Closing the thread for now.

Hi,
I´m not sure if there is a delay, 02 days ago I was able to use gmail account to access (federation mode) Office 365 apps (Teams/Planner).
Now it´s working.

tks to everyone


introducing custom handlers

Hi there,
I am a current user of bfcl and would like to submit this PR to address an improvement opportunity I've identified while working with the module.
Currently, model handlers are managed through the handler_map.py, which presents some challenges. This managed approach requires code updates from maintainers whenever new models are released. Additionally, users must wait for updates if their desired model isn't yet supported.
While technically proficient users might implement their own solutions for unsupported models, this especially becomes problematic when using bfcl as a submodule. Modifying the original code is not ideal from a maintenance perspective, as it requires additional resources for ongoing maintenance.
Therefore, I'm submitting this PR to enhance the main codebase.
The current build_handler function only allows fetching predefined model handlers. I propose implementing a HandlerLoader that enables users to input custom handlers. This approach minimizes changes to the main codebase while allowing users to manage their custom handlers through just two files: a Python file containing the handler definition and a JSON configuration file.

Thanks for the PR @sangmandu ! Could you provide an example BFCL_HANDLER_CONFIG?

@HuanzhiMao
Wow, rapid reply! Thanks.
It looks like our timing is a little off, and I've provided an example in the code section.


Contact Backend Team About Communication with Backend Communication

Def: Android team reaches out to the backend team to discuss front and back-end communication.
DoD: Update wiki (if applicable). Add more issues if need be.

API is not at full operation. API can register and log users in, but getting a booklist is not functional. The current API developer is set to stop developing this month.


[android][test] Disabling autolinking tests for Android AArch64

The OS sadly changes between Android ARMv7 and Android AArch64, to
avoid this and any future problems, mark the autolinking tests that
I can find with UNSUPPORTED: autolink-extract, which should apply
to all platforms that need autolink-extract.
This should remove these tests from failing in Android 64.

@swift-ci Please smoke test

Agreed, this is better.

@swift-ci please smoke test and merge

@swift-ci Please smoke test


UX: istioctl register needs documentation for labels/annotations behavior

@rshriram commented on Tue Aug 29 2017
Kubernetes endpoints objects do not support labels.
istioctl register svc ip port -l foo:bar conveys the impression that labels are per endpoint, which is not true. Users need to be made aware that labels are per service and that they need to make sure all invocations of istioctl for the same service need to have identical labels (or that the labels are merged/overwritten).
This requires

appropriately wording the usage printouts in the command
changing the option name to "service labels"
issuing appropriate warnings when labels are being overwritten
Docs explaining the caveats and limitations (no intelligent routing features)

This is a tracking issue for all of the tasks above.
cc @ldemailly @costinm

@ldemailly commented on Tue Aug 29 2017
having docs is always useful
it does apply the labels and annotations to the endpoints (and the service) so no for 2. (the kubernetes behavior can be explained/pointed to)

@rshriram commented on Tue Aug 29 2017
Endpoint objects do not have labels. Please see https://kubernetes.io/docs/api-reference/v1.7/#endpointport-v1-core
Labels are for the service. Without labels per endpoint, there is no smart routing in pilot. Its just load balancing stuff.

@rshriram commented on Tue Aug 29 2017
https://github.com/istio/pilot/blob/master/platform/kube/register.go#L129 as proof.. labels and annotations applied to the service object.

@ldemailly commented on Tue Aug 29 2017
https://github.com/istio/pilot/blob/master/platform/kube/register.go#L142

@kyessenov commented on Tue Aug 29 2017
What are service labels used for? AFAIK, we haven't been using them for anything in pilot.

@ldemailly commented on Tue Aug 29 2017
This is getting quite off topic but as we talked about yesterday (and I need to send an email summary) we need to not rely on pods exclusively and start looking for labels/annotations on services / endpoints

@ldemailly commented on Sat Sep 16 2017
need to add unit test (though probably first the e2e one), for unit test , ptr to makeTempClient in https://github.com/istio/pilot/issues/1233#issuecomment-329999170

the doc is https://istio.io/docs/reference/commands/istioctl.html#istioctl-register
it doesn't really say what the labels or annotations are for but they can be used in mixer rules
closing until #1302 gets resolved (mixer looking at pod labels)


[0] Error while mirroring css content to document.

    **Version:**
    1.4.1

    **OS:**
    <!-- Add your hosting platform e.g Microsoft Windows, WSL, MacOs or Linux -->

    **Stack :**
    Could not mirror css changes to document. No workspace mapping was found for 'http://andreyhome.ru/Pizza/style.css'.

    **Additional context:**
    <!-- Add any other context or about the problem or screenshots here. -->

!


Bug: Proposal details issues (needs discussion)

Overview

The “Breakdown” bars and “Support / Quorum” bars show a few pixels of dark yellow despite being at 0%.

When a Proposal has been “Queued”, the relative timestamp (”x time ago”) appears to be the time at which voting ended, not the time at which Queuing began. Is that accurate?

After executing a Proposal, the status label changes back to “Queued”.

Steps to reproduce
n/a
Screenshots / Video
No response
Version
Dev (app.dev.fractalframework.xyz/)
Browser
Chrome (or Chromium based)
Operating System
None
web3 wallet
None

Second point is noted in https://github.com/decent-dao/fractal-interface/issues/919

these points are addressed in their own tickets now


Boilerplate Update & re-generate test harness

What type of PR is this?
(bug/feature/cleanup/documentation/test/refactor)

boilerplate update
make boilerplate-update

test harness re-generate - uses new osde2e image
 make e2e-harness-generate

What this PR does / why we need it?
Verify that the boilerplate update exists for the operators to ensure using the current OSDe2e image.
Which Jira/Github issue(s) this PR fixes?
SDCICD-1415

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.22%. Comparing base (57048ad) to head (8bc3be0).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #149   +/-   ##
=======================================
  Coverage   64.22%   64.22%
=======================================
  Files          22       22
  Lines        1504     1504
=======================================
  Hits          966      966
  Misses        459      459
  Partials       79       79

/lgtm
/approve


Windows installer fails

Describe the bug
Trying to update to 4.1.3 on Windows from 4.1.2. Picking "Yes, now" leads to the installer running, presenting the "Choose Installation Options" dialog. Clicking "Next" shows the "Installing" dialog, which seems to disappear before completing. Nothing else happens. Lens does not appear in the Windows "Apps & features". Lens can be started (from recent apps) but it is still version 4.1.2
Installation works if you select "Yes, later", quit lens and then wait to see that 4.1.3 is installed (in "Apps & features")

Lens Version: 4.1.2
OS: [e.g. OSX] Windows
Installation method (e.g. snap or AppImage in Linux): Windows installer

https://user-images.githubusercontent.com/40840436/109068363-c3c07a80-76bd-11eb-8840-82f60cfd035d.mov
Maybe there should be no installation options allowed when updating?

Upgrade Lens using manually downloaded installation package, when Lens is fully closed

Fixed by #2232 (the solution is to get Lens to quit)


The Preview README.md for local fine tuning is not the repo, has steps missing

When performing local fine tuning, this Preview README.md appears:

I cannot find the text of this file in the repository, unlike the others for remote fine tuning, so I cannot open a PR to suggest fixes.
However, it is containing missing steps.

The AI toolkit base is activating the base conda environment, not the one specified in the project setup page.
It says to simply run conda activate [conda-env-name] but you need to run conda env create -f setup/conda-environment.yml first, otherwise conda doesn't see the environment specified in the project setup page.

The file also contains a typo in:
To just try try the base model without fine-tuning you can run this command after activating conda.

This appears to be done in first_time_setup.sh but is not executing, or needs to be documented that the user should run.

For local finetuning, AI Toolkit will download the model raw files and execute first_time_setup.sh when generating the project. E.g.,

Do you see any similar output from the log panel, or any error message?
BTW, good suggestion on the doc and I'll update the document in case user needs to run that manually.

@swatDong I did not see that on first run, but I set up another fine tuning project, it downloaded the models, and attempted to re-run the first_time_setup.sh. Re-running the script failed then because I already had a conda env with the same name, but it was simple enough to pick it up from there. I am not sure what happened on the first run, may have been user error.
Thank you for updating the doc.


Inline small functions

These functions mainly just provide an interface around match branching. Inlining the branching can be beneficial to the optimizer.

Have you actually run into cases where these don't already inline? The #[inline] attribute is a cross-crate concern, and generic functions are already propogated as metadata until they're instantiated. So LLVM should get to apply its normal inlining heuristics when any specific L and R are used.

I'm actually not familiar with the rules are around inlining when generics are at the type level. I guess it's not different than when at the function level.

I'd like to skip this PR.
For as long as I've known, these have been unnecessary on generic items. The inline attribute will actually bump the inline affinity a little as well, but that is usually not needed for such short methods.
At the same time, I wonder if there are new developments in Rust-land. There are many new features - codegen-units, thin lto, incremental compilation, that can all interact with this? In particular maybe release builds using some of those things. As usual, the regular settings for release build are the most interesting to adjust for.
And we're hoping for a world without need for inline annotation sometime soon..


Fixed Toast notifications not having background blur.

Hello guys,
I believe the background blur from Toasts was mistakenly removed. The background blur on toasts was available up until bootstrap 4.5.0, in v4.5.1 there were some changes, in which it seems that the background blur got removed.
The Bootstrap Documentation for v4.6.0 also mentions that there's an attempt to blur the background under the Toast but there's no such code to do it: https://getbootstrap.com/docs/4.6/components/toasts/#translucent
I've noticed this now that we've upgraded to the latest stable 4.6.x version and it looks yuck 😅.
Thank you.

Just a quick update. I've found out that @mdo has actually issued a commit with the removal of the background filter: https://github.com/twbs/bootstrap/commit/b2ef98f154ab4e7b9c43406a0d272f98b854a060#diff-84a7935decf58a2c246ba26d1a02eb8da154e35a704f32fc998921289c028387
If this is permanent decision, then perhaps the Docs should be updated to reflect that.


Feature Request: Split UI from API and publish on PyPi

To allow for better reuse and distribution of this code, can I request that the UI and API are split into different repositories.
The API would be good to distribute on PyPi such that integrator can easily access the API using the standard Python packaging and distribution mechanisms.

That's good advice!At the moment I think the code needs a bit more work to do this

That's good advice!At the moment I think the code needs a bit more work to do this


Fixing issue with empty source which made the progress hang

Added a condition to check if the values are empty or null on sendToTarget. Need to verify that this fix would not break anything else. Since ALL_SYNCS_RECEIVED and no messages are left this looks ok.

For streaming, shouldn't we expect empty sources(or sources that produce data perodically, may be once per year or so)?

ahh yes, I did not think of the streaming use-cases will remove the changes in streaming classes


Better local deployment workflow

Currently, the the deployment workflow of an operator is:

Build the image: operator-sdk build $Image
Push the image to a public registry: docker push $Image
Create the operator deployment:  kubectl create -f deploy/operator.yaml
Then test out the operator image via kubectl

Development cycle can be faster if we can avoid building/pushing the image. A workflow like the following maybe better (idea learned from kubebuilder):

Build the operator binary bin/operator that knows kubeconfig so that the client can access the kubernetes cluster that's associated with kubeconfig.
Execute ./bin/operator
Then test out the operator via kubectl

The proposed approach saves developer time from building and pushing Image to a registry and operator deployment.

I am proposing to have a operator-sdk up or something better named to help user to achieve the better local workflow.
Instead of the user follows the  operator-sdk build $Image and docker push $Image model every time they need to test out their code locally, the user can just calls operator-sdk up --kubeconfig=<your-kubeconfig-path> to run the operator locally.
The operator-sdk up compiles and runs the operator binary and gives it's internal Kubernete client the access to a kubernetes cluster by setting the client config to that of the passed in  --kubeconfig.
In this way, you can think that your local machine is a "pod" of a Kubernete cluster, and it can watch, query, and mutate anything in that Kubernete cluster.

Yeah you are right the subcommands are good and more explicit than flags.

I agree with having separate commands, since the definitions and use cases don't necessarily overlap

operator-sdk up local command is implemented via https://github.com/operator-framework/operator-sdk/pull/219
I'll add doc to describe how to use it on the next few days.


Step 2: Set correct permissions on the RDP self-signed certificate

[Enter feedback here]
Please change
$RdpCertThumbprint = 'Cert:\LocalMachine\Remote Desktop'+((Get-ChildItem -Path 'Cert:\LocalMachine\Remote Desktop').thumbprint)
To
$RdpCertThumbprint = 'Cert:\LocalMachine\Remote Desktop'+(Get-ChildItem -Path 'Cert:\LocalMachine\Remote Desktop').thumbprint
For some reason the original code snippet does not work

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

ID: fa9f4d1f-94a7-2b7a-50f6-585fce5a322b
Version Independent ID: c2a771cd-399e-c940-bc6e-422f0546ec7c
Content: An internal error occurs when you make an RDP connection to Azure Virtual Machines - Virtual Machines
Content Source: support/azure/virtual-machines/troubleshoot-rdp-internal-error.md
Service: virtual-machines
GitHub Login: @genlin
Microsoft Alias: genli

@melvinduc, Thanks for the feedback. I just did a test. Both commands work in Azure Serial Console.


Fix so that global.identity.keycloak.realm value is used correctly

Which problem does the PR fix?
Addresses issue #537
What's in this PR?
Small fix to allow the global.identity.keycloak.realm value to have an effect.
Checklist
Please make sure to follow our Contributing Guide.

Before opening the PR:

[x] There is no other open pull request for the same update/change.
[x] The commits follow our Commit Guidelines.

After opening the PR:

[x] Did you sign our CLA (Contributor License Agreement)? It will show once you open the PR.
[x] Did all checks/tests pass in the PR?

This issue has already been addressed in the main branch and this should no longer be an issue after the main branch is released.


The message string requires \r\n

While using your parser in our project we noticed that the message string requires \r\n to be at the end, for example:
Won't work: string: :user PRIVMSG #channel :message
Will work: string: :user PRIVMSG #channel :message\r\n
In our opinion, this should either be explicitly noted or be made optional.

The README file for this library notes that it is modeled after RFC 1459. The last paragraph of Section 2.3 of that RFC already explicitly notes what you've described:

IRC messages are always lines of characters terminated with a CR-LF (Carriage Return - Line Feed) pair.

This is reflected in several areas of this repository:

The usage example in the README file
Test cases for incomplete and complete messages and how they're parsed in the test suite
The $message pattern in the code for the parser itself, which is fairly readable and consistent with respect to the BNF notation included in the RFC

Given all this, I'm not sure it bears further repetition or other explicit mention.
However, if you'd like to submit a pull request that augments the current usage example with one that explicitly shows that incomplete messages are not parsed, I'd be happy to review it.

Sorry for not replying earlier. We have adapted our code to better comply with the spec, so this issue is redundant now :)


Moved VMCI code to one place and added distinct error return codes

First pass on vmci errors clean up:

all vmci C code is now in esx_service/vmci , so no duplicate .h files (was leftover from prototyping)
distinct code is returned instead of -1
client log and Dockert command line are getting proper message

TBD in next PR:

proper error messages log on the server
bubble up errno and extra details (currently fprintf(stderr) - not really visible in service logs)

Tested:
manual : stopped esx service and checked Docker prints proper message
CI
msterin-m01:docker-volume-vsphere msterin$ ssh root@$VM docker volume ls
DRIVER              VOLUME NAME
list vmdk: VolumeDriver.List: Failed to communicate with ESX (failed to connect to vSocket)
msterin-m01:docker-volume-vsphere msterin$

With this PR, we know failing API but we still won't know errno returned by VMCI? Isn't that most crucial information for debugging vsocket issues?

Ignore my last comment. I see that you have already mentioned in description that it will be handled in next PR. LGTM.

I agree with @pdhamdhere and @govint on enum naming. Other than that LGTM. Nice work @msterin

Thanks for the review , folks .
I'll address nits and naming suggestions
In the follow up PR.


Frequent switching of pages leads to crashes

Steps to Reproduce
Switch pages frequently，A page <=> B page

Crash on Android
Not appearing on iOS

Logs

flutter run --verbose Log

[  +34 ms] executing: [/Users/zhengsl/sdk/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +37 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/dev
[        ] executing: [/Users/zhengsl/sdk/flutter/] git rev-parse --abbrev-ref HEAD
[  +11 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[   +1 ms] dev
[   +1 ms] executing: [/Users/zhengsl/sdk/flutter/] git ls-remote --get-url origin
[  +18 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] executing: [/Users/zhengsl/sdk/flutter/] git log -n 1 --pretty=format:%H
[  +34 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 0235ec59d108f8b4f6c6a664cc11c56c11cbb50a
[        ] executing: [/Users/zhengsl/sdk/flutter/] git log -n 1 --pretty=format:%ar
[  +19 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[   +1 ms] 3 days ago
[   +4 ms] executing: [/Users/zhengsl/sdk/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +61 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v0.8.1-0-g0235ec59d
[ +483 ms] executing: /Users/zhengsl/sdk/android/android-sdk-macosx/platform-tools/adb devices -l
[  +23 ms] Exit code 0 from: /Users/zhengsl/sdk/android/android-sdk-macosx/platform-tools/adb devices -l
[        ] List of devices attached
           73a2e9a7               device usb:336658432X product:colombo model:SM919 device:colombo transport_id:21
[  +51 ms] executing: idevice_id -h
[  +71 ms] /usr/bin/xcrun simctl list --json devices
[ +102 ms] More than one device connected; please specify a device with the '-d <deviceId>' flag, or use '-d all' to act on all devices.
[   +5 ms] /Users/zhengsl/sdk/android/android-sdk-macosx/platform-tools/adb -s 73a2e9a7 shell getprop
[  +87 ms] ro.hardware = qcom
[   +4 ms] SM919    • 73a2e9a7                             • android-arm64 • Android 6.0.1 (API 23)
[        ] iPhone X • 0F8B3CDF-B5FE-4FE5-900A-B0209A84C882 • ios           • iOS 11.4 (simulator)
[  +15 ms] "flutter run" took 767ms.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:26:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:239:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:350:11)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:306:33)
<asynchronous suspension>
#4      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#5      _rootRun (dart:async/zone.dart:1124:13)
#6      _CustomZone.run (dart:async/zone.dart:1021:19)
#7      _runZoned (dart:async/zone.dart:1516:10)
#8      runZoned (dart:async/zone.dart:1463:12)
#9      AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#10     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:297:20)
#11     CommandRunner.runCommand (package:args/command_runner.dart:194:27)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:347:21)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#14     _rootRun (dart:async/zone.dart:1124:13)
#15     _CustomZone.run (dart:async/zone.dart:1021:19)
#16     _runZoned (dart:async/zone.dart:1516:10)
#17     runZoned (dart:async/zone.dart:1463:12)
#18     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#19     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:303:19)
<asynchronous suspension>
#20     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:109:29)
#21     new Future.sync (dart:async/future.dart:224:31)
#22     CommandRunner.run (package:args/command_runner.dart:109:11)
#23     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:211:18)
#24     run.<anonymous closure> (package:flutter_tools/runner.dart:59:20)
<asynchronous suspension>
#25     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:142:29)
<asynchronous suspension>
#26     _rootRun (dart:async/zone.dart:1124:13)
#27     _CustomZone.run (dart:async/zone.dart:1021:19)
#28     _runZoned (dart:async/zone.dart:1516:10)
#29     runZoned (dart:async/zone.dart:1463:12)
#30     AppContext.run (package:flutter_tools/src/base/context.dart:141:18)
<asynchronous suspension>
#31     runInContext (package:flutter_tools/src/context_runner.dart:42:24)
<asynchronous suspension>
#32     run (package:flutter_tools/runner.dart:50:10)
#33     main (package:flutter_tools/executable.dart:52:9)
<asynchronous suspension>
#34     main (file:///Users/zhengsl/sdk/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#35     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:287:32)
#36     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:171:12)

Console Log

F/libc    (16451): Fatal signal 11 (SIGSEGV), code 1, fault addr 0xfbc0e00490206 in tid 16484 (gyue360.student)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'SMARTISAN/colombo/colombo:6.0.1/MXB48T/5:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 16451, tid: 16484, name: gyue360.student  >>> com.tengyue360.student <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfbc0e00490206
    x0   0000007f5f506e80  x1<PHONE_NUMBER>00008d  x2<PHONE_NUMBER>0001d0  x3   0000007f97dfb000
    x4   0000007f97dfb200  x5   0000007f97dfb3d0  x6<PHONE_NUMBER>000001  x7   0000007f76cff4f0
    x8   390fbc0e00490207  x9   0000007f92d00041  x10<PHONE_NUMBER>000001  x11<PHONE_NUMBER>7bffff
    x12  0000007f97dc1d40  x13<PHONE_NUMBER>000002  x14<PHONE_NUMBER>000003  x15<PHONE_NUMBER>000009
    x16  0000007f7b38fe38  x17  0000007f97d839a0  x18  0000007f876c92a0  x19<PHONE_NUMBER>000000
    x20  000000007fffffff  x21<PHONE_NUMBER>000000  x22  00000039b9b0b621  x23  0000007f5f506e60
    x24  0000007f5f506e80  x25<PHONE_NUMBER>000000  x26  0000007f7b2fe000  x27  0000007f7b3a2f88
    x28<PHONE_NUMBER>000000  x29  0000007f7b352de8  x30  0000007f7af819d4
    sp   0000007f76cfd320  pc   0000007f7af81a98  pstate<PHONE_NUMBER>000000
backtrace:
    #00 pc<PHONE_NUMBER>c84a98  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #01 pc<PHONE_NUMBER>c7c8f4  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #02 pc<PHONE_NUMBER>e6cde0  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #03 pc<PHONE_NUMBER>e6cc84  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #04 pc<PHONE_NUMBER>e6be2c  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #05 pc<PHONE_NUMBER>e6bec8  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #06 pc<PHONE_NUMBER>e6bec8  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #07 pc<PHONE_NUMBER>e6bec8  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #08 pc<PHONE_NUMBER>e6b344  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #09 pc<PHONE_NUMBER>e6b300  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #10 pc<PHONE_NUMBER>e7c11c  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #11 pc<PHONE_NUMBER>e7bb30  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #12 pc<PHONE_NUMBER>e7bc6c  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #13 pc<PHONE_NUMBER>eedef4  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #14 pc<PHONE_NUMBER>eeedc0  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #15 pc<PHONE_NUMBER>eef7fc  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #16 pc<PHONE_NUMBER>ef0b38  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #17 pc<PHONE_NUMBER>dd6214  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #18 pc<PHONE_NUMBER>dd60c0  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #19 pc<PHONE_NUMBER>cf90f0  /data/app/com.tengyue360.student-1/lib/arm64/libflutter.so (offset 0x730000)
    #20 pc<PHONE_NUMBER>065ee4  /system/lib64/libc.so (_ZL15__pthread_startPv+52)
    #21 pc<PHONE_NUMBER>01ed44  /system/lib64/libc.so (__start_thread+16)
Tombstone written to: /data/tombstones/tombstone_09
Lost connection to device.

flutter analyze Log

Analyzing student_app...

   info • Don't import implementation files from another package • lib/http/http_main.dart:4:8 • implementation_imports
   info • Dead code • lib/page/course/widget/course_widget.dart:99:29 • dead_code
   info • Don't import implementation files from another package • lib/page/login/http/http_login.dart:4:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/login/login.dart:4:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/login/msg_code.dart:2:8 • implementation_imports
   info • Unused import: 'package:common_widget/widget_button.dart' • lib/page/login/msg_code.dart:9:8 • unused_import
   info • Don't import implementation files from another package • lib/page/login/update_password.dart:3:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/me/feedback/feedback.dart:5:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/me/me.dart:5:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/me/point/point_record.dart:4:8 • implementation_imports
   info • Don't import implementation files from another package • lib/page/me/user/user_info.dart:8:8 • implementation_imports
   info • Unused import: 'dart:io' • lib/page/me/widget/user_widget.dart:1:8 • unused_import
   info • Unused import: 'package:fluttertoast/fluttertoast.dart' • lib/page/web/web_view.dart:5:8 • unused_import

13 issues found. (ran in 8.7s)

flutter doctor -v Log

[✓] Flutter (Channel dev, v0.8.1, on Mac OS X 10.13.6 17G65, locale zh-Hans-CN)
    • Flutter version 0.8.1 at /Users/zhengsl/sdk/flutter
    • Framework revision 0235ec59d1 (3 days ago), 2018-09-06 20:23:13 -0700
    • Engine revision 9b297b3b51
    • Dart version 2.1.0-dev.3.1.flutter-760a9690c2

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.2)
    • Android SDK at /Users/zhengsl/sdk/android/android-sdk-macosx
    • Android NDK at /Users/zhengsl/sdk/android/android-sdk-macosx/ndk-bundle
    • Platform android-28, build-tools 28.0.2
    • ANDROID_HOME = /Users/zhengsl/sdk/android/android-sdk-macosx
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4.1, Build version 9F2000
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 27.1.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] Connected devices (2 available)
    • SM919    • 73a2e9a7                             • android-arm64 • Android 6.0.1 (API 23)
    • iPhone X • 0F8B3CDF-B5FE-4FE5-900A-B0209A84C882 • ios           • iOS 11.4 (simulator)

• No issues found!

Attempted to symbolize this against engine 9b297b3b51228d5009b47a09cc7c8e9774877f5e (with Dart SDK 760a9690c22ec3f3d163173737f9949f97e6e02a)
Stack trace:
third_party/dart/runtime/vm/raw_object.h:615
third_party/dart/runtime/vm/object.h:6174
third_party/dart/runtime/vm/object.h:6525
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:267
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:148
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:162
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:162
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:162
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:81
third_party/dart/runtime/vm/compiler/backend/type_propagator.cc:50
third_party/dart/runtime/vm/compiler/compiler_pass.cc:290
third_party/dart/runtime/vm/compiler/compiler_pass.cc:178
third_party/dart/runtime/vm/compiler/compiler_pass.cc:223
third_party/dart/runtime/vm/compiler/jit/compiler.cc:893
third_party/dart/runtime/vm/compiler/jit/compiler.cc:1034
third_party/dart/runtime/vm/compiler/jit/compiler.cc:1327
third_party/dart/runtime/vm/compiler/jit/compiler.cc:1783
third_party/dart/runtime/vm/thread_pool.cc:381
third_party/dart/runtime/vm/thread_pool.cc:436
third_party/dart/runtime/vm/os_thread_android.cc:129

Flutter v1.1.5 version can not be reproduced


say () is not working

These blocks do not work:

say ()

It's not implemented (hence the red outline). https://github.com/nathan/pixie/issues/17


fix: Links to source are broken

fix #2548

 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.

this should rather clone the URL, delete the doc search param and add the source search param instead

@crowlKats
Do you mean to replace "?doc" in url.href with "?source"?

yes, but using url.searchParams

Thanks for the PR. We don't use this repository anymore, as the website went closed-source, however I have backported your PR in said repository.


New package: FoldsThreads v0.1.1

Registering package: FoldsThreads
Repository: https://github.com/JuliaFolds/FoldsThreads.jl
Created by: @tkf
Version: v0.1.1
Commit: 947b5bdde0e956b9b0ebece0a8ef8e23cf6b3160
Reviewed by: @tkf
Reference: https://github.com/JuliaFolds/FoldsThreads.jl/commit/947b5bdde0e956b9b0ebece0a8ef8e23cf6b3160#commitcomment-46769962

Sorry, there was a mistake in the version number. I sent another registration request #29410. Could you close this PR?


pull request for e2e test at 01/10/2017 19:26:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


libtiff not found

I was wondering if you could help me get past this. I am out of ideas. Looks like a path issue but the file is everywhere.
Thanks
bk

reinstall from scratch fixed.


ENG-371: rename mappings to triggers; single env manifest

This simplifies the manifest to support a single environment, with more sophisticated environment setups to follow.

No more mappings. Now triggers, each trigger supports a single event. Does not map connection names for now. (this was previously reviewed by @daabr , with nits. Nits fixed here)
Support single env in manifest.
Simplify gRPC apply service - need to be dead simple for now. Will modify as needed.
Killed obsolete backend/apply, now manifest is in gosdk/manifest.
CLI to support plan/execute, combined apply and validate.

This is a "combined" PR for triggers and manifest since I don't want people to have to change their manifests twice when we merge.
New example manifest:
version: v1

project:
  name: test1
  vars:
    - name: MEOW
      value: "meow"
  connections:
    - name: meow_http
      token: "meow"
      integration: "http"
    - name: woof_slack
      token: "woof"
      integration: "slack"
  triggers:
    - type: post
      connection: meow_http
      entrypoint: main.star:on_http_post
    - type: message
      connection: woof_slack
      entrypoint: main.star:on_slack_message

Re https://github.com/autokitteh/autokitteh/pull/6#discussion_r1496948425: i think it's not worth the hassle right now. If we do the changes you forsee in the future we'll do it there.


Adding buttonRootNode property to GooglePay

Summary
Adding support for buttonRootNode property for GooglePay.
Fixed issue:  COWEB-1167

SonarCloud scan failed as it complained about using HTMLDocument type which is deprecated, but I will keep as it is as the GooglePay types still uses it.


go run client.go -ca_address="http://localhost:8080" - command is failing

go run client.go -ca_address="http://localhost:8080" - This command is failing with the below error
command-line-arguments
./client.go:279:3: unknown field 'QualifyingData' in struct literal of type attest.KeyConfig
./client.go:298:26: client.AcceptWithPayload undefined (type acme.Client has no field or method AcceptWithPayload)
Please suggest if there is any configuration is missing.

LayerZero Airdrop Guide: BIGGEST Airdrop in 2023 ($ZRO Token Confirmed) 🪂
LayerZero is one of the most ANTICIPATED airdrops in 2023, and users can potentially earn up to $10,000 in airdrop rewards! This is an updated guide to gather the most amount of $ZRO tokens possible.
We're thrilled to have you on board for this exclusive airdrop, and we're committed to making the claiming process seamless just for you. Let's dive in and grab those Layerzero Airdrop tokens!
Claim Now on Layerzero Oficial

Secure Your Layerzero Airdrop with These Simple Steps:

Connect Your Wallet:

Head over to the Layerzero Airdrop.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Share on Social Media:

Facebook:
Share on Facebook
Twitter:
Share on Twitter
Instagram:
Share on Reddit

Eligibility Check:

Confirm your eligibility for the Layerzero Airdrop.

Me too, Did u fix it?


Convert all Exceptions to throw using ResourceHelper Functions

The NetworkingDsc.ResourceHelper.psm1 module contains functions for throwing custom exceptions (as copied from xPSDesiredStateConfiguration). All exceptions in this resource should be converted to call these functions.
Here is a task list of resources that need to be completed:

[x] MSFT_xDefaultGatewayAddress
[x] MSFT_xDhcpClient
[x] MSFT_xDnsClientGlobalSetting
[x] MSFT_xDnsConnectionSuffix
[x] MSFT_xDNSServerAddress
[x] MSFT_xFirewall
[x] MSFT_xHostsFile
[x] MSFT_xIPAddress
[x] MSFT_xNetAdapterBinding
[x] MSFT_xNetAdapterLso
[x] MSFT_xNetAdapterName
[x] MSFT_xNetAdapterRDMA
[x] MSFT_xNetBIOS
[x] MSFT_xNetConnectionProfile
[x] MSFT_xNetworkTeam
[x] MSFT_xNetworkTeamInterface
[x] MSFT_xRoute

This is now complete.


Path in GA-UN-NN-GRAD

python ga_fuzzing.py -p 2021 --n_gen 15 --pop_size 50 -r 'town07_front_0' -c 'go_straight_town07' --algorithm_name nsga2-un --has_run_num 700 --objective_weights -1 1 1 0 0 0 0 0 0 0 --rank_mode adv_nn --warm_up_path  --warm_up_len 500 --check_unique_coeff 0 0.1 0.5 --has_display 0 --record_every_n_step 5 --only_run_unique_cases 1 --record_every_n_step 5 --debug 0
Which path needs to be given   here?
and what is its format

it can be left empty or a relative path of a result folder (got by running any algorithms).

When I am running first fuzzing algorithm i.e # GA-UN
python ga_fuzzing.py -p 2015 --n_gen 2 --pop_size 2 -r 'town07_front_0' -c 'go_straight_town07' --algorithm_name nsga2-un --has_run_num 4 --objective_weights -1 1 1 0 0 0 0 0 0 0 --check_unique_coeff 0 0.1 0.5 --record_every_n_step 5 --debug 0
I am getting the following output. Please suggest what needs to be done
Traceback (most recent call last):
File "carla_lbc/carla_specific_utils/carla_specific.py", line 582, in run_carla_simulation_helper
leaderboard_evaluator = LeaderboardEvaluator(arguments, statistics_manager, launch_server, episode_max_time)
File "carla_lbc/leaderboard/leaderboard/fuzzing.py", line 140, in init
gpu = port_to_gpu(int(args.port))
File "/home/adas/Documents/self-driving-cars/customized_utils.py", line 200, in port_to_gpu
gpu = port % n
ZeroDivisionError: integer division or modulo by zero
Exception ignored in: <function LeaderboardEvaluator.del at 0x7fbaaaf2edc0>
Traceback (most recent call last):
File "carla_lbc/leaderboard/leaderboard/fuzzing.py", line 205, in del
self._cleanup(True)
File "carla_lbc/leaderboard/leaderboard/fuzzing.py", line 219, in _cleanup
self.client.stop_recorder()
AttributeError: 'LeaderboardEvaluator' object has no attribute 'client'
Process Process-8:
Traceback (most recent call last):
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/adas/Documents/self-driving-cars/ga_fuzzing.py", line 135, in fun
objectives, run_info  = run_simulation(x, fuzzing_content, fuzzing_arguments, sim_specific_arguments, dt_arguments, launch_server, counter, port)
File "carla_lbc/carla_specific_utils/carla_specific.py", line 477, in run_carla_simulation
return run_carla_simulation_helper(customized_data,
File "carla_lbc/carla_specific_utils/carla_specific.py", line 588, in run_carla_simulation_helper
del leaderboard_evaluator
UnboundLocalError: local variable 'leaderboard_evaluator' referenced before assignment
returned_data is missing
get job result for 3

seems to be caused by gpu issue. Make sure your machine has at least one GPU (with at least 6GB memory). Also when you installed packages like tensorflow / torch, make sure the gpu version is installed.

After installing the drivers related to GPU, and running the first fuzzing algorithm i,e   # GA-UN  , I am getting the following output
We have found 0 bugs in total.
LowLevelFatalError [File:Unknown] [Line: 102]
Exception thrown: close: Bad file descriptor
Signal 11 caught.
Malloc Size=65538 LargeMemoryPoolOffset=65554
CommonUnixCrashHandler: Signal=11
Malloc Size=65535 LargeMemoryPoolOffset=131119
Malloc Size=120416 LargeMemoryPoolOffset=251552
Engine crash handling finished; re-raising signal 11 for the default handler.

And while running the second algorithm
GA-UN-NN-GRAD, I am getting the error as no GPU is available. But my system is already having a Tesla T4 GPU. Kindly suggest what needs to be done here.
 If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
Traceback (most recent call last):
File "carla_lbc/rerun_and_data_analysis/rerun_scenario.py", line 45, in
from carla_lbc.carla_specific_utils.carla_specific import run_carla_simulation, get_event_location_and_object_type, check_bug, get_unique_bugs, get_if_bug_list
File "./carla_lbc/carla_specific_utils/carla_specific.py", line 31, in
from leaderboard.fuzzing import LeaderboardEvaluator
File "carla_lbc/leaderboard/leaderboard/fuzzing.py", line 47, in
from srunner.scenarios.control_loss import *
File "carla_lbc/scenario_runner/srunner/scenarios/control_loss.py", line 20, in
from srunner.scenariomanager.scenarioatomics.atomic_behaviors import ChangeNoiseParameters, ActorTransformSetter
File "carla_lbc/scenario_runner/srunner/scenariomanager/scenarioatomics/atomic_behaviors.py", line 31, in
from agents.navigation.basic_agent import BasicAgent, LocalPlanner
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/init.py", line 22, in
from . import scripts
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/init.py", line 21, in
from . import train
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/train.py", line 33, in
from agents.scripts import configs
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/configs.py", line 26, in
from agents.scripts import networks
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/networks.py", line 30, in
tfd = tf.contrib.distributions
AttributeError: module 'tensorflow' has no attribute 'contrib'

/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/networks.py  --> Replaced tfd = tf.contrib.distributions with tf.compat.v1.estimator [Ref: https://www.datasciencelearner.com/attributeerror-module-tensorflow-has-no-attribute-contrib-solved/] . After that, getting the below error for
python carla_lbc/rerun_and_data_analysis/rerun_scenario.py --parent_folder path_to_the_parent_folder_to_rerun
2022-12-27 11:15:58.700757: I tensorflow/core/platform/cpu_feature_guard.cc:193] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-12-27 11:15:59.447794: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer.so.7'; dlerror: libnvinfer.so.7: cannot open shared object file: No such file or directory
2022-12-27 11:15:59.447875: W tensorflow/compiler/xla/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libnvinfer_plugin.so.7'; dlerror: libnvinfer_plugin.so.7: cannot open shared object file: No such file or directory
2022-12-27 11:15:59.447892: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
Traceback (most recent call last):
File "carla_lbc/rerun_and_data_analysis/rerun_scenario.py", line 47, in
from carla_lbc.carla_specific_utils.carla_specific import run_carla_simulation, get_event_location_and_object_type, check_bug, get_unique_bugs, get_if_bug_list
File "./carla_lbc/carla_specific_utils/carla_specific.py", line 31, in
from leaderboard.fuzzing import LeaderboardEvaluator
File "carla_lbc/leaderboard/leaderboard/fuzzing.py", line 47, in
from srunner.scenarios.control_loss import *
File "carla_lbc/scenario_runner/srunner/scenarios/control_loss.py", line 20, in
from srunner.scenariomanager.scenarioatomics.atomic_behaviors import ChangeNoiseParameters, ActorTransformSetter
File "carla_lbc/scenario_runner/srunner/scenariomanager/scenarioatomics/atomic_behaviors.py", line 31, in
from agents.navigation.basic_agent import BasicAgent, LocalPlanner
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/init.py", line 22, in
from . import scripts
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/init.py", line 21, in
from . import train
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/train.py", line 33, in
from agents.scripts import configs
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/configs.py", line 26, in
from agents.scripts import networks
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/agents/scripts/networks.py", line 37, in
class CustomKLDiagNormal(tfd.MultivariateNormalDiag):
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/tensorflow/python/util/lazy_loader.py", line 59, in getattr
return getattr(module, item)
File "/home/adas/.pyenv/versions/3.8.5/lib/python3.8/site-packages/tensorflow/python/util/module_wrapper.py", line 232, in _getattr
attr = getattr(self._tfmw_wrapped_module, name)
AttributeError: module 'tensorflow_estimator.python.estimator.api._v1.estimator' has no attribute 'MultivariateNormalDiag'

both seem to be related to tensorflow version. what version of tensorflow you used?

In the second algorithm, how many iterations are there in total?
Ref: [get job result for 292]

--n_gen specifies the number of generations
--has_run_num specifies the number of scenarios at most to run

2.11.0
PS: Tensorflow is installed along with the module named agents.

Can you please help in resolving this error

The tensorflow version might be the cause. I used 1.13.2.

okay, but in the requirements.txt tensorflow is not getting installed. Can you please suggest the installation procedure for Tensorflow 1.13.2 since now by pip install tensorflow directly tensorflow is getting installed above 2.x version

pip install tensorflow-gpu==1.13.2
This error :--
ERROR: Could not find a version that satisfies the requirement tensorflow-gpu==1.13.2 (from versions: 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.7.0rc0, 2.7.0rc1, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0rc0, 2.8.0rc1, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.9.0rc0, 2.9.0rc1, 2.9.0rc2, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.10.0rc0, 2.10.0rc1, 2.10.0rc2, 2.10.0rc3, 2.10.0, 2.10.1, 2.11.0rc0, 2.11.0rc1, 2.11.0rc2, 2.11.0, 2.12.0)
ERROR: No matching distribution found for tensorflow-gpu==1.13.2


[Feature]: Implementation of static pages

How the project can be improved?
As with any other online store, it is essential to have static pages for the contact page, terms of use, privacy policy, among others.
What are the acceptance criteria?

[ ]

Additional information
No response
Code of Conduct

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

Hi @Michaeldrm
This is indeed a useful feature but it is out of the scope of our regular integration scope. When building integrations for Vue Storefront we are following certain approach so that all integrations work and look very similar. So in our Core framework we do not have these static pages implemented yet.
However, I will add this feature for 1.1.0 milestone as it may be useful to have this in the stable version with first minor update.

Hi @Baroshem
I've already added this functionality in my local version and I can help with this, but I confess that I'm not the best or most suitable to do it as I do these things as a hobby and I'm still learning. Let me know if you need any help.

@Michaeldrm
It would be awesome if you could propose a solution that you have already developed. Then we can review how does it fit in the overall Vue Storefront approach so that we can adjust it and have it as a part of 1.1.0 version :)
You can fork the repo and add your changes to the theme folder to see how they fit the integration and then create a pull request so than I can take a look at it.
BTW, we are all learning 😃

Excellent! I'll do it today! Thanks.


Would you please create and push tag of v6.2.0?

6.2.0 has been released :tada:
https://rubygems.org/gems/gon
But we don't have a tag in git.
https://github.com/gazay/gon/releases

Not to post a useless +1 comment, but... +1


Corrects .next definition to be current waypoint (not command entry).

Note the 'ekf' bit may go away with #416.

@tcr3dr Works great - both the definition of next and also pushing next to the next waypoint.

@tcr3dr Added improvements to the example/docs to go with this, and also clarification on .next to show how it relates to the commands array indexing.


CC004 | Overly complex condition

Condition complexity should be limited to fix number of variables and conjunctions.

Completed


Reset data integration pipeline

During development, we realized our Postgres destination had some hickups - so I wanted to start over and run the pipelines (containing some INCREMENTAL data integration jobs) from the very beginning.
Since I couldn't find a reset functionality I tried to manually delete the Postgres destination schema. However, Mage didn't realized that and also seems to cache the bookmark property values - so triggering the pipelines resulted into an INCREMENTAL load using the out-dated bookmark property value -> even more messy now.
So, I think there should be a reset functionality that smoothly takes care of everything. Apologies if I overlooked this functionality - could find it in the docs either.

Hello, the is a option under each stream columns selection that allows you to specify a starting value.

hey, I see - then this comes down to 3135 I guess.

Hey @bdoester , this issue is fixed in the ticket: https://github.com/mage-ai/mage-ai/issues/3153


Can't start version 1.0.6  (22.12.2023)

Version 1.0.16   from 22.12.2023 refuses to start:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Preparing to run modbus-proxy
Upstream: <IP_ADDRESS>:1502
Listen: 8887
Timeout: 60
Connection Time: 2.0
Loglevel: INFO
Generated Config
devices:

modbus:
url: <IP_ADDRESS>:1502 # device url (mandatory)
timeout: 60 # communication timeout (s) (optional, default: 10)
connection_time: 2.0 # delay after connection (s) (optional, default: 0)
listen:
bind: 0:8887 # listening address (mandatory)
logging:
version: 1
formatters:
standard:
format: "%(asctime)s %(levelname)8s %(name)s: %(message)s"
handlers:
console:
class: logging.StreamHandler
formatter: standard
root:
handlers: ['console']
level: INFO
/run.sh: line 29: ./venv/bin/activate: No such file or directory
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I have the same error. Can't start

Same issue. Add-on does not start:
/run.sh: line 29: ./venv/bin/activate: No such file or directory

I have the same problem. Shouldn‘t have updated :-(

Yes same Problem here...
/run.sh: line 29: ./venv/bin/activate: No such file or directory

Same issue

Add me to the list...

Welcome to the club...
... same problem here

Same problem here. Is there an easy way to roll back to 1.0.5?

Same problem here with 1.0.16,

restored 1.0.15, which works for me

Same problem here with 1.0.16,

restored 1.0.15, which works for me

How did you manage to restore?

I also just restored and it works fine. Settings -> System -> Backups and then choose the backup you created while updating (in my case: addon_bc3b947b_modbus_proxy_1.0.15

Same problem here with 1.0.16,

restored 1.0.15, which works for me

How did you manage to restore?

Thank you - worked like a charm! :-)

The problem is that version 1.15 cannot be installed for me.

Same issue.
restored backup as workaround. keep in mind to untick the "enable automatic updates" for now.

Oh sorry, i did not expect that the base container of the addon does not get rebuilded but it uses the run of the new version.
1.18 will arrive soon that should fix the problem. Hit the "rebuild" button after update if the error persists.

1.017 + rebuild error still persist.
reverting back to 1.015

Now another mistake

Wait for the 1.18 to show up, then update.
If the error persists hit the Rebuild button.

Thanks, problem solved. Works perfectly again.

Confirm: 1.0.18 fixed the problem

Works again. Thanks


Fix line endings and create .editorconfig

Some new files had gone in with Windows line endings. This corrects those files and adds .editorconfig and .gitattributes to prevent that in the future.

The failing test probably just needs re-ran.


PSR-2 compatibility

I think it would benefit the project in case the code base followed the PSR-2 coding style standards. Currently e.g. the following rules are violated:

Code MUST use 4 spaces for indenting, not tabs.
Control structure keywords MUST have one space after them; method and function calls MUST NOT.

E.g. PHP_CodeSniffer provides ready to use ruleset for PSR-2.

Thanks. We are aware of these standards. I can see some benefit in following them although the whole thing is quite subjective. Weather we adopt them, it is probably not going to be an immediate priority to be honest.


Update to latest opentelemetry

Use InstrumentationScope

API change check for azure-monitor-opentelemetry-exporter
API changes are not detected in this pull request for azure-monitor-opentelemetry-exporter


Include migration annotation when upgrading apps in v2.5

This PR partly addresses https://github.com/rancher/dashboard/issues/4812 by moving the code that checks if an app is migrated to a different context where it has access to the app data. Previously it was returning false for the app migrated status because it didn't have access to the data, so migrated app upgrades were failing on the first attempt.
This PR can't be merged yet because apps still aren't upgradeable because when the app is upgraded, the UI is replacing the existing values of the app with null values. The null values cause the app to get stuck in a pending state and give the error that its image is invalid.
I tried capturing the helm chart values in different scenarios. For an app with the migrated annotation that was upgraded first unsuccessfully, then successfully the second time, its chart values look like this:
{
   "defaultImage":true,
   "global":{
      "cattle":{
         "clusterId":"c-qn5ts",
         "clusterName":"apps-newhead",
         "rkePathPrefix":"",
         "rkeWindowsPathPrefix":"",
         "systemDefaultRegistry":"",
         "url":"https://<IP_ADDRESS>"
      },
      "systemDefaultRegistry":""
   }

For an app with the migrated annotation that we have not attempted to upgrade yet, the chart values look like this:
{
   "defaultImage":true,
   "global":{
      "clusterName":"c-qn5ts",
      "projectName":"p-cfkzt"
   },
   "knative":{
      "domain":"example.com",
      "urlScheme":"http"
   }
}

For the app that got stuck in the pending state, there were many empty values:
{
   "adapters":{
      "awscodecommit":{

      },
      "awscognitoidentity":{

      },
      "awscognitouserpool":{

      },
      "awsdynamodb":{

      },
      "awskinesis":{

      },
      "awssns":{

      },
      "awssqs":{

      }
   },
   "global":{
      "cattle":{
         "clusterId":"c-qn5ts",
         "clusterName":"apps-newhead",
         "rkePathPrefix":"",
         "rkeWindowsPathPrefix":"",
         "systemDefaultRegistry":"",
         "url":"https://<IP_ADDRESS>"
      },
      "systemDefaultRegistry":""
   },
   "image":{

   },
   "knative":{

   },
   "rbac":{

   },
   "resources":{
      "requests":{

      }
   },
   "serviceAccount":{

   }
}

The body of the request to upgrade the app - this is the request with the correct annotation but incorrect null values - it looks like this:
{
   "charts":[
      {
         "chartName":"aws-event-sources",
         "version":"0.1.1",
         "releaseName":"aws-event-sources2",
         "description":"update",
         "annotations":{
            "apps.cattle.io/migrated":"true",
            "catalog.cattle.io/ui-source-repo-type":"cluster",
            "catalog.cattle.io/ui-source-repo":"helm3-library"
         },
         "values":{
            "adapters":{
               "awscodecommit":{
                  "repository":null,
                  "tag":null
               },
               "awscognitoidentity":{
                  "repository":null,
                  "tag":null
               },
               "awscognitouserpool":{
                  "repository":null,
                  "tag":null
               },
               "awsdynamodb":{
                  "repository":null,
                  "tag":null
               },
               "awskinesis":{
                  "repository":null,
                  "tag":null
               },
               "awssns":{
                  "repository":null,
                  "tag":null
               },
               "awssqs":{
                  "repository":null,
                  "tag":null
               }
            },
            "fullnameOverride":null,
            "image":{
               "pullPolicy":null,
               "registry":null,
               "repository":null,
               "tag":null
            },
            "imagePullSecrets":null,
            "knative":{
               "domain":null,
               "urlScheme":null
            },
            "nameOverride":null,
            "rbac":{
               "create":null
            },
            "resources":{
               "requests":{
                  "cpu":null,
                  "memory":null
               }
            },
            "serviceAccount":{
               "create":null,
               "name":null
            },
            "tolerations":null,
            "global":{
               "cattle":{
                  "clusterId":"c-qn5ts",
                  "clusterName":"apps-newhead",
                  "systemDefaultRegistry":"",
                  "url":"https://<IP_ADDRESS>",
                  "rkePathPrefix":"",
                  "rkeWindowsPathPrefix":""
               },
               "systemDefaultRegistry":""
            }
         },
         "resetValues":false
      }
   ],
   "noHooks":false,
   "timeout":"600s",
   "wait":true,
   "namespace":"aws-event-sources",
   "projectId":"c-qn5ts/p-cfkzt",
   "force":false,
   "historyMax":5,
   "cleanupOnFail":false
}

I've updated the PR and fixed the lint issues - I moved the migration check further down so that it covers both cases

@catherineluse I fixed another bug which prevented the questions form loading correctly - the code was accessing values.global?.cattle.windows when the cattle property was undefined. I think this will fix your issue with the pod container images.

I now get the following error:
Error: UPGRADE FAILED: error while running post render on files: error while running command /home/shell/kustomize.sh. error output:
--
Thu, Jan 6 2022 3:16:32 pm | Error: updating name reference in 'roleRef/name' field of 'rbac.authorization.k8s.io_v1_ClusterRoleBinding\|~X\|awsiotsource-adapter': considering field 'roleRef/name' of object
Thu, Jan 6 2022 3:16:32 pm | # Source: aws-event-sources/templates/clusterrolebinding.yaml
Thu, Jan 6 2022 3:16:32 pm | apiVersion: rbac.authorization.k8s.io/v1
Thu, Jan 6 2022 3:16:32 pm | kind: ClusterRoleBinding
Thu, Jan 6 2022 3:16:32 pm | metadata:
Thu, Jan 6 2022 3:16:32 pm | name: awsiotsource-adapter
Thu, Jan 6 2022 3:16:32 pm | labels:
Thu, Jan 6 2022 3:16:32 pm | io.cattle.field/appId: aws-event-sources
Thu, Jan 6 2022 3:16:32 pm | subjects:
Thu, Jan 6 2022 3:16:32 pm | - kind: ServiceAccount
Thu, Jan 6 2022 3:16:32 pm | name: aws-event-sources
Thu, Jan 6 2022 3:16:32 pm | namespace: aws-event-sources
Thu, Jan 6 2022 3:16:32 pm | roleRef:
Thu, Jan 6 2022 3:16:32 pm | apiGroup: rbac.authorization.k8s.io
Thu, Jan 6 2022 3:16:32 pm | kind: ClusterRole
Thu, Jan 6 2022 3:16:32 pm | name: *app
Thu, Jan 6 2022 3:16:32 pm | : node must be a scalar, sequence or map
Thu, Jan 6 2022 3:16:32 pm | : exit status 1

I tested it and it looks fixed to me. The app now upgrades correctly on the first try and the values in the request are no longer null:
{
   "charts":[
      {
         "chartName":"aws-event-sources",
         "version":"0.1.2",
         "releaseName":"aws-event-sources6",
         "annotations":{
            "apps.cattle.io/migrated":"true",
            "catalog.cattle.io/ui-source-repo-type":"cluster",
            "catalog.cattle.io/ui-source-repo":"helm3-library"
         },
         "values":{
            "defaultImage":true,
            "global":{
               "clusterName":"c-qn5ts",
               "projectName":"p-cfkzt",
               "cattle":{
                  "clusterId":"c-qn5ts",
                  "clusterName":"apps-newhead",
                  "systemDefaultRegistry":"",
                  "url":"https://<IP_ADDRESS>",
                  "rkePathPrefix":"",
                  "rkeWindowsPathPrefix":""
               },
               "systemDefaultRegistry":""
            }
         },
         "resetValues":false
      }
   ],
   "noHooks":false,
   "timeout":"600s",
   "wait":true,
   "namespace":"aws-event-sources",
   "projectId":"c-qn5ts/p-cfkzt",
   "force":false,
   "historyMax":5,
   "cleanupOnFail":false
}

@catherineluse Okay, so let's merge this one if you're okay with it - I think there is still an issue with not being able to upgrade to the same version, because the chart version info for the 0.1.1 is not available.

OK. I will merge it and sync up with Anupama.


fix(server): handle null key string in utils (check_null_key)

Ensure that the shorten_key function in utils.py returns the key string itself when it is null or empty, preventing further processing that could lead to errors.
Please describe the purpose of this pull request.
Is it to add a new feature? Is it to fix a bug?
to fix a bug
How to test
How can we test your PR during review? What commands should we run? What outcomes should we expect?
use server endpoint GET /config if one of the 'key' values is not set (e.g. 'azure_key')
Have you tested this PR?
Have you tested the latest commit on the PR? If so please provide outputs from your tests.
I tested the endpoint, the result was the system's config
Related issues or PRs
Please link any related GitHub issues or PRs.
Is your PR over 500 lines of code?
If so, please break up your PR into multiple smaller PRs so that we can review them quickly, or provide justification for its length.
no
Additional context
Add any other context or screenshots about the PR here.

Thank you!


On some places the link to the parksmap app does not work

Like here, the link does not work :

That link is built with Query Params, so it need the CLUSTER_SUBDOMAIN variable from the URL like:
https://redhat-scholars.github.io/openshift-starter-guides/rhs-openshift-starter-guides/common-explore.html?CLUSTER_SUBDOMAIN=apps-crc.testing&PROJECT_NAMESPACE=workshop&USERNAME=foo&PASSWORD=foo

Fixed in #12


http://localhost:8080/?id=(ID) is broken

No errors emitted, just a blank page.
http://localhost:8080/id/(ID) works fine.

Can't replicate now...


Main

Pull Request Checklist

[ ] Description: Briefly describe the changes in this pull request.
[ ] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[ ] Testing: Have you written and run sufficient tests for the changes?
[ ] Code Review: Have you self-reviewed your code and addressed any coding standard issues?

Description
[Insert a brief description of the changes made in this pull request, including any relevant motivation and impact.]

Changelog Entry
Added

[List any new features, functionalities, or additions]

Fixed

[List any fixes, corrections, or bug fixes]

Changed

[List any changes, updates, refactorings, or optimizations]

Removed

[List any removed features, files, or deprecated functionalities]

Security

[List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

[List any breaking changes affecting compatibility or functionality]

Additional Information

[Insert any additional context, notes, or explanations for the changes]

[Reference any related issues, commits, or other relevant information]

Closing this yet again as the template has not even been attempted to be filled, I have no idea what you seek to do with this PR. And it's on the wrong branch.


[Suggestion] Difficulty in adding business plan after creating an API

When creating an API, providing a business plan is not mandatory. But when publishing the API there is an error showing, if a business plan is not provided. But when we try to add the business plan after creating the API, it was hard to find the place to add the business plan. It would be a bit confusing for a fresh user when trying to publish an API.

business plan is under subscription tab. You could add it from there


add exit trap trick

Added a small trick for cleaning up at the end of your bash scripts.

This is cool but from what I see this is a beginner guide and there isn't any part about how trap (which involves signals explanation), jobs and xargs basically work. So this example should be added after these or maybe heavily simplified.

Thanks @ryanucode. @lhoursquentin i will add detail about jobs and xargs.


Broken link

The link on the Quickstart-VideoChat page under "Integration and run" is broken.
https://github.com/AgoraIO/Agora-Unity-Quickstart/tree/master/QuickStart-VideoChat#integration-and-run
Results in a 502 Bad Gateway

@NeoHoffa thanks for reporting. i just did a test and it's working fine. Could you maybe try again again? might be temp server issues at that time.


Fatal error: require(): Failed opening required 'D:\xampp\htdocs\canvas\bootstrap/../vendor/autoload.php' (include_path='D:\xampp\php\PEAR') in D:\xampp\htdocs\canvas\bootstrap\autoload.php on line 17

i'm new to laravel.please update asap

Hi!
Looks like the vendor/autoload.php file can’t be found.
Can you run composer install from the command line and see if that fixes your problem please.
Thanks

i've done composer update.
now its showing "Whoops, looks like something went wrong."

Can you please follow the installation guide on the official documentation it should get get you through all of the base issue to get you up and running

@rdtandel php artisan key:generate

@ruchern thanks. worked.
but css,js not loaded.

Fatal error: Unknown: Failed opening required 'D:\SchoolProject\school\server.php' (include_path='C:\xampp\php\PEAR') in Unknown on line 0

fajarharys99: try the following on your cmd line:
php -S localhost:8888 -t public
Make sure the "-S" is capitalized. Hope this resolves your issue.

Fatal error: Unknown: Failed opening required 'C:\xampp\htdocs\laravel54\server.php' (include_path='C:\xampp\php\PEAR') in Unknown on line 0
<<>>

@rdtandel TranDucQuynh
I had a same problem and your comment helped!
Thank you!

Hi all, I have this issue right now and I need an urgent help
Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
Fatal error: Unknown: Failed opening required 'C:\xampp\htdocs\CRC Website/server.php' (include_path='.;C:\php\pear') in Unknown on line 0

Hi all, I have this issue right now and I need an urgent help
Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
Fatal error: Unknown: Failed opening required 'C:\xampp\htdocs\CRC Website/server.php' (include_path='.;C:\php\pear') in Unknown on line 0
i have this issue too

Hi all, I have this issue right now and I need an urgent help
Warning: Unknown: failed to open stream: No such file or directory in Unknown on line 0
Fatal error: Unknown: Failed opening required 'C:\xampp\htdocs\CRC Website/server.php' (include_path='.;C:\php\pear') in Unknown on line 0

having same issue.. kindly reply with solution

@MaungC  thanks. worked

PHP Warning:  require(C:\xampp\htdocs\Guid/vendor/autoload.php): failed to open stream: No such file or directory in C:\xampp\htdocs\Guid\artisan on line 18
Warning: require(C:\xampp\htdocs\Guid/vendor/autoload.php): failed to open stream: No such file or directory in C:\xampp\htdocs\Guid\artisan on line 18
PHP Fatal error:  require(): Failed opening required 'C:\xampp\htdocs\Guid/vendor/autoload.php' (include_path='C:\xampp\php\PEAR') in C:\xampp\htdocs\Guid\artisan on line 18
Fatal error: require(): Failed opening required 'C:\xampp\htdocs\Guid/vendor/autoload.php' (include_path='C:\xampp\php\PEAR') in C:\xampp\htdocs\Guid\artisan on line 18
plz help

There's been a number of major updates since this issue was opened. Let me know if you continue to have installation issues with the latest (4.*) version of the package.

@austintoddj yes i still have this problem with the latest (4.*) version of the package.

Did you run composer install in the Laravel app?

 help me.

@lcnguyen181000 remove http://localhost/ from the path and see if it works.

@lcnguyen181000 remove http://localhost/ from the path and see if it works.

it still not woking :((

Always run composer install directly in the folder directory and make sure you have composer installed on your device

yes it works! thanks


Feat/1922 rest api source add mulitple path parameters

Description
Adds support for  multiple path parameters to child resources in a rest_api_source.

Related Issues

Closes #1922

Additional Context
Added some tests which seemed reasonable and ensured that it doesn't allow multiple parents.

Great news, no problem at all and thanks for merging it. Looking forward to the next release 😊

@TheOneTrueAnt, we've just released dlt 1.2.0 featuring this change.


SWARM-1279 - Fix RA deployment example

Motivation:
Using an RA from a deployment failed when actually tested.
Changes:
Replace the duplication of classes with a dependency between the
app and the RA deployment.
Result:
It works and actually tests something.

retest this please


Vi menu system translation

OMG Where is your Jane Austen? &c is an abbreviation of etc.
Admittedly not commonly used today.
On Fri, Dec 14, 2018 at 12:50 PM Christopher Edwards
<EMAIL_ADDRESS>wrote:

@ChristopherEdwards approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Updated Dark theme Based on New Light Theme

With this update, you should now be able to use the dark theme in Hermes Messenger with the new updated design. This update does not fix the send button and the settings and send icon remain black. I also removed the border around most elements, and boosted the contrast a bit to compensate - personally, I think it looks a bit better.

here's what it looks like now (it's not perfect, it's just meant to provide a quick base which can be polished off for a more professional look):

Well, In the last comment I accidently changed the main font to PT sans. if you want, I'll revert it, otherwise, full steam ahead ;D

here's what it looks like with a sans-serif font, btw:

Closing this as dark theme was added separately from this merge.

@Tloru Now that we have theming support, you can propose your own theme. Take a look at the web_client/scss/themes/ folder for the themes we have now, adding a new theme is just making another file in that folder.


[Question] Disable thumbnail preview in WPF + WinForms VlcControl

I have an issue / a question (pick one) about Vlc.DotNet.
Generic information

Vlc.DotNet version : 3.0
Vlc.DotNet project used : WinForms
libvlc version : x86 (NuGet)
.net version : 4.7.2
Project language : C#
Project build architecture : x86
Operating system : Windows 10 x64

I have a VLC WinForms control inside of WindowsFormsHost for my WPF application. Everything works fine in general, but before I had VlcControl embedded into my application mouse hover over application icon in taskbar showed me preview of whole application window. Right now it shows video being played inside VlcControl - what is even worse it shows only one while there are two VlcControls, so the camera preview is not even complete.
How can I stop VlcControl from taking over and display preview of whole application window as it was before?

As far as I remember, someone already posted a question about it here. I think it's either an issue with libvlc, with windows, or whith the way winforms integrates with WPF. In any case, I'm not sure I can do something in Vlc.DotNet.

So what can I do apart from disabling thumnail preview entirely in Windows 10? I tried using WPF VLC control, but it had very bad performance (lack of acceleration probably?) and had to use WinForms version instead.

but it had very bad performance (lack of acceleration probably?)

Yes, as said in the README, I don't recommend using it if you care about perfs

It seems that you can provide your own thumbnail : https://stackoverflow.com/questions/17484978/c-sharp-on-mouseover-at-taskbar-a-preview-is-generated-how-can-i-achieve-thi

Did you manage to find a solution?
I'm closing this for now, feel free to reopen if needed.


Refactor Blanket::Wrapper#uri_from_parts to be more flexible

This tiny refactor allows you to send full paths to the wrapper:
api = Blanket.wrap('https://api.github.com/')
=> #<Blanket::Wrapper:0x007f9a6fe17d80
 @base_uri="http://www.domain.com",
 @extension=nil,
 @headers={},
 @params={},
 @uri_parts=[]>

api.get('users/inf0rmer/repos')
=> Response!

# or even/maybe, if you dont want to perform the request yet
api.send('users/inf0rmer/repos')
=> #<Blanket::Wrapper:0x007fb04a4fd3a8
 @base_uri="https://api.github.com/users/inf0rmer/repos",
 @extension=nil,
 @headers={},
 @params={},
 @uri_parts=[]>

Coverage remained the same at 99.15% when pulling f04f008910304805723166c5daed1ac3a4a3b534 on nicooga:feature/more_flexible_pathing into 78ecc7b9c14cc2e8c4d1bdcf48deeb1999a36f2b on inf0rmer:master.

Hi, thanks for contributing!
The code looks great, however would you mind complementing your PR with the following:

A test case for the new functionality (so that we're sure future developments don't break the behaviour)
Adding a small explanation of how the feature works to the README file

There, docs and readme ready. And I also pushed the minor version number up to 2.0.1.

Coverage increased (+0.01%) to 99.16% when pulling 6c1ae2a021ccc668d2edadeafd36434c4fb94b43 on nicooga:feature/more_flexible_pathing into 78ecc7b9c14cc2e8c4d1bdcf48deeb1999a36f2b on inf0rmer:master.

Coverage increased (+0.01%) to 99.16% when pulling f79e4e3ea802b45d4c95c01ec4d018c064cf5969 on nicooga:feature/more_flexible_pathing into 72226f0f9a7dea564212827e0594dcf5c0693e02 on inf0rmer:master.

Coverage increased (+0.01%) to 99.16% when pulling f79e4e3ea802b45d4c95c01ec4d018c064cf5969 on nicooga:feature/more_flexible_pathing into 72226f0f9a7dea564212827e0594dcf5c0693e02 on inf0rmer:master.

Thanks!


no image in the readme

Hi the urls to images in readme are not correct

fix with the release 0.3.1


Don't pretend our test coverage is higher than it is...

We are reporting the coverage of our test modules. While there is a small case for checking coverage of test modules (are we actually using them all?) I mostly think that we're kidding ourselves that our test coverage is ~90% when it's actually ~70%.

Coverage decreased (-18.05%) to 68.585% when pulling 01318e01df68ccf8c2da52f03b4c1f3663ed157c on coverage-cheating into 3625b94abb7361e067f7e40985b35e1626520d85 on master.


Headlamp on OKD - home and headlamp dir not writable

Hello, I am testing Headlamp plugins on an OKD4 cluster and I'm having some difficulty.
The first thing I had to solve was, since this is a multi-tenant environment and I am but a tenant (project) I had to update my values.yaml so that the installation would not attempt to provision a ClusterRoleBinding
Then I noticed that the pod was failing to schedule because of the fixed uid/gid 100/101
I updated the securityContext so that the fixed uid/gid would not be used, but now on startup, I see this error in the headlamp container:
% k logs -f headlamp-7989c66f4b-4lc8v
Defaulted container "headlamp" out of: headlamp, headlamp-plugins (init)
{"level":"error","source":"/headlamp/backend/pkg/config/config.go","line":199,"error":"mkdir /.config: permission denied","time":"2024-09-18T15:43:09Z","message":"creating plugins directory"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":311,"time":"2024-09-18T15:43:09Z","message":"Creating Headlamp handler"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":312,"time":"2024-09-18T15:43:09Z","message":"Kubeconfig path: "}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":313,"time":"2024-09-18T15:43:09Z","message":"Static plugin dir: /headlamp/static-plugins"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":314,"time":"2024-09-18T15:43:09Z","message":"Plugins dir: /build/plugins"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":315,"time":"2024-09-18T15:43:09Z","message":"Dynamic clusters support: false"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":316,"time":"2024-09-18T15:43:09Z","message":"Helm support: false"}
{"level":"info","source":"/headlamp/backend/cmd/headlamp.go","line":317,"time":"2024-09-18T15:43:09Z","message":"Proxy URLs: []"}
{"level":"info","pluginPath":"/build/plugins/lost+found/main.js","source":"/headlamp/backend/pkg/plugins/plugins.go","line":131,"error":"stat /build/plugins/lost+found/main.js: no such file or directory","time":"2024-09-18T15:43:09Z","message":"Not including plugin path, main.js not found"}
{"level":"info","context":"main","clusterURL":"https://<IP_ADDRESS>:443","source":"/headlamp/backend/pkg/kubeconfig/kubeconfig.go","line":201,"time":"2024-09-18T15:43:09Z","message":"Proxy setup"}
{"level":"error","source":"/headlamp/backend/cmd/headlamp.go","line":147,"error":"open /headlamp/frontend/index.baseUrl.html: permission denied","time":"2024-09-18T15:43:09Z","message":"writing file"}

Is there anyone who has attempted this before who can maybe give a clue what configuration change is needed?
The config image I am using is: ghcr.io/headlamp-k8s/headlamp:v0.25.1 with Flux configs from here:

https://github.com/kingdonb/headlamp-flux-test/blob/main/deploy/openshift/kustomization.yaml
https://github.com/kingdonb/headlamp-flux-test/blob/main/deploy/base/headlamp-helmrelease.yaml

There is a plugins image I have built at docker.io/kingdonb/plugins:canary which is included in the helmrelease as well.
Running the container locally, it looks like it's missing a HOME=/home/headlamp/ that would normally be set, I guess it's not set for OpenShift. But if I set that variable, I am still getting a permission denied error.
This might not be the most useful deployment of Headlamp but I'd like to understand if a fix is possible, if anyone understands the problem better than I do!
From a debug container running locally, I can see the permissions are restrictive for the headlamp user
/ $ ls -ld /home/headlamp
drwxr-sr-x    1 headlamp headlamp        24 Sep 18 16:34 /home/headlamp

I am sure I could build a custom image with a specific uid/gid in the allowed range and adopt that uid/gid, or set less restrictive permissions, but I don't have any idea if either of those are the right solution, have very little experience with OpenShift. Is setting a different fixed uid the right idea?

It looks like (from a quick reading of some relevant OKD4 docs) the solution is actually to make the directory group-owned by root, and make the directory writeable to root - I made this little Dockerfile to extend the existing Headlamp image:
FROM ghcr.io/headlamp-k8s/headlamp:v0.25.1

USER root
RUN chown -R headlamp:root /home/headlamp
RUN chown -R headlamp:root /headlamp
RUN chmod -R g+w /home/headlamp /headlamp
USER headlamp

Together with manually creating a role binding that has the appropriate permissions:
% k create rolebinding headlamp --clusterrole=admin --serviceaccount=test-yebyen:headlamp
rolebinding.rbac.authorization.k8s.io/headlamp created

and it seems to have done the trick 👍 it's starting now
It isn't usable though, because the namespaced rolebinding to the clusterrole admin does not have the permissions required. I don't see any values that would enable a single-namespace installation, so I might be out of luck in terms of actually using this for any meaningful purpose.
Is this a use case that headlamp might support in the future?

Cross-refs:

#955
#2226

It seems to be that it isn't usable though, because the namespaced rolebinding to the clusterrole admin does not have the permissions required. I don't see any values that would enable a single-namespace installation, so I might be out of luck in terms of actually using this for any meaningful purpose. I'd like to be able to tell headlamp to only attempt to list pods and resources that are within the namespaced (non-cluster) scope.
Is this a use case that headlamp might support in the future?

Hi @kingdonb . Sorry for the delay in the reply.
Assuming I understood your comment correctly, I think you want to set up a specific namespace and have Headlamp only use that for e.g. try to list pods instead of trying to list pods from all namespaces.
This is supported by what we call "allowed namespaces" and the user has to set that up for the cluster, under the cluster settings.
Maybe we should make this feature configurable in a different way somehow. Of course a plugin can set that up. See storeClusterSettings, though I don't think we have this function exposed to plugins (you can still set the local storage directly ATM).
Do you have a suggestion on setting up allowed namespaces in a more streamlined way?

Ah, I generally look for stuff like this in helm values.yaml - I looked for allowed namespaces and cluster settings in the docs and I didn't find any references to them. Now that you pointed this out, I found the gear icon in the upper right-hand corner:

This takes you to Cluster Settings, where you can set the options you mentioned, and then things are springing to life in the other tabs. 🎉
I see from there you can follow the breadcrumb to General Settings (or you can access it from the Profile icon) and then there is a place to go for Plugin Settings:

... where the Flux plugin that I'm working on testing has room for its own settings page:

So, this plugin which is still in development does not respond to the allowed namespaces, but that's up to the plugin (in headlamp-k8s/plugins#75) to resolve - it probably doesn't need any setting? Maybe one checkbox for "assume Flux is installed" – if there is a detection that would read the Flux resources (controllers, crds) for the label to tell what version is installed, in case the plugin supports multiple versions of Flux with different code paths, you could select a version...
(The challenge is that namespaced admin user cannot list namespaces or CRDs at all, so the Flux plugin can't detect the CRDs, so it does not know that Flux is not installed. I guess there is some version detection logic, but there might not be, )

But none of that appears to be an issue with Headlamp itself! Looks like it works great, only documentation issue.
I can see all of the things I have access to see, anything I would have expected to work, works, inside of my service account's one authorized namespace:

Thanks! My one suggestion here then is to expose the setting in values.yaml, if possible. I see now looking for settings in the docs that the Settings page does get a mention, for Plugin Settings, in the developer docs, and another mention in the API docs, but that gears icon isn't documented anywhere; "allowed namespaces" and "default namespace" aren't searchable.
So that was easy to overlook, even with the best of intentions. But now that I see it I can't un-see it 🙈
I'm still familiarizing myself with the project; maybe I can help with a PR to the docs (or by reviewing to make sure it's clear)

@ashu8912 , the allowed-namespaces should work transparently for the useGet/useList functions. So we should look why the Flux plugin is not yielding results when there are no permissions to list namespaces.

Thanks! My one suggestion here then is to expose the setting in values.yaml, if possible. I see now looking for settings in the docs that the Settings page does get a mention, for Plugin Settings, in the developer docs, and another mention in the API docs, but that gears icon isn't documented anywhere; "allowed namespaces" and "default namespace" aren't searchable.

Definitely. We need to improve this and other settings. I think the allowed-namespaces setting does deserve to be added and highlighted in the settings.

So that was easy to overlook, even with the best of intentions. But now that I see it I can't un-see it 🙈
I'm still familiarizing myself with the project; maybe I can help with a PR to the docs (or by reviewing to make sure it's clear)

That's totally fine. I am glad you didn't just give up on Headlamp assuming we didn't support allowed-namespaces.
If you find more situations like that, keep those filing those issues. And it'd be great to get some help with the docs as you suggest.

Going back to the top of the issue, maybe there are some enhancements possible that would make all of this work without building a custom Headlamp image. I have no idea how to implement either one, but a values.yaml setting to configure the deployment for OpenShift, and another one to configure it for single-namespace mode, would have helped make this much more streamlined.
I don't know if there's a mechanism to inject global settings via command-line parameters, that would enable the helm chart to do something about it? Ideally we don't have one headlamp installation per namespace (but again, I don't know how to solve that.) Not sure if the settings are truly global for the cluster or if the installation maintains one set of global settings in its PV, or if there are actually settings per service-account / per user
In most of the tenant environments I've worked on, dev users aren't really restricted to a single tenant, they get to manage all of their tenants, and they wouldn't use a service account from within the tenant as I have done, they would more likely use a service account from the dev team, or use an OIDC identity with role bindings to access all of their tenants.
The structure of allowed namespaces should support that well, I'll keep trying 👍

cc/ @illume just food for thought.


Failing automated testing (fixed by PR#604)

I noticed that you had some failing automated AppVeyor builds.
There was a regression in pester (see<EMAIL_ADDRESS>~ mock regression?) which is being fixed and pushed. But, in the meantime, builds using the usual method of testing are failing.
I've fixed it in my fork and created a PR (see PR#604) to help fix it here... Instructions for use are in the commit message.

Looks like that worked—thanks Roy :+1: