Show descriptive message when login format is invalid

Details
Message about an invalid phone number or email entered instead of only mentioning the email is wrong. I also added a front-end error to avoid relying on the back-end message.
Related Web PR:
Fixed Issues

$ https://github.com/Expensify/App/issues/5339
Tests

QA Steps

Navigate to log in page
Enter several phone numbers or emails that are incorrectly formatted.
Press continue
Make sure the following error is thrown:

Tested On

[x] Web
[ ] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

I broke the login form here and it was fixed in this PR https://github.com/Expensify/App/pull/5352


Cabal fetches an old plutus-core version to compile

Hi, I've been trying to setup a very simple and minimal environment to compile Plutus scripts using plutus-tx.
I'm using haskell.nix and I followed the README but for some reason cabal is trying to compile plutus-core-lib-plutus-core-<IP_ADDRESS> which I suspect is an "old" version (from what I see from https://chap.intersectmbo.org/).
Here is the error I get:
warning: Git tree '/home/albertodvp/Projects/plutus-playground' is dirty
error: builder for '/nix/store/c70cypp031sgpcymsdvap7glg33s5lwc-plutus-core-lib-plutus-core-<IP_ADDRESS>.drv' failed with exit code 1;
       last 10 log lines:
       >       Expected: Either Context Info
       >         Actual: Context
       >     • In the first argument of ‘ThunkInfo’, namely ‘ctx’
       >       In the second argument of ‘($)’, namely ‘ThunkInfo ctx’
       >       In the expression: pure . Just $ ThunkInfo ctx
       >    |
       > 41 |         BuiltinResult _ _          -> pure . Just $ ThunkInfo ctx
       >    |                                                               ^^^
       > [138 of 165] Compiling UntypedPlutusCore.Evaluation.Machine.Cek.CekMachineCosts ( untyped-plutus-core/src/UntypedPlutusCore/Evaluation/Machine/Cek/CekMachineCosts.hs, dist/build/UntypedPlutusCore/Evaluation/Machine/Cek/CekMachineCosts.o, dist/build/UntypedPlutusCore/Evaluation/Machine/Cek/CekMachineCosts.dyn_o )
       > [140 of 165] Compiling UntypedPlutusCore.Evaluation.Machine.Cek.StepCounter ( untyped-plutus-core/src/UntypedPlutusCore/Evaluation/Machine/Cek/StepCounter.hs, dist/build/UntypedPlutusCore/Evaluation/Machine/Cek/StepCounter.o, dist/build/UntypedPlutusCore/Evaluation/Machine/Cek/StepCounter.dyn_o )
       For full logs, run 'nix log /nix/store/c70cypp031sgpcymsdvap7glg33s5lwc-plutus-core-lib-plutus-core-<IP_ADDRESS>.drv'.
error: 1 dependencies of derivation '/nix/store/883b7clr2b018pcmxwx73lgnrnqm1frv-plutus-playground-exe-plutus-playground-<IP_ADDRESS>-env.drv' failed to build

What am I be doing wrong?
Here is my experiment:
https://github.com/albertodvp/plutus-playground

Try using constraints: plutus-core > 1.7 in your cabal.project and cabal will probably tell you.

Ok, thanks to your hint I managed to understand what I was missing: I forced a higher version using constraints: plutus-core > 1.7 and I discovered I was missing libblst-any. I think the easier thing to do is using the iohk-nix overlays, that actually allows me to compile.
Thank you!


Don't generate mappers for enums

Don't generate mappers for enums because some enums may not have corresponding values to be mapped to each other

Actually generate mappers for enums but use valueOf instead

Use other mappers when generating mappers for classes with inner classes


Question about style of coding

have you ever considered using a more complex workflow, for the longest time, i have been using your repos to learn how to make scripts, but now that I'm older, I would like to challenge myself with more well-written projects like orca[https://github.com/richie0866/orca]
do you have any plans on continuing such projects and if so are you willing to design it better? I would love to learn how you would go about it

My workstyle or to say, signature handwriting, is a mix between vanilla Lua and Luau (I just don't utilize their fancy type checking and generics). These sort of repositories are kind of modern because they use optimization techniques that is only on Luau. I can reference as an example JavaScript and TypeScript, I can sort of imagine my code being written in a JavaScript style and theirs in a TypeScript one. Here's an example of what I am trying to say:
Luau
local stringOrNumber: string | number = "foo" -- This variable can ONLY be a string or an integer

if type(stringOrNumber) == "string" then
    local onlyString: string = stringOrNumber -- ok
    local onlyNumber: number = stringOrNumber -- not ok
end

if type(stringOrNumber) ~= "string" then
    local onlyString: string = stringOrNumber -- not ok
    local onlyNumber: number = stringOrNumber -- ok
end

Lua
local stringOrNumber = "foo" -- Lua automatically assigns the type

assert(type(stringOrNumber) == "string" or type(stringOrNumber) == "number", "The variable must either be a string or a number")

-- If stringOrNumber were to be set to a boolean value (true / false) it would error.

if type(stringOrNumber) == "string" then
    local string = stringOrNumber -- ok
    local number = stringOrNumber -- ok
end

if type(stringOrNumber) ~= "string" then
    local string = stringOrNumber -- ok
    local number = stringOrNumber -- ok
end

I also somewhat do this for some of my programs but I have my own way of doing it, I use assert instead of this new type checking syntax (that is for Luau only), which I just showed you an example of in the code block above. For reference:

This is actually an interesting discussion and I am somewhat surprised someone would ask me this. Also thank you for staying loyal to my work and that you could actually learn something!

Inactive ticket + this is not an issue, feel free to comment though.


Removing the NoneAdapter

The NoneAdapter class is never used and extends an unexisting abstract class.

Done in #121


Support PublishAsDockerFile on project resources

Today PublishAsDockerFile only supports ExecutableResources, but we should support docker files in projects.

@davidfowl this issue is relevant for me, I think I'll work on it
I also have a question about the design: I think we can provide two fluent signatures for this:

Automatically search for Dockerfile in project:

var builder = DistributedApplication.CreateBuilder(args);

builder.AddExecutable<Projects.Some_Proj>("Some_Proj")
    .PublishAsProjectDockerFile();

Specify path, in case if there's 2 or more Dockerfiles inside the project:

var builder = DistributedApplication.CreateBuilder(args);

builder.AddExecutable<Projects.Some_Proj>("Some_Proj")
    .PublishAsProjectDockerFile("/Dockerfile");

The signature can look smth like this:

// ExecutableResourceBuilderExtensions.cs

/// <summary>
/// Adds annotation to <see cref="ExecutableResource" /> to support containerization during deployment.
/// The resulting container image is built, and when the optional <paramref name="buildArgs"/> are provided
/// they're used with <c>docker build --build-arg</c>.
/// </summary>
/// <typeparam name="T">Type of executable resource</typeparam>
/// <param name="builder">Resource builder</param>
/// <param name="path">Path to the dockerfile starting from ROOT of the project. If null, first dockerfile inside the project will be used</param>
/// <returns>A reference to the <see cref="IResourceBuilder{T}"/>.</returns>
public static IResourceBuilder<T> PublishAsProjectDockerFile<T>(this IResourceBuilder<T> builder, string path = null) where T : ExecutableResource
{
    return ...
}

(P.S or should be perhaps use two different methods for this, with and without string path param?)

I'm wondering if there is a way to just get dotnet publish to pickup the Dockerfile in the project directory when AZD does its normal publish? I'd be surprised if there isn't some MSBuild properties that you can set.


Gulp Support

Are you guys planning on releasing a version using gulp?

I've replaced Grunt with Gulp as of now. The release isn't official yet, but you can download it here on the repo and it will be available with the next v1.1.0 release.

Looks great! thanks! 😄


rrdht_utils

PR summary
Provides RRDHT utilities for:

calculating a u32 "Location" for a given agent or node id
manipulating "Locations" using wrapping (circular) math
comparing the "forward" distance between two locations (i.e. always from the first point to the second point even if that means wrapping around the circle)
constructing / accessing data about "Arcs", that is, a start location and length and/or a center point and a radius
and finally determining whether a "Location" is inside an "Arc"

Review checklist

[ ] The story has unit or integration tests
[ ] No new bugs, and any tech-debt is identified and justified
[ ] There is enough API documentation (how to use)
[ ] There is enough code documentation (how the code works)

@lucksus

should this code live in its own rrDHT crate?

It certainly could. I don't have a strong opinion. There's some overhead in terms of crating a standalone error type...


node-uuid deprecation warning

Migrating these over to the re-created project on my new account.
https://github.com/matt-major-zz/do-wrapper/issues/50

Upgraded dependency - 3.12.0 published.


Add a test for shared framework not found scenario

Verify that we produce useful diagnostics.

@mikeharder have you started on this yet? If not, this is a fairly high priority issue I would like to resolve.

@jkotalik : Go ahead if you want to start on this now.  I'll remove myself from issues unless i'm actively working on them.


CP-2816 prepare for dev VPN

this PR has mainly two effects:

it simplifies the remote command by delegating the ssh setup to the sshconfig command (in other words, it assumes your ssh configuration is already setup with the right options)
it adds the --vpn and --nat cli options to sshconfig, to control whether the config file will include the ProxyCommand setting (needed to tunnel through the NAT instances) or not.

This looks good to me, I did wonder perhaps about adding a section for all SSH connections at the top of the ssh config:
Host *
ServerAliveInterval 30

Not having this in my own config can be crippling on connections where the ISP aggressively terminates TCP sessions that appear idle.

@Azrael808 those are good options, but I'll leave them for individuals to add. I have a lot of stuff in my .ssh/config that I wouldn't like this command to mess with, so I think it's best to focus on just the C+ related hosts in this one.

@lackac ah, apologies, I didn't realise this was editing only a portion of the SSH config. Your comment makes complete sense!


ERROR: Valid currency pair is only BTC/USD for now.

When i trying to run blackbird by ./blackbird here it is what message i receiving:
ERROR: Valid currency pair is only BTC/USD for now.
 But i didnt understand "how to replace all CR characters in file" thats thing what @khgiphvi said, i am not a programmer and i already googled it.
Guys in the internet saying different things how to do this,so can anyone explain what EXACTLY i need to do,to fix this issue?
p.s. i already tried to change EOL format to windows,it not helps.

There is a cmd utility specifically for the conversion of different platform line endings "dos2unix".
However is this not just the limitation that the project currently faces only supporting USD?
I see USD is hardcoded in some of the the exchange files.


[REQ]ARM support for docker

Can't run the image on a arm based Raspberry Pi 4.
Think you'll have to build the container for arm also.
Keep getting "exec /usr/bin/supervisord: exec format error"

I’ve temporarily created an ARM64 build. If you’d like to give it a try and let me know if it works, you can pull the :nightly tag instead of :latest.

Same issue
Running this on a Raspberry Pi 4
Could be I'm debugging it wrong, think it's wrong CPU architecture (tried pulling the nightly build but same error)but I keep getting this.
`
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error
exec /usr/bin/supervisord: exec format error`

Raspberry Pi 4

Are you encountering this error during startup? The build is correctly configured for ARM64, and I've verified its functionality on my MacBook M2.

Yes
The script doesn't run at all and just gives this error.
My processor does seem to be arm64

Yes
The script doesn't run at all and just gives this error.
My processor does seem to be arm64

Can you check which architecture your CPU is so i can try to make a package for you

I tried it again, today and it somehow worked.
Also sidenote is it possible to use this without overseer?
On Sat, Oct 26, 2024 at 12:50 PM Giuseppe Barchetta <
@.***> wrote:

Yes
The script doesn't run at all and just gives this error.
My processor does seem to be arm64
Can you check which architecture your CPU is so i can try to make a
package for you
—
Reply to this email directly, view it on GitHub
https://github.com/giuseppe99barchetta/SuggestArr/issues/36#issuecomment-2439672654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKYNCQNGATLJ4O3RCQ27KATZ5PI7RAVCNFSM6AAAAABQSDYXGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGY3TENRVGQ
.
You are receiving this because you were assigned.Message ID:
@.***>

I tried it again, today and it somehow worked. Also sidenote is it possible to use this without overseer?
…
On Sat, Oct 26, 2024 at 12:50 PM Giuseppe Barchetta < @.> wrote: Yes The script doesn't run at all and just gives this error. My processor does seem to be arm64 Can you check which architecture your CPU is so i can try to make a package for you — Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BKYNCQNGATLJ4O3RCQ27KATZ5PI7RAVCNFSM6AAAAABQSDYXGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZGY3TENRVGQ . You are receiving this because you were assigned.Message ID: @.>

Not at the moment, it only works with overseer/jellyseer.


Optimize minimap handling

Level 0:
Memoization of the mappings
Assumptions:

Minimap part update frequency: 250ms
Minimap Size: 80x80

The workerhandler, getMinimapPart required to probe 6400 tiles each second. Each of those iterations needs multiple, nested function calls and a lot of AL and control operations. This could create a performance overhead but can be avoided by memoizing the mappings from coordIndex to arenaTiles coordinates.
Level 1:
Compute minimap values while updating the arenaTiles
Assumptions:

Arena Size: 600x600 (excluding walls, dino no like 598)
Global Speed: 6 blocks/second

Computation of the minimap points can be further optimized by generating the minimap status while updating the arenaTiles. This  reduces the number of computations needed and spreads them out over time, avoiding spikes every 250ms.
For measuring the performance improvement,  we consider a worst case scenario, dino is trying to conquer the full 600x600 arena and there's only dino on the server, it takes dino  at least 600 x 4 / 6seconds. that is, 900 blocks per second.
If dino got georgie, and hannah and nazaki to simulatenously conquer the arena, we could cover twice as many blocks per second, that's 1800 blocks per second.
Even if dino got all templars, it would still takes 4^log2(6400/900) ≈ 51 of them to use up enough computation that's consumed by the current minimap generation mechanism every second.
Level 2:
Umm.. maybe  a different way of broadcasting the minimap?
Dino no know, but how about sending the delta vectors instead of the streaming the whole bitmap? or how about rectangles? or the convex hull as a set of vertices? or maybe splitting the minimap to more parts? or maybe..  no need? it's good already and dino is afraid to touch the client code :))

dino is afraid to touch the client code

I too am afraid to touch the client code haha.

This is the cpu graph for the last 14 days on the nyc server. I don't know how much of this is currently taken up by the minimap message generation, but it seems like it still has a lot of room to spare.
On the client, the time it takes to update the minimap seems to be negligible.
In a performance profile I did it only reported one update as taking '0.16 ms'. The other updates didn't even show up in the graph. Though I have a pretty powerful computer.
If you want to optimize things, I think there's probably more low hanging fruit in the way areas are being filled, as that has traditionally always required a lot more computing power.

I think there's probably more low hanging fruit in the way areas are being filled...

Dino already noticed that low hanging fruit in the flood fill algorithm but it was too intimidating like a bigggg pumpkin, that why dino thought of starting with smol low hanging fruits first..
then dino did a performance analysis on the workers and saww this :((

Yesss.. floodfill is eating almost all cpu time. dino then went fight the floodfill and found a way to optimize it and it seems twice as faster than current algorithm on average (dino will open a pull request as a test branch).
However the minimap part is still taking a lot more computations than it should be, it's insignificant.. but.. umm.. dino no like hogs. So dino will do the memoization part (mentioned as Level 0) and leave the rest as same.


kclient: fix filtering

I think its logically correct to trigger Updates to/from filtering as Add/Delete. K8s does this too; we should adopt their behavior and simplify our code by using theirs.
Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-basic-arm64_istio
7c7ef8697a715a8ae6b1a39ed48bd845efb32653
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


feature: add several improvements to local search

Improvements:

Let search input get focus automatically when search panel pops up

Clean search input and search result when search panel closes

When search panel pops up, click anywhere outside search panel can close it

Padding search icon and button, comparison:
before:

after:

Support to highlight keywords in title, demo:

Support to show first n highlighted results per title. Originally, search panel can only show first one result per title. Add a new configuration item local_search.top_n_per_title to config it. Default value of local_search.top_n_per_title is 1 to keep compatibility. Demo:
local_search.top_n_per_title = 0:

local_search.top_n_per_title = 1 (default):

local_search.top_n_per_title = 3:

local_search.top_n_per_title = -1 (show all results):

Note: I adjust the result concatenation algorithm to show specified number of results without overlapping highlighted word between adjacent results. It complicates the algorithm. If anyone has simpler solution, tell me ^_^

It's cool! It's exactly what i was want from searchbox. I will test it soon.

@ivan-nginx Thanks for your testing. I cannot find all the corner cases by myself. Found any bug, tell me ^_^
P.S. surprised to find someone response to my pull request so quickly

@uchuhimo in current search and in your patch — all tiltes are lowercases:

Can u do their true cases, like in post titles?
P.S. In search.xml is true cases.

@ivan-nginx I fix both of the bugs. Now title is shown with correct letter case, and result is shown with all keyword hits. Demo:

I also adjust the algorithm to order results by the hit count in article. In addition, I fix a bug that when searching one or more spaces, the result will show a frown icon (a search icon should be shown by design).
I will update pull request later. Welcome for more bug reports.

@uchuhimo seems u profi. GJ and thank's!

@ivan-nginx
What does "profi" means? Google Translate tells me that "profi" is German and means "professional", is it right?
I guess "profi" is abbreviation of "professional" in English. But I'm not sure. I'm not a native English speaker.
Just out of curiosity ^_^

@uchuhimo > I guess "profi" is abbreviation of "professional" in English.
That's right.
Check your e-mail, please.

@uchuhimo u got e-mail? What u think?
 I have checked them just now.
You report 2 bugs in your e-mails:

Search by multiwords not working or working not right
Can you give me a search.xml in English site and some keywords to reproduce the bug? It will help me a lot.
With big search data, browser is not responding for a long seconds
I did not tune it for performance. Since I have not written over 1000 line of JavaScript, I'm not sure I can solve it. But I will try my best. It will helps if you can send a large enough search.xml for reproduction.

Are there any other bugs? Send them to me together. Thanks~

@uchuhimo no no, that's all bugs for now. I just think what u don't understand this bugs or anotther any things, cause u not give some answers.

Can you give me a search.xml in English site and some keywords to reproduce the bug? It will help me a lot.
Yes, i will send it on your e-mail.

I'm not sure I can solve it.
Need just to add button to search at the left, for example. Issue is that when you press the buttons on keyboard — appear some delay and search do on each button pressed. I think, we may add some option for auto search and for search by press search button, that's what i mean.

@ivan-nginx

I just think what u don't understand this bugs or anotther any things, cause u not give some answers.

Sorry for the delay. I cannot get notification if a e-mail is treated as spam.

I think, we may add some option for auto search and for search by press search button, that's what i mean.

How about trigger search by pressing enter? It seems more intuitive than pressing search button, which is on the left side and hard to reach (at least for me).

@ivan-nginx

article is find by word "you", but not by multiwords "you can".

OK, it's not a bug. The logic is:

"you can" will be split into "you" and "can", all the position of them will be found
Since the default value of local_search.top_n_per_article is 1, search panel will show the first hit, which contains not more than 100 characters. Thus "you can find the answer in troubleshooting or you can ask me on GitHub" is not shown.

You can set local_search.top_n_per_article to 2 to get your desired result in this case (or set local_search.top_n_per_article to -1 to get all results).
The problem is: should I explain "you can" in this way? "you" + "can" or "you can", which is desired?

@uchuhimo this is simple example. The problem is with search in search.xml at sites with big data (example you get by e-mail). For example, if we want to search by multiwords "you can give it from code" and we have many many other articles with words in start with "you" or "you can" — this articles will be shown firstly, and, probally, needed article with "you can give it from code" not be shown.
By the way, if we want start search with multiwords "you can give it from code", search must shown in 1 results srticle, what contain this multiwords firstly, and, if other separated words exists, must shown it secondly, thirdly, etc.
Another words: i want to find "we wait for car" ("мы ждём машину"), and a have many many results by words "we" ("мы"), but needed article with this multiwords not exists in list. This multiwords wasn't find what u want.

@uchuhimo > OK, it's not a bug.
I understand, what this is not a bug. But, this is not search by multiwords what i need with big data (over 100 contains there).

@uchuhimo u understand what i mean? Give me anser, please.

@ivan-nginx I get what you mean. To solve this problem completely, I have to search every combination of keywords, and then sort them by their match rate. By splitting N keywords and search each of them, I scan all the articles by N passes; By combining N keywords and search each of the combinations, I scan all the articles by 2^N passes, which is apparently unacceptable, especially when the number of articles is huge.
There are several solutions/workarounds:

Use Natural language processing (NLP) to reduce the possible combination of keywords. But NLP will consume a lot of CPU resources. It's not realistic for browser environment.
Use "" to imply that "don't split it". It's Google's search rule, but not intuitive enough.
Search both of the original string and the split string, and give higher priority for results containing the original string. It means, if you search "we wait for car", results contain "we wait for car" will be shown first, and then the others. However, results containing "we wait" or "wait for car" are not guaranteed to show before results containing "we" only.

I think the third proposal is most suitable. How about you? Any better suggestion?

@uchuhimo i'm for 3rd varianr, of course. Need to show firstly by 100% contains multiwords, and others.. others results may be shown after main search keys. Search is search — if i search by "1 2 3 4 5" — search must me give article, what include "1 2 3 4 5" firstly with 100% contain, isn't it?

However, results containing "we wait" or "wait for car" are not guaranteed to show before results containing "we" only.

This is no matter. If i search by template of words and get that's what i searched — this is already victory for search. Other "we" or "we wait" no matter, if i get my searched article firstly by searched keywords.

@ivan-nginx OK, I will add two improvements in the next pull request:

Give higher priority for results containing the whole search string
add a new flag local_search.auto_search, search will be triggered by pressing enter if the value is false (It's the default behavior considering sites containing many posts)

Any supplement?

Give higher priority for results containing the whole search string.

Yes, it's will be nice.

add a new flag local_search.auto_search, search will be triggered by pressing enter if the value is false

And i may add to this option button. Will be button ot Enter.

@ivan-nginx I submit a new pull request for these 2 improvements, check it please.


Javadoc has invalid references after the recent refactorings + other fixes

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

This PR fixes some issues in the javadoc, in particular invalid links and references to stuff that no longer applies, as well as:

Useless semicolon use
Overcomplicated boolean expressions
Removes unneeded java keywords (e.g. final on private method, return ; in void).
Style fixes for Filter

I did not create a JIRA for this since this is a small fix, but please tell me in case I must create one.
R: @dhalperi

R: @jbonofre

LGTM.
I will squash the commits and amend the message to link to https://issues.apache.org/jira/browse/BEAM-475.


add changes in formatting to master

Reference issue

Type of change

What does this implement/fix?

Additional information

Codecov Report

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

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
- Coverage   88.21%   87.69%   -0.52%
==========================================
  Files          26       26
  Lines        1044     1065      +21
==========================================
+ Hits          921      934      +13
- Misses        123      131       +8

Impacted Files
Coverage Δ

mgc/independence/dcorr.py
100% <ø> (ø)
:arrow_up:

mgc/ksample/ksamp.py
81.48% <ø> (-1.86%)
:arrow_down:

mgc/ksample/base.py
88.88% <0%> (-11.12%)
:arrow_down:

mgc/discrim/discrim_two_samp.py
74.5% <0%> (-9.81%)
:arrow_down:

mgc/independence/mgc.py
100% <0%> (ø)
:arrow_up:

mgc/sims/ksample_sim.py
70.45% <0%> (ø)
:arrow_up:

mgc/independence/hsic.py
100% <0%> (ø)
:arrow_up:

mgc/independence/hhg.py
100% <0%> (ø)
:arrow_up:

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 52e33d0...bb59565. Read the comment docs.


vectorstore: openai apikey is must required only when embedder is nil

PR Checklist

[x] Read the Contributing documentation.
[x] Read the Code of conduct documentation.
[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
[x] Contains test coverage for new functions.
[x] Passes all golangci-lint checks.

@tmc @noodnik2  This pr contains a few changes:

make openai apikey must required only when embedder is nil.
collection name is duplicated with namespace. we keep namespace .

I think this is a positive change -- Can you explain removing the collection name option

collection name is the concept in chroma which is the same thing as namespace

I think this is a positive change -- Can you explain removing the collection name option

collection name is the concept in chroma which is the same thing as namespace

either we use collection or namespace

I think this is a positive change -- Can you explain removing the collection name option

collection name is the concept in chroma which is the same thing as namespace

I originally kept namespace separate from collection because I thought it was useful.  Previously, all items in the same collection were kept separate between namespaces using a filter on the query.  That is - a "collection" is like a database which can store elements logically separated into separate namespaces, enforced through (filter) predicates.
If that's not useful, then I have no concerns about removing support for this distinction.

I think this is a positive change -- Can you explain removing the collection name option

collection name is the concept in chroma which is the same thing as namespace

Perhaps I'm guilty of "overengineering" if in fact support for both together (i.e., multiple namespaces within a single collection) in my initial implementation was not needed or desired.  Good catch, if so!

btw... I don't think we should treat openai so different. Use a common embedder is good enough @noodnik2 any thought?

Not sure what you mean by "use a common embedder."  If I'm not mistaken, I had supported both the provided embedder, or the internal OpenAI embedder if one was not provided.


Branch feature add command

Codecov Report

Merging #62 into master will increase coverage by 0.14%.
The diff coverage is 84.61%.

@@             Coverage Diff              @@
##             master      #62      +/-   ##
============================================
+ Coverage     72.85%   73.00%   +0.14%
- Complexity      413      417       +4
============================================
  Files            72       72
  Lines          1271     1278       +7
  Branches        125      127       +2
============================================
+ Hits            926      933       +7
  Misses          310      310
  Partials         35       35

Impacted Files
Coverage Δ
Complexity Δ

.../java/seedu/tr4cker/logic/commands/AddCommand.java
100.00% <ø> (ø)
8.00 <0.00> (ø)

.../java/seedu/tr4cker/model/util/SampleDataUtil.java
20.00% <ø> (ø)
1.00 <0.00> (ø)

src/main/java/seedu/tr4cker/ui/TaskCard.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...c/main/java/seedu/tr4cker/model/task/Deadline.java
89.47% <85.71%> (+1.97%)
9.00 <2.00> (+2.00)

...in/java/seedu/tr4cker/logic/parser/ParserUtil.java
97.14% <100.00%> (+0.36%)
14.00 <0.00> (+2.00)

...in/java/seedu/tr4cker/storage/JsonAdaptedTask.java
100.00% <100.00%> (ø)
10.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Automated daily update to rustc (to nightly-2024-03-08)

Automated update to Github CI workflow rust.yml by create-pull-request GitHub action

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19515

Relevant Lines:
23294

💛  - Coveralls

Neat! It does run CI, but it uses my name as the PR author. I guess I'm okay with that.

If you are the author then someone else will have to ack, I was planning on just acking mechanically and not doing any checks - just stating in case something else is expected.

ACK 5d078ce660b40548c8b71b346568cf7ed8916a7e

@tcharding sgtm. The point of this pinning is to avoid CI breaking out from under us, so in theory CI is the only check that we need.

Seems like the system is working, our code does not build cleanly with this version of nightly so we shouldn't merge it, right - we have to do the update manually? Did you guys have a timeframe in mind for how often that should be done? Within a week, within a month, just when we get round to it?

Still failing and no update on our clippy issues.


Copy docs repo content

The purpose of this PR is to migrate OpenLineage/docs repo into the main OpenLineage/OpenLineage repo. The benefits of such an approach are:

synchronise releases of new features and fixes with corresponding documentation changes,
improve development process so that all the changes are done within the single PR that affects both codebase and documentation.

This PR is first in a row which is only exact copy of the documentation website. That's why it is so big. The followup PR would be to setup deployment process of documentation website. This has already been tested within https://github.com/OpenLineage/OpenLineage/pull/2875.
The proposed migration process is:

Copy repo content. At this moment we make sure all the PRs to Openlineage/docs repo are merged (valid on 21st August). After copying the content no changes to the old repo should be done.
Prepare and merge deployment process through GitHub actions that will deploy website on GitHub pages and accessible openlineage.github.io
Make sure Argos plugin is working. It requires some extra settings on the repo level. This can be done afterwards as the plugin is non-blocking.
Make Github page openlineage.github.io accessible through openlineage.io
Remove OpenLineage/docs repo

Except for one-to-one exact copy, this PR fixes spelling issues encountered (see second commit).

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.52%. Comparing base (413e94f) to head (495d9e3).
Report is 2 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2948   +/-   ##
=======================================
  Coverage   85.52%   85.52%
=======================================
  Files          58       58
  Lines        3413     3413
=======================================
  Hits         2919     2919
  Misses        494      494

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


"chaining"

Out of curiosity, I quickly implemented a test case here that generates n_data (currently 2) datasets (linear model m * xs + c) and compares

a single VB run on a combined model error with all n_data:

  param:         MVN with
                  ├── mean: [ 6.757e+00  1.002e+01]
                  ├── std:  [ 6.782e-01  4.187e-02]
  noise:         {'noise0': Gamma with
                  └── mean: (69.11101249683999, 9)}

n_data VB runs with one of the data sets and taking the posterior as prior for the next run (thus "chaining" :smile:  ):

  param:         MVN with
                  ├── mean: [ 6.672e+00  1.003e+01]
                  ├── std:  [ 7.352e-01  4.543e-02]
  noise:         {'noise0': Gamma with
                  └── mean: (67.5849803323776, 9)}

Potential issue: The results do not match. Should they?

I would have assumed this to give the same result, since the theoretical solution is exactly the same, since the model is linear (thus the linearization does not depend on m).

Even if you decrease the tolerance such that it is never reached and VB iterates 50 times -- and I would expect 50 fixed-point iterations to be enough -- you get the same result as above...

That could be checked with the analytical example, we could take 2 data points and compute the exact solution with a given prior, and then do the same thing with the sequential approach. Would Isabela or Abbas being interested to check the standard deviation part in the example for the analytical solution Thomas implemented and verify, if this is true for the subsequent iteration, and then, why this is not the case for our implementation. Maybe we still have a bug in our implementation that leads to wrong results, and then any discussion of results with a larger complexity might be obsolete.

If I skip the noise update (I know that this actually requires a new derivation of the equations...), the parameter posteriors match. So I also expect investigating the standard deviation part in the example for the analytical solution to be fruitful.


[Feature Request] Add Dialogs Template to a project from a Context Menu

Is your feature request related to a problem? Please describe.
I would like to be able to add Dialogs to a bot project from a Context Menu. It should help those developers that are starting to work with their first bots.
Describe alternatives you've considered
Create a Visual Studio Extension for adding the classes and accessors needed to use Dialogs in a bot project. The user should press right click on the project and select Add -> New Item -> Dialogs Template.
It would be great if the tool added all the necessary configurations and references for the user just compile and test the bot.
To review:
We created a POC in PR #177 to showcase a possible approach to implement this feature.

LGTM! 👍


iOS flutter_inapp_purchase in ios geting error listen (FlutterInappPurchase.purchaseError)

@arisbartee @LinusU @emostar @nucleartux
Please help me for same.
Version of flutter_inapp_purchase
flutter_inapp_purchase: ^5.6.1
Platforms where the error occurred (iOS)
The error occurred on iOS only.
Expected behavior
Actual behavior
Tested environment (Emulator? Real Device?)
Real Device
Steps to reproduce the behavior
When initiating my payment process using the following code:

await FlutterInappPurchase.instance.initialize();
connectionSubscription = FlutterInappPurchase.connectionUpdated.listen((connected) { print("test") });
purchaseUpdatedSubscription = FlutterInappPurchase.purchaseUpdated.listen((productItem) async) { print("test") });
purchaseErrorSubscription = FlutterInappPurchase.purchaseError.listen((purchaseError) { print("test") });

I encounter an error at the 4th step. Every time the control reaches the 4th step, my payment process halts, but this issue occurs only on iOS.

Is it work on emulator?

@KyawSoeW1n  not its not work on emulator , i have check and test in real iPhone device


Failed to compile

I have previous had good luck with this package, but now that I try to combine it with react-native-firebase it fails to compile to a real android device.
The react-native-firebase requires some fiddling within the native android code - so the might be the reason why it fails - I'm just not able to fix it and ask for a little help.
I hooked up react-native-firebase first (native code fiddling) and then I ran the react-native link.
../node_modules/react-native-huawei-protected-apps/android/src/main/java/com/github/pgengoux/huaweiprotectedapps/HuaweiProtectedAppsPackage.java:25: error: method does not override or implement a method from a supertype
    @Override
    ^
1 error
:react-native-huawei-protected-apps:compileReleaseJavaWithJavac FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-huawei-protected-apps:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

Is just because since<EMAIL_ADDRESS>@Override is deprecated, remove
    @Override
    public List<Class<? extends JavaScriptModule>> createJSModules() {
        return Collections.emptyList();
    }

from ../node_modules/react-native-huawei-protected-apps/android/src/main/java/com/github/pgengoux/huaweiprotectedapps/HuaweiProtectedAppsPackage.java
and it work :p

Fixed using pull request #2 from @elieteyssedou
Sorry for the delay!


Jorge Osto Sprint Challenge, all tasks done.

Hey @gikko1 I finished the sprint challenge, this is my pull request.

Git-Comments

[x] Utilizing Meaningful Commit Messages
[x] Committing Often: On Every Breakthrough or Feature Completion.
[x] Submitted a Pull Request with your First & Last Name in the title.

Comments

Congratulations, you have met expectations and are properly utilizing git version control.
 If you have not yet tried it
Using git from the command line with bash you can do the following:

git commit -m "Implemented Desktop Break-Points
> CSS Break-Points with media query at 1024px max-width
> Tested in Chrome, Firefox
> Fluid transition between breakpoints."

Press Enter when you want a new line. When you see the `>`
symbol this means that you have pressed Enter and there is a
new line. Remember to close your quotes at the end of your
message and press Enter to submit the command.


Xcode beta 5: integrating Swift 2.0 branch issues

I'm getting these errors when pulling from the pod spec 2.0.0-beta.1

Also when just trying to pull straight form the swift-2.0 branch. I'm receiving this error from cocoapods.
[!] A dependency with an external source may not specify version requirements (Alamofire).

Could you please post your Podfile?

source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '9.0'
use_frameworks!
pod 'Alamofire', '2.0.0-beta.1'
pod 'UICountingLabel'
pod 'Timepiece', :git => "https://github.com/naoty/Timepiece.git", :branch => "swift-2.0"
pod 'CryptoSwift', :git => "https://github.com/krzyzanowskim/CryptoSwift", :branch => "swift20"
pod 'TTTAttributedLabel'
pod 'MBProgressHUD'

I'm using Carthage and get the same error while building:
[...]/Carthage/Checkouts/Alamofire/Source/Manager.swift:75:20: error: cannot invoke 'CFStringTransform' with an argument list of type '(CFMutableString, UnsafeMutablePointer<  CFRange>, CFString, Bool)'
[...]/Carthage/Checkouts/Alamofire/Source/MultipartFormData.swift:260:27: error: 'NSURL' does not have a member named 'checkPromisedItemIsReachableAndReturnError'
[...]/Carthage/Checkouts/Alamofire/Source/ServerTrustPolicy.swift:166:41: error: cannot invoke 'SecPolicyCreateSSL' with an argument list of type '(Bool, CFString)'
[...]/Carthage/Checkouts/Alamofire/Source/ServerTrustPolicy.swift:172:45: error: cannot invoke 'SecPolicyCreateSSL' with an argument list of type '(Bool, CFString)'
[...]/Carthage/Checkouts/Alamofire/Source/ServerTrustPolicy.swift:176:17: error: cannot invoke 'SecTrustSetAnchorCertificatesOnly' with an argument list of type '(SecTrust,    Bool)'
[...]/Carthage/Checkouts/Alamofire/Source/ServerTrustPolicy.swift:203:45: error: cannot invoke 'SecPolicyCreateSSL' with an argument list of type '(Bool, CFString)'
A shell task failed with exit code 65

I just realized that I was still using beta 4. I was sure I was using beta 5. It work fine with beta 5.
@Prince2k3 are you sure you have beta 5? Maybe try to clean and rebuild.

For the record they fixed it in 62947d6deffc30d3128da580d91084a174fe485d

Ah you are right @jschmid. I am on beta 4. Thanks for figuring that out. I felt the same thinking I was on beta 5 Xcode. Argh ... closing this one

Glad everyone figured it out! 👍🏼


Not use more than one global variable. Think about it. You will have to explain its purpose (Optional)

Important to think: Global Variable create a strong dependency, maybe this can broke future changes in code

we didn't use global variable


[BUG] Current NPC HP reset after next turn

Hello,
FVTT 0.8.6
Nextup: latest
Browser: Chrome
Dnd: 1.3.5
When I remove HP from a NPC token, and it is that NPC turn, when pressing the NEXT TURN button, the NPC goes back to its previous HP count.
https://user-images.githubusercontent.com/1687854/123014386-78e21580-d3c6-11eb-9117-3fc4ae7a13d3.mp4

Is this will no other modules enabled ?

@kandashi nope, only next up module.

Can you check without any modules, I'm not sure how next up would be triggering this

@kandashi made the test, no issue without any modules.
Note that the demo video showcases a combat without any PCs, only NPCs, could it be smt in relation with combats without PCs?

@kandashi made the test with a PCs as well in the combat. Same issue.

@kandashi tested in a new world with only next up & libwrapper (as suggested by the module).
No prob at first.
Then, after matching my world configuration, trouble started. Maybe if you match this exact same config, you will have the issue?

Well, I can replicate, now to figure out whats up

Found the problem, fix going live soon


better document what libraries work in front-end/how to use libraries on the front-end

Problem
People don't understand that a compilation step prevents them from being able to use some libraries on the front-end; folks try to pull dependencies like @google-cloud/speech into React components, as an example, and the webpack error they receive is cryptic.
Long term solution
There's already awesome work in process by folks like @eoogbe and @alexander-fenster to reduce our reliance on compiled node.js libraries over time (hooray \o/).
But, it will take a while to reach this vision of the future.
Stop Gap Solution
It would be nice to be able to demonstrate to people how they might still use some of our compiled libraries in web applications...
What if we added samples to some of our more popular GAPIC libraries that demonstrates how to build a simple client/server applications that interacts with them?

Note 1: for the time being (while GAPIC libraries are server-side only), we can direct people to use googleapis package which can be used in browser. This is worse in terms of usability but an acceptable alternative.
Note 2: even when we start fully supporting GAPIC libraries in browser using gRPC-Web, some gRPC functionality (client streaming calls) will never be supported (until gRPC-Web implements it).

an update, triaging issues today there were at least 5 that related to folks not understanding that various Node.js libraries that were installed couldn't webpack.
@alexander-fenster I love your idea of calling out the fact (in our READMEs  perhaps?) that googleapis is an alternative to the GAPIC libraries); I also think calling out in general in our READMES the fact that some of our libraries (in googleapis as well) won't necessarily work in he browser.

I don't think this would be applicable to all languages (just node.js?). If we do put this information in .repo-metadata.json, it would probably be a good time to specify how language specific information gets added with a json schema.

@busunkim96 I agree, the frontend/backend dichotomy really only comes up in JavaScript right? I wonder if we could look for the gapic dependency when generated docs?

We are working on an RFC to address the problem of a Web SDK more holistically.


Single tech/synapse serverless delta cls

Type of PR

Documentation changes
Code changes

Purpose
This sample aims to demonstrate the use of Synapse Serverless Pools with Delta Lake files.
A second objective includes to share findings around the automation of view creation on top of the Data Lake.
And lastly, it demonstrates how to implement CLS (Column Level Security) on the delta tables using the views.
Does this introduce a breaking change? If yes, details on what can break
No breaking changes. Isolated folder under single-tech-samples.
Author pre-publish checklist

[X] No PII in logs
[X] Made corresponding changes to the documentation

Issues Closed or Referenced

Closes #545

Might be best to put this under /single_tech_samples/synapseanalytics as we already have an existing synapse analytics sample?


Make launch.json envFile vars available for consumption in args:[]

I'd like to be able to have a .env file that has variables describing (in my case) positional input args to a debug config.  I have about 100 debug config cases and I have to go and update ALL the input args to a NEW file if I want to go back and debug some regression.
So in my .env file I want to define ARG1="path to some file", ARG2="path to some other file" and then define:
      "envFile": "${workspaceRoot}/.vscode/.env",

and then in the SAME config JSON
      "args": [
         "-V",
        "${workspaceRoot}/${env:ARG1}",

That way I only have to define my test/debug arg files in one place.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Declare support for multimon in proxy server.

Unfortunately, by mistake, in the DISP PR the multimon was broken (the UseMultimon was set to FALSE, then gcc_write_client_monitor_data wasn't called).
This PR fixes it.

@freerdp-bot test


service worker not Registered :/

Show message in console
Uncaught (in promise) DOMException: Only secure origins are allowed (see: https://goo.gl/Y0ZkNV).
I'm working in localhost... <IP_ADDRESS> with LAMP server on Elementary Os and Vhost added
Help me, please!

What's the url for your ajax call?

That happens for not reading correctly...
I thought that by registering the service-worker.js the file was automatically created...

This is the code where I'm trying to register service but...
// TODO add service worker code here
if ('serviceWorker' in navigator) {
navigator.serviceWorker
.register('./service-worker.js')
.then(function() { console.log('Service Worker Registered'); })
.catch(function(err){
console.log('Filed to register', err);
});
}
Always falls into the catch :/

Well, I was making use of vhost, which is why I got error with the service-worker.js

Hi!
Thanks for the feedback. I've rewritten the codelab from scratch and believe I have fixed this issue. The code has been updated, and the new guide is now live.
If you find any issues with the new codelab, please let us know!
Thanks!


Exception handling

Pull request information

Status: ready to merge
Kind of changes: more descriptive error messages
Related PR or issue: N/A

Description
I'm adding more descriptive error messages in TraCIVehicle, Env, and MultiEnv so that we have fewer silent failures. In general, we should limit our use of try-except.
A few locations are commented out (up for discussion), because those are somehow intentional try-except messages, and currently would generate a lot of error messages if we printed the traceback.

Thanks for the fix @AboudyKreidieh !

Pull Request Test Coverage Report for Build 4077

7 of 8 (87.5%)  changed or added relevant lines in 2 files are covered.
356 unchanged lines in 18 files lost coverage.
Overall coverage increased (+1.2%) to 91.824%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

flow/multiagent_envs/multiagent_env.py
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

flow/scenarios/grid.py
1
99.48%

examples/sumo/bay_bridge_toll.py
1
97.3%

examples/rllib/multiagent_exps/multiagent_traffic_light_grid.py
1
98.48%

tests/fast_tests/test_environments.py
1
99.68%

examples/rllib/multiagent_exps/multiagent_figure_eight.py
1
98.39%

flow/renderer/pyglet_renderer.py
2
95.17%

tests/fast_tests/test_util.py
3
96.08%

tests/setup_scripts.py
3
97.76%

flow/envs/merge.py
5
93.18%

flow/scenarios/bottleneck.py
5
88.64%

Totals

Change from base Build 3919:
1.2%

Covered Lines:
8670

Relevant Lines:
9442

💛  - Coveralls


Fix in trace_generator.py

I am using the gem5-aladdin Docker image. I attempted to generate the simulation files in a directory different from /workspace/gem5-aladdin/sweeps, and while configs and gem5_binary generated without issue, trace was throwing an error:
use benchmarks.designsweeptypes.Gem5DesignSweep
begin Gem5DesignSweep boa_experiment
use benchmarks.machsuite.*
generate configs
generate trace
generate gem5_binary
set output_dir "output_dir"
set source_dir "/workspace/gem5-aladdin/src/aladdin/MachSuite"
set simulator "gem5-cpu"
set memory_type "cache"
set cycle_time 5
set unrolling for bfs_bulk.bfs.loop_horizons 1
set unrolling for bfs_bulk.bfs.loop_neighbors 0
set unrolling for bfs_bulk.bfs.init_horizons 0
set unrolling for bfs_queue.bfs.init_horizons 0
set unrolling for gemm_blocked.bbgemm.loopjj 1
set unrolling for gemm_blocked.bbgemm.loopkk 1
set unrolling for gemm_blocked.bbgemm.loopk 0
set unrolling for gemm_blocked.bbgemm.loopj 0
set unrolling for gemm_ncubed.gemm.outer 1
set unrolling for gemm_ncubed.gemm.inner 0
set unrolling for kmp_kmp.CPF.c2 1
set unrolling for kmp_kmp.kmp.k2 1
set unrolling for md_grid.md.loop_grid0_x 1
set unrolling for md_grid.md.loop_grid0_y 1
set unrolling for md_grid.md.loop_grid0_z 1
set unrolling for md_grid.md.loop_grid1_x 1
set unrolling for md_grid.md.loop_grid1_y 1
set unrolling for md_grid.md.loop_grid1_z 1
set unrolling for md_grid.md.loop_p 0
set unrolling for md_grid.md.loop_q 0
set unrolling for sort_radix.last_step_scan.last_2 0
set unrolling for sort_radix.local_scan.local_2 0
set unrolling for sort_radix.hist.hist_2 0
set unrolling for sort_radix.update.update_2 0
set unrolling for sort_radix.ss_sort.sort_1 1
set unrolling for spmv_crs.spmv.spmv_2 0
set unrolling for spmv_ellpack.ellpack.ellpack_2 0
set unrolling for md_knn.md_kernel.loop_j 0
set unrolling for nw_nw.needwun.fill_in 0
set unrolling for nw_nw.needwun.trace 1
set unrolling for nw_nw.needwun.pad_a 1
set unrolling for nw_nw.needwun.pad_b 1
set unrolling for sort_merge.ms_mergesort.mergesort_label1 1
set unrolling for sort_merge.ms_mergesort.mergesort_label2 1
set unrolling for stencil_stencil2d.stencil.stencil_label1 1
set unrolling for stencil_stencil2d.stencil.stencil_label3 0
set unrolling for stencil_stencil2d.stencil.stencil_label4 0
set unrolling for stencil_stencil3d.stencil3d.height_bound_col 1
set unrolling for stencil_stencil3d.stencil3d.height_bound_row 0
set unrolling for stencil_stencil3d.stencil3d.col_bound_height 1
set unrolling for stencil_stencil3d.stencil3d.col_bound_row 0
set unrolling for stencil_stencil3d.stencil3d.row_bound_height 1
set unrolling for stencil_stencil3d.stencil3d.row_bound_col 0
set unrolling for stencil_stencil3d.stencil3d.loop_height 1
set unrolling for stencil_stencil3d.stencil3d.loop_row 0
set memory_type for aes_aes.rcon "spad"
set memory_type for fft_transpose.twiddles8.reversed8 "spad"
set memory_type for fft_transpose.data_x "spad"
set memory_type for fft_transpose.data_y "spad"
set memory_type for kmp_kmp.pattern "spad"
set memory_type for kmp_kmp.kmpNext "spad"
set memory_type for kmp_kmp.n_matches "spad"
set memory_type for stencil_stencil2d.filter "spad"
set memory_type for stencil_stencil3d.C "spad"
set memory_type for viterbi_viterbi.obs "spad"
set partition_type for aes_aes.rcon "complete"
set partition_type for fft_transpose.twiddles8.reversed8 "complete"
set partition_type for fft_transpose.data_x "complete"
set partition_type for fft_transpose.data_y "complete"
set partition_type for kmp_kmp.pattern "complete"
set partition_type for kmp_kmp.kmpNext "complete"
set partition_type for stencil_stencil2d.filter "complete"
set partition_type for stencil_stencil3d.C "complete"
set partition_type for viterbi_viterbi.obs "complete"
set memory_type for aes_aes.sbox "spad"
set memory_type for bfs_queue.queue "spad"
set memory_type for fft_transpose.work_x "spad"
set memory_type for fft_transpose.work_y "spad"
set memory_type for fft_transpose.DATA_x "spad"
set memory_type for fft_transpose.DATA_y "spad"
set memory_type for fft_transpose.smem "spad"
set memory_type for nw_nw.M "spad"
set memory_type for nw_nw.ptr "spad"
set memory_type for sort_merge.temp "spad"
set memory_type for sort_radix.b "spad"
set memory_type for sort_radix.bucket "spad"
set memory_type for sort_radix.sum "spad"
set memory_type for viterbi_viterbi.llike "spad"
end boa_experiment
Building gem5 binaries for aes_aes
Building gem5 binaries for bfs_bulk
Building gem5 binaries for bfs_queue
Building gem5 binaries for fft_strided
Building gem5 binaries for fft_transpose
Building gem5 binaries for gemm_blocked
Building gem5 binaries for gemm_ncubed
Building gem5 binaries for kmp_kmp
Building gem5 binaries for md_grid
Building gem5 binaries for md_knn
Building gem5 binaries for nw_nw
Building gem5 binaries for sort_merge
Building gem5 binaries for sort_radix
Building gem5 binaries for spmv_crs
Building gem5 binaries for spmv_ellpack
Building gem5 binaries for stencil_stencil2d
Building gem5 binaries for stencil_stencil3d
Building gem5 binaries for viterbi_viterbi
Building non-DMA traces for aes_aes
Traceback (most recent call last):
  File "/workspace/gem5-aladdin/sweeps/generate_design_sweeps.py", line 31, in <module>
    main()
  File "/workspace/gem5-aladdin/sweeps/generate_design_sweeps.py", line 28, in main
    run(args.xenon_file)
  File "/workspace/gem5-aladdin/sweeps/generate_design_sweeps.py", line 12, in run
    genfiles = interpreter.run()
  File "/workspace/gem5-aladdin/sweeps/xenon/xenon_interpreter.py", line 87, in run
    genfiles = self.generate_outputs()
  File "/workspace/gem5-aladdin/sweeps/xenon/xenon_interpreter.py", line 80, in generate_outputs
    generated_files = sweep.generateAllOutputs()
  File "/workspace/gem5-aladdin/sweeps/xenon/base/datatypes.py", line 408, in generateAllOutputs
    genfiles = generator()
  File "/workspace/gem5-aladdin/sweeps/benchmarks/designsweeptypes.py", line 44, in generate_trace
    return generator.run()
  File "/workspace/gem5-aladdin/sweeps/generators/trace_generator.py", line 77, in run
    os.rename(trace_orig_path, trace_new_path)
OSError: [Errno 18] Invalid cross-device link: '/workspace/gem5-aladdin/src/aladdin/MachSuite/aes/aes/dynamic_trace.gz' -> '/workspace/boa/test/warmup/output_dir/aes_aes/inputs/dynamic_trace.gz'

I managed to fix this by slightly modifying gem5-aladdin/sweeps/generators/trace_generator.py. In particular, after inserting import shutil at the top, I modified line 77 from os.rename(…) to shutil.move(…), which according to https://stackoverflow.com/questions/42392600/oserror-errno-18-invalid-cross-device-link seems to be the recommended way of moving files in Python 3, though it might still error out in Python 2.

Just updated the commit message to the suggested one.


Decimal precision seperator

How to change decimal precision seperator dot (.) to comma (,)?

This component uses the native <input type="number"> element for inputting and it does not support comma as the decimal precision separator.

it should use it. because every country have their own cultures... why you closed the issue without my opinion?

I'm sorry, I mean this component will not support that feature.


Potential url-parsing issue during document processing

Proceed with the following attachment
exception.txt

Actually comes from the problem of urllib python package, and urlsplit function.


Website: "Learn about ...." links are broken

You've moved files around in the repo but haven't updated the links. 3/4 are broken.

Learn how to build Yarn Spinner from source.
Learn more about Yarn, and the Yarn editor.
Learn more about writing dialogue in Yarn.
Learn about using Yarn Spinner in your Unity game.

Many apologies for the delayed reply. Are you talking about the first four dot points from 'What To Do Next' on https://github.com/thesecretlab/YarnSpinner/blob/master/README.md ? I've just tested them and they seem to be currently working. If you could clarify it'd be greatly appreciated. Once again, my apologies for the delay.

I think he might be referring to the learn links on your website.
https://www.secretlab.com.au/yarnspinner

@PeteLawler: No worries. Just mentioning small errors I happen to notice as I pass through.
@james-sullivan: Yes that's correct.

Ah right, that is a page owned by Secret Lab, the creator of and major contributor to the project but owned by that company and not generated by this project. As such, I'm going to ping @desplesda and @parisba about it, as they own that company. However, as it's not anything specific to this project or able to be edited by this project, this is an invalid bug. I encourage you to contact Secret Lab via https://www.secretlab.com.au/contact-rally  if they do not respond to my ping here.

Fixed 😍


The minimum size of TPM NV 0x01C101C0

The minimum size of NV 0x01C101C0 is unclear from the document.

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

ID: 31d623d9-316c-0ef1-b6be-c3773d77ca21
Version Independent ID: 83ddb59d-0cfc-34f2-e666-8927d86a04a7
Content: System Guard Secure Launch and SMM protection (Windows 10) - Windows security
Content Source: windows/security/threat-protection/windows-defender-system-guard/system-guard-secure-launch-and-smm-protection.md
Product: m365-security
Technology: windows-sec
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@e0i   Created PR #10167 for a different issues.


[REQUEST] - Automatically screen creation and rotation

First of all I would like to give credits to the devs of this project. One of the nicest and useful Dashboard for Zabbix I've encounter.
The situation is that sometimes when you have a 4 columns configuration, not all hosts fit in one single window. You would have to squeeze everything into 6 or more columns.
Would be very nice to have options in the settings to;
- If set to X number of columns and hosts do not fit in screen.
- Automatically create new screen and rotate XX number of seconds.

I love this idea. It might be dependent on the height of the screen, so that would be needed to taken into account. (if bottom of a row div goes past the viewport height?) I'm not a CSS expert - and don't have a ton of time right now - but help welcome


Pulling jessie-20180926 (current latest) fails on rpi1

I have a strange problem. Pulling the current latest (jessie-20180926) fails on my rpi1:
$ docker pull resin/rpi-raspbian:jessie-20180926
error pulling image configuration: Get https://production.cloudflare.docker.com/registry-v2/docker/registry/v2/blobs/sha256/ab/abe564b9f580b5631c14d54358babedbffde08207218756c5ee191f5daebc256/data?verify=1538821028-X9vHOQq%2BBhwHRG%2FkeZ5EGy1vur4%3D: net/http: TLS handshake timeout

The Sha256 hash is sometimes different, but I think there was only three or four different.
Pulling the previous jessie-20180815 works. Also pulling this image on a amd64 PC works. First I thought this is a temporary problem in the docker hub infrastructure, but I tested daily since the 20180929 and it had failed every day.
Any Ideas how I can fix this?

Hi, @StefanSchoof, what version of Docker are you have on the Pi1? (what OS are you running on the Pi1?)
We know issues with Docker HUB regarding pulling on Pi1 (well, armv6) devices, since they switched to Cloudflare, but we don't have enough info to pin it down.
The newer Docker/Balena versions should be working, but there's a window of versions that we've seen the same issue you report (though reproducibly). Thus hearing more details from you could helps us hunt down the issue further!
Have a potential workaround, but it depends on the OS/Docker that you are using, so that would help a lot to know.

Thanks for the reply:
It is an raspian stretch with the kernel from Hypriot (4.14.34-hypriotos+ #2 Sun Apr 22 15:29:32 UTC 2018 armv6l GNU/Linux)  and docker from deb [arch=armhf] https://download.docker.com/linux/raspbian stretch stable
$ docker --version
Docker version 18.06.1-ce, build e68fc7a

I found a solution for me.
I added
  "max-concurrent-downloads": 1

to my /etc/docker/daemon.json. Now the pull works. I assume the rpi1 has not enough power for three parallel downloads. Why some images were working and others not is still mysterious, but now all are working.


rope scaling doesn't work

I'm trying to use rope scaling to increase the max_seq_len. I refer to #555 and modify the model's config.json to add the key rope_scaling:
{
  "_name_or_path": "m42-health/med42-70b",
  "architectures": [
    "LlamaForCausalLM"
  ],
  "bos_token_id": 1,
  "eos_token_id": 2,
  "hidden_act": "silu",
  "hidden_size": 8192,
  "initializer_range": 0.02,
  "intermediate_size": 28672,
  "max_position_embeddings": 2048,
  "model_type": "llama",
  "num_attention_heads": 64,
  "num_hidden_layers": 80,
  "num_key_value_heads": 8,
  "pad_token_id": 0,
  "rms_norm_eps": 1e-05,
  "tie_word_embeddings": false,
  "torch_dtype": "float32",
  "transformers_version": "4.28.1",
  "use_cache": true,
  "vocab_size": 32000,
  "rope_scaling": {
    "factor": 2.0,
    "type": "dynamic"
  }
}

And I initiated vLLM engine by
cache_dir = "/secure/hf_cache"
model_name_or_path = "m42-health/med42-70b"
llm = LLM(model=model_name_or_path, download_dir=cache_dir, tensor_parallel_size=4, dtype="auto")

However, when I performed inference on long prompts, I still got the warning:
WARNING 01-20 16:48:15 scheduler.py:149] Input prompt (2380 tokens) is too long and exceeds limit of 2048

Does anyone have this issue before?
p.s., version of my vllm is 0.2.7.

Looks like this should work now https://github.com/vllm-project/vllm/blob/c64cf38673780544087af5ad5d3baf879a29220b/vllm/config.py#L968-L974


P2000 error while upserting model and connect to other model

Bug description

When upserting one model (TestReport) with a 1-to-1 relation to another model (Build) the whole transaction is rollbacked, due to a P2000 error.
Reported error:
PrismaClientKnownRequestError2:
Invalid `prisma.testReport.upsert()` invocation:

  The provided value for the column is too long for the column's type. Column: \<unknown\>
    at PrismaClientFetcher.request (/usr/src/dasboard/modules/etl-manager/node_modules/@prisma/client/runtime/index.js:78782:15)
    at runMicrotasks (\<anonymous\>)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async Store.upsertTestReport (/usr/src/dasboard/modules/etl-manager/src/lib/store/store.js:90:12) {
  code: 'P2000',
  clientVersion: '2.11.0',
  meta: { column_name: '\<unknown\>' }
}

How to reproduce

No small size example, but I have detailed logging. I will also add comment inline:
Methods definitions :

create a build ConnectBlobRepo_NIGHTLY_625 via build.upsert

async upsertBuild(job, buildNumber, serviceAbbr, epoch, duration, result) {
    const variables = {
      job,
      number: buildNumber,
      job_number: job + "_" + buildNumber,
      service: serviceAbbr,
      epoch: epoch,
      duration: duration,
      result: resultToBoolean(result)
    };

    console.info("##! upsert build: ", variables.job_number);

    return await prisma.build.upsert({
      create: {
        job: variables.job,
        number: variables.number,
        job_number: variables.job_number,
        service: variables.service,
        epoch: variables.epoch,
        duration: variables.duration,
        result: variables.result
      },
      update: {
        duration: variables.duration,
        result: variables.result
      },
      where: {
        job_number: variables.job_number
      }
    });
  }

testreport.upsert connecting to the just created build (ConnectBlobRepo_NIGHTLY_625)

async upsertTestReport(job, buildNumber, reportData) {
    const variables = {
      job_number: `${job}_${buildNumber}`,
      createDataSet: {
        job_number: `${job}_${buildNumber}`,
        build: { connect: { job_number: `${job}_${buildNumber}` } },
        RegressionTestCases: reportData.RegressionTestCases,
        NonRegressionTestCases: reportData.NonRegressionTestCases,
        PerformanceAutomatedTestCases: reportData.PerformanceAutomatedTestCases,
        TotalRegressionPassed: reportData.TotalRegressionPassed,
        TotalTestCases: reportData.TotalTestCases,
        TotalNonRegressionFailed: reportData.TotalNonRegressionFailed,
        SecurityAutomatedTestCases: reportData.SecurityAutomatedTestCases,
        RegressionAutomatedTestCases: reportData.RegressionAutomatedTestCases,
        AutomatedTestCases: reportData.AutomatedTestCases,
        NonRegressionAutomatedTestCases:
          reportData.NonRegressionAutomatedTestCases,
        TotalNonRegressionPassed: reportData.TotalNonRegressionPassed,
        TotalRegressionFailed: reportData.TotalRegressionFailed
      },
      updateDataSet: {
        RegressionTestCases: reportData.RegressionTestCases,
        NonRegressionTestCases: reportData.NonRegressionTestCases,
        PerformanceAutomatedTestCases: reportData.PerformanceAutomatedTestCases,
        TotalRegressionPassed: reportData.TotalRegressionPassed,
        TotalTestCases: reportData.TotalTestCases,
        TotalNonRegressionFailed: reportData.TotalNonRegressionFailed,
        SecurityAutomatedTestCases: reportData.SecurityAutomatedTestCases,
        RegressionAutomatedTestCases: reportData.RegressionAutomatedTestCases,
        AutomatedTestCases: reportData.AutomatedTestCases,
        NonRegressionAutomatedTestCases:
          reportData.NonRegressionAutomatedTestCases,
        TotalNonRegressionPassed: reportData.TotalNonRegressionPassed,
        TotalRegressionFailed: reportData.TotalRegressionFailed
      }
    };

    console.info(
      "##! Createset",
      variables.createDataSet,
      variables.updateDataSet
    );

    return await prisma.testReport.upsert({
      create: variables.createDataSet,
      update: variables.updateDataSet,
      where: {
        job_number: variables.job_number
      }
    });
  }

Logging with annotations

gather the information for creating a build and call above mentioned upsertBuild method

upsert build:  ConnectBlobRepo_NIGHTLY_625
prisma:query SELECT 1
prisma:query BEGIN
prisma:query SELECT "dashboard$develop"."Build"."id" FROM "dashboard$develop"."Build" WHERE "dashboard$develop"."Build"."job_number" = $1 OFFSET $2
prisma:query SELECT "dashboard$develop"."Build"."id" FROM "dashboard$develop"."Build" WHERE "dashboard$develop"."Build"."job_number" = $1
prisma:query UPDATE "dashboard$develop"."Build" SET "result" = $1, "duration" = $2 WHERE "dashboard$develop"."Build"."id" IN ($3)
prisma:query SELECT "dashboard$develop"."Build"."id", "dashboard$develop"."Build"."duration", "dashboard$develop"."Build"."epoch", "dashboard$develop"."Build"."job", "dashboard$develop"."Build"."job_number", "dashboard$develop"."Build"."number", "dashboard$develop"."Build"."result", "dashboard$develop"."Build"."service", "dashboard$develop"."Build"."testReportId" FROM "dashboard$develop"."Build" WHERE "dashboard$develop"."Build"."id" = $1 LIMIT $2 OFFSET $3
prisma:query COMMIT
....

gather the information for creating a test report and call above mentioned upsertTestReport method

...
##!  Error upserting test Report PrismaClientKnownRequestError2:
Invalid `prisma.testReport.upsert()` invocation:

  The provided value for the column is too long for the column's type. Column: <unknown>
    at PrismaClientFetcher.request (/usr/src/dasboard/modules/etl-manager/node_modules/@prisma/client/runtime/index.js:78782:15)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)
    at async Store.upsertTestReport (/usr/src/dasboard/modules/etl-manager/src/lib/store/store.js:90:12) {
  code: 'P2000',
  clientVersion: '2.11.0',
  meta: { column_name: '<unknown>' }
}

Error reporting information (similar as above)

##! Service:  ConnectBlobRepo_NIGHTLY
##! Buildnumber:  625
##! TestReport:  {
  RegressionTestCases: 231,
  NonRegressionTestCases: 48,
  PerformanceAutomatedTestCases: 0,
  TotalRegressionPassed: 229,
  TotalTestCases: 279,
  TotalNonRegressionFailed: 1,
  SecurityAutomatedTestCases: 14,
  RegressionAutomatedTestCases: 231,
  AutomatedTestCases: 258,
  NonRegressionAutomatedTestCases: 27,
  TotalNonRegressionPassed: 25,
  TotalRegressionFailed: 2
}

Expected behavior

Expected behavior is to be able to upsert a TestReport and connect to the already existing Build.
Prisma information

! removed other models
Model build with one optional testReport.
model Build {
  id           String      @id @default(cuid())
  duration     Float       @default(0)
  epoch        Float?
  job          String
  job_number   String      @unique
  number       Int
  result       Boolean?
  service      String
  testReportId String?     @unique
  testReport   TestReport? @relation(fields: [testReportId], references: [id])
  testRuns     TestRun[]
}
// .....

model TestReport {
  id                              String @id @default(cuid())
  job_number                      String @unique
  RegressionTestCases             Int?
  NonRegressionTestCases          Int?
  PerformanceAutomatedTestCases   Int?
  TotalRegressionPassed           Int?
  TotalTestCases                  Int?
  TotalNonRegressionFailed        Int?
  SecurityAutomatedTestCases      Int?
  RegressionAutomatedTestCases    Int?
  AutomatedTestCases              Int?
  NonRegressionAutomatedTestCases Int?
  TotalNonRegressionPassed        Int?
  TotalRegressionFailed           Int?
  build                           Build?
}

Environment & setup

OS:  MacOSX Cataline 10.15.7 and Linux (docker image FROM node:latest = Ubuntu)
Database:  PostgresQL 10.3 in docker
Node.js version:  On MacOS: v12.18.0, On Linux docker: node:latest = 15.2.1
Prisma version:  "@prisma/client": "^2.11.0", "@prisma/cli": "^2.11.0"

Hey @claassenarjan
Can you please try this again in the latest version?
From the error message it seems to appear that one of your integer field is exceeding the database size limit so try changing that to a bigint in the database and then use introspection to use it via native types: https://www.prisma.io/docs/concepts/components/preview-features/native-types
Regarding the error message here not mentioning the exact field, there was a discussion here in the past where we concluded it can't be improved as the database doesn't return this information in the first place: https://github.com/prisma/prisma/issues/2730

Thanks, In the mean time I have restructured the database model, removing this specific query.

Thanks, In the mean time I have restructured the database model, removing this specific query.

For anyone who is getting this error at this date. 2022! just remove the length limit for the field, in my case i was waiting only for a 50 limit characters, but i need more, so i just change my db varchar to no def

@Allislove how to remove the length limit? I have this issue for a string field in Postgres... it is ridiculous, that Prisma does not include any kind of documentation on such limits etc.. it just fails, and goodbye.

@Allislove how to remove the length limit? I have this issue for a string field in Postgres... it is ridiculous, that Prisma does not include any kind of documentation on such limits etc.. it just fails, and goodbye.

Hey! Salute, can you please show the error and you code.

@JannikZed Cuz first of all "The length limit" is the database field, please share the error and the db schema, so I can help you.

in 2024 you can use :
topic String  @db.LongText()


Fix the broken URL

Summary:-
In the README.md file the header (Water.css) is not properly linkified to https://watercss.kognise.dev/
Current Behaviour
On click of link, Water.css redirects to https://github.com/kognise/water.css#watercss page.
Expected Behaviour
On click of link, Water.css redirects to https://watercss.kognise.dev/

Water.css
Just stick this in your <head>:
🌙/☀ Automatic Theme:

🌙 Dark Theme:

☀ Light Theme:

A preview of the different themes is available on the demo page! ⚡
We can use this markdown to fix the broken link.

can fix this

I have fixed this and sent a pull request


wrt incorrect Media Plugin picture orientation

Hi Mr James,
is there any easy way to rotate the image after selecting it from the gallery (with the Media Plugin)?

Not currently, you would have to write some code to do this natively.


Project refactoring broke future gradle support

Hello everyone,
I took a look into Gradle support with https://github.com/netfalo/gradle-raml-plugin as a working base.
In v1 the springmvc-raml-plugin had a structure that allowed only to include the required parts as a dependency to the gradle plugin, whereas for v2 there is only the maven plugin as artifact.
Additionally due to renamings the code is not quite portable.
In summary the refactoring of V2 as in the current state of the project architecturally breaks gradle support for the near future, as

the generation code is in the Maven Mojo and is tightly coupled to that
the plugin jar is tightly coupled to the Maven infrastructure
the plugin has a direct dependency on maven an lots of other classes
there does not seem to be an easy way to use other "drivers", such as a command line interface, instead of Maven

I understand that this is still work in progress (as in https://github.com/phoenixnap/springmvc-raml-plugin/projects/1), so maybe we can adjust the whole thing a little?
I would like to suggest something along the lines of

springmvc-raml as a technology platform for RAML <-> code, RAML validation and Documentation generation
springmvc-raml-plugin as the maven plugin that drives the platform (and does nothing more)
springmvc-raml-gradle as the gradle equivalent that also drives the very same platform

Figuratively speaking springmvc-raml would be the car and there are different kinds of drivers (such as Maven, Gradle, Ant(?!), Integration tests or a simple console application).
Otherwise I think the Maven Plugin is great and stands for itself, so thanks a lot for all the time and effort! :)

Hi,
Thanks for reaching us.
Gradle support would be great addition to this project.
IIRC, the main problem with 2.0 is that is distributed as single jar tightly coupled with maven.
So splitting project in two modules where one contains main parsing logic without being dependent on maven would help.
Is that correct?

Basically, yes. There is a lot of code thats currently in the Maven Mojo itself which could be refactored into a common foundation.

I will start refactoring master branch as soon as I find some time.

I would help porting the plugin's code to the RAML Plugin 2.0 "core" and add the RAML to Code path.

Yes please. RAML to Code path is the only one supported in 2.0 and will probably stay like that.

Relates to #65

Do you think it is possible to allow customized code generation? So that I can e.g. generate Interfaces without feign annotations etc.?
Also it would be great to apply the plugin repeatedly with a set of generation rules (Models, Controllers, Clients) :)

I spent a few hours trying to split apart the Maven stuff from the generation stuff, here is what I found so far:

A root project that contains a core and a maven module
There are dependencies to utility methods of the spring framework everywhere (StrinUtils.hasText() etc.)
Config is a kind of global object that is used almost everywhere. Because the properties in Config are static, there are some indirect immediate dependencies with classes that are mostly unrelated.

Configuration and Naming is tightly coupled, naming is directly built-in the generation code, so Configuration and code generation are closer than they have to be
There is a lot of "if-elseif-elseif-else"-code, which makes it kind of hard to read
The Mojo Code itself is Spaghetti
Can we use somthing like https://google.github.io/dagger/ for dependency injection?

Not that I meant this as a "everything is bad" thing, there has been a lot of great work by many people which is really amazing! I just wanted to point out that it won't be an easy thing to do

I updated my fork as requested :)


Can't start on Windows 7 SP1

Welp, idk what happened.
Specs

OS: Windows 7 (With SP1)
IPFS Desktop Version: 0.10.2
go-ipfs Version: 0.4.22

Error
2020-01-09T19:30:43.724Z error: [ipfsd] start daemon Error: multiaddr "                       " must start with a "/"

Windows 7 is no longer supported by Microsoft so it's not weird for me that some errors start to pop up on older Windows versions. So, as a part-time Windows user, this has never happened to me.
Is there any more context on when the error happened? Or anything else of the logs?

I actually started using Windows 10.

This just happened to me on Windows 10. Well, actually it didn't just start happening now, I see in the error logs that it's been happening for three months.
error.log

Update: Delete the folder .ipfs
This will lose access to your original files stored on your peer
In fact, Your peer will be reset.


fix compiler warning; update readme.md

Hi @danielli90, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Daniel Li (BING)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Add RBD CSI migration section to the storage volumes guide

Kubernetes adds the RBD CSI migration functionality via CSI
migration translation lib.
Ref# https://github.com/kubernetes/kubernetes/pull/95361
This commit add the migration details to volumes.md and
feature-gates.md
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

Cc @Jiawei0227 @msau42

/lgtm

/milestone v1.23

/lgtm cancel

@humblec This doc PR should be submitted to dev-1.23 branch, not main.

@humblec This doc PR should be submitted to dev-1.23 branch, not main.

sure. sorry.. let me resend.

@humblec This doc PR should be submitted to dev-1.23 branch, not main.

sure. sorry.. let me resend.

@xing-yang https://github.com/kubernetes/website/pull/30533 covers it for dev-1.23.

closing this one.


make server variable public

The use case:
I have have a multiple instance of atreugo in single application.  They have kind of dependency between each other.
I like to shutdown both instances gracefully  using context with timeout in certain order. The only way to achieve this is to implement a custom graceful stop. To do that i need a direct access to fasthttp instance in  atreugo  structure or  expose fasthttp shutdown function

Pull Request Test Coverage Report for Build 472

0 of 6 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.9%) to 99.14%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

atreugo.go
0
6
0.0%

Totals

Change from base Build 470:
-0.9%

Covered Lines:
692

Relevant Lines:
698

💛  - Coveralls


Race Condition occurs in SDWebImagePrefetcher.m at startPrefetchingAtIndex

New Issue Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
iOS

Platform Version
10.1.0

SDWebImage Version
3.8.1

Integration Method
cocoapods

Xcode Version
Xcode 8.0

Repro rate
sometimes

Repro with our demo prj
no

Calling SDWebImagePrefetcher.shared().prefetchURLs(prefetchUrls) with this code produces the race condition/crash:
let dispatchQueue = DispatchQueue.global(qos: DispatchQoS.QoSClass.default)
// test the dispatch async bug with race conditions and array index out of bounds
for i in (0 ... 40).reversed() {
let prefetchUrls = [URL](repeating: URL%28string:)!, count: i)
dispatchQueue.async {
SDWebImagePrefetcher.shared().prefetchURLs(prefetchUrls)
}
}
Issue Description and Steps
When calling SDWebImagePrefetcher.shared().prefetchURLs(prefetchUrls) from a background queue repeatedly, we can see a race condition occur in func startPrefetchingAtIndex. Though the func checks that the index is valid on one line, after that point the array could have been modified, so in the [self.manager downloadImageWithURL:self.prefetchURLs[index]... line, an index out of bounds error can occur.
Crash:
fatal error: Array index out of range
Stack Trace:
Crashed: com.apple.main-thread
0  libswiftCore.dylib             0x1086dddc0 TTSf4s_s_d_d___TFs18_fatalErrorMessageFTVs12StaticStringS_S_Su_T + 40
1  libswiftCore.dylib             0x108732778 TPA__TFFCs40_SwiftNativeNSArrayWithContiguousStorage13objectAtIndexFSiPs9AnyObject_U_FGSRPS0___PS0_ + 134
2  libswiftCore.dylib             0x10873256c TPA__TTRXFo_dGSRPs9AnyObject___dSizoPs9ErrorType__XFo_dGSRPS____iSizoPS0__ + 84
3  libswiftCore.dylib             0x1087346e0 TPA__TTRXFo_dGSRPs9AnyObject___oPS__zoPs9ErrorType__XFo_dGSRPS____iPS__zoPS0__ + 12
4  libswiftCore.dylib             0x1086b4454 _TTSg5Ps9AnyObject____TFCs21_SwiftDeferredNSArray25withUnsafeBufferOfObjectsurfzFzGSRPs9AnyObject__xx + 668
5  libswiftCore.dylib             0x1086b3780 TToFCs40_SwiftNativeNSArrayWithContiguousStorage13objectAtIndexfSiPs9AnyObject + 304
6  SDWebImage                     0x1012dd620 -SDWebImagePrefetcher startPrefetchingAtIndex:
7  libdispatch.dylib              0x184a6d200 _dispatch_call_block_and_release + 24
8  libdispatch.dylib              0x184a6d1c0 _dispatch_client_callout + 16
9  libdispatch.dylib              0x184a71d6c _dispatch_main_queue_callback_4CF + 1000
10 CoreFoundation                 0x185b8ff2c CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 12
11 CoreFoundation                 0x185b8db18 __CFRunLoopRun + 1660
12 CoreFoundation                 0x185abc048 CFRunLoopRunSpecific + 444
13 GraphicsServices               0x187542198 GSEventRunModal + 180
14 UIKit                          0x18baa72fc -[UIApplication _run] + 684
15 UIKit                          0x18baa2034 UIApplicationMain + 208
16 LinkedIn                       0x1000c9628 main (AppDelegate.swift:27)
17 libdispatch.dylib              0x184aa05b8 (Missing)
Solution:
In the following function:

(void)prefetchURLs:(nullable NSArray<NSURL *> *)urls
progress:(nullable SDWebImagePrefetcherProgressBlock)progressBlock
completed:(nullable SDWebImagePrefetcherCompletionBlock)completionBlock {

simply wrap the entire function body in
dispatch_async(self.prefetcherQueue, ^{
// code
});

This should be fixed in version 4.0.0.


[CSV parsing] Empty columns support.

This commit support empty column from csv parsing.
Signed-off-by: Dmitrii Makarenko<EMAIL_ADDRESS>

What happens if the schema is explicitly not null, e.g.:
create table t (x int not null, y int, z int);

and then import your test CSV file.

What happens if the schema is explicitly not null, e.g.:
create table t (x int not null, y int, z int);

and then import your test CSV file.

I'm not sure we really check for NULL values when importing into a non-nullable column. Worth testing.

What happens if the schema is explicitly not null, e.g.:
create table t (x int not null, y int, z int);

and then import your test CSV file.

Added check, that should cover this case, also test "ImportCsv_KnownSchema_NullsColumn_NullableTypeHeader" describes similar scenario.

PR looks good to go! You might want to rebase it first, CI should be green if rebased on the current main branch.

Hm, looks like there was Null on non-nullable type.
[  FAILED  ] Select.GroupEmptyBlank
C++ exception with description "Null values used in non-nullable type: DICT32(TEXT[NN])[16777272]" thrown in the test body

Hm, looks like there was Null on non-nullable type.

That's probably a sign to leave the null-check part for another PR. I don't think that in this test we actually have imported NULL value. The test is for an empty string and the reference value has no NULLs. Also, changing the type to allow NULLS in the test table causes the test to fail. So, in this case, NULL is probably interpreted as an empty string on import/execution/conversion.

@alexbaden PTAL your notice (verification for nulls depending on schema) not covered fully. String conversion to null looks a bit difficult to support in current PR. Should we crate an issue with this and remove this WA in further PR? Or is current WA fine?


remove messagebuilder, combine functionality into MessageOptions instead

tested, see #off-topic. closes #222