DOCKER-71-fix-wrong-condition-for-sonarSecretKey-in-helm-chart

fix condition in helm templating for sonar.properties ConfigMap
fix condition in helm templating for volumeMounts of this sonar.properties data

tests:

templating locally with various .values file
ct tests

Please ensure your pull request adheres to the following guidelines:

[x] explain your motives to contribute this change: what problem you are trying to fix, what improvement you are trying to make
[x] Document your Changes in the CHANGELOG.md file of the respected chart as well as the Chart.yaml
[x] Bump the Version number of the respected chart

For testing this change, I would suggest the following:

Use sonarSecretKey, sonarProperties, sonarSecretProperties, elasticsearch.bootstrapChecks independently then runs the helm chart and verify that in the pod, /opt/sonarqube/conf/sonar.properties and /opt/sonarqube/secret/sonar-secret.properties are defined as expected
Activate multiple of these parameters at the same time and ensure the result in the same way

Chart is failing + comments Also missing a dash in commit message DOCKER-71 :)

For testing this change, I would suggest the following:
* Use sonarSecretKey, sonarProperties, sonarSecretProperties, elasticsearch.bootstrapChecks independently then runs the helm chart and verify that in the pod, /opt/sonarqube/conf/sonar.properties and /opt/sonarqube/secret/sonar-secret.properties are defined as expected

* Activate multiple of these parameters at the same time and ensure the result in the same way

Thanks a lot for the good comments, passing the PR back in draft, until the tests are all done for the various parameters


http_authorization event isn't triggered on iOS

When the server answers with a 401 Unauthorized code, the plugin doesn't trigger the http_authorization event. The log in placed inside the plugin doesn't even appear. I'm trying this on a iOS emulator. The backend server is a Ruby On Rails api.
Your Environment

Plugin version: 0.6.1
Platform: iOS
OS version: 12.4
Device manufacturer and model: Iphone X
Running in Simulator: Yes
React Native version: 0.60.5
Plugin configuration options:

{
            desiredAccuracy: BackgroundGeolocation.HIGH_ACCURACY,
            stationaryRadius: 20,
            distanceFilter: 10,
            stopOnTerminate: true,
            maxLocations: 100000,
            syncThreshold: 100,
            locationProvider: BackgroundGeolocation.DISTANCE_FILTER_PROVIDER,
            url: `xxx/update_tracking`,
            syncUrl: `xxx/update_tracking`,
            httpHeaders: {
                Authorization: `Bearer ${Api.accessToken}`,
            },
            postTemplate: {
                latitude: '@latitude',
                longitude: '@longitude',
                speed: '@speed',
                tracking_at: '@time',
            },
        }

Link to your project: I can't provide it sorry.

Context
I need it to trigger to be able to change the headers in the template with the new accessToken. The event should clearly trigger.
Expected Behavior
The event trigger
Actual Behavior
Nothing happens

@FeNoMeNa It looks like you're the guy who added that feature, is it working for you?


Deprecation Notice for Composer v2.0

Deprecation Notice: Class:
TheRezor\TransactionalJobs\TransactionalDispatcher located in ./vendor/therezor/laravel-transactional-jobs/src/TransactionalDispatcher.php does not comply with psr-0 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201

Deprecation Notice: Class:
TheRezor\TransactionalJobs\BusServiceProvider located in ./vendor/therezor/laravel-transactional-jobs/src/BusServiceProvider.php does not comply with psr-0 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201

Thanks for report, will cover in new version

Should be fixed in v1.0


Script creation of S3 and SQS resources

Provisioning the app now creates RF_SQS, RF_SQS_DEAD_LETTER, and RF_S3_BUCKET in /etc/rf.d/env based on the USER, and runs a script to create an SQS queue, an SQS dead letter queue, and an S3 bucket with names specified by these environment variables. The frontend should get the new bucket name and upload there, which should result in messages in the queue.
Connects #116

@hcastro: Might want to take a look at this. Using boto3 wasn't a problem locally.

Overall this seems pretty good.

Don't bother trying to test this. I'll have a better version up soon.

I'm not sure why the build is failing, but I think we had something similar happen recently. I couldn't get the AWS script to run on provisioning (spent a couple hours and gave up), but you should be able to test it by provisioning the app and then running ./scripts/create-aws-resources.sh from your host machine.

@azavea-bot rebuild

@azavea-bot rebuild

I'm finding that after running vagrant provision app, the rf-app service isn't started even when I've made no modifications to the upstart job. I tried killing the debugserver while provisioning, but that didn't help.

@azavea-bot rebuild

@azavea-bot rebuild

The upstart job does create the AWS resources for me. I'm unclear why we moved this from the worker upstart task to the app upstart task but I'm now confident that everything works properly (after patching... see slack for patch.)

The upstart job does create the AWS resources for me. I'm unclear why we moved this from the worker upstart task to the app upstart task but I'm now confident that everything works properly (after patching
worker-service.patch.txt)

I think that the application should be responsible for ensuring that the AWS resources exist because that's where message publishing happens. That said, I cannot think of a reason why it shouldn't exist as a dependency for both services.
I am against some of the changes in the suggested patch because they make it slightly more difficult to differentiate services. One service is the Django web application (rf-app), while the other is meant to be a worker service that polls SQS (rf-worker). Naming them both the same thing works because they're targeted at different machines, but I like the idea of having accurate names.
Also, I am unable to reproduce a failure (using both development and test mode) with the current state of this branch. Looking into the Jenkins failure now, but I think that it may be related to the fact that we're bouncing between service definitions across PRs.

@azavea-bot rebuild

@azavea-bot rebuild

@azavea-bot rebuild

@azavea-bot rebuild

@azavea-bot rebuild

Good to merge. I confirmed that the creation of AWS services works, and that the upload workflow still completes. Jenkins difficulties were due to PRs with different provisioning steps crossing up between builds.
:+1:


Add a physical location field to monitor attributes

📑 I have found these related issues/pull requests
Nothing found
🏷 Feature Request Type
Change to existing monitor
🔖 Feature description
It would be very useful to add a physical location string field to the attributes for a monitor.  Unlike the freindly name field this doesn't have to appear in the monitor list, but would be visible at the top when someone clicks on the details page for that monitor.
✔ Solution
Add a physical location string to the attributes for a monitor and display it on the monitor details page.
❓ Alternatives
It's common to have such an attribute
📝 Additional Context
No response

@sprior
Why not add a tag like datacenter:eu-central-1, location:frankfurt, az:primary, ... (something that matches your deployment strategy).
I think this is already handled by said subsystem.

@CommanderStorm a tag would be appropriate for which datacenter as you were thinking, but I'm thinking on a smaller level like which rack within the datacenter and tags aren't as great for that.

Why could this not be coverend by a tag like  room:2410.EG.006 or room:MW 0450B?


refactor: multiple roslyn analyzer fixes

Includes:

IDE0270: Null check can be simplified
IDE0200: Remove unnecessary lambda expression
IDE0120: Simplify LINQ expression

Codecov Report

Merging #404 (a5d4acc) into main (a8dea41) will increase coverage by 0.01%.
The diff coverage is 54.54%.

@@            Coverage Diff             @@
##             main     #404      +/-   ##
==========================================
+ Coverage   68.99%   69.01%   +0.01%
==========================================
  Files         242      242
  Lines        7777     7772       -5
==========================================
- Hits         5366     5364       -2
+ Misses       2411     2408       -3

Files
Coverage Δ

...bom.Api/Executors/ConcurrentSha256HashValidator.cs
82.14% <100.00%> (ø)

...m.Api/Manifest/Configuration/SbomConfigProvider.cs
70.89% <100.00%> (-0.22%)
:arrow_down:

....Api/Utils/ComponentDetectionCliArgumentBuilder.cs
81.75% <100.00%> (ø)

...bom.Api/Workflows/Helpers/PackageArrayGenerator.cs
89.28% <100.00%> (-0.19%)
:arrow_down:

...soft.Sbom.Contracts/Contracts/SBOMSpecification.cs
16.07% <0.00%> (+0.55%)
:arrow_up:

...crosoft.Sbom.Parsers.Spdx22SbomParser/Generator.cs
12.00% <0.00%> (+0.05%)
:arrow_up:


Fix element removal on transition end in Firefox70

Apparently Firefox 70 does not reflow the page with getComputedStyle().transform any more. Using element.offsetLeft apparently works.
Before this fix:

Travis log
Browserstack (ignore the failing chrome 49)

After this fix:
Browserstack session
Build log from my local test run
Scope: current workspace package

><EMAIL_ADDRESS>test-browser /home/jan/Dokumente/Programmierprojekte/cyclejs/dom
> karma start

27 10 2019 20:42:06.018:INFO [compiler.karma-typescript]: Compiling project using Typescript 3.2.4
27 10 2019 20:42:09.988:INFO [compiler.karma-typescript]: Compiled 11 files in 3942 ms.
27 10 2019 20:42:11.664:INFO [bundler.karma-typescript]: Bundled imports for 30 file(s) in 1173 ms.
27 10 2019 20:42:12.153:INFO [karma-server]: Karma v4.2.0 server started at http://<IP_ADDRESS>:9876/
27 10 2019 20:42:12.154:INFO [launcher]: Launching browsers BS_Chrome_Current, BS_Firefox_Current, BS_Safari_Current, BS_Android_8, BS_Chrome_49, BS_Firefox_52, BS_Safari_9, BS_Android_4_4, BS_iphone_11, BS_MS_Edge, BS_IE_11, BS_IE_10 with concurrency 1
27 10 2019 20:42:12.209:INFO [launcher]: Starting browser chrome latest (Windows 10) on BrowserStack
27 10 2019 20:42:17.701:INFO [launcher.browserstack]: chrome latest (Windows 10) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/6e864865eb891cbed0f42de1d39c2d35dd89686f
27 10 2019 20:42:24.307:INFO [Chrome 78.0.3904 (Windows 10.0.0)]: Connected on socket o2mR2zXc30aAN3uIAAAA with id 95928590
................................................................................
....................
Chrome 78.0.3904 (Windows 10.0.0): Executed 100 of 100 SUCCESS (7.806 secs / 7.294 secs)
27 10 2019 20:42:36.151:INFO [launcher]: Starting browser firefox latest (Windows 10) on BrowserStack
27 10 2019 20:42:38.262:INFO [launcher.browserstack]: firefox latest (Windows 10) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/cd87478ce16ddec2f9465d47bf50c110fda9e667
27 10 2019 20:42:45.470:INFO [Firefox 70.0.0 (Windows 10.0.0)]: Connected on socket hNhxiR5XIa2c3ckYAAAB with id 95940883
....................................................................27 10 2019 20:42:54.622:INFO [Safari 11.1.2 (Mac OS X 10.13.6)]: Connected on socket Jj0TLrvfN90hLHtwAAAC with id 5988172
............
...........................
Safari 11.1.2 (Mac OS X 10.13.6): Executed 39 of 0 SUCCESS (0.441 secs / 3.918 secs)
................................
Firefox 70.0.0 (Windows 10.0.0): Executed 100 of 100 SUCCESS (7.821 secs / 7.378 secs)
27 10 2019 20:42:57.345:INFO [launcher]: Starting browser safari latest (OS X High Sierra) on BrowserStack
................................27 10 2019 20:42:59.329:INFO [launcher.browserstack]: safari latest (OS X High Sierra) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/912024899589902a8eadabb6fb28902156901338
........................................27 10 2019 20:43:04.530:INFO [Safari 11.1.2 (Mac OS X 10.13.6)]: Connected on socket fzsb6luiYzpKikO2AAAD with id 16851665
........
....................
Safari 11.1.2 (Mac OS X 10.13.6): Executed 100 of 100 SUCCESS (8.281 secs / 7.49 secs)
................................................................................
....................
Safari 11.1.2 (Mac OS X 10.13.6): Executed 100 of 100 SUCCESS (8.464 secs / 7.633 secs)
27 10 2019 20:43:17.519:INFO [launcher]: Starting browser Android (Android 8.0) on BrowserStack
27 10 2019 20:43:18.988:INFO [launcher.browserstack]: Android (Android 8.0) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/a7c824004284d688c4bcd07e9a62401aed583856
27 10 2019 20:43:25.243:INFO [Chrome Mobile 76.0.3809 (Android 8.0.0)]: Connected on socket qc7QpQVYEehl773xAAAE with id 52262906
................................................................................
....................
Chrome Mobile 76.0.3809 (Android 8.0.0): Executed 100 of 100 SUCCESS (8.136 secs / 7.534 secs)
27 10 2019 20:43:37.485:INFO [launcher]: Starting browser chrome 49 (Windows 10) on BrowserStack
27 10 2019 20:43:39.913:INFO [launcher.browserstack]: chrome 49 (Windows 10) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/582b5baabf014a82ac3aac44d5eb3bcef38f89fb
27 10 2019 20:43:48.806:INFO [Chrome 49.0.2623 (Windows 10.0.0)]: Connected on socket 5mFpzYSW9YZ1W-rjAAAF with id 4196734
................................................................................
....................
Chrome 49.0.2623 (Windows 10.0.0): Executed 100 of 100 SUCCESS (7.763 secs / 7.291 secs)
27 10 2019 20:44:00.954:INFO [launcher]: Starting browser firefox 52 (Windows 10) on BrowserStack
27 10 2019 20:44:03.369:INFO [launcher.browserstack]: firefox 52 (Windows 10) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/8aaf3e8e75476c52139240c5074c8981b88c1ba6
27 10 2019 20:44:09.469:INFO [Firefox 52.0.0 (Windows 10.0.0)]: Connected on socket lkhXkmlrM-Ldfq8lAAAG with id 57673169
................................................................................
....................
Firefox 52.0.0 (Windows 10.0.0): Executed 100 of 100 SUCCESS (8.368 secs / 7.357 secs)
27 10 2019 20:44:21.928:INFO [launcher]: Starting browser safari 9.1 (OS X El Capitan) on BrowserStack
27 10 2019 20:44:23.148:INFO [launcher.browserstack]: safari 9.1 (OS X El Capitan) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/3f3ed53eefe98f48e0fd2efe83d2acee421037d6
27 10 2019 20:44:32.473:INFO [Safari 9.1.3 (Mac OS X 10.11.6)]: Connected on socket bUDsuYFS-sZoiK-pAAAH with id 13056251
................................................................................
....................
Safari 9.1.3 (Mac OS X 10.11.6): Executed 100 of 100 SUCCESS (8.315 secs / 7.613 secs)
27 10 2019 20:44:44.968:INFO [launcher]: Starting browser Google Nexus 5 (Android 4.4) on BrowserStack
27 10 2019 20:44:45.926:INFO [launcher.browserstack]: Google Nexus 5 (Android 4.4) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/494d8419d4bd026e4cb685975e96fd1085b46241
27 10 2019 20:45:00.119:INFO [Chrome Mobile 76.0.3809 (Android 4.4.0)]: Connected on socket WUD66gW46a--QG3iAAAI with id 84465019
................................................................................
....................
Chrome Mobile 76.0.3809 (Android 4.4.0): Executed 100 of 100 SUCCESS (8.846 secs / 7.913 secs)
27 10 2019 20:45:13.127:INFO [launcher]: Starting browser Mobile Safari (ios 11.0) on BrowserStack
27 10 2019 20:45:14.662:INFO [launcher.browserstack]: Mobile Safari (ios 11.0) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/6cc20d53a1d9289fdeaa4df470331a3a87b39ac3
27 10 2019 20:45:24.792:INFO [Mobile Safari 11.0.0 (iOS 11.0.0)]: Connected on socket TaTL3ZYR1QRruyIbAAAJ with id 64132194
................................................................................
....................
Mobile Safari 11.0.0 (iOS 11.0.0): Executed 100 of 100 SUCCESS (7.987 secs / 7.555 secs)
27 10 2019 20:45:37.090:INFO [launcher]: Starting browser edge latest (Windows 10) on BrowserStack
27 10 2019 20:45:39.634:INFO [launcher.browserstack]: edge latest (Windows 10) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/4cd08121fdbb97bd29bf36954c0dc0ab3b73b499
27 10 2019 20:45:45.720:INFO [Edge 18.18362.0 (Windows 10.0.0)]: Connected on socket oKl-N7nm6XcXc35ZAAAK with id 61551593
................................................................................
....................
Edge 18.18362.0 (Windows 10.0.0): Executed 100 of 100 SUCCESS (7.862 secs / 7.408 secs)
27 10 2019 20:45:58.024:INFO [launcher]: Starting browser ie 11.0 (Windows 7) on BrowserStack
27 10 2019 20:45:59.843:INFO [launcher.browserstack]: ie 11.0 (Windows 7) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/f341401500ecb4a46808fe97f00de92ff56cf4f0
27 10 2019 20:46:32.339:INFO [IE 11.0.0 (Windows 7.0.0)]: Connected on socket PpJUOBtMDJ1_E3cEAAAL with id 92234561
27 10 2019 20:46:33.922:WARN [Safari 11.1.2 (Mac OS X 10.13.6)]: Disconnected (0 times)Client disconnected from CONNECTED state (transport close)
Safari 11.1.2 (Mac OS X 10.13.6) ERROR
  DisconnectedClient disconnected from CONNECTED state (transport close)
................................................................................
....................
IE 11.0.0 (Windows 7.0.0): Executed 100 of 100 SUCCESS (8.622 secs / 7.824 secs)
27 10 2019 20:46:45.262:INFO [launcher]: Starting browser ie 10.0 (Windows 7) on BrowserStack
27 10 2019 20:46:47.541:INFO [launcher.browserstack]: ie 10.0 (Windows 7) session at https://automate.browserstack.com/builds/f587b63c51112ab8dfd1f67370b7849a7962a250/sessions/122dab988800c3172f1600fa078e3759eec3ad54
27 10 2019 20:46:50.970:INFO [IE 10.0.0 (Windows 7.0.0)]: Connected on socket IgMXT3gmeH4HSlaRAAAM with id 20231488
IE 10.0.0 (Windows 7.0.0) ERROR: 'This browser lacks typed array (Uint8Array) support which is required by `buffer` v5.x. Use `buffer` v4.x if you require old browser support.'
IE 10.0.0 (Windows 7.0.0) ERROR: 'This browser lacks typed array (Uint8Array) support which is required by `buffer` v5.x. Use `buffer` v4.x if you require old browser support.'
................................................................................
....................
IE 10.0.0 (Windows 7.0.0): Executed 100 of 100 SUCCESS (8.158 secs / 7.664 secs)
TOTAL: 1300 SUCCESS

LGTM!


Evaluate policies concurrently

This adds concurrency to evaluating configuration policies. This
defaults to two Go routines to provide a performance increase while not
overwhelming the Kubernetes API in resource constrained deployments.
Additionally, it means that the E2E tests will be testing the
concurrency on every test, which is desired.
The number of Go routines can be configured with the
--evaluation-concurrency flag.
Relates:
https://github.com/stolostron/backlog/issues/23546

@JustinKuli is this good to merge now?


Godot crashes with a segfault shortly after being launched on linux (Ubuntu 20.04)

Godot version
3.3.3-stable
System information
Ubuntu 20.04, Intel i5-6200u cpu, intel 520 hd integrated graphics (mesa 21.0.3), Nvidia 940m discreet graphics (nvidia propriteary driver 470), laptop
Issue description
I downloaded the official binary for godot 3.3.3-stable x64 for Linux on my machine, which is running Ubuntu 20.04 (xubuntu flavour-- Xfce desktop environment). When I ran the file, it opened, started reserving some ram, and crashed almost immediately. I ran it from the command line in order to get the trace information, which indicated it had exited with signal 11 (segmentation fault). Not to be deterred, I posted this question in the Q&A forum, and followed these suggestions, all of which still resulted in the same crash (with slightly different backtraces): I built Godot from source (I did, however, clone the 3.x version, which turned out to be 3.4.-beta as opposed to 3.3.3-stable, but I got the same result regardless); I downloaded the proprietary Nvidia driver for my discreet gpu; and I tired running the windows binaries through wine. While wine wasn't able to provide a backtrace, it still crashed in the same way as the native binaries. I have a dual-boot system, and I can confirm that the very same binary runs without issue in windows. I also downloaded the 32bit binary for Linux, and the result was the same.
This is the stack trace for the official 64-bit Linux binaries. I ran the program several times and the trace was identical each time. As you can see, it runs using the integrated intel 520 gpu, with the mesa driver. This was the case both before and after I installed the proprietary driver for the Nvidia card, and I don't know how I might force it to run using the other GPU.
Godot Engine v3.3.3.stable.official.b973f997f - https://godotengine.org
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics 520 (SKL GT2)
OpenGL ES Batching: ON
/usr/lib/x86_64-linux-gnu/libasound.so.2: undefined symbol: snd_dlpath

handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8d94f210" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f4e8d94f210] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8af48b84" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[2] /usr/lib/x86_64-linux-gnu/dri/iris_dri.so(+0xddeb84) [0x7f4e8af48b84] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8b102f7e" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[3] /usr/lib/x86_64-linux-gnu/dri/iris_dri.so(+0xf98f7e) [0x7f4e8b102f7e] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8af23517" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[4] /usr/lib/x86_64-linux-gnu/dri/iris_dri.so(+0xdb9517) [0x7f4e8af23517] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8af24b46" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[5] /usr/lib/x86_64-linux-gnu/dri/iris_dri.so(+0xdbab46) [0x7f4e8af24b46] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8a339b26" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[6] /usr/lib/x86_64-linux-gnu/dri/iris_dri.so(+0x1cfb26) [0x7f4e8a339b26] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x27656e7" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[7] ./Godot_v3.3.3-stable_x11.64() [0x27656e7] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x11af3ae" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[8] ./Godot_v3.3.3-stable_x11.64() [0x11af3ae] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x9966db" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[9] ./Godot_v3.3.3-stable_x11.64() [0x9966db] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x7f4e8d9300b3" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f4e8d9300b3] ()
ERROR: execute: Cannot pipe stream from process running with following arguments '"addr2line" "0x99f5ae" "-e" "/home/dallin/Desktop/programing/Godot/Godot_v3.3.3-stable_x11.64" 2>/dev/null'.
   At: drivers/unix/os_unix.cpp:295.
[11] ./Godot_v3.3.3-stable_x11.64() [0x99f5ae] ()
-- END OF BACKTRACE --
Aborted (core dumped)

Steps to reproduce
In order to reproduce this issue, the particular hardware/software combination that I am using may be required. Of course, on my system, the issue appears each time I try to launch Godot. I'm not sure what useful information I can provide beyond details about my system information, so I'll include as much of that as possible:
The output of glxinfo -B is as follows:
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Intel (0x8086)
    Device: Mesa Intel(R) HD Graphics 520 (SKL GT2) (0x1916)
    Version: 21.0.3
    Accelerated: yes
    Video memory: 3072MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 21.0.3
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 21.0.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

The output of lscpu is as follows:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              2
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           78
Model name:                      Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
Stepping:                        3
CPU MHz:                         500.005
CPU max MHz:                     2800.0000
CPU min MHz:                     400.0000
BogoMIPS:                        4800.00
Virtualization:                  VT-x
L1d cache:                       64 KiB
L1i cache:                       64 KiB
L2 cache:                        512 KiB
L3 cache:                        3 MiB
NUMA node0 CPU(s):               0-3
Vulnerability Itlb multihit:     KVM: Mitigation: Split huge pages
Vulnerability L1tf:              Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable
Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Mitigation; Microcode
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl
                                  xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand
                                  lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap
                                 clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

kernel version (uname -a):
Linux [name]-HP-Pavilion-Notebook 5.4.0-86-generic #97-Ubuntu SMP Fri Sep 17 19:19:40 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

full hardware report (sudo lshw -short)
H/W path       Device      Class          Description
=====================================================
                           system         HP Pavilion Notebook (N5R60UA#ABL)
/0                         bus            80A4
/0/0                       memory         128KiB BIOS
/0/4                       processor      Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
/0/4/6                     memory         64KiB L1 cache
/0/4/7                     memory         512KiB L2 cache
/0/4/8                     memory         3MiB L3 cache
/0/5                       memory         64KiB L1 cache
/0/17                      memory         12GiB System Memory
/0/17/0                    memory         8GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/17/1                    memory         4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/100                     bridge         Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
/0/100/2                   display        Skylake GT2 [HD Graphics 520]
/0/100/4                   generic        Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
/0/100/14                  bus            Sunrise Point-LP USB 3.0 xHCI Controller
/0/100/14/0    usb1        bus            xHCI Host Controller
/0/100/14/0/2              input          USB Optical Mouse
/0/100/14/0/3              multimedia     HP Truevision HD
/0/100/14/0/7              communication  Bluetooth wireless interface
/0/100/14/1    usb2        bus            xHCI Host Controller
/0/100/14.2                generic        Sunrise Point-LP Thermal subsystem
/0/100/16                  communication  Sunrise Point-LP CSME HECI #1
/0/100/17                  storage        Sunrise Point-LP SATA Controller [AHCI mode]
/0/100/1c                  bridge         Sunrise Point-LP PCI Express Root Port #1
/0/100/1c/0                generic        GM108M [GeForce 940M]
/0/100/1c.4                bridge         Sunrise Point-LP PCI Express Root Port #5
/0/100/1c.4/0              generic        RTS522A PCI Express Card Reader
/0/100/1c.5                bridge         Sunrise Point-LP PCI Express Root Port #6
/0/100/1c.5/0  wlo1        network        Wireless 3165
/0/100/1d                  bridge         Sunrise Point-LP PCI Express Root Port #9
/0/100/1d/0    eno1        network        RTL810xE PCI Express Fast Ethernet controller
/0/100/1f                  bridge         Sunrise Point-LP LPC Controller
/0/100/1f.2                memory         Memory controller
/0/100/1f.3                multimedia     Sunrise Point-LP HD Audio
/0/100/1f.4                bus            Sunrise Point-LP SMBus
/0/1                       system         PnP device PNP0c02
/0/2                       system         PnP device PNP0c02
/0/3                       system         PnP device PNP0c02
/0/6                       system         PnP device PNP0b00
/0/7                       generic        PnP device HPQ8001
/0/8                       generic        PnP device SYN1ef2
/0/9                       system         PnP device PNP0c02
/0/a           scsi0       storage
/0/a/0.0.0     /dev/sda    disk           1TB WDC WDS100T2B0A-
/0/a/0.0.0/1   /dev/sda1   volume         259MiB Windows FAT volume
/0/a/0.0.0/2   /dev/sda2   volume         15MiB reserved partition
/0/a/0.0.0/3   /dev/sda3   volume         788GiB Windows NTFS volume
/0/a/0.0.0/4   /dev/sda4   volume         846MiB Windows NTFS volume
/0/a/0.0.0/5   /dev/sda5   volume         920MiB Windows NTFS volume
/0/a/0.0.0/6   /dev/sda6   volume         24GiB Windows NTFS volume
/0/a/0.0.0/7   /dev/sda7   volume         243MiB EFI partition
/0/a/0.0.0/8   /dev/sda8   volume         116GiB EXT4 volume
/0/b           scsi1       storage
/0/b/0.0.0     /dev/cdrom  disk           DVDRW GUD1N
/1                         power          KI04041
/2                         power          OEM Define 5

alternative hardware/software report (inix -Fxz)
System:    Kernel: 5.4.0-86-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Xfce 4.14.2
           Distro: Ubuntu 20.04.3 LTS (Focal Fossa)
Machine:   Type: Laptop System: HP product: HP Pavilion Notebook v: Type1ProductConfigId serial: <filter>
           Mobo: HP model: 80A4 v: 91.1D serial: <filter> UEFI: Insyde v: F.80 date: 06/14/2016
Battery:   ID-1: BAT0 charge: 22.0 Wh condition: 24.3/24.3 Wh (100%) model: Hewlett-Packard Primary status: Unknown
CPU:       Topology: Dual Core model: Intel Core i5-6200U bits: 64 type: MT MCP arch: Skylake rev: 3 L2 cache: 3072 KiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19200
           Speed: 400 MHz min/max: 400/2800 MHz Core speeds (MHz): 1: 400 2: 400 3: 400 4: 400
Graphics:  Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0
           Device-2: NVIDIA GM108M [GeForce 940M] driver: N/A bus ID: 01:00.0
           Display: x11 server: X.Org 1.20.11 driver: intel resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa Intel HD Graphics 520 (SKL GT2) v: 4.6 Mesa 21.0.3 direct render: Yes
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3
           Sound Server: ALSA v: k5.4.0-86-generic
Network:   Device-1: Intel Wireless 3165 driver: iwlwifi v: kernel port: 5040 bus ID: 03:00.0
           IF: wlo1 state: up mac: <filter>
           Device-2: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000
           bus ID: 04:00.0
           IF: eno1 state: down mac: <filter>
Drives:    Local Storage: total: 931.51 GiB used: 517.37 GiB (55.5%)
           ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50 size: 931.51 GiB temp: 27 C
Partition: ID-1: / size: 114.98 GiB used: 66.77 GiB (58.1%) fs: ext4 dev: /dev/sda8
Sensors:   System Temperatures: cpu: 39.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Info:      Processes: 217 Uptime: 2d 5h 34m Memory: 11.54 GiB used: 3.83 GiB (33.1%) Init: systemd runlevel: 5 Compilers:
           gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38

Please contact me if there's additional information I can provide.
Minimal reproduction project
No response

So, update: after making this issue yesterday, I noticed that the inxi -Fxz output listed the driver for the Nvidia card as "N/A". So, I did a few things, including nvidia-xconfig and prime-select nvidia. None of this changed anything, and nvidia-settings wouldn't even open properly, so I called it a day.
Today, after logging in, the software updater indicated that there was a new kernel update, so I downloaded that and restarted. uname -a now gives the following result:
Linux HP-Pavilion-Notebook 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

As far as I can tell, this is the only thing which has changed. inxi -Fxz still shows N/A for the nvidia driver. Godot (official 3.3.3 x64 bin) now launches as expected and the windows binary also runs successfully through wine. It still uses the mesa/intel configuration, although the nvidia-settings panel now opens correctly as well.
I can only surmise that either there was some issue with the specific #-97 kernel build, or that kernel was causing an issue with the nvidia driver that then had knock-on effects. Either way, it seems pretty clear that this issue was isolated to my specific hardware-software situation, since the updated kernel resolved the issue. I'll close this issue now, as if even I am no longer able to reproduce it, it doesn't seem helpful to to have an issue open.

Ah, one last thing. While looking around on the net for "how to force an application to run on discreet GPU linux" I found at least one person who mentioned that they had needed to clear the kernel header files in order for their system to work correctly, after installing a proprietary driver. I didn't feel confident in messing with my kernel, but given that this update presumably refreshed those headers, it's entirely possible that this is what resolved my issue; and, in this case, it would indicate that the core problem was indeed some conflict between the two gpus or with prime.

For the reference, the configuration you have is called "Nvidia Optimus", and is (still nowadays) fairly badly supported on Linux. You should be able to find many guides about how to configure things on Ubuntu 20.04 to use either the integrated or the discrete GPU - with caveat that some of the information might be outdated (e.g. bumblebee workarounds, etc.).


Develop

Coverage decreased (-0.1%) to 85.54% when pulling 5e0dedf629dbb823e283fe31bcdd04fb08b225aa on develop into 60264296ac2437a6f0b2fde30b5d0f6e140bc894 on qa.


Convert PrimUndefined

This converts PrimUndefined to a constant symbol 'undefined. The other choice was (void) but using a constant allows us to know that it came from PS code (or potentially Chez Scheme FFI)

I'm requesting that we use gensym "ps-undefined" (or some name like that) to prevent this symbol from being equal to another one somewhere in the program.


Update LMDB backend functional tests to use generate_block()

Recommitting because it wasn't signed (reinstalled my machine over the weekend). I'll merge once it's green.


Add support for Alt Text Title and newlines in Alt Text

Add support for the Alt Text Title field (altTitle) in addition to the existing Alt Text Description field (altText)
This allows populating the Title field in addition to the Description field in PowerPoint:

Convert newlines to
 such that they show up correctly in alt text
This allows displaying correctly text with newlines, e.g.

rather than

@gitbrent Hi Brent, sorry to urge you. Would you have time to take a look at this PR? It's quite small and self-contained.
As you may see, I only strip newlines from the XML text for the AltText field, so it won't impact on anything else.
This is a great library!

@ptosco - where is this in PowerPoint? I do not see anything other than "Alt Text" on image or chart objects...

@gitbrent In PowerPoint, after exporting from PPtxGenJS with this PR and the altTitle and altText fields populated, right-click on an exported image, choose Format Picture, choose the size widget with 4 arrows, select Alt Text:

@ptosco - i dont see that in the current PowerPoint app. What version are you using?

@gitbrent Ha, right. I am on PowerPoint 2016, which looks like this:
https://facultyhub.chemeketa.edu/aim-for-accessibility/accessible-graphics/alt-text-for-word-and-powerpoint-office-2016/
and indeed has a Title field.
But looking at the online version of PowerPoint it is not there anymore:

The Title attribute is indeed present and documented in the OpenXML SDK as NonVisualDrawingProperties.Title, but apparently latest versions of PowerPoint do not show it in the AltText box anymore.
I still believe it may be a useful tag to programmatically include in a picture, as it is supported by OpenXML.

Closing as not standard/does not target current PowerPoint API.


Tests failing on updating office-ui-fabric-react package

Category

[x] Question
[ ] Bug
[ ] Enhancement

After updating a package "office-ui-fabric-react" from "5.124.0 to "6.128.0", all my tests are failing with following error:
FAIL  ***.test.tsx
● Test suite failed to run
node_modules\office-ui-fabric-react\lib\components\Button\index.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){export * from './BaseButton';
                                                                                ^^^^^^

SyntaxError: Unexpected token export

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/ScriptTransformer.js:289:17)
  at Object.<anonymous> (**.tsx:17:67)
  at Object.<anonymous> (**.test.tsx:7:29)

I'm using framework  Jest, enzyme, sinon. Please let me know why.

@VelinGeorgiev Could you please let me know if you have any idea to resolve this?

Hey @xyz92 , I am not using Fabric UI in my solutions and I do not have a quick solution for you here.
You might have to ignore some Fabric UI stuff to make it work. Have a look here: https://github.com/facebook/jest/issues/2550


Add OsResources to PyBlockExecutor with data test in runtime.

This change is

Codecov Report

Merging #943 (9e2a962) into main (0bdd300) will decrease coverage by 0.34%.
The diff coverage is 19.51%.

@@            Coverage Diff             @@
##             main     #943      +/-   ##
==========================================
- Coverage   68.78%   68.45%   -0.34%
==========================================
  Files          44       44
  Lines        5940     5979      +39
  Branches     5940     5979      +39
==========================================
+ Hits         4086     4093       +7
- Misses       1480     1512      +32
  Partials      374      374

Files
Coverage Δ

crates/blockifier/src/block_context.rs
68.75% <ø> (ø)

crates/blockifier/src/fee/os_resources.rs
100.00% <100.00%> (ø)

...ates/native_blockifier/src/transaction_executor.rs
22.44% <66.66%> (+1.61%)
:arrow_up:

crates/native_blockifier/src/py_block_executor.rs
40.30% <62.50%> (+0.94%)
:arrow_up:

crates/blockifier/src/fee/os_usage.rs
37.25% <0.00%> (-49.11%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Will reopen a reworked PR soon


Fix location of Dockerfile for dependabot

Signed-off-by: Daniel Holbach<EMAIL_ADDRESS>

/lgtm

/lgtm

This command is not picked up by GitHub. Kured does not use prow.


Allow custom disk size

Thank you for the great tool. Currently, it allows us to create the main bootable image of the kernel but doesn't have too much of empty space left for other actions from within Qemu. Please allow zero padded binaries to play with disk drivers from kernel.

I'm not quite sure what you mean. Could you clarify the advantage of zero padded binaries?

I needed to play around with binary sizes a bit for bochs to load my kernel (https://github.com/64/solstice/blob/master/scripts/bochs.sh) so it might be better to support this inside bootimage if possible

Currently bootimage generates a "just enough" disk size. Qemu treats it as a bootable disk and works as expected.
When we develop a file system, we need a place to read and write from. Currently, bootimage neither supports adding custom files to the bootimage other than the kernel, nor supports empty space.
Adding custom file support enables us to load them dynamically from our kernels.
Adding empty space (by padding zeros) enables us to have some space to write from kernel for files and other stuff as a persistent storage.

@64

I needed to play around with binary sizes a bit for bochs to load my kernel (https://github.com/64/solstice/blob/master/scripts/bochs.sh) so it might be better to support this inside bootimage if possible

I never really used bochs, but sounds reasonable.

@vinaychandra Thanks for clarifying!

Adding custom file support enables us to load them dynamically from our kernels.

We had something like this before the rewrite, but it was never finished so we removed it again. I think this would need to be implemented in the bootloader crate, since bootimage does no image generation.

Adding empty space (by padding zeros) enables us to have some space to write from kernel for files and other stuff as a persistent storage.

So QEMU treats the loaded image as a hard disk, which allows a file system driver to write to the image file?

@phil-opp,

I think this would need to be implemented in the bootloader crate
I don't know which crate should be implemented where but my point would be to not autoload these extra files (like we do for kernel) but leave them on the bin file so that we can load them dynamically as required.

So QEMU treats the loaded image as a hard disk, which allows a file system driver to write to the image file?

Yes, that is my understanding. See Image types

I don't know which crate should be implemented where but my point would be to not autoload these extra files (like we do for kernel) but leave them on the bin file so that we can load them dynamically as required.

Sounds reasonable. I think it could be implemented by putting it into a separate ELF section that is not loaded. We could pass the file offset in the boot info to tell the kernel the disk location of the file.

Yes, that is my understanding. See Image types

Interesting!

Note that I'm very busy for the next four weeks, so I won't have time to implement it.


Add Korean

Added ko.json file.

Thanks for your contribution @Tekiter! Now available in version 2.4.0.


general chunked response question

I am looking into getting chunked response using httpbin /stream/10,  it seems that Transfer-Encoding is not sent in the response header, and the question is: how is the body sent?
I am looking for something like what https://en.wikipedia.org/wiki/Chunked_transfer_encoding#Encoded_data said, the response should contain the size of each chunk,  but httpbin does not seem to be sending the size?

It is set.

Thank you @MarloweW
@woosley, I'm sorry I didn't respond sooner. The last ~1 month of my life has been hectic to say the least. :-) I'm afraid I can't help you without more information though. We can reopen this if you can help me reproduce what you're seeing.

I ran the httpbin with the builtin server and used httpie to see the details.
python -m httpbin.core --port 8080
 * Running on http://<IP_ADDRESS>:8080/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [25/Sep/2016 09:34:52] "GET /stream/10 HTTP/1.1" 200 -

it does not seem to have the chunked header
http -v GET http://localhost:8080/stream/10
GET /stream/10 HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: localhost:8080
User-Agent: HTTPie/0.9.2

HTTP/1.0 200 OK
Access-Control-Allow-Credentials: true
Access-Control-Allow-Origin: *
Connection: close
Content-Type: application/json
Date: Sun, 25 Sep 2016 01:34:52 GMT
Server: Werkzeug/0.10.4 Python/2.7.10

this might be a issue with Werkzeug?

So HTTPbin is typically run via Gunicorn (e.g., pip install gunicorn; gunicorn httpbin:app). This will get you the correct TE. For some reason, Werkzeug doesn't do that though if you run it the way you ran it.
You should file a bug against Flask (and then they might tell you to file it against Werkzeug).


typescript improvements using type overrides with setDriver()

What this PR does:
Please consider this PR more of a request for feedback rather than being fully production ready yet. The general idea here is that I'm trying to avoid users needing to use // @ts-ignore or as unknown as Type workarounds, of which we have a few in api.test.ts. Mostly due to accessing connections and collections that are actually stargate-mongoose connections/collections, not plain Mongoose connections/collections
I think the best approach would be to have a StargateMongoose type that overrides a bunch of types on the Mongoose type, along with a generic param to setDriver(). This will enable users to opt in to getting the overridden types using const mongooseInstance = (new mongoose.Mongoose()).setDriver<StargateMongooseDriverOverrides>(StargateMongooseDriver);.
I've made progress, but there are a few points of friction:

src/driver/connection and src/driver/collection import Mongoose connections and collections in a non-standard way, import MongooseCollection from 'mongoose/lib/collection' rather than import mongoose from 'mongoose'; mongoose.Collection. This means that stargate-mongoose Connection and Collection instances are not assignable to values that expect Mongoose Connection and Collection instances. Also means that we can't make StargateMongoose extend Mongoose.
Mongoose's model() functions have fairly complex TypeScript definitions, and we don't want to maintain duplicates.

Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

I'm gonna close this one, it isn't entirely necessary and I don't think we should prioritize this work.


Page focus moves to the top of the page

After using the formatter the focus of the page shifts from where you currently are to the top of the page.
Make it stop. Kthnxbye.

Just wanted to note that I've seen the same happen.
The window slightly shifts focus to the right, which is a bit annoying, especially since I use a hook to run the formatter every time on save.


Getting Fatal error in taking pull from latest master.

Bug report
Title
Getting Fatal error in taking pull from latest master.
Issue Description
Getting Fatal error in taking pull from latest master.
Preconditions
1. framework Version.-master

Expected result
Code should get updated
Actual result

@jyoti-webkul
run composer install


Is there a compressed model of ViTForImageClassification.from_pretrained('google/vit-base-patch16-224-in21k')?

Hi! :)
I wanted to ask, as for LLMs there are several, if there was any compressed model of ViTForImageClassification.from_pretrained('google/vit-base-patch16-224-in21k') (or any other pre-trained model) either quantization, knowledge distillation, pruning, or some other technique.
Thank you so much :)

@PaulaDelgado-Santos that's a transformers ViT, not timm, it's a fairly straightforward model so I imagine many quantization tools could help.


Exposing a port for the node service

Description
I'm attempting to expose a port on the node service to run storybook.
I added a ports key to the docker-compose.yml:
  node:
    build:
      context: ./docker/node
      dockerfile: Dockerfile
      args:
        uid: "${WWWUSER}"
    image: vessel/node
    ports:
      - "${STORYBOOK_PORT}:9001"

I added a variable to .env:
STORYBOOK_PORT=9001

I added the bash wrapper for the env variable in vessel:
export STORYBOOK_PORT=${STORYBOOK_PORT:-9001}

Then I run ./vessel yarn storybook, which is an alias for start-storybook --ci -p 9001 -c ./resources/js/.storybook.
This generates the following output
➜  my-app git:(react_storybook) ✗ ./vessel yarn storybook
yarn run v1.12.3
$ start-storybook --ci -p 9001 -c ./resources/js/.storybook
info @storybook/react v4.1.11
info
info => Loading presets
info => Loading presets
info => Using base config because react-scripts is not installed.
info => Using default webpack setup based on "create-react-app".
info => Using base config because react-scripts is not installed.
webpack built 5e118cecc475ef46d285 in 2828ms
╭────────────────────────────────────────────────╮
│                                                │
│   Storybook 4.1.11 started                     │
│   3.44 s for manager and 3.16 s for preview    │
│                                                │
│   Local:            http://localhost:9001/     │
│   On your network:  http://<IP_ADDRESS>:9001/    │
│                                                │
╰────────────────────────────────────────────────╯

So far that all seems normal, but accessing http://localhost:9001 times out.
Finally, here's the docker ps output:
CONTAINER ID        IMAGE                COMMAND                  CREATED              STATUS              PORTS                                NAMES
90d54f8a544f        vessel/node          "yarn storybook"         22 seconds ago       Up 21 seconds                                            my-app_node_run_2217684cc83a

Notice the frustratingly vacant PORTS section.
I'm sure I'm missing something obvious with docker here, but how can I expose a port from the node container?
OS
My OS is:
[🐧] Linux
Docker
The output of docker version:
➜  ~ docker version
Client:
 Version:           18.09.1-ce
 API version:       1.39
 Go version:        go1.11.4
 Git commit:        4c52b901c6
 Built:             Thu Jan 10 06:51:04 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.09.1-ce
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.11.4
  Git commit:       4c52b901c6
  Built:            Thu Jan 10 06:50:46 2019
  OS/Arch:          linux/amd64
  Experimental:     false

The output of docker-compose version:
➜  ~ docker-compose version
docker-compose version 1.23.2, build unknown
docker-py version: 3.7.0
CPython version: 3.7.2
OpenSSL version: OpenSSL 1.1.1a  20 Nov 2018

Hi!
I tested this out real quick - In the vessel script, Node tasks are all assumed to be one-off commands. So, it uses docker-compose run, which is intended to be for one-off commands and thus does not map ports.
You should be able to do one of the following:
Edit vessel and edit the yarn command to expose the port you'd like (-p $STORYBOOK_PORT:9001):
elif [ "$1" == "yarn" ]; then
        shift 1
        $COMPOSE run --rm \
            -p $STORYBOOK_PORT:9001
            node \
            yarn "$@"

OR
Edit docker-comose.yml and copy the node service (or edit the node service), giving it a command to run on startup, so you can use ./vessel start or ./vessel up -d and it will start the new node service with that port mapping and command.
node:
    build:
      context: ./docker/node
      dockerfile: Dockerfile
      args:
        uid: "${WWWUSER}"
    image: vessel/node
    user: node
    command: yarn storybook
    volumes:
     - .:/var/www/html
    networks:
     - vessel
    ports:
     - "${STORYBOOK_PORT}:9001"

In hindsight, it makes perfect sense docker-compose run doesn't expose the port and I should have dug deeper there. I think I'll just add a storybook service as you suggested. Cheers, and thanks for the quick turnaround on such a big day. Speaking of which, I'm loving MySQL backups so far.

For future googlers, here's what I ended up with:
  storybook:
    build:
      context: ./docker/node
      dockerfile: Dockerfile
      args:
        uid: "${WWWUSER}"
    image: vessel/node
    user: node
    command: bash -c "yarn && yarn storybook"
    volumes:
     - .:/var/www/html
    networks:
     - vessel
    ports:
     - "${STORYBOOK_PORT}:9001"

This will install all yarn dependencies (useful for the first time its run) and start storybook on the port. You'll have to follow the instructions to add environment the variable here or see how I did it above.

Great!!


Actual error information

Mojo::Pg version: any
Perl version: any
Operating system: any

Steps to reproduce the behavior
Any invalid database query raise exception from Mojo::Pg::Database file and it's hard to find actual file with error.
$ cat error.pl
#!/usr/bin/perl

use Mojo::Base -strict;
use Mojo::Pg;

my $pg = Mojo::Pg->new('postgresql://and@/m');

say $pg->db->query('table x')->text;

Expected behavior
$ perl -Ilib/ error.pl
DBD::Pg::st execute failed: ERROR:  relation "x" does not exist
LINE 1: table x
              ^ at error.pl line 8.
$

Actual behavior
$ perl error.pl
DBD::Pg::st execute failed: ERROR:  relation "x" does not exist
LINE 1: table x
              ^ at /usr/local/share/perl/5.22.1/Mojo/Pg/Database.pm line 78, <DATA> line 2125.
$

Patch
diff --git a/lib/Mojo/Pg/Database.pm b/lib/Mojo/Pg/Database.pm
index b0727d4..081ad1f 100644
--- a/lib/Mojo/Pg/Database.pm
+++ b/lib/Mojo/Pg/Database.pm
@@ -75,6 +75,7 @@ sub query {
   $attrs{pg_placeholder_dollaronly} = 1        if delete $self->{dollar_only};
   $attrs{pg_async}                  = PG_ASYNC if $cb;
   my $sth = $self->dbh->prepare_cached($query, \%attrs, 3);
+  $sth->{HandleError} = sub { croak shift } if $sth->{RaiseError};
   $sth->execute(map { _json($_) ? to_json $_->{json} : $_ } @_);

   # Blocking

I definitely :+1: this ... having more accurate error information helps a lot

It's simple and can save some time searching for a broken queries after recent schema update. :) :+1:

Thanks, i went with a slightly different solution.

@kraih thanks.


Logging improvements

Optional input to logger + a small set of defined tags. To start, perhaps

transaction ID
block ID
a boolean specifying whether or not it is a message from libp2p

Stale.


OJS Health Science Theme Does not Work

Hello,
After I configured the journal website in OJS (using Health Science Theme), the journal website doesn't display in Health Science Theme.

Thanks,
Yuan

The Health Science theme should look like this  https://demo.publicknowledgeproject.org/ojs3/demo/index.php/health-sciences. The journal title and homepage image are customizable in the OJS (which I already did). The layout/display should be the same with the above demo site.

This looks like it is a local caching issue for the reporting user's browser.  Visiting https://ojs-staging.princeton.edu/index.php/tj1 in a private tab shows the following:

This is the Health Sciences theme minus the configurations in the above example.

Closing this issue; the theme is configured and displaying appropriately according to the user.  There is an additional issue reported for custom header images not uploading.  I am coordinating a meeting with the stakeholder to review this and open tickets together if needed.


Update load-balancer-outbound-connections.md

Fixed grammatical error.

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

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

Looks good; thanks @rahulbhansali2111.

Looks good; thanks @rahulbhansali2111.


Reporting NonStop platform release build status

Is there a mechanism/location/otherwise for reporting the condition/status of an OpenSSL release build/test on the two NonStop build platforms? I am unsure of the infrastructure to report this. I did check into trying to integrate our system into GitHub but there are security reasons why we cannot do that at this time.
This would apply to 3.0.0 and optionally 1.1.1 (if desired) releases.

@levitte has on his TODO list (and it must be done before 3.0 beta1) to setup a buildbot infrastructure. You could setup a buildbot worker to report status.

@levitte has on his TODO list (and it must be done before 3.0 beta1) to setup a buildbot infrastructure. You could setup a buildbot worker to report status.

Sounds a bit cool, but given that this is an "exotic" platform, I'm not sure I can run a worker (I am pretty sure that I can't - the ia64 platform is stuck on Python2 forever - until the end of 2023 when that variant is at EOL - and virtualnet isn't likely to install cleanly). However, if I can MacGyver a status report via an IRC bbnet structure manually (or well, writing a dedicated IRC notifier is not hard) that might be sufficient. Understand that the build/test time is measured in hours on that box.

FWIW: commit e8dca211b4 passes on TNS/E (ia64) with the PR #13103, which is still in a pending state. The build used egd and no-fips options.

Given that this was on @levitte TODO list for 3.0 beta... any progress? Incorporate some feedback mechanism in our CI/CD structure would be really a good thing. Some details:

I have a Jenkins installation that monitors the OpenSSL repo for changes.
We currently use it for builds based on a specific tag for our definitive builds. There has been some good uptick in 3.0 downloads in the community, so that's a happy place. Our curl and git builds are using 3.0 now (in addition to 1.1).
I can add a monitor on master to kick off a build on a schedule. We would not want to kick off each change simply because change some in faster than the system can realistically build them. So once a day to once a week might not make our sysadmins upset.
In the master build we could send some kind of automated notification back to the OpenSSL team.

The easiest way right now is sending an email to someone's address indicating success/failure of the build until a more formal mechanism is established, like an IRC feed or other asynchronous thing. I currently get one for every build in our system. Would this work as a start for the OpenSSL team? Is there an address we can use?

Other such messages are currently send to @.***

That is openssl-commits at openssl dot org

If that is acceptable, I can instrument it. There is a slight warning on the list page:
_Only GIT and TRAVIS can post here._

So I'm a bit worried about getting flack for posting there.

@levitte @rsbeckerca whats going on with this.  I know we have a buildbot infrastructure now, but it seems nonstop was not incorporated.  Is this still an outstanding to?  If so, whom is it waiting on?

@nhorman I've been waiting on @levitte for some input on how to connect our build system results with some mechanism. As I understand it, buildbot has to run on our system - which I do not think works (happy to try it, but unsure of dependencies). We have a POST API that can query the current builds remotely, if that helps.

@rsbeckerca I would absolutely agree, CI bots on github are (I think) exclusively windows/unix/macos, so we may be out of luck there, bu t I'll let @levitte answer, as he knows better than I (hes in meetings this week, but I'll follow up).
An alternate solution might be for you to query builds periodically, build outside of the CI system, and just open issues if anything breaks, but we can talk about that when @levitte is available

@rsbeckerca I would absolutely agree, CI bots on github are (I think) exclusively windows/unix/macos, so we may be out of luck there, bu t I'll let @levitte answer, as he knows better than I (hes in meetings this week, but I'll follow up).
An alternate solution might be for you to query builds periodically, build outside of the CI system, and just open issues if anything breaks, but we can talk about that when @levitte is available

That alternate solution is actually what we try to do now when our CI system runs.

The buildbot setup we had has been removed, and has (almost) all been moved to github actions.
I do have some ideas on making actions that could ssh to a worker to perform the build and test steps.  That would require an account on that machine, an SSH key (which would be a github actions secret) that can be used to log in on that machine, and knowing what commands to run to build and to test.
I can't promise to do this fast (but perhaps a bit faster than in 3 more years 😉), as my next 2-4 weeks are already filled up with stuff to do.  Reminder ping welcome.

The buildbot setup we had has been removed, and has (almost) all been moved to github actions.
I do have some ideas on making actions that could ssh to a worker to perform the build and test steps. That would require an account on that machine, an SSH key (which would be a github actions secret) that can be used to log in on that machine, and knowing what commands to run to build and to test.
I can't promise to do this fast (but perhaps a bit faster than in 3 more years 😉), as my next 2-4 weeks are already filled up with stuff to do. Reminder ping welcome.

We have a mechanism available now where a GitHub action could go into our website and ask whether a version is available. I don't know whether that will help - it was something the Curl team asked for. The POST is simple to build (one URL) to find out the latest build for, say, OpenSSL 3.3.x.

@rsbeckerca I'm not sure if this is useful to you, but have you tried building https://github.com/actions/runner for nonstop?  I suspect it wont build, but if it did, we could setup a remote CI runner which would certainly smooth this process out.
@levitte will set a reminder to ping you in a few weeks

@rsbeckerca I'm not sure if this is useful to you, but have you tried building https://github.com/actions/runner for nonstop? I suspect it wont build, but if it did, we could setup a remote CI runner which would certainly smooth this process out.

I am having difficulty tracking down how to build a self-hosted running. Running it, sure, but there are no downloads for NonStop. It seems that I would need the actual source code of the application. The runner.git repo is just the actions wrappers.

The pre-requisites for a self-hosted runner for linux  are here https://github.com/actions/runner/blob/main/docs/start/envlinux.md
From what I read the runner repository is a .net application that receives (effectively) web hook requests from github to preform various actions.  to get it up and running, you're not likely to find nonstop binaries, you will have to compile the .net dependencies yourself.  If thats not feasible then this effort is likely DOA, and we will have to find another way to do automated CI on nonstop

adjunct question, can nonstop be emulated in a virtual machine?

@rsbeckerca ping

We cannot yet emulate. There are plans to work in AWS but not available soon. Even then, spinning up a NonStop VM takes longer than a single OpenSSL build/test cycle and has a non-zero license cost.


Markdown Preview is not correctly rendering

The Markdown Preview is not correctly rendering the MyST enhancements.
The following enhanced markdown is ignored and only the content is rendered as plain text.
``` {tip} this is a MyST tip that fails! ```

and
``` {note} this is a MyST tip that fails! ```

The MyST-Markdown extension is enabled since highlighting, intellisense, etc works on the enhanced MyST. However it seems that the enhanced Preview part is either not working or not activated. None of the enhanced MyST markup is previewing as expected.
Desktop:
Windows 11,
VSCodeUserSetup-x64-1.83.1
MyST-Markdown 2.0.0

Screenshot of Edit and Preview panes in VSCode:

Screenshot of Edit and Preview panes in VSCode:

It is working fine on my side on Arch Linux with VS Code 1.88.0 and all extensions up to date:

It also works on my machine; maybe you need to rename the file to end in .myst.md for it to enable?

The op states the problem is in Windows 11, not Arch Linux. I have the same issue on Windows 10. Your test suite in your ci.yml only tests on Ubuntu.

Removing alternative extensions one-by-one, the culprit for me seemed to be by having both of the following extensions enabled:

Markdown Preview Enhanced
MyST-Markdown

Disabling Markdown Preview Enhanced seems to make the problem go away.
Caveats:

You no longer have a button to render the markdown. Instead, you must use ctrl+shift+c
If you use the code fences syntax (:::) for your admonitions rather than backticks (```), you need to enable code_fences in your settings.json

"myst.preview.extensions": [
    "dollarmath",
    "colon_fence"
  ]

Also be sure you don't have any other extensions enabled that might make the output look "odd" (e.g. Dark GitHub Markdown Preview)


Remove offscreen canvas types

Possible fix for #9594
An alternative is to add @types/offscreencanvas as a dependency. I wasn't sure we wanted to do that since we do not have any dependencies right now

I think it might be better to add the @types/offscreencanvas as a dependency then because in the performance part of the docs the offscreencanvas is explained as an option and it would be weird if we document it but typing wont allow it.

I played around with adding the dependency, but could not get everything working with ts 4.4.2 unless library checking was diaabled. Maybe this is a good way for now.


change: split training and serving logic

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

In this PR, the serving seems to disappear, can we find it somewhere else ?

In this PR, the serving seems to disappear, can we find it somewhere else ?

https://github.com/aws/sagemaker-pytorch-serving-container


Use artifacts instead of GHCR for build-kit-

When running the forklow in a PR coming from a fork it is not possible to push to the Github Container Registry since secrets are not available in a "fork run".

Store build-kit- in build-kit.tar and upload as artifact
Download artifact and load docker image from build-kit.tar

tested with

https://github.com/EVerest/everest-core/pull/926


Connecting with a remote cloud

Hello everybody.
I have a particular cloud  running a docker app, and I can connect with it using ssh and the Docker CLI.
Basically I set on CLI a ssh command, my userId and a password to connect.
How can I do that with a method using this client?
Thanks

Feel free to create another issue if you're having problems. If you figure out the remote docker API endpoints your docker CLi command is making, you can use the docs to figure out the DockerClient methods to use. The client methods map one-to-one with the remote docker API endpoints.

This old one was already solve.
Thanks
`public static DockerClient conn() {
DockerClient docker = null;
docker = DefaultDockerClient.builder().uri(URI.create("http:IP")).build();
return docker;
}`


arn

arm binaries pleased
make depend does not work

This will depend a lot on the arm support of the dependent libraries, but I will make a travis job to attempt a build.


seems_monospaced condition triggered too easily in font without Latin characters

Observed behavior
I am building and checking Noto Sans Nushü, a proportional font without Latin characters, and I’m getting the following FAIL:
    * FAIL: On monospaced fonts, the value of post.isFixedPitch must be set to a non-zero value (meaning 'fixed width monospaced'), but got 0 instead. [code: mono-bad-post-isFixedPitch]

    * FAIL: On monospaced fonts, the value of OS/2.panose.bProportion must be set to 9 (proportion: monospaced), but got 0 instead. [code: mono-bad-panose-proportion]

This seems to be triggered by FontBakery comparing widths of ASCII characters (due to https://github.com/googlefonts/fontbakery/pull/2349) with the following code:
https://github.com/googlefonts/fontbakery/blob/547630259405878ebf924ceeb99f05ec8e67ca78/Lib/fontbakery/profiles/shared_conditions.py#L149-L171
However, this font only has space from ASCII u+0020, so that single glyph registers as "100% of ASCII is the same width" and triggers this fail.
Expected behavior
Probably, we need to restrict the seems_monospaced condition a little further. Something like
# if "number of ASCII characters" > 26:
    # check whether characters have matching widths

(26 may not be the correct number, but that would check for the basic Latin alphabet plus at least one more glyph, e.g. the space.)

so, do you think it would be good to have the same 80% threshold but for the most_common_width in cases where latin glyphs are not avaiable?

As a counter are there real fonts that people think of as monospaced that don't have all their glyphs with the same width?

I think it's too easily triggered for font with Latin characters too. I have a font that is "nearly" monospace: https://gitlab.com/drj11/arch8/-/tree/main/quazatron
It has two glyphs (W and M) that are not the same width as all the others. But it would be wrong to mark it as monospace.
It still trips over the the monospace checks. For com.google.fonts/check/monospace:
* FAIL: On monospaced fonts, the value of post.isFixedPitch must be set to a non-zero value (meaning 'fixed width monospaced'), but got 0 instead. [code: mono-bad-post-isFixedPitch]
* FAIL: On monospaced fonts, the value of OS/2.panose.bProportion must be set to 9 (proportion: monospaced), but got 1 instead. [code: mono-bad-panose-proportion]
* WARN: Font is monospaced but 2 glyphs (4.761904761904762%) have a different width. You should check the widths of: ['M', 'at'] [code: mono-outliers]


Fix cli path

Refs: https://github.com/metarhia/metasql/issues/30

Landed in https://github.com/metarhia/metasql/commit/345181592276d071b98f3a14729c40f80b8eda88


Make this package implementation-agnostic

Rather than always loading Node Sass, this now requires users to pass
in either Dart Sass or Node Sass as an option to the plugin.
Closes #184

@nex3 @aexmachina Is this branch nex3:dart-sass in a workable state allowing consumers to pass dart-sass, it's just tests that are failing?
My team wants to get away from node-sass asap and this is currently the blocker.
If there is anything I can help with let me know...

I'm not sure how to pass a Sass implementation in to the tests

@nex3 The tests builds the dummy app (/tests/dummy), could you add the sass implementation option here as well.

@nex3 @aexmachina Is this branch nex3:dart-sass in a workable state allowing consumers to pass dart-sass, it's just tests that are failing?

As far as I know, but I want to emphasize that I'm not an expert in Ember or this package so I can't make any guarantees that I did anything right.

@nex3 The tests builds the dummy app (/tests/dummy), could you add the sass implementation option here as well.

Thanks, done!

@aexmachina Looks like the latest change @nex3 made, adding the sass implementation to ember-cli-build.js, got the tests passing! If that's enough to land this, it would be awesome to get this in.

I think it'd be good for this addon to install sass into the user's package.json. @jbailey4 do you know how to get an addon to do this?

Published v9.0.0 :+1:

However, a lot of people just ember install and expect it to work. I think adding sass to the project is the path of least resistance and offers the least chance of problems. I'm not using this module any more, do you feel like doing a quick PR?

I'm not using this module any more, do you feel like doing a quick PR?

@aexmachina Checkout https://github.com/aexmachina/ember-cli-sass/pull/192


Add option to hide file from "Go to file"

I think it would be useful to have an option to hide a file from "Go to file".
For example, I have a project that contains many subprojects. Each subproject has files that are very similar to the base code in the project. I rarely need to modify the subprojects, so whenever I use "Go to file", it is polluted with files in the subprojects.
I'd like to be able to hide these files in the subprojects from "Go to file", without hiding them from the sidebar.

@garyking you could try to ignore via search.exclude setting, that would exclude it from fulltext searches too though.

Yep I'm aware of that option, but I'm making this suggestion because the search.exclude option is too aggressive for me (hides search results from files that I don't want to hide).


I can't install mods in the dev build

Describe your bug here.
Android
Crash Log or logcat logs (if existing)
I get an error when opening the free play, the editor character, the week editor and etc.

Are you modding a build from source or with Lua?
I am not modding
What is your build target?
Android
Did you edit anything in this build? If so, mention or summarize your changes.
No

can you show us the errors?

wait

needed update devbuild


[CP] Fix pub publish hanging after reading from stdin

commit(s) to merge: 109c317ac12a43d8a25b14bca9805276bf8c84ee
merge instructions: Should merge clean, this a one-liner bumping pub_rev to 96404e0749864c9fbf8b12e1d424e8078809e00a.
What is the issue: New method of reading from stdin caused dart pub publish and dart pub token add to hang after completing. This likely happens because of some lingering event listener on stdin, it seems to not have affected tests because exit() was explicitly called.
What is the fix: Use stdin.readLineSync() from dart:io, instead of trying to read stdin async, which we don't need to do.
Why cherrypick: Affects users running pub publish as they will likely have the process hanging.
Risk: Minor, theprevious method of reading stdin with StreamQueue was introduced just before 2.15.0 branched.
Link to original  issue(s): https://github.com/dart-lang/pub/issues/3219
/cc @kevmoo @mit-mit @whesse @athomas @vsmenon @devoncarew

@jonasfj - thanks for the cherry pick. I see this is a DEPs update. I haven't looked at the diff in the pub repo; is this just getting the fix from the pub repo (or the fix and other unrelated commits)?

This is just the fix.

approved

Merged to beta in c8b50bd835770529f30c6079376c824264a57e2c (2.15.0-268.8.beta).


APP-3031: make auth0.go generic to auth providers

APP-3031
(app PR that incorporates these changes)
Tiny PR that I believe (🤞) includes all the changes needed to auth0.go to make it so that we can cutover the app backend to FusionAuth without any further goutils changes.
I didn't rename auth0.go because it'll destroy the version history on this file if I do a squash and merge (only thing enabled for our repo afaik).
Tested that auth still works in app if I:
0) [local setup] add go replace go.viam.com/utils => ../goutils and then go mod tidy

replace uses of Auth0Config with AuthProviderConfig in 2 places in server/server.go

diff --git a/server/server.go b/server/server.go
index 9b8a5643..29d00820 100644
--- a/server/server.go
+++ b/server/server.go
@@ -299,7 +299,7 @@ type simpleServer struct {
 	unauthenticatedMux    *goji.Mux
 	grpcServer            rpc.Server
 	auth0State            io.Closer
-	auth0Config           uweb.Auth0Config
+	auth0Config           uweb.AuthProviderConfig
 	webTokenKeyProvider   jwks.KeyProvider
 	jWKSKeyProvider       rpc.TokenVerificationKeyProvider
 	sessions              *uweb.SessionManager

and
@@ -640,7 +640,7 @@ func (ss *simpleServer) setupDependencies(ctx context.Context) error {
 		return errors.Wrap(err, "error unmarshaling auth0 data")
 	}

-	ss.auth0Config = uweb.Auth0Config{
+	ss.auth0Config = uweb.AuthProviderConfig{
 		Domain:     m["domain"],
 		ClientID:   m["clientId"],
 		Secret:     m["secret"],

I'll update goutils in app with the changes above once this is ready to merge.

Bringing in the council of Michaels on this one

One thing I'm not clear on is whether I broke the automatic call to Close() by futzing around with utilization of the io.Closer interface. Any ideas? Could produce some resource leaks.

One thing I'm not clear on is whether I broke the automatic call to Close() by futzing around with utilization of the io.Closer interface. Any ideas? Could produce some resource leaks.

As long as the app side still calls Close() like it does here: https://github.com/viamrobotics/app/blob/main/server/server.go#L1691, then I don't think there is anything to be concerned about. Its just refactoring and the Close call will be the same.

Finally gearing up to merge this since we moved forward the testing and doesn't look like we'll need more app changes?


Order of attributes matter to XNode.DeepEquals

The description is misleading: "Two XElement nodes are equal if they have the same tag name, the same set of attributes with the same values" would suggest that order of attributes doesn't matter (since it is a set), but the order does matter.
E.g. following will result in false, i.e. noequivalent XMLs.
XElement xmlTree1 = new XElement("Root",
new XAttribute("Att1", 1),
new XAttribute("Att2", 2)
);
XElement xmlTree2 = new XElement("Root",
new XAttribute("Att2", 2),
new XAttribute("Att1", 1)
);
Console.WriteLine(XNode.DeepEquals(xmlTree1, xmlTree2));
I am not sure how exactly are the attributes compared, but perhaps "two equal length sequences of equal attributes" is closer to truth.
EDIT:
The reference source says that my description of attribute equality is basically accurate, attributes are compared from first to last on both sides and each one must have same name and value:
https://referencesource.microsoft.com/#System.Xml.Linq/System/Xml/Linq/XLinq.cs,d4ee71a752e8b485

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

ID: 5b409bae-8bca-83ad-c127-b43f5c626954
Version Independent ID: bd83ab61-3e42-c0aa-7cd6-b5ee081ac63c
Content: XNode.DeepEquals(XNode, XNode) Method (System.Xml.Linq)
Content Source: xml/System.Xml.Linq/XNode.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Relevant excerpt from Extensible Markup Language (XML) 1.0 (Fifth Edition):

[Definition: The Name-AttValue pairs are referred to as the attribute specifications of the element], [Definition: with the Name in each pair referred to as the attribute name ] and [Definition: the content of the AttValue (the text between the ' or " delimiters) as the attribute value.] Note that the order of attribute specifications in a start-tag or empty-element tag is not significant.


Unable to map through types and assign to a field

Passing in a mapped array of ArrayMembers causes this error:
  Source provides no match for required element at position 0 in target.

Whereas using a literal is fine
import quote from "./quote";
import ticker from "./ticker";

const allComponents = [quote, ticker];

const mappedArray = allComponents.map(component =>
  defineArrayMember({
    name: component.name,
    type: component.name,
  }),
);

const normalArray = [ // <-- working fine
  defineArrayMember({
    name: quote.name,
    type: quote.name,
  }),
  defineArrayMember({
    name: ticker.name,
    type: ticker.name,
  }),
] as const;

export const allComponentsField = defineField({
  name: "components",
  title: "Components",
  type: "array",

  of: [...normalArray],
  // of: [...mappedArray], <-- Throws error
});

Changing:
of: [TMemberDefinition, ...TMemberDefinition[]]

to:
of: TMemberDefinition[]

in the array type fixes this, but there are probably knock on negative effects to making this change.

So of requires a tuple of at least length one, because sanity requires this. mappedArray is just an array as opposed to normalArray being a tuple. Having the types match the reality as well as possible is a good idea. It could be argued that this library's goal is to create the derived sanity value types, not add new restrictions. I think it's worth it to do this, because having typescript enforce the same things runtime will enforce will correct issues before you even run sanity.
That being said, I'm sure you'll run into arrays/tuples again somewhere, so here's some issues I'm seeing with your current implementation:

Is allComponents being typed as a tuple or an array? Not sure how that works.

Mapping tuples has issues in typescript, although there are workarounds. Making of require an array instead of a tuple would avoid these issues, but the issue isn't that the library is typed wrong but, rather, that typescript doesn't have a good solution for this. I'd prefer people use the workaround rather than changing the library to a less correct type.

I'm going to close this, as it's not an issue with the library but rather a difficulty with typescript.

Thanks for the help. A messy solution for reference if needed.
declare global {
  interface Array<T> {
    map<U>(
      callbackfn: (value: T, index: number, tuple: T[] | [T]) => U,
      thisArg?: any,
    ): { [K in keyof this]: U };
  }
}

type DeepMutable<T> = { -readonly [P in keyof T]: DeepMutable<T[P]> };
const allComponents = [quote, ticker] as const;

const mutableComponents = allComponents as DeepMutable<typeof allComponents>;

const mappedArray = mutableComponents.map(component => {
  return defineArrayMember({
    name: component.name,
    type: component.name,
  });
});

export const allComponentsField = defineField({
  name: "components",
  title: "Components",
  type: "array",
  of: mappedArray,
});


What batch_size did you use?

Hello,
You didn't mention batch size in the ReadMe so I assume you're using batch size as 1. Is that correct?
Thanks!

@dev-kodeplus yes, the batch size 1 is used.

there is not a perfect clear guide how to run this project? will you explain

@usamaahme Please refer to README.md for a complete installation and usage guide, if you have further questions. Please create a separate issue.


wrong ip assigned

Hi,
i am running registrator using the following form:
docker run -d --name=registrator  --volume=/var/run/docker.sock:/tmp/docker.sock --net=host -h $HOSTNAME  gliderlabs/registrator:latest  consul://<IP_ADDRESS>:8500

When i resolve addresses from that host - i get the internal ip addresses of the container instead of the host ip address.
Any workaround for this bug?

thanks!
this will only work for a stand alone docker engine. not for swarm. am i right?

I'm not a swarm user sorry


[Bug] Cannot locate symbol "_Unwind_GetTextRelBase" - x64 emulator

An application using the library crashes on an x64 emulator with the following error:
java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_Unwind_GetTextRelBase" referenced by "/data/app/.../base.apk!/lib/x86_64/libhftokenizer.so"...

On examining the libhftokenizer.so carefully (with ldd), we notice the following dependency:
$> ldd libhftokenizer.so
        linux-vdso.so.1 (0x00007ffeac3b8000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff4a44db000)
        /lib64/ld-linux-x86-64.so.2 (0x00007ff4a4ada000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff4a43fc000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ff4a43dc000)

The symbol seems to originate from libgcc_s.so which is a shared runtime library for GCC. (see this answer on SO)
Removal of libgcc_s.so as a dependency OR packaging libhftokenizer as a static library should solve the issue

References:

https://stackoverflow.com/a/76095789/13546426
https://stackoverflow.com/a/58565529/13546426

The issue was discovered by @greenrobot

Converting a static library may result in the application not loading the jniLibs/<arch>/libhftokenizer.a as Android does not package the static libraries in the APK. A possible workaround could be downloading the static libraries from a remote source or copying them to the local file-system from the assets folder.


Iroh fails when running through an outbound HTTPS proxy

this user is running a proxy that forces outbound HTTP traffic onto a port that isn't 443
router blocks outbound traffic on 443, it should follow redirects, apparently in the way recent versions of reqwest do
log: https://gist.github.com/zicklag/d6e2fb694650cabcb556258f30dd7405
from the user: "it looks like it fails with a couple timeouts, which is usually what happens when something tries to go outbound on 443 and the router blocks it."

Further background, the most common way to configure the http(s) proxy is through environment variables: http_proxy, https_proxy, no_proxy, or their uppercase variants.

This appears to be the function in question. Since you're using hyper directly, instead of reqwest or ureq or some other http client library that already supports proxies, it might mean a bit more work for us. I think maybe the best route would be to try and lift the proxy logic from reqwest if possible. I'm pretty sure it also uses hyper.

https://github.com/siketyan/hyper-proxy2 looks like it should be easy to use


fix(openspec,common): Fix wrong import of OS3Example

Closes: #1349

:tada: This PR is included in version 6.41.1 :tada:
The release is available on:

v6.41.1
GitHub release

Your semantic-release bot :package::rocket:


[FIX]Fix complex type meta schema in information database

Proposed changes
link : https://github.com/apache/doris/pull/27203
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Undo stack is lost on file name change

VSCode Version: 1.24.1
OS Version: Windows 10

Steps to Reproduce:

Make changes to a file
Rename file
Cannot use Ctrl+Z to undo changes made any more

Does this issue occur when all extensions are disabled?: Yes

I see the proposed dups, but except the 50570 I would never have considered the others related.

I believe this is covered by https://github.com/Microsoft/vscode/issues/50801