Apex Trigger Deployment Errors

V2.8
Errors...
dlrs_CampaignMemberTest.testTrigger System.DmlException: Insert failed. First exception on row 0; first error: MALFORMED_ID, Invalid campaign id: null: [CampaignId] Class.dlrs.RollupService.testHandler: line 272, column 1 Class.dlrs_CampaignMemberTest.testTrigger: line 11, column 1
dlrs_ContactTest.testTrigger System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, ContactTrigger2: execution of BeforeInsert caused by: System.NullPointerException: Attempt to de-reference a null object Trigger.ContactTrigger2: line 9, column 1: [] Class.dlrs.RollupService.testHandler: line 272, column 1 Class.dlrs_ContactTest.testTrigger: line 11, column 1
Issues implies that the second error was fixed in a previous version (1.14?)
Not sure how the CampaignId can be malformed.
Rollup runs fine one-time on a "Developer" schedule.

I'm having a very similar error:
Error:
dlrs_CampaignMemberTest.testTrigger System.DmlException: Insert failed. First exception on row 0; first error: MALFORMED_ID, Invalid campaign id: null: [CampaignId] Class.dlrs.RollupService.testHandler: line 272, column 1 Class.dlrs_CampaignMemberTest.testTrigger: line 11, column 1
Also:
Warning:
dlrs_CampaignMemberTrigger:Test coverage of selected Apex Trigger is 0%, at least 75% test coverage is required
_

Have a look through some of the other issues using this child object, https://github.com/afawcett/declarative-lookup-rollup-summaries/search?q=CampaignMember&type=Issues&utf8=✓. You do need a little bit of custom code to get the test to pass for this object. Are you using a some custom test code in the Test Code field?

Thanks Andrew -
I should have checked resolved issues first.  Sorry about that.
I solved it on contact using the test code found in a resolved issue:
Campaign camp = new Campaign(Name = 'Test Campaign');
Insert camp;
Contact c = new Contact(LastName = 'Test');
Insert c;
    dlrs.RollupService.testHandler(new CampaignMember(CampaignId = camp.Id, ContactId = c.Id));

I will fiddle with it to get the same test code for Leads I assume?

Thanks @dionisus1122 for the update. Honestly i'm not a major user of the Leads object, so not sure, try it without first. 👍


Error when using 'awslocal configure list'

Environment:

awscli-local: 0.20 (from awscli_local-0.20-py3-none-any.whl)
localstack: 1.2.0
aws-cli/2.8.12 Python/3.10.8 Darwin/22.1.0 source/x86_64 prompt/off

When I used awslocal configure list, I got ERROR: Unable to find LocalStack endpoint for service "configure".
It should be used to verify the current configuration as the document said.

I can reproduce it as well

same thing

Any update on this?

I am having a same issue. Any feedback on this error?


<EMAIL_ADDRESS>hash check failed

Scoop Configuration

App:         extras/scoop-completion
URL:         https://github.com/Moeologist/scoop-completion/archive/v0.2.3.zip
First bytes: 50 4B 03 04 0A 00 00 00
Expected:    59fcda6e723b2c0bf7430668ccfb57086d82e9472733a01f9f7f9315768b5e5f
Actual:      c55a85e011cdfb03592691f52c5fb7076284dac01c1af87931fad36bcc0b1c65

> scoop download scoop-completion
INFO  Starting download for scoop-completion...
Loading v0.2.3.zip from cache
Checking hash of v0.2.3.zip ... ok.
'scoop-completion' (0.2.3) was downloaded successfully!
> (Get-FileHash .\scoop-completion#0.2.3#https_github.com_Moeologist_scoop-completion_archive_v0.2.3.zip).Hash
59FCDA6E723B2C0BF7430668CCFB57086D82E9472733A01F9F7F9315768B5E5F

please clear cache and reinstall.


Remove bosh spec property Labels as it conflicts with k8s-args node-labels property.

What this PR does / why we need it:

Remove confusion between k8s-args node-labels and bosh spec Labels. It is expected that we can use k8s-args to set flags for kubelet rather than using bosh spec flags. This PR preferences using k8s-args.
How can this PR be verified?
CI
Is there any change in kubo-deployment?
No
Is there any change in kubo-ci?
Yes, will add PR to add integration test for Labels
Does this affect upgrade, or is there any migration required?
Yes, people who have used Labels in the past will need to move their custom labels to be
k8s-args:
  node-labels: "comma delimited labels"

Which issue(s) this PR fixes:
Release note:

Remove bosh spec property `Labels` as it conflicts with k8s-args `node-labels` property.

lgtm


add support for json expression methods

This PR adds support for json expression methods mentioned in #4216

is_json_object
is_not_json_object
is_json_array
is_not_json_array
is_json_scalar
is_not_json_scalar

@guissalustiano , I moved json expression methods under PgTextExpressionMethods as you suggested. When it comes to SELECT NULL  ... I think that is how psql works and null will always will be returned, it applies to other methods as well. I added a test in is_json_scalar.


4-d Variable Output Using Standard Memory Mode

I used the "standard" option and ran into an issue.  If I tried to include soil moisture (4-d variable) in the configuration file I got the following error when the code tries to write to the netcdf files after it loads all the files in the current chunk:
Traceback (most recent call last):
  File "/glade/u/home/anewman/bin/vic_utils", line 5, in <module>
    pkg_resources.run_script('tonic==0.0.0.dev-2bf5167', 'vic_utils')
  File "/glade/apps/opt/python/2.7.7/gnu-westmere/4.8.2/lib/python2.7/site-packages/pkg_resources.py", line 534, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/glade/apps/opt/python/2.7.7/gnu-westmere/4.8.2/lib/python2.7/site-packages/pkg_resources.py", line 1441, in run_script
    exec(script_code, namespace, namespace)
  File "/glade/u/home/anewman/lib/python2.7/site-packages/tonic-0.0.0.dev_2bf5167-py2.7.egg/EGG-INFO/scripts/vic_utils", line 221, in <module>

  File "/glade/u/home/anewman/lib/python2.7/site-packages/tonic-0.0.0.dev_2bf5167-py2.7.egg/EGG-INFO/scripts/vic_utils", line 197, in main

  File "build/bdist.linux-x86_64/egg/tonic/models/vic/vic2netcdf.py", line 546, in _run
  File "build/bdist.linux-x86_64/egg/tonic/models/vic/vic2netcdf.py", line 896, in vic2nc
  File "build/bdist.linux-x86_64/egg/tonic/models/vic/vic2netcdf.py", line 459, in nc_add_data_standard
  File "netCDF4.pyx", line 3267, in netCDF4.Variable.__setitem__ (netCDF4.c:39658)
ValueError: total size of new array must be unchanged

I traced it back to line ~448:
self.f.variables[name][:, i, ys, xs]

is looking for something that is 2-dimensional while
p.df[sn].values[self.slice]

is only 1 dimensional with a length set at the number of time steps going into the current netcdf file.  If I removed soil moisture in the configuration file, I got this option to output properly, so it was an issue with 4-d variables.
I then made some modifications to the code and got it to work for 4-d variables.  This is really my first halfway serious go with python, so my syntactical understanding is limited, lots of potential for me to have messed the fix up in some fashion.
I ran the code a bunch and it worked fine.  It seemed a little slow, but there is lots of I/O both in and out so I didn't think much of it.  Then I got an email from our supercomputer system administration folks stating that my code was performing an excessive amount of disk writes to the same location.  They reported that the read rates were fine, but the output was many times the input.  That makes me think I fixed the code in an improper fashion so the netcdf writes are occurring an excessive number of times...
The changes are in the function: nc_add_data_standard.  What is the best way for me to post my "fixed" code?
Cheers,
Andy

Sounds like we have two issues here:

Standard mode slice bug: I think we can fix this for the 4-d var.  It sounds like a pretty simple fix that you may have already applied. This would be worth issuing a pull request against develop for.
Your sys admin is right, the standard mode makes a lot of writes.  You could try the big_memory mode or the original mode and see if that helps.  big_memory will be the fastest but, as you may glean from its name, it uses the most memory.  This mode reads and writes each file only once.

Hi Joe,  I've pushed to my fork.  It looks like I edited both the 3-d and 4-d output for the nc_add_data_standard function.  I can go ahead and issue the pull request.

On point 2:  Right, the standard mode would write after each chunk is read in.  Does it work like this:

Define the netcdf file with the full grid dimensions
Issue write commands to fill the portions of the grid as they are read in.  Something like netcdf_put_vara_*  would be used for each variable write.

I would think the total data writes would still be roughly equal to the total data read...  I was getting something on the order of 10x data being written than read.

I would think the total data writes would still be roughly equal to the total data read... I was getting something on the order of 10x data being written than read.

It probably depends how you chunk you dataset up.


updating bash_profile

Proposed changes
Consolidating some useful information. The following lines have to be added to the ~/.bash_profile for it to work. I pulled this information from https://docs.docker.com/compose/completion/.
I thought it would be useful to add it here so that all this info could be in one place.
if [ -f $(brew --prefix)/etc/bash_completion ]; then . $(brew --prefix)/etc/bash_completion fi
If not the above, the other command could be
 [ -f /usr/local/etc/bash_completion ] && . /usr/local/etc/bash_completion
which is displayed once you've installed bash-completion

@shin - PTAL - thank you!

area/compose label is misleading I think - this is one for the Desktop team :) That said, LGTM


Truncate with foreign key checks

Is your feature request related to a problem? Please describe.
It's currently not possible to truncate a table and also delete all associated data with it. We would like to truncate e.g. a customer table and have to also remove all associated data in other tables.
Describe the solution you'd like
Provide an additional table strategy which truncates with foreign key checks enabled.
Describe alternatives you've considered
none
Additional context
none

Hi!  There is already a truncate table strategy, does this work for you?
https://github.com/jerometwell/pynonymizer/blob/master/doc/strategyfiles.md#table-strategy-truncate

If i understand what you're trying to achieve ( cascading delete) then TRUNCATE won't work anyway.
IIRC truncate isn't suitable for tables with foreign keys.
You'd need a DELETE statement. Is this a feature you need?
As a workaround, you could add this as a before script:
scripts:
  before:
    - DELETE FROM table;

@jerometwell yes you are correct, TRUNCATE doesn't actually work with foreign keys. The before script works, but an official table strategy would be more handy I think.

@TitanNano in this scenario, would you have foreign key checks with CASCADE enabled? or were you implying that pynonymizer should do discovery also?
I'm just writing documentation and i want to be sure on the use-case.
I've started PR #23 for this issue. If you could take a look at the implementation I'd appreciate a second pair of eyes.

@jerometwell yes CASCADE is enabled in our scenario. I will have a look at your WIP.

This change has been merged into master and should go out with v1.13.0 - please test and report back if you can!

@jerometwell the new table strategy works as expected / described.


Update bitmos records to metadata in tokens.ts

Update bitmos records to metadata in tokens.ts

Summary by CodeRabbit

New Features

Added metadata for the BMOS token, enhancing token recognition and interaction capabilities within the platform.

missing file upload.  to resubmit


[SPARK-14334] [SQL] add toLocalIterator for Dataset/DataFrame

What changes were proposed in this pull request?
RDD.toLocalIterator() could be used to fetch one partition at a time to reduce the memory usage. Right now, for Dataset/Dataframe we have to use df.rdd.toLocalIterator, which is super slow also requires lots of memory (because of the Java serializer or even Kyro serializer).
This PR introduce an optimized toLocalIterator for Dataset/DataFrame, which is much faster and requires much less memory. For a partition with 5 millions rows, df.rdd.toIterator took about 100 seconds, but df.toIterator took less than 7 seconds. For 10 millions row, rdd.toIterator will crash (not enough memory) with 4G heap, but df.toLocalIterator could finished in 12 seconds.
The JDBC server has been updated to use DataFrame.toIterator.
How was this patch tested?
Existing tests.

cc @marmbrus @rxin

Test build #54714 has started for PR 12114 at commit 52d7520.

hm we need to think about the api -- this is a scala iterator right? it's going to be problematic for java users.
maybe we can have toLocalScalaIterator and toLocalJavaIterator, or just have toLocalIterator returning a Java iterator, and scala users can easily do the implicit conversion or using asScala anyway.

@rxin Good point, will use the Java iterator as public API.

Test build #54715 has started for PR 12114 at commit b12097e.

Test build #54716 has started for PR 12114 at commit e62d35a.

Test build #54715 has finished for PR 12114 at commit b12097e.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #54714 has finished for PR 12114 at commit 52d7520.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Test build #54716 has finished for PR 12114 at commit e62d35a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

cc @sameeragarwal for review

Test build #54869 has started for PR 12114 at commit 0f75cec.

Test build #54872 has started for PR 12114 at commit 34b3f1c.

LGTM

Test build #54869 has finished for PR 12114 at commit 0f75cec.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Test build #54872 has finished for PR 12114 at commit 34b3f1c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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


Remove the Gradient type and its module

As discussed in #218, the Gradient type has not gotten the attention it deserves and it's better to remove it in favor of other alternatives. This will also make the library more focused and easier to maintain. The predefined, named gradient constants are also removed.
Closed Issues

Closes #152, since the Gradient is now gone.
Closes #156, since the Gradient is now gone.

Breaking Change
Both Gradient and gradient::named are gone with no replacement. There are other, better alternatives out there.

I'm thinking of making it possible to multiply hues as if they are just regular numbers but will probably do that separately.

bors r+


Cant get this to compile my scss files

I went through the installation process, and when I activate meteor, I lose all my css styling.
the project runs correctly, but no style.
would love some help.
thanks!

Can you create a repo with a reproduction.

hey!
thanks for the quick reply. I tried working on it today and solved the problem, it was another add-on that messed it up when combined with this one.
thanks again!
Dean
Sent from my iPad

On 26 Apr 2016, at 9:43 PM, Seba Kerckhof<EMAIL_ADDRESS>wrote:
Can you create a repo with a reproduction.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


licenseSets do not work properly

See https://github.com/hazendaz/base-parent/tree/license-issue
Run on that branch, 'mvn license:format'.
Results in warning that
[WARNING] Parameter 'legacyConfigHeader' (user property 'license.header') is deprecated: use {@link LicenseSet#header}
But I updated it to use licenseSets
Without the update, see the master branch and do same.
That one gives 2 expected warnings.
[WARNING] Parameter 'legacyConfigExcludes' (user property 'license.excludes') is deprecated: use {@link LicenseSet#excludes}
[WARNING] Parameter 'legacyConfigHeader' (user property 'license.header') is deprecated: use {@link LicenseSet#header}
Looked at IT tests in this project and they do not seem to have this issue.  I cannot see anything different other than using all modern plugins from maven.  So I think the issue is present due to resolution.  Further, the injection points throughout this project are the same naming.  So from just looking at it, I cannot see how maven would not have issue here.  The legacy vs new should really be called something different IMO to avoid such conflicts.
@mathieucarbou Can you take a quick look at this and see if you see anything wrong?  I've persisted on the legacy now since 2020 so nearly 3 years and want to upgrade as maven 3.9.0 is a lot more in our face about the warnings.  I'm not sure what exactly is the cause other than I suspect naming the 'header' and 'excludes' the same results in them being injected in both places but only because I overload nearly everything to latest.
Maven used 3.9.0
Java used 17.0.6
Tested against 4.2.rc3 of this plugin.

If I look at the diff here (https://github.com/hazendaz/base-parent/compare/master...license-issue), you juste added empty tags but didn't move the header related attributes like header and excludes inside.
Example from the doc:
  <configuration>
    <properties>
      <owner>Mycila</owner>
<EMAIL_ADDRESS>    </properties>
    <licenseSets>
      <licenseSet>
        com/mycila/maven/plugin/license/templates/APACHE-2.txt
        <excludes>
          <exclude>**/README</exclude>
          <exclude>src/test/resources/**</exclude>
          <exclude>src/main/resources/**</exclude>
        </excludes>
      </licenseSet>
    </licenseSets>
  </configuration>

I wrapped the existing header / excludes entirely.  Diff shows that, am I missing something with that?  I just didn't tab it in for sake of keeping diff reasonable.
Full section.
                        <licenseSets>
                        <licenseSet>
                        ${license.header}
                        <excludes>

                            <exclude>LICENSE.txt</exclude>
                            <exclude>LICENSE.TXT</exclude>
                            <exclude>license.txt</exclude>

                            <exclude>**/unlicensed/**</exclude>
                        </excludes>
                        </licenseSet>
                        </licenseSets>

No, should be fine. That's weird... We should look at the effective pom i think

ok - I'll look more into that and also look at the ITs and possibly mimicking some of the changes I have in that base parent to see if I can figure out the root on this.

@mathieucarbou I resolved my issue, was very obscure but finally found it.  I was using a profile that had property 'license.header' that then was used in the block of code I provided earlier.  Reason for the code like that is that I used to have a different license header file name as 'license.txt' and migrated over to 'LICENSE_HEADER' and supported both for a period of time.  I no longer have the old support so fixing was easy.  I didn't realize that was then propagated entirely to the plugin so I just had to remove the property 'license.header' and add 'header' directly in the licenseSet.


Printing Map Issue

problem with print!, code:undefined message: Cannot read property '0' of undefined

fixed issue v4.2.8


many nugets are currently showing "This package has not been indexed yet"

From @SimonCropp on August 4, 2015 23:5
even though they were deployed a long time ago
https://www.nuget.org/packages/EntityFramework/5.0.0
https://www.nuget.org/packages/Fody/1.29.0
https://www.nuget.org/packages/Newtonsoft.Json/3.5.8
Copied from original issue: NuGet/Home#1112

From @yishaigalatzer on August 5, 2015 17:27
@SimonCropp thanks for the report. We are aware and actively looking at

Updating our monitoring to catch the issues
Fix the individual packages
Track the bug causing this

CC @johnataylor @maartenba @xavierdecoster @bhuvak

From @yishaigalatzer on August 6, 2015 1:28
This looks like is just a bug in the notification, for packages that are not the latest package. We are looking into a solution. Thanks for reporting

From @SimonCropp on August 6, 2015 1:30
BTW a google search for "This package has not been indexed yet" will show u more examples

From @johnataylor on August 6, 2015 1:30
I think the “not indexed yet” banner is giving us some false negatives. i.e. its saying that packages are not yet indexed when in fact they are.
The fix is in this code I think: (PackagesController.cs l.304)
        if (_searchService.ContainsAllVersions)
        {
            var isIndexedCacheKey = string.Format("IsIndexed_{0}_{1}", package.PackageRegistration.Id, package.Version);
            var isIndexed = HttpContext.Cache.Get(isIndexedCacheKey) as bool?;
            if (!isIndexed.HasValue)
            {
                var searchFilter = SearchAdaptor.GetSearchFilter(
                        "id:\"" + package.PackageRegistration.Id + "\" AND version:\"" + package.Version + "\"",
                        1, null, SearchFilter.ODataSearchContext);
                var results = await _searchService.RawSearch(searchFilter);

That is to say you are building a raw Lucene query and need to say that. This also avoids the filtering logic too I think.
Anyhow, without this many packages (everything but the latest?) are appearing as “not indexed” when in fact they are.

A fix has been deployed.

Looking into it, thanks!

From @ryanhelms on April 28, 2016 6:13
Has this bug be reintroduced? I am getting the "This package has not been indexed yet" banner on many packages, example:

https://www.nuget.org/packages/NUnit.Runners/3.2.0
https://www.nuget.org/packages/NUnit.Runners/2.6.4

And after just searching around for a few, I noticed that there are a lot (90% of the non-latest package) being reported "not been indexed yet", example:
(3 randomly selected packages, not latest stable package)

https://www.nuget.org/packages/Microsoft.AspNet.Mvc/5.2.0
https://www.nuget.org/packages/BuildingBlocks.Mvc.KnockoutMvc/<IP_ADDRESS>
https://www.nuget.org/packages/NExtra.Mvc/2.6.5

Issue resolved.


Infinite recursive calls in downloader class (v9.0.4)

Hello,
With the latest version of java_se  (9.0.4) our code relying on it is not working anymore, hitting a stack too deep error:
SystemStackError:    stack level too deep
     # /tmp/d20180411-7446-1f6rgce/cookbooks/java_se/libraries/downloader.rb:78:in `first_hash_argument'
     # /tmp/d20180411-7446-1f6rgce/cookbooks/java_se/libraries/downloader.rb:73:in `allow_redirections'
     # /tmp/d20180411-7446-1f6rgce/cookbooks/java_se/libraries/downloader.rb:60:in `open_uri'

I don't see the 9 branch.  But if I had to guess, the path might of changed 9.0.4+11? http://download.oracle.com/otn-pub/java/jdk/9.0.4+11/c2514751926b4512b076cc82f959763f/jdk-9.0.4_linux-x64_bin.tar.gz

I forgot master was 9 and not 10. The link still looks good https://github.com/vrivellino/chef-java_se/blob/master/libraries/default.rb#L30-L31

I'm not able to download chef java_se
22:51:01 Recipe: java_se::_windows_install
22:51:01 * ruby_block[fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe] action run
22:52:02
22:52:02 ================================================================================
22:52:02 Error executing action run on resource 'ruby_block[fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe]'
22:52:02 ================================================================================
22:52:02
22:52:02 ArgumentError
22:52:02 -------------
22:52:02 too many download failures from http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe
22:52:02
22:52:02 Resource Declaration:
22:52:02 ---------------------
22:52:02 # In C:/Users/ADMINI~1/AppData/Local/Temp/kitchen/cache/cookbooks/java_se/libraries/default.rb
22:52:02
22:52:02 52: ruby_block "fetch #{download_url}" do
22:52:02 53: block do
22:52:02 54: JavaSE::Downloader.fetch(download_url, file_cache_path, checksum)
22:52:02 55: end
22:52:02 56: not_if { ::File.exist?(file_cache_path) && JavaSE::Downloader.valid?(file_cache_path, checksum) }
22:52:02 57: end
22:52:02 58: end
22:52:02
22:52:02 Compiled Resource:
22:52:02 ------------------
22:52:02 # Declared in C:/Users/ADMINI~1/AppData/Local/Temp/kitchen/cache/cookbooks/java_se/libraries/default.rb:52:in `fetch_java_installer'
22:52:02
22:52:02 ruby_block("fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe") do
22:52:02 action [:run]
22:52:02 default_guard_interpreter :default
22:52:02 declared_type :ruby_block
22:52:02 cookbook_name "java_se"
22:52:02 recipe_name "_windows_install"
22:52:02 block #Proc:0x000000000605c3e0@C:/Users/ADMINI~1/AppData/Local/Temp/kitchen/cache/cookbooks/java_se/libraries/default.rb:53
22:52:02 block_name "fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe"
22:52:02 not_if { #code block }
22:52:02 end
22:52:02
22:52:02 System Info:
22:52:02 ------------
22:52:02 chef_version=14.0.202
22:52:02 platform=windows
22:52:02 platform_version=6.3.9600
22:52:02 ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x64-mingw32]
22:52:02 program_name=C:/opscode/chef/bin/chef-solo
22:52:02 executable=C:/opscode/chef/bin/chef-solo
22:52:02
22:52:02
22:52:02 Running handlers:
22:52:02 [2019-03-24T03:52:01+00:00] ERROR: Running exception handlers
22:52:02 [2019-03-24T03:52:01+00:00] ERROR: Running exception handlers
22:52:02 Running handlers complete
22:52:02 [2019-03-24T03:52:01+00:00] ERROR: Exception handlers complete
22:52:02 [2019-03-24T03:52:01+00:00] ERROR: Exception handlers complete
22:52:02 Chef Client failed. 1 resources updated in 01 minutes 21 seconds
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: Stacktrace dumped to C:/Users/ADMINI~1/AppData/Local/Temp/kitchen/cache/chef-stacktrace.out
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: Stacktrace dumped to C:/Users/ADMINI~1/AppData/Local/Temp/kitchen/cache/chef-stacktrace.out
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: ArgumentError: ruby_block[fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe] (java_se::_windows_install line 52) had an error: ArgumentError: too many download failures from http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe
22:52:02 [2019-03-24T03:52:01+00:00] FATAL: ArgumentError: ruby_block[fetch http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe] (java_se::_windows_install line 52) had an error: ArgumentError: too many download failures from http://download.oracle.com/otn-pub/java/jdk/11.0.2+9/f51449fcd52f4d52b93a989c5c56ed3c/jdk-11.0.2_windows-x64_bin.exe
22:52:02 >>>>>> ------Exception-------
22:52:02 >>>>>> Class: Kitchen::ActionFailed
22:52:02 >>>>>> Message: 1 actions failed.
22:52:02 >>>>>> Converge failed on instance . Please see .kitchen/logs/default-windows2012r2.log for more details
22:52:02 >>>>>> ----------------------


UX: Reset Loader when Zip is cancelled

Whenever the user click on cancel Uploading zip , the loader should reset.
Steps to Reproduce

Upload Zip and click generate app
Cancel Zip when app is generated and upload new zip

@aayusharora I noticed this bug too. I will work on fixing it ASAP. Thanks.

@aayusharora  I tried to solve the issue and I have got this result.

There is one more problem that I have noticed , while generating the app if we hit cancel it wont stop the generating process of the web app.
Check this out!

@geekyd Looks great. I had also started working on the issue :smile:. In the future, before working on an issue, please ask the members who have volunteered to work on it before taking it up. This would lead to more efficient utilization of time and resources. Anyways, no problem. Please make a PR.
To cancel the generation process, placing a button next to the generation slider or a cancel button would be more apt. @aayusharora Please guide on this.

@Princu7 Sorry about that, I will be more careful in the future!
I'm generating a PR.

@Princu7 Thank you :)

@geekyd No problem at all. Good Work. It was a trivial issue so no harm done. Sometimes, it might happen that the other person might have invested a lot of time on the issue which would be nullified this way. Cheers :smiley:

@Princu7 I'm sorry about the misunderstanding. I did not mean to nullify your work.

@geekyd No problem at all. No misunderstandings. You didn't do anything but great work. I was speaking from a general perspective. All is Well :smiley:

@geekyd Nice work! You catch a crucial bug. You can create a seperate issue for that and can go ahead.
@Princu7 Do you want to work on this issue ?

@aayusharora Geekyd wanted to work on it so he should go ahead. I will fix other bugs. Thanks.

Issue has been fixed. Closing this.


wg-outreach Meeting 2019-07-08

This is wg-outreach's regular weekly meeting with varying agenda, usually presented by wg-outreach members. Mostly meant for wg-outreach regulars, but open for anyone who'd like to contribute to AMP outreach.
Meeting date/time (UTC)
17:00 (10am PT)
Instructions for joining the meeting
Please join us on Google Meet with this link.
Agenda
Note: Add a comment on this issue to propose items for the agenda.

Nothing yet!

This meeting has been cancelled due to the vast majority being out (a two week period of meeting-free weeks for the Googlers).


ol.layer.Layer maxZoom property causes zooming bug on android devices

Setting property maxZoom on ol.layer.Layer causes zooming the whole page instead of the map itself on most of the android devices.
Steps to reproduce the behavior:

Go to https://openlayers.org/en/latest/examples/layer-zoom-limits.html.
Pinch zoom over threshold zoom level 14.
From this point, instead of the map the whole page is zoomed and the view is broken.

There is no problem on iPhones and some android devices. We observed that the bug can be reproduced on approximately 80% of the android devices at least on google chrome and samsung internet browser.
Problem: Samsung S21 Ultra 5G, Samsung Note 20 Ultra, Samsung Galaxy Note 9
No problem: Samsung s10e, Xiaomi Redmin Note 9 pro
I am using the library version 7.1.0, but the problem is also in the newest version. I think, that I saw this issue even years ago on one android phone. It really might be a very old problem, although I can't imagine it has been unobserved and unresolved till now.

See #13495

There is no need to place one finger on some ui control for this to happen. It happens even when pinch zooming on a blank map only.

There is direct connection between layer's "maxZoom" or "minZoom" property and this behaviour. This problem does not occur on a map with layers without these properties set. And even on the maps with such a layers active, it only happens when you pinch zoom over this threshold zoom. On the example I provided, it is zoom 14. Try to reach zoom 14 and get over it. Then this happens.

A different cause in your case (a change of elements as the layer visibility changes) but the same fix should work https://deploy-preview-14906--ol-site.netlify.app/en/latest/examples/layer-zoom-limits.html


Add some demo project

Hello,
First of all, thank you for your project which is saving me from pain. You example playground file don't run on my machine and i think that one is not sufficient. I suggest you to add some demo project like the given image on your readme file. It would be helpful for us.
Thank you

Example projects take way too much time to write and maintain which is why i have gone against one. If you’d like to make one and maintain, PRs are welcome. Otherwise, this is why i spend so much time on the documentation. Thanks!


Doc: bad format on MDN links

The 1.7.1 docs display raw URLs for some of the links to developer.mozilla.org, along with some misplaced markdown code.
Might have something to do with the fact that I used the 2.0.0 version of Leafdoc (that I was working on) to build the 1.7.1 docs; and it changed the whole way that comment blocks are parsed, and it changes the markdown→html engine.

See also https://github.com/Leaflet/Leafdoc/issues/21

Upstream: https://github.com/Leaflet/Leafdoc/issues/56


Change Own SSH key as API endpoint

To do cluster provisioning with a master node controlling the slave nodes, we need to add the master's ssh key to the preseed, but as the master node itself needs to be reprovisioned, its SSH key will change.
We would need some kind of way to automatically update the SSH key of an account (for which we have the token) to do this.

It would also be good to have access to the ssh key via an API call, or just HTTP, so that other processes can query and use it. Otherwise, I'll have to store the key in yet-another place (including in addition to LDAP for real users).


Cleanup CSR decoding

move the comment to the place where is handled.
simplify the logic csr_read_enable as ctl_CSR is only set when ctl_SYSTEM is set.

Thanks for your contribution.


feat(site): Make live code examples more readable

Description

Change Root in the example source to be DemoLayout in most cases and FixedWidthLayout when that was instructive.
Motivation and context

Root doesn't mean anything and I imagine it will confuse people. Adding a descriptive name is a simple way to provide clarity.
connects #29
Screenshots or videos, if appropriate

How has this been tested?

ran the demo, snapshots updated
Types of changes

Other (provide details below)

refactor
Checklist

[x] Renders and functions properly in all supported browsers
[x] Automated tests written and passing
[x] Accessibility and inclusivity considered
[x] Rendering performance (initial load time & 60fps) and perceived performance considered
[x] Documentation created or updated

How does this PR make you feel?

connects #177


File watcher

This branch is over feature/file-checker
Merge after https://github.com/eProsima/databroker/pull/8

FileWatcher.hpp file added to thirdparty without reference link.
Fails

When the file does not exist, it shows an error in creation and the watcher does not work.
Every time file is pressed, modified is called twice.


The sampler is not consistent with the original implementation of CCKD

hi，why the sampler (CUR or SUR) is not consistent with the original implementation of CCKD (Correlation Congruence for Knowledge Distillation)？
And I would like to know what delta[:-1] * delta[1:] denotes？
Thanks!

@winycg , that's the code the original author shared with me.


Fix REST API /_admin/cluster/removeServer.

Scope & Purpose
Fix REST API /_admin/cluster/removeServer.
This also fixes the removal of servers via the web interface.

[x] Bug-Fix for devel-branch (i.e. no need for backports?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)

Related Information

[x] There is a JIRA Ticket number: https://arangodb.atlassian.net/browse/BTS-45

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.
http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/9628/

http://<IP_ADDRESS>:8080/view/PR/job/arangodb-matrix-pr/9640/

Tests blue except unrelated failures.


Returns feedback if failed to make analysis.

I saw a couple of times, that cppcheck fails to make analysis:

failed to find cppcheck friendly files
doesn't have access
etc

So, it would be nice to send feedback to gerrit as well.

@sschuberth was faster :)


AZ-580 Removed Ideal Staked, Staked and Inlfation widgets from Staking/Overiew tab

Testing done:

yarn install,
yarn build,
yarn run test,
yarn start
Result is that those widgets are removed:

Declining as we've changed approach - see https://github.com/Cardinal-Cryptography/apps/pull/13 .


Default endpoint timeout configuration is 300ms which is wrong

Description:
When created a new API with providing the endpoint, The default timeout configuration is shown as 300ms.

In previous 2.x family this was 30 seconds by default
In the endpoint configurations there is no timeout configured
In the log, it goes up to 120 seconds.

Affected Product Version:
APIM 3.2.0 - RC2

Optional Fields
Either we have to correct UI to not include any timeout configuration or correct timeout configuration. This is a huge misleading bug.

Fixed with https://github.com/wso2/carbon-apimgt/pull/9155

The above configuration applies only if the Advanced Configurations are saved. Still, the configuration available in the UI can be misleading and therefore it would be better to completely remove the value and have the correct default value in the UI as well. This might be related to the details mentioned in https://github.com/wso2/product-apim/issues/6725.


Policy service

Updated delegate header flow for create policy and delete policy
updated tests for create policy and delete policy
updated openapi spec
refactored ComposeException

Can one of the admins verify this patch?

Please test this

retest this please

retest this please

please retest this

please retest this

retest this please


Robustness: rework isConstructorOrProto

The isConstructorOrProto fix does not look right for the v0.2.x branch. I looked at various commits and suspect the back port of the fix itself went somewhat awry. This PR makes the code match the mainline.
Here are the relevant lines of code from the main branch and from the original commit and adapted commit adding isConstructorOrProto.
Main line

https://github.com/minimistjs/minimist/blob/6901ee286bc4c16da6830b48b46ce1574703cea1/index.js#L19-L21
https://github.com/minimistjs/minimist/blob/6901ee286bc4c16da6830b48b46ce1574703cea1/index.js#L85
https://github.com/minimistjs/minimist/blob/6901ee286bc4c16da6830b48b46ce1574703cea1/index.js#L99

Original change

https://github.com/minimistjs/minimist/blob/c2b981977fa834b223b408cfb860f933c9811e4d/index.js#L247-L249
https://github.com/minimistjs/minimist/blob/c2b981977fa834b223b408cfb860f933c9811e4d/index.js#L73
https://github.com/minimistjs/minimist/blob/c2b981977fa834b223b408cfb860f933c9811e4d/index.js#L82

Adapted change (suspect)

https://github.com/minimistjs/minimist/blob/ef9153fc52b6cea0744b2239921c5dcae4697f11/index.js#L9-L11
https://github.com/minimistjs/minimist/blob/ef9153fc52b6cea0744b2239921c5dcae4697f11/index.js#L28-L30
https://github.com/minimistjs/minimist/blob/ef9153fc52b6cea0744b2239921c5dcae4697f11/index.js#L44

Codecov Report

Merging #24 (3bc746e) into v0.2.x (c0b2661) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           v0.2.x      #24   +/-   ##
=======================================
  Coverage   98.55%   98.55%
=======================================
  Files           1        1
  Lines         138      138
  Branches       60       60
=======================================
  Hits          136      136
  Misses          2        2

Impacted Files
Coverage Δ

index.js
98.55% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I'll look at adding tests for constructor, and the last key. (It took me a while to untangle the code, but I hopefully learnt enough on the way to write the tests now!)

There are separate checks against the leading keys in a dotted option name than against the last key. If the checks for __proto__ or constructor are wrong in the checks of the last key then it won't lead to prototype pollution as such, but will lead to less consistent behaviour between --a.constructor.prototype.b and --a.constructor.
The pollution checks on the v0.2.x branch missed the constructor check on the last key in the dotted option name. So again this does not allow prototype pollution, but does mean there is different behaviour between the main branch and the v0.2.x branch.
This PR adds a test which fails if the constructor check is missing for the last key. (And a matching test for __proto__.)
The tests were run against the previous code in #25 to show the failure.

To be clear, after testing I do not think this PR is a security fix. Just a tidy-up to make the dotted option key handling more consistent.


Add header, method and statusCode to http request data

Fixes #392

LGTM

@sjanuary thank you for fix this soon.
Just a confirm, we found there is "header" and "requestHeader" in http event. it seems requestHeader is also important for us, will this fix also include requestHeader in request event?

@xiaoshimimi - it only contains requestHeader, which is the full header.  I don't think 'header' is needed any more, it was just left in for backwards compatability


Put 'Save' Button on 'List Table Column' Tab

It's annoying that the check boxes don't autosave, and that you have to scroll up and go to the other tab just to be able to save. Please make sure that the save button is visible on all edit table views!

Yeah that's from FAB (flask appbuilder), the project needs a little bit of love. We may enhance the CRUD feature or eventually write our own forms...

Notice: this issue has been closed because it has been inactive for 726 days. Feel free to comment and request for this issue to be reopened.


JsonSchema.js:178 Error on gulp trust-dev-cert

node -v v11.0.0 ,   npm -v 6.4.1 ,   gulp -v  CLI version: 2.2.0   Local version: 3.9.1
Getting following error:
C:\Temp\SharePoint\APPs\MyApp1\config\package-solution.json
Error: #/solution
Additional properties not allowed: isDomainIsolated
at validateObjectWithCallback (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\node_modules@microsoft\node-core-library\lib\JsonSchema.js:178:19)
at JsonSchema.validateObjectWithCallback (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\node_modules@microsoft\node-core-library\lib\JsonSchema.js:193:13)
at JsonSchema.validateObject (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\node_modules@microsoft\node-core-library\lib\JsonSchema.js:175:14)
at PackageSolutionTask._readConfigFile (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\node_modules@microsoft\gulp-core-build\lib\tasks\GulpTask.js:308:28)
at PackageSolutionTask.onRegister (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\node_modules@microsoft\gulp-core-build\lib\tasks\GulpTask.js:87:32)
at Object.initialize (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-common\node_modules@microsoft\gulp-core-build\lib\index.js:299:24)
at SPWebBuildRig.initialize (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-common\lib\BuildRig.js:61:19)
at SPWebBuildRig.initialize (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-common\lib\SPBuildRig.js:22:15)
at SPWebBuildRig.initialize (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\lib\SPWebBuildRig.js:15:15)
at Object.exports.initialize (C:\Temp\SharePoint\APPs\MyApp1\node_modules@microsoft\sp-build-web\lib\index.js:23:17)
at Object.<anonymous> (C:\Temp\SharePoint\APPs\MyApp1\gulpfile.js:7:7)
at Module._compile (internal/modules/cjs/loader.js:707:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:718:10)
at Module.load (internal/modules/cjs/loader.js:605:32)
at tryModuleLoad (internal/modules/cjs/loader.js:544:12)
at Function.Module._load (internal/modules/cjs/loader.js:536:3)

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

ID: 6c25a90e-829c-b436-d8ab-f9c010588ee1
Version Independent ID: 768fa9a1-2375-fb5a-be58-cb66320cc789
Content: Build your first SharePoint client-side web part (Hello World part 1)
Content Source: docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

you are using Node.js  v11.0.0 which is not supported with SharePoint Framework.
you can uninstall node.js v11.00 and install mode.js v10.x
Refer the below URl, it will guide how to setup
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment
Note:
The current supported LTS version of NodeJS for the SharePoint Framework is both Node.js v8.x and Node.js v10.x (recommended). Node.js v12.x is not currently supported. Notice that 9.x or 11.x versions are currently also not supported with SharePoint Framework development.

Node. js v11 is not supported to build SPFX solution, currrently please use Node.js v10.x instead, this is the recommended version, if you are working with SharePoint Online, this is the result in my local which is using Node.js v10.17.0:

Following the instructions and using gulp 3.9.1, I've gotten this message: "This tool requires a version of NodeJS that matches >=8.9.4 and <9.0.0 || >=10.13.0 and <11.0.0 ".
I have installed NodeJS 10.13.0 and everything worked perfectly :)


Support for private repositories

What is your issue?
No support for private repositories.
Why is it issue?
Private repositories are required for internal projects.
How do you expect to be?
Access token option, to enable access to private repositories.

Feel free to reopen the issue if this does not solve the issue.


First attempt at cumulative chart #118

@mrkwanzaa Can you review this? I already merged because I need the chart now, but I would guess we could code in a more functional manner. Can you look into this for @Visionnaire19

Hey @Visionnaire19, good work here tying everything into the existing charts system. I've made a commit that makes some of the code more functional here 1c10f9333a8551d8ebdb0209465b128338ce3dbf Let me know if you have any questions about what was changed. (Additionally Connor fixed a small bug in my code here 0cfe2b91d6de83072b2e9ce391e71a7005d0d872)


Static Library

Hi wbenny. Thank you for implementing a Tor client that is more Windows oriented. I'd like to use your code in a messaging app I'm developing, and would like to use mini-tor as a communication transport. Is there a way to compile your software into a static library for use in a C++ app? Thanks for the guidance

Hi, in Visual Studio, you can change the project Configuration Type (<ConfigurationType> in .vcxproj) from "Application" to "Static Library".

I seem to still be having some trouble getting the software to compile into a static library. I changed the Configuration Type to a Static Library, but Visual Studio is unhappy. I suspect that my issue isn't related to the static library compilation flag, but perhaps I'm missing something in my environment. I'm on Windows 10 using Visual Studio Community 2017 with Windows SDK 10.0.17763.0. I've posted the build output below. Any ideas?
(sorry for the wall of text)
1>------ Build started: Project: mini-tor, Configuration: Debug_Clang Win32 ------
1>base16.cpp
1>base64.cpp
1>main.cpp
1>console.cpp
1>In file included from mini\console.cpp:1:
1>In file included from mini/console.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>In file included from mini\crypto\capi\base64.cpp:1:
1>In file included from main.cpp:4:
1>In file included from mini\crypto\capi\base16.cpp:1:
1>In file included from mini\crypto\capi/base64.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/console.h:3:
1>In file included from mini\crypto\capi/base16.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>2 errors generated.
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>base_encode.cpp
1>curve25519.cpp
1>random.cpp
1>random.cpp
1>In file included from mini\crypto\capi\detail\base_encode.cpp:1:
1>In file included from mini\crypto\capi\detail/base_encode.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\crypto\capi\random.cpp:1:
1>In file included from mini\crypto\capi/random.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\crypto\cng\random.cpp:1:
1>In file included from mini\crypto\cng/random.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>In file included from mini\crypto\cng\curve25519.cpp:1:
1>In file included from mini\crypto\cng/curve25519.h:4:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>base32.cpp
1>2 errors generated.
1>2 errors generated.
1>2 errors generated.
1>curve25519.cpp
1>file.cpp
1>file_enumerator.cpp
1>In file included from mini\crypto\ext\base32.cpp:1:
1>In file included from mini\crypto\ext/base32.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\crypto\ext\curve25519.cpp:1:
1>In file included from mini\crypto\ext/curve25519.h:4:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>path.cpp
1>logger.cpp
1>In file included from mini\io\path.cpp:1:
1>In file included from mini\io/path.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\io\file.cpp:1:
1>In file included from mini\io/file.h:4:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\io\file_enumerator.cpp:1:
1>In file included from mini\io/file_enumerator.h:4:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>ssl_context.cpp
1>http.cpp
1>2 errors generated.
1>ssl_socket.cpp
1>In file included from mini\net\detail\ssl_context.cpp:1:
1>In file included from mini\net\detail/ssl_context.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/net/tcp_socket.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>In file included from mini\net\http.cpp:1:
1>In file included from mini\net/http.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\logger.cpp:2:
1>In file included from mini/console.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>ssl_stream.cpp
1>In file included from mini\net\ssl_socket.cpp:1:
1>In file included from mini\net/ssl_socket.h:2:
1>In file included from mini\net/tcp_socket.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\net\ssl_stream.cpp:1:
1>In file included from mini\net/ssl_stream.h:2:
1>In file included from mini\net/tcp_socket.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>tcp_socket.cpp
1>2 errors generated.
1>string.cpp
1>In file included from mini\net\tcp_socket.cpp:1:
1>In file included from mini\net/tcp_socket.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>string_ref.cpp
1>In file included from mini\string.cpp:1:
1>In file included from mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>event.cpp
1>2 errors generated.
1>thread.cpp
1>In file included from mini\string_ref.cpp:1:
1>In file included from mini/string_ref.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>time.cpp
1>cell.cpp
1>In file included from mini\time.cpp:1:
1>In file included from mini/time.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\cell.cpp:1:
1>In file included from mini\tor/cell.h:2:
1>In file included from mini\tor/common.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\threading\event.cpp:1:
1>In file included from mini\threading/event.h:5:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/time.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\threading\thread.cpp:1:
1>In file included from mini\threading/thread.h:5:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/time.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>circuit.cpp
1>circuit_node_crypto_state.cpp
1>2 errors generated.
1>In file included from mini\tor\circuit.cpp:1:
1>In file included from mini\tor/circuit.h:2:
1>In file included from mini\tor/tor_socket.h:2:
1>In file included from mini\tor/onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>consensus.cpp
1>In file included from mini\tor\circuit_node_crypto_state.cpp:1:
1>In file included from mini\tor/circuit_node_crypto_state.h:2:
1>In file included from mini\tor/cell.h:2:
1>In file included from mini\tor/common.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>hybrid_encryption.cpp
1>In file included from mini\tor\consensus.cpp:1:
1>In file included from mini\tor/consensus.h:2:
1>In file included from mini\tor/onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\crypto\hybrid_encryption.cpp:1:
1>In file included from mini\tor\crypto/hybrid_encryption.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>key_agreement_tap.cpp
1>circuit_node.cpp
1>2 errors generated.
1>key_agreement_ntor.cpp
1>In file included from mini\tor\circuit_node.cpp:1:
1>In file included from mini\tor/circuit_node.h:2:
1>In file included from mini\tor/circuit_node_crypto_state.h:2:
1>In file included from mini\tor/cell.h:2:
1>In file included from mini\tor/common.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\crypto\key_agreement_tap.cpp:1:
1>In file included from mini\tor\crypto/key_agreement_tap.h:2:
1>In file included from mini\tor\crypto/key_agreement.h:2:
1>In file included from mini\tor\crypto/../onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>hidden_service.cpp
1>In file included from mini\tor\crypto\key_agreement_ntor.cpp:1:
1>In file included from mini\tor\crypto/key_agreement_ntor.h:2:
1>In file included from mini\tor\crypto/key_agreement.h:2:
1>In file included from mini\tor\crypto/../onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\hidden_service.cpp:1:
1>In file included from mini\tor/hidden_service.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/stack_buffer.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>onion_router.cpp
1>consensus_parser.cpp
1>2 errors generated.
1>hidden_service_descriptor_parser.cpp
1>In file included from mini\tor\parsers\consensus_parser.cpp:1:
1>In file included from mini\tor\parsers/consensus_parser.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/time.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\onion_router.cpp:1:
1>In file included from mini\tor/onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>introduction_point_parser.cpp
1>In file included from mini\tor\parsers\hidden_service_descriptor_parser.cpp:1:
1>In file included from mini\tor\parsers/hidden_service_descriptor_parser.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\parsers\introduction_point_parser.cpp:1:
1>In file included from mini\tor\parsers/introduction_point_parser.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>onion_router_descriptor_parser.cpp
1>relay_cell.cpp
1>2 errors generated.
1>tor_socket.cpp
1>In file included from mini\tor\parsers\onion_router_descriptor_parser.cpp:1:
1>In file included from mini\tor\parsers/onion_router_descriptor_parser.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\relay_cell.cpp:1:
1>In file included from mini\tor/relay_cell.h:2:
1>In file included from mini\tor/cell.h:2:
1>In file included from mini\tor/common.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>tor_stream.cpp
1>In file included from mini\tor\tor_socket.cpp:1:
1>In file included from mini\tor/tor_socket.h:2:
1>In file included from mini\tor/onion_router.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/collections/list.h:3:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/byte_buffer_ref.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>In file included from mini\tor\tor_stream.cpp:1:
1>In file included from mini\tor/tor_stream.h:2:
1>In file included from mini\tor/common.h:2:
1>In file included from V:\Code\Libraries\mini-tor-0.1.22\mini/string.h:3:
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(11,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_offset_basis = 0x811C9DC5u;
1>  ^
1>V:\Code\Libraries\mini-tor-0.1.22\mini/hash.h(12,3): error : 'inline' can only appear on functions
1>  inline constexpr size_type FNV_prime        = 0x1000193u;
1>  ^
1>2 errors generated.
1>2 errors generated.
1>2 errors generated.
1>2 errors generated.
1>Done building project "mini-tor.vcxproj" -- FAILED.

Use MSVC, not clang (use any other project configuration, that doesn't end with _Clang).


/status/100 will crash

Going to http://httpbin.org/status/100 with show a Heroku error page.

constraints


Generic type arguments are sometimes also valid JavaScript comparison expressions

TypeScript Version:  3.4.0-dev.201xxxxx

Search Terms:
superset, syntactic, semantic, heuristic, parsing
Code
function f(x = {}) {
  document.body.innerText =
    `I'm ${
      arguments[1] === false ?
      "java" :
      "type"
  }script`;
}
let h = () => "";
f(h.apply<String, Object>("type"));

Expected behavior:
When run as JS (since it's valid JS) it should output the same as when run as TS.
Actual behavior:
The behavior is different in JavaScript and TypeScript
Playground Link:
https://www.typescriptlang.org/play/#code/GYVwdgxgLglg9mABMAFAD0QXkQbwL4CUuAsAFCKIAmcEIAtgKZhQB0ARnJQJ4sxhgMATgBUGaKFjIUKAAwCSAcjqIAJDinSKAQ0EBzekygBnANoBGALpZM2YFoA2RhogD8GzQCIAVloBuWj0QALndpDyguAAcGDw08IwhBGEioGQBuMjwyewYJAAssRBQiTAA+RA8PDNJUPJYtSMj7LgAeAGUoJLBdABpEAHk2LwZoUpRwqJiCAmqgA
Related Issues:
https://github.com/microsoft/TypeScript/issues/26179
Note
I wrote about this at some length https://medium.com/@jasvir/monoglots-when-a-subset-is-not-1604e3a51d9 because I thought it was just cute but not serious. I was inspired to file it here by a comment @erights made in a bug filed against TC39 (https://github.com/tc39/ecma262/issues/1681) on JS failing to be a superset of JSON that resulted in a security bug.

Nice construction!

We can create a more interesting construction,
let as=()=>0,m=[].map<0>as(()=>[]);console.log(`I'm ${!m?'Java':'Type'}Script`)

This piece of code won't emit any error on a default-configured tsc, and the running result is I'm TypeScript. In a JS runtime, this code produces I'm JavaScript. 🤣
I've also tried some popular TS runtime. The result is:
$ deno
Deno 1.45.5
exit using ctrl+d, ctrl+c, or close()
REPL is running with all permissions allowed.
To specify permissions, run `deno repl` with allow flags.
> let as=()=>0,m=[].map<0>as(()=>[]);console.log(`I'm ${!m?'Java':'Type'}Script`)
I'm TypeScript
undefined

$ bun repl
Welcome to Bun v1.1.24
Type ".help" for more information.
[!] Please note that the REPL implementation is still experimental!
    Don't consider it to be representative of the stability or behavior of Bun overall.
> let as=()=>0,m=[].map<0>as(()=>[]);console.log(`I'm ${!m?'Java':'Type'}Script`)
I'm TypeScript
undefined

$ node --experimental-strip-types
Welcome to Node.js v22.6.0.
Type ".help" for more information.
> (node:6927) ExperimentalWarning: Type Stripping is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
let as=()=>0,m=[].map<0>as(()=>[]);console.log(`I'm ${!m?'Java':'Type'}Script`)
I'm JavaScript
undefined

Nice! There's a shorter construction due to @mikesamuel viz.
console.log(`I'm ${ (0).toFixed.apply<Number, String>(1) ? 'Type' : 'Java' }Script`).
Semantic supersetting is hard - I think it's a dead horse not worth beating further.


I have a quick close issue. Not anyone encountered this?

Script ran successfully but when i click to open as administrator or normally, terminal window will opening and closing quickly.

When you click any "as administrator" menu item, two windows are opened. One of them should close immediately itself, while the other remains and is the elevated Windows terminal for you to use.
If your observation matches this, then that's normal and by design (elevation as administrator requires the first window).
If you observed something different, can you capture a short video to reveal what you saw?

I uploaded the problem.
problem.zip

Thanks. That's clear.

When "as administrator" items are clicked, we do see the first PowerShell window flash as expected. That indicates the menu items were created properly.
No Windows Terminal window is showed, no matter which menu item you clicked. That indicates wt.exe does not work on your machine.

Can you open command prompt and run the following?
%localappdata%\Microsoft\WindowsApps\wt.exe -d .

What happens when this executes will tell us more about the culprit.

wt.exe is in the right place, it is not the problem.
I think the problem is spaces in the user profile folder path.
This not recognized:
%localappdata%\Microsoft\WindowsApps\wt.exe -d .
But this is working (with single quotation marks):
"%localappdata%\Microsoft\WindowsApps\wt.exe" -d .
My local appdata folder;
C:\Users\Talha Zengin\AppData\Local
As you can see there is spaces in the path. Problem is this.

You can now try the latest version. By using another approach to launch Windows Terminal I think this issue is resolved.


Revert "Revert "Use common tranport for TlsClient""

Reverts vespa-engine/vespa#21311

Nothing yet, WIP

@geirst PR Now the unit tests pass


Where will US agencies repositories be aggregated?

From the White House Directive they're now all setting up repo's. Some will go into Pubmed (yay) but where will others go and will we be able to interface with them?

Looks like Share has DOE pages

Pubspace just goes into PMC, so, that's okay!

NTL is here, note for me: http://ntlsearch.bts.gov/repository/index.do

NOAA & CDC will put stuff here: https://stacks.cdc.gov/

Smithsonian will go here: http://research.si.edu/

USDA will go here, which has an api https://pubag.nal.usda.gov/pubag/static/api.html

USGS will be here: https://pubs.er.usgs.gov/ (and Chorus, but also here)

Some agencies will be contracting with Chorus to provide access. Their API is here: http://www.chorusaccess.org/resources/funding-agency-dashboard-service-api/

For all of the above this resource is my source: https://docs.google.com/spreadsheets/d/1StkRzBvnvnVqVul9YflAuNxIKZpY0ORnGUmntNg1FcY/edit#gid=1957704682 - I've just tried to pull out direct links.

Next step here is to find out if Base / OpenAire / Share get these places & if not, make issues to get them ourselves (or get them too)

@meganwaps can you push forwards the above?

Given these aren't EU based I'm not checking Openaire.
I looked for:

NOAA
USGS
USDA
Chorus
Smithsonian

Share has:

NOAA
USGS
DOE
Smithsonian

See #112 for progress here.
Base has:

USDA
Smithsonian

So I couldn't find NTL & CDC.
However, on closer inspection, CDC does seem to say it'll go in PMC. Ref: https://stacks.cdc.gov/pap.
NTL also seems to have it's stuff searchable here: https://trid.trb.org/search.aspx.
Considering all other agencies have been picked up by some & I can't see any API here I assume NTL will be too. In short, the vast majority of agencies are covered and we don't need to worry.


no-unbound-method errors even for non-problematic references

Bug Report

TSLint version: 4.4.1
TypeScript version: 2.1.5
Running TSLint via: cli

TypeScript code being linted
// Check if an optional method exists on obj (or its prototype chain)
function a(obj) {
  return obj && obj.method !== undefined;
}

with tslint.json configuration:
{"no-unbound-method": true}

Actual behavior
no-unbound-method gives an error: Avoid referencing unbound methods which may cause unintentional scoping of 'this'.
Expected behavior
Storing a reference to the unbound method should give an error, but simply referencing it without capturing that reference should not.

I think .apply and .call are also exceptional case for no-unbound-method rule because they binds value to this.
const a = [0];
Array.prototype.push.apply(a, [1]); // This line causes an error
console.log(a);

cc: @andy-hanson

fixed


Mobile menu should disable scrolling

When the mobile menu is open, app shouldn't be able to scroll content in the background.
Dialog component from headlessui should handle this automatically

Could also be fixed by setting body css position to fixed when menu is open. Though it may be beneficial so refactor with Dialog component anyways.


002: Uncontroversial solution

I went for a fairly straightforward and uncontroversial solution:

Initialises an empty list
Iterates over each step in the sequence adding the fibonacci number to the list
To prevent the list becoming too long, every 10,000 steps it shortens the list to just the last two numbers

I'm going to try a solution next which just updates individual variables (since we only need the last two numbers) rather than uses a list.
Here's the performance on my machine:

Updating variables directly rather than building a list has proved signfiicantly more performant:


After adding new nodes, the network between pods does not work correctly

Expected Behavior

Pod-to-pod communication should work and pods should be able to reach external networks such as hosts on the Internet

Current Behavior

pods can only reach pods on the same node, and not pods on other nodes or external networks (connections are dropped after timeout)

Context

After adding new nodes, the network between pods does not work correctly (on new nodes), very high latency, connections are dropped after timeout:
BAD nodes:
bash-5.1# curl http://api-gateway.bm-us-was-prod.svc.cluster.local:9000
curl: (6) Could not resolve host: api-gateway.bm-us-was-prod.svc.cluster.local

bash-5.1# curl google.com
curl: (6) Could not resolve host: google.com

bash-5.1# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=57 time=14.5 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=57 time=14.4 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=57 time=14.5 ms
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 14.445/14.450/14.453/0.003 ms

bash-5.1# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.041 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.031 ms
64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=64 time=0.029 ms
--- <IP_ADDRESS> ping statistics ---
4 packets transmitted, 3 received, 0% packet loss, time 3078ms
rtt min/avg/max/mdev = 0.024/0.031/0.041/0.006 ms

bash-5.1# dig api-gateway.bm-us-was-prod.svc.cluster.local
; <<>> DiG 9.16.20 <<>> api-gateway.bm-us-was-prod.svc.cluster.local
;; global options: +cmd
;; connection timed out; no servers could be reached

bash-5.1# dig google.com
; <<>> DiG 9.16.20 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17346
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.                    IN      A
;; ANSWER SECTION:
google.com.             30      IN      A       <IP_ADDRESS>
;; Query time: 0 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Wed Aug 17 10:37:12 UTC 2022
;; MSG SIZE  rcvd: 65

bash-5.1# curl google.com
curl: (6) Could not resolve host: google.com

bash-5.1# cat /etc/resolv.conf
search bm-us-was-prod.svc.cluster.local svc.cluster.local cluster.local default.svc.cluster.local
nameserver <IP_ADDRESS>
options ndots:5

bash-5.1# nslookup kubernetes.default
;; connection timed out; no servers could be reached

bash-5.1# nmap <IP_ADDRESS> -p53 -sT -sU
Starting Nmap 7.91 ( https://nmap.org ) at 2022-08-18 08:53 UTC
Nmap scan report for <IP_ADDRESS>
Host is up (0.00012s latency).

PORT   STATE SERVICE
53/tcp open  domain
53/udp open  domain

Nmap done: 1 IP address (1 host up) scanned in 13.18 seconds

Nodelocaldns logs BAD nodes:
2022/08/17 10:55:04 [INFO] Starting node-cache image: 1.21.1
2022/08/17 10:55:04 [INFO] Using Corefile /etc/coredns/Corefile
2022/08/17 10:55:04 [INFO] Using Pidfile
2022/08/17 10:55:04 [ERROR] Failed to read node-cache coreFile /etc/coredns/Corefile.base - open /etc/coredns/Corefile.base: no such file or directory
2022/08/17 10:55:04 [INFO] Skipping kube-dns configmap sync as no directory was specified
2022/08/17 10:55:04 [INFO] Added interface - nodelocaldns
cluster.local.:53 on <IP_ADDRESS>
in-addr.arpa.:53 on <IP_ADDRESS>
ip6.arpa.:53 on <IP_ADDRESS>
.:53 on <IP_ADDRESS>
[INFO] plugin/reload: Running configuration MD5 = adf97d6b4504ff12113ebb35f0c6413e
CoreDNS-1.7.0
linux/amd64, go1.16.8,
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>483407723.5767495469467330511.in-addr.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>116011608.611466303435741516.ip6.arpa. HINFO: dial tcp <IP_ADDRESS>:53: i/o timeout
[ERROR] plugin/errors: 2<PHONE_NUMBER>949309265.7264781733226064609.cluster.local.  A: dial tcp <IP_ADDRESS>:53: i/o timeout

Your Environment

Calico version 3.22.3
Orchestrator version (e.g. kubernetes, mesos, rkt): kubernetes 1.23.7
Operating System and version: Ubuntu 20.04.4
Link to your project (optional):

I checked the network on the servers, everything works correctly, I tried to disable the firewall, reinstall the nodes, but nothing helps. Please tell me how I can solve this problem

Hey @VA-PLE , usually these sorts of issues seem to be caused by firewall rules (like you've already investigated) and IP auto detection issues. Can I ask you if you're configured to use IP autodetection (usually it's on by default) and if so, can you check your logs to see which interface was selected? What could be happening is that IP autodetection is finding the wrong network interface on the new node and that interface doesn't have connection to your network, which is why the pods who would use that interface cannot access other nodes or the internet.

Hey @VA-PLE , I'm going to close this issue since we haven't had any movement on it for a couple weeks. Please shout out if your issue persists and I'll reopen the issue.


Draft: Feature/user preferences

Description
In relation to: https://github.com/payloadcms/payload/discussions/174

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have made corresponding changes to the documentation

Oehh, thanks :) was looking forward to this

@Ontopic hell yes. It's a big quality of life improvement. This PR as of now already saves column order and locale, but we're going to roll in the "collapsed" states of blocks on a document level (and maybe a few other items) before we merge.
Keep an eye out! What do you think of the approach?

Overwhelmed with your push for the next episode as well. Gonna carefully take a look and document my experiences and questions here, but it's definitely all looking like the kind of quality I'm starting to get almost used to 🙃

No bugs so far 😅 Everything running like I expected it to. I feel there's a lot of extra opportunities within this setup - like most of the stuff you guys create - waiting to be explored. To prevent myself forking or monkey-patching stuff that could be done cleanly, some extra guidelines and insights into how to approach certain tasks would be a nice addition :)


System interfaces are not deleted on worldgen

If I delete a system, then run worldgen, the ISystem interface is not deleted. This is inconsistent with tablegen

For worldgen there is the --clean flag you can pass to delete old files: https://github.com/latticexyz/mud/blob/main/packages/cli/src/commands/worldgen.ts#L13
For tablegen it automatically deletes the previous table directory: https://github.com/latticexyz/mud/blob/main/packages/store/ts/library/render-solidity/tablegen.ts#L15
Agree we should align the worldgen script here and automatically delete the previously generated files. We just have to make we don't accidentally delete any source files, but I believe table interfaces are always placed into the codegen folder so should be fine.

I think --clean flag should just be true by default, and for some cases (like world package itself, which overrides worldgenDirectory and has some manual interfaces there) it can be set to false


Optimize Mesh Data Project Configurator

Overview
The project configurator now warns against optimizing mesh data during development.

I've heard this brought up by a few community members, but was never able to reproduce this within the MRTK Unity project. Build times in current mrtk_development:
Compiled shader 'Mixed Reality Toolkit/Standard' in 6.47s
    d3d11 (total internal programs: 21504, unique: 7168)

But, I opened a project  the other day and did encounter an issue with shader compilation taking upward of 5 minutes. After doing some poking around I narrowed the issue down to the "Optimize Mesh Data" in the player settings.
If you need this setting, I would recommend disabling it while iterating on your application and only enabling it when you go to make final builds. The "Optimize Mesh Data" settings tries to remove unused vertex attributes within your application. It does this by running over every shader pass in every material that is on every mesh in the build. (You can see why this would take awhile in mid to large size projects.)
Changes

Fixes: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/6629 (partially)

Verification

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

/azp run

I'm somewhat torn because I somewhat want it to be "set and forgtet" for the average developer since the value gained from vastly improved iteration times is greater than the (sometimes modest) perf gain from this setting. Ideally the developers CI build would handle toggling this. As in this scenario, but that is outside of the control of the MRTK. Also, we "ship" the MRTK with this setting off.
I could remove this and add a warning that gets logged right before a build is created. Do you think that would get enough eyes on it?

I'm somewhat torn because I somewhat want it to be "set and forgtet" for the average developer since the value gained from vastly improved iteration times is greater than the (sometimes modest) perf gain from this setting. Ideally the developers CI build would handle toggling this. As in this scenario, but that is outside of the control of the MRTK. Also, we "ship" the MRTK with this setting off.
I could remove this and add a warning that gets logged right before a build is created. Do you think that would get enough eyes on it?

Best course of action would be if you could register when a build occurs. Then show a popup, like the project configurator, that has Apply, Ignore, Later for just this setting.

I'll try something like that, thank you for the idea!


[Docker] Generating sensible icons for manifest file.

First off we need some kind of descriptive manifest file. Or we need some kind of convention to package icons in the tar ball of our images. Like a simple icon.png in the tar ball top level could be enough. This can be easily accessed from the tarball to display the icon.
This however is not the main point of this enhancement issue. The main point is to generate icons for the hundreds if not thousands of docker images we will produce from the docker integration.  I think our docker conversion tool should add some kind of automatic google "feeling lucky" lookup on google images for a picture and use that for the template icon. This is better than no icon and it's really easy to do.
#156 @p1gmale0n ping!

Not applicable


[EDA] Add Application Created Date field on Application Object

Do you want to request a feature or report a bug?
feature

What is the expected behavior?
A new field in EDA to capture "Application Created Date"

Acceptance Criteria

Given: I am on a Application Object
When: I click a Fields
Then: I should be able to see "Application Created Date"

**lurch: attach W-042818

Tracking W-042818


Extend track flag to save all relevant training data

When a developer runs gait commit --track, we want to capture the diff (currently implemented), the OpenAI generated commit message, and the message chosen by the user (either generated, edited, or skipped).  Come up with a schema to represent these files as input training data to improve the OpenAI model.

This issue should follow #7


voiceLeave doesn't work

//Once bot is logged in and ready...

mybot.on("voiceLeave", function(user, voiceChannel) {
	console.log(user + " left " + voiceChannel);
});

Nothing is ever printed to the console

seems related to https://github.com/hydrabolt/discord.js/issues/116

There should definitely be a voiceSwitch event too, if this is the intention of voiceLeave.