FIX TreeMultiselectField passes value 'unchanged' as null to ORM

Fix for https://github.com/silverstripe/silverstripe-framework/issues/8332

There's also a missing space after === (not covered by phpcs) and would be good to add a unit test for it if you have time =)

there's even more about @deprecate. We're not deprecating the method itself, but rather will have to remove this particular implementation of it in the next major. I'm gonna change it to internal.
Regarding tests - fair enough, I'll add some coverage for the class.

@maxime-rainville

Silly questions, but what is actually preventing us from fixing the core issue that we're assigning unchanged to the value? Is it a semver thing that we're afraid that other people might be relying on the value being unchanged?

Yes, exactly. The string 'unchanged' is the default empty value of the field. That contract is propagating to some other libraries as well in both back-end and front-end sides. At this point we don't have guarantees that no 3rd party libraries rely on this particular behaviour and changing that default value would be a breaking change in the framework API.

If there's a good reason for keeping the current behavior in 4, I think we should do a PR to fix the issue in 5 right away, because that's the kind of thing we'll forget about later on.

I believe we should keep the current behaviour for 4 in sake of backward compatibility.
Regarding the fix for the next major (5.0), yes that's the current plan. However, due to avoiding conflicts when merging 4 into master I want this PR to go into the 4 first, then we merge it into master and then I do another PR that overwrites this change and removes 'unchanged' string, leaving null value in its place.

Sounds sensible. We should be able to merge once we got some unit test.

@robbieaverill I've managed to rewrite the tests. Now we're not checking the rendering anymore, but rather what data the object passes to the template engine.

Ok, everything's been fixed. Good to be merged.


CI for NWChem

closes #211
Description
try ubuntu's nwchem package, as recc by #211
Changelog description

[x] Adds CI testing of NWChem 6.6 through Ubuntu xenial pkg

Questions

[ ] networkx is req'd for the NWChem interface for all but energies to align arrays, but at present it's only an optional requirement for qcel. There's a nice "install me" message, but in production users would probably like to know to install the pkg before the QC job, not after. But I'm hesitant to put the check in def found because if ppl are only looking at the boolean, it'd be unintuitive for which nwchem to be present but nwchem harness not be available. Where to address this? require networkx? or have a distinction btwn nwchem-found and nwchem-ready?
[ ] combine this CI lane with another?

Status

[x] Code base linted
[x] Ready to go

Awesome :)
FYI @WardLT

We have a similar issue with the Orca interface where CCLib may be required. Should found be more complex where you can say something like found(binary_only=True)? Seems awkward however.

maybe something like the below for when main QC present but non-QC component missing.
>>> Program information
Available programs:
dftd3 v3.2.1
mp2d v1.1

Incomplete programs (see devtools/conda-envs for install help):
nwchem -- needs networkx
orca -- needs cclib

Other supported programs:
cfour entos gamess molpro mopac nwchem openmm psi4 qchem rdkit terachem torchani turbomole


Added concurrent connection test type

I had a need to test concurrent connections through a load balancer and went ahead and added that test type to the external test mode.
I am still missing results logging and updated documentation but I wanted to start the conversation with a working feature.
Thoughts?

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


Doesn't work when the username has space in it

Just to be clear, it works fine so far using windows powershell, but it fails when switching to git bash (which is what i use almost always), and shows this error:
** Presuming my windows username is Lina Lina**
C:\Users\Lina : The term 'C:\Users\Lina' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

C:\Users\Lina Lina\scoop\apps\sudo\current\sudo.ps1

  + CategoryInfo          : ObjectNotFound: (C:\Users\Lina:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException

To fix this, the path to sudo must be escaped. Example of a broken shim:
> cat 'C:\Users\Felipe Santos\scoop\shims\sudo'
#!/bin/sh
powershell.exe -noprofile -ex unrestricted "C:\Users\Felipe Santos\scoop\apps\sudo\current\sudo.ps1"  "$@"

Example of a working shim:
> cat 'C:\Users\Felipe Santos\scoop\shims\sudo'
#!/bin/sh
powershell.exe -noprofile -ex unrestricted "C:\Users\Felipe` Santos\scoop\apps\sudo\current\sudo.ps1"  "$@"

Notice the ` before the space.


Cannot send mail after merge when Username contains UTF8 character

Gitea version (or commit ref): 1.1.2
Git version: git version 2.13.0.windows.1
Operating system: Windows Server 2016 Standard
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant (cannot view logs)

Log gist:
2017/07/03 12:14:19 [...les/mailer/mailer.go:244 processMailQueue()] [E] Failed to send emails<EMAIL_ADDRESS>Subject: [Project] description (#16), issue comment - gomail: could not send email 1: gomail: invalid address "=?UTF-8?q?"P=C3=A9ter"_git@mycompany.com?=": mail: expected single address, got "?="

Description
After merging a commit in one of our repositories, I saw this in the log, which says it was unable to deliver the notification.

P=C3=A9ter

Should be

Péter

which is used as the Full name for that user (acquired through Active Directory), so I think the latin/utf8 character

é

causes the mentioned error.

Seems to be validation problem as UTF-8 email address is correct

I'll check tomorrow if this happens all the time, since I do remember receiving some notifications. Is the error message for not being able to deliver mails because e.g. the mail server is not available the same, or different?

I could be wrong but seems to be validation in Gitea code

I'm facing this problem right now, where all of the people in my team have a name with characters out of basic latin character set… So none of them are receiving the emails :)

Hi rems4e,
Our workaround for the problem was to replace/remove these characters in the Gitea database (since the full name was coming from AD we could not edit it on the UI) and since then everyone is receiving emails.

Hi,
Thanks for the hint. But this is not really acceptable for us, as the directory is used for other stuffs that can't accomodate with this change.
Anyway, this is a bug in Gitea that is a little cumbersome at the moment :) Maybe I could have a look and try fixing it?

@rems4e you are more than welcome to try to fix it and send PR

@lafriks OK, that should be feasible. However, could you please hint me where to start? Mainly, on which branch should I base my work? I've had a look at the contributing info but I'm not sure it answers all of my questions :)

I was hoping this could be in the 1.2.0 release. Is there something I can do to see it in 1.2.X ?

@rems4e Backporting all fixed issues to 1.2 will take too much time. I think we will release 1.3-rc in coming weeks :)


[nmstate-1.4] ip: Support treating string as int for prefix-length

When the network role user is using the network_state variable to configure the network, and if they are using Jinja2 template to define the prefix-length, the type conversion
prefix-length: "{{ __str_val | int }}" does not work as expected, the type for prefix-length in the end is still string. Therefore, nmstate need to support treating string as int for prefix-length in order to make the apply succeed.

I have fixed the CI. Please rebase and try again.

I have fixed the CI. Please rebase and try again.

I rebased, thanks.

Merged. Thanks!


Support Xamarin.Mac applications in the XamariniOS@2 task

Required Information
Question, Bug, or Feature?
Type:  Feature
Enter Task Name: XamariniOS@2
Issue Description
The build process for Xamarin.iOS & Xamarin.Mac is the same. Both MSBuild tasks require some information on configurations and need to be provided Apple certificates in order to sign the applications.
When using the xamarin ios task in a pipeline it sets the MSBuild platform to iPhone and there is no way to override this. See here how the platform is passed to msbuild from the code.
When using the task for iOS the following msbuild command will be generated:
/Library/Frameworks/Mono.framework/Versions/Current/Commands/msbuild /Users/runner/work/1/s/src/ACME.sln
    /p:Configuration=Release
    /p:Platform=iPhone
    /p:BuildIpa=true
    /p:Codesignkey=Developer ID Application: ACME (00000000)
    /p:CodesignProvision=00000000-0000-0000-0000-000000000000

Due to the task not supporting mac, a developer has to use the MSBuild task to build their macOS app. This is not as convenient as providing a task and adds an arbitrary barrier to entry.
The following yml will build the app successfully:
- task: MSBuild@1
  displayName: 'Build macOS'
  inputs:
    solution: '**/*.sln'
    configuration: 'Release'
    msbuildArguments: '/p:Codesignkey=\"$(APPLE_CERTIFICATE_SIGNING_IDENTITY)\" /p:CodesignProvision=\"$(APPLE_PROV_PROFILE_UUID)\"'

This will generate the following MSBuild command:
/Library/Frameworks/Mono.framework/Versions/Current/Commands/msbuild /Users/runner/work/1/s/src/ACME.sln
    /p:Configuration=Release
    /p:Codesignkey=\Developer ID Application: ACME (00000000)
    /p:CodesignProvision=00000000-0000-0000-0000-000000000000

As you can see the command for both platforms is extremely similar and it would be beneficial for those few xamarin.mac developers if we had a task. The benefit for developers is maintaining the pipelines would be easier. I found when figuring out the msbuild inputs, the command line was incredibly flakey with how I formatted the msbuild arguments due to the fact that the code-sign variables can contain spaces. Wrapping this up in an official task would make this process more robust.
Options
I foresee this could take a number of outcomes:

Update the task to accept mac as a platform, perhaps through a new parameter named Platform (default to iOS, add macOS as alternative value)
Create a new task named XamarinMaciOS@1 which combines both
Create a new task named XamarinMac@1 which just builds mac
I Fork the task and update it accordingly, making it available on the pipeline marketplace

I would rather have the official task support this functionality and would be happy to put in the work required to make the change.

Hi @Axemasta sorry for the delay - we are currently working on more prioritized issues, but will get back to this feature request once be able to.

Clearly not many people are using xamarin mac & azure pipelines, can we add a flag such as isMac that we can set to prevent the platform flag iPhone from being sent to msbuild?


Weekly Kickoff for Milestone - Fri: Apr 30, 2021

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2718
Originally created by @tayloramurphy on 2021-04-21 15:00:47

Milestone: https://gitlab.com/groups/meltano/-/milestones/156
General Priorities:

SingerHub soft launch in the Meltano slack

Get JSON schema for taps and targets
All discoverable extractors and loaders from meltano.com are on the site.

MVC of getting data from GitHub into BigQuery

View 2 previous comments from the original issue on GitLab


chore: Adds linting + clean & nuke scripts

This PR adds linting via editorconfig-checker and prettier.
Furthermore, it externalizes all package.json scripts to a scripts/ directory and adds a clean and a nuke script.

Hi @henrikradandt,
thanks for testing this so thoroughly :+1:
This helped me uncover a major API change in husky that totally slipped me. (see: https://typicode.github.io/husky/#/?id=husky-4-to-7-cli)
I fixed the setup and added a postinstall script, so that the git hooks are being properly installed right after running pnpm install.
I also rebased this branch on main and applied the new linting to the recently added use-business package.


Unable to update field in rule object when using Custom Java Object in @Given

Hi,
I have followed megabank example to create a rule which uses custom java object, but I keep getting error that
RuleAdapter - Unable to update field 'tags' in rule object 'class com.bofa.sa.rulebook.TwoWeekDestroyRule'
Here is my Rule class.
@Rule
public class TwoWeekDestroyRule {
    @Given("crDate")
    private ResourceTags tags;

    @Result
    private Boolean result;

    @When
    public boolean when() {
        return tags.getTest1().equals("Test1");
    }
    @Then
    public void then() {result = true; }
}
 ResourceTags tags = new ResourceTags( "Test1",  "Test2", "Test3", "Test4",  "Test5", "Test6" );
RuleBook<Boolean> ruleBook = new RuleBookRunner("com.rulebook");
NameValueReferableMap<ResourceTags> facts = new FactMap<>();
facts.put(new Fact<>("crDate",tags));
ruleBook.setDefaultResult(false);
ruleBook.run(facts);
ruleBook.getResult().ifPresent(result -> System.out::println);

Any help is appreciated.
Thanks

Sorry about the delayed response. My full-time gig has been a little unforgiving in terms of workload over the past few months. But I have a breather this weekend. I'll check it out. Thanks.

I checked this out and the only thing that stood out was the last line of your code is not valid syntax. You combine the reference syntax with lambda syntax and in Java 8+, it's one or the other. So, ruleBook.getResult().ifPresent(System.out::println); or ruleBook.getResult().ifPresent(result -> System.out.println(result));
Now, I did have to infer the internals of ResourceTags based on your code. So, this is what I implemented to test and it seemed to work out as expected.
package com.example.rulebook.pojo;

import java.util.ArrayList;
import java.util.List;

public class ResourceTags {
  private List<String> _tags = new ArrayList();

  public ResourceTags(String... tags) {
    for (String tag: tags) {
      _tags.add(tag);
    }
  }

  public String getTest1() {
    return _tags.get(0);
  }

}

package com.example.rulebook.pojo;

import com.deliveredtechnologies.rulebook.annotation.*;

@Rule
public class TwoWeekDestroyRule {
  @Given("crDate")
  private ResourceTags tags;

  @Result
  private Boolean result;

  @When
  public boolean when() {
    return tags.getTest1().equals("Test1");
  }
  @Then
  public void then() {result = true; }
}

package com.example.rulebook.pojo;

import com.deliveredtechnologies.rulebook.Fact;
import com.deliveredtechnologies.rulebook.FactMap;
import com.deliveredtechnologies.rulebook.NameValueReferableMap;
import com.deliveredtechnologies.rulebook.model.RuleBook;
import com.deliveredtechnologies.rulebook.model.runner.RuleBookRunner;

public class Application {
  public static void main(String args[]) {
    ResourceTags tags = new ResourceTags( "Test1",  "Test2", "Test3", "Test4",  "Test5", "Test6" );
    RuleBook<Boolean> ruleBook = new RuleBookRunner("com.example.rulebook.pojo");
    NameValueReferableMap<ResourceTags> facts = new FactMap<>();
    facts.put(new Fact<>("crDate",tags));
    ruleBook.setDefaultResult(false);
    ruleBook.run(facts);
    ruleBook.getResult().ifPresent(result -> System.out.println(result));
  }
}

I hope that helps. If not, please post the code for your ResourceTags class. Perhaps there is something in the makeup of that class that is unaccounted for.
Thanks,
Clayton

Thanks Clayton.
I will take a look at it.
Any future plans on adding a feature to externalize rules?
Thanks
Manish
Regards,
Manish

From: Clayton Long<EMAIL_ADDRESS>Sent: Sunday, March 18, 2018 5:10:44 PM
To: rulebook-rules/rulebook
Cc: Manish Sangani; Author
Subject: Re: [rulebook-rules/rulebook] Unable to update field in rule object when using Custom Java Object in @Given (#117)
I checked this out and the only thing that stood out was the last line of your code is not valid syntax. You combine the reference syntax with lambda syntax and in Java 8+, it's one or the other. So, ruleBook.getResult().ifPresent(System.out::println); or ruleBook.getResult().ifPresent(result -> System.out.println(result));
Now, I did have to infer the internals of ResourceTags based on your code. So, this is what I implemented to test and it seemed to work out as expected.
package com.example.rulebook.pojo;
import java.util.ArrayList;
import java.util.List;
public class ResourceTags {
private List _tags = new ArrayList();
public ResourceTags(String... tags) {
for (String tag: tags) {
_tags.add(tag);
}
}
public String getTest1() {
return _tags.get(0);
}
}
package com.example.rulebook.pojo;
import com.deliveredtechnologies.rulebook.annotation.*;
@Rule
public class TwoWeekDestroyRule {
@Given("crDate")
private ResourceTags tags;
@Result
private Boolean result;
@When
public boolean when() {
return tags.getTest1().equals("Test1");
}
@Then
public void then() {result = true; }
}
package com.example.rulebook.pojo;
import com.deliveredtechnologies.rulebook.Fact;
import com.deliveredtechnologies.rulebook.FactMap;
import com.deliveredtechnologies.rulebook.NameValueReferableMap;
import com.deliveredtechnologies.rulebook.model.RuleBook;
import com.deliveredtechnologies.rulebook.model.runner.RuleBookRunner;
public class Application {
public static void main(String args[]) {
ResourceTags tags = new ResourceTags( "Test1",  "Test2", "Test3", "Test4",  "Test5", "Test6" );
RuleBook ruleBook = new RuleBookRunner("com.example.rulebook.pojo");
NameValueReferableMap facts = new FactMap<>();
facts.put(new Fact<>("crDate",tags));
ruleBook.setDefaultResult(false);
ruleBook.run(facts);
ruleBook.getResult().ifPresent(result -> System.out.println(result));
}
}
I hope that helps. If not, please post the code for your ResourceTags class. Perhaps there is something in the makeup of that class that is unaccounted for.
Thanks,
Clayton
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/rulebook-rules/rulebook/issues/117#issuecomment-374047459, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD3MlmT_N9oTP3iKECvmJiD_YUX6F4fmks5tfs1UgaJpZM4SMc0e.

@manishsagani There are plans to externalize rules using Groovy scripts. I just need to time to make it happen ;) But, it will happen.


OpenSSL Error

Using the master branch with the unstable and s3 features I get the following error:
thread 'main' panicked at 'Error dispatching request: HttpDispatchError { message: "An error in the OpenSSL library" }', ../src/libcore/result.rs:788
stack backtrace:
   1:     0x557cc2f813cd - std::sys::backtrace::tracing::imp::write::h29f5fdb9fc0a7395
   2:     0x557cc2f84d21 - std::panicking::default_hook::_{{closure}}::h2cc84f0378700526
   3:     0x557cc2f83e39 - std::panicking::default_hook::hbbe7fa36a995aca0
   4:     0x557cc2f844aa - std::panicking::rust_panic_with_hook::h105c3d42fcd2fb5e
   5:     0x557cc2f84362 - std::panicking::begin_panic::hbf62ea4a5ff3f9de
   6:     0x557cc2f84290 - std::panicking::begin_panic_fmt::h20f5943904e5791d
   7:     0x557cc2f84211 - rust_begin_unwind
   8:     0x557cc2fbbcac - core::panicking::panic_fmt::h19323e466869c656
   9:     0x557cc2adfb02 - core::result::unwrap_failed::hbed20a9805d54579
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/result.rs:29
  10:     0x557cc2accde3 - _<core..result..Result<T, E>>::expect::hbbac5fd2c6c600df
                        at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/result.rs:750
  11:     0x557cc2b63d85 - rusoto::s3::sign_and_execute::h16c34eeb12b23ff4
                        at /home/user/.cargo/git/checkouts/rusoto-761d9ff5e4550023/master/src/s3.rs:12784
  12:     0x557cc2ad0bce - _<rusoto..s3..S3Client<P, D>>::get_object::h2a1f12a14fbe1100
                        at /home/user/.cargo/git/checkouts/rusoto-761d9ff5e4550023/master/src/s3.rs:11964
  13:     0x557cc2ac09f1 - _<rusoto..s3..S3Helper<P>>::get_object::h4481a3ee7f86944b
                        at /home/user/.cargo/git/checkouts/rusoto-761d9ff5e4550023/master/src/s3.rs:12455
  14:     0x557cc2bb1a18 - _<devise..provider..amazon..S3 as lpac..provider..Provider>::provide::hdcd51b52f9fe9271
                        at /workspace/devise/src/provider/amazon/mod.rs:16
  15:     0x557cc2bb3de6 - devise::main::h2b5d54f8e88e2158
                        at /workspace/devise/<lpac macros>:29
  16:     0x557cc2f84167 - std::panicking::try::call::h5df3ac2979db3c90
  17:     0x557cc2f8c826 - __rust_maybe_catch_panic
  18:     0x557cc2f835f9 - std::rt::lang_start::hfe9ab243c60ffb9b
  19:     0x557cc2bb6323 - main
  20:     0x7f80637b2b14 - __libc_start_main
  21:     0x557cc2a86f58 - <unknown>
  22:                0x0 - <unknown>

Using the S3Helper with:
impl Provider for S3 {
    fn provide(self: Box<Self>) -> Result<Vec<u8>> {
        let provider = DefaultCredentialsProvider::new().unwrap();
        let s3 = S3Helper::new(provider, Region::UsWest1);

        match s3.get_object(&self.bucket, &self.key) {
            Ok(response) => {
                let body = response.body;
                Ok(body)
            },
            Err(error) => panic!(error),
        }
    }
}

I have openssl installed. Running inside centos docker container.

That's a new one.  We're not doing anything directly with OpenSSL, we just open up https://foo.amazonaws.com/ connections with hyper, which in turn uses rust-openssl.
Some googling shows similar issues at https://github.com/sfackler/rust-openssl/issues/205 and https://github.com/fxbox/foxbox/issues/372
The latter of those indicates that the not-so-helpful error message shows up when the local client doesn't have a certificate for the remote host.  Are you sure that the process you're running in your docker container has read access for the root certificate bundle that installed with openssl on the docker host?  Barring that, is the openssl install new-ish?  I know some things (in particular the JVM) ship with older certificate bundles that don't include the Verisign root certificate that AWS requires.  Can you tell I'm just guessing blindly? :smile:
Also - do you only get this with the unstable feature?

The error is not very useful but I think it is because my bucket is a CNAME, which is not supported for ssl. Is it possible to use http?

Created a new bucket, not using a CNAME, and everything works fine.


Hi，I'm having some problems

iOS17.02
XCode15.1
When running the app:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSMutableOrderedSet addObject:]: object cannot be nil'

IOS 17.2
Xcode 15.2
same here i got the same problem, did you find any solution ?

oh, It's been a long time, and I'm now successful with ios18.

i'll test it with ios 18 and see !
i found the root of the issue with ios 17.2 though
i had to comment out the following line for it to launch successfully on the simulator, but obviously didn't work as expected
https://github.com/barisozgenn/PackageDeliverySwiftUI/blob/e143eafedc93441adecdb6c7858cbbb32adeecbc/PackageDeliverySwiftUI/Core/Views/Map/Views/NewMapView.swift#L77-L97
down belown are the changes that i made to the NewMapView.swift file
https://github.com/R3-da/PackageDeliverySwiftUI/blob/930b25a2a50e755afd0fba356deade34ae114890/PackageDeliverySwiftUI/Core/Views/Map/Views/NewMapView.swift#L77-L99


[PE-D][Tester C] Phone number

Only allows 8 digits. Foreign students might not be able to enter a valid phone number relative to their country.

Labels: severity.Low type.FeatureFlaw
original: seandias/ped#1

This will be updated in a future release.


Start Webdriver server when on VPN

In my protractor config file, I had this line, seleniumAddress: 'http://localhost:4444/wd/hub'. On running Protractor I was getting an error "ECONNREFUSED connect ECONNREFUSED". After going through lot of other existing issues and solutions, I removed "seleniumAddress" property. That resolved the issue. Selenium standalone server gets started. "Selenium standalone server started at http://<IP_ADDRESS>:64477/wd/hub"
But when I turn on the VPN, then I get an error "Error: Timed out waiting for the WebDriver server at http://<IP_ADDRESS>:63199/wd/hub", which I have been able to resolve.
I am on a HP laptop which has Windows 7 Professional and I am using Cisco VPN.

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!

Sure, Nick. Thanks.


[downstream project integration] Enable use of LLVM_EXTERNAL_PROJECTS

Other MLIR repositories such as mlir-hlo support using the LLVM_EXTERNAL_PROJECTS (https://github.com/tensorflow/mlir-hlo/blob/master/CMakeLists.txt#L93) as a build mechanism for plugging in the provided dialects into a downstream project.
IREE also uses this mechanism for various dialects (https://github.com/iree-org/iree/tree/main/llvm-external-projects).
It would be great if the build system could be updated to support this mechanism for at least the ONNX dialect, which allows for easier integration of onnx-mlir into downstream projects.
Currently it seems like the project has a very sensitive build system, and downstream users who may only need a small part of the project don't want to build all the dialects or the runtime if they only want to use onnx-mlir as a frontend layer that imports an ONNX model to the ONNX IR level. Such a user might end up rolling their own CMake integration instead of using the current build system.
Related: https://github.com/onnx/onnx-mlir/issues/1597
Edit:
Also related, other orgs seem to be rolling their own forks: https://github.com/nod-ai/onnx-mlir-exporter

Opened an issue in the onnx-mlir-exporter to see if they can provide their expertise to merge what they need back in onnx-mlir
https://github.com/nod-ai/onnx-mlir-exporter/issues/1
@christopherbate We have asked the MHLO and Pytorch-MLIR to have a switch so that folks don't necessarily have to build their stuff, though for our CIs we want to test everything. Would you be able to contribute and/or collaborate with the folks from onnx-mlir-exporter to properly switch off what you don't need?
Historically, the only way to use this repo was to lower to binary... but now that there are new bridges from onnx-mlir to mlir dialects being built, through TOSA/MHLO/Torch-MLIR, obviously what used to be necessary is not so anymore.
We have a dependence on ONNX as I believe we use some of the protobuf tools that ONNX provide to parse the input files. Presumably any project using onnx-mlir GitHub repo would need that component. But beyond that, I can see that the lowering from ONNX to Krnl/Zhigh/Zlow and everthing after that could be switched off under the right cmake variables.
Further opinions @gongsu832 @caoimhinuibrian ?

Just following up on this thread from  https://github.com/nod-ai/onnx-mlir-exporter/issues/1
We created that fork mostly to refactor / untangle the different layering of the monolithic onnx-mlir build system so we could "exit" with the onnx-mlir dialect. We did that to start prototyping where to do the torch-mlir backend contract integration which eventually lead to https://github.com/onnx/onnx-mlir/issues/1639  and the corresponding first PR https://github.com/onnx/onnx-mlir/pull/1731 . Unfortunately we are still navigating the CI to make sure all the tests pass.  Having the ability to run the CI locally would help too (we have something like https://github.com/llvm/torch-mlir/blob/main/docs/development.md#mimicing-cirelease-builds in torch-mlir). Once that is done we have a set of follow-on patches for further lowering.
On the build infra side we are happy to help contribute. We setup a similar setup with torch-mlir CI with in-tree LLVM and out-of-tree LLVM builds. @ashay has helped a lot and could possibly have some guidance here too.
In general having a core set that is buildable / testable and others that can be enabled / disabled (like we have MHLO and LTC in torch-mlir) would be super useful for developer velocity.
Overall we (nod.ai team) have multiple customers that are interested in the the onnx-mlir path (ONNX->onnx-mlir->torch_backend-->mhlo/tosa/tcp/linalg/custom) and are willing to help with this effort (once we get our onnx-mlir->torch-mlir backend contract PRs in).

Thanks for your response.

Would you be able to contribute and/or collaborate with the folks from onnx-mlir-exporter to properly switch off what you don't need?

I see this less as a problem with predicating project  features in the build and more of an organizational problem Specifically in this issue I'm recommending to use the LLVM "External Projects" feature to isolate your core dialect (ONNX) that is probably the most useful to downstream projects from the rest of your project. You would essentially be treating it as a dependency in a manner that prevents developers from breaking the "use of ONNXDialect out of onnx-mlir tree" feature. I've submitted a simple rearranement of your build that shows how this works:
https://github.com/onnx/onnx-mlir/pull/1796
Unknown how much  time I would be able to put in to drive this to completion, ideally you guys could help with the issues I describe in the PR (if you agree with this approach).


Stream2

Keep stream cursors from corrupting transactions.

I don't think creating a base class for bson tablet connection, v3 vtgate connection and v2vtgate connection is the way to go here, as we are retiring bson, tablet connection and v3 connection... I'd rather we retire the stuff we don't use first, then refactor?

I can live with that.

Should the bug fix be done though?

I'm going to restrict it to the vtgatev2.py code.


Runing Speed

When I try to segment a point cloud about 30M, the code becomes very slow. How can I solve this problem?

Is the visualization slow or the inference? What GPU do you use?
Some options since 30M is a relatively large point cloud:

Adapt the code after the first positive click to operate (and visualize) only on a 3D bounding box roughly placed around the object to segment. In most cases, you will not need to click all over the scene for an object relatively small. If the object spans the whole scene (eg. a construction beam) it can always be merged together on post-processing based on the same identifier/label.
Crop the scene to smaller pieces in pre-processing
The inference runs on CPU also if needed, it might help with memory.

The visualization and inference speed are both slow. I am using a RTX 4090 GPU. Thank you very much for your suggestion. I am taking the approach of cropping to speed it up.


Help setting up .env file

When I run the command npm run first-time, I get a few errors. I'm wondering if it has to do with how I set up my .env file. This is how I have it set up:
MONGOHQ_URL='mongodb://localhost:27017/freecodecamp'

MANDRILL_PASSWORD=‘XXXXXX’
<EMAIL_ADDRESS>

SESSION_SECRET=secretstuff
COOKIE_SECRET='this is a secret'

PEER=stuff
DEBUG=true

npm run first-time causes problems for a lot of people. Could you paste the error you are getting?

@ltegman

Looks like npm run create-rev fails if the file already exists. What happens if you run node seed/ && node seed/nonprofits? Does that command work?

I'm getting this

I think if you add entries for everything listed in the example .env this should resolve. You can just copy and paste from the example, it doesn't have to be real API keys. Let me know if that works.

node seed/ && node seed/nonprofits seemed to work fine, but I still get the same errors

It works when I rungulp

@ChristianLapinig
MONGOHQ_URL='mongodb://localhost:27017/freecodecamp'

FACEBOOK_ID=stuff
FACEBOOK_SECRET=stuff

GITHUB_ID=stuff
GITHUB_SECRET=stuff

GOOGLE_ID=stuff
GOOGLE_SECRET=stuff

LINKEDIN_ID=stuff
LINKEDIN_SECRET=stuff

MANDRILL_PASSWORD=stuff
MANDRILL_USER=stuff

TRELLO_KEY=stuff
TRELLO_SECRET=stuff

TWITTER_KEY=stuff
TWITTER_SECRET=stuff
TWITTER_TOKEN=stuff
TWITTER_TOKEN_SECRET=stuff

BLOGGER_KEY=stuff

SESSION_SECRET=secretstuff
COOKIE_SECRET='this is a secret'

PEER=stuff
DEBUG=true

I think you should leave the other keys and secrets in the same place. Do not delete them from .env file. Since you have MANDRILL_PASSWORD and MANDRILL_USER, replace the values against them. Leave the remaining lines intact.

Ok so gulp runs the application fine, but npm run first-time has been giving me the same errors. Using the .env file from the example and everything seems to work (At least I think it does)

FYI, for more direct support, you can get help here:
https://gitter.im/FreeCodeCamp/HelpContributors

run first-time will not work after once. As soon as the create-rev part runs successfully it will fail. All it is is create-rev + node seed/ so you're all good now :smile: Let us know if you have any more questions but I'm closing this bug!


MAINT: Filename_parse, identity_parse, tidy_headers, gdrive

Done in preparation for transition to wt3
Requires new dependency, tidy_headers
Should only be Google Drive, tuning, and artists that depend on WrightTools 2 only features (plus a variable renaming here or there, but that is easy, and I think limited to wt.units.unit_dicts to wt.units.dicts).
Google drive code extraction to follow prior, then once attune is ready, we will fully deprecate WT2. At that point, I plan on tagging the 2.X backports branch and closing (tagging mostly so we can refer back to it in it's final stage should there be any questions like "how did we handle this in wt2 days")

Is the plan to put Google Drive code currently in wt2 into PyCMDS somewhere?

Yes, that is the plan

Closing in favor of #209


🐛 Bug Report: Storage error

👟 Reproduction steps
when I try to upload files, I get network request failed. Am using expo
export const uploadDriver = async (file: ImagePickerAsset) => {
  try {
    // remove all spaces, special characters and convert to lowercase
    let name = file.fileName?.replace(/[^a-zA-Z0-9]/g, "").toLowerCase();
    name = name?.replace(/\s/g, "_");
    const response = await storage.createFile(
      DRIVER_BUCKET_ID,
      ID.unique(),
      {
        name: name!,
        type: file.type!,
        size: file.fileSize!,
        uri: file.uri,
      },
      [Permission.read(Role.any()), Permission.write(Role.any())]
    );
    return response;
  } catch (error) {
    console.log("Error uploading image", error);
    throw new Error("Failed to upload image");
  }
};

const pickImage = async () => {
    // Request permission to access media library
    const { status } = await ImagePicker.requestMediaLibraryPermissionsAsync();
    if (status !== "granted") {
      alert("Sorry, we need camera roll permissions to make this work!");
      return;
    }

    // Launch image picker
    const result = await ImagePicker.launchImageLibraryAsync({
      mediaTypes: ImagePicker.MediaTypeOptions.Images,
      allowsEditing: true,
      aspect: [4, 3],
      quality: 1,
    });

    if (!result.canceled) {
      setImage(result.assets[0]);
      try {
        const response = await uploadDriver(result.assets[0]);
        console.log("Image uploaded", response);
      } catch (error) {
        console.log("Error uploading image", error);
      }
    }
  };

👍 Expected behavior
successful upload of image
👎 Actual Behavior
 LOG  Error uploading image [AppwriteException: Network request failed]
LOG  Error uploading image [Error: Failed to upload image]
Also every other things like database insert, user creation is working without any issues, on the storage is not working
🎲 Appwrite version
Version 0.10.x
💻 Operating system
MacOS
🧱 Your Environment
No response
👀 Have you spent some time to check if this issue has been raised before?

[x] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[x] I have read the Code of Conduct

have been able to solve it, this is the solution
I had to add fileTypeExtended as the type
 let name = file.fileName?.replace(/[^a-zA-Z0-9]/g, "").toLowerCase();
    name = name?.replace(/\s/g, "_");
    const uriArray = file.uri.split(".");
    const fileExtension = uriArray[uriArray.length - 1]; // e.g.: "jpg"
    const fileTypeExtended = `${file.type}/${fileExtension}`; // e.g.: "image/jpg"

    console.log("File type", fileTypeExtended);

    const response = await storage.createFile(
      DRIVER_BUCKET_ID,
      ID.unique(),
      {
        name: name!,
        type: fileTypeExtended,
        size: file.fileSize!,
        uri: file.uri,
      },
      [Permission.read(Role.any()), Permission.write(Role.any())]
    );

@SOG-web You should use file.mimType instead of fileTypeExtended.


[stable/redis] Sentinel helm upgrades cause CrashLoopBackOff for last slave

Describe the bug
A clear and concise description of what the bug is.
When we upgrade anything in our sentinel chart using helm upgrade, the last slave's pod becomes unhealthy. In the below repro example, I do a deployment and then upgrade the deployment by adding resource/request limits. This causes the following error:  Back-off 5m0s restarting failed container=sentinel pod=michele-test-redis-slave-2_default(d9383410-8d49-11e9-b7f3-42010ab404ba): CrashLoopBackOff.
Version of Helm and Kubernetes:
$ helm version Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"} Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
K8s cluster version: 1.12.6-gke.11
Which chart:
stable/redis
What happened:
The last slave's sentinel container becomes unhealthy, causing the pod to enter CrashLoopBackOff mode instead of Running mode.
What you expected to happen:
Upgrading the chart via helm upgrade should do a seamless upgrade.
How to reproduce it (as minimally and precisely as possible):

Copy the following into chart.yaml:

cluster:
  slaveCount: 3

password: test

metrics:
  enabled: false

image:
  tag: 5.0.5-debian-9-r14

sentinel:
  enabled: true
  masterSet: "michele-test-redis-master"
  image:
    tag: 5.0.5-debian-9-r14
  # resources:
  #   requests:
  #     memory: 128Mi
  #     cpu: 100m
  #   limits:
  #     memory: 128Mi

master:
  persistence:
    enabled: false
  nodeSelector:
    service: "ads-shared-tools"
  tolerations:
    - key: "service"
      operator: "Equal"
      value: "ads-shared-tools"
      effect: "NoSchedule"

slave:
  persistence:
    enabled: false
  nodeSelector:
    service: "ads-shared-tools"
  tolerations:
    - key: "service"
      operator: "Equal"
      value: "ads-shared-tools"
      effect: "NoSchedule"

Run helm install --name michele-test -f chart.yaml stable/redis

See that everything works fine. All pods are running, etc

Edit chart.yaml with the following, noting that the only difference between these charts is the addition of resource/request limits:

cluster:
  slaveCount: 3

password: test

metrics:
  enabled: false

image:
  tag: 5.0.5-debian-9-r14

sentinel:
  enabled: true
  masterSet: "michele-test-redis-master"
  image:
    tag: 5.0.5-debian-9-r14
  resources:
    requests:
      memory: 128Mi
      cpu: 100m
    limits:
      memory: 128Mi

master:
  persistence:
    enabled: false
  nodeSelector:
    service: "ads-shared-tools"
  tolerations:
    - key: "service"
      operator: "Equal"
      value: "ads-shared-tools"
      effect: "NoSchedule"

slave:
  persistence:
    enabled: false
  nodeSelector:
    service: "ads-shared-tools"
  tolerations:
    - key: "service"
      operator: "Equal"
      value: "ads-shared-tools"
      effect: "NoSchedule"

Upgrade the chart with helm upgrade michele-test -f chart.yaml stable/redis to break things

See that the last slave's sentinel container is in CrashLoopBackOff mode (pics below show the service and pod affected):

Anything else we need to know:

Update: Just as an fyi, I checked and do not see any issues when doing the same upgrade in cluster mode.

Hi @mdeggies, we can reproduce the issue that you are describing. Just to confirm, can you share with us the logs of the sentinel container that is crashing? You can execute:
kubectl logs michele-test-redis-slave-2 sentinel

Yeah, here are the logs from sentinel michele-test-redis-slave-2:
$ kubectl logs michele-test-redis-slave-2 sentinel
Getting information about current running sentinels
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 9eee1c38364e43ca1446d8819077c05991d6f403
sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 766d717d2e0f3524892040d101ab8911b73f9ce3

*** FATAL CONFIG FILE ERROR ***
Reading the configuration file, at line 4
>>> 'sentinel monitor michele-test-redis-master michele-test-redis-master-0.michele-test-redis-headless.default.svc.cluster.local 6379 2'
Can't resolve master instance hostname.
sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3

kubectl logs michele-test-redis-slave-1 sentinel
$ kubectl logs michele-test-redis-slave-1 sentinel
Getting information about current running sentinels
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc31:X 13 Jun 2019 16:50:59.071 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 13 Jun 2019 16:50:59.071 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 13 Jun 2019 16:50:59.071 # Configuration loaded
1:X 13 Jun 2019 16:50:59.073 * Running mode=sentinel, port=26379.
1:X 13 Jun 2019 16:50:59.073 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 13 Jun 2019 16:50:59.077 # Sentinel ID is e70f5b7441b0e8e589a1073329e6986a6382e576
1:X 13 Jun 2019 16:50:59.077 # +monitor master michele-test-redis-master <IP_ADDRESS> 6379 quorum 2
1:X 13 Jun 2019 16:50:59.080 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:50:59.082 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:00.154 * +sentinel sentinel 766d717d2e0f3524892040d101ab8911b73f9ce3 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:09.114 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:10.025 * +sentinel sentinel 9eee1c38364e43ca1446d8819077c05991d6f403 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:19.222 * +fix-slave-config slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.177 # +sdown master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.177 # +sdown sentinel 766d717d2e0f3524892040d101ab8911b73f9ce3 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.239 # +odown master michele-test-redis-master <IP_ADDRESS> 6379 #quorum 2/2
1:X 13 Jun 2019 16:52:23.239 # +new-epoch 1
1:X 13 Jun 2019 16:52:23.239 # +try-failover master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.243 # +vote-for-leader e70f5b7441b0e8e589a1073329e6986a6382e576 1
1:X 13 Jun 2019 16:52:23.243 # +sdown sentinel 9eee1c38364e43ca1446d8819077c05991d6f403 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.254 # 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 voted for e70f5b7441b0e8e589a1073329e6986a6382e576 1
1:X 13 Jun 2019 16:52:23.371 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:34.098 # -failover-abort-not-elected master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:34.156 # Next failover delay: I will not start a failover before Thu Jun 13 16:53:00 2019
1:X 13 Jun 2019 16:52:59.976 # +new-epoch 2
1:X 13 Jun 2019 16:52:59.978 # +vote-for-leader 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 2
1:X 13 Jun 2019 16:53:00.037 # Next failover delay: I will not start a failover before Thu Jun 13 16:53:36 2019

kubectl logs michele-test-redis-slave-0 sentinel
$ kubectl logs michele-test-redis-slave-0 sentinel
Getting information about current running sentinels
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
1:X 13 Jun 2019 16:50:54.039 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 13 Jun 2019 16:50:54.039 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 13 Jun 2019 16:50:54.039 # Configuration loaded
1:X 13 Jun 2019 16:50:54.041 * Running mode=sentinel, port=26379.
1:X 13 Jun 2019 16:50:54.041 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 13 Jun 2019 16:50:54.044 # Sentinel ID is 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3
1:X 13 Jun 2019 16:50:54.044 # +monitor master michele-test-redis-master <IP_ADDRESS> 6379 quorum 2
1:X 13 Jun 2019 16:50:54.047 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:50:54.148 * +sentinel sentinel 766d717d2e0f3524892040d101ab8911b73f9ce3 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:01.087 * +sentinel sentinel e70f5b7441b0e8e589a1073329e6986a6382e576 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:04.104 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:10.025 * +sentinel sentinel 9eee1c38364e43ca1446d8819077c05991d6f403 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:14.186 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:14.277 * +fix-slave-config slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:51:36.650 * +sentinel sentinel bbfcb75265f3c0afaf95310b12f748634b3e5f2a <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.167 # +sdown master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.168 # +sdown sentinel 766d717d2e0f3524892040d101ab8911b73f9ce3 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.168 # +sdown sentinel 9eee1c38364e43ca1446d8819077c05991d6f403 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.249 # +new-epoch 1
1:X 13 Jun 2019 16:52:23.253 # +vote-for-leader e70f5b7441b0e8e589a1073329e6986a6382e576 1
1:X 13 Jun 2019 16:52:23.327 # +sdown slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:24.303 # +odown master michele-test-redis-master <IP_ADDRESS> 6379 #quorum 2/2
1:X 13 Jun 2019 16:52:24.303 # Next failover delay: I will not start a failover before Thu Jun 13 16:52:59 2019
1:X 13 Jun 2019 16:52:59.966 # +new-epoch 2
1:X 13 Jun 2019 16:52:59.966 # +try-failover master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:59.970 # +vote-for-leader 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 2
1:X 13 Jun 2019 16:52:59.979 # e70f5b7441b0e8e589a1073329e6986a6382e576 voted for 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 2
1:X 13 Jun 2019 16:53:10.631 # -failover-abort-not-elected master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:53:10.688 # Next failover delay: I will not start a failover before Thu Jun 13 16:53:36 2019
1:X 13 Jun 2019 16:53:36.216 # +new-epoch 3
1:X 13 Jun 2019 16:53:36.219 # +vote-for-leader e70f5b7441b0e8e589a1073329e6986a6382e576 3
1:X 13 Jun 2019 16:53:36.279 # Next failover delay: I will not start a failover before Thu Jun 13 16:54:12 2019
1:X 13 Jun 2019 16:54:12.440 # +new-epoch 4
1:X 13 Jun 2019 16:54:12.440 # +try-failover master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:54:12.444 # +vote-for-leader 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 4
1:X 13 Jun 2019 16:54:12.454 # e70f5b7441b0e8e589a1073329e6986a6382e576 voted for 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 4
1:X 13 Jun 2019 16:54:22.762 # -failover-abort-not-elected master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:54:22.818 # Next failover delay: I will not start a failover before Thu Jun 13 16:54:48 2019
1:X 13 Jun 2019 16:54:48.793 # +new-epoch 5
1:X 13 Jun 2019 16:54:48.793 # +try-failover master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:54:48.796 # +vote-for-leader 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 5
1:X 13 Jun 2019 16:54:48.822 # e70f5b7441b0e8e589a1073329e6986a6382e576 voted for 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc3 5
1:X 13 Jun 2019 16:54:59.179 # -failover-abort-not-elected master michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:54:59.235 # Next failover delay: I will not start a failover before Thu Jun 13 16:55:25 2019

kubectl logs michele-test-redis-master-0 sentinel
$ kubectl logs michele-test-redis-master-0 sentinel
Getting information about current running sentinels
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 9eee1c38364e43ca1446d8819077c05991d6f403
sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 766d717d2e0f3524892040d101ab8911b73f9ce3
sentinel known-sentinel michele-test-redis-master <IP_ADDRESS> 26379 7d3b60b9ba6b7d4f7f7f3db36d8ff68a69c8efc31:X 13 Jun 2019 16:51:34.631 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 13 Jun 2019 16:51:34.631 # Redis version=5.0.5, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 13 Jun 2019 16:51:34.631 # Configuration loaded
1:X 13 Jun 2019 16:51:34.633 * Running mode=sentinel, port=26379.
1:X 13 Jun 2019 16:51:34.633 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
1:X 13 Jun 2019 16:51:34.637 # Sentinel ID is bbfcb75265f3c0afaf95310b12f748634b3e5f2a
1:X 13 Jun 2019 16:51:34.637 # +monitor master michele-test-redis-master <IP_ADDRESS> 6379 quorum 2
1:X 13 Jun 2019 16:51:44.710 * +slave slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:04.841 * +fix-slave-config slave <IP_ADDRESS>:6379 <IP_ADDRESS> 6379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:23.602 # +new-epoch 1
1:X 13 Jun 2019 16:52:34.645 # +sdown sentinel 766d717d2e0f3524892040d101ab8911b73f9ce3 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:52:34.645 # +sdown sentinel 9eee1c38364e43ca1446d8819077c05991d6f403 <IP_ADDRESS> 26379 @ michele-test-redis-master <IP_ADDRESS> 6379
1:X 13 Jun 2019 16:53:00.297 # +new-epoch 2
1:X 13 Jun 2019 16:53:36.842 # +new-epoch 3
1:X 13 Jun 2019 16:54:13.500 # +new-epoch 4
1:X 13 Jun 2019 16:54:50.001 # +new-epoch 5
1:X 13 Jun 2019 16:55:26.742 # +new-epoch 6
1:X 13 Jun 2019 16:56:03.535 # +new-epoch 7
1:X 13 Jun 2019 16:56:38.231 # +new-epoch 8

Thanks for the information. We will investigate the issue and we will get back to you.

I found that in this case, the master and slave gets re-created at the same time and since the sentinel configuration is not persisted, the slave goes into a crashloop because we bungle up the config by trying to manually discover the sentinels running in the cluster. The redis-sentinel auto-discovers slaves running in the cluster and this manual discovery is not required.
I've submitted the fix for this issue in https://github.com/helm/charts/pull/15005.


use

torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 3.00 GiB. GPU 0 has a total capacty of 23.65 GiB of which 1.66 GiB is free. Including non-PyTorch memory, this process has 20.81 GiB memory in use. Of the allocated memory 12.09 GiB is allocated by PyTorch, and 4.84 GiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF


Check jwt token expiry before making a httprequest

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
Because the jwt token expires every 5 minutes you get a lot of unauthorized messages in the client.
The way it works now by catching an exception every 5 minutes is bad from a performance standpoint but mainly bad design decision because the jwt expiration is an expected behavior and not an exception.
Describe the solution you'd like
Because the jwt token expiration date is known in the client one possible solution is to check expiration date and refresh the token before making the request to the server. That should reduce the number of unauthorized messages a lot.
Additional context
No response

When do we refresh the access token?

When a user navigates to an authorized page during pre-rendering, and the access token is either expired or doesn’t satisfy the roles and policies of the authorized attribute, we redirect the user to the NotAuthorized page. In this NotAuthorized page, we attempt to refresh the token (as the server side does not have a refresh token available during pre-rendering).

If any API HTTP call returns a 401 or 403, we attempt to refresh the token.
403 => meaning the access token doesn’t meet the roles and policies of the authorized attribute

If a user passes an expired access token to SignalR's AppHub, it returns an Unauthorized error, and we then attempt to refresh the token. Connecting to AppHub without any access token yet still valid.

Regarding 403 responses: We try to refresh the token, as it’s possible that the user has gained the required roles and/or claims sicnce last refresh.
An error is only shown in the following cases:

No refresh token is available in storage.

A refresh token completes but results in a 401, indicating the refresh token has expired, or the user’s session no longer exists in the database *

A refresh token completes successfully but attempts to re-render the original page or re-send the original API request still return a 403.

The user is only redirected to the sign-in page if the current page is an authorized page.
Let me know if any additional clarification is needed.
P.S. Please test above scenarios depend on your requirements on the latest stable release that is being published right now.

This is the 12p13 template running with no code changes in wasm mode.
Every single time the token expires I get this error message.

Looking in the AuthDelegatingHandler it's clear that it tries to query the server with SendAsync before it tries to refresh the token

Resolving this issue has started. It will be announced when this issue is resolved.

This issue has been resolved and it will be available in the next pre-release version. It will be announced when the pre-release becomes ready.

the new release is out now.
@Kyemate could you plz test the new version and make sure the issue is resolved?

the new release is out now. @Kyemate could you plz test the new version and make sure the issue is resolved?

Hi, sorry for late reply. The problem seemed solved but now when I tried to with the 9.1p3 template it seems to be back

These errors are typically because you've disabled trackers, as you can see, all those failed requests are related to app insights

There  are some unauthorized requests in there to

What's instrument hook? Could you please test new version on a browser with no extension installed?

I tried it now with chrome without extensions and I still get the 401 error. What I do is I login, wait 5 minutes then I navigate to an authorized page like settings.

Could you please give me your email or phone number that you use to register in online todo or admin demo apps?

I used the default<EMAIL_ADDRESS>account

It's not happening on my side, please do one of the followings:
1- Create new test account on demo apps, do the test again and give me your email address of that test account, so I can search logs based on your user id
OR
2- Do the test with the same<EMAIL_ADDRESS>account, but when issue happened, press Ctrl + Shift + X at the same time and give me your application session id in telemetry context (You can also click on header 7 times or open it by running the App.showDiagnostic() command in browser's dev tools's console)

The app session id is: e8dfe9a2-0938-4ad0-ac27-a6b146fc9db6
But I'm not sure it's logged.

These are being logged through both sentry and app insights
I'll keep you posted
We can also have online meeting to investigate further

Alright, sure I'm up for an online meeting.

Please send me DM on https://join.skype.com/invite/uCpyryqWbUgK
There we will schedule


feat: add PrintOrErr util function and improve devux in cli commands

Description
In cli code we have a lot of code repetition related to handling error and printing proto message.
This PR introduces a PrintOrErr util function to reduce repeated code.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #1157 (c006eb7) into main (069e145) will increase coverage by 0.48%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #1157      +/-   ##
==========================================
+ Coverage   43.65%   44.13%   +0.48%
==========================================
  Files          65       65
  Lines        8460     8367      -93
==========================================
  Hits         3693     3693
+ Misses       4523     4430      -93
  Partials      244      244

Impacted Files
Coverage Δ

x/leverage/client/cli/query.go
0.00% <0.00%> (ø)

Oh, and might also change to refactor prefix in PR title


Digit recognizer

Description
A short summary of what is included in your Pull Request.
Fixes #(issue_no)

[ ] Issue_no: <insert your issue no here>
[x] Not applicable

Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[x] New project insert
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation Update

Project

Your Project Name: MNIST Digit Recognizer

Short Description: This is MNIST handwritten digit recognition project developed using Keras library in Python. Neural network has been created to recognize digits.

Checklist:
Please tick all the boxes that are fulfilled by your Pull Request.

[x] I have named my files and folder, according to this project's guidelines.
[x] My code follows the style guidelines of this project.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] I have created a helpful and easy to understand README.md, according to the given README_TEMPLATE.
[x] My changes do not produce any warnings.

@ndleah Could you please review this PR.


[Bug] blinking pdf

Hi,
When I open a pdf it start to blink.
https://user-images.githubusercontent.com/4999783/205438589-b54451b6-5251-46ab-86d2-d72e5c2c8929.mp4

Hi,
I would expect it to blink once when you open a PDF for the first time, because it is generating a table of contents.
Would it be possible for you to provide a copy of the PDF to me so that I can do some more thorough debugging?

This happen with all PDFs. But, I'll send a bug one.
CheatSheet.pdf

I just tried the PDF and it seems to be working properly in my installation.
What browser are you using (and version), and what operating system?
Looking in the browser console, I'm seeing a lot of warnings about some data in the PDF header:
Warning: Unsupported header type<PHONE_NUMBER> (pclr).
pdf.worker.js:1111 Warning: Unsupported header type<PHONE_NUMBER> (cmap).

Did you create the PDF yourself? Do you know what tool created it?

One last question.
Does the PDF display properly if you disable the "PDF Pager" module?  (When you will have to press the LOAD PDF button)

One last question. Does the PDF display properly if you disable the "PDF Pager" module? (When you will have to press the LOAD PDF button)

Yes. It work well without pager.

I just tried the PDF and it seems to be working properly in my installation.
What browser are you using (and version), and what operating system?
Looking in the browser console, I'm seeing a lot of warnings about some data in the PDF header:
Warning: Unsupported header type<PHONE_NUMBER> (pclr).
pdf.worker.js:1111 Warning: Unsupported header type<PHONE_NUMBER> (cmap).

Did you create the PDF yourself? Do you know what tool created it?

Windows 10
Google Chrome 108.0.5359.95 (oficial) 64 bits and Firefox 107.0.1 (64-bits)
System: SWADE
Module list:

I tried Find the Culprit

Unfortunately libWrapper is unlikely to actually cause the error - it is more likely several modules which use that library are affecting each other.
I tried loading up most of the modules in your list, and I get a swirling circle for longer with the following modules enabled:

Can you try disabling custom CSS?
I don't know what changes the CSS might be making to the PDF pages.

I had the same thing. Steps to reproduce :
1-new world
2-create pdf journal page
3-install pdfpager module
4-try to open journal page
5-blink happens
6-edit page, save
7-doesn't blink anymore
IMHO it comes down to having a pdf page number stored with your journal page entry

I would expect it to blink once when you set up a new PDF, because it calculate the journal's table of contents from the Outline inside the PDF (which causes the page to reload when the table of contents is displayed). But after that there shouldn't be a continuous blinking.

I had the same thing. Steps to reproduce :
1-new world 2-create pdf journal page 3-install pdfpager module 4-try to open journal page 5-blink happens 6-edit page, save 7-doesn't blink anymore
IMHO it comes down to having a pdf PageOffset stored with your journal page entry

This stops the blink. But, I have several worlds with lots of PDFs. Is it possible to fix this?
https://user-images.githubusercontent.com/4999783/208421317-9763c004-40e6-48d7-a222-7ade99235aaa.mp4

I had the same thing. Steps to reproduce :
1-new world 2-create pdf journal page 3-install pdfpager module 4-try to open journal page 5-blink happens 6-edit page, save 7-doesn't blink anymore
IMHO it comes down to having a pdf PageOffset stored with your journal page entry

When these specific steps are used with a PDF without an outline, and the PDF page has not already been loaded at least once, then the above steps were enough to cause the constant reloading.
Version 0.36.2 should fix this problem (although it seems like a lower level lack of optimisation that really caused the problem - unsetFlag caused the page to load, even if the flag never existed on the document).


[3.x] SpriteFramesEditor Reallow deselecting frame with LMB press in select frames dialog

Fixes #63811.
It got broken when cherry-picking, one line change (L127/R155) was incorrectly not picked:
https://github.com/godotengine/godot/commit/ad7a6102aed9ca25524d169570c29a599ab8e2a5#diff-3e7f486c64d2a3de1a4c3fcde4afc7705675df0adf3af634f78f67ebbaf4bddbL127-R156
https://github.com/godotengine/godot/commit/891681a5a328dd80630f1e75c7b8430d32125511#diff-3e7f486c64d2a3de1a4c3fcde4afc7705675df0adf3af634f78f67ebbaf4bddbR155-R156

Thanks!

Cherry-picked for 3.5.1.


Use background loop for query translation and transmission

This pull request will be replaced with the solution in PR https://github.com/opencybersecurityalliance/kestrel-lang/pull/355


Unable to capture failed task

When task failed and its corresponding process ended, the task state is still in running state.

addressed by #2


Support 1:1 NAT option

Resolves #835
Added these parameters configured via SettingEngine

NAT1To1IPs []string - an array external IP addresses
NAT1To1IPCandidate - target candidate the external IP address is used for ("host" or "srflx")

See #835 for details.

Codecov Report

Merging #845 into master will decrease coverage by 0.09%.
The diff coverage is 50%.

@@           Coverage Diff            @@
##           master    #845     +/-   ##
========================================
- Coverage    76.7%   76.6%   -0.1%
========================================
  Files          60      60
  Lines        4262    4278     +16
========================================
+ Hits         3269    3277      +8
- Misses        719     727      +8
  Partials      274     274

Impacted Files
Coverage Δ

settingengine.go
45.45% <0%> (-6.27%)
:arrow_down:

ice_go.go
90% <100%> (+0.52%)
:arrow_up:

icegatherer.go
82.32% <60%> (-0.94%)
:arrow_down:

dtlstransport.go
74.43% <0%> (-1.14%)
:arrow_down:

sctptransport.go
75.62% <0%> (+1.25%)
:arrow_up:

Continue to review full report at Codecov.

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

I will do https://github.com/pion/webrtc/issues/778 after this next!

is there any reason not to use one call with both parameters in settingsengine?

No! I TOTALLY forgot our original plan! Thank you for noticing it! I will fix it!

@seppo0010 Now it looks like this:
func (e *SettingEngine) SetNAT1To1IPs(ips []string, candidateType ICECandidateType)

@enobufs I think the createAgent is not honoring the settings
something like this around line 143 is missing:
NAT1To1IPs: g.nat1To1IPs,
NAT1To1IPCandidateType: g.nat1To1IPCandidateType,


1.2.0 + migrations

Pick up some open PRs.
Builds on #40 & #41
Closes #41
Closes #40
Closes #39
Closes #38
Closes #37

@conda-forge/topologytoolkit, this is ready for review!
Itshould unblock a whole lot of things, and so I'd like to merge it soon-ish. It's probably easiest to review commit-by-commit. Happy to explain if you're unsure about some changes.


Celery workers shutdown and do not restart after reaching CELERYD_MAX_TASKS_PER_CHILD

We've been having an issue where celery workers shut down and do not restart after reaching CELERYD_MAX_TASKS_PER_CHILD.
In attempting to diagnose the issue, I've explored a few configurations:

Ubuntu, django db backend+postgres: fails
Ubuntu, rabbitmq: works fine
OS X, django db backend+sqlite: works fine

When workers die, the final log messages, when running with the DEBUG log level are:
[2016-06-15 12:00:26,105: INFO/MainProcess] Task study.models.parse_study[3c1850ab-090f-4332-adb9-4c8e9ab56293] succeeded in 1.2661089329994866s: None
[2016-06-15 12:00:29,938: DEBUG/MainProcess] Canceling task consumer...
[2016-06-15 12:00:30,857: DEBUG/MainProcess] Canceling task consumer...
[2016-06-15 12:00:30,858: DEBUG/MainProcess] Closing consumer channel...

Failing configuration:
 -------------- celery@app1 v3.1.23 (Cipater)
---- **** -----
--- * ***  * -- Linux-3.2.0-59-generic-x86_64-with-Ubuntu-12.04-precise
-- * - **** ---
- ** ---------- [config]
- ** ---------- .> app:         project:0x7f285fc06f28
- ** ---------- .> transport:   django://localhost//  # NOTE: Django 1.8, PostgreSQL DB
- ** ---------- .> results:     disabled://
- *** --- * --- .> concurrency: 1 (prefork)
-- ******* ----
--- ***** ----- [queues]
 -------------- .> celery           exchange=celery(direct) key=celery

are you using django as transport? what about increasing the max number?

I am using django as the broker/message transport when it fails, yes.  Increasing the max number increases the number of tasks that succeed before it falls down again correspondingly.

using django as a broker is not a good idea

I'm having this same issue with v3.1.23 and a redis broker.

The same issue with Celery 3.1.25 + prefork + redis broker + djcelery + django db result backend.
On Ubuntu 16.04
All child processes turned zombie (defunct) after finishing the tasks.

The same issue with Celery 4.1.0, broker is redis.

this is not recommended package with celery greater or equal 4.x.x

@auvipy what's your recommendation about version?

check the latest docs!


PostGres single-node package.

PostGres package running PostGres 9.5 with PostGIS 2.2 extensions in DCOS in a single-node layout. Future release will support DB replication to allow for multiple read-replicas.
Resubmission to satisfy requested 3.0 packaging update from #477.

@gisjedi we have a postgres package. this PR can be closed.

@ryadav88 This can be closed out as there appears to be an existing Postgres package in the universe.


UnzipFile is vulnerable to Zip Slip #5497

@eric-martin  I don't think we need to push the zip file.


Make separate builds for tests on Travis CI

This makes the build look nicer on Travis CI.

👍 thanks


MTL failed to run rwkv-4-world-7b: Failed to load libsycl-fallback-bfloat16.spv

MTL (Ultra 5 125H + 32GB 7467MHz) failed to run rwkv-4-world-7b.

Configured according to: https://ipex-llm.readthedocs.io/en/latest/doc/LLM/Quickstart/install_windows_gpu.html. The oneAPI is installed using pip installer. The commands I used are as follows. Don't set SYCL_CACHE_PERSISTENT and remember to change the test_api to transformer_int_gpu_win.
conda create -n your_llm python=3.9 libuv
conda activate your_llm
pip install dpcpp-cpp-rt==2024.0.2 mkl-dpcpp==2024.0.0 onednn==2024.0.0
pip install --pre --upgrade ipex-llm[xpu] -f https://developer.intel.com/ipex-whl-stable-xpu
set BIGDL_LLM_XMX_DISABLED=1
python run.py

Env
bigdl-core-xe-21            2.5.0b20240327
ipex-llm                    2.1.0b20240327

And we can't find libsycl-fallback-bfloat16.spv after windows pip install in the environment, but it is there when using the offline installer or using pip install on linux.


Fix typo in Microsoft.Framework.Caching.SqlServer\SqlServerCache.cs

This PR fixes a typo in SqlServerCache : a private field was named _systemCock instead of _systemClock.

Hi @mgrosperrin, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Lol thanks for the PR :smile:

@kichalla please merge this ASAP...

Thanks @mgrosperrin :smile:

You're welcome, I was happy to help :smile:


Not an issue but I don't know where to post my appreciation

Description of the new feature / enhancement
I dont need shit. This helped me throughout my high school life.  Keep doing whatever you're doing out there! It may be a really simple app but it brings a lot to the table.
Scenario when this would be used?
.
Supporting information
.

I don't know how github works so if ya'll want me to delete this, its alright.

Thanks a lot for the feedback! :)


Single checkbox's label style is not the same as multi-checkbox's labels

This one is correct:

Will be closed by #1566


install-tool no longer respects https_proxy env vars since version 9.7.0

Expected behavior
When downloading files during execution of install-tool a proxy configured via https_proxy env var should be used to download files.
$ install-tool helm v3.12.2
[08:00:41.124] INFO (60): Installing tool helm v3.12.2...
installing v2 tool helm v3.12.2
linking tool helm v3.12.2
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /builds/argerten/playground.tmp/KUBECONFIG
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /builds/argerten/playground.tmp/KUBECONFIG
version.BuildInfo{Version:"v3.12.2", GitCommit:"1e210a2c8cc5117d1055bfaa5d40f51bbc2e345e", GitTreeState:"clean", GoVersion:"go1.20.5"}
[08:00:42.854] INFO (60): Installed tool helm in 1.7s.

Actual behavior
install-tool runs into a timeout (because the execution environment does not allow direct internet access).
install-tool helm v3.12.2
[07:56:46.652] INFO (57): Installing tool helm v3.12.2...
installing v2 tool helm v3.12.2
[07:56:46.863] INFO (84): Downloading file ...
    url: "https://get.helm.sh/helm-v3.12.2-linux-amd64.tar.gz"
    output: "/tmp/e967b8b92ca5b74b3690cc7c824c082b94415b513269e0d8a513bfa0e9d76e0a/helm-v3.12.2-linux-amd64.tar.gz"
[07:58:58.048] FATAL (84): connect ETIMEDOUT <IP_ADDRESS>:443
    err: {
      "type": "RequestError",
      "message": "connect ETIMEDOUT <IP_ADDRESS>:443",
      "stack":
          RequestError: connect ETIMEDOUT <IP_ADDRESS>:443
              at ClientRequest.<anonymous> (/snapshot/dist/containerbase-cli.js:37024:94)
              at Object.onceWrapper (node:events:652:26)
              at ClientRequest.emit (node:events:549:35)
              at TLSSocket.socketErrorListener (node:_http_client:465:9)
              at TLSSocket.emit (node:events:537:28)
              at emitErrorNT (node:internal/streams/destroy:151:8)
              at emitErrorCloseNT (node:internal/streams/destroy:116:3)
              at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
              at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1237:16)
      "code": "ETIMEDOUT",
      "timings": {
        "start":<PHONE_NUMBER>872,
        "socket":<PHONE_NUMBER>873,
        "lookup":<PHONE_NUMBER>065,
        "error":<PHONE_NUMBER>037,
        "phases": {
          "wait": 1,
          "dns": 192,
          "total": 131165
        }
      },
      "name": "RequestError",
      "options": {
        "agent": {},
        "decompress": true,
        "timeout": {},
        "prefixUrl": "",
        "ignoreInvalidCookies": false,
        "context": {},
        "hooks": {
          "init": [],
          "beforeRequest": [],
          "beforeError": [],
          "beforeRedirect": [],
          "beforeRetry": [],
          "afterResponse": []
        },
        "followRedirect": true,
        "maxRedirects": 10,
        "throwHttpErrors": true,
        "username": "",
        "password": "",
        "http2": false,
        "allowGetBody": false,
        "headers": {
          "user-agent": "got (https://github.com/sindresorhus/got)",
          "accept-encoding": "gzip, deflate, br"
        },
        "methodRewriting": false,
        "retry": {
          "limit": 2,
          "methods": [
            "GET",
            "PUT",
            "HEAD",
            "DELETE",
            "OPTIONS",
            "TRACE"
          ],
          "statusCodes": [
            408,
            413,
            429,
            500,
            502,
            503,
            504,
            521,
            522,
            524
          ],
          "errorCodes": [
            "ETIMEDOUT",
            "ECONNRESET",
            "EADDRINUSE",
            "ECONNREFUSED",
            "EPIPE",
            "ENOTFOUND",
            "ENETUNREACH",
            "EAI_AGAIN"
          ],
          "backoffLimit": null,
          "noise": 100
        },
        "method": "GET",
        "cacheOptions": {},
        "https": {},
        "resolveBodyOnly": false,
        "isStream": true,
        "responseType": "text",
        "url": "https://get.helm.sh/helm-v3.12.2-linux-amd64.tar.gz",
        "pagination": {
          "countLimit": null,
          "backoff": 0,
          "requestLimit": 10000,
          "stackAllItems": false
        },
        "setHost": true,
        "enableUnixSockets": false
      }
    }
[07:58:58.051] INFO (84): Download completed with errors  in 2m 11.1s.
Download failed: https://get.helm.sh/helm-v3.12.2-linux-amd64.tar.gz
[07:58:58.065] FATAL (57): Command failed with exit code 1: /usr/local/containerbase/bin/install-tool helm 3.12.2
    err: {
      "type": "Error",
      "message": "Command failed with exit code 1: /usr/local/containerbase/bin/install-tool helm 3.12.2",
      "stack":
          Error: Command failed with exit code 1: /usr/local/containerbase/bin/install-tool helm 3.12.2
              at makeError (/snapshot/dist/containerbase-cli.js:38310:13)
              at handlePromise (/snapshot/dist/containerbase-cli.js:38765:29)
              at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
              at async InstallLegacyToolService.execute (/snapshot/dist/containerbase-cli.js:39637:5)
              at async InstallToolService.execute (/snapshot/dist/containerbase-cli.js:39803:7)
              at async InstallToolShortCommand.execute (/snapshot/dist/containerbase-cli.js:39872:14)
              at async InstallToolShortCommand.validateAndExecute (/snapshot/dist/containerbase-cli.js:1342:26)
              at async _Cli.run (/snapshot/dist/containerbase-cli.js:2455:22)
              at async _Cli.runExit (/snapshot/dist/containerbase-cli.js:2463:28)
              at async main (/snapshot/dist/containerbase-cli.js:40006:3)
      "shortMessage": "Command failed with exit code 1: /usr/local/containerbase/bin/install-tool helm 3.12.2",
      "command": "/usr/local/containerbase/bin/install-tool helm 3.12.2",
      "escapedCommand": "\"/usr/local/containerbase/bin/install-tool\" helm 3.12.2",
      "exitCode": 1,
      "failed": true,
      "timedOut": false,
      "isCanceled": false,
      "killed": false
    }
[07:58:58.073] INFO (57): Installed tool helm with errors in 2m 11.4s.

This used to work until version 9.6.2 and broke with version 9.7.0. I'd suspect the replacement of curl to download files to cause this issue: https://github.com/containerbase/base/commit/cdec808f716fa8dd8ad3c9d8302e9d0663ef85ab#diff-28a534928943da3d486bb4bdd14e9440275bca5c1ff6ba37e8e8aab6c9857f8bR93

Duplicate of #1237


Clicking in the scrollbar jumps to where I clicked

Why, in the latest version, clicking in the scrollbar jumps to where I clicked? It should just scroll to the next "page", as I specified in "System Preferences" -> "General": "Click in the scroll bar to:" -> "Jump to the next page" vs. "Jump to the spot that's clicked".
Steps to Reproduce:
In VSCode version 1.41.0, click in the scroll bar of any long file opened.
Observe the behaviour.
This feature was initially requested here :
https://github.com/microsoft/vscode/issues/87273

/duplicate of #43564


can not Authorize FHIRServerProxy-1

After running the deployhl72fhir.bash script everything is set up.
After that FHIRServerProxy-1  API Connection is in Error state ( This connection is not authenticated )
When attempting to Authorize I am directed to a login form for my credentials and getting this error message after logging in:
AADSTS90008: The user or administrator has not consented to use the application with ID '3648ca46-8d1e-4d62-8cde-27c00e70b03b'(https://sfp-proxy18447.azurewebsites.net). This happened because application is misconfigured: it must require access to Microsoft Graph by specifying at least 'Sign in and read user profile' permission.
In the documentation it is stated :
%%%%%
Goto the resource group that contains the deployed HL7toFHIR workflow
Find the FHIRServerProxy-1 API Connection and click on it
Click on Edit API Connection
Enter a Display name of FHIR Server Proxy
Click Authorize
Enter the Credentials for the user account, group or service principal from step #4
Click Save
%%%%%
3648ca46-8d1e-4d62-8cde-27c00e70b03b was created by the scripts and the values added to the key vault.
How can be this issue resolved?  Where should I "Enter the Credentials for the user account, group or service principal from step #4"?

looking into this

I had granted Admin consent for the mentioned Enterprise application created by the script in the Permissions section:
'3648ca46-8d1e-4d62-8cde-27c00e70b03b'(https://sfp-proxy18447.azurewebsites.net)
Now after clicking Authorize in  FHIRServerProxy-1 API Connection  and logging in, I am getting this new error :
AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: '3648ca46-8d1e-4d62-8cde-27c00e70b03b'.
Where should be the reply URL changed and to what?

I had granted Admin consent for the mentioned Enterprise application created by the script in the Permissions section: '3648ca46-8d1e-4d62-8cde-27c00e70b03b'(https://sfp-proxy18447.azurewebsites.net)
Now after clicking Authorize in FHIRServerProxy-1 API Connection and logging in, I am getting this new error :
AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: '3648ca46-8d1e-4d62-8cde-27c00e70b03b'.
Where should be the reply URL changed and to what?

There should be 2 reply url's in your app where $fphost = name of your proxy function app and $resourceGroupLocation = name of your region (without spaces)
https://"$fphost"/.auth/login/aad/callback
https://logic-apis-"$resourceGroupLocation".consent.azure-apim.net/redirect

Thank you, that helped.
The first url was already present (https://"$fphost"/.auth/login/aad/callback ), added the second one and it started working.


Updated to a newer version of bootstrap-datepicker to fix z-indexing

Updated to a newer version of bootstrap-datepicker. This fixes the z-indexing issue when selecting the effective date when importing a measure.

You mentioned that the date picker default location has moved to over vs under, and I didn't think that would be an issue, but I tried it out and it actually feels awkward to me. Is there a way to change the behavior so that it works as it used to?
Also, it looks like you may have tried to rebase this pull request, but it looks like there's a merge on it now, which we should clear up; we just want a single commit on this branch that contains the changes.

I redid my changes against the latest revision of master. This single commit updates the library and initializes the datepickers with the 'bottom left' orientation option.

The only difference I see now is that if the field is scrolled to the bottom of the page, it no longer automatically moves the popup to the top. I think that's ok, and I'll merge this.


GM can set default system to use

Allow the GM to set what system should be selected by default for all players. Should this be the system selected each time they open the roller, or just the first time it's opened after the setting is set/changed?

Implemented!


Add query buttons of selectorName and ruleName in PluginList/plugin page

This is the frontend code for #1328


Add dependency and remove requirement from manifest.json

We have a dependency on MQTT that needs to be initialised before we start reaching out to the device. We also don't need to explictly call out paho-mqtt as a dependency as it is required by HA more generally and is not specific to Dyson.

Can we get a review on this please?

Ahh sorry, this slipped through the cracks. I'll take a look today or tomorrow.


Apply is not working

I’m finding the plan works fine, but Atlantis logs the following warning on the subsequent apply: Unable to update commit status: POST https://gitlab[redacted]: 400 {message: Cannot transition status via :enqueue from :pending (Reason(s): Status cannot transition via "enqueue")}
Helm chart version: 3.12.4
VCS: Gitlab
Result: The pipeline gets stuck to pending forever.

@stafot please post Atlantis issues that aren't related specifically to the Helm chart in https://github.com/runatlantis/atlantis

@stafot please post Atlantis issues that aren't related specifically to the Helm chart in https://github.com/runatlantis/atlantis


using outdated @cts in new release

There are quite a few @cts missing, that are unstable and buggy - and fixed versions already have been made in the #act-share in the ppooll discord. Acts i've noticed already: forbiddenplannet (vocoder is broken), the new ll.blues is very problematic, changing send amounts from one act to another is very unpredictable, if you want to upload some of the best acts from the discord, i'd really reccomend taking a look at the efx acts they are wonderful and could use some love! Thank you once again ppooll, the elites of music production software!

dear @50NNY1 ,
i'm not sure i can follow exactly what your issues are. please try to describe the issues more precisely, and only one topic per issue thread!
please post general feedback in the discussions under "user feedback":
https://github.com/ppooll-dev/ppooll/discussions/categories/user-feedback
(issues should be reserved for bug reports or feature requests).
anyway thanks for your words and using pppooll! 😊

ps: please don't misread it that i closed your issue – we're very happy to have feedback, it was just the wrong location for it with the current wording.
regarding blues: if you have a specific issue with it please describe it clearly and open up a new issue!!


discard(), update rspirv, better capability computation

We could bikeshed on the names of discard() and demote_to_helper_invocation(), but I hope with the doc comments it's pretty clear to users regardless of the exact names.
Capability computation was apparently borked, as we were including e.g. OpCapability DerivativeControl in our shaders even without calling the derivative functions. We should probably rethink this area, the current system is still a "temporary" hack. I cleaned up the hack a little bit, but it's still pretty gross and weird.

and to answer questions about "why not just default to demote to helper invocation always, not even support OpKill", I get this error message on my modern desktop GPU with up-to-date drivers:

Shader requires VkPhysicalDeviceShaderDemoteToHelperInvocationFeaturesEXT::shaderDemoteToHelperInvocation but is not enabled on the device

and to answer questions about "why not just default to demote to helper invocation always, not even support OpKill", I get this error message on my modern desktop GPU with up-to-date drivers:

Shader requires VkPhysicalDeviceShaderDemoteToHelperInvocationFeaturesEXT::shaderDemoteToHelperInvocation but is not enabled on the device


Proof of concept: calling remote interactors

Depends on #166
I've been unable to knock this idea out of my head. So my weekend hack was to try and see if I could actually make it work. And it kinda sorta works, with a lot of caveats! But I think it proves that the idea itself is fundamentally interesting.
Background
One of the big missing pieces of BigTest and Interactors is that Interactors currently need to be running in the same process as the test runner. This limits us a lot in terms of how interactors can be used. For example we can never have the test runner and the page under test be on different origins, which is very limiting. In many cases, calling interactor directly is good, but in some cases, it would be better to have a request/response cycle for this.
Implementation
This uses the addInteractionWrapper API to make it possible to call interactors running in a different process. Basically when writing your test, you would use interactors as you normally would, but instead of running them in the current process, the interaction is serialized and sent over a websocket connection running in another process (could be a browser!).
Try it out!
Start the server:
cd packages/remote
yarn ts-node example/server.ts

Then run the client:
cd packages/remote
yarn ts-node example/client.ts

You should see output like this:

Note that "Some Link" is rendered in a JSDOM context running in the server!!!
Limitations

The implementation of the interactor must match between the client and server for this to behave as expected.
Multiple interactors must not have the same name
The server is currently running a websocket server, which is limiting since we want it to run in a browser. It should be running a websocket client as well.
Composed interactors are not yet implemented (but should be trivial)
It's generally a hacky pile of jank. This is not production grade stuff at all. There are any number of edge cases which will cause this to very much blow up.

@jnicklas @cowboyd I have an idea how we can bypass the first two limitations. When we get interaction in our wrapper we calculate hash from interaction name, available filters/actions, default filters values. So it's like duck typing. And do the same thing on a client for all imported interactors.

@jnicklas @cowboyd I have an idea how we can bypass the first two limitations. When we get interaction in our wrapper we calculate hash from interaction name, available filters/actions, default filters values. So it's like duck typing. And do the same thing on a client for all imported interactors.

@wKich Interesting! I think we would also need to check the arity of the action functions too, right?

This is relevant to support Playwright #191 which has its own protocol for referencing and interacting with objects in a remote page. Maybe some abstraction could be made?

Yeah, I already thought about that. But actually for the playwright we can have another solution.
We can add function exposer, ask user to put all his interactors there. That exposer exposes interactors in global namespace, so they will be available through window.Button for example or window.__INTERACTORS__.Button. Then we create helpers for the playwright, like cy.do or cy.expect in these helpers we just need to get code representation and call page.evaluate() with exposed interactors. The problem is you can't pass non-serializable things as well as in this spike.

The problem is you can't pass non-serializable things as well as in this spike.

We would need a similar mechanism for matchers

@cowboyd, yeah, we missed that point

Since the effection branch was merged (yay!), I've rebased and updated this PR. I've also extracted #197 out of this as a generally sensible thing to do, which shows how remote interactors can really be implemented on top of our existing interactors.


Add to Sugar instead of a separate package

@quozl, can we add this to sugar instead of keeping it as a separate package ?

I'll fork to sugarlabs so we can remember we use it, but as @dnarvaez vanished, I'm not sure we can do much about this original repository.
In another fork, https://github.com/curiousguy13/gwebsockets contains a port to Python 3.

I'm not quite sure what you mean.  To me, a package is usually a .deb or .rpm file.  But perhaps you mean Python module?  gwebsockets is a package now, on Debian and Ubuntu, and there may be software depending on it, so I suggest porting it to Python 3, make a release in absence of @dnarvaez, and mention the new release to Fedora and Debian team.

Sure, will do that


ServerRequestFactory

This all works fine. Great.
But why all the logic is concentrated in one place?
Moreover, there is a class of Server.
I think it would be better to make a directory of the factories.
Firstly, it allows to separate each logic element in its factory.
Secondly, because I can always get in the code of the original values.
For example, Zend\Diactoros\Factory\HttpProtocolFactory:
use UnexpectedValueException;

class HttpProtocolFactory
{
    public static function make(array $server = null)
    {
        if (empty($server)) {
            $server = $_SERVER;
        }

        if (! isset($server['SERVER_PROTOCOL'])) {
            return '1.1';
        }

        $protocol = $server['SERVER_PROTOCOL'];

        if (! preg_match('#\A(?:HTTP/)?(?P<version>\d{1}\.\d+)\Z#', $protocol, $matches)) {
            throw new UnexpectedValueException(sprintf(
                'Unrecognized protocol version "%s".',
                $server['SERVER_PROTOCOL']
            ));
        }

        return $matches['version'];
    }
}

All this is true for the request method, headers, Uri, uploaded files etc

Originally posted by @easy-system at https://github.com/zendframework/zend-diactoros/issues/158

And for the host is must be required!
forced host... This is not such a rare situation. And it should be done without interfering with the application logic, the best from the index.php
use DomainException;

class ServerHostFactory
{
    protected static $forcedHost = '';

    public static function setForcedHost($host)
    {
        static::$forcedHost = $host;
    }

    public static function getForcedHost()
    {
        return static::$forcedHost;
    }

    public static function make(array $server = null)
    {
        if (! empty(static::$forcedHost)) {
            return static::$forcedHost;
        }

        return static::calculate($server);
    }

    public static function calculate(array $server = null)
    {
        if (empty($server)) {
            $server = $_SERVER;
        }

        // from server config, if present
        if (isset($server['SERVER_NAME'])) {
            return $server['SERVER_NAME'];
        }

        // from headers, dangerous to use
       /* if (isset($server['HTTP_HOST'])) {
            return $server['HTTP_HOST'];
        }*/

        throw new DomainException(
            'Missing host in server parameters.'
        );
    }
}

Originally posted by @easy-system at https://github.com/zendframework/zend-diactoros/issues/158#issuecomment-195967151

Ok. Im delete this from public.
P.S.: reported

Originally posted by @easy-system at https://github.com/zendframework/zend-diactoros/issues/158#issuecomment-195991259

No longer relevant.


NPM 5 support

This PR follows this one : https://github.com/rauchg/slackin/pull/344.
It adds a package-lock.json that npm 5 uses to lock inner dependencies.

Closing this PR because this project seems to be dead and I don't want to keep this fork forever. Good riddance.