migrate away from goautoneg, a soon-to-be deprecated dependency

https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
tl;dr : Mercurial features and repositories will be officially removed from Bitbucket and its API on June 1, 2020.
goautoneg uses mercurial, and when support ends, the repo will be deleted. I suggest either making a git fork or migrating to another library.

We could move to this: https://github.com/adjust/goautoneg
It's not been updated in 5 years, but then the original in bitbucket hasn't been updated in 7.
@leighmcculloch what do you think?

It would be convenient to adopt proposal #19307 that will add some of this logic to the stdlib or the x packages.
It'd be okay to move to the adjust fork, but there would likely be no advantage over forking it ourselves given the authors haven't suggested they're going to maintain it.
I think we should fork the BitBucket version at least temporarily until the proposal has code behind it. I'd like to preserve the original history in the fork too, which we can do. If the proposal ends up being an x package we can start using it immediately without needing to wait for two Go releases to happen.
I'm participating in the proposal from here: https://github.com/golang/go/issues/19307#issuecomment-564702037.
I'm happy to take this on sometime, it is a small effort. Anyone else is welcome to take it though.

Preserving the history seems valuable. Forking ourselves seems straightforward until/if stdlib picks this up. I agree.

Process to import mercurial data into a git repo is here: https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git#_mercurial

Is there anything I can do ? If I were to import it into a git repo and you just fork it (to have control over the code) would you use that as a dependency ?

This is one thing that will be simpler for us to do. The code review and verification we'll need to do means the effort to switching and importing the fork will be essentially the same, we'd be repeating your effort. Thanks for offering.
I've got this in my backlog but we've got sometime before this needs to be address given Mercurial on BitBucket isn't disappearing until June 2020.
@drov0 Is there anything else that'd drive needing to change this before that date that you know of?

@leighmcculloch Well our CI is failing because we don't have mercurial installed in the image. But more important than that, people always take a long time to update dependencies, especially with golang so the sooner this change is made, the less likely people's build will fail in june.

@drov0 If you use the latest version of Go and modules, you shouldn't need Mercurial installed.  This is how I avoid needing Mercurial installed.

Bump. Looks like http://bitbucket.org/ww/goautoneg got removed today.

Fixed in #2952.

Fixed in #2952.

Hi everyone! Any idea on a timeline for when this dependency update will become available in a new horizonclient/txnbuild release? From what I can see this change is not yet available in the latest release of the client libraries.
Please let me know if I am misunderstanding something and there is a way to use the latest client libraries release with the updated depenency.


Added Dockerfile + puppeteer support

Here it is, located in the backend\AzureContainer folder I include a Dockerfile that will build a docker image that supports starting the code-server and then running the action.js with nodejs and saving the screenshot to a folder named images. You can mount a local (or Azure blob storage) to this location to get the image outside of the container!
Oh, I also changed the WORKDIR to onlythemes so we aren't using the user profile root location.
Also.... I learned that we cannot override the ENTRYPOINT of the base image so instead, I replaced their entrypoint.sh with our own.

@all-contributors please add @parithon for code, documentation and infrastructure


⚠ ClamAV has degraded performance

In 3a38c34, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 68 ms

Resolved: ClamAV performance has improved in d263db7.


Add support for node 4.3.2 runtime

Amazon recently added a nodejs 4.3.2 runtime for lambda. It would be able to specify it as a value in the configuration json files.  Maybe like:
{
  "description": "<function desc> ",
  "runtime": "nodejs:4.3.2"
}

:+1: just saw this as well

+1

http://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunction.html
Amazon has "nodejs" for the 0.10 runtime, and "nodejs4.3" for the new one, would make sense to stay aligned with that terminology

It's a little annoying (internally) not having a nice delimiter, even "nodejs:4.3" like you mention would be nice

+1 for staying aligned with AWS terminology. I will work on it tomorrow.


reorganizing the docs

This does a few things

Changes _toc.yml so that pages: are now sections:. cc @najuzilu I think this will require an update on your end.
Updates the documentation to give a better idea for how header: can be used to define chapters
Reorganizes the docs a bit more in general to make them more modular.

@choldgraf fantastic! Is divider no longer supported? I'm just wondering because I did not see it in the documentation.

I did decide to drop divider support for now, because I think the same could be accomplished with header and css. What do you think?

(mostly because divider was doing a bunch of complicated stuff under the hood and it seems like there must be an easier way to accomplish it... We can always revisit though)

Sounds good!


feat[readme]: Included readme file for replica rebuild scenarios

Signed-off-by: nsathyaseelan<EMAIL_ADDRESS>

As this test case is changed hence the readme also need to be change


Fail to install powerfulseal because of locale?

ubuntu 16.04
python 2.7.12
root@i-mki26uqf:/opt# python --version
Python 2.7.12

root@i-mki26uqf:/opt# pip install powerfulseal
Traceback (most recent call last):
  File "/usr/bin/pip", line 11, in <module>
    sys.exit(main())
  File "/usr/lib/python2.7/dist-packages/pip/__init__.py", line 215, in main
    locale.setlocale(locale.LC_ALL, '')
  File "/usr/lib/python2.7/locale.py", line 581, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting

This looks like a problem with your setup. Check out this response on stackoverflow - looks like it might be useful to you ?

Hi @calvinyv any updates on this ?
Can we close the issue ?


Add Support for MSVC compiler

Is that a possibility?

I assume you mean Microsoft's MSVC compiler (and MSCV was a typo). Unfortunately I don't believe that will run on linux...maybe under wine? Anyway, to work on Docker it has to be on linux.

Something like that?
https://stackoverflow.com/questions/36639422/microsoft-compiler-in-docker

It looks like it's possible with a microsoft/windowsservercore base image

So I had never really thought about supporting windows in this repo....all the images in here are specific to boost on linux, but I'm not sure there is a fundamental reason not to. However, before hitting that step we need to get an image with the msvc compiler/toolchain on it (the linux images in here pull from the respective gcc and clang images). My interest has been peaked enough that I'd like to put together one of these, but my amount of free time is pretty low, so it will probably be months before I get around to it. If you want to put together a docker image with the tool chain on it, I'd be more than happy to add an image here with the appropriate boost config. This would be really useful for my project that consumes these images for running the boost unit tests, right now I have manually created VM images with all the Visual Studios installed on them to run those. Docker images would be much better.

Ok, I'll see what I can do

This work has been started in the msvc-win-docker repo, but hasn't been very smooth. Once that is working, boost test images can be pulled in here, but we'll open a new issue at that point.


Issue : Prevent text select on firefox

When doing a click and lock by mistake (touchpad mostly) FF will start selecting text wherever it can.

Looks like this has been fixed since the issue was filed. I can't reproduce on FF with my laptop.

I admit I tried to reproduce and couldn't manage as well. Closing.


Some file is skipped during searches

I have a really strange issue. I have a variable called start_time that is declared in a file called Active.d and used in a file called Downloads.d. But when I try to search for it with ag -w start_time src, it only shows the occurrence in Active.d. If I use grep -rw start_time src, then it shows me all occurrences as expected.
I can't figure out why the Downloads.d file is skipped.
Unfortunately I can't share the source code as they are my employer's proprietary software. I tried to reduce the test case further by copying only these two files into a temporary directory, but then ag did not skip the Downloads.d file and reported all occurrences.
I'd appreciate any help on this, and would be happy to run other tests if needed.

Maybe there is something in your ingore lists (eg. .gitignore) that prevents the Downloads.d folder to be scanned ? Is the file in the Downloads.d directory listed when you do ag -l ?

Downloads.d & Active.d are not directories, they are source files. We code in the D programming language.
I haven't tried ag -l yet though. Will try and report back.

Sorry, i totally missed the 7 times you mentioned that those .d things were files and assumed dirs. I'll blame the lack of coffee :\

I can't for the life of me reproduce this anymore. I wonder if it was human error, but I also can't imagine what I could have done wrong.
I'm going to close this now, and reopen if I see this again (after having run ag -l).
Maybe it was me who was suffering from the lack of coffee :
Sorry for the noise.


Get rid of the removed DeadLetterChannel in ChannelableStatus

Problem
This PR https://github.com/knative/eventing/pull/6722 removes DeadLetterChannel in ChannelableStatus
We will have to remove it from the following places

https://github.com/knative-sandbox/eventing-natss/blob/e1340217a7afb996d6264d4f97bb1b2a10dfa3ed/pkg/reconciler/dispatcher/jetstream/nats_jetstreaming_schannel.go#L291
https://github.com/knative-sandbox/eventing-natss/blob/e1340217a7afb996d6264d4f97bb1b2a10dfa3ed/pkg/reconciler/dispatcher/natss/natsschannel.go#L291

Persona:
Which persona is this feature for?
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.

/remove-lifecycle stale


move scitokens cache to /var/run

Since they didnt' bother to make a specific environment variable for it or whatever... sigh.

Is it guaranteed that  /var/run/user/{uid}/ will exist? Should at least check, no?
Looks like that's a tmpfs filesystem, I guess that's OK? Cache is small, and if it has to be recreated occasionally so be it.
Also I notice on an AL9 system that it creates /run/user/{uid} instead.
Ain't it fun?

To @DrDaveD's point in slack, and @retzkek's here, since /var/run/user may not even exist, depending on OS, we're already dumping small files (tokens) into /tmp, we could even dump this in there too.  Maybe make a directory in there for the user, something like /tmp/scitokens_$(id -u)?  So you'd make that dir if it doesn't exist, and then set cache_location there?
Before merging this PR, we should make sure that we test this both with regular and shared-account users.

We could even theoretically let users share a single cache file in /tmp, but that's probably just inviting more trouble.

$XDG_RUNTIME_DIR is set to /run/user/{uid} even on el7; /var/run is a symlink pointing to /run.  The directory and the environment variable are created only by systemd for interactive logins.  That directory cannot be created by an unprivileged program.  The backup will need to be something either under /tmp (as is the case for the WLCG bearer token discovery protocol) or /dev/shm/.

In any case it would be better for a fix to be in the scitokens library instead of in jobsub, since that's where the problem is.

So, just to avoid cases where the runtime dir isn't set, etc.  I've simplified it to put the scitokens config and the token cache all in the same /tmp/js_scitoken_{UID} directory (with $TMPDIR overriding /tmp)   Then there is only one directory to make and manage.   I also have it touch the config file whenever we run, so /tmp cleaners don't delete it out from under us.
Added a doc strng as well, and passes unit tests.

So it looks like this:
[mengel@fifeutilgpvm01 lib]$ ls -laR /tmp/js_scitok_1733
/tmp/js_scitok_1733:
total 128
drwxrwxr-x   3 mengel mengel   4096 Nov 20 11:25 .
drwxrwxrwt. 16 root   root   114688 Nov 20 11:29 ..
drwxrwxr-x   2 mengel mengel   4096 Nov 20 11:25 scitokens
-rw-rw-r--   1 mengel mengel     48 Nov 20 11:28 .scitokens.cfg

/tmp/js_scitok_1733/scitokens:
total 12
drwxrwxr-x 2 mengel mengel 4096 Nov 20 11:25 .
drwxrwxr-x 3 mengel mengel 4096 Nov 20 11:25 ..
-rw-r--r-- 1 mengel mengel 3072 Nov 20 11:25 scitokens_keycache.sqllite
[mengel@fifeutilgpvm01 lib]$ cat /tmp/js_scitok_1733/.scitokens.cfg
[scitokens]
cache_location: /tmp/js_scitok_1733

But I agree with @DrDaveD, it should be fixed upstream.   Putting the token cache in $HOME is a problem with NFS mounted $HOME areas, and that should be adressed up there.   In the mean time, however, this is a workaround that
should let us keep running.

And I see that @retzkek beat me to it already https://github.com/scitokens/scitokens/issues/188.

So in case this moving to /tmp thing doesn't fix the bug, remove zero length cache files, if found.

Alternatively it could set only $XDG_CACHE_HOME if it isn't set, as suggested in https://github.com/scitokens/scitokens/issues/188#issuecomment-1820558467.

Alternatively it could set only $XDG_CACHE_HOME if it isn't set, as suggested in scitokens/scitokens#188 (comment).

I like this idea, but for now, since nobody has any functional issues with Marc's PR, let's merge it and get this released so users won't have to do the workaround themselves.
I'll open a new issue with this suggestion so we can try it out, since it is much cleaner than our workaround.  I suppose we can set $XDG_CACHE_HOME for only the jobsub operation (and then put it back), but I want to make sure we're not breaking anything else.


Use ISO date format not checked when using configure on integration

The problem
When adding the integration through the configflow I selected the option to use the ISO date format. However when I press Configure it is not checked. I guess this would also disable the option when I would save the form (I did not try it, was just checking what was behind the Configure button)

Version of afvalwijzer integration having the issue?
2024.12.01
Version of Home Assistant Core having the issue?
core-2024.12.2
Anything in the logs that might be useful for us?
No

Additional information
No response

see: https://github.com/xirixiz/homeassistant-afvalwijzer/issues/328
It is the same error

Ah, indeed. That seems the same. I did scan the titles before submitting, but I thought this was only a presentation issue. Did not try to change anything.
Will close this one because it is duplicate


[ASCII-1442] components documentation.  Explaining how the status component works and how to add a status provider to your component

What does this PR do?
Add documentation on how the status component works and how to add a status provider to your component

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


2 dark pressure plate issues

version used: MC 1.7.10 enderIO <IP_ADDRESS>7

a picked up dark pressure plate (silent or normal) stacks (and changes its type to fit silent->normal or vice versa) to any other (painted to the same block) you have in your inventory (if you don't have another dark pressure plate in your inventory everything works fine)

the dupe bug from #2053 still works for dark pressure plates (always producing a non painted one). The duplication only happens if the pressure plate sits on top of the teleposer.

(the dark pressure plate is also the only item from enderIO that drops when destroyed in creative, could be connected to 2.)

1 is fixed in Ender IO 2.3


Not found androidx.paging (LazyPagingItems and collectAsLazyPagingItems) in common and desktop module

common module:

desktop module:

The issue looks like you're not using Multiplatform Paging! In commonMain, if the package name is app.cash.paging, then it's from Multiplatform Paging, and if the package name is androidx.paging, it's not from us and is instead from the official AndroidX Paging artifact (which won't compile as it's not multiplatform!).
Unfortunately, changing the package name in your code won't help as:

You're using the paging-compose artifact, and Multiplatform Paging doesn't have a paging-compose artifact yet. We just have the artifacts paging-common and paging-runtime.
Multiplatform Paging doesn't target desktop yet. It just targets Android and iOS.

I'm going to close this issue and create two separate issues for the above points as they're independent.


Add props to handle test IDs

Describe the desired behavior
Add a prop for adding a data-test-id, e.g. <Hero testID={'test'}/>
Describe the current behavior
In order to place a test ID on a component, it has to be wrapped, which can break positioning, etc. When placing a test-id directly on a component, it gets ignored.
Is this request related to a current issue?
This is related to issues with the ScoreCard component in WAS

Should we add a PXBlueComponentProps type that enforces the addition of classes and testID props to all our (future) components?

Should we add a PXBlueComponentProps type that enforces the addition of classes and testID props to all our (future) components?

Since the classes change for each component, I don't know that we can make a generic type to enforce it across all of our components.

Looks like the work to extend the root component props has indeed given us the ability to add any data-* property we want onto the component when it's used in an application. So there is no need to add this prop to the components.


Add components repo

Components repo is open for business :tada:

Add componets repo to package.json
Add start-console script  for starting the console

/lgtm


Integrate Firebase Storage in React Native

As a user, I can upload text of my recipe to the app. As a developer, I can store user input in Firestore and easily retrieve and render this information

Currently, as a user they can add a post with pre-programmed input into the database, we will expand on this to account for this feature soon.


NO-TICK: nctl nightly bugs

Disables itst14, passing locally but stalls in ci, tracking here: https://casperlabs.atlassian.net/browse/OP-1932
Pushes era back 1 (default is 3) in test to allow ci to pass. See: https://casperlabs.atlassian.net/browse/OP-1932

bors r+


refmt removes semicolons inside ternary blocks in jsx

This bug appears in<EMAIL_ADDRESS>{true
	? {let foo = "foo"; // refmt removes the semicolon here
		<span> {ReasonReact.string(foo)} </span>}
	: <span> {ReasonReact.string("bar")} </span>}

Reproduced in https://github.com/baldurh/repro-refmt-issue-bs-platform-5
cc @bobzhang

I'm fixing this.


Handle output file names descripency between tsc --b and actual program emit file path calculation

Ensures that if there is error that all files dont belong to 'rootDir' even then 'rootDir' is used as common source directory
Calculation of commonSourceDirectory is done for tsc -b that uses getOutputFileNames api
Fixes  #41801 and #41780

Thank you so much for the fix!! Any idea whether it might be in 4.1.3 or not until 4.2.0?

We would probably want to wait for 4.2 as it is not minor fix and not patch it to 4.1

@sheetalkamat I don't see this in the 4.2.0 or 4.2.1 list of issues for those milestones. Can you confirm it made it into either release?

Yes, I believe this is working in TypeScript 4.2 now. It appears there was a new issue introduced directly in rollup/plugins and TypeScript is no longer the root cause of the failure. See https://github.com/rollup/plugins/pull/818#issuecomment-785194595 for more details


Added Physics Platformer

Hope I've done it right!

It's not exactly the scheme, that I want to follow, but close enough so that I can fix it. My fault. I need some kind of task that runs automatically, then PRs are created.
Thanks.

Thanks.  Which bit needed changing?  There's a few more I want to add.  It's a great list BTW.

I changed it to (state inactive lowercase, keywords lowercase, code repository ends on ".git"):
Physics Platformer
Physics-based platform game

Home: https://github.com/SteveSmith16384/PhysicsPlatformer
State: beta, inactive since 2017
Platform: Windows, Linux
Keywords: arcade, platformer
Code repository: https://github.com/SteveSmith16384/PhysicsPlatformer.git
Code language: Java
Code license: MIT
Code dependencies: JBox2D

Building

Build instructions: Import from sources into a IDE

You're welcome to add more. Please make sure that they are at least in beta stage (kind of runnable) and have a clear (open source) license information as well as a code repository/source code as download. That's the minimal requirement really. Physics Platformer was a bit on the edge in terms of being beta, but that is true for quite some entries here.


[BUG] Lack of generatedMapping.putIfAbsent

Describe the bug
Generated code does not contain "generatedMapping.putIfAbsent" and leads to an exception: Could not find factory for type LoginEmailPost$Response.
To Reproduce
swagger:
openapi: 3.0.3

paths:
  /login/email:
    post:
      requestBody:
        content:
          application/x-www-form-urlencoded:
            schema:
              type: object
              properties:
                email:
                    type: string
                password:
                    type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
                properties:
                  token:
                    type: string

Expected behavior
Generated code should include generatedMapping.putIfAbsent for the response type
Library version used:
swagger_dart_code_generator: 2.11.12

Hi @zltnDC , could you prepare example of swagger file?

Isn't the content of the yaml file enough?

@zltnDC  It's enough)) Will take a look into it!


What are all these green bounding boxes?

In the result video what are all these green bounding boxes? Aren't these bounding boxes should only be on detected objects? I saw many boxes in empty space where there are no objects. Are these false detections?

@monjurulkarim They are top-K region proposals according to the detection scores. In this work, we sampled top-K bounding boxes as region proposals where K is set to 19 by default. It follows the same protocol as DSA-RNN (accv'16). If the bounding boxes are only on detected objects, the number of boxes will not be fixed, which is not practical for model learning.

@Cogito2012 , thank you for your reply. I understood what you did.
Could you please just give me a little more explanation what did you mean by, "If the bounding boxes are only on detected objects, the number of boxes will not be fixed."?

@monjurulkarim Right, in my paper, I proposed to use GCN to learn the object relations for accident anticipation. If the number of bounding boxes is not fixed, the graph structure will be dynamically changing due to increasing/decreasing nodes. In this case, graph convolution is not applicable.

@Cogito2012 I got it. thank you.

@Cogito2012
In the code where can I find the following equation from your paper:

@monjurulkarim It's in line 304 at DataLoader.py file. As our graph is fully connected with this Eq., I just implemented it in data loading.

@Cogito2012
Can you please kindly explain what are these two numbers indicate?

@monjurulkarim The det entry of the feature file is the object detection results for the whole video. In the last dimension, it has 6 columns which are [x1, y1, x2, y2, score, class_label]. You may refer to demo.py at line 65 to see how they are obtained.

@Cogito2012
Thank you for the clarification!

@Cogito2012
I just checked inside the feature file. Why the class score is always zero in all frames?

@monjurulkarim It's just because the threshold of object detection output is small in order to get enough bounding boxes. But this class score is not used in the algorithm. You can just ignore it.

@Cogito2012 Thank you for the reply.
If the score of all the objects are zero then how did you select 19 objects in each frame?

@monjurulkarim You can refer to our bbox_sampling function in line 46 in demo.py. With the detected bounding boxes, we do not rely on the score but use a sampling strategy here.  We randomly select the rest of boxes from top-N entries of the detected boxes, if the number of detected boxes are less than 19.
For your concern, if you find a frame in which all objects have zero scores, that means the detection performance is not good enough for that frame. Absolutely, you can try your best to train a good object detector for your dataset.

Hello, I hope you are doing well!
I came up with a question. My question is why did you select exactly 19 candidate objects? Why not any other number (eg.10 or 30)?

@monjurulkarim This number is simply following the prior work DSA-RNN , where 19 objects + 1 full-frame are used as the feature representation of each frame. I think there is no special reason to set this number but just an empirical value.

@Cogito2012 Thank you!


using opened: false and selected: true

Apologies if this has been covered before, I searched through issues but couldn't find it.
I've tried setting "initially closed" leaf bellow to opened: false but if set to selected: true it will be expanded by default.
    $(function () {
        $('#jstree1').jstree({'plugins':["wholerow","checkbox"], 'core' : {
            'data' : [
                {
                    "text" : "Same but with checkboxes",
                    "children" : [
                        { "text" : "initially closed", "state" : { "opened" : false, "selected": true }, "children" : [ "Another node" ] },
                        { "text" : "custom icon class", "icon" : "glyphicon glyphicon-leaf" }
                    ]
                },
                "And wholerow selection"
            ]
        }});
    });

Any ideas?
Thank you!

Set core.expand_selected_onload to false in this config.
To explain in detail - since you are using checkboxes, the nodes that are children of "initially closed" are considered selected (because the parent is and the parent's state is cascaded down). By default all selected nodes are shown (their parents are opened), because that would make more sense to the end user (especially if checkboxes are not used). But you can disable this behavior with the above mentioned setting in the config.
http://www.jstree.com/api/#/?q=expand&f=$.jstree.defaults.core.expand_selected_onload
Best regards,
Ivan

Thank you Ivan!
Much appreciated


[Analysis - 514] Personalizable Collections

What this PR does / why we need it:
This PR will be kept in DRAFT, it is only to be able to analyze through Storybook how the UI will look and behave to create "featured items" and how they will look in a collection.
Which issue(s) this PR closes:

Closes #514

coverage: 98.403% (+0.9%) from 97.53%
when pulling ad22674bc8a65abf4961bc4a1fcd2a5587e8e3fd on analysis/514-personalizable-collections
into ff8ed384968784225e5a2ebd0618f7a8e332c16f on develop.


fix(clerk-js): Fix props typings for openSignUp function

Type of change

[x] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

While working on the clerk-js beta docs, I noticed that the typings for openSignUp didn't seem right. This PR corrects the issue.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Generate proper symbol name when use C# keywords as variable name.

Souce generator will generate wrong code and cause compile error when use C# keywords like @class @event as variable name. This appear to CommunityToolkit string fieldName = fieldSymbol.Name;. Name will ignore "@" prefix.

Currently the only way to get proper symbol name I found is to use symble.ToDisplayParts().Last().

CC @jaredpar

The API behavior here is "By Design". The name of the symbol here is the name modulo the @. The @ is just not a part of the name, it's a signal to the compiler on how to treat the name that follows. Code that emits names and needs to be conscious of emitting keywords and escape them appropriately.
@333fred this is the second generator issue where we don't have a good API for encoding namse with @ prefix when they are keywords.


Doc: Clarify connection direction of configs in sni.yaml

IIUC, the sni.yaml works for both inbound and outbound TLS connections. But almost all of the configs work on inbound or outbound. This change clarifies which config works in which direction of TLS connection.

@masaori335 can you fix the conflict and make appropriate updates.

@shinrich Rebased on the latest master and followed your comment.

Rebased on the latest master to resolve new conflicts. @shinrich please take another look.

[approve ci clang-analyzer]

[approve ci clang-analyzer]


Set url box send button min width

Fixes
Resolve #1588
Checks

[ ] Ran yarn test-build
[ ] Updated relevant documentations
[ ] Updated matching config options in altair-static

Changes proposed in this pull request:
Just a quick fix via dev tools. Check if it works for you too 😉

Thank you! ❤


Grayscale not working

Hi,
I am trying to covert pdf to grayscale using property 'grayscale':1, but seems to be not working. please help.

Sorry, we can't provide support for questions regarding wkhtmltopdf itself. This is only a wrapper for PHP.


feat: add options.target

Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Introducing a target option in nuxt.config.js, available values:

'server' (default)
'static'

I also add the information in the Nuxt.js banner:

Add process.target in the Vue app + update process.static to use target === 'static' so it works in dev mode.

With CLI: nuxt <command = dev> <dir = '.'> [--target='server']

This option will allow to:

static: Enhance the developer experience when running nuxt dev:

Remove req & res from context
Fallback to client-side on 404 / error / redirect
[x] Dissociate nuxt build & nuxt generate -> creating nuxt prerender to only pre-render routes
[x] Generate a payload for not-excluded routes + EXPORT_TIME (if generate.static = true)
[x] Crawl every dynamic pages (if generate.crawler = true)
[x] Handle Page.static = false or $nuxt.isPreview
[x] Force $route.query to be empty on SSR to mimic nuxt prerender

[ ] server: Expose a .nuxt/dist/server.js to start Nuxt in production with a script (ie: PM2, etc)

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[x] I have added tests to cover my changes (if not applicable, please state why)
[x] All new and existing tests are passing.

Codecov Report

Merging #6159 into dev will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##              dev   #6159      +/-   ##
=========================================
+ Coverage   95.75%   95.8%   +0.05%
=========================================
  Files          80      80
  Lines        2659    2667       +8
  Branches      682     686       +4
=========================================
+ Hits         2546    2555       +9
+ Misses         97      96       -1
  Partials       16      16

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.84% <38.09%> (-0.05%)
:arrow_down:

#unit
92.5% <100%> (+0.06%)
:arrow_up:

Impacted Files
Coverage Δ

packages/config/src/config/_common.js
100% <ø> (ø)
:arrow_up:

packages/generator/src/generator.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderers/spa.js
87.69% <100%> (ø)
:arrow_up:

packages/webpack/src/config/base.js
94.79% <100%> (+0.05%)
:arrow_up:

packages/config/src/options.js
100% <100%> (ø)
:arrow_up:

packages/webpack/src/builder.js
92.55% <100%> (ø)
:arrow_up:

packages/cli/src/commands/generate.js
91.3% <100%> (ø)
:arrow_up:

packages/builder/src/context/build.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
94.44% <100%> (+0.94%)
: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 95b2e6f...1dda5d8. Read the comment docs.

Codecov Report

Merging #6159 into dev will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##              dev   #6159      +/-   ##
=========================================
+ Coverage   95.75%   95.8%   +0.05%
=========================================
  Files          80      80
  Lines        2659    2667       +8
  Branches      682     686       +4
=========================================
+ Hits         2546    2555       +9
+ Misses         97      96       -1
  Partials       16      16

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.84% <38.09%> (-0.05%)
:arrow_down:

#unit
92.5% <100%> (+0.06%)
:arrow_up:

Impacted Files
Coverage Δ

packages/config/src/config/_common.js
100% <ø> (ø)
:arrow_up:

packages/generator/src/generator.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderers/spa.js
87.69% <100%> (ø)
:arrow_up:

packages/webpack/src/config/base.js
94.79% <100%> (+0.05%)
:arrow_up:

packages/config/src/options.js
100% <100%> (ø)
:arrow_up:

packages/webpack/src/builder.js
92.55% <100%> (ø)
:arrow_up:

packages/cli/src/commands/generate.js
91.3% <100%> (ø)
:arrow_up:

packages/builder/src/context/build.js
100% <100%> (ø)
:arrow_up:

packages/vue-renderer/src/renderer.js
94.44% <100%> (+0.94%)
: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 95b2e6f...1dda5d8. Read the comment docs.

This looks really interesting. One question. What is the difference between static and serverless?
As I understand new modes are more or less similar to the following:

generate spa= serverless
generate universal = static
build spa/universal =  server

Hey @husayt
Target is directly linked to the platform you want to host your Nuxt.js App, by default, it's server and is a normal node.js server with SSR.

server: Normal node.js hosting (Heroku, Amazon EC2, etc)
serverless: Serverless hosting (Now V2, AWS Lambda, Google Cloud Functions, etc)
static:  Static/CDN hosting (Netlify, GitHub Pages, Surge.sh, Amazon S3, etc)

As it is getting shape this is getting even cooler than anticipated.

Nice work!
It would be useful for me if it was possible to merge the payloads of every page corresponding to a certain dynamic route into a single file. The total data in my use case would be about 100 kB uncompressed (about 10 kB concatenated and compressed) and cover about 100 pages. Users are likely to navigate to many of the pages in a session, and each navigation involving the fetch of a <1 kB payload.json seems less preferrable than fetching  the whole database once when any one of the pages is accessed.
Maybe payload.json could be a key-value map with keys corresponding to the dynamic part of the route.
Additionally, would it be possible to generate a link rel="preload" corresponding to the payload file?
Thanks!

Hi @ion1
I understand this improvement but I don’t believe that it will scale nicely, some people have 10k dynamic pages and that would create a really big payload.
Regarding the rel=preload, it’s a good idea and I should add it for the payload.js which is added at the end of the body indeed :)

I completely agree merging payloads should not be the default, but it would be very nice if it was configurable for a dynamic route.

One thing that just came to my mind: Do we already handle the edge case that some pages are rendered through the SPA fallback (and that there shouldn't be payloads loaded but the actual asyncData function executed there instead)? ☺

I need to add a fallback when the payload is not found to not mock asyncData/fetch indeed, good one @manniL !

I need to add a fallback when the payload is not found to not mock asyncData/fetch indeed, good one @manniL !

Maybe we can restore the original asyncData function when fetching fails? ☺

Hi @Atinux , can you please provide an update on the status of this long awaited feature. It has been announced few times, but seems some problem is holding it up. Perhaps there is an issue we as a community can help with.
Alos, what will you suggest to use meanwhile as a replacement? There are some solutions which are partially doing this, like:
https://github.com/stursby/nuxt-static/
https://github.com/DreaMinder/nuxt-payload-extractor
https://github.com/pimlie/nuxt-lambda
and others
Thanks.

Something comes.. https://twitter.com/Atinux/status/1249385748874309633

Confirming with @Atinux and after team meeting:

PR status is fully ready now to be tested on edge
We need to add tests covering new functionalities later on before next release
We need to release docs before next release
created hook change for new fetch should be tested if introducing a breaking change or not (unwanted behaviour changed)
Some performance parts (including initial chunk) need to be tested against real projects to tune up

@Atinux @pi0
I found a bug in full static export:
If I switch routes it doesn't load the state for the new route.

Indeed @J05HI, this is not a bug but a specific behavior. We don’t want to save the state in each payload for performances but also the fact that replacing the whole state each time is not good.

@Atinux
Okay makes sense.
Is there a workaround for this? Or shouldn't I just use the store if I need full static?

You need to avoid using the store. Could you share and example of how and why you are using it?

@J05HI Actually you can use an anonymous middleware in order to dispatch actions to the store: https://nuxtjs.org/api/pages-middleware#anonymous-middleware
Keep in mind that they won’t be cached as full static though

@Atinux
https://github.com/J05HI/nuxtdoc
Take a look at this demo. I changed it to nuxt-edge and enabled static export.
At this line it tries to change the store through a mutation which doesn't work on static: https://github.com/J05HI/nuxtdoc/blob/a52bf35b17b5120100e7d41237e9351e246bed03/pages/_version/_category/_doc.vue#L41

@Atinux @pi0
I have a question/addition for the payload extraction.
Is it possible to extract and save only used data to payload.js? Would save a lot of data because you never need the whole api response.

@J05HI Well you only need to return the data you will use in asyncData :)

@Atinux
The solution is to filter out not needed data before returning.
Thank you very much for your help! Keep the good work!

@Atinux
I have another question.
Is there a way to rebuild only specific pages? If the api side content only changes for a specific page I would like to only export it, not all the others which stayed the same.

@pi0 @Atinux  Awesome! Really excited to use first party code for this.
What does this functionality cover in terms of asyncdata, fetch and nuxtserverinit? Will all data from those methods be included?

Woah, awesome. I'm really glad to deprecate my module in favor of native implementation. And since I've seen some edge cases, I'll be able to check them this week...
I have one concern so far: versioning. The native implementation uses timestamps to invalidate browser cache on every build. That's what I'm using for my module.
I noticed once that netlify builds are faster without payload-extractor because when enabled, netlify has to reupload all payloads to CDN from scratch. It would be ideal to upload only files that actually changed.
Do you see any way to use hashes on payload filenames instead of timestamps? I know, it may make builds slower and more CPU-intensive. And you wouldn't like to have additional hashing dependency, especially in nuxt-start. But still, maybe you have a better idea on how to solve it?
And answering @J05HI question:
You can implement it yourself using nuxt programmatically. Just override routes array before running generator.generate(), Or you could use one of the hooks to do the same.

I have one concern so far: versioning. The native implementation uses timestamps to invalidate browser cache on every build. That's what I'm using for my module.

About that what's the preferred workaround for this scenario? 🤔 (it existed before with a similar module as nuxt-payload-extractor, and from what I understand it still exists(?))

User is on the website
Website is regenerated & redeployed
User try to get to another existing page
Because site has been updated previous timestamped file is not available anymore and lead to 404 where there isn't a 404

@DreaMinder
Thank you very much! I'll try that.

@lihbr I think the best way to solve this issue is to use own deployment system that stores old static files along with new ones. Proper payloads versioning could help a little bit, but not in the case when user tries to open a page that has been updated.

@J05HI actually @pi0 implemented the store mutations when done in asyncData / fetch: https://github.com/nuxt/nuxt.js/pull/7350
This should fix your issue :)
@DreaMinder thank you again on your work for paylaod-extractor, it helped a lot shaping this feature!
Regarding versionning, I thought about it a lot, but the biggest issue is the ability to guess the filename when navigating on client-side, and if each payload file has different hash, this will be impossible without keeping a manifest file, but this one can become really big depending of how many routes you have in your application. We could consider such feature in the future as enhancements :)

@Atinux oh, right, I remember now. I tried to do it last year and stopped exactly because of this reason... and forgot about it. 😬
I think manifest-file solution is not that bad for most of the projects. And it's useful not only for storing payload hashes: I used a map of existing pages to check if a link is external in one of my projects. Also, it's useful for implementing breadcrumbs, overriding CMS-slugs (or IDs)... But it should be an option disabled by default, in case the manifest file becomes too big.

@DreaMinder I agree with you, I think I'll try to implement a way to do a hard reload if fetching payload fail once when this feature become available out of nuxt-edge, doing a hard reload here given the edge case seems decent to me :)

@Atinux @pi0 @DreaMinder
Are there any export hooks? Like generate hooks?
I would like to save all images in API responses to assets folder and replace the image URL with the local one. I need them locally to process them with webpack (Nuxt Optimized Images).

@Atinux

Are there any export hooks? Like generate hooks?
I would like to save all images in API responses to assets folder and replace the image URL with the local one. I need them locally to process them with webpack (Nuxt Optimized Images).

Are there any news for this?

@Atinux FYI many of projects I have are broken after trying them on this version. I probably need to pass some new parameters. But it would be even better if the new features work as before with previous configuration. Otherwise most of existing nuxt projects will be broken.
For example, SPA with all entry points generated after runnig this version doesn't have any of the other routes generated.

@husayt could you please provide me a reproduction? Nothing should break actually if you don’t specify the target: ‘static’

@Atinux I don't have to go far, even the spa example which comes with nuxt  breaks.
https://github.com/nuxt/nuxt.js/tree/dev/examples/spa
add  "generate": "nuxt generate", line to scripts, then  run generate. You will see about folder in dist.
Now switch to nuxt-edge and yarn run generate again. You will see there is no about folder in dist

@J05HI you can use the generate hooks, they are the same when using nuxt export actually (we just renamed to command to avoid breaking changes).
@husayt oh yes this is because it makes no sense to generate all the routes when using mode: 'spa' since you have the SPA fallback (200.html) to catch all the routes or you can directly link to index.html to catch all the routes.

@Atinux but still it breaks the previous behavior. Many used this to get SPAs with all entry points generated to have routes working on static websites. And what will be similar behavior in the new version?

@Atinux
Thank you very much for your reply!
I was confused of generate. Shouldn't we introduce separate export hooks? It would be much clearer.

@husayt you have valid point, will revert it :)
@J05HI indeed we are going to add export:* hooks as well as the export key (alias of generate)

@Atinux
Yeah, alias is the key ;)

@Atinux Thanks. Also to help with testing of this so much anticipated feature it would be great if there was some basic description of how this new mode works. What we have in description here is too little, I ended up breaking everything  and just gave up until it was clear how it all works.

At the moment you can learn more on https://www.notion.so/nuxt/Going-Full-Static-0633ab06d3d34d479947694d457a4817
Will publish it soon on the Nuxt blog

Hey @husayt
Target is directly linked to the platform you want to host your Nuxt.js App, by default, it's server and is a normal node.js server with SSR.

server: Normal node.js hosting (Heroku, Amazon EC2, etc)
serverless: Serverless hosting (Now V2, AWS Lambda, Google Cloud Functions, etc)
static:  Static/CDN hosting (Netlify, GitHub Pages, Surge.sh, Amazon S3, etc)

They mainly differs when running nuxt build, so Nuxt.js knows what kind of hosting platform you are aiming at :)

@atinux thanks for the link to documentation, that helped, but also created a number of questions. I am confused also probably because of changing scope for this feature.
Here is a reply from you last year where you mentioned serverless mode, but seems that now it is being dropped.
So as I understand we have these modes :

server: Normal node.js hosting (Heroku, Amazon EC2, etc)
with target:server and commands  npm run build and then npm run start
static:  Static/CDN hosting (Netlify, GitHub Pages, Surge.sh, Amazon S3, etc)
with target:static and commands  npm run build and then npm run export

And both of them have modes universal/SPA.
Also we still have nuxt generate which as I understand does npm run build and  npm run export as one step.
Now we have a combination of  two settings target (server/static) and mode(spa/universal), we have
*build-start-server/spa
*build-start-server/universal
*build-export-static/spa
*build-export-static/universal
What about generate, is it being deprecated or is it going to stay?
I am probably confused becaused I think in old terms, but I guess there will be a lot of similar questions.

@husayt thank you for your feedback

What about generate, is it being deprecated or is it going to stay?

We plan to deprecate it yes, but because we want to add full static for 2.13, we cannot add a breaking change, so it will be deprecated and removed for Nuxt 3.

Hey,
I am using<EMAIL_ADDRESS>and I am trying to use the full static version which is working for me.  I am using it in the conjunction with the nuxt-community/apollo-module. Shouldn't it just reuse the payload from the generated page?
This is my AppNavbar.vue (script part) for example:
  apollo: {
    navigation: {
      prefetch: true,
      fetchPolicy: 'cache-and-network',
      query: navigationQuery,
    },
  },

Hi @SvenC56
Actually the full static only mock fetch and asyncData, Apollo is used outside of it actually, I can see quickly how I can support it but may be tricky

full static only mock fetch and asyncData

Thanks to this hint I adapted my config the following (same example as above https://github.com/nuxt/nuxt.js/pull/6159#issuecomment-632768070):
async fetch() {
    const response = await this.$apolloProvider.defaultClient.query({
      query: navigationQuery,
    })
    this.navigation = response.data.navigation
  },

  fetchOnServer: true,

Now the data is rendered serverside and it does not reach out to my API anymore. :slightly_smiling_face:

Hey all! First of all thanks for the work you're doing on this :)
I finally managed to get full static generation where all I have to do is upload the dist folder on Netlify and everything works right away, payload and assets included.
Right now I'm still using a little hack to add a generate:staticAssets hook to grab the image links and replace them with local versions before saving the json payloads (as discussed here). I wanted to ask the Nuxt team if it's possible to include a hook to modify the payload before it goes through @nuxt/devalue, or if you guys have some better ideas on how to handle this case - I tried to look around the code but I'm still a bit lost on how everything works under the hood.

Hi! Thanks for all the hard work everyone. This is indeed a great feature. I'm wondering if the generate route+payload feature has been removed?
export: {
  routes (): {
     return [{
       route: '/',
       payload: pageData
     }]
  }
}

I'm asking because I'm using Sanity CMS as backend and they have a price cap on the number of API calls we make. So, I would like to be able to be able to grab all the page data in one call and feed it to all the pages, instead of making API calls per page on each deploy or content change.
I did some testing with the classic generate route+payload feature just now using<EMAIL_ADDRESS>I'm calling npx nuxt build && npx nuxt export. And it doesn't seem to use my pre-generated route payloads.
Might be bugs in my code off course. Nonetheless, it would be great to hear if generating data for all pages in one action is still supported?
Thanks. 🙏
cc: @Atinux

Literally just came to as the same thing as @nilsnh :)

Hi Team,
I am trying this static generation. I see Lot of 404 on my console whenever subpage has slug which has space in it.
open chrome inspect/devtools
go to homepage - https://cscom-2019.web.app
you can see many errors.
Here subpage is category. Any category which has a space(%20) in its name is giving 404 error on console for its payload.js.
One more scenario:
Single page - https://cscom-2019.web.app/aloo-puri-recipe-crispy-yet-soft-masala-potato-poori-cookingshooking
This post is linked to 6 categories, apart from one category rest 5 categories payload.js throws 404 error.
Please let me know if you need more details on the same.

Ok I have planned to change my backend data for categories list.
But now I am stuck with querying :(
how can i look for slug = 'ABC' in the below categories list/array
categories = [ {'slug':'123', category:'1 2 3'}, {'slug':'ABC', category:'A B C'}, {'slug':'XYZ', category:'X Y Z'}]
qry = this.$content().where({  categories: { $contains : 'How To Manage Slug Here'  }  })
Earlier I had categories as below, only values
categories = ['A B C', '1 2 3', 'X Y Z']
and my query was as below
qry = this.$content().where({  categories: { $contains :  'A B C'  }  })

@rajesh-h Would you please kindly report this issue to nuxt/content and possibility with proper repro?
I will also try to reproduce and check the issue you mentioned about spaces :)

Thank you @pi0. looks like json/netsed filter is not possible based on comments on this issue.
If space issue is resolved, I can go back to my original design where keeping categories array as simple list. Please let me know if you want any input for the space issue.
Thank you very much.

Hello,
Thank you so much for the static generation mode, I'm trying it through nuxt-edge, great job from the team !
I stumbled upon a weird flash between route changes. The error page appears for a brief time, and displays a resolveRouteComponents is not defined message.
In dev mode, it happens on each route change.
In production mode (after nuxt build && nuxt export && nuxt serve) it does not happen between generated routes anymore, but still for fallback routes that are excluded from the static generation (the /profil route for example).
In both modes, the route loads after the flash. Did you encouter this behaviour before ?
Thank you !

@rajesh-h Would you please kindly report this issue to nuxt/content and with proper repro?
I will also try to reproduce and check the issue you mentioned about spaces :)

@pi0 I am not sure its the issue with space :( .
I removed the space on my category names still find the 404 error.
When you go down at this link - https://cscom-2019.web.app/category/cakes-more when more posts are getting loaded you will see lot of 404 for payload.js
this behavior not observed on homepage. https://cscom-2019.web.app you can keep going down and load posts.
Both have the same structure like load 10 posts initially then load further posts when you scroll down. Any lead to resolve this will be helpful.
In case you want to refer:
My Github Repo is here
SandBox - Here
Side Question: Does the static site removes that nice animation of horizontal line page loading on top when you click on a link?

Pages with pagination navigations with this "full-static" feature don't work by the way. I assume that it is a bug. The pagination works fine with Nuxt 2.12.2.

@rajesh-h Would you please kindly report this issue to nuxt/content and with proper repro?
I will also try to reproduce and check the issue you mentioned about spaces :)

@pi0 I am not sure its the issue with space :( .
I removed the space on my category names still find the 404 error.
When you go down at this link - https://cscom-2019.web.app/category/cakes-more when more posts are getting loaded you will see lot of 404 for payload.js
this behavior not observed on homepage. https://cscom-2019.web.app you can keep going down and load posts.
Both have the same structure like load 10 posts initially then load further posts when you scroll down. Any lead to resolve this will be helpful.
In case you want to refer:
My Github Repo is here
SandBox - Here
Side Question: Does the static site removes that nice animation of horizontal line page loading on top when you click on a link?

@pi0 did you happen to see what might be causing 404 errors? any lead would be helpful. Functionally no problem, just that too much error on console.

I am eager to test this out, but I have two questions:

Will it work on a e-commerce platform with roughly 5-6000 routes with payload? Perhaps increase generate time a lot, or something else?

Will it work with Vuex? In my asyncData I do like so:
async asyncData ({ store, app, error, route, payload }) {
if (payload) {
store.dispatch('product/set', payload);
return;
}

@Atinux GREAT work! Seems to work out of the box. Even with routes which are meant to be fetched from server. Page switching is waay faster now.
However, I noticed my og:description is now "undefined". I am not sure if it is related to this pull through. I set og:description to process.env.npm_package_description. Has anything changed with this? @pi0

One question though @Atinux. I am curious, will this have any inital page speed / load time issues?
How is the implementation done exactly?
I really love the feature, and how fast it now switches pages, but we have a e-commerce platform with 5-6000 routes, so I am curious if this amount of pages will slow down initial page load speed.
You can check here https://beta.thejewelleryroom.com vs https://thejewelleryroom.com

Hello,
Thank you so much for the static generation mode, I'm trying it through nuxt-edge, great job from the team !
I stumbled upon a weird flash between route changes. The error page appears for a brief time, and displays a resolveRouteComponents is not defined message.
In dev mode, it happens on each route change.
In production mode (after nuxt build && nuxt export && nuxt serve) it does not happen between generated routes anymore, but still for fallback routes that are excluded from the static generation (the /profil route for example).
In both modes, the route loads after the flash. Did you encouter this behaviour before ?
Thank you !
EDIT: I was toying around the options. The weird flash only happened when I had loading: false in my nuxt config, I removed it and it is now working perfectly. I'm just leaving this message here in case someone finds themself in the same situation !

Same issue over here, the following error flashes by when changing routes however no error is logged to the console.
resolveRouteComponents is not defined
An error occurred while rendering the page. Check developer tools console for details.

I have it in dev and production mode.

I'm finding a funny issue: Routes that return a 404 error still get statically rendered when using nuxt export. Shouldn't this halt the rendering and leave it to the fallback strategy?

I'm finding a funny issue: Routes that return a 404 error still get statically rendered when using nuxt export. Shouldn't this halt the rendering and leave it to the fallback strategy?

Why would you generate a route that returns 404?

I'm finding a funny issue: Routes that return a 404 error still get statically rendered when using nuxt export. Shouldn't this halt the rendering and leave it to the fallback strategy?

Why would you generate a route that returns 404?

It's kind of a bug in my code (related to i18n and missing translated documents), but I can see some scenarios where the crawler can get confused and try to render a route that returns an error state - like, say, a route that comes from user input. Shouldn't Nuxt avoid statically rendering these routes and instead let the client-side code pick it up? Or, at least, shouldn't it statically render a 404 page? Right now it just falls back to the static SPA version of the page, which doesn't add much value. Funny enough; if you raise an exception, then the route doesn't get rendered (which is how I ultimately did the trick on my scenario).
In any case, this is such a neat feature and I'm enjoying it so much!

Normally if the crawler hits a page that render a 404, it will render the page with no ssr to let the client-side falling back

@Atinux I want to host the app in was s3, but still want to load data from my API for the dynamic routes. is there a to disable reading the payload.js and read the API response ? I can exclude the dynamic routes, but was s3 will return it as 404 status and can impact the Google indexing


kubernetes etcd

I am runubg etcd in  kubernets cluster  as petset.
When one etcd POD goes down,  petset automatically creates  POD.
So new pod has empty  data dir ..But i  see logs .. new pod (etcd node) is trying to  join cluster with  same member  id 2d38ede45015dfb6
How you guys generate member id.. why  it is same..  when new node.pod comes,  it uses same etcd name.. Does it matter?
Any help  really appreciate
2017-01-25 23:18:46.336883 W | rafthttp: health check for peer 2d38ede45015dfb6 failed
2017-01-25 23:19:16.337090 W | rafthttp: health check for peer 2d38ede45015dfb6 failed
2017-01-25 23:19:22.612428 I | membership: removed member 2d38ede45015dfb6 from cluster c897f11da038da78
2017-01-25 23:19:22.612453 I | rafthttp: stopping peer 2d38ede45015dfb6...
2017-01-25 23:19:22.612475 I | rafthttp: stopped streaming with peer 2d38ede45015dfb6 (writer)
2017-01-25 23:19:22.612493 I | rafthttp: stopped streaming with peer 2d38ede45015dfb6 (writer)
2017-01-25 23:19:22.612519 I | rafthttp: stopped HTTP pipelining with peer 2d38ede45015dfb6
2017-01-25 23:19:22.612549 I | rafthttp: stopped streaming with peer 2d38ede45015dfb6 (stream MsgApp v2 reader)
2017-01-25 23:19:22.612625 I | rafthttp: stopped streaming with peer 2d38ede45015dfb6 (stream Message reader)
2017-01-25 23:19:22.612656 I | rafthttp: stopped peer 2d38ede45015dfb6
2017-01-25 23:19:22.612683 I | rafthttp: removed peer 2d38ede45015dfb6
2017-01-25 23:19:56.752086 W | rafthttp: rejected the stream from peer 2d38ede45015dfb6 since it was removed
2017-01-25 23:19:56.752174 W | rafthttp: rejected the stream from peer 2d38ede45015dfb6 since it was removed
2017-01-25 23:31:38.998958 I | etcdserver: start to snapshot (applied: 330050, lastsnap: 320049)

Please try etcd-operator (https://github.com/coreos/etcd-operator) for running etcd on Kubernetes.

This doesn't solve the problem... This looks like POC..
You can use kubernetes petset  feature to  build a etcd cluster. We are in production and it worked fine till one node/ pod went down. There is no easy way we are able to add the node back.
Our question is  why we are always getting  same member id "2d38ede45015dfb6". One  pod is down .. we remove the node. Now new pod come up and we are expecting new member id...
which is not the case. It came back with same member id "2d38ede45015dfb6"
2017-01-25 23:19:56.752174 W | rafthttp: rejected the stream from peer 2d38ede45015dfb6 since it was removed
Why new node / pod is coming up  with same member id? what algorithm is being used to create this member  id?
Thanks
~Suchi

This looks like POC..

No. It is not a POC.

We are in production and it worked fine till one node/ pod went down. There is no easy way we are able to add the node back.

That is why you need etcd operator. There is no magic in petset. It does not understand etcd at all.
In another word, petset wont manage etcd for you.
You need to read https://github.com/coreos/etcd/blob/master/Documentation/op-guide/runtime-configuration.md#replace-a-failed-machine to manage etcd manually on Kubernetes.

@suchisubhra it's determined based on the command line arguments. Removing a node from etcd by just deleting the data directory and then expecting it to join as a new member is not how etcd works. Membership must be managed through etcdctl or, like @xiang90 suggested, through etcd-operator.

I have removed the node thr curl command curl  http://dns2379/v2/members/2d38ede45015dfb6 -XDELETE
and then re-create the pod.. which means it is new node.. New pod/node is trying to join the cluster.
and then i am getting this error.
017-01-25 23:19:56.752086 W | rafthttp: rejected the stream from peer 2d38ede45015dfb6 since it was removed
2017-01-25 23:19:56.752174 W | rafthttp: rejected the stream from peer 2d38ede45015dfb6 since it was removed
Why new node/ pod got same member id?

@suchisubhra You probably use Kuberentes with PV. Your new pod probably attaches the old data dir from that PV.

Xiang,
No I don't use PV.
Yes we use manual / script to  remove the crashed node.
Then new pod/ node come and try to join the cluster.  All  seems good till peer finds out new node/pod has same member id (which we have removed thr script) and declined to add it the cluster.
How we can generate a new member id every time?

Then new pod/ node come and try to join the cluster.

how does it try?

we start etcd (/usr/lical/bin/etcd ) process in the node/pod...
For reference here is env variable in all the node/pods
{
"name": "ETCD_INITIAL_CLUSTER",
"value": "etcd-0=http://etcd-0.DNS:2380,etcd-1=http://etcd-1.DNS:2380,etcd-2=http://etcd-2.DNS:2380"
},
{
"name": "ETCD_INITIAL_ADVERTISE_PEER_URLS",
"value": "http://$(ETCD_NAME).DNS:2380"
},
{
"name": "ETCD_LISTEN_PEER_URLS",
"value": "http://$(POD_IP):2380"
},
{
"name": "ETCD_LISTEN_CLIENT_URLS",
"value": "http://$(POD_IP):2379"
},
{
"name": "ETCD_ADVERTISE_CLIENT_URLS",
"value": "http://$(ETCD_NAME).DNS:2379"
}
This works perfectly if we delete petset  and start from  scratch... WE are hoping if one pod/ node goes down,  after removing if we start pod/node etcd,  it should join  back the cluster.

@suchisubhra

WE are hoping if one pod/ node goes down, after removing if we start pod/node etcd, it should join back the cluster.

As we told you, it wont. Please read what @heyitsanthony and I just told you: https://github.com/coreos/etcd/blob/master/Documentation/op-guide/runtime-configuration.md#replace-a-failed-machine.
Or we cannot really help you further. The doc explains it much better than we could do here in the issue in short time.

Thanks for all  your help .. I really appreciate that.. I think I know the issue.. I will try tomorrow morning and let you guys know..
adding "etcd restart" would be a great feature ....


In each test, run gpufit and cpufit and compare results

Currently it's only done in one. However I think it makes sense to do it every time.

It also makes sense so I can debug the algorithm easier. Debugging on the GPU might be a bit more complicated.

I do that now in 3a6395222416932f739db561a328c423676c2921 in the consistency tests calls cpufit and gpufit on the same input data and compares the outputs of both. I will include more of the other tests in this consistency test later and then close this.


Upgrade to AGP 7

Upgrade the project to use AGP 7

I also needed to upgrade dokka and detekt plugins, since the old versions were broken


Create Release files for those of us that cant compile Yolo_mark

Hi there, would be nice to have some installer or just a portable executable file for both linux and windows for those of us who cant compile Yolo_mark, in my case I need a windows compiled version and cant manage to compile Yolo_mark because of opencv.

I use openCV 3.4.0. It will help you


terminate_server only release memory on one gpu when using tensor_parallel

I am trying to use two GPUs with tensor_parallel=2. It seems it only releases memory on one gpu. There is some process still running. The client.terminate_server doesn't seem to kill all processes.  I can kill the process manually, but how can I do it properly in the python code?
import mii

client = mii.serve("mistralai/Mistral-7B-v0.1",
                   deployment_name="ray_scorer_deployment",
                   tensor_parallel=2)
response = client.generate("Deepspeed is", max_new_tokens=128)
client.terminate_server()

print(response.response)

This was a bug that has been fixed in #262. Please update to the latest main (we will also do a patch release with this and other bug fixes later this week).

Closing, this was resolved in the latest release (v0.1.1).


Re-store usize::MAX when CellRef::try_clone fails.

Heya @zakarumych, is it correct now?
GitHub doesn't let me add yourself to the Reviewers

Sorry, but no.
It's has two issues now.
First is that overflow still occurs. Even briefly, there can be unbounded time window where another thread can observe 0 counter.
Second is that increments and decrements are not balanced.
When one thread may overflow counter, other threads can decrement on release. Then overflowing thread would overwrite it with usize::MAX. In this case counter will never reach 0 after all borrows are released.

Got it, I've tried using fetch_update which does a compare_swap under the hood, but to be honest the reordering concept is really difficult to understand.

This should work.
But, tbh, I'd make it differently.
For all practical cases fetch_add(1) should work just fine. It only gets problematic if counter overflows.
Let's assume that each thread occupies at least 2 bytes in memory.
Than we can safely conclude that there can't be more than isize::MAX concurrent threads accessing the counter.
Similarly, there can't be more than isize::MAX clones of the reference without leaks, so limiting counter at isize::MAX should be OK.
Now we can safely do fetch_add(1) by keeping counter under isize::MAX. If thread increments the counter and it was isize::MAX or greater - then thread should fetch_sub(1) to balance counter and return an error.
In practice this will only happen when clones are leaking in a loop. So marking this branch as unlikely would be correct.
And that's it. Hot-path is optimized to single fetch_add(1).
P.S. Increment can be done with Relaxed ordering, since no other operations should be synchronized around the atomic.

cool, I think I've implemented the above, please could you verify?

heya, all good now?

Looks good to me :)

Oh no, we forgot to fix it in check_flag_read

oh ya, nice catch :eyes:


QUIC: Hidden more pp_key_info detail in QUICContext

It is not necessary to explore all pp_key_info to context. So hidden it into context.

I may want to call it QUICPacketProtectionKeyStateProvider, if we only provide the two functions but not actual key information (keys, lengths, etc.).

Also, I'm still not sure if the two are enough. After we implement key update, we might need something else.

Hi @maskit

I'm still not sure if the two are enough. After we implement key update, we might need something else.

Adds more read only method into QUICPacketProtectionProvider.

I may want to call it QUICPacketProtectionKeyStateProvider, if we only provide the two functions but not actual key information (keys, lengths, etc.).

Not sure I need to change name or not.

I'm ok with this change but I don't understand the motivation.
For access control, we could also return const QUICPacketProtectionKeyInfo * from QUICContextImpl::key_info() const.
I remember you were talking about abstraction, but what issue does it solve?

I may want to call it QUICPacketProtectionKeyStateProvider, if we only provide the two functions but not actual key information (keys, lengths, etc.).

Not sure whether I need to change name or not.

I'm fine with the current name is it also provides actual keys.

For access control, we could also return const QUICPacketProtectionKeyInfo * from QUICContextImpl::key_info() const.

It is also fine to me .  I just want to make all params in context are read only. So when I use it as the QUICFrameGenerator's base params. It will not break anything up but only provide information. Also add an abstraction is clearer for someone which method can be used in this class.
The reason I need to  add context into QUICFrameGenerator is reenable the QUIC write event. I tested the quic performance recently. It seems the quic always blocked by flow control. So the max_xxx_data frame must be blocked by some reason.


Prevent crashes for per values ≤ 0

This PR quickly fixes a bug in which the Pagination library crashes the entire server due to division by zero.

@Cellane Thank you for this! I never checked that value. Will get this merged and tagged now.


How to add chinese font for v1.4.1

I added all these to my var doc = new jsPDF();
addFileToVFS('SimSun.ttf'
addFont('SimSun.ttf'
setFont
however it still cant display chinese char. Anyone can help? thanks

@MrRio 需要告知如何使用

janjon
Pls. answer in english!.
I'm stuck with the same problem! Can anyone help?

i solved it by using TCPDF, it support chinese character

The TCPDF is a backend (PHP) solution. I'm looking forward seeing a solution for this jspdf library. I've tried using sphilees fork of this code, but could not get the chinese fonts working there either.
I've converted to vfs files with makeFonts.js several chineese .ttf fonts without success.
I've tried simhei.ttf, SIMSUN.ttf, and wts11.ttf.
Any other suggestions?

I will work to get the ttf support right.
Duplicate of #1902


GitHub Actions: ubuntu-latest no longer supports Python 3.6

https://github.com/actions/setup-python/issues/544#issuecomment-1332535877
This failure is blocking other pull requests:

https://github.com/Ousret/charset_normalizer/pulls

The alternative would be to drop Python 3.6 which is no longer supported:

https://devguide.python.org/versions

Thank you for the submission, unfortunately :
(i) I'd rather stop supporting Python 3.6.
(ii) There are many more GHA workflow files
(iii) security-wise, I'd be more comfortable with maintained GHA images
(iv) scheduled for the next minor 3.1
PR are accepted.


ARROW-10719: [C#] ArrowStreamWriter doesn't write schema metadata

Add support for reading and writing Schema and Field metadata
Also, reducing some allocations in a few spots.
Tagging people who have contributed to the C# library in the past year for review. (Feel free to ignore if you don't have time.)
@pgovind @suhsteve @chutchinson @Ulimo @mr-smidge @zgramana @HashidaTKS @nhustler
cc @olgacarpenter

LGTM, it was just the constructors that confused me a bit.

LGTM 2

assuming TestRoundTripRecordBatch actually tests the metadata for equality

Yes, it does here:
https://github.com/apache/arrow/blob/cbb1ed5d39f16189992298a2f8db21a325321d0b/csharp/test/Apache.Arrow.Tests/SchemaComparer.cs#L30-L36
https://github.com/apache/arrow/blob/cbb1ed5d39f16189992298a2f8db21a325321d0b/csharp/test/Apache.Arrow.Tests/FieldComparer.cs#L34-L39


Propose an FAQ

I've added a question for LF @aalmiray, let me know what you think

Thanks for the comments @gavinking, I've made the suggested changes

Great, thank you all!


Rspec 3.3.3 support

Bundler could not find compatible versions for gem "rspec-support":
  In snapshot (Gemfile.lock):
    rspec-support (= 3.2.2)

  In Gemfile:
    fuubar (= 2.0.0) ruby depends on
      rspec (~> 3.0) ruby depends on
        rspec-core (~> 3.2.0) ruby depends on
          rspec-support (~> 3.2.0) ruby

    fuubar (= 2.0.0) ruby depends on
      rspec (~> 3.0) ruby depends on
        rspec-core (~> 3.2.0) ruby depends on
          rspec-support (~> 3.2.0) ruby

    fuubar (= 2.0.0) ruby depends on
      rspec (~> 3.0) ruby depends on
        rspec-core (~> 3.2.0) ruby depends on
          rspec-support (~> 3.2.0) ruby

    rspec-rails (= 3.3.3) ruby depends on
      rspec-support (~> 3.3.0) ruby

@oswaldoferreira I had this issue when I was trying to upgrade the rspec-rails gem from 3.2 to 3.3 using bundle update rspec-rails. I was able to deal with it by updating the rspec gem along with the rspec-rails gem as well (bundle update rspec rspec-rails)


Flipping for background mistakes percentages in color functions for background-position

Consider the following definition:
background: hsl(150 30% 30%);

The percent values are about the saturation and lightness of the generated color and are unrelated to directions.
Yet, when passing it through CSSJanus you get:
background: hsl(150 70% 30%);

which is totally wrong.
Another example:
background: color-mix(in srgb, red 30%, blue);

turns into
background: color-mix(in srgb, red 70%, blue);

The root cause is probably this regex which tries to capture background-position values out of the background shorthand property.

(As a side note, I'm not sure how this is even supposed to work well for actual position values, considering that the default alignment direction is still "left". For example,
background-position: 30%;

turns into
background-position: 70%;

which seems off)

@HumansCanWinElves Thanks for filing this bug. Looks like this is specific to the new space-separated color functions, which CSSJanus does not yet know about.

@Krinkle the issue is the same with the old comma-separated syntax.

@Krinkle I'm not requesting a fix or anything of the sort, but can you please just correct the misleading title of the issue. It's clearly not about the space-separated syntax as it happens the same with the comma-separated syntax:
background: hsl(150, 30%, 30%);

becomes
background: hsl(150, 70%, 30%);

@Krinkle Hello I want to work on this issue, the code where the issue is occurring has been identified.

@AbhineetSaha It looks like code changes must be pushed to their Gerrit repository as this is a read-only mirror


All jars missing from maven central

It appears all jars for this library have disappeared form maven central. com.llamalad7 no longer exists.
https://repo.maven.apache.org/maven2/com/llamalad7
(base) gamebuster@database:~/Desktop/wildermyth/WilderForge$ ./gradlew build
> Task :compileJava FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileJava'.
> Could not resolve all files for configuration ':compileClasspath'.
   > Could not find com.llamalad7:MixinExtras:0.4.0.
     Searched in the following locations:
       - file:/home/gamebuster/.m2/repository/com/llamalad7/MixinExtras/0.4.0/MixinExtras-0.4.0.pom
       - https://repo.maven.apache.org/maven2/com/llamalad7/MixinExtras/0.4.0/MixinExtras-0.4.0.pom
       - https://repo.spongepowered.org/maven/com/llamalad7/MixinExtras/0.4.0/MixinExtras-0.4.0.pom
       - https://maven.fabricmc.net/com/llamalad7/MixinExtras/0.4.0/MixinExtras-0.4.0.pom
     Required by:
         project :

You are looking at the wrong groupid, it's io.github.llamalad7:mixinextras-common, see https://mvnrepository.com/artifact/io.github.llamalad7
For reference, MavenCentral never pulls any artifacts unless something truly spectacular happened (probably legal stuff first and foremost)


SVG position rendered incorrectly

With this SVG input,
<svg>     <g>         <rect x="79" y="15" width="170" height="25" style="fill:ivory;"></rect>     </g> </svg>
The output looks like this,

The output doesn't seem to account for the x and y positions and ends up cutoff.

Hello, you'll need to add specific dimension attributes to the <svg> element, either both a width and height or a viewBox. Without these the underlying librsvg library is having to guess the desired canvas size.
const svg = Buffer.from('<svg width="249" height="40"> <g> <rect x="79" y="15" width="170" height="25" style="fill:ivory;"></rect> </g> </svg>');
sharp(svg).toFile('out.png', console.log);

null { format: 'png',
  width: 249,
  height: 40,
  channels: 4,
  premultiplied: false,
  size: 209 } null

Hope this helped, please feel free to re-open with more details if required.

Setting the width and height properties did fix it. However, it did not work if just viewBox was set. Thanks!


More hooks...

I was just curious why there aren't more hooks available for this? I don't currently have any particular reason for any specific additional hooks, but it just seems odd that you limited the set. For example, why not post-commit?

No specific reason… When I wrote this module, I got all the default .sample hooks that git provided and used them as a starting point. Adding new hooks is very straight forward (check this PR out https://github.com/gtramontina/ghooks/pull/12), and I'd welcome new additions :wink: :+1:

I'm closing this one. I've just added  so we can have these questions answered there.


Trinity log output: reorder, align

What was wrong?
Logging output is somewhat hard to read:
DEBUG root 2018-05-18 18:29:05,034 - Logging initialized
INFO p2p.server.Server 2018-05-18 18:29:05,067 - Running server...
INFO p2p.server.Server 2018-05-18 18:29:10,073 - No UPNP-enabled devices found
INFO p2p.server.Server 2018-05-18 18:29:10,074 - enode://bdd67f995510d373497248f62f05c5260dc5e5240df95863e3c4963a32090313420ead08c10173bf18039e713cbceaf4c7223a3089a98692fb4814829f169430@<IP_ADDRESS>:30303
DEBUG p2p.discovery.DiscoveryProtocol 2018-05-18 18:29:10,122 - boostrapping with [<Node(0x30b7@<IP_ADDRESS>)>]
INFO p2p.peer.PeerPool 2018-05-18 18:29:10,125 - Running PeerPool...
DEBUG p2p.peer.PeerPool 2018-05-18 18:29:10,125 - Last node discovery lookup too long ago, triggering another
DEBUG p2p.peer.PeerPool 2018-05-18 18:29:10,128 - Connecting to <Node(0x0250@<IP_ADDRESS>)>...
DEBUG p2p.discovery.DiscoveryProtocol 2018-05-18 18:29:10,181 - >>> ping <Node(0x30b7@<IP_ADDRESS>)> (token == 0x16bc62851fdc06810c8d7b94b5318e555e5bd5630b42f96702cf141523519fb8)
DEBUG p2p.discovery.KademliaProtocol 2018-05-18 18:29:10,324 - <<< pong from <Node(0x30b7@<IP_ADDRESS>)> (token == 0x16bc62851fdc06810c8d7b94b5318e555e5bd5630b42f96702cf141523519fb8)
DEBUG p2p.discovery.KademliaProtocol 2018-05-18 18:29:10,325 - got expected pong with token 0x16bc62851fdc06810c8d7b94b5318e555e5bd5630b42f96702cf141523519fb8
INFO p2p.sync.FullNodeSyncer 2018-05-18 18:29:10,871 - Starting fast-sync; current head: #0

How was it fixed?
The formatting string was changed to have time first, and char-limit the level to 8 chars (which matches the char count in CRITICAL):
2018-05-18 18:30:52,908    DEBUG root - Logging initialized
2018-05-18 18:30:52,941     INFO p2p.server.Server - Running server...
2018-05-18 18:30:57,947     INFO p2p.server.Server - No UPNP-enabled devices found
2018-05-18 18:30:57,949     INFO p2p.server.Server - enode://bdd67f995510d373497248f62f05c5260dc5e5240df95863e3c4963a32090313420ead08c10173bf18039e713cbceaf4c7223a3089a98692fb4814829f169430@<IP_ADDRESS>:30303
2018-05-18 18:30:57,992    DEBUG p2p.discovery.DiscoveryProtocol - boostrapping with [<Node(0x30b7@<IP_ADDRESS>)>]
2018-05-18 18:30:57,994     INFO p2p.peer.PeerPool - Running PeerPool...
2018-05-18 18:30:57,994    DEBUG p2p.peer.PeerPool - Last node discovery lookup too long ago, triggering another
2018-05-18 18:30:57,996    DEBUG p2p.peer.PeerPool - Connecting to <Node(0x0250@<IP_ADDRESS>)>...
2018-05-18 18:30:58,054    DEBUG p2p.discovery.DiscoveryProtocol - >>> ping <Node(0x30b7@<IP_ADDRESS>)> (token == 0x41b2d2fd37000511507fe4b7000155628d0922ffba10836529afb7f4a7be7bf3)
2018-05-18 18:30:58,197    DEBUG p2p.discovery.KademliaProtocol - <<< pong from <Node(0x30b7@<IP_ADDRESS>)> (token == 0x41b2d2fd37000511507fe4b7000155628d0922ffba10836529afb7f4a7be7bf3)
2018-05-18 18:30:58,198    DEBUG p2p.discovery.KademliaProtocol - got expected pong with token 0x41b2d2fd37000511507fe4b7000155628d0922ffba10836529afb7f4a7be7bf3
2018-05-18 18:30:58,738     INFO p2p.sync.FullNodeSyncer - Starting fast-sync; current head: #0

This also makes it easier to remove the timestamp without code modifications (e.g. if running with systemd, which already includes a timestamp).
Cute Animal Picture

(Source unknown, found here)

@veox
Thoughts on moving to something closer to the geth terminal output format.

level as leftmost element.
drop year from timestamp
drop millisecond from timestamp
drop logger path from log message (which we might want to be able to re-enable with a flag???)

DEBUG    05-18 18:30:52  Logging initialized

After too much fiddling for this much result, I got to:
   DEBUG  05-18 22:29:59    logging  Logging initialized
    INFO  05-18 22:29:59     server  Running server...
    INFO  05-18 22:30:04     server  No UPNP-enabled devices found
    INFO  05-18 22:30:04     server  enode://fbeaded3e994f9c4c2a24165b256f22b99be4831a5df6ef97f2624ada4375bc159fd08389f663ff5f3b61fb782a16e3206881f85e94f75e3ad7d3d99650df5c2@<IP_ADDRESS>:30303
   DEBUG  05-18 22:30:04  discovery  boostrapping with [<Node(0x30b7@<IP_ADDRESS>)>]
    INFO  05-18 22:30:04       peer  Running PeerPool...
   DEBUG  05-18 22:30:04       peer  Last node discovery lookup too long ago, triggering another
   DEBUG  05-18 22:30:04       peer  Connecting to <Node(0x0250@<IP_ADDRESS>)>...
   DEBUG  05-18 22:30:04  discovery  >>> ping <Node(0x30b7@<IP_ADDRESS>)> (token == 0x0cb234542b1b5f98f6886bf01f08b727454b7370827b3627f299def362fd8314)
   DEBUG  05-18 22:30:05   kademlia  <<< pong from <Node(0x30b7@<IP_ADDRESS>)> (token == 0x0cb234542b1b5f98f6886bf01f08b727454b7370827b3627f299def362fd8314)
   DEBUG  05-18 22:30:05   kademlia  got expected pong with token 0x0cb234542b1b5f98f6886bf01f08b727454b7370827b3627f299def362fd8314
    INFO  05-18 22:30:05       sync  Starting fast-sync; current head: #0
   DEBUG  05-18 22:30:05   kademlia  timed out waiting for ping from <Node(0x30b7@<IP_ADDRESS>)>
   DEBUG  05-18 22:30:05   kademlia  bonding completed successfully with <Node(0x30b7@<IP_ADDRESS>)>
   DEBUG  05-18 22:30:05   kademlia  starting lookup; initial neighbours: [<Node(0x30b7@<IP_ADDRESS>)>]
   DEBUG  05-18 22:30:05   kademlia  node lookup; querying [<Node(0x30b7@<IP_ADDRESS>)>]
   DEBUG  05-18 22:30:05  discovery  >>> find_node to <Node(0x30b7@<IP_ADDRESS>)>
   DEBUG  05-18 22:30:06   kademlia  <<< neighbours from <Node(0x30b7@<IP_ADDRESS>)>: [<Node(0xb6f9@<IP_ADDRESS>)>, <Node(0x239c@<IP_ADDRESS>)>, <Node(0x1cbb@<IP_ADDRESS>)>, <Node(0x7ed8@<IP_ADDRESS>)>, <Node(0x4974@<IP_ADDRESS>)>, <Node(0x01c7@<IP_ADDRESS>)>, <Node(0x545e@<IP_ADDRESS>)>, <Node(0x4a08@<IP_ADDRESS>)>, <Node(0xac6b@<IP_ADDRESS>)>, <Node(0x1a7e@<IP_ADDRESS>)>, <Node(0xf37d@<IP_ADDRESS>)>, <Node(0xdfc2@<IP_ADDRESS>)>]
   DEBUG  05-18 22:30:06   kademlia  <<< neighbours from <Node(0x30b7@<IP_ADDRESS>)>: [<Node(0xbeae@<IP_ADDRESS>)>, <Node(0x3645@<IP_ADDRESS>)>, <Node(0x662b@<IP_ADDRESS>)>, <Node(0x5639@<IP_ADDRESS>)>]
   DEBUG  05-18 22:30:06   kademlia  got expected neighbours response from <Node(0x30b7@<IP_ADDRESS>)>
   DEBUG  05-18 22:30:06   kademlia  got 16 new candidates

Full log path would quite likely be a good thing to allow enabling (along with milliseconds?), but I'd rather see first if what's in this PR is too little context already.

👍 looks good enough to iterate on from there.  Thanks for cleaning this up.


Add support for a default and custom Server HTTP response header

Current coverage is 83.53% (diff: 100%)

No coverage report found for master at e4aeb6f.

Powered by Codecov. Last update e4aeb6f...1c40309


CI not working

Gitlab CI gives this error:
$ julia -e 'using InteractiveUtils; versioninfo()'
Julia Version 1.0.3
Commit 099e826241 (2018-12-18 01:34 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Xeon(R) CPU E5-2637 v2 @ 3.50GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-6.0.0 (ORCJIT, ivybridge)
Environment:
  JULIA_DEPOT_PATH = /builds/JuliaGPU/Makie.jl/.julia/
$ julia --project=test/ -e 'using Pkg; Pkg.build("Makie"); include("test/runtests.jl")'
ERROR: The following package names could not be resolved:
 * Makie (not found in project or manifest)
Please specify by known `name=uuid`.
Stacktrace:
 [1] pkgerror(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Types.jl:120
 [2] #ensure_resolved#43(::Bool, ::Function, ::Pkg.Types.EnvCache, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Types.jl:900
 [3] ensure_resolved at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Types.jl:870 [inlined]
 [4] #build#53(::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}, ::Function, ::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:455
 [5] build at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:436 [inlined]
 [6] build(::String) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/API.jl:431
 [7] top-level scope at none:0
ERROR: Job failed: exit code 1

This is a subset of the full output.  It seems that there's an error where Makie isn't being found by Julia, maybe the directory is wrong?

See JuliaPlots/Makie.jl@8e9fb1ed3cdb6a565914bb2c825117e170fcdd0e

This should be fixed in a while by #297


Feature: t reply STATUS_ID opens a text editor / prompts for reply status

If I run t update with no status, a text editor opens where I can write my status.
If I run t reply TWEET_ID with no status, I get the error message:
ERROR: "t reply" was called with arguments ["672207489530597377"]
Usage: "t reply TWEET_ID MESSAGE"

I would like reply to behave the same as update in that it will prompt for the status by opening an editor.
I'm posting this feature idea for early feedback, before implementing it myself

:+1: to this idea. I’ll take a look at the implementation now.


Globally switch off html escaping

I know that per the specifications, mustache defaults to html escaping. This is however inconvenient when using it for documents different from html. Is there a way to globally turn it off, eg. some equivalent to the javascript version?

There wasn't before, but that's actually a great idea! I've released a new version, and it's now possible to write:
mstch::config::escape = [](const std::string& str) -> std::string {
  return str;
};

to achieve the result you want.

This is amazing!! Thank you for this great solution and a great tool!


Hide DynamicDataProperty

Addresses https://github.com/Azure/azure-sdk-for-net/issues/35944

[ ] Make DynamicDataProperty internal and implement IDynamicMetaObjectProvider to fulfill its public contract

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Core

The code looks fine, but I admit I'm not understanding the overall change. How did this work before?

It worked prior to this change because DynamicDataProperty was a public type.  The DLR was resolving the items returned from ObjectEnumerator, which implements IEnumerable<DynamicDataProperty> as DynamicDataProperty types, and then accessing their public members.
If we were only to change DynamicDataProperty to internal, the DLR might be able to resolve the type, but it would also know that callers outside the assembly no longer have access to the type or its members.  So trying to call .Name or .Value on the dynamic item will throw a Microsoft.CSharp.RuntimeBinder.RuntimeBinderException.  Specifically, you'd get:
Microsoft.CSharp.RuntimeBinder.RuntimeBinderException : 'System.ValueType' does not contain a definition for 'Name', so it looks it actually resolves to the public base type of the internal type.
IDynamicMetaObjectProvider is a public interface, so I we can still return the type from the enumerator and anyone accessing it outside the assembly (through the dynamic keyword) will see it as an implementation of that interface.  They can only see the interface, not the internal type, but this is sufficient for us to implement the dynamic bindings to the member names.

Thank you! That explain everything.


zephyr: Revamp jerry-port.c, add more functions.

The file was named jerry-entry.c and not even built. Rename for clarity,
and add jerry_port_fatal(), jerry_port_get_current_time(),
jerry_port_get_time_zone() functions. User-visible result is that
if Date builtin is enabled (e.g. if building "full" config, its
Date.now() method can be used to measure relative time difference,
e.g. for benchmarking).
JerryScript-DCO-1.0-Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

@sergioamr , @poussa : FYI.

lgtm

lgtm

Fixed comment and rebased on the master.


Unable to import assets in JS

Many thanks for this module - it's made working with Vite in Django much easier for me!
I've converted your example app to a React Vite app, and I'm trying to import and use an image from an assets folder inside src:
import reactLogo from './assets/react.svg'

Vite does not complain about the path being wrong (I've tried a few variations) but in the browser the image 404s because the path resolves to:
http://localhost:8000/static/assets/react.svg

I believe the problem is that in dev the url should be the port 3000 url, but I'm not sure the best way to address this. Any guidance would be greatly appreciated!

Try changing your setting on settings.py -> DJANGO_VITE_DEV_SERVER_PORT

I'm having the same issue when importing fonts. The problem is that the urls that Vite generates don't have a host, and the browser tries to get them from the Django server instead of the Vite dev server.
I can't launch the dev server on the same port, and I don't really know what to do.

I'm having the same issue when importing fonts. The problem is that the urls that Vite generates don't have a host, and the browser tries to get them from the Django server instead of the Vite dev server.
I can't launch the dev server on the same port, and I don't really know what to do.

I have made a custom Vite config js file for this and some other cases, it also includes code for building and saving dist files accordingly:
https://gist.github.com/GatoVuelta/a87d0007415d3f34d497269ce6dde09b
Then, if you use SASS you can import fonts and Vite will automatically look for it both on dev and build.
For a dir structure like: (root)/static/public/fonts/Poppins-Regular.ttf you could import it like this:
@font-face {
    font-family: 'Poppins';
    font-style: normal;
    src: url('/static/fonts/Poppins-Regular.ttf') format('truetype');
}

In the future, I'll make a starter repo that would include all files and configs for an ideal Django + Vite setup.
Note that my approach may not be the best.

The whole problem is that dynamically included files are referenced as /static/path-to/file.woff2 which assumes that page is opened on the same port. I recall this was fixed by using proxy to backend, instead of loading django served pages directly.

Turns out it is trivial to solve. Simply set server.origin in your vite.config.js
server: {
  origin: 'http://localhost:5173',
},


[Misc]:  Question about Serving with Server API

API Server
I have been digging around VLLM. and I have observed that the API server actually holds a client to an RPC server.
I guess this is needed because of the multi model potential nature. But if I were to serve a single model instance, would it be recommended to use directly an AsyncLLMEngine behind my FastAPI app or any web server?
Thanks for the clarification.
Before submitting a new issue...

[X] Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Hey thanks，
This is quite interesting, however have you considered also simply using a ThreadPool to asynchronize blocking CPU actions? At the end most of the time you would be calling libraries releasing the GIL right?

The issue is not asyncio related.
The issue is that on H100 with small models, the GPU forward part of the inner loop is very fast (this is the only section that releases the GIL) and we have CPU contention between the rest of the inner_loop (schedule and process_outputs) operations and the FastAPI server. So running in a ThreadPool will not fix the issue because none of the operations that are causing CPU contention release the GIL

Thanks for the reply.

Thanks for the reply.

@JoanFM Are you running into some issues? The RPC caused some problems in v0.5.4 that we stabilized in v0.5.5, but if there are any ongoing problems I would greatly appreciate any reproduction instructions

Hey, no not issue thanks.


Sign-in Frequency using Company portal support in Preview

According to Michael Epping when he was a guest on the Mac Admins Podcast (Episode 293, Nov 2022 at the 1:05:30 mark) https://podcasts.apple.com/us/podcast/mac-admins-podcast/id1097430326?i=1000588019066:
Sign-in Frequency as a Conditional Access requirement is not (as of the time of the podcast) compatible with SSO using CompanyPortal on Mac. Can you confirm if this limitation has been resolved and hence not in this documentation or please note this limitation in the documentation?
Thanks!

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

ID: f3aa0933-44ee-6c0f-caf2-defe2b90c3f9
Version Independent ID: 7a281e52-2e8d-cae3-34b8-8ce5f6b78c03
Content: Microsoft Enterprise SSO plug-in for Apple devices - Microsoft Entra
Content Source: articles/active-directory/develop/apple-sso-plugin.md
Service: active-directory
Sub-service: develop
GitHub Login: @henrymbuguakiarie
Microsoft Alias: henrymbugua

@cchambers-cap
Thanks for your feedback! We will investigate and update as appropriate.

Hi @cchambers-cap
Thank you for bringing this to our attention.
To gain a better understanding of your issue, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request). Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
[Teams Q&A forum] (https://docs.microsoft.com/en-us/answers/topics/46488/office-teams-windows-itpro.html) for technical questions about the configuration and administration of Microsoft Teams on Windows.
[Microsoft Teams Community forum] (https://answers.microsoft.com/en-us/msteams/forum?sort=LastReplyDate&dir=Desc&tab=All&status=all&mod=&modAge=&advFil=&postedAfter=&postedBefore=&threadType=All&isFilterExpanded=false&page=1

So does that mean that Sign-in Frequency conditional access policies should no longer cause any issues with SSOe?

Hello @cchambers-cap,
Thank you for your feedback.
We resolved the issue and documented new functionality here:
User sign-in frequency
Now, I'll close the issue.
#please-close


Confidence in my experience

you state "After you're confident of the extension based Hybrid Worker experience and use, you can [remove] the agent based Worker."
I now have both extension and agent installed on the same VM, how do I know it is using the extension or the agent to run my jobs?
How can I be confident of my "experience"

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

ID: e46cfd4e-9663-145f-dd23-28effd108738
Version Independent ID: f5126582-7211-65c9-0817-cef899f6aee5
Content: Migrate an existing agent-based hybrid workers to extension-based-workers in Azure Automation
Content Source: articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
Service: automation
Sub-service: process-automation
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

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

Thanks for the feedback @postledm! I have assigned the issue to the content author to investigate further.

@postledm - The Engg team has confirmed as following -
_We don’t give preference to any agent. The one who polls first will run the job.
To control the distribution of runbooks on Hybrid Runbook Workers and when or how the jobs are triggered, you can register the hybrid worker against different Hybrid Runbook Worker groups within your Automation account. Target the jobs against the specific group or groups to support your execution arrangement. _

#please-close


Update FAQ, update storage and metadata cleanup doc, add the online v…

…ideo section

Can one of the admins verify this patch?


Editing values in the grid?

Is it possible to edit the values in the grid, or do you need to go to an edit form?

It's possible, but not implemented.
You need to implement component that will save data & override TCell component to render inputs. Form already exists for each grid & it's always submitted to current URL.
Also you can do it even without extending Grids functionality, pure frontend JS and server action to save data.