added guide for mercurial

NOTE:

Please fill out the template below

Did you read the instructions in the README?

Y

Have you read the instructions in CONTRIBUTING?

Y

Have you written this article by yourself? Have you taken inspiration from anywhere and then written it in your words?

[I have taken reference from wikipedia and official guide]

@the-ethan-hunt please review it

@RN0311 i have updated the changes please review it

@sourabh1031 : Now, it's better! Thanks for updating!
@the-ethan-hunt : Reviewed.

@the-ethan-hunt please review i have updated the guide

Merging


The session never updates and remains stale.

You can see it via Java EE cafe.

Once you deploy Java EE Cafe to a cluster, you can see session replication not working. Just make an update on one instance and the update will not show up on the other one. Make sure to pre-load the application on the other instance. It just continues to show the stale session even after refresh.
My guess is that this is because of more Azure port blocking or networking glitches.


Use version property in ReleasePublish task

If the releaseVersion property is not set, attempt to use the
project's version as releaseVersion.
If neither are set, throw exception.

Coverage decreased (-0.6%) to 54.494% when pulling edc0c3a76478066bb9cb56a596889cca73458737 on jgaribaldi:master into 6ca63200c43065351bae483732faf87f26807fb2 on RobWin:master.

Thx


Dev branch appears to stop permitting agents to phone home after ~24 hours.

Empire Version
newest, out of dev
This gig we're on is a long one. We're still getting shells phoning in.
I kill empire, git pull, restart it, and later (I have 3-4 waves of persistence throughout the day) shells can phone home again.
I'm not sure how to get to the bottom of this one, but I have validated that i have to kill/restart empire once a day while on the dev branch.
Is there a way for me to debug this? perhaps a packet capture?

This turned out to be a bug on my end.


feat: Init expressjs app and openapi

Enable basic routing using express-openapi and path versioning.
First Endpoints:
http://localhost:3000/v1/api-definition
http://localhost:3000/v1/forms/{id}/submission/new

Did you consider adding Typescript support? I know that is something I did right away when I made a PoC with Express for HTTP streaming. Did not think about not having it.

correct, in the plan

Is the express-openapi package just here to generate some kind of an API documentation? Otherwise, when building my PoC (I mentioned in the previous comment), I felt like Express had enough stuff to start building an API.

Is the express-openapi package just here to generate some kind of an API documentation? Otherwise, when building my PoC (I mentioned in the previous comment), I felt like Express had enough stuff to start building an API.

Not an expert, but express-openapi does more than automatic doc: It provides request and response validation against the OpenAPI schema, routing,  help generate client SDKs, server stubs etc.

Is the express-openapi package just here to generate some kind of an API documentation? Otherwise, when building my PoC (I mentioned in the previous comment), I felt like Express had enough stuff to start building an API.

Not an expert, but express-openapi does more than automatic doc: It provides request and response validation against the OpenAPI schema, routing, help generate client SDKs, server stubs etc.

Sounds good! Will read about this when I have time but I guess this is just me trying to make sure we include packages that we know we will need, use and won't hinder our progression towards the API MVP.


How to install petrel_client？

pip Could not find a version that satisfies the requirement petrel_client，How to install petrel_client？

hi @Maxchengqin
If you don't use petreloss as your cloud data storage, you can skip the step of installing petreloss


ETW rundown for registry events

I'm aware PH has an ETW-based plugin to collect disk/net I/O events from NT Kernel Logger ETW provider. It also relies on rundown provider to enumerate all open file objects for the purpose of deriving the file name from file object reference. Do you know if rundown provider is able to log open registry keys or system handles?
Thanks

able to log open registry keys

Event 24 of the Registry class has rundown events for open registry keys.
https://docs.microsoft.com/en-us/windows/desktop/etw/registry

or system handles
https://docs.microsoft.com/en-us/windows/desktop/etw/obhandlerundownevent

PH has an ETW-based plugin to collect disk/net I/O events

It's not configured for these events and even then handle/registry events are practically useless because they don't include some types of accesses. If you compare the ETW events to Process Monitor you will see the etw events are missing entries.


Fix logging

For #3106

Coverage remained the same at 62.067% when pulling 974d6083644363c27e1e137b5f722b0837e27d57 on fix-logging into 8e382c65aefaeefec240f30d36b20215cd3af5c9 on master.


search always return 500

I tried multiple searches (including "lord of the rings") but I always get this error:

That may be the case if cloudflare has blacklisted your IP. That should be temporary or a VPN can solve that issue.

I'm trying to investigate by running the app locally, but when run with yarn start it's extremely slow, do you know why?

nevermind, after it fakely re-downloads the torrents in the download page it starts to go fast again.
it's much slower at doing so than the official app (which also lags until this process is complete) probably because it's running in dev mode.
I'll update you here when If I find out more about the returned 500

It is supposed to be slow in dev mode because the files are compiled on the fly whereas in production the static files are created in advance.

@FrancescoCioria any update ?

I couldn't find out the issue and after a couple of days it began to work again so I stopped worrying about it

I think that may have been a CloudFlare blocking issue due to a lot of requests. Good to hear that its working fine for you.


Add more than one domain?

Hi,
I am using 3 different sub domains for my DuckDNS account. With the standard Addon it is easiely possible to add several sub domains in the configuration.yaml. Does adding multiple sub domains work in your addon, too?

After revisiting the duckdns documentation and trying a few things I have found that you can just add multiple domains separated by commas. Important is to leave no spaces between the domains and comma.
Example:
duckdns_ipv4_ipv6:
  access_token: YOUR_ACCESS_TOKEN
  domain: YOUR_SUBDOMAIN_1,YOUR_SUBDOMAIN_2
  ipv4_mode: duckdns
  ipv6_mode: nameserver


Binary data not retuned correctly

I have an existing express app which I'm moving to AWS Lambda. I'm using @vendia/serverless-express version 4.10.1 while doing this.
I have one API endpoint that returns a binary file. I'm having issues with corrupted binary response. I'm using AWS API GW V2.
I first returned the binary without any base64 encoding:
console.debug('Returning file to client. Length: ' + data.length)
res.setHeader('content-type', 'application/octet-stream')
res.status(200)
res.send(data)

When using API GW Payload format version 2.0 I got back something that looked like the correct binary, but it was corrupted. Data length before sending was about 75kb while I received file size of 110kb. I got the same 110kb regardless if the call was via API GW or directly to Function URL. Hence I think it's serverless-express tried to manipulate the response.
I then tried to return the data as base64 encoded:
const base64data = data.toString('base64');
res.setHeader('content-type', 'application/octet-stream')
res.status(200)
res.send(base64data)

In these cases I only get the base64 encoded string back (size about 100kb), API GW does not convert the base64 to binary.
My client sends Accept: application/octet-stream in the request headers.
My understanding is that with serverless-express version 4, I don't need to pass any isBase64Encoded  or binaryMimeTypes . Many of the guidelines are also for AWS API GW 1.0. I've tried returning base64 encoded file using API GW payload format versions 1.0 (explicit response format) and 2.0 (interpreted response format). Both have the same result.
My API uses "ProtocolType": "HTTP", and my integration uses below configs, so I believe I cannot set ContentHandlingStrategy (CONVERT_TO_BINARY) together with "ProtocolType": "HTTP",.
"ConnectionType": "INTERNET",
"IntegrationMethod": "POST",
"IntegrationType": "AWS_PROXY",

Is serverless-express manipulating data if I simply try to retun the binary with res.send(data), as it seems like APIGW would pass it through.

Ok, so it seemed serverless-express did a base64 encoding for the content I passed as base64 encoded. I resolved this by:
In lambda.ts I added the binary setting:
exports.handler = serverlessExpress({
  app,
  binarySettings: {
    contentTypes: ['application/octet-stream']
  }
})

and in the API I returned binary without base64 encoding:
res.setHeader('content-type', 'application/octet-stream')
res.status(200)
res.send(data)


Implement separate functions for get_device from id and array

Fix #2051

LGTM. Please merge _v2 and resolve conflicts.

And I think we can merge this feature in v1.

I noticed that I can remove get_device method completely from Chainer now. I'm fixing this PR.

@unnonouno As for this comment,

And I think we can merge this feature in v1.
Finally I removed get_device method completely. So it's not possible now...

I mean, we can add new methods and replace old one in v1, make old API deprecated and remove old API in v2.

OK, I understand. But it breaks backward compatibility, so I think it's better to merge this only into v2. Removing get_device also from v1 sounds a bit risky. How do you think on it? @beam2d

We should not remove get_device from v1. As @unnonouno wrote, we have to leave it at least with deprecation warning. How about making this PR only deprecate get_device and add get_device_from_*, merge it into master, and make another PR targetting v2 that just removes get_device?

OK, I'll make other PRs. So I close this. Thanks

Sorry, applying this after #2391 can achieve what you guys thought? So I re-opened it.

We need to change get_device with newer APIs in v1. But does the newer API support Device object?


HWKAPM-668 Replace Externalizable with Serializable

@pavolloffay could you review please?

Could you please add serialVersionUID to the other classes which implement Serializable to keep consistent.

@pavolloffay Thanks!


Fix downstream Dockerfile and add page elements to storagedrivers.md

The docker/docker:docs/Dockerfile on the engine repo has an additional sed script that was not in the downstream repos like distribution or compose.  This sed script is causing a problem in the output of the docs/storagedriver.md file.
As a result, when I tested on the cherry-pick-branch everything looked good:

When I tested for publish it failed with a bad title and a borked nav:

@moxiegirl Is this addressed by #480?

Confirmed.


fix: typo + missing bin directory

What this PR does / why we need it
This PR fixes typos.
Additionally, it fixes the Make target make install-requirements because of missing bin directory.

sorry, was too fast with my comment... ok, bin directory is missing... when? Shouldn't the make target ensure that it is created when necessary instead of having an empty file lying around :thought_balloon:

Shouldn't the make target ensure that it is created when necessary instead of having an empty file lying around 💭

@hilmarf Sure, you are totally right. I was trying out different ways to make the install-requirements Make target work. I changed it now so that the bin directory will be created if it does not exist.


Bugs/share warning removal and renabling detectExposures

Why:

This commit:

Screenshots:

How to test:

Linked issues:

Looks good. We will add chaff back in at a later date.


Specify handling of repeated field names in system Structs

This came up while reviewing a pull request on serde_ion.
Background
Ion specifically allows for Struct values to contain duplicate field names. [1, 2]
But throughout the specification, sections are written as though this were not the case. There are a number of references to "the {field_name} field", and the specification provides for the scenarios where no field with a particular name exists, but not for the scenario where multiple exist.
The section for local symbol tables encountered in an Ion stream is one example.

The imports field should be the symbol $ion_symbol_table or a list as specified in the following section.
The symbols field should be a list of strings. If the field is missing or has any other type, it is treated as if it were an empty list.

As is the section for import structs in a local symbol table.

If no name field is defined, or if it is not a non-empty string, the import clause is ignored.
If the name field is "$ion", the import clause is ignored.
If no version field is defined, or if it is null, not an int, or less than 1, act as if it is 1.
If a max_id field is defined but is null, not an int, or less than zero, act as if it is undefined.

This issue also exists for shared symbol tables, but due to the opening disclaimer this may not actually be a flaw in the specification. A higher-level convention could exist for how repeated field names are handled. But I think that the standard should define the handling.

This section defines the serialized form of shared symbol tables. Unlike local symbol tables, the Ion parser does not intrinsically recognize or process this data; it is up to higher-level specifications or conventions to define how shared symbol tables are communicated.

There are tests in ion-tests/bad that cover a subset of these scenarios, specifically repeated imports and symbols fields in local symbol tables. Strictly speaking, I don't think the behavior of those tests is supported by the specification.
Updating the specification to fix this was mentioned in a related issue but doesn't seem to have happened.
Possible fixes

Following the JSON philosophy: Leave it up to the implementation to select a matching field or to error.
Handle this on a case-by-case basis, updating the spec with required behavior in the same way that the spec currently has case-by-case handling for what to do if a field is absent or holds an unusual value.
Define a convention that when the specification refers to "the {field_name} field" it is referring to the first (alternately, the last) field with that name.
Define a convention that whenever the specification refers to a field by name, it is an error for multiple fields to exist with that name.

Considerations
Inferring from the tests in ion-tests, option 4 seems to be the option that would specify the behavior of the existing implementations (though of course option 1 would as well). This would likely be the easiest to move forward with, requiring only updating the spec and adding some more tests in ion-tests to cover all of the other named fields in system structs.
But option 4 is also the worst option from a technical standpoint, for the same reason given in the FAQ for why duplicate fields are permitted in the first place.
It rules out both the high-performance approach of doing a skip-search scan across field names in the binary encoding, as well as the developer-friendly approach of just deserializing all of the fields into a clobbering hash table and then looking up the required names.
Recommendation
Option 1 would be my recommendation, given that Ion is a superset of JSON. I think this lines up best with the fact that names should be unique. People should not construct weird system Structs, and if they do, they might get weird behavior. In practice no behavior should change, since no implementations should be writing repeated fields in system structs, and existing implementations would have rejected (at least some of) them.
The work required for this change would only be to add a second caveat to the data model definition of Structures and remove tests in ion-tests.

When two fields in the same struct have the same name we say there are “repeated names” or (somewhat misleadingly) “repeated fields”. Implementations must preserve all such fields, i.e., they may not discard fields that have repeated names. However, implementations may reorder fields (the binary format identifies structs that are sorted by symbolID), so certain operations may lead to nondeterministic behavior.

would become something like

When two fields in the same struct have the same name we say there are “repeated names” or (somewhat misleadingly) “repeated fields”. Implementations must preserve all such fields, i.e., they may not discard fields that have repeated names. However, implementations may reorder fields (the binary format identifies structs that are sorted by symbolID) and may error or return any matching field when reading a repeated name from system structs, so certain operations may lead to nondeterministic behavior.

Thanks for the detailed issue. I agree that the spec can use clarification here, and we should have done that when the test cases were added that prohibit repeated field names in symbol table structs.
We will need to opt for a solution like your option 4 above. In other words, we must prohibit repeated field names for system fields in system structs, and we can probably address all cases with a single statement at the top of the Symbols page of the spec. With that in mind, let me explain why by addressing some of your points.
Our decision about what to do in this case is guided by two philosophies, which we follow whenever practical:
a) Ion data must be equivalent when read by any Ion implementation. If this cannot be guaranteed, parsing should fail as early as possible. Violating this rule leads to data that can only be read by certain implementations, a problem common with JSON and its variants. Option 1 violates this rule.
b) An Ion writer must not allow the user to write date that violates (a). Violating this rule can lead to the need for expensive backfilling to try to salvage the data.

This issue also exists for shared symbol tables, but due to the opening disclaimer this may not actually be a flaw in the specification.

The same rules described above should apply to shared symbol tables. Some Ion libraries provide utilities that write and parse shared symbol tables via in-memory representations that can be added to a catalog for use by Ion writers and readers. The constraint is needed so that each implementation of these utilities handles shared symbol tables in the same way, since the contents of the shared symbol table affects the meaning of data.

But option 4 is also the worst option from a technical standpoint, for the same reason given in the FAQ for why duplicate fields are permitted in the first place.
It rules out both the high-performance approach of doing a skip-search scan across field names in the binary encoding, as well as the developer-friendly approach of just deserializing all of the fields into a clobbering hash table and then looking up the required names.

Prohibiting duplicate field names in symbol tables does not suffer from the O(N) space problem described in the linked FAQ because there is a known, fixed number of system fields that need to be checked. We don't need to specify that all field names in symbol tables must be unique (i.e. even open content), just symbols and imports (and, within import descriptor structs, name, version, and max_id).
For the same reason, it doesn't affect skip-scanning over open content; in structs, the field name symbol always precedes the value, so the value can be skipped without parsing once the field name is determined to not match one of the system fields. This field name check would need to be done regardless of which option from above is chosen.
As you state, it may prevent you from being able to read the struct into a map whose implementation you don't control, but it's not clear to me that that's something that would actually be desirable to do.

People should not construct weird system Structs, and if they do, they might get weird behavior.

Following rule (b) stated above, prohibiting duplicate field names on read also implies that they should be prohibited on write. So by going with Option 4, we will help users avoid getting in this situation that can be a large headache once data is already serialized. I think we can give implementations freedom about how to handle this case on write, as long as no implementation writes a symbol table with repeated system fields in the same struct.
For example, an writer may fail, or it may intercept the symbol table being written and combine repeated fields in memory in a well-defined way before writing out a valid symbol table that does not violate the rules stated above.

Let me know if anything is unclear. I'm happy to continue the discussion.

We will need to opt for a solution like your option 4 above. In other words, we must prohibit repeated field names for system fields in system structs, and we can probably address all cases with a single statement at the top of the Symbols page of the spec.

I agree that this would be sufficient. Moreover I think the prohibition has to be restricted to system fields, else the change would be backwards-incompatible, as the spec currently says that non-system fields should be ignored.

a) Ion data must be equivalent when read by any Ion implementation. If this cannot be guaranteed, parsing should fail as early as possible.

This seems reasonable. As a corollary, I think this means that parsers can't have any limitations that can't be detected by the parser at runtime.

b) An Ion writer must not allow the user to write date that violates (a)

It's not clear to me what this means. If this this intended to mean that an Ion writer should never write output that is not Ion, that seems like it goes without saying.
Alternatively this could mean that there exists valid Ion that when read by a correct Ion parser has multiple valid results. I don't think any such valid Ion exists (though option 1 proposes that it could). Regardless, I think this is a good principle. Even if ambiguous Ion does exist, Ion writers should not write it if there is a non-ambiguous alternative.

For the same reason, it doesn't affect skip-scanning over open content; in structs, the field name symbol always precedes the value, so the value can be skipped without parsing once the field name is determined to not match one of the system fields. This field name check would need to be done regardless of which option from above is chosen.

I think my concern here has been misunderstood. I had intended that "scanning" convey stopping once the required values are found. The performance impact is not that field values would need to be parsed deeper than is required to determine their byte length, the issue is that the once symbols and imports are found, all remaining field names still need to be checked, despite being ignored, because they might be repeats of imports/symbols.

Following rule (b) stated above, prohibiting duplicate field names on read also implies that they should be prohibited on write.

Oddly enough, prohibiting duplicate field names on write intrinsically ensures that they will not be present on read, as a representation that contains them would then not be Ion. This still achieves the goal in (a), since "Ion data must be equivalent when read by any Ion implementation" is also satisfied by specifying that representations containing duplicate field names are not Ion.
But I think it's more valuable to preserve the invariant that an Ion parser should always fail if used to parse a representation that is anything other than valid Ion.

All these points being considered, it seems like option 3 (with the "first" variant) fits best. Parses are always unambiguous, (a) and (b) are achieved, and early-terminating a field name scan once (imports + symbols) /  (name + version + max_id) are located is valid. Ion writers get flexibility on whether or not to write repeated system fields, since in either case they will be ignored.
No existing valid Ion would become invalid, and while some existing invalid Ion would become valid, I doubt much exists.

That's because no existing Ion writer implementation that I know of will actually write open content within symbol table structs, and I don't think there is really a use case for that.

I assumed that the reason why extra fields in a symbol table are ignored instead of prohibited is to support optional extensions, both official and user-defined. I don't see why the spec would not have prohibited them if it did not intend to support writing to them. In fact, this has led me to thinking about proposing an optional extension, where a binary local symbol table could present a max_subfield_magnitude field to inform the parser that it has the option to switch to a more efficient codepath until the next IVM is encountered.
If no writer will write them, and you don't think there is a use case for them, I'm inclined to propose the more radical fix that this problem be solved by specifying that a local symbol table contains only and exactly one imports and one symbols, with the existing logic for how to derive their values if they are absent or malformed, and likewise for name/version/max_id.

For that reason, I'm still leaning toward Option 4, but I am open to additional opinions.

Anyhow, I don't think there are much in the way of additional options. Faced with the issue of multiple of something which there should only be one of, the options are really only

error
select one in a deterministic way
select one in an arbitrary way
somehow merge them

The only remaining plausible thing I can think of that a parser could do is somehow merge duplicate fields. But what would that mean for system fields like max_id that are not collections? It wouldn't make sense without a lot of superstructure do define what "merging" means. That seems like an unreasonably complicated approach to solving this problem.

It sounds like we agree on the approach: to raise an error if more than one of the same system field is defined in a system struct. Is that accurate?

I'm not opposed to that solution. Is there a reason not to go further, and reject all unexpected fields in system structs?

Is there a reason not to go further, and reject all unexpected fields in system structs?

I'm not sure we'd really gain anything by making this change. Historically we've wanted to support open content in system structs, but the reality is that full support has always fallen below the line when it comes to prioritization. Right now, we at least support reading such symbol structs with correct system semantics, even if the open content would be lost on round trip.

Right now, we at least support reading such symbol structs with correct system semantics, even if the open content would be lost on round trip.

It seems like this is not the case, since open content in a system struct won't make it into the stream of values read from the byte stream. Since the fields are ignored the content is never read.

I'm not sure we'd really gain anything by making this change.

It preserves (actually, enhances) the optimization potential that inclined me toward options 1 and 3. If both repeated and unexpected fields were rejected, a parser would never have to read more than 2 fields to determine the validity of a system symbol table (or 3 for an import). Either there are fewer than 2 fields, or if there are two fields, they must be symbols and imports and the end of the second field value must coincide with the end of the struct. This technically breaks down in the face of NOP padding, but prohibiting NOP padding in system structs seems like an easy addition if everything that the NOP pad could be converted into is already prohibited. If the NOP padding is for alignment purposes, the writer can just pad the symbols or imports instead.


[SUPPORT] "Failed to read schema/check compatibility" on Hudi upgrade from 0.12.2 to Hudi 0.14.1

Describe the problem you faced
We're upgrading from Hudi 0.12.2 to Hudi 0.14.1 and are running into failures on all of our log ingestion jobs on:
Caused by: org.apache.hudi.exception.HoodieException: Failed to read schema/check compatibility for base path s3://...
	at org.apache.hudi.table.HoodieTable.validateSchema(HoodieTable.java:844)
	at org.apache.hudi.table.HoodieTable.validateUpsertSchema(HoodieTable.java:854)
writerSchema: ...
tableSchema: ...

The only diff in the schema seems to be the snippet below in all of our jobs where meta is a record type (table_name is a placeholder for every affected table):
➜  ✗ diff writer_schema_table_name.json table_schema_table_name.json
65,66c65
<           "name": "meta",
<           "namespace": "hoodie.table_name.table_name_record",
---
>           "name": "table_name_meta",

Oddly, the table version was bumped even though the commit failed, so we ended up having to run a tedious bulk downgrade command. That seems super surprising.
To Reproduce
Unclear, it seems like some one-time upgrade step of the table version did not run for whatever reason?
Expected behavior

Is this expected behavior? How do we manually upgrade our tables if not?
The table version should not be bumped if the commit fails

Environment Description
We are running on EMR 7.2

Hudi version : 0.14.1

Spark version : 3.5.1

Hive version :

Hadoop version :

Storage (HDFS/S3/GCS..) : S3

Running on Docker? (yes/no) :

Ok I think the root cause is because the upgrade silently turned on schema validation with
https://github.com/apache/hudi/blob/release-0.14.1/hudi-client/hudi-client-common/src/main/java/org/apache/hudi/table/HoodieTable.java#L822
    boolean shouldValidate = config.shouldValidateAvroSchema();
    boolean allowProjection = config.shouldAllowAutoEvolutionColumnDrop();
    if ((!shouldValidate && allowProjection)
        || getActiveTimeline().getCommitsTimeline().filterCompletedInstants().empty()
        || StringUtils.isNullOrEmpty(config.getSchema())
    ) {
      // Check not required
      return;
    }

Previously in 0.12.2 https://github.com/apache/hudi/blob/release-0.12.2/hudi-client/hudi-client-common/src/main/java/org/apache/hudi/table/HoodieTable.java#L749C1-L754C6
    if (!config.getAvroSchemaValidate() || getActiveTimeline().getCommitsTimeline().filterCompletedInstants().empty()) {
      // Check not required
      return;
    }

Questions:

Whys there a coupling with hoodie.datasource.write.schema.allow.auto.evolution.column.drop and disabling schema validation? Why is schema validation silently turned on by default now?
Did some table upgrade silently not run successfully causing the schemas to be broken? The namespace/name change seems like an internal detail.
It seems like we can just turn off schema validation but is there a way to fix the schemas of our tables without a re-write?

Referencing slack thread for this discussion - https://apache-hudi.slack.com/archives/C4D716NPQ/p1723826030979209

@ad1happy2go hmm setting hoodie.datasource.write.schema.allow.auto.evolution.column.drop to `true still doesn't skip the schema validation check, any idea why?
We're hard blocked by this issue on upgrading and its quite painful, let me know if you have any ideas on how to work around  this

It seems like there is a second issue, if you use the default configs for Hudi this line (https://github.com/apache/hudi/blob/release-0.14.1/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieSparkSqlWriter.scala#L751 ):
      parameters.getOrDefault(HoodieWriteConfig.AVRO_SCHEMA_VALIDATE_ENABLE.key(), "true")

Will actually just ignore the default for hoodie.avro.schema.validate and enable schema validation silently... you actually need to explicitly set hoodie.avro.schema.validate to false now
Seems like this regression was introduced in https://github.com/apache/hudi/commit/06c8fa5a62fab607d3be6e321a580d9cf13b572a#diff-8bda4b2174721fd642a543528283[…]a320c1d9e1366b27be86bd548d48aR527

Thanks a lot @mzheng-plaid for detailed explanation and triaging the issue. This sounds reasonable and we should highlight in our release docs. The default config is confusing in this case.
Created JIRA for tracking the fix - https://issues.apache.org/jira/browse/HUDI-8173


Mipmaps decmods

Adds output schemas for mipmaps and uses tilespec-based parallelization for applymipmaps.  These versions were cherry picked from repo used for EM December SMART goal.

Codecov Report

Merging #53 into develop will increase coverage by 0.24%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #53      +/-   ##
===========================================
+ Coverage     60.5%   60.74%   +0.24%
===========================================
  Files           22       22
  Lines          957      963       +6
===========================================
+ Hits           579      585       +6
  Misses         378      378

Impacted Files
Coverage Δ

rendermodules/dataimport/generate_mipmaps.py
86.66% <100%> (+0.62%)
:arrow_up:

rendermodules/dataimport/create_mipmaps.py
75% <100%> (ø)
:arrow_up:

rendermodules/dataimport/schemas.py
85.93% <100%> (+1.19%)
:arrow_up:

...endermodules/dataimport/apply_mipmaps_to_render.py
83.33% <100%> (-0.31%)
:arrow_down:

Continue to review full report at Codecov.

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


<EMAIL_ADDRESS>typings error

Hello,
First of all thank you for what you have implemented so far on this project 👍
I encountered the following errors in CI environment:
node_modules/@bull-board/api/typings/app.d.ts:1:29 - error TS2307: Cannot find module '../src/queueAdapters/base' or its corresponding type declarations.
1 import { BaseAdapter } from '../src/queueAdapters/base';
                              ~~~~~~~~~~~~~~~~~~~~~~~~~~~
node_modules/@bull-board/api/typings/app.d.ts:2:26 - error TS2307: Cannot find module '../src/constants/statuses' or its corresponding type declarations.
2 import { STATUSES } from '../src/constants/statuses';

It looks like the imports of the typings are referencing the source code instead of the built one, or am I missing something ? 🤔
Thanks in advance for your insights !

What is the code you are trying to compile / run?

What is the code you are trying to compile / run?

I've just updated the title with the version, if this is what you're asking about, it is<EMAIL_ADDRESS>

Can you share the code that uses @bull-board?

I'm using NestJS ^7.5.1 by the way, here's the code:
import { MiddlewareConsumer, Module } from '@nestjs/common';
import { Queue } from 'bull';
import { BullModule, InjectQueue } from '@nestjs/bull';
import { createBullBoard } from '@bull-board/api';
import { BullAdapter } from '@bull-board/api/bullAdapter';
import { ExpressAdapter as BullBoardExpressAdapter } from '@bull-board/express';
import { QueueService } from './queue.service';

@Module({
    imports: [
        BullModule.registerQueue(
            {
                name: 'queue1'
            },
            {
                name: 'queue2'
            }
        )
    ],
    providers: [QueueService],
    exports: [QueueService]
})
export class QueueModule {
    private bullBoardExpressAdapter: BullBoardExpressAdapter;
    constructor(
        @InjectQueue('queue1')
        private readonly queueOne: Queue,
        @InjectQueue('queue2')
        private readonly queueTwo: Queue
    ) {
        /* relevant code related to bull-board below*/
        this.bullBoardExpressAdapter = new BullBoardExpressAdapter();
        createBullBoard({
            queues: [
                new BullAdapter(this.queueOne, { readOnlyMode: false }),
                new BullAdapter(this.queueTwo, { readOnlyMode: false })
            ],
            serverAdapter: this.bullBoardExpressAdapter
        });
    }

    configure(consumer: MiddlewareConsumer): void {
        this.bullBoardExpressAdapter.setBasePath('/status/queues');
        const router = this.bullBoardExpressAdapter.getRouter();
        consumer.apply(router).forRoutes('/status/queues');
    }
}

Let me know if it helps,

Thanx for pointing out this issue, looks like it will be solved in the next release (v3.2.4)

@AntoineMaitre can you confirm that v3.2.4 solved your issue?

Thanks for your quick reply and release 🚀
3.2.4 Solved the previous error, but there's a new one though:
node_modules/@bull-board/express/dist/ExpressAdapter.d.ts:1:112 - error TS2307: Cannot find module '@bull-board/api/typings/app' or its corresponding type declarations.

1 import { AppControllerRoute, AppViewRoute, BullBoardQueues, ControllerHandlerReturnType, IServerAdapter } from '@bull-board/api/typings/app';

Checking....

Can you test v3.2.5?

v3.2.5 fixes the compiling errors 🚀
Thank you very much for your reactivity, and nice job !


contributors page title color

please change title color to white

@devvsakib assign this issue to me, please.

@devvsakib assign this issue to me, please.

assigned


upgrade vscode extension versions for Scala

Motivation for this change
to update the vscode extensions for Scala to their latest version. merging this to master is fine because vscode 1.43 is already in the master branch. The minimal vscode version to use these new versions is 1.42.
Things done

Built on platform(s)

[x] NixOS (commit 82b54d490663b6d87b7b34b9cfc0985df8b49c7d)

@jonringer thanks for your feedback. I will create new PR later.


Correct misnamed attribute from hostname to host

I discovered this while running the app in production mode to check that
the smoke tests worked.

Oops, you're quite right.

I wonder if there's a way we can catch this general class of error that isn't 'deploy and hope smoke tests catch it'?

(Good spot though, @tatyree!)

Well, I caught it by running the smoke tests locally, @SteveMarshall...


Train 280 (master)

🚂 :two::eight::zero::train: (master)
https://github.com/dcos/dcos/pull/2169 – Set new --reconfiguration_policy mesos flag.

This commit sets the newly added reconfiguration policy for mesos-agent to additive, in order to allow agents to add new domains without draining all tasks.
DCOS_OSS-1959

https://github.com/dcos/dcos/pull/2167 – Enabled UCR auto image gc for DC/OS.

Enabled UCR auto image gc for dc/os.
This PR builds on top of pull/2165(DCOS_OSS-1945).
DCOS_OSS-1933 Enable UCR basic auto image GC for DC/OS.

https://github.com/dcos/dcos/pull/2158 – bumping metronome to 0.3.1

Upgraded to a released version of Marathon Lib v1.3.13
Updates to dependencies (including an Akka update to fix schedule time wrap around bug)
Added /info end point for metronome version information
PR150 Added /info endpoint
MARATHON_EE-1717 60s min between
MARATHON_EE-1725
MARATHON_EE-1726 Upgrade Marathon libraries and dependencies

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot merge-it

@mesosphere-mergebot merge-it


How to add tourAnchor to elements dynamically?

I have a use case where I need to add tourAnchor attribute to an element that comes in after a http request.  The element is within a *ngFor loop and add the attribute tourAnchor based upon a condition like this:
[attr.tourAnchor]="i==0?'expand':null"
The tourAnchor attribute shows up in html but it is not binding with the step mentioned for it.  The error shown is:
Can't attach to unregistered anchor with id expand
I tried re-initializing the steps again after the http request is completed within the subscribe block:
this.apiService.getJobsList(start, interval).subscribe(data => {
    this.tourService.initialize(steps);
});

This does not do the necessary binding.  Is there any other way to dynamically bind the elements to steps?

The best way to add directives dynamically is to copy the host element and use an *ngIf directive.
So if you had this before:
<div *ngFor="let item of items">
<my-component [attr.tourAnchor]="i==0?'expand':null"></my-component>
</div>

You would change it to this:
<div *ngFor="let item of items">
<my-component  *ngIf="i==0" tourAnchor="expand"></my-component>
<my-component  *ngIf="i!=0"></my-component>
</div>

Thanks for your reply @isaacplmann . That works perfectly!  Just out of curiosity, would you know why the earlier approach would not work?

I agree that would be nice.  Unfortunately, Angular doesn't work that way.  In order for AoT compilation to work, the compiler needs to know up front whether a directive will be applied to an element.  [attr.tourAnchor] just means apply the html attribute tourAnchor to this element, but that happens after the compiler has looked through your templates for selectors that match directives.
You can dynamically create a component using ComponentFactoryResolver and some manual code to wire things up, but I haven't found any way to dynamically add a directive to an existing element/component.

Thanks for your explanation @isaacplmann

Why not
<div *ngFor="let item of items; let i = index">
  <my-component  [tourAnchor]=" i=== 0 ? 'expand' : undefined"></my-component>
</div>

?

You can generate unique step ID, but don't use it
For example:
[tourAnchor]="i === 0 ? 'expand' : 'uniqueFakeStepId_' + i"


All features negative

hi,
i used trained model to extracti feature from mp3s, but all 1000 dimentional features are negative. is this normal?

I also get the same result, all features are negative

I also get the same result, all features are negative


Use a released version in place of master for boosters

Right now we are using the master of boosters GitHub for regression rest. This will sometimes break because of changes in master.
You can check this here https://github.com/fabric8io/fabric8-maven-plugin/blob/master/rt/src/test/java/io/fabric8/maven/rt/SpringbootConfigmapBoosterIT.java#L36
We should always use a released version of booster in regression tests and should do an upgrade of booster version whenever required. We should not always rely on the master. This will help us regularly fixing the regression tests.
This will also help in fixing #1198

Need your inputs, comments or suggestions @hrishin @rohanKanojia

I am not sure whether a release will happen for boosters.
@Ladicek @cescoffier Any inputs on this will be really helpful. Thanks

@piyush1594 I second that. Let's do it. At the same time can we make a plan to move regression test from f8-m-p?

There is already a discussion about separating these tests from fmp : #1155 . Feel free to share your thoughts on it.

@cescoffier @Ladicek Can you please guide if there are any released version of boosters. If yes, then where are released. From Github, it seems like released happened a long time back. TIA

Yes, boosters are being released. The last releasees happened a couple of weeks ago. You might also want to take a look at the booster catalog (https://github.com/fabric8-launcher/launcher-booster-catalog) -- whatever is recorded there is available through the Launcher.

Hey @Ladicek
Thanks for the help. Just one more thing, if you have an idea, which version (community or redhat) is used for OSIO.
Thanks

I think its the community version that is getting used in OSIO, not sure.

@Ladicek @piyush1594 it depends on which UI you are running the tests. The legacy UI in OSIO uses the community versions. In the new UI the user is free to select the version.

Thanks, @gastaldi @Ladicek Right now I have switched the regressions test for latest released community version. #1262 is the PR which will fix this.

As #1262 is merged, closing this.


Improve the visual display of function parameter lists (toggle display of type hints)

Historically, type hints for type checking parameters in a method/function were not used. We are seeing more and more use of type  hints for static and dynamic checking today.
Readability of these functions becomes more difficult when the types are displayed especially as the list of parameters increases. If there was a way to toggle on and off the display of these types, it would improve readability and cognitive understanding of a page of code. The type hints would remain part of the source code but would be optional to display.
cc @brettcannon @tonybaloney

Hi @willingc , just to clarify, you're referring to the window that appears when you hover over a function or method (as shown in the screenshot)?

@tonybaloney That would be an awesome step in  the right direction. Ideally a toggle on the whole file, display or not.


(#274) Update hiera.yaml syntax to version 5

This patch updates the syntax of hiera.yaml file to version 5, as
version 4 is deprecated.

awesome, thanks


Pre merge (3803)

new config props for display of date and date/time

@andi-huber  - could you review this?  I couldn't see another way to have Causeway render dates as "dd-MM-yyyy"

Btw. if you are looking for ISO date format like 2024-12-31, that would by provided by the combination of Locale nds (or e.g. kw-GB) and FormatStyle.SHORT. Which is supported by the framework.

What the requirement is from our users is the same format that they had in v1, namely 24-05-2024.  Can this be done without this PR? I couldn't find a way.
I don't think iso format will be accepted.


Env variables set but "No transport method defined"

Issue Summary
I use environment variables into my docker-compose file to configure Ghost, as explained on the documentation.
NODE_ENV=production
url=https://myblog.example.tld
server__host=<IP_ADDRESS>
server__port=2368

database__client=mysql
database__connection__host=ghost-db
database__connection__user=ghost
database__connection__database=ghost
database__debug=false
database__connection__password=SECRET

mail__transport=STMP
mail__options__port=587
mail__options__host=smtp.example.tld
mail__options__auth__user=smtp_user
mail__options__auth__pass=smtp-pass
<EMAIL_ADDRESS>
imageOptimization__resize=true

Database and mail configuration is set as you can see, but Ghost seems not to use the mail part.
When I click on the test button, it does not work: "Failed to send email. Reason: No transport method defined."

But in the "About Ghost" part, I can see "Mail" set to "SMTP":

To Reproduce

Create a Ghost container built from GitHub code
Start it with environment variables to configure Ghost
Connect to the web interface and click on "test mail" button

Technical details:

Ghost Version: 3.2.0
Node Version: 8.15.0
Browser/OS: Firefox 72
Database: mysql 5.5

You have a typo, STMP should be SMTP :relaxed:

God 🤣
Thanks it was fast as light!

No probs!!


Add contracts submodule

This is used to build and deploy an OS contract to the fleet.
Changelog-entry: Add contracts submodule
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

Can one of the admins verify this patch?

@balena-ci I self-certify!


Update constants.py

Better wording.

Codecov Report

Merging #68 into master will not change coverage.
The diff coverage is n/a.


Network: update wlan0 interface settings

There so many unnecessary changes polluting the patch. Why do you need to change support for two dns servers to one? Why stripping comments, changing order of arguments if it does not add value to the patch? Let's keep it to the bare neccesity and leave all cosmetic changes for a separate patch.

See it more as a draft in conjunction with the network PR on the firmware repo. Based on what we decide it will be reworked or even discarded if there is a better solution at hand.

To address some of your concerns:

Reducing the DNS server to one is intended to reduce the ui size and simplify the code/usage.
The wlandev command needs to be added to select a profile, the hostname command was inconsistent and has been fixed.
Stripping greyed out commands and notes has basically the same intention: simplify and adjust the code to the current wireless interface. Otherwise we would have two different systems. The current webui implementation is not working for 90% of the devices, without any possibility of setting a gpio on the ui.


np.linalg.norm() does not accept axis argument in nopython mode

When I try to run the following
import numba

@jit(nopython = True)
def numba_func(x)
    x_norm = np.linalg.norm(dx, axis = 1)
    return(x_norm)

x = np.ones([3,3])
numba_func(x)

I get InternalError: norm_impl() got an unexpected keyword argument 'axis'
I am running numba 0.28.1 in python 2.7.9.

Thanks for the report. This is true at present, as per the docs http://numba.pydata.org/numba-doc/0.28.1/reference/numpysupported.html#linear-algebra
numpy.linalg.norm() (only the 2 first arguments and only non string values in ord).
Most numpy.linalg support is basic at present as it's only been around for a short while.
Should you develop a fix for this, patches are most welcome :-)
Thanks again...

duplicated https://github.com/numba/numba/issues/2558


[EventRequest] Table 38 “Purchase header”, UpdateAllLineDim[External]

Please add a new publisher event OnUpdateAllLineDimOnBeforeModifyPurchLine as shown in the picture below in the function UpdateAllLineDim in table 38

Please add the corresponding Integration Event In the bottom of the Codeunit.

This event already exist


Enhance the scan delay

Hi
The new version is working perfectly, is it possible to accelerate the scan time?
It's seems to take 10sec each time the bot scan

That's a server limitation. Use more accounts.


Error if more than 7 blinds

If the array passed to get_blinds_state() contains more than 7 blinds, the following error is produced:

Traceback
(most recent call last):
File "jblinds.py", line 11, in
states = client.get_blinds_state(blinds)
File "/home/pi/smartblinds-client/smartblinds_client/smartblinds.py", line 144                                                                                , in get_blinds_state
return self._parse_states(response)
File "/home/pi/smartblinds-client/smartblinds_client/smartblinds.py", line 169                                                                                , in _parse_states
for blind_state in response['data'][key]:
TypeError: 'NoneType' object is not iterable

Doing a bit of digging, it seems that the bridge was returning the following error message:

{'data': {'blindsState': None}, 'errors': [{'path': ['blindsState'], 'message': 'Bridge only supports up to 7 commands at a time', 'locations': [{'line': 3, 'column': 21}]}]}

If I change the example script as follows, the problem is resolved (albeit very inartfully, I have basically zero python skills):

blinds1 = [blinds[0], blinds[1], blinds[2], blinds[3], blinds[4], blinds[5]]
blinds2 = [blinds[6], blinds[7], blinds[8]]
states = client.get_blinds_state(blinds1)
print(states)
states = client.get_blinds_state(blinds2)
print(states)

If someone could fix this in a nicer way that scales, I sure would appreciate it.

Thanks for the detailed report, can't promise a fix right away but when I get a chance I'll address.


Sliced receive buffers

First I would like to thank you for this simple yet powerful library.
It would be great if we could pass a custom MutableByteArray with an offset and length to a receiveMutableByteArraySlice function (symmetric to sendMutableByteArraySlice).
This would allow us to create a giant pinned buffer, and use an offset+size per client when receiving. Hence unlocking better performance for receive operations (for instance, constant in memory if we fix the maximum number of clients in a given program).

I’m glad that you find the library useful!  I am planning on adding a receive function that works the way you describe.


helix-service staging service fabric cluster having disk space problems.

Builds of helix-service have been failing to deploy to staging service fabric cluster for the last few days. Error messages report out-of-space.
Example build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2488102&view=logs&j=c6814a9d-ff0f-5bfa-074d-854f77349740&t=3ec608fc-a2ce-52d7-4169-05c405ccc1dc

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

Hold on this for a bit. Internal discussion indicates it may have been resolved...

Still happening, but use dotnet/dnceng#3226 for the work instead of this issue.


Add linting (with prettier) to hardhat folder

We should have a consistent formatting as the frontend folder in the hardhat folder as well

solved here https://github.com/scaffold-eth/se-2/pull/37


Steps to build

Excuse me if this is not the right place to write, but what are the right steps to build the image and deploy it to a private repository for testing?
I tried to do it on my own but I got some errors. First of all, I had to execute the command chmod +x *.sh to make the sh files executable.
The problem now is that when i try to deploy to a stack, in the logs I see the message /usr/local/bin/run-upgrades.sh: waiting for server to become available... and, after some lines with the same message,
Received TERM|INT signal. Shutting down... MariaDB exited with return code (0)
Is it possible to expose some other ports? I have to use 8080 for another container with tomcat

Hi Dave,
These sounds like implementation issues so this isn't really the right place for these questions, I only intend to support bug fixes and improvements via github. That said...
The run-upgrades.sh error is not a problem, you can ignore those log messages. Since it says "Received TERM|INT" it sounds like Docker signaled the container to shut down and the reason is unknown to me.
It is ok if the internal ports conflict with your other containers, docker lets you map them to other ports. E.g. -p 54321:8080.


feat: remove unnecessary unboxing

Removes unnecessary unboxing, and simplified one conditional.
Submitter checklist

[x] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[x] Recommended: If you participate in Hacktoberfest 2023, maake sure you're signed up there and in the WireMock form
[x] The PR request is well described and justified, including the body and the references
[x] The PR title represents the desired changelog entry
[x] The repository's code style is followed (see the contributing guide)
[x] Test coverage that demonstrates that the change works as expected
[x] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

Can you do a ./gradlew spotlessApply please?


Style and formatting changes

Style and formatting changes to bring codebase to the recommendations here:
https://github.com/golang/go/wiki/CodeReviewComments

I like that, thanks!


removed connection_status field from the status command, use wallet.connected instead to determine if SDK is connected to a wallet server

fixes #3196
related to #3158

@seanyesmunt here's how you can differentiate the states of lbrynet status wallet connection

if wallet.connected has a value, then it's connected.
otherwise:

if startup_status.wallet is false, then sdk is still connecting to wallet servers. it will never stop trying till it connects.
if startup_status.wallet is true, then the sdk used to have a wallet server connection but that dropped and it's still trying to reconnect

does this work for you?


Support 1 or 3 arg in generate_series() UDTF

Which issue does this PR close?

Closes #13615.
Rationale for this change

What changes are included in this PR?

Added some args validation to GenerateSeriesTable
Added step field to GenerateSeriesState, and added support for generating series with custom step

Are these changes tested?

sqllogictests for generate_series() UDTF
Are there any user-facing changes?
No

Thanks @UBarney. Overall looks good to me but some minor comments. cc @2010YOUY01

Thanks @goldmedal for reviewing. All comments have been addressed. Please take another look

Thanks @UBarney


[Додати гурток] The 'Назва' field doesn't have restrictions on entered characters

Environment: Windows, Google Chrome 88.0.4324.190 (64-bit).
Reproducible: always.
Build found: last commit from https://speak-ukrainian.org.ua/dev/clubs
Steps to reproduce

Go to https://speak-ukrainian.org.ua/dev/
Click on 'Додати гурток' button on the main page or in user's private office
Enter less than 5 characters/ more than 100 charachers/ not Ukrainian or English letters in 'Назва' field

Actual result
A club is created if the 'Назва' field contains less than 5 characters/ more than 100 charachers/ not Ukrainian or English letters
Expected result
'Назва' field should contain only Ukrainian and English letters, numbers and reserved characters.  Min 5 characters and max 100 characters should be allowed to be entered.
User story and test case links
User story #70
Labels to be added
"Bug", Priority ("pri: high"), Severity ("severity:medium"), Type ("Functional").

Defects:
The system allows less than 5 and more than 100 characters
Not Ukrainian and English letters allowed (e.g. 'Ü,Ы,ы,Ä,Ö,Э')


Merging ODPi spec-tests back into the master line

We are ready to integrate the spec tests back to the master.

And merging now


Make LLVM lowering deterministic

The inability to get reproducible compiler error output frustrates debugging.

I could be mistaken, but it was my understanding we don't have control over this (without understanding and patching LLVM internals).  If that's true, maybe an issue should be filed against LLVM.

The most likely source of nondeterminism here is the random order that things appear in hash containers from run to run (that's a Swift security feature).  If you want to straighten that out there's probably a .sorted() that could be inserted somewhere.

We can define the order in which Hylo IR functions will be transpiled to LLVM. That will likely make our builds much more deterministic.
Unfortunately we only have partial control over the order in which LLVM will manage it's internal representation, run its optimization passes, etc. That may be another cause of nondeterministic errors which we can't address without patching LLVM.


[FLINK-25268] Support task manager node-label in Yarn deployment

What is the purpose of the change
Now Flink only support application level node label, it's necessary to introduce task manager level node-label on Yarn deployment.
Why we need it?
Sometimes we will implement Flink to support deep learning payload using GPU, so if having this feature, job manager and task managers could use different nodes.
Brief change log
Introduce node-label of task manager level in Yarn deployment.
Verifying this change
Does this pull request potentially affect one of the following parts:

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

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Could you help check this features? @wangyang0918  @KarmaGYZ
Now this PR is just draft, if this feature could be invovled in Flink, i will optimize.
And maybe jobmanager(Yarn application) node label should also be supported.

@KarmaGYZ Could you help review it? Thanks

You can build the doc with mvn clean package -Dgenerate-config-docs -pl flink-docs -am -nsu -DskipTests -Dcheckstyle.skip.

You can build the doc with mvn clean package -Dgenerate-config-docs -pl flink-docs -am -nsu -DskipTests -Dcheckstyle.skip.

Thanks @KarmaGYZ .
Got it. Any other comments on it?

All done @KarmaGYZ Could you help review it again? Thanks

@KarmaGYZ Thanks again.
All done except the instanceof ContainerRequestWithConstructor assertion.
Besides i have checked this PR in our internal Hadoop cluster.

All done @KarmaGYZ Thanks.

@flinkbot run azure


DataFusion upstream PR for: Unparser omit cast to double when translating filter expression

Closed by: https://github.com/apache/datafusion/pull/12609


Module not usable with Terraform >= 0.15 (MySQL)

Hello,
I tried to upgrade module in my code from 4.5.0 to 6.0.0 and I was surprised to see the following error when I applied:
❯ terraform apply -var-file $(terraform workspace show).tfvars

╷
│ Error: Output refers to sensitive values
│
│   on .terraform/modules/mysql/modules/mysql/outputs.tf line 106:
│  106: output "primary" {
│
│ Expressions used in outputs can only refer to sensitive values if the sensitive attribute is true.
╵
╷
│ Error: Output refers to sensitive values
│
│   on .terraform/modules/mysql/modules/mysql/outputs.tf line 116:
│  116: output "instances" {
│
│ Expressions used in outputs can only refer to sensitive values if the sensitive attribute is true.

It seems like due to attributes declared as sensitive in sql_database_instance resource (used in this module), this module is not working correctly with Terraform >= 0.15 because of missing sensitive setting on primary and instances outputs that you find here.
IMO, the fix consists at least on adding sensitive = true to the primary and instances outputs in terraform-google-modules/terraform-google-sql-db/blob/master/modules/mysql/outputs.tf.
I can prepare a small pull request to do this if you're ok with this :-)

Hi @JulienJourdain
TF fixed this bug in 0.15.1. Now only your root modules where you invoke the module need to make this as sensitive. Feel free to reopen if the issue persists.


How to use custom environment without adding them to the repo?

Hello!
I aim to execute MARLLib algorithms using my own MARL environment.
I am following the add_new_env example but also looking at how SMAC has been integrated into MARLLib.
I installed MARLLib through PyPI because I just want to have some files in my repo to demonstrate how to use MARLLib with our environment but it appears that the make_env function requires some config file accessible only by a hardcoded env_config_file_path included in the make_env function.
Did I miss something or is it infeasible for the moment?
I would not mind trying to help find a fix.
Cheers for your nice work putting up this repo.

Temporarily, the configuration path is fixed and must be located within the project's inner path. I acknowledge that this approach is not elegant and will work on making it possible to set the configuration path externally.

Please Check out here. #153

Thanks!


railway=abandoned rendered too prominently

Description
An abandoned railway should be de-emphasized for rendering. Currently it looks pretty much like a normal railway.
Here's abandoned, normal and disused side by side. I can't tell the difference.

Version
2.00-alpha.3.3
What browser are you seeing the problem on? What version are you running?
Firefox v109.0
Steps to reproduce
No response
The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=Bing&datasets=fbRoads,msBuildings&disable_features=boundaries&id=w7651285&map=18.83/32.54243/-86.21143

I think this is a duplicate of #535


Scrolling tab not working for tabs inside tabs

I have a tabs inside tabs, and it its only working on the parent one, I've set the same class for each group of tabs so one call make the magic, it works like a charm, but no on the child tabs.
What can I do?
$(function() {
    $('.nav-tabs').scrollingTabs();
});

Unfortunately, Bootstrap tabs do not support nested tabs.

Workaround
$('.nav-tabs:first').scrollingTabs();
I will elaborate more in the future so it can detect and initialize diferent instances of tabs with scrollingTab. Thanks @mikejacobson for this great plugin!.


HBASE-25441:branch-2.4 add security check for some APIs in RSRpcServices

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  9s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
4m 48s
branch-2.4 passed

+1 :green_heart:
checkstyle
1m 23s
branch-2.4 passed

+1 :green_heart:
spotbugs
2m 26s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 54s
the patch passed

+1 :green_heart:
checkstyle
1m 24s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
19m 52s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

46m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2830

JIRA Issue
HBASE-25441

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 3a5088557cf6 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 90db5e4f99

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/console

versions
git=2.17.1 maven=3.6.3 spotbugs=3.1.12

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
4m 26s
branch-2.4 passed

+1 :green_heart:
compile
1m  7s
branch-2.4 passed

+1 :green_heart:
shadedjars
6m 46s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  8s
the patch passed

+1 :green_heart:
compile
1m  9s
the patch passed

+1 :green_heart:
javac
1m  9s
the patch passed

+1 :green_heart:
shadedjars
6m 50s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
151m 32s
hbase-server in the patch passed.

180m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2830

JIRA Issue
HBASE-25441

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e1357236e625 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 90db5e4f99

Default Java
AdoptOpenJDK-11.0.6+10

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/testReport/

Max. process+thread count
4141 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.4 Compile Tests _

+1 :green_heart:
mvninstall
3m 43s
branch-2.4 passed

+1 :green_heart:
compile
1m  2s
branch-2.4 passed

+1 :green_heart:
shadedjars
5m 57s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
branch-2.4 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 18s
the patch passed

+1 :green_heart:
compile
0m 58s
the patch passed

+1 :green_heart:
javac
0m 58s
the patch passed

+1 :green_heart:
shadedjars
6m  3s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
160m 14s
hbase-server in the patch passed.

185m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2830

JIRA Issue
HBASE-25441

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 36720a284ac2 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.4 / 90db5e4f99

Default Java
AdoptOpenJDK-1.8.0_232-b09

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/testReport/

Max. process+thread count
3918 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2830/1/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Add support for passing arguments to xacro files

Currently, there's no way to load a xacro file that expects command line arguments.
convert_xacro_to_urdf expects only a filename, changing the signature is an API breaking change, do you have a better solution or are you ok with breaking the API?
I'm more than happy to implement it!

Hi,
I do not like to change API, but you can add new API like *_with_args.
Does it works in your case?
2023年2月12日(日) 6:45 Jafar @.***>:

Currently, there's no way to load a xacro file that expects command line
arguments.
convert_xacro_to_urdf
https://github.com/openrr/urdf-rs/blob/main/src/utils.rs#L10-L30
expects only a filename, changing the signature is an API breaking change,
do you have a better solution or are you ok with breaking the API?
I'm more than happy to implement it!
—
Reply to this email directly, view it on GitHub
https://github.com/openrr/urdf-rs/issues/60, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABSSJVTIG7WOKWPMOEXXBLWXAB63ANCNFSM6AAAAAAUY5H6HM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Ran cargo fmt

Is there any specific reason the code is manually formatted :smile:

I likes tabs :-)

Gofmt's style is no one's favorite, yet gofmt is everyone's favorite.

:stuck_out_tongue_closed_eyes:
But feel free to set your own config https://github.com/rust-lang/rustfmt/blob/master/Configurations.md

You are right. I will check it.

I added a config... See commit 08b64b1


Changing style of the website.

Describe the feature
To change the background and other styles of the website to make it look more pleasing and appealing.
Adding background images related to engineering.
To change font style to make it look good.
Adding dark mode feature to the website for the users who prefer using websites in dark mode.
To add the logo for this website. (the logo is not present, logo is the main part of any project, it makes a good impression)
Add ScreenShots
The dark mode feature.

The page is not styled properly.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'24 contributor
[X] I want to work on this issue

@Shivangi015 Assigned :+1:

Thankyou so much


"The Platform for project 'serial port.vcxproj' is invalid. Platform='x64'.

This has been reported by a user of a project of my that use serialport. This is what I know so far:
When building on Windows 7 (or 8) 64 bit the following error:  "The Platform for project 'serial port.vcxproj' is invalid. Platform='x64'.
Windows 7 or 8 64bit
node js v0.8.9 (64 bit)
python 2.7.x
Visual Studio 2010 (or 2012, which I understand there are other possible issues with)
Windows 7 SDK 64bit

python 2.7.9 + nodejs 0.12.7 +npm 2.11.3 +windows 64 + VC++ Express 2010
err
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.Cpp.InvalidPlatform
.Targets(23,7): error MSB8007: The Platform for project 'hcaptha.vcxproj' is in
valid.  Platform='x64'. You may be seeing this message because you are trying t
o build a project without a solution file, and have specified a non-default Pla
tform that doesn't exist for this project. [C:\Users\adam\AppData\Roaming\npm\n
ode_modules\ccap\build\hcaptha.vcxproj]
?


Installed minified (--prod) APK but gets stuck on Splash screen, unable to load in Chrome Dev Tools

Ionic Info
Run ionic info from a terminal/cmd prompt and paste the output below.
cli packages: (C:\Users\bengrah\AppData\Roaming\npm\node_modules)

    @ionic/cli-plugin-proxy : 1.5.8
    @ionic/cli-utils        : 1.19.2
    ionic (Ionic CLI)       : 3.20.0

global packages:

    cordova (Cordova CLI) : 8.0.0

local packages:

    @ionic/app-scripts : 3.1.8
    Cordova Platforms  : none
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 26.1.1
    Node              : v8.9.4
    npm               : 5.7.1
    OS                : Windows 10

Environment Variables:

    ANDROID_HOME     : C:\Android\android-sdk
    HTTP_PROXY       : http://webproxy.millerextra.com:8081
    http_proxy       : http://webproxy.millerextra.com:8081
    HTTPS_PROXY      : not set
    https_proxy      : not set
    IONIC_HTTP_PROXY : http://webproxy.millerextra.com:8081
    PROXY            : not set
    proxy            : not set

Misc:

    backend : pro

Describe the Bug
I've built an apk file using the ionic cordova build android --prod --release command. I'm able to successfully install the APK on an Android 5.1.1 Samsung Galaxy Tab (Active). When I start the app up, the splash screen appears but nothing else happens. I'm able to install this same APK on other devices and I'm able to get past the splash screen as expected. One other oddity is that when trying to inspect the device via Chrome Dev Tools, I'm able to Inspect the device but the app code / sources / HTML doesn't load. Nothing happens. So I'm not able to see if there are any errors at this point.
Steps to Reproduce
Steps to reproduce the behavior:

Create a new prod release apk by running ionic cordova run android --prod --release in your Ionic project
Sign the newly created APK
Install the APK on a device
Tap the app icon to start it up from the app drawer
App should load the Splash screen at this point, but it never gets past this screen.

Related Code
If you are able to illustrate the bug with an example, please provide a sample application via an online code collaborator such as StackBlitz, or GitHub.
Expected Behavior
Upon starting up the app, the Splash screen should appear for 5 seconds before loading up the main screen.
Additional Context
I have attempted to debug this via logcat but there isn't much useful here neither. What follows is a capture of what happens when I tap the app icon to start the app up, to the point where the logging output stops.
I/Timeline(11021): Timeline: Activity_launch_request id:com.mh.sma time:9551847 V/WindowManager( 1087): addAppToken: AppWindowToken{3c03bff5 token=Token{1935492c ActivityRecord{2174e8df u0 com.mh.sma/.MainActivity t60}}} to stack=1 task=60 at 0 V/WindowManager( 1087): Adding window Window{36b591c4 u0 d0 Starting com.mh.sma} at 4 of 13 (after Window{5d813e u0 d0 com.sec.android.app.launcher/com.android.launcher2.Launcher}) I/ActivityManager( 1087): Start proc 25863:com.mh.sma/u0a170 for activity com.mh.sma/.MainActivity D/ActivityManager( 1087):  Launching com.mh.sma, updated priority D/StatusBarManagerService( 1087): manageDisableList userId=0 what=0x0 pkg=Window{36b591c4 u0 d0 Starting com.mh.sma} E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/files/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/files E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/cache/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/cache E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/files/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/files E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/cache/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/cache V/WindowManager( 1087): Adding window Window{1a3aed92 u0 d0 com.mh.sma/com.mh.sma.MainActivity} at 4 of 14 (before Window{36b591c4 u0 d0 Starting com.mh.sma}) D/StatusBarManagerService( 1087): manageDisableList userId=0 what=0x0 pkg=Window{1a3aed92 u0 d0 com.mh.sma/com.mh.sma.MainActivity} V/WindowManager( 1087): Adding window Window{3555b60 u0 d0 com.mh.sma/com.mh.sma.MainActivity} at 4 of 15 (before Window{1a3aed92 u0 d0 com.mh.sma/com.mh.sma.MainActivity}) I/Timeline( 1087): Timeline: Activity_windows_visible id: ActivityRecord{2174e8df u0 com.mh.sma/.MainActivity t60} time:9552746 D/StatusBarManagerService( 1087): manageDisableList userId=0 what=0x0 pkg=Window{1a3aed92 u0 d0 com.mh.sma/com.mh.sma.MainActivity} E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/files/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/files E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/files/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/files E/Vold    (  320): Failed to find mounted volume for /storage/extSdCard/Android/data/com.mh.sma/cache/ W/ContextImpl(25863): Failed to ensure directory: /storage/extSdCard/Android/data/com.mh.sma/cache

What is your package.json?

{
"name": "site-manager-app-upgraded",
"version": "0.0.1",
"author": "Ionic Framework",
"homepage": "http://ionicframework.com/",
"private": true,
"scripts": {
"clean": "ionic-app-scripts clean",
"build": "ionic-app-scripts build",
"lint": "ionic-app-scripts lint",
"ionic:build": "ionic-app-scripts build",
"ionic:serve": "ionic-app-scripts serve"
},
"config": {
"ionic_source_map": "source-map"
},
"dependencies": {
"@angular/animations": "^5.2.11",
"@angular/common": "^5.0.3",
"@angular/compiler": "^5.0.3",
"@angular/compiler-cli": "^5.0.3",
"@angular/core": "^5.0.3",
"@angular/forms": "^5.0.3",
"@angular/http": "^5.0.3",
"@angular/platform-browser": "^5.0.3",
"@angular/platform-browser-dynamic": "^5.0.3",
"@ionic-native/android-permissions": "^4.11.0",
"@ionic-native/app-version": "^4.11.0",
"@ionic-native/barcode-scanner": "^4.11.0",
"@ionic-native/camera": "^4.11.0",
"@ionic-native/core": "^4.11.0",
"@ionic-native/date-picker": "^4.11.0",
"@ionic-native/deeplinks": "^4.11.0",
"@ionic-native/device": "^4.11.0",
"@ionic-native/device-feedback": "^4.11.0",
"@ionic-native/file": "^4.11.0",
"@ionic-native/file-opener": "^4.11.0",
"@ionic-native/file-transfer": "^4.11.0",
"@ionic-native/header-color": "^4.11.0",
"@ionic-native/keyboard": "^4.11.0",
"@ionic-native/mobile-accessibility": "^4.11.0",
"@ionic-native/native-storage": "^4.16.0",
"@ionic-native/network": "^4.11.0",
"@ionic-native/open-native-settings": "^4.11.0",
"@ionic-native/screen-orientation": "^4.11.0",
"@ionic-native/secure-storage": "^4.11.0",
"@ionic-native/social-sharing": "^4.11.0",
"@ionic-native/splash-screen": "^4.11.0",
"@ionic-native/sqlite": "^4.11.0",
"@ionic-native/status-bar": "^4.11.0",
"@ionic/storage": "^2.0.1",
"cordova-android": "6.3.0",
"cordova-android-support-gradle-release": "^1.4.5",
"cordova-open-native-settings": "^1.5.1",
"cordova-plugin-android-permissions": "^1.0.0",
"cordova-plugin-app-version": "^0.1.9",
"cordova-plugin-camera": "^4.0.3",
"cordova-plugin-console": "^1.1.0",
"cordova-plugin-datepicker": "^0.9.3",
"cordova-plugin-device": "^2.0.2",
"cordova-plugin-file": "^6.0.1",
"cordova-plugin-file-opener2": "^2.0.19",
"cordova-plugin-file-transfer": "^1.7.1",
"cordova-plugin-geolocation": "^4.0.1",
"cordova-plugin-headercolor": "^1.0.0",
"cordova-plugin-ionic-webview": "^2.2.0",
"cordova-plugin-logtofile": "^1.1.2",
"cordova-plugin-native-settings": "^1.0.0",
"cordova-plugin-nativestorage": "^2.3.2",
"cordova-plugin-network-information": "^2.0.1",
"cordova-plugin-root-detection": "^0.1.1",
"cordova-plugin-screen-orientation": "^3.0.1",
"cordova-plugin-secure-storage": "^2.6.8",
"cordova-plugin-splashscreen": "^5.0.2",
"cordova-plugin-statusbar": "^2.4.2",
"cordova-plugin-stetho-android": "0.0.1",
"cordova-plugin-whitelist": "^1.3.3",
"cordova-plugin-x-socialsharing": "^5.4.1",
"cordova-sqlite-storage": "^2.5.0",
"es6-promise-plugin": "^4.2.2",
"hammerjs": "^2.0.8",
"ionic-angular": "3.9.2",
"ionic-img-viewer": "^2.9.0",
"ionic-plugin-deeplinks": "^1.0.17",
"ionic-plugin-keyboard": "^2.2.1",
"ionicons": "3.0.0",
"phonegap-plugin-barcodescanner": "^8.0.0",
"phonegap-plugin-mobile-accessibility": "^1.0.5",
"rxjs": "5.5.11",
"sw-toolbox": "3.6.0",
"zone.js": "^0.8.26"
},
"devDependencies": {
"@ionic/app-scripts": "3.2.0",
"cordova-plugin-root-detection": "^0.1.1",
"typescript": "2.4.2"
},
"description": "An Ionic project",
"cordova": {
"plugins": {
"cordova-plugin-device": {},
"cordova-plugin-logtofile": {},
"cordova-plugin-console": {},
"cordova-plugin-whitelist": {},
"cordova-plugin-network-information": {},
"cordova-plugin-geolocation": {},
"cordova-plugin-splashscreen": {},
"cordova-plugin-camera": {},
"phonegap-plugin-barcodescanner": {},
"cordova-plugin-ionic-webview": {},
"cordova-plugin-datepicker": {},
"cordova-plugin-app-version": {},
"cordova-plugin-statusbar": {},
"cordova-plugin-file": {},
"cordova-plugin-file-opener2": {},
"ionic-plugin-keyboard": {},
"cordova-plugin-file-transfer": {},
"cordova-open-native-settings": {},
"cordova-sqlite-storage": {},
"cordova-android-support-gradle-release": {
"ANDROID_SUPPORT_VERSION": "26.+"
},
"cordova-plugin-x-socialsharing": {},
"cordova-plugin-android-permissions": {},
"ionic-plugin-deeplinks": {
"URL_SCHEME": "mhsma",
"DEEPLINK_SCHEME": "https",
"DEEPLINK_HOST": "mhsma.com",
"ANDROID_PATH_PREFIX": "/",
"ANDROID_2_PATH_PREFIX": "/",
"ANDROID_3_PATH_PREFIX": "/",
"ANDROID_4_PATH_PREFIX": "/",
"ANDROID_5_PATH_PREFIX": "/",
"DEEPLINK_2_SCHEME": " ",
"DEEPLINK_2_HOST": " ",
"DEEPLINK_3_SCHEME": " ",
"DEEPLINK_3_HOST": " ",
"DEEPLINK_4_SCHEME": " ",
"DEEPLINK_4_HOST": " ",
"DEEPLINK_5_SCHEME": " ",
"DEEPLINK_5_HOST": " "
},
"cordova-plugin-secure-storage": {},
"cordova-plugin-root-detection": {},
"phonegap-plugin-mobile-accessibility": {},
"cordova-plugin-screen-orientation": {},
"cordova-plugin-headercolor": {},
"cordova-plugin-nativestorage": {},
"com.outsystems.mobile.stetho": {}
},
"platforms": [
"android"
]
}
}
Miller Homes Limited Registered in Scotland - SC255429
2 Lochside View, Edinburgh Park, Edinburgh, EH12 9DH
Disclaimer: The Information in this e-mail is confidential and for use
by the addressee(s) only. It may also be privileged. If you are not the
intended recipient please notify us immediately on +44 (0)<PHONE_NUMBER>
and delete the message from your computer: you may not copy or forward
it, or use or disclose its contents to any other person. We do not
accept any liability or responsibility for: (1) changes made to this
email after it was sent, or (2) viruses transmitted through this email
or any attachment.

Erich Stark<EMAIL_ADDRESS>02/11/2018 20:31 >>>
What is your package.json?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
(
https://github.com/ionic-team/ionic/issues/14442#issuecomment-435490784)
, or mute the thread
(
https://github.com/notifications/unsubscribe-auth/AK6ZwqziaK77HILJ4V8RHEE0sCplQe60ks5urKufgaJpZM4T2NMP)
.


Maximum character line slightly wrong

In Spyder 5.1.1, the maximum character line is slightly moved to the left, so that is does cross the characters at the maximum allowed position:

Same line of code in Spyder 3.3.6, maximum character line is displayed correctly:

Hi @ccordoba12 , thanks for the info.
Do you know maybe, where to look in the code?

It could be in spyder/plugins/editor/widgets/codeeditor.py (not really sure though).

Well, I also noticed this and already wanted to open a new issue,but there were more pressing issues and now @andprosoft beat me to it!

I'd be happy to submit a PR with a simple fix for this if no one else is on it (@andprosoft ?)

@rhkarls No problems, go for it! ;)


Fix GradientDescent Opt to not require FiniteDiff type

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
#2175
What are the significant changes in functionality due to this change request?
This PR removes the requirement for GradientDescent optimizer to be of type="FiniteDifference"

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@wangcj05 It looks like SimulatedAnnealing was removed in the patch. I'm not familiar with SA, is this just a type of GradientDescent? Or should I add that type back in?

@wangcj05 It looks like SimulatedAnnealing was removed in the patch. I'm not familiar with SA, is this just a type of GradientDescent? Or should I add that type back in?

sorry Daylan. I added a patch that you can apply. SimulatedAnnealing is supposed to be In the validation dictionary as well.

@dylanjm also doc/workshop/optimizer/Inputs/1_grad_desc.xml  should be updated. Sorry I missed this.

Only waiting on tests to pass before merging. If tests pass without further changes, feel free to merge.


Local api latest version via docker is worst than the api version

I was trying to use unstructured to extract a table from pdf but when I used the open source api and the api from the site I found out that the local version is really worst than the other version in table extraction, is this normal ?

I used the same strategy and model for both : hi_res, yolox

Hi there! Our paid API includes better performance and our latest models, so this is expected.

@awalker4 Understandable. Is there any comparison table or can you provide one, which choose which differences in models or performance there is between self-hosted and the SaaS version?

Thanks for linking the docs. But it doesn't show numbers or actual model names :/


Dropzizard Metrics integration

We need at least client and server decorators.

/cc @blmarket

Implemented in 0.10.0.Final


Controller: minor tweaks

incorporated Darren's feedback: journal
and missing commit from the yesterdays merge

@yasker I addressed you comments; squashed and rebased

take a look at the recent patches. If that's what you meant I'll squash/rebase

LGTM.

rebased

renamed


Updates NEWS for new release

This is for the 1.0.2 branch only and, since this is a NEWS update for the new release the 24hr rule does not apply.

Pushed. Thanks.


User would like to manage tun devices with NetworkManager

Currently all tun devices are unmanaged in NetworkManager, mainly to have resin-vpn unmanaged. But that's too wide blacklist, as users then cannot use other tun devices themselves with NetworkManager.
Forums

Any news on this? I suppose, managing tun devices via NetworkManager makes sense and there are more potentially more users benefiting from it.


Update Youtube Publication documentation

The documentation for publishing to youtube is a bit outdated. I tried updating it based on my experiences with setting it up.

I also think that the two restarts in the guide aren't actually necessary, so maybe get rid of those as well?

Did you successfully set this up without restarting?

Yes I did. The URL that is mentioned just appears in the log and you can continue to use Opencast even before going through that.
However, it is true that if you (re-)start Opencast without having completed that step, stuff won't start up correctly. 🤔


update(README): add repo badges

What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
This PR introduces the scope and status badges. See https://github.com/falcosecurity/evolution/issues/271 for more details.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:

@zuc: The label(s) area/documentation cannot be applied, because the repository doesn't have them.

In response to this:

What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
This PR introduces the scope and status badges. See https://github.com/falcosecurity/evolution/issues/271 for more details.
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, zuc
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:

OWNERS [jasondellaluce,zuc]

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


GCM: Temporary Whitelist currently does not seem to work

Some time ago, GMS Core gained the ability to put an app into the temporary whitelist when a push notification arrived (see the corresponding feature request).
This does not seem to work anymore after upgrading to v<IP_ADDRESS>315.
I have some older logcats when it still worked.
Old behavior when a push notification arrived:

Logcat with message GmsGcmMcsSvc: Adding app <package name> for userId 0 to the temp whitelist
Command adb shell dumpsys deviceidle tempwhitelist displayed package in the temporary whitelist shortly after arrival of the push notification

Current behavior:

Neither seems to happen

Note that I artificially put my smartphone into doze by adb shell dumpsys deviceidle force-idle as described in the Google Documentation. Moreover, microg has the correct permissions: I have put the corresponding file into /system/etc/permissions as described here.

I have taken a quick look at the recent commits related to GCM, and it seems that apps are indeed not always whitelisted, see here.


Added contact details to CoC

@peterjwest - I don't now if you want to add your details too (asked in slack earlier)

:+1:


release new version to capture Rails 5.1 Deprecation Warning patch

Context
acts-as-taggable-on is a dependency in Spree
getting the following when bumping to Rails 5.1
DEPRECATION WARNING: Passing a class to the `class_name` is deprecated and will raise an ArgumentError in Rails 5.2. It eagerloads more classes than necessary and potentially creates circular dependencies. Please pass the class name as a string: `has_many :tag_taggings, class_name: 'ActsAsTaggableOn::Tagging'` (called from block in <module:ActsAsTaggable> at /spree/core/app/models/concerns/spree/acts_as_taggable.rb:6)
DEPRECATION WARNING: Passing a class to the `class_name` is deprecated and will raise an ArgumentError in Rails 5.2. It eagerloads more classes than necessary and potentially creates circular dependencies. Please pass the class name as a string: `has_many :tags, class_name: 'ActsAsTaggableOn::Tag'` (called from block in <module:ActsAsTaggable> at /spree/core/app/models/concerns/spree/acts_as_taggable.rb:6)

https://github.com/spree/spree/blob/master/core/app/models/concerns/spree/acts_as_taggable.rb

Possible Fix
A new version release should solve the problem as the fix was patched in a recent PR here #813

@rbritom Let prepare a release .

So is there a release planned to drop this warning?

Any thoughts on this?

So is there a release planned to drop this warning?

Please go to here : Pull Request #887 to see all the ready to merge and to use solutions to work with Rails 5.2! It is fully tested and ready to go! It is just missing to merge the changes into the main project!


Intellisense stops working after a brief period

Issue Type: Bug
Editing C# using OmniSharp, I can use Intellisense for a brief period of time, but after ctrl-clicking to follow a few links and then returning to the first document, intellisense fails and then stops working for all documents.
This happened some time in the last two weeks, and started affecting everyone in the office at the same time. We use VSCode to edit .csharp projects generated by Unity 2018.2.
I've tried using and old version on OmniSharp (1.30.0) but the issue persists.


Validates Flaw Fields with Visual Feedback

I'd suggest updating EditableDate and EditableText to avoid error messages overlaping on the form fields. (Also mentioned on #105 (review))

I noticed the same thing and wanted to huddle about the UI convention, about how to handle the error message indicators in the UI. Should we just show a hoverable icon that shows the error message in the UI?

However for this case I think that showing same validation messages twice can be kind of redundant. My preference would be to keep the toast for specific details of the validation and in the form just mark the related fields (like Public Date is currently doing).

I agree--it could be nice to have the feedback as the user types. What do you think about the hoverable error icon idea above?

I agree--it could be nice to have the feedback as the user types. What do you think about the hoverable error icon idea above?

The hoverable icon is a very good idea, it could be a clean way to display the info/messages.
I definitely agree on a huddle to define some UI conventions.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2892

Questions ?
Please refer to the Backport tool documentation


Add Mouse and IE10/Win8/WinPhone8 (MSPointer) support

I found the existing MSPointer solutions to be a bit heavyweight, so here is my contribution to the project. A more streamlined approach to adding support for both mouse and MSPointer events.
The priority order for listening to events is (based on feature detection in the browser):

touch[start|move|end]
MSPointer[Down|Move|Up]
mouse[down|move|up]

The addition of -ms-touch-action is necessary in CSS to prevent the default scrolling behaviors; setting the value to 'pan-y' allows for you to still vertically scroll the page by tapping on the swipe element, while horizontal swiping will navigate through the slides as expected. If your carousel is arranged vertically, instead, you can adjust this value as appropriate for the desired behavior.
Furthermore, I suppress 'click' events on the swipe element (for mouse/MSPointer events). When swiping, I found the click event was firing, and propagating up the page causing undesired side effects (mostly with jQuery Mobile and a fixed header).
Hopefully you'll find this useful to merge. I also appreciate any feedback on how to improve upon these changes.

Not working perfectly in Chrome.
The mouse get stack to the slider and whenever you move it, even without clicking to drag, it drags the slider right and left.

@alvarotrigo I'm using this on Chrome 43 with a mouse without issue. Are you sure it's not something else in your JS or HTML that's interfering?

Im having an issue while using media queries with "Swipe".
If i open my website in "tablet" mode, the swipe works in Mobile and Tablet forms, Desktop wont.
BUT, if i save my files again in the text editor and open them in Desktop mode, they work, but not in Mobile and Tablet.

Is this merge request going to be granted ? It would really help

Any updates on this feature? Would be nice to re-implement a similar update I think.

For people looking for a solution for this: https://github.com/lyfeyaj/swipe
Its a new repository that is being maintained and has this feature OOB. Controllable via the prop draggable