README example doesn't compile

error[E0609]: no field `step_size_adapt` on type `SamplerArgs`
   --> src/nl_fit/nuts.rs:293:22
    |
293 |         sampler_args.step_size_adapt.target = 0.8;
    |                      ^^^^^^^^^^^^^^^ unknown field
    |
    = note: available fields are: `num_tune`, `num_draws`, `maxdepth`, `store_gradient`, `store_unconstrained` ... and 3 others

error[E0609]: no field `store_mass_matrix` on type `nuts_rs::adapt_strategy::GradDiagOptions`
   --> src/nl_fit/nuts.rs:296:40
    |
296 |         sampler_args.mass_matrix_adapt.store_mass_matrix = true;
    |                                        ^^^^^^^^^^^^^^^^^ unknown field
    |
    = note: available fields are: `dual_average_options`, `mass_matrix_options`, `early_window`, `step_size_window`, `mass_matrix_switch_freq`, `early_mass_matrix_switch_freq`
help: one of the expressions' fields has a field of the same name
    |
296 |         sampler_args.mass_matrix_adapt.mass_matrix_options.store_mass_matrix = true;
    |                                        ++++++++++++++++++++

error[E0308]: mismatched types
   --> src/nl_fit/nuts.rs:303:71
    |
303 |         let mut sampler = new_sampler(logp_func, sampler_args, chain, seed);
    |                           -----------                                 ^^^^ expected `&mut _`, found integer
    |                           |
    |                           arguments to this function are incorrect
    |
    = note: expected mutable reference `&mut _`
                            found type `{integer}`
note: function defined here
   --> /Users/hombit/.cargo/registry/src/index.crates.io-6f17d22bba15001f/nuts-rs-0.8.0/src/cpu_sampler.rs:184:8
    |
184 | pub fn new_sampler<F: CpuLogpFunc, R: Rng + ?Sized>(
    |        ^^^^^^^^^^^
help: consider mutably borrowing here
    |
303 |         let mut sampler = new_sampler(logp_func, sampler_args, chain, &mut seed);
    |                                                                       ++++

error[E0599]: no method named `to_vec` found for associated type `<impl nuts_rs::Chain as nuts_rs::Chain>::Stats` in the current scope
   --> src/nl_fit/nuts.rs:314:34
    |
314 |             let _info_vec = info.to_vec(); // We can collect the stats in a Vec
    |                                  ^^^^^^ method not found in `<impl Chain as Chain>::Stats`

error[E0599]: no method named `start_location` found for reference `&DivergenceInfo` in the current scope
   --> src/nl_fit/nuts.rs:317:66
    |
317 |                 println!("Divergence at position {:?}", div_info.start_location());
    |                                                                  ^^^^^^^^^^^^^^-- help: remove the arguments
    |                                                                  |
    |                                                                  field, not a method

Thanks for letting us know.
Seems I forgot to update the readme with the contents of lib.rs. Should be fixed by #16

Should be fixed on main


chore(main): release 5.6.4

:robot: I have created a release beep boop
5.6.4 (2023-10-24)
Minor changes and bug fixes

update deps, change opus provider (814029e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/mariusbegby/cadence-discord-bot/releases/tag/v5.6.4 :sunflower:


Exporting SOAP project: file not found 0MtHdM.rsc

I recently started using CastleMock on a Docker container.  I was able to export the REST project but I am not able to export the SOAP project. I get this error: "Unable to find the following file: 0MtHdM.rsc". My SOAP project has 15 WSDLs although not all ports are mocked. I created a new empty SOAP projects and was able to export it.

Hi @orodrigueztorres.
Would it be possible for you to provide an example of a SOAP project that could not be imported? Sometimes it could be related to encoding or special characters.
In the meantime, I will try to reproduce this issue.
Thanks!
Best regards,
Karl Dahlgren

Hi @orodrigueztorres.
Were you able to provide an example SOAP project?
If not, then I will close this issue. Feel free to re-open it if you were to experience this issue again.
Best regards,
Karl Dahlgren

Hello,
And I am sorry, a couple of days ago I logged in to provide status and apparently forgot to submit it.
Yes, I was able to resolve the issue. As you said, there were some special characters causing the problem.
Thanks again.


Create 'create-plugin-template' command

Closes #166

We should create a github template which includes the ci scripts.
The create-template command then is used to create a specific plugin template.

Superseded by #245


bug: wrong binary name in CICD

Are you use the envd server?

[ ] Yes, I am using the envd server.
[X] No, I am not using the envd server.

Describe the bug

#10 [stage-1 3/5] RUN curl -sSfL https://envd.tensorchord.ai/install.sh | bash -s ''
#10 1.430 Downloading envd 0.3.32 for Linux x86_64...
#10 1.436   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#10 1.436                                  Dload  Upload   Total   Spent    Left  Speed
#10 1.437
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     9    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
#10 1.692 curl: (22) The requested URL returned error: 404
#10 1.696 Failed to download envd 0.3.32 for Linux x86_64: no matching binary is found.

To Reproduce
It does not matter
Expected behavior
No response
The docker info output
It does not matter
The envd version output
0.3.32
Additional context
No response

Maybe we need this https://goreleaser.com/customization/templates/#functions


ecr: grant methods cause circular references in generated templates

The grant* methods on the ecr.Repository class incorrectly add self-references to the repository's policies, leading to a circular reference error.
Example code:
const repo = new ecr.Repository(this, 'TestHarnessRepo', {
    repositoryName: props.repoName,
});
repo.grantPull(principal);

Rendered template (in relevant part):
TestHarnessRepoAA7E9724:
    Type: AWS::ECR::Repository
    Properties:
      RepositoryName: codebuild-inspec-test-harness
      RepositoryPolicyText:
        Statement:
          - Action:
              - ecr:BatchCheckLayerAvailability
              - ecr:GetDownloadUrlForLayer
              - ecr:BatchGetImage
            Effect: Allow
            Principal:
              Service:
                Fn::Join:
                  - ""
                  - - codebuild.
                    - Ref: AWS::URLSuffix
            Resource:
              Fn::GetAtt:
                - TestHarnessRepoAA7E9724 # !!!! this is the problem
                - Arn

ECR repository policies do not require resources to be defined (or they can be set to *) -- see the documentation for examples.

A workaround for the moment is to use the addToResourcePolicy method on the repo instead.


verify_pod_keys: Ability to supply "path" / "podfile" argument

When I run verify_pod_keys, I get the following error:
[!] No Podfile exists at path `Podfile`.

This is because I am building a react-native app, so the directory that I am running my fastlane commands out of is not the same directory as my Podfile.
It would be great if this action supported a path or podfile argument (similar to how the cocoapods action does) so I can specify the path to my Podfile and use this action in my setup.

Can you surround the verify_pod_keys command using
Dir.chdir("ios") do
  verify_pod_keys
end

and see if that works?

No luck:
[15:27:55]: No such file or directory @ dir_chdir - ios

+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | update_fastlane     | 2           |
| 2    | Verifying required  | 0           |
|      | fastlane version    |             |
| 3    | Verifying required  | 0           |
|      | ruby version        |             |
+------+---------------------+-------------+

[15:27:55]: fastlane finished with errors

[15:27:55]: Error accessing file, this might be due to fastlane's directory handling
[15:27:55]: Check out https://docs.fastlane.tools/advanced/#directory-behavior for more details

Fastfile:33:in `chdir': No such file or directory @ dir_chdir - ios (Errno::ENOENT)
	from Fastfile:33:in `prebuild'
	from Fastfile:122:in `block (2 levels) in parsing_binding'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/runner.rb:274:in `execute_flow_block'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/runner.rb:46:in `block in execute'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/lane_manager.rb:52:in `cruise_lane'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/command_line_handler.rb:30:in `handle'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/commands_generator.rb:104:in `block (2 levels) in run'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.5/lib/commander/command.rb:178:in `call'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.5/lib/commander/command.rb:153:in `run'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.5/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:64:in `run!'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.5/lib/commander/delegates.rb:15:in `run!'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/commands_generator.rb:303:in `run'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/commands_generator.rb:42:in `start'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/fastlane/lib/fastlane/cli_tools_distributor.rb:66:in `take_off'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/gems/fastlane-2.58.0/bin/fastlane:20:in `<top (required)>'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `load'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `<main>'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval'
	from /Users/joncursi/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `<main>'

I am executing fastlane from my react-native root directory, which does have an ios folder within.


Embed Pages

is it possible to use embed and normal strings as pages.
as an example:
pages = [Embed, string, Embed, Embed]

Just added this into my fork if you still need this: https://github.com/MrKev312/Discord.Addons.Interactive

Just added this into my fork if you still need this: https://github.com/MrKev312/Discord.Addons.Interactive

ah forgot to mention that i've already fixed this issue myself in my fork:
https://github.com/Venipa/Discord.Addons.Interactive/commit/abf050b5b40bab13668e71cfe1dd647573a105f2


Supergloo Support

Adding supergloo support.
I need to add a few more things here to support the A\B testing case, but wanted to make sure that we are good with the general structure of this PR before I continue investing in it.
One TODO that I have there, is the reference to the target mesh. as supergloo supports more than one mesh, it's CRDs have a mesh reference.
I think this can be passed as command line flags \ environment variables.
note that it seems like a lot of changes, but most of them are vendor \ generated code.

This looks great thanks @yuval-k
Flagger has a command flag called mesh provider that you could use to set the target mesh, for now it accepts istio and appmesh as values.
It looks like the e2e tests are failing, Flagger keeps crashing at startup, can you please rebase your PR.

where can you see the reason for the failure? I just see
Too long with no output (exceeded 10m0s)

@yuval-k have you tested this PR inside Kubernetes? Here is the error, looks like the klog is not initialised and it tries to write the logs to disk:
W0418 09:17:13.168786       1 client_config.go:549] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.

log: exiting because of error: log: cannot create log: open /tmp/flagger.flagger-845645c8fc-vtbpt.unknownuser.log.WARNING.20190418-085541.1: read-only file system

For logging Flagger uses zap and the Istio logger that replaces glog with zap. Kubernetes 1.13 switched to klog and the logging is broken now.  Flagger should log to stderr in json format only.
[[override]]
  name = "github.com/golang/glog"
  source = "github.com/istio/glog"

I've tried to override klog with istio/glog but it doesn't work. I would rollback to Kubernetes 1.11 until klong can be replaced with zap.

Thanks for all the info - I'm looking into this on our end and see if we can use lower version of kube.

@yuval-k I've done the upgrade to 1.13 in master and the override of klog with zap.
Please rebase and take my Gopkg files, also pin the supergloo package in Gopkg.toml to a git tag or commit. Thanks!

hi @stefanprodan I was able to work around the klog issue by changing main.go like so:

type klogZapAdapter struct {
	logger *zap.SugaredLogger
}

func (k *klogZapAdapter) Write(p []byte) (n int, err error) {
	k.logger.Info(string(p))
	return len(p), nil
}

func main() {
	flag.Parse()

	logger, err := logger.NewLoggerWithEncoding(logLevel, zapEncoding)
	if err != nil {
		log.Fatalf("Error creating logger: %v", err)
	}
	if zapReplaceGlobals {
		zap.ReplaceGlobals(logger.Desugar())
	}

	defer logger.Sync()

	klog.SetOutput(&klogZapAdapter{logger})

does that sound reasonable to you?

Please disregard my last comment - I just saw your comment from before saying you solved it

Hi @stefanprodan this should be ready for review

Hi @yuval-k can you please add some docs on how was this tested and how to setup a e2e testing for it. I would like to have e2e tests the same as for Istio and be able to run it on GKE and on Kubernetes KinD. Thanks

I tested it manually before, added e2e tests now. From reason I saw an issue to connecting to promethues when I ran them locally (which is not in the supergloo code path) - so I pushed them to see if it reproduces in CI.

I see the test failing - I think i'm missing something for the A\B test use case - checking.

I think I know why the tests are failing, the default Istio memory and CPU requests are very high for the CirceCI VM. To make Istio work with KinD you need to set these resources requests https://github.com/weaveworks/flagger/blob/master/test/e2e-istio-values.yaml
I would add a check to e2e-supergloo.sh:
kubectl -n istio-system rollout status deployment/istio-pilot
kubectl -n istio-system rollout status deployment/istio-mixer
kubectl -n istio-system rollout status deployment/istio-sidecar-injector
kubectl -n istio-system rollout status deployment/istio-telemetry
kubectl -n istio-system rollout status deployment/prometheus


Assume role support for aws eks credentials

Describe what this Pull Request does and why you think it is needed.
We are using this kubeclient to perform API operations against the AWS EKS (kubernetes) clusters (i.e. the Kubernetes API Server). But we are not using access_key & secret_key directly as it is generally considered insecure. Hence we use - role based access control along with AWS STS to perform authentication (i.e. short lived temporary credentials). But the support for such Credentials Provider is not there in this Client (only supports - static Credentials & profile based static credentials).

I tried a small change to support the AssumeRoleCredentials Provider and it worked nicely. Hence I thought this would be a nice feature enhancement for this repo to users like me who want to use role based access with STS assumed role credentials.

If this fixes an existing issue, please specify in Fixes #<id> format
Not a bug fix. It is a feature enhancement.

Ask @miq-bot to apply a scope label (bug, enhancement, etc) and any additional reviewers or assignees.
@miq-bot add-label enhancement
@miq-bot add-label aws
@miq-bot add-label eks
@miq-bot add-label aws_eks

@miq-bot add-label enhancement
@miq-bot add-label aws
@miq-bot add-label eks
@miq-bot add-label aws_eks

Test failures should be resolved by #631 and #632


Add default values, ranges, valid values, and a verify function for the input deck

Summary

This PR is a feature
It does the following:

Allows specifying default values and ranges for Fields in the input deck.
Provides a verification function for the input deck.

@aeshapar dont worry about styling your code, @kennyweiss is going to have a large PR soon that fixes the style on the whole code base and this will fix it for you.

LGTM


Adds mvn wrapper tools to project

Fixes #25

Cool! Now I can build project locally 😄
Merging...


Added an additional check for validate_user function with some additi…

…onal tests.
Closes: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


bosh release 404 not found.

The url in following command has been removed.
bosh upload release https://cf-contrib.s3.amazonaws.com/boshrelease-cf-services-contrib-6.tgz

There is a the official url instead.
bosh upload release https://bosh.io/d/github.com/cloudfoundry-community/cf-services-contrib-release

Thanks for the report, @samueldeng.
@bingosummer Please update README


completed blocks should only be recorded as COMPLETED once in block table

Is your feature request related to a problem? Please describe.
The block table logs a completed message for a completed block quite a lot (probably once per status poll).
It would be nice if once a block was completed, it did not continue to be logged.
eg:
sqlite> select * from block where job_id=42124101 order by timestamp asc;
run_id                                executor_label  block_id  job_id    timestamp                   status
------------------------------------  --------------  --------  --------  --------------------------  ---------
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:11:26.281743  PENDING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:12:27.078317  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:13:26.166260  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:14:26.147591  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:15:27.383811  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:16:26.150544  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:17:27.542485  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:18:27.327732  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:19:17.496592  CANCELLED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:19:27.581401  RUNNING
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:20:27.632491  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:21:26.732398  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:22:28.236627  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:23:26.637338  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:24:26.789805  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:25:26.589810  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:26:26.211026  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:27:26.240359  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:28:26.926321  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:29:28.432590  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:30:27.883743  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:31:28.485131  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:32:26.633687  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:33:26.583509  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:34:27.237217  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:35:26.454162  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:36:26.504780  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:37:26.540891  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:38:28.499967  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:39:28.149559  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:40:28.302512  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:41:26.550003  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:42:26.849695  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:43:26.515778  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:44:28.175655  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:45:26.609580  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:46:28.261130  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:47:27.971551  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:48:26.478649  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:49:27.967931  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:50:27.870873  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:51:26.530769  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:52:26.678164  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:53:26.769777  COMPLETED
c70b21d1-2d24-4c4c-9da4-9ac5903382f7  batch-2         0         42124101  2021-04-29 15:54:26.536399  COMPLETED

Describe the solution you'd like
A single COMPLETED entry in the block table when a block is first completed.
Additional context
desc branch

crossref #2121


disallow non-secure transport on the base web endpoint

Issue #, if available:
Description of changes:
Fix an S3 bucket policy that allows non-secure transport on the base url for the web endpoint
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Skipping review for this trivial change.


Add celebrity category

I've formatted qual_id/pattern.py using black.

Codecov Report

Merging #53 into main will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #53   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           66        68    +2
  Lines          613       613
=========================================
  Hits           613       613

Impacted Files
Coverage Δ

qual_id/categories/celebrity.py
100.00% <100.00%> (ø)

qual_id/pattern.py
100.00% <100.00%> (ø)

test/categories/test_celebrity.py
100.00% <100.00%> (ø)

test/utils/category_helper.py
100.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 fc159c3...c3620fd. Read the comment docs.

Thanks for the contribution @sgalpha01 🙂


Wrong item rendering of virtualScroll which is inside ion-card.

Your Notes
It' took me weeks to compare hybrid frameworks and choose Ionic for our company, Of course minus the time spent on learning and setup it!! It's really shameful to announce Ionic 2 as stable version with this horrible bug!
Ionic version:
[ ] 1.x
[x] 2.x
I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] support request
Current behavior:
Using virtualScroll inside ion-card cause virtualScroll to render wrong items while scrolling.
Some of items of virtualScroll visible area aren't rendered and also some of them which are not in visible area are rendered.
Expected behavior:
1.Only those items of virtualScroll must be rendered that are in visible range.
2.Any items of virtualScroll outside visible range must not be rendered. [Usually first element of array is always rendered]
Steps to reproduce:
Simply put virtualScroll inside a ion-card.
Here is Plunker for lazy people.
http://plnkr.co/edit/1taMRHiGUVL1rRpoWrbN?p=preview
Other information:
Nothing more
Ionic info:
Your system information:
Cordova CLI: 6.5.0
Ionic Framework Version: 2.0.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 0.0.44
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.2
Xcode version: Not installed

Almost one month and not even a response...

@jgw96  @mlynch @manucorporat Shouldn't this issue have virtualscroll label and maybe 3.0 blocker too!?

Just upgraded to v3 and the problem still exist.. Does anybody care about virtual-scroll issues !?
Steps to reproduce for v3:
http://plnkr.co/edit/F3hFNnXuVOXpulBcUJv5?p=preview

Virtual scroll is broken and not ready for production, try to find angular2 virtual list alternative


Bluetooth: mesh: support load iv && neykey from app

The user application needs to specify IV and netkey when creating the mesh network for the first time,
so net_key and iv_index should be over-ridden here.
Signed-off-by: YanBiao Hao<EMAIL_ADDRESS>

LGTM Please remove this: https://github.com/zephyrproject-rtos/zephyr/pull/42957/files#diff-721db5c8b120e58a2f2137153346b2777330b8aeb1a6fcd5be1dc9d5ada51580R58-R61
This is not actual anymore after your fix.

I've removed the notes you mentioned


AMBARI-25453. If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false

What changes were proposed in this pull request?
If hive.server2.webui.use.ssl was setted to true it will always use https, does not matter if now it is false
How was this patch tested?
manually
Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5638/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5640/
Test PASSed.


Document table deletion strategy

Basically deprecate then remove 2 point releases later.  Ensure tracking issues etc.

Done, see schema document


Consolidated channel: SASL/PLAIN does not work with public TLS certificate

Describe the bug
When using a channel against a public service, with proper TLS certificates, the channel is not working, since it expects there CA Cert
https://github.com/knative-sandbox/eventing-kafka/blob/master/pkg/channel/consolidated/utils/util.go#L80
Expected behavior
Works without the ca cert
Knative release version
0.19+

/assign @matzew


Unable to lookup provisioned efs file systemid in custom addon

Describe the bug
cdk can't lookup the fileSystemId as getRequiredResource() states that the efs resource is missing however it is declared
Expected Behavior
Stack should deploy and it is possible to lookup the id of the efs file system
Current Behavior
The following error is return when running cdk deploy
AssertionError [ERR_ASSERTION]: Required resource eks-test-efs is missing.
at ClusterInfo.getRequiredResource (/mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/@aws-quickstart/eks-blueprints/lib/spi/types.ts:263:9)
at DeploymentServiceJob.deploy (/mnt/d/Oceans/oceans-templates/eks-blueprint/bin/eks-blueprint.ts:127:33)
at new EksBlueprint (/mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/@aws-quickstart/eks-blueprints/lib/stacks/eks-blueprint-stack.ts:273:34)
at BlueprintBuilder.build (/mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/@aws-quickstart/eks-blueprints/lib/stacks/eks-blueprint-stack.ts:201:16)
at Object. (/mnt/d/Oceans/oceans-templates/eks-blueprint/bin/eks-blueprint.ts:217:6)
at Module._compile (node:internal/modules/cjs/loader:1256:14)
at Module.m._compile (/mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/ts-node/src/index.ts:1618:23)
at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
at Object.require.extensions. [as .ts] (/mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/ts-node/src/index.ts:1621:12)
at Module.load (node:internal/modules/cjs/loader:1119:32) {
generatedMessage: false,
code: 'ERR_ASSERTION',
actual: undefined,
expected: true,
operator: '=='
}
Reproduction Steps
  const efsResourceName = stackName + "-efs";

  export class DeploymentServiceJob implements blueprints.ClusterAddOn {
  @blueprints.utils.dependable(blueprints.EfsCsiDriverAddOn.name)
  deploy(clusterInfo: blueprints.ClusterInfo): void {
      const cluster = clusterInfo.cluster;

      const efs = clusterInfo.getRequiredResource<IFileSystem>(efsResourceName);

      const scResource = new KubernetesManifest(clusterInfo.cluster, 'efs-sc', {
          cluster: clusterInfo.cluster,
          manifest: [{
              apiVersion: "storage.k8s.io/v1",
              kind: "StorageClass",
              metadata: { name: "efs-sc" },
              provisioner: "efs.csi.aws.com",
              parameters: {
                  provisioningMode: "efs-ap",
                  fileSystemId: `${efs.fileSystemId}`,
                  directoryPerms: "700",
                  gidRangeStart: "1000",
                  gidRangeEnd: "2000",
                  basePath: "/dynamic_provisioning"
              }
          }], overwrite: true,
      });
  }
}

const stack = blueprints.EksBlueprint.builder()
    .resourceProvider("efs-file-system", new blueprints.CreateEfsFileSystemProvider({name: efsResourceName}))
    .addOns(...addOns)
    .build(app, stackName);

Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.9.1
EKS Blueprints Version
1.11.2
Node.js Version
18.17.1
Environment details (OS name and version, etc.)
Ubuntu 20.04
Other information
No response

I was using the wrong name to lookup the resource, it should have been "efsResourceName".
I then got this error
"Error: TypeError: Cannot read properties of undefined (reading 'then') at /mnt/d/Oceans/oceans-templates/eks-blueprint/node_modules/@aws-quickstart/eks-blueprints/lib/utils/addon-utils.ts:50:31" ,
I was able to fix this by removing the dependable at the top of the class


[Feature Request] (GuildProfile) Hide Joined/Last Message times for "Home" Screen

When viewing the Friends list "Joined At" shows "(!) Failed to Fetch" and Last Message shows "(!) Cannot resolve channel/guild id."
This is expected behavior but just looks odd to uninformed users.
When you go into a conversation the last message date populates correctly, but the joined at date remains in an error state.
I am uncertain if any logic could handle this to simply not display on the "Home" and Direct Messages screens when errored but it would make it just a bit more graceful in my mind.

GuildProfile doesn't create any "Last Message" section. Are you sure that GuildProfile is responsible for that?

Ah, I found that one was a separate plugin, I may have a few that actually handle that and got them crossed.
LastMessageDate by DevilBro (maybe) and UserDetails by Strencher (more likely) are apparently where I should be looking.
Thank You for the prompt response!


[C++/WinRT] Async methods don't take parameters by const&

[C++/WinRT] Async methods don't take parameters by const&
The documentation shows async methods in C++/WinRT takes parameters by const& but in C++/WinRT async methods take the parameter by value and never by const&.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ebb48ceb-7901-50d7-1748-1b97e543a5dd
Version Independent ID: f599ae92-4fd9-2c8a-712a-9ed0594b0aa3
Content: CoreApplication.RequestRestartForUserAsync(User, String) Method (Windows.ApplicationModel.Core) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.ApplicationModel.Core/CoreApplication.xml
Product: uwp
Technology: winrt-reference
GitHub Login: @mikben
Microsoft Alias: mikben

Hi, @Jaiganeshkumaran, and thanks for filing this issue. This is an interesting point, and it occurred to me, too. I got some info from the C++/WinRT team.
Coroutines must take parameters by value. Everything else is a regular function that should accept params by reference.
But the indications of a function being a coroutine are the presence of a co_await, co_return, or co_yield statement. Not whether the function's name has "Async" in it, and/or it whether it returns IAsyncAction or IAsyncOperation.
"Async" methods in the C++/WinRT language projection such as CoreApplication::RequestRestartForUserAsync are actually not coroutines, they're just regular functions.
The C++/WinRT language projection's "Async" methods all take params by reference – we don't need to prematurely pessimize them by incurring an extra copy, because the projection method isn't the one doing the work. It might not even be the top-level function on the other side of the API inside Windows that does the work. There could be several layers of indirection before the "async"-ness kicks in; only then does the code need to ensure that it has a local copy of whatever data it's going to stash away for later.
So, the topic for CoreApplication::RequestRestartForUserAsync does correctly document the parameters. The projection does indeed take those parameters by reference.
Thanks!
Steve


⚠ Processors has degraded performance

In 2343655, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 167 ms

Resolved: Processors performance has improved in f3f5322.


Add configuration to run debugger to application's entry point.

This adds a new stopAtEntry configuration option which can be used to
command the extension to run the application up to its entry point.
This can be used for both launch and attach configurations.  For
launch configurations, the debugger's "start" command will be used if
available, otherwise a temporary breakpoint will be set at the entry
point and execution will be commanded (to allow running to the
breakpoint).  When no entry point is provided for an attach
configuration the extension will default the entry point to "main" as
a reasonable default.  When no entry point is provided for a launch
configuration and the debugger does not support the "start" command,
the extension will also default the entry point to "main" as well.
The user can explicitly specify the entry point, in which case that
will be used to set a temporary breakpoint.

Can you please elaborate what the point about that is and what issue this solves?
A working stopAtStart or similar would only use "start" when possible and in the other cases connect to the application and interrupt then, no?
And if you want to stop at a specific point you can set breakpoints the normal way already - or are those currently not handled correctly during startup?

Can you please elaborate what the point about that is and what issue this solves?
A working stopAtStart or similar would only use "start" when possible and in the other cases connect to the application and interrupt then, no? And if you want to stop at a specific point you can set breakpoints the normal way already - or are those currently not handled correctly during startup?

Sure, I will attempt to expand on this.
This capability provides a feature similar to cpptools "stopAtEntry" and Eclipse/CDT "stop on startup at" with respect to bringing the debugged application to a recognizable place (i.e., the entry point of the application).  Sometimes we don't want to run immediately and thus bringing the application to this point allows the developer to set other breakpoints prior to continuing execution.  The developer could have set the other breakpoints prior to running the debugger, but that is not always the preferred workflow.
One of the problems with the cpptools version of this capability is that it is currently hard-coded to use "main" as the entry point.  This means it doesn't work for applications which use a non-main entry point (e.g., Ada).  Additionally, I wanted this to attempt to auto-detect the entry point if possible (thus the reason for use the "--start" option to "exec-run" if supported by the debugger for a "launch" configuration) as that is what that capability is for.  The following snippet for a "launch" configuration will use "exec-run --start" if the debugger supports it, otherwise, it falls back to a sensible default of setting a temporary breakpoint at "main".  For an "attach" configuration (since there is no "--start" option for that), this would immediately default to setting a temporary breakpoint at "main".
"stopAtEntry": true

The following snippet shows explicitly specifying the entry point in the case that either the debugger does not support the "--start" option ("launch" configuration only), or that the entry point is not "main" ("launch" or "attach" configuration).  For the "attach" configuration, this is not generally applicable to the "attach to PID" scenario as likely the application will have already started running past the entry point.  In the "attach to PID" scenario, this provides nothing useful.  However, for the "attach to gdbserver" scenario, it works similarly to the launch configuration.  If we run gdbserver and provide the application to it, gdbserver will not start running the application immediately.  This means, we can attach to gdbserver and run the application to the entry point, similarly to how we would for the "launch" configuration.
"stopAtEntry": "hello_world"

In theory you could use the "autorun" configuration to set a breakpoint, but there can be race conditions with configuring breakpoints too early.  Any breakpoints set prior to the "setBreakPointsRequest" arriving from the client will be cleared out (see MI2DebugSession::setBreakpointsRequest), thus the "autorun" configuration is not an ideal location to automatically configure additional breakpoints.
You could manually set a breakpoint at the entry point prior to executing, but this requires manual intervention.  If this debug configuration is being shared with a team, it requires everyone on the team to perform this manual setting, if this is the desired startup behavior.
Hopefully this provides the additional details you were looking for.

I'm a fan of this change.
I wonder does having this setting also add a checkbox in the breakpoints view for stop at entry or is that something you need to do separately?

Currently it needs to be done additionally - but I really think we should implement what Termdebug has (now): it checks the MI output:
      elseif msg =~ '^\^done,bkpt=' || msg =~ '^=breakpoint-created,'
        call s:HandleNewBreakpoint(msg, 0)
      elseif msg =~ '^=breakpoint-modified,'
        call s:HandleNewBreakpoint(msg, 1)
      elseif msg =~ '^=breakpoint-deleted,
	call s:HandleBreakpointDelete(msg)

This allows for:

a breakpoint being created or deleted from the command line and still be recognized
a breakpoint that was created by some debugger script be recognized
a breakpoint that was previously pending (because it was set before attaching/running) is reached and then modified (because now the debugger has symbols for it) be recognized
breakpoint changes (commonly enabled/disabled, but also "commands executed when reached" or "conditions") being recoggnized by the UI

I suggest to use the same approach in this extension and this will also automatically bring in the support for showing the entry breakpoint (if it is used and necessary) be added in the breakpoint list - automatically as soon as it is reached.
Any volunteers?

@brownts Doesn't that conflict and/or t least overlap with stopAtConnect? Once this is clear and solved (may need README.md and/or package..json adjustments) I'm fine with merging that PR.

I wonder does having this setting also add a checkbox in the breakpoints view for stop at entry or is that something you need to do separately?

This is set as a temporary breakpoint (either explicitly with the breakpoint command or implicitly via the "exec-run --start" command), so will be deleted from the breakpoint list as soon as it is hit.  I'm not sure it makes sense for it to be shown in the UI as it would just be inserted and then almost immediately removed.  It might be more of a distraction than a benefit.  From previous experience with Eclispe/CDT, I've never seen this temporary breakpoint shown in the UI's breakpoint list.

Note: I'd also call the auto-removing of breakpoints a mis-feature, so I strongly suggest to remove that

This behavior (of clearing breakpoints) seems to be consistent with the specificiation.  The only difference is that the current implementation clears all breakpoints where the specification indicates that only breakpoints in the same source file should be cleared.  It looks like there is a PR for this (i.e., #259), but not sure what happened with it.

Doesn't that conflict and/or t least overlap with stopAtConnect? Once this is clear and solved (may need README.md and/or package..json adjustments) I'm fine with merging that PR.

I would not expect much overlap between "stopAtConnect" and "stopAtEntry".  They are expected to be used in different situations.  For example, "stopAtConnect" might be used to debug early startup code prior to the application entry point.  Another example might be to stop a running application to debug it...maybe it's stuck in a loop and you want to see what it's doing.  Thus continuing execution after connect is not desirable.  Yet another example might be that the application being debugged is stopped at a breakpoint or exception and you want to attach to it and debug it...again, you wouldn't want to continue execution in this scenario.  These are few examples where "stopAtConnect" would be desirable.
The "stopAtEntry" would be used during application startup and is primarily used to just quickly setup the debugger at the application entry point.  This way you can set additional breakpoints here, start stepping through your application, or continue execution.  This often makes more sense than either stopping at connect (in the early startup code) or continuing execution, for a nominal debug scenario.  Also, "stopAtConnect" can only be associated with "attaching", but "stopAtEntry" can be associated with both "launching" and "attaching" (primarily in combination with gdbserver).
I would not expect that it's useful that both "stopAtConnect" and "stopAtEntry" both be enabled at the same time (and this would only be possible with an "attach" configuration as the "launch" configuration does not allow configuration for "stopAtConnect").  However, in the case that they are, the debugger will stop on connection, however it will also set a temporary breakpoint for either "main" or the supplied entry point breakpoint, as specified in the "stopAtEntry" configuration.  Thus, when continuing from the point where it was initially stopped on connect, it should run and hit the temporary entry point breakpoint.  So these can both be enabled at the same time, and should work as expected, but I wouldn't expect that this configuration would be useful for most scenarios.

Is there any further discussion to be had on this or can it be pulled in?

ping @GitMensch, @WebFreak001

Thanks for your additional contribution, for the explanation (after re-reading README I've seen no conflict any more) and for your patience (I was away for two weeks).
I still think that it would be good to implement a breakpoint recognition as outlined above, but this is a general issue not only related to this issue (I'd argue for "useful to be shown" when connecting / reaching the debugger's application entry point takes a while).
If someone (@brownts ?) could have a look into this it would be marvelous, but as it is a different issue - merged this.


Bug: Hide and Seek

Bug
Hi @arnoldnekemiah
I found that your mobile menu not functioning as it should be
in line 8 main.js you forget to put method .add() to adding class to the element
In your main.js
  function openMenu() {
    mobileMenu.style.display = 'flex';
    body.classList('menu-open');
  }

Suggestion for fixing the bug
  function openMenu() {
    mobileMenu.style.display = 'flex';
    body.classList.open('menu-open');
  }

Hopefully, it solves your problem
Cheers
Ichsan

Correct! Your on point


Pre-training details about PPIRef

Hi, Congrats on your excellent work!
I try to pretrain my model on PPIRef50K. However, it seems that there is no specific description of the data-splitting strategy in your paper. How do you split the PPIRef50K for pre-training, conduct the validation, and select the pre-training checkpoint? Besides, given several protein-protein interfaces, how do you construct batches for training? Specifically, do you crop interfaces into patches and conduct padding like RDE? I would really appreciate it if I could get your help! Thank you!
Regards,
Ralph

Hi, Ralph,
Thank you for your comment. It should be explained more clearly in the camera-ready version of the paper.

How do you split the PPIRef50K for pre-training, conduct the validation, and select the pre-training checkpoint?

We pre-train on the whole PPIRef50K and monitor zero-shot ddG performance on the training part of SKEMPI for validation/selecting checkpoints.
Specifically, paths to the PPIs for training can be read via ppiref as following:
from ppiref.split import read_fold
ppi_paths_pre_training = read_fold('ppiref_6A_filtered_clustered_04', 'whole')

The ppiref_6A_filtered_clustered_04 contains only a single fold whole (and not for example two folds training and validation) because we did not split PPIRef50K. Instead, for validation we used the PPIs from SKEMPI and measured zero-shot ddG to select the best pre-training checkpoints. You can read all validation PPIs as below:
ppi_paths_fine_tuning = read_fold('skempi2_iclr24_split', '0+1+2')

The paths in the ppi_paths_fine_tuning list correpond to the interfaces extracted from the cleaned .pdb files available on the SKEMPI website. Finally, we use these 3 folds (0, 1, 2) to fine-tune three models starting from the same pre-trained checkpoint (using for example 0+1 for training and 2 for validation), and test the ensamble of three models (averaging the predictions) on the SKEMPI test set:
ppi_paths_test = read_fold('skempi2_iclr24_split', 'test')

Besides, given several protein-protein interfaces, how do you construct batches for training? Specifically, do you crop interfaces into patches and conduct padding like RDE?

For a batch, for example, of size 2, we use 2 complete interfaces. Then we mask some ratio of nodes (50% in the final model) from each interface, such that only the amino acids from a single partner in the interface are masked. So, we do not crop PPIs into patches. Technically, we collate several PPIs into a batch using Pytorch Geometric, which is described in detail on this page in the PyG docs.
Notes:

For pre-training we used PPIRef50K with the interfaces based on 10A distance between heavy atoms. Now, on PPIRef Zenodo there are only interfaces based on 6A distance. I will upload the 10A interfaces, updated to this year, in the nearest future. Nevertheless, at the moment I do not know if training from 6A interfaces will lead to better or worse performance. Both distance are well-established in literature.
If you liked to split PPIRef50K, I would suggest using the pre-computed iDist embeddings for PPIRef300K available on PPIRef Zenodo.

Best,
Anton

Hi, Anton,
Thanks so much for your detailed clarification! It did help a lot. Regarding splitting PPIRef50K, do you have any recommendations for the threshold when using the pre-computed iDist embeddings? Since PPIRef50K has been deduplicated under the threshold of 0.04, so I guess maybe random splitting into training and validation parts is feasible, too?
Regards,
Ralph

Hi, Ralph.
Yes, you are right. Splitting PPIRef50K randmly is reasonable. Similarly, to randomly splitting UniRef seeds.
Nevertheless, it is potentially possible to achieve an even more struct split by, for example, connecting PPIRef50K using a higher threshold (such as 0.06) and then splitting the connected components of PPIs.
Best,
Anton


Unsigned integers should be printed as hexadecimal

Currently, everything is converted to Int64, but this has a fundamental incompatibility with unsigned integers, and this is not consistent with the original TOML specification, e.g
the following TOML file should be valid according to the specification, but the Julia parser fails to parse or print
hex1 = 0xc53fc6704b16fdc2

One interesting question here is whether we should preserve type differences stemming from how integer values are formatted. The TOML spec doesn't say much about what types should be used to represent values, merely that

Arbitrary 64-bit signed integers (from −2^63 to 2^63−1) should be accepted and handled losslessly. If an integer cannot be represented losslessly, an error must be thrown.

That means that while we should parse hex literals (and binary and octal), we could still represent the values using Int64. However, we don't have to. We could parse unsigned literals to unsigned integer types determined by the number of digits of the literal like Julia itself does. If we do that, then we further have the option to print them out using the corresponding hex format. Slightly tangential, but we can also support parsing very large integer literals as larger types like Int128, UInt128 and BigInt.

the following TOML file should be valid according to the specification, but the Julia parser fails to parse or print

As Stefan showed, 64-bit integers should be handled losslessly (which the current parser does) so I would say it is within spec.
There's been some discussion about this:
https://github.com/toml-lang/toml/issues/688
https://twitter.com/hsivonen/status/1461684220519141384?lang=da

Since it's within the bounds of the spec, I'd certainly be in favor of using larger types to faithfully represent integer values larger than the range of Int64. There are two options that seems viable to me:

Use Int128 and BigInt to represent large values no matter the syntax. Always print integers using decimal syntax.
Parse large decimal values using Int128 and BigInt; parse binary, octal and hex values as we do in Julia, choosing an unsigned type based on the number of digits in the literal. Print similarly to Julia show: use decimal syntax for signed integers and hex syntax for unsigned integers, with the number of digits determined by type.

Option 1 is simpler, but I feel like option 2 makes TOML more useful for Julia usage where that type information can be useful. Changing the type used to represent hex/octal/binary literals is technically a breaking change, but I doubt it would cause much trouble.

I second @StefanKarpinski 's option 2 - if we don't do it, the current way is to write them as strings and parse to a Julia type anyway, I'd rather let it be handled by the parser directly.
FYI. I bring this issue up mainly because it fails to serialize the random number generator seed in UInt64 because it cannot always be converted to Int64, which initially I was expecting the TOML parser could handle.

I definitely feel that for Julia being able to store integer values of arbitrary size in TOML files is a good idea. Of course, other TOML implementations might not be able to read them, but that's ok.


example with flags, but without tailwind

Thanks for amazing example!
But actually tailwind is a bit overkill for me. I make a small demo https://github.com/nosovk/KBC-webcomponents where I pack svelte-tel-input in a web component to allow embedding on landings etc. But unfortunately I wasn't able to correctly separate it from Tailwind. In my case click on element in dropdown stopped working, because of wrong css layering is wrong and elements overlapped. Have you some example of usage with flags, but without tailwind probably?

Hello there!
Your welcome.
I'm on holiday right now. I can take a look on sunday or monday. Shouldn't be too complicated.

Hello!
I have some questions about the use of your example, can I ask for help with the example of use with flags only?

Thanks for amazing example! But actually tailwind is a bit overkill for me. I make a small demo https://github.com/nosovk/KBC-webcomponents where I pack svelte-tel-input in a web component to allow embedding on landings etc. But unfortunately I wasn't able to correctly separate it from Tailwind. In my case click on element in dropdown stopped working, because of wrong css layering is wrong and elements overlapped. Have you some example of usage with flags, but without tailwind probably?

It's not done yet, but this is the way:
https://stackblitz.com/edit/svelte-tel-input-regular-css?file=src%2Flib%2Fcomponents%2FAdvancedTelInput.svelte

Hello! I have some questions about the use of your example, can I ask for help with the example of use with flags only?

Sure!

I've removed unused classes from the example, the result is here. It would be nice to add tailwind free example to readme.

I'll make some soon.
I migrated the project into the monorepo which is solves the problem of the example creation.
https://github.com/gyurielf/mono-sti
Technically it's done, I just polishing.

It would be nice to also have a flag example with UTF-8 flags.

There is a PR on the way where you can choose what do you want to use.
Once more:  Everybody can implement his own ideas, svelte-tel-input has only need a country iso2 alpha.


[AutoPR] powerbiembedded/resource-manager

Created to accumulate context: powerbiembedded/resource-manager

Closing PRs that are older than 1 month.


Investigate running lighthouse behind authentication

the helix bot ends up running on the authentication page, which has a surprisingly low score

thread in #franklin-chat
https://cq-dev.slack.com/archives/C9KD0TT6G/p1679472242713369
Valentin Olteanu
28 days ago
we have some experience with running lighthouse on own infra (memory consumption, failure handling etc.)
@dyland
have you started looking into it? happy to help
Tobias Bocanegra
:house:  28 days ago
@maxed
successfully implemented a POC

https://github.com/adobe/helix-lighthouse-service#readme

this is now working... closing.

actually it wasn't working, not sure why I thought it was

okay, now it's really enabled... lhs 99


SSL verification fails

Hi,
I installed the API and tried to run the example code, but I keep getting the same error:
aiohttp.client_exceptions.ClientConnectorError: [Errno 1] Cannot connect to host ws-feed.gdax.com:443 ssl:True [Can not connect to ws-feed.gdax.com:443 [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)]]
Does anyone know how to fix this issue?

I found the solution here: https://github.com/Cog-Creators/Red-DiscordBot/issues/581


Suggestion for eth-lite: add support for authentication on JSON-RPC

Hyperledger Besu supports user-password authentication on JSON-RPC endpoints, which is useful in some cases of private chains.
Is it interesting to add support for this authentication mode in the eth-lite plugin?
I've started a first implementation draft here: https://github.com/adetante/explorer-core-plugins.
This version of the plugin requires configuration changes in config.json:

Add the withauthentication: true plugin configuration

    "plugins": [
      ...,
      {
        "uri": "plugin://aleth.io/eth-lite",
        "config": {
            "nodeUrl": "http://my_besu_node:8545",
            "withAuthentication": true
        }
    }],

Add the auth module in dashboard page (this module displays the login form)

"pages": [
  ...,
  {
    "def": "page://aleth.io/dashboard",
    "children": {
        "content": [
            { "def": "module://aleth.io/lite/auth" },
            ...
        ]
    }
  }
}

Yes, we should support custom authentication methods per node, but I think most of the functionality should be implemented in a separate plugin. From what I saw in the Besu docs and your implementation, the authentication method used is specific to Besu and will most likely not be of any use to other types of nodes.
While most of the code to support this authentication can be included in a new plugin, we do need a method of hooking to the web3 initialization that happens in eth-lite, in order to add the authentication headers. This being said, I propose the following changes in the eth-lite plugin:

Add a configuration key authStoreUri that points to a custom auth adapter responsible for applying any needed modifications to the web3 provider

Example:
    "plugins": [
      ...,
      {
        "uri": "plugin://aleth.io/eth-lite",
        "config": {
            "nodeUrl": "http://my_besu_node:8545",
            "authStoreUri": "adapter://adetante/besu/auth-store"
        }
    }],

The AuthStore will have to implement the following interface:
interface IAuthStore {
    // This needs to be an @observable (will work b/c mobx instance is shared between plugins)
    // Alternatively we could use a more complicated observer pattern implementation
    isAuthenticated: boolean;
    // Alternatively we could pass just the provider, instead of the entire web3eth object
    applyLoginInfo(web3Eth: Web3Eth): void;
}

The web3 initialization code would be changed along the lines of this pseudo-implementation:

const authStore = await adapters.get("adapter://adetante/besu/auth-store").load();
when(() => authStore.isAuthenticated, () => {
    this.lastBlockWatcher.watch();
    authStore.applyLoginInfo(web3Eth);
})

There are a few gotchas though:

We need to fetch the adapter by its URI (this also means the besu plugin needs to be included BEFORE the eth-lite plugin, but that's ok). That means a data dependency between plugins, which I'm not sure is possible right now. I'll have to do some digging, we might have to make a few modifications to the plugin engine. I'll get back to you on that.
The when part needs to block/pause the initialization of the eth-lite data source, otherwise we'll get errors everywhere.

The besu plugin implementation could look like this:
import { IDataAdapter } from "plugin-api";
class AuthAdapter implements IDataAdapter {
    constructor(private authStore: AuthStore) {}
    async load() {
        return this.authStore;
    }
}

class AuthStore {
    @observable
    isAuthenticated: boolean;
    applyLoginInfo(web3Eth: any) {
        web3Eth.currentProvider.headers = [{
            name: "Authorization",
            value: `Bearer ${this.jwtToken}`
        }];
    }
    //...
}

interface IAuthProps {
    authStore: AuthStore;
}
const authModule: (authStore: Web3AuthStore) => IModuleDef<IAuthProps, {}, void> =
    (authStore) =>
        ({
            contextType: {},
            slotNames: [],
            dataAdapters: [],

            getContentComponent: () => import("./Auth").then(({ Auth }) => Auth),

            getContentProps() {
                // You can pass the store here, you don't need to wrap your component with a factory function
                return {
                    authStore
                };
            }
        });

// in plugin init
const authStore = new AuthStore();
api.addAdapter("adapter://adetante/besu/auth-store", new AuthAdapter(authStore));
api.addModule("module://adetante/besu/auth", authModule(authStore));
// NOTE: we pass the authStore directly to the module, but if we needed to do some async init, we could instead add it as a lazy dependency in the module's implementation, under `dataAdapters: [...]`

Please let me know if this approach sounds OK to you.

See the eth-lite modifications in https://github.com/Alethio/explorer-core-plugins/pull/59
You will have to checkout the latest ethereum-lite-explorer master branch, which supports this functionality (added with Alethio/cms#v1.0.0-beta.12)
After digging deeper into the plugin code, it becomes obvious that we have to block initialization until authentication is performed, otherwise everything will start throwing errors. On the other hand because the plugin engine expects all data sources to be loaded before actually rendering anything on the page, this means you can't define a module that renders the login form, but have to either:
a) Render the form manually in the blank page:
b) Redirect to a 3rd-party login URL - I'm not sure how this would work with Besu
For the first case, your custom plugin init code would look something like this:
let authStore = new AuthStore();
api.addDataAdapter("adapter://adetante/besu/auth-store", authStore);

if (!authStore.isAuthenticated) {
    const formEl = document.createElement("div");
    document.body.appendChild(formEl);

    ReactDOM.render(<Auth authStore={authStore} onLoginSuccess={async () => {
        ReactDOM.unmountComponentAtNode(formEl);
        document.body.removeChild(formEl);

        // Notify eth-lite plugin
        runInAction(() => {
            authStore.isAuthenticated = true;
            //...
        });
    }} />, formEl);
} else {
    // Notify eth-lite plugin
    runInAction(() => {
        authStore.isAuthenticated = true;
        // ....
    });
}

Thank you for your detailed answer! I had initially tried to implement it as a standalone plugin, I agree it's better than including Besu related features in eth-lite. But without the hook at web3 initialization, it was impossible without duplicating a large part of the plugin.
I'll start an implementation as you presented it, and I'll update this ticket with the info to use it.
Thanks also for highlighting how to use getContentProps instead of the factory function in the module definition, I hadn't noticed that!

Sure, let me know when you have something working, so I can publish the updated eth-lite plugin. You can also check the docs at https://github.com/Alethio/cms and if you get stuck creating the new plugin, you can also ask questions on our Discord server.

I released the first version of the plugin, it works with modifications on eth-lite (branch custom-auth-store) and explorer-lite (master).
Here is the github repo https://github.com/adetante/explorer-besu-plugin and the npm package https://www.npmjs.com/package/@adetante/explorer-besu-plugin.
Thanks for your patch & support

Published eth-lite @ 4.2.0
ethereum-lite-explorer @ 1.0.0-beta.10 Docker image is pending

Also a suggestion: if you render the form manually and don't depend on the global @alethio/ui theme provided by the host explorer app, you can use the next tag instead for easier form handling: https://alethio.github.io/ui/?path=/story/form--default


Unsynchronized scrolling of two scroll viewer in WinUI

Describe the bug
Facing unsynchronized scrolling of two scroll viewer in WinUI, in my scenario i am using two scroll viewer and updating the vertical offset of one scroll viewer based on another scroll viewer by using ChangeView method. But facing scrolling delay in scroll viewer, both scroll viewer is not scrolling even and in synchronized manner.
Steps to reproduce the bug

Run the sample.
Scroll any one scroll viewer using mouse scroll wheel.

Expected behavior
Both scroll viewer should be scrolled evenly in synchronized manner.
Screenshots
DemoVideo.zip
Version Info
WinUI NuGet package version = 3.0.0-preview4.210210.4
OS version = Windows 10 Pro

NuGet package version:
[Microsoft.WinUI 3.0.0-preview4.210210.4]

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context
Demo smple:
WinUIScrollDemo.zip
Note: This scenario works perfectly in WPF and Native UWP

Hello, @Ganeshamoorthy10
Seems, you are solving the same issue as I am. There are independent animations during the scrolling, which you cannot control. It could be solved by the composition layer as @Sergio0694 described in this post.

@RBrid can you weigh in?


"experimentalDecorators" and "types" properties can't coexist in tsconfig

Reported in gitter, I repro in 1.5-insider.
Have a tsconfig.json with "experimentalDecorators": true and "types": []. If you use a decorator in TS, you get that error "... set the experimentalDecorators option to remove this warning..." but if you delete the "types" property, then it does not complain about the decorator, as expected.

This issue was moved to Microsoft/TypeScript#10790


Starscream dependency on zlib

https://github.com/daltoniam/Starscream/pull/844
this prevents xcframeworks being spat out
https://github.com/supabase-community/supabase-swift/issues/38

Hi @johndpope
I decided to align the minimum supported platform of this library to the supabase-swift, that makes it possible to remove the starscream dependency, as you can check on https://github.com/supabase-community/realtime-swift/pull/11
Does that solve your problem?


Is this method also applicable for fer2013 data set? Why did the author not verify it on the most common fer2013 data set

The obtained accuracy and loss of Epoch 10/10, Loss: 0.6809, Validation Accuracy: 0.5688, when fine-tuning the DAN model on the Fer2013 dataset and loading the weights of rafdb_epoch21_acc0.897_bacc0.8275.pth, are as such. The significant difference in performance between different datasets can be attributed to several factors. It is possible that the data preprocessing and handling might not have been optimized for the Fer2013 dataset. Additionally, the introduction of the ImbalancedDatasetSampler class to address class imbalance might not have yielded a significant improvement in this case.


Changing the rules for evaluator and server validations.

@brendanbond then I actually feel even better about this change. If you look here https://github.com/formio/formio/pull/1682/files#diff-a7d5a18a3ab4285cc4ae2f08cbaf65996a2c773a4fc1866dc14f6e08bf9fed0b I had to add the "value" to the tests recently to get them to pass, and never identified what was happening and just figured it was benign enough to just add the "value" to get the tests to pass. This actually seems to have resolved that issue and now reverts it back to the way it would validate within 8.x.  I am going to run some more tests tomorrow to see if there are any other things that fail unexpectedly, but as far as I can tell, we should not let that keep this change from making 9.0.0.

closing, this work completed in #45


Update input when invoking function with mutable context

Motivation and Context

This change fixes #1443. There is a code path in SKFunctionExtensions.InvokeAsync where we don't update the context with the input from the user.
Description

Update the input context variable before invoking the SK function, to ensure the input gets passed through.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[ ] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

We should improve the test coverage for SKFunctionExtensions.cs but I think that should be done by someone on the kernel team, and is outside the scope of my change to fix the broken sample.


Issue on build.

go get -u github.com/ykzts/webp-proxy
github.com/harukasan/go-libwebp/webp
go/src/github.com/harukasan/go-libwebp/webp/decode.go:5:10: fatal error: webp/decode.h: No such file or directory
#include <webp/decode.h>
^~~~~~~~~~~~~~~
compilation terminated.
github.com/pixiv/go-libjpeg/jpeg
go/src/github.com/pixiv/go-libjpeg/jpeg/compress.go:6:10: fatal error: jpeglib.h: No such file or directory
#include "jpeglib.h"
^~~~~~~~~~~
compilation terminated.

$ sudo apt-get install libjpeg-dev libwebp-dev

or
$ sudo yum install libjpeg-dev libwebp-dev

[root@ip-172-31-35-97 ~]# go get -u github.com/ykzts/webp-proxy
github.com/harukasan/go-libwebp/webp
go/src/github.com/harukasan/go-libwebp/webp/decode.go:68: cf.format undefined (type C.struct_WebPBitstreamFeatures has no field or method format)
go/src/github.com/harukasan/go-libwebp/webp/decode.go:219: config.options.dithering_strength undefined (type C.struct_WebPDecoderOptions has no field or method dithering_strength)
[root@ip-172-31-35-97 ~]#

GitHub is not StackOverflow.


Still in being maintained ?

Is there a roadmap for the plugin ?

I'm still struggling to find a reasonable goal. It's hard to provide an optimal solution for SDI with this plugin due to the limitation of DeckLink products. I have to find a middle ground.
How do you want to use the plugin? What features do you want in the plugin? Any input is welcomed.

Hello Keijiro! Thank you for amazing stuff you make for unity community!
But a want ask a question - is there any chance to make this plugin for "Decklink"
capture work on osx ?

@keijiro I'm use external Intensity Shuttle device (usb3/thunderbolt2) and looks like it works thru the same DeckLink library as PCI capture cards.  Already tested my devices in openframeworks with  this addon [https://github.com/hanasaan/ofxDeckLink].

@grigM Thanks for the response. Yes, it would work with Intensity. It's a little bit troublesome to add macOS support though.

Hi @keijiro, is the new version of the desktop video 11 SDK supported?

@Filmengineers Currently I'm not working on this project, so there is no update for the new SDK.


Suppress format-all-mode error when no formatter is available

Having this on renders it difficult to work with debug-on-error, since a
lot of filetypes don't have formatters

Something is not quite right with this, as ... after a restart it's not suppressing the error. I'm not entirely sure why either.
(I swear I'm decent at this coding thing, but damn, does working on emacs configs confound me :) )

... except it is working now? For a moment it actually stopped suppressing the original errors. So, it's not my patch that's wrong, it's something in emacs' signal handling. So, please ignore my comment and feel free to merge; this works, it's computers that suck :)

Thanks!


feat: Adds a dry run to cli and server operations.

I think the deleteOne is probably the best place for this, this lets
all the code paths execute making it "accurate".
ref: #34

Merged in 1ac1af8320faa110bd20f3555cd8e870ab01a247 with slight alterations to outout.


[Bug] Releasing V key should finish shape, but doesn't

see #63

Fixed in version 1.318

This version is now available on the asset store, so closing ticket


Add ordering information to lines.color

This PR tries to be a bit more explicit about the possible values in @lines.color.
Closes #946

+1
--
p.
From: Andrew Hankinson @.>
Sent: Wednesday, June 15, 2022 12:51 PM
To: music-encoding/music-encoding @.>
Cc: Subscribed @.***>
Subject: Re: [music-encoding/music-encoding] Add ordering information to lines.color (PR #977)
@ahankinson commented on this pull request.

In source/modules/MEI.visual.xmlhttps://github.com/music-encoding/music-encoding/pull/977#discussion_r898208593:

     <datatype maxOccurs="unbounded">

       <rng:ref name="data.COLOR"/>

     </datatype>

   <remarks>

     <p>The value is structured; that is, it should contain a single color value or have

       the same number of space-separated values as the number of lines indicated by the

       lines attribute. The first value then applies to the lowest line of the staff.

       A line can be made invisible by assigning it the same color as the

I think we should strike this last sentence since data.COLOR allows alpha-channel colours, so it is possible to make a fully transparent ("invisible") line with the values in this attribute.
—
Reply to this email directly, view it on GitHubhttps://github.com/music-encoding/music-encoding/pull/977#pullrequestreview-1007831066, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABLSX3LJGREUJWEP2M3DXR3VPICYRANCNFSM5Y3WE3DQ.
You are receiving this because you are subscribed to this thread.Message ID<EMAIL_ADDRESS>

@ahankinson Are the recent changes OK with you?

Three approvals. Merging right now.


Revert "chore: update no-response workflow"

Reverts remix-run/examples#217

@mcansh nice catch 🙏🏼 fixed

By the way, I left 21 on purpose here, since it's the examples repository, and we want people to contribute at their own pace


[FEAT] use capital letters for match names

Hi,
it would be nice if i could use capital letters for my match names (for example Darius instead of darius).
I think this will produce more nice looking names in Frigate in german (e.g. in sub-labels).
Is this already possible at this moment?
Thank you very much :)
Darius

to be clear, frigate already capitalizes sub labels in the ui


fix: sphinx finally deprecated old add_source_parser in 3.3, returning AttributeError

This addresses https://github.com/CrossNox/m2r2/issues/13
Given add_source_parser() in sphinx 3.3 has changed the signature (https://github.com/sphinx-doc/sphinx/pull/8280), invocations with the extra params result in AttributeError exceptions, not TypeError, so adding this condition to the failback logic to consume the latest signature when that occurs.

@CrossNox , any chances of reviewing and potentially merging this? We cannot use the plugin in the latest sphinx releases...

Locally this fix solves my problem.  Using OSX Mojave, python 3.7.

Will review shortly, sorry, it's been a rough week

@dcaba thanks so much for the PR!
To everyone else: sorry for the delay. I'll create a tag and release ASAP.

Hi @CrossNox : better late than never. Thanks in any case for bringing the fix in the end, i see the new release is now public. BTW, what should we expect regarding this project maintenance? Of course I just aim for a best-effort maintenance, but if you are afraid you don't have too much focus, should we try to bring in more maintainers?

IMHO, despite my personal situation at any time given (which rn depends on university deadlines) m2r failed because there was a single mantainer, which is a SPOF. I'll be opening a new issue explaining all this and making clear that I'd prefer to have other people involved as collaborators. Not just because of new features, but because any changes such as seen these past weeks breaks a fair amount of projects, and m2r2 should quickly give support to it. That should not depend on a single person, even if they had all the time for it.

Hi @CrossNox : better late than never. Thanks in any case for bringing the fix in the end, I see the new release is now public. BTW, what should we expect regarding this project maintenance? Of course I just aim for a best-effort maintenance, but if you are afraid you don't have too much focus, should we try to bring in more maintainers, or should we just assume the delay was a result of a very exceptional situation?

Hi. Yes, we are on the same page: however, not in a position to say what you should do with your repo, but happy to see you just want to do the best for the project (some other maintainers do not want to share their "pets", no matter if that is the best for them or not ;) )


Update Readme.md

Added info on access to the ZIH HPC system

Awesome, thank you @njurenaite !
I'm also going to invite you to the repository.

Thanks!


Latent bug in device_atomic_functions, atomicInc, for reductions

The cuda analogue of atomicInc is documented to do:

reads the 32-bit word old located at the address address in global or shared memory, computes ((old >= val) ? 0 : (old+1)), and stores the result back to memory at the same address. These three operations are performed in one atomic transaction. The function returns old.

This is used by reduction.cu with a comment showing that the author knew this was the behaviour

// atomicInc increments 'timestamp' and has a range [0, NumTeams-1].
// It resets 'timestamp' back to 0 once the last team increments
// this counter.
unsigned val = __kmpc_atomic_inc(timestamp, NumTeams - 1);
IsLastTeam = val == NumTeams - 1;

Our implementation of this function is

unsigned atomicInc(unsigned *address, unsigned max) {
if (*address >= max)
return *address;
else
return atomic_inc_unsigned(address);
}

This is not atomic and does not write a zero to *address in the first part of the branch. I don't have a test case that fails due to this.

The HW has instructions that do this atomically, e.g. global_atomic_inc and ds_inc_u32, and there are amdgcn intrinsics that can be used to generate them.  We might want to go through a new OCKL function rather than directly invoking the intrinsic.

That is great news, thanks. I couldn't find a corresponding intrinsic in the gcc/c11/opencl set but didn't think to look at the amdgcn specific ones.

A clang builtin was introduced in https://reviews.llvm.org/D80804 and used in the devicertl shortly afterwards.


Can't use set_body in pipeline CE

set_body referes to an overloaded member of PipelineBuilder and it looks like overloaded members can't be used in CEs. The compiler has to say the following about that:

The custom operation 'set_body' refers to a method which is overloaded. The implementations of custom operations may not be overloaded.

Is it possible to just rename the overload that works on strings to something like set_string_body or set_body_from_string?

Now that F# 6.0 supports overloads on CEs by default, should we consider unfixing this issue?


Doesn't build on Fedora 40. No make errors just plain stops

cmake build runs without errors but the make command gives the following error.
[  1%] Built target vkbootstrap
[ 28%] Built target sdl_headers_copy
[ 92%] Built target SDL2
[ 96%] Built target imgui
[ 96%] Built target fmt
[ 96%] Building CXX object src/CMakeFiles/engine.dir/main.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/vk_engine.h:6,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/main.cpp:1:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 96%] Building CXX object src/CMakeFiles/engine.dir/vk_initializers.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/vk_initializers.h:6,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/vk_initializers.cpp:1:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 96%] Building CXX object src/CMakeFiles/engine.dir/vk_descriptors.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/vk_descriptors.h:3,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/vk_descriptors.cpp:1:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 96%] Building CXX object src/CMakeFiles/engine.dir/vk_pipelines.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/vk_pipelines.h:2,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/vk_pipelines.cpp:1:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 96%] Building CXX object src/CMakeFiles/engine.dir/vk_engine.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/vk_engine.h:6,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/vk_engine.cpp:2:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 98%] Building CXX object src/CMakeFiles/engine.dir/camera.cpp.o
In file included from /home/nikhil/dev/VulkanApps/vkguide/src/camera.h:2,
                 from /home/nikhil/dev/VulkanApps/vkguide/src/camera.cpp:1:
/home/nikhil/dev/VulkanApps/vkguide/src/vk_types.h:24:73: warning: backslash-newline at end of file
   24 | #define VK_CHECK(x)                                                     \
[ 98%] Linking CXX executable /home/nikhil/dev/VulkanApps/vkguide/bin/engine
CMake Error: cmake version 3.28.2
Usage: /usr/bin/cmake -E <command> [arguments...]
Available commands:
  capabilities              - Report capabilities built into cmake in JSON format
  cat [--] <files>...       - concat the files and print them to the standard output
  chdir dir cmd [args...]   - run command in a given directory
  compare_files [--ignore-eol] file1 file2
                              - check if file1 is same as file2
  copy <file>... destination  - copy files to destination (either file or directory)
  copy_directory <dir>... destination   - copy content of <dir>... directories to 'destination' directory
  copy_directory_if_different <dir>... destination   - copy changed content of <dir>... directories to 'destination' directory
  copy_if_different <file>... destination  - copy files if it has changed
  echo [<string>...]        - displays arguments as text
  echo_append [<string>...] - displays arguments as text but no new line
  env [--unset=NAME ...] [NAME=VALUE ...] [--] <command> [<arg>...]
                            - run command in a modified environment
  environment               - display the current environment
  make_directory <dir>...   - create parent and <dir> directories
  md5sum <file>...          - create MD5 checksum of files
  sha1sum <file>...         - create SHA1 checksum of files
  sha224sum <file>...       - create SHA224 checksum of files
  sha256sum <file>...       - create SHA256 checksum of files
  sha384sum <file>...       - create SHA384 checksum of files
  sha512sum <file>...       - create SHA512 checksum of files
  remove [-f] <file>...     - remove the file(s), use -f to force it (deprecated: use rm instead)
  remove_directory <dir>... - remove directories and their contents (deprecated: use rm instead)
  rename oldname newname    - rename a file or directory (on one volume)
  rm [-rRf] [--] <file/dir>... - remove files or directories, use -f to force it, r or R to remove directories and their contents recursively
  sleep <number>...         - sleep for given number of seconds
  tar [cxt][vf][zjJ] file.tar [file/dir1 file/dir2 ...]
                            - create or extract a tar or zip archive
  time command [args...]    - run command and display elapsed time
  touch <file>...           - touch a <file>.
  touch_nocreate <file>...  - touch a <file> but do not create it.
  create_symlink old new    - create a symbolic link new -> old
  create_hardlink old new   - create a hard link new -> old
  true                      - do nothing with an exit code of 0
  false                     - do nothing with an exit code of 1

make[2]: *** [src/CMakeFiles/engine.dir/build.make:248: /home/nikhil/dev/VulkanApps/vkguide/bin/engine] Error 1
make[2]: *** Deleting file '/home/nikhil/dev/VulkanApps/vkguide/bin/engine'
make[1]: *** [CMakeFiles/Makefile2:422: src/CMakeFiles/engine.dir/all] Error 2
make: *** [Makefile:136: all] Error 2

Also the fastgltf library didn't build cuz of some unknown errors (might be due to gcc 14, as I have seen a few issues in that repo regarding the same. I intend to use diff lib for loading gltf models when need arises but for now I have removed it from cmakelists. It produced no error regarding it but just wanted to inform for the clarity)

Marked as completed as I was able to fix it by removing the custom command at the end of CmakeLists.txt file in the src directory, as it wasn't required in non dll based systems like Linux based distros


windows-compatible build script

Added powershell script enables build on windows. (fixing the problem that blob syntax** is not usable in windows powershell)
Added new npm script option for building use the powershell script.
Run npm run build-win to use the script.
Note: npm run build will build the file /src/foo/bar.tx into /dist/foo/bar/index.js. Where as this script will build /src/foo/bar.tx into /dist/foo/bar.js which might be a little bit different.

@zeowang any updates on this?

Had added the passing parameter: when invoking npm run test:api, one can add param like -- wiki.stack-template 8000 LAZY to indicate parameters. If nothing is added then it will use some default template-port-dockerOption parameters in the script.
Hot reload works, just some minor issue left on ctrl-c to end the background server...


TvRecyclerView.setItemSelected  is useless

just like the title

This problem has been resolved, please use version 1.0.2.

If it is possible，how can i contact you?

yes, if you have any question about TR, you can open issues


FastAI (lib and audio module) V1->V2 Migration

Our aifororcas_livesystem models are trained with FastAI v1 and fastai_audio (the V1 version of an audio module built on top of FastAI v1). FastAI v2 is now the preferred version for training models. The benefits of replacing our usage of v1 with v2 (for both FastAI library and fastAI audio module) are plentiful:

Documentation of v1 audio module is very poor (hard to debug, to find answers to questions, to understand by newcomers). Documentation of v2 audio is much better, and project is still in actively-maintained by FOSS community.
There are lots of library version conflicts between audio v1 library and some of our other libraries (ex. librosa). Package management becomes less challenging if we move to FastAI v2 and fastaudio (the v2 version of fastai_audio).
It'll be nice to leverage new FastAI v2 technology as we build more sophisticated models. FastAI v1 is no longer receiving non-bug-fix updates

A branch is ready, but not back compatible with FastAIv1 models here: https://github.com/bnestor/aifororcas-livesystem


Features for start up in seconds and rewind and fast forward

I added 4 main features:

Start the video (startVideoAtSeconds) at a specific time in seconds
Rewind video in seconds: backInSeconds
Fast forward video in seconds: forwardInSeconds
Exposed lastPlayInSeconds.  This allows to determine where the user stopped playing a video in seconds. For later start up at that point in time.

I think I added most of the documentation in code and updated the README.md to support a version bump.  I tagged mine as 0.4.0 since I saw some 0.3.x versions in your repo.  Thanks for the initial release of the project.  More features comin' right up..   I'd love to add a caching layer.  I was using a previous open source project (GSPlayer GitHub) but it had some visual issues and wasn't written in SwiftUI and I'd rather go that route and learn more.

ok, some issues with the macOS example. I was mostly focusing on iOS. But I need the macOS changes too at some point. Not sure why yet but the back / rewind buttons aren't working yet for macOS.  I'll get it figured out sometime soon.

ok all done. I tagged it as 0.4.2.  If needed I can switch he pull request to that.  I also changed to 11.0 Mac OS deployment target.  it was mostly for the icon system sets.

@nneuberger1 can you please create a separate feature branch for your PR for example: feature\rewind_fast_forward and instead of targeting the master branch target the develop branch?
That will make it easier for me to do the merge of your changes.

@nneuberger1 can you please create a separate feature branch for your PR for example: feature\rewind_fast_forward and instead of targeting the master branch target the develop branch?
That will make it easier for me to do the merge of your changes.

Will do...

Closed in favour of this PR: https://github.com/SergioEstevao/SVEVideoUI/pull/7


chore(main): release veto 0.1.1

:robot: I have created a release beep boop
0.1.1 (2024-04-12)
Bug Fixes

veto: add keywords (1f5672c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fuf-stack/uniform/releases/tag/veto-v0.1.1 :sunflower:


[BUG] about tree-sitter

Describe the bug
tree-sitter   not work
protobuf-ts-mode
Emacs version
Run M-x emacs-version and put its output here:
GNU Emacs 29.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.38, cairo version 1.17.8) of 2023-09-01
To Reproduce
Steps to reproduce the behavior:

add this in config.el

(use-package protobuf-ts-mode
  :straight t
  :ensure t
  :mode ("\\.proto\\'" . protobuf-ts-mode))

2.open one proto file
Screenshots

this file already in protobuf-ts-mode
but It seems that the syntax tree is not effective and there is no color keyword prompt.

I also tried other languages, such as c#, although the csharp-ts-mode & so files are already there, but the syntax is still not colored, and it still doesn’t seem to work.

Additional context
When I open the proto file or switch protobuf-ts-mode, I will be asked to download libtree-sitter-protobuf.so* every time
tree-sitter not work well
M-x treesit-auto-install-all
It keeps prompting that protobuf has downloaded the .so file in time.

I tested it with c++ & c treesit and it works fine but there are some issues with csharp and protobuf I know you don't use these thanks for your time

I've just tried this and it seems buggy. After installing protobuf-ts-mode and opening a .proto file, treesit-auto keep asking to download the library (even though it is installed).
I will temporarily disable protobuf-ts-mode in treesit-auto until it gets fixed upstream.
@donneyluck Can you please open an issue in the treesit-auto upstream repo?

ok i will open an issue in the treesit-auto upstream repo


Bug: [DebugBar] block by CSP

PHP Version
8.2
CodeIgniter4 Version
4.4.4
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Windows, Linux
Which server did you use?
apache
Database
No response
What happened?
Debugbar use inline style ,  in mode development and CSPEnabled true will show many error in console browser

Steps to Reproduce
set  CSPEnabled = true,
set ENVIRONMENT to development
Expected Output
No error
Anything else?
No response

Thank you for reporting.
If you can fix these, please send a PR.
https://github.com/codeigniter4/CodeIgniter4/blob/develop/contributing/pull_request.md

any update on this ? i would really love to have this update to the debugbar, so annoying with csp enabled.

@crustamet See #8411