Add lakeFS connection type

Using a custom connection allows setting the fields name and better overall usability of the provider.
https://github.com/astronomer/airflow-provider-sample#adding-custom-connection-forms
https://airflow.apache.org/docs/apache-airflow/stable/howto/connection.html#custom-connection-types

Adding more information.
Today the airflow-lakefs-provider relies on an airflow connection of type HTTP, as described in the docs. HTTP connections allow adding extra information through the conn-extra param and we use that to pass the access_key_id and secret_access_key. This works for us, but it's not as convenient as having a dedicated lakeFS connection type (by adding custom connections, as described here). The custom lakeFS connection type will enable the users to fill a simple tailor-made list of params to lakeFS instead of passing a json string to be parsed by the operator.

I thought so too at first, their manual says
To connect a form to Airflow, add the hook class name and connection type of a discoverable hook to "connection-types" in the get_provider_info method as mentioned in Defining an entrypoint

So I think that once the jar is loaded and the custom connection is configured properly, the new connection type should be available for usage.

Got it .
So while creating and building the hook do I need to change the operator endpoint as well. As my airflow is on localhost. Just Confirming?

Hey @vaibhavk1992 , not sure I understand. The above example is for the SampleProvider, right? I don't see a similar get_link function in the lakeFS provider.

Yes the above was for sample provider.
Within lakeFS it is defined in the below file under         "extra-links": ["lakefs_provider.operators.create_branch_operator.ExtraLink"],.
I feel ExtraLink connect to it's local airflow. But not sure because I haven't see ExtraLink in the whole repo.
https://github.com/treeverse/airflow-provider-lakeFS/blob/main/lakefs_provider/__init__.py

We can start with the connection form and add custom links later.
To test the custom connection type locally you can fill the endpoint url for lakeFS to point to the local lakeFS instance, not the local airflow.

Thanks, @vaibhavk1992 , for doing this in #49!


micro command not found while GOPATH env is in $PATH

I have used go-micro installation instructions. It has been successfully installed. Now I dont have access to micro command in bash:
$ micro cli

Command 'micro' not found, but can be installed with:

sudo snap install micro

Now when I echo $GOPATH:
echo $GOPATH
/home/myuser/go

When I echo $PATH the below paths are present:
/home/myuser/go:/home/myuser/go/bin

Shouldn't I have access to micro command now? Why it is not recognized?

Can you tell us the following:

what version of go you are using.
do you have go modules turned on when getting the repo (this should be irrelevant to your question, but I'm asking it anyways)

Can you check if micro cli is in $GOPATH/bin/micro:
ls -l $GOPATH/bin/micro

Sorry if question is not in the right place!
go version: go1.12.7 linux/amd64
How should I check for go modules state (new to the language)
Unfortunately it is not present in the bin folder:
ls -l $GOPATH/bin/micro
ls: cannot access '/home/myuser/go/bin/micro': No such file or directory

All, right, something might be "broken" in your work environment.
Can you try doing something like this:
export GO111MODULE=on
go get -u github.com/micro/micro

Alternatively, for more verbose output:
export GO111MODULE=on
go get -x -u github.com/micro/micro

If that does not work pop by in our slack channel as I mentioned earlier. There might be more people to give you a hand.

@milosgajdos83 I cannot join to the work space. It gives error to contact work space administrator. Can I have join link or something to join to the channel? if you could help how to join the workspace that'd be great for my questions :)
I ran the command by the way after getting a long list of modules it gave the below error:
go: extracting golang.org/x/sys v0.0.0-20190726091711-fc99dfbffb4e
build github.com/micro/micro: cannot load github.com/micro/go-micro/cmd: cannot find module providing package github.com/micro/go-micro/cmd

@alirezastack the link to our slack is on here. Apologies for invalid URL earlier.
I don't quite understand how can you be getting this error:
build github.com/micro/micro: cannot load github.com/micro/go-micro/cmd: cannot find module providing package github.com/micro/go-micro/cmd

Since there is NO package called cmd under github.com/micro/go-micro
Can you create a gist of output that captures the command you're attempting to run and the output somewhere?

@milosgajdos83 it is really weird that every time I run the same command I get a different result. The first installation attempt and the second installation attempt

Very strange! Tbh, kinda running out of ideas here...I suspect some local workstation go setup shenanigans.
It seems the command in the second gist has succeeded then?
Also snap is some kinda Ubuntu command thing, no? I'd maybe uninstall go and installed the latest go from source and do the go get -u... thing again.

I appreciate for the work. I think it would be much easier to reinstall golang and proceed with micro installation again. I will update here.

Unfortunately reinstalling go from source an installing go-micro didn't help. I'm closing this issue as this seems work environment issue rather than go-micro.

Just in case anyone else run into the same issue, What fixed it for me,
export PATH=$PATH:$(go env GOPATH)/bin
export GOPATH=$(go env GOPATH)

Just in case anyone else run into the same issue, What fixed it for me,
export PATH=$PATH:$(go env GOPATH)/bin
export GOPATH=$(go env GOPATH)

export PATH=$PATH:$(go env GOPATH)/bin
export GOPATH=$(go env GOPATH)

worked for me thank you @teract-ng


The instance will be re-registered when the unified was instance is restarted

Search before asking

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

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened
When we use the skywalking agent, every time we restart the instance, than will regenerate a random number of registered instances to the oap server, which will make it inconvenient to analyze the problem from the perspective of the instance. So we suggest whether SkyWalking can provide a mechanism to ensure that the registered instance can be returned to the same instance every time it is restarted,thanks.
What you expected to happen
Generally, when a service instance does not change in deployment, we think it is the same instance, regardless of whether there is a restart in the middle. In this way, we can summarize and analyze the data in different time periods of the same instance.
How to reproduce
When we use the skywalking agent, every time we restart the instance, than will regenerate a random number of registered instances to the oap server, which will make it inconvenient to analyze the problem from the perspective of the instance. So we suggest whether SkyWalking can provide a mechanism to ensure that the registered instance can be returned to the same instance every time it is restarted,thanks.
Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Why are you opening a new one?


[SPARK-48633][BUILD] Upgrade scalacheck to 1.18.0

What changes were proposed in this pull request?

Upgrade scalacheck to 1.18.0.
Why are the changes needed?

There are some fixes:
https://github.com/typelevel/scalacheck/releases/tag/v1.18.0
https://github.com/typelevel/scalacheck/releases/tag/v1.17.1
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.
Was this patch authored or co-authored using generative AI tooling?

No

This is the first release that supports Scala Native 0.5. Otherwise this is functionally the same as 0.17.1.

We won't necessarily upgrade this though but I am fine.

Merged to master.


Telemetry for pilot xDS streaming

With envoy v2, we lost metrics of sidecar's xDS request, because non-mtls traffic goes to pilot grpc port directly without going through sidecar. Besides that, we don't have good support for http streaming telemetry https://github.com/istio/proxy/issues/1828. Suggest to revive pilot metrics after istio-proxy adds grpc streaming telemetry report.
cc @costinm @douglas-reid @kyessenov

I'm not sure why we opted out of the proxy for non-mTLS traffic. That seems like a step backwards -- and one that was not done with the requisite changes to monitoring configuration for dashboards, etc. It also significantly impacts the ability to route telemetry for Pilot through Mixer, undoing work that has been marked as complete on our roadmap for a long time now.
cc: @andraxylia
I think all of this means that we need to disable large sections of the Pilot dashboard -- pending suitable replacements.

@costinm had a reason for bypassing the proxy.

Even with the proxy in between, you won't get any useful metrics. You simply get info that the ADS call was made and not about the individual resources requested in each call. Pilot is emitting the same metrics internally (as prometheus metrics). We can stream these metrics to the dashboard, if that helps..

Custom metrics will not be handled by mixer adaptors. That's why we want to
emit the default limited metrics. The missing details in metrics is an
istio limitation that we should all be working towards fixing, since the
same arguments apply to application level metrics.
On Thu, Jun 21, 2018, 12:45 PM Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

Even with the proxy in between, you won't get any useful metrics. You
simply get info that the ADS call was made and not about the individual
resources requested in each call. Pilot is emitting the same metrics
internally (as prometheus metrics). We can stream these metrics to the
dashboard, if that helps..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/6458#issuecomment-399220658, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJGIxo7q10m-Ki6gHkga-w_eA7zTQ1NNks5t-_fYgaJpZM4UxbY6
.

@rshriram yeah, we are going to have to make sure that we have a source for those metrics.
I do want to point out that this isn't just about metrics. This also means we've lost access logs for Pilot (and any other sort of information that could be generated from Report() calls, including trace, edge, and other known templates).
The switch to streaming gRPC certainly would have impacted us as well, but a little something is still marginally better than nothing.
In any case, we need to update the dashboards, track further changes, and document that Pilot is no longer using Istio for monitoring (i think this undoes release notes from 0.8).

This is probably no longer relevant without a sidecar. Let's close this and open a more general one for h2/grpc streaming metrics.

ref https://github.com/istio/istio/pull/7251

ref https://github.com/istio/istio/issues/7259


Split up DNS integration module

Codecov Report

Merging #89 into master will decrease coverage by 2.72%.
The diff coverage is 44.18%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
- Coverage    93.4%   90.68%   -2.73%
==========================================
  Files          16       19       +3
  Lines         728      762      +34
==========================================
+ Hits          680      691      +11
- Misses         48       71      +23

Impacted Files
Coverage Δ

opwen_email_server/services/cloudflare.py
0% <0%> (ø)

opwen_email_server/constants/cloudflare.py
0% <0%> (ø)

opwen_email_server/constants/sendgrid.py
100% <100%> (ø)

opwen_email_server/actions.py
96.2% <100%> (+0.04%)
:arrow_up:

opwen_email_server/services/sendgrid.py
77.41% <57.14%> (-3.31%)
:arrow_down:

Continue to review full report at Codecov.

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


Editing QIS tutorials to be compatible with QISKit 0.5.0

This addresses Issue #155 for the quantum information science tutorials.

There are still some Q_program.execute calls in entanglement_revisited.ipynb. Is this intentional?

@quantumjim and @rraymondhp, I've now removed the execute calls from all the QIS tutorials.


python39Packages.tensorflow build failure on x86_64-linux as of 891d0226

Issue description
Build of python39Packages.tensorflow failed on x86_64-linux as of 891d0226de6e281422a8d0d99814925fd7aed8d0. This is currently breaking python3Packages.tensorflow-bin.
error: builder for '/nix/store/ra0brrxhlk461ig6imw2b0il7lyjbxli-python3.9-tensorflow-2.7.0.drv' failed with exit code 1;
       last 10 log lines:
       > Requirement already satisfied: protobuf>=3.9.2 in /nix/store/azllrykpck52hhismhn7vdfjqv8slh83-python3.9-protobuf-3.19.3/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (3.19.3)
       > Requirement already satisfied: numpy>=1.14.5 in /nix/store/lwk6w9022x0rn7v9jf4lraxyykb3yqzf-python3.9-numpy-1.21.5/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (1.21.5)
       > Requirement already satisfied: google-pasta>=0.1.1 in /nix/store/f5r90mvr7fhzbzf9b1qcxjx3v407dpin-python3.9-google-pasta-0.2.0/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (0.2.0)
       > Requirement already satisfied: tensorboard~=2.6 in /nix/store/h4qszvv52j0hq2pmiy5gadqpaqnyzah5-python3.9-tensorboard-2.8.0/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (2.8.0)
       > Requirement already satisfied: wrapt>=1.11.0 in /nix/store/yxgwr65bfpzb9py2q0rf7a1ididm9nph-python3.9-wrapt-1.13.3/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (1.13.3)
       > Requirement already satisfied: absl-py>=0.4.0 in /nix/store/kkwdp67afj2qk2h380zq4giiwi7y8wwl-python3.9-absl-py-1.0.0/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (1.0.0)
       > Requirement already satisfied: h5py>=2.9.0 in /nix/store/xshnrg2zmvc3chs9bm84s68zmmdrccj4-python3.9-h5py-3.6.0/lib/python3.9/site-packages (from tensorflow-cpu==2.7.0) (3.6.0)
       > ERROR: Could not find a version that satisfies the requirement tensorflow-estimator<2.8,~=2.7.0rc0 (from tensorflow-cpu) (from versions: none)
       > ERROR: No matching distribution found for tensorflow-estimator<2.8,~=2.7.0rc0
       >
       For full logs, run 'nix log /nix/store/ra0brrxhlk461ig6imw2b0il7lyjbxli-python3.9-tensorflow-2.7.0.drv'.

full build log
python3Packages.tensorflow-bin maintainers cc: @jyp @abbradar @cdepillabout
python39Packages.tensorflow maintainers cc: @jyp @abbradar
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit 891d0226de6e281422a8d0d99814925fd7aed8d0
Run nix-build -A python39Packages.tensorflow

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.13.0-1021-azure, Ubuntu, 20.04.4 LTS (Focal Fossa), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.7.0`
 - nixpkgs: `/nix/store/r902mrj2iwsjhy8gs6y0rbr9nada0z4z-source`

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tag:<PHONE_NUMBER>954458355

I'm not quite sure why this doesn't have the same internal tag as https://github.com/NixOS/nixpkgs/issues/169018... they seem to be the same AFAICT.

oh I see... the hashes in /nix/store/-pname-version for each of the dependencies changed. hmmmm


Question & Feature request: how can I integrate other 3rd party sign-in in Frontend react-app only？such as Sign In with Google for Web (gsi)

I have a simple react-app typescript sample by using package react-gsi which been integrated Sign In with Google for Web (gsi)  as below:
https://github.com/AwesomeYuer/react-gsi.sample.ts
I also made some login UI related modification in
https://github.com/AwesomeYuer/chat-copilot/blob/mutiple-sign-in/webapp/src/components/views/Login.tsx
but I do not know how to enter the chat functional interface after login?
Would you give me some suggestion and sample code to implement it?
BTW: I want implement other 3rd party and custom common OAuth2/JWT SSO, not only Google Sign-In.
I think the unified solution abstraction for chat-copilot frontend webapp SSO is better.
I hope it will be new feature in recent future pipeline
the screenshots as below:

Google Login Button

Signed-In Info show in Login View only

@gitri-ms, do you have any pointers on how someone could integrate a different auth provider?

for referring: another simple react js sample in js not ts , support msi and gsi
https://github.com/AwesomeYuer/msi-gsi-sso-react-spa.js

This is not a feature we are planning to support in the Chat Copilot reference app, but I highly encourage you to keep pursuing it. Let me see if I can shed some light on our authentication setup to help you along.

All requests from the frontend to the backend need to include an access token. We currently retrieve that token via AuthHelper.getSKaaSAccessToken. You could consider adding another option in there that detects if the user has signed in with Google (or

You will also need to make changes on the backend, as the service is set up to require authentication to all endpoints. Take a look at the AddCopilotChatAuthentication extension method. You could add a third authentication option here, and I encourage you to dig into the different options available through IServiceCollection.AddAuthentication -- looks like there is one for AddOAuth.

I have a task on me to create an architecture document for our authentication setup. I am hoping to be able to start that soon, and I expect it would be helpful to you and others who are interested in supporting other auth providers.

@gitri-ms thanks , go ahead

@AwesomeYuer - I'm not sure of this answer here, but I think this would be a great conversation to have in our Discord community. In fact, we have a dedicated channel just for Chat Copilot where you can engage with other developers who might have ideas on how to build this.
As I mentioned before, this is not a feature that we are planning to bring to the Chat Copilot repo, so I am going to close this issue. But I encourage you to continue exploring how to build a unified identity solution and implement it in your own fork of Chat Copilot!

@gitri-ms
how can I join the dedicated channel just for Chat Copilot?
I can't access it now.
I can't search any useful results by using 'chat-copilot' or 'chat' or copilot?
Is the discord NOT public?
Thanks


Deprecate Top App Bar renderProps

related https://github.com/material-components/material-components-web-react/pull/688
In v0.13.0 deprecate props and methods in top-app-bar/index.ts to support renderProps. This is in favor of compositional declaration of the TopAppBar.

@mgr34 did you want to deprecate this since you also added the new top app bar format?

hey @moog16  Sure, I will get to it sometime this week.

awesome! Thanks

Hey @moog16 I wont be able to get to it this week after all. I'll aim for sometime next week.  Have a good holiday weekend.

no worries! we can push til next release. Have a great long weekend too!


fix: Uncaught exception in getCamelRoute method + increase test coverage

The fix for https://github.com/KaotoIO/kaoto-backend/issues/662
The Reproducer for https://github.com/KaotoIO/kaoto-backend/issues/662
Extends test coverage to test this case in each StepParserService implementation ( + created test for IntegrationStepParserService)

Changed to IOException


Antistasi medical not turning off

Version: <IP_ADDRESS>
Mods: CBA, TFAR, ACE, RHS, RHS ACE compat
Environment: MP dedi.
have you edited the missionfile?: No
Issue:

Is there a way to manually disable the antistasi medical system as it isn't automatically turning off when it detects ace medical and sometimes leaves enemies in this confusing limbo where they're in the antistasi downed state instead of the ace medical downed state. They cannot be killed unless you throw grenades at them or use ace medical to give them an epipen to maybe wake them up so you can kill them again. The surrendering and other parts of the AI work as intended.

Turn off AI unc it causes issue's with the Antistasi medical


Visual Studio Test task fails with System.IO.FileNotFoundException on temp file

Type: Bug
Task Name: Visual Studio Test
Environment

Server - Azure Pipelines

Agent - Hosted:

OS: Windows Server 2016 Standard

Visual Studio Version: 2019

Agent Version: 2.155.1

Issue Description
The task has started failing every time it runs. It started failing when the pipeline auto-updated the task from version 2.159.1 to version 2.160.2.
The log for this task shows it failing with a System.IO.FileNotFoundException:
Task logs
logs_15713.zip
Error logs
##[error]Error occured while executing System.IO.FileNotFoundException: Could not find file 'E:\agentG2\_work\_temp\m0umztbldww.tmp'. File name: 'E:\agentG2\_work\_temp\m0umztbldww.tmp'    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)    at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)    at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)    at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)    at System.IO.StreamReader..ctor(String path, Encoding encoding)    at System.IO.File.InternalReadAllLines(String path, Encoding encoding)    at MS.VS.TestService.VstestConsoleAdapter.TestSelectorCommandInputs.GetTestsList(String listTestsFile)    at MS.VS.TestService.VstestConsoleAdapter.TestSelectorCommandInputs.GetImpactedTestsCommandInput(VstestConsoleRunContext testRunContext)    at MS.VS.TestService.VstestConsoleAdapter.ExecutionStateResolver.GetNextPhase(VstestConsoleRunContext consoleRunContext, ITestRunPhase currentPhase, ITestRunPhaseResults phaseResult) Completed TestExecution Model... ##[warning]Vstest failed with error. Check logs for failures. There might be failed tests. ##[error]Error: The process 'E:\agentG2\_work\_tasks\VSTest_ef087383-ee5e-42c7-9a53-ab56c98420f9\2.160.2\Modules\DTAExecutionHost.exe' failed with exit code 1 ##[error]Vstest failed with error. Check logs for failures. There might be failed tests. ##[section]Finishing: VsTest - testAssemblies x86

Running into the same error.  I have 6 test tasks in a pipeline and this was happening to two of them - the ones that had "Run only impacted tests" checked. Unchecked that and now the test tasks don't error out.

Running into the same error.  I have 6 test tasks in a pipeline and this was happening to two of them - the ones that had "Run only impacted tests" checked. Unchecked that and now the test tasks don't error out.

I tried unchecking that box on my test task...and my pipeline runs OK. That is a good enough workaround for me. Thanks for providing the suggestion.

We have this problem too, only since today...
Task is 2.160.2 but i can't be sure about the previous version.
We never had any issue with the checked option "Run only impacted tests" before today.
The temporary workaround will do but a quick fix or rollback would be great!

We are encountering this problem as well.

We get the same error

FYI - I reached out to @AzureDevOps on twitter yesterday about this. Here is their most recent response:

Thanks for sharing this with us! We noticed that some other users are experiencing a similar problem and that you shared a considerable amount of details, including the error log. Our engineers will reach out rather swiftly to look further into this. We appreciate your help.

We are facing the same issue, since the auto-upgrade from 2.159.1 to 2.160.2.
We are getting System.IO.FileLoadException loading our CLI/C++ assemblies from C# test projects.

We have faced the same issue, since the auto-upgrade from 2.159.1 to 2.160.2. We have found the reason: the generated .runsettings file by the task uses single '' instead of '\'. See attached files.
Using the settings file with '\' solved the issue for us.
runsettings_2.159.1.runsettings.txt
runsettings_2.160.2.runsettings.txt

I believe we have a regression when "run only impacted tests" is selected. We will get the RCA at the soonest and hotfix the task in the next few days. Stay tuned here for updates.

As for

We have faced the same issue, since the auto-upgrade from 2.159.1 to 2.160.2. We have found the reason: the generated .runsettings file by the task uses single '' instead of '\'. See attached files.

We have already hotfixed this and the update should reach all accounts in the next 2-3 days.

I have identified the issue and have made the fix. Will post the hotfix deployment status here once i start the process

If something like this occurs in the future, is there a way we can force the pipeline to use a specific previous minor version of the task?
In this instance, making it use 2.159.1 would have been an easy workaround until the hotfix version was published.

@KevinCust this is something we've actually thought about before.
 As of today if i wanted to rollback i would have take the old task package change the task version to something greater than what is present and deploy a hotfix the make the change. And this generally can be completed in 4-5 hours tops. And we have done this once or twice when the break was so complex that it would take us a day or two to figure out the root cause.
In this case the change required was quite literally 3 lines of code, (and of course a few reactionary items to go fix our telemetry so that we can auto detect a similar issue in the future) but we were able to make the fix in a very short amount of time and i am starting the deployment as i am typing this out and will update the status here.

This has been hotfixed for all accounts. You will find the fix in task version 2.160.4 or 2.161.2 and above. Please let me know if you are able to turn on test impact and get things going again. And thank for you bringing this to our notice.
Please note that by adding the "Area: Test" tag you can get the issue routed to us much sooner and reduce the delay for a response.

I gave it a go and can confirm v2.160.4 works as expected while looking for impacted tests again :
***************************** Section 'Get Impacted Tests' Starting *****************************
V, 2019/11/20, 15:06:05.737, PERF: CreateTestRun: took 153.1381 ms
V, 2019/11/20, 15:06:05.737, PERF WARNING: CreateTestRun: took 153.1381 ms
V, 2019/11/20, 15:06:05.737, Tests that are discovered.

...

V, 2019/11/20, 15:06:07.018, Published Test Run : 1013592
***************************** Section 'Update test results' Ended ********************************

Apologies again for the break and thank you everyone for reporting this and being patient while we patched it up.


Latin and cyrillic letters not showing in Http response body

I have a backend that stores some locations. When i call a POST request
the json should look like this:
{"location":"Karađorđeva 45"}
But instead it looks like this:
{"location":"KaraÄorÄeva 45"}
I tried setting the encoding parameter multiple times, but that didn't help.
var response = await http.post(       Uri.encodeFull(Registry.BASE_URL + "/places/get-all-places/"),       encoding: Encoding.getByName("utf-8"),       headers: {         "Accept": "application/json"       }     );
I'm sure that I'm missing something. How can I fix this?
Thanks in advance!

Using an UTF8 decoder like shown in https://stackoverflow.com/questions/27808848/retrieving-the-response-body-from-an-httpclientresponse might help

That worked, thank you so much!

I also found this: https://stackoverflow.com/a/51370010/1121497
Use json.decode(utf8.decode(r.bodyBytes)) instead of just json.decode(r.body).

You save my day bro


KaTeX rendering error

The katex inline math and display math failed to rendering expressions like ${{C}_0}$, ${{C}^0}$.
It is the curly braces around C causing this problem, although in the example the curly braces can be dropped but not in the actual slide code. A work around is to insert space such as ${{ C }_0}$.
To Reproduce
Steps to reproduce the behavior:

slidev to initialize a slide
put ${{C}_0}$ in the md file
See the error in attached picture

Desktop (please complete the following information):

OS: Kubuntu-22.04 LTS
Browser: Firefox, Chromium
Slidev version: v0.34.3

The issue comes from the fact that katex generates code that (also) contains the raw typed expression, so it contains {{ that is used for vue expressions.
To be sure, can you confirm that what works around the problem is to add a space between the two { (I still get an error with the workaround mentioned in the issue description).


Add initial swagger spec generation for API docs

This adds swagger comments into a separate doc package, so they don't
interfere with existing comments.  Models are scanned automatically, but
routes are not and need to be added manually.
https://goswagger.io/use/spec.html

Swagger specs have to be manually created. Linking to the pkg reference docs for now


Notify duration is not working

Changing the time parameter has no effect whatsoever, could you take a look or guide me how to solve it?

https://sandbox.org.ua/olton/code/9zjmNDbXV4

I was using it this way, passing the parameter inside the notify.create
notify = Metro.notify;
notify.create(message, '' , {
duration: 3000,
width: 250,
cls: classe
});	}
but now putting in the notify.setup worked, grateful for the help
	notify = Metro.notify;
	notify.setup({
		duration: 3000
	});
	notify.create(message, '' , {
		width: 250,
		cls: classe
	});	}


Is MapBox Token needed if we dont make any Mapbox queries?

All I want is to position 3d objects in GPS coordinates. I dont need mapbox maps or directions or anything like that. Do I still need a mapbox token and internet connection for this purposes ?

No, a Mapbox API token is not required. You will likely need some connectivity for location services to work well, however.

Thanks.. I implemented the mapbox positioning classes independently.. and apparently they work.  :)


general: pass self to ./lib & ./hosts

It is generally useful to acess the top level flake from
library functions or hosts. This not only simplifies
the mental model and code but also provides additional
context and not least a handle to the repo source code
in the nix store.
closes #169
bors delegate=@Pacman99

bors r+

bors try

@Pacman99 Is this clarifying force push correct?
https://github.com/divnix/devos/compare/0173d29843c5f272a11bbec9ea56f938f759471c..30f18c720e917f71caf12e78084b0ab7c3a09707

Yeah this makes sense, it would be good to get in these changes soon.

I think @nrdxp has to delegate one of us first since their the repo owner.

bors r+

Is this a duplicate of #164?

It is a carve out as direct dependency to #168 and is included in #168 .
I wanted to separate concerns of #164 in order to accentuate and walk through their use cases a little slower.

I would prefer we discuss and merge #164 instead since thats already come up as a requirement for a couple other PR's. I don't see the point in picking apart the different parts of it into seperate PR's that need it.

I think @nrdxp has to delegate one of us first since they're the repo owner.

That is correct, delegation happens on a per PR basis.

I don't see the point in picking apart the different parts of it into seperate PR's that need it.

It's kind of a review tactic of mine... :wink: Also, #164 had a lot of force pushes which made it hard in my opinion to follow the complete thought process.
This was a dependency of #168 so it was just incorporated.


IE8 error when submitting form: Object doesn't support this action

Error is raised when you submit ajaxifized form for the second time (form was re-rendered by snippet replacement). Problem is on this line as it was previously reported on nette forum.
How to reproduce:

download WinXP/IE8 virtual machine and load it (I can't reproduce it in emulated IE8 in devtools)
download nette sandbox, load nette.ajax.js, init it
wrap page to content snippet
create following form, place it to snippet and submit it twice

$form = new \Nette\Application\UI\Form();
$form->addSubmit('send');
$form->getElementPrototype()->addClass('ajax');
$form->onSuccess[] = function ($form) {
    $this->redrawControl('content');
};

Oh, now I see that the original problem is #75 and people were reporting the same thing as I'm in comments of commit b96243f35b58c880dd1fad2778395a08a8193c69. The proposed solution works, may I send PR?
Working fix:
if (validate.form && analyze.form && !((analyze.isSubmit || analyze.isImage) && analyze.el.attr('formnovalidate') !== undefined)) {
    var ie = this.ie();
    if ((typeof ie === 'undefined' || ie >= 9)) {
        if (analyze.form.get(0).onsubmit && analyze.form.get(0).onsubmit(e) === false) {
            e.stopImmediatePropagation();
            e.preventDefault();
            return false;
        }
    }
}

I think this has been fixed long time ago.


A new Class, creating bridge-free Josephson Junctions

A class creating a bridge-free JJ.

What are the issues this pull addresses (issue numbers / links)?
Creating a bridge-free junction
Did you add tests to cover your changes (yes/no)?
Yes.
Did you update the documentation accordingly (yes/no)?
documentation added
Did you read the CONTRIBUTING document (yes/no)?
yes
Summary
This class is to design a brdige-free josephson junction.
The reference has been mentioned in the description of the class.
All features can be adjusted as needed.
Details and comments

 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.


SLW  WIND TOKEN  -  SLW

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ] Filename in the lowercase format
[ ] Image format: png
[ ] Image size: 256 by 256 px

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[ ]  Filename in the lowercase format
[ ]  Image format: png
[ ]  Image size: 256 by 256 px

0x0a98273b00d699bfc0bc445ec8cdf17653a98c1c

0x0a98273b00d699bfc0bc445ec8cdf17653a98c1c


Pick a GitHub App name

😢
Adam has reserved us takocat, which is pretty good actually. Do we have any other ideas?
Further Reading
https://en.wiktionary.org/wiki/Appendix:1000_Japanese_basic_words

I've tried some unicode like æ, but I believe GitHub might be converting it to ascii.


Fix reach example.

urdf_robot was None when being added to the viewer. It did not appear that urdf_robot would ever be Some from the current code.
This does break a public API, so an alternative would be to add urdf_robot via a builder method instead if preferred.
If it is ok to break the API I can make urdf_robot no longer optional.
Error message:
➜  gear git:(master) cargo run --release --example reach
   Compiling gear v0.6.0 (/Users/jon/src/gear)
    Finished release [optimized] target(s) in 14.62s
     Running `target/release/examples/reach`
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', examples/reach.rs:67:40
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Sorry for late. Let's fix it!


Remove now useless kotlin script compiler flag

It was only useful during the 1.3/1.4 migration

@bot-gradle test this

Closing as dropped


Fixes configuration issue

Fixes issues encounterd in #3

Thanks for this.
Looks like I have some additional work to do to get the tests up to speed with the rest of the seneca data stores. I'll try to find some time for this during the week.

This can't be merged, please update


Feature request: Show linked PRs (if any) in Projects

Gitea version (or commit ref): v1.13.0

Description
At this moment, both PRs and Issues can be added to Projects, which I think it's a nice feature. However, issues being tracked in a Project do not reflect having any PRs attached to them. This makes navigation a bit cumbersome, specially if one is making use of the popular "Ready for review" column, as a reviewer has to navigate to the issue and then to the PR linked in it.
I think it would be nice if PRs showed as an add-in to issue cards in the Project view. This is similar to what github does.
Screenshots

How it looks now
How I think it could be improved (from Github.com)

I forgot to mention that I can try to work on a PR for this if you think it'd be a useful feature, and give me some pointers on where to get started!

@roobre I think we have stored the information on comment table but they have neither been displayed on issue page right sidebar nor projects, dashboard. But it's useful I think.


⚠ Mobitopup has degraded performance

In 10e6a62, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 14086 ms

Resolved: Mobitopup performance has improved in 6d88a2a.


Is this project still alive?

I'm wondering if this project is still alive, as there are no recent commits and the whole init process does not seem to work anymore.

Hi Igor,
A lengthy Python 3 migration, and limited engineering hours have put external releases on hold for some time. I can't speak for the engineering team any more, but I do believe that they want to get back to a regular external release cycle at some point in the future.


New records: mx, srv

Initial PRs are https://github.com/infobloxopen/infoblox-go-client/pull/200 and https://github.com/infobloxopen/infoblox-go-client/pull/198


verus coin

Please describe your issue in detail. Attach screenshots if you can, they help a lot.

If you're experiencing an issue or have any question about the desktop app, please ask in http://verus.io/discord, or create a detailed GitHub issue.


Module that is "deselected" via -pl !... is built if changed

If a module that is "deselected" via mvn -pl !... is detected as "changed", then GIB will have it built, which is most likely not what the user expects.
This is caused by the following change: https://github.com/vackosar/gitflow-incremental-builder/commit/e46a53817ab92246a4369e2007a98e086963ae49#diff-76674b96623cf2df2e4eccd68f1183f1
The question is: Should (non-deselected) up- and/or downstream modules of the deselected module(s) still be built?

The question is: Should (non-deselected) up- and/or downstream modules of the deselected module(s) still be built?

I went with: yes! In case this doesn't meet the expectations of some user we can introduce a toggle for that.


[Auth] Port IAuthenticator change to support MSI authentication

as per PR https://github.com/microsoft/botbuilder-dotnet/pull/3255
Azure App Service (and several other resource types) has a Managed Service Identity feature which simplifies management of application identity - see Microsoft.Azure.Services.AppAuthentication for more information.
By having AdalAuthenticator derive from an interface, I can then inject my own MsiAuthenticator that uses AzureServiceTokenProvider to get the token to call the channels.
I can inject my MsiAuthenticator via overriding BuildCredentialsAsync on BotFrameworkHttpAdapter and returning a MsiAppCredentials class that, in turn, returns the MsiAuthenticator

@rggammon I can assign this one to yourself if you are interested. The goal is to port your dotnet PR to python. If not interested, I can pick it up :) Thanks again for your contribution!

Thanks @carlosscastro - I was looking at how this works in python. Perhaps I would inherit from BotFrameworkAdapter & override create_connector_client() to customize token getting in the python implementation? Happy to look at this, but I don't think the IAuthenticator change translates directly to python, so just need a few tips.

I think the closest translation would be to override a subclasses "__get_msal_app".  For example, see AppCredentials (base class) or MicrosoftAppCredentials or CertificateAppCredentials.  "__get_msal_app" is the MSAL object to get the token.  If that is the case I'd rename that method since the double-udnerscore indicate "private".

Gabo and I had a conversation on this one. Since this IAuthenticator is in the deep auth layer and is not openly documented as an extension point, or particularly valuable as an extension point, we'll leave it as-is.


Update multisig.md

Adding an extended overview of multi signatures and multisig scripts, some edits in instructions. Worked on this with @Jimbo4350

bors r+

bors r+


Expose waitForDedupingInterval() as part of the public API

Writing tests with SWR is very painful. If you don't know the magic incantation in #781, you can easily have nondeterministic tests that can be quite difficult to debug.
I'd expect there to be a way for a test to wait for all pending requests to complete. We have rolled our own at Twitter but I'd much prefer it to be documented, stable behavior rather than sleep(1) :)

waitForDedupingInterval that I've added depends on sleep(1) and  testing-library's act, so it doesn't make sense to expose this as a public API.
But I think it's a good idea that SWR provides an API for the case.
SWR can provide a more stable API if it's implemented as a part of SWR because it can wait for a deduping interval and async mutations precisely.
The downside is to increase the file size even though it's an API for testing.
But I think it worth considering adding it even though I have no idea what the appropriate interface is.

@koba04 If you're concerned about file size, you could provide a swr/testing module to export them through so they don't get included as part of the main bundle.


GETTING ERROR WHILE DOING BACKUP

getting this error
time="2022-04-01T08:36:44Z" level=error msg="Error listing backups in backup store" backupLocation=default controller=backup-sync error="rpc error: code = Unknown desc = RequestError: send request failed\ncaused by: Get https://snapshot-volume-backup.snapshot-volume-backup.us-southeast-1.linodeobjects.com/?delimiter=%2F&list-type=2&prefix=backups%2F: x509: certificate is valid for *.us-southeast-1.linodeobjects.com, *.website-us-southeast-1.linodeobjects.com, us-southeast-1.linodeobjects.com, website-us-southeast-1.linodeobjects.com, not snapshot-volume-backup.snapshot-volume-backup.us-southeast-1.linodeobjects.com" error.file="/go/src/github.com/vmware-tanzu/velero-plugin-for-aws/velero-plugin-for-aws/object_store.go:308" error.function="main.(*ObjectStore).ListCommonPrefixes" logSource="pkg/controller/backup_sync_controller.go:182"

i found this error was on my side so i solved that error but now i am getting another error which is
Warning  FailedAttachVolume  62s (x9 over 3m15s)    attachdetach-controller  AttachVolume.Attach failed for volume "pvc-29c090aeea174590" : rpc error: code = NotFound desc = Volume with id 101963647 not found
how to resolve this ?

@sdarshil I haven't looked at this project in a couple of years. I'm not running it today since I tore down the clusters where I was using this and haven't added Valero back in.
Guessing from the error message, you may want to ensure that the API token you created using includes Volume reading scopes.
Adding LINODE_DEBUG: 1 to the environment of the deployment should reveal API level details (which may contain your private API token so be careful about reposting without reviewing).

hi @displague actually my api token do have the volume scope , but anyway thanks for help !
it would be great if you can guide in something :)

Take a look at the container logs after enabling the debug environment variable. If the API request is being rejected (or sending the wrong ID) that would be telling.
Likewise, kubectl describe the CSI and Velero resources for their state. Any added detail you could provide would be helpful.

Looks like you found another approach:

https://www.linode.com/community/questions/22647/how-to-take-pvc-backup-in-linode#answer-80082
https://www.linode.com/community/questions/22181/backup-k8s-with-velero#answer-78728


Azure Cloud Services

Azure Cloud Service can no longer be found in the Azure Portal; I was only able to find it via search engine. It seems to be in extended support; as I will need soon sharding and split-merge for a productive app; can you please provide a new and supported option.

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

ID: b10fc569-c153-ecb7-d442-9ae62d22eddf
Version Independent ID: 1bb6b162-c777-4cae-553e-2e1b382eb5fe
Content: Deploy a split-merge service - Azure SQL Database
Content Source: articles/azure-sql/database/elastic-scale-configure-deploy-split-and-merge.md
Service: sql-database
Sub-service: scale-out
GitHub Login: @scoriani
Microsoft Alias: scoriani

@Markus-Wolff Thanks for contacting Microsoft. Are you able to access the Azure Portal?

I can access the Azure Portal and now also did found Cloud Service Classic; I was even there able to create the service; however, the deployment failed. It gave me the following message:
"message": "The requested VM tier is currently not available in West Europe for this subscription. Please try another tier or deploy to a different location."
I also tried the same in the "East US" region with the same failure. Maybe another VM tier, which is available can be used, however, I found nowhere in the azure portal or in the cscfg-file an option/setting for the VM tier or the SKU.
Can you please hint me, what I need to do in order to successfully deploy the split-merge Cloud-Service?
Thanks in advance.

@Markus-Wolff We are checking on this and will get back shortly. Thanks

Cloud Services (extended support) is a new Azure Resource Manager based deployment model for Azure Cloud Services product and is now generally available. Cloud Services (extended support) has the primary benefit of providing regional resiliency along with feature parity with Azure Cloud Services deployed using Azure Service Manager. It also offers some ARM capabilities such as role-based access and control (RBAC), tags, policy, and supports deployment templates.
With this change, the Azure Service Manager based deployment model for Cloud Services is renamed as Cloud Services (classic).
Please follow these steps to create a Cloud service extended support via Azure portal and let us know if you still see this error: https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/deploy-portal
Also, please share your subscription type (pay as you go, free trial?)
I tried creating Cloud services Classic in East US and the deployment was successful.
Depending on the type of your subscription, you may get an error like:

@Markus-Wolff Please see Karishma comment above. Please share the type of subscription you are using. Thanks

Thanks for your help already.
I am clear, that the correct service for the initial mentioned SQL Merge and Split Service is Cloud Services (classic).
With this service and my Visual Studio Professional Subscription, I am able to create the Cloud Services (Classic); as described in the SQL Merge and Split Guidance, I added the certificates, when I go to the step "Deploy your service", and upload the cscfg and cspkg, it accepts the request for deployment. However, after some time in the logs, the message "message": "The requested VM tier is currently not available in West Europe for this subscription. Please try another tier or deploy to a different location." appears.
I have also created, a classic Cloud Services in East US; there the same message appears during deployment.

Thanks for your help already.
I am clear, that the correct service for the initial mentioned SQL Merge and Split Service is Cloud Services (classic).
With this service and my Visual Studio Professional Subscription, I am able to create the Cloud Services (Classic); as described in the SQL Merge and Split Guidance, I added the certificates, when I go to the step "Deploy your service", and upload the cscfg and cspkg, it accepts the request for deployment. However, after some time in the logs, the message "message": "The requested VM tier is currently not available in West Europe for this subscription. Please try another tier or deploy to a different location."

@Markus-Wolff I would suggest to create a support ticket to enable your subscription as shared in the comment above by Karishma . It could be related to subscription type. Support will be the best point of contact for this issue.
https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview Please let me know if you run into any issues.
Regards,
Oury


[FEATURE] 📜 Custom Plugins Log Levels

Is your feature request related to a problem? Please describe
Currently FusionCache allows customization of a lot of different log levels to be used in different scenarios, such as for serialization errors, factory errors, factory synthetic timeouts, backplane errors, etc.
When talking about plugins though, this is not the case: every log message is either Information (for things like "a plugin has been added") or Error (for things like when an error occurred while adding a plugin, etc).
Describe the solution you'd like
Based on a request by community member @shoaibshakeel381 , FusionCache may add a couple of custom log levels, related to plugins.
In particular, 2 new options will be added in the FusionCacheOptions class:
public LogLevel PluginsInfoLogLevel { get; set; }
public LogLevel PluginsErrorsLogLevel { get; set; }

Their default values will be, respectively, LogLevel.Information and LogLevel.Error.

Hi all, I just release v0.20.0-preview2 🎉
Unless some problems will came up this week, the next weekend I'll release the final v0.20.0.

Hi everyone, I've finally released the new v0.20.0 🎉


Fix typos. (kui -> skippbox)

Also, npm install nw doesn't work unless you are inside the skippbox source directory

Good catch @chiradeep thanks.
I also made a small mode that reads the config from your home dir. so it won't read from config.sample file.


Update CI workflow

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

Project coverage is 100.00%. Comparing base (aed588b) to head (7478b56).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #150   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           48        48
  Lines         1117      1117
  Branches       127       127
=========================================
  Hits          1117      1117

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


Create Helm templates from resource manifests

This PR provides support for authoring Helm templates based on existing resources.  The intended workflow is as follows:

Open a resource in the cluster explorer tree view and invoke the Helm: Convert to Template command.  (You can also right-click the resource and choose Convert to Template from the context menu.
You are prompted for a template name (and, if necessary, a chart to add it to).
A template is created in the chart's templates directory.  Initially, we only 'templatise' the metadata.name and metadata.labels.chart fields.
You can now move the cursor to any value in the template and invoke the Helm: Convert to Template Parameter command.
The extension replaces the value with a template expression ({{ .Values.widget.snoofles }}) and creates a corresponding entry and value (widget: > snoofles: mysnooflevalue) in values.yaml.
You can continue converting values to parameters until your template is PERFECT IN EVERY WAY.

The scope for this is 'basic getting started'.  It's not intended to be a means of maintaining complex charts - just a way for someone to take an existing resource and say "this does what I want but I just need to be able to vary these knobs."
Now, I have plenty of questions about my implementation.

Is this a useful workflow for Helm chart authors?
Are there any values which should always be parameterised in predictable ways?
Is it okay to infer a parameter name or is it important to offer fine control?
Is the structure of the generated parameters reasonable?  It's a bit flatter than the manifest YAML but that seems consistent with some of the sample templates.
Are the resultant templates and values.yaml entries correct, or have I missed some subtlety of how Helm wires these things up?
  (The implementation code will make you flinch but let's skate delicately past that.)

It would be great if folks could have a play with it and see if it feels natural and helpful.  Please also report bugs as it's not been extensively tested, though at this stage I'm most concerned about getting the right flow - squashing the edge cases can come later.  Things in the 'and it would be great if it could do X' category might be best raised as issues so that we don't try to boil the ocean in one PR - it's already large and complicated enough - but I can incorporate them if they're must-have.

will take a spin when back on Tuesday for sure!

I found one bug: if you convert a deployment to a template and give it a name with hypens (say, brigade-api-deployment), then when you convert a value in that template using Helm: Convert to Template, it'll use the template name as part of the value. That's normally fine, but hyphens are a special case in Go templates. There's a short write-up of it here: https://github.com/helm/helm/issues/2192
Since it's just interaction with the values, would it be best to convert invalid Go template characters to underscores?
e.g. if I have a template called brigade-api-deployment and convert a value to a template parameter, the resultant value should be .Values.brigade_api_deployment.myValue.
What do you think?

This, by the way, is INSANELY useful, and users have been asking for a feature like this for a long time. See https://github.com/helm/helm/issues/2730 for a proposal on the same features, but as a Helm plugin.
cc @thomastaylor312, you'd probably get a kick out of this

To answer your questions:

Now, I have plenty of questions about my implementation.
Is this a useful workflow for Helm chart authors?

Hard yes.

Are there any values which should always be parameterised in predictable ways?

Nope! Nothing is set in stone in the Chart Template Guide either.

Is it okay to infer a parameter name or is it important to offer fine control?

I could see potential value in prompting while providing the default value, but I like the current infer model as it makes for a better UX for someone unfamiliar with the Helm chart spec. The convention VSCode is choosing looks fantastic to me, at least. If the user wants to customize the value, they can make changes to the template and value after the fact.

Is the structure of the generated parameters reasonable? It's a bit flatter than the manifest YAML but that seems consistent with some of the sample templates.

yep!

Are the resultant templates and values.yaml entries correct, or have I missed some subtlety of how Helm wires these things up?

See my mini bug report above. Otherwise it looks good to me!

 (The implementation code will make you flinch but let's skate delicately past that.)

Absolutely not. The experience is great.

I also like the inferring of the name.

Tidied some code and improved some error handling.  It's not perfect, but ready for a review I think.  @bnookala do you have time?  Thanks!

Oh wow, this is super nice. Especially because I haven't had any time to work on the commandeer stuff.

One other edge case: when converting secrets to templates, the base64 encoding of the secret's data is retained.
Basically, when I convert to a template, this is what I get:
apiVersion: v1
data:
  allowHostMounts: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  allowPrivilegedJobs: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  cloneURL: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  initGitSubmodules: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  repository: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  sharedSecret: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
  vcsSidecar: IEhlbHAsIEknbSBiZWluZyBvcHByZXNzZWQuIENvbWUgYW5kIHNlZSB0aGUgdmlvbGVuY2UgaW5oZXJlbnQgaW4gdGhlIHN5c3RlbS4=
kind: Secret
metadata:
  annotations:
    projectName: bacongobbler/test
  labels:
    app: brigade
    chart: "{{ .Chart.Name }}-{{ .Chart.Version | replace "+" "_" }}"
    component: project
    heritage: Tiller
    release: test
  name: {{ template "fullname" . }}
type: brigade.sh/project

This means that if I install this chart, the secret's metadata will get base64-encoded a second time, which probably isn't the user's intent.

@bacongobbler What is the desired behaviour in the secrets scenario then?  Should all data values be automatically converted to parameters or something?

I can try base64-decoding the data fields but not sure what to do if the result is not text.  Or is that not a concern?  I also see incantations like {{ default "" .Values.api.password | b64enc | quote }} in public Helm charts - do I need to reproduce this and under what circumstances?

I think it only gets re-encoded for the stringData key. The data key will simply leave it alone. Or am I missing something?

I tried round-tripping a secret and it seemed to work but I'm not sure what additional shenanigans Helm might be putting in its way.  It definitely looks like kubectl create (when passed a YAML of kind Secret) expects secrets data to be base64 encoded in the YAML.
I'm inclined to merge with this as it stands in order to get it into the release, and raise an issue for this once we can pin down the scope of the issue and desired behaviour.

Okay, after discussions we believe that the existing code handles secrets data correctly, and I have a thumbs of from Bhargav to defer addressing his remaining comments, so I'm merging this quick before anyone turns up anything else!  #supremeprofessionalism


Upgrade to Node 16 Gallium with Debian Bullseye

This PR:

updates the Docker base image and the Docker builder images to the Node 16 official image, using Debian Bullseye
updates the node engine to 16.14.0, and npm to 8.3.1
updates the package-lock.yaml files to match the new versions; this will also clear the lock file being Uber-specific

Partially resolves #451

 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.Tamas Weisz seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Not quite sure why the build is failing. It works for me locally. Is the PR build not using docker build?

The PR build does a checkout, it doesn't use the docker container.
Looks like the build fails to npm install.
Can you try pulling latest changes from master and try again?
I have rebuilt package-lock with public npm packages.
I have also fixed the package which npm ci was failing on (just-at-uber/eslint-plugin-header).

@just-at-uber , it looks like the updated package-lock.json still have one diff when I rebuild locally in docker:
diff --git a/package-lock.json b/package-lock.json
index 33c7ab4..e60658a 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -5162,2 +5162,2 @@
-      "version": "github:just-at-uber/eslint-plugin-header#ef55ce547ecb6801da326c75374711f0865a57a6",
-      "from": "github:just-at-uber/eslint-plugin-header#ef55ce547ecb6801da326c75374711f0865a57a6",
+      "version": "github:just-at-uber/eslint-plugin-header#aee6a4610ffc1946b821fe869f0ac6b922df303c",
+      "from": "github:just-at-uber/eslint-plugin-header#aee6a4610ffc1946b821fe869f0ac6b922df303c",

Do you mind committing that too? Once done, I'll rebase this PR and try again.

PR has landed with the package-lock update.

LGTM


Bug report: Teams channel validation fails when channel ID contains _ (underscore)

Description
Teams channel validation fails when channel ID contains _ (underscore)
Steps to reproduce
m365 teams channel get --teamName Contoso --channelId<EMAIL_ADDRESS>
Expected result
CLI retrieves information about the specified channel
Actual result
Error<EMAIL_ADDRESS>is not a valid Teams ChannelId

Environment
Latest CLI

We should fix this by extending the validation regex on https://github.com/pnp/cli-microsoft365/blob/4e51be5584b839453f9363b73ee22f0ea8ef3c1c/src/Utils.ts#L56 with _


Emit expected events when destorying a model

When soft deleting a model we must be sure to also emit destroying and destroyed so it won't break compatibility with existing code.

@bsiddiqui

@alanhoff if events are emitting destroying and destroyed do you think we should try and block the saving, updating, saved, updated events?

@bsiddiqui I don't think so. An easy example to follow is that bookshelf-history wouldn't log the soft delete on that model bc it depends on that events, so could any other lib.

@alanhoff but can you see the confusion if saving, updating, saved, updated, destroying, and destroyed would all be called on a delete?

@bsiddiqui as we talked earlier saving, updating, saved and updated wont be triggered by default but the user can opt for turning it on.

@bsiddiqui ready for review

@bsiddiqui ready for review

LGTM


Update tests to remove dependency on Rails 6

Embedded rails app in the tests is outdated

This is particularly important now because the tests fail in Ruby 2.7.0 because of the Rails 4 app that is embedded.
Work to start soon!

This has been resolved by #124.


Prefix all css classnames

Fix global namespace pollution by css classnames.

Hey @karamalie - anything we can do to help ship this one?
The class names collisions are breaking our app and prevents us from merging in the Lottie Player...
Thanks!


refactor(InputMacro): introduce InputMacro classes for grouping

This commit introduces a few InputMacro classes to avoid repetitive
code. Most of the replacement functions are doing the same with different
set of parameters, we can move them to a parent class.

Use vector.size() to avoid a few magic numbers.
Use std::unique_ptr for icu objects
Mark virtual method overrides properly.
Add clang-tidy checks to catch virtual function issues.

Add short keywords for the time macros as discussed in
https://github.com/openvanilla/fcitx5-mcbopomofo/pull/98#issuecomment-1857094043
refactor(InputMacro): provide formatWithPattern and formatWithStyle

extract common tasks from formatDate and formatTime into formatWithStyle
for more generic formatting.
add a new formatWithPattern helper to format datetime with patterns
implement THIS_YEAR/LAST_YEAR/NEXT_YEAR macros with formatWithPattern

@lukhnos this is the follow-up from https://github.com/openvanilla/fcitx5-mcbopomofo/pull/98#issuecomment-1857323122, please kindly take a look.
It'd be nice if my proposal of short keywords for the time macros can be back ported to the upstream.

Just popped up another idea that we can add some more macros:
今年 -> 2023 / 2023 年 / 民國112年 / 令和5年
今天 -> 星期一 / 禮拜一
Would that be a good idea?

While implementing the year macros, I noticed that we can apply some further extractions to make our helpers more generic.

screenshots from my local build

With the pattern stuff, implementing weekday macros is trivial.


Prototype out IntervalHeap or std's BinaryHeap with a comparator-based API

This would allow a heap to be reinterpretted as min/max without affecting the consumer of the collection (no wrapping the data to redefine Ord). It may also be the future of searching in maps/sets. However Heaps are a good simple place to test the ideas out on.
See this PR for preliminary work done in the area. It got blocked on unboxed closures becoming more coherent, which is now the case.
Ideally comparators would be part of the type, with a default Natural Comparator that just uses Ord. A Reverse Comparator would also be useful, in the same vein as the Reverse iterator adaptor. We could also consider providing a Fake Comparator for wrapping PartialOrd impls unsafely.
Unboxed closures that return Ord should presumably work as Comparators.
CC @huonw @sellibitze @aturon @reem

@apasel422 knocked this outta the park


[Bug]: Cannot properly uninstall this app

The problem
I installed WinGet-AutoUpdate-aaS, which comes bundled with a version of your software) by mistake and I'm trying to uninstall it. It somehow created two different entries in my installed apps list (one for theirs and one for yours), and it's yours the one that gives me trouble, as any attempt to uninstall returns a<PHONE_NUMBER> error. Do you know what can I do to fix that error, whatever they have done to cause it?
What version of WAU has the issue?
1.21.13
What version of Windows are you using (ex. Windows 11 22H2)?
Windows 11 23H2
What version of winget are you using?
1.9.25200
Log information
No response
Additional information
No response

No problem. Found the way. The way that app installs this software doesn't work with a RemoteSigned script execution policy.


Fix build/lint due to differences in master and LKG

Fixes CI builds

I'd also open an issue to track performing the action in the comment, when possible ;)


Update style for StyleCI

From #4

Requires @dunglas to configure StyleCI properly

Close because no activity since almost 1 year, and this repository is abandoned.