Better TypeScript type imports

Problem
We’ve been seeing a lot of issues around importing TypeScript types in projects with our import scanner. In most cases, neither the problem nor solution is clear:
import { anything } from 'csstype';

👆 In this example, csstype doesn’t import anything other than TypeScript types. But rather than surface that error to the user with a friendly error message, we give them the following:
 ENOENT: no such file or directory, open …/node_modules/csstype/index.js

That’s not clear! We should help users figure out what the root cause is.
Possible Solution
But figuring that out isn’t so easy. We’d need to make our import scanner a bit smarter by doing any/all of the following:

Checking whether an import exists (if it’s relative)
Checking whether an import is of a TypeScript type

And then simply skipping those instances (and optionally throwing a warning for either/both).

Note that this will also be automatically solved by tackling this: https://github.com/pikapkg/snowpack/issues/475

Note that this will also be automatically solved by tackling this: #475 I lied, in dev we would still need to support when the user imports a package that is TS only.
I think it would be fair to just ignore a package during installation that has no "main" entrypoint but does have a "types"/"typings" entrypoint. Thoughts?


settings: Rename display_settings.hbs to preferences.hbs.

Finished renaming display_settings.hbs to preferences.hbs.
Fixes part of zulip#26874.

this pull request:
Renames display_settings.hbs to preferences.hbs.
Changed Files:
web/templates/settings/preferences.hbs(File name changed from display_settings.hbs to preferences.hbs)
web/templates/settings/organization_user_settings_defaults.hbs
web/templates/settings/user_display_settings.hbs

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@sahil839 could you please review this one as well?

Looks good to me. There are only a few template files left to be renamed which should be easy to complete.

Merged, thanks @Jai0401! you can probably do the remaining files all in one PR.


Wrong index for existing icon reference due to Async operation

I'm using https://github.com/kisenka/svg-sprite-loader in one of our projects which uses this project under the hood. Issue that I have is that sometimes on build I get incorrect set of icons (when there are duplicates).
So after debugging, I've spotted the source of problem. The issue is caused by incorrect index of icon in array due to asynchronous operations. I have not found contributing guide so I'll describe issue here
If you would look at source code lines 51-55
https://github.com/JetBrains/svg-mixer/blob/v1/packages/svg-baker/lib/compiler.js#L51
you will see that it is storing index of current element in array.
Later, there is an asynchronous operation
https://github.com/JetBrains/svg-mixer/blob/v1/packages/svg-baker/lib/compiler.js#L57
where this index is used
https://github.com/JetBrains/svg-mixer/blob/v1/packages/svg-baker/lib/compiler.js#L64
we update item be previously stored index and than call sort which can totally change order of items and all other "addSymbol" calls which have "existingIndex" already calculated but wait for their async task to end can end up with wrong index.
My proposal is to move lines 51 through 55 inside of "SpriteSymbol.create" in current code it would be line 58 or even better on line 63, so we don't execute code that won't be used (in case it's nonexisting icon). By doing this we can guarantee that index is calculated correctly when it is used and nothing can mess it up.
Hope my point is clear, unfortunately it's really hard to create test case to reproduce this issue, but I think you would agree that my arguments makes sense.
Thank you in advance,
Vladimir

@esjs hi! Thanks for detailed report. Could you please make a pull request with described modifications?

Hi, @kisenka
Do you have any updates on it? This bug is affecting svg-sprite-loader.
https://github.com/kisenka/svg-sprite-loader/issues/328
Thank you for your time.

Fixed in<EMAIL_ADDRESS>please update


Channel should be notified when user completes an action

With much pomp and circumstance 🎉

Edward Elgar or otherwise


[bug] Overflow for long content

Hi,
Using the following incantation:
SimpleUrlPreview(
    previewContainerPadding:
        const EdgeInsets.only(top: 10, left: 46),
    bgColor: Colors.white,
    textColor: Colors.black,
    url: "https://giphy.com/gifs/crazy-the-simpsons-halloween-eaECZB7V6GACc")

I get the following error:
======== Exception caught by rendering library =====================================================
The following assertion was thrown during layout:
A RenderFlex overflowed by 6.0 pixels on the bottom.

The relevant error-causing widget was:
  SimpleUrlPreview file:///Users/sstarkey/Synced/dev/dreamful-service/client/mobile/lib/facets/chat_facet.dart:324:27
The overflowing RenderFlex has an orientation of Axis.vertical.
The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex.

Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size.
This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView.

The specific RenderFlex in question is: RenderFlex#87db2 relayoutBoundary=up19 OVERFLOWING
...  parentData: offset=Offset(8.0, 8.0) (can use size)
...  constraints: BoxConstraints(w=192.5, 0.0<=h<=96.0)
...  size: Size(192.5, 96.0)
...  direction: vertical
...  mainAxisAlignment: spaceEvenly
...  mainAxisSize: max
...  crossAxisAlignment: start
...  textDirection: ltr
...  verticalDirection: down
◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
====================================================================================================

Would much prefer the content not to wrap, but instead truncate. Can we make that a configuration option?

Have fixed this overflow bug, in case of long description lines and when padding is given(use version 1.1.1).
For this you also have 2 configuration options:
Either provide "descriptionLines: 2," in case you are okay with less number of description lines.
Else best recommended way will be to increase the previewHeight, using "previewHeight: 150,".

Have fixed this overflow bug, in case of long description lines and when padding is given(use version 1.1.1).
For this you also have 2 configuration options:
Either provide "descriptionLines: 2," in case you are okay with less number of description lines.
Else best recommended way will be to increase the previewHeight, using "previewHeight: 150,".

Let me know if this fixes your problem/any other feedback!

Let me know if this fixes your problem/any other feedback!

That works! Now I'm looking into how I can customize font size. I'll submit a PR for that.

That works! Now I'm looking into how I can customize font size. I'll submit a PR for that.


[SUPPORT] Slow file listing after update to Hudi 0.10.0

Description
I have two tables with large amount of partitions (~300k). Both contain almost the same data, but were created and updated
with slightly different configurations and versions of Hudi. For some reason I see a significant time difference in file
listing when reading both tables. A new table spends much more time listing files in many instants, when in the other
table there are none (please see logs below).
The first table is managed by Hudi 0.8.0. It was created with a few INSERT commits and then updated daily with UPSERT
operation. Table is auto cleaned after each commit.
Hudi configuration:
 HoodieWriteConfig.TABLE_NAME                           -> "table_v1",
 DataSourceWriteOptions.RECORDKEY_FIELD_OPT_KEY         -> "event_id",
 DataSourceWriteOptions.PRECOMBINE_FIELD_OPT_KEY        -> "generated_at",
 DataSourceWriteOptions.OPERATION_OPT_KEY               -> DataSourceWriteOptions.UPSERT_OPERATION_OPT_VAL,
 DataSourceWriteOptions.TABLE_TYPE_OPT_KEY              -> DataSourceWriteOptions.COW_TABLE_TYPE_OPT_VAL,
 DataSourceWriteOptions.PARTITIONPATH_FIELD_OPT_KEY     -> "date,source,type",
 DataSourceWriteOptions.KEYGENERATOR_CLASS_OPT_KEY      -> classOf[ComplexKeyGeneratorWithLowerCasePartitionPath].getName,
 DataSourceWriteOptions.HIVE_STYLE_PARTITIONING_OPT_KEY -> "true",
 HoodieCompactionConfig.PARQUET_SMALL_FILE_LIMIT_BYTES  -> 200.mb.toBytes.toLong.toString,
 HoodieStorageConfig.PARQUET_FILE_MAX_BYTES             -> 1.gb.toBytes.toLong.toString,
 DataSourceWriteOptions.HIVE_SYNC_ENABLED_OPT_KEY       -> "false",
 HoodieMetadataConfig.METADATA_ENABLE_PROP              -> "true",
 HoodieWriteConfig.UPSERT_PARALLELISM                   -> "15000"

The second table was created after application pipeline was migrated to Hudi 0.10.0. The table was created with a few
INSERT_OVERWRITE commits and then updated daily with UPSERT operation. Table auto clean is disabled, because cleaning operation suffered from long file listing times (it always took ~3 hours). Instead the table is cleaned with org.apache.hudi.utilities.HoodieCleaner later and takes about 30 minutes.
Hudi configuration:
 HoodieWriteConfig.TBL_NAME.key                         -> "table_v2",
 KeyGeneratorOptions.RECORDKEY_FIELD_NAME.key           -> "event_id",
 HoodieWriteConfig.PRECOMBINE_FIELD_NAME.key            -> "generated_at",
 DataSourceWriteOptions.OPERATION.key                   -> DataSourceWriteOptions.UPSERT_OPERATION_OPT_VAL,
 DataSourceWriteOptions.TABLE_TYPE.key                  -> DataSourceWriteOptions.COW_TABLE_TYPE_OPT_VAL,
 KeyGeneratorOptions.PARTITIONPATH_FIELD_NAME.key       -> "date,source,type",
 HoodieWriteConfig.KEYGENERATOR_CLASS_NAME.key          -> classOf[ComplexKeyGenerator].getName,
 KeyGeneratorOptions.HIVE_STYLE_PARTITIONING_ENABLE.key -> "true",
 HoodieCompactionConfig.PARQUET_SMALL_FILE_LIMIT.key    -> 192.mb.toBytes.toLong.toString,
 HoodieStorageConfig.PARQUET_MAX_FILE_SIZE.key          -> 256.mb.toBytes.toLong.toString,
 DataSourceWriteOptions.HIVE_SYNC_ENABLED.key           -> "false",
 HoodieMetadataConfig.ENABLE.key                        -> "true",
 HoodieWriteConfig.UPSERT_PARALLELISM_VALUE.key         -> "15000",
 HoodieWriteConfig.COMBINE_BEFORE_UPSERT.key            -> "false",
 HoodieCompactionConfig.AUTO_CLEAN.key                  -> "false"

Only differences I can see between both tables are:

use of different Hudi versions (0.8.0 vs 0.10.0)
different output parquet file sizes
disabled auto clean
use of INSERT_OVERWRITE instead of INSERT during initial backfill

I would appreciate help answering a few questions:

Why clean operation is much slower (minutes vs hours) between Hudi 0.8.0 and 0.10.0? I know it's because of number of
partitions, but is it possible to bring old performance with some configuration changes?
Why file listing times for both tables are so different? How could it be fixed?

Thanks!
How tables are read
I cleaned both tables and read from them a few partitions using Hudi 0.10.0. I disabled table metadata and
provide paths to specific partitions in READ_PATHS.
Example:
spark.read.format("org.apache.hudi").
  option("hoodie.metadata.enable", "false").
  option("hoodie.datasource.read.paths", "s3://bucket/table_v1/date=2021-12-30/source=test/type=test,s3://bucket/table_v1/date=2021-12-31/source=test/type=test").
  load()

Expected behavior
It used to take a few seconds to list files in provided partitions, but now it takes minutes.
Environment Description

Hudi version : 0.10.0
Spark version : 3.1.1
Hadoop version : 3.2.1
Storage : S3
Running on Docker? : no

Stacktrace
Logs from reading table 1 (fast):
INFO AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v1
INFO AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO AbstractTableFileSystemView: Building file system view for partition (date=2021-12-30/source=test/type=test)
INFO AbstractTableFileSystemView: addFilesToView: NumFiles=28, NumFileGroups=27, FileGroupsCreationTime=1, StoreTimeTaken=0
INFO HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v1, caching 27 files under s3://bucket/table_v1/date=2021-12-30/source=test/type=test
INFO AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v1
INFO AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO AbstractTableFileSystemView: Building file system view for partition (date=2021-12-31/source=test/type=test)
INFO AbstractTableFileSystemView: addFilesToView: NumFiles=21, NumFileGroups=20, FileGroupsCreationTime=1, StoreTimeTaken=0
INFO HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v1, caching 20 files under s3://bucket/table_v1/date=2021-12-31/source=test/type=test

Logs from reading table 2 (slow):
INFO AbstractTableFileSystemView: Took 8508 ms to read  17 instants, 15201 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v2
INFO AbstractTableFileSystemView: Took 8468 ms to read  17 instants, 15201 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO AbstractTableFileSystemView: Building file system view for partition (date=2021-12-19/source=test/type=test)
INFO AbstractTableFileSystemView: addFilesToView: NumFiles=47, NumFileGroups=46, FileGroupsCreationTime=3, StoreTimeTaken=0
INFO HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v2, caching 46 files under s3://bucket/table_v2/date=2021-12-19/source=test/type=test
INFO AbstractTableFileSystemView: Took 8513 ms to read  17 instants, 15201 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v2
INFO AbstractTableFileSystemView: Took 9192 ms to read  17 instants, 15201 replaced file groups
INFO ClusteringUtils: Found 0 files in pending clustering operations
INFO AbstractTableFileSystemView: Building file system view for partition (date=2021-12-21/source=test/type=test)
INFO AbstractTableFileSystemView: addFilesToView: NumFiles=71, NumFileGroups=70, FileGroupsCreationTime=5, StoreTimeTaken=0
INFO HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v2, caching 70 files under s3://bucket/table_v2/date=2021-12-21/source=test/type=test

Couple of observations.

May I know why you are setting upsert parallelism to 15k. 15k is very high. Is that intentionally tuned. If not, would recommend to something like 200 to 300.
I see your 2nd table has lot of file groups which were replaced. And so it does add some latency while checking valid file groups. So, once the cleaner comes through and deletes all replaced file groups, I feel the latency hit should go away.

In general, do you know total file groups in table1 vs table2. If they are drastically different, then latency is expected to be different.
CC @xushiyan @codope @yihua

Thank you for looking into this.
I don't know how I could count file groups, so I listed all Parquet files in both tables. There's 535 741 files in table_v1 and 371 102 in table_v2. That number doesn't surprise me and if it was any performance indicator, then reading from the first table should be slower.
You're absolutely right, 15k is too much. I had issues with executors running out of memory (due to data skew) and tried increasing parallelism. Do you suspect that it could be causing this issue? It's not optimal, but doesn't create a lot of small files. Also, the same parallelism was used with both tables.
I'm sorry if I wasn't clear, but I had run cleaner on both tables before reading from them. I just tested it again and I can see that the last commit is *__clean__COMPLETED commit. What I did was:

I run cleaner on the second table

spark-submit \
    --driver-memory 8G \
    --deploy-mode cluster \
    --conf "spark.yarn.maxAppAttempts=1" \
    --conf "spark.dynamicAllocation.maxExecutors=20" \
    --class org.apache.hudi.utilities.HoodieCleaner \
    hudi-utilities-bundle_2.12-0.10.0.jar \
    --target-base-path s3://bucket/table_v2 \
    --hoodie-conf hoodie.cleaner.parallelism=10 \
    --spark-master yarn-cluster

There's was almost nothing to do, so it finished within 2 minutes.

I read one of the partitions in the second table

def time[T](func: => T): T = {
    val t0 = System.nanoTime
    val result = func
    val t1 = System.nanoTime
    println("Elapsed time: " + (t1-t0)/1000000000 + "s")
    result
}

time {
	spark.read.format("org.apache.hudi")
	.option("hoodie.metadata.enable", "false")
	.option("hoodie.datasource.read.paths", "s3://bucket/table_v2/date=2022-01-01/source=test/type=test")
	.load()
}

Logs:
DataSourceUtils: Getting table path..
TablePathUtils: Getting table path from path : s3://bucket/table_v2/date=2022-01-01/source=test/type=test
DefaultSource: Obtained hudi table path: s3://bucket/table_v2
HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://bucket/table_v2
HoodieTableConfig: Loading table properties from s3://bucket/table_v2/.hoodie/hoodie.properties
HoodieTableMetaClient: Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from s3://bucket/table_v2
DefaultSource: Is bootstrapped table => false, tableType is: COPY_ON_WRITE, queryType is: snapshot
DefaultSource: Loading Base File Only View  with options :Map(hoodie.datasource.query.type -> snapshot, hoodie.datasource.read.paths -> s3://bucket/table_v2/date=2022-01-01/source=test/type=test, hoodie.metadata.enable -> false)
HoodieActiveTimeline: Loaded instants upto : Option{val=[20220124110227018__clean__COMPLETED]}
HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://bucket/table_v2
HoodieTableConfig: Loading table properties from s3://bucket/table_v2/.hoodie/hoodie.properties
HoodieTableMetaClient: Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from s3://bucket/table_v2
HoodieTableMetaClient: Loading Active commit timeline for s3://bucket/table_v2
HoodieActiveTimeline: Loaded instants upto : Option{val=[20220124110227018__clean__COMPLETED]}
FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v2
AbstractTableFileSystemView: Took 9286 ms to read  17 instants, 15201 replaced file groups
ClusteringUtils: Found 0 files in pending clustering operations
AbstractTableFileSystemView: Building file system view for partition (date=2022-01-01/source=test/type=test)
AbstractTableFileSystemView: addFilesToView: NumFiles=40, NumFileGroups=39, FileGroupsCreationTime=3, StoreTimeTaken=0
HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v2, caching 39 files under s3://bucket/table_v2/date=2022-01-01/source=test/type=test
AbstractTableFileSystemView: Took 8423 ms to read  17 instants, 15201 replaced file groups
ClusteringUtils: Found 0 files in pending clustering operations
Elapsed time: 20s

For comparison I read the same partition in the first table

time {
	spark.read.format("org.apache.hudi")
	.option("hoodie.metadata.enable", "false")
	.option("hoodie.datasource.read.paths", "s3://bucket/table_v1/date=2022-01-01/source=test/type=test")
	.load()
}

Logs:
DataSourceUtils: Getting table path..
TablePathUtils: Getting table path from path : s3://bucket/table_v1/date=2022-01-01/source=test/type=test
DefaultSource: Obtained hudi table path: s3://bucket/table_v1
HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://bucket/table_v1
HoodieTableConfig: Loading table properties from s3://bucket/table_v1/.hoodie/hoodie.properties
HoodieTableMetaClient: Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from s3://bucket/table_v1
DefaultSource: Is bootstrapped table => false, tableType is: COPY_ON_WRITE, queryType is: snapshot
DefaultSource: Loading Base File Only View  with options :Map(hoodie.datasource.query.type -> snapshot, hoodie.datasource.read.paths -> s3://bucket/table_v1/date=2022-01-01/source=test/type=test, hoodie.metadata.enable -> false)
HoodieActiveTimeline: Loaded instants upto : Option{val=[20220124032411__clean__COMPLETED]}
HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://bucket/table_v1
HoodieTableConfig: Loading table properties from s3://bucket/table_v1/.hoodie/hoodie.properties
HoodieTableMetaClient: Finished Loading Table of type COPY_ON_WRITE(version=1, baseFileFormat=PARQUET) from s3://bucket/table_v1
HoodieTableMetaClient: Loading Active commit timeline for s3://bucket/table_v1
HoodieActiveTimeline: Loaded instants upto : Option{val=[20220124032411__clean__COMPLETED]}
FileSystemViewManager: Creating InMemory based view for basePath s3://bucket/table_v1
AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
ClusteringUtils: Found 0 files in pending clustering operations
AbstractTableFileSystemView: Building file system view for partition (date=2022-01-01/source=test/type=test)
AbstractTableFileSystemView: addFilesToView: NumFiles=20, NumFileGroups=18, FileGroupsCreationTime=2, StoreTimeTaken=0
HoodieROTablePathFilter: Based on hoodie metadata from base path: s3://bucket/table_v1, caching 18 files under s3://bucket/table_v1/date=2022-01-01/source=test/type=test
AbstractTableFileSystemView: Took 0 ms to read  0 instants, 0 replaced file groups
ClusteringUtils: Found 0 files in pending clustering operations
Elapsed time: 1s

I guess the replaced file groups(15201 file groups, where as actual valid file groups are only 17 or 18) are causing a lot of impact. We can probably trigger archival and see whats happening.
I am assuming you are using default configs for cleaning and archiving. especially below configs.
hoodie.cleaner.commits.retained
hoodie.keep.min.commits
hoodie.keep.max.commits

default values are 10, 20 and 30.
Can you make the 2nd and 3rd configs to 11 and 12.
This should trim your active timeline and likely replaced file groups as well.
And I assume you have metadata disabled (hoodie.metadata.enable) in both. bcoz, in your description, I see the config value is different in table1 to table2.
CC @manojpec for perf issues reported.

@parisni : lets keep the issue you are facing out of this one. we can discuss it in the one you raised.

@parisni No, I wasn't able to mitigate this. We worked around it by doing the following:

Disabling table metadata for all Hudi tables (hoodie.metadata.enable=false) noticeably speeds up read and write times. Also, performance doesn't seem to degrade over time as new partitions are added.
I redesigned our ETL so that we don't need a Hudi table with 300k partitions. Resulting table is smaller, differently partitioned, has reasonable amount of partitions and uses pure Parquet files (no Hudi)

I keep tracking new releases of Hudi. Eventually, I plan to enable Hoodie metadata back.

@ganczarek : have you tried giving latest version of hudi (0.12) which has few critical perf fixes.
also, we stabilized our metadata table in 0.11 and above. So, if you can give it a try and let us know how it goes, would be nice.

@nsivabalan I'm sorry, but I no longer have a setup to test it the same way as I did back in January. I will update to Hudi v0.12 and enable metadata table to see if there are performance improvements, but I won't test it with a table with 300k partitions.
I think we can close this ticket. If I see any performance issues with the latest version of Hudi, then I will create a new ticket.
Thank you for your help and assistance.


ARROW-12724: [C++][Docs] Add documentation for authoring compute kernels

The goal of this PR is to update the existing documentation for authoring compute kernels.
This PR will primarily reformat the documentation from markdown into reStructured text and updated descriptions. In some cases, I will try to reference a cookbook.
This is a new PR against apache/master, created as a rebase of the original PR (https://github.com/apache/arrow/pull/10296) on top of apache/master as of 2022/08/20.

Note that I plan on using a cookbook (https://github.com/apache/arrow-cookbook/pull/227) to address most snippets and examples in the future.

https://crossbow.voltrondata.com/pr_docs/13933/ once docs are built.

rebased for that sweet doc preview feature

@github-actions crossbow submit preview-docs

I am still restructuring docs so this will need some iterations before final review, but it'll be cool to get initial feedback if the preview works

Indeed. You'll need to re-run for each preview.

cpp/developers/author_compute_fn.html

This page is still a work in progress, but it's where I am thinking of putting some higher level overview of "the compute layer" (what are compute functions, what are function kinds, etc.) so that the author_compute_fn.html doc can be a bit leaner and more to the point.
cpp/concepts/compute.html

Sorry for orphan-ing this for so long. I would like to get back to this towards the end of the week.


Look into using the snapshot plugin of OAV

Currently we get a snapshot from the ffmpeg stream. There is  already a plugin for taking snapshots on the oav which we could possibly use instead.

Needs discussion with @thomascobb and Neil

I don't think this is completed, we're still getting the snapshot from the stream so a discussion of the pros/cons of switching to the plugin is warranted

oh, we should clarify wording then seeing as mjpg is also a plugin.


Add Comments and Fix linting

Looking for help with adding comments and formatting our codebase.

PR #15 is approved.

PR #14 is going to need a few adjustments before approval.

PR #14 is going to need a few adjustments before approval.

will sure do so


Add meta tags

In order to improve the SEO params of the website , we have to add meta tags on every page.
E.g.  vue-head

Implemented by #98


fix(clerk-react): IsomorphicClerk#addListener should return unsubscribe method

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[x] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Issue: https://github.com/clerkinc/javascript/issues/1451

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


IronicSpecCore support for validation functions

A follow up to allow the new IronicSpecCore to work with the webhook ValidateCreate and ValidationUpdate functions.
Jira: OSPRH-4835

looks good to me, but lets see what CI comes back with.

/lgtm
podified-multinode-ironic-deployment is failing but the manager is running OK[1], so lets land this.
[1] https://logserver.rdoproject.org/08/408/ac1fa19ef3bfc82d79ce7887fff1db50021c5e7d/github-check/podified-multinode-ironic-deployment/72fa63d/controller/ci-framework-data/logs/openstack-k8s-operators-openstack-must-gather/namespaces/openstack-operators/pods/ironic-operator-controller-manager-7bffbd8cf-fbnnb/logs/manager.log


Clean up form validation tests

There are a number of places where $_POST is modified and not
reset back to its previous state. This could lead to side effects
impacting other tests. There are also a number unnecessary calls to
reset_validation(). A new form_validation object is already
initialized for every test in set_up(), so these lines do nothing
unless they are cleaning up from earlier in the same test.
To remedy this, we make the following changes:
Set $_POST = array() in set_up(), resetting to a default state for
every test run. Add a tear_down() method that does the same and is
called by PHPUnit's tearDown() after each test.
Remove now-redundant lines where tests set $_POST = array() at the
beginning or end of the test.
Remove unnecessary calls to reset_validation() intended as setup
or teardown.

This works, but ... it's the brute-force way.
$_POST should be reset by the tests that modify it, not via setup and teardown.

I looked into the PHPUnit documentation. From the current stable version documentation (https://phpunit.de/manual/6.4/en/fixtures.html#fixtures.global-state):

Prior to version 6, by default, PHPUnit ran your tests in a way where changes to global and super-global variables ($GLOBALS, $_ENV, $_POST, $_GET, $_COOKIE, $_SERVER, $_FILES, $_REQUEST) do not affect other tests.
As of version 6, PHPUnit does not perform this backup and restore operation for global and super-global variables by default anymore. It can be activated by using the --globals-backup option or setting backupGlobals="true" in the XML configuration file.

We are currently on 5.7, so $_POST and all of those other globals are reset by default. Thus we could remove all the cleanup of resetting $_POST altogether. In the event that we switch to PHPUnit 6+, it's probably a good idea to add backupGlobals="true" to the config. However, considering that PHPUnit 6 requires PHP 7, that may never happen and people will instead migrate to CodeIgniter 4.
With that in mind, what do you think about:

Removing all resetting of $_POST as cleanup, since it is automatically done for us.
Adding backupGlobals="true" to phpunit.xml, just to be explicit.

I don't care about backupGlobals, but I do insist that $_POST is reset by any test case that modifies it, regardless of how PHPUnit works.

As requested, $_POST is now explicitly reset at the end of each test that modifies it.


removed question numbers and uppercase all input

@smn @miltontony @bruskiza quick review please. just html changes

:+1:


NOISSUE - Fraud detection project

Code looks decent, but this completely misses README. Users will have no idea what is this about, how to run it, where to get datasets, and so on... Complete mystery.


Add the ability to query what variables are currently loaded.

I'm working on a thing that would like to know all the env variables currently loaded with the prefix THING_. I'm imagining an api like:
glenvy.loaded()
|> list.filter(string.starts_with(_, "THING_")
//=> ["THING_WIBBLE", "THING_WOBBLE"]

Does this seem like something glenvy would what to provide?

In v1.0.0 you can use glenvy/env/get_all to retrieve all of the environment variables.
In your example it would look like this:
import gleam/dict
import gleam/list
import glenvy/env

env.get_all()
|> dict.keys()
|> list.filter(string.starts_with(_, "THING_"))
// => ["THING_WIBBLE", "THING_WOBBLE"]

Does that suit your needs?


[Feature Request]-Add some more components/factors to the report

Add a few other factors also to the report like the below status and add some color tags to make the report user friendly
if possible have the report in HTML format to share with others

Critical
Minor
Major

Hey @sseenivasan89 ,
Pynt is out with a new report version. Check out the new docker and new collection. You would be pleased to find the report got a complete redesign and in an html format which you can save and share with folks.
Waiting to hear from you :)


Add Shubham-Pampattiwar to Contributors list

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Is there a way to show only dates and times in the future?

Ask your Question
In our app, we have a use case in which the user picks the date and time, but only future dates and times are applicable. Is there a way to restrict the modal such that the user can pick only future dates and times?

Hi,
https://github.com/mmazzarolo/react-native-modal-datetime-picker#how-can-i-set-a-minimum-andor-maximum-date


Type of  Comment DropDown shows incorrect name on change.

In the comment section the user have option to select and change the type of comment.

On change to Intro Comments the drop down value is marked with the code rather than description shown below.

This should not happen and On change the value should remain as that of the description shown in the drop down initially.

@hkirat I already have started to look for the changes and I don't think it requires much effort. Can I fix this?


First !Account definition missed due to !Option:AutoSwitch

In your most recent release, you included a change (#90) to ignore !Clear:AutoSwitch lines. I'm getting similar lines in Quicken exports: !Option:AutoSwitch. I'm not very familiar with these file formats, and as the PR states, these sections aren't defined in the standard. So, I'm not sure if this !Option section is the cause of the issue I'm having, or if it's a bug.
Here's a snippet from the top of a sample file I'm working with that demonstrates the issue.
!Option:AutoSwitch
!Account
NChecking
TBank
^
NSavings
TBank
^
!Clear:AutoSwitch
!Option:AutoSwitch
!Account
NChecking
TBank
^
!Type:Bank
D8/ 2'24
U5.00
T5.00
CX
POpening Balance
L[Checking]
.
.
.

When reading this file, it ignores everything up until the first !Type:Bank, at which point there is no account so it creates the "Quiffen Default Account". It seems like everything between !Option:AutoSwitch should be ignored. But because sections are split on ^, it's also skipping over the !Account for "Checking", effectively ignoring the definition of the account.
Any thoughts? I'd be happy to contribute a PR addressing this, but I'm not sure if I'm on the right track. I'll tinker with it a bit and see if I can come up with something that works for me, but I wanted to also get input from here in case I'm missing something obvious.
FYI: I'm on the latest release of Quiffen: 2.0.11, and I'm exporting a very simple set of accounts from Quicken Classic R59.18.

I did some tinkering and came across a fairly simple solution. It was simple enough that I thought it'd be easier to just submit a PR  (#93) than describe it here. But I'm open to discussion if there's something I've missed.


-buildmode=c-archive or -buildmode=c-shared not support 32 bit?

i use "GOARCH=386 go build -buildmode=c-archive",it shows ": no buildable Go source files in"
if use "GOARCH=386 go build -buildmode=c-shared", it shows "-buildmode=c-shared not supported on linux/386"

The error message seems to answer the question?

the error message  shows "-buildmode=c-shared" not supported on linux/386, but "-buildmode=c-archive"
also not support on linux/386?

Over to @ianlancetaylor to clarify and/or fix the error message.

You need to tell us more.  What files are in the directory in which you run the command?  Are there any buildable Go source files there?

yes,there is Go sources file ,if i just use "go build -buildmode=c-archive" without "GOARCH=386",it can build  an archive file that can be linked into a C program

I can not recreate the problem.  Can you show a small example with the exact .go files you are using?
I do see a completely different problems.  When setting GOARCH with -buildmode=c-archive, you may need to add a go build argument
-ldflags=-linkmode=external

[root@ubuntu:mytest]# tree
.
├── mytest.go
└── p
└── p.go
this is mytest.go
package main // import "mytest"
import _ "mytest/p"
func main() {} // ignored
this is  p.go
package p //import "mytest/p"
import "C"
//export Foo
func Foo() int32 { return 42 }
use "GOARCH=386 go build -ldflags=-linkmode=external -buildmode=c-archive" failed

Ah.  By default, cross-compilers do not enable cgo, so the go tool is ignoring p/p.go since it needs cgo.


Highlight current lines with multiple cursors

VSCode Version: 1.22.1
OS Version: windows10 x64

Make all line's numbers colored
instead of coloring just the first one
like Atom when multi select

We now render multiple line highlights, but only in the case where they are rendered with a background color (not with a border), i.e.

vs

How to enable it ?

@mostafaabobakr7 You can build VS Code from source or wait for tomorrow's Insiders build


Config Client Can Not Refresh Automatically

Question
Here is my sample application.
Step to reproduce my issue:

Start the discovery-service with default profile, the config-service with default profile, and the client-service with zone1 profile.
Change value of sample.string.prop property in client-service-zone1.yml file of config-repo repository, stage changed, commit, push.

You can see from the console logs that config-service is refreshing its context , while client-service remains unchanged.

Can anyone give me a hand, please?

I have the same problem, Have you solved your problem? @PeichengLiu

@leogoing According to the document,

you can trigger a change notification by POSTing to /monitor with form-encoded body parameters in the pattern of path={name}. Doing so broadcasts to applications matching the {name} pattern (which can contain wildcards).

I have verified this using Postman.

However, I don't know how to send the custom payload with GitLab Webhooks. And I can't find the solution neither from the document nor Google.
What's more, with this approach, we have to specify the APP name. This limitation may be unacceptable under certain circumstances. While we can surely write some additional script to verify the delta and then specify the APP name accordingly.

@leogoing According to the document,

you can trigger a change notification by POSTing to /monitor with form-encoded body parameters in the pattern of path={name}. Doing so broadcasts to applications matching the {name} pattern (which can contain wildcards).

I have verified this using Postman.

However, I don't know how to send the custom payload with GitLab Webhooks. And I can't find the solution from neither the document nor Google.
What's more, with this approach, we have to specify the APP name. This limitation may be unacceptable under certain circumstances. While we can surely write some additional script to verify the delta and then specify the APP name accordingly.

I'm afraid that's a limitation of gitlab, there's not anything we can do.


⚠ Bofrost.at has degraded performance

In 69b7014, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1602 ms

Resolved: Bofrost.at performance has improved in f2504e8 after 6 minutes.


Specify the anisotropy flow map

This PR replaces the definitions specular_rotation and coat_rotation specifying the anisotropy with an angle relative to the reference coordinates, with specular_direction and coat_direction that instead specify that direction with a normalized 2D vector.
This parametrization doesn't suffer from discontinuity at 0°, is more robust to interpolation, and more aligned with the parametrization typically used in normal mapping.

I've added several changes, as proposed in #155:
Naming (d7d7040):

Specification of the direction as a property of the NDF (e321ff9):

I feel strongly that we should keep the existing specular_rotation and coat_rotation parameters, applied as an additional angular offset on top of the flow-map generated T, B. This should normally only be used to globally rotate the highlights (but in some cases could be textured, with the caveat about the interpolation artifacts due to the discontinuity which we should warn about in the spec). This ability to globally rotate seems useful to retain.
Also, there will be existing assets that texture the rotation. A case where it could genuinely make sense to texture the rotation would to add some perturbing angular noise to procedurally break up the flow-map generated directions (which will not introduce any artifact provided the noise is smooth).

Regarding the discussion in the meeting about what assumptions we should make about the tangent space, i.e. assume the policy is roughly:

a reference tangent space (N, T, B) is assumed to be known. We do provide the parameters geometry_normal and geometry_tangent which are supposed to specify this, though I think in practice the renderer itself will normally ensure the shader knows the local tangent frame, adjusted according to the shading normals and tangents supplied with the geometry, modulated by any normal and displacement maps.
the final tangent frame is defined relative to this reference space. I think we should probably write this formula down in the spec, to avoid any confusion about how this is defined

Yes, good point. We already state the assumption of the existing frame of reference, but the exact transform is certainly lacking.

The direction is specified as a normalized 2D vector, with $(1, 0)$ being the original tangent vector direction.

I think we need to be more explicit that the values in the texture, $(R, G)$ (where $R, G \in [0,1]$ after dequantization), are mapped to $(t, b)$ via:
$$
t = 2R-1
$$
$$
b = 2G - 1
$$
where we require that $t^2 + b^2 =1$. Then the final tangent vector is given (in terms of the reference tangent frame) by:
$$
\mathbf{T}' = t \mathbf{T} + b \mathbf{B}
$$

There were several points brought, so I'll try to address them one by one:

On the additional rotation parameter: I am not convinced this value is worth the cost. This reintroduces the implementation complexity that the flowmap was meant to avoid. It also adds a parameter, which is something we should try to limit, for a control that's essentially redundant with the anisotropy direction. I hear the use case, but that sounds like a proposal to work around a potential limitation of the authoring tool. I would instead suggest to leave this proposed parameter out at least until we have a clear demand for it.

On the specification of the tangent space: agreed, will amend the PR to specify the relation between $T$ and $T'$.

On the direction of the grooves vs direction of the highlight: your comment makes me realise I confused what the effect of stretching the NDF would be. I will have to amend the PR to fix that. As for $T$ vs $B$, I agree it makes more sense for the artist to draw the direction of the groves, but as you point out, the vector field will express both equivalently. So in the end I think we can conclude it's irrelevant, which means the decision to how best express it will be left to the authoring tool. On the specification side, we then should probably choose the simplest and clearest specification. I think "NDF stretching along T" would be it (even though it means the opposite of what I originally thought it meant 🙃).

On the mapping from $[0, 1]$ to $[-1, 1]$: I was asking because I was not sure there was a consensus, but I'll update the PR to reflect this.

Did I forget anything?

On the additional rotation parameter: I am not convinced this value is worth the cost. This reintroduces the implementation complexity that the flowmap was meant to avoid. It also adds a parameter, which is something we should try to limit, for a control that's essentially redundant with the anisotropy direction. I hear the use case, but that sounds like a proposal to work around a potential limitation of the authoring tool. I would instead suggest to leave this proposed parameter out at least until we have a clear demand for it.

Sounds reasonable. At least, putting the rotation angle parameter back if users demand it would be strictly additive to the model so would not be a very disruptive change. The main thing I worry is that users may want to globally rotate the direction by 90 degrees, in case the flow direction was painted as "groove stretch" instead of "highlight stretch". Though of course it can always be done at the level of the flow map.

On the specification of the tangent space: agreed, will amend the PR to specify the relation between
👍

I agree it makes more sense for the artist to draw the direction of the groves, but as you point out, the vector field will express both equivalently. So in the end I think we can conclude it's irrelevant, which means the decision to how best express it will be left to the authoring tool. On the specification side, we then should probably choose the simplest and clearest specification. I think "NDF stretching along T" would be it (even though it means the opposite of what I originally thought it meant 🙃).

Possibly i'm mistaken, but won't artists usually think of the lines they are painting as corresponding to the "brush" direction in brushed metal? So e.g. to get the thing below, wouldn't they want to paint circles around the base of the pan, rather than radial lines? (As if they are applying the brushing themselves to the metal). In that case, they would be specifying what we refer to a B.
Personally I'd  vote to swap the meaning of T and B, so that T actually means the groove direction (so B is the NDF highlight stretch direction). This is not what glTF did though, for whatever reason. Ideally we need to hear from more people who are familiar with the actual artist tools and workflows for this (maybe your Substance colleagues for example).

Possibly i'm mistaken, but won't artists usually think of the lines they are painting as corresponding to the "brush" direction in brushed metal?

Oh yes, I completely agree. But whether we specify the grooves as being T or B won't matter, since it's up to the authoring tool to decide what a brush stroke of the artist will result in. Arguably, an authoring tool that doesn't give much thought into it will likely map our parameter as is, so that would be an argument to indeed align the grooves with T.
I'll try to gather some feedback internally.

NB, the Arnold tutorial for that pan render is here:
https://help.autodesk.com/view/ARNOL/ENU/?guid=arnold_for_3ds_max_ax_shading_ax_anisotropic_brushed_html
It's interesting that in this case, he didn't rely much (or at all?) on the tangents, instead the circles were generated using a bump map with circular "scratches" in it (which is kind of like authoring the "anisotropic microfacet distribution" with bumps, rather than the actual NDF).  Which is another valid way to get "anisotropic roughness" at a geometrical level, I suppose.

On the additional rotation parameter: I am not convinced this value is worth the cost...  suggest to leave this proposed parameter out at least until we have a clear demand for it.

Agreed.
? On the specification of the tangent space: agreed, will amend the PR to specify the relation between $T$ and $T'$
👍

On the direction of the grooves vs direction of the highlight: your comment makes me realise I confused what the effect of stretching the NDF would be. I will have to amend the PR to fix that.

👍

On the specification side, we then should probably choose the simplest and clearest specification. I think "NDF stretching along T" would be it (even though it means the opposite of what I originally thought it meant 🙃).

Arguably, an authoring tool that doesn't give much thought into it will likely map our parameter as is, so that would be an argument to indeed align the grooves with T.

I think glTF opted to have the NDF stretch along T.
Personally, I think it's more intuitive though if the grooves aligned with T, so the highlight (and thus the NDF stretch) should align with B.
Though I suppose we should go with whatever convention is most consistent with existing flow-map tools (your Substance colleagues would be the best people to ask).

On the mapping from
[0,1] to [-1,1]
(https://github.com/AcademySoftwareFoundation/OpenPBR/issues/155#issuecomment-2009614171) ... I was not sure there was a consensus, but I'll update the PR to reflect this.

Seems like there is a consensus (i.e. do same as in glTF).

Did I forget anything?

Nope. Only issue to decide is the stretch direction convention. Otherwise, proposed fixes to the spec sound good.

I went with what I think is the simplest proposal.
Here are the relevant parts:


SAP Router for SAP Note Download - no longer applies

Hello,
Please check SAP note 3010412 - "SAP Support Backbone - Configuration Overview, Responsibilities and Troubleshooting".
SAP note download into SAP Netweaver ABAP has not required the SAP Router since January 2020.
Thanks
Darryl

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fdf95a78-b354-11c7-de36-2bc0787c930c
Version Independent ID: fdf95a78-b354-11c7-de36-2bc0787c930c
Content: Inbound and outbound internet connections for SAP on Azure - Azure Architecture Center
Content Source: docs/guide/sap/sap-internet-inbound-outbound.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @msftrobiro
Microsoft Alias: robiro

Thank you for raising this Darryl. Absolutely agree and it was an oversight to keep that superfluous sentence about note download. Appreciate your raising this and PR on the way to correct this very soon. Will update once PR is live.

PR was merged.
I will close the ticket, but feel free to re-open if additional clarification is needed.

#please-close


Disable allDay events

How can I disable allDay events so that I will not see the first cells on the ui?
I did not found it on the docs nor in other issues.
Thanks

For now, the only available option is to use css for that
.rbc-allday-cell {
   display: none;
}

And as far as I remember there were discussions to create an option for this which IMO would be useful. I've personally had to in 2 different projects hide it using css what isn't the most elegant way

For now, the only available option is to use css for that
.rbc-allday-cell {
   display: none;
}

And as far as I remember there were discussions to create an option for this which IMO would be useful. I've personally had to in 2 different projects hide it using css what isn't the most elegant way

Thanks @michalak111


Tileset: Clicking anything when there is shader attached to tile prompt shader editor

Godot version
4.0 beta 16
System information
Windows 11
Issue description
There are shaders on alternative tiles. Clicking anything or trying to paint stuff on tile (in this example modulate) ends with the opening shader editor.
PS: Reloading project helps.

Steps to reproduce
Add shader to tile and try using paint tool on that tile.
Minimal reproduction project

CC @KoBeWi @groud

Somewhat similar to #70705
Clicking the tile brings up the inspector for that tile and switches to shader editor. It will stop doing that once you fold the property.
Maybe a solution to both these issues could be automatically folding the resources when inspector is updated? This would mean that you'd have to manually unfold the resource every time you want to edit it; it would no longer happen on node switch etc. idk what else can be done 🤔


Permission issues

HTTP Error 400: {"errorMessages":[],"errors":{"assignee":"The default assignee does NOT have ASSIGNABLE permission OR Unassigned issues are turned off."}}

More context is needed please. Can you please share the log? How was the script invoked?


400 Bad Request when passing the --duration flag

I consistently get a 400 Bad Request from the application when I pass the --duration flag, no matter the value or units (tried "h" and "m").
Without the --duration flag it works fine.

👋🏻 Hello @PauloGDPeixoto
Thank you for trying aws-console! Could you please add some details regarding:

The output of aws-console --version.
The full command you are running and resulting output.
Which exact type of IAM principal (user/role/etc) you are attempting to generate a console login url for.

Thank you so much, cheers!

Hi, thanks for replying!
Here you go:
homepage: https://github.com/joshdk/aws-auth
author:   Josh Komoroske
license:  MIT

The full command (and error message):
aws-console: request failed: 400 Bad Request

I'm logging in as a federated user with a role, I don't know if this makes sense to you, I can try to elaborate further, if needed.


Generate classes by feature creates duplicates

When I using the command 'mvn generate-test-sources' everything is working fine, but when I use the command 'mvn test' the generate classes creates duplicates.

What configuration are you using in your POM?
Can you provide a sample project?

com.github.temyers
cucumber-jvm-parallel-plugin
2.0.2

generateRunners
generate-test-sources

generateRunners

com.automationrhapsody.cucumber.parallel.tests.wikipedia
src/test/resources/com
${basedir}/target/cucumber
html
FEATURE

I'm sorry, I found the FEATURE was deprecated.

FEATURE is deprecated, in favour of the new SCENARIO scheme.
FEATURE shall be removed as an option in a future release, but for now it should generate as expected.
Please could you try with the SCENARIO scheme?

I updated the plugin to version 2.1.0 an changed the parallelScheme to SCENARIO, when I using the command 'mvn clean generate-test-sources' everything is working fine, bug when I using command 'mvn clean test' the generate classes creates duplicates too

cucumber.zip

cucumber-parallel.zip
Could you help me to check my project? When I added the maven-surefire-report-plugin into my project the cucumber-jvm-parallel-plugin will be calling twice and else anything is working fine.

See http://maven.apache.org/surefire/maven-surefire-report-plugin/usage.html
The reporting plugin should be added to the  section - not plugin dependencies.

Thanks Temyers.

Hi @temyers
When I using the driver-binary-downloader-maven-plugin plugin the generate classes creates duplicates again.
<plugin>
				<groupId>com.lazerycode.selenium</groupId>
				<artifactId>driver-binary-downloader-maven-plugin</artifactId>
				<version>1.0.11</version>
				<configuration>
					<rootStandaloneServerDirectory>${project.basedir}/src/test/resources/selenium_standalone_binaries</rootStandaloneServerDirectory>
					<downloadedZipFileDirectory>${project.basedir}/src/test/resources/selenium_standalone_zips</downloadedZipFileDirectory>
					<customRepositoryMap>${project.basedir}/src/test/resources/RepositoryMap.xml</customRepositoryMap>
					<overwriteFilesThatExist>${overwrite.binaries}</overwriteFilesThatExist>
				</configuration>
				<executions>
					<execution>
						<goals>
							<goal>selenium</goal>
						</goals>
					</execution>
				</executions>
			</plugin>

Thanks

What section is the plugin defined in?
Is sounds like the generate-test-sources phase is being called twice.
Can you post debug output:mvn clean package -X


Changing CMP0078 to OLD if cmake version is greater than 3.13

Proposed by Gérard Vidal<EMAIL_ADDRESS>ENS de Lyon IFÉ
Add test in CMakefiles.txt on cmake version
If version > 3.13 set value OLD to CMP0078
This is proposed because the compilation of mraa yields an mraa module that cannot be imported in python3
Signed-off-by: Gérard Vidal<EMAIL_ADDRESS>

Thanks for the contribution, could you please sign-off your commit as described in:
https://github.com/intel-iot-devkit/mraa/blob/master/CONTRIBUTING.md#code-signing

Probably copy / paste mistake  reproduced when testing.
Adding this code just enables to remove the warnings during cmake execution.
Is the signoff OK now?

Still not seeing the sign-off on the commit :/


fix: Fix typo in comment for infinitely

This PR fixes a small typo in the Haddock comment for infinitely.
Checklist:

HLint

[ ] I've changed the exposed interface (add new reexports, remove reexports, rename reexported things, etc.).

[ ] I've updated hlint.dhall accordingly to my changes (add new rules for the new imports, remove old ones, when they are outdated, etc.).
[ ] I've generated the new .hlint.yaml file (see this instructions).

General

[ ] I've updated the CHANGELOG with the short description of my latest changes.
[x] All new and existing tests pass.
[x] I keep the code style used in the files I've changed (see style-guide for more details).
[x] I've used the stylish-haskell file.
[x] My change requires the documentation updates.

[x] I've updated the documentation accordingly.

[ ] I've added the [ci skip] text to the docs-only related commit's name.

What's the best way to add unreleased change descriptions to the CHANGELOG? I haven't done that because I didn't want to break the CHANGELOG format.


Fix issues with windows paths

See https://github.com/babel/babel/issues/9032
I'm not sure if the ignore path is necessary. But I know it will cause issues in its current form. I'm not able to start any react-static example without this change.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

My guess is the error is being caused by something else, but I'd like to know more about this error as well.

I did some more research and found that this is a problem with unix vs windows path (using windows currently). The original ignore took only unix into consideration.
Here is the original ignore option of babel:
https://github.com/babel/babel/blob/47da5cf75a4f67d199422e7f2a2635a71317d478/packages/babel-register/src/node.js#L145
The windows path style causes problems in other places too. I'm still getting Error: Could not find a route for the "index" page of your site! This is required. Please create a page or specify a route and template for this page. when running the examples which I've been talking about here: https://github.com/nozzle/react-static/issues/721

A bit off-topic, I also notices that getRoutesFromPages in installed react-static lib folder contains
(function () {
  var reactHotLoader = require('react-hot-loader').default;

  var leaveModule = require('react-hot-loader').leaveModule;

  if (!reactHotLoader) {
    return;
  }

  reactHotLoader.register(watcher, "watcher", "/Users/tannerlinsley/GitHub/react-static/packages/react-static/src/static/getRoutes/getRoutesFromPages.js");
  reactHotLoader.register(routesCache, "routesCache", "/Users/tannerlinsley/GitHub/react-static/packages/react-static/src/static/getRoutes/getRoutesFromPages.js");
  leaveModule(module);
})();

Okay, I can run example projects on windows with the changes applied here. I don't know if there is still problems due to windows path vs unix path, it is difficult to find them as long as they don't cause exceptions.
You should definitely use nodejs path.resolve / path.sep etc more, hard-coding '/' in str.replace or str.split is super error prone.

Lodash is already part of many dependencies of react-static.
info Reasons this module exists
   - "@babel#types" depends on it
   - Hoisted from "@babel#types#lodash"
   - Hoisted from "@babel#traverse#lodash"
   - Hoisted from "@babel#generator#lodash"
   - Hoisted from "react-static#webpack-bundle-analyzer#lodash"
   - Hoisted from "react-static#inquirer#lodash"
   - Hoisted from "react-static#@babel#cli#lodash"
   - Hoisted from "react-static#@babel#core#lodash"
   - Hoisted from "react-static#@babel#register#lodash"
   - Hoisted from "react-static#css-loader#lodash"
   - Hoisted from "react-static#html-webpack-plugin#lodash"
   - Hoisted from "eslint-config-react-tools#eslint#lodash"
   - Hoisted from "eslint-config-react-tools#eslint-plugin-import#lodash"
   - Hoisted from "react-static#extract-css-chunks-webpack-plugin#lodash"
   - Hoisted from "react-static#react-dev-utils#inquirer#lodash"
   - Hoisted from "react-static#thread-loader#async#lodash"
   - Hoisted from "react-static#@babel#preset-env#@babel#plugin-transform-block-scoping#lodash"
   - Hoisted from "eslint-config-react-tools#eslint#table#lodash"
   - Hoisted from "react-static#webpack-dev-server#http-proxy-middleware#lodash"
   - Hoisted from "react-static#optimize-css-assets-webpack-plugin#last-call-webpack-plugin#lodash"
   - Hoisted from "eslint-config-react-tools#babel-eslint#@babel#types#lodash"
   - Hoisted from "eslint-config-react-tools#babel-eslint#@babel#traverse#lodash"
   - Hoisted from "eslint-config-react-tools#eslint#inquirer#lodash"
   - Hoisted from "react-static#@babel#preset-env#@babel#plugin-transform-classes#@babel#helper-define-map#lodash"
   - Hoisted from "react-static#@babel#preset-env#@babel#plugin-transform-modules-umd#@babel#helper-module-transforms#lodash"
   - Hoisted from "react-static#@babel#preset-env#@babel#plugin-proposal-unicode-property-regex#@babel#helper-regex#lodash"
   - Hoisted from "eslint-config-react-tools#babel-eslint#@babel#traverse#@babel#generator#lodash"
   - Hoisted from "eslint-config-react-tools#babel-eslint#@babel#traverse#@babel#helper-function-name#@babel#template#lodash"

Done!

Thanks for the hard work and helping us understand!


Add instructions for contributing using a Windows based machine

It would be useful to list instructions on getting hug setup for development / contributing from a Windows based machine. Since I do not own any computers running Windows personally, this is an area where I could really use another contributor's help to ensure the instructions are correct.

I'll try taking a stab at this.  I'll need to create a windows batch file equivalent to .env; I'll name it .env.cmd, unless you want it named something else.
I don't foresee any major changes to the instructions; mainly just running .env.cmd instead.

Files beginning with a . can be a pain on Windows, is there any reason not to call it env.cmd?

No strong reason.  I just figured I'd keep it as a hidden file on POSIX systems and keep the differences minimal.

Fair enough

+1 Any work that is done on this would be super appreciated / helpful :)
~Timothy

I would be interested in working on this! Might need some help though!

I tried running the tests and a simple example (given in issue #500) using 'pipenv' in Windows and can confirm that it works properly. Just a note that it asks firewall permission for the first time. Would you guys be interested in having that added to the contribution file?

Yes! I would love to have that added!
Thanks!
~Timothy


Add hnswlib implementation

Codecov Report

Merging #13 (89b6a9c) into main (3f6288e) will increase coverage by 0.90%.
The diff coverage is 54.42%.

@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
+ Coverage   63.15%   64.06%   +0.90%
==========================================
  Files           4        6       +2
  Lines          57      192     +135
  Branches        4       23      +19
==========================================
+ Hits           36      123      +87
- Misses         21       69      +48

Impacted Files
Coverage Δ

...ain/scala/io/github/saucam/shiva/common/Node.scala
100.00% <ø> (+100.00%)
:arrow_up:

...io/github/saucam/shiva/hnsw/HnswIndexBuilder.scala
81.25% <25.00%> (ø)

...scala/io/github/saucam/shiva/common/ItemImpl.scala
33.33% <33.33%> (ø)

.../scala/io/github/saucam/shiva/hnsw/HnswIndex.scala
60.00% <54.74%> (+14.83%)
:arrow_up:

.../src/main/scala/io/github/saucam/shiva/Index.scala
100.00% <100.00%> (ø)

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


version 1.14.7 uses glob v8, that needs node version >=12

I need to use node v10. js-beautify version 1.14.0 supports node v10, but version 1.14.7 doesn't support.
A patch increment must not break retro compatibility.
Error message:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">=12". Got "10.24.1"
error Found incompatible module.

yarn.lock before:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  version "1.14.0"
  resolved "https://registry.yarnpkg.com/js-beautify/-/js-beautify-1.14.0.tgz#2ce790c555d53ce1e3d7363227acf5dc69024c2d"
  integrity sha512-yuck9KirNSCAwyNJbqW+BxJqJ0NLJ4PwBUzQQACl5O3qHMBXVkXb/rD0ilh/Lat/tn88zSZ+CAHOlk0DsY7GuQ==
  dependencies:
    config-chain "^1.1.12"
    editorconfig "^0.15.3"
    glob "^7.1.3"
    nopt "^5.0.0"

yarn.lock after:
<EMAIL_ADDRESS><EMAIL_ADDRESS>  version "1.14.7"
  resolved "https://registry.yarnpkg.com/js-beautify/-/js-beautify-1.14.7.tgz#9206296de33f86dc106d3e50a35b7cf8729703b2"
  integrity sha512-5SOX1KXPFKx+5f6ZrPsIPEY7NwKeQz47n3jm2i+XeHx9MoRsfQenlOP13FQhWvg8JRS0+XLO6XYUQ2GX+q+T9A==
  dependencies:
    config-chain "^1.1.13"
    editorconfig "^0.15.3"
    glob "^8.0.3"
    nopt "^6.0.0"

Solution: change yarn.lock js-beautify to old version (1.14.0)


Custom error messages for Azure

Can you add option overrides for the error messages in Azure, for example when the signature returns 403.
Static text is in v5.0.4 at line 6504 and 6513
        getSasFailure = function(reason, getSasXhr) {
            log("GET SAS request failed: " + reason, "error");
            promise.failure({error: "Problem communicating with local server"}, getSasXhr);
        },
        determineBlobUrlSuccess = function(blobUrl) {
            api.getSasForPutBlobOrBlock.request(getSasId, blobUrl).then(
                getSasSuccess,
                getSasFailure
            );
        },
        determineBlobUrlFailure = function(reason) {
            log(qq.format("Failed to determine blob name for ID {} - {}", id, reason), "error");

Pls guys, I am trying to upload a CSV file and this is what I am getting.
Dataset upload failed. Internal Service Error. Request ID: b043ceae-5516-48f4-be11-3be51acb7543 2015-01-28 15:48:07Z
Pls, any help?
Do not know whether its because I'm using a trial version, or is it an error? I need a help.
Thank you.

:+1: was also looking for this feature.
Another example:
function handleFailure(xhr, promise) {
        var azureError = qq.azure.util.parseAzureError(xhr.responseText, log),
            errorMsg = "Problem sending file to Azure";

        promise.failure({error: errorMsg,
            azureError: azureError && azureError.message,
            reset: xhr.status === 403
        });
    }

Semi-related question: is this supposed to trigger the callback onError? We're attached a logger and it's not logging anything. :) If not, how do I hook in to this?

It should triggger onError. But you should also (and more properly) be able to access the status of the request in an onComplete callback. If you are seeing a specific issue, please open up a new case.

Is there any plan to complete this item?

There is no specific timeline to complete these. Reasons for this:

Azure is much less popular than S3 or traditional endpoint support. The S3 and traditional/custom endpoint modules of the code are given priority attention
I am the only developer allocated to Fine Uploader, and my time to work on this project is unfortunately quite limited as well.

No problem, I just wanted to know. :) We've been using FineUploader for about a year now for transfers of 250-1000 MB datasets, and it's working out great; we're very content. Not being able to customize an error message is only a minor annoyance. We might open a PR for it ourselves at some point.

Thanks for that. I'm working on a plan to get more eyes on Fine Uploader and Modern Uploader.


How can I trace a request

Hello, OpenWhisk is new to me. I currently build an OpenWhisk on my server with the local configuration. I wanna trace the request and get to know the information about execution, like which container it use, the total execution time and cold start status. Is it possible? Is there any tools or UI that can help me out? Thank you!!

There is an OpenWhisk plugin in Pinpoint and I am using Pinpoint with OpenWhisk(downstream).
https://github.com/pinpoint-apm/pinpoint/tree/master/plugins/openwhisk
Since Pinpoint works based on the bytecode instrumentation, it does not require any code change in the OW layer.
But, on the other hand, it is a bit sensitive to code changes.
So I am not quite sure the above plugin works with the latest OpenWhisk code base.

The request information from wsk activation get {activationId} includes information on the:

duration : execution time
initTime: time to initialize the container (only present if invocation was a cold start)
waitTime: time from controller receiving the action and invoker provisioning a container
Source

Hope this helps!


Port to python3

Changes : -

Added pipenv to management the dependencies with ease and for maintenance
Ported python2 code to python3
Updated the readme

Looks great 😍
Hope you are enjoying your journey 🚆  with OpenGenus


configure fails with "Endpoint temporarily disabled"

oghliner configure currently fails with the error Endpoint temporarily disabled:
11-19 14:43 > oghliner configure

Configuring Travis to auto-deploy to GitHub Pages…

Your repository has a single remote, origin.
Ok, I'll configure Travis to auto-deploy the origin remote (mykmelez/test-auth-github).

To check the status of your repository in Travis and authorize Travis to push
to it, I'll create GitHub personal access tokens, for which I need your GitHub
username and password (and two-factor authentication code, if appropriate).

ℹ For more information about GitHub personal access tokens, see:
    https://github.com/settings/tokens

Username: mykmelez
Password:

× Checking credentials… error!

You're using two-factor authentication with GitHub.
Please enter the code provided by your authentication software.

Auth Code: 123456

✓ Checking credentials… done!
✓ Creating temporary GitHub token for getting Travis token… done!
  Getting Travis token… \Endpoint temporarily disabled

That causes the "live" tests to fail on Travis, for example on this build job:

Configure "before each" hook for "activates inactive repository - displays message on failure":
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
at tryCallOne (node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:37:12)
at node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:103:15
at flush (node_modules/promisify-node/node_modules/nodegit-promise/node_modules/asap/raw.js:50:29)

CLI interface, oghliner as a template should work:
Error: the number 1 was thrown, throw an Error :)

CLI interface, oghliner as a template "after all" hook for "should work":
Error: the string "no access token supplied" was thrown, throw an Error :)
at tryCallOne (node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:37:12)
at node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:103:15
at flush (node_modules/promisify-node/node_modules/nodegit-promise/node_modules/asap/raw.js:50:29)

CLI interface, oghliner as a tool should work:
Error: the number 1 was thrown, throw an Error :)

CLI interface, oghliner as a tool "after all" hook for "the CLI program should have an exit code != 0 if deploy fails":
Error: the string "no access token supplied" was thrown, throw an Error :)
at tryCallOne (node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:37:12)
at node_modules/promisify-node/node_modules/nodegit-promise/lib/core.js:103:15
at flush (node_modules/promisify-node/node_modules/nodegit-promise/node_modules/asap/raw.js:50:29)

Here's a nock recording of the transaction:
nock('https://api.travis-ci.org:443')
  .post('/auth/github', {"github_token":"…"})
  .reply(503, "Endpoint temporarily disabled", { connection: 'close',
  server: 'nginx',
  date: 'Thu, 19 Nov 2015 22:52:24 GMT',
  'content-type': 'application/json',
  'content-length': '29',
  status: '503 Service Unavailable',
  'access-control-allow-origin': '*',
  'access-control-allow-credentials': 'true',
  'access-control-expose-headers': 'Content-Type, Cache-Control, Expires, Etag, Last-Modified',
  'strict-transport-security': 'max-age=31536000',
  'x-endpoint': 'Travis::Api::App::Endpoint::Authorization',
  'x-pattern': '/github',
  'x-oauth-scopes': 'public',
  'x-accepted-oauth-scopes': 'public',
  vary: 'Accept,Accept-Encoding',
  'x-rack-cache': 'invalidate, pass',
  via: '1.1 vegur' });

The Past Incidents section of Travis CI Status has this to say:

Nov 19, 2015
/auth/github disabled due to continued DDoS
Resolved - Login via the CLI is now working again. If you have a custom client using /auth/github, it might be misidentified as being part of the DDoS. If so, please get in touch via<EMAIL_ADDRESS>Nov 19, 19:04 UTC
Investigating - We have been under a constant DDoS attack for the last two months. We are able to handle the load since we last addressed these attacks a few weeks ago. However, this seems to now be impacting the GitHub API using us as a proxy. We have therefore disabled the endpoint in question (/auth/github), which unfortunately means that it is temporarily impossible to log in on travis-ci.org via the CLI. If you are already logged in, you are not affected. Also, travis-ci.com and our web interface on travis-ci.org are not affected either.
Nov 19, 18:52 UTC

So I'll email them. But we should also handle the errors better, both in UX (which should do more than just output the error and die) and in how we report/throw the error to the caller, per the test harness.

This is a direct link to the incident report: https://www.traviscistatus.com/incidents/bntk781kb8y8

I received a response from Travis that they've whitelisted the Oghliner user agent, but I'm still seeing an error (albeit a different one):
✓ Creating temporary GitHub token for getting Travis token… done!
  Getting Travis token… \you are currently not allowed to perform this request. please contact<EMAIL_ADDRESS>
I've contacted them again about the new error.

The live tests are still failing (with a different error).

https://github.com/mozilla/oghliner/pull/222


Update README for V2 development

This updates the README by removing mention to pirouette-plutusir and adds a disclaimer about V2 not being released yet and points to the version 1 tag.
This also removes the README in cooked-validators full of now outdated information. It will have to be replaced by a new quick presentation and tutorial. It removes the one in examples as well which talked about Split which is not present at the moment, and refered to the README in cooked-validators.
So basically, a reset READMEs PR

Is the 'direnv' part of the README still applicable ?

I agree that direnv should probably not be mentioned here. People already using nix-direnv know that where there is a nix develop there is an echo 'use flake' > .envrc, so this line would only target people not knowing about direnv, and I'm not sure it's the place of our README to make people aware of such a tool.

I would also remove the table of contents at the beginning of the file. GitHub already shows a table of contents for Markdown files anyways, and will be much better at keeping it in sync (the current version is clearly very broken).

I removed the table of contents and section on direnv. Will merge when I receive green lights from the CI.


Pnpm instead of yarn

PR Checklist:

[x] Link to related issue: closes #210 closes #213
[x] Add changelog entry linking to issue
[ ] Added tests (if needed)
[x] (If new feature) added in description / readme

@Polleps can you try running this locally and see if that works well?

Tests succeeding locally, merging.


Fix File location for UserData.html

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

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@rgbm21 - thanks for your contribution!


Error when using multiple times

Hey there
I really do love this plugin for semantic release. However, when using with multiple locations, the pushing part results in a "no such image" error.
https://github.com/smartive-education/cas-fee-adv-qwacker-api/blob/7610ddae918477787e180ef01b4dabbb024d4b68/.releaserc.json#L7-L49
The configuration above is used to create a set of images for ghcr.io and one for the google artifact repository.
When running the action, the following logs appear:

[7:31:42 AM] [semantic-release] › ℹ  Start step "prepare" of plugin "@codedependant/semantic-release-docker"
[7:31:42 AM] [semantic-release] [@codedependant/semantic-release-docker] › ℹ  building image europe-west6-docker.pkg.dev/ost-cas-adv-fee/qwacker-api-docker/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e
[7:31:42 AM] [semantic-release] [@codedependant/semantic-release-docker] › ⬤  build command: docker build --quiet --tag europe-west6-docker.pkg.dev/ost-cas-adv-fee/qwacker-api-docker/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e --build-arg SRC_DIRECTORY=cas-fee-adv-qwacker-api --build-arg TARGET_PATH=. --build-arg NPM_PACKAGE_NAME=qwacker-api --build-arg NPM_PACKAGE_SCOPE --build-arg CONFIG_NAME=cas-fee-adv-qwacker-api --build-arg CONFIG_PROJECT=ost-cas-adv-fee/qwacker-api-docker --build-arg GIT_SHA=7610ddae918477787e180ef01b4dabbb024d4b68 --build-arg GIT_TAG=v1.1.2 --build-arg BUILD_VERSION=1.1.2 --build-arg COMMIT_SHA=7610ddae918477787e180ef01b4dabbb024d4b68 -f /home/runner/work/cas-fee-adv-qwacker-api/cas-fee-adv-qwacker-api/Dockerfile /home/runner/work/cas-fee-adv-qwacker-api/cas-fee-adv-qwacker-api
sha256:ca4dc9af82b89c9b146af2bddbcd34c292e380bd167ad97c39700e809bc29794
[7:33:24 AM] [semantic-release] › ✔  Completed step "prepare" of plugin "@codedependant/semantic-release-docker"
[7:33:24 AM] [semantic-release] › ℹ  Start step "prepare" of plugin "@codedependant/semantic-release-docker"
[7:33:24 AM] [semantic-release] [@codedependant/semantic-release-docker] › ℹ  building image ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e
[7:33:24 AM] [semantic-release] [@codedependant/semantic-release-docker] › ⬤  build command: docker build --quiet --tag ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e --build-arg SRC_DIRECTORY=cas-fee-adv-qwacker-api --build-arg TARGET_PATH=. --build-arg NPM_PACKAGE_NAME=qwacker-api --build-arg NPM_PACKAGE_SCOPE --build-arg CONFIG_NAME=cas-fee-adv-qwacker-api --build-arg CONFIG_PROJECT=smartive-education --build-arg GIT_SHA=7610ddae918477787e180ef01b4dabbb024d4b68 --build-arg GIT_TAG=v1.1.2 --build-arg BUILD_VERSION=1.1.2 --build-arg COMMIT_SHA=7610ddae918477787e180ef01b4dabbb024d4b68 -f /home/runner/work/cas-fee-adv-qwacker-api/cas-fee-adv-qwacker-api/Dockerfile /home/runner/work/cas-fee-adv-qwacker-api/cas-fee-adv-qwacker-api
sha256:ca4dc9af82b89c9b146af2bddbcd34c292e380bd167ad97c39700e809bc29794
[7:33:24 AM] [semantic-release] › ✔  Completed step "prepare" of plugin "@codedependant/semantic-release-docker"

and then pushing the first (google artifactory) does work, however when trying to push the ghcr images:
[7:34:01 AM] [semantic-release] › ℹ  Start step "publish" of plugin "@codedependant/semantic-release-docker"
[7:34:01 AM] [semantic-release] [@codedependant/semantic-release-docker] › ℹ  tagging docker image cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e
[7:34:01 AM] [semantic-release] [@codedependant/semantic-release-docker] › ℹ  pushing image: ghcr.io/smartive-education/cas-fee-adv-qwacker-api tag: 1.1.2
[7:34:01 AM] [semantic-release] › ✖  Failed step "publish" of plugin "@codedependant/semantic-release-docker"
[7:34:01 AM] [semantic-release] › ✖  An error occurred while running semantic-release: Error: Command failed with exit code 1: docker tag ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e ghcr.io/smartive-education/cas-fee-adv-qwacker-api:1.1.2
Error response from daemon: No such image: ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e
Error: Error: Command failed with exit code 1: docker tag ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e ghcr.io/smartive-education/cas-fee-adv-qwacker-api:1.1.2
Error response from daemon: No such image: ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e
    at makeError (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/@codedependant/semantic-release-docker/node_modules/execa/lib/error.js:59:11)
    at handlePromise (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/@codedependant/semantic-release-docker/node_modules/execa/index.js:114:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Image.tag (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/@codedependant/semantic-release-docker/lib/docker/image.js:121:5)
    at async publish (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/@codedependant/semantic-release-docker/lib/publish.js:29:5)
    at async validator (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/semantic-release/lib/plugins/normalize.js:34:24)
    at async /home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/semantic-release/lib/plugins/pipeline.js:37:34
    at async Promise.all (index 0)
    at async next (/home/runner/work/_actions/cycjimmy/semantic-release-action/v3/node_modules/p-reduce/index.js:16:18) {
  shortMessage: 'Command failed with exit code 1: docker tag ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e ghcr.io/smartive-education/cas-fee-adv-qwacker-api:1.1.2',
  command: 'docker tag ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e ghcr.io/smartive-education/cas-fee-adv-qwacker-api:1.1.2',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: 'Error response from daemon: No such image: ghcr.io/smartive-education/cas-fee-adv-qwacker-api:934b96dca07d0ae2ef7e',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false,
  pluginName: '@codedependant/semantic-release-docker'
}

addition: I already used this technique here: https://github.com/WirePact/k8s-contract-repository/blob/main/.releaserc.json
BUT the difference is, in the wirepact repo, it's two different dockerfiles


if I have an account of deepL

how to use this with my account? sometime need to translate more than 5000 characters

I am willing to work on this if someone could provide me further information:

Does the official deepl-python package from DeepLcom not work with a DeepL API Free account?
What is the benefit of the DeepL API Free API?
Does logging in to https://www.deepl.com/translator with the DeepL API Free account increase any limits or give any benefits at all?
What are the official limits of using deepl.com without using an account?
Is the free remaining free quota visible somewhere?

Does the official deepl-python package from DeepLcom not work with a DeepL API Free account?
I think the official deepl-python package from DeepLcom work with a DeepL API Free account.
What is the benefit of the DeepL API Free API?
DeepL API Free API has no limit on the number of characters per translation, but only 500,000 per month.
Does logging in to https://www.deepl.com/translator with the DeepL API Free account increase any limits or give any benefits at all?
In fact, I will be logging in https://www.deepl.com/translator using a DeepL Pro account https://www.deepl.com/pro , which allows for no word limit per translation and no monthly total limit. If I use the api instead of the web or app, it will charge $25 per 1 million.
What are the official limits of using deepl.com without using an account?
Only 5000 characters per translation.
Is the free remaining free quota visible somewhere?
I'm not sure, because I don't have a free api account. But I am sure that DeepL Pro account can translate unlimited characters per time using web or app, and the total number of characters per month is also unlimited. You can see a description of the DeepL Pro account here https://www.deepl.com/pro .

Okay, I'm not quite sure I understand the problem.
I just setup a DeepL API Free account and tried to translate text using the website, but ran into the following error message:

Your current plan does not include the use of DeepL Translator via our website.

Then I tried to translate text using the official deepl-python package and my Deepl API Free account it worked fine:
 deepl --auth-key "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx:xx" text "Guten Tag!" --to "ZH"

Output:
日安!

So what is the problem with using the official python package?
My package only allows text translation without an account, and signing in doesn't seem to give any advantages over just using the official package.

https://www.deepl.com/pro/change-plan#single

Ah, I finally understand what you meant.
There are still some problems before being able to implement this feature.
After analyzing the requests during the login process, I found that the request with the name
https://w.deepl.com/account?request_type=jsonrpc&il=D&method=login is responsible for it.
This is the code to login to deepl.com (generated using Chromium DevTools and Postman):
import requests
import json

url = "https://w.deepl.com/account?request_type=jsonrpc&il=D&method=login"

email =<EMAIL_ADDRESS>password = "xxxxxxxx"
keep_login = True  # ?
login_id = 12345678  # ?
clearance_duration = 29  # ?

payload = json.dumps({
  "jsonrpc": "2.0",
  "method": "login",
  "params": {
    "email": email,
    "password": password,
    "keepLogin": keep_login,
    "version": "44",
    "loginDomain": "default",
    "clearanceInfo": {
      "status": 200,
      "duration": clearance_duration
    }
  },
  "id": login_id
})

headers = {
  'authority': 'w.deepl.com',
  'sec-ch-ua': '" Not A;Brand";v="99", "Chromium";v="98"',
  'sec-ch-ua-mobile': '?0',
  'user-agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/98.0.4758.80 Safari/537.36',
  'sec-ch-ua-platform': '"Linux"',
  'content-type': 'application/json',
  'accept': '*/*',
  'origin': 'https://www.deepl.com',
  'sec-fetch-site': 'same-site',
  'sec-fetch-mode': 'cors',
  'sec-fetch-dest': 'empty',
  'referer': 'https://www.deepl.com/',
  'accept-language': 'de-DE,de;q=0.9',
}

response = requests.request("POST", url, headers=headers, data=payload)

print(json.dumps(response.json(), indent=2))

Output:
{
  "jsonrpc": "2.0",
  "id": 12345678,
  "error": {
    "code": -31999,
    "message": "Insufficient clearance. Please solve challenge and come again",
    "data": {
      "challengeUri": "https://clearance.deepl.com/captcha?redirect_to=https%3A%2F%2Fw.deepl.com%2Fclearance%2Flogin"
    }
  }
}

The challengeUri leads to a captcha solving page, which is currently not easy to complete using python.
I assume the incorrect (?) duration parameter value in the clearanceInfo block prevents proper login.
What has to be found out is the following:

how and where is the duration parameter value calculated
does the id play a role?
does keepLogin play a role?
what does "code": -31999 mean?

Is it possible to run translator_late.min.$41c5cd.js with Python? like pyexecjs？

Is it possible to run translator_late.min.$41c5cd.js with Python? like pyexecjs？

There's way more to that, and it's not that easy.
If anyone wants to give it a try, go ahead.

I have tried to use pro account and translated by loading session to simulate web request. But there is no limit as officially stated, after about 500000 characters of translation, the pro account will be cancelled. The pro account I purchased is a kind of team account sold online.

I believe the message Insufficient clearance. Please solve challenge and come again is being triggered by cloudflare bot detection. In other words when trying to login using jsonrpc, cloudflare is detecting this is not coming from a browser and is prompting to solve a challenge. I believe to fix this you will have to either fool cloudflare into thinking the request is coming from a browser or you will have to figure out how to solve the challenge.


Add restart test for sandbox recovery.

For https://github.com/kubernetes-incubator/cri-containerd/issues/238.
Add integration test to test sandbox state recovery across cri-containerd restart.
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Will address comments today.

@mikebrow Addressed comments.

There is no Version in image service

Actually this is a problem... We just haven't hit this yet.
We assume that image and runtime services may be separate, but we don't have separate Status and Version function.

WithBlock the problem is that we are not using that in Kubernetes today

I think adding WithBlock in kubelet cri remote client may change the original behavior, which might cause some bug. It doesn't add value, but may introduce bug, so I don't think we should do that.
However, we should let kubelet cri remote client accept extra grpc option, so that other users than kubelet could be able to customize it. We could file an issue for that.

Filed an issue for WithBlock https://github.com/kubernetes/kubernetes/issues/57060.


[stable/prometheus-operator] Update README.md for wrong example prometheus.prometheusSpec.retentionSize

Fix wrong example value of  prometheus.prometheusSpec.retentionSize to correct.
Signed-off-by: Yosapol Jitrak<EMAIL_ADDRESS>What this PR does / why we need it:
README in example is wrong units of retentionSize. It can't be start prometheus-prometheus-operator-prometheus workload.

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/retest

/ok-to-test

/ok-to-test
/lgtm

You'll need to bump the chart version for any change to be valid

You'll need to bump the chart version for any change to be valid

I update document to correct and don't change anything. Why I need to bump the chart version?

The readme is packed into the chart when it is built. If you do not change the version, a new chart version cannot be built and pushed to the chart repository.
You must bump the chart version according to semver rules (For this change, changing the minor version is ok) whenever you make any change to any file. This is enforced by the CI process and I will not be able to merge the changes until you do it.

/retest

/ok-to-test

/retest

/ok-to-test

/lgtm


Add example for 2D triangle-point intersection

This should be useful for XGC. In particular, this pull request separates TreeTraversal construction and actually running the search allowing applications to use the TreeTraversal class in their own Kokkos kernels.

I'm deeply confused about the purpose of this PR and its relationship to XGC. In my understanding, XGC would require calling tree traversal individually from each thread, with no collaboration. This PR seems to still assume that there's a place in XGC where all thread are able to launch the search at the same time.
I thought that instead the API for TreeTraversal should be changed to allow a single thread (like team_member) as an argument.
I may be missing something here.
Also, this PR tries to do too many things simultaneously, and should be split in multiple, like the part touching the core (with the addition of unit testing) and adding an example.

Also, this PR tries to do too many things simultaneously, and should be split in multiple, like the part touching the core (with the addition of unit testing) and adding an example.

This is a draft showing my current progress.

I'm deeply confused about the purpose of this PR and its relationship to XGC. In my understanding, XGC would require calling tree traversal individually from each thread, with no collaboration. This PR seems to still assume that there's a place in XGC where all thread are able to launch the search at the same time.

I'm happy to discuss why this approach might or might not work.

This should now be in decent shape to be reviewed again. As opposed to the initial approach, we now run a "classical" batched query.

We only see SYCL warnings that are being addressed in #923.

I'd like to have NDEBUG (except for the final one checking the results) and print outs removed (print outs may be replaced by leading comments).
I think it would work well if you have them in one of the commits in history to be able to easily restore the code, but they add a bulk to the example. If we want a user to read easily, we want to make it as short as possible.

Here you go!

masterleinad/ArborX#7
I also noticed that det and inv_det are actually equal to 1.f for this configuration. So, if you accidentally miss using them in any of the formulas, the check would still succeed. It may be better to shift some of the nodes slightly during the triangle generation so that it doesn't happen.

retest this please


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 854 ms

Resolved: Bofrost.at performance has improved in 3fc6b22 after 10 minutes.


Interpolate default string values

archaius-pull-requests #242 SUCCESS
This pull request looks good

NetflixOSS » archaius » archaius-pull-requests #73 SUCCESS
This pull request looks good


Docs: Glossary Addition for Model

While reviewing a research meeting a point of misunderstanding came up around the use of the word Model, which has a distinct meaning in TBP that contrasts with deep learning.  This glossary item hopes to clarify this.

You could also add a link to here for further reading: https://thousandbrainsproject.readme.io/docs/how-learning-modules-work#object-models
And to this FAQ question: https://thousandbrainsproject.readme.io/docs/faq-monty#do-cortical-columns-in-the-brain-really-model-whole-objects-like-a-coffee-mug-in-v1

@vkakerbeck I made some changes that I think require a re-review.