⚠ Bofrost.be has degraded performance

In bf895ab, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1331 ms

Resolved: Bofrost.be performance has improved in cbdfe7d after 6 minutes.


No episode found gogoanime domain

Source information
Gogoanime 13.78
Source language
English
Steps to reproduce

Expected behavior
Message are coming
No episode are found
Actual behavior
Refresh the page episodes are not coming
Aniyomi version
<IP_ADDRESS>
Android version
Android 11
Other details
Please solve this problem
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Duplicate of #2986

Episode are not coming

What is your problem
Why are Remove this problem

Because its a duplicate of the issue i mentioned

Ok but episodes are not coming to but I can do I am delete my app and download again but same problem are coming no episode are found this message are coming I am refresh my gogoanime library but episode are not coming other I am good other I am go to the browser and open GoGoAnime exception and check another anime name episode are not download and not found is coming

If you have a solution give me please

The extension is broken, hence the issue i mentioned earlier. Wait for an extension update.

Ok if update are coming please tell me
Because I was go browser open and gogoanime domain
And I am click any anime option
They show message are coming no episode found

Also I have another problem after the update my app
Manga extension are not working please solve this also my problem

Don't comment with unrelated issues. If you have a separate problem, make a separate bug report.

Don't comment with unrelated issues. If you have a separate problem, make a separate bug report.

I am using older version aniyomi app
If I am update my app Manga extensions are not working


ja: Make docs/concepts/workloads/pods/pod.md follow v1.17 of the original text

This is a Feature Request

What would you like to be added
Update docs/concepts/workloads/pods/pod.md to follow v1.17 of the original (Englist) text.
Why is this needed
content/ja/docs/concepts/workloads/pods/pod.md is outdated.
Comments
/language ja
/good-first-issue
File to update
https://github.com/kubernetes/website/blob/dev-1.17-ja.2/content/ja/docs/concepts/workloads/pods/pod.md
Original
https://github.com/kubernetes/website/blob/release-1.17/content/en/docs/concepts/workloads/pods/pod.md
diff between translated and v1.17
https://gist.github.com/28e1a7e93bf82708e38ce34e86f67681
Note
Currently, we use dev-1.17-ja.2 branch. Please open a PR targeting the branch.
ref
How To Contribute
翻訳スタイルガイド
If you have a question, feel free to ask us at slack.k8s.io #kubernetes-docs-ja channel.

/assign

/close


chore: prepare 0.3.10 release

Signed-off-by: Tomer Figenblat<EMAIL_ADDRESS>

Codecov Report

Merging #626 (23b91b1) into master (c4b6c8c) will increase coverage by 0.92%.
The diff coverage is n/a.

:exclamation: Current head 23b91b1 differs from pull request most recent head 7777eb6. Consider uploading reports for the commit 7777eb6 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master     #626      +/-   ##
==========================================
+ Coverage   58.74%   59.67%   +0.92%
==========================================
  Files          18       18
  Lines         863      863
  Branches      173      173
==========================================
+ Hits          507      515       +8
+ Misses        356      348       -8

see 1 file with indirect coverage changes


Layout header component options potentially no longer used

The layout header component has a variation that I think is no longer used anywhere, since the work to improve the site header and make it consistent across the site in the last few years. This is the variant:

Would need a little investigation to just confirm this is no longer used anywhere, then remove it from the component.

Agree that this variation can be removed, searching for the search_left option returns 0 results across alphagov - https://github.com/search?q=org%3Aalphagov+"search_left"+language%3AHTML%2BERB&type=code


New package: albertony.npiperelay Version 1.6.2

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

/azp run

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\albertony.npiperelay__DefaultSource\npiperelay.exe returned exit code: 1
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\npiperelay.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Packages\albertony.npiperelay__DefaultSource\npiperelay.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\npiperelay.exe returned exit code: 1

(Automated response - build 886.)

@stephengillie the command C:\Users\<username>\AppData\Local\Microsoft\WinGet\Links\npiperelay.EXE without any argument is simply printing the help screen and as this is not suffient, it exit with exit code 1:
npiperelay v1.6.2
  commit 98b61e5808f48ca603a2e99a14a5026a8ecf3497
  build date 2024-04-05T08:08:55Z
  built by goreleaser
  built with go1.22.2

usage:
  -bg
        hide console window and run in background
  -ei
        terminate on EOF reading from stdin, even if there is more data to write
  -ep
        terminate on EOF reading from the pipe, even if there is more data to write
  -p    poll until the the named pipe exists and is not busy
  -s    send a 0-byte message to the pipe after EOF on stdin
  -v    verbose output on stderr

Verify:

@stephengillie the command C:\Users<username>\AppData\Local\Microsoft\WinGet\Links\npiperelay.EXE without any argument is simply printing the help screen and as this is not suffient, it exit with exit code 1:

Yes, this is something of a known issue with our pipelines, which were built with Windows Forms in mind. Sorry for the delay verifying this new application.


Splunk Hook fails to marshal logrus.Entry

I'm using https://github.com/caddac/logrus-splunk-hook to try to log to splunk. I've opened an issue on the original repo here https://github.com/Franco-Poveda/logrus-splunk-hook/issues/1 but have gotten no reply, so trying here to see if I can get some help.
I've setup my hook like
import (
	"github.com/caddac/logrus-splunk-hook"
	log "github.com/sirupsen/logrus"
)
splunkClient := splunk.NewClient(nil, cfg.SplunkUrl, cfg.SplunkToken, cfg.SplunkSource, cfg.SplunkSourcetype, cfg.SplunkIndex)
splunkHook := splunk.NewHook(splunkClient, []log.Level{level})
log.AddHook(splunkHook)
log.Info("Test logging"))

and I get error:
Failed to fire hook: json: unsupported type: func(*http.Request) (*url.URL, error)

The hook fails to JSON marshal the logrus.Entry sent into the Fire() method. The error is coming from  here: https://github.com/Franco-Poveda/logrus-splunk-hook/blob/5edca16794c6d300ff72b75ca774ec4ec20617c0/splunk.go#L116-L119
I've dug in a bit, but can't seem to find where this function is coming from on the event. Does anyone have a suggestion or idea about where the real problem lies here?

OK, I've fixed this by doing:
func (h *Hook) Fire(entry *logrus.Entry) error {
	event := map[string]interface{}{
		"message": entry.Message,
		"time": entry.Time.String(),
		"level": entry.Level.String(),

	}
	for k, v := range entry.Data {
		event[k] = v
	}

	err := h.Client.Log(
		event,
	)
	return err
}

Does it mean this issue can be closed?

I'd be curious to get some feedback about my solution, and if I need to handle the logrus.Entry.err field.

I came here looking for solutions to the same problem in the splunk hook library.

Failed to fire hook: json: unsupported type: func(*http.Request) (*url.URL, error)

For logrus I guess the question is whether or not the Entry struct should be possible to marshall to JSON.
Ie. add annotations to ignore the "non-marshable" parts.
Also, the original splunk hook library has been forked several times to fix this issue. The author seems to have abondned it, so maybe the list of hooks in the documentation should be updated with a forked version?


Unit-tests for model-package-group

Description of changes:
Sdk.go coverage: 96.1%
Overall coverage: 64.3%
Covers all custom code except this portion of delete requeue.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test sagemaker-kind-e2e

/test sagemaker-release-test

/approve
/lgtm

/test sagemaker-release-test


Squash Django migrations files (2021)

(EDIT 2021/04: changed title to say 2021; was originally 2018/06)
We should be able to compress these into 1 to 3 equivalent migrations files per app. Instead of having migrations describing years of design-change history - create table, add columns, move columns to other tables, modify columns, etc., - the migrations would just have some table creations describing our current database design. Cutting down our migrations should speed up unit-test initialization.
We can get rid of the south_migrations directories as well. Those aren't needed if we're sticking with Django versions past 1.7 (that's when migrations became baked into Django, rather than being part of the 3rd party app South).
Also, update our repository docs to spell out the migration-squashing procedure, so we don't get lazy about it again in the future. Migration squashing can be done whenever we're sure that the server + all developers are up to date with running migrations.
Recommended to do this before upgrading to Python 3 (#59), so that we have fewer Python files to upgrade.

Done with PRs #371 and #382.


House cleaning

Sonar has dozens of bugs related to the use of " instead of '. Missing ; and spaces. This chore is to run npm run lint to fix them.
Take the opportunity and add the official icons

These changes look great. I'm going to have to run the linter on a regular basis as I'm coding to get used to the TypeScript style. And to find missing semi-colons.


Refactor reducers to prepare for undo/redo

Description of the problem this pull request fixes
Inspector may not be the best name, but selected mark and expanded layers are related so this PR

groups them together within the redux store
combines their reducers (not sure how I feel about this)
Adds a module to define actions
Removes sample code
better handles initial state within inspector component

@deathbearbrown I see selected layer and expanded layers as being related, so this PR changes the store state to be
{
  inspector: {
    selected: 6,
    expandedLayers: {
      '4': true,
      '8': true
    }
  }
}

Extremely open to :bike: shedding this

I'm going to merge this now.  I tested it locally and it doesn't break anything and I need dat code. We can add comments afterwards.


Kafka - Initial attempt at doing less calls to the group coordinator.

Pull request
Description
Avoid commit calls to the group-coordinator for each event. Instead make use of the client local offset store as the only way to handle commits, so the traffic from them is bounded.
Try to avoid unnecessary calls for the current assignment, by caching it.
Related
Checklist

[ ] The RFC, if required, has been submitted and approved
[ ] Any user-facing impact of the changes is reflected in docs.tremor.rs
[ ] The code is tested
[ ] Use of unsafe code is reasoned about in a comment
[ ] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[ ] The performance impact of the change is measured (see below)

Performance

Since this will break stuff lets point it to 0.13-staging?


Add expression type support

Add expression type support like %number, %integer, %boolean and %string in the Documentation Generator and schemas.

Added support for %Vector2 in https://github.com/jakubg1/OpenSMCE/commit/9b2196e508ca274dd18deaa1f89128a7dd1a44a5.


🔭 Experiment: Checksum local pod content instead of file modification dates

Description
Hashing whole files is a little bit slower than just hashing the file modification times, but the upside is less cache invalidation.
I have 2 use cases where this is very important:

CI machines. When they checkout/clone new code the modification dates are updated for directories. I'm experimenting with using rugby in pull request CI which some large local pods that rarely change.
pod install generated code. This is in a react native project and there they have codegen that happens as a part of pod install, this results in rugby rebuilding 21 pods that haven't actually changed. The timings below are for this project. So we can see the prepare step increases from 2s to 6s, but the 11s build step is skipped completely (7s win! I expect more on the slower CI machines).

Before:
[2s] Prepare ✓
[11s] Build ✓
[1s] Integration ✓
[1s] Clean up ✓
[14s] Cached 139/166 pods.
[!] Project size ↓83%
[!] Indexing files count ↓96%
[!] Targets count ↓83%
[14s] Let's roll 🏈

With --experimental-checksum-content:
[6s] Prepare ✓
Build Skip
[1s] Build ✓
[1s] Integration ✓
[1s] Clean up ✓
[7s] Cached 139/166 pods.
[!] Project size ↓83%
[!] Indexing files count ↓96%
[!] Targets count ↓83%
[7s] Let's roll 🏈

I've been testing this locally, but I'm not sure how to write test cases for this functionality in the project here, let me know if you have ideas.
Additionally I think the checksumming and file loading can be improved to speed this up a bit, left some comments in that section of the code.
References
N/A
Checklist

[ ] I've added at least one test that validates that my change is working, if appropriate
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary

❤ Thanks for contributing to the 🏈 Rugby!

@cltnschlosser Thanks a lot for this request! It’s a great feature!
It’s pretty similar to the first implementation of the checksum algorithm) Then I changed it in favor of checking date modifications. But I think you are right now and it’s a better solution. I was going to rethink this one, but I didn’t have enough time.
Could we split this request into two separate ones? Like these:

nonInteractive flag
New experimental checksums algorithm

I think there are two different purposes.
And then will continue reviewing it.

Created https://github.com/swiftyfinch/Rugby/pull/183 for the --non-interactive flag. I'll pull it out of this one shortly.

I've been testing this locally, but I'm not sure how to write test cases for this functionality in the project here, let me know if you have ideas.

I think we can change tests after flag became non experimental. It's OK for now 👍

OK, everything is fine. Let ship it! 🚀
I will fix spell checking beyond this request.

Can this feature add to 2.0 version? @swiftyfinch
After pod install when change branch, there are still some pods will rebuild when use 2.0 version. If there are some low level pods should rebuild(no modified file at all), It also trigger all Pods depends on it to rebuild because of the graph. This may unnecessary and waste time.

@zzzworm Hello! It's strange. Rugby2.x should compare the content of files and their targets from Pods project.
Do you have some build phase scripts which change your source code?

Before using 🏈 Rugby you should be sure that your project code base is finalized.
https://github.com/swiftyfinch/Rugby/blob/beta/docs/remote-cache.md

Also, you can generate the yaml files with information about each module checksum.
https://github.com/swiftyfinch/Rugby/issues/220#issuecomment-1458308497
But in the latest version you should use RUGBY_KEEP_HASH_YAMLS env variable.
Please, open an new issue/discussion if you still have question about this topic.


Syncplay seeks to the position in the previous file on playlist change

We usually use the playlist to add videos which we want to add next.
If you manually change from one video to the next(e.g. you skip the outro of a video) Syncplay skips into the next video - possibly spoiling its contents.
Since we almost never need this behaviour and it often gets in the way it would be nice to hear from more people if they need it or would rather want it changed.

The current expected behaviour is that Syncplay only rewinds when it is autoplaying the next file or if you shift+drag the file in to Syncplay. I'm happy with making it also rewind when you change playlist item. Anyone have any strong views in favour or against?

If the behaviour is changed then there could be a "change without rewind" menu item too, but not sure if that'd add unnecessary complexity.

Have the same problem with next episode in list. It will be very useful thing for me. Even checkbox in menu will be ok :)

It seems like the consensus view is to make this change, so I'll do that next time I have some free time (unless someone else gets to it first).

The changes I've made should do the trick. Let me know if it doesn't work.


Update README.md

Add reference to clearance-i18n gem

I expanded on this a tiny bit and merged as abd6f75. Thanks


HDDS-11119. Unnecessary UPDATE_VOLUME audit entry for DELETE_TENANT

What changes were proposed in this pull request?
removal of duplicate audit logging of UPDATE_VOLUME for delete tenant case. Already DELETE_TENANT audit log is present.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11119
How was this patch tested?

existing test cases for impact

@sumitagrawl Thanks for the patch, @kerneltime @devmadhuu for the review.


Commander Items on Lecterns

This is exactly what I needed for my vanilla multiserver world.
I currently have the commands bound to books that port people to and from different servers "Myst" Ages style.
Is there a way to apply a command to a lectern with a book on it?
Or have the object remain behind after use (I guess a drop command they teleport?)
I want to keep the book (or the lecturn with the book) where it is when they get teleported.

For now no, but I'm adding this use to the to-do list!

Added in 4d84651


Single file or offline install

Figure out if there's a way to get PyAutoGUI as a single .py file so that non-technical folks can simply drop pyautogui.py into a folder and use it.

pyautogui uses many other open source libraries under the hood so IMO the best you can do @asweigart is provide the entire environment with f.ex Anaconda or Python's venv module


This library should "simplify" url before perfoming request

Hi. URLs like 'http://example.com/foo/./bar/./foobar/' should be simplified to 'http://example.com/foo/bar/foobar/' before request. Chrome for example performs this simplification

I presume this will be taken care of when we start using the URL constructor that is planned for v3, already have some tickets for that

Ok. Thanks for answer


Default serializer behavior changed between version 6 and 7

Using NEST.JsonNetSerializer in NEST 7 changes the default serialization behavior from NEST 6. NEST.JsonNetSerializer is using the default serialization settings from Json.NET, while NEST 6 was using the settings specified in InternalSerializer.CreateSettings. NEST 6 defined NullValueHandling = NullValueHandling.Ignore by default, while Json.NET (with NEST 7) uses Include by default. This is quite an important change if you were doing partial document updates by specifying null values for properties that should not be modified. (The old behavior was ignoring these fields, the new behavior updates these to null.)
One can achieve the same behavior by specifying explicitly the JsonSerializerSettings, but the default behavior changed, and I couldn't find any mention of this in the documentation.

Hi @tamasvajk
the 7.x NEST.JsonNetSerializer serialization behaviour is the same as the 6.x NEST.JsonNetSerializer serialization behaviour. The internal serializer in 7.x has different serialization behaviour to the internal serializer in 6.x; we have documented the changes that we're aware of.
The internal serializer in both 7.x and 6.x has different default serialization behaviour to NEST.JsonNetSerializer. The intention with NEST.JsonNetSerializer is that it uses the default Json.NET serializer settings, and can be customized to suit user needs. We had a discussion at the time about whether NEST.JsonNetSerializer should be configured with serializer settings similar to the default serialization behaviour of the internal serializer and decided not to, thinking that a user using NEST.JsonNetSerializer is likely to also configure it to suit their serialization needs that are not met by the internal serializer.

Thanks for the clarification. I didn't realize that InternalSerializer in 6.x is not the same as 6.x Newtonsoft.Json. It probably confused me that the InternalSerializer also uses JsonSerializerSettings.
https://github.com/elastic/elasticsearch-net/blob/6.x/src/Nest/CommonAbstractions/SerializationBehavior/InternalSerializer.cs#L130

6.x uses an internalized version of Json.NET, which is IL rewritten and merged into NEST 6.x. For all intents and purposes, consider it a serializer that has the same behaviour as Json.NET but is not Json.NET because it exists in a different assembly in a different namespace.
In NEST 6.x+, there are effectively two serializers

RequestResponseSerializer, the serializer to use for requests and responses. This is always the internal serializer and its behaviour cannot be changed
SourceSerializer, the serializer for documents and document related fields. By default, this also uses the internal serializer, but can be changed through custom serialization, For example, using the Nest.JsonNetSerializer changes this serializer.

I think we have the changes between 6.x and 7.x internal serializers covered in the docs, but if there are cases that seem missing, please do raise them.
I hope this helps, @tamasvajk. Are you happy for me to close this issue?


Add custom elements support and test for it

Some alternative marketplaces has additional element definitions that are not part of the standard Yandex DTD.
One example is <stock_quantity> element described here.
This pull request adds support for custom offer elements by AbstractOffer class and a test for it. Multiple custom elements of the same type are supported.
Use:
    $offer = (new OfferSimple())
        ->setId(100500)
        ->setAvailable(true)
        // ...
        ->addCustomElement('stock_quantity', 100);

will result in <stock_quantity> element added to the header section of the generated  element:
<offer id="100500" available="true">
  <!-- ... -->
  <stock_quantity>100</stock_quantity>
  <!-- ... -->
</offer>

AbstractOffer class received 4 new methods:

setCustomElements(array $customElements = [])
addCustomElement($elementType, $value)
getCustomElements()
getCustomElementByType($elementType)

AbstractGeneratorTest was modified in order to extract generation code
from runGeneratorTest() method into generateFile() method
OfferCustomElementsGeneratorTest uses SimpleXML to load and check
generated values, added SimpleXMl as an extension requirement to
composer.json

Codecov Report

Merging #22 into master will decrease coverage by 1.27%.
The diff coverage is 40%.

@@             Coverage Diff              @@
##             master      #22      +/-   ##
============================================
- Coverage       100%   98.72%   -1.28%
- Complexity      248      255       +7
============================================
  Files            18       18
  Lines           691      706      +15
============================================
+ Hits            691      697       +6
- Misses            0        9       +9

Impacted Files
Coverage Δ
Complexity Δ

src/Model/Offer/AbstractOffer.php
94.47% <40%> (-5.53%)
59 <6> (+7)

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 3df790d...87da6ca. Read the comment docs.


content encoding error serving react site

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
# randomly picked react project as an example
git clone https://github.com/ahfarmer/calculator
cd calculator
npm install
netlify dev --live

Expecting properly served react site and instead getting Content Encoding Error.
- If the current behavior is a bug, please provide the steps to reproduce.
See the attached files what shows a difference in output between curl localhost:3000 and the dev.live site.
localhost.txt
devlive.txt
- What is the expected behavior?
properly served html
- Please mention your node.js, and operating system version.

node v11.6.0
macos 10.14
netlify netlify-cli/2.11.16 darwin-x64 node-v11.6.0

Closing this a a duplicate of https://github.com/netlify/cli/issues/719.
See my comment here for more information.


Expose Execution URL as a variable

In some previous ChatOps version the URL with results was always included in message:

Execution Details available at: http://...

In the new and more flexible ChatOps version with formatting and everything it's missing now.
Some tasks could be really long-running and having full execution URL would be nice, so user can include it with own formatted result message (Jinja2 stuff in Action Alias). Ideally to make it available as ready-to use variable.

That's reasonable. Just wondering: the link in the ack message isn't enough for your case, or did you find it was better to disable the link / entire ack?

Yeah, the case is a long-running task, when ack with link appears in chat immediately, but the actual result can appear in chat after several minutes of execution.
So link in ack is not enough.

Yeah, if possible I think having execution URL in the context which is available to the message would be nice.

So this is implemented and available via Jinja variable {{ execution.web_url }} in ChatOps alias
See:
https://github.com/StackStorm/st2/blob/ed6fdb4043647b766551c25f365782a58abce019/contrib/chatops/actions/templates/default.j2#L17-L19


Expose express middleware

Expected Behavior

(change/improvement)
I would like to embed altair in my express server utilizing something like:
import altairMiddleware from 'altair/express-middleware' // for example
import express from 'express'
import {graphqlExpress, graphiqlExpress} from 'apollo-server-express'

import schema from './schema'

const app = express()
// This is how Apollo Server handles this: app.get('/graphql', graphiqlExpress({endpointURL: '/graphql'})
app.get('/graphql', altairMiddleware({endpointURL: '/graphql'})
app.post('/graphql', graphqlExpress({schema}))

Current Behavior

I see a server.js file that exposes the express server, but it also starts the server on a given port, which I do not want to do.  Also, it would be nice if the middleware accepted options like Apollo Server does.

@jrop that's a nice idea. I've also been thinking of the same thing. Still trying to figure out how best to do it. Any input on this is very appreciated! :)

@jrop The server.js file is used for the altair web app. I have been able to test altair running as a sub app within an express application. I guess that takes care of this?
I would create a package with this as an initial release. I guess other things can be contributed by the community as needed 🙂

For this initial release, it would just be an instance of the altair client without any configuration options available when using it as a middleware.

@jrop I have an npm package up now https://www.npmjs.com/package/altair-express-middleware. There's no readme currently but you can use it the same way you use apollo-server-express, but without the options you pass to it (altair is already pretty configurable, so you can still work with it).


Front end codes v3

Updates to website codes and READMEs to troubleshoot errors when downloading from GIthub

Thanks, @Imran2923 for the submission.
But, it is a little bit too small to be merged. Can you add some additional enhancement or fix?

Alright, I'll try to add more to the enhancement when I can.


[prefer-tacit] May cause source of error

Bug Report
The documentation of prefer-tacit states:
| Generally there's no reason to wrap a function with a callback wrapper if it's directly called anyway.
But this is not correct.
Steps to reproduce
Imagine you are using (a third-party library which provides) a function shorten:
function shorten (text) {
	return text.substr(0, 2);
}

Now you want to use Array.prototype.map() to transform an array of strings to a version with shortened strings:
console.log(['Hello', 'World'].map((text) => shorten(text)));
// -> ["He", "Wo"]

Since this is reported as "Potentially unnecessary function wrapper" by prefer-tacit, you change it to:
console.log(['Hello', 'World'].map(shorten));
// ["He", "Wo"]

Same result, so everything is fine.
Later the author of shorten decides to add a second, optional parameter:
function shorten (text, length = 2) {
	return text.substr(0, length);
}

Now, the "optimized" code, returns a totally different result, because the second parameter of map is the index:
console.log(['Hello', 'World'].map(shorten));
// ["", "W"]

This could result in hard-to-find bugs.
Proposed changes
I would expect the documentation to clearly point out this problem, rather than pretending it's the same functionality.
And that this rule will not be added to the recommend and lite configs in the next major release (#171)

The documentation probably should be updated to highlight this issue.
However, the rule itself is smart enough to not mark the following as a violation if shorten is typed as taking more than 1 parameter.
['Hello', 'World'].map((text) => shorten(text));

In JS world were there are no types, the rule's fixer is disabled by default and only set to the "warn" severity.
The only issue comes when the function shorten is modified after the fact. @jonaskello Do you think this is reason enough to not add the rule to the recommended and lite configs?
I having also been thinking that it might be best to change the fixer to a suggestion.

| The only issue comes when the function shorten is modified after the fact.
This is the main problem - the result is code which changes it's behaviour unintentionally.
I just found this article by Jake Archibald who describes the exact same problem:
https://jakearchibald.com/2021/function-callback-risks/
Maybe it could be linked in the documentation of the rule.

Well, this seems like a tough problem to solve automatically. If you enable the rule and follow it blindly you could run into situations like the one described here. I would say the developer must understand the risks at each call-site and make a decision.
Documenting the risks more would of course be a good step. I have not used suggestions in eslint but it seems like they may be able to provide more descriptions to the developer before applying the fix? In that case I think that could also be a good thing. A text like "Switch to point-free style. Be aware that future changes to the function's signature may cause unintended behavior. See docs, [link to docs]" would be helpful when applying the fix.
In case the developer decides that he don't want to use point-free style, perhaps because it is a third-party function, then it should also be possible to avoid having the rule flagging the case. The rule seem to have the ignorePattern option but I'm not sure how it works for this particular rule?
If possible I think having the fixer display two suggestions would be a good solution, something like this:

Replace with point-free style.  Be aware that future changes to the function's signature may cause unintended behavior. See docs, [link to docs]
Change to follow ignorePattern so that this usage of non-point-free style will be ignored.

I think you're right @jens-duttke, with the way the rule currently is, the rule should be opt-in rather than enabled by default.
I wonder if we could add a setting so that the rule would ignore functions that come from an external source (though this might be difficult to do as "what defines an external source?" - we'd need to get the user to specify (by default it would be any import that doesn't start with "./" or "../")).
With such a setting enabled, the rule could then be used in conjunction with rules like unicorn/no-array-callback-reference without error.

The fixer has been replaced with a suggestion so there are no automatic changes that could break things.


Update replication-error-8606.md

fixed commands
Pull request guidance
Thank you for your contribution. The content team is monitoring the pull requests. Once your pull request is ready for review, please type "#sign-off" in a new comment or add a comment such as "PR is ready for review and merge."

@gabor-rozsa The changes will be live at https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/replication-error-8606. This PR will be closed.


Button action in list view not working

Hi, at first I want to say GREAT job!
Really it is very nice library, very fast porting on STM32H7 nucleo and 3.5 inch display with ILI9488 controller.
Just noticed that in demo application, clicking on buttons in list don't give expected results. I tried in debug but not getting callback for button click. Also tried to change action to button press LV_BTN_ACTION_PR and that is working.
Also, one more info, when i work with buttons outside list, I regularly receive callback for LV_BTN_ACTION_CLICK.
Best regards, and once again great job!

I will try tomorrow, thank you for response. Currently I do not return same value for x and y when press is released. I will write results. If this help maybe this notice should be in porting tutorial.

Great great great! Evrything works as you suggested.
Thanks @TomasPech
@kisvegabor maybe this point should be in porting tutorial, lv_tutorial_porting.c in explanation for function
static bool ex_tp_read(lv_indev_data_t * data)
Thank you once again for great work.


Quicksort

pls, Merge for Hacktoberfest CB

Add resources not codes
Add resources like courses, certifications, roadmaps, notes, cheat sheet, etc


Docker Engine Error: init: secure_channel main process terminated with status 255

Output of docker version:
[root@node264 tmp]# docker version
Client:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        Thu Feb  4 18:34:50 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.0
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   590d5108
 Built:        Thu Feb  4 18:34:50 2016
 OS/Arch:      linux/amd64

Output of docker info:
[root@node264 tmp]# docker info
Containers: 13
 Running: 3
 Paused: 0
 Stopped: 10
Images: 24
Server Version: 1.10.0
Storage Driver: overlay
 Backing Filesystem: xfs
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local rexray
 Network: host bridge null
Kernel Version: 3.10.0-327.4.4.el7.x86_64
Operating System: Red Hat Enterprise Linux Server 7.2 (Maipo)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.58 GiB
Name: node264.local.net
ID: EVY3:7RCW:KJX2:VUVC:YEOQ:BKQO:WZFV:FVQK:VT54:IBBM:7KFC:KY76
Username: XXXXXXXXX
Registry: https://index.docker.io/v1/
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS, VirtualBox, physical, etc.):
Docker + Mesos + Marathon + on VMware ESXi
Steps to reproduce the issue:
Happens randomly
Describe the results you received:
Mar 18 09:36:09 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2226) terminated with status 255
Mar 18 09:36:09 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:10 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2230) terminated with status 255
Mar 18 09:36:10 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:12 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2234) terminated with status 255
Mar 18 09:36:12 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:13 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2238) terminated with status 255
Mar 18 09:36:13 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:14 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2258) terminated with status 255
Mar 18 09:36:14 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:15 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2261) terminated with status 255
Mar 18 09:36:15 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:16 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2264) terminated with status 255
Mar 18 09:36:16 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning
Mar 18 09:36:17 node264 docker: init: secure_channel (XXX.XXX.158.236) main process (2267) terminated with status 255
Mar 18 09:36:17 node264 docker: init: secure_channel (XXX.XXX.158.236) main process ended, respawning

Result: Can't spawn any containers...
Additional information you deem important (e.g. issue happens only occasionally):
Issue happens occasionally. I have to completely stop docker engine and then start it.

Are you able to reproduce this on 1.10.3? I know we made some changes (e.g. https://github.com/docker/docker/issues/19950) that resolved issues when using Mesos

I can try to upgrade and see if problem re-surfaces

Updated to docker 1.10.3. the problem has gone away, for now. However, I am getting this instead:
Mar 23 06:39:39 node264.local.net docker[1354]: time="2016-03-23T06:39:39.783790561-04:00" level=warning msg="Failed to allocate and map port 31100-31100: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -A DOCKER ! -i docker0 -o docker0 -p tcp -d <IP_ADDRESS> --dport 31100 -j ACCEPT' failed: iptables: No chain/target/match by that name."

Mar 23 06:39:39 node264.local.net docker[1354]: time="2016-03-23T06:39:39.869694798-04:00" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /var/lib/docker/containers/ea6048117dd8d61c11143e7685bd4f0e2a2cd3f17ede571ef284580f2a1d3859/shm: no such file or directory"

Mar 23 06:39:39 node264.local.net docker[1354]: time="2016-03-23T06:39:39.872639155-04:00"
level=error msg="Handler for POST /v1.22/containers/ea6048117dd8d61c11143e7685bd4f0e2a2cd3f17ede571ef284580f2a1d3859/start returned error: failed to create endpoint mesos-bea8729f-8675-4e41-bb44-917f8c6250d3-S4.cf14f2a5-d4f3-4061-8b31-af1197a06fd9 on network bridge: COMMAND_FAILED: '/sbin/iptables -w2 -t filter -A DOCKER ! -i docker0 -o docker0 -p tcp -d <IP_ADDRESS> --dport 31100 -j ACCEPT' failed: iptables: No chain/target/match by that name."

Mar 23 06:39:45 node264.local.net docker[1354]: time="2016-03-23T06:39:45.092250517-04:00" level=error msg="Handler for POST /v1.22/containers/mesos-bea8729f-8675-4e41-bb44-917f8c6250d3-S4.cf14f2a5-d4f3-4061-8b31-af1197a06fd9/stop returned error: Container already stopped"
[root@node264 test]#

To remedy this issue, I have to restart Docker service. Once docker engine restarted, all is well, the problem goes away (but it most definitely comes back, perhaps after a week or so).

@akamalov thanks for testing, and good to hear -that- issue has been resolved. W.r.t. the other issues, I don't think those are new to 1.10.3, as I've seen them reported with older versions as well by some people. Could you search for existing issue, perhaps those contain useful information for that
Are you okay with closing this issue?

Yep, I am going to close it. Yes, indeed I have seen the issue before. I am wondering what is it that is causing it. I won't be able to deploy the environment into production without resolving this outstanding issue.
Thanks again,
Alex

@akamalov if you know a good way to reproduce, or have additional information on when it's happening (or something special to your setup or the way you're using docker) please open an issue for that :+1:


Trailing spaces in mesh config lead to it being hard to edit with kubectl edit

See https://github.com/kubernetes/kubernetes/issues/75446. The reason when you kubectl edit the mesh config and it has all the string escaping is because of trailing spaces. This is something we can probably fix

Fixed by https://github.com/istio/istio/pull/16820


Decouple SSL expiry alerts from Up/Down alerts

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
It would be extremely helpful to be able to configure a notification ONLY for certificate expiration alerts, either per monitor, or as a global.
✔ Solution
Add an option in Settings > Notifications for configuring a notification specifically for certification expiry alerts.
❓ Alternatives
No response
📝 Additional Context
Right now we have a single Slack channel which receives all alerts, and it is hard to detect certificate-related alerts among all up/down events.

@ligouras @ass
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/508 as this is included there
⇒ I am going to close this as a duplicate.


Where'd SimpleReduceHandler go?

In jaraco.modb, tests that passed a year ago are now failing with AttributeError: module 'jsonpickle.handlers' has no attribute 'SimpleReduceHandler'. Looking at the changelog, I see no reference to a change regarding this class.
And looking at the module in question, the docstrings still mention the handler, but the handler is just not there :(.

Boo. Looks like the code was removed as part of "Style fixes" https://github.com/jsonpickle/jsonpickle/commit/3e3296bb6ba1a9e06409a3138e2f313a090e3dfb#diff-a407a7c860cf65b3175948a216a0b6f6.

Looking at #170, it looks like the handler was removed intentionally, and coincidental with style fixes. I think the proper fix is for libraries to require 0.9.5+ and not use SimpleReduceHandler, but rely on the now integrated reduce support. That's what I've done in the latest version of jaraco.modb. I still think a notice of the backward incompatibility should be added to the changelog for 0.9.5.


Fix ORC writer with ZLIB compression

The current version uses org.apache.orc.impl.ZlibCodec to enable ZLIB compression for ORC, but it's impossible to use it as secor fails to create it if it's specified in the secor.compression.codec property.
The PR uses org.apache.hadoop.io.compress.GzipCodec to trigger ORC ZLIB compression which is used usually for other formats.

I am not familiar with the difference between zlib and gzip.  It seems to me in most other big-data projects, GzipCodec is the commonly used one.  Is GzipCodec the superclass of ZliCodec?
With the change, do you specify gzip or zlib in your config file?

ok, commented it

Thanks for the contribution.


Side panel red background

System Details

OS: macOS 14.5
Thorium Version 124.0.6367.218 (Official Build) (arm64)

Screenshots

Additional Notes
And, when will be the next release? I prefer the new UI and I don't wanna launch Thorium through terminal everytime.

System Details

OS: macOS 14.5
Thorium Version 124.0.6367.218 (Official Build) (arm64)

Screenshots

**Additional Notes**
And, when will be the next release? I prefer the new UI and I don't wanna launch Thorium through terminal everytime.

am having the same issue here on x86.

Adding a bookmark

Same issues for me as well

Same issue here, on MacBook Pro M1

Same.

Working just fine.

System Details

OS: macOS 14.5
Thorium Version 124.0.6367.218 (Official Build) (arm64)

Screenshots

**Additional Notes**
And, when will be the next release? I prefer the new UI and I don't wanna launch Thorium through terminal everytime.

@RoyRao2333 you can probably save yourself a bit of a headache by creating a terminal Shortcut.

Same here! Red for Bookmarks and Reading List, and the scrollbar of History and the dropdwon menu in Reading Mode are red!

@Alex313031
Hi Alex. Is this fixed in M126? This red color is quite unusable. 😭

Fixed in M126


Update JDK versions

New JDKs are released including security fix, see:
https://mail.openjdk.java.net/pipermail/jdk8u-dev/2021-January/013337.html
https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2021-January/004689.html
Also update Scala 2.12 version

thanks!


Gradle build error

Hi everyone,
I got this error with gradle build.
Error:Could not GET 'http://cdn.repro.io/android/chat/rocket/android-ddp/0.0.1/android-ddp-0.0.1.pom'. Received status code 403 from server: Forbidden
Do you have any suggestion? Thank you so much.

I found that I need to compile with newer rocket.chat version
Replace this line
compile 'chat.rocket:android-ddp:0.0.1'
by this
compile 'chat.rocket:android-ddp:0.0.1'
in build.gradle at module:app


Build Fixes

I thank you for reviewing this PR.
The purpose of the PR is to enable an optional (group ID) GID argument to be passed so that it matches the
one on the host. Often, the render group id, when matched with the host, allows us to build and
run the examples without requiring root permissions. With that, I am able to run this on most distributions
and I can pass --build-arg GID=$(getent group render  | cut -d: -f3) while building with Docker.
The other fix adds the Build directory to .gitignore, in-line with the naming convention.
Commit Message:
Build Fixes for various distributions.

* Change groupid to an optional argument a user can pass when building.
* Add Build to .gitignore

I think this looks good. Can someone approve it?


Option to save panel layouts globally instead of per-workspace.

I would like the option to just save the VS Code panel layouts once and never have to re-arrange them again.
 Machines are meant to perform boring manual tasks, not to give us more of them to do.
There are other issues that asked for this such as #138263, but they're closed due to "lack of interest", which is a bunch of baloney because it's based on a garbage measurement of user interest since you can't even easily find these issues without arcane knowledge of exactly what to search for.

Can you clarify what you mean by having to move panels for each new folder? What state should be included in this saved state that is not today?

This is how I organize my bottom panel in every workspace:

However, whenever i open a VS Code to a new folder, the bottom panel areas are all out of whack with the huge source control (left), tiny search (middle) and collapsed outline (right):

So, it's just a little dance that I have to do every time I open a new folder and it just annoyed me for the nth time... but anyway, thanks for the really great free software and your attention! and sorry for complaining :)

Thanks for the explanation @waynebloss
https://github.com/microsoft/vscode/blob/f55ddeb7dab0df9cca72f45873ab618b6e7470aa/src/vs/workbench/services/views/common/viewContainerModel.ts#L81-L101
@sandy081 I was looking at this and notice we keep some properties in both global and workspace state, but not all. And our behavior is that we tend to allow updates to the workspace state and global state but don't apply across windows until reload. This manifests itself sometimes as a bug where moving a full view container can result in different orders of views in multiple windows. I wonder if we should move more to global. Visibility and resizing shouldn't automatically apply across windows, but I think reordering or should force the view containers to sync up. Also, we should store the most recently used workspace state into the global state so that we have sane default state for new workspaces. Lmk your thoughts

We store in workspace state only for those views which are defined to be workspace scoped.
https://github.com/microsoft/vscode/blob/c6fa8b7e03da3071f0b90ca2a1c07844c9eab470/src/vs/workbench/common/views.ts#L290
I am having a debt item to remove workspace specific views - https://github.com/microsoft/vscode/issues/153513 so that we will not store visibility and order in workspace state at all. I think we are currently not updating the order of the views across windows when they are changed in one window. I do not remember if it is intentional or we missed it. IMO we shall not have any workspace specific views and visibility and order shall be updated across windows.

@sandy081 let me know if you want/need any assistance in picking up the debt work

It would be great, if you can pick it up.
Regarding removing workspace specific views, I have to consult with Alex Ross for remote container views - the only ones having this flag.

This issue is the bane of my existence because I jump in and out of projects often. Is there anyway I can help clean up?

Just wondering if there has been any progress on this one. It's one of those little annoyances than breaks peoples' workflows.

Has this been rolled out?

Any updates?


Duplicate ID's in mobile menu

The mobile menu has a static 0 in the ID rather than using the Nunjucks iterator.

Fixed in commit 3307b5e

Fixed in commit 3307b5e

Deployed in v1.0.1

Deployed in v1.0.1


Tailwind compilation

Added functionality for Tailwind to be compiled at runtime (on the fly), along with support for custom fonts and colors (top level, not at the page level)

Waiting for a meeting with Adam

Thanks a lot guys, @leandrocp @ryanwinchester @TheFirstAvenger


An error with CSP if you run npm run check during npm run dev

Describe the bug
I just figured out what the problem is that causes https://github.com/sveltejs/vite-plugin-svelte/issues/969.
Everything works good until I launch npm run check in another console tab during the already started npm run dev.

package.json:

"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json"

The npm run check apparently ignores the if (dev) return in:

svelte.config.js:

import 'dotenv/config';

const dev = process.env.NODE_ENV === 'development';

function gen_csp() {
  if (dev) return;

  let directives = {
    // ...
  };

  return { directives };
}

const config = {
  preprocess: vitePreprocess({ script: true }),

  kit: {
    // ...

    csp: gen_csp(),
  },
};

export default config;

but not only for itself, it also breaks the current npm run dev:
(index):42 Refused to create a worker from 'http://localhost:4000/service-worker.js' because it violates the following Content Security Policy directive: "script-src https://*.website.com 'nonce-4r1nfez5GdG7nc+4Ce8Wvg=='". Note that 'worker-src' was not explicitly set, so 'script-src' is used as a fallback.
(index):42 Uncaught (in promise) DOMException: Failed to register a ServiceWorker: The provided scriptURL ('http://localhost:4000/service-worker.js') violates the Content Security Policy.
localhost/:1 Refused to load manifest from 'http://localhost:4000/manifest.webmanifest' because it violates the following Content Security Policy directive: "default-src https://*.website.com". Note that 'manifest-src' was not explicitly set, so 'default-src' is used as a fallback.
6
Refused to connect to '<URL>' because it violates the following Content Security Policy directive: "connect-src 'self'".

Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-bzs49u
Changes from the starter template

I added packages to package.json:

"dotenv": "16.4.5"
"@sveltejs/vite-plugin-svelte": "4.0.0-next.6"

I changed svelte.config.js

Steps to reproduce:

pnpm install && pnpm dedupe

npm run dev

npm run check (in another new tab)

System Info
@sveltejs/adapter-static: 3.0.4 => 3.0.4
@sveltejs/kit: 2.5.25 => 2.5.25
@sveltejs/vite-plugin-svelte: 4.0.0-next.6 => 4.0.0-next.6
svelte: 5.0.0-next.240 => 5.0.0-next.240

Severity
serious, but I can work around it
Additional Information
A small note:
I opened https://github.com/sveltejs/vite-plugin-svelte/issues/969 because I had the problem right after the (only) update from vite-plugin-svelte@3 to<EMAIL_ADDRESS>Nothing else changed.
I'm not a high-quality developer, I'm trying to learn day by day and I'm passionate about quality projects like Svelte.
As you can see, I contributed in my own small way to suggesting bugs and to be a beta tester for all the preview versions that come out, both of Svelte and Kit.
I've ALWAYS been polite with EVERYONE, ALWAYS.
Maybe I opened an extra superfluous issue? Yes, maybe. But as soon as I understood the problem I also closed it and thanked those who helped me (and I must say that almost everyone has always been welcoming, warm and kind, starting with Rich).
That "ALMOST" because sometimes, even in the warmest and most welcoming communities in the OSS world, there is someone who responds badly, rudely and who perhaps needs a few days of vacation: https://github.com/sveltejs/vite-plugin-svelte/issues/970.
There are some really bad people in the world to blame, not someone who is trying to help solve a problem on a project, to the best of their ability.

I don't know if the reproduction is still needed in cases like this. If yes, I will create one (I'm out of time now unfortunately).

Put yourself in our shoes: how would you begin investigating a report like this? Of course a reproduction is needed. Without one, the best we can hope for is that we're able to create an equivalent reproduction ourselves (we are also not overburdened with time, btw), except without any of the context that you already have (like, the content of directives). It's not surprising if maintainers become frustrated with these sorts of issues!

Ok, fair. I added the reproduction and the reproduction steps.

If I run NODE_ENV=development pnpm check that doesn't cause any errors. So I'm guessing we should set the node environment to development whenever pnpm check runs?

I think we should address the NODE_ENV var.


custom fields: add vocabulary

requires https://github.com/inveniosoftware/invenio-records-resources/pull/353
closes https://github.com/inveniosoftware/invenio-vocabularies/issues/202

closing in favor of custom-fields branch


Factory surface is surrounded by grass

I believe this was fixed in some earlier version, but for some reason my surface is still grassy. I can walk outside and even jog over to a different building and exit from there.
Running on latest version, 3.4.1

Please run this command:
/c for _, surface in pairs(game.surfaces) do     if surface.name:find("%-factory%-floor$") or surface.name:find("^factory%-floor%-%d+$") then         surface.freeze_daytime = true         surface.daytime = 0.5         if remote.interfaces["RSO"] then             pcall(remote.call, "RSO", "ignoreSurface", surface.name)         end         local mgs = surface.map_gen_settings         mgs.width = 2         mgs.height = 2         surface.map_gen_settings = mgs         local grass_1 = surface.find_tiles_filtered {name = "grass-1"}         local new_tiles = {}         for _, tile in pairs(grass_1) do             table.insert(new_tiles, {name = "out-of-map", position = tile.position})         end         surface.set_tiles(new_tiles)     end end


Modified genrsa to generate RSA private key with numbers p and q

Hi, I added a feature to genrsa option to be able to generate a private RSA key with a given pair of prime numbers, p and q. This was part of my experiments to audit the strength of RSA keys. Regards, S.

cool.

I recently needed something similar[1] myself, but found it much more easy to simply hack some script to write some (proper) ASN.1 containing the key I wanted. If I had this patch it might have saved me some hours of work, but this change is rarely useful outside of (academic) research or your ivory tower sandbox. Much more this provides a powerful canon to everyone to not only blow their feet off, while eradicating themselves at the same time.
Given how rarely the above feature is useful I do not see a proper reason to break the API/ABI of the library.
[1] https://github.com/BenBE/kompromat/blob/master/scripts/convert-key.php
And yes: My script is a hack which needs some post-processing under certain conditions.

This is a pretty large patch for a pretty limited-use feature.  See BenBE's script.  (API changes are not an issue, since this would be for 1.1)  But we're not going to take this.

Fine, I will have to maintain my own implementation then, thanks. S.
On Sun, Apr 19, 2015 at 10:04 PM, Rich Salz<EMAIL_ADDRESS>wrote:

This is a pretty large patch for a pretty limited-use feature. See BenBE's
script. (API changes are not an issue, since this would be for 1.1) But
we're not going to take this.
—
Reply to this email directly or view it on GitHub
https://github.com/openssl/openssl/pull/262#issuecomment-94305500.

I needed that feature for this project https://github.com/sganis/rsa
and I wondered for long time why making a private key from given prime
numbers was not available in openssl, I think it would be useful for
educational purposes, even with limited-use cases.
Regards,
S.
On Mon, Apr 20, 2015 at 5:53 PM, Santiago Ganis<EMAIL_ADDRESS>wrote:

Fine, I will have to maintain my own implementation then, thanks. S.
On Sun, Apr 19, 2015 at 10:04 PM, Rich Salz<EMAIL_ADDRESS>wrote:

This is a pretty large patch for a pretty limited-use feature. See
BenBE's script. (API changes are not an issue, since this would be for 1.1)
But we're not going to take this.
—
Reply to this email directly or view it on GitHub
https://github.com/openssl/openssl/pull/262#issuecomment-94305500.


Updates to datapackage.json are not updated on the site

If I update a data package descriptor file datapackage.json it does not get updated on the site (not until it gets reloaded/rebooted).
We need some sort of a mechanism to reload descriptor files. There are multiple ways of doing this but I think something like checking/storing ETag and providing a webhook or something else which would go and look if the ETag has changed. This way we could trigger updates to datapackage.json via webhooks.
Another option would be to introduce time limits to the internal cache so when we fetch from the internal cache it first checks to see if a certain amount of time has passed and would then refresh (probably via an ETag mechanism like in the other suggestion above).

@tryggvib this is a great point. I guess we could just reboot every day atm but we do need a better solution.

OK, I've introduced the /admin/reload api so that anyone can reload the database. We could find a way to call this regularly or just make sure to hit it after you've updated your datapackage.jon.

FIXED.


Remove species stat changes

I shouldn't have to wiki if a slime takes less or more heat damage than an arachnid or if one moves 0.5m/s faster or some other stuff, just standardise it as it doesn't lead to interesting gameplay.

we could add it to the guidebook, stat changes gives antags a bit of a reward for scouting out their target and making a plan, like slipping a diona captain in welding fuel then lighting them ablaze discreetly as you pass by.

like slipping a diona captain in welding fuel then lighting them ablaze discreetly as you pass by.

This isn't a stat change?

diona take enough extra heat damage to where being set on fire is actually a threat. I'm assuming that's what you meant by stat changes.

I think I disagree with this partially. I have seen a lot of interesting gameplay from certain races having different stats but I can see why standardizing it would make balance a lot easier.

I am actually totally willing to do this, and even tried to (or rather layed out some plans) right after moths came out. The main issue from there is giving each face a mechanical sidegrade or upside/downside to account for it, and I don’t really have ideas for any of the races as to what that might be.

I'd be fine with removing stat differences if other races were made mechanically unique

not actionable/agreed upon rn


Google Drive: Access token on download

Hi,
I used this script to download a file from Google Drive:
var stream = fs.createWriteStream("demo.txt");
drive.files.get({
    fileId: myId,
    alt: "media"
}).on("end", function() {
    console.log("Finished");
}).on("error", function(err) {
    console.log(err);
}).pipe(stream);

The first time I run it, in "demo.txt", instead of getting the content of the file I am downloading, I get my private access token (which, of course, is not a good thing).
I would like to understand what I am doing wrong.
Thank you very much in advance!

Hope this helps
#501

p, td { line-height: 1.3; }
p { padding-bottom: 1em; }
a { color: #3697b3; font-weight: bold; text-decoration: none; }
a:hover { color: #000; text-decoration: underline; }
a:active { color: #000; text-decoration: underline; }

 Evernote helps you remember everything and get organized effortlessly. Download Evernote.

@Aspie96 Is this still an issue for you? If not, mind if I close this?

It very much is still an issue (not just for me).
I am actually no longer using Google Drive as a backend for this reason.
@jmdobry actually opened a new issue: #625 for this, so you can close mine if you wish.

Will do - thanks for the quick responses!


[Next] [Feature] Generalized query placeholders (including support for expanding arrays into multiple placeholders)

@abonander and I have been discussing the benefits of providing a more Python style of SQL placeholders for parameters
In Python database connectors, it looks like this:
conn.execute("SELECT %(name)s", name="Hello")

The connector takes care of:

Using ?, $1, or @p1 depending on the database driver
Expanding arrays into ?, ?, ?, ...
Allowing named parameters where none are supported such as PostgreSQL

The really interesting part is Intellij understands that %(name)s is a SQL parameter and correctly parses that query and still provides proper code completion ( as a side note, Intellij Rust recently gained support for SQL highlighting and code completion inside of sqlx::query! ).

We are proposing that we add support for the following ( both in query! and query ):
Positional Parameter
// "SELECT ?" in MySQL
// "SELECT $1" in PostgreSQL

sqlx::query!("SELECT {0}", 10);

Named Parameter
// "SELECT @id" in MSSQL
// "SELECT $id" in SQLite
// "SELECT $1" in PostgreSQL

sqlx::query!("SELECT {id}", id=10);

Inline Parameter (only macros)
// "SELECT @id" in MSSQL
// "SELECT $id" in SQLite
// "SELECT $1" in PostgreSQL

let id = 10;
sqlx::query!("SELECT {id}");

Array Parameter
// MySQL = "SELECT * FROM foo WHERE id IN (?, ?, ?, ...)"
// PostgreSQL = "SELECT * FROM foo WHERE id IN ($1, $2, $3, ...)"

sqlx::query!("SELECT * FROM foo WHERE id IN ({ids+})", ids=[1, 2, 3]);

{ids+} or {ids*} becomes a comma-delimited list of parameters
{ids+} for a 0 length array becomes NULL
{ids*} for a 0 length array becomes `` (nothing)

I was on the fence about doing something like this but we can teach Intellij to recognize {...} as a SQL parameter which would let Intellij continue to parse and provide completion in our SQL queries.
Thoughts?

Big thumbs up from me :+1:
If the inline form could also permit {foo.bar}, that would be amazing!

If the inline form could also permit {foo.bar}, that would be amazing!

We should probably follow the syntax recommendation here if we want to allow expressions: https://rust-lang.github.io/rfcs/2795-format-args-implicit-identifiers.html#alternative-solution---interpolation
let foo = Foo { bar: 50 };

// SELECT $1
sqlx::query!("SELECT {(foo.bar)}");

This also lets our Kleene operator work with these complex expressions:
let foo = Foo { bar: [1, 2, 3] };

// SELECT $1, $2, $3
sqlx::query!("SELECT {(foo.bar)*}");

I think that 90% of my uses of this are going to be {(foo.bar)} or {(foo.bar.baz)}. But since it's backwards-compatible to allow this without the extra parentheses later on, it seems fine to start without that.

The IN ({ids*}) syntax would be a god send for Sqlite in particular.
I wonder if it would be possible to add a minimal extensions of this syntax for INSERT as well?
I'd like to insert all the fields of a struct succinctly - as a nice ergonomic for developers who want to prototyping quickly and leave choosing specific fields as a later optimization.
Perhaps if there was a way to generate 'static str or const column names via a macro they could be expanded into the query at compile time?
[derive(sqlx::Columns)]
struct Foo { a: i32, b: i32, c: i32 }
let foo = Foo { a: 1, b: 2, c: 3 };

// INSERT INTO foos (a, b, c) VALUES (?, ? ,?)
sqlx::query!("INSERT INTO foos ({Foo::COLUMNS*}) VALUES (foos*)");

@D1plo1d I would probably prefer something a little less implicit like the following: https://github.com/launchbadge/sqlx/issues/591

Is there any update to when this might be implemented, or alternatively what blockers currently exist for implementation?
I have a use-case of passing a vec of arguments for a WHERE x IN (?) clause with SQLite and cannot use the listed postgres workaround due to the database type, this feature would be incredibly helpful towards that goal.

I would love this as I'm currently writing a lot of code to manually trick indices for postgres. Having this done by name instead would be amazing


fix(mv): Fix moving files across volumes

At some point options parsing happened inside _mv() and _cp() but that is no longer the case so a parsed options object should be used instead.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #982   +/-   ##
=======================================
  Coverage   97.22%   97.22%
=======================================
  Files          35       35
  Lines        1332     1332
=======================================
  Hits         1295     1295
  Misses         37       37

Impacted Files
Coverage Δ

src/mv.js
97.77% <ø> (ø)
:arrow_up:

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 aed6d99...3dc5898. Read the comment docs.

Is there any plan to release?

Is there any plan to release?


Fix WIFF SIM/SRM RTWindows bug

added automatic doubling of SIM/SRM RTWindows if a WIFF file was collected by SCIEX OS version less than 3.1 (reported by Phillip)

removed very old conditional code for .NET < 4

ProteoWizard installer (MSConvert/SeeMS)
SkylineTester.zip

@brendanx67 I have been trying to decide whether I want to leave this ignoreScheduledLimitsForChromatograms flag as an option or make it unconditional (i.e. always return the biggest chromatogram possible for scheduled MRM data). Turning it on does break one Skyline test (TestOptimization). But I'm not actually sure what the test difference is reporting:
Diff found at line 1:
450.695949,524.246337,20,peptides1.FNDDFSR.+2y4.light,80,21.1,17.00
>
450.695949,524.246337,20,peptides1.FNDDFSR.+2y4.light,80,21.1,16.50
#    at pwiz.SkylineTestFunctional.OptimizeTest.CovOptimizationTest() in C:\dev\pwiz\pwiz_tools\Skyline\TestFunctional\OptimizeTest.cs:line 704

What is that last column? Compensation voltage?
The user that had this problem wasn't using Skyline, but if they had, they would have the same problem this new option fixes: they would not have been able to see all the data they expected to see. That's because the API's default chromatogram extraction method uses too narrow RT window boundaries for some scheduled methods. So I wonder actually how many users this has affected without them realizing it.

@chambm,
I could not figure out how to get "TestOptimization" to fail.
I tried changing the C++ code so that "ignoreScheduledLimitsForChromatograms" was always true, and as far as I could tell, TestOptimization still passed.
If you get this pull request into a state where tests are failing, I'll try to figure out how to fix them.

@chambm, I could not figure out how to get "TestOptimization" to fail. I tried changing the C++ code so that "ignoreScheduledLimitsForChromatograms" was always true, and as far as I could tell, TestOptimization still passed. If you get this pull request into a state where tests are failing, I'll try to figure out how to fix them.

I'm actually getting 3 failures with ignoreScheduledLimitsForChromatograms = true in the MsDataFileImpl constructor: TestSrmTutorialLegacy,TestPeakPickingTutorial,TestAsymCEOpt
None are TestOptimization. I'm not sure what I did to cause that one.

I think we should just update the expected values and audit log files for "TestSrmTutorialLegacy" and "TestPeakPickingTutorial".
I'll try to figure out what is going on with "TestAsymCEOpt".

If we're not considering making user-configurable in Skyline, I'm inclined to just always enable it in pwiz and remove the option. Did you determine that the new behavior is preferable for those tutorials?
I'm a bit worried that I didn't see those test failures the first time I was working on this PR and set the parameter to always be true; maybe I didn't have it set to run the tutorials, but that doesn't explain why only TestAsymCEOpt failed now and only TestOptimization failed back then.

Did you determine that the new behavior is preferable for those tutorials?
I would not say "preferable".
The new behavior did not seem to raise any red flags.

Yes, getting rid "ignoreScheduledLimitsForChromatograms" sounds like a good idea.
I will try running the entire test suite on macs2 and make sure everything passes.


Save geometric_height of model levels in nc_diag files for wind.

Save geometric heights at model levels in ncdiag files in order to interpolate some wind data in a geometric height coordinate in UFO using IODA geoval files created from those ncdiag files.
(NOTE:  I still don't have a chance to run my test about this change on Discover, but it looks fine.)

Not sure how the changes in https://github.com/GEOS-ESM/GEOSana_GridComp/pull/129 sneaked into this PR!

Jianjun,
There is also a line of code to calculate zges from geopotential height, similar to zges_read. That line probably is no longer needed.
Yanqiu
From: Dan Holdaway @.>
Reply-To: GEOS-ESM/GEOSana_GridComp @.>
Date: Friday, May 12, 2023 at 8:33 AM
To: GEOS-ESM/GEOSana_GridComp @.>
Cc: "Zhu, Yanqiu (GSFC-6101)" @.>, Review requested @.***>
Subject: [EXTERNAL] [BULK] Re: [GEOS-ESM/GEOSana_GridComp] Save geometric_height of model levels in nc_diag files for wind. (PR #130)
CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC.
@danholdaway approved this pull request.
—
Reply to this email directly, view it on GitHubhttps://github.com/GEOS-ESM/GEOSana_GridComp/pull/130#pullrequestreview-1424419707, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARUMEBV52HDCMJCAFCAOVITXFYUYFANCNFSM6AAAAAAX7ABGEI.
You are receiving this because your review was requested.Message ID: @.***>

@gmao-yzhu Thanks. That redundant calculation is now deleted.

Thanks Jianjun.
From: Jianjun Jin @.>
Reply-To: GEOS-ESM/GEOSana_GridComp @.>
Date: Friday, May 12, 2023 at 1:07 PM
To: GEOS-ESM/GEOSana_GridComp @.>
Cc: "Zhu, Yanqiu (GSFC-6101)" @.>, Mention @.***>
Subject: [EXTERNAL] [BULK] Re: [GEOS-ESM/GEOSana_GridComp] Save geometric_height of model levels in nc_diag files for wind. (PR #130)
CAUTION: This email originated from outside of NASA.  Please take care when clicking links or opening attachments.  Use the "Report Message" button to report suspicious messages to the NASA SOC.
@gmao-yzhuhttps://github.com/gmao-yzhu Thanks. That redundant calculation is now deleted.
—
Reply to this email directly, view it on GitHubhttps://github.com/GEOS-ESM/GEOSana_GridComp/pull/130#issuecomment-1546041166, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARUMEBVJSHA7K5TOU6INAP3XFZU4LANCNFSM6AAAAAAX7ABGEI.
You are receiving this because you were mentioned.Message ID: @.***>


Migrate connections between engines

Is there any method to migrate connections context info between engines for multi-process program or multi-thread program？
I'm curious how litespeed do it with lsquic since litespeed web server is a multi-process program。

We do it using shared memory.  You can check out OpenLiteSpeed to see the details.  (Note that connections are not actually migrated between processes.)

Thank you very much for you reply !


Carbon release

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Lightning-SDK/129/rdkcentral/Lightning-SDK

Commit: d242d1e7e8c8ad8b5f3743841210b22e075d177d

Report detail: gist

Hi Michiel,
I approved this in the compliance tool as a "boilerplate code match".  But the offending file (events.js) has no header - please can be be added.  Several other code files in the pull req don't have headers either - can these be added?
Thank you,
Martin Hughes, RDK CMF Compliance Team


Postal code validation error messages don't match with regex

Postal code validation error message doesn't show correct information. It says that 99999 format should be correct, but it's not correct, error message is still shown.

In https://github.com/Adyen/adyen-web/blob/main/packages/lib/src/components/internal/Address/validate.ts:
language LT pattern is "/^(LT-\d{5})$/"
But in https://github.com/Adyen/adyen-web/blob/main/packages/lib/src/components/internal/Address/validate.formats.ts error message for language LT is: '9999 or 99999 or LT-99999'
There may be a similiar issue for other languages too

Hello @ignas-seskauskas2
This issue has been fixed on the latest version 5.68.1 and 6.1.1.


Fix DappKit Example: Exchanging cUSD and Locking CELO

Example: Exchanging cUSD and Locking CELO currently doesn't compile/work. Fix these docs so that the example is actually runnable.
Combine this with the reorganization of the README vs. usage.md docs.

@eelanagaraj I cannot find Exchanging cUSD and Locking CELO in the docs. where is it?

Also did you already do the  "reorganization of the README"

Merged Ponti's PR that fixed this into my reorg PR here, a review on that will close!


A top corner pixel is missing in non-filled CanvasItem.draw_rect()

Godot version
v4.0.alpha.custom_build [013efeef0]
System information
Windows 10, Intel Core i5 7200U CPU, Vulkan
Issue description
When using CanvasItem.draw_rect() with fill = false and width = 1, one of the top corner pixels are missing. From my observations, the top-left corner is missing when the pixel position is an integer and the top-right corner is missing when the pixel position has a decimal.
This also affects some areas of the editor, such as the 2D rectangle selection and the gradient editor:

Steps to reproduce
Each of these 3 options exhibits this bug:
a. Open the 2D editor and start a rectangle selection
b. Create a Gradient resource and add some points to the gradient editor
c. Attach a script to a CanvasItem-inherited node, and use draw_rect() with fill = false in the _draw() function.
Minimal reproduction project
No response
Possibly Related
https://github.com/godotengine/godot/pull/32657
https://github.com/godotengine/godot/issues/32279

@fire-forge Can you reproduce this in 3.4.3?

@Calinou in 3.4.3, the bottom-left corner is missing with an integer position and nothing is missing with a decimal position.

Integer position:

Decimal position:

I think I got the same issue in Godot 4.0 Beta 4.

The corner pieces of the rectangle are missing, iff rect.x<0.
draw_rect(rect, Color.LIME_GREEN, false, 6)

@mrimvo This looks like a different bug, where negative X results in too short lines, and negative Y results in too long lines. I know how to fix it, but want to first see if daleexev's PR will fix it.

Quoting kleonc's comment:

I think #58775 is not really solvable in a general case. It's not just a matter of obtaining proper final positions of the line endpoints in the coordinate space of the viewport/framebuffer/render target (or whatever you call it) which would be needed to be able to apply a proper offset in that space (small final offset; regardless of the zoom etc.). What we'd also need to know to determine what such offset should be is the exact algorithm used by the Vulkan/OpenGL/etc. for rasterizing the line primitives. And that's problematic, because these can differ between implementations since specifications aren't super strict:
* [OpenGL 3.3 Basic Line Segment Rasterization](https://registry.khronos.org/OpenGL/specs/gl/glspec33.core.pdf#subsection.3.5.1) (for [4.6 it's pretty much the same](https://registry.khronos.org/OpenGL/specs/gl/glspec46.core.pdf#subsection.14.5.1)),

* [Vulkan 1.1 Line Segments Rasterization](https://registry.khronos.org/vulkan/specs/1.1/html/chap25.html#primsrast-lines).

So even assuming that rasterization is done according to the diamond exit rule (which is not guaranteed; but maybe it's actually the most common case?thinking no idea about that) we would still need to find a way to somehow obtain the final positions of the line endpoints within the fragments' coordinate space (I don't see how we could currently do it). And then we would still need to find a way of how to offset the vertices (probably branching into many different cases) to always produce satisfying fragments. E.g. take a look at the image from this post and imagine all possible configurations of the vertices (colored dots); and yeah, the rect can end up being transformed in there (so take into consideration rotations or... skewing; yeah, good luck with that smile).
TL;DR: I don't see us solving it. Would love to be surprised by someone but I don't think it will happen.
For a non-general solution / hacky solution what maybe could be done is adding a method (are a bool param to the current draw_rect) which would be supposed to work properly only in a very specific conditions: when the given CanvasItem is not transformed so the offset we would apply to the vertices would actually be equivalent to the offset in the fragments' space. Still it wouldn't be guaranteed to always work because of the loose specifications mentioned previously. Anyway, I'm not convinced that trying to handle such edge case is a good idea.

A few hints:

#69851 fixed this for positive widths, this issue only applies to negative widths. If you explicitly pass width = 1, then the corners should not be missing or brighter.
Thin rectangles can indeed be rendered slightly incorrectly, but it won't be very noticeable as lines with negative widths remain thin when the CanvasItem is scaled. As long as you don't stretch the Viewport image. If you expect this (for example in pixel games), then you should always pass width = 1.
See godotengine/godot-docs#6455. This is not obvious, but important information that will allow you to avoid some problems.


Regenerate .NET SDK for Front Door to Include Recent Swagger Changes

Summary:
Regenerating .NET SDK for Front Door to include recent Swagger changes that added the following parameters:

HealthProbeSettingsUpdateParameters: HealthProbeMethod (Configures which HTTP method to use to probe the backends defined under backendPools) and EnabledState (Operational status of the Front Door load balancer.)
BackendPoolsSettings: sendRecvTimeoutSeconds (Send and receive timeout on forwarding request to the backend. When timeout is reached, the request fails and returns.)
CustomHttpsConfiguration: minimumTlsVersion (The minimum TLS version required from the clients to establish an SSL handshake with Front Door.)

How Verified:

Modified unit test to include new parameters

Hi @jessicl-ms , please fix the CI errors, and you might as well want to update the tags in AzSdk.RP.props

I updated the tags in AzSdk.RP.props. Will work on figuring out why the unrelated WAF tests are failing.

                                            Action = "Redirect",

This is causing the WAF unit tests to fail when running in record mode. Change it to the following to make the tests work.
RuleId = "942100"

Refers to: sdk/frontdoor/Microsoft.Azure.Management.FrontDoor/tests/ScenarioTests/FrontDoorTests.cs:226 in 50ef286. [](commit_id = 50ef28635baaa832bd419d2cbffcf5010c58cee8, deletion_comment = False)

Hi @isra-fel A couple of the ci are failing with this error
error : Failed to resolve SDK 'Microsoft.Build.CentralPackageVersions/2.0.36'. Package restore was successful but a package with the ID of "Microsoft.Build.CentralPackageVersions" was not installed. I'm unable to repro this locally. Have you seen this error before? Is this a build issue caused by a version update? Thanks!

/azp run net - client -ci

/azp run net - client - ci

@jessicl-ms Re-run the piplines, all passed. I'll just go and merge it.

@jessicl-ms Re-run the piplines, all passed. I'll just go and merge it.

Thank you!


Feature request: Add automated tests to stac-node-validator

Is your feature request related to a problem? Please describe.
It would be good to make sure stac-node-validator is in a healthy state and being maintained.
Describe the solution you'd like

[x] Add Dependabot support

[x] Add automated tests

Describe alternatives you've considered
We could leave this up to the stac-node-validator maintainers.
Additional context
Test PRs are welcome.

This looks good from what I can tell. And after discusison wtih @l0b0


Configuration to run tests on firefox on saucelabs.com gives "java.lang.NullPointerException"

What are you trying to achieve?
Run tests on firefox on saucelabs.com
On running them, I get a
[1.basic:firefox] One a page which has the fitment widget enabled --
[1.basic:firefox]   I was able to see the widget
[1.basic:firefox]   ✖ "before each" hook: codeceptjs.before for "I was able to see the widget" in 13301ms
[1.basic:firefox] Error: java.lang.NullPointerException

What do you get instead?

Provide console output if related. Use --verbose mode for more details.
Tests are run as :

./node_modules/.bin/codeceptjs run-multiple basic --config codecept.sauce.js --steps

// Terminal output
➜ npm run test:sauce

><EMAIL_ADDRESS>test:sauce /Users/n0s00jx/codebase/work/CEV/codeceptjs-playground
> codeceptjs run-multiple basic --config codecept.sauce.js --steps

2019-03-04T17:59:38.013Z DEBUG wdio-config: @wdio/sync not found, running tests asynchronous
[1.basic:firefox] CodeceptJS v2.0.4
[1.basic:firefox] Using test root "/Users/n0s00jx/codebase/work/CEV/codeceptjs-playground"

[1.basic:firefox] One a page which has the fitment widget enabled --
[1.basic:firefox]   I was able to see the widget
[1.basic:firefox]   ✖ "before each" hook: codeceptjs.before for "I was able to see the widget" in 13301ms
[1.basic:firefox] Error: java.lang.NullPointerException

[1.basic:firefox] -- FAILURES:

  1) One a page which has the fitment widget enabled
       "before each" hook: codeceptjs.before for "I was able to see the widget":
     java.lang.NullPointerException

  Run with --verbose flag to see NodeJS stacktrace

[1.basic:firefox]   FAIL  | 0 passed, 1 failed   // 14s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test:sauce: `codeceptjs run-multiple basic --config codecept.sauce.js --steps`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test:sauce script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/n0s00jx/.npm/_logs/2019-03-04T17_59_51_845Z-debug.log

Details

Protractor || WebDriverIO || Nightmare version (if related)
Configuration file:

exports.config = {
  tests: "./*_test.js",
  output: "./output",
  helpers: {
    WebDriver: {
      url: "http://localhost:8080/",
      browser: "chrome",
      user: "111",
      key: "111",
      host: "ondemand.saucelabs.com"
    }
  },
  multiple: {
    basic: {
      browsers: ["firefox"]
    }
  },
  include: {
    I: "./steps_file.js"
  },
  bootstrap: null,
  mocha: {},
  name: "codecept-playground"
};

@puneet0191 could you please help

@nilanjansiromani ,
Please, add your test and before hook.
And run with --verbose key instead of --steps and paste output

@nilanjansiromani try this,
"WebDriverIO": {
      "url": "http://localhost:8080/",
      "browser": "firefox",
      "user": "sauce_user",
      "key": "sauce_key",
      "desiredCapabilities": {
        "os_version": "Windows 2010",
        "version": "63.0",
        "platform": "Windows 10",
        "windowSize": "maximize"
      }
    }

haven't tried multiple with sauce before so not sure, also try to use the helper for saucelabs to publish the rest results, https://www.npmjs.com/package/codeceptjs-saucehelper

Will try and update tonight.

Try upgrading codeceptjs and webdriverio; I saw similar behaviour with 2.0.6 and 5.6.2, but upgrading to 2.0.7 and 5.7.2 seems to have fixed it.

This actually worked !!