Prints *.htm.* continuously as part of reply about gitignore

Type: Bug
Ask the prompt, "In a CubeIDE project, what should the gitignore look like?"
The reply starts off sensical and then continues to produce *.htm.* continuously forever.
 Both times I eventually hit stop.
Reply:
# CubeIDE specific files
.cproject
.project
.settings/
.vscode/
.idea/

# CubeMX generated files
*.ioc
*.log
*.bak
*.launch

# Build artifacts
Debug/
Release/
build/

# Object files, static and dynamic libs
*.o
*.a
*.so

# Precompiled Headers
*.gch
*.pch

# Libraries
lib/

# Executables
*.elf
*.bin
*.hex
*.map

# Backup files
*~
*.swp
*.swo
*.swn
*.bak
*.tmp

# Other IDE specific files
*.d
*.dep
*.lst
*.srec
*.lss
*.axf
*.sct
*.crf
*.htm
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*
*.htm.*


Fix getInStream worker net address

What changes are proposed in this pull request?
Please outline the changes and how this PR fixes the issue.
Why are the changes needed?
Please clarify why the changes are needed. For instance,

If you propose a new API, clarify the use case for a new API.
If you fix a bug, describe the bug.

Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

alluxio-bot, cherry-pick this to branch-3.0-preview

alluxio-bot, merge this please

alluxio-bot, cherry-pick this to branch-3.0-preview please


[windows] Provide %long-tmp in Windows for extended length temp paths.

In Windows %t might end up very close to the maximum path length of 260
characters. It is possible to use extended lenght paths with a \?
prefix. The changes introduce %long-tmp for cases that the test suite
is going over those limits and need a hint in Windows that the path
might be long. It expands to the same as %t in other platforms.
This should fix the test/Misc/stats_dir_profiler.swift in the Windows
VS 2017 CI machines and hopefully not affect anything else.

@swift-ci please smoke test

This is definitely a clever solution to the problem.  I wonder how terrible it would be to actually make this part of %t in general.  Is there a reason to not just do that?

This is definitely a clever solution to the problem. I wonder how terrible it would be to actually make this part of %t in general. Is there a reason to not just do that?

Two reasons:
%t is provided by Lit. I think one can use %t to override the value, but I didn't find a way to recover the old value. The default substitutions are not in the array when lit.cfg executes, and are added later.
The second reason is that this is limited to something that I know it is working. Replacing every %t might be fine, but maybe some tools will not behave correctly when using paths that start by \\?\. In this case it seems to work. I think this allows us to grow the solution until we are sure is safe, instead of finding a lot of problems because of a simple change.

@compnerd: some reason NOT to merge this? Otherwise it would be nice to have a good build in the VS2017 builder.

Nope, should be okay to merge.  I just wanted to understand if there was any limitation or not (Id like to see this grow to replace %t so that we don't need to do the ad hoc changes for long paths).

You can check if adding the prefix in Lit itself will work for every test. Besides printing \\?\ in front of every path, it might be that everything works. But I will not be surprised if some tools starts to fail because they "parse" the paths in Windows expecting relative paths, and interpret the first \ of the prefix as relative to the current drive.
Thanks for merging! https://ci-external.swift.org/job/oss-swift-windows-x86_64/5594/ is the first blue in a while! :D


Add dotEnv to turbo.json

Enable configuring .env files inside of turbo.json. These are addition-only to file hashes.
(More details later.)

@mehulkar

Is there any difference between using this key and the inputs key?

Yes, specifying the first glob in inputs toggles off the "include everything in the git index inside this package's folder" default. (caveats apply, but they're bugs: see Slack thread)
Having an alternative method to specify this does a few things:

By simple existence causes people to actively consider their .env files. Sometimes simply naming a thing or pattern makes the UX better. (For context: you could do 100% of what Ember Services could do when introduced using vanilla Ember things if you knew the incantation; same applies here.)
Creates a configuration location that does not toggle off the default behavior.
Gives us some rails to ride on for future "help me not screw up .env files" behavior.

do we want to throw an error if it's specified in both places?

No, because it doesn't make any material difference if you include it in both places (they get combined into the same list of hashed files).

What happens if you add inputs: [!.env]?

Given this configuration:
{
  "inputs": ["**", "!.env*"],
  "dotEnv": [".env.local", ".env"]
}

The file hash will include .env and .env.local (if present on disk). This is a conservative default; it results in over-partitioning in the event of misconfiguration.
In one proposed possible future variant turbo --dotenv will load environment variables from those locations and not merge the files into the task hash; instead encouraging you to specify your environment variable dependencies using env (and passthroughEnv). This would make the configuration you describe appear sensible, but would already be configured for you by turning all of dotEnv to excludes when that flag is present.
(Including the entire file and the entire fallback chain is already over-partitioning; this would enable precise targeting.)


my server can not access ILB ASE in the same network

The same vnet and resources are in different subnets
checking the default created NSG it looks ok.
what else should i do to be able to access the ILB ASE
I have also double clicked onto the certificate in the vm that i am doing the calls
Reference
https://docs.microsoft.com/en-us/azure/app-service/environment/create-ilb-ase

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

ID: 2b1afa49-a5b4-92db-68e8-3feeeff52eb3
Version Independent ID: c9191775-e49c-1462-e525-a5ce549ae743
Content: Create and use an internal load balancer with an Azure App Service Environment
Content Source: articles/app-service/environment/create-ilb-ase.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@rifaterdemsahin Thank you for your question. The scope azure-docs on GitHub is for handling issues directly related to the doc. Since this is going beyond the initial creation that the doc covers, we request you to post your question in the MSDN Forums. Microsoft actively monitors this channel as well and someone will be able to assist you there.
Thank you for your understanding.

@BryanTrach-MSFT than there is no custom DNS setting in the documentation.
We are about to fail the project as we can not set the custom dns for our web app for containers in side the ILB ASE.

I have created a video about the problem and emailed to<EMAIL_ADDRESS>


Fix VS F1 for ASP.NET Core API

@rpetrusha can you get me started on this?

From: Daniel Roth
Den, when we get API refs setup for ASP.NET Core will we also get F1 support? Or do we have to do additional work?
From: Gordon Hogenson
OK – here is the feedback bug. I assigned it to Dan Roth:
https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems?id=437117&_a=edit
From: Den Delimarschi
I am meeting with Dan about this tomorrow – ASP.NET Core does not yet publish from ECMAXML.
From: Gordon Hogenson
Dan –
The issue is customers are saying that F1 doesn’t work for ASP.NET Core APIs. Is that true, and if so, how can we enable F1 for ASP.NET Core API reference?
I was asking about Xamarin XML because that system for Managed Reference has a built-in F1 support mechanism.
If you are creating your own reference topics, you probably just need to add the F1 metadata as part of your process.  For example, in C++ reference, we add the “f1_keywords” metadata directly to the the header in each topic:
https://github.com/Microsoft/vcppdocs/blob/master/docs/c-runtime-library/cgets-cgetws.md
f1_keywords:

"cgetws"
"_cgetws"
"_cgets"

cc @dend

@rpetrusha  or @dend can you get me started on this?

@rpetrusha or @dend can you get me started on this?


Improve db reingest range command

Improves db reingest range command by starting multiple workers at the same time and committing work more often. Introduces util.WorkersPool  responsible for distributing work between workers.
This changes some queries that required Postgres 9.5+ (upsert query) so a base branch was set to release-horizon-v0.18.0.
Fix (partially): #931 and #917.

Do you mind rebasing this PR and resolve the conflicts?

@howardtw rebased. Can you take a look again?

I wonder if we can break this PR into two different ones: one for introducing workers, one for making from & to CLI flags, since most of the work here is aiming to add worker functionalities.

I wonder if we can break this PR into two different ones

Yeah, maybe that would make sense before a review but now, after 2 rounds, I think it doesn't make sense.

Well the first round was to ask for resolving merge conflict. That was really a review.

OK, you're right. I was quickly switching between PR and haven't noticed it. I think I'm good with splitting this into 2 PRs.

@howardtw done, CLI params will be added in a separate PR (not sure if this is the final form of the code - pre review).

@howardtw fixed. PR branch was way behind Circle CI integration that's why it didn't work.


[fixes #22744] Update hadoop library patch versions to 2.10.2 and 3.2.4

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run PostCommit_Java_Hadoop_Versions

R: @apilloud

Run Kotlin_Examples PreCommit

Run SQL PreCommit


How to use collections with ignore?

I am having a one-page that should include some collections. But, I don't want to generate those include files. So I am using .ignore("mypath") like described in the docs. However, when using ignore after or before using collections, those include files will be deleted from the stack of the collection. So, how can I use ignore but still get even ignored files into the stack of collections?
I am aware that this repository is not actively maintained, so in the meantime I will either don't use this plugin or delete the ignore files after using metalsmith.

Just adding my voice as I'm struggling with this, too. Would like to be able to basically say "Add all of markdown files in folder abc except files named blah".
Was trying to employ some of the concepts described here but didn't get anything to stick.

It's an old issue, but for any future searchers, you can exclude them like this under pattern:
.use(collections({
    pages: {
        pattern: '*(!cv).md',
    }
}))

So now I have a pages collection with every Markdown file under src/, except my cv.md file.

Metalsmith.ignore always executes before any plugins run. Use @metalsmith/remove to remove files after they have been used by other plugins. As for excluding certain files inside a same folder, you would use a negated pattern along with a regular glob pattern, like so: ['abc/**/*.md', '!abc/blah.md']


[ConstraintSystem] trySimplifyToExpr shouldn't rely on locator bein…

…g always anchored
If constraint system is used as part of the declaration checker to
e.g. verify generic requirements for a witness, locators are not going
to have an anchor.
Resolves: SR-10728
Resolves: rdar://problem/50987089

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 0d9ef6975efa29ece664904169b1a217274c86ba

Build failed
Swift Test Linux Platform
Git Sha - 0d9ef6975efa29ece664904169b1a217274c86ba

@swift-ci please test

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test source compatibility


The Jenkins part works as expected. On Github the job is currently marked as "failed" instead of unstable. I'm not sure this is easily fixable

The Jenkins part works as expected (see https://jenkins.devops.iris-sensing.net/job/iris-kas/job/PR-70/4/display/redirect). On Github the job is currently marked as "failed" instead of unstable. I'm not sure this is easily fixable

Leave it as it is for now. MIght just be the matching between unstable and failed, But this doesn't matter for now. Toolintegration isn't annouced yet.


updated gog-downloader (1.2_512)

Thank you for the contribution. It was merged directly as 4caf203f304e7c7866a81d6e7ff49750117b9fac to keep commit history cleaner. Your contribution is still credited to you.


Connection refused

After typing in my username and password, I'm getting the following message:
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='apresolve.spotify.com', port=443): Max retries exceeded with url: /?type=accesspoint (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x000001CF36E4EDB0>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it'))
Any idea what is wrong?

could be a rate limit or maybe ban

Did you ever fix it? I have the same problem


update version due to recent update

For me its 5th but in the US in some places its 4th so I set this as 4th, @ThioJoe tell me if I should set this to 5, but this needs updating because you commited more links 1 hour ago.

Ah already fixed


Options for UI/whichkey?

The "whichkey" UI is helpful for submenus, or if I forget keybindings/want to see a menu; but it can be a bit distracting when I'm using frequently used commands.
is there a way to control when it is displayed? perhaps something like only displaying when the root key (super_l in the default) is released?

There are tons of options to configure it.
There are toggle_keys.  You can also configure hints.delay. Or you can simply disable it for the root menu, and enable it for every submenu individually, which is also how I set it up personally.

A combination of disabling hints for the root menu and enabling hints for individual submenus along with toggle_keys seems to work.


Wrong sorting of numbers after a minus

Hi, there is a strange bug in the TinySort library.
When I have a number after a minus at the end of a text, it is sorted in the wrong direction. When there is any letter after the number, it works as expected.
The issue is reproduced in this fiddle: http://jsfiddle.net/gcLhon04/4/

It's not a bug it's a feature :-D
It's intended behaviour. It will read numeral values including minus signs (negative) unless you specify {ignoreDashes:true} .


HostConfig.json URL is directing to a not found page

On clicking the "HostConfig.json" link mentioned in the first paragraph, user is directed to a github's 'page not found' page.

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

ID: 44fd469c-440f-4cdd-d3fb-7e5e3c04b6c7
Version Independent ID: 4f75b3e8-6705-80f5-d4b6-e2eeac654f35
Content: HostConfig for Adaptive Cards - Adaptive Cards
Content Source: AdaptiveCards/rendering-cards/host-config.md
Product: adaptive-cards
GitHub Login: @paulcam206
Microsoft Alias: paulcam

Thanks! This is fixed and should be updated on the site within the hour


Replace vendored quantified by the released gem

@Shopify/shipping This fixes #227.

https://rubygems.org/gems/quantified
:rocket:


Scrolling inside Slide

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
Hello, I have slides with vertical sliding direction. Inside one of the slides I have the list with the scroll. When I try to scroll the list, the whole slide slides to the next slide. In previous version of slides, I've added noSwipingClass to my list and everything worked like a charm. Now I can't do such thing because of the new uber-crippled slides. Is there any solution to this or do I have to throw away my whole project?
Expected behavior:
Scrolling list inside slide instead of swiping to the next slider.
Steps to reproduce:
Put a list inside slider. Same scrolling direction for the list and slider.

Hello, thanks for opening an issue with us and sorry slides are not working like they should, we will look into this. Is this happening in 2.3.0? @manucorporat is this possibly happening because of the scroll events issues in 2.3.0?

Hello, thanks for using Ionic. After further review I am going to close this issue as a duplicate of https://github.com/driftyco/ionic/issues/6301.


GIT Checkout of Master Branch is 2.6.0rc1 versus west update as 2.5.99

Using a GIT clone, and making the master branch active, there are tons of differences between what is provided as the master branch, and the typical method for getting Zephyr source code as:
west init ~/zephyrproject
cd ~/zephyrproject
west update
west update does not bring this source distro to match the GIT master branch.
So what is the recommended version, i.e. the stable master branch?

An update using the standard west procedure described above to recreate the entire ZephryProject appears to pull at this time of this memo, the 2.6.0.rc1 release as the master branch in GIT.


Add Dijkstra Algorithm

Add the C++ version of Dijkstra Algorithm.
The code should be in /Graph Theory/Dijkstra Algorithm
For further reference: Brilliant

Hey, @ekdnam I would like to work on it.

I would like to contribute to this issue in c++ language

I would like to contribute. Provide me the chance

hey @ekdnam i would like to work on this

Dijkstra C++ has been added. Closing this issue now


cds translate error

this an error message - it would be helpful if this also included a report of what the sequences name is causing the problem (and sequence file) - I assume there is an internal stop codon, it would be better to just skip failed sequences than crash the whole thing.
2023-10-05 10:17:52,338 PHYling INFO Inputs are dna sequences
Traceback (most recent call last):
  File "/bigdata/stajichlab/shared/condaenv/phyling2/bin/phyling", line 8, in <module>
    sys.exit(main())
  File "/bigdata/stajichlab/shared/condaenv/phyling2/lib/python3.10/site-packages/phyling/phyling.py", line 208, in main
    args.func(**vars(args))
  File "/bigdata/stajichlab/shared/condaenv/phyling2/lib/python3.10/site-packages/phyling/libphyling.py", line 431, in main
    msa = msa_generator(inputs)
  File "/bigdata/stajichlab/shared/condaenv/phyling2/lib/python3.10/site-packages/phyling/libphyling.py", line 155, in __init__
    self._pep_seqs = self._sequences.translate()
  File "pyhmmer/easel.pyx", line 5835, in pyhmmer.easel.DigitalSequenceBlock.translate
  File "pyhmmer/easel.pyx", line 5889, in pyhmmer.easel.DigitalSequenceBlock.translate
ValueError: Incomplete sequence of length 1672 at index 2281

Fix by fe7267fb2ba26062cf70f8dd6d35c320b325a585


Click event on bar chart on Chrome

Here I have a very simple example:
<c3chart bindto-id="bar-plot1-chart">
  <chart-column column-id="Data 1"
              column-values="70"
              column-type="bar"/>
  <chart-column column-id="Data 2"
              column-values="35"
              column-type="bar"/>
  <chart-column column-id="Data 3"
              column-values="60"
              column-type="bar"/>
  <chart-bar title="Donut" width="60"/>
  <chart-events on-click-data="showClick(data)"/>
</c3chart>

with the corresponding function
$scope.showClick = function(data){
  console.log(data);
};

It works fine and displays the graph both on FF and Chrome, but when I click on the graph, it works on FF but on Chrome I get the error
Uncaught TypeError: Cannot read property 'getItem' of undefined c3.js:3248

But if I change the chart type to donut:
<c3chart bindto-id="bar-plot1-chart">
  <chart-column column-id="Data 1"
              column-values="70"
              column-type="bar"/>
  <chart-column column-id="Data 2"
              column-values="35"
              column-type="bar"/>
  <chart-column column-id="Data 3"
              column-values="60"
              column-type="bar"/>
  <chart-bar title="Donut" width="60"/>
  <chart-events on-click-data="showClick(data)"/>
</c3chart>

It works like a charm on both Chrome and FF

I can verify your issue, now need to make sure it is a problem in my code or in the c3 code. Strange that it happens in chrome only. Need to do some more research.

Is a problem in the c3 library:
https://github.com/masayuki0812/c3/issues/1566

Indeed, thanks for the investigation :)

There is a fix available, you need to include an additional library, did not (yet) test it myself:
https://github.com/progers/pathseg


Allow function calls to be lowered as statements

This PR allows the user to specify that certain function calls should be lowered as statements.
For example, on Python, print and assert are statements -- return print(x) and f(print(x)) are errors. So a function like this:
(define foo (x)
  (print x))

... compiles to return print(x), causing a syntax error.
Currently, a user could deal with this situation by making print and assert special forms via define-special. But that's rather inconvenient since print and assert aren't really special forms -- their compiled output is identical to regular function calls.
After merging this PR, (setenv 'print :stmt) and (setenv 'assert :stmt) will cause (print x) and (assert x) to be lowered as statements, solving the problem.

Too complicated.


[New API] : adding climacell api

Brief Description 🤓
Climacell, now known as Tomorrow.io, offers a comprehensive weather data platform that provides accurate, hyper-local weather information.
How will you develop it?🤩
react,js
Deployment
None
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @AmruthaPariprolu🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc 24

/gssoc24


Read with timeout

Is there any way to read ifce with timeout?

I still haven't found an easy way to read and write over time. Finally, the go-winio library is adopted and part of the code is extracted for implementation.


What eyebrows are needed for upper Mid 2x1 eyes?

I tried to animate the skin, but for some reason I always had problems with either the eyes or the eyebrows...

If it’s not difficult, how to make an animation for this:
!(https://github.com/IthanMendoza/Fresh-Moves/assets/121681870/dd58af36-06da-4c28-81a2-f360d587dda7)

This one

This one

Everything was done according to the instructions:

You put them too high. This is the correct positions:


[1.3] Demand Response Load Control Cluster XML has to be updated as per spec

Description :

[ ] While defining the 'LoadControlEventStatusChange' event field, there was a miss in defining the mandatory 'Signature' field.

PFA XML Reference
https://github.com/project-chip/connectedhomeip/blob/master/src/app/zap-templates/zcl/data-model/chip/drlc-cluster.xml

That field is removed in the outstanding spec PRs that should be landing soon.


Failed to build tensorflow 2.3.0 from source on Nvidia Jetson Nano

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Jetpack 4.4 (Ubuntu 18.04 LTS)
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version: 2.3.0
Python version: 2.7.17 and 3.6.9
Installed using virtualenv? pip? conda?: N/A
Bazel version (if compiling from source): Build label: 3.1.0- (@non-git)
GCC/Compiler version (if compiling from source): (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0
CUDA/cuDNN version: 10.2.89 / <IP_ADDRESS>
GPU model and memory: Nvidia Jetson Nano

Describe the problem
ERROR: /home/minhduc/src/tensorflow-2.3.0/tensorflow/core/kernels/BUILD:6109:1: C++ compilation of rule '//tensorflow/core/kernels:training_ops' failed (Exit 4)
aarch64-linux-gnu-gcc-7: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
Target //tensorflow:libtensorflow.so failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 10499.940s, Critical Path: 654.48s
INFO: 5016 processes: 5016 local.
FAILED: Build did NOT complete successfully
Provide the exact sequence of commands / steps that you executed before running into the problem
I followed this tutorial (github). I set up my virtual screen, start the build (NOT install) script (build_libtensorflow-2.3.0.sh). Go to school and come back home with the error log above
Any other info / logs
I also install both protobuf 3.8.0 and bazel using shell scripts from the above github repo

@minhduc66532,
TensorFlow v2.3 is compatible with CUDA 10.1 and cuDNN 7.6. For more information, please take a look at the tested build configurations.
Also, please follow the official guide while building TensorFlow from source and check if you are facing the same issue. Thanks!

@minhduc66532,
TensorFlow v2.3 is compatible with CUDA 10.1 and cuDNN 7.6. For more information, please take a look at the tested build configurations.
Also, please follow the official guide while building TensorFlow from source and check if you are facing the same issue. Thanks!

I have downgraded Jetpack 4.4 to Jetpack 4.3

Still the getting error:
ERROR: /home/minhduc/src/tensorflow-2.3.0/tensorflow/core/kernels/BUILD:2828:1: C++ compilation of rule '//tensorflow/core/kernels:padding_fifo_queue' failed (Exit 4)
aarch64-linux-gnu-gcc-7: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
Target //tensorflow/tools/lib_package:libtensorflow failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 9190.224s, Critical Path: 1217.73s
INFO: 5456 processes: 5456 local.
FAILED: Build did NOT complete successfully

I have downgraded Jetpack 4.4 to Jetpack 4.3

Still the getting error:
ERROR: /home/minhduc/src/tensorflow-2.3.0/tensorflow/core/kernels/BUILD:2828:1: C++ compilation of rule '//tensorflow/core/kernels:padding_fifo_queue' failed (Exit 4)
aarch64-linux-gnu-gcc-7: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
Target //tensorflow/tools/lib_package:libtensorflow failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 9190.224s, Critical Path: 1217.73s
INFO: 5456 processes: 5456 local.
FAILED: Build did NOT complete successfully

@minhduc66532,
Now you have CUDA 10.0 with cuDNN 7.6, which is not compatible with any of the TensorFlow 2.x versions. As shown in the table below, please try building either
TF v2.4 with CUDA 11.0 and cuDNN 8
or
TF v2.3 with CUDA 10.1 and cuDNN 7.6

Version
Python version
Compiler
Build tools
cuDNN
CUDA

tensorflow-2.4.0
3.6-3.8
GCC 7.3.1
Bazel 3.1.0
8.0
11.0

tensorflow-2.3.0
3.5-3.8
GCC 7.3.1
Bazel 3.1.0
7.6
10.1

tensorflow-2.2.0
3.5-3.8
GCC 7.3.1
Bazel 2.0.0
7.6
10.1

tensorflow-2.1.0
2.7, 3.5-3.7
GCC 7.3.1
Bazel 0.27.1
7.6
10.1

tensorflow-2.0.0
2.7, 3.3-3.7
GCC 7.3.1
Bazel 0.26.1
7.4
10.0

Thanks!

@minhduc66532,
Now you have CUDA 10.0 with cuDNN 7.6, which is not compatible with any of the TensorFlow 2.x versions. As shown in the table below, please try building either
TF v2.4 with CUDA 11.0 and cuDNN 8
or
TF v2.3 with CUDA 10.1 and cuDNN 7.6

Version
Python version
Compiler
Build tools
cuDNN
CUDA

tensorflow-2.4.0
3.6-3.8
GCC 7.3.1
Bazel 3.1.0
8.0
11.0

tensorflow-2.3.0
3.5-3.8
GCC 7.3.1
Bazel 3.1.0
7.6
10.1

tensorflow-2.2.0
3.5-3.8
GCC 7.3.1
Bazel 2.0.0
7.6
10.1

tensorflow-2.1.0
2.7, 3.5-3.7
GCC 7.3.1
Bazel 0.27.1
7.6
10.1

tensorflow-2.0.0
2.7, 3.3-3.7
GCC 7.3.1
Bazel 0.26.1
7.4
10.0

Thanks!

Wow, so it has to be EXACTLY cudnn 7.6.0 and CUDA 10.1 ? Ok i'm gonna try again tomorrow and report the result

Wow, so it has to be EXACTLY cudnn 7.6.0 and CUDA 10.1 ? Ok i'm gonna try again tomorrow and report the result

Problem solved. This guy  already built it on Jetpack 4.4 you can just download and use it.
And fun fact Jetpack 4.4 is using CUDA 10.2 and cuDnn 8.0. But anyway thank you for answering all of my question, really appreciated it. Have a great day

Problem solved. This guy  already built it on Jetpack 4.4 you can just download and use it.
And fun fact Jetpack 4.4 is using CUDA 10.2 and cuDnn 8.0. But anyway thank you for answering all of my question, really appreciated it. Have a great day


Photo should display owner(uploader)?

When viewing photo in detail, the owner account should be displayed also (maybe like in gallery view, under title)

Yup


ContainerLayers with BlendMode look inconsistent

with the following RenderObject only in case of ColorFilterLayer the green rectangle is inside the red one since it is drawn with BlendMode.srcIn, is it by mistake and blend modes should not be honored in ContainerLayer's painter code?
class FooWidget extends LeafRenderObjectWidget {
  @override
  RenderObject createRenderObject(BuildContext context) => _RenderFooWidget();
}

class _RenderFooWidget extends RenderProxyBox {
  @override
  void performLayout() {
    size = Size(constraints.maxWidth, 7 * 150.0);
  }

  @override
  void paint(PaintingContext context, Offset offset) {
    context.pushLayer(OffsetLayer(offset: offset), _offsetPainter, offset);
  }

  double y = 0;
  TextPainter tp;
  _offsetPainter(PaintingContext context, Offset offset) {
    y = 0;
    final layers = [
      OffsetLayer(offset: Offset.zero),
      ClipRectLayer(clipRect: Offset.zero & size),
      ClipRRectLayer(clipRRect: RRect.fromRectAndRadius(Offset.zero & size, Radius.zero)),
      ClipPathLayer(clipPath: Path()..addRect(Offset.zero & size)),
      ColorFilterLayer(colorFilter: ColorFilter.mode(Colors.black, BlendMode.dst)),
      TransformLayer(transform: Matrix4.identity()),
      OpacityLayer(alpha: 255),
    ];
    layers.forEach((childLayer) {
      tp = TextPainter(
        text: TextSpan(text: childLayer.toString(), style: TextStyle(color: Colors.black)),
        textDirection: ui.TextDirection.ltr,
      );
      tp.layout();
      context.pushLayer(childLayer, _layerPainter, offset);
    });
  }

  _layerPainter(PaintingContext context, Offset offset) {
    context.canvas.drawRect(Rect.fromLTWH(100, y + 0, 100, 100), Paint()..color = Colors.red);
    context.canvas.drawRect(Rect.fromLTWH(150, y + 50, 100, 100), Paint()..color = Colors.green..blendMode = BlendMode.srcIn);
    tp.paint(context.canvas, Offset(0, y));
    y += 150;
  }
}

the following image shows FooWidget - all layers are drawn the same way except for ColorFilterLayer - only with that layer the green rectangle drawn with Paint()..color = Colors.green..blendMode = BlendMode.srcIn seems to be drawn correctly, so the question is if all other layers have bugs or ColorFilterLayer is buggy?

flutter doctor output:

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, 2.7.0-3.0.pre, on LMDE 4 (debbie) 4.19.0-8-amd64, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 4.0)
[✓] Android Studio (version 3.4)
[✓] Android Studio (version 3.6)
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2017.1)
[✓] VS Code (version 1.62.0)
[✓] Connected device (2 available)
• No issues found!

@pskink
Thanks for the report. Can you please provide flutter doctor -v along with actual vs expected behavior ?

added an image and "flutter doctor" output

Thanks for the update. I see the same behavior on latest stable and master.

 stable, master flutter doctor -v
[✓] Flutter (Channel stable, 2.5.3, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.5.3 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (2 days ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/dhs/Library/Android/sdk
    • Java binary at: /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 93.0.4577.82

• No issues found!

[✓] Flutter (Channel master, 2.6.0-12.0.pre.701, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.6.0-12.0.pre.701 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 24b9346c9b (5 hours ago), 2021-11-11 16:45:40 -0800
    • Engine revision aaacb670af
    • Dart version 2.15.0 (build 2.15.0-285.0.dev)
    • DevTools version 2.8.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Users/dhs/Library/Android/sdk
    • Java binary at: /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/dhs/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/202.7486908/Android
      Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.57.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 93.0.4577.82

• No issues found!

if all other layers have bugs or ColorFilterLayer is buggy?

Will leave it for team to comment on it.

cc @flar

First, to understand SrcIn, it draws within the alpha of its background.  If you then draw a green rectangle anywhere on this surface with SrcIn, it will just be a green rectangle. SrcIn is no different than SrcOver in the case of rendering to a large surface full of opaque pixels.
The ColorFilterLayer is different because it involves a graphical saveLayer which isolates its children in order to apply the ColorFilter to them. It must first accumulate the output of its children and then filter them. This graphical layer starts out transparent. In that one case the rendering becomes an opaque red rectangle on a transparent surface and when the SrcIn green rectangle is drawn over it, it can only affect the opaque pixels that only exist in the bounds of the red rectangle.
I can see how the terminology used in the names of the classes can cause confusion here, though.
Most of the ...Layer classes don't represent a separate graphical rendering layer as in a saveLayer, they represent a group of objects with some sort of modification applied to them.
Sometimes that modification requires a saveLayer to do its work (such as in ColorFilterLayer or ImageFilterLayer). I would have thought that the OpacityLayer - which operates via a saveLayer as well, would have also shown the "clipping" of the green rectangle as did the ColorFilterLayer, but the results for that layer were not shown in the image attached above.
In other cases the layers don't really require graphically capturing/separating the pixels of the children. OffsetLayer, for example, just offsets its children which it can do through a modification of the transform matrix. Clipping just requires the installation and removal of a clip. Though a clip layer that uses the antialiasWithSaveLayer behavior will also show the intersection of the green rectangle because it needs to isolate the child rendering before applying the clip mask.
This all stems from a confusion over the use of the term Layer in the framework classes and how that implies a connection with a saveLayer type of graphical operation.

thanks a lot for explaining that it uses saveLayer under the hood- i thought that ColorFilterLayer do that in some other "magical" way
as for OpacityLayer - it renders as any other layer (that is big green rect on top of big green one) - are you sure OpacityLayer uses saveLayer as well? i learned from the docs that saveLayer is an expensive operation so how RenderAnimatedOpacityMixin can efficiently manage "opacity animation" if it uses saveLayer in OpacityLayer (https://github.com/flutter/flutter/blob/c19845a8c3/packages/flutter/lib/src/rendering/proxy_box.dart#L1008)?

Ah, I see. You are using an OpacityLayer with an alpha of 255 which omits the layer. If you change the alpha (even to 254) then it will use the saveLayer.
There is a bug about this behavior (https://github.com/flutter/flutter/issues/58425) of omitting the layer when alpha is 255. That issue describes a break in the raster caching performance, but you've just created a case that demonstrates how doing so also creates an inconsistency of its output.

@flar yes indeed, i check it and when run with alpha: 254 it forces saveLayer and "clipped" green rectangle

I believe this is WAI and I'm closing the issue.


ONE D&D Heal buff [CureWounds]

ONE D&D Heal buff [CureWounds]

It looks like you forgot to push most of your changes, or am I missing something? I can only see 1 line changed, and that line just declares new property.

ush most of your

I didn't know how to upload them together, so I uploaded them separately.SolastaUnfinishedBusiness/Models/SrdAndHouseRulesContext.cs
This is the function where you can adjust the numerical values in earnest.


Advancements

Advancements for recipe-unlock are appearing on the advancements page. Just three "black sections", with a respective icon only, no title, no background, etc. (easily reproducible by creating a world and granting an user all advancements by command)
The solution I have seem around is that for advancements related to recipe unlock only, the section "display":{...} should not be included. Doing so will hide those glitches sections, avoiding the small inconvenience for the users.
This does not affect game-play. And can be fixed in the user side by simple replacing the respective files in a datapack.

Might i ask for a datapack to fix it?
Also here are screenshots

@InsaanNotFound here is what i am using.
toms-storage-fix.zip


Qingwei/fix trade amount

Coverage decreased (-0.01%) to 31.648% when pulling bda7c720241f5efafa7ef4c2dce5b196a7500104 on qingweibinary:qingwei/fix_trade_amount into 8c45a1b495ab0c12b7a622d594f5f88ebe76714f on binary-com:master.


Using assembly

"Using assembly" doesn't work in PS 6 as well as in PS 5.1.  It's also undocumented in "about_using".  https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_using?view=powershell-6
Steps to reproduce
using assembly system.web

Expected behavior
# successfull execution with no output

Actual behavior
At line:1 char:16
+ using assembly system.web
+                ~~~~~~~~~~
Cannot load assembly 'system.web'.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : ErrorLoadingAssembly

Environment data

Name                           Value
----                           -----
PSVersion                      6.1.2
PSEdition                      Core
GitCommitId                    6.1.2
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

@jszabo98 PowerShell Core doesn't support using assembly ... with partial names. If you use the full path to the assembly, it should work.

Seems weird that it doesn't support assembly names. The first thing I think to parallel using assembly is Add-Type -AssemblyName 😕

@vexx32 In Windows PowerShell, Add-Type has (or had?) a list of partial name to full name mappings so that you could load assemblies by partial name without going through the  deprecated-since-forever LoadWithPartialName() API. All of this stuff is related to the GAC but on Core, there is no GAC and no partial names.

@vexx32 In Windows PowerShell, Add-Type has (or had?) a list of partial name to full name mappings so that you could load assemblies by partial name without going through the deprecated-since-forever LoadWithPartialName() API. All of this stuff is related to the GAC but on Core, there is no GAC and no partial names.

Now it just does Assembly.Load(new AssemblyName(assemblyName)), which will load from the GAC on Windows.  I believe non-Windows will still try to load from  AppDomain.CurrentDomain.BaseDirectory (which would be where ever pwsh is installed), so System.Web should still work.

I think using assembly should have parity with Add-Type -AssemblyName, especially since Windows PowerShell had it.
@iSazonov Can you remove Resolution-Answered so this isn't closed? I think even if the PowerShell team disagrees, this would need Resolution-Won't Fix instead.

I checked that follow works
 Add-Type -AssemblyName System.Web

so follow should works too
using assembly System.Web

even if the PowerShell team disagrees

@SeeminglyScience  I am not in MSFT, I am a community maintainer. Sometimes I do a formal moderation based on trusting. "Formal" because I really can not looks every (from 2000!) issue in depth.
As for "Won't fix" I'd leave this to MSFT experts and PowerShell Committee to mark issues with backward compatibility and security considerations.

I am not in MSFT, I am a community maintainer. Sometimes I do a formal moderation based on trusting. "Formal" because I really can not looks every (from 2000!) issue in depth.
As for "Won't fix" I'd leave this to MSFT experts and PowerShell Committee to mark issues with backward compatibility and security considerations.

 I'm very glad the repo has you sorting through the chaos 🙂
I only meant to explain the reasoning behind my request, I 100% understand why you chose the original label.

I just realized I accidentally created a duplicate:

#11856

Indeed, name-only loading of assemblies that PowerShell ships with should work (plus from the GAC, on Windows) - both for symmetry Add-Type -AssemblyName and because using assembly System.Windows.Forms, for instance, works just fine in Windows PowerShell.


Seems to work nicely on my end. Did a schema update which added 8 new columns across multiple tables, and all where inserted at the right position, and the migration worked flawlessly.

Just for reference a link to the ticket: https://github.com/propelorm/Propel/issues/274

You need to write unit tests :)

Ok, I have experience writing PHPUnit-tests, but writing tests for these methods needs a lot of infrastructure. Any pointers on where to look for unit-tests inside Propel that do similar things, so I could have a look at it?

Yes, look at other tests in related Test classes :)

Ok I will rewrite it as necessary and provide some tests.


Postgres support broken since Netcore3 due to missing translation for DateTimeOffset

@fhebel the issue has been fixed 4 days ago

Sorry for bothering you. I”ll give it a try ...


Several lintian errors

I don't know if you know of lintian but it gives quite a number of errors on a sample generation:
N:
E: my-awesome-app: control-file-is-not-a-file ./
N:
N:   The package contains a control file that is not a regular file.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: control-files
N:
N:
E: my-awesome-app: description-synopsis-is-duplicated line 1
N:
N:   The first line of the extended Description: should not repeat the synopsis
N:   exactly. This indicates that either the synopsis is badly formed or that
N:   the extended description has been wrongly copied and pasted.
N:
N:   Please refer to Debian Policy Manual section 3.4.2 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: fields/description
N:
N:
E: my-awesome-app: no-changelog usr/share/doc/my-awesome-app/changelog.gz (native package)
N:
N:   A Debian package that provides a /usr/share/doc/*pkg* directory must
N:   install a changelog file.
N:
N:   For native packages the best name is /usr/share/doc/*pkg*/changelog.gz.
N:
N:   For non-native packages the best name is
N:   /usr/share/doc/*pkg*/changelog.Debian.gz.
N:
N:   This tag may also be emitted when the changelog exists but does not
N:   otherwise resemble a Debian changelog.
N:
N:   Please refer to Debian Policy Manual section 12.7 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: debian/changelog
N:   Renamed from: changelog-file-missing-in-native-package
N:   debian-changelog-file-missing
N:
N:
E: my-awesome-app: no-copyright-file
N:
N:   Each binary package has to include a plain file
N:   /usr/share/doc/*pkg*/copyright
N:
N:   Please refer to Debian Policy Manual section 12.5 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: debian/copyright
N:
N:
E: my-awesome-app: non-standard-toplevel-dir ./
N:
N:   The Filesystem Hierarchy Standard forbids the installation of new files or
N:   directories in the root directory.
N:
N:   Please refer to Filesystem Hierarchy Standard for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: files/hierarchy/standard
N:
N:
E: my-awesome-app: wrong-file-owner-uid-or-gid ./ 1000/1000
N:
N:   The user or group ID of the owner of the file is invalid. The owner user
N:   and group IDs must be in the set of globally allocated IDs, because other
N:   IDs are dynamically allocated and might be used for varying purposes on
N:   different systems, or are reserved. The set of the allowed, globally
N:   allocated IDs consists of the ranges 0-99, 64000-64999 and 65534.
N:
N:   It's possible for a Policy-compliant package to trigger this tag if the
N:   user is created in the preinst maintainer script, but this is a very rare
N:   case and doesn't appear to be necessary.
N:
N:   Please refer to Debian Policy Manual section 9.2 for details.
 directory within data.tar.gz, control.tar.gz
Default uid/gid can be set to root
/usr/lib as a destination location is not a given for all apps

This package is concerned with building valid .deb distributables, not so much with making lintian happy, especially because there's no easy way to run a lintian check on systems other than Linux. As long as the user provides the minimum required info, they can have a .deb in the end.
That's why deboa provides lots of ways to fine-tune the build along the way (and I'm happy to add more if necessary) and leaves details regarding metadata and package structure best practices up to the user — it can't possibly do all the checks lintian does.
With that being said, here's the commented version of your error log:
### not sure about this one, could you share your .deb or at least the control file?
E: my-awesome-app: control-file-is-not-a-file ./
N:
N:   The package contains a control file that is not a regular file.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: control-files
N:
N:

### if you don't provide `options.controlFileOptions.extendedDescription`, it falls back to `options.controlFileOptions.shortDescription`. I should probably make the extended description a required field
E: my-awesome-app: description-synopsis-is-duplicated line 1
N:
N:   The first line of the extended Description: should not repeat the synopsis
N:   exactly. This indicates that either the synopsis is badly formed or that
N:   the extended description has been wrongly copied and pasted.
N:
N:   Please refer to Debian Policy Manual section 3.4.2 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: fields/description
N:

### this seems specific to your use case
E: my-awesome-app: no-changelog usr/share/doc/my-awesome-app/changelog.gz (native package)
N:
N:   A Debian package that provides a /usr/share/doc/*pkg* directory must
N:   install a changelog file.
N:
N:   For native packages the best name is /usr/share/doc/*pkg*/changelog.gz.
N:
N:   For non-native packages the best name is
N:   /usr/share/doc/*pkg*/changelog.Debian.gz.
N:
N:   This tag may also be emitted when the changelog exists but does not
N:   otherwise resemble a Debian changelog.
N:
N:   Please refer to Debian Policy Manual section 12.7 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: debian/changelog
N:   Renamed from: changelog-file-missing-in-native-package
N:   debian-changelog-file-missing
N:

### while having a copyright file is required by the Debian Policy Manual, you can install and run your app just fine without one
E: my-awesome-app: no-copyright-file
N:
N:   Each binary package has to include a plain file
N:   /usr/share/doc/*pkg*/copyright
N:
N:   Please refer to Debian Policy Manual section 12.5 for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: debian/copyright
N:

### the tar implementation I'm using creates an empty `.` directory in the root of the .deb directory structure, but nothing gets actually copied to the `/` directory when installing the package
E: my-awesome-app: non-standard-toplevel-dir ./
N:
N:   The Filesystem Hierarchy Standard forbids the installation of new files or
N:   directories in the root directory.
N:
N:   Please refer to Filesystem Hierarchy Standard for details.
N:
N:   Visibility: error
N:   Show-Always: no
N:   Check: files/hierarchy/standard
N:

### also seems specific to your use case. if you want the files to belong to this user/group, you'd need to check for them in a `preinst` script and create them if necessary
E: my-awesome-app: wrong-file-owner-uid-or-gid ./ 1000/1000
N:
N:   The user or group ID of the owner of the file is invalid. The owner user
N:   and group IDs must be in the set of globally allocated IDs, because other
N:   IDs are dynamically allocated and might be used for varying purposes on
N:   different systems, or are reserved. The set of the allowed, globally
N:   allocated IDs consists of the ranges 0-99, 64000-64999 and 65534.
N:
N:   It's possible for a Policy-compliant package to trigger this tag if the
N:   user is created in the preinst maintainer script, but this is a very rare
N:   case and doesn't appear to be necessary.
N:
N:   Please refer to Debian Policy Manual section 9.2 for details.
 directory within data.tar.gz, control.tar.gz

As noted above, it's a quirk of https://github.com/mafintosh/tar-fs IIRC. I tried changing this behavior when deboa was written, but I didn't managed to at the time.

Default uid/gid can be set to root

Can you clarify this?

/usr/lib as a destination location is not a given for all apps

/usr/lib is used as a sensible default, and deboa provides the beforePackage option which allows you to easily modify your directory structure just before packaging to serve other use cases:
import fsExtra from 'fs-extra'
import path from 'path'
import { Deboa } from 'deboa'

const deboa = new Deboa({
  beforePackage: async function (destination) {
    const newLocation = path.join(destination, '/your/desired/directory')

    await fsExtra.move(path.join(destination, 'usr', 'lib'), newLocation)
  },
  // ...other options
})

I don't think you can say than a deb package with lintian errors is a valid deb package.
Issues regarding changelog and copyright are not really specific to my use case. I don't provide them explicitly anywhere. I don't think it's a deal breaker, but deboa can provide some sensible defaults for these files.
E: my-awesome-app: control-file-is-not-a-file ./
E: my-awesome-app: non-standard-toplevel-dir ./

These two would be caused by a tar-fs bug.

Default uid/gid can be set to root

Can you clarify this?

AFAIK native package managers install files with their owner set to root. Otherwise we would have system files owned by a specific user, which is not good. It's nice we can override it using postinstall scripts but I'm not sure if it's the most convinient approach. Different defaults might possibly do the same job.

/usr/lib is used as a sensible default

I'm not sure it's a sensible default at all. For me that would be "/". But deboa might just pull it as another config option

AFAIK native package managers install files with their owner set to root.

By default, deboa already makes all files/folders owned by root:root (uid 0 / gid 0).

I'm not sure it's a sensible default at all. For me that would be "/".

It really depends on your use case. As per https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#shared-library-support-files:

It is recommended that supporting files and run-time support programs that do not need to be invoked manually by users, but are nevertheless required for the package to function, be placed (if they are binary) in a subdirectory of /usr/lib, preferably under /usr/lib/package-name.

I wrote deboa as a base for https://github.com/erikian/electron-deboa-maker, so defaulting to /usr/lib has that use case in mind. Sure, I could add an option to specify the root directory so users could install stuff to /some-directory instead of /usr/lib/some-directory. But then what if users want to install a file to the root directory (/some-file.sh)? Should there be an option for that too? As you can imagine, it can get complex really fast, so I think providing direct access to the directory structure is a superior option because users can change it to whatever they need and the code can be kept as simple as possible.

I don't think you can say than a deb package with lintian errors is a valid deb package.

By "valid", I mean dpkg is able to correctly parse the package, install it and run any maintainer scripts. Lintian is just a linter, and while it's certainly useful, it doesn't necessarily mean there will be any errors when installing the app if there's a lintian error. Not the best analogy, but consider Javascript bundling/minification by Webpack and a linter like ESLint. Would the bundled .js file pass ESLint without a lot of errors? Probably not. Does that file contain valid Javascript, in the sense that it can be interpreted by Node/Chrome? Absolutely.

Issues regarding changelog and copyright are not really specific to my use case. I don't provide them explicitly anywhere.

Could you share the directory structure you have?

By default, deboa already makes all files/folders owned by root:root (uid 0 / gid 0).

I don't think it's true. Otherwise I wouldn't have errors related to gid/uid (I use your basic JS example where no changes is made to gid/uid).
My directories are as follows:
my-awesome-app-linux-x64/
└── usr
    └── bin
        └── app.sh

*.desktop file for example is added by deboa automatically and still has id 1000

Sure, I could add an option to specify the root directory so users could install stuff to /some-directory instead of /usr/lib/some-directory. But then what if users want to install a file to the root directory (/some-file.sh)? Should there be an option for that too?

I don't really get the complexity of it. A file within an input directory would be handled the same way as inner dirs.

By "valid", I mean dpkg is able to correctly parse the package, install it and run any maintainer scripts.

My only objection to that would be that some GUI Linux Application Installers could have different requirements and might fail because of those deb inconsistencies. We can't know in advance if they will that's for sure

It really depends on your use case. As per https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#shared-library-support-files:
I could give you this link:
https://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/opt.html
/opt is used a lot for applications not included with the distribution itself. Multiple programs are installed there. That's why more flexibility could be useful

I don't think it's true. Otherwise I wouldn't have errors related to gid/uid (I use your basic JS example where no changes is made to gid/uid).

You're right, the control.tar and data.tar files themselves belong to root, not their contents. I've fixed this, thank you!

My only objection to that would be that some GUI Linux Application Installers could have different requirements and might fail because of those deb inconsistencies. We can't know in advance if they will that's for sure

That's fair, I've added the installationRoot option, so now you can specify where you want your app to live when it's installed (the default is still /usr/lib/${packageName}):
const deboa = new Deboa({
  installationRoot: '/opt',
  // ...other options
})

I've tested installationRoot and it works perfectly. Still getting 1000/1000 uid/gid though. A bug might be lurking somewhere

Do you mind sharing a sample .deb? Also, what OS are you using?

There are also lintian warnings that I haven't posted ever:
W: my-awesome-app: non-standard-dir-perm usr/ 0775 != 0755
N:
W: my-awesome-app: non-standard-dir-perm usr/bin/ 0775 != 0755
N:
W: my-awesome-app: non-standard-dir-perm usr/share/ 0775 != 0755
N:
W: my-awesome-app: non-standard-dir-perm usr/share/applications/ 0775 != 0755
N:
W: my-awesome-app: non-standard-file-perm usr/bin/app.sh 0664 != 0644

I'd like to know what is the supposed course of action here: writing custom JS code or some other setting

I installed your .deb on Ubuntu 22.04 and the file is owned by root as expected

That's good but the permissions within tar archive can still be broken

About the permissions, since you're on Unix, it's just copying over the permissions your files already have (I only set the permissions to 0644 / 0755 on Windows because it doesn't have chmod-style permissions).
You can either change the permissions of the files you're packaging or use the modifyTarHeader option to set them manually:
const deboa = new Deboa({
  modifyTarHeader: header => {
    switch (header.type) {
      case 'file': {
        header.mode = parseInt('0644', 8)
        break
      }

      case 'directory': {
        header.mode = parseInt('0755', 8)
        break
      }
    }

    return header
  },
  // ...other options
})

That's good but the permissions within tar archive can still be broken

I'll take another look, but I wouldn't be too worried about it since the file is being copied with the appropriate owner

Clear, thanks

Fixed in https://github.com/erikian/deboa/commit/9cb03efd90b40a3d587c521fb0760704ffe13a6d.
The uid/gid in the .tar archive were wrong as you suspected, now they're always set to 0 regardless of the current user's uid/gid. Lintian should be much happier now :smi


More concise way to get user email from git config

As title says.

@wfxr Thanks for your contribution!


feat: add price icon

References IN-2305
Motivation and context
We want to use Price icon for Price column in listing table header in vehicle pool.
Before

After

I am just not sure naming is correct, maybe ChfCurrencyIcon or something similar? Btw why do we need icon for this?

Yes, it sounds better and more appropriate. Thank you. :)
Well, I wanted to use it because of the consistency (I tried with a text but couldn't get the font and the width).
The plan is to reach this stage with listing table header.


Bump gidgethub from 5.0.1 to 5.1.0

Bumps gidgethub from 5.0.1 to 5.1.0.

Release notes
Sourced from gidgethub's releases.

5.1.0

Use X-Hub-Signature-256 header for webhook validation when available.
([PR #160](brettcannon/gidgethub#160)).

The documentation is now built using Sphinx v>= 4.0.0.
([Issue #143](brettcannon/gidgethub#143))

gidgethub.abc.GitHubAPI.getiter now accepts iterable_key parameter
in order to support the Checks API.
([Issue #164](brettcannon/gidgethub#164))

Accept HTTP 202 ACCEPTED as successful.
([PR #174](brettcannon/gidgethub#174))

Changelog
Sourced from gidgethub's changelog.

5.1.0

Use X-Hub-Signature-256 header for webhook validation when available.
(PR [#160](https://github.com/brettcannon/gidgethub/issues/160) <https://github.com/brettcannon/gidgethub/pull/160>_).

The documentation is now built using Sphinx v>= 4.0.0.
(Issue [#143](https://github.com/brettcannon/gidgethub/issues/143) <https://github.com/brettcannon/gidgethub/issues/143>_)

:meth:gidgethub.abc.GitHubAPI.getiter now accepts iterable_key parameter
in order to support the Checks API.
(Issue [#164](https://github.com/brettcannon/gidgethub/issues/164) <https://github.com/brettcannon/gidgethub/issues/164>_)

Accept HTTP 202 ACCEPTED as successful.
(PR [#174](https://github.com/brettcannon/gidgethub/issues/174) <https://github.com/brettcannon/gidgethub/pull/174>_)

Commits

313f06b Release v5.1.0
734ff53 Properly handle HTTP 202 ACCEPTED as successful (#174)
7f05154 Add the iterable_key parameter to getiter. (#170)
2a8f57f Start using Sphinx>=4.0 (#165)
48b5a76 Use X-Hub-Signature-256 for webhook validation (#160)
c05189d Upgrade to GitHub-native Dependabot (#163)
8b240f7 Test against Python 3.10 on GH Actions (#162)
b99a2e9 Change to main branch in GH Actions file (#161)
629b283 Update noxfile, test against Python 3.9 (#142)
80d769d Post release: bump the version to 5.0.1.dev (#158)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Codecov Report

Merging #393 (620d5da) into master (b49254c) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #393   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines         1298      1298
=========================================
  Hits          1298      1298


chore: update project ownership

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


weechatScripts.wee-slack: 2.4.0 -> 2.5.0

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Looks like this PR duplicates #83339
Could you check the other one (that brings some modifications) and select the one which is most adequate?

The other one is better.


3.1.0 pip release seems broken

Describe the bug
Cannot import charset_normalizer
To Reproduce
import charset_normalizer
Expected behavior
Successful import
Logs
>>> import charset_normalizer
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/<redacted>/anaconda3/envs/huggingface-bug-test/lib/python3.9/site-packages/charset_normalizer/__init__.py", line 23, in <module>
    from charset_normalizer.api import from_fp, from_path, from_bytes, normalize
  File "/<redacted>/anaconda3/envs/huggingface-bug-test/lib/python3.9/site-packages/charset_normalizer/api.py", line 10, in <module>
    from charset_normalizer.md import mess_ratio
  File "charset_normalizer/md.py", line 5, in <module>
ImportError: cannot import name 'COMMON_SAFE_ASCII_CHARACTERS' from 'charset_normalizer.constant' (/<redacted>/anaconda3/envs/huggingface-bug-test/lib/python3.9/site-packages/charset_normalizer/constant.py)

Desktop (please complete the following information):

OS: Linux
Python version 3.9.16
Package version 3.1.0

Additional context
Imports causing issues in other libraries.
https://github.com/huggingface/transformers/issues/21858#issuecomment-1480094049

I cannot reproduce—insufficient information.
It is most likely a problem within your environment.

The title speaks of pip but the given stack trace shows evidence of anaconda3.
I tried to set up environments based on conda v4 / anaconda3 and no exception occurred at import.
Tested on Linux with the exact same criteria.

If there is no reproducibility on my end, I consider it external.
So, in case of clear evidence that this package is causing (directly) that exception, I am willing to fix it (and reopen that issue). But I doubt it has anything to do with that.
p.s. I don't maintain the conda package charset-normalizer if anything happens to be there.

I cannot reproduce—insufficient information. It is most likely a problem within your environment.

The title speaks of pip but the given stack trace shows evidence of anaconda3.
I tried to set up environments based on conda v4 / anaconda3 and no exception occurred at import.
Tested on Linux with the exact same criteria.

If there is no reproducibility on my end, I consider it external. So, in case of clear evidence that this package is causing (directly) that exception, I am willing to fix it (and reopen that issue). But I doubt it has anything to do with that.
p.s. I don't maintain the conda package charset-normalizer if anything happens to be there.

# packages in environment at /cmlscratch/anisaha1/anaconda3/envs/huggingface-bug-test:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                        main
_openmp_mutex             5.1                       1_gnu
blas                      1.0                         mkl
brotlipy                  0.7.0           py39h27cfd23_1003
bzip2                     1.0.8                h7b6447c_0
ca-certificates           2023.01.10           h06a4308_0
certifi                   2022.12.7        py39h06a4308_0
cffi                      1.15.1           py39h5eee18b_3
charset-normalizer        3.1.0                    pypi_0    pypi
cryptography              39.0.1           py39h9ce1e76_0
cuda-cudart               11.7.99                       0    nvidia
cuda-cupti                11.7.101                      0    nvidia
cuda-libraries            11.7.1                        0    nvidia
cuda-nvrtc                11.7.99                       0    nvidia
cuda-nvtx                 11.7.91                       0    nvidia
cuda-runtime              11.7.1                        0    nvidia
ffmpeg                    4.3                  hf484d3e_0    pytorch
filelock                  3.10.0                   pypi_0    pypi
flit-core                 3.6.0              pyhd3eb1b0_0
freetype                  2.12.1               h4a9f257_0
giflib                    5.2.1                h5eee18b_3
gmp                       6.2.1                h295c915_3
gnutls                    3.6.15               he1e5248_0
huggingface-hub           0.13.3                   pypi_0    pypi
idna                      3.4              py39h06a4308_0
intel-openmp              2021.4.0          h06a4308_3561
jpeg                      9e                   h5eee18b_1
lame                      3.100                h7b6447c_0
lcms2                     2.12                 h3be6417_0
ld_impl_linux-64          2.38                 h1181459_1
lerc                      3.0                  h295c915_0
libcublas                 <IP_ADDRESS>                    0    nvidia
libcufft                  <IP_ADDRESS>           h4fbf590_0    nvidia
libcufile                 <IP_ADDRESS>                      0    nvidia
libcurand                 <IP_ADDRESS>                     0    nvidia
libcusolver               <IP_ADDRESS>                      0    nvidia
libcusparse               <IP_ADDRESS>                     0    nvidia                                                                                [17/59]
libdeflate                1.17                 h5eee18b_0
libffi                    3.4.2                h6a678d5_6
libgcc-ng                 11.2.0               h1234567_1
libgomp                   11.2.0               h1234567_1
libiconv                  1.16                 h7f8727e_2
libidn2                   2.3.2                h7f8727e_0
libnpp                    <IP_ADDRESS>                     0    nvidia
libnvjpeg                 <IP_ADDRESS>                      0    nvidia
libpng                    1.6.39               h5eee18b_0
libstdcxx-ng              11.2.0               h1234567_1
libtasn1                  4.16.0               h27cfd23_0
libtiff                   4.5.0                h6a678d5_2
libunistring              0.9.10               h27cfd23_0
libwebp                   1.2.4                h11a3e52_1
libwebp-base              1.2.4                h5eee18b_1
lz4-c                     1.9.4                h6a678d5_0
mkl                       2021.4.0           h06a4308_640
mkl-service               2.4.0            py39h7f8727e_0
mkl_fft                   1.3.1            py39hd3c417c_0
mkl_random                1.2.2            py39h51133e4_0
ncurses                   6.4                  h6a678d5_0
nettle                    3.7.3                hbbd107a_1
numpy                     1.24.2                   pypi_0    pypi
numpy-base                1.23.5           py39h31eccc5_0
openh264                  2.1.1                h4ff587b_0
openssl                   1.1.1t               h7f8727e_0
packaging                 23.0                     pypi_0    pypi
pillow                    9.4.0            py39h6a678d5_0
pip                       23.0.1           py39h06a4308_0
pycparser                 2.21               pyhd3eb1b0_0
pyopenssl                 23.0.0           py39h06a4308_0
pysocks                   1.7.1            py39h06a4308_0
python                    3.9.16               h7a1cb2a_2
pytorch                   1.13.1          py3.9_cuda11.7_cudnn8.5.0_0    pytorch
pytorch-cuda              11.7                 h778d358_3    pytorch
pytorch-mutex             1.0                        cuda    pytorch
pyyaml                    6.0                      pypi_0    pypi
readline                  8.2                  h5eee18b_0
regex                     2022.10.31               pypi_0    pypi
requests                  2.28.2                   pypi_0    pypi
setuptools                65.6.3           py39h06a4308_0
six                       1.16.0             pyhd3eb1b0_1
sqlite                    3.41.1               h5eee18b_0
tk                        8.6.12               h1ccaba5_0
tokenizers                0.13.2                   pypi_0    pypi
torchaudio                0.13.1               py39_cu117    pytorch
torchvision               0.14.1               py39_cu117    pytorch
tqdm                      4.65.0                   pypi_0    pypi
transformers              4.28.0.dev0              pypi_0    pypi
typing-extensions         4.5.0                    pypi_0    pypi
typing_extensions         4.4.0            py39h06a4308_0
tzdata                    2022g                h04d1e81_0
urllib3                   1.26.15                  pypi_0    pypi
wheel                     0.38.4           py39h06a4308_0
xz                        5.2.10               h5eee18b_1
zlib                      1.2.13               h5eee18b_0
zstd                      1.5.2                ha4553b6_0

Yes, it's a conda environment but the charset_normalizer installation is from the pypi channel. Also, the error seems to emanate from a missing chardet dependency. Once I install chardet with code pip install chardet, the problem gets solved.
So, do you think this is a dependency problem which needs to be fixed in charset_normalizer?

re
It is not because of that package.
My guess is that using pip in conda environment makes some confusion.
Yes, you have 3.1.0 installed, but for some reason, it is trying to import charset_normalizer.constant from the v2.0.4 (conda original depo) which does not have the constant COMMON_SAFE_ASCII_CHARACTERS in it.
You have literally a Frankenstein environment.

@Ousret you are right.
I installed charset-normalizer with conda
conda install conda-forge::charset-normalizer
and the problem was gone.


add registry for getting activations by name.

Codecov Report

Merging #10 (1830f39) into main (9c35ef2) will decrease coverage by 3.68%.
The diff coverage is 87.09%.

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
- Coverage   98.44%   94.76%   -3.69%
==========================================
  Files           8        9       +1
  Lines         129      191      +62
==========================================
+ Hits          127      181      +54
- Misses          2       10       +8

Impacted Files
Coverage Δ

src/hearth/_internals.py
76.47% <76.47%> (ø)

src/hearth/activations.py
100.00% <100.00%> (ø)

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 9c35ef2...1830f39. Read the comment docs.


PANIC after entering guest VM under riscv64 with arceos's "irq" feature enabled

When we enabled "irq" feature for hypervisor level IRQ, it won't work under RISCV64 currently.
# arceos-vmm/Cargo.toml

# System dependent modules provided by ArceOS.
axstd = { workspace = true, features = [
    "alloc",
    "paging",
    "fs",
    "irq", # It has to be disabed in riscv64. Todo: fix it.
    "hv",
    "multitask",
    # "sched_rr"
] }

command

make ARCH=riscv64 VM_CONFIGS=configs/nimbos-riscv64.toml run

phenomena

       d8888                            .d88888b.   .d8888b.
      d88888                           d88P" "Y88b d88P  Y88b
     d88P888                           888     888 Y88b.
    d88P 888 888d888  .d8888b  .d88b.  888     888  "Y888b.
   d88P  888 888P"   d88P"    d8P  Y8b 888     888     "Y88b.
  d88P   888 888<PHONE_NUMBER>8 888     888       "888
 d8888888888 888     Y88b.    Y8b.     Y88b. .d88P Y88b  d88P
d88P     888 888      "Y8888P  "Y8888   "Y88888P"   "Y8888P"

arch = riscv64
platform = riscv64-qemu-virt
target = riscv64gc-unknown-none-elf
smp = 1
build_mode = release
log_level = warn

[  0.154169 0 fatfs::dir:139] Is a directory
[  0.172770 0 fatfs::dir:139] Is a directory
[  0.193889 0 fatfs::dir:139] Is a directory
[  0.215718 0 fatfs::dir:139] Is a directory
[  0.338912 0:5 axruntime::lang_items:5] panicked at /home/hky/.cargo/git/checkouts/riscv_vcpu-0ecce50bd3948e2b/e3c9929/src/vcpu.rs:499:17:
Unhandled trap: Exception(InstructionPageFault), sepc: 0x90200000, stval: 0x90200000

It may take some time to fix this bug. Because if irq is enabled, clock interrupts will be involved. Since the virtual machine timer interrupt and arceos timer interrupt in riscv cannot be distinguished, timerlist is needed to help judge. However, the current timer design has not yet been added to the main line, so this problem can only be fixed after the timer design is added to the main line.

Now during vmexit the relevant interrupts are disabled to support the enable irq function.Related PR: https://github.com/arceos-hypervisor/riscv_vcpu/pull/12


exe file

If a package contains a number of dlls only then there is no exe file to run. But it seems unfurl cannot be set to not run an exe file?

I fixed by adding a dummy.exe file to the zip file


Corrected the date on the PL release notes.

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[X] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s) (none)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-722