diffrent validation not work correctly

Laravel Version: #.#.#
PHP Version: #.#.#
Database Driver & Version:

Description:
'result1'=>'nullable|numeric|different:
result2|different:result3|different:result4|different:result5|different:result6|
different:result7|different:result8|different:result9|different:result10|different:result11|different:
result12|different:result13|different:result14|different:result15|different:result16|different:
result17|different:result18|different:result19|different:result20',
		'result2'=>'nullable|numeric|different:result1|different:
		result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result3'=>'nullable|numeric|different:result1|different:
		result2|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result4'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result5'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result6'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result7'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result8'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result9'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result10'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result11'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result12'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result13'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result14'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result15|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result15'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result16|different:
		result17|different:result18|different:result19|different:result20',

		'result16'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:
		result17|different:result18|different:result19|different:result20',

		'result17'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result18|different:result19|different:result20',

		'result18'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result19|different:result20',

		'result19'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result20',

		'result20'=>'nullable|numeric|different:result1|different:
		result2|different:result3|different:result4|different:result5|different:result6|different:
		result7|different:result8|different:result9|different:result10|different:result11|different:
		result12|different:result13|different:result14|different:result15|different:result16|different:
		result17|different:result18|different:result19'

Steps To Reproduce:

You would, at a minimum, need to explain why you don’t think this is working. What is your expectation vs. what is the actual result.
You may actually get help faster on one of the community help sites like Laracasts, Laravel.io, Laravel’s Discord channel, or Larachat Slack.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Toggler not splitting traffic as expected

As noted.
The cloudfront lambda responsible for splitting traffic is not working as expected. When set to 50/50, it seem to split traffic 1/2.
Needs investigation.

So this turned out to be user error.
I thought the range property was for specifying how to split the traffic into the 2 conditions. However, the traffic is always split 50/50 and the range determines the amount of traffic to include in that split.
By specifying a range of [0, 50] only half of total traffic was included and then half of that had the toggle set to true, which was why we were seeing about a third of all traffic with the toggle set to true.
N.B. We still need to be careful using the when property to determine when cookies are set if client side routing is involved.


[AlgorithmSelection] Rename BackendSelection, introduce Backend type

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

Project coverage is 48.23%. Comparing base (ceb26a7) to head (8a70717).
Report is 11 commits behind head on main.

:exclamation: Current head 8a70717 differs from pull request most recent head 51d64f3. Consider uploading reports for the commit 51d64f3 to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1407      +/-   ##
==========================================
- Coverage   49.23%   48.23%   -1.00%
==========================================
  Files         110      123      +13
  Lines        8320     8769     +449
==========================================
+ Hits         4096     4230     +134
- Misses       4224     4539     +315

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


Remove Redis Cache from R2 Infrastructure

Redis Cache is no longer used by the Services and should be removed from the R2 Infrastructure Deployment.

Implementation of Redis Cache has been removed out of R2 Infrastructure Templates.


Remove API private from Extractor

Custom Extractor classes are already being used in production and the Private API warning in the docs is confusing for developers.
https://www.rubydoc.info/gems/blueprinter/Blueprinter/Extractor

@cagmz thanks for doing this, it makes sense to make the base Extractor public so that others can inherit from it and create their own custom extractors. However, would you mark AssociationExtractor, AutoExtractor, BlockExtractor, HashExtractor, and PublicSendExtractor as @api private? I don't think we can promise that those won't change.

Closing in favor of https://github.com/procore/blueprinter/pull/182 .


1.2.0-criteo10

Signed-off-by: Jean-Francois Weber-Marx<EMAIL_ADDRESS>

Codecov Report

Merging #14 into criteo-dev will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           criteo-dev      #14   +/-   ##
===========================================
  Coverage       80.11%   80.11%
===========================================
  Files              85       85
  Lines            8910     8910
  Branches         1906     1906
===========================================
  Hits             7138     7138
  Misses           1504     1504
  Partials          268      268

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 72e2fff...248d32f. Read the comment docs.


[BUG]: multi audio selection

Version
v6 (Beta)
What platforms are you having the problem on?
Android
Architecture
Old architecture
What happened?
A bug happened! I am trying to implement multi audio from the m3u8 URL it is working on the web but not on mobile i am selecting the audio track after onload,
I want to change the audio from this URL also it does not play the default selected audio on this player
URL : https://video.gumlet.io/65bce2937b739aad127489d4/65d5aa5b1150436a0cdffb28/main.m3u8
Reproduction
Step to reproduce this bug are:

having the same issue but only in ios

can you detail how you select the track ?
Did you try to reproduce the issue in sample from the project ?

no update, audio track change works fine with basic sample. let's close

it's working

But the video selection only working in android, in IOS didn't get any video tracks from onLoad method

But the video selection only working in android, in IOS didn't get any video tracks from onLoad method

Yes, I think we need to have a deep thinking on video track selection due to ABR.
Thank you for the feedback

Sure, could you please provide me with a timeline for when the feature will be available?


keyInSelect has a limit of 35 array elements

I have to display a huge list of directories so that the user can choose from one of them. What is the reason for the limit of 35?

Hi @smks, thank you for the comment.

For the user, the list should not be too long. The size of many terminal windows is small, then your app should have a pagination (like more command) to show the long list.
keyInSelect is used for simple interface. 0 .. 9, A .. Z keys are found easily by user.
The keys other than the 36 keys (includes 0) are not many, if you want to receive multiple keys such as the item number for long list, you can use questionInt method. But I think that it's not good idea as I said. The list should be split. For example: https://github.com/anseki/readline-sync#itemscount

I decided to use a columnify npm package, and built 4 columns of options to format and compact it a bit better. I then use a questionInt to grab the index. Great package by the way!

😃


optimize memtable desc scan

What have you changed? (mandatory)

Update rust-rocksdb to branch tikv-2.1.9-desc, which optimize memtable desc scan.

What are the type of the changes? (mandatory)

Improvement

How has this PR been tested? (mandatory)
It has been tested by inlineskiplist_test in Rocksdb repo.
Does this PR affect documentation (docs) or release note? (mandatory)

No

Does this PR affect tidb-ansible update? (mandatory)

No

Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

/release


Support for Postgres Sequences

In Postgres you can define you custom sequences.
it would be awesome to define them with schema_plus
here is an example how we use it in our migration right now.
execute "CREATE SEQUENCE invoice_number_seq OWNED BY invoices.invoice_number INCREMENT BY 1 START WITH 10000"

execute "ALTER TABLE invoices ALTER COLUMN invoice_number SET DEFAULT nextval('invoice_number_seq')"

+1 (can we vote for features ?)

@zedalaye sure you can vote -- but I'm afraid it won't do much good unless you can also vote in a few extra hours a day or days a week.
I'd be happy to accept a PR.   But I'm unlikely to add any new features myself.  (Unless I happen to need them for one of my day jobs :)


.tools: repo validation tool

Initially only a DCO validation for travis
https://github.com/opencontainers/specs/issues/90
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

yay. updated, and now that travis is enabled you can see that it also validated the DCO in this PR. :-)

@tianon review?

Adorbs. :+1:

(LGTM)

updated ... PTAL!

GitHub seems to have eaten my emailed response, so I'll repeat it here:
On Wed, Sep 09, 2015 at 03:15:53PM -0700, Vincent Batts wrote:

updated ... PTAL!

8b55acffb looks good enough to me.  I'd still recommend the --format
updates suggested in 1, but if you'd rather maintain it the way it
is, then I'm happy enough ;).

@wking i'm not going to worry about depending on their git version.

nit: not a huge fan of hiding code. tools without the .tools would be better IMHO

good start, better than the nothing we have now. LGTM for merge.

@philips i only hid it because it's like project housekeeping. If it were in ./tools/ or just ignored but sitting with a name like validate.go it may be expected for specs tools or validation. right?

we can move it out later, or just have that kind of git validation be go getable for travis use. For now, I'm going to merge this for DCO enforcement of PRs

lol. feature needed!

On Wed, Sep 09, 2015 at 08:17:27PM -0700, Vincent Batts wrote:

we can move it out later, or just have that kind of git validation
be go getable for travis use…

This sounds good to me, especially since “I want to validate PRs
against our project's commit policy” seems like something that other
repositories might want to use too.

Yup
On Sep 9, 2015 23:39, "W. Trevor King"<EMAIL_ADDRESS>wrote:

On Wed, Sep 09, 2015 at 08:17:27PM -0700, Vincent Batts wrote:

we can move it out later, or just have that kind of git validation
be go getable for travis use…

This sounds good to me, especially since “I want to validate PRs
against our project's commit policy” seems like something that other
repositories might want to use too.
—
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/specs/pull/167#issuecomment-139107332.


Typo in CMakeList?

https://github.com/codr4life/snabl/blob/cffb3ef3a7231d7a78cb923967d22cebeac5ccd3/CMakeLists.txt#L19
I may be off-base, here, but I think this is supposed to say src/snabl/*.hpp?

Nice catch, fixed.


Can the validation work on models returned from a computed

Can the validation work on models returned from a computed?

If i tell you the truth I didnt test it but it should

I've been unable to get it working with a model returned from a computed, it seems like the validations do not get applied.

I get errors when calling .validate and if I include $error in the markup it errors

Probably the computed removes the validator internal variables but I will take note and think a way to do it for next versions :)

I am preparing a full rework of the component using full ES6 syntax with classes, proxies and other stuff. This way will be much more powerful, and easy to develop.
I didn't reach the computed properties so I can't tell you yet if it is possible, but if you have any other ideas of enhacements and improvements is a good moment contribute :)

New version almost ready 😃
If I didn't understand you wrong, includes all features you requested, even computed.
Unfortunally it is not compatible with current version as the new version is built on top of ES6, this means classes, proxies, maps, destructuring etc. This means that the validator has brand new architecture , clear, easy to understand and hopefully more open to contributing.
I also decided to chage its name, as the owner of vue-model-validator ignored my messages trying to transfer me the package name (abandoned for more than 3 years) so the new version will be called vue-daval which I like and is shorter (vue-DAtaVALidator) hehehe.
I'll let you know once the docs are updated so in case you want to give it a try, you can send me comments and some feedback.
Really appreciate your time and comments.
Best regards!

Thanks for the update, I look forward to trying it out.

Hello, I presume the new data validator is finished.
 :)
It has many improvements and enhacements that other validators don't have.
Regards!


Generate AWS X-ray compatible trace IDs

What feature do you want to see added?
It would be very useful when using AWS X-Ray to have the plugin be able to generate X-Ray compatible trace IDs. The awsxrayexporter chokes when it encounters non-xray ids. I'm not aware of other ways to convert or process non-xray IDs in flight at the otel-collector.
`2024-05-24T10:14:53.225Z	debug	awsxrayexporter@v0.78.0/awsxray.go:114	Error translating span.	{"kind": "exporter", "data_type": "traces", "name": "awsxray", "error": "invalid xray traceid: b47fb1759d3adef02fac9043e6d0354b"}`

I appreciate that vendor specific support might not be desirable but AWS might be a large enough of a use case to be considered, I'm not aware of other vendors using their own ID formats.
Upstream changes
The AWS distribution for the Java agent patches in support for generating X-ray IDs, I wonder if this could be a toggle based on a configuration option in the Jenkins plugin.

https://github.com/aws-observability/aws-otel-java-instrumentation/blob/v1.32.0/awsagentprovider/src/main/java/software/amazon/opentelemetry/javaagent/providers/AwsTracerCustomizerProvider.java
AWS Java Agent - how it works

Are you interested in contributing this feature?
No response

I think I've found the answer, X-Ray started supporting W3C trace IDs ~8 months ago so no need to generate X-Ray format at the source. ADOT Collector >= v0.34 is required.

https://aws.amazon.com/about-aws/whats-new/2023/10/aws-x-ray-w3c-format-trace-ids-distributed-tracing/

Thanks @hhtpcd . Can we then close this issue?

Sure can - I've tested the plugin with the ADOT Collector and it works like a charm. Thanks for the plugin! ❤


input type email does not render email alias

I was going crazy trying to figure out why the email alias was not working, turns out input type="email" will break it. Is this a known issue? I couldn't find anything about it.

Related to #828... modern browsers no longer support selecting text in input type email and number. See that other issue for more details.

Any update on this? I realize this is a few years later, but I'm having the same issue.


Add CodeQL Workflow for Code Security Analysis

Summary
This pull request introduces a CodeQL workflow to enhance the security analysis of this repository.
What is CodeQL
CodeQL is a static analysis tool that helps identify and mitigate security vulnerabilities. It is primarily intra-function but does provide some support for inter-function analysis. By integrating CodeQL into a GitHub Actions workflow, it can proactively identify and address potential issues before they become security threats.
For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/).
What this PR does
We added a new CodeQL workflow file (.github/workflows/codeql.yml) that

Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience).
Runs daily.
Excludes queries with a high false positive rate or low-severity findings.
Does not display results for git submodules, focusing only on our own codebase.

Validation
To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code.
Using the workflow results
If this pull request is merged, the CodeQL workflow will be automatically run on every push to the main branch and on every pull request to the main branch. To view the results of these code scans, follow these steps:

Under the repository name, click on the Security tab.
In the left sidebar, click Code scanning alerts.

Is this a good idea?
We are researchers at Purdue University in the USA. We are studying the potential benefits and costs of using CodeQL on open-source repositories of embedded software.
We wrote up a report of our findings so far. The TL;DR is “CodeQL outperforms the other freely-available static analysis tools, with fairly low false positive rates and lots of real defects”. You can read about the report here: https://arxiv.org/abs/2310.00205
Review of engineering hazards
License: see the license at https://github.com/github/codeql-cli-binaries/blob/main/LICENSE.md:
Here's what you may also do with the Software, but only with an Open Source Codebase and subject to the License Restrictions provisions below:

Perform analysis on the Open Source Codebase.

If the Open Source Codebase is hosted and maintained on GitHub.com, generate CodeQL databases for or during automated analysis, CI, or CD.

False positives: We find that around 20% of errors are false positives, but that these FPs are polarized and only a few rules contribute to most FPs. We find that the top rules contributing to FPs are: cpp/uninitialized-local, cpp/missing-check-scanf, cpp/suspicious-pointer-scaling, cpp/unbounded-write, cpp/constant-comparison, and cpp/inconsistent-null-check. Adding a filter to filter out certain rules that contribute to a high FP rate can be done simply in the workflow file.

Thanks but I would prefer to try it before merging in the GH workflow.

@s-hadinger Checking in on any updates?

I'm confused. All the CI jobs are failed. How to make it useful?

@b4yuan It seems to be broken...

@s-hadinger @skiars Can you show a screenshot of the failed job?

https://github.com/berry-lang/berry/actions/runs/6937597371
The action failed, but there doesn't seem to be a more specific log.

This script fail_on_error.py is invoked to force the entire workflow to fail if the CodeQL analysis finds an error. This isn't because the workflow doesn't work--it's because CodeQL found a bug (error) and this script forces it to fail so you can more easily visually see there's an error

Got it. But how do we see the error?

Yes, it's useless if you can't get the error message...

You can find results under the Security tab in Code Scanning

I'm still confused. The errors returned are coded this way on-purpose. I don't see any obvious alternative. Can we silence them?

If you click the checkmark to the left of the error, you can dismiss it as "false positive", "won't fix", etc. This way you can dismiss errors for code that maybe doesn't follow standard code practice, but was done so for a specific reason.

You can find results under the Security tab in Code Scanning

I found it.

However I don't think the Analysis is necessary to block the PR since we can see the report in Security and handle it.

Of course, you can modify codeql.yml by commenting out:
  pull_request:
    branches: '*'

or anything else that you may wish to change.


re-hide modules

The _oasis file lists all but the main Oloop module as InternalModules. This is causing some typing problems, which I resolved temporarily by exposing all modules in c465761bec33ab5d5bf79b712001643afa4a78bf.
To reproduce the problem, path pin the repo and git checkout 95fa79aac8f01733a663c143b0d0761f81d8b509, the commit before c465761bec33ab5d5bf79b712001643afa4a78bf. Then try the following two cases:
cd to your working directory and launch utop from there, which will cause the checked-in .ocamlinit file to be used:
utop # let f (x:Oloop.Script.Evaluated.phrase) = match x.Oloop.Script.Evaluated.outcome with `Eval _ | `Uneval _ -> ();;
val f : Oloop.Script.Evaluated.phrase -> unit = <fun>

Now, opam install oloop and try the same thing with the installed version of oloop:
utop # #require "oloop";;
utop # let f (x:Oloop.Script.Evaluated.phrase) = match x.Oloop.Script.Evaluated.outcome with `Eval _ | `Uneval _ -> ();;
Error: This pattern matches values of type [? `Eval of 'a ]
          but a pattern was expected which matches values of type
          Oloop.Outcome.merged Oloop_outcome.t

Do you intend Oloop_core2 to be used externally?

Do you intend Oloop_core2 to be used externally?

No. It's definitely for internal use only.

Thanks, so you just have to expose the relevant modules. I wasn't sure if there's another solution.

On Fri, 8 May 2015 06:38:00 -0700, Ashish Agarwal wrote:

Thanks, so you just have to expose the relevant modules. I wasn't sure if there's another solution.

Not sure what you mean.  What kind of "other solution" do you have in mind?

The API is meant to require that all sub-modules be accessed as Oloop.Foo rather than Oloop_foo, so I thought in theory Oloop_foo shouldn't have to be exposed.
Probably I don't understand what InternalModules does? The oasis documentation says these modules are "not exported", but how is that accomplished?

On Fri, 8 May 2015 08:18:51 -0700, Ashish Agarwal wrote:

The API is meant to require that all sub-modules be accessed as Oloop.Foo rather than Oloop_foo, so I thought in theory Oloop_foo shouldn't have to be exposed.
Probably I don't understand what InternalModules does? The oasis documentation says these modules are "not exported", but how is that accomplished?

I do not remember for sure but I think this is as simple as the .cmi not being distributed.


Adding SCIP package in simple words

Hi,
Could anybody describe me how I can add "SCIP" solver to the Julia in very simple words. I have just started working with Julia and README file description seems too complicated to me.
Thanks.

Unfortunately, the installation is not completely automatic and the steps described in the README are necessary. To help you better, could you answer these questions:

what operating system do you use?
have you managed to download and compile the SCIP solver itself?
what steps from the README have you tried, or do need explanation of?

Thanks for answering.

My operating system is windows 10
I am using both Julia 0.5.1 and 0.6.0
I need to solve my optimization problem in Julia since I implemented it in Julia. So, I have not tried to use compiler itself
The installation consists of 4 main steps:

there is two codes in README to download and untar SCIP as below:

wget http://scip.zib.de/download/release/scipoptsuite-4.0.0.tgz
tar xzf scipoptsuite-4.0.0.tgz
non of these codes works for me in Julia. In fact, I downloaded the SCIP from its website manually and unzip it. Then, what should I do next?

I do not know how to make share library. How I can use the below code:

make SHARED=true GMP=false READLINE=false ZLIB=false scipoptlib

Accessing library: what should I need exactly in this step.

step 4 is for adding package in Julia which might be accomplished by using below code:
Pkg.add("SCIP")

Sorry, but Windows is not currently supported.
There used to be a note, but I must have been lost, so I'm adding it again: #58.


Community store won't update list

The list to update the store automatically doesn't work after attempt of doing redirecting code.

aight, I have to trace what happens after the redirect.
It could be something else with the URL changes though.
Give me a day, exhausted today.

aight, I have to trace what happens after the redirect.
It could be something else with the URL changes though.
Give me a day, exhausted today.

I also forgot that I didn't get redirect to fully work. I'm pretty sure for updating code written in Python is that the extra lines in the Json is causing that issue.

In case you forgot our conversation in the discord, the reason the sources are no longer updating is because my AltSourceParser code uses Pythons standard json library to read the files. Since you don't trim the markdown headers before loading the file, it is technically invalid json. For now, the easy solution is to simply trim the header before using it, and then add the headers after the updates are complete.
Also, I will note that I am currently in the process of refactoring the code and creating a PyPI package in this repository (https://github.com/noah978/AltSourceParser) which should make the code cleaner and easier for you and others to use to auto-update your source.

Check out #2 for my changes to fix all the issues and get the update script and workflow up-to-date

Instead of using markdown redirect we could use cloudflare since that's been added recently and this can apply to apps.sidestore.io also.

@Spidy123222 You mentioned this is still the case and is likely related to https://github.com/SideStore/SideStore/issues/103 - so I'll mark that issue as a Soft Launch milestone.


docs: Fix simple typo, refereces -> references

There is a small typo in src/flash/flash-audio-ogg/flacc/oggvorbis.c.
Should read references rather than refereces.

Coverage remained the same at 74.376% when pulling ae5966790cdf3db8ed64c203f944416d02e24f7d on timgates42:bugfix_typo_references into d8a667fd65560093fb227700a82805600ec9e8e3 on mediaelement:master.

@timgates42 thanks for contributing to mediaelementjs.


[reviewable] Integrate @superset-ui/{core,color,chart} modules

Delete files that are already extracted to @superset-ui
Update references to the files above to point to corresponding @superset-ui code.
Update color module usage to utilize the new SequentialScheme function to create linear color scale.
Remove core-js from vendor-major hard-coded bundle. The core-js comes from babel-polyfill and by enforcing it into vendor-major causes some issues.

@williaster @conglei @graceguo-supercat @michellethomas @xtinec @mistercrunch

Codecov Report

Merging #6234 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6234   +/-   ##
=======================================
  Coverage   76.85%   76.85%
=======================================
  Files          47       47
  Lines        9393     9393
=======================================
  Hits         7219     7219
  Misses       2174     2174

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 1473e2c...09bcf1e. Read the comment docs.

@kristw there's a conflict now, looks fixable with the web UI possibly 🤔

conflict fixed


Add vue3-chart-v2 to Chart section

General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ  What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Fix
[ ] Feature

Checklist

ℹ  Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉  Put an x in the boxes that apply.

[X] Title as described
[X] Make sure you put things in the right category!
[X] Always add your items to the end of a list

Open Source

[X] Link description does not contain a link to an author / third-party resource
[X] The documentation (README) contains a description of the project, illustration of the project with a demo or screenshots and a CONTRIBUTING section
[X] The documentation is in English.
[X] The project is active and maintained.
[X] The project accepts contributions.
[X] Not a commercial product

Apps/Websites

[ ] The website is available without errors or ssl certificate problems, and load in a reasonable amount of time.
[ ] The website is using vuejs intensively. It should detect vue with vue-devtools.

If you cannot detect vue with vue-devtools due to work at non public pages (e.g. for enterprise website), you can send Pull Request with screenshot that detected it.

[ ] The website is original and not too simple. For that reason, blogs and simple landing pages are rejected.
[ ] A commercial product using Vue, provided that guests could reasonably check out how Vue was used A commercial product using Vue, provided that guests could reasonably check out how Vue was used (i.e. A headless CMS which uses Vue for the Admin/editor Area and offers a free tier).

I new to this pull request. Do I need to do something on my end?

I new to this pull request. Do I need to do something on my end?

I new to this pull request. Do I need to do something on my end?

no, that's enough. Thanks for your investment

I new to this pull request. Do I need to do something on my end?

no, that's enough. Thanks for your investment


Can't use with astro

Having same issue as #973
Any magic workarounds ?
Thank you.

Workaround: setting a global variable in pages where the component is used seems to work:

Workaround: setting a global variable in pages where the component is used seems to work:

Thanks it help me to fix my project

If you're encountering issues with using a particular tool or library with Astro, as noted in issue #1152, it may be due to compatibility problems or configuration errors. Astro is a modern static site generator, and certain tools or plugins might not fully integrate with it. Check the documentation for both Astro and the tool in question to ensure compatibility and correct usage. Look for any updates or community discussions about similar issues. If needed, reach out to the developers or community forums for support in resolving the compatibility problem.


Please set env variable PHANTOMJS_BIN

Can't get phantomjs to launch. I have installed karma and karma-phantomjs-launcher both locally and globally. I've tried reverting the versions and manually setting the environment variable but it still doesn't work. I can launch karma-chrome-launcher no problem but would prefer to use phantomjs. Is this a problem with phantomjs itself?
Windows 7, node 0.12, karma 12.31, karma-phantomjs-launcher 0.1.4, phantomjs 1.9.16
Any help is appreciated!

Does phantomjs work for you independently of karma?

yup just installed phantomjs 2.0 from their site and did the quick start

Same issue here since latest update

Same issue here.
INFO [karma]: Karma v0.12.36 server started at http://localhost:9099/
INFO [launcher]: Starting browser PhantomJS
ERROR [launcher]: Cannot start PhantomJS
	Can not find the binary node_modules/karma-phantomjs-launcher/node_modules/.bin/phantomjs
	Please set env variable PHANTOMJS_BIN

Ironically, exporting PHANTOMJS_BIN to some existing path seems to have no effect whatsoever. The issue is resolved by manually installing karma-phantomjs-launcher dependencies, by means of:
nfantone@thinkpad-t430 ~/dev/js/myproject $ cd node_modules/karma-phantomjs-launcher/
nfantone@thinkpad-t430 ~/dev/js/myproject/node_modules/karma-phantomjs-launcher $ npm install

This actually installs the expected phantomjs binary at ./bin, and makes tests run without problems.

Could you show me the output of npm ls in the failing case please?

Of course, here it is.
...and here is the output of the working scenario with the "extraneous" packages, after the manual installation of dependencies. Just in case.

Okay it's as I expected, due to deduplication and being a peerDependency the phantomjs package gets moved to the top level, and so the path to it is node_modules/phantomjs instead of the expected node_modules/karma-phantomjs-launcher/node_modules/phantomjs.
Will have to fix the path detection in here. Thanks for your help in tracking this down.

You are welcome. Glad to help.

Okay so it looks like it's not us :( We are just using require('phantomjs').path which should export the correct path to the binary, but it looks like it doesn't in your case.
Could you do me a favor and open an issue here: https://github.com/Medium/phantomjs/issues with a reference to here.

Are you positive on this, @Dignifiedquire ? I have debugged the plugin and it seems as if require('phantomjs').path holds what it's expected to hold: the value of $PHANTOMJS_BIN. This property contains a correct path to a valid phantomjs binary. However, it does not seem to be using its value at all during the execution.

No I'm not sure as I can't reproduce it on my machine :/ which os/node version are you on?

Linux Mint 17.1 "Rebecca".
Latest 0.12.4 node.
On Jun 13, 2015 5:17 AM, "Friedel Ziegelmayer"<EMAIL_ADDRESS>wrote:

No I'm not sure as I can't reproduce it on my machine :/ which os/node
version are you on?
—
Reply to this email directly or view it on GitHub
https://github.com/karma-runner/karma-phantomjs-launcher/issues/69#issuecomment-111686600
.

@AquilaSagitta could you please provide the full log output with log level set to DEBUG

@nfantone could you please test the version in my pr #78 ? (You should be able to install it via npm install Dignifiedquire/karma-phantomjs-launcher#69-bin)

debug info you requested. http://pastebin.com/XhSEppjh

@AquilaSagitta thanks, if you want please try my pr #78 as well, I hope it fixes this issue

@Dignifiedquire Didn't solve the issue. Now the path is, indeed, absolute. But it's still a path to a non existent binary.
INFO [launcher]: Starting browser PhantomJS
ERROR [launcher]: Cannot start PhantomJS
	Can not find the binary /home/nfantone/dev/js/my-project/node_modules/karma-phantomjs-launcher/node_modules/karma-phantomjs-launcher/node_modules/.bin/phantomjs

Ok, I feel dumb. I've discovered that my auto-generated karma.conf.js had this line:
process.env.PHANTOMJS_BIN = 'node_modules/karma-phantomjs-launcher/node_modules/.bin/phantomjs';

at the very beginning. Entirely missed it this whole time. Removed it and worked flawlessly, both your branch and the 0.2.0 version.
Nevertheless,

Your modifications in Dignifiedquire/karma-phantomjs-launcher#69-bin are still reasonable.
This very same karma.conf.js file has been like that in my repo since the beginning of time. And it has never been a problem up until the last update to 0.2.0. Also, it's obviously not a coincidence that installing the plugins dependencies manually, creates that .bin/phantomjs. Any ideas on why this could have happened?

We should wait for some input from @AquilaSagitta. But, apart form that, you could close this issue if you want.
Thank you very much, @Dignifiedquire for your time and patience.

Happy to hear that :)

I also have the
process.env.PHANTOMJS_BIN = 'node_modules/karma-phantomjs-launcher/node_modules/.bin/phantomjs';

in my karma.conf.js but thats pointing to the right place. I'll try removing it and let you know if that resolves the issue.

That seems to resolve the issue >.<
I karma was complaining that the plugin for phantomjs was missing tho. Thought karma shipped with phantomjs and chrome

@AquilaSagitta Was your karma.conf.js` created automatically by an app generator, such as yeoman or slug?
I believe this is affecting users with existing/old setups created by those tools.

in my karma.conf.js but thats pointing to the right place.

It wasn't. Do a clean npm install and check the path. You'll see .bin does not exist. It used to be there, though, as my builds never failed until recently.

@nfantone Yes this project was scaffold with Slush (Gulp.js equivalent of Yeoman)
You're right the clean install doesn't have a .bin directory with phantomjs however, it was correct before I did a clean install. The process.env.PHANTOMJS_BIN... doesn't seem to actually do anything even when I change the path karma still throws this error
ERROR [launcher]: Cannot start PhantomJS
        Can not find the binary ...\node_modules\karma-phantomjs-launcher\node_modules\.bin\phantomjs
        Please set env variable PHANTOMJS_BIN

@nfantone Yes this project was scaffold with Slush (Gulp.js equivalent of Yeoman) probably 2-3 months ago.

Exactly. So was ours. In that same window frame. (I have edited my previous answer where I wrote slug, instead of Slush)
I don't know if newer versions of Slush still include this, but we should open an issue over there.

If you want to go ahead and do that feel free. I still don't understand what's happening or why removing that process.env... seems to solve the issue, You seem to have a better understanding of the situation.


Turn off Monitor Not working

Turn off Monitor Doesnot work i tried whith and whitaut Delay and it dosent work on the Original Screen

Turn off Monitor Doesnot work i tried whith and whitaut Delay and it dosent work on the Original Screen

Same issue faced , any solution ??

rename in   /home/pi/MagicMirror/modules/MMM-OnScreenMenu/MMM-OnScreenMenu.js
 kbMultiInstance: true,         keyBindingsTakeFocus: "Menu", // Can also be object: { KeyName:"Menu", KeyState:"KEY_LONGPRESSED" }         pm2ProcessName: "mm"
"mm" to "MagicMirror"


collision check and update between component and hand area is broken

moving / resizing hand area does not change component's ownership
dragging directly from someone's hand area to another's seem broken (probably related to #5)

fixed


fix some null annotation in ControlCatalog

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0021019-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0021053-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0021054-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


Indexer integration with Cassandra and Elasticsearch

Basically get data into Cassandra

[ ] Create init script for Cass
[ ] Test inserting indexer data into db
[ ] Create "ORM" functionality in /common

I think we got through most of this yesterday. Now we need to create a cassandra config script


How can i always show sort icons?

Sort icons is only show when click specific column title.
how can I make all sort icons always visible?
thanks in advance.

I can't see anything in the source code that lets you control the sort icons. You need to handle that yourself.
`
th.sortable {
/* anchor point for our :after pseudo class*/
position: relative;
}
th.sortable:after {
/* create the sort icon with css */
font-family: Icons;
font-style: normal;
font-weight: 400;
text-align: center;
content: "\f077";
/* Position the icon with pixels (old browsers) */
position: absolute;
top: 23px;
right: 16px;
/* Position the icon relative values (modern browser) */
top: 50%;
transform: translateY(-50%);
}
th[class*="sorted"]:after {
/* hide icons if sorting is active on that headline */
display: none;
}`


Unable to sort string fields of attribute indexing type

Describe the bug
Unable to sort based on single valued string fields
To Reproduce
Steps to reproduce the behavior:

Deploy application with schema containing a single valued string field
Yql query - select * from sources * where user contains "random" order by singleStringField ASC

Expected behavior
Results should be sorted based on the field given
Environment (please complete the following information):

Infrastructure: Kubernetes
Versions : 8.80.20

Vespa version
8.80.20
Additional context
I have a document that matches the below criteria but when I an using the above yql query mentioned I am not getting documents
with the field singleStringField

select * from sources * where user contains "rodipa" AND singleStringField contains "random"

Hi, please add the schema as well so this can be reproduced - thanks :-)

Copyright Verizon Media. Licensed under the terms of the Apache 2.0 license. See LICENSE in the project root.
A description of a type of data, how to store and index it, and what to compute over the data elements

See:
- https://docs.vespa.ai/en/schemas.html
schema testingDomainBlexDocument  {
document testingDomainBlexDocument {

        field singleStringField type string {
            indexing: summary | attribute

        }

    }

}

We have tests for this, also see https://api.cord19.vespa.ai/search/?query=sars&yql=select title, id,source from doc where userQuery() order by source+asc and https://api.cord19.vespa.ai/search/?query=sars&yql=select title, id,source from doc where userQuery() order by source+desc


docs base url

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Something went wrong with PR preview build please check

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs

Preview is available here:http://developers-pr4.previews.kube001.services.stellar-ops.com/docs


Always prompts for password on Travis

When building on Travis with MySQL enabled, the skeema tool always prompts for a password, even though no password is required. I believe the reason is that Travis creates a file at ~/.my.cnf containing:
[client]
default-character-set = utf8
port = 3306
user = root
password =
socket = /var/run/mysqld/mysqld.sock

Skeema automatically detects and uses the password setting in this file, which it interprets as a request to prompt for a user. This is undesirable behaviour, since this config file is clearly indicating that no password is required. The absence of a password setting in this config file would indicate that prompting for a password is reasonable.
I am aware that I can pass --skip-my-cnf to skeema to avoid this problem. However, it took some time to discover that the ~/.my.cnf file was the cause, so this does not avoid other users running into the same problem and similarly having to spend time to diagnose it. I suggest either changing this behaviour or adding an FAQ entry to cover this.

Thank you for the report. This seems to be a bug in how Skeema handles password=, i.e. when there's no value but the equals sign is still present.
The goal is for Skeema to match the behavior of the mysql client exactly, which it does in all other cases:

password alone with no equals sign: prompt for password
password='' i.e. explicit blank string: connect without a password
no password option supplied at all: connect without a password

I'm surprised that Travis isn't using that last method -- the canonical way of telling mysql to connect without a password is to just omit the password option entirely. password = is super weird, I've never encountered that in my 16 years of using MySQL. Regardless, I'll get this fixed in Skeema soon, and will aim to post an update on this issue later today.

On closer inspection, password='' i.e. explicit blank string doesn't currently work properly in Skeema either. Seems I broke this in a refactor long ago, or I misremembered handling that case...
I'll need to give more thought to the best way to differentiate between these cases generically. String args that don't require a value are painful to parse in general, which is why mysql has special rules around spacing (see 5th bullet on https://dev.mysql.com/doc/refman/8.0/en/command-line-options.html)

Fix included in the newly-released Skeema v1.2.3. Thanks again for the issue report!


Github actions incorrectly configured

Package+Version:
All 1.0.0
Framework version:
All
Describe the bug
The test logger is logging to GithubActions logger but it's not installed.
To Reproduce
Steps to reproduce the behavior:

Run CI pipeline.

Expected behavior
We'd expect to see code comments on faillures.
And a report.
Screenshots
N/A
Additional context
Run dotnet add package GitHubActionsTestLogger on setup dotnet command.

The GitHubActionsTestLogger is installed in the test projects.
So maybe something else is incorrectly configured

It appears that this logger does log out the results in the summary.
The only thing that doesn't seem to work is the in-code comments


Failure to add a connection due to missing crypto.randomUUID()

When I click this button ‘add connection’, it's not pop-up window appears to add a ollama serve

i dont know why

Can you tell me which browser/version you are using? Looks like you are missing the crypto dependency.

Can you tell me which browser/version you are using? Looks like you are missing the crypto dependency.

I deploy via docker, version 0.22.0 and version 0.23.0 both have this problem, and i use chrome.

I need to know which version of Chrome you are using.
Perhaps there is something special about your browser setup that might be blocking the Crypto API, maybe a browser extension? corporate/IT-managed browser configuration?
If you can, can you try opening Inspector on any page and running:
console.log('crypto.randomUUID available:', !!crypto.randomUUID);

Should give you a result like this:

Alternative, can you try a different browser? Firefox? Safari?

I need to know which version of Chrome you are using.
Perhaps there is something special about your browser setup that might be blocking the Crypto API, maybe a browser extension? corporate/IT-managed browser configuration?
If you can, can you try opening Inspector on any page and running:
console.log('crypto.randomUUID available:', !!crypto.randomUUID);

Should give you a result like this:
Alternative, can you try a different browser? Firefox? Safari?

My chrome version is 131.0.6778.86, and i try in Safari. It has the  same problem.

Understood, I'm not entirely sure why crypto it's not available on all of those browsers.
Regardless, I'll push a fix for this in the next few hours.

:tada: This issue has been resolved in version 0.23.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


update example conf to valid json

Hi, your example web config file did not contain valid JSON. So I've updated it.

Thanks for your contribution!
The reason why the example config is a js module and not json is that json does not support comments.
Do you think the module.exports = {} syntax is too confusing? How would you demonstrate the optional support for dropping privileges?

this has been solved in https://github.com/wiedi/node-dmx/commit/3e88846b550c05b5a2228a09f2980429aee95159 which kept the comments.


Centralize inputs

Adds a new Inputs class that reads the inputs with core.getInput(). This is done to better type the inputs and initialize them all at the  of execution.
Knowing the inputs early is necessary for internal caching.
This is based on my branch from https://github.com/jurplel/install-qt-action/pull/132, I can rebase it later if necessary.
I also added Prettier with default settings, I can remove it or change the settings as you see fit.
Closes https://github.com/jurplel/install-qt-action/issues/133 if it's supposed to be target.

This needs to be rebased because I added a commit to https://github.com/jurplel/install-qt-action/pull/132.

Superseded by https://github.com/jurplel/install-qt-action/pull/137


[plugin-rss-feed] Permalinks don't match posts' routes.

My permalinks don't match the routes I've defined (the rest works fine, only the RSS feed is affected).
phenomic.config.js
module.exports = {
  content: {
    pages: { root: 'content', globs: ['*.md'] },
    posts: { root: 'content/posts', globs: ['**/*.md'] },
  },
  plugins: [
    ['@phenomic/plugin-rss-feed', { feeds: { query: { path: 'posts', limit: 20 } } }
  ]
}

Routes
Link to a blog post is e.g. /first-post (without any trailing slash or any other path component).
<Router history={browserHistory}>
  <Route path="/about" component={Page} />
  <Route path="/" component={Page} />
  <Route path="/404.html" component={PageError} />

  <Route path="/p:after" component={PageBlog} />
  <Route path="/*" component={PageBlogPost} />
</Router>

Permalinks in the generated feed
The generated RSS link for the blog post mentioned above is /posts/first-post/ (instead of /first-post).
<item>
  <title>
    <![CDATA[ This is a first post ]]>
  </title>
  <link>http://localhost:5000/posts/first-post/</link>
  <guid isPermaLink="true">http://localhost:5000/posts/first-post/</guid>
  <pubDate>Sun, 01 Jan 2017 00:00:00 GMT</pubDate>
</item>

I think it mistakenly uses the query domain instead of the route 🤔

It looks like the /<query path>/id/ route is hard-coded at https://github.com/phenomic/phenomic/blob/master/packages/plugin-rss-feed/src/index.js#L63-L67

I've tried specifying the feeds.<my feed url>.map option, which would allow me to override this behavior, but neither a function nor a copy of defaultMap work. I get an unhandled rejected promise error 😢

We should definitely work on that. Contribution welcome. Maybe I  fixed the situation on master branch already for dev server...

rr3 won't be supported in phenomic revamp. A new solution will show up. This problem will have to be handled differently.

Reopening as it's still a good reminder


Fix create_backup and get_backup.

Fixes https://github.com/finish06/pyunifi/issues/61 and more.
For create_backup the suggested solution from https://github.com/finish06/pyunifi/issues/61 was taken.
get_backup still failed, because
if response != 200:
was used instead of
if response.status_code != 200:.
The README.md was updated to contain both arguments for get_backup.

any chance getting this merged? I confirm that it fixes the problem.


Is it responsive for mobile and does it allow zoom?

Hi, just about testing this lib. Just a few questions, please:

Is react-image-crop ready for mobile browsers?
Does it allow zoom in/out by pressing with two fingers (similar to the Whatsapp avatar editor)?

Thanks. However I didn't mean the "meta tags" based zoom but the ability to zoom the image being cropped dynamically.


Fix typo

Description
Fixes a minor typo in the docs
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ flake8
[ ] All tests pass: $ python run-tests.py --unit
[ ] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

I'll be glad to add it, @Saransh-cpp! Would you prefer it as a separate PR?

Would the spell check have caught this case ("is" is a valid word)? I think it might be overkill with way too many exceptions

That's right, it's more of a grammatical error rather than a typo – codespell has the potential to cause some problems with triggering certain function names in some repositories

codespell has the potential to cause https://github.com/matplotlib/matplotlib/issues/22740/ problems with triggering certain function names in some repositories

I don't understand the reference here (the issue talks about adding codespell to matplotlib?), but yes, as @tinosulzer mentioned, codespell might be overkill (and we might end up maintaining a long list of false positives).
Thanks for fixing this! 😄

@all-contributors add @agriyakhetarpal for infra


Example code on v0.9.0 release page

I'm relatively new to tide, but I think this line in the example code for Server::respond on the releases page should be:
let req = http::Request::new(Method::Get, Url::parse("http://computer.soup")?);

instead of
let req = http::Request(Method::Get, Url::parse("http://computer.soup")?);

Updated, thanks heaps!

Wow! Thanks for the quick action.
But I think the code still has some issues:

It complains about not being able to infer the type for res

assert_eq!(res.body_string().await?, "hello world".to_owned());
           ^^^ cannot infer type

Once that is fixed with res: http::Response then it complains about not being able to borrow res as mut.

assert_eq!(res.body_string().await?, "hello world".to_owned());
           ^^^ cannot borrow as mutable

This due to https://github.com/http-rs/tide/blob/f4e76f6b6813c5a783d2b55f503b9b3ef2ad71c6/src/response.rs#L176
The following works.  But having to define res as mut, while perfectly fine when coding for an end-point, it makes no sense to me in the context of testing.
     #[async_std::test]
     async fn hello_world() -> tide::Result<()> {
         let mut app = tide::new();
         app.at("/").get(|_| async move { Ok("hello world")} );

         let req = http::Request::new(Method::Get, Url::parse("http://computer.soup")?);
         let mut res: http::Response = app.respond(req).await?;

         assert_eq!(res.body_string().await?, "hello world".to_owned());
         Ok(())
     }

Should I raise a new issue?


[stable/metricbeat] Chart install fails when using cluster-local output

Version of Helm and Kubernetes:
Kubernetes v1.10.7
Which chart:
stable/metricbeat
What happened:
After installing the chart onto my cluster, the daemonset pods showed errors resolving the name "logstash" which is another service in the same namespace.
2018-10-01T15:23:50.773Z	WARN	transport/tcp.go:53	DNS lookup failure "logstash": lookup logstash on <IP_ADDRESS>:53: no such host
2018-10-01T15:24:50.774Z	ERROR	pipeline/output.go:91	Failed to connect: lookup logstash on <IP_ADDRESS>:53: no such host

What you expected to happen:
The pods to come up with DNS configured correct to resolve cluster-local addresses.
How to reproduce it (as minimally and precisely as possible):

Install the metricbeat chart and use a configuration that outputs to a cluster-local destination.

Further Investigation
Other folks have run into this and reported it on Stack Overflow.
Per the Kubernetes documentation, we should be setting dnsPolicy to ClusterFirstWithHostNet since these daemonset pods are running with hostNetwork: true

“ClusterFirstWithHostNet“: For Pods running with hostNetwork, you should explicitly set its DNS policy “ClusterFirstWithHostNet”.

I am running into similar issues,
@davidarcher  how did you get helm to remove the output.file definition in metricbeat.yaml though?
I added a output.elasticsearch setting instead of writing to file and I get the following error:
Exiting: error unpacking config data: more than one namespace configured accessing 'output' (source:'metricbeat.yml')


How can i create centered carousel with 1 slide per view in loop mode?

Hi
I want to create carousel like this, (1 slider per view in center mode)

as you see, Active slide has not 100% width.
This is my template:
    <client-only>
      <swiper class="swiper" :options="swiperOption">
        <swiper-slide v-for="(item, index) in gallery" :key="index">
          <b-img :src="item.img" :alt="item.alt | slug" />
        </swiper-slide>
      </swiper>
    </client-only>

This is option:
      swiperOption: {
        slidesPerView: 1,
        spaceBetween: 18,
        // centeredSlides: true,
        loop: true,
        loopFillGroupWithBlank: false
      },

This is style:
.swiper-slide {
  width: 70% !important;
  height: 250px;
  color: #fff;

  img {
    width: 100%;
    height: 100%;
    object-fit: cover;
  }
}

This is result:

import 'swiper/css/swiper.css'
is outdated, use
import 'swiper/swiper-bundle.css';

import 'swiper/css/swiper.css'
is outdated, use
import 'swiper/swiper-bundle.css';

this does not work, can you elaborate?

import 'swiper/css/swiper.css'
is outdated, use
import 'swiper/swiper-bundle.css';

this does not work, can you elaborate?

import 'swiper/css/swiper.min.css'
or check in swiper node modules, which css is there. It will depend on your swiper version.


[skrifa] Implement an optimized fill_glyph operation

In COLRv0/v1 drawing clients may gain a performance benefit from filling
a shape (with a solid or gradient fill) instead of performing a clip +
unbounded fill in sequence.
Allow clients to do that using a fill_glyph() operation that combines
the two.
Implement this using a temporary painter that speculatively traverses
the glyph tree down from a PaintGlyph operation collecting potential
transforms along the way.
New behavior shows clearly in new baselines for tests added in #758 that
nest PaintGlyph tables and cover mixed situations in
which the optimization succeeds for a leaf but fails for the
PaintGlyph at a layer above, and demonstrate recording transforms
along the way.
Fixes #746.

I would like to send this for review now. This is still a nested painter-based implementation. I have opted for now not to change signatures of the draw functions to return a Result and thus potentially be able to cancel drawing, as I believe this realizes the performance benefit and we would have yet to discover pathological situations in which there are deeply nested trees behind a PaintGlyph. The benefit the nested painter approach I see in avoiding implementing separate imperative traversal logic - instead - the existing traverse_with_callbacks can be used.
Please let me know if this works for you or if there are strong opinions about a different approach. I am open to revisiting this, but for now, this definitely meets the mark in terms of benchmark results as shared in the chat. An API change to Result<>-returning, cancellable methods would require a roundtrip of deprecation steps and careful chaining it into Skia and then Chrome with a phase of parallel ColorPainter functions along the way. I prefer to save that time atm and focus on implementing bitmap fonts support next.


Add semantic versioning tags as GitHub workflow

Will add a workflow to the GitHub actions which attaches a semantic version to the commit which is tagged with the release tag.
Description

Related Issue

Screenshots (if appropriate):

Is there a way to test this without actually releasing anything?

Well, not really actually. You'll always have to release something to test it, but that is why the 0.?.? versions exist. I'd say, increment the version.txt file to 0.1."higher number"-SNAPSHOT and push it to the repo. Then add the release tag and push that. You should see the workflow script running and a new version be created. (You can also always delete tags in GitHub, so that shouldn't really be an issue. And we already have 9 releases, so an extra one wouldn't make much difference)


Blob Trigger storage account binding

Layer 8 issue - please delete

@fgessen what doc are you referring to?

@Mar


fees: Reduce minimum relay fee to 0.001 DOGE

This loosens the minimum set of fee values for 1.14.4 to enable the rest in 1.14.5. Please review the figures, they should match the proposal, if not do let us know. If any values need to change for 1.14.4 and have been missed, equally let us know. Otherwise we'll raise the second set as a follow-on PR.

Apart from review - I noticed that item 4 from the fee plan was implemented differently (wallet only.) What is the rationale for that?

Apart from review - I noticed that item 4 from the fee plan was implemented differently (wallet only.) What is the rationale for that?

Item 4 being free transaction space, right? It will mean we missed somewhere to change it, but if we're reverting wallet.h, can tackle on the next iteration.

If I've understood the ask on integration tests, they're actually more tests of the policy, is that correct? As in, we're not testing the currently set value against previous versions (because that test would break on expected changes in 1.14.5), but instead simulating nodes with those values?
If so, I think it can be raised as a separate PR, and I'll do that.

Item 4 being free transaction space, right? It will mean we missed somewhere to change it, but if we're reverting wallet.h, can tackle on the next iteration.

Right. But there's something... just was curious why I didn't see the implementation. The problem that I see with item 4 right now is that there is a conflict between fee filter and free transaction space. There are notes authored by you in the current qa testset, originating from #1431, commenting on unavailability of free transaction space that may be the cause of this, but I do not have a clear view of what was done to cause that, yet, and I suspect that we need a network protocol feature to properly manage free transaction relay, and then bump the version, to resolve this for good. So I already hinted that we may need to do the free transaction space with 1.14.5 instead of 1.14.4, so that we can do that protocol extension properly. This would be an acceptable outcome, because I think it's more important to have properly functioning features than saying it's in and then there being hidden caveats, as was done with 1.14.2.
As for the wallet.h change. Any wallet changes will conflict with the existing network.

If I've understood the ask on integration tests, they're actually more tests of the policy, is that correct?

Incorrect. The policy elements are:

Get rid of the 1.14.2 hardcoded fees and do a true recommendation-only that can be changed by any individual node operator, without needing to compile new software.
Do an updated recommendation that is effectively 100x lower than the enforced hardcoded fee is today.

I had shared a WIP test with you over the weekend, building on #2437, that, on top of the test introduced with the dust limit configuration, tests and ensures element 1. The success of element 2 can really only be measured after the recommendation has been done and wallet software - including Dogecoin Core - implement it and we have some results on mainnet.
1.14.4 implements prerequisites that enable recommending a lower fee than currently hardcoded since 1.14.2. On mainnet, transition take time, as people need to update their live nodes, but on regtest we can perfectly test (now that everything is configurable) whether the changes we do now enable the updated recommendation and have no adverse effects for the network as a whole, or node operators upgrading from 1.14.2 or 1.14.3 to 1.14.4. This means we can test integration against a simulated 1.14.3 network right now for the current planned release, and the effects that a new wallet will have once this has been adopted on mainnet. And since we can, we should, because that proves that things work rather than a "Core Developer" claiming that it works.

Good. Now remove the hardcoded limitations completely for us legacy users.

Good. Now remove the hardcoded limitations completely for us legacy users.

Already done with #2368, #2348, #2437 and will be released with 1.14.4, which we are finalizing right now - see my WIP fee test for proof - this already works on current 1.14.4-dev branch.


Analytics hidden events refactor

Motivation and Context
Goal is to have a better overview of hidden events usage in the code / application.
Find a way to list it for stakeholders.
Description
"Hidden events" are the Play native apps events, contrary to "click events", which are defined for the Play web events.
The "click events" was introduced with #259.
The idea is to have a similar struct for "hidden events" and have common readable methods.
Checklist

[x] The branch has been rebased onto the develop branch.
The code followed the code style:

[x] swiftlint has run to ensure the Swift code style is valid.
[x] rubocop -a has run to ensure the Ruby code style is valid.

[x] Remote configuration properties have been properly documented (if relevant).
[x] The documentation has been updated (if relevant).
[x] Issues are linked to the PR, if any.

Hidden events are now defined as a Swift struct AnalyticsHiddenEvent.
A class still exist to have Objective-C Compatibility, AnalyticsHiddenEventObjC.
The hidden event name and type are now only know by AnalyticsHiddenEvent.
The hidden event source is still exposed publicly.
Maybe a next iteration could hide it behind a property in static methods, after a new overview of various existing sources for each tracked usage case.

Event sources are now hidden in the Analytics hidden event struct.
Simplification of enums for event name, event source and event type: just strings now.


Identify More Traits

Since we have narrowed out so many traits, we would like to identify new traits to analyze, as well as verify that the databases contain meaningful amounts of data for these traits.

Height is the only issue we have good data for. That's just it.


Vendor css file and extractVueStyles, I'm missing something..

Laravel Mix Version: 4.0.14
Node Version (node -v): 11.0.0
NPM Version (npm -v): 6.6.0
OS: OSX

Description:
Hi all!
I'm trying to get rid of the injected styles in the <head> from node_module packages (vue components). I've been digging around several days now, but I'm guessing I'm missing a piece of the puzzle.
Tried several forms of;
extractVueStyles: '[name].css' => This never resulted in any extracted files.
After I couldn't get that to work, I found several similar questions / issues:

https://github.com/JeffreyWay/laravel-mix/issues/1589
https://github.com/JeffreyWay/laravel-mix/issues/1050
https://github.com/JeffreyWay/laravel-mix/issues/1896

Reading up on this, the ExtractTextPlugin / mini-css-extract-plugin seemed to make sense to try. The ExtractTextPlugin resulted in errors like TypeError: Cannot read property 'find' of undefined. Ok, this plugin is depricated for Webpack 4 anyway. Maybe there are unresolved issues.
Then mini-css-extract-plugin resulted in errors like Error: Rule can only have one result source (provided use and loaders). I figured that Mix was already doing some extracting magic behind the scenes and the loaders were clashing.
So what am I missing to achieve creating a vendor.[HASH].css? 17 style tags (some of which are empty), with such a high specificity (since it's injected) is not really something to go into production with.
Thanks in advanced for any pointers.
My webpack.mix.js file:

const mix = require('laravel-mix');
const webpack = require('webpack');

const domain = 'my-domain.mac'

mix.browserSync({
    host:  domain,
    proxy: 'https://'+domain,
    open: 'external',
    browser: 'google chrome canary',
    files: [
       /* .. not relevant for example .. */
    ],
    https: {
        key: `/Users/my-name/.valet/Certificates/${domain}.key`,
        cert: `/Users/my-name/.valet/Certificates/${domain}.crt`,
    }
})

mix
    .setPublicPath('html/')
    .disableNotifications()
    .webpackConfig({
        // Ignore all momentjs locales, decreases bundle size greatly
        plugins: [
            new webpack.IgnorePlugin(/^\.\/locale$/, /moment$/),
        ],
    })
    .options({
        // Tried several options like, true, vendor.css
        extractVueStyles: '[name].css',
    })
    .js('resources/js/shared.js', 'js/')
    .js('resources/js/login.js', 'js/')
    .js('resources/js/users.js', 'js/')
    .sass('resources/scss/style.scss', 'css/')
    .extract()

if (mix.inProduction()) {
    mix.version()
} else {
    mix.webpackConfig({ devtool: 'inline-source-map' })
    mix.sourceMaps()
}

I  have some problem.

I have this issue too!


List Offline Devices

In the Summary you see which Devices are offline or inactive. As I spread the devices into many applications its not easy to get the devices that are offline and inactive.
Consider showing which devices are offline/inactive. Or include this information in the api.
https://github.com/chirpstack/chirpstack/blob/98978135c47d71a0a43826934ceb2e10d74a7e5a/chirpstack/src/api/internal.rs#L598
https://github.com/chirpstack/chirpstack/blob/98978135c47d71a0a43826934ceb2e10d74a7e5a/chirpstack/src/storage/device.rs#L620
Should be possible to also select device.dev_eui

This information is available via the API.
You need to loop through applications that the tenant has access to - Are you using the correct API User?
Here's a quick script to loop through items in the manner you desire (untested).
import requests

# Base Chirpstack API URL and headers
base_url = "https://<chirpstackAPI>/api"
headers = {
    "Grpc-Metadata-Authorization": "Bearer YOUR_API_TOKEN",
    "Content-Type": "application/json"
}

# Function to get all applications
def get_applications():
    response = requests.get(f"{base_url}/applications", headers=headers)
    if response.status_code == 200:
        return response.json().get("result", [])
    else:
        print("Error fetching applications:", response.text)
        return []

# Function to get devices for a given application ID
def get_devices(application_id):
    response = requests.get(f"{base_url}/devices?applicationId={application_id}", headers=headers)
    if response.status_code == 200:
        return response.json().get("result", [])
    else:
        print(f"Error fetching devices for application {application_id}:", response.text)
        return []

# Main script to find offline devices across all applications
offline_devices = []
applications = get_applications()

for app in applications:
    application_id = app["id"]
    devices = get_devices(application_id)

    # Filter offline devices in this application
    offline_devices_in_app = [device for device in devices if device.get("status") == "offline"]
    offline_devices.extend(offline_devices_in_app)

# Display offline devices
print("Offline Devices Across All Applications:")
for device in offline_devices:
    print(f"- Device Name: {device['name']}, Device EUI: {device['devEUI']}, Application ID: {device['applicationID']}")

Did this resolve your issue @offizium-berndstorath ?

@offizium-berndstorath

Your initial request suggested that the issue you face is finding devices that are offline between applications.

What would the user journey look like for a tenant administrator, that has visibility of multiple applications, with devices that are offline?
Would this be displayed in the tenant dashboard, in the application/devices table, or somewhere else?

Another good solution would be to be able to filter stauts in the device list

This is where my thought drifted too - Being able to sort and filter based on "Device name, last seen, device profile, devEUI, etc.."


Litmus test results URL in Readme doesn't work anymore

In the readme the URL "See the Litmus test results" opens the website, but it hasn't the same results as the screenshot provided in the readme.
The screenshot attached shows what I can see on Litmus.

Other then that, very nice template, thanks!

Whoops. Updated. Thanks for heads up. https://litmus.com/checklist/emails/public/233ded7


Problem with definition of check_proposer_signature?

What is wrong?
In the function per_block_transition (in .../state_transitions.py, we take a boolean variable named check_proposer_signature. I think this variable is being used in the opposite sense of how it is named.
If check_proposer_signature is True, then we skip the validation of the proposer signature. If the parameter is False, then we do validate the proposer signature. I looked a bit at its uses across the codebase and couldn't add much more to the picture.
How can it be fixed
If I can confirm the semantics, I would suggest we change the if not check_proposer_signature: conditional to if check_proposer_signature and patch the existing call sites. (we could also change the name but i would rather make the non-local edits in this case and keep the name).
@hwwhww looks like you were the last to touch this line?

Agreed!!!
I recalled that was is_proposer but was changed to check_proposer_signature per
https://github.com/ethereum/trinity/pull/241#discussion_r252768490, my fault that I didn't reverse True and False in PR feedback.


NoopCloudWatch does not implement putMetricDataAsync

emitCloudWatchMetrics in DynamoDBReplicationEmitter.java calls putMetricDataAsync on the cloudwatch object, which is an instance of NoopCloudWatch when --dontPublishCloudwatch is specified. This leads to unintended behavior, and metric publishing failures.

Actually, upon debugging further, it seems that DynamoDBMasterToReplicasPipeline calls the deprecated DynamoDBReplicationEmitter constructor which takes only the streams configuration. Therefore, it isn't actually using the NoopCloudWatch instance, but instead creates a new Cloudwatch client. Looking further now...


Checkvist

Ref: Conversation #420 / Gregg

Ref: Conversation #4101 / Andrzej

Ref: Conversation #5483 / Gregg

Popclip and checkvist work well together with Applescript and Mail (sample script from Alfred forum thread here) to create and send a mail message to the Checkvist list address (each list has one that you can retrieve like so). I modified the BBEdit sample Popclip extension to get this going, and was also able to make a similar alfred extension with a keyword trigger. Works really well. I tried to figure out the Checkvist API, but using Applescript and Mail was far faster for me and still works well.


Post deploy commands

Is it possible to run commands within containers after deployment? I'd like to define these commands in the topology itself or specify a filename where the commands reside.
This is required to make crpd useful since even if a startup-config is provided commands still need to be run within the container.

I see that the deploy command has a flag to skip post deploy actions but the documentation contains no examples of actual post deploy actions.
The nearest example I can find is in the frr01 lab example (https://github.com/srl-labs/containerlab/blob/main/lab-examples/frr01/run.sh) but this is using shell commands rather than the clab deploy interface directly.

Hi @mtucker502
you should use exec stanza for executing commands in the container namespace https://containerlab.dev/manual/nodes/#exec
if you need to run a cli command on crpd, then I think crpd should have some CLI process that can take in commands to run as arguments.
Let me know if this helps

Thanks @hellt. This is exactly what I was looking for.
An example for anyone else looking for the same:
name: crpddemo1

topology:
  nodes:
    crpd1:
      kind: crpd
      image: crpd:latest
      startup-config: crpd.conf
      exec:
        - ip addr add <IP_ADDRESS>/30 dev eth1
        - ip addr add <IP_ADDRESS>/32 dev lo
    crpd2:
      kind: crpd
      image: crpd:latest
      startup-config: crpd.conf
      exec:
        - ip addr add <IP_ADDRESS>/30 dev eth1
        - ip addr add <IP_ADDRESS>/32 dev lo

  links:
    - endpoints: ["crpd1:eth1", "crpd2:eth1"]

Contents of crpd.conf:
system {
    root-authentication {
        encrypted-password "$6$lB5c6$Zeud8c6IhCTE6hnZxXBl3ZMZTC2hOx9pxxYUWTHKW1oC32SATWLMH2EXarxWS5k685qMggUfFur1lq.o4p4cg1"; ## SECRET-DATA
    }
}
protocols {
    ospf {
        area <IP_ADDRESS> {
            interface eth1;
        }
    }
}

Validation
$ docker exec -it clab-crpddemo1-crpd1 cli
root@crpd1> show ospf neighbor
Address          Interface              State           ID               Pri  Dead
<IP_ADDRESS>       eth1                   Full            <IP_ADDRESS>          128    33

root@crpd1>


BUG: Not opening .tex files when opened via the file tree.

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
NVIM 0.9.4
Operating System / Version
Windows 11
Describe the Bug
When I try to open a .tex file through the file tree (using NeoTreeShowToggle), the file appears empty. No pop-up error message when opening
Although when trying to save this empry file it shows de following error message:
E212: Can't open file for writing: no such file or directory
Moreover, if I open a file like 'nvim main.tex' and switch files through the File Tree. When I return to main.tex, this error doesn't occur
Screenshots, Traceback
Original file:

When opening via Tree:

Steps to Reproduce

In a directory with .tex files Open nvim
Open Tree with NeoTreeShowToggle
Open a .tex file
Save file to pop-up the error E212

Expected Behavior
The file opens without any content
Your Configuration
-

NeoTreeShowToggle was removed in 3.0, so you must be on old version. Can you try updating to the latest version (which is 3.14) and seeing if that fixes it?

It's already updated and even other commands to open neotree shows the same problem

@rafaelferracini unless you are using a different Neovim config than what's public in your dotfile repository, you are not on the latest stable branch. Check out your nvim-tree plugin spec, it is using 2.x: https://github.com/rafaelferracini/dotfile/blob/e5d8da0292de20b53d3a5e4f52cbfcaebbf2f8a1/nvim/lua/plugins.lua#L36-L44
You need to change this to 3.x and have packer update your Neo-tree plugin. I suspect you're having issues with the spaces in your path and the buffer is being opened to a non-existent file. The escaping issue was fixed 8 months ago in https://github.com/nvim-neo-tree/neo-tree.nvim/commit/7f6fa04dbd8e8c79d1af33bc90e856b65d8641da, but this is only on 3.x (it was not merged into 2.x).

This should be fixed with the latest branch. Closing.
Please reopen and ping me if you still experience this issue.


TIPP disappears from OAI output

Occurred in dev.
Whenever I set in a TIPP the property Depth from Fulltext to Empty (https://phaeton-dev.hbz-nrw.de/gokb/resource/show/org.gokb.cred.Package%3A236080), the whole TIPP disappears from the corresponding OAI extract.

Thanks for the report. This is caused by unexpected HQL behaviour (as described here: http://tomaszdziurko.com/2011/12/problem-withjpa-join-column-null-values-and-orderby/).
We'll have a fix in the next release, but we may also take this opportunity to make coverageDepth not-nullable (this is already validated for in integration imports anyway).

Fixed in #212


Packaging switch to an empty buildpack

This PR switches the package building process to an empty build pack. We are not using the functions the build pack provides and this

makes the process faster
removes the need to keep versions of build packs in sync and working
makes it possible to package for more platforms (CentOS, newer versions of Debian, ubuntu)

This has problems that seem complex to debug; Will re-open later


TypeError: 'undefined' is not an object (evaluating 'e.schemeCategory10')

C3 version: 0.7.20 (latest)
D3 version: 7.4.4 (latest)
Browser: google chrome (Version 100.0.4896.88 (Official Build) (x86_64))
OS: macOS Monterey 12.2.1 (21D62)
codepen link : https://codepen.io/tanya5895/pen/KKQWKJV

error log :
ERROR :  TypeError: 'undefined' is not an object (evaluating 'e.schemeCategory10')
c3.min.js:2 Uncaught TypeError: this.d3.set is not a function
at l.mapTargetsToUniqueXs (c3.min.js:2:128160)
at p.t.updateXAxisTickValues (c3.min.js:2:13207)
at l.redraw (c3.min.js:2:31077)
at l.initWithData (c3.min.js:2:27500)
at l.init (c3.min.js:2:22585)
at new n (c3.min.js:2:463)
at Object.generate (c3.min.js:2:21614)
at pen.js:2:16

@masayuki0812 can you please help here ?

We currently stop maintaining the repo. Please consider using billboard.js https://github.com/naver/billboard.js which has almost the same API and maintained better


Import suggestions

Codecov Report

Merging #15 (ae30d9e) into main (567ab8b) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head ae30d9e differs from pull request most recent head f4b72ef. Consider uploading reports for the commit f4b72ef to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##                main       #15   +/-   ##
===========================================
  Coverage     100.00%   100.00%
- Complexity       104       106    +2
===========================================
  Files             28        29    +1
  Lines            381       389    +8
===========================================
+ Hits             381       389    +8

Impacted Files
Coverage Δ

.../Command/ImportSuggestionsToMeilisearchCommand.php
100.00% <100.00%> (ø)

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


QUESTION: FITTING IMPROVEMENT

Dear Elio,
I'm trying to abel-inverse some images of xenon using your pBASEX code. However, somehow the fit trace does not reproduce fine features that are relevant for finding the beta parameters. I was wondering if you could give me some advice for improving my fit.
Attached you find an example of the problem I'm having. In case it's useful, xenon was ionized by 266 nm pulses, implying that we have roughly a 3-photon absorption process.
I'm looking forward to your reply! Thank you!

Thank you! Yeahh.... that was the problem. Would it be possible to have your PhD thesis?  I am very interested on reading it :)

Dear Elio,
please let me ask you another question: both the fitted image I get and its abel inversion display relatively weak rings that ultimately give rise to oscillations in the photoelectron spectrum (see pic attached). Is there a way to deal with these features?
Thank you!

I'm not sure what exactly is causing that, but I'd argue it would be due to data/imaging fidelity. The two clues I see on this figure are (1) the oscillations don't go much below zero, integrating to a net positive number of counts, and (2) there is a left-right asymmetry in your residuals. Two easy things you could try on the pbasex code side of things would be to change the centroid slightly or invert each quadrant independently (using the quadrant_filter option in the foldQuadrant function) and see if these oscillations appear in all of the quadrants or just one. Doing this is also one (non-unique) way to get some idea for error bars on your data. Beyond that, you could look into doing a regularized least squares fit (l2-regularization is implemented in this code already, although l1- might work better to get rid of small spurious features like these oscillations).
It seems your fit is able to get the main two energetic features and some nice angular distributions.

Hi, Elio,
This are the new images I'm getting:

Instead of using a linear 'k_spacing' Im using the quadratic and this improved my situation. I don't know if I did correctly the inversion by quadrants. In the code, I used quadrant_filters = [1,1,1,1], [1,0,0,0],[0,1,0,0], etc. Is that what you meant? How can I change to l1 regularization?
I symmetrized the input images by averaging over all quadrants. Do you think that there's still room for improvement regarding having a better output spectrum or fitted image (apart from having much better data quality)?
Thanks!

Yea, you can try to run quadrant_filter=[1,1,1,1], [1,0,0,0], [0,1,0,0], etc. and see how the results compare.
Besides that, I think it looks good, there isn't any obvious feature in the residual plot (besides the slight asymmetry in the quadrants) that I would worry about.


Re-enable CodeClimate coverage reporting

There were some difficulties with the CodeClimate gem running on Codeship which previously required a patch. v1.0.5 of the gem should resolve this issue.

:eyes: @mrgeitz


Error validating workflow "workflow": error populating workflow: APIError: dialing: missing 'type' field in credentials

I'm not sure what dialing is...
I used https://console.cloud.google.com/apis/credentials to create an OAuth 2.0 client IDs and then downloaded the resulting JSON file.

What you need to create is a service account key.  See here for more info: https://cloud.google.com/docs/authentication/production
In short, if no credentials are provided on the command line, Daisy will look in well known locations. If running in GCE it will use the default service account set for the instance.
Gcloud can also be used to store credentials in a well known location by running 'gcloud auth application-default login', you then do not need to pass the path to the credential file on the command line.

Yeah, I eventually settled on gcloud auth application-default login -- It just feels like dialing is an odd thing to have as output, there's nothing anywhere that talks about it. -- I can't figure out what it means...

That's just how the error is passed up, the api library has that in the
setup error, probably because it's setting up a tcp connection.
On Wed, Mar 14, 2018, 2:22 PM Josh Soref<EMAIL_ADDRESS>wrote:

Yeah, I eventually settled on gcloud auth application-default login -- It
just feels like dialing is an odd thing to have as output, there's
nothing anywhere that talks about it. -- I can't figure out what it means...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/compute-image-tools/issues/368#issuecomment-373179183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQWyS3piyiunGFpnoyA3MQvnsM0bu3PKks5teYoHgaJpZM4SrEyU
.

The word dialing comes from daisy itself:
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/24859bb2213074212a17c8227db0cde4397090ac/daisy/compute/compute.go#L172
Does it mean connecting? Is it trying to tell someone the name of a module under the hood?

Ack, ok I think that was based on previous code. I'll take a look and see
about working out a more clear error message. Thanks
On Wed, Mar 14, 2018 at 3:52 PM Josh Soref<EMAIL_ADDRESS>wrote:

The word dialing comes from daisy itself:
https://github.com/GoogleCloudPlatform/compute-image-tools/blob/24859bb2213074212a17c8227db0cde4397090ac/daisy/compute/compute.go#L172
Does it mean connecting? Is it trying to tell someone the name of a
module under the hood?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/compute-image-tools/issues/368#issuecomment-373201666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQWyS4vIoFjg8GD7aKWztbyBcRuyV8tVks5teZ8ygaJpZM4SrEyU
.


Add support for multiple managed identities

thoughts on including #22 in this ?

I would keep it separate at least as a PR , not sure if there are other implications of teams updating to 1.31.x ? we should probably deal it separately and give teams a deadline to move to latest.