Random icons missing from sprite.

It is a question.
Current behaviour Sometimes random icons missing from sprite.
Expected behaviour Always all icons includes in sprite.
Maybe you know about this issue and easily can help us. If you have not encountered this problem before i can add more description. I tried to use svg-sprite-loader without svgo and it is not affected.
https://gist.github.com/BrRenat/3decec5e6ce42ca4db4e01c3db147d9c

Node.js version: 9.11.1
webpack version: 4.5.0
svg-sprite-loader version: 3.7.3
OS type & version: macos, linux, windows

@kisenka Sure! I will add more description and demo.

It's better to create separate git repo which I can clone, run and see the problem.


Remove error classes and use http-errors.

Remove the previously exported error classes to use http-errors instead.
Error details are now snapshot tested.

Most errors were a pretty obvious conversion, but I do wonder about the errors for when the client unexpectedly disconnects. I chose the status code 499, which is a non-standard code used by nginx for Client Closed Request which seems like a perfect fit: https://httpstatuses.com/499. http-errors does not have a special class for this code though, so it falls back to a BadRequestError class name.

499 is the perfect code to use here, is it will mirror the logs in any nginx proxies, etc.


[Draft]

This is draft PR. Please do not review.
Motivation
This PR updates Safety Rules to avoid signing votes using the consensus key directly, and instead make all requests to the storage backend. It's a little rough (there's probably a few better ways to make these changes), but it's useful as a prototype for performance measurements to see how bad things will be.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
All local smoke tests seem to pass... (some unit tests fail, but this seems to be an orthogonal issue related to error handling)
Related PRs
None.

Closing this out for now. We can return to it when the time is right.


rename u19 etl

closes #173
Renames the U19Etl class to a more generic name.

Lots of issues that don't seem to be coming from changes I've made. Requesting a look from @mekhlakapoor.


Bump minor version, backwards incompatible changes with gRPC metrics.

To provide more context for the readers, the backward incompatible changes are introduced in:
https://github.com/Stackdriver/stackdriver-prometheus-sidecar/pull/201 , as we won't export certain metrics anymore (e.g. ocgrpc.ClientServerLatency).


Add some basic documentation

Added some very basic docs how to use shipyard

Thanks Daniel, I've committed your suggestions


[sqlpp11-connector-postgresql] Added new port

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: vs-76 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Deduce forward reasoning from backward and variants

Since goals are ephemeral, equation nodes that involve backward reasoning from goals (especially) should also generate ones that are direct.

The equations are loosely coupled anyway.

This is worth doing. Specifically:

Important: any type as a TargetTyp can be generated by the fromTyp node - we add these since the type may have been generated by the fromGoal noode.
Any term appears as a TermWithTyp for its type, using a conditionedVariable node.
Similarly for functions as well as functions with a fixed domain.
We can also flip between picking a function and an argument first.
Unified applications can be resolved as a string of function applications.

Unification is complicated as lambdas are also generated. Excluded for now.


docs: Add Ts.ED framework Some packages using Ajv

What issue does this pull request resolve?
This PR add the framework Ts.ED because this package use Ajv as validator to validate input data.
What changes did you make?
Update the readme
Is there anything that requires more attention while reviewing?
Thanks team for your awesome work on AJV!

sorry, the readme/site was restructured - please add to this site section: https://ajv.js.org/#who-uses-ajv

Hello @epoberezkin
Thanks for your reply. Can you be more precise please :)
How I can do this? Where is located the file ?


[WebOS] Add a header file to fix build error

Changes

Added a header file in WebOS Platform to fix build error

Testing

Tested done on WebOS

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Delay export service should print stack trace if there are exception o…

What is the purpose of the change
Optimize delay export service logic.
Pre condition:
If module A and B dependency the same dubbo-config core, and it define netty server port is 20880, config delay export service time is 1000 and protocol is dubbo.
Usage scenarios:
When I run module B after successfully started module A at the same compute, module B can successfully started, but module B not export any service, because module A occupied 21880 port.
Conclusion：
So, I think delay export service should print stack trace if there are exception occur so that programmer can see errors in console.
Brief changelog
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[ ] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8125 (0f9d62a) into master (b194bb0) will decrease coverage by 0.75%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #8125      +/-   ##
============================================
- Coverage     61.14%   60.38%   -0.76%
+ Complexity      490      488       -2
============================================
  Files          1090     1090
  Lines         43937    43897      -40
  Branches       6418     6386      -32
============================================
- Hits          26867    26509     -358
- Misses        14091    14412     +321
+ Partials       2979     2976       -3

Impacted Files
Coverage Δ

...in/java/org/apache/dubbo/config/ServiceConfig.java
66.37% <100.00%> (+0.19%)
:arrow_up:

...ookeeper/ZookeeperDynamicConfigurationFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...gcenter/wrapper/CompositeDynamicConfiguration.java
0.00% <0.00%> (-73.34%)
:arrow_down:

...fig/configcenter/TreePathDynamicConfiguration.java
25.71% <0.00%> (-60.01%)
:arrow_down:

...pport/zookeeper/ZookeeperDynamicConfiguration.java
0.00% <0.00%> (-57.15%)
:arrow_down:

.../dubbo/metadata/report/MetadataReportInstance.java
12.50% <0.00%> (-40.63%)
:arrow_down:

.../configcenter/support/zookeeper/CacheListener.java
0.00% <0.00%> (-28.58%)
:arrow_down:

...mmon/config/configcenter/DynamicConfiguration.java
68.18% <0.00%> (-18.19%)
:arrow_down:

...gistry/client/migration/MigrationRuleListener.java
55.88% <0.00%> (-17.65%)
:arrow_down:

...ient/metadata/store/RemoteMetadataServiceImpl.java
38.59% <0.00%> (-17.55%)
:arrow_down:

... and 58 more

Continue to review full report at Codecov.

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


When calling the 'Phaser/Geom/Intersects#LineToLine' method without passing in the third parameter, 'out', avoid creating a new Phaser.Geom.Point, as it will be totally inaccessible.

Please do not update the README or Change Log, we will do this when we merge your PR.
This PR (delete as applicable)

Fixes a bug

Describe the changes below:
Not quite a bug fix😅: just a very small performance improvement by not creating an inaccessible object.
In fact, the third parameter, 'out', must have an external reference (e.i. it must be passed in by the user), otherwise creating and populating an unreachable new Point is just a waste of memory and computing time.

👍


JBPM-5293 - Remove Lists of group names from 'getGroupsForUser( ... )…

…' method signature in UserGroupCallback interface
depends on https://github.com/droolsjbpm/jbpm/pull/652
@krisv @psiroky  and the last one from this work.

+1


Improve GitIgnore parsing

https://github.com/sabhiram/go-gitignore

Make sure to also follow .gitignore files within sub folders.

Solved - now we are able to properly respect a Git repository ignore files configuration when creating thee deploy tarball.


fixed transfer of bad namespace information on login (to new cluster)

fix #2299
I went with the last option: check validity, clear data if not, and report the issue in that case too
(all other options do not really fit into the scope of 1.8.1 to come)

I'm not sure on what should be the expected behaviour for a user that has not access to an existing namespace.
Maybe is better to have a more generic message, like namespace '%s' not found in targeted cluster instead of invalid. That is the behaviour of different website/app (404 instead of errors).

Sure.

Verified fixed in v1.8.1
Created entry namespace: nonexisting in settings and performed login:
./epinio login --user admin --password password https://epinio.<IP_ADDRESS>.sslip.io

🚢  Login to your Epinio cluster [https://epinio.<IP_ADDRESS>.sslip.io]

⚠  Certificate signed by unknown authority

|     KEY     |     VALUE      |
|-------------|----------------|
| Issuer Name | CN=epinio-ca   |
| Common Name | epinio-ca      |
| Expiry      | 2023-August-23 |

Do you want to trust it (y/n): y

✔  Trusting certificate for address https://epinio.<IP_ADDRESS>.sslip.io...

✔  Login successful

⚠  Current namespace 'nonexisting' not found in targeted cluster

⚠  Cleared current namespace

⚠  Please use `epinio target` to chose a new current namespace


Simple value hover doesn't seem to wrap

Tests #1832

The test item says the hover would wrap, but it seems to be shortened instead.

Nah, it is good, it is just that the node debug adapter cuts the string. If you use make the window smaller you will see that it is nicely wrapped.
We are aware of the node debug adapter cutting the string thus closing this


[Bug] Dashboard: Weblog pane includes pages in post count

Bug Description
While this counting bug was fixed for actual published weblogs, I just noticed it’s still there in the omg.lol Dashboard.
Steps to Reproduce
No response

So, this is kind of intentional, but also a little confusing. I’m using the term “entries” there, which as far as weblog.lol is concerned mean posts + pages, but... I’m now realizing that the more typical use of the term entry is synonymous with post, and that pages are something else entirely.
Ultimately some folks might use weblog.lol with pages only (no posts), and that’s perfectly fine... but I don’t want them to see "no entries yet" or "no posts yet" or whatever. But now I feel like I'm doomed to generate confusion here no matter what, heh.
If you have any thoughts, I'm all ears!

Items sounds great! Just ran with it. Thanks!


UnicodeDecodeError: 'gbk' codec can't decode byte 0x80 in position 585: illegal multibyte sequence

Expected behavior
System: windows 10 Build 17134
Local Python: Python 3.6.5 :: Anaconda, Inc.
When I finish the specification, I want the program to run. But this problem occurred.
Actual behavior
This problem occurred when I tried to start the program.
Traceback (most recent call last):
  File "start.py", line 67, in <module>
    main()
  File "start.py", line 26, in main
    load_implementations()
  File "start.py", line 33, in load_implementations
    load_files(d)
  File "C:\Users\Blueshark-JF\AppData\Roaming\Python\Python36\site-packages\getgauge\static_loader.py", line 24, in load_files
    pf = PythonFile.parse(file_path)
  File "C:\Users\Blueshark-JF\AppData\Roaming\Python\Python36\site-packages\getgauge\parser.py", line 18, in parse
    return PythonFile.Class.parse(file_path, content)
  File "C:\Users\Blueshark-JF\AppData\Roaming\Python\Python36\site-packages\getgauge\parser_parso.py", line 30, in parse
    content = f.read()
UnicodeDecodeError: 'gbk' codec can't decode byte 0x80 in position 585: illegal multibyte sequence

I went to check my script and found that I wrote Chinese notes in the script, such as this:
def do_requests(method, url, retry_time=3, **kwargs):
    while retry_time:
        try:
            return session.request(method, url, **kwargs)
        except requests.exceptions.ConnectionError:
            # Failed to establish a new connection: [WinError 10061] 由于目标计算机积极拒绝，无法连接。
            pass
        retry_time -= 1

Steps to reproduce

Initialize an project using the gauge init python command
Write any Chinese character in the .py script, Such as the following

This problem can occur using the gauge run command or the gauge run specs /

Gauge version
# gauge -v
Gauge version: 1.0.3
Commit Hash: ff6c0c3

Plugins
-------
html-report (4.0.5)
python (0.3.4)
screenshot (0.0.1)

@OxNone
As mentioned in https://github.com/getgauge/gauge-python/issues/86#issuecomment-396228074 please use # -*- coding: utf-8 -*- to tell explicitly that utf-8 encoding is used.

Thanks your reply. I know this way, but it doesn't work in Windows system. This solution seems to work in Python 2.x.

em...
I think this should be the reason why the system default language, because in Windows, when the regional language is selected as Chinese, the system code will change to GBK

And when I changed the area to English, it works fine now. Thank you again for your answer.


Support for Node-RED < v1.0

https://github.com/d-Rickyy-b/node-red-contrib-ffpass/blob/5cb932a95dd2402ee5009ad7a70c8d9f3c3acb2a/ffpass/ffpass.js#L103

NodeRed  <= 1.0 is already out of maintenance (https://nodered.org/about/releases/), so I won't put any effort into supporting these versions of NodeRed


Consider offering separate containers for each PHP version

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
We'd like to slim down the webserver image to save CI minutes, both in ddev itself and in projects using DDEV in CI.
One of the largest single-item sets of packages in ddev is all of the different PHP versions. Of course, this is great for locals in that it's pretty quick to test upgrading to a new PHP release. However, it also means you're getting old PHP versions you may not need (like the 5.x releases). And, for CI, you typically only need one PHP version, so why spend time downloading and extracting those files during docker pull?
Describe your solution
As a proof of concept, rebuilding the webserver image to just have PHP 8.2 saves around 260MB of docker image data. Could we add a config option, such as single_php_version: true that when enabled downloads a variant of the webserver image that only has the selected PHP version in it? Then, users by default get the good experience today, but they can opt in to smaller images if they would like.
Describe alternatives
We could perhaps just publish different images, and users could override the image tag directly in their config. But, then ddev versions could become out of sync which seems painful.
Additional context
No response

Thanks for the thoughtfulness about creating these issues!
We spent some sigificant time talking about this particular one, and about splitting webserver from php. The usability cost to users would be enormous, so we decided it wasn't worth it. (People wouldn't know where ddev ssh ended up, what context they needed to use for a .ddev/web-build/Dockerfile, etc.

I wasn't thinking of splitting to a separate php-fpm only container - just providing different webserver variants that only have one PHP version installed, with php still stacked in the same image.

Oh, that wouldn't be as hard, thanks. And if done like we do ddev-dbserver it would be done in parallel and pretty fast.
It would mean changing PHP version would involve a docker pull though, which would probably be unwelcome and a bit of a surprise. Maybe it wouldn't be bad if we used it as a separate layer and didn't squash the layers.
There is also the very occasional user that tries to use 2 versions at same time as in today's slack, but that's weirder than weird.

It would mean changing PHP version would involve a docker pull though

That's why I think this should be opt in, at least at first. If we just build additional images, but keep the existing webserver one, most users wouldn't see a change. But for those of us doing CI, we could add ddev config --single-php-version true or something and save some time!

There is also the very occasional user that tries to use 2 versions

I actually did that a few months ago. I was working with a site that only worked with PHP 7.2, but Pantheon's terminus required PHP 7.4. Having both versions available made it super easy to just prefix /usr/bin/php7.4 terminus ... and get things working.

One more note, that applies to the other issues too. I built an image that contains all of these changes together so I could compare timings in real-world GitHub actions.
DDEV 1.23.4: https://github.com/Lullabot/drainpipe/actions/runs/11069357996/job/30756742446 - the install ddev step is 1m16s (which is about average).
With a slimmer image, it's 1m1s, about a 20% improvement: https://github.com/Lullabot/drainpipe/actions/runs/11077498311/job/30788501427?pr=709

One conversation to have about these strategies: DDEV has always been focused on local development, and every alternate use (like CI or hosting) has always been considered just "gravy", extras that people use the way they want, but are not the aim of the project.
It's possible that an alternate project or sub-project should be spun off, especially for the CI needs.

I've been thinking about the same. The PRs I've filed are things I'm pretty confident would benefit all users and development of DDEV itself. For example, on my home internet connection a download reduction of 200MB would save me ~40 seconds of download time when updating ddev, using a different computer, or switching docker providers.
Also from a development standpoint - standardizing on ddev for CI vastly improves our day-to-day developer experience too. It means you have a consistent local environment to test CI integrations, can more easily switch CI providers, and so on.
I also noticed that even when you specify webimage:  in your config file, ddev will still download the normal webserver image on ddev start. So, to use a custom image we have to overwrite the ddev tag, which is tricky!
Perhaps a half way there measure would be to make installing old, EOL PHP versions optional or dependent on the recipe. I 100% see the value in shipping PHP 5.6 - but the oldest PHP versions we've seen even in unmaintained WordPress sites is the 7.x branch.

We've long had one-off techniques for even older versions of PHP in ddev/ddev-contrib. We could stop providing 5.6 and 7.0 and 7.1 and instead have an add-on for those.  With @stasadev's new technique of providing args to add-ons it would be even that much easier. And of course, we have the maybe-not-ever-used https://github.com/rfay/ddev-php-patch-build which can provide most any version of PHP, with some caveats.  The general idea would work fine and we could really trim things down.

I'm really liking this initiative. My current thinking on options:

Keep the configuration as it currently is (driven by php_version), but remove all old versions up through 8.0. Then, when the php_version is set to something else, 5.6-8.0, add a layer to the image at start-time adding that php install + its traditional config. This would remove lots of stuff from the default image, but not change the behavior at all, but there would be a minor build time increase for people using older php versions on first start.
Add a "full" ddev-webserver image with all the php versions in it and all the flexibility. Use a lighter one by default. This probably results in complexity for configuration, or perhaps when you choose something not in the "newer" versions use the heavyweight upstream version. This might also give benefits beyond PHP, where some other things (like locale versions) could be factored out.
Provide separate ddev-webserver for each PHP version. Sounds fairly easy, the build is not hard on github actions by spinning off into a matrix. This approach may surprise people when changing php version by requiring a new docker pull (as changing mariadb version does currently)

add a layer to the image at start-time adding that php install + its traditional config. This would remove lots of stuff from the default image, but not change the behavior at all, but there would be a minor build time increase for people using older php versions on first start.

In general, I do think avoiding start-time build steps is a good idea. However, the hard part is supporting arbitrary combinations of PHP versions. I don't think it's really worth it for us to prebuild dozens of version combinations of PHP.

Add a "full" ddev-webserver image with all the php versions in it and all the flexibility. Use a lighter one by default.

What about going the other way around? Prove out the lighter ones are working well, are used, and wait until do something that could break existing installs.

Provide separate ddev-webserver for each PHP version.

I think this would be my preference as well, at least to start.
Here's an outline of a possible implementation plan:

Add new webserver images containing individual modern versions of PHP (8+).
To start, let users manage this just by setting webimage directly. Avoid adding new config options for now. We'd need to fix the issue of ddev force-downloading ddev/webserver even if an alternate webImage is specified.
If all goes well, create images for the rest of the PHP versions.
Add a simpler config option to opt-in to the images instead of webImage.
Then, 6-12 months from then, gather feedback, check analytics, etc, and see if we should flip the default to only ship a single version of PHP.

Off topic from this issue, but another way to tackle the same problem space would be to look into optimizing ddev start itself. In CI, about half our startup time is downloading and installing ddev (~30s), and the other half is starting it (30s). It wouldn't help with bandwidth or disk space, but reducing container start time would have a similar benefit.

To start, let users manage this just by setting webimage directly. Avoid adding new config options for now. We'd need to fix the issue of ddev force-downloading ddev/webserver even if an alternate webImage is specified.

I try to forget and let everybody else forget that this has ever existed :) People who use it invariably end up lost. :)

Off topic from this issue, but another way to tackle the same problem space would be to look into optimizing ddev start itself. In CI, about half our startup time is downloading and installing ddev (~30s), and the other half is starting it (30s)

I imagine that most of the time starting - that other 30s - in a non-mutagen environment, is waiting for the containers to become ready. If we don't wait, we get unpredictable behavior. But your analysis and followup is very welcome. We're always super-motivated to improve startup time while retaining consistent behavior.

I'm pretty excited about the idea of building only currently supported versions of PHP in the main container, and adding others if people change to a different PHP version. For example, right now, PHP 8.1-8.4 would be preinstalled. But 5.6 would not be there, but changing to php_version: 5.6 would add a layer installing the necessary packages and its config. This would involve no change to user behavior or configuration at all, and be a huge win in image size.

I'm pretty excited about the idea of building only currently supported versions of PHP in the main container, and adding others if people change to a different PHP version.

Yes, this sounds really cool.
It would be good if we had the option to opt-out of PHP altogether, like we do with the database container.
This would be helpful for people running/serving node projects (Next, Gatsby, best-javascript-framework-since-yesterday, ...)

If "cool" is just making the web container smaller, we're all living pretty sheltered lives :)


Add FieldDefault method to Mutation interface and entc template.

The Save/SaveX methods on the generated Create mutation wrapper sets field defaults before hooks are run so code has no way to tell which fields were explicitly set and which are using default values.
This change adds a FieldDefault method to Mutation that is similar to the existing Field method, only it returns a fields default value. This allows code to compare the current and default value and infer if the
field was explicitly set to a non-default value.
A few things to note:

The template code will produce an empty switch statement if there are no field default values. I did not see an easy way to check for this, but if it is a deal breaker I can loop the fields to check before proceeding.
FieldDefault has interaction with ent/runtime just like the internal defaults method for Create and Update mutation wrappers. Instead of exposing an error I am simply returning nil, true when the function has not been properly set. I figured this issue can be caught elsewhere, such as during the save call (which will generally precede use of FieldDefault) and it is not worth complicating the API by also returning an error value. Just let me know if this is a mistake and I should add in an error return parameter like defaults does.

My motivation for making this change was to allow privacy rules to protect specific fields from alteration. I have user attribute fields (is_staff, is_superuser) that need to be set during user creation by an admin and should later be alterable by an admin, but should never be editable by anyone else even though the user may alter other fields on their own User entity.
My User policy looks like this:
func (User) Policy() ent.Policy {
	return privacy.Policy{
		Query: privacy.QueryPolicy{
			rule.AllowIfSuper(),
			rule.QueryUserFilter(),
		},

		Mutation: privacy.MutationPolicy{
			rule.AllowIfSuper(),
			rule.DenyIfNotActiveOrgAdmin(),
			rule.DenyFields("is_staff", "is_super", "password_hash"),
			// ...more filtering
		},
	},
}

I also have a rule.AllowFields that will deny access if a field is being set that is not in the list.
Here is one of the rules that makes use of the new m.FieldDefault method:
// DenyFields checks the create/update mutation for set fields and denies
// access if any set fields are found in the fields parameter.
func DenyFields(fields ...string) privacy.MutationRule {
	return privacy.MutationRuleFunc(func(ctx context.Context, m ent.Mutation) error {
		ctx = disableRules(ctx)
		view := viewer.FromContext(ctx)
		if view == nil {
			return fmt.Errorf("DenyFields: %w", NoViewerError)
		}

		illegal := []string{}

		changed := m.Fields()

		for _, c := range changed {
			for _, f := range fields {
				if c == f {
					// If create, see if value is equal to default.
					if m.Op().Is(ent.OpCreate) {
						cur, _ := m.Field(c)
						def, _ := m.FieldDefault(c)
						if cur == def {
							continue
						}
					}
					// Defaults aren't applied on update calls, so only check if field was set.
					illegal = append(illegal, c)
				}
			}
		}

		if len(illegal) > 0 {
			return privacy.Denyf("viewer cannot set field(s): %s", strings.Join(illegal, ", "))
		}

		return privacy.Skip
	})
}


Exercise JSON logging

We had an issue #423 where JSON logging was completely broken, and this was not detected.  Add a simple exercise of the JSON logging type (including exporting restructureJsonLog for access)

@abukharov feeling a little uncomfortable about making stuff in logger.ts public in order to enable testing (and the slightly grotty way in which I substitute the output function).  Any better ideas?

PS: this test (correctly) fails when #424 is reverted.

Too slow, merging


Proposal: Coroutines with Async: an easy way of sync an async

All of us know that both coroutines and async\await is desirable features.
Some of us complained to fact that these two aren't composable enough.
That's right: the main reason of it is that generators basically are sync, when async\await - async).
Proposal:
My proposal is to make some special case of generator(can't tell about syntax):
1)The generator which yields await!{...} should select from features.
2)Such case should block thread until at least one of futures is ready(and yield its result).
The benefits are following:
1)It will allow us to write less async code(that's because async code can be turned to spaghetti much easier)
2)It will allow us to create nice async iterators, and write sync-like asynchronous code.

The async working group and the language design team have been working in cooperation to develop a design for asynchronous generators. If you're interested in joining the discussion, I'd encourage joining the wg-net-async discord channel and joining in discussion there.


Swift: Allow cells to define their own size

I thought it would be nice to have protocols that allow cells to provide their own size, so I introduced the following Protocols and a new initializer for BindingData:

ListSwiftSizeProviding: Protocol for cells that can provide their own size based on context and value.
ListSwiftFixedHeightProviding: Protocol for full width, fixed height cells.

That makes sense. Also it doesn't really bridge any IGListKit feature, so it probably shouldn't be there anyway.


upgrade to sbt 0.13.16 + misc other changes

not to be merged until 0.13.16 final is out.  in the meantime,
just helping test the new sbt version.  @eed3si9n @dwijnand

test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1468/consoleFull

EXTRACTION FAILED (failed: scala-parser-combinators)

Cyclic reference involving
*:scalaVersion
root-950fabd31421f835198eabd03f5fa1753af44c91/*:crossScalaVersions
root-950fabd31421f835198eabd03f5fa1753af44c91/*:scalaVersion

@SethTisue known?

perhaps a recent change in that repo. I'll investigate

[scala-parser-combinators] Commit: 2324d69d24e5540e220c91e46aa07a0962e3b330

This is from Jan 25 https://github.com/scala/scala-parser-combinators/commit/2324d69d24e5540e220c91e46aa07a0962e3b330

yeah, so this must have to do with the sbt version bump. @dwijnand is there any change in 0.13.6-M1 that could affect this somehow?
the scala-parser-combinators build has scalaVersion in ThisBuild := crossScalaVersions.value.head and then the crossScalaVersions doesn't consult any other keys

maybe sbt/sbt@ff017eb475fbf18b8066125596bcd1a8cd8fb3ff ?

maybe sbt/sbt@ff017eb ?

That could be the culprit since I did add scalaVersion at the project level.

I can start up sbt 0.13.16-M1 on 1.0.x branch of scala-parser-combinators, so I'm wondering if the problem was actually to do with AutoPlugin ordering that @dwijnand fixed in https://github.com/scala/sbt-scala-modules/pull/20. Will scala/scala-parser-combinators@6cac8c3c603e3ff3ec1a3c8dde438d38fbebcced be forward ported?

Actually the forward porting was already done 5 days ago in https://github.com/scala/scala-parser-combinators/pull/115, so it should build now.

rebased. new test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1493/consoleFull

[info] >>> The dbuild result is------------: SUCCESS (project rebuilt ok)

Awesome.

test run with 0.13.6-RC1: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1689/consoleFull (404 til Jenkins sits and ponders why the little birds flit from branch to branch, why don't they just sit still?)

new test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1690/consoleFull (404 while Jenkins gazes blankly at Warren Harding's deathbed)

I think I'm going to merge this even though 0.13.16 is still in release candidates, since it enables building the master branch of MiMa (now that Scala 2.12 support in that repo was merged), which is a pretty nice benefit.

aborted the old test run — everything extracts, at least.
new test run to test just the conductr-lib reinstatement: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1691/consoleFull

new test run https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1692/consoleFull

new test run https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1693/consoleFull

sure is dark down in this rabbit hole

the scalafmt part of this is turning out to be especially hard, so I'll make a separate PR out of that

ok I think this is done, but we need a full test run to make sure nothing regressed: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1696/consoleFull


'Fast Groups Muter' node doesn't appear in ComfyUI's /object_info

Hello,
The 'Fast Groups Muter' node doesn't appear in ComfyUI's /object_info , so ComfyUIMini or other apps that rely on the ComfyUI API, won't be able to see it.
https://github.com/ImDarkTom/ComfyUIMini/issues/19#issuecomment-2491583767

Many nodes, including the Fast Groups Muter are client-only nodes (aka "Virtual Node" in comfy). There's no object_info because the server doesn't know anything about the node. On the client, the node mutes/unmutes groups when clicked, but isn't sent to the server since there's no work that needs to be done, the groups are already in their correct state.


Job starts without locking resource when using a label and quantity=0

Steps to reproduce

Job 1 is running with a $resource locked
Job 2 is queued with a resource-lock label matching $resource, and quantity set to zero. That means all matching resources need to be locked.
Job 1 finishes, releasing $resource
Job 2 is started when $resource becomes free, but does not actually lock $resource

I noticed it when I had two jobs with the quantity=0 match waiting on a resource. They both were allowed to start, causing many issues.
I found the issue in the plugin code, filing a PR below.

Is it related to #468 ?

Yep, just forgot to put the cross-reference

NP, thanx for contributing


Adds policyInformer to Trigger and Broker controllers

Observed a state where a Trigger can be in an unready state even though the Queue and Policy are both in Ready.
Changes
The trigger controller will now watch for events in policies and enqueue the trigger if it's the owner of the policy.
The broker controller will also watch for policies owned by Brokers
/kind bug
Addresses some of the flakes observed in #588

/hold

/test all

/test ?

This change seems to consistently get passed the Setup phase but there is now a flake that could happen in the Requirement phase. Opened #603 to address it

/hold cancel

I and @gabo1208 looked it at and we have a question. Informers set up handlers to enqueue events, but where is the actual processing is done? Like we see only producing part, where is Policy changes processed.

This repo doesn't reconcile the Policy, that's done by the topology-operator. We do however rely on the Policy's status in order to set the Trigger's status. The handler will trigger a reconcile on the Trigger/Broker when a policy they own is updated.
Any Policy changes will get reflected onto the Trigger/Broker through this codeblock

Per zoom: Informer's handler enqueues event that will be later picked up by controller loop: https://github.com/knative-sandbox/eventing-rabbitmq/blob/56717fb27f1980c4306b9988bc570cd1f919e3a8/vendor/knative.dev/pkg/controller/controller.go#L493.
Which shows us that knative uses its own controller framework and not the one from Operator SDK - https://github.com/kubernetes-sigs/controller-runtime


Fix build with gcc13.1

Hello, solve #2
I have also revisioned your AUR pkgbuild:

pkgbuild: https://github.com/FabioLolix/AURFIX/blob/main/q/qscan/PKGBUILD
diff: https://github.com/FabioLolix/AURFIX/commit/ebe530a1ed87217eb830e89533a77934e155bd09

Thanks. I will also update the AUR package soon, once I have made a new release.

btw please rename sources as in https://github.com/FabioLolix/AURFIX/commit/ebe530a1ed87217eb830e89533a77934e155bd09, having all the archives as $version.tar.gz isn't ideal especially for who is storing all the source in a single folder


Whether dynibar has the ability to render larger time spans in fixed viewing angles？

I noticed that in the girl in green clothes dataset, you render 74 moments from a fixed perspective. I reproduced the experiment and found that the time span in a fixed view was around 70 frames.
I see the quality of the first few frames and the last few frames of the render results is not very good, of course, the further away from the training views, the worse the quality.
I would like to ask you if dynibar has any hyperparameters that can be adjusted to render more moments from fixed vies, how to get more than 74 moments when render in a fixed view of the girl in green dress dataset.
Is dynibar unable to render plenty moments images under fixed viewing angles.

your render results from dynibar project page:
time 0:

time 45:

time 73:

my reproduced results, I choose the the time 51 background as the fixed render view:
time 0:

time 45:

time 74

Hi I think due to limited training supervision signal, current IBRNet can only rendered limited viewpoints and time ranges (meaning in this case, if girl is very further away from original viewpoint or time, the quality would degrade very quickly)

I only found the datasets from the NSFF, and there is no girls_in_green_clothe. Could you please tell me where to find the data?
Thank you !

I only found the datasets from the NSFF, and there is no girls_in_green_clothe. Could you please tell me where to find the data? Thank you !

Sorry for waiting a long time, you can get this dataset from https://zhmeishi.github.io/dvs/


What is "--no-designer-plugin" for when executing configure.py for PyQt4 compiling ?

Hi cyrillef, I noticed that both on your blog and in the build script, there is always this argument
"%MAYA_LOCATION%\bin\mayapy" configure.py -p %QMAKESPEC% LIBDIR_QT="%QTDIR%\lib" INCDIR_QT="%QTDIR%\include\Qt" MOC="%QTDIR%\bin\moc.exe" -w --no-designer-plugin

if I remove it, I'll get the following error message when I do nmake install:
        "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd64\nmake.exe" -f Makefile.Debug install

Microsoft (R) Program Maintenance Utility Version 11.00.50727.1
Copyright (C) Microsoft Corporation.  All rights reserved.

        link /LIBPATH:"x:\lib" /NOLOGO /DYNAMICBASE /NXCOMPAT /DEBUG /DLL /OUT:debug\pyqt4.dll @C:\Users\oglop\AppData\Local\Temp\nm5BE2.tmp
LINK : fatal error LNK1104: cannot open file 'QtScriptd.lib'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd64\link.EXE"' : return code '0x450'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
Stop.

So what is pyqt4 designer plugin ( PyQt4.dll ) for ? Why don't I  need it ?
Thanks!
edit: I found some explanation here , but I'm not quite sure what It meant by

PyQt4 installs a C++ plugin in Designer’s plugin directory. It conforms to the interface defined by
the QDesignerCustomWidgetCollectionInterface class. It searches a configurable set of directories > looking for Python plugins that implement a class sub-classed from
QPyDesignerCustomWidgetPlugin. Each class that is found is instantiated and the instance
created is added to the custom widget collection.

Hi
look at this post and this post, they should explains most of the questions you have about the designer plugin option.
Now your error is due to the fact you're trying to link with the debug version of qtscript (cannot open file 'QtScriptd.lib') vs the release version ('QtScript.lib' i.e. no 'd'). Maya only comes with the 'release' version of QT.
-cyrille

hello !
when I execute the test code, there has a error :
"name 'ok' is not defined !"
please help!

i find the solution ！thanks ！


Setting Text style.color does not work on 1.1.0

| -------------------------------------------------------------------------------------------------

Reporting a bug or issue

Expected behavior:
Setting the color property inside <Text> style should change the color of the text
Observed behavior:
Text color remains #000
How to reproduce:
Run examples/basic-example and the color names and hex should be in black.
This only happens on<EMAIL_ADDRESS>on Sketch@>=50. This is not an issue on Sketch @<=49.
Furthermore, this is not an issue on Sketch@>=50 with<EMAIL_ADDRESS>Sketch version:
50.2
Please attach screenshots, a zip file of your project, and/or a link to your github project
    <Text name="Swatch Name" style={{ color: textColor(hex), fontWeight: 'bold' }}>
      {name}
    </Text>
    <Text name="Swatch Hex" style={{ color: textColor(hex) }}>
      {hex}
    </Text>

@thecalvinchan - I would recommend using 2.x releases as it is unlikely that we will backport changes to 1.x release.

@jaridmargolin gotcha, thanks. how often are changes published on npm/yarn? I'm trying to get the latest patch for symbols, what would be the best way to stay up-to-date with latest changes?

And how do you even install 2.0 via npm, Mentioned in #355

npm install react-sketchapp@2


@conda-forge-admin, please add bot automerge

Additional comment:
@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/mp-api-feedstock#2.


Use gsctl where possible

This PR contains these changes towards making testing on tenant clusters easier:

Replace custom curl calls to GS API with gsctl
Add Dockerfile
Bump the scripts version to 0.6.0
Remove different service urls for chart-museum on kind and giantswarm clusters in create_app_catalog_cr
Add --no-external-kube-api flag for disabling AWS security group updating for running locally against a giantswarm tenant cluster
Remove -a, --auth-token and --giantswarm-api-url flags. Either use GSCTL environment variable configuration or your local ~/.config/gsctl configuration for this

@ubergesundheit is this ready for review and merge or are you still waiting for something else?

This is ready for review. :)


update Baidu voice pic

fixed the invalid link of Baidu Voice Service Pic

perhaps the screenshot of this page is better: http://ai.baidu.com/. on this site, all the services are concentrated here, users can create application with needed services in console conveniently.

Yes, you are right. how about this one ?

pretty good! is i edit directly, or you create a new PR?

I will raise a new PR


AWS BSL should allow empty region

Describe the bug

AWS BSL cannot have empty region. This is not how it should be according to BSL docs for aws plugin
Region can be queried from aws s3 api or not needed through means such as s3Url
To Reproduce
Steps to reproduce the behavior:
Create Velero CR with region empty
Expected behavior
Velero reconcile
Provide the following logs
Got error reconcile condition on velero object.
region for AWS backupstoragelocation config cannot be empty
Version of operator being used

0.3.0

Additional context
Fix by changing the following
https://github.com/openshift/oadp-operator/blob/5a5d4439b0ccbbc200a606cb133b5ad56e8e7e07/controllers/bsl.go#L144-L146

This validation logic should be changed to check if a region is not specified, the user must supply s3Url. If s3Url and region are missing, then it should fail and display the error.

We do not need s3Url as well. Both are optional. The AWS BSL can be created with just specifying the bucket and nothing in the config spec. We need the region for registry deployment though. So more like the region validation for AWS BSL should be modified to be called only for B/R of images velero.Spec.BackupImages == nil || *velero.Spec.BackupImages) . This will be same as the prefix validation I believe https://github.com/openshift/oadp-operator/blob/v0.3.0/controllers/bsl.go#L148


DCR application creation error in analytics dashboard profile.

Description:
The following error occurs in the DCR application creation since the 201 response is not accepted from the External IDP. We may need to accept the 201 response as well other than 200 since it may be the most valid response code as this operation led to a resource creation.
ERROR {org.wso2.analytics.apim.idp.client.ApimIdPClient} - Error occurred while DCR application creation. Error: '{"grant_types":[],"client_secret_expires_at":"0","redirect_uris":[null],"client_secret":"xxxxxxx","client_name":"xxxx","client_id":"xxxx"}'. Status Code: '201'.
Suggested Labels:
APIM 3.1.0-beta
Suggested Assignees:
Affected Product Version:
APIM 3.1.0-beta
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

We assume this was due to providing the external IDPs URLs in auth configs instead of publisher Url. Hence closing.


How to call methods? (Scope/Namespacing?)

Hello again, sorry for another question - say I have something like src/templates/home/index.js:
import<EMAIL_ADDRESS>import './index.css'

const hello = () => {
	alert('Hello!')
}

and want to call the method from the php script at templates/home.php:
Hello

What is the right way to reference this method? (it is undefined in the general scope).

In this case you can either expose your method to the global scope explicitly
window.hello = () => alert('Hello!')

Which kind of defeats the whole purpose of using javascript modules, which is not to pollute the global space. So I would rather register the click event in your javascript file.

hello

// @/index.js
const hello = () => alert('Hello!')
document.querySelector('.hello-button').addEventListener('click', hello)


Fixing typo

This sentence contains the typo :
It also goes againt Flux's unidirectional data flow

Thanks!


APPS-1481 Enable create_asset_focal in the azure:uksouth-ofh region

This seems like it could be the wrong approach...
On Thu, Nov 10, 2022, 5:04 PM Aleksandra Zalcman @.***>
wrote:

Merged #34 https://github.com/dnanexus/dx_app_builder/pull/34 into
master.
—
Reply to this email directly, view it on GitHub
https://github.com/dnanexus/dx_app_builder/pull/34#event-7787936942, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABM36P2XTTNDXDAD4BTL7DWHWERXANCNFSM6AAAAAAR43PR44
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Enable pretty test files.

Test files can now contain # comments and multi-line JSON sections.
Comments cannot be mixed in with JSON structures. Every file must
contain a comment on the first line. This currently does not have a
purpose but may be used later on.

@abrodersen What's the state of this?


Non 200 http code is not catches as exception

Hi !
I have some issue with authorization.
When authorization failed twitter return 401  http code.
This code is not valid HTTP error code.
Then stream is not failed and error returned. Response is ended without any message.
Very hard to find this error and understand what happening.
I add if clause solve this issue. String 200-204 on twitter.js
Thanks

@ozlevka thanks for this.  Do you mind squashing down these commits, then we can get this merged.

You not need all commits.
Enough merge latest 8193010
Then I not need squash...

Yep...
Agree
On Sat, May 14, 2016 at 12:12 AM, Francis Gulotta<EMAIL_ADDRESS>wrote:

I'm going to close this issue due to it's age, I don't think this
particular issue is an issue anymore.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/desmondmorris/node-twitter/pull/69#issuecomment-219160552

--
Best regards
Ozeryansky Lev


linkedAccountKey not returned at getAccountInfo

linkedAccountKey is missing from AccountInfo model class
linkedAccountKey not returned from getAccountInfo and getAccountsInfo from AccountHttp

the issue have been fixed, will proceed to close it


Make global context internal, context is now immutable

Since we already have a way to pass the context to the function without having to call the registry, i think it may be better to put more options / features in the context and remove the static context instance from the registry.
This avoid a lot of potential problems (when one would change directory in one function, then call another function that will not work since it's not the good directory)
Also add method to change context and clone him in the same time
EDIT :
Context is now immutable
Context is back again "global" but only for internal use (to avoid a lot of code repetition in usage)

This fix also https://github.com/jolicode/castor/pull/25, does't?


CCDB GE/015 - Section <IP_ADDRESS>.3

Para 91
Comment:
I cannot find where it is written in the standard that a set of 24 (FCC) or 30 (ECC) test vectors are used.  As a general note: The number of repetitions of some tests seem to be arbitrarily chosen. Where do those numbers come from if they are not to be found in the standard?
Proposal:
Priority: 1

This seems similar to #81
I think this can be covered under the v1.1 update to see about making the number of tests consistent or explaining why the numbers are chosen.

The numbers of tests 24 and 30 are from section section 6.3 of The KAS Validation System (KASVS): https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/keymgmt/KASVS.pdf
To address the comment, The KAS Validation System (KASVS) should be added to paragraph 84 as a reference from which the test requirements are derived.

Similar to #79
Move to v1.1

Closed by #353


desktop multitouch

How can enable multitouch on windows 8.1?
Thanks.

https://github.com/libgdx/libgdx/blob/master/CONTRIBUTING.md


Enable new usage modes for performance testing

At the request of @louiscryan , I've added material to the performance testing protos to support
new modes of communication. All our standardized performance testing so far has been based on ping-pongs, but these protos will enable the testing of 1-sided streaming and 2-sided unconstrained streaming. The code to implement those options is not yet there.
Additionally, this pull request deletes unused random distributions from open-loop and adds support for a core_count_only RPC testing mode at the driver. These changes should not require any changes in any other language implementations since the first part is not ever used, and the second part is driver-only.
Would appreciate eyes from @jtattermusch and @murgatroid99 as well.

I quickly went over the last version of this PR and I am happy with the changes.

Thanks. I'm going to add in an implementation for C++ and Node first so that the world isn't broken and then we can put this in.

@louiscryan I've added additional content to support variant client/server implementations besides those
defined, as well as the chance for a client or server to respond to the driver with a DriverResponse that includes a map for the worker to give additional info back to the server.

LGTM

Ok, this is ready to review. The protos are set according to the changes desired. The C++ workers and driver are now able to use them for the basic rpc types defined previously (unary and streaming-ping-pong). The performance testing scripts (run_performance.sh and qps-sweep.sh) have been adjusted for the new command names. I have attempted to make the Node version work, but am not positive that it does. The other languages package their own protos, so we'll need to update those separately.
Review assigned to @jtattermusch for global view of thins
Input sought from @louiscryan , @murgatroid99 , @kpayson64
TODO: As the languages support ClientStreaming, ServerStreaming, and BidiStreaming, we'll update the scripts accordingly. Similarly with the languages supporting the Capabilities RPC. I'll start on the C++ versions of those later this week.

This PR has entered serious mission creep and the comments are no longer reconcilable. Will instead do this as incremental PRs.


Configurable root suite timeout

This changes the behavior of the timeout configuration parameter to set the root suite timeout for mocha in addition to imposing a timeout on mocha launching.
In a way this constitutes a breaking change, however I think this is what most people would have expected.
My use case for this change is wanting to set a higher timeout when running tests in phantomjs compared to chrome, as I found that some tests that ran quickly in chrome ran significantly slower in phantomjs and were exceeding the default timeout of 2000 ms - without maintaining separate html files for this purpose.

Oh wow I thought I had this option available but your right, it's no where to be found.

however I think this is what most people would have expected.

I agree. However I don't like this the same timeout - they are very different use cases of it.
I'd rather introduce loadTimeout that is the current use of timeout - it really shouldn't be used much. We'll just make this a breaking change and major bump it. If you could make that change to your PR, that'd be great. Thanks!

No problem, done. I've left the change log for you to update when you do the version number.

Perfect yes, I'll manage the changelogs. I feel embarrassed I missed such a basic cofig option. Thanks a lot!


Syntax Error - Indicate Location

Preflight Checklist

[X] I have installed the latest version of Power Query SDK.
[X] I have checked existing resources, including the common issues and the release notes.
[X] I have searched for similar issues.

Problem
When a .pq file has a syntax error, the error that is displayed may not identify which file in the project has the problem.
Example
Notice how below reports a syntax error, but not where it is to be found:
[5:58:24 PM]	[Info]	[Task found] c:\Users\ben\.vscode\extensions\powerquery.vscode-powerquery-sdk-0.2.3-win32-x64\.nuget\Microsoft.PowerQuery.SdkTools.2.114.4\tools\PQTest.exe run-test
				--extension "Some.mez"
				--queryFile "Some.query.pq"
				--prettyPrint
[5:58:26 PM]	[Error]	[Task exited abnormally] pqtest run-test pid(23484) exit(3762504530) stderr:
Unhandled Exception: System.InvalidOperationException: Unable to parse the document
   at PQTest.Common.Utilities.Parse(String mashupDocument)
   at PQTest.Common.Utilities.GetDocumentKind(String code)
   at PQTest.Common.QueryFileAnalyzer.PerformAnalysis()
   at PQTest.Common.Commands.PrepareTests(Configuration configuration)
   at PQTest.Common.Commands.<>c__DisplayClass14_0.<RunTestBattery>b__0()
   at PQTest.Common.Commands.ConfigureMashupEnvironmentAndRun(Configuration configuration, Action action)
   at PQTest.Console.Program.RunTestBatteryCommand(CommandLineApplication app, CommandLineApplication command, Action`1 invoke)
   at Microsoft.Extensions.CommandLineUtils.CommandLineApplication.Execute(String[] args)
   at PQTest.Console.Program.Main(String[] args)

Desired Solution
Indication of which file contains the syntax error and (ideally) the line and column number of its location.
Alternatives and Workarounds
No response
Additional Context
The above example error was from a syntax problem in the .query.pq file.

This should be resolved in the 0.3.1 release (sdktools 2.127.2).
Syntax errors should now be caught and displayed as an error.
The raw output looks like this:
    {
        "ActivityId": "785b203d-6cf3-4ade-af76-f09e6d0d8422",
        "DataSourceAnalysis": [],
        "Details": "Token ',' expected. Start position: (3, 22). End position (3, 38).",
        "EndTime": "2024-03-18T22:05:19.6392845+00:00",
        "Method": "PQTest.RunTest",
        "Name": "test.query.pq",
        "StartTime": "2024-03-18T22:05:19.6228897+00:00",
        "DiagnosticEvents": {},
        "RowCount": 0,
        "Status": "Failed",
        "Type": "PQTest.Expression",
        "Error": {
            "Message": "Token ',' expected. Start position: (3, 22). End position (3, 38)."
        }
    }

Thank you, @mattmasson! Unfortunately, the line numbers reported appear incorrect. Since I don't have permissions to reopen this issue, I'll open a new one.


Optionally bind using credentials passed in by the user

This patch allows you to configure a bind user/pass that contains a "%s" to allow for binding with the username and password passed in. Some LDAP servers are tightly shut so you cannot bind anonymously, and binding with a fixed username/password is frowned upon by a lot of admins. So this patch allows a locked-down LDAP server to be accessed, using the credentials of whoever is trying to log in.
Example usage in local_settings.py:
LDAP_BASE_USER = "uid=%s,ou=People,ou=department,o=company"
LDAP_BASE_PASS = "%s"
(I don't see a direct use case for the %s expansion in LDAP_BASE_PASS, but it didn't hurt to put it in either).
The patch also executes a start_tls, which afaik is good practice and won't hurt.

Closing PR as it is probably obsolete by now.


implement vector view map

interface should look like a generalized version of vector view, as suggested by @bob-carpenter :
template <typename Container, typename View>
class vector_view_map {
};
where user specifies the container type and the view type, and passes in a pointer of type View*. The class implements operator[](int i) and stores a pointer to an array of type View.

@bob-carpenter @syclik what do you guys think about the name "array_view" for these objects? maybe "structured_array_view"? I don't like the "vector_view_map" but I'm not sure what a better name would be.

container_view?
On May 14, 2015, at 9:59 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:

@bob-carpenter @syclik what do you guys think about the name "array_view" for these objects? maybe "structured_array_view"? I don't like the "vector_view_map" but I'm not sure what a better name would be.
—
Reply to this email directly or view it on GitHub.

that's not so bad! better than vector_view_map.

it's growing on me. think it may be the winner. @syclik @bob-carpenter thoughts? Any way to incorporate embiggen or cromulent into the name?

container.embiggen(5);
container.is_cromulent()
I will not approve any code review without these methods somewhere.
On May 14, 2015, at 10:15 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:

it's growing on me. think it may be the winner. @syclik @bob-carpenter thoughts? Any way to incorporate embiggen or cromulent into the name?
—
Reply to this email directly or view it on GitHub.

haha! Thank you. Your input on this issue has been invaluable.

sequence_view or seq_view might be better given
that you're explicitly providing a view that
behaves like a sequence.
But if you're envisioning something more general,
container_view would work.
As a general rule, try to stay away from vague
qualifiers like "structured" or redundant ones
like "object".

Bob

On May 14, 2015, at 5:10 PM, Michael Betancourt<EMAIL_ADDRESS>wrote:
container_view?
On May 14, 2015, at 9:59 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:

@bob-carpenter @syclik what do you guys think about the name "array_view" for these objects? maybe "structured_array_view"? I don't like the "vector_view_map" but I'm not sure what a better name would be.
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

Yeah, agreed, structured is a bad modifier. I'm going to go with container_view, think it's concise and descriptive.

Are you imagining more general containers than sequences?

Bob

On May 15, 2015, at 1:45 PM, Rob Trangucci<EMAIL_ADDRESS>wrote:
Yeah, agreed, structured is a bad modifier. I'm going to go with container_view, think it's concise and descriptive.
—
Reply to this email directly or view it on GitHub.

Hmm, probably not. You'd prefer sequence_view? I could see generalizing to an implementation with operator()(int i, int j) that could return a vector or a matrix, though perhaps that would be better as a separate class.

This issue was moved to stan-dev/math#103


[FEATURE]-Add event to ICommunicationReceiver notifying change in IsConnected

Is your feature request related to a problem? Please describe.
The ICommunicationReceiver interface requires a Connect(), Disconnect() and IsConnected{ get; } implementation.  It would make sense to implement an Event that notifies when IsConnected is updated.
Describe the solution you'd like
public interface ICommunicationReceiver
{
  event EventHandler ConnectedStatusChanged;
}

public event EventHandler ConnectedStatusChanged;

protected virtual void OnConnectedStatusChanged()
{
  var handler = ConnectedStatusChanged;
  if (handler == null) return;

  handler(this, EventArgs.Empty);
}

Describe alternatives you've considered
Currently we cast to a GenericTcpIpClient to monitor the socket change.  Another alternative would be a separate interface with the event on it.

The ISocketStatus interface has a ConnectionChange event on it. I would suggest casting to this interface instead of adding a second event on to the ICommunicationReceiver interface.

OK, well what if the device is not a socket?  Ostensibly if it implements ICommunicationReceiver it has a Connect(), Disconnect(), and IsConnected property which would indicate that is has those statuses?

OK, well what if the device is not a socket? Ostensibly if it implements ICommunicationReceiver it has a Connect(), Disconnect(), and IsConnected property which would indicate that the IsConnected status might change?

That's what the ICommunicationMonitor interface is for.  It attaches to an IBasicCommunication class and monitors for the health of a non-socket (or socket) communication class by regularly sending a poll string and checking for a response.  It also has an IsOnline property and an IsOnlineFeedback property whose OutputChange event can be monitored.
It sounds like that should deliver what you need, no?

Anything that isn't a socket (like a COM port or UDP server) doesn't have a positive feedback mechanism to drive connected status anyway.  We have to monitor the traffic to derive if we have a healthy communication stream.

Got it, so the real problem is that the interface is too broad.  I'd agree we shouldn't pollute it any further.  In my case the ICommunicationMonitor  doesn't really do what I need since there's no poll string involved.  We connect, send the data, make sure we get the response we need, then disconnect.  It's a specialized device/situation though and I can use ISocketStatus to accomplish what's required.


fix!: use absolute path for OCI root

Fixes: #404
BREAKING CHANGE: oci.NewStorage() now returns an error

Codecov Report

Merging #412 (a2d179b) into main (1484139) will increase coverage by 0.03%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##             main     #412      +/-   ##
==========================================
+ Coverage   72.31%   72.34%   +0.03%
==========================================
  Files          46       46
  Lines        4349     4365      +16
==========================================
+ Hits         3145     3158      +13
- Misses        903      904       +1
- Partials      301      303       +2

Impacted Files
Coverage Δ

internal/fs/tarfs/tarfs.go
67.46% <40.00%> (-2.16%)
:arrow_down:

content/oci/oci.go
68.78% <41.66%> (-2.36%)
:arrow_down:

content/oci/storage.go
61.64% <77.77%> (-2.13%)
:arrow_down:

internal/syncutil/merge.go
85.71% <0.00%> (+16.07%)
:arrow_up:

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


feat: support api debug capability and optimize api display interface

Codecov Report
Attention: 265 lines in your changes are missing coverage. Please review.

Comparison is base (5994705) 0.95% compared to head (650b176) 1.18%.

Files
Patch %
Lines

...kotlin/com/alibabacloud/api/service/ProcessMeta.kt
0.00%
236 Missing :warning:

...in/com/alibabacloud/api/service/util/FormatUtil.kt
0.00%
28 Missing :warning:

...alibabacloud/api/service/constants/ApiConstants.kt
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #14      +/-   ##
=========================================
+ Coverage    0.95%   1.18%   +0.23%
=========================================
  Files          20      12       -8
  Lines         842     675     -167
  Branches      125     113      -12
=========================================
  Hits            8       8
+ Misses        833     666     -167
  Partials        1       1

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


update readme

update readme and csv

I think we should wait for the 1.1.0 User Guide to be finished before updating its duplications (e.g. README files)

@27149chen could we delete this branch?


[add-resource] New Plugin

I would like to add my new plugin to the Grav Repository.
Here are the project details: https://github.com/jimblue/grav-plugin-webpacker

Thanks will get this added to GPM shortly.

This has been added.  cheers.

Thanks @rhukster !


After upgrade from Mojave to macOS Catalina, php7.4.12 can't compiled anymore with Xcode 12

Output

There are a lot of Implicit declaration function errors after upgrade to macOS Catalina

Implicit declaration of function 'xxx' is invalid in C99

Can't find icu4c packages, need to use pkg_config to find it.

Expected Result
Compiled without errors
Command
phpbrew --debug install --jobs "$(nproc)" 7.4.12 +default +dbs +dba +apxs2 +ftp +soap +gettext +exif +iconv +intl +bz2 +zlib

Platform
OS:
macOS 10.15.7
Xcode 12
CLT 12

Running PHP:
PHP-7.4.11, compiled in macOS Mojave with Xcode 11
phpbrew 1.26.0

Installing PHP:
PHP-7.4.12

Solutions

Use export CFLAGS='-Wno-implicit-function-declaration' to avoid Implicit declaration function errors. Maybe we can patch configure  file for this option.

Use export PKG_CONFIG_PATH="/usr/local/opt/icu4c/lib/pkgconfig" to avoid icu4c errors. I may write a PR for this when I am available.

Or downgrade to Xcode 11 and CLT 11 to avoid above two issues.

References
https://github.com/phpbrew/phpbrew/issues/1194
https://github.com/phpbrew/phpbrew/issues/1199

After check the master branch, I think icu4c issue already fixed, we need to backport to 2.0 branch.

These two issues seems fixed in 1.27.0, i'll close this.


Sync Virtual Machine network names

Our VMs are connected to Networks with a clear defined naming convention that lets us get a lot of Information about the Network just by the name. Sadly those Names are not synced to Netbox and the interfaces are just named generic vNIC0, vNIC1, ...
Describe the solution you'd like
If the network name is available sync it to Netbox if not use the generic vNICx.
Describe alternatives you've considered
Maybe some people don't want the network names to be synced, so an optional setting could be created for that.
Additional context
The change would be really simple, only one line in run.py would have to change from nic_name = "vNIC{}".format(index) to nic_name = getattr(nic, "network", "vNIC{}".format(index))

I don't know what the Netbox api character limit ist but the name should probably also be truncated

Hello, @Haeki.
Thanks for the suggestion. This seems like a reasonable ask. Let me do some further testing and I'll work on getting this patched in.

I found and fixed a little Problem with this myself. Our network names contain plus signs so when rerunning the sync they don't get found in Netbox and are created again,
Luckily this is a very easy fix. When creating the query for virtual_interfaces qute_plus() should be used on vc_data[query_key]:
query = "?virtual_machine={}&{}={}".format(quote_plus(vc_data["virtual_machine"]["name"]), query_key,quote_plus(vc_data[query_key]))

Hi @Haeki! If you'd like to submit a pull request I would be happy to credit you with the contribution. Otherwise I am happy to patch this in. Thanks!

Also looked into it. For some strange reason you only get the network name from the guest tools. but the API should report the network names even without Guest tools installed.

I went down a rabbit hole and finally can see the light at the end of the tunnel again. This took way longer then expected (as usual).
Here you go: https://github.com/bb-Ricardo/netbox-sync
please test as much as you can: Debug logs are very welcome.


Query running on both client and server.

I'm a little confused with what's going on here, but my GraphQL query is being run twice - once on server and once on the client; even though I'm following the example. The prepared data is being correctly serialized out to the rendered page and then deserialized for use with injectPreparedData, but the client still makes the query. My understanding is that because all the query data should be in the cache, the client doesn't need to run a query of its own.

It works in my project, so I can't tell what is wrong in your case not seeing your code, or at least instructions of how to reproduce that.

My client-side code path looks identical to yours, but for some reason injectPreparedData doesn't actually add any records to the store data. I'm trying to find if there's any fundamental structural differences between our serialized payloads, but they look very similar.
Basically, in your example, I've dropped into debugger immediately after injectPreparedData and run environment.getStoreData() , and the _records field is fully populated. In my code, doing the same gives me an empty records object. The only difference I can see is that we have different queries and data, but structurally the deserialized objects looks the same.
This is really bizarre :/

It is strange indeed. Do you produce data on the server using isomorphic-relay or by some custom method? Do you use the same version of Relay on the server and in the browser?

I think I found the issue, but not the ultimate cause.
I'm using the same versions of Relay on client and server (0.9.2), but on the client i'm using a CDN build (https://cdnjs.cloudflare.com/ajax/libs/react-relay/0.9.2/relay.js) and webpack to set it as an external, and on the server i'm using the npm module.

I've forked and modified your example to reproduce the issue for you: https://github.com/AndrewIngram/isomorphic-relay/tree/demo-broken-cache-prime

But how did you build isomorphic-relay? It imports some internal Relay modules. You probably have two copies of Relay in the browser (one from CDN and one built into your app bundle).

I've forked and modified your example to reproduce the issue for you

Yes, you definitely have two copies of react-relay.

Hm, well that's no fun at all. I guess the only plausible solution is to somehow externalise all of isomorphic-relay's explicit imports, or just stick with the npm module instead.

I believe the CDN version of Relay does not export internal modules, so we have to stick with the NPM version for now.

@AndrewIngram is it possible that this is happening because relay automatically adds a timestamp to connections?
    _projectsjoTE5:projects(after:"2016-09-07T01:59:21+02:00",first:99) {
    ....
    }


R0.9: Fixes URLs and headings

Points links to wide_and_deep.py to master, fixes a heading, and changes a versioned URL to a generic URL.

Can one of the admins verify this patch?

Trying to trigger a cla recheck.

Jenkins, test this please!

failure unrelated


Scanner finds comment in template string with placeholder

When using the scanner to find comments in typescript code a comment is detected inside of a template string that contains a placeholder. Remove the placeholder or changeing the template string to single/double quoted string fixes the issue. The scanner is user in the typescript-eslint-parser and was reported in this issue:
https://github.com/eslint/typescript-eslint-parser/issues/216
TypeScript Version:  2.2.1 / nightly (2.2.0-dev.201xxxxx)
Version 2.3.0-dev.20170318
Code
const ts = require("typescript");

var code = 'const a = `${folder}/**/*.ts`;';
var triviaScanner = ts.createScanner(ts.ScriptTarget.Latest, false, 0, code);

var kind = triviaScanner.scan();
while (kind !== ts.SyntaxKind.EndOfFileToken) {
    if (kind !== ts.SyntaxKind.SingleLineCommentTrivia && kind !== ts.SyntaxKind.MultiLineCommentTrivia) {
        kind = triviaScanner.scan();
        continue;
    }

    var range = {
        pos: triviaScanner.getTokenPos(),
        end: triviaScanner.getTextPos(),
        kind: triviaScanner.getToken()
    };

    var comment = code.substring(range.pos, range.end);
    console.log(comment);
    console.log(range);

    kind = triviaScanner.scan();
}

Expected behavior:
No comments found.
Actual behavior:
Finds comment in template string.
Output of script:
/**/
{ pos: 20, end: 24, kind: 3 }

Sorry guys. Looks like there is no issue here. After reading the code I see there is a reScanTemplateToken() that will correctly scan template strings.


Added a simple calculator to GUI

Added a simple calculator build using the Tkinter module.

good job 👍🏼 :


Don't ignore the "Done" message of dein#check_update() even if there are no updated plugins

Hi. Thanks for developing dein.vim. No dein.vim, no my Vim life.
I have an issue that the "Done" message, e.g., "Done: (2023/01/02 03:04:05)", of dein#check_update() is ignored if there are no updated plugins. This issue is caused as follows:

dein#check_update() calls dein#install#_check_update() internally
dein#install#_check_update() calls dein#install#_get_updated_plugins() and checks if there are updated plugins
If there are no updated plugins, dein.vim calls s:notify() for sending the "Done" message and finishes its update process
Because the variable context is empty, s:notify() does nothing and the "Done" message is ignored

The context is derived from s:global_context, that is empty because dein#install#_get_updated_plugins() makes it empty

This pull request fixes the issue. Even if context is empty, s:notify() will call s:updates_log() and assign s:progress. Then only if context isn't empty, s:notify() will check context.message_type and call dein#util#_notify().

Thank you.  Merged.

Thank you!


chore(deps): update ci dependencies

Description

Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

The changes are update in place.

/run pipeline

@Aashiq-J Why are we ignoring this now?? The consistency check is to ensure the module is idempotent, and if it fails we need to know why, and not just ignore it

@ocofaigh ,This is similar to this provider bug,
created a new provider issue for this.
This error is causing all PR and continuous pipelines to fail for this module.

/run pipeline

@Aashiq-J @ocofaigh I think we are going to have to add these ignores this way, at least until the provider fixes this idempotent issue. When looking at testwrapper, it only supports identification of updates (and ignoring those updates) at the resource level, not the attribute level.

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


i18n(es): add core-concepts/partial-hydration

What kind of changes does this PR include?

[ ] Minor content fixes (broken links, typos, etc.)
[ ] New or updated content
[x] Translated content
[ ] Changes to the docs site code
[ ] Something else!

Description
Adds core-concepts/partial-hydration page in Spanish.

LGTM!


bug: switchNetwork exposes infura/alchemy API keys when adding a new network

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.10.10
Current Behavior
When using switchNetwork and the user doesn't have the network created, instead of adding the network with a public RPC, it uses the RPC with the API. This is highly undesirable, as not only it exposes our private API key, but also stores it on the user chain even for actions unrelated to our website.
With Polygon network not created, and providers created with API keys (Infura or Alchemy), something as easy as this:
const network = await switchNetwork({
chainId: 137,
})
Tries to add the new network but with the internal RPC with our API key instead of the public RPC.
Expected Behavior
Create the network with the public RPCs.
Steps To Reproduce
With Polygon network not created, and providers created with API keys (Infura or Alchemy), use this code:
const network = await switchNetwork({
chainId: 137,
})

In case anyone is interested in picking this up, seems like you just need to remove the code overriding Chain.rpcUrls.default for the following providers: infuraProvider, alchemyProvider, and jsonRpcProvider.

In case anyone is interested in picking this up, seems like you just need to remove the code overriding Chain.rpcUrls.default for the following providers: infuraProvider, alchemyProvider, and jsonRpcProvider.

Pull request created.


Display the 5-star ratings on the Skill Detail page

Actual Behaviour
Currently, thumbs-up and thumbs-down rating is shown.
Expected Behaviour
It should display it according to images below -

Steps to reproduce it

[x] Implement UI of 5-star Rating in Skill Detail Screen [PR #310]
[ ] Get and Display 5-star rating from getSkillRatings.json API
[ ] Submit 5-star rating on Skill Detail page from fiveStarRatings.json API

Screenshots of the issue
N/A
Would you like to work on the issue?
Yes

Part-2 and Part-3 of this issue need to be done. Opening again


Update graphql dependency in gql-format and gql-merge.

The specified graphql version in gql-merge and gql-format currently prevents me from upgrading my graphql version, as multiple versions of graphql in node_modules has some issues due to instanceof checks.
I checked the changelog of graphql and it looks like this library shouldn't be affected by breaking changes there.
I tried running your tests, but after lerna bootstrap I got an error: Error: Cannot find module 'gql-utils'. I'm not sure where that issue originates from.
Also flow finds some errors both in the graphql package as well as in your lib code. I added node_modules to your ignored flow files to get rid of the former ones, but I'm not sure where the others are coming from.
Also the lint task returns a bunch of errors – I don't think they are related to the upgrade of graphql, are they?

Another option would be to remove graphql from dependencies and move them to peerDependencies. WDYT?

IMHO, graphql should definitely be declared as "peerDependency". Having it fixed as an internal dependency can only bring problems down the build pipe line for users.


Screen cheese when expanding collapsing notebook cells

Does this issue occur when all extensions are disabled?: N/A

Version: 1.63.0-insider (user setup)
Commit: 827f76521d33a61c19e92160649a0a6af8bad132
Date: 2021-11-30T11:58:52.241Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000
Steps to Reproduce:

Create two cells, one markdown & one code cell
Use the commands to toggle collapse state of the input cells

See recording

This is caused by moving collapse state out of metadata.

Verified in Code-OSS running out of sources


Video Recording

Builds on the work #29 and #23 to use AVCaptureScreenInput to record a video of multiple Simulators at once, to separate files.

[ ] Figure out why Error Domain=AVFoundationErrorDomain Code=-11809 "Recording Stopped" happens when the Simulator boots.

The error code for 11809 is AVErrorMediaChanged, so the Simulator.app must be doing something that caused AVFoundation to suspend/cancel, recording.
Recording is fine if it starts after the Simulator has booted to Springboard. In a single-sim environment this would be fine, but when booting two or more simulators at once, a booted Simulator will cancel recording for all Simulators at once. It should be possible to resume to the video, but this seems pretty terrible too as there will be gaps in the video.

This looks to be a change in the Xcode 7 Simulator.app. Running an iOS 8 Simulator on Xcode 6.4 doesn't exhibit the AVErrorMediaChanged behavior. I guess this makes some sense, given that Simulator booting appears to be a bit different; there are progress bars before springboard is visible.

The termination of the AVCaptureMovieFileOutput looks to be caused by a change in the AVCaptureScreenInput's Pixel format. Before the Simulator has finished booting it is apparently '0000'. When the Simulator boots a AVCaptureInputPortFormatDescriptionDidChangeNotification will fire and the Session re-starts. The re-starting session will cause the output to file to finish.
It would be really awesome if we could just use AVCaptureMovieFileOutput rather than having to resort to AVCaptureVideoDataOutput. I'm not entirely sure how this can be done, since it doesn't look like the pixel format can be changed for AVCaptureMovieFileOutput.

There's a reasonable and non-terrible solution that involves deferring the start of the AVCaptureMovieFileOutput until after the AVCaptureSessionDidStartRunningNotification has started, which co-incides with the start of the Simulator. When a Capture Session has started, it will not be interrupted by other Simulators starting, so it will be fine in a multisim environment.

Merging this now. Will look at a longer-term solution for the tests-on-travis later.


[Notifications/Analytics] Launch app in background when received

We need to know what notifications are actually being delivered, so include the content-available flag.

Close in favour of #1119.


Added agent-specific public and private goals, updated problem_kind.py

Codecov Report
Patch coverage: 47.05% and project coverage change: -0.08% :warning:

Comparison is base (190baf7) 85.20% compared to head (acfba34) 85.12%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #465      +/-   ##
==========================================
- Coverage   85.20%   85.12%   -0.08%
==========================================
  Files         198      198
  Lines       25887    25938      +51
==========================================
+ Hits        22056    22080      +24
- Misses       3831     3858      +27

Files Changed
Coverage Δ

unified_planning/model/multi_agent/agent.py
49.60% <36.84%> (-5.58%)
:arrow_down:

unified_planning/model/multi_agent/ma_problem.py
57.93% <72.72%> (+0.62%)
:arrow_up:

unified_planning/model/problem_kind.py
96.35% <100.00%> (+0.05%)
:arrow_up:

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

@Alee08 You also need to update the documentation describing the new problem kind features. Update this table.

@Alee08 You also need to update the documentation describing the new problem kind features. Update this table.

Done, let me know if it's okay!


Fizzler (1.1.0) warning when installing svg.core nuget on .net standard 2.0 project

@ChristinaFaur
Please use Svg.
@mrbean-bremen
What is Svg.Core ??

What is Svg.Core ?? (#595 ?)

Never saw that - seems to be a copy of SVG. Looks like you are right regarding that PR - most certainly taken from here, which is an older release with the PR added.
A bit unfortunate regarding the naming - this was actually a name we have been considering for the moved repo (or does it already exist?). For some reason he decided to register an own NuGet instead of answering the questions in the PR...
Also completely misleading, as he did not add any additional description, so it looks like SVG.

Closing as not related to this project.


Prepare for auto-powered releases

I followed the instructions for a project that is already released: https://intuit.github.io/auto/docs/welcome/getting-started#make-latest-release
Now, it appears to be configured correctly.
./auto info

Environment Information:

"auto" version: v11.1.5
"git"  version: v2.45.0
"node" version: v16.16.0

Project Information:

✔ Repository:      con/duct
✔ Author Name:     Austin Macdonald
✔ Author Email<EMAIL_ADDRESS>✔ Current Version: v0.0.1
✔ Latest Release:  v0.0.1

✔ Labels configured on GitHub project

GitHub Token Information:

✔ Token:            [Token starting with ghp_]
✔ Repo Permission:  admin
✔ User:             asmacdo
✔ API:
✔ Enabled Scopes:   repo, write:packages
✔ Rate Limit:       2862/5000

I've also run auto shipit --dry-run and that looks good. I suppose we merge this, then I'll mark https://github.com/con/duct/pull/110/ as a "minor" update. (Its actually a breaking change, but I don't want auto to go to 1.0.0). When that merges, hopefully we see the magic!

@asmacdo

I see you're using the default auto label names of "major", "minor", and "patch".  If you ever enable Dependabot in this repository, this will lead to problems, so you may want to rename the labels to something like "semver-major", "semver-minor", and "semver-patch".  See https://github.com/datalad/datalad-installer/issues/175 for more information.
release.yml is currently configured to only run on workflow dispatch, i.e., manually, rather than when a PR is merged.  Is that intentional?
.autorc currently sets onlyPublishWithReleaseLabel to true, so releases require a PR to be marked with "release", and the "skip-release" label is unnecessary.  Is that intentional?

ty @jwodder

release.yml is currently configured to only run on workflow dispatch, i.e., manually, rather than when a PR is merged. Is that intentional?

No that was not intentional, good catch.

.autorc currently sets onlyPublishWithReleaseLabel to true, so releases require a PR to be marked with "release", and the "skip-release" label is unnecessary. Is that intentional?

I prefer explicitly ask for a release, I've deleted the skip-release label
I've updated the auto labels to use the semver prefix and https://github.com/con/duct/labels to match


Depth should be 6n+8 instead 6n+2 in CIFAR-10?

Hi, thanks for this nice code!
In my understanding, it seems that you didn't count downsampling blocks as depth 2 layers?

Sorry, I didn't see the "1" in "range(1, blocks)", never mind!


Add new tomtom geocoder

Related to https://github.com/CartoDB/carto.js/issues/2213
Objectives:

[x] Add new tomtom geocoder provider
[x] Connect it as default to the 'search bar'
[x] (optional...) improve the provider selection, to change more easily in the future (hopefully).

This process is very similar to what we did in: https://github.com/CartoDB/carto.js/pull/2020

Instead of removing the previous geocoder provider, the new tomtom is selected by default for the Search.
But, in the future, the Search could receive another service as parameter with geocoderService (if properly configured, currently just 'mapbox' or 'tomtom' are valid):
var search = new Search({
      model: this.map,
      mapView: this.mapView,
      geocoderService: 'mapbox', // <<<
      token: 'a_valid_mapbox_api_key'
    });

That parameter could be controlled by cartodb backend in the future


? couldn't convert the error to CustomError

my compiler gives me this message
`?` couldn't convert the error to `SyntheticError`
the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
the following implementations were found:
  <SyntheticError as From<std::io::Error>>
required because of the requirements on the impl of `FromResidual<Result<Infallible, JoinError>>` for `Result<(), SyntheticError>`rustcE0277
try_trait.rs(339, 5): required by `from_residual`

Here is my rust code.
  async fn handle(mut connection: Connection) -> Result<(), SyntheticError> {
    let result = tokio::spawn(async move {
      connection.send_server_greeting().await?;
      connection.send_setup_response().await?;

      let mut framed = SyntheticFrameCodec::new().framed(connection.stream);
      while let Some(message) = framed.next().await {
        match message {
          Ok(bytes) => println!("bytes: {:?}", bytes),
          Err(err) => return Err(SyntheticError::from(err)),
        }
      }
      Ok(())
    });
    result.await?
  }

and below is my implementation.
#[derive(Debug, Error)]
pub enum SyntheticError {
  /// An error when the port is unavilable
  #[error("Port already in use: {port:?}")]
  PortUnavailable {
    /// The port that is unavailable
    port: String,
  },

  /// Error while trying to convert bytes to frame
  #[error("Invalid or empty frame")]
  IllegalFrame,

  /// To catch all unwanted errors, this is the default error
  ///
  /// > If we get this, the system has behaved in a way that we don't expect
  #[error(transparent)]
  IOError(#[from] std::io::Error),
}

My bad, not related to this crate.


Bundle lib%sBridge.so and libqxcb.so in the updatedeployqt AppImage

Please bundle all versions of lib%sBridge.so and libqxcb.so in the updatedeployqt AppImage rather than downloading them at runtime. Some build systems (e.g., https://build.opensuse.org/) do not allow accessing the internet at AppImage build time. So the current solution would not work there at all.

This was a good decision, The binary size is now only 600 KiB(appox.), libcurl was really heavy. Anyways now updatedeployqt does not require network on runtime.


:new_methods_only option

Default to true
Affect advices using regular expressions

This brings up some interesting things:
When a new_methods_only advice for /*/ is defined, it'll not be applied to an existing method. When another advice is defined for :test, the first advice will be included in the generated method. The logic of whether the first advice is included is decided by another unrelated advice. This does not sound right.


allow postfix "mynetworks" editing

Hi,
Thanks for the easy postfix installation.
Is there an easy way to extend the "mynetworks" postfix config please?
For example I'd like to allow several local subnets.. or even (<IP_ADDRESS>/8).
Regards,
Andrea

Not, currently it's autodetected in the entrypoint: https://github.com/Tecnativa/docker-postfix-relay/blob/0d869f935e85b5de08d70fb19996219e6b8de9c6/entrypoint#L33-L37
PRs welcome :wink:, closing for now.

PR submitted


Upgrade undici to v5.8.0

Hi! Upgraded undici to v5.8.0. This release fixed the vulnerabilities.
https://github.com/nodejs/undici/releases/tag/v5.8.0

This undici updating has breaking changes. We can't adapt as it is.
But, I think we should fix the vulnerabilities. Hmm...

Hi @mrbbot ! Thank you for checking this PR.

Will check we can bump the minimum supported Node version (in Wrangler too)

Please!

but these security issues are unlikely to affect Miniflare users, as it's only intended as a local development and testing tool.

Ah, you're definitely right!


replace === with R.eq in equality functions

i think this will go a long way to ensuring consistent behavior.

... and :cow2:

:herb:


'-append' don't work in my vim/neovim?

It seemed that the function s:run in line 847 should make some change:
  if !a:flags.append
    if a:flags.quickfix
      call setqflist([])
    else
      call setloclist(0, [])
    endif
  endif

Oh. Wow. Apparently that was broken for a very long time... thanks for pointing this out! ✨


Fix incorrect variable name logging checkpoint_period parsing problem

note that this changes behaviour when there's a parsing problem: previously this threw an exception (due to the error being fixed) but now a log message is logged and execution continues.
I think I prefer the exception-throwing behaviour.


permit2

current implementation of permits has some drawbacks:

you can have only one permit in mempool at the time
there is no function on RPC to give you the latest nonce based on mempool like for regular transactions
it is hard to index permits as you don't know the sequence as there is no nonce in arguments
dispatch permits are sometimes randomly deleted from mempool on nodes because of nonce validation, because node is not synced to the latest nonce yet
permit cannot be replaced with another one

therefore we should add nonce as an additional param when submitting permit and validate the permit against that nonce (not the one in state), the permit will be then dispatched with the same nonce as a priority allowing you to have multiple permits in the pool at the same time

this should resolve points 1. - 4.

should be resolved by allowing you to replace the permit with a newer one by specifying a bigger tip, therefore granting it more priority as well - same behavior as for normal transactions

note: changes should be backward compatible with original moonbeam-derived interface - we will be still able to process old permits with same limitations as before

related to #846 #845 #814


oud_export.sh can not handle multiple backends

The current ´´oud_export.sh´´ can not handle multiple backends. Currently is just exports the default / UserRoot backend.

add new feature to collect backend information. By default oud_export.sh will export all backends with a base DN except the internal backends. Internal backends are the following:

cn=monitor
cn=backups
cn=ads-truststore
cn=admin data
cn=virtual acis
cn=tasks

So by default oud_export.sh will backup all other backends.
There is also a new parameter -b. This parameter explicitly allows to specify a backend to backup.
Usage, oud_export.sh [-hv -i <OUD_INSTANCES> -b <BACKENDS> -m <MAILADDRESSES>]
    -h                 Usage (this message
    -v                 enable verbose mode
    -i <OUD_INSTANCES> List of OUD instances (comma separated)
    -b <BACKENDS>      List of OUD instances default all (semi-comma seperated)
    -m <MAILADDRESSES> List of Mail Addresses (comma separated)
    -o                 force to send mails. Requires -m <MAILADDRESSES>
    -c                 Compress LDIF file (default no compression)
    -k <DAYS>          Number of days to keep old exports (default 7)
    -D <BINDDN>        Bind DN used for the export (default: cn=Directory Manager)
    -j <PWDFILE>       Password file used for the export (default: $PWD_FILE)
    -f <EXPORTPATH>    Directory used to store the exports (default: $OUD_EXPORT_DIR)
Logfile : /u01/log/oud_export.log

Dedicated backends can be exported by specifying -b although the backends have to be correctly escaped and separated by a semicolone e.g. -b "OracleContext0;monitor"


connection sync failure

Hi, I am new to postman and I have been seeing some issues like :-

my postman collection is not syncing. (It was few months ago)
A week ago some of my requests went blank
app was not updating to the latest version
I tried re-installing the app and now its showing as connecting on the right most corner, coz of which my workspace is not downloading (NOTE - I do see my collection online)

Appreciate all the help!!!

sorry but I think you are in the wrong repo :)


pad_calc fix: size_t -> std::size_t

Bug carried over from older code.

With some changes made to ROCm stack for GCC compiler, QA found that the compiler produces an unknown type name "size_t" error.


PeakChain Moveup

What changed? Why?
We have implemented the necessary changes to request the addition of our project "PeakChain MoveUp" to the Base Ecosystem.
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/2

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
1

Sum
2

@WalidGueddari
Hi there! Apologies, we recently updated the way we categorize and subcategorize apps; could you please rebase + update your PR, conforming to the new format by removing the tag, and defining the category and subcategory?
We'll do our best to review as soon as possible once you do! 🙏

We've rebased our branch and updated the pull request to conform to the new categorization format. Please review when you have a chance!

@WalidGueddari Thank you for the update. This needs to be rebased again.

@WalidGueddari
Could you also please update the language on the homepage to say "Powered by Base" instead of "Powered by Base.org"?
Lastly, could you please confirm what parts of the platform are onchain on Base and how users transact on Base using PeakChain?


[Deposit] Improve data handling for balances

Currently we load all balances for deposit (which might take some time). Use cached balances (done by #1188) and improve reloadBalances by loading balances for selected assets only.
https://user-images.githubusercontent.com/61792675/112472704-bbfffe80-8d6d-11eb-882f-20936ddb29e3.mp4

resolved at #1262