transitions mixin doesn't seem to work as per documentation

The Bourbon docs on transition shows this example:
@include transition (all 2.0s ease-in-out);

That doesn't seem to work for me.
This css declaration:
test {
	@include transition(opacity 2.0s linear);
}

gets compiled to:
test {
	-webkit-transition-property: opacity, 2s, linear;
	-moz-transition-property: opacity, 2s, linear;
	-ms-transition-property: opacity, 2s, linear;
	-o-transition-property: opacity, 2s, linear;
	transition-property: opacity, 2s, linear;
	-webkit-transition-duration: 0.15s;
	-moz-transition-duration: 0.15s;
	-ms-transition-duration: 0.15s;
	-o-transition-duration: 0.15s;
	transition-duration: 0.15s;
	-webkit-transition-timing-function: ease-out;
	-moz-transition-timing-function: ease-out;
	-ms-transition-timing-function: ease-out;
	-o-transition-timing-function: ease-out;
	transition-timing-function: ease-out;
	-webkit-transition-delay: 0;
	-moz-transition-delay: 0;
	-ms-transition-delay: 0;
	-o-transition-delay: 0;
	transition-delay: 0;
}

timing and delay is correct, but property and durations aren't.
If i use commas:
test2 {
	@include transition(opacity, 2.0s, linear);
}

Then the output is correct:
test2 {
	-webkit-transition-property: opacity;
	-moz-transition-property: opacity;
	-ms-transition-property: opacity;
	-o-transition-property: opacity;
	transition-property: opacity;
	-webkit-transition-duration: 2s;
	-moz-transition-duration: 2s;
	-ms-transition-duration: 2s;
	-o-transition-duration: 2s;
	transition-duration: 2s;
	-webkit-transition-timing-function: linear;
	-moz-transition-timing-function: linear;
	-ms-transition-timing-function: linear;
	-o-transition-timing-function: linear;
	transition-timing-function: linear;
	-webkit-transition-delay: 0;
	-moz-transition-delay: 0;
	-ms-transition-delay: 0;
	-o-transition-delay: 0;
	transition-delay: 0;
}

However, as per docs commas should separate multiple transitions - 2nd example in the docs - not sure how this would work..
Environment:

I'm running sass with sass -r ./bourbon/lib/bourbon.rb style.scss style.css

ruby --version is ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-darwin11.2.0] (using rbenv)

 gem --version is 1.8.10

gem list --local bourbon is bourbon (1.4.0, 1.3.5)

gem list --local sass is sass (3.1.12)

Why it does not include -o-transition and -ms-transitions properties? In my case, bourbon is generating only -webkit, -o and transiton properties only

@Maciekp Per Can I Use data, -ms- prefixes were never needed (it went straight to spec implementation in IE 10) and Opera had the -o- prefix only in version 11.5, which is super out of date now.
Also, I’d recommend using Autoprefixer for your prefixing needs. It has tons of benefits over using Bourbon for prefixing, so much so, that Bourbon v5.0 will no longer have prefixes.


use bfgeom_v01.txt in ceSimReco

BTW, this fcl get this field from Services.Sim but that is superseded by Production/JobConfig/digitize/epilog.fcl.  I wouldn't naturally expect that epilog to be be setting the b field file.

Hi @rlcee,
You have proposed changes to files in these packages:

Validation

which require these tests: build.
@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.
:hourglass: The following tests have been triggered for eb44c28613f4ecccbf547f10a7137ff6364c2912: build  (Build queue has 1 jobs)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at eb44c28613f4ecccbf547f10a7137ff6364c2912.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged eb44c28613f4ecccbf547f10a7137ff6364c2912 at 108a906464e4667abbaf447ade36b0fc15f35687

build (prof)
:white_check_mark:
Log file. Build time: 13 min 54 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at eb44c28613f4ecccbf547f10a7137ff6364c2912 after being merged into the base branch at 108a906464e4667abbaf447ade36b0fc15f35687.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.

I think that this PR is meant to address issue Offline#862. Right?
I don't think it goes all of the way there.  In that issue there are 4 fcl files involved:
Option 1:
ceSteps.fcl:           bFieldFile: "Offline/Mu2eG4/geom/bfgeom_no_tsu_ps_v01.txt"
ceDigi.fcl:              bFieldFile: "Offline/Mu2eG4/geom/bfgeom_reco_v01.txt"
reco.fcl:                 bFieldFile: "Offline/Mu2eG4/geom/bfgeom_v01.txt"

Option 2:
ceSimReco.fcl:      bFieldFile: "Offline/Mu2eG4/geom/bfgeom_reco_v01.txt"

It's not clear to me how to proceed.  I guess the first step is to test the claim that there is more than just bfield and seeding going on.

Thinking a little more.  I don't know if ceDigi.fcl uses the field maps?  It might for looking up the field for B x v  effects?  In any case it only needs the DS map - so all of the above maps files are equivalent for ceDigi.fcl
But code will not be repeatable if ceSimReco and ceSteps use different field maps.

ceDigi uses fields for Lorentz effects, otherwise not.  So only the DS map.
reco clearly doesn't need more than the DS map.
steps (ie primary particle generation) is an interesting case.  In
principle it only cares about DS field as any particle that goes back
through the TS opening will never produce hits and so
we don't care about the field there.  However the field there will affect
the G4 randomization.  So nothing physically incorrect will come from using
just the DS field, but it won't be the
same as if you used the full field.  I don't personally see a need to
burden all our productions with 300MB additional memory overhead for this
aesthetic concern, so I suggest using just the
DS field.
Dave
On Fri, Oct 14, 2022 at 12:37 PM Rob Kutschke @.***>
wrote:

Thinking a little more. I don't know if ceDigi.fcl uses the field maps? It
might for looking up the field for B x v effects? In any case it only needs
the DS map - so all of the above maps files are equivalent for ceDigi.fcl
But code will not be repeatable if ceSimReco and ceSteps use different
field maps.
—
Reply to this email directly, view it on GitHub
https://github.com/Mu2e/Production/pull/206#issuecomment-1279386445, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAH575H44366LGRYHRFB2DWDGZBJANCNFSM6AAAAAARDLVQJU
.
You are receiving this because you are on a team that was mentioned.Message
ID: @.***>

--
David Brown            @.***
Office Phone<PHONE_NUMBER>
Lawrence Berkeley National Lab
M/S 50R5008 (50-6026C)  Berkeley, CA 94720

As discussed in the comp/soft meeting 10/19/22, we agreed to modify the ceSimReco field choice to agree exactly with ceSteps (no TSu_PS).  Even though there is no particular reason to expect a production job like ceSteps to agree exactly with a validation job (ceSimReco) it is probably a little better to bring them into alignment, if there is ~no cost.  There may be an observable random number shift in nightly validation.
After this merge I'll close #862

@FNALbuild run build test
I will wait until tomorrow to merge this.  We expect changes tonight from Ralf's Offline PR#866 and I would like them to be tested in isolation.

:hourglass: The following tests have been triggered for 917d3b9f35780bf34b94c83a2f410b7bb2d1f35b: build  (Build queue has 1 jobs)

:sunny: The build tests passed at 917d3b9f35780bf34b94c83a2f410b7bb2d1f35b.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged 917d3b9f35780bf34b94c83a2f410b7bb2d1f35b at 108a906464e4667abbaf447ade36b0fc15f35687

build (prof)
:white_check_mark:
Log file. Build time: 11 min 54 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at 917d3b9f35780bf34b94c83a2f410b7bb2d1f35b after being merged into the base branch at 108a906464e4667abbaf447ade36b0fc15f35687.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


Show journal entry for a day if that day's page has linked references

Description:

I have a day page which has a linked reference
However, this day won't show up in the calendar as a day with entries

Would love this :)


Bump dependencies under AgentBaker with 0 updates

This PR bumps the following dependencies:

Dependency
From
To

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.263%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
2589

Relevant Lines:
3633

💛  - Coveralls


Note about the compatibility between Sciter SDKs

It should be clear that rust-sciter supports both.

Including some sciter-js examples would help along to make that clear, would also help explain to the user how to use the bindings to rust now that that view.method_name(args) no longer work, and instead Window.this.xcall("method_name", args) has to be used.

https://github.com/GirkovArpa/sciter-js-rust-boilerplate

in 58b5a29, for example.


No extension button

I have installed the plugin and it is enabled, however, I cannot find the extension button to run the HTMl validation. I have relaunched VSCode and have a HTML file open, but the extension button is not present. Any ideas how I can fix it? Thanks!

PS. I am able to use the plugin and it's working well, but the shortcut button would be nice!

Hi @ChrisJohnNewton, thanks for posting this issue.
Have you tried to toggle the vscode status bar?


[Enhancement] Added a message that spark load does not support automatic partitioning

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #19565
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

@Mergifyio backport branch-3.0


Update README.md

Maybe this directory?  hmmm

What are you trying to do? Looks like you just changed the readme?

:-) I don't remember.  Too many days in between.  Not sure why I would have
touched the readme.
Friend Kathren from Maine is here now. She's my UX friend.  You met her.
I'll get her help me.  :-)
EL
On Wed, Aug 21, 2019 at 2:44 PM Brady Sheehan<EMAIL_ADDRESS>wrote:

What are you trying to do? Looks like you just changed the readme?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/RecoveryEnhancementSolutions/recoveryenhancementsolutions.github.io/pull/5?email_source=notifications&email_token=AM3SVP2UWZ6OGHYQTQ5I2WDQFWEKPA5CNFSM4IMLKDF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42XU6I#issuecomment-523598457,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM3SVPZF3V3YHK6VG2BXTY3QFWEKPANCNFSM4IMLKDFQ
.

--
Elizabeth L.
412-999-4812
Twitter: @elaruepa


Can't connect to MySQL server on 'localhost'

I am having an issue with my flexible python app deployment connecting to the cloud sql instance. It is the same issue as posted here: https://github.com/GoogleCloudPlatform/getting-started-python/issues/92
Here is the error I receive:
sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 2] No such file or directory)")
"

I have setup a MySQL Second Generation instance.
It is working fine when I run the application locally and connect through the proxy.
I have the following flag set in my service.yaml:

beta_settings:
cloud_sql_instances: "project:us-central1:dbinstance"

I was able to find a solution, so I will post it here for others:
I added the following to my yaml file. I think the main difference from the config, is that 'localhost' is omitted.
env_variables:
  SQLALCHEMY_DATABASE_URI: >-
    mysql+pymysql://user:password@/database?unix_socket=/cloudsql/project:us-central1:instance

Interesting. @ryanmats can you see if you can reproduce? If so, we may need to update our connection strings.

So I just tested this quite a few times and have gotten the error sometimes and a functional website other times. The error seems to be independent of whether or not I delete 'localhost' from the SQLALCHEMY_DATABASE_URI. I do know that CloudSQL has been having some flaky problems lately.
@ajpharrington Can you please do me a favor and try again both with and without localhost, back-to-back?

@ryanmats I have tried again with and without 'localhost' in the connection string, and have found it does not make a difference. I even removed the env_variables from my yaml file, to check if the config file string works and it does. It is working as expected now, and I am not able to re-create the original error.

@ajpharrington Thanks for checking. Several other developers have noticed issues like this recently, and we are looking into what could be the problem.
In the near future, please let us know if any already deployed and functional apps suddenly run into this bug. Trying to figure out if this is a CloudSQL issue or an App Engine issue. Thanks!

@ajpharrington So we've determined that this is an issue with new App Engine deployments and CloudSQL (not existing deployments that have already worked) -> we've assigned this bug to someone on the App Engine Infrastructure team to fix.
If you deploy your app and it works, it should continue to work. If one of your new deployments isn't working, you should be able to try again later and it will work.

@ryanmats I just followed the tutorial and I am consistently getting this error. I have tried making multiple new projects, fiddling with settings, however I still get the error with this codebase, as well as my actual app I am trying to deploy (that uses cloudsql).
Do you have any solutions or updates on this?

@ajpharrington I tried your environment variable changes but they did not help.

I described a potential solution (enabling Cloud SQL Admin API) here: https://github.com/GoogleCloudPlatform/getting-started-python/issues/129#issuecomment-332803546


refract uiResponse code

Codecov Report

Merging #165 (c6db8cc) into main (fa70fc0) will increase coverage by 0.46%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##               main     #165      +/-   ##
============================================
+ Coverage     21.38%   21.85%   +0.46%
  Complexity      160      160
============================================
  Files            90       88       -2
  Lines          1590     1556      -34
  Branches         93       93
============================================
  Hits            340      340
+ Misses         1234     1200      -34
  Partials         16       16

Flag
Coverage Δ

unittests
21.85% <0.00%> (+0.46%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...com/github/shoothzj/dev/module/SshShellResult.java
0.00% <ø> (ø)

...ava/com/github/shoothzj/dev/transfer/Transfer.java
0.00% <0.00%> (ø)

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 fa70fc0...c6db8cc. Read the comment docs.


semaphores error: cannot get LockName for a Sync of Unknown type

Pre-requisites

[X] I have double-checked my configuration
[ ] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?
Tried following the example of using a semaphore in WF but once I submit the WF using the semaphore - I get an error.
I've copied and pasted the example used in the docs (& I did mind the namespace name).
Version(s)
v3.5.8
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Followed the steps described in here: https://argo-workflows.readthedocs.io/en/latest/synchronization/#synchronization
created the CM in my argo namespace:
apiVersion: v1
kind: ConfigMap
metadata:
 name: my-config
data:
  workflow: "1"  # Only one workflow can run at given time in particular namespace
  template: "2"  # Two instances of template can run at a given time in particular namespace

Next created the dummy WF using the lock:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: synchronization-wf-level-
spec:
  entrypoint: hello-world
  synchronization:
    semaphores:
      - configMapKeyRef:
          name: my-config
          key: workflow
  templates:
  - name: hello-world
    container:
      image: busybox
      command: [echo]
      args: ["hello world"]

Once I submit the WF via UI - I see in the in the execution window this error message:
 Failed: Failed to acquire the synchronization lock. requested configuration is invalid: cannot get LockName for a Sync of Unknown type

Logs from the workflow controller
I have 2 controllers deployed. These are the logs of controller A:
{"Phase":"","ResourceVersion":"1279411754","level":"info","msg":"Processing workflow","namespace":"argo","time":"2024-09-22T07:54:17.594Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Task-result reconciliation","namespace":"argo","numObjs":0,"time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"warning","msg":"Failed to acquire the lock","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Updated phase  -\u003e Failed","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Updated message  -\u003e Failed to acquire the synchronization lock. requested configuration is invalid: cannot get LockName for a Sync of Unknown type","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Marking workflow completed","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Marking workflow as pending archiving","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"action":"deletePod","key":"argo/synchronization-wf-level-ww7cf-1340600742-agent/deletePod","level":"info","msg":"cleaning up pod","time":"2024-09-22T07:54:17.604Z"}
{"level":"warning","msg":"Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"synchronization-wf-level-ww7cf\": the object has been modified; please apply your changes to the latest version and try again Conflict","namespace":"argo","time":"2024-09-22T07:54:17.607Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Re-applying updates on latest version and retrying update","namespace":"argo","time":"2024-09-22T07:54:17.607Z","workflow":"synchronization-wf-level-ww7cf"}
{"error":"must never update completed workflows","level":"info","msg":"Failed to re-apply update","namespace":"argo","time":"2024-09-22T07:54:17.610Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"archiving workflow","namespace":"argo","time":"2024-09-22T07:54:17.611Z","uid":"387f5ffd-187e-4d76-83ee-0baf46e8b5f6","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Queueing Failed workflow argo/synchronization-wf-level-ww7cf for delete in 1h0m0s due to TTL","time":"2024-09-22T07:54:17.637Z"}
{"level":"info","msg":"Queueing Failed workflow argo/synchronization-wf-level-ww7cf for delete in 59m28s due to TTL","time":"2024-09-22T07:54:49.957Z"}

These are the logs of controller b:
{"Phase":"","ResourceVersion":"1279411754","level":"info","msg":"Processing workflow","namespace":"argo","time":"2024-09-22T07:54:17.594Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Task-result reconciliation","namespace":"argo","numObjs":0,"time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"warning","msg":"Failed to acquire the lock","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Updated phase  -\u003e Failed","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Updated message  -\u003e Failed to acquire the synchronization lock. requested configuration is invalid: cannot get LockName for a Sync of Unknown type","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Marking workflow completed","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"Marking workflow as pending archiving","namespace":"argo","time":"2024-09-22T07:54:17.599Z","workflow":"synchronization-wf-level-ww7cf"}
{"action":"deletePod","key":"argo/synchronization-wf-level-ww7cf-1340600742-agent/deletePod","level":"info","msg":"cleaning up pod","time":"2024-09-22T07:54:17.605Z"}
{"level":"info","msg":"Workflow update successful","namespace":"argo","phase":"Failed","resourceVersion":"1279411755","time":"2024-09-22T07:54:17.606Z","workflow":"synchronization-wf-level-ww7cf"}
{"level":"info","msg":"archiving workflow","namespace":"argo","time":"2024-09-22T07:54:17.619Z","uid":"387f5ffd-187e-4d76-83ee-0baf46e8b5f6","workflow":"synchronization-wf-level-ww7cf"}
	Arguments:      []interface {}{"default", time.Date(2024, time.September, 22, 7, 54, 17, 0, time.Local), "", "synchronization-wf-level-ww7cf", "argo", "Failed", time.Date(2024, time.September, 22, 7, 54, 17, 0, time.Local), "387f5ffd-187e-4d76-83ee-0baf46e8b5f6", "{\"kind\":\"Workflow\",\"apiVersion\":\"argoproj.io/v1alpha1\",\"metadata\":{\"name\":\"synchronization-wf-level-ww7cf\",\"generateName\":\"synchronization-wf-level-\",\"namespace\":\"argo\",\"uid\":\"387f5ffd-187e-4d76-83ee-0baf46e8b5f6\",\"resourceVersion\":\"1279411755\",\"generation\":2,\"creationTimestamp\":\"2024-09-22T07:54:17Z\",\"labels\":{\"workflows.argoproj.io/completed\":\"true\",\"workflows.argoproj.io/creator\":\"system-serviceaccount-argo-argo-server\",\"workflows.argoproj.io/phase\":\"Failed\",\"workflows.argoproj.io/workflow-archiving-status\":\"Persisted\"},\"managedFields\":[{\"manager\":\"argo\",\"operation\":\"Update\",\"apiVersion\":\"argoproj.io/v1alpha1\",\"time\":\"2024-09-22T07:54:17Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:metadata\":{\"f:generateName\":{},\"f:labels\":{\".\":{},\"f:workflows.argoproj.io/creator\":{}}}}},{\"manager\":\"workflow-controller\",\"operation\":\"Update\",\"apiVersion\":\"argoproj.io/v1alpha1\",\"time\":\"2024-09-22T07:54:17Z\",\"fieldsType\":\"FieldsV1\",\"fieldsV1\":{\"f:metadata\":{\"f:labels\":{\"f:workflows.argoproj.io/completed\":{},\"f:workflows.argoproj.io/phase\":{},\"f:workflows.argoproj.io/workflow-archiving-status\":{}}},\"f:spec\":{},\"f:status\":{}}}]},\"spec\":{\"templates\":[{\"name\":\"hello-world\",\"inputs\":{},\"outputs\":{},\"metadata\":{},\"container\":{\"name\":\"\",\"image\":\"busybox\",\"command\":[\"echo\"],\"args\":[\"hello world\"],\"resources\":{}}}],\"entrypoint\":\"hello-world\",\"arguments\":{},\"serviceAccountName\":\"argo-workflow\",\"ttlStrategy\":{\"secondsAfterCompletion\":180,\"secondsAfterSuccess\":180,\"secondsAfterFailure\":3600},\"synchronization\":{}},\"status\":{\"phase\":\"Failed\",\"startedAt\":\"2024-09-22T07:54:17Z\",\"finishedAt\":\"2024-09-22T07:54:17Z\",\"progress\":\"0/0\",\"message\":\"Failed to acquire the synchronization lock. requested configuration is invalid: cannot get LockName for a Sync of Unknown type\",\"conditions\":[{\"type\":\"Completed\",\"status\":\"True\"}],\"artifactRepositoryRef\":{\"default\":true,\"artifactRepository\":{\"archiveLogs\":true,\"gcs\":{\"bucket\":\"loops-argo-testing-logs\",\"serviceAccountKeySecret\":{\"name\":\"loops-gcs-artifacts-sa\",\"key\":\"sa.json\"}}}},\"artifactGCStatus\":{\"notSpecified\":true}}}"}
{"error":"failed to archive workflow: ERROR: duplicate key value violates unique constraint \"argo_archived_workflows_pkey\" (SQLSTATE 23505)","key":"argo/synchronization-wf-level-ww7cf","level":"error","msg":"failed to archive workflow","time":"2024-09-22T07:54:17.628Z"}
{"level":"info","msg":"Queueing Failed workflow argo/synchronization-wf-level-ww7cf for delete in 1h0m0s due to TTL","time":"2024-09-22T07:54:17.637Z"}
{"level":"info","msg":"Queueing Failed workflow argo/synchronization-wf-level-ww7cf for delete in 55m20s due to TTL","time":"2024-09-22T07:58:57.303Z"}

Logs from in your workflow's wait container
can't access them

v3.5.8

Followed the steps described in here: https://argo-workflows.readthedocs.io/en/latest/synchronization/#synchronization

You're using v3.5.8 but reading the docs for latest. Use the docs for your version instead: https://argo-workflows.readthedocs.io/en/release-3.5/synchronization/#synchronization
The semaphores array is new in 3.6 per #13358, in 3.5 there is only semaphore. The error is therefore correct in 3.5 as you did not specify a valid synchronization type.

[x] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.

Version(s)
v3.5.8

You also checked this box -- which is required -- but don't appear to have tested :latest nor explained why. This syntax does work on :latest.
This was also posted on Slack, where a thread just above had the same error


Fiat orders  has no information in the data field

Good morning, I am trying to have the deposits and withdrawals that I have made in my account and in the data field it does not show any type of information, and it's okay to say that if I have deposits
Request
LinkedHashMap<String,Object> parameters = new LinkedHashMap<>();
parameters.put("transactionType", "0");
parameters.put("beginTime","1609477200000");
parameters.put("endTime", ""+new Date().getTime());
String result = spotClient.createFiat().orders(parameters);
Response
{"code":"000000","message":"success","data":[],"total":0,"success":true}
Please what could be happening?

This library is able to send the request and get response,  so it's not an issue from this library.
Please feel free to open a topic at dev.binance.vision,  or get help with customer support regarding the fiat transaction.


Added url validation for aws metadata endpoints in aws external account

This PR adds validation for all the AWS metadata endpoints used in aws_external_account_credentials to match the new changes in the AIP.

The test failure here looks like an unrelated problem, so I'll go ahead and merge this.


Fixing Bad Sed For Updating Toran_Host

Rogue semi colon was preventing Toran_Host from updating correctly.

Hi !


main: test

Having a meta-annotation using @Column and the @Column itself brings undefined behavior, and only one annotation (the one that does not define the custom value converter) gets used here.
Merging annotations was considered when implementing meta-annotations, but it is also fragile and non-intuitive, so we just pick one annotation and go with it.
It is strongly recommended to only use one of the (meta-annotation, @Column annotation).


Experimental editing commands

Signed-off-by: Darby Johnston<EMAIL_ADDRESS>This PR is an experiment implementing some of the editing commands in #711

Thanks for checking out the changes, if this seems like a good direction I would like to try implementing more of the commands. They seem quite useful and and I wanted to try and resurrect this issue since there hasn't been any activity for awhile.

Closing this PR since it has been superseded by https://github.com/AcademySoftwareFoundation/OpenTimelineIO/pull/1654


--stdin option should also allow passing filename

I'm using ALE to lint files asynchronously from Vim. This uses the --stdin flag to lint the file as it exists in the buffer, which may be different from the file on disk. When using rubocop this approach breaks down when editing a file that matches a configured excluded path or when editing a file in a subfolder that has its own .rubocop.yml.
If we could pass the filename of the code being linted on STDIN this could be alleviated. ESLint, for example, offers --stdin-filename for this purpose.

Expected behavior
excludes and other filename based behavior should be supportable when using --stdin
Actual behavior
--stdin has no way to specify the filename, so no exclusions are applied.
Steps to reproduce the problem
Use this rubocop config:
AllCops:
  Exclude:
    - 'db/schema.rb'

Add a db/schema.rb file with linting errors.
Run rubocop --stdin to lint the contents of db/schema.rb
RuboCop version
Include the output of rubocop -V. Here's an example:
$ rubocop -V
0.47.1

I think this is already working. My test case:
 $ cat .rubocop.yml
AllCops:
  Exclude:
    - 'test.rb'
$ cat test.rb
3 = 3
$ cat test.rb | rubocop --force-exclusion --stdin test.rb
Inspecting 0 files

0 files inspected, no offenses detected
$ rubocop --force-exclusion test.rb
Inspecting 0 files

0 files inspected, no offenses detected
$ rubocop test.rb
Inspecting 1 file
E

Offenses:

test.rb:1:3: E: unexpected token tEQL
(Using Ruby 2.1 parser; configure using TargetRubyVersion parameter, under AllCops)
3 = 3
  ^

1 file inspected, 1 offense detected

That's right. The --stdin option takes a file name argument, but this is not documented in the manual or in the output from rubocop --help.

Thanks for the clarification. I verified this works. I took a quick look at how to add this information to --help output but wasn't sure.

Let's keep the issue open until we have updated the documentation.

This can be closed since we have updated the documentation. CC @jonas054


Add jwt issuer configs to config catalog

Fixes https://github.com/wso2/docs-apim/issues/1316

@ChamodDamitha , please note the comment that I added and also please make sure to pull my changes which are in your Fork to your local repo when addressing the review comment so that my changes do not get deleted.

@ChamodDamitha , please note the new review comments.


[Backport] NETOBSERV-922 - Flaky topology data

Backport of https://github.com/netobserv/network-observability-console-plugin/pull/301

So @jpinsonneau should we close this one if it's not a release blocker?

yes @jotak, it seems the fix doesn't cover everything so let's close the backport and skip the release for this one


Migrate to Swift 4.0

Thanks for sharing this work! This PR is for informational purposes. I haven't done any critical thinking about the appropriateness of this resolution of the lone migration issue, so I'm not going to worry about signing a CLA right now. Please close the PR as soon as you're ready.
Description
This PR migrates the repo to Swift 4. It's a breaking change, so I've bumped the major version number. I've done my best to update docs to reflect both version changes.
Motivation and Context
There's no logged issue at this time of writing, but the framework is broken in Swift 4. reference is a Substring, and compilation fails here with
Cannot subscript a value of type '[String : Character]' with an index of type 'Substring'
How Has This Been Tested?
Running swift test still fails for me, but it's claiming "method 'defaultTestSuite' was used as a property; add () to call it", indicating swift test is running Swift 3, even though I've used xcode-select and verified swift --version indicates Swift 4. There is probably something I'm missing causing it to test with Swift 3.
In an Xcode project from swift package generate-xcodeproj, the existing tests pass after this migration to Swift 4. Major Input depends on [swift-html-entities] and has successfully migrated to Swift 4 using these changes.
Checklist:

[ ] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

@rlwimi Thanks for looking into this.
On the running in Swift 3 issue, this is due to the Package manifest being in Swift 3 syntax instead of Swift 4 syntax. swift test looks at Package.swift and builds the source code in either Swift 3.2 or Swift 4 mode depending on the contents of the file.
I'll open an issue to track the Swift 4 migration work.

Aha! Thanks for the explanation and pointers, @youming-lin!

I did some testing and uploaded a Swift 4 branch here: https://github.com/IBM-Swift/swift-html-entities/tree/swift-4
With this change the source code will only compile on Swift 4 toolchain, in Swift 4 mode. Will merge once Swift 4 GAs and we decide if we want to add #if statements to support 3.1 backward compatibility.

I have merged in changes to support Swift 4. As we have decided to support both 3.1.1 and 4.0 to maintain backwards compatibility, I've added a<EMAIL_ADDRESS>that is only used by Swift 4 and added Swift version compiler checks in the source code.


OpenEphysBinaryRawIO: Fixing ttl multichan

Addressing #1437.
Currently, all the logic in the events parser for OpenEphys data assumes that there is a single stream of events (simply positive or negative states), and it breaks down when acquiring multiple digital signals at once (states having different absolute values for different channels).
This is a simple fix that looks for rising and falling edges separately for each of the digital channels.
Add simple testing relying on existing test data, which fails before the fix and passes afterwards.

Thanks @vigji! Looking great!

Great, let me know if there's anything needed before merging!


fix: wearables ab conversion improvements (v3)

Changes that will be addressed by this PR:

[x] Non-used skeleton will be stripped from each non-body wearable, saving many transform/gameObjects instantiation. This will improve wearable loading hiccups.

[x] Wearable textures will be clamped to a smaller size. Now all the wearable textures are 1k-2k in size, occupying 1.5mb or more in raw bytes. This will improve loading hiccups and wearable load times.

Updating master in PR

This PR was behind of master branch a lot, the AB Converter system in master had already changed several classes and implementations, so it took a while to adapt this PR.
Added visual testing step to wearables ABs dumping process

commits history at: https://github.com/decentraland/explorer/pull/1066


Target Powershell 5.0

Add support to emit Write-Information to the logs

Hi @SharpeRAD, my company is using Cake.Powershell to run some Powershell scripts as part of our build process. We are targeting PS 5.0, and made this PR in order to get calls to Write-Information written to Cake's logger.
I don't know if/when PS 5.0 support was planned, but wanted to give a heads up.

Merged :+1:


Clarify how to unwatch a repository.

Why:
Closes: #29082

What's being changed (if available, include any code snippets, screenshots, or gifs):
Extended an option for clarity.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

Thanks for the issue and PR @ObjectOops. I'll get this triaged for review.


removeEventListener is not working

react-native: "0.63.3"
react-native-applovin-max": "1.1.4"
A subscription.remove method should be called in addEventListener and removeEventListener.
const addEventListener = (event, handler) => {
  let subscription = emitter.addListener(event, handler);
  const currentSubscription = subscriptions[event];
  if (currentSubscription) {
    currentSubscription.remove();
  }
  subscriptions[event] = subscription;
};

const removeEventListener = (event) => {
  if (subscriptions[event]) {
    subscriptions[event].remove();
    delete subscriptions[event];
  }
};

Thanks for reporting this. It has been fixed in 1.1.5.


Replaced youtube_dl with yt-dlp

Closes #17
Replaced youtube_dl with yt-dlp to download videos much faster and also made relevant changes in README.md

Can you install it via pip instead? Would like to not add extra friction

done

I had to remove the reference to youtube_dl_log to get this working on line 7 in /Users/meow/Library/Python/3.9/lib/python/site-packages/yt_whisper/cli.py :
Traceback (most recent call last):
  File "/Users/meow/Library/Python/3.9/bin/yt_whisper", line 5, in <module>
    from yt_whisper.cli import main
  File "/Users/meow/Library/Python/3.9/lib/python/site-packages/yt_whisper/cli.py", line 7, in <module>
    from .utils import slugify, str2bool, write_srt, write_vtt, youtube_dl_log
ImportError: cannot import name 'youtube_dl_log' from 'yt_whisper.utils' (/Users/meow/Library/Python/3.9/lib/python/site-packages/yt_whisper/utils.py)

Thanks for this pull request! The download is sooo much faster

Thank you for this! Makes downloads much much faster ❤


Add more Python version support

Everything should work from 3.8 to 3.10, we just need to update tox config to validate support.

Done in 0.6.0 release


[HOLD for payment 2022-03-08] Extra space is being added in last name on request call page - reported by @thesahindia

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Navigate to Request a call RHN

Expected Result:
There should be no extra space between boxes
Actual Result:
There is an extra white space between name and contact info
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.1.35-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43995119/152286063-d52daf2b-190a-40ed-87f6-5053eab74b35.mov

Expensify/Expensify Issue URL:
Issue reported by: @thesahindia
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1643145163426700
View all open jobs on GitHub

Triggered auto assignment to @luacmartins (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Proposal
On line 211 we need to make it (lastSpaceIndex + 1) to get the expected output, because without the +1 we are skipping the space
https://github.com/Expensify/App/blob/9d6e07a0d3bb298d7edba16824efb95afc94f280/src/pages/RequestCallPage.js#L209-L212

Triggered auto assignment to @kadiealexander (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Upwork link: https://www.upwork.com/jobs/~017f7581c4c2006a85

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (Exported)

Current assignee @luacmartins is eligible for the Exported assigner, not assigning anyone new.

Interesting issue.
@thesahindia
Why don't we use the first name and Lastname from personal details? We can fall back to displayName.

Proposal
myPersonalDetails prop has firstName and lastName as well. So my proposal is to replace following lines of codes by:
https://github.com/Expensify/App/blob/9d6e07a0d3bb298d7edba16824efb95afc94f280/src/pages/RequestCallPage.js#L195-L216
    getFirstAndLastName({login, displayName, firstName, lastName}) {
        let fName;
        let lName;

        if (Str.removeSMSDomain(login) === displayName) {
            fName = '';
            lName = '';
        } else {
            fName = firstName;
            lName = lastName;
        }

        return {fName, lName};
    }

Why don't we use the first name and Lastname from personal details? We can fall back to displayName.

@parasharrajat, checked the code and didn't find any reason. So yeah I guess we can use it.

:eyes:

Thanks for the proposal guys. I like @sobitneupane's proposal lets go with that. Don't forget to fall back to displayName.
cc: @luacmartins
:ribbon: :eyes: :ribbon:  C+ reviewed

Thanks for the input @parasharrajat! I agree that @sobitneupane is better.

Sorry, I accidentally unassigned everyone 🤦 @sobitneupane please apply to the job in Upwork!

Sorry, I accidentally unassigned everyone facepalm @sobitneupane please apply to the job in Upwork!

Applied.

📣 @sobitneupane You have been assigned to this job by @kadiealexander!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Sent you an offer in Upwork @sobitneupane, thanks!!

Sent you an offer in Upwork @sobitneupane, thanks!!

Accepted offer. I will be submitting PR before Feb. 11.

The solution for this issue has been :rocket: deployed to production :rocket: in version 1.1.40-2 and is now subject to a 7-day regression period :calendar:. Here is the list of pull requests that resolve this issue:

https://github.com/Expensify/App/pull/7707

If no regressions arise, payment will be issued on 2022-03-08. :confetti_ball:

Paid @sobitneupane!
@parasharrajat and @thesahindia, could you please let me know when you've accepted the contract I just sent, so I can pay you out for C+ and reporting respectively?

@kadiealexander, Done ✅

Everyone is paid! 💰💰💰


BUG Fix usage of $this as closure argument

Fixes issue in https://github.com/silverstripe-labs/silverstripe-sqlite3/pull/24

That's a bit of a sledge hammer approach... Are they not needed?

It's a closure; There's no obligation to provide dummy parameters.


Adding citations for facility location notebook

This PR add a complement of citations for the facility location notebook

Pull Request Test Coverage Report for Build 2088

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 94.951%

Totals

Change from base Build 2086:
-0.4%

Covered Lines:
7896

Relevant Lines:
8226

💛  - Coveralls


godot 4.0.1  videostreamplayer does not play http ogv urls

Godot version
4.0.1
System information
ubuntu 20.0.4
Issue description
i simply create a 2d node and as child a videostreamplayer, then set http://localhost:8080/stream.ogv to "File" and run it.   The ogv stream comes from :
cvlc v4l2:///dev/video0 --no-audio --sout '#transcode{vcodec=theo,vb=800}:standard{access=http,mux=ogg,dst=:8080/stream.ogv}'

It returns: cannot open file ?
Steps to reproduce
run it
Minimal reproduction project
none

The file access system doesn't support network files like this as far as I know, you have to use HTTP or other similar things, the file paths here are strictly filesystem ones, not network

ok, thanks

No problem!


Enable scheduling of critical pods and network plugins on master

Added toleration to DNS, netchecker, fluentd, canal, and
calico policy.

ci check this

Nice!


Incorrect interpolation of discrete labels in the FreeSurfer anatomical segmentation

This issue is in the anatomical processing pipeline of fmriprep.
What version of fMRIPrep are you using?
20.2.1
What kind of installation are you using? Containers (Singularity, Docker), or "bare-metal"?
Singularity container derived directly from Docker hub image
What is the exact command-line you used?
N/A
Have you checked that your inputs are BIDS valid?
Yes
Did fMRIPrep generate the visual report for this particular subject? If yes, could you share it?
Yes, can provide if requested.
Can you find some traces of the error reported in the visual report (at the bottom) or in crashfiles?
N/A
Are you reusing previously computed results (e.g., FreeSurfer, Anatomical derivatives, work directory of previous run)?
No, first run on raw scans.
fMRIPrep log
Can be provided if necessary.
Our T1w scans have a resolution of 1.0x1.0x1.2 mm3 voxel size. Scans are processed correctly, with FreeSurfer resampling the volumes to 1mm isotropic resolution for internal use. fmriprep makes the segmentations conveniently available as *_desc-aparcaseg_dseg.nii.gz and *_desc-aseg_dseg.nii.gz in the fmriprep/subjectID/anat/ folder resampled to match the native resolution of the T1w scan. However, an interpolation method is used that is not suitable for volumes with discrete labels.
On the left an example of the apardaseg_dseg produced by fmriprep. On the right is the original aparc+aseg from the FreeSurfer output.

I agree this is related to #254 - but looks like a legitimate bug we should address. Changing the interpolation should not affect derived outputs (such as CompCor) dramatically.

Is this bug still open?  I think the problem is that you just can't interpolate a file full of integer labels and not get corruption at the edges.  Once solution to this is to convert the 3D label file to 4D, one volume for each label, as a 1.0 or 0.0.  Then interpolate each volume independently.  Then to go back to 3D, set each voxel to the time index with the maximum value for that voxel.  It's time-consuming, but works pretty well.

I don't think so. We're now using nearest neighbor interpolation, but it's worth confirming...


Update LICENSE

I accept having my contribution relicensed to comply with DRF licensing.

:+1: looks good to me

Thanks @ryansb :+1:


How to use mysql streams?

Does this library provide a method for accessing MySQL stream similar to mysql2 adapter?
Sources:
Mysql2 Adapter - https://github.com/brianmario/mysql2#streaming
Mysql documentation - https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-implementation-notes.html

you can access the jdbc connection from your AR connection: connection.jdbc_connection
from there you could create a statement and set stmt.setFetchSize(Integer.MIN_VALUE)
not sure whether where we should add that since we do not emulate the mysql2 API that much
client.query("SELECT * FROM really_big_Table", :stream => true) we simply do not have that
as AR-JDBC implements AR API: connection.exec_query do you feel that could be made streamable?


Add preload attribute to all video tags.

Feature Description
To improve performance of videos, all video tags should have the preload attribute added.

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

Original comment from @dvoytenko - https://github.com/google/web-stories-wp/pull/720/files#r397962369


How can I update the clipboard icon and the code block style?

Checklist

[x] I have read the newlest tutorials and know the correct effect of the functional design.
[x] There is no similar question on existing issues (including closed ones).
[x] I have tried to find the answer on Jekyll Forum and StackOverflow.
[x] My question is based on the latest code of the master branch.

Description

I use the jekyll-theme-chirpy gem. After the update to version 4.3.1, the clipboard icon for copying code is not rendered as it should (especially in dark mode). It is placed at the left of the code block instead of at the right. The code language and the "status bar" (see below for comparison) are not shown either:

How can I get the code block style in the official version (see below)?

Thank you in advance.

Thank you. I do in effect have some leftover files since forking jekyll-theme-chirpy (having switched over to chirpy-starter in the meantime). Cloning chirpy-starter as instructed in the readme solves the styling issue. I will update my repo. Closing this issue.


[Bug]: Unable to search for items when creating data source binding

ODC version
ODC 4.2.4
OB version

What happened?

Unable to search for items when creating data source binding
What did you expect to happen?
Search function works
How can we reproduce it (as minimally and precisely as possible)?
Follow what happened
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit b02e6b6ad04d979bd9631bc30a97ac70a3010310
------
xiaokang
Thu Mar 7 15:02:34 2024 +0800

pass


ADD: Passing the vault name on resharing

At the moment when re-sharing a vault to a new device, the name New Vault # gets inserted. Please implement that the vault name of the re-shared vault gets passed to the new device.

fixed at https://github.com/vultisig/vultisig-android/pull/442](https://github.com/vultisig/vultisig-android/pull/442)


RET-5444

Jira link

See PROJ-XXXXXX
Change description

Testing done

Checklist

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] Does this PR introduce a breaking change

Maybe add unit test(s) for the changes?

changes are already covered by existing UTs

Maybe add unit test(s) for the changes?

changes are already covered by existing UTs

@LahiruOshara the tests that are in place don't actually cover it properly as the test that is in place is just passing in a blank CaseData object. Technically whilst the null checks are covered, it would be better to have a new test where we are passing in actual data and verifying the object we pass into Tornado


Cancel Kubernetes Job when CancelScript is called

Background
Currently, when a script being executed via Kubernetes Job is cancelled (via the CancelScript RPC call), we don't cancel the Job.
Results
In the RunningKubernetesJob, we now attach a cancellation callback to the scriptCancellationToken, so we are notified when the cancellation token is cancelled.
This callback spawns a background task which calls the DeleteJob method in the KubernetesJobService. This marks the job for termination, which triggers a SIGTERM signal, allowing for graceful shutdown before the termination command is sent 30s later (SIGKILL).
I have adjusted the code so that the scriptCancellationToken only cancels the job, not the monitoring of the job (which will now stop watching when the job is deleted)

Shortcut story: [sc-67104]
How to review this PR

Quality :heavy_check_mark:

Pre-requisites

[ ] I have read How we use GitHub Issues for help deciding when and where it's appropriate to make an issue.
[ ] I have considered informing or consulting the right people, according to the ownership map.
[ ] I have considered appropriate testing for my change.

After advice/discussion with @cailyoung, I have changed it again so that the job is suspended (which tells the control plane to terminate the pods), then we delete the job


Unnecessary dependency on "art.scnassets"?

error: Build input file cannot be found: 'art.scnassets'

Removing the file corrects this issue.


Imrpove debugging of tests using click runner

/packit test

/packit test

Rebased / fixed the typo. I'll merge soon.


YoloV7 serverless support for automatic annotation

It would be great to have support for YoloV7 object detector for automatic annotation. I already created such feature using ONNX backend. Please let me know if it is needed so other can also use it. How can I provide PR for it?

Hi, thank you for asking! Yes, it would be great to have this model available in CVAT. Please follow the contribution guide here. Basically, you just need to create a PR and follow the template. We expect most PRs to include tests and documentation, but in case of models, we don't have a relevant test suite now, so it's not needed.

#5552


chore(release): update release 1.0.0-alpha.4

:tada: This PR is included in version 1.0.0-alpha.5 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

GitHub release
v1.0.0-alpha.1

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.4 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:


Start adding labels for a11y

This change adds an option to specify colour labels which a screen reader is able to use to read out the colour. Without this the only thing the screen reader gets is the hex code read out.
If you're happy with this proposal to add labels to the colours I can update the other components to match.
I've also made the role of the swatch a button so it at least tells the user it is clickable. I think ideally it would be a radio group and radio button but that would require further css changes.
Starts work on #678

This is great changes and I hope this PR will be merged.


RPC client refactoring plan

#2585 and #2586 solved the problem of excessive client dependencies, now we can move on to other topics. We already have #1967, but that's not the only problem we have, even though it sets the main direction of RPC client evolution. But we have other problems as well:

Packaging.
Unfortunately, client and server are not a very good package names. We also have data types split between request, response and response/result. All of this was done quite a long time ago and can be improved to simplify using the client. But it's controversial at the same time, because it's a breaking change.
smartcontract.Parameter type
While it's very natural for the RPC protocol we have is not very usable without an ability to convert convert from/to regular Go types (like toStackParameter in NeoFS).
Too many things happening in the Client
Explained in #1967, we have both simple API requests there as well as higher-order functions like NEP17Symbol or MultiTransferNEP17.
Missing wrappers for native contracts
While NEP-17 functions are present, one can't easily do vote in NEO contract, for example.
Contract-specific clients can't be created easily
Backend code mostly wants to work with some particular contract and while it can implement NEP-17 or other standard it's also very likely to have some task-specific methods that aren't easily accessible currently.
Missing some wait-loop helpers
State-changing requests normally produce a transaction and the client then needs to wait for the result. While the best way to do that is via subscriptions, it can also do polling and currently it's out of client's scope.
State-changing functions that create transactions internally don't return ValidUntilBlock.
Which means that the client doesn't know how long to wait for the transaction to be accepted (or not).
Some methods have "create tx, but don't send" methods, some don't
There has to be some uniformity there, proper client needs both.
Wrappers don't usually provide a way to test-exec something
Any state-changing method should be available for test execution as well as creation of a complete transaction and its transmission.
Wrappers don't provide any easy way to perform historic calls.
Again, any method can be invoked with some old state and this should be possible to do easily without moving a layer below (calling generic InvokeFunctionAtHeight or similar).

What I'd like to do is to concentrate first on the functionality we have, not expanding it in the first phase. At the same time breaking changes are better be done eariler, therefore the plan that I have in mind is:

Rename rpc/client to rpc/rpcclient, rpc/server to rpc/rpcserver and merge request/response/result into neojson package. So it'll be like neojson.Request, neojson.Response, neojson.Invocation. I'm interested in opinions on this though.
Move script creation routines out of the client to the smartcontract package. It's there exactly for this purpose.
Provide smartcontract.Parameter helpers and add client APIs that will use bare Go types for invocations.
Strip the client from the methods not directly related to the original RPCs. Move nep11 and nep17 functions to the respective packages that are to be initialized with the Client and token contract hash. Move functions for native contracts we have into packages of their own reusing nep17 where possible. This will affect all clients, unfortunately. I'd like to keep old APIs available for at least one release along with the new ones, but I'm not sure it'll be possible to do this due to potential package import cycles.
Make APIs consistent wrt the abilities they provide for different classes of functions. It should be possible to create a script for some invocation, create a transaction for it and send it. Or do all of this with a single call.
Extend native contract packages to cover all functions needed. This can be done in phases, we don't need all of the native contracts at once, but we can start with NEO and Oracle and then extend the set when needed (Notary is a notable target as well).
Provide test-exec abilities to all wrapped contract-specific calls.
Either a set of new methods (nep17.Transfer vs nep17.TestTransfer) or some interface implementation (nep17.Transfer but with modified underlying client or setting). But it's likely to be the first one as test executions provide a lot of additional data that might be useful for the client in various circumstances.
Provide historic calls for all wrapped calls.
Via an interfaced lower-layer client that will be initialized with some state definition, likec := client.New(...)
hi := c.HistoricInvoker(hash/block)
hnep17 := nep17.New(hi, token_hash) // Instead of the usual `nep17.New(c, token_hash)`
out := hnep17.Transfer(...)

Add wait loops.
Only after all of this we can think of extending compiler (I think bindings data can be used as the basis) to generate additional data which then will be used to automatically provide wrappers for contracts.

Unfortunately, there will be a lot of breaking changes, so I'm interested in opinions on how can we make this transition period less stressful for people. And in general, what can we do more or less.

We're at 4-6 at the moment, 4 is not yet completed (notary, nns, tokeninfo), yet at the same time we already have a nice contract coverage for 6 and at least partially established APIs for 5 (Method (that sends transaction), MethodTransaction (signs, but not sends), MethodUnsigned (not signed transaction returned)).

We're done up to number 6 now. We don't have a wrapper for StdLib or CryptoLib contracts, but I doubt these wrappers can be useful, these contracts are just libraries to be used by other contracts. We also don't have for the Ledger contract, but all of what it does is accessible via regular RPC API, no point in wrapping it. All the other contracts are completely available.
As for 7. We have the concept of TransactionCheckerModifier in the Actor and it probably solves the problem. It's easy to do any kind of checks in this callback before transaction is created/sent. So I this it's covered as well, but @alexvanin and @fyrchik please tell me if I'm wrong.
We also have full historic abilities in Invoker for 8 (and any reader API building on top of it). Actor does not have it, but it's made for state-changing calls, so it'd be strange for it to try creating transaction that is run against the old state. If any test-calls are needed they're available via Invoker. Seems to be OK to me.
So we can move on to canonical wait loops of 9 and then a separate issue for 10.

I've created #2704 and #2705 to simplify tracking these specific things that we still have left. This issue can be closed, everything else is done.


PaginatedDataTable: Improved error message when rowsPerPage is not 10, 20 or 50.

Currently the following error message is thrown when rowsPerPage is not set to availableRowsPerPage:
The following assertion was thrown building PatientDataTable(dirty, state: _PatientDataTableState#d2ed0):
Assertion failed:
..\…\material\paginated_data_table.dart:100
availableRowsPerPage != null && availableRowsPerPage.contains(rowsPerPage)
is not true

Proposed to update the error message to:
rowsPerPage is set to a value that is in availableRowsPerPage. By default, rowsPerPage can only be 10, 20 or 50. You can create a custom set of allowed values by setting availableRowsPerPage

Hi @fringefilmsoz
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you


Cleaner action fails to cleanup CRDs with conversion webhooks during kyma undeploy

Description
Looks like the cleaner action executed last fails as the conversion webhooks for some CRDs (Functions, Api-rules) got already deleted  earlier
Expected result
Cleaner should be able to cleanup all CRDs w/o conversion webhooks.
Actual result
Cleaner action fails
Steps to reproduce
1.) Deploy Kyma
kyma deploy -s main
...
- Kyma deployed successfully!

Kyma is installed in version:	main
Kyma installation took:		0 hours 5 minutes

2.) Create some functions and api rules
3.) Undeploy Kyma
kyma undeploy

X Component 'cleaner' failed. Retrying...
conversion webhook for gateway.kyma-project.io/v1beta1, Kind=APIRule failed: Post "https://api-gateway-webhook-service.kyma-system.svc:443/convert?timeout=30s": service "api-gateway-webhook-service" not found

X Component 'cleaner' failed
All attempts fail:
#1: conversion webhook for gateway.kyma-project.io/v1beta1, Kind=APIRule failed: Post "https://api-gateway-webhook-service.kyma-system.svc:443/convert?timeout=30s": service "api-gateway-webhook-service" not found
#2: conversion webhook for gateway.kyma-project.io/v1beta1, Kind=APIRule failed: Post "https://api-gateway-webhook-service.kyma-system.svc:443/convert?timeout=30s": service "api-gateway-webhook-service" not found
#3: conversion webhook for serverless.kyma-project.io/v1alpha2, Kind=Function failed: Post "https://serverless-webhook.kyma-system.svc:443/convert/functions?timeout=30s": service "serverless-webhook" not found
#4: conversion webhook for serverless.kyma-project.io/v1alpha2, Kind=Function failed: Post "https://serverless-webhook.kyma-system.svc:443/convert/functions?timeout=30s": service "serverless-webhook" not found
#5: conversion webhook for gateway.kyma-project.io/v1beta1, Kind=APIRule failed: Post "https://api-gateway-webhook-service.kyma-system.svc:443/convert?timeout=30s": service "api-gateway-webhook-service" not found

X Undeploying Kyma

Deleted Components: 15/16
Could not delete the following components:
- cleaner

Error: kyma undeployment failed

Troubleshooting
Both apirule.gateway.kyma-project.io and function.serverless.kyma-project.io have introduced  new api versions and conversion webhooks in kyma 2.6.
Could be related
https://github.com/kubernetes/kubernetes/issues/71925

When I try cleaning the CRDs manually via kubectl I am able to do it
kubectl delete crd apirules.gateway.kyma-project.io
customresourcedefinition.apiextensions.k8s.io "apirules.gateway.kyma-project.io" deleted

kubectl delete crd functions.serverless.kyma-project.io
customresourcedefinition.apiextensions.k8s.io "functions.serverless.kyma-project.io" deleted

Issue could be related to the "drop finalisers" code-block in the cleaner reconciler:

https://github.com/kyma-incubator/reconciler/blob/main/pkg/reconciler/instances/cleaner/pkg/cleanup/crd.go#L93
https://github.com/kyma-incubator/reconciler/blob/main/pkg/reconciler/instances/cleaner/pkg/cleanup/crd.go#L116

This code drop the finalisers from any CRs which were left over after deleting all Kyma components. The purpose behind this code is to unblock the deletion process of the cluster by Gardener (Gardener got blocked sometimes when the CRs had finalisers which were already wiped out before).


Cannot download the model

It's locked behind a chinese website (Baidu) which I cannot gain access to without being Chinese

You can download the model using Google Drive hyperlink rather than Baidu Cloud. Their contents are the same.

Hi, the Google Drive link that was provided only contains the checkpoint not the model. Is there a way share the link for the model? Thank you

@HeylonNHP You can Download the Model from here https://drive.google.com/file/d/1CmDMypSlLM6EAvOt5yjwUQ7O5w-xCm1n/view

@RNubla Thank you! I misunderstood his meaning before. I will add this link to README.

@CM-BF No problem!


.alpha based on current health

Describe your problem here.
so i was wondering, is something like  setProperty('funny.alpha', math.ceil(getProperty('health') * 0.5) ); is even possible?
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

oh, i just removed math.ceil and it worked almost perfectly, but i'd like to make it reverse, image goes less transparent with more health player got

oh, i did it.


🐛 Bug Report: httpAuth issued cookies do not support split backend deployments

📜 Description
We deploy our techdocs-backend on a separate backend and observed that static asset requests that require cookie auth fails due to the cookie failing to be set on the browser. Here's my diagnosis of the issue:
In the following code a cookie is being set against the request origin header host:
https://github.com/backstage/backstage/blob/96b23786f648ea28c2ab81d4888c46ab8bbd907b/packages/backend-app-api/src/services/implementations/httpAuth/httpAuthServiceFactory.ts#L232-L242
In our use-case our frontend is being served from backstage.company.com while our techdocs backend is served from backstage-techdocs.company.com. Line 235 above is prioritizing the request origin so the cookie is being set for backstage.company.com. The browser ends up rejecting this as misconfigured since the request is against backstage-techdocs.company.com/cookie but the cookie is being attempted to set against backstage.company.com.
I believe the solution is to just reverse the order of precedence to prefer the external base URL as determined by the DiscoveryService:
const externalBaseUrl = new URL(externalBaseUrlStr ?? origin);

This should guarantee the cookie will always be set against the target domain (instead of the source) but wanted to run this by the maintainers first since there have been a couple auth changes in flux recently. Happy to open a PR fix if this solution makes sense 🙂
👍 Expected behavior
Issued cookies should target the correct backend domain
👎 Actual Behavior with Screenshots
Issued cookies target the request origin and is rejected by the browser
👟 Reproduction steps

Deploy the techdocs-backend plugin on a separate backend with a different host address
Cookie auth for static assets fails when requesting techdocs

📃 Provide the context for the Bug.
No response
🖥 Your Environment
Backstage v1.25.2
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Yep I think you are quite right. Happy to discuss further and validate in a PR


bug: incorrect language tag for JavaScript

In many of the .mdx files containing the documentation, the JavaScript code snippets have been marked with the language tag JavaScript as follows:

This tag is incorrect and should be replaced by javascript. These incorrect language tags lead the build by Shiki to not be rendered as JS, but rather plaintext:

A simple global search and replacing [triple backticks]JavaScript with [triple backticks]javascript should fix the same.

I can take this issue up if the maintainers approve.

just a quick note here that the majority of these are in src/content/contributor-docs, which have to be fixed in the p5 repo and then re-imported here with the build contributor docs script. i see a few in src/content/tutorials, which can be fixed directly in this repo.

For those in contributor docs, we'll fix in the p5.js repo.

Hi, I saw this was inactive for some time, so I made a PR. I also noticed that sometimes 4 backticks were used instead of 3 to define code blocks. I fixed both errors, hope it helps 🙈
https://github.com/processing/p5.js/pull/7314


Contrasting coding styles with chromium/base

I've observed one thing, the chromium style guide has censored a lot of modern C++ features. This repository chose to go all together in another direction. For instance shared_ptr is banned in the chromium's codebase.
https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++-features.md#Shared-Pointers-banned
Please clarify if any style guide exists for this project. Looking forward to contribute to this project

Please refer to Introduction documentation page.
TL;DR - this project adheres to the Google Style Guide but does make exceptions for things that are now implemented in the STL and will use them instead of the custom solutions (unless some functionality cannot be achieved without writing a custom counterpart). For example: for a long time Chromium's code didn't have C++17 so it had to use its own custom base::Optional type. Then it switched to absl::Optional. This library aims to have as few external dependencies as possible and there is an implementation of optional in STL now, so we simply use it. Similarly with std::shared_ptr vs scoped_refptr.
NOTE: scoped_refptr have a few more usages in //base, but I decided to not go for them here, so for now there is no need to port it/reimplement it here.

Thanks for the clarification. It is true that chromium's //base has quite a tech debt owing to modern C++ and hence they continued with the in-house implementation.


Okta rate limit

e0000047 => api call exceeded rate limit due to too many requests.

Closing in favor of #6748


libzbc: 5.12.0 -> 5.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/westerndigitalcorporation/libzbc/releases.
meta.description for libzbc is: "ZBC device manipulation library"
meta.homepage for libzbc is: "https://github.com/westerndigitalcorporation/libzbc"
meta.changelog for libzbc is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.13.0 with grep in /nix/store/bas4m4iw6lhgxbiwx57jqx4g5zagrbfq-libzbc-5.13.0
found 5.13.0 in filename of file in /nix/store/bas4m4iw6lhgxbiwx57jqx4g5zagrbfq-libzbc-5.13.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
libzbc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bas4m4iw6lhgxbiwx57jqx4g5zagrbfq-libzbc-5.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libzbc https://github.com/r-ryantm/nixpkgs/archive/ada913cae5a2b4edd97bb2ffea740b344e9bac8d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bas4m4iw6lhgxbiwx57jqx4g5zagrbfq-libzbc-5.13.0
ls -la /nix/store/bas4m4iw6lhgxbiwx57jqx4g5zagrbfq-libzbc-5.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

libzbc

Maintainer pings
cc @zseri for testing.

this pretty much works, but for the bump autoconf-archive should be dropped.


[Snyk] Upgrade @fortawesome/fontawesome-free from 6.2.0 to 6.4.2

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @fortawesome/fontawesome-free from 6.2.0 to 6.4.2.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 4 versions ahead of your current version.
The recommended version was released 2 months ago, on 2023-08-02.

Release notes

Package name: @fortawesome/fontawesome-free

6.4.2 - 2023-08-02Change log available at https://fontawesome.com/docs/changelog/

6.4.0 - 2023-03-27Change log available at https://fontawesome.com/docs/changelog/

6.3.0 - 2023-02-07Change log available at https://fontawesome.com/docs/changelog/

6.2.1 - 2022-11-15Change log available at https://fontawesome.com/docs/changelog/

6.2.0 - 2022-08-30Change log available at https://fontawesome.com/docs/changelog/

    from @fortawesome/fontawesome-free GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Builds successfully and looks OK on local build. Merging.


Custom Streaming Function (Excel) - Invocations not firing with quick changes

I have a use case where one of my custom formulas fires an API POST to write data to our backend database.
With this formula, if an auto send formula parameter is set to true, the formula execution will directly invoke the API call. If the parameter is set to false, we hold the value and send later, with a button click. For the deferred calls we utilize the invocation's setResult() method to keep itself current - so this is a streaming function.
We are finding that if we have a large number of these formulas in a sheet, and we set the parameters to one value, and quickly set the parameters back to the original value our backend data gets out of sync. This is because Excel fires the invocation for the first change, but does not trigger the reverting back invocation and seemingly uses its own cached results.
In this scenario, our backend API is only called for the first wave of changes, and is never called on the second wave (the reverting back) of changes.
Simple Example: where the first excel argument/parameter is the value to send to the database, and the second parameter is the auto send flag)

Existing/original state of the formula with its parameter values:
custom_function("value 1",true)

First wave of changes:
custom_function("value 2, true)

Second wave (reverting) of changes:
custom_function("value 1, true)

It should be noted that doing this scenario with just one formula, the process works as expected because both executions seem to fire new invocations. It is only when I have a sheet that has the 1,000 formulas linked to one another in a cascading fashion does Excel not fire distinct invocations and instead seems to use its own cached value to get back to the reverted values (the reversion happens immediately, and console logs prove that the second invocation is never fired).
Given this behavior, it seems like there should be a way for me to tell the particular invocation(s) to not use a cached value and/or force it to fire unique invocations on every change.

This is a problem with the platform rather than the documentation for the platform, so I'm going to try and transfer it to the office-js repo.


Tweaks for those migrating from Ritwick's extension

Although these are my current plans, this is still Open For Discussion and comments are welcome (for thoughts) and 👍 for those in support

@ritwickdey has kindly archived his extension and is redirecting people to my fork here. Now more people will be migrating I want to try and make the process easier.
The key points are:

Add liveSassCompile.settings.showOutputWindow as a deprecated fallback
When a liveSassCompile.settings.showOutputWindowOn setting is not present I will check for a true or false value of liveSassCompile.settings.showOutputWindowOn

When true I will use the Information setting
When false I will use the Warning setting (which will only output on errors or warnings)
This option will be marked as deprecated with a note to use the new setting. However, it will likely never be removed as people could be migrating in the next major release (and beyond)

The autoprefix setting needs to accept null and will act like it's false

Tasks

[x] Allow fallback to showOutputWindow when showOutputWindowOn isn't present
[x] Allow null in autoprefix setting
[x] Update documentation to note these changes

I have code changes ready to go, just waiting a day or two before applying in case anyone has feedback

No objections so I'm pushing these two tweaks


feat(tee): add Prometheus metrics to the TEE Prover

What ❔
This commit adds Prometheus metrics to the TEE Prover. Specifically, the following metrics were added:

Waiting time for a new batch to be proven
Proof generation time
Proof submitting time
Network error counter
Last block number processed

Why ❔
Setting up Prometheus metrics is a prerequisite before rolling them out to staging and testnet environments. Prometheus metrics are useful for monitoring, providing valuable insights into the running system.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.

@popzxc @haraldh Please review. Hopefully, this should be an easy one. I'm not sure if there's an easy way to test it before rolling it out to staging/testnet.


Fix no empty input check in newSignatureFromCommitline for gogit version

Fix #28840
In signature_nogogit,go:

In signature_gogit.go:

Can you add some tests?

How to add test in both nogit and gogit version? 🤔

Have you tested Linux kernal?

How to add test in both nogit and gogit version? 🤔

It seems you have to changed twice at the moment.

Have you tested Linux kernal?

Yes. It works well.

It seems you have to change them twice at the moment.

A copy from signature_gogit_test.go is allowed? But seems no better method.

It seems you have to change them twice at the moment.

A copy from signature_gogit_test.go is allowed? But seems no better method.

You can copy first and then try to extract a function

I understanded now.
Just remove //go:build gogit in the test.go, then we can test it in both gogit version and no gogit version. 😄

@yp05327 after reading the code again, I think we should rewrite the code. If you don't mind, I could propose a new approach soon.

@yp05327 after reading the code again, I think we should rewrite the code (for both gogit and nogogit). If you don't mind, I could propose a new approach soon.

Never mind. It seems that the old codes haven’t been finished yet. So let’s finish it.


patch: Streamline the docs

Before merging, we need to generate the docs website. So don't merge until I commit those files as well.
Signed-off-by: Vipul Gupta (@vipulgupta2048) <EMAIL_ADDRESS>

@balena-ci I self-certify!


Improve SQL Server write bottlenecks

[ ] Improve Cloud SQL Server single write bottlenecks to improve Forseti Inventory performance
[ ] Break apart the storage class into storage writer (use sqlalchemy core, optimize for fast bulk writes) and the storage reader class, which can remain using ORM as it does today.
[ ] Update inventory and crawler initialization to use the new writer class with a a sqlalchemy engine that maintains a pool of connections shared between threads, and not use a global session object.
[ ] Update the ParallelCrawler class to to not use a global lock on writes and updates.
[ ]  Optimize the writer class to have fewer SQL calls, optimize for bulk writes and few or no updates. Updates should be an exception, and strongly discouraged in code or removed completely (also needed for BigQuery streaming writer eventually).

Additional work completed in PR #3068. Closing issue.


Relay support

The current server can only use a disk source. We need to add the ability to receive a live stream and redistribute it.
This should be relatively straight forward because of the reusable media producer objects. There should be a trait Source so we can switch between disk/net sources on a whim.

Working on this now.

wurks albeit with a few bugs.


Rely on sbt-slamdata and slamdata-predef

Depends on slamdata/sbt-slamdata/pull/16

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@af2bdc7). Click here to learn what that means.
The diff coverage is 57.14%.

@@            Coverage Diff            @@
##             master    #1968   +/-   ##
=========================================
  Coverage          ?   64.87%
=========================================
  Files             ?      380
  Lines             ?    18772
  Branches          ?      225
=========================================
  Hits              ?    12178
  Misses            ?     6594
  Partials          ?        0

Impacted Files
Coverage Δ

frontend/src/main/scala/quasar/sql/CIName.scala
83.33% <ø> (ø)

frontend/src/main/scala/quasar/std/date.scala
96.73% <ø> (ø)

...scala/quasar/physical/couchbase/fs/writefile.scala
0% <ø> (ø)

...main/scala/quasar/physical/marklogic/fs/data.scala
93.28% <ø> (ø)

...ector/src/main/scala/quasar/qscript/Coalesce.scala
86.36% <ø> (ø)

frontend/src/main/scala/quasar/codec.scala
95.4% <ø> (ø)

...n/scala/quasar/physical/couchbase/fs/package.scala
7.27% <ø> (ø)

ejson/src/main/scala/quasar/ejson/jsonParser.scala
100% <ø> (ø)

.../main/scala/quasar/contrib/scalaz/enumeratee.scala
100% <ø> (ø)

...ontend/src/main/scala/quasar/namegen/package.scala
88.88% <ø> (ø)

... and 163 more

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 af2bdc7...06dddeb. Read the comment docs.

@djspiewak Travis appeased and ready for another look.

@drostron What was wrong with the TravisCIPlugin?

@djspiewak When enabled at that level supposedly it was defaulting to Scala 2.10 (due to absent .travis.yml), yet resolving occurred for sbt-slamdata against 2.11 which was failing.

Oh, this is because of using sbt-slamdata in the meta project.  RIP
Just so we don't get confused about the level at which this is being disabled, I would actually move that line to a separate project/build.sbt.  It will have the same effect, but it's a bit more explicit that we're disabling things in the meta project.  As it stands, it looks (especially to someone who doesn't know SBT well) that the travisci plugin is being disabled in the primary project.

Agreed — will do.

Ready


SecHub Windows Client Includes Zip File in Compression, Causing Endless Loop

Situation
When doing a scan for secrets ("secretScan") the SecHub client compresses source code into a zip file. When including "." (the folder you are currently in), the SecHub Linux client successfully excludes the zip file from the compression and works as expected. However, when performing the same action with the Windows SecHub client, the zip file itself is included in the compression, resulting in an endless loop.
Example sechub.json:
{
  "apiVersion": "1.0",
  "secretScan": { "use": [ "myscan" ] },
  "data": {
    "sources": [
      {
        "name": "myscan",
        "fileSystem": { "folders": [ "." ] }
      }
    ]
  }
}

Wanted
It is desired that this bug is investigated and fixed.
Solution
A potential solution could involve checking if the exclude pattern does not work on Windows for some reason. Alternatively, it might be that the temporary zip file on Windows has a different name or extension.

The problem applies only to scan type "secretScan".


dbeaver: 5.0.6 -> 5.1.0

Motivation for this change

Updates dbeaver 5.1.0.

Things done

✔ Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

✔ NixOS

✔ Tested execution of all binary files (usually in ./result/bin/)
✔ Fits CONTRIBUTING.md.

As a side note, #34182 is still open and I will still gladly accept any help in figuring out how to build this using the source release.

@GrahamcOfBorg  build dbeaver

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: dbeaver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: dbeaver
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0
shrinking /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0/dbeaver/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.551.v20171108-1834/eclipse_1630.so
shrinking /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0/dbeaver/dbeaver
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0/bin
patching script interpreter paths in /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0
checking for references to /build in /nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0...
/nix/store/zv77vlfpyk37ki74xi4vldbqqk4yw2bx-dbeaver-ce-5.1.0

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: dbeaver
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


[Feature]: Create VPC endpoints in the AWS VPC

Describe the Feature
This feature would allow all the traffic to be routed inside of the VPC instead of going out and coming back in again. The code for the VPC endpoints can be found here in the VPC module.
Importance of the Feature
This is important to keep all the traffic inside of the AWS network instead of going out in the internet and coming back in again. It is important for security, and to reduce the egress costs.

hey  @aliabbasjaffri pls assign me this issue
thanks

Hello! Sure! All the best, feel free to ask any questions in our discord


[prettier-plugin-sql] enable SQLite

Hi again 👋 hope you’re doing well!  Just thought I’d try prettier-plugin-sql and contribute a quick fix
According to the npm package and README, the prettier-plugin-sql plugin supports sqlite.
However, the sqlite option is not enabled https://github.com/un-ts/prettier/blob/master/packages/sql/src/index.ts#L87
PR incoming…

Nice catch, it has been released. Thanks @jlarmstrongiv


Feat: Implement the functions in the base_order_handler contract.

Description
Implement the get_execute_order_params function in the base_order_handler library.
File: src/exchange/base_order_handler.cairo.
Function signature:
        /// Get the BaseOrderUtils.ExecuteOrderParams to execute an order.
        /// # Arguments
        /// * `key` - The the key of the order to execute.
        /// * `oracle_params` - The set price parameters for oracle.
        /// * `keeper` - The keeper executing the order.
        /// * `starting_gas` - The starting gas.
        fn get_execute_order_params(
            ref self: ContractState,
            key: felt252,
            oracle_params: SetPricesParams,
            keeper: ContractAddress,
            starting_gas: u128,
            secondary_order_type: SecondaryOrderType
        ) -> ExecuteOrderParams

Acceptance criteria

Function is implemented and well commented.
Associated unit tests (nominal and failure) are implemented and passing.

Resources

_getExecuteOrderParams function in GMX repo

Can I take this?

Of course ! Assigned !

is this still WIP? @khaeljy

is this still WIP? @khaeljy

I'm really sorry, I haven't had time to get into it. You can assign this issue to someone else.
Next time I'll make sure I have enough time before asking for an issue.

let me at it then!

Ok I will assign it to you @dbejarano820 🔥


Allow "bumping" a timer

From @jonscheiding on February 27, 2016 1:53
A timer should be able to be "bumped" (restarted).
Maybe one of the following actions:

Invoking /switches/:id/on when it is already on
A new PUT or maybe PATCH endpoint for timers

Copied from original issue: jonscheiding/st-power-control#10

See #5


When I close Zap and start it again, I get following Javascript error

Uncaught Exception:
Error: Connect Failed
at ClientReadableStream._emitStatusIfDone (/Applications/Zap.app/Contents/Resources/app.asar/node_modules/grpc/src/client.js:255:19)
at ClientReadableStream._readsDone (/Applications/Zap.app/Contents/Resources/app.asar/node_modules/grpc/src/client.js:221:8)
at readCallback (/Applications/Zap.app/Contents/Resources/app.asar/node_modules/grpc/src/client.js:283:12)
--
MacOs 10.13.1
A reboot resolves the issue

Can someone confirm if this issue is still reproducible with the latest code in the master branch?

Closing this story as a duplicate of https://github.com/LN-Zap/zap-desktop/issues/234


docs: add note regarding unspecified behavior for 0d arrays in cumulative_sum

This PR

Closes https://github.com/data-apis/array-api/issues/797.
updates specification language to limit input arrays to those having one or more dimensions. Conforming implementations are permitted to support 0d arrays for backward-compatibility, but this should not be considered portable behavior due to ambiguities arising from expected output for 0d input (e.g., when providing include_initial, what should be the dimensionality of the output? what should happen with the axis kwarg? etc).
aligns the specification based on discussions in #797 and the Consortium workgroup meeting on May 2, 2024.

As no objections have been raised for this PR and the proposed change already discussed during workgroup meetings, I'll go ahead and merge. Any further changes can be addressed in follow-up PRs...


Added the function isInvolutory()

Pull Request Template
Description
This function checks whether the given matrix is involutory or not. If the matrix is found to be involutory, the function returns 1 else, it returns 0.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I have run the code on compiler.

[ ] Test A
[ ] Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

!bounty 20


Solutions for full 12 exercises

Ruby basic practices

We do not merge in solutions into this repo, so I will be closing this PR.


Build pipeline

First Pull request to merge build-pipeline into master branch

 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.:x: ChPfisterer sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Close this and reject.


Build(deps-dev): Bump lint-staged from 12.1.6 to 12.1.7 (#2333)

Pull request opened by the merge tool on behalf of #2333

Merged in 3a8d45aa0cfbb090a2ab5846c41d0e67021ca4ec


Use unprefixed sccs, but postCss with autoprefixer in the build script

Atm the animations wont work.
Also all major browsers support media queries without vendor prefixes.

Hi @mablae thank you for spotting this, please verify if it works for you now :)


[Packaging] Remove unnecessary packages in docker image

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Packaging

Very comprehensive history analysis. Nice work!


fix space in travis.yml

LGTM

This pull request has been rebased via git hub pull rebase. Original pull request HEAD was fa31ee6439d280d70f92fb07a8682e3491cfc651, new (rebased) HEAD is 4356a580ff0112eff74b0be1a090a4149a9b8d20


405 Method Not Allowed

Using the code postUrl: '/uploadHandler' gives me a 405 error on the POST request. How do I fix this?

For a simple case, using the defaults, you need to provide a valid endpoint which accepts an HTTP POST with name 'file'.
For example (php):
http://yourserver.php/file_upload
which would have something like:

if(isset($_POST["submit"])) {
upload_file = $_FILES["file"]["tmp_name"];


Admin denied api access

I attempted to access my api using:
https://zulip.mydomain.com/api/v1/messages
I'm routed to login screen.
Enter admin email and password
access denied.

Second attempt

Log in to regular zulip account as admin. https://zulip.mydomain.com
attempt to access api. https://zulip.mydomain.com/api/v1/messages
I'm sent back to login screen again.

The API endpoints are not meant to be visited using a browser, and do not accept username/password authentication (instead you should be using the API key auth described in the API docs)


The validator can't validate input value set by v-model directive?

related #94

published v2.0.0-alpha.10
https://github.com/vuejs/vue-validator/releases/tag/v2.0.0-alpha.10


NameRes is missing from OTEL on both CI and Test

We probably messed up something in the Helm configuration.

https://github.com/helxplatform/translator-devops/pull/971 appears to have fixed this in CI. I'll close this once it gets pushed to Test.


Expand Branch Planner support to include more Git providers

We aim to extend the branch planner's capability to support more Git providers. The main focus, for now, would be on GitLab and Azure DevOps.

[ ] #692
[ ] #693

Note: potentially it can be an easy task as jenkins-x/go-scm supports both providers with a unified API. Potentially both issues will be just:

copy github provider
tweak it a bit,
profit

I'd like to throw in gerrit for consideration


timePicker component

Create a Time Picker component.
All the information related to the component can be found here:
https://github.com/wix/stylable-components/tree/master/specs/timeInput

List of issues for the first testing version:

[ ] AM/PM should be clickable & have special hover color for "am/pm" letters (ask Alex to provide designs for this)
Use wix style react for reference

[ ] When I click inside the input, I should automatically be focused on 'hh'

[ ] Stepper works incorrect with 'hh' for 24h format input. When I click Up Arrow Key I can get (34, -1, etc).
Please make sure that 24h format does not have negative numbers (-4) & can not exceed 24.

[ ] Up/Down Arrow Keys are not functional

[ ] When I click on 'hh', 'mm' I focus should automatically be set to 2 numbers (http://joxi.ru/xAe6lwjTYbO0Pr). I should not be able to set focus like this (http://joxi.ru/a2XEygkuyleNjA).

[ ] Stepper should be shown only on hover & focus.

[ ] Shift + Stepper/Arrow Up/Down should increase 'mm' by 10. Not working right now.
NOTE: Shift + Stepper/Arrow Up/Down works only for 'mm'.

[ ] Use text input Disabled state for