Docker image for Selenium-Grid_Extras

Hi ,
I have been long fan of selenium grid extras currently we a selenium grid have 20 nodes running using SG Extras, and i am planning to migrate this grid to docker based , was just wondering if there is an official image for the same?
Has anyone has tried running the SG EXTRA using docker ? Any help/pointer would be useful

This has been discussed before, at least privately. We think it is a good idea. There is currently not a docker image we provide, but any help would be appreciated.
@dimacus You talked to me about this awhile ago.

there is an example https://github.com/banuchka/selenium_scope/tree/master/SeleniumExtraGrid

I am working on this.  I am able to  run tests and even capture videos.  But l found grid extra assumes some utility like killall present. It also issues reboot... Which are not working . On Grid nodes browsers crashes occasionally. Extra is not cleaing it. I  didn't see logs for cleaup browser.  I have asked Shawn's help. Once I get it stable i will submit a pull request to this repository.

By the way i forgot to mention that I have used swarm cluster instead of single machine. It allows me to scale more selenium nodes.

@shankarkc if crashes are happening only on Chrome it might be due to this and here a solution

Any updates on this enhancement? Is there any testing or development work that we the community can pair or assist with? I'd love for their to be an official community provided docker image but want to avoid redundant efforts if possible

I have created docker images and they work on swarm cluster... Working good
for us.  I am planning to open source it soon. I will update you once its
in public git up.. Eta is about a week. It has even sikuli integration for
ui tests.
On Feb 15, 2017 12:43 AM, "gabecase"<EMAIL_ADDRESS>wrote:

Any updates on this enhancement? Is there any testing or development work
that we the community can pair or assist with? I'd love for their to be an
official community provided docker image but want to avoid redundant
efforts if possible
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/252#issuecomment-279805165,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEb7VyFlEK4hHfsLGeQuPyZw8qStPI_Xks5rcfzLgaJpZM4J13g0
.

These are the changes that you can expect from docker selenium grid extra:-
This docker image uses docker native swarm cluster and service architecture to spin the containers. In few secs you can scaleup and scaledown the nodes.
It uses SeleniumGridExtra binaries to create grid.
It has Sikuli integration so that user can use it for FileUpload and UI tests.
As its using SeleniumGridExtra you have the ability to download test video and OS level screenshot.
Using this grid you can automte scenarios like file download....File get downloaded on remote node machine....Using sikuli APIs you can transfer it to your local machine.

@shankarkc I would be interested if you (or anyone else) has a working dockerfile available.
I have tried to create my own, connecting to an existing hub and nodes in separate docker containers but with no success so far.

Yes... I have selenium grid extra on docker swarm working end to end.  Our
teams are using it with great success.
On Jun 2, 2017 6:15 AM, "Russell Clarke"<EMAIL_ADDRESS>wrote:

@shankarkc https://github.com/shankarkc I would be interested if you
(or anyone else) has a working dockerfile available.
I have tried to create my own, connecting to an existing hub and nodes in
separate docker containers but with no success so far.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groupon/Selenium-Grid-Extras/issues/252#issuecomment-305658666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEb7V8J0jTY9mtUumWo6MOMASZXkdkuuks5r_1stgaJpZM4J13g0
.

Thanks @shankarkc . Can you share the relevant docker-compose.yaml and Dockerfiles?

I uploaded docker images for selenium-grid-extras for hub, chrome and firefox to the Docker Hub.
You can find the source code here and help me test them: https://github.com/viltgroup/docker-selenium-grid-extras

Thanks @mariolameiras ! I will close this issue and add a link to your repo in the README.


chore: remove 99% of the duplicated code for the editor steps resolvers

Sorry @gashcrumb, I could have figured out this earlier 😅

PR Storybook available here

Actually, let me check if I can pull off something similar for the actual apps.

:+1: less code!

I think this is good enough for the moment.

https://github.com/syndesisio/syndesis-react/blob/768c1e75f8b97a75756c7e752c78e2eb3634cd7d/app/ui-react/syndesis/src/modules/integrations/components/editor/EditorApp.tsx
This is where new configurators (I really don't know how to call them, is configurator an ok name?) need to be wired. The idea is that since the whole editor app is built on top of the subSteps routes and relative resolvers, we can assume how all the "configurators" should be wired. The only exercise left to the consumer of the EditorApp is to tell the editor mode (if it's editing an existing step or adding a new one) and where to when canceling the configurator and when mutating the integration.

PR Storybook available here

On this amq 2 log integration if I go and look at the template step it's listed twice in the sidebar:

Also 'Cancel' from say the action configuration page for a connection takes me back to the integration list, it used to take me to the add step page.

Similar happens when I go to this sql2sql integration and click 'configure' for the finish step:

Also the 'Next' button is disabled even though there's valid config.  I added this bit to get around it.  Though I guess actually it'd be better to figure out why it's setting isValid to false even if the input data is valid, doesn't need to happen for this PR.

Also the 'Next' button is disabled even though there's valid config. I added this bit to get around it. Though I guess actually it'd be better to figure out why it's setting isValid to false even if the input data is valid, doesn't need to happen for this PR.

Yeah, that happens when there is a default value. I haven't thought about how to fix it.

Btw sidebar and cancel buttons should be ok now.

Yeah, that happens when there is a default value. I haven't thought about how to fix it.

Lemme get an issue raised for it, we'll see this kinda thing in a few places.

Btw sidebar and cancel buttons should be ok now.

Awesome!  Will retest and see if I spot anything else.

PR Storybook available here


⚠ Bofrost.at has degraded performance

In 5518bd7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1888 ms

Resolved: Bofrost.at performance has improved in f4ab76b.


stopping all running commands programmatically

It would be nice to get a killall method on ControlledCommandHandle that allows to kill all subtasks.
Background: I have a Rust app that programmatically starts a number of subtasks, does something, and then needs to shut them all down programmatically.

Kill should kill everything so if that isn't working, this is a bug that needs to be fixed

@kevgo
I've tried to replicate with the following program but all threads are killed as expected:
(Note that /tmp/tmp.TuAMUcExAU/hello is just a simple program with an infinite loop).
use currant::Color;
use currant::Command;
use currant::ConsoleCommand;
use currant::Runner;
use std::thread;
use std::time::Duration;
fn main() {
    let handle = Runner::new()
        .command(
            ConsoleCommand::from_string("test1", "/tmp/tmp.TuAMUcExAU/hello")
                .unwrap()
                .color(Color::BLUE),
        )
        .command(
            ConsoleCommand::from_string("test2", "/tmp/tmp.TuAMUcExAU/hello")
                .unwrap()
                .color(Color::RED),
        )
        .command(
            ConsoleCommand::from_string("test3", "/tmp/tmp.TuAMUcExAU/hello")
                .unwrap()
                .color(Color::GREEN),
        )
        .execute();
    thread::sleep(Duration::from_secs(10));
    println!("done sleeping");
    handle.kill();
    handle.join().unwrap();
}

Do you have an example of a program that isn't working as intended?


feat(dswx-s1): dedupe post-catalog query

Refs #883
Purpose

improve dedupe to avoid redundant job submissions

Proposed Changes

[CHANGE] improve dedupe to avoid redundant job submissions.

Issues

issue-883

Testing

tested locally

Turn on the rtc timer for 3 hours -> triggered 31 DSWx-S1 sciflo jobs  (no deduped jobs)


Consider superset:ui as (blocking) version of superset:up and superset:down

Migrated from GitLab: https://gitlab.com/meltano/files-superset/-/issues/5
Originally created by @aaronsteers on 2022-01-27 19:27:25

@pnadolny13 - In the meltano project, we considered a generic ui command for any utility that has a web UI. As we discussed it, that would be a blocking command, which when killed would also kill the UI.
I see here in this package we have up and down as commands. What do you think about feasibility and practicality of having ui as a command - either in place of or in addition to the up and down commands?
Linked issues:

https://gitlab.com/meltano/meltano/-/issues/2606+
https://gitlab.com/meltano/meltano/-/issues/2944+

View 5 previous comments from the original issue on GitLab


[WIP] Added protocol CodingKeyRepresentable

[WIP]

The current Codable system has an issue that only String and Int can be used as keys in keyed containers.
This has been discussed on various topics on the Swift Evolution forums <TODO - find references>. I believe that it has been mentioned by Itai Ferber that it was an early oversight that types that are RawRepresentable as String or Int could not be used as keys <TODO - find reference>.
It is unfortunately too late to fix this now. For one it is a behavior breaking change - and furthermore the change is tied to the Swift stdlib, so the behavior would basically differ between different consumers of the code (for instance different behaviors on different iOS versions).
I had another take at this issue: https://github.com/apple/swift/pull/26257
The idea there was to be able to express an opt-in to the new (fixed?) behavior directly in the JSONEncoder and JSONDecoder types by venting a new encoding/decoding 'strategy' configuration.
I have since changed my personal opinion about this and I believe that the problem should not just be fixed for specific Encoder/Decoder pairs, but rather for all.
This PR is an attempt to fix the situation by adding a new protocol: CodingKeyRepresentable. By adding conformance to the type of a key, you will be opting in to having dictionaries with keys of this type to encode as dictionaries instead of arrays of key/value pairs.
The opt-in can only happen for a version of swift where the protocol is available, so the user will be in full control of the situation. For instance I am currently using my own workaround, but once I only support iOS versions running a specific future Swift X version with this feature, I could skip my own workaround and rely on this behavior instead.
This draft PR is a placeholder so that I can start a Swift Evolution discussion. Perhaps even a pitch.

The new and old behaviors will need to be tested somehow.

I have tests locally - in the same file as you point out - but I was uncertain about the style.
Any help about how the tests should look is very welcome.
Here are my own tests:
struct GenericStringCodingKey: CodingKey {
  var stringValue: String
  var intValue: Int? { nil }

  init(stringValue: String) {
    self.stringValue = stringValue
  }

  init?(intValue: Int) {
    return nil
  }
}

enum NotCodingKeyConvertible: String, Codable {
  case a
  case b
}

enum CodingKeyConvertibleEnum: String, Codable {
  case a
  case b
}

extension CodingKeyConvertibleEnum: CodingKeyConvertible {
  init?(codingKey: CodingKey) {
    self.init(rawValue: codingKey.stringValue)
  }
  var codingKey: CodingKey { GenericStringCodingKey(stringValue: self.rawValue) }
}

// MARK: - Tests
class TestCodable : TestCodableSuper {
  lazy var dictValues: [Int: [NotCodingKeyConvertible: Bool]] = [
    #line : [.a: true, .b: false]
  ]

  func test_DictionaryAsArray_JSON() {
    for (testLine, dictionary) in dictValues {
        expectRoundTripEqualityThroughJSON(for: dictionary, lineNumber: testLine)
      let encoder = JSONEncoder()
      let decoder = JSONDecoder()
      do {
        let data = try encoder.encode(dictionary)
        let stringValue = String(decoding: data, as: UTF8.self)
        expectEqual("[\"a\",true,\"b\",false]", stringValue, "\(stringValue)")
        expectEqual(dictionary, try? decoder.decode([NotCodingKeyConvertible: Bool].self, from: data), "Expecting dictionary to encode as an array of pairs")
      } catch {
        fatalError("\(#file):\(lineNumber): Unable to encode [NotCodingKeyConvertible: Bool]: \(error)")
      }
    }
  }

  lazy var dictValues2: [Int: [CodingKeyConvertibleEnum: Bool]] = [
    #line : [.a: true, .b: false]
  ]

  func test_DictionaryAsDictionary_JSON() {
    for (testLine, dictionary) in dictValues2 {
      expectRoundTripEqualityThroughJSON(for: dictionary, lineNumber: testLine)
      let encoder = JSONEncoder()
      let decoder = JSONDecoder()
      do {
        let data = try encoder.encode(dictionary)
        let stringValue = String(decoding: data, as: UTF8.self)
        expectEqual("{\"a\":true,\"b\":false}", stringValue, "\(stringValue)")
        expectEqual(dictionary, try? decoder.decode([CodingKeyConvertibleEnum: Bool].self, from: data), "Expecting dictionary to encode as a JSON object")
      } catch {
        fatalError("\(#file):\(lineNumber): Unable to encode [CodingKeyConvertibleEnum: Bool]: \(error)")
      }
    }
  }
}

Please note - I have edited these files after they were last running - and I unfortunately can't build/test the standard library right now.
In case the proposal is accepted, the testing should of course be part of the final PR.

Any help about how the tests should look is very welcome.

You could create a new (or update an existing) helper function, to make it easier to test all the different combinations within a single test_Dictionary_JSON() method. For example, by adding an optional parameter to the expectRoundTripEqualityThroughJSON helper function.

If the tests are expecting a specific JSON output, you'll need to use either single-element dictionaries or the .sortedKeys formatting option.

The lazy var properties won't work for all the dictionaries needed. You can probably define the enum types locally within the test method. The existing UUIDCodingWrapper struct could be extended with a CodingKeyRepresentable conformance.

Hi @benrimmington ,
I finally got the tests to build and run after a long battle with disk space and compiler issues.
It still takes me a really long while to run the tests, as I don't know how to single out the tests that I am interested in. (I'm using utils/build-script --skip-build-benchmarks   --skip-ios --skip-watchos --skip-tvos --swift-darwin-supported-archs "$(uname -m)"   --sccache --release-debuginfo --swift-disable-dead-stripping --test from the documentation.)
I'll have a look at your suggestions ASAP. Thanks for your help! :-)

You can try the following, from within the swift directory:
utils/run-test \
  --build-dir=../build/Ninja-RelWithDebInfoAssert \
  --build=true \
  --subset=all \
  --target=macosx-x86_64 \
  --verbose \
  test/stdlib/CodableTests.swift

(The exact --build-dir and --target arguments may vary, depending on your machine and build options.)

\
  --build=true \
  --subset=all \
  --target=macosx-x86_64 \
  --verbose \
  test/stdlib/CodableTests.swift

Thanks - that improved my quality of life quite significantly! :-)
I just merged main into the PR branch and added tests. There are just a few of your comments I'm not quite sure about:
You mention 'all the different combinations'. Isn't this just: A dictionary keyed by a non-conforming type and a dictionary keyed by a conforming type?
I'm not quite certain what you are suggesting that the extra parameter to expectRoundTripEqualityThroughJSON should do.
Regarding the encoded output and sorting: Of course, thanks! I'm now just encoding a single value - that is just as well for testing purposes.
In the last comment you mention the 'all dictionaries needed'. Do you suggest that I create a dictionary keyed by each of the types that are already tested in the file for completeness?

One other question: When adding the 'future availability' flag to CodingKeyRepresentable:
@available(macOS 9999, iOS 9999, watchOS 9999, tvOS 9999, *)

Then I get a compiler error at the usage point - even though it's in the same file.
Do I need to do something special to let the compiler know that I'm basically running this future version of macOS?
Sincerely,
/morten

I forgot to mention that for utils/run-test you can also use --build=skip when you're only making changes to the tests themselves. In my experience, committing a small change to a test file can somehow touch the entire working tree, so that more of the project is rebuilt unnecessarily.

You mention 'all the different combinations'.

I was thinking of:

enums with different raw-value types (String, Int, other).
enums with different conformances (none, default, custom).
structs such as UUID and UUIDCodingWrapper.
standard and custom CodingKey types.

(Some of these will vary, depending on what is actually proposed.)

I'm not quite certain what you are suggesting that the extra parameter to expectRoundTripEqualityThroughJSON should do.

It would be something like _ expectedJSON: String? = nil so that existing tests aren't affected. When the parameter isn't nil, the helper function would add the .sortedKeys formatting option, and later compare the expectedJSON string and the encode() data.
func test_Dictionary_JSON() {
  enum X: String, Codable { case a, b }
  enum Y: String, Codable, CodingKeyRepresentable { case a, b }
  enum Z: String, Codable, CodingKeyRepresentable {
    case a, b
    init?(codingKey: CodingKey) {...}
    var codingKey: CodingKey {...}
  }
  // ...

  expectRoundTripEqualityThroughJSON([X.a: true],             #"["a",true]"#,           lineNumber: #line)
  expectRoundTripEqualityThroughJSON([Y.a: true, Y.b: false], #"{"a":true,"b":false}"#, lineNumber: #line)
  expectRoundTripEqualityThroughJSON([Z.a: true, Z.b: false], #"{"α":true,"β":false}"#, lineNumber: #line)
  // ...
}

Do I need to do something special to let the compiler know that I'm basically running this future version of macOS?

You might need to add @available(...) or if #available(...) {...} wherever the new protocol is used (or the new behavior is expected).
(The existing test methods are ordered alphabetically.)

Thanks again, @benrimmington - your assistance is invaluable!
The .sortedKeys flag itself is only available for:
(macOS 10.13, iOS 11.0, watchOS 4.0, tvOS 11.0, *)
Can I add an if #available in the middle of func expectRoundTripEqualityThroughJSON?
I don't know if the tests could be run on a system not matching the requirements here - but if so, the tests could fail when I use multiple keys. I can of course just go with a single key per test...
I added all the availability tests for the changes to the stdlib/public/core/Codable.swift, but for some reason it appears that I don't need to add those to the tests. I am not quite certain why that is.
I included both the suggestions from Jordan Rose and the default implementations and generic initalizer that you suggested. This should of course be reflected in the proposal text, but I am uncertain if it's fine to change that after the review period. In my eyes the changes are not very controversial.

Still a few more tests to be added.

The documentation comment of Dictionary.encode(to:) is currently:
  /// If the dictionary uses `String` or `Int` keys, the contents are encoded
  /// in a keyed container. Otherwise, the contents are encoded as alternating
  /// key-value pairs in an unkeyed container.

When decoding, should it attempt to migrate data from the old format? For example:
extension Dictionary: Decodable where Key: Decodable, Value: Decodable {
  public init(from decoder: Decoder) throws {
    self.init()

    if Key.self == String.self {
      // ...
    } else if Key.self == Int.self {
      // ...
    } else if #available(macOS 9999, iOS 9999, watchOS 9999, tvOS 9999, *),
      let codingKeyRepresentableType = Key.self as? CodingKeyRepresentable.Type,
      let container = try? decoder.container(keyedBy: _DictionaryCodingKey.self)
    {
      // ...
    } else {
      // ...
    }
  }
}

(The original error will be lost by the try?, so there might be a better way.)

Can I add an if #available in the middle of func expectRoundTripEqualityThroughJSON?

Yes, and the [.sortedKeys] option is only needed when expectedJSON != nil, but it should be safe to use for all tests.

I added all the availability tests for the changes to the stdlib/public/core/Codable.swift, but for some reason it appears that I don't need to add those to the tests. I am not quite certain why that is.

It might have something to do with the UNSUPPORTED: back_deployment_runtime at the top of the file?
In case it's needed later, you can add the availability to the entire test method (along with a MARK comment):
    // MARK: - Dictionary
    @available(macOS 9999, iOS 9999, watchOS 9999, tvOS 9999, *)
    func test_Dictionary_JSON() {
        //...
    }

if #available(macOS 9999, iOS 9999, watchOS 9999, tvOS 9999, *) {
    tests["test_Dictionary_JSON"] = TestCodable.test_Dictionary_JSON
}

Thanks again for another round of great feedback, @benrimmington !
I'm a bit torn about adding code for 'backwards compatibility' decoding. I think that the changes in the proposal gives the end user full control over when/if they are able to adopt the behavior. And I suspect that many (at least myself) are already using other workarounds. When I build something where this feature is supported on all supported platforms, I'll adopt the new protocol and remove my workarounds.
The 'cost' of adding the backwards compatibility code is that it 'muddies the waters' about what's going on when decoding a bit. I think that it's easier to explain the behavior without the backwards compatibility.
That said, it is a small thing to add, and it may help some users in some use cases.
What do you think?

I marked this PR as ready for review now that SE-0320 was accepted (https://forums.swift.org/t/accepted-se-0320-coding-of-non-string-int-keyed-dictionary-into-a-keyedcontainer/52057).

@swift-ci Please smoke test

https://ci.swift.org/job/swift-PR-macos-smoke-test/31085/
Failed Tests (2):
  Swift(macosx-x86_64) :: api-digester/dump-module.swift
  Swift(macosx-x86_64) :: api-digester/stability-stdlib-abi-with-asserts.test

I think each new public API (of the protocol and extensions) will also need @available attributes. (apple/swift#38824)

@swift-ci Please smoke test

https://ci.swift.org/job/swift-PR-macos-smoke-test/31097/
Failed Tests (1):
  Swift(macosx-x86_64) :: api-digester/dump-module.swift

The test expects the following additions in the test/api-digester/Outputs/cake-abi.json file:
         {
           "kind": "Conformance",
           "name": "Decodable",
           "printedName": "Decodable",
           "usr": "s:Se"
         },
+        {
+          "kind": "Conformance",
+          "name": "CodingKeyRepresentable",
+          "printedName": "CodingKeyRepresentable",
+          "usr": "s:s22CodingKeyRepresentableP",
+          "isABIPlaceholder": true
+        },
         {
           "kind": "Conformance",
           "name": "CustomReflectable",
           "printedName": "CustomReflectable",
           "usr": "s:s17CustomReflectableP"
         },

@swift-ci Please smoke test

https://ci.swift.org/job/swift-PR-macos-smoke-test/31102/
Failed Tests (1):
  Swift(macosx-x86_64) :: api-digester/dump-module.swift

I think the same additions are also needed in the test/api-digester/Outputs/cake.json file:
         {
           "kind": "Conformance",
           "name": "Decodable",
           "printedName": "Decodable",
           "usr": "s:Se"
         },
+        {
+          "kind": "Conformance",
+          "name": "CodingKeyRepresentable",
+          "printedName": "CodingKeyRepresentable",
+          "usr": "s:s22CodingKeyRepresentableP",
+          "isABIPlaceholder": true
+        },
         {
           "kind": "Conformance",
           "name": "CustomReflectable",
           "printedName": "CustomReflectable",
           "usr": "s:s17CustomReflectableP"
         },

PS: I've hidden all the resolved comments, to make it easier for future reviewers.

@swift-ci Please smoke test

https://ci.swift.org/job/swift-PR-macos-smoke-test/31105/
Failed Tests (1):
  Swift(macosx-x86_64) :: api-digester/dump-module.swift

Xcode (or another editor) has added a newline at the end of each JSON file, so the test is still failing.

Thanks, that was my vim configuration that added those. They are now removed.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux platform

Is this ready for merging, or is there anything else I can do? 😊

Is this ready for merging, or is there anything else I can do? 😊

@mortenbekditlevsen You could update the comment at the top of this page, with a link to the SE-0320 proposal.
I don't know who the "code owner" is, but I've requested reviews from:

@amartini51 (documentation)
@lorentey (standard librarian)
@tbkka (performance re: #31278)

Apologies for bumping this: is there anything else I can do for now? I am not familiar with the usual process after a proposal has been accepted. @lorentey @tbkka
Out of curiosity: I have not seen any plans for the next Swift version, but I assume that it will be 5.6. Are you familiar with any timeline for the next release?

@swift-ci Please smoke test

Thank you @benrimmington

@swift-ci smoke test

Yaaaaaay! Thank you so much to everyone who helped! 😊🥰🎉


fix: updating logs behavior

Hi @marcopiraccini @mcollina
this loom explain the behavior of the logs
https://www.loom.com/share/9b3e3d26a2df40c18df1f271481319ce


Optimized parallel prolongation operator for conforming meshes [prolongation-opt]

This optimization is used when the matrix-free version of FormLinearSystem is used, i.e. the one defined by the Operator class.

Nice work, thanks @v-dobrev!
@jakubcerveny, any objections to merging this?


always get error: module 'fluttertoast' not found（version: 8.1.3）

s.pod_target_xcconfig = { 'DEFINES_MODULE' => 'YES', 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'i386, arm64' }
Hi brother, Why do you need to exclude arm64 here? Will this cause the CPU running on the Apple M series to fail to work properly?

Same erro here on ios build

same issue when running iOS build on M1 Mac

any update ?


Creation of Minimalistic UI Client-v2

Modification of the front end apparence of the LinkDisplay and ChatLink Components. Before Continuing with the text messaging section would like to have this part approved first.

Hi Mukesh, apologies for overlooking the guidelines; I inadvertently placed the code in the client-v2 folder.


Contact volunteers signed up through web form

Contact each person that signed up to volunteer through the PyDX.org volunteer interest form.
Send a personal note regarding how to select shifts within the volunteer app.

Created<EMAIL_ADDRESS>to source emails. Reply-to set to<EMAIL_ADDRESS>All webform volunteered emailed. Two bounced.


FOV orthogonal views

FOV lower bound currently is 10. Could FOV lower bound be extended to 0 or 1 to support orthogonal views?

We have not supported orthogonal views as they complicate the math too much. They are especially a problem for skyboxes, as a skybox is meaningless to an orthographic camera. What is your use case?

Working on a multi vertical model viewer portal. One vertical is art. My personal mathematical art benefits greatly from close to orthogonal views with minimal FOV distortion. Currently use SketchFab, their lower bound is 1 and does great. Two examples of my work (viewer dev and math art). Both with FOV at 10. Select animation tab.

https://virtualexhibits-qa.azurewebsites.net/viewer/artwork/6a3d3a9b-512e-4096-8e50-aab8769acf15
https://virtualexhibits-qa.azurewebsites.net/viewer/artwork/c9812c0e-e3c4-4b20-9978-4bdcdc3410de

Any lowering to even 1 or 2 degrees would be very beneficial. I understand the challenge with truely orthogonal at 0 :)

You can set the min-field-of-view attribute, just don't set it to zero :). 1 degree should be no problem.

Awesome!

Would that allow me to see an object at a distance with FOV = 1?
I tried the min-field-of-view = 1 result -> https://virtualexhibits-qa.azurewebsites.net/viewer/artwork/6a3d3a9b-512e-4096-8e50-aab8769acf15

Please read through the rest of the attributes. You'll want to increase max-orbit radius so you can set a sufficiently large radius.

:)
Closing out the issue.
Thanks again.


Use man content for `help ' and ' --help'

Call 'go generate ./commands' to generate code from .ronn files which the cobra command can then use. Added to the build scripts but needs to be done manually at least once to test it outside that.
I've done the minimum re-formatting for now. The man format is pretty damn ugly on the command line and I'd like to do better but didn't want to spend time on that until the principle was approved. For now it just fixes the backtick issue, other things we could do:

Strip off the 2-line headers
Strip 'SYNOPSIS' and pull out the command summary as the first line
Strip '##' section markers generally
Use an abbreviated form for command --help (just contents of SYNOPSIS, DESCRIPTION and OPTIONS) and only print the full text for help command. Cobra splits this as Usage/Help, currently it's the same for both.

If you think this is a good idea I can hack on it some more.

Oops, 'go generate' is go 1.4+ so the 1.3 tests failed. We're dropping those though I hear :)

I really dig this idea :+1: It's like #568, but takes advantage of go's code generation (which I've been meaning to check out since it was announced).
Also, to answer your final reply on that thread:

were you aware that the default behaviour in Windows for something like git checkout --help is that it launches the browser & displays the HTML version of the man page?

Nope, that sounds awesome. Then the man page references at the bottom would actually link to each other :metal:

I really dig this idea :+1: It's like #568

Gah, I was looking for that yesterday but couldn't find it, I must have been looking at the issues. I prefer the map approach & general help/usage functions too since it means it automatically works for new commands if you provide a man page, without having any compile errors.
About the HTML on Windows; that's basically the other option; we could instead have 2 different behaviours for Linux/Mac and Windows, the former calling 'man git-lfs-' and the latter opening HTML which we have to deploy somewhere. My main problem with that approach is that even though it's nice in a pre-packaged release, it's not very usable in source builds, because the man/HTML might not be present (or at the least the paths would be different)
I'm tempted just to go with this for now (with suitable reformatting) & consider extending things later so that when built with the release flags the man/HTML route is used instead.

Already looking better, just want to tackle the links next:
steve@Stevens-MacBook-Pro ~/p/G/s/g/g/git-lfs> git lfs help push

git lfs push [options] <remote> [<ref>...]

git lfs push <remote> [<ref>...]

git lfs push --object-id <remote> [<oid>...]

Upload Git LFS files to the configured endpoint for the current Git remote.  By
default, it filters out objects that are already referenced by the local clone
of the remote.

Options:

* --dry-run:
    Print the files that would be pushed, without actually pushing them.

* --all:
    This pushes all objects to the remote that are referenced by any commit
    reachable from the refs provided as arguments. If no refs are provided, then
    all refs are pushed.

* --object-id:
    This pushes only the object OIDs listed at the end of the command, separated
    by spaces.

* --stdin:
    Read the remote and branch on stdin. This is used in conjunction with the
    pre-push hook and must be in the format used by the pre-push hook:
    <local-ref> <local-sha1> <remote-ref> <remote-sha1>. If --stdin is used
    the command line arguments are ignored.  NOTE: This is deprecated in favor
    of the pre-push command.

I'm tempted just to go with this for now (with suitable reformatting) & consider extending things later so that when built with the release flags the man/HTML route is used instead.

Baby steps. :+1:

Already looking better, just want to tackle the links next

That looks much better than what I saw. The man page headers were annoying. I like the more compact format.

OK I think this is ready to be merged now. I've made the links look nicer:
Options:

* -I <paths> --include=<paths>:
  Specify lfs.fetchinclude just for this invocation; see "Include and exclude"

* -X <paths> --exclude=<paths>:
  Specify lfs.fetchexclude just for this invocation; see "Include and exclude"

* --recent:
  Download objects referenced by recent branches & commits in addition to those
  that would otherwise be downloaded. See "Recent changes"

* --all:
  Download all objects referenced by any commit that is reachable; this is
  primarily for backup / migration purposes. Cannot be combined with --recent or
  --include/--exclude. Ignores any globally configured include and exclude paths
  to ensure that all objects are downloaded.

Include and exclude
-------------------

It's not 100% foolproof because it only processes the man pages line-wise and not with a full lexer (links split across lines wouldn't work for example) but I think it does the job much better for now.

It's not 100% foolproof because it only processes the man pages line-wise and not with a full lexer (links split across lines wouldn't work for example) but I think it does the job much better for now.

I think any edge cases for the parser should be tested. I'm not sure how that would work yet though.


plot library

There are a few different types of plots that can be made using this library, so an easy to use format might be nice. For instance, plotting the wildtype score across all residues, or plot something like N-effective (a separate issue to be raised). I also think it would be cool to overlay that over a seqlogo, but maybe that would be too crazy!

We now have a plot library! (1e104ce


fix(complete): avoid combine abbr hlgroup on space fill

Problem: the fill space should not use combined attr.
Solution: use original attr on fill space
cc @zeertzjq

thanks!


SND-4566: Letter "g" cutoff in search hits

SND-4566: Letter "g" cutoff in search hits
Issue:
- While applying ARTTextStyle to Label, it internally add the attributes
to label such as NSParagraphStyleAttributeName. And uses ARTTextStyle.lineHeight
for minimumLineHeight and maximumLineHeight properties of this attribute.
- If ARTTextStyle.lineHeight is larger than font.lineHeight, label's bottom gets truncated.
Cause:
- While calculating height, If numberOfLines is greater than 0 then, font.lineHeight
is being used for height calculation. But actually in UI, ARTTextStyle.lineHeight is being rendered.
Fix:
- So to fix this issue, added line height to LabelLayout.
- Added lineHeight parameter to LabelLayout's init(...) method and used it for height calculation
- Please see the discussion in RB- https://rb.corp.linkedin.com/r/1214302/#comment3598733.

What does your subclass look like? Instead of just making this public, can/should we add support for line height to LabelLayout?

As per @nicksnyder suggestion,  added lineHeight parameter to LabelLayout's init(...) method and used it for height calculation

@nicksnyder: Could you please merge this pull request?

Was waiting for build to pass.


Fix metadata links

It could be that I'm not understanding what is being done here, but inverting the value and the link I get clickable, linked URLs. I read this as: if it's a link, create a URL if you can; the way it's written it looks: if it's a link, let it be; otherwise create a URL.
In my specific case I want the links - like the within - to be clickable.

Careful, the value is already an HTML link, properly constructed using the anchor text provided by the user, while the method call is looking to convert URLs in text to clickable links.  In short, the change will break things.

Ok - then my manifest could be broken. I have a within value with the URL of a search that generated the results (IE: 'http://search.frick.org/search/id"). When that value is displayed in the metadata panel, without this change, is displayed as plain text. With this fix - since it's in links - it will be clickable.
I was under the impression that the content of the within tag was supposed to be a URL - which made sense. What value should I use to have the within link clickable in the metadata view? Should it be some HTML  element?

Can you post a link to a test manifest?

The manifest looks something along the lines of this: https://gist.github.com/Wedjaa/164b287c82d874522943
The IIIF specification says that within is supposed to be a URI - and in the example it shows: "within":"http://www.example.org/collections/books/" - this is somewhat consistent with the code I saw in Mirador: _this.getMetadataLinks will simply take within and keep it as a string.
I think that the proper solution would be to treat within like related, even if the specs are not as specific, and allow using a label in it, by using stringifyRelated.
Does it make sense?

Yep, within should have either a URL or a list of URLs as its value, not
HTML.  HTML is allowed in description, attribution and in the value fields
of metadata pairs, but that's it.
Rob
--
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305

Yep - makes sense - will move the link to the related field, where it belongs!


Add org parameter to form list request

What problem does the pull request solve?
Adds the user's organisation to the forms request on the homepage. Combined with the corresponding API PR by Tris this will result in the user only seeing forms from their organisation.
I've edited the DB seed script to include the user's organisation_slug, but this won't work for existing local users, you'll have to update or destroy your existing user manually. I can add something to automate this if people think it's necessary.
Checklist

[x] I've used the pull request template
[n/a] I've linked this PR to the relevant issue (if mission work)
[x] I've written unit tests for these changes (if code change)
[n/a] I've updated the documentation in (If any documentation requires updating)

Security lint is failing because activerecord has a vulnerability - will be resolved by bumping to <IP_ADDRESS>


Error within commit textbox

Sometimes this happens, I don't really know why, but it happens when I use json files (which by the way are presenting very weird errors even if the file is perfectly fine and the syntax is also correct).

Generated by some outdated extension.
https://github.com/Togusa09/vscode-tmlanguage/issues/14

Confirmed. Removing the Textmate Language extension solves the problems.


console transport should accept option to send all output to stdout

I understand the decision to send error logs to stderr, but in some cases I would prefer all console output going to stdout. Seems another config variable could easily solve this problem.
Would a PR be accepted for this ?

@kylezeeuwen absolutely. So long as it is approached as #619, which this is a duplicate of. i.e. if you want to log everything to stdout just pass the process.stdout as the stream option.


bug: changed persisting null to alpine store to empty array.

We also have this issue...

We also have this issue...

Clear your view cache! Ours was because we had published all the views.

After a couple hours of debugging we've found the issue. For some reason the collapsedGroups value was saved in localstorage as null...That's why it was crashing.

Yeah - ours is because we had published the views in our app so the cache was nackered!


Updated GeoRSS Events sensor to take configurable location

Description:
I've added some config entries to the GeoRSS sensor so that a location other than that in the homeassistant component can be used.
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#6703
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: geo_rss_events
    name: USGS All Earthquakes
    latitude: 19.838103
    longitude: -155.688949
    radius: 1000
    url: https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_day.atom
    categories:
      - 'Past Hour'
      - 'Past Day'

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

@Solije Can I ask what the use-case is for selecting different coordinates than the ones where your HA instance is located?

The major ones I can think of are if you want some form of tracking of events which may be relevant to family/friends (Get an alert when an earthquake happens where, say, your elderly parents live)
Other than that, maybe you have another property (cabin out in the woods) and you'd like to track events around that.


vendor: Update to hashicorp/memberlist v1.0.3

Motivation is to update to github.com/miekg/dns v1.0.14, relating to https://github.com/prometheus/alertmanager/issues/1734.
I ran:
GO111MODULE=on go get<EMAIL_ADDRESS>GO111MODULE=on go mod vendor

@simonpasquier Is that the right process?
//CC @knweiss

Had to run GO111MODULE=on go mod tidy as well. Should be good to go now.

LGTM.
The canonical documentation for dependency management is in the Prometheus repository. I've sent https://github.com/prometheus/alertmanager/pull/1745...


Convert non-persistent JMS tests to the test infra

this reworks several tests relying on a non-persistent broker to use the equivalent service in the test-infra
moves some of the legacy code to test-infra
minor test cleanups (mostly logs)
avoid sharing resources as a pre-work for future parallelization

Note: there's still a lot more to be done here, but given the number of
tests, let's do it in small steps.

Checkstyle failure is not on this code, so merging.


IPv4 Forwarding not active on newly created local clusters with RKE

*hat kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Install Rancher 2.5.5 on bare metal or virtual machine.
Create a new custom node on the local machine with default options plus enabling etcd, controlplane and worker.
Issuing docker command and wait until provisioning of the new clusternode is done.
Check IP-Forwarding status on new cluster shell by "sysctl net.ipv4.ip_forward"
Result:
0 = ipv4.ip_forward is not active
Expected:
Either ipv4_ip_forwarding set to 1 by default or an instruction how to archive this.
Other details that may be helpful:
The forwarding cannot be activated in the shell as the root-filesystem is read-only.
Trying to run a Wireguard workload on this node is not possible, because IP4 forwarding is mandatory.
Environment information
Version: Rancher 2.5.5.
Installation option: single install
Cluster information

Cluster type:  Custom
Machine type: VM
Provider: RKE
Kubernetes version: v1.19.6
Docker version: 19.03.14

I'm having the same issue and it is affecting my ability to run WireGuard in a Rancher pod.  If I execute shell for the running pod and type: "sysctl -w net.ipv4.ip_forward=1" the connection instantly works, however, each time the pod is restarted the command needs to be run in the shell to get it to work.  Editing the .yaml file does not work as the changes to not persist.

I'm having the same issue and it is affecting my ability to run WireGuard in a Rancher pod. If I execute shell for the running pod and type: "sysctl -w net.ipv4.ip_forward=1" the connection instantly works, however, each time the pod is restarted the command needs to be run in the shell to get it to work. Editing the .yaml file does not work as the changes to not persist.

Hey, have you found any solution for this?

The issue still persists.
The idea with the "Init-Container" is great, but I still would request a streamliend fix for this. Its quite essential.


[REQUEST] How to do 3D Parallelism for HuggingFace Models?

Overview
Does DeepSpeed leverage the 3D parallelism (i.e. data parallelism + pipeline parallelism + tensor parallelism) for huggingface models (e.g., GPT-J, LLaMA) fine-tuning?
May I ask anybody know how to simply implement this using DeepSpeed? Thanks!

make them pipeline, last layer's output is next one's input

make them pipeline, last layer's output is next one's input

Thanks for your reply, however, this method is pipline-only parallelism, not 3D :(

make them pipeline, last layer's output is next one's input

Thanks for your reply, however, this method is pipline-only parallelism, not 3D :(

Yes, I have the same doubt
https://github.com/microsoft/DeepSpeed/issues/3888


SYS-917 Added user_owned property to Location endpoint description.

Most delightful. Need to have note in the Changelog, too.


listing-importer.ts creates two properties for each one listing (they should be 1:1)

How to reproduce: run any of our listing importer scripts, and check select count(*) from property; before and after.

Summarizing what I know about this before heading out:

listing-importer.ts uploads a new property once when it calls uploadProperty, and another property is created when it calls uploadListing because the backend ListingsService.create creates a new property from the passed-in ListingDto (link).
Okay great, so we can just remove the call to uploadProperty, right? Nope: the PropertyCreateDto created from the ListingDto in ListingsService.create doesn't include any of the fields that the original input listing.property had (e.g. "region", "phone_number", etc.). This is possibly because the PropertyCreateDto doesn't include any fields other than units and buildingAddress (link)?
So how does one upload a property and upload a listing, without creating two properties? One idea I'm trying now: upload the listing, and then update the created property after that. The issue I'm running into there: the Listing returned from uploadListing doesn't include the property (I'd wanted to grab the id from listing.property.id). So do I do something complicated like "search for the property that corresponds to this listing, retrieve it, and update it to include the fields the input property has"?

I haven't digested everything in your note, but you could look at the seeder script, which does do something like what you're suggesting above.

The fields that are impacted by this:

listing.property.phone_number (added by us; not present in Exygy's code)
listing.property.region (added by us; not present in Exygy's code)
listing.property.neighborhood (added by Exygy; present in their code too)

So one way to fix this (which is in line with Exygy's plans to have Listing eventually absorb Property's fields) would be to just migrate our fields (phone_number and region) to be fields in Listing instead of in Property. That will still leave us unable to upload a neighborhood until Exygy does actually make that field live within Listing instead of Property, but that seems worth it to save us effort that will eventually be obsolete.


Crashed: com.apple.main-thread  EXC_BAD_INSTRUCTION 0x00000000feedfacf

[REQUIRED] Please fill in the following fields:

Unity editor version: 2021.3.30f1
Firebase Unity SDK version: 10.6.0
Source you installed the SDK: unitypackage
Problematic Firebase Component:Firebase CallBack
Other Firebase Components in use: _____ (Auth, Database, etc.)
Additional SDKs you are using: _____ (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Mac
Platform you are targeting: iOS
Scripting Runtime:  IL2CPP
Pre-built SDK from the website](https://firebase.google.com/download/unity)

[REQUIRED] Please describe the issue here:
iphone6s, iphone6, ipad air  Os Version: 12.5.7
Crashed: com.apple.main-thread
0  UnityFramework                 0x102000000 selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
1  UnityFramework                 0xfaabb4 firebase::callback::CallbackString::Run() + 196
2  UnityFramework                 0xfcaeb4 firebase::callback::CallbackEntry::Execute() + 144
3  UnityFramework                 0xfc8694 firebase::callback::CallbackDispatcher::DispatchCallbacks() + 116
4  UnityFramework                 0xfc85dc firebase::callback::PollCallbacks() + 68
5  UnityFramework                 0x1085318 Firebase_App_CSharp_PollCallbacks + 12
6  UnityFramework                 0x12fecd8 selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
7  UnityFramework                 0x1312458 selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
8  UnityFramework                 0xf58a48 il2cpp::vm::Runtime::InvokeWithThrow(MethodInfo const*, void*, void**) + 580 (Runtime.cpp:580)
9  UnityFramework                 0xf588a8 il2cpp::vm::Runtime::Invoke(MethodInfo const*, void*, void**, Il2CppException**) + 574 (Runtime.cpp:574)
10 UnityFramework                 0x569ab4 scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 292 (ScriptingApi_Il2Cpp.cpp:292)
11 UnityFramework                 0x57529c ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 298 (ScriptingInvocation.cpp:298)
12 UnityFramework                 0x583a68 MonoBehaviour::CallUpdateMethod(int) + 543 (MonoBehaviour.cpp:543)
13 UnityFramework                 0x3f227c void BaseBehaviourManager::CommonUpdate() + 178 (Behaviour.cpp:178)
14 UnityFramework                 0x4974c8 ExecutePlayerLoop(NativePlayerLoopSystem*) + 383 (PlayerLoop.cpp:383)
15 UnityFramework                 0x497508 ExecutePlayerLoop(NativePlayerLoopSystem*) + 407 (PlayerLoop.cpp:407)
16 UnityFramework                 0x497764 PlayerLoop() + 514 (PlayerLoop.cpp:514)
17 UnityFramework                 0x9dda58 UnityPlayerLoopImpl(bool) + 342 (LibEntryPoint.mm:342)
18 UnityFramework                 0x17ee4 -[UnityAppController(Rendering) repaint] + 238 (UnityAppController+Rendering.mm:238)
19 UnityFramework                 0x17e74 -[UnityAppController(Rendering) repaintDisplayLink] + 72 (UnityAppController+Rendering.mm:72)
20 QuartzCore                     0x11ff0 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 636
21 IOKit                          0x54b0 IODispatchCalloutFromCFMessage + 488
22 CoreFoundation                 0x84990 __CFMachPortPerform + 188
23 CoreFoundation                 0xab594 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 56
24 CoreFoundation                 0xaace0 __CFRunLoopDoSource1 + 440
25 CoreFoundation                 0xa5b04 __CFRunLoopRun + 2096
26 CoreFoundation                 0xa4fb4 CFRunLoopRunSpecific + 436
27 GraphicsServices               0xa79c GSEventRunModal + 104
28 UIKitCore                      0x8bcc38 UIApplicationMain + 212
29 UnityFramework                 0x17a18 -[UnityFramework runUIApplicationMainWithArgc:argv:] + 96 (main.mm:96)
30 TRTBilBakalm                   0x412c main + 28 (main.mm:28)
31 libdyld.dylib                  0x18e0 start + 4
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

Hi @aslmtrt,
Does updating the SDK to its latest version (11.5.0 as of writing) make any difference? If not, could you share your Podfile along with the steps to reproduce the issue so we can identify what's causing this to happen?

Hi @paulinon Thank you for your repply.
I updated to the latest version but the problem still persists.

Hi @aslmtrt,
Could you provide a minimal, reproducible example of your implementation along with detailed steps to replicate the issue so we can identify what's causing this to happen?

We are experiencing the same crash after an update of Unity from 2021.3.12f -> 2021.3.28f
With this update we also updates Firebase from 9.0.0 -> 11.2.0
Unfortunately we have only been able to see this in Crashlytics for now and don't have a reproduction case. It's happening almost exclusively on iOS/iPadOS 12.
Crashed: com.apple.main-thread
0  UnityFramework                 0x102000000 selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
1  UnityFramework                 0x190b234 firebase::callback::CallbackString::Run() + 196
2  UnityFramework                 0x192bb7c firebase::callback::CallbackEntry::Execute() + 144
3  UnityFramework                 0x1928fd0 firebase::callback::CallbackDispatcher::DispatchCallbacks() + 116
4  UnityFramework                 0x1928f18 firebase::callback::PollCallbacks() + 68
5  UnityFramework                 0x19e8dd8 Firebase_App_CSharp_PollCallbacks + 12
6  UnityFramework                 0x1e7c2ac selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
7  UnityFramework                 0x1e94b2c selector_thread(void*) (.cold.1) + 656 (threadpool-ms-io.cpp:656)
8  UnityFramework                 0x18cbcdc il2cpp::vm::Runtime::InvokeWithThrow(MethodInfo const*, void*, void**) + 578 (Runtime.cpp:578)
9  UnityFramework                 0x18cbb3c il2cpp::vm::Runtime::Invoke(MethodInfo const*, void*, void**, Il2CppException**) + 572 (Runtime.cpp:572)
10 UnityFramework                 0xec8bd8 scripting_method_invoke(ScriptingMethodPtr, ScriptingObjectPtr, ScriptingArguments&, ScriptingExceptionPtr*, bool) + 292 (ScriptingApi_Il2Cpp.cpp:292)
11 UnityFramework                 0xed41ec ScriptingInvocation::Invoke(ScriptingExceptionPtr*, bool) + 298 (ScriptingInvocation.cpp:298)
12 UnityFramework                 0xee29b8 MonoBehaviour::CallUpdateMethod(int) + 543 (MonoBehaviour.cpp:543)
13 UnityFramework                 0xd53f48 void BaseBehaviourManager::CommonUpdate() + 178 (Behaviour.cpp:178)
14 UnityFramework                 0xdf6d30 ExecutePlayerLoop(NativePlayerLoopSystem*) + 383 (PlayerLoop.cpp:383)
15 UnityFramework                 0xdf6d70 ExecutePlayerLoop(NativePlayerLoopSystem*) + 407 (PlayerLoop.cpp:407)
16 UnityFramework                 0xdf6fcc PlayerLoop() + 514 (PlayerLoop.cpp:514)
17 UnityFramework                 0x1345788 UnityPlayerLoopImpl(bool) + 342 (LibEntryPoint.mm:342)
18 UnityFramework                 0x15bd0 -[UnityAppController(Rendering) repaint] + 238 (UnityAppController+Rendering.mm:238)
19 UnityFramework                 0x15b60 -[UnityAppController(Rendering) repaintDisplayLink] + 72 (UnityAppController+Rendering.mm:72)
20 QuartzCore                     0x11ff0 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 636
21 IOKit                          0x54b0 IODispatchCalloutFromCFMessage + 488
22 CoreFoundation                 0x84990 __CFMachPortPerform + 188
23 CoreFoundation                 0xab594 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION + 56
24 CoreFoundation                 0xaace0 __CFRunLoopDoSource1 + 440
25 CoreFoundation                 0xa5b04 __CFRunLoopRun + 2096
26 CoreFoundation                 0xa4fb4 CFRunLoopRunSpecific + 436
27 GraphicsServices               0xa79c GSEventRunModal + 104
28 UIKitCore                      0x8bcc38 UIApplicationMain + 212
29 UnityFramework                 0x15704 -[UnityFramework runUIApplicationMainWithArgc:argv:] + 96 (main.mm:96)
30 [GAME NAME]                        0x412c main + 28 (main.mm:28)
31 libdyld.dylib                  0x18e0 start + 4

Hi, I have the same crashes on iOS 12.5 devices on my last game update.
Tested with 11.4.0, 11.6.0 and the problems is the same.
Currently using Unity 2021.3.31f1 (LTS)
For information here is my PodFile:
source 'https://cdn.cocoapods.org/'

platform :ios, '12.0'

target 'UnityFramework' do
  pod 'Firebase/Analytics', '10.15.0'
  pod 'Firebase/Core', '10.15.0'
  pod 'Firebase/Messaging', '10.15.0'
  pod 'Firebase/RemoteConfig', '10.15.0'
  pod 'FirebaseInstallations'
  pod 'GoogleSignIn', '~> 6.0.2'
  pod 'GoogleUtilities', '~> 7.11.0'
end
target 'Unity-iPhone' do
end
use_frameworks! :linkage => :static

target 'NotificationServiceExtension' do
  pod 'Firebase/Messaging', '10.15.0'
  pod 'GoogleUtilities', '~> 7.11.0'
end

post_install do |installer|
# Get main project development team id
dev_team = ""
project = installer.aggregate_targets[0].user_project
project.targets.each do |target|
    target.build_configurations.each do |config|
        if dev_team.empty? and !config.build_settings['DEVELOPMENT_TEAM'].nil?
            dev_team = config.build_settings['DEVELOPMENT_TEAM']
        end
    end
end

# Fix bundle targets' 'Signing Certificate' to 'Sign to Run Locally'
installer.pods_project.targets.each do |target|
    if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
            target.build_configurations.each do |config |
                config.build_settings['DEVELOPMENT_TEAM'] = dev_team
            end
        end
    end

# Disable bitcode compilation
    installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
            config.build_settings['ENABLE_BITCODE'] = 'NO'
        end
    end
end

I'll try to test with xCode 14.3 to see if the problem persists.

Here is a small repro project, just add your packages as listed in the Packages/manifest.json otherwise the archive is too big to upload here.
I also removed the google-service... file.
As I tested:
1 - Open the project.
2 - make sure to target iOS platform.
3 - build and run targeting xCode 15.
4 - run on an iPhone 6 device (iOS 12.5.7)
5 - on the launched app, click on the button START.
6 - see the crash happening.
FirebaseCrashIOS12.zip

More informations about my config to build the repro project on my previous post:
Unity: 2021.3.31f1
MacOS: 14.0
Xcode: 15.0.1
MacBook Pro M1 8Gb RAM / 256Gb SSD

Hi,
Just a follow up to prevent your bot to close the issue...
As your bot said it's been more than 5 weekdays now and I'm still waiting for a response.
I think we gives you all you need to find and fix the bug, this bug seems pretty simple to reproduce and I gives you a sample project to reproduce it as asked by @paulinon.
I'm still available to answer any question you could have.
Thanks.

We updated Firebase libraries.
We downgraded the Unity version.
We tried similar different steps, nothing changed.
We upgraded the Unity version again and got a new build.
In this build, we turned off analytics and firebase usage for OS 12.
(FirebaseAnalytics.LogEvent)
Crashes related to Analytics and Firebase continued, but the number of crashes decreased.
Crashes only occurred on iPhone 6 OS 12.
As far as I understand, the problem occurs when sending analytical events for iPhone OS 12.

I'm using Unity 2021.3.21f1, Firebase 10.7.0, xcode 15.1 and I'm getting the same crash on iPhone SE / iOS 13.
There seems to be no problem when using xcode 14.x version.
However, since I need to use xcode 15, this problem should be resolved.
Thanks

@a-maurice @cynthiajoan @sunmou99 @chkuang-g, anyone could take a look at this please ?

I had encountered a similar problem, but was able to resolve the issue with the responses on the following pages.
https://baba-s.hatenablog.com/entry/2023/11/27/091420

We were able to confirm with 100% certainty that building the app with Xcode 14 instead of Xcode 15 resolved this crash for us.

@baba-s Thanks, it seems to fix the issue.

Xcode 15.1 was fixed this issue. Check more information here:
https://developer.apple.com/documentation/xcode-release-notes/xcode-15_1-release-notes#Linking


x/tools/cmd/present: playground support leaks goroutines

To reproduce, start present, navigate to localhost:3999 in your browser, and open a presentation.  For each reload, a new playground socket handler gets spun up, each of which permanently leaks a goroutine.
Hitting present with a SIGQUIT yields lots of these:
goroutine 52 [chan receive, 6 minutes]:
golang.org/x/tools/playground/socket.func·002()
	$GOPATH/src/golang.org/x/tools/playground/socket/socket.go:125 +0x10b
created by golang.org/x/tools/playground/socket.socketHandler
	$GOPATH/src/golang.org/x/tools/playground/socket/socket.go:131 +0x2b0

Note that in socketHandler.go line 125 there's a range loop reading from a channel that never gets closed.
Noticed because I added net/http/pprof to present for a demo and saw the goroutines profile number steadily increasing.

As an aside, if vet had oracular powers, it could warn about such matters. There would probably be too many false positives, though. Plus oracle the lives in x/tools and somehow I don't see that changing soon.


Position of Popover is wrong, its fixed to top left

Reproduction demo
Codesandbox Demo
Steps to reproduce the problem

Click Red Field
Wrong position

What is the expected behavior?
That the popover renders to the right start of the ref element.
What went wrong?
Popover position is set to top 0px, left 0px
Any other comments?

Packages versions

Popper.js<EMAIL_ADDRESS>react-popper: 2.2.5

I have the same issue. My current workaround is to use<EMAIL_ADDRESS>

https://github.com/tailwindlabs/headlessui/issues/985


how to deal with multilingual assets

gen
de
en

won't fix ... this should do: http://marizmelo.com/2013/01/28/requirei18n.html


Additional attributes?

In the json template thus far, the POI attributes are title, address, web, poi_type, and scoop. Do people think other attributes could be useful? For example, I'm thinking about phone # and hours. These are likely available from each place's website, but it could save a few clicks.

@neuhausr Great idea, I think hours and phone number would be great additions!
If you add in the attributes to the places.geojson, you can also add in the update to the script.js file as well to ensure the pop-up displays the attributes (currently located between lines 48-62).
Let us know if you'd like us to tackle it when you submit the PR, too. :stuck_out_tongue:

We can do that.  For the other maps like this that I have created, I have stopped at URL, which is linked in the Title in the map popup.  I have figured that over the long term, it is hard to maintain hours, etc. for all of those datasources that I don't have control over.
The way that the script code is set up though, attributes that exist for that feature show up in the popup, and if they don't exist, it doesn't throw an error.  We could add options for hours and phone to display if they exist.
Personally, I am guessing that they will go to the Web page for more details anyway, but if others feel differently, I am open to it.

I totally get that, I was just thinking of a recent trip we took and some of the info we looked for. Menu/prices were other info which is often (but not always) easy to find on the website, and not all are easy to navigate on smartphone.
Maybe, rather than new attributes, it'd be just as easy to highlight certain key info under the scoop attribute, such as: "open late", "breakfast and lunch only", "no reservations", "always crowded", "cheap eats", " good but pricey"

Personally, I like seeing hours (esp. since some places aren't open some weekdays). In fact, I added them into the 2015 GIS/LIS conference map.
The way I see it, the conference is in October, and if things get outdated, they get outdated. Luckily it's all on GitHub, so anyone can put in a PR, or create their own app in the future. Just my 2 cents :moneybag:.
But, this is our collective map. So, @neuhausr, add in what you see fit, and @fawcett and I can review/duel it out when you put in the PR! :smile:

I will do no dueling...  At least not on this issue.  I say that if you think that it adds to the data, you should add an attribute for hours.  I might have actually done that for the PDX map, now that I think of it.  The trick is how to describe hours that vary by day.
We can add the logic to the template so that if there are values for hours, they show up, and if not, nor harm.
{
"type": "Feature",
"properties": {
"title": "Occidental Brewing",
"description": "Wed-Thur(4pm-8pm), Fri(3pm-8pm), Sat(12pm-8pm), Sun(12pm-6pm)",
"address": "6635 N Baltimore Ave, Portland, Oregon, 97203",
"web": "http://www.occidentalbrewing.com",
"marker-symbol": "beer",
"marker-color": "#23344c"
},
"geometry": {
"type": "Point",
"coordinates": [
-122.7610695362091,
45.58895111219635
]
}
}
From https://raw.githubusercontent.com/JasonSanford/foss4g-map/gh-pages/things.geojson

I like it! :+1:

Hey @neuhausr: just checking in on your progress, were you planning on adding any additional features to the POI's?

umm, little progress to report, sorry! been busy with other life. sounds like attribute-wise, it's probably good enough so I'll close this

No worries, feel free to reopen at any time! Thanks!


test: cover one time token sevrice

:white_check_mark: Build TheIdServer 1.0.0-export-import1-0070 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/a76c3ebbfb by @aguacongas)


flexbox styles

Description
Bootstrap upgrade to use flexbox feature to handle form and carddetails layout.
Overview of Changes
N/A
Type of Change

[ ] Other
Bootstrap upgrade

Test Details
Tested via LTSS
Additional Notes
N/A

You did it @dinakarmeda!
Thank you for signing the Anthem Opensource Software CLA.


Add a meta viewport to ensure proper rendering

Hi guys,
I think that the meta viewport should be added for a proper displaying on the mobile devices and correct work of media queries.

thanks! @yuyokk

My pleasure.
I believe that it has to be cherry-picked to gh-pages branch as well.
So if you want me to do that, just let me know.


Cannot see other peoples votes

Hi,
a want to start by saying thanks for the plugin. We use it very frequently for years and it is a great help, especially since the Rona hit.
I tried to make sure that this issue has not yet been reported. I apologize if I did a bad job at that.
This is something which is not a big deal, but kind of annoying. We always had this problem, so I am surprised nobody reported it.
When we are voting the cards of other people are not showing up face down. We constantly have to switch between work items to refresh the view and see if everybody has voted yet to reveal the cards.
I would be very happy to find a solution for that.

@FabBadDog  Thanks for reporting, i it will be fixed in the next release

Hi @AminTi,

I am confused. This is the repo for MS DevLabs Estimate, right? At least this is what we are using. Am I wrong here? I do not know anything about the "Estimation Poker" extension.
Please clarify
Thank you

Hi! @FabBadDog  your right this repo belong to MS DevLabs Estimate (Estimate)

Hi! @FabBadDog  It work as expected for me, can you please describe reproduction step.

Hi @FabBadDog yes we can do it you have time now ?

Not right now, but maybe in about 30 minutes?
Can you send your e-mail address? I will invite you to a teams meeting.
------ Originalnachricht ------
Von "AminTi" @.>
An "microsoft/azure-boards-estimate"
@.>
Cc "Fabio" @.>; "Mention" @.>
Datum 19.07.2022 15:32:50
Betreff Re: [microsoft/azure-boards-estimate] Cannot see other peoples
votes (Issue #155)

Hi @FabBadDog https://github.com/FabBadDog yes we can do it you have
time now ?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azure-boards-estimate/issues/155#issuecomment-1189059724,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMPQG2LTXNTL7TVOYLZWDTVU2VAFANCNFSM5ZIRAYZA.
You are receiving this because you were mentioned.Message ID:
@.***>

<EMAIL_ADDRESS>

Hi, It should be fixed I couldn't reproduce the bugs, if you  still facing the same issue let me know. We can schedule a Teams meeting.


Pull out initButtonSelects from core.js into includes/initButtonSelects.ts

Is your proposal related to a problem?
initButtonSelects should move from core.js to a new file client/src/includes/initButtonSelects.ts
Wagtail's JavaScript core.js is quite large and many items can be pulled out to shared utils or includes to help make the code more maintainable and supported with base unit tests.
Pulling some basic functions out lets us put these into TypeScript (type safety) but also document and unit test them better.
Describe the solution you'd like
The function initButtonSelects should be moved from
https://github.com/wagtail/wagtail/blob/aaea8710c21ba4d5368d3825781bc54e1869c561/client/src/entrypoints/admin/core.js#L607-L631
To a new file client/src/includes/initButtonSelects.ts (note: TypeScript ts not JavaScript js)
From there it can be imported and triggered the same way (see line 633) $(document).ready(initButtonSelects);.
Requirements

[ ] Move the function to the the new TypeScript file and set up correct types - https://www.typescriptlang.org/
[ ] Add a JSDOC description to the function
[ ] Add a basic set unit test (just one is fine) for this function in a new client/src/includes/messages.test.js file using Jest - look at client/src/includes/breadcrumbs.test.js for an example of mocking some HTML to then trigger some behaviour on that HTML
[ ] Ensure the util is imported in core.js correctly so that the select buttons correctly initialise (take a screenshot of a usage that is correctly functioning after the change for the PR)

Additional context

This has been created as part of the Outreachy program to help new contributors that are interested in the Stimulus project.

@Lovelyfin00 - if you want - feel free to claim this one as per Slack chat.

Awesome thanks😁😁
I'm on it

As per slack
You will have to search for the CSS class that gets used button-select
Which uses wagtail-new/wagtail/admin/templates/wagtailadmin/widgets/button_select.html
Which uses this python file wagtail-new/wagtail/admin/widgets/button_select.py
Which is used in these files

wagtail-new/wagtail/contrib/redirects/filters.py
wagtail-new/wagtail/admin/views/reports/workflows.py

so based on that, it looks like you could check the workflow UI and also the filtering (used in reporting pages I think)


Make room for testing of evaluation documents

Here is the first version with room for testing of evaluation docs.  They have been numbered on Google Drive.

@bsharpataz, this is what people can use to write their own tests, or at least it's the start of such a framework.  They can always ask me questions about any code they might need to copy and paste.


Broken behavior when dealing with libraries containing an @ symbol

Functional impact
Attempting to check for updates to something like SignalR results in breaking the library name
Minimal repro steps
Set your libman.json file as follows
{
  "defaultProvider": "unpkg",
  "libraries": [
    {
      "library": "<EMAIL_ADDRESS>      "files": [
        "dist/browser/signalr.js"
      ],
      "destination": "wwwroot/vendor/signalr"
    }
  ],
  "version": "1.0"
}

Then using the lightbulb quick action to try and check for updates to SignalR.
Expected result
It should determine there are no updates available
Actual result
You'll get the option to update to "Stable: 1.0.2"
Clicking to do so will replace the entire library name from "<EMAIL_ADDRESS>to "1.0.2".
Further technical details
I believe It's just parsing off of the first found @ symbol, when it should be using the last one.

This is working for me.  Feel free to reopen if you're still hitting it.


tools: rename max10 hash keys

bmc_root__hash to bmc_root_entry_hash
pr_root__hash to pr_root_entry_hash
sr_root__hash to sr_root_entry_hash

Coverage remained the same at 81.48% when pulling fe2643b22a095363a14431c3035220e731f81897 on aravuri/hash_entery into 2e2511a83bce2004d5e221e4bba65d9c464a33ef on master.


CSHARP-3314: Implemented Known Serializers

This PR is against Robert's csharp3320-optimizer branch, which I had been working off of. I rebased it on top of a refetch of linq3 followed by csharp3320-optimizer. Given that I've dealt with merge conflicts due to linq3 changes once already, it shouldn't be too hard to rebase on whichever branch is latest.
The test suite is green and these changes are ready for review. Looking forward to incorporating any and all feedback.

Note: The EG patch is currently failing due to CS0173. This has been fixed in master by CSHARP-3874 (commit SHA 9e2476), but I'm holding off on rebasing on master as that will require Robert to rebase linq3 and related branches on master as well. These changes do build and test cleanly locally.


Generic TSS

What
Making TSS generic - work for all transactions. Implementation of the doc: https://docs.google.com/document/d/1MJ3iyiTbASJp8hq1cTJO_aHDtP3Ko7kpMnKqzjYhITE/edit?tab=t.0
Why
We need to make TSS work for all types of transactions and not just the disbursement use case
Known limitations
N/A
Issue that this PR addresses
https://github.com/orgs/stellar/projects/58/views/2?filterQuery=&sliceBy[columnId]=Status&sliceBy[value]=In+progress&pane=issue&itemId=87419862&issue=stellar|wallet-backend|79
Checklist
PR Structure

[x] It is not possible to break this PR down into smaller PRs.
[x] This PR does not mix refactoring changes with feature changes.
[x] This PR's title starts with name of package that is most changed in the PR, or all if the changes are broad or impact many packages.

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] All updated queries have been tested (refer to this check if the data set returned by the updated query is expected to be same as the original one).

Release

[x] This is not a breaking change.
[x] This is ready to be tested in development.
[x] The new functionality is gated with a feature flag if this is not ready for production.

Should this work for transactions that need a specific signer(s)?
If so maybe we could use an option to submit an already signed tx and only build it instead of build + sign it?


Investigate slow-down in reverse-mode with nested loops in Bezier curves PR

There appears to be some slow-down when using reverse-mode with multiple nested loops. See bezier_curvefit.py in slang-torch PR#1.
Filing this in the main repository because its most likely an issue with recompute/checkpoint policy creating unnecessary intemediates.

No compiler changes needed. Fixed by updating user code to take advantage of recomputation.
See for more details: https://github.com/shader-slang/slang-torch/pull/6


[Feature] Move from cargo generate-rpm, cargo deb, and cargo wix to cargo bundle

Depends on https://github.com/burtonageo/cargo-bundle/issues/115.
Once this feature is resolved, move to using cargo bundle instead of the separate Cargo packages as to speed up the process of packaging per platform. Additionally, it supports generation of MacOS packages.

[ ] DEB and RPM migration
[ ] Windows migration
[ ] MacOS implementation

Potentially look into how cargo generate-rpm generates RPM's and move to implement the same functionality into cargo-bundle in a PR.


Added current dir to $LOAD_PATH, as in the original ruby koans.

Needed this to get going with ruby-1.9.2-p180.

require_relative 'edgecase'


Removes semicolons on commented lines?

I'm the standard-formatter for Atom (Atom/GitHub) in semi-standard mode, and it is removing semicolons in my commented lines when I actiavte the plugin. I voiced my concern in an issue in that repo, and was redirected here, so will you take a look at what I'm describing?

Hi @jsejcksn,
The formatter included as based off https://github.com/ricardofbarros/semistandard-format which (which is a fork of standard-format). Unfortunately its not perfect and not really being maintained.
However, you can now do semistandard --fix instead to use the eslint auto-fix function.. I've found it to be a lot more reliable.

@Flet I'm not sure what you mean by

you can now do semistandard --fix instead.

If you're talking about terminal commands, I don't use the terminal with Atom.


Add a "main" entry point function for use by SPM.

This PR adds a new symbol, __swiftPMEntryPoint(), that can be called by Swift Package Manager to trigger running tests. This function shares most of its implementation with XCTestScaffold, so that function's implementation has been factored out into a common function both call.
Note that this function is not available on Darwin because Apple's platforms invoke tests very differently from Linux/Windows/etc. (by relying on the XCTest framework that ships inside Xcode.)

@swift-ci please test

@swift-ci please test

@swift-ci please test


Failed jobs in queue manager

Bug Description
Description
I am getting a failed job in the queue manager on deleting an entry. The entry contains a Neo field with multiple blocks in it.
Other information
I reported the bug to the Neo plugin author and after analysing the files for my project setup he concluded that there is a conflict with the Cache Flag plugin.
Here is the log:
2023-04-14 12:50:58 [-][1][-][error][craft\queue\QueueLogBehavior::afterError]  [334] Deleting old Neo blocks (attempt: 1, pid: 2328) - Error (time: 0.007s): Invalid owner ID: 35277
2023-04-14 12:50:58 [-][1][-][error][yii\base\InvalidConfigException] yii\base\InvalidConfigException: Invalid owner ID: 35277 in /var/www/html/vendor/spicyweb/craft-neo/src/elements/Block.php:347
Stack trace:
#0 /var/www/html/vendor/craftcms/cms/src/helpers/ElementHelper.php(414): benf\neo\elements\Block->getOwner()
#1 /var/www/html/vendor/craftcms/cms/src/helpers/ElementHelper.php(452): craft\helpers\ElementHelper::rootElement(Object(benf\neo\elements\Block))
#2 /var/www/html/vendor/mmikkel/cache-flag/src/CacheFlag.php(226): craft\helpers\ElementHelper::isDraftOrRevision(Object(benf\neo\elements\Block))
#3 /var/www/html/vendor/mmikkel/cache-flag/src/CacheFlag.php(180): mmikkel\cacheflag\CacheFlag->_maybeInvalidateFlaggedCachesByElement(Object(benf\neo\elements\Block))
#4 [internal function]: mmikkel\cacheflag\CacheFlag->mmikkel\cacheflag\{closure}(Object(craft\events\DeleteElementEvent))
#5 /var/www/html/vendor/yiisoft/yii2/base/Event.php(312): call_user_func(Object(Closure), Object(craft\events\DeleteElementEvent))
#6 /var/www/html/vendor/yiisoft/yii2/base/Component.php(642): yii\base\Event::trigger('craft\\services\\...', 'beforeDeleteEle...', Object(craft\events\DeleteElementEvent))
#7 /var/www/html/vendor/craftcms/cms/src/services/Elements.php(1699): yii\base\Component->trigger('beforeDeleteEle...', Object(craft\events\DeleteElementEvent))
#8 /var/www/html/vendor/spicyweb/craft-neo/src/jobs/DeleteBlock.php(49): craft\services\Elements->deleteElement(Object(benf\neo\elements\Block), false)
#9 /var/www/html/vendor/yiisoft/yii2-queue/src/Queue.php(246): benf\neo\jobs\DeleteBlock->execute(Object(craft\queue\Queue))
#10 /var/www/html/vendor/yiisoft/yii2-queue/src/cli/Queue.php(147): yii\queue\Queue->handleMessage('334', 'O:25:"benf\\neo\\...', '300', 1)
#11 /var/www/html/vendor/craftcms/cms/src/queue/Queue.php(131): yii\queue\cli\Queue->handleMessage('334', 'O:25:"benf\\neo\\...', '300', 1)
#12 [internal function]: craft\queue\Queue->craft\queue\{closure}(Object(Closure))
#13 /var/www/html/vendor/yiisoft/yii2-queue/src/cli/Queue.php(117): call_user_func(Object(Closure), Object(Closure))
#14 /var/www/html/vendor/craftcms/cms/src/queue/Queue.php(140): yii\queue\cli\Queue->runWorker(Object(Closure))
#15 /var/www/html/vendor/craftcms/cms/src/controllers/QueueController.php(84): craft\queue\Queue->run()
#16 [internal function]: craft\controllers\QueueController->actionRun()
#17 /var/www/html/vendor/yiisoft/yii2/base/InlineAction.php(57): call_user_func_array(Array, Array)
#18 /var/www/html/vendor/yiisoft/yii2/base/Controller.php(178): yii\base\InlineAction->runWithParams(Array)
#19 /var/www/html/vendor/yiisoft/yii2/base/Module.php(552): yii\base\Controller->runAction('run', Array)
#20 /var/www/html/vendor/craftcms/cms/src/web/Application.php(293): yii\base\Module->runAction('queue/run', Array)
#21 /var/www/html/vendor/craftcms/cms/src/web/Application.php(602): craft\web\Application->runAction('queue/run', Array)
#22 /var/www/html/vendor/craftcms/cms/src/web/Application.php(272): craft\web\Application->_processActionRequest(Object(craft\web\Request))
#23 /var/www/html/vendor/yiisoft/yii2/base/Application.php(384): craft\web\Application->handleRequest(Object(craft\web\Request))
#24 /var/www/html/web/index.php(26): yii\base\Application->run()
#25 {main}

Can you kindly look into it and suggest a way to resolve this issue?
For more details, please check: https://github.com/spicywebau/craft-neo/issues/724
Steps to reproduce

Install and enable Neo and Cache Flag plugins.
Add an entry with a Neo field with multiple blocks in it.
Try to delete the saved entry.

Expected behaviour
The entry should delete properly without any failed job.
Neo version
2.13.16
Cache Flag version
1.3.3
Craft CMS version
3.8.2

Thanks for reporting that. In my opinion this is a Neo issue, and I've made a comment on https://github.com/spicywebau/craft-neo/issues/724 explaining why.
That said, the problem is easy enough to mitigate in Cache Flag, and I've just published v. 1.3.4 which should resolve the issue.

Thank you for looking into it and providing an update.


Where Col is Null

Is your feature request related to a problem? Please describe.
I've got a table with parentId which is a self relationship, I would like to be able to select just the parents.
Describe the solution you'd like
with .find({ where: { parentId: null } }) or .find({ where: { $isNull: parentId } }) or similar
Describe alternatives you've considered
I tried with parentId: undefined... and that returns all rows. I've looked through source code and API has isNull options, but its not available to FindOptions or related types.

Hi, @blalan05,
This should work today - please make sure that the parentId has allowNull set to true - when it is, it shoud be:
where:{parentId:null}
Check it and let me know

  @Fields.cuid()
  id = ''

  @Fields.integer({ allowNull: true })
  appId = 0

  @Fields.string()
  firstName = ''

  @Fields.string()
  lastName = ''

  @Fields.date()
  customerAt?: Date

  @Fields.string({ allowNull: true })
  parentId?: string
  @Relations.toOne(() => Customer, 'parentId')
  parent?: Customer
}```
![image](https://github.com/remult/remult/assets/42892508/3e6bfa1f-182c-4c4b-a1d7-f8076eb5e628)
![image](https://github.com/remult/remult/assets/42892508/3a1df516-bf49-488b-ae77-cb9c272b9ed7)

Wait... This is working as expected, my data was saving as empty string instead of null... is there a way to match empty string/ or falsey?

You can use the valueConverter to control how it's being loaded to and from the database:
https://remult.dev/docs/field-types#customize-db-value-conversions
Or you can use the saving hook to map that:
@Fields.string({saving:(_,ref){
if (ref.value=='')
ref.value=null
} })

Great! Is there something I can do to remove the type error when doing this?

Can you reproduce the typing error, I want to investigate it.
Try reproducing it here:
https://stackblitz.com/github/noam-honig/ready-to-play

https://stackblitz.com/edit/github-bxxyjv?file=src%2Fshared%2Fmodel.ts,src%2FApp.tsx Error replicated.
Solution though title?: string | null, but I guess I expected to not have to add | null... probably my misunderstanding of TS.

I'm not sure which type error are you referring to - can you reproduce it in this stackblitz?
https://stackblitz.com/github/noam-honig/ready-to-play

To be honest, in these cases I do title:null! and that works just fine

Did this workout for you?

I haven't seen null! before and was trying to learn what this is... I'm not sure where this snippet fits?

  useEffect(() => {
    taskRepo
      .find({
        limit: 20,
        orderBy: { createdAt: 'asc' },
        where: { title: null! }, //here
      })
      .then(setTasks)
  }, [])


CHEBI:50010 structural formula inconsistency

Both the IUPAC name of CHEBI:50010 and its parent stilbene have unspecified cis/trans isomery, the structural formula however does not reflect this (it's specific).

The same holds for the salt ChEBI:50011.

The presence of the wavy bonds in the structures indicate that the double bond stereochemistry is undefined.


Fail to Helm Install with Namespace defined in Chart

My local helm version 3.8.2, and I have a namespace defined with customized labels in the current folder.
helm will not create namespace with or without --create-namespace option, which seems dumb.
$helm install kserve . --namespace kserve
Error: INSTALLATION FAILED: create: failed to create: namespaces "kserve" not found
$helm install --create-namespace kserve . --namespace kserve
Error: INSTALLATION FAILED: no Namespace with the name "kserve" found

Please check your k8s permissions. @xfzhang1974 Thanks very much.


MarketCollateralPool Test

Description
Tests for Market Collateral Pool minting, redeeming and settle and close.
Checklist

[x] Linter status: 100% pass
[x] Changes don't break existing behavior
[ ] Tests coverage hasn't decreased

Refers/Fixes
Fixes: #159

@perfectmak Is this WIP PR tied to a specific issue? If so, go ahead and connect it to the PR. If not, set the Estimate and the current Milestone. Thanks!

I found the issue and connected it!

@perfectmak - rebase when you have a chance, everything is deploying properly and tests can now be ran.
The first basic minting test works, so hopefully, now your able to move forward without dealing with the complexities before!

Pull Request Test Coverage Report for Build 633

0 of 0   changed or added relevant lines in 0 files are covered.
131 unchanged lines in 17 files lost coverage.
Overall coverage decreased (-41.7%) to 36.501%

Files with Coverage Reduction
New Missed Lines
%

contracts/Linkable.sol
2
0.0%

contracts/chainlink/MarketContractFactoryChainLink.sol
2
64.29%

contracts/oraclize/MarketContractFactoryOraclize.sol
2
64.29%

contracts/oraclize/OracleHubOraclize.sol
3
34.88%

contracts/tokens/PositionToken.sol
3
40.0%

contracts/chainlink/OracleHubChainLink.sol
4
74.36%

contracts/tokens/UpgradeableTokenMock.sol
5
0.0%

contracts/Creatable.sol
5
10.0%

contracts/oraclize/MarketContractOraclize.sol
6
31.25%

contracts/tokens/UpgradableToken.sol
6
0.0%

Totals

Change from base Build 631:
-41.7%

Covered Lines:
149

Relevant Lines:
343

💛  - Coveralls

@perfectmak - reviewing and changing removing WIP from title

Missing tests (I think)

[ ] mintPositionTokens fails if market contract is already settled
[ ] mintPositionTokens TokensMinted event is fired and correctly returns values
[ ] redeemPositionTokens TokensRedeemed event is fired and correctly returns values
[ ] settleAndClose burns the expected number of position tokens upon success
[ ] settleAndClose TokensRedeemed event is fired and correctly returns values

I also think we should consider looking at the totalSupply_ of the erc20 short and long tokens to make sure that is being accounted for correctly, but perhaps @eswarasai is tackling that in his tests of PositionToken.sol

@pelsasser @perfectmak -- So the tests in regards with the PositionToken.sol are more of the duplicate to that of CollateralPool.test.js. It makes sense for me to have all the passing/failing tests in regards with the PositionToken to be under CollateralPool since it's the caller of the Long/Short Position Tokens. I'll try to tackle few of the above tests on this branch to breakdown the tasks. Thanks!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: perfectmak:x: eswarasaiYou have signed the CLA already but the status is still pending? Let us recheck it.

@pelsasser I believe all the case should have been checked now.


UND-12-31-49 Theming of list, images molecule, checkbox and radio

Closing this PR as it is now raised for ticket separately by shubham


⚠ Avatar API Endpoint has degraded performance

In 9d853f6, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1743 ms

Resolved: Avatar API Endpoint performance has improved in ec365bd after 9 minutes.


What software would you like us to add to our image catalog? (one per issue please)
Keycloak https://github.com/keycloak/keycloak
which versions of the containerized software do you need?
No response
Add some justification for why this specific image and versions are important.

Keycloak is a widely popular choice for identity, especially on-premise.
it's a CNCF project.
Wolfi already has Keycloak package.

Few thing to note though:

Keycloak operator (https://github.com/keycloak/keycloak/tree/main/operator) hardcode the kc.sh path to /opt/keycloak/bin/kc.sh in their code so it's sth we need to keep in mind if we want our image to be compatible with official keycloak operator.

What software would you like us to add to our image catalog? (one per issue please)
Keycloak https://github.com/keycloak/keycloak
which versions of the containerized software do you need?
No response
Add some justification for why this specific image and versions are important.

Keycloak is a widely popular choice for identity, especially on-premise.
it's a CNCF project.
Wolfi already has Keycloak package.

Few thing to note though:

Keycloak operator (https://github.com/keycloak/keycloak/tree/main/operator) hardcode the kc.sh path to /opt/keycloak/bin/kc.sh in their code so it's sth we need to keep in mind if we want our image to be compatible with official keycloak operator.

Good catch! We typically use the /usr/share/java/ convention instead of /opt, but this seems like a good enough reason to use /opt or symlink for this specific case.

To be precise, they have a realm import job which uses the same image as the main image.
in that job, they hardcode the path to kc.sh: https://github.com/keycloak/keycloak/blob/main/operator/src/main/java/org/keycloak/operator/controllers/KeycloakRealmImportJob.java#L165
        var runBuild = (keycloak.getSpec().getImage() == null) ? "/opt/keycloak/bin/kc.sh build && " : "";

        var commandArgs = List.of("-c",
                runBuild + "/opt/keycloak/bin/kc.sh import --file='" + importMntPath + getRealmName() + "-realm.json' " + override);

I think these PRs should fix it

https://github.com/wolfi-dev/os/pull/18780/
https://github.com/chainguard-images/images/pull/2690


Fix column resize issue in profiler

This PR fixes https://github.com/microsoft/azuredatastudio/issues/24540.
Somehow setting the padding to move the loading indicator down messed up the columns' resize functionality. Localizing the issue to when the loading indicator is actually added and removing the padding when it is removed.

can you also please add screenshots or gifs of before and after?

can you also please add screenshots or gifs of before and after?

Updated with gifs with before and after the fix.


locode_db -> locode.db

Where the underscore comes from? Let's rename it to locode.db!

Where do the dots come from?

It happened so.
https://en.wikipedia.org/wiki/Filename_extension
https://en.wikipedia.org/wiki/Media_type#Mime.types
https://wiki.debian.org/MIME/etc/mime.types

Obsoleted by #17, there won't be any DB in releases (and IR config).


A&R-> Exported report shows more than 2 decimal places on the Net Revenue column

Description
How to replicate:

Navigate to the A&R Admin on the Test environment
Log in and navigate to the Export Reports page
Generate a new report or download an already exported report
Open the generated report and check all the Net revenue columns on the report

Expected Behavior:

As it’s a currency value, I would assume the amount should be rounded up to 2 decimal places. @JLWade to confirm

Issue:

All the Net revenue columns show more than 2 decimal places

Tested on TEST: Passed

verified that this issue has been fixed.

only showing 2 decimals - moving to done


[FLINK-22157][table-planner-blink] Fix join & select a portion of composite primary key will cause ArrayIndexOutOfBoundsException

(This PR is picked from #15540.)
What is the purpose of the change
FlinkRelMdUniqueKeys#getTableUniqueKeys currently does not consider the case when projections are pushed down and cause only a part of the composite primary key to be selected.
This PR fixes this issue.
Brief change log

Fix join & select a portion of composite primary key will cause ArrayIndexOutOfBoundsException

Verifying this change
This change added tests and can be verified by running the added tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

Hi, it is better to re-open JIRA before open cherry-pick PR.

@flinkbot run azure


apt-packages invalid signature was encountered

Since yesterday I am not able to rebuild the dev container based on python:3.12-bullseye adding ffmpeg,libsm6,libxext6 APT packages.
//.devcontainer.json
{
  // https://github.com/devcontainers/images/blob/main/src/python
  "image": "mcr.microsoft.com/devcontainers/python:3.12-bullseye",
  "features": {
    // https://containers.dev/features
    "ghcr.io/rocker-org/devcontainer-features/apt-packages:1": {
      "packages": "ffmpeg,libsm6,libxext6"
    }
  },
  "postCreateCommand": "pip install -r requirements.txt"
}

Error log
------
 > [dev_containers_target_stage 5/5] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=apt-packages_0,target=/tmp/build-features-src/apt-packages_0     cp -ar /tmp/build-features-src/apt-packages_0 /tmp/dev-container-features  && chmod -R 0755 /tmp/dev-container-features/apt-packages_0  && cd /tmp/dev-container-features/apt-packages_0  && chmod +x ./devcontainer-features-install.sh  && ./devcontainer-features-install.sh  && rm -rf /tmp/dev-container-features/apt-packages_0:
0.120 ===========================================================================
0.120 Feature       : apt packages
0.120 Description   : Installs packages via apt.
0.120 Id            : ghcr.io/rocker-org/devcontainer-features/apt-packages
0.120 Version       : 1.0.2
0.120 Documentation : https://github.com/rocker-org/devcontainer-features/tree/main/src/apt-packages
0.120 Options       :
0.120     PACKAG
[2024-02-07T20:34:46.256Z] ES="ffmpeg,libsm6,libxext6"
0.120     UPGRADEPACKAGES="false"
0.120 ===========================================================================
0.135 find: ‘/var/lib/apt/lists/*’: No such file or directory
0.136 Running apt-get update...
0.217 Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB]
0.246 Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
0.278 Get:3 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
0.289 Get:4 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
0.329 Err:1 http://deb.debian.org/debian bullseye InRelease
0.329   At least one invalid signature was encountered.
0.367 Err:2 http://deb.debian.org/debian-security bullseye-security InRelease
0.367   At least one invalid signature was encountered.
0.392 Err:3 https://dl.yarnpkg.com/debian stable InRelease
0.392   At least one invalid signature was encountered.
0.426 Err:4 http://deb.debian.org/debian bullseye-updates InRelease
0.426   At least one invalid
[2024-02-07T20:34:46.256Z] signature was encountered.
0.430 Reading package lists...
0.436 W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered.
0.436 E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed.
0.436 W: GPG error: http://deb.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered.
0.436 E: The repository 'http://deb.debian.org/debian-security bullseye-security InRelease' is not signed.
0.436 W: GPG error: https://dl.yarnpkg.com/debian stable InRelease: At least one invalid signature was encountered.
0.436 E: The repository 'https://dl.yarnpkg.com/debian stable InRelease' is not signed.
0.436 W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered.
0.436 E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed.
0.436 ERROR: Feature "apt packages" (ghcr.io/rocker-org/devcontainer-features/apt-
[2024-02-07T20:34:46.256Z] packages) failed to install! Look at the documentation at https://github.com/rocker-org/devcontainer-features/tree/main/src/apt-packages for help troubleshooting this error.
------

My understanding is that this is a base image issue and there is nothing that can be done here.
Would running docker pull mcr.microsoft.com/devcontainers/python:3.12-bullseye before the build help?


Add support for modulo on semirings

Hopefully we'll be able to use this to flatten nats and odd/even coeffects.
Currently WIP as the SMT solver (I'm assuming it's that) is hanging on certain operations, such as (n * m) % m.

What's the status of this? Can we merge it into dev-minor now?


font family in jspdf

Hi
How to use font family Calibri for text in jspdf/html2canvas?
Thanks
Nitin

inside jspdf.js they only have addFont function as an private function. If you however scroll down or search "Public API". somewhere there (maybe after API.setFont) add
API.addFont = function(postScriptName, fontName, fontStyle) {
addFont(postScriptName, fontName, fontStyle, 'StandardEncoding');
};
this will enable you to set custom fonts. Below is an example of how to add this later on your document.
/* EXAMPLE
doc.addFont('ComicSansMS', 'Comic Sans', 'normal');
doc.setFont('Comic Sans');
doc.text(50,50,'Hello World');
*/

Thanks for reply