Update surfacelights-1.17.ckan

As per
https://forum.kerbalspaceprogram.com/index.php?/topic/139724-minimum-ksp-version-111-surface-mounted-lights-v117/
the KSP min version should be 1.11.0

Thanks for another one!
This one will be slightly more complicated because it's the current version; we will want to go "upstream" to where this data comes from to fix it, so the automated systems will handle it properly...
Try editing here:

https://github.com/ihsoft/SurfaceLights/edit/master/SurfaceLights.version

That's where the info is coming from now, so updating it will propagate through to CKAN. You can create another pull request using essentially the same steps, but @ihsoft will review it instead of the CKAN team.

Thanks for another one!
This one will be slightly more complicated because it's the current version; we will want to go "upstream" to where this data comes from to fix it, so the automated systems will handle it properly...
Try editing here:

https://github.com/ihsoft/SurfaceLights/edit/master/SurfaceLights.version

That's where the info is coming from now, so updating it will propagate through to CKAN. You can create another pull request using essentially the same steps, but @ihsoft will review it instead of the CKAN team.

I see... so for a current version, PR should be created in the mod author's repository, for older versions directly at CKAN?

I see... so for a current version, PR should be created in the mod author's repository, for older versions directly at CKAN?

Yeah, that's how it works for mods with version files. For mods without version files, any number of other hacks might be in place that would need updating. It depends on the specific mod, so you can keep submitting things here at first and we'll figure out what to do.

Yeah, that's how it works for mods with version files. For mods without version files, any number of other hacks might be in place that would need updating. It depends on the specific mod, so you can keep submitting things here at first and we'll figure out what to do.

(Xref ihsoft/SurfaceLights#35)

(Xref ihsoft/SurfaceLights#35)

Ok, done.
And how would I cancel/delete my PR here?

Ok, done.
And how would I cancel/delete my PR here?

There's a button under the text box:

But you might as well wait till the other PR gets merged, in case we do need to make any other changes on the CKAN side.

There's a button under the text box:

But you might as well wait till the other PR gets merged, in case we do need to make any other changes on the CKAN side.

Got it, thanks! I'll leave this PR then as it is now.

Got it, thanks! I'll leave this PR then as it is now.

The other PR's changes have come through:  5630f29b90f51109e28137899e78404d16ab9442
Nice work! :tada:

The other PR's changes have come through:  5630f29b90f51109e28137899e78404d16ab9442
Nice work! :tada:


deleted message has an undefined deletedAt value

I was expecting some way of checking if a specific message was deleted since it's not actually deleted (the content is just updated to "DELETED"). So if the user just typed in "DELETED" there's no way to check if it was actually deleted since the deletedAt is still undefined even if the message was deleted:

Hi @anchetaWern.
This is definitely a bug! Thanks for reporting it, we'll look into it soon.


Add recipe to example bot configs.

Closes #9886.

yep, that would be great. Separate PR or in here?


Why my VS Code version is consuming too much memory?

I have three questions:

first of all why do I have eight process of VS Code?

then why VS Code is consuming something like 522096KB of memory? Isn't that too much?
and last, if electron allow 64-bit build why VSC still target 32-bit ?http://electron.atom.io/docs/v0.36.0/development/build-instructions-windows/#64bit-build

Extra info:

I'm running windows 7 ultimate x64. 6GB memory, and this processor http://www.notebookcheck.net/AMD-A-Series-A6-3400M-Notebook-Processor.55753.0.html. VSC version 0.10.6
I took that screenshot with a small project (12 files, and 18 folders) on VSC, and with no file editing.

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


Fixed IOTA API Builder

This PR is a small refactor of the IOTA builder, to get it effectively accept host, protocol and port overrides.
Without this change:
IotaAPI proxy = new IotaAPI.Builder().host("somewhere_over_the_rainbow").build();

yields:
09:50:54.540 [main] DEBUG jota.IotaAPICore - Jota-API Java proxy pointing to node url: 'http://localhost:14265'

With this change:
09:51:44.421 [main] DEBUG jota.IotaAPICore - Jota-API Java proxy pointing to node url: 'http://somewhere_over_the_rainbow:14265'

Please PR to the dev branch.


HDFS-17300. [SBN READ] A rpc call in Observer should throw ObserverRetryOnActiveException if its stateid is always lower than client stateid for a configured time.

…ateid is always delayed with Active Namenode for a period of time

Description of PR
JIRA:       HDFS-17300
Now when Observer is enable, Observer will update its stateid through that EditLogTailer near-real-time tailing editlog form Active Namenode.  And if a rpc call's stateid is lower than client stateid which may update from active namenode with msync, the call will be requeued into callqueue.
This PR is intend to if a rpc call's stateid is always lower than client statid for a configured time , the call should throw ObserverRetryOnActiveException for client and client will go to active namenode for processing.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m  2s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 14s

trunk passed

+1 :green_heart:
compile
8m 40s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
7m 45s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
2m  3s

trunk passed

+1 :green_heart:
mvnsite
1m 40s

trunk passed

+1 :green_heart:
javadoc
1m 18s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 33s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

-1 :x:
spotbugs
1m 45s
/branch-spotbugs-hadoop-hdfs-project_hadoop-hdfs-warnings.html
hadoop-hdfs-project/hadoop-hdfs in trunk has 1 extant spotbugs warnings.

+1 :green_heart:
shadedclient
21m  1s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  4s

the patch passed

+1 :green_heart:
compile
8m  9s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
8m  9s

the patch passed

+1 :green_heart:
compile
7m 37s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
7m 37s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
2m  2s

the patch passed

+1 :green_heart:
mvnsite
1m 44s

the patch passed

+1 :green_heart:
javadoc
1m 14s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 43s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
3m 22s

the patch passed

+1 :green_heart:
shadedclient
21m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
15m 58s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

-1 :x:
unit
186m 47s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

335m 31s

Reason
Tests

Failed junit tests
hadoop.conf.TestCommonConfigurationFields

hadoop.hdfs.server.datanode.TestDirectoryScanner

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6414

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint

uname
Linux 388e1a351c90 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c589b62974209b5fbf08716838757f56b9882dda

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/1/testReport/

Max. process+thread count
4145 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m 54s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 11s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 29s

trunk passed

+1 :green_heart:
compile
8m 34s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
7m 45s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
2m  1s

trunk passed

+1 :green_heart:
mvnsite
1m 38s

trunk passed

+1 :green_heart:
javadoc
1m 18s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 32s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
3m  8s

trunk passed

+1 :green_heart:
shadedclient
21m 42s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  7s

the patch passed

+1 :green_heart:
compile
8m 15s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
8m 15s

the patch passed

+1 :green_heart:
compile
7m 50s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
7m 50s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 58s

the patch passed

+1 :green_heart:
mvnsite
1m 37s

the patch passed

+1 :green_heart:
javadoc
1m 11s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 31s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
3m 18s

the patch passed

+1 :green_heart:
shadedclient
21m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 40s

hadoop-common in the patch passed.

-1 :x:
unit
191m 22s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 38s

The patch does not generate ASF License warnings.

347m  4s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDirectoryScanner

hadoop.hdfs.TestErasureCodingPolicies

hadoop.hdfs.server.datanode.fsdataset.impl.TestFsDatasetImpl

hadoop.hdfs.TestDistributedFileSystemWithECFileWithRandomECPolicy

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6414

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint

uname
Linux 5eea4a21e82e 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 56101db610b19013c3a1fa57a61afb7845cd3971

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/2/testReport/

Max. process+thread count
3824 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 21s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
13m 59s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
19m 48s

trunk passed

+1 :green_heart:
compile
8m 32s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
7m 55s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
checkstyle
2m  5s

trunk passed

+1 :green_heart:
mvnsite
1m 40s

trunk passed

+1 :green_heart:
javadoc
1m 20s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
3m 12s

trunk passed

+1 :green_heart:
shadedclient
21m 37s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  8s

the patch passed

+1 :green_heart:
compile
7m 58s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
7m 58s

the patch passed

+1 :green_heart:
compile
7m 39s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
7m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 57s

the patch passed

+1 :green_heart:
mvnsite
1m 41s

the patch passed

+1 :green_heart:
javadoc
1m 21s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 41s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
spotbugs
3m 16s

the patch passed

+1 :green_heart:
shadedclient
20m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 45s

hadoop-common in the patch passed.

+1 :green_heart:
unit
187m 18s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

335m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6414

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets xmllint

uname
Linux 944f1f3dd85f 5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 3253b3ba230da6b7d9ffadefcd83dfc3506275b6

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/3/testReport/

Max. process+thread count
3836 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6414/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Bump supported Wagtail version to "< 3"

Currently cannot test an 2.12rc1 because of the wagtail>=2.5, <2.12 constraint :/

Thanks for pointing this out @zerolab, this has now been fixed in the latest release. 0.5.0

Thanks for pointing this out @zerolab, this has now been fixed in the latest release. 0.5.0


Honor removed review request

Fixes #9.

OK addressed, also I had missed to add the test, oops.

Good going, @zcorpan!


Feature: next/prev video button using turborepo structure

This pull request Resolves #811
i have already made a pr using existing repo structure. so this pr has all those features, Also i have added feature of prev content button.
but since we are planning to use the turborepo structure as discussed in pr #787, i have implemented the feature using this  repo by hitesh.
there were no merge issues when i merged my main branch which was uptodate with current main repo ,with turborepo branch.
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

closing this for now, will wait until we dont merge the monorepo structure


Xcode archiving fails with SPM

Description
I'm using realm-cocoa 10.1.1, which depends on realm-core 10.0.0. The dependency is managed using Swift Package Manager.
Goals
I'm trying to archive an iOS app that uses Realm(Swift) integrated via Swift Package Manager
Expected Results
The app is archived for distribution
Actual Results
This error is produced:

The error actually happens in realm-core, but they told me to open an issue here.
Steps for others to Reproduce

Create a new iOS app in Xcode
Add the dependency to Realm via Swift Package Manager
Try to archive the project

Code Sample
n/a
Version of Realm and Tooling
Realm framework version:
Realm Cocoa: 10.1.1
Realm Core: 10.0.0
Realm Object Server version: not used
Xcode version: 12.1
iOS/OSX version: iOS 11-14.1
Dependency manager + version: Swift Package Manager 5.3

@xavierLowmiller The minimum deployment target when using SPM is iOS 11, changing your project to support a minimum version of iOS 11 should help.

Our main project only supports iOS 11 and up, and my test project to reproduce the issue is iOS 14+.
I think that Realm Core's Package.swift file should be limited to iOS 11+, like Realm Cocoa's Package.swift file:
platforms: [
        .macOS(.v10_10),
        .iOS(.v11),
        .tvOS(.v9),
        .watchOS(.v2)
    ],

@xavierLowmiller So all targets in your project are iOS 11+ and it still gives this issue trying to archive?

Yes. Adding the lines to realm-core's Package.swift locally file resolves the issue for me.

Solved by https://github.com/realm/realm-core/pull/4039.

@xavierLowmiller I've got the same problem, I don't understand how did you solve it ?
can you give a bit more detail ?
Thank-you very much

It won't work out of the box until a new version of realm-core is released. Until then you can add an explicit dependency to realm-core pointing at the current master.

Adding RealmCore git: https://github.com/realm/realm-core branch: master
Seam to work ! thank-you for you very quick answer !!

It won't work out of the box until a new version of realm-core is released. Until then you can add an explicit dependency to realm-core pointing at the current master.

Tried that, but it didn't work.
Swift package target 'RealmCore' is linked as a static library by 'TestRealm' and 'RealmCoreDynamic'. This will result in duplication of library code.
If you know the reason for this, I'd be interested to know. But for now I'll just use CocoaPods until the SPM version is ready.
Thanks


Expose Producer function type

There was already an open PR but hasnt been addressed since Aug 18 2022
PR for this issue https://github.com/immerjs/immer/issues/955
Co-authored-by: @feihexyz

The PR was indeed waiting for a new submission, but now edited the file directly on the PR instead.


Add an underscore to the valid VAR description

Right now a valid long name var is:
Starts with a alpha char a-z
then  0-9 and a-z and . are valid
Would like to add _ as valid
This would make editing from an external editor (Windows / Linux) WAY easier.

Underscore characters in symbol names supported in commit dde8cba


Fetching collections with data files

Hi,
I'm API fetching three collections using three different data files. When I try {% sitemap  datafile %} I'm getting an error EmptySitemap: You ended the stream without writing anything.
Is there a way to use your plugin with such configuration, where collections are not coming from folders nor as custom collections defined in .eleventy.js?
Cheers.

Hi @WebShapedBiz ,
I've just pushed an example that works with data files and a small fix so that items without the data bag don't break.
Have a look at it and let me know if it helps your case.
Cheers.

Hi @WebShapedBiz ,
I've just pushed an example that works with data files and a small fix so that items without the data bag don't break.
Have a look at it and let me know if it helps your case.
Cheers.

Thank you @nunof07 for your time and effort, but I was pressed with time and moved on, making my own ad-hoc solution. It would be nice though if one could pass all the data files for which there should be a sitemap, something like {% sitemap file1, subfolder.file2 %} and end up with a sitemap like this.
Cheers.

Thank you @nunof07 for your time and effort, but I was pressed with time and moved on, making my own ad-hoc solution. It would be nice though if one could pass all the data files for which there should be a sitemap, something like {% sitemap file1, subfolder.file2 %} and end up with a sitemap like this.
Cheers.

That's not a bad idea, adding support for sitemap indexes, although it would require a lot of changes to the current plugin and it's out of my plans for the moment.

That's not a bad idea, adding support for sitemap indexes, although it would require a lot of changes to the current plugin and it's out of my plans for the moment.


Feature: Program simplification variant that removes unused calibrations

When users build Quil-T programs, they often add the full set of production calibrations to the Quil program. This makes the program very large to persist and slower than necessary to parse. Given the set of instructions in the program, it would be desirable to remove all of unused Quil-T calibrations, frames, and waveforms. For feature completeness, it should also be considered to remove any DEFGATE or DEFCIRCUIT that are not referred to.
This is similar to the existing Program.into_simplified(), except that the calibrations would not be expanded. It may be most appropriate for this feature to be implemented here first, and then exposed suitably through pyquil.

Further suggestion: In common use cases, users bring a Program with instructions and some optional subset of new calibrations, frames and waveforms, meant to support novel instructions or to override those available from a prior process. In the override case it is not preferred to add inconsistent duplicates to a single Program and rely on some ordering rule to resolve. It might be preferred to provide a Program to resolve, and then a (potentially empty) ordered list of other calibration-only Programs which are successively used to resolve calibrations, frames and waveforms. Any matched across that ordered resolution fold up into the final result.


Include only shader throws an exception

I think I stumbled upon an edge case. I have a shader that basically just includes another shader like this:
#include <other_shader.hlsl>
This shader fails parsing in PreProcessor::Process() and throws the following exceptions:
Exception thrown at 0x00007FF92430A388: Microsoft C++ exception: std::runtime_error at memory location 0x00000054CF3D5400.
Exception thrown at 0x00007FF92430A388: Microsoft C++ exception: Xsc::Report at memory location 0x00000054CF3D2A50.

I can't reproduce this issue without more information.
What does the other_shader.hlsl file look like and what are the compiler options?
I just tried xsc -PP -Valid include_test.hlsl where the input file only includes an empty other_shader.hlsl file.
Nothing problamatic happens.

You are right it's probably not related to that. I was digging into this a bit deeper and I think the issue is that I haven't found a way to set the defines we use on the HLSL compiler side. The HLSL compiler has a parameter that accepts an arbitrary list of defines, I can't see anything similar in XShaderCompiler at the moment. Am I just missing it somehow?

I'm specifically talking about the pDefines parameter of D3DXCompileShader.
You are right that I can add it to the string, I was just wondering if there is a more elegant solution.


NEW: FreezeTimezoneNow()

Add a context manager / decorator to mock django.utils.timezone.now() with a fixed datetime.
Freezegun is nice. But it will replace the datetime object. e.g.: repr() output is different. This may be a problem in some tests.

Codecov Report

Merging #146 (1477e6e) into master (b158f30) will increase coverage by 0.03%.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##           master     #146      +/-   ##
==========================================
+ Coverage   90.98%   91.01%   +0.03%
==========================================
  Files          66       66
  Lines        2340     2349       +9
  Branches      419      419
==========================================
+ Hits         2129     2138       +9
  Misses        141      141
  Partials       70       70

Files
Coverage Δ

bx_django_utils/test_utils/datetime.py
100.00% <100.00%> (ø)


Easier-to-perform actions on issues

Right now, to perform an action (close, add label, etc.) on an issue, a user must go to the issue's page. This can be burdensome if a user wants to perform an action on several issues, as they have to navigate to each issue's page.
It would be cool if we did something like Github, where you can perform actions on several issues from the issues page.
I would be happy to work on this, but just want to confirm there is interest.

Please do it. I just put this in v1.2. But if you are faster enough, I don't mind put it to v1.1.

resolved by #926


Can't compile

I followed the instructions in the README, and am getting this error:
In file included from /home/misa_n/dev/builds/wwise-audio-tools/src/wwtools/bnk.cpp:7:
/home/misa_n/dev/builds/wwise-audio-tools/include/wwtools/bnk.hpp:61:47: error: ‘uint32_t’ in namespace ‘std’ does not name a type; did you mean ‘wint_t’?
   61 | std::string get_event_name_from_id(const std::uint32_t &event_id);
      |                                               ^~~~~~~~
      |                                               wint_t
/home/misa_n/dev/builds/wwise-audio-tools/src/wwtools/bnk.cpp:270:47: error: ‘uint32_t’ in namespace ‘std’ does not name a type; did you mean ‘wint_t’?
  270 | std::string get_event_name_from_id(const std::uint32_t &event_id) {
      |                                               ^~~~~~~~
      |                                               wint_t

I'm unable to replicate this issue. Could you please indicate your operating system and compiler?

I'm using Manjaro Linux KDE, latest version. Unfortunately I don't really understand C(++) development at all, so I'm not sure how to get you the information you need... I did just think to run cmake -B build again, and it looks like that might be helpful?
-- The C compiler identification is GNU 13.2.1
-- The CXX compiler identification is GNU 13.2.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
PACKED_CODEBOOKS_AOTUV not set or set as off. Using data from packed_codebooks.bin.
-- Configuring ogg 1.3.5
-- Looking for include file inttypes.h
-- Looking for include file inttypes.h - found
-- Looking for include file stdint.h
-- Looking for include file stdint.h - found
-- Looking for include file sys/types.h
-- Looking for include file sys/types.h - found
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of int16_t
-- Check size of int16_t - done
-- Check size of uint16_t
-- Check size of uint16_t - done
-- Check size of u_int16_t
-- Check size of u_int16_t - done
-- Check size of int32_t
-- Check size of int32_t - done
-- Check size of uint32_t
-- Check size of uint32_t - done
-- Check size of u_int32_t
-- Check size of u_int32_t - done
-- Check size of int64_t
-- Check size of int64_t - done
-- Check size of short
-- Check size of short - done
-- Check size of int
-- Check size of int - done
-- Check size of long
-- Check size of long - done
-- Check size of long long
-- Check size of long long - done
-- Configuring vorbis 1.3.7
-- Looking for floor in m
-- Looking for floor in m - found
-- Configuring done (5.7s)
-- Generating done (0.0s)
-- Build files have been written to: /home/misa_n/dev/builds/wwise-audio-tools/build

Could you try adding #include <cstdint> at the top of any files that are giving this issue? In your case that seems to be bnk.cpp at least.

That fixed it, thanks! I imagine adding that line to the file in general doesn't cause any problems on other systems? Then that'd also make the AUR package work.

If possible, would you mind making a PR with that? Just add the include directive and I'll merge it and update the AUR package as well.

sure, I can do that: #18


Display High scores as a menu

Similarly as an item bag or History is displayed as a menu. When an item of the menu is selected, show details of the score record: all the components of the score and how they add up to the total; perhaps some extra info, like lost teammates, killed enemies, detailed cause of death and name of the last party member/detailed way of winning. Then add the high scores menu as a submenu to the ~ lore menu and/or to dashboard.
Also swap the current high score display at game end with the new one (just put it at the end of the current sequence of gameover menus with loot, foes, etc.). When doing that, make sure to show the menu with the current score record highlighted (menu cursor over that item).
This will require minor changes to the high score format, bigger changes to its presentation and the biggest element will be the new menu, perhaps with some minor extensions to the generic menu mechanisms.

In the high score record show also the amount of gold collected, because this is no longer covered in the score (only the percentage counts). In this way the player will not feel completely cheated when he goes to a great length to create a new precious gem and it doesn't affect his score --- it will affect his score record at least (and it's already shown in the gameover blurb).

Perhaps also show this submenu somehow as part of the main menu or make it enterable from it or at least from the dashboard.
See also #36 and #183.

Related ideas: it should be easy to see high scores for the currently running scenarios, with lots of detail for comparison with our current run (e.g., to beat the previous individual stats, not only the overall score).
Also, try to give at least the score details in a way that is story-related, and not dry technical itemization. Either generate the texts really smartly or add another description field to scenario that conveys the scoring in a story-related manner and pray it doesn't get out of sync with the actuall score polynomial formula.

From a chat with Pug: high score is saved permanently, but it holds little detail --- perhaps clicking on the high score entry should display again the many screens of stuff from the game in question, the same that are displayed at game over?

A more ambitious goal is to keep savefiles from previous games and enter the games when a high score menu item is selected. We already have the functionality that the player can stay in a game one turn after game over, so we could use that. Additionally, it would be great to permit viewing the whole game over stats menu slideshow (enough info is in the savegame).
A tricky point may be to go back to the original savefile after entering a savefile from the high score menu. Probably making sure the files are saved should be enough and then the last savefile should be present in the high scores menu, showing the score so far and marked as a non-finished game. Then we don't have to remember which savefile was viewed before, but we can just jump between savefiles, play a bit or review stats, save, try another.
In this way, the feature evolves into having many games active at once, though only one played. This is a sensible feature, though it should be disabled in the web version of the game not to overflow the local web storage.


[Test Framework] Fix panic if echo creation fails

This fixes a panic that will occur if echo creation fails before the workload manager is created.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@nmittler: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
d16c2ea3418f2aeb2b815697de0c46d7d065e3ba
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


[frontend] checklist page overflow issue on mobile/french

Overflow control on mobile devices.  It was found that CSS grid is the culprit.  Made the content a block on smaller devices and grid on small and up viewports.

I don't see why grid would be the issue and only an issue with french content. It must be something else.

Maybe, but I have no idea what it could be and quite frankly I'm frustrated I can't figure it out (well this solution actually does work).  I've tried several permutations of adding different classes to parent containers and I can't get it not overflow.  It's not the French content per se, it just happens in French since there's more text.

I don't see why grid would be the issue and only an issue with french content. It must be something else.

Maybe, but I have no idea what it could be and quite frankly I'm frustrated I can't figure it out (well this solution actually does work). I've tried several permutations of adding different classes to parent containers and I can't get it to not overflow. It's not the French content per se, it just happens in French since there's more text.

The following content cause the issue.


Fixed yaml model (insecureSkipTlsVerify)

Field insecureSkipTlsVerify was incorrectly put in AuthInfo instead of Datacenter. Therefore, generated .yaml config bundles were invalid.

@avelanarius

I'll need to take a look at the python driver, to see if we read it from the correct place. (we don't do validation...


Microsoft 365 learning pathways template failed

Hi
I tryed to deploy Microsoft 365 learning path on your tenant.
I got following error:
Your request to provision
"Microsoft 365 learning pathways"
template failed!
correlation ID: 9c3e4df6-c454-443c-a6eb-4d5870707e37
please help

It looks like most content got deployed but the two pages CustomLearningAdmins and CustomLearningViewer hav only strange content

Hi,
Thanks for using the Look Book site. This seems to be a random hiccup on the SharePoint side which would imply that the template should work properly if you try it one more time. Seems that the provisioning did succeed partially. Can you test this one more time and, in case of any failure, share the updated Correlation ID (by creating a new issue) for us to double-check the flow. Thanks.


Issue/3872 fix doc link check

Description
Update dock link check ignore list to ignore all docker ips.
closes #3872
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

Merged into branches master in f2c2badde2efa1629988d1b1ba6e170e2f21a99e

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.


Document why bintray is better than packagecloud

I'm a huge fan of packagecloud, but we're currently using bintray. But looking at our use case, I can't justify us switching because:

we want to host mac (& maybe someday windows) packages
we want a landing page for installing, and bintray lets us point back to the project

Are there any other benefits to bintray over packagecloud or github releases?

I really have no opinion.  Simply, I had heard of bintray, and had not heard of packagecloud - I've distributed a lot of stuff via source, but not via large binaries, so I just grabbed whatever seemed simplest.  It's probably not the best.


internal/pkg/scorecard/plugins: return an error if no CRs exist in alm-examples w/o cr-manifest set

Description of the change: check if CRs are present when parsing metadata.annotations['alm-examples'].
Motivation for the change: see #1780
Closes #1780

Before you merge, can you also update the CHANGELOG?

/retest

/test e2e-aws-go

/test e2e-aws-go


Profile export/import does not include extension Enabled setting

As I understand profiles, we should be able to save a profile with a full set of extension details, disable some extensions, save another profile with this reduced extension set, then restore the first to get all extension settings back. That's not what I'm seeing.
Version: 1.74.2 (system setup)
Commit: e8a3071ea4344d9d48ef8a4df2c097372b0c5161
Date: 2022-12-20T10:29:14.590Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No
Steps to Reproduce:

Open a workspace with many enabled extensions.
Export a profile "v1", extensions only, all other options unchecked.
Disable the top 10 extensions.
Reload and verify the extensions are disabled.
Export a profile "v2", extensions only, all other options unchecked.
Import profile "v1".

Expectation: Disabled extensions will re-enable.
Actual:

All extensions seemed to reinstall or update.
The disabled extensions remained disabled.

Reload, no change.
Close workspace and re-open, no change.

Issue 1: It would improve the UX/DX if existing extensions with correct configuration are not reloaded on profile import.
Issue 2: I don't see a field in .code-profile data for an Enabled status - even in a full export with all options checked. It seems obvious that the import doesn't restore the setting because export isn't saving it.

May I know why you want to export an installed extension that is disabled? I do not see a reason to import a disabled extension?

My 2 cents here
Its related to #40239 maybe this helps.
We are trying to find a solution, how we can have a workspace with extension A + B enabled, but not C.
In an other workspace/folder we would like to have maybe A + C enabled, but not B.
This all started with some incompatibility of extensions, but also simply makes sense, if you think, that not all projects one works on, does need all extensions. Some projects simply don't need some extensions, and it would be nice we can manage this somehow in workspace or other settings.

@sandy081 thanks - you've been in on this stuff since the start.  With this ticket I'm demonstrating that since the Enabled status of extensions is not exported, it's also not imported, and therefore the target environment does not look like the source. Is that a bug per-spec, or was this a design decision?
In #40239 it was suggested that Profiles might be a solution to the challenge : "Enable/disable extensions from config file".
This ticket is evidence that Profile export/import is not a solution - yet. If this ticket is processed and we can use profiles to enabled/disable extensions, then we can close that ticket. If not, then many of us will look forward to new comments from the team about what can be done.
HTH - TY

@Cyclodex

My 2 cents here
Its related to https://github.com/microsoft/vscode/issues/40239 maybe this helps.
We are trying to find a solution, how we can have a workspace with extension A + B enabled, but not C.
In an other workspace/folder we would like to have maybe A + C enabled, but not B.

I do not want to say profiles is the solution for the above issue. But if you want to use different set of extensions for different workspaces using profiles it is possible like below

Workspace 1: Use a profile with Extension A and Extension B
Workspace 2: Use a profile with Extension A and Extension C

Whether an extension is installed or enabled or disabled is an implementation detail IMO.

 With this ticket I'm demonstrating that since the Enabled status of extensions is not exported, it's also not imported, and therefore the target environment does not look like the source. Is that a bug per-spec, or was this a design decision?

Yes, your understanding is correct. We can export an extension in the profile even if it is disabled and when the profile is imported, the extension is installed and disabled. How different is it to not to include this extension at all? You still get the same running environment (this is more considered). If you want to have a new extension in the profile, you can simply install it.

because there's nothing in the profile to tell it to change state.

I am not sure what you mean by this. The exported profile file has already have the information of enablement. So when importing the extension is enabled/disabled accordingly.

I'm saying, that if the extension is enabled and we save the profile, the extension is not enabled on profile import ... because there's nothing in the profile to tell it to change state.

Why do not you want extension to be enabled when you import a profile that has extension enabled?

And if the extension is disabled and we save the profile, and the extension is already enabled in the target, the extension is not disabled on profile import ... because there's nothing in the profile to tell it to change state.

On the target you will not have any extensions except builtin extensions. If an built in extension is marked as disabled, after importing the profile, extension is marked as disabled.
As said, at present an installed extension (not builtin) will not be exported if it is disabled in the source.
Actually I have to say, I am not sure what we are trying to come up here. To simplify our discussion are we talking about the following statement or do you have more other thoughts?
Ability to export an user installed extension that is disabled in a profile and ability to import that profile and install that extension in the target and disable it

On the target you will not have any extensions except builtin extensions

That's only one possible use case, in a new installation. We all have VSCode already installed and configured. As noted in 40239 many of us want to import and occasionally change a standard set of extensions across systems.
If a source system and a target system have the same extension, the profile should export the state of the extension's enablement as well as the state of its existence. In the current platform: If the extension is already installed on the target, the new state is not changed to match the source. And if the extension is not installed on the target, it is installed with the default set to enabled, even if it was disabled when the profile was saved.

Actually I have to say, I am not sure what we are trying to come up here.
To simplify our discussion are we talking about the following statement
or do you have more other thoughts?
"Ability to export an user installed extension that is disabled in a profile,
and ability to import that profile and install that extension in the target and disable it"

That is correct. Use case:

Disable all of your extensions.

Why? Use cases are noted in 40239, including desire to whitelist extensions, eliminate cognitive load, and testing.

Load a workspace.
Set the extension to Enable in Workspace
Close Workspace.
Reload.
Enable all of your extensions so that you can export to profile, because that's how it works.
Export to profile.
Disable all of your extensions again because that's your preference.

If you're already at the "I don't want to do that" stage, +1 this issue.

Reload. Let's pretend you're on another machine.
Import the profile and Reload.
Disable all of your extensions again - yes, again, because that's your preference.

Tired yet?

Open the workspace.

Yay, the extension is enabled!

Close Workspace.
Export another profile now, with all of the extensions disabled.
Delete the top 10 or so extensions and Reload. Let's pretend you're on another machine.
Import the most recent profile.
Open the workspace.

Hey, I can't work without that first extension - what happened?

What happened is that the profile does not include disabled extensions. So on the target system the extension wasn't even installed for the "Enable (Workspace)" feature.
Here's another scenario to support profile including the enabled status.

Developer 1 wants Developer 2 to duplicate an issue.
She sends him the code, the .code-workspace, and a .code-profile.
He can't duplicate the issue.

Why? Because she has the same extensions that he has, but one of hers is enabled and the same one on his is disabled. The profile import doesn't change the enabled status on his target. Her system manifests the issue because of the enabled extension.
Again, my impression, which I believe is shared, is that the Profle Export/Import is intended to duplicate an environment so that it can be restored on a single system, and so that it can be replicated to other systems in a team. This ideal has not been realized because (1) profiles do not export disabled plugin specs, and (2) enabled plugins, when imported, do not override a disabled status on a target system.
Note from above a side-effect - that if a disabled plugin is not imported, then by definition the "Enable (Workspace)" setting is also not imported. I don't know where that setting is stored, but it's not in the .code-workspace or the .code-profile. It should be in the profile. I can think of at least another two tickets that could be created for this problem.
So now do we have any sense of agreement about the problems and solutions?

Today, my friend want me to share my VSCode environment to him, but I found the profile can't export the installed extension which is disabled. I had to use command line code --list-extensions > extensions.txt to export extensions ids to him. The settings sync extension had been marked depracated, and we can't install it any more. I think VSCode builtin settings sync and profiles together is designed to replace the settings sync extension, but now seems can't

@sandy081 Are we still trying to get a common understanding of the issue and use-case? Or are we in agreement that there is an issue that "might" later be addressed?
I'm not looking for a commitment for a change. I just want to know if we're still in discussion about whether or not there is an issue, if there is legit use case, justification for some level of prioritization in a milestone, etc.
Obviously others are now stumbling on this, so I'm hoping we can conclude that this is legitimate. If so, this might be the answer to #40239. Now that Profiles have been announced for production, I predict we'll see more dupes of this.
Thanks as always for your time.

I am sorry that I did not give this a read yet, will get back to this and let you know.

@TonyGravagno If I understand correctly, you want to use a single profile for a set of workspaces and for each workspace you want to enable specific set of extensions per workspace. You want to export that profile to some one else so that they can do the same for the same set of workspaces. This is instead of having profile per workspace?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Let's try again 🥲
We have "Feature Request: Enable/disable extensions from config file" #40239. Think of the ExtensionState as separate from workspaces and profiles. ExtensionState includes the list of installed extensions. A subset of that is the list of enabled extensions. A subset of that is the list of extensions that is disabled for the current workspace.
We're talking about how the following data stored:

We're looking for the ability to duplicate ExtensionState across environments.
How do we copy ExtensionState?
The above detail is not included in file *.code-workspace, nor in *.code.profile.
There have been attempts to access that data using third-party extensions, but those are not adequate, and they only exist because someone hid the configuration data and stored it in a proprietary format. Request 40239 asks for this data to be accessible in a standard format, ideally JSON in something like *.code.extensions. Then that file name would be saved in the .code-workspace file. This abstracts the extensions out from workspace and profile.
Now, some time ago it was suggested that since Profiles were still in development, we should try to use Profiles to achieve the goal, rather than trying to come up with a completely new concept. We have done that, but a number of us have found and reported that Profiles do not have the above detail.
IF Profiles are intended to share ExtensionState, this ticket details the issue.
If Profiles are NOT the way to go, let's close this and go back to 40239 to discuss how we might be able to export and import ExtensionState as a config file.
"Why?" you may ask again ... We have provided many use cases in both of these tickets. The simplest answer is that it is a common need for our environment to be consistent with another environment - across individuals, systems, and projects. This is exactly why we have package.json and package-lock.json, and tools like Composer. We cannot truly duplicate a VSCode environment because there is no defined way to save or restore ExtensionState.
The Workspace is great for some of this. Profiles are great for some of this. But, while Extensions are integrated with Workspaces, and there is some handling of Extensions in Profiles, neither of those components contain the entire ExtensionState for our access and manipulation.

@TonyGravagno If we include enablement state in the exported profile template file *.code-profile, then it will be just if the extension is enabled or not. May I know if this is good enough? It can contain if an extension is enabled/disabled at workspace level because there is no workspace semantics (identification) information stored in the profile file.

It can contain if an extension is enabled/disabled at workspace level because there is no workspace semantics (identification) information stored in the profile file.

It can? Or it can not?
@sandy081 to better understand your point, does it mean:
That you could just say if the extension is enabled or not. You can not identify or save, if the extension was disabled for the workspace or not. Correct?
I guess this would be okey, because if I understand correctly, the profile is something globally, and not specific to a workspace, right?

Side note: (I can create separate ticket if you want):
I am wondering: Is there any possibility (or is it planned in the future) to support the case:
That one could say: "Workspace X" uses "Profile Y"?
So is there a way, to kind of automate, that a specific workspace has a specific profile to use?
If you save these information on a "workspace" level, some other DEV loads your project, it would contain the workspace settings and applying the profile? Or would it more likely be an "shell" command, to start vs code with Workspace X and apply Profile Y?

It can? Or it can not?

I am sorry. It cannot. Updated my comment.

That you could just say if the extension is enabled or not. You can not identify or save, if the extension was disabled for the workspace or not. Correct?

Thats correct. To be clear, profile will contain that if an extension is enabled/disabled in that profile. For eg., if it is enabled in the profile and disabled in the workspace, extension state will be enabled in the exported profile.

I am wondering: Is there any possibility (or is it planned in the future) to support the case:
That one could say: "Workspace X" uses "Profile Y"?

It is not possible now and this needs workspace identification.

I think we have agreement. Thanks for working with us, @sandy081.
Thinking through a couple use cases...

Dev1 sends their profile to Dev2. Opening that profile results in all of the required extensions being loaded, and all extensions being disabled as defined in the profile.

What might happen to extensions that Dev2 has that are not mentioned in the profile? They would be untouched in the Dev2 setup, and thus not the recreating the same environment in the Dev2 system.
To recreate the DEV1 environment, DEV2 needs to create their own preferred profile for a later restore (not a bad idea for all of us to do this anyway). Then use the existing feature to "Disable all installed extensions". Then run with the DEV1 profile. On completion, DEV2 reloads the "backup" to restore the previous DEV2 settings to its preferred state.
Is that an acceptable workflow? To me it is. (Question open to all devs)
But that seems like a manual way of handling something that the tool is still not quite doing for us. The solution here would be for an option on CLI and menu for Import Profile, to disable all extensions prior to opening the new profile. Personally, I'd vote to let that be the Default, and the Option would be to Not disable all extensions, for those who actually do want a hybrid environment between DEV1 and DEV2.

Side note: Without doubt, someone will disable all extensions without a backup and then cry about the need to manually re-enable. I'm just documenting this as a procedural advisory/requirement, unless the profile import gets an enhancement to create up to three default backups prior to import.

One workstation, multiple instances of VSCode. Example: We have a JavaScript project up in one instance for front-end, and a PHP project for back-end, and we don't want to use the same extensions.

In this scenario I think extension management with Workspaces works.
However, it's important to have a common baseline of extensions for both workspaces which comes from a single profile, maybe opened by the CLI.

In summary: "If we include enablement state in the exported profile template file *.code-profile, then it will be just if the extension is enabled or not." Yes, this resolves this ticket and #40239.
I would just ask ... PLEASE don't encode this data in an unnecessarily "proprietary" manner. Use standard JSON. Then people can write code to manipulate the .code-profile details as desired, injecting or changing extension data as requested in 40239.
If we have agreement here, let's get concensus from the folks in #40239. Agreed?

To verify:

Create a custom profile by disabling some builtin and installed extensions
Export the profile
Delete the above custom profile
Import the profile and make sure extensions you disabled and disabled

Revision to verification steps - accounting for language issue and a more rigorous test:
To verify:

Create/export a custom profile P1, saving extension settings
Disable/enable some builtin and installed extensions (note original and new state)
Create/export another custom profile P2, saving extension settings
Import P1
Verify that extensions have the original state from step 1
Import P2
Verify that the extensions are disabled/enabled with the new state as they were at step 3
Import P1
Again the state of extension enablement should be returned to the original

On another system:

Create/export a custom profile P3, saving extension settings
Disable/enable some builtin and installed extensions (note original and new state)
Create/export another custom profile P4, saving extension settings
Import P2 from the first system
Verify that extensions look as they did at step 3 for the first system
Import P3
Verify that extensions have the original state from this system's step 1


Luacov

#90
add coverage in CI script
Not finished yet, do not merge now
I also have a plan to add C extension's coverage

For some unknown reasons, coverage of C part only works on Mac OS. I have no idea on how to deal with it. Maybe the version of gcc on linux on travis-CI is too low

A result could be found here. 50%, not so good

This is because we only use some basic APIs in xmake/tests  now.

Right. So tons of tests are needed

Done. It nearly makes me mad that C coverage does not work on linux. I quit. Do you have any idea on it? :disappointed:

Ok, I will look at it.

This branch allows you to push. If you found a solution, you could directly push to this branch. It might be clear in history @waruqi

got it

@TitanSnow It works on my ubuntu for your script in .traivis.yml
...

File 'src/xmake/machine.c'
Lines executed:83.33% of 102
Branches executed:84.21% of 76
Taken at least once:43.42% of 76
Calls executed:85.25% of 61
Creating 'src#xmake#machine.c.gcov'
Cannot open source file src/xmake/machine.c

Lines executed:48.06% of 21284
==> Python coveragepy not found
==> Searching for coverage reports in:
    + .
    -> Found 117 reports
==> Detecting git/mercurial file structure
==> Reading reports
    + ./src#xmake#os#exists.c.gcov bytes=1583
    + ./src#luajit#src#lj_asm.c.gcov bytes=70959
    + ./src#xmake#os#tmpdir.c.gcov bytes=1547
    + ./src#luajit#src#lj_lex.c.gcov bytes=2

...

So does my ubuntu. So I'm wondering if the version of gcc is too low on travis-ci

I have upgraded gcov to version 6 on travis-ci but seems has no use. Maybe upgrade gcc is also needed @waruqi

@TitanSnow Right, Incompatible *.gcno file version.  ./build/.objs/testgcov/src/main.c.gcno:version '406*', prefer '602*'

I have upgraded all. Maybe works

It works! :tada:

Great! 👍
I think we can remove these flags "-fprofile-arcs", "-ftest-coverage" if gcc and gcov have been updated to new version.

@waruqi No, we cannot. I have tried but it fails

I wanna remove coverage of luajit

Got same issue on jayl/jay, finally get it it work with this configuration !
matrix:
  include:
    # coverage build
    - os: linux
      dist: trusty
      compiler: gcc-5
      addons:
        apt:
          sources:
            - george-edison55-precise-backports
            - ubuntu-toolchain-r-test
          packages:
            - cmake
            - cmake-data
            - gcc-5
      install:
        - mkdir build && cd build
        - cmake -DCOVERAGE=ON -DCMAKE_BUILD_TYPE=Debug ..
        - make
        - cd ..
      after_success:
        - bash <(curl -s https://codecov.io/bash) -xgcov-5

(george-edison55-precise-backports is only for cmake)

👍

@uael I will try it. Thanks!

@uael Great, in this way sudo is not required anymore!

@waruqi In fact, codecov's coverage does not count the files not ran into so that it's higher than real number

@uael No homebrew addons on Travis? like:
addons:
        homebrew:
          packages:
            - dmd
            - rust

@waruqi
still waiting :cry:

@uael 😓

As I know sudo: false does not influence osx

I found ./core/build/.objs/xmake/src/xmake/os/chdir.c.gcno:version '408*', prefer '504*' in build. What's that?

@TitanSnow I have fixed it.


Bug related to not specifying polypath

Issues with taint being marked when POLYPATH=*
I think it's an integer overflow

POLYPATH is currently not supported.


Change 'Annotations' to 'Note'

@iaanw please double-check if this was addressed and close or merge the PR.


Function syntax highlight breaks macro syntax highlight

or is it the way it should be?

Verified it on my side. No it's not intentional.

Known limitation, but there is unfortunately currently no work in progress that I'm aware of to fix it.


Support forwarding without re-encrypting traffic

The current design for supporting hub-and-spoke connectivity assumes that the hub is a node participating in the zone. It would be incredibly valuable to support an architecture where the service can provide traffic forwarding without needing to re-encrypt the traffic. This would allow the service to provide connectivity without the service needing access to the actual traffic in a zone.

implemented in #1778


PhysiTech

PhysiTech and #3719

Close #3719

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@MohitGupta121 sir kindly review and merge this PR


Issue 90: Add additional instrumentation for flash messages.

This change addresses #90. It introduces a new debug log point that records the current state of the flash message cookie on every request. Using the custom log levels introduced in #171, developers can easily set the dream.flash log source to debug level to trace their flash messages. The flash message example (w-flash) has been updated to illustrate how to do this.
On some browsers (for example, Firefox) cookies are limited to a maximum of 4096 bytes; above this limit, a browser may drop the cookie. Since this can prevent flash messages from appearing, I've also included a warning log point to alert developers when their message content is too big.

Okay, I realized I have only trivial nits left, so I merged. Thanks for doing this with the several steps it took!


crop the image

after choosing the image,by the camera or from the gallery,
i should be able to #crop the image before press OK

It's not part of this library, but it's nice to add it in future

crop feature added.


Update Web3-Onboard Guide

Would be nice to make also a link to this article from the README of this repo:
https://github.com/lukso-network/web3-onboard-config


Attaching inverses of generators

In the labelled world, when we click to attach a generator, we need to search through every orientation in which that generator can be applied.

Closed by f06f0130d2bd9cc1d4b76cda536b8a4cb8d8f58f


Nuxi generate throws 500 error

Environment

Operating System: Linux
Node Version:     v18.16.0
Nuxt Version:     3.5.3
Nitro Version:    2.5.1
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
when we lauch nuxi generate, there is a lot of callings to "locales" sites that not exists :(
ERROR  [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost/pt/unsubscribe)   ERROR  [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost/pl/unsubscribe)
we have an url http://localhost:3000/unsuscribe but without lang
Describe the bug
when we lauch nuxi generate, there is a lot of callings to "locales" sites that not exists :(
ERROR  [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost/pt/unsubscribe)   ERROR  [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost/pl/unsubscribe)
we have an url http://localhost:3000/unsuscribe but without lang
Additional context
No response
Logs
No response

the fail its for strategy: 'no_prefix', of the module i18n...
But there is another error now
ERROR  [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost/test)
The callbackUrl is not correct, must be the same that api/auth

Hey @agracia-foticos!
Thanks for the issue - sounds like it couild be related to other parts of your setup. Can you please provide a full reproduction? So, a repo + some simple commands that will result in the error?
It's hard to debug this, as you yourself noticed: part of the error was related tio i18n!

It is also difficult for me to provide you with a functional environment.
Here you are an environment with a copy of our code related with auth and i18n
https://stackblitz.com/edit/nuxt-starter-wyfi9k
I hope I can help you

any advance?

I have the same issue is there any solution? after getting this error i tried with "ssr:false" then it complied but after run the complied files it given same error.

Hi,
I am having the same problem than both of you : everything was working perfectly, but I  received the following error after trying to activate https on dev server :
[16:18:33] [nuxt] [request error] [unhandled] [500] fetch failed (http://localhost:3000/api/auth/session?callbackUrl=http://localhost:3000/)
I have set in an env file:
AUTH_ORIGIN = 'https://localhost:3000'
NEXTAUTH_URL = 'https://localhost:3000'
as wel AUTH_SECRET and AUTH_NO_SECRET
I followed the exact config detailled in the Official Nuxt 3 page for https (https://nuxt.com/docs/api/configuration/nuxt-config#https) :
export default defineNuxtConfig({
  modules: ['@sidebase/nuxt-auth''],
  devServer: {
    https: {
      key: './myserver+3-key.pem',
      cert: './myserver+3.pem',
    },
  },
})

I will try to propose you a fresh install reproducible error (with typescript, as I am using this as well), and note all error and how I fixed them until this blocking error.
Gitlab repo will be found at this url :
1°)  fresh install : npx nuxi@latest init auth-localhost
2°) cd auth-localhost, and yarn install
3°) install nuxt-auth module : yarn add @sidebase/nuxt-auth
In nuxt.config.ts, I am already having this (typescript error) with this configuration :
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  devtools: { enabled: true },
  modules: [
    '@sidebase/nuxt-auth',
  ],
  auth: {
    provider: {
      type: 'authjs',
    },
    globalAppMiddleware: true,
})

Error (auth keyword not recognised, sorry in french)
``L`'argument de type '{ devtools: { enabled: boolean; }; modules: string[]; auth: { provider: { type: string; }; globalAppMiddleware: boolean; }; }' n'est pas attribuable au paramètre de type 'InputConfig<NuxtConfig, ConfigLayerMeta>'.
Un littéral d'objet peut uniquement spécifier des propriétés connues, et 'auth' n'existe pas dans le type 'InputConfig<NuxtConfig, ConfigLayerMeta>'.ts(2345)
(property) auth: {
provider: {
type: string;
};
globalAppMiddleware: boolean;
}

I solved this inserting an `auth.d.ts` file inside my `types` folder :

```ts
// Hack : copied from @/.nuxt/types/auth.d.ts

declare module '#auth' {
  const getServerSession: typeof import('./../node_modules/@sidebase/nuxt-auth/dist/runtime/server/services').getServerSession
  const getToken: typeof import('./../node_modules/@sidebase/nuxt-auth/dist/runtime/server/services').getToken
  const NuxtAuthHandler: typeof import('./../node_modules/@sidebase/nuxt-auth/dist/runtime/server/services').NuxtAuthHandler
  interface SessionData {
    id: string | number
  }
}

Try adding callbackUrl in your signIn like this: await signIn('google', { callbackUrl: '/' })

Hi, is there any workaround for this already? Can't put my application to production using reverse proxy in apache.

hi,, is any solution for this issue?, i have simillar issue while running npx nuxi generate

Same problem

Hi everyone,
Sorry this issue went under. So there are a few different issues going on here. From the original issue, I can say that nuxi generate does not work with the authjs provider as SSR is required for it to work properly.
if you are using the local provider from 0.6.0 you can render it statically.
I hope this may already answer some question.
I also see that some people were having issues with running a SSL certificate on dev servers, this is something unrelated to the original issue, AFAIK. I would recommend we open a new issue for this, as it became a little hard for me to properly follow along/get the current projects and reproduction links from the people still active in this thread!


chore: fix go releaser

main moved to root, so this config isn't required anymore

Codecov Report

Merging #189 (a272106) into develop (8e18ed5) will decrease coverage by 0.15%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop     #189      +/-   ##
===========================================
- Coverage    36.05%   35.90%   -0.16%
===========================================
  Files           47       47
  Lines         3938     3938
===========================================
- Hits          1420     1414       -6
- Misses        2392     2396       +4
- Partials       126      128       +2

Flag
Coverage Δ

unittests
35.90% <ø> (-0.16%)
:arrow_down:

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

Impacted Files
Coverage Δ

pkg/ghissue/buglink.go
90.32% <0.00%> (-9.68%)
:arrow_down:

pkg/utils/paths.go
5.55% <0.00%> (-5.56%)
: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 8e18ed5...a272106. Read the comment docs.


Add feature to install WireCloud widgets

Proposed changes
This PR adds feature to install WireCloud widgets.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
N/A

Codecov Report

Merging #40 (fd0185e) into main (467be14) will increase coverage by 0.89%.
The diff coverage is 83.33%.

@@            Coverage Diff             @@
##             main      #40      +/-   ##
==========================================
+ Coverage   72.39%   73.28%   +0.89%
==========================================
  Files           2        2
  Lines         547      554       +7
==========================================
+ Hits          396      406      +10
+ Misses        151      148       -3

Impacted Files
Coverage Δ

lets-fiware.sh
72.49% <83.33%> (+0.92%)
:arrow_up:

Continue to review full report at Codecov.

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


Unescape special chars on translate chain

Questions
Answers

Description?
There was encoded html chars on the configuration page

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes https://github.com/PrestaShop/PrestaShop/issues/23147.

How to test?
See issue

@PierreRambaud close it if you think this is not the right way at all


ApiResponse from custom meta annotations are ignored in certain case

https://github.com/swagger-api/swagger-core/blob/96b072caa8d178f7f81941c52725b7577c64eeca/modules/swagger-core/src/main/java/io/swagger/v3/core/util/ReflectionUtils.java#L321
Why is this only executed when the Array in the line above is null or empty? In this case ApiResponse Annotations made in a custom annotation to centralize error responses or other common responses like for example:
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.METHOD, ElementType.TYPE})
@ApiResponses(value = {
        @ApiResponse(
                responseCode = "500",
                description = "Returns Object of Type: MyException in case of an error." +
                " Please check the MyException for further details.",
                content = @Content(schema = @Schema(implementation = MyException.class))
        )
})
public @interface CommonResponses {}

Which later is used like this for example:
    @CommonResponses
    @Operation(
            summary = "Inserts a new thing",
            description = "Use this method to insert a new thing",
            operationId = "insertThing",
            tags = {"thing"}
    )
    @ApiResponse(responseCode = "201",
            description = "Returns the the created thing.",
            content = @Content(schema = @Schema(implementation = Result.class)),
            headers = {@Header(name = HttpHeaders.LOCATION, description = "The location of the newly created thing.")}
    )
    @ApiResponse(responseCode = "400",
            description = "Returns 400 if required parameters are missing.",
            content = @Content(schema = @Schema(implementation = Result.class))
    )
    @POST
    @Produces(MediaType.APPLICATION_JSON)
    public Response insertThing(
            @Context UriInfo uriInfo,
            @Context SecurityContext securityContext,
             Thing thing) {

        .....
        return Response.created(new URI(locationHeader)).entity(result).build();

    }

When using my CommonResponses like this, the 500 Response (would like to place some more there...) from that is ignored.
If I don't use ApiResponse annotations on the method itself, only then my meta annotation is picked up.
Is it possible to always include meta annotations or what's the point against doing this?
Thanks for reply / fixing this
/Soeren

fixed in #3931


Announcement on Temporary Support Reduction

I'm sorry to announce that for period of time that can lasts/varies from 1 to 2 weeks (as maximum) from now (02 Oct 2015), I'll not be able to supply support to this (and other open source projects).
Cause: I'm overwhelmed from duties caming from ordinary (not OSS) job orders.
I'll try not to completely blackout (if possible) my presence here, but please be patient if I reply late to issues or emails (I can even not reply at all during this period, sorry).
I'm here also to ask help in giving support to developers/users to project's main contributors (in no particular order): @nemec, @mizipzor, @Thilas, @gimmemoore.
Regards and thanks for understanding!
Yours,
Giacomo
P.S.: End of such period will be emphasized/confirmed from the closure of this issue.

I'm sorry to renew the "support lack period" to other 1-2 weeks (from now 13 Oct 2015); I'm quite sure (certainity 85%) this is the last time.
Sorry again, guys, I hope main contrib can help you... (If they have time).
The nature itself of the project will already helps you, it's OSS; hack it -> use private hacked version for a while and when I'll be back available we can even disucuss to merge your work w/ a PR if of public utility.
So at maximum extent first days of november this issue will be digitally killed and reduced to an useless junk sequence of 0 and 1, when I'll hit "Close and comment" buttton! (...and in GitHub DB system -- I don't know details -- this issue will be flagged as CLOSED).
:smile: Giacomo :smile_cat:

Support restored! Please be patient while I try to catch up with backward issues.
Giacomo :)


Find a cleaner way to change tile render color

I noted it in TileMap.cpp, I need to find a much better way to handle tile render color versus the clumsy nested if/else chain I've got going on. I'm at a point now where I want to be able to highlight tiles in different colors based on whether or not they're part of paths, comm ranges, etc.
A simple way to do this would be to add a NAS2D::Color_4ub member to the Tile class and get/set functions for it.
See #xxx about addressing potential issues with this method of tile coloration.

While talking to @DanRStevens about how to possibly handle this it occurred to me that the Tile could be modified to include a std::bitset as a means to indicate tilemap 'overlays' (e.g., connectedness, part of a route, covered by comm, etc.). It's a really simple way to do this and can even supplant the current bool flag in Tile.
I'm thinking the std::bitset could be used to index into a color table to determine which color to use to draw a tile. Should be a pretty quick lookup as I don't imagine there would be too many combinations (16 values assuming four flags).


use message to open duckplayer from overlay

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#993
#992  👈
#991
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @shakyShane and the rest of your teammates on  Graphite