chore: add combine-dependabot-prs workflow

Details
Add a new workflow to automatically combine dependabot PRs into a single PR. Any PR with a failing build or the pr: do not combine label will be excluded from the new combined PR.
This workflow runs automatically every Monday at 1PM UTC (6AM PST), or it can be run manually from the "actions" tab in the repo.
Motivation
Reduce the number of dependabot commits in the repo
Context
This action is already used in the accessibility-insights-service repo on a manual trigger. After a discussion, our team has decided to experiment with using this action on an automatic trigger in our other repos.
Pull request checklist

[n/a] Addresses an existing issue: Fixes #0000
[n/a] Added relevant unit test for your changes. (yarn test)
[n/a] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[n/a] Ran precheckin (yarn precheckin)
[n/a] Described how this PR impacts both the ADO extension and the GitHub action

Codecov Report

Merging #1376 (ec6c95c) into main (0679434) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head ec6c95c differs from pull request most recent head a49ed9e. Consider uploading reports for the commit a49ed9e to get more accurate results

@@           Coverage Diff           @@
##             main    #1376   +/-   ##
=======================================
  Coverage   91.97%   91.97%
=======================================
  Files          62       62
  Lines        1607     1607
  Branches      206      206
=======================================
  Hits         1478     1478
  Misses        129      129

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Missing C++/winrt sample

Hello,
When selecting C++/winrt on the language select box, the samples displayed on the page are still C#.
They should be in C++/winrt.
Regards,

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

ID: efdbf325-cfae-54ca-9f32-0d6dbce462cc
Version Independent ID: e9476192-6dde-b261-d24f-7862d3b7934b
Content: DependencyObject.RegisterPropertyChangedCallback Method (Windows.UI.Xaml) - Windows UWP applications
Content Source: winrt-api-build/xml/Windows.UI.Xaml/DependencyObject.xml
Service: uwp
Sub-service: winrt-reference
Technology: winui
GitHub Login: @jwmsft
Microsoft Alias: jimwalk

Yes, in fact on API reference topics like this one, that language picker affects only the "Syntax" section. It doesn't affect the code examples that exist in the topic.
Providing code examples in C# is the first priority. Then, usually if the scenario would especially benefit from it, we try to provide a C++/WinRT version also. For example, the Win2D "Hello, World!" quickstart does have a C++/WinRT version.
However, that wouldn't be good ROI for every code example. Many of them are quite mechanical to port to C++. So for those cases, we have resources such as the C++/WinRT content in general, and then the Porting the Clipboard sample to C++/WinRT from C#—a case study and Move to C++/WinRT from C# topics in particular.
So I'll close this issue for now.
-Steve


Tracking supported RL libraries with ONNX Export

[x] StableBaselines3
[ ] Sample Factory
[x] Ray RLLib
[ ] CleanRL

Duplicate of #84


click points

Recently, I researched on interactive segmentation. I would like to ask what is the click point map format (ex: gaussaion heatmap) to feed into network.

Hi, clicks are encoded as a 2-channel disk map.

Does 2-channel mean that one is positive and the other channel is negative?

Yes, you are right.

Thanks a lot


2 bugs with snapshot mode

Bug is not really a bug it could be annoying for smoo when you rewind and open snapshot mode and wait you can teleport.
Filters dont go away until you rewind

Showcase for both bugs are here
https://imgur.com/a/8Y1q0AZ

1 happens because time travel is not disabled when you open snapshot mode or the map. Thats why you can see the trail on the map. The thing even charges up during those modes.


Fixed broken Eris link

What does this PR do?

[ ] Adds or edits a feature
[x] Fixes a bug
[ ] Edits typings
[x] Edits documentation
[ ] Edits config files
[ ] Edits CI or workflows
[ ] Something else

Things to check

[x] Have you tested changes locally?
[x] Have you followed our linter rules?
[x] Have you ensured TypeScript compiles?

Notes

[ ] New dependencies added
[ ] Unsure of functionality

Description
I've edited the Eris link because the correct link is https://abal.moe/Eris/ with a uppercase E, https://abal.moe/eris/ returns a 404 Not Found error.

Merged!
Sorry for the first closure. Github mobile app isn't super user friendly in pointing out what does what. 😅


[21.05] firefox: introduce nspr_latest, update nss_latest

Motivation for this change
ERROR: Requested 'nspr >= 4.32' but version of NSPR is 4.30.0
ERROR: Requested 'nss >= 3.68' but version of NSS is 3.67.0

Fixup #133305
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I have builds for all three firefox flavors running. They all passed the configure phase, so we could merge this early, to fix the situation quickly. Or we wait until I have completed all tests. I don't mind either way.

The 91 and 91esr tests have completed. The 78esr test is looping in wait_for_sound.


commissioner in the web ui doesn't work

Describe the bug
Border router:
I set up a border router on Raspberry Pi 3B, in the Border Router web UI "Commission" page, i set up two parameters and start the commissioner, and got the information "Commission operation is success":
Network Passphrase: 12345678
Joiner Pskd: J01NMM

Joiner
then I tried to start the joiner, but it failed to join:
> factoryreset
> ifconfig up
Done
> panid 0xffff
Done
> scan
| J | Network Name     | Extended PAN     | PAN  | MAC Address      | Ch | dBm | LQI |
+---+------------------+------------------+------+------------------+----+-----+-----+
> | 0 | OpenThreadDemo   |<PHONE_NUMBER>222222 | 1234 | 2e4f28c66b2de83e | 15 | -45 | 192 |
Done
> joiner start J01NMM
Done
> Join failed [NotFound]
>

I also have a question, what is the "Network Passphrase"?  Where do i need this ? Seems that i only need the "Pskd" when i start a joiner.

@cahty82008 , thanks for raising this issue.
"Network Passphrase" should be removed from the Commission page.
I have submitted #780 to fix the issues you have raised.


[SUPPORT] Failed to upsert for commit time

Describe the problem you faced
Hi all,
We are currently facing some sporadic issues with the error: org.apache.hudi.exception.HoodieUpsertException: Failed to upsert for commit time when doing a CoW upsert.
I searched about this error and all i found was that it is related with multiple-writing scenario, that it's not my case, we are using the single writter Hudi config, using hudi 0.8 in AWS Glue jobs and our jobs do not run in parallel for the same dataset.
This error it's not fully reproducible, but it mainly happens in my biggest datasets, for some time, increasing the number and size of the AWS Glue machines fixed this error, but I also had this problem even with 14 * G.2X machines. But, we did not think that this problem is 100% related to data size, cause some bigger datasets worked on the same machines configs.
Can you guys help me found what other causes may throw this error?
Stack error
ERROR:__main__:WRITE:HUDI:TABLE:S3:ERROR: An error occurred while calling o193.save. : org.apache.hudi.exception.HoodieUpsertException: Failed to upsert for commit time<PHONE_NUMBER>4859 at org.apache.hudi.table.action.commit.AbstractWriteHelper.write(AbstractWriteHelper.java:62) at org.apache.hudi.table.action.commit.SparkUpsertCommitActionExecutor.execute(SparkUpsertCommitActionExecutor.java:46) at org.apache.hudi.table.HoodieSparkCopyOnWriteTable.upsert(HoodieSparkCopyOnWriteTable.java:94) at org.apache.hudi.table.HoodieSparkCopyOnWriteTable.upsert(HoodieSparkCopyOnWriteTable.java:84) at org.apache.hudi.client.SparkRDDWriteClient.upsert(SparkRDDWriteClient.java:154) at org.apache.hudi.DataSourceUtils.doWriteOperation(DataSourceUtils.java:214) at org.apache.hudi.HoodieSparkSqlWriter$.write(HoodieSparkSqlWriter.scala:186) at org.apache.hudi.DefaultSource.createRelation(DefaultSource.scala:145) at org.apache.spark.sql.execution.datasources.SaveIntoDataSourceCommand.run(SaveIntoDataSourceCommand.scala:45) at org.apache.spark.sql.execution.command.ExecutedCommandExec.sideEffectResult$lzycompute(commands.scala:70) at org.apache.spark.sql.execution.command.ExecutedCommandExec.sideEffectResult(commands.scala:68) at org.apache.spark.sql.execution.command.ExecutedCommandExec.doExecute(commands.scala:86) at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:131) at org.apache.spark.sql.execution.SparkPlan$$anonfun$execute$1.apply(SparkPlan.scala:127) at org.apache.spark.sql.execution.SparkPlan$$anonfun$executeQuery$1.apply(SparkPlan.scala:155) at org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151) at org.apache.spark.sql.execution.SparkPlan.executeQuery(SparkPlan.scala:152) at org.apache.spark.sql.execution.SparkPlan.execute(SparkPlan.scala:127) at org.apache.spark.sql.execution.QueryExecution.toRdd$lzycompute(QueryExecution.scala:80) at org.apache.spark.sql.execution.QueryExecution.toRdd(QueryExecution.scala:80) at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:676) at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:676) at org.apache.spark.sql.execution.SQLExecution$$anonfun$withNewExecutionId$1.apply(SQLExecution.scala:78) at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:125) at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:73) at org.apache.spark.sql.DataFrameWriter.runCommand(DataFrameWriter.scala:676) at org.apache.spark.sql.DataFrameWriter.saveToV1Source(DataFrameWriter.scala:285) at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:271) at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:229) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244) at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357) at py4j.Gateway.invoke(Gateway.java:282) at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132) at py4j.commands.CallCommand.execute(CallCommand.java:79) at py4j.GatewayConnection.run(GatewayConnection.java:238) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalArgumentException at org.apache.hudi.common.util.ValidationUtils.checkArgument(ValidationUtils.java:31) at org.apache.hudi.common.table.timeline.HoodieActiveTimeline.transitionState(HoodieActiveTimeline.java:396) at org.apache.hudi.common.table.timeline.HoodieActiveTimeline.transitionRequestedToInflight(HoodieActiveTimeline.java:453) at org.apache.hudi.table.action.commit.BaseCommitActionExecutor.saveWorkloadProfileMetadataToInflight(BaseCommitActionExecutor.java:114) at org.apache.hudi.table.action.commit.BaseSparkCommitActionExecutor.execute(BaseSparkCommitActionExecutor.java:128) at org.apache.hudi.table.action.commit.BaseSparkCommitActionExecutor.execute(BaseSparkCommitActionExecutor.java:78) at org.apache.hudi.table.action.commit.AbstractWriteHelper.write(AbstractWriteHelper.java:55) ... 39 more
Hoodie configs:
"hoodie.datasource.write.keygenerator.class": "org.apache.hudi.keygen.ComplexKeyGenerator",
"hoodie.datasource.write.payload.class": "org.apache.hudi.common.model.DefaultHoodieRecordPayload",
"hoodie.datasource.hive_sync.partition_extractor_class": "org.apache.hudi.hive.MultiPartKeysValueExtractor",
"hoodie.table.name": table_name,
"hoodie.datasource.write.recordkey.field": IDX_COL,
"hoodie.datasource.write.partitionpath.field": pks,
"hoodie.datasource.write.hive_style_partitioning": "true",
"hoodie.datasource.write.precombine.field": tiebreaker,
"hoodie.datasource.write.operation": operation,
"hoodie.write.concurrency.mode": "single_writer",
"hoodie.cleaner.commits.retained": 1,
"hoodie.fail.on.timeline.archiving": False,
"hoodie.keep.max.commits": 3,
"hoodie.keep.min.commits": 2,
"hoodie.bloom.index.use.caching": True,
"hoodie.parquet.compression.codec": "snappy"
Environment Description
AWS Glue Job

Hudi version :
0.8

Spark version :
"Spark 2.4 - Python 3 with improved job times (Glue Version 2.0)"

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

Running on Docker? (yes/no) :
No

Additional context
Infrastructure: Glue Job + S3

hmmm, interesting. do you happened to have any driver logs related to this? Stack trace given above does not have much info :(.
what do you mean by biggest datasets?
I mean, I understand your hudi dataset size is large. But does your write batch is large too? can you give us some insights on your dataset characteristics in general. like # partitions, data size, updates vs inserts, etc.

Hi,
Thanks for the reply.
I was trying in some ways to change the memory and memory-overhead parameters without success.
Since i am using the AWS Glue to run this, i opened a ticket with AWS support and received this response:
_These 'conf' settings are not available for override. [1] This allows AWS to manage the resources dynamically and provide efficient performance. Below are  several argument names used by AWS Glue internally that you should never set:
--conf — Internal to AWS Glue. Do not set!
--debug — Internal to AWS Glue. Do not set!
--mode — Internal to AWS Glue. Do not set!
--JOB_NAME — Internal to AWS Glue. Do not set!
I am writing down difference between different worker types below .
-->For G.1X Worker nodes:
The maximum amount of driver memory you can provide is 10GB.
Each executor is configured with 10 GB memory
Each executor is configured with 8 spark cores
Each worker is configured with 1 executor
Each worker maps to 1 DPU (4 vCPU, 16 GB off memory, 64 GB disk), and provides 1 executor per worker.
For G.2X Worker nodes:
The maximum amount of driver memory you can provide is 20GB.
Each executor is configured with 20 GB memory
Each executor is configured with 16 spark cores
Each worker is configured with 1 executor
Each worker maps to 2 DPU (8 vCPU, 32 GB of memory, 128 GB disk), and provides 1 executor per worker
Each executor has several task slots (or CPU cores) for running tasks in parallel [4].

numExecutors =
* (DPU - 1) * 2 - 1 if WorkerType is Standard
* (NumberOfWorkers - 1) if WorkerType is G.1X or G.2X

numSlotsPerExecutor =

4 if WorkerType is Standard
8 if WorkerType is G.1X
16 if WorkerType is G.2X

numSlots = numSlotsPerExecutor * numExecutors_

Reference: https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-glue-arguments.html
So, in this case, the best option on AWS Glue is to use the G.2X machines, that we are already using, that sets the following parameters by default (and can't be overriden)
--conf spark.dynamicAllocation.enabled=true
--conf spark.shuffle.service.enabled=true
--conf spark.dynamicAllocation.minExecutors=1
--conf spark.dynamicAllocation.maxExecutors=6
--conf spark.executor.memory=20g
--conf spark.executor.cores=16
--conf spark.driver.memory=20g
--conf spark.default.parallelism=112
--conf spark.sql.shuffle.partitions=112 --conf
Like i mentioned on my initial post, we used 14 * G.2X machines and also got this error.
Since these parameters can't be change, there is any tuning that can be done on Hudi configuration side?

Have you tried tuning GC by any chance?
Do you mind posting spark UI stages screenshot to see if there are any skews are GC overhead.

Hi @nsivabalan,
After some other testing, we figured out what was our problem.
Based on the AWS recommendation, we were wrongly assuming that the any memory parameter passed on the glue spark context were being automatically replaced by Glue. (Like some indicators showed us on SparkUI), but, in some ways this parameters were affecting in a negative way the Glue native memory management.
Basically, removing all the manual memory settings (like memory and memory overhead) on our glue spark context made the jobs running properly without any memory issues. (We also tested the same jobs with the double of the files and with fewer machines, and it also worked well)
Thank you for help on this case.

awesome, thnx for the update.

Hello , trying to write a glue job script for reflecting CDC delete . Insert and update are working fine. Kindly help
import sys
from awsglue.transforms import *
from awsglue.utils import getResolvedOptions
from pyspark.sql.session import SparkSession
from pyspark.context import SparkContext
from awsglue.context import GlueContext
from awsglue.job import Job
from pyspark.sql import DataFrame, Row
from pyspark.sql.functions import *
from pyspark.sql.functions import col, to_timestamp, monotonically_increasing_id, to_date, when
import datetime
from awsglue import DynamicFrame

import boto3

## @params: [JOB_NAME]
args = getResolvedOptions(sys.argv, ["JOB_NAME", "database_name", "kinesis_table_name", "starting_position_of_kinesis_iterator", "hudi_table_name", "window_size", "s3_path_hudi", "s3_path_spark" ])

spark = SparkSession.builder.config('spark.serializer','org.apache.spark.serializer.KryoSerializer').config('spark.sql.hive.convertMetastoreParquet','false').getOrCreate()

sc = spark.sparkContext
glueContext = GlueContext(sc)
job = Job(glueContext)
job.init(args['JOB_NAME'], args)

logger = glueContext.get_logger()

database_name = args["database_name"]
kinesis_table_name = args["kinesis_table_name"]
hudi_table_name = args["hudi_table_name"]
s3_path_hudi = args["s3_path_hudi"]
s3_path_spark = args["s3_path_spark"]

commonConfig = {'hoodie.datasource.write.hive_style_partitioning' : 'true','className' : 'org.apache.hudi', 'hoodie.datasource.hive_sync.use_jdbc':'false', 'hoodie.datasource.write.precombine.field': 'ApproximateCreationDateTime', 'hoodie.datasource.write.recordkey.field': 'id', 'hoodie.table.name': hudi_table_name, 'hoodie.consistency.check.enabled': 'true', 'hoodie.datasource.hive_sync.database': database_name, 'hoodie.datasource.hive_sync.table': hudi_table_name, 'hoodie.datasource.hive_sync.enable': 'true', 'path': s3_path_hudi}

partitionDataConfig = { 'hoodie.datasource.write.keygenerator.class' : 'org.apache.hudi.keygen.ComplexKeyGenerator', 'hoodie.datasource.write.partitionpath.field': "partitionkey, partitionkey2 ", 'hoodie.datasource.hive_sync.partition_extractor_class': 'org.apache.hudi.hive.MultiPartKeysValueExtractor', 'hoodie.datasource.hive_sync.partition_fields': "partitionkey, partitionkey2"}

incrementalConfig = {'hoodie.upsert.shuffle.parallelism': 68, 'hoodie.datasource.write.operation': 'upsert', 'hoodie.cleaner.policy': 'KEEP_LATEST_COMMITS', 'hoodie.cleaner.commits.retained': 2}

combinedConf = {**commonConfig, **partitionDataConfig, **incrementalConfig}

glue_temp_storage = s3_path_hudi

data_frame_DataSource0 = glueContext.create_data_frame.from_catalog(database = database_name, table_name = kinesis_table_name, transformation_ctx = "DataSource0", additional_options = {"startingPosition": "TRIM_HORIZON", "inferSchema": "true"})

def processBatch(data_frame, batchId):
    if (data_frame.count() > 0):

        DataSource0 = DynamicFrame.fromDF(data_frame, glueContext, "from_data_frame")

        your_map = [
            ('eventName', 'string', 'eventName', 'string'),
            ('userIdentity', 'string', 'userIdentity', 'string'),
            ('eventSource', 'string', 'eventSource', 'string'),
            ('tableName', 'string', 'tableName', 'string'),
            ('recordFormat', 'string', 'recordFormat', 'string'),
            ('eventID', 'string', 'eventID', 'string'),
            ('dynamodb.ApproximateCreationDateTime', 'long', 'ApproximateCreationDateTime', 'long'),
            ('dynamodb.SizeBytes', 'long', 'SizeBytes', 'long'),
            ('dynamodb.NewImage.id.S', 'string', 'id', 'string'),
            ('dynamodb.NewImage.custName.S', 'string', 'custName', 'string'),
            ('dynamodb.NewImage.email.S', 'string', 'email', 'string'),
            ('dynamodb.NewImage.registrationDate.S', 'string', 'registrationDate', 'string'),
            ('awsRegion', 'string', 'awsRegion', 'string')
        ]

        new_df = ApplyMapping.apply(frame = DataSource0, mappings=your_map, transformation_ctx = "applymapping1")
        abc = new_df.toDF()
        logger.info("This is abc = {}".format(abc))
        if str(abc["eventName"]) == "REMOVE":
            inputDf = abc.withColumn('Result',when(abc.id!=abc["id"],"True")).filter("Result==True").drop("Result")
        else:
            inputDf = abc.withColumn('update_ts_dms',to_timestamp(abc["registrationDate"])).withColumn('partitionkey',abc["id"].substr(-1,1)).withColumn('partitionkey2',abc["id"].substr(-2,1))

        # glueContext.write_dynamic_frame.from_options(frame = DynamicFrame.fromDF(inputDf, glueContext, "inputDf"), connection_type = "marketplace.spark", connection_options = combinedConf)
        glueContext.write_dynamic_frame.from_options(frame = DynamicFrame.fromDF(inputDf, glueContext, "inputDf"), connection_type = "custom.spark", connection_options = combinedConf)

glueContext.forEachBatch(frame = data_frame_DataSource0, batch_function = processBatch, options = {"windowSize": "10 seconds", "checkpointLocation":  s3_path_spark})

job.commit()


checkov: 2.0.820 -> 2.0.823, fix build

Motivation for this change
follow-up to: https://github.com/NixOS/nixpkgs/pull/159077
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Same as https://github.com/NixOS/nixpkgs/pull/159083?

Same as #159083?

no, I pin in this one. which I think is the right course, because there was removal jsonschema.compat

The change in #159083 works for me locally but this is the proper approach.


Add data returns for INSERT/UPDATE/UPSERT

This pull request places RETURNING * on all data manipulation queries (INSERT/UPDATE/UPSERT) that do not delete records, with the returned data being stored in the new Table.result attribute.
The purpose is to allow for a fastlite refactor to use Table.result attribute for improved stability and performance.

[!NOTE]
fastlite enhance that takes advantage of this code change: https://github.com/AnswerDotAI/fastlite/pull/45

Justification
RETURNING * is the standard SQL dialog to have data manipulation commands (INSERT/UPDATE/UPSERT) return the records that have been added/altered. Using RETURNING * instead of relying on the current last_rowid + follow-up queries system provides the following advantages:

Allows rollback and vacuum safety, something that last_rowid does not provide
Incurs no risk of corruption due to race conditions
Improved performance by having 2 less sql operations per data manipulation: select last_rowid and the follow-up query to get changes will not be performed

Methodology
Minimal changes to reduce impact to API users
Tests verified to pass

sqlite-minutils pytest suite
sqlite-minutils 01_core.ipynb
All fastlite test_ notebooks
fastlite 00_core.ipynb and index.ipynb
All fasthtml notebooks
fasthtml/examples/adv_app.py
Internal application tests

Exciting! :D


Revise the Implementation of Named Cluster Configs

Revise the Implementation of Named Cluster Configs
Named cluster configurations are supported in oshinko
using configmap volumes. However, there is a simpler
implementation which gives the user more flexiblity and
eliminates a timing problem on update of the configmap.

Note that a benefit of this approach (eliminating a volume mount for oshinko-rest) makes it possible to use the business logic of oshinko-rest somewhere else, like a CLI, without having to worry about where to store the named cluster configs.


jfh

Challenge Use CSS Selectors to Style Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.75 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

Kitty ipsum dolor sit amet, shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff.

@PhanXuanDuc, that is not issue. you could ask a help at FCC Help room


gifski: move to by-name, use useFetchCargoVendor

gifski: use useFetchCargoVendor
gifski: format using nixfmt
gifski: move to by-name
gifski: remove meta with lib use

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

That should be done with https://github.com/NixOS/nixpkgs/pull/356862.

https://github.com/NixOS/nixpkgs/pull/356862

@ofborg build gifski


improve async iter performance

Description
Performance fix for async iter. Use chunked fetch approach, chunk size can be altered from the outside.
Fixes:  #34

@jreese thank you for your feedback and review, I'll apply your suggestions as soon as I find some time, hopefully within a few days.

Thank you for working through this!


Performance audits

We @ClarenceAtim AND @RileyManda  have completed the implementation of Vet clinic database schema according to the stipulated requirements : 🌱
After:Owners tables
-altered table owners with email column:

SELECT * FROM visits where vet_id = 2;

SELECT * FROM owners where email =<EMAIL_ADDRESS>
Time improvement:

SELECT COUNT(*) FROM visits where animal_id = 4;

Explain analyze owners

Please kindly review our implementation and suggest any changes.
Thank you 🙏

We have completed implementing the following iterations as requested by the previous reviewer:
EXPLAIN ANALYZE SELECT COUNT(*) FROM visits where animal_id = 4;
Before:

After:

EXPLAIN ANALYZE SELECT * FROM visits where vet_id = 2;
Before:

After:

EXPLAIN ANALYZE SELECT * FROM owners where email =<EMAIL_ADDRESS>Before:

After:


Add bucket support

Add an optional bucket parameter to the config file so that uploaded files can be more organized

@n8maninger there is already a siaRootDir parameter and all files are stored under that directory :

Would adding a bucket parameter really be any different? Other than that the siashare directory wouldn't be underneath the default bucket.

It's a little different. Buckets provide a more clear boundary for apps that folders don't.


Cluster stuck in updating state after Rancher upgrade

Rancher Server Setup

Rancher version: Rancher upgrade from v2.5.9 to v2.6.0-rc1
Installation option (Docker install/Helm Chart): HA helm install

Information about the Cluster

Kubernetes version: v1.20.9
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Azure node driver

Describe the bug

Azure node cluster becomes stuck in updating state after Rancher upgrade
To Reproduce

Bring up a v2.5.9 HA install.
Deploy an Azure node cluster (3 etcd, 1 control, 3 worker) k8s version v1.20.9. Ubuntu 18.04 LTS
After the cluster becomes available, upgrade Rancher to v2.6.0-rc1.
Result
The cluster becomes stuck in updating state.
[file-deploy] Deploying file [/etc/kubernetes/kube-api-authn-webhook.yaml] to node [...]

An etcd node becomes unreachable.
Expected Result

All nodes should be active after Rancher upgrade.

I saw a downstream cluster go to Updating state (not a complete RKE up), but came back up Active . This was on an upgrade from 2.5.9 to 2.6.0-rc1

Not able to reproduce with upgrade from v2.5.9 to v2.6.0-rc1.
Created an ec2 cluster and azure node driver cluster. Both clusters stayed in Active state post upgrade.
@sowmyav27 mentioned that this issue doesn't reproduce all the time, so keeping it open in case it happens again. We can take a look at logs to confirm if the cluster actually went through provisioning then.

Could not reproduce clusters going into Upgrading state on an upgrade from 2.5.9 to 2.6.0-rc3

Closing this issue. Will reopen if we see this issue again


Update clear_history to use Range instead of Ranges

When loading IJulia, I received the following error:
julia> using IJulia
Warning: both Libdl and Base export "dlopen_e"; uses of it in module ZMQ must be qualified
ERROR: LoadError: LoadError: UndefVarError: Ranges not defined
 in include at ./boot.jl:250
 in include_from_node1 at ./loading.jl:129
 in include at ./boot.jl:250
 in include_from_node1 at ./loading.jl:129
 in reload_path at ./loading.jl:153
 in _require at ./loading.jl:68
 in require at ./loading.jl:51
while loading /home/brad/.julia/v0.4/IJulia/src/history.jl, in expression starting on line 29
while loading /home/brad/.julia/v0.4/IJulia/src/IJulia.jl, in expression starting on line 113

The warning is discussed in the comments in https://github.com/JuliaLang/julia/issues/11058
The error comes from a typo in history.jl, which hadn't mattered before, and for some reason started to matter recently.

(It wasn't a typo: if I remember correctly, in Julia 0.2, Range was a concrete type and Ranges was the abstract type.  This got renamed in 0.3, and they must have recently deleted the old deprecated name from 0.4?)

Tagged as IJulia 0.2.4.

@stevengj That's correct.

@stevengj thanks for the correction - I should have looked back at Julia's history before labeling it a typo


[NeoForge] Crash on startup

When launching a mod on NeoForge 1.21.1, a crash occurs, how to reproduce:

Install the NeoForge server version 21.1.80 for 1.21.1
Add the mod.
Start the server and... crash, yes.
Logs: https://mclo.gs/cSpEBDF
Debug logs: https://mclo.gs/xi4WN34

Ah... quite a silly mistake on my part, sorry. I haven't tested the mod on NeoForge, assuming Architectury would take care of modloader parity - woops! Thanks for reporting this.

The fix was quite simple (change the mod ID to conform to NeoForge's specifications) - seems like the mod is working fine after the latest commits. Given the mixin is exactly the same as in Fabric, and only uses vanilla code, I'm going to publish this hotfix as 2.0.1.
Please don't hesitate to open another issue if any other bugs pop up! Thanks again! <3


[HOLD E/App ##40548] [$250]  Profile - Zoom slider does not change position when moving to zoom an image

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.6-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/44788
Action Performed:

Navigate to account Settings > Profile
Click on the avatar
Click on upload photo and upload any JPEG image
Hover over the zoom slider and move to the right

Expected Result:
The zoom slider is moving to show how an image is zoomed
Actual Result:
The zoom slider stays on the same position when moving it to zoom uploaded image
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/fd7a8c59-f557-4379-882d-2f15fd7edbd0
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0130ac939be52a2a80
Upwork Job ID:<PHONE_NUMBER>081764317
Last Price Increase: 2024-07-11

Issue OwnerCurrent Issue Owner: @hungvu193

@Julesssss  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Cute cat.
This needs to be fixed, but I'm demoting it from being a blocker.

My best guess so far is that this PR introduced the bug

Thanks for looking

On reproducing the issue, Zoom slider does change its position but it's only when clicked and doesnt move when dragged. No animation for dragging
https://github.com/Expensify/App/assets/73997189/9dac4f95-5bd7-41ad-ae19-3e9eedf6eee6

Proposal
Please re-state the problem that we are trying to solve in this issue.
The zoom slider doesn't work.
What is the root cause of that problem?
In versions below 2.16.0, react-native-gesture-handler registers pointermove listeners but never unregisters them. This causes issues in development mode since StrictMode renders components twice. This has been fixed by https://github.com/software-mansion/react-native-gesture-handler/pull/2815.
What changes do you think we should make in order to solve the problem?

Wait until #45162 is resolved. Currently I'm using the work-in-progress solution from #45314.
Upgrade react-native-gesture-handler to version 2.16.0 or newer.

What alternative solutions did you explore? (Optional)
N/A

I'll take a look this weekend

Please check my Proposal here, it fixes the Crash when trying to upload the Avatar. I believe it fixes this issue also (maybe not completely).

Please check my Proposal here, it fixes the Crash when trying to upload the Avatar. I believe it fixes this issue also.

Your proposal did fixed the crashes but didn't fix this issue, also in your RCA's proposal, you mentioned the code that was added 14 months ago, I don't think that's correct RCA.

@QichenZhu Your proposal looks promising but I'm facing a crash while testing it on mobile. Did you test it with mobile platform?

@hungvu193 Yes, I came across the same problem on mobile, so I suggested holding for #45162 for now.

@hungvu193 Yes, I came across the same problem on mobile, so I suggested holding for #45162 for now.

I actually applied your proposal from that issue along with your mentioned PR, but it still crashed

@hungvu193 Thanks for testing and pointing out the problem. I'll revisit #45162 in a few hours.

I think that this notice is an error, but correct me if I'm wrong @hungvu193. Thanks!

I think that this notice is an error, but correct me if I'm wrong @hungvu193. Thanks!

Yeah. This issue has similar root cause with a DB, so a contributor mentioned in DB that his proposal will fix this issue too that's why we saw this alert. We can ignore that 😄

@hungvu193 The fix for #45162 has been merged. Could you retest on the latest main?

@hungvu193 The fix for #45162 has been merged. Could you retest on the latest main?

Sure. I'll retest it tomorrow in my time.

@hungvu193 I am withdrawing my proposal because react-native-gesture-handler 2.16.0, despite its README claiming to support React Native 0.68.0+, does not support React Native 0.73.4 as mentioned in this issue:

Our current policy regarding the new architecture support is to support only the most recent version, which at the time of writing is 0.74. The crash you're describing is caused by a breaking change between RN 0.73 and 0.74.

@QichenZhu Thanks for your update!
Still waiting for proposals.

I re-test it today, I think this issue is fixed.
https://github.com/user-attachments/assets/8276fb23-f321-4b0b-9289-10dfe8c03a52

Bug is fixed
https://github.com/user-attachments/assets/25783ca4-96f8-4d19-829a-39430bfb67fd

Why I am still able to reproduce it on the latest main v9.0.8-2
https://github.com/user-attachments/assets/003acbf5-e1da-459d-a858-90be8717c0d1

@hungvu193 @kavimuru @Ahmed-Abdella The bug is reproducible in development mode, but not in production mode.
Development mode
https://github.com/user-attachments/assets/53c96227-6f4e-4d3f-8ca8-01f92f89138d
Production mode
https://github.com/user-attachments/assets/52fc381e-d371-43ad-b29a-a32195c360ac

Oops I think I disabled StrictMode during test this issue

Proposal
Please re-state the problem that we are trying to solve in this issue.
The zoom slider doesn't work.
What is the root cause of that problem?
in the slider component
https://github.com/Expensify/App/blob/7f66ea3632c787bce4ab8b6dc12c252c1ddc7685/src/components/AvatarCropModal/Slider.tsx#L41-L53
the tooltipIsVisible state doesn't change in a correct way Here is what happened
the minDistance(5) make sure that the gesture doesn't get active until after 5 finger

minDistance(value: number)
Minimum distance the finger (or multiple finger) need to travel before the gesture activates. Expressed in points.

so the tooltipIsVisible state change to true before activating the gesture which prevent us to control the gesture handler
What changes do you think we should make in order to solve the problem?
We should call the minDistance() method with 0 instead of 5
Gesture.Pan()
        .minDistance(0)

by change the value to 0 we ensure the gesture active immediately
Result
https://github.com/user-attachments/assets/6f1c64b1-386b-47b6-971c-b4a1356bb922
What alternative solutions did you explore? (Optional)
N/A

Proposal updated for more explanation.

Thanks for your update. I'll review it on my morning.

So we lose the control of gesture handler before the activation, and now we can't active the gesture anymore and the onChange method (event) that's responsible to update the sllider will never run.

Hey can you give me more detailed about this one right here?
Also please notice that this issue is now only reproduced when StrictMode is enabled.

Hey can you give me more detailed about this one right here?

Maybe I complicated things a little bit, all I mean is that the onChange callback in Gesture.pan() never got invoked because we delayd the activation for a distance of 5 by using minDistance(5).
the onBegin callback got invoke, and immediately after start moving the onFinalize got invoked, means that the gesture ended. And the onChange callback is skipped. So we need to active the gesture immediately to trigger the onChange callback and apply the updates inside it.

Also please notice that this issue is now only reproduced when StrictMode is enabled.

Yes, Maybe because the fact that the StrictMode double invoke the component to identify the side effects and also enforce synchronous state updates that cause immediate rerender.
Maybe this is causing problems in how the state got managed and updated in the gesture handler after Delaying the activation using minDistance, which make the onChange not being invoked and the onFinalize called before it's time.
Setting the minDistance to 0 ensure that the gesture activate immediatey and the onChange that update the slider got invoked.

I've been under the water for past few days, I'll take another look today

Reviewing shortly

Maybe I complicated things a little bit, all I mean is that the onChange callback in Gesture.pan() never got invoked because we delayd the activation for a distance of 5 by using minDistance(5).

I don't think this is correct and setting minDistance to 0 feels like a workaround to me.
Upgrade react-native-gesture-handler will fix this issue, however we already had a PR to do that:
https://github.com/Expensify/App/pull/40548
@alexpensify Please put this PR on hold for https://github.com/Expensify/App/pull/40548, this bug's only reproduced on StrictMode, so I think that's fine to hold it.

Thanks for the update! I've updated this GH.

Weekly Update: On hold for https://github.com/Expensify/App/pull/40548

Weekly Update: hold for https://github.com/Expensify/App/pull/40548

Weekly Update:  https://github.com/Expensify/App/pull/40548

Weekly update: The other GH we have been tracking states - Closing this in favor of the 0.75 upgrade
I need to figure out what we should do here. @roryabraham any feedback? Thanks!

Should HOLD on https://github.com/Expensify/App/issues/37374 instead

Weekly Update: Thanks, Rory! Still on hold for https://github.com/Expensify/App/issues/37374

We are on RN 0.75 now, so I think this can come off hold. That issue isn't closed yet but is in the cleanup phase.

Thank you, @roryabraham, for the update. @hungvu193 please keep us posted if you agree with this plan. Thanks!

@alexpensify I think this is fixed on latest main, can you re-test this issue?
https://github.com/user-attachments/assets/c9b178f7-5512-43eb-9329-e4a78fa0b636

@lanitochka17 can your team please retest to confirm if there is still an issue? Thanks!

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

Weekly update: waiting on a retest

Weekly Update: I'll need to ask in Slack soon if no movement here.

Issue not reproducible during KI retests. (First week)

Closing - this is confirmed in the recent test.


New rule: jsx-children-newline

Examples of incorrect code for this rule:
<Hello
  foo="bar
>Children
</Hello>

Examples of correct code for this rule:
<Hello
  foo="bar
>
  Children
</Hello>

See https://github.com/jsx-eslint/eslint-plugin-react/blob/HEAD/docs/rules/jsx-one-expression-per-line.md

I don't believe this rule quite accomplishes my use case. For example, I want this to be correct:
<>Some text is: {variable} and goes here.</>

but with that rule it wants to make it:
<>
  Some text is:
  {` `}
  {variable}
  {` `}
  and goes here.
</>

I'm specifically looking to prevent the case of having multiline props but not multiline children

If you set allow to literal?

Ends up with the same result. I think the rule interprets putting in a variable as a non-literal causing it to force it to multiline.
The single-child option seems closest to what I want, but I would want it to consider Some text is: {variable} and goes here. as a single child and allow that to stay on one line

ah, well sure, a variable isn't a literal.
hmm, that seems like a reasonable option to add - non-jsx, which would allow a single line child for anything that's not a literal jsx element?

@ljharb happy to tackle this in coming days

That'd be great, thanks!

@ljharb So just to be sure I understand it correctly. The allow: 'non-jsx' would disallow:
<Foo>
    <Bar /><Bar /><Bar />
</Foo>

<Foo>
    aaa<Bar />bbb
</Foo>

but allow:
<Foo>
    aaa {variable} bbb
</Foo>

Right?

@ljharb whats the release timeline for this project? I see there haven’t been any releases since August and there are a couple of merged things I’m waiting on

@reediculous456 there's no strict timeline, but i'll likely cut a release sooner than later.

I hope to get #3678 in as well :)


Filter qs on qs of orgs with selected type

Get all organizations with selected type. Then filter existing queryset based on organizations present in the organization queryset.

Coverage decreased (-0.05%) to 91.349% when pulling 65316e40b1222c6bf579399a0dd8a7722851cebd on faulty-filters into 780afc4c59b2dfa134ad794a4c0d36de89c287c8 on master.


HARVESTER: fix resource loading logic

When switching between Explorer and harvester in the same cluster, the scheme needs to be reloaded, so we also need to use the product to determine
Related issue:
https://github.com/rancher/dashboard/issues/3894

Reproduce steps

Import a harvester cluster
Click the cluster name on the side menu and then nav to explorer dashboard.
Click the side menu "Virtualization Management".
Click the cluster name as the same as the above cluster name.
Nav to the harvester dashboard.

Result
Dashboard page lost many data.

Additional context
loadVirtual and loadCluster use the same state.clusterId, So it will not load Virtual store when the clusterId is not changed.


Stopped Working

My integration has suddenly stopped. Using latest version and understand how it works, but I cannot see any entities in the integration. I have reinstalled and made sure my router hasn't changed IP... nope.
Logger: homeassistant.loader
Source: loader.py:842
First occurred: 5:29:34 PM (1 occurrences)
Last logged: 5:29:34 PM
Unexpected exception importing platform custom_components.dius.sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 842, in get_platform
cache[full_name] = self._import_platform(platform_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/loader.py", line 859, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "", line 1204, in _gcd_import
File "", line 1176, in _find_and_load
File "", line 1147, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/dius/sensor.py", line 18, in
from .entity import DiusEntity
File "/config/custom_components/dius/entity.py", line 10, in
class DiusEntity(CoordinatorEntity):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 408, in init
wrap_attr(cls, property_name)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 380, in wrap_attr
raise TypeError(f"Can't override {attr_name} in subclass")
TypeError: Can't override _attr_unique_id in subclass

See latest release

Cheers.


Test how we handle unicode mapping

#442

Hi @ChenYan98, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Yan Chen). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Make small fix and :shipit:


Webview downloads fail on Linux due to a persist error

Okay, as I noted in the PR, it seems that the error which occurs when using the web browser is actually different from the one when extracting the archive. The web browser experiences an issue well before the archive extraction does. https://github.com/atlanticaccent/starsector-mod-manager-rust/pull/159 will fix the archive extraction.
The web browser error, when trying to install nexerelin, is as follows:
Navigation: https://fractalsoftworks.com/forum/index.php?topic=9175.0
Client answered: Download("https://github.com/Histidine91/Nexerelin/releases/download/v0.10.4d/Nexerelin_0.10.4d.zip")
Navigation: https://fractalsoftworks.com/forum/index.php?topic=9175.0
thread 'tokio-runtime-worker' panicked at 'Persist download: PersistError { error: Os { code: 18, kind: CrossesDevices, message: "Invalid cross-device link" }, file: NamedTempFile("/tmp/.tmp3sbLmg") }', src/app.rs:881:47

It may be worth making this ticket specifically about the archive issue and creating a new one for the web browser problem.

Originally posted by @TheDukeofErl in https://github.com/atlanticaccent/starsector-mod-manager-rust/issues/158#issuecomment-1145468797

The error message CrossesDevices makes me think that for some reason, calling persist is causing the folder to be persisted on a different disk than the temp directory. That would imply that the OS has been installed on one drive/device, but been configured to keep it's default tmp directory on another drive/device - which I have to say is unusual.
I'll see if there might be some way to abstract over this edge case and prevent this

That would imply that the OS has been installed on one drive/device, but been configured to keep it's default tmp directory on another drive/device - which I have to say is unusual.

This is standard practice on a Linux-based system. /tmp isn't really the same disk as the rest of the mounts, per se. It's actually it's own filesystem. A sample mount command would output something similar to this
tmpfs on /tmp type tmpfs
/dev/sda3 on / type ext4

In this (simplified) sample mount output, disk sda3 is mounted at root, covering the root dir and home dirs (/home). With this in mind, it seems that /tmp is being considered a different device. I don't think I've ever seen any *nix setup that has the /tmp dir actually mounted to the physical disk. tmpfs is very much temporary: it is always lost upon reboot. I imagine that rust has some built-in way to try to deal with this, as I'd be willing to wager other projects have run into this in the past. If nothing else, hopefully this explanation helps you figure something out.


Rate limit async change

Commit Message: As a follow up to 29199 we are moving the rate limit filter to use the change.
Additional Description: The original API would hash a proto on every single request. This will pre hash the proto and store it within the filter callback.
Risk Level: Low

@ggreenway Another follow up to the AsyncClientManager change. Moving over rate limiting

/assign @tyxia

/retest


Cropper region as circle

Hi! How can i change the cropper region as a circle when aspect ratio is 1:1?

You can do that from the css files, by setting border-radius: 50% for the .croppr-region class.

You can achieve this by patching the dist/croppr.js file
Function redraw, line 685, replace
       _this3.imageClippedEl.style.clip = 'rect(' + y1 + 'px, ' + x2 + 'px, ' + y2 + 'px, ' + x1 + 'px)';

with
      if(_this3.useCircle) {
         _this3.imageClippedEl.style.clipPath = 'circle(' + ((x2 - x1)/2) + 'px at ' + (x1 + (x2-x1) / 2) + 'px ' + (y1 + (y2-y1) / 2) + 'px)';
       }
       else {
         _this3.imageClippedEl.style.clip = 'rect(' + y1 + 'px, ' + x2 + 'px, ' + y2 + 'px, ' + x1 + 'px)';
       }

You can then set the useCircle property on your croppr object and it will use a circle instead, although you also need to constrain it to an aspect ratio of 1 when you instantiate the object (just past aspectRatio: 1 in options)
This would be a nice addition to the library I think


Allow jQuery wrapped elements in templates

Sorry, this is a pretty terrible PR. I've changed way too many things.
Also, I haven't looked at it in nearly 4 years, so it's probably about time to close it.
Happy to re-open if you'd like to discuss this change further 😉


typing.d.ts

@asadsahi  can you help me, please
i want to import model reference in this file but this gives me error I need to implicitly add a typing.d.ts reference in each file.
because i need load application data on initial page load.
import { Category, IPostModel, City } from './app/shared/models/post.model';
/* SystemJS module definition */
declare var module: NodeModule;
declare var global: NodeJS.Global;
declare module NodeJS {
interface Global {
appData: IApplicationConfig
}
}
interface NodeModule {
id: string;
}
interface IApplicationConfig {
cultures: ICulture[];
content: StringMap[];
loginProviders: string[];
cities: City[];   when i try to use this
categories: Category[]; when i try to use this
posts: IPostModel[]; when i try to use this
}
i already defined models Category, IPostModel in models folder so i don't need to again decalre in typing.d.ts file just want resue by importing.
can you please give me direction
Thanks

@sajidali2444 you don't need to declare typings again in typings.d.ts if you have model files in their respective feature folder.
Usually I tend to create intellisense type of models (i.e interfaces) in typings.d.ts and they are available in the whole project so that I don't have to import anything in feature folders just for intellisense purpose.
if you have created:
import { Category, IPostModel, City } from './app/shared/models/post.model';
then you don't need to defined them again in typings.d.ts.
I didn't fully understand your issue. but typings.d.ts already has some examples.

closing for now. Awaiting response.


SAP HANA XS Advanced - Clone and run SHINE applications

Great tutorial, unfortunately step 5 (build core-db module) fails in Hana 2 Express SPS03 at GCP with
Deploying "src/models/spatial/REGION_PRODUCT.hdbcalculationview"...     Error: com.sap.hana.di.role: Could not create the role definition in the database [8254541]       at "src/roles/admin.hdbrole" (0:0)      Error: com.sap.hana.di.role: "TRIGGER": invalid schema privilege [8254524]        at "src/roles/admin.hdbrole" (0:0)    Error: com.sap.hana.di.role: Deploying "src/roles/admin.hdbrole"... failed [8212145]      at "src/roles/admin.hdbrole" (0:0)

Hi, Klaus,
I tried to reproduce the problem on the same setting but have been unable to. Can you please add the details to the Q&A ( https://answers.sap.com/index.html ) so I can point the SHINE team to it? These issues are not meant for support.
Thanks,
Lucia,


first open source

Namaste,
I'm Aishwary Jain and I'll be contributing my first open source here

/assign

Hey
I will like to make my first open source contribution on this repo i am new to this world of open source so , I request for your assistance

@Nyxoy77 contact me on my linkedin "linkedin.com/in/aishwary-jain-555b042a7"
i can help you there

I look forward to making simple open-source contributions to this repository if you need someone. Please let me know if there is any work.

@Nyxoy77 contact me on my linkedin "linkedin.com/in/aishwary-jain-555b042a7" i can help you there
sure


Command-line task reports false success if STDIO left open

Originally posted by @glucaci in https://github.com/microsoft/azure-pipelines-tasks/issues/11334#issuecomment-583333300
I've created new issue because nobody answers on closed one.
Below is the content of the original post:
Original:
Lately we have the same problem with a .NET Core Task. I reported this also in https://github.com/microsoft/azure-pipelines-image-generation/issues/1386 because I'm not sure where this fits.
Starting: dotnet tool restore
==============================================================================
Task         : .NET Core
Description  : Build, test, package, or publish a dotnet application, or run a custom dotnet command
Version      : 2.164.0
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli
==============================================================================
/opt/hostedtoolcache/dotnet/dotnet tool restore --ignore-failed-sources --no-cache --verbosity normal

... restoring packages

Restore was successful.
The STDIO streams did not close within 10 seconds of the exit event from process '/opt/hostedtoolcache/dotnet/dotnet'. This may indicate a child process inherited the STDIO streams and has not yet exited.

and the task will remain blocked until build timeout expires.
Update:
Also with Task Version 2.169.1
Workaround:
Enable Continue on error and set Timeout on 1 min

Hi @glucaci, can you share the full debug logs where you have faced this issue?
Also, how can I repro this for investigation?

There is nothing more to add from the logs, it's running dotnet tool restore successfully and then it blocks and you can see the message The STDIO streams did not close... .
I don't know how you can reproduce it, because also on our pipelines it happens sporadic and i assume it's a race condition somehow.

I'm having the same issue. Before this task I also do a NuGetAuthenticate, because we are using a DevOps Artifact Repo.

I'm having the same issue. Before this task I also do a NuGetAuthenticate, because we are using a DevOps Artifact Repo.

We are getting this error too on dotnet test command. But it's occurring intermittently.

We are getting this error too on dotnet test command. But it's occurring intermittently.

We have also seen this happen in the past couple of weeks with dotnet test. It seems to happen when the runner is uploading the test results and then hangs, and also intermittently

we are having the same, even after isolating the publishing result into a different step we sometimes see this error message when the test runs are over.
the problem started all of a sudden a couple of weeks ago. It's not clear to us whether this depends on anything in our code at all (e.g. ApplicationInsights telemetry), the tests host itself or else. we went through our codebase several times to make sure all the dotnet hosts are properly disposed and we are currently stalled with the investigation.
while this is not really a blocking issue the impact on our business is huge as it's essentially breaking our automated deployment process several times a day with lots of delays
any help in troubleshooting this is greatly appreciated

Same issue here with bash
The STDIO streams did not close within 10 seconds of the exit event from process 'C:\Program Files\Git\bin\bash.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited.

This happens daily to us! Can this get more attention? Will there be improvements for dotnet tool restore using Azure DevOps?

@vineetmimrot please take a look

Small update; we've changed nothing and it hasn't occured in several days. Maybe something was changed at the agent level?

Hi all,
the dotnet task uses the task-lib to run dotnet commands, and the error is coming from there. From the task-lib code, it seems that the wait for streams to close(default 10000, which is 10 seconds) can be increased through the TASKLIB_TEST_TOOLRUNNER_EXITDELAY environment variable. Can you try to set it to 60000 or even more and see if this issue still persists? And if yes, please share the complete pipeline and full debug logs.

we have just had this start happening in a "AzurePowerShell@4" task where we run terraform from.
The STDIO streams did not close within 10 seconds of the exit event from process '/usr/bin/pwsh'. This may indicate a child process inherited the STDIO streams and has not yet exited.
Have tried the env var of TASKLIB_TEST_TOOLRUNNER_EXITDELAY=60000 but doesnt have any effect on the issue

Same issue with you.
Do you fix the issue, or have some workarounds?
@alanwales

We worked around it by outputting the logs to a file and failing the pipeline if issues were found. We added this to a PowerShell file which runs the build:
dotnet build "$buildFile" --configuration "Release" -warnaserror | tee build.log
foreach($line in [System.IO.File]::ReadLines("build.log")){
if($line -contains "Build FAILED.") {
Write-Error "Build forced as fail in powershell because errors were found in the build output. Fix the errors and retry"
}
}

Seems to happen more frequent now. Still happening when executing a dotnet tool restore after a NuGet Authenticate step (0.181.0). Setup is still similar to the one suggested by me above.

ack, will look into this and update today

hi all, since we have not been able to repro this issue, will need the pipeline(including any src) and debug logs for one of your failure instance(as i had said earlier) for investigating. It will be helpful in figuring out what kind of projects see this error. If you need to share in private, you can mail me at<EMAIL_ADDRESS>Also, can anyone tell how frequently you see this error(what percent of deployments)?

The issue was 100% reproducable with https://github.com/Codeuctivity/OpenXmlToHtml as long, as I missed closing every spawned chromium processes before the unit tests end.
After fixing the missing disposing of chromium processes, the pipeline stopped failing.
romanko also found out, that orphaned browsers could lead to the same issue https://stackoverflow.com/questions/55953465/azure-devops-pipeline-test-showing-partially-succeeded/56955030#comment120054880_56955030
You got a mail with links to the build history.

@tejasd1990 I've send an email with our pipeline and log-files.

In my case, we see this log:
  Determining projects to restore...
  Restored D:\Build\a2\212\s\Tests\Domain.Tests.Unit\Domain.Tests.Unit.csproj (in 421 ms).
  3 of 4 projects are up-to-date for restore.
CSC : warning SA0001: XML comment analysis is disabled due to project configuration [D:\Build\a2\212\s\Tests\Domain.Tests.Unit\Domain.Tests.Unit.csproj]
Test run for D:\Build\a2\212\s\Tests\Domain.Tests.Unit\bin\release\net461\ServiziCgn.Inventario.Domain.Tests.Unit.dll(.NETFramework,Version=v4.6.1)
Microsoft (R) Test Execution Command Line Tool Version 16.7.0
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...

A total of 1 test files matched the specified pattern.

Test Run Successful.
Total tests: 118
     Passed: 118
 Total time: 1,7004 Seconds
##[debug]Exit code 0 received from tool 'C:\Program Files\dotnet\dotnet.exe'
The STDIO streams did not close within 10 seconds of the exit event from process 'C:\Program Files\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited.
##[debug]The STDIO streams did not close within 10 seconds of the exit event from process 'C:\Program Files\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited.
##[debug]which 'C:\Program Files\dotnet\dotnet.exe'
##[debug]found: 'C:\Program Files\dotnet\dotnet.exe'

In this case it refers to a project with only classes and business logic inside. no dependency or anything more.
But sometimes it changes the project that cause this.
One of the way we have to repro the problem is starting two or more pipelines for the same repo.

I am experiencing this issue as well when running a bash script.  If I use a script block in the azure-pipelines.yml file and write out the bash code there, it works fine, but if I leverage it as a script, it will get the STDIO error.

Happy new year!
We've also been seeing this issue since at least November 2021. It's erroring for us when we run this task as part of our build and test stage.
- task: DotNetCoreCLI@2
      displayName: .NET Test
      inputs:
        command: 'test'

We also use the UseDotNet@2 task and set the version to 5.0.x before the build and test tasks.
We also don't have any dependencies such as drivers, and the tests we have are just NUnit tests.
We see this timeout happening around 80% of our pipeline runs.

Getting this error from dotnet test for a test project having multiple target frameworks.

Hi @abatishchev, could you please provide a link to your test project if it is public?
If not, could you provide steps to create such a test project to reproduce this issue?

Hi @stesee, could you please provide a hash of the commit on which this issue is reproduced in this project?

The issue was 100% reproducable with https://github.com/Codeuctivity/OpenXmlToHtml as long, as I missed closing every spawned chromium processes before the unit tests end.

As far as I can remember it was the change in the dependency https://github.com/Codeuctivity/OpenXmlToHtml/commit/9569b6fdc4d5b0dc25562673509ca1d70416023c#diff-5d0f6f7eb881422177fbe495c1b81ac39b4a349ab25c4299dcbe7ec13aa4cfb0L13
There was some disposing missing in the code of PuppeteerSharp.Renderer 1.1.14 which got fixed here
https://github.com/Codeuctivity/PuppeteerSharp.Renderer/compare/1.1.23...1.1.32#diff-8fdf9d8aa24b945d9607963cdaa80d28ec187e794de3bbdbd1043d8b1518786bR83

Because several commenters mentioned a similar issue with dotnet test, I wanted to report this too, see #17548.

@vineetmimrot please take a look

Did you eventually take a look at this issue?
This error is affecting our builds when we want to install a tool to generate code-coverage reports using dotnet CLI task, after a build task, that is nothing under our control.
We already added a 1-minute timeout to the failing task as workaround, but it's really annoying to see in 5 builds, 4 builds failing and then 1 passing because of this.

I cannot verify this currently, but this might be fixed by this agent bug fix.

We see this frequently with the DotNetCoreCLI@2 yaml task. It writes "The STDIO streams did not close within 10 seconds of the exit event from process 'C:\Program Files\dotnet\dotnet.exe'. This may indicate a child process inherited the STDIO streams and has not yet exited." to the log and then does nothing until the job times out (after 60 minutes).
Note: The dotnet command we run is "pack"

Hi,
Any updates on this one, we are also having this problem.
Thanks.

Hi Team,
Even I am Facing Similar Issue,
The STDIO streams did not close within 10 seconds of the exit event from process '/usr/bin/bash'. This may indicate a child process inherited the STDIO streams and has not yet exited.
In my Use Case I am Running a python Script from my azure pipeline which Internally Calls A python Script to Return Some Value which takes some 5 mins but during this Call, I am Facing this

I Have Already Tried adding this timeoutInMinutes: 30 as well
So Do we Have Any Resolution on this or any Workaround also is fine.
Please Drop A suggestion
Thank you.

Hitting the same issue with an AzureCLI@2 bash task. Running a background process that I can terminate but even with long waits before and after killing the process still getting the
The STDIO streams did not close within 10 seconds of the exit event from process '/usr/bin/bash'. This may indicate a child process inherited the STDIO streams and has not yet exited. and a hung (at 100%) ADO task :(


Use golangci-lint instead of assorted linters, build with github actions

Given binary release process is currently broken because of more than one reason, with this PR I want to fix multiple outstanding things and provide "official" binaries/docker image again.

Use golangci-lint instead of assorted linters, apart from simplifying setup overall it'll allow running linters locally with a simple make lint. We still have a lot of linters disabled but otherwise there're too many failures. Will address those in a follow-up PR.

Build with GitHub Actions instead of Travis CI. Added Release action that will push an "official" docker image to GitHub Package Registry.

Changes to Go code are based on linter warnings and are expected to be no-op. If you're reading this PR please feel free to do code review, feedback is welcome 👀🙏

@d1egoaz thanks for a thorough review, really appreciated! I'll update this PR addressing some of your comments soon.


fix: fix update bug when the dependency is from local path

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[x] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[ ] Unit test
[x] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 38 (0.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 36.014%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/client/client.go
0
5
0.0%

pkg/cmd/cmd_metadata.go
0
11
0.0%

pkg/cmd/cmd_run.go
0
11
0.0%

pkg/cmd/cmd_update.go
0
11
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
1272

Relevant Lines:
3532

💛  - Coveralls


[new product] mautic

close #4460

LGTM

Hi, let me know if any modifications are needed

Thanks for this PR @nperez60, overall LGTM. I have a few remarks / updates, see above.


Help me, im trying to join your discord , it says "Invite expired..."

I need your guys 's help to figure how to fix my buttons and port the MarcoClient's (My client.) in VRCModloader...

The actual link on github is outdated, the current one is https://discord.gg/rCqKSvR


Add some serverless discussion

I've been getting more and more into using Swift on the server, but I'm very into serverless. Thought it could be worth a mention, especially because there are a bunch of great packages out there.

@mattmassicotte Here are two packages I built that make serverless Swift a heck of a lot more practical:

Deploy to Vercel - https://github.com/swift-cloud/Vercel
Deploy to Fastly Compute@Edge https://github.com/swift-cloud/Compute

Sounds good to me, however I think we should keep it more compact by e.g. not mentioning DynamoDB and the trade-offs/advantages. What do you think @0xTim?
Also, are there other serverless functions we support? (thinking Google Cloud Functions, Azure, ....)

@mattmassicotte Here are two packages I built that make serverless Swift a heck of a lot more practical:

Deploy to Vercel - https://github.com/swift-cloud/Vercel
Deploy to Fastly Compute@Edge https://github.com/swift-cloud/Compute

These look cool! I'm not super-familiar with the underlying technologies being used, but seems like it could be a great addition. Open a PR!

I agree the database discussion is confusing here. I just wanted to mention it because it's typically a key part of a low-cost serverless deployment. But, its much more important this be informational! Will update.

@marius-se tried to do as you asked. I was going to move the Cassandra driver link to the top-level, but that whole area feels so Vapor-specific that I wasn't sure that was what you'd want.

Ok, I believe I've incorporated the requested changes, including the additional links from @AndrewBarba


update ocw import to match new ocw-to-hugo output structure

Pre-Flight checklist

[x] Testing

[x] Code is tested
[x] Changes have been manually tested

What are the relevant tickets?
Related to https://github.com/mitodl/ocw-to-hugo/issues/214
What's this PR do?
This PR alters the way ocw-studio parses ocw-to-hugo output to match the new output structure as detailed in this PR.  Some issues were also corrected with the way the import script determines the UID of a page.  Rather than trying to grab the UID from the menu, it's now taken from the uid property on the front matter of any given page.  The "page or resource" question is answered by checking the layout property and comparing it to known layouts for each type.  Root level pages also now correctly set the course home page as their parent.
How should this be manually tested?
I'm not exactly sure how this could be manually tested aside from the unit tests, as the import script is set up to pull directly from an s3 bucket and cannot be redirected at a local folder.  Either way, the unit tests should be checked locally against the new test data.

Would it be possible to reduce the number of test files?

@mbertrand Hypothetically the new content structure should be in the bucket.  I just checked the build server's deploy script and it runs the s3 sync with the --delete flag so the new structure should be there.  I wanted to get this PR up preemptively so that import isn't broken for too long.  I think we can reduce the amount of test data, I'll work on that tomorrow.

@mbertrand should be ready for another look

@mbertrand as far as the test data goes, I think the major difference is in the amount of PDF's recognized.  The files themselves are all fairly small.  What I'm wary about is that if we remove some of the files representing the PDF's that there will be links referencing them that will need to be edited out.  If it's a problem maybe we should just find better test courses?


commands: submit_tuxbuild: enable duration data in ALLOWED_METADATA

ALLOWED_METADATA doesn't save 'duration'. Duration can be used to track
the build time.
Signed-off-by: Anders Roxell<EMAIL_ADDRESS>

Nice stuff! Perhaps you could also send duration as metric?
Just add
metrics.update({'build/duration': build["duration"]}

Right below this line: https://github.com/Linaro/squad-client/blob/master/squad_client/commands/submit_tuxbuild.py#L162
The "build/duration" is just a suggestion.

Make metric name contain compile + defconfig + env

LGTM, there's still one failing test. I can fix that one out. I'll let you know when I roll it out


[Impeller] Flutter Gallery has some overdraw problems when navigating to sub apps

Navigate to the shopping sub app in the new flutter gallery and take a frame capture. Notice that we're taking a loooong time ~18ms on the iPad to render the frame. Then look into the draw calls, and notice that we're painting the previous route too!
Unclear what the problem is here. Are we missing a clip herustic? Or is this something that could be elimated by better ordering of paint commands

err not the shopping but Crane. Though it probably tracks for all of them

This happens with all of the routes actually.

This app is using the router/navigator the same way most other apps would, so it doesn't seem to be an app specific problem

Some sort of issue with modal routes? The route itself isn't really modal, it covers the entire screen, but perhaps it is implented with one and that is why the preivous route sticks around.

ahh potentially false alarm. We might still be able to do something here, but this is a but in the gallery. It thinkgs the iPad is a foldable device so it opens the sub-pass in a positioned widget instead of using a Route.
We might still use this as an opportunity to do better but its clearly a misuse of the Flutter API.

Closing as fixed with the linked patches. If there is something we need to track in Impeller internals, let's re-open with the specific work item.


taking toooooooooo much time to compile a 20 line code

We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
i had written a 20 line code in visual studio code and it takes much time to compile.i had waited for half an hour but  i didnt get any output.I dont know when will this run succesfully .I get this compiling duration delay  on nearly every programme i run on it. If the problem persist then i'll had to switch to my earlier software i.e.., CODE  BLOCK
VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz (4 x 3191)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: unavailable_offopengl: enabled_onprotected_video_decode: enabledrasterization: unavailable_offskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: unavailable_off

Load (avg)
undefined

Memory (System)
7.93GB (5.16GB free)

Process Argv
--crash-reporter-id 0a0147a5-1d1a-4d17-aea2-bb7d51deb5ab

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

code-runner
for
0.11.2

csharp
ms-
1.23.9

cpptools
ms-
1.2.0

java
red
0.75.0

swdc-vscode
sof
2.4.9

vscodeintellicode
Vis
1.2.11

vscode-java-debug
vsc
0.31.0

vscode-java-dependency
vsc
0.18.0

vscode-java-pack
vsc
0.12.1

vscode-java-test
vsc
0.28.0

vscode-maven
vsc
0.27.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30256638
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30251590

Hi, is it possible to post the source code, build tools/logs, please. It'll help others debug the issue.

Could you Please tell me which extension should i install so that system
doesn't take much time to compile even a larger file.
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:

Closed #116641 https://github.com/microsoft/vscode/issues/116641.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#event-4329164825, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3SAXDWTG2FC7IO2B2LS7BARDANCNFSM4XTHHRHA
.

I didnt get what you said.
Explain me properly and please name the extension i ought to download
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:

This issue is caused by an extension, please file it with the repository
(or contact) the extension has linked in its overview in VS Code or the
marketplace https://aka.ms/vscodemarketplace for VS Code. See also our issue
reporting https://aka.ms/vscodeissuereporting guidelines.
Happy Coding!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#issuecomment-778847355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3X3Y7QV74ZJH5BRWQ3S7BARBANCNFSM4XTHHRHA
.

Hi
I just found that scanf() is not working .
Whenever i use scanf() function then compiler didnt finished compiling not
even hours later. Could you now describe why this error occurs or any
extension i should download.
On Mon, Feb 15, 2021, 4:49 PM MANISH KUMAR<EMAIL_ADDRESS>wrote:

I didnt get what you said.
Explain me properly and please name the extension i ought to download
On Mon, Feb 15, 2021, 3:20 AM VS Code Issue Triage Bot <
<EMAIL_ADDRESS>wrote:

This issue is caused by an extension, please file it with the repository
(or contact) the extension has linked in its overview in VS Code or the
marketplace https://aka.ms/vscodemarketplace for VS Code. See also our issue
reporting https://aka.ms/vscodeissuereporting guidelines.
Happy Coding!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/116641#issuecomment-778847355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3CV3X3Y7QV74ZJH5BRWQ3S7BARBANCNFSM4XTHHRHA
.

Hi @manishrnl, your issue seems to be with your code not vscode nor any extension. Please try to compile the program from terminal.


cmd/go: GONOPROXY is undocumented

GOSUMDB, GONOSUMDB, and GONOPROXY variables were added in CL 173951.
Documentation for GOSUMDB and GONOSUMDB was added to https://tip.golang.org/cmd/go/#hdr-Module_authentication_failures, but I don't see any mention of GONOPROXY in the cmd/go docs at all.
CC @jayconrod @rsc

Some specific questions:

Should GOPROXY=off with GONOPROXY=*/x disable all fetches, or allow (only) */x to be fetched directly?
What should happen if GOPROXY includes off explicitly in the fallback chain, such as GOPROXY=https://my.proxy,https://other.proxy,off? (In that case, should fetches of the GONOPROXY paths be disabled?)

Also note that all environment variables should be documented at https://golang.org/cmd/go/#hdr-Environment_variables.  These new variables are not mentioned there.

One more question to document:

If GOPROXY does not include direct as a fallback, should GONOPROXY fall back to direct implicitly, or behave as if GOPROXY were set to off for that module?

I find it a bit odd that GONOPROXY is using sh-style globs anyway, given that GONOPROXY holds a set of package paths (AIUI) not URLs, and package paths are almost always matched with patterns as documented in go help packages.
That is, I'd expect:
GONOPROXY=myorg.com/...

to avoid the proxy for all modules under myorg.com.

If GOPROXY=off and GONOPROXY=* (say), then I think GONOPROXY wins. No matter what GOPROXY is set to, GONOPROXY matching the module means don't pay attention to that.

@rogpeppe, I see your point but I was trying to line up a bit with the standard NO_PROXY (for example https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html). Also I think it would be just too hard to write something like GONOPROXY=*.corp.yourcompany.com using ... (its not actually possible at all).

I guess I don't understand the GONOPROXY semantics (the whole point of this thread, and probably why I can't get it to work for me); how is GONOPROXY=*.corp.yourcompany.com different from GONOPROXY=....corp.yourcompany.com ?

how is GONOPROXY=*.corp.yourcompany.com different from GONOPROXY=....corp.yourcompany.com ?

The have different behavior for packages such as contrived.example.com/not.your.corp.yourcompany.com.


Docusaurus versions page as docs page

Creating a draft to demonstrate versions page as a docs page instead of a docusaurus page. This will be a good solution once we get rid of antd, but for now, it breaks the ui a little too much.

Vercel deployment seems to fail, but as described, this is just a draft and we're not going forward with this yet so closing this pr.


have access to the chart files in hook before applying it

hello guys,
I'm setting up helmfile for our production at tripadivisor. But I need some help from you for a specific need.
Each of our project have a /tmpl dir containing secrets tmpl and we generate secrets with consul-template. the /tmpl is packaged with the chart and pushed into chrtmuseum repository.
With helmfile, I want to apply a command to apply the command
consule-template to generate secrets values and apply it with other values.
To do that I did with hooks :
releases:
{{ if eq .Environment.Name "staging" }}

name: grafana
chart: chartmuseum/grafana
version: "0.1.0"
namespace: grafana
missingFileHandler: Error
hooks:

events: ["presync"]
showlogs: true
command: "consul-template -vault-retry-attempts=1 -log-level=debug -vault-renew-token=false -template grafana/tmpl/secrets.yaml.tmpl:secrets.yaml -once"
{{ end }}

but it seems the presync doesn't download the chart to have access to it, isn't it? I have a no such file or directory error ...
Do you have an idea of how to manage it?
thank you in advance

@dugouchet Hey! Thanks for trying Helmfile.
Unfortunately, Helmfile doesn't have access to the contents of automatically-downloaded charts. That's due to How Helmfile/Helm works - Under the hood, Helmfile just calls helm upgrade --install, and AFAIK helm upgrade doesn't extract files contained in chart archives.
A workaround that came to my mind is this:
hooks:
  command: "/bin/sh"
  args:
  - -c
  - "helm fetch chartmuseum/grafana --version 0.1.0 --untar && consul-template -vault-retry-attempts=1 -log-level=debug -vault-renew-token=false -template grafana/tmpl/secrets.yaml.tmpl:secrets.yaml -once"

helm fetch chartmuseum/grafana --version 0.1.0 --untar fetches the chart archive and extracts it under ./grafana, so that your consul-template command will read grafana/tmpl/secrets.yaml.tmpl without any problem.

Btw, this should ideally be done more declaratively. I'd appreciate any feature request towards that. Maybe add an configuration option to download the chart locally and fills the local chart path to a template variable?
releases:
- name: myapp
  chart: stable/mychart
  extractChartFiles:
  - tmpl/secrets.yaml.tmpl
  hooks:
    command: "/bin/sh"
    args:
    - -c
    - "consul-template -vault-retry-attempts=1 -log-level=debug -vault-renew-token=false -template {{`{{getChartFilePath "tmpl/secrets.yaml.tmpl"}}`}}:secrets.yaml -once"

Thanks for your response @mumoshu. It's exactly what I did. I'll see if I have time and if it's interesting for users to have this feature.

A solution here would also be useful for people wanting to run Kustomize on-top of a helm chart.

@conradj87 Yeah that makes sense. Actually, that's what I did for helm-x and its integration with helmfile.


Add WebAuthnValidator with P256Owner

Summary of this PR:
This test replaces the old WebAuthnOwner with a new one. Since it's set up to use the eth_sendTransaction method, the Account's sign() method is utilized. This ensures:

The initialization of an imAccount with wbAuthnValidator using initWithFactory() is correct.
The sign() methods in the webAuthnValidator class and the webAuthnValidatorOwner are functioning correctly.


[2] Conntecting two straight road objects

As a developer I want to connect two straight road in order to enable complex road networks.

Visualisierung demonstrieren


List requirements to run UI commands

requirements.txt file in main directory does not seem to concur with the packages required for the individual scripts in the User Interface directory. Can you please update the requirements so that I can install the required packages and test the code?

removing this as it is a duplicate issue. Still working on it though.


add maxRetry in NewWithOptions

This PR add maxRetry in the Client and Options  for indicates how many times we can retry the request

This is not needed, you can just set minio.MaxRetry in your init() function, let's not add new options with prior discussion on https://slack.minio.io


Remove CMDQueryStringSerialization dependancy

nice work! :green_apple:

Nice! How did you verify that this works?

Also how is ISO8601 being added?

I have tests for that and they are passing :smile:

Let's merge https://github.com/venmo/VENCore/pull/40 first.

Thanks Lionel!
On Sat, Sep 11, 2021 at 4:04 AM Lionel Alves @.***>
wrote:

Closed #39 https://github.com/venmo/VENCore/pull/39.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/venmo/VENCore/pull/39#event-5287325738, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACA5JDN6SEKZO2BSBIF27TUBMERPANCNFSM4BUIRERA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


chore: add a new example using Astro

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

Hello @smaye81,
I had tried to build something a little different, especially in terms of style, but it makes perfect sense to maintain consistency across all the examples.
So I updated everything as requested, especially the package name/version 🚀

Hey @smaye81,
I've made all the requested changes, including adding end-to-end tests to ensure the functionality is working as expected. Please take a look at the latest commit in my pull request and let me know if you have any further comments or concerns.
Thanks again for your help and guidance throughout this process 🎉

Looks great, @ftonato! Thanks for the contribution.


OLS-140: Added authorized endpoint to check if the user has permissions to acc…

…ess ols
Description

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

integration tests seems to be failing. Are those intended?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.93%. Comparing base (41dbeb3) to head (7c5621b).
Report is 53 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #519      +/-   ##
==========================================
+ Coverage   96.77%   96.93%   +0.16%
==========================================
  Files          47       50       +3
  Lines        1457     1534      +77
==========================================
+ Hits         1410     1487      +77
  Misses         47       47

Files
Coverage Δ

ols/app/endpoints/authorized.py
100.00% <100.00%> (ø)

ols/app/models/models.py
100.00% <100.00%> (ø)

ols/app/routers.py
100.00% <100.00%> (ø)

... and 13 files with indirect coverage changes

/test e2e-ols-azure-openai-gpt35

/lgtm
/approve


update readme

updated readme.

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


[aws-efs] Update base image to Alpine 3.10

Alpine 3.6 is out of service and has many security vulnerabilities that I introduce into my environment by using this container.
This PR attempts to update the base image to something more current.
Ref: https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases

I have signed the CLA.  Thank you.
/assign @wongma7

Thanks. This deserves a new release/tag. Not sure why travis is failing, apparently the mac job is running when it should be skipped, I'll need to fix it to unblock this.
/lgtm
/approve

Can this patch be merged please?
It would be great to have the image updated with the latest security patches.
Thanks!

Sorry, did not see that this blocked on test failure.
I will release a new image tag this week, please do not hesitate to bug me about it.

Thanks for looking into this @wongma7!
I do not see any recent tags in the repo: https://quay.io/repository/external_storage/efs-provisioner?tab=tags
Is this the right place to look for a new image?

@szmytson yes, a v2.3.0 was pushed there just now.

Could we please get a release tag for v2.3.0?

It's not fixed yet, I'll get https://github.com/kubernetes-incubator/external-storage/pull/1234 merged today


add a flow id to the analytics system

specifying a flow id for a set of events can group them together and
enables calculation client performance.

@jiayliu @tkchin @chuckhays

lgtm %nit


Add instruction for requesting extra credits

Add clear instructions on what needs to happen when credits run out.
Would probably be good to add something on these two pages:
getting started
tips
Although, maybe we need a FAQ page?

I think a FAQ section would be good, and we can then link to there from the two pages you mentioned?


Small Circle Problem

Hello,
Thanks for the gorgeous work, it was very use to integrate in my project.
But the circles is so small (I think)
Is there any way to make bigger than it looks?

Hi @yhaznedar,
Sorry for the delay in responding to you. Have you tried using the app:dotRadius property in your layout file? The default is 3dp, so you can supply it with any larger dimension to increase circle sizes.
If you do this, you'll probably want to increase the app:dotPadding property as well.
For all current configuration options, please see this page on the wiki: https://github.com/ronaldsmartin/Material-ViewPagerIndicator/wiki/Advanced-Usage
Feel free to reach out if you have any more questions!

You saved the day @ronaldsmartin, thank you good sir.


chore(ci): Try to display code coverage

I want set the minimum coverage to 80%.
But Jacoco analyze the compiled code and not the source code.
So some utils classes, lambda classes are not tested for him ..
Waiting for a solution


Visualize Linebreaks With "CRLR" or "LR"

Hello,
Please add option to visualize line breaks with CRLR or LR as it is done in Notepad++
Thank you,
Yuriy

To keep the number of issues in our inbox at a manageable level, we're closing issues that have been on the backlog for a long time but haven't gained traction: we look at the number of votes the issue has received and the number of duplicate issues filed. Thank you for your time and understanding.
P.S. If you disagree and feel that this issue is crucial: we're happy to listen and to reconsider.


feat: make a txsim binary build from Makefile and dockerfile

ReadMe for TL;DR
Closes https://github.com/celestiaorg/devops/issues/249

Codecov Report

Merging #2052 (a5a1d70) into main (5bcf4ad) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #2052   +/-   ##
=======================================
  Coverage   21.54%   21.54%
=======================================
  Files         127      127
  Lines       14293    14293
=======================================
  Hits         3079     3079
  Misses      10922    10922
  Partials      292      292

need one of us to merge @Bidon15?


chore(other): adds react-testing-library

PR Type

[ ] Bug fix
[ ] Feature
[ ] Code style update (whitespace, formatting, missing semicolons, etc.)
[ ] Refactor (i.e., no functional changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation changes
[ ] Other (please describe below):

Description
Adds react-testing-library and example card tests.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR fixes open issues?

[ ] Yes
[x] No

After merging in the changes removing the Card component, this needs to update to use another component. Otherwise, looks good to me. Glad we'll get some React component testing in here!

After merging in the changes removing the Card component, this needs to update to use another component. Otherwise, looks good to me. Glad we'll get some React component testing in here!

@bucko13 updated, please re-review.

LGTM. Sorry about the delay. Another merge conflict fix is needed 😬

LGTM. Sorry about the delay. Another merge conflict fix is needed

It's all good, I'll rebase it once https://github.com/unchained-capital/caravan/pull/92 is merged.

@bucko13 updated and ready to review/merge.


BUG - Contextmenu resizing by its self

While the crafting window is open the contextmenu for artisan is gound out of bound - It gets bigger and bigger.

v<IP_ADDRESS> fixed the issue. thumbs up


New rip uses folder of previous rip

Ripme version: v1.7.92
Java version: : 1.8.0_241-b07
Operating system: : 10.0.18362.836
Exact URL you were trying to rip when the problem occurred: n/a
Please include any additional information about how to reproduce the problem:

Expected Behavior
Paste link to rip. New folder created based on rip URL. Start rip.
Actual Behavior
Rip starts saving in the previous folder used. I didn't want to post this immediately as I assumed it would be spotted and patched straight away but as it hasn't (wut? no daily updates any more?!) and nobody else has mentioned this bug yet I'm doing my duty.

Could you post the links? or is always? are you using windows?

Nope (because) -> Yup. Yup.
Doesn't happen for you too?

I am using v1.7.90 and is working fine for me, let me update my repo and test again