Streama fails to use MySQL Database

Issue description
I am trying to test run Streama using MySQL Database as back end. I have correctly (I believe) setup application.yml to use a different port and MySQL as data source. While the port change takes effect, Streama however still uses the the inbuil H2 database instead of MySQL
Steps to Reproduce
Create Streama database on MySQL Server backend
Configure application.yml (actual content included in ENVIRONMENT INFORMATION below)
Run Streama (java -jar streama-1.6.0-FINAL.war)
Expected Behaviour
Streama is expected to connect to MySQL , create requisite tables and use Database specified in application.yml
Actual Behaviour
Streama uses in built H2 Database (evidenced by creation of streama.mv.db & streama.trace.db). No tables are created in the MySQL Database specified in application.yml
Environment Information
Operating System: Ubuntu Server 18.10 x64 Server running MySQL Server 5.7.24
Streama version: v1.6.0 FINAL
Custom streama build, describe customizations or provide link to fork (If Applicable):
application.yml Content
environments:
production:
dataSource:
        #driverClassName: 'com.mysql.jdbc.Driver'
        driverClassName: 'com.mysql.cj.jdbc.Driver'

        #url: jdbc:mysql://localhost/streama
        url: jdbc:mysql://localhost/streama?useLegacyDatetimeCode=false&serverTimezone=UTC&useSSL=false

        username: admin
        password: admin

server:
port: 6789
Container Version (If Applicable): /

Try to use this
environments:      production:         dataSource:             dbCreate: update             driverClassName:  'com.mysql.cj.jdbc.Driver'             url: jdbc:mysql://localhost:----insert-port---/streamadb?useLegacyDatetimeCode=false&serverTimezone=UTC&useSSL=false             username: streamausername             password: streampass

Hi @EchoDev thanks for your response. Got around to trying this both on the 1.6.0 and 1.6.1. Doesn't work. Streama still doesn't use MySQL even though it runs on the port specified in application.yml. I tried both http://localhost:mysqlPort and http://server-ip:mysqlPort.

Can you tell us how your set up looks like? In what folder do you have the application.yml, what commands are you using, what is the console output etc. I can compare to what it looks like on my end.

Streama 1.6.1.war and application.yml are both in /root.
I'm running streama by issuing the following command
java -jar streama-1.6.1.war

can you paste the contents of your entire application.yml pls?

environments: production: dataSource: dbCreate: update driverClassName: 'com.mysql.cj.jdbc.Driver' url: jdbc:mysql://localhost:----insert-port---/streamadb?useLegacyDatetimeCode=false&serverTimezone=UTC&useSSL=false username: mysqlusername password: mysqluserpass

Bump


Update main.ts

Experimental, untested, but will possibly remedy the issue described in Issue #40

@djmango Please review

I've run a workflow to package the plugin with this code. However, this behavior change should be a setting, not a change in default. Please update accordingly and I'm happy to merge!

Awesome, thanks for your reply! Can you explain your response a bit? I didn't quite understand what you meant.

You're welcome to make the change with your own copy of the plugin, but the default behavior (what people have come to expect from the plugin) should not be changed. Happy to merge this into the distributed plugin if you made it a setting though.

@djmango Excellent, that makes sense. I've made the changes, let me know if they're good-to-go!
FYI I haven't tested, because I don't have the local workflow set up yet for testing custom Obsidian plugins. Will set up the workflow for myself in the future.

@djmango Fixing error, one moment

That's the purpose of the workflow. It auto packages the application for you to test. It seems to have failed
https://github.com/djmango/obsidian-transcription/actions/runs/7722208435/job/21050070060?pr=41
The commands to test it yourself are also in the YAML

@djmango K, I've pushed the fix, let's see if the workflow is happy with it

LGTM

Woot woot! +1 and thank you!

@djmango How long until the changes are live in the Obsidian Community Plugin update menu?

Should be up


JOSS paper statement of need: Algorithms implemented

JOSS paper statement of need should cite markets algorithms implemented.

Fixed in commit https://github.com/gus0k/pymarket/commit/2f8db92010d5f9407a72941788500351e92cbe81


ZXingScannerFragment not working

I've tried to use ZXingScannerFragment to embed the scanner into my activity, but it doesn't recognize any barcodes. I'm using Xamarin.Android for this project.
I've also downloaded Sample.Android project from here and installed ZXing.Net.Mobile 2.2.9 from NuGet into it. Normal scanning works perfectly, but when I tap Fragment Scaner button, scanner shows but doesn't recognize a 1D or 2D barcode.
I've even tried to PauseAnalysis / ResumeAnalysis to no effect.
I'm at a loss, since ZXingScannerFragment is using the same underlying engine.
Any help would be appreciated very highly.
My environment
Windows 10 Enterprise x64 : Version 10.0.15063 Build 15063
Microsoft Visual Studio Enterprise 2015 : Version 14.0.25431.01 Update 3
Microsoft .NET Framework : Version 4.7.02046
Xamarin : <IP_ADDRESS>7 (4a8abec)
Xamarin.Android : <IP_ADDRESS> (0cd0214)
Java : jdk1.8.0_112
Andorid SDK up to date
P.S. : If it makes any difference, I'm testing on a Samsung Galaxy Note 3 with Android 5.0.

I'm experiencing the same issue, oddly running continuous scanning in sample app makes scanner fragment in my app work...

I having same issue and I got it fixed...it's due to the delay of commit of fragment transaction.
Add SupportFragmentManager.ExecutePendingTransactions(); just after commit to forcefully do this.

@lijo007 Thank you, excellent finding. I've made the sample work using your solution. Now I can make my app work too.
Great job !

@lijo007 Thanks a million! Saved my day


{Storage} Add example for storage file upload-batch

Description

Fix #6310
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

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

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Storage


Add some TypeScript

Add support to babel for transpiling .ts
Convert main govuk-react exports to .ts for better autocompletion/hinting

Codecov Report

Merging #836 (e4dc9a2) into master (c24c67d) will not change coverage.
The diff coverage is n/a.

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

@@           Coverage Diff           @@
##           master     #836   +/-   ##
=======================================
  Coverage   95.90%   95.90%
=======================================
  Files         119      119
  Lines         854      854
  Branches      237      237
=======================================
  Hits          819      819
  Misses         33       33
  Partials        2        2

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 c24c67d...7cf64c0. Read the comment docs.


SetuptoolsDeprecationWarning: setup.py install is deprecated.

When trying to install with
python .\setup.py install

I get the warning:  SetuptoolsDeprecationWarning: setup.py install is deprecated.

pysunspec needs maintenance.
Tom Tansy
SunSpec Alliance
831-227-1073
@.***
On Tue, Jan 2, 2024 at 6:49 AM tk1 @.***> wrote:

When trying to install with
python .\setup.py install
I get the warning: SetuptoolsDeprecationWarning: setup.py install is
deprecated.
—
Reply to this email directly, view it on GitHub
https://github.com/sunspec/pysunspec2/issues/86, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA37CSXOCSHQ5BXO2MV25ALYMQM7XAVCNFSM6AAAAABBKEKEYKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DENJSGYZDKMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi Tom,
It seems like the 'python setup.py install' has been deprecated. Here's the article talking about it: https://packaging.python.org/en/latest/discussions/setup-py-deprecated/
I believe we just need to change the Readme on github to state 'Use pip install pysunspec2' for installation. That's the recommended command for installation and it works fine. I will make that change.
Thanks,
Kudrat
Kudrat Kaur
@.***
SunSpec Alliance
On Tuesday, January 2nd 2024, 9:35:18 AM @.*** @.***> wrote:
pysunspec needs maintenance.
Tom Tansy
SunSpec Alliance
831-227-1073
@.***
On Tue, Jan 2, 2024 at 6:49 AM tk1 @.***> wrote:
When trying to install with
python .\setup.py install
I get the warning:  SetuptoolsDeprecationWarning: setup.py install is deprecated.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
Desk tracking: [DESK-3b2n-2nqmh]

Sounds good Kudrat. Thanks for making the change.
Let's make a plan for supporting this project. Should we co-opt the Modbus
group once per month?
Tom Tansy
SunSpec Alliance
831-227-1073
@.***
On Wed, Jan 3, 2024 at 11:44 AM SunSpec Support @.***> wrote:

Hi Tom,
It seems like the 'python setup.py install' has been deprecated. Here's
the article talking about it:
https://packaging.python.org/en/latest/discussions/setup-py-deprecated/
I believe we just need to change the Readme on github to state 'Use pip
install pysunspec2' for installation. That's the recommended command for
installation and it works fine. I will make that change.
Thanks,
Kudrat
Kudrat Kaur
@.***
SunSpec Alliance
On Tuesday, January 2nd 2024, 9:35:18 AM @.*** @.***>
wrote:
pysunspec needs maintenance.
Tom Tansy
SunSpec Alliance
831-227-1073
@.***
On Tue, Jan 2, 2024 at 6:49 AM tk1 @.***> wrote:
When trying to install with
python .\setup.py install
I get the warning: SetuptoolsDeprecationWarning: setup.py install is
deprecated.
—
Reply to this email directly, view it on GitHub
https://github.com/sunspec/pysunspec2/issues/86, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA37CSXOCSHQ5BXO2MV25ALYMQM7XAVCNFSM6AAAAABBKEKEYKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DENJSGYZDKMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>
Desk tracking: [DESK-3b2n-2nqmh]
[image: read tracking] [image: read tracking]
[image: read tracking]

Hi Tom, It seems like the 'python setup.py install' has been deprecated.

I installed it via pip, but my intention was to say that the documentation is outdated.

Hi @tk1 Thanks for pointing that out. We've updated the Readme to install using pip and mentioned the python setup.py install is deprecated.


pass arguments to the release process correctly

Pull Request Test Coverage Report for Build #369

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.796%

Totals

Change from base Build #368:
0.0%

Covered Lines:
489

Relevant Lines:
490

💛  - Coveralls


EBS-149 Textarea component improvements

breaking changes to Textarea
removed:

onInput since onChange is clearer and matches most other components
required is now optional to match InputWrapper usage, I think we should change it later to required since it's weird to mark optional fields with * IMO.

added:

id, name, defaultValue, iconName, onChange, onBlur, validateOnChange and validateOnBlur.

now uses the ValidationContext and InputWrapper.

@Weetbix I check the css seems similar now


Cannot get the speaker to work in ESP-IDF

I am trying to port the provided firmware to ESP-IDF but it seems like I am not able to get the speaker to work.
First off, I wanted to make sure if the code is alright, so I recreated the circuit (or let's say the important parts of the circuit) on a breadboard with ESP32-S3-DevkitC at its core, and seems like the speaker works just fine when using the wired up circuit. But when I flash the same binary onto the custom PC, for some reason the speaker does not play the sound. I noticed that there is a variable defined without any documentation in the original firmware called SPEAKER_EN, and it is set to output high, but never used. Does this have anything to do with the speaker not playing what's been written on I2S TX channel when the PCB is used?

Not sure if you got this working, but I was able to get the speaker working using ESPHome using the following pins:

GPIO12: DOUT (Data Out) signal for DAC
GPIO13: WS (Word Select) signal
GPIO18: BCLK (Bit Clock) signal
GPIO21: set on to energize the DAC


wlr/taskbar on multi-monitor: icons not displayed for apps launched before waybar

Wayland compositor: sway (v 1.9) or Hyprland (0.41.1) [error happens with both]
Waybar version: 0.10.3
I have 2 monitors (output LVDS-1 and HDMI-A-1), and the exact same waybar configuration is applied to both. Specifically for wlr/taskbar:

wlr/taskbar config
    "wlr/taskbar": {
      "format": "{icon}",
      "icon-size": 24,
      "on-click": "activate",
      "on-click-middle": "close",
    },

Observations:

If waybar has already started, all new apps that I open will display the correct icon on any of the waybar taskbars on both monitors.
If waybar starts later, with an app already open, the icon is only displayed correctly in one of the taskbars (the one in HDMI-A-1), and not on the other (there is an empty space with no icon, though it works when clicked and tooltips are displayed).

Logs:
By using log-level trace, I see that icons are found and "Loaded" for all open applications, but only are "now visible" on the HDMI-A-1 output. When the icon is "loaded" for the application on LVDS-1, it isn't "now visible". See examples below:
Example on HDMI-A-1:
Task (4) overwriting app_id 'unknown' with 'firefox-esr'
Task (4) Mozilla Firefox Private Browsing [firefox-esr] <amif> Loaded icon 'firefox-esr'
Task (4) Mozilla Firefox Private Browsing [firefox-esr] <amif> entered output 0x5d274d223ef0
Task (4) Mozilla Firefox Private Browsing [firefox-esr] <amif> now visible on HDMI-A-1
Task (4) Mozilla Firefox Private Browsing [firefox-esr] <amif> changed

Example on LVDS-1:
Task (7) overwriting app_id 'unknown' with 'thunar'
Task (7) waybar - Thunar [thunar] <amif> Loaded icon 'org.xfce.thunar'
Task (7) waybar - Thunar [thunar] <amif> entered output 0x5d274d2bc930
Task (7) waybar - Thunar [thunar] <amif> changed

As you can see, on LVDS-1, the line "now visible on LVDS-1" is missing. I think this could help find the issue.
I have attached the trace logs in case it is helpful.
Operations performed:

Run sway with 2 apps open on each monitor (4 apps in total, foot and thunar on LVDS-1, firefox and geany on HDMI-A-1).
Start waybar.
Move the cursor to the LVDS-1 monitor (on thunar).
Open a new foot terminal (icon is correctly rendered for this app on LVDS-1).
Kill waybar.

I will provide any information required to help understand and fix this bug.
waybar.log

I think Task (7) is not the correct task we should be looking at.
My (limited) understanding of wlr/taskbar is that all apps have a Task object representation in the module regardless of whether the app is currently on the module's output or not. There is a module instance for each output. So there are actually two representations for thunar, one is a Task object in the taskbar module on LVDS-1, and one is a Task object in the taskbar module on HDMI-A-1.
Task (7) is thunar's representation on HDMI-A-1's wlr/taskbar module. Task (3) is thunar's representation on LVDS-1.
When the module is rendered (or when apps are added, moved or removed), the handle_output_enter/handle_output_leave run in each module. But using tbar_->show_output(output) the method checks if the app's output matches the module's output and skips the rest if not. THAT explains why you don't see a "now visible on" line. Looking at Task (3):
[2024-06-16 16:30:47.551] [debug] Task (3) setting app_id to unknown
[2024-06-16 16:30:47.553] [debug] Task (3) overwriting app_id 'unknown' with 'thunar'
[2024-06-16 16:30:47.553] [debug] Couldn't find icon for thunar
[2024-06-16 16:30:47.553] [debug] Task (3) waybar - Thunar [thunar] <amif> entered output 0x5d274d2bc930
[2024-06-16 16:30:47.553] [debug] Task (3) waybar - Thunar [thunar] <amif> now visible on LVDS-1
[2024-06-16 16:30:47.553] [debug] Task (3) waybar - Thunar [thunar] <amif> changed
[2024-06-16 16:30:48.770] [debug] Task (3) waybar - Thunar [thunar] <Amif> changed
[2024-06-16 16:30:50.426] [debug] Task (3) waybar - Thunar [thunar] <Amif> changed
[2024-06-16 16:30:50.471] [debug] Task (3) waybar - Thunar [thunar] <amif> changed

I think [2024-06-16 16:30:47.553] [debug] Couldn't find icon for thunar is the interesting part. The module will never try to load an icon again for a Task it already knows.
Why that again is happening, I'm not sure at this point.
I can reproduce the issue, though.

Apparently, the icon theme can be empty, so the for loop in handle_app_id isn't entered. This means that the constructor for Taskbar has not run, but the Tasks already get their app_ids/icons. Possibly something around the static methods, but with my limited knowledge of C++ that might be complete nonsense. The following seems to work around the issue:
diff --git a/src/modules/wlr/taskbar.cpp b/src/modules/wlr/taskbar.cpp
index 41d46748..bf634192 100644
--- a/src/modules/wlr/taskbar.cpp
+++ b/src/modules/wlr/taskbar.cpp
@@ -434,10 +434,16 @@ void Task::handle_app_id(const char *app_id) {

   int icon_size = config_["icon-size"].isInt() ? config_["icon-size"].asInt() : 16;
   bool found = false;
-  for (auto &icon_theme : tbar_->icon_themes()) {
-    if (image_load_icon(icon_, icon_theme, app_info_, icon_size)) {
+  if (tbar_->icon_themes().size() == 0) {
+    if (image_load_icon(icon_, Gtk::IconTheme::get_default(), app_info_, icon_size)) {
       found = true;
-      break;
+    }
+  } else {
+    for (auto &icon_theme : tbar_->icon_themes()) {
+      if (image_load_icon(icon_, icon_theme, app_info_, icon_size)) {
+        found = true;
+        break;
+      }
     }
   }

But of course it has the disadvantage that any icon themes specified in the config would be ignored on that particular screen, for existing tasks. That shouldn't be the solution. :P

Workaround (a different one) is now in the master branch via PR #3393 . @abc-nix  Any chance you can check if it solves the issue for you?

Fantastic, @RobertMueller2. It works. I can only test on sway right now, but it works and fixes the issue on multi-monitors (at least on my system).
Many thanks.


Official example throws error

I'm using Node v0.11.14, Fedora 64 bits with sox installed:
events.js:85
throw er; // Unhandled 'error' event
^
TypeError: Invalid non-string/buffer chunk
at chunkInvalid (/home/q2dg/node_modules/baudio/node_modules/readable-stream/lib/_stream_readable.js:416:10)
at readableAddChunk (/home/q2dg/node_modules/baudio/node_modules/readable-stream/lib/_stream_readable.js:172:12)
at B.Readable.push (/home/q2dg/node_modules/baudio/node_modules/readable-stream/lib/_stream_readable.js:162:10)
at Object. (/home/q2dg/borrar2:22:3)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:124:16)

That totally simplifies baudio, it's a bit more elegant that way... I was playing with plucky to make it work.
I manager to patch in this ....

var channels = [];
var b = baudio({ rate : 44100 }, function(t) {
    var sum = 0;
    for (var i = 0; i < channels.length; i++) {
        sum += channels[i](t);
    }

    return sum / channels.length;
});

and then instead of b.push use channels.push.
BUT plucky itself is a weird toy project it seems.
it looks like you can arbitrarily start any one of the sound track functions, which get a handle that encompasses the start time, and then you can skip to the next track, which keeps allocating  more handles over time...
I think originally he intended to allow tracks to start at time Ts and then be "silenced" and reactivated at a future - Tn  with  and Tn - Ts  time had passed, respecting the nature of the tune, BUT... none of the examples look like they use that, and instead leak memory py fulling up the "playing" array ... I think... I'm futzing with it.


[Bug]: Error is not displayed when function is with same name

Is there an existing issue for this?

[X] I have searched the existing issues

Description
JSfunction with same name should throw error

Steps To Reproduce

Add two jsfunction with same name, it should throw error- This is not working

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
cloud

@ohansFavour could you please investigate why a lint error isn't being thrown?

@bharath31 this is a regression caused by the linting of individual properties of the JSObject, instead of the Object as a whole.

@ohansFavour could you please run an RCA and fix this in the upcoming sprints?

@bharath31 @ohansFavour I want to work on this. Could you please help me regarding, where is the code for linting in codebase.


"visibility settings" error in core when building via CocoaPods

Hi Guys,
After updating to Realm 2.3.0 (was 2.1.2), I get the following warning in Xcode:
direct access in function 'realm::SharedGroup::SharedGroup(realm::Replication&, realm::SharedGroupOptions)' from file '/Users/xxxx/Documents/Projects/ImageScape/Pods/Realm/core/librealm-ios.a(client_file_access_cache-iphonesimulator.o)' to global weak symbol 'realm::util::InterprocessMutex::initialize_statics()' from file '/Users/xxxx/Library/Developer/Xcode/DerivedData/ImageScape-hetxuiirverpbbdrqeqlutdnufdo/Build/Products/Debug-iphonesimulator/Realm/libRealm.a(shared_realm.o)' means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.

As far as I can check everything works as expected, but the warning isn't nice of course. Thanks!
Script info:
ProductName:	Mac OS X
ProductVersion:	10.12.2
BuildVersion:	16C67

/Applications/Xcode.app/Contents/Developer
Xcode 8.2.1
Build version 8C1002

/usr/local/bin/pod
1.0.0
Realm (2.3.0)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16)

/usr/local/bin/carthage
0.18.1
(not in use here)

/usr/bin/git
git version 2.10.1 (Apple Git-78)

Thanks for reporting this, @yuggieg! Would you be able to provide a sample project that reproduces the issue so we can better debug this? Cheers! :-)

No need to send us a repro case @yuggieg, we can see this too. This is a similar linker warning as realm/realm-object-store/issues/281 and https://github.com/realm/realm-cocoa/issues/4438. I thought we had updated our upstream projects to use the same visibility settings, but evidently that's not the case. I'm looking into this.

Hi! Same problem on 2.4.2

@jpsim ^

install realm by pod could cause it on 2.4.2 and wouldn't appear install by static framework

I have the same warning since several versions before.

The same warning in the version 2.7.0.

Yes, this is still a problem. I haven't found a reliable way to avoid it in all cases, however.

The problem still exists in 2.8.0. Thanks!

Mark. The problem still exists in 2.8.0. (Xcode 8.2.1     CocoaPods 1.2.1)

Correct, this problem still exists, under certain compiler conditions with CocoaPods. If anyone has suggestions for a proper fix that works under all circumstances, please let me know

The problem still exists in 2.9.1. Thanks!

The problem still exists in 2.10.0. Thanks!

The problem still exists in 2.10.0.

Still happening in 2.10.1

Still happening in 2.10.2


Error Saving Image on Page

Hello,
I'm receiving "error saving image on page" for each image of a pdf file, but cannot see why.
See layout_scanner.py line 169

Thanks for posting this, and sorry I couldn't reply sooner.
Could you link or send me the pdf file(s) in question?
It would help to understand the problem.

Hello, I am also getting the same error. Can you help me with this? I have attached the code below.
pdftotext.txt


Replaced qualified featherbed.Client with import in docs

Current coverage is 63.35% (diff: 100%)

Merging #46 into master will not change coverage

@@             master        #46   diff @@
==========================================
  Files             9          9
  Lines           262        262
  Methods         259        259
  Messages          0          0
  Branches          3          3
==========================================
  Hits            166        166
  Misses           96         96
  Partials          0          0

Powered by Codecov. Last update bdecef0...3b6bc48


Error building on windows

I'm new to React development, so I could be making a noob mistake, but I get this error when checking out a fresh copy of the master branch and running yarn build.
Cannot read property 'name' of null
$ node -v
v8.11.4

$ npm -v
6.9.0

Full output -
$ yarn build
yarn run v1.17.3
$ grafana-toolkit plugin:build
Running Build plugin task
√ Cleaning
√ Preparing
√ Prettier check
√ Linting
 PASS  src/module.test.ts

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.841s, estimated 2s
Ran all test suites with tests matching "".
√ Running tests
× Cannot read property 'name' of null
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I updated Node and Npm but still get the error -
$ node -v
v10.16.0

$ npm -v
6.10.2

@jdbranham -- can you tell me anything else about your environment?  This is what I see:

It seems to be Windows specific; I'm able to build in a Linux shell -
Probably a path separator problem somewhere...

@ryantxu - unrelated question... which OS/shell are you running? I like the git branch indicator in your prompt.

I'll try to test it better on windows -- yes, most likely a path separator issue with the new @grafana/toolkit this is using

Yeah the problem is in the grafana\toolkit\src\config\webpack.plugin.config.js file line 55
var idx = id.indexOf('/src/');
so a local workaround to make it work in windows would be to change it to:
var idx = id.indexOf('\\src\\');

See https://github.com/grafana/grafana/issues/18294

@jdbranham -- can you pull from master and try again?  toolkit 6.4.0-alpha.42 should work on windows

Yep - works now!


Using Google Sign-in for authentication

Hi, my app uses Google Sign-in through Firebase and from what I've read, it handles the OAuth system, but how could I use your plugin with it?

This plugin is only about google drive.


[BUG] Gradle dependencies for 1.3.6 build tools are missing

What is the bug?
Plugins depending on 1.3.6 are failing to build
How can one reproduce the bug?
Try and build a plugin
What is the expected behavior?
Plugin should successfully build
What is your host/environment?
Github actions runner  using actions/setup-java@v1
Do you have any additional context?
> Could not resolve all artifacts for configuration ':classpath'.
   > Could not find com.avast.gradle:gradle-docker-compose-plugin:0.12.1.
     Searched in the following locations:
       - file:/home/runner/.m2/repository/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://aws.oss.sonatype.org/content/repositories/snapshots/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://repo.maven.apache.org/maven2/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
       - https://plugins.gradle.org/m2/com/avast/gradle/gradle-docker-compose-plugin/0.12.1/gradle-docker-compose-plugin-0.12.1.pom
     Required by:
         project : > org.opensearch.gradle:build-tools:1.3.6
   > Could not find com.netflix.nebula:nebula-core:3.0.0.
     Searched in the following locations:
       - file:/home/runner/.m2/repository/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://aws.oss.sonatype.org/content/repositories/snapshots/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://repo.maven.apache.org/maven2/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
       - https://plugins.gradle.org/m2/com/netflix/nebula/nebula-core/3.0.0/nebula-core-3.0.0.pom
     Required by:
         project : > org.opensearch.gradle:build-tools:1.3.6 > com.netflix.nebula:nebula-publishing-plugin:4.4.4

Should be fixed by https://github.com/opensearch-project/OpenSearch/commit/7bbf0d11a0151078c6a3e478c1d2020a586b3e3e, it seems like there in an incident with Gradle Plugins portal:
Unfortunately, this means artifacts that were only available on JCenter/Bintray and were never migrated to Maven Central will not be available from the Plugin Portal. If you are using dependency verification, you may also notice different artifact checksums for libraries that were re-uploaded to Maven Central.

https://status.gradle.com/


IntelliSense broken with Pandas

Environment data

Language Server version: <IP_ADDRESS>
OS and version: Windows 10 x64 1909 (b18363.476)
Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.3 (Anaconda; pandas 0.25.3)

This problem can be reproduced on various machines with various versions of vscode.
Expected behaviour

Open the sample file Untitled-1.py
Untitled-1.py.zip

import pandas as pd

df = pd.DataFrame([0,1,2,3,4])

df.med

Re-type the last line with the same contents:
df.med
After typing the letter 'd', an IntelliSense suggestion list should appear with the method 'median' highlighted.
Please refer to the Spyder auto-complete for expected behavior:

Actual behaviour
In step 3, the method 'median' does not exist in the suggestion list.

Logs

Please refer to the full log in the zip archive:
4-Python Language Server.zip
Code Snippet / Additional lnformation

import pandas as pd

df = pd.DataFrame([0,1,2,3,4])

df.med

FYI, this is just an example of the problem with intellisense. There are many other methods or fields that are missing from the suggestions, and the example I posted here is the simplest one to reproduce the problem.

This is b/c these members are not statically declared and rather created dynamically.

Thank you. As Spyder does this nicely, I was long expecting VSCode to do the same thing.
Any ideas on how Spyder did that? Does it rely on additional metadata (apart from the source code of the package) to prepare the suggestion and do the instant documentation lookup so that it behaves much better?

My guess is same way Jedi does - by loading module into Python which causes code to actually execute. Static analysis does not run any Python code and relies on declarations and stubs.

If Spyder in this context means a live interactive experience (a la Jupyter), then it could be live data like in the VS Code extension's interactive window / notebook.

@jakebailey No I'm talking about writing in the editor of Spyder IDE without running the script. IPython is always live in Spyder so I can't determine whether the analysis is run in the REPL context without looking at the code. (But I'm sure the suggestions work in the editor pane before execution.)
If VSCode can make the suggestions work with the prerequisite that a IPython session must be live, it is already a big relief for data scientists. (The code editing part of Spyder is completely rubbish; however VSCode just puts everything on my computer crazily swapping between the RAM and pagefile and stop working after the Language Server analyzes tens of thousands of "items" and eats up my memory, so I have to switch back to Spyder.)
@MikhailArkhipov Jedi does not work either within VSCode.
I saw survey requests popping up in VSCode asking for feedback on the Data Science support, so I'm interested whether you will be taking enhancement in such feature under consideration when planning future releases. Just make IntelliSense work, and VSCode shall overwhelm anything that comes with Anaconda.

Spyder is written in Python so it has access to loaded modules and the data objects. Since it indeed appears to be running things (judging from charts), it certainly has access to dynamically created data.

Thank you very much for clarification. It's quite a pity to know there are quite fundamental limits to do similar things in VSCode Language Server. I appreciate your time.


How can I stop AP mode?

How can I stop AP mode? Eg, if a user does not connect to the AP portal within, let's say 5 minutes, close the servers and close MODE_AP on the WiFi?

Already fixed


TextField decoration documentation/assertion bug

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Use Material TextField inside a custom theme, outside of MaterialApp and any other Flutter-provided wrappers

Set TextField.decoration to null as per documentation only having it non-null requires you to have a Material ancestor:

If decoration is non-null (which is the default), the text field requires one of its ancestors to be a Material widget.

Which is understood as having decoration value to be null allows you not to have Material ancestors

Expected results
Everything works and no errors are happening
Actual results
The error:
No Material widget found.

TextField widgets require a Material widget ancestor within the closest LookupBoundary.

So either documentation has to be changed or the assertion has to take into account the decoration value
Code sample
Code sample
TextField(decoration: null)

Screenshots or Video
No response
Logs
No response
Flutter Doctor output
[✓] Flutter (Channel stable, 3.10.5, on macOS 12.6.3 21G419 darwin-x64, locale en-RU)
• Flutter version 3.10.5 on channel stable at /usr/local/Caskroom/flutter/3.10.5/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 796c8ef792 (3 months ago), 2023-06-13 15:51:02 -0700
• Engine revision 45f6e00911
• Dart version 3.0.5
• DevTools version 2.23.1
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
• Android SDK at /Users/outring/Library/Android/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 14C18
• CocoaPods version 1.12.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2022.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
[✓] Connected device (3 available)
• iPhone 14 (mobile) • BB48C113-D88F-42CF-992A-A9ABDE3F5069 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-16-2 (simulator)
• macOS (desktop)    • macos                                • darwin-x64     • macOS 12.6.3 21G419 darwin-x64
• Chrome (web)       • chrome                               • web-javascript • Google Chrome 116.0.5845.110
[✓] Network resources
• All expected network resources are available.
! Doctor found issues in 1 category.

@outring Thanks for filing this issue, please provide a minimal reproducible code so that we can assist you better.

Hi @outring. Please can you provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code?
Thank you

Hi @outring. Thanks for your response. Kindly check out the documentation https://docs.flutter.dev/release/breaking-changes/text-field-material-localizations on why you are getting this issue.

@dam-ease thanks. Please, check my code sample — it contains all the localizations (specifically it uses the method explained in the 3rd example of the page you have shared). The error I'm getting is:
No Material widget found.

TextField widgets require a Material widget ancestor within the closest LookupBoundary.

As you can see it says nothing about localizations. If I add a Material ancestor I won't get any errors at all. So the localizations have nothing to do with this
The problem is that per documentation you can use use TextField without Material ancestor if the decoration is null. Which is currently not true per implementation

Hi @outring. I think there might be a misinterpretation in the line you're referencing from the docs. From my understanding and from the error displayed, TextField widget requires a Material ancestor as also shown https://docs.flutter.dev/release/breaking-changes/text-field-material-localizations.

The documentation doesn't say that the TextField requires Material ancestor at all times. It only says that it's needed only when the decoration is not null:

If decoration is non-null (which is the default), the text field requires one of its ancestors to be a Material widget.

So if you believe the implementation is correct, then the documentation has to be fixed to avoid future confusion

https://docs.flutter.dev/release/breaking-changes/text-field-material-localizations specifically doesn't say anything about Material ancestors, it only covers Localizations ancestor or a MaterialApp ancestor which has Localizations built-in. So I'm afraid it's not related to the issue I'm facing in any way

I would like to have a confirmation on the point 1, whether the documentation is wrong or implementation so I can prepare a PR for this issue, please

Hi @outring. Thanks for your patience and detailed explanation. From what's here, it seems the textfield applies the effectiveTextDecoration only when the textDecoration is not null. But then again, if you don't want to use the Material, you could look into using EditableText directly so that he can customize it.

Here's where that assertion was added for the record: https://github.com/flutter/flutter/pull/16147
I wonder if someone uses a TextField inside of CupertinoApp, does this assertion get triggered?
If someone (CC @Renzo-Olivares ) can put together a simple app that doesn't have a Material where TextField seems to work with the assertion disabled, then let's remove it.  Otherwise, if the TextField seems to break somehow, then we should remove the line in the docs.

I came up with a few samples to observe this behavior.
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const WidgetsWithTextFieldApp());
}

/// Using [TextField] in [CupertinoApp].
class CupertinoWithTextFieldApp extends StatelessWidget {
  const CupertinoWithTextFieldApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const CupertinoApp(
      localizationsDelegates: [
        DefaultMaterialLocalizations.delegate,
      ],
      home: CupertinoPageScaffold(
        child: Center(
          child: TextField(),
        ),
      ),
    );
  }
}

/// Using [CupertinoTextField] in [MaterialApp].
class MaterialWithCupertinoTextFieldApp extends StatelessWidget {
  const MaterialWithCupertinoTextFieldApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: Center(
          child: CupertinoTextField(),
        ),
      ),
    );
  }
}

/// Using [TextField] in [WidgetsApp].
class WidgetsWithTextFieldApp extends StatelessWidget {
  const WidgetsWithTextFieldApp({super.key});

  @override
  Widget build(BuildContext context) {
    return WidgetsApp(
      localizationsDelegates: const <LocalizationsDelegate<dynamic>>[
        DefaultMaterialLocalizations.delegate,
      ],
      color: Colors.white,
      pageRouteBuilder: <T>(RouteSettings settings, WidgetBuilder builder) => PageRouteBuilder<T>(
        settings: settings,
        pageBuilder: (BuildContext context, Animation<double> animation, Animation<double> secondaryAnimation) =>
            builder(context),
      ),
      home: Container(
        color: Colors.white,
        child: const Center(
          child: TextField(),
        ),
      ),
    );
  }
}

/// Using [CupertinoTextField] in [WidgetsApp].
class WidgetsWithCupertinoTextFieldApp extends StatelessWidget {
  const WidgetsWithCupertinoTextFieldApp({super.key});

  @override
  Widget build(BuildContext context) {
    return WidgetsApp(
      localizationsDelegates: const <LocalizationsDelegate<dynamic>>[
        DefaultCupertinoLocalizations.delegate,
      ],
      color: Colors.white,
      pageRouteBuilder: <T>(RouteSettings settings, WidgetBuilder builder) => PageRouteBuilder<T>(
        settings: settings,
        pageBuilder: (BuildContext context, Animation<double> animation, Animation<double> secondaryAnimation) =>
            builder(context),
      ),
      home: Container(
        color: Colors.white,
        child: const Center(
          child: CupertinoTextField(),
        ),
      ),
    );
  }
}

Some observations:

CupertinoTextField will load without any localizations provided to WidgetsApp, but will crash when doing something like opening the context menu because of those missing localizations. We should probably assert and document this in CupertinoTextField.
CupertinoTextField currently "works" on all App variants without any changes.
Removing the assert for material ancestors in TextField lets us use TextField in CupertinoApp and WidgetsApp.

Looks like CupertinoTextField and TextField should be able to be used in any App context given that the proper localizations are defined. I'll work on verifying this further and making this change.


How to prevent node rotation behavior from causing cluster instability

We are just starting out with the Solr Operator, and intend on moving several large Solr clusters over to leveraging the operator for their management. In our initial tests, we've encountered a situation that seems incredibly risky, and we would like to understand whether there is a reasonable solution for this in place, or good suggestions for how to improve reliability around it.
The logic around SolrCloud.Spec.updateStrategy being Managed (https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.html#update-strategy) means that the operator will never take an action that risks cluster stability (shutting down a pod that would result in no live replicas etc...) This is fantastic, but only relates to actions that the operator itself would make (statefulset updates etc...), and doesn't appear to come into play during normal kubernetes operations, such as node rotations.
On an EKS cluster, when a node group is refreshed, the nodes are marked for termination within their autoscaling groups, and subsequently their pods are drained from the nodes that are to be shut down, and re-scheduled to valid nodes. Normal k8s operations to prevent service disruptions during this type of an event are to utilize Pod Disruption Budgets, which prevents the draining nodes from stopping their pods if it would cause a disruption. This leverages Readiness/Liveness status to determine when a disruption would occur, and is generally a reliable way of preventing applications from becoming unavailable.
With Solr, there is another level of abstraction, as a Solr pod being "ready" doesn't mean that all of the cores on that node are available/replicated, and thus a pod disruption budget, which only monitors that readiness state, may perceive that it is safe to delete an arbitrary pod in the cluster without the necessary logic (which the Operator has) of checking whether that pod would cause a disruption should it be shut down.
Since with a large cluster, nodes/pods coming up and down may take time to recover, and without a PDB, you may risk multiple pods going down simultaneously, there is a risk (we perceive) that Solr's availability could be at risk should a node rotation or other form of pod deletion etc... occur outside the Operator's pervue.
So, my question is:
What methodology is recommended for eliminating this risk? Are there configurations we've overlooked that will reduce this risk? Has the community simply accepted this limitation and found ways to reduce the odds of being impacted? (are we maybe overreacting, and this isn't actually a risk?)

This is a very good callout, so thank you for bringing it up.
We can easily add a PodDisruptionBudget for the entire SolrCloud cluster, and the maxUnavailable can be populated with the SolrCloud.spec.updateStrategy.managed.maxPodsUnavailable value. This is a pretty good first-step and gets us halfway there.
The next half would be replicating the SolrCloud.spec.updateStrategy.managed.maxShardReplicasUnavailable functionality through PDBs. Through the managed update code, we already understand the nodes that each shard resides on, so it wouldn't be far-fetched to create a PDB for every shard, using a custom labelSelector to pick out the node-name labels of nodes that we already know host that shard. We could even just routinely check (every minute or so) to update/create/delete PDBs, as we aren't listening to the cluster state in the cloud. The PodDisruptionBudget documentation tells us that we can't use maxUnavailable, as PDBs with custom labelSelectors can only use int-valued minAvailable. That's fine because we can always convert between the two, since we know the number of Nodes that host the shard.
However, there's another rule for PDBs that makes this part of the solution untenable. It specifies that you can only have 1 PodDisruptionBudget per-pod, and for this solution we would need to have a PDB for every shard that lives on that pod, which will almost certainly be >1. (Otherwise the general cluster PDB should be fine to use)
Hopefully Kubernetes will eventually remove the PDB per-pod limit, then we can fully (and not-too-difficultly) implement shard-level PDBs managed by the Solr Operator. In the meantime, we should go-ahead and implement the per-cluster PodDisruptionBudget and fill it with the value used in the managed update settings.
Given the limitations, what are your thoughts on moving forward with the cluster-level PDB @joshsouza ?

I 100% support adding a cluster-level PDB here, as that's definitely a first step towards success.
My concern is that the PDB will ensure we don't take a pod down if one is already down, but in the scenario where a pod just started and is coming online/doing a recovery for some large dataset that takes longer than the ReadinessProbe, from k8s' perspective it's safe to take down another pod, but from Solr's perspective it may be a risky operation.
A cluster-level PDB will at least reduce the level of risk here, but to the point of your (very thorough, thank you) note above, it's a step on the path to a final solution.

Ideas our team has been tossing around in discussions:
startupProbe may also reduce risk (though still allows for some edge cases). If a newly starting pod had a startup probe that didn't go green until all of the shards assigned to that pod were active/recovered, that could prevent what I described above. However there's secondary risk there of stuff getting stuck (I.E. what if there's an inactive shard on that pod?)
Sidecar readiness - I need to check up on the docs/test myself, but I'm curious if the entire pod needs to pass all of its readiness checks in order to be active in the service, or if we can leverage a sidecar whose readiness check just verifies that all shards on that pod are in an active/ok state. If that works (that sidecar flapping doesn't impact the pod's availability to the real solr service) then a PDB would enforce the desired behavior (it would never allow for a pod to be taken out of commission if there was one in a not-ready state in the cluster). Side effect is that this could have detrimental effects on situations where it's ok to take down some pods while others are recovering, and slowing rotations etc..., so it's still just a half-measure to your suggestion of a real check that uses Solr logic to indicate what pods are acceptable to disrupt via a PDB that ties together pods that own a shard. I'm just not sure that's going to be on a realistic horizon from the k8s timeline perspective.
Sorry to brain dump, just thought I'd add what's on my mind to the conversation in case it's helpful.

(Read up more carefully on the docs, we can't use the sidecar idea, because it would indicate the whole pod isn't ready, and drop it from the service)

Just had a thought on this after perusing the docs further to see if there's anything I could find to support our end goals within current constraints: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
I can specify a disruption maxUnavailable of 0. This will prevent any voluntary disruptions entirely.
So if the operator managed the PDB, and set the maxUnavailable to, for example 1, as long as every shard is happy, but when it detects that there are shards in a recovering state where an additional pod going down risks reliability, it can adjust the PDB to set maxUnavailable to 0 until that condition passes, then we could prevent additional eviction behavior until it's safe.
I think this is a potentially viable solution until the platform supports multiple PDB's on a pod.
What do you think?

It also occurred to me that if each SolrCloud had a PDB with a maxUnavailable of 0 at all times, the Solr Operator could monitor the cluster for node rotation behavior (node drain events, etc....) and take the appropriate action itself (I believe pods can still be deleted, or otherwise shut down). I neither know what would need to be monitored, nor how to shut down Solr pods while a PDB would normally prevent actions, but that may be a thought process worth pursuing at some point, since the Operator already has the logic baked in to know when a pod is safe to delete/disrupt.

Just had a thought on this after perusing the docs further to see if there's anything I could find to support our end goals within current constraints: https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
I can specify a disruption maxUnavailable of 0. This will prevent any voluntary disruptions entirely.

That is very interesting, and could certainly be something for us to look into.
If we go further down that idea, we could have a PDB for each pod individually, and basically set the minAvailable to either 0 or 1 depending on whether it's ok to take down that pod at any given time (given the same logic we use for restarts). That gives us a much more fine-tuned ability to control this.

It also occurred to me that if each SolrCloud had a PDB with a maxUnavailable of 0 at all times, the Solr Operator could monitor the cluster for node rotation behavior

This is probably the best solution, if we can get it right. There are things the Solr Operator generally wants to control before letting a pod get deleted, such as moving replicas off of Solr Node with ephemeral data. So if we are able to do that then I think we go for it.
The new DistruptionCondition stuff might give us that info, but its alpha in v1.25, so probably won't be available by default for at least a few more versions. I'm also not sure if it will put the condition on the pod if the PDB says not to delete it... But it would certainly be the easiest way forward if we wanted to do this.
Either way, we don't need to be perfect from the beginning. I say that for now, we either go cluster-wide PDB or do per-pod PDBs. But I absolutely love this discussion, and with a few new versions of Kubernetes, we can probably get this to an amazing place.

Thanks for all the thoughtful discussion. It hadn't even occurred to me to
do a per-pod pdb, but that makes a ton of sense given the context, and I
would say that's probably the near-term most viable solution (since there's
so much in the air for future k8s revisions, and we wouldn't want to
require bleeding edge k8s to run Solr safely).
That said, I think it's worth taking the time to do this right, get other
voices, and test things out. In the interim, my team is proceeding with a
cluster-wide PDB, and a pod that will flip between 0-1 for availability on
that in order to be overly cautious.
I think that's a reasonable option as a stop-gap for us, but I'd love to
help where I can in making this a first-party solution.
How can I best help out?
On Fri, Sep 16, 2022, 8:58 AM Houston Putman @.***>
wrote:

Just had a thought on this after perusing the docs further to see if
there's anything I could find to support our end goals within current
constraints:
https://kubernetes.io/docs/tasks/run-application/configure-pdb/#specifying-a-poddisruptionbudget
I can specify a disruption maxUnavailable of 0. This will prevent any
voluntary disruptions entirely.
That is very interesting, and could certainly be something for us to look
into.
If we go further down that idea, we could have a PDB for each pod
individually, and basically set the minAvailable to either 0 or 1
depending on whether it's ok to take down that pod at any given time (given
the same logic we use for restarts). That gives us a much more fine-tuned
ability to control this.
It also occurred to me that if each SolrCloud had a PDB with a
maxUnavailable of 0 at all times, the Solr Operator could monitor the
cluster for node rotation behavior
This is probably the best solution, if we can get it right. There are
things the Solr Operator generally wants to control before letting a pod
get deleted, such as moving replicas off of Solr Node with ephemeral data.
So if we are able to do that then I think we go for it.
The new DistruptionCondition
https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#pod-disruption-conditions
stuff might give us that info, but its alpha in v1.25, so probably won't
be available by default for at least a few more versions. I'm also not sure
if it will put the condition on the pod if the PDB says not to delete it...
But it would certainly be the easiest way forward if we wanted to do this.
Either way, we don't need to be perfect from the beginning. I say that for
now, we either go cluster-wide PDB or do per-pod PDBs. But I absolutely
love this discussion, and with a few new versions of Kubernetes, we can
probably get this to an amazing place.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/solr-operator/issues/471#issuecomment-1249533894,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGKLJISYCUZ5N5W7GOD7PDV6SKLRANCNFSM6AAAAAAQJBT6FE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@joshsouza Please let me know if you try the new version and if it helps resolve the problem. We kind of have a similar scenario. Will give it a try ourselves soon and will share our observations as well.

Also looking forward to some of the features suggested above...
This probably won't be the route for the operator, but posting an alternative idea here for others. Our centralized K8s management currently requires that we have a PDB of at least 1, so we can't necessarily go with flipping cluster level PDB between 0-1.
We were thinking of making a modified version of /admin/collections?action=CLUSTERSTATUS that essentially throws a non-200 when status is non-GREEN. This would involve writing Solr cluster-level plugins, which might not be ideal for those otherwise using vanilla Solr.


MB-8021 Explain shipment fields in Prime API documentation

Description
This PR adds descriptions to all of the fields in the two Prime API shipment endpoints, createMTOShipment and updateMTOShipment. The downstream affect for most of these updates was extremely small, except when it came to the addresses.
In order to override the base address description for each of pickupAddress, destinationAddress, secondaryPickupAddress, and secondaryDeliveryAddress, I needed to structure them around the allOf key. This meant that the field references in the generated code were all different, so I needed to update the payload/model conversion functions. Any negative effects of this should be caught in the server tests.
Setup
To view the updated documentation for these endpoints, follow these links:

createMTOShipment
updateMTOShipment

To run all of the server tests:
make server_test

Or to run all of the Prime API tests related to shipments, try:
go test ./pkg/handlers/primeapi -v -testify.m Shipment

Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change.

Messages

:book:
:link: MB-8021

  Generated by :no_entry_sign: dangerJS against a5954645da5010051416c86a84a8a8cecd278cf8


fix: Contact link, home description, todo img & pug source path

Checklist

[x] I didn't over-scope my PR
[x] My PR title matches the commit convention
[x] I did not include breaking changes
[ ] I included unit tests that cover my changes
[ ] I added/updated the documentation about my changes
[x] I made my own code-review before requesting one

Description of the changes
Some fixes

:tada: This PR is included in version 1.0.0-beta.8 :tada:
The release is available on:

GitHub release
v1.0.0-beta.8

Your semantic-release bot :package::rocket:


Confirmation prompt added to reset subcommand

Addresses #392
Fixes the bug in make_gh_request function in utils.py

Hello @UjjwalAyyangar! Thanks for submitting the PR.

In the file cli/popper/commands/cmd_reset.py, following are the PEP8 issues :

Line 19:1: W293 blank line contains whitespace

@ivotron : Requested changes have been made.


Structure fingerprint not matching

For some reason ZINC92580503 (CCCc1c2c(n(n1)C)n(c(n2)N)c3ccccc3) isn't matching against a current build of the database using default settings (Morgan fingerprint) - it's only coming back as a 68% match.
Through a good deal of testing, this seems to be quite rare or entirely unique to this compound, but it is very worrisome.

@greglandrum - do you have any ideas here?  Does this molecule look like anything that Morgan might not be 100% consistent with?

Nevermind, testing against the newest version of gpusim works.  Might have been a bug fixed in the major rewrite a few months ago.

Glad you found that; it would have been quite scary


Fix an possible json parsing error in graphrag.llm.openai.utils.py

Description
Some open-source LLM may return something like '''JSON''', they were elegantly processed with the function clean_up_json but this function was not used in some places which caused some problems.
Related Issues
Proposed Changes

Checklist

[x] I have tested these changes locally.
[x] I have reviewed the code changes.
[ ] I have updated the documentation (if necessary).
[ ] I have added appropriate unit tests (if applicable).

Additional Notes
Tested on qwen2-7b-instruct. Another possible problem is top_p in the config file, some llms(qwen-7b for example) only support (0,1) instead of [0,1].

@microsoft-github-policy-service agree
发自我的iPhone
------------------ Original ------------------
From: microsoft-github-policy-service[bot] @.>
Date: Thu,Jul 25,2024 6:55 PM
To: microsoft/graphrag @.>
Cc: unknown918 @.>, Mention @.>
Subject: Re: [microsoft/graphrag] Fix an possible json parsing error ingraphrag.llm.openai.utils.py (PR #710)
@unknown918 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"        Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.
Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


[BUG] Internal Server Error in Local Query

Whenever I ran query/local, this error occurred:
Internal Server Error
b'Unexpected internal server error'
CPU times: user 6.76 ms, sys: 3.43 ms, total: 10.2 ms
Wall time: 2.21 s
<Response [500]>
To Reproduce
perform a local query
local_response = local_search(
index_name=index_name, query="How to reset my password?"
)
parse_query_response(local_response, return_context_data=True)
Expected behavior
Local query should return the result

I am getting the same error when running a local query.

I double checked my indexing operation and it is complete. I am also using the latest version of graphrag-accelerator.


-as operator is unexpectedly culture-sensitive, unlike casts

Related: #6989
Casts from strings use the invariant culture whenever the underlying type has a static ::Parse() method that accepts an IFormatProvider parameter.
Surprisingly, the -as operator does not exhibit this behavior and instead exhibits culture-sensitive behavior, but does so inconsistently.
Steps to reproduce
[cultureinfo]::CurrentCulture = 'fr-FR'

[double] '1,2.3'
'1,2.3' -as [double]

[datetime] '10/20/2018 1:22:33 AM'     # OK, invariant culture is used.
'10/20/2018 1:22:33 AM' -as [datetime] # Yields $null, because the *current* culture is used.

Expected behavior
12,3
12,3

samedi 20 octobre 2018 01:22:33
samedi 20 octobre 2018 01:22:33

Actual behavior
samedi 20 octobre 2018 01:22:33
# !! No output, because the string wasn't recognized as a date.

That is, -as [datetime] only works with strings that are formatted according to the rules of the current culture; '20 octobre 2018 01:22:33' -as [datetime] would work, for instance.
By contrast, '1,2.3' was consistently interpreted according to the rules of the invariant culture (where , is the grouping char., and . the decimal mark; with fr-FR in effect, the culture-sensitive [double]::parse('1,2.3') would fail).
Environment data
PowerShell Core 6.2.0-preview.1 on macOS 10.14
PowerShell Core 6.2.0-preview.1 on Ubuntu 16.04.5 LTS
PowerShell Core 6.2.0-preview.1 on Microsoft Windows 10 Pro (64-bit; Version 1803, OS Build: 17134.165)
Windows PowerShell v5.1.17134.228 on Microsoft Windows 10 Pro (64-bit; Version 1803, OS Build: 17134.345)

I can confirm this behaviour
I'm using en-GB culture   so dates are day/month/year

PS> [datetime]'25/12/2018 1:00:00 PM'
Cannot convert value "25/12/2018 1:00:00 PM" to type "System.DateTime". Error: "String was not recognized as a valid
DateTime."
At line:1 char:1
+ [datetime]'25/12/2018 1:00:00 PM'
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvalidCastParseTargetInvocationWithFormatProvider

fails as expected. The .NET constructor wants month/day/year so
PS> [datetime]'12/25/2018 1:00:00 PM'

25 December 2018 13:00:00

This is known .NET related issue since PowerShell v1
The -as operator
PS> '25/12/2018 1:00:00 PM' -as [datetime]

25 December 2018 13:00:00

accepts and uses the culture specific date format
whereas
'12/25/2018 1:00:00 PM' -as [datetime]
returns null
Checked this on
PowerShell v5.1, v6.1, v6.2 preview 1 on Windows 10 1803 Build 17134.345
My PowerShell v6.1 on WSL uses en-US culture so I get these results
PS /home/Richard> '25/12/2018 1:00:00 PM' -as [datetime]
PS /home/Richard> '12/25/2018 1:00:00 PM' -as [datetime]
Tuesday, December 25, 2018 1:00:00 PM
and
[datetime]'12/25/2018 1:00:00 PM'
[datetime]'25/12/2018 1:00:00 PM'
work as previously shown as expected

Thanks for confirming the issue, @RichardSiddaway.

The .NET constructor wants month/day/year so
This is known .NET related issue since PowerShell v1

It's actually PowerShell that by design opts for interpreting strings using the invariant culture, for predictability across cultures.
Also note that there's no constructor involved in this case (there is none that accepts a string in this case): PowerShell calls the [datetime] type's static .Parse() method, and explicitly chooses the overload that allows it to pass the invariant culture as the culture to interpret the input string by.
For instance, behind the scenes,
[datetime] '12/25/2018 1:00:00 PM'

is effectively translated to:
[datetime]::Parse('12/25/2018 1:00:00 PM', [cultureinfo]::InvariantCulture)

Also note that, fortunately, it isn't just US-style month-first dates that the invariant culture recognizes; there are formats that are less confusing to international audiences; e.g.:
[datetime] '2018-12-25 13:00:00'

Irrespective of the exact mechanism there is still a mismatch between cast and -as as shown in both sets of examples

I guess that unification here will big breaking change.
Perhaps we could resolve all related issues introducing globally "invariant culture mode" like .Net Core now has. Only we have to review all code and add Culture parameter in most of cmdlets.

I assume you're referring to .NET Core Globalization Invariant Mode; correct, @iSazonov?
From my limited understanding this is a per-application configuration setting.
Can you say more about how this could fit into PowerShell, and what the -Culture parameters would do?

Yes, I thought that we could set CurentCulture to Invariant. I don't think about this in depth but it could be interesting.

This has the potential to be a huge breaking change.  As a first step I'd suggest that the PowerShell documentation should be revised to reflect the difference in behaviour between cast and -as

Re documenting the behavior: good idea - see https://github.com/PowerShell/PowerShell-Docs/issues/3193 and, for #6989, https://github.com/PowerShell/PowerShell-Docs/issues/3194

To make matters worse, I just realized that even the behavior of -as itself is internally inconsistent:
E.g., using -as [double] is again culture-invariant (I've added an example to the OP) - unlike -as [datetime].
I haven't dug deeper to see what logic underlies this discrepancy


Misleading claims in README

Your README begins with the claim

Successor of Cxx.jl and CxxWrap.jl.

This is arguably false, as it comes with the implict connotation that it is an "official" succcessor (which it isn't) and that those projects are dead (which they are not, at least CxxWrap is actively used and receiving fixes).
It certainly is an alternative to these packages, so you could say that.
You also claim CxxWrap does not support Julia 1.7. This is also not true, we are actively using it there. Of course there may be bugs, in that case; in that case an issue report would be good, otherwise the issue cannot be addressed

Apologies; I've updated the README. Please let me know if I should make more corrections.
Regarding CxxWrap.jl, please see https://github.com/JuliaInterop/libcxxwrap-julia/issues/90.

Thank you. I'll take a peek at your cxxwrap issue.


Invalid prop AddonPanel

Hi,
I'm using the latest version of your module (very useful by the way) and i have the following warning from propTypes.
Warning: Failed prop type: Invalid prop `panels.kadira/jsx/panel.title` supplied to `AddonPanel`.
    in AddonPanel (created by Container(AddonPanel))
    in Container(AddonPanel) (created by addonPanel)
    in addonPanel (created by Layout)
    in div (created by Styled(div))
    in Styled(div) (created by Layout)
    in div (created by Pane)
    in Pane (created by SplitPane)
    in div (created by SplitPane)
    in SplitPane (created by Layout)
    in div (created by Pane)
    in Pane (created by SplitPane)
    in div (created by SplitPane)
    in SplitPane (created by Layout)
    in Layout (created by Layout)
    in div (created by Styled(div))
    in Styled(div) (created by Layout)
    in div (created by Layout)
    in ThemeProvider (created by Layout)
    in Layout (created by Container(Layout))
    in Container(Layout)
    in div

This is due to storybook's AddonPanel propTypes, now checking a shape for the panels prop.
This can be solved by passing the Title functional component directly to the panel title property when registering in register.js#L18.
I'll submit a PR by the day.

I'm still getting this issue.
It's not clear what action I have to take to fix it.
Thanks

@bmordan can you provide more detail about which version you are on?


Probably Trailing new lines not supported/Line Break Issue

I browsed the code on github and think colorize(String text, String ansiCode) will not handle trailing new lines correctly, because split will not return them. See https://docs.oracle.com/javase/7/docs/api/java/lang/String.html#split(java.lang.String)
" ... Trailing empty strings are therefore not included in the resulting array. ... "
I think the code gets in trouble with:
"a\n\n\n" because split will result in ["a"]
"a\n\n\b" because endsWithLine is set to false and therefore no new lines are added in the loop

As assumed, the code did not work for both examples. It also has problems, if the newline to be output is not the newline of the current jre/os, which can occure in a multi-platform environment, where for example messages are logged into files with a fix new line for all os.
The code below solves the three issues and can replace the existing method in class Ansi:
`
// Windows, Unix or old Classic Mac OS
static Pattern newLinePattern = Pattern.compile("((\r?\n)|\r)", Pattern.MULTILINE);
static StringBuilder output = new StringBuilder();

static public String colorize(String text, String ansiCode) {

    output.setLength(0);

    // assure at least one newline for logic simplicity
    text = text + "\n";

    Matcher newLineMatcher = newLinePattern.matcher(text);

    int nextLineBegin = 0;
    String line = null;
    String newLine = null;

    while (newLineMatcher.find()) {

        line = text.substring(nextLineBegin, newLineMatcher.start());

        // determine the exact new line (which can be different from line to line)
        // to assure identical new lines output
        newLine = text.substring(newLineMatcher.start(), newLineMatcher.end());

        if (! line.isEmpty())
        {

            output.append(ansiCode);
            output.append(line);
            output.append(RESET);

        // ELSE: no text => no ansiCode output => no RESET => keep effect of last RESET

        }

        // Not at last line?
        if (newLineMatcher.end() != text.length()) {

            // yes, there is more to come, output new line
            output.append(newLine);
            nextLineBegin = newLineMatcher.end();

        }

    }

    return output.toString();

}

`
If a line is empty, the code neither sets attributes nor resets the terminal. The last state is keept to reduce output, because last reset (of none-empty line output) still is active. If this assumption is wrong, just remove IF to make reset unconditional again.
I assure this code was written by me and only by me and I contribute it under MIT License to the project.

Apologies for my silence in the last days, I've been struggling with some personal issues. I'll try to review your issue and code asap. If you want, you can create a PR in the meantime, that will speed up the review process, you will also be listed as a contributor to this project :)

I have a PR that solves the bug you found. I tested your code and it worked, however I found it too complex and hard to understand. I achieved the same thing just by changing a few lines.
I'll push this in a new release.

The replace function always uses the same (plattform specific) NEWLINE. I think the original text passed to colorize should only be attributed by ansiCode, but kept as it is. If you are using different NEWLINEs in a string or consistently a fix NEWLINE, which is not the plattform-specific NEWLINE the result is not what I expect. The source of text to be attributed maybe is not under control of the caller and the text is just received as it is.


ticking bomb? EOF record would prevents truncation (!?)

This is on the same register as all of the on-disk data truncation problems, and this probably suggests a common solution.
Shortcut Suggestion:
We could delete queues upon reception of suggest_truncate to EOF.
@guilload This requires however to push #4099 and remove the autocreation of queues upon reception of first log from ingesters

Closed via #4238.


[Tabs] Add missing updateScrollButtons type in TabActions

[x] I have followed (at least) the PR section of the contributing guide.

@notsidney Much appreciated, thanks :+1:


Feature request: DCE based on liveness analysis

It should be possible to do dead code elimination based on liveness analysis information.

Thanks for opening an issue! While you're totally right that we could, this is not part of the current goals of this crate. We expect the user of this crate to have done higher-level IR optimizations beforehand, including dead code elimination, etc. For instance, it is one thing done by Cranelift, our main target consumer. Regalloc can help just a bit by reducing the amount of dead spills/writes, but performing full DCE is out of scope. Does it make sense?

Yeah I understand. Maybe then it will be a good idea to provide liveness analysis API so everyone could use it for optimizations?

Alternatively, a way for the user to provide liveness information to regalloc so it doesn't have to be recomputed. But I think this is more of a long-term wishlist item, it is not needed for an MVP.


Show targets of vtable/itable calls

In some applications, a signiticant amount of CPU time is spent on dispatching megamorphic virtual/interface calls. This appears in the profile as vtable stub or itable stub. However, this does not give any clue on why the particular call site is megamorphic and how to optimize it.
I propose adding a pseudo-frame on top of v/itable stub with the actual type of an object the virtual method is called on. This should make clear the propotion of different receivers for the particular call site:

New feature is turned on by default, but can be disabled with --safemode 0x40 option.

Great feature, thank you.

Great feature

How do we use this with JMH?
-prof "async:libPath=/home/foo/Downloads/async-profiler-3.0-linux-x64/lib/libasyncProfiler.so;output=jfr;dir=direction;rawCommand=-F vtable"
Yields:
Run progress: 50.00% complete, ETA 00:00:02
Fork: 1 of 1
Preparing profilers: AsyncProfiler
Warmup Iteration   1: [WARN] Unknown argument: -F vtable
100.598 us/op
Iteration   1: [WARN] Unknown argument: -F vtable

@toaler Async-profiler plugin for JMH is a part of JMH project.
You may use rawCommand option to pass raw async-profiler command line to the plugin:
-prof async:rawCommand=features=vtable

Thanks @apangin , when I run:
-prof async
I get vtable/itable frames
when I run:
-prof async:rawCommand=features=vtable
The vtable frames are not included. Infact any time I set a option via -prof async like
-prof async:output=jfr;rawCommand=features=vtable
vtable is ignored.

@toaler
It worked for me. Make sure to enclose the argument in quotes: -prof "async:output=jfr;rawCommand=features=vtable", otherwise bash will treat ; as a command separator.
Also note that you need async-profiler version 3.0 to use this feature.

Thanks that solved it


[Request] python3.7 support

Description
Consider supporting python3.7.
Shapely currently supports the following platforms:

python2.7
python3.4
python3.5
python3.6

source: https://pypi.org/project/Shapely/#files
Repro steps:
When a user tries to pip install shapely using a python3.7 interpreter, PYPI defaults to using the source package Shapely-1.6.4.post1.tar.gz since no wheels are available.
Actual behavior
Shapely fails to install since the source package doesn't come with libgeos
Collecting shapely
  Using cached https://files.pythonhosted.org/packages/7d/3c/0f09841db07aabf9cc387662be646f181d07ed196e6f60ce8be5f4a8f0bd/Shapely-1.6.4.post1.tar.gz
    Complete output from command python setup.py egg_info:
    Failed `CDLL(libgeos_c.so.1)`
    Failed `CDLL(libgeos_c.so)`
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-dvsq7fc3/shapely/setup.py", line 80, in <module>
        from shapely._buildcfg import geos_version_string, geos_version, \
      File "/tmp/pip-install-dvsq7fc3/shapely/shapely/_buildcfg.py", line 167, in <module>
        fallbacks=['libgeos_c.so.1', 'libgeos_c.so'])
      File "/tmp/pip-install-dvsq7fc3/shapely/shapely/_buildcfg.py", line 161, in load_dll
        libname, fallbacks or []))
    OSError: Could not find library geos_c or load any of its variants ['libgeos_c.so.1', 'libgeos_c.so']

Expected behavior
Package installs correctly because a python37 wheel is available.
Note
I can probably help with packaging python37

@pydo thank you for bringing this up. I will schedule a 1.6.4.post2 release.

Closing, see #612.


Update -step.txt

Summary

Changes

Closes:
Task list

[ ] For workflow changes, I have verified the Actions workflows function as expected.
[ ] For content changes, I have reviewed the style guide.

confim


fix(v2): restore previous scroll position on back button click

Motivation
Quick attempt to fix #5076
Currently, after changing the location, we focus on the skip link to focus on that link at first. However, this has the side effect that when the user clicks on the browser's back button, then the previous scroll position is lost. To avoid this we can focus on the skip link only when moving forward in browser history.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Scroll a bit on any doc page, then go to another page, then press on back button in the browser, as result is the previous scroll position should be preserved.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

I would like to have scroll position restored when navigating both ways (back and forward), because ... that is how webpages work.

It also will work correctly if you move forward in history. You can check this behavior on the preview site, it should work.

Yes, indeed, thank you so much for your work!

Thanks @lex111 ! that seems to work fine


Proxy auth + https

HTTP proxy through SSL not working.
HttpRequest request = HttpRequest.get("httpS://foo.bar/");
request.useProxy("<IP_ADDRESS>", 123);
request.proxyBasic("user", "passw");
request.trustAllCerts().trustAllHosts().ok();

java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 407 Proxy Authentication Required" - info.urobots.utils.HttpRequest.stream(HttpRequest.java:1663)
info.urobots.utils.HttpRequest.buffer(HttpRequest.java:1639)
info.urobots.utils.HttpRequest.body(HttpRequest.java:1558)
info.urobots.utils.HttpRequest.body(HttpRequest.java:1573)
info.urobots.main.Application.main(Application.java:53)

user and password is correct.

I can confirm this happens.
And looking at the code it seems that the Proxy-Authorization is stored together with the rest of the other headers: consequently the first HTTPS CONNECT to the proxy doesn't get the Proxy-Authorization header.


update all.json

Site
URLscan.com link

thetrolllerart.dvrlists.com
https://urlscan.io/result/b667dd6e-76f8-4694-9616-ff6d05da148e/

web3connector.com
https://urlscan.io/result/d299e1ae-2c61-4512-a18b-d24fa7fbb2e5/

cn59409.tmweb.ru
https://urlscan.io/result/0735803d-13c3-466c-9f94-d956aa2e4693/

walletconct.co
https://urlscan.io/result/a92d0530-d96e-41d4-a97b-0e5626f5d680/

polikadot.com
https://urlscan.io/result/b1eb6000-c09c-4a75-acec-26633e24918f/

myauthnetwork.com
https://urlscan.io/result/cebf582b-b186-4991-af23-c0981a9c34ea/

main-errorfix.live
https://urlscan.io/result/045adffb-632f-42d2-822f-34189665d34a/

walletconnecting.co
https://urlscan.io/result/318765c4-2744-440f-8a4a-ea718778b0c7/

added
"walletconct.co",
"polikadot.com",

added
"thetrolllerart.dvrlists.com",
"web3connector.com",
"cn59409.tmweb.ru",

added
nodechain.me
walletconnecting.co

added walletconnect-web3.com


spire 1.6.3 has been released: update the code

I tested it as part of a different effort.
It works fine.
We only need to bump the version number in the manifests.

Done.


buefy.css much too aggressive

If you set a base font-family for example and then subsequently add buefy.css, buefy stomps all over the site rules.
Is the inclusion re-adding all of the bulma styles back in? Is there a way to only add styles necessary?

Yes, Buefy compiled css has all Bulma's styles included. I wouldn't recommend utilizing the compiled css if you're customizing the theme. You have two options:

Use the non compiled (Sass) instead.
Recompile the css with your variables.

or add https://github.com/purifycss/purifycss(remove unused CSS) in your webpack

@rafaelpimpa Including the specific utils + component sass files worked for me thank you


perftest: bomber must not use pbill.number anymore

https://github.com/untillpro/air-devops/commit/31550768934e7060027c5207f8723f1e806f0cbb


[CELEBORN-1237][METRICS] Refactor metrics name.

What changes were proposed in this pull request?
Refactor metrics name.
Why are the changes needed?
Easier to understand the meaning of metrics
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Existing UTs.

cc @AngersZhuuuu

Pls crate a jira ticket and write pr title as [CELEBORN-xxx][XX] title

cc @waitinfuture @SteNicholas @FMX

Done.

Done.


When using Mermaid Gantt Charts with exclusion of weekends, the weekends are in a very bright tone, text

Example code:
gantt
	dateFormat YYYY-MM-DD
	axisFormat %W
	excludes weekends
	section Sprints
		xxxx:						MS40, 2023-01-12, 2023-01-28
	section Tasks
		Example Text that cannot be read well:					1, 2023-01-12, 1d

notice the color used to display the weekends is a bright white, making overlapping text impossible to read.

Thanks for pointing this out. Fixed!


Don't try to run cargo metadata on stub crates

Closes: https://github.com/coreos/cargo-vendor-filterer/issues/32
Our approach of filtering down the Cargo.toml kept running into problems with trying to actually run cargo metadata on the result.  Specifically some crates have path dependencies that can't actually be built at runtime anyways.
In practice, since we're relying on this not actually being compiled, let's keep the full existing Cargo.toml as is, and not run cargo metadata on it at all.
We're deleting everything else (including things like build scripts, test code etc.), so I think this is generally fine.
(Ideally though we'd neuter the licenses too and such...)

OK actually, no we do need to filter out things like [[bin]] in order for nushell to work:
$ cargo b --verbose
error: failed to get `atty` as a dependency of package `nu-cli v0.73.0 (/var/srv/walters/src/github/nushell/nushell/crates/nu-cli)`

Caused by:
  failed to load source for dependency `atty`

Caused by:
  Unable to update registry `crates-io`

Caused by:
  failed to update replaced source registry `crates-io`

Caused by:
  failed to parse manifest at `/var/srv/walters/src/github/nushell/nushell/vendor/alloc-no-stdlib/Cargo.toml`

Caused by:
  can't find `example` bin at `src/bin/example.rs` or `src/bin/example/main.rs`. Please specify bin.path if you want to use a non-default path.

OK, this now now verifies that we can successfully build nushell from vendored sources.  One thing I hit on though is two bugs:

We need --all-features true for some reason; otherwise ahash-0.7.6 drops out.  But OTOH, I think most people will want to enable that anyways so that their users can build the crate with any/all features.
It should just be --all-features; no idea why I made it an Option<bool> in clap.  But fixing this would be an incompatible CLI change.


Can't download full imgur gallery

thread https://imgur.com/r/nsfwcyoa/
one of many gallery in thread https://imgur.com/r/nsfwcyoa/I2SFr
ripme only download first picture of every gallery (if it have gallery instead single pic) instead full download all images in gallery
but when i try to test reddit instead https://www.reddit.com/r/nsfwcyoa/
it still working and download full gallery if it have gallery link instead single pic...but it seem like it's not download full topic in /r/nsfwcyoa , when i'm random test, it missed https://imgur.com/a/wv3F0 https://www.reddit.com/r/nsfwcyoa/comments/7m1e83/first_cyoa_the_new_warden_very_nsfw_contains_very/ ...maybe more

Hey, this is the old (And unmaintained) repo. Please repo this issue over at the new repo https://github.com/RipMeApp/ripme