Discussion on API spec -  Default and limit values for the API characteristics

During meeting held on 7th february, open questions were raised:

Minimum and maximum date minimum and maximum date allowed as requested time range. Currently, 15 minutes is set as the minimum (soonest time target the request can consider), and 1 year for maximum (longer date with information to extrapolate). TBD

Time interval in the request: Maximum (and minimum) lenght of the time range requested in the API. TBD

Time granularity in the response: Lenght of the information pieces in which the time interval is subdivided in the response. Default value is proposed in 1hour, so the response will include density information of each 1hour range that can be included in the requested interval. E.g. If request interval is 15minutes to 1 hour, 1 only result will be provided, if 3 hours and 45 minutes are requested, 4 results will be provided (from 0-1, 1-2, 2-3, 3-3:45). TBD

Cell size/granularity in the response: Currently both cell definition systems allow to implement different size of cells.  TBD

Participants are invited to provide their view about this issue →

On "Minimum and maximum date ":  If certain providers have the ability to offer relevant and accurate information within a shorter time frame (< 15mins) as well, I believe , it should reasonable to consider adjusting the API specifications to accommodate their capabilities and shouldn't restrict them for 15minute minimum time frame .
on "Cell size/granularity " :  When we talk about splitting the polygon into equal-sized cells, are we suggesting different approaches to developer to achieve the same like Bounding Box Approach that will ensures that the entire polygon is included and gives a simple way to create cells of the same size. However, in this approach, some cells might go beyond the polygon's actual boundaries, which could introduce inaccuracies.
And other option to  create Equal-Sized Cells Within the Polygon itself that will ensures that all cells stay inside the specified polygon, potentially providing more accurate estimates of population density. However,  this approach can be more computationally complex for implementation, and the cells may not be perfectly equal in size due to the irregular shape of the polygon.

Hi @sachinvodafone,

About time frame limits, agree on minimum date. I think we can consider a time frame from t=0, but according to the scope of the API all the data will be calculated as a prediction. Are you proposing to provide real & current data?

Proposed WF: Close time frame limits in t=0 (min) and t=1year (max) with data prediction algorithm in all the timeframe

About cellsize, If focusing on geohash cells, having equal-sized cells and agreeing on the size of those among providers can be easilly managed.

Proposed WF: Document in the API yaml that response will include equal-sized cells, focusing on the geohash cells format.

Lenght of the time frame: As stated, the minimum will be 1 set of data in case the timeframe lenght is shorter than the granularity, and we propose to stablish X days as maximum, at least for this version, since we consider that feasible and suitable for the reference use case, and also considering the size of the data required for the response. The proposed stablished on previous call, with 7 days (1 week) is ok to be consiedered as default.

Proposed WF: 1 week (7 days) is proposed as maximum time frame length.

Time granularity: Up to now, 1 hour is the default value to consider.

Proposed WF: maintain 1 hour as the time granularity for the response.
Please share your feedback about this.

Proposed WF (discussed in the meeting and based on offline discussions):

Close time frame limits in t=0 (min) and reduce max to t=(6)months (max) with data prediction algorithm in all the timeframe. That covers current use case.
Document in the API yaml that response will include equal-sized cells, focusing on the geohash cells format.
1 week (7 days) is proposed as maximum time frame length.
Maintain 1 hour as the time granularity for the response.
Open discussion on maximum requested area size, need to consider a feasible maximum response size jointly with the maximum length of the timeframe.

To open discussion focusing on open point (maximum requested area size). Feedback required previous to next meeting. Companies are invited to provide their preference before next meeting (06 March)

Close time frame limits in t=0 (min) and reduce max to t=(6)months (max) with data prediction algorithm in all the timeframe.

Why exclude historical data from the API? Probably not needed for the flight control use case, but could be useful for other use cases. Or the whole API servers exactly one use cases?

Close time frame limits in t=0 (min) and reduce max to t=(6)months (max) with data prediction algorithm in all the timeframe.

Why exclude historical data from the API? Probably not needed for the flight control use case, but could be useful for other use cases. Or the whole API servers exactly one use cases?

Hi Gregory, it was decided to focus on this reference use case first where only non-past information is required. We can include such functionality of historical in a following version.

Update from last meeting 06/03 Minutes
Agreed WF

Close time frame limits in t=0 (min) and reduce max to t=(3)months (max) with data prediction algorithm in all the timeframe. That covers current use case.
Document in the API yaml that response will include equal-sized cells, focusing on the geohash cells format.
1 week (7 days) is proposed as maximum time frame length.
Maintain 1 hour as the time granularity for the response.
Default value on level 7 (150m x 150m) (TBC). Open Discussion, please provide feedback.
Maximum requested area size, need to consider a feasible maximum response size jointly with the maximum length of the timeframe. Dependency with #10 Open Discussion, please provide feedback.

Update from last meeting 20/03 Minutes
Agreed WF
→ Open discussion on maintaining the default geohash level in 7, but include an optional parameter in the request for the consumer to select a different value. "Not supported" error to be analyzed on those cases
→ Max area still under discussion

Setting the default geohash to 7 seems suitable. However, the provider should specify to the client which geohash levels it supports, as this may vary among providers, to prevent unnecessary "Not supported" errors.

Support a input parameter for the developer to select level (optional, default ==7), and create a "level not supported" error. To consider in future release the analysis of other global grids.
Solved in #21
Max area size is leave open (technically) to a reasonable use case management, each operator launch an error in case the size is not supported. To include error in code

Closed as fixed in #21


Bumps sbt-org-policies Plugin Version

This PR integrates Milestone 2 of sbt-org-policies plugin.
Please, @fedefernandez @raulraja   could you review? Thanks!

Codecov Report

Merging #144 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #144      +/-   ##
==========================================
- Coverage   75.94%   75.86%   -0.09%
==========================================
  Files          33       33
  Lines         291      290       -1
  Branches        2        2
==========================================
- Hits          221      220       -1
  Misses         70       70

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 ca93d1d...9b7c05d. Read the comment docs.


[Q] Upgrade version 3.25 to 3.30 : tsversion: error while loading shared libraries: libsrt.so.1.4: cannot open shared object file: No such file or directory

Hi,
I use Tsduck version 3.25 with ubuntu 21.10.
when i upgrade version to 3.30 i have this error :
tsversion --check
tsversion: error while loading shared libraries: libsrt.so.1.4: cannot open shared object file: No such file or directory
when i downgrade to 3.25 all it's ok.
Thank you for helping

hi @Anas92230
Have you launched the script "install-prerequisites" first ? That's one way to fix your problem.
The other way is to install the libsrt.so.1.4 package manually. Some info here.

hi @moving-digital
Thank you for your help i just install "apt install libsrt1.4-openssl" and install 3.30 version and all it's ok now :-)

Hello @Anas92230 ,
There is somethink weird here. I understand that installing libsrt fixes the issue because this is a prerequisite. But I do not understand how you could have installed tsduck without libsrt being installed first. The installation of tsduck should have failed.
Example using official 3.30 binary:
$ sudo dpkg -i tsduck_3.30-2710.ubuntu21_amd64.deb
Selecting previously unselected package tsduck.
(Reading database ... 193542 files and directories currently installed.)
Preparing to unpack tsduck_3.30-2710.ubuntu21_amd64.deb ...
Unpacking tsduck (3.30-2710.ubuntu21) ...
dpkg: dependency problems prevent configuration of tsduck:
 tsduck depends on libsrt | libsrt1 | libsrt1-openssl | libsrt1.4-openssl; however:
  Package libsrt is not installed.
  Package libsrt1 is not installed.
  Package libsrt1-openssl is not installed.
  Package libsrt1.4-openssl is not installed.

dpkg: error processing package tsduck (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 tsduck

Of course, you can still use some --force-all option in dpkg to force the installation despite the lack of dependency but the error message indicates that it won't work anyway.
@moving-digital, the install-prerequisites script is used to setup the environment to build TSDuck. Once a binary package is produced, the dependencies are enforced by the package management (apt and dpkg on Ubuntu).

hello @lelegard
previsouly i always have 3.25 version and i used tsversion --upgrade.
After that when i check version with tsversion --version i had this error :
tsversion: error while loading shared libraries: libsrt.so.1.4: cannot open shared object file: No such file or directory
i used also apt install ./tsduck_3.30-2710.ubuntu21_amd64.deb => same problem.


this commit fixes #6

It also covers issues with modules not included in the Bigfast build

@phemmylintry

@nseetim @odizee can i get a reason why this has not been merged yet?

 Do you read readme file on how to set this up?

The requirements file covers all the modules/library needed in bigfast. This is because i am currently one of the contributors and i know and have experienced issues with not having all the modules installed. That is why i added it @samsoft00

I understand you @blacdev, but I think we can fix any issue right from bigfat.
Also, things seems to be working perfectly from my side, I didn't install any other package aside the basic requirements.

Okay then. I'll take them out now. @samsoft00

@samsoft00 @blacdev
I noticed some packages are still missing even when I installed bigfast directly, I don't know why that is but it doesn't hurt to have all the requirements there just to be double sure. bigfast itself is currently ongoing changes every time. So we don't break production. Thanks

@phemmylintry i'll add it back. Do i also add a better env.sample file that covers all env variables?

@blacdev Error from google when testing with keys


refactor(fiatconnect): update fiat details screen to match design

Description
Part 1 of updates to fiat details screen to match design: https://www.figma.com/file/bwIY7peeykI8K4wTrXs4iN/Fiat-Connect?node-id=1496%3A33857

Removed select provider option
Updated header to include provider info
Add description before form
Use keyboard scroll view and spacer
Use number keyboard for Account Number

https://user-images.githubusercontent.com/5062591/183028784-fa678678-9c83-4b99-80c9-54f451a12fd1.mp4
https://user-images.githubusercontent.com/5062591/183029007-8cf8a992-5aa1-414c-80aa-c0e9eb5943ac.mp4
Other changes
N/A
Tested
Manually
How others should test
N/A
Related issues

Fixes ACT-181

Backwards compatibility
N/A

Hey @MuckT since NA is mentioned in how other should test , we are skipping this PR
Cc: @satish-ravi
Thanks!


Add C UDF Support

This PR adds support for calling C-style UDFs from within an Weld program. C UDFs are functions with with C-style symbol names. As long as the symbol name is linked with the executable, Weld can call into it.

See language.md for a detailed discussion on the semantics of the UDF node.
See examples/cpp/udfs/ for an example of using UDFs in a C++ program.

TODO: Still need to figure out how to add integration tests for the UDFs; we somehow need to link a C-callable function into the integration test suite. Alternative designs for the UDF node are also welcome.

Took a quick look -- looks pretty good. You might want to add some info on where the C function needs to be located -- I think any function in the address space of the program that calls weld_module_compile/weld_module_run is fine, right? It can be statically/dynamically linked, etc.

Also, I don't understand the challenge with the integration tests -- can you just pass a Rust function that has a C interface?

@jjthomas yeah that's what I'll try.

Okay @jjthomas, added a unit test.

Looks good, feel free to merge.


os.Clearenv sets variables to "" rather than deleting them on Windows

It appears that, on Windows, os.Clearenv sets all variables to "" rather than actually unsetting them (as it does on Linux and Unix based other platforms).
I can submit a patch for this, but wanted to clarify if it was expected behavior.
What version of Go are you using (go version)?
go version go1.7.3 windows/386
What operating system and processor architecture are you using (go env)?
windows/386
What did you do?
package main

import (
        "fmt"
        "os"
)

func main() {
        os.Setenv("FOO", "bar")
        v, ok := os.LookupEnv("FOO")
        fmt.Printf("%q %q\n", v, ok)

        os.Clearenv()
        v, ok = os.LookupEnv("FOO")
        fmt.Printf("%q %q\n", v, ok)

        os.Unsetenv("FOO")
        v, ok = os.LookupEnv("FOO")
        fmt.Printf("%q %q\n", v, ok)
}

What did you expect to see?
"bar" %!q(bool=true)
"" %!q(bool=false)
"" %!q(bool=false)

What did you see instead?
"bar" %!q(bool=true)
"" %!q(bool=true)
"" %!q(bool=false)

On linux/amd64:
"bar" %!q(bool=true)
"" %!q(bool=false)
"" %!q(bool=false)

Not intentional. Feel free to send a fix.
The Go 1.8 dev cycle is closed for the release freeze, though, so it might not make it until Go 1.9.


Seo blade tag to set social image?

The @seo blade tag can set e.g. the description like this @seo(['description' => 'foo']). But I didn't find any way to do the same for the social image? The following call (which I expected to work) resulted in an error:
ArchTech\SEO\SEOManager::set(): Argument #2 ($value) must be of type Closure|string|null, array given, called in /Users/tpetry/Documents/laravel-seo/src/SEOManager.php on line 95

@seo(['flipp' => ['blog', ['title' => 'Lorem Ipsum', 'description' => 'Lorem Ipsum, Lorem Ipsum']]])
```php

Is it not supported to set the social image with the `@seo` tag without returning any value or did I just miss the correct call?

Seems like @seo() uses seo()->set(), and Flipp needs to be used via seo()->flipp(). It then calls set() for 'image': https://github.com/archtechx/laravel-seo/blob/754b3936d0772a1d368240271ec8532353bac1e8/src/SEOManager.php#L180

Sure, but flipp() requires 2 parameters, how to do that with the @seo array parameter?

Ah hmm, seems like @seo uses flipp() correctly, it doesn't call set():
https://github.com/archtechx/laravel-seo/blob/master/src/SEOServiceProvider.php#L34-L40
I think the right syntax is @seo('flipp', [ array data ]). When you pass an array to @seo, there's no first argument indicating that this is a flipp() call, so it goes straight to set().

But @seo('flipp', [ array data ]) will output the image URL. I just want to define the social image on one view which is then used by the meta tags in the laout, exactly like @seo(['title' => 'Test123']).
To make it more clear. Here's an example:
@seo([
  'title' => 'Hello World',
  /* not possible */ 'flipp' => ['blog', ['headline' => 'Lorem Ipsum', 'teaser' => 'Lorem Ipsum, Lorem Ipsum']]
])
<x-layout>Some content</x-layout>

The @seo tag seems to only support strings for values, but the flipp and previewify functions need more parameters.

Ahh I see. Yeah hmm so:

array syntax (@seo([...])) is used for setting values rather than outputting stuff
arrays get passed to set()

So the blade directive should probably check if a passed array has a flipp key, and then call the flipp() method and exclude it from the data passed to set()?

That's a possible approach, but the same for previewify.

Perhaps your PR could check for the presence of flipp and previewify in this array ($args[0]) too?
https://github.com/archtechx/laravel-seo/blob/d12038f207b2f0588cf6f60b8a5706d478428ddf/src/SEOServiceProvider.php#L47-L52


Combine identical Makefile rules

Combine identical integrations.mysql.test and integrations.pgsql.test targets into a single integrations.test target; no need to compile twice.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2916   +/-   ##
=======================================
  Coverage   27.24%   27.24%
=======================================
  Files          89       89
  Lines       17640    17640
=======================================
  Hits         4806     4806
  Misses      12146    12146
  Partials      688      688

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 a30cc63...d2c8661. Read the comment docs.

LGTM

LGTM

But CI failed. It should be related.


Compact game list with number of players, playtime and actions.

Default load view:

Search by player:

Search by play time:

Sorting could have some logic to only sort those rows that has a proper value.
Playing Time filter could be a drop down with values: 15, 30, 45, 60.

Rebased and merged


Fix Bo3

room.battle isn't an object.
Used room.game in stead.

Good catch, but I don't want an OU Bo3 format yet...

ooh I forgot I modified that file


data-table problmes

Check "data-table" component in RTL direction:
http://codepen.io/seyedi/pen/LpYjQO
But it should look like this:
http://codepen.io/seyedi/pen/rONzdW

Is new issues or same issue as that pull request?

Same

I made a branch named data-table and optimize it for RTL support


[#2793] Change ZOOKEEPER event registration method.

handling per event -> handling bulk

Codecov Report

Merging #2795 into master will increase coverage by 0.12%.
The diff coverage is 91.07%.

@@            Coverage Diff             @@
##           master    #2795      +/-   ##
==========================================
+ Coverage   40.69%   40.81%   +0.12%
==========================================
  Files        1775     1775
  Lines       61139    61200      +61
  Branches     8586     8601      +15
==========================================
+ Hits        24881    24980      +99
+ Misses      36258    36220      -38

Impacted Files
Coverage Δ

...cluster/zookeeper/ZookeeperClusterDataManager.java
75.51% <100%> (ø)
:arrow_up:

.../collector/cluster/zookeeper/job/ZookeeperJob.java
94.11% <87.5%> (-5.89%)
:arrow_down:

...ollector/cluster/zookeeper/ZookeeperJobWorker.java
87.55% <91.26%> (+6.99%)
:arrow_up:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
77.14% <0%> (-5.72%)
:arrow_down:

...m/navercorp/pinpoint/test/OrderedSpanRecorder.java
77.9% <0%> (ø)
:arrow_up:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
81.43% <0%> (+0.37%)
:arrow_up:

.../profiler/sender/StandbySpanStreamDataStorage.java
81.35% <0%> (+1.69%)
:arrow_up:

...m/navercorp/pinpoint/rpc/packet/RequestPacket.java
89.74% <0%> (+2.56%)
:arrow_up:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
74.3% <0%> (+6.94%)
:arrow_up:

... and 6 more

Continue to review full report at Codecov.

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


External table: Checkboxes always have "-" on object mapping page

Checkboxes keep reverting to "-" state even after being checked and unchecked. The actual backend state of the checkboxes is fine though, since selected tables show up in the summary page as expected.

The VSCode merge commit broke this. That means the fix should be on the Azure Data Studio side. Seems like treeComponentRenderer wasn't changed so maybe tree itself or checkbox, which definitely had changes?

Fix has been merged.


Improve readability of reduction kernel

This PR only changes variable and function names to improve readability, and does not change any behaviors.
Concerns:  This requires JIT compilation again because texts of kernel codes are changed. Is it okay? (Personally thinking, I feel it is okay).

Changes:

J_offset => reduce_block_offset
j_offset => reduce_offset
J_stride => reduce_block_size
j_stride => reduce_stride
i => i_out
j => i_in
J => removed (not used)
out_clp2_size => out_block_size
clp2_count => reduce_block_size
get_trans_args => get_permuted_args
laxis => reduce_axis
raxis => out_axis
out_offset  =_tid % _out_block_size
out_stride = gridDim.x * _out_block_size
out_block_ num = (out_indexer.size + out_block_size - 1) // out_block_size

jenkins, test this please.

Jenkins CI test (for commit e26c79a03939fada10fc2ae620b2a6faaf8988f4, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

jenkins, test this please.

Jenkins CI test (for commit f668d83d59a7c4156de37f15a181d7c3fae4dc17, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

Cloud you split this PR?

Since this change introduces backward incompatibility to users, I separated changes in only python layter => https://github.com/cupy/cupy/pull/1580
Let me close this PR itself.


copy nodes being referenced over

This would resolve compilation error when there are nodes being referenced not copied to unittest manifest

Added manually in https://github.com/dbt-labs/dbt-core/commit/4dc6dd395edce960dfb0f563ea14376d118f2af9


Fix: cmd-click to select views

Problem:
There were two problems with selection on canvas, this PR fixes both:

cmd-click to select was not at all fixed, I somehow tricked my brain into belieiving I fixed it
double click to select was flawed, it was adding double offsets to focused component root elements. I didn't find it because I was not testing it with absolute positioned elements (my bad)

Commit Details:

Created a getAllPathsIncludingUnfurledFocusedComponents similar to getAllPaths. This fixed cmd - click to select
split the return value of getAllChildrenIncludingUnfurledFocusedComponents to children and unfurledComponents so Canvas.getFramesInCanvasContext can apply different offset to these by type

there's one more bug with generated elements, I made an entry for it in the paper doc. I will, however, wait until Rheese merges his PR before attempting to fix that

Introducing the New CMD Select. The same functionality you've always trusted, now with 100% more selection power. ~Call now to get a free click-to-zoom~


update tutorial, pictures and the portal's deployment name

The image report's section is not updated because we find a bug today. Will handle that part in the next pr.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop-0.3@820b824). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             develop-0.3     #206   +/-   ##
==============================================
  Coverage               ?   56.28%
==============================================
  Files                  ?       11
  Lines                  ?      947
  Branches               ?        0
==============================================
  Hits                   ?      533
  Misses                 ?      380
  Partials               ?       34

Flag
Coverage Δ

unittests
56.28% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Dockerized version of UBKG service

Create a Docker image of this UBKG service to run as we run other RESTful services.
Install the service on the new VM created by x-atlas-consortia/devops #26 accessible via the Gateway service set up by x-atlas-consortia/ubkg-api #90

https://github.com/x-atlas-consortia/ubkg-api/pull/96


Lighthouse slasher history size variable

Dear Stereum Devs,
thank you for the work, stereum is lovely to use.
Using lighhouse with stereum the slasher db size is configured to 16 GB by default and the slasher history size is left to its default value which is 4096. According to the lighthouse doc, this default history size would require a db size of 256GB .
Would it be possible to have an env variable to specify this slasher history size?
I would recommand to set the slasher history size to 256 by default. From what I understand of how the slashing database is filled up it would be coherent with the 16GB default size in stereum.
cheers,
Romain

Hi @romainreuillon,
Thank you for raising this issue. I agree this should be configured via some setting and also be persistent with Stereum updates.


Custom rate constant parameters cannot be set per grid cell

Looking at this
https://github.com/NCAR/micm/blob/main/include/micm/solver/state.inl#L103-L113
we seem to set the rate constant parameters once and it can't be done per grid cell.

The old link is invalid. This is the code in question
https://github.com/NCAR/micm/blob/main/include/micm/solver/state.inl#L138-L188
however, I think it's not true anymore. All you have to do is set the incoming vector properly and you can set whatever you want per grid cell

Inaccurate


bug: Gemini can't read the whole project even with @codebase variable

Describe the bug
Tried to add @codebase in avante ask to know about whole project, but it can't read the project.
To reproduce
No response
Expected behavior
with the @codebase variable, avante should know about the whole project
Installation method
Use lazy.nvim:
{
  "yetone/avante.nvim",
  event = "VeryLazy",
  lazy = false,
  version = false, -- set this if you want to always pull the latest change
  opts = {
    -- add any opts here
  },
  -- if you want to build from source then do `make BUILD_FROM_SOURCE=true`
  build = "make",
  -- build = "powershell -ExecutionPolicy Bypass -File Build.ps1 -BuildFromSource false" -- for windows
  dependencies = {
    "nvim-treesitter/nvim-treesitter",
    "stevearc/dressing.nvim",
    "nvim-lua/plenary.nvim",
    "MunifTanjim/nui.nvim",
  },
}

Environment
neovim version: 0.10.2
OS: Linux
Distribution: Arch

I have the same issue.

claude either

None of you have shared what language you're using.
My understanding is that @codebase triggers the creation of a "repo map" that is sent to the llm provider. It doesn't yet support all treesitter grammars, I believe this is what it can currently parse:
It appears that only certain languages are supported currently for the repo map:
https://github.com/yetone/avante.nvim/blob/839a8ee25a84f813545440c4c798edd25bfd68a9/crates/avante-repo-map/src/lib.rs#L51-L66
If you turn on debug logging:
https://github.com/yetone/avante.nvim/blob/839a8ee25a84f813545440c4c798edd25bfd68a9/lua/avante/config.lua#L10
Then you'll see a message like this if you're using an unsupported language:
https://github.com/yetone/avante.nvim/blob/839a8ee25a84f813545440c4c798edd25bfd68a9/lua/avante/repo_map.lua#L78-L84
Note: I also think it matters which current buffer you're prompting from. If you're trying to get typescript context in a sql file, and you include @codebase from your sql file, then I don't think it will work

I will activate debug, but I am using TS / TSreact

I tried it with go, php, html, javascript and it always said repo map empty, i think this feature is not working yet.

You can use :AvanteShowRepoMap to check whether the current project's repomap is normal.

when I check the repomap for example for Lua, I would expect to see whole files and file structure. but for example this repo, repomap does not see README.md. I don't know I should expect it to see the README.md or not but only thing it sees is following ss:

Am I on a wrong track or?


Add user-specific and developer-specific documentation (in GitHub README files, website)

[x] Update Repository Structure section in README.md
[ ]

Fixes #807

@turbomam we can collaborate on documentation updates on this branch. Feel free to suggest/make modifications as you see fit and we can work on it together.


Release 1.2.0

Let's release version 1.2.0, it contains numerous refactorings, bugfixes and the new driver option (configurable in .charles.yml) which lets you choose between phantomjs and chrome as the crawling tool.

@rultor release it, tag is 1.2.0

@rultor release it, tag is 1.2.0

@amihaiemil OK, I will release it now. Please check the progress here

@rultor release it, tag is 1.2.0

@amihaiemil Oops, I failed. You can see the full log here (spent 3min)
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/CharlesResource.java:101: warning: no @param for secret
[ERROR] public CharlesResource (
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/CharlesResource.java:101: warning: no @param for reg
[ERROR] public CharlesResource (
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/CharlesResource.java:101: warning: no @param for es
[ERROR] public CharlesResource (
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/LogsResource.java:49: warning: no @param for name
[ERROR] public Response getActionLogs(@PathParam("name") String name) {
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:125: error: unexpected text
[ERROR] * @see https://developer.github.com/v3/activity/events/types/#webhook-event-name-13
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "58" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "47" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "45" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "45" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/NotificationsResource.java:131: warning - Tag @see:illegal character: "45" in "https://developer.github.com/v3/activity/events/types/#webhook-event-name-13"
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/RestApplication.java:36: error: unknown tag: todo
[ERROR] * @todo #162:1h/DEV Checkstyle validation was added but currently the
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/SearchResultsPage.java:100: error: @param name not found
[ERROR] * @param previousPage String.
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/SearchResultsPage.java:103: warning: no @param for prevPage
[ERROR] SearchResultsPage withPrevPage(final String prevPage);
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/ElasticSearchResults.java:54: error: @param name not found
[ERROR] * @param hits Results in JSON.
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/ElasticSearchResults.java:56: warning: no @param for results
[ERROR] public ElasticSearchResults(final JsonObject results) {
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/ElasticSearchResults.java:65: error: @param name not found
[ERROR] * @param preciousPage Link to the previous page.
[ERROR] ^
[ERROR] /home/r/repo/src/main/java/com/amihaiemil/charles/rest/model/ElasticSearchResults.java:68: warning: no @param for previousPage
[ERROR] public ElasticSearchResults(
[ERROR] ^
[ERROR]
[ERROR] Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc @options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/r/repo/target/apidocs' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
container b326ba3ba18595b474e8a24603f987924e2691d0dfdc1153dc7fa4554f0aa334 is dead
Wed Oct 10 20:48:02 CEST 2018

Let's fix these javadocs...

@rultor try to release again, tag is 1.2.0

@amihaiemil Done! FYI, the full log is here (took me 5min)


Add entriesTail method to RBTree

Inspired by Java's TreeMap#tailMap method but this one automatically gives you an iterator.
The use case is cursor pagination through a long list.
I've been trying to implement cursor pagination in the IC. Think a long list of items that a client needs to fetch, e.g. comments on a post, stories on a feed, etc. The client should fetch a small number of items at a time, say 20, in order to minimize server load as well as meet IC message requirements (<2 MB for requests, I think).
Offset pagination is one option, but it's not really viable at all for real-time, dynamic data. If items get removed or added while the user is scrolling through a partial list, it can result in skipped or duplicate data rendered on the client. At least there isn't really a performance hit on the IC, since it can be implemented with array indexing thanks to orthogonal persistence.
As a result, cursor pagination is generally preferred. In web2 land, this is generally done with a SQL query WHERE id > ... LIMIT .... This requires id be sorted in some database index. On the IC, the only data structure that can emulate a sorted map like this is RBTree.
So in this PR, I add a new method to the RBTree.RBTree class that allows a user to pass in some cursor (i.e. x) to continue iterating where they left off, crucially in ~O(log n) time.

@matthewhammer might be a good candidate to review, given that he wrote the RBTree.mo code. If someone could approve the workflow run (for tests), that would also be great. Thanks!

Can you please run it again?

My (minor) concern is that having such a method will add the need to implement similar methods for other container also. Not necessarily a bad thing, but a library designer should make a statement about this.

My (minor) concern is that having such a method will add the need to implement similar methods for other container also. Not necessarily a bad thing, but a library designer should make a statement about this.

Fair enough, but I think this method is somewhat unique to RBTree, since it's the only ordered container available in motoko-base right now.


[Docs] fix shaderlab doc error

Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:

Summary by CodeRabbit

New Features

Updated syntax for declaring BlendState in shader pass configurations for improved clarity.
Simplified declaration format enhances user understanding by removing unnecessary variable identifiers.

Documentation

Revised documentation in both English and Chinese to reflect the updated syntax changes.

duplicate https://github.com/galacean/engine/pull/2306


missing-field-initializer

I'm getting this error when compiling tcmalloc with -Werror:
tcmalloc/tcmalloc/huge_page_filler.h:763:31: error: missing initializer for member '...::TryGetResult::from_released' [-Werror=missing-field-initializers]
  763 |     return {nullptr, PageId{0}};

Should that field be false or true here?

Thanks for the speedy fix! There's a bunch more missing-field-init warnings elsewhere; can I put up a PR similarly fixing them?


setup auth plugin to native password by default

Access denied for user defined in .env in MySQL 8
#1694

I completed the 3 steps below:

[*] I've read the Contribution Guide.
[*] I've updated the documentation. (refer to this for how to do so).
[*] I enjoyed my time contributing and making developer's life easier :)

Hi,
This should not be mandatory to change default auth to the old one. Please read my comment here https://github.com/laradock/laradock/pull/2156 to see the way to enable it if you want.

Fixed in https://github.com/laradock/laradock/pull/2510.

@lanphan how come my PR wasn't merged and then a year after someone does exactly same and gets merged?

Hi @Yiidiir
I'm sorry for this
When i deal with merge
Did not notice a duplicate situation
Say sorry again.

No worries.