Fix autoload error

The specs are currently failing for using Rails 5.0.0.beta2. It looks like the changes from #1388 has something to do with it. I won’t clain to understand all (or anything) of that pull request, but by changing a few pieces, I got the spec suite running and not have only 1 failing spec locally. Let’s see what Travis says.
cc/ @cupakromer

Note that I included the 1 commit from #1570 which will (hopefully) eventually be merged on its own.

There you go: a green build. I don’t really understand why my changes make it work.
I noticed that the build error started in the example app’s config/initializers/action_mailer.rb when it references ActionMailer::Base:
NameError: uninitialized constant AbstractController::Rendering
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionpack-5.0.0.beta2/lib/action_controller/base.rb:204:in `<class:Base>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionpack-5.0.0.beta2/lib/action_controller/base.rb:164:in `<module:ActionController>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionpack-5.0.0.beta2/lib/action_controller/base.rb:5:in `<top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/test_case.rb:11:in `<class:TestCase>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/test_case.rb:10:in `<module:ActionView>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/test_case.rb:8:in `<top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/bundler/gems/rails-controller-testing-ce370fe84883/lib/rails-controller-testing.rb:16:in `block in <top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/activesupport-5.0.0.beta2/lib/active_support/lazy_load_hooks.rb:38:in `instance_eval'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/activesupport-5.0.0.beta2/lib/active_support/lazy_load_hooks.rb:38:in `execute_hook'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/activesupport-5.0.0.beta2/lib/active_support/lazy_load_hooks.rb:45:in `block in run_load_hooks'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/activesupport-5.0.0.beta2/lib/active_support/lazy_load_hooks.rb:44:in `each'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/activesupport-5.0.0.beta2/lib/active_support/lazy_load_hooks.rb:44:in `run_load_hooks'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/base.rb:215:in `<class:Base>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/base.rb:139:in `<module:ActionView>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/base.rb:10:in `<top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionview-5.0.0.beta2/lib/action_view/view_paths.rb:1:in `<top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionpack-5.0.0.beta2/lib/abstract_controller/rendering.rb:4:in `<top (required)>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionmailer-5.0.0.beta2/lib/action_mailer/base.rb:426:in `<class:Base>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionmailer-5.0.0.beta2/lib/action_mailer/base.rb:420:in `<module:ActionMailer>'
/home/travis/build/rspec/bundle/ruby/2.2.0/gems/actionmailer-5.0.0.beta2/lib/action_mailer/base.rb:9:in `<top (required)>'
/home/travis/build/rspec/rspec-rails/tmp/example_app/config/initializers/action_mailer.rb:15:in `<top (required)>'

For some reason, there’s a circular dependency! Notice how abstract_controller/rendering.rb:4 is in the trace, and module Rendering isn’t defined until line 16.

Sigh … specs are failing for Rails master.

Kinda expected, to merge this it needs squashing, also shouldn't it be < 5 not 4? 4 builds fine.

4 builds fine without the hack, so I see no need to include it.

Squashed.


WFS Filter PropertyName lost

Using the following WFS-Filter we want to reduce the response from the WFS to the attributes 'ogc_fid' and 'cat'. It works properly with geoserver.
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:ogc="http://www.opengis.net/ogc" xmlns:gml="http://www.opengis.net/gml" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" service="WFS" version="2.0.0" startIndex="0" count="25" outputFormat="application/json">
<wfs:Query typeNames="EOME:WRS2">
<wfs:PropertyName>ogc_fid</wfs:PropertyName>
<wfs:PropertyName>cat</wfs:PropertyName>
  <fes:Filter xmlns:fes="http://www.opengis.net/fes/2.0">
 <fes:And>
   <fes:PropertyIsBetween><fes:ValueReference>sensing_time</fes:ValueReference>
    <fes:LowerBoundary>
      <fes:Literal>2013-02-02T13:00:00.000Z</fes:Literal>
    </fes:LowerBoundary>
    <fes:UpperBoundary>
      <fes:Literal>2017-01-03T15:20:47.654Z</fes:Literal>
    </fes:UpperBoundary>
  </fes:PropertyIsBetween>
 </fes:And>
</fes:Filter>
</wfs:Query></wfs:GetFeature>

Converting this XML to JSON with JSONIX produces the following result:
{
    "name": {
        "namespaceURI": "http://www.opengis.net/wfs/2.0",
        "localPart": "GetFeature",
        "prefix": "wfs",
        "key": "{http://www.opengis.net/wfs/2.0}GetFeature",
        "string": "{http://www.opengis.net/wfs/2.0}wfs:GetFeature"
    },
    "value": {
        "TYPE_NAME": "WFS_2_0.GetFeatureType",
        "service": "WFS",
        "version": "2.0.0",
        "startIndex": 0,
        "count": 25,
        "outputFormat": "application/json",
        "abstractQueryExpression": [{
            "name": {
                "namespaceURI": "http://www.opengis.net/wfs/2.0",
                "localPart": "Query",
                "prefix": "wfs",
                "key": "{http://www.opengis.net/wfs/2.0}Query",
                "string": "{http://www.opengis.net/wfs/2.0}wfs:Query"
            },
            "value": {
                "TYPE_NAME": "WFS_2_0.QueryType",
                "typeNames": ["EOME:WRS2"],
                "abstractSortingClause": {
                    "name": {
                        "namespaceURI": "http://www.opengis.net/wfs/2.0",
                        "localPart": "PropertyName",
                        "prefix": "wfs",
                        "key": "{http://www.opengis.net/wfs/2.0}PropertyName",
                        "string": "{http://www.opengis.net/wfs/2.0}wfs:PropertyName"
                    },
                    "value": {
                        "TYPE_NAME": "WFS_2_0.PropertyName",
                        "value": {
                            "namespaceURI": "",
                            "localPart": "cat",
                            "prefix": "",
                            "key": "cat",
                            "string": "cat"
                        }
                    }
                }
            }
        }]
    }
}

It seems that only the last PropertyName ('cat') has been considered. The PropertyName 'ogc_fid' has been ignored.
Vice versa we have the same problem to generate a json and convert it to XML with several PropertyNames so that the result-XML looks like the XML-example (see above).
Thank you and best regards

Sorry to bring this up after quite some time, but I think it would be redundant to file a new issue for the same problem.
I have encountered this same issue with both the unmarshalling and marshalling of a WFS GetFeature element. This seems to be related to a bug in Jsonix's handling of substitutionGroups and abstract elements/types.
More specifically, the wfs:QueryType extends fes:AbstractAdhocQueryExpressionType, which in turn extends fes:AbstractQueryExpressionType. This last type holds three references to abstract elements, fes:AbstractProjectionClause, fes:AbstractSelectionClause and fes:AbstractSortingClause. These elements are AnyType and there seems to be some constraint in Jsonix's type/structure internal object where there can only be one AnyType element.
The code where the I think I found the bug is here, in the unmarshal function:
// New sub-element starts
var elementNameKey = input.getNameKey();
if (Jsonix.Util.Type
		.exists(this.structure.elements[elementNameKey])) {
	var elementPropertyInfo = this.structure.elements[elementNameKey];
	this.unmarshalProperty(context, input,
			elementPropertyInfo, result);
} else if (Jsonix.Util.Type
		.exists(this.structure.any)) {
	// TODO Refactor

	var anyPropertyInfo = this.structure.any;
	this.unmarshalProperty(context, input,
			anyPropertyInfo, result);
} else {
	// TODO optionally report a validation error that the element is not expected
	et = input.skipElement();
}

So, the first if condition is not met as it does not take into account the substitutions.
The second, instead, is true as the structure does have an AnyType element, but it wrongly references just the last one. In this case, AbstractSortingClause. And this seems to be the reason why the unmarshaller puts the PropertyName under the wrong element (while it's supposed to go in the AbstractProjectionClause).
I also suspect that for the reasons I just listed, the handling of an AnyType collection might be broken. One such example is exactly the AbstractProjectionClause element (minOccurs=0, maxOccurs=unbounded).
And all this is just for the unmarshalling. I'm having a hard time trying to do the marshalling as well, and I am quite positive similar issues exist in the marshalling process.
@highsource Could you confirm if those issues do indeed exist? I could attempt a fix on my own but I am not familiar with this library's structure and code.
Thank you.
Riccardo

@ricky92
There is indeed a problem, but not in Jsonix.
It is complicated so please bear with me.
OGC schemas sometimes use substitution groups as extension points. For instance, Filter 2.0 defines the following elements:
   <xsd:element name="AbstractProjectionClause" abstract="true"/>
   <xsd:complexType name="AbstractProjectionClauseType" abstract="true"/>

   <xsd:element name="AbstractSelectionClause" abstract="true"/>
   <xsd:complexType name="AbstractSelectionClauseType" abstract="true"/>

   <xsd:element name="AbstractSortingClause" abstract="true"/>
   <xsd:complexType name="AbstractSortingClauseType" abstract="true"/>

Other schemas define elements which the may substitute these abstract elements. Like WFS 2.0:
   <xsd:element name="PropertyName"
      substitutionGroup="fes:AbstractProjectionClause">
      ...
   </xsd:element>

For this to work, Jsonix has to generate element reference properties.
The problem is in how JAXB (the tech Jsonix is based on) processes abstract elements.
If JAXB sees other elements which may replace this element, it will generate element reference properties.
If there are no elements to replace this element, it will be generated as an element property.
When compiling schemas separately (i.e. Filter 2.0 without WFS 2.0), some of the abstract elements designated to be substitution group heads will not have substitutes in the given schema set. So JAXB desides that these should be simple element properties. This leads to the problem that these elements cannot be replaced by anything else.
So far I did not found a better solution rather than simply adding at least one substitution element per designated substitution group head. For instance, in Filter 2.0:
   <xsd:element name="ProjectionClauseExtension" substitutionGroup="fes:AbstractProjectionClause"/>
   <xsd:element name="SelectionClauseExtension" substitutionGroup="fes:AbstractSelectionClause"/>
   <xsd:element name="SortingClauseExtension" substitutionGroup="fes:AbstractSortingClause"/>

With this you get element reference properties like it should be.
This requires patching schemas which I actually do in ogc-schemas.
Ok, to sum up - yes, there is a problem but I do not think it is a bug in Jsonix.

So, the first if condition is not met as it does not take into account the substitutions.

It would have taken substitution into account if they were defined in mappings. But due to the reasons listed above, they are not.

@highsource
Thank you so much for your quick response.
I understand that there is a problem in how JAXB handles abstract elements, but, as you said, you provided a patch/workaround to 'fix' those mappings.
After digging some more in the code and in the schemas, though, I noticed that the workaround you applied to mark those abstract elements as elementRefs works for all but the AbstractProjectionClause element.
In fact, as you can see in the Filter_2_0 schema, such element does not even have a type specified:
        ln: 'AbstractAdhocQueryExpressionType',
        bti: '.AbstractQueryExpressionType',
        ps: [{
            n: 'abstractProjectionClause',
            mno: 0,
            col: true,
            en: 'AbstractProjectionClause',
            ti: 'AnyType',
            // There should be the following line here:
            // t: 'er'
          }, {
            n: 'abstractSelectionClause',
            mx: false,
            dom: false,
            en: 'AbstractSelectionClause',
            ti: 'AnyType',
            t: 'er'
          }, {
            n: 'abstractSortingClause',
            mx: false,
            dom: false,
            en: 'AbstractSortingClause',
            ti: 'AnyType',
            t: 'er'
          },

After modifying the schema manually, it now works as expected. The example request gets unmarshalled correctly and the PropertyNames end up in the abstractProjectionClause object property.
Marshalling works as well, for example an object with this structure:
{
  "wfs:GetFeature":{
    "TYPE_NAME":"WFS_2_0.GetFeatureType",
    "service":"WFS",
    "version":"2.0.0",
    "outputFormat":"application/json",
    "count":20,
    "abstractQueryExpression":[
      {
        "wfs:Query":{
          "TYPE_NAME":"WFS_2_0.QueryType",
          "abstractProjectionClause":[
            {
              "wfs:PropertyName":{
                "TYPE_NAME":"WFS_2_0.PropertyName",
                "value":{
                  "namespaceURI":"http://example.org/",
                  "localPart":"zone",
                  "prefix":"example",
                  "key":"{http://example.org/}zone",
                  "string":"{http://example.org/}example:zone"
                }
              }
            },
            {
              "wfs:PropertyName":{
                "TYPE_NAME":"WFS_2_0.PropertyName",
                "value":{
                  "namespaceURI":"http://example.org/",
                  "localPart":"name",
                  "prefix":"example",
                  "key":"{http://example.org/}name",
                  "string":"{http://example.org/}example:name"
                }
              }
            }
          ],
          "typeNames":[
            "example:test"
          ]
        }
      }
    ]
  }
}

...gets correctly marshalled to:
<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dct="http://purl.org/dc/terms/" xmlns:fes="http://www.opengis.net/fes" xmlns:gml="http://www.opengis.net/gml" xmlns:ogc="http://www.opengis.net/ogc" xmlns:p0="http://www.opengis.net/wfs/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="p0:GetFeatureType" service="WFS" version="2.0.0" count="20" outputFormat="application/json">
  <wfs:Query xsi:type="p0:QueryType" typeNames="example:test">
    <wfs:PropertyName xmlns:example="http://example.org/" xsi:type="p0:PropertyName">example:zone</wfs:PropertyName>
    <wfs:PropertyName xmlns:example="http://example.org/" xsi:type="p0:PropertyName">example:name</wfs:PropertyName>
  </wfs:Query>
</wfs:GetFeature>

So I guess this means that there is some problem in how the schema gets compiled.
I cannot really submit a fix to the ogc-schemas repository as I only found where the problem lies, but not its cause. I hope this information can help you fix the issue, though. Thank you again.


Choosing new parents

Due to an installation loop, a new override has been created (see Issue #27 in the formerly used repo). Automated import into munki repo has succeeded.

No issues were found during review


nested react-sortable-hoc conflict,  react-sortable-hoc.esm.js:1380 Uncaught TypeError: Cannot read property 'top' of undefined

in my module i'm using this hoc in nested variant, when i trying to sort in second level sortable elements, parent level sorting getting stuck
here are my repo: https://github.com/amirjanyanIT/react-form-designer
parent level you can find in /src/index.js
second level you can find in "/src/Options/MultiSelect/index.js", "/src/Options/DropDown/index.js"
actualy i tryed change keys of sortableElements from numeric into string variant but problem not gone

I solved my issue, problem in SortableElement wich wrapper component or tag always should be same, i just wrapped all my conditional changes in div and problem gone :)


grpcclient: don't retry on ResourceExhausted

What this PR does:
The changes fix, what looks like a typo in the grpcclient package's middleware. That is the client should not retry their requests if server signals its resources are already exhausted (i.e. the ResourceExhausted error).
Which issue(s) this PR fixes:
Checklist

[ ] Tests updated
[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

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

this middleware seems to be turned on when back_off_on_rate_limits: true
https://github.com/grafana/mimir/blob/1997cf598be8d94a2d2761915a78c940c82dbc93/vendor/github.com/grafana/dskit/grpcclient/grpcclient.go#L110-L112
Doesn't ResourceExhausted refer to cases where the a rate limit has been exceeded? That's what some of the comments/strings say in mimir code and tempo code

this middleware seems to be turned on when back_off_on_rate_limits: true

That's what I missed, indeed. How about we rename the middleware to something more obvious, maybe NewRateLimitRetrier()?
For the context, of why I'm looking at that, from https://github.com/grafana/mimir/issues/6609, gRPC server returns the codes.ResourceExhausted code if the payload exceeds the configured limit. I looked around for examples of where the code used across the code, and bumped into this one.

How about we rename the middleware to something more obvious, maybe NewRateLimitRetrier()?

makes sense to me. At a glance I couldn't find it being widely used outside of the linked dskit usage, so we might be ok to do this breaking change.


[#115] Add Skeleton loading support

Solves #115
What happened 👀
We can add Skeleton loading - which brings better UX - as an option to show the loading progress on listview or a single view beside the ProgressBar.
Insight 📝
There are 2 good candidates with 2 different ways to implement:

Facebook shimmer-android basically produces a shimmer effect on the layout, so what we need is to create skeleton layouts to fake the main layout components.
SkeletonLayout produces an automatic way to create a skeleton, what we need is executing createSkeleton or applySkeleton on RecyclerView or ViewPager2.

To ease and simplify the implementation process, I decided to give it a try with the second candidate.
Proof Of Work 📹
https://user-images.githubusercontent.com/16315358/129722568-372df742-34a4-44b7-aa43-6df45ff6c251.mp4

Home screen

Second (with a fake delay to see the loading on the image)

Cool!
Should we add this library to CoroutineTemplate as well? 🙏

possible, after we merged this one maybe 🤔

@lydiasama @sleepylee let me check and find a good way to manage this kind of essential feature in our template 🙏

@luongvo Should target branch be develop ? 🙏

@luongvo Should target branch be develop ? 🙏

aha, yes, thank you :))

@luongvo should we close this PR (maybe update the title to annotate the decision we made) - and keep the branch?

@luongvo @lydiasama: for showcases like this, I would recommend creating a separate initiative + repository to demonstrate this knowledge or component. You may want to visit this board where we had some initiatives drafted with proper output tracking + purposes: https://www.notion.so/nimblehq/e0591f3e0b5349be8890dcada863796f?v=c42d5b71765b4a5cb0bdc400eacb4b8b. For now, I suggest closing the PR + branch to reduce the stale work residue


validators of statically created objects can't access custom Messages object

In validators of statically created objects this.errorMessages points to the default ember-cp-validations/validators/messages instead of app/validators/messages
For example:
// app/validators/messages.js
export default Messages.extend({
  example: "example error message"
});

// models/user.js
var Validations = buildValidations({
  username: [
     validator(function(){
        return this.errorMessages.getMessageFor('example', {});
     })
  ]
});
export default Ember.Object.extend(Validations, {
  username: null
});

// routes/index.js
import User from '../models/user';
export default Ember.Route.extend({
  model() {
    var options = { username: 'John' };
    Ember.setOwner(options, Ember.getOwner(this));
    return User.create(options)
  }
});

{{!-- /app/templates/index.hbs --}}
{{v-get model 'username' 'message'}}

The output will be "undefined is invalid" instead of "example error message".
This is because the default message type is invalid.

Ah I know what the issue is. Ill open a PR with the fix in a little bit. Thanks for pointing this issue out!

Waiting on rwjblue/ember-getowner-polyfill#1 before this can be resolved.

@ramybenaroya please upgrade to v2.1.4. Should solve this problem :smile_cat:

@offirgolan Thanks for all your hard work and for this great addon!

Np :smiley_cat: Feel free to reach out if any other issues come up!


Compilation Error on iOS with Flutter 3.19.5: 'ui.KeyEventDeviceType' not found

Steps to reproduce
Environment
[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4.1 23E224 darwin-arm64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.88.0)
[✓] Connected device (3 available)
Description
I encountered a compilation error while building an iOS app using Flutter version 3.19.5. The error seems to be related to a missing type in the Flutter framework.
Steps to Reproduce

Update Flutter to version 3.19.5.
Attempt to compile the iOS version of my application.
Compilation fails with the following error message:
../packages/flutter/lib/src/services/hardware_keyboard.dart:215:9: Error: Type 'ui.KeyEventDeviceType' not found

Would appreciate any guidance on resolving this issue or any workarounds that might be available. Thank you!
Expected results
The application should compile without errors.
Actual results
The application fails to compile, and the error message indicates a missing type ui.KeyEventDeviceType.
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs

**../packages/flutter/lib/src/services/hardware_keyboard.dart:215:9: Error: Type 'ui.KeyEventDeviceType' not found**

[Paste your logs here]

Flutter Doctor output

[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4.1 23E224 darwin-arm64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.88.0)
[✓] Connected device (3 available)

[Paste your output here]

@kerneltea
When you upgraded the version, did you run flutter pub get ?
It seems some caching issue which didn't clear after the upgrade was done. Can you provide complete error log in properly formatted text ?
Also, what command are you running to run on iOS ?

When you upgraded the version,

I downloaded this version yesterday.(2024/04/11)

did you run flutter pub get ?

I did run the flutter pub get command, and I also tried performing flutter clean followed by flutter pub get.

It seems some caching issue which didn't clear after the upgrade was done. Can you provide complete error log in properly formatted text ?

error: ../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:215:9: Error: Type 'ui.KeyEventDeviceType' not found.
  final ui.KeyEventDeviceType deviceType;
        ^^^^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1182:3: Error: Type 'ui.KeyEventDeviceType' not found.
  ui.KeyEventDeviceType _convertDeviceType(RawKeyEvent rawEvent) {
  ^^^^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:127:26: Error: Undefined name 'KeyEventDeviceType'.
    this.deviceType = ui.KeyEventDeviceType.keyboard,
                         ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:215:12: Error: 'KeyEventDeviceType' isn't a type.
  final ui.KeyEventDeviceType deviceType;
           ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1186:17: Error: Undefined name 'KeyEventDeviceType'.
      return ui.KeyEventDeviceType.keyboard;
                ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1192:19: Error: Undefined name 'KeyEventDeviceType'.
        return ui.KeyEventDeviceType.keyboard;
                  ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1195:19: Error: Undefined name 'KeyEventDeviceType'.
        return ui.KeyEventDeviceType.directionalPad;
                  ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1198:19: Error: Undefined name 'KeyEventDeviceType'.
        return ui.KeyEventDeviceType.gamepad;
                  ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1201:19: Error: Undefined name 'KeyEventDeviceType'.
        return ui.KeyEventDeviceType.joystick;
                  ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1204:19: Error: Undefined name 'KeyEventDeviceType'.
        return ui.KeyEventDeviceType.hdmi;
                  ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1206:15: Error: Undefined name 'KeyEventDeviceType'.
    return ui.KeyEventDeviceType.keyboard;
              ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1223:14: Error: 'KeyEventDeviceType' isn't a type.
    final ui.KeyEventDeviceType deviceType = _convertDeviceType(rawEvent);
             ^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1324:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.
 - 'KeyData' is from 'dart:ui'.
Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.
          deviceType: keyData.deviceType,
                              ^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1333:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.
 - 'KeyData' is from 'dart:ui'.
Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.
          deviceType: keyData.deviceType,
                              ^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1341:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.
 - 'KeyData' is from 'dart:ui'.
Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.
          deviceType: keyData.deviceType,
                              ^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1504:4: Error: Type 'ui.GlyphInfo' not found.
   ui.GlyphInfo? getClosestGlyphForOffset(Offset offset) {
   ^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1508:14: Error: 'GlyphInfo' isn't a type.
    final ui.GlyphInfo? rawGlyphInfo = cachedLayout.paragraph.getClosestGlyphInfoForOffset(offset - cachedLayout.paintOffset);
             ^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1512:15: Error: Method not found: 'GlyphInfo'.
    return ui.GlyphInfo(rawGlyphInfo.graphemeClusterLayoutBounds.shift(cachedLayout.paintOffset), rawGlyphInfo.graphemeClusterCodeUnitRange, rawGlyphInfo.writingDirection);
              ^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1508:63: Error: The method 'getClosestGlyphInfoForOffset' isn't defined for the class 'Paragraph'.
 - 'Paragraph' is from 'dart:ui'.
Try correcting the name to the name of an existing method, or defining a method named 'getClosestGlyphInfoForOffset'.
    final ui.GlyphInfo? rawGlyphInfo = cachedLayout.paragraph.getClosestGlyphInfoForOffset(offset - cachedLayout.paintOffset);
                                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/semantics/semantics.dart:2787:7: Error: No named parameter with the name 'identifier'.
      identifier: data.identifier,
      ^^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/rendering/paragraph.dart:736:11: Error: 'GlyphInfo' isn't a type.
    final GlyphInfo? glyph = _textPainter.getClosestGlyphForOffset(position);
          ^^^^^^^^^
../../../flutter/flutter-3.19.5/packages/flutter/lib/src/rendering/editable.dart:1951:11: Error: 'GlyphInfo' isn't a type.
    final GlyphInfo? glyph = _textPainter.getClosestGlyphForOffset(effectivePosition);
          ^^^^^^^^^
Target kernel_snapshot failed: Exception
Failed to package /Users/fusion/dev/guru/guru_app_sdk3/m2blocks.

  final ui.KeyEventDeviceType deviceType;

        ^^^^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1182:3: Error: Type 'ui.KeyEventDeviceType' not found.

  ui.KeyEventDeviceType _convertDeviceType(RawKeyEvent rawEvent) {

  ^^^^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:127:26: Error: Undefined name 'KeyEventDeviceType'.

    this.deviceType = ui.KeyEventDeviceType.keyboard,

                         ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:215:12: Error: 'KeyEventDeviceType' isn't a type.

  final ui.KeyEventDeviceType deviceType;

           ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1186:17: Error: Undefined name 'KeyEventDeviceType'.

      return ui.KeyEventDeviceType.keyboard;

                ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1192:19: Error: Undefined name 'KeyEventDeviceType'.

        return ui.KeyEventDeviceType.keyboard;

                  ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1195:19: Error: Undefined name 'KeyEventDeviceType'.

        return ui.KeyEventDeviceType.directionalPad;

                  ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1198:19: Error: Undefined name 'KeyEventDeviceType'.

        return ui.KeyEventDeviceType.gamepad;

                  ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1201:19: Error: Undefined name 'KeyEventDeviceType'.

        return ui.KeyEventDeviceType.joystick;

                  ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1204:19: Error: Undefined name 'KeyEventDeviceType'.

        return ui.KeyEventDeviceType.hdmi;

                  ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1206:15: Error: Undefined name 'KeyEventDeviceType'.

    return ui.KeyEventDeviceType.keyboard;

              ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1223:14: Error: 'KeyEventDeviceType' isn't a type.

    final ui.KeyEventDeviceType deviceType = _convertDeviceType(rawEvent);

             ^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1324:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.

 - 'KeyData' is from 'dart:ui'.

Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.

          deviceType: keyData.deviceType,

                              ^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1333:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.

 - 'KeyData' is from 'dart:ui'.

Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.

          deviceType: keyData.deviceType,

                              ^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:1341:31: Error: The getter 'deviceType' isn't defined for the class 'KeyData'.

 - 'KeyData' is from 'dart:ui'.

Try correcting the name to the name of an existing getter, or defining a getter or field named 'deviceType'.

          deviceType: keyData.deviceType,

                              ^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1504:4: Error: Type 'ui.GlyphInfo' not found.

   ui.GlyphInfo? getClosestGlyphForOffset(Offset offset) {

   ^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1508:14: Error: 'GlyphInfo' isn't a type.

    final ui.GlyphInfo? rawGlyphInfo = cachedLayout.paragraph.getClosestGlyphInfoForOffset(offset - cachedLayout.paintOffset);

             ^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1512:15: Error: Method not found: 'GlyphInfo'.

    return ui.GlyphInfo(rawGlyphInfo.graphemeClusterLayoutBounds.shift(cachedLayout.paintOffset), rawGlyphInfo.graphemeClusterCodeUnitRange, rawGlyphInfo.writingDirection);

              ^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/painting/text_painter.dart:1508:63: Error: The method 'getClosestGlyphInfoForOffset' isn't defined for the class 'Paragraph'.

 - 'Paragraph' is from 'dart:ui'.

Try correcting the name to the name of an existing method, or defining a method named 'getClosestGlyphInfoForOffset'.

    final ui.GlyphInfo? rawGlyphInfo = cachedLayout.paragraph.getClosestGlyphInfoForOffset(offset - cachedLayout.paintOffset);

                                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/semantics/semantics.dart:2787:7: Error: No named parameter with the name 'identifier'.

      identifier: data.identifier,

      ^^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/rendering/paragraph.dart:736:11: Error: 'GlyphInfo' isn't a type.

    final GlyphInfo? glyph = _textPainter.getClosestGlyphForOffset(position);

          ^^^^^^^^^

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/rendering/editable.dart:1951:11: Error: 'GlyphInfo' isn't a type.

    final GlyphInfo? glyph = _textPainter.getClosestGlyphForOffset(effectivePosition);

          ^^^^^^^^^

Target kernel_snapshot failed: Exception

Failed to package xxxxx

../../../flutter/flutter-3.19.5/packages/flutter/lib/src/services/hardware_keyboard.dart:215:9: Error: Type 'ui.KeyEventDeviceType' not found.

Also, what command are you running to run on iOS ?
I compiled directly using Xcode. Previously, I was using version 3.16.9."

I downloaded this version yesterday.(2024/04/11)

So you directly downloaded the latest version instead of upgrading it by let's say running flutter upgrade ?
If you create default counter app project, does it still give you same errors ?
Also, if you switch to latest master and try to run your app (not the counter app), do you still see same errors ?


Response to smart home action

Hey, can you confirm that this version o SDK in C++ does not have support to actions response?
I'm trying to get a JSON with an answer of a smart home action but I'm getting an empty JSON.
I tried to get the JSON using the method device_request_json listed on the DOCs of Package google.assistant.embedded.v1alpha2.
     actionObject = response.device_action().device_request_json();

Smart home responses are not available through the API. Conversational actions do get sent back.


custom dataset

Hi, thanks for this great work.
By given custom dataset's camera intrinsic and extrinsic, is it possible to inference directly without training the model?
Best regards

Yes, that's what I did to get Fig. 9 in the paper.

Thanks for replay. I will check Fig. 9 in the paper.


Discover inputs for Cpp compilation

@lptr I ended up creating a new plugin which adds the discover inputs tasks for C/CPP compilation. If this plugin is applied when using the software model native plugins then the discover inputs tasks will be created, too. Please have a look.

@lptr I addressed your comments, please have another look.

I left a few comments on the Crucible review: https://code-review.gradle.org/cru/REVIEW-6568

\o/


Clarifying GW upgrade options

Hi @AlekseiPolkovnikov, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (alpolko). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@AlekseiPolkovnikov : Thanks for your contribution to the Azure documentation! The author, @cherylmc, has been notified to review your proposed change.

@charwen

#sign-off

#sign-off

Yes, it's true that this was just added. I'll update the doc after this is merged in. no need to put another update through.

Only the author of the article can use the sign off comment to add the ready-to-merge label.

#sign-off


tests: add test for issue 7241

Test for 8+ only.
Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket:

Merged in #2030, thanks!


WIP: Feat/integrate with html

@XBITSwitzerland wait with merge until bindings are finished

@Ofaso Okay, how is it going with the proxy? Did you found a solution for this? Did it work for you?


[RFC]: Add/Update package of ndarray namespace for BooleanArray support (tracking issue)

Description
This RFC proposes add or update all packages of ndarray namespace that needs to be changed in order to add BooleanArray support to Stdlib. The purpose of this issue is to serve as a tracking issue for update or add packages.
Packages need to be added:

[x] @stdlib/ndarray/base/assert/is-boolean-data-type

Packages need to be updated:

[x] @stdlib/ndarray/base/assign
[x] @stdlib/ndarray/base/buffer-ctors
[x] @stdlib/ndarray/base/buffer-dtype
[x] @stdlib/ndarray/base/buffer -> update docs
[x] @stdlib/ndarray/base/nullary
[x] @stdlib/ndarray/base/unary
[x] @stdlib/ndarray/dtypes
[x] @stdlib/ndarray/defaults
[x] @stdlib/ndarray/from-scalar
[x] @stdlib/ndarray/min-dtype
[x] @stdlib/ndarray/mostly-safe-casts
[x] @stdlib/ndarray/next-dtype
[x] @stdlib/ndarray/same-kind-casts
[x] @stdlib/ndarray/base/zeros, @stdlib/ndarray/base/empty, @stdlib/ndarray/base/zeros-like, @stdlib/ndarray/base/empty-like -> update tests
[x] @stdlib/ndarray/zeros, @stdlib/ndarray/empty, @stdlib/ndarray/zeros-like, @stdlib/ndarray/empty-like -> update tests

Related Issues
None
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@Jaysukh-409 As I believe everything in this tracking issue has now been completed, I will go ahead and close this issue.


E5113: Error while calling lua chunk: Vim:E6100: "log" is not a valid stdpath

I use the install.sh to install.  Then I tap nvim in console.
Then I meet the error follow:
OS: Linux vultr 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Error detected while processing /root/.hwloser-vim/init.lua:
E5113: Error while calling lua chunk: Vim:E6100: "log" is not a valid stdpath
stack traceback:
        [C]: in function 'stdp'
        ....config/nvim/lua/standardpath/standardpathdefination.lua:126: in main chunk
        [C]: in function 'require'
        /root/.config/nvim/lua/standardpath/init.lua:15: in main chunk
        [C]: in function 'require'
        /root/.config/nvim/lua/bootstrap.lua:11: in main chunk
        [C]: in function 'require'
        /root/.config/nvim/init.lua:4: in main chunk
Press ENTER or type command to continue

plz help me

Description
I know, your neovim is not the nightly neovim, whcih is latest version of neovim.
My Macos「command - :version」:
NVIM v0.9.0-dev-988+gf905ab045-dirty
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>How fix it
brew install --HEAD neovim

before I run these commands:
nvim --version
NVIM v0.6.1
Build type: Release
LuaJIT 2.1.0-beta3
after I update:
nvim --version
NVIM v0.7.2
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>but still error

before I run these commands:

nvim --version
NVIM v0.6.1
Build type: Release
LuaJIT 2.1.0-beta3

after I update:

nvim --version
NVIM v0.7.2
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>
but still error

i`ll try fix it. Try it again after git pull new codes.

It`s look like a nother problems of lower version。

i will hidden it by check if we could set it, but we cloud enjoy the feature of bufferline, which could hover close button.
you can install from source code/ from https://github.com/neovim/neovim.git

install command

git clone https://github.com/neovim/neovim.git && cd neovim
git checkout nightly -b nightly
make CMAKE_BUILD_TYPE=RelWithDebInfo && sudo make install

Error detected while processing /root/.hwloser-vim/init.lua:
lazy.nvim requires Neovim >= 0.8.0
Press ENTER or type command to continue

I know what should i do. Thanks.


Change TimeGeneration configuration script

A new script that changes the TimeGenerated configuration to point to log creation time instead of log collection time.

@NoamLandress is PR still relevant?

Script Was merged in a different PR- https://github.com/Azure/Azure-Sentinel/pull/1288


[Feature] Add missing security rule to allow traffic flow within the LB subnet

Configuration:

OKE cluster with public OCI LB.
OCI API GW deployed into the same public subnet as OCI LB.

But it appears that the traffic is not flowing from a public API GW to public OCI LB via private IP addresses (from the following IP pool: <IP_ADDRESS>/27).
The reason for that is a missing egress rule on the LB subnet that allows both HTTP/HTTPS traffic on the following destination pool <IP_ADDRESS>/27.
It makes any incoming HTTP/HTTPS request to OCI API GW timeout because the network is not reachable.

Why would you want the LB balancer to be public if you have a public API gateway? Shouldn't you use a private LB instead?

I thought I explained this: we'd like to use public API GW, therefore a subnet that it is attached to must be public as well.
So, we deploy an Ingress object we receive an OCI LB with a private IP and later on we connect API GW to OCI LB and let them communicate with each other through private IPs, but the only service that has a public IP is an. API GW.
Our setup is: public subnet for LB, but every LB provisioned in that subnet receives a private IP intentionally, we use API GW connected to LB public subnet to work as a reverse proxy to LB.

You can achieve this by the following:

Set your lb_subnet_type to both - this will create 2 subnets for lb: public and private
Use the public lb subnet to create your api gw
Use the lb annotations to deploy your internal lb to the private subnet: https://github.com/oracle/oci-cloud-controller-manager/blob/master/docs/load-balancer-annotations.md

I'm sorry, but it doesn't solve the issue described above. It is not related to a type of load balancer, but to the absence of a security rule that prevents traffic flow between components of a system bound to the LB subnet.
I'm still not able to make API GW talk to LB unless I allow ingress traffic from any IP address from the LB subnet.


[Map] The incorrect name of the Crimea territory on the map when searching for a workshop

Environment: Win10 v21H2 64-bit, Chrome v 98.0.4758.82
Reproducible: always
Build found: frontend: gcp-0.0.53, backend: gcp-0.0.114
Preconditions

Go to OoS (https://oos.dmytrominochkin.cloud/#/)
Go to the 'Search' page by clicking 'Переглянути всі' near 'Найпопулярніші гуртки'

Steps to reproduce

Select the map view by clicking 'Карта' button
Zoom in the map and go to the Crimea territory

Actual result
The incorrect name of the Crimea territory is displayed on the map. The name of settlements and other objects is in Russian while settlements in Khersonska oblast is in Ukrainian.

Expected result
The Crimea is marked as the territory of Ukraine, all settlements and objects on the map are in Ukrainian
User story and test case links
User story #23
Test case OS-271
Labels to be added
"Bug", "pri: very high", "severity: trivial"

This bug is not reproduced.


Re-add support for full task status for backward compatibility

Tektoncd/pipelines release v0.45 came with some breaking changes. As a result, Chains needed to be updated. Support for fully embedded task status in pipelinerun status had to be removed. This PR re-adds support for those fields to make chains compatible with  older versions of Tekton pipelines (<v0.45).

Changes

Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
Re-add support for full task status for backward compatibility

/kind feature

cc @wlynch @lcarva

/assign @wlynch


Corrected comment referencing incorrect function name

Referencing uhdr_decode() instead of uhdr_decompress()

Thank you for the fix!


Fwxv 250 update drive fsm

Refactor Drive FSM to finalize the main functionality it needs to have

@JarvisWeng Main changes to this are moving all of the hardware interaction for Centre Console to one file, update_dashboard.c. Would be a good place to start your review. You can also look at other places where I've added comments. Ayo is working on validating these changes, but might be better to merge them in so we don't block others


Adding Documenter.jl documentation

Updating Documentation and switching to Documenter.jl documentation hosted on GitHub pages.

@arun3688 feel free to push your updates to this branch. Then we can see the updates in the documentation on the hosted page: https://openmodelica.github.io/OMJulia.jl/dev/

Of course the CI gets stuck again
 ┌ Debug: Evaluating @repl block:
│ using OMJulia
│ mod = OMJulia.OMCSession()
│ omcWorkDir = mkpath(joinpath("docs", "omc-temp"))  # hide
│ mkpath(omcWorkDir)                                 # hide
│ sendExpression(mod, "cd(\"$(omcWorkDir)\")")       # hide
│ ModelicaSystem(mod,
│                joinpath("docs", "testmodels", "ModSeborgCSTRorg.mo"),
│                "ModSeborgCSTRorg")
└ @ Documenter.Expanders ~/.julia/packages/Documenter/bYYzK/src/Expanders.jl:710
Error: The operation was canceled.

I think I found the error in https://github.com/OpenModelica/OMJulia.jl/pull/92/commits/0ec9f7d60725d2c6b9a00f7299e3834905c26057#diff-dc43fffef55b37c2a83193f882e2353198d095feda1cc5d5f89dd962ae49efc0R134-R136.
It looks like
open(pipeline`$omc $args1 $args2`)

broke the Documenter.jl build. Reverting the change to
open(pipeline`$omc $args1 $args2`, stdout="stdout.log", stderr="stderr.log")

seems to fix this. But in that case we will never be able to build the documentation on Windows, because of https://github.com/OpenModelica/OMJulia.jl/issues/88.


Messages not being unqueued

Hi, we have maximum_delivery_attempts set to 1 but messages are still be requeued after a soft fail? This is causing a lot of issues for our customers. Any solution?

Its not even respecting the default max delivery attempts of 18, it will keep re-queueing the email, some are at 27+ attempts

Did you restart Postal after changing the configuration file?

Yes, several times. still not luck

I'm not sure how this is possible to be honest, unless you've made changes to app/jobs/unqueue_message_job.rb or you're saving the config file weirdly like putting quotes around the number or something.
You could check the database and see what the attempts count is for the message?

We did an auto-upgrade and that appears to have resolved the problem.

Good to know, it may be that some code changes were reverted or something else was cleared out during that process.

is this resolved in some version?


add mediator implementation by Networks Synergy

Signed-off-by: Mikhail Lytaev<EMAIL_ADDRESS>

Great stuff.  Are you interested in doing a session providing an overview of the work for Aries WG?


FS: Create Account page, cancel button behavior

By clicking on the cancel buton on Create Account page, the tab will be closed!

the way that Create Account, Add Watch only account pages are different!
these pages should be open in a new tab!


Can not start docker 1.10.1 on Debian with kernel 4.4.2

I am newbie in docker and I was following the tutorial step by step. After installation I am trying to start the docker daemon. It says: [ ok ] Starting Docker: docker.
But the docker does not start. In /var/log/docker is:
time="2016-02-18T19:35:38.071941209+01:00" level=info msg="[graphdriver] using prior storage driver "overlay""
time="2016-02-18T19:35:38.072402194+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
time="2016-02-18T19:35:38.077121935+01:00" level=info msg="Firewalld running: false"
time="2016-02-18T19:35:38.123266732+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address"
time="2016-02-18T19:35:38.163126043+01:00" level=fatal msg="Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Failed to inject docker in PREROUTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No chain/target/match by that name.\n (exit status 1)"
Google did not help me too much with the issue. Any hint is welcome
thanks
Dodo

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see CONTRIBUTING.md.
You don't have to include this information if this is a feature request
(This is an automated, informational response)

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Could you add your docker info ? And 'uname -a' info

And how did you install docker ? which tutorial guide you follow ? Which can help us to know if doc issue or other docker code issue

docker version
Client:
Version:      1.10.1
API version:  1.22
Go version:   go1.5.3
Git commit:   9e83765
Built:        Thu Feb 11 19:09:42 2016
OS/Arch:      linux/amd64
Cannot connect to the Docker daemon. Is the docker daemon running on this host?
uname -a
Linux opahapaka 4.4.2 #1 SMP Thu Feb 18 16:33:38 CET 2016 x86_64 GNU/Linux
I followed the: https://docs.docker.com/engine/installation/linux/debian/

hi @dodiak  Could you possible manual start docker with  docker daemon -D  to add debug log here ?

Here you go. I do not think I have any strange network configuration.

FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to program NAT chain: Faile
d to inject docker in PREROUTING chain: iptables failed: iptables --wait -t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER: iptables: No c
hain/target/match by that name.
(exit status 1)

please input your
iptables -t nat -L

iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE  all  --  <IP_ADDRESS>/16        anywhere
Chain DOCKER (0 references)
target     prot opt source               destination
RETURN     all  --  anywhere             anywhere

Is this a custom kernel? Sounds like you're missing CONFIG_NETFILTER_XT_MATCH_ADDRTYPE.
You can check that you have all the requisite kernel options by running this script: https://github.com/docker/docker/blob/master/contrib/check-config.sh

Thanks, that could be the problem ... The script is very useful :)

Confirmed. My minimalistic kernel did not have all the needed features enabled. Thanks!

Thanks all for helping out. I'm going to close this issue, because this looks to be resolved. Feel free to continue the discussion after I've closed

BUG REPORT INFORMATION
docker version:

Docker version 1.10.1, build 9e83765

docker info:

Containers: 5
Running: 0
Paused: 0
Stopped: 5
Images: 81
Server Version: 1.10.1
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 102
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 3.13.0-75-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.798 GiB
Name: gns3-iouvm
ID: B3ZB:OWZQ:4HE6:MNIU:6XDT:TZSO:FOUP:C7KG:M2IL:7RAF:C4IK:3BTV
Username: ajnouri
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Provide additional environment details (AWS, VirtualBox, physical, etc.):
Physical machine

Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.4 LTS
Release:	14.04
Codename:	trusty
Linux gns3-iouvm 3.13.0-75-generic #119-Ubuntu SMP Mon Jan 11 13:49:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

List the steps to reproduce the issue:
1.docker network create --driver bridge mynet1
Error response from daemon: unable to insert jump to DOCKER-ISOLATION rule in FORWARD chain:  (iptables failed: iptables --wait -I FORWARD -j DOCKER-ISOLATION: iptables v1.4.21: Couldn't load target `DOCKER-ISOLATION':No such file or directory
Try `iptables -h' or 'iptables --help' for more information.
(exit status 2))
Describe the results you expected:
Create a user-defined bridge network, so I can connect containers to.

Generally Necessary:

cgroup hierarchy: properly mounted [/sys/fs/cgroup]
apparmor: enabled and tools installed
CONFIG_NAMESPACES: enabled
CONFIG_NET_NS: enabled
CONFIG_PID_NS: enabled
CONFIG_IPC_NS: enabled
CONFIG_UTS_NS: enabled
CONFIG_DEVPTS_MULTIPLE_INSTANCES: enabled
CONFIG_CGROUPS: enabled
CONFIG_CGROUP_CPUACCT: enabled
CONFIG_CGROUP_DEVICE: enabled
CONFIG_CGROUP_FREEZER: enabled
CONFIG_CGROUP_SCHED: enabled
CONFIG_CPUSETS: enabled
CONFIG_MEMCG: enabled
CONFIG_MACVLAN: enabled (as module)
CONFIG_VETH: enabled (as module)
CONFIG_BRIDGE: enabled (as module)
CONFIG_BRIDGE_NETFILTER: enabled
CONFIG_NF_NAT_IPV4: enabled (as module)
CONFIG_IP_NF_FILTER: enabled (as module)
CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module)
CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module)
CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module)
CONFIG_NF_NAT: enabled (as module)
CONFIG_NF_NAT_NEEDED: enabled
CONFIG_POSIX_MQUEUE: enabled

Optional Features:

CONFIG_USER_NS: enabled
CONFIG_SECCOMP: enabled
CONFIG_MEMCG_KMEM: enabled
CONFIG_MEMCG_SWAP: enabled
CONFIG_MEMCG_SWAP_ENABLED: missing
(note that cgroup swap accounting is not enabled in your kernel config, you can enable it by setting boot option "swapaccount=1")
CONFIG_RESOURCE_COUNTERS: enabled
CONFIG_BLK_CGROUP: enabled
CONFIG_IOSCHED_CFQ: enabled
CONFIG_BLK_DEV_THROTTLING: enabled
CONFIG_CGROUP_PERF: enabled
CONFIG_CGROUP_HUGETLB: enabled
CONFIG_NET_CLS_CGROUP: enabled (as module)
CONFIG_NETPRIO_CGROUP: enabled (as module)
CONFIG_CFS_BANDWIDTH: enabled
CONFIG_FAIR_GROUP_SCHED: enabled
CONFIG_RT_GROUP_SCHED: missing
CONFIG_EXT3_FS: missing
CONFIG_EXT3_FS_XATTR: missing
CONFIG_EXT3_FS_POSIX_ACL: missing
CONFIG_EXT3_FS_SECURITY: missing
(enable these ext3 configs if you are using ext3 as backing filesystem)
CONFIG_EXT4_FS: enabled
CONFIG_EXT4_FS_POSIX_ACL: enabled
CONFIG_EXT4_FS_SECURITY: enabled
Storage Drivers:

"aufs":

CONFIG_AUFS_FS: enabled (as module)

"btrfs":

CONFIG_BTRFS_FS: enabled (as module)

"devicemapper":

CONFIG_BLK_DEV_DM: enabled
CONFIG_DM_THIN_PROVISIONING: enabled (as module)

"overlay":

CONFIG_OVERLAY_FS: missing

"zfs":

/dev/zfs: missing
zfs command: missing
zpool command: missing

----------END REPORT ---------
#ENEEDMOREINFO


Implement native RSS feed into the forum

As far as I am aware, the discussion forum currently has no direct integration with RSS. This should be relatively easy to implement, and I would certainly use it.

I need this function too. Can't wait to see this in the nearly future.


Document Holesky support

Document Holesky support by updating the network option.
See https://github.com/Consensys/web3signer/pull/900.

This has been implemented here: https://docs.web3signer.consensys.net/reference/cli/subcommands#network


will not refresh() data on empty table

Hi,
I am experiencing the same problem that is described in issue #90 - namely that calling refresh on a table with no data does not call the server. I have 3 tables in one page and editing the state of one record I want it to jump into the next table. This works fine when the tables are not-empty of course. Is there something that can be done?
Regards

I think that problem was related to the pagination component, where 0 was not a legal page. I have changed the totalPages function to return at least 1.
Please pull the newest version and try again (It should pull v-pagination 0.1.1)

from my initial testing this look fixed, thanks for your prompt response @matfish2!


Updated navbar and home tag functionality in the index.html file

Related Issue
1)Arrangement of the contents in the navbar 2)home anchor tag is not working in the navbar
Fixes:  #528
Description
Arranging the contents of the navbar for better user experience and linking the text "BuddyTrail" and "home"  in the navbar to the Home section
#528 issue fixed
Type of PR

[x] Bug fix
[x] Feature enhancement

Screenshots / videos
(https://github.com/user-attachments/assets/6a0be956-a42a-442a-a209-8b688e1272d4)
Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

@poojitha-ch Due to a conflicting issue, some code was removed from the repository. We are investigating the matter. Meanwhile, please check on your end, and if your PR code no longer exists, kindly create the PR again for merging.Please Do Sync fork before then add your part in code as none of the contributions are visible in website BuddyTrail. Thank you for your understanding!


MM-56592: Remove deeplink for plugins

Summary
Removes a deeplink on '/plugins/' as it wasn't currently being used and was causing some problems.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-56592
Checklist

[X] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.

Device Information
This PR was tested on:
Screenshots

Release Note

NONE

There soon will be changes to this PR

/update-branch


sea-orm-cli migrate for Postgres database schema

PR Info

Closes #521

Adds

TBD

Fixes

TBD

Changes

TBD

@billy1624 I definitely need some assistance here 😄 I'm getting this error after making some of the changes and to be honest I don't understand why this is suggested. Should we have done certain things differently to avoid this error? 🙏

Hey @nahuakang, regarding your question on how to add schema name prefix to TableRef. I think we need to create a trait in SeaQuery where we can get and alter the TableRef of any type implemented the trait.
pub trait SchemaDefinitionStatement {
    fn get_table_name(&self) -> Option<&TableRef>;

    fn set_table_name(&self) -> &mut Self;

    fn prefix_table_name_with_schema<A>(&mut self, schema: A) -> &mut Self
    where
        A: IntoIden + 'static;
}

Also, we need a helper method to apply the schema name on the TableRef:
impl TableRef {
    pub fn schema<A>(self, schema: A) -> Self
    where
        A: IntoIden + 'static,
    {
        match self {
            ...
        }
    }
}

Hey @billy1624 So #1056 Can close this one? :) Thanks!

 Thanks for the contributions as always! :)

@billy1624 Thank you! I'll pick up where I left off on sea-query later this month :) Have too many things to handle right now outside open source 😅

Thanks!! @nahuakang Take your time :D


Change apoc.meta.schema output format (label of node = type of relationship)

Current behavior
Create a node and relationship with the same identifier
and call apoc.meta.schema:
CREATE (:STUDIO {name:'Warner Bros'})<-[:STUDIO]-(:MOVIE {title: 'Harry Poppins'});
CALL apoc.meta.schema();

Output:
{
  "MOVIE": {
    "count": 1,
    "labels": [],
    "properties": {
      "title": {
        "unique": false,
        "indexed": false,
        "type": "STRING",
        "existence": false
      }
    },
    "type": "node",
    "relationships": {
      "STUDIO": {
        "count": 0,
        "direction": "out",
        "labels": [
          "STUDIO"
        ],
        "properties": {

        }
      }
    }
  },
  "STUDIO (RELATIONSHIP)": {
    "count": 1,
    "properties": {

    },
    "type": "relationship"
  },
  "STUDIO": {
    "count": 1,
    "labels": [],
    "properties": {
      "name": {
        "unique": false,
        "indexed": false,
        "type": "STRING",
        "existence": false
      }
    },
    "type": "node",
    "relationships": {
      "STUDIO": {
        "count": 1,
        "direction": "in",
        "labels": [
          "MOVIE"
        ],
        "properties": {

        }
      }
    }
  }
}

As you can see, function had to add a  (RELATIONSHIP) suffix to STUDIO key to avoid having duplicate keys in json object. If it was CREATE (:Studio)<-[:STUDIO];, there would be no suffix. This behavior doesn't feel nice.
Feature description
Split nodes and rels to into different arrays like it is in
CALL db.stats.retrieve('GRAPH COUNTS')

Output:
{
  "relationships": [
    {
      "count": 1
    },
    {
      "relationshipType": "SAID",
      "count": 0
    },
    {
      "relationshipType": "SAID_TO",
      "count": 0
    },
    {
      "relationshipType": "STUDIO",
      "count": 1
    },
    {
      "relationshipType": "STUDIO",
      "count": 1,
      "endLabel": "STUDIO"
    },
    {
      "relationshipType": "STUDIO",
      "startLabel": "MOVIE",
      "count": 1
    }
  ],
  "nodes": [
    {
      "count": 2
    },
    {
      "count": 0,
      "label": "Person"
    },
    {
      "count": 1,
      "label": "STUDIO"
    },
    {
      "count": 1,
      "label": "MOVIE"
    }
  ],
  "indexes": ""
}

Considered alternatives
Since there are some ways of getting kinda similar data from vanilla Neo4j, maybe the best choice would be to inherit the output format from Neo4j itself.
How this feature can improve the project?
I am using Powershell and Neo4j HTTP connector and I am converting a lot of json objects into pwsh objects, and pwsh object's property names are case-insensitive.  I have a database with (:Studio) and [:STUDIO] in it's schema and it lead to Pwsh failng to interpret apoc.meta.schema json output. When I noticed that, I was curious what would happen if I'll use case-sensitive equal label for node and type for relationship, and found out function adds a  (RELATIONSHIP) suffix.
Changing format of Json output of apoc.meta.schema function will make it more machine-readable and predictive.

Thanks @Podbrushkin, I do fully agree with you. An alternative can often be to use some combination of CALL db.stats.retrieve('GRAPH COUNTS'), CALL db.schema.visualization(), CALL db.schema.nodeTypeProperties() and db.schema.relTypeProperties(). Apoc is currently under freeze of new features, and this this would be considered a new feature, so the chances that it would be prioritized anytime soon is slim I'm afraid.


more accurate exception types on argument checks

Hi,
RuntimeError() is now fired on any problem with arguments.
It is difficult to handle it in clients's code.
Could you please change it to ValueError/TypeError according to conditions?
Thank you.

PR is ready.


Migrate to Pytorch Lightning: Plot cross validation changes

This is superseded by #323

This is superseded by #323


Test on Rails 5.2 & fix mysql for older Rails

Nice!
Boy howdy is that a serious test matrix now--Travis builds look like they will go from 40 minutes (!) to  over an hour (!!). I was hoping we could drop some of those ruby versions, but as of this moment, they're all currently supported. 2.2 should EOL soon.
Perhaps we should remove the tests whose results we always discard, like 2.6 and activerecord_edge?

FYI I have an issue open w/ Travis about the 2.6 build failing https://github.com/travis-ci/travis-ci/issues/9383#issuecomment-375994207

Yeah, that build took 80 minutes, so it doubled. Do you think we should include all the ruby versions? I don't remember ever seeing a difference in how 2.x rubies performed in tests (whereas there certainly was between 1.x and 2.x, of course).

Good point. I think it can be cut down to oldest supported version. Activrecord versions are more important.


Feature Request: StatusTraffic > Graph

Hi,
Would like to request the StatusTraffic > Graph but only getting the current bandwidth IN and OUT by a local ip address. ea by <IP_ADDRESS>
Thanks!

or get all as a list with column, IP, IN, OUT

Sorry to necro this, but I was wondering if any of the current APIs offer these types of traffic stats in some manner, even if I have to parse it out in some manner? I realize that a more direct route, such as the one requested in this post probably doesn't exist yet, but perhaps there is a more 'round-about' way to obtain it?
I am unfortunately not familiar enough with it yet to know if any of the specific top-level routes might have it buried down in them somewhere (like interface, firewall, etc).
Thanks,
-MH


Make typing and posting controllable

@davidschlangen @fabiang7  We may postpone this until after version 1.1?

I can't quite recall what was meant here, but isn't this just the "block typing" feature -- which is already implemented? I mean, we can stop a player from typing, no?

Hmm, you are probably right.. I'd close this then and if there is something wr have missed here, this will be opened again.


Number of descriptors that should be returned in referrers with filter conformance test?

Hi,
I have implemented an embedded registry that is part of our product here at Avassa, and I have always run the OCI conformance test to make sure it complies. But I hadn't implemented the referrers API, so I was running the v1.1.0-rc1 release up until now.
Last week I implemented the referrers API, and tried to up the test to the conformance test to first the v1.1.0-rc3, and then the latest main, but I still failed one test, the "GET request to existing blob with filter should yield 200", specifically the number of descriptors returned (03_discovery_test.go line 340). Specifically, the test expects there to be two descriptors, and my implementation returned only one. At this point I am a bit unsure if I've understood the spec completely, or if there is something wrong with the test. Here is output from a run from my implementation:
First the unfiltered referrers GET, "GET request to existing blob should yield 200"
~~~ REQUEST ~~~
GET  /v2/foo/bar/referrers/sha256:e0307b12b5d5a18a84662fd41610689c40c2fbc4091ccf24bdbda0025822cc95  HTTP/1.1
HOST   : <IP_ADDRESS>:8888
HEADERS:
        Authorization: Basic YWxpY2U6c2VjcmV0
        User-Agent: distribution-spec-conformance-tests
BODY   :
***** NO CONTENT *****
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 200 OK
PROTO        : HTTP/1.1
RECEIVED AT  : 2023-10-02T10:01:12.129951+02:00
TIME DURATION: 617.625µs
HEADERS      :
        Content-Length: 1224
        Content-Type: application/vnd.oci.image.index.v1+json
        Date: Mon, 02 Oct 2023 08:01:12 GMT
        Server: Mona
BODY         :
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "artifactType": "application/vnd.nhl.peanut.butter.bagel",
         "digest": "sha256:6e54201a24c7de9de03f2dd1c22c56a94d7a6a1b63c873236e4eb94a2bcbb82f",
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         },
         "size": 771
      },
      {
         "digest": "sha256:8f43d76f0e445f2da55380e76cee1a415a5aa6aed69636064fd08a750319c478",
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         },
         "size": 711
      },
      {
         "digest": "sha256:b350164697784d931e533f8fe29505a4ab5b9564a9f0b8b1e87dcf42c6bdddd1",
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         },
         "size": 716
      },
      {
         "artifactType": "application/vnd.nba.strawberry.jam.croissant",
         "digest": "sha256:8a3101bad4ff22ca3356477a10f985c46416de94c6d8418e1e573c8351634678",
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         },
         "size": 781
      },
      {
         "artifactType": "application/vnd.food.stand",
         "digest": "sha256:8584abecd193777a1d21d60db596ad48143dc64ca076e20f762e008a4f8352e8",
         "mediaType": "application/vnd.oci.image.index.v1+json",
         "size": 769
      }
   ]
}

The next test does a filtered get, with the filter set to artifactType=vnd.nhl.peanut.butter.bagel, again output from my implementation:
~~~ REQUEST ~~~
GET  /v2/foo/bar/referrers/sha256:e0307b12b5d5a18a84662fd41610689c40c2fbc4091ccf24bdbda0025822cc95?artifactType=application%2Fvnd.nhl.peanut.butter.bagel  HTTP/1.1
HOST   : <IP_ADDRESS>:8888
HEADERS:
        Authorization: Basic YWxpY2U6c2VjcmV0
        User-Agent: distribution-spec-conformance-tests
BODY   :
***** NO CONTENT *****
------------------------------------------------------------------------------
~~~ RESPONSE ~~~
STATUS       : 200 OK
PROTO        : HTTP/1.1
RECEIVED AT  : 2023-10-02T10:01:12.130739+02:00
TIME DURATION: 565.416µs
HEADERS      :
        Content-Length: 350
        Content-Type: application/vnd.oci.image.index.v1+json
        Date: Mon, 02 Oct 2023 08:01:12 GMT
        Oci-Filters-Applied: artifactType
        Server: Mona
BODY         :
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.oci.image.index.v1+json",
   "manifests": [
      {
         "artifactType": "application/vnd.nhl.peanut.butter.bagel",
         "digest": "sha256:6e54201a24c7de9de03f2dd1c22c56a94d7a6a1b63c873236e4eb94a2bcbb82f",
         "mediaType": "application/vnd.oci.image.manifest.v1+json",
         "platform": {
            "architecture": "unknown",
            "os": "unknown"
         },
         "size": 771
      }
   ]
}

First of all, did I understand it right that I'm supposed to return OCI-Filters-Applied: artifactType (and not OCI-Filters-Applied: application/vnd.nhl.peanut.butter.bagel)? Second, isn't sha256:6e54201a24c7de9de03f2dd1c22c56a94d7a6a1b63c873236e4eb94a2bcbb82f the only manifest that matches? If that is the case, then I suspect the following should be done to the test:
diff --git a/conformance/03_discovery_test.go b/conformance/03_discovery_test.go
index bd54c3e..a7655ef 100644
--- a/conformance/03_discovery_test.go
+++ b/conformance/03_discovery_test.go
@@ -337,7 +337,7 @@ var test03ContentDiscovery = func() {

 				// also check resp header "OCI-Filters-Applied: artifactType" denoting that an artifactType filter was applied
 				if resp.Header().Get("OCI-Filters-Applied") != "" {
-					Expect(len(index.Manifests)).To(Equal(2))
+					Expect(len(index.Manifests)).To(Equal(1))
 					Expect(resp.Header().Get("OCI-Filters-Applied")).To(Equal(artifactTypeFilter))
 				} else {
 					Expect(len(index.Manifests)).To(Equal(5))

Or it could be that what I returned in the first GET was wrong, has anyone else implemented this?
Thanks,
/Sebastian

There are two separate artifacts pushed with the testRefArtifactTypeA artifact type value, refsManifestAConfigArtifact, and refsManifestALayerArtifact. One has the artifactType explicitly set, the other has it inferred from the config.mediaType value. It looks like you didn't pull up the config media type with the artifactType isn't explicitly set.
I'm also confused that you have the platform set in the responses. Are you attempting to parse the config blob for artifacts with unknown media types?

Ahh - thank you! I had a feeling that I had missed something - will fix.

I'm also confused that you have the platform set in the responses. Are you attempting to parse the config blob for artifacts with unknown media types?

Well, yes, I am a bit unsure about that one too. My reasoning was like this, the Listing referrers section says that the registry should return an "image index containing a list of descriptors". And the in the image spec repo, it says "Descriptors pointing to application/vnd.oci.image.manifest.v1+json SHOULD include the extended field platform". So I assumed, since the "mediaType" is "application/vnd.oci.image.manifest.v1+json" (even thought the artifactType is "application/vnd.nhl.peanut.butter.bagel") that I was supposed to at least try to figure out the platform (and yes, I do it by parsing the config blob)...

You will likely enjoy https://github.com/opencontainers/image-spec/issues/1131 😁

Indeed - I guess I just made his point :)
Thanks for the help and the pointers @sudo-bmitch and @tianon - much appreciated. I'm closing the issue, as it is obviously my bug and not a problem with the test.


Support for xlsx encoding

Summary
This PR adds a possibility to specify an output encoding and export productTypes to xlsx format.
TODO

Tests

[x] Unit
[x] Integration
[ ] Acceptance

[x] Documentation

So some of the new tests in this PR are failing on Node 6.x because of different error messages. Though I think supporting version 6 is outside of the scope @junajan if you have the time could you resolve this in a separate PR?


[Revisit] List Group components

I think we should to revisit PR #9947 for the list group component to push it into core instead.
Reasons:

Super uselful for sidebars, off-canvas, or mobile menus.
Generic Component instead of handful tasks!
Bootstrap have it.
Bulma is thinking about to have it.
Material Design Components have it!

Isn't this just a vertical menu with borders? Could we simply not have a modifier class for menu to apply the correct borders, eg 'menu-bordered' or something? Not sure this needs be another new component, but just my opinion :smile:

Dang no issue @brettsmason ...
Yup .menu-bordered combined with Active ... is an another option too ....
But there is one issue in that scenario,
List groups are mostly for menu but not just for menu!

List group can be useful for stuff's like where things like cards or panel is so popular
Example: Notification Panel

I think this may be best as part of the new prototyping classes. In fact, it's perfect for that.
A big part of the reason Foundation is popular is because it ISN'T Bootstrap or Material. Foundation gives you a much cleaner canvas to start from. If we start providing too many of these design related elements, a big reason for using Foundation is lost.

@JeremyEnglert

I think this may be best as part of the new prototyping classes. In fact, it's perfect for that.

Hmmmnnn... sounds good but i am not sure about that
@kball @rafibomb can i get a word from one of you before doing an action ??

This almost sounds more like a building block, no?

I feel this like a component rather than a prototype utility first and foremost
But I don't concur that it doesn't deserve to be in the core component sections!
Secondly I personally think for f7 to {theme up}
We would want components of material design to be a part of the components in the core section (of course as a flat design) like this one and #9645 ??

Let's revisit this for v7.


Support protocol specific topic (/ul/<apiKey>/<deviceId>)

IoT agents are going to drop the support for the legacy MQTT Topic format (/<apiKey>/<deviceId>) soon. The only supported format will be the one that includes the protocol in advance (i.e. /ul/<apiKey>/<deviceId>) as described in the documentation
This is the PR
https://github.com/telefonicaid/iotagent-json/pull/633

closed by 6d8eb1f


Allow more enum variants with custom structs in TryFromRpcValue derive macro

A RpcValue Map is parsed into the first fitting user struct in declaration order of the enum variants.

conflilcts pls.


Reduces codecov threshold

Signed-off-by: Paul S. Schweigert<EMAIL_ADDRESS>Changes
The current code coverage threshold of 80% was aspirational, and the test has been failing for so long that I think we mostly just ignore it. So this PR drops the code coverage threshold to 65%, which is about at the current level of coverage.
This should prevent any slippage in coverage, and as we add more tests we can up the threshold.
/assign @nader-ziada

/lgtm


PyTorch-backed forward simulation

This PR introduces TorchForwardSimulator, a forward simulator (for computing circuit outcome probabilities) based on PyTorch. It uses automatic differentiation to compute the Jacobian of the map from model parameters to circuit outcome probabilities. In the future we could extend it to do computations on a system's GPU, or to use PyTorch-based optimization algorithms instead of pyGSTi's custom algorithms for MLE.
Approach
My approach required creating a new ModelMember subclass called Torchable. This subclass adds two required functions, called stateless_data and torch_base. Their meanings are given below:
https://github.com/sandialabs/pyGSTi/blob/1ec6909a7f9149c4f6758f9cd46256dbbff984c1/pygsti/modelmembers/torchable.py#L18-L43
In principle, TorchForwardSimulator can handle all models for which constituent parameterized ModelMembers are Torchable. So far I've only extended TPState, FullTPOp, and TPPOVM to be Torchable; these are the classes used in "full TP" GST.
The Python file that contains TorchForwardSimulator also defines two helper classes: StatelessCircuit and StatelessModel. I think it's fine to keep these classes as purely internal implementation-specific constructs for now. Depending on future performance optimizations of TorchForwardSimulator we might want to put them elsewhere in pyGSTi.
What should come after this PR
We should compare performance of TorchForwardSimulator to MapForwardSimulator on problems of interest. There's a chance that the former isn't faster than the latter with the current implementation. If that's the case then I should look at possible performance optimizations specifically inside TorchForwardSimulator.
We should add implementations of stateless_data and torch_base to GST models beyond "Full TP" (in particular I'd like to try CPTP).
Incidental changes
My implementation originally interacted with the following evotype classes
    <class 'pygsti.evotypes.densitymx[_slow].statereps.StateRepDense'>
    <class 'pygsti.evotypes.densitymx[_slow].opreps.OpRepDenseSuperop'>
    <class 'pygsti.evotypes.densitymx[_slow].effectreps.EffectRepConjugatedState'>

When I write [_slow] in the class names above you can put the empty string or just _slow, depending on the default evotype specified in evotypes.py.
To my surprise, I found that interacting with evotypes was neither necessary nor sufficient for what I wanted to accomplish. So while I did make changes in evotypes/densitymx_slow/ to remove unnecessary class inheritances and to add documentation, those changes were only to make life a little easier for future pyGSTi contributors.

I'm giving a few quick comments here because I think this PR will actually take me some time to get through.
The main thing I am concerned and thinking about is the choice to extend the ModelMember class as opposed to adjusting the evotypes. The general purpose of the split between modelmembers and evotypes is so that we don't have to go through and implement these abstract methods in all modelmembers - we can make the change in the evotype and then any modelmember works.
It is totally possible that extending the API is the best way to do this. The TermSimulator follows a similar pattern where the API extensions are the cleanest way to do it. But I'll probably spend some time thinking about whether this is way we want to implement this. Probably a point of discussion for us in our dev meetings in the upcoming weeks.

@sserita, regarding

The main thing I am concerned and thinking about is the choice to extend the ModelMember class as opposed to adjusting the evotypes. The general purpose of the split between modelmembers and evotypes is so that we don't have to go through and implement these abstract methods in all modelmembers - we can make the change in the evotype and then any modelmember works.

Unfortunately there's no way to do this just through evotypes. Using pytorch's AD capabilities requires knowing the free parameters in a modelmember and how those free parameters map to the common parameterization-agnostic representation (i.e., representations in evotypes).

Notes from today's meeting:

I removed empty base classes for OpRep, EffectRep, StateRep. I should make sure we aren't doing type checking elsewhere in pyGSTi that would be broken by this. (There's a chance we are and it simply isn't showing up in current tests.)

@coreyostrove, @sserita, @enielse: this is ready for review.

@coreyostrove and @sserita this is ready for review.

@coreyostrove I still plan on adding proper unit tests (in contrast to the existing tests, which are really integration tests).

I'm withholding explicit approval until 0.9.13 goes out just as a reminder that we don't want this to merge in before then, and it sounds like you are still working on getting in a few tests as well.

Minor clarification, did you mean <IP_ADDRESS>?

Yes I absolutely meant <IP_ADDRESS>. Speaking of which, Tim just approved that so it will be going live as soon as all the tests pass and I get the release drafted up.
So just let me know when the tests are good on this branch and I'll give my approval also.

@sserita, @coreyostrove all tests pass, including new tests that I wrote in test_forwardsim.py. Merge when ready!


Feature: Study Overview (almost) Entirely in UI

Feature Details
The only way in which the Study Overview tab can require reactivity is if we're sharing Metric/Site input between it and the other tabs (for selection and as an input). The overall data it displays doesn't change as a result of any selections (since he purpose is to display all data).
Update the app to load this data statically. The hedging in this ticket is because other tickets might make this tab a bit more interactive, but we should still set everything up in the UI even if so.
Possible Implementation

Additional Comments

This has been implemented where it makes sense to implement it.


switch list for describe

On https://docs.bacalhau.org/demos/image-processing, using the describe command would be shorter and cleaner

We should also use bacalhau get instead of linking to cloudflare-ipfs, which can be flaky (at least for the output)

good issue for you @js-ts


cbor 4.5 - supported java version?

Has the target java version for the 4.5 release changed from 1.7 to 1.8?

The target Java version was changed to 8 from 6 because Maven no longer supports compiling for Java version 6.

Thanks! java 7 is no option?
(It's not a that big thing, but for now, I still try to support java 7 :-). )

(And just to say: thanks for the 4.5 release with the sorted map option!)

Maven still supports compiling for Java version 7; I may consider changing the target version to that in a later version of this library.

That would be great!

Addressed in version 4.5.2 (and 4.5.1).

Cool, I will pick it in the afternoon.


Any update for last 6 months?

I plan to use hilt in my new project, but this lib is still alpha and not update for 6 months, so is this lib not support or not?

Yes it is supported. It is in beta now, See this: https://github.com/google/dagger/releases/tag/dagger-2.33


createMuiTheme Bug with change of the colors

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

Current Behavior 😯

PD: I don't write english good
The error is that I am using createMuiTheme and change the properties of primary, for another color, a red color, and everything works fine, the color is set as it should be, but if I update the page, it turns blue again as if it never did. would have changed
this is how it looks without refreshing the page

and refreshing the page:

that's my code:

Expected Behavior 🤔

Steps to Reproduce 🕹

Steps:

Context 🔦

Your Environment 🌎

`npx @material-ui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @material-ui/envinfo` goes here.

Please provide a minimal reproduction test case with the latest version. This would help a lot 👷 .
A live example would be perfect. This codesandbox.io template may be a good starting point. Thank you!


React Viro don't work ios 13.5

Hello.
I install the react-viro, but it does not work.
When the camera opens, the application closes, no errors.
I installed the application again as written in the documentation, but still the same ... does not work!
ios - 13.5.1
react-native - 0.62.2
react - 16.13.1

@Hayk-Zohrabyan I had the same issue when opening the demo apps and accessing the camera however building a new app worked as expected on my iphone

@danielpettifer I tried this application on different versions of the iPhone (ios 13.5.1), it still does not work (AR). When I open the application, it automatically closes.
https://apps.apple.com/us/app/viro-media/id1163100576
https://drive.google.com/file/d/13r11WAZiGRutIl7sVj_y4cbHI8a9Z3-D/view?usp=sharing
The same thing happens when I open a new application React Viro.

because UIWebView https://github.com/viromedia/viro/issues/852

I just upgraded my device to 13.5.1 and I am using react-native 0.61.5, no issues on my end.


View is across batch instances?

https://github.com/xinyandai/string-embed/blob/61e03475ad8d5b28db6a67e85ffd2473e60a421e/networks.py#L71-L72
It seems to be this code is making x to mix values from different batch instances. Instead, I think it should be x = x.view(x.size(0), self.mtc_input, -1)

It seems that the code runs correctly

I guess the author had tried several versions of the data structure.
and the final version lacks cleanup, which works correctly but is not very elegant.

Thanks, I understand the code works, I've used it too.
But I guess it's not desirable to mix batch instances.

So sorry for the delay. @fjsj
Thank you for your explanation and verification. @aalennku
The input strings are shape of (N,  C, M),

if mtc_input is disabled:

1D-Conv-s with one channel are applied on each row of the input strings  (shape of 1xM).
we reshape input into shape of (N * C, 1, M)

if mtc_input is enabled:

1D-Conv-s with $C$ channels are applied on each input string (shape of CxM).
we reshpae input into shape of (N, C, M)

The following codes are equivalent:
x = x.view(-1, self.mtc_input, self.M)

 N = s.size(0) # number of batchse
 C = ...            # number of distince characters
 M = ...            # maximum string length
 if mtc_input: # .i.e., self.mtc_input == 1
     x = x.view(N * C, 1, self.M)
 else:             # , i.e., self.mtc_input == 1
     x = x.view(N, C, self.M)

In the paper, we use the version that mtc_input is disabled.


fix: ignore irrelevant request listeners during response patching

emitter.untilIdle awaited all listeners for a certain event. When the listener resolution is nested, for example, like during response patching, this caused for untilIdle to never resolve, pending infinitely.
- request A
  - "request" listener (pending)
    - request B (called within the "request" listener)
      - "request" listener (the same)
        - interceptor waits `untilIdle` but the listeners Promise state is:
[
// The first "request" listener that awaits the child requests
// to get resolved.
Promise<pending>,

// The child (nested) request. Cannot be resolved because it waits
// for the parent (first) request to be resolved.
Promise<pending>
]

Released: v0.16.3 🎉
This has been released in v0.16.3!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


Add java client for the rest api

Please consider adding a java client for the standalone rest api into this project.

You can programmatically manipulate the proxy from Java code by using BMP in "embedded mode". Instructions are available in the README.md file.
Once we upgrade to the latest Resteasy and JAX-RS 2.0, creating a client should be straightforward.

there was a client for the 'old' version... I will adopt it to the newer one.. (as it might not work anymore)
see: https://github.com/roydekleijn/BrowsermobHTTPRESTclient

Thanks! I'm looking forward to the day when we have a JAX-RS 2.0 compatible API and you no longer need to maintain this manually.

@jekh any update on this?.. is there any official rest client for BMP?..

Not yet. It's the "next big thing", but it'll at least a few months out.

Update: work is underway, but the new REST API and client won't be ready until the fall.

Hi, any update on such client?


Fix partial messages handling

Kafka 2.0 introduced chunked message down conversions which might
produce partial messages at the end of the set. These partial messages
are not well formed beyond offset and length, so they might cause
strange decoding errors down the line.
This fix makes lengthField a dynamicPushDecoder so it checks that
the packetDecoder has at least that many bytes. It fixes the problem
above and I think it's a more robust check in general.
Fixes #1144

Thanks for digging into this! I've pushed a test branch on CI but still seeing failures https://travis-ci.org/Shopify/sarama/jobs/415607362?

Test branch is 🍏 , could please chery-pick https://github.com/Shopify/sarama/commit/3de182b43ce4e6ac1599844866957655ba7d32a2 to enable Kafka 2.0 on CI?


SomePythonThings.WingetUIStore version 0.4

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Yes it looks like, but i don't know what happened, because i opened only one PR


Facing error during re-run the same terraform script

Provider Version
0.22.0
Terraform Version
1.0.11
Describe the bug
Basically, Terraform script is assigning role(SYSADMIN) to the user, when I run the script for the first time, its executed successfully and the role(SYSADMIN) is assigned to user as expected, but when I re-run the same script its showing below error:
Error: 003042 (42501): SQL compilation error:
│ Role 'SYSADMIN' is a system object. REVOKE cannot be performed.
│
│   with snowflake_role_grants.grants,
│   on grants.tf line 1, in resource "snowflake_role_grants" "grants":
│    1: resource "snowflake_role_grants" "grants" {
Expected behavior
A clear and concise description of what you expected to happen.
Code samples and commands
resource "snowflake_role_grants" "grants" {
provider  = snowflake.security_admin
role_name = "SYSADMIN"
users     = [upper(var.username)]
}
Additional context
Add any other context about the problem here.

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


List format on FileInfo and DirectoryInfo on Unix-like systems shows Mode property instead of UnixMode, unlike table format

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
On Unix-like systems, if a FileInfo or DirectoryInfo object is formatted as a list by Format-List, it displays the Mode property, but if it is formatted as a table, e.g. by Format-Table, it displays the UnixMode property.
Expected behavior
PS /> gi . | ft

    Directory:

UnixMode   User             Group                 LastWriteTime           Size Name
--------   ----             -----                 -------------           ---- ----
drwxr-xr-x root             root               11/10/2021 00:23           4096 /

PS /> gi . | fl

    Directory:

Name           : /
CreationTime   : 11/10/2021 00:23:56
LastWriteTime  : 11/10/2021 00:23:56
LastAccessTime : 05/02/2022 10:56:57
UnixMode       : drwxr-xr-x
LinkType       :
Target         :

Actual behavior
PS /> gi . | ft

    Directory:

UnixMode   User             Group                 LastWriteTime           Size Name
--------   ----             -----                 -------------           ---- ----
drwxr-xr-x root             root               11/10/2021 00:23           4096 /

PS /> gi . | fl

    Directory:

Name           : /
CreationTime   : 11/10/2021 00:23:56
LastWriteTime  : 11/10/2021 00:23:56
LastAccessTime : 05/02/2022 10:56:57
Mode           : d-r--
LinkType       :
Target         :

Error details
No response
Environment data
PS /> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.2.1
PSEdition                      Core
GitCommitId                    7.2.1
OS                             Linux 5.16.2 #1-NixOS SMP PREEMPT Thu Jan 20 08:12:22 UTC 2022
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Visuals
No response

You can edit output format and  update default with custom one. Update-FormatData

Yes, but I think that should be the default wherever UnixMode is already the default.

You can customize it, but really the properties for list and table should be in sync - there is no reason for them to be different.
It looks to me like the table was changed for Unix and the list was overlooked.

As an example of the customization, I use Update-TypeData to get the table output to remove the @AD.COMPANYNAME.COM from both User and Group PSScriptProperties since it was causing gci ouput to wrap.

@iSazonov   Do we know a reason why the list should show a different mode from the table ?
https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/FormatAndOutput/DefaultFormatters/FileSystem_format_ps1xml.cs  has an #if unix block for tables at line 44,  but there isn't one for lists.
If I'm right and this was by omission not by design , then should be marked as a bug not an enhancement.  It's one of those mods where adding a test is much more work than making the change :-)

@iSazonov Do we know a reason why the list should show a different mode from the table ?

It was an enhancement from @JamesWTruher for table format. Anybody could pull a PR to enhance list format too.