add rpc method getblockheader

Add the rpc method "getblockheader" with supporting integration unit test from NBitcoin.  Test CanGetBlockFromRPC() assertion is currently failing but not sure what I'm doing wrong - need another set of eyes to see what I missing.

Check bitcoin code directly, this is more reliable than the doc.
https://github.com/bitcoin/bitcoin/blob/041dad94b047313a17edb0324742cf80cfd550f1/src/rpc/blockchain.cpp#L629

From the core reference just use the time property is fine
https://github.com/bitcoin/bitcoin/blob/041dad94b047313a17edb0324742cf80cfd550f1/src/rpc/blockchain.cpp#L91

@mikedennis whats the progress on this?

Hi @mikedennis, is this ready for review? apart from the median time, there are a few items in TODO.

@dangershony @bokobza Still needs some work and clean up but I still haven't figured out why the unit test is not passing. I get a different hash back than the genesis. If anyone knows what I'm doing wrong and can point me in the right direction, I'll finish this baby off!

You're not getting the hash you're expecting because the hash is calculated from the BlockHeader's "value" itself.
If you look at Block.cs line 177 you'll see
h = Hashes.Hash256(this.ToBytes());
this being a BlockHeader.
What I suggest is for you to change this test to Assert all the fields in the BlockHeader, add what's missing in the BlockHeaderModel and leave the hash for last.
Does that make sense?

@bokobza Ah yes that makes sense. It's because I haven't added all the fields yet. Sounds good! Thanks for the help.

Nice one, I'll have a look soon.

@bokobza Thanks for the feedback. I think I've got the issues sorted out in my latest commit.
Regarding the questions around BlockHeader.Bits serialization. Another alternative would to make this https://github.com/MetacoSA/NBitcoin/blob/9843ab333f93394d70287bec3f3754610abe7897/NBitcoin/Target.cs#L28 NBitcoin method for GetBytes() public and then I could use it directly.  It was a very simple method so I just copied it into the Model. There is definitely some funkiness in the way Bitcoin is serializing this but I believe I am now doing it correctly as the hashes do match up now. Let me know if you see a better way or want me to modify access to the NBitcoin method  instead.

Can to you not just do a normal set
this.Bits = blockHeader.Bits

@dangershony I wish it was that simple! The Bits.ToString() gives you a uint256 encoded string but the Target constructor needs a "compact" encoded string. See here https://github.com/MetacoSA/NBitcoin/blob/9843ab333f93394d70287bec3f3754610abe7897/NBitcoin/Target.cs#L43

Do I need to change something in NBitcoin to make it more easy?

Lovely, thank you @mikedennis.
Thanks @NicolasDorier I think we're OK for now :-)


feat: add exec command

keeper/exec command will create a temporary scrip file containing the command to execute.
Then, it will run this script using ksm exec.
~Two workarounds are necessary:~

~we need to provide --capture-output: https://github.com/Keeper-Security/secrets-manager/pull/244~
~we unset CIRCLE_PROJECT_REPONAME env var: https://github.com/Keeper-Security/secrets-manager/issues/243#issuecomment-1079700528~

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:dce41698ff3125252737dd741e39171f6884b9cc

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:669477afcadd744ab37cdc8efbd27888713baceb

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:2c9fb12ccbebde43f26a9c82516e9a185d628cba

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:44ef51982b87c5cbe2c16ffd456f8d51703a0a7c

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:4da06db1ea05655b21ed0468de436c225c9240d6

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:30f2dcf0c5a721a6e1250b50b8f4bf12b68398eb


[Azure Machine Learning Service] application/octet-stream instead of application/json

Nowadays the only type of data accepted as an argument for AzureML Deployed Webservices on AKS are JSONs (application/json)? Is it possible to send binary data to the webservice (application/octet-stream)?
For example: if I want to make an Object Detection Webservice, I would prefer to send the binary images without any base64 or ASCII encoding, because the encoding would enlarge the body of my request.
Originally posted by @nansravn in https://github.com/MicrosoftDocs/azure-docs/issues/16485#issuecomment-428301599

Thanks for the question! We are investigating and will update you shortly.

@YutongTie-MSFT - please assign to @Blackmist thank you.

@nansravn Support for this is coming. I'll let you know once this is enabled and we have an example.

#please-close


Search editor: review potential unsafe editor resource usage

Background: the search editor overrides the editor open behaviour for certain files. It takes the resource of the editor here:
https://github.com/microsoft/vscode/blob/46ba25e11d30a9d7477e6c014f7fbcee679d54bc/src/vs/workbench/contrib/searchEditor/browser/searchEditor.contribution.ts#L78-L78
And then later uses that for parseSavedSearchEditor and as backingUri.
The editor.resource property for files is the canonical form of that URI and must not necessarily match with the form it had originally. Here is a good example:

an extension triggers to open an editor /FOO/BAR/file.txt
the editor opens and from now on /FOO/BAR/file.txt is the canonical form of that URI
the user clicks on /foo/bar/file.txt in the explorer (assuming that /foo/bar is actually the casing on disk)
at this point editor.resource will be /FOO/BAR/file.txt because that is still the canonical form

To circumvent this, EditorResourceAccessor utility was added with methods to get the original URI (/foo/bar/file.txt) as well as the canonical one (/FOO/BAR/file.txt).
This issue is to review that you understand the problem and your usage is safe. I am not entirely sure how the editor resource is later used so maybe you can clarify. Bottom line:

canonical form is fine for any file access (e.g. via node.js) and should be used when checking for identity or comparing editors
original form should be used e.g. when you show a label to the user

Pushed code to use original uri in display contexts, though I'm not sure it's possible to reach this state -- an extension can only open text documents, passing the uri of a .code-search to vscode.window.showTextDocument(await vscode.workspace.openTextDocument(uri)) opens up the raw text version rather than going through the editor open overrides.


Project-local custom reporters

According to the wiki, you can

define custom third-party reporters within your own test suite, or by using npm modules

The second part ("reporters that are npm modules") works fine, but when I try to use a project-local custom reporter, I'm forced to specify the path relative to node_modules/mocha/lib/.
That is, supposing I have a custom-reporter.js in the root of my project, running
node_modules/.bin/mocha --reporter=./custom-reporter.js

fails, but
node_modules/.bin/mocha --reporter=../../../custom-reporter.js

works.
It would instead be nice if the --reporter option were relative to the current directory for non-npm reporters.
Here's the relevant line that needs fixing. It would need to fall back to something like path.resolve(process.cwd(), reporter). I can try to put together a PR, but I want to make sure I'm not missing something.

@cletusw Sounds about right.  Just nest another try/catch with path.join(process.cwd(), reporter) or something.  path.resolve() should work as well.

Will do.

@boneskull On a related note, what's the difference between that code in lib/mocha.js and https://github.com/mochajs/mocha/blob/2a510800bd13f095ebea3b5ae6bf6e25206d8628/bin/_mocha#L209-L220?

That code is causing errors after my fix, but it looks like Reporter is not actually used anywhere. Does that sound right?

This feature has been released in v3.3.0! 🎉

I can't get this to work with v4.0.1.

Try removing any leading ./; see https://github.com/mochajs/mocha/pull/2659#issuecomment-316465350 for details (it's been a while but I think my recommendations # 1 and # 2 would cover getting this fix to actually work, while # 3 and # 4 expand the idea to other similar issues).


Create a seed

Contexte / Problème
When setting up the database, it takes a lot of time to setup an environment :
create a User, to validate with (confirmed_at...), a partner...
Proposition
Create a DB seed, so developers could have a DB populated when starting to contribute
Priorité (Requis)
Ajouter un label Priorité
P3

There is the populate rake task who create bunch of users, and one vaccination center.
I think this rake task may be need to be developed more

Ok Nice!
Maybe We could extract the code of this rake task to use it in the rake task and in the seed ?
Where should we extract it ? In a helper ? A service ?

Hello,
As newbie,  I maybe I can try this .
I just noticed something in the rake task : there is an error on password field
actually the users table hasn't password field .


AsNavFor doesn't work with version 0.23.0 and higher

I have tried to use the code(from here), but it didn't sync well. When i downgrade it to 0.21.0, it works great
import React, { Component } from "react";
import Slider from "react-slick";

export default class AsNavFor extends Component {
  constructor(props) {
    super(props);
    this.state = {
      nav1: null,
      nav2: null
    };
  }

  componentDidMount() {
    this.setState({
      nav1: this.slider1,
      nav2: this.slider2
    });
  }

  render() {
    return (

Slider Syncing (AsNavFor)

First Slider

        <Slider
          asNavFor={this.state.nav2}
          ref={slider => (this.slider1 = slider)}
        >

1

2

3

4

5

6

        </Slider>

Second Slider

        <Slider
          asNavFor={this.state.nav1}
          ref={slider => (this.slider2 = slider)}
          slidesToShow={3}
          swipeToSlide={true}
          focusOnSelect={true}
        >

1

2

3

4

5

6

        </Slider>

    );
  }
}

I encountered same problem here. I downgraded install to 0.21.0 but still not working. How can I fix it?

same problem here.   Looks like the two sliders only sync once after 2 clicks

and yes, just downgraded to 0.21.0, and it work perfectly

Yes. version 0.21.0 it's working properly with sync sliders but 0.23.2 it's not. Changing slides every second click.

Yes. version "0.23.1" it's working properly with sync sliders but 0.23.2 it's not. Changing slides every second click.

Tested on 0.23.1, I still have the same problem, slider is skipping every second item. On 0.21.0 work OK.

Same here, working correctly only on 0.23.1 version.


Updated layout

Added loading progress bar,
Added appbar to layout
updated all dimensions using appbar height as reference to be replicable

Looks very nice, :)


Update migration-guide-5.x-6.x.md

Add updates to TwilioVoice#handleNotification method.

@rapito
The method signature was updated in 5.0.0 release.

Oh, my bad.
I was updating from an older version, so probably this same change should be added to the migration guide 4.x-5.x then?


Improve visual treatment for indicating changed variables in debug viewlet

As we discussed, we should explore different visual treatments for indicating the last changed variable in the variable window. Currently changed variables are indicated by colouring the value red but this can clash with the way that strings are represented. Some of the ideas we discussed are

Bolding the name and/or value
Highlighting the background then fading to a specific opacity
Changing the colour of the name and/or value

Below is the visual treatment that we agreed on today (please disregard the inaccurate changes in variables).  I will be pushing these visual changes to master branch soon.

Design Rationale

Fading after a fixed amount of time emphasizes a change has occurred (while avoiding a misrepresentation that a change is in progress)
Helps to visualize the order and timing in which each variable has been evaluated… may also help solving race condtions in ansynchronous code.
Chrome DevTools uses this approach (combined with inline REPL)

Reopening until I have a commit to update this issue with

Resolved 1132f27e22b59b5bc4c57a61d9be23963354f05a

Although to make it flash on each change, we would need additional logic to re-flash a variable if its changed more than one time in a row.  For instance, we could apply a .changing and .changed class.


UD tree pipeline

The "links" mentioned in #4 are still very necessary; the treebanks work ok on the Parrish translation, less so when we're in the "card" format of from Odyssey.
One other thing to try may be to run the "large" text parts (chapters, etc) through the pipeline and then use selectors (https://www.w3.org/TR/annotation-model/#selectors) to target the original passages.

I'm merging this as-is to unblock #7; we may revisit some of the structure of these pipelines in future work.


External images should not be encoded

When you embed an external image
<img src="http:/i.creativecommons.org/l/by-nc-sa/3.0/it/88x31.png">
gulp-img64 returns an error with
Error: ENOENT, no such file or directory
It should instead ignore the external images.

@matteosuppo I think you have a typo in the src, you have http:/ (single slash) instead of http:// (double slash)


Better records.js bundle and other related fixes

Remove the cloudconnector from a record view
Rename cloudconnector icon to its correct name
Reduce records.js bundle file size by 100%
Massive JavaScript refactoring and bug fix as the tabs were not properly working when using the history.back() button of the browser
Fixes tind/base-overlay#92

@jirikuncar ping, thanks.

@greut remove -> removal, sykdrive -> skydrive + labels for release notes so people know what has changed and was fixed. Thanks

@jirikuncar
Improved features
-----------------

- Refactors the record.js code handling tabs.
- Reduces the records.js bundle file size.

Bug fixes
---------

- Fixes the information tab of a record doing nothing when another tab
  had been loaded.

Notes
-----

- Removes the cloudconnector modal view from a record.

@greut can you also improve the titles of commit messages? Thanks

better?


wrong counting of found frequencies

I just had the strange situation that one frequency was counted twice. So the number of ensembles was 1 too high.

Thanks for reporting. I use band scan very rarely so I have never had this issue. Is it reproducible with that ensemble? I should have recording of Austrian Mux from Insbruck from February this year so I will check it if there is anything specific that might cause the issue.

I have an idea, what about ECC, when it is received only some frames too late? Will the app discover two muxes then??
8A is weak and might cause some issues here.

You are right, it could be releated to ECC in some way.

ECC is handled in the library and it does not generate log.

I'll close it, this seems to happen very very rarely. Could not reproduce it in the past months.


Add option to only show first and last x axis

Summary
It would be awesome if we could enable an option to only show the first and last value on the X-axis. However, this would still show the x axis values on hover, but would prevent clutter.
API Changes
{
  xaxis: {
     showType: 'boundary' // defaults to 'all', allows for 'even', 'odd' etc
  }
}

Intended Use Case
I use ApexCharts heavily in my analytics SaaS (Analyse) and I often have many data points. I'd like to be able to only show the first and last, but still show them on hover.
Current Dash:

I'd also be happy to donate (GitHub Sponsor) in return for adding this.


Add STATUS column for pc endpoint Command

Like this:
istioctl proxy-config endpoint details-v1-5b7f94f9bc-wp5tb --port=443
ENDPOINT              STATUS      CLUSTER
<IP_ADDRESS>:443       HEALTHY     outbound|443||istio-ingressgateway.istio-system.svc.cluster.local
<IP_ADDRESS>:443       HEALTHY     outbound|443||istio-galley.istio-system.svc.cluster.local
<IP_ADDRESS>:443        HEALTHY     outbound|443||istio-sidecar-injector.istio-system.svc.cluster.local
<IP_ADDRESS>:443        HEALTHY     outbound|443||istio-egressgateway.istio-system.svc.cluster.local

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: nmittler
If they are not already assigned, you can assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @ayj @liamawhite

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ayj
If they are not already assigned, you can assign the PR to them by writing /assign @ayj in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@liamawhite Yeah, I think that the status filter will be helpful, have added and also added the test for status filter. PTAL :)

/approve
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: liamawhite
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS [liamawhite]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


How to find the model information

Thanks for your algorithm.
Is there a way to look into the model? I'm quite confused how to find the convolution functions in the code.

Do you mean the convs for patch embedding? It's here. The model's structures are inside the core/FlowFormer.

Thanks so far.
But it's more of a general problem of understanding what happens if you - for example - call module(image1, image2)

Maybe this is the code entry you are looking for?


Getting a RichTextDocument from plain dictionary data (not fetched with Contentful SDK)

I'm trying to use this library to render rich text from Contentful, but client side, I'm not using the Contentful SDK for retrieving data, instead I'm using Apollo reaching our own graphql server (Hasura with Contentful integration). Because of that, I'm receiving the content as a swift dictionary ([String: Any?]), and I wonder how to create the RichTextDocument from it.
Could you give me some directions here?

I do not think that the library was designed just to cherry pick stuff from it. But your best and probably the only way in the current state would be to parse the dictionary you receive into a json string and then decode that into the object. Here is a generic example:
let richTextDocumentDictionary: [String: Any?] =
let encoder = JSONEncoder()
if let jsonData = try? encoder.encode(dic) {
if let jsonString = String(data: jsonData, encoding: .utf8) {
// You got that into the string json
// Now lets encode that into the object of rich text document
let jsonData = jsonString.data(using: .utf8)!
let richTextDocument = try! JSONDecoder().decode(RichTextDocument.self, from: jsonData)
}
}

Thanks it's working that way!


Suggestion for executing templates with location/path as a variable

I'm trying to think of a way to execute templates based on router parameters. If I have a large collection of templates arranged in a folder structure, I'd like to be able execute one via the path without explicitly wiring everything up before hand. I'd love to see an option on qtc to generate a map of function pointers where I could look for a template at a particular path, execute it if it exists, or choose a template in a parent location if it doesn't. (hope that makes sense, and I'm assuming that the template all need to take the same args) Eventually, I may actually store the templates in a database and write them out to the file system as part of the build process before invoking qtc. This would give me back some of the advantages of dynamic templates while enjoying the speed and efficiency of quicktemplates.

@stevielj did you fixed this?
I think I need something similar here: https://github.com/valyala/quicktemplate/issues/58, right @valyala?

Yes, it is quite similar to the issue described in #58 .
Unfortunately the solution proposed by @stevielj looks quite complicated from user PoV. That's why it isn't implemented yet :(


CombinationsSequence should be a Collection

It's multipass (like almost every other Sequence in practice).  Not being a collection limits its applicability in silly ways.

@dabrahams Could you give some examples of the limitations that you're running into here?
IIRC, the reason that CombinationSequence is only a sequence is that its iterator stores and mutates a single copy of the base collection's indices as it iterates. By contrast, a collection would need to provide an index type that either stores a separate copy of the indices (potentially very heavyweight) or stores just a position, and then recalculates the indices when used (which should be doable, but might be costly). While the Collection protocol doesn't explicitly rule out such a heavy index type, it's very different from the way most collections work, and having O(N) work happening in each subscript would probably be unexpected for users.
That said, CombinationSequence might already be falling down on the efficiency job. It looks like the iterator currently copies each combination into a new array, instead of using a collection wrapper to combine the base collection and the array of indices. Such a wrapper would be independently useful, as well (and indeed I thought we already included it):
let numbers = [10, 20, 30, 40, 50]
for x in numbers.indexed(by: [4, 2, 0]) {
    print(x)
}
// 50
// 30
// 10

Could you give some examples of the limitations that you're running into here?

I didn't run into a limitation, but I know such limitations exist.  It's the whole reason I wrote Zip2Collection: there are algorithms that are defined only on Collection because it is multipass.

IIRC, the reason that CombinationSequence is only a sequence is that its iterator stores and mutates a single copy of the base collection's indices as it iterates.

That's no reason it can't be a collection, as you yourself know well and  this implementation demonstrates.

having O(N) work happening in each subscript would probably be unexpected for users.

I don't know what your N is in this case; it's certainly not the length of the resulting collection, which is what people usually mean when they say O(N).
The work of dereferencing this thing is proportional to the data footprint of the elements you get, which is no worse than someStrings.lazy.map($0 + ".").
"It's surprisingly expensive" is subjective and not a reason for non-conformance to a protocol.  The implementation either meets the efficiency bounds (and we even play loosey-goosey with that criterion in places) or it does not.


[Remote Store] Use lastRefreshedCheckpoint as a refresh checkpoint in remote segment store

Is your feature request related to a problem?

Today, we use maxSeqNo from refreshed segments as a refresh checkpoint in remote segment store.
But the Engine.getMaxSeqNoFromSegmentInfos method does not guarantee returning seq number in monotonically increasing order.
Take following example (maxSeqNo is the return value of Engine.getMaxSeqNoFromSegmentInfos):

Index 100 docs, maxSeqNo = 99
flush
Delete last 10 docs that were ingested in step 1, maxSeqNo = 109
flush and forcemerge
maxSeqNo = 89

This can result in data loss as remote translog may have purged data for the sequence number that is being referred by remote segment store.

Correctness and data integrity guarantees by using lastRefreshedCheckpoint

TBD

This task is completed in 2.10 using following:
final long maxSeqNo = ((InternalEngine) indexShard.getEngine()).currentOngoingRefreshCheckpoint();


Handle special case of NaN's to avoid NumberFormatException's

Handle special case of NaN's to avoid NumberFormatException's that can result in 500 error conditions related to metrics. See #464. This does not address the reason for those NaN's but at least prevents 500 errors to be returned. Some new tests added.
Signed-off-by: Santiago Pericas-Geertsen<EMAIL_ADDRESS>

Might be a good idea to make String.valueof(Double.Nan) into a constant.
What does Prometheus etc. do with a "NaN" value?

@batsatt Fixed constant suggestion. From what I read, Prometheus "handles" NaN's, as in it does not throw exceptions. Regardless, the main objective here is to prevent a Helidon-based service to return 500.


Support for Macs and iOS devices compatibility on the framework

When accessing the Shesha site on Safari, an error occurs. Ensure compatibility with Macs and iOS platforms.

Excluding support for old versions of Safari >7years old

What I've observed while testing with BrowserStack is that the latest top three versions of Safari (17, 16, and 15) are functioning properly. However, versions 14 and earlier either render the site inaccessible or continuously initialize without loading


TypeResolverVisitor computes some generic function types incorrectly when using new analysis driver

Consider the following code (from test_infer_mixin_with_substitution_functionType_new_syntax):
abstract class A<T> {}
class B {}
mixin M<T, U> on A<T Function(U)> {}
class C extends A<int Function(String)> with M {}

When this is analyzed using the analyzer new analysis driver, the AST nodes for A<T Function(U)> and A<int Function(String)> are both incorrectly assigned the type A<dynamic>.  This is happening because the DeclarationResolver class doesn't properly assign a type to all GenericFunctionType nodes, only to those that it can find an associated type for in the element model.
This is causing TypeResolverVisitor to store incorrect types in the element model, leading to bogus errors being reported.  I will shortly send out a workaround that prevents the element model from being corrupted; a more involved fix will be needed to fix the types stored in the AST.

Workaround to avoid storing incorrect types in the element model: https://dart-review.googlesource.com/c/sdk/+/76441


Performance of validation of JSON objects with very long lists of JSON objects within is very, very slow.

It seems that validating an object with a list of 1000 objects with uniqueItems property takes time in the order of one second to complete.
This may be verified by creating an object such as:
{
  "test": [
    {"key1": "1", "key2": "1", "key3": "1", },
    {"key1": "2", "key2": "2", "key3": "3", },
    ...
    {"key1": "1000", "key2": "1000", "key3": "1000", },
  ]
}

and validating it against an schema such as:
{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "definitions": {
    "dataType": {
      "type": "object",
      "properties": {
          "key1": "string",
          "key2": "string",
          "key3": "string"
      }
    }
  },
  "type": "object",
  "properties": {
    "test": {
      "type": "array",
      "uniqueItems": true,
      "items": {
        "$ref": "#/definitions/dataType"
      }
    }
  }
}

One solution to this is already verified for forked project https://github.com/kobil-systems/jessy
The solution is here: https://github.com/kobil-systems/jessy/pull/7
I have prepared already a patch to this project and would love to have the opportunity to submit a pull request with this proposal.

Hi,
do you have any idea if the performance is not great because of nested loop
lists:foldl( fun(Item, RestItems) ->
                     lists:foreach(...

or because of slow comparison function jesse_validator_draft4:is_equal/2?
I have at least one problem with the implementation you have in your fork - it uses sets module with {version, 2}, which is not available on OTP versions prior to, I think, 24. Jesse currently supports OTP versions starting from 19. I would suggest using lists:usort instead.

The current nested loop seems to be slightly optimized quadratic complexity (it needs 45 calls to is_equal for list of 10 elements, 1225 for 50 elements and  4950 for 100 elements), which is indeed far from optimal =(
Are you sure your jesse_lib:normalize_and_sort is equivalent to is_equal? I can try to write a property-based test...

Hi,
do you have any idea if the performance is not great because of nested loop
lists:foldl( fun(Item, RestItems) ->
                     lists:foreach(...

or because of slow comparison function jesse_validator_draft4:is_equal/2?
I have at least one problem with the implementation you have in your fork - it uses sets module with {version, 2}, which is not available on OTP versions prior to, I think, 24. Jesse currently supports OTP versions starting from 19. I would suggest using lists:usort instead.

My impression is that the main reason is the nested loop.  If I am not wrong that means this search is O(n^2), while creating a set, which should be creating a hash for each element and then comparing, is O(n).  The observation is that the time that it takes grows more than proportionally with the number of elements in the list.

I have at least one problem with the implementation you have in your fork - it uses sets module with {version, 2}, which is not available on OTP versions prior to, I think, 24. Jesse currently supports OTP versions starting from 19. I would suggest using lists:usort instead.

Thank you very much for the suggestion!  I have no problem at all in changing the implementation, that is in fact one of the reasons to propose this change here.  Is it enough if I create a new pull request in the child project using lists:usort after testing it? Or do you want to see the new proposals in any other way? Would it be possible for me to get permissions to create a pull request here and discuss the implementation there?

The current nested loop seems to be slightly optimized quadratic complexity - 0.5 * x^2 - 0.5 * x, which is indeed far from optimal =(
list len	num calls to is_equal
10	45
50	1225
100	4950
500	124750
1000	499500
http://tryerl.seriyps.ru/#id=fbb4
Are you sure your jesse_lib:normalize_and_sort is equivalent to is_equal? I can try to write a property-based test...

I am going to try that is_equal thing.  I have to say that my knowledge of the library is very little at the moment, so there might be many options that I just didn't considered for lack of knowledge. It was just a matter of solving this problem with what I could do at the moment, since it was really dangerous as it was.

Hi,
do you have any idea if the performance is not great because of nested loop
lists:foldl( fun(Item, RestItems) ->
                     lists:foreach(...

or because of slow comparison function jesse_validator_draft4:is_equal/2?
I have at least one problem with the implementation you have in your fork - it uses sets module with {version, 2}, which is not available on OTP versions prior to, I think, 24. Jesse currently supports OTP versions starting from 19. I would suggest using lists:usort instead.

After looking a bit into this, my proposal is to just check the OTP version and use {version, 2} only when available.  This is anyway an optimization that, as far as I know, it only matters in terms of memory used.  The improvement in speed is there with and without this parameter, but I would prefer to keep it for OTP versions 24 and higher. My idea is to do this with a macro, such as this one:
-ifdef(OTP_RELEASE).
  -if(?OTP_RELEASE >= 24).
  %% OTP 24 or higher
    -define(SET_FROM_LIST(List), sets:from_list(List, [{version, 2}])).
  -else.
  %% OTP 23 or lower.
    -define(SET_FROM_LIST(List), sets:from_list(List)).
  -endif.
-endif.

Are you sure your jesse_lib:normalize_and_sort is equivalent to is_equal? I can try to write a property-based test...

I am working now in that property-based test.  Thank you very much for this idea.  If you have a suggestion for a "Generator" for lists of JSON objects, that would be awesome.

If you have a suggestion for a "Generator" for lists of JSON objects, that would be awesome.

I actually have https://gist.github.com/seriyps/ffe0f5f5ba270fc4dd395208718e84d3
Maybe not perfect and would need to be wrapped to proper_types:list

This looks awesome!  Thank you very much, I hope to have something working in a day or two.

Hello again @seriyps !
I would like to propose the changes in this branch: https://github.com/kobil-systems/jessy/pull/8/files
Please tell me if this looks ok or any change in direction is needed.
The ideas behind the changes are the following:

is_equal is moved to jesse_lib and a parameter is added so that it behaves different for draft 3 and for draft 4. This saves from repeating many lines of code that are equal and makes it much more easier to spot the change between the two behaviors.
A module for property based testing is added. The intention is only to verify that "normalization" produces objects that are equal in terms of the is_equal function.  Maybe this is not the best way to check if normalization works, please comment.
Normalization was also fixed in order to take into account the difference between draft 3 and draft 4 comparisons.
The Erlang sets version {version, 2} is only used if running on OTP 24 or higher.

Please tell me what you think about all this.

@germanblanco I added one coment regarding big integers in your jessy PR. I think it would be a bit easier if you will open a PR towards this repository, so we can continue the discussion there.

is_equal is moved to jesse_lib and a parameter is added so that it behaves differently for draft 3 and for draft 4. This saves from repeating many lines of code that are equal and makes it much more easier to spot the change between the two behaviors.

I see in your PR you made v3 and v4 versions of es_equal to behave the same way even though there was a difference in how they compare integers with floats. I might need to check the specks to see if it's ok.

A module for property based testing is added. The intention is only to verify that "normalization" produces objects that are equal in terms of the is_equal function. Maybe this is not the best way to check if normalization works, please comment.

:+1:
not yet sure what other tests can be added (maybe the one withbig integers I mentioned in other PR), but I think it is already a great start!

During normalization, JSON objects are tagged with the "struct" atom in order to be able to tell the difference between an empty object and an empty list or set

Wouldn't it be easier to convert them to maps instead?

The Erlang sets version {version, 2} is only used if running on OTP 24 or higher.

:+1:

Hello!
please take a look at the pull request, I have tried to address all the issues you mentioned.
It seems I need your approval so that CI checks this pull request, please consider this.
Thanks a lot again for all the great suggestions to this change.

Fixed by #116


Semi-Automatic testing for GPU support

k8s 1.8 changed the resource request to a resource limit
I think there are other bits about using GPU on k8s that may be changing as this API surface changes.
To date, our recommended solution has been tested in a specific way, but manually. It would be nice to have a test suite we can run (not every build since its expensive) ad hoc (maybe once/week or per release) to validate GPUs are still working.
If we could virtualize GPUs on travis, that might be a good way to do this. However, our current recommended approach assumes an aws p2 instance, installing specific nvidia drivers, using kops, etc. So while GPU testing on travis might be helpful, it also wouldn't validate our suggested deployment approach.

stale


craft an upstream support policy

Describe the behavior changes introduced in this PR
Linked Issues?
resolves #345
related to # <-- Use this if it shouldn't
Testing Instructions
Please include any additional commands or pointers in addition to our standard PR testing process.
@redhat-cop/mdt

/lgtm


Auto-save comment and post text

Okay, I think this has everything we'd want for a first pass. There is a feature setting (defaulting to enabled) at the tech-level 1, and when disabled, the localStorage data is removed if there were anything saved before it was disabled.

Another issue worth mentioning is that there is no easy way to clear the memory of the "post" draft upon submission of the post. In the case of a "comment" draft, the submission is done with AJAX, so I was able to use the successful POST request conditional to know I could remove the localStorage value. Post submissions reload the page, so there would have to be an awkward feedback loop from PHP that sets a JavaScript variable via the jot-header.tpl.

there is no easy way to clear the memory of the "post" draft upon submission

What about an on submit handler? Something like that:
$(document).on('submit', '#post-form', function(){
    localStorage.removeItem('foo');
});

What about an on submit handler? Something like that:

Preview I think invokes the submit handler. You can still do this, but in the preview callback code you might need to turn it on again, since it will likely get turned off when you submit the preview.

Anyway, i will merge now. You can adjust things later. We are still a week or two from the next RC.

I'll let you decide if this is a bug or feature. I'm going to call it a feature, but it's interesting so I'll share. Type something into a new post on your network page. Now go to your Cards page. Your text appears as a card. Go back to your network page. Your text becomes a post again.
This may not have been intended, but I'm totally ok with it..

I thought it would be simplest to have the post draft apply to anything using the core "jot" editor. If we decide to start implementing app-specific draft saving, then we'll want to change this, but for now this at least satisfies basic auto-save needs.

Is there any way to disable this feature? It's awkward to delete the old and already posted content every time I'll post new content.

Okay  - so I'll stay with it until it is fixed.

There's nothing like settings  > additional features > post composition features > Auto-save comment and post text here >:

You are looking in the wrong tab. Should be the third from above, not sure what the german translation says...

Found it: Nachbearbeitungsfunktionen
Thanks 😊


feat: basic application build

add new build workflow step to generate the code for logic layer coverage test
move the types for api and logic layer to new package to avoid cycle imports
add Config type to provide application config items and add test
add config file path override method (by env)
add user/video/comment model dal interface
add jwt token config, signer
add jwt whitelist, middleware
config routes
based on dal interfaces and jwt singer, add the login/register logic and test
add feed query logic and test
add user profile query logic and test
specified upload api handler,add initial upload logic
add fx framework to build the application
based on fx, add server graceful shutdown logic and test
organized by layer, define fx modules
initial user/video dal logic
fix #13
fix #14
fix #15
fix #16
fix #17
fix #18
fix #19
fix #20
fix #23

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@97d2a47). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage        ?   71.66%
=======================================
  Files           ?       14
  Lines           ?      240
  Branches        ?        0
=======================================
  Hits            ?      172
  Misses          ?       58
  Partials        ?       10

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Tests for multi-object delete with object lock

Tests to go along with https://github.com/ceph/ceph/pull/37933, which fixes an issue where multi-object delete didn't respect object locks.

squashed and rebased, merged, and cherry-picked to ceph-master


Renaming of static pipes + connectors

Renaming pipes to something a bit more serious.
For presentation purposes.

@ChaelKruip FYI: This might break scenarios you have already been working on, on account of the new names for the connectors. Is that a problem? If so, we can remedy this by adding a migration to update existing LESes.

Is that a problem?

No problemo!


RSI value not correct ?

Hi,
I was running the bot to check if the values are the same with the ones that I see on the exchange:
ETH/BTC:        Breakout: 0.0   RSI: 81.59
ZCL/BTC:        Breakout: 0.0   RSI: 52.49
XVG/BTC:        Breakout: 0.0   RSI: 40.08
EMC2/BTC:       Breakout: 0.0   RSI: 40.69
EMC/BTC:        Breakout: 0.4   RSI: 56.50
Sleeping for 3 seconds
ETH/BTC:        Breakout: 0.0   RSI: 81.59
ZCL/BTC:        Breakout: 0.0   RSI: 52.49
ADA/BTC:        Breakout: 0.0   RSI: 43.61
XVG/BTC:        Breakout: 0.0   RSI: 40.08
EMC2/BTC:       Breakout: 0.0   RSI: 40.69
EMC/BTC:        Breakout: 0.4   RSI: 56.50
Sleeping for 3 seconds
ETH/BTC:        Breakout: 0.0   RSI: 81.59
ZCL/BTC:        Breakout: 0.0   RSI: 52.49
ADA/BTC:        Breakout: 0.0   RSI: 43.61
XVG/BTC:        Breakout: 0.0   RSI: 40.08
EMC2/BTC:       Breakout: 0.0   RSI: 40.68
EMC/BTC:        Breakout: 0.4   RSI: 56.50
Sleeping for 3 seconds
ETH/BTC:        Breakout: 0.0   RSI: 81.55
ZCL/BTC:        Breakout: 0.0   RSI: 52.49
ADA/BTC:        Breakout: 0.0   RSI: 43.61
XVG/BTC:        Breakout: 0.0   RSI: 40.04
EMC2/BTC:       Breakout: 0.0   RSI: 40.68
EMC/BTC:        Breakout: 0.4   RSI: 56.50
Sleeping for 3 seconds
ETH/BTC:        Breakout: 0.0   RSI: 81.55
ZCL/BTC:        Breakout: 0.0   RSI: 52.49
ADA/BTC:        Breakout: 0.0   RSI: 43.61
XVG/BTC:      Breakout: 0.0   RSI: 40.04
It's very unlikely for a coin with high transaction volume to have the same value after 9,18,27 seconds.

By default it uses hourly candles., the smallest value candles any exchange will give you is 1 minute candles... so even after 27 seconds you still aren't likely to see a change.

agree that over the minute RSI will not be affected ..
Not sure if some of the broader discrepancy  is based on the memory of RSI not being part of TA-LIB
https://www.quantopian.com/posts/ta-lib-rsi-using-something-other-than-close-price
http://ta-lib.org/d_api/ta_setunstableperiod.html
been doing some research around this

update FWIW .. appears that using 14 periods with 120 periods of history aligns TA-Lib nicely with TradingView at the 1 minute interval .. YMMV

Also worth noting that the python binding library documentation will tell you what functions do not have the unstable flag set and thus are susceptible to variance due to time period: http://mrjbq7.github.io/ta-lib/func_groups/overlap_studies.html

There is no further work to do on this ticket I am closing it for now.


BUG Feedback:  lookup_users use GET request in Official Twitter Docs

Hey,
I find  tweep do lookup_users with  "POST" request style,
but in official Twitter docs , it's   "GET" request style .
def lookup_users(self, user_ids=None, screen_names=None, *args, **kwargs):
        """ :reference: https://developer.twitter.com/en/docs/accounts-and-users/follow-search-get-users/api-reference/get-users-lookup
            allowed_param= 'user_id', 'screen_name', 'include_entities',
                           'tweet_mode'
        """
        return bind_api(
            api=self,
            path='/users/lookup.json',
            payload_type='user', payload_list=True,
            method='POST',
            allowed_param=['user_id', 'screen_name', 'include_entities',
                           'tweet_mode']
        )(list_to_csv(user_ids), list_to_csv(screen_names), *args, **kwargs)

SO   its a bug for Tweepy ?
https://developer.twitter.com/en/docs/twitter-api/v1/accounts-and-users/follow-search-get-users/api-reference/get-users-lookup

The documentation on that page says (multiple times), "You are strongly encouraged to use a POST for larger requests."
Since the endpoint supports it, Tweepy simply uses POST for all requests to the endpoint. This is not a bug.

@Harmon758  could Tweepy can use GET for this ?  when we  use POST method to get larger requests , Twitter will limit this user's all Tweepy functions which use POST request.

There is no advantage to using GET here. In fact, it's likely that it will cause issues with larger requests to this endpoint.
I'm not sure what exactly you're saying is the downside for using POST, but if you're talking about rate limits, they are per endpoint.
There shouldn't be any rate limit encompassing all POST requests to all API endpoints.

There is no advantage to using GET here. In fact, it's likely that it will cause issues with larger requests to this endpoint.
I'm not sure what exactly you're saying is the downside for using POST, but if you're talking about rate limits, they are per endpoint.
There shouldn't be any rate limit encompassing all POST requests to all API endpoints.

Do you mean we can support GET request ?  for millions of followers ID ,  request 100 per 2 seconds , so it's larger requests ??
I mean  to divide big number into small number , maybe its not larger request ?

Again, there's no reason to use GET rather than POST for this endpoint.


GetRegionDataKeyForValue returns incorrect region key

https://github.com/googlei18n/libaddressinput/blob/5764685e7ca0dc410c535dba3bad29f703e78c32/android/src/main/java/com/android/i18n/addressinput/AddressWidget.java#L231
There are certain display strings that end with the same thing. the specific instance I encountered was trying to get the key for Netherlands ("NL") and this function returning the key for Caribbean Netherlands ("BQ"). other examples of this particular issue are Samoa and American Samoa.

This bug should now be fixed.


Bump PostCommit Java DataflowV1 timeout to 6h

It is consistently timing out
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Fix timeout seen in #30323
R: @johnjcasey

R: @damccorm


If sketch is not turned on, choosing "edit" should turn it on.

I wanted to edit an sketch that was not turned on. It zoomed to the extent of the sketch but didn't display the geometry. That was a bit confusing. Seems like choosing "edit" should display the shape.

Fixed but not deployed quite yet.


No updates of Copr boolean values for custom projects and request builder permission if needed

Improve comment texts for copr settings edits.
Request 'builder' permission for custom projects if we needed.
Do not overwrite Copr boolean values if we don't own it.
Requires: https://github.com/packit/packit/pull/938
Fixes: https://github.com/packit/packit/issues/935

recheck


Typescript server should support passing format options on format request

Refers to the code in src/server
Current format options can either globally configured are defined via an open call. Since formatting options can change dynamically (auto detected) or changed without open/closing a file the protocol should support sending them. The TS language service already support formatting options in the corresponding methods.

If this is something the server would accept I will work on a pull request.

@dbaeumer the server has a configure message that can set format options tabSize and indentSize (it takes an optional file name so that the options can be applied to single files).  If you need additional formatting options, we'd welcome a pull request that adds them as optional fields to the configure request.

Adding the formatting options as an optional object parameter to the formatting request messages would also be fine.

@steveluc opened pull request #2468. Forgot to use automatic linking,,,
The pull request only adds format options to the format requests. I am happy to work on adding the options to configure and open requests as well but wanted to get your opinion on whether we should add an options property to those and deprecate tabSize and indentSize or whether you want to list them individually.
I also fixed a problem with indentation correction and tabs. This revealed when using convertTabsToSpace set to false.

Closing. Got fixed via #2489


Render template content before rendering layout content

This is a slight procedural change that will allow things like sharing content from the template up to the layout. For example if a "content_for"-style method was made available to both the template and the layouts, then it would be important to render the template first so that it could provide the "content_for" data, which would then be used by the layout (e.g. useful for specifying page-specific content that needs to go into the layout’s <head>).

Copied from https://github.com/dry-rb/dry-web/pull/18, which was made back when dry-view was part of rodakase.

This is another tiny behavioural change that should have no impact on existing usage, but opens up a lot of possibilities for template authors. Will merge!


Side menu behaviour

The side menu in the current production app closes after users have selected a language, which is the expected behaviour. The staging app though does not do that. The side menu would continue to remain present despite the overlay shadow has disappeared. Users will have to dismiss the side menu manually which could cause frustration overtimes.
Current side menu behaviour
recording for the current staging app (1.29.0):

Expected side menu behaviour
recording from the current production app (1.7.0):

Acceptance Criteria

[ ]  Upon selecting a language, the side menu closes along with the overlay shadow.

Steps for QA:

Open the side menu by clicking on to the hamburger icon.
Select any language except Arabic (since Arabic resets the whole app).

An side effect of the app not reloading enough is that the token language doesn't get updated. Non arabic languages to arabic and vice versa will trigger an update on the token to the correct language, but switching between non arabic languages does not.

QA Passesd.


LiveDebugging doesn't work even with experimental stabilityLevel

Chart version: 1.4.4
Piece of Chart values:
cluster:
  name: eu1-aks-dev-1
alloy:
  alloy:
    stabilityLevel: "experimental"
    uiPathPrefix: /agent
    clustering:
      enabled: true
    enableReporting: false
  config:
    liveDebugging:
      enabled: true

Even with this config, Alloy UI still displays error:
Error: Failed to connect, status code: 500, reason: the live debugging service is disabled. Check the documentation to find out how to enable it

Live debugging is enabled like this, not inside the config block:
alloy:
  liveDebugging:
    enabled: true

@petewall ahh my bad! :(
Thank you pointing it out, it works now

Ahh, my bad! It works with the updated config, thank you!


Fixing #251: proper handling of InvalidSegmentException and InvalidVersionSpecificationException

The situations indicated in the exceptions were not handled properly throughout the code, in some places, MojoExcecutionException was simply being thrown leading to the whole run being stopped; InvalidVersionSpecificationException was unchecked, leading to the same.
Handling those situations in the Mojo itself rather than in the methods so that a proper handling could be effected where necessary.
Because of all that, a rather sizeable refactoring was due.
More PRs will follow, I want to refactor and polish the code more, but this one is what's necessary for resolving this issue.
So, like I said in the linked issue:
The more I look into it, the more issues I see:

segment appears to be 0-based (see e.g. AbstractVersionsUpaterMojo.determineUnchangedSegment or MavenVersionComparator.innerIncrementSegment), but the comparison against the segment count suffers from the 1-off problem:

if ( segment > segmentCount )
{
    throw new InvalidSegmentException( segment, segmentCount,
            version.toString() );
}

segment determination flags (allowMajorUpdates, etc.) are actually not at all independent, but are actually a sort of enum; so an actual enum or an unchanged segment index would be better;
part of the above: it's not actually possible to have allowMajorUpdates = true and allowMinorUpdates = false; allowMajorUpdates = true implies all others also being true;

There are probably more problems with this, but I'll limit the scope of this item to the issue OP raised only. The other findings will be done as separate issues.

@slawekjaranowski please review :smile:


Geometric line with only one point in Postgresql/PostGIS gives unhelpful error

Description
When viewing a field with a geometry linestring with only one point (which is allowed in PostGIS) the result tab shows the field with  a purple background colour and the text

Invalid hex digit: 'L'

When changing to Spatial view a new error message pops up:

Can't switch presentation
Reason:
Invalid hex digit: 'o'

The value does not show up in the value panel either.
It is true that an OGC-valid LineString has either zero or two or more points, but PostGIS also allows single-point LineStrings. Also, other invalid geometries can be shown without getting an error message.
How to display the value spatially is an open question, however it should be possible just to see the value as-is, just as other geometric values are shown as text. In any case the error messages are unhelpful.
DBeaver Version
<IP_ADDRESS>301211053
Operating System
Windows 11
Database and driver
Server: PostgreSQL 13.4, PostGIS 3.2.3
Driver: PostgreSQL JDBC Driver 42.2.5
Steps to reproduce

Connect to PostgreSQL database with PostGIS
Create line with a single point, e.g.: SELECT ST_MakeLine(ST_MakePoint(10, 20));
View result: Invalid hex digit: 'L'
Click on Spatial tab and view result: Invalid hex digit: 'o'

Additional context
Screenshot with error message and no value for field:

Screenshot of error message when clicking on Spatial tab:

For what it's worth: DBeaver accepts and can visualize a line with two identical points, e.g.:
SELECT ST_MakeLine(ST_MakePoint(0,0), ST_MakePoint(0,0))

This suggests that the concept of a line without any length is currently accepted by DBeaver in some form.

This is a bug in the geometry library we're using. We need to update to the latest version.

Thank you for your report.

Thank you for your report.


Pattern Detector Warnings

Required Information

[ ] AEM Version, including Service Packs, Cumulative Fix Packs, etc: <IP_ADDRESS>_______
[ ] ACS AEM Commons Version: 4.5.0_____
[ ] Reproducible on Latest? yes

Expected Behavior
Pattern Detector is giving warning regarding ACS Commons which is referring granite:FinalArea nodes. Though this ACS version is compatible with 6.5, it should not give us the warning.
Actual Behavior
As we are migrating from aem <IP_ADDRESS> to 6.5.4. We have installed the latest version of ACS  which is compatible with 6.3 and 6.5 still when we run Pattern Detector, it gives us the warning that ACS is referring to final path (For Example: The path: /apps/acs-commons/components/authoring/graphiciconselect violates content areas override final path: /libs/granite/ui/components/foundation/form/select) which cannot be overlaid.
Steps to Reproduce
Install ACS AEM Commons 4.5.0
Install Pattern Detector
Run Pattern Detector to get the warnings
Links
Links to related assets, e.g. content packages containing test components
Pattern Detector DAM Issues.xlsx

timestamp
suspicion
pattern/code
pattern/type
pattern/detective
pattern/moreInfo
item/id
item/message
item/referencedBy
item/referring

2020-03-26T12:43:08.279Z
TRUE
CAV
content.area.violation
ContentAccessDetector
https://www.adobe.com/go/aem6_CAV
232bac6dbbeee9b8299b0a2a9784e39bc25c5fd7c98329df0fd9a0c33fed11a8
The   path: /apps/acs-commons/components/authoring/graphiciconselect violates   content areas override final path:   /libs/granite/ui/components/foundation/form/select
/apps/acs-commons/components/authoring/graphiciconselect
/libs/granite/ui/components/foundation/form/select

2020-03-26T12:43:13.700Z
TRUE
CAV
content.area.violation
ContentAccessDetector
https://www.adobe.com/go/aem6_CAV
2dd5f7e35e0fc965f857524732d2418e6820c682f40029dddda8ffd5c36ee1af
The   path: /apps/acs-commons/components/authoring/graphiciconselect/render.jsp   violates content areas override internal path:   /libs/granite/ui/components/foundation/form/select/render.jsp
/apps/acs-commons/components/authoring/graphiciconselect/render.jsp
/libs/granite/ui/components/foundation/form/select/render.jsp

2020-03-26T12:43:13.700Z
TRUE
CAV
content.area.violation
ContentAccessDetector
https://www.adobe.com/go/aem6_CAV
7c00d62205c2aa3430d5af8604750e8c33d5d698a2ce0430a6243d0c2a271700
The   path:   /apps/acs-commons/components/authoring/graphiciconselect/render.jsp/jcr:content   violates content areas override internal path:   /libs/granite/ui/components/foundation/form/select/render.jsp/jcr:content
/apps/acs-commons/components/authoring/graphiciconselect/render.jsp/jcr:content
/libs/granite/ui/components/foundation/form/select/render.jsp/jcr:content

Have you tried to do the exercise with a more recent version of ACS AEM Commons as well?

Yes, I tried with the latest version 4.5.0 of ACS AEM Commons as well and still, it gives warnings.

Please let me know if any updates regarding this.

This duplicates #1511

What is the fix of this issue. We are migrating from AEM 6.5.14 to AEMaaCS and we ran BPA , there we can see similar issues.

Hi @joerghoh / @kwin
I have tried with the latest version of ACS-Commons but still am getting these kind of similar errors.
Is there any update on this issue?  We are migrating from AEM 6.5.15 to AEMaaCS and we ran BPA , there we can see similar issues. Please provide suggestions to resolve the issues.


Update AnnotationBean.java fix add annotation on setter

Update AnnotationBean.java fix add annotation on setter

 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.


Admin actions under one button

Dropdown menu instead of single a href

Fixed with https://github.com/linkdotnet/Blog/commit/47452d8d03b50f54dad53092ee95ee56828f7558


feat: track climate finished

will resolve https://github.com/fuatakgun/kia_uvo/issues/142

Only thought on this is it may not work for EU since duration is a NA thing.  In the EU climate will run for a preset length of time.  Now I think we are okay on that since the default is set to 5 so it would check in 5 minutes later to see if it finished.  I will sift through code to confirm the theory since I can't test to confirm.
Great idea for an add by the way!

@cdnninja great point on the duration being ignored, I hadn't thought to check and in the USA it is ignored too. I haven't worked out how long it is yet exactly but seems more then 5 and likely is 15 minutes.  Going to have to rethink this feature a bit once I pin point the duration in USA kia.  I really wanted it for a script to keep the climate on until I turn it off or the car turns on, sometimes I just leave it running for hours unlocked and that would be much better ;)

just observed 18 minute climate run, US definitely ignores the parameter, will have to run more tests to see how consistent it is


fix the bug that CAS do not auto redirect

Add the function to enable auto redirect in CAS login #2482

 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.


Suggest custom filenames

A bit like saving folders, newly created files can be customized with variables like time and title.

Sorry for the delay. This is the option in the settings so you could customize the filename with title and date

#30

@StrollStars Sorry, this is something I have been working on in #30 so it's just a preview from my local machine.
I'm hoping this would suffice your need :)

@sywhb Thanks, it looks like it will do what I need, but if it doesn't solve https://github.com/omnivore-app/omnivore/issues/1837, I wish to support adding 1 on the original date.

Hey @StrollStars, yeah, we display the date in UTC in the reader currently. I will change it to use local time and will update you once i'm done

@sywhb thank you very much.

Sorry for the long delay but please check out the new version v1.1.0 @StrollStars
I hope it will fix the issue here

@sywhb Thank you very much for adding this feature, I think it fully meets the needs. But there is a small flaw, the Folder Date
Format must be set at the same time to take effect. If someone wants one of the two to have a date and the other to have no date, there is no way. I don't have this need, so I closed this issue, thanks again.


Deprecated warnings when initialized with Terraform v0.15.3

Warning: Version constraints inside provider configuration blocks are deprecated
│
│   on main.tf line 9, in provider "aws":
│    9:   version = "~> 2.0"
Terraform 0.13 and earlier allowed provider version constraints inside the provider configuration block, but that is
│ now deprecated and will be removed in a future version of Terraform. To silence this warning, move the provider
│ version constraint into the required_providers block.
At this point in the book, I'm not sure where required_providers block is at.

@KingAndrew you need to remove the 9: version = "~> 2.0" from the provider version. This will get rid of the deprecated warning

As is listed multiple times in the book and this repo, the code examples are only tested with Terraform 0.12. Versions 0.13, 0.14, and 0.15 all introduced backwards incompatible changes, and the book/examples have not yet been updated to take those into account.

This has been updated in the 3rd edition of the book.


add update_nested

as discussed in https://github.com/bioimage-io/core-bioimage-io-python/pull/256

Yes, let's maybe add a cli command update-rdf with the (default?) option --validate that takes RDF, UPDATE, OUTPUT as arguments.
The other use cases I see for now are:

updates in collection (internal)
updates in export_bioimageio_model (internal)

Yes, let's maybe add a cli command update-rdf with the (default?) option --validate that takes RDF, UPDATE, OUTPUT as arguments.

That sounds good, but update_rdf should also be available as a proper function in bioimageio.spec, so that it can be used programatically and not only through the CLI.

Yes, let's maybe add a cli command update-rdf with the (default?) option --validate that takes RDF, UPDATE, OUTPUT as arguments.

That sounds good, but update_rdf should also be available as a proper function in bioimageio.spec, so that it can be used programatically and not only through the CLI.

how about
def update_rdf(
    source: Union[dict, os.PathLike, IO, str, bytes],
    update: Union[dict, os.PathLike, IO, str, bytes],
    output: Union[dict, os.PathLike] = None,
    validate: bool = True,
) -> Union[dict, Path]:
   ...

the default would be to return a dict

how about
def update_rdf(
    source: Union[dict, os.PathLike, IO, str, bytes],
    update: Union[dict, os.PathLike, IO, str, bytes],
    output: Union[dict, os.PathLike] = None,
    validate: bool = True,
) -> Union[dict, Path]:
   ...

the default would be to return a dict

Yeah, that's good!
Can you implement s.t. "inplace" updates are possible? I.e. if ouptut=source the input rdf file should be updated directly.


Changing less breaks live-reload (p0)

Changing less breaks live-reload (p0)

Even refreshing does not fix this.  I have to restart the server.  cc @matthewp

Fixed in done-css 1.1.6 https://github.com/donejs/css/commit/1ec5153a8b3a0a2194f34fab2ef8b3def27375c5


Consider supporting SLA4OAI spec

Problem to solve
SLA + SLO are things that go together. This spec defines the second.
However, there is also another spec with the goal of describing SLA, called SLA4OAI.
Would it make sense to add support, somehow? Perpahs just as a linked doc to this spec.
Proposal
To somehow have the ability to link an OpenSLO file with a SLA4OAI one.
--
Congrats on this great initiative folks! 🚀

Also opened an issue on the SLA4OAI repo: https://github.com/isa-group/SLA4OAI-Specification/issues/17


Wait until the postgres is ready before test running

Purpose
The drone will always wait for the database before starting to run the tests.
Approach
Added a script to wait for the database for 120 seconds. If it exceeds the 2 min, it's gonna fail.

Coverage remained the same at 58.506% when pulling 0c0189d41e900dc5e275e0abb7922f431285019c on jefmoura:fix-deployment into e37898bfd60a94c2a698864e9b0734de4ed1889a on toladata:dev-v2.


#251 - Adjusted sending emails through Sendgrid.

Anyway of seeing the actual email addresses?
ב-25 במאי 2015, בשעה 20:34, Avi Klaiman<EMAIL_ADDRESS>כתב/ה:

You can view, comment on, or merge this pull request online at:
https://github.com/hasadna/anyway/pull/270
Commit Summary
#251 - Adjusted sending emails through Sendgrid.
File Changes
M config.py (2)
M main.py (10)
M templates/sendemail.html (2)
Patch Links:
https://github.com/hasadna/anyway/pull/270.patch
https://github.com/hasadna/anyway/pull/270.diff
—
Reply to this email directly or view it on GitHub.

You mean that you want to see them before you send the email?

I want to see the actual addresses. Like<EMAIL_ADDRESS>ב-25 במאי 2015, בשעה 20:49, Avi Klaiman<EMAIL_ADDRESS>כתב/ה:

You mean that you want to see them before you send the email?
—
Reply to this email directly or view it on GitHub.


Support render functions (+ misc tweaks)

Hey, thanks for building this to DRY out the pain of wiring up react-bootstrap components to formik! Very helpful, but in my use-case I needed to pass a function as children, so I recreated the logic formik uses to handle either nested components or a function.
Once I figured out how to get yarn link working to test locally I added a couple other changes as well; feel free to add or ignore as you see fit -- each is in a separate commit.
Commits:

Support function children
Add groupClassName prop (gives control over FormGroup's className prop - I used groupClassName="w-100" to make textarea full width)
Added a default export for Form
Added Submit - just a small wrapper to add a spinner to the submit button when the form is submitting
Added a tiny usage example to the README (I found the previous "supports Input" statements very confusing at first, this section clarifies that components should be called like Form.Input).

... in my use-case I needed to pass a function as children, so I recreated the logic formik uses to handle either nested components or a function.

Also, I think adding this is useful since formik supports it. To hold you over, are you able to use useFormikContext?
import { useFormikContext } from "formik";
import { Form } from "react-bootstrap-formik";

const SamplePage = () =>(
  <Form>
    <SampleForm />
  </Form>
);

const SampleForm = () => {
  const { ... } = useFormikContext();
  return (
    <>
      <Form.Input name="foo" />
    </>
  )
}

Thanks for the review! Feel free to tweak & merge -- in the intervening months I've just inlined the parts of the code I needed in my own app, so I'm not using the library anymore myself.

Going to close this for now then. Apologies for the delay!


Fix typo

I'm assuming this is a typo.

First of all, thank you to everyone for their hard work on PromiseKit. It's become an invaluable asset to asynchronous architecture that I write. Secondly, this pull-request might be moot but my understanding between then and when made me think this was a typo. Please correct me if I'm wrong!

No, it is correct as is. Usually you want when and not to use sequential thens.


blindly check for .go files across the repository

See https://github.com/heroku/heroku-buildpack-go/issues/115 for more context on why Heroku originally did not do this, but I think the number of users who have ruby apps with .go files in their repo is very small. Worst case scenario these users can just call draft create --pack ruby to explicitly override the system.
closes #101.

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

This doesn't seem right. I'm still getting an error after removing the glide.yaml file. cc/ @bacongobbler
draft [bacongobbler-check-go-files-in-root]$ rm bin/draft
draft [bacongobbler-check-go-files-in-root]$ make build
go generate ./pkg/draft/pack/generated
GOBIN=/Users/michellenoorali/gocode/src/github.com/Azure/draft/bin go install  -tags 'kqueue' -ldflags ' -X github.com/Azure/draft/pkg/version.Version=v0.1.0 -X github.com/Azure/draft/pkg/version.GitCommit=9ffd834942bbd0e66cb584700c777c2ec8083b75 -X github.com/Azure/draft/pkg/version.GitTreeState=clean' github.com/Azure/draft/cmd/...
draft [bacongobbler-check-go-files-in-root*]$ cd examples/golang/
golang [bacongobbler-check-go-files-in-root*]$ ls
Dockerfile	chart		draft.toml	glide.yaml	main.go
golang [bacongobbler-check-go-files-in-root*]$ rm -rf chart/
golang [bacongobbler-check-go-files-in-root*]$ rm glide.yaml
golang [bacongobbler-check-go-files-in-root*]$ ../../bin/draft create
Error: Unable to select a starter pack Q_Q
golang [bacongobbler-check-go-files-in-root*]$

Did you rm -rf ~/.draft/packs/golang && draft init --client-only? It looks like you installed the new client but forgot to update the local packs :)

Still getting that error..
draft [bacongobbler-check-go-files-in-root*]$ rm -rf ~/.draft/packs/
draft [bacongobbler-check-go-files-in-root*]$ make build
go generate ./pkg/draft/pack/generated
GOBIN=/Users/michellenoorali/gocode/src/github.com/Azure/draft/bin go install  -tags 'kqueue' -ldflags ' -X github.com/Azure/draft/pkg/version.Version=v0.1.0 -X github.com/Azure/draft/pkg/version.GitCommit=9ffd834942bbd0e66cb584700c777c2ec8083b75 -X github.com/Azure/draft/pkg/version.GitTreeState=dirty' github.com/Azure/draft/cmd/...
bin/draft draft [bacongobbler-check-go-files-in-root*]$ bin/draft init --client-only
Creating /Users/michellenoorali/.draft/packs
Creating pack python
Creating pack golang
Creating pack node
Creating pack java
Creating pack php
Creating pack ruby
$DRAFT_HOME has been configured at /Users/michellenoorali/.draft.
Not installing Draftd due to 'client-only' flag having been set
Happy Sailing!
draft [bacongobbler-check-go-files-in-root*]$ cd examples/golang/
golang [bacongobbler-check-go-files-in-root*]$ ../../bin/draft create
Error: Unable to select a starter pack Q_Q
golang [bacongobbler-check-go-files-in-root*]$

I've got some other ideas. Let me try something and get back to you.

I just saw the trailing ||. That is what's causing the headaches. Removing that from ~/.draft/packs/golang/detect fixes draft create. Lemme patch that right up. 🐑

k, fixed

manually tested. 👍


[Enhancement]: The home page icon is difficult to identify until discovered . Create a hover effect to make it more understandable.

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Game enhancement: The small hut at the top left corner become very difficult to identify. The user will get confuse about its functionality. The home icon should be more understandable.
Describe the solution you'd like
Either i can change the home icon or add a hover effect on it. As soon as user hover on it it will display home which will make the user understand that it is the home page icon.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@SIM-RAITANI Could you please explain more what you want to do, if possible you can also add screenshot...
If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

I would like to work on this issue. Please assign it to me.

@SIM-RAITANI Could you please explain more what you want to do, if possible you can also add screenshot... If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

Sir i would add hover effect that will tell us that it is an home icon and it will take us to a new page. Such that when someone hover on it , on the bottom home should be written with it.
Like in the above image,the description comes upon hover.

@thevirengarg I am confident that, if assigned this task, I will complete it promptly and to a high standard. My goal is to create a visually appealing and user-friendly About page that accurately represents our project and engages our audience. I am excited to contribute to this project under GSSoC and make a positive impact on our website.
I will use my skills in HTML, CSS, and JavaScript to create a responsive and accessible About page that meets the needs of our users. I will also ensure that the page is optimized for search engines and follows best practices for web development.
I am confident that my contributions will help to improve the overall user experience of our website and make it a valuable resource for our audience.i can add hover effect in it.

@thevirengarg I can improve https://github.com/GameSphere-MultiPlayer/Physi-c-Tech/issues/39 and https://github.com/GameSphere-MultiPlayer/Physi-c-Tech/issues/42 which is about home page button and icon assign me this task. I am confident that, if assigned this task, I will complete it promptly and to a high standard. My goal is to create a visually appealing and user-friendly About page that accurately represents our project and engages our audience. I am excited to contribute to this project under GSSoC and make a positive impact on our website.
I will use my skills in HTML, CSS, and JavaScript to create a responsive and accessible Home page that meets the needs of our users. I will also ensure that the page is optimized for search engines and follows best practices for web development.
I am confident that my contributions will help to improve the overall user experience of our website and make it a valuable resource for our audience. i will add hover effect in it.

@thevirengarg I am confident that, if assigned this task, I will complete it promptly and to a high standard. My goal is to create a visually appealing and user-friendly About page that accurately represents our project and engages our audience. I am excited to contribute to this project under GSSoC and make a positive impact on our website.
I will use my skills in HTML, CSS, and JavaScript to create a responsive and accessible Home page that meets the needs of our users. I will also ensure that the page is optimized for search engines and follows best practices for web development.
I am confident that my contributions will help to improve the overall user experience of our website and make it a valuable resource for our audience. i will add hover effect in icon.

@KomalSrivastava Create a new issue


Add FS0703 to compiler messages documentation

Summary
Compiler message 0703 was not in the documentation here which I found when following the link through Ionide for VSCode today.
I followed the instructions here so please let me know if there is anything else to add.

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


Missing "requests" dependency in setup.py

This is just documenting the issue. I have already fixed this in my fork, and am awaiting resolution of issue #218 before I make a pull-request of it.

Fixed by https://github.com/openworm/PyOpenWorm/pull/220


*: Fixed various go vet and golint warnings

Fixes #38. These are only renames done by gofmt and a few manualy reverts, e.g. to keep TaskService inside the Controller for the field name.

Current coverage is 51.58%

Merging #43 into master will not affect coverage as of d3ac661

Powered by Codecov. Updated on successful CI builds.

ping @giantswarm/cena

I think some changes do not make sense but I don't have strong feelings here. Go ahead.


Mismatching Hash Error for Persona 3 Reload

I just bought Persona 3 Reload Digital Premium Edition this Steam Autumn Sale as well as the Expansion Pass for Episode Aigis. But, upon adding to Reloaded-II I've been met with a Mismatching Hash for the executable found in steamapps\common\P3R\P3R\Binaries\Win64
I've also tried verifying my files on the game, but I'm still met with the error

It just means game got updated, but this repository.
I'll ask in the community. You can ignore the error outside of that.


Updated the endpoints

Would love to see this merged in.

it's nice that you can't get an "errors" member in a 2xx response but it'd be helpful if there was a list of which api's they changed the response format for like https://developer-docs.amazon.com/sp-api/docs/reports-api-v2020-09-01-reference#responses vs https://developer-docs.amazon.com/sp-api/docs/reports-api-v2021-06-30-reference#responses
i guess this is their changelog but tough to follow the pre-2022 ones https://developer-docs.amazon.com/sp-api/page/release-notes and doesn't seem like they mentioned the breaking changes e.g. to the reports one in that announcement https://github.com/amzn/selling-partner-api-docs/discussions/1107

we could merge this if we could fix the example code in the readme and add a list of what endpoints have version updates in this PR as opposed to which are just totally new

Thanks for merging this! I see that the latest version of the gem is still 0.2.2. Could we have something like a 1.0.0.rc.1 (or something like that) until the version 1.0.0 is ready?

@pasandrei https://github.com/ericcj/amz_sp_api/releases/tag/v1.0.0


Update HotReloading.js

Leading slash produces the following hot http://localhost:8080/ that leads to a double slash like so in the link of dev server assets http://localhost:8080//js/app.js

Thank you, you saved me some more troubleshooting. This should be merged and released because it breaks the usage of hot reloading.

So, I hadn't merged this yet because I thought we'd need to coordinate a release with Laravel to normalize the // -> / mainly in the case of an asset not beginning with a slash causing an invalid url. However, poking at the source code now it fixes it up if something doesn't already (and has done so almost since the inception of the mix() helper)
What's weid is this shouldn't cause an issue anyway because I worked around the problem with this: https://github.com/JeffreyWay/laravel-mix/blob/3fa559471aa0bb092934f8dc72601f6bd144cbec/src/builder/WebpackConfig.js#L136-L142
I use HMR a decent amount and it's been working so it's possible a recent change to a dependency may have broken it.

Thanks!


java.nio.file.NoSuchFileException: /bin

Hi!
I encountered the problem using JmeterDSL 1.7
Library could not find /bin directory in JmeterEnvinroment Class

InstallConfig method contains hardcoded path "/" on 92 line

Hello, thank you for reporting this!
Can you share the full stack trace?
Regards
On Wed, Feb 22, 2023, 14:57 Ilya @.***> wrote:

Hi!
I encountered the problem using JmeterDSL 1.7
Library could not find /bin directory in JmeterEnvinroment Class
[image: telegram-cloud-photo-size-2-5454235959567697918-y]
https://user-images.githubusercontent.com/11280681/220709063-71fe2baa-0400-4173-bf64-0f26bc9892e4.jpg
[image: telegram-cloud-photo-size-2-5456235129405030929-y]
https://user-images.githubusercontent.com/11280681/220714130-6055aed7-fd30-41fc-bc0d-906c655a6779.jpg
InstallConfig method contains hardcoded path "/" on 92 line
—
Reply to this email directly, view it on GitHub
https://github.com/abstracta/jmeter-java-dsl/issues/174, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYIFL4GCLXF6A3RQGUKGYLWYZHPBANCNFSM6AAAAAAVEUVPOE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I don't know, mb it is connected with class path?

Seems that it could not find /bin directory in jar to copy it to target path during installConfig method

Are you trying to repackage Jmeter dsl inside another jar? I see some tomcat and spring framework references in the stack trace, like you packaged jmeter dsl inside a spring application.
If that is the case, you have to be careful so as for bin folder to be included in final jar, otherwise you might lose it and get such error.
When you say you exec as jar... what jar are you actually executing? is that a spring boot app that you are trying to run from the jar? You might need to tune spring boot packaging maven/gradle plugin to get bin directory properly placed and solved on it.
Maybe if you can share some code on how you are using the DSL, maybe a sample project that has similar structure as the one you are using, or the exact same code, we might be able to help you further.

Here is a spring boot related discussion, maybe this helps you: https://github.com/abstracta/jmeter-java-dsl/issues/147

<plugin>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-maven-plugin</artifactId>
    <configuration>
        <layout>ZIP</layout>
        <requiresUnpack>
            <dependency>
                <groupId>us.abstracta.jmeter</groupId>
                <artifactId>jmeter-java-dsl</artifactId>
            </dependency>
        </requiresUnpack>
    </configuration>
</plugin>

Did not help

Maybe if you can share some code on how you are using the DSL, maybe a sample project that has similar structure as the one you are using, or the exact same code, we might be able to help you further.

Here is a simple demo. Build Jar using maven by mvn clean package
JmeterDSLTest.zip

You need to unpack dependencies that contain JMeter components as well, as the example provided in the issue I passed.
Can you try with something like this?:
<requiresUnpack>
                        <dependency>
                            <groupId>us.abstracta.jmeter</groupId>
                            <artifactId>jmeter-java-dsl</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_components</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_config</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_core</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_functions</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_http</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>org.apache.jmeter</groupId>
                            <artifactId>ApacheJMeter_java</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>kg.apc</groupId>
                            <artifactId>jmeter-plugins-casutg</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>kg.apc</groupId>
                            <artifactId>jmeter-plugins-dummy</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>kg.apc</groupId>
                            <artifactId>jmeter-plugins-tst</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>com.blazemeter</groupId>
                            <artifactId>jmeter-plugins-random-csv-data-set</artifactId>
                        </dependency>
                        <dependency>
                            <groupId>com.blazemeter</groupId>
                            <artifactId>jmeter-plugins-wsc</artifactId>
                        </dependency>
                    </requiresUnpack>

I wish to express my appreciation for all your efforts. I am truly grateful for your advice and help. Thank you so much for this tool! Everything is working!

Thank you very much for your words @sial.
I am glad that everything worked only with that change and that you can enjoy the tool and find it helpful.
Regards


Update derive.rs: you should accept one as positive according to the latest research

…latest research
From the The Very Important Problems dept.

Indeed. What was I thinking... I appreciate a fix :heart:


Cobalt.io-logo with fixed curvature, parts where not perfectly circular!

Alright, thanks for the update!


Run GlanceAPI with GlanceUID user

When the backend is not Cinder (Cinder still has to be fully tested), GlanceAPI can reduce the permissions required for glance-api container, and run as GlanceUID/GlanceGID. This patch introduces scc for both glanceAPI and httpd.

https://github.com/openstack-k8s-operators/glance-operator/pull/609
https://github.com/openstack-k8s-operators/glance-operator/pull/620

Jira: https://issues.redhat.com/browse/OSPRH-9842
Jira: https://issues.redhat.com/browse/OSPRH-10149

/test glance-operator-build-deploy-kuttl

/test glance-operator-build-deploy-kuttl

/test glance-operator-build-deploy-kuttl

Tested with uni*eta to make sure Glance + Cinder is not a problem. I think we can merge this patch, and follow up in case of unexpected issues.

Thank you @abays for the review.


improve species hint

Let's change this hint to indicate that the NCBITaxon approach is an option.

Originally posted by @bendichter in https://github.com/NeurodataWithoutBorders/nwb-guide/issues/634#issuecomment-1987303710

Likewise the message is directly from the NWB Inspector: see https://github.com/NeurodataWithoutBorders/nwbinspector/pull/439

Originally posted by @CodyCBakerPhD in https://github.com/NeurodataWithoutBorders/nwb-guide/issues/634#issuecomment-1987309451

Fixed upstream, will snap into place on next releases (or when using dev mode)


Nested body and html tags trip jsoup into closing the stack too early

For the attached eisenachonline-de.html.gz, jsoup 1.15.3 returns a tree different from that shown by Firefox and Chrome in their dev tools. There are nested body and especially html tags that seem to trip up the parser to close the stack prematurely.
The relevant HTML section looks like this:

Unfall zwischen PKW und Fußgänger

...

       <?xml encoding="utf-8" ?>
Bildquelle: © Comofoto – stock.adobe.com

           Symbolbild

       <time datetime="2022-10-20 14:24">20. Oktober 2022</time>

For this HTML, the following code:
    public static void main(String[] args) throws IOException {
        Document doc = Jsoup.parse(new File("eisenachonline-de.html"));
        System.out.println(doc.selectFirst("header[class=entry-header]").selectFirst("div[class=entry-date]"));
    }

should print

<time datetime="2022-10-20 14:24">20. Oktober 2022</time>

but prints null instead. The entry-date div is present in the parsed document, but it is a child of the body element.
There seems to be a deviation from the HTML spec in the jsoup implementation. In the AfterBody state, when processing an html end tag, jsoup pops the stack to close. In the "after body" insertion mode, the HTML spec only says to switch to the "after after body" mode, but it doesn't ask to close the stack. So it appears to me the stack is closed too early.

Thanks, fixed.


connection timed out

What happened? What did you expect to happen?
I timed out when executing CI after deploying to the server

connection timed out

It looks like this is getting stuck in the pulling registry.dagger.io/engine:v0.9.5 step.
It could just be that the connection to registry.dagger.io is slow, can you attempt to manually pull it using docker pull registry.dagger.io/engine:v0.9.5?

It's caused by network issues. The company website is really poor


Possible improvements for the current visualization strategy

I would propose two improvements to the current visualization strategy and specifically in the phase of generation of the .xmf file:

Add the possibility for the user to choose which field should be loaded;
Add the possibility for the user to choose the frequency at which each field is loaded as some of them can be skipped and therefore should not be loaded.

Thank you Nicolò, @nscapin!

The choice of the fields to be loaded can be done during the visualization stage (at least in paraview), by choosing not to load these files.

The frequency option (1) has been added in f56fa37 (see parameter istep which is set to 1, constant spacing, by default).


Mac Make Issue

gcc -Wall -m64 -c -o shabal64-darwin.o shabal64-darwin.s
gcc -D OSX -D AMD64 -Wall -m64 -O3 -mtune=native -D_FILE_OFFSET_BITS=64 -c -o helper64.o helper.c
helper.c:114:23: error: use of undeclared identifier '_SC_PHYS_PAGES'
long pages = sysconf(_SC_PHYS_PAGES);
^
1 error generated.
make: *** [helper64.o] Error 1
Issue still persists on MacOS 10.9.5. Issue appears to not be an issue on the latest version of MacOS, but it should be backwards compatible to an extent (which currently appears to be unknown). The released binary for Mac appears to run on MacOS 10.9.5 from the onset (but no params have yet been tested).

Based on my research, it appears that _SC_PHYS_PAGES wasn't available in older MacOS versions, and so a more universal alternative should be used. If this isn't feasible, a conditional wrapper should be implemented instead.

latest Engaver support MacOs out-of-the-box.


Project status

Latest commit 8586e9a  on Aug 26, 2018

Is this project still maintained or is it abandoned?

I'm sorry that I didn't find time/motivation to work on this, but I'm still using it myself, so I won't call it "abandoned". I want to update the underlying HAP-Node.js and add the TV Accessories asap, give me some more time, can't promise when it will happen. I hope to get this done at the latest before christmas, maybe earlier.

 In my opinion its much better than HomeBridge which is too much complex and hard in use ( unless you know how to write plugins ).
Maybe people can organise some dotation for this project ?
Best regards!


docker :latest should point to master not latest PR build

ATM

so running :latest would result running that PR image.
Ideally, IMHO, :latest should correspond to "latest release" but there seems to be no releases really (and :master to last build on master branch -- all consistent and clear).  But it better not to point to some PR (could still be buggy/breaking/etc).
edit 1: it seems to be not quite trivial to filter through all those tags and find commit- tag on docker hub corresponding to master, just need to do it "manually" from looking at commit of current master:
❯ pwd
/home/yoh/proj/misc/qlever
❯ docker pull adfreiburg/qlever:commit-$(git log -1 --format="%h")
commit-e3dcc9c: Pulling from adfreiburg/qlever
7646c8da3324: Pulling fs layer
...

Hi,

All the published docker images correspond to a commit on the Master branch, there is no intermediate work from unfinished PRs on Dockerhub.
The prXXX tag come from our workflow. We consistently squash each PR into a single commit before merging it, thus each commit on the master branch uniquely identifies a PR. This PR is used as one of the tags. In particular that PR number also appears  in the commit message of the corresponding commit. Additionally, each image is also tagged with its commit hash. If you compare the git log of the master branch with the names of the provided images, you should be able to observe the correspondence between those two.

Does this answer your questions and address your concerns?

@yarikoptic Since there was no more reaction, I am closing this issue now. If there are still questions, feel free to reopen or start a new issue.

Sorry, missed that comment -- IIRC was traveling at that point.
FWIW -- response said nothing about latest label which was the subject of my issue.


Connection Reset by Peer

I woke up to seeing this:
2016-07-25 01:30:44  INFO: [24BF1F6D] disconnected
2016-07-25 01:31:09  INFO: [8470655A] connected
2016-07-25 01:31:10  WARN: [8470655A] error - Connection reset by peer - IOException (...)
2016-07-25 01:31:10  INFO: [8470655A] disconnected
2016-07-25 01:31:12  INFO: [62C9C476] connected
2016-07-25 01:31:35  INFO: [0D237162] connected
2016-07-25 01:31:35  WARN: [0D237162] error - Connection reset by peer - IOException (...)
2016-07-25 01:31:35  INFO: [0D237162] disconnected
2016-07-25 01:32:00  INFO: [76127C4D] connected
2016-07-25 01:32:00  INFO: [ED3B2CD5] connected
2016-07-25 01:32:00  WARN: [ED3B2CD5] error - Connection reset by peer - IOException (...)
2016-07-25 01:32:00  INFO: [ED3B2CD5] disconnected
2016-07-25 01:32:25  INFO: [CC142B6A] connected
2016-07-25 01:32:26  WARN: [CC142B6A] error - Connection reset by peer - IOException (...)
2016-07-25 01:32:26  INFO: [CC142B6A] disconnected
2016-07-25 01:32:51  INFO: [EAC272DF] connected
2016-07-25 01:32:51  WARN: [EAC272DF] error - Connection reset by peer - IOException (...)
2016-07-25 01:32:51  INFO: [EAC272DF] disconnected
2016-07-25 01:32:59  INFO: [708071C7] connected
2016-07-25 01:33:16  INFO: [D88A4C95] connected
2016-07-25 01:33:16  WARN: [D88A4C95] error - Connection reset by peer - IOException (...)
2016-07-25 01:33:16  INFO: [D88A4C95] disconnected
2016-07-25 01:33:41  INFO: [988A5B94] connected
2016-07-25 01:33:41  WARN: [988A5B94] error - Connection reset by peer - IOException (...)
2016-07-25 01:33:41  INFO: [988A5B94] disconnected
2016-07-25 01:33:44  INFO: [564D35AE] connected
2016-07-25 01:34:06  INFO: [B69C0396] connected
2016-07-25 01:34:07  WARN: [B69C0396] error - Connection reset by peer - IOException (...)
2016-07-25 01:34:07  INFO: [B69C0396] disconnected

NORAN Protocol on 5053. Not sure what I'm doing wrongly or what changed.

Connection reset by peer means that TCP client has disconnected from the server. Not sure if it's actually from your device, but even if it is from device, it doesn't send any actual data.

Thanks, but doesn't NORAN use only UDP?

Yes, it does. It means that those connections are not even for port 5053.

Okay. So I just redirected the NORAN traffic to one of the traccar's server and it works fine. OSMAND Protocol works well on our server, but not NORAN. I've checked firewall and everything, I'm not sure what could be wrong anymore. Any help?

Take a look at this guide:
https://www.traccar.org/troubleshooting/
Basically, if you don't see any HEX messages in the log, it means that server doesn't receive anything from your device.

Thanks so much. I ended up having a closed port in Microsoft Azure Management Portal. Opened it up and everything works fine now.
Thanks a lot!


Update travis to try to build for osx and linux

Experimenting with osx build/test.

Woo!  This seems to work.
Merging so the osx package will be built and pushed to anaconda.