Cross Context Contamination during Nuxt SSR

Reproduction
https://codesandbox.io/p/devbox/nuxt-empty-pinia-state-race-condition-lv74z2?file=%2Fcomponents%2FMainContainer.vue%3A29%2C10-29%2C22
Steps to reproduce the bug

Reproduction Code: https://codesandbox.io/p/devbox/nuxt-empty-pinia-state-race-condition-lv74z2?file=%2Fcomponents%2FMainContainer.vue%3A29%2C10-29%2C22

Reproduction URL:

Unexpected behavior: with dangling store ref
Expected behavior: with accessing store ref from Nuxt plugin

Keep refreshing the page at a rate of 10 times per second until you see an empty store state where the elements are bordered in red.

Expected behavior
I expect that the store state should be consistent when there are multiple concurrent requests during server side rendering of Nuxt 3 app. The pinia store state seems to have been interfered with and kind of lost through the async context's operation.
I previously raised this bug as a Nuxt Bug but the author mentioned that it is actually a Pinia bug. https://github.com/nuxt/nuxt/issues/29718#issuecomment-2454721098
Actual behavior
Describe the bug
We had this bug on production after releasing our first Nuxt3 APP.
Here's the target page with the deployed fix
There is a page rendering a child component, both of them running in Nuxt 3 using the Composition API (or options API - it does not matter). The child component has a setup function that contains: const store = usePostStore() and other computed props used to display store state values on the UI.
The page component also has a setup function that contains: const store = usePostStore(). The page component also has an onServerPrefetch lifecycle hook that makes API calls on SSR. The API calls a function that goes like this:
Executes an async fetch operation.

References the store: const store = usePostStore().
Patches the store.
Makes 2 other concurrent API calls async. Each call references the store after each async call is fulfilled, and then patches the store afterwards.

More Theoretical Analysis on What's happing internally:

Mermaid Graphs with in-depth use case scenario trying to depict the root cause of the issue
Please trying uncommenting some of the graphs and commenting the rest to check different perspectives.

Additional information
Here is the catch
Accessing the page shows the post data correctly from the store state in the child component template. Sometimes, though, after refreshing the page at a fast rate, the child component renders an empty/stale state of the store. I could reproduce this in two different apps by having this code flow and logic steps.
How we quickly solved this?
In the async function that gets triggered in the onServerPrefetch of the page component, we moved the store ref to be hoisted at the root of the function.
Other solutions:

Seems to be that somehow the context is lost when this line is executed in the child component const store = usePostStore(), which can happen when the micro-task queue has unfulfilled requests.
Delaying the rendering of the child component until the data is fully loaded from the page, can solve it, as it ensures that the const store = usePostStore() gets the resolved context that was updated from/after any async operation
Accessing store reference through a plugin like here:

import { defineNuxtPlugin } from "#app";
import { usePostStore } from "../store";

export default defineNuxtPlugin((nuxtApp) => {
  nuxtApp.provide("store", usePostStore());
});

Accessing the ref like this const store = await runWtihContext(() => usePostStore())

Additional context
Tried bumping version of the following dependencies but it did not solve the issue:

Node
Nuxt
Vue
Pinia

Logs
For SSR logs: please check the console here: https://codesandbox.io/p/devbox/nuxt-empty-pinia-state-race-condition-lv74z2?file=%2Fcomponents%2FMainContainer.vue%3A29%2C10-29%2C22
For Client side logs: https://lv74z2-3000.csb.app/main

Other references which could be helpful: https://github.com/tc39/proposal-async-context

I already commented on the nuxt issue. See https://pinia.vuejs.org/core-concepts/outside-component-usage.html#Using-a-store-outside-of-a-component and https://pinia.vuejs.org/ssr/#Using-the-store-outside-of-setup- for practical solutions

@posva
If we use mapState something like this:
export default {
   computed: {
       ...mapState(usePostStore, { ... })
   }
}

Do we need to do like this???
export default {
   computed: {
       ...mapState(() => {
          const { $pinia } = useNuxtApp()
           return usePostStore($pinia)
        }, { ... })
   }
}

Looks like it is not needed based on this: https://github.com/vuejs/pinia/blob/v2/packages/pinia/src/mapHelpers.ts#L270


MS-DOS 6.22 crashes on "Starting MS-DOS" Screen

i made a MS-DOS 6.22 Boot Floppy that loads Windows 1 into RamDisk and runs it, but it's stuck at "Starting MS-DOS" , and here is console log:

note: the drivers loaded in CONFIG.SYS are:
HIMEM.SYS (XMS Manager)
EMM386.EXE (Expanded Memory Manager)
RAMDRIVE.SYS (for Creating RamDisk Drive)
Setver.exe (for Windows 1 to NOT crash on "Incorrect DOS Version" while loading)
GSCDROM.SYS (CD-ROM Driver)
and here is the floppy image:
Windows1-Ramdrive.zip

why hasn't anyone responded yet

Because people aren't paid anything for this, and therefore have no obligation to you

okay , i was just asking

You don't have to close the issue. It is still a valid issue, it just seemed you expected an immediate response as if you put a support request in at a large company that you bought a product from, which just isn't how open source software like this is.
It may or may not get fixed, but asking "why hasn't anyone responded yet" seems quite rude when it's a project people work on in their free time

okay, i didn't know this is rude .

I was probably more rude than you were, honestly


LiftTrace concept

So this is not quite what we discussed on Discord, but I hope you'll like it better since you are suspicious of the two-parameter typeclasses. This does away with that by keeping the effect used for tracing completely opaque. This enables instances for both Kleisli and IOLocal.
IMO the ugliest part of it is that users will have to wrap their program in:
trait Traceable[A] {
  def run[F[_]](implicit trace: Trace[F]): F[A]
}

Everything subject to bikeshed of course. Let me know what you think!

Yeah, just ignore everything above, I bungled it 😅 obviously the problem with an opaque effect is that you don't have any other constraints available besides Trace ... which makes it pretty useless. So back to the original idea.


Update Openflow port to 6653

We should move from 6633 to 6653 to match IANA assigned port number.
http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=openflow

We might want to try 6653, then fall back to 6633 if the port is unspecified.


Support for tables

I am guessing this has to do with the segments being treated as code blocks and markdown not running any more processing on them.
I am trying to do something like the following:
title: Rule 5.5.5
After $n$ selections of *combinations* or *sequences* with or without replacement, the formulas are as follows:
- *For all of the following: If the quantity has 2 kinds, the quantity has $N$ elements, $S = S_1$* of the first kind, and $p = p_1$, the probability for $k$ of the selections being of the kind and $n-k$ being of the second kind is:
|                               |         With replacement         |                                                   Without replacement                                                   |
|:-----------------------------:|:--------------------------------:|:-----------------------------------------------------------------------------------------------------------------------:|
|    Sequence
(Ordered)    |         $p^k(1-p)^{n-k}$         |                                       $\frac{{{N-n}\choose{S-k}}}{{N}\choose{S}}$                                       |
| Combination
 (Unordered) | ${{n}\choose{k}}p^{k(1-p)^{n-k}$ | $\frac{{{S}\choose{k}}{{N-s}\choose{n-k}}}{{{N}\choose{n}}}=\frac{{{N-n}\choose{S-k}}{{n}\choose{k}}}{{{N}\choose{S}}}$ |

Is there any way to make this work currently?
If not, I'd like to suggest MD table processing as a feature.

Just 6 minutes after posting this, I discovered I needed to have a space above the table to get it to render.  My bad.


Coin cost for cars

Costs for the cars needs to be decided on, this should be based entirely on rate at which that should be able to unlock. So playtime = cars.

See the above commit for the prices that I used.


Please invite me to the GitHub Community Organization

Please invite me to the GitHub Community Organisation.

Name: Zeapherine Islary

Discord Username(if exists): Zeapherine Islary #0056

Additional Context:

:nerd_face:

Welcome @zeapherine 🤓


MLPerf: move model dependency from program.template:mlperf-inference-bench-* to a specific program workflow

We need it to associate an MLPerf program workflow with a specific framework (ONNX, TVM, PyTorch) with a specific model (ONNX, PyTorch).

Done: https://github.com/octoml/mlops/commit/40340d5537c9e2160f21502a080ed9adf88527e3#diff-22667d99bedd57233168f6741a3b70933ced0ef1e09e37ab4f0896014e933fe6


[Bintray] Downloads (Bintray Versions renamed and not changed)

Resolves #1193

Warnings

:warning:

:books: Remember to ensure any changes to config.private in services/bintray/bintray-downloads.service.js are reflected in the server secrets documentation

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @mpetuska!

  Generated by :no_entry_sign: dangerJS against 81f6cbc2ab9f4efa0cd6a6c5657226cb28ad5e7f

When running locally I've noticed some unrelated tests and prettier scans failing. Would be nice to have a maintainer to run prettier fix every now and then to get rid of those and also have a look at the failing tests.

@mpetuska All that stuff is passing in master. I'm guessing your version of Prettier is out of sync with the lockfile. Could you try running npm ci and see if those failed scans go away?

@mpetuska

Would be nice to have a maintainer to run prettier fix every now and then to get rid of those and also have a look at the failing tests.

Prettier is required gate on our PRs, and accordingly there's no prettier issues with the latest source on our master branch.
If you look at the failed check for this PR, you can see that the prettier issues are coming from files you've added, so the formatting issues are ones you've introduced :smile:
https://app.circleci.com/pipelines/github/badges/shields/2120/workflows/943e869d-0e7d-428b-9a95-2f6aab569a0e/jobs/110156/parallel-runs/0/steps/0-107
npm run prettier:check

><EMAIL_ADDRESS>prettier:check /home/circleci/project
> prettier --check "**/*.@(js|ts|tsx|md|json|yml)"

Checking formatting...
services/bintray/bintray-downloads.service.js
services/bintray/bintray-downloads.tester.js
Code style issues found in the above file(s). Forgot to run Prettier?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>prettier:check: `prettier --check "**/*.@(js|ts|tsx|md|json|yml)"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prettier:check script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/circleci/.npm/_logs/2020-07-12T20_17_52_171Z-debug.log

Regarding the service tests, you really only need to run the tests for the service(s) you are working with as detailed in our the running service tests documentation.
That same documentation also describes the need for mentioning modified services in the PR title so those specific tests will be executed https://github.com/badges/shields/blob/master/doc/service-tests.md#pull-requests (I've updated your PR title accordingly).
We run our full suite of ~1800 service tests twice daily and we do actively monitor them. Out of that suite there's one failing test related to a known issue that's being tracked (refs #5282). Running the full suite of tests is slow and requires a lot of proper configuration, which is why we direct contributors to only run the subset of tests for a given service.
We really appreciate your PR and look forward to working with you to try to get this merged, but please do be mindful about issuing direction to the maintainer team.
As noted above, the changes here are introducing failures so please take a look at fixing them and let us know if you have any questions.
Thanks!

Thanks for the feedback. Will get them all resolved tomorrow!

P.P.S. I was trying to open up failing CI steps, however I'm getting 404 on the links. Are they supposed to be publicly available?

P.S. By no means I was implying any directions to the maintainer team (apologies if it seemed that way), but rather just noted my observations.

No worries! It's been a longstanding request so would be great to get this incorporated

P.P.S. I was trying to open up failing CI steps to try and pinpoint the issue myself, however I'm getting 404 on the links. Are they supposed to be publicly available?

They should be though I'm not sure if the new Circle UI changes impacted anything :thinking: It would be rather problematic if folks can't see the PR check logs

The other relevant thing from the logs is a unit test failure (you should be able to reproduce locally with an npm run test:core)
    BintrayDownloads auth sends the auth information as configured - sends the auth information as configured
    /home/circleci/project/services/bintray/bintray-downloads.spec.js

    AssertionError: expected { Object (label, message, ...) } to deeply equal { label: undefined, message: '69' }
        at Context.<anonymous> (services/bintray/bintray-downloads.spec.js:37:17)
        at runMicrotasks (<anonymous>)
        at processTicksAndRejections (internal/process/task_queues.js:97:5)

They should be though I'm not sure if the new Circle UI changes impacted anything 🤔 It would be rather problematic if folks can't see the PR check logs

They should be public. I wonder if you need to sign into CircleCI using your GitHub account.

Should be all now. Oddly enough, lib\logos.spec.js:34 is failing on my windows machine no matter what.

One more thing, when I run npm run prettier it changes more than half of the project's files (according to git history) so it'd probably good for a maintainer to run and commit linter on all repo to have it consistently formatted (again, might be just an issue on my machine)

One more thing, when I run npm run prettier it changes more than half of the project's files (according to git history) so it'd probably good for a maintainer to run and commit linter on all repo to have it consistently formatted (again, might be just an issue on my machine)

There's definitely something going on with your machine, or perhaps Windows in general :eyes: Amongst the maintainer team there's a mix of Mac/Linux/Windows usage and I'm not aware of anyone else seeing this.
By any chance do you have git's auto crlf config setting enabled?
For reference on my machine:
$ git branch
  code-of-conduct
  dependabot/npm_and_yarn/typescript-3.9.6
* master
  pr/5270
  restore-cors-injection-4171
  website-service-test
$ git pull
Already up to date.
$ npm run prettier:check

><EMAIL_ADDRESS>prettier:check /home/caleb/dev/shields
> prettier --check "**/*.@(js|ts|tsx|md|json|yml)"

Checking formatting...
services/visual-studio-app-center/visual-studio-app-center-releases-osversion.seservices/visual-studio-app-center/visual-studio-app-center-releases-osversion.teservices/visual-studio-app-center/visual-studio-app-center-releases-size.serviceservices/visual-studio-app-center/visual-studio-app-center-releases-size.tester.services/visual-studio-app-center/visual-studio-app-center-releases-version.servservices/visual-studio-app-center/visual-studio-app-center-releases-version.testservices/visual-studio-marketplace/visual-studio-marketplace-azure-devops-instalservices/visual-studio-marketplace/visual-studio-marketplace-azure-devops-instalservices/visual-studio-marketplace/visual-studio-marketplace-downloads.service.js

All matched files use Prettier code style!

How about now?

If you are running prettier and it wants to reformat everything, is it possible you've installed prettier globally (npm install -g) and you're running an old version (1.x) instead of the one in the project requirements?

I'm a little confused where we're planning to go with this one. Is there indeed a native/supported API we can use (albeit one with limited variants for download stats)? My understanding is that there is not, so the outstanding question for us (@badges/shields-maintainers) is whether we want to add this badge with the current implementation that uses an undocumented/unsupported, but functional, API.
Do I have that right?

We could add the variant for latest version only using the public API - its the 'all versions' and 'specific version' variants where that is an issue.

Caleb, correct. Either merge it or decline it. Everything was tried and discussed already and current version is the best we can get at the moment given bintray api limitations

I don't think we've ever contacted Bintray regarding the API throttling limitations. Maybe it's something worth trying? As an example Discord has recently provided us with a custom token with significantly higher rate limits (see #5346). And even if they refuse to do anything, we can at least flag up that we'll have to use their undocumented API instead.

I don't think we've ever contacted Bintray regarding the API throttling limitations. Maybe it's something worth trying?

The main (or at least first) problem here with the official API is more about permissions/auth. The officially documented/supported APIs for the full set of download stats requires auth from a user with read/write scope, so our badge servers couldn't use a Shields-owned token anyway regardless of rate limits. We also can't accept user-provided token via query/route param parameters from users because the Bintray API tokens do not support read-only scoping.
There's an official/documented API that provides download stats just for the latest version of a package, and this endpoint can be used anonymously and is not rate limited (like the similar API endpoints we use for the bintray version badges). There's also unofficial/undocumented APIs that provide anonymously accessible (presumably non-rate limited, but not known definitively) download stats for typical variants (including total download counts).
As things stand today, those are the only two options I see for Shields to be able to provide some form of download-related badges for Bintray, and IMO the question is more so which of those two options we'd prefer:

Official/documented endpoint with limited download variant support
Unofficial/undocumented endpoint with full variant support

Perhaps there's a dialog to be had with the JFrog folks to see if there's a better option that could be created which we could move to eventually, but I think it'd be good to figure out how we'd like to proceed tactically with this PR.

Thanks for clarifying. My gut feeling would be option 2 and contacting JFrog  to discuss a possible better option for the future.

Thanks for clarifying. My gut feeling would be option 2 and contacting JFrog to discuss a possible better option for the future.

Excellent, thanks! So that's one definitive vote for using the undocumented APIs, and two, Chris and myself, that have expressed some unease with this option. I don't think my unease rises to the point of being firmly against this option, so I could get on board if the maintainer team collectively wants to move forward with this.  In that case though I think it would be helpful to pin an issue or create a discussion conveying this may be a trial attempt that could have to be reverted should any issues arise.
The challenge with the first option as I see it is that IMO the primary use case for a download stats badge is the total, with some cases for yearly/monthly trends. I know there's also use cases where folks want version-specific download counts but think that's a comparatively smaller slice (especially with only being able to use "latest" as would be the case here).

Just to clarify, only the latest version badge needs to make additional call to fetch later version. Total and specific version badges both make just a single call

Just to clarify, only the latest version badge needs to make additional call to fetch later version. Total and specific version badges both make just a single call

Not sure I understand. What's that intended to clarify?

(especially with only being able to use "latest" as would be the case here).

This

(especially with only being able to use "latest" as would be the case here).

This

Then I'm even more confused :smile:
Are you saying that it's possible to get the total download stats across all versions using the official/documented/supported API endpoints anonymously? It was my understanding that was explicitly confirmed to not be the case in the above thread, and is the driver of the circumstances leaving us with the two options as I summarized in https://github.com/badges/shields/pull/5316#issuecomment-665412650.

Oh, here's a recap of bintray situation:

The only endpoint we can use from documented api is latest version name (used by version badge already)
Anything that deals with statistics can only be done via undocumented api for now
Total downloads and downloads of specific version can be extracted with a single api call
Downloads for the latest version require additional api call to fetch latest version name

Hope this helps.

Thank you for the response @mpetuska. Though I'm not 100% sure I'm clear on the answer. My understanding from the thread, particularly the latter dialog between you and Chris, was that it was possible to get the download counts for the latest version of a package  utilizing official APIs, but only for the latest version. However, it now sounds like I've got that wrong?
Below is a breakdown that may help, can you clarify whether this is correct and/or what needs to be updated to make it accurate?
There's a straightforward binary question for the maintainer team in terms of whether we're willing to accept and utilize an undocumented/unsupported API, and I'm really just trying to succinctly summarize the options in terms of the what (which download badges could we possibly provide) so other maintainers can more easily weigh in. This will be helpful since we're not all experts on the bintray APIs and this thread has gotten too long to expect folks to read and digest every comment.

API
Total downloads (all time)
Trending downloads (yearly/monthly/weekly)
Total downloads (specific version)
Total downloads for latest version

Undocumented/unsupported
Yes
No
Yes
Yes

Official documented/supported
No
No
No
Yes

Fixed your table from my perspective.
Trending downloads can be retrieved via https://bintray.com/statistics/packageStatistics?startDate={ISO Date (e.g.: 2020-08-02T17:12:47.691Z)}&endDate={ISO Date (e.g.: 2020-08-02T17:12:47.691Z)}&pkgPath=/{subject}/{repository}/{package}

API
Total downloads (all time)
Trending downloads (yearly/monthly/weekly)
Total downloads (specific version)
Total downloads for latest version

Undocumented/unsupported
Yes
Yes
Yes
Yes

Official documented/supported
No
No
No
Not that I'm personally aware of

Fixed your table from my perspective.

Perfect, thank you!

Trending downloads can be retrieved via https://bintray.com/statistics/packageStatistics

Interesting, this looks like another undocumented API, correct?

It does have some limitations for packages not linked to jcenter

Could you elaborate on these limitations? My first thought/question when I saw this was whether we could just use this across the board (provided the package path could incorporate the version when needed)

Interesting, this looks like another undocumented API, correct?
Correct
Could you elaborate on these limitations? My first thought/question when I saw this was whether we could just use this across the board (provided the package path could incorporate the version when needed)

All undocumented apis are available for public bintray packages. You can get total downloads for all packages, but for trending downloads for the packages that are not linked to jcenter you can only request up to 30d history. For jcenter linked packages this limitation is not present.
Furthermore, you can certainly request trending stats for explicit version by adding versionPath=/{subject}/{repository}/{package}/{version} query param. e.g.: https://bintray.com/statistics/versionStatistics?startDate=2020-07-27T05:41:27.727Z&endDate=2020-08-03T05:41:27.727Z&pkgPath=/mpetuska/lt.petuska/kotlinx-html&versionPath=/mpetuska/lt.petuska/kotlinx-html/0.7.3

You can get total downloads for all packages, but for trending downloads for the packages that are not linked to jcenter

And what is jcenter? Do you know what portion of public packages on bintray are not linked to jcenter?

Jcenter is maven central equivalent for gradle mostly. Most if not all stable public packages are linked to jcenter

Furthermore, if the user is generating a badge for his bintray repo, he'll most likely be aware of these limitations. Also linking to jcenter can be done with two clicks and is pretty seemless

Thanks @mpetuska that's helpful. We discussed this one earlier today and have agreed we can move forward with the utilization of these undocumented APIs. One addition is that we will want to add some extra help texts to the examples that conveys some of the constraints (usage of undocumented APIs that may break beyond our control, jcenter requirement for interval/trending downloads, etc.).
I'll take another pass through this in the next day or two, but other than the additional help text I believe this PR will be in good shape for merging.
Thanks for all your hard work on this one!

Great news! I take it you'll make the extra commit for those texts yourselves?

I take it you'll make the extra commit for those texts yourselves?

I'd rather do that as part of this PR. I don't trust myself to accurately (and succinctly) describe the jcenter piece :laughing:

Actually, I forgot that the trending download variants weren't included here. Would you be interested in incorporating that within this PR? I'd prefer deferring that to a follow up PR, though at a minimum we should probably update the badge route to include the variant option (so that others can be added later without breaking the routes/requiring redirectors)


issue about signals

I use Lua as extensions for my program. I noticed a problem: the signal is outside the built-in main loop. This causes my program freezes if a signal is received. I wanted to give an interface for extensions to connect signal inside the program, but LUA can't do that because I can't get the pointer of a function in Lua. Is there any workaround?

@ekd123, this issue is almost a decade old.
I wonder whether it has been fixed and you would close it.
Many thanks for your help.


[BUG] Unable to setup backup-target with error: There is a VM either in the process of creating or deleting

Describe the bug
https://github.com/harvester/harvester/assets/5169694/73ac1dd0-4e34-4d6d-bbfc-8163945a383d
To Reproduce
Steps to reproduce the behavior:

Install Harvester with any nodes
Setup backup-target
Create an image for VM creation
Create VM vm1 and take backup vm1b
Restore vm1b into new VM VM1r
Reset backup-target to default value
Setup backup-target

Expected behavior
We should able to change backup-target, there haven't any VMs.
Environment:

Harvester ISO version: v1.2-a9968541-head
ui-source Option: Auto
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal DL360 4 nodes

Additional context
I'm not 100% sure that the root cause is related to #4544, but hit the bug after it.  (so I labeled reproduce/often not reproduce/always)
Support bundle
The SB size is too large (>25MB), separated into following:
harvester-tchfx.zip
harvester-d5hzw.zip
harvester-d2csm.zip
harvester-gv6lk.zip
supportbundle_c6db0211-4e97-404e-bb78-72f4606f5a86_2023-09-19T14-55-03Z.zip

After some investigation, I think we may need to prevent users from giving uppercase letters.
VirtualMachineRestore encountered error
VirtualMachine.kubevirt.io "VM1r" is invalid: metadata.name: Invalid value: "VM1r": a lowercase RFC 1123 subdomain mus
t consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.
g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

Encountering this without restore invalid VM name, the root cause might not be the same as #4544

Confirmed that the bug caused by #4544, so this issue would be closed along with #4544.
For users encountered this, it could be fix by following commands:
# list all restores, and find the stuck one
kubectl get virtualmachinerestores.harvesterhci.io -A
# delete it
kubectl delete virtualmachinerestores.harvesterhci.io  -ndefault <THE_STUCK_RESTORE_NAME>

this issue could be close along with #4552

Close along with #4552


Ammends SearchStocks Type

Context
search Endpoint returns a Promise but declared as RawStockSearch  instead. According to
What was done?
According to search tests, used as an async call, it's clear the Endpoint returns. a Promise.
https://github.com/zackurben/alphavantage/blob/master/test/data.js#L94

Coverage decreased (-77.0%) to 16.97% when pulling 41c29e161069493ae326b4358138004f78c22aec on ArianZargaran:ammend-searchstocks-type into d7cb8d45b2dadb979bc89830a0c7078f58f04ef3 on zackurben:master.

Thanks for the contribution, sorry for the delay!

Thanks for the contribution, sorry for the delay!


Fix 4 bugs

Removes delete prompt
Removes GUI of register and login
Fixes the bug of person disappearing after undo the edit
Enables the edit of tags of a person (> userid /tag xxx). I have confirmed this with Prof and he says it's allowed to be fixed.

lgtm!


adding color and no-color support for cli output

:tada: This issue has been resolved in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Hooking an optional delegate method that isn't implemented

Basically I want to add aspects to a datasource/delegate of a UITableView.
Obviously UITableView has lots of optional callbacks.
In many of my use cases the data source/delegate doesn't implement the optional methods, but I still need a way to forward the table view calls to my hooks.
In this example I need to return a different height for certain cells but I get an error "AspectErrorDoesNotRespondToSelector".
token = [object
           aspect_hookSelector:@selector(tableView:heightForRowAtIndexPath:)
           withOptions:AspectPositionInstead
           usingBlock:^(id <AspectInfo> info,UITableView *tableView,NSIndexPath *indexPath) {
                  // replace the original implementation with different calculation
                  // object doesn't implement the method...
                  // hook fails :(
             }error:&error];

Any suggestion how to go about adding the method dynamically to the class and then hooking?
Thanks

I'm running into the exact same scenario, with the added wrinkle of using Swift. Any advice would be greatly appreciated!

@avnerbarr I have the same problem.   Have you solved it？

You would need to add the method at runtime to the delegate class and then hook it. Which version of the library are you using? Perhaps this feature was added?


support RNA sequence in gb file

1 support reading the RNA type info from locus line in gb file
2 for RNA, use 'U' as the complement base

Hi @tnrich, I added some code to enhance the existing the RNA parser for gb file. Please help review it, thanks.

close this to use another PR


startConversastion under IE11

Hello everyone,
We meet some strange issues while trying to integrate our chatbot into a client's host page (under liferay I believe). Indeed, everything works fine under chrome and firefox, but not for IE11.
While using IE11, we got a 401 during the startConversation http call, and the reason is that :
normally, the startConversation func send an empty body for post call, but under ie11, we don't know why, the body is changed to "undefined" as a string (http header has also been updated with "Content-Type	text/plain;charset=UTF-8").
Yesterday, I tried to add "body:undefined" into the function, but it does not help.
(now, I tried again to use "body:{}", let's wait and see)
Appreciated if you got some experiences to share about this.
Thanks a lot

Hi @jacyuan.
Do you think your page loaded a polyfill that will interfere with XMLHttpRequest?
For example, if you open F12 console and type XMLHttpRequest, do you see [native code] like the screenshot below?

It sounds like something is interfering with Observable.ajax() function, which will in turn call XMLHttpRequest.
I checked the network traffic when using IE11 with DirectLineJS, it did not send undefined as the body.

So I am guessing something loaded in your page that interfere with XMLHttpRequest and it is buggy about body: undefined.

Hi @compulim,
I think you're right.
Indeed, direct line works well alone under IE11, but since our client integrated the chatbot under  liferay, this might be the reason for this issue (maybe caused by liferay, or maybe caused by the codes of our client).
While debugging this morning under IE11, I do see things (more specifically errors) in a js file, loading xmlHttpRequest functions (prototype). I was thinking about some kind of "transcription", or calls to lower level libraries, which translate incorrectly an empty body. But since I'm not really familiar with this part, I didn't go further.
But yes, this makes sense.
Thanks


Add github action for coding style checking

This should be resolved before #1

Later we might run testcases in github action too, but at this point - coding style only.


[nginx-ingress-controller] Proxy protocol for TCP services

There is a possibility to use Proxy protocol when Nginx accepts traffic from L4 proxy.
But is there a possibility to enable Proxy protocol for exposed TCP services via Nginx Ingress Controller, so those services will receive a real client IP?
Something like following HAProxy configuration:
    frontend ft_pop3_secure
        bind :995
        mode tcp
        log global
        option tcplog
        default_backend bk_pop3_secure_dovecot

    backend bk_pop3_secure_dovecot
        mode tcp
        log global
        option tcplog
        server dovecot server.mail.svc.cluster.local:995 send-proxy-v2

Actually, yes by Nginx.
But no by Nginx Ingress Controller at the moment.

@tyranron the problem with add this feature is that all the TCP apps must support proxy protocol.
Is not possible to configure the stream section per TCP service.
I need to add change the configuration in the configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: tcp-configmap-example
data:
  9000: "default/example-go:8080:PROXY"

I will add this to the TODO list

@aledbf I like that ConfigMap modification.
Would you mind if I try to contribute that?

@tyranron sure. Please open the PR in this repo instead https://github.com/kubernetes/ingress

Hey @tyranron - we have a concrete implementation/need for this at my company. We need to load balance some MQTT requests using the ingress controller. I can work with you and possibly provide some resources. We have a call with nginx on Monday to talk about this issue. I will bring up this issue comment stream.

Any progress on this one?


Upload progress is actually progress of creating a temp file?

In UploadTaskRequest.kt, the progress callback isn't sending the progress of the file upload, it's incorrectly sending the progress of writing the file to the output stream
Line 42:
    //input file data
    if (outputStream != null) {
       FileInputStream(file).use {
           it.copyTo(outputStream, BUFFER_SIZE) { writtenBytes ->
               progressCallback?.invoke(contentLength + writtenBytes, totalLength)
             }
         }
    }
  contentLength += file.length()
  contentLength += write(CRLF)

So does that mean when progress is 100%,  that the upload has been submitted to the server, but it doesn't mean that the upload has completed uploading to the remote server?

There is an old Github Gist git diff (from May 2017, not sure if this can be still applied to the current Fuel version) which fixes this issue partly: https://gist.github.com/dstd/cc5710c52c58eec6f14ee1eb229eb4de
The applied fix only works for Fuel.download.
For Fuel.upload it still reports the wrong progress.
Maybe someone can take a look and completely fix this :)

Fixed with #485


Updating Identity

Fixes #1472
and several related issues:
1462, 1465

@ardalis,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@ardalis  red box around change auth in  aspnetcore/security/authentication/identity/_static/01-mvc.png

At the right place add see account conf on how to config to prevent login at reg
https://review.docs.microsoft.com/en-us/aspnet/core/security/authentication/accconfirm?branch=pr-en-us-3652#prevent-login-at-registration

@ardalis  It looks like it wasn't a fluke. Do you want to revert my commit or would it be easier to fix up what you have? BTW, when you're happy with my PR, feel free to merge.

@Rick-Anderson I'll fix it.

@Rick-Anderson should be good to go now


Bug with Disequilibriate

Spell Disequilibriate of Mind Breaker is not working

Reworked the ability. It now constantly removed 3 armor instead of 1 and being stackable.


[BUG] Cannot set value lookup with 1 character

        XrmApp.Entity.SetValue(new LookupItem { Name = "transactioncurrencyid", Value = "円"  });

It will give error: System.InvalidOperationException: No Results Matching 円 Were Found.
The problem is the lookup now start to query after second character

@chrizz-msweb For now SetValue supports set value only with search.
Just select a value from a lookup that is not supported,
If can you perform it manually only after expanding lookup this is a new feature.


feat: useSignTransaction and useSendRawTransaction

Adds useSignTransaction and useSendRawTransaction hooks.

Working on the next major version of Wagmi and going to make it easier to add actions and framework-specific function with much less code. Going to close for now and will add your work into there so you still get credit.


Support saving the location of the cursor in files

In other editors, when you toggle between files, it opens the file to the same location it was last opened to

Good idea 👍


Add limit ipaddr=

Provide the ability to limit the inventory using an IP-prefix.  For example, I want to include only inventory records that are in the <IP_ADDRESS>/24 subnet:
netcfgbu inventory ls --limit ipaddr=<IP_ADDRESS>/24

To limit based on a list of ip subnets, for example any record in the <IP_ADDRESS>/24 or the <IP_ADDRESS>/27 subnet:
netcfgbu inventory ls --limit ipaddr=<IP_ADDRESS>/24,<IP_ADDRESS>/27

This was resolved by @thepacketgeek; thank you!.  Now available in v0.7.1
https://pypi.org/project/netcfgbu/0.7.1/


[Task]: Save user code [ToB] [Frontend]

What needs to happen?
Automatically save snippets after a user edits unit example/challenge code.
Issue Priority
Priority: 3
Issue Component
Component: beam-playground

.remove-labels awaiting triage

.take.issue

.remove-labels 'awaiting triage'

.remove-labels beam-playground

.add-labels tour-of-beam

.add-labels 'new feature'

.take-issue


Argument / Parameter Intellisense

Greetings,
I am currently not able to see intellisense for a functions arguments or parameters.
Is this currently not supported or is there an additional configuration I must set in order to get intellisense on function arguments?

Yeah, we just don't have that yet. See here for some progress.

Just checking does this close mean that it is now available ?
I see a prompt for a new Julia client update in atom
And I see the property has been merged.

Yeah, this feature is in the latest Juno release (in a somewhat limited but still very useful form).


example load all images at once

I believe that all images don't have a width and height in the beginning that makes all img tags to be smooshed tight together making the observer immediately see everything as vissible

Hi @jimmywarting, this repository is not maintained anymore as stated in the README file. You should look at the WICG polyfill or alternative libraries like hunt, the one I wrote.


Sound record clean

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #77
Description
The file cleanup for sound_record_tests is added and the issue is fixed.
Type
Type Choose one: (Bug fix | Feature | Documentation | Testing | Other)
Screenshots (if applicable)
Checklist

[x] I have read the Contribution Guidelines
[x] I have written Unit Tests
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach

My second comment is addressed:
do not raise 2 pull requests from the same branch, create a new branch with only sound_record_tests.cpp changes from main and raise new pull request

I will make the proper changes and open a new PR for sound record clean.


When i do /axir (player) does not work

i keep on trying to open somebody backup i keep on getting this screen and i'm doing the command right and such

The new syntax is /axir view


Observers are identified by name in Tracer#subscribe

Thoughts on this, @markelliot ? Goal is to make sure different observers don't trample each other.

Or maybe exactly is desired? I don't know.

how does this make it more likely observers won't trample each other?

my explanation was the opposite of what I had in mind: this makes it so that trampling must be explicit. if your library registers an "SLF4J" observer and mine does too, then this will throw. i'm a little worried that we'll end with an unbounded number of similar observers if we dedupe them by object identity.

Ok, agree this does that, though the namespacing is still unbounded, and it might be confusing to have your subscriber trampled, so we should probably add some logging if you trample but don't have object equivalence?
We can also say there's exactly one observer, and allow for a multi-observer observer that aggregates.
Practically speaking, I expect there to be ~2 observers max, ever.

the multi thing in itself doesn't quite help if someone else can come along
and replace it with something else.
i be down for (1) named observers, (2) "warn" log entry when you overwrite
an existing one (by name). deal?
On Mon, Oct 17, 2016 at 10:10 PM Mark Elliot<EMAIL_ADDRESS>wrote:

Ok, agree this does that, though the namespacing is still unbounded, and
it might be confusing to have your subscriber trampled, so we should
probably add some logging if you trample but don't have object equivalence?
We can also say there's exactly one observer, and allow for a
multi-observer observer that aggregates.
Practically speaking, I expect there to be ~2 observers max, ever.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/palantir/http-remoting/pull/268#issuecomment-254387046,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGOdwaiNbQIz8lQVZcTD5mh79eopluwlks5q1Cp5gaJpZM4KZOL3
.

Yep, that's fine.

Probably also want to warn any time size of the map grows to > 5, too.


License?

@chfi What's the license for this? MIT?
Would like to fork and extend.

Yes, it's MIT. Added the LICENSE file :)

Thanks!


Update link to Nominatim documentation

The documentation for Nominatim is no longer maintained in the OSM wiki. Point to the latest documentation on nominatim.org instead. That is the one that is valid for nominatim.openstreetmap.org.

Sure. I've amended the commit accordingly.


DB: Ambari User Creation Task not failing properly

Hi,
I'm trying to install a static inventory using postgres. I ran prepare_nodes.sh and it stops working on the ambari db user creation task.
It does not abort/fail with an error message, just keep being stuck in the task.

Can you give more infos:

OS used ?
did you try running with -vvvv ?
IMO It could be a problem running the task with become postgres user

Closing for inactivity.


TimeSync.watchClockChanges is undefined

Ran inside client's Meteor.startup().

Oh sorry, docs are out of date. This is automatically enabled now.
I will update the docs and close this issue once that is done.

That's what I figured while testing other things afterwards... Sorry I did not come back before but was at work doing other things.


Pull Request CRD: GitLab Support

Tracking issue for GitLab Pull Request support in the Pull Request CRD.
GitLab API documentation: https://docs.gitlab.com/ee/api/merge_requests.html
Existing Tekton Pull Request support (GitHub): https://github.com/tektoncd/pipeline/tree/master/cmd/pullrequest-init

AND ITS ISSUE 1000

woooooo 🎉

I think we have this now, is that right @wlynch ?

Yup! This was added in d478e7d6d576d2e309c6a42ecf8da75c536df681

@wlynch @bobcatfish is there a plan to have a guide showing build taskrun from gitlab?

Gitlab support in Triggers might be related: https://github.com/tektoncd/triggers/pull/434


DocuSign.eSign.Client.ApiException: "Error while requesting server, received a non successful HTTP code with response Body: {"error":"consent_required"}"

I tried to receive a token with the code below. Unfortunatelly I get the error:
DocuSign.eSign.Client.ApiException
  HResult=0x80131500
  Nachricht = Error while requesting server, received a non successful HTTP code with response Body: {"error":"consent_required"}

I tried with set TLS 12 and without. We run it in dev mode with base path https://demo.docusign.net/restapi
and oAuthBasePath =account-d.docusign.com
Anyone konws what is wrong?
  byte[] privateKey=DSHelper.ReadFileContent(DSHelper.PrepareFullPrivateKeyFilePath(privateKeyFilename));
            var scopes = new List<string>
                {
                    "signature",
                    "impersonation",
                };
            var basePath = ApiClient.Production_REST_BasePath;
            var oAuthBasePath = OAuth.Production_OAuth_BasePath;
            if (!production)
            {
                basePath = ApiClient.Demo_REST_BasePath;
                oAuthBasePath = OAuth.Demo_OAuth_BasePath;
            }

            var _apiClient = new ApiClient(basePath);
            ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
            var authToken = _apiClient.RequestJWTUserToken(
            clientId,
            ImpersonatedUserId,
            oAuthBasePath,
            privateKey,
            1,
            scopes);

I tried to set the consens manually URL below. But I receive the (Login Window) the error invailid Authorization: RequestType is not supported.
https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature impersonation&client_id=a5ed47d5-xxxx-xxxx-8a19-756da64391de&redirect_uri=https://www.docusign.com
Is the something wrong with my account Setting?

I found the solution. instead of  reponse_type= code I have to use token

The real issue is that you have the client id (integration key) set to Implicit grant.
That is not safe from an information security point of view.
Change the client id to NOT use implicit grant.
Then the individual consent API can use response_type=code

We choose Implicit grant we have a SPA App. I read this article.https://developers.docusign.com/platform/auth/. Is Implicit grant not correct for SPA Apps?

Is this issue still relevant?


Add Dan Steren to Contributors list

@dansteren, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?

@Roshanjossey, The tutorial was very well put together. The process itself is very straightforward. It's nice knowing that I have one PR under my belt. Now the rest should be a little easier.
One suggestions for this tutorial would be to connect it to a more typical PR. For example, when beginning this thread (the first comment where I didn't provide a description), I was a little unsure if I was supposed to add in a description. It would be nice if you provided an explanation of the things most people put in that box, standard formatting, or other advice. Could make the transition to the second PR a little easier.

@dansteren, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com


Failed to get matching snapshots

Thanks for the library. I have an issue with the latest release

Assertion Failure: MonkeyXCTest.swift:33: Failed to get matching snapshots: Timed out while evaluating UI query.

Here is my setup
func testMonkey() {
    let monkey = Monkey(frame: app.frame)
    monkey.addDefaultUIAutomationActions()
    monkey.addXCTestTapAlertAction(interval: 100, application: app)
    monkey.monkeyAround()
}

Hey there! Is the sample App working for you? Also, are you integrating the library from CocoaPods repository, or are you referencing SwiftMonkey directly from GitHub (master)?

@wojciechczerski Hi, thanks for quick response. I use CocoaPods, and I see it origins from this call addXCTestTapAlertAction

Could you try referencing SwiftMonkey in your Podfile like that:
pod 'SwiftMonkey', :git => 'https://github.com/zalando/SwiftMonkey.git'

I would like to check whether perhaps the existing code on master could solve your issue.

@wojciechczerski ja will try, and also I have this issue which happens only during monkey tests

Failed to determine hittability of Button: Unable to fetch parameterized attribute XC_kAXXCParameterizedAttributeConvertHostedViewPositionFromContext, remote interface does not have this capability.

When you fetch the code from GitHub, could you also try replacing monkey.addDefaultUIAutomationActions  with monkey.addDefaultXCTestPublicActions(app: application)? I know it's not really solving the issue but maybe using XCTest public action could at least get you going while the issue is being solved.

@wojciechczerski seems to work, thanks

@wojciechczerski any news about this issue?
I'm using the GitHub version in my Podfile (currently at 2.1.1), and the matching snapshots failure is still present.
Regarding your suggestion to use monkey.addDefaultXCTestPublicActions(app: application) --
that method does not appear to be available.
Thank you.

@adario Hey there! Is this how your Podfile looks like?
pod 'SwiftMonkey', :git => 'https://github.com/zalando/SwiftMonkey.git'

If the monkey.addDefaultXCTestPublicActions method is not present, perhaps there is some caching issue that's preventing pulling the latest version. In such case you could try deleting the Pods directory and running pod install again.

@wojciechczerski Hey there, thanks for the quick reply —
yes, my Podfile contains the :git statement to locate the pod, so I'm on the latest (I assume: pod install reports version 2.1.1).
The method is indeed missing: I've looked at the sources, and couldn't find it.

 Another thing to try could be to delete Podfile.lock. Alternatively, just to be sure you are getting the lastest sources, you could try adding this to your Podfile (as a test):
pod 'SwiftMonkey', :git => 'https://github.com/zalando/SwiftMonkey.git', :commit => '68f49bb69381103224b0e77ab615baac8b1fd750'

Please let me know whether that helps.

@wojciechczerski adding the commit ID in the Podfile (after manually removing Podfile.lock and Pods) seems to work — that is, the addDefaultXCTestPublicActions method is now visible...
Is the method supposed to work on actual devices, or only on the simulator?
Thank you.

It looks like the public actions do work on actual devices — cool!
Is it possible to add extra actions besides tap, press and drag?
Thank you.

Glad to hear it worked for you! As for adding extra actions - I am not sure. SwiftMonkey used to support quite a lot of actions, this was however possible due to usage of private APIs. These APIs do not exist anymore therefore public XCTest actions are used. Maybe it would be possible to combine these actions to simulate a pinch or rotate gestures, but I haven't checked that yet (it's still on my TODO).

@wojciechczerski I've tried adding public XCTest actions for swipe and rotate: unfortunately, they're not very useful.  That is, they are executed correctly, as well as shown by MonkeyPaws, but since they're run via the application XCUIElement instead of XCUICoordinate, they don't produce the expected results because of truly counterintuitive locations...
For instance, the rotate gesture is applied to the edges of the screen, instead of around the center of the screen, which obviously results in no rotation at all.  Conversely, the swipe gestures are applied around the screen center, instead of from the screen edges.


red-knot panics found by the py-fuzzer fuzzer

The following code snippets surfaced by the py-fuzzer script all produce red-knot panics. Some of these may be duplicates in terms of their syntax structure; I haven't tried hard to deduplicate them. I've only gone through panics found in the first 500 seeds.
To run red-knot on all failing seeds in the first 500 seeds, you can run the following command from the Ruff repository root:
uvx --from ./python/py-fuzzer fuzz --bin=red_knot 0 5 16 19 25 28 30 36 39 57 76 81 91 100 102 107 110 115 116 119 120 125 127 138 141 147 158 168 174 175 224 234 247 255 260 261 282 294 295 311 313 321 332 344 347 348 350 351 353 361 374 382 386 391 395 397 400 409 414 451 452 454 455 463 473 488 492 494 497

They are all (or at least should be) valid Python syntax.
Failing seeds
Seeds 39, 25, 19, 107, 138, 110, 115, 120, 125, 116, 147, 174, 175, 260, 294, 313, 261, 347, 282, 350, 391, 386, 374, 414, 409, 451, 455, 497
The panics in these seeds all boil down to recursive type aliases of the form
type name = name

Seed 28
class name_5[**name_4](name_5.name_5):
    pass

Seed 30
async def name_5[name_2](name_5: (name_1 and name_5)(), /):
    pass

Seed 0
type name_5 = name_2
type name_2 = name_5

Seed 76
class name_4[**name_5](name_3, name_0=name_4.name_3):
    pass

Seed 81
class name_4[**name_2](name_4.name_1):
    pass

Seed 57
class name_4[name_5]({}, name_3=name_4.name_1):
    pass

Seed 91
type name_2 = name_3
(name_3 := name_2)

Seed 100
type name_5 = name_0
(name_0 := name_5)

Seed 168
class name_0[name_5](name_0.name_5):
    pass

Seed 158
async def name_4[*name_5](name_5: name_4(), /):
    pass

Seed 224
class name_2[name_5](name_2.name_4):
    pass

Seed 247
type name_3 = name_4
(name_0 := name_3)
(name_4 := name_0)

Seed 255
class name_5[**name_3](name_5.name_3):
    pass

Seed 234
def name_2[*name_0](*, name_4: name_4):
    pass
type name_4 = name_2()

Seed 332
class name_1[**name_0](name_1()()):
    pass

Seed 361
async def name_0[*name_5](name_4: name_0()):
    pass

Seed 351
class name_3[*name_1](something, **name_3.name_2):
    pass

Seed 344
type name_3 = name_4()

def name_4[*name_0](*, name_3: name_3):
    pass

Seed 311
class name_1[**name_4](name_1, name_1=name_5):
    pass
match name_2:
    case None:
        try:
            pass
        except name_1 as name_5:
            pass
    case []:
        type name_5 = name_1

Seed 400
class name_4[*name_2](name_5 if name_4() else name_4):
    pass

Seed 382
class name_1[name_1](name_4, name_1=name_3.name_2):
    pass
(name_3 := name_1)

Seed 395
class name_5[name_1](*name_5):
    pass

Seed 397
class name_0[name_4](name_0[name_1]):
    pass

Seed 488
class name_1[name_5](name_1.name_5):
    pass

Seed 473
async def name_2[*name_4](*, name_5: name_3()):
    pass
(name_3 := name_2)

Seed 492
class name_0[name_5](name_0.name_3):
    pass

Seed 454
type name_5 = name_0
name_0 = name_5

Seed 463
def name_3[**name_2](*, name_3: name_4):
    pass
type name_4 = name_3()

Also failing (but pysource-minimize can't minimize the panics in these for some reason, so the repros are too much text to paste into this GitHub issue) are the following seeds:

Seed 5
Seed 16
Seed 36
Seed 102
Seed 119
Seed 127
Seed 141
Seed 295
Seed 321
Seed 348
Seed 353
Seed 452
Seed 494

Thanks @AlexWaygood. I skimmed through these examples and I think they are almost all related to known issues:

#14672: recursive and self-referential (circular) type aliases
#14333 and and the two known failures here:
https://github.com/astral-sh/ruff/blob/5137fcc9c81610f687b6cb45413ef83c2c5eea73/crates/red_knot_workspace/tests/check.rs#L267-L270

What's new to me are some examples with self-referential/cyclic function definitions, but given that we have the same problem with classes and type aliases, this is not a big surprise 😄.
I think the value of the fuzzer will be much bigger after we solved those three issues (it sounds like maybe it's just one big issue with self-referential definitions). Do you think it makes sense to keep this ticket open?

I think the value of the fuzzer will be much bigger after we solved those three issues (it sounds like maybe it's just one big issue with self-referential definitions). Do you think it makes sense to keep this ticket open?

Agreed. I think I'd like to keep this issue open for now, though. I'd like to eventually run this fuzzer on red-knot in CI like we already do with the parser, so it's useful to have something to track that. I'm also not 100% sure if all these panics are to do with self-referential definitions -- the ones that pysource-minimize is failing to minimize are somewhat mysterious (not sure what's going on there). And it's also possible that on some of these seeds there are actually multiple panics, and the self-referential definitions are obscuring other issues that also exist.


Preview error when using StreamField with EditHandler on per-request basis

Issue Summary
We're using EditHandlers, which show/hide fields depending on the user's permission. This is based on the example in wagtail's tests (see https://github.com/wagtail/wagtail/blob/main/wagtail/tests/testapp/models.py#L1418).
Problem:
Unfortunately, there are multiple places in wagtail's codebase, where BaseFormEditHandler.get_form_class() is called, without binding the current request (and also instance etc). One example is the preview-mode (see preview.py).
As a result, a user which can only view a subset of the full admin form of a page for example, actually validates his POST-data (which only contains a subset of the fields) with the full form, since the logic that would hide some fields based on the request isn't called.
This probably works for simple cases like wagtail's test and described in multiple tickets (e.g. https://github.com/wagtail/wagtail/issues/5546), but in our case it results in crashes when showing/hiding StreamFields.
Solution:
At least bind instance and request before get_form_class() is called, where possible, similar to how the normal edit-view does it: https://github.com/wagtail/wagtail/blob/main/wagtail/admin/views/pages/edit.py#L311
I will try to add those calls to all the places I can find and let the tests run and I hope this can be fixed quickly.
Steps to Reproduce
I don't have a simple example available yet, but basically we have a custom BaseCompositeEditHandler which may skip some of its children, if the user is not a superuser. This is very similar to the sample in wagtail's tests, but instead of switching between two panel-lists, we have one default list, and based on the field-keys we may exclude some of those fields.
So this all works for the superuser, since he can edit all of the fields. But if one of those excluded fields is a StreamField and the non-superuser clicks on the preview button, the server crashes with something like that:
2021-09-24 11:43:13 ERROR django.request: Internal Server Error: /admin/content/pages/add/base/testpage/1337/preview/ (log.py:224)
Traceback (most recent call last):
  File "/****/lib/python3.8/site-packages/django/utils/datastructures.py", line 76, in __getitem__
    list_ = super().__getitem__(key)
KeyError: 'form_element_blocks-count'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
...****...
    return view_func(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/django/views/decorators/cache.py", line 44, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/wagtail/admin/urls/__init__.py", line 121, in wrapper
    return view_func(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/wagtail/admin/auth.py", line 193, in decorated_view
    return view_func(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/django/views/generic/base.py", line 98, in dispatch
    return handler(request, *args, **kwargs)
  File "/****/lib/python3.8/site-packages/wagtail/admin/views/pages/preview.py", line 64, in post
    form = self.get_form(self.get_page(), request.POST)
  File "/****/lib/python3.8/site-packages/wagtail/admin/views/pages/preview.py", line 129, in get_form
    if form.is_valid():
  File "/****/lib/python3.8/site-packages/wagtail/admin/forms/pages.py", line 150, in is_valid
    return super().is_valid()
  File "/****/lib/python3.8/site-packages/modelcluster/forms.py", line 316, in is_valid
    form_is_valid = super(ClusterForm, self).is_valid()
  File "/****/lib/python3.8/site-packages/django/forms/forms.py", line 175, in is_valid
    return self.is_bound and not self.errors
  File "/****/lib/python3.8/site-packages/django/forms/forms.py", line 170, in errors
    self.full_clean()
  File "/****/lib/python3.8/site-packages/django/forms/forms.py", line 372, in full_clean
    self._clean_fields()
  File "/****/lib/python3.8/site-packages/django/forms/forms.py", line 384, in _clean_fields
    value = field.widget.value_from_datadict(self.data, self.files, self.add_prefix(name))
  File "/****/lib/python3.8/site-packages/wagtail/core/blocks/base.py", line 535, in value_from_datadict
    return self.block_def.value_from_datadict(data, files, name)
  File "/****/lib/python3.8/site-packages/wagtail/core/blocks/stream_block.py", line 97, in value_from_datadict
    count = int(data['%s-count' % prefix])
  File "/****/lib/python3.8/site-packages/django/utils/datastructures.py", line 78, in __getitem__
    raise MultiValueDictKeyError(key)
django.utils.datastructures.MultiValueDictKeyError: 'form_element_blocks-count'
2021-09-24 11:43:13 ERROR django.channels.server: HTTP POST /admin/content/pages/add/base/testpage/1337/preview/ 500 [0.15, <IP_ADDRESS>:44074] (runserver.py:160)

In the above stacktrace, the form_element_blocks (which is a StreamField) are now visible to the user in the frontend. But the preview-request actually creates a form with the StreamField (because our code in on_request_bound() isn't called), which fails when validating against the POST-data, which doesn't contain any of the StreamField's POST-data.
Technical details

Python version: 3.8.10
Django version: 3.2.7
Wagtail version: 2.14.1

Ok, multiple places in wagtail's codebase is what I've found after a quick search for "get_edit_handler().get_form_class()", but it seems that only the preview's usage is a real issue, since it can be overridden easily with custom edit handlers.
Actually I only found one place in the workflow's EditView (see https://github.com/wagtail/wagtail/blob/main/wagtail/admin/views/workflows.py#L141), where I'm not completely sure, if it should also bind the form to the current object, just to avoid bugs in the future. But I'm not really an expert here, because I haven't used workflows intensively yet.


Adding provenance to COMBINE archive record

A COMBINE archive when imported that does not include provenance should get an Activity with a Plan(s) that references the SED-ML file as an Attachment, a Usage(s) that references the SBML Model as an SBOL Model.  All other files should be packaged into a Collection of results as Attachments, and this Collection should have a wasGeneratedBy link to the Activity.

should already exist for combine archives


⚠ Turnos 24x7 has degraded performance

In d0c6571, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 3346 ms

Resolved: Turnos 24x7 performance has improved in ab39c43.


⚠ Jenkins Plugins Artifactory has degraded performance

In 74d8140, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1224 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 31d52c6 after 17 minutes.


Codeunit 1013 new event publisher OnAfterApplyJobJnlLineFilter

Requesting a new publisher event in codeunit 1013, function Code. New publisher event "OnAfterApplyJobJnlLineFilter"

LOCAL [IntegrationEvent] OnAfterApplyJobJnlLineFilter(VAR JobJournalLine : Record "Job Journal Line";VAR JobJournalBatch : Record "Job Journal Batch")

What is the point to have JobJournalBatch in the event if it is overwritten three lines lower by:
 JobJnlBatch.Get("Journal Template Name", "Journal Batch Name");?

There is actually no point, my mistake. It would be sufficient to have only JobJournalLine as a parameter:
LOCAL [IntegrationEvent] OnAfterApplyJobJnlLineFilter(VAR JobJournalLine : Record "Job Journal Line")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Simple Objects - Shape Line: Wrong 'Shape Line' color when clicking on icon

Steps to Reproduce

Open Ketcher.
Click to 'Shape Line' button in the tool palette.

Expected behavior
The line has a white color.

Actual behavior
The line has a dark color.

Desktop:
OS: Windows
Browser: Chrome Version 93.0.4577.63, Firefox Version 92.0, Microsoft Edge Version 93.0.961.47

Release/2.4 Closed as fixed.


fix: 12456 - oauth redirection issue

Description

fixed issue with redirecting urls from oauth

Fixes #12456
Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please refer linked issue

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Test coverage results :test_tube:
:green_circle: Total coverage has increased
// Code coverage diff between base branch:release and head branch: fix/12456-oauth-redirecting-issue

Status
File
% Stmts
% Branch
% Funcs
% Lines

:green_circle:
total
56.43 (0)
37.81 (0.01)
36.07 (0)
56.65 (0)

:green_circle:
app/client/src/utils/autocomplete/TernServer.ts
52.94 (0.23)
41.67 (0.84)
36.21 (0)
56.99 (0.25)

https://www.loom.com/share/0fd1c1d876174aac8431727f64b5ee01

@haojin111 Is there a Cypress test to assert this fix?

not now! we can't process cypress testing with gsheet authorization.

/ok-to-test sha=dd7d91b


Output alb dns name

For our use case, we are using the ALB DNS name to create an external DNS record to the atlantis load balancer. This adds the ALB DNS name to the outputs.

Hi @antonbabenko, would you be able to review this PR at your convenience? Thank you!

Makes sense to add this. Thank you!

v1.14.0 has been released.


datafusion cannot recognize chinese charactors.

Describe the bug
datafusion cannot recognize chinese charactors.
To Reproduce

simply create a csv file, put the title as name in chinese charactor: 扫描人
run the rust code as below,will get the parse error: Error: SQL(ParserError("Expected an expression:, found: 扫"))

`use datafusion::prelude::*;
#[tokio::main]
async fn main() -> datafusion::error::Result<()> {
// register the table
let ctx = SessionContext::new();
ctx.register_csv("example", "lite.csv", CsvReadOptions::new()).await?;
// create a plan to run a SQL query
let df = ctx.sql("SELECT distinct 扫描人 FROM example").await?;
// execute and print results
df.show().await?;
Ok(())
}`
Expected behavior
make datafusion recognize the chinese charactors.
Additional context

You can try this
let df = ctx.sql("SELECT distinct \"扫描人\" FROM example").await?;

Thanks.


TX fails due to PrevrandaoNotSet on non-mainnet forks

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (31f945c 2023-01-30T00:05:12.356073Z)
What command(s) is the bug in?
anvil --fork-url https://moonbeam.blastapi.io/<api_key>
Operating System
macOS (Apple Silicon)
Describe the bug
Attempting to deploy a contract to local fork of the Moonbeam network
Run the local node:
anvil --fork-url https://moonbeam.blastapi.io/<api_key>

Deploy the contract:
forge script scripts/foundry/DeployGarage.s.sol:DeployGarage --rpc-url http://localhost:8545 --broadcast --legacy

Fails with:
Fork
==================
Endpoint:       https://moonbeam.blastapi.io/<api_key>
Block number:   2844720
Block hash:     0x1ee3577268a3d1f1fcb2da74d0b1cd4f56a6ccc89abe80771486551d3e9bdc2b
Chain ID:       1284
...
eth_blockNumber
eth_chainId
eth_getBlockByNumber
eth_chainId
eth_chainId
eth_sendRawTransaction

    Transaction: 0xd76504b4c53e2f0051c26f106469a0d47d1807fb3cc865aab50f064e017991cc
    Gas used: 0
    Error: failed due to PrevrandaoNotSet

    Block Number: 2844721
    Block Hash: 0x98f3806dff433e5c3d38550262854e0763980f3fa32bb0287356ff228df44964
    Block Time: "Tue, 31 Jan 2023 00:30:23 +0000"

eth_getTransactionReceipt

can you please post an eth_getBlockByHash response from that provider?

@mattsse :
curl --location --request POST 'localhost:8545/' \
--header 'Content-Type: application/json' \
--data-raw '{
        "jsonrpc":"2.0",
        "method":"eth_getBlockByHash",
        "params":[
                "0x84fa58a278a7fd1782796fb62f728c5cf687212a022c621ecc03532be4f64eb3",
                true
        ],
        "id":1
}'

with response:
{"jsonrpc":"2.0","id":1,"result":{"hash":"0x84fa58a278a7fd1782796fb62f728c5cf687212a022c621ecc03532be4f64eb3","parentHash":"0x4b3d5f405d87b9ce1bf7f3bf43a148fa74489f9216c5cc49a1b332af01510b93","sha3Uncles":"0x1dcc4de8dec75d7aab85b567b6ccd41ad312451b948a7413f0a142fd40d49347","miner":"0x0000000000000000000000000000000000000000","stateRoot":"0x0000000000000000000000000000000000000000000000000000000000000000","transactionsRoot":"0xbb470b51ea61958a789f9e2c8ae17577dcad600ee55731cd9197c1fd776dff53","receiptsRoot":"0x703c035562d8e37c66f2f9461219b45c710e59c8d0d234f6b062107de627758c","number":"0x2b78f1","gasUsed":"0x0","gasLimit":"0xe4e1c0","extraData":"0x","logsBloom":"0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000","timestamp":"0x63d92d74","difficulty":"0x0","totalDifficulty":"0x0","sealFields":["0x0000000000000000000000000000000000000000000000000000000000000000","0x0000000000000000"],"uncles":[],"transactions":[{"hash":"0x1e59a2767f2960bc4ceaded667cd8493a2815925735916f0ffbe0cac0619d892","nonce":"0x4","blockHash":"0x84fa58a278a7fd1782796fb62f728c5cf687212a022c621ecc03532be4f64eb3","blockNumber":"0x2b78f1","transactionIndex":"0x0","from":"0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266","to":null,"value":"0x0","gasPrice":"0x14f42e429d","gas":"0x2090f","input":"0x6080604052348015600f57600080fd5b506063600055607d806100236000396000f3fe6080604052348015600f57600080fd5b506004361060285760003560e01c80634e70b1dc14602d575b600080fd5b603560005481565b60405190815260200160405180910390f3fea2646970667358221220bf8077bb444b3110164dd2d4b292160bc8c702eab717c0c61fa80178183a557c64736f6c634300080f0033","v":"0xa2c","r":"0x2a328141daded32b3c27496ff65eab47f643af176ebbeb522d222dced8f48d62","s":"0x7fc65be499cfcbc148459f118bf9e96c59e8649de9bb07b056dd0e6b9260cb43","type":"0x0","maxPriorityFeePerGas":"0x14f42e429d","maxFeePerGas":"0x14f42e429d","chainId":"0x504"}],"size":"0x2fc","mixHash":"0x0000000000000000000000000000000000000000000000000000000000000000","nonce":"0x0000000000000000","baseFeePerGas":"0x14b893789d"}}

hmm
mixHash is definitely present in the response so no idea why prevrandao is not set.

@mattsse looks like this was fixed in #4238 , thank you!

Hi. I am still getting issue in 5ireChain testnet
My command for testing:
forge script script/deploy.s.sol --private-key <my private key>  --broadcast --legacy --rpc-url https://rpc.testnet.5ire.network/

My issue:
- Error #0: header validation error: `prevrandao` not set
- Error #1: `prevrandao` not set

May I open this issue again ? @mattsse

Same case here

Hi @anajuliabit
This likely relates to the recent upgrade to default the evm_version to cancun rather than paris. Perhaps are trying to deploy to a chain that does not support shanghai (push0)?
https://github.com/moonwell-fi/moonwell-contracts-v2/blob/a3559fe4d379ff0874fd4a3202d4a019bc6267aa/foundry.toml#L9
To resolve this you could manually pass --evm-version paris in forge script

@zerosnacks I believe this happens because moonbeam doesn't return a mixHash


Accordion issues

[ ] accordion item shouldn't be draggable (or you should only be able to drop it into accordion)
[ ] draggable list in accordion context menu could solve that (move up and move down buttons in accordion item context menu could help too, but might not be necessary if accordion items  are not selectable, see progress-indicator)
[ ] when you delete the last accordion item it should delete the accordion (parent)
[ ] accordion items shouldn't be expanded on click in canvas (draggable list with expanded prop could fix that)

others?

can you please elaborate a bit on what to do to improve on this topic?


Add option forceConsole

Add new option to the Console transport:
forceConsole (Boolean): when true, force transport to use console log/warn/error instead of write. With this option, VSCode terminal will work without setting the "outputCapture" to "std".

Hmm, this seems to change default behavior, which might require a major version bump.  VSCode might be a better place for this to be fixed, especially if the impact is intended only for that one environment.

I believe this would resolve my feature request #2175 and others like it. I'm not sure how it would change the default behavior since the default value is false, so the statement:
if (console._stderr && !this.forceConsole)

would evaluate to the same as before if this prop wasn't set.

Found this open PR after spending way too long trying to find out why I wasn't getting Winston console logs in VSCode. Turns out it's because I'm attaching to the process (required in my case), and stderr/stdout can't be captured in that config.
Would love to have this option available as it would enable VSCode to actually see the logs I want to write with Winston.

I agree that it doesn't look like this is introducing a breaking change.  I'm okay with merging this but it would be good to have some documentation (even just a comment) somewhere explaining that you may need to set this option with VSCode.  Enough people are using VSCode that maybe that's worth a line in the README?  @neilenns , would you feel up to the task of adding some brief documentation somewhere for this?

Yep, I'd be happy to and will later today!

Cool, you rock!! 🎸

I, like presumably many others, do console.log = logger.log.bind(logger) (etc), to capture all console.log calls from all modules into my logging stream (and previously use something like the SimpleConsoleTransport in #1544 to get the logs showing up in Node Inspector / VSCode / etc).  Unfortunately this fix doesn't actually help (causes an infinite recursion / call stack exceeded crash).  Probably just need to save a reference to the global console at the time of logger instantiation and it'd be good though?

@Jimbly @neilenns If you think saving a copy of the global console or some other mod to this PR would be an improvement, please open another quick PR and let's get those fixes/improvements in there.  With a test case would be ideal, but let's just do what we can to address this properly once and for all, I know this and related issues like #1544 have been open for a while.  Appreciate your help in figuring out all these corner cases and details.

I'm not an expert at all in this unfortunately, just someone who got tripped up with the whole "can't capture in vscode when attaching to node.js" mess.

If you think saving a copy of the global console or some other mod to this PR would be an improvement, please open another quick PR and let's get those fixes/improvements in there.

Looking at this a bit more, the changed proposed in https://github.com/winstonjs/winston/pull/2474 might fix the infinite recursion issue @Jimbly hit? Since it doesn't call console.log() directly and instead uses inspector.console to log?

I manually applied a variation of the change in #2474 and confirmed it does not have any issue with infinite recursion. In my main .ts file I added this:
import mainLogger from "@utils/logger";
console.log = mainLogger.log.bind(mainLogger);

And everything logs correctly to the console.


Custom list and list item template in a table

Hi,
I'm trying to achieve the following look and feel for my list:
+----------+----------+----------------+
| Pet Name | Pet Type |    Actions     |
+----------+----------+----------------+
| Foo      | Bar      | remove/up/down |
| Foo2     | Bar2     | remove/up/down |
+----------+----------+----------------+
| Add                                  |
+----------+----------+----------------+
```
After following the guidance here #109, I ended up with the template shown at the bottom of this issue.

The problem with that template is that the `petLayout`
```
var petLayout = function(locals){
  return (

        {locals.inputs.name}
        {locals.inputs.type}

  );
};
```
is breaking the dom (because the `<div>` is a child of a `<tr>`) and hence react raises an `Invariant Violation` error due to the dom being auto-corrected by the browser (tried in chrome).

Using a `<tr>` tag instead of the `<div>` breaks too.

I've been able to go around this with the following:
```
var petLayout = function(locals){
  return (

        {locals.inputs.name}
        {locals.inputs.type}

  );
};
```
It kinda does work "by chance" because the way the browser is auto-correcting the dom suits react ... But it is very fragile and I'd like to find another way.

I could ditch the `<table>` and try to recreate the same design with divs but well, the rest of the application is using tables for such components and I'd like to keep it simple.

Thanks again for the support !

```
import React from 'react/addons';
import t from 'tcomb-form';

var Form = t.form.Form;

var Animal = t.enums({
 dog: "Dog",
 cat: "Cat"
});

var Pet = t.struct({
  name: t.Str,
  type: Animal
});

var Person = t.struct({
  pets: t.list(Pet)
});

var listLayout = function(locals){
  return (

                Pet name
                Pet type
                Actions

        {
          locals.items.map(function (item) {
            return (

                    {item.input}

                        {
                            item.buttons.map(function (button, i) {
                                return <button key={i} className="btn btn-info" onClick={button.click}>{button.label}</button>;
                            })
                        }

            )
          })
        }

                <button className="btn btn-info" onClick={locals.add.click}>{locals.add.label}</button>

  );
};

var petLayout = function(locals){
  return (

        {locals.inputs.name}
        {locals.inputs.type}

  );
};

var options = {
  fields: {
    pets: {
      template: listLayout,
      item: {
        template: petLayout
      }
    }
  }
};
```

Hi,
Yeah tables are a pain in the xxx.
On thing I don't understand. You have this template
var petLayout = function(locals) {
  return (

      {locals.inputs.name}
      {locals.inputs.type}

  );
};

but the model is
var Pet = t.struct({
  type: Animal
});

What's locals.inputs.name ?

Hey @gcanti , I updated the initial issue's content
I removed name from Person and moved it where it belongs:
var Pet = t.struct({
  name: t.Str,
  type: Animal
});

I was thinking maybe I could simply override the field template instead of the pet template ?
Does that sound as a viable option ?

I just can't find a workaround for React's limitation in returning only one node from a render method :-(
var petLayout = function(locals) {
  return (

 // <= ouch!
      {locals.inputs.name}
      {locals.inputs.type}

  );
};

Yep, same here :/
So I guess I will have to deal with a field level template then. I'll let you know how it turn out

won't doing this work?
var petLayout = function(locals) {
  return ([
      {locals.inputs.name}	,
      {locals.inputs.type}
  ]);
};

@VinSpee sadly it will not work no, react still complains with Adjacent JSX elements must be wrapped in an enclosing tag

Hi @johnraz,
I know it's probably too late, but I found an interesting hack:
const Animal = t.enums({
  dog: 'Dog',
  cat: 'Cat'
})

const Pet = t.struct({
  name: t.Str,
  type: Animal
})

const Person = t.struct({
  pets: t.list(Pet)
})

const listLayout = locals => {
  return (

          Pet name
          Pet type
          Actions

      {
        locals.items.map((item) => {
          //
          // here's the trick: setting the template on the fly and clone the item!
          //
          const options = {
            template: (sublocals) => {
              return (

                  {sublocals.inputs.name}
                  {sublocals.inputs.type}

                    {
                      item.buttons.map((button, i) => {
                        return <button key={i} className="btn btn-info" onClick={button.click}>{button.label}</button>
                      })
                    }

              )
            }
          }

          return React.cloneElement(item.input, {
            key: item.key,
            options: options
          })
        })
      }

          <button className="btn btn-info" onClick={locals.add.click}>{locals.add.label}</button>

  )
}

const options = {
  fields: {
    pets: {
      template: listLayout
    }
  }
}

It's somehow horrible, but seems to work. Probably it's too risky for production code though


Compilation error (warning treated as error)

I get this error when trying to compile the game with make -B.
It gives a usable something.debug but no something.release.
OS: Arch linux
GCC: 10.2.0
In file included from src/something.cpp:14:
src/aids.hpp: In function ‘void command_history(Game*, aids::String_View)’:
src/aids.hpp:574:25: error: ‘snprintf’ argument 4 may overlap destination object ‘game’ [-Werror=restrict]
  574 |         int n = snprintf(
      |                 ~~~~~~~~^
  575 |             buffer->data + buffer->size,
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  576 |             buffer->capacity - buffer->size,
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  577 |             "%.*s", (int) view.count, view.data);
      |             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from src/something.cpp:57:
src/something_commands.cpp:153:28: note: destination object referenced by ‘restrict’-qualified argument 1 was declared here
  153 | void command_history(Game *game, String_View)
      |                      ~~~~~~^~~~
cc1plus: all warnings being treated as errors
make: *** [Makefile:21: something.release] Error 1

@apa420 this is a really weird error... Is it reproducible with clang?

I do not get this error with clang

I'm not a C++ Developer so I'm not able to explain technically why my pull request solves the issue. But if this works to me maybe it's the solution. If @apa420 could check in his machine will be great.


Enhanced Footer Design and Updated footer.ejs

Description
Changed the footer design, added animations and the one which I've implemented works on different devices smoothly and added the about us in quick links also
Fixes #265
Replace issue_no with the issue number which is fixed in this PR
Screenshots

Checklist

[  ] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[  ] Code follows the established coding style guidelines
[ ] All tests are passing

@SurajPratap10 could you review this pull request

@SurajPratap10 I tried many different combinations like red-white, grey-white, black-white and those didn't look good, so I added silver-white , could you suggest the new colour you want

@SurajPratap10 should I keep the moving thing in slider animation like silver and the background bar enclosing it as white

@SurajPratap10 , I've added blue shades to it could you please look into it and merge it possibly

Resolve the conflicts @Vishalk91-4

@SurajPratap10 , the conflicts have been resolved

@SurajPratap10 , I've added blue shades to it, could you please review it


chore: create reproducible bug case

Reproducible bug example
Modification of the next-firebase-auth example application to simulate a race condition described in this issue – https://github.com/gladly-team/next-firebase-auth/issues/189.
This only seems to happen when you run the application in production mode: yarn build && yarn start

Note: Not intended to merge

This was fixed in #243.


Latest tag docs doesn't update automatically

Since the latest tag is generated automatically, its docs don't update automatically.
This can be resolved by incorporating it directly in the docs action, which will need to be cloned for this purpose

Fixed by e27dd91817962e5c44a13e84d9adf298014cc497 and previous commits, using our new custom version of action-docs


Remove CI exclusion for 3.12 tests on Windows

Pywin32 to released version 306 on March 25th adding tags for 3.12.
Pillow released version 9.5.0 on April 1st adding a pre-built binary for 3.12.
These were the only blockers previously identified for installing Azure dependencies so the unit tests would run with Python 3.12. This PR updates Pillow and removes the exclusion.

@LiliDeng  LGTM


Added test case for HTTPConduit's 'http.redirect.allowed.verbs' context property

Added test case for HTTPConduit's 'http.redirect.allowed.verbs' context property

@ypiel-talend wdyt?

@reta thanks for the help :+1:  I add this to my pr and commit asap.

@reta thanks for the help 👍 I add this to my pr and commit asap.

I think I merged it already, the change look trivial so we could add the tests, but please feel free to create another one with tests if you like


Create and deploy new Azure OpenAI Service resource

Walk-through:
https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/create-resource?pivots=web-portal

Application approved by Microsoft, awaiting policy change to allow for service creation in zone with support for GPT-4 model (Sweden Central, Switzerland Central or France Central)

service created and tested. Performance significantly improved, compared with OpenAI infrastructure.


Restore access for removed users from the the Realm

Description:
This ticket is to come up with a plan for how to restore the 3 users that were removed from the realm.
Note: this is an in database function, not a UI
This has become more important as the BCeID bug fix has removed 3 users from the realm
Acceptance Criteria:

[ ] Clear and complete steps for the team on how to work internally and with the applicant to transfer the applications
[ ] Identify & be sure which user identity is connected to each use. Be absolutely sure the application belongs to them. Confirmation from Mars that User & Applications match
[ ] Mars send email to user
[ ] Triple check assigning the correct user to the right application
[ ] View connections of Application ID & User ID in Metabase (3 applicants that were removed from the realm have their access restored with new user credentials?)

Risk: Applying script on production, no way to check it's done until it's done.

Needs Refinement:  @VB-at-Bis  put documentation on Scrum Team channel with UUID and user IDs etc and include link to it in this ticket.

Link to the document: https://bcgov.sharepoint.com/:w:/r/teams/04708-ScrumTeam/Shared Documents/Scrum Team/removed_users.docx?d=wb94c8200f67a4792ac050375838792db&csf=1&web=1&e=z8bHi4

@MarsRomer , I added questions to the document

Blocked until we reach out to user and decide if user would like us to consolidate their orphaned/abandoned applications.  Mars to reach out to user week of July 17

Closing this ticket as we have decided that we are not going to do anything about this issue at this time


Merge pull request #1 from python-escpos/master

Contributor checklist

[ ] I have read the CONTRIBUTING.rst
[ ] I have tested my contribution on these devices:

e.g. Epson TM-T88II

[ ] My contribution is ready to be merged as is

Description
update branch to 1.0.9

Sorry, wrong button.
Delete this PR.


Example for UniformBuffer update

Suppose we want to add camera rotation to our fancy teapot example. In the example we have 2 command buffers with shared uniform buffer and  pipeline_layout::set0::Set attached to them. How can we perform an update on each frame?

Do we need to create 3 uniform buffers for this?
Do we need to update uniform buffer directly or do some magic with pipeline_layout::set0::Set ?

If the uniform buffer contained a large amount of data, you would need to create 3 uniform buffers and create a new descriptor set before each rendering.
There is a technique that vulkano does not yet support: you can create just one buffer that you split in three parts, and when you bind the descriptor sets you can specify an offset in the buffer for the start of the data. This technique has the advantage that you're only using one buffer and that the descriptor set stays the same.
However for small amounts of data (like here), you can just either use an update_buffer command in the command buffer, or use push constants (which are like uniforms, but limited to 128 bytes of data).

Thanks for the answer, took some time to figure out.


Readme: install command line should include package version ranges

Following up from https://github.com/standard/standard/issues/1357#issuecomment-521317287.
If there are no version ranges, unsupported packages could be installed and then errors on running and that's bad UX.

If peerDependecies are properly specified, then npm should warn about an incompatible version at install time.