Fixed short links and table bug in the RU documentation file

Links had wrong path, changed to the correct one.
The table bug was just a typo kind thing.

Hi @xk0fe
Thank you for your PR, but an earlier PR https://github.com/freeCodeCamp/freeCodeCamp/pull/35140 (which has not been merged yet) has the same changes to the same file yor changed.  We are going to close this as a duplicate.
If you feel you have more to add, please feel free to open up a new PR.
Thanks again! 😊

If you have any questions, feel free to reach out through Gitter or by commenting below. 💬


How can i add a submit button and send all the form values?

`_onChange = (formData) => console.log(JSON.stringify(formData, null, ' '))

`
Console gives `undefined```

For me, I added setState to formdata on _onChange so that I can receive all the data upon completion


[Test Hook] Need the ability to clear the new lazy cache values for environment values #110

Codecov Report

Merging #111 (c4a1724) into main (9a935e9) will not change coverage.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #111   +/-   ##
=======================================
  Coverage   98.76%   98.76%
=======================================
  Files          62       62
  Lines         971      971
  Branches      195      195
=======================================
  Hits          959      959
  Misses         12       12

Impacted Files
Coverage Δ

lib/src/helpers/environment.ts
94.11% <100.00%> (ø)

lib/src/helpers/perf.ts
100.00% <100.00%> (ø)


Update README.md to correct Homebrew command

Homebrew removed the cask subcommand in favor of a flag to install, just updated the readme to reflect this...

Duplicate of #53.


at42qt1070: Additional functionality

This patch series adds some additional functionality to the at42qt1070 touch sensor.
It allows the user to read and change the low-power mode settings, the averaging factor and the adjacent key suppression groups.
It also allows the user to read the Chip ID register and does so in the constructor, as a sanity check.
Tested on Intel Edison on Xadow with a Xadow Q Touch sensor.

@Propanu can this get merged?

Merged, thanks a lot!


bug(Chips): Screen reader does not announce proper selected state when multiselect enabled

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When using Chips component that allows multiple options to be selected, screen reader does not announce the state correctly and causes confusion for customers. Without multiple attribute screen reader announces the "selected/not selected" state as expected.
Reproduction
Steps to reproduce:

Open basic example from the Chips doc:

Add multiple attribute to mat-chip-listbox to allow multiselect.

<mat-chip-listbox multiple aria-label="Fish selection">
  <mat-chip-option>One fish</mat-chip-option>
  <mat-chip-option>Two fish</mat-chip-option>
  <mat-chip-option color="accent" selected>Accent fish</mat-chip-option>
  <mat-chip-option color="warn">Warn fish</mat-chip-option>
</mat-chip-listbox>

Turn on a screen reader and navigate between chip options.

Expected Behavior
When multiselect enabled, when clicking/tabing on a chip, screen reader announces:

(when option selected) "{label} selected"
(when option not selected) "{label} not selected"

Actual Behavior
When multiselect enabled, when clicking/tabing on a chip, screen reader announces:
On MacOS + VoiceOver:

(when option selected) "{label} selected, selected"
(when option not selected) "{label} not selected, selected"

On Linux + Orca:

(when option selected) "{label}"
(when option not selected) "{label} not selected"

Environment
Not a custom env, able to reproduce in basic example on StackBlitz in Chrome:

This seems fine for MacOS + VoiceOver, since the correct state is being read aloud. I'm closing this bug because we don't support Orca.

Hey @amysorto, thanks for posting the list of supported tools.
Regarding MacOS + Chrome - are you saying that the current way SR announces state ("not selected, selected") is expected? Isn't it confusing?


Backport of #2602

Backport of #2602

Codecov Report

Merging #2604 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2604   +/-   ##
=======================================
  Coverage   27.32%   27.32%
=======================================
  Files          86       86
  Lines       17143    17143
=======================================
  Hits         4684     4684
  Misses      11781    11781
  Partials      678      678

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 339d7de...c9430b2. Read the comment docs.

Currently there is an issue in v39 which needs to be fixed before merging

@daviian what issue?

@lafriks https://github.com/daviian/gitea/blob/c9430b29a5220e2297aa9b93b70a25062f831509/models/migrations/v39.go#L73
Xorm doesn't return anything here, despite there should be 96 units in my testdata with UnitTypeIssue

Any chance to see an automated test for migration from a dump of a Gogs0.99 database ?

@strk not in the scope of this PR but otherwise I agree we would need that but I currently have no idea how to achieve that

Trusted/untested LGTM - please make sure to manually test it !

@strk me and @daviian have tested it multiple times

Just tried this on a database with version=17 and it appears to have worked (raspberry pi zero w, had to change swap size to 1024mb to compile)!
# Make errors about go-bindata go away
go get github.com/jteeuwen/go-bindata
cd $GOPATH/src/github.com/jteeuwen/go-bindata/go-bindata
go build
export PATH=$PATH:$GOPATH/src/github.com/jteeuwen/go-bindata/go-bindata

# Get gitea
go get -d -u code.gitea.io/gitea
cd $GOPATH/src/code.gitea.io/gitea

# Get PR 2604 that fixes migration issues
git fetch origin pull/2604/head:pr-2604
git checkout pr-2604

# Build gitea (will take some time)
TAGS="bindata sqlite" make generate build

I kind of followed https://docs.gitea.io/en-us/install-from-source/ and https://docs.gitea.io/en-us/upgrade-from-gogs/ and @lafriks told me to change the gogs.db with the following SQL command: update version set version=14; which may or may not have contributed...

@mrexodia Glad to here that 😃 Setting the version to 14 is necessary as otherwise required migrations (in your example 14 to 17) are not applied to the database.

LGTM, code looks good, trusting manual tests of @lafriks & @daviian

Make LG-TM work again

@lunny @lafriks Should I create a backport to 1.2?

@daviian sure, go ahead


Redis trigger spec

Adding the redis trigger to the new documentation location.

Thank you!

Relates to #299


dhcp: patch up static leases with missing prefix

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
When tracking DHCPv6 manually you can set suffix addresses and DHCPv6/RADVD completes them, but Unbound and Dnsmasq do not.
While here it would make sense to create an iterator to get rid of all the duplication in the code for IPv4 and IPv6 staticmap handling.
To Reproduce
See forum link.
Expected behavior
Patch up addresses in the manual tracking case but do not solve the changing prefix issue.
Screenshots
N/A
Relevant log files
N?A
Additional context
https://forum.opnsense.org/index.php?topic=21108.0
https://github.com/opnsense/core/issues/2544
Environment
Most.

Isn't that a duplicate of #3657? Don't get me wrong, I would appreciate a solution, but am a bit surprised about the sudden change of mind.

Isn't that a duplicate of #3657? Don't get me wrong, I would appreciate a solution, but am a bit surprised about the sudden change of mind.

Yes, looks like it. I switched jobs in January to work on OPNsense full time so this is more of a reachable scope now.

Yes, looks like it. I switched jobs in January to work on OPNsense full time so this is more of a reachable scope now.

PR at https://github.com/opnsense/core/pull/4723

d0822b006785be56d3cad925e5f5f04c63de1d9e + e73db9c7aef5cfaf63e1c23637dafa29885ae58b seems to fix it for DHCPv6 + Unbound. 👍
Didn't test dnsmasq, didn't test DHCPv4.
Following up on my comment at d0822b006785be56d3cad925e5f5f04c63de1d9e:
Would be nice to have the full addresses in status_dhcpv6_leases.php, too. Not a functional issue, just a cosmetic one.
While at it, can we avoid restarting radvd every time the dhcpd6 config changes? It's a long standing issue which causes the entire network to go down briefly when you e.g. add a static mapping. I guess we'd have to find out whether this entanglement is actually required or purely historic.

Hmm, the code was pretty bad, it should have checked for ipaddrv6:
https://github.com/opnsense/core/commit/db29e02ecbfded6298da2c01b444a3ce01ebd264#diff-892d19c546842230914680258f3f81046a0d541c8f0196bd82a1dbe628c3c82bL461
Anyway, db29e02 should be an improvement on the leases page. That's half of your requests done :)

Did a quick test and it's looking good, thanks!

We could pull the radvd reconfiguration from the main restart sequence and start it one layer up manually after dhcp reconfiguration. The resulting commit would be enough to discuss which calls need to stay and which need to be removed, ok?

@fichtner - please join our discussion on #4768

@fichtner Sounds good to me!

@maurice-w can you have a look at 012e0f7f11f0f62 ? Slightly different approach, see commit message

Definitely an improvement. Changing DHCP settings doesn't restart radvd anymore. 👍
The only side effect I've noticed so far: If Use the DNS settings of the DHCPv6 server is enabled in the RA settings, changing the DHCPv6 DNS servers now requires a manual radvd restart to update RDNSS in radvd.conf. No surprise.
Applying Unbound configuration changes also triggers a radvd restart - probably because of possible RDNSS changes, too. Maybe we could restart radvd only if RDNSS actually changes?

There is a likely issue with the v6 leases page now expecting an IP address and a hostname so static leases may not show up. The question is what should be mandatory for static leases and what can we fill out  from the lease page add button.
IPv6 also not merging system leases and static leases. What is their respective lookup key.. the IP address or DUID or a combination?
Reference: https://forum.opnsense.org/index.php?topic=22742.0

Hm, the bug report on the forum is a bit hard to follow...
Static mappings without a hostname don't show up on the leases page? Possible, I never tested this.

The question is what should be mandatory for static leases and what can we fill out from the lease page add button.

Technically, a static mapping only requires a DUID and an IP address. Some DHCPv6 servers (e.g. Microsoft) won't allow reservations without a hostname though, so making this mandatory might be acceptable. For converting dynamic leases to static mappings, we should grab DUID + IP address + hostname from the leases page. Isn't that the case? Never really used that feature.

IPv6 also not merging system leases and static leases. What is their respective lookup key.. the IP address or DUID or a combination?

Sorry, I don't understand. Could you elaborate? Unless this is just a "note to self". :-)

All code for this issue is now in 21.1.6 and we are almost there. One small regression reported with Unbound waiting for confirmation:
https://forum.opnsense.org/index.php?topic=23304.0

IPv6 also not merging system leases and static leases. What is their respective lookup key.. the IP address or DUID or a combination?
Sorry, I don't understand. Could you elaborate? Unless this is just a "note to self". :-)

yes, IPv6 leases page is a little weird still... otherwise I think we are set for 21.7.

@maurice-w I'm following your suggestion to make the IP mandatory for static lease consumers. For DHCP registration in DNS obviously we need to double-check for the hostname otherwise there is nothing to register. DHCPv6 leases page now merges static entries on DUID match and the DHCPv4 leases page will also use dhcpd_staticmap() which brings this particular saga to a happy end.
@marjohn56 @maurice-w Thanks for all the help!
Cheers,
Franco


Pandas KeyError

Hi! Your recent paper is great! Phase variation is such a cool topic, glad it's getting some attention in host-associated communities. I'm excited to apply your PhaseFinder program on some genomes I have that aren't publicly available, but have run into a problem. I followed the installation instructions and took care of the dependencies, but I get this error when running the program on a Mac OSX 10.14.3:
| => python PhaseFinder.py ratio -i ./wkB2/wkB2.ID.fasta -1 ./wkB2/reads/wkB2_R1.fastq.paired.fq -2 ./wkB2/reads/wkB2_R2.fastq.paired.fq -p 16 -o ./wkB2/out
****** NOW RUNNING COMMAND ******:
bowtie -p 16  -a --best --strata ./wkB2/wkB2.ID.fasta -1 ./wkB2/reads/wkB2_R1.fastq.paired.fq -2 ./wkB2/reads/wkB2_R2.fastq.paired.fq -S|    samtools view -@ 16 -F 4 -h  |sam2bed -d|sortBed |cut -f 1-4,7 > ./wkB2/out.bed
reads processed: 26028097
reads with at least one reported alignment: 155613 (0.60%)
reads that failed to align: 25872484 (99.40%)
Reported 379312 paired-end alignments
Total time:  6.966 mins
****** NOW RUNNING COMMAND *****:
awk -v out=./wkB2/wkB2.ID.fasta.info.tab 'BEGIN{OFS="\t"}{print $1"_F",$2,$3,$4,$5"\n"$1"_R",$2,$3,$4,$5 > out".bed";print $1"_F", $6 "\n" $1"_R",$6 > out".info" }'  ./wkB2/wkB2.ID.fasta.info.tab
awk '{print $1"\t"$2"\t"$3"\t1\n"$1"\t"$4"\t"$5"\t1\n"$1"\t"$2"\t"$5"\t-1"}' ./wkB2/wkB2.ID.fasta.info.tab.bed |slopBed -b 10 -g ./wkB2/wkB2.ID.fasta.info.tab.info |    sortBed|intersectBed -c -f 1 -a - -b ./wkB2/out.bed |awk '{a[$1]+=$4$5}END{for(i in a){print i"\t"a[i]}}'|sort -k1,1|sed 's/_F\t/\tF\t/;s/_R\t/\tR\t/' >./wkB2/out.span.count
Total time:  .016 mins
****** NOW RUNNING COMMAND ******:
cat ./wkB2/out.bed|awk 'BEGIN{OFS="\t"}{print $4,$5,$1}'|sed 's/_(.)$/\t\1/g'|awk '{if(and(64,$2)){P=1}else{P=2};print $1"\t"P"\t"$3"\t"$4}' > ./wkB2/out.tab
cut -f 1-3 ./wkB2/out.tab|sort|uniq -u|fgrep -f - ./wkB2/out.tab|cut -f 3-4|sort|uniq -c|awk '{print $2"\t"$3"\t"$1}' >./wkB2/out.pe.count
fgrep: -: No such file or directory
Total time:  .333 mins
PhaseFinder.py:190: FutureWarning: read_table is deprecated, use read_csv instead.
df = pd.read_table(infile, sep="\t", names=("ID", "dir", "count"))
Traceback (most recent call last):
File "PhaseFinder.py", line 412, in
args.func(args)
File "PhaseFinder.py", line 238, in pipeline_align
"Pe_F": dfmerge["F_x"].astype(int),
File "/usr/local/lib/python2.7/site-packages/pandas/core/frame.py", line 2927, in getitem
indexer = self.columns.get_loc(key)
File "/usr/local/lib/python2.7/site-packages/pandas/core/indexes/base.py", line 2658, in get_loc
return self._engine.get_loc(self._maybe_cast_indexer(key))
File "pandas/_libs/index.pyx", line 108, in pandas._libs.index.IndexEngine.get_loc
File "pandas/_libs/index.pyx", line 132, in pandas._libs.index.IndexEngine.get_loc
File "pandas/_libs/hashtable_class_helper.pxi", line 1601, in pandas._libs.hashtable.PyObjectHashTable.get_item
File "pandas/_libs/hashtable_class_helper.pxi", line 1608, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'F_x'
I have python2.7 and pandas installed:
Package         Version

biopython       1.73
nose            1.3.7
numpy           1.15.4
pandas          0.24.1
pip             18.0
python-dateutil 2.8.0
pytz            2018.9
scipy           1.1.0
setuptools      40.4.3
six             1.12.0
wheel           0.32.0
Finally, why do you use bowtie instead of bowtie2? When I try mapping to the simulated inverted repeats with bowtie2 by hand, I get much higher mapping %.
Thanks for your time!

Based on the error message "fgrep: -: No such file or directory", it seems that you have run PhaseFinder on Mac OS. Please try to run it on linux. or you can try to run the command line separately.
The reason we chose bowtie rather than bowtie2 is because bowtie2 allow for gapped alignment, which is what we don't want, especially in the context of metagenomic read alignment.

Great! I fixed this a while back, I downloaded the gnu versions of sed /
awk etc using homebrew. it worked fine on my Mac after that. Thanks so much!
On Mon, Apr 1, 2019 at 2:00 PM XiaofangJ<EMAIL_ADDRESS>wrote:

Based on the error message "fgrep: -: No such file or directory", it seems
that you have run PhaseFinder on Mac OS. Please try to run it on linux. or
you can try to run the command line separately.
The reason we chose bowtie rather than bowtie2 is because bowtie2 allow
for gapped alignment, which is what we don't want, especially in the
context of metagenomic read alignment.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/XiaofangJ/PhaseFinder/issues/1#issuecomment-478703553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AECiCP3USjOhD3Nt1zyNnr-1jIsReNbqks5vcldWgaJpZM4bQtIh
.

all fixed, I'm closing.


Modular version

Hello!
Would you be able to create a modular version using module-info.java?
We are trying to create a jpackage installer, but it isn’t working due to compatibility issues with Circe.
Your help would be greatly appreciated!
Best,
Serge

I see another request https://github.com/circe/circe/issues/2318


Activate county type selection (Fixes #354)

can you add new screenshot?

selecting all counties doesn't work for urban vs rural.


Fix pget permission denied error by using XDG_RUNTIME_DIR for pid file

This pull request addresses the issue of the pget tool encountering a permission denied error when trying to access /run/pget.pid, which required root privileges to run. The error caused inconvenience during testing and usage of the tool.
The changes in this PR introduce a new method _run_pget in both weights_downloader.py and weights_manifest.py to handle the pget command execution and error handling. The method captures the output of the subprocess and checks for the "permission denied" error message. If the error is encountered, it attempts to retry the command using the --pid-file flag, specifying an alternative location for the pid file.
The alternative location for the pid file is determined using the following logic:

If the XDG_RUNTIME_DIR environment variable is set, it is used as the directory for the pid file.
If XDG_RUNTIME_DIR is not set or is not writable, the user's home directory (~) is used as a fallback.

The _run_pget method constructs the new command arguments with the --pid-file flag and the determined pid file location. It then attempts to run the command with the new arguments. If the retry fails, the method raises the exception for proper error handling.
The existing calls to subprocess.check_call in the download method of weights_downloader.py and the _download_updated_weights_manifest method of weights_manifest.py have been replaced with calls to the new _run_pget method.
These changes ensure that the pget tool can be run without requiring root privileges by using an alternative location for the pid file, preferably XDG_RUNTIME_DIR if available.
Detailed changes:

Added _run_pget method in weights_downloader.py and weights_manifest.py to handle pget command execution and error handling.
Modified the download method in weights_downloader.py and the _download_updated_weights_manifest method in weights_manifest.py to use self._run_pget instead of subprocess.check_call.

This pull request should resolve the permission denied error encountered when running the pget tool, providing a better user experience and eliminating the need for root privileges.
Lmk if you have any feedback or suggestions for improvement

@zsxkib Could you abstract the repeated pget bit into a separate module?

Not sure what you mean?
Like make a pget wrapper in python so that the logic is abstracted away?

Closing for now.


Edit CrashReporting/AddStackToCrashReports.md

@sulekhark Does this change look good to you?

Yes, it looks good to me. Thank you!

@dandclark I needed to make a minor edit. I'm not able to add reviewers to the PR. PTAL

Thank you both!


fix(datetimepicker): disable apply button when absolute value is emtpy

Closes #3474
Summary

When switching from preset to relative and then absolute, the Apply button is enabled when no date is selected.

Change List (commits, features, bugs, etc)

added a check for absolute value

Acceptance Test (how to verify the PR)

Go to Default story
Click on Custom Range
Click on Absolute
check Apply button is disabled

Regression Test (how to make sure this PR doesn't break old functionality)

tests here

Things to look for during review

[ ] Make sure all references to iot or bx class prefix is using the prefix variable
[ ] (React) All major areas have a data-testid attribute. New test ids should have test written to ensure they are not changed or removed.
[ ] UI should be checked in RTL mode to ensure the proper handling of layout and text.
[ ] All strings should be translatable.
[ ] The code should pass a11y scans (The storybook a11y knob should show no violations). New components should have a11y test written.
[ ] Unit test should be written and should have a coverage of 90% or higher in all areas.
[ ] All components should be passing visual regression test. For new styles or components either a visual regression test should be written for all permutations or the base image updated.
[ ] Changes or new components should either write new or update existing documentation.
[ ] PR should link and close out an existing issue

When I am in this story and I clear out the value I am not seeing the button getting disabled.

When I am in this story and I clear out the value I am not seeing the button getting disabled.

@jessieyan, There has been no response to this comment.

When I am in this story and I clear out the value I am not seeing the button getting disabled.

@jessieyan, There has been no response to this comment.

Sorry I missed the comment. It should be fixed by adding a check on the empty time value.


Option with value 0 not showing.

When setting the the mulitselect value it does not display the selected value if it is 0. The model is correctly bound but for display purposes it is not working when I believe it should especially when the default is 0, this triggers the user to try and select it again.
Version
2.1.0 - CDN version as per Getting started guide
Steps to reproduce
<multiselect v-model="numberOfChildren"  :multiple="false" :close-on-select="true" placeholder="Number of Children" :options="numberOfChildrenOptions">                             </multiselect>
vue data property:
data: {     numberOfChildrenOptions: [0,1,2,3,4,5,6,7,8,9,10],     numberOfChildren: 0 }
Expected behaviour
The drop down will display '0'
Actual behaviour
The drop down display is empty.

I'd like to reopen this issue, because I still have the same problem...

Same here, I believe it's a genuine bug


Support for Gnome 40

Support for Gnome 40 incl. preferences
dropped support for older Gnome versions since prefs now use GTK4

@sluedecke
I tried your patch. It seemed to update the files in the correct location:
<EMAIL_ADDRESS>But after reloading, and even rebooting I am still not able to configure it without errors:

Thanks for your contribution. Please see the status update in #61.

yo @sluedecke
any ideas on getting settings to work here again? we're now moving ahead onto gnome 42.4, and options no longer show up

@mikoducky I tried this as well, I'm on 22.04 now and the default version stopped working. So I used the code here to make it work again.
One thing: I edited the version in the list of versions to add "42" and it worked. My gnome shell says I'm in "42.5" but it looks like "42" was sufficient.
Edit metadata.json and change the version:
"shell-version":
  "3.18",
  "3.28",
  "42"
],


Add Chinese and language switching

Now, you can switch between Chinese and English using the language switch button in the upper right corner

Now, you can switch between Chinese and English using the language switch button in the upper right corner

Thanks 😊

现在，您可以使用右上角的语言切换按钮在中文和英文之间切换

谢谢 😊
😁

Now, you can switch between Chinese and English using the language switch button in the upper right corner

Thanks 😊

😁


Display compatible custom resources when editing a Resource property in the inspector

Fixes #31591
When the user adds a custom resource via a GDScript plugin, their resource will now be displayed in the pop up menu when editing a compatible Resource property.
One limitation of my solution however is that it does not display children of custom resources. The solution I have in mind for that issue is a bit messy: find children of each custom type already found, and then find their children until no more children are found.
I'm actually not sure how to make a custom resource that derives from another custom resource through a GDScript plugin, so I can't set up a test project right now. If anyone knows how, I'd appreciate some guidance.

I rebased recently, and it's still working!

I spoke a little too soon. After some testing, I found out that although compatible resources appear in the list, they do not instance yet. I'll turn this PR into a draft instead and continue working on it.

My current solution works on the 3.2 branch, but now an error message is printed when a custom resource is instantiated through the inspector.
" Cannot get class 'CustomResource'. "
This error is not printed when instantiating a custom resource through the file system.
I'm having difficulties testing this on the 4.0 branch due to its instability, but I'm certain my solution isn't working there. I'm able to instance a custom type with this function:
obj = EditorNode::get_editor_data().instance_custom_type(intype, b);

But it must not be what I think it is, because it cannot cast to Resource:
Resource *resp = Object::cast_to<Resource>(obj); //cast fails, and thus resp is null
ERR_BREAK(!resp);

Hopefully I can figure it out after some debugging.

I got it working on 3.2 without errors! There is however one edge case I've found. Some resources have sub-resources, like materials in meshes for example. For some reason, the base_type is in reverse order for sub-resources, meaning I can't use get_slice() to reliably get the base type, and thus can't reliably instance the custom resource.

I fixed my edge case by not using get_slice(). Now, I record what base resource the custom resource inherits and instance that directly. If this passes the checks, I'll rebase and make this ready to review.

I rebased recently, and have moved functionality to the new EditorResourcePicker class. Although I can successfully populate the menu with the appropriate items, I can not instantiate them without crashing the editor. It looks like #48201 fixes the crash I'm experiencing, but my PR will likely need to be updated again once #48201 is merged.

This seems closely related to #48201 and related PRs, CC @willnationsdev. I'm assuming it might be superseded by some of the newer/recently updated PRs but it would be good to check.

I believe this was superseded by #62413, and the linked issue has already been resolved.

Superseded by https://github.com/godotengine/godot/pull/62413. Thanks for the contribution nonetheless!


Django 1.8 support

Update tox.ini
Fix RemovedInDjango19Warning: "requires_model_validation" is deprecated in favor of "requires_system_checks".

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Coverage remained the same at 29.56% when pulling 6bf64ae7ac1654794947458c009c2e77f562f9a8 on jpadilla:master into 2a058ef5b88694bf210b7c22ce7fd7d44dd92686 on django-extensions:master.

Thanks !

:+1: , please, some warnings with django 1.9


rdfs:seeAlso resources

=== This issue was migrated from JIRA ===
Type: New Feature
Priority: Major
Status: Open
Resolution: Unresolved
Reported by: Robert Cooper
Assigned to: Robert Cooper
Created: Fri Apr 01 22:12:49 CEST 2011
Updated: Fri Apr 01 22:12:49 CEST 2011
JIRA Link: https://rometools.jira.com/browse/MODULES-4
=========================================
Hi,
I'd like to create a feed containing something like this:
<rss:item rdf:about="#foo">
       ...
       <rdfs:seeAlso rdf:resource="http://sun.com/"/>
       ...
</rss:item>
I've only seen String, List (of Strings) and Dates as
data types.  Is it possible to add a URI and have the
URI serialised as in the example above?
Best regards,
Andreas.

Moved this issue to https://github.com/rometools/rome/issues/238 as part of https://github.com/rometools/rome/issues/217


return position from find functions

Currently, the leave the $~json.at value pointed to the specified value, but I think it will be more flexible to just return that value.

closed via 88b827b1de246b1b14e2b70890856381f7cfa34a


Add/use slab-bump allocator?

The basic idea is, you have slabs of some size.
When you run out of memory, you allocate a new slab.
Examples:
llvm: https://llvm.org/doxygen/Allocator_8h_source.html
LoopModels: https://github.com/JuliaSIMD/LoopModels/blob/bumprealloc/include/Utilities/Allocators.hpp
LoopModel's is largely a copy of LLVM's, but supports either a bump-up or bump-down.
LoopModel's slab size is constant, but LLVM's slabs grow.
A julia struct itself could look like
mutable struct BumpAlloc{Up,SlabSize}
    current::Ptr{Cvoid}
    slabend::Ptr{Cvoid}
    # you could try and get fancy and reduce the number of indirection's by having your own array type
    slabs::Vector{Ptr{Cvoid}}
    custom_slabs::Vector{Ptr{Cvoid}}
end
# should probably register a finalizer that `Libc.free`s all the pointers
# optionally use a faster library like `mimalloc` instead of `Libc`

The custom_slabs are for objects too big for the SlabSize.
The point of being separate was largely because in C++ there possibly are possibly faster free/delete functions that take the size (i.e. there might exist, and they might be faster).
Given that we don't have that here, we may as well fuse them, unless you find some allocator API that supports sizes.
Being able to grow lets you default to a much smaller slab size.
I was thinking about modifying SimpleChains to use something like this.

Yeah that'd be great to have here. It definitely should be the default.

I guess overcommiting with mmap may be an even better idea?
julia> Sys.total_memory() / 1<<30
15.319782257080078

julia> Sys.free_memory() / 1<<30
10.188095092773438

julia> using Mmap

julia> x = Mmap.mmap(Vector{UInt8}, Sys.total_physical_memory() + 1<<30); # mmap 1 more gig than total memory

julia> Sys.free_memory() / 1<<30
10.179462432861328

I think this might not work on Windows, but you could maybe pick a little bit less than the total memory.
Basically, the OS gives you as much as you ask for, without actually mapping any particular page to physical memory until you touch it.
So this is better than the slab approach in some sense.
You'll page fault when you hit a new page (but your allocator for the slab has that problem too!), and then the OS gives it to you.
This makes partial resets easier/more efficient.

Hm, that's a really interesting approach. Is this what our GC is doing under the hood too?

I think it's the primary way programs get memory from the OS, e.g. mallocs will mmap memory under the hood.
I haven't looked into how Julia's GC is implemented, but would guess so.
Searching the source code you can find plenty of mmap (aka VirtualAlloc on Windows), e.g. https://github.com/JuliaLang/julia/blob/406ba123cedcfcc66cb50d15bb5eaeb2bcefea5b/src/cgmemmgr.cpp#L38
Also, Vectors in Julia stop copying memory/relocating over a certain size; the OS will just start paging in more memory as needed. I also haven't looked into how that is implemented, but would definitely guess it is using mmap.
Here's a blogpost where someone talks about it in more detail:
https://yakubin.com/notes/comp/reserve-and-commit.html
Julia already takes care of the messiest bits in the Mmap standard library (i.e. it is cross platform), and Julia gives you access to total_memory so you can avoid overcomitting (which can be disabled on Linux, and doesn't work on Windows). It's nice to know what the total memory is so that you can safely undershoot it.
A bit off topic (but on the topic of bump allocators), but I liked this blog post describing arenas and the author's memory management strategy in C (which was more or less what I've also started doing recently):
https://www.rfleury.com/p/untangling-lifetimes-the-arena-allocator
For certain data structures, it's easy to reason about and very fast.
I think partial deallocations so that each arena/bump allocator can work like a stack where you push things to it and pop them off is important.
Although simple enough use cases like SimpleChains doesn't really need that functionality.

@chriselrod turns out that you don't even need mmap for this. A regular undef array will do.
julia> Sys.free_memory() / 1e9
12.138631168

julia> x = Vector{UInt8}(undef, Sys.total_physical_memory());

julia> Sys.free_memory() / 1e9
12.127961088

julia> x[1:end÷4] .= 1;

julia> Sys.free_memory() / 1e9
7.952367616


Date read incorrectly

3/8/2020  5:01:00 AM is read as 3/8/2020  5:00:50 AM Indian Standard Time. There is an issue while reading the date from India timezone.

Test.xlsx
Use the attachment for testing purpose, losing 10 seconds on each timestamp.

@SheetJSDev important issue!
Same problem in my case with GMT+3 timezone, where 24 seconds are lost. In my case the import of date data type is a must, so if this problem won't be solved quickly, I'll have to change the library used for this functionality. I updated to the last 0.16 version and nothing changed. Any thoughts?

related https://github.com/SheetJS/sheetjs/issues/2196

https://github.com/SheetJS/sheetjs/issues/2304#issuecomment-916707320
Please follow https://github.com/SheetJS/sheetjs/issues/1565 for updates


Build error during preLaunchTask 'build'.

Whenever I press F5 to debug an RC2 ASP.Net app, I get the following error in a bar along the top:
Build error has been detected during preLaunchTask 'build'.

with a 'Debug Anyway' and 'Close' option.
I encounter the issue every time.
Build outputs associated with this:
Project Project.Omega (.NETCoreApp,Version=v1.0) will be compiled because Input items removed from last build
Compiling Project.Omega for .NETCoreApp,Version=v1.0
Compilation succeeded.
    0 Warning(s)
    0 Error(s)
Time elapsed 00:00:01.3013499

Project Project.Omega (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.

VS Code:
[Window Title]
Visual Studio Code - Insiders

[Main Instruction]
Visual Studio Code - Insiders

[Content]

Version 1.1.0-insider
Commit c212f0908f3d29933317bbc3233568fbca7944b1
Date 2016-05-09T13:09:51.092Z
Shell 0.37.6
Renderer 49.0.2623.75
Node 5.10.0

omnisharp-vscode package: csharp-1.0.5-rc2.vsix
In the project, I'm using Microsoft.NETCore.App version 1.0.0-rc2-3002700.
Debug Anyway works, but it's a pain to have to click that every time.

Strangely enough, the issue stopped when I selected the (web) configuration in the debug tab, and I haven't been able to replicate it since.

I just ran into this myself. Changing the launch configuration didn't help for me though, restarting VS Code made the issue go away.

If you run into this on Windows, please try using Process Monitor to check the exit from dotnet.exe. Then we can know if this is a bug in VS Code (they are claiming the task failed for no reason), or a bug in the .NET CLI (they are exiting with non-zero exit code on success).

I'm hitting the same issue. dotnet.exe is returning with exit code 0 according to Process Monitor.

@mellinoe if you go to 'View->Errors and Warnings' does VS Code show you any errors?
This sounds like it might be -
https://github.com/Microsoft/vscode/issues/4987

Looks like there is another active issue that also sounds the same: https://github.com/Microsoft/vscode/issues/4070

Hm, I'm not able to get a repro at this exact moment. If I hit this again i will check that panel.

I had the same issue on OSX. Restarted after updating C# extension and the asset installtion and it went away

Has anyone seen this in awhile? It feels like this issue might be a bit stale.

I have seen this issue with this repro https://github.com/OmniSharp/omnisharp-vscode/issues/352

@rajkumar42 this bug tracks the scenario where VS Code claims that the build fails, but it actually succeeded. Is that what you saw?

This behavior shows up on Windows only. In my case the build actually failed, it did not update the dlls.
Its quiet different on mac, where it somehow creates a zero sized file.

Is this still a problem?

I'm having the exact same problem with version 1.10.2 ;(

Same goes here.

@damtur and @cihadsevim what OSs are you guys on? What version of VS Code do you have?

@gregg-miskelly Windows 8

@cihadsevim can you repro this problem regularly? If so, could you try running procmon to verify that indeed dotnet (or whatever process you are using to build with if you have something else configured) is returning a non-zero exit code? You should be able to get back speed by disabling almost all events in procmon and enabling the option to drop filtered out events.

@gregg-miskelly still same mate.

@cihadsevim sorry, I didn't mean to imply that procmon would fix the problem. I just wanted to confirm if the dotnet process was exiting with a zero exit code (meaning we should get the VS Code folks involved since this sounds like a VS Code bug) or a non-zero exit code (meaning we should get the .NET CLI folks involved). What was the exit code you saw?

I got this error using Code for Mac today. I restarted Code as recommended above and ran Debug. I got a message about configuration not being setup correctly. Clicking yes, setup config, fixed it. Debugging now works.

Thanks @jajajames. I’m glad the extension fixed this for you. I’m closing the issue. If folks see similar symptoms then please open a new issue so we can see what’s happening on latest bits.


My tweaks are not showing up in settings and Cydia menu don’t open up on iPhone 7 IOS 12.4 how can I fix it ?

My tweaks are not showing up in settings and Cydia menu don’t open up on iPhone 7 IOS 12.4 how can I fix it ?

I tink it's not support iOS12.4 now.
My all iOS device is iOS 12.4(5s,7,x) it show "Unsupported" button after run unc0ver.
My iPad Pro 1gen with 12.3.1 say Unsupported too.

I tink it's not support iOS12.4 now.
My all iOS device is iOS 12.4(5s,7,x) it show "Unsupported" button after run unc0ver.
My iPad Pro 1gen with 12.3.1 say Unsupported too.

It do support ios 12.4.

Run I-cleaner.  Also do you have Flame installed?

I have find out it is a bug  everyone’s is like that. It’s annoying, but I found if you slide your finger to the left while your tapping it helps. Sometimes takes a couple tries.

Still a issues on the new update .


Avoid recovery when using Durability::Paranoid

Currently, redb sets the needs_recovery flag as soon as you open the database, which means any unclean shutdown will trigger recovery.  For large databases, this isn't a great experience -- it means a simple Ctrl-C can end up locking you out of your database for a half-hour or more while it recovers.  It would be really nice if there were a way to avoid this.
Of course, recovery is unavoidable after an unclean shutdown when using Durability::Immediate, since there's no way to know whether the last commit was complete.  But if you're using Durability::Paranoid, it seems like recovery shouldn't be necessary!  This would let applications opt into slower commits in exchange for not needing recovery, which would be a big usability win when the database is large.
To make this work, I believe redb would need to write out the allocator state as part of Durability::Paranoid commits (or this could be a new durability level above Paranoid, to avoid slowing down existing Durability::Paranoid users who don't care about recovery speed).  But I think it could be done in a fully backwards- and forwards-compatible way.
Does this sound right to you?  And if so, do you think it would be a worthwhile change?

Ya, that seems useful. It should probably be separate from Paranoid since the allocator state grows linearly in the size of the database, and could be quite large.
Do you think a new Durability level, or a separate Database::flush(&self) method is more idiomatic?

Either way works, but I think a new Durability level would be nicer.  This minimizes the performance impact (since calling Database::flush() would mean an extra fsync(), whereas a new Durability level lets us do it as part of the regular two-phase commit), and it also avoids having a gap in between commit() and Database::flush() where a crash would still require recovery.
If it's useful, I can describe the design I had in mind -- I haven't implemented it yet, but I think I have a decent idea of how it would work.

Ya, a new Durability level seems good to me. Happy to merge a PR if you want to implement it!

Awesome!  I'll try implementing this and I'll send you a PR in a week or two.

I'm just finishing up the code here; I'll have a PR for you soon!  In the meantime, I've also got a few small fixes for preexisting redb bugs that I ran into -- I'm going to submit those first, because it'll make testing the main PR easier.


updated Shopify URLs

Currently, the Shopify URLs in the starter are:
`https://${SHOPIFY_STORE_ID}/admin/products/${productId}`

but there was an update not long ago changing the URLs to:
https://admin.shopify.com/store/${SHOPIFY_STORE_ID}/products/${productId}

and this pull request is to update those paths.

Thanks! I think the constants.ts file should be updated too to reflect this change where the SHOPIFY_STORE_ID const is initialized, even if it's just in the comment - currently this suggests the .myshopify.com domain which could be confusing.


[BUG] Unable to delete namespace longhorn-system in Rancher version 2.6.0

Describe the bug
Unable to delete longhorn-system namespace in Rancher version 2.6.0
To Reproduce
Steps to reproduce the behavior:

Installed longhorn on Rancher Version 2.5.14 using helm chart using private registry.
Created a storage class 'longhorn'
Added ingress to helm chart and upgraded
Upgraded Rancher server to 2.6.0
uninstalled loghorn using helm chart
delete longhorn-system namespace (k delete namespace longhorn-system)
Unable to delete longhorn-system namespace output of k delete namespace longhorn-system is "namespace "longhorn-system" deleted" and struck in terminating state since 2 days
Run 'kubectl api-resources --verbs=list --namespaced -o name | xargs -n 1 kubectl get --show-kind --ignore-not-found -n longhorn-system' returns
NAME                         READY   ALLOWSCHEDULING   SCHEDULABLE   AGE
node.longhorn.io/Host1   True    true              True          4d17h
node.longhorn.io/Host2   True    true              True          4d17h
node.longhorn.io/Host3   True    true              True          4d17h

Expected behavior
namespace longhorn-system should be deleted successfully
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: 1.3.0
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster: 2
Number of worker node in the cluster: 3

Node config

OS type and version: RHEL Server 7.9
CPU per node: 4
Memory per node: 4GB
Disk type(e.g. SSD/NVMe): NVMe
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): VMWare
Number of Longhorn volumes in the cluster: 0

Additional context
Add any other context about the problem here.

This issue has been inactive for a long time, the information may be outdated. Please create a new issue if come across a similar situation.


The action failed because of npm ci sync problem

But we didn't change code, a week ago, the action failed, we tried checkout the code locally, run npm ci, it works well:

Here is our action code:
name: API CI for New Pull Requests

on:
  pull_request:
    paths-ignore:
      - '**.md'
    branches:
      - main

jobs:
  install:
    name: Install dependencies
    runs-on: ubuntu-latest
    steps:
      # https://github.com/actions/checkout
      - name: Checkout 🛎
        uses: actions/checkout@v3

      # only install dependencies
      # https://github.com/cypress-io/github-action
      - name: Install 📦
        uses: cypress-io/github-action@v4
        with:
          runTests: false

@dadiorchen
Your log file uses cypress-io/github-action@v5 whereas the workflow source you posted shows cypress-io/github-action@v4. It would be best to use v5 in any case.
It looks like you have something out of sync in your repository. Make sure also that you only have one type of lock file in the branch.
Try to run npm install locally to make sure that your package-lock.json is in sync, then commit the changes to your repository.
If that does not help, then you may need to enable debugging. You can add
  env:
    DEBUG: '@cypress/github-action'

to your workflow.

@dadiorchen
Was this by any chance a create-react-app? I just had the same issue after I did an update.
It is most probable that the issue is not caused by github-action itself as the action just reports what npm ci did.

No I'm using next.js. I tried it again, using:

v5 of this action
Delete lock file and do install again
Try to change the node version locally to use 18, I was using v16 previously.
The result is the same, locally, it works, fails on github action, maybe I can try the tool to run action locally later.

@dadiorchen
Did you make any progress?
You could test without github-action using something like:
name: check-lockfile
on: workflow_dispatch
jobs:
  check-lockfile:
    runs-on: ubuntu-22.04
    steps:
      - name: Checkout
        uses: actions/checkout@v3
      - run: npm ci

@dadiorchen

After I saw your link to https://github.com/Greenstand/treetracker-web-map-client/pull/1598 I cloned the repository https://github.com/Greenstand/treetracker-web-map-client and ran npm ci locally. This gives the same errors that you are seeing in the GitHub workflow:

$ npm ci
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Invalid: lock file's<EMAIL_ADDRESS>does not satisfy<EMAIL_ADDRESS>npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file
npm ERR! Missing<EMAIL_ADDRESS>from lock file

You will need to run npm install to make sure that your package-lock.json is updated. You also need to make sure that you commit the updated  package-lock.json to GitHub so it is available when npm ci is run on GitHub.
Good luck!

@nagash77 oh, sorry, sounds great, I will try it!

@MikeMcC399 I'm really sorry, this is my fault, I found the reason, on my machine, I set up a npm config for some reason: legacy-peer-deps=true and this will cause the npm ci could be run successfully, and the npm install will not modify the lock file.

@dadiorchen

I found the reason, on my machine, I set up a npm config for some reason: legacy-peer-deps=true and this will cause the npm ci could be run successfully, and the npm install will not modify the lock file.

Congratulations on your successful troubleshooting!


Typechecker fails to unify

I finally got around to implementing an immutable vector type (#472). While implementing it, I ran into a case where the typechecker fails to unify, when it should.
Condensed example:
type Digit a =
    | One a
    | Two a a
    | Three a a a
    | Four a a a a

type Node a =
    | Node2 a a
    | Node3 a a a

type FingerTree a =
    | Empty
    | Single a
    | Deep (Digit a) (FingerTree (Node a)) (Digit a)

type View a =
    | Nil
    | View a (FingerTree a)

rec
let viewl xs : FingerTree a -> View a =
    match xs with
    | Empty -> Nil
    | Single x -> View x Empty
    | Deep (One a) deeper suffix ->
        match viewl deeper with
        | View (Node2 b c) rest -> View a (Deep (Two b c) rest suffix)
        | View (Node3 b c d) rest -> View a (Deep (Three b c d) rest suffix)
        | Nil ->
            match suffix with
            | One w -> View a (Single w)
            | Two w x -> View a (Deep (One w) Empty (One x))
            | Three w x y -> View a (Deep (Two w x) Empty (One y))
            | Four w x y z -> View a (Deep (Three w x y) Empty (One z))
    | Deep (Two a b) deeper suffix -> View a (Deep (One b) deeper suffix)
    | Deep (Three a b c) deeper suffix -> View a (Deep (Two b c) deeper suffix)
    | Deep (Four a b c d) deeper suffix -> View a (Deep (Three b c d) deeper suffix)
in

viewl

The specific lines the typechecker doesn't seem to like are lines 28 - 34, but am not sure for what reason. Full error:
error: Expected the following types to be equal
Expected: .tmp.test.FingerTree a
Found: .tmp.test.FingerTree a
1 errors were found during unification:
Types do not match:
    Expected: a
    Found: a
- <.tmp.test>:28:46
   |
28 |         | View (Node3 b c d) rest -> View a (Deep (Three b c d) rest suffix)
   |                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |

error: Expected the following types to be equal
Expected: .tmp.test.FingerTree a
Found: .tmp.test.FingerTree a
1 errors were found during unification:
Types do not match:
    Expected: a
    Found: a
- <.tmp.test>:31:32
   |
31 |             | One w -> View a (Single w)
   |                                ^^^^^^^^
   |

error: Expected the following types to be equal
Expected: .tmp.test.FingerTree a
Found: .tmp.test.FingerTree a
1 errors were found during unification:
Types do not match:
    Expected: a
    Found: a
- <.tmp.test>:32:34
   |
32 |             | Two w x -> View a (Deep (One w) Empty (One x))
   |                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
   |

error: Expected the following types to be equal
Expected: .tmp.test.FingerTree a
Found: .tmp.test.FingerTree a
1 errors were found during unification:
Types do not match:
    Expected: a
    Found: a
- <.tmp.test>:33:38
   |
33 |             | Three w x y -> View a (Deep (Two w x) Empty (One y))
   |                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |

error: Expected the following types to be equal
Expected: .tmp.test.FingerTree a
Found: .tmp.test.FingerTree a
1 errors were found during unification:
Types do not match:
    Expected: a
    Found: a
- <.tmp.test>:34:39
   |
34 |             | Four w x y z -> View a (Deep (Three w x y) Empty (One z))
   |                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |

This may be helpful to figure out the reason. Use different variables in each place:
type Digit a =
    | One a
    | Two a a
    | Three a a a
    | Four a a a a

type Node b =
    | Node2 b b
    | Node3 b b b

type FingerTree c =
    | Empty
    | Single c
    | Deep (Digit c) (FingerTree (Node c)) (Digit c)

type View d =
    | Nil
    | View d (FingerTree d)

rec
let viewl xs : FingerTree e -> View e =
    match xs with
    | Empty -> Nil
    | Single x -> View x Empty
    | Deep (One a) deeper suffix ->
        match viewl deeper with
        | View (Node2 b c) rest -> View a (Deep (Two b c) rest suffix)
        | View (Node3 b c d) rest -> View a (Deep (Three b c d) rest suffix)
        | Nil ->
            match suffix with
            | One w -> View a (Single w)
            | Two w x -> View a (Deep (One w) Empty (One x))
            | Three w x y -> View a (Deep (Two w x) Empty (One y))
            | Four w x y z -> View a (Deep (Three w x y) Empty (One z))
    | Deep (Two a b) deeper suffix -> View a (Deep (One b) deeper suffix)
    | Deep (Three a b c) deeper suffix -> View a (Deep (Two b c) deeper suffix)
    | Deep (Four a b c d) deeper suffix -> View a (Deep (Three b c d) deeper suffix)
in

viewl

The error would become:
error: Expected the following types to be equal
Expected: test.FingerTree e
Found: test.FingerTree c
1 errors were found during unification:
Types do not match:
    Expected: e
    Found: c
   ┌─ test:28:46
   │
28 │         | View (Node3 b c d) rest -> View a (Deep (Three b c d) rest suffix)
   │                                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: Expected the following types to be equal
Expected: test.FingerTree e
Found: test.FingerTree c
1 errors were found during unification:
Types do not match:
    Expected: e
    Found: c
   ┌─ test:31:32
   │
31 │             | One w -> View a (Single w)
   │                                ^^^^^^^^

error: Expected the following types to be equal
Expected: test.FingerTree e
Found: test.FingerTree c
1 errors were found during unification:
Types do not match:
    Expected: e
    Found: c
   ┌─ test:32:34
   │
32 │             | Two w x -> View a (Deep (One w) Empty (One x))
   │                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^

error: Expected the following types to be equal
Expected: test.FingerTree e
Found: test.FingerTree c
1 errors were found during unification:
Types do not match:
    Expected: e
    Found: c
   ┌─ test:33:38
   │
33 │             | Three w x y -> View a (Deep (Two w x) Empty (One y))
   │                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: Expected the following types to be equal
Expected: test.FingerTree e
Found: test.FingerTree c
1 errors were found during unification:
Types do not match:
    Expected: e
    Found: c
   ┌─ test:34:39
   │
34 │             | Four w x y z -> View a (Deep (Three w x y) Empty (One z))
   │


Review for missing content - at_backupkey_flutter (API Reference)

[ ] Right nav bar API reference needs review for missing content. (samples and examples)
[ ] Do we need a documentation link?

Please check library links (current, samples, examples)
LIBRARIES

[ ] at_backupkey_flutter
[ ] backup_key_widget
[ ] backupkey_service
[ ] color_constants
[ ] size_config
[ ] strings

Hi @sarika01 we need to review this very old ticket for accuracy, potentially close it and divert to the new pub.dev publishing issue. Creating new issue cards today.
If you are not the correct package maintainer, we need to update the list.


Support new contributors to this project by creating a "Good first issue" or "Help wanted" label.

I'm trying to find out good ways to start contribute to AspNetCore but there are no issues that are marked as "Good first issue" or "Help Wanted". This makes it very difficult to find tasks to work on, and discourages outside developers from working on the project.
User story: As a programmer, it's difficult to find ways to start contributing to AspNetCore projects.
Proposed solution: A new "Good first issue" label
Create a new label as per the Github Guidelines to help new contributors find new issues that they can work on.
The label should either contain the words

Good first issue
Help wanted

In order to have GitHub pick up the label as something to promote. This is not necessary as part of this proposal, but it would be nice.
After a preliminary search it seems no such label exists. If such a label does exist, please rename it. Of course, this also requires you to label good first time issues.
Notes

You can learn more about this here: https://help.github.com/en/articles/helping-new-contributors-find-your-project-with-labels
Here's a Microsoft product that does this properly: https://github.com/OfficeDev/office-ui-fabric-react/issues
Can help with on-boarding new team members and interns too, by making it easy to pick tasks for them
GitHub will automatically promote the labels if named properly. It will look like this:

Alternatives
Updating contributing guidelines
Additionally, updating the contributing guidelines to be more clear where users can start would be useful. Updating instructions for building would be good.
I understand it's important that users start a dialog before starting any tasks. However, it's important to also on-board new contributors to the project. This label would be a good step in this direction.
Participate in Google Summer of Code
Participating in Google Summer of Code would also be a good idea. Not only would it get students interested in contributing, it would also get you good feedback about how open your project is to outside contributions.

Hi @Quenty , this repo uses the up-for-grabs label: https://github.com/aspnet/AspNetCore/issues?q=is%3Aopen+is%3Aissue+label%3Aup-for-grabs
That label is applied when it's a "good first issue" and requires relatively little context.

But perhaps this label should be renamed. "Back in the day" the up-for-grabs label was quite common; only later did the other label names become more common.

I'm in favor of following the new GitHub guidelines. As Eilon mentioned, those guidelines are newer than our repos. Renaming a label should be trivial. We should check the other @aspnet repos, too.
Cc @pilchie

We talked about it with our team, and I'll be updating labels and contributing guid later today to use GitHub's "help wanted" and "good first issue" conventions. Thanks for the suggestion @Quenty!
As far as your other suggestions:

re: "Updating instructions for building would be good.". We already have a doc for this that we keep up to date. I'll add a link to it from CONTRIBUTING.md to https://github.com/aspnet/AspNetCore/blob/master/docs/BuildFromSource.md.
Re: Google's Summer of Code - it looks like we missed the cutoff for participating as an organization for Summer 2019. But I'll keep this in mind for next year.

Thank you so much!


blog post: lts19 release and nightly to ghc9.2

I think we can wait for the Nightly rebase to 9.2 before publishing this.

I would welcome any suggestions on possible improvements.
Maybe it is better to prefix the filename with the date?

LGTM. I'd recommend merging as it is now, we don't usually include dates in the filename.

Okay, cool, please merge!

Should be all good now, thanks :+1:


Refactor ideas

Code is getting a bit of a mess as it is now. Refactor ideas: create separate classes for batch and carriers and wrap elements inside them.

Refactor ideas/notes:
omSipCreator.py
1283 lines
main
433 lines
processPPN
args:

PPN
carriers
dirOut
colsBatchManifest
batchIn
dirsInMetaCarriers
carrierTypeAllowedValues

returns: -
287 lines
processCarrier
args:

carrier
fileGrp
SIPPath
sipFileCounterStart
counterTechMDStart

returns:

fileGrp
divDisc
premisCreationEvents
techMDFileElements
cdInfoElt
sipFileCounter
counterTechMD

332 lines
get_immediate_subdirectories
called from main
checkFileExists
called from main
readChecksums
called from processCarrier
generate_file_sha512
called from processCarrier, main
errorExit function in main, but alled from other modules --> move to shared module!

Done https://github.com/KBNLresearch/omSipCreator/releases/tag/0.5.0


simplify NotAnalyzed handling, minor performance optimization

Codecov Report

Merging #73 (980ce1c) into avi/exception2 (ef91cde) will decrease coverage by 0.34%.
The diff coverage is 80.00%.

@@                Coverage Diff                 @@
##           avi/exception2      #73      +/-   ##
==================================================
- Coverage           78.65%   78.31%   -0.35%
==================================================
  Files                   3        3
  Lines                 923      913      -10
==================================================
- Hits                  726      715      -11
- Misses                197      198       +1

Impacted Files
Coverage Δ

src/utils.jl
38.00% <0.00%> (ø)

src/EscapeAnalysis.jl
87.34% <85.71%> (-0.32%)
:arrow_down:

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 ef91cde...980ce1c. Read the comment docs.


Allow development events through config

The config parameter of create_client is not spread into the internal metrics config.
This prevents us from overwriting protocol in development. As a result events are not received by mixpanel. Also I cant turn on the debug / verbose flags to aid my debugging.

The user-provided config is applied on initialization here: https://github.com/mixpanel/mixpanel-node/blob/e24a3980d0ffbc82e2478c6ac33efbb255a7b1a0/lib/mixpanel-node.js#L453-L455

🤦 whoops, I had something else preventing events being sent, my bad


Build with debug logging disabled in release builds (by default)

The log_level configuration variable is used by macros in the log crate to enable/disable logging statements at compile time. Because this feature controls a performance versus debugging trade-off, it would be useful to control it per-profile, like Cargo already does for the debug_assertions cfg variable.
I suggest adding a log_level key to the [profile.*] sections, with a default value of info for the release and bench profiles.
Note: Unlike debug_assertions, this variable is not used by the compiler standard library, but it's used by the Rust team's own log library, and can potentially be used by other logging libraries, so I think it's worth having sensible default values built in to Cargo.  But an alternate solution is to add a way to set arbitrary cfg variables in the profile sections, and allow each application to choose whether to set log_level.

Should this be an RFC?

+1

I commented on the associated PR but for now I'm going to close this in favor of "needs an RFC".

Filed rust-lang-nursery/log#58 for an alternate solution.


FontIcon not working

Hello,
I am not able to use FontIcon in my Project. Can you provide some example for it.
Thanks

The FontIcon has no styles! You have to include material icons as stated in repository


fix onPress bug

fix for that issue:
https://github.com/marklawlor/nativewind/issues/770 when you have some callback and some state with the callback
const [counter, setCounter] = useState(0)
...

<Pressable
    className="active:bg-red-500"
    onPress={()=> console.log(counter)}
/>
<Text> Press me
</Pressable>l
...

the counter will show only the initial value

I tried this PR and it didn't work for me.
The problem seems to be that in order to please React Native, NativeWind adds an onPress handler which is not kept up to date
https://github.com/marklawlor/nativewind/blob/516c0c620384fdd058d060c034a09f8816e3f6dc/packages/react-native-css-interop/src/runtime/native/style.ts#L569
So to counteract the previous onPress hack, we need to add another one but only for the onPress property:
// keep this the same as before
props = {
 ...props,
 ...state.props,
};

// add these two lines
if (state.convertToPressable && originalProps?.onPress)
   props.onPress = originalProps.onPress

Fixed in 4.0.24
And yes, unfortunately this PR would not have worked. E.g if the user provided inline styles + className - it would only render the inlineStyles.


added logic to handle onetime payment schedule

added logic to handle onetime payment schedule

Need to update DB file


Shortcuts  FancyZones not working

Microsoft PowerToys version
0.47.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
I have multiple shortcuts defined in FancyZones. I am unable to switch between zones. When I use the shortcuts the last selected shortcut is always the default and none of the others work.
For example, I select shortcut 8 in the editor. After closing the editor and selecting shortcut number 6, 8 is chosen."No matter which shortcut I choose, the last one opened in the editor is always the chosen one.
✔ Expected Behavior
Switching between layouts.
❌ Actual Behavior
Defaults to last selected layout in editor
Other Software
No response

@DieBruine did you press the Save button after selecting the shortcut?

I have the same issue. I have two custom designs, one with shortcut 0 and the another one with 1. When I press the shortcut for 0 or 1 it doesn´t switch between designes, it only shows the last one selected on the editor. I pressed save, removed and re-created the designs... It happens since the last update v.0.47.0. On older versions works perfectly
By the way, the app works great, many thanks for your work!!

Same problem for me and a friend of mine

@dlorenzonespereira thank you for the clarification!
It looks like the same issue as https://github.com/microsoft/PowerToys/issues/13515, so I'll close this as a duplicate to centralize the discussion thread.


Add preferred format check for LogSearch

Description
Add org files support for LogSearch by fetching preferred format from Logseq config
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@futantan could you look into this PR and give a review?

Bumping this

Wrote the author

Anything I can help?

@yishus @pernielsentikaer
Sorry, my bad, I forgot to submit the review. 16 days ago...

Thanks for taking your time @futantan 🔥


ray <IP_ADDRESS> - open files with vscode-ssh does not work

ray version <IP_ADDRESS>
with vscode logged using ssh, when you click on filename, vscode tries to open another instance using filepath as it were on local pc. obviously it doesn't work. ray should instead search for that path in the already-opened instance of remotely connected vscode.

thanks in advance for your support

You can solve this, but adding a Ray config file on your remote server. You an use this to translate the remote path to the local path.
https://spatie.be/docs/ray/v1/configuration/framework-agnostic-php


get(type=) should catch TypeError consistently

#2842 changed TypeConversionDict.get to catch TypeError in addition to ValueError, but other datastructures with get(type=) were not changed. Make them all consistent.

Headers only has string values, so a type that raised TypeError on any string would be pointless. So Headers.get can be excluded.


How to use plugin with webpack-dev-server?

Hi! I have problem when using plugin with webpack-dev-server.
I've rendered my index.html but it stays in memory, not in the content-base folder where static should be located. So browser cannot find any index.html and gives 404 error.

Hi - could you send me a minimal project setup so I can try to reproduce the error?

I fixed it after setting publicPath to "/". Didn't work with any other path.


Need help training models/ draw ROI bug

Hi! I'm wondering how model training works? I am currently trying to train a model in cellpose 3.0.8 to identify all muscle fiber cells in a cross section with IF Laminin staining (stains extracellular matrix-images attached below). I first tried to train the model based on one cropped-out muscle group. However, after about 4 different cropped images, the model was spitting out an ROI coverage not nearly as great as just using cyto3- especially when applying the models to an entire cross section with all muscle groups. Is this based off of the set calibration? Does the size of the image (in terms of zoom in/out and #cells per image) matter when it comes to model accuracy?
I also noticed that when you train the model, the initial model used is the cyto3 for each. Are each of my models that I have made and corrected based solely on cyto3 and not the previous model I am trying to build? If the models are being built on top of one another (as I hope), how does this work and is there a way to see what models the new model will be based off of? Otherwise, how do I make a model that is much more accurate in identifying muscle fiber cells? Is there a repetition range I should shoot for during training?
I am also noticing that the draw ROI bug is still present with cellpose 3.0.8. The red circle disappears but the mouse tracker trail stays and does not leave unless I exit the program/ add a new image. When this happens, should I save my model with the image I am correcting right then or start over with corrections? (does the program identify the trail as draw ROI or can it not recognize it?)
Muscle Group Cropped.pdf

duplicate of #961 please try the latest python=3.10 or python=3.11 and upgrade pyqt6

I've added more info about image normalization and training here, which could be your issue: https://cellpose.readthedocs.io/en/latest/train.html#re-training-a-model
correct, the training starts with cyto3 each time -- you want to make sure all your labeled images are in the training folder so they are all used for training, we have some youtube videos on cellpose2 that can provide more info on this - basically if you keep retraining on new models you will forget your previous image segmentations, so it's best to train on all images together


What type of globs does pattern use?

Hi, I was wondering what type of globs the file pattern use?
I was trying to use glob /**/*.[jt]s?(x) which works on this glob tester which uses minimatch, to no avail. I couldn't find any documentation on what glob matcher this library uses and my attempts to search the source for pattern were in vain.
Any guidance would be very appreciated.
Tags
globs pattern minimatch wildcard file pattern

As workaround, I just include my languages like this:
"language": [
                "typescript",
                {
                    "pattern": "/**/*.ts"
                },
                "javascript",
                {
                    "pattern": "/**/*.js"
                },
                "jsx",
                {
                    "pattern": "/**/*.jsx"
                },
                "tsx",
                {
                    "pattern": "/**/*.tsx"
                },
            ]

It's verbose, but, perhaps overall it's a bit better. This way I'm not overloading the job of one pattern to match many types of files. I suppose I can live with this.


tcp_proxy: wait for CONNECT response before start streaming data

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message: The TCP proxy used in tunneling mode now waits for the CONNECT response before start sending the data. Before the data was transmitted right after the CONNECT request.
Additional Description:
Risk Level: medium
Testing: unit test, integration, manual test
Docs Changes: https://github.com/irozzo-1A/envoy/blob/wait-for-connect-response/docs/root/intro/arch_overview/http/upgrades.rst#tunneling-tcp-over-http
Release Notes: https://github.com/irozzo-1A/envoy/blob/wait-for-connect-response/docs/root/version_history/current.rst#minor-behavior-changes
Platform Specific Features: NONE
Runtime guard: http_upstream_wait_connect_response

Refers to https://github.com/envoyproxy/envoy/pull/13293#issuecomment-701408912

cc. @wez470 @alyssawilk

The solution proposed here has to be considered as a base for discussion. I think this is not a good approach, but I'm still looking for a solution that does not require too much refactoring. Any idea is welcome.

yeah, stashing the params (maybe in a wrapper struct) seems like the only thing I can think of either.

yeah, stashing the params (maybe in a wrapper struct) seems like the only thing I can think of either.

ok, I'll proceed this way then ;-)

This looks great - I love how self contained it ended up being.

Thx @alyssawilk, I'm trying to avoid having the cyclical ownership issue with:
https://github.com/irozzo-1A/envoy/blob/d867f50fcf75e5c6efc15826e2c9e7534680e21f/source/common/tcp_proxy/upstream.h#L178-L180
https://github.com/irozzo-1A/envoy/blob/d867f50fcf75e5c6efc15826e2c9e7534680e21f/source/common/tcp_proxy/upstream.h#L93
After that, I'll address your remarks ;-)

oh, and given the change to the data plane, we should probably runtime guard this (see CONTRIBUTING.md).  Sorry, should have called that out before.

I'm on vacation starting today through the new year, so I'm going to pass this off to snow/Matt. I hopefully explained the corner case enough they can help you for the few days until the envoy project goes 'on vacation' but if not I'll pick it up when I get back!

Thx for the info @alyssawilk, enjoy your vacation ;-)

oh, and given the change to the data plane, we should probably runtime guard this (see CONTRIBUTING.md). Sorry, should have called that out before.

No worries, I'll take a look at this.

@alyssawilk I think I addressed your points. At the moment the feature flag is enabled by default, let me know if you prefer the opposite.

@alyssawilk I think I addressed your points. At the moment the feature flag is enabled by default, let me know if you prefer the opposite.

I can take a look since Snow is sick.

I can take a look since Snow is sick.

Yeah, watermarking already connects the upstream (TCP or HTTP) watermarks to downstream, and vice versa.
Timeouts are mildly interesting because the connection looks established from the connection pool perspective but the TCP proxy session doesn't know the upstream connection is assigned.   Given we handle the appropriate (wait for upstream connect) timeout in the connection pool, I think the only arguably error is if you had say a 5s keepalive timeout, and you got a 200-Ok in 3s and data in 3s you'd time out where it shouldn't.  I think this is orthogonal of this change, but if we cared we could fix by sending an empty date frame or some other ping to tickle the keepalive when the 200 came in.

Yeah, watermarking already connects the upstream (TCP or HTTP) watermarks to downstream, and vice versa.
Timeouts are mildly interesting because the connection looks established from the connection pool perspective but the TCP proxy session doesn't know the upstream connection is assigned.   Given we handle the appropriate (wait for upstream connect) timeout in the connection pool, I think the only arguably error is if you had say a 5s keepalive timeout, and you got a 200-Ok in 3s and data in 3s you'd time out where it shouldn't.  I think this is orthogonal of this change, but if we cared we could fix by sending an empty date frame or some other ping to tickle the keepalive when the 200 came in.

Timeouts are mildly interesting because the connection looks established from the connection pool perspective but the TCP proxy session doesn't know the upstream connection is assigned. Given we handle the appropriate (wait for upstream connect) timeout in the connection pool, I think the only arguably error is if you had say a 5s keepalive timeout, and you got a 200-Ok in 3s and data in 3s you'd time out where it shouldn't. I think this is orthogonal of this change, but if we cared we could fix by sending an empty date frame or some other ping to tickle the keepalive when the 200 came in.

Yeah I think this is fine. I just wanted to make sure we don't somehow lose the timeout entirely.

Timeouts are mildly interesting because the connection looks established from the connection pool perspective but the TCP proxy session doesn't know the upstream connection is assigned. Given we handle the appropriate (wait for upstream connect) timeout in the connection pool, I think the only arguably error is if you had say a 5s keepalive timeout, and you got a 200-Ok in 3s and data in 3s you'd time out where it shouldn't. I think this is orthogonal of this change, but if we cared we could fix by sending an empty date frame or some other ping to tickle the keepalive when the 200 came in.

Yeah I think this is fine. I just wanted to make sure we don't somehow lose the timeout entirely.


Expand icon prop

Currently the icon, iconList and iconSet props in many components accept just a String that is automatically mapped to the fas subset of FontAwesome icons.
Any deviation from this icon set must be achieved by populating the respective add-on slot housing the icon. This can get cumbersome and unnecessarily verbose.
A viable alternative would be to allow passing each icon either as a String (that is programmatically mapped to ['fas', icon]) or as an array listing the subset and the icon name.
This approach would also simplify template declarations of FontAwesomeIcon components
as this functionality is implemented in the FontAwesomeIcon Vue component itself).
<FontAwesomeIcon :icon="icon"/>

Hi I am a Outreachy Fall 2019 applicant. I would like to work on this issue. Can you please assign it to me?

Sure. Take it up!

@sabina-rohman any updates?

@dhruvkb oh so sorry, didn't realize it was already assigned to me! I accepted and am working on a separate mozilla task at the moment. I could try this one once I complete the current task. Though I am not sure when. For now please feel free to un-assign it in case anyone else may want to pick it up. Thanks :)

I'm unassigning this for time being. Feel free to take it up again if you are freed from the other task and this hasn't been taken up in the meantime.

Hello @dhruvkb I'm an Outreachy applicant and would like to take this up if its available. I would start with all the icon props components, submit pull request and then the iconList and finally iconSet. What do you think?

@sayima-n sounds good!

Thank you! Talk to you soon

@dhruvkb in addition to not allowing any non Creative Commons icon within it's icon-list prop, the LicenseIconography is the only component not to provide a slot to render alternative icons. So it seems that this component refuses non Creative Commons icons by design. For this reason I'm wondering if the icon-list prop should nevertheless be made to accept any icons or left as is?

@sayima-n the LicenseIconography component is meant solely to depict icons that are parts of CC licenses. That is why their so constrained in terms of what icons they can show.
Since the component has a very narrow usecase and its icons are only available in the ‘fab’ set, you can leave the prop there as is.


support -typed option

gomock supports -typed option to generate type safe code currently. https://github.com/uber-go/mock/blob/main/mockgen/mockgen.go#L67
This PR adds the option to gomockhandler to be able to use the option via gomockhandler.

released as -
https://github.com/sanposhiho/gomockhandler/tree/v1.6.0

thank you for the quick review!


Update scenerendering.cpp

When merging indexes, we need to consider the number of vertices that have been merged

Can you elaborate? Does this crash with the current version of the sample?

the current version of the sample is right, but when I run your code with sponza , some of the models fail to be rendered.

Can you elaborate? Does this crash with the current version of the sample?
the current version of the sample is right, but when I run your code with sponza , some of the models fail to be rendered.

Can you elaborate? Does this crash with the current version of the sample?

the current version of the sample is right, but when I run your code with sponza , some of the models fail to be rendered.

Can you elaborate? Does this crash with the current version of the sample?

Replaced with sponza model, some models cannot be rendered，Isn't this a bug?   I reference your project  [https://github.com/SaschaWillems/VulkanSponza ]，It is right 。

Sorr  for the late reply. Just checked and Sponza didn't work for me either. I just pushed a fix that makes scenes other than Sibenik (like Sponza) to render properly witht that sample.

Fixes rendering for other models like sponza

Sorr for the late reply. Just checked and Sponza didn't work for me either. I just pushed a fix that makes scenes other than Sibenik (like Sponza) to render properly witht that sample.

It's ok，The problem is solved


Settings UI: Renaming default color scheme applies to each profile instead of defaults section

Environment
Windows build number: Microsoft Windows [Version 10.0.19042.746]
Windows Terminal version (if applicable): Windows Terminal Preview Version: 1.6.10272.0

Steps to reproduce

Create a custom color scheme named 'foo'
In the "Base Layer" settings page, select 'foo' as the color scheme
Rename the color scheme 'foo' to 'bar'

Expected behavior
The color scheme in the "Base Layer" settings should be updated to be 'bar' and changing it should affect all profiles.
Actual behavior
The color scheme in the "Base Layer" settings changes to "Campbell" and changing it has no effect on other profiles.  Looking at the settings file you will see that each profile has had the colorScheme attribute added with the new name, and the colorScheme attribute in the defaults section still has the old name.

@carlos-zamora

Oh man. I know exactly what the problem is:
https://github.com/microsoft/terminal/blob/47f4b4197d82f3e4cdb3886148a25f9ff30322c4/src/cascadia/TerminalSettingsModel/CascadiaSettings.cpp#L875
We should also update ProfileDefaults (aka "base layer") in this function.

Oof, you know what? I bet the loop here is forcing every profile to override the setting, too.
https://github.com/microsoft/terminal/blob/47f4b4197d82f3e4cdb3886148a25f9ff30322c4/src/cascadia/TerminalSettingsModel/CascadiaSettings.cpp#L879-L884
If you set BaseLayer's color scheme first, that check won't force an override ........ but that feels like "works because of circumstances", not "works because of good design"

Good call. We need a HasColorSchemeName() check inside the loop too. Make sure that we're only redirecting any explicitly set references.

Thanks again for the report!


AmbiguousTermWarning: Multiple unit options are possible for parameter 'base peak intensity' but none were specified

Hi,
when I the program using the test data:
singularity exec --writable-tmpfs -e \
/nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/dia-ms.sif \
python /timsconvert/bin/run.py --input /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/massive.ucsd.edu/MSV000088438/updates/2022-02-24_gbass_3339138d/raw/timsconvert_raw_data_2/brevi_brachy.d --outdir /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/data --exclude_mobility --verbose

I get these warnings:
/miniconda3/lib/python3.7/site-packages/psims/mzml/components.py:585: AmbiguousTermWarning: Multiple unit options are possible for parameter 'base peak intensity' but none were specified
  self._check_params()
/miniconda3/lib/python3.7/site-packages/psims/mzml/components.py:614: AmbiguousTermWarning: Multiple unit options are possible for parameter 'base peak intensity' but none were specified
  self.write_params(xml_file)

Here is the full exec log:
convert_tests/massive.ucsd.edu/MSV000088438/raw/timsconvert_raw_data/dd/rs17e_1mgml_no_tims_1_0_C2_MS.d --outdir /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/data --exclude_mobility --verbose
2022-08-30_11-37-31-298235:Initialize Bruker .dll file...
2022-08-30_11-37-31-399510:Loading input data...
2022-08-30_11-37-31-399867:Reading file: /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/massive.ucsd.edu/MSV000088438/raw/timsconvert_raw_data/dd/rs17e_1mgml_no_tims_1_0_C2_MS.d
2022-08-30 11:37:31.526350 [tid=0x8630d180] [WARN ] bdal.io.tims.TdfReaderImpl: Requested recalibration file "/nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/massive.ucsd.edu/MSV000088438/raw/timsconvert_raw_data/dd/rs17e_1mgml_no_tims_1_0_C2_MS.d/calibration.sqlite" does not exists. Fallback to instrument calibration from tdf.
2022-08-30_11-37-31-575524:input: /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/massive.ucsd.edu/MSV000088438/raw/timsconvert_raw_data/dd/rs17e_1mgml_no_tims_1_0_C2_MS.d
2022-08-30_11-37-31-575752:outdir: /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/data
2022-08-30_11-37-31-575839:outfile:
2022-08-30_11-37-31-575922:mode: centroid
2022-08-30_11-37-31-576006:compression: zlib
2022-08-30_11-37-31-576082:ms2_only: False
2022-08-30_11-37-31-576160:exclude_mobility: True
2022-08-30_11-37-31-576239:encoding: 64
2022-08-30_11-37-31-576365:barebones_metadata: False
2022-08-30_11-37-31-576441:profile_bins: 0
2022-08-30_11-37-31-576516:maldi_output_file: combined
2022-08-30_11-37-31-576591:maldi_plate_map:
2022-08-30_11-37-31-576666:imzml_mode: processed
2022-08-30_11-37-31-576741:lcms_backend: timsconvert
2022-08-30_11-37-31-576815:chunk_size: 10
2022-08-30_11-37-31-576889:verbose: True
2022-08-30_11-37-31-576964:start_frame: -1
2022-08-30_11-37-31-577038:end_frame: -1
2022-08-30_11-37-31-577112:precision: 10.0
2022-08-30_11-37-31-577206:ms1_threshold: 100
2022-08-30_11-37-31-577315:ms2_threshold: 10
2022-08-30_11-37-31-577390:ms2_nlargest: -1
2022-08-30_11-37-31-577464:version: 1.1.0
2022-08-30_11-37-31-577538:infile: /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/massive.ucsd.edu/MSV000088438/raw/timsconvert_raw_data/dd/rs17e_1mgml_no_tims_1_0_C2_MS.d
2022-08-30_11-37-31-577616:.tsf file detected...
2022-08-30_11-37-31-577704:Processing MALDI dried droplet data...
2022-08-30_11-37-31-577784:Initializing mzML Writer...
2022-08-30_11-37-31-581618:Initializing controlled vocabularies...
2022-08-30_11-37-32-327398:Writing mzML metadata...
2022-08-30_11-37-32-334649:Writing data to .mzML file /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/data/rs17e_1mgml_no_tims_1_0_C2_MS.mzML...
2022-08-30_11-37-32-335093:Calculating number of spectra...
/miniconda3/lib/python3.7/site-packages/psims/mzml/components.py:585: AmbiguousTermWarning: Multiple unit options are possible for parameter 'base peak intensity' but none were specified
  self._check_params()
/miniconda3/lib/python3.7/site-packages/psims/mzml/components.py:614: AmbiguousTermWarning: Multiple unit options are possible for parameter 'base peak intensity' but none were specified
  self.write_params(xml_file)
2022-08-30_11-37-32-378134:Updating scan count...
2022-08-30_11-37-32-381740:Finished writing to .mzML file /nfs3_ib/ip29-ib/ip29/sheela_group/programs/containers/timsconvert_tests/data/rs17e_1mgml_no_tims_1_0_C2_MS.mzML...

Is this normal behaviour or chould it be of concern?
tks

Thanks for asking! I think those warnings are fine, we're likely doing a slightly wrong thing in writing out the mzML without the right units in that area, but intensity generally doesnt really need units anyway, but we'll take a look!

Very late to this but to elaborate on the warning this issue mentions, that was an warning from an old version of psims (0.1.34) that appeared when no intensity value was explicitly provided for the base peak intensity. This resulted in the use of the default CV param MS:1000131 number of detector counts, which should be the correct CV param. 434d61f6696859074289a51f628a8c9677087c79 has updated psims to version 1.2.7 and explicitly calls for this CV param for base peak intensity value so this should no longer appear.
Also thank you for the singularity container, I will reference this as I (slowly) continue to add various recipe files.


Adds missing data in fetch response.

Closes #4
Closes #5
This PR adds all missing methods for doing a fetch call as shown here: https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch
This aligns with Deno, since Deno uses the same API as the browser, and no Node fetch.
All added methods just return the normal body, since the responseBody is assumed to be in final output form.
This also adds response.ok which is a boolean set to true when the response is < 400 or the default of 200.

@SachaCR this passes locally on Deno version 1.2 locally, but not Deno version 1.0 in GitHub Actions, I am not sure why.
Would you like me me to upgrade the Deno version for GitHub actions?

I downgraded my local to Deno 1.0.0 and this happens locally. The issue is in the testing library. My guess is we are using the latest assertion library, which has some requirements on the newer version of Deno. When importing, we are not locking the version of we using, which seems to be the cause.
I believe running tests against master will still fail and has nothing to do with my changes.
You will need to do deno test -r to reinstall to get the version of the files on GitHub actions, otherwise, you most likely have the older version cached, which will pass.

@khrome83 Thanks for your contribution and your investigation. I'll try to fix the version when importing the package to avoid that behavior in the future.

@khrome83 I just have updated deno to 1.2.0 for github action. if you rebase your PR on master the CI should pass.


Upload to NuGet

Can you upload your library to NuGet please ? Because I'm tired about updating the new version by cloning this repo

This Package is already uploaded to Nuget under https://www.nuget.org/packages/Lavalink.NET, i will add this into the readme soon.


[stable/falco] Use KUBERNETES_SERVICE_HOST environment variable

Instead of hardcoding or relying in DNS, use this method.
Signed-off-by: Néstor Salceda<EMAIL_ADDRESS>
What this PR does / why we need it:
This PR uses KUBERNETES_SERVICE_HOST environment variable instead of relying on a hardcoded name.
It synchronizes with Falco daemonSet:
https://github.com/falcosecurity/falco/blob/dev/integrations/k8s-using-daemonset/k8s-with-rbac/falco-daemonset-configmap.yaml#L28
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

/assign @bencer

/lgtm
/approve


Add support for Heltec ESP32 based boards

This pull request adds documentation, code, and pre-built static libs for Heltec ESP32 based boards

Hi @lokkju, thank you for your contribution!
The only part left to do is to re-build the library sources for m0 & m0+, since they will be effected by the header changes as well.
Thanks!
-Kent

Probably a good idea; though since the header changes are name-only, and don't change the internal enum values, I'm pretty sure the existing libs are still compatible.  That said, it's probably best for you to rebuild all the binaries yourself.

@lokkju This currently breaks support for the cortex-m0 targets without a rebuild of the library. I am happy to rebuild the libs for the m0's. Would you mind giving me push permission to your fork so I can PR on top of your branch.
Thanks!
-Kent

@kent-williams you should already have access to my branch; "allow edits from maintainers" is enabled for this pull request.

@lokkju Even easier, thanks!


Unable to send outgoing payments

I can receive incoming payments from other wallets but can't seem to send funds out of my Mutiny wallet. Error: Unable to find routes.

can you post your logs?

mutiny-logs.txt

Seems like you don't have enough balance to afford an HTLC right now with current on-chain fees. We outline this in our FAQ, hope that helps!
https://blog.mutinywallet.com/mutiny-wallet-faq/
Typically the way to fix this is to top up more or wait for fees to go down.
We are working on solutions to better communicate this!

I'm not able to receive payments on Lightning to top up my wallet

Hey, I've tried topping up my wallet but I keep getting the error that no routes are found even after that.
I just want to sweep my wallet but it seems like my funds are just stuck. What do I do?

How much balance does it say you have available to spend in your channel view?
Otherwise just close your channels if you want out.

I have enough outbound capacity.
There's no 'close channel' option anywhere. Where and how can I do that?

It's there in the same screen as the channel info. Are you on the latest version?

Yeah I was using an older version. Updated the app and I can see it now.
But the fund balance I have in my wallet differs from the numbers in the channel information page. Half my funds are being shown as reserve.

We do our best to explain some of that on that page and here https://blog.mutinywallet.com/mutiny-wallet-faq/
When you close, you'll get your "home page balance" minus on chain fees. It'll be somewhere between the two balances. The reserve you see now includes possible on chain fees that might occur if a force close happens while routing a payment.

It's a bit difficult to be onboard with how this whole thing works when I get to know about this after I deposited funds into the wallet.
It's like I lost a portion of my funds the moment I deposited funds into the wallet. Will the amount of funds that's reserved get reduced as on-chain fees goes down? Or is it going to permanently be a part of the reserves?


EV-4848 docs for packetcapture resource requirement

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@ctauchen Adding the resource requirement for packet capture deployment. This need Packetcapture custom resources definitions which has been added recently in calico-private.
Would you be generating all the spec's again? or should i create a PR for that?

LGTM. Yes, we'll be regenerating the specs as we approach the release date.


[Docs] Add msix embedding instructions

Summary of the Pull Request
What is this about:
What is include in the PR:
How does someone test / validate:
Quality Checklist

[x] Linked issue: #11705
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

@crutkas @dedavis6797
This is the documentation with instructions for adding a msix PowerToy.
Please take a look and let us know if this is what you intended.

Let's get this merged in by tomorrow if there's no other feedback.


Always reset file descriptor after consuming it

This prevents the request cancelling logic from closing an unrelated fd that happens to reuse the same number.
https://github.com/zsh-users/zsh-autosuggestions/blob/a411ef3e0992d4839f0732ebeb9823024afaaaa8/src/async.zsh#L12-L15

Hey, thanks for this. I stumbled across the same issue while looking into #753 (see last paragraph of https://github.com/zsh-users/zsh-autosuggestions/pull/753#issuecomment-1694146062).
I was able to produce errors with ZSH_AUTOSUGGEST_MANUAL_REBIND active and sourcing a file async-widget-setup.zsh after the first precmd with the plugin active. If manual rebind is not active or if the widgets are created before the first precmd, then zsh-autosuggestions wraps the widgets and for some reason we don't seem to get any fd conflicts.
The .zshrc:
ZSH_AUTOSUGGEST_MANUAL_REBIND=true
source zsh-autosuggestions.zsh

and async-widget-setup.zsh:
function async-widget-fork() {
	exec {fd}< <(echo foo)
	zle -M "opened: $fd, autosuggest fd: $_ZSH_AUTOSUGGEST_ASYNC_FD"
}

function async-widget-read() {
	zle -M "reading from $fd: $(cat <&$fd)"
}

zle -N async-widget-fork
zle -N async-widget-read

bindkey ^A async-widget-fork
bindkey ^B async-widget-read

Then run ZDOTDIR=$PWD zsh and:

source async-widget-setup.zsh
At the next prompt, type one character e.g. "a" to trigger an async request/response cycle. This leaves _ZSH_AUTOSUGGEST_ASYNC_FD set to the stale file descriptor number.
Then press ^A to activate the fork. This will set the fd parameter to the same number as _ZSH_AUTOSUGGEST_ASYNC_FD.
Then type another character e.g. "a" to trigger an async request. This will print a "No handler installed" error and close the file descriptor pointed to by both _ZSH_AUTOSUGGEST_ASYNC_FD and fd.
Pressing ^B at this point will fail to read with a "bad file descriptor" error.