fatal error: 'Flutter/Flutter.h' file not found

Failed to build iOS app
Error output from Xcode build:
↳
    --- xcodebuild: WARNING: Using the first of multiple matching destinations:
    { platform:iOS Simulator, id:dvtdevice-DVTiOSDeviceSimulatorPlaceholder-iphonesimulator:placeholder, name:Any iOS Simulator Device }
    { platform:iOS Simulator, id:AA0EE6D2-4E24-48C6-B9D6-4F2598B68E4E, OS:15.0, name:iPad (9th generation) }
    { platform:iOS Simulator, id:765C02E6-837E-4443-9073-722162C490DC, OS:15.0, name:iPad Air (4th generation) }
    { platform:iOS Simulator, id:30429B61-93BC-4497-B556-3639373A10D0, OS:15.0, name:iPad Pro (9.7-inch) }
    { platform:iOS Simulator, id:57217E13-F700-4673-9ABF-1866BAE1E435, OS:15.0, name:iPad Pro (11-inch) (3rd generation) }
    { platform:iOS Simulator, id:A85DD0A6-EA0F-480C-9A6F-07966F4FE66B, OS:15.0, name:iPad Pro (12.9-inch) (5th generation) }
    { platform:iOS Simulator, id:1D568B75-852B-42BE-8178-C39E6C515C41, OS:15.0, name:iPad mini (6th generation) }
    { platform:iOS Simulator, id:347466A9-6BA4-4674-94B6-BCB3ACB11F00, OS:15.0, name:iPhone 8 }
    { platform:iOS Simulator, id:F74B444A-2838-4920-91DB-83893719250E, OS:15.0, name:iPhone 8 Plus }
    { platform:iOS Simulator, id:2D4AF847-04A7-463C-A46C-D5D1E200CFDC, OS:15.0, name:iPhone 11 }
    { platform:iOS Simulator, id:BCD3D3BD-6485-4575-AA35-BF9ADEEBB4BD, OS:15.0, name:iPhone 11 Pro }
    { platform:iOS Simulator, id:06DE013F-BF48-4857-B952-BFC2AA1BD304, OS:15.0, name:iPhone 11 Pro Max }
    { platform:iOS Simulator, id:8A06D628-6132-4558-BB65-5598FFAC98DC, OS:15.0, name:iPhone 12 }
    { platform:iOS Simulator, id:885B1C8A-0497-4D95-8A87-447E40AB9238, OS:15.0, name:iPhone 12 Pro }
    { platform:iOS Simulator, id:FF519331-8490-4219-92D0-ED9A08F11976, OS:15.0, name:iPhone 12 Pro Max }
    { platform:iOS Simulator, id:51671583-ED36-4330-839B-401BA09B3996, OS:15.0, name:iPhone 12 mini }
    { platform:iOS Simulator, id:950FC388-6567-40BD-AD31-6CC5A334AC97, OS:15.0, name:iPhone 13 }
    { platform:iOS Simulator, id:562728AB-E0CA-4675-BF75-787299ECE105, OS:15.0, name:iPhone 13 Pro }
    { platform:iOS Simulator, id:CBB3D2FF-97DF-4328-8AD0-7350F83989D1, OS:15.0, name:iPhone 13 Pro Max }
    { platform:iOS Simulator, id:D99FD6E3-C6DC-4F16-8092-83EA0216367F, OS:15.0, name:iPhone 13 mini }
    { platform:iOS Simulator, id:2A06C9C4-9D8C-4C9B-9620-12265131A747, OS:15.0, name:iPhone SE (2nd generation) }
    { platform:iOS Simulator, id:EA2B1A03-78F8-42B2-9818-41FE3F1E833A, OS:15.0, name:iPod touch (7th generation) }
    { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
    ** BUILD FAILED **
Xcode's output:
↳
    /Users/lukeirvin/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/wakelock-0.5.2/ios/Classes/messages.m:4:9: fatal error: 'Flutter/Flutter.h' file not found
    #import <Flutter/Flutter.h>
            ^~~~~~~~~~~~~~~~~~~
    1 error generated.
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in parallel

Running Xcode 13, flutter 2.5.1 on stable, and cocoa pods 1.10.1
Prior to this, I was getting complaints that some pods were on 8.0 and needed to be on 9.0+ so I updated my Podfile to have this:
post_install do |installer|
  installer.pods_project.targets.each do |target|
   target.build_configurations.each do |config|
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '9.0'
   end
  end
 end

I have tried re-installing Flutter, re-cloning my app, deleting the ios folder, deleting the Flutter folder, cleaning, pod install... anything I have found online. But still getting the above every time. Just on iOS though.
Any guidance would be greatly appreciated.

After updating my Flutter to 2.5.1, it stopped to working on iOS.

Prior to this, I was getting complaints that some pods were on 8.0 and needed to be on 9.0+ so I updated my Podfile to have this:

And I'm getting the same error from pods on 8.0 and 9.0.
[...] warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'Reachability' from project 'Pods')
[...] warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'AppAuth' from project 'Pods')
[...] The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'GoogleSignIn' from project 'Pods')

After updating my Flutter to 2.5.1, it stopped to working on iOS.

Prior to this, I was getting complaints that some pods were on 8.0 and needed to be on 9.0+ so I updated my Podfile to have this:

And I'm getting the same error from pods on 8.0 and 9.0.
[...] warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'Reachability' from project 'Pods')
[...] warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'AppAuth' from project 'Pods')
[...] The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 8.0, but the range of supported deployment target versions is 9.0 to 15.0.99. (in target 'GoogleSignIn' from project 'Pods')

Correct. I'm getting the same thing. Any suggestions? I've tried everything I've found via Stackoverflow but it's been no luck. A co-worker, though, isn't having these issues and has the same versions on his machine. So this one is very confusing.

I'm having a similar issue and made a post as well. Just like @lukeirvin I've tried basically everything and nothing seems to fix the issue. It was a bad idea do try and update everything at once.
That said, the 'IPHONEOS_DEPLOYMENT_TARGET' error was fixed for me by removing the deployment target in the pod file:
config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET

I'm having a similar issue and made a post as well. Just like @lukeirvin I've tried basically everything and nothing seems to fix the issue. It was a bad idea to try and update everything at once.
That said, the 'IPHONEOS_DEPLOYMENT_TARGET' error was fixed for me by removing the deployment target in the pod file: config.build_settings.delete 'IPHONEOS_DEPLOYMENT_TARGET
Would be great to get some help with the 'Flutter/Flutter.h not found' though. It's been frustrating trying to get it to work

Tried the delete approach, and yes, the same thing on my end. It resolves the Pod 8.0 / needs to be 9.0... issue, but the other still exists.

@lukeirvin  Do you use M1 Mac ?

Steps which helped me:

update flutter
create a new project outside of the project you are working right now
delete ios folder in the project with error fatal error: 'Flutter/Flutter.h' file not found
copy ios folder from the new project
re set-up firebase if you are using it
run the project

Hi @lukeirvin
Can you please restore podfile & try the following commands and
post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

1. pod deintegrate
2. rm ios/Flutter/Flutter.podspec
3. flutter clean
4. flutter pub get
5. pod install
6. flutter run

@lukeirvin Do you use M1 Mac ?

No, I do not use a M1 Mac

Hi @lukeirvin Can you please restore podfile & try the following commands and
post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

1. pod deintegrate
2. rm ios/Flutter/Flutter.podspec
3. flutter clean
4. flutter pub get
5. pod install
6. flutter run

So, flutter run will not work as I have dev and prod environments. So just to verify, try this but on the last step, trigger the proper environment file with the proper flavor?

Steps which helped me:

update flutter
create a new project outside of the project you are working right now
delete ios folder in the project with error fatal error: 'Flutter/Flutter.h' file not found
copy ios folder from the new project
re set-up firebase if you are using it
run the project

I'm trying this but right now I'm getting this error:
Exception: The Xcode project does not define custom schemes. You cannot use the --flavor option.

I reset everything with the post above & I am getting the same set of errors...

@lukeirvin does you use google_sign_in framework? If yes, try updating to version 5.1.1.
Flutter 2.5.0 deprecated iOS 8.0 version, and google_sign_in used this version. In 5.1.1 they added this to changelog:
Update minimum Flutter SDK to 2.5 and iOS deployment target to 9.0.
I updated mine, ran flutter clean and worked again.

@lukeirvin
if the issue is specific to your project, please try the command with your flavor.

I ended up reformatting my Mac yesterday.
So, once I had everything installed again I cloned my project & still received the same issue, the core one due to updating the version to 9.0+.
I then updated google_sign_in to 5.1.1 & the project worked. I reverted that change & I could still load the project with all the base settings.
The first thing I did today was trying to load the project but it failed again.
So, I updated google_sign_in to 5.1.1 & now I can run the project.
But, I can only run it via simulator for iOS. If I try to build to my iPhone I get the update issue again.

Hi @lukeirvin
Can you please provide a flutter run -v <your_flavor>  > run.log connected to a physical device?

Hi, try to remove build folder and run
flutter clean
flutter pub get
pod install
flutter run

I have spent a week trying to resolve this issue, I tried all methods possible, still always one of pods will fail with missing Flutter/Flutter.h. The only similarity I see is that pods for those plugins are installed with initial version 0.0.1. Please help !
    { platform:iOS, id:dvtdevice-DVTiPhonePlaceholder-iphoneos:placeholder, name:Any iOS Device }
    ** BUILD FAILED **

Xcode's output:
↳
    In file included from
    /Users/michal/Development/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-6.0.12/ios/Classes/FLTURLLauncherPlugin.m:7:
    /Users/michal/Development/flutter/.pub-cache/hosted/pub.dartlang.org/url_launcher-6.0.12/ios/Classes/FLTURLLauncherPlugin.h:5:9: fatal error:
    'Flutter/Flutter.h' file not found
    #import <Flutter/Flutter.h>
            ^~~~~~~~~~~~~~~~~~~
    1 error generated.
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in parallel

Could not build the application for the simulator.

At diffrent times failing pods:
I```
nstalling path_provider (0.0.1)
Installing shared_preferences (0.0.1)
Installing syncfusion_flutter_pdfviewer (0.0.1)
Installing tau_core (8.3.12)
Installing url_launcher (0.0.1)
Installing video_player (0.0.1)

I tried:
1. Remove ios folder 1 flutter create . 1 and copy Runner back etc...
2. Remove build..
3. Remove Flutter\Flutter....
4. All combinations of pod install/upgrade after clean ...

Nothing works. My project suddenly top to compile for iOS.

/Users/lukeirvin/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/wakelock-0.5.2/ios/Classes/messages.m:4:9: fatal error: 'Flutter/Flutter.h' file not found
#import <Flutter/Flutter.h>

@lukeirvin please also try upgrading the wakelock plugin, it seems to be the cause of the build failure,  the latest version is wakelock: ^0.5.6.


GridOut object has no attribute X

It seems like GridFS.get and .put don't work at all...
from twisted.internet import reactor
import txmongo
from txmongo.gridfs import GridFS

d = txmongo.MongoConnectionPool()

def gotDB(db):
    files = GridFS(db.fs, collection='foo')
    print files
    return files

def gotFiles(files):
    obj_id = files.put('some contents', filename='foo', content_type='image/png')
    print 'saved', repr(obj_id)
    obj = files.get(str(obj_id))
    print 'got', repr(obj)
    print dir(obj)
    print obj.read()
    print obj.name
    print obj.content_type

d.addCallback(gotDB)
d.addCallback(gotFiles)

reactor.run()

gives me this:
<txmongo._gridfs.GridFS object at 0x12885d0>
saved ObjectId('4fe84a9bf648c2b4df000001')
got 4fe84a9bf648c2b4df000001
['_GridOut__buffer', '_GridOut__chunks', '_GridOut__current_chunk', '_GridOut__position', '__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattr__', '__getattribute__', '__hash__', '__init__', '__iter__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_file', '_id', 'aliases', 'chunk_size', 'close', 'content_type', 'length', 'md5', 'metadata', 'name', 'read', 'seek', 'tell', 'upload_date']
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
  File "/Volumes/FatMan/home/matt/venvs/things/lib/python2.6/site-packages/Twisted-12.1.0-py2.6-macosx-10.3-fat.egg/twisted/internet/defer.py", line 464, in _startRunCallbacks
    self._runCallbacks()
  File "/Volumes/FatMan/home/matt/venvs/things/lib/python2.6/site-packages/Twisted-12.1.0-py2.6-macosx-10.3-fat.egg/twisted/internet/defer.py", line 551, in _runCallbacks
    current.result = callback(current.result, *args, **kw)
  File "badmongo.py", line 19, in gotFiles
    print obj.read()
  File "/Volumes/FatMan/home/matt/venvs/things/lib/python2.6/site-packages/Twisted-12.1.0-py2.6-macosx-10.3-fat.egg/twisted/internet/defer.py", line 1187, in unwindGenerator
    return _inlineCallbacks(None, gen, Deferred())
--- <exception caught here> ---
  File "/Volumes/FatMan/home/matt/venvs/things/lib/python2.6/site-packages/Twisted-12.1.0-py2.6-macosx-10.3-fat.egg/twisted/internet/defer.py", line 1045, in _inlineCallbacks
    result = g.send(result)
  File "build/bdist.macosx-10.3-fat/egg/txmongo/_gridfs/grid_file.py", line 345, in read

  File "build/bdist.macosx-10.3-fat/egg/txmongo/_gridfs/grid_file.py", line 331, in __getattr__

exceptions.AttributeError: GridOut object has no attribute 'length'
<Deferred at 0x128aee0 current result: <twisted.python.failure.Failure <type 'exceptions.AttributeError'>>>

I think it's because GridFS.put returns grid_file._id, and GridFS.get takes a file_id, but uses that id as if it were a document in this line:
return GridOut(self.__collection, file_id)

@iffy You still interested in making that patch? :)

@psi29a Probably not :(  We ended up not using Mongo, so it would be far afield of what I'm doing now.

GridFS.put() seems to be working now. May we close this issue?

I think we can close this, if someone tests and isn't happy... they can post here and we can re-open it.


[ETL-447] Provide access to pranav

Allow Pranav to access the ingestion bucket

The build is failing because you forked the repo. (You'll want to create a branch in the main repo in the future). It's fine otherwise.


Use symfony/console for bin/codacycoverage

I can help you to rewrite ugly bin/codacycoverage by using symfony/console dependcies (this add requirements in composer.json)
This will be like this:
#!/usr/bin/env php
<?php

require 'vendor/autoload.php';

$app = new \Codacy\Coverage\Application();
$app->run();

And split clover and phpunit by dedicated \Codacy\Coverage\Command classes.
I can do this work, if you wanted.

Sounds good. Would be nice if codacycoverage could be started interactively then. But the current behaviour (codacycoverage clover or codacycoverage clover build/cover/clover.xml) should still be possible. If you want to do this, go ahead. Can you make it a pull request and incorporate all your other pull requests?

Good. I'll do it tomorrow.


Replace exec_program with execute_process

A replacement PR for #2744

It looks like it was introduced in version 3.0, so we should be good.


MobilenetV2-ssd is failed!

onverted to TensorRT: Fill, Merge, Switch, Range, ConcatV2, ZerosLike, Identity, NonMaxSuppressionV3, Minimum, StridedSlice, Shape, Split, Where, Exp, ExpandDims, Unpack, GatherV2, NoOp, TopKV2, Cast, Placeholder, Mul, Pack, Reshape, ResizeBilinear, Squeeze, Add, Greater, Const, Sub, Transpose, Slice, (For more information see https://docs.nvidia.com/deeplearning/dgx/integrate-tf-trt/index.html#support-ops).
2019-03-29 13:17:01.262911: I tensorflow/contrib/tensorrt/convert/convert_graph.cc:928] Number of TensorRT candidate segments: 1
[1]    27275 killed     python3 camera_tf_trt.py --image --filename  --model ssd_mobilenet_v2_coco

I'm having the exact same problem when running that script on the Jetson Nano.

Are you getting out of memory? That's the problem I've been having. Does anyone know if Tensorrt is device agnostic? If so we could try the tensorrt optimization on a desktop with more memory and transfer the model to the nano.

You should modify the default parameters on the optimize function.
AFAIK the optimization must be done in the device you are going to use for inference.

Hi All,
I was able to optimize on Jetson Nano with 4GB of swap enabled using the released TensorFlow 1.13
You can permanently add 4GB of swap with the following commands
sudo fallocate -l 4G /var/swapfile
sudo chmod 600 /var/swapfile
sudo mkswap /var/swapfile
sudo swapon /var/swapfile
sudo bash -c 'echo "/var/swapfile swap swap defaults 0 0" >> /etc/fstab'

Please let me know if you run into any issues.
Thanks!
John


Cloud parameter does not work

Describe the bug
Cloud threshold settings  do not work properly
To Reproduce
Steps to reproduce the behavior:
We get
For 90 % setting https://github.com/swisstopo/topo-satromo/blob/46086d429040a7cbb82ba4f34f0ea148c8aa18bf/step0_processors/step0_processor_s2_sr.py#L374
We get 59.3% "percentMasked" (https://sys-data.int.bgdi.ch/ch.swisstopo.swisseo_s2-sr_v100/2024-02-23t103031/ch.swisstopo.swisseo_s2-sr_v100_mosaic_2024-02-23t103031_metadata.json)

This
„Cutting asset create for projects/satromo-int/assets/COL_S2_SR_HARMONIZED_SWISS / 2024-02-23
Reason: cloudy
Asset not yet available for date 2024-02-23“
Image is actually pretty cloudfree
this pretty cloudfree scene

Expected behavior
Scene is recognized as not cloudy: Threshold for % cloudiness does take the "percentMasked" value into account.
Screenshots
If applicable, add screenshots to help explain your problem.
OS, python version
Additional context

when we we switch to "20" in S2_sr = S2_sr.filter(ee.Filter.gte('percentData', 10)) in https://github.com/swisstopo/topo-satromo/blob/46086d429040a7cbb82ba4f34f0ea148c8aa18bf/step0_processors/step0_processor_s2_sr.py#L374
Then the scene is not cloudy

After an analysis, i also find that percent of clear data on the scene is 40.7, which is completely reasonable.
There is no problem here for me.

It seems that not all S2 tiles of the orbit were available in GEE at the time of generation.  There was cloudiness in the available tiles.
To overcome this, we will introduce a delayed processing and a  check if the orbit is complete https://github.com/swisstopo/topo-satromo/issues/61.
What would be good in this case to see the actual amount of pixel  to extent https://github.com/swisstopo/topo-satromo/blob/af33a72b154535fe4ec8b7ca05288adb0e5398ea/step0_processors/step0_processor_s2_sr.py#L375
with something in this direction
# Calculate the total number of pixels in the original collection
total_pixels_original = S2_sr.reduce(ee.Reducer.sum()).select([0], ['total_pixels'])

# Calculate the total number of non-cloudy pixels in the original collection
non_cloudy_pixels_original = S2_sr.map(lambda img: img.updateMask(img.select('QA60').eq(0))).reduce(ee.Reducer.sum()).select([0], ['non_cloudy_pixels'])

# Calculate the percentage of cloud-free pixels
percentage_cloud_free_original = ee.Number(non_cloudy_pixels_original).divide(total_pixels_original).multiply(100).getInfo()

print("Percentage of cloud-free pixels in the original images:", percentage_cloud_free_original)

But I don't get the total number of non-cloudy pixels in the original collection --- @gilliM any ideas for a code snippet here?


Read WebDriver paths from env at highest priority

Make sure these boxes are checked! 📦✅

[ x] You have the latest version of rustfmt installed

$ rustup component add rustfmt

[ x] You ran cargo fmt on the code base before submitting
[ x] You reference which issue is being closed in the PR text

✨✨ 😄 Thanks so much for contributing to wasm-pack! 😄 ✨✨
This closes #1126. A separate PR will be submitted for wasm-bindgen to update the docs.

Thank you for this contribution! Your branch solves my use case

The failing test seems to be failing in rustwasm:master and unrelated to this PR.


Binstar build for prepackaged binaries

http://docs.binstar.org/draft/examples.html#SubmitYourFirstBuild

Done for win64: https://binstar.org/kwikteam/klustakwik2


Transition issue at loading with chrome

Hi, just spotted a bug with bootstrap 4 alpha 6 and chrome only. The bug does not happen on both of firefox and IE. I actually tested on chromium (v55) for linux and chrome for windows (v55).
What is the bug?
When loading a page that contains both of a button and an input, and that does not contain javascript, the button will appear with a transition (size, backgroun color and color have a transition from initial state to the bootstrap style).
I didn't test it much, I might be wrong on the exact conditions for the bug to happen
I could not provide a fiddle because fiddlejs injects some codes that break the conditions.
Here are 3 sample to reproduce and fixe the bug:
Case 1: button alone [WONT have the issue]
<!DOCTYPE html>
<html lang="fr">
	<head>
	    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0-alpha.6/css/bootstrap.min.css">
	</head>
	<body>
		<button class="btn btn-primary" role="button" type="submit">Connexion</button>
	</body>
</html>

Case 2: we added an input on the page [WILL have the issue]
<!DOCTYPE html>
<html lang="fr">
	<head>
	    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0-alpha.6/css/bootstrap.min.css">
	</head>
	<body>
		<button class="btn btn-primary" role="button" type="submit">Connexion</button>
		<input type="text">
	</body>
</html>

Case 3: we added a script on the page [NO MORE issue]
<!DOCTYPE html>
<html lang="fr">
	<head>
	    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0-alpha.6/css/bootstrap.min.css">
	</head>
	<body>
		<button class="btn btn-primary" role="button" type="submit">Connexion</button>
		<input type="text">
                <script>
			var foo = "foo";
		</script>
	</body>
</html>

Please note that no matter the order  of the elments the bug will happen: the script might be at the beggining of the document or at the end, the button might be before the input or after or in parent elements, etc...
As I said that might be a bug with chrome itself that would show the DOM before it loads the CSS, I also opened an issue on the chromium side

This is confirmed as a bug in chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=693088

I reopen the issue because we have to add this issue to the browser bug page

Ok, but note that the condition to reproduce the bug are very special and this bug should be extremly rare!

I can confirm adding an empty script tag solves this issue for me

Ok, this is even weirder... If an input has a value, the issue shows up. If the input is empty it does not. Bizarre...

@danawoodman  as I said the bug is confirmed on chrome side

Looks like they're waiting for a reply from the submitter. Also, my point about input field contents seems relevant to the issue

What's the status on this one? Still need to add a bug to our docs?

@mdo
That's not fixed on chrome's side for the moment

https://bugs.chromium.org/p/chromium/issues/detail?id=709718

Currently, Chrome on Windows 10 is at Version 79.0.3945.117. The previously detailed chromium bug reported id=709718 has been closed out as of 4th December 2019 as deemed working. Is this now resolved and if so, close of issue here?

Closing this per @stealth-swift's comment


Prioritize DependencyObject over INPC for UNO

What kind of change does this PR introduce?
Bug fix
What is the current behavior?
When building an Observable to observe a property of an object, if it inherits for DependencyObject and implements INotifyPropertyChanged the observable will be built using the INotifyPropertyChanged.PropertyChanged event.
The issue is that on iOS and Android the UIElement implements the INotifyPropertyChanged but it never raise the event: https://github.com/unoplatform/uno/issues/1551.
What is the new behavior?
On UNO projects, if an object inherit from DependencyObject we will create a observable from the DependencyProperty if found and fallback to the INotifyPropertyChanged otherwise.
What might this PR break?
If a DependencyObject has a DependencyProperty which is bypassed by the object's property getter / setter, the resulting observable won't produce any value.
Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
The real issue is on the Uno side (https://github.com/unoplatform/uno/issues/1551) however it's safer / lighter to change the priority in ReactiveUI for now, and rollback this commit once the issue has been fixed in Uno.

Some minor code errors being detected there. I'd be happy to make this change for all platforms tbh so feel free to remove the ifdef and just make dependency props win

Here it is :)


Minor fixes for selection-udf. Adding test cases

Moved AggregationFunctionType to common. This is needed to know if the udf in the select clause is Aggregation or scalar udf.

Minor fixes

Added test case.

By default enableUDFInSelection is false and its turned on/off in testSelectionUDF method

Codecov Report

Merging #25 into develop will decrease coverage by 9.49%.
The diff coverage is 42.18%.

@@             Coverage Diff              @@
##             develop      #25     +/-   ##
============================================
- Coverage      64.95%   55.45%   -9.5%
  Complexity         4        4
============================================
  Files           1048     1049      +1
  Lines          54397    54420     +23
  Branches        7757     7761      +4
============================================
- Hits           35331    30180   -5151
- Misses         16500    21872   +5372
+ Partials        2566     2368    -198

Impacted Files
Coverage Δ
Complexity Δ

.../data/aggregator/PercentileEstValueAggregator.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

...y/aggregation/function/MaxAggregationFunction.java
91.89% <ø> (-8.11%)
0 <0> (ø)

...pinot/core/data/aggregator/MinValueAggregator.java
81.81% <ø> (ø)
0 <0> (ø)
:arrow_down:

.../function/DistinctCountHLLAggregationFunction.java
30.43% <ø> (ø)
0 <0> (ø)
:arrow_down:

...n/function/DistinctCountMVAggregationFunction.java
26.66% <ø> (ø)
0 <0> (ø)
:arrow_down:

...aggregation/function/AggregationFunctionUtils.java
87.17% <ø> (-2.57%)
0 <0> (ø)

...ion/function/DistinctCountAggregationFunction.java
38.53% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ot/core/startree/v2/store/StarTreeLoaderUtils.java
93.65% <ø> (ø)
0 <0> (ø)
:arrow_down:

...pinot/core/data/aggregator/AvgValueAggregator.java
100% <ø> (ø)
0 <0> (ø)
:arrow_down:

...t/core/data/aggregator/ValueAggregatorFactory.java
75% <ø> (ø)
0 <0> (ø)
:arrow_down:

... and 383 more

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 261638e...0fff75a. Read the comment docs.


Update Thread.swift

Correct typo on Windows.

@swift-ci please test and merge

@swift-ci please test and merge


Words with the letters "fi" appearing as just "i" in a post page.

Note: This is a bug in Google Fonts: https://github.com/google/fonts/issues/8 - Google are pushing a fix on Monday January 26th 2016.
This is a Casper bug being tracked here: https://github.com/TryGhost/Casper/issues/235
Original issue below

I noticed this bug while I was reading a blog post written by a friend of mine.  Words that contain the letters "f" and "i" in that order, such as "figure" and "horrific" are appearing without the "f".  That is, "figured" becomes "igured" and "horrific" becomes "horriic". Interestingly (perhaps unsurprisingly), the page actually does contain the letter "f", and the browser can find the words when searching the page for the correctly spelled versions.
You can see in this screenshot of my own blog post that the word "horrific" appears as "horriic" but searching the page for "fi" highlights part of the word.

For your reference

My friend's post: http://blog.jrmiller.co/what-ive-been-up-to-lately/
My own blog post: http://zsck.co/2016/01/01/onward-to-2016/

My friend was able to verify this behavior in Chrome on Debian 8.2 and I was able to observe it in both the latest Chrome and the latest Firefox on the latest version of OS X.
We've both found that changing the text's font-family using the Chrome Developer Tools to something like Ariel results in the letter "f" becoming visible, shown in the image below.

I've noticed this too. I believe there's something wrong with the Merriweather font. Anyone else out there that can confirm

This was discussed on Slack earlier this evening.

https://ghost.slack.com/archives/atrium/p1453511622000004

My posts are acting in exactly the same manner, using the standard Ghost font.
Strangely enough, my blog tagline doesn't act quite the same. It only eliminates the letter "f" if it starts a word and is immediately followed by "i" or "l".

https://bug-demonstration.herokuapp.com/final-bug-demonstration/

Changing the font-family from Merriweather to Open Sans for the body selector in screen.css does not exhibit the problem :
body {
    font-family: "Open Sans", serif;
}

Note the recent "improvement" of "Merriweather" mentioned here: https://www.google.com/fonts/specimen/Merriweather

I had the same weird problem, thank you all for figuring out what the problem is and where it comes from.
I applied @nmhuy's suggestion.

This is a bug in the merriweather font itself, which affects the Casper theme. The Merriweather team released an update to Google Fonts on Friday, which caused this.
If it is not going to be fixed tomorrow (Monday) we will push out a new release of Casper.

@ErisDS curious as to the "fix" you propose in Casper to deal with an issue in Merriweather ???

A different font.
On Jan 24, 2016 2:35 PM, "Robert W Boyer"<EMAIL_ADDRESS>wrote:

@ErisDS https://github.com/ErisDS curious as to the "fix" you propose
in Casper to deal with an issue in Merriweather ???
—
Reply to this email directly or view it on GitHub
https://github.com/TryGhost/Ghost/issues/6375#issuecomment-174298920.

https://github.com/google/fonts/issues/8 - Google are pushing a fix tomorrow. This is a Casper bug being tracked here: https://github.com/TryGhost/Casper/issues/235

The update to Merriweather was made in advance of the Firefox 44 launch on Tuesday that will mean the old files will just stop working.
The bug with fi/fl ligatures has a workaround - you can turn ligatures off with CSS to work around this until then:
-webkit-font-feature-settings: 'liga' 0, 'onum' 1, 'kern' 1;
-moz-font-feature-settings: 'liga' 0, 'onum' 1, 'kern' 1;
-o-font-feature-settings: 'liga' 0, 'onum' 1, 'kern' 1;
font-feature-settings: 'liga' 0, 'onum' 1, 'kern' 1;

The fix is now pushed all the way through the Fonts API


[WFLY-13295] activate REST-AT for REST endpoints on plain EJBs as well

https://issues.redhat.com/browse/WFLY-13295
Test and fix for REST-AT and plain EJB transactional annotations.
This fix required component upgrade of narayana to 5.10.5.Final

@mmusgrov could you please take a look and review?

@kabir this is a bug fix, could this be merged for 20.0.0.Final?


NaN non-determinism for intrinsics and libm functions

@bors r+

:pushpin: Commit 08e6b3061ed92584994f3f1dccdbba85b01839e5 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 08e6b3061ed92584994f3f1dccdbba85b01839e5 with merge 4503503f76d049d827942d108ca992bb70872197...

@bors r+

:pushpin: Commit 2d4f580226b191dff57020dcc3e9bdb8cf93b275 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 2d4f580226b191dff57020dcc3e9bdb8cf93b275 with merge d7ccde298a95787a1e445a40f739016d13a650d4...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing d7ccde298a95787a1e445a40f739016d13a650d4 to master...


Produce Junit XML format instead of .Junit

Hi There
First of all, thank you for creating this library.
The -j produces the junit report but in .junit format which is not compatible with Gitlab pipelines. Is there a way to produce Junit XML style report?

Are you using the latest latest source?
I am using xchtmlreport build from latest develop and it works with my gitlab pipeline.
Here is a part of my .gitlab-ci.yml
test-ios-ProjectName:
  stage: test
  script:
    - xcrun xcodebuild -version
    - XCODE_TEST_RESULTS=${CI_PROJECT_DIR}/xcodeTestResults.xcresult
    - xcrun xcodebuild -project ProjectName.xcodeproj/ -scheme SchemeName -destination "platform=iOS Simulator,name=iPhone 8,OS=latest" clean test -resultBundlePath $XCODE_TEST_RESULTS -enableCodeCoverage YES -quiet
  after_script:
    # Generate HTML test report (index.html) and JUNIt report (report.junit)
    - XCODE_TEST_RESULTS=${CI_PROJECT_DIR}/xcodeTestResults.xcresult
    - xchtmlreport -r $XCODE_TEST_RESULTS -j -i
    - mv ${XCODE_TEST_RESULTS}/report.junit ${CI_PROJECT_DIR}/report.junit
    - mv ${CI_PROJECT_DIR}/index.html ${CI_PROJECT_DIR}/index.html
    - cd ${CI_PROJECT_DIR}
    # Also generate a Zip file from the original xcresult bundle
    - zip -r -q -X xcodeTestResults.zip $(basename "$XCODE_TEST_RESULTS1") || true
  tags:
    - ios-xcode12
  only:
    refs:
      - merge_requests
  artifacts:
    paths:
      - index.html
      - xcodeTestResults.zip
    reports:
      junit: report.junit

Thanks @nacho4d
Turned out the issue is with Gitlab. There is open bug with Gitlab pipelines where gitlab throws parsing error for large junit files (bug link below), and that's exactly what I am encountering, and so for now I am eliminating some nodes using xmlstarlet in junit.report and that seems to resolved the issue.
Gitlab Bug: https://gitlab.com/gitlab-org/gitlab/-/issues/268035
Workaround to reduce size of junit report:
(xmlstarlet ed -d '/testsuites/testsuite/testcase/system-out' < ${CI_PROJECT_DIR}/TestResults.xcresult/report.junit) > final.xml

Oh! I wasn't aware of this issue in gitlab.
Great to know you found a way to work-around it! Thank you for closing the issue.


Shift-Insert?

It would be great if you could paste  the same way you can on LInux.

I'll take a look at adding that functionality when I get some time (likely tomorrow 2018-07-24 at the earliest). If you want to fork this project and tinker with it on your own, please feel free to do that as well. If you end up creating the key combination yourself you can do a merge request back in and I'd be happy to accept it.


OpenGL编译的bug

谢谢作者贡献的论文与工作，在执行ray caching那一步的时候，我这里有一个编译报错，然后找了一下解决方法，，还是没有具体解决，nvdiffrast document（https://nvlabs.github.io/nvdiffrast/#rasterizing-with-cuda-vs-opengl-new）有提到说：
1.Since version 0.3.0, nvdiffrast on PyTorch supports executing the rasterization operation using either CUDA or OpenGL. Earlier versions and the Tensorflow bindings support OpenGL only.
2.To run rasterization in CUDA, create a RasterizeCudaContext and supply it to the rasterize() operation. For OpenGL, use a RasterizeGLContext instead. Easy!
具体做法我应该怎么做呢

Hi @anvenle,
I think this issue is related to the compilation of nvdiffrac. And we have never seen this problem on our devices. Please check the existing issues at the official repo (https://github.com/NVlabs/nvdiffrast/issues) to see if there are any similar problems.


having issue i don't know why

got this issue today after updating.
earlier it was working fine.

Full error? Workflow? Update from how long ago?
Most likely just some of the changes in the node inputs, try remaking the sampler node.

That workflow runs fine for me, maybe you haven't updated the nodes, or the update has failed?

For me, I get same error, only thing that's new is I have installed sageattention and triton

What is the full error?

Full error.txt
Here I have attached full error.

It's indeed error with Triton and nothing to do with these nodes:

OK so removing triton should make things work? Any other suggestion to improve speed because I installed it expecting some speed boost.

OK so removing triton should make things work? Any other suggestion to improve speed because I installed it expecting some speed boost.

I just tested it myself in Windows and got it working, so it definitely can work. I can't really offer support in installing all that as it's many steps with lots of things that can go wrong, I can only confirm it is possible.
Other than that:

fp8 fast mode obviously if supported by your system
for image2vid, use less steps, it can work with surprisingly little, some samplers like SASolver perform better at low steps
if your VRAM allows, use PAB (just connect PAB config node to model loader)
don't use GGUF unless you have to (VRAM, it's slower
use smaller resolution, 5b fun version can do extremely small videos coherently that then could be upscaled by other means

For now, I have removed Triton and sageattention just to make things work. May be in near future will spend time investigate how to make it work easily.
Thanks for helping out.

After connecting to the person who build wheels for Triton I manage to make it work, however fp8 gives error-
torch._scaled_mm is only supported on CUDA devices with compute capability >= 9.0 or 8.9, or ROCm MI300+

Also I am trying your suggestion, so if in example we got workflow with those things it will very helpful.
@jepjoo  At home I got RTX 4070 and here fp8 working fine, thanks for the reply.

After connecting to the person who build wheels for Triton I manage to make it work, however fp8 gives error- torch._scaled_mm is only supported on CUDA devices with compute capability >= 9.0 or 8.9, or ROCm MI300+
Just reopen to see if its possible to make fp8 also work.

I think that basically means Hopper and Ada Lovelace (RTX 40) only. You said you have 3060, I don't think it's supported for native fp8.
btw @kijai can you confirm whether Sageattention is also working on Windows? I have it + Triton installed but not sure how to tell whether it is being utilized or not.
Getting somewhere around 4.2s/it with CogVideo I2V 5B on a 4090, fp8 "fastmode" selected.

Yeah sageattn works if you can get Triton to work, that speed would suggest it's working, it's not quite as fast as on Linux, but still way faster than without.

Also I am trying your suggestion, so if in example we got workflow with those things it will very helpful. @jepjoo At home I got RTX 4070 and here fp8 working fine, thanks for the reply.

Fp8 itself will work on 4070, but fp8_fastmode will not, that requires 4090 or newer GPU.


Possible security enhancement suggestion: ask for GA code after wrong password or login

Only after entering a wrong GA code, should you be told that either login, password, or GA code is wrong.

That can be done with mere PAM configuration already.


TPA3004D2PHPR

create symbol and footprint

symbol name should be TPA3004D2.
PHP is the package and R is for reel

Footprint will be Package_QFP:TQFP-48-1EP_7x7mm_P0.5mm_EP5x5mm_ThermalVias from the default library


Can not start lxd due to non existent storage pool

Required information

Distribution: Ubuntu
Distribution version: 18.04
The output of "lxc info" or if that fails:

Kernel version: 4.15.0-23-generi
LXC version: 3.0.1
LXD version: 3.0.1
Storage backend in use:zfs

Issue description
Can not start lxd due to non existent storage pool (juju-zfs).  I had started a conjure-up install (kubernetes), that failed, and I removed all relative containers and pools.  I also have existing storage-pools and containers sitting on plain lxc/lxd.  Where the problem has begun, my computer lost power and now when booting up the local.db must still have reference to juju-zfs zpool.
I dont think this is a realistically reproducible scenario. I just need help cleaning my db to remove the juju-zfs reference   I am familiar with sqlite3 or sqlitebrowser, but with the introduction to raft/dqlite...

Easiest way out of this is usually to just create a temporary pool, that'll unstick LXD, then you can delete the various objects through the LXD CLI and then destroy your pool.
truncate -s 1GB /tmp/zfs.img
zpool create juju-zfs /tmp/zfs.img

Then start LXD (systemctl start lxd.service).
Delete any containers with lxc delete, then look for any volume left in the pool with lxc storage volume list juju-zfs, for any of those, delete them with lxc storage volume delete, once all clean, you can do lxc storage delete juju-zfs.
After that LXD cleanup, remove the temporary pool with:
zpool destroy juju-zfs
rm /tmp/zfs.img

Closing as there's no actual bug to fix in LXD here. It's intentional that LXD will refuse to start if it can't find storage pools as those occasionally require manual admin intervention to appear and starting things without the pool being mounted may caused data corruption.
Let us know if the instruction above aren't sufficient.

Thank you, that worked, I appreciate it.


The number of bugs for the first fix item is incorrect in Release Notes Fixes part

Storage Explorer Version: 1.12.0
Build: 20200113.2
Branch: rel/1.12.0
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer -> Open Release Notes.
Check the description of the first fix in Fixes part.

Expect Experience:
The number of bugs is described correctly.
Actual Experience:
The number of bugs is described incorrectly.

Won't fix. There is 1 bug with 2 relevant GitHub issues.


Filter Dropdown Only Actives for Events

A new filtering function that shows only open events has been added.


Question about linear_kalman_filter

Hi, I have some questions about your linear kalman filter.cpp.
In Mit Cheetah program, they let
$$
x = [{}^op_{com}, {}^ov_{com}, {}^op_i]^T
$$
where represents the position of COM, the velocity of COM and the position of foot in the world frame, respectively.  Therefore their c matrix is
 _C.block(0, 6, 12, 12) = T(-1) * Eigen::Matrix<T, 12, 12>::Identity();

But in your linear Kalman filter, your  c matrix is
c_.block(0, 6, 12, 12) = Eigen::Matrix<scalar_t, 12, 12>::Identity();

What's the difference between your filter and MIT's filter?  What variable does y represent in your program? Can you give me some advice, thanks！

It's a typo of mine, the reason why the program still working is I didn't use the foot position from the kalman filter in other places. I will fixed it in the latest commit.


Revert introduction of sourcePath for Javadoc options

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

@bot-gradle test RfR

OK, I've already triggered the following builds for you:

ReadyForRelease build

OK, I've already triggered a build for you.


intel_gpu_install.sh isn't executable after git clone

perhaps add chmod to copy-pasteable section of README?

or perhaps call out sh BSD-XFCE/intel_script.sh explicitly


Cannot see any error logs in pilot but getting errors in prometheus metrics

(This is used to report product bugs, please visit https://discuss.istio.io for questions on using Istio)
Bug description
Getting pilot_total_xds_internal_errors & pilot_rds_expired_nonce metric errors in prometheus but cannot find any error logs in pilot pods. So not sure how to resolve this error and avoid pilot_total_xds_internal_errors & pilot_rds_expired_nonce
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[x] User Experience
Expected behavior
If there are pilot_total_xds_internal_errors & pilot_rds_expired_nonce then we should see some error or warning logs in pilot pods
Steps to reproduce the bug
Installed Istio with following values.yaml
global:
  tag: 1.1.4
  logging:
    level: "default:warn"

  proxy:
    resources:
      requests:
        cpu: 100m
        memory: 128Mi
      limits:
        cpu: 500m
        memory: 512Mi

    accessLogFile: ""
    accessLogEncoding: JSON
    enableTracing: false

    # this means that auto-injection will be opt-in.
    # For autoinjection both namespace label & pod annotation will be required
    # https://istio.io/help/ops/setup/injection/
    autoInject: disabled

  # TODO: Change this to true when start supporting Istio CRDs
  useMCP: false

pilot:
  enabled: true
  autoscaleMin: 3
  env:
    GODEBUG: gctrace=0
    PILOT_ENABLE_FALLTHROUGH_ROUTE: 1

mixer:
  enabled: false
  env:
    GODEBUG: gctrace=0
  policy:
    enabled: false
  telemetry:
    enabled: false
    loadshedding:
      mode: logonly
      latencyThreshold: 200ms

sidecarInjectorWebhook:
  enabled: true
  replicaCount: 3

galley:
  enabled: false

# Used as secondary monitoring tool for istio components
prometheus:
  enabled: false

# Used as secondary monitoring tool for istio components
grafana:
  enabled: false

gateways:
  enabled: false

security:
  enabled: true

nodeagent:
  enabled: false

servicegraph:
  enabled: false

tracing:
  enabled: false

kiali:
  enabled: false

istio_cni:
  enabled: false

istiocoredns:
  enabled: false

Version (include the output of istioctl version --remote and kubectl version)
client version: version.BuildInfo{Version:"1.1.7", GitRevision:"eec7a74473deee98cad0a996f41a32a47dd453c2-dirty", User:"brew", Host:"Mojave.local", GolangVersion:"go1.12.5", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.7"}
citadel version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
pilot version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
pilot version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
pilot version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
sidecar-injector version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
sidecar-injector version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}
sidecar-injector version: version.BuildInfo{Version:"1.1.4", GitRevision:"bc7465793cbff4c4189639b3f404e21c517cbdc6-dirty", User:"root", Host:"471e568b-66d7-11e9-a0d5-0a580a2c0304", GolangVersion:"go1.10.4", DockerHub:"docker.io/istio", BuildStatus:"Modified", GitTag:"1.1.3-20-gbc74657"}

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T18:55:03Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.7-gke.17", GitCommit:"b1adfec15b29a53b3dcf4af600952861b5819ede", GitTreeState:"clean", BuildDate:"2019-05-01T18:59:13Z", GoVersion:"go1.10.8b4", Compiler:"gc", Platform:"linux/amd64"}

How was Istio installed?
Using helm template
Environment where bug was observed (cloud vendor, OS, etc)
GKE
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

I checked both discovery container and istio-proxy container logs in pilot pods, but there are only info logs.
Another strange thing is getting pilot_total_xds_internal_errors  in only 1 pilot pod out of 3 pilot pods

There is only one place in the code where pilot_rds_expired_nonce is sent.  It is preceded by a message logged at Debug level.  Adding the area/networking because I believe we should log at Error level if we are sending error metrics to Prometheus.
Can you trying doing istioctl proxy-status and see if the proxies are becoming STALE?
If you have 3 Pilot pods it is possible that only one of the pods is talking to a sidecar that is rejecting the RDS being sent by Envoy.  There have been recent fixes in this area (search closed issues for 'RDS' and 'Stale').  If not we need to understand why Pilot-generated RDS (route) updates are failing to be accepted by Envoy.

Tried istioctl proxy-status and all the proxies are synced
NAME                                                      CDS        LDS        EDS               RDS        PILOT                            VERSION
app-server-757fc74c7f-2px8r        SYNCED     SYNCED     SYNCED (100%)     SYNCED     istio-pilot-5688c45f78-4v9xq     1.1.3
app-server-757fc74c7f-fskws        SYNCED     SYNCED     SYNCED (100%)     SYNCED     istio-pilot-5688c45f78-4v9xq     1.1.3
app-server-istio-86f6755b4b-5rfpd     SYNCED     SYNCED     SYNCED (100%)     SYNCED     istio-pilot-5688c45f78-pfndp     1.1.3
app-server-istio-86f6755b4b-689l7     SYNCED     SYNCED     SYNCED (100%)     SYNCED     istio-pilot-5688c45f78-4v9xq     1.1.3
app-server-istio-86f6755b4b-hsbff     SYNCED     SYNCED     SYNCED (100%)     SYNCED     istio-pilot-5688c45f78-4v9xq     1.1.3

Only 2 pilot pods are talking to sidecars of application pods.
pilot_rds_expired_nonce  is coming from  istio-pilot-5688c45f78-pfndp pilot pod.
pilot_total_xds_internal_errors  is coming istio-pilot-5688c45f78-qrwn7 pilot pod which is not talking to any application sidecar.
Also i tried removing sidecars from all application pods by disabling istio on those pods... but still getting the pilot_total_xds_internal_errors  errors

There was mistake in understanding the metrics, pilot_total_xds_internal_errors & pilot_rds_expired_nonce are both counter metrics. Once they get increase , they will never go down until unless we restart the pilot pods which were reporting this metrics.
What happened:
I got pilot_total_xds_internal_errors & pilot_rds_expired_nonce errors at x time which increased the count and i pretended that there are continuous errors but they weren't
I checked when these errors were increased first time, at that time i was able to see logs in pilot, so this issue can be closed


FIX: do not explicitly import pydata theme

its already imported by sphinx.

Can we maybe tag a release with this? I keep seeing this 404 in the console log.

@QuLogic, yes we should talk about how to tag this and mpl-brochure-site.  I am not sure how doc builds work once a release has been made.
The released version of this probably needs to track the MPL doc release because the top menubar navigation is hard-coded here.  So dependent sites should use the stable version of the site, not the dev version.  This adds to the release burden because this needs to be checked and tagged at that point.  Then we shouldn't release again until the next docs release?

@QuLogic, yes we should talk about how to tag this and mpl-brochure-site. I am not sure how doc builds work once a release has been made.

The mpl-brochure-site is published from every commit on main, so we just need to push something there.

The released version of this probably needs to track the MPL doc release because the top menubar navigation is hard-coded here. So dependent sites should use the stable version of the site, not the dev version. This adds to the release burden because this needs to be checked and tagged at that point. Then we shouldn't release again until the next docs release?

Doesn't it all link to /stable? Why do we need to coordinate releases?

The mpl-brochure-site is published from every commit on main, so we just need to push something there.

OK, that seems fine...

The released version of this probably needs to track the MPL doc release because the top menubar navigation is hard-coded here. So dependent sites should use the stable version of the site, not the dev version. This adds to the release burden because this needs to be checked and tagged at that point. Then we shouldn't release again until the next docs release?

Doesn't it all link to /stable? Why do we need to coordinate releases?

The brochure site indeed always points to stable, as do the satelite sites.
If we use mpl_sphinx-theme  on the main site, it will use relative links.  So when it is built, matplotlib.org/3.5.0/docs/index.html  the tutorial link should point to  matplotlib.org/3.5.0/tutorials.  Which is all fine, if we never rebuild the docs.  However, lets say we decide to change the top-level nav and there is a link to 3.6.0/future-cool-thing and we rebuild the 3.5 docs, they will get that button and it will point to non-existent 3.5.0/future-cool-thing.  So if we ever want to rebuild the docs, we will need to install an old version of mpl-sphinx-theme to have the right nav - hence it probably is good to tag?

See https://github.com/matplotlib/mpl-sphinx-theme/blob/main/mpl_sphinx_theme/mpl_nav_bar.html for the if-statment here...

Ah, we don't need to tie releases together all the time then. We should pin the theme version in Matplotlib, and release this one when it gets new stuff, then bump the theme in Matplotlib main.

I think that would be fine.  But for sanity sake, maybe this should get the same version tags as Matplotlib so its easy to cross-correlate when the change went in?  i.e. we could stay on 3.5.0 until a change is made in 3.7.0 and then update the tag to 3.7.0 at that time?

Can you upload a new version now? We don't have parallel safeness, nor the fixed JS here.

@QuLogic moved to gitter for clarification!


Fix placement of template literals in arrow bodies

Closes #117.
If you are not going to squash it, please tell me so I can squash it :)

Thanks @kdy1! It looks good, but I think there might need to be some heuristic for deciding whether to newline or not. For example, prettier does this:
https://prettier.io/playground/#N4Igxg9gdgLgprEAuc0DOMAE8OYLyYAUAlPgHyYAGOMAllAObYAWtamEArljfU742xwMfISKiYGA-sLqNKAHShLIUXBBjM4AJ3xFSeCotizRMcxctXrN23fsPbSx5dPylK9Fg1btAJj0SciVjaWwXCMioyOdItwZjEAAaEAgABzp0ZFAAQ21tCAB3AAU8hDRkEByAG0KcgE8KlIAjbRywAGs4GABlNPa+ZBhtTjgUuABbZrgAExnZgBkcxk4chjgAMQhtCZzzQZQc7ghkkGYYCeqAdVYcfrA4HvLaOgA3F-rKsDQmkHo0HQwYptBi7ZAAMxqAJSACs0AAPABCbU63R6OQmcAW9DgEKhYxAcPhPT41TgAEVOBpcUhIdVoSB+toAdpKs0ctNqqc0tp6DArrQZppkAAOAAMKR5EABVzaaUqPOEOleuJSAEcqfBgekKoc0ABaKBwWazU7aOAa2jm4FrMG0-EpAETWhDEYEtCkimaml0hkwDkCoXMZB+FLDHK0ap8ADCEAmdpAwgArKdOACACoc3W+gmvUYASSg81gPTAvIyAEEiz0YPUyXj6XAAL5NoA
I'm not sure what that heuristic should be though. I'll look at this more later and merge it soon!

@dsherret I modified it a bit, but I didn't implement preserving of the original line when it starts with a newline character.
It's because I'm not sure if it's desirable and I'd like to ask if you want it.

@kdy1 thanks! It looks good. I will take a look at this in more detail and merge it soon.

Apologies for my delay. Thanks for this change, @kdy1!


 decoding?

How does this package manage decoding of checkbox values as type bool? When parsing forms myself, I've always had to create a utility function to parse checkbox values:
func ParseCheckbox(checkbox string) (bool, error) {
	if checkbox == "on" {
		return true, nil
	} else if checkbox == "off" || checkbox == "" { //Empty = unchecked
		return false, nil
	}

	return false, errors.New("Invalid checkbox value. Must be \"on\" or \"off\".")
}

Any light shed on this would be appreciated!

hey @danhardman
I completely get where you're coming from, I've had the same troubles where the value passed down is on or off and Go's strconv.ParseBool(...) doesn't handle those values.
so my parseBool, seen here, handles all of Go's standard values plus a few extra, but otherwise mimics the function exactly. If more values are required and those values make sense, I'd be happy to add more.
func parseBool(str string) (bool, error) {

	switch str {
	case "1", "t", "T", "true", "TRUE", "True", "on", "yes", "ok":
		return true, nil
	case "0", "f", "F", "false", "FALSE", "False", "off", "no":
		return false, nil
	}

	// strconv.NumError mimicing exactly the strconv.ParseBool(..) error and type
	// to ensure compatibility with std library and beyond.
	return false, &strconv.NumError{Func: "ParseBool", Num: str, Err: strconv.ErrSyntax}
}

That seems to work fine on my tests, thanks for the info!


[FEATURE] Terraform Input Device Support

Is your feature request related to a problem? Please describe.
The VNC console (with Windows at least) is very problematic without the 'USB Tablet' input option specified (under Advanced). So far as I can determine, this flag cannot currently be enabled in the VM definition using the latest version of the Harvester and the Harvester Terraform provider.
Describe the solution you'd like
Ideally, all of the options which can be specified in the UI (at least) should be specifiable from the Terraform resource definition. This item (USB Tablet interface) in particular is very important in our use case, because the Windows UI seems to be unusable from the Console without it.
Describe alternatives you've considered
The only alternative that we can see is manually enabling the option in the Harvester web UI after the VM is created. This requires a restart of the VM, which is less than ideal.
Additional context
I have done some initial research on what would be required to add this capability into the Harvester Terraform provider. Unfortunately, it appears that the required schema is not currently exposed by the 'Builder.VM' struct in Harvester.
[https://github.com/harvester/harvester/blob/9c3f8a635e371674dd9b2a9ff0c9b4bbafa07afe/pkg/builder/vm.go#L63]
Therefore, it appears the feature enhancement will require improvements to both Harvester and the Harvester Terraform provider. On the plus side, this capabilty appears to be cleanly/simply exposed by the KubeVirt API on which the Harvester Builder API depends.
[https://github.com/kubevirt/kubevirt/blob/main/staging/src/kubevirt.io/api/core/v1/schema.go#L512]
We are willing to help when possible with this, given some guidance, help with testing/validation, etc. However, our team has very limited Go experience.

Verified this feature has been implemented.

Test Information

Environment: qemu/KVM 2 nodes
Harvester Version: master-0f10441a-head
ui-source Option: Auto
Harvester Terraform Provider Version: master or >0.6.1

Verify Steps:

Install Harvester with any nodes
Setup Harvester Terraform Provider^1
Apply a VM with usb inputs (example snippet as below)
Login to dashboard, navigate to Virtual Machines page
The VM should be created and Enable Usb Tablet should be checked

resource "harvester_image" "ubuntu20" {
  name      = "ubuntu20"
  namespace = "harvester-public"

  display_name = "ubuntu-20.04-server-cloudimg-amd64.img"
  source_type  = "download"
  url          = "http://cloud-images.ubuntu.com/releases/focal/release/ubuntu-20.04-server-cloudimg-amd64.img"
}

resource "harvester_virtualmachine" "ubuntu20" {
  name                 = "ubuntu20"
  namespace            = "default"
  restart_after_update = true

  description = "test ubuntu20 raw image"
  tags = {
    ssh-user = "ubuntu"
  }

  cpu    = 2
  memory = "2Gi"

  efi         = true
  secure_boot = true

  run_strategy    = "RerunOnFailure"
  hostname        = "ubuntu20"
  reserved_memory = "100Mi"
  machine_type    = "q35"

  network_interface {
    name           = "nic-1"
    wait_for_lease = true
  }

  disk {
    name       = "rootdisk"
    type       = "disk"
    size       = "10Gi"
    bus        = "virtio"
    boot_order = 1

    image       = harvester_image.ubuntu20.id
    auto_delete = true
  }

  disk {
    name        = "emptydisk"
    type        = "disk"
    size        = "20Gi"
    bus         = "virtio"
    auto_delete = true
  }

  input {
   name         = "tablet"
   type         = "tablet"
   bus          = "usb"
}

  cloudinit {
    user_data    = <<-EOF
      #cloud-config
      password: 123456
      chpasswd:
        expire: false
      ssh_pwauth: true
      package_update: true
      packages:
        - qemu-guest-agent
      runcmd:
        - - systemctl
          - enable
          - '--now'
          - qemu-guest-agent
      EOF
    network_data = ""
  }
}


Update to ImGUI .Net 4.9.0

Add Controller to remove broken Veldrid.ImGui reference
I took the controller from the demo in the IMGui release and fixed it to allow fonts to be loaded properly.
Add a free font for the demo - From Google Fonts
Fix the Demo
Note I'm building this on Linux, you might need to make changes for windows

Thanks for this, I'd inlined the code from Veldrid.ImGui in some other projects but hadn't fixed up this one yet. I'll give the changes a test on Windows shortly.

It's working fine on Windows. I'll merge it through as is, then make a change to tidy things up and use the latest ImGui.NET package.


Whether there are options that only show the updateable version, and do not really perform the update.

Whether there are options that only show the updateable version, and do not really perform the update.
Because I found that executing the update would destroy my TOML file format.

If you don't want to rewrite, format or update the TOML file then this plugin isn't for you. You could just use the dependency versions plugin to get a report of available updates in stead.
#63 will make updates to make it easier to apply only the changes you want, but it will still format the TOML file in that case.

There is one use case where having a report is desired, just like in the gradle-versions-plugin, and in this use case, the gradle-versions-plugin is not sufficient to achieve that.
That is, when we have a module that publishes a versionCatalog to be consumed by other projects. In that case, we would still want to see the report of available updates, without modifying the file; and the ben-manes plugin is not going to work because that will only look at actual applied dependencies. In the case of a versionCatalog project, those aliases do not actually get applied to project.dependencies, so neither plugin is really suitable for that.
Also in this case, it's unlikely that we'll be publishing the gradle/libs.versions.toml file, because as a standalone module we may want that file to live in $rootDir/catalog-module/src/main/com.company.versions.toml. The file is intended for publishing only, and doesn't actually play a role in the project's own dependency resolution.
As it is now, I can see no way to get a report of available updates for the dependencies listed in this toml file, because it will only scan the gradle project's actual dependency configurations. If we aren't selecting anything from the toml file in any configuration dependencies, then neither plugin will have an effect.

What about creating a configuration that applies all of the toml dependencies? It doesn't have to use them for anything, just make them available for inspection.

That was exactly the idea I had in mind as well. Unfortunately the toml accessors generated by gradle are not iterable, so this would have to be done manually or via reflection. Or I suppose we could use this plugin's toml parser to iterate the modules and dump everything into a dummy configuration.

A quick google and I found this which might be helpful

Make sure we can iterate on entries of a version catalog

I still use the ext pattern where everything is a map declaration, which is nice for applying build logic over an set of definitions. But from the API it looks like you could query for libraries, then for their definition and version, and add that to a configuration. A little more work but since Gradle is a DSL on top of a Java API, most things are available if you peek under the covers.

You can also do something like this: https://github.com/littlerobots/version-catalog-update-plugin/issues/65#issuecomment-1204954251
Re: separate toml file for publishing, with support for multiple toml files coming soon that should be possible too.


Investigate Asar

youtube-dl use execFile to execute the binary and this hits the limitation of asar. Need to figure this out and turn on asar back later.

Got another idea, I think I can just use a new folder which contains youtube-dl binary file and in the future, users can even directly update that file to make Kaku works !

Fixed at 0ef3da728036ac3c0164c340f91c77521e5f87e5


Display .NET SDK version

It would be great for Cake.Recipe to display info about the version of .NET SDK being used.
Currently, the only clue we have is the MSBuild version like in this example:
========================================
DotNetCore-Build
========================================
Building Source/Cake.Email.Common.sln
MSBuild version 17.8.3+195e7f5a3 for .NET

and then we have to figure out what version of .NET SDK corresponds to 17.8.3 by looking it up here.
What I would like to see, is the result of the dotnet --version command. Bonus points if we get additional info similar, like we get when running the dotnet --info command.

For the time being, I added the following in my appveyor.yml:
before_build:
  - dotnet --info

This gives me the info I want when my build is running on AppVeyor but I still think it would be beneficial to add this to Cake.Recipe.


CF Release

Updates
Added

capital-framework: [patch] Adds environment.js for environment vars.

Changed

capital-framework: [patch] Updates webpack, gulp-rename, and
silent-npm-registry-client.
capital-framework: [minor] Fixes linter errors in release npm scripts.
capital-framework: [patch] Fixes globing in lint:scripts task
cf-atomic-component: [patch] Fixes or silences linter errors in Atomic Component
cf-expandables: [minor] Export the cf-expandables component
cf-expandables: [minor] Export the cf-tables component

Review

@cfpb/front-end-team-admin

I am a bot
After this PR is merged, I will instruct Travis to automagically perform the following steps:

Increment Capital Framework's version per our guidelines.
Add a timestamped entry to the changelog with the new version and its changes.
Tag the release and push it to GitHub.
Publish both capital-framework and any individually updated components to npm.
Update both canary, our development branch, and master, our release branch.

If I do something wrong, blame a human.

You are not
After this PR is merged, you should be prepared to update the CF dependencies I've released in the following projects:

[ ] capital-framework gh-pages branch -
The documentation site for Capital Framework, entire repo (including build process) could be affected.
[ ] design-manual -
The documentation site for the Design Manual, entire repo (including build process) could be affected.
[ ] generator-cf -
The Yeoman generator for creating new CFPB projects, only the app/templates directory should be affected.
[ ] cfgov-refresh -
The CFPB website, build process, cfgov/jinja2/v1, cfgov/unprocessed, and cfgov/wellbeing could all be affected.

Whoops, messed up the package name for cf-tables update.


Add Better Support For Whitelisting DM Commands

Relevant Issues

Closes #952
Description

Disabled commands in DMs by default. Note that this only disables the invocation of a command in DMs, not handling of messages. This means commands which use DMs for other purposes, such as battleship will still work. (Tested with a game of battleship against @Akarys42. Issue will be updated with the victor)
Adds a toggle to the whitelist override utility, to allow explicit enabling of a command in DMs.
Did you:

[x] Join the Python Discord Community?
[x] Read all the comments in this template?
[x] Ensure there is an issue open, or link relevant discord discussions?
[x] Read and agree to the contributing guidelines?

The French take this one


Inconsistent keyboard triggering from TMP input field

Describe the bug
After dismissing the keyboard by any means other than tapping another surface (such as pressing the X or enter buttons), tapping another surface toggles the keyboard on instead of off.
In addition, the keyboard sometimes dismisses itself seemingly without any user trigger. I don't think this is an accidental tap of something in the background, because it experiences the same bug with everything being a keyboard trigger:
Keyboard is shown -> Tap ground -> Keyboard is hidden -> Tap ground again -> Nothing happens
Keyboard is shown -> Keyboard disappears -> Tap ground again -> Keyboard reappears
To reproduce
Steps to reproduce the behavior:

Create a new scene and configure MRTK.
Create a TMP input field from the right click menu.
Convert the canvas that appears to MRTK, adding a NearInteractionTouchableUnityUI component as prompted, and scale that and the text field to a reasonable size.
Compile & deploy.
Trigger the keyboard, perhaps typing something, then press X.
Air tap the floor.

Expected behavior

The keyboard appearing only when an input field or similar object is tapped, not every surface.
The keyboard not disappearing without being prompted, especially while typing.

Your setup (please complete the following information)

Unity Version: 2020.3.12f1
MRTK Version: 2.7.2

Target platform (please complete the following information)

HoloLens 2

Thanks for reporting the issue. Could you try reproducing the behavior of TMP input field in the MixedRealityKeyboardExample scene and let us know if the problem also appears there?

It occurs for both types of input field in the MixedRealityKeyboardExample scene.

The keyboard disappearing for no reason part is a Unity bug and is tracked here: https://issuetracker.unity3d.com/product/unity/issues/guid/1360514/

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


app.respond does not use the proxy set in the application initialization

Reproducible in:
The Slack SDK version
"slack/bolt": "^3.13.0",
"slack/web-api": "^6.8.1",
Node.js runtime version
v20.0.0
OS info
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.17.3
PRETTY_NAME="Alpine Linux v3.17"
163-Ubuntu SMP Fri Mar 17 18:26:02 UTC 2023
Steps to reproduce:
(Share the commands to run, source code, and project settings)
const proxy = new HttpsProxyAgent(
  `http://${process.env.PROXY}:${process.env.PROXY_PORT}`,
);

const app = new App({
  clientOptions: { agent: proxy },
});

await app.respond({
  text: 'This is an example of a response to a slash command'
});

Due to being behind a corporate firewall, I'm using HttpsProxyAgent to traverse the proxy.

Slash command is sent to the Bolt.js app.
The app processes the request
Once done, responds in the same channel the slash command was sent from
Resond fails to use the configured proxy

Expected result:
The response message is sent to the user in the channel that they sent the slash command.
{
  "ok": true,
}

Actual result:
    AxiosError: read ECONNRESET
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
  syscall: 'read',
  code: 'ECONNRESET',
  errno: -104,
  config: {
    transitional: {
      silentJSONParsing: true,
      forcedJSONParsing: true,
      clarifyTimeoutError: false
    },
	adapter: [Function: httpAdapter],
    transformRequest: [ [Function: transformRequest] ],
    transformResponse: [ [Function: transformResponse] ],
    timeout: 0,
    xsrfCookieName: 'XSRF-TOKEN',
    xsrfHeaderName: 'X-XSRF-TOKEN',
    maxContentLength: -1,
    maxBodyLength: -1,
    env: { FormData: [Function] },
    validateStatus: [Function: validateStatus],
    headers: {
      Accept: 'application/json, text/plain, */*',
      'Content-Type': 'application/json',
      'User-Agent': 'axios/0.27.2',
      'Content-Length': 170
    },
    proxy: false,
    method: 'post',
    url: 'https://hooks.slack.com/commands/{removed-for-security}/{removed-for-security}/{removed-for-security}',
    data: '{"text":"This is a test response to a slash command."}'
  },
  request: <ref *1> Writable {
    _writableState: WritableState {
      objectMode: false,
      highWaterMark: 16384,
      finalCalled: false,
      needDrain: false,
      ending: false,
      ended: false,
      finished: false,
      destroyed: false,
      decodeStrings: true,
      defaultEncoding: 'utf8',
      length: 0,
      writing: false,
      corked: 0,
      sync: true,
      bufferProcessing: false,
      onwrite: [Function: bound onwrite],
      writecb: null,
      writelen: 0,
      afterWriteTickInfo: null,
      buffered: [],
      bufferedIndex: 0,
      allBuffers: true,
      allNoop: true,
      pendingcb: 0,
      constructed: true,
      prefinished: false,
      errorEmitted: false,
      emitClose: true,
      autoDestroy: true,
      errored: null,
      closed: false,
      closeEmitted: false,
      [Symbol(kOnFinished)]: []
    },
	_events: [Object: null prototype] {
      response: [Function: handleResponse],
      error: [Function: handleRequestError],
      socket: [Function: handleRequestSocket]
    },
    _eventsCount: 3,
    _maxListeners: undefined,
    _options: {
      maxRedirects: 21,
      maxBodyLength: 10485760,
      protocol: 'https:',
      path: '/commands/{removed-for-security}/{removed-for-security}/{removed-for-security}',
      method: 'POST',
      headers: [Object],
      agent: undefined,
      agents: [Object],
      auth: undefined,
      hostname: 'hooks.slack.com',
      port: null,
      nativeProtocols: [Object],
      pathname: '/commands/{removed-for-security}/{removed-for-security}/{removed-for-security}'
    },
	_ended: false,
    _ending: true,
    _redirectCount: 0,
    _redirects: [],
    _requestBodyLength: 170,
    _requestBodyBuffers: [ [Object] ],
    _onNativeResponse: [Function (anonymous)],
    _currentRequest: ClientRequest {
      _events: [Object: null prototype],
      _eventsCount: 7,
      _maxListeners: undefined,
      outputData: [],
      outputSize: 0,
      writable: true,
      destroyed: false,
      _last: false,
      chunkedEncoding: false,
      shouldKeepAlive: true,
      maxRequestsOnConnectionReached: false,
      _defaultKeepAlive: true,
      useChunkedEncodingByDefault: true,
      sendDate: false,
      _removedConnection: false,
      _removedContLen: false,
      _removedTE: false,
      strictContentLength: false,
      _contentLength: 170,
      _hasBody: true,
      _trailer: '',
      finished: false,
      _headerSent: true,
      _closed: false,
      socket: [TLSSocket],
	  _header: 'POST /commands/{removed-for-security}/{removed-for-security}/{removed-for-security} HTTP/1.1\r\n' +
        'Accept: application/json, text/plain, */*\r\n' +
        'Content-Type: application/json\r\n' +
        'User-Agent: axios/0.27.2\r\n' +
        'Content-Length: 170\r\n' +
        'Host: hooks.slack.com\r\n' +
        'Connection: keep-alive\r\n' +
        '\r\n',
      _keepAliveTimeout: 0,
      _onPendingData: [Function: nop],
      agent: [Agent],
      socketPath: undefined,
      method: 'POST',
      maxHeaderSize: undefined,
      insecureHTTPParser: undefined,
      joinDuplicateHeaders: undefined,
      path: '/commands/{removed-for-security}/{removed-for-security}/{removed-for-security}',
      _ended: false,
      res: null,
      aborted: false,
      timeoutCb: [Function: emitRequestTimeout],
      upgradeOrConnect: false,
      parser: null,
      maxHeadersCount: null,
      reusedSocket: false,
      host: 'hooks.slack.com',
      protocol: 'https:',
      _redirectable: [Circular *1],
	   [Symbol(kCapture)]: false,
      [Symbol(kBytesWritten)]: 0,
      [Symbol(kNeedDrain)]: false,
      [Symbol(corked)]: 0,
      [Symbol(kOutHeaders)]: [Object: null prototype],
      [Symbol(errored)]: null,
      [Symbol(kHighWaterMark)]: 16384,
      [Symbol(kUniqueHeaders)]: null
    },
    _currentUrl: 'https://hooks.slack.com/commands/{removed-for-security}/{removed-for-security}/{removed-for-security}',
    [Symbol(kCapture)]: false
  }
}

:warning: Note: This works during local testing when I don't have to use the proxy.

Hi @chasek-hpe 👋🏻
Thanks for sharing this issue! Looking a little deeper into the source code, the app.respond(...) does not inherit the clientOptions proxy. This is something that we should fix 🙇🏻
A workaround (untested) may be to manually set the proxy when calling response because the second argument is a <AxiosResponse> which exposes config: AxiosRequestConfig:
await app.respond({
  text: 'This is an example of a response to a slash command'
}, {
  config: {
    proxy: proxy,
  },
);

Would you mind giving that a shot to let me know if the workaround helps?

@mwbrooks - that workaround was successful. ✅

Hi, @mwbrooks - The workaround worked in local testing; however, not in production.
Is the agent property available in the respond config object? I may also need to disable the proxy when I set the agent and set rejectUnauthorized to false

Hey @chasek-hpe , just to confirm, you are using app.command to respond to a slash command, is that correct? And executing await respond() within the listener passed to app.command? That part is unclear to me based on your code snippets.
One more question I had is: what is the difference between your local testing and production environments? I am trying to reason through why the workaround provided works locally but not in production.

Hi @filmaj -
I'm doing this → https://slack.dev/bolt-js/concepts#commands

Followed by referencing this → https://slack.dev/bolt-js/concepts#action-respond

The only difference between local development and production is that the application runs from a docker container in production.

@chasek-hpe there must be some difference in terms of networking between the two environments that causes this difference.
Have you tried playing with other axios request config properties like httpsAgent instead of proxy?

Hi @filmaj
After quite a bit more troubleshooting, the issue is caused by a redirect loop since Axios is not setting the xsrfCookieName and the xsrfHeaderName.
const agent = new HttpsProxyAgent(
    `http://${process.env.PROXY}:${process.env.PROXY_PORT}`,
);

await axios(body.response_url, {
            method: 'post',
            rejectUnauthorized: false,
            Headers: {
                'Content-Type': 'application/json',
                'Accept-Charset': 'utf-8',
            },
            data: {
                delete_original: 'true',
            },
            withCredentials: true,
            xsrfCookieName: 'XSRF-TOKEN',
            xsrfHeaderName: 'X-XSRF-TOKEN',
            proxy: false,
            httpsAgent: agent,
        });

I had to add the following to the config in Axios to get this to work properly.
{
    rejectUnauthorized: false,
    withCredentials: true,
    xsrfCookieName: 'XSRF-TOKEN',
    xsrfHeaderName: 'X-XSRF-TOKEN',
    proxy: false,
    httpsAgent: agent,
}

That sounds frustrating, but glad you figured that out. I am going to close this issue out, but if there's more to discuss feel free to re-open or file another issue.


Install PyAedt with error

Before submitting the issue

[x] I have searched among the existing issues
[x] I am using a Python virtual environment

Description of the bug
Install PaAedt with error

Steps To Reproduce
Clone PyAedt any place example C:\pyaedt
Open command line and type these command:

py -3.11 -m venv venv311
call venv311\Scripts\activate
python -m pip install pip -U
python -m pip install wheel setuptools -U
python -m pip install C:\pyaedt.[tests]   <-------------------- get error after this

Which Operating System are you using?
Windows
Which Python version are you using?
3.11
Installed packages
Nothin come up

Hi @anspraksaph. I was not aware that you could provide a target like C:\pyaedt.[tests] to pip install !
I tried what you just described on my laptop and it worked in my case.
Below is the code I used. Note that I am:

using a Python that was installed with hatch (I don't know where your py -3.11 comes from);
cloning pyaedt in my user space and not in C:

C:\Users\smorais\AppData\Local\hatch\pythons\3.11\python\python.exe -m venv venv311
 .\venv311\Scripts\activate
python -m pip install pip -U
python -m pip install wheel setuptools -U
python -m pip install C:\Users\smorais\pyaedt.[tests]

On top of being able to install it myself, we do have CI jobs that consist in testing the installation of pyaedt with the combination of:

Python version: '3.8', '3.9', '3.10', '3.11', '3.12';
OS: Ubuntu, Windows;
Install target: 'all', 'installer'.
Therefore, I feel like the problem is associated to your environment. Could you try to clone the repo in another place and move inside the cloned repo (with cd path/to/pyaedt) to call python -m pip install .[tests] ?


Improved std dev code for stats.py

Consider updating stats.py with
Welford's algorithm computes the sample variance incrementally.
From: https://stackoverflow.com/questions/5543651/computing-standard-deviation-in-a-stream

The OnlineMeanVariance thing in stats.py computes mean, variance and std incrementally, based on Welford's algorithm.


Origin header validation in WS transport - APIM 3.2.0

Problem
Currently, if we configured the Origin header validation for the WS transport, the Origin header will validate even if the header is not in the request.
Solution
Need to validate the Origin header value in the web socket transport if the Origin header is in the request
Affected Component
APIM
Version
3.2.0
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Hi Team,
Customer has modified the requirement as follows.
Also we need some way to update origin header values at runtime for websocket apis. Because to add origin header value we can't do a deployment in production environment. It will be very costly effort we need to spend in higher environment. In REST we have cors_request_handler.xml sequence file where we can add allow origin header at runtime. This is not require any deployment. Similar kind of approach we are expecting for websocket api as well. we mentioned this information in the last meeting as well. Please consider all the scenarios discuss with your product team and let us know. Websocket origin header addition should have some kind of leverage like REST and can be add at runtime. This is what our expectation.
Please consider these requirements as well when the improvement is given.

Following PRs cover origin header validation per API.
https://github.com/wso2/apim-apps/pull/378
https://github.com/wso2/carbon-apimgt/pull/11622

Please note that this improvement can be managed using API Handlers in APIM 4.x version. Until this implementation is confirmed with a POC we will need to hold the issue.

closing this issue since the master fix: https://github.com/wso2/carbon-apimgt/pull/11908 has already been merged into the master branch.
Refer: https://github.com/wso2/api-manager/issues/1484 as per the comment [1].
[1] https://github.com/wso2/api-manager/issues/612#issuecomment-1333662010


Fail 'istioctl kube-inject' on failure instead of reporting to stderr

Resolve https://github.com/istio/istio/issues/23717 by failing kube-inject if a pod is already injected or has host networking.

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

Test name
Commit
Details
Rerun command

gencheck_istio
8c0c3f93297b42fb3bfd5bfdad29af47b0966982
link
/test gencheck_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
8c0c3f93297b42fb3bfd5bfdad29af47b0966982
link
/test gencheck_istio

unit-tests_istio
8c0c3f93297b42fb3bfd5bfdad29af47b0966982
link
/test unit-tests_istio

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

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

Test name
Commit
Details
Rerun command

gencheck_istio
8c0c3f93297b42fb3bfd5bfdad29af47b0966982
link
/test gencheck_istio

unit-tests_istio
8c0c3f93297b42fb3bfd5bfdad29af47b0966982
link
/test unit-tests_istio

lint_istio
28d13c54b129893ff3cf29cff94b585795c368e7
link
/test lint_istio

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

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
02686485363b2a51f6a7e3e64c065aea14e7c45c
link
/test integ-pilot-k8s-tests_istio

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

/retest

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

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
02686485363b2a51f6a7e3e64c065aea14e7c45c
link
/test integ-pilot-k8s-tests_istio

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

/retest

What if you have a big yaml of all your deployments? Now a single one will cause it to fail - may cause some issues in ci pipelines

Fair enough.  How would you feel if the IntoResourceFile yaml reader accumulated the errors in a multi-error instead of bailing on the first one?  Then stdout would include injected yaml.  I could code it to keep or reject the unchanged failures.
I created this because @GregHanson reported users missing the output.  Any thoughts?
Other possibilities considered

Output processing errors to stdout at the end, surrounded by lines of asterisks, but keep current $? results.
Keep processing, skipping invalid injections
Keep processing, pass invalid injections through
A --force option, or guidance in the long description to use | true in scripts to avoid bombing out.

@esnible for #23717 my main comment was the one line error message is very easy to miss since there are no newlines between the error message and the rejected yaml.  I don't know if in cases like this it would be better to put the error message at the end of the yaml output?  Or maybe some additional formatting around the error message to call better attention to it in this case?

@GregHanson This keeps the $? behavior the same.
Instead of stderr messages appearing at the beginning they are held until the end.  There is a \n dividing them from the YAML and ===> before each one:

===> Skipping injection because "hello-host-network" has host networking enabled

@GregHanson Can you review?


build: Added CONFIG_NO_OPTIMIZATIONS

Added a new config option which lowers the compiler
optimizations to -O0 independently of other flags.
CONFIG_COVERAGE uses it now instead of having its own
choice in CMakeLists.txt
Fixes #5720
Signed-off-by: Alberto Escolar Piedras<EMAIL_ADDRESS>

@SebastianBoe @andrewboie : Are we ready to merge?


fix: forcing requests to be larger than 2.32.2

As title says

I think we need to seriously consider this policy: https://iscinumpy.dev/post/bound-version-constraints/

I agree :) I wasn't planning on merging this. This is related to determine which library was causing the limitation to 2.32 - see https://github.com/ansys/pyensight/pull/382

All working now - closing


[FLINK-11099][Table API&SQL] Migrate flink-table runtime  CRow  Types classes

What is the purpose of the change
(To Migrate flink-table runtime  CRow  Types classes.)
Brief change log
(for example:)

Migrate CRow.Scala to CRow.Java and write it into the flink-table-common directory.
Migrate CRowComparator.Scala to CRowComparator.Java and write it into the flink-table-common directory.
Migrate CRowSerializer.Scala to CRowSerializer.Java and write it into the flink-table-common directory.
Migrate CRowTypeInfo.Scala to CRowTypeInfo.Java and write it into the flink-table-common directory.
In addition, there are other file changes due to the above four file changes

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Hi, @XuQianJin-Stars , according to FLIP-28 it looks CRows may need to migrate into flink-table-runtime module. This moudle will be set up, is it right? @twalthr

@xueyumusic According to the description, flink-table will be removed as the top-level module.Something seems to be wrong.

@xueyumusic yes, the module structure will be setup soon. Once the discussion about the new structure has finished. @XuQianJin-Stars you can put your ported class in flink-table for now. We can update the PR once the new structure is ready. I think this will happen in the next few days.

hi @twalthr Well, look forward to it .
thanks
qianjin

@XuQianJin-Stars no need for a new PR, just update the branch or do a force push. Thanks.

@twalthr I update the branch or do a force push.
thanks
qianjin


react-app-rewire-define-plugin

Hi,
is there any way to define environment variable in webpack config?
something like :
const rewireDefinePlugin = require('react-app-rewire-define-plugin')

// Use `webpack.DefinePlugin` to add the version number from package.json
config = rewireDefinePlugin(config, env, {
  'process.env.VERSION': JSON.stringify(require('./package.json').version)
})

@aaronchenwei
I would like to be able to use DefinePlugin to define DEV and PROD variables. Any idea how I should try to achieve that ? I tried your solution but it does not work.

@devals9
Do you mean ?
proccess.env.DEV = {...}
process.env.PROD = {...}

My previous code snippet is just to append variables under process.env

Here is package.json/scritps config:
  "scripts": {     "dev": "react-app-rewired start --open",     "build:test": "react-app-rewired build --test",     "build:pre": "react-app-rewired build --pre",     "build:prod": "react-app-rewired build --prod",     "eject": "react-scripts eject"   }
const path = require('path')
const path = require('path')
const Dotenv = require('dotenv-webpack')
const version = JSON.stringify(require('../package.json').version)
const resolvePath = dir => path.join(__dirname, '..', dir)
const mode = process.argv[2].split('--')
const isDev = process.env.NODE_ENV === 'development'
const envPath = isDev ? resolvePath('.env.development') : resolvePath(.env.${mode})
const envVars = {}
const definitions = new Dotenv({
path: envPath
}).definitions
Object.keys(definitions).forEach(key => {
const [, api] = key.split('process.env.')
envVars[api] = definitions[key]
})
function rewireDefinePlugin (config) {
config.plugins.some(p => {
if (
p.definitions &&
p.definitions['process.env']
) {
p.definitions['process.env'] = { ...envVars, version}
return true
}
})
return config
}
module.exports = rewireDefinePlugin

Closing as the solution from @aaronchenwei is verified as working with<EMAIL_ADDRESS>If there are further problems, please open a new issue.

https://github.com/foxundermoon/cra-define-override#readme


DOCKER_BUILDKIT --mount is broken

Problem description

Following instructions for mounting secrets here: https://docs.docker.com/develop/develop-images/build_enhancements/#new-docker-build-secret-information
Results in
failed to solve with frontend dockerfile.v0: failed to create LLB definition: Dockerfile parse error line 2: Unknown flag: mount

Details:
$ cat mysecret.txt
WARMACHINEROX

$ cat Dockerfile_2
FROM alpine
RUN --mount=type=secret,id=mysecret cat /run/secrets/mysecret
RUN --mount=type=secret,id=mysecret,dst=/foobar cat /foobar

$ DOCKER_BUILDKIT=1 docker -D build -f Dockerfile_2 --no-cache --secret id=mysecret,src=mysecret.txt .
DEBU[0000] serving grpc connection
[+] Building 0.1s (2/2) FINISHED
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 34B                                                                                0.0s
 => [internal] load build definition from Dockerfile_2                                                                                0.0s
 => => transferring dockerfile: 40B                                                                                0.0s
failed to solve with frontend dockerfile.v0: failed to create LLB definition: Dockerfile parse error line 2: Unknown flag: mount

In logs I see:
warning msg="grpc: addrConn.createTransport failed to connect to { 0  <nil>}. Err :connection error: desc = \"transport: Error while dialing only one connection allowed\". Reconnecting..." module=grpc

Problem location

effects docker build

Project version(s) affected

Docker version 19.03.9, build 9d988398e7
Ubuntu 20.04
Suggestions for a fix

You need to specify the "experimental" syntax in the dockerfile. The --mount option is not in the 1.0 stable syntax yet.
See https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/experimental.md#use-experimental-dockerfile-frontend

Ahhh, missed that bit.  Thanks!  Closing.


Error When Revisiting Custom Teams ?app=portals App

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details
browser version Teams desktop App
SPFx version 1.13
Node.js version V 12.13
Describe the bug / error
When revisiting the custom personal app that is registered with ?app=portals it opens a browser with incorrect url:
_layouts/15/undefined&inPlaceNav=portals
This issue is based on this comment: https://github.com/SharePoint/sp-dev-docs/issues/8191#issuecomment-1184108605
Steps to reproduce
You have a custom spfx teams app , you click on the app and it's loads fine

Later you click in any option in the menu like calendar , teams chat

You click in teams app again and then it show up white screen

Expected behavior
The app is opened normally.

hello @AJIXuMuK, do you think will be fixed in the next release?  do you know where will be the next teams release? Thanks

@Rtoribiog - it has been merged and will be rolled out in the next couple of weeks.

thanks @AJIXuMuK  for the comments

This should be rolled out WW by now.

Now it works as expected.  Thanks for addressing it @AJIXuMuK