Improvement idea: Real PTT for SSTV Encoder App?

Hello.
Out there's an interface called AOIC: https://github.com/skuep/AIOC on the market.
This hardware is able to use PTT on ttyACM port. What do you think? Is this PTT function interesting for you, too? AIOC has proparitary VOX PTT function implemented only. I think real PTT on ttyACM port would be really great. Because amateur operators prefering real PTT.
I'd test it for you. :)
Thank you very much for rating this idea.
de DO7OO

Hello, thank you.
However, please note that an issue with PTT suggestion already exists: https://github.com/olgamiller/SSTVEncoder2/issues/12


pull request for e2e test at 01/13/2017 09:56:07

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


server/shadow: Fix incorrect handle of makecert_context_process.

This is introduced in PR #2708 with fault handling for makecert functions.
Other functions return '1' for OK, but makecert_context_process returns '0' for OK, so the current code is incorrect.

I wonder if we should fix makecert_context_process to keep consistent with other makecert functions. Weird meaning of return values introduces lots of trouble for both coding and reviewing :)

LGTM

+1
@realjiangms thank you! - Since we do have so much different return type handlings in FreeRDP it's sometimes really hard to keep track ;)


[QUESTION] Is FastAPI possible to use Python dataclasses in the future?

Dataclasses is now a relative new feature for python and claims to replace pydantic. Is FastAPI possible to use Python dataclasses in the future?
Maybe I don’t know any features of dataclasses, fastapi and pydantic, so maybe this question is a little dumb.

Dataclasses is just a cleaner alternative to regular Python class. The key point is having less boilerplate code like def __init__(self, ...).
Pydantic, in the context of FastAPI at least, is mainly for data validation and/or serialization purposes. I think it also plays a part in generating the OpenAPI JSON for documentation.
So as long as dataclassess is not providing the validation functionality, it cannot replace Pydantic. You can, however, use it to define your data models and map them to the database if the ORM allows.

Looks like pydantic does support them in some way: https://pydantic-docs.helpmanual.io/usage/dataclasses/
More in-depth discussion here: https://github.com/samuelcolvin/pydantic/issues/710

Thanks for answers. I close issue.

Thanks for the help here everyone! :clap: :bow:
Thanks for reporting back and closing the issue :+1:


Error when leaving tabpage

To reproduce

Run Vim with vim-hitspop.

:tabnew.

Run arbitral search command to show hitspop's popup.

:tabclose.

Error occurs.

Error detected while processing WinEnter Autocommands for "*"..function hitspop#main:
line   13:
E716: Key not present in Dictionary: "line, opts.col] != [coord.line, coord.col]"

After :tabclose, hitpop's popup is closed but it's callback function seems to be not called. why?

After :tabclose, hitpop's popup is closed but it's callback function seems to be not called. why?


Setup process by which contributors can access shared crendentials

Right now, I have test credentials supplied DynECT, UltraDNS, DiscoveryDNS, Rackspace and Google Cloud. I also have paid-for credentials for HP cloud (designate), and Amazon.
I'd like for us to be able to share access to credentials, if at least for testing.
This could be a credential store authorized by github, or this could be a parameterized travis or cloudbees job that allows contributors to kick off live tests. Maybe it could be something else.
Let's figure out what to do here.

related mail thread https://groups.google.com/forum/#!topic/denominator-dev/Fj95GSCg-UI


Allow opening inventory in the Nether portal.

This is kinda like stable_cacti; this was added to mask a limitation in the engine that has now been fixed for years.

This is kinda like stable_cacti; this was added to mask a limitation in the engine that has now been fixed for years.

I've received an overwhelming number of feature requests over the week and they are filling up the issue tracker and making it difficult to keep track of what is even going on. I've enabled Discussions on the repo as a new location for feature requests. Unfortunately, GitHub has "temporarily" disabled the ability to convert issues to discussions, so I'm closing all feature request issues. However, I'm tracking all the closed issues in a Project board; despite being closed, they're still on my radar on the board. All new feature requests must go to Discussions. Feature requests opened as issues going forward will be closed.

I've received an overwhelming number of feature requests over the week and they are filling up the issue tracker and making it difficult to keep track of what is even going on. I've enabled Discussions on the repo as a new location for feature requests. Unfortunately, GitHub has "temporarily" disabled the ability to convert issues to discussions, so I'm closing all feature request issues. However, I'm tracking all the closed issues in a Project board; despite being closed, they're still on my radar on the board. All new feature requests must go to Discussions. Feature requests opened as issues going forward will be closed.


[WIP] Implementing binary decorators for smarts sampling

I started to implement the idea that @cbayly13 gave to me about having binary decorators instead of unary decorators for smarty.
The first modification was changing the decorator file, where we removed the bond-atom specification and let only bond specifications.
$(*-z) simply bonded
$(*=z) doubly bonded
$(*#z) triply bonded
$(*:z) aromatic
$(*~z) any

Then, we started to generate smarts strings randomly adding one, two or three decorators, as we discussed on #13. The modification was mostly inside the function sample_atomtypes.
The code is not done yet, and I need to clean up a lot of things, but we can have an idea about what is going on and what we can improve from that.
Please, let me know if you need more explanation about it.

@camizanette: This sounds like exactly what we need. Thanks for putting this PR together, and succinctly summarizing the proposed solution in #13!
Some comments on the PR in progress:

What do you think about retaining both the old behavior and new behavior? It might be simplest to add an option (e.g. a command-line option) to select a mode (perhaps simple-decorators and combinatorial-decorators), and to also refactor the child atomtype proposal into separate functions that handle the different behaviors. That way, we could easily experiment with adding other schemes in the future without changing the existing code.
It looks like you accidentally ran git add on a number of directories and files that shouldn't be in the repo:

smarty.egg-info/
build/
You'll have to remove them, since it would cause trouble to have these committed to the repo since they are rebuilt each time you install.

Again, this is looking great---thanks for working on this!

@camizanette , @davidlmobley asked me to take a look at your pull request. I found one small error that is due to variable name differences.
            # Update proposed parent dictionary
            proposed_parents[atomtype].append(proposed_atomtype)
            proposed_parents[proposed_atomtype] = []

The lines above aren't working anymore, I think it's because you've changed variable names. I added them while you were working on this to track parent hierarchies.
atomtype was the atom that was being decorated, the variable doesn't seem to exist anymore. Are you calling that basetype now?
Also, I think you'll want to use print(...) for your print statements.

What do you think about retaining both the old behavior and new behavior? It might be simplest to add an option (e.g. a command-line option) to select a mode (perhaps simple-decorators and combinatorial-decorators), and to also refactor the child atomtype proposal into separate functions that handle the different behaviors. That way, we could easily experiment with adding other schemes in the future without changing the existing code.

I like the idea of this, I think it will give us flexibility in experimenting later. What do you think?

@camizanette - after discussion with @cbayly13 and @bannanc , we're hoping you can go ahead and get the minor issues noted above (plus the optional command-line option) fixed so we can go ahead and merge this and begin using it more, ASAP. @bannanc is I think going to coordinate with you about who fixes the proposed_parents issue she mentioned.
We've got some more extensive changes that we want to make that I'll describe in a separate issue shortly, but we should get this merged before doing that.

@camizanette I fixed the parent issue, I'll make a pull request to your branch.

Thank you all for the comments. I updated my branch and I will submit the pull request tomorrow morning.

@camizanette I don't think this handling the parents/children correctly still
For example, in a run I just did I got the following for children of hydrogen:
[#1]
         [#6$(*~[#1])+0]
         [#1H0]

The first child is a carbon not a hydrogen. However the second one is a hydrogen so I think I'm missing something about which variable you're using to make the children.

Thanks, @bannanc . Working on this!

@bannanc, can you check if it is correct now? Thanks!

If I understand right, this is good to merge now once @bannanc and/or I have a look? If so you can remove [WIP] from the title, @camizanette .

The parents look good to me now. Here's the tree from my last run:
[#1]
         [#1$(*~[#8])X1]
[#8]
         [#8$(*~[#6])H1]
[#6]

Thanks! So looks like I can merge... I'll go ahead and do so. Then we can shift our focus to #48 . It's nice to see that we're finding more complicated/decorated smarts patterns now.
It would probably be good if we understood why we can't find H1 yet, but maybe we can get an idea of that when we talk this afternoon.

Awesome!


docs: Update roadmap

Codecov Report

Merging #445 into rc7.0 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            rc7.0     #445   +/-   ##
=======================================
  Coverage   96.29%   96.29%
=======================================
  Files          56       56
  Lines        1914     1914
  Branches      228      228
=======================================
  Hits         1843     1843
  Misses         71       71

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 de13e6e...0fcc8bd. Read the comment docs.


Unbounded Binary Search

Explanation
Unbounded Binary Search is missing in NeoAlgo/C-Plus-Plus/search/
Find the point where a monotonically increasing function becomes positive first time.
Have you read the [Contributing Guidelines on Pull Requests]
Yes, I've read the guidelines.
As a GSSOC21 Participant, I would love to work on this issue.
@ankitaggarwal23 Please assign me this issue

@AmanBisht01 Can you please bit more elaborate your approach how you're going to implement?

The function is monotonically increasing with respect to the value of x, i.e., the value of f(x+1) is greater than f(x) for every input x. Find the value ‘n’ where f() becomes positive for the first time. Since f() is monotonically increasing, values of f(n+1), f(n+2),… must be positive and values of f(n-2), f(n-3), .. must be negative.
Approach
O(n): A simple solution is to start from I equals to 0 and one by one calculate the value of f(i) for 1, 2, 3, 4 .. etc until we find a
positive f(i).
O(Logn): We can’t directly apply Binary Search as we don’t have an upper limit or high index.The idea is to do repeated doubling until we find a positive value, i.e., check values of f() for following values until f(i) becomes positive. Let 'high' be the value of i when f() becomes positive for first time.
We can apply Binary Search now, we can use ‘high/2’ as low and ‘high’ as high indexes in binary search. The result n must lie between ‘high/2’ and ‘high’.

@AmanBisht01 Hi, I assigned you. Happy Coding!😊

@ankitaggarwal23 i have  created PR please review it.


Update of polish language

Update of all texts in polish language, change translation of book from 'Podręcznik' to 'Książka'. I think it better reflects the meaning of the word.
If I made a mistake, please correct me.

Thank you @artskoczylas for providing these updates. Will merge them in now for the next release.


Fix platform specific issues with provider ciphers

s390_aes naming issues with ofb128 and cfb128
Solaris missing include for camellia.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

Thanks Richard. Merged to master.


Use setPrototypeOf

Hey, just perusing the repo's around here and noticed in this one it is setting __proto__.  Not sure what the end use of this module will be, but we had a discussion around this here because that breaks some browser support.  Also, there is a new and standardized api to do this, Object.setPrototypeOf.  So the router is using this module to get a nice fallback.
If you want I can PR that in, but I wanted to open this to make sure I wasn't misunderstanding the use case for this module :)

When @dougwilson has previously tested this, __proto__ was the most efficient in V8 / node.
@wesleytodd what browsers don't support __proto__? As far as I understand all current ones do and will continue to do so due to usage.

IE10 was the main one, but I guess since MS just dropped support for anything below 11, maybe this is a moot point.  Technically according to MDN __proto__ have been standardized as legacy:

Warning: While Object.prototype.proto is supported today in most browsers, its existence and exact behavior has only been standardized in the ECMAScript 6 specification as a legacy feature to ensure compatibility for web browsers. For better support, it is recommended that only Object.getPrototypeOf() be used instead.

The original issue I linked to was about a year ago, and I was trying to support back to IE9 with the router.  Anyway, totally understand if you want to close this.

@wesleytodd what exactly are you trying to run in a browser that requires this functionality?

Hopefully most what what express is doing.  I am currently running just the router, but in the future I would love to be able to run something that looks and functions just like an express app on the backend.  That is the only reason I even mentioned this issue here is because I assume this module will take over this (https://github.com/strongloop/express/blob/5.0/lib/express.js#L43-L44) in the future.  Am I correct in assuming that?

Correct. If you make a PR I'll review it but I don't really make any guarantees about browser support from myself.

Thats what I'm here for, browser support :)
And FWIW, just ran this jsperf and the perf is comparable in up to date chrome: http://jsperf.com/new-vs-mutable-proto/2

@wesleytodd Two things:
There will be up to like, 100 properties attached, not just from express, in a busy application.
They can't really be defined in an object literal I think, most will be defined after the fact, causing some amount of deopt.

updated that jsperf to add 200 properties, still same perf characteristics. http://jsperf.com/new-vs-mutable-proto/5
This might be an issue, since the fallback iterates over the properties.  Do you have a link to somewhere that does this so I can see?

@wesleytodd Currently in express: no, but that is what this library does because it makes this a usable API.
Some background: setPrototypeOf() seems fairly new, I only heard about it around a week ago. Either way, it's definitely not in node <4. The alternatives had been either __proto__ or some sort of Object.setProperty(). The latter was much slower.
From what I can tell __proto__ and setPrototypeOf() are possibly aliases in some form.

Yeah, I guess its newish, here is the best source for info on it that I know of: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/setPrototypeOf
It was spec'd out in es2015, but that was the point of that module I linked to originally.  To get the new feature while keeping backward compat.
For reference, I am currently working on building a express compatible implementation for the browser.  It would hopefully encompass as much of the express api surface area as makes sense run in the browser.  So supporting the ability to customize req/res in the same way express allows would be awesome.  That is why I care about this.

@wesleytodd are you interested in making a PR for it? :)

Absolutely, sorry, I got distracted and on other things.  I can do that tonight or tomorrow when I get home.

See #6 :)

As far as my opinion on this, I'm more aligned with @wesleytodd, as that is the more up-to-date consensus since the last time you were around, @Fishrock123 :) The router discussion has a pretty relevant recent discussion on this.


GitHub private repositories fail due to unable to find any valid known_hosts file, set SSH_KNOWN_HOSTS env variable

Kpack 0.11.0 replaced git2go with go-git and doing so GitHub private repositories fail due to this error:
unable to fetch references for repository: unable to find any valid known_hosts file, set SSH_KNOWN_HOSTS env variable
The same configuration works with kpack-0.9.4 without issue. This appears to be a regression due git2go -> go-git and may be caused by the handling of known_hosts in the context of the underlying SSH connection to GitHub's git repositories.
In kpack-0.9.4, private repositories on GitHub required a secret that included GitHub's SSH public key(s). For example KNOWNHOSTS64 below would be ssh-keyscan github.com encoded base64. This requirement was pieced together from aged documentation references including #413. It is possible that this issue is from some unrelated misconfiguration we have, so we'd like this to be confirmed prior to giving this issue any more attention!
apiVersion: v1
data:
  known_hosts: KNOWNHOSTS64
  ssh-privatekey: PRIVATEKEY64
kind: Secret
metadata:
  annotations:
    kpack.io/git<EMAIL_ADDRESS>
This has been tested by trying identical Image configurations on kpack-0.9.4 (working) and kpack-0.11.0 (not working).

I am actually not sure why it works in 0.9.4. The only thing we read from the secret is the ssh-privatekey field: https://github.com/pivotal/kpack/blob/4ce090eb8a72579bd76ea1604b4e83b89f3ae6d2/pkg/secret/volume_secret_reader.go#L31-L41
I wonder if libgit2 just silently trusts unknown hosts, @usiegj00 can you try using the same image configuration on 0.9.4 but without the known_hosts field on the secret?

Yes--kpack 0.9.4 does not need the known_hosts field. I must have added it in attempting to debug the go-git update.

After talking with @tomkennedy513, since this is technically a regression, we're gonna introduce a --insecure-ssh-allow-unknown-hosts (or similarly named) flag which will default to true to keep the old behaviour. We'll also introduce a way to provide a known_hosts file (probably the same as the way you're doing it) to the build.
Then at some time in the future we can default the flag to false and only allow user supplied known_hosts

Hello,
I had this same issue using version 0.11.0 and 0.11.1, but I managed a partial workaround.
I added the known_hosts field to the same git-ssh-auth Secret that is mounted in the kpack build Pod at /var/build-secrets/git-ssh-auth/. This means it mounts the known_hosts field of the Secret as file: /var/build-secrets/git-ssh-auth/known_hosts in the container.
In the build pod, by specifying the environment variable SSH_KNOWN_HOSTS manually, I am able to specify the value /var/build-secrets/git-ssh-auth/known_hosts which contains the contents of:
ssh-keyscan -H github.com > github_knownhosts.txt

I'm currently looking for a way to always create this ENV variable. Adding it through the Image seems to create an environment variable called PLATFORM_ENV_KNOWN_SSH_HOSTS which doesn't work/help.


fix(si): Ensure that running an update when no containers installed doesn't trigger start

ENG-1886
ENG-1887

feat(si): Ensure we capture the name of the containe engine when tracking usage
fix(si): Ensure that running an update when no containers installed doesn't trigger start

bors merge


[Bug]: Can't initiate auth.handleRequest using Nextjs 13 app router

Package
lucia-auth
Describe the bug
Context
I'm currently trying to implement Lucia auth on a Nextjs 13 project which will run on the edge. I've figured out how to set up oAuth with drizzle and planetscale connection, but got stuck at authRequest creation step and can't figure out if it's something I don't know, something I've missed, or if the problems outlined bellow are impossible to overcome at this stage.
Problems:
It might be that I'm missing something (or more likely not understanding something to the fullest), but I have 2 related problems with handleRequest method:

It seems that it's impossible to create auth request instance with auth.handleRequest using NextJS 13 app dir routing, because native request and response aren't provided, only NextRequest and NextResponse which aren't compatible.
Trying to implement edge funcionality using docs example middleware: env === "DEV" ? node() : web() breaks TS (and most likely functionality too) because node and web middlewares have different "request" / "response" attribute typings, which get inferred by TS and don't accept either.

Code example:
I've created a small codesandbox template to notice these problems:
https://codesandbox.io/p/sandbox/busy-hofstadter-e3mbpo?file=%2Fapp%2FoAuthCallback%2Froute.ts%3A12%2C71
There are 2 folders:

app - nextjs 13 app dir routing example. Used to show Request / Response incompatabilities
pages - same example, but with the old way of routing. Done by Lucia Nextjs example, used to show "edge" problem.

Files related to the problems:

db/index.ts - DB and Lucia auth config. Here we have the middleware settings.
app/page.tsx - server-side rendered page. HandleRequest invocation inside a new page component that doesn't receive context as getServerSideProps used to before, thus we're left with NextRequest / NextResponse
app/oAuthCallback/route.ts - server-side API call. Only native Request is provided, no Response, not enough for
pages/index.tsx - getServerSideProps example. The same way is done in Lucia's nextjs example, the difference - edge functionality enabling with web middleware.
pages/api/oAuthCallback.ts - server-side API call. Same as with pages/index.tsx - problem is with web middleware usage.

Regarding Nextjs Request / Response issue: In Nextjs we can access cookies, host and other relevant info using its provided dependencies, but these are not bundled inside its NextRequest / NextResponse
Regarding web middleware usage problem, if you'd change line 20 inside db/index.ts to middleware: node() - pages folder files would work fine without any errors.
Question
Is there a way of fixing these two issues, or should there be another middleware just for that?
Also, moving forward, all new Nextjs projects will use the app dir instead of pages (even more now that the router is in stable state), so IMO it would be good to future-proof the examples folder with nextjs app dir example (if it's possible)

I played around with your example, and I got the following to not go BOOM.
Link: https://codesandbox.io/p/sandbox/lucia-next-app-dir-forked-t4w4q8?file=%2Fapp%2FoAuthCallback%2Froute.ts%3A15%2C1
Essentially the stuff I changed:
db/index.ts - Set the middleware as web since Next 13's edge runtime does not support Node.
pages/* - Deleted to not cause conflict.
app/page.tsx - Removed any lucia stuff here since your cookie would have your user id.
app/oAuthCallback/route.ts - Using the Request/Response stuff here to handle the request.
Could you check this with your Planetscale credentials?

https://codesandbox.io/p/sandbox/busy-hofstadter-e3mbpo?file=%2Fapp%2FoAuthCallback%2Froute.ts%3A12%2C71

Hey Sean, thanks for checking it out!
Using only the web middleware without node was a gateway when debugging (and a great help in remembering that mostly everything about page dir should be thrown out the window when working with app dir in nextjs).

I've made multiple variations, delved deep into the structure of lucia-auth and nextjs app dir server, both lucias and nextjs docs, and in the end through tears and sweat got it to work!
For anyone else stumbling here with similar issues here are some key points to take out:

With Nextjs App Router only use web middleware (doesn't matter if you're using edge or nodejs runtime, use it for both, and skip lucia's node middleware)
At the time of writing this there's a typo in the docs regarding web middleware required handleRequest arguments. It says that handleRequest should be initiated like this auth.handleRequest(request as Request, response as Response), while in reality it should be auth.handleRequest(request as Request, headers as Headers) (this got me going in the wrong direction from the start)
At the moment, while Nextjs docs say that it's possible to set cookies with next/headers provided cookies().set - that's not true, and in other parts of the docs it is clearly stated that both cookies and headers are read-only. So you can't use them to write a custom lucia middleware or to pass them from the start.

The most difficult part of all of this was finding a way for auth.handleRequest to set cookies that would persist. The only way I've found out to make it happen is to initiate handleRequest like this:

For request attribute there are two parts. In route handlers route.ts just pass the request that you get with the route function. For pages page.tsx you have to create a custom request, pass cookies to it and then use it in handleRequest.
For headers create NextResponse instance before, then pass its headers to handleRequest.

Snippet of auth actions (usage in page.tsx or any other RSC)
export async function createAuthRequest() {
    const requestHeaders = new Headers();
    requestHeaders.append("origin", headers().get("origin") || "");
    requestHeaders.append("cookie", headers().get("cookie") || "");

    // TODO: This implementation isn't the best, should be changed to something more sturdy
    const requestUrl = `${headers().get("x-forwarded-proto") || ""}://${
        headers().get("x-forwarded-host") || ""
    }${headers().get("x-invoke-path") || ""}`;

    return new NextRequest(requestUrl, { method: "GET", headers: requestHeaders });
}

export async function getAuthRequest() {
    const request = await createAuthRequest();
    const response = NextResponse.next();
    const authRequest = auth.handleRequest(request, response.headers);

    return authRequest;
}

export async function getAuthUser() {
    const authRequest = await getAuthRequest();
    const { user } = await authRequest.validateUser();

    return user as Lucia.UserAttributes;
}

// page.tsx
export default async function Page() {
    const user = await getAuthUser();

    ...
}

Snippet of oauth callback (usage in route.ts and other route handlers)
export async function GET(request: NextRequest) {
    if (!request.url) return new Response("Not found", { status: 404 });

    const redirectUrl = request.nextUrl.clone();
    redirectUrl.pathname = "/";

    const response = NextResponse.redirect(redirectUrl, 302);
    const authRequest = auth.handleRequest(request, response.headers);

    const { searchParams } = new URL(request.url);
    const code = searchParams.get("code");
    const state = searchParams.get("state");
    const storedState = request.cookies.get("oauth_state")?.value;

    if (typeof code !== "string" || typeof code !== "string" || storedState !== state) {
        return new Response("Invalid request", { status: 400 });
    }

    try {
        let getUser = async (): Promise<any> => null;

        if (provider === "google") {
            const { existingUser, providerUser, createUser } = await googleAuth.validateCallback(
                code,
            );

            getUser = async () => {
                if (existingUser) return existingUser;

                return await createUser({
                    email: providerUser.email,
                });
            };
        }

        const retrievedUser = await getUser();
        const session = await auth.createSession(retrievedUser.id);

        authRequest.setSession(session);

        response.headers.set("location", "/");

        return response;
    } catch (error) {
        return new Response("Invalid request", { status: 500 });
    }
}

Hope this helps.
If there's anyone that still gets confused - let me know here and I could try to create a somewhat-refined sandbox with everything that's needed to go up and running with Nextjs app router.
For now I'm closing this issue because the major issue is resolved, and the minor issues IMO aren't worth this kind of thread.
Recapping lucia related issues:

Using middleware: env === "DEV" ? node() : web() breaks auth.handleRequest TS - IncomingMessage =/= Request and OutgoingMessage =/= Headers, but TS doesn't know which middleware should be used.
web() middleware documentation typo, this auth.handleRequest(request as Request, response as Response); should be this auth.handleRequest(request as Request, headers as Headers);

@veiico I've been trying to get your code to work to no avail. Basically, I have a sign in form where I execute this:
const router = useRouter();

const handleSubmit = async (event: React.FormEvent<HTMLFormElement>) => {
  event.preventDefault();
  const formData = new FormData(event.currentTarget);
  const input = signInSchema.parse(formData);
  const { email, password } = input;

  const response = await fetch("http://localhost:4200/api/sign-in", {
    method: "POST",
    body: JSON.stringify({
      email,
      password,
    }),
  });

  if (response.redirected) {
    return router.push(response.url);
  }
};

It's not a server action, as that apparently doesn't work. Anyway, in the sign in route I just call this function:
export async function signIn(request: NextRequest) {
  if (!request.url) {
    return new Response("Not found", { status: 404 });
  }

  const redirectUrl = request.nextUrl.clone();
  redirectUrl.pathname = "/";

  const json = await request.json();
  const { email, password } = signInSchema.parse(json);

  const response = NextResponse.redirect(redirectUrl, 302);
  const authenticationRequest = authentication.handleRequest(request, response.headers);

  const session = await authenticationRequest.validate();

  if (session) {
    response.headers.set("location", "/");
    return new Response(null, {
      status: 302,
      headers: response.headers,
    });
  }

  const requestOrigin = request.headers.get("origin");

  const isValidRequest =
    !!requestOrigin && requestOrigin === (process.env.NEXT_PUBLIC_SITE_URL ?? process.env.NEXT_PUBLIC_VERCEL_URL);

  if (!isValidRequest) {
    return new Response(null, {
      status: 403,
      headers: response.headers,
    });
  }

  try {
    const key = await authentication.useKey("email", email, password);

    const session = await authentication.createSession(key.userId);

    authenticationRequest.setSession(session);
    // redirect on successful attempt
    response.headers.set("location", "/");

    return new Response(null, {
      status: 302,
      headers: response.headers,
    });
  } catch (error) {
    // Invalid password
    console.error(error);

    return new Response(null, {
      status: 400,
      headers: response.headers,
    });
  }
}

It seems to all work (logging session and key), but when I use your getAuthUser function, my app explodes. Basically the requestUrl ends up being :// and so I get this error:
Error: URL is malformed "://". Please use only absolute URLs - https://nextjs.org/docs/messages/middleware-relative-urls

I've tried setting requestUrl to a hardcoded value to see if it work (e.g. http://localhost:4200), which makes the error go away, and then it works (I have been tearing my hair out over another error regarding an Nx monorepo, but that's another story). Any ideas how to handle this better (you left a // TODO, maybe you solved it 😋)

Ok, so 2 updates I'll be pushing based on the discussion here:

web()middleware should take in either Headers() or Response()
Add nextjs() middleware that's a combination of node() and web()

If you're using the app router, I highly recommend extending the session timeout since there's no way to extend it with the current state.


bbox_mAP_s: -1.0000

On my own dataset, the bbox_mAP_s is -1.0000 regardless of the method.

https://github.com/open-mmlab/mmdetection/blob/master/docs/en/faq.md#evaluation

On my own dataset, the bbox_mAP_s is -1.0000 regardless of the method.

I also ran into this issue, if you solve it please reply to me, my email is<EMAIL_ADDRESS>


Migrate Gradle Enterprise Plugin to Develocity Plugin

This PR updates usage of the com.gradle.enterprise plugin to the equivalent com.gradle.develocity plugin as a result of renaming Gradle Enterprise to Develocity. This change will result in no functional changes to the Beam project.
For convenience, the changes have been broken up into 4 commits:

Applying and configuring the Develocity plugin via the new develocity configuration
Mass renaming GRADLE_ENTERPRISE_ACCESS_KEY to DEVELOCITY_ACCESS_KEY for the new plugin in GitHub Actions workflows (sorry, there are lots 😅)
Applying the most recent Common Custom User Data Gradle Plugin (2.0.1)
Ensuring remote cache push is disabled in forks that cannot write to the remote cache

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Merge confict is fixed 👍
I suspect the whitespace check is a flake here too. I ran it locally from the new commit and it passed successfully: https://ge.solutions-team.gradle.com/s/72mmccuyaynyg/console-log?page=2#L1534. But I'm also not familiar with what all it is checking for.

I think this PR is causing the below build error on settings.gradle.kts
Script compilation errors:

  Line 39:   server = "[https://ge.apache.org](https://www.google.com/url?q=https://ge.apache.org&sa=D)"
             ^ Val cannot be reassigned

  Line 39:   server = "[https://ge.apache.org](https://www.google.com/url?q=https://ge.apache.org&sa=D)"
                      ^ Type mismatch: inferred type is String but Property<String!>! was expected

  Line 42:     uploadInBackground = !isCi
               ^ Val cannot be reassigned

  Line 42:     uploadInBackground = !isCi
                                    ^ Type mismatch: inferred type is Boolean but Property<Boolean!>! was expected

4 errors

My best guess is that Kotlin version need to use .set() instead of assignment.

@tommyang  - what version of Gradle are you building with? The = operator has been supported by default since Gradle 8.2. With Beam being on 8.4, I'm surprised you are seeing any issue.

@clayburn Thanks for the explanation. It was indeed because the Gradle version of our particular repo was out of date. Long story short, that repo has its another Gradle project with an old wrapper and the build script invoked that for Beam src code as well. Sorry for the noise.

No problem, glad to help!


fix(client): get translationPending in video chals

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

The added prop is used to show the "Help us translate." text

This was brought up by @ShaunSHamilton here https://github.com/freeCodeCamp/freeCodeCamp/pull/41565#issuecomment-805230116

@ojeytonwilliams I am still encountering this error:
Warning: Failed prop type: The prop `translationPending` is marked as required in `Project`, but its value is `undefined`.
    in Project (created by withI18nextTranslation(Project))
    in withI18nextTranslation(Project) (created by Connect(withI18nextTranslation(Project)))
    in Connect(withI18nextTranslation(Project)) (created by HotExportedConnect(withI18nextTranslation(Project)))

Steps to reproduce:

Navigate to: /learn/scientific-computing-with-python/scientific-computing-with-python-projects/probability-calculator
Submit any solution
See error, once navigated to next superblock

Now, I am struggling to get the error back, but I did come across this:
Warning: Failed prop type: Invalid prop `user.completedChallenges[0].files` of type `object` supplied to `CertChallenge`, expected `array`.
    in CertChallenge (created by withI18nextTranslation(CertChallenge))
    in withI18nextTranslation(CertChallenge) (created by Connect(withI18nextTranslation(CertChallenge))

Thanks, Shaun, I've pushed another commit to fix that.


@vijcheru Called Meshkit Error Handler instead of Logrus

Description
This PR fixes #3303
Notes for Reviewers
I updated oam_handler and error.go to use the error handler
Signed commits

[X] Yes, I signed my commits.

Heads-up - merge conflicts - https://github.com/meshery/meshery/pull/3387/conflicts

Hey @vijcheru I think the DCO is failing due to the signoff problem which I think you can refer to https://github.com/meshery/meshery/pull/3387/checks?check_run_id=3019099334  and can fix it.

@vijcheru Ive resolved the DCO issues, can you rebase on the conflict?

Link the the merge conflict - https://github.com/meshery/meshery/pull/3387/conflicts

I have merged the conflicts and rebased again. Please let me know if there
is a problem.
On Tue, Jul 13, 2021 at 3:35 PM Lee Calcote @.***>
wrote:

Link the the merge conflict -
https://github.com/meshery/meshery/pull/3387/conflicts
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/meshery/meshery/pull/3387#issuecomment-879384424, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF4QXIQK47H2DNQKSWTYF3TXSPSDANCNFSM473AUUUA
.

I have merged the conflicts and rebased again. Please let me know if there is a problem.
…

There is still one more to address I think @vijcheru

I will look into it and get back to you.
On Thu, Jul 15, 2021 at 8:29 AM abishek @.***> wrote:

I have merged the conflicts and rebased again. Please let me know if there
is a problem.
… <#m_4576790912282070771_>
There is still one more to address I think @vijcheru
https://github.com/vijcheru
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/meshery/meshery/pull/3387#issuecomment-880695615, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF4QXOEHTEYKWNNVVXI6ETTX3PDVANCNFSM473AUUUA
.

Its rebased.
On Thu, Jul 15, 2021 at 9:44 AM Vijay Cherukuri @.***> wrote:

I will look into it and get back to you.
On Thu, Jul 15, 2021 at 8:29 AM abishek @.***> wrote:

I have merged the conflicts and rebased again. Please let me know if
there is a problem.
… <#m_7877180027921264102_m_4576790912282070771_>
There is still one more to address I think @vijcheru
https://github.com/vijcheru
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/meshery/meshery/pull/3387#issuecomment-880695615,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF4QXOEHTEYKWNNVVXI6ETTX3PDVANCNFSM473AUUUA
.

Codecov Report

Merging #3387 (69a1953) into master (de9c2c0) will decrease coverage by 8.39%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3387      +/-   ##
==========================================
- Coverage   18.58%   10.18%   -8.40%
==========================================
  Files          37       37
  Lines        3299     3299
==========================================
- Hits          613      336     -277
- Misses       2531     2896     +365
+ Partials      155       67      -88

Flag
Coverage Δ

gointegrationtests
?

unittests
10.18% <ø> (ø)

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-64.62%)
:arrow_down:

mesheryctl/internal/cli/root/system/start.go
1.20% <0.00%> (-53.02%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
0.90% <0.00%> (-39.10%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.48% <0.00%> (-22.23%)
:arrow_down:

Continue to review full report at Codecov.

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


Metal Open Source

Places Metal under the permissive MIT license. Closes #65

Do we really, like, REALLY need license headers in every file?

it's just better legally since it's harder to excuse not putting attribution for using our code,
especially when it's at the top of the file.

As per discussion on Discord, this SO post (a "highly" "reliable" source, but that's the best we can get) and this answer in particular, i have replaced the copyright notices with SPDX license identifiers.
Additionally, i have updated the main LICENSE file using the SPDX text of it. Following the lead of Facebook (example), Microsoft (example, example, comment by a developer), Node.js (example), and somewhat Rust (commit-discussion), i didn't add the copyright date. Following the lead of Node.js (see previously linked example), libuv (example), and Vue (example), i left the "Metal contributors" part as is.
Note that the point of these example is not to show that "this is how most projects do it". In fact, directly below this paragraph i complain about the opposite. The point is to show that some major/popular projects do it this way, and therefore doing this way is a viable option.
As an aside, i hate how much of a gray area all of this open source licensing is. You can google a question, wait a month, google it again, and get totally different answers. Even if you only look at the "big" projects, that are supposed to actually care about copyright and stuff, there's no coherence there, at all.
Some projects have start year, some start year - end year, some start year, all years in-between, end year, some start year - present, some just omit the date entirely.
Some projects have a legal entity name as an author, some have authors' real names, some keep an AUTHORS file, some specify username, some say " contributors", some omit it (???).
The need of duplicating copyright notices in all project files is also debated. Some projects copy the license fully, some refer to the "project root" or "LICENSE" file (which may not even exist by the time the code is copied), some just specify what license is used, some, again, omit this entirely. Here at least there is some effort going on to standardize this mess (namely, SPDX).

And finally, the mandatory disclaimer: I agree to license all of my past contributions to this project, available at https://github.com/metallang/metal, under the MIT license as available at https://spdx.org/licenses/MIT.html
(all future contributions will be automatically licensed thanks to GitHub's explicit inbound=outbound policy)

I will approve the PR once you do the same

I agree to license all of my past contributions to this project, available at https://github.com/metallang/metal, under the MIT license as available at https://spdx.org/licenses/MIT.html
(all future contributions will be automatically licensed thanks to GitHub's explicit inbound=outbound policy)


feat: error for duplicate outline?

Hi,
as a learning experience of both Rust and Crux, I am developing a feed reader called Crab News. It is my very fisrt app after reading The Book, so the code is what it is.
I have implemented the main stuff for OPML and I am now trying to throw errors when an outline (either folder or subscription) exists already (whether importing feeds from file or adding outlines manually). I am attempting a few things and none of them feel right and I was wondering if a native Error type in the opml crate would be appropriate to have?
EDIT: if this is unfeasible at the create level, would it be possible to extened the Error types locally? how?
Please and thank you

I did this and it works. closing but please consider as nice to have. cheers and thank you for the amazing crate!
https://github.com/crab-apps/crab-news/blob/main/shared/src/app/subscriptions.rs#L22-L31


Add tox env for building docs

Add a tox environment for building the docs, and update the README to recommend tox for running tests.  This should wrap up all of the changes originally proposed in #20 .
This is about the end of the changes I was planning to make in the near future.  Any thoughts on when to make a new release?  I need to make some updates to bok-choy, and would rather not switch it over to installing needle from git.

Thanks. Does that mean that the ReadTheDocs configuration also needs updating? By the way, I don't have access to the RTD project myself, so I'll have to check with Ben. Also, I've just noticed that the builds have been failing there for a while.... https://readthedocs.org/projects/needle/builds/

Also, to answer you question, I should be able to push a new release in the coming days. I'm just hoping to resolve the RTD issue first.

It looks like your RTD build is configured to use a virtualenv with dependencies specified in a requirements.txt file at the project root, but you have no such file.  You can either fix that by adding such a file containing at least "Sphinx", or by changing the build config to not specify a requirements file (RTD installs a relatively recent version of Sphinx for builds by default).  I usually use a requirements/docs.txt file for my projects and pin known-working versions of all of Sphinx and all of its dependencies, but that's arguably overkill.

That makes sense, thanks. I'll try to fix all of that soon and then I'll merge this PR.

Cool, so I added a docs/requirements.txt file and the build passed. Merging now, thank you!


Fail fast when results-dir is incorrect

Fixes #753
Checklist

[x] Unit tested
[x] release_notes.md updated

Codecov Report

Merging #772 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #772   +/-   ##
=========================================
  Coverage     78.22%   78.22%
  Complexity      665      665
=========================================
  Files           125      125
  Lines          2778     2778
  Branches        399      399
=========================================
  Hits           2173     2173
  Misses          351      351
  Partials        254      254


bug: links that have a null value throw exceptions

Fixes non-standards links nodes such as the following breaking the deserialiser with an exception
"links": {
"self": "/v1/products?page[size]=10&page[number]=1",
"first": "/v1/products?page[size]=10&page[number]=1",
"last": "/v1/products?page[size]=10&page[number]=2",
"prev": null,
"next": "/v1/products?page[size]=10&page[number]=2"
},

Thanks @alastairtree  for noticing and fixing this. Could you also put in a test case to cover the fix

Added a test case. Would an updated nuget release be possible once you are happy? Thanks for the library, very useful.

Merged and available on nugget. You should see your fix in version 1.3.1


Trying twoagent.py in Getting Started and it does not run on Windows. Gives WARNING:root:SIGALRM is not supported on Windows.

I cannot get the twoagent.py script to run under Windows in VSCode (via the "Run | StartDebugging" command). I followed the instructions in the Getting Started docs but get the following error:
ModuleNotFoundError: No module named 'pandas'
Also, I get the SIGALRM is not supported waring; here is the console output:
`user_proxy (to assistant):
Plot a chart of NVDA and TESLA stock price change YTD.

assistant (to user_proxy):
To plot the chart of NVDA and TESLA stock price change Year-to-Date (YTD), we need to first collect the stock price data
for both NVDA and TESLA. We can fetch the data from a financial API such as Alpha Vantage. Here is an example of how you
can plot the chart using Python:
# Required Libraries
import pandas as pd
import matplotlib.pyplot as plt

<edited for brevity>

plt.show()

Please note that you need to replace <your_api_key> with your API key from Alpha Vantage. Make sure you have the required libraries installed (pandas, matplotlib, seaborn, and requests) before executing the code.
Let me know if you need any further assistance.

Provide feedback to assistant. Press enter to skip and use auto-reply, or type 'exit' to end the conversation:

NO HUMAN INPUT RECEIVED.

USING AUTO REPLY...

EXECUTING CODE BLOCK 0 (inferred language is python)...
WARNING:root:SIGALRM is not supported on Windows. No timeout will be enforced.`

Note: of course, I can install pandas, etal. but that defeats the auto-troubleshooting of the UserProxyAgent.
I suspect this is somewhat similar to the problems mentioned in #17, #19 and #38.
Does AutoGen support running on Windows?
pyautogen version: 0.1.6 (from 10/2/2023 build)
Windows specs: Windows 10 Home (64-bit), OS build: 19045.3448
Running in virtual python environment from VSCode.
NOT running in docker (yet).

The warning shouldn't stop the program. Could you wait and see if it finishes with an error?

Thnx for the quick response.
Yes, that does help a lot. Seems one problem I had was while running in vscode, I had "uncaught exceptions" break point turned on and I was just hitting that breakpoint. The SIGALRM warning was not the problem. I am able to progress quick a bit further. It now seems to be installing the correct modules but I am now hitting a tokens limit problem.
Therefore, I will close this issue and re-submit a different one if that is warranted.


has_many :through errors in complex case

Discussion start in https://github.com/eladmeidar/rails_indexes/pull/23 by @mexxer
    class Message < ActiveRecord::Base
    belongs_to :author, :class_name => "User"
    has_many :message_copies
    has_many :recipients, :through => :message_copies

    class MessageCopy < ActiveRecord::Base
    belongs_to :message
    belongs_to :recipient, :class_name => "User"
    belongs_to :folder
    delegate :author, :created_at, :subject, :body, :recipients, :to => :message

    class User < ActiveRecord::Base
    has_many :sent_messages, :class_name => "Message", :foreign_key => "author_id", :dependent => :destroy
    has_many :received_messages, :class_name => "MessageCopy", :foreign_key => "recipient_id"
    has_many :new_messages, :class_name => "MessageCopy", :foreign_key => "recipient_id", :conditions => "read = 'f'"

rake aborted!
uninitialized constant Recipient
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/rspec-core-2.0.1/lib/rspec/core/backward_compatibility.rb:20:in const_missing'
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/rspec-expectations-2.0.1/lib/rspec/expectations/backward_compatibility.rb:6:inco
nst_missing'
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.0.1/lib/active_support/inflector/methods.rb:124:in block in const
antize'
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.0.1/lib/active_support/inflector/methods.rb:123:ineach'
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.0.1/lib/active_support/inflector/methods.rb:123:in constantize'
/usr/local/ruby/lib/ruby/gems/1.9.1/gems/activesupport-3.0.1/lib/active_support/core_ext/string/inflections.rb:43:inconstantize'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:153:in block (2 levels) in check_for_indexes
'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:117:ineach_pair'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:117:in block in check_for_indexes'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:107:ineach'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:107:in check_for_indexes'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/rails_indexes.rb:284:insimple_migration'
/home/max/.bundler/ruby/1.9.1/rails_indexes-0d4e405d5964/lib/tasks/rails_indexes.rake:10:in block (2 levels) in <top (requ
ired)>'

@warpc had you fixed this problem?

@plentz It works, but not in all case

gotcha, thanks! great work btw :)

Thanks! If you have problems, write, i try to fix it


fix: delete entity in use 1618

:tada: This PR is included in version 0.323.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove mention of non-existent C support (328)

https://github.com/risc0/risc0/issues/328 says that C support doesn't work at the moment.

Completed?

The prover supports running any code that is compiled to rv32im. I think it's valid to say that we support these languages but there might be more or less batteries included.


Custom NuGet feed accessibility

If we have an on-premise NuGet feed that is connected to Azure across an ExpressRoute gateway and the K8s cluster is connected to that virtual network, will Azure Dev Spaces be able to pull packages from it?
In other words, when you say "The NuGet feed must be publicly accessible." do you mean globally public or just accessible from the K8s cluster?

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

ID: bb5ac3c4-5680-2e8f-6a4c-f908de70593a
Version Independent ID: 04ae332e-3890-6370-fe4a-7ba1f7add15b
Content: How to use a custom NuGet feed in Azure Dev Spaces - Azure Dev Spaces
Content Source: articles/dev-spaces/how-to/use-custom-nuget-feed.md
Service: azure-dev-spaces
GitHub Login: @johnsta
Microsoft Alias: johnsta

@thecontrarycat Thank you for the feedback!  We are investigating this and will get back to you shortly.


ZXingScannerFragment not working

The sample provided in the Git repo is not working either. The console output does however say "Barcode found", only that ZXing doesn't react to any results.
To reproduce, download the samples and test run the fragment scanner.

Yes, I also create my scanner activity scanner, and when I start scanning, then nothing happens when I read the QR-code

This issue was long ago.
If anyone come across this, the workaround is to add
SupportFragmentManager.ExecutePendingTransactions() right after SupportFragmentManager commit to force OnCreateView in fragement to execute correct in order to initialize the scanner correctly.
Source:

Thanks for reporting this issue!  Unforunately it took me way too long to respond 😭.  Sorry, I apologize!  Recently the source code for this project was completely refactored to modernize it.  Many PR's were included in this effort, and many bugs were hopefully fixed.  Please try out the latest 3.x series of NuGet packages (currently in prerelease).  To try and make the project more maintainable in my spare time going forward, I've decided to close all existing issues to start with a clean slate.  If you're still experiencing this issue on the newest version, please open a new issue with as much detail as possible.  Thank you for your patience and understanding!  Happy scanning!


[DO NOT MERGE] Enable Large Tensor Support : Stage2

Description
This PR enables Large Tensor Support(LTS) by default on master for platforms that were not covered by https://github.com/apache/incubator-mxnet/pull/18625.
DO NOT MERGE BEFORE THIS PR: https://github.com/apache/incubator-mxnet/pull/18625
Progress of Large Tensor Support tracked here: https://github.com/apache/incubator-mxnet/issues/17331
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot add [pr-awaiting-review]

@leezu @ChaiBapchya @josephevans Please review

Not required as I have already enabled large tensor by default #18625

Not required as I have already enabled large tensor by default #18625


Update README.md

Fix spelling
PR Checklist
Please check all that apply to this PR using "x":

[X] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[X] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[X] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number:
What is the current behavior?
What is the new behavior?
Other information

@josteinl thanks :v:


When using VS Code with a remote server (via SSH), Jupyter Notebook’s working directory does not correctly reflect the directory where the .ipynb file is located. Instead, %pwd always returns the path to the root of the workspace (e.g., Src), regardless of the location of the opened notebook file.

Does this issue occur when all extensions are disabled?: when I run %pwd at local home/Src/ray/a.ipynb,  return home/Src/ray as expected.

Problem:
When using VS Code with a remote server (via SSH), Jupyter Notebook’s working directory does not correctly reflect the directory where the .ipynb file is located. Instead, %pwd always returns the path to the root of the workspace (e.g., Src), regardless of the location of the opened notebook file.
Environment:
•	Local OS Version: macOS Sonoma 14.6.1, M1pro
•	VS Code Version: 1.92.2 (Universal)
•	Remote Extension: Remote - SSH latest version
•	Jupyter Extension Version: latest
•	Remote Server OS: Scientific Linux 7.9 (Nitrogen), based on: RHEL, CentOS, Fedora
•	Jupyter Notebook Version:  IPython          : 8.26.0
ipykernel        : 6.29.5
ipywidgets       : 8.1.3
jupyter_client   : 8.6.2
jupyter_core     : 5.7.2
jupyter_server   : 2.14.2
jupyterlab       : 4.2.4
nbclient         : 0.10.0
nbconvert        : 7.16.4
nbformat         : 5.10.4
notebook         : 7.2.1
qtconsole        : 5.5.2
traitlets        : 5.14.3
Steps to Reproduce:
1.	Open VS Code and connect to a remote server using SSH.
2.	Navigate to a subdirectory (e.g., home/user/Src/ray) and open a Jupyter Notebook file (a.ipynb).
3.	Run %pwd in a cell of the notebook.

Expected Behavior:
%pwd should return the path to the ray directory (where a.ipynb is located).
Actual Behavior:
%pwd returns Src, the root directory of the workspace, instead of the directory containing the notebook file.
Solutions Attempted
1.	Configured VS Code Remote Settings:
•	Added "jupyter.notebookFileRoot": "${fileDirname}" to .vscode/settings.json and verified in both local and remote workspace settings.
2.	Manually Changed Working Directory:
•	Used %cd {fileDirname} in the notebook to manually change the directory, but this is not an automatic solution.
3.	Deleted and Reinstalled VS Code Server:
•	Uninstalled VS Code Server by removing the .vscode-server directory on the remote server and reinstalled it by reconnecting to the server, but the issue persists.
4.	Verified and Updated Extensions:
•	Ensured that both the Remote - SSH and Jupyter extensions are up to date.
    5.     run %pwd a.ipynb at local home/Src/ray/a.ipynb
    •	return home/Src/ray as expected.

Request for Help
Despite trying the above solutions, the working directory in Jupyter Notebook does not reflect the location of the a.ipynb file. Assistance in resolving this issue or any additional suggestions would be greatly appreciated.

Please could you enable logging as follows:

Open settings & go into Jupyter->Logging
Change the value to trace
Reload VS Code,
Attempt to repro the issue & then copy the output from the Jupyter output panel (use the command Jupyter: Show Output to get to the logs).


A few suggestions

Hi, great plugin for clue scroll enthousiasts :) I do have a few suggestions.

Add Nature impling jar for hard clues, they are currently the cheapest jar to obtain hard clue scrolls from.
Would it be possible for the plugin to check the bank for clue scrolls? Right now it doesn't hide them if you have a clue in the bank.
I think it would be better if the plugin would just hide/remove the "Loot" menu option on the item instead of hiding the item itself. I think it's a bit weird to have your inventory full of invisible items. It also glitches when switching tabs.

Thanks for the feedback! I'll work on the changes once I get a chance.

I'll add nature impling, as well as crystal imps for elites.
Removing the option while you have a clue in the bank I feel could cause frustration or confusion for users if they turned this on at one point, forgot about it, and are hunting implings for other loot at some later point and don't know why they can't open their jars.
I'm new to the runelite api, I'll poke around a bit and try to find how to remove menu options

Big +1 on just hiding the loot option.  I got this plugin a couple weeks ago and just saw it in action for the first time, I was SO confused lmao


Fix CSS Media Queries for mobile header text on certain form factors

[ ] A little too close together

[ ] I want in the tablet case to make the paragraph text flow as one line across the top and make it all tuck in more

[x] Got the navbar text to disappear when the screensize gets too small!

Paragraph expands whole header bar. I don't know how to change this. I may have to look into the animated header for both things to see if there is any fancy CSS or JS going on.

Split other items into separate issues.


DVC is not picked up from conda environment

Related to #1791
DVC installed into Conda in not picked up by the extension (while Python extension activates is well).
To reproduce. Install mini conda, install dvc vis pip install dvc. Try to run a project in any DVC repo.
https://user-images.githubusercontent.com/3659196/184040749-4740d123-4348-40dc-8bf9-6ea1a2dc5e45.mov

I think that the Python extension returns something like conda run for the python executable for conda based environments. Hopefully should be a straightforward fix.

I am unable to recreate this issue. Steps that I went through:

Install miniconda from https://docs.conda.io/en/latest/miniconda.html
install dvc into base environment with pip  => /opt/miniconda3/bin/dvc
Try to auto activate extension (does not work).
Set base conda environment as the python interpreter for the workspace (works).

Demo
https://user-images.githubusercontent.com/37993418/184560153-fe2c7516-7baf-4bad-948c-9f640fbc7d65.mov
Did you miss step 4 or have I oversimplified the problem?

Yep, I think I didn't do 4. Conda by default changes shell rc files to initialize itself, and it was not needed to do an extra setup. But I see that it would be needed if I had to run something more complicated (debug, etc).
I think what would be helpful is to show current Python interpreter in the error message?

How about this:
https://user-images.githubusercontent.com/37993418/184561231-07cff991-64db-40e6-8ad9-dd2a78a4895d.mov

Can we put an explicit message - DVC is not found in the currently active Python env: ""?


Constants in default struct fields are not accessible

The following snippet should compile
const C: Int = 0b0001;

message Foo {
    asset0type: Int as uint4 = C;
}

but it fails with the following error message:
Syntax and type checking failed
Error: test.tact:4:32: Cannot evaluate expression to a constant: cannot evaluate declared constant "C" as it does not have a body
Line 4, col 32:
  3 | message Foo {
> 4 |     asset0type: Int as uint4 = C;
                                     ^
  5 | }

Kudos to @a-bahdanau for uncovering this

Looks like we have circular dependencies here:
https://github.com/tact-lang/tact/blob/b8c07e1c48373d69bbb77956a57ba4217f106124/src/types/resolveDescriptors.ts#L2177-L2180
On the one hand, we need to process fields first and then constants, and on the other hand (this issue) we need to process constants first 🤔

This code is too weird for me:
const MY_CONST: Int = S{}.f

struct S { f: Int = 42 }

The correct code should probably be:
const MY_CONST: Int = 42

struct S { f: Int = MY_CONST }

The first example uses weird reverse logic and it seems it should be banned in favor of the second option, which is much more logical.

I meant Tact:
import "@stdlib/deploy";

const MY_CONST: Int = S{}.f

struct S { f: Int = 42 }

    TactParseError: test/main.tact:5:1: Parse error: expected "}", ";", ".", "!!", "(", "%", "/", "*", ">>", "<<", "-", "+", "==", "!=", "<=", "<", ">=", ">", "^", "&", "&&", "|", "?", or "||"

    Line 5, col 1:
      4 |
    > 5 | struct S { f: Int = 42 }
          ^
      6 |

But even if TS supports this way, for me writing code this way still looks strange, IMHO

Could you please elaborate? From what I see, that's just a regular initializer expression, and no matter where expressions happen, they should be just that: expressions.
The S{}.f probably should be (S{}).f.

The proper way would be something in lines of
Suffix       = expression:Primary suffixes:Suffix*;

Suffix
    = SuffixUnboxNotNull
    / SuffixCall
    / SuffixFieldAccess;

SuffixFieldAccess = "." id;

// Order is important
Primary
    = ...
    / StructInstance
    / ...;

Could you please elaborate?

I may be too harsh with the ban, but for me such an inversion of logic confuses the code. Instead of assigning a literal value to the constant and using it, we use the value of a field from some structure:
const MY_CONST: Int = S{}.f

struct S { f: Int = 42 }

In this case, there is no direct connection between the MY_CONST and the S.
But in
const MY_CONST: Int = 42

struct S { f: Int = MY_CONST }

there is a specific connection that is easy to find and the code is much more logical.
Perhaps if unification of these two cases would be too difficult, then I would choose the second option to support, and the first would be banned.

These two snippets have different semantics. Assume that instead of 42 there is a getNextId() call. Now first example takes an id generated for some exact object, and second example generates an id once per struct.
I'm unsure which option is correct in given case, but in general both should be valid.

Hmm, I think I get it, thank you very much for the explanation!


Couldn't get digest: digest not found in []

Error:
./manifesto put hello-world:latest test test.json
Couldn't get digest: digest not found in []

Hi @i4specete, I think the problem is that you're trying to add data to an image repo that you don't own in the registry. You'd need to do something like this to create your own version of the repo:
docker tag hello-world:latest <yourname>/hello-world:latest
docker push <yourname>/hello-world:latest

Then you should be able to do
./manifesto put <yourname>/hello-world:latest test test.json

Hi,
I tried you said me but the error persists...
To replicate the error:
docker pull hello-world
docker tag hello-world pecete/hello-world
./manifesto put pecete/hello-world:latest  test test.json
Error:
Storing metadata 'test' for 'pecete/hello-world:latest'
Couldn't get digest: digest not found in []
Regards

Another error is that when you put ":" in the repo name the tool split that beacuse the tool think that is the tag.
localhost:5000/

You will need to login to the Hub registry first using,
docker login -u  -p
and run,
docker push /hello-world:latest
Then you should be able to do,
./manifesto put /hello-world:latest test test.json

Thanks for that - the login is a good point (I'll add that to the readme now) and we should also parse the repo name better.

Registry name issue now covered by #9, I think everything else in this issue is dealt with so I'm closing. Please comment or raise new issues if I missed something.


1823825 | Message fixes | Address validation issues | 4

This PR is for user story 1823825.
Fixed an issue with duplicate H1s.
If these changes are not appropriate, please let me know. I'm only trying to clean up validation issues in this repo. So I can easily close this PR or modify it in whatever way is best for the content.

Docs Build status updates of commit 4e50f5a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/core/how-to-add-a-catch-exception-block4.md
:warning:Warning
View
Details

biztalk/core/how-to-add-a-catch-exception-block6.md
:warning:Warning
View
Details

biztalk/core/how-to-add-a-fault-message1.md
:warning:Warning
View
Details

biztalk/core/how-to-add-a-message-for-an-exception2.md
:warning:Warning
View
Details

biztalk/core/how-to-add-a-scope-shape1.md
:warning:Warning
View
Details

biztalk/core/how-to-add-a-scope-shape3.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md
:bulb:Suggestion
View
Details

biztalk/core/handling-string-values1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block3.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-message-for-an-exception1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape4.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-assign-message-context-property-values1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-avoid-disk-contention1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-configure-the-http-receive-adapter1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-create-a-send-port1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-identify-bottlenecks-in-the-messagebox-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-analysis-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-archive-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-notification-services-databases2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-primary-import-database1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-star-schema-database1.md
:bulb:Suggestion
View
Details

biztalk/core/importing-schemas-into-biztalk-server-projects1.md
:bulb:Suggestion
View
Details

biztalk/core/deploying-biztalk-adapter-for-jd-edwards-enterpriseone.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-a-catch-exception-block4.md

Line 31, Column 1196: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-21-exceptionhandling-message3test.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block6.md

Line 57, Column 10: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-20-exceptionhandling-constructmessage.gif'. Alt text is required for accessibility.
Line 65, Column 10: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-21-exceptionhandling-message3test.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-fault-message1.md

Line 62, Column 10: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-17-exceptionhandling-addscope.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Fault Message' is duplicated in 'core/how-to-add-a-fault-message1.md(2,14)', 'core/how-to-add-a-fault-message2.md(2,14)'.

biztalk/core/how-to-add-a-message-for-an-exception2.md

Line 36, Column 4: [Warning-alt-text-missing] Missing alternate text for image '../core/media/jdeoneworld-03-addscope.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Message for an Exception' is duplicated in 'core/how-to-add-a-message-for-an-exception1.md(2,14)', 'core/how-to-add-a-message-for-an-exception2.md(2,14)', 'core/how-to-add-a-message-for-an-exception3.md(2,14)'.
Line 23, Column 1: [Suggestion-duplicate-h1s] H1 'How to Add a Fault Message' is duplicated with other articles: 'core/how-to-add-a-fault-message2.md(21,1), core/how-to-add-a-message-for-an-exception2.md(23,1)'. First level headings must be unique within a docset.

biztalk/core/how-to-add-a-scope-shape1.md

Line 30, Column 6: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-18-exceptionhandling-insertscope.gif'. Alt text is required for accessibility.
Line 40, Column 6: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-19-exceptionhandling-newexception.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape3.md

Line 27, Column 6: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-18-exceptionhandling-insertscope.gif'. Alt text is required for accessibility.
Line 37, Column 6: [Warning-alt-text-missing] Missing alternate text for image '../core/media/siebeladapter-19-exceptionhandling-newexception.gif'. Alt text is required for accessibility.
Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How BizTalk Server Solves the Business Need' is duplicated in 'adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md(2,14)', 'adapters-and-accelerators/accelerator-rosettanet/how-biztalk-server-solves-the-business-need1.md(2,14)'.

biztalk/core/handling-string-values1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Handling String Values' is duplicated in 'core/handling-string-values1.md(2,14)', 'core/handling-string-values2.md(2,14)'.

biztalk/core/how-to-add-a-catch-exception-block1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-message-for-an-exception1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Message for an Exception' is duplicated in 'core/how-to-add-a-message-for-an-exception1.md(2,14)', 'core/how-to-add-a-message-for-an-exception2.md(2,14)', 'core/how-to-add-a-message-for-an-exception3.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape4.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-assign-message-context-property-values1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Assign Message Context Property Values' is duplicated in 'core/how-to-assign-message-context-property-values1.md(2,14)', 'core/how-to-assign-message-context-property-values2.md(2,14)'.

biztalk/core/how-to-avoid-disk-contention1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Avoid Disk Contention' is duplicated in 'core/how-to-avoid-disk-contention1.md(2,14)', 'technical-guides/how-to-avoid-disk-contention2.md(2,14)'.

biztalk/core/how-to-configure-the-http-receive-adapter1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Configure the HTTP Receive Adapter' is duplicated in 'core/how-to-configure-the-http-receive-adapter1.md(2,14)', 'core/how-to-configure-the-http-receive-adapter2.md(2,14)'.

biztalk/core/how-to-create-a-send-port1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Create a Send Port' is duplicated in 'core/how-to-create-a-send-port1.md(2,14)', 'core/how-to-create-a-send-port2.md(2,14)'.
Line 21, Column 1: [Suggestion-duplicate-h1s] H1 'Create a Send Port' is duplicated with other articles: 'core/creating-send-ports1.md(18,1), core/how-to-create-a-send-port1.md(21,1)'. First level headings must be unique within a docset.

biztalk/core/how-to-identify-bottlenecks-in-the-messagebox-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Identify Bottlenecks in the MessageBox Database' is duplicated in 'core/how-to-identify-bottlenecks-in-the-messagebox-database2.md(2,14)', 'technical-guides/how-to-identify-bottlenecks-in-the-messagebox-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-analysis-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Analysis Database' is duplicated in 'core/how-to-move-the-bam-analysis-database2.md(2,14)', 'technical-guides/how-to-move-the-bam-analysis-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-archive-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Archive Database' is duplicated in 'core/how-to-move-the-bam-archive-database2.md(2,14)', 'technical-guides/how-to-move-the-bam-archive-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-notification-services-databases2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Notification Services Databases' is duplicated in 'core/how-to-move-the-bam-notification-services-databases2.md(2,14)', 'technical-guides/how-to-move-the-bam-notification-services-databases1.md(2,14)'.

biztalk/core/how-to-move-the-bam-primary-import-database1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Primary Import Database' is duplicated in 'core/how-to-move-the-bam-primary-import-database1.md(2,14)', 'technical-guides/how-to-move-the-bam-primary-import-database2.md(2,14)'.

biztalk/core/how-to-move-the-bam-star-schema-database1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Star Schema Database' is duplicated in 'core/how-to-move-the-bam-star-schema-database1.md(2,14)', 'technical-guides/how-to-move-the-bam-star-schema-database2.md(2,14)'.

biztalk/core/importing-schemas-into-biztalk-server-projects1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Importing Schemas into BizTalk Server Projects' is duplicated in 'core/importing-schemas-into-biztalk-server-projects1.md(2,14)', 'core/importing-schemas-into-biztalk-server-projects2.md(2,14)'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1f2639a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md
:bulb:Suggestion
View
Details

biztalk/core/handling-string-values1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block3.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block4.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-catch-exception-block6.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-fault-message1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-message-for-an-exception1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-message-for-an-exception2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape3.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-add-a-scope-shape4.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-assign-message-context-property-values1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-avoid-disk-contention1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-configure-the-http-receive-adapter1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-create-a-send-port1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-identify-bottlenecks-in-the-messagebox-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-analysis-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-archive-database2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-notification-services-databases2.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-primary-import-database1.md
:bulb:Suggestion
View
Details

biztalk/core/how-to-move-the-bam-star-schema-database1.md
:bulb:Suggestion
View
Details

biztalk/core/importing-schemas-into-biztalk-server-projects1.md
:bulb:Suggestion
View
Details

biztalk/core/deploying-biztalk-adapter-for-jd-edwards-enterpriseone.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How BizTalk Server Solves the Business Need' is duplicated in 'adapters-and-accelerators/accelerator-hl7/how-biztalk-server-solves-the-business-need2.md(2,14)', 'adapters-and-accelerators/accelerator-rosettanet/how-biztalk-server-solves-the-business-need1.md(2,14)'.

biztalk/core/handling-string-values1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Handling String Values' is duplicated in 'core/handling-string-values1.md(2,14)', 'core/handling-string-values2.md(2,14)'.

biztalk/core/how-to-add-a-catch-exception-block1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block4.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-catch-exception-block6.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Catch Exception Block' is duplicated in 'core/how-to-add-a-catch-exception-block1.md(2,14)', 'core/how-to-add-a-catch-exception-block2.md(2,14)', 'core/how-to-add-a-catch-exception-block3.md(2,14)', 'core/how-to-add-a-catch-exception-block4.md(2,14)', 'core/how-to-add-a-catch-exception-block5.md(2,14)'....

biztalk/core/how-to-add-a-fault-message1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Fault Message' is duplicated in 'core/how-to-add-a-fault-message1.md(2,14)', 'core/how-to-add-a-fault-message2.md(2,14)'.
Line 23, Column 1: [Suggestion-duplicate-h1s] H1 'Add a Fault Message' is duplicated with other articles: 'core/how-to-add-a-fault-message1.md(23,1), core/how-to-add-a-message-for-an-exception2.md(23,1)'. First level headings must be unique within a docset.

biztalk/core/how-to-add-a-message-for-an-exception1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Message for an Exception' is duplicated in 'core/how-to-add-a-message-for-an-exception1.md(2,14)', 'core/how-to-add-a-message-for-an-exception2.md(2,14)', 'core/how-to-add-a-message-for-an-exception3.md(2,14)'.

biztalk/core/how-to-add-a-message-for-an-exception2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Message for an Exception' is duplicated in 'core/how-to-add-a-message-for-an-exception1.md(2,14)', 'core/how-to-add-a-message-for-an-exception2.md(2,14)', 'core/how-to-add-a-message-for-an-exception3.md(2,14)'.
Line 23, Column 1: [Suggestion-duplicate-h1s] H1 'Add a Fault Message' is duplicated with other articles: 'core/how-to-add-a-fault-message1.md(23,1), core/how-to-add-a-message-for-an-exception2.md(23,1)'. First level headings must be unique within a docset.

biztalk/core/how-to-add-a-scope-shape1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-add-a-scope-shape4.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Add a Scope Shape' is duplicated in 'core/how-to-add-a-scope-shape1.md(2,14)', 'core/how-to-add-a-scope-shape2.md(2,14)', 'core/how-to-add-a-scope-shape3.md(2,14)', 'core/how-to-add-a-scope-shape4.md(2,14)', 'core/how-to-add-a-scope-shape5.md(2,14)'.

biztalk/core/how-to-assign-message-context-property-values1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Assign Message Context Property Values' is duplicated in 'core/how-to-assign-message-context-property-values1.md(2,14)', 'core/how-to-assign-message-context-property-values2.md(2,14)'.

biztalk/core/how-to-avoid-disk-contention1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Avoid Disk Contention' is duplicated in 'core/how-to-avoid-disk-contention1.md(2,14)', 'technical-guides/how-to-avoid-disk-contention2.md(2,14)'.

biztalk/core/how-to-configure-the-http-receive-adapter1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Configure the HTTP Receive Adapter' is duplicated in 'core/how-to-configure-the-http-receive-adapter1.md(2,14)', 'core/how-to-configure-the-http-receive-adapter2.md(2,14)'.

biztalk/core/how-to-create-a-send-port1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Create a Send Port' is duplicated in 'core/how-to-create-a-send-port1.md(2,14)', 'core/how-to-create-a-send-port2.md(2,14)'.

biztalk/core/how-to-identify-bottlenecks-in-the-messagebox-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Identify Bottlenecks in the MessageBox Database' is duplicated in 'core/how-to-identify-bottlenecks-in-the-messagebox-database2.md(2,14)', 'technical-guides/how-to-identify-bottlenecks-in-the-messagebox-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-analysis-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Analysis Database' is duplicated in 'core/how-to-move-the-bam-analysis-database2.md(2,14)', 'technical-guides/how-to-move-the-bam-analysis-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-archive-database2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Archive Database' is duplicated in 'core/how-to-move-the-bam-archive-database2.md(2,14)', 'technical-guides/how-to-move-the-bam-archive-database1.md(2,14)'.

biztalk/core/how-to-move-the-bam-notification-services-databases2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Notification Services Databases' is duplicated in 'core/how-to-move-the-bam-notification-services-databases2.md(2,14)', 'technical-guides/how-to-move-the-bam-notification-services-databases1.md(2,14)'.

biztalk/core/how-to-move-the-bam-primary-import-database1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Primary Import Database' is duplicated in 'core/how-to-move-the-bam-primary-import-database1.md(2,14)', 'technical-guides/how-to-move-the-bam-primary-import-database2.md(2,14)'.

biztalk/core/how-to-move-the-bam-star-schema-database1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: How to Move the BAM Star Schema Database' is duplicated in 'core/how-to-move-the-bam-star-schema-database1.md(2,14)', 'technical-guides/how-to-move-the-bam-star-schema-database2.md(2,14)'.

biztalk/core/importing-schemas-into-biztalk-server-projects1.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Importing Schemas into BizTalk Server Projects' is duplicated in 'core/importing-schemas-into-biztalk-server-projects1.md(2,14)', 'core/importing-schemas-into-biztalk-server-projects2.md(2,14)'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


cal_heatmap not working as expected

Superset version
0.17.0
Expected results
Calendar to display the metric (Count, in this case) on the date associated with the metric.
Actual results
Calendar displays the metric on the day before the date associated with the metric.
Steps to reproduce
Default example of the calendar on the default Misc Charts dashboard. Reproduced on my own data.

I am facing the same issue.

I kind of figured out why this might be happening. I was using SQLite as database, which treats timestamps in GMT \ UTC timezone. But JS considers local timezone, which is EST in my case. So it ends up reducing 1 day from the date in the database.

https://github.com/wa0x6e/cal-heatmap/issues/126

Notice: this issue has been closed because it has been inactive for 335 days. Feel free to comment and request for this issue to be reopened.