Mixed Reality Feature Toolkit causes importing error.

Describe the bug
When I import MRTK example package(it imports dependent packages, like MRTK foundation and etc also) from Mixed Reality Feature Toolkit, unity shows error log for all packages like below.
[xxx\com.microsoft.mixedreality.toolkit.xxx.tgz] is not a valid package tarball
Environments are:
Unity 2019.4.19f
Mixed reality Feature Tool for Unity v<IP_ADDRESS>.0 Beta
Target MRTK version is 2.6.
Is there anyone who can use Mixed Reality Feature Toolkit to import MRTK packages succesfully?

Yes I was able to import the packages successfully. I did a video about it at here

@omanuke, did you receive any errors from the Feature Tool? Can you confirm the sizes of the packages that were copied into your project's Packages/MixedReality folder?
Thanks!

Please try the new release of the Feature Tool at https://aka.ms/mrfeaturetool. It adds a new diagnostic log and better handling of downloads that fail with 0 bytes downloaded.

v1.0.2103.2 has been released and should no longer attempt to import zero length package files. Updated version is at https://aka.ms/mrfeaturetool

@dilmerv
I tried v1.0.2103.2beta. It can download successfully but raises error like 1.0.2103.1.
Unity project tree is like this.
Is this expected behaviour?
What I did are:

create unity 3d project by 2019.4.19f.
open Mixed Reality Feature Tool for that project and checked only 'Mixed reality toolkit Examples(v2.6)'

@davidkline-ms Report above that v1.0.2103.2beta might not have fully fixed this.

@omanuke,
Can you send me the log file that is in c:\users<your name>\AppData\Local\MixedRealityFeatureTool? It might help identify the issue.
Based on the error message, Unity is claiming there is a missing dependency. Based on your images, that seems incorrect.
Also, if you are willing, a copy of the manifest.json file would be helpful as well. It is possible something did not get written correctly.
Thank you!

Here. But they seems OK.
Do I have to add some entries for package server?
MixedRealityFeatureTool.zip

@davidkline-ms Reading this thread, looks like you are the person responsible for issues with the Feature Tool. I left a bug report #9618 on Feature Tool failing to add Mixed Reality Toolkit to Unity main menu. Hope you could take a glance at it. :)

@davidkline-ms I did more testing and found the issue is related to the Azure Object Anchors feature selection. When selected at the beginning of a new project, this feature fails with multiple error and warnings causing the Feature Tool process to fail to complete. See #9618 for more detailed results and errors list.

@davidkline-ms , Do u have some plan to fix this issue?
Or if u know environments on which this tool works perfectly like Unity version or some, please tell me it. I'll try it.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


SelenideElement#toWebElement() should not wait for timeout if element does not exist

the subj method is implemented based on the command:
public class ToWebElement implements Command<WebElement> {
  @Override
  public WebElement execute(SelenideElement proxy, WebElementSource locator, Object[] args) {
    return locator.getWebElement();
  }
}

this command will fail if element does not exist...
and will be retried inside "the only one logic of SelenideElementProxy invocation of all commands":
class SelenideElementProxy implements InvocationHandler {
//...

  @Override
  public Object invoke(Object proxy, Method method, Object... args) throws Throwable {
    if (methodsToSkipLogging.contains(method.getName()))
      return Commands.getInstance().execute(proxy, webElementSource, method.getName(), args);

    validateAssertionMode(config());

    long timeoutMs = getTimeoutMs(method, args);
    long pollingIntervalMs = getPollingIntervalMs(method, args);
    SelenideLog log = SelenideLogger.beginStep(webElementSource.getSearchCriteria(), method.getName(), args);
    try {
      Object result = dispatchAndRetry(timeoutMs, pollingIntervalMs, proxy, method, args);
      SelenideLogger.commitStep(log, PASS);
      return result;
    }
    catch (Error error) {
      Error wrappedError = UIAssertionError.wrap(driver(), error, timeoutMs);
      SelenideLogger.commitStep(log, wrappedError);
      if (config().assertionMode() == SOFT && methodsForSoftAssertion.contains(method.getName()))
        return proxy;
      else
        throw wrappedError;
    }
    catch (RuntimeException error) {
      SelenideLogger.commitStep(log, error);
      throw error;
    }
  }
// ...
}

but it should not... We should have a raw interface to original Selenium WebDriver WebElement without any waiting logic...

Will better to create new method if it needs, because changing current will be breaking change that will not be easy to find and fix.
Also I am not sure about this idea... you need element but you are ready to recieve NoSuchElementEx instead.. for what?

I am not sure this "breaking change" will affect a lot of users...
If somebody uses "webelement" he is using it in rare cases, I probably they would expect element not to wait. Otherwise they would use SelenideElement as it is...
Also, this method was almost all the time in Selenide, and in the past it was without waiting logic... So I would say - this is really a bug, not something that people got used to, and now we are going to break it...
The idea is to have an ability to get a raw interface to webelement from Selenide. This might be needed for implementing some extensions on top of Selenide in the cases where Selenide lacks something... For example right now I am extending Selenide in context of Mobile Automation, and in some cases I need this "raw" interface to WebElement...

For example, I need this toWebElement to fail at the moment of call to identify this failure as a false feedback in context of implementing custom conditions in context of mobile automation

If somebody uses "webelement" he is using it in rare cases, and probably they would expect webelement not to wait.

Unfortunately, it is not true. I've seen a lot of cases when people use toWebelement to pass use weblement directly. Mostly they try to cheat selenide to avoid "Element is not visible" exception or smth else. And removing waiting will affect them.

Also, this method was almost all the time in Selenide, and in the past it was without waiting logic

It is interesting. I agree it is a bug. Will see how long is it.

Also, this method was almost all the time in Selenide, and in the past it was without waiting logic

I checked. toWebElement is implemented by command since at least 2015... I didn't go deeper. So I assume it was with waiting originally

I am afraid, you missed something... Just did not check deep enough...
Look at this state on 1/11/2015, this is a class that implements waiting logic, it defines two methods: getDelegate that waits and getActualDelegate that does not wait:

Then all selenide methods are based on calling either getDelegate (if they need to wait) or getActualDelegate (if they do not want to wait). Now look at how toWebElement is defined:

Same as getWrappedWebElement by the way:

And here is an example of method that needs to wait:
    else if ("pressEnter".equals(method.getName())) {
      getDelegate().sendKeys(Keys.ENTER);
      return proxy;
    }

As you can see, in the past toWebElement was implemented without waiting explicitly. This was an original intent to provide an access to the raw webelement, so called "actual delegate" without any "selenide magic".
Then, after refactoring, the bug was introduced :( Seems like it happened even earlier than moving to Command pattern.

Unfortunately, it is not true. I've seen a lot of cases when people use toWebelement to pass use weblement directly. Mostly they try to cheat selenide to avoid "Element is not visible" exception or smth else. And removing waiting will affect them.

I am sure somebody will find a way to use a selenide in a crazy way:) But I would not keep API adapted for those "crazy things":) Especially if it is a bug, and if logically it's not natural to have such implementation...
Yet we can discuss the "natural" behaviour... And if we find that old behaviour is unnatural, I would vote for a breaking change... Maybe though in a next increment of main number in versioning...
So... we have two methods toWebElement and getWrappedElement ...
Both originally did not have waiting logic...
And at least getWrappedElement - should always return wrapped entity as it is... as in raw selenium... Because Selenide is a wrapper, and when we have some method in it that by its name tells "give me a thing that you wrapped in" - we should give it as it is... waithout waiting...
About toWebElement - I am not totally sure... The name sounds like "type convertion"... So maybe it is natural to keep an actual object with all "waiting magic" but provide it via raw WebElement interface so somebody in their code can use it for some legacy stuff... Seems like it's more natural to keep this method with waiting logic... The only thing that confuses me, is that actually for such convertion behaviour we don't need a separate method... We can just path SelenideElement to whatever accepts WebElement, because SelenideElement extends WebElement...

I am afraid, you missed something... Just did not check deep enough...

great investigation. thank you!

Especially if it is a bug, and if logically it's not natural to have such implementation...

Yeah I don't argue that is a bug. But old bugs become feature for users after long time :)))
Finally, we want to have two method to get WebElement - one with waiting, one without to please all, right?

I would vote for a breaking change... Maybe though in a next increment of main number in versioning...

I'd be better to deprecate one method now, and then replace it in with next increment of main number. It will make transition more smoothly

The only thing that confuses me, is that actually for such convertion behaviour we don't need a
separate method... We can just path SelenideElement to whatever accepts WebElement, because > SelenideElement extends WebElement...

Yes it is. But selenide overrides original selenium methods behaviour - it is acceptable not for all.

:)
Yeah, not for all - that's why they can have an api to raw webelement, completely the same way  as in raw webdriver:) for example via getWrappedElement
So...
1
I am ok to have two methods in Selenide, one with waiting and one without... Though I would have only one, without:), and for "waiting case", I would just use (WebElement) mySelenideElement. But no problem, we can have two methods:)
2
I vote for having SelenideElement#getWrappedElement as the version without waiting, asap as bug fix, not waiting for next increment of main number. Or - deprecate in next minor version, and change it's behaviour in the following minor version (after next one).
3
Regarding SelenideElement#toWebElement - I am ok to keep it as "waiting version", though I would change it's implementation to just return something like (WebElement) proxy just because for my taste it's more natural :)... But ok to keep it as it is...
@asolntsev, what do you also think on all of that?

Yes, this is true:

the original intent to provide an access to the raw webelement, so called "actual delegate" without any "selenide magic".

So I suggest to change toWebElement() behaviour to just return the WebElement without waiting.
I am pretty sure that it was an accidental change when toWebElement() started waiting for the element.
If somebody needs to wait, he can write $.shouldBe(visible).toWebElement().
That's why I don't want to introduce 2 separate methods.
P.S. Just proxying to WebElement may not work. For example, if I remove .toWebElement() from this example, I get the following error:
java.lang.ClassCastException: Cannot cast com.sun.proxy.$Proxy5 to org.openqa.selenium.remote.RemoteWebElement

	at java.lang.Class.cast(Class.java:3369)
	at io.appium.java_client.touch.offset.ElementOption.withElement(ElementOption.java:89)
	at io.appium.java_client.touch.offset.ElementOption.element(ElementOption.java:49)
	at org.selenide.examples.appium.AndroidDragAndDropTest.dragAndDrop(AndroidDragAndDropTest.java:34)

I am pretty ok with the last Andrey's proposal.

@yashaka I could not reproduce the issue? Did you actually try it, or just analyzed the code? :)
Method toWebElement() never waited because of methodsToSkipLogging:
class SelenideElementProxy implements InvocationHandler {
  private static final Set<String> methodsToSkipLogging = new HashSet<>(asList(
      "toWebElement",
      "toString",
      "getSearchCriteria"
  ));

@asolntsev, pretty fast close:-)
I tried it, and it blocked me in some way... I had to find workarounds to get an API to raw webelement...
I will check details and come back later...

@asolntsev ,
Weird... Probably originally I tried only with getWrappedElement, and that's why I saw waiting on my side... And seems like I did not pay enough attention to the difference between getWrappedElement and toWebElement... Sorry...
So, summarizing:

toWebElement fails fast, with no waiting
getWrappedElement waits...

Maybe I would vote for keeping toWebElement as version with waiting and getWrappedElement as non-waiting version... Because "get..." - usually means "get it now, fast". And "to..." usually means "represent what we have now", and it's seems to natural to represent SelenideElement that is dynamic and with waiting logic in general – as WebElement with waiting...
But ok as it is...

I suggest that both methods should NOT wait. They are rather synonyms. Otherwise it's too hard to keep the difference in mind.
I don't see any reasons why someone would need the "waiting" here.

Yeah, me too... Originally I was also for the idea to keep both as non-waiting...
Let's add getWrappedElement to the list in methodsToSkipLogging

Done in https://github.com/selenide/selenide/pull/1124


sx1276 and adxrs610: C++11 incompatibility fixes

Signed-off-by: Eugene Bolshakov<EMAIL_ADDRESS>

Merged, should make it into upstream shortly! Thanks a lot for the patch, hope the libs build nicely with nodejs4+ now.


python312Packages.betamax-matchers: refactor

enabel tests
disable on unsupported Python releases
add pythonImportsCheck
add changelog to meta

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 333938 run on x86_64-linux 1

4 packages failed to build:

python311Packages.sopel
python311Packages.sopel.dist
python312Packages.sopel
python312Packages.sopel.dist

22 packages built:

giara
home-assistant-component-tests.reddit
packj
packj.dist
python311Packages.betamax-matchers
python311Packages.betamax-matchers.dist
python311Packages.github3-py
python311Packages.github3-py.dist
python311Packages.praw
python311Packages.praw.dist
python311Packages.prawcore
python311Packages.prawcore.dist
python312Packages.betamax-matchers
python312Packages.betamax-matchers.dist
python312Packages.github3-py
python312Packages.github3-py.dist
python312Packages.praw
python312Packages.praw.dist
python312Packages.prawcore
python312Packages.prawcore.dist
visidata
visidata.dist

sopel is already broken (https://hydra.nixos.org/build/268316808).


fixing rulesViolated

added sample Id check for incompatible-types and sum-of-answers. sum-of-answers still needs some work.
fixed create project bug: when a project is created from template, rules are not shown, so fixed it.

PostgresProjects.java:

Line 788: I'm not sure getOrZero() is going to work with .getAsBoolean().

database.ini:

Line 13: password=password works on Githika's machine. I don't have any password set for my postgres user account. Matt?

database.ini:

Line 13: password=password works on Githika's machine. I don't have any password set for my postgres user account. Matt?

---- This section is removed in my next PR
PostgresProjects.java:

Line 788: I'm not sure getOrZero() is going to work with .getAsBoolean().

---- Either way it is certainly more clear to add a getOrFalse().


Phase 3 Completion-dev branch

Final commits have been made, build passes for the branch with coverage 87%

Looks Good. Thanks.


Exception in EnvelopedSignatureWriter when Signature element is first child of element

In trying to create a SAML Federation Metadata document, there appears to be a bug/unsupported scenario in the EnvelopedSignatureWriter when the Signature element is the first child:
var credentials = new SigningCredentials(...);
var settings = new XmlWriterSettings
{
    Encoding = new UTF8Encoding(false)
};
var buffer = new MemoryStream();
var writer = new EnvelopedSignatureWriter(XmlWriter.Create(buffer, settings), credentials, "_id");

writer.WriteStartElement("EntityDescriptor", "urn:oasis:names:tc:SAML:2.0:metadata");

writer.WriteSignature();

writer.WriteEndElement();

When the writer tries to emit the signature after the root element is written, the following exception is thrown:
System.Xml.XmlException: Name cannot begin with the '<' character, hexadecimal value 0x3C. Line 1, position 18.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, XmlException exception)
   at System.Xml.XmlUTF8TextReader.VerifyNCName(String s)
   at System.Xml.XmlUTF8TextReader.ReadQualifiedName(PrefixHandle prefix, StringHandle localName)
   at System.Xml.XmlUTF8TextReader.ReadAttributes()
   at System.Xml.XmlUTF8TextReader.ReadStartElement()
   at System.Xml.XmlUTF8TextReader.Read()
   at System.Xml.XmlBaseReader.MoveToContent()
   at Microsoft.IdentityModel.Xml.EnvelopedSignatureWriter.OnEndRootElement() in C:\agent2\_work\56\s\src\Microsoft.IdentityModel.Xml\EnvelopedSignatureWriter.cs:line 139

This appears to be because the inner writer is still positioned inside the unfinished start element when the EnvelopedSignatureWriter captures the signature position in its internal buffer.
I would expect the behaviour to be the same as calling WriteStartElement, WriteElementString or WriteValue, which will "finish" the started element before proceeding to start writing the next node as content of the element.
As a workaround, you can call WriteComment to finish the started element, but that does emit an unwanted comment before the signature.

A possible fix is to check the current write state, and if the state isn't within content, call WriteWhitespace(" ") on the InnerWriter to force it to transition to the content element, then manipulate the buffer to remove the single character that was added before taking the position of the signature.
It feels pretty hacky, but I haven't been able to find a clean way to trigger the XmlWriter to complete the element.

@Tragedian you are right in suspecting that our scenario was focused on Reading not Writing.
We will see when we can fit this in.

If you'd be interested, I'm open to submitting a pull request for this issue.

@Tragedian we just got back from the holidays.
PR's are always welcome.

Set to P1 to match the EnvelopedSignatureReader in this release would provide a nice round trip experience.

Fixed with: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/1195


bug: npd_versioon  spelling mistake

npd_versioon should spelling  as npd_version, We should adjust it in time.

done;

Get.


[TreeView] Duplicate nodeId can cause maximum call stack size exceeded error

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

A TreeView that has two TreeItems with the same nodeId can throw the following error:
Uncaught RangeError: Maximum call stack size exceeded
Expected Behavior 🤔

A warning rather than an error should occur.
Steps to Reproduce 🕹

Steps:

Create a TreeView with the following structure:

<TreeView defaultExpanded={["1"]}>
  <TreeItem nodeId="1" label="Applications">
    <TreeItem nodeId="1" label="Calendar" />
  </TreeItem>
</TreeView>

Demo: https://codesandbox.io/s/nostalgic-platform-vyns0?file=/src/Demo.js
Context 🔦

While the nodeId should always be unique, if an accident happens, it would be great if the TreeView could handle that case by showing a warning instead of crashing.
Your Environment 🌎

Tech
Version

Material-UI-Lab
v4.0.0-alpha.53

React
v16.8.0

Browser
chrome

Duplicate of #20832

The observed effect between #20832 and #21144 is the same but is the root cause identical?
The reproduction of these two issues looks different enough to make me wonder. I think that we would need to add these two new tests with the fix. Should we keep it open not to forget (we usually tend to completely ignore duplicate issues) and in the eventually that the root cause is different, that we can't fix both at the same time?

The observed effect between #20832 and #21144 is the same but is the root cause identical?

I don't know and you don't seem to know either. If you can identify two different reproductions that lead to different errors then go for it. That's what everyone else is doing. Otherwise I don't know why we should keep issues open because you "wonder"?

@eps1lon The reasoning was in this order:

the reproduction example between the two issues looks unrelated
the infinite loop RangeError crash seems to occur in two different methods

https://github.com/mui-org/material-ui/blob/a2e0e32b25b171e0359d80a685e8dede24975254/packages/material-ui-lab/src/TreeView/TreeView.js#L494
vs.
https://github.com/mui-org/material-ui/blob/a2e0e32b25b171e0359d80a685e8dede24975254/packages/material-ui-lab/src/TreeView/TreeView.js#L408

Not sure what you want me to do. Both repros use duplicate ids, the prior issue already has a test. Is there something specific beyond a "concern" or "possibly unrelated"?

@eps1lon Sorry for the wasted time, ignore me.
I thought #20832 was only about an edge case during the unmount, I didn't realize the demo had a duplicate id too. It looks definitely like a duplicate.
I thought we were discussing a broader topic on issue policy optimization: what should we do when two issues are showing the same error but using two different (enough) ways to surface it? But it's not an occurrence of this.


Query Regarding a Potential Typo in the Narcissus.ipynb File

I've been using your ipynb file recently and came across a minor confusion that I haven't seen discussed anywhere else. I thought I'd bring it up here and ask for clarification, in case I've misunderstood something. I hope you won't mind my question!

You can remove this step since in the next line we clean the gradient in the optimizer, sorry for the repeat code.

Thank you for your response!


Linkerd crd helm chart

Don't know why I thought so but the helm chart won't trigger a update so this isn't a good workaround.


couldn't create file

some trouble with launchig DS Patcher, no have idea what is that

duplicate of #2 - do you already have a dreamseeker.exe.bak file?


Enforcer custom filter

Description:
Amali said that we need a doc on Enforcer custom filter by the end of this week (10th March).
More info
Amali mentioned

Mentioned that it would be similar to https://apim.docs.wso2.com/en/latest/deploy-and-publish/deploy-on-gateway/choreo-connect/extensions/custom-filters/
but instead of maven we now need gradle
Amila has test code.
Amila mentioned
Amila provided this doc [1].
Amila mentioned that we will be using choreo.connect as the implementation details initially
He will provide the steps to build from apk repo later.

[1] https://docs.google.com/document/d/1K7VPjCR-QwuNKGATW4FGv6ZTR83gPbc4GzvzUCVjx_g/edit#

Contact person is Amila.

Link to live doc: https://apk.docs.wso2.com/en/latest/apk-deck/gateway/enforcer/custom-filters/

Sanjeewa suggested and (Amali seconded it) that the location of the file should be changed as follows:


fix format specification

Hi, i've fixed some issues with type fromat specification in query parameters and models. So with this fixes types like int64 and decimal correctly passes to swagger schema.

Also SwaggerTypeMappingTests shuld be fixed because mutual influence.
Should type mapping be static?

Looks good to me!
No it probably shouldn't be static, I agree that the tests aren't in great shape. I'm still trying to find some time to go all out and re-write this to support OpenAPI 3.


Error installing

If this is the package for www.pagefronthq.com, then there are problems trying to load the package, using the (somewhat sparse) docs:
ember install ember-pagefront --app=mindstorm
Future versions of Ember CLI will not support v4.2.1. Please update to Node 0.12 or io.js.
version: 1.13.8
The option '--app' is not registered with the install command. Run ember install --help for a list of supported options.
Installed packages for tooling via npm.
installing ember-pagefront
install package ember-cli-deploy
Installed packages for tooling via npm.
create .pagefrontrc
create config/deploy.js
key is not defined (Error in blueprint template: /Users/john/Devel/ember/mindstorm/node_modules/ember-pagefront/blueprints/ember-pagefront/files/.pagefrontrc)
ReferenceError: key is not defined (Error in blueprint template: /Users/john/Devel/ember/mindstorm/node_modules/ember-pagefront/blueprints/ember-pagefront/files/.pagefrontrc)
at eval (eval at  (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/node_modules/lodash/string/template.js:214:12), :8:11)
at processTemplate (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/lib/models/file-info.js:13:52)
at /Users/john/Devel/ember/mindstorm/node_modules/ember-cli/lib/models/file-info.js:94:20
at lib$rsvp$$internal$$tryCatch (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:493:16)
at lib$rsvp$$internal$$invokeCallback (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:505:17)
at lib$rsvp$$internal$$publish (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:476:11)
at lib$rsvp$asap$$flush (/Users/john/Devel/ember/mindstorm/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1198:9)
at doNTCallback0 (node.js:417:9)
at process._tickCallback (node.js:346:13)

I think even calling the docs sparse right now is quite generous of you :smile:!
Sorry you ran into issues here! This is definitely a bug, in that the error messages need to be much more clear about what is happening and what you can do to fix it. I'm gonna leave this issue open until that is corrected.
In the meantime, you can fix this by first creating the mindstorm app in the pagefront dashboard. Once you do that, it will show you a full install command that you can copy and paste into the terminal. That should get you going.
Thanks a lot for reporting this! Feel free to shoot me an email at<EMAIL_ADDRESS>if you have any questions at all.

Thanks. I used the command given when I created the app on the dashboard. While it didn't throw the errors above, it does still give:
The option '--app' is not registered with the install command. Run `ember install --help` for a list of supported options.
The option '--key' is not registered with the install command. Run `ember install --help` for a list of supported options.

Another valid issue. Those are just warnings, so you can safely ignore them. However, it is indeed another thing we need to get rid of. Thanks for pointing it out!
Glad you got it installed now though. Thanks for following up!

Having more problems installing. Wanted to get up to date. First attempt was to update the version in the package.json file and 'npm install'. That seemed to install, but trying to do an 'ember deploy' failed with:
- Missing required config: `key`
|
+- didFail
Error: Missing required config: `key`
Error: Missing required config: `key`
    at Class.CoreObject.extend.ensureConfigPropertySet (/Users/John/Dev/Ember/mindstorm/node_modules/ember-cli-deploy-plugin/index.js:41:13)

Attempting to reinstall ('npm uninstall' followed by ember install...) fails with:
ember install ember-pagefront --app=mindstorm
version: 1.13.13
The option '--app' is not registered with the install command. Run `ember install --help` for a list of supported options.
Installed packages for tooling via npm.
installing ember-pagefront
  install package ember-cli-deploy
Installed packages for tooling via npm.
  create .env.deploy.production
  identical config/deploy.js
key is not defined (Error in blueprint template: /Users/John/Dev/Ember/mindstorm/node_modules/ember-pagefront/blueprints/ember-pagefront/files/.env.deploy.production)
ReferenceError: key is not defined (Error in blueprint template: /Users/John/Dev/Ember/mindstorm/node_modules/ember-pagefront/blueprints/ember-pagefront/files/.env.deploy.production)

Ugh. My bad (mostly). I forgot to add the --key= to the ember install command. Once I did that, it all worked.

@jtsom Sorry for the confusion on that. That's definitely still our fault. These are not things you should have to be thinking about at all. We will improve this process, it's just a matter of time. I apoligize that it has taken so long.

@jtsom Just wanted to follow up on this. As of 0.10.9, it is now possible to simply ember install ember-pagefront --app=mindstorm and ember deploy production. No need to create the app in the dashboard first. We've also done a lot fo work to improve the error messages and make it much more obvious what is going wrong.
I'm Gonna go ahead and close this issue now but please let me know if you have any other issues. Thanks for your help on all this!


debug protractor

Hello. I have spend my entire day trying to launch the protractor test in "debug".
ideally I would like to debug it from visual studio but I did not manage.
I tried both ways from the accepted answer on stackoverflow:
https://stackoverflow.com/questions/54016095/how-to-debug-protractor-in-vs-code
I also looked at this video: https://www.youtube.com/watch?v=6aPfHrSl0Qk&t=1208s
I really lost my day today... Any help would be really appreciated.

Can you elaborate? Trying to debug protractor?  Are aware that protractor is an E2E test suite?  So it is used to test your application

Can you elaborate? Trying to debug protractor? Are aware that protractor is an E2E test suite? So it is used to test your application

looking at stackoverflow link poster linked, i think he mean launching debugger on protractor app's code itself (i.e. the /e2e directory in the repo).


NPR extractor failures

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2020.03.01
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log
$ youtube-dl https://www.npr.org/2020/03/02/811280651/the-economic-lessons-of-a-free-solo-climb --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.npr.org/2020/03/02/811280651/the-economic-lessons-of-a-free-solo-climb', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2020.03.01
[debug] Python version 3.8.1 (CPython) - Linux-5.5.7-2-ck-skylake-x86_64-with-glibc2.2.5
[debug] exe versions: ffmpeg 4.2.2, ffprobe 4.2.2, rtmpdump 2.4
[debug] Proxy map: {}
[Npr] 811280651: Downloading JSON metadata
ERROR: An extractor error has occurred. (caused by KeyError('story')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 530, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/npr.py", line 61, in _real_extract
story = self._download_json(
KeyError: 'story'
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 530, in extract
ie_result = self._real_extract(url)
File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/npr.py", line 61, in _real_extract
story = self._download_json(
KeyError: 'story'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 797, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 543, in extract
raise ExtractorError('An extractor error has occurred.', cause=e)
youtube_dl.utils.ExtractorError: An extractor error has occurred. (caused by KeyError('story')); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure tocall youtube-dl with the --verbose flag and include its complete output.

Description
Some NPR links fail to download with the log above. Example links:

https://www.npr.org/2020/03/02/811280651/the-economic-lessons-of-a-free-solo-climb
https://www.npr.org/2020/02/28/810546698/coronavirus-a-view-from-hong-kong
https://www.npr.org/2020/02/26/809732454/the-rise-and-fall-and-rise-of-nascar

Downloads fail regardless of the download link availability on the NPR site.

hi


How to add private Maven repositories with credentials

Hello,
I don't know if this is the place but I am playing around with the Teiid operator and was wondering if it was possible to add a private Maven repositories with credentials. We're using our own Nexus and know that you can add a Maven repository to the VirtualDatabase resource, but I cannot figure out how  to provide credentials.
Kind regards,
Jacob

Unfortunately, it does not have the feature to provide the secrets yet for private nexus repo, can you open a JIRA at https://issues.redhat.com/projects/TEIIDTOOLS/summary for this, I will see if I can add this.

Done. TEIID-950.
Thnx.
Kind regards,
Jacob

From: Ramesh Reddy<EMAIL_ADDRESS>Sent: Monday, March 2, 2020 2:38:10 PM
To: teiid/teiid-operator<EMAIL_ADDRESS>Cc: Jacob Hoeflaken<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [teiid/teiid-operator] How to add private Maven repositories with credentials (#81)
Unfortunately, it does not have the feature to provide the secrets yet for private nexus repo, can you open a JIRA at https://issues.redhat.com/projects/TEIIDTOOLS/summary for this, I will see if I can add this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/teiid/teiid-operator/issues/81?email_source=notifications&email_token=ABF6OGMB5EJ5C7J6OA6GJOTRFOZEFA5CNFSM4K7IGN62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENPKRKA#issuecomment-593406120, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABF6OGJB7NE5IGYRR24QXALRFOZEFANCNFSM4K7IGN6Q.

Will continue this in TEIIDTOOLS-950


[FEATURE] Improved Favorite Bar

Problem: Currently, the favorites bar is very inconvenient, especially when exceeding 3-4 features, or when the feature names are long. It would be very interesting to have the ability to customize the favorites bar, which is currently very inconvenient and allows you to see very few elements.
I've thougth about three ways to do that:

Creating a more compact version of the existing one, with smaller images, fonts, and uses.
Creating an additional page where only the favorite actions are displayed, divided into categories (spell, feature...) and the main stats. 3. Switching the space occupied by the favorite section,  and the sections of senses, equipment, languages, and tools

^ This

I'm personally very surprised that hiding the side hides some of the most edited/referenced information on a sheet; hp, ac, movement, favourite actions (except art).
In contrast I definitely don't need to see what race background and creature type I am at all times.
It seems to me that some of the collapsible regions really aren't thought out at all.

Perhaps having the favorites bar scroll independently form the rest of the sheet would be of added value as well.


Dropbox Sample for Mac

Hi...am not sure whether this question is already asked, i went through the book and issues but couldn't find.
My question is whether there is any sample app which uses ensembles app in OSX to sync over dropbox. Idiomatic for Mac doesn't have dropbox sync feature like Idiomatic for iOS.
Jinto

No sample app for that, no. It is quite similar to iOS, but authentication works a bit differently. Read the Dropbox Core API README file for OS X. It describes what you need to do to authenticate.


[Sprint 44] XD-2764 Avoid escaping topic name twice

Due to a bug in KafkaMessageBus.escapeTopicName(), "_" is re-converted on already escaped topic names (even if it is a valid character). This causes the initialization of the topic states to read the wrong initial offsets, subsequently causing the test to fail. This behaviour is observable only on already cleaned (pruned) topics.

I was gonna merge this but now realize the initial behavior is correct:
When there is an escape mechanism, the escaping character must always be escaped itself, or else you can't distinguish between "normal" and "escaped" cases. (e.g. in java, a backslash is \\).
Moreover, not sure I understand what you mean with "re-escaping". What should be passed to the escape method are un-escaped names only.

Well, the fix to the test is necessary anyway. As for the escaping, I think it's a misnomer anyway. What we are doing is re-encoding topic names by replacing invalid characters with valid sequences of characters, so in that context, I don't see the need for replacing _, but it's such a minor concern that from my point of view it can go one way or another.

Well, we're not encoding topic names. (or at least that's not what the method did when I wrote it).
We're encoding bus binding names to be kafka compliant topic names.

Okay. Let me know if you'd prefer me to revert the changes to KafkaMessageBus. The other commit stands on its own.

I think I see what you mean. And also that part about it being misnamed.
The change to KafkaMessageBus should not be applied indeed. But are you saying the rest fixes something on its own?

I can test that on my own.
Also, the "fix" on KMB is currently harmless because we never unescape, but..

Yeah, there are two commits. One that fixes the problem that we had in the test, because escaping was applied twice and the test read initial offsets from the wrong topic. So I've changed that.
I've added the second commit later, since I couldn't see the need to modify a topic name that was already valid. But again, that, in and by itself is a different discussion (since, yes, we never unescape).

Merged on master as 683e35e6e71a3ff77908455cdf811df1caff8f6b. Another PR for maintenance to come


The script creation icon is not displayed

Godot version:
3.2 stable mono
OS/device including version:
win10 64 home
Issue description:
When a new script is created and the C # option is accepted, the language icon is not displayed.
Steps to reproduce:
Add a script to any node, when choosing the language select C #, now you can see that the icon does not appear symbolizing the language.

Minimal reproduction project:

Hello. I'm a new contributor. I think this issue is accessible for me. I will take a look into it

If it doesn't happen to you in the first script, then try adding several (you will have to have several nodes to be able to add more than one script).


Minor improvements based on feedback from peers

First of all, kudos for building this minimal and great theme. Secondly, apologies for a PR with multiple things without creating issues first. Let me know if I should break this down, here are the minor improvements I suggest.

User network name in place of links in header section as it looks cleaner for showing more number of profiles
Use hyphen (-) in place of comma (,) for position as it is a more firm indicator of what is my role in an organization (based on some feedback from peers)
Increased the base size from 12px to 13px, 12 looked a bit too small
Make the theme responsive via media query (screenshot attached)

Remove the background color on body when printing, it was breaking the print screen for me (screenshot attached)

@ainsleyc : Any update on this? Please choose to merge or decline! I will in that case deploy a fork.
Thanks 👍

Oops, sorry missed this. I'll try to have a look over the weekend, sorry
for the delay.
On Wed, Mar 21, 2018 at 2:46 AM Divyendu Singh<EMAIL_ADDRESS>wrote:

@ainsleyc https://github.com/ainsleyc : Any update on this? Please
choose to merge or decline! I will in that case deploy a fork.
Thanks 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ainsleyc/jsonresume-theme-onepage/pull/8#issuecomment-374881566,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADuKhng_i7d-54Kpuu_Y_aDauExGd-Fvks5tgiF2gaJpZM4Oxmcw
.

Thanks for the pull request!


FIX: issue when DataSource request is empty

If client requested empty string in DataSource endpoint ClassMethod GetDataSource() return status 200. The PR is relative to https://github.com/intersystems-community/DeepSeeWeb/issues/121

@eduard93 can you merge this one?


Synchronization questions

When synchronizing between master and slaves, is it possible for:

A slave to indicate that he is ready, i.e. the master should not increment the time until all slaves are done with their current step. Otherwise, one slave may start to lag behind.
A slave to indicate when he needs a new time event, so the triggers or timeouts that he sets are transmitted to the master, and the master will generate a time event as requested.
The master to pause time or change the simulation speed, and this will update the planned triggers. For example, if I've planned a trigger in 10s time, and the speed factor changed from 1 to 2, I expect the event in 5s. And when I pause time, the event should not occur until I continue again.

I think you're referring to synchronizing non-paced simulation time. I would love to implement this, it's is still missing in the implementation, and it's crucial in order to be able to scale simulations.
From the docs on Synchronization:

WARNING: this is an experimental feature, and currently only supports paced mode.

https://github.com/enmasseio/hypertimer#synchronization

Thanks for the reply, but actually, question 1 and 3 were aimed at paced mode.
In 1, if the master increases the time every second, and a slave is not ready processing the last time step, how can the slave tell the master to wait a bit?
For 3, when the slave has set some triggers or timeouts, how are they affected when the master pauses or changes the speed?

Sorry for the late reply.
This is an interesting point. In paced (continuous or "animated") mode, would you expect/want a distributed system to just continue in parallel and ignore the duration of actions themselves? Or do you still want everything to run in deterministic order? If one event takes place at t=0s and execution takes 2s, and another event takes place at t=1s, should this event wait for the first to be finished and thus start 1s too late?
I think what you are looking for is a paced and deterministic mode? The experimental support for synchronization doesn't do things in a deterministic order. And I'm personally most interested in a non-paced + deterministic mode :).


Identity Verification with EvidentID

Is your feature request related to a problem? Please describe.
Perform the required improvements to the existing Evident connector [1][2].

[ ] Capability to define verification attributes from the management console.

ATM, the connector asks to validate the US Drivers License of the user. This needs to be able to configurable from the UI. One approach to this would be having a drop-down list of verification attributes provided by Evident. There could be more user-friendly/efficient ways to get this done.

[ ] Current connector pulls the name of the verified user from Evident and matches it with the name given to the WSO2 side. This should also be able to either change or enable/disable. Need to discuss further.
[ ] Extend Evident connector use cases.

ATM, the connector can only be engaged in the self-registration flow. But there could be more use cases that we can use IDV.

[1] - https://store.wso2.com/store/assets/isconnector/details/1a85a226-177c-4a90-8da3-b142c46ae658
[2] - https://github.com/wso2-extensions/identity-verification-evident/tree/v1.0.0/docs
[3] - https://everything1know.wordpress.com/2020/06/03/identity-verification-with-wso2-identity-server-and-evident-id/

I'm working on this

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


ENH: update SuperLU to version 6.0.1

This was quite a pain to untangle. This updates to the latest commit in the master branch of https://github.com/xiaoyeli/superlu, which has a few fixes on top of the 6.0.1 tag. Some of our patches have been upstreamed, others are still to be upstreamed - this is easier now that SuperLU is actively maintained on GitHub.
Closes gh-19092
Potential follow-ups:

upstreaming the remaining patches
enable 64-bit build of SuperLU (needs to go with an ILP64 BLAS, so is a little tricky)
convert to using a git submodule perhaps (after dropping the setup.py build)

EDIT: for reference, here are the previous SuperLU update PRs: gh-7554, gh-12243

Recording the refguide check failure for future reference:

===================
scipy.sparse.linalg
===================

scipy.sparse.linalg.SuperLU
---------------------------

File "/tmp/tmpezm8vra_/builtins", line ?, in SuperLU
Failed example:
    lu.perm_r
Expected:
    array([0, 2, 1, 3], dtype=int32)
Got:
    array([2, 1, 3, 0], dtype=int32)

File "/tmp/tmpezm8vra_/builtins", line ?, in SuperLU
Failed example:
    lu.perm_c
Expected:
    array([2, 0, 1, 3], dtype=int32)
Got:
    array([0, 1, 3, 2], dtype=int32)

File "/tmp/tmpezm8vra_/builtins", line ?, in SuperLU
Failed example:
    lu.L.A
Expected:
    array([[ 1. ,  0. ,  0. ,  0. ],
           [ 0. ,  1. ,  0. ,  0. ],
           [ 0. ,  0. ,  1. ,  0. ],
           [ 1. ,  0.5,  0.5,  1. ]])
Got:
    array([[ 1. ,  0. ,  0. ,  0. ],
           [ 0.5,  1. ,  0. ,  0. ],
           [ 0.5, -1. ,  1. ,  0. ],
           [ 0.5,  1. ,  0. ,  1. ]])

File "/tmp/tmpezm8vra_/builtins", line ?, in SuperLU
Failed example:
    lu.U.A
Expected:
    array([[ 2.,  0.,  1.,  4.],
           [ 0.,  2.,  1.,  1.],
           [ 0.,  0.,  1.,  1.],
           [ 0.,  0.,  0., -5.]])
Got:
    array([[ 2. ,  2. ,  0. ,  1. ],
           [ 0. , -1. ,  1. , -0.5],
           [ 0. ,  0. ,  5. , -1. ],
           [ 0. ,  0. ,  0. ,  2. ]])

The results are correct; the decomposition still reconstructs, but the numerical values have all changed. Adding a # may vary.


[Suggestions] Add 10Bit for Radarr v3

Add json template for h265 10bit

Being you already prefer x265 you could just use the x265 with the HDR CF.
And give them like a score of 10 each.
This way if you get a x265 it will get a score of 10 but if it has both it gets 20.
If it doesn't show HDR I will need a few filename examples so I can do a few test.
You could also pm on discord if you don't want to share them here

10bit does not equal HDR. One release type that is common is 10bit h265 bluray rips. Which would not qualify as HDR.

Added: https://github.com/TRaSH-/Tutorials-FAQ/commit/ebbc87ef146373f61b32ea53ecdd81b03a38eb9a


[BUG] The backwards compatible parquet annotation MAP_KEY_VALUE crashes on read

Describe the bug
This is similar to https://github.com/NVIDIA/spark-rapids/issues/6968 but it is for maps.  In the parquet spec a map can be annotated with MAP_KEY_VALUE instead of MAP. But when CUDF sees this is does not treat it like a MAP, but returns the data without a LIST, and ends up throwing out some data. This corresponds to the test MAP_KEY_VALUE in https://github.com/NVIDIA/spark-rapids/pull/6914
This is really a CUDF issue so I will file something there for this. But we will need to enable the test once it is fixed.

The CUDF issue is https://github.com/rapidsai/cudf/issues/12044


chore(main): release 2.131.0

:robot: I have created a release beep boop
2.131.0 (2024-07-22)
Features

pg-usage-data: Add cache to batch tracking data (#4308) (117f72a)
Wolfi-based Docker images (#4276) (2e461c8)

Bug Fixes

build: Incorrect package used for GPG (#4355) (aa2fd70)
build: Missing gpg-agent for the SaaS build (#4356) (c655c73)
Non-admin project Role request to /projects/ID/features/ID Causes Crash (#4289) (bce6530)
Styling alert for API usage banner (#4360) (61cfdbf)
Update of organisations during flags and admin access (#4344) (7a9edca)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v2.131.0
:sunflower:


SDN & ROK WHO Region coding errors

For entries associated with SDN and ROK, there are multiple WHO regions identified. Some SDN entries coded as AFRO, some ROK entries coded as SEARO.
Could be these entries should actually be coded for SSD (which is AFRO) or DPK (which is SEARO), but doesn't look like that from cursory review of comments.
Does suggest a second round of scrutiny on SDN / SSD, ROK / DPK needed.

The most likely cause I can think of is records reassigned to a new country without WHO region being changed.
We should check that WHO Region and ISO numeric continues to align with the country name and ISO code.
I believe that updating these fields could be done automatically after the data is returned from volunteers.

WHO region, ISO numeric should be reassigned when manually cleaned data is merged.
Open in #56.


Support application of polymorphic operators in typed builder

Closes #2559
Closes #2581
It appears that the typed builder is not currently able to handle constructing application of polymorphic operator.
This adds a regression test for this omission and a fix to unblock it.
The fix is to replace the limited and more ad-hoc type compatibility check used in the builder previously with the same type unifier we use for type checking. The result is

More code reuse.
More correct checks on type compatibility in the builder.
Less code.

This will unblock #2552.

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[x] Documentation added for any new functionality
[x] Entries added to ./unreleased/ for any new functionality

In conversation last week, @Kukovec rejected this change in preference for avoiding use of ScopedBuilder and instead using the unsafe builder methods for converting quint.
I am fine with this approach in principle, however afaict, there is no non-scope-safe builder implementation that has parity with the scoped builder. We don't even have an abstract interface to build against for putting this together. As a result, the scope or work required is much larger than the two line change I've proposed here.
I am asking that we move forward with my proposal here, in light of the following considerations:

the scoped builder is broken in this regard: it is impossible to build the application of polymorphic operators
the scoped builder is meant to be a helper operation that expedites other aims, it is not a goal in itself, whereas completing the integration with quint is high priority
if it deemed important to enrich the builder with more type guarantees during construction or to add a non-scoped version satisfying the same interface, this can easily be added later, replacing my change.

Codecov Report

Merging #2560 (ccac59d) into main (eab4d23) will increase coverage by 0.00%.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##             main    #2560   +/-   ##
=======================================
  Coverage   78.46%   78.46%
=======================================
  Files         445      445
  Lines       15626    15628    +2
  Branches     2534     2572   +38
=======================================
+ Hits        12261    12263    +2
  Misses       3365     3365

Impacted Files
Coverage Δ

...che/tla/typecomp/signatures/FlexibleEquality.scala
68.96% <50.00%> (-1.41%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks for the review!


fix (batcher): nonce verification order in handle_message function

Description

The current implementation of the handle_message function in the batcher performs nonce verification using the check_nonce_and_increment method, which increments the nonce before checking the proof. This order of operations may introduce vulnerabilities, specifically to replay attacks and potential denial-of-service (DoS) scenarios.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


results page is empty any idea what i'm doing wrong ?

thanks for your work
i have installed you package but the results page is empty any idea what i'm doing wrong ?

@quasiperfect Please follow this documentation
https://spatie.be/docs/laravel-health/v1/introduction

thanks i just needed to register the checks


feat: Enqueue Klab jobs when projects geometry is changed and KLAB is enabled

This PR allows to enqueue Klab jobs when project geometry or impact areas changes. To do so, new env variable called KLAB_ENABLED needs to be set to true.
I am also adding all new required columns to Project model (please see migrations) and basic structure of Klab jobs -- these are more or less dummy now and I will code rest of the stuff when I start working on appropriate tickets.
Testing instructions
Set KLAB_ENABLED to true and verify that Klab::SubmitContextsJob and Klab::CalculateImpactsJob are enqueued.
Tracking
https://vizzuality.atlassian.net/browse/LET-1351
https://vizzuality.atlassian.net/browse/LET-1356

looks great, but we need a new env var. if it's OK to merge this while the env var is not yet available in staging, I'll add it in a separate PR, otherwise I'd add it here - let me know!

No need for new variable now @agnessa. KLAB_ENABLED  is required to turn feature on so if omit it for now, it will work same way as before. I also plan to merge all stuff for BC3 feature for some time into klab-integration branch so it will not interfere with staging. After we have some reasonable part of BC3 functionality done, I will push it to Stage so it can be tested at once.


rs-pointcloud-stitching installation

Required Info

Camera Model
D435

Firmware Version
2.50.0

Operating System & Version
Ubuntu 18.04

Platform
PC

SDK Version
2.0

Language
Python

Issue Description
I want to use the rs-pointcloud-stitching in the wrappers.
Its usage is pretty well documented, but it assumes it is already installed.
I can't find a way to install it.
Any insight on how to is welcome.
Thanks in advance.

Hi @Testoxe  It is possible to perform point cloud stitching with Python, though there is not an official pre-made point cloud example program for doing so.  Whilst stitching can be done via the PCL or Open3D libraries, if you would prefer to do it completely within the RealSense SDK with Python then the instruction rs2_transform_point_to_point may meet your needs.
This instruction is an 'affine transform', where separate sets of coordinates such as a pair of individual point clouds have their position and rotation set to the same values in 3D space.  The instruction is discussed at https://github.com/IntelRealSense/librealsense/issues/5583

Alternatively, if you have two cameras and are able to use ROS and the RealSense ROS wrapper then Intel provide a stitching tutorial here:
https://github.com/IntelRealSense/realsense-ros/wiki/Showcase-of-using-2-cameras

My priority is to check how accurate is the rs-pointcloud-stitching program first to see if I can use it in my case, so it's not obligatory for me to use Python.
I'm just trying to make it work but I can't find how to install it. I don't mind if it uses cpp.
Thank you for you detailed answer though, it will definitely help me in the future.

As far as I am aware, there is no feedback available from other RealSense users regarding accuracy of the C++ rs-pointcloud-stitching  example program.  The instruction guide for the program at the link below indicates though that the MATLAB software tool and an additional tool for MATLAB called the Computer Vision Toolbox are required by this example program to calibrate two cameras together.
https://github.com/IntelRealSense/librealsense/blob/master/wrappers/pointcloud/pointcloud-stitching/doc/pointcloud-stitching-demo.md
If you are able to use C++ then it would be much easier to use the rs-kinfu SDK example.  This program only requires a single camera that you move around the scene to progressively build up a pointcloud in real-time by 'fusing' frames together instead of stitching separate point clouds from different views.  Once you are satisfied with the amount of detail in the pointcloud, you can stop adding frames and export the finished cloud as a .ply format pointcloud file.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/opencv/kinfu

I need to visualize a real-time panorama with 2 cameras, so the rs-kinfu is not going to help.
I have already installed the MATLAB's Stereo Camera Calibrator software so that's not a problem.
The problem is, when following the installation doc, I reach a step where I need to run rs-pointcloud-stitching command:

Now, run rs-pointcloud-stitching:
rs-pointcloud-stitching C:\pc_stitching_ws

But when I do, I get an error:

rs-pointcloud-stitching: command not found

I am not familiar with the rs-pointcloud-stitching example program.  I would assume though that it would first have to be built from its source code, and then you would input the rs-pointcloud-stitching command from the directory on your computer that it had been built in.

I found a solution.
In order to use the rs-pointcloud-stitching program, BUILD_PC_STITCHING parameter should be true when installing the library.
Small tuto for anyone having the same problem:

Clone repo
Open a console in the root folder and execute following commands:
mkdir build && cd build
cmake ../ -DBUILD_EXAMPLES=true -DBUILD_PC_STITCHING=true
sudo make uninstall && make clean && make && sudo make install

You should then be able to use rs-pointcloud-stitching command from the console, you can also find it in usr/local/bin by default.
Would be nice if this could be added to the readme.

Thanks so much @Testoxe for sharing the solution that worked for you with the RealSense community!


wiki instructions for installing GCC trunk on macOS fail

[X] I am not reporting a bug or asking for a new feature
[X] I am asking a general question about, e.g., the internal workings of this software, the direct use of this software, or use cases for this software, etc.
[X] I have already searched for the answer to my question on Google and Stack Overflow

The OpenCoarrays wiki suggests the following command for installing the GCC trunk on macOS:
brew upgrade --fetch-HEAD --HEAD gcc

which gives the following output:
$ brew upgrade --fetch-HEAD --HEAD gcc
Usage: brew upgrade [options] formula

Upgrade outdated, unpinned formulae (with existing and any appended brew formula
options).

If formula are given, upgrade only the specified brews (unless they are
pinned; see pin, unpin).

Unless HOMEBREW_NO_INSTALL_CLEANUP is set, brew cleanup will be run for the
upgraded formulae or, every 30 days, for all formulae.

    -d, --debug                      If brewing fails, open an interactive
                                     debugging session with access to IRB or a
                                     shell inside the temporary build directory
    -s, --build-from-source          Compile formula from source even if a
                                     bottle is available.
        --force-bottle               Install from a bottle if it exists for the
                                     current or newest version of macOS, even if
                                     it would not normally be used for
                                     installation.
        --fetch-HEAD                 Fetch the upstream repository to detect if
                                     the HEAD installation of the formula is
                                     outdated. Otherwise, the repository's HEAD
                                     will be checked for updates when a new
                                     stable or development version has been
                                     released.
        --ignore-pinned              Set a 0 exit code even if pinned formulae
                                     are not upgraded.
        --keep-tmp                   Don't delete the temporary files created
                                     during installation.
    -f, --force                      Install without checking for previously
                                     installed keg-only or non-migrated
                                     versions.
    -v, --verbose                    Print the verification and postinstall
                                     steps.
        --display-times              Print install times for each formula at the
                                     end of the run.
    -h, --help                       Show this message.
Error: invalid option: --HEAD

Fixed: https://github.com/sourceryinstitute/OpenCoarrays/wiki/Using-Homebrew-to-upgrade-GCC-to-trunk


Yashasvi/eslint deprecated tags

Custom ESLint rule that enforces version and at least a sentence description for @deprecated tags.
Fixes #4968.

I can fix up the non-UI lint errors.

Do you intend to add tests?

Your lint rule caught this (core/backend/src/BackendHubAccess.ts)
/**
 * @deprecated in 3.x.
 * @internal
 */
export type CheckpointArg = DownloadRequest;

But failed to catch this:
  /**
   * download a v1 checkpoint
   * @deprecated in 3.x.
   * @internal
   */
  downloadV1Checkpoint: (arg: CheckpointArg) => Promise<ChangesetIndexAndId>; // eslint-disable-line deprecation/deprecation

Please write some tests to verify expected behavior with a wide variety of inputs.

Make sure to cover all deprecatable syntax constructs and comment syntaxes in your tests. Here are some recommended tests (but please enumerate the syntax constructs this should work for, i.e. class methods, functions, classes, namespaces, etc)
// @deprecated
function canWeFailForNotUsingADocCommentPlease {}

/* @deprecated */
let canWeFailOnThisOnePlease2 = () => {};

/** @deprecated */
class shouldFailSinceNoVersionOrSentenceGiven {};

You can look at tools/eslint-plugin/tests/no-internal-barrel-imports.js (which seems to be the only eslint tests we have) for inspiration?

Your lint rule caught this (core/backend/src/BackendHubAccess.ts)
/**
 * @deprecated in 3.x.
 * @internal
 */
export type CheckpointArg = DownloadRequest;

But failed to catch this:
  /**
   * download a v1 checkpoint
   * @deprecated in 3.x.
   * @internal
   */
  downloadV1Checkpoint: (arg: CheckpointArg) => Promise<ChangesetIndexAndId>; // eslint-disable-line deprecation/deprecation

Please write some tests to verify expected behavior with a wide variety of inputs.

I think I may need to cover more syntax nodes. Will work on writing some tests.

Make sure to cover all deprecatable syntax constructs and comment syntaxes in your tests. Here are some recommended tests (but please enumerate and test the syntax constructs this should work for, i.e. class methods, functions, classes, namespaces, etc)
// @deprecated
function canWeFailForNotUsingADocCommentPlease {}

/* @deprecated */
let canWeFailOnThisOnePlease2 = () => {};

/** @deprecated */
class shouldFailSinceNoVersionOrSentenceGiven {};

You can look at tools/eslint-plugin/tests/no-internal-barrel-imports.js (which seems to be the only eslint tests we have) for inspiration.

Okay, I will get started on this.

--[ FAILURE: @itwin/core-backend ]--------------------------[ 19.39 seconds ]--
@GytisCepk ?
itwinjs-core/core/backend/src/BackendHubAccess.ts(168,1)
itwinjs-core/core/backend/src/BackendHubAccess.ts(217,3)
@paulius-valiunas ?
itwinjs-core/core/backend/src/AliCloudStorageService.ts(13,1)
itwinjs-core/core/backend/src/CloudStorageBackend.ts(25,1)
itwinjs-core/core/backend/src/CloudStorageBackend.ts(35,1)
itwinjs-core/core/backend/src/CloudStorageBackend.ts(52,1)
itwinjs-core/core/backend/src/CloudStorageBackend.ts(174,1)
itwinjs-core/core/backend/src/IModelHost.ts(201,3)
itwinjs-core/core/backend/src/IModelHost.ts(355,3)
itwinjs-core/core/backend/src/IModelHost.ts(365,3)
--[ FAILURE: @itwin/core-common ]---------------------------[ 14.11 seconds ]--
@swbsi
itwinjs-core/core/common/src/BackendTypes.ts(19,1)
itwinjs-core/core/common/src/BackendTypes.ts(22,1)
itwinjs-core/core/common/src/BackendTypes.ts(25,1)
@paulius-valiunas
itwinjs-core/core/common/src/CloudStorage.ts(13,1)
itwinjs-core/core/common/src/CloudStorage.ts(25,1)
itwinjs-core/core/common/src/CloudStorage.ts(35,1)
itwinjs-core/core/common/src/CloudStorage.ts(49,1)
itwinjs-core/core/common/src/CloudStorage.ts(64,1)
itwinjs-core/core/common/src/CloudStorageTileCache.ts(23,1)
itwinjs-core/core/common/src/rpc/IModelTileRpcInterface.ts(45,3)
itwinjs-core/core/common/src/rpc/IModelTileRpcInterface.ts(56,3)
@iTwin/itwinjs-core-presentation
--[ FAILURE: @itwin/presentation-common ]-------------------[ 10.79 seconds ]--
itwinjs-core/presentation/common/src/presentation-common/content/Descriptor.ts(312,3)
itwinjs-core/presentation/common/src/presentation-common/content/Item.ts(24,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Key.ts(50,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Key.ts(60,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Key.ts(70,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Key.ts(80,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Key.ts(90,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(90,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(92,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(94,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(96,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(102,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(104,3)
itwinjs-core/presentation/common/src/presentation-common/hierarchy/Node.ts(106,3)
14 problems
--[ FAILURE: @itwin/presentation-components ]---------------[ 21.21 seconds ]--
itwinjs-core/presentation/components/src/presentation-components/tree/Utils.ts(105,1)
1 problem

I pushed some tests. Two of them fail.

Are the @itwin/eslint-plugin tests not run as part of CI? Output from local run:
  38 passing (833ms)
  2 failing

  1) require-version-in-deprecation
       invalid

          /** @deprecated in 3.6. Ok.*/
          function descriptionTooShort() {}
        :

      AssertionError [ERR_ASSERTION]: Should have 1 error but had 0: []
      + expected - actual

      -0
      +1

      at testInvalidTemplate (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:724:24)
      at Context.<anonymous> (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:958:29)
      at process.processImmediate (node:internal/timers:476:21)

  2) require-version-in-deprecation
       invalid

          /** @deprecated in 3.6.                                                        */
          function whitespaceIsNotADescription() {}
        :

      AssertionError [ERR_ASSERTION]: Should have 1 error but had 0: []
      + expected - actual

      -0
      +1

      at testInvalidTemplate (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:724:24)
      at Context.<anonymous> (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:958:29)
      at process.processImmediate (node:internal/timers:476:21)

The @itwin/eslint-plugin tests not run as part of CI because package.json has an empty "cover" script. That seems wrong to me.
Output from local run:
  38 passing (833ms)
  2 failing

  1) require-version-in-deprecation
       invalid

          /** @deprecated in 3.6. Ok.*/
          function descriptionTooShort() {}
        :

      AssertionError [ERR_ASSERTION]: Should have 1 error but had 0: []
      + expected - actual

      -0
      +1

      at testInvalidTemplate (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:724:24)
      at Context.<anonymous> (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:958:29)
      at process.processImmediate (node:internal/timers:476:21)

  2) require-version-in-deprecation
       invalid

          /** @deprecated in 3.6.                                                        */
          function whitespaceIsNotADescription() {}
        :

      AssertionError [ERR_ASSERTION]: Should have 1 error but had 0: []
      + expected - actual

      -0
      +1

      at testInvalidTemplate (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:724:24)
      at Context.<anonymous> (/home/paul/c/js/s/itwinjs/common/temp/node_modules/.pnpm/eslint@7.32.0/node_modules/eslint/lib/rule-tester/rule-tester.js:958:29)
      at process.processImmediate (node:internal/timers:476:21)

Yeah agreed.

Please update rule to fix the two failing tests I added. Please evaluate what else is missing from tests.

Yes, I am making changes to the rule.

The @itwin/eslint-plugin tests not run as part of CI because package.json has an empty "cover" script. That seems wrong to me.

Yeah, I was curious about that too when I first started the task.

The @itwin/eslint-plugin tests not run as part of CI because package.json has an empty "cover" script. That seems wrong to me.

Yeah, I was curious about that too when I first started the task.

Yash, please update the cover script in this pkg to run the tests

@NancyMcCallB @raplemie @grigasp @saskliutas please review.

@mergifyio backport release/3.7.x


use cfnKeyPair instead of cdk-ec2-key-pair

Per https://github.com/udondan/cdk-ec2-key-pair/issues/53#issuecomment-1173932370 the author of cdk-ec2-key-pair is deprecating the repo and suggests we start using the now-standard https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.CfnKeyPair.html

Not deprecating. 😸 See comment in the linked issue above.


failed to produce output path for output 'out'

When I use home-manager switch, I get:
error: builder for '/nix/store/pcrnv2awjzv600j5rd92jbv9svwf529z-auto-fix-vscode-server.service.drv' failed to produce output path for output 'out' at '/nix/store/pcrnv2awjzv600j5rd92jbv9svwf529z-auto-fix-vscode-server.service.drv.chroot/nix/store/2p8rilkxs755n2n6ygz38z649vx6yyh6-auto-fix-vscode-server.service'
error: 1 dependencies of derivation '/nix/store/qf05qafi6nnzrb5hdbdbxgipw9g72zp8-home-manager-files.drv' failed to build
error: 1 dependencies of derivation '/nix/store/g2z40rk3fhsapf01cmysadwm2inb78fl-home-manager-generation.drv' failed to build

This was working before I upgraded to nixos-22.05 (which has nix 2.8).
Attempting to diagnose what's wrong but not certain I'll get to the bottom of it.

Oh, that is odd. It just fixed itself. I was trying to upgrade my home-manager from 21.11 to 22.05. I did this by updating the home-manager channel to 22.05 and then commenting out home-manager.enable = true; in my home configuration. This then just worked, when I wasn't expecting it to. Hope that helps someone.


Allow long URLs in commit messages

This changes the gitlint configuration to allow long URLs in commit
messages, as long as they are on their own line; for example
https://kubernetes.io/docs/reference/using-api/deprecation-guide/#rbac-resources-v122
or
http://kubernetes.io/docs/reference/using-api/deprecation-guide/#rbac-resources-v122
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

Nice!

Dropped in favour of https://github.com/submariner-io/submariner-operator/pull/1494


Implementing max_on_percent setting

Implemented the max_on_percent expert level config to clamp the max ON time to a certain percentage of the cycle length. As discussed here https://github.com/jmcollin78/versatile_thermostat/discussions/602.
max_on_percent can be set in the configuration.yaml like this:
versatile_thermostat:
    max_on_percent: 0.8

I have also added tests, to check if the calculation is done correctly.
To avoid confusions, I also exposed the following attributes to HA:
max_on_percent
calculated_on_percent

Together with the already existing on_percent (which no can be clamped), all the informations are available to properly debug something if needed.

Hello @ms5,
Thank you for this, I will have a look until this week-end. I'm not at home this end of week.

I have updated the README by creating a new Expert Mode section (as discussed), moved the existing expert mode settings there and added the new max_on_percent setting. Please have a look and tell me if you would like to have some changes.
Have a nice Sunday 🌞

Merged ! Will be in the next release.

Awesome! Thank You!

https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.8.0.beta3
You can isntall this preview release if you want. Give me some feedback if all is alright for you.

I just had a look, but it seems the changes are not merged into the 6.8.0.beta3 tag.

You are right. I will fix that. I forgot the rebase the branch.

Should be fixed : https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.8.0.beta4

perfect! now it works. seems good so far.

I just want to report back since I have tested this now over the last week and I did not encounter any problems.


drop dependency caffee-rails

This PR drop dependency of coffee-rails gem.
phantomjs does not support ES2015 syntax, So it cannot use class syntax.

I changed rebase base branch.

hmm. I can't understand why this test failed. https://travis-ci.org/esminc/adhoq/jobs/515006628
It passed on my local environments:
bundle exec --gemfile gemfiles/Gemfile-rails-4.2.x rake spec
/Users/yoshimin/.rbenv/versions/2.3.6/bin/ruby -I/Users/yoshimin/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/rspec-core-3.8.0/lib:/Users/yoshimin/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/rspec-support-3.8.0/lib /Users/yoshimin/.rbenv/versions/2.3.6/lib/ruby/gems/2.3.0/gems/rspec-core-3.8.0/exe/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

Randomized with seed 6076
...............................

Top 10 slowest examples (12.65 seconds, 95.5% of total time):
  Golden-path: execute adhoc query Visit root, input query and click explain then we get a EXPLAIN query result
    8.19 seconds ./spec/features/execute_adhoc_query_spec.rb:36
  Golden-path: execute adhoc query Visit root, input placeholdered query and generate report then we get a report
    0.77699 seconds ./spec/features/execute_adhoc_query_spec.rb:67
  Golden-path: execute adhoc query Visit root, input query and generate report then we get a report
    0.75369 seconds ./spec/features/execute_adhoc_query_spec.rb:46
  Golden-path: execute adhoc query async_execution feature is ON Visit root, input query and generate report then we get a report
    0.72198 seconds ./spec/features/execute_adhoc_query_spec.rb:110
  Golden-path: execute adhoc query async_execution feature is OFF Visit root, input query and generate report then we get a report
    0.68216 seconds ./spec/features/execute_adhoc_query_spec.rb:159
  Golden-path: execute adhoc query async_execution feature is ON Visit root, input placeholdered query and generate report then we get a report
    0.64341 seconds ./spec/features/execute_adhoc_query_spec.rb:133
  Can see database schema at editing form See database schema
    0.31256 seconds ./spec/features/show_database_schema_spec.rb:4
  Golden-path: execute adhoc query Visit root and input invalid query then we get a error message
    0.24594 seconds ./spec/features/execute_adhoc_query_spec.rb:89
  Golden-path: execute adhoc query Visit root, input invalid query and click explain then we get a error message
    0.21158 seconds ./spec/features/execute_adhoc_query_spec.rb:98
  Adhoq::GlobalVariable config.storage = [:s3, ....] should be an instance of Adhoq::Storage::S3
    0.11358 seconds ./spec/adhoq/global_variable_spec.rb:32

Top 10 slowest example groups:
  Golden-path: execute adhoc query
    1.53 seconds average (12.22 seconds / 8 examples) ./spec/features/execute_adhoc_query_spec.rb:1
  Can see database schema at editing form
    0.31285 seconds average (0.31285 seconds / 1 example) ./spec/features/show_database_schema_spec.rb:1
  Adhoq::GlobalVariable
    0.06609 seconds average (0.13218 seconds / 2 examples) ./spec/adhoq/global_variable_spec.rb:2
  Adhoq::Report
    0.05319 seconds average (0.10637 seconds / 2 examples) ./spec/models/adhoq/report_spec.rb:2
  Adhoq::Execution
    0.04285 seconds average (0.17141 seconds / 4 examples) ./spec/models/adhoq/execution_spec.rb:2
  Adhoq::Reporter::Xlsx
    0.01917 seconds average (0.01917 seconds / 1 example) ./spec/adhoq/reporter/xlsx_spec.rb:2
  Adhoq::Storage
    0.0142 seconds average (0.0568 seconds / 4 examples) ./spec/adhoq/storage_spec.rb:2
  Adhoq::Reporter::Csv
    0.01346 seconds average (0.02693 seconds / 2 examples) ./spec/adhoq/reporter/csv_spec.rb:4
  Adhoq::Reporter::Json
    0.01291 seconds average (0.02583 seconds / 2 examples) ./spec/adhoq/reporter/json_spec.rb:4
  Adhoq::Executor::ConnectionWrapper
    0.01188 seconds average (0.01188 seconds / 1 example) ./spec/adhoq/executor/connection_wrapper_spec.rb:2

Finished in 13.24 seconds (files took 3.61 seconds to load)
31 examples, 0 failures

Randomized with seed 6076

I changed base on #173


[GitHub Desktop] Update Configuring Git for GitHub Desktop Flow

What article on docs.github.com is affected?
https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/configuring-git-for-github-desktop
What part(s) of the article would you like to see updated?
GitHub Desktop v2.6.4 will have a new Git configuration flow that allows you to select an email address associated with your GitHub account from a dropdown list in Preferences -> Git. Users can also select the Other option to use a custom email address, and GitHub Desktop will warn them if the email is not associated with the currently logged in account. See https://github.com/desktop/desktop/pull/11566 for screenshots and details.
The current article has the flow of copying an email from your GitHub account in browser and then pasting it into GitHub Desktop. We can now simplify this article and remove steps 1-5 since GitHub Desktop will automatically pull down all of the emails associated with your GitHub account.
Additionally in v2.6.4 you can now select a per-repository local email address (stored in the repository's .git/config). See https://github.com/desktop/desktop/pull/11595 for the related PR. I'm open for ideas about the best way to present this. Is it something we tag to the end and then add the "In this article" side navigation?
/cc @billygriffin

Thanks so much for opening an issue @steveward! When does v2.6.4 ship?
cc @myarb for 👀 since this should probably go on your squad's roadmap. They could also write a content design for this issue, then open it up here to make the changes ✨

@janiceilene Thank you! 2.6.4 ships tomorrow, but we're fine with lagging docs since this is implemented in a way that will dramatically alleviate confusion relative to current state, instead of potentially adding to it. 😄

Duplicate of #

@steveward and @billygriffin  - apologies for the delay in getting to this issue.
I've installed GitHub Desktop and looked at the new options. I've updated the OP with a content design plan that covers both the changes you mention above as well as the new section for defining the name for the default branch in new repositories.


Update Logger type to be closer to winston's Logger

What
Update Logger type to be closer to winston's Logger.
Why
After upgrading @makerx/node-winston in a project, I got a TypeScript error on the following code block, as log is not part of the definition.
const msalLoggerConfig: Partial<Configuration> = {
  system: {
    loggerOptions: {
      loggerCallback: (level, message) => logger.log(toNpmLogLevel(level), message),
    },
  },
}

I'm all for removing the methods that are not available in Node.js, but find the current definition too restrictive.
I'm not using all the methods it defines, but would like to be able to if I need to.
Was there a reason for restricting it to what it is now?

I did a dry-run update on MakerGraph, and the missing log method causes issues there as well:
λ npm run check-types

><EMAIL_ADDRESS>check-types
> tsc --noEmit

src/db/logger.ts:27:12 - error TS2339: Property 'log' does not exist on type 'Logger'.

27     logger.log(level, message)
              ~~~

src/express.ts:55:54 - error TS2339: Property 'log' does not exist on type 'Logger'.

55           loggerCallback: (level, message) => logger.log(toNpmLogLevel(level), message),

@cuzzlor, @tristanmenzel, @robdmoore, could you please have a look at this and let me know what you think?

@cuzzlor drove the original implementation for this, I can't completely remember why there is a cut down interface, but I know it was deliberate.

I pushed an update recently because I got a run time error trying to use warning instead of warn or vice versa. I'm not sure why the winston interface has methods that aren't implemented. I created the cut down one by searching for all usages though it looks like I've missed one or two. Another issue I had was that the node-common Logger interface differed to the Winston one and there was mixed usage.
I still feels it's better to have a narrower interface that we expand as needed rather than taking the widest possible interface as the whole reason for having an interface is that we can swap out the implementation if we decide winston isn't working for us. If we expose too many of winston's idiosyncrasies then that job becomes a bit harder.

On a related note, I played around with pino on a side project recently and it might be worth us adopting as it's an order of magnitude faster than winston

On a related note, I played around with pino on a side project recently and it might be worth us adopting as it's an order of magnitude faster than winston

Pino looks great, it would be good to transition to something more modern assuming it's not missing anything kinda vital people are using (e.g. any particular transports).
All our winston package really does is:

wrap up creating a logger instance with sensible defaults / easy config support for level, metadata (mixin)
support pretty logging output (which PINO seems to support OOTB nicely)
ensure errors are serialised with message and stack (which you'd expect PINO to take care of OOTB)

We use child loggers in GraphQL to add contextual metadata which PINO supports.
Be good to try PINO if someone has some time to invest and consider a few projects, if they use any winston transports etc which can't easily be swapped out.

LGTM


How to run?

there is no thing like in the video when you double click and it opens the program, or when i try to open index.js manually it sends me syntax error it also does the same thing with cmd

u dont open the zip u open the exe in the release: https://github.com/ThatTSGuy/discord-qr-token-grabber/releases/tag/v1.0


adding robots.txt and sitemap.xml

I'm submitting a...

[ ] Bug report
[x] Feature request
[ ] Documentation issue or request

In package

[ ] @ng-toolkit/init
[ ] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[x] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior
adding robots.txt and sitemap.xml to the /src directory and adding them to angular.json build.options.assets works fine and on build they appear in the dist directory. They can also be fetched when running a local server
Expected behavior
expecting the same behaviour remotely but instead I get the 404 set by the website. It's trying to go to a angular route
Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?
We all need sitemap.xml and robots.txt
Environment

Angular version: X.Y.Z

- Node version: 10.9.1
- Platform:  Ubuntu 18

Others:

@gp187 Good idea, I do think it can be easily done by providing default configuration for both files.


Update README with new locust mode 'worker' instead of 'slave'

Currently the README notes the following:

LOCUST_MODE | Set the mode to run in. Can be standalone, master or slave.

In the latest locust versions this is changed to 'worker' instead of 'slave'

Thanks for spotting this.

Resolved with external PR

Resolved with external PR


Being able to play a local mp3 file

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

If this is possible I haven't found how to do it I have it setup to do a tts when my favorite team scores and thought it would be cool if it could play the team fight song

Not doable. It's an amazon limitation.


phi3 medium

https://huggingface.co/microsoft/Phi-3-medium-128k-instruct
https://huggingface.co/microsoft/Phi-3-medium-4k-instruct
https://huggingface.co/microsoft/Phi-3-small-8k-instruct
https://huggingface.co/microsoft/Phi-3-small-128k-instruct
Suggested by @Qualzz
https://huggingface.co/microsoft/Phi-3-vision-128k-instruct/

There is also the vision model:
https://huggingface.co/microsoft/Phi-3-vision-128k-instruct/

https://github.com/ggerganov/llama.cpp/pull/7225 just merged, so I wonder if it's time to get the 128k models added to the library as well.

Ollama probably just needs to bump the llama.cpp submodule version, I have mine auto-updating each morning and it works great:
ollama run phi-3-medium-4k-instruct-bartowski:q5_k_m tell me a short joke --verbose
 Why don't scientists trust atoms? Because they make up everything!

(Note: This is an example of light-hearted humor that plays on the double meaning of "make up" as both to compose and to fabricate.)

total duration:       2.782812333s
load duration:        3.342083ms
prompt eval count:    9 token(s)
prompt eval duration: 801.181ms
prompt eval rate:     11.23 tokens/s
eval count:           51 token(s)
eval duration:        1.976573s
eval rate:            25.80 tokens/s

Modelfile:
FROM ./Phi-3-medium-4k-instruct-Q5_K_M.gguf
#FROM ./Phi-3-medium-128k-instruct-Q5_K_M.gguf

#  ollama create phi-3-medium-4k-instruct-bartowski:q5_k_m -f Modelfile-phi
#  ollama create phi-3-medium-128k-instruct-bartowski:q5_k_m -f Modelfile-phi

PARAMETER num_ctx 4096
#PARAMETER num_ctx 16384

TEMPLATE """{{ if .System }}<|system|>
{{ .System }}<|end|>
{{ end }}{{ if .Prompt }}<|user|>
{{ .Prompt }}<|end|>
{{ end }}<|assistant|>
{{ .Response }}<|end|>
"""

PARAMETER num_keep -1

PARAMETER stop "<|user|>"
PARAMETER stop "<|assistant|>"
PARAMETER stop "<|system|>"
PARAMETER stop "<|end|>"
PARAMETER stop "<|endoftext|>"

Phi3 medium 4k is available here. 128k, small, and vision models are coming soon :tm:

While you're quantizing models, I also have noticed several times that the mini-4k model only has fp16 and q4_K_M. I guess it would be cool to have the rest of the quantizations, but I'll probably stop caring once the mini-128k model is quantized and usable, haha

Hi all, just now i have pulled Phi3 medium in ollama and i'm getting error "ollama run phi3:medium
Error: llama runner process no longer running: -1" but phi3 mini is working fine. system info: Linux  (POP OS), CPU: AMD 9 5900, RAM: 32GB and GPU: Nvidia RTX 3070 8GB

Getting the new Phi-3 models working is going to require a newer version of llama.cpp than ollama currently has. Some of the required changes were merged into llama.cpp only a few hours ago. Some people in this thread have been testing it by building ollama from scratch with the updated llama.cpp, but I haven't tried to do that yet.

I have updated ollama and now i'm able to run Phi3 medium. Thank you.

FYI for the future to update the llama.cpp submodule when building Ollama:

Clone Ollama
git submodule update --remote
OLLAMA_SKIP_PATCHING=true go build

And I see this popped up a few seconds ago!

phi3:14b-medium-4k-instruct-q8_0 seems to be working well in some quick testing!

I am getting weird results, does there need to be a update I assume?

I also see similar things… simply saying “Hello” does seem to cause problems for it here. I’m seeing both **Instruction and ### Instruction just before it goes off the rails, so maybe those should be added as stop tokens?

This could also be related: https://github.com/ggerganov/llama.cpp/pull/7449

This could also be related: ggerganov/llama.cpp#7449

Merged in master !

There is a recent PR opened to fix/implement GGUF conversion of phi3-vision: https://github.com/ggerganov/llama.cpp/pull/7705
This might be the missing piece of the puzzle to get this into ollama sooner or later.

@olumolu can you link to the PR that fixed Phi3 small and Phi3 Vision? I didn’t think they were supported yet.

Yes it is not it was opened since a long time so i closed this.


[suggestion] Clarification of Vulkan related requirements

Vulkan runs well on Windows 10, but this is not the case for Windows 7
This is because most GPU drivers on the latter only support the Vulkan 1.2 API

Done with PR #883


handleFlutterPayment callback is called twice

This happens especially if a payment has been made before and a user is making a second payment, the implementation calls twice, making three.

Any fix or work around for this?


Fix CameraImagePicker bad instanciation

This PR fixes the bad super constructor parameter of CameraImagePicker resulting in a bad handling of the submit method.

WOW... That was a bad mistake. Thanks. Wondering how it has been working all this while.


How to run batch inference for llama2

Hi team, could you help me in figuring how could I run batch inference for llama2 in python?

You could set --batch_size > 1 in summarize.py


Add Display Version to create release request

Testing changes

maybe make it a Draft-PR while in its early stages


Generate ids for localizable strings and images

I'm not sure that this functionality should be placed directly inside Natalie, may be should be created a different tool.
Generating identifiers for storyboards stuff definitely is a good step :) But there are also quite a lot of magic strings in the project - for localizable strings (NSLocalizedString("Hello", ...)) or for images UIImage(named: "Logo"), and other files in the bundle.
So, may be also can be generated analogue of R file on android. So, for strings and images can be generated something like:
struct Strings {
     static let Hello = "Hello"
}
struct Images {
    static let Logo = "Logo"
}

And for convenience:
struct LocalizedString {
     static var Hello = { return NSLocalizedString(Strings.hello, ...) }
}

Apple did a great talk on this at WWDC 2015 called Swift in practise.

Thanks, this is valid feature request, I'd like to have it. I'll work on that after transition to Swift 2.0

@CallumOz As seen on tv ;-)

hey, great! I don't have any preferences in that regard. Feel free to propose something. I'm looking forward to merge it!


Deprecate redundant itemExtent in RenderSliverFixedExtentBoxAdaptor methods

Multiple methods in RenderSliverFixedExtentBoxAdaptor pass a double itemExtent for computing things like what children will be laid out, what the max scroll offset will be, and how the children will be laid out.
Since RenderSliverFixedExtentBoxAdaptor was further subclassed to support a itemExtentBuider in RenderSliverVariedExtentList, these itemExtent parameters became useless when using that RenderObject. Reading through RenderSliverFixedExtentBoxAdaptor.performLayout, the remaining artifacts of passing around itemExtent make it hard to follow when it is irrelevant.
RenderSliverFixedExtentBoxAdaptor.itemExtent is available from these methods, so it does not need to pass it. It is redundant API.
Plus, if a bogus itemExtent is passed for some reason, errors will ensue and the layout will be incorrect. 💣 💥
Deprecating so we can remove these for a cleaner API. Unfortunately this is not supported by dart fix, but the fact that these methods are protected means usage outside of the framework is likely minimal.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

We have been on holiday recently, and will return to work next week! Happy Spring Festival!

来自TT移动邮箱 / From TT mailbox

发件人: Kate Lovett @.>
发送时间: 2024年02月14日 08:00
收件人: flutter/flutter @.>
抄送: 徐宝林(Ava) @.>; Review requested @.>
主题: Re: [flutter/flutter] Deprecate redundant itemExtent in RenderSliverFixedExtentBoxAdaptor methods (PR #143412)
@Piinkshttps://github.com/Piinks requested your review on: #143412https://github.com/flutter/flutter/pull/143412 Deprecate redundant itemExtent in RenderSliverFixedExtentBoxAdaptor methods.
―
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/pull/143412#event-11795321758, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOR66GBV3JUU3PBW6ALXBYDYTP5C3AVCNFSM6AAAAABDHL36IWVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRG44TKMZSGE3TKOA.
You are receiving this because your review was requested.Message ID: @.***>

OPPO
本电子邮件及其附件含有OPPO公司的保密信息，仅限于邮件指明的收件人（包含个人及群组）使用。禁止任何人在未经授权的情况下以任何形式使用。如果您错收了本邮件，切勿传播、分发、复制、印刷或使用本邮件之任何部分或其所载之任何内容，并请立即以电子邮件通知发件人并删除本邮件及其附件。
网络通讯固有缺陷可能导致邮件被截留、修改、丢失、破坏或包含计算机病毒等不安全情况，OPPO对此类错误或遗漏而引致之任何损失概不承担责任并保留与本邮件相关之一切权利。
除非明确说明，本邮件及其附件无意作为在任何国家或地区之要约、招揽或承诺，亦无意作为任何交易或合同之正式确认。 发件人、其所属机构或所属机构之关联机构或任何上述机构之股东、董事、高级管理人员、员工或其他任何人（以下称“发件人”或“OPPO”）不因本邮件之误送而放弃其所享之任何权利，亦不对因故意或过失使用该等信息而引发或可能引发的损失承担任何责任。
文化差异披露：因全球文化差异影响，单纯以YES\OK或其他简单词汇的回复并不构成发件人对任何交易或合同之正式确认或接受，请与发件人再次确认以获得明确书面意见。发件人不对任何受文化差异影响而导致故意或错误使用该等信息所造成的任何直接或间接损害承担责任。
This e-mail and its attachments contain confidential information from OPPO, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you are not the intended recipient, please do not read, copy, distribute, or use this information. If you have received this transmission in error, please notify the sender immediately by reply e-mail and then delete this message.
Electronic communications may contain computer viruses or other defects inherently, may not be accurately and/or timely transmitted to other systems, or may be intercepted, modified ,delayed, deleted or interfered. OPPO shall not be liable for any damages that arise or may arise from such matter and reserves all rights in connection with the email.
Unless expressly stated, this e-mail and its attachments are provided without any warranty, acceptance or promise of any kind in any country or region, nor constitute a formal confirmation or acceptance of any transaction or contract. The sender, together with its affiliates or any shareholder, director, officer, employee or any other person of any such institution (hereinafter referred to as "sender" or "OPPO") does not waive any rights and shall not be liable for any damages that arise or may arise from the intentional or negligent use of such information.
Cultural Differences Disclosure: Due to global cultural differences, any reply with only YES\OK or other simple words does not constitute any confirmation or acceptance of any transaction or contract, please confirm with the sender again to ensure clear opinion in written form. The sender shall not be responsible for any direct or indirect damages resulting from the intentional or misuse of such information.