Platform and Optimization extensibility

Hi,
I'm currently working on a project where I need to add more platforms and optimizations. However, I'd like to do this without requiring code changes to Sharpmake.Platform and Sharpmake.Optimization.
Please do you have any suggestions or best practices for achieving this? Any advice would be greatly appreciated.
Thank you!
Best regards,
Cesar

Hi,
Which platforms do you want to add? If this is for consoles support, you will need to get platforms code from their respective console makers forums.
As for optimization for your project, what you need to do is define an optimization fragment
namespace MyEngine
{
    [Fragment, Flags]
    public enum Optimization
    {
        Debug = 0x01,
        SuperAwesomeDebug = 0x02,
        Release = 0x04,
        Profile = 0x08,
        QCFinal = 0x10,
        Final = 0x20
    }
    public class Target : ITarget
    {
            public Platform Platform;
            public Optimization Optimization;
            public BuildSystem BuildSystem;
            public DevEnv DevEnv;
            // Plus any other fragments/properties
    }

}

And then you use your Target type in your projects.
See this:
https://github.com/ubisoft/Sharpmake/wiki/Custom-Targets

Thank you very much for the prompt response and the suggestion to define our own optimization fragment and reference it from a custom target.
Is it possible to do something similar to extend Sharpmake.Platform? I'm afraid it is not possible because the 'Sharpmake.Platform' type is referenced by Sharpmake.Configuration.
The platform I would like to add is XBox Series X. But I would be more interested in being able to add more platforms in general without requiring code changes in the Sharpmake codebase. Either through some plugin DLL or other form of extension that could be included outside the Sharpmake codebase. Is that currently possible?
Thanks a lot for your kind attention!
Best regards,
Cesar

If you want to add XBox, I guess you got the sharpmake code for the XBox platform from the forums?
Each non public platform use a _reservedXX value from Platform enum. Public platforms use the real value defined in that enum.
I am curious about what platform you want to add.

Interesting, thanks again for the prompt response!
But then let's say, if I wanted to keep adding support for new reserved platforms, should I manually copy and paste each one from the forums and merge into my own custom version of Sharpmake\Target.cs? If that's the case, I wonder if we could help implement an extensibility approach that is more pluggable? Maybe some helpers to provide a custom enum from outside the Sharpmake codebase?
Thanks!
Best regards,
Cesar

If you need some platform support, you should get those platform code modules from the forums and include them into your SharpmakeExtended solution.
There is some doc regarding platforms here:
https://github.com/ubisoft/Sharpmake/blob/main/docs/Platforms.md
There is some doc regarding how to setup a SharpmakeExtended solution here:
https://github.com/ubisoft/Sharpmake/blob/main/README.md
I will paste some code here to show you how to integrate those platforms in your code but will obfuscate the platform name as the platform owners don't let us put their platform in Sharpmake public code.
We have a platform class for all consoles(XBox, PSX, switch). This is annoying but each of those platform code is only available in forums. This is not our choices. Ideally all platforms support would be in github. Sharpmake is after all only a glorified xml/json generator.
Here are some example on how we are using some of those platforms. I just renamed the real platform name. Apart from the name change, this is pasted from our actual production code.
Here is some code for a platform called "SomeAnonymous". Each non public platform defines a SharpPlatform constant borrowing one of the reserved values(each using a unique value).
    public static partial class SomeAnonymousPlatform
    {
        public const Platform SharpmakePlatform = Platform._reserved7;
....
    }

Then in our code we are doing things like
public static Target[] GetEngineTargets()
{
      var result = new List<Target>();
      result.Add(new Target(
                        SomeAnonymousPlatform.SharpmakePlatform,
                        GetDefaultDevEnv(),
                        GetDefaultEngineOptimization(),
                        OutputType.Lib,
                        Blob.Blob,
                        Mode.Engine,
                        BuildSystem.FastBuild));
      return result;
}

We can use in in Configure methods in Configure attribute also do in our projects:
``
class SomeProject : CommonProject
{
[Configure(SomeAnonymousPlatform.SharpmakePlatform)]
public void ConfigureAnonymousPlatform(Configuration conf, Target target)
{
//....
}
}
I hope this clears everything out.

Yes, those resources solve my needs completely. Thank you very much for your extensive help and congrats for the great work!
Best regards,
Cesar


[Bug]:  docker compose project name

Description
no docker compose project name is being set so it is using the file name which is source and doesn't really show what it is.
i have something like 30 project running and this offputing.
fix is either add -p coolify to docker compose up or add COMPOSE_PROJECT_NAME=coolify to the env
Minimal Reproduction (if possible, example repository)
NA
Exception or Error
No response
Version
V4

Docker Compose support is not yet available in v4. How (or why) do you use it?

sorry i should have explained it more this the docker compose stack name that coolify uses to deploy coolify, postgresql and redis.
its done using this compose file.
https://github.com/coollabsio/coolify/blob/main/docker-compose.yml

Sorry, but I still don't get it. Can you please rephrase your problem?
By the way, composd support is available for a few days.

as document in link below shows --project-name is used to set the project name when running a docker compose file
https://docs.docker.com/compose/reference/#command-options-overview-and-help
currently coolfiy's start script just calls
docker compose -d
which means if your call docker compose ls coolify will be listed as
source              running(3)                  /data/coolify/source/docker-compose.yml,/data/coolify/source/docker-compose.prod.yml
because the project name was just chosen from the dir  that the compose is in which is source.
but if docker compose is called like
docker compose -p coolify -d
it would look like
coolify              running(3)                  /data/coolify/source/docker-compose.yml,/data/coolify/source/docker-compose.prod.yml

this is for the coolify stack its self none of the things it runs

Due to inactivity, I'm closing this issue. However, if the problem persists, please reopen the issue. Thanks!


Update Model API

Description
This PR should enable model updating through model update API
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Do we undeploy the model when updating it? I think we should do it.

Nice catch. This should be further discussed.

Tests are failing..

Tests are failing..

Hmmm...let me check

Do we undeploy the model when updating it? I think we should do it.

We will undeploy the model.


Add yanix crate and replace nix with yanix in wasi-common

This PR adds yanix crate as a Unix dependency for wasi-common. yanix stands for Yet Another Nix crate and is exactly what the name suggests: a crate in the spirit of the nix crate featuring certain adjusments and additions tailored specfically to its main application area which are implementation of WASI syscalls.
This PR also makes the necessary changes to wasi-common to depend only on yanix crate.
I apologise for the largeness of the PR! I've kept it as two orthogonal commits for easier reviewing, so I hope that helps somewhat.
This PR is a successor and hopefully an improvement of #640 and is the first of addressing #520.

cc @marmistrz

In terms of style and how to organize this, my personal preference is to do what the standard library does. There's a crate that has a cross-platform API, and then internally it's got a sys module that's entirely different per platform, but all platforms provide the same API to use in this platform-specific implementation module.
I don't get the feeling this PR is quite like that, but I don't think that's necessarily a bad thing. It's a reflection of reality as it is today and I think that's fine, incremental improvement is always good!
In that sense I mostly just want to comment about how I don't think this is the best organization we can have long-term, but I also don't want to block this in any way!

In terms of style and how to organize this, my personal preference is to do what the standard library does. There's a crate that has a cross-platform API, and then internally it's got a sys module that's entirely different per platform, but all platforms provide the same API to use in this platform-specific implementation module.
I don't get the feeling this PR is quite like that, but I don't think that's necessarily a bad thing. It's a reflection of reality as it is today and I think that's fine, incremental improvement is always good!
In that sense I mostly just want to comment about how I don't think this is the best organization we can have long-term, but I also don't want to block this in any way!

Thanks for the feedback! Yep, personally, I'm also a fan of the libstd's style. However, initially I wanted to keep yanix closer to nix organisation-wise in order to be able to compare which functionality is needed and which one is not, I assumed their style. Having said that, I'm all for rewriting it using the libstd style, however, I'd do it incrementally just as you suggested, and roll out the changes gradually in the subsequent PRs. Does that sound fair?

👍
definitely sounds good to me!

👍
definitely sounds good to me!

In the end, I've decided to the reorg in this PR since there were some other outstanding things to sort out. This, however, meant that it was easier to do the reorg by pulling in #650 into this PR which is less than ideal, but hopefully not a complete deal breaker.


Add Wethio network (ZYN)

Description

[X] Symbol: ZYN
[X] ChainId: 78
[X] Website: https://wethio.io/
[X]  Block-Explorer: https://explorer.wethio.io/
[X] slip-0044 type: 77777

Additional comments
First PR #104

@cseguret-ledger Should we create a new Pull Request to add Wethio network on the ledger app ?

This has already been added here: https://github.com/LedgerHQ/app-ethereum/pull/289


Includes latest swagger updates for :

New models for different message types (xml=>json)
Updates on nullability for attributes (readonly/required changes in swagger)
Updates in test.

/azp run net - communication - ci

/azp run net - communication - ci

Rebasing nightmare, will recreate this branch and link the previous comments @RezaJooyandeh

Rebasing nightmare, will recreate this branch and link the previous comments @RezaJooyandeh


Add samples "Hungryman" and "Spring SMTP Gateway"

Add "Hungryman" and "Spring SMTP Gateway" samples.
Tasks for each sample:

Add/Change license file to MIT-0 license (same as in the root of this repo)

Notes for VMware contributors:

see https://github.com/vmware-tanzu/application-accelerator-samples/blob/main/CONTRIBUTING.md
must be member of vmware-tanzu org to avoid CLA issues - https://cla.vmware.com/employee
sign commits

To acknowledge the Developer Certificate of Origin (DCO), sign your commits by adding Signed-off-by: John Doe<EMAIL_ADDRESS>to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author.

PRs for these changes.  Although the "main" branch is not being pulled into a specific accelerator (only branches), a LICENSE file has been added to the main branches.
https://github.com/sample-accelerators/hungryman/pull/2
https://github.com/sample-accelerators/hungryman/pull/1
https://github.com/sample-accelerators/spring-smtp-gateway/pull/5
https://github.com/sample-accelerators/spring-smtp-gateway/pull/4
@trisberg Please review.


Persist open state for list items during session

Is your feature request related to a problem? Please describe
This is a follow up of: https://github.com/bpmn-io/properties-panel/issues/86
Introducing #86, list items are completely unique per id. Therefore they have their own state depending on what element is selected. Since the items are unique per id, they got rerendered when a new element got selected.+
That causes that the state got lost when switching from one element to another and switch back again (the item is closed, no matter it was opened after the switch).

Describe the solution you'd like
For a smoother editing experience and to avoid opening list items multiple times during element switches, it should be possible to persist the opened state per item during a session (or multiple sessions).
We have the LayoutContext which was meant for exactly this purpose, but we are currently not using it.
Describe alternatives you've considered

keep things as they are
next to list items state, we could potentially persist any other layout changes (cf. bpmn-io/bpmn-properties-panel#61)
persist layout not only during runtime, but also make it possible to persist them anywhere, cf. propertiesPanel.layoutChanged.

Additional context
Cf. #86

A sketch of how to use the LayoutContext to persist the open state (cf. this branch)
import {
  useContext,
  useMemo,
  useState
} from 'preact/hooks';

import {
  LayoutContext
} from '../../context';

export default function CollapsibleEntry(props) {

  const {
    // ...
    open: shouldOpen
  } = props;

  const {
    layout,
    setLayoutForKey
  } = useContext(LayoutContext);

  const layoutKey = useMemo(() => {
    return `collapsible-${id}`;
  }, [ id ]);

  const collapsibleLayout = layout[layoutKey] || {};

  const [ open, setOpen ] = useState(shouldOpen || collapsibleLayout.open);

  const toggleOpen = () => {
    setOpen(!open);
    setLayoutForKey(layoutKey, {
      ...collapsibleLayout,
      open: !open
    });
  };

  // ...
}

Open for discussion: how should the layout API look like? how should the props be stored?

Open for discussion: how should the layout API look like? How properly store the data inside the context?


IoT Central support for Microsoft Modbus desired properties

Hello,
I have set up an IoT Edge device connected to IoT Central. One of the modules connected is a Microsoft Modbus device (taken from the marketplace).
These are the initial Modbus module desired properties:
        "Modbus": {
            "properties.desired": {
                "PublishInterval": 100,
                "SlaveConfigs": {
                    "Slave01": {
                        "SlaveConnection": "<IP_ADDRESS>",
                        "HwId": "Wise01",
                        "Operations": {
                            "Op01": {
                                "PollingInterval": "100",
                                "UnitId": "1",
                                "StartAddress": "00131",
                                "Count": "1",
                                "DisplayName": "IFM00"
                            }
                        }
                    }
                }
            }
        },

If I import the deployment manifest, the import succeeds:

I do not change anything to the interface afterward.
Also, the deployment and the first connected device perform well. Here is the Manage page:

But, when I want to change the IP address in the IoT Central portal, the Modbus module desired properties update fails:

It seems the desired properties sent are not matching that what the code is expecting.
Can you confirm this behavior? Is there a workaround?

@sandervandevelde - can you share the model you are using in IoT Central. It appears that it does not match the desired properties you have listed above.


skipping APR integration tests

When external data token yield sources are down tests are failing. We might be better off with unit tests only.

Do we intend to use this tests again in the future? If not, isn't it better to remove them entirely?

good point, we might just remove it

yeah - I approved and merged so I could get the other pending PRs merged, but I think it would be nice to remove these unused tests eventually.


Update to 4.3.18

https://access.redhat.com/errata/RHBA-2020:1529
curl -s -H "Accept: application/json" https://api.openshift.com/api/upgrades_info/v1/graph?channel=stable-4.3 | jq '.nodes[] | select(.version == "4.3.18")'
{
  "version": "4.3.18",
  "payload": "quay.io/openshift-release-dev/ocp-release@sha256:1f0fd38ac0640646ab8e7fec6821c8928341ad93ac5ca3a48c513ab1fb63bc4b",
  "metadata": {
    "description": "",
    "io.openshift.upgrades.graph.release.channels": "candidate-4.3,fast-4.3,stable-4.3,candidate-4.4,fast-4.4,stable-4.4",
    "io.openshift.upgrades.graph.release.manifestref": "sha256:1f0fd38ac0640646ab8e7fec6821c8928341ad93ac5ca3a48c513ab1fb63bc4b",
    "url": "https://access.redhat.com/errata/RHBA-2020:1529"
  }
}
oc adm release info quay.io/openshift-release-dev/ocp-release@sha256:1f0fd38ac0640646ab8e7fec6821c8928341ad93ac5ca3a48c513ab1fb63bc4b | grep must
  must-gather                                   sha256:2e10ad0fc17f39c7a83aac32a725c78d7dd39cd9bbe3ec5ca0b76dcaa98416fa

/azp run e2e

| On Monday, we'll push out 4.4.2 along with a fast channel edge from 4.3.18 -> 4.4.2.


feat(tutorial): complete step 5

Link to deployment
 carbon-tutorial-disput.mybluemix.net
Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

link added


file.Lines returns slices of length 0xAAAAAAAAAAAAAAAA

Looks like the length field of the slice is left uninitialized?
$ icarus repro.ic
length:<PHONE_NUMBER>2473034410: file ::= import "file.ic"
length:<PHONE_NUMBER>2473034410: io ::= import "io.ic"
length:<PHONE_NUMBER>2473034410:
length:<PHONE_NUMBER>2473034410: file.With("repro.ic") open [f: file.File] {
length:<PHONE_NUMBER>2473034410:   file.Lines(f) each [line: []char] {
length:<PHONE_NUMBER>2473034410:     io.Print("length: ", line.length, ": ", line)
length:<PHONE_NUMBER>2473034410:   }
length:<PHONE_NUMBER>2473034410: }
length:<PHONE_NUMBER>2473034410:

Yes, we write 0xAA bytes in debug mode into memory that would be uninitialized in opt-mode, so this is a bug in the IR-generation. We're likely reading the register holding the length but never wrote to it.
To clarify, it's reading the file correctly just the length is wrong? Meaning the call to printf("%*s", ...) likely is getting lucky regarding null terminators.

Yup, the printing must be hitting the null byte and stopping, rather than trying to print all 0xAAAA... bytes.

This bug is relatively new, by the way, because the length was initialized properly back when I wrote my day 9 advent solution. I suspect it popped up in the last week or two's changes.


Uncaught (in promise) TypeError: get_document(...).createElement is not a function

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Can't load atom core package for development.
Steps to Reproduce

git clone https://github.com/atom/atom.git
cd atom
apm link -d
atom --dev

Also tried apm install.
Expected behavior: Atom to load.
Actual behavior:

Reproduces how often: Every time.
Versions
Atom    : 1.21.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
Ubuntu 16.04.03

Atom itself is not a package, therefore you aren't supposed to run apm link -d on it.  Set ATOM_DEV_RESOURCE_PATH to where your Atom git repository is located, execute script/build --install, and then run atom -d.


fix reconnection logic

i was having issues with irc reconnecting, it would attempt once, if the connect failed, Loop would return and my bot would close, which was frustrating.
i assumed the intention was to attempt to reconnect infinitely, i havnt tested all cases...

one of my changes is probably redundant, little mis understnading of the logic, that is sending on irc.end so that the go routines would finish (as was implemented in PR #29)... i wasnt seeing them end on my machine when testing... maybe im crazy


Fix the broken link to Medium

This link has already been updated on the next branch so I will close this PR. Thanks for your contribution.


Update "get started" link on page to point to this repo

Right now the user will get a 404, but I think the main page of the repo with the "readme" is a good starting point. So we just need to update location.href to the main repo github address. Can we make the link using an <a> instead of a button? I didn't look closely enough at the styling to see if that would work. It would be better semantic HTML (make a link out of a <a> tag instead of a button).

I just fixed this :)

Nice, it's live on the main page now, thanks!


Add support for lock_version rename

version is going to be renamed to lock_version in https://github.com/alphagov/publishing-api/pull/206.

Talked to @tuzz, and they will change lock_version back to version, so closing this PR.


Auto-incrementing citation key?

I wonder if I could make a feature request.
I have a database that originally began in RefWorks.  There, the citation keys were just an ID number that would increment by 1 each time a reference was added.   It's a simple system, but I've stuck with it ever since (migration to JabRef and now to Zotero), and actually kind of like it.
The question is, would it be possible to add such an auto-incrementing ID number for the citation key generator in BBT?  Ideally the option would force a scan of the existing ID numbers and would start with the next ID beyond the highest ID found.  I also wouldn't mind interacting with it as an option in the hidden menu (maybe specify a starting place for the ID number and it would just increment by 1 each time it is used).
Let me know what you think.

You should be able to get mostly there by just using [id] as a pattern. It
won't scan for existing entries, but existing entries should have gotten
pinned keys on import if you imported as bibtex, and the newer ones will
get the zotero-assigned internal id, which is unique to an installation of
zotero, usually consecutive, and the import should have taken the lower
numbers.
How on earth do you keep apart what you're citing though? I have some 3000
refs in Zotero, no frigging way I'd know what reference 1578 would mean in
a paper.

Thanks, indeed it is close!
Yes it is a good question :)  When citing, I likely wouldn't remember the exact citation key for a paper, so I don't think I'm loosing much just grabbing from Zotero.  Once inside, if needed, I can see what was cited just using the output references.  Readability of the TeX is not as great I'll admit though.  Might abandon this soon... kinda something I just held over from Refworks!  At least the key generation and lack of clashing is simple...

It makes me think Refworks wasn't really concerned with BibTeX users. I've never heard of meaningless citation keys as a desideratum.

Indeed.  Followup question, is there a nice way (existing database?) for handling journal acronyms in the BBT citekey generation?  For example, for "Proceedings of the National Academy of Sciences" the abbreviation would be something like "Proc. Natl. Acad. Sci. U.S.A.", but for the citekey you would want PNAS.

I think [journal:abbr] does that if you have a journal abbrev filled out (although it will probably turn into PNASU -- haven't tried). You can enable BBT auto-abbrev and it will use the abbrevs Zotero generates if you don't have one filled out, but they are of varying quality.

Nice thank you.  I will give it a look!


How to disable scroll animation with scrollTo()

Is there a way to disable scroll animation when I set scroll position with scrollTo()?
Like.. when I do .
this.$refs.Scrollbar.scrollToY(1000)

My window scroll to the position as if someone is scrolling to the location manually. Is there a way to disable it, and instead jump to the scroll location?

I've switched to use perfect-scrollbar - which works more like a native scrollbar.
npm install perfect-scrollbar --save

import 'perfect-scrollbar/css/perfect-scrollbar.css'
import PerfectScrollbar from 'perfect-scrollbar'

..

    data() {
        return {
            ps: null,
        }
    },

    mounted () {
        this.ps = new PerfectScrollbar(this.$el);
    },

    destroyed() {
        this.ps.destroy();
    },

You can remove the transition from the css file.


test(app-testing): Run App automation for end to end testing

Overview
Add the ability to drive the installed run app for the predominate purpose of end to end testing.

Use python, selenium(4), and pytest to execute tests against the installed run app.
Roughly use the Page Object Model
See Notes in README

Changelog
All new code with no dependencies outside of the new app-testing directory.
Review requests
@Opentrons/qa
@Opentrons/cpx
@Opentrons/app-and-uis
Risk assessment
There is no risk to any other module in the repository.  The app-testing folder is self contained.  It is included in monorepo because changes to the run app will coincide with test changes.  Open to this tool living in its own repository if that is preferred. The workflows added are proof of concept and are dispatch.

Linux run on Github Actions
MacOS run on Github Actions
Windows run on Github Actions
@sfoster1 @mcous would you prefer I remove the windows and mac dispatch jobs?

Windows is the beta version windows-2022, with at least 2 issues: a docker issue and the .exe path.
Mac works better but is slow and the tricky interaction with the system file dialog works locally but not on the runner, so 1 test fails.

@sfoster1 @mcous would you prefer I remove the windows and mac dispatch jobs?

Interesting idea. If we can still successfully run these locally, I'd be down to focus on getting Linux working well in CI and layering on macOS and Windows.

All Comments Resolved

took out pylint
took out windows and mac github actions dispatch workflows
working linux dispatch
updated electron version per edge
replaced * with versions in Pipfile

pinging @mcous and @sfoster1 for re-review.


Water doesn't light properly

Is this only visible when there are no player lights on?

probably fixed in soft shadow branch


add PORT envvar to nodejs example

supercedes #196
I also renamed the example to "nodejs" to better reflect the example application.

@bacongobbler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #291 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #291      +/-   ##
==========================================
+ Coverage   30.94%   31.05%   +0.11%
==========================================
  Files          28       28
  Lines        1771     1771
==========================================
+ Hits          548      550       +2
+ Misses       1144     1142       -2
  Partials       79       79

Impacted Files
Coverage Δ

pkg/linguist/linguist.go
34.61% <0%> (+1.28%)
:arrow_up:

Continue to review full report at Codecov.

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

looks good. just waiting till CI is green.


Does lookAt returns a left handed matrix 😲 ?

While writing this issue, I've got the strong feeling that I'm wrong and Filamant is correct ... but as always I'm up for a lesson. The docs, section 8.6 Coordinate Systems describes that Filament uses a right handed coordinate system +X = right, +Y = up, +Z = forward. Normally a camera looks into the negative Z right? Is this the difference with other right handed libs: that we look into the positive Z?
When I create a basic lookat matrix like using the code below, I get this result:
 1.00,  0.00,  -0.00,  0.00
-0.00,  1.00,  -0.00,  0.00
 0.00,  0.00,   1.00,  15.00
 0.00,  0.00,   0.00,  1.00

Using this test case.
#include <stdio.h>
#include <stdlib.h>
#include <math/mat4.h>

static void print_mat4(const char* title, filament::math::mat4& m);

int main(int argc, char* argv[]) {

  filament::math::mat4 m;
  filament::math::float3 p(0.0, 0.0, 15.0);
  filament::math::float3 t(0.0, 0.0, 0.0);
  filament::math::float3 u(0.0, 1.0, 0.0);

  m = m.lookAt(p, t, u);

  print_mat4("lookat", m);

  return 0;
}

static void print_mat4(const char* title, filament::math::mat4& mat) {

  printf("Matrix: %s.\n", title);

  double* m = (double*)&mat[0][0];

  printf("%2.2f, %2.2f, %2.2f, %2.2f\n", m[0], m[4], m[8], m[12]);
  printf("%2.2f, %2.2f, %2.2f, %2.2f\n", m[1], m[5], m[9], m[13]);
  printf("%2.2f, %2.2f, %2.2f, %2.2f\n", m[2], m[6], m[10], m[14]);
  printf("%2.2f, %2.2f, %2.2f, %2.2f\n", m[3], m[7], m[11], m[15]);
}

I've got a little repository where I compare different math libraries.  These are the results of other libraries using the same eye/target/up vectors.
Lookat matrices test with the GLM library (right handed)
---------------------------------------------------------
 1.00, -0.00,  0.00, -0.00
 0.00,  1.00,  0.00, -0.00
-0.00, -0.00,  1.00, -15.00
 0.00,  0.00,  0.00,  1.00

Lookat matrices test with the Songho library
----------------------------------------------
[  -1.00000    0.00000    0.00000    0.00000]
[   0.00000    1.00000    0.00000    0.00000]
[   0.00000    0.00000   -1.00000   15.00000]
[   0.00000    0.00000    0.00000    1.00000]

Lookat matrices test with the linmath library (right handed)
-------------------------------------------------------------
 1.00, -0.00,  0.00,  0.00
 0.00,  1.00,  0.00,  0.00
-0.00, -0.00,  1.00, -15.00
 0.00,  0.00,  0.00,  1.00

Lookat matrices test with the mathfu library (right handed)
--------------------------------------------------------------
 1.00, -0.00, -0.00,  0.00
 0.00,  1.00,  0.00, -0.00
-0.00, -0.00,  1.00, -15.00
 0.00,  0.00,  0.00,  1.00

The docs say:
"Filament's Camera looks towards its local -Z axis. That is, when placing a camera in the world without any transform applied to it, the camera looks down the world's -Z axis."
I'm not sure where you got the info that +Z is forward.

@romainguy I was a confused because of the result of the lookat function and because the caption under figure says +Z, but thanks for clearing that up.
But when the system is right handed and the camera looks along the negative Z shouldn’t the result be -15?

I see where the confusion comes from. Our lookAt returns the post (or model matrix/transform) of the camera, not what's commonly called the view matrix. If you want the view matrix, take the inverse of what lookAt computes and you'll get the same result as glm for instance.
print_mat4("lookat", inverse(m));

1.00, 0.00, 0.00, -0.00
0.00, 1.00, 0.00, -0.00
0.00, 0.00, 1.00, -15.00
0.00, 0.00, 0.00, 1.00

Thanks doesn't it make more sense to follow the convention regarding this?

I would dispute it's an actual convention but more importantly Filament APIs expect model matrices, not "view" matrices. We do have a Camera::getViewMatrix() for convenience and for people used to this terminology but you never set the view matrix yourself. You either call Camera::lookAt() or Camera::setModelMatrix() (all the former does is setModelMatrix(mat4f::lookAt(eye, center, up)) anyway).

Ah I see, thanks for explaining!


Update Server.ts

Not a required setting.

that's a wrong branch. I wont' be accepting changes to v3 sorry. Not gonna release it. I was planning to merge v4 to master soon.


Ability to send email for lost password ?

Hi,
I've played with the Docker image (cool !) and was unable to send any email (typically for a lost password).
Is the image able to send email ? Did I miss something ?
Thank you

Thanks!
Agree email is important for passwords and stuff.
I don't think we can configure email once and for all inside this docker image, since it requires server config and credentials.  The mail server should probably live out on the Internet somewhere, or at least in a different Docker image.
But I think you can mount in the necessary config when running this image.  I'm using gmail's free smpt service for one project, and the config looks like this:
/var/archiva/conf/jetty.xml
  <New id="validation_mail" class="org.eclipse.jetty.plus.jndi.Resource">
    <Arg>mail/Session</Arg>
    <Arg>
      <New class="org.eclipse.jetty.jndi.factories.MailSessionReference">
        <Set name="user">***</Set>
        <Set name="password">***</Set>
        <Set name="properties">
          <New class="java.util.Properties">
            <Put name="mail.user">***</Put>
            <Put name="mail.password">***</Put>
            <Put name="mail.smtp.host">smtp.gmail.com</Put>
            <Put name="mail.transport.protocol">smtp</Put>
            <Put name="mail.smtp.port">587</Put>
            <Put name="mail.smtp.auth">true</Put>
            <Put name="mail.smtp.starttls.enable">true</Put>
            <Put name="mail.debug">true</Put>
          </New>
        </Set>
      </New>
    </Arg>
  </New>

This makes an email resource available in the Jetty container.  Archiva knows how to find it from there.

Great, thanks !
Your excerpt would be a great help in the README for other users

Agree again.  Already put it there!  Thanks.


chore: switch to toml-select github action

Quick improvement
See https://github.com/marketplace/actions/toml-select-toml-field-extractor-action

Why on earth should this be changed to a package you control? It's not like the old one is out of date or doesn't get updates: https://github.com/SebRollen/toml-action
Is this some cybersec theatre?

Since your action is literally doing the same thing as the one we currently use, I don't see why we would change usage tbh.

I am not a maintainer, my opinions are my own. My harshness was to ensure this did not get merged without strong consideration as it has the potential to proliferate to a lot of projects.
Suggesting an open source project change to a package you maintain should come with much more explanation than "Quick improvement". I'm sure the contribution is appreciated but appears unnecessary in the current circumstances.
That's the last I'll say on this, sorry if my wording caused a minor headache maintainers.

Sure. Thanks for the apology. Nothing was hidden Ryan. Link to full description was provided very start.


Update docker-entrypoint.sh

Please answer these questions before submitting pull request

Why submit this pull request?

[X] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.

当我通过configmap将配置文件通过卷挂载的形式挂载到pod中时，配置文件是软连接，需要在cp时指定-L参数才可以

How to fix?

New feature or improvement

Describe the details and related test reports.

Please change your description to English.


bug:  Service alias pointing to service alias does not resolve in DNS

Rancher Version:
0.59.1
Docker Version:
1.10.2
OS:
centos
Steps to Reproduce:
Create a stack (stack1) with an external service (extsrv) pointing to  an IP
Create a second stack (stack2) with a service alias (alias1) pointing to extsrv on stack1
Create a third stack (stack3) with a service alias (alias2) pointing to alias1 on stack2
Add an ubuntu container to stack3 and open a shell
Try to resolve the name with a command like "ping alias2"
Results:
The service alias (alias2 in this example) cannot be resolved by name from a container in the stack containing this alias.
Expected:
You should be able to resolve alias2, and it should return the IP address in extsrv.

This is reproducible.  Easy way to do this is to create the external service, both service alias' and the ubuntu service in one stack.  The first service alias resolves, the second service alias cannot be found.

docker-compose.yml
alias2:
  image: rancher/dns-service
  links:
  - alias1:alias1
alias1:
  image: rancher/dns-service
  links:
  - externalService:externalService
externalService:
  image: rancher/external-service
ubuntu1:
  tty: true
  image: ubuntu:14.04.3
  stdin_open: true

rancher-compose.yml
externalService:
  external_ips:
  - <IP_ADDRESS>

@tfiduccia should be resolved in the latest.

Version - master 3/2
Verified fixed


PR: Install wheel in macOS build environment

Description of Changes
Install wheel in macOS standalone build environment
Issue(s) Resolved

Fixes #20834
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @mrclary

Installing wheel seemed to have fixed the issue, but I don't understand why. Perhaps @CAM-Gerlach has some insight?

FYI, @spyder-ide/core-developers, after removing the macOS and Windows standalone installer workflows from the master branch (since the will not be used for 6.x), the workflow_dispatch (manual trigger) no longer works. This is because workflow_dispatch must be present in the workflow in the master branch in order for it to be available for any other branch. This was an oversight of mine when submitting #20368.
We may want to discuss whether we want to retain some dummy workflows in the master branch just for this purpose, at least until development on 5.x is completely terminated.

the workflow_dispatch (manual trigger) no longer works

I think @dalthviz found a way to work around that.

We may want to discuss whether we want to retain some dummy workflows in the master branch just for this purpose, at least until development on 5.x is completely terminated.

You could just remove all the triggers but workflow_dispatch from the workflow in master?

I think @dalthviz found a way to work around that.

Oh what was that?

the workflow_dispatch (manual trigger) no longer works

I think @dalthviz found a way to work around that.

@dalthviz do tell!

installer-macos.yml and installer-win.yml no longer exist on the master branch; that is why the workflow_dispatch trigger does not work even though the workflows exist on 5.x.

Right—what I'm saying is in master, add them back but with only the workflow_dispatch trigger

Right—what I'm saying is in master, add them back but with only the workflow_dispatch trigger

Oh, sorry for the misunderstanding. Yes, I agree, this is what I meant by a dummy workflow.

It seems we are in violent agreement, then :)

Installing wheel seemed to have fixed the issue, but I don't understand why. Perhaps @CAM-Gerlach has some insight?

Hmm, well the proximate issue appears to be that without wheel in the local env, in the Install Dependencies step pip/Setuptools tries a PEP 660 isolated editable build and install relying on the pyproject.toml metadata, which we don't have (yet):
Obtaining file:///Users/runner/work/spyder/spyder
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Checking if build backend supports build_editable: started
  Checking if build backend supports build_editable: finished with status 'done'
  Getting requirements to build editable: started
  Getting requirements to build editable: finished with status 'done'
  Preparing editable metadata (pyproject.toml): started
  Preparing editable metadata (pyproject.toml): finished with status 'done'

With wheel it does what appears to be a non-isolated build, gets the metadata from the setup.py (where it is) and may use the legacy editable install method instead (not clear):
Obtaining file:///Users/runner/work/spyder/spyder
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'

I would have to dig a lot deeper (or ask the pip or Setuptools folks I know — the frontend-backend boundary here isn't totally clear from the available output) to figure out why exactly that is. Once I finally get to upgrading the packaging metadata for this repo, I can take a closer look for it seems this solution works for now.

Also, just FYI, in the Determine build matrix job, you need to change the line
echo "::set-output name=build_type::{'build_type':$(echo $build_type)}"

to
echo "name=build_type::{'build_type':$(echo $build_type)}" >> $GITHUB_OUTPUT

to avoid the warning (which will become an error in a month and a half:
Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

per this changelog entry.

@CAM-Gerlach, do you want to review this or are we okay?

Just in case, when doing the pre release steps for Spyder 5.4.3 I was able to run the workflows related with the installers by using the GitHub CLI, I did notice that the button to trigger the workflows was unavailable from the GitHub web interface but maybe using the GitHub CLI workarounds that since you can provide a ref from where to run the workflow? 🤔
Anyhow, I described the usage of the GitHub CLI for running the workflows here: https://github.com/spyder-ide/spyder/blob/5.x/RELEASE.md#check-release-candidate

Okay, I'll just add some dummy workflows back into master.

are we okay?

I think we're okay. This is a relatively simple change which will fix our CIs in 5.x, so let's merge it.


Use YAML instead of CSV for tag files

Need extensibility for tag property and configurations, and more human readable.

Using YAML might deteriorate the readability of the configuration and tag stream listings. CSV is just fine for now.


links added to social media icons

I have added proper links to social media icons.
Please add GSSOC and level label.
My issue no: #592
https://github.com/Anushkabh/krishiconnect/assets/143275265/43d739be-a81a-4a7a-8b09-97bd2b387f59

hey @harikasayani !
We dont have any socials as of now. So sorry but we cannot accept this PR at this moment.
Keep lloking for more issues in the repo.
happy coding ✨


Update datamodel-POSTGRES-knum.mdx

Adds missing word.

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


feat(dex): integrate stab-fee api

What this PR does / why we need it:
Which issue(s) does this PR fixes?:

Fixes #
Sample Links & Screenshots:

Link:

Desktop Screenshot

Mobile Screenshot

Additional comments?:
Developer Checklist:

[ ] Read your code changes at least once
[ ] Tested on multiple web browsers
[ ] Tested responsiveness (e.g, iPhone, iPad, Desktop)
[ ] No console errors
[ ] Unit tests*
[ ] Added e2e tests*

Lyka can you update @waveshq/walletkit to ^0.41.0 in this PR? Then change target branch to rc/1.10.0


Silverlight videos require the play button to be pressed twice to replay after a video has played

Wordpress 3.6 Beta3
Mediaelement version 2.11.3 (Wordpress)
Tried having a go to fix this but was unsuccessful.
From what I can see the media.paused status which is true a the end of play is reset to false somewhere after. When the play key is pressed to replay it incorrectly assumes that it is pausing play.
It seems the 'media' object is being recreated as I tried changing other values in this object and they are also wiped.
Can't figure out where this is happening so this one is in your bag.
Cheers
TheProfessor

@professor99 Closing old issues. If you'd like to reopen this, let us know. Thanks!


Add equivalent PowerShell commands for this

These docs should have PowerShell equivalent commands for admins to choose which one they want to use.

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

ID: bb8e2623-1f79-aee3-bd97-8b5f647b6980
Version Independent ID: 6346b54d-cc8d-0b79-a6b8-f9144cfa2459
Content: Log in to a Linux VM with Azure Active Directory credentials
Content Source: articles/virtual-machines/linux/login-using-aad.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

This blog has powershell cmd for this https://blog.azureandbeyond.com/2018/07/31/aad-login-linux/


Service discovery

Make backends able to register / deregister to the LB dynamically.

[ #5 ]  MVP

ship it


Laplacian pyramid or Gaussian pyramid?

In the code a Laplacian pyramid which saves the difference between two images is calculated but did not used. I think call it "Gaussian pyramid" in the paper is more appropriate.

Sure


Multimodal Retriever is not retrieving right documents with OPENclip embedding models.

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
https://docs.llamaindex.ai/en/stable/examples/multi_modal/ChromaMultiModalDemo.html
I was using above code for retrieving right images from the directory of images,
But every time i'm getting wrong images from the retriever,
My input images usually contains tables or paragraphs.
I also tried with Multimodalvector and Vector retriever , but the results are same..
So please anyone knows how to improve this , Let me know

Hi , can you show me an example how to use this Multimodal embedding ? with code

@NeethanShetty07 do you have enough images for retrieval?

Hi @hatianzhang , here is the colab code which i was using.
https://colab.research.google.com/drive/1NZJXjg7q7Q4fn-kdP2VRmI2L0j8UNbcB?usp=sharing
Let me know if im doing anything wrong here.
also i have attached the image zip file, , please find it
table_images.zip


glibc: depends on gawk

Details: #953

xz was installed by bottle, but that bottle is not working on the Travis CI system.
https://travis-ci.org/Linuxbrew/linuxbrew/builds/117300152#L655-L658
==> Downloading http://ftpmirror.gnu.org/gawk/gawk-4.1.3.tar.xz
Already downloaded: /home/travis/.cache/Homebrew/gawk-4.1.3.tar.xz
==> Verifying gawk-4.1.3.tar.xz checksum
Error: Empty archive

Travis CI is running Ubuntu 12 Trusty.
It compiled successfully on LinuxbrewTestBot running Ubuntu 14 Precise.
See https://github.com/LinuxbrewTestBot/linuxbrew/tree/pr-DoomHammer-add-glibc-deps

See #968 xz: Error: Empty archive

Yet another reason to give #601 a try? ;)

I fixed #968 xz: Error: Empty archive

I would like any deps of the toolchain (i.e. glibc and gcc) to be bottled, to make installing the toolchain quick and painless. gawk doesn't say it's cellar :any, but I suspect it would work just fine.
Anything bottles installed before glibc (that is any deps of glibc, like zlib and binutils) have to be built on a "holy build box" with glibc 2.5, the oldest glibc supported to bootstrap Linuxbrew. The downside to that solution is that these "compatible" bottles have to be built by hand. So I want to avoid adding hard deps to glibc, and most systems do provide gawk.
I suggest adding a Requirement rather than a dependency that first checks whether the system provides awk, and if not builds gawk from source. gawk takes one minute to build, so perhaps I'm overthinking this, but it's a simple fix.
class AwkRequirement < Requirement
  fatal true
  default_formula "gawk"
  satisfy { which "awk" }
end

Understood, sir!
BTW: why build by hand on a holy machine? Can't we make a holy Docker container just for that?

For sure! Any distribution that uses glibc 2.5 will do just fine. CentOS 5 for example, though I'd prefer a Debian or Ubuntu release that also used glibc 2.5.

BTW: where does linuxbrew/linuxbrew come from as it is not the Dockerfile from current repo for sure?

OK, nevermind that. I pushed doomhammer/linuxbrew-lenny to Docker cloud but wouldn't call it working.
When I issued brew install gcc --with-glibc --verbose it got stuck:
==> Installing dependencies for gcc: patchelf, zlib, binutils, linux-headers, glibc, xz, gmp, gpatch, mpfr, libmpc, isl
==> Installing gcc dependency: patchelf
==> Downloading https://linuxbrew.bintray.com/bottles/patchelf-0.9.x86_64_linux.bottle.tar.gz
/usr/bin/curl -fLA Homebrew 0.9.5 (Ruby 2.1.5-273; x86_64-linux) https://linuxbrew.bintray.com/bottles/patchelf-0.9.x86_64_linux.bottle.tar.gz -C 0 -o /home/linuxbrew/.cache/Home
brew/patchelf-0.9.x86_64_linux.bottle.tar.gz.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  285k  100  285k    0     0   129k      0  0:00:02  0:00:02 --:--:--  140k
==> Verifying patchelf-0.9.x86_64_linux.bottle.tar.gz checksum
==> Pouring patchelf-0.9.x86_64_linux.bottle.tar.gz
tar xvf /home/linuxbrew/.cache/Homebrew/patchelf-0.9.x86_64_linux.bottle.tar.gz
tar: Failed to set default locale
x patchelf/0.9/
x patchelf/0.9/bin/
x patchelf/0.9/bin/patchelf
x patchelf/0.9/share/
x patchelf/0.9/share/doc/
x patchelf/0.9/share/doc/patchelf/
x patchelf/0.9/share/doc/patchelf/README
x patchelf/0.9/share/man/
x patchelf/0.9/share/man/man1/
x patchelf/0.9/share/man/man1/patchelf.1
x patchelf/0.9/COPYING
x patchelf/0.9/INSTALL_RECEIPT.json
x patchelf/0.9/README

Funny thing, running brew install patchelf seemed to work, but then:
==> Installing dependencies for gcc: zlib, binutils, linux-headers, glibc, xz, gmp, gpatch, mpfr, libmpc, isl
==> Installing gcc dependency: zlib
==> Downloading https://linuxbrew.bintray.com/bottles/zlib-1.2.8.x86_64_linux.bottle.1.tar.gz
Already downloaded: /home/linuxbrew/.cache/Homebrew/zlib-1.2.8.x86_64_linux.bottle.1.tar.gz
==> Verifying zlib-1.2.8.x86_64_linux.bottle.1.tar.gz checksum
==> Pouring zlib-1.2.8.x86_64_linux.bottle.1.tar.gz
tar xvf /home/linuxbrew/.cache/Homebrew/zlib-1.2.8.x86_64_linux.bottle.1.tar.gz
tar: Failed to set default locale
x zlib/1.2.8/
x zlib/1.2.8/ChangeLog
x zlib/1.2.8/lib/
x zlib/1.2.8/lib/libz.so.1
x zlib/1.2.8/lib/libz.so.1.2.8
x zlib/1.2.8/lib/pkgconfig/
x zlib/1.2.8/lib/pkgconfig/zlib.pc
x zlib/1.2.8/lib/libz.a
x zlib/1.2.8/lib/libz.so
x zlib/1.2.8/README
x zlib/1.2.8/INSTALL_RECEIPT.json
x zlib/1.2.8/include/
x zlib/1.2.8/include/zlib.h
x zlib/1.2.8/include/zconf.h
x zlib/1.2.8/share/
x zlib/1.2.8/share/man/
x zlib/1.2.8/share/man/man3/
x zlib/1.2.8/share/man/man3/zlib.3
/home/linuxbrew/.linuxbrew/Cellar/patchelf/0.9/bin/patchelf --set-rpath /home/linuxbrew/.linuxbrew/lib /home/linuxbrew/.linuxbrew/Cellar/zlib/1.2.8/lib/libz.so.1.2.8

Could you point me @sjackman where to go from here as I am still not very familiar with Homebrew internals?
Thanks!

tar: Failed to set default locale
See https://github.com/Linuxbrew/linuxbrew/blob/master/Dockerfile#L9

Is it just hanging after extracting the tarball? I've seen that behaviour too on Ubuntu 12 precise, and haven't figured it out.

For my own reference:
History of Debian releases: https://wiki.debian.org/DebianReleases
History of glibc releases: https://sourceware.org/glibc/wiki/Glibc Timeline

localedef on lenny have no notion of -i switch. That is why I omitted
this.
As for hanging: this is what it looks like. May try a bit of straceing
but other than that, no idea.
On Tue, Mar 22, 2016, 5:27 PM Shaun Jackman<EMAIL_ADDRESS>wrote:

For my own reference:
History of Debian releases: https://wiki.debian.org/DebianReleases
History of glibc releases:
https://sourceware.org/glibc/wiki/Glibc Timeline
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/Linuxbrew/linuxbrew/pull/955#issuecomment-199890280

Lenny probably didn't support UTF-8 either.
I noticed that Ruby was still using CPU, so I think it was stuck in some kind of loop. Possibly (long shot here) due to a missing program.

I'd also bet for a missing program. Maybe command-not-found's approach would help here?

Funny thing. Should cc1 be running during pouring bottle? I thought this process was more like: "unpack your things and move them to correct places"...

No, cc1 should not be running when pouring a bottle. pstree may be useful to see who's running it.

While running brew install binutils --verbose:
$ pstree
bash-+-pstree
     `-ruby-+-ruby-+-ruby-+-make---sh---make---sh---sh---make---make---sh---make---8*[gcc-4.3-+-as]
            |      |      |                                                                   `-cc1]
            |      |      `-{ruby}
            |      `-{ruby}
            `-{ruby}

The output on the other hand was:
[...]
/home/linuxbrew/.linuxbrew/Cellar/patchelf/0.9/bin/patchelf --set-rpath /home/linuxbrew/.linuxbrew/lib --set-interpreter /home/linuxbrew/.linuxbrew/lib/ld.so /home/linuxbrew/.linuxbrew/Cellar/binutils/2.25.1/x86
_64-unknown-linux-gnu/bin/objdump
/home/linuxbrew/.linuxbrew/Cellar/patchelf/0.9/bin/patchelf --set-rpath /home/linuxbrew/.linuxbrew/lib --set-interpreter /home/linuxbrew/.linuxbrew/lib/ld.so /home/linuxbrew/.linuxbrew/Cellar/binutils/2.25.1/x86
_64-unknown-linux-gnu/bin/ranlib
/home/linuxbrew/.linuxbrew/Cellar/patchelf/0.9/bin/patchelf --set-rpath /home/linuxbrew/.linuxbrew/lib --set-interpreter /home/linuxbrew/.linuxbrew/lib/ld.so /home/linuxbrew/.linuxbrew/Cellar/binutils/2.25.1/x86
_64-unknown-linux-gnu/bin/strip

Come to think of it, maybe 4.3 was deprecated based on fact it has some weird loop issue or some such?
Still: what is that guy even doing when I am pouring from a bottle?

It's clearly compiling something. It looks as though the output is not updated, but brew has moved on to compiling a formula. Does ps aux |egrep 'make|sh' give some indication of what's being compiled? You can also poke around in /proc to figure out what these processes are up to.

What is being compiled is usually what is being installed. I am more concerned whether it is done after pouring. Is there some logic in place to build from source after pouring is done (eg. if poured bottled is incompatible with the system or something like that)?

Another interesting question: what could be blocking output? I clearly see in ps aux that installation of binutils is taking place whereas console seems stuck on:
brew install binutils
==> Installing dependencies for binutils: patchelf, zlib
==> Installing binutils dependency: patchelf
==> Downloading https://linuxbrew.bintray.com/bottles/patchelf-0.9.x86_64_linux.bottle.tar.gz
######################################################################## 100.0%
==> Pouring patchelf-0.9.x86_64_linux.bottle.tar.gz

In the meanwhile zlib got silently installed as well.

It looks like the console has hang up. Perhaps its file descriptor was inadvertently closed.

Tried my luck with Centos and things were mostly smooth, until gawk couldn't link. Maybe this is a dead end, in fact?
As a workaround one might create a fake keg with curl -Lq s.minos.io/s > /home/linuxbrew/static-get &&         sh /home/linuxbrew/static-get -x gawk...

That's the first that I've heard of minos. It's not a bad workaround, but I'd prefer to install gawk using Linuxbrew.

I would too, but no luck on ancient distro ;)

Where are you stuck? With the broken console? I haven't figured that one out yet myself.
I regularly use Linuxbrew on CentOS 5.11 with glibc 2.5.

Console problems were on Debian Lenny. gawk on CentOS couldn't build due to some reloc problem, which I suspect means linker is too old.

Can you post the error message?

My bad, linking error was with something different altogether. gawk was pretty simple:
==> Installing dependencies for gawk: xz
==> Installing gawk dependency: xz
==> Downloading https://linuxbrew.bintray.com/bottles/xz-5.2.2.x86_64_linux.bottle.tar.gz
######################################################################## 100.0%
==> Pouring xz-5.2.2.x86_64_linux.bottle.tar.gz
/home/linuxbrew/.linuxbrew/Cellar/xz/5.2.2: 65 files, 1.6M
==> Installing gawk
==> Downloading http://ftpmirror.gnu.org/gawk/gawk-4.1.3.tar.xz
==> Downloading from http://ftp.task.gda.pl/pub/gnu/gawk/gawk-4.1.3.tar.xz
######################################################################## 100.0%
Error: Empty archive

This is both well-known and a circular dependency (I cannot install glibc if we want gawk linked against the old glibc). Workaround might perhaps be to install non-brewed xz?

Ah, xz is linked against new glibc. As a temporary workaround, use the gz http://ftpmirror.gnu.org/gawk/gawk-4.1.3.tar.gz rather than xz.

As discussed, this fix requires an :awk requirement, so as to avoid adding a build dependency to binutils. Closing this PR for now, before the grand split of brew and homebrew-core.


Add rahulbabu95 to owners

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/lgtm
/approve


Change the instructions to remove reference to Python 2.7

On step 4, the instructions read
"virtualenv -p /usr/bin/python2.7 databrickscli"
This no longer works. It should read:
"virtualenv -p /usr/bin/python databrickscli"

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

ID: 64be8819-4ac8-cceb-313f-2561a6c2c759
Version Independent ID: 1ca873b5-f399-179f-e721-b09a78dab4fc
Content: Use Databricks CLI from Azure Cloud Shell
Content Source: databricks/scenarios/databricks-cli-from-azure-cloud-shell.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@clintsherwood
Thanks for your feedback! We will investigate and update as appropriate.

@clintsherwood
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Title should be "resource estimator". Note that the TOC and the article dont match

[Enter feedback here]

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

ID: a53f218b-929a-66f9-b18f-9062b3f4d8c8
Version Independent ID: a53f218b-929a-66f9-b18f-9062b3f4d8c8
Content: Quantum resources estimator - Quantum Development Kit - Azure Quantum
Content Source: articles/machines/resources-estimator.md
Service: azure-quantum
Sub-service: qsharp-guide
GitHub Login: @SoniaLopezBravo
Microsoft Alias: sonialopez

Hi @SerinaKaye! Note that heading, metadata title and TOC title don't always match. In this case, the heading expands the TOC title implying that the resource estimator is part of the QDK extension.


remove singletons from CRAM

Command used:
samtools view -T ../../genome/seq/GCA_000001405.15_GRCh38_full_plus_hs38d1_analysis_set_chr21.fna -C -e 'rnext != "*"' test.cram

Did you check if the metrics tools work? And yours?

HsMetrics works, I'll wait till the pipeline is done and then I'll merge


how do I decode  LTV (not TLV) arrays?

I'm trying to decode BLE advertisements, which are length-type-value encoded
it would amount to someting like LTV(len_size=1, swapTL=True) for this particular case
here's an example:

do you see a way to do this, maybe subclassing?
best regards
Michael

I gave it a try, see https://github.com/mhaberler/uttlv/tree/ltv-option - rather rough
example for decoding the above advertisement
is that something you would be willing to consider a PR for?


Added Hiera support for postfix::config, postfix::hash, postfix::transport and postfix::virtual

This PR adds support for Hiera. Some dependency were removed since Puppet throw dependency cycle errors:
Class['postfix']

I not really sure if this will throw errors in some edge cases, i found none in my tests.
Class['postfix'] -> Postfix::Hash <| |>

No longer needed since dependency to class{ 'postfix': } is managed in hash.pp

Will close this issue as no news have been provided in over 9 months.

@raphink What's the state of this PR. Does it need code or just testing? It would be very nice to have a postfix module that is entirely hiera-compatible.

I agree... it was 90% there, not sure why the authors didn't just finish it off?

Is there any development going on in this module? It looks quite dead.

I switched to https://github.com/thias/puppet-postfix

ok. hmm last update 2 years ago

Better than 4 years, right? ;) I'm still using it for my server and it works so far. Hope thias might consider moving the module to Voxpupuli  (https://github.com/thias/puppet-postfix/issues/116)

I've moved to Ansible :)

The latest release of this module was done a month ago so it's obviously not dead.

I realize this thread is dead, but is there an example on how one can configure main.cf through postfix::files using Hiera?

@raphink could you re-open this issue? What does this PR needs?
Would you agree on moving this module to voxpupuli if you don't have much time for it anymore?
@finalhow I'm no expert, but here's what I did to enable hiera for some configs for the posgresql module'
  $configs=hiera('postgresql::server::config_entry', {})
  create_resources('postgresql::server::config_entry', $configs)

Then, I set the values I wanted this way:
postgresql::server::config_entry:
  max_wal_senders:
    value: '2'

  wal_level:
    value: 'hot_standby'

  archive_mode:
    value: 'on'

If I underestand correctly how it works, if you can set variables values in manifests, you can set variables values in hiera, once you've added the 2 lines above where you call your class (you'll obviously won't use the same names as me because it's not for the same context).

@ubellavance Thanks, I will give that a try.

@finalhow if you need help, just post your config and I'll try to help.

@ubellavance 	I reopened the issue, but you have commit rights on the reporter's branch I guess, so it might still require to open a new one.

@ubellavance any news?


Change the execution endpoint in consensus (Prysm)

--execution-endpoint flag was giving error so changing it with the --http-web3provider
Error:
time="2022-10-03T14:55:12Z" level=error msg="flag provided but not defined: -execution-endpoint" prefix=main

Fixes | Closes | Resolves #

Anything marked as optional that you didn't need to fill in, please remove it from the PR description. Choose one of the keywords above to refer to the issue this PR solves, followed by the issue number (e.g Fixes # 666). If there is no issue, remove the line. Remove this note after reading.

Changes:

Types of changes
What types of changes does your code introduce?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Other (please describe):

Testing
Requires testing

[ ] Yes
[ ] No

In case you checked yes, did you write tests?

[ ] Yes
[ ] No

Comments about testing , should you have some (optional)
Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Hi @dharmendrakariya , thanks for the PR. We will investigate this. According to Prysm docs the http-web3provider flag is deprecated, so I'm afraid this can't be the solution :(
Can you please open an issue describing with more details the problem you faced? Feel free to share more details here as well, like OS, sedge version, the command you used, prysm docker image tag, etc.

@AntiD2ta yeah I read the doc and thought to update the image! I opened the PR I should close this one!


Is it possible to customise the height of richEditor?

Sometimes I need to set it as Dimensions.get('window').height * 0.5 or even less,
can we do that?

可以使用 useContainer 在即将发布的1.0.5版本
You can use useContainer in the upcoming 1.0.5 release


Deleting a schema branch with an enabled schema should throw BAD REQUEST error

Deleting a schema branch with an enabled schema version throws a BAD REQUEST error from the back end, but the error is not propagated to UI.

Raised PR https://github.com/hortonworks/registry/pull/340 for UI - Showing error notification on BAD REQUEST.

Thanks @satishwaghela for addressing this issue.


Document key telemetry events and errors to aid in troubleshooting

Issue Category

Missing page/section/topic

Details
Internally at Microsoft, we maintain "TSGs" or Troubleshooting Guides to help during investigation of errors in the system. These should be published on the docs site in some form. Here are some examples of what to consider including:

Key telemetry events for main scenarios (Container load, Summarize, Request routing)
Error propagation (e.g. which APIs throw v. expose an error event)
How to debug/diagnose particular classes of errors that appear in the logs
Instructions for logging issues when an error in the Fluid Framework is impacting your app/service reliability

And of course we need to find the right spot on the docs site, or make a new one.

The first bullet is a bit Nope, see #6976.
Documenting errors is a good idea, but not something we need to track right now.  We do imagine a world where our API surface exposes errors by returning a result object with a strongly typed error in failure cases, rather than throwing errors by default.  And especially then we would document those error types.
And debugging instructions would be nice, but that's more of a feature-by-feature approach, we're not going to drive a top-down effort here.
The last one is definitely interesting, but again not worth tracking here now.  cc @skylerjokiel and @tylerbutler as FYI - "Instructions for logging issues when an error in the Fluid Framework is impacting your app/service reliability" sounds like a good idea, something to keep in mind.  Feel free to reach out to me about this topic.


initialStyles not affected by applyStyles

As a developer I want to use the popper library without CSP header unsafe-inline.
Therefore I need no inline styles to be applied to any DOM element.
To achieve this I use the the applyStyles modifier to catch the styles and write it to a

You also need to override the modifier's effect.
https://github.com/popperjs/popper-core/blob/1450aa5f1b113726f9b70d3d3b9ace53e1be290e/src/modifiers/applyStyles.js#L36-L75


CVE-2022-42003

Describe the bug

What did you see instead?
Impacted versions: <2.14.0
In FasterXML jackson-databind before 2.14.0-rc1, resource exhaustion can occur because of a lack of a check in primitive value deserializers to avoid deep wrapper array nesting, when the UNWRAP_SINGLE_VALUE_ARRAYS feature is enabled. Additional fix version in <IP_ADDRESS> and <IP_ADDRESS>
Additional context
Add any other context about the problem here.

Dependency updated in the fork
https://github.com/gdohmeier-wawa/aws-otel-java-instrumentation/pull/1

Fixed by #240.

is the 1.19.0 version released?

Releases can be tracked here https://github.com/aws-observability/aws-otel-java-instrumentation/releases

Couldn't find 1.19.0, even though PR is merged yesterday. Is there any release schedule?


[5.5] Envoy not working after upgrade from 1.2.2 to 1.3.4.

Laravel Version: 5.5
PHP Version: 7.1.10
SO: Alpine 3.4.6

Description:
After upgrade from envoy 1.2.* to 1.3.*, some comands are broken:
/www $ vendor/bin/envoy run disk-info --path="/var/www/conf" --depth=1

  [Exception]
  Task "disk-info" is not defined.

run [--continue] [--pretend] [--path PATH] [--] <task>

/www $ vi composer.json
/www $ composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
  - Updating laravel/envoy (v1.3.4 => v1.2.2): Downloading (100%)
Writing lock file
Generating autoload files
/www $ vendor/bin/envoy run disk-info --path="/var/www/conf" --depth=1
<EMAIL_ADDRESS>206916	/var/www/home/000000331
<EMAIL_ADDRESS>205316	/var/www/home/000000024

Steps To Reproduce:
command with path and extra parameters after path.
this command works fine:
vendor/bin/envoy run disk-info --depth=1 --path=/var/www/home/
this not:
vendor/bin/envoy run disk-info --path=/var/www/home/ --depth=1
both commands works fine in previous releases 1.2.X

Is this still broken in 1.4.0?

No, now works fine. I'm retrying with 1.3.4 version and works fine, maybe the bug was in another envoy dependency.


Can not use click event on the icon

I would like to propose to forward mouse events so we can use markup like this;
<RiSkipRightFill on:click={next} />
I might make a PR for this when I have time

This option was there in previous versions of this library, but it was removed in the latest version.
The reason being the component will place in a <svg> tag, and these tags should not be click targets by default for accessibility. It is preferable to wrap these components in <button> tag and add relevant handlers there. In that way, even who are using your application with a screen reader or maybe just trying to navigate your application with keyboard only will get proper feedbacks. It was removed to discourage adding click handlers to non-interactive elements.

A section has been added on the usage of events. Usage example
Thanks!


Benchmarking proved my speculative optimization wrong. Something else…

… made things better.

Added a microbenchmark with jmh for AccessLogger.
Switched back to shorter and simpler string interpolation because it's totally fine

I threw this into protocol-benchmark because that's what I was testing. We can move this elsewhere but I wanted an example of how to microbenchmark somewhere in our repo for future use.

:star: :christmas_tree:

:star: :dango: Thanks for updating -- looks good to me.


Rename action and update description

Please help to correct the description if needed.

I also update the action name in RADME.


Make the module base address unchanged

Describe the feature you'd like to see added

When we restart the computer, or modify the bio4.EXE file.  The module base address of the game will change. As shown in the figure.  This limits our modifications to the game EXE file.  Is there any way to fix it?

In the 2007 version it worked without any issues.  We can freely modify EXE files.  But not in 2014 version

If you set the relocations stripped flag it should stop Windows from relocating it, making it stay at 0x400000

您可以设置 relocations stripped 标志，该标志应该阻止 Windows 重新定位它，使其保持在 0x400000：（ 这在使用 IDA 调试时非常有用，否则 IDA 每次调试时都会花费 5 分钟以上重新定位 >.>）

Ahhh, thank you very much for your answer

Did you show your friend the post I sent before? That flag & the .reloc edit should work pretty much the same, both should make EXE use the default base addr (0x400000 for RE4) instead of moving it around.
Anything dynamically allocated (like pointers to certain things in memory) would still be placed at random addresses though (.reloc wouldn't affect that neither afaik) - but things that are actually inside the EXE file on your HDD should get put at a static offset.
re4_tweaks should work fine with either method, don't know about other mods though - IIRC companion will complain about game not being 4GB patched if you use this flag though even if the 4GB patch is present, since this flag & 4GB patch both change the same byte.
There is another flag you can set which might work better with companion (OptionalHeader -> DllCharacteristics -> uncheck "DLL can move"), haven't tested that with companion yet but seems to make addr static like the other flag, but if companion still gives a warning with both of them maybe editing .reloc would be better.
Here's a zip with both flags, bio4_flag1 sets the first flag I mentioned (FileHeader -> Characteristics -> "Relocation info stripped"), the bio4_flag2 sets the other one, both have 4GB patch applied too:
bio4-106-relocflags.zip

Here's a zip with both flags

Thanks for all this info, I am sure it will be helpful. I will let you know how things go after we decided which way to go and how it all works out. I'm relieved that it will not interfere with your work!
Peace!

Sorrry I know this is closed but I have some questions about nuking the table. I posted them here:
https://cs.stackexchange.com/questions/158869/questions-about-relocation-tables


x/build/cmd/coordinator: decide what to do about a global build time limit

The comment of CleanUpOldVMs (and CleanUpOldPodsLoop) includes:

This is the safety mechanism to delete VMs which stray from the
normal deleting process. VMs are created to run a single build and
should be shut down by a controlling process. Due to various types
of failures, they might get stranded. To prevent them from getting
stranded and wasting resources forever, we instead set the
"delete-at" metadata attribute on them when created to some time
that's well beyond their expected lifetime.

This mechanism requires maintaining a timeout for builds, one that's always "well beyond their expected lifetime". If that stops being true, also depending on the state of #42699, resources may be wasted due multiple retries (as happened in #49666 and #52591 in 2021-2022).
Since coordinator knows about all the builds it started, and already deletes builds that it doesn't know about (e.g., because they're left over from a previous instance of coordinator), I don't think a timer is actually needed for that. However, it might still be useful to handle stalls or other unexpected reasons why a build keeps going beyond a "reasonable" timeframe. So maybe we'll always need to maintain such a timeout.
One of the things we can do in either case is add better metrics/monitoring, so we find out when normal builds start to get dangerously close to the limit before it starts to cause problems.
CL 406216 increased the global timeout for builds from 45 mins to 2 hours to accommodate longtest builders, and this is the tracking issue to figure out what we want to do in this space long term. (Possibly simply bump it up from 2 hours if some builds need even longer in the future.)
CC @golang/release.

FWIW, with the current builder triage process I'm using there is a natural limit on builder time, which is the interval between a CL being submitted and its triage being performed.
I've been using the day boundary as the triage cutoff, and I think the timestamps that fetchlogs uses are in UTC. I'm in UTC-4 and I don't start triage until at least 9AM local time, so that gives a natural limit of ~13h (less scheduling latency) before the tests for a CL committed just before midnight would start to overrun the triage window.


Fix the hard polygon closing

Add the current zoom level to the calculation of the distance to the starting point

Coverage remained the same at 45.039% when pulling 018f9759c3be2113bcba88b49ae1e1b255141f94 on SirmaITT:feature/fix_polygon_close into 284ffd58e462e567f44250acace6d30ecfffc1fc on IIIF:annotation-work.


Document key permissions needed with ProtectKeysWithAzureKeyVault

Issue description
There is no documentation on what keyvault permissions are needed with ProtectKeysWithAzureKeyVault(). It should note which specific access policy permissions are required for use.
Software versions
Check the .NET target framework(s) being used, and include the version number(s).

[X ] .NET Core
[ ] .NET Framework
[ ] .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

dotnet --info output or About VS info
.NET Core SDK (reflecting any global.json):
 Version:   2.2.104
 Commit:    73f036d4ac

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17763
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.104\

Host (useful for support):
  Version: 2.2.2
  Commit:  a4fd7b2c84

.NET Core SDKs installed:
  2.0.3 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.401 [C:\Program Files\dotnet\sdk]
  2.1.504 [C:\Program Files\dotnet\sdk]
  2.1.505 [C:\Program Files\dotnet\sdk]
  2.1.600 [C:\Program Files\dotnet\sdk]
  2.1.601 [C:\Program Files\dotnet\sdk]
  2.1.602 [C:\Program Files\dotnet\sdk]
  2.2.104 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.8 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Can you create an issue from the doc page? That will connect the doc to the issue. Go to the bottom of the page and select the Content feedback issue.

https://docs.microsoft.com/en-us/aspnet/core/security/data-protection/configuration/overview