Add: :tool reference module [WIP]

This module add reference (bibtex) support to org-mode and elfeed, it can also replace the bibtex settings in the latex module.
Features and workflows is documented in the readme.org file. Mainly:

Async download of bibtex entry and PDF from DOI or elfeed feeds
Ivy-bibtex frontend for org-ref (originally only comes with helm-bibtex)
A library of applescript to interact with Skim.app in macOS to create highlights and link to notes in org-mode. The links are bi-directional between PDF and org-mode.

This module as well as the latex module define different parameters for the biblatex package.
What would be the best way to handle this type of situations @hlissner?

@UndeadKernel my thought was to merge the two settings and let this module handle all bibtex related settings.

I'll probably get to this later in the week. I gave up and ended up using Mendeley as a short-term fix for my stack of papers. I have been using Org-noter for classes and it's decent.

Ah....I guess I accidentally deleted the branch in Magit....

A lot of the functions defined seem Mac specific, could there be an OS check before loading them?

@HaoZeke that would be fantastic.
regarding the snippet above, will it also work in the autoload.el file?

Hi @fuxialexander. To selectively load autoloads based on the MAC os, I imagine you can write at the top most of the file:
;;; modules/tools/reference/autoload/applescript.el -*- lexical-binding: t; -*-
;;;###if IS-MAC

@hlissner, could you confirm if this would just work?

Yes, that should work.
It will instruct the autoloads generator (and byte-compiler) to ignore that file if the condition fails.

Sorry for the late response. Would you mind moving this module into lang/org behind a +ref flag? i.e.

tools/reference/README.org -> lang/org/contrib/ref.org
tools/reference/config.el -> lang/org/contrib/ref.el
tools/reference/packages.el -> lang/org/packages.el
tools/reference/autoload/applescript.el -> lang/org/autoload/contrib-ref-applescript.el
tools/reference/autoload/org-ref-ivy.el -> lang/org/autoload/contrib-ref.el

Sure. Will do that in the coming days.

Hi @hlissner , I've refactored this module accordingly.

@fuxialexander Sorry to spring this on you suddenly. I'm prepping to merge the straight branch soon, which imposes a couple widespread changes. If it isn't too much trouble, could you retarget this PR at the straight branch? Otherwise, I can look into it myself once the branch has been merged.

@hlissner Sure. I'll have a try.

It's only in the documentation... as an example. You can of course (and need to) set the variable to whatever you want.
Ahh yes, that is just the documentation in an org file, sorry. :grin:

It's only in the documentation... as an example. You can of course (and need to) set the variable to whatever you want.

Ahh sorry, yeah that is just the documentation. This tool is a great help.

Now that I've almost finished the integration between org-noter, org-pdftools and pdftools, I'm considering to split this PR into two parts: one PR to the :tools pdf module as +skim-note and +pdftools-note flag, dedicating to PDF note-taking; and another PR to this :lang org module as +ref flag, dedicating to reference management. What's your opinion about this? @hlissner @Emiller88 @nbk9 @chengyi @HaoZeke
Reference:
https://github.com/weirdNox/org-noter/pull/75
https://github.com/fuxialexander/org-pdftools

@fuxialexander org-pdfview is no longer maintained. markus1189 has listed your org-pdftools as the alternative, better to use org-pdftools when featurep! :tools pdf instead?


Data directory writable

Does the data directory need to be writable by the web server user after the db.sqlite file has been created? (Obviously the database file itself needs to be writable.)
Unless the data directory is also used for temporary files or the database file needs to be recreated at some point, relaxing that requirement would allow (as far as I can see) users not to make the data directory world-writable after file creation or not require root access during installation (to change the owner of the data directory to the web server user).

database file needs to be recreated at some point

Well, you can create more than one database at any time.

Unless the data directory is also used for temporary files

According to http://www.pantz.org/software/sqlite/unabletoopendbsqliteerror.html sqlite creates temporary transaction files at the same directory the database file is kept. I have seen those temporary files as well, while using a sqlite database editor.

Right. That answers my question.


fix: the signature unmatch in async trait function

What's changed and what's your intention?
When we use state_table.iter() in a async trait function, it shows a confusing compiler error about signature mismatch. I think it's compiler's problem but I do not get too many evidence. I just removed the unnecessary closure mentioned in the error and it seems work.
@wcy-fdu can you please check that it fixs your problem? I have tested it on my version.
The compiler error looks like:

Because the .map looks unnecessary, so I just removed it.
Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

I also provide a PR if you want to test locally #2999 : https://github.com/singularity-data/risingwave/pull/2999/commits/2a7e5156b1293e7ac6d26f449a3f6ece71bfbc27


DBZ-677 Updating docs for renamed SMTs

@gunnarmorling Should not the left bar menu be changed too?

Ah yes, good point. Perhaps you could do it tomorrow?


Add telegram link to footer

Add telegram icon/URL to the footer to match https://github.com/MyCryptoHQ/MyCrypto/blob/master/src/config/links.ts

@MrLuit can you create the branch directly from landing repo not the fork ? It will fix the problems with actions :)


Migrate ollama to jackson

Issue

#1042
Change

Migrate Ollama module from Gson to Jackson. But we still need to migrate langchain4j-core and openai4j too.

Note that there are three things confused me(these issues exist in original ollama module):

I observe that some tests with inputTokenCount Assertion (such as assertThat(tokenUsage.inputTokenCount()).isEqualTo(35)) failed because of the differencet count of input tokens. I don't know whether it's because Ollama's update. Now I correct it
should_propagate_failure_to_handler_onError in Streaming{xxx}ModelIT failed in my local because NullPointerException do not have any message. Is it a problem in my local environment?
Somtimes if I run tests individually, all tests will pass. But if I run them in the same time(such as using command line rather than IDE), they will failed due to some strange reasons(e.g. input token usage will be null). I think Maybe it's a network problem or Testcontainers's problem.

I'm not sure if these problems are due to my local environment, so if you have any suggestions or solutions, please let me know!
General checklist

[x] There are no breaking changes
[ ] I have added unit and integration tests for my change
[x] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[x] I have manually run all the unit and integration tests in the core and main modules, and they are all green

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)

Checklist for adding new model integration

[ ] I have added my new module in the BOM

Checklist for adding new embedding store integration

[ ] I have added a {NameOfIntegration}EmbeddingStoreIT that extends from either EmbeddingStoreIT or EmbeddingStoreWithFilteringIT
[ ] I have added my new module in the BOM

Checklist for changing existing embedding store integration

[ ] I have manually verified that the {NameOfIntegration}EmbeddingStore works correctly with the data persisted using the latest released version of LangChain4j

Hi @Martin7-1 thanks a lot! I will try to review it asap!

Hi, thanks a lot!
This PR should wait till we release the first migration from Gson to Jackson (Anthropic module) and see that it actually works.
We can then proceed with this PR and migrating other modules.

I found a strange thing that all numPredict parameter failed to restrict the max output token in tests.

BTW, I found that there are some token usage differences. I don't know what the reason is


Merge config if passed when using auto feature

Right now we overwrite any config passed in when using auto on width or height.

Fixed here https://github.com/souporserious/react-motion-ui-pack/commit/a42dc705945d3dd00d0842e526b272ae21823202#diff-fc5e09db46647eb4cbfd02c2dfde98d2R185


Support React Native

Hi!
Is there any plan to support React Native?
Thanks!

Hi, we have react-native-lock-ios that is a wrapper for the iOS Lock library and react-native-lock-android for Android. Both support passwordless authentication. They look different than lock-passwordless, but and update is on the way.

Thank you. This should be added to the Readme, so other people can find them easily :)

Done, thanks for the suggestion! :dancers:


POA module data presentation issues

Incorrect time period;
incorrect number of nodes currently online in the network;
the wrong reward obtained

It's back to normal.


Switch back guaranteed producer

All bugs in the driver related to this has been fixed, so this is ready to go.
The memory leak wasn't found yet, so after deploying this we'd need to watch the memory really closely.
cc @wikimedia/services

Coverage increased (+3.6%) to 89.873% when pulling 6e81beb68b990a849d8ae895777fbfe881a1c20c on Pchelolo:guaranteed_again into ca54ef0bbf525ca091abdb3b591234e45cd9a75e on wikimedia:master.

The vacation times are over, let's get this moving?


New Runtime Features

Features:

Shell API
Getting CPU Count
WIP Threads
New File structure
cpuid function
WIP support for non-x64 cpu's

Blocked-by: https://github.com/runtimejs/runtime/issues/156


Test mods + Export-DbaLogin now outputs Get-ChildItem

NBD test updates that silence warnings, but Fred will fix that. Ultimately, I like this PR cuz it changes the behavior of Export-DbaLogin.

unrelated failures


Problem with fill highlight

whats the highlight for the fill of the bufferline

Just merged a PR that adds a fill_hl option. Hope that works!


7.0.0.dev Upstream "Proxy Authentication Required", possibly related to #4355

Problem Description
407 Authentication required
Setting an upstream proxy following options in all of mitmproxy, mitmweb and inside python scripts :
System Information
Mitmproxy: 7.0.0.dev
Python:    3.9.1
OpenSSL:   OpenSSL 1.1.1i
Steps to reproduce the behavior:
mitmweb --mode 'upstream:http://localhost:1337' --upstream-auth testuser:testpass
mitmproxy --mode 'upstream:http://localhost:1337' --upstream-auth testuser:testpass
options = Options(
    listen_host='<IP_ADDRESS>',
    listen_port=8080,
    upstream_auth='testuser:testpass',
    mode='upstream:http://localhost:1337',
)

Then set mitmproxy, mitmweb or set upstream auth in Python.
I tested on multiple auth required proxies, can test easily with tinyproxy
mkdir -p ./tinyproxy

PROXY_USER=testuser
PROXY_PASS=testpass
PROXY_PORT=1337

tee ./tinyproxy/tinyproxy.conf <<EOF
User tinyproxy
Group tinyproxy
Listen <IP_ADDRESS>
Port ${PROXY_PORT}
Timeout 600
LogFile "./tinyproxy/tinyproxy.log"
LogLevel Info
MaxRequestsPerChild 0
MaxClients 100
StartServers 10
# Allow <IP_ADDRESS>
# Allow ::1
BasicAuth ${PROXY_USER} ${PROXY_PASS}
DisableViaHeader Yes
EOF

tinyproxy -d -c ./tinyproxy/tinyproxy.conf

#curl -x testuser:testpass@localhost:1337 api.ipify.org

Error
Addon error: Traceback (most recent call last):
  File "./lib/python3.9/site-packages/mitmproxy/addons/view.py", line 568, in error
    self.update([f])
  File "./lib/python3.9/site-packages/mitmproxy/addons/view.py", line 612, in update
    self.sig_view_update.send(self, flow=f)
  File "./lib/python3.9/site-packages/blinker/base.py", line 266, in send
    return [(receiver, receiver(sender, **kwargs))
  File "./lib/python3.9/site-packages/blinker/base.py", line 266, in <listcomp>
    return [(receiver, receiver(sender, **kwargs))
  File "./lib/python3.9/site-packages/mitmproxy/tools/web/master.py", line 57, in _sig_view_update
    app.ClientConnection.broadcast(
  File "./lib/python3.9/site-packages/mitmproxy/tools/web/app.py", line 214, in broadcast
    message = json.dumps(kwargs, ensure_ascii=False).encode("utf8", "surrogateescape")
  File "/usr/lib/python3.9/json/__init__.py", line 234, in dumps
    return cls(
  File "/usr/lib/python3.9/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.9/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.9/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type bytes is not JSON serializable

Addon error: Traceback (most recent call last):
  File "./lib/python3.9/site-packages/mitmproxy/addons/view.py", line 612, in update
    self.sig_view_update.send(self, flow=f)
  File "./lib/python3.9/site-packages/blinker/base.py", line 266, in send
    return [(receiver, receiver(sender, **kwargs))
  File "./lib/python3.9/site-packages/blinker/base.py", line 266, in <listcomp>
    return [(receiver, receiver(sender, **kwargs))
  File "./lib/python3.9/site-packages/mitmproxy/tools/web/master.py", line 57, in _sig_view_update
    app.ClientConnection.broadcast(
  File "./lib/python3.9/site-packages/mitmproxy/tools/web/app.py", line 214, in broadcast
    message = json.dumps(kwargs, ensure_ascii=False).encode("utf8", "surrogateescape")
  File "/usr/lib/python3.9/json/__init__.py", line 234, in dumps
    return cls(
  File "/usr/lib/python3.9/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.9/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python3.9/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type bytes is not JSON serializable

Request then ultimately fails and returns 407 Proxy Authentication Required

The upstream_auth option is not implemented yet in the new core, although it should be relatively trivial to add. The error your are seeing is unrelated and will be fixed by #4357.
I'll close this here in favor of  https://github.com/mitmproxy/mitmproxy/issues/4348. Thanks!

Fantastic, fixed in https://github.com/mitmproxy/mitmproxy/pull/4635


Laravel 8, where do I put require_once '/path/to/your-project/vendor/autoload.php';

I am using Laravel 8, it's a fresh project and just installed the dependency through composer. I have a few questions:
Where do I put this:
require_once '/path/to/your-project/vendor/autoload.php';

On the .env file I added this line:
YOUTUBE_TOKEN=googlecloudplatformapikey
Is that where you're supposed to place that? Im trying to make this work just by reading the documention in this repo and using this documentation: https://developers.google.com/youtube/v3 , if anyone knows of a video-tutorial or something else that might help my case, please share here as im new to this API.
Thanks!

Using laravel, you doesn't need put require_once '/path/to/your-project/vendor/autoload.php';, because laravel automatically load vendor autoload in /public/index.php.

Closing as this is answered.


Write tests

I agree that having tests would have been great, but when deciding between keeping this closed source and open-sourcing without tests, we decided for the latter one. You're more than welcome to contribute some tests @stevenvachon 🙂

I've gone back and forth a lot on this, and eventually landed on functional tests vs unit. Once you start mocking the CDP module it gets pretty hairy and unmaintainable quickly (since it's an extremely wide API). Would be curios to hear others' opinions.

+1 for the bulk of the tests being functional. Due to the nature of this library, unit tests wouldn't give me a ton of confidence that everything works properly.

I just noticed this thread. I ended up covering with mostly unti tests to start without mostly to learn the code base. See #188. I'll admit it's kind of messy, but hopefully it's a good start. I was kind of bouncing all over the place as I learned how each class is used (and using TypeScript for the first time).
I think the unti tests come in handy for a sanity check. As I was writing the tests I found a few spots where a method wasn't being called, i.e. const val = client.someMethod vs const val = client.someMethod(), and some if/else logic issues. Also, a few spots where the host/port wasn't being passed. It seems like the underlying chrome debugger protocol could change quite a bit, so I think unit tests can help ensure we're calling/using CDP correctly as it changes. The other thing is testing logic of things like uploading screenshots to S3, or a feature like clearing the input which involves a series of CDP calls.
Having said that, I think functional tests will be very necessary. In the real world, it doesn't always be have as expected in unit tests, or the call to CDP isn't quite right, etc. I think writing out some known HTML with form inputs, missing selectors, etc. would be helpful to test against, and serve that up locally and/or reference them on Github. Thoughts on this?


feat: use hashicorp/cronexpr for cron

This replaces our cron calculation with those provided by a 3rd party library.
Unfortunatly we still need to do our own parsing however, as we support additional syntax, and other parts of the code expect to be able to parse the Pattern using participle.
closess #1744

This is awesome! 🤩


Use AsRef for find_prop

This allows passing things like String or CStr and alike. Usually, it's good practice to use AsRef instad of &str for fuction parameters.
See: http://xion.io/post/code/rust-string-args.html

Mostly handy since I have a few situations where I need to compare to String.

waa, sorry, wrong button, meant to merge, not close 🙈

so I hope I can make that up by just releasing this immediately ;)
thanks for the contribution


how to use gst-plugin-pylon construct gstreamer project in c++?

hi,can you provide some examples to demonstrate how to use cmakelist to build c++projects?

As a first start two links;
One example to use cmake for Gstreamer is here:
https://stackoverflow.com/a/74038236
The plugin can be used like any other Gstreamer plugin.
We have some examples on how to use it programmatically here:  https://github.com/basler/gst-plugin-pylon/tree/main/tests/examples/pylon

As a first start two links;
One example to use cmake for Gstreamer is here: https://stackoverflow.com/a/74038236
The plugin can be used like any other Gstreamer plugin. We have some examples on how to use it programmatically here: https://github.com/basler/gst-plugin-pylon/tree/main/tests/examples/pylon

Thank you very much for your help, I would like to ask if this plugin can start the camera supported by the pylon package, can it take up less CPU resources than calling the pylon C++ interface directly?

The gstreamer pylon plugin is a based on the pylon c++ SDK. So what pylon supports, this plugin can also Support in principle ( In the limits of Gstreamer capabilities)
On what platform and  with which camera interface do you observe too much CPU ressources used ?

I'm running a gige protocol based camera on the xavier platform and it takes 30% of the cpu. Can I reduce it to around 10% if I use the gstreamer plugin?

@Junkai-Liu, important factor in gige performance is the size of the network packet, that are send.
To configure your host:

https://docs.baslerweb.com/network-configuration-(gige-cameras)#changing-the-network-adapter-properties-linux
To configure your camera if you can receive  e.g. 8192 byte per packet from your network settings:

gst-launch-1.0 pylonsrc cam::GevSCPSPacketSize=8192  ! videoconvert ! autovideosink


[Safari|IE|Firefox] Performance Issues

Hi, in the last days i builded a onepager with EQCSS. Two Sliders, one Accordion and Smoot Scrolling Anchor Navigation. Everything was fine on Chrome.
But on IE, Firefox and especially with Safari I had many Performancedrops, if one of the animations wants to start. The reaction after click is delayed and in the animation phase itself there is a short stop in the middle.
In total there were 15 EQCSS Conditions working in the background. The only browser that did not bother you was Chrome. As I said the whole falls on the other browsers synonymous then only properly when you animate elements.
I am testweise again changed back to the CQ-Prolyfill (https://github.com/ausi/cq-prolyfill)  there it runs without problems, but also stop fewer options.

Oh no! Sorry you're having a hard time with it @gisu
Do you have an example of the EQCSS-powered version that had the performance issues - I'd love to have a peek and see where they might be coming from, either if there's a way it could be refactored to run more smoothly or if this exposes some performance issues with the plugin we could improve!

Hi @gisu! Any update on this? I'd love to have a peek at code that can reproduce the problem to see what can be done about it :D

Ah sorry for the late reply. But an example I have unfortunately no longer. The site where I have integrated EQCSS is not yet public and now runs the CQ-Prolyfill.
I try to put the days but once a similar page, where you will see the problems then.


docs: updated getting started ios [ci skip]

This PR resolves []
Description
Updated the docs for opening xcode in the correct file now that the structure changed with the new app shell.

PR Checklist

[ ] I tested my changes on iOS / Android.
[ ] I added screenshots or videos to illustrate my changes.
[ ] I added Tests and Stories for my changes.
[ ] I added an app state migration.
[ ] I hid my changes behind a feature flag.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

updated getting started docs ios - gkartalis

Need help with something? Have a look at our docs, or get in touch with us.

Thanks for showing our docs some love! 🎉


Outline creating ClimateParams instance from fair params files in pkg

Creates scmcoat.utils.get_fairv1_climateparams(), which creates a scmcoat.ClimateParams instance from FaIR params files.
Using the "slim" and "common" JSON files from https://doi.org/10.5281/zenodo.6601980 because they're very small.
@kemccusker, you'd need to fill in the scmcoat.utils._climateparamslist2ds() with your existing code. Double check this produces comparable results!

Love it. Will give it a go. Thanks @brews !


How to write custom decode? Any good example?

For non-built-in types, it's necessary to write custom decode. But I'm still confused.
What's the difference among Custom(Arc<PgCustomType>), DeclareWithName(UStr) and DeclareWithOid(u32)? For example, for pg_lsn, sqlx would provide a Custom(Arc<PgCustomType>). But the PgCustomType is private, then how to write an accepts() for decode? And moreover, for simple query (unprepare), it seems sqlx would provide a DeclareWithOid(u32) for it. (https://github.com/launchbadge/sqlx/blob/master/sqlx-core/src/postgres/connection/describe.rs#L124). So for the same pg_lsn, it would have two possible type_info?
Another side question, in golang, the sql package provides a convinent interface Scan() (https://golang.org/pkg/database/sql/#Rows.Scan). No matter which backend db driver, it would mostly convert the data into language built-in types (e.g. int64, string) and then let the Scan() to convert the built-in types into user domain types. But in sqlx, to write a decode, it need to be bound to a specific db driver?

What's the difference among Custom(Arc), DeclareWithName(UStr) and DeclareWithOid(u32)?

For the consumer of SQLx, there is no difference in use. You should only use them as PgTypeInfo::with_name("pg_lsn").

And moreover, for simple query (unprepare), it seems sqlx would provide a DeclareWithOid(u32) for it.

That is correct, however, SQLx also does not attempt type verification in simple queries as the returned types are not reliable.

Another side question, in golang, the sql package provides a convinent interface Scan()

Your Decode does not need to be bound to a specific driver. You can write a generic one. See the example I linked at the bottom of this comment.

https://github.com/launchbadge/sqlx/blob/0b2844bf39128132aeccce2cfc02ec94472e074f/sqlx-core/src/decode.rs#L9-L59


Replacing spaces in objectWithPath with pluses

Replacing spaces in objectWithPath with pluses, otherwise deleteObjectWithPath fails.

Fixed by 0ff20a15b4496949fa6d58dfec8b2d6e6e7d80ab.


[FEA] LEAD/LAG should support [ IGNORE NULLS | RESPECT NULLS ]

Is your feature request related to a problem? Please describe.
Support [ IGNORE NULLS | RESPECT NULLS ] for LEAD/LAG  was added here: https://github.com/apache/spark/commit/3e9821edfd . Need to evaluate and add tests.

@mythrocks this is a change in windows lead / lag for Spark 3.2.  Minimally we need to not map to the GPU if we cannot support the new functionality.
Are any cudf changes required to support this?


chore: bump chart 0.3.10

bump helm chart for new release.
diff: https://github.com/external-secrets/external-secrets/compare/v0.3.9...f8cd59c
notable changes:

Azure: support authentication with managed identity
SecretStore: add RetrySettings field
IBM: implement retry settings
various patches & typo fixes

/approve

/merge


[SPARK-16596] [SQL] Refactor DataSourceScanExec to do partition discovery at execution instead of planning time

What changes were proposed in this pull request?
Partition discovery is rather expensive, so we should do it at execution time instead of during physical planning. Right now there is not much benefit since ListingFileCatalog will read scan for all partitions at planning time anyways, but this can be optimized in the future. Also, there might be more information for partition pruning not available at planning time.
TODO: In another pr, move DataSourceScanExec to it's own file.
How was this patch tested?
Existing tests (it might be worth adding a test that catalog.listFiles() is delayed until execution, but this can be delayed until there is an actual benefit to doing so).

Test build #62438 has started for PR 14241 at commit 0d4642a.

This doesn't actually give us a way to add additional filter constraints in the physical operator, does it?

Test build #62438 has finished for PR 14241 at commit 0d4642a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62438/
Test FAILed.

You should be able to add those filter constraints in FileDataSourceStrategy. I don't think it matters too much whether that code is located within buildScan(), or in the operator itself.

@ericl I was talking with @marmbrus -- it'd be better to create an API in the physical scan operator that accepts a list of filters, and then do pruning there. That is to say, we also want to move all the pruning code from physical planning into the physical operators.

Test build #62619 has started for PR 14241 at commit b45e253.

Test build #62623 has started for PR 14241 at commit ebf2102.

Test build #62624 has started for PR 14241 at commit bbf89a1.

Test build #62619 has finished for PR 14241 at commit b45e253.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62619/
Test FAILed.

Test build #62625 has started for PR 14241 at commit 358eb9f.

Test build #62627 has started for PR 14241 at commit 2d78051.

Test build #62623 has finished for PR 14241 at commit ebf2102.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62623/
Test FAILed.

Test build #62624 has finished for PR 14241 at commit bbf89a1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62624/
Test FAILed.

Test build #62625 has finished for PR 14241 at commit 358eb9f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62625/
Test FAILed.

Merged build finished. Test FAILed.

Test build #62627 has finished for PR 14241 at commit 2d78051.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62627/
Test PASSed.

Merged build finished. Test PASSed.

Test build #62691 has started for PR 14241 at commit a3d2c69.

Test build #62691 has finished for PR 14241 at commit a3d2c69.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62691/
Test PASSed.

Test build #62845 has started for PR 14241 at commit 780fec5.

Test build #62845 has finished for PR 14241 at commit 780fec5.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62845/
Test FAILed.

Test build #62847 has started for PR 14241 at commit ddb202e.

Test build #62847 has finished for PR 14241 at commit ddb202e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62847/
Test PASSed.

This looks pretty good. I have left a few comments.

Test build #62979 has started for PR 14241 at commit 18f5543.

Test build #62979 has finished for PR 14241 at commit 18f5543.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62979/
Test PASSed.

Test build #63139 has started for PR 14241 at commit a76b432.

Test build #63141 has started for PR 14241 at commit 704511e.

LGTM

Test build #63139 has finished for PR 14241 at commit a76b432.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkConf(loadDefaults: Boolean) extends Cloneable with Logging with Serializable
case class MonotonicallyIncreasingID() extends LeafExpression with Nondeterministic
case class SparkPartitionID() extends LeafExpression with Nondeterministic
case class AggregateExpression(
case class Least(children: Seq[Expression]) extends Expression
case class Greatest(children: Seq[Expression]) extends Expression
case class CurrentDatabase() extends LeafExpression with Unevaluable
class GenericInternalRow(val values: Array[Any]) extends BaseGenericInternalRow
class AbstractScalaRowIterator[T] extends Iterator[T]
 implicit class SchemaAttribute(f: StructField)

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63139/
Test PASSed.

Test build #63141 has finished for PR 14241 at commit 704511e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63141/
Test PASSed.

Merged build finished. Test PASSed.

@hvanhovell Have you finished your round of review?

LGTM

Merging this into master, thanks!


Raiplay

Hi, I wanted to know when the Raiplay windows update will be available. thanks

@fabio1962 If you didn't manage to solve this yet, it's fixed in #23040. You can just apply this patch and then it works fine.


Remove the hash from the location

How can I remove the hash and number from the location?

Set sectionName to false. As explained in the docs.

Hi, when I set sectionName to false then the plugin doesn't work.

If you're not using sectionName then Scrollify has no way of knowing what the href of your link is referring to.
You can either use sectionName and parse href values to the move method or you can set sectionName to false and parse index values to the move method.

Thank you very much. I will try it.

For anyone looking for a solution (i.e. no hash in url using pagination), simply add return false in the click function.
$(".pagination a").on("click", function() {         $.scrollify.move($(this).attr("href"));         return false;       });
Also as luke mentioned, use sectionName (i.e. sectionName: "section-name")

I'm new to coding and I'm struggling to implement the solutions mentioned above.  I have tried to set the "sectionName" to false, but it doesn't work. I also can't find "pagination" in the code.

hey coloufulcam,
hope you are still on the project. I was in a similar situation, where I did not now how I can get the hash. It's pretty easy to see the hash e.g. in your console, just do a console.log(location.hash) https://www.w3schools.com/jsref/prop_loc_hash.asp
This made it click for me.


[ZEPPELIN-3060] Unable to use interpreter names with special characters (e.g. dash or underscore)

[ZEPPELIN-3060] Unable to use interpreter names with special characters
(e.g. dash or underscore)
What is this PR for?
This fixes a regression which was introduced with ZEPPELIN-3013. There
is no restriction regarding characters when creating new interpreters.
But when running a note the interpreter name was parsed using the regex
%([\w.]+)., which only considered the word character class and dots.
Interpreter names with special characters (e.g. _ or -) were not matched
correctly. This change enables usage of interpreter names that use other
characters by changing the regex group to %([^\s(]+)., which means:
parse the interpreter name from % until any whitespace or open
parenthesis.
What type of PR is it?
Bug Fix
Todos

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-3060
How should this be tested?
Create an interpreter with a name containing one or more special
characters, e.g. dash or underscore. Try running that interpreter.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

@weand In ZEPPELIN-3013, I try to make interpreter name only contains alphabet ,number and under score, just like valid variable name in most of programing languages. Is it necessary and normal for you to have special character in your interpreter ? although it is possible to do that, I would recommend user don't include special character in interpreter name.

well, IMHO - and _ are very common in programming languages too (eg. python)
I think it's reasonable to accept these two in names.
Not sure about other characters though, ( can be problematic

'_' is acceptable in interpreter name and current code support that I believe.
But - is not acceptable IMHO, because no programming language allow - in variable identifier IIRC.

Well, the current implementation does not enforce any naming pattern when creating a new interpreter.
Before ZEPPELIN-3013 interpreters with any characters e.g. - could be created and executed.
If that's not supported anymore, there should be a failure when creating such an interpreter.
The current behavior is quite misleading, as the interpreter name is not even display correctly in the error message. See the corresponding Jira ticket of this PR.

Good point @weand , We should validate the interpreter name when creating new interpreter.

Closed and created https://issues.apache.org/jira/browse/ZEPPELIN-3083 instead.


[Summer 2021] Update vulnerable dependency in SAPP

GitHub has detected that a package defined in the sapp/ui/frontend/package-lock.json file of the facebook/sapp repository contains a security vulnerability.
Package name: react-dev-utils
Affected versions: >= 0.4.0, < 11.0.4
Fixed in version: 11.0.4
Severity: MODERATE
Identifier(s):
GHSA-5q6m-3h65-w53x
CVE-2021-24033
We should likely just update this dependency and make sure there are no conflicts and nothing breaks

Currently with sapp there are 14 vulnerabilities. I think we should fix all those (report by npm audit)

Closed via https://github.com/facebook/sapp/commit/0dbae133a5e05ab6b6725183b9bfbc6ecc0ee897


[TASK] MVP.server: Verify the current use of dockers.

This needs to be reviewed because of the new milestone.
Dockers should be part of the development workflow, there are no instructions for that on `server/README.md´.

This is done. The Dockerfile results in a container with the compiled code and is meant to be used as a dependency (like FROM monty:latest)


Unable to create Object Storage Bucket with OKIT

I am trying to create bucket in Object Storage using OKIT with Resource Access Manager
when click on "apply", it's throwing an below error:
Error: Unsupported block type
  on main.tf line 84, in data "oci_objectstorage_namespace" "Okit_BucketNamespace"
  84:     filter {
Blocks of type "filter" are not expected here.

Fixed in 0.26.0 release


Unable to import updated elasticsearch as opensearch resource

Is there a way to import elasticsearch -> opensearch updated service into the aiven_opensearch terraform resource?
Steps to reprduce
The following ES service is defined in terraform
resource "aiven_service" "es" {
  project                 = data.terraform_remote_state.aiven.outputs.project
  cloud_name              = "aws-eu-west-2"
  termination_protection  = true
  plan                    = "hobbyist"
  service_name            = "elasticsearch"
  service_type            = "elasticsearch"
  maintenance_window_dow  = "monday"
  maintenance_window_time = "00:00:00"
  project_vpc_id          = data.terraform_remote_state.aiven.outputs.vpc
  elasticsearch_user_config {
    elasticsearch_version = "7"
  }
}

Service was updated from console

Update was successful

Executing terraform plan results in bringing back the ES version
Terraform will perform the following actions:

  # aiven_service.es will be updated in-place
! resource "aiven_service" "es" {
        id                      = "dev/elasticsearch"
        # (16 unchanged attributes hidden)

!       elasticsearch_user_config {
!           elasticsearch_version = "1" -> "7"
            # (2 unchanged attributes hidden)
        }
        # (1 unchanged block hidden)
    }

The ES resource was removed from terraform and from plan  terraform state rm aiven_service.es
A new resource was added
resource "aiven_opensearch" "es" {
  project                 = data.terraform_remote_state.aiven.outputs.project
  cloud_name              = "aws-eu-west-2"
  termination_protection  = true
  plan                    = "hobbyist"
  service_name            = "elasticsearch"
  maintenance_window_dow  = "monday"
  maintenance_window_time = "00:00:00"
  project_vpc_id          = data.terraform_remote_state.aiven.outputs.vpc
  opensearch_user_config {
    opensearch_version = "1"
  }
}

Import the updated from Elasticsearch to Opensearch resource with
terraform import aiven_opensearch.es dev/elasticsearch

Error
aiven_opensearch.es: Importing from ID "dev/elasticsearch"...

Error: cannot set `elasticsearch_user_config` : Invalid address to set: []string{"elasticsearch_user_config"};Please make sure that all Aiven services have unique service names

Versions
> terraform version
Terraform v0.14.8
+ provider registry.terraform.io/aiven/aiven v2.2.1

Hey @edbighead,
Thanks for reporting, I was able to reproduce the issue and am looking into it.

Hey @edbighead,
could you try from the latest master ( not released yet ); it works for me now.

@mhoffm-aiven thanks, will test it and let you know

@mhoffm-aiven I was able to successfully import updated OpenSearch resource.
$ terraform import aiven_opensearch.es dev/elasticsearch
aiven_opensearch.es: Importing from ID "dev/elasticsearch"...
aiven_opensearch.es: Import prepared!
  Prepared aiven_opensearch for import
aiven_opensearch.es: Refreshing state... [id=dev/elasticsearch]

@edbighead  thanks for verifying! I'll close this issue after the next release then!

Sorry, i slipped and closed the issue on accident.

Hello, is this fixed in the provider v2.3.0 ?
I've tried and faced the same error

Hey @gbuirel,
no but the fix should be included in the next version!

just released 2.3.1, if it works with that version we could close i think

Closing as fixed


Add wiki links to enchantments (Not Complete yet)

I don't really know if links with '#'s will work in NEU, sorry if it doesn't work.

Links with '#'s in them don't work, closing this.


How to avoid saving empty areas

When I save the image it saves empty areas of the view as well. Say I load a square photo, the saved image would have black areas on top and bottom like displayed on phone screen.  I am using code from the sample app, the only difference is I am using fragment activity as opposed to activity. Any idea what's happening here? (Note: sample app saves correctly)

There are some options on save method, use them like this:
val saveSettings = **SaveSettings.Builder().setTransparencyEnabled(false).build()**
            photoEditor.saveAsFile(pathFile, saveSettings, object : PhotoEditor.OnSaveListener {
                override fun onSuccess(imagePath: String) {
                    //success
                }

                override fun onFailure(exception: Exception) {
                    //failure
                }
            })

Refer Wiki


New "vNext" update script using dependabot-core updater; aligns update behaviour more closely with the GitHub Dependabot service

What are you trying to accomplish?

More closely align the update script logic with the GitHub hosted Dependabot updater service so that the Azure DevOps user experience is more consistent with the GitHub experience.
Enable more Dependabot features that are not currently supported by the existing update script (e.g. groups:, directories:, etc)

New update script 'vNext'
To preserve the existing behavior, a new update script (update_script_vnext.rb) was added.
This new script leverages as much existing functionality from the dependabot-core "updater" project as possible; as opposed to update_script.rb which is based on dry-run.rb and does not handle many of the newer Dependabot features such as dependency groups and multiple directories.
High-level update sequence diagram
 sequenceDiagram
    participant script as update_script_vnext.rb
    participant jb as TingleSoftware.Dependabot.Job
    participant cmd as TingleSoftware.Dependabot.Commands.UpdateAllDependenciesCommand
    participant updater as Dependabot.Updater
    participant client as TingleSoftware.Dependabot.ApiClients.AzureApiClient
    participant ado as Azure DevOps

    script->>+jb: Create new job
    jb->>jb: Parse "DEPENDABOT*" environment variables
    jb->>+ado: Get active pull requests using "TingleSoftware::Dependabot::Clients::Azure"
    ado-->>-jb: Pull request info
    jb->>+ado: Get active pull request properties using "TingleSoftware::Dependabot::Clients::Azure"
    ado-->>-jb: Property info
    jb->>jb: Parse "UPDATED_DEPENDENCIES" properties of active pull request
    jb-->>-script: "Dependabot::Job" object
    script->>+cmd: Perform job
    cmd->>cmd: Clone git repo contents using "Dependabot::FileFetcher"
    cmd->>cmd: Snapshot dependencies using "Dependabot::DependencySnapshot"
    loop For every existing pull request
       cmd->>updater: Update or close dependency update using "Dependabot::Updater"
    end
    cmd->>-updater: Create all dependency [group] updates using "Dependabot::Updater"
    alt when "Dependabot::Updater" creates a new pull request
        updater->>client: Create pull request
        client->>+ado: Publish pull request using "Dependabot::PullRequestCreator"
        ado-->>-client: Pull request info
        client->>ado: Set pull request property metadata using "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Set auto-approve using "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Set auto-complete using "Dependabot::Clients::Azure"
    end
    alt when "Dependabot::Updater" updates an existing new pull request
        updater->>client: Update pull request
        client->>+ado: Update pull request using "Dependabot::PullRequestUpdater"
        ado-->>-client: Pull request info
        client->>ado: Set pull request property metadata using "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Set auto-approve using "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Set auto-complete using "Dependabot::Clients::Azure"
    end
    alt when "Dependabot::Updater" closes an existing new pull request
        updater->>client: Close pull request
        client->>+ado: Comment on pull request with close reason usin "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Delete source branch using "TingleSoftware::Dependabot::Clients::Azure"
        client->>ado: Abandon pull request using "TingleSoftware::Dependabot::Clients::Azure"
    end

Dependency state metadata now stored in pull request properties
The vNext script will use Pull Request Properties to store metadata related to Dependabot updates. This is done to mimic how Dependabot::ApiClient works and is primarily used to accurately identify which dependencies were modified by a PR without needing to interept the PR title. The stored PR property names are:

dependabot.base_commit_sha
dependabot.updated_dependencies

If the "updated_dependencies" property is not present in a PR, the vNext script will not recognise it when checking for existing PRs during the update process.
The property list for a grouped dependency update PR would look like:
{
  "Microsoft.Git.PullRequest.IsDraft": {
    "$type": "System.String",
    "$value": "False"
  },
  "Microsoft.Git.PullRequest.SourceRefName": {
    "$type": "System.String",
    "$value": "refs/heads/dependabot/nuget/multi-1d378ec07d"
  },
  "Microsoft.Git.PullRequest.TargetRefName": {
    "$type": "System.String",
    "$value": "refs/heads/main"
  },
  "dependabot.base_commit_sha": {
    "$type": "System.String",
    "$value": "3a69392dd425b5c7864b7ae5c9b1f43d81a27e4c"
  },
  "dependabot.updated_dependencies": {
    "$type": "System.String",
    "$value": "{\"dependency-group-name\":\"microsoft\",\"dependencies\":[{\"dependency-name\":\"Microsoft.AspNetCore.Authentication.OpenIdConnect\",\"dependency-version\":\"8.0.6\",\"directory\":\"/\"},{\"dependency-name\":\"Microsoft.AspNetCore.Authentication.WsFederation\",\"dependency-version\":\"8.0.6\",\"directory\":\"/\"}]}"
  }
}

Limitations
The following environment variables and features are not currently supported by the vNext script.

Feature
Supported
Notes

DEPENDABOT_EXCLUDE_REQUIREMENTS_TO_UNLOCK
Not Supported
No out-of-the-box extension point to implement this currently.

DEPENDABOT_FAIL_ON_EXCEPTION
Not Supported
Using Dependabot::Updater to run the core updater logic, there is no out-of-the-box option to cleanly break out of the update process. The behaviour is that the updater will process all updates and then aggregate errors at the end; Interrupting this process by throwing exceptions to break out of the updater results in error details and stack trace info being lost, making diagnosing issues very difficult

DEPENDABOT_OPEN_PULL_REQUESTS_LIMIT
Behaviour Changed
Similar to above Dependabot::Updater cannot be cleanly interrupted. This means that once the pull request limit is reached, dependency updates will continue to be processed but they will not be committed to DevOps. This may result in overall longer task run times due to the updater processing updates that may not end up being committed.

New environment variables
The following new environments variables have been added and are supported by the vNext script only.

Variable Name
Description

DEPENDABOT_DIRECTORIES
Optional. The list of directories in which dependencies are to be checked, in JSON format. For example: ['/', '/src']. When specified, it overrides DEPENDABOT_DIRECTORY. When not specified, DEPENDABOT_DIRECTORY is used instead. See official docs for more.

DEPENDABOT_SECURITY_UPDATES_ONLY
Optional. If true, only security updates will be processed. Can be used in combination DEPENDABOT_OPEN_PULL_REQUESTS_LIMIT to exclusively perform security updates whilst also limiting the total number of security PRs opened at once.

DEPENDABOT_VENDOR_DEPENDENCIES
Optional Determines if dependencies are vendored when updating them. Don't use this option if you're using gomod as Dependabot automatically detects vendoring. See official docs for more.

DEPENDABOT_DEPENDENCY_GROUPS
Optional. The dependency group rule mappings, in JSON format. For example: {"microsoft":{"applies-to":"version-updates","dependency-type":"production","patterns":["microsoft*"],"exclude-patterns":["*azure*"],"update-types":["minor","patch"]}}. See official docs for more.

DEPENDABOT_SIGNATURE_KEY
Optional. The GPG signature key that git commits will be signed with. See official docs for more. By default, commits will not be signed.

DEPENDABOT_BRANCH_NAME_PREFIX
Optional. The prefix used for Git branch names. Defaults to dependabot.

DEPENDABOT_PR_NAME_PREFIX_STYLE
Optional. The pull request name prefix styling. Possible options are none, angular, eslint, gitmoji. If DEPENDABOT_COMMIT_MESSAGE_OPTIONS prefixes are also defined, this option does nothing. Defaults to none.

DEPENDABOT_COMPATIBILITY_SCORE_BADGE
Optional. Determines if compatibility score badges are shown in the pull request description for single dependency updates (but not group updates). This feature uses public information from GitHub and enabling it does not send any private information about your repository to GitHub other than the dependency name and version number(s) required to calculate to the compatibility score. Defaults to false. See official docs for more.

DEPENDABOT_MESSAGE_HEADER
Optional. Additional pull request description text to shown before the dependency change info.

DEPENDABOT_MESSAGE_FOOTER
Optional. Additional pull request description text to shown after the dependency change info. This text will not be truncated, even when the dependency change info exceeds the PR maximum description length.

DEPENDABOT_COMMENT_PULL_REQUESTS
Optional. Determines whether to comment on pull requests which an explanation of the reason for closing. Defaults to false.

DEPENDABOT_JOB_ID
Optional. The unique id for the update job run. Used for logging and auditing. When not specified, the current date/timestamp is used.

DEPENDABOT_DEBUG
Optional. Determines if verbose log messages are logged. Useful for diagnosing issues. Defaults to false.

Dependency groups
Dependency groups are supported if DEPENDABOT_DEPENDENCY_GROUPS is set with the group rules, in JSON format. See the official docs for more.

Multiple directories per package ecosystem
Multiple directories per ecosystem are supported if DEPENDABOT_DIRECTORIES is set with the directory paths, in JSON format. See the official docs for more.
Comment on pull requests
When DEPENDABOT_COMMENT_PULL_REQUESTS is set, a comment will be added before closing pull requests explaining why it was closed. The comment closely (but not exactly) match those used by the GitHub Dependabot service.

Git branch prefixes
The Git branch prefix can be set using DEPENDABOT_BRANCH_NAME_PREFIX.

Pull request name prefix styles
The (hidden?) name prefix style options can be forced on using DEPENDABOT_PR_NAME_PREFIX_STYLE. These styles are similar to "commit options" prefixes, but slightly more dynamic? (e.g. gitmoji uses "⬆" for regular updates, or "⬆🔒" for a security updates). Not sure if this is a new experimental feature, or an old one that they are phasing out. Either way, it can now be configured. Supported options are:
Default

Gitmoji

Angular

Eslint

Compatibility score badges
When DEPENDABOT_COMPATIBILITY_SCORE_BADGES is set, compatibility score badges are shown in the pull request description for single dependency updates (but not group updates). This feature uses public information from GitHub and enabling it does not send any private information about your repository to GitHub other than the dependency name and version number(s) required to calculate to the compatibility score. Defaults to false. See official docs for more.

Pull request description header/footer text
Extra header/footer text can be added to pull request descriptions with DEPENDABOT_MESSAGE_HEADER and DEPENDABOT_MESSAGE_FOOTER respectively.

Pull request description "Vulnerabilities fixed" info
When GITHUB_ACCESS_TOKEN is set, pull requests containing security related dependency updates will now have:

"[Security]" prefix added to the PR name (or equivalent when using PR prefix name styles);
"security" label added to the PR (unless custom labels are used);
"Vulnerabilities fix" section added to the PR description, with expandable vulnerability details and links to the GitHub Advisory Database.

Pull request author signed commits (signature key config)
Commits made by Dependabot will be signed when DEPENDABOT_SIGNATURE_KEY is set with an appropriate GPG key. See official docs for more.

This has got to be the most detailed contribution I have seen in this repository. Maybe the first from someone with proper Ruby knowledge. Thank you so much.
Here's my view:

The renaming of files towards using the lib makes a lot of sense. However, I'd prefer we did that in a separate PR before to be merged before this one.
The files I copied from the core repository are unused so you're right in starting to create a new client. I think we need to delete those files too.
To allow for others to test, id rename update_script_new.rb to update_script_vnext.rb, add a Boolean input to the extension task named useVNext, which in turn changes the command sent to docker.
What feature set are we looking at in this new/vnext workflow? Groups is one, are there others that I didn't see or come as a consequence? Also, I wonder if this will affect things like conflict resolution and closure. Though I think that's why we are keeping the other one around.

Overall, thanks so much for the contribution!

The renaming of files towards using the lib makes a lot of sense. However, I'd prefer we did that in a separate PR before to be merged before this one.

Makes sense, I'll push a new PR for these.

The files I copied from the core repository are unused so you're right in starting to create a new client. I think we need to delete those files too.

There are a few files from the core repo that will be really useful still I think, but I agree there are a few that could be removed. I will see if I can clean them up a little.

To allow for others to test, id rename update_script_new.rb to update_script_vnext.rb, add a Boolean input to the extension task named useVNext, which in turn changes the command sent to docker.

Sounds good to me, I'll update this.

What feature set are we looking at in this new/vnext workflow? Groups is one, are there others that I didn't see or come as a consequence? Also, I wonder if this will affect things like conflict resolution and closure. Though I think that's why we are keeping the other one around.

The main features I am personally interested in are:

Directories
Groups

I was hoping that if the updater piggybacks off the core repository classes as much as possible, then any new Dependabot features should more easily "just work" (overly optimistic maybe).

Overall, thanks so much for the contribution!

I should be thanking you for making this project in the first place :)

After merging the other PRs, the focus here is now more specific.
If we can piggyback on the updated core logic then it simplifies the maintenance works. This is why I had started to keep the files up-to date but got too busy to keep track, yet the updater is not published as a consumable. They don't accept contributions for it either.
Gathered some extra thoughts:

We have an empty client were the actual PRs opened? It may have done so if we are relying on the internal Azure client but I'm unsure.
Do signature annotations require adding of types to the whole runtime code? (Assuming you have more knowledge on Ruby than me which is likely)
Maybe we can indicate what features are not supported at the start. For example: vulnerability checks, auto approve, etc Unless you already have solutions for this.

If we can piggyback on the updated core logic then it simplifies the maintenance works. This is why I had started to keep the files up-to date but got too busy to keep track, yet the updater is not published as a consumable. They don't accept contributions for it either.

We have an empty client were the actual PRs opened? It may have done so if we are relying on the internal Azure client but I'm unsure.

The API client still needs to be finished, it will be a combination of your "azure_helper" and the built-in Azure client. When I put this up for draft, I only did the minimum required to get the grouped PRs to work on the local repo within the Dependabot container.
I have today updated it to push the PRs to DevOps now, but again, still a lot of work to do yet.

Do signature annotations require adding of types to the whole runtime code? (Assuming you have more knowledge on Ruby than me which is likely)

Honestly, not sure. I only just picked up Ruby a couple of weeks ago when I started contributing to this and dependabot-core. I will look in to it though before publishing the PR.

Maybe we can indicate what features are not supported at the start. For example: vulnerability checks, auto approve, etc Unless you already have solutions for this.

Good idea. I'm hoping to implement all the features in to the new script, but if that doesn't happen for some reason I'll look in to this.

Heads up! Made some updates that may cause trouble with lint/specs.
https://github.com/tinglesoftware/dependabot-azure-devops/issues/1202

@mburumaxwell this is [mostly] feature complete now. I still need to fully test all config options, fix a few small bugs, and clean/optimise the code. However, I would be interested to know if you have any concerns or suggestions on the high-level implementation of this, especially regarding structure of the code and the environment variable limitations (see PR description section on limitations).
I've added a new column to the updater environment variables that lists which command scripts each variable is supported by. If you can think of a better way to communicate this, let me know.
I also decided not update the DevOps extension in this PR, just focus on the updater and environment variables. I'll update the extension in a separate PR if/when this is approved.

I think this is generally okay. I cannot see anything of major concern yet in the updater. Issues may show up when we make it available for others to test. I see some commits since you asked for review, I will keep the assumption that so long as the PR is in draft mode, you are still working on stuff, and then I can review again when you make it ready to review.
On a side note, I do not know if other people use the server component that will be affected when we make this mainstream as it would require the fetch_files.rb and update_files.rb. Maybe we can worry about it when it happens.

I think this is generally okay. I cannot see anything of major concern yet in the updater. Issues may show up when we make it available for others to test. I see some commits since you asked for review, I will keep the assumption that so long as the PR is in draft mode, you are still working on stuff, and then I can review again when you make it ready to review.

Will do. There are two bug lefts that I know about that I still want to fix, so shouldn't be too far away from publishing now.

On a side note, I do not know if other people use the server component that will be affected when we make this mainstream as it would require the fetch_files.rb and update_files.rb. Maybe we can worry about it when it happens.

I didn't realise the server component used these files, my mistake. It is probably a good idea that I restore them then if that is the case.

Hey guys! I've been following this.. we are just starting to implements dependabot on our Azure organization. I am tempted to test this, since we have a monorepo and want to use groups.
Any tips on how to test this vnext update script? Do I just run the ecosystem image and use the new name as the command?
Thank you!!

Any tips on how to test this vnext update script?

Unfortunately you can't test this new script in DevOps until the extension is updated (see: https://github.com/tinglesoftware/dependabot-azure-devops/pull/1216). However, you can run the updater manually using Docker if that is something you are comfortable with. The image tag would need to be 1.29.8-ci0001 and the command would be update_script_vnext, for example:
docker run --rm -t \
           <your_environment_variables_here> \
           ghcr.io/tinglesoftware/dependabot-updater-<your_ecosystem_name_here>:1.29.8-ci0001 update_script_vnext

Hi @rhyskoedijk appreciate it will give it a try and I'll report back in the form of new issue/discussion with my findings.
Thanks! Have a great day
Leo.


[Bug]:  Issue with pip install llama-index

Bug Description
I tried installing llama_index on both Google Colab and my local machine and I am met with this wierd (but same) error.
`Collecting llama-index
Using cached llama_index-0.9.28.post1-py3-none-any.whl (15.8 MB)
Requirement already satisfied: SQLAlchemy[asyncio]>=1.4.49 in /usr/local/lib/python3.10/dist-packages (from llama-index) (2.0.24)
Requirement already satisfied: aiohttp<4.0.0,>=3.8.6 in /usr/local/lib/python3.10/dist-packages (from llama-index) (3.9.1)
Collecting beautifulsoup4<5.0.0,>=4.12.2 (from llama-index)
Using cached beautifulsoup4-4.12.2-py3-none-any.whl (142 kB)
Collecting dataclasses-json (from llama-index)
Using cached dataclasses_json-0.6.3-py3-none-any.whl (28 kB)
Collecting deprecated>=<IP_ADDRESS> (from llama-index)
Using cached Deprecated-1.2.14-py2.py3-none-any.whl (9.6 kB)
Requirement already satisfied: fsspec>=2023.5.0 in /usr/local/lib/python3.10/dist-packages (from llama-index) (2023.6.0)
Requirement already satisfied: httpx in /usr/local/lib/python3.10/dist-packages (from llama-index) (0.26.0)
Requirement already satisfied: nest-asyncio<2.0.0,>=1.5.8 in /usr/local/lib/python3.10/dist-packages (from llama-index) (1.5.8)
Requirement already satisfied: networkx>=3.0 in /usr/local/lib/python3.10/dist-packages (from llama-index) (3.2.1)
Requirement already satisfied: nltk<4.0.0,>=3.8.1 in /usr/local/lib/python3.10/dist-packages (from llama-index) (3.8.1)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from llama-index) (1.23.5)
Requirement already satisfied: openai>=1.1.0 in /usr/local/lib/python3.10/dist-packages (from llama-index) (1.7.0)
Requirement already satisfied: pandas in /usr/local/lib/python3.10/dist-packages (from llama-index) (1.5.3)
Requirement already satisfied: requests>=2.31.0 in /usr/local/lib/python3.10/dist-packages (from llama-index) (2.31.0)
Requirement already satisfied: tenacity<9.0.0,>=8.2.0 in /usr/local/lib/python3.10/dist-packages (from llama-index) (8.2.3)
Collecting tensorrt_llm<0.8.0,>=0.7.1 (from llama-index)
Using cached tensorrt-llm-0.7.1.tar.gz (6.9 kB)
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
Preparing metadata (setup.py) ... error
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.`
I have pasted the logs here for reference. I have never encountered this any suggestions about whats going on?
Does it have something to do with the latest release?

Version
llama-index 0.9.28.post1
Steps to Reproduce
pip install llama-index in terminal
Relevant Logs/Tracbacks
No response

cannot reproduce ```Installing collected packages: llama-index
Successfully installed llama-index-0.9.28.post1

Faced the same issue on Google Colab. 0.9.27 seems to be fine

Should be fixed here
https://github.com/run-llama/llama_index/pull/9946
Well put out a new release asap

Thank you for the quick fix @logan-markewich!


chore(dart_frog_cli): v1.0.0

Status
READY
Description
chore(dart_frog_cli): v1.0.0

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x] 🗑 Chore

Examples are expected to be red at this point.


Update "How to help" section

@talalryz or @lydian  for review

Codecov Report

Merging #59 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #59   +/-   ##
=======================================
  Coverage   74.09%   74.09%
=======================================
  Files          15       15
  Lines         772      772
  Branches      106      106
=======================================
  Hits          572      572
  Misses        200      200


Method $kernel->terminate() is not being called

Hello, I just created a new Laravel 5 a minute ago
And I notice the $kernel->terminate at the end of the index.php file is not being called.
Therefore the Session is not being saved() and CRSF securitity doesn't work etc.

Anybody who ran into this issue recently? I am currently using 6.2 and suddenly my project is having very high latency.


Add translation into russian

Hello!
I've made translation into russian.
I think that some of strings that are marked as non-tranlatable should be translated:
Sign Out
INBOX
Privacy Policy
Also there is no sense to translate  is we don't provide translation for .

Hi Natalia, thanks for the translation, I merged the pull request and will update the app on the Play Store as soon as I can. You are right, I could change those word to translatable.
As soon as I have time I will come back to the project, I am very busy at the moment :(
have a great day and thanks!


Don't use -o pipefail for plugin

I don't think it's a good idea to document the use of -o pipefail by default.
Plugin author blindly follow this instruction and we have issue with the plugin after that.
A simple command like:
elasticsearch:create)
# Check if Elasticsearch container is installed
IMAGE=$(docker images | grep "jezdez/elasticsearch" | awk '{print $3}')
if [[ -z $IMAGE ]]; then
echo "Elasticsearch image not found... Did you run 'dokku plugins-install' ?"
exit 1
fi
will completely stop dokku right before the if because grep returned exit code 1. (jezdez/elasticsearch image not build)

@michaelshobbs thoughts on this? I feel as though if a plugin fails, then the deploy should also fail, but I'm not strong on that opinion.

Seeing as core is fairly religious about using pipefail I would think others should as well. The way around this example would || true. However, I think it ultimately up to the author of the plugin as to what makes sense in their use case. Augmenting the docs with pros/cons might be fine but I wouldn't remove the example altogether.

@vincentfretin do you mind updating the example and making it apparent as to what pipefail does?

@michaelshobbs
IMAGE=$(docker images | grep "jezdez/elasticsearch" | awk '{print $3}' || true) doesn't work. The script exists before the awk command.
@josegonzalez I updated the PR.

Oups, fixed

Yeah @vincentfretin you would need to do that for every command that could fail. I'm not saying its the right choice for your plugin. Just an option.


[Chery-pick][branch-2.2] [Feature] Add InsertTxnCommitAttachment to support version rollback

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

run starrocks_fe_unittest


Allow user to await async transports

I wanted to open this PR to have a discussion about how to implement this and if this is the way to go but we need to come up with a solution of some sorts.
The problem is that the HttpTransport uses an async client that because of how php works never actually starts the sending of the events until ->wait is called. Previously in 1.x this was fixed by an sendUnsentErrors and this attempts to replace that with Hub::getCurrent()->await() that a user or a framework integration can use to send unsent errors (if there are any).
We can for now go with not changing the Client interface so this is a non-bc and we can release it sooner so we can fix the problems people might encounter in longer running processes like a Laravel queue worker.
My intention is to get a fix/workaround for this issue crafted sooner rather than later if possible, it ofcourse doesn't have to be this exact way but also doesn't need to take use a few week to come up with a decent solution :)

What is the actual specification of the await method? Is it supposed to just tell the transport to send all events or does it also specify that these must be serialized and the method should only return when all requests have been sent? Just noting that latter is a very bad idea for asynchronous applications, as you force them to be synchronous, blocking.

@CharlotteDunois the point is to make the execution block, that is the main purpose of most implementations of the await keyword as far as I know.
This method is meant to make it possible for the implementor to force the requests to be sent.
Since PHP is a single threaded application there is no concept of asynchronous execution (without extensions) and thus "async" is really a way to defer heavy tasks to later.
For example the curl-client from httplug implements async by "queueing" requests and executing them in parallel later to make them "async".
I hope I explained it correctly but yes, the meaning of this await implementation is to make the execution block until al events are sent. This way in long running processes we can periodically force events to be sent so they won't delay until the process exits (or is killed and the events are lost).
Please note that this method is never called in the SDK except for in the shutdown handler (which indicates the end of an execution and we should wait for event to be sent before the process is killed). So the user can call the await to block execution.
This was made for solving: getsentry/sentry-laravel#222

@stayallive Asynchronous does not mean multithreaded, so does not mean multithreaded asynchronous. In PHP and JavaScript, asynchronous means non-blocking I/O, and I/O is the great devil here. The point of asynchronous, non-blocking I/O is not to block the thread simply to wait for I/O to happen. Simply do something else and check if it's ready yet periodically and get back to it when it's really ready.
Defering tasks does not make anything asynchronous. cURL multi relies onto a separate process (or thread) to do blocking I/O, that does not make it asynchronous. It just means you're telling someone else to do it, which means you are free to do something else, which is also to some degree the point of asynchronous frameworks (such as ReactPHP and Amphp). cURL multi relies onto the fact that you poll cURL meanwhile periodically to see if cURL is done, where you have now two paths 1) do a blocking loop until cURL is ready, or 2) just do something else and check again later.
Asynchronous frameworks such as ReactPHP do it similarily, they do the necessary I/O and then just wait until the I/O is ready using an event loop. As long as I/O isn't ready, the event loop can do something else. Computation isn't really a problem in PHP, blocking I/O is. That's why we rely on event loops to minimize the impact of I/O, and the largest impact is waiting for I/O.
I don't really see the point of an await method for asynchronous applications, nor do I think it's wise to promote it for asynchronous transports. Instead you should probably make it return some sort of awaitable (depends naturally onto the transport) that users can await themself (may that be with some sort of coroutines or not, does not really matter here).
But if the point of await is to force an asynchronous transport to be synchronous, this should be throughrougly documented, as from the current PR state that's not clear. This can lead to various misunderstandings and misapplications of the provided methods.
Extensions such as ext-async provide here naturally a great help because they already implement an underlying libuv event loop to do non-blocking I/O and task scheduling (pretty much like coroutines).

I'm not really trying to discuss the very inner workings of php/async/await etc. and maybe I explained myself badly what I was trying to say, allow me to take another try to explain why this is currently need, if you still feel otherwise please let me know how to proceed :)
I also wan't to mention again I am not married to the name await if that causes confusion because I am using the await word wrong, happy to call it whatever 😄

https://github.com/getsentry/sentry-php/blob/0132227763669321dded54e89b75a319d8ee895c/src/Transport/HttpTransport.php#L81
We currently receive a promise from an async HttpClient which is supplied by httplug, for example let's take the current preferred one and how it implements their async.
The CurlPromise we get back is implemented using a MultiRunner  which uses the curl_multi_* functions under the hood.
To execute a curl_multi_ request you need to call curl_multi_exec. In the current MultiRunner this is done in the wait() method.
If you call wait on a CurlPromise you execute wait on the MultiRunner. A request will not be sent until you call wait on the CurlPromise as far as I can understand it right now.
This presents a problem. We never call wait until the php shutdown handler is called (currently and with this PR). This presents issues for long running processes like the Laravel queue worker since they run indefinitely and are sometimes killed to restart (no shutdown handler) which makes the curl-client queue up curl multi requests until the shutdownn handler is finally called when the worker is stopped, if the worker is killed no events will have ever be sent.
This PR tries to provide an interface to make sure all requests were sent before what's coming next. We would hook in the queue events from Laravel and make sure all events are submitted before the worker is allowed to handle a new event. This way we can be sure all events are correctly submitted to sentry and are not lost.

@stayallive I'm not saying this is not needed, I'm saying if it's merged, it must at least be documented properly, that means the method description must say what it does and what it tries to achieve, so that it can't be misused. Since it's a public SDK method, it's open to misapplication, and good documentation can mitigate this.
And just in my own opinion, I think that the async implementation of httplug curl is broken, because that's not how you implement asynchronous, a better example of how you do it is implemented in guzzle (however that's still bad for async applications, but it actually sends the request at any time asynchronously, with no need to synchronize it). If you want to resolve this the actual good way, then it should be properly solved in httplug curl, however I do see where you're coming from and I agree that sentry should provide a standardized way to "await" outstanding requests (maybe even with being able to return an actual "awaitable" from the transport?).

Closing this as it has been superseded by #813


[Audit_RV] add_liquidity does not fully follow the math model when computing the imbalance

calculate_delta_imbalance uses asset_state.reserve and asset_state.hub_reserve for its computation: https://github.com/galacticcouncil/HydraDX-math/blob/f4dab244bb5d57971325f0ba6fbb8f6c1353beeb/src/omnipool/math.rs#L419-L421
add_liquidity calls recalculate_imbalance which calls calculate_delta_imbalance with new_asset_state as an argument. This means that calculate_delta_imbalance receives the updated values for asset_state.reserve and asset_state.hub_reserve (i.e., using the math notations, it receives and uses uses Qi+ and Ri+). https://github.com/galacticcouncil/HydraDX-node/blob/8de6222f967cc1bfe120207a775e8f0dc8eb92a5/pallets/omnipool/src/lib.rs#L698
However, in the math model, the imbalance delta uses the non-updated reserves (Qi and Ri). https://github.com/galacticcouncil/HydraDX-simulations/blob/main/hydradx/spec/AddLiquidity.ipynb
Since Qi/Ri should be equal to Qi+/Ri+ (except for rounding errors), this may be fine. However, in today's meeting it seemed that you wanted to take another look, so I filed this issue.

this might no longer relevant and/or might be actually resolved. Imbalance calculation was completely refactored as part of other PR(s) and it not longer recalculated as mentioned in PR.


RATIS-1129. Move out the RPC related APIs from DataStreamOutput.

See https://issues.apache.org/jira/browse/RATIS-1129

@szetszwo Thanks the patch. I have merged it.


Include our video on main page

Going ahead and taking this... @nellshamrell

It's already on homepage. Closing this.


404 for carousel page

The carousel page shows 404 error.
https://www.ui-layout.com/components/embla-carousel
How to reproduce:
on components page click on carousel card.
Fix: typo error. only carousel instead of embla-carousel in url.

we don't have embla-carousel page now, check this one https://www.ui-layout.com/components/carousel

Yes but when i click on this card it redirects me to:  https://www.ui-layout.com/components/embla-carousel

Same issue when clicked on this drawer and modal component card.

Thanks, Rutwik, for pointing all these out. I've just fixed them now


x/tools/gopls: panic with 'instantiated ident not found'

gopls version: v0.14.1 (go1.21.3)
gopls flags:
update flags: proxy
extension version: 0.39.1
go version: 1.21.3
environment: Visual Studio Code linux
initialization error: undefined
issue timestamp: Fri, 03 Nov 2023 00:14:18 GMT
restart history:
Thu, 02 Nov 2023 19:11:31 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

panic: instantiated ident not found

goroutine 9211 [running]:
go/types.(*Checker).handleBailout(0xc0002c9a40, 0xc006ff3578)
	  check.go:336  0x88
panic({0xdfb3c0%3F, 0x1220aa0%3F})
	  panic.go:914  0x21f
go/types.instantiatedIdent(...)
	  check.go:594
go/types.(*Checker).recordInstance(0x0%3F, {0x12292c0%3F, 0xc00af28dc0%3F}, {0xc00a09bca0%3F, 0xc00a09bca0%3F, 0x1%3F}, {0x1225f68%3F, 0xc0010c7740%3F})
	  check.go:570  0x1de
go/types.(*Checker).instantiateSignature(0xc0002c9a40, 0x17af6, {0x12292c0, 0xc00af28dc0}, 0xc0010c7700, {0xc00a09bca0, 0x1, 0x1}, {0x0, 0x0, ...})
	  call.go:153  0x2f9
go/types.(*Checker).arguments(0xc0002c9a40, 0xc00af28e40, 0xc0010137c0, {0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, {0xc00c013350, ...}, ...)
	  call.go:635  0x15ea
go/types.(*Checker).callExpr(0xc0002c9a40, 0xc0010c7580, 0xc00af28e40)
	  call.go:302  0x86d
go/types.(*Checker).exprInternal(0xc0002c9a40, {0x0, 0x0}, 0xc0010c7580, {0x12292c0, 0xc00af28e40%3F}, {0x0%3F, 0x0%3F})
	  expr.go:1359  0x1809
go/types.(*Checker).rawExpr(0xc0002c9a40, {0x0, 0x0}, 0xc0010c7580, {0x12292c0%3F, 0xc00af28e40%3F}, {0x0%3F, 0x0%3F}, 0x0)
	  expr.go:965  0x1a5
go/types.(*Checker).multiExpr(0x678185%3F, {0x12292c0%3F, 0xc00af28e40}, 0x1)
	  expr.go:1517  0x85
go/types.(*Checker).initVars(0xe42ae0%3F, {0xc00a09bc20%3F, 0x2, 0x2}, {0xc00b705e20%3F, 0x1, 0x1}, {0x0, 0x0})
	  assignments.go:398  0x12c
go/types.(*Checker).shortVarDecl(0xc0002c9a40, {0x1223680, 0xc000aa3908}, {0xc008d696c0, 0x2, 0xc00af28800%3F}, {0xc00b705e20%3F, 0x1, 0x1})
	  assignments.go:546  0xbce
go/types.(*Checker).stmt(0xc0002c9a40, 0x0, {0x12293e0%3F, 0xc00af28e80%3F})
	  stmt.go:476  0xee5
go/types.(*Checker).stmtList(0xc0002c9a40%3F, 0x0, {0xc000faf900%3F, 0x0%3F, 0x120%3F})
	  stmt.go:124  0x85
go/types.(*Checker).funcBody(0xc0002c9a40, 0xc00b57ade0, {0xc00084a330%3F, 0xc000180c80%3F}, 0xc0010c4c40, 0xc000a92810, {0x0, 0x0})
	  stmt.go:44  0x345
go/types.(*Checker).funcDecl.func1()
	  decl.go:826  0x39
go/types.(*Checker).processDelayed(0xc0002c9a40, 0x0)
	  check.go:439  0x15c
go/types.(*Checker).checkFiles(0xc0002c9a40, {0xc00b3c7990, 0x1, 0x1})
	  check.go:383  0x245
go/types.(*Checker).Files(...)
	  check.go:341
golang.org/x/tools/gopls/internal/lsp/cache.doTypeCheck({0x122ae08, 0xc001fe30b0}, 0xc007d7fe60, {{0xc0006cd3b0, 0x43}, {0xc0006cd3b0, 0x43}, {0xc001652a88, 0x4}, {0xc00a9e1c40, ...}, ...})
	  check.go:1562  0x8a5
golang.org/x/tools/gopls/internal/lsp/cache.typeCheckImpl({0x122ae08, 0xc001fe2f30}, 0xc000d9a060%3F, {{0xc0006cd3b0, 0x43}, {0xc0006cd3b0, 0x43}, {0xc001652a88, 0x4}, {0xc00a9e1c40, ...}, ...})
	  check.go:1420  0x205
golang.org/x/tools/gopls/internal/lsp/cache.(*typeCheckBatch).checkPackage(0xc00a309ed8%3F, {0x122ae08, 0xc0007dcab0}, 0xc00c022a20)
	  check.go:674  0x245
golang.org/x/tools/gopls/internal/lsp/cache.(*typeCheckBatch).handleSyntaxPackage(0xc007d7fe60, {0x122ae08, 0xc0007dcab0}, 0xc0080e9e30%3F, {0xc0006cd3b0, 0x43})
	  check.go:532  0x42a
golang.org/x/tools/gopls/internal/lsp/cache.(*snapshot).forEachPackageInternal.func2()
	  check.go:394  0x2b
golang.org/x/sync/errgroup.(*Group).Go.func1()
	  errgroup.go:75  0x56
created by golang.org/x/sync/errgroup.(*Group).Go in goroutine 720
	  errgroup.go:72  0x96
[Error - 5:14:09 PM]
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

The stack indicates that a call f(g), where g itself has a generic function type, was instantiated, and the syntax of g was found not to be one of the following forms: id, pkg.F, F[T], pkg.F[T], F[T, T2], pkg.F[T, T2].
I wonder whether it's possible that g was an anonymous function (FuncLit)? A better panic message would help.
Paging go/types experts @findleyr, @gri.

Let's reopen this as we're waiting for information from crash reports from the field, and that could take several weeks.

Let's reopen this as we're waiting for information from crash reports from the field, and that could take several weeks.

We probably won't get more data on this until the v0.15.0-pre.1 prerelease. But yes, this is definitely a real bug (albeit rare) as we've seen this in a couple google internal reports as well. Still need more info to diagnose.

Repro'ed successfully (!) in https://github.com/golang/vscode-go/issues/3114, thanks to @szesch's https://github.com/szesch/go-63933.
Notably, this reproduces at go1.21.5, but not at master, so it may have been fixed. Investigating the root cause and bisecting the fix.

This bug was inadvertently fixed in https://go.dev/cl/543176, though the root cause is addressed in https://go.dev/cl/554395.
This was a latent bug that was activated by reverse type inference in Go 1.21. Since it will be fixed by Go 1.22, I don't think we need to back-port.

Moved this to the Go 1.23 milestone, since it's not directly a gopls bug, it's already mitigated in 1.22, and we're not going to back-port the fix.


rpc: WebSocket client cannot parse Tx events

This error occurs only with Ethermint message which add a log event there
https://github.com/tharsis/ethermint/blob/main/x/evm/keeper/msg_server.go#L58
The websocket is unable to receive the tx result. I am assuming it is related to deserialization.
I managed to narrowed down the issue to those line
https://github.com/informalsystems/tendermint-rs/blob/master/rpc/src/event.rs#L75
https://github.com/informalsystems/tendermint-rs/blob/master/tendermint/src/abci/tag.rs#L50
And if I remove
    #[serde(
        serialize_with = "base64string::serialize",
        deserialize_with = "base64string::deserialize_to_string"
    )]

from the tag's Values, then it fixes the issue (I can see the tx from websocket)
Any idea how this could be fixed in a clean way?

How can we reproduce this to confirm?
One way of testing this out (with more verbose logging) is to use our RPC CLI.


update section pods are preempted unneccessarily

Preemption must not happen when
there is no pending Pod, or when the pending Pods have equal or lower priority
than the victims.

/assign @kbarnard10

@kbarnard10  - I have signed the LCA. please let me know in case I missed something.

@bsalamat 👋 Mind giving this a quick review please?
/assign @bsalamat

/assign @kbarnard10

@bsalamat  thank you for reviewing the PR, can we please get it merged?

@kpjani Please be patient. We review PRs as quickly and thoroughly as we can before merging.

/approve


Cannot access 'GanttEditorOptions' before initialization

I'm facing this issue on an Angular v8 app. I'm using the component in my app.component and have imported the Module too.
Uncaught ReferenceError: Cannot access 'GanttEditorOptions' before initialization
    at Module../node_modules/ng-gantt/fesm2015/ng-gantt.js (ng-gantt.js:63)
    at __webpack_require__ (bootstrap:83)
    at Module../src/app/app.module.ts (app.component.ts:13)
    at __webpack_require__ (bootstrap:83)
    at Module../src/main.ts (main.ts:1)
    at __webpack_require__ (bootstrap:83)
    at Object.0 (main.ts:12)
    at __webpack_require__ (bootstrap:83)
    at checkDeferredModules (bootstrap:45)
    at Array.webpackJsonpCallback [as push] (bootstrap:32)

Following are the versions I'm at:
"jsgantt-improved": "^2.4.4",
"ng-gantt": "^2.4.3",

weird.. I released another vesion.. 2.4.4  please test this out

@mariohmol , now I'm getting the following error:
ERROR in ./src/app/gantt/gantt.component.ts
Module not found: Error: Can't resolve 'ng-gantt/gantt/gantt.editoroptions' in 'src/app/gantt'

Also, I can't import it from ng-gantt because it says no exported member for GanttEditorOptions for the import below:
import { GanttEditorOptions, GanttEditorComponent } from 'ng-gantt';

let me try again here.. sorry.. still using ang7

weird that travis is passing https://travis-ci.com/jsGanttImproved/ng-gantt
what is your angular versions?

try v2.4.5


Support Workers Analytics Engine in Cloudflare Pages

You can now use Workers Analytics Engine with Cloudflare Pages (and Workers).
The new binding type can be used via the console, wrangler.toml, or API.

I'd like to contribute support for this feature, but could use a few pointers on where to start.

Hi @mlafeldt - thank you for your enhancement request.
We're super excited you'd like to contribute.
Unfortunately, this provider is a transformation of the Cloudflare Terraform Provider so any enhancements would need to happen there first. We pull in updates and new resources as soon as they're available.
I'd recommend opening an issue upstream, and enquiring there about helping add this feature.
You're always welcome to contribute to the Pulumi ecosystem - this document is a fairly good starting point, and we're always happy to help on our community slack


Error with creating virtual environment

I faced this error when trying to setup the enviroment.
Error: Command '['C:\.........\pypi\.venv\Scripts\python.exe', '-m', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.

To solve it i had to disable antivirus real time protection.


Uniform hover effect for all links in the footer

There is no hover effect applied to the links in the footer. This makes the footer less visually appealing and decreases user experience.

@khushi-joshi-05 Request you to assign this task to me under GSSOC'24.

@khushi-joshi-05 Please assign this issue to me


Add Sepolia support and remove Kintsugi support

Sepolia config: https://github.com/eth-clients/merge-testnets/pull/14

Sorry, I just realized this PR is on master branch. 😨
(not too terrible but messed up the release history)


I2C GPIO pins for touch driver

I have noticed a mistake. I2C pins are declared as following in the image:
SDA = 17
SCL = 18

However in the schematic they are wired the other way around:

Is that an error or I am misunderstanding something? :)

thanks for feedback

Closed without an answer to a legitimate question. Which one is correct.

Oh, sorry .
The schematic is correct and the sketch is marked
The pin diagram has been updated