Quoting message in fido meeting quotes the wrong text

Example: I read message 405 and then I read message 406 and I decide I want to comment on message 405. So I start to write a comment and quote the original message (405), but this leads to NiKom actually quoting the last read message (406):
Ärende: Grandstream VOIP
All,
Wondering if anybody here has any experience with Grandstream VOIP's? I have a
2-port HT702 I got from E Bay, trying to figure out how to get it connected to
my modem (for dial-up for my BBS). I figured out/configured SEXPOTS, and my
modem in linux, now I have to figure out how to connect the modem to the
VOIP...
Thanks
Regards,
KrUpTiOn
--- SBBSecho 3.04-Linux

Origin: thenewfrontier2.hopto.org:2333 (Akron, OH) (21:2/105.1)

(Slut på text 405 av KrUpTiOn)
(Läsa) nästa text -->
Text 406  Möte: FSX BBS (FSXNet)    30 Nov 18  20:49:48
Skriven av apam (21:1/125.0)
Till: Avon
Ärende: Sprocket Mud continues :)
A> On 11/30/18, apam pondered and said...
A>
A>  ap> Slowly coming together..
A>
A> Glad you're having fun, sorry I have not been offering much feedback,
A> just been busy at work and seemingly limited time to play on BBS
A> stuff at the moment. I'm heading away for a few days also so...
A> yeh... meh... :(
It's ok.
--- MagickaBBS v0.12alpha (Linux/x86_64)

Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)

(Slut på text 406 av apam)
(Läsa) nästa text --> ko 405
Möte: FSX BBS (FSXNet)    30 Nov 18  12:47:08
Skriven av Joacim Melin (21:2/130.0)
Till: KrUpTiOn
Ärende: Re: Grandstream VOIP
1: !cit
12:  a> --- MagickaBBS v0.12alpha (Linux/x86_64
13: !läs
1:  A>> On 11/30/18, apam pondered and said...
2:  A>>
3:  A>>  ap> Slowly coming together..
4:  A>>
5:  A>> Glad you're having fun, sorry I have not been offering much feedback,
6:  A>> just been busy at work and seemingly limited time to play on BBS
7:  A>> stuff at the moment. I'm heading away for a few days also so...
8:  A>> yeh... meh... :(
9:
10:  a> It's ok.
11:
12:  a> --- MagickaBBS v0.12alpha (Linux/x86_64
13:

ahem it's been close to a year since this was reported.  :D


QPS continue reduce when running TPCC

Bug Report

QPS continue to reduce when running TPCC

What version of TiKV are you using?

master
What operating system and CPU are you using?

Linux/x86_64
Steps to reproduce

Running TPCC.
Wait for about a few hours. Then the QPS drops much
What did you expect?
The QPS should still be high
What did happened?
QPS drops about 5k in 2 hours

@hicqu How about the test result for gc with compaction filter?

The result of GC compaction filter is much better

prepare go-tpc data in compaction branch, and run go-tpc, it is OK
After the binary from  compaction upgrade to master, then run go-tpc, there are some inconsistent

[CUR] PAYMENT - Takes(s): 10.0, Count: 2117, TPM: 12717.5, Sum(ms): 28354, Avg(ms): 13, 95th(ms): 24, 99th(ms): 32, 99.9th(ms): 32
[CUR] STOCK_LEVEL - Takes(s): 9.9, Count: 203, TPM: 1224.4, Sum(ms): 2913, Avg(ms): 14, 95th(ms): 20, 99th(ms): 24, 99.9th(ms): 24
execute run failed, err exec DELETE FROM new_order WHERE (no_w_id, no_d_id, no_o_id) IN (
	(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?)
) failed Error 8021: inconsistent extra index PRIMARY, handle 30082058 not found in table
execute run failed, err exec DELETE FROM new_order WHERE (no_w_id, no_d_id, no_o_id) IN (
	(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?),(?,?,?)
) failed Error 8021: inconsistent extra index PRIMARY, handle 30082058 not found in table
Finished


chore: Upgrade to golang 1.22, Replace sprig with sprout, and other updates and fixes plus plank upgrade to fix deletes

coverage: 41.534% (-13.0%) from 54.581%
when pulling 54503f21d3fabe80b2b8af628a4baf8642be0fa7 on UpgradesAndFixes
into d0dc889db2c6ec8cff011b67d2859940d3a8dba8 on master.

coverage: 41.534% (-13.0%) from 54.581%
when pulling caac80b46a4d74d6431aa690e318f1da5fb8de45 on UpgradesAndFixes
into d0dc889db2c6ec8cff011b67d2859940d3a8dba8 on master.


question about FT

Nice work. But I have a question about FT.
The FT in Table 3 means FT or MFT (multi-task fine-tuning)?

Hi,
The FT in Table 3 means single-task fine-tuning.


Feature Request: File Format - Feedback and Dynamic Variable

Hi,
Is it possible to implement the following features:
ACTION
Setting the File Format is already implemented for in the module.
configuration: file format: {File format}↵
FEEDBACK
The "configuration" command may be used to query the current configuration of the deck:
configuration↵
The server returns the configuration of the deck:
211 configuration:↵
file format: {File format}↵
↵
All HyperDeck models currently support the following file formats:
QuickTimeUncompressed
QuickTimeProResHQ
QuickTimeProRes
QuickTimeProResLT
QuickTimeProResProxy
QuickTimeDNxHD220
DNxHD220
HyperDeck Studio Mini and HyperDeck Studio 12G additionally support the following file formats:
QuickTimeDNxHR_HQX
DNxHR_HQX
HyperDeck Studio Mini also supports the following file formats:
H.264Low
H.264Medium
H.264High
QuickTimeDNxHD45
DNxHD45
QuickTimeDNxHD145
DNxHD145
QuickTimeDNxHR_SQ
DNxHR_SQ
QuicktimeDNxHR_LB
DNxHR_LB
Supported file formats may

This will require an update to the hyperdeck-connection module to support notification of configuration changes.
nrkno/tv-automation-hyperdeck-connection#13

Perhaps I misunderstand. There is already a variable 'hyperdeck:fileFormat' and with 'internal: variable: check: value' one can set feedback. Also with boolean expression. The strings used by COmpanion are "text box friendly" with inserted blanks for example. You can use function replaceAll to replace one string for another (in an expression).
So this request can be closed?!

Hi!
Missing the FileFormat "h264/5 SDI" wich is supported by the HyperDeck Studio 4K Pro.
Is it possible to implement it, please?


Pass.ts does not include view in get descriptor so we're unable to render to texture

When generating the descriptor object, the Pass class does not check whether there is a view attribute in the Attachment objects (around line 19 of Pass.ts).
Because of this current view is always used by Context.ts (line 115) which makes the framework unable to render stuff directly to a texture.

I was able to workaround this by using the WebGPU API directly to create a render pass:

But I am still getting an error:

which I spent too many hours debugging. I looked into fragment targets in renderpipeline and made sure they are the same format than the textures being created for the output. I also have been mostly comparing the code with the deferred rendering code here.
Another issue I found is that it looks like the output texture has to be included in a bindgrouplayout, but the shader sets the type of the output texture as vec4 and not texture2d. Which I believe might be another issue for us given we create the variable definitions based on the BindGroupLayout information.
All this to say that maybe a simple example demonstrating rendering to a texture might go a long way in making the framework more robust for these use-cases.

I have revamped the Attachment object so you're able to pass an object with the new options op/view/resolveTarget as second argument after the value, and updated the Pass getter: new Attachment({ r: 0.07, g: 0.07, b: 0.07, a: 1 }, { view: yourView })

All this to say that maybe a simple example demonstrating rendering to a texture might go a long way in making the framework more robust for these use-cases.

Agreed, the examples are few for now as my availability is limited but a RTT example could help for deferred and post processing.

Added a RTT example which renders a cube (with uv texture) to a texture and use it as another pass' cube texture : https://dmnsgn.github.io/dgel/?id=render-to-texture
To sum up:

the format of the RTT texture here is "rgba32float"

it is unfilterable so the BindGroupLayout needs an entries with sampleType defined as texture: { sampleType: "unfilterable-float" },
the pipeline of the command rendering to a RTT pass needs to set its fragmentTargets with this format
the pipeline program entrypoint "main" return value is defined by pipeline.fragmentOuts so that's where you map the targets (here just a f32 color, but can be any gbuffer you want with maximum <= 8)

the rttTexture needs to have RENDER_ATTACHMENT and TEXTURE_BINDING usages
the rttCommand pass needs a view created from this texture with the same format
the drawGeometryCommand needs this view as a resource in one of its BindGroup

Most of the code here:
https://github.com/dmnsgn/dgel/blob/f78974b155d617460006acb669827913f3ebbb32/examples/render-to-texture.js#L261-L285
Quirks:

uv.y needs to be flipped in textureLoad
everything is triggered on resize as it doesn't look like you can reset a texture size without recreating it
the process feels a bit inelegant but I assume that might be the job of a higher abstraction in the future

Thank you!


it only wanna create horizontal elements

Can not get it to make rectangular elements of any kind for a menu  or for a grid or an image carousel where they are vertical so they are taller then they are wide. I tried with every combinations of synonyms and metaphors i could think of but it keep making them horizontal.

Can you share a link to a session on the hosted service?


Add compact-ids to WebGPU->Vulkan transform

This currently exists in the Vulkan->WebGPU, to work around an issue in SPIRV-Cross but because ids being compact isn't in the spec, the validator will not reject sparse ids, so the WebGPU->Vulkan also needs it, so that spvc can make sure ids are compact before invoking SPIRV-Cross.

Apparently I had never actually added it to either pass, so I guess my PR will do both.


shows correct app name + adds API to set time text in banner

makes reference to issue
https://github.com/pikacode/EBForeNotification/issues/11
and
https://github.com/pikacode/EBForeNotification/issues/7

@tiagomartinho
thank you so much ：）
I will treat you for dinner if u come to China 😬


IIS 8.5 binding with "DS Mapper usage" disabled under Client Cert Auth Scenario

I am using win-acme (v2.1.10) locally on a Windows 2012 R2 (IIS 8.5)/Exchange 2013 server to obtain/renew a certificate used for client access (activesync, owa, etc.).
The problem is that when the cert gets renewed and installed by the scheduled task, it does so with the flag "DS Mapper usage" set to disabled. This would be of no consequence (and is the correct setting) for most scenarios, but I have client certificate authentication set up on our activesync devices, and without DS Mapper usage enabled they will fail to authenticate. Once I manually delete and then re-create the binding using the following commands, all is well:
netsh http delete sslcert ipport=<IP_ADDRESS>:443
netsh http add sslcert ipport=<IP_ADDRESS>:443 certhash=[thumbprint of LE cert] appid={4dc3e181-e14b-4a21-b022-59fc669b0914} certstorename=My dsmapperusage=enable
Also, it seems that maybe there is a difference in behavior when binding a cert using IIS Manager, as stated by this post.
I am not sure if there is anything win-acme itself can do differently when establishing the binding to allow DS Mapper usage to be enabled from the get-go. The value itself is stored in the registry, but if manipulated directly the server must be rebooted for the change to take effect.
So if there is not a way for Win-acme to create the binding with DS Mapper usage enabled, I wonder what method I could use to enable it immediately after the binding is created each time the LE cert is renewed. This blog post describes a couple of methods (scroll down to the section "Activating the Client Certificate Mapping through code and script").
I would much appreciate any suggestions you have on how best to address this issue so I don't have to manually remember to re-create the binding every couple of months.

I think the easiest way to achieve this would be include those two commands in your installation script. I.e. don't use the example script literally but place your own copy somewhere and add these lines after its done updating Exchange.

Apologies I'm just now getting back to this. So to implement what you've suggested, is this the proper course of action?

Make a copy of C:\Program Files\Lets Encrypt\Scripts\ImportExchange.ps1, rename the copy to, say "ImportExchangeWithCertAuth.ps1"

Edit ImportExchangeWithCertAuth.ps1 to include these lines, perhaps directly after line 166 Import-ExchangeCertificate @importExchangeCertificateParameters -ErrorAction Stop | Out-Null")

netsh http delete sslcert ipport=<IP_ADDRESS>:443
netsh http add sslcert ipport=<IP_ADDRESS>:443 certhash= $NewCertThumbprint appid={4dc3e181-e14b-4a21-b022-59fc669b0914} certstorename=My dsmapperusage=enable

Modify the .renewal.json file in C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org to change the line Script": "./Scripts/ImportExchange.ps1", to Script": "./Scripts/ImportExchangeWithCertAuth.ps1",

Hi @bookemdano08, I believe that should do the trick. Thanks for posting this step by step for future googlers 😄

Thanks @WouterTinus. I've got one correction to make: due to the difference in parsing between cmd and Powershell, the AppID in the netsh http add sslcert command needs single quotes on either side of the braces. Otherwise you'll get a "Parameter is incorrect" error. Thanks to this stackoverflow post for the answer to that. So the proper command for the script is:
netsh http add sslcert ipport=<IP_ADDRESS>:443 certhash=$NewCertThumbprint appid='{4dc3e181-e14b-4a21-b022-59fc669b0914}' certstorename=My dsmapperusage=enable
I haven't actually tested this yet in the context of the renewal script--my current cert won't renew until early May. I'll report back here once that happens.


feat: Graphite: Adding some of the core Grpahite workflows from the Graphite cheatsheet website: https://graphite.dev/docs/command-reference

https://graphite.dev/docs/command-reference
Discord username (optional) please include so we can attribute you with our Contributor role (like so elvis#4747)
Description of changes (updated or new workflows)

Current dependencies on/for this PR:

main

PR #140   👈

This comment was auto-generated by Graphite.


⚠ Bofrost.at has degraded performance

In 9a0e6c0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1505 ms

Resolved: Bofrost.at performance has improved in 1df3038.


Easily ignore ibc messages

For mesh security testing, I want to be able to run the code that sends IBC packets without it failing. Maybe lost functionality, but not having existing functions panic.
I was going to add this to the code, then found we had this in test code, so I exposed it and added some docs on how to enable it. I'd love to get this in 0.16.5 so we can add ibc functionality to mesh-security without breaking the existing test suite (and just focus the new test suite on the ibc stuff)

Huh, cargo clippy --tests and cargo clippy --all-targets both pass for me locally. (Rust 1.69)
And when I make the recommend changes, cargo test fails:
   --> src/staking.rs:493:39
    |
493 |             .filter(|ub| ub.validator == validator)
    |                                       ^^ no implementation for `cosmwasm_std::Addr == &cosmwasm_std::Addr`
    |
    = help: the trait `PartialEq<&cosmwasm_std::Addr>` is not implemented for `cosmwasm_std::Addr`
    = help: the following other types implement trait `PartialEq<Rhs>`:
              <cosmwasm_std::Addr as PartialEq<&str>>
              <cosmwasm_std::Addr as PartialEq<std::string::String>>
              <cosmwasm_std::Addr as PartialEq>

.filter(|ub| ub.validator == validator)

.filter(|ub| ub.validator == *validator)
?

Okay CI va local. What is up:
CI:
#!/bin/bash -eo pipefail
rustc --version; cargo --version; rustup --version; rustup target list --installed
rustc 1.65.0 (897e37553 2022-11-02)
cargo 1.65.0 (4bc8f24d3 2022-10-20)
rustup 1.25.1 (bb60b1e89 2022-07-12)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.65.0 (897e37553 2022-11-02)`
x86_64-unknown-linux-gnu
CircleCI received exit code 0

Local:
rustc +1.65.0 --version; cargo +1.65.0 --version; rustup --version; rustup target list --installed

rustc 1.65.0 (897e37553 2022-11-02)
cargo 1.65.0 (4bc8f24d3 2022-10-20)
rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.69.0 (84c898d65 2023-04-16)`
aarch64-apple-darwin
wasm32-unknown-unknown

CI:
#!/bin/bash -eo pipefail
cargo clippy --all-targets -- -D warnings
....
    Checking cw-multi-test v0.16.4 (/root/project)
error: : needlessly taken reference of left operand
   --> src/staking.rs:493:26
    |
493 |             .filter(|ub| &ub.validator == validator)
    |                          -------------^^^^^^^^^^^^^
    |                          |
    |                          help: use the left value directly: `ub.validator`
    |
    = note: `-D clippy::op-ref` implied by `-D warnings`
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#op_ref

Local:
cargo +1.65.0 clippy --all-targets -- -D warnings
...
    Checking cw-multi-test v0.16.4 (/Users/ethanfrey/rust/cw-multi-test)
    Finished dev [unoptimized + debuginfo] target(s) in 15.41s

Do you want to debug the CI issue more?
Or should I just put some #[allow(...)] block to stop this spurious warning?

 Seemed like there was nothing to change in the code (as the change broke compiling under multiple Rust versions)


Make placeholders smoother

Hey there,
when using your plugin "as-is", I get this:

From the banner image, I was under the impression to get softer gradients and overall smoother images, is there a way to "improve" the output quality by tweaking parameters? Or is it my images (strong light/shadow transitions etc)
Thanks!

// Edit:
For PNG files with transparency, I get this:

Hello there!
You can try to improve the pixel target to generate bigger thumbnails (although not recommended), which are embedded into the blurry SVG placeholder. The implementation mocks the one from Google's former AMP project. I'm not sure what you expected.
Regarding transparent images, there is the transparent option for both $file->placeholder() and $file->placeholderUri() field methods. It will omit the artifacts of transparent images.
There is also a different implementation for blurry images using the blurhash algorithm by @tobimori. You can check it out as well: kirby-blurhash

You can customize the blur by adjusting the stdDeviation in https://github.com/johannschopplich/kirby-blurry-placeholder/blob/main/BlurryPlaceholder.php#L54

@tobimori Great input! 👏

Thanks you guys! Seems even @johannschopplich learned something 😅 (just kidding)

Absolutely! The younger generation builds upon what the older one has created and teaches a lesson or two. Circle of life. 🙃
The Gaussian blur parameter could be a plugin option. 👀

Not sure about who's the younger generation here 🤣
That's what I ended up with (note the blur in the beginning, the bw-color effect applies to all images, see the end of the clip, when scrolling up again)
https://user-images.githubusercontent.com/122524301/227766297-d3019370-f559-4a0e-b83e-869a7875888c.mov

The filesize savings are quite decent, and in accordance with the bw effect, with placeholders being generated as bw, this shaves some additional kb 😉

Absolutely! The younger generation builds upon what the older one has created and teaches a lesson or two. Circle of life. 🙃
The Gaussian blur parameter could be a plugin option. 👀

TOTALLY!


Code and data for LID model

Hi, my question is around Language Identification (LID) part of NLLB and was wondering if the code and data used to train the LID model are part of this codebase? My goal is to first reproduce the results from the paper and then later train on my own data. Any help would be much appreciated. Thanks.

hi skomban,
we don't plan to publish the data we used for training the LID model. Regarding the training code, we used regular fastText supervised training. There is no plan to open-source the preprocessing steps, but you can refer to the section 5.1.3 of our paper: "Filtering Training Data". Script detection used here corresponds to this open-sourced code.
Regards,
Onur

Hi Onur, thank you for your prompt response. One further question, any plans on open sourcing the LID Inspection Interface? If not, could you give me some pointers on how I could do it myself. Right now if I understand correctly the fastText api does not support querying the ngram weights, right? Thanks.

Hi @Celebio,
Thank you for your prompt response. One further question, any plans on open sourcing the LID Inspection Interface? If not, could you give me some pointers on how I could do it myself. Right now if I understand correctly the fastText api does not support querying the ngram weights, right?
Thanks,
Stanley

Hi @Celebio,
Thank you again for your prompt reply and for all the clarifications. The explain method would certainly be useful particularly for debugging. Fingers crossed that it soon becomes part of the fastText api.
Thanks,
Stanley


2.4 - Update MCH Sample to remove Imagepullsecret

Signed-off-by: Zachary Kayyali<EMAIL_ADDRESS>https://github.com/open-cluster-management/backlog/issues/17919

/hold

/unhold


Remove the deprecated short name from README

Proposed Changes

By https://github.com/knative/serving-operator/pull/250, short name ks for the Knative Serving Operator CRD was removed from code. This PR is removing remaining ks in README.

Release Note

Remove the deprecated short name from README.

/check-cla

/retest

/check-cla

This was my first PR to google opensource so I signed CLA just before writing this comment.

/ok-to-test

/retest

Thank @q0115643 for the contribute!
/lgtm
/approve

@houshengbo sorry for the inconvenience, my profile in the commit was a bit messed up so I force-pushed a new commit with same change.

/lgtm


Problems with TicTacToe tutorial

Hey folks
I´ve found your boardgame.io project and I think that it's very interesting. I've decided to give it a try so I began for the TicTacToe tutorial. My aim is to perform the full process of the app building with React until deploy de app in Heroku. In this way, I can test and understand your project and finally, check if it cover my needs. In this process I've found several issues:

I began with this tutorial: https://boardgame.io/documentation/#/tutorial and I've found some problems that I fixed analysing the code in the examples folder: https://github.com/nicolodavis/boardgame.io/tree/master/examples/react-web/src/tic-tac-toe. But the two sources are different versions that I think that it should be the same.
The tutorial, in the multiplayer description makes a "jump" in which the code is split in the game and board files and this step is not explained. I suppose that fluent React developers can make this transformation easily, but people that are not familiarized with this platform, as me, find this step difficult. When I put together all the code, the multiplayer system Local Master works in my computer, but the Remote Master system not.
As Local Master failed to me, I realized that the tutorial has the following link to a working example of the system: https://codesandbox.io/s/boardgameio-fsl8y. I downloaded it and it worked perfectly. This version is also different to the tutorial and the example TicTacToe codes.
I've build a github repo and connect it to a heroku account to perform the deploy. After the deployment process, in Mozilla I was the following error when I choose a player:
 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8000/socket.io/?EIO=3&transport=polling&t=N42v9Ah. (Reason: CORS request did not succeed)
Searching in google, I've changed:
multiplayer: SocketIO({ server: "localhost:8000" })
to
multiplayer: SocketIO({ server: "https://boardgameparty.herokuapp.com/:8000" })
But now, Mozilla don´t show any error only the "Connecting..." message but in Chrome appears the following error:
polling-xhr.js:271 POST https://boardgameparty.herokuapp.com/socket.io/?EIO=3&transport=polling&t=N43J2-R 404 (Not Found)

Currently, I don't know how to fix this problem. I think that an update of the tutorial covering from the app building until the deployment process in a server (not necessarily in heroku ) would be very interesting.
Thank you in advance
Pedro Seoane

This is great feedback.   Thank you!
Yes, I think the CodeSandbox link sometimes falls out of sync with the tutorial code.  We'll have to come up with a better process for this.  I think I might consider having CodeSandbox pull from the Git repo directly and making sure that the tutorial uses the same code.
About deployment, that is on the radar.  You should see a guide on how to deploy it on various options prior to our v1 launch.

Closing this as I think this has mostly now been addressed. The tutorial was rewritten in #714, addressing the “jump” described in 2 above, and I think resolving 1 too. A Heroku deployment guide has also since been added to the docs. Thanks for the helpful feedback!


Twig Emmet Issues when Classes have hyphens and numbers

VSCode Version: Code 1.15.0 (8b95971d8cccd3afd86b35d4a0e098c189294ff2, 2017-08-09T20:06:21.685Z)
OS Version: Darwin x64 16.7.0

Extension
Author (truncated)
Version

sublime-keybindings
ms-
2.9.1

twig
wha
1.0.2

vscode-twig-pack
baj
1.0.0

Steps to Reproduce:

I have twig configured with emmet by added "twig": "html" to emmet.syntaxProfiles and emmet.includeLanguages so emmet as a whole works okay.
From an HTML twig template when I execute something like .row>.col-md emmet will respond just fine. If however I do .row>.col-md-5 emmet doesn't respond at all.

Issues still happen when vscode-twig-pack is deactivated which leads me to think it's associated with the built in extension.

@timknight I am not very familiar with twig.
Can you share a self contained example that I can try?

Hi Ramya, no problem at all. Just know that for the most part Twig is basically just HTML. The only thing that changes is where dynamic output happens. It would probably help too to have the Twig extension installed just for syntax coloring.
Then to get started, you can use the base Emmet ! template on a page that's defined as HTML (Twig):
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <meta http-equiv="X-UA-Compatible" content="ie=edge">
  <title>Document</title>
</head>
<body>

</body>
</html>

Within the body just starting:
.container>.row>.col-md-5
You'll notice that all the way through typing md you'll see Emmet still respond. Until you type -5 and nothing will happen. If you take the same exact template and change the language mode to HTML it will behave correctly. I thought it might be the whatwedo twig extension at first, but it looks like all that extension does is define a language template for syntax coloring for the twig language. Aside from adding the emmet.syntaxProfiles and mmet.includeLanguages options I mentioned in my OP that's all the special configuration I've done.
I hope that counts as a self-contained example, but let me know if I can provide something better to help you test what I'm seeing.

Though I should note executing "Emmet: Expand Abbreviation" manually will work. It just seems odd to me that the same class would stop detecting for tab abbreviation between HTML and HTML (Twig).

Thanks for the clarification. I was able to repro.
So what is happening is that running the command Emmet: Expand Abbreviation works.
Triggering suggestions manually (via Ctrl+Space) works.
But suggestions stop showing the emmet abbreviation as soon as you type the number
The quick suggestions feature (suggestions showing up as you type) is triggered when you type anything that matches the word pattern as defined for the language.
In case of html, the word pattern is defined to include numbers. See https://github.com/Microsoft/vscode/blob/master/extensions/html/client/src/htmlMain.ts#L85
In case of twig, no word pattern is registered in the extension that provides the twig support. So VS Code falls back to the default word pattern it uses which doesn't include numbers.
I'd suggest to create an issue in the whatwedo extension to include a word pattern for twig. Since it is basically html, you can copy the one from https://github.com/Microsoft/vscode/blob/master/extensions/html/client/src/htmlMain.ts#L85
Until then, hit Ctrl+Space whenever you feel there should have been an emmet suggestion, but its not.
Makes sense?

Ah yes okay that makes sense. Looks like it would probably have to go within the language-configuration.json, but I'll have to do some research to see how that actually works and how to properly escape the regex. I figured, I might as well try to address it and send a pull request for them. Thank you so much for clarification on this!

No problem, Happy Coding!

@ramya-rao-a, this might be a little out of scope for our question I'm just hoping you can tell me if I'm on the right track or let me know if there's a way to test that it's reading the wordPattern. I have a fork of this project at https://github.com/timknight/vscode-twig. I've included a JS file that it's referenced in the package.json and the script is just a basic setLanguageConfiguration to set the wordPattern. Nothing errors for me, but I still don't get a fix to the problem. Is there more I need to do to define the wordPattern to correct the issue?

Since a couple of months, you dont need to add the wordPattern via code. You can add it in the language-configuration.json file directly. Have you tried that?

I considered that first, from what I read it would be doing something like this...
{
  "wordPattern": {
    "pattern": "..."
  },
  "comments": {
    "blockComment": [ "{#", "#}" ]
  },
  "brackets": [
    ["{", "}"],
    ["[", "]"],
    ["(", ")"]
  ]
}

Or it could be just a string right off of "wordPattern" right? Where I struggled however was properly escaping the Regex in question into a string in the JSON file. So I jumped into the .js file option instead. Open to thoughts on how to best approach that within the language-configuration.json though.

Its supposed to be just "wordPattern": "...." in the twig.configuration.json file in that repo
Below is the escaped version of the word pattern for html. I placed it in the twig.configuration.json file, and I can get emmet suggestions on the last -5 now.
"wordPattern": "/(-?\\d*\\.\\d\\w*)|([^\\\~\!\@\$\^\&\*\(\)\=\+\[\{\]\}\\|\;\:\'"\,\.\<\>/\s]+)/"`

What you have done works as well, except you need to add another field in the package.json file
You cannot have a main without the activationEvents, else the extension host in VS Code will not know when to activate the extension.
"activationEvents": [
        "onLanguage:twig"
    ]

Thank you so much. This has been incredibly helpful just for me to grasp how all of the various configuration is setup for vscode. Strangely, adding it to twig.configuration.json stops all but ! from working.
{
	"comments": {
		// symbols used for start and end a block comment. Remove this entry if your language does not support block comments
		"blockComment": [ "{#", "#}" ]
	},
	// symbols used as brackets
	"brackets": [
		["{", "}"],
		["[", "]"],
		["(", ")"]
	],
	"wordPattern": "/(-?\\d*\\.\\d\\w*)|([^\\`\\~\\!\\@\\$\\^\\&\\*\\(\\)\\=\\+\\[\\{\\]\\}\\\\|\\;\\:\\'\"\\,\\.\\<\\>\/\\s]+)/"
}

Am I missing something with that?
However adding activationEvents worked great. 🎉

Maybe I missed an escape sequence somewhere when copy pasting :)
Either model (programatic vs declarative) works

Shall we close this issue then?

Absolutely, thank you so much for your time @ramya-rao-a. Way more than I could have expected on this!

Great! Happy Coding!


Restore pull_request_target trigger on coverage check

The  PR add code coverage is here: https://github.com/GoogleCloudPlatform/alloydb-java-connector/pull/17.

It is obsolete since the code it points at was removed.


Cannot use {% url path %} in blog posts

Using {% url path %} in blog posts results in the following error:
*** Error while building
'__CACTUS_SITE__'
Traceback (most recent call last):
...
File "/usr/local/lib/python2.7/dist-packages/Cactus-3.3.2-py2.7.egg/cactus/template_tags.py", line 52, in url
    site = context['__CACTUS_SITE__']
  File "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/context.py", line 56, in __getitem__
    raise KeyError(key)
KeyError: '__CACTUS_SITE__'

Try modifiying the blog.py plugin to add the "page" to the blog post context dictionary.
# Build a context for each post
postContext = {}
postContext['page'] = page

You can then use {% url page.url %} in the templates.

Should be resolved duie to the merge of #229


Exception loop when using new Rails helpers

Hello,
I was testing out a phlex-rails view and ran into an issue where an (expected) exception could cause an infinite loop and peg the ruby process to ~100%. I was wondering if I'm doing something obviously wrong (besides the exception) or if there could be something related to phlex-rails here.
Here's a sample project that reproduces the issue, but it does stop after 17 iterations vs infinite like the original project.
In the stuck process backtrace it looks like the rails wrapped_causes_for is called in an endless loop.
Here's the view that throws the exception. The f.label line throws an ArgumentError, because it needs a name, but then this same exception get rethrown continuously.
Please let me know if I can provide any more detail.
Thanks!
class List < Phlex::HTML
  include Phlex::DeferredRender

  def initialize
    @items = []
  end

  def template
    ul do
      @items.each { render(_1) }
    end
  end

  def with_item(...)
    @items << Item.new(...)
  end

  class Item < Phlex::HTML
    def template(&)
      li(&)
    end
  end
end

module Views
  module Demo
    class Index < Phlex::HTML
      include Phlex::Rails::Helpers::FormWith
      def template
        form_with url: "/" do |f|
          render List.new do |list|
            list.with_item do
              f.label
            end
          end
        end
      end
    end
  end
end

A lot of the same exception:

Backtrace
ArgumentError (wrong number of arguments (given 0, expected 1..3)):

/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/form_helper.rb:2369:in `label'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/buffered.rb:27:in `label'
/Users/ben/Desktop/blog/app/views/demo/index.rb:33:in `block (3 levels) in template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:242:in `yield_content_with_args'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:114:in `rescue in yield_content_with_args'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:102:in `yield_content_with_args'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:79:in `block (2 levels) in __final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:217:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:99:in `rescue in yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:87:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/elements.rb:25:in `li'
/Users/ben/Desktop/blog/app/views/demo/index.rb:20:in `template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:77:in `block in __final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:201:in `around_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:71:in `__final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:57:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:96:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:16:in `render'
/Users/ben/Desktop/blog/app/views/demo/index.rb:10:in `block (2 levels) in template'
/Users/ben/Desktop/blog/app/views/demo/index.rb:10:in `each'
/Users/ben/Desktop/blog/app/views/demo/index.rb:10:in `block in template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:217:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:99:in `rescue in yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:87:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/elements.rb:25:in `ul'
/Users/ben/Desktop/blog/app/views/demo/index.rb:9:in `template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:75:in `block in __final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:201:in `around_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:71:in `__final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:57:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:96:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:16:in `render'
/Users/ben/Desktop/blog/app/views/demo/index.rb:31:in `block in template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/helper_macros.rb:75:in `block (2 levels) in form_with'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:217:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:99:in `rescue in yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:87:in `yield_content'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:162:in `capture'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:80:in `capture'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/helper_macros.rb:74:in `block in form_with'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:45:in `block in capture'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:209:in `with_output_buffer'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/capture_helper.rb:45:in `capture'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/helpers/form_helper.rb:768:in `form_with'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/helper_macros.rb:73:in `form_with'
/Users/ben/Desktop/blog/app/views/demo/index.rb:30:in `template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:86:in `block in __final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:201:in `around_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:71:in `__final_call__'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-1.3.2/lib/phlex/html.rb:57:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/phlex-rails-0.6.1/lib/phlex/rails/html/overrides.rb:52:in `render_in'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/template/renderable.rb:16:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:65:in `block (2 levels) in render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:206:in `block in instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:206:in `instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:60:in `block in render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:79:in `render_with_layout'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:59:in `render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/template_renderer.rb:11:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:61:in `render_template_to_object'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/renderer/renderer.rb:29:in `render_to_object'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:117:in `block in _render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/base.rb:270:in `in_rendering_context'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:116:in `_render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/streaming.rb:216:in `_render_template'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:103:in `render_to_body'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:46:in `render_to_body'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/renderers.rb:141:in `render_to_body'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/rendering.rb:25:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:30:in `render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:22:in `block (2 levels) in render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/3.2.0/benchmark.rb:311:in `realtime'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/core_ext/benchmark.rb:14:in `ms'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:22:in `block in render'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:91:in `cleanup_view_runtime'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:34:in `cleanup_view_runtime'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:21:in `render'
/Users/ben/Desktop/blog/app/controllers/demo_controller.rb:3:in `index'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:215:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rendering.rb:53:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:234:in `block in process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:118:in `block in run_callbacks'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actiontext-<IP_ADDRESS>/lib/action_text/rendering.rb:20:in `with_renderer'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actiontext-<IP_ADDRESS>/lib/action_text/engine.rb:69:in `block (4 levels) in <class:Engine>'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:127:in `instance_exec'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:127:in `block in run_callbacks'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:138:in `run_callbacks'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/callbacks.rb:233:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/rescue.rb:22:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:206:in `block in instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:206:in `instrument'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/instrumentation.rb:66:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/railties/controller_runtime.rb:27:in `process_action'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/abstract_controller/base.rb:151:in `process'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionview-<IP_ADDRESS>/lib/action_view/rendering.rb:39:in `process'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:188:in `dispatch'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_controller/metal.rb:251:in `dispatch'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:32:in `serve'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:50:in `block in serve'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:32:in `each'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/journey/router.rb:32:in `serve'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/routing/route_set.rb:852:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/tempfile_reaper.rb:15:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/etag.rb:27:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/conditional_get.rb:27:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/head.rb:12:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/permissions_policy.rb:38:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/http/content_security_policy.rb:36:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/session/abstract/id.rb:266:in `context'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/session/abstract/id.rb:260:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/cookies.rb:704:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/migration.rb:603:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:99:in `run_callbacks'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/callbacks.rb:26:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:14:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/actionable_exceptions.rb:17:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/web-console-4.2.0/lib/web_console/middleware.rb:132:in `call_app'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/web-console-4.2.0/lib/web_console/middleware.rb:28:in `block in call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/web-console-4.2.0/lib/web_console/middleware.rb:17:in `catch'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/web-console-4.2.0/lib/web_console/middleware.rb:17:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/show_exceptions.rb:26:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:40:in `call_app'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:25:in `block in call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:99:in `block in tagged'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:37:in `tagged'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:99:in `tagged'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/rack/logger.rb:25:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/sprockets-rails-3.4.2/lib/sprockets/rails/quiet_assets.rb:13:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/request_id.rb:26:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/method_override.rb:24:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/runtime.rb:22:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/server_timing.rb:61:in `block in call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/server_timing.rb:26:in `collect_events'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/server_timing.rb:60:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/executor.rb:14:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/static.rb:23:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/rack-<IP_ADDRESS>/lib/rack/sendfile.rb:110:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/actionpack-<IP_ADDRESS>/lib/action_dispatch/middleware/host_authorization.rb:137:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/railties-<IP_ADDRESS>/lib/rails/engine.rb:530:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/configuration.rb:252:in `call'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/request.rb:77:in `block in handle_request'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/thread_pool.rb:340:in `with_force_shutdown'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/request.rb:76:in `handle_request'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/server.rb:443:in `process_client'
/Users/ben/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/puma-5.6.5/lib/puma/thread_pool.rb:147:in `block in spawn_thread'

Thank you! I’ll look into this as soon as possible.

Yes, that's it. I’ll need to revert #52 and find another way to handle C-level Procs.

@benubois I was able to find a way to avoid calling binding at all.


boost 1.61.0 uuid random_generator doesn't compile with -Werror=pedantic

centos 4.7 and g++ 4.8.5
g++ -std=c++11 -Werror=pedantic
boost-1.61.0/include/boost/uuid/seed_rng.hpp: In member function 'void boost::uuids::detail::seed_rng::sha1_random_digest_()':
/export/home/software/boost-1.61.0/include/boost/uuid/seed_rng.hpp:222:60: error: ISO C++ forbids casting between pointer-to-function and pointer-to-object [-Werror=pedantic]
             sha.process_bytes( (unsigned char const*)&std::rand, sizeof( void(*)() ) );

sorry duplicate.


fix: use generics to allow for transform

🔗 Linked issue
#49
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Introduces two more generics to OpenAPI-typed composables, allowing for use of transform, which previously would create a TypeScript error, because return type of the composable — and therefore transform method — was forced, rather than inferred from options.
This makes transform match its original intent and behaviour from Nuxt, which is to take response data and transform it in some way before exposing as returned data ref.
Resolves #49.
📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

@killjoy1221 Would you mind taking a look at this implementation? Thanks in advance!

@brawaru Thanks a lot for the PR!


Update cats-effect-std to 3.1.1

Updates org.typelevel:cats-effect-std from 3.1.0 to 3.1.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "cats-effect-std" } ]

labels: library-update, semver-patch

Codecov Report

Merging #215 (e9a55f6) into master (dd24653) will decrease coverage by 0.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #215      +/-   ##
==========================================
- Coverage   84.61%   84.16%   -0.46%
==========================================
  Files          35       35
  Lines         221      221
  Branches       10       10
==========================================
- Hits          187      186       -1
- Misses         34       35       +1

Flag
Coverage Δ

unittests
84.16% <ø> (-0.46%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

core/src/main/scala/io/fmq/poll/Poller.scala
86.20% <0.00%> (-1.73%)
:arrow_down:

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 dd24653...e9a55f6. Read the comment docs.


Vanilla install will not build

A complete new app with typescript fails to build with error:

ERROR in ../src/router/index.ts(25,11):
TS2591: Cannot find name 'process'. Do you need to install type definitions for node? Try npm i @types/node and then add node to the types field in your tsconfig.

Using yarn: 1.21.1
node: v10.17.0
quasar: 1.4.3
@quasar/quasar-app-extension-typescript: ^1.0.0-beta.2
I created a fresh app with 'quasar create', accepted the default prompts and added ESLint, Vuex, Axios, IE11.
cd into the project directory and run quasar ext add @quasar/typescript and press enter to accept all the defaults.
Run 'quasar b' and the build fails.
If I create an app without the 'experimental' convert .js to .ts files then the app builds ok.
Output from 'quasar info':
Operating System - Linux(3.10.0-1062.9.1.el7.x86_64) - linux/x64
NodeJs - 10.17.0
Global packages
NPM - 6.11.3
yarn - 1.21.1
@quasar/cli - 1.0.5
cordova - Not installed
Important local packages
quasar - 1.6.1 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app - 1.4.3 -- Quasar Framework local CLI
@quasar/extras - 1.3.3 -- Quasar Framework fonts, icons and animations
vue - 2.6.11 -- Reactive, component-oriented view layer for modern web interfaces.
vue-router - 3.1.3 -- Official router for Vue.js 2
vuex - 3.1.2 -- state management for Vue.js
electron - Not installed
electron-packager - Not installed
electron-builder - Not installed
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed
@babel/core - 7.7.7 -- Babel compiler core.
webpack - 4.41.3 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
webpack-dev-server - 3.9.0 -- Serves a webpack app. Updates the browser on changes.
workbox-webpack-plugin - 4.3.1 -- A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.
register-service-worker - 1.6.2 -- Script for registering service worker, with hooks
Quasar App Extensions
@quasar/quasar-app-extension-typescript - 1.0.0-beta.2 -- A Quasar CLI Extension

I managed to fix this by adding 'node' to the types array in the tsconfig. The extension is installing the @types/node package but doesn't appear to add it to the tsconfig.
"types": [       "quasar",       "node"     ]

It shouldn't need to do so, given how TS types resolution works

Please try with the new starter kit TypeScript option or with TS config preset
https://quasar.dev/quasar-cli/cli-documentation/supporting-ts#Installation-of-TypeScript-Support
Let us know if you hit the same problem


[Bug] CDCTools job cannot restart from previous checkpoint/savepoint when multiple tables in sync

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
1.4.0
What's Wrong?
CDCTools job cannot restart from previous checkpoint/savepoint when multiple tables in sync.
What You Expected?
The job should be able to use previous checkpoint/savepoint to restart.
How to Reproduce?
To reproduce, sync multiple tables, for example:
--including-tables test|test2|test_clone|test_clone2
The reason is that Flink is a stateful application, and it is recommended by official that each stateful operator should have a unique uid.
I fixed this issue by using table name as the uid of its associated sink operators.
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

What is the specific error that cannot be started?


Add FastAPI project structure with SQLite database, SMTP functionality, and example templates

YOU MAY DELETE THE ENTIRE TEMPLATE BELOW.
How Has This Been Tested?
Please describe if you have either:

Generated the "example" project
Ran the entire benchmark suite
Something else

Please reference our contributing guidelines and explain how this benefits GPT-Engineer.

@topisun, can you please refer to @captivus' comment? We need that clarification to decide how/if to proceed with this PR. Otherwise, I'll close it next week.

Since there was no feedback or comments provided by @topisun - I'm closing this.


Revive cache cleaning

bors r+
🤖

bors r-

bors r+

bors r+

bors r+

@matklad

The idea here is that, on CI, we only want to cache crates.io
dependencies, and not local crates. This keeps the size of the cache
low, and also improves performance, as network and moving files on
disk (on Windows) can be slow.

But the cache is downloaded from the network, isn't it? Btw, I have doubts that caching CARGO_HOME subdirs gives any ci performance wins, because these are the files downloaded by cargo and taking into account that cache is also restored from network there shouldn't be big difference in using it, since either way we use network?

But the cache is downloaded from the network, isn't it?

It's faster to download 100MB of cache than 200MB of cache.

I have doubts that caching CARGO_HOME subdirs gives any ci performance wins, because these are the files downloaded by cargo and taking into account that cache is also restored from network there shouldn't be big difference in using it, since either way we use network?

I think this is roughly correct, but I'd still expect caching to be a win even in this case:

downloading one big thing should be faster than downloading many small things
I expect cache is closer to workers than crates.io

But its worth experimenting here


autocomplete.noConflict

Follow-up of #117 .
We're not the only lib which wants to use autocomplete in the global scope.
We could provide a new noConflict() method as jQuery's $.noConflict() and lodash's _.noConflict().
Usage
<script src="xxx/autocomplete.min.js"></script>
<script>
  window.algoliaAutocomplete = autocomplete.noConflict();
</script>

Implementation
Probably only necessary in the standalone build.
var wasAutocompleteSet = 'autocomplete' in window;
var oldAutocomplete = window.autocomplete;
autocomplete.noConflict = function noConflict() {
  if (wasAutocompleteSet) {
    window.autocomplete = oldAutocomplete;
  } else {
    delete window.autocomplete;
  }
  return autocomplete;
}

module.exports = autocomplete;

We might want to handle it a bit differently in case the variable was not in the global scope instead of assigning it to undefined (i.e. deleteing it), but it's not really necessary I think.

cc @rayrutjes @vvo

For me that seems like a good approach!

Seems nice! Just be careful about
var oldAutocomplete = window.autocomplete;
window.autocomplete = oldAutocomplete;

When doing this and if window.autocomplete was not present at load, code like:
'autocomplete' in window;

Will not return true
So only replace window.autocomplete in noconflict is something was really defined before. We actually had the issue at some point I think.
Other than that, nice!

@vvo updated first post's implem with your feedback taken into account. WDYT?

All good!

gg @Jerskouille 👍


Support for école directe

Support for this ENT:
École directe
Unfortunately I can't help.

EcoleDirecte is a separate service not associated with pronote.


Verified extraction to OCaml

To verify extraction to OCaml, one needs a semantics of OCaml in Coq (which may or may not be verified itself in some way). This is an attempt to document relevant resources to make this happen.
One early effort on formalizing OCaml semantics is OCaml Light by Scott Owens and his collaborators.  The language and semantics is encoded in the Ott language and then exported to HOL4, Isabelle/HOL, and Coq. The soundness proof of the type system is only in HOL4, however. A paper describing the formalization and proofs was published in ESOP 2008. All files are available in the Ott repository on GitHub. The repository version of Ott can produce a definition of OCaml Light that compiles with recent Coq.
While there are some related efforts to formalize OCaml in different proof assistants, as discussed here, OCaml Light seems to me to still be the most realistic and relevant one for verifying extraction in MetaCoq.

Would type soundness be needed for the correctness of extraction? Probably everything you would need is a definition of the OCAML light type system and a definition of evaluation on OCAML light, plus potentially some minor convenience Lemmas about evaluation.
But I don't think type safety would actually be needed to prove a simulation result between erased Coq terms and OCAML.

Ah, and as @mattam82  has mentioned before, OCaml light probably does not cover Obj.magic, which is inserted a lot by the extraction at points where the erased Coq terms have boxes.
I have been thinking about extraction to cbv lambda-calculus, encoding recursion using fixed-point combinators and inductives using scott encodings (as we do it in the ITP paper). In untyped lambda-calculus, you can implement Obj.magic again using a FPC. Probably the same trick can be used for untyped OCaml, but to get the extraction type-check we'd have to extend OCaml light by Obj.magic (which might still not be very hard).

I think you're right that having the type soundness proof in Coq is not strictly necessary for doing verified extraction. In theory, the only thing we want is that the OCaml Light semantics is consistent with what is actually implemented in a recent OCaml compiler, which is justified in the paper and could also be justified by differential testing. Nevertheless, it could be a good student project to translate the OCaml Light type soundness proof from HOL4 to Coq, for example, using CoqHammer to do the translation at the high-level argument level.
Right, you need Obj.magic also, and hopefully it's not too hard to add. But a first step might be to see if the OCaml Light semantics could be used to verify extraction for some really restricted subset of Gallina without Obj.magic?

There is now a standalone repository that can generate the OCaml Light definitions that works in Coq 8.8: https://github.com/palmskog/ocaml-light-extraction
@mattam82 can I add extra-dev OPAM packages for MetaCoq so I can use them in CI for MetaCoq-dependent projects like this one?

Sure! Do you think the current .opam files will work easily? I wonder what's the most efficient way to do that.

About the changes to erasure that would be necessary to target ocamllight: certainly quite a few Obj.magics would be needed for dependently-typed code. About linking to CertiCoq, we discussed a bit with Andrew Appel and Aquinas Hobor, the first obstacle we see would be updating the garbage collector to handle refs. The purely functional character of Coq helps a lot having an efficient GC that does not require any operation at deallocation time for example.

I submitted the OPAM package definitions based on the .opam files, and they seem to work as intended.
The initial workflow I had in mind for OCaml Light extraction was actually to completely elide CertiCoq and output the verified OCaml code in the simplest way possible (e.g., printing it from inside Coq). This has the advantage that it can be applied directly to lots of our existing OCaml-based extraction projects for testing, although the OCaml compiler of course remains in the TCB.
With respect to Obj.magic and OCaml Light extraction, one plan could be as follows:

set up boilerplate for MetaCoq+OCaml Light extraction correctness (for some tiny language fragment?)
prove correctness (and output well-typing) for "typedef" OCaml Light (no modules) assuming input Coq code never needs Obj.magic or modules (is not dependently-typed)
extend OCaml Light definition and type system with Obj.magic
extend correctness proof to dependently-typed Coq code
extend correctness proof to "modules+typedef" OCaml Light for Coq code with dependent types and (non-parameterized?) modules

Hi guys,
I've been looking in the same direction. It looks like if we want to integrate this with the certified erasure, we need, probably, to do it in a similar way, as it described in Pierre Letouzey's thesis: implement a modified version of the type inference algorithm (Pierre's proposal is to use algorithm M) to recover types from the CIC_box.
I am currently taking a bit different route: remove redundant boxes after erasure and pretty print OCaml-like code (I target smart contract languages). It is safe to remove boxes if the constants and constructors are applied to all logical arguments (either coming from proofs, or types). I've implemented a version of erasure for types to OCaml-like types and validation procedures that check if constants and constructors applied enough.
It is available in my fork: https://github.com/annenkov/template-coq/blob/coq-8.11-erase-annotated/erasure/theories/Debox.v
I also added some information to binders, so one can know if the binder is a "dummy" abstraction or application and can be potentially removed.
I have a working pretty-printer that prints Liquidity code (basically, some sort of a restricted OCaml):
https://github.com/AU-COBRA/ConCert/blob/extract-cert/extraction/theories/LPretty.v
Maybe we can accommodate some of that stuff for OCaml Light.


devtools support for non-poetry components - ci commands

Currently devtools ci commands are prefixed with "poetry run".
This needs to not happen when they are overridden using ci.PluginServices.CONFIGS.COMMAND_GROUPS, but we need to find some other way to specify the virtual environment to use.

after updating the ProjectTools and ComponentTools to be less poetry-specific, i deleted any remaining ci command that wasn't trivial to support. since they were all just shortcuts to poetry commands, you should be able to go back to using your favorite package tool directly and not worry about doing it through rats-devtools ci subcommands.
rats-devtools should work with pdm, uv, and poetry now with a few new tests but it should also work with any other PEP 621 compatible tool (still can't support conda).


Gallery

Cool user prompts or functions need an official gallery for showing off.

I have ported my ZSH prompt to janetsh, you can see the result here:

That is awesome, I definitely want to collect screenshots and the code people can paste into their own files, perhaps as gists.
Here is my current prompt, though it isn't as nice as your one haha

(set *hist-file* (first (sh/expand "~/.janetsh.hist")))

(def tc
  {
    # The wrapping \x01 ... \x02 tell readline the surrounded string has zero length.
    # Without it we get strange artifacts in the string history.
    :bold "\x01\x1b[1m\x02"
    :none "\x01\x1b[0m\x02"
  })

(set *get-prompt*
  (fn [p]
    (var cwd (os/cwd))
    (var home (os/getenv "HOME"))
    (var who "<unknown>")
    (var where "<unknown>")
    (var end "$")
    (def pstate (parser/state p))

    (when (not (empty? pstate))
      (set end (string pstate "..")))
    (try
      (do
        (set who (sh/$$_ whoami))
        (set where (sh/$$_ hostname)))
      ([e] nil))
    (when (string/has-prefix? home cwd)
      (set cwd (string "~" (string/slice cwd (length home)))))
    (string (tc :bold)
            "[" who "@" where ":" cwd "] " end " "
            (tc :none))))

Here are my current rc files:
https://gist.github.com/pauldub/73ee3501382ed85dc9b49a398e501da8

this is a little bit old with regards to latest janetsh updates so some things are not needed anymore (like the constant string trimming...)

All good - btw, don't hesitate to let me know if there are other problems. I am glad you worked out using keywords for escaping the janet symbol rules.

Really simple RC file I've been using to emulate my bash prompt, which is pretty basic.
https://gist.github.com/bakpakin/1cbb2d86e346355695778b41d300f16f

Site is in the www directory - hosted at janet-shell.org

@pauldub is it ok if I update the code for the newer janetsh before I put it on the site?

@andrewchambers of course, go ahead :)

@pauldub I fixed some bugs in the prompt code (a redirect missing a '&'), and used some of the new command shorthand.
It is now in the gallery with the modified code: https://janet-shell.org/gallery.html


CSS not accessible while I run the app

I learning the Blazor, While I create App and run it, bootstrap is not loading, while it presents in wwwroot / css folder.
Please let me know which issue was there.
Thanks in Advance
Shree Nivas Kushwah

Were you running the Blazor tutorial when you encountered this issue?
https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/run
Did you make any changes to template code before running into this?
Adding @danroth27 for assistance.

Can you try creating the project with no spaces in the name? I'd like to confirm a hypotheses we have.

Thanks lot,
It works.
Shreeniwas Kushwah
Senior .Net Developer
MAPIT Bhopal
On Wed, Feb 14, 2024 at 1:43 AM Maira Wenzel @.***>
wrote:

Can you try creating the project with no spaces in the name? I'd like to
confirm a hypotheses we have.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/website-feedback/issues/8#issuecomment-1942370735,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASAJFSUKFAMWRU5G45UX5R3YTPCQLAVCNFSM6AAAAABDEGRX22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBSGM3TANZTGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Glad to hear and thanks for letting us know. This is also a known bug that is being tracked to fixed.
Check https://github.com/dotnet/aspnetcore/issues/52519 for more information.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-30-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4266

Questions ?
Please refer to the Backport tool documentation


new_allocator

Empire Version
most recent git clone (6/14/18)
OS Information (Linux flavor, Python version)
Linux - 3.16.0-4-amd64
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
running setup.sh fails
Screenshot of error, embedded text output, or Pastebin link to the error
Traceback (most recent call last):
File "./empire", line 8, in
from OpenSSL import SSL
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/init.py", line 8, in
from OpenSSL import rand, crypto, SSL
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/rand.py", line 10, in
from OpenSSL._util import (
File "/usr/local/lib/python2.7/dist-packages/OpenSSL/_util.py", line 18, in
no_zero_allocator = ffi.new_allocator(should_clear_after_alloc=False)
AttributeError: 'FFI' object has no attribute 'new_allocator'
Any additional information

@r3cursive123 What troubleshooting steps have you taken? Also, please provide the linux distro that you're using.


Record a count metric for any rate sensors

Codecov Report

Merging #115 (ed82f95) into main (d9aa322) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #115      +/-   ##
==========================================
+ Coverage   71.85%   71.94%   +0.09%
==========================================
  Files         147      147
  Lines        2814     2816       +2
  Branches       75       77       +2
==========================================
+ Hits         2022     2026       +4
+ Misses        792      790       -2

Impacted Files
Coverage Δ

...metrics/src/main/scala/surge/metrics/Metrics.scala
100.00% <100.00%> (ø)

.../surge/internal/kafka/KafkaProducerActorImpl.scala
82.84% <0.00%> (-0.73%)
:arrow_down:

...health/windows/actor/HealthSignalWindowActor.scala
93.10% <0.00%> (ø)

...kafka/streams/KafkaStreamLifeCycleManagement.scala
65.51% <0.00%> (+4.59%)
: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 d9aa322...ed82f95. Read the comment docs.


[vagrant] Installation of nfs client fails

Hi,
I am migrating my vagrant boxes from centos/8 to almalinux/8 and am using the libvirt provider with nfs shares.
The setup of the machine fails like this:
==> default: Installing NFS client...
==> default: Removing domain...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

if command -v dnf; then
  if `dnf info -q libnfs-utils > /dev/null 2>&1` ; then
    dnf -y install nfs-utils libnfs-utils portmap
  else
    dnf -y install nfs-utils nfs-utils-lib portmap
  fi
else
  yum -y install nfs-utils nfs-utils-lib portmap
fi

if test $(ps -o comm= 1) == 'systemd'; then
  /bin/systemctl restart rpcbind nfs-server
else
  /etc/init.d/rpcbind restart
  /etc/init.d/nfs restart
fi

Stdout from the command:

/bin/dnf
No match for argument: nfs-utils-lib

Stderr from the command:

Error: Unable to find a match: nfs-utils-lib
Failed to restart rpcbind.service: Unit rpcbind.service not found.
Failed to restart nfs-server.service: Unit nfs-server.service not found.

dnf info -q libnfs-utils fails and then dnf -y install nfs-utils nfs-utils-lib portmap does not find nfs-utils-lib.
The issue here is that libnfs-utils is in the epel-release repo. I did not look at the centos/8 image but I suppose that it comes with epel-release pre-configured so I am suggesting to add epel-release to the almalinux/8 image as well, for compatibility reasons.
I modified the vagrant file plugins/guests/redhat/cap/nfs_client.rb and added the line dnf install -y epel-release as a workaround and that worked for me.
Thanks

Hi, @mtorromeo
EPEL is not enabled on centos/7, centos/8 and centos/steam8 vagrant boxes.
Here are a couple of Workarounds until #11 or maybe another fix:

You can add config.nfs.verify_installed = false in your Vagrantfile and install nfs-utils manually.
or
Change dnf -y install nfs-utils nfs-utils-lib portmap line to dnf -y install nfs-utils
Because RHEL8 family distros don't have nfs-utils-lib package, and portmap obsoletes by rpcbind which is a dependency of nfs-utils.

I've released the updated box with nfs-utils installed: https://app.vagrantup.com/almalinux/boxes/8/versions/8.3.20210427
@LKHN thanks!

@ezamriy, Thanks!
I just checked the new build of the box, the NFS version v3 and v4 works out of the box.

dnf -y install nfs-utils nfs-utils-lib portmap line

Could you tell me in what file I can find this [dnf -y install nfs-utils nfs-utils-lib portmap] line?


Improve Test coverage

Add unit tests to increase coverage to at least 85%.

We're tracking this separately.


Recipe command

Initial commits are very early draft! I just want a clean way to follow along and ask feedback if necessary.

What might also be a good idea is to accept 0 as a possible answer on every question to abort the process of adding a recipe

What might also be a good idea is to accept 0 as a possible answer on every question to abort the process of adding a recipe

Done!


Bug of Intellisense with JavaScript

VSCode Version: 1.8.0
OS Version: Windows 10.0.14393

Steps to Reproduce:

Create a project folder and create func.js, main.js, and jsconfig.json in it.

jsconfig.json:
{
    "compilerOptions": {
        "target": "ES6"
    },
    "file": [
        "func.js"
    ]
}

func.js:
function Test() {
    // ...
}
// ...
Test.a = function() {
    // ...
    var k = require('n');
    // ...
    return 0;
};
// ...
Test.prototype.b = function() {
    // ...
    var k = require('n');
    // ...
    return 1;
};

main.js:
Test.a();
var test = new Test();
test.b();

Open main.js, and move mouse on Test or a() at line 1, the ToolTip shows any, move mouse on any words, the ToolTip shows the sentence that have any. Also autocomplete do not show a when I type Test. and b when I type test..

Edit func.js, make lines which has require as comment, like :

function Test() {
    // ...
}
// ...
Test.a = function() {
    // ...
    //var k = require('n');
    // ...
    return 0;
};
// ...
Test.prototype.b = function() {
    // ...
    //var k = require('n');
    // ...
    return 1;
};

Open main.js, and move mouse on Test at line 1 and line 2, the ToolTip shows function Test(): void, but move mouse on  a() at line 1, the ToolTip still shows any, move mouse on any words at line 2 and line 3, the ToolTip shows the sentence that haven't any. For example, test shows

var test: {
    b: () => number;
}

Output Test.a() can get 0, test.b() can get 1. At Step 4, Visual Studio Code found the definition of test.b() as Test.prototype.b (move mouse on b() at line 3 and the ToolTip shows (property) Test.b: () => number), but not found the definition of Test.a() because move mouse on a() at line 1 and the ToolTip shows any. Also autocomplete show b when I type test., but not show a when I type Test..

Conclusion:
If the definition of the method or prototype of function in JavaScript have method require() in it, Intellisense in Visual Studio Code cannot find the definition of "that function, the prototype of that function, and the method of that function" at another JS file.
If the definition of the method or prototype of function in JavaScript do not have method require() in it, Intellisense in Visual Studio Code can find the definition of "that function, and the prototype of that function" at another JS file, but still cannot find the definition of method of that function at another JS file.

Quick question: is "main.js" listed in the "files" section of the jsconfig.json?

All problem still exist when "main.js" listed in the "files" section of the jsconfig.json.Also all problem still exist when "files" section has nothing.

I have reproduced this and it looks like a duplicate of https://github.com/Microsoft/TypeScript/issues/7046
@mjbvz can you look at the issue I posted and confirm if you think it is a duplicate?

So method require() can impact on Intellisense work or not is a bug?

@waderyan No, I think this is a different issue. You see the same using classes:
class Test {
    foo() {
        var k = require('fs');
        return 1;
    }
}

var x = new Test();
// Type of `x` is any. If you remove the `require`, the type becomes `Test`.

From debugging, this looks like a TS issue. I'll move this issue over to them for tracking.

This issue was moved to Microsoft/TypeScript#13033


dragging is not working in this case

I am trying to drag a tab to another column and the targeting column is not accepting it. It is hard to describe, but I have an animation.
The gif is converted from a video and somehow it is a bit slow, sorry about that

Thanks!

I was able to reproduce the bug, I think it only affects the "Apps" folder.
As a workaround, enable "Show top-level folders" in the options

Thanks! It worked!

I have same issue, but it is not only Apps folder but any folder and enabling (or reenabling) "Show top-level folders" did not help.
I'm using latest version installed from chrome store in Microsoft Edge on OpenSUSE Tumbleweed.


Web ant97 2022 03 01

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

/azp run

Retrying rerun the CI to see why fail in SemanticValidation.
@naveedaz
Do we have owner from AppServicePlans.json and WebApps.json?
Here is 2 customer issue that likely caused by incorrect/incomplete swagger. Checking if we can at least add the "addition" one into 2022-03-01.
The other alternative would be S360 report...
One is on AppServicePlans, which only adds a property (that might be missing from swagger but exists in backend).
https://github.com/Azure/azure-rest-api-specs/pull/19254
Another one is on WebApps, seems fixing an incorrect swagger (that involved breaking change review, but apparently customer not able to do that).
https://github.com/Azure/azure-rest-api-specs/pull/17653

OK, SemanticValidation likely caused by incorrect resolution of merge conflict. It should be same level as "inputs" property.
https://github.com/Azure/azure-rest-api-specs/blob/6345e8a41024025f8a6470dbf5ac018f300a5428/specification/web/resource-manager/Microsoft.Web/stable/2022-03-01/WebApps.json#L24763:23

cross-version breaking changes already approved in PR https://github.com/Azure/azure-rest-api-specs/pull/18460

/azp run

/azp run

@naveedaz, @weidongxu-microsoft -- What's your rough estimate on when we'll get this merged, are we looking at this week or into July?
@naveedaz -- It looks like this new API version renames the RP's (web/sites to WebApps). Does this mean the package and method names will change on the client SDKs?

@naveedaz
Error in ModelValidation would require either adding examples, or suppression in readme.
@alexkarcher-msft for verify whether the pagination with POST would require POST or GET in {nextLink} query.
If it is POST in {nextLink} query, I recommend remove the x-ms-pagable unless you are sure future it will be a pageable and plan to support GET in {nextLink} query.


Minor grammar tweak to README

Title says it all

Codecov Report

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

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   28.28%   28.28%
=======================================
  Files           9        9
  Lines         693      693
=======================================
  Hits          196      196
  Misses        465      465
  Partials       32       32

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 513a799...7897f0b. Read the comment docs.

Welcome @c0bra. Thanks a lot 🤗


docusaurus-init fails in Hack/PHP projects: Error: ENOTDIR: not a directory, scandir '.../vendor/bin/hh-autoload'

Is this a bug report?
(write your answer here)
Yes
Have you read the [Contributing Guidelines on issues]
Yes
Environment
Docusaurus was just installed via yarn global add docusaurus. Yarn outdated command fails:
error An unexpected error occurred: "No lockfile in this directory. Run `yarn install` to generate one.".

Probably because this isn't a JS project.
Steps to Reproduce

Install HHVM: https://docs.hhvm.com/hhvm/installation/introduction

$ git clone git@github.com:hhvm/hhast.git
$ cd hhast
$ wget https://getcomposer.org/composer.phar
$ hhvm composer.phar install
$ docusuarus-init

Expected Behavior
Creation of a docusaurus skeleton
Actual Behavior
Errors out. Ends with:
(node:2585) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
warning package.json: No license field
$ docusaurus-examples
Wrote docusaurus scripts to package.json file.

.gitignore already exists in /private/tmp/hhast/website. Creating an example gitignore file for you to copy from if desired.

fs.js:145
    throw err;
    ^

Error: ENOTDIR: not a directory, scandir '/private/tmp/hhast/vendor/bin/hh-autoload'
    at Object.fs.readdirSync (fs.js:895:3)
    at print (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:82:21)
    at contents.forEach (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:114:26)
    at Array.forEach (<anonymous>)
    at print (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:112:12)
    at contents.forEach (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:114:26)
    at Array.forEach (<anonymous>)
    at print (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:112:12)
    at contents.forEach (/private/tmp/hhast/website/node_modules/tree-node-cli/tree.js:114:26)
    at Array.forEach (<anonymous>)
error An unexpected error occurred: "Command failed.
Exit code: 1
Command: sh
Arguments: -c docusaurus-examples
Directory: /private/tmp/hhast/website
Output:
".
info If you think this is a bug, please open a bug report with the information provided in "/private/tmp/hhast/website/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

yarn-error.log and full terminal log: https://gist.github.com/fredemmott/3755bca61cddc6718afc16ae83979f2f
Reproducible Demo
Covered above. No siteConfig.js as this is a bug in docusuarus-init - it doesn't exist yet.
Reproduces with other hack projects, eg hhvm/hsl. Does not reproduce with mkdir foo; cd foo; mkdir -p vendor/bin; touch vendor/bin/helloworld

@fredemmott I wasn't able to reproduce this issue. I cloned https://github.com/hhvm/hhast, did docusaurus-init and the website dir was generated. Do you have any symlinks in your dir?
It seems like it failed in the tree printing step but the directory skeleton generation step should have succeeded.

no symlinks except as created by composer/git - this does mean that vendor/bin/hh-autoload is a symlink.
If composer isn't ran (equivalent to not running npm install):

vendor/bin/hh-autoload doesn't exist
there are no symlinks
docusaurus-init works fine

I see. The tree printing library we're using doesn't support symlinks at the moment. But the skeleton should have been generated. Was the skeleton dir generated? Feel free to ping me on Work Chat to discuss about it, I'll be able to respond faster there 😄

https://github.com/hhvm/hh-apidoc/issues/29 is what led to this :)


Cargo fix --prepare-for should only apply edition fixes

Fixes #5738
.. or at least it looks like it does? Please check my test.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! I'm not sure though that this strategy will work because I believe the reported lint in the diagnostics is the lint in question (like async_idents) rather than the lint group (the compatibility lint group) unfortunately.
We may be able to tweak the compiler to tell us the lint group though!

I think I see what you mean: see the fix::fix_overlapping failure in CI which says:
note: `-W absolute-paths-not-starting-with-crate` implied by `-W rust-2018-compatibility`

We may be able to tweak the compiler to tell us the lint group though!

Before you nerd-snipe me into the compiler repo, how maintainable is it to whitelist the list of lints implied by rust-*-compatibility?

That's what I suspected/feared.
Is there an existing ticket in the rust repo for this? Do you think you (or @killercup, or...?) could flesh one out so I know how to get started? 🙏

Ah unfortunately I don't thik there's an issue on the rust-lang/rust repo, and I wouldn't actually know where to get started for it :(
@killercup may have more ideas though!


use config.validator instead of validator

this allows you to actually specify a custom validator instead of having to patch node-validator.

thanks. can you let me know when this is published?

@seiyria It's been published in v2.0.2 😊

thanks so much!

Strangely, I keep getting an error trying to install 2.0.2:
npm ERR! enoent ENOENT: no such file or directory, open '/Users/seiyria/GitHub/posys/node_modules/.staging/bookshelf-validate-d0eadb27/package.json'

@kripod could you please re-publish as 2.0.3 or something? I cannot install 2.0.2 and it's breaking my builds + forcing me to keep local changes for this. Thanks!

@seiyria I just re-published the package as v2.0.3 with updated dependencies. Sorry for the inconvenience!

Thanks! Looks like it's working now.