Fix unit tests due to PropelQuickBuilder errors

The PropelQuickBuilder doesn't work at the moment, we get the following error:

phpunit -c phpunit.xml.dist tests/Propel/Tests/Generator/Builder/Om/GeneratedObjectArrayColumnTypeTest.php
PHPUnit 3.5.14 by Sebastian Bergmann.
Fatal error: Cannot use Propel\Runtime\Propel as Propel because the name is already in use in /Users/william/projects/Propel/Propel2/src/Propel/Generator/Util/PropelQuickBuilder.php(141) : eval()'d code on line 816

Due to use statements, we cannot call eval().
William
/ping @fzaninotto

Seems that there is no other way than hacking the generated code, "a la" Symfony2.
See https://github.com/symfony/symfony/blob/master/src/Symfony/Component/ClassLoader/ClassCollectionLoader.php


Geometry clipping

Possible algos:

Efficient Parallel and Distributed Algorithms for
GIS Polygon Overlay Processing
Vatti clipping algorithm
p56-vatti.pdf

@gdey

Quick update. Have clipping working for most tiles. However, there are a few polygons that get clipped to nothing, that I believe should not be.
As you can see from the missing tile:

I'm currently working on tooling to help me debug what is going on here. Once this is solved, clipping will be merged in for fuller testing. Initially, we will be rolling it out disabled.  Enabled the setting by setting the environment variable TEGOLA_CLIPPING to yes.

@gdey I was able to extract the geometries from the OSM database that were causing clipping issues as shown in the following screen shots:

Using the following SQL
SELECT
  ST_AsBinary(geometry) AS geometry,
  id,
  osm_id,
  name,
  type
FROM
  osm_waterways
WHERE
  geometry && ST_MakeEnvelope(254382.43009765446,5310233.228288574,256828.4150024396,5307787.243383789)

The attached output has 3 geometries in WKB format with their accompanying attributes.
osm-waterway-output.txt

One more isolated test case

Using the following SQL
SELECT
  id,
  osm_id,
  name,
  type,
  ST_AsBinary(geometry) AS geometry
FROM
  osm_roads
WHERE
  geometry && ST_MakeEnvelope(-1.3644926791343994e+07,5.657563084768066e+06,-1.3644315295117797e+07,5.65695158854187e+06)

The attached output has 2 geometries in WKB format with their accompanying attributes.
osm-roads-output.txt

Hi @ARolek and @gdey, I am getting the same type of errors with my line layers frequently. I am also getting (occasionally) the polygon error described by @gdey above, so whole tiles would be completely missing from my map. If I can help with anything (logged SQL statements, etc.) to solve that issue faster please let me know. The clipping issue is the main reason that prevents me from going fully live with my page currently. I would provide a link early next week after updating my server so you can test on my mapbox-gl-js application/page if this is of help. Many thanks for your great efforts!

Hi @allspatial !
Have you tried the latest build from this branch? I push up a few more fixes late last night. Also, be aware that by default the clipping is turned off and you have to setting the environmental variable TEGOLLA_CLIPPING to mvt, TEGOLA_CLIPPING="mvt" not to yes as I had in said in a different comment.
I'm looking into more bugs that @ARolek ARolek has pointed out to me. I, also, have pushed out a small utility to help me get test cases. I'll write up a quick usage guide for it after I make some improvements to make generating the test cases easier.

Hi @gdey, thanks for your swift reply! The changes from last night I haven't tried yet. Will do so right now. The "mvt" I already figured out.

Hi @gdey, I tested the latest clipping_3 branch. Line clipping seems to work better now, polygons still disappear (see screenshot). And I can now see the tile boundaries, I assume you are showing them for testing purposes. Many thanks!

@allspatial No, those gray lines should not be there. I think I have to increase the overlap buffer for that. I've got a few more fix coming with a new push.
Thank you for looking into this.

Hi @gdey and @ARolek, issues #90, #100 and #56 could probably be merged since they all refer to the clipping. It would reduce the number of issues at once without much effort ;-). Taking into account also issue #102 which would be the recommended Tegola version to test now with regard to improved geometry clipping and MVT specification compliance? By the way, here is the link to the application I am working on, just to have another test case:
https://www.webgis.gov.sc/mobile/
Thanks again!

Hi @gdey, I just pulled and tested the latest v0.4.0 branch. The line clipping works much better and there are no fictive lines anymore crossing the screen. However, there is one issue I found where a part of the line would be completely missing (screenshot "shot3" attached). Regarding the polygons I still get the issue of tiles completely missing. And currently I am seeing the tile boundaries. Many thanks!!

@allspatial thanks for testing out the v0.4.0 branch and providing the screen shots. We have a lot of effort going into clipping right now and we believe we have identified the clipping issues you're showing screenshots 1 and 2. The primary issue has to do with scaling and what happens to the geometries at lower zoom levels. After scaling the geometries can become invalid which causes the clipping algorithm fail in certain situations (as you're seeing). For the most part we only see the issue at low zooms. Do you see issues when zoomed in?
The second issue has to do with our tile buffer which we're also working on. The tile buffer needs to extend past the tile extent to ensure smooth transitions from tile to tile. We're already on it and hope to have a solution soon. Would you like me to ping you next time the v0.4.0 branch is updated?

@allspatial Thanks for the update. I found some issues with the way I have been doing things, that is requiring a deeper change. So, I am working through that change right now.
The issue with the borders is because my buffer zone around the title is not large enough. I will be increasing that as soon as I get better handle of the clipping.
One of the issue is that once we scale the polygons to the the correct zoom level. The polygon becomes invalid, the clipping also expects valid polygons (concave, non-intersecting) so it ends up not clipping things correctly.

I'm working through these things.
Thank you for all the info.

Hi @ARolek and @gdey, many thanks for your efforts! The issue with the missing tiles for the polygon layer I also get at higher zoom levels. And yes, please let me know once the v0.4.0 branch has been updated. However, I am frequently checking anyway ;-). Thanks again!!!

@allspatial Just pushed up some more changes to the v0.4.0 branch. Let me know if that works better. It is slower, and will work on speeding things up once I have things working correctly.

Ho @gdey, much better now! Lines look all good and tile boundaries don't show anymore. The only remaining issue is the tiles for polygon layers that are still missing sometimes. Many thanks!

@arolek is this the same thing we see at low zo in the OSM
On Sat, Apr 15, 2017 at 10:36 Michael Wagner<EMAIL_ADDRESS>wrote:

Ho @gdey https://github.com/gdey, much better now! Lines look all good
and tile boundaries don't show anymore. The only remaining issue is the
tiles for polygon layers that are still missing sometimes. Many thanks!
[image: shot]
https://cloud.githubusercontent.com/assets/12534211/25065593/8e004f1c-2223-11e7-833d-f37c431077ec.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/terranodo/tegola/issues/56#issuecomment-294307420,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAe43kU75nz1qyz5Mroo1TmG10FemLz4ks5rwQAfgaJpZM4JbLym
.

@allspatial thanks again for the tests. What zoom level are you at? Also we have a new tool that can dump WKB for our test suite. @gdey would it be helpful to have a dump of the tile for a test case?

Hi @ARolek and @gdey , I observed the issue at zoom levels 12 to 16 mostly in my case:
Seychelles WebGIS
And yes, let me know if you need a geometry dump.
Many thanks!

Hi @gdey and @ARolek, after updating to the latest v0.4.0 version it seems the number of geometry issues has increased again. mapbox-gl-js also shows a warning that the tiles are not tile spec v2 conform which could cause rendering issues. I can't tell though how serious this warning is and if it really causes some of the issues you can see in the attached screenshots or if all results from the clipping. Many thanks!

Hi @ARolek, many thanks for the clarification! That sounds all good and I am very much looking forward. Tegola is a great tool and with the clipping fixed it will be perfect ;-).

Hi @ARolek and @gdey, did you by chance find the time to do some refactoring/improvement on the clipping part? If so - in what branch would I find that? With the current version of v0.4.0 I can't go live (see attached). Many thanks!!!

@allspatial we have some major clipping improvements coming queued up. Hoping to merge into his ranch next week. In the mean time I think what you're seeing is the clipping is not turned on. Can you check if the environment var TEGOLA_CLIPPING="mvt" is set?

Hi @ARolek, I indeed forgot to set the clipping parameter this time. I apologise for the "false alarm".

@allspatial No worries, always appreciate people keeping an eye out for possible regressions. I've got more changes, coming. Need to push up the changes I have from last week to the issue-56 branch( https://github.com/terranodo/tegola/tree/issue-56 ). I have gotten few more fixes. I'm still seeing issues that I am working through one by one.

@allspatial Hey I have the latest version of the clipping code pushed to issue_56 branch. Be warned it's slow now, and I have to go through a round of optimizations. I believe I have it clipping most things correctly now. At least things looked good when I did a quick skim.
I have not had a chance to zoom around the global map searching for issues.

Hi !
Thanks you for this software !
I have the same issue as allspatial, I'm gettings something like this (https://github.com/terranodo/tegola/issues/56#issuecomment-306079317) in the master branch.
I tried the issue-56 branch (with and without your latest changes) and it's worse, nothing appears, even with TEGOLA_CLIPPING="mvt". How can I help to debug this ?

@Wykks Could you post an image. Also, with my latest changes, it takes a long while to generate the tiles. The reason being the validation process checks every segment in a feature against every other segment in that feature to make sure that no two segments that are not direct neighbors cross.  The crossing can occur after simplification — this was the source of some of the clipping issues. I will be profiling and see how I can speed this up as it's unusable at current. I am trying to get clipping correct first before optimizing it.

Sure !
With issue-56 without TEGOLA_CLIPPING="mvt" :

With issue-56 with TEGOLA_CLIPPING="mvt" :

With master :

With master + zoom :

(Mapbox-gl only, work fine with leaflet)
Data used : https://github.com/gregoiredavid/france-geojson/blob/master/departements.geojson (imported to postgis with ogr2ogr)

@Wykks Thanks! I'll take a look at it later today. I really need to get some sleep. :P

#132 seem to show the same issue. At mapbox the suggestion is done that it is due to the 'buffer-size' of the tiles. Would that ring a bell?

Please take a peak at this comment:
https://github.com/mapbox/mapbox-gl-js/issues/5175#issuecomment-323609118

This is now done.


Fix Error: bytes is not iterable

Motivation
Got Error: bytes is not iterable when downloading json state
Description

SSZ Container toJson() only works with value, not DU object
Maybe we need to fix in ssz too?

Closes #3934 #3872

This works fine in contabo-20


Fix the broken link to azure cni

Fix the broken link to azure cni

@bahman616 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @bahman616


Move number of assemblies out of global space

There have been several bugs recently due to strange race conditions and edge cases to do with the fact that the total number of assemblies in a reactor is stored in a global variable:
https://github.com/terrapower/armi/blob/907f2b49d4063cfd07068431698d22dab4c7d267/armi/reactor/assemblies.py#L36-L44
It appears all of these bugs have been present in the code for years. And in the past few weeks I have had to work on several of these issues.
Since the rest of the codebase is Object Oriented, I see now reason why this one Reactor value shouldn't be part of the Reactor object. And that is my suggestion for fixing it.

Okay, I found what I think is the only reason that we have a global _assemNum:
https://github.com/terrapower/armi/blob/907f2b49d4063cfd07068431698d22dab4c7d267/armi/reactor/assemblies.py#L99-L100
When we create a new Assembly object, we want to give it a new, unique assembly number that is only one higher than the next largest assembly number in the Reactor.
The obvious solution would seem to be not allowing None as an assemNum value when creating an Assembly. I'm not sure if that might get complicated. But I guess I'll find out.

Perhaps we could just give each assembly that needs a unique ID one from the linux timestamp:
from time import time

assemNum = int(time() * 1e8)

Then each assembly should have a unique number. And when we need create a reactor, we can go through each assembly and re-number them quickly, starting with zero (and preserving the order).

Also, I feel like the biggest troubles come from giving assemblies number when building a Reactor from a Case Settings file.
It seems like, in that scenario, we can just provide sequential assembly numbers while reading through the CS file.

This was closed with: https://github.com/terrapower/armi/pull/1383


[containerapp] az containerapp service milvus create : Add support for milvus vdb service

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

containerapp

closing -- a similar PR is open.


do not convert local paths to URL

Do not convert local paths to URLs, just keep them as they
are.
This way we add support for Windows without taking care of
Windows path-to-URL conversion.

It seems it works :)
We used to get a lot of these errors in Windows tests:
----------------------------------------------------------------------
FAIL: references_test.go:291: ReferencesSuite.TestObjectNotFoundError
references_test.go:300:
    c.Assert(err, IsNil)
... value *plumbing.PermanentError = &plumbing.PermanentError{Err:(*url.Error)(0xc043723950)} ("permanent client error: parse file://C:\\Users\\appveyor\\AppData\\Local\\Temp\\1\\tmp-tgz-678061493: invalid character \"\\\\\" in host name")

not anymore


Add test /functional/measured-boot-swtpm-sanity to Packit CI plan

Signed-off-by: Karel Srot<EMAIL_ADDRESS>

Codecov Report

Merging #1009 (eb09f9a) into master (c26a729) will increase coverage by 4.79%.
The diff coverage is 55.17%.

Flag
Coverage Δ

packit-e2e
63.44% <55.17%> (+6.42%)
:arrow_up:

testsuite
27.07% <34.48%> (-0.02%)
:arrow_down:

unittests
13.14% <20.68%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

keylime/ca_util.py
49.12% <0.00%> (+0.14%)
:arrow_up:

keylime/ima/ima.py
65.23% <ø> (+1.51%)
:arrow_up:

keylime/measured_boot.py
66.10% <0.00%> (+33.89%)
:arrow_up:

keylime/tornado_requests.py
69.23% <0.00%> (-3.75%)
:arrow_down:

keylime/tpm/tpm_abstract.py
82.05% <ø> (+5.12%)
:arrow_up:

keylime/cloud_verifier_tornado.py
66.29% <50.00%> (+0.87%)
:arrow_up:

keylime/tpm/tpm_main.py
71.72% <50.00%> (+5.37%)
:arrow_up:

keylime/elchecking/policies.py
71.42% <66.66%> (+6.31%)
:arrow_up:

keylime/ima/ima_dm.py
92.84% <88.88%> (-0.11%)
:arrow_down:

keylime/cloud_verifier_common.py
79.19% <0.00%> (+0.67%)
:arrow_up:

... and 13 more

The newly added test is not supposed to run on CentOS Stream yet, it is failing there due to old tpm2-tools.
I have updated test metadata to exclude it.

/packit test


Use StandardSerializers#protobuf in protobuf serializers [ECR-2712]

Overview
Use StandardSerializers#protobuf in protobuf serializers.

See: https://jira.bf.local/browse/ECR-2712
Definition of Done

[x] There are no TODOs left in the code
[x] Change is covered by automated tests
[x] The coding guidelines are followed
[x] Public API has Javadoc
[x] Method preconditions are checked and documented in the Javadoc of the method
[x] Changelog is updated if needed (in case of notable or breaking changes)
[x] The continuous integration build passes

Coverage increased (+0.1%) to 84.227% when pulling 89876fe732b69bd606d0f1fed0d6ebd41dd457fb on ECR-2542-protoser into 7e078e1cd5fd3f21a2c0aece6bbd80eb9a1412fd on master.


Reply Editing Function

I Will Add Reply Editing Function As Quickly As Possible.

Added in v20150430 dev.


Browserify + gulp-sourcemap = no luck (wrong paths and total mess)

I tried really hard to come up with working configuration for getting sourcemaps done right in a simple project which uses Browserify but I gave up.
I've prepared a sample project which you can pull and try out:
https://github.com/OnkelTem/demo_sourcemaps_bug
Usage:
gulp serve

TL;DR: debugging doesn't work in IDE (WebStorm).
Please take a look into docroot/js/main.js and docroot/js/main.js.map - both are screwed up. Specifically:

docroot/js/main.js for some odd reason contains the garbage from Browserify //# sourceMappingURL=data:application/json;charset=.... instead of just main.js.map

docroot/js/main.js.map has several issues:

sources array starting with not existing path js/src/scripts/... is wrong.
file property equals to main.js — i.e. w/o js prefix. I assume in this case there should be sourceRoot property set to '../'.
there is still preExisting key with the original source data from Browserify. But I passed includeContent: false to the write() method, then shouldn't it be removed?

Workarounds. I found none, except of patching.

apply this patch

diff --git a/src/init.js b/src/init.js
index c1c405a..d285b38 100644
--- a/src/init.js
+++ b/src/init.js
@@ -84,7 +84,7 @@ function init(options) {
             sourceMap.sourcesContent[i] = sourceMap.sourcesContent[i] || null;
             return;
           }
-          var absPath = path.resolve(sourcePath, source);
+          var absPath = path.resolve(source);
           sourceMap.sources[i] = unixStylePath(path.relative(file.base, absPath));

           if (!sourceMap.sourcesContent[i]) {
@@ -200,8 +200,6 @@ function init(options) {
         sourcesContent: [fileContent]
       };
     }
-    else if(preExisting !== null && typeof preExisting !== 'undefined')
-      sourceMap.preExisting = preExisting

     sourceMap.file = unixStylePath(file.relative);
     file.sourceMap = sourceMap;

Call the .write() with sourceRoot set to the current directory value (uncomment the 1st variant in the gulpfile.js):

.pipe(sourcemaps.write('./', { includeContent: false, sourceRoot: './' }))

Now it starts working in WebStorm.

I am swamped right now. If someone wants to make a PR and attempt to fix things; please feel free.

I'm pretty sure the patch is dirty and would fail in other cases. So I don't feel like it's a candidate for a PR.

@OnkelTem I removed the preEixsting stuff and unpublished 1.9.1 and 2.2.1 try 2.2.2 and 1.9.2


Update datastream name for ES

for example:

https://kibana.cscs.ch/s/fm/app/r/s/9Q7Lr
https://gitlab.com/cscs-ci/ci-testing/webhook-ci/mirrors/6557018579987861/835515875116201/-/jobs

⚠ it will break daint/eiger dashboards

do not merge: need to change it to logs-performance.reframe.alps


Upgrade django and urllib3

@akatsoulas r?

Coverage remained the same at 87.532% when pulling f0603a9688552c21f79ceedc8231a5f7a59b9b52 on johngian:upgrade-django into 1dffe44738b7bea1467ba041689da9aa2818fdea on mozilla:master.


upgrade dd-trace-go to v1.41.0 or newer

Expected Behavior
Running on Go v 1.19 is supported without errors.
Actual Behavior
I found the program got an error about gc and it exited with a panic.
It seems to be related to dependent module dd-trace-go.
https://github.com/DataDog/datadog-lambda-go/blob/main/go.mod#L13
Please refer this resolved issue; https://github.com/DataDog/dd-trace-go/issues/1455
Specifications

Datadog Go Lambda package version: 1.6.0
Go version:  1.19

Stacktrace
2022-09-09T15:31:31.249+09:00   panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use.
panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use.

2022-09-09T15:31:31.249+09:00	goroutine 1 [running]:

2022-09-09T15:31:31.249+09:00	go4.org/unsafe/assume-no-moving-gc.init.0()

2022-09-09T15:31:31.249+09:00	/go/pkg/mod/go4.org/unsafe/assume-no-moving-gc@v0.0.0-20211027215541-db492cf91b37/untested.go:25 +0x1f4

2022-09-09T15:31:31.250+09:00	EXTENSION Name: datadog-agent State: Registered Events: [INVOKE,SHUTDOWN]

2022-09-09T15:31:31.285+09:00	LOGS Name: datadog-agent State: Already subscribed Types: [platform,function,extension]

@shota-hizawa I have bump the dd-trace-go version and released. Thank you for letting us know!

Hi, @kimi-p
Thank you! I'll try soon.


This shuttle is unpowered also pod fuckery

Description

Reproduction

Screenshots

Additional context

cluster evac shuttle

did that shittle have 2 gens if it did then ce lied


Update Remove-MDATPDevice.ps1

Added notification that the request errored due to a request already in progress. This also enables handling of other errors that may provide additional information in the native error vs. the exceptions received

@alexverboon I've gone through all the action commands and updated them to handle either the DeviceName or DeviceID. Code recycled so they are consistent throughout. Ready to test and merge


[SPARK-4387][PySpark] Refactoring python profiling code to make it extensible

This is a refactor of the profiling feature done by @davies
This will allow us to hook in custom profilers and output sinks more easily.

Sorry, just saw this. Thanks @davies

@udnay this does not merge cleanly. Can you rebase it?

@pwendell I had create another PR #3901 to fix the conflict, also there are some refactor there.
@udnay Would you mind to close this one?

Replaced by #3901


How do you train the TAESD's latent space shared with SD VAE?

Hi Ollin~ I have read a lot about your discussion in Reddit, github gist, and open-sourced project about the VAE in the SD/SDXL Thanks for sharing! I know you are an expert in the VAE study and I'd like to ask you some questions.
As to the TAESD, I learned from your answers in other issues that "TAESD received the image input in [0, 1] and has the scale_factor=1 rather than 0.18215 in SD'. But your model has a totally different structure (it's simpler) than SD.  So I wonder how do you train the TAESD ? From Scratch or Taking reference to some weights in the SD? Besides, I noticed that you mentioned that the TAESD's latent space is compatible with SD, only with the scaling_factor to adjust. This really surprised me and what magic did you take to make these two latent spaces compatible? I'm new to the distillation and would you be kind to tell how you realized this?
The official SD' VAE is trained with a small KL-weight 1e-6 and it indeed has a large variance distribution in the latent space (std=1/0.18215) and then SDXL has a larger variance (std=1/0.13025).   I have also trained the SD'VAE, and according to the experiment, the std of latent space tends to decrease (the kl loss is also decreasing). Does your TAESD have the same tendency?

how do you train the TAESD ? From Scratch or Taking reference to some weights in the SD?
TAESD weights are initialized from scratch, but TAESD is supervised using outputs from the SD VAE.

what magic did you take to make these two latent spaces compatible
TAESD is just trained to directly mimic the SD encoder / decoder, without using any KL loss or whatever. In pseudocode:

def taesd_training_loss(real_images, taesd, sdvae):
    taesd_latents = taesd.encoder(real_images)
    sdvae_latents = apply_scaling_factor(sdvae.encoder(real_images))
    taesd_images = taesd.decoder(sdvae_latents)

   # in the ideal case latent_loss and image_loss would be F.mse_loss,
   # but in practice they're some mix of adversarial and perceptual loss terms
   return latent_loss(taesd_latents, sdvae_latents) + image_loss(taesd_images, real_images)

https://github.com/madebyollin/taesd/issues/11#issuecomment-1914990359 has more detail about the approach used

according to the experiment, the std of latent space tends to decrease (the kl loss is also decreasing). Does your TAESD have the same tendency?

TAESD is entirely deterministic and doesn't use any KL loss. So, no :)

Thanks for your response. It really helps!


how to set the video as AspectFill

how to set the video as AspectFill

Hi @janczakb , you can refer to #23

@josejuanqm  Now it does not work. Using this command causes a crash

@janczakb Oh, ok. Can you post the crash log here?
I just tested on the example and seems to be working ok. But please post so that I can help.
Thanks!


Possible DeadlyReentry issue

With the recent release of 7.0.0, DeadlyReentry has been upgraded to support KSP 1.0.2. While there are a few PR for the netkan to reflect this, we already have .ckan file for 7.0.0 and 7.0.1. When the netkan metadata updates, I guess the 7.0.0 .ckan file will not be updated.
Currently, it should be visible for users of KSP 0.90, but I am unsure if it supports that version of KSP. Can someone with a 0.90 KSP version check the compatibility between DeadlyReentry 7.0.0 (And perhaps also 7.0.1 in case of a positive result) and report back, as I don't have access to a KSP 0.90 install.
TL;DR: We might have stale, invalid metadata for DeadlyReentry in the form of the version 7.0.0 file. Can someone with a KSP 0.90 install check this.

Fixed in https://github.com/KSP-CKAN/CKAN-meta/commit/8cbe9d8c0ad99acee8af5323e4faeea43901f176.


NetflixStockPrediction added

#480

I've added under NYSE folder pls @Akshat111111 check it

i've already told that when i cloned the repo i didn't get all the file NYSE has missed and some of are also you told make fresh PR i've made again told make PR under NYSE so i've made NYSE folder then i made new PR now again you are telling under NYSE folder that i'm unble to find that folder.
pls merge it otherwise close it i'm unable to find NYSE folder @Akshat111111

 i've already told that when i cloned the repo i didn't get all the file NYSE has missed and some of are also you told make fresh PR i've made again told make PR under NYSE so i've made NYSE folder then i made new PR now again you are telling under NYSE folder that i'm unble to find that folder. pls merge it otherwise close it i'm unable to find NYSE folder @Akshat111111

@ashis2004 Have you synchronous the cloned repo?

 i've already told that when i cloned the repo i didn't get all the file NYSE has missed and some of are also you told make fresh PR i've made again told make PR under NYSE so i've made NYSE folder then i made new PR now again you are telling under NYSE folder that i'm unble to find that folder. pls merge it otherwise close it i'm unable to find NYSE folder @Akshat111111

@ashis2004 Have you synchronous the cloned repo?

yes in the starting i got error and unable to clone the repo then i've watched this video
https://youtu.be/qactwdDmluI?si=H9knLrQVWg-MUMIL
then i follwed the steps i got some files not all

@ashis2004 In the beginning I also this issue then I have done it manually using vscode

You can try this and for update or synchronous try sync fork

Amarta113

getting error

It looks like it is due to the large size of repo.

It looks like it is due to the large size of repo.

What did I do now?

@ashis2004
In your forked repository there is an option of add file from here you can add the file:

After that open pr from here :

It may help you so

Add your file in the particular folder mention by @Akshat111111
Like this

okay thank you

@Akshat111111 pls check it I've uploaded


Update SUPPORT.md

Support for this PROJECT or PRODUCT is limited to the resources listed above.

We need to specify here

Refers to: SUPPORT.md:14 in b9f14c8. [](commit_id = b9f14c8aa21d87d134b86f687012f60c63bde6ce, deletion_comment = False)


Flash write data exception during OTA upgrade (IDFGH-10448)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.0.2
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32-C2
Power Supply used.
External 5V
What is the expected behavior?
When OTA upgrade, flash write data is the same as read data
What is the actual behavior?

When OTA upgrade, calculate the checksum value before writing data to flash, and then read it out after writing to calculate the checksum value, the two are not consistent.
and each time an exception occurs from the offset address 65536.
File transfer protocol is Xmodem-1k.
Steps to reproduce.

Trigger xmodem-1k upgrade process
Preparation before transferring files

    /* TODO:擦除升级固件所在的所有页 */
    /* 获取当前系统下一个（紧邻当前使用的OTA_X分区）可用于烧录升级固件的Flash分区 */
    partition_data_ota = esp_ota_get_next_update_partition(NULL);
    if (NULL == partition_data_ota)
    {
        HAL_xmodemDebugPrint("esp_ota_get_next_update_partition fail!!!\r\n", strlen("esp_ota_get_next_update_partition fail!!!\r\n"));
    }

    if (esp_ota_begin(partition_data_ota, OTA_SIZE_UNKNOWN, &update_handle) != 0) //启动OTA模块要进行烧写
    {
        HAL_xmodemDebugPrint("esp_ota_begin failed\r\n", strlen("esp_ota_begin failed\r\n"));
    }

    int err = esp_partition_erase_range(partition_data_ota, 0, partition_data_ota->size);
    printf("err = %d\r\n", err);

    printf("size = %ld. addr = %ld", partition_data_ota->size, partition_data_ota->address);

Flow of writing to flash

int32_t HAL_flashWrite(uint8_t *buf, uint32_t len,uint32_t offset)
{
    uint8_t src[1024] = { 0 };
    int32_t err;
    printf("w offset :%ld\r\n", offset);
    // err = flash.ota_write(update_handle, buf, len);
    esp_partition_erase_range(partition_data_ota, (offset / 4096) * 4096 - partition_data_ota->address, 4096);
    err = esp_ota_write_with_offset(update_handle, buf, len, offset);
    printf("w err :%ld\r\n", err);
    err = esp_partition_read(partition_data_ota, offset, src, len);
    printf("R err :%ld\r\n", err);
    write_crc = xmodemCrc16(src, len);
    printf("R crc :%04X\r\n", write_crc);
    esp_rom_md5_update(&md5, src, len);

    return err;
}

When HAL_flashWrite() passes in an offset real parameter of 65536, the checksum value calculated by xmodemCrc16() is different from the one before writing

Debug Logs.
No response
More Information.
No response

Hello @BurnerK
Can you share the code to reproduce this issue? Please Also share the sdkconfig file you are using when building the application.

Hello @BurnerK Can you share the code to reproduce this issue? Please also share the sdkconfig file you are using when building the application.

Thanks, the problem has been solved, it's the rest of the code that takes up the flash address.


[docs] Further improve quickstart.js

To avoid confusion, I think we should remove the Document created console output since firestore.doc() merely returns a reference. It does not talk to the backend.

Thanks for the test fix :) I was unaware this test existed.


App crashing on sony experia with android 6

I'm getting this error (only on a sony experia):
java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
                                                             at android.util.ResolutionOverride.<init>(ResolutionOverride.java:56)
                                                             at android.view.SurfaceView.init(SurfaceView.java:207)
                                                             at android.view.SurfaceView.<init>(SurfaceView.java:187)
                                                             at maps.X.x.<init>(Unknown Source)
                                                             at maps.X.v.<init>(Unknown Source)
                                                             at maps.E.u.<init>(Unknown Source)
                                                             at maps.E.u.a(Unknown Source)
                                                             at maps.ag.ad.a(Unknown Source)
                                                             at maps.ag.t.a(Unknown Source)
                                                             at maps.ag.Q.a(Unknown Source)
                                                             at vn.onTransact(:com.google.android.gms.DynamiteModulesB:66)
                                                             at android.os.Binder.transact(Binder.java:387)
                                                             at com.google.android.gms.maps.internal.IMapViewDelegate$zza$zza.onCreate(Unknown Source)
                                                             at com.google.android.gms.maps.MapView$zza.onCreate(Unknown Source)
                                                             at com.google.android.gms.dynamic.zza$3.zzb(Unknown Source)
                                                             at com.google.android.gms.dynamic.zza$1.zza(Unknown Source)
                                                             at com.google.android.gms.maps.MapView$zzb.zzzW(Unknown Source)
                                                             at com.google.android.gms.maps.MapView$zzb.zza(Unknown Source)
                                                             at com.google.android.gms.dynamic.zza.zza(Unknown Source)
                                                             at com.google.android.gms.dynamic.zza.onCreate(Unknown Source)
                                                             at com.google.android.gms.maps.MapView.onCreate(Unknown Source)
                                                             at com.AirMaps.AirMapView.<init>(AirMapView.java:71)
                                                             at com.AirMaps.AirMapManager.createViewInstance(AirMapManager.java:70)
                                                             at com.AirMaps.AirMapManager.createViewInstance(AirMapManager.java:27)
                                                             at com.facebook.react.uimanager.ViewManager.createView(ViewManager.java:44)

As are a few other people:
https://code.google.com/p/gmaps-api-issues/issues/detail?id=9071
and: https://github.com/lelandrichardson/react-native-maps/issues/165
Does anyone know of a solution?

I'm working on a fix using the activity context as suggested by others. If you have access to a sony xperia device to test, can you try the fork at https://github.com/locly/react-native-maps/tree/0.4-stable and let me know the outcome and on what device you tested?

Change react-native-maps in package.json to be "git://github.com/locly/react-native-maps.git#0.4-stable"
Change android/app/src/main/java/com//MainActivity.java to have "new AirPackage(this)" rather than just new AirPackage().

I made the change and asked someone to try it for me on their sony but they said the app just crashed.  I'll try and get a stack trace from them soon.

I've pushed another change to use the activity context in the AirMapView.
Have also just got a Z5 Compact here and can confirm it now works without crashing.
Can you update your package.json to this and confirm if it works for you?
"git://github.com/locly/react-native-maps.git#6d393fb6796deb4f8620533cee5c90cb8051d48f"

Should I change new AirPackage() to new AirPackage(this)?

Yes, it should be new AirPackage(this)

Ok, looks like that change worked on a Xperia Z5 Compact running Android 6.0

Great - I'll post to #165 to get others to test and then prep a PR

Getting this error on Xiaomi Note 3 Pro.

@sirwoetang can you post some more info on the error you're getting?

@locly, i am quickly stepping through all of the solution variants above and will post the trace if it persists.

This fix is based on the 0.4-stable branch rather than 0.5, which introduced the change of name - yet to update the 0.5 version.

Cool, your fix on this fork works for Xiaomi Note Pro 3 and Xiaomi Mi4c.

Any idea when there will be a release containing the fix?

Just get this error on Asus ZenPhone 2 (Android 6.0.1).

Hey guys, after update react-native-maps from master (after this PR: https://github.com/airbnb/react-native-maps/pull/589) the app is no longer crashes with this error!

The issue still persists on Xiaomi Redmi Note 3.
Android: 5.1
react-native-maps: 0.10.0
react-native: 0.33.1

I am also getting this issue, here is my trace:

Stack Trace
java.lang.NullPointerException Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference
ResolutionOverride.java:56 android.util.ResolutionOverride.
SurfaceView.java:207 android.view.SurfaceView.init
SurfaceView.java:187 android.view.SurfaceView.
:com.google.android.gms.DynamiteModulesB:231 com.google.maps.api.android.lib6.gmm6.vector.an.
:com.google.android.gms.DynamiteModulesB:163 com.google.maps.api.android.lib6.gmm6.vector.ai.
:com.google.android.gms.DynamiteModulesB:389 com.google.maps.api.android.lib6.gmm6.api.ao.
:com.google.android.gms.DynamiteModulesB:349 com.google.maps.api.android.lib6.gmm6.api.ao.a
:com.google.android.gms.DynamiteModulesB:4048 com.google.android.gms.maps.internal.eb.a
:com.google.android.gms.DynamiteModulesB:403 com.google.maps.api.android.lib6.impl.az.a
:com.google.android.gms.DynamiteModulesB:308 com.google.maps.api.android.lib6.impl.az.a
:com.google.android.gms.DynamiteModulesB:79 com.google.maps.api.android.lib6.impl.da.a
:com.google.android.gms.DynamiteModulesB:66 com.google.android.gms.maps.internal.z.onTransact
Binder.java:387 android.os.Binder.transact
Unknown:-1 com.google.android.gms.maps.internal.IMapViewDelegate$zza$zza.onCreate
Unknown:-1 com.google.android.gms.maps.MapView$zza.onCreate
Unknown:-1 com.google.android.gms.dynamic.zza$3.zzb
Unknown:-1 com.google.android.gms.dynamic.zza$1.zza
Unknown:-1 com.google.android.gms.maps.MapView$zzb.zzbsp
Unknown:-1 com.google.android.gms.maps.MapView$zzb.zza
Unknown:-1 com.google.android.gms.dynamic.zza.zza
Unknown:-1 com.google.android.gms.dynamic.zza.onCreate
Unknown:-1 com.google.android.gms.maps.MapView.onCreate
AirMapView.java:93 com.airbnb.android.react.maps.AirMapView.
AirMapManager.java:62 com.airbnb.android.react.maps.AirMapManager.createViewInstance
AirMapManager.java:29 com.airbnb.android.react.maps.AirMapManager.createViewInstance
ViewManager.java:46 com.facebook.react.uimanager.ViewManager.createView
NativeViewHierarchyManager.java:218 com.facebook.react.uimanager.NativeViewHierarchyManager.createView
UIViewOperationQueue.java:149 com.facebook.react.uimanager.UIViewOperationQueue$CreateViewOperation.execute
UIViewOperationQueue.java:892 com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.dispatchPendingNonBatchedOperations
UIViewOperationQueue.java:865 com.facebook.react.uimanager.UIViewOperationQueue$DispatchUIFrameCallback.doFrameGuarded
GuardedChoreographerFrameCallback.java:32 com.facebook.react.uimanager.GuardedChoreographerFrameCallback.doFrame
ReactChoreographer.java:131 com.facebook.react.uimanager.ReactChoreographer$ReactChoreographerDispatcher.doFrame
Choreographer.java:856 android.view.Choreographer$CallbackRecord.run
Choreographer.java:670 android.view.Choreographer.doCallbacks
Choreographer.java:603 android.view.Choreographer.doFrame
Choreographer.java:844 android.view.Choreographer$FrameDisplayEventReceiver.run
Handler.java:743 android.os.Handler.handleCallback
Handler.java:95 android.os.Handler.dispatchMessage
Looper.java:171 android.os.Looper.loop
ActivityThread.java:5417 android.app.ActivityThread.main
Method.java:-2 java.lang.reflect.Method.invoke
ZygoteInit.java:726 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run
ZygoteInit.java:616 com.android.internal.os.ZygoteInit.main

@the-simian Any update ??

@iiitmahesh I still get this issue, but I see it intermittently in our tracker. Unfortunately no updates.


Remove unused sub-crates from master

We still have them in the git history, if/when we want them back.
@hero78119 Thanks for the suggestion.

related to #316


Could not find 'bundler'

Software

osx 10.11.4
rbenv 1.0.0
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin15]
Rails 4.2.6

bundle exec gem list|grep guard
guard (2.13.0)
guard-compat (1.2.1)
guard-rspec (4.6.5)

bundle exec guard -d
RubyDep: WARNING: Your Ruby has security vulnerabilities! (To disable warnings, set RUBY_DEP_GEM_SILENCE_WARNINGS=1)
RubyDep: WARNING: Your Ruby is: 2.2.3 (insecure). Recommendation: install 2.2.5 or 2.3.1. (Or, at least to 2.2.4 or 2.3.0)
00:54:56 - DEBUG - Notiffany: gntp not available (Please add "gem 'ruby_gntp'" to your Gemfile and run your app with "bundle exec".).
00:54:56 - DEBUG - Notiffany: growl not available (Please add "gem 'growl'" to your Gemfile and run your app with "bundle exec".).
00:54:56 - DEBUG - Notiffany: terminal_notifier not available (Please add "gem 'terminal-notifier-guard'" to your Gemfile and run your app with "bundle exec".).
00:54:56 - DEBUG - Notiffany: libnotify not available (Unsupported platform "darwin15.4.0").
00:54:56 - DEBUG - Notiffany: notifysend not available (Unsupported platform "darwin15.4.0").
00:54:56 - DEBUG - Notiffany: notifu not available (Unsupported platform "darwin15.4.0").
00:54:56 - DEBUG - Command execution: {"ALTERNATE_EDITOR"=>"false"} emacsclient --eval '1'
00:54:56 - DEBUG - Notiffany: emacs not available (Emacs client failed).
00:54:56 - DEBUG - Notiffany: tmux not available (:tmux notifier is only available inside a TMux session.).
00:54:56 - DEBUG - Notiffany: file not available (No :path option given).
00:54:56 - DEBUG - Notiffany is using TerminalTitle to send notifications.
00:54:56 - DEBUG - Command execution: hash stty
00:54:56 - DEBUG - Guard starts all plugins
00:54:56 - DEBUG - Hook :start_begin executed for Guard::RSpec
00:54:56 - INFO - Guard::RSpec is running
00:54:56 - DEBUG - Hook :start_end executed for Guard::RSpec
00:54:56 - INFO - Guard is now watching at '/Users/lemon/Documents/chavis'
00:54:56 - DEBUG - Start interactor
00:54:56 - DEBUG - Command execution: stty -g 2>/dev/null
[1] guard(main)>
00:54:58 - DEBUG - Interactor was stopped or killed
00:54:58 - DEBUG - Command execution: stty  2>/dev/null
00:54:58 - INFO - Run all
00:54:58 - DEBUG - Hook :run_all_begin executed for Guard::RSpec
00:54:58 - INFO - Running all specs
/Users/lemon/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/dependency.rb:315:in `to_specs': Could not find 'bundler' (>= 0) among 98 total gem(s) (Gem::LoadError)
Checked in 'GEM_PATH=/Users/lemon/Documents/chavis/vendor/bundle/ruby/2.2.0', execute `gem env` for more information
	from /Users/lemon/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/dependency.rb:324:in `to_spec'
	from /Users/lemon/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_gem.rb:64:in `gem'
	from /Users/lemon/.rbenv/versions/2.2.3/bin/bundle:22:in `<main>'
00:54:58 - ERROR - Failed: "bundle exec rspec -f progress -r /Users/lemon/Documents/chavis/vendor/bundle/ruby/2.2.0/gems/guard-rspec-4.6.5/lib/guard/rspec_formatter.rb -f Guard::RSpecFormatter --failure-exit-code 2  spec" (exit code: 1)

00:54:58 - DEBUG - Start interactor
00:54:58 - DEBUG - Command execution: stty -g 2>/dev/null

gem env
RubyGems Environment:
  - RUBYGEMS VERSION: <IP_ADDRESS>
  - RUBY VERSION: 2.2.3 (2015-08-18 patchlevel 173) [x86_64-darwin15]
  - INSTALLATION DIRECTORY: /Users/lemon/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0
  - RUBY EXECUTABLE: /Users/lemon/.rbenv/versions/2.2.3/bin/ruby
  - EXECUTABLE DIRECTORY: /Users/lemon/.rbenv/versions/2.2.3/bin
  - SPEC CACHE DIRECTORY: /Users/lemon/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /Users/lemon/.rbenv/versions/2.2.3/etc
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-darwin-15
  - GEM PATHS:
     - /Users/lemon/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0
     - /Users/lemon/.gem/ruby/2.2.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
     - :sources => ["https://gems.ruby-china.org/"]
  - REMOTE SOURCES:
     - https://gems.ruby-china.org/
  - SHELL PATH:
     - /Users/lemon/.rbenv/versions/2.2.3/bin
     - /usr/local/Cellar/rbenv/1.0.0/libexec
     - /Users/lemon/.rbenv/shims
     - /usr/local/bin
     - /usr/bin
     - /bin
     - /usr/sbin
     - /sbin

https://github.com/guard/guard-rspec/issues/369

What is the output of bundle env?

I have the same issue on arch-linux with the following:

bundler 1.12.0.pre.2 to 1.12.4 inclusive
rbenv 1.0.0
ruby 2.0.0-p247, 2.3.1
rubygems 2.5.1

ruby versions tested:
ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux]
ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]

Bundler versions 1.12.0.pre.1 and earlier did not exhibit this problem for me.
gem env:
RubyGems Environment:
  - RUBYGEMS VERSION: 2.5.1
  - RUBY VERSION: 2.3.1 (2016-04-26 patchlevel 112) [x86_64-linux]
  - INSTALLATION DIRECTORY: /home/bill/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0
  - USER INSTALLATION DIRECTORY: /home/bill/.gem/ruby/2.3.0
  - RUBY EXECUTABLE: /home/bill/.rbenv/versions/2.3.1/bin/ruby
  - EXECUTABLE DIRECTORY: /home/bill/.rbenv/versions/2.3.1/bin
  - SPEC CACHE DIRECTORY: /home/bill/.gem/specs
  - SYSTEM CONFIGURATION DIRECTORY: /home/bill/.rbenv/versions/2.3.1/etc
  - RUBYGEMS PLATFORMS:
    - ruby
    - x86_64-linux
  - GEM PATHS:
     - /home/bill/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0
     - /home/bill/.gem/ruby/2.3.0
  - GEM CONFIGURATION:
     - :update_sources => true
     - :verbose => true
     - :backtrace => false
     - :bulk_threshold => 1000
     - "gem" => "--no-user-install --no-ri --no-rdoc"
  - REMOTE SOURCES:
     - https://rubygems.org/
  - SHELL PATH:
     - /home/bill/.rbenv/versions/2.3.1/bin
     - /usr/lib/rbenv/libexec
     - /home/bill/.rbenv/plugins/rbenv-binstubs/bin
     - /home/bill/.rbenv/shims
     - /usr/local/sbin
     - /usr/local/bin
     - /usr/bin
     - /opt/cuda/bin
     - /usr/lib/jvm/default/bin
     - /usr/bin/site_perl
     - /usr/bin/vendor_perl
     - /usr/bin/core_perl
     - /usr/local/jdk/bin
     - /home/bill/.gem/ruby/2.1.0/bin

I've narrowed down point where the issue is introduced to #4298. Whether the problem is with bundler or with the way guard uses it I'm not yet sure.

I have created a minimal repo that demonstrates when the issue occurs for me: https://github.com/biinari/bundler-rbenv-guard-issue
Included outputs from bundle env, gem env, bundle exec guard.

I think I've diagnosed this. It's a lot, so I may be missing stuff.
In 1.12.5 (and prior 1.12 versions), bundle exec calls a new method, kernel_load if the cmd to execute (guard in this case) has a ruby shebang in it. => https://github.com/bundler/bundler/blob/a65a2db118ed714586ac4c56a0584c97bf0305df/lib/bundler/cli/exec.rb#L24
Inside kernel_load - "bundler/setup" is required. => https://github.com/bundler/bundler/blob/a65a2db118ed714586ac4c56a0584c97bf0305df/lib/bundler/cli/exec.rb#L62
That drills down into this call stack:
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:413:in `configure_gem_home_and_path'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:60:in `configure'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:121:in `definition'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler.rb:91:in `setup'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/setup.rb:19:in `<top (required)>'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/bundler-1.12.5/lib/bundler/cli/exec.rb:62:in `kernel_load'

...ending at this bit of code:
    def configure_gem_home_and_path
      blank_home = ENV["GEM_HOME"].nil? || ENV["GEM_HOME"].empty?
      if settings[:disable_shared_gems]
        ENV["GEM_PATH"] = ""
      elsif blank_home || Bundler.rubygems.gem_dir != bundle_path.to_s
        possibles = [Bundler.rubygems.gem_dir, Bundler.rubygems.gem_path]
        paths = possibles.flatten.compact.uniq.reject(&:empty?)
        ENV["GEM_PATH"] = paths.join(File::PATH_SEPARATOR)
      end

      configure_gem_home
      bundle_path
    end

Since --path vendor was used, :disable_shared_gems is true, so ENV['GEM_PATH'] isn't set to nil (like it would be in 1.11.2 which doesn't involve any of this setup) but set to empty string.
Once we jump over to the new process, we hit this initial code load Gem.activate_bin_path('bundler', 'bundle', version) which leads into this call stack:
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/site_ruby/2.3.0/rubygems/dependency.rb:279:in `matching_specs'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/site_ruby/2.3.0/rubygems.rb:248:in `find_spec_for_exe'
/Users/chrismo/.rbenv/versions/2.3.1/lib/ruby/site_ruby/2.3.0/rubygems.rb:278:in `activate_bin_path'
/Users/chrismo/.rbenv/versions/2.3.1/bin/bundle:22:in `<main>'

and no matching specs are found, because when Gem.path is setup in path_support.rb:
    @path = split_gem_path env["GEM_PATH"], @home

  def split_gem_path gpaths, home
    # FIX: it should be [home, *path], not [*path, home]

    gem_path = []

    if gpaths
      gem_path = gpaths.split(Gem.path_separator)
      # Handle the path_separator being set to a regexp, which will cause
      # end_with? to error
      if gpaths =~ /#{Gem.path_separator}\z/
        gem_path += default_path
      end

      if File::ALT_SEPARATOR then
        gem_path.map! do |this_path|
          this_path.gsub File::ALT_SEPARATOR, File::SEPARATOR
        end
      end

      gem_path << home
    else
      gem_path = default_path
    end

    gem_path.uniq
  end

=> https://github.com/rubygems/rubygems/blob/9c1101160d1b7394a4acc96f0e183334d7346dfe/lib/rubygems/path_support.rb#L65 (2.6.4)
If gpaths is "" or nil it matters. When nil (1.11.2 behavior), then Gem.path gets GEM_HOME included, which is where bundler exists. In this case in 1.12.5, it doesn't, and bundler itself isn't installed in only the vendor path ... therefore - kerblooie.
Since kernel_load hits up bundler/setup and there's a ton of stuff in there, I don't know of a potential patch - bypassing all of that seems suspect. (cc @segiddins).

changing that code to be nil makes this pass - but that code is ooooold ... so no idea how risky that is otherwise.
      if settings[:disable_shared_gems]
        ENV["GEM_PATH"] = nil   # <= ...

@chrismo a PR changing to to nil would be great :D

I ran it locally, and got mixed results on specs, but then again I don't think I've run the whole suite locally recently, so I'll push up a PR in a bit.

First shot tests passing, just pushed up a legit commit with a small method extract and a spec to match. We'll check on it mañana.

@chrismo Can you please look into #4974. This fix might have changed bundler install --deployment behaviour.


fix(chgm): Clean up PD notes when fields are empty

OSD-11939
Updates the notes so the UserName and IssuerUserName fields are not printed when empty. The ServiceLog Sent field will display 'None' when empty.

/lgtm


Parsing  attributes to transform from string to object

Fixes issue mentioned in https://github.com/noraesae/react-render-html/issues/3

Great work! I didn't know that style should be handled specially. Thanks!


Panel preview stops refreshing after datasource query error

What did you do?
Enter the edit mode of a panel, change the datasource to a broken one (url not reachable or whatever), then change back to the previous & working datasource.
What did you expect to see?
The panel preview should refresh and display back a proper graph that should replace the error message that appeared after selecting a broken datasource.
What did you see instead? Under which circumstances?
The error message persists. You have to save to go back to the dashboard view and optionally to refresh the page to finally get your graph.
Perses version
0.39

Has most probably the same root cause as #1337.


Remove pre IE10 code and convert JS code to vanilla JS

One less JS file, faster load due to async.

👍


Document EncryptionConfiguration format for kube-apiserver

This is a Feature Request

What would you like to be added

Within https://kubernetes.io/docs/reference/config-api/ add a new generated page that documents the format for an encryption configuration.
Update https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/ to hyperlink to that new reference

Why is this needed
Within apiserver.config.k8s.io/v1, there is a configuration format for the API server, EncryptionConfiguration. At the moment that format is not documented in https://kubernetes.io/docs/reference/config-api/
Readers may want to look up what that format covers.
Comments
/sig api-machinery
/sig auth
/kind feature
/language en

/triage accepted

/assign
This file is already generated in the generator. All we need to do is to copy it to the website repo.


generatePerson sometimes generates invalid id

It looks like either the generatePerson function or info has some bug in it. If I use generatePerson to create a kennitala and then use info to parse it, info sometimes results in invalid kennitala.
it('should return a valid national id', () => {
      const nationalId = generatePerson(new Date())!
      const nationalIdInfo = info(nationalId)
      expect(nationalIdInfo?.valid).toEqual(true)
    })

Example of a kennitala created with generatePerson
  {
      kt: '0101210190',
      valid: false,
      type: 'invalid',
      birthday: Invalid Date,
      birthdayReadable: '',
      age: NaN
    }

This test is flaky. I'm using version 2.0.6.

Also should the Date parameter be optional for generatePerson? it looks like it's required now :)

Thanks for the bug report @Herdismaria
I think the tests might be failing because like the KT you generated shows it has a 7th-8th digits of 01 which would be illegal for persons since they start generating personal ID's at 20 and up.
Looks like the bug is residing in ./src/generation.ts where startingIncrement should have a default value of 20.
I'll push out a fix for after work today. Apologies for the inconvenience. If you want a quick fix you can add 20 as an optional parameter to your generatePerson function call.
const generatePerson = (
  date: Date,
  startingIncrement?: number
): string | undefined => {
  return generateKennitala(date, personDayDelta, startingIncrement);
};

Also should the Date parameter be optional for generatePerson? it looks like it's required now :)

Interesting thought. So if the Date parameter is optional we could generate a random Date as a default parameter?
Would be a cool feature

Fixed in #36
Thanks for creating the issue!

Fixed in V3.0.0 that was released just now. Thanks a lot for reporting this, I think it would have gone unnoticed for a while otherwise :)


downgrade jsdom to avoid nwsapi

Fixes #1330. Supersedes #1331.

It’d probably be useful for us to run yarn upgrade and make sure we’re also testing against the latest dependencies… We were still running against nwsapi 2.2.7 which is why we didn’t notice the problem.

LGTM with a caveat: "^23.0.0" accepts both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>which means we don't guarantee which CSS selector engine is used. To be clear, 23.2.0 is OK, but 23.1.0 is broken (tested broken) — and any previous version is probably broken too because they all use nwsapi.
So I think we'd be better off being explicit about "jsdom": "=23.2.0"?

I think we should do ^23.2.0 since that’s pretty standard and if they were to do a patch on 23.x it seems like they would keep the same non-broken selectors implementation.


github: workflows: Check port usage

Let's see port 6000 and 7000 are already in use or not.

They are not used.


[Test Harness] Add test harness library

Adds a new testing library, testharness for testing Compose layouts.

Want to add isRound? :)

Want to add isRound? :)

For isRound, I'd want to do more investigation with how the APIs handle rendering outside of the round viewport on a circular watch.
For example: if you render something in the very corner of a physically round watch (such that it isn't actually visible), do the testing APIs treat it as being visible?
If they do, the isRound should be just a matter of flipping the Configuration flag, otherwise we could inset the content within the round viewport.

Please add an issue template to .github/ISSUE_TEMPLATE and also an entry for the docs generation into mkdocs.yml

Added, along with a first draft of documentation as well.

Also, is there no sample for this project?

There are the tests of the TestHarness itself, and I converted some tests in pager and adaptive where it makes sense to use TestHarness, but agreed there should be more.
Do you think it makes sense to add some tests to sample that make use of it? I was thinking a navigation rail versus navigation bar test setup would be a good showcase of it.

Want to add isRound? :)

For isRound, I'd want to do more investigation with how the APIs handle rendering outside of the round viewport on a circular watch.
For example: if you render something in the very corner of a physically round watch (such that it isn't actually visible), do the testing APIs treat it as being visible?
If they do, the isRound should be just a matter of flipping the Configuration flag, otherwise we could inset the content within the round viewport.

Yep, I can follow up.
The answer is yes, they can draw outside the bounds and screenshot tools show content outside.  So for Paparazzi I change both the configuration as you suggest, but also apply a circular crop.

Given the sample is a catalog, we could add a testharness sample (with a big warning so that it's not used in prod)

Once I fix the darkMode issue...
Thoughts?

I've pushed it anyway, but happy to revert.

I tried this to see if it could replace my bespoke code.  Not sure if it's AGP or paparazzi related (I doubt given it's debug code, not test). But seeing
java.lang.NullPointerException: Cannot invoke "android.content.Context.getResources()" because "resContext" is null   at android.view.ContextThemeWrapper.getResourcesInternal(ContextThemeWrapper.java:137)   at android.view.ContextThemeWrapper.getResources(ContextThemeWrapper.java:128)   at androidx.compose.ui.res.Resources_androidKt.resources(Resources.android.kt:33)   at androidx.compose.ui.res.StringResources_androidKt.stringResource(StringResources.android.kt:35)

Hopefully some typo in my copy/paste/simplification. But wanted to flag.

Hopefully some typo in my copy/paste/simplification. But wanted to flag.

I can't think of anything that the harness might be doing that might be affecting resource loading. Can you share your code?

Hopefully some typo in my copy/paste/simplification. But wanted to flag.

I can't think of anything that the harness might be doing that might be affecting resource loading. Can you share your code?

https://github.com/yschimke/horologist/commit/155971e206ce01afa69238ba9ced67e44397c719
Don't block on this, mainly flagging in case it's a more general problem.

For completeness I would suggest one of the tests being to change the locale and call stringResource() from a composable.

List of updates since your approval @bentrengrove :

Added test harness sample
Added locale overriding to sample and tests
Documented current @Preview limitation

Got the Trengrove :rocket: of approval offline, merging!


identityToken is null

Hi there ! It seems like the login button works, but in the callback the identityToken is never returned, which I need to validate the user server side. The user id and the email are correctly returned.

Just as a side note, the expo module does return the identityToken, so it is probably not some kind of bad setup on my project.

Are you still not able to receive identity token? I'm closing this issue for now. Feel free to open it again if the issue still exists.


Plan for the next version

[ ] migrate all code to ts
[ ] mongo
[ ] meteor-adapter
[ ] graphql
[ ] client

@davidyaha @TimMikeladze

@davidyaha is meteor working with the latest version?

Not sure. Will need to check it out


Support for remote system targets

Neat project been needing something like as opposed to Proxmox Backup.
Not clear from the README, is there support for remote data?

Remote data as something like nfs or cifs? Mount them under the data path, then you can backup them like local files.

While mounting is always nice, hoping to instead let it run as a server that accepts input streams

Writing to a tape device needs foreseeable input speed, for LTO5 it's 140MB/s, for LTO6 it's 160MB/s, etc. If we accept an input stream, current read mechanisms that is made to keep up this speed (like preload file with mmap hint) will be disabled. And tbh networks always have some problems making the link speed lower than expected. Lower input speed is likely to cause shoe-shining and other problems while writing. I would suggest avoiding using remote file systems if possible, let along input streams.


Disable Sent Metric Types Globally

Hi everyone,
I like to contribute a new feature to metrics-graphite.
Currently, all "metric types" of a metric are sent to graphite. If you have a Timer you will always get max, mean, min, stddev, p50, p75, p95, p98, p99, p999. However, in reality only some of them are really used for monitoring. It would be great, if I could select the metric types that will be send. This way, we can reduce the load on both the network and graphite and save storage.
Cheers, Philipp

Hello Philipp,
Sorry to get to back to you late. Your pull request looks reasonable, but could you say why you don't want to use MetricFilter to specify metrics which should be reported? I guess your use case could be implement as:
final Set<String> disabledMetricTypes = new HashSet<String>();
disabledMetricTypes.add(MetricTypes.M15_RATE);
disabledMetricTypes.add(MetricTypes.M5_RATE);

GraphiteReporter.forRegistry(registry) .filter(new MetricFilter() {
                    @Override
                    public boolean matches(String name, Metric metric) {
                        return !disabledMetricTypes.contains(name);
                    }
                })

HI Artem,
thanks for your feedback. Does this work for you? It doesn't work for me, because name doesn't contain the metric type. The values look like this:
heap.committed
heap.used
classes
httpsessions.max
systemload.average
mem.free
processors
gc.ps_marksweep.count
threads.peak
mem
nonheap.used
heap

I'm using Metrics in conjunction with Spring Boot Actuator. Maybe this is the reason.

Got it. My biggest concern for this feature is that we implement it only for GraphiteReporter, but not for other reporters. On the other hand, judging that every reporter has an own mechanism for sending metrics, it's rather hard to generalize it. I think we can start with Graphite for the time being.

Good points. I changed the code according to your feedback. Are you okay with my changes?

Looks better! Unfortunately, the pull requests still has merging conflicts. I think we could make at least mergeable, so folks who are interested in this feature could build it locally.

@ryantenney mentioned that we will likely pass on this feature for the 3.2.* branch, because it creates a disparity between reporters. But we definitely can consider for it Metrics 4.0.0, perhaps in a more generic manner.

Superseded by #1048


Illegal reflective access issue with Java 11 on server start

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by me.lucko.luckperms.common.dependencies.classloader.ReflectionClassLoader (file:/C:/CivcraftBETA/plugins/LuckPerms-Bukkit-4.4.1.jar) to method java.net.URLClassLoader.addURL(java.net.URL)
WARNING: Please consider reporting this to the maintainers of me.lucko.luckperms.common.dependencies.classloader.ReflectionClassLoader
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Using 1.13.2 Paper Build 641

See #952

dang, ty


Fix Fresco initialisation

Fixes #986.
Reasons explained in the issue thread.

Thanks @maskaravivek ! The release build passes for me, so I will go ahead and merge this before doing the final pre-release testing. :)


FSharp.Formatting for F# 3.1 implicitly reading FSharp.Core <IP_ADDRESS>

I'm using the latest FSharp.Formatting on a Windows machine with both F# 4.0 and F# 3.1 installed. I'm running from a F# 3.1 command prompt.
I'm getting an error where the FSharp.Core <IP_ADDRESS> (from F# 4.0) is now being used by the FSharp.Formatting toolchain (for example the error below).  This is a bug - the FSharp.Formatting toolchain is currently built on FSharp.Compiler.Service for F# 3.1 and should never be reading FSharp.Core <IP_ADDRESS> unless explicitly directed to do so.
Has the change to Yaaf.FSharp.Scripting caused this?  Or is it an implicit reference to FSharp.Core <IP_ADDRESS> flowing from elsewhere, e.g. FCS itself?  Either way the FSharp.Formatting tooling feels somewhat broken right now, or at least not working in an isolated way,
I feel we need to move to a model where the reference set being used by interactive evaluation with FSharp.Formatting is more locked down.
    unknown(1,1): error FS0229: Error opening binary file 'C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp\.NETFramework\v4.0\<IP_ADDRESS>\FSharp.Co re.dll': Error reading/writing metadata for the F# compiled DLL 'C:\Program Files (x86)\Reference Assemblies\Microsoft\FSharp\.NETFramework\v4.0\<IP_ADDRESS>\FSharp.Core.dll'. ...).

cheers
don

My impression was that (when invoked via F# Interactive and not as a stand-alone application) F# Formatting will always load the FSharp.Core.dll that is used by the current process. Or is that not the case?
I think this would be sensible behavior - otherwise, the values you get from FsiEvaluator might involve different FSharp.Core.dll types (say, list) than the ones your current process is using... (but I'm not sure if this is actually possible?)

How can I reproduce this? I have installed both F# 4.0 and F# 3.1 as well, but everything seems to be working fine for me.
I agree with @tpetricek and I tested with Yaaf.FSharp.Scripting with the F# 3.1 fsi.exe and the F# 4.0 fsi.exe and it was always using the current FSharp.Core. But it is quite possible that I got something wrong in the FSharp.Core resolution of Yaaf.FSharp.Scripting.

I cant get fsfromatting to work either I get FSahrp.Core version mismatches and also Microsoft.Build.Utilities masmatches when runing the documentation generator for FCS:
FSharp.Formatting Information: 0 : FSharp.Formatting Logging setup!
Yaaf.FSharp.Scriping Information: 0 : Yaaf.FSharp.Scripting Logging setup!
Copying file: /Users/dave/code/FCS/docs/output/images/en.png
Copying file: /Users/dave/code/FCS/docs/output/images/ja.png
Copying file: /Users/dave/code/FCS/docs/output/images/logo.png
Copying file: /Users/dave/code/FCS/docs/output/content/fcs.css
Copying file: /Users/dave/code/FCS/docs/output/content/style.ja.css
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/style.css
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/style.css.bak
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/style_light.css
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/tips.js
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/img/github-blue.png
Copying styles and scripts: /Users/dave/code/FCS/docs/output/content/img/github.png
Generating '/Users/dave/code/FCS/docs/tools/../content/caches.html'
FSharp.Formatting Critical: 0 :
Processing the file 'docpage' failed
Source written to: '/var/folders/5v/p_5h35nd70s8x7fh8fqn7hyh0000gn/T/tmp47c63951.tmp.cs'
Compilation errors:
 - warning: (0, 0) Assuming assembly reference `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' matches assembly `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. You may need to supply runtime policy
 - error: (0, 0) Assembly `Microsoft.Build.Utilities.v12.0, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' references `Microsoft.Build.Framework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version number than imported assembly `Microsoft.Build.Framework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

System.Exception: Generating HTML failed.
   at FSharp.Literate.RazorRender.handleCompile[a] (System.String source, Microsoft.FSharp.Core.FSharpFunc`2 f) in <filename unknown>:line 0
   at FSharp.Literate.RazorRender.ProcessFileModel[b] (System.Type modelType, System.Object model, Microsoft.FSharp.Core.FSharpOption`1 properties) in <filename unknown>:line 0
   at FSharp.Literate.Templating.generateFile (Microsoft.FSharp.Core.FSharpOption`1 references, System.String contentTag, IEnumerable`1 parameters, Microsoft.FSharp.Core.FSharpOption`1 templateOpt, System.String output, IEnumerable`1 layoutRoots) in <filename unknown>:line 0
   at FSharp.Literate.Templating.processFile (Microsoft.FSharp.Core.FSharpOption`1 references, FSharp.Literate.LiterateDocument doc, System.String output, FSharp.Literate.ProcessingContext ctx) in <filename unknown>:line 0
   at FSharp.Literate.Literate.ProcessScriptFile (System.String input, Microsoft.FSharp.Core.FSharpOption`1 templateFile, Microsoft.FSharp.Core.FSharpOption`1 output, Microsoft.FSharp.Core.FSharpOption`1 format, Microsoft.FSharp.Core.FSharpOption`1 formatAgent, Microsoft.FSharp.Core.FSharpOption`1 prefix, Microsoft.FSharp.Core.FSharpOption`1 compilerOptions, Microsoft.FSharp.Core.FSharpOption`1 lineNumbers, Microsoft.FSharp.Core.FSharpOption`1 references, Microsoft.FSharp.Core.FSharpOption`1 fsiEvaluator, Microsoft.FSharp.Core.FSharpOption`1 replacements, Microsoft.FSharp.Core.FSharpOption`1 includeSource, Microsoft.FSharp.Core.FSharpOption`1 layoutRoots, Microsoft.FSharp.Core.FSharpOption`1 generateAnchors, Microsoft.FSharp.Core.FSharpOption`1 assemblyReferences, Microsoft.FSharp.Core.FSharpOption`1 customizeDocument) in <filename unknown>:line 0
   at<EMAIL_ADDRESS>(System.String file, System.String output) in <filename unknown>:line 0
   at Microsoft.FSharp.Core.FSharpFunc`2[T,TResult].InvokeFast[V] (Microsoft.FSharp.Core.FSharpFunc`2 func, Microsoft.FSharp.Core.T arg1, Microsoft.FSharp.Core.TResult arg2) in <filename unknown>:line 0
   at <StartupCode$FSharp-Literate>.$Main.processDirectory@199 (Microsoft.FSharp.Core.FSharpOption`1 format, Boolean processRecursive, Microsoft.FSharp.Core.FSharpFunc`2 processScriptFile, Microsoft.FSharp.Core.FSharpFunc`2 processMarkdown, System.String indir, System.String outdir) in <filename unknown>:line 0
   at FSharp.Literate.Literate.ProcessDirectory (System.String inputDirectory, Microsoft.FSharp.Core.FSharpOption`1 templateFile, Microsoft.FSharp.Core.FSharpOption`1 outputDirectory, Microsoft.FSharp.Core.FSharpOption`1 format, Microsoft.FSharp.Core.FSharpOption`1 formatAgent, Microsoft.FSharp.Core.FSharpOption`1 prefix, Microsoft.FSharp.Core.FSharpOption`1 compilerOptions, Microsoft.FSharp.Core.FSharpOption`1 lineNumbers, Microsoft.FSharp.Core.FSharpOption`1 references, Microsoft.FSharp.Core.FSharpOption`1 fsiEvaluator, Microsoft.FSharp.Core.FSharpOption`1 replacements, Microsoft.FSharp.Core.FSharpOption`1 includeSource, Microsoft.FSharp.Core.FSharpOption`1 layoutRoots, Microsoft.FSharp.Core.FSharpOption`1 generateAnchors, Microsoft.FSharp.Core.FSharpOption`1 assemblyReferences, Microsoft.FSharp.Core.FSharpOption`1 processRecursive, Microsoft.FSharp.Core.FSharpOption`1 customizeDocument) in <filename unknown>:line 0
   at FSI_0003.buildDocumentation () in <filename unknown>:line 0
   at <StartupCode$FSI_0003>.$FSI_0003.main@ () in <filename unknown>:line 0
   at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
   at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) in <filename unknown>:line 0
Stopped due to error

I have tried the standalone command line tool with the  metadataformat option with pretty much the same errors.

Same here, building on mac os x (v 10.11.1) I am getting:
Compilation errors:
 - warning: (0, 0) Assuming assembly reference `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' matches assembly `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. You may need to supply runtime policy
 - error: (0, 0) Assembly `FakeLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' references `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version number than imported assembly `FSharp.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

System.Exception: Generating HTML failed.
  at FSharp.Literate.RazorRender.handleCompile[String] (System.String source, Microsoft.FSharp.Core.FSharpFunc`2 f) [0x00000] in <filename unknown>:0
  at FSharp.Literate.RazorRender.ProcessFileModel[IDictionary`2] (System.Type modelType, System.Object model, Microsoft.FSharp.Core.FSharpOption`1 properties) [0x00000] in <filename unknown>:0
...

But when building on Windows or on Linux, everything runs fine. So, it seems to be a mono version dependency issue? On mac os x I am running mono version 4.0.5. The build that passes on Travis uses mono 4.0.4.

Its not a particular mono version I get the same with F# master at https://github.com/fsharp/fsharp

I'm still not sure what's happening here.
One thing I figured out recently is that when running things via FAKE, we always get the version of FSharp.Compiler.Service that comes with FAKE (and is used to invoke the script that then calls F# Formatting which then uses F.C.S.).
This is a bit problematic - in practice, it means we need to keep in sync with FAKE (in some way) - though this is not really a package dependency in one or the other direction.  The most recent releases are synced though, so should work, I think...
But that does not answer the issues with FSharp.Core versions.

There are really 2 use cases for FSharp.Formatting

Library: This means downstream is responsible for either providing a compatible FSharp.Core or otherwise making sure one is available (we always prefer a bundled FSharp.Core).

In build scripts: Since we upgraded to F#4 I think the initial issue from @dsyme is no longer valid (please correct me if I'm wrong). It might come back with the next F# update. I hope I can reproduce it then...
However another issue appeared since upgrading:
Because we call "fsharpi generate.fsx" we will run with a older version of FSharp.Core on systems where F#3 or F#3.1 is installed. This might very well be the reason for the various issues popping up (but I could not reproduce the reported issues instead I got another one).

@7sharp9 @halcwb Can you try to use the following patch (https://github.com/fsprojects/ProjectScaffold/pull/217) in your build scripts and report if that fixes the issues you are seeing?
Let's continue discussing on https://github.com/tpetricek/FSharp.Formatting/issues/356 as I think the initially reported bug is no longer valid (until the next F# upgrade) and sadly I could never reproduce it...

Ill try out the projectscaffold fix although one of my problems was I could not build Fsharp.Formatting, has that now being addressed?

Yes FSF has the same problem in its build script, will update as soon as it is sure that this in fact fixes the problem. Could you test?

See https://github.com/fsprojects/ProjectScaffold/pull/217#issuecomment-158634784


Issue installing Zarf Init - permission denied

Environment
Device and OS: Debian 11
App version: 0.21.3
Kubernetes distro being used: Kind
Other:
Steps to reproduce
When installing Zarf to /usr/local/bin on a linux box (Debian 11), and running as a user. It will try to write the zarf init pkg to /usr/local/bin/ and fail. with a permission denied.
Expected result
Zarf place init pkg into the directory (I think)
Actual Result
Fails with permission denied
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Low - CLI user was able to troubleshoot and fix without referencing docs
Additional Context
Collected from user engagement

That should be when also installing K3s, which the description for the component starts with *** REQUIRES ROOT *** before you confirm deployment.

In this situation the user did not install K3s

/usr/local/bin is owned by root on most systems so yes it will fail here.
Note: This will require an internet connection.
? Do you want to download this init package? Yes
  DEBUG   open /usr/local/bin/zarf-init-amd64.tar.zst: permission denied
└ (/home/wayne/workspace/zarf/src/internal/utils/network.go:61)
     ERROR:  Unable to create the destination file
└ (/home/wayne/workspace/zarf/src/cmd/initialize.go:110)

Yeah or their current working directory might make sense here.

@jeff-mccoy @Racer159 I can ask the user what behavior they would expect - will report back

Yeah or their current working directory might make sense here.
Either would resolve the issue, but a home directory folder might be nice for users managing multiple packages (i.e. many working dirs).

It also might come in handy for future use (like a cobra config or something).

FWIW -- I ran into this on a fresh install of Ubuntu 22.04.

We could also move the --zarf-cache flag to a global flag and then just drop the files in there?

@jeff-mccoy We could try a poll on our K8 channel to see what users would expect the behavior to be?
Can you provide me a clear wording for the three options above?


Update PostLedgerEntryOperation retry logic

Contributing to the Azure SDK
Fixes a bug for PostLedgerEntryOperation in both sync and async clients when using waitUntil.Complete. Azure Confidential Ledger generally has client IP-based stickiness so that users observe session consistency. Occasionally this affinity is lost unexpectedly, which can lead to errors when waiting for a commit (write is made to Node A but the read is on Node B, which doesn't know about the write yet). This can be disruptive, so we introduce a small change to retry some HttpStatusCode.NotFound errors.
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Feature: add additional tests for TiTestPresenter

This pull request closes #125 by adding the missing tests.

Wow! Thank you for that PR. You are just incredible!
On Oct 7, 2017 7:46 PM, "Pascal Welsch"<EMAIL_ADDRESS>wrote:

Merged #127 https://github.com/grandcentrix/ThirtyInch/pull/127.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grandcentrix/ThirtyInch/pull/127#event-1282936934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJwYe1cen0f_sxonJF6kyDrZQE8rpPOEks5sp7kIgaJpZM4Pwtgo
.


 I haven't tried yet but I imagine a 65k context window is too much for my hardware to handle.
I was planning on increasing to GPT-4 and then GPT-4-32k but at this point you might consider refactoring your code before running it to save on costs.

This should be resolved now, assuming the context is less than 32k

I did managed to make it work in the text wui oogabooga or whatever its
called .
and modified the settings.json file lines 17 and 19 i think to 65k
and then launched it with : --model-menu --notebook --model
mosaicml_mpt-7b-storywriter --trust-remote-code
On Tue, 9 May 2023 at 11:36, BillSchumacher @.***>
wrote:

Have you actually been able to run this? I haven't tried yet but I imagine
a 65k context window is too much for my hardware to handle.
I was planning on increasing to GPT-4 and then GPT-4-32k but at this point
you might consider refactoring your code before running it to save on costs.
—
Reply to this email directly, view it on GitHub
https://github.com/BillSchumacher/SumPAI/issues/7#issuecomment-1539198853,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABNVRS4QSHCJ3JKJ76JEM3XFH6Z5ANCNFSM6AAAAAAXZCZCSQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Volumes shall be supported in extended form to specify type of volume

Right now compose file ingestion does not seem to be supporting specifying volumes in extended form (https://docs.docker.com/compose/compose-file/#volumes) and hence it's impossible to specify volume type to be volume as opposed to default bind. It's possible to do it via XML deployment via Driver="local" but not via compose file deployment since it defaults to bind and hence compose file with snippet below will fail via compose
      volumes:
        - whoami:c:\inetpub\logs\logfiles\host

This shall work
        - type: volume
          source: whoami
          target: c:\inetpub\logs\logfiles\host

And below works with XML style deployment which is equivalent of above
<Volume Source="whoami" Destination="c:\inetpub\logs\logfiles\host" IsReadOnly="false" Driver="local"></Volume>

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

ID: 6898cd0d-98c0-9c54-feed-93e5025c1eaf
Version Independent ID: f31f4333-598d-2b12-7138-46d6f0399f50
Content: Azure Service Fabric Docker Compose Deployment Preview
Content Source: articles/service-fabric/service-fabric-docker-compose.md
Service: service-fabric
GitHub Login: @mani-ramaswamy
Microsoft Alias: subramar

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@artisticcheese, thanks for the feedback. Closing due to age and lack of doc-affecting action. If you feel this is still an issue, feel free to reopen with a specific reference to what you believe should change in the article.
#please-close


Integration tests fail to build when mini-dashboard is disabled

Describe the bug
Integration tests fail to build when mini-dashboard feature is disabled.
To Reproduce
cargo test --no-default-features
...
error: couldn't read target/debug/build/meilisearch-http-ec029d8c902cf2cb/out/generated.rs: No such file or directory (os error 2)
 --> meilisearch-http/tests/dashboard/mod.rs:8:9
  |
8 |         include!(concat!(env!("OUT_DIR"), "/generated.rs"));
  |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: this error originates in the macro `include` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `meilisearch-http` due to previous error

Expected behavior
It shall pass.
Meilisearch version: [e.g. v0.20.0]
v0.29.0rc4

Hello @jirutka thanks for the report and the PR!
We will review it asap! 😄


Support for BigAutoField

BigAutoField, is the default value of DEFAULT_AUTO_FIELD for new Django-3.2 projects.

Added https://github.com/jordaneremieff/djantic/commit/859e2e5532c9147edccf0152465a8e66b602e10a


bump-coredns-app

towards https://github.com/giantswarm/giantswarm/issues/28646

e2e do not work atm, merging


WFLY-6607

https://issues.jboss.org/browse/WFLY-6607
fix is based on https://issues.jboss.org/browse/WFCORE-1556

@soul2zimate are you still working on this issue?
This PR needs to be rebased and changed according to my previous comments so that we can merge it.

I have updated this PR. It's been a while,  AFAIU at last time, it can not neither create non-existent socket-binding nor copy(resolve) attributes expression. I just put socketing-binding in place to please the validator, and user needs to update their migrated subsystem based on warning messages.

retest this please

retest this please

@soul2zimate As this pull request has  been held up for a long time, I am closing it to get the pull request queue under control again. Since this is very old now, it will be a very long time until this one will be addressed. Also, I don't have much time to spend on this to evaluate on a case by case basis.
If this is something important to you or the project please feel free to recreate the pull request. That way it will come on top of the pile again, and be looked at again sooner.
If it is a new feature, please follow the new process for features. Ping @kabir or @jamez if you are unsure what this means, and we can help. Please do that before opening the pull request though.
Sorry for any inconvenience!


Implement tests

Codecov Report

Merging #5 (daef323) into main (6732abe) will increase coverage by 8.08%.
The diff coverage is 100.00%.

:exclamation: Current head daef323 differs from pull request most recent head b5056ea. Consider uploading reports for the commit b5056ea to get more accurate results

@@            Coverage Diff             @@
##             main       #5      +/-   ##
==========================================
+ Coverage   70.00%   78.08%   +8.08%
==========================================
  Files           1        5       +4
  Lines          10       73      +63
  Branches        0        4       +4
==========================================
+ Hits            7       57      +50
- Misses          3       15      +12
- Partials        0        1       +1

Impacted Files
Coverage Δ

src/Test/Tasty/AutoCollect/ModuleType.hs
55.55% <ø> (ø)

src/Test/Tasty/AutoCollect/Config.hs
97.67% <100.00%> (ø)

src/Test/Tasty/AutoCollect/Constants.hs
42.85% <0.00%> (ø)

src/Test/Tasty/AutoCollect/Utils/Text.hs
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


LCS Process data package

Team,
The current page seems outdated, the asset library on LCS doent show "Process data package" any more, additionally I am not sure if Configuration data manager is available with LCS anymore.
[Enter feedback here]

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

ID: da1ee1f9-6624-ffbb-70a5-d275c0cf4c62
Version Independent ID: 48f53ecb-a716-e17b-8939-63b669176e73
Content: Process and consume data packages in finance and operations apps - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/lcs-solutions/process-data-packages-lcs-solutions.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @sericks007
Microsoft Alias: sericks

@twheeloc can you please review this feedback? Thanks.

@twheeloc bumping this back onto your radar. Thanks!


Extra assertions on URLs

I want to keep r.releases.utils:::assert_package_lite() the way it is, but r.releases.utils:::assert_package() might need more assertions. One that we are currently missing is to check if the URL is actually online. Anything else we are missing?

There is already a PR for this https://github.com/r-releases/r.releases.utils/pull/5

Thanks @shikokuchuo! Much appreciated!
One might also consider checking that a release exists, but I do not think it is necessary.

To check that we'd probably need to interface with the APIs, and then it's a case of URL manipulation and a lot of extra work for not very much gain.
Did you have anything else to add to this issue?

I can't think of anything else. We might have to do more if https://github.com/r-releases/help/issues/13#issuecomment-1975153905 fails, but according to Jeroen it should succeed.

With #13 solved, I think we can close this one for now.

Hmm... I tried creating a test universe with a released repo that is not an R package, and I saw: https://github.com/r-universe/wlandau-test/actions/runs/8139061504/job/22241346983#step:3:61. I am not sure it is feasible to check for a DESCRIPTION file, and I think non-R-package registrations will not be as common, but it is worth pointing out.

Regardless, I still like how we handled #13.


web scraping project in python

I had learned web scraping in python. so I want to add a beginner friendly project to the repo for web enthusiast.
and I can make it in it in Jupyter notebook with the explanation of every step.
so please assign this issue to me.

Link PR here if made

#272


Mixed language

Thank you for your open-source contributions.
Could you develop a guide to support mixed language? For example, a sentence existing both Chinese and English.

Now Chinese and English is supported. Japanese and English mix is supported too.


Ibex: Write instruction trace into log file

To help debugging test runs, Ibex can now write an instruction trace
into a log file. Create one test-specific log file for each run.
Also create a .objdump-noalias file for each test which calls objdump
with arguments to produce a file closer to what you'd see in the log
files (no ABI names for registers, and no instruction aliases). Using
this file together with the Ibex-generated trace is helpful to debug
test cases.
Depends on https://github.com/lowRISC/ibex/pull/368
Closes lowRISC/ibex#217

Hi Philipp,
Thanks for the contribution. Some comments:

I don't think compliance tests should be generating trace output. I don't think any other compliance target does, and this seems to be beyond the role of a compliance test suite. If it does it should certainly be optional and off by default.
we need a ChangeLog entry, which should also be in the commit message.
should there be some documentation update to go with this change?

Let me know your thoughts.

Having traces available was a request from @eroom1966 (Lee) in https://github.com/lowRISC/ibex/issues/217. It doesn't slow down the execution noticeably and writes files only to the work directory, so I thought it wouldn't hurt to have it unconditionally enabled. I can try adding a switch (it's a bit tricky given the current makefile structure).
Changelog and documentation are good points, I'll add them once we have agreement on how/if to implement this feature.

Ho hum. I'd like to get the wider group's view on this. The original idea was that compliance should only produce a yes/no result as output. I'll send an emal

@imphil @jeremybennett The request I made was unrelated to the riscv-compliance setup
This was to enable the riscv-dv ongoing work to use verilator.
As Jeremy says for compliance - it is simply the signature output.
However, I have also made trace output an optional feature from riscvOVPsim, which is off by default. So I would think that a similar mode (as suggested by Jeremy), to have off by default, but can be enabled, would be fine.

Asking the other way around: What do we loose by always having the trace around, like other log files, objdump intermediate representations, etc.? It doesn't hurt and makes debugging and development of tests easier.
I fully agree that this trace should not in any way considered for the result of the test run.

@imphil
Cannot disagree with your comment. I am not overly concerned to be honest, I presume verilator does not see an IO impact with the trace generation, due the the fact it is an RTL simulation and will be thousands of instructions rather than billions of instructions per second.

Let's see if there are any other feedback from the wider community.
Depending what you are doing, tracing can clobber Verilator performance, although in this case I can't see that matters since the compliance tests are tiny.

Note that these traces are instruction traces (effectively a printf per instruction, rather cheap in simulation time), not signal traces (which slow down Verilator considerably). We run all verification which instruction traces enabled and haven't noticed any real slowdown.
I'll try to get a version running with optional tracing however.

I updated the PR to include a changelog entry.
In my previous comments, I forgot that the Ibex simulation actually always emits the trace. What this PR does it only move it to a sensible directory next to the other log files.

Thanks - I wasn't at the last meeting and was waiting for confirmation


Ubuntu Build error

Hey, I've got this error (Ubuntu 16.04)
Node Version: v16.14.0
NPM Version: v9.3.0
Node-Gyp Version: v9.3.1
npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
npm ERR! In file included from ../cppsrc/js-wrappers/../modules/blit.hpp:2:0,
npm ERR!                  from ../cppsrc/js-wrappers/wrapBlit.cpp:2:
npm ERR! ../cppsrc/js-wrappers/../modules/../util/image.hpp:4:20: fatal error: optional: No such file or directory
npm ERR! compilation terminated.
npm ERR! make: *** [Release/obj.target/jimp-native/cppsrc/js-wrappers/wrapBlit.o] Error 1
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: make failed with exit code: 2

Hm, that's a bit strange. I'll spin up a Ubuntu 16.04 VM and look into it. Thanks for reporting the issue

any update on this?

I had a look at it in a 16.04 setup and I'm able to reproduce it. I can't pinpoint why this happens though. It's not an issue if I install the same version of node on more recent versions of Ubuntu. I'm still looking into it.

After some more digging, I've found the reason why this happens. Ubuntu 16.04 ships with a pretty old version of g++. jimp-native needs C++17 support to work properly. The error you're seeing is because it's unable to load optional from the standard library.
I'm afraid you're going to have to upgrade your version of Ubuntu or find a way to get a more recent version of g++ (from what I can find you'll need at least version 7.1) on your machine to get the build to work. You may have some luck with a PPA. Note that Ubuntu 16.04 is at end of life so if you have any choice in the matter then upgrading is probably the best idea here.


Profiling through code?

Hello,
Thank you for this profiler, I've been on the lookout for one that works with Numba!
Is it possible to profile specific function calls and not an entire file? I'm trying to profile a large python package that uses numba, but the part that uses numba cannot be called independently. Is there a way to do this currently?
This is what I get when I run the script that calls my package internally
/home/dyuman/miniconda3/envs/pyreason-dev/lib/python3.9/site-packages/numba/typed/typeddict.py:23: NumbaDebugInfoWarning: Could not find source for function: <function unicode_repr.<locals>.<lambda> at 0x7fffb27d0940>. Debug line information may be inaccurate.
  return dictobject._as_meminfo(dictobject.new_dict(keyty, valty,
/home/dyuman/miniconda3/envs/pyreason-dev/lib/python3.9/site-packages/numba/typed/typeddict.py:23: NumbaDebugInfoWarning: Could not find source for function: <function unicode_str.<locals>.<lambda> at 0x7fffb2bb1ee0>. Debug line information may be inaccurate.
  return dictobject._as_meminfo(dictobject.new_dict(keyty, valty,
/home/dyuman/miniconda3/envs/pyreason-dev/lib/python3.9/site-packages/pyreason/scripts/numba_wrapper/numba_types/interval_type.py:145: NumbaDebugInfoWarning: Could not find source for function: <function ctor.<locals>.impl at 0x7fffb2534d30>. Debug line information may be inaccurate.
  return Interval(np.float64(lower), np.float64(upper), static, np.float64(lower), np.float64(upper))
Filtering rules based on queries
Timestep: 0
Timestep: 1

Converged at time: 1
Fixed Point iterations: 2
**Total samples:** 4766 (99.7% non-Numba samples, 0.3% bad samples)

What version gdb do you have installed? (gdb --version) You may have hit #12

My guess is this will be fixed by release 0.3.0, please reopen if not.


Not working with reanimated v3

hello, there is a bug with reanimated 3.

project detail:
"react": "18.2.0",
"react-native": "0.71.2",
"react-native-reanimated": "^3.0.2",
"react-native-reanimated-player": "^2.3.0",

hey @itsnyx , yeah, it's does not supprot Reanimated v3 yet, let me find some time to add support for it!

@alantoa thanks for the response.

Hi @alantoa, Our project requires to use Share Elements. So is there a workaround for using reanimated 3? Thank you so much


Update Gridster.js

I encountered a problem with long browser rendering times due to an deprecated version of Gridster.js.
The particular fix is documented in https://github.com/Freeboard/freeboard/issues/112
We from flaregames GmbH and I believe everyone else using your great tool would really love you to fix that issue :)

Closing this as duplicate of #112


Added Recommended Language/Framework

Added Suggested Language, library and implementation Example for Video Subtitle Generator.

Thanks for submitting the PR, there are a few conflicts with this branch. They will be resolved and the PR merged soon.