broken build

user@subgraph:~/gopath/src/github.com/subgraph/roflcoptor$ go build
# github.com/subgraph/roflcoptor
./main.go:136: cannot use procsnitchClient (type *client.SnitchClient) as type "github.com/subgraph/go-procsnitch".ProcInfo in argument to NewProxyListener:
	*client.SnitchClient does not implement "github.com/subgraph/go-procsnitch".ProcInfo (wrong type for LookupTCPSocketProcess method)
		have LookupTCPSocketProcess(uint16, net.IP, uint16) *"github.com/subgraph/procsnitchd/vendor/github.com/subgraph/go-procsnitch".Info
		want LookupTCPSocketProcess(uint16, net.IP, uint16) *"github.com/subgraph/go-procsnitch".Info
user@subgraph:~/gopath/src/github.com/subgraph/roflcoptor$ ls

nevermind


Add token endpoints from rest_framework_simplejwt to url config

Changes

adding url endpoints for TokenRefreshView and TokenVerifyView

closes #37

Looks like test coverage decreased by a smidge

Thanks for reviewing!
Is the decreased coverage a blocking problem? I'm not sure if writing a test for this is really worth it...


Google Play Music not working

Hello there,
Is there any issues with the equalizer when using Google Play Music?
The extension works just fine with Youtube for example, but with Google Play Music after forcing HTML5 it doesn't work.
Thank you

Are you using also Google music extension? Because if they are both enabled EQ will not work.

I was and was causing the conflict, as soon  I have removed the extension it worked straight away!
Thank you for the help!


Feature/select all when filtered

Fix for #125 - select all after entering text
I messed this up a bit and it includes changes from PR #131 so please only merge if that is also accepted.

I confused myself with all my branches, but I think it's ok.


Windows 11 normal user problem

Windows 11 "normal user" / "standard user" has been tested?
I could not make it run with Windows 11 normal user..
Super user in Server 2019 and Windows 11 ( default user tested ) successfully.
What can be blocking normal user with Windows 11 to reach the SudoService.exe ?

If run the program as a standard user, the service (SudoService.exe) cannot get the elevated token of the user, which is a limitation of Windows.
To run elevated processes, the user should be an administrator.
How can a standard user run elevated processes? Of course, it is not possible.
If you mean that you want to run programs as another administrator account in a standard user environment, the tool currently does not implement this feature.
I'm not working on this project now, maybe I will add the feature in the future.


[HUDI-1453] Throw Exception when input data schema is not equal to th…

…e hoodie table schema
add test case
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Fix the bug when write  compatible data type to the hudi table, an exception throw out. For example when first write a double to the table, then write a int to the table, an exception throw out as the ISSUE [HUDI-1453] describe.
Brief change log
Currently, Hudi will store the incoming record schema(we call it inputSchema here) in HoodieWriteConfig. In the write stage, Hoodie use the inputSchema to parse the incoming record and read&write record to the hoodie table.
In most case it works well.However when the incoming schema is compatible but not equal to the table schema(write a "int" to "long").It will throw an Exception in write stage as the ISSUE [HUDI-1453] describe. I fix this issue by distinguishing the two kind schemas(inputSchema and tableSchema). Here is the major change:

Divide writerSchema into inputSchema and tableSchema in HoodieWriteHandle.The inputSchema is used for getInsertValue to parse the incoming record.And the tableSchema is used for read/write data in/to the table which is the schema of  the hoodie table.
Change all references to writerSchema to inputSchema or tableSchema, according to the usage scenario. If parser the incoming record, we use the inputSchema. If we read/write data from the table, we use tableSchema.
Add a getTableSchema method in HoodieTable to read the table schema.
Refactoring the construct method for HoodieWriteHandle. Add an Option param to the construct method for HoodieBootstrapHandle to pass the specified schema.

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added TestCOWDataSource#testWriteWithCompatibleType to verify the change

Committer checklist

[x] Has a corresponding JIRA in PR title & commit

[x] Commit message is descriptive of the change

[x] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #2334 (2e086b9) into master (236d1b0) will decrease coverage by 41.93%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master    #2334       +/-   ##
=============================================
- Coverage     52.34%   10.40%   -41.94%
+ Complexity     2631       48     -2583
=============================================
  Files           329       51      -278
  Lines         14808     1787    -13021
  Branches       1484      213     -1271
=============================================
- Hits           7751      186     -7565
+ Misses         6442     1588     -4854
+ Partials        615       13      -602

Flag
Coverage Δ
Complexity Δ

hudicli
?
?

hudiclient
?
?

hudicommon
?
?

hudihadoopmr
?
?

huditimelineservice
?
?

hudiutilities
10.40% <ø> (-59.71%)
0.00 <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

 Can you throw some light.
Schema evolution is throwing an exception w/ Hudi, i.e a field's data type evolved to a compatible data type and hudi fails to accommodate it? is that the problem.
If yes, can you check https://github.com/apache/hudi/pull/2350. there is a bug in schema compatibility check and the patch should fix it. If not, can you elaborate what exactly is the problem.
For eg: use-case given at https://github.com/apache/hudi/issues/2063 succeeds with https://github.com/apache/hudi/pull/2350

@pengzhiwei2018 : sorry I am not following the problem here. Can you throw some light.
Schema evolution is throwing an exception w/ Hudi, i.e a field's data type evolved to a compatible data type and hudi fails to accommodate it? is that the problem.
If yes, can you check #2350. there is a bug in schema compatibility check and the patch should fix it. If not, can you elaborate what exactly is the problem.
For eg: use-case given at #2063 succeeds with #2350

Hi @nsivabalan, When I write a long value  to the double type field in the table, It can pass the TableSchemaResolver.isSchemaCompatible,However it failed in the write stage.
I found the problem is that the schema (e.g double) used in write & read table are the same with the input schema(e.g. long). I fixed this problem by distinguishing the two schemas.

@pengzhiwei2018 @nsivabalan Is there a different way to resolve this issue ? The writer/reader schema is baked into many parts of the code, even on the reader side, see example here -> https://github.com/apache/hudi/blob/master/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/realtime/RealtimeCompactedRecordReader.java#L70
To be able to remove the concept of writer into input requires more changes in the code and also requires us to understand what does the readerSchema mean in this scenario.
I'm OK if you want to introduce another transient field called tableSchema and compare the writer (in your case inputSchema) against the tableSchema to throw the exception, but keep the concepts of writer/reader intact. If you want to propose changing them, I think putting a 1 pager about how writer/reader schema maps to your new suggested way (input/table) will help to understand how to reason about schemas going forward to avoid any regressions.

@pengzhiwei2018 @nsivabalan Is there a different way to resolve this issue ? The writer/reader schema is baked into many parts of the code, even on the reader side, see example here -> https://github.com/apache/hudi/blob/master/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/realtime/RealtimeCompactedRecordReader.java#L70
To be able to remove the concept of writer into input requires more changes in the code and also requires us to understand what does the readerSchema mean in this scenario.
I'm OK if you want to introduce another transient field called tableSchema and compare the writer (in your case inputSchema) against the tableSchema to throw the exception, but keep the concepts of writer/reader intact. If you want to propose changing them, I think putting a 1 pager about how writer/reader schema maps to your new suggested way (input/table) will help to understand how to reason about schemas going forward to avoid any regressions.

https://github.com/apache/hudi/blob/master/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/realtime/RealtimeCompactedRecordReader.java#L70

Hi @n3nash ,Thanks for your suggestion.
This PR only covers the part where HUDi writes the data, not the part where hudi reads the data. The introduced inputSchema/tableSchema is only used for parser the incoming record and read&write data in table.which is much different from the writer/reader schema in RealtimeCompactedRecordReader.
And I will describe the changes in more detail in the  Brief change log part of this PR.

https://github.com/apache/hudi/blob/master/hudi-hadoop-mr/src/main/java/org/apache/hudi/hadoop/realtime/RealtimeCompactedRecordReader.java#L70

Hi @n3nash ,Thanks for your suggestion.
This PR only covers the part where HUDi writes the data, not the part where hudi reads the data. The introduced inputSchema/tableSchema is only used for parser the incoming record and read&write data in table.which is much different from the writer/reader schema in RealtimeCompactedRecordReader.
And I will describe the changes in more detail in the  Brief change log part of this PR.

@pengzhiwei2018 first of all, thanks for these great contributions.
Wrt inputSchema vs writeSchema, I actually feel writeSchema already stands for inputSchema, input is what is being written, right? We can probably just leave it as is. and introduce new tableSchema variables as you have in the HoodieWriteHandle class.?
Like someone else pointed out as well, so far, we are using read and write schemas consistently. Love to not introduce a new input schema, unless its absolutely necessary .

Hi @vinothchandar ,thanks for your reply on this issue.
Yes, in most case ,the writeSchema is the same with the inputSchema  which can stands for the inputSchema . But in the case in this PR, we write the table twice:
First, we write a "id: long" to the table. The input schema is "a:long", the table schema is "a:long".
Second, we write a "id:int" to the table. The input schema is "a:int", but the table schema is "a:long" as the previous write. The write schema should be the same with the table schema, or else an Exception would throw out which is the problem we want to solve in this PR.
So in this case, we need to distinguish the difference between the inputSchema and writeSchema. The inputSchema is the incoming records's schema, but the writeSchema is always the tableSchema.
Here's the summary

The inputSchema is used to parser the record from the incoming data.
The tableSchema is used to write and read record from the table. When we want to write or read record to the table, we use the tableSchema.

So to rephrase the description this solves the case where the input-data has a compatible field (int) to be written to the table (long field). Can this issue not be solved at the input record level by converting the "int" data into the "long" before writing into HUDI?
hoodieTable.getTableSchema() always returns the "latest" schema which is the schema used for the last HoodieWriteClient (saved into commit instants). So when the "int" based RDD is written the table schema will no long have a "long" field. When this table schema is used to read an older file in the table (merge during updatehandle) then the reading should fail as a long (from parquet) cannot be converted to an int (from schema). This is actually a backward incompatible schema change and hence is not allowed by HUDI.
@pengzhiwei2018 Can you add a test to verify my hypothesis? In your existing test in TestCOWDataSource, can you write a long to the table in the next write? Also, can you read all the data using the "int" schema, even the older records which contain a long?

just to clarify. some schema evolution just for types are working fine w/ hoodie. for eg: integer to double works fine. Problem is that, double to int is where the issue is. I am not sure why schema compatibility check does not fail this evolution.

oh, didn't realize default schema compatibility check is false. I assume if I enable schema compatibility check, double to int evolution is likely to fail. So, not sure what this PR tries to achieve. At least from my local test run, integer to double worked for me.
https://gist.github.com/nsivabalan/91f12109e0fe1ca9749ff5290c946778

https://gist.github.com/nsivabalan/91f12109e0fe1ca9749ff5290c946778

Hi @nsivabalan , I have take a review for your test code. First you write a "int" to the table, so the table schema type is "int". Then you write a "double" to the table, so the table schema become to "double". The table schema changed from "int" to "double". I think this is more reasonable.
In my original idea, I think the first write schema(e.g. "int") is the table schema forever. The incoming records after that should be compatible with the origin table schema(e.g. "int"). This is this PR wants to solve. I can understand more clearly now. The table schema should be change to a more generic type (e.g. from "int" to "double"), but not always be the first write schema.
So I can close this PR now. Thanks @nsivabalan for correct me.

Yeah, I did verify by enabling schema compatability check. it will fail if we try to evolve a field from double to int.
scala> dfFromData5.write.format("hudi").
     |   options(getQuickstartWriteConfigs).
     |   option(PRECOMBINE_FIELD_OPT_KEY, "preComb").
     |   option(RECORDKEY_FIELD_OPT_KEY, "rowId").
     |   option(PARTITIONPATH_FIELD_OPT_KEY, "partitionId").
     |   option("hoodie.index.type","SIMPLE").
     |   option(TABLE_NAME, tableName).
     |   option("hoodie.avro.schema.validate","true").
     |     mode(Append).
     |   save(basePath)
org.apache.hudi.exception.HoodieUpsertException: Failed upsert schema compatibility check.
  at org.apache.hudi.table.HoodieTable.validateUpsertSchema(HoodieTable.java:629)
  at org.apache.hudi.client.SparkRDDWriteClient.upsert(SparkRDDWriteClient.java:152)
  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:83)
  at org.apache.spark.sql.execution.QueryExecution.toRdd(QueryExecution.scala:81)
  at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:677)
  at org.apache.spark.sql.DataFrameWriter$$anonfun$runCommand$1.apply(DataFrameWriter.scala:677)
  at org.apache.spark.sql.execution.SQLExecution$$anonfun$withNewExecutionId$1.apply(SQLExecution.scala:80)
  at org.apache.spark.sql.execution.SQLExecution$.withSQLConfPropagated(SQLExecution.scala:127)
  at org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:75)
  at org.apache.spark.sql.DataFrameWriter.runCommand(DataFrameWriter.scala:677)
  at org.apache.spark.sql.DataFrameWriter.saveToV1Source(DataFrameWriter.scala:286)
  at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:272)
  at org.apache.spark.sql.DataFrameWriter.save(DataFrameWriter.scala:230)
  ... 72 elided
Caused by: org.apache.hudi.exception.HoodieException: Failed schema compatibility check for writerSchema :{"type":"record","name":"hudi_trips_cow_record","namespace":"hoodie.hudi_trips_cow","fields":[{"name":"_hoodie_commit_time","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_commit_seqno","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_record_key","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_partition_path","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_file_name","type":["null","string"],"doc":"","default":null},{"name":"rowId","type":["string","null"]},{"name":"partitionId","type":["string","null"]},{"name":"preComb","type":["long","null"]},{"name":"name","type":["string","null"]},{"name":"versionId","type":["string","null"]},{"name":"doubleToInt","type":["int","null"]}]}, table schema :{"type":"record","name":"hudi_trips_cow_record","namespace":"hoodie.hudi_trips_cow","fields":[{"name":"_hoodie_commit_time","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_commit_seqno","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_record_key","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_partition_path","type":["null","string"],"doc":"","default":null},{"name":"_hoodie_file_name","type":["null","string"],"doc":"","default":null},{"name":"rowId","type":["string","null"]},{"name":"partitionId","type":["string","null"]},{"name":"preComb","type":["long","null"]},{"name":"name","type":["string","null"]},{"name":"versionId","type":["string","null"]},{"name":"doubleToInt","type":["double","null"]}]}, base path :file:/tmp/hudi_trips_cow
  at org.apache.hudi.table.HoodieTable.validateSchema(HoodieTable.java:621)
  at org.apache.hudi.table.HoodieTable.validateUpsertSchema(HoodieTable.java:627)
  ... 97 more


fix(debian): ensure unzip is available when installing

when installing a nerd font we need to unzip the file.
unzip is not installed by default in wsl.
this may also effect other distros

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: add log() method to BuildClient (Python)

This wraps the new /actor-builds/<BUILD_ID>/log API.

@fnesveda I haven't added any tests as the existing suite is very limited and it'd take some investment to extend it properly.
This is something I'd actually like to look into, to get the tests at least on par with apify-client-js, but it's probably not the biggest burning issue right now.

@fnesveda I haven't added any tests as the existing suite is very limited and it'd take some investment to extend it properly.
This is something I'd actually like to look into, to get the tests at least on par with apify-client-js, but it's probably not the biggest burning issue right now.

Yeah, that's OK, the tests here are pretty basic, so it would take quite a lot of effort to add new ones for specific endpoints. It would be nice to have proper tests for the client, but it's really not worth the effort right now.
When I was writing the Python API client, I decided not to replicate the test structure from the JS API client, because I didn't really like it - the unit tests basically have to mock the whole API server, which is a lot of duplicated code, and you have no guarantee that they're mocking it properly.
I was planning to come up with some proper testing framework, but that would mean rewriting half of the integration tests we have for the platform, and that seemed like a lot of effort too. And at that point we didn't know if the investment into Python tooling would be worth it, so we decided to not put in the effort into writing automated tests, and we just tested everything manually.
In the end, I think it was the right decision - the manual testing didn't take too much time, and we don't really do many structural changes to the API client that could cause bugs that only a full test suite in the API client would catch.
Anyway, I think the decision whether it's OK to keep the API client like this, with bare-bones tests, is now on @vdusek as the new owner of our Python tooling, what do you think?
If we ever decide to write proper tests here, I think we could take inspiration from the testing framework that's in the Apify SDK for Python, there the tests are much more detailed, and the test fixtures make writing tests quite easy, I would say.

Hi there, improving the test suite for the Python client is currently not on our roadmap due to the main focus on Crawlee for Python. So it's up to you guys, if you could find time to implement some better tests here, it would indeed be awesome. Otherwise, just stay with the basic tests we currently have in place.

@fnesveda Added the async API variant 👍

Re tests, I generally don't feel comfortable submitting code without at least some test automation 😅 Manual testing is a valid option but also by definition brittle.
I also don't really have that much of a problem with mocking. For a unit test, that's fine. Just a piece of code that tells me that the new method calls the expected API endpoint and pipes back the data. For me as a new developer on the team who doesn't really understand how the client is built from within, this is already useful feedback.
With integration / e2e tests, while they are obviously preferred, maintaining a full suite on every single layer (API -> client -> SDK) is perhaps also not very economical.
Anyway, as said, this is definitely something I'd enjoy looking into (after agreeing on an approach with both of you), but it also doesn't seem like a burning issue right now.

Updated CHANGELOG.md.


how use the pretrain checkpoint to continue train on my own corpus?

I want to load the pretrain checkpoint to continue train on my own corpus, I use the run_pretrain.py code and set the init_checkpoint to the pretrain dir, while I run the code, it raise error?
ERROR:tensorflow:Error recorded from training_loop: Restoring from checkpoint failed. This is most likely due to a Variable name or other graph key that is missing from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:

From /job:worker/replica:0/task:0:
Key bert/embeddings/LayerNorm/beta/adam_m not found in checkpoint
	 [[node save/RestoreV2 (defined at /usr/local/lib/python3.6/dist-packages/tensorflow_core/python/framework/ops.py:1748) ]]

I know that when finish training, it is better to remove adam_m and adam_v parameter to reduce the size of the checkpoint file, but I while want to continue train on the pretrain checkpoint, how to sovle this problem,  may be I can recovert adam reference variable name in the checkpoint file ?thank you

Hi all! I'm trying to initiate from mBERT checkpoint but it is missing the "bert/embeddings/LayerNorm/beta/adam_m" key in the list of variables (just like you described). I'm using TF=1.14 and have not found a solution in the conversion of checkpoint in TF >2. Did you find a solution?

Hi @RyanHuangNLP, if you have found a solution for this problem, would you mind sharing it? :)

Hi, I am also facing the same issue :
While trying to train from the mbert checkpoint : Key bert/embeddings/LayerNorm/beta/adam_m not found in checkpoint
While trying to predict from the mbert checkpoint : Key global_step not found in checkpoint
@RyanHuangNLP Did you find a solution for the same?
Thanks in advance!

Kindly share the solution if someone knows.
Thanks

Did anyone figure out a solution for this? I'm facing the same problem. Kindly share if someone does know.


add delay between detach volume and deleting volume

This PR to make the following changes

add some check between volume detach and volume deletion. Volume deletion will fail if volume is used and in the progress of detaching.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test


XMLHttpRequest fails on withCredentials line - undefined object

What is your Scenario?
When trying to call a lazy loaded JavaScript XMLHttpRequest call to load additional page data, hammerhead.js is throwing an error on the .withCredentials line

What is the Current behavior?
XMLHttp call fails in attached screenshots
What is the Expected behavior?
The XMLHttp request should be allowed to complete successfully.  Page works outside the testing script.
What is your public website URL? (or attach your complete example)
https://www.rsaconference.com/experts
What is your TestCafe test code?
await t
.click(Selector('main a').withText('AGENDA'))
.click(Selector('main a').withText('FULL AGENDA'))
Your complete configuration file
No response
Your complete test report
No response
Screenshots
No response
Steps to Reproduce

Open the Experts page using the Coveo search mechanism
Error is thrown and page does not load - shows blank boxes
Viewing the console shows the error being thrown by hammerhead

TestCafe version
1.18.3
Node.js version
14.5.0
Command-line arguments
testcafe "chrome" mobile-tests/**/* --reporter spec,xunit:report.xml --skip-js-errors --proxy-bypass *.coveo.com
Browser name(s) and version(s)
No response
Platform(s) and version(s)
No response
Other
No response

Thank you for your report. I reproduced the issue with the testcafe-hammerhead module and the gulp https-playground --dev command.

Duplicate of https://github.com/devexpress/testcafe-hammerhead/issues/2634


Unknown option '--webManifestPath'

I'm trying to generate assets across iOS, Android, and PWA builds. When try to use the --webManifestPath flag to configure the web directory I get error:
error: unknown option '--webManifestPath'

Is this flag not yet supported? Thanks

Just noticed the typo correction in the lastest commit 🙂I was referencing the stale readme on npmjs.com.


[Kernel][Java to Scala test conversion] Convert and refactor TestParquetBatchReader

Convert the tests written in Java to Scala. Scala suites have better test framework and takes few lines to write a test compared to Java.
Java suite: TestParquetBatchReader
Target Scala suite ParquetFileReaderSuite (create new file).
As part of the conversion, make use of the spark based reader to verify the returned results. The example code is here.

@vkorukanti Can you recheck? I found file ParquetBatchReaderSuite exists already

You are right. It already exists.

One more point. When you are moving the Java tests, the current expected result verification code is too large. Instead we can now use spark in tests to verify the expected results. Here is an example of how to do that.
If it helps, move the verifyUsingSparkReader into TestUtils or create a new file ParquetSuiteBase.scala and move there. This can be a separate PR.

@vkorukanti thank you, I think it might be better if we create a new ParquetSuiteBase then move all logic handler, i/o utils... unrelated to the test here, and keep only unit tests in ParquetFileReaderSuite/ParquetFileWriterSuite.
I will create a PR for this task soon.


How to use tab title renaming

Disclaimer: I know very little coding, just enough to take what's out there and make minor changes to hopefully get it to do what I want. I would likely need this explained to me like I'm 5 years old...
I'm trying to use the tab title renaming for an electronic notebook (chemistry). The default names are a bit long so when I have multiple tabs open, it can be difficult to remember which is which.
The current title is something like "SMW-00001-###" where ### represents a three digit notebook page number. The "SMW-00001-" part will remain static in the title, but the ### changes depending on which page number I'm working in. I would like to truncate this title on the tab to something like SW1-### or even just ###. Is it possible for tab modifier to pull the unique ### such that each tab would display SW1-###.
For example, I would like a tab with the title "SMW-00001-661" to show as "SW1-661" and tab with title "SMW-00001-662" to show as "SW1-662"
Is this possible using this extension? If so, what do I put in the Title and Title Matcher fields?
Thanks in advance for any pointers!

Hello @HoorayFerSocks,
Hard to help you without the HTML source code associated on the page.
To assign a custom title, you can extract a portion of a text from the HTML source code and/or a fragment from the URL.
If you need, reopen the issue with more information.
Best


[Question] Lua<->AST

Does Loretta support both ways of conversion from:
Lua->AST
AST->Lua
Thanks for reading.

Yes, it generates an AST from code such as in Program.cs and you can use the LuaReconstructor to generate code from an AST.
But I must warn you, this parser is buggy and won't work all the time.

Update to this issue.
Post-rewrite, the way to convert an AST back into code is calling .ToString(), .ToFullString() or .WriteTo(TextWriter) on the SyntaxNode.


A solution was missing for Data Structures: Use Breadth First Search in a Binary Search Tree

A solution was missing for Data Structures: Use Breadth First Search in a Binary Search Tree.
I included my personal solution

Congrats @emoracle on your first pull request (PR)! :tada:
Thank you for your contribution to the page! :+1:
We're happy to accept these changes, and look forward to future contributions. :memo:


Dual node-template versions (mac, linux)

In order to be able to run a local node, at the moment exists a node-template inside test-util.
During some pair programming with 2 different OS (mac, linux), it was identified that the node-template that was executing on Mac would not run on Linux.
It seems like a good idea, to have 2 different versions of node-template, inside test util, named e.g.:
a) node-template-linux and b)node-template-mac, and create a new task that will detect the OS and run the one needed.

Currently, the repository contains the compiled node-template bin. This is not ideal. Perhaps a better approach is to extend the underlaying configuration, such that a repository URL can be specified.
const process = await substrateProcess({
  repo: "git@github.com:substrate-developer-hub/substrate-node-template.git",
  dev: true,
});

Under the hood, this would clone the repo into a ~/.local/share/capi/cloned and compile and execute it. Perhaps we should allow the user to specify the clone dest as well.
const process = await substrateProcess({
  repo: "git@github.com:substrate-developer-hub/substrate-node-template.git",
  dest: "~/Desktop/tmp",
  dev: true,
});

I did some experimentation in #142. Seems we should support several means of local node instantiation:

Specifying repo (user, repo name, branch, directory into which to clone)
Specifying project (path on disk (to Substrate project root))
Specifying a compiled executable

In the mocked branch, the following clones, compiles and runs a node.
const process = await substrateNode({
  repo: "git@github.com:substrate-developer-hub/substrate-node-template.git",
  cloneDir: "./examples/node-template",
  ensureSynced: false, // we don't care about pulling new commits with each run
  recompile: false, // we don't care about recompiling with each run
});

This works, but it feels like bloat. Doesn't allow for the seamless experience we want:
const node = await test.node();

// connect to & use node here

node.close();

Some Tentative Requirements

Avoid bundling many (or even any) artifacts in Capi (let's eventually remove test-util/node-template entirely –– for now, it gives us development velocity)
Avoid depending on Docker/Nix/virtualization solutions... although it would be quite convenient to simply specify an image and offload the machine-specific considerations

this would clone the repo into a ~/.local/share/capi/cloned and compile and execute it.

I think we should put under consideration the fact that the cloned/compiled repo is needs approx. 4.5 GB of space, plus it can take some considerable time for 1st time compilation. Maybe this is something that user would not like, doing.. We can either add a note that "this is what it is and how its done" in the documentation, or just provide 2 different compiled (node-template) nodes.

Closing this issue as out-of-scope. Capi will eventually lean on Zombienet's programmatic API, pending Deno support #259.


Do drivers need to be installed for the Nano?

hopefully we can test on a windows and a mac computer that don't have Arduino installed


Include tests in pypi sdist tarball

This allows distributions to execute and verify against their python stack.

Why?

As I said above, we check if basically the python modules work when generating packages, otherwise it is just copy A to B and pray it works.
Unittests are pretty good to catch if the module didn't break ie with python update (or any of its dependencies update).


[SPARK-21772] Fix staging parent directory for InsertIntoHiveTable

Summary:
Due to the incorrect tmpLocation in InsertIntoHiveTable is set. SQL queries like create table as select
or insert into would all run in error.
What changes were proposed in this pull request?
Fix the sql staging parent directory for InsertIntoHiveTable
(Please fill in changes proposed in this fix)
How was this patch tested?
manual tests
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Please review http://spark.apache.org/contributing.html before opening a pull request.

Can one of the admins verify this patch?

ok to test

Test build #80852 has started for PR 18985 at commit b293e1c.

Is it possible you can provide a test case?

Test build #80852 has finished for PR 18985 at commit b293e1c.

This patch fails PySpark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80852/
Test FAILed.

You can try this very simple test case:
use test; // change db
create table t1 as select * from t2;

Is you code change based on the latest InsertIntoHiveTable? Can you sync up with master branch?

spark-sql> create database test;
17/08/19 10:29:33 WARN ObjectStore: Failed to get database test, returning NoSuchObjectException
spark-sql> use test;
spark-sql> create table t2(col1 int, col2 int);
17/08/19 10:30:46 WARN HiveMetaStore: Location: file:/Users/xiaoli/IdeaProjects/sparkDelivery/bin/spark-warehouse/test.db/t2 specified for non-external table:t2
spark-sql> insert into t2 values (1, 2);
spark-sql> select * from t2;
1	2
spark-sql> create table t1 as select col1, col2 from t2;
17/08/19 10:31:10 WARN HiveMetaStore: Location: file:/Users/xiaoli/IdeaProjects/sparkDelivery/bin/spark-warehouse/test.db/t1 specified for non-external table:t1
spark-sql> select * from t1;
1	2
spark-sql>

I am still unable to reproduce it. Could you provide us more info?

I am unable to reproduce the issue too.
Moreover, the PR would change also the location for normal SparkSQL application. This sounds strange to me because then this problem should affect normal SparkSQL application too.

Sorry, I think SPARK-18675 has solved this problem.
https://issues.apache.org/jira/browse/SPARK-18675
My environment is hive-0.13, spark2.1.0, There are two reasons caused this problem.
First, this issue is not fixed until Spark-2.1.1
Second, we didn't configure the spark.sql.metastore.version(default is 1.2.1), which caused this problem!

OK. Thanks @liupc.

@liupc If you have no more question about this, can you close this PR? Thank you.


fix linked hash map

Fix an error caused by not adjusting the linked list during shift_back

Pull Request Test Coverage Report for Build 2275
Details

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 90.46%

Files with Coverage Reduction
New Missed Lines
%

builtin/linked_hash_map.mbt
1
84.55%

Totals

Change from base Build 2270:
-0.02%

Covered Lines:
3660

Relevant Lines:
4046

💛  - Coveralls


Add multi-item select to the book-sort interface

As originally requested by @Biepa in #2064

Not sure if this is the right place for this, but thank you.


Align NC instance file to both CGMES 2.4 and CGMES 3.0

CGMES Network Code (NC) instance data will follow the same namespace that will be used for the CIMJSON-LD. However, we need to defined a machine-understandable structure and syntax to explain the mapping between the namespaces. In addition, we would like that the same Network Code instance file should work with CGMES 2.4 (CIM16) and CGMES 3.0 (17).
@prefix rdfs: 	<http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: 	<http://www.w3.org/2002/07/owl#> .
@prefix cim:    <https://cim.ucaiug.io/ns#> .
@prefix cim16:  <http://iec.ch/TC57/2013/CIM-schema-cim16#> .
@prefix cim17:  <http://iec.ch/TC57/CIM100#> .

cim:Equipment owl:equivalentClass cim16:Equipment .
cim16:Equipment owl:equivalentClass cim:Equipment .
cim:Equipment owl:equivalentClass cim17:Equipment .
cim17:Equipment owl:equivalentClass cim:Equipment .

Equivalences like this are not free!

(you don't need equivalentClass in both directions since it's symmetric by definition)
If you declare this, every equipment node will get 3 types. To deal with these types, queries will need to be a lot more complex
You'd also need to declare equivalentProperty for each prop, with further complications for queries
This will multiply x3 the number of triples

I think the more feasible approach is to write SPARQL updates that migrate a database from the older to the newest namespace.
Furthermore, equivalences don't express the idea of migrating namespaces across versions (16->17->18) because:

they are symmetric
mapping individual terms is not the same as mapping whole namespaces. If one of the classes was missed, would it mean the same or different thing?

"There’s No Such Thing as a Free Lunch"
The alternative is that we have everything duplicated three times and use sameAs. In the future we need to implement this by versioning of the vocabulary. Now we have - in the context of Semantic Web three different ontologies. For OOP tool vendors they will have one internal datamodell that they would need to map to three different namespace. In the context of NC they need to use cim:    <https://cim.ucaiug.io/ns#> in the context of CGMES 3.0 cim:  <http://iec.ch/TC57/CIM100#> and in the context CGMES 2.4 cim:  <http://iec.ch/TC57/2013/CIM-schema-cim16#>
We need to find a way to inform the tools - as we want everything to be data/schema driven. We can come up with our own mapping or try to re-use something from Semantic web.
As part of KG we would need to evaluate the best way to execute this. Primarily we are now looking into SHACL validation that can support multiple versions.
Good point that the operation is symmetric:
@prefix rdfs: 	<http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: 	<http://www.w3.org/2002/07/owl#> .
@prefix cim:    <https://cim.ucaiug.io/ns#> .
@prefix cim16:  <http://iec.ch/TC57/2013/CIM-schema-cim16#> .
@prefix cim17:  <http://iec.ch/TC57/CIM100#> .

cim:Equipment owl:equivalentClass cim16:Equipment .
cim:Equipment owl:equivalentClass cim17:Equipment .

This statement does not cover all the requirement in regards to the migrating namespaces across versions (16->17->18). However, this solution will be based on the fact that there will be different version of the same namespace.

Vlado, I was thinking that it is possible to define "mapping" or basically a transformation technique between 2 graphs (e.g. the graphs of the RDFS) by using SPARQL as we can also express mathematical relationship between properties. I attempted to so a small sample which I can try to find.
What do you think for such an idea?
Perhaps this is a bit bigger scope than what is in this issue

In metadata (or the ontologies), we can state

cim:Equipment              dct:replaces cim16:Equipment, cim17:Equipment. # class
cim:Equipment.inService dct:replaces cim17:Equipment.inService. # prop that was added in cim17

From such declarations, we can generate SPARQL Updates to migrate (of course, we can use VALUES lists):

insert {
  graph <new-graph> {
    ?x a cim:Equipment ?y
  }
} where {
  graph <old-graph> {
    ?x a cim17:Equipment
  }
};

insert {
  graph <new-graph> {
    ?x cim:Equipment.inService ?y
  }
} where {
  graph <old-graph> {
    ?x cim17:Equipment.inService ?y
  }
};

We could also do this with GraphDB rules. The benefit is that if you change the value of cim17:Equipment.inService in <old-graph>, it will be automatically propagated to cim:Equipment.inService in <new-graph>


failed to run in docker or remote, report Soleil.woff2 not found

<IP_ADDRESS> - - [24/Jun/2021:09:09:52 +0000] "GET /res/Soleil.woff2 HTTP/1.1" 404 555 "http://localhost:8080/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36" "-"

2021/06/24 09:14:21 [error] 32#32: *4 open() "/usr/share/nginx/html/res/Soleil.woff2" failed (2: No such file or directory), client: <IP_ADDRESS>, server: localhost, request: "GET /res/Soleil.woff2 HTTP/1.1", host: "localhost:8080", referrer: "http://localhost:8080/"

I ran with "docker run -p 8080:8080 cruise/webviz", and got this in the command line, the localhost:8080 only appear a logo flashing forever.
I try to inspect, chrome console shows:
Failed to load resource: the server responded with a status of 404 (Not Found): Soleil.woff2:1
loadWebviz.js:241 Uncaught (in promise) DOMException: A network error occurred.: loadWebviz.js:241

When I open "https://webviz.io/app/", I got the same problem and console feedback.

Problem solved, seem like it's related to some extensions in my Chrome. I start with a clean chrome and everything runs fine.

In the case someone stumbles upon this, is seems to be https://chrome.google.com/webstore/detail/evernote-web-clipper/pioclpoplcdbaefihamjohnefbikjilc


snaketerm reads hotkey config from file

I actually tried that first and used to json library to parse the file but it couldn't handle things like self.clear_text without crashing
2 options:
Could change the file type to json and just leave it the way it is with the instance references in the config file and using eval on the whole file
Or could use load and have the json file contain strings instead ("clear_text") and that gets converted to self.clear_text by the script

New commit takes the second option and processes JSON file for key config


Cannot run Blazor Wasm debugging after closing the previous session

Type: Bug
Issue Description
I am trying to debug a newly created Blazor WebAssembly application. I created the application via dotnet new blazorwasm. The launch.json was generated by the C# extension. When I try to debug the application, it works fine the first time. However, subsequent attempts to run it fail due to port conflicts: "Failed to bind to address http://<IP_ADDRESS>:5293: address already in use."
Steps to Reproduce

Create an empty Blazor WebAssembly application using:dotnet new blazorwasm

Generate launch.json with the C# extension.

My current launch.json:{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch and Debug Standalone Blazor WebAssembly App",
            "type": "blazorwasm",
            "request": "launch",
            "cwd": "${workspaceFolder}"
        }
    ]
}

Run debugging. The browser is opened.
Close the browser and stop debugging.
Try to start debugging again.

Expected Behavior
The application should successfully start debugging again without port conflicts after stopping and restarting the session.
Actual Behavior
The application fails to start debugging after the initial session, reporting that the port is already in use.
Logs
I will attach a zip file.
C# log
2024-12-07 13:17:05.332 [info] Using dotnet configured on PATH
2024-12-07 13:17:05.333 [info] Dotnet path: /usr/local/share/dotnet/dotnet
2024-12-07 13:17:05.333 [info] Activating C# standalone...
2024-12-07 13:17:08.022 [info] [stdout] {"pipeName":"/var/folders/lr/q1frb3cx33b0y4gyw8fs7hn40000gn/T/245b8346.sock"}
2024-12-07 13:17:08.022 [info] received named pipe information from server
2024-12-07 13:17:08.023 [info] client has connected to server
2024-12-07 13:17:08.197 [info] [Info  - 13:17:08] [Program] Language server initialized
2024-12-07 13:17:13.056 [info] [Info  - 13:17:13] [LanguageServerProjectSystem] Successfully completed load of /Users/user/VS Code Test Apps/blazorwasm1/blazorwasm1.csproj
2024-12-07 13:17:13.061 [info] [Info  - 13:17:13] [LanguageServerProjectSystem] Completed (re)load of all projects in 00:00:03.9894763
2024-12-07 13:22:24.766 [info] [LanguageServerHost] [02:22:24.765][End]roslyn/updateLogLevel
2024-12-07 13:23:12.555 [info] [LanguageServerHost] [02:23:12.540][Start]textDocument/didClose
2024-12-07 13:23:12.556 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Home.razor__virtual.cs
2024-12-07 13:23:12.556 [info] [LanguageServerHost] [02:23:12.546][End]textDocument/didClose
2024-12-07 13:23:12.557 [info] [LanguageServerHost] [02:23:12.552][Start]textDocument/didClose
2024-12-07 13:23:12.557 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Counter.razor__virtual.cs
2024-12-07 13:23:12.557 [info] [LanguageServerHost] [02:23:12.554][End]textDocument/didClose
2024-12-07 13:23:12.557 [info] [LanguageServerHost] [02:23:12.554][Start]textDocument/didClose
2024-12-07 13:23:12.558 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Weather.razor__virtual.cs
2024-12-07 13:23:12.558 [info] [LanguageServerHost] [02:23:12.554][End]textDocument/didClose
2024-12-07 13:23:12.558 [info] [LanguageServerHost] [02:23:12.554][Start]textDocument/didClose
2024-12-07 13:23:12.558 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/_Imports.razor__virtual.cs
2024-12-07 13:23:12.558 [info] [LanguageServerHost] [02:23:12.555][End]textDocument/didClose
2024-12-07 13:23:12.558 [info] [LanguageServerHost] [02:23:12.555][Start]textDocument/didClose
2024-12-07 13:23:12.558 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/MainLayout.razor__virtual.cs
2024-12-07 13:23:12.558 [info] [LanguageServerHost] [02:23:12.555][End]textDocument/didClose
2024-12-07 13:23:12.559 [info] [LanguageServerHost] [02:23:12.555][Start]textDocument/didClose
2024-12-07 13:23:12.559 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/NavMenu.razor__virtual.cs
2024-12-07 13:23:12.559 [info] [LanguageServerHost] [02:23:12.555][End]textDocument/didClose
2024-12-07 13:23:12.559 [info] [LanguageServerHost] [02:23:12.555][Start]textDocument/didClose
2024-12-07 13:23:12.559 [info] [LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/App.razor__virtual.cs
2024-12-07 13:23:12.560 [info] [LanguageServerHost] [02:23:12.555][End]textDocument/didClose
2024-12-07 13:23:12.641 [info] [LanguageServerHost] Closing workspace/diagnostics request for HotReloadDiagnostics
2024-12-07 13:23:12.642 [info] [LanguageServerHost] Closing workspace/diagnostics request for WorkspaceDocumentsAndProject
2024-12-07 13:23:12.642 [info] [LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics
2024-12-07 13:23:12.642 [info] [LanguageServerHost] Closing workspace/diagnostics request for enc
2024-12-07 13:23:12.642 [info] [LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics
2024-12-07 13:23:12.643 [info] [LanguageServerHost] [02:23:12.641][End]workspace/diagnostic
2024-12-07 13:23:12.643 [info] [LanguageServerHost] [02:23:12.641][End]workspace/diagnostic
2024-12-07 13:23:12.643 [info] [LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics
2024-12-07 13:23:12.643 [info] [LanguageServerHost] [02:23:12.641][End]workspace/diagnostic
2024-12-07 13:23:13.065 [info] [RazorWorkspaceListener] Serializing information for (ProjectId, #a9bb344c-6f7c-4c67-a4a5-305afe68c4e5 - /Users/user/VS Code Test Apps/blazorwasm1/blazorwasm1.csproj ($net9.0))
2024-12-07 13:23:14.709 [info] [LanguageServerHost] Request did not contain a textDocument, using default language handler
2024-12-07 13:23:14.710 [info] [LanguageServerHost] Request did not contain a textDocument, using default language handler
2024-12-07 13:23:14.710 [info] [LanguageServerHost] Request did not contain a textDocument, using default language handler
2024-12-07 13:23:14.710 [info] [LanguageServerHost] [02:23:14.708][Start]workspace/diagnostic
2024-12-07 13:23:14.710 [info] [LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: WorkspaceDocumentsAndProject) started getting diagnostics
2024-12-07 13:23:14.710 [info] [LanguageServerHost] previousResults.Length=0
2024-12-07 13:23:14.711 [info] [LanguageServerHost] Processing 0 documents
2024-12-07 13:23:14.711 [info] [LanguageServerHost] [02:23:14.708][Start]workspace/diagnostic
2024-12-07 13:23:14.711 [info] [LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: HotReloadDiagnostics) started getting diagnostics
2024-12-07 13:23:14.711 [info] [LanguageServerHost] previousResults.Length=0
2024-12-07 13:23:14.711 [info] [LanguageServerHost] Processing 0 documents
2024-12-07 13:23:14.711 [info] [LanguageServerHost] [02:23:14.709][Start]workspace/diagnostic
2024-12-07 13:23:14.712 [info] [LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: enc) started getting diagnostics
2024-12-07 13:23:14.712 [info] [LanguageServerHost] previousResults.Length=0
2024-12-07 13:23:14.712 [info] [LanguageServerHost] Processing 0 documents
2024-12-07 13:28:42.150 [info] Using dotnet configured on PATH
2024-12-07 13:32:16.780 [info] [LanguageServerHost] No request parameters given, using default language handler
2024-12-07 13:32:16.783 [info] [LanguageServerHost] [02:32:16.780][Start]workspace/buildOnlyDiagnosticIds
2024-12-07 13:32:16.784 [info] [LanguageServerHost] [02:32:16.783][End]workspace/buildOnlyDiagnosticIds
C# LSP Trace Logs
[Trace - 13:22:24] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:22:24.765][End]roslyn/updateLogLevel"
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Home.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Counter.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Weather.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/_Imports.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/MainLayout.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/NavMenu.razor__virtual.cs"
}
}
[Trace - 13:23:12] Sending notification 'textDocument/didClose'.
Params: {
"textDocument": {
"uri": "virtualCSharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/App.razor__virtual.cs"
}
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.540][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Home.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.546][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.552][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Counter.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.554][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.554][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Pages/Weather.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.554][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.554][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/_Imports.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/MainLayout.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/Layout/NavMenu.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][Start]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] didClose for virtualcsharp-razor:///Users/user/VS Code Test Apps/blazorwasm1/App.razor__virtual.cs"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.555][End]textDocument/didClose"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Closing workspace/diagnostics request for HotReloadDiagnostics"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Closing workspace/diagnostics request for WorkspaceDocumentsAndProject"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Closing workspace/diagnostics request for enc"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics"
}
[Trace - 13:23:12] Received response 'workspace/diagnostic - (85)' in 176130ms.
Result: {
"items": []
}
[Trace - 13:23:12] Received response 'workspace/diagnostic - (86)' in 176130ms.
Result: {
"items": []
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.641][End]workspace/diagnostic"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.641][End]workspace/diagnostic"
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Microsoft.CodeAnalysis.LanguageServer.Handler.Diagnostics.Public.PublicWorkspacePullDiagnosticsHandler finished getting diagnostics"
}
[Trace - 13:23:12] Received response 'workspace/diagnostic - (84)' in 176131ms.
Result: {
"items": []
}
[Trace - 13:23:12] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:12.641][End]workspace/diagnostic"
}
[Trace - 13:23:13] Received notification 'window/logMessage'.
Params: {
"type": 4,
"message": "[RazorWorkspaceListener] Serializing information for (ProjectId, #a9bb344c-6f7c-4c67-a4a5-305afe68c4e5 - /Users/user/VS Code Test Apps/blazorwasm1/blazorwasm1.csproj ($net9.0))"
}
[Trace - 13:23:14] Sending request 'workspace/diagnostic - (89)'.
Params: {
"identifier": "enc",
"previousResultIds": [],
"partialResultToken": "255ba741-649a-4b81-9d3b-714dbca8a66a"
}
[Trace - 13:23:14] Sending request 'workspace/diagnostic - (90)'.
Params: {
"identifier": "HotReloadDiagnostics",
"previousResultIds": [],
"partialResultToken": "6aac1bba-2162-445b-b8d4-ca6d66565daf"
}
[Trace - 13:23:14] Sending request 'workspace/diagnostic - (91)'.
Params: {
"identifier": "WorkspaceDocumentsAndProject",
"previousResultIds": [],
"partialResultToken": "8527e187-a498-429e-b7a9-546ea7a90544"
}
[Trace - 13:23:14] Received request 'workspace/codeLens/refresh - (37)'.
Params: []
[Trace - 13:23:14] Sending response 'workspace/codeLens/refresh - (37)'. Processing request took 0ms
No result returned.
[Trace - 13:23:14] Received request 'workspace/diagnostic/refresh - (38)'.
Params: []
[Trace - 13:23:14] Sending response 'workspace/diagnostic/refresh - (38)'. Processing request took 0ms
No result returned.
[Trace - 13:23:14] Received request 'workspace/semanticTokens/refresh - (39)'.
Params: []
[Trace - 13:23:14] Sending response 'workspace/semanticTokens/refresh - (39)'. Processing request took 1ms
No result returned.
[Trace - 13:23:14] Received request 'workspace/inlayHint/refresh - (40)'.
Params: []
[Trace - 13:23:14] Sending response 'workspace/inlayHint/refresh - (40)'. Processing request took 0ms
No result returned.
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Request did not contain a textDocument, using default language handler"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Request did not contain a textDocument, using default language handler"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Request did not contain a textDocument, using default language handler"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:14.708][Start]workspace/diagnostic"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: WorkspaceDocumentsAndProject) started getting diagnostics"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] previousResults.Length=0"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Processing 0 documents"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:14.708][Start]workspace/diagnostic"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: HotReloadDiagnostics) started getting diagnostics"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] previousResults.Length=0"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Processing 0 documents"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:23:14.709][Start]workspace/diagnostic"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] PublicWorkspacePullDiagnosticsHandler(category: enc) started getting diagnostics"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] previousResults.Length=0"
}
[Trace - 13:23:14] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] Processing 0 documents"
}
[Trace - 13:32:16] Sending request 'workspace/buildOnlyDiagnosticIds - (92)'.
[Trace - 13:32:16] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] No request parameters given, using default language handler"
}
[Trace - 13:32:16] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:32:16.780][Start]workspace/buildOnlyDiagnosticIds"
}
[Trace - 13:32:16] Received response 'workspace/buildOnlyDiagnosticIds - (92)' in 5ms.
Result: {
"ids": [
"CS1607",
"CS0169",
"CS0414",
"CS0067",
"CS0649",
"CS0656",
"CS0518",
"CS5001",
"CS0028",
"CS0017",
"CS7022",
"CS1556",
"CS0402",
"CS1558",
"CS1555",
"CS8892",
"CS0148",
"CS8078",
"CS7038",
"CS0204",
"CS0570",
"CS8004",
"CS8006",
"CS8005",
"CS8008",
"CS4007",
"CS8178",
"CS4013",
"CS1969",
"CS9026",
"CS9068",
"CS9144",
"CS9148",
"CS9149",
"CS9153",
"CS9154",
"CS9155",
"CS9156",
"CS9158",
"CS9159",
"CS9160",
"CS9163",
"CS9177",
"CS9178",
"CS9207",
"CS8419",
"CS8420",
"CS9217",
"CA1016",
"CA1014",
"CA1017",
"CA1017",
"CA1724",
"CA1724",
"CA1501",
"CA1502",
"CA1505",
"CA1506",
"CA1509",
"CA1852",
"CA5360",
"CA5399",
"CA5400",
"CA5380",
"CA5381",
"CA5367",
"CA5401",
"CA5402",
"CA2301",
"CA2302",
"CA2321",
"CA2322",
"CA2329",
"CA2330",
"CA2311",
"CA2312",
"CA2327",
"CA2328",
"CA5387",
"CA5388",
"CA5362",
"CA5396",
"CA5391",
"CA5395",
"CA5382",
"CA5383",
"CA1812"
]
}
[Trace - 13:32:16] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:32:16.783][End]workspace/buildOnlyDiagnosticIds"
}
[Trace - 13:32:56] Sending request 'workspace/buildOnlyDiagnosticIds - (93)'.
[Trace - 13:32:56] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] No request parameters given, using default language handler"
}
[Trace - 13:32:56] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:32:56.616][Start]workspace/buildOnlyDiagnosticIds"
}
[Trace - 13:32:56] Received response 'workspace/buildOnlyDiagnosticIds - (93)' in 31ms.
Result: {
"ids": [
"CS1607",
"CS0169",
"CS0414",
"CS0067",
"CS0649",
"CS0656",
"CS0518",
"CS5001",
"CS0028",
"CS0017",
"CS7022",
"CS1556",
"CS0402",
"CS1558",
"CS1555",
"CS8892",
"CS0148",
"CS8078",
"CS7038",
"CS0204",
"CS0570",
"CS8004",
"CS8006",
"CS8005",
"CS8008",
"CS4007",
"CS8178",
"CS4013",
"CS1969",
"CS9026",
"CS9068",
"CS9144",
"CS9148",
"CS9149",
"CS9153",
"CS9154",
"CS9155",
"CS9156",
"CS9158",
"CS9159",
"CS9160",
"CS9163",
"CS9177",
"CS9178",
"CS9207",
"CS8419",
"CS8420",
"CS9217",
"CA1016",
"CA1014",
"CA1017",
"CA1017",
"CA1724",
"CA1724",
"CA1501",
"CA1502",
"CA1505",
"CA1506",
"CA1509",
"CA1852",
"CA5360",
"CA5399",
"CA5400",
"CA5380",
"CA5381",
"CA5367",
"CA5401",
"CA5402",
"CA2301",
"CA2302",
"CA2321",
"CA2322",
"CA2329",
"CA2330",
"CA2311",
"CA2312",
"CA2327",
"CA2328",
"CA5387",
"CA5388",
"CA5362",
"CA5396",
"CA5391",
"CA5395",
"CA5382",
"CA5383",
"CA1812"
]
}
[Trace - 13:32:56] Received notification 'window/logMessage'.
Params: {
"type": 5,
"message": "[LanguageServerHost] [02:32:56.617][End]workspace/buildOnlyDiagnosticIds"
}
Environment information
VSCode version: 1.95.3
C# Extension: 2.55.29
Using OmniSharp: false
Dotnet Information
.NET SDK:
 Version:           9.0.101
 Commit:            eedb237549
 Workload version:  9.0.100-manifests.4a280210
 MSBuild version:   17.12.12+1cce77968
Runtime Environment:
OS Name:     Mac OS X
OS Version:  12.7
OS Platform: Darwin
RID:         osx-x64
Base Path:   /usr/local/share/dotnet/sdk/9.0.101/
.NET workloads installed:
[wasm-tools]
Installation Source: SDK 9.0.100
Manifest Version:    9.0.0/9.0.100
Manifest Path:       /usr/local/share/dotnet/sdk-manifests/9.0.100/microsoft.net.workload.mono.toolchain.current/9.0.0/WorkloadManifest.json
Install Type:        FileBased
Configured to use loose manifests when installing new manifests.


gopass init fails to initialize git repo.

Initialized empty Git repository in /home/james/.password-store/.git/

*** Please tell me who you are.

Run

  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: empty ident name (for<EMAIL_ADDRESS>not allowed
Failed to init git: exit status 128

maybe check git config first and ask what information is wanted for those fields? I like to initialize my repository information differently depending on the project so I don't set the global.

This should have been fixed by #68


ui-timepicker-div height too small

I'm having a problem on Chrome 13, iOS 5 and IE8 (but not in IE8 compatibility mode) where the height of the timepicker div is too small, i.e. the last slider is printed outside of the back platter.
For the time being I'm manually setting a fixed height of .ui-timepicker-div to compensate for this but this shouldn't be necessary.

This kind-of works. The backplatter is large enough for holding all the content, however it gets too big as it makes room for the slider for seconds (which I don't use).


Recognition Train/Test Model

When i try training for many times，loss value is different，is there problem with my video dataset？Notice:model is ST_GCN_18 and same lr，batchsize.

Maybe this answer can help you:
https://github.com/open-mmlab/mmskeleton/issues/303#issuecomment-620330849


mod_unique_id cause Apache to fail restart on first coverge

Hello,
I've encountered a problem after introducing unique_id where Apache fails to restart.
The work around at this moment is a killall httpd and re run chef-client
This can be reproduced in test-kitchen by just including two recipes:

name: upstream_apache
run_list:
- "recipe[apache2]"
- "recipe[apache2::mod_unique_id]"

The behavior seen is that httpd is stopped but only the master process is killed. There are a bunch of httpd orphans still sitting there listening on 80 and 443
When Apache tries to start it fails as ports are already in use.
Every now and then it will succeed which suggests to me this maybe a timing issue and that httpd start is happening before the stop has completed.
Error:
           Error executing action `restart` on resource 'service[apache2]'

       ================================================================================

           Mixlib::ShellOut::ShellCommandFailed
           ------------------------------------
           Expected process to exit with [0], but received '1'
           ---- Begin output of /sbin/service httpd restart ----
           STDOUT: Stopping httpd: [  OK  ]
           Starting httpd: [FAILED]
           STDERR: [Thu Oct 09 11:56:26 2014] [warn] NameVirtualHost *:80 has no VirtualHosts
           (98)Address already in use: make_sock: could not bind to address [::]:80
           (98)Address already in use: make_sock: could not bind to address <IP_ADDRESS>:80

       no listening sockets available, shutting down
           Unable to open logs
           ---- End output of /sbin/service httpd restart ----
           Ran /sbin/service httpd restart returned 1

       Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/apache2/recipes/default.rb

            24: service 'apache2' do
            25:   service_name node['apache']['package']
            26:   case node['platform_family']
            27:   when 'rhel'
            28:     reload_command '/sbin/service httpd graceful'
            29:   when 'debian'
            30:     provider Chef::Provider::Service::Debian
            31:   when 'arch'
            32:     service_name 'httpd'
            33:   end
            34:   supports [:start, :restart, :reload, :status]

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/apache2/recipes/default.rb:24:in `from_file'

           service("apache2") do

         action [:enable, :start]
             updated true
             supports {:restart=>true, :reload=>true, :status=>true, :start=>true}
             retries 0
             retry_delay 2
             guard_interpreter :default
             service_name "httpd"
             enabled true
             running true
             pattern "apache2"
             reload_command "/sbin/service httpd graceful"
             cookbook_name "apache2"
             recipe_name "default"
             only_if "/usr/sbin/httpd -t"
           end

This seems to be an issue with the 2.2 init scripts. We did remove a && sleep 1 from service resource in the cookbook (https://github.com/svanzoest-cookbooks/apache2/commit/f0fc1ce490a5fccb10915c1e5088a4caaa352db5)  seems like this showed up when we removed it?
We clearly do not need it on the newer platforms, but it seems like mod_security and mod_unique_id cause things to take longer in a way that the init scripts do not handle gracefully. When tried to look back to see what was the reasoning for the sleeps to get added, but there was nothing in the commits that indicated a reason. I guess we found two. ;-)

I believe this should fix it - it seems like this is only being experienced on rhel systems.

I'm still seeing this exact issue on Apache 2.2/Centos 6.5, using the latest 3.1.0 version of this cookbook.  Does it take a really long time or cause some sort of error?

I am having this issue using latest version of this cookbook as well. When I adjust the restart/reload lines to be as follows, all is well:
service 'apache2' do
  service_name node['apache']['service_name']
  case node['platform_family']
  when 'rhel'
    restart_command '/sbin/service httpd restart && sleep 1'
    reload_command '/sbin/service httpd graceful && sleep 1'
  when 'debian'
    provider Chef::Provider::Service::Debian
  when 'arch'
    service_name 'httpd'
  end
  supports [:start, :restart, :reload, :status]
  action [:enable, :start]
  only_if "#{node['apache']['binary']} -t", :environment => {           'APACHE_LOG_DIR' => node['apache']['log_dir'] }, :timeout => 10
end

Just like to add this is still happening with 3.1.0 version of this cookbook for me


iOS build fails to run in with Xcode 11.0 beta

React Native version:

Steps To Reproduce
1.Create a new react-native project with react-native init ""
2.open iOS project and run
Describe what you expected to happen:
Build and run successfully and show launch screen with default UI
What is happening:
Build shows Error Screen saying -
"Unknown argument type 'attribute' in method -[RCTAppState getCurrentappState:error:].
Extend RCTConvert to support this type
Snack, code example, or link to a repository:
Happens with all my existing projects and newly created samples as well.Here is the sample code I have tried.
FinalTry.zip
Please refer to below screenshot for error data

NOTE:
Happens only in newly launched MacOS and Xcode 11 beta

OMG, seems Xcode 11 beta breaks method signature parsing. Now I have no chance to install Xcode beta. @vivekhumnabad Would you mind paste the method selector string for us? just add the NSLog like below.

fixed by #25146

@ericlewis  Any idea when this will be released???

@vivekhumnabad needs to be accepted and merged, which shouldn't take long, and after maybe @grabbou wouldn't mind pulling it in to the 0.60 RC, since it is a pretty minor change? :D

@vivekhumnabad its been merged, this will land hopefully in 0.60 or 0.61!

@vivekhumnabad its been merged, this will land hopefully in 0.60 or 0.61!

Hey Eric, do you know if this fix ended up in 0.60?

Would it be possible to get a fix in version precceding 0.60? Say 59?
(0.60 completely breaks a lot of third party packages that are no longer supported)

@ollydixon This fix is already part of the 59.9 react-native.

I am still facing this issue on

react natvie :0.59.3

@MuhammadUsman786786
According to Betko's post, it is included in 0.59.9, you are using 0.59.3. You will need to upgrade to see the fix.

Does it affect on users upgraded to ios13 with apps that is currently in store?

@Desintegrator Users who are on iOS13 can download and run React Native 0.59.<9 apps from the play store, as long as they are built with Xcode 10. The issue is when building apps with Xcode 11 (which is required to run locally on iOS 13 devices).

OMG, dường như Xcode 11 beta phá vỡ phân tích chữ ký phương thức. Bây giờ tôi không có cơ hội để cài đặt Xcode beta. @vivekhumnabad Bạn có phiền dán chuỗi chọn phương thức cho chúng tôi không? chỉ cần thêm NSLognhư dưới đây.

not work for me

fixed by #25146

https://github.com/facebook/react-native/pull/25146/files that work in my case, react-native 0.59.8

react-native 0.52.3
fix xcode 11 beta
code ./node_modules/react-native/React/Base/RCTModuleMethod.mm
Replace
return RCTReadString(input, "__unused") ||
RCTReadString(input, "attribute((unused))");
To
return RCTReadString(input, "attribute((unused))") ||
RCTReadString(input, "attribute((unused))") ||
RCTReadString(input, "__unused");

fixed by #25146

https://github.com/facebook/react-native/pull/25146/files that work in my case, react-native 0.59.8

it works for me. do reinstall the app after replace

@Desintegrator Users who are on iOS13 can download and run React Native 0.59.<9 apps from the play store, as long as they are built with Xcode 10. The issue is when building apps with Xcode 11 (which is required to run locally on iOS 13 devices).

What about app from the store that is currently run React Native 0.55.0?

Thanks, @CaopanHuster for confirming about 0.59.8. Is this change available on RN 0.59.8? I can't upgrade my RN version further 0.59.8.

@NguyenVanVietPoLy "RCTReadString(input, "attribute((unused))")" adding this worked for me on 0.57.4

react native 0.59.9 solved this problem.
but if you want to keep 0.59.0~0.59.8
find the file here: node_modules/react-native/React/base/RCTModuleMethod.mm
at line 93 add:
static BOOL RCTParseUnused(const char **input) {   return RCTReadString(input, "__unused") ||          RCTReadString(input, "__attribute__((__unused__))") || //solve by add this line          RCTReadString(input, "__attribute__((unused))"); }

This issue still exists in xcode 11.1 and rn 0.59.9. Do I have to update to 0.6**?Thanks.

Yes, upgrade to the latest version of react-native.

fixed by https://github.com/facebook/react-native/pull/25146/files#diff-263fc157dfce55895cdc16495b55d190

it works for me.
but if you want to keep a stable version
update here: node_modules/react-native/React/base/RCTModuleMethod.m
then patch-package,patch-package lets app authors instantly make and keep fixes to npm dependencies.

if ([@(input) hasPrefix:@"getCurrentAppState"]){
NSLog(@"@", @(input))
}

react native 0.59.9 solved this problem.
but if you want to keep 0.59.0~0.59.8
find the file here: node_modules/react-native/React/base/RCTModuleMethod.mm
at line 93 add:
static BOOL RCTParseUnused(const char **input) { return RCTReadString(input, "__unused") || RCTReadString(input, "__attribute__((__unused__))") || //solve by add this line RCTReadString(input, "__attribute__((unused))"); }

Worked for me


Error while running jug execute prime.py

I tried the default example given in the documents. I get the following error. Can you please help me
Traceback (most recent call last):
  File "/storage/work/dua143/anaconda2/bin/jug", line 11, in <module>
    sys.exit(main())
  File "/storage/work/dua143/anaconda2/lib/python2.7/site-packages/jug/jug.py", line 278, in main
    cmdapi.run(options.subcommand, options=options, store=store, jugspace=jugspace)
  File "/storage/work/dua143/anaconda2/lib/python2.7/site-packages/jug/subcommands/__init__.py", line 271, in run
    return cmd(*args, **kwargs)
  File "/storage/work/dua143/anaconda2/lib/python2.7/site-packages/jug/subcommands/__init__.py", line 161, in __call__
    return self.run(*args, **kwargs)
  File "/storage/work/dua143/anaconda2/lib/python2.7/site-packages/jug/subcommands/execute.py", line 86, in run
    store, jugspace = init(options.jugfile, options.jugdir, store=store)
  File "/storage/work/dua143/anaconda2/lib/python2.7/site-packages/jug/jug.py", line 97, in init
    jugfile_contents = open(jugfile).read()
IOError: [Errno 2] No such file or directory: 'primes.py'

According to the error message, primes.py was not found, while the example expects that you have saved the code to a file called primes.py
You can download it here: https://github.com/luispedro/jug/tree/master/examples/primes


IndexError when masking empty jaggedArray made from offsets

I'm trying to apply a mask onto my JaggedArray. Unfortunately, in the corner case where the JaggedArray is empty, I can an IndexError.
a = awkward.JaggedArray.fromoffsets([1, 1], [1, 1])
mask = a > 10
a[mask]

In case of arrays created by fromcounts, this seems to work.

Awkward 1 is so close to being ready that my recommendation is to use the work-around. (Leave this issue open so that anyone else who runs into this can find it.)
Thanks for reporting it, though!


docs: [vision-on-sample-app][8/n] SDK Installation view

Stack from ghstack (oldest at bottom):

#617
#613
#612
-> #611
#610
#609
#608
#606
#605
#604

Context
This is a PR in a series of PRs to build sample app that runs Identify and Track in VisionPro
The app is built to be an interactive walk through guidance for developers who are integrating Customer.io Swift SDK in their VisioPro apps.
For more context:

See the project one pager
See Linear Issue

PR Summary
This PR introduces a very brief SDK installation tutorial screen. It is intentially very brief as assume the developer knows how to use Swift Package Manager or Cocoapods if their app uses any of them already.
Beside the regular code review, I would really appreciate any suggestion to improve the visual content.
Test plan
Beside testing the newly added screenand it associated behavior, since this is the first change in the app where we have multiple screen, I will also add a test to ensure the app remembers the last opened screen.
New user experience
This scenario validates that:
1- Top left menu "opened" status is updated when we visit the SDK Installation screen correctly.
2- Taping/chosing the "installing CustomerIO SDK" direct to the correct screen
3- Tapping/chosing the "SDK Installtion" menu entry navigates to the correct screen
Pre condition:
Make sure the app is not installed on the device or simulator to run through the new user experience.
Test steps

Open VisionOs.xcproject
Hit CMD+R to run the project and make sure you have VisionOS simulator installed and selected
Expected behavior:

The app opens on the App Intro View.
Top left menu shows no checkmark beside the "SDK Installation" entry because we never opened it before.
Tapping/chosing the "installing CustomerIO SDK" should open the SDK Installation View
Now the top left button should show the checkmark beside the "SDK Installation"

https://github.com/customerio/customerio-ios/assets/142905621/c4faca1a-7c4a-4550-8bb6-0dc478c948f9
Existing user experience
This scenario validates that the app opens on the last visited screen and the menu state is persisted cross app runs.
https://github.com/customerio/customerio-ios/assets/142905621/ca9670d4-ee28-4277-8611-6ef31aff666b

Apologies for that, gh-stack pushes seems to cause too much noise due to the fact that it pushes the entire stack for every push. These changes will carry on #624


Added nuke/cleanup script

Added a nuke cleanup script to the workshop.
Signed-off-by: JJ Asghar<EMAIL_ADDRESS>

Could we just delete what we installed on the k8s cluster?
Also, could we add instructions on clean up the the user's machine?  That is what users care most.  I think this is just clean up the ibmcloud CLI and the kube config file.
Thanks for jumping on working on this JJ!

Oh! yeah that makes so much sense.
I'll take a stab at it here and report back :)

The updates I've made also are taken from here: https://github.com/IBM-Bluemix-Docs/cli/pull/75


Add possibility to ignore time spent while AFK.

Ignore AFK players. Maybe a way to define how long a player is afk, and/or hooks into other afk detection plugins.

It should also be possible to see the time spent while AFK, instead of discarding (not counting).


auto-assign hardware with scoped user not assigned

Scenario/Intent
Hi,
We are using the autoassign feature of the Server Profile but the SP is not assigned when we execute the playbook with the scoped user.
It seems to related to the following issue: https://github.com/HewlettPackard/oneview-ansible/issues/469
This scoped used has administrator access to the following resources:

/rest/enclosures/..
/rest/sas-interconnects/...
/rest/drive-enclosures/...
/rest/logical-interconnect-groups/...
/rest/sas-logical-interconnect-groups/...
/rest/sas-logical-interconnects/...
/rest/logical-interconnects/...
/rest/sas-interconnects/....
/rest/sas-logical-interconnect-groups/...
/rest/sas-logical-interconnects/...
/rest/drive-enclosures/...
/rest/server-hardware/...

When we create the SP from ServerProfileTemplate, the ServerProfile is created but it is not automatically assigned to a server hardware.
Note: It is working when we execute the playbook as an administrator (not scoped) who has access to all resrouces into OneView.
Environment Details

OneView Ansible Docker Image: v6.1.0-OV6.1
OneView Appliance Version: 4.40

Steps to Reproduce
Below a small example:
---
- hosts: localhost
  vars:
    # Python
    ansible_python_interpreter: '/usr/local/bin/python3.6'
    config: 'oneview-.json'
    ooneviewsptName: "spt-480g10"
    ooneviewspName: "test-assign-sp"

  tasks:

  - name: "Create SP from SPT"
    oneview_server_profile:
      config: "{{ config }}"
      state: present
      data:
        name: "{{ ooneviewspName }}"
        serverProfileTemplateName: "{{ ooneviewsptName }}"
      params:
        force: true
```

### Expected Result

The Server Profile is created but It is not assigned to a hardware server.

### Actual Result

Not working as expected.

I thank you for your help,

Best Regards,
NIcolas

Hi @bigmagic , we have analyzed the issue and found the issue could be reproduced when the initialScopeUris is not passed in the playbook as mentioned in the server profile examples.
Could you please try with the below playbook. Meanwhile we will be looking into the issue.
---
- hosts: localhost
  vars:
    # Python
    ansible_python_interpreter: '/usr/local/bin/python3.6'
    config: 'oneview-.json'
    ooneviewsptName: "spt-480g10"
    ooneviewspName: "test-assign-sp"
    scope_uris: "<scope_uri>"

tasks:

name: "Create SP from SPT"
oneview_server_profile:
config: "{{ config }}"
state: present
data:
name: "{{ ooneviewspName }}"
serverProfileTemplateName: "{{ ooneviewsptName }}"
initialScopeUris:
- {{ scope_uri }}
params:
force: true

Hi @VenkateshRavula
I thank you for the reply and we will try.
what should be value of initialScopeUris exactly ? The value of addedResourceUris of the scoped user ?
I thank you for the confirmation,
Best Regards,
Nicolas

Hi @VenkateshRavula
I confirm It is working with initialScopeUris.
Thanks,
Best Regards,
Nicolas


feat: artist past shows improvements

The type of this PR is: Enhancement
Description
This is a kind of hybrid PR. It does three small things, two of which are kind of proposals or PoCs of UX tweaks that I think we could potentially roll out everywhere.
The three small things:

Add a skeleton loading screen to Past Shows
Add a sticky scroll header to Past Shows
Add an effect that I'm going to call "springy overscroll" to Past Shows

Note that I also removed Pull to Refresh, since I don't think it makes sense in this screen.
I'm totally happy to revert (2) and/or (3), depending on what people think. I'd be interested in hearing from @samchieng and @joanna20, and maybe having a brief discussion about using these tweaks in other places.
The Skeleton:

The sticky scroll header and springy overscroll:
https://user-images.githubusercontent.com/1815204/104301621-296af580-54c8-11eb-868e-e429431f19d6.mov
I'll update the changelog once we decide which parts to keep.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a CHANGELOG.yml entry or my changes do not require one.

Oh wow I love all these 3 small things! Curious: how easy is it to roll out these same UX improvements on more pages? We have #1 on a lot of screens and its started to become a standard pattern for us, but i've been hoping to roll out #2 as a standard pattern across the app as well. #3 also feels like a better iteration on pull to refresh in this context.
Small design note for the sticky header is that we'll want to change the text to use the medium weight instead of regular!

Oh wow I love all these 3 small things! Curious: how easy is it to roll out these same UX improvements on more pages? We have #1 on a lot of screens and its started to become a standard pattern for us, but i've been hoping to roll out #2 as a standard pattern across the app as well. #3 also feels like a better iteration on pull to refresh in this context.
Small design note for the sticky header is that we'll want to change the text to use the medium weight instead of regular!

+1 love these improvements!

+1 love these improvements!

Thanks Adam, this really looks great. We definitely need to be using these UX adjustments everywhere.

Thanks Adam, this really looks great. We definitely need to be using these UX adjustments everywhere.

Hi Adam, I have one minor comment that I missed the last time, It looks like the back button is slightly hiding the screen title on small devices (I am using an iPhone 8)

Hi Adam, I have one minor comment that I missed the last time, It looks like the back button is slightly hiding the screen title on small devices (I am using an iPhone 8)

Thanks Adam 🎉

Thanks Adam 🎉


Functions for getting string array attributes

adds get_strattrarray and get_strattrarray!

@iaravena, could you add tests for these in test/test_grb_attrs.jl?

It's already working in my machines (tried on Win7, Win10 and MacOS). Is there anywhere else where could I try it? (as far as I know, JuliaBox would not do because of Gurobi license)

That's great, but adding a unit test to the package is your insurance that someone (or a gurobi release) won't unintentionally break this code in the future.

Added (test_get_strarray.jl and test_get_strarray.mps), should I  create an independent pull request?

@iaravena, it's better to add to this PR if you can. Just push a new commit to this branch.

The new test file should be added to the list in runtests.jl so that it gets run with Pkg.test("Gurobi").

Confirmed tests passing locally, thanks!

Perfect! thanks for your patience :)


can't toggle between structures

Hi, this is maybe more of a question than an issue, but I'm not sure how to resolve this.
Basically, my use case is this: I would like to toggle between the known structure of a protein (which exists as a PDB file), and a predicted structure (another PDB file).
I want to allow the user to select which version of the structure to view in the same component (as there may be many predictions, and I don't want to have too many structure viewers on the page).
What I have tried is something similar to the following:
export default function StructureViewer(props) {

  const [selectedStructure, setSelectedStructure] = useState('');
  const [path, setPath] = useState(null);
  const structureBlobs = {'known': new Blob(), 'predicted': new Blob()}; // in the actual code these are real blobs
  const availableStructures = ['known', 'predicted'];

  useEffect(() => {
    setPath(structureBlobs[selectedStructure]);
  }, [selectedStructure])

  const handleStructureInputChange = (event) => {
    setSelectedStructure(event.target.value);
  }

...

  return (
      <AutoSizer disableHeight>
          <Stage
            height={'300px'}
            width={width}
            params={{
              backgroundColor: '#f5f5f5',
              quality: 'low',
              ...stageParams,
            }}
            cameraState={{}}
          >
            <Component
              path={path}
              reprList={reprList}
              transform={viewerControls}
              loadFileParams={loadFileParams}
            />
          </Stage>
      </AutoSizer>

      Select which structure to view:

      <select name='structure' onChange={handleStructureInputChange}>
        {
          availableStructures.map( (structureName) =>
            <option
              key={structureName.toLowerCase()}
              value={structureName.toLowerCase()}
            >
              {structureName}
            </option>
          )
        }
      </select>
  )
}

This works just fine for viewing the structure at first, but when I select a new structure and change the value of structureName (which changes path), instead of clearing the previous structure and displaying the new one, it superimposes them!
This may be an interesting feature in the future, but for now it's not the desired behavior. Looking at the Component class, it looks like when path updates, it should trigger a re-render here:
  useAsyncEffect(
    function* loadFile(setCancelHandler, c) {
      const abortController = new AbortController();
      setCancelHandler(() => abortController.abort());
      let nextComponent: NGL.Component | undefined;
      try {
        nextComponent = (yield* c(stage.loadFile(path, loadFileParams))) as
          | NGL.Component
          | undefined;
      } catch (error) {
        if (onLoadFailure) {
          onLoadFailure(error);
        }
      }
      if (nextComponent) {
        setComponent(nextComponent);
      }
    },
    [loadFileParams, onLoadFailure, path, stage]
  );

does setComponent(nextComponent) not clear the current component? or is there an easy workaround?
would love any help, and thank you in advance!

Thank you for reporting an issue!
I think I forgot to add a cleanup function to remove an old component from the stage.
I'll add a cleanup function. 4cc4498

amazing, thank you!


Timeout downloading weak subjectivity state

Describe the bug
Got this error when trying to download a weak subjectivity state:
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:  ✖ Error: Unable to fetch weak subjectivity state: Timeout request
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:     at fetchWeakSubjectivityState (file:///usr/src/lodestar/packages/cli/src/networks/index.ts:190:11)
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:     at processTicksAndRejections (node:internal/process/task_queues:96:5)
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:     at initFromWSState (file:///usr/src/lodestar/packages/cli/src/cmds/beacon/initBeaconState.ts:153:37)
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:     at initBeaconState (file:///usr/src/lodestar/packages/cli/src/cmds/beacon/initBeaconState.ts:94:12)
Jun 24 14:40:11 contabo-7 beacon_run.sh[2384756]:     at Object.beaconHandler [as handler] (file:///usr/src/lodestar/packages/cli/src/cmds/beacon/handler.ts:68:41)

Expected behavior
Since the state is big, we should be able to increase the timeout at client api when downloading a state
Steps to Reproduce
Use below param:
weakSubjectivitySyncLatest: "true"
weakSubjectivityServerUrl: "https://some-server.io"
weakSubjectivityCheckpoint: "checkpoint:epoch"

What's the current timeout? It should also log the timeout time for better debugging

60_000 is the default timeout, i think its sufficient for for 150/200MB downloading state, others can offline download it (octect stream) and dump into file and provide that, may be we can log this message in the timeout error here

I think its sufficient for for 150/200MB downloading state (and most of time i have seen timeouts happening when server is genrally super slow or network is really very bad).

it usually takes more than 60s to download state:

contabo-20: 1m57s

devops@contabo-20:~$ curl -H 'Accept: application/octet-stream' https://***.infura.io/eth/v2/debug/beacon/states/3367104 --output state_3367104.ssz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 49.8M    0 49.8M    0     0   434k      0 --:--:--  0:01:57 --:--:--  884k

hetzner-test0: 3m1s

devops@hetzner-test0:~/tuyen/beacon$ curl -H 'Accept: application/octet-stream' https://***.infura.io/eth/v2/debug/beacon/states/3367104 --output state_3367104.ssz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 49.8M    0 49.8M    0     0   281k      0 --:--:--  0:03:01 --:--:--  871k

my localhost: 2m21s

Tuyens-MacBook-Pro-16519:Downloads tuyennguyen$ curl -H 'Accept: application/octet-stream' https://***eth2-beacon-prater.infura.io/eth/v2/debug/beacon/states/3367104 --output state_3367104.ssz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 49.8M    0 49.8M    0     0   359k      0 --:--:--  0:02:21 --:--:--  320k

Because the issue with really big timeouts with (for really slow networks) would be to log status on the cli else the user wiil go wondering if lodestar is stuck

this is a valid concern 👍 , I think it's a matter of UX, not with the timeout. One thing we can do is periodically log to the screen while waiting for all state bytes to be downloaded

In this scenario others can offline download it (octect stream) via curl and dump into file (we can may be throw the command here) and provide that, may be we can log this message in the timeout error here

this is a good idea, we should improve our log to instruct users to do that

@tuyennhv thanks for the stats! is infura super slow generally or have speed rationing? very poor download speeds seems like.

I'm not sure if that's the specific issue of infura or not since the node usually have to regen state (we store state per 1024 epochs)

In this case I would propose make kick it to 5 mins. multiple logs will take care of UX.

I increased that to 5 mins in the PR 👍


Crawler[UPDATED]

I have done all the changes pointed. Please review @sayamkanwar

@arjunkapoor19 You didn't make any change to the files. Please check your PR, also this is the master branch. I think you wanted to create a PR from a different branch? If that's the case please close this PR and open a new one from that branch where you have made the changes

@arjunkapoor19 You didn't make any change to the files. Please check your PR, also this is the master branch. I think you wanted to create a PR from a different branch? If that's the case please close this PR and open a new one from that branch where you have made the changes

ok