Liveshare IO Operations Slow after some time

Describe what happened:
During liveshare, I'm getting lots of lagging on IO operations such as loading files, searching in VSCode, Saving files, Renaming Symbols with F2, etc.
This lagging happens on the Client and not the Host of Liveshare.
 Both are running the latest builds of VSCode. I own both machines (physically right next to each other, but connected over regular liveshare connections - no local connection stuff).
The lagging appears to happen after an hour or two of being connected to the the live share, and progressively gets worse over time. It doesn't just appear. I can fix this by leaving the collaboration session and then rejoining again.
I tend to leave the host session open for extended periods of time, and disconnect and reconnect as I work. The project is required to be ran on macOS (project limitations), but I code on Windows machine due to the setup being better (more screen space, mouse and keyboard etc.)
The code is updated in both the Client and the Host - there is no desync of contents in Editors
What was your system configuration?
Client config can be found below, exported from VSCode itself. There should be no memory issue, or CPU issue as seen by the system info.

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
63.93GB (46.23GB free)

Process Argv
--crash-reporter-id 1274adda-145d-4536-81dd-31f25d9fa962

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	   119	 12220	code-insiders main
    0	   124	  3200	   shared-process
    0	    83	 13164	     fileWatcher
    0	    85	 19228	     fileWatcher
    0	    85	 30468	     ptyHost
    0	     7	  1376	       console-window-host (Windows internal process)
    0	     7	 12432	       console-window-host (Windows internal process)
    0	     6	 15420	       "C:\Program Files\Git\bin\bash.exe" --login
    0	    11	 28484	         "C:\Program Files\Git\bin\..\usr\bin\bash.exe" --login
    0	     0	 33172
    0	     0	 33380
    0	     0	 33656
    0	     0	 33612
    0	     6	 32676	       "C:\Program Files\Git\bin\bash.exe" --login
    0	    11	 21212	         "C:\Program Files\Git\bin\..\usr\bin\bash.exe" --login
    0	    41	  3780	   utility-network-service
   18	   583	  9648	   extension-host
    0	   107	  8160	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node --max-old-space-size=3072 "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --serverMode partialSemantic --useInferredProjectPerProjectRoot --disableAutomaticTypingAcquisition --cancellationPipeName C:\Users\Jason\AppData\Local\Temp\vscode-typescript\7151d16fc59f18c6fcfb\tscancellation-aafab7c953c3273b035f.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
    0	   107	 18328	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node --max-old-space-size=3072 "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\Jason\AppData\Local\Temp\vscode-typescript\7151d16fc59f18c6fcfb\tscancellation-5cb74823cba71d06380f.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
    0	   101	 18340	       "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node "c:/Program Files/Microsoft VS Code Insiders/resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js" --globalTypingsCacheLocation C:/Users/Jason/AppData/Local/Microsoft/TypeScript/4.8 --enableTelemetry --typesMapLocation "c:/Program Files/Microsoft VS Code Insiders/resources/app/extensions/node_modules/typescript/lib/typesMap.json" --validateDefaultNpmLocation
    0	    83	 21280	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node -e "delete process.env.ELECTRON_RUN_AS_NODE;require(process.argv[1])" c:\Users\Jason\.vscode-insiders\extensions\ms-vsliveshare.vsliveshare-1.0.5750\out\prod\speaker\out\speaker.js
    0	    84	 28212	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=9648
   15	   570	 10820	   extension-host
    0	    86	 16648	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\css-language-features\server\dist\node\cssServerMain" --node-ipc --clientProcessId=10820
    0	   108	 17968	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node --max-old-space-size=3072 "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName C:\Users\Jason\AppData\Local\Temp\vscode-typescript\aa3e3c8e3f7797c1f8a6\tscancellation-ffaee95f5b5636fb4b5a.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
    0	   102	 22708	       "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node "c:/Program Files/Microsoft VS Code Insiders/resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js" --globalTypingsCacheLocation C:/Users/Jason/AppData/Local/Microsoft/TypeScript/4.8 --enableTelemetry --typesMapLocation "c:/Program Files/Microsoft VS Code Insiders/resources/app/extensions/node_modules/typescript/lib/typesMap.json" --validateDefaultNpmLocation
    0	    84	 30952	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=10820
    0	   108	 32752	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node --max-old-space-size=3072 "c:\Program Files\Microsoft VS Code Insiders\resources\app\extensions\node_modules\typescript\lib\tsserver.js" --serverMode partialSemantic --useInferredProjectPerProjectRoot --disableAutomaticTypingAcquisition --cancellationPipeName C:\Users\Jason\AppData\Local\Temp\vscode-typescript\aa3e3c8e3f7797c1f8a6\tscancellation-75d9e6595d0253c7ce7d.tmp* --locale en --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc
    0	    84	 33540	     "C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe" --ms-enable-electron-run-as-node -e "delete process.env.ELECTRON_RUN_AS_NODE;require(process.argv[1])" c:\Users\Jason\.vscode-insiders\extensions\ms-vsliveshare.vsliveshare-1.0.5750\out\prod\speaker\out\speaker.js
    0	   173	 15620	   gpu-process
    0	   263	 15752	   window (index.js - Visual Studio Live Share (Workspace) - Visual Studio Code - Insiders [Administrator])
    0	    96	 26176	   issue-reporter
    0	   218	 32160	   window (Visual Studio Live Share (Workspace) - Visual Studio Code - Insiders [Administrator])
    0	    28	 33056	   crashpad-handler

Workspace Info
|  Window (index.js - Visual Studio Live Share (Workspace) - Visual Studio Code - Insiders [Administrator])
|    Folder (vsls:/): Workspace stats not available.
|  Window (Visual Studio Live Share (Workspace) - Visual Studio Code - Insiders [Administrator])
|    Folder (vsls:/): Workspace stats not available.;

Product and Version [VS/VSCode]: VSCode Insiders latest (also happens on latest stable)
OS Version: macOS Host, Windows 10 Client
Live Share Extension Version: 1.0.5750
Target Platform or Language [e.g. Node.js]: NodeJS / React
Steps to Reproduce / Scenario:
Edit code as normal on a liveshare. IO operations appear to be the ones affected over time progressively getting slower. Noticable after about an hour to two hours as being slow but bearable. Quickly deteriorates though into unusable over another 30 mins.
Please attach logs to this issue:
LiveshareLogs.zip
Screenshots
If applicable, add screenshots to help explain your problem.

Hi @test137E29B - For this scenario, I'd recommend checking out VS Code Server it was recently announced - https://code.visualstudio.com/blogs/2022/07/07/vscode-server.


DRILL-6239: Add build and license badges to README.md

Add nice build and license badges that everyone else has. See a preview of what they look like here:
https://github.com/ilooner/drill/tree/DRILL-6239

@arina-ielchiieva

+1

@vrozov Fixed bad link and added maven badge. Currently the maven badge points to drill's distribution pom. It's also interesting to note that only some of drill's artifacts are published on maven central. See https://search.maven.org/#search|ga|1|g%3A"org.apache.drill"


Documentation Rewrite to Reflect New Config Structure

The Documentation directory has many items that needs to be updated to the new config structure.

duplicate.


Nice idea

Can this be implemented using platformio ?
Can be usefull to use and test with an [Heltec WiFi LoRa 32]  [LILYGO TTGO LoRa32]

I've done the build-upload, everything seems correct (with a lilygo) but :
rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13192
load:0x40080400,len:3028
entry 0x400805e4
E (156) esp_core_dump_flash: Core d3f␋�data check failed:
Calculated checksum='50cb89e6'
Image checksum='ffffffff'

My fault !
This doesnt work without the antenna ....


docs: Use react-docgen-typescript for autodoc generation

What are the relevant tickets?
None, but did this as a separate PR on the way to https://github.com/mitodl/hq/issues/6192
Description (What does it do?)
This switches Storybook's autodocs to use react-docgen-typescript, as described here
Why:

react-docgen wasn't worked with styled components / emotion. This appears to be a known, old issue with react-docgen.
react-docgen-typescript handles enums automatically for us, and other types, too.

How can this be tested?

Read the updated readme
Run yarn storybook --docs locally.
View http://localhost:6006/?path=/docs/smoot-design-button--docs ; the docs should look good and http://localhost:6006/?path=/docs/smoot-design-actionbutton--docs
Some other stuff you could try:

remove a union value from ButtonSize. The "argstable" in storybook docs should update
Update a jsdoc description in ButtonStyleProps ... the argstable should update
Update the jsdoc description above Button; the docs intro should update

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Serious problems when using multiple branches.

Bug
When using two deployments with the CMS pointed to two different branches everything works ok until one person edits the same file as another person on the other branch. Since the refs/heads/cms is not name spaced by the base branch like `refs/heads/cms/${basebranch}` maybe or some variation.  Make a netlify content repo with admin setup.
Branch the repo.
Deploy both branches on different netlify instances.
Login to admin on both.
Edit the same file in both instances.
Everything works fine without Editor workflow turned on, so you'd have to turn that on as well.
- Please mention your versions where applicable.
Netlify CMS version: 1.9.3
Browser version: 67 chrome

Node.JS version: 9.11
Operating System: Mac OS X
- Please link or paste your config.yml below if applicable.

Added PR #1494

Closing as stale


How to use hyphenation with textview?

I do not need the DocumentView. I just want have hyphenation in TextView.
Thanks.

At the moment, they are closely intertwined because you have to manually draw out the tokens. So, any implementation must extend textview.

Sorry I do not understand. Could you please elaborate more?

I apologize for the late response. Generally, all the content needs to be drawn out manually here which means the Hyphenation is built exclusively for just that. So, you cannot use it with TextView. Please reopen if you have any more questions.


Method names on Native Libraries

Hi,
First of all, thanks in advance, your module rocks!
This is less an issue - more a simple & useful feature request:
I managed to use ffi with both node.js & nw.js on Windows & Linux.
A feature that is very easy to implement but feels missing is a function name mapper to handle dynamic libraries which has method names mangled and export methods like _Z17vdoSomethingiib
I will show an example from my code:
existing working code (but with mangled names)
var cartManager = ffi.Library('bManager', {
  '_Z9addToCartv': [ 'void', [ 'double' ] ]
  ..... more method declarations ...
});

cartManager._Z9addToCartv(126.3);

I know it's possible to do something like
cartManager.addToCart = cartManager._Z9addToCartv; for each method, but it would have been much better to have something like:
var cartManager = ffi.Library('bManager', {
  '_Z9addToCartv': [ 'void', [ 'double' ] , 'addToCart']
  ..... more method declarations ...
});

cartManager.addToCart(126.3);

(adding another optional parameter that will represent the name of the method you want the JS object to have for each given method)

Nice feature.
+1


Add ability to lock/unlock issues

Closes #143

@rnystrom Any changes needed on this one? Got some time tomorrow! 😄

Nope I think we're good to go here!


[Docker] Add patches for distributed randomness

In this PR, we update the pytorch patch for including the DTensor sharding info in Cuda RNG states.

@lichen225 @JsBlueCat I find many unchanged code but high-lighten in green?

I think Github has these syntax highlights for patch files by default.


Errors when build readium sdk on Visual Studio 2012

Hi,
I'm facing an issue that cannot compile Readium SDK in VS 2012, it shows a lot of error like:
error C2143: syntax error : missing ',' before '...' (........\ePub3\ePub\archive.cpp)	in integer_sequence.h
Is there anyone can make build SDK successfully?
How to config the environment?
Thanks so much.

Hello,
Hello how do you configure visual studio to use Release 0.5
Thank you for your answer.


Add uiOverride to user for custom styles to be displayed on everything

Why:
Need a way for the system to identify if the user wants to have their own styles override to view
What:
Add prop to user and everywhere else it needs to be added to in order to get everything working
Required:
Docs made first for how to update fields (do it while making this)

Added, next action is to have the override actually override on the frontend


Add bucket versioning pt 2

Feature or Bugfix

Bugfix

Detail

After adding explicitly created artifacts bucket for CodePipeline - began seeing errors when running cdk synth (ONLY FOR SPECIFIC DEPLOYMENTS)

Error Message Error: Artifact Bucket must have a KMS Key to add cross-account action 'Prepare' (pipeline account: 'XXXXX', action account: 'YYYYY'). Create Pipeline with 'crossAccountKeys-true'

This error only showed on some deployments and seemed to be throwing a validation error even though docs say providing a manually created bucket which is encrypted should suffice

potentially could be a version mismatch for why it is working only on some deployments (??)

After adding 'crossAccountKeys=true'parametercdk synth` works appropriately for all

Relates

N/A

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

tested in AWS deployment in us-east-1 - still creates and uses the explicitly created artifacts bucket and KMS Key as expected

I was able to replicate the error and I am now testing the fix while reviewing the PR


pass req to the getFileName and getDirectory

It is very small patch:
-  getDirectory: function (fileInfo, formData) {
+  getDirectory: function (req, fileInfo, formData) {
-  getFileName: function (fileInfo, formData) {
+  getFileName: function (req, fileInfo, formData) {

This parameter let me handle re.query inside getDirectory, where i can pass the HTTP GET parameter to manipulate of subdirectory path from the client.

Ok, I found the bug...
First of all, I want to say thank you for ur upload-server. It works. But u do not follow conventions :/ , so ur code is very hard to read(especially for noobs like me).
Also, always use path.join instead concatination(that's about ur bug):
-    var destinationFile = currentFolder + newFileName;
+    var destinationFile = path.join(currentFolder, newFileName);

so, the result of ur concatination is:
 /path/tofilename
instead:
/path/to/filename
there r alot of concatinations in ur code more, but it seems it works :) It would be awesome to refactor ur code and cover with tests...


Changing variables in ansible roles from {{variable}} to {{ variable }}

Code styling changes

closing in favour of https://github.com/Capgemini/Apollo/pull/335/files


batch insert breaks after 5k lines with ca 65 columns

Hello there,
I tried to write an Excel import for my application. After importing smaller excelfiles (1000ish lines), I tried a big one with ca 20000. The excel import stopped working.
I debugged it down to the parameterized queries, which seem to not be able to handle all the different parameters and is ULTRA slow at that point too.
To workaround that, I used the toString() method and applied the query then with knex.raw.
The problem with this approach is that the 5k line limit is still valid. Even the toString()-Method seems to be at some kind of end with too much data.
So my second workaroung is to bundle my data in smaller packets (1000) and to toString() that (to be fast again), which works but is really really ugly.
 var sqlquery = '';

                var batchSize = 1000;
                var newListEntriesLength = newListEntries.length;
                // build sql string in batchSize packs
                for(var i = 0; (i * batchSize) < newListEntriesLength; i++) {
                    var slicedNewEntries = newListEntries.splice(0, batchSize);

                    if(slicedNewEntries.length > 0) {
                        sqlquery += _strucd.knex(tableName).insert(slicedNewEntries).toString() + '; ';
                    }
                }

                // Add leftovers
                if(newListEntries.length > 0) {
                    sqlquery += _strucd.knex(tableName).insert(newListEntries).toString() + ';';
                }
                _strucd.knex.raw(sqlquery)
                    .then(function(results) {
                        return callback(null, results);
                    }, function(err) {
                        return callback(err);
                    });

Am I missing something?
Is it really that complicated to do fast batch insert with several 1000 lines?
Is there a better way to build an insert query, without doing everything it manually?

Kind Regards,
Matthias

I'm going to dig into this a bit and see if I can improve things to make this possible

Ah Im using Postgres underneath, if that matters at all.

At the very least I'll make it so there's a (configurable) batch limit so the ugly code is pushed into the library and not on you to produce

Just checking in to see if there's been any work on this?  I'm also working with big imports (~16000 lines) on MariaDB, and I'm having similar problem.  If I let the query run long enough, then I eventually get the following error:
[project]/node_modules/mariasql/lib/Client.js:367
      this._client.query(this._curResults._query, this._curResults._useArray);
                   ^
Error: Not ready to query
    at Error (native)
    at Client._processQueries ([project]/node_modules/mariasql/lib/Client.js:367:20)
    at [project]/node_modules/mariasql/lib/Client.js:263:38
    at process._tickCallback (node.js:355:11)

Which makes it look like the problem might be with MariaDB, except that the OP has a similar result using Postres.
I also found that if you're using Bluebird promises, you can use a shorter hack using the Bluebird Promise.map concurrency option, as follows:
    Promise.map(data, function(row) {
      return knex.table(tablename)
        .insert(row)
        .then(function() {
          //console.log('row inserted');
        });
    }, {concurrency: 1})
    .then( function() {
      console.log('done');
    })
    .catch( function(e) {
      console.error(e);
    });

This means that only one short db connection is open at any given time.  More than one might be okay, but usually there's a max limit to that, so I decided to start small.

Yeah so I'm thinking there should be an API like:
knex.batchInsert(values, limit).into(table)

Which would operate by inserting values in batches of limit (where limit would default to 1), and it would automatically wrap everything in a transaction.
Does this sound reasonable?

sounds fine by me.

Yeah, that would be great.  Thanks!

Can you try the batch-insert branch I just pushed and see if it's intutive:
API:
knex.batchInsert(table, values, [limit: default 1]).then(...

Hey,
I tried your branch with a batchSize of 1000. The interface works, the data is inserted, BUT my handwritten solution takes like 4 seconds, your solution around 21s, so I prefer the crappy, fast code at the moment :)
_strucd.knex()
                    .batchInsert(tableName, newListEntries, batchSize)
                    .then(function(results) {
                        return callback(null);
                    }, function(err) {
                        return callback(err);
                    });

I am using the batch-insert feature at the moment, any chance it will be merged into a new release so I can get all the bugfixes again?

I haven't had a chance to test this extensively (I got moved to a more urgent project temporarily), but I'd like to second the request to have this feature merged into the new release.  Thanks!

+1

+1

can we get proper batchInsert support, with transactions, with returning into the next release? This issue is open since  Mar 31.
Kind Regards,
ArdentZeal

Hey everyone. Obviously you all want batchInsert. I'm going to try to do a release soon, and it's not going to make it in because I have no pull request to review, and the branch is stale and targets the old lib/ build folder.
However once I've learned how to do releases, it should be simple enough for me to do another release soon. I'll just merge and release when the PR is ready.
Will you be able to create a new PR @ArdentZeal?

I did not wrote the original logic for the batch insert.
@tgriesser did that. It never got fully completed sadly.
I am not very well versed in the knexjs internals (read: never looked at the internal code for more than 1 minute) and I am really limited for time at the moment, so I cant promise a PR.
Kind Regards

I've made a pull request for this: #1182

Fixed by #1182


Manipulable outputs

Currently all nodes are integrated as binary sensors. Which at least works very well with my UVR16x2. What is annoying, however, is that the displayed values of the outputs cannot be manipulated.
It would be nice if you could not only monitor, but also switch an output on or off if necessary.
Unfortunately, at the moment this is only possible with the CMI app and cannot be automated with HA due to other factors.
I have several devices that use up residual power. However, these can only be prioritized to a very limited extent. This particularly applies to the outputs of the UVR16x2. In summer this is not so relevant, but in winter I would rather have hot water than stored electricity.

I don't understand your issue, can you summarize again what the error is?

Please excuse me, there is no error. I started with "Feature request - Suggest an idea for this project". Digital sensors are ideal for inputs, for outputs switches could sometimes be better. So, it's just an idea for the future that came about because I'm looking for such a solution for my energy management.

This would be a very nice feature if the CMI can be controlled from within HA. Switching the Outputs or changing fixvalues.

It is not possible to change values on the C.M.I. via the API used by this integration. There are unofficial methods to do this, but I will not implement them as they are experimental. As an alternative, there is my CoE integration, which can be used to send data from the Home Assistant to the C.M.I. via CAN over Ethernet.


Add a unique modifier

Faker has a unique modifier that forces it to generate unique values. Would be great to have something like that in jFairy.

+1 it would be great !


Add the ablity to set a local address for BIO_dgram_pair

BIOs created from a BIO_dgram_pair don't normally have a local BIO_ADDR
associated with them. This allows us to set one.
Fixes https://github.com/openssl/project/issues/933

@andrewkdinh

Somewhat related: while I was investigating this, I noticed this bug
https://github.com/openssl/openssl/blob/b9886a6f3483e0525596d3b3956416282038da82/crypto/bio/bss_dgram.c#L751
I believe should instead be:
ret = BIO_ADDR_make(&data->peer, BIO_ADDR_sockaddr((BIO_ADDR *)ptr));

This pull request is ready to merge

Pushed to the feature/quic-server branch.


⚠ Bofrost.at has degraded performance

In 4334a49, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2321 ms

Resolved: Bofrost.at performance has improved in cdff99c after 26 minutes.


[Route-Manager] Modify getConnectedSubnets

Modify response entity of getConnectedSubnets API in neutron router controller to match with ACA

Linked to #434 as the new InternalRouterEntity is required by DPM for L3 programming.

Codecov Report

Merging #445 into master will decrease coverage by 0.10%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #445      +/-   ##
============================================
- Coverage     36.85%   36.75%   -0.11%
- Complexity     1150     1152       +2
============================================
  Files           447      448       +1
  Lines         10722    10759      +37
  Branches       1371     1373       +2
============================================
+ Hits           3952     3954       +2
- Misses         6232     6268      +36
+ Partials        538      537       -1

Impacted Files
Coverage Δ
Complexity Δ

.../futurewei/alcor/route/config/ConstantsConfig.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...r/route/service/Impl/NeutronRouterServiceImpl.java
53.67% <0.00%> (-6.55%)
25.00 <0.00> (ø)

...com/futurewei/alcor/macmanager/utils/MacUtils.java
56.52% <0.00%> (-8.70%)
7.00% <0.00%> (-1.00%)

...alcor/elasticipmanager/dao/ElasticIpAllocator.java
63.81% <0.00%> (+0.27%)
48.00% <0.00%> (ø%)

...rewei/alcor/portmanager/processor/PortContext.java
69.09% <0.00%> (+1.81%)
23.00% <0.00%> (+1.00%)

...i/alcor/portmanager/processor/RouterProcessor.java
84.37% <0.00%> (+6.25%)
10.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

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


Flipped the %vocal activity dawn plot to the left (Dr.Symes' suggestion)

Hi Vijay,
I worked on your comment on the figure to flip the %overall activity figure. Hope it's okay.
Thank you very much,
Pavithra

Hi Pavithra - I am noticing negative values for the x-axis - could you fix that and make another pull request?


Can I do grading in some way with rapidfire

Do you have any functionality or is it possible to extend RapidFire to do grading of answers and assigning them to individual people? Like a quiz system?
Thank you

can you give me a concrete example? im unable to understand the requirement properly.

Thank you for your reply!
 I want to see if you know a simple way to get the answers and compare them to a key. Then with this be able to assign users a grade based on the number of correct answers.

im afraid, such grading system is out of the scope of this gem. but it should be easy to implement.
im willing to help you with internals of rapidfire, if you are implementing grading system.

That would be amazing! I would greatly appreciate the help!
So how does the gem work? How do you think it would be best to implement a system such as this?
Where do you think I should start?


Deprecated Flag for Uncrawlable Publishers

This PR adds a flag for uncrawlable publishers. The Publisher Coverage Script is updated to skip publishers marked as deprecated. Also, deprecated publishers are marked as such by strike-through in the supported_publishers.md

@addie9800 I moved the ignore_deprecated flag from the crawl method to Crawler. The paradigm of crawl is to only include parameters affecting all crawlers (forward, backward). Since the depreciation flag does not serve any purpose regarding backward crawling, I decided to move it to the crawler. What do you think about that?

@addie9800 I moved the ignore_deprecated flag from the crawl method to Crawler. The paradigm of crawl is to only include parameters affecting all crawlers (forward, backward). Since the depreciation flag does not serve any purpose regarding backward crawling, I decided to move it to the crawler. What do you think about that?

I think it's a good idea. I also updated the docs a bit. Maybe you can also say what you think about that

@addie9800 thanks for updating the documentation. Unfortunately the latest documentation commit breaks a lot of links. Also tutorial 4 now seems completely overwhelming and out of focus while tutorial 5 looks like it was cannibalized. The purpose of tutorial 4 is to enable the user to filter for specific articles. search or deprecatrd isn't as nearly as important here. The latter ones are mostly for convenience. I would let tutorial 4 as it was and add the deprecation mechanica to the former tutorial 5.

Oh, and I thought I had caught the broken links. Well, I undid the previous changes and just appended it to section 5 of the tutorial


Set memory limit for build pods + 'docker build'

Requires a repo2docker with https://github.com/jupyter/repo2docker/pull/159

Should we make binderhub depend on r2d in setup.py? We'd have to finish off releasing r2d, and then make the dependency >= that version.

@betatim I think that wouldn't matter, since binderhub only launches repo2docker inside a container. I'd need to bump the default container image tag...

This works great now form my testing.

I added a significant security method to this PR and retitled it, since doing 'dependent PRs' in GitHub is hard :(

This is great! I've looked it over and everything seems good for 'real' cases where a registry is in use. The only missing piece is that running without a registry (e.g. minikube for local or travis testing) no longer works because builds and runs are no longer talking to the same docker instance.
There are three places where we look for docker images when there isn't a registry:

with docker_client in binderhub itself, where we use the docker env (this is typically the node docker via tcp using $(minikube docker-env))
kube uses the node docker directory when launching images
build uses node docker (okay) or dind (now separate)

We need to make sure that when we aren't using a registry, all three of those are either talking to the same docker or at least using the same image list. I suspect the simplest way to do this is to eliminate support for running without a registery. When a public registry is not in use, we could require a local registry, which is easily added with minikube via minikube addon enable registry.
This would simplify some things, because we could eliminate a branch in the runtime code and make it a branch in the setup code (i.e. setup public registry or launch internal one). The alternative is figuring out some way to move images from dind to the node docker, but I'm not sure there's a simpler way to do that than just using a registry.

@minrk the default should still be to mount /var/lib/docker.sock into it, no? shouldn't that continue to work for minikube? This should be entirely optional right now.
I do agree that only supporting the use case with the registry is sensible long term.

@yuvipanda that makes sense! It's failing because dind is enabled by default in the helm chart. I switched the default to disabled based on your comment.


Hide mainstream browse pages

Mainstream browse pages are currently not indexed, but soon will be to allow rummager to deliver content.
We're still unsure if we want to display mainstream browse pages in the search results, and how. By boosting them with zero, they can be hidden from the results.
Before

After

Trello: https://trello.com/c/6vXKBd5d
PR to index browse pages: https://github.com/alphagov/collections-publisher/pull/127

I've not tested this, but I'd expect that code to just move these to the end of the list, rather than remove the results from search.  If a mainstream browse page is the only match, they'll still come back.  This is probably fine for now, though.


Ruff + Tox integration

This PR does two things:

It implements RUFF as a replacement for flake8 (unfortunately replacing other packages is still quite restricted) (config in the pyproject.toml). It has replaced flake8 in the GitHub workflow.
It implements TOX (in the pyproject.toml), with testing environments, so that one can easily run tests locally (this can be done by using tox -e [environments] e.g.: tox -e ruff,pylint,pydocstyle,mypy,sphinx,pytest,nbval. To run these tests it is required to install tox into your environment first.
Theoretically each step in the GH Workflow/Actions could be replaced with TOX, e.g. tox-e ruff instead of ruff metasyn. Is that something we would want? It might be nice for consistency as it matches how tests can be done locally, but it does also mean that tests will run IN a tox environment IN a GitHub environment, adding an extra layer to the CI.

I am not extremely confident in the way the config is set-up, as it is the first time I have configured these kinds of tools - so I do apologise if the settings and configuration do not fully make sense.
This solves #178

Shouldn't we add ruff, etc to our environment lists in tox, so they get run automatically?

I am a bit confused with what you mean, Ruff is in the tox environment list, right?
On a side-note, the other comments have been resolved and committed!


All carousel items visible during initialisation

Have simple three panel owl carousel.  When carousel is initialised, all three panels appear briefly on the page, before disappearing and only the opening item showing.  Is there a way to stop this happening?

Yes. There is actually a fix for that.
OwlCarousel is preventing this automatically if you name your carousel .owl-carousel, but you can also prevent this manually. See this example here: http://codepen.io/anon/pen/gPBQXM?editors=0100
What we are doing here, is hiding the carousel by default and only showing it, once it has finished initializing.
.your-carousel-wrapper {
    display: none;
}

.your-carousel-wrapper.owl-loaded {
    display: block
}

Thanks  @eWert-Online - very helpful.  Fixing the CSS did the trick.


Fixed #602 Make / db names work in windows

Use period "." instead of ":" for Windows platform

Have you had a chance to test the fix on a Windows machine?

No. Do you have Windows environment?

Just chat with @ashvindersingh, and @ashvindersingh can provide an access to a Windows VM.

Thanks!

https://issues.couchbase.com/browse/CBIT-2373


Check whether CoreLocationAnimator progress may be bigger than 100%

On Android it was possible for the progress to exceed 100% which lead to runtime errors. We should check if that's also the case in this project.
Android issue for reference: https://github.com/ably/ably-asset-tracking-android/issues/751
┆Issue is synchronized with this Jira Uncategorised by Unito

I've been looking into this and doing some refactoring, as part of which I discovered #375. Parking this work until we decide what to do about #375.


Overlay another pdf at specific location?

For example: I have 3 by 5 inch pdf and I want to overlay it at a specific location on a Letter size pdf.

This is not possible yet from the CLI, though it is possible from the C++ API. This feature is often requested, and it is on my roadmap.

This issue is part of the qpdf pages epic. If you are interested in following, please see #1104.


Data dump fixes

What's New?

Fix some queries in the ToolsController
Fix bug where data dump output erroneously showed some tools as inactive when they were actually active

Coverage increased (+0.002%) to 90.986% when pulling 92ac9a76192f764601152ceb7cd11c3f2b5b2b89 on RickCarlino:data_dump_fixes into ecbb7bbdf8e47bf2aaa2cf2318fb74cb5ce36949 on FarmBot:staging.


resource provider for aad related resources.

I am seeing "microsoft.aadiam" resource provide and I am trying to stream AAD activity logs using this resource provide type but I am getting error. "microsoft.aadiam" can you please provide any link explain about this provider

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

ID: 40c2b004-24fa-c5aa-5eb6-5fa7b88510f7
Version Independent ID: 5944eaa6-b0bb-2b1b-e0f5-0d17df19b89f
Content: Azure resource providers and resource types
Content Source: articles/azure-resource-manager/resource-manager-supported-services.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@ajaypamarthy Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

@ajaypamarthy - I would recommend looking at the documentation focused on that feature - What are Azure Active Directory reports?

I am trying ARM template to stream AAD logs into log analytics & event hub. I am looking for specific resource provider at tenant level. Somewhere in other part of document section, currently it is not supporting at tenant level.


Projects without separate directory for solution breaks props file

If a project is created without the "Create directory for solution" option checked, then the way the props file is copying the osx/linux binaries breaks, putting them in nested folder structure that mirrors the layout inside the package.
The fix is to update the props file to handle this correctly, which I'm working on now.

/cc @copygirl


ReadTimeout errors not being caught and/or logged

We experienced some connectivity issues with our ES cluster and the reads from ES where timing out. It retried a few times but it ended up giving up.
The problem is that those read timeout errors where not logged into the logger and we were not alerted of this fact, they ended up in stderr, I believe, and not in the log file that we configured in mongo-connector's config.json.
Here is the trace
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/threading.py", line 920, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.4/site-packages/mongo_connector-2.3-py3.4.egg/mongo_connector/util.py", line 85, in wrapped
    func(*args, **kwargs)
  File "/usr/local/lib/python3.4/site-packages/mongo_connector-2.3-py3.4.egg/mongo_connector/oplog_manager.py", line 304, in run
    ns, timestamp)
  File "/usr/local/lib/python3.4/site-packages/mongo_connector-2.3-py3.4.egg/mongo_connector/util.py", line 32, in wrapped
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.4/site-packages/elastic2_doc_manager-0.2.0-py3.4.egg/mongo_connector/doc_managers/elastic2_doc_manager.py", line 164, in update
    self.upsert(updated, namespace, timestamp)
  File "/usr/local/lib/python3.4/site-packages/mongo_connector-2.3-py3.4.egg/mongo_connector/util.py", line 32, in wrapped
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.4/site-packages/elastic2_doc_manager-0.2.0-py3.4.egg/mongo_connector/doc_managers/elastic2_doc_manager.py", line 181, in upsert
    refresh=(self.auto_commit_interval == 0))
  File "/usr/local/lib/python3.4/site-packages/elasticsearch-2.3.0-py3.4.egg/elasticsearch/client/utils.py", line 69, in _wrapped
    return func(*args, params=params, **kwargs)
  File "/usr/local/lib/python3.4/site-packages/elasticsearch-2.3.0-py3.4.egg/elasticsearch/client/__init__.py", line 279, in index
    _make_path(index, doc_type, id), params=params, body=body)
  File "/usr/local/lib/python3.4/site-packages/elasticsearch-2.3.0-py3.4.egg/elasticsearch/transport.py", line 329, in perform_request
    status, headers, data = connection.perform_request(method, url, params, body, ignore=ignore, timeout=timeout)
  File "/usr/local/lib/python3.4/site-packages/elasticsearch-2.3.0-py3.4.egg/elasticsearch/connection/http_urllib3.py", line 102, in perform_request
    raise ConnectionTimeout('TIMEOUT', str(e), e)
elasticsearch.exceptions.ConnectionTimeout: ConnectionTimeout caused by - ReadTimeoutError(HTTPSConnectionPool(host='XXXXX', port=9243): Read timed out. (read timeout=100))

What version of mongo-connector are you using? This looks like an issue that was fixed in this commit and was released as part of version 2.4.

@llvtt Definitely < 2.4. Will upgrade, thanks.


[Bugfix]: Fix Tensorizer test failures

This PR attempts to fix the issue raised at #6809

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@youkaichao @ywang96 Tensorizer tests are now passing.
As I initially suspected, this was due to lack of resource cleanup. These tests were created before #3783 when it was assumed that a cleanup() would be run implicitly after each test. After its implementation, this silently stopped happening, since the PR didn't account for tests relying on its previous autouse fixture no longer able to clean up. I added an auto cleanup fixture for Tensorizer tests, and then specifically invoke cleanup() one more time before running the problematic test.
Please do feel free to ping me next time something like this comes up, as allowing Tensorizer tests to soft fail runs the risk of a breaking change being merged silently.  Cheers! :)

/ready


Consideration for Maintainership

Hello KEDA community!
Since joining this project, I've become really passionate about seeing KEDA become the de-facto autoscaler for all k8s services. If there is interest, I would love to be considered for a maintainership so I can help merge PRs, promote KEDA to the community, and just generally help any way I can :).
Thank you for your consideration!

Thanks @dimberman! Jeff will PR an update to our governance to list onboarding new members as we are checking what that would look like and what the max number of maintainers is that we want.
Stay tuned!

Thank you Tom!

Just dropping a note that we have not forgotten about this but just a bit delayed due to current world scenario.
Will keep you posted and sorry for the delay!

No worries at all :). It's a crazy time

@tomkerkhove any update? I'm also considering volunteering to be a maintainer so just checking 😄

I'll post an update this week!

Feel free to open a dedicated issue for you if you are interested @turbaszek to follow the process.

First things first, sorry for the delay!
Around April, @jeffhollan reached out to Daniel to let him know we are currently not planning on increasing our amount of maintainers but if there are long-term contributions we might consider changing our current maintainers board.
Given we haven't seen any contributions lately we will close this but feel free to re-open if you want to be reconsidered.


Align params with sassC

The C implementation of sassc has slightly different parameters. It would be nice to harmonize those for them to be exchangeable. See here for the sassC parameters. Note that I don't know which of libsass-python or sassC came first, and which set of params should be used as a reference.

Quite a few of sassc's options are specific to their implementation so I don't think we'd pick up all of them.  The others should match reasonably well but I imagine there's some we should change to be more like them.

Maybe not all should be aligned indeed. The one I had in mind is -s

Ruby sass uses -t for output style, which is why sassc (and perl-libsass cli) also go with -t :)

#130 added --source-comments


Fix EC_POINT_bn2point() for BN_zero()

Fix EC_POINT_bn2point() for BN_zero()
EC_POINT_bn2point() rejected BIGNUMs with a zero value.
This behavior indirectly caused failures when converting a point
at infinity through EC_POINT_point2hex() and then back to a point with
EC_POINT_hex2point().
With this change such BIGNUMs are treated like any other and exported to
an octet buffer filled with zero.
It is then EC_POINT_oct2point() (either the default implementation or
the custom one in group->meth->oct2point) to determine if such encoding
maps to a valid point (generally the point at infinity is encoded as
0x00).
Fixes #10258
Add self-test for EC_POINT_hex2point()
Adds tests for each curve to ensure that encodings obtained through
EC_POINT_hex2point() can be fed to EC_POINT_point2hex() yielding a point
identical to the one from which the encoding is generated.
Checklist

[x] tests are added or updated

Does this need a CHANGES entry? (I dont know the answer)

Does this need a CHANGES entry? (I dont know the answer)

I am not sure either, but gravitating toward a "probably not" answer.
Maybe the OMC reviewer can give feedback on it. (ping @mattcaswell )
I am currently looking into #10366 which is somehow related, but I am still undecided if that should have an impact on this PR or not.

Does this need a CHANGES entry? (I dont know the answer)

I'd say probably not. However perhaps the man page should be updated with something about what happens with points at infinity?
Other than that this PR looks good.

Does this need a CHANGES entry? (I dont know the answer)

I'd say probably not. However perhaps the man page should be updated with something about what happens with points at infinity?
Other than that this PR looks good.

Ultimately it's each EC_METHOD responsibility to decide what is an acceptable representation of any point, including point at infinity, through the point2oct and oct2point pointers.
I believe all of the currently included implementations translate Pinf -> \0\0 -> Pinf, but can we really document something specific?

Ultimately it's each EC_METHOD responsibility to decide what is an acceptable representation of any point, including point at infinity, through the point2oct and oct2point pointers.

Surely, if an application calls EC_POINT_bn2point() then it is going to expect to always get the same result for a given point, regardless of which EC_METHOD happened to have been chosen? Similarly it should not matter which GFp curve you use they should all behave consistently with each other. And all GF2m curves should also be consistent with each other.

@mattcaswell do you think the added lines clarify things enough?

Merged to master with:

d47c108756 Fix EC_POINT_bn2point() for BN_zero()
35ed029b5a Add self-test for EC_POINT_hex2point
3cc26f2eba Extend docs for EC_POINT conversion functions

Merged to 1.1.1 with:

6f6adf1d7b Fix EC_POINT_bn2point() for BN_zero()
f59967cb72 Add self-test for EC_POINT_hex2point (trivial changes on cherry-picking)
3c25ac2d2e Extend docs for EC_POINT conversion functions

Thanks!


Can't Unregister ADFS Adaptor

Upgrading from v 7.x to 8.01. I don't have "WindowsAzureMultiFactorAuthentication" or "AzureMfaServerAuthentication" as adaptors, only "AzurePrimaryAuthentication" and "AzureMFAAuthentication". Attempting to remove "AzureMAAuthenticaion" results in "Unregister-AdfsAuthenticationProvider : The 'AzureMfaAuthentication' authentication provider cannot be unregistered as it is internal to AD FS.".

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

ID: 86e190f4-0027-f42f-68ec-7d6a9a3975ae
Version Independent ID: e7cd369b-eb6f-eefb-d96b-da5888d7ce74
Content: Azure MFA Server upgrade
Content Source: articles/active-directory/authentication/howto-mfaserver-deploy-upgrade.md
Service: active-directory
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@PeteBurgess Thanks for your feedback! We will investigate and update as appropriate.

Please ignore... someone had already removed the old adapter and not documented it. Apologies for the inconvenience.


Investigate Using Older Versions of Jackson

This is an investigatory PR which checks what happens in the Azure SDKs when different versions of Jackson are resolved in the classpath.

/azp run java - storage - tests


Errors from custom providers are rendered in cli but not web UI

When using a custom provider, errors show up in the cli:

But in the UI the test is marked as failure with no clear reason:

It would be great to see the same error in the UI.
Here is a minimal reproducible example:
promptfoo config:
prompts:
  - "foo"

providers:
  - id: 'python:./test.py'

tests:
  - vars:
      x: y
    description: abc

python provider (test.py):
def call_api(prompt, options, context):
    return {
        "error": "something went wrong"
    }

Fix in #990.  Thanks @aantn

Thank you very much as always.

Released in 0.66.0


Simplify a few pattern-matches.

When those have an exact Option / Result equivalent.
Bonus:

remove a few unneeded .clone()s, returns and statics
when applicable (i.e. no interpolation), "Hello, World".to_string() brings less overhead than format!("Hello, World")

Tool-aided by comby-rust.

Thanks!


EDS Data Grid Feature: onRowContextMenu

I have added a onRowContextMenu feature to allow for right-click on table rows.
We need this to be able to use context menus on tables generated using Eds Data Grid.
onRowContextMenu works the same as the already existing onRowClick functionality. It just uses the other mouse button.
Tests and storybook is updated, and runs.
If there's anything I've missed, please let me know.

I changed it to use a menu instead, as that is more in line with what it probably will be used for.

Thank you :)


feat: add special feature types (flow, page, widget)

Close this for now as users can configure what their features should look like using flags


Backup last seed before loading the next one

This PR intends to save the last seed played when the user requests a new one, so they can go back to it (for log review or when reset was unintended).

Working at the moment so can't take a proper look at this until later (unles Zac looks it over before i do), just noting that i changed the base branch from main -> staging since main is usually kept in state of current release while staging is where we add new features to in preparation for future releases (bugfixes is the branch for small hotfixes).
Doesn't make a huge difference right now since we just had a release so main/staging are up to date but in future there may be a case where staging has quite a few things updated from main


ReadTheDocs has limited build time

The build time for free projects is limited to 15 minutes (Source). Checking one of the latest successful builds reveals that we are already getting quite close to this limit (772 seconds ~ 13 minutes). I expect us to exceed this limit in the near future if we add more jupyter notebook tutorials. So what are our options?

As stated on the linked page, one can ask for additional build time. Not sure if they will do that, especially when they see, that the pandas theme we use somehow circumvents the embedding of adds.
Buying a business plan. Pricing starts at 50$ per month.
Publish somewhere else (Github pages)
Reduce build time. There are two possible approaches I think we can do this for now:

Use a dedicated Conda environment. Currently, we are using the weldx environment which already takes several minutes to build. If we can reduce the necessary packages to a minimum, this might free some resources. However, this will only work if we skip running the notebooks
Using a dedicated documentation branch. The GitHub action that currently builds the docs pushes all generated files to that branch and triggers the RTD build (only for the master branch).

See this link

cref https://github.com/BAMWelDX/weldx/pull/238#issuecomment-783383061

the current build time sits around ~630s with the recent tweaks, so enough breathing room for now? 😃


Disable the system LAF

Friends, this is a very sensitive topic that I'd love your feedback. 😉
As you all know, arara 4.0 features message boxes for user input (buttons, lists, text boxes, and so on). This is provided by the Swing widget toolkit.
Swing is known to be slower than, say, SWT (Standard Widget Toolkit, from Eclipse), but it is a pure Java approach rather than a wrapper to the native window manager. I like to favour Swing because I feel safer using it, even at the cost of some time for rendering.
That said, I would like to point you all to this particular line. This might add a significant time for rendering in some JVM implementations (not counting the Swing rendering time). So I was wondering if we should disable the system LAF configuration and stick with the default widget rendering. In general, the first execution takes more time than subsequent executions. System LAF is more polished, so it gives a more receptive box than the (usually) ugly Swing ones.
It's also worth noting that it's possible to set up the system LAF via command line (in java, not arara). And personally I am not keen on adding an option in our configuration (or am I). 😉
Thoughts?
Paulo

Sensitive it is indeed 😄.
First, excuse me for possibly providing some clouds for the parade. I personally don't see the use for a GUI on a build tool (but that's one of the reasons I like to use Unix at times).  But I might be the odd duck in that respect, since especially in Windows shops everything is expected to have a GUI (even a poor one).
When there is a GUI, however, I think it is quite important that it reacts in a way that is "native" to the OS your are using. This is two-fold: everything should look uniform, and all applications should ideally react according to the design language of the OS. Those are small things, but they go a long way towards a fluent user experience. If I had a cent for every time I grunted over some common shortcut such as Ctrl-A not working properly in an application (on whatever platform!), I would be rich.
That being said, if you really see a good use-case for a GUI (again, not my use case), and think the initial startup time is annoying, then it might be better to disable the native LaF by default if that can be tuned externally as well.

Thanks for the great feedback, Egon!
Thankfully, the GUI part is not an essential part of the tool (it's actually very optional). 😉  It just offers an user input in a more friendly way of interacting with the automation flow, say
% arara: makeglossaries if showOptions(2, 'Question!',
% arara: --> 'Do tell me, my good friend: should I create a glossary?',
% arara: --> 'Yes, please!', 'No way!') == 1

(GUI on my Fedora machine)
In fact, the way I implemented these features, the rendering only happens if and only if there is any call to these GUI elements. Otherwise, arara behaves normally, with the usual startup time and no additional payload. So we are saved. 😉
I also believe the more friendly the elements are, the easier will be for users to interact. So I think we are in the right track. The additional time only hits when these elements are used, but it does happen when arara is used the traditional way.

Looks nice, I have to say. I agree with you that for some people it might offer a nice feature.
I wouldn't worry about the delay, as long as it is only a second or so (to put this in perspective, the last TeX document I worked on took about 10 seconds to compile (with a lot of effort to speed up the process; I think without that on a slow compiler it took about 20 minutes (still building the figures in parallel, though)).

Thanks, I might leave things as they are then. The idea of having these GUI elements is to provide some sort of didactic approach to the automation flow. Personally, I wouldn't use, but maybe one could use a set of directives during a course to make the student choose the right options in order to continue. 😉
With these elements, the first execution takes more time than the subsequent ones, at least in my Linux box. But in my Mac, the time is very insignificant comparatively. Linux might be tricky due to other JVM vendors and implementations, and not to mention different window managers. But hey, it works! 🍷

I must admit, the rendering is very fast in my Mac, so I think it was just my usual paranoia striking back again. And do this window look very nice! Those Apple bastards... ❤

Interesting, I thought I had closed this issue.  However, the configuration file now features a laf entry that allows overriding this behaviour, by providing the desired LAF full name. For example:
laf: 'com.sun.java.swing.plaf.motif.MotifLookAndFeel'

This one is the Motif LAF provided by Java. Other styles can be used as well. As a shortcut, two special keywords as used to set up the LAF:

system: this keyword makes the application rely on the system LAF (e.g, GTK+ in a typical Linux environment).
none: (default) this keywork makes the application rely on the default LAF provided by the Swing toolkit.

When an invalid value is used (typo or inexistent LAF), the application gracefully fallback to the default LAF provided by the Swing toolkit. No error is generated.


Don't work on Windows with Python3.9

Hi, I tested this library on Windows 11 with Python 3.9 and couldn't get it to work at all.
There is no error, however the calls to winreg.CreateKey don't create anything.
It's only when I found this thread https://stackoverflow.com/questions/65929777/python-winreg-unable-to-write-to-hkey-current-user that I tried the exact same code with Python 3.8, and it worked perfectly fine.
I see you had users mentioning this problem in the issue #13 that have been closed, and while it may not be something to fix in your library, but a bug in Python, I'm opening this issue for further reference

I encountered the same problem with Python 3.10, but the problem seems to be fixed in Python 3.11.


Merge Strategy Documentation

fixes #226
I chose the merge strategy approach namely because I'm not sure how to plumb the depths of possible issues around @daKmoR's note that:

iirc using only config set however breaks webpack configs as they need to be "carefully" copied with keeping function in tact and such... that's why we use webpack-merge generally

If anyone else has deeper insight on this, I'd be happy to make updates here.

hmm strange in the preview the markdown seem to not be correctly rendered?
https://deploy-preview-250--nervous-stonebraker-1f429b.netlify.com/testing/testing-karma.html#manual-setup

Oh, indeed. Tweaked it and I think the parse likes me again...

thxxxxx :heart:


VRP

What language and solver does this apply to?
Python
Describe the problem you are trying to solve.
i want to solve the problem that how to append time dimension into the cost function

not an issue

set the SpanCost coeff of the dimension to 1 (0 by default thus not participating to the objective value)
https://github.com/google/or-tools/blob/a0690fc79db6a49a14610697996fa73993d12012/ortools/constraint_solver/routing.h#L3204-L3211


Refactor Storage Kotlin Snippets

This PR should:

Replace GlideApp with Glide
Replace Java's System.out.println() with Kotlin's println()
Remove uploadTask's explicit type to keep code clean
Remove usage of the !! operator on the upload snippets

@rosariopfernandes as always, LGTM!


OperationException(linkException: ResponseFormatException(originalException: FormatException: Unexpected end of input (at character 1)

1
Previously I was using graphql version 3.1.0 and it was working fine, able to receive request as expected, but recently I had to update my flutter version to 2.10.3 and all other packages, including graphql.
Now I am using v.5.1.0 and I suddenly get this error.
Only changed the documentNode to document in Query. I built the request as per the documentation.
Also posted it here
main.dart
@override
  void initState() {
    GraphQLRepository.instance.initializeClient();
    super.initState();
  }

GraphQLProvider(client: GraphQLRepository.instance.graphQLClientValueNotifier,child: MaterialApp....

Graphql Repository
class GraphQLRepository {
  factory GraphQLRepository() {
    return instance;
  }

  GraphQLRepository._();

  static final GraphQLRepository instance = GraphQLRepository._();
  GraphQLClient _graphQLClient;
  ValueNotifier<GraphQLClient> _graphQLClientValueNotifier;

  GraphQLClient get graphQlClient => _graphQLClient;
  ValueNotifier<GraphQLClient> get graphQLClientValueNotifier =>
      _graphQLClientValueNotifier;

  void initializeClient() {
    _graphQLClientValueNotifier = GraphqlClient.initializeClient();
    _graphQLClient = _graphQLClientValueNotifier.value;
    return;
  }
}

Client
class GraphqlClient {
  static String _token;

  static final HttpLink httpLink = HttpLink(
     serverUrl,
  );

  static final AuthLink authLink = AuthLink(getToken: () async {
    _token = 'Bearer $accountKey, Bearer $sessionKey';
    return _token ?? '';
  });

  static final Link link = authLink.concat(httpLink);

  static ValueNotifier<GraphQLClient> initializeClient() {
    final policies = Policies(
      fetch: FetchPolicy.networkOnly,
    );

    final ValueNotifier<GraphQLClient> client = ValueNotifier<GraphQLClient>(
      GraphQLClient(
        cache: GraphQLCache(store: HiveStore()),
        link: link,
        defaultPolicies: DefaultPolicies(
          watchQuery: policies,
          query: policies,
          mutate: policies,
        ),
      ),
    );
    return client;
  }
}

Response
{
  "data": {
    "balanceList": {
      "data": [
        {
          "currency": "GBP",
          "amount": 1000,
          "pendingAmount": 199,
          "holdAmount": 0,
          "availableBalance": 801
        },
        {
          "currency": "EUR",
          "amount": 1000000,
          "pendingAmount": 647,
          "holdAmount": 0,
          "availableBalance": 999353
        }
      ]
    }
  }
}

Previously I was using graphql version 3.1.0 and it was working fine, able to receive request as expected, but recently I had to update my flutter version to 2.10.3 and all other packages, including graphql.

Welcome to the present.
Try to look in the migrate guide https://github.com/zino-hofmann/graphql-flutter/blob/main/changelog-v3-v4.md this will solve your problem!
In addition, your query needs to contain __typename as described in the example https://github.com/zino-hofmann/graphql-flutter/blob/main/packages/graphql/README.md#query

Already followed the migration guide
documentNode: gql(...) is now document: gql(...)
added __typename
Remove uri in httpLink
Expected Response
query BalanceList {
  balanceList {
    ... on BalanceList {
      data {
        __typename
        currency
        amount
        pendingAmount
        holdAmount
        availableBalance
      }
    }
    ... on ResponseErrors {
      errors {
        __typename
        message
        code
        displayMessage
        ... on InternalError {
          __typename
          message
          code
          displayMessage
          context
        }
      }
    }
  }
}

Maybe adding the stack trace can be helpful!


Make fvp work for anything other than aarch64 when being set as the test machine

The current picolibc changes can't handle fvp being set as the test machine for anything other than aarch64. If fvp isn't set, it defaults to qemu, which works for now because the ARM fvp doesn't require anything special.
However, when adding new aarch64 big-endian variants, one of the picolibc patches includes test-machine as an option in the Meson build scripts. Consequently, the library's CMake needs to set this option using -Dtest-machine=${TEST_EXECUTOR}. This means that for the armv8.1m library variant,we are explicitly passing the FPU, which can cause the error fvp: requested test machine not found since fvps are only defined for the aarch64 case.

While this does solve the problem, it looks like it means an fvp version of the startup code will now be produced for everything, even though for non-AArch64 it's identical to the standard code. That duplication of work seems very inefficient: if the same code works for both test executors, it makes more sense to me to use it for both instead of generating two versions for the sake of satisfying an expected filename.

While this does solve the problem, it looks like it means an fvp version of the startup code will now be produced for everything, even though for non-AArch64 it's identical to the standard code. That duplication of work seems very inefficient: if the same code works for both test executors, it makes more sense to me to use it for both instead of generating two versions for the sake of satisfying an expected filename.

I don't understand why it's considered inefficient since the startup code is copied separately into the specific library variants during packaging anyways. Essentially, this is just a name change. Although the startup code for ARMv8.1-M appears similar between FVP and QEMU, we will have FVP-specific boot code changes in the ARM crt0.c file for the A and R profiles in the future.

While this does solve the problem, it looks like it means an fvp version of the startup code will now be produced for everything, even though for non-AArch64 it's identical to the standard code. That duplication of work seems very inefficient: if the same code works for both test executors, it makes more sense to me to use it for both instead of generating two versions for the sake of satisfying an expected filename.

At the moment we don't have a separate boot code changes for non-aarch64. But we will need separate QEMU/FVP startup code for A-profile AArch32, and probably R-profile AArch32 in the future. Building one bootcode object for M-profile could be an option, but  building two objects would simplify things, and the bootcode objects are small so the compile time or distribution size is not going to be a big problem.


Subcolumns of a sheet are not detected properly (no name given, just 'Column '

Hello,
I just tried to analyse a xlsx file and this file uses table formatting so I'm able to filter for columns etc. Furthermore there is a column which has sub-columns like this (see the columns with years like 2014, 2015, ...):

This is parsed as:

I think is is somehow a bug or feature request. I'm sorry if I did something wrong - I'm new to this project and it's my first try!

Could you be specific what's your expectation? OpenRefine can import the excel but does not support the filter like Excel does. The similar functionality of is facade though which you can filter the data and edit them by batch.

I think the desirable behaviour in this case would be to name columns based on the hierarchy of their heading columns. In this case I could see having the columns:

Ressort
Zuwendungsempfanger
Haushalts-stelle(n)
Zuwendungszweck
Institutionnelle Zuwendungen Bremen - 2014
Institutionnelle Zuwendungen Bremen - 2015
Project-forderungen Bremens - 2014
Project-forderungen Bremens - 2015
Institutionelle Forderung / Projektforderung Dritter - 2014
Institutionelle Forderung / Projektforderung Dritter - 2015
Finance-rungsart
Stadteil

However, whether this is achievable based on the information available to us in the Excel file I don't know.
@GiantCrocodile are you able to share an example Excel file with us?

I am not sure it is possible to importing the sub-column like you expect. But supporting "Column Groups" and "importing a auto-filtered excel" seems different. Auto-filter is a "view" of the excel, not the real data get saved. Alternatively, you can manually merge your 2nd row with 1st row to build a header and import into OpenRefine.


Device - cast - support

Preconditions:
Swag-lyrics turned on - currently playing.

Alexa Echo bot.

To Reproduce
Steps to reproduce the behavior:

Click on "Devices Available"
Click on "Connected device"
See error

Expected behavior
Lyrics showed up.
Actual result:
<
Nothing Playing.
Lyrics unavailable for by .

If I understand this correctly, you're playing music through Alexa Echo but controlling it through Spotify on your PC? And SwagLyrics does not display lyrics in that case?

Correct, aadibajpai.

Correct, aadibajpai.

That's actually an issue with Spotify since they do not set the playing info on your device if the music is playing on some other device. I'll transfer this issue to https://github.com/SwagLyrics/SwSpotify for further monitoring.


[INLONG-7218][CI] Add Windows support on GitHub Actions

Fixes #7218
Motivation
We can use jobs.<job_id>.runs-on to define the type of machine to run the job on.
See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idruns-on
Modifications
Add Windows support on GitHub Actions when building and testing InLong.

@dockerzhang Windows, Linux and MacOS are all available GitHub-hosted runner types. Should we support MacOS on GitHub Actions?

@shink it's better to add the action for MacOS. Thanks.

@dockerzhang PTAL.

@shink, the CI workflow run failed for windows os. Please fix it.

@dockerzhang
It seems that there are some codes that do not support cross-platform.
See https://github.com/shink/inlong/actions/runs/4097168091/jobs/7065344093#step:6:2138
File.separator is used as a regex; will not work on Windows.

@dockerzhang PTAL


Typo in example

https://github.com/jscad/OpenJSCAD.org/blob/6c7be85d7e208a2b100c3bce10380ada8f9d7e32/packages/modeling/src/primitives/polyhedron.js#L21
It should be "mypoints" instead of "mypoint"

Fixed and released. Thanks for the help @Sefanor


question re: instant client

Hi again Vincent:
We continue to test our application using OCILIB 4.7.2 along with Instant Client 21.1 using AddressSanitizer, and we're seeing a hang at shutdown in Oracle library:
(gdb) thread apply all bt

Thread 1 (Thread 0x7fd811d02d00 (LWP 1202791)):
#0  __lll_lock_wait (futex=futex@entry=0x7fd815be83c0, private=0) at lowlevellock.c:52
#1  0x00007fd815bf50a3 in __GI___pthread_mutex_lock (mutex=0x7fd815be83c0) at ../nptl/pthread_mutex_lock.c:80
#2  0x00007fd815be1718 in _Unwind_Find_FDE () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#3  0x00007fd815bdd848 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#4  0x00007fd815bdea10 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#5  0x00007fd815bdf75c in _Unwind_Backtrace () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#6  0x00007fd81634ea28 in ?? () from /lib/x86_64-linux-gnu/libasan.so.5
#7  0x00007fd816324862 in free () from /lib/x86_64-linux-gnu/libasan.so.5
#8  0x00007fd815be160d in __deregister_frame_info_bases () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#9  0x00007fd7decc08ce in __do_deregister_frame () from /build/share/oracle/instantclient_21_1/libociei.so
#10 0x00007fd7decc0947 in __icrt_terminate () from /build/share/oracle/instantclient_21_1/libociei.so
#11 0x00007ffea8f42e10 in ?? ()
#12 0x00007fd7decc0c49 in _fini () from /build/share/oracle/instantclient_21_1/libociei.so
#13 0x00007ffea8f42e10 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

As noted above, this is the only thread running, and the main() function has already exited.
Just wanted to ask if you think that OCILIB may be implicated in some way?  FWIW, we don't see this unless we run under ASAN, so we suspect that ASAN itself may be the root cause of this.
NOTE: this is on Ubuntu 20.04, running under ASAN w/clang 10.  Also, this is consistent -- we must kill process with -9.
Thanks for any suggestions you may have!

Hi,
OCILIB codebase does not use any OS/library locking/threading primitives.
It relies on Oracle clients mutex/threads primitives only if you initialize OCILIB in OCI_ENV_THREADED.
And as the stack trace involve libasan thus I would think that is related to ASAN.
In this case, I am afraid that I won't be able to bring help :(
Regards,
Vincent

Thanks Vincent!  That's kind of what I thought, but I figured I would at least ask ...


[FEATURE] Include configurations to disable/throttle appearance

It would be awesome if users of the package (and their extensions) had an easy, 'official' way to control appearance of the page.
For the end-users, it might manifest as two settings:
extension.showWhatsNew (true/false)
extension.whatsNewThreshold ('patch', 'minor', 'major')
@alefragnani I'd love to hear what you think about implementation for this. Could be a combination of snippets, instructions, or more tangibly but I think this would help adoption and be appreciated by users :)

Hi @ryanraposo ,
I think, if the package would let the end user to control if the What's New page should be displayed, I wouldn't create another setting. Instead, I would use the already existing "update.showReleaseNotes" setting, from VS Code itself. This is based on the feedback from some users, which don't like the page 😃 .
Defined as true, the package works as today, showing the What's New page on Major and Minor releases (remember, patches are silent). Defined as false, it never shows.
But, this feature must be opt-in. The extension author needs to enable it while initializing/registering the package. By default, it should be disabled, and the user wouldn't be able to decide if the What's New page will be displayed or not, when a new version (Major or Minor) is installed.
The threshold setting, on the other hand, I don't think is necessary.
Hope this helps

Hi @ryanraposo ,
I think, if the package would let the end user to control if the What's New page should be displayed, I wouldn't create another setting. Instead, I would use the already existing "update.showReleaseNotes" setting, from VS Code itself. This is based on the feedback from some users, which don't like the page 😃 .
Defined as true, the package works as today, showing the What's New page on Major and Minor releases (remember, patches are silent). Defined as false, it never shows.
But, this feature must be opt-in. The extension author needs to enable it while initializing/registering the package. By default, it should be disabled, and the user wouldn't be able to decide if the What's New page will be displayed or not, when a new version (Major or Minor) is installed.
The threshold setting, on the other hand, I don't think is necessary.
Hope this helps

Hi @ryanraposo ,
I think, if the package would let the end user to control if the What's New page should be displayed, I wouldn't create another setting. Instead, I would use the already existing "update.showReleaseNotes" setting, from VS Code itself. This is based on the feedback from some users, which don't like the page 😃 .
Defined as true, the package works as today, showing the What's New page on Major and Minor releases (remember, patches are silent). Defined as false, it never shows.
But, this feature must be opt-in. The extension author needs to enable it while initializing/registering the package. By default, it should be disabled, and the user wouldn't be able to decide if the What's New page will be displayed or not, when a new version (Major or Minor) is installed.
The threshold setting, on the other hand, I don't think is necessary.
Hope this helps

Thanks! Solid points and drawn from collected feedback, can't go wrong.
In my project I think I'm going launch it with a specific, substantial feature release and experiment with two things:

On that launch, show a notification that asks if they want to continue being informed about releases
The threshold/enable configs wired to "Show more", "Show less", "Disable" options on the page every time

I'll let you know what I learn from feedback in return :)

Hi @ryanraposo ,
I think, if the package would let the end user to control if the What's New page should be displayed, I wouldn't create another setting. Instead, I would use the already existing "update.showReleaseNotes" setting, from VS Code itself. This is based on the feedback from some users, which don't like the page 😃 .
Defined as true, the package works as today, showing the What's New page on Major and Minor releases (remember, patches are silent). Defined as false, it never shows.
But, this feature must be opt-in. The extension author needs to enable it while initializing/registering the package. By default, it should be disabled, and the user wouldn't be able to decide if the What's New page will be displayed or not, when a new version (Major or Minor) is installed.
The threshold setting, on the other hand, I don't think is necessary.
Hope this helps

Thanks! Solid points and drawn from collected feedback, can't go wrong.
In my project I think I'm going launch it with a specific, substantial feature release and experiment with two things:

On that launch, show a notification that asks if they want to continue being informed about releases
The threshold/enable configs wired to "Show more", "Show less", "Disable" options on the page every time

I'll let you know what I learn from feedback in return :)

I'm also very interested in automation for this feature in general, so I'll share any of that with you too. Thinking about workflows for targeted releases, with drop-in for screenshot demos, blurbs, etc.
Basically, automate quick prep of "fancy" editions that show something off.

I'm also very interested in automation for this feature in general, so I'll share any of that with you too. Thinking about workflows for targeted releases, with drop-in for screenshot demos, blurbs, etc.
Basically, automate quick prep of "fancy" editions that show something off.

I'm going to try very hard to remember my bias, because over the course of about 100 'Whats New in Bookmarks' I had no thoughts other than 'damn thats clean. I need something like that.' 😂

I'm going to try very hard to remember my bias, because over the course of about 100 'Whats New in Bookmarks' I had no thoughts other than 'damn thats clean. I need something like that.' 😂

That't great!
I suggest you to take a look at two issues the VS Code team itself has about this. One is basically what we are talking about here (https://github.com/microsoft/vscode/issues/110507), the other is more like a "native" alternative this this repo (https://github.com/microsoft/vscode/issues/102139).
Neither one is planned for upcoming releases (just Backlog milestone for now), but are very rich in details and feedback.
I have no intention in replace this package once https://github.com/microsoft/vscode/issues/102139 is released. But I keep my eyes on it. Maybe I use it somehow 😬 .
Hope this help

That't great!
I suggest you to take a look at two issues the VS Code team itself has about this. One is basically what we are talking about here (https://github.com/microsoft/vscode/issues/110507), the other is more like a "native" alternative this this repo (https://github.com/microsoft/vscode/issues/102139).
Neither one is planned for upcoming releases (just Backlog milestone for now), but are very rich in details and feedback.
I have no intention in replace this package once https://github.com/microsoft/vscode/issues/102139 is released. But I keep my eyes on it. Maybe I use it somehow 😬 .
Hope this help

There is no need to close the issue, if you intend to contribute to the package 😬

There is no need to close the issue, if you intend to contribute to the package 😬

@alefragnani so appreciated. thanks. 🙏I'll be keeping an eye out for what you decide on re: the incoming official stuff! And for contributing, I plan on taking what we've talked about, trying my hand in my own extension's context, and then opening a PR here depending on how it all goes.

@alefragnani so appreciated. thanks. 🙏I'll be keeping an eye out for what you decide on re: the incoming official stuff! And for contributing, I plan on taking what we've talked about, trying my hand in my own extension's context, and then opening a PR here depending on how it all goes.

That's great. Looking forward about how it goes.
Thank you!

That's great. Looking forward about how it goes.
Thank you!


Set OPENSSL_ROOT to ensure the correct OpenSSL version is located

This addresses the issue described in #432

Thanks


kubeclarity: 2.21.1 -> 2.22.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/openclarity/kubeclarity/releases.
meta.description for kubeclarity is: Kubernetes runtime scanner
meta.homepage for kubeclarity is: https://github.com/openclarity/kubeclarity
meta.changelog for kubeclarity is: https://github.com/openclarity/kubeclarity/releases/tag/v2.22.0
Updates performed

Golang update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.22.0 in filename of file in /nix/store/igx245qbkmj6qi6nzvw4p2v1cxhr8dxh-kubeclarity-2.22.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
kubeclarity

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/igx245qbkmj6qi6nzvw4p2v1cxhr8dxh-kubeclarity-2.22.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kubeclarity https://github.com/r-ryantm/nixpkgs/archive/eda430b89e86a882992f8f5e9dc28fa0f64d6d19.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/eda430b89e86a882992f8f5e9dc28fa0f64d6d19#kubeclarity

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/igx245qbkmj6qi6nzvw4p2v1cxhr8dxh-kubeclarity-2.22.0
ls -la /nix/store/igx245qbkmj6qi6nzvw4p2v1cxhr8dxh-kubeclarity-2.22.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kubeclarity

Maintainer pings
cc @fabaff for testing.

@ofborg eval


There is sth wrong with ./annotator/grounded-sam/run.py

I modify the args and used
python ./annotator/grounded-sam/run.py --dataset_root ./single/ --partition 1。
Under groundsam_vis folder，I got 001.png.mask.jpg  and 001.png.mask.png. The original size of pic is 540960, 001.png.mask.png is 540960, but it is all black. 001.png.mask.jpg's foreground color is yellow and its background is purple,
but its size is 1299 x 2310.

I noticed that self.ref_mask_path_web = '{}/groundsam/{}.mask.jpg' in tiktok_controlnet_t2i_imagevar_combine_specifcimg_web_upsquare.py. But /groundsam/{}.mask.png is not been called in anywhere. So why do we need to generate /groundsam/{}.mask.png?

I use groundsam/{}.mask.png. The generated png is not pure black, the fg area has the RGB value of (1, 1, 1)

@zhangtao22
How did you modify the grounded-sam/run.py?

Do we need to create a new argument for dataset_root?
What is "todo_folder_list"?
Where is "tiktok_scale_smalllist.txt"?


Resize a floating window around its center

I've been trying to add an effect to toggling a window into floating mode to make it a bit more obvious, and for that I wanted to resize the window around its center.
I tried this:
yabai -m query --windows id,frame --window |
  jq -er '"yabai -m window \(.id) --toggle float --resize top_left:\(.frame.w/40):\(.frame.h/40) --resize bottom_right:\(.frame.w/-40):\(.frame.h/-40)"' |
  sh -

# This executes something like this:
#   yabai -m window 157365 --toggle float --resize top_left:19.775:25.9 --resize bottom_right:-19.775:-25.9

But then I quickly noticed that it doesn't achieve what I wanted it to, as yabai ignores the first --resize I passed in. Not sure whether that should be considered a bug.
From a user experience perspective, I don't actually want to express this as two resizes anchored at opposite corners. All I wanted to do is shrink my window by 20% around its center. It'd be nice to have a dedicated window command for this, for example:
# x and y are absolute values; positive numbers grow, negative numbers shrink the window
yabai -m window --resize center:x:y

Because then my script could just be this:
yabai -m query --windows id,frame --window |
  jq -er '"yabai -m window \(.id) --toggle float --resize center:\(.frame.w/-20):\(.frame.h/-20)"' |
  sh -

I would consider that a bug. In fact it is caused by using a cached value of the window frame instead of requesting it from the AX API.
I'm not opposed to looking into adding a center "handle" to the resize command, but that will likely come at some other point in time. For now I'll just resolve the bug with your current method.

Awesome, thanks for the quick fix. I can confirm this works as expected now.

Fixed in v7.0.4. I'll keep this open as a suggestion for a new resize handle which may make this operation built-in in the future.

@dominiklohmann does this work for you on 7.0.4?
yabai -m query --windows id,frame --window |
  jq -er '"yabai -m window \(.id) --toggle float --resize center:\(.frame.w/-20):\(.frame.h/-20)"' |
  sh -

Or did you end up with a different syntax? The above doesn't work for me.

@Pe8er if you read the thread again you'll see that the center anchor was not implemented. Instead, the behavior for providing two resizes with different anchors at once was fixed, allowing you to achieve the same effect that a center anchor would have.

@dominiklohmann I see now, sorry for the oversight and thank you for clarification!


Create a skeletal PPP

Just the headings are enough. You can write to be added soon as placeholders for content.
PDF conversion not required.
Follow the details in the the CS2103T GitHub guide.

All updated


Feature: Support workload identity federation

This PR is to add support for Workload Identity Federation (OIDC) in the Terraform Task.
The intention is that this will be a non-breaking change, it will simply identify the authentication scheme and setup the provider accordingly.
Testing Evidence:
In order to run this test, the following steps were followed:

Compiled and packaged the extension as per the steps HERE.
Removed the public extension from the organisation.
Published the extension to the market place, shared it to the organisation and installed it in the organisation.
Deployed the Service Connection, Managed Identity, etc using this example code: https://github.com/Azure-Samples/azure-devops-terraform-oidc-ci-cd
Updated the oidc.yml pipeline to include the Terraform task steps (see below).
Ran the pipeline.

Pipeline Code

Test Extension

Service Connection

Terraform Init

Terraform Apply

The previous PR https://github.com/microsoft/azure-pipelines-terraform/pull/164 was closed in favour of this one.


Dataset API

The SDK PR is in the works. Meanwhile let's talk about the implications for the CLI...
As noted in the SDK planning ticket the Datasets API is a bit trickier as it involves two resources types: Datasets which are collections of Features.  Then there are all of the standard "CRUD" operations on those resources.
How do we best represent these actions in the CLI? My initial thought is sub-sub-commands like:
mapbox dataset list-features
               read-features
               update-features
               delete-features
               list-datasets
               create-datasets
               read-datasets

Related: https://github.com/mapbox/mapbox-data-cli

@emilymcafee - that looks great, we'll probably follow the design of mapbox-data-cli pretty closely for this tool.

@perrygeo as per discussion yesterday, I think mapbox datasets action-resource will be a fine pattern.
There's a bug in our Datasets API documention. It says

Using the dataset API involves interacting with two types of resources: a dataset, which is a collection of features.

But there are actually four types of resources in /datasets/v1/{account}/{dataset}/features/{feature}:

The datasets container /datasets/v1/{account}.
The dataset /datasets/v1/{account}/{dataset}.
The dataset's feature container /datasets/v1/{account}/{dataset}/features.
The feature /datasets/v1/{account}/{dataset}/features/{feature}.

GETs on these 4 different URLs give 4 different responses. 4 different kinds of resources.
So, I propose we change your sketch above to
mapbox datasets list
mapbox datasets create [args]

mapbox datasets read-dataset DSNAME [args]
mapbox datasets update-dataset DSNAME [args]
mapbox datasets delete-dataset DSNAME [args]

mapbox datasets list-features DSNAME [args]
mapbox datasets batch-update-features DSNAME [args]

mapbox datasets read-feature DSNAME FNAME [args]
mapbox datasets update-feature DSNAME FNAME [args]
mapbox datasets delete-feature DSNAME FNAME [args]

Worth combining the DSNAME and FNAME into one argument? Something like DSNAME:FNAME?

:clap: that's clarifies things immensely! Thanks @sgillies - maybe once we're done here we can suggest some api documentation changes.
I like separate args for easier composibility.
In terms of DSNAME and FNAME, are you refering to the id or actual names (feature name not being standard unless we require a properties.name which is icky)

I'm using name and id interchangeably.

there are actually four types of resources

Hmm. I didn't consider the list of datasets as a distinct resource, but I see your point. If you think its confusing I'm happy to update the docs.
I'll jump on this as soon as @sgillies' work on the sdk wraps up.

I've started putting this together, and I'm getting to the batch_update_features function, which is always the problematic one.
From the CLI perspective, the goal in mapbox-data-cli was basically to expose three subcommands:

mapbox dataset put-features: insert or update a set of features, performing as many backend requests as needed to get through the feature set
mapbox dataset delete-features: delete a set of features, performing as many backend requests as needed to get through the id set
mapbox dataset replace-dataset: list the ids in the dataset, delete them all and/or replace them with the features provided

Hidden here is a more generic question about how we want to handle "higher-level" commands that might result in multiple API requests.

Closed via #32.


Supported Versions of :all-the-things:

Problem
Presently we offer no guidance as to what versions of any of our dependencies we support/rely on.
The two which come to mind most readily:

PostgreSQL
JSON Schema

There are significant differences between each version of PSQL and each draft of JSON Schema.
Suggestion
For JSON Schema we pick a single version we support. For PSQL, I think that supporting multiple versions is reasonable and should be as simple as updating our CI to fan out over various versions of PSQL.
Suggested Musical Pairing
https://soundcloud.com/sylvanesso/hskt

@AlexanderMann  Purely from a postgres perspective, I think 9.0+ is all we need to support. Perhaps even just 9.4+.
If this gains something from being able to test redshift (which was forked from 8.2 many years ago), then I could see an argument.
Based on feedback from Stitch, I think we can go with Draft 4 of JSON Schema. I added an issue in the backlog to validate incoming JSON Schema. If it doesn't match Draft 4, we can warn or throw an exception. https://github.com/datamill-co/target-postgres/issues/20


Hi and thanks Ilmoi! <3

Thank you very much for your amazing tool - it's been a huge help!

Hi ilmoi,
I am just writing to thank you - one of your many tools (NFTArmory) has been a huge help in the creation of my collection
[mostly for having all the minted NFT's data/addresses in one neat folder]
(really - I had difficulty finding a tool that could properly query my entire collection - kind of disappointed with SOLANA - the NFT creation process is meh at best.)
Just wanted to say that I am truly grateful for the obvious efforts you've put towards your tool, and would like to send you a few NFT's as a token of my appreciation.
I don't use Twitter so I apologize for this method of contacting!
Please feel free to add me on discord at Oasis Cover Band#9047 to pass me your Solana address <3
or you can find me here https://discord.gg/superpixelers
Once again - thank you so much for your amazing work - it's truly appreciated and by far the best NFT metadata tool I could find - you are truly special!
Thanks a million.

Really appreciate the kind words <3 I'm going to close the PR, just not to merge the txt file in, but again really appreciate you taking the time to write this!


image still a problem

Still not fixed.
You need to update the version of the whatsapp-web.js library.
maybe it is also this problem...
https://github.com/pedroslopez/whatsapp-web.js/issues/2081

https://github.com/pedroslopez/whatsapp-web.js is not the library used.