Long Term Support schedule

With the release of v3, I want to make it very clear to anyone interested in using WebEngine of how its support is to be planned, specifically relating to the versions of PHP supported.
I want to keep PHP.Gt stable, but not so much so that it can't adopt newer PHP versions, etc.
One policy should be to freeze the latest stable PHP version at the point of major version release, so until the next major version release, no new PHP versions are adopted within the releases.
At some fixed amount of time after the first stable release, master will move to whatever is now the latest stable PHP release. New features will be implemented on master and only security and bug fixes will be backported to the Gt release on their own release branch.

Solution:
It will be too much effort to maintain backported versions of PHP.Gt repositories. Only one branch should be maintained per repo, with regular releases following semantic versioning.
In relation to what PHP version requirements are specified per repo, this should follow the largest Linux distribution's decision on what PHP version to consider safe and stable: Debian.
Debian is known for being a little out of date and not cutting edge - this is exactly what PHP.Gt needs to be. Stability over cutting edge features.
When any PHP.Gt repository is made into a new, major, stable release, whatever version of PHP the latest version of Debian ships with should be used as the PHP requirement.
For example, the newly released Debian "Buster" v10 ships with PHP 7.3 so the next PHP.Gt stable release while Buster is considered "Debian stable" will require PHP 7.3 in composer.json.
Some more thought needs to go into the LTS plan - a guaranteed amount of time that a PHP requirement will be kept - but the release schedule of Debian is nice and slow so should help with predictability.

https://wiki.debian.org/DebianReleases


add scoop as installation method

add scoop as installation method on website and on readme.md
https://github.com/lukesampson/scoop-extras/blob/master/bucket/screentogif.json
Scoop is a command-line installer for Windows

+1 to idea, but...
besides placing website/readme.md, this method needs more testing because there is a little issue with installing of (and I'll describe it here as the title best fit):
ScreenToGif doesn't seem to save user configuration between its launching.
Scoop makes two things:

symlinks ~\scoop\apps\screentogif\current to actual app version folder (as of writing 2.36), that's OK;
particular file ~\scoop\apps\screentogif\current\Settings.xaml is hardlinked to ~\scoop\persist\screentogif\Settings.xaml that is a culprit!
Breaking this hardlink (specifically: replacing with symlink to persistent dir) restores saving of settings.

I am writing a parallel issue on extras bucket github repo issues. Here for anybody wanting to instant solution.

I'm not able to reproduce the above issue. My settings are saved as they should. Also, in both the the cases, the link is a hardlink. Scoop does not create symlinks.

OK. In my case, two discrete machines have the same behavior.
I've just made another test and have a suspicion:
After standard installation by scoop, the file Settings.xaml has 0 bytes (empty, of course).
But when this file is not existing, ScreenToGif creates one on first launch with such content:
<ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"></ResourceDictionary>
So existing an empty file (with no structure) prevents from making new default file.

Is the default settings file available somewhere in this repo? We can use it instead of creating a new (blank) settings file.

Nope, installation scoop just downloads portable edition of app, then extracts it and creates it's file structure (links files and folders in few places).
I'm a newbie in scoop configs, but maybe there is possibility to fill up file with correct/required content, right after creation.

You asked if there is a file, but I'm saying there is no such file. So I came up with ScreenToGif ability to fill an empty file with correct structure:

I'm not sure I follow, how will you ask Screentogif to create the file while it's installing?

OK, so the simplest way of my understanding...
Two alternative solutions I'm imaging:

scoop installs S2G by placing correctly .exe file and making an empty .xaml file in appropriate directories. When done, scoop injects to file such string <ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"></ResourceDictionary>
scoop installs S2G by placing correctly .exe file, next launches S2G, kills it and finishes installation with hardlinking to persistent dir.

The first method sounds elegant. Can you make a PR for it?


Button to reroll letter locations

It's a rather common feature in games like these to have a button that moves the letters around. I assume this is to allow our very pattern-focused brains to have new entry points, leading to finding new words. Maybe a worthwhile inclusion? :)

Yea, nice suggestion, thank you.


Refactor path template to match other languages

Particularly, use go's yacc to generate the parser.

I think yacc is overkill. A simple recursive descent parser should be enough. Let me take a crack at it.

Yeah sure, I think it should be relatively easy, as it's a small grammar.
For reference, the parser implementation in Python:
https://github.com/googleapis/gax-python/blob/master/google/gax/path_template.py#L162


about kitti train

Can I get the convert_datasets  code about kitti to complete the training and evaluation?

Sorry that we do not have plans to support kitti. Recommend to use the large-scale BDD100K benchmark. : )


Sluggable with embeddable

if it supports only php 7, that cannot be accepted. try to find the reasons why this property is not available in older versions

@l3pp4rd  it's weird that for some reason the error isn't on PHP7.0! Maybe that one doesn't have mongoDB? I should have fixed it right now for PHP5

I'd love to see this PR merged.

Hello, and thank you for your contribution.
In the interest of spring cleaning and package modernization, I'm going through and closing old issues and pull requests that have had no recent activity, do not have associated tests, or have failing tests.
If you are still experiencing this issue or wish to contribute an up-to-date pull request, please create a new issue.
Thank you!


Basin stops processing after single process

Describe the Bug
Happens in versions after this commit :
https://github.com/Fabricators-of-Create/Create/commit/456d604a06fbe0b5cc0c9c47d490099397877e81#diff-1431545e5918c84f5cf60dff82206a2ecc9b96861ef2faf0049d3f27024dd134

Reproduction Steps

Create andesite mixing, then sending to other basin setup as attached above.
Input cobblestone and diorite in upper basin, in any form.
Process then watch.

Expected Result
Processing should not stop.
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
Windows 11
Mod Version
0.5.0i
Minecraft Version
1.19.2
Other Mods
No response
Additional Context
If basin is broken (below), then basin can process again, but its inconsistent.
I suspect its something related to recipe caching invalidation problem.

When a basin has a spoutput, it will only process when it can output. Since basins can only hold 16 of an item, it stops quickly. This is the same as on forge.
In my testing, this behavior is working fine. If you still think there is an issue, please elaborate. A video may help.


Support pragma foreign_keys in batch()

Applications should use the defer_foreign_keys which works within a transaction instead so closing this as obsolete.


Rust and WebAssembly Working Group Meeting #44

Our next meeting will be Thursday, May 21st at 17:00 UTC.
Add agenda items here: https://paper.dropbox.com/doc/RustWebAssembly-WG-dcXi5F7Bqlvg10zd7dKve
As usual, we'll be holding open office hours, so if you have any questions about Rust and WebAssembly, feel free to add a bullet point to the agenda!
We use Zoom for video meetings, so make sure you've downloaded the client! (It's free, but you have to sign up.) Here is our meeting room: https://zoom.us/j/715879536
Anyone interested in Rust and WebAssembly is invited to join! Yes, that includes you!

Thursday, May 21st at 17:00 UTC.

I'm sorry, I didn't receive my official Rust Time Machine yet, where can I apply for that?


Profile Extensions, Take 3: Extension Rules

Hey all!
Here is an updated PR for profile extensions. I’d really like to get this merged soon, or else get a concrete list of blockers if it’s not mergeable as is. We’ve been sitting on this for two years, and the design has gone through quite a lot of vetting and revision, so I think it’s time. Besides, 1.1 is still a draft, so we can still change things if this design proves unworkable.
History
For anyone reviewing this PR who hasn’t followed (or has forgotten) the prior discussions around JSON:API extensions, here are some links describing, broadly, why this proposal works the way it does:

Issue #614 (starting here) lays out the broad design goals for JSON:API extensions and groups possible extensions into two different types. Specifically, it separates out “profile extensions”—which are limited in what they can do, in order to simplify processing, maximize interoperability, and compose seamlessly—from more powerful “comprehensive extensions”.

Issue #650 contains my first stab at specifying the extension system. This design tried to cover both profile extensions and comprehensive extensions, as well as an extension advertising/discovery mechanism.

After #650 proved to be too big to consider all at once, I decided to focus on profile extensions first, and I put forward a refined design for them in #915. The first post in #915 offers some background on why I chose to focus on profile extensions and also why I think extensions are so important generally. That post also offers some additional design goals unique to profile extensions.

The discussion in #915 was wide-ranging. It covered what restrictions should go on profile extensions, whether and how they should be registered, whether and how they should be versioned, and how extension-added data should be distinguished from data that might be defined by future versions of the base specification. We explored many different possibilities and considered models developed by, and lessons learned from, other standards efforts. I was particularly influenced by a W3C TAG–recommended model of compatibility (defined in detail here), which undergirds the approach to extension versioning used in this PR (namely, extensions are unversioned and must change in fully-compatible ways over time).

Finally, #957 attempted to put the conclusions of #915 into specification-ready text. This text was reviewed at an editors meeting and tweaked—most notably, to require that extension-defined data live under the meta object. This PR is based on #957.

New Changes
For easier review, this PR rebases the latest version of #957, and some changes from #957 have been split off into a separate PR. In particular, this PR defines profile extensions, while #1196 outlines the (optional but encouraged) registration process. Beyond splitting up #957, this latest revision contains some small changes:

I removed the requirement that an array of profile links be added in the links object to indicate the extensions in use. The extensions in use are still conveyed in the aliases object in the document body, and in the Content-Type header.

In the error object, I introduced type as a top-level key, rather than as a link. (For more on the error object changes, see the commit messages; they provide some context on why these changes are needed and why they’re acceptable from a compatibility POV.)

I've decided to keep the aliases key at the top-level, rather than nest it under jsonapi, because it includes data that applies to the current document, not necessarily to the server as a whole (which is more what the jsonapi key is for iiuc).

Next Steps
Again, I think this is either ready to merge or very close, especially since we'd only be merging it into a draft spec. Still, I'm open to any feedback, although I'd rather not get bogged down bikeshedding names. I know it's a lot to review, so I've tried to break it up into coherent commits with detailed commit messages.

Thanks for the review @jmeas, and the encouraging comments. Typos fixed!

Thanks for rebasing your work and reopening this discussion, Ethan.
I'd like to try to establish consensus on some fundamentals before engaging in a thorough detailed review.
You have defined profile extensions as follows:

An API MAY support one or more "profile extensions" to supplement the capabilities of this specification.

A profile extension is a small, separate specification that defines a set of values that can be added to a JSON API document, and the meaning of those values at the different places they can occur.

My preference would be to define profile extensions as separate specifications that define particular usage patterns that are wholly compatible with the base JSON API specification.
I believe that profile extensions can be much more useful if they are allowed to define usage expectations of any specific part of the spec including query params, attributes, relationships, meta, etc. The only requirement is that these extensions must fully conform with the base spec.
Here are a few of the use cases we have discussed in the past:

particular pagination patterns through specifying usage of the page param

particular filtering patterns through specifying usage of the filter param

inclusion of set data in top-level meta (e.g. pagination statistics in a partial set)

inclusion of timestamps as either attributes or meta info per resource

expectations about the nature of IDs - i.e. client or server generated, UUIDs, etc.

I am concerned that this PR does not allow for some of these use cases. Do you agree that they should be in scope? Do we have a fundamental disagreement on the purpose of profile extensions?

@ethanresnick - Thanks as always for engaging so thoughtfully!
In order to establish the boundaries of the responsibilities of profile extensions, I would find it helpful to step back and try to carve up the responsibilities of the "neighbors" to profile extensions (i.e. other extensions, schemas, profiles, home documents, etc. that help to define and clarify an API). Otherwise, we risk introducing an unintentionally "gerrymandered" concept prematurely (sorry for the tortured analogy).
To be clear, I don't want to take away from your hard work here and all the discussions that have taken place. I believe much of this work is useful even if its boundaries shift a little bit after discussion.
I would find it useful to start a new discussion (very soon!) with a goal of providing a 10K foot view of the potential ways to define and standardize API structure and capabilities (i.e. profile extensions and all its neighbors). If we can agree on the high order bits, we can empower the community to explore some of these areas, and we can come back to review your PR here with confidence.

In order to establish the boundaries of the responsibilities of profile extensions, I would find it helpful to step back and try to carve up the responsibilities of the "neighbors" to profile extensions (i.e. other extensions, schemas, profiles, home documents, etc. that help to define and clarify an API). Otherwise, we risk introducing an unintentionally "gerrymandered" concept prematurely (sorry for the tortured analogy).

Hey Dan! I also don't want us to ship something that's narrower than it needs to be and/or ultimately makes JSON:API's design unnecessarily fragmented. To avoid that, I'm open to having the high-level discussion you're describing, and will try to go into it not totally attached to the existing design.
That said, I think there's also huge value in just shipping something soon, as long as it gets us, say, 80% of the way there. Right now, there are a number of use cases that JSON:API isn't addressing, that us editors haven't had the bandwidth to address, and we're starting to see non-compliant implementations and (I'd imagine) people just abandoning JSON:API as a result. While the current profile extension design is intentionally limited, I do believe it would immediately unblock the community to start addressing many of these issues in ways that we can learn from, without being bound to adopt their solutions in the base spec. I don't want the perfect to be the enemy of the good here.
So, in the name of making sure we ship something, do you have ideas for how we can constrain this 10k foot conversation so it doesn't totally derail shipping something? I'd really like to figure out the parameters for such a conversation before we open what could be a giant can of worms.

@ethanresnick I agree that we've got to build some momentum. I'm willing to say that we should at the very least time box such a potentially sprawling open-ended conversation. I think we could hash some rough parameters out in a couple weeks. I'm willing to get the discussion started this week and try to build consensus by August 11.
I think it's critical that we proceed cautiously and deliberately, but that we do in fact proceed.
If there are other ways you'd like to constrain this conversation before we start, please let me know.

@dgeb Cool. Timeboxing this to August 11th sounds like a good solution to me. I think we should also define the scope and desired output a bit more, but I'll let you do that in your OP, since I want to make sure we're including all the things you think are important to include.

@ethanresnick Please see https://github.com/json-api/json-api/issues/1207 for my attempt at a high-level discussion about extending and describing the spec. Sorry that it took me longer than expected.

Just wanted to chime back in and say that I've since read your further comments in https://github.com/json-api/json-api/issues/1207#issuecomment-320864590 and am less convinced link templates could not handle our filters. Good explanations!
However, I'm still ever so slightly on the side of @dgeb that I would like profiles to have greater power to define the usage of reserved query parameters without adopting link templates.


targetWidth smaller than tipWidth produces invalid position

When targets DOM element's width is smaller than tip's width - tooltip is placed incorrect. Its position is negative.
overridePosition function's parameters currentEvent currentTarget are equal nodes in this case.
My data-for DOM element is dinamically changed, and when this DOM element changed to smaller size (data-for is changing too) for the same tooltip - position is incorrect.
Rebuild doesn't help.

Hi @TotallWAR, could you plea put an example or use codesandbox and share what is happening.


Not working for Spotify

I am not able to use the extension with Spotify, to pause, play, etc.

Looks like the CSS classes are no longer in use:

Take a look at this PR:
https://github.com/borismus/keysocket/pull/355/files
Copy pasta the changes to your local files and it should work again.

I just discovered that I don't need this extension anymore since Chrome natively gives control over Spotify, etc with media keys. The PR looks good though


Exclude signatures from external dependencies

Fix java.lang.SecurityException on jar starting. Hopes to fix the issue #25

Thanks, yes this should fix it. The maven shade plugin will copy all files from the external dependencies to the final jar. Which results in an invalid signature.

@philipparndt sorry this was my first pull-request - how can I now sync my fork with yours or have I delete this and fork it again for a future pull-request?
Thanks, Alex

@AleksCee
Have a look at the description here:
https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/syncing-a-fork
You have to set the upstream first and then pull from this. Give it a try, you can do nothing wrong ;)
I always suggest always creating a branch when doing changes on a fork. Otherwise, you need to request the changes from your master and are locked out for future changes until your PR is merged.

@philipparndt ok, I have just fork via Browser and update the file online. So my fork now shows: ' This branch is 1 commit ahead, 1 commit behind philipparndt:master. ' - is the best way to delete it?
above this line github says

Pull request closed
If you wish, you can delete this fork of philipparndt/miele-to-mqtt-gw in the settings.

So, should I delete it?

you can delete it and create it again for the next change, or update it using a git cli.


Implement sensors

Sensors endpoint isn't currently supported. This results in Hue essentials effects stored on the bridge not functioning.

What exactly does a sensor have to do with effects ? What sensor is it missing exactly ?
Adding some sensors from HASS should be pretty easy I guess.

What exactly does a sensor have to do with effects ? What sensor is it missing exactly ?
Adding some sensors from HASS should be pretty easy I guess.

It seems that hue essentials uses some sensor stuff to get effects working on the bridge only without having to use the phone. If you try adding those effects, you will see what I mean.

It seems that hue essentials uses some sensor stuff to get effects working on the bridge only without having to use the phone. If you try adding those effects, you will see what I mean.

Seems like HueLabs also uses the same sensors trick for effects.

Seems like HueLabs also uses the same sensors trick for effects.

Once this issue has been resolved, it may be possible to add support for simple Routines. This could maybe be achieved by converting them to Home Assistant automations. See further:  https://github.com/hass-emulated-hue/core/discussions/103

The Home Assistant sensors did not import to Alexa, I was thinking to trigger some Alexa routines based on real or virtual HA sensors. The sensors do not show in the json. Do they export automatically or is there come configuration required?

curl  http://{ip}/api/{user}/sensors
	"1": {
		"state": {
			"daylight": null,
			"lastupdated": "none"
		},
		"config": {
			"on": true,
			"configured": false,
			"sunriseoffset": 30,
			"sunsetoffset": -30
		},
		"name": "Daylight",
		"type": "Daylight",
		"modelid": "PHDL00",
		"manufacturername": "Signify Netherlands B.V.",
		"swversion": "1.0"
	},
	"2": {
		"state": {
			"temperature": 2039,
			"lastupdated": "2021-03-14T16:43:11"
		},
		"swupdate": {
			"state": "noupdates",
			"lastinstall": "2019-03-15T18:32:32"
		},
		"config": {
			"on": true,
			"battery": 100,
			"reachable": true,
			"alert": "none",
			"ledindication": false,
			"usertest": false,
			"pending": []
		},
		"name": "Hue temperature sensor 1",
		"type": "ZLLTemperature",
		"modelid": "SML001",
		"manufacturername": "Signify Netherlands B.V.",
		"productname": "Hue temperature sensor",
		"swversion": "<IP_ADDRESS>575",
		"uniqueid": "00:17:88:01:02:03:c3:a5-02-0402",
		"capabilities": {
			"certified": true,
			"primary": false
		}
	},
	"3": {
		"state": {
			"presence": false,
			"lastupdated": "2021-03-14T16:44:41"
		},
		"swupdate": {
			"state": "noupdates",
			"lastinstall": "2019-03-15T18:32:32"
		},
		"config": {
			"on": true,
			"battery": 100,
			"reachable": true,
			"alert": "none",
			"ledindication": false,
			"usertest": false,
			"sensitivity": 2,
			"sensitivitymax": 2,
			"pending": []
		},
		"name": "Living room sensor",
		"type": "ZLLPresence",
		"modelid": "SML001",
		"manufacturername": "Signify Netherlands B.V.",
		"productname": "Hue motion sensor",
		"swversion": "<IP_ADDRESS>575",
		"uniqueid": "00:17:88:01:02:03:c3:a5-02-0406",
		"capabilities": {
			"certified": true,
			"primary": true
		}
	},
	"4": {
		"state": {
			"lightlevel": 27009,
			"dark": false,
			"daylight": true,
			"lastupdated": "2021-03-14T16:44:28"
		},
		"swupdate": {
			"state": "noupdates",
			"lastinstall": "2019-03-15T18:32:32"
		},
		"config": {
			"on": true,
			"battery": 100,
			"reachable": true,
			"alert": "none",
			"tholddark": 16000,
			"tholdoffset": 7000,
			"ledindication": false,
			"usertest": false,
			"pending": []
		},
		"name": "Hue ambient light sensor 1",
		"type": "ZLLLightLevel",
		"modelid": "SML001",
		"manufacturername": "Signify Netherlands B.V.",
		"productname": "Hue ambient light sensor",
		"swversion": "<IP_ADDRESS>575",
		"uniqueid": "00:17:88:01:02:03:c3:a5-02-0400",
		"capabilities": {
			"certified": true,
			"primary": false
		}
	},
	"5": {
		"state": {
			"status": 0,
			"lastupdated": "2021-03-14T16:41:37"
		},
		"config": {
			"on": true,
			"reachable": true
		},
		"name": "MotionSensor 3.Companion",
		"type": "CLIPGenericStatus",
		"modelid": "PHA_STATE",
		"manufacturername": "Philips",
		"swversion": "1.0",
		"uniqueid": "MotionSensor 3.Companion",
		"recycle": true
	}
}

curl  http://{ip}/api/{user}/sensors/3
	"state": {
		"presence": false,
		"lastupdated": "2021-03-14T16:46:31"
	},
	"swupdate": {
		"state": "noupdates",
		"lastinstall": "2019-03-15T18:32:32"
	},
	"config": {
		"on": true,
		"battery": 100,
		"reachable": true,
		"alert": "none",
		"ledindication": false,
		"usertest": false,
		"sensitivity": 2,
		"sensitivitymax": 2,
		"pending": []
	},
	"name": "Living room sensor",
	"type": "ZLLPresence",
	"modelid": "SML001",
	"manufacturername": "Signify Netherlands B.V.",
	"productname": "Hue motion sensor",
	"swversion": "<IP_ADDRESS>575",
	"uniqueid": "00:17:88:01:02:03:c3:a5-02-0406",
	"capabilities": {
		"certified": true,
		"primary": true
	}
}

Let me know if there is more info needed.

will it be possible to support triggering routines on the echo with the sensors feature? I'd love to be able to trigger echo routines based on HA entities

will it be possible to support triggering routines on the echo with the sensors feature? I'd love to be able to trigger echo routines based on HA entities

HI! how can I control hue emulation with echo device?


Use last known GPS location when open the app instead of waiting for a new one

Especially as if far away then have moving animation which involves an additional delay.
Related to Benjamin_Loison/WhatsApp/issues/2.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. For example:
I'm always frustrated when [...]
Describe the ideal solution
A clear and concise description of what you want to see in Organic Maps.
Describe alternatives you have considered

How do you solve this issue now with Organic Maps or other apps?
Attach any examples, screenshots, or screen recordings from other apps that help us to better understand the idea.

Additional context
Add any other context or screenshots about the feature request here.

Contrarily to WhatsApp this app always has access to my location, so it should be able to leverage it.

This feature would particularly be interesting when we want to locate us on a mpa but when we are in an unknown location building. Even if provided the permission Allow only while using the app, could ask anyway for privacy reasons consent to give the app the last known location by showing it. So this use-case is quite very different as the original one. Here the stake is that even we wait infinitely we will not be able to be located within a building while in the original use-case the purpose was just to wait a few seconds before getting current location.

Last location can be understood also as the phone always trying to locate itself and leverage last known location before opening the app.


Remove unneeded initialize functions

The function only call the parent.
All tests pass on Chrome 16

Please merge if the tests continue to pass.

tests continue to pass with FF 8


Prevent unsetting viewportEntered when not spying

When scrolling through a large list of components with the InViewport mixin, the _triggerDidAccessViewport method can set the viewportEntered property to false after listeners for the component have been unbound, causing the components to remain stuck in their outside viewport state. viewportEntered should only be set back to false if the spy is being used.

Any update on this? Our app depends on this fix and we've been running a fork version

LGTM, apologies for the incredible delay.

Np, thanks for the merge, @XrXr has been bothering me to remind you for the past week.


⚠ ClamAV has degraded performance

In b9addf9, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 443 ms

Resolved: ClamAV performance has improved in d6417b4 after 9 minutes.


Fix bad result on empty input passed to validate functions

The current code behaves differently if empty inputs is passed with a nullptr or not:
char16_t dummy{};
// this returns false (unexpected, empty input is valid UTF-16!)
validate_utf16be(nullptr,0);
// this returns true
validate_utf16be(&dummy,0);

This PR

strengthens the existing test a bit (there is more to do)
fixes such that empty input is deemed valid, regardless of nullptr or not
removes redundant zero length tests

Merging!

I think this may be worth pointing out in the next release notes, since it affects what could be a common use case.


feat: HttpServerService add default service list to config

Provide a config option to pre-filled the list of service routes.
This allows to work without info message

User Hono based web server which targets this behavior - see #153


Add Forking Clarification

Purpose
Dev docs specify to clone the original, but most contributors will be cloning a fork.
Changes

Clarify at the top of the docs that you should be cloning your fork
Add some more specific instructions about how to keep your fork in sync with the upstream branch
Also, make the PR from my fork!

Ticket
[unticketed]

Good point!


Cannot get RoadLines label from a LiDAR sensor

I am trying to get the object class for LiDAR. I have modified ALidar::ShootLaser and I have added this code:
uint8_t ObjectLabel  = static_cast<std::underlying_type<ECityObjectLabel>::type>(ATagger::GetTagOfTaggedComponent(*HitInfo.GetComponent()));
But it seems there is a problem to get Vehicles and RoadLines labels. By tracking the issue I realized
 GetWorld()->LineTraceSingleByChannel(     HitInfo,     LidarBodyLoc,     EndTrace,     ECC_MAX,     TraceParams,     FCollisionResponseParams::DefaultResponseParam   );
never hit RoadLines and HitInfo never contains any component of  Vehicles nor RoadLines.
In this visualization points are colored based on their labals, you can see there is no RoadLine label:

But I could get this information from a  'SemanticSegmentation' camera.

Thank you so much,
Best regards,
Ehsan

Hi @EhsanCode,
The ray-cast used by the lidar uses the collision channel, so only things with collision enabled will appear. Things like road-lines do not have collision for performance reasons. See also this issue with the vehicles #423. In the case of the vehicle the collision occurs with their physics asset instead of the mesh, I'm guessing that's the reason why they don't have a tag.

Hi @nsubiron
Thank you so much for your attention. I've enabled the collision on every roadLine content. Now, they have the same collision configuration as shown in this figure:

but still, no roadLine collision has been detected. Would you please let me know if I could do anything more to detect roadLine collision?
Thanks again.

Hi @EhsanCode,
Hmm I see the problem. Even if you set collision to BlockAll, the road lines do not have a collision mesh. You could add it manually but you'd have to do so for each road line, doesn't seem like a very optimal solution.
I'm suspecting we can change the lidar ray-cast configuration to go on the visibility channel, it is probably slower but it should hit the right item every time. If this works, it would fix the issues with the dynamic agents too. I'll try to get some time next week to experiment with this.
Btw, we were talking about different ray-cast options in the #cpp channel of our Discord.

Hi @nsubiron
Thank you so much for consideration.
As you mentioned, It seems collision mesh is not able to present some material such as fences. For example, as shown in the following image:

fence structure is not detectable with this method. I do not know if it is possible on the visibility channel?
Thank you so much
Best regards,
Ehsan

Hi @nsubiron
Thank you so much for your attention. I've enabled the collision on every roadLine content. Now, they have the same collision configuration as shown in this figure:

but still, no roadLine collision has been detected. Would you please let me know if I could do anything more to detect roadLine collision?
Thanks again.

I am trying to get the object class for LiDAR. I have modified ALidar::ShootLaser and I have added this code:
uint8_t ObjectLabel = static_cast<std::underlying_type<ECityObjectLabel>::type>(ATagger::GetTagOfTaggedComponent(*HitInfo.GetComponent()));
But it seems there is a problem to get Vehicles and RoadLines labels. By tracking the issue I realized
GetWorld()->LineTraceSingleByChannel( HitInfo, LidarBodyLoc, EndTrace, ECC_MAX, TraceParams, FCollisionResponseParams::DefaultResponseParam );
never hit RoadLines and HitInfo never contains any component of Vehicles nor RoadLines.
In this visualization points are colored based on their labals, you can see there is no RoadLine label:

But I could get this information from a 'SemanticSegmentation' camera.

Thank you so much,
Best regards,
Ehsan

Hello, I'm a beginner for this software.
May I ask you, how did you plot this point cloud out? How could you combine the UE4 with the lidar?

Road lanes are now detected by the new LiDAR introduced in #3131.


2 time text

Hello,
I have configured the following

    $(":file").filestyle('buttonText', 'Kies');

The result is that 'kies' is concatenated with 'choose file' this is the case in IE and chrome.

you have any examples of this error on the web so I can analyze?


remove agemo specifics from config_utils

Closes / Fixes / Resolves #0000
Motivation and Context

Description

Removes agemo specific implementation from config_utils file.
Splits up the gathering of configuration into:

default config
config from file
commandline config

This separation should allow for the util code to be easily placed in a common repo in the future. It should also allow for more flexibility.

Need to reopen this pr against main


unable to execute DELETE queries

Describe the bug
Hey there, i'm trying to test your library which looks pretty good, but got some errors trying to delete data, which always return an error but i see the query in my snowflake audit log, do you know if it is a limitation in that sense?
To Reproduce
Snowpack.query!(:snowpack, "delete from all_events_v3 where account_id='15094' and user_id='fake'")
[warning] Unable to execute query: No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
** (Snowpack.Error) No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
    (snowpack 0.7.4) lib/snowpack.ex:170: Snowpack.query!/4

Snowpack.query!(:snowpack, "delete from all_events_v3 where account_id='15094'", [], parse_results: false)
[warning] Unable to execute query: No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
** (Snowpack.Error) No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
    (snowpack 0.7.4) lib/snowpack.ex:170: Snowpack.query!/4

Snowpack.query!(:snowpack, "delete from all_events_v3 where account_id=?", ["15094"], parse_results: false)
[warning] Unable to execute query: No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
** (Snowpack.Error) No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
    (snowpack 0.7.4) lib/snowpack.ex:170: Snowpack.query!/4

i can't use prepare statements either
iex(6)> query = Snowpack.prepare!(:snowpack, "delete_events", "delete from all_events_v3 where account_id=?")
%Snowpack.Query{
  columns: nil,
  name: "delete_events",
  num_params: nil,
  ref: nil,
  statement: "delete from all_events_v3 where account_id=?",
  type: nil
}
iex(7)> Snowpack.execute(:snowpack, query, ["15094"])
[warning] Unable to execute query: No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
{:error,
 %Snowpack.Error{
   message: "No SQL-driver information available. | ODBC_CODE \a | SNOWFLAKE_CODE<PHONE_NUMBER>",
   native_code: "1167924348",
   odbc_code: "\a"
 }}

but for example this works
Snowpack.query!(:snowpack, "select current_user()")
%Snowpack.Result{columns: ["CURRENT_USER()"], num_rows: 1, rows: [["MYUSER"]]}

Expected behavior
it should not be returning an error but instead succeed
Additional context
I'm testing this using the ARM version of snowflake and odbc

I added a test for DELETE here and it is passing, so my guess is a configuration or permissions issue. That error message is not entirely helpful.
Can you run other select queries that hit your real Snowflake tables?
I also added some steps that we use to run on ARM to the readme.

hey @forest thanks for you fast response, is really weird, select works and i'm using a staging DB which i have permissions and we are also evaluating snowflex but they hay a similar issue with parametrized deletions, but in their case, it works when we use it this way, i'm going to try the steps you use in your readme for ARM and see if that changes something, thank you.
# splited for readability
Snowflex.sql_query(
	SnowflakeConnection,
	"delete from all_events_v3 where account_id='15094'",
	[ timeout: :timer.hours(1), map_nulls_to_nil?: true ]
)

I already replaced unixodbc with libiodbc did the same as in the PR you linked but still the same
iex(1)> Snowpack.query!(:snowpack, "select current_user()")
%Snowpack.Result{columns: ["CURRENT_USER()"], num_rows: 1, rows: [["SIMON"]]}
iex(2)> Snowpack.query!(:snowpack, "select * from all_events_v3 where account_id = '15094'")
%Snowpack.Result{columns: ["ID", "ACCOUNT_ID", "USER_ID", "NAME", ...], num_rows: 0, rows: []}
iex(3)> Snowpack.query!(:snowpack, "delete from all_events_v3 where account_id = ?", ["15094"], parse_results: false)
[warning] Unable to execute query: No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
** (Snowpack.Error) No SQL-driver information available. | ODBC_CODE ^G | SNOWFLAKE_CODE<PHONE_NUMBER>
    (snowpack 0.7.4) lib/snowpack.ex:170: Snowpack.query!/4

Do you see the query in the Snowflake query logs? I'm wondering if the issue is before the query is made to SF or after when the results are handled.

yes, this is what i'm seeing in the query history

I think I found the issue. Erlang ODBC incorrectly returns an error for DML (INSERT, UPDATE, DELETE) when there are no results returned. I need to confirm with a test and then make a fix.

Did the row you delete with account_id = '15094' actually get deleted from SF?

hey forest, i'm not sure about this, for example when i exec that query in snowflex i get {:updated, 0} (no parametrized) but with snowpack i get an error, and no, it is not deleting data as i'm just testing it works before running it against a real account just to be safe, but it should be returning 0 rows still

@sescobb27 let me know if this fix resolves your issue.

hey forest, well yeah, that indeed worked, i'm going to try with real data and going to see how it goes, thank you!!!!


HDDS-5075. [SCM HA Security] Remove code of not starting ozone services when Security is enabled on SCM HA cluster

What changes were proposed in this pull request?
Now SCM HA security is implemented, we can remove additional config of not starting ozone services when SCM HA is enabled on a secure cluster.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5075
How was this patch tested?
Existing docker tests.

Thanks for creating this PR @bharatviswa504
Does it mean that security of SCM-HA is fully finished and production ready?

Thanks for creating this PR @bharatviswa504
Does it mean that security of SCM-HA is fully finished and production ready?

@elek
Yes, planned phase 1 items are almost completed. We have one in-progress HDDS-5060.
And also we have a docker-compose ozone-secure-ha which starts SCM HA in a secure environment and CI is running tests in this env.

@adoroszlai I have added for almost all SCM HA security tasks the [SCM HA Security], so following the same notion for this task also.Hope you are okay with it?

Thanks the answer @bharatviswa504

Yes, planned phase-1 development tasks are almost completed. We have one in-progress HDDS-5060.

Based on my understanding without HDDS-5060 it can not be secure in production. We shouldn't release the current code it without this safety check (or we need to issue a cve... ;-) )
Is there any specific reason to remove this check before having full security? I mean: if it's required for acceptance tests, we can directly configure this value in docker-config files.
Or do we have any other motivations?
I have a strange feeling about committing something to the master which makes the branch non-releaseable...

Thanks the answer @bharatviswa504

Yes, planned phase-1 development tasks are almost completed. We have one in-progress HDDS-5060.

Based on my understanding without HDDS-5060 it can not be secure in production. We shouldn't release the current code it without this safety check (or we need to issue a cve... ;-) )

Is there any release planned from master, before next release we will make sure we shall have this fix.

Is there any specific reason to remove this check before having full security? I mean: if it's required for acceptance tests, we can directly configure this value in docker-config files.

Currently, in docker-tests we have that way.  If you see this PR, this PR is removing the config in docker tests.

Or do we have any other motivations?
I have a strange feeling about committing something to the master which makes the branch non-releaseable...

The motivation for this is in Cloudera CM integration we don't need this additional config for CM integration of SCM HA.
Currently, SCM HA work is merged to master, so SCM HA security tasks are being worked on in master directly, and as said above this will be addressed before next release. But if you feel strongly this cannot be committed until we have HDDS-5060 I am fine with it.

I have added for almost all SCM HA security tasks the [SCM HA Security] prefix, so following the same notion for this task also.Hope you are okay with it?

Sure, it's OK, although I think it makes titles too long without adding much value.  Both SCM HA and security are already part of the title in this case.  Labels also help categorize PRs and Jira issues.
I just wanted to add the missing Jira ID.

I think the release is far away. HDDS-5060  is required only if log purging is enabled for SCM HA which is currently disabled. I prefer to merge this change right away.
Thanks @elek , @elek and @adoroszlai for suggestions/feedbacks.

I think the release is far away

I am not sure. 1.1.0 is merged a long time ago, so it seems to be reasonable to publish sg. in the next 1-2 months. (IMHO).

The motivation for this is in Cloudera CM integration we don't need this additional config for CM integration of SCM HA.

I have a very mixed feeling about this motivation. If it's a problem on the vendor side, I strongly recommend fixing it on the vendor side instead of Apache master. Especially if it can be done easily. There are other users of Apache Ozone and I know at least one who uses snapshots from the master branch. I think master should be as stable and secure as possible. This is the reason why we use feature branches to stabilize all the works outside the master.

HDDS-5060 is required only if log purging is enabled for SCM HA which is currently disabled by default.

This is a very good argument, and I am fine with that if this is the case. Can you please share how is this log purging used? Isn't it required for bootstrapping/restoring Ratis nodes? Is this grpc endpoint turned off by default? How is ratis snapshot moved between nodes when this is turned off?

I prefer to merge this change right away.

My preference is keeping master always as secure and stable as possible. Our 1.1.0 release was delayed with 3-4 months because earlier we used snapshot dependencies from Ratis. While I think it was a good decision earlier, my preference is improving our practice and keeping the master always releasable. (feature flags are good, but we should make it impossible to start something which is supposed to be secure but not).

I think the release is far away

I am not sure. 1.1.0 is merged a long time ago, so it seems to be reasonable to publish sg. in the next 1-2 months. (IMHO).

The motivation for this is in Cloudera CM integration we don't need this additional config for CM integration of SCM HA.

I have a very mixed feeling about this motivation. If it's a problem on the vendor side, I strongly recommend fixing it on the vendor side instead of Apache master. Especially if it can be done easily. There are other users of Apache Ozone and I know at least one who uses snapshots from the master branch. I think master should be as stable and secure as possible. This is the reason why we use feature branches to stabilize all the works outside the master.

HDDS-5060 is required only if log purging is enabled for SCM HA which is currently disabled by default.

This is a very good argument, and I am fine with that if this is the case. Can you please share how is this log purging used? Isn't it required for bootstrapping/restoring Ratis nodes? Is this grpc endpoint turned off by default? How is ratis snapshot moved between nodes when this is turned off?

I prefer to merge this change right away.

My preference is keeping master always as secure and stable as possible. Our 1.1.0 release was delayed with 3-4 months because earlier we used snapshot dependencies from Ratis. While I think it was a good decision earlier, my preference is improving our practice and keeping the master always releasable. (feature flags are good, but we should make it impossible to start something which is supposed to be secure but not).

Log purging can be enabled in SCM HA by setting the config "ozone.scm.ha.ratis.log.purge.enabled" set to true which is set to false by default. For more details, please refer SCMHAConfiguration.java class.
Unless, the logs are purged, ratis uses the same appendLog protocol using grpc to replicate the scm metadata. Unless, the logs are purged, no install snapshot notification will get initiated to the follower nodes. There is no requiemnet to moves across ratis snapshots.
https://github.com/apache/ozone/pull/2155 will fix the install snapshot mechanism which incoroporates some ratis fixes to make the whole install snapshot mechanism work. Once this gets done, the secure grpc channel work can start.


RPC support

Hope this tool can support RPC,like grpc、dubbo

@L-sing We have support for http/2 or grpc but it's not built into this project for a myriad of reasons. Take a look at https://github.com/SpectoLabs/hoverfly-java-grpc and contact me direct if that approximates what you are looking for stating what you need.

Closing issue as it's not really specific enough to produce any tasks & it is unclear what the OP's use-case is.


Enable openssl:arm64-windows (Fix #4478, #4812)

Enable openssl:arm64-windows by updating port file for ARM64 and removing -WX
Fix #4478, #4812

Thanks for the PR, @tony979!

Thanks!


CPU and GPU at same time

When I does hashcat in my slow machine, I can use CPU and GPU at same time. It gives about 5 to 10% more power.
So, when I rent a server in Vast.ai and use the SAME hash type, I couldn't use CPU and GPU. The CPU usage showed in Vast.ai is always low, so I thing I am loosing computer power. So:

Is it a good idea? The power will increase or using the CPU will make the GPU degrade?
If so, what does I need to install? Lets say I am using RTX 3090
Is there a easy solution or every CPU will have to install the driver?

I tried to install a lot of things and none worked.

Back when I was only writing these docker scripts (mostly for myself) I also tried to employ every possible backend, namely CPU and GPU (intel card but it does not matter). Over the years I've stopped using this approach and given CPU to rest, and now I refrain from utilizing CPU for things like hashcat unless I'm running it on a Raspberry Pi.
You can read plenty of discussions on Hashcat forum where serious people say that utilizing CPU for password cracking is a bad idea.
In your case with Vast.ai it may very be that the provider limits your CPU usage with time. For example, if you always utilize CPU by 100% (please don't), then they may slow it down intentionally.
In short, don't use the CPU backend other than for testing.

Closed due to no activity.
Feel free to ask.


SQL for samples query mishandles OR condition in filter

When adding a SodaCL missing_count check with an OR condition in the filter, we get inaccurate results for the samples. In particular, we discovered that this OR condition can override the dataset filter SQL.
We found this stems from how the samples SQL is generated. The SQL to get the number of failed rows is not affected because it uses COUNT(CASE WHEN... rather than placing all filters on a single line.
Example Soda check:
filter db.table [dataset_filter]:
    where: db_filter = '${variable}'

checks for db.table [dataset_filter]:
    - missing_count(value_column) = 0:
            filter: column_a IS NOT NULL OR column_b IS NOT NULL

Example samples query:
SELECT * FROM db.table
 WHERE db_filter = ‘variable’ AND value_column IS NULL AND column_a IS NOT NULL OR column_b IS NOT NULL
 LIMIT 5

This leads to us getting results where column_b IS NOT NULL is true regardless of the other conditions.
The accurate query is as follows:
SELECT * FROM db.table
 WHERE db_filter = ‘variable’ AND value_column IS NULL AND (column_a IS NOT NULL OR column_b IS NOT NULL)
 LIMIT 5

The correct SQL can be generated by adding parentheses to the check filter, as so:
checks for db.table [dataset_filter]:
    - missing_count(value_column) = 0:
            filter: (column_a IS NOT NULL OR column_b IS NOT NULL)

However, this is an unexpected behavior and ideally the parentheses would not be required.

from pyspark.sql import SparkSession
from soda.scan import Scan
from soda.sampler.sampler import Sampler, SampleContext

# custom sampler to print the amount of rows being sampled
class CountRowsSampler(Sampler):
    def store_sample(self, sample_context: SampleContext):
        print(f'samples: {sample_context.sample.get_rows()}')

spark_session = SparkSession.builder.config('spark.app.name', 'pytest-spark').getOrCreate()

data = [[ 'banana', 10, -1 ]] * 3 + [[ 'apples', 8, -1 ]] * 3
df = spark_session.createDataFrame(data=data, schema=['fruit', 'sweetness_score', 'umami_score'])
df.createOrReplaceTempView('dataframe')

# setup the scan
scan = Scan()
scan.add_spark_session(spark_session=spark_session)
scan.set_data_source_name('spark_df')

check = """
filter dataframe [bananas_only]:
    where: fruit = 'banana'

checks for dataframe [bananas_only]:
    - missing_count(umami_score) = 0:
        missing values: [-1]
        filter: sweetness_score = 8 OR sweetness_score = 10
"""
scan.add_sodacl_yaml_str(check)
scan.sampler = CountRowsSampler()

scan.execute()

output:
samples: (['banana', 10, -1], ['banana', 10, -1], ['banana', 10, -1], ['apples', 8, -1], ['apples', 8, -1], ['apples', 8, -1])

You can see here the sampler includes apples where the dataset wide filter should filter for just bananas

Thanks for reporting @abargar ! This indeed seems to be easily fixable by putting the check filter into parentheses, would you be open to contribute a fix here? It should be very straightforward - add parentheses to all check types when filter is applied + add a test for each test type.

Hi, sure I'd be happy to! I'm more likely to have availability for this next week.


BLD: Don't assume -pthread is already set on compiler

Reference issue
Fixes gh-11323
What does this implement/fix?
This explicitly adds the -pthread argument to pypocketfft builds. This isn't usually required since distutils usually adds this argument already.

I successfully tested this on the system it failed previously. Thanks!

Alright, original issue reporter confirmed fix & there's a core dev approval. FWIW, I don't observe any build issues like this on POWER8 or POWER9 gcc compile farm machines using latest master, so it seems to apply to that very specific build scenario with certain flags set, etc.

Thanks @peterbell10


readme

Coverage decreased (-1.1%) to 79.464% when pulling 27cda50bbaa067e3c6a52314cda136fd14a2ff41 on ldecicco-USGS:master into 9946fb7a9032ef2bff31a76bc0d4123739dab88e on USGS-R:master.


Unsubscribe support for email

I added email. I didn't add unsubscribe since there's only 1 email so far, not a long running mailing list. However, others will probably add so this would be good to have.

[ ] Add a bool unsubscribed property to the profile table
[ ] Update sendUserEmail function to check unsubscribed property, and not send if unsubscribed
[ ] In the email section of settings add an "Unsubscribe" button (which changes to "Re-Subscribe" when unsubscribed), which is functional, and sets DB property.
[ ] Add unsubscribe link to /account/settings?unsubscribe to email templates

Hi @scosman, can I work on this please?


how listview gridview load more data!

How ListView and GridView load more dada!

What I did is using ListView.builder() with a size bigger than the available items.
If ListView.builder() requests an item for an index that is not loaded, I return a dummy item that shows a loading spinner and invoke a request to the database. When the response from the database arrives I re-render (call setState()) and when ListView.builder() requests the index again, I can instead return an actual item because now it is available.
You can use a ScrollController with ListView.builder() to figure out scroll position, but here you also need the size of the list. I haven't tried to get that yet myself.

I am very much interested in this. There is not much documentation on how to do this with loading data from a server.  All the tutorials talk about loading objects that are created.

summon @brianegan

Thanks for the feedback, everyone! I'll add this to my list of Recipes :) Please vote for this issue on the list here: https://github.com/flutter/flutter/issues/15297#issuecomment-377540849
The more thumbs I get, the higher priority it becomes!

I was able to get it to work, not a perfect method but it works, if it helps someone to perfect it...
you can get the initial idea from this page https://stackoverflow.com/questions/49508322/flutter-listview-lazy-loading, just like @zoechi had explained
extending the idea...
I receive the json data from a rest service with 20 rows, and i request the next (and the rest) page(s) with an offset of 19.
in the ListView.builder i check whether its the last item and if it is, i render a CircularProgressIndicator() instead, as i offset by 19 (one less that the page size), i get the last item i skipped rendering on the previous request as the next requests first item, and so on.
Yes there is a data overhead, still trying to figure how to avoid it...

Hi there
I don't know how to create a list view that loads a page at a time

@gratefulgirl I created a plugin that is a paged list view for mobile and paged data table for tablets. Check it out and see if it can do what you need

Thanks . Who are you by the way 😏
On Tue, Mar 5, 2019, 00:22 Rody Davis<EMAIL_ADDRESS>wrote:

@gratefulgirl https://github.com/gratefulgirl I created a plugin that
is a paged list view for mobile and paged data table for tablets. Check it
out and see if it can do what you need
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/15195#issuecomment-469465861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtEIMgLHjp2jQKIZr0l-akL6utr285wuks5vTaqjgaJpZM4SeLLJ
.

Especially when the ListView has scrolled to the bottom, it still calls the scrollListener a couple of times. The better approach is to combine Notification Listener with Remi’s approach. Here is my solution:
https://icetutor.com/question/flutter-listview-lazy-loading

wow, nice....
On 5 Oct 2019 6:43 pm, "patelkrunal78"<EMAIL_ADDRESS>wrote:

Especially when the ListView has scrolled to the bottom, it still calls
the scrollListener a couple of times. The better approach is to combine
Notification Listener with Remi’s approach. Here is my solution:
https://icetutor.com/question/flutter-listview-lazy-loading
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/15195?email_source=notifications&email_token=ALIQQMQVSROTB2XMZISB7ATQNDG5RA5CNFSM4ETYWLE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEANXX3Q#issuecomment-538672110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALIQQMU6PHYGT4O4J5WK4HDQNDG5RANCNFSM4ETYWLEQ
.


Add note explaining that dotnet CLI doens't support pushing to feeds that require API Key

Using the DotNetCoreCLI nuget push task doesn't work if the feed requires an API Key (like nuget.org). See: https://github.com/microsoft/azure-pipelines-tasks/issues/7160
Workaround is below where $(NuGetSourceServerUrl) and  $(NuGetSourceServerApiKey) are defined in pipeline variables.
- task: DotNetCoreCLI@2
  displayName: Push Nuget Package
  inputs:
    command: custom
    custom: nuget
    arguments: >
      push $(Build.ArtifactStagingDirectory)/**.nupkg
      -s $(NuGetSourceServerUrl)
      -k $(NuGetSourceServerApiKey)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d1d9884-19f7-592b-f47c-8cf100639ff0
Version Independent ID: 555c3826-60d9-2589-54af-850efbfbb13a
Content: .NET Core CLI task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/dotnet-core-cli.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @pulkitaggarwl
Microsoft Alias: puagarw

The > got encoded when you were copying the custom task

Thanks. Fixed that and a typo in the title.


Is there any example with recent version of Megatron-LM?

The examples showed here or here is based on versions about half a year ago. Is there any examples aligned with recent Megatron? Or, is there still relatively obvious optimization with deepspeed to Megatron with pipeline parallelization now?

Hi but the second page says that it is updated on March 21, 2022. I am new to Deepspeed and learning it. I don't know whether it is true.

Hello, I am a studenHello, I am a student studying zero3. I wonder if you have successfully run this project. If possible, could you please briefly explain the processt studying zero3. I wonder if you have successfully run this project. If possible, could you please briefly explain the process


Intended logic in updateKeyframes()

I have some questions about this section of updateKeyframes():
https://github.com/vectr-ucla/direct_lidar_inertial_odometry/blob/a524000eb2e18a801a9222410650ddb12eddde39/src/dlio/odom.cc#L1572-L1589
To my understanding, there are some possible issues here:
rotational exploration keyframing
// rotational exploration keyframing
if (abs(dd) <= this->keyframe_thresh_dist_ && abs(theta_deg) > this->keyframe_thresh_rot_ && num_nearby <= 1) {
  newKeyframe = true;
}

is always overwritten by
 if (abs(dd) <= this->keyframe_thresh_dist_) {
   newKeyframe = false;
}

num_nearby has no effect
If this statement
 if (... || abs(theta_deg) > this->keyframe_thresh_rot_) {
   newKeyframe = true;
 }

is true (from the second condition),
// rotational exploration keyframing
if (abs(dd) <= this->keyframe_thresh_dist_ && abs(theta_deg) > this->keyframe_thresh_rot_ && num_nearby <= 1) {
  newKeyframe = true;
}

this statement doesn't change newKeyFrame, even if num_nearby is larger than 1. At this point, abs(dd) <= this->keyframe_thresh_dist_ is always true, given that abs(dd) > this->keyframe_thresh_dist_ was false in the condition before.
Intended logic
What is the intended logic here? I couldn't find much about this in your papers, except the adaptive thresholding distance to account for tight spaces.
Without the rotational exploration keyframing, the logic is clear to me (roughly):
if abs(dd) <= this->keyframe_thresh_dist or abs(dd) > 0.5 -> return false
else if abs(dd) > this->keyframe_thresh_dist -> return true

Now, I don't quite understand why the keyframe are updated when a large rotation was registered. In a scenario where, let's say, the robot stays in the same spot, but turns 180deg. Why do I have to update keyframes? The map is rotation invariant, so to speak, so I have gained no new information about the environment just be turning. I guess this is what was meant with the following statement in the DLO-paper?

Keyframe nodes are commonly dropped using fixed thresholds (e.g., every 1m or 10◦ of translational or rotational change)

Thanks for you help, happy to discuss

There were originally some additional checks in that block from our new DLIOM algorithm that I removed when open-sourcing this code (e.g., slippage), but I should have just removed that entire block. I'll push a new update in a bit. Thanks for the catch.

Understood. DLIOM being available some day would be awesome :)

There are some sensors (i.e., Intel L515 or some older Livox sensors) that have a limited FOV, so keyframes are rotation-dependent [...]
so tilting up or down would provide more information

Makes perfect sense!

Updated! Thanks again for the catch.


Add focus guidance

This PR adds guidance on focus states in the Design System and how to make them accessible in custom components.

You can preview this change here:
Built with commit 7f3173f2670fb6b3258865a4b87d27409502ce7a
https://deploy-preview-975--govuk-design-system-preview.netlify.com


do not add tls contexts to inboud clusters

Please provide a description for what this PR is for.
if trafficDirection is inbound, explicitly set the tls context to disable else auto mtls kicks in and sets up the transport socket matcher for inbound as well
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

it's odd, clusteropts.direction is not used anywhere in the code.  also seems odd that in a method called applyUpstreamTLSSettings we never check direction anywhere before calling it

@GregHanson: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
288e6eb425c79cc79f873065e4d671406ffda497
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I modified the title, as I understand you want to remove the transport_socket_matches not the Cluster.tls_context for inbound cluster.
Also this is a clean up of the config, but should not have actual effect in terms of connectivity, right?

@incfly yes, this is partial config cleanup - as of right not including the transport_socket_matches on the inbound cluster does not produce any failures.  But as John also said, the proxy version check does verify compatibility with older sidecars since they are expecting a cluster.tlscontext to be set in that case

@GregHanson: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
bd7586a09f55917a9d929f6b4426170f463710c5
link
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@GregHanson: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
bd7586a09f55917a9d929f6b4426170f463710c5
link
/test unit-tests_istio

integ-security-k8s-tests_istio
bd7586a09f55917a9d929f6b4426170f463710c5
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest
test disabled in https://github.com/istio/istio/pull/18053

In response to a cherrypick label: new pull request created: #18072


Unable to connect to host

Hello,
I try to use Hyperion but I have "unable to connect to host"...
$ sudo netstat -ntl
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:8070            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:3306          <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:8334            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:80              <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:8019            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:8083            <IP_ADDRESS>:*               LISTEN
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN
AND
$ sudo hyperiond /etc/hyperion.config.json :
Application build time: Mar  6 2015 20:57:44
QCoreApplication initialised
Selected configuration file: /etc/hyperion.config.json
ColorTransform 'default' => [0; 49]
Device configuration:
{
"colorOrder" : "rgb",
"name" : "MyPi",
"output" : "/dev/spidev0.0",
"rate" : 250000,
"type" : "ws2801"
}
Black border threshold set to 0.01 (3)
Not creating any smoothing
Effect loaded: Knight rider
Effect loaded: Blue mood blobs
Effect loaded: Cold mood blobs
Effect loaded: Full color mood blobs
Effect loaded: Green mood blobs
Effect loaded: Red mood blobs
Effect loaded: Warm mood blobs
Effect loaded: Rainbow mood
Effect loaded: Rainbow swirl fast
Effect loaded: Rainbow swirl
Effect loaded: Snake
Effect loaded: Strobe blue
Effect loaded: Strobe Raspbmc
Effect loaded: Strobe white
Initializing Python interpreter
Hyperion created and initialised
run effect Rainbow swirl fast on channel 0
Boot sequence(Rainbow swirl fast) created and started
XBMC video checker created and started
hyperiond: /home/tvdzwan/hyperion/libsrc/grabber/dispmanx/DispmanxFrameGrabber.cpp:23: DispmanxFrameGrabber::DispmanxFrameGrabber(unsigned int, unsigned int): Assertion `_vc_display > 0' failed.
What it means to the last line ?

I solved the problem...
I comment in hyperion json config file :
///"framegrabber" :
///{
///     "width" : 64,
///     "height" : 64,
///     "frequency_Hz" : 20.0
///},
And it work !

Are you running it on a raspberry pi ?

Yes, Raspberry Pi 2

I've seen that error sometimes if I have 2 instances running . Restarting both has always fixed it for me.
Is there anything else running which is also grabbing from the dispmanx display ?


change database format to two columns: ID and xml

@Brennan1994 please add anything I missed

this work has been completed:


Moved inline css/javascripts out to their own files

As constance use inline JavaScript to reset field to default, it will be unusable when the site have CSP setup. I've moved inline JS/CSS out to their own files.

Thank you


regexp: fast path for prefix/suffix literals matching on anchored regexps

To my understanding, currently there's no fast path for anchored regular expressions starting/ending with a literal, like ^something.*$ or ^.*something$. I'm wondering if you have considered adding a specific optimisation for this use case.
Use case
I'm raising this issue, because in Prometheus we do a large use of anchored regexps (for labels matching) and having prefix/suffix literals in the regex looks to be quite a common use case.
In past few days I've worked on a small optimization in Prometheus (PR) to detect safe cases when we can circuit break the regex matching with a strings.HasPrefix() and strings.HasSuffix(), and it showed to bring significant benefits for our specific use case.

As an extension the regexp does not even need to be anchored. Some overuses of regex I have seen are just matching a constant string which can usually optimized by using strings.Contains

Perhaps a duplicate of https://github.com/golang/go/issues/21463? CC @sylvinus

/cc @matloob per owners.

Yeah, I think this would be addressed through a combination of https://github.com/golang/go/issues/21743, and Russ's first suggestion in https://github.com/golang/go/issues/21463#issuecomment-326151555.
I think in the case of ^something.*$, it looks like go through the fast path of checking a literal prefix, and then get bogged down scanning the rest of the string to handle the .*$. And if we could scan backwards as in #21743, we'd be able to handle the second case too.


Unable to create bean SimpleMessageListenerContainer due to not matched signature

Hello, could you please help? thanks very much.
We are trying to use spring-cloud-aws (2.3.5) to handle s3 file upload event as following (java + user credentials + aws assume role, role with right permission to retrieve access/secret keys from secret manager):
@SqsListener(value="${my.sqs.name}", deletionPolicy=SqsMessageDeletionPolicy.ON_SUCCESS)
public void receiveMessages(S3EventNotification s3Event) { ... }
The spring boot java config file initiate AmazonSQSAsync bean as:
@Bean("amazonSQS")
@DependsOn ("awsCredentialsProvider")
public AmazonSQS amazonSqs() throws JsonProcessingException {
return AmazonSQSAsyncClientBuilder.standard()
.withCredentials(credentialsProvider())
.withRegion(Regions.fromName(region))
.build();
}
Where credentialsProvider() will depends on the AWS access/secret keys retrieved from secret manager. AmazonSQS bean creation OK, but failed with following message while create bean SimpleMessageListenerContainer:
ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'simpleMessageListenerContainer' defined in class path resource [io/awspring/cloud/autoconfigure/messaging/SqsAutoConfiguration$SqsConfiguration.class]: Invocation of init method failed; nested exception is com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (Service: AWSSecurityTokenService; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: ....
If we directly use aws user credentials instead of retrieving from secret manager, everything works fine.
If we remove spring-aws-cloud (thus no SqsListener but still create AmazonSQS bean), everything works fine.
Googled around and some posts indicating credentials with special characters such as  / or + are the issues, but some claiming no special character credential still failed.

Ideally please try with the latest version in 2.x and see if the issue remains. If it does, maybe we can figure it out.

BTW, tried 2.4.2 spring-cloud-aws, same issue. thx

by debugging, issue from com.amazonaws.http.AmazonHttpClient.java (execOneParams.apacheRequest=POST https://sts.amazonaws.com/ HTTP/1.1, Header info: name=Authorization, value=AWS4-HMAC-SHA256 Credential=..., Signature=....): when try to retrieve secrete from secret manager (temporary credentials) and after assume role ( retrieved from secret manager), different credentials make the above POST return 403 Forbidden. Tried modify task definition by adding secrets, failed with same errors. thanks

Closing as 2.x is not maintained anymore. If you would like to contribute a fix for that, we will make an exception and release new 2.x version.


Mongodb service conflict: Could not find the requested service mongodb: host on centos

Fixed on v4.4.x


Add Waiting Room resources

Description of your changes
Add Waiting Room resources

Fixes #
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
With uptest tests

/test-examples="examples/zone/zone-enterprise.yaml, examples/waitingroom/room.yaml, examples/waitingroom/event.yaml, examples/waitingroom/rules.yaml"


update-commit-db might miss commits

It only looks at the first page of commits. If we get very busy, it might not catch all of them.
This should be alleviated once a release happens, but master will be missing in the meantime. So ideally it should go back enough to not miss anything.

I'll pick this up. Idea is to loop through pages grabbing commits until you either run out of pages or hit the SHA of the latest commit in the latest release for a project currently in the database. Quick question though, what is the purpose the visible field in the Releases table?

Idea is to loop through pages grabbing commits until you either run out of pages or hit the SHA of the latest commit in the latest release for a project currently in the database

Exactly.

Quick question though, what is the purpose of the visible field in the Releases table?

In order to write the release blog post, I need to know how many people have contributed. In order to do that, I have to create the release. But then it's up before the actual announcement. So, basically, a new release will sit as false for a few days, and then set to true on release day.
Given that this process is only done with the master release, which will always be true, you shouldn't have to worry about it :)

Having hacked on it a little, there's two ways I can see implementing this.
The first assumes that commits are inserted in order which is a hacky
assumption BUT requires very little change to the current code. The second
would add a date column to the commits table in order to set a sort order
for commits but is a much more involved change. Thoughts? Sorry for the
terrible formatting
On Apr 3, 2017 10:21 AM, "Steve Klabnik"<EMAIL_ADDRESS>wrote:

Idea is to loop through pages grabbing commits until you either run out of
pages or hit the SHA of the latest commit in the latest release for a
project currently in the database
Exactly.
Quick question though, what is the purpose of the visible field in the
Releases table?
In order to write the release blog post, I need to know how many people
have contributed. In order to do that, I have to create the release. But
then it's up before the actual announcement. So, basically, a new release
will sit as false for a few days, and then set to true on release day.
Given that this process is only done with the master release, which will
always be true, you shouldn't have to worry about it :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/thanks/issues/15#issuecomment-291157954,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACwkvoSsPdyahjv6R1HqHODi8R7SKIASks5rsQBngaJpZM4LiSko
.

Thoughts?

Can you elaborate a bit more at the high level of how this works? That is, I'm not sure what adding the dates would get you, exactly.

We need a way to say "what was the last commit saved for the latest non
master release". We could assume that commits are inserted in order which
means we wouldn't need dates, or we could use the date_approved field.
Unless there is some other mechanism for ordering commits that I'm not
aware of
On Apr 3, 2017 11:31 AM, "Steve Klabnik"<EMAIL_ADDRESS>wrote:

Thoughts?
Can you elaborate a bit more at the high level of how this works? That is,
I'm not sure what adding the dates would get you, exactly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/thanks/issues/15#issuecomment-291179369,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACwkvqckUSg-aZrJ42L6pk-EfUnjSBlPks5rsRC3gaJpZM4LiSko
.

We need a way to say "what was the last commit saved for the latest non master release"

Ah, I see. Right. Hm.
Honestly, with stuff like https://github.com/rust-lang-nursery/thanks/pull/97, I'm starting to wonder if the right approach here is to just always dynamically calculate things. Originally I chose not to because I wasn't sure about heroku; however, crates.io is hosted there, and it seems to work? I'm not sure how that works though; maybe @carols10cents could help enlighten us here.

Sorry, I don't have much context here about what you'd like to know... what about heroku are you not sure? The performance of database queries? The performance of web requests? Are you on free or paid dynos, free or paid database? What are you currently caching and considering dynamically calculating? How often do you need to update the data and query the data?
Crates.io does have some values we've tried to cache, and have had problems invalidating the cache at the right time in the right ways. We're now dynamically calculating the max_version of a crate and that seems to be performing okay.
Version downloads, however, are still being aggregated by a background worker script-- version downloads get updated in one table within a download request, then the background worker rolls up those counts to a downloads field on the versions table, on the crates table, and finally on a total_downloads field in the metadata table. I'm a little nervous about getting rid of this script because of postgres locking, since download requests are what happen most often.
Is any of that helpful...?

@carols10cents sorry, I should have written more, sigh.
The way that thanks currently works is basically by mirroring a git db as a postgres db. i was thinking maybe instead, keeping a local git repo on the dyno would work instead.
Given crates.io has to deal with the index, I thought maybe it had it locally, but that could be wrong...

Do you mean calculating commits, contributions, etc. in memory from the Github API responses?

or from a local git repo.

Aha, i see. Yes, crates.io does have a local checkout of the git repo on heroku -- this code sets it up. GIT_REPO_CHECKOUT is set to /app/tmp/index-checkout on crates.io and staging, and I have it set to ./tmp/index-co on my mirror that also runs on heroku, and both seem to be working fine.
As long as you don't expect that directory to be the same across dyno instances or through restarts (that code checks out the git repo on server start if it's not there), then it should be fine.

Here's the official heroku docs

As long as you don't expect that directory to be the same across dyno instances or through restarts (that code checks out the git repo on server start if it's not there), then it should be fine.

We will never have more than one instance, and even then, can make it work regardless 👍

Actually, @boxtown let me give some stuff a try first, and then we can decide what to do here 😄

👍
On Apr 5, 2017 3:18 PM, "Steve Klabnik"<EMAIL_ADDRESS>wrote:

Actually, @boxtown https://github.com/boxtown let me give some stuff a
try first, and then we can decide what to do here 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/thanks/issues/15#issuecomment-291967583,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACwkvmQZ_xo9a8OTr8GRznmXjnd67Lctks5rs-kbgaJpZM4LiSko
.

@boxtown so yeah https://github.com/rust-lang-nursery/thanks/pull/99
basically, after this merges, this specific issue can be closed; https://github.com/rust-lang-nursery/thanks/issues/13 would always get all the commits, since we're doing it from git natively.
i'm not closing this yet because i haven't actually landed that PR.


si7006 temperature conversion offset missing

The si7006 sensor driver (./drivers/sensor/si7006/si7006.c) is missing an offset as described in the datasheet. An offset of 46.85 should be subtracted in order to get the temperature in degrees Celsius.
#19941 attempts to fix it along with some unrelated changes.

@anthonybrandon would you mind reviewing and testing #19941 to see if we can move it forward?

@carlescufi
Sure, I have a board I can try it out on.
Do I just report it in a comment on the merge request once I have tried it, or did you mean something else?

@carlescufi
Sure, I have a board I can try it out on.
Do I just report it in a comment on the merge request once I have tried it, or did you mean something else?

Yep, just approve the Pull Request and add a comment there.

Fixed by #24563


Mac Silicon installation issues

Hi Guys,
after upgrading rust and creating a virtual environment for dbt with python 3.8 I can install dbt-extractor using pip install .
The problem is I get the error:
(dbt-env) > $ /Users/jorge/.venv/dbt-env/bin/dbt --version                                                                                [±main ✓]
Traceback (most recent call last):
File "/Users/jorge/.venv/dbt-env/bin/dbt", line 5, in
from dbt.main import main
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/main.py", line 13, in
import dbt.task.build as build_task
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/task/build.py", line 1, in
from .run import RunTask, ModelRunner as run_model_runner
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/task/run.py", line 8, in
from .compile import CompileRunner, CompileTask
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/task/compile.py", line 2, in
from .runnable import GraphRunnableTask
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/task/runnable.py", line 54, in
from dbt.parser.manifest import ManifestLoader
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/parser/init.py", line 8, in
from .models import ModelParser  # noqa
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt/parser/models.py", line 11, in
from dbt_extractor import ExtractionError, py_extract_from_source  # type: ignore
File "/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt_extractor/init.py", line 1, in
from .dbt_extractor import *
ImportError: dlopen(/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt_extractor/dbt_extractor.cpython-38-darwin.so, 0x0002): tried: '/Users/jorge/.venv/dbt-env/lib/python3.8/site-packages/dbt_extractor/dbt_extractor.cpython-38-darwin.so' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')), '/usr/local/lib/dbt_extractor.cpython-38-darwin.so' (no such file), '/usr/lib/dbt_extractor.cpython-38-darwin.so' (no such file)
Any ideas ?

@jomach We highly recommend you install dbt on M1 Macs via Homebrew + Rosetta, following the outline here: https://hackernoon.com/apple-m1-chip-how-to-install-homebrew-using-rosetta-su12331b. It's how I've been using dbt on my M1 Mac for a few months now, and it's been working without a hitch.
We use GitHub Actions to build wheels for this package on different system architectures. We aren't yet able to build wheels for Mac silicon architectures, because GHA does not yet support it as a runner: https://github.com/actions/virtual-environments/issues/2187


entry "www."

In https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling/hosts, there is a host listed simply as 'www.'   Is this a typo? It is the only entry in their without a domain (or without a host, depending which way you look at it).

damson$ wget -q -O - https://raw.githubusercontent.com/StevenBlack/hosts/master/alternates/fakenews-gambling/hosts | grep -n ' www\.$'
101943:<IP_ADDRESS> www.
damson$

Thank you for this Alexis @alexishuxley.
This is a bug! I have reported this upstream at https://github.com/FiltersHeroes/KADhosts/issues/84.
Our own domain parsers should have caught this.

i use this block list on my fortigate firewall and i was having all kinds of problems accessing tons of sites like
www.amazon.com
www.etsy.com
www.google.com
www.reddit.com
and so on. as soon as i disable this list
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
the issue goes away, so i am sure it is linked with the erroneous "www." entry

Fixed!  Closing!

Try it now @wallacebrf.

Try it now @wallacebrf.

just updated the lists and everything seems to be working now!


Draw lines, boxes

Weekend airplane project. Must be useful for something, right?
IBA::render_point() draws a single pixel.
IBA::render_line() draws a line segment between two designated pixels (it    can easly be used for one segment of a poly-line, with an option to avoid    rasterizing the first point, so polyline vertices are not double-drawn).
IBA::render_box draws a filled or unfilled box between the two diagonal corner pixels.
oiiotool --line x1,y1,x2,y2,... draws a polyline
oiiotool --box x1,y1,x2,y2 draws a box

After sending the first PR last night, I decided we really did need IBA::render_box(), so I added that.


How to set CMAKE_TOOLCHAIN_FILE

such as:
    externalNativeBuild {
        cmake {
                arguments "-DCMAKE_TOOLCHAIN_FILE=../../cmake/my_android.toolchain.cmake"
        }
    }

I know, it must use an absolute path

oh,  it duplicated.
-DCMAKE_TOOLCHAIN_FILE=/Users/dpull/Library/Android/sdk/cmake/3.6/android.toolchain.cmake
-DANDROID_NATIVE_API_LEVEL=21
-DTARGET_PLATFORM_VERSION=18
-DANDROID_TOOLCHAIN=clang
-DCMAKE_TOOLCHAIN_FILE=/.../Test/Android/app/src/android.toolchain.cmake

Duplicating should be fine. We use our own toolchain file. If you want to use a different one, what you're doing here should work. Appending the argument should just override the previous CMAKE_TOOLCHAIN_FILE.
Be aware that you're on your own if you run into problems with your own toolchain file.


Fix parens for functions inside TaggedTemplateExpression

Fixes #244 (again)
Sorry for missing this one!

Yay thanks!


Allow JRuby to run Rakefile and compile Java bits + libparser.so

Does two things for JRuby run to run Rake:

ruby_memcheck is not supported by JRuby so we need to exclude it.
uses rake-javaextensiontask to compile java/* files.

Bonus:

gitignore generated compile.jar

This minimally allows me to verify Java files compile and to generate the lib/rubyparser.{so,dylib,dll}.  Longer term I would like JRuby to be able to properly build and test the gem without having to rely on MRI to run Rake.

lol.  I guess I used main from my fork and not from this repo.  I will reopen this again with newer Rakefile.


test: adding oncluster builds e2e tests for s2i supported runtimes

Changes

:gift: Oncluster builds tests for s2i supported runtimes
:bug: Fix s2i task when build env array is empty for node functions

/kind cleanup

wating for #1234

/cc @zroubalik @lance


HDDS-7448. Upgrade RocksDB to 7.7.3

What changes were proposed in this pull request?
RocksDB 7.7.3 includes a important bug fix.
https://github.com/facebook/rocksdb/issues/9423
The minimum version includes this fix is 7.5.3, but CI is OK with RocksDB 7.7.3.
I wish this fix can be included in the 1.3.0 release.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-7448
How was this patch tested?
https://github.com/kaijchen/ozone/actions/runs/3369331676

If 7.7.3 is too aggressive, we can use 7.5.3 instead.

If it is to be included in 1.3.0, has it been stress tested under load?

Thanks @jojochuang for the review.

If it is to be included in 1.3.0, has it been stress tested under load?

I have run several tests (about 1TB data), and it looks good.

Fix FIFO compaction causing corruption of overlapping seqnos in L0 files due to ingesting files of overlapping seqnos with memtable's under CompactionOptionsFIFO::allow_compaction=true or CompactionOptionsFIFO::age_for_warm>0 or CompactRange()/CompactFiles() is used. Before the fix, force_consistency_checks=true may catch the corruption before it's exposed to readers, in which case writes returning Status::Corruption would be expected.

We do use CompactRange() API in Ozone. So watch out.

Looking into the commit for the fix https://github.com/facebook/rocksdb/commit/fc74abb436c5807e967aecc892bb8fa127f2fa85, I'm not sure if this problem is introduced in recent releases. It might exist at the current version (7.4.5) we are using as well.

Please pay attention to commit message when merging PRs.  Also, please update Jira issue (status, fix version).

Thank you @adoroszlai and @kaijchen for the commit.


Replace myself as a Dart maintainer

@athomas has volunteered to be an owner for the time being.

Thanks for all your hitherto contributions!


How to suppress CA2007 Warning!

Documentation said:

You can suppress this warning if you know that the consumer is not a graphical user interface (GUI) app or if the consumer does not have a SynchronizationContext.

But did not tell how to suppress this.  Would any anybody tell how can I suppress this in ASP.NET Core Application from .editorconfig?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02d637a6-6f73-c865-94ea-28ca5d9861a0
Version Independent ID: df24f234-848f-e04c-488d-6b6346e51fa6
Content: CA2007: Do not directly await a Task - Visual Studio
Content Source: docs/code-quality/ca2007-do-not-directly-await-task.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @gewarren
Microsoft Alias: gewarren

@TanvirArjel  Thank you for the question.
Does manually configure rule severity not apply?
Assigning this to the author now.

@msebolt Thank you. Your specified link helped me. I have done this as follows:
[*.cs]
dotnet_diagnostic.CA2007.severity = none

It should have been mentioned in this documentation.

@TanvirArjel Thanks, that is a good suggestion.

As asp.net core applications do not have a context, this warning should not be on by default for asp.net core.

The document needs to be changed.  It says to use:
dotnet_code_quality.CA2007.exclude_async_void_methods = true which does not disable the warning.
The correct syntax is:
dotnet_diagnostic.CA2007.severity = none

@udlose Looks like exclude_async_void_methods only excludes asynchronous methods that don't return a value, and is not the general way to suppress the warning (for which, as you mentioned, the correct syntax is:
dotnet_diagnostic.CA2007.severity = none).
If exclude_async_void_methods is not working, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.
The original issue mentioned by @TanvirArjel applies to most or all of the warnings topics, not just this one. However, there is a link to the .editorconfig topic already at the end of the Configurability section.

if the analyzers were written correctly, they would take the type of assembly they are used in into account and USERS would not have to suffer from YOUR screwups, but hey that why you don't have REAL developers on your staff right, otherwise YOUR staff would be the ones finding all the bugs instead of END USERS WASTING TIME REPORTING YOUR SHIT. How many "features" have you produced that have NO regression and where bugs are not still open after 10 years because YOU don't think they matter????? that'ts right NONE!!!!!! you can't even apply your own coding rules


Implemented a js-only distribution

Refactored the assembies to allow js-only distributions.

Hi Chris, I tested both with/without SWF and all works well except IDE SDK compiling with js-only version. option-with-swf continues to work in all cases. I'm going to merge since it the issue is just for the new js-only distribution when compiling from IDE. Thanks for doing it! :)

@carlosrovira Could you please drop on the list email with exact steps how to run both swf/js distribution build? I know there were some instructions in the other threads, but summary would be awesome. Thanks!
Thanks @chrisdutz !

Hi Piotr, I already updated the main wiki page with actual info :). All is here:
https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven
with this change you now can avoid "option-with-swf" profile for a JS-only build (no SWF). I'll update wiki page as soon as we fix the JS-only compilation with IDE.
Please, let me know if you see some issue in that page in order to update that page

Just fixed the issue with IDEs. It was just a matter of copying frameworks/libs to distribution.
Thanks Chris again for all the work done to get this JS-only maven distribution SDK!! :)

Just fixed the issue with IDEs. It was just a matter of copying frameworks/libs to distribution.
Thanks Chris again for all the work done to get this JS-only maven distribution SDK!! :)

I still didn't check any of that with Moonshine, unless you did that by saying IDEs ?

Hi Piotr,
no, just tested with VSCode. My point is that if VSCode recognize Maven distribution as SDK, and was able to compile TDJ with it successfully then Moonshine should do that too, right?


Classes/methods vs top level functions source ordering limitations

Acton Version
<IP_ADDRESS>21<IP_ADDRESS>
Steps to Reproduce
def bar(f: Foo):
    pass

class Foo:
    def foo(self):
        bar(self)

Expected Behavior
Success!
Actual Behavior
Building project in /home/ddjoh/workspaces/act-test-1
  Compiling mod1.act for development

ERROR: Error when compiling mod1 module: Compilation error
 1:12-14
  |
1 |def bar(f: Foo):
  |           ^^^
Name Foo is not in scope

A workaround is to use a class staticmethod instead of a top-level function, e.g:
class Bar:
    @staticmethod
    def bar(f: Foo):
        pass

class Foo:
    def foo(self):
        Bar.bar(self)

The provided code now compiles just fine. We did loosen up the constraint on ordering of definitions which is probably what solved this. Closing.


Installation fails on Ubuntu 14.04.1 Trusty Tahr

The rsync step fails to copy up the vagrant directory complaining about too many attempts to log in.

Don't have access to http://storage.core-os.net/coreos/ , Who can give me a file coreos_production_vagrant.box Send to my email<EMAIL_ADDRESS>

Closing due to inactivity.


Better template errors

Template dispatcher should return error details instead of panicking
Should enable the invoke result to return something like
#[derive(Clone, Debug, Decode, Encode)]
pub struct InvokeResult {
   success: bool,
   output: Vec<u8>,
   error: String
}

Closed in #247


unzip_requirements leaves /tmp in a bad state

Hello!  🎈
The symptom of the problem I'm seeing is that on the initial boot of Lamba, some modules will fail to load due to missing files (different modules and files most times). The hot instance is then unusable until it's restarted. This happens randomly on a service with maybe one or two concurrent instances with a very low request load, producing failures about once a week.
I thought I was able to trace this down before to a requirements archive that would inflate to just short of the 500 MB /tmp mount limit without throwing disk space errors.
Reducing the uncompressed size of the archive has reduced the frequency of failures, but this issue persists with an archive that's well within the variability of the extracted package.
I don't think my python-requirements or serverless setup are unreasonable, but I'll post them here for good measure.
package
"serverless": "^1.26.0"
"serverless-python-requirements": "^3.1.1",

python requirements config:
pythonRequirements:
    fileName: requirements.txt
    dockerizePip: non-linux
    zip: true

requirements.txt
dill==<IP_ADDRESS>
numpy==1.13.1
pandas==0.20.3
PyMySQL==0.7.11
python-dateutil==2.6.1
pytz==2017.2
raven==6.5.0
raven-python-lambda==0.1.4
scipy==0.19.1
scikit-learn==0.19.1

The whole zip file is 114.95 MB compressed. The .requirements.zip inflated is anywhere from 396 MB (extracted locally) to 416 MB (measured on the lambda). I also can't explain the reason for the large size discrepancy between my local (OSX) file system and AWS.
Even worse, my space usage measurements for unzipping fluctuate (5%) without impacting the functionality of the service.

TL;DR
What can be done to improve the reliability of the unzipping process?
Or this an AWS problem?
Thanks!

That should be addressed by #150, which I merged yesterday. It'll be in the 4.0.0 release. I'll probably cut a 4.0.0-beta.2 soon.


Polish remote customization implementation

Some customization options were not configured, and a few values were assigned to the wrong fields. This fixes them.

!merge


New aka.ms link

Aka.ms link name
assessments
Category (Optional. Select None to auto-select)
None

Thank you for submitting aka.ms/assessments. Your link already exists at akaSearch.net. 🙏✅


Pin to SHA in README Examples

See https://github.com/secret-scanner/action/pull/15#discussion_r932640317

Hi @jsoref I see that you just force pushed to this.
Since landing in England things have been a bit hectic and I just started the new job so I don't think that I will be doing anything on this project for the next little while!

Hi @bgolding355. I hope you enjoy England.

@jsoref this doesn't seem to be going anywhere and want to get rid of this notification in the Pull Requests tab. Feel free to reopen if you want to do something with this