Removes unused npm packages.

Removes unused npm packages.
Removals

Removes istanbul and jsdom because these are used through gulp-istanbul and mocha-jsdom respectively.

Testing

gulp test or gulp test --sauce=false not be different from flapjack branch.

Review

@KimberlyMunoz
@jimmynotjim
@sebworks

Todos

mocha-jsdom seems to be using an outdated version of jsdom. I'm going to open a PR over there for it and it'll pull automatically into our project.

Should we wait to see if we're going to stop using mocha-jsdom?

Why would we switch away from mocha-jsdom, @jimmynotjim?

@KimberlyMunoz @anselmbradford brought up a point about it last week. I'll defer to him since he knows better than I do what the issue is.

@KimberlyMunoz Jimmy and I chatted about this at regroup because mocha-jsdom was woefully outdated with its jsdom dependency and the repo's tests were broken (running npm install && npm test on mocha-jsdom itself was broken), however, it looks like the maintainer may have fixed those issues so we might be good to keep it https://github.com/rstacruz/mocha-jsdom/pull/12 ... in which case this PR should proceed.

In that case :+1:

mocha-jsdom seems to be using an outdated version of jsdom. I'm going to open a PR over there for it and it'll pull automatically into our project.

maintainer of mocha-jsdom here, let's see what we can do.

...just checked now: jsdom is not actually required by mocha-jsdom as a dependency, you're supposed to install it alongside as a peer dependency.

@rstacruz Thanks for the input! We've kept both jsdom and mocha-jsdom as devDependencies, but should we actually add jsdom to a peerDependencies section like you have it in https://github.com/rstacruz/mocha-jsdom/blob/master/package.json#L29 ?

@anselmbradford leave 'em as dev deps. npm deprecated the peerDependencies object and in npm 3 it'll throw an error and not install anything. https://github.com/npm/npm/issues/6565

So how does this work? mocha-jsdom has a version of jsdom pegged to 7.0.2 in devDependencies and any version in peerDependencies. If I pull in the latest major version in devDependencies in this project, what happens when jsdom goes to, say, 7.9.0; all other things being equal? What version is mocha-jsdom using in that case?

mocha-jsdom has jsdom listed as a dev dependency because it uses it internally for its own tests. In your example, your project would be using jsdom v7.9.0.
my-project
├── src
└── node_modules
    ├── jsdom (7.9.0)
    └── mocha-jsdom

devDependencies are only installed when you run npm install from the directory's root. Unlike dependencies, they aren't pulled down when you install the project as a dependency of another project. If this was not the case, your tree would look like this:
my-project
├── src
└── node_modules
    ├── jsdom (7.9.0)
    └── mocha-jsdom
        └── node_modules
            └── jsdom (7.0.2)

And your project would use jsdom v7.0.2. Which would be bad because you probably wouldn't even realize that was happening and there'd be no way to stop it.
But what if the the module maintainer erroneously added jsdom as a normal dep instead of a dev dep? Then v7.0.2 would get installed and imported and you'd crawl into a corner bawling after spending six hours trying to figure out why you're seeing errors that should be fixed in v7.9.0. Fortunately, this isn't the case with mocha-jsdom because @rstacruz is a crazy smart guy who did everything correctly. But peer deps open up a lot of scary doors so npm decided to stop automatically installing them.

:point_up: yep, what he said! :)


ops: split deploy workflow steps into jobs

This PR updates our base deploy workflows to improve organization and maintainability.
This new approach splits the existing single-job workflows into three separate jobs build-frontend, glob, and deploy. This change provides better separation of concerns and makes it easier to understand the purpose of each job.
Right now this doesn't get us much other than better organization and maintainability, but in the future we could run jobs in parallel (one workflow for both talk and groups deploys, or other future apps) or introduce better error handling based on job failures.
Key changes in this PR:

Extracted build-frontend job to handle frontend building steps for both deploy-talk and deploy-groups.
Created a separate glob job for generating and committing glob files.
Updated the deploy job to focus solely on the deployment process.
Added artifact upload and download steps to pass the built files between jobs.
Ensured that jobs run sequentially, maintaining the original behavior.

"glob job" lol


Improve the warning/error message, expected identifier to correctly identify the issue

Adding extra , at the end of a widget written inside a view macro generates this vague warning and error:

Removing the extra comma make it go away:

Other times, I came across this when trying to add a named child to GtkStack:

What can be done to improve the user to understand the underlying problem neatly?

Thanks for your report! Does this issue still appear in 0.6?
Also, the last error is valid though, no?

Yes, I'm on 0.6.
The last error does confuse me, probably it could be just Did you confuse with =/: ... warning would have made sense 🤔


Version 1.4: Suggestions to the install section

Version 1.4 is amazing! Congratulations, it's really hard to believe you made so much in just a few months almost single-handedly!
I think the install section is missing a few things compared to the others, so I am gonna make a few suggestions:

[ ] select/unselect multiple packages to install at once (I think sequentially is better)

[ ] export packages to a file (useful if you want to install apps on another PC that you don't have installed on your own).

[X] Icon inconsistency https://github.com/martinet101/WingetUI/commit/ae72172ab6dc27158512cc6df09365722396a518:

export packages to a file (useful if you want to install apps on another PC that you don't have installed on your own).

You can export things from the uninstall section

You can export things from the uninstall section

I know. But imagine you wanna export some packages like drivers for a different hardware or programs that only work on another Windows version.

Aaaaaah i get your point.
Like creating some kind of package kit from the discover software section and then export it?

Like creating some kind of package kit from the discover software section and then export it?

Yes, my idea initially was to create a .ps1 or .bat file or even downloading a .zip file with all the files. I changed it to export package since it's already a feature under installed applications

I believe https://github.com/martinet101/WingetUI/commit/ae72172ab6dc27158512cc6df09365722396a518 fixes icon consistency

Yes, wanted to reference the issue but couldn't find which one was😅

export packages to a file (useful if you want to install apps on another PC that you don't have installed on your own).

I believe this idea is similar to https://github.com/martinet101/WingetUI/issues/152


Glass prefabs filled with colored liquid/garnish

Cannot be completed without #40 also being complete
Take the 3D image, fill it with an object, and assign that object a color (or texture, if you want to make soda bubbly) based on the primary mixer used.
References:
https://docs.google.com/document/d/1YmSmHOAYKzmCU9hBz_QsyhOy-GWBxBwKasGI5-ZyYhw/edit#bookmark=id.v9rj0ymmliz4
https://docs.google.com/document/d/1YmSmHOAYKzmCU9hBz_QsyhOy-GWBxBwKasGI5-ZyYhw/edit#bookmark=id.f87r3uvjck4k
Apply a garnish to the rim of the glass.  These will probably be very small to the player, so simple, distinct shapes/colors will work.
3 garnishes

PR #69


divide error when i use 1e21 over number use

Describe the bug
A clear and concise description of what the bug is.
An error occurs when dividing with a number greater than 1e21.
To Reproduce
Steps to reproduce the behavior, preferably with sample code.
const data = 1e21
multiplier = new bigDecimal(Math.pow(10, 18));
console.log(data / multiplier.value)
let divideAsset = bigDecimal.divide(received.toString(), multiplier.value, 18)
console.log('divideAsset')
console.log(divideAsset)
===>
10.000000000000000000(error)
Expected behavior
A clear and concise description of what you expected to happen.
===>
1000.0000000000000000(Normal case)
Additional context
Add any other context about the problem here.

In the example code, i do not see you initialising receivedvalue. Moreover, you are not using it as expected.
Your data is not a string or bigdecimal.

Here is a working example:
var big = require("js-big-decimal")
a = new big('1e21');
b = new big('1e18')
console.log(a)
console.log(b)
console.log(a.divide(b))


Project feedback

At the outset I would like to say that this is an interesting and ambitious project and you have done well to get to where you are.
There are a few things to note:

The .sol references in your main contract reference local directories, so pulling it down doesn't quite work

import "/home/joe/Code/blockchain-developer-bootcamp-final-project/interfaces/ILendingPoolAddressesProviderV2.sol";
import "/home/joe/Code/blockchain-developer-bootcamp-final-project/interfaces/ILendingPoolV2.sol";

You could use SafeMath for any calculations as it isn't included in Solidity Compilers pre .0.8.0
The EscapeHatch doesn't quite count as a circuit breaker, as other functions are still executable - a Pause on other methods is the general practive
The EscapeHatch  LINK send is to the caller vs owner - still is valid and the same address, just inconsistent in the code
You could save gas by packing the state variables better - e.g. grouping all the uint16s first
You could use a smaller defined ERC20 interface to save gas vs. pulling in the entire interface

I can see where the project is headed and I wish you well.

Hello,
thanks a lot for this feedback - I am pushing some amends in a few minutes. The first point about the references is my oversight as there are copies of each of those imported contracts in the project repository and I neglected to update the references before submitting. Fixed in next commit. Also now see how the escapeHatch function and gas optimisation comments make a lot of sense.
Could you possibly explain the final comment about a smaller erc20 interface in a little more detail?
Thanks again!

My comment on the IERC20.
If you see: https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/IERC20.sol
There are a few methods you don't use, so don't really need to use the entire interface.
If you declare your own IERC20.sol with just the approve and transfer functions, it should bring down the gas costs. Also, you get to remove the floating pragma on the interface.

The feedback is more for future and your knowledge - don't need to do them now :)

Brilliant, thanks. Yes, np I just like to do these things while they are fresh!


🐛 Fix community auto-complete moves cursor to start of text

After community auto completion the code tried to place the cursor 2 characters after the auto-completion. This meant that auto-completion at the end of a line would place the cursor after the last position in the line, which is invalid so Flutter treated it as 0.
Now we correctly place the the cursor only 1 character after the auto-completion.
I also reduced code duplication between the username, hashtag and community auto-completion methods.

Looks good! Thanks Jakob!

Found another similar bug. Fixing that now.

Okay, the last commit fixed an issue where community autocompletion would skip the first character of the community name when searching (e.g. c/oku would trigger a search for ku rather than oku).

Tested and works as intended. Thanks again Jakob.


enh: add network policy for core and fix it for oauth

Description

oauth policy is wrong (front and connectors should be allowed, but not core)
add network policy for core (should only be reachable from front or front-worker)

Should we have prodbox as well ? 🤔
Risk
Should be fine, but if something is wrong we can't reach core anymore
Deploy Plan
apply infra

Very naice


Remove extern information from signature

Describe the todo
Signatures should not contain keyword extern and any C-binding annotations.
Link to a branch
develop
Task list
To mark completed todos, use [x]

[ ] Filter C binding annotations
[ ] Do not print extern in prototypes, consts and params
[ ] Write test cases

This is a bad idea.


UIScrollbar zero division hardening

Contains
Short and simple fix for #2283. I originally wanted to couple this with more zero division fixes, but after some investigation (i.e. searching for '/' in widget code) it seems that these are actually the only lines of code in the UI* widget family that don't handle zero division properly.
How to test
Launch the game, type in showScreen migTestScreen, click on the min-sized UIScrollbar, check that it didn't throw a silent stacktrace.
Outstanding before merging
No outstanding issues.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/582/
Hooray Jenkins reported success with all tests good!

Thanks, @rzats. Does a sliderSize value 0 make sense?
If so (and this is the only spot where slider size is a divisor), then I would split the modified line in two to make it easier to read and understand.
If not, then I'd clamp the minimum slider size to 1 (or maybe more?).

@msteiger: sliderSize is checked for zero in the same file (blob link), so I assume it's an acceptable value.
Not quite sure what you mean regarding splitting the line in two. Should the control flow look like this?
if (sliderSize > 0) {
    if (vertical) {
        updatePosition(pos.y - mouseOffset);
        setValue(TeraMath.clamp(pos.y - mouseOffset, 0, sliderSize) * getRange() / sliderSize);
    } else {
        updatePosition(pos.x - mouseOffset);
        setValue(TeraMath.clamp(pos.x - mouseOffset, 0, sliderSize) * getRange() / sliderSize);
    }
} else {
    setValue(0);
}

Thanks for the info. I find this easier to read and understand. You might need to add updatePosition(..) for the case where sliderSize is zero. How about this?
int delta;

if (vertical) {
    delta = pos.y - mouseOffset;
} else {
    delta = pos.x - mouseOffset;
}
updatePosition(delta);
if (sliderSize > 0) {
    int clamped = TeraMath.clamp(delta, 0, sliderSize);
    setValue(clamped * getRange() / sliderSize);
} else {
    setValue( .. what is a reasonable value in that case and why? );
}

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/584/
Hooray Jenkins reported success with all tests good!

@msteiger: thanks for the feedback! Updated accordingly.
Fallback value should definitely be set to 0, IMO (since the slider is 0-sized, any higher values may potentially cause unexpected issues).

Great - thanks for the update.


Add: a method which hook after graceful shutdown.

https://github.com/lestrrat/go-server-starter/blob/master/starter.go#L429
I wanna hook after graceful shutdown.
The line of target in which graceful restart logic is called syscall.SIGTERM.
（Unfortunately, the line is naming s.signalOnHUP.
That identification's PR is https://github.com/lestrrat/go-server-starter/pull/14 ）
I've hooked to receive a channel calling syscall.SIGTERM,
// create a hook point to receive a channel in my main.go
case syscall.SIGTERM:
  want execute logic after shutdown....

but it has executed both graceful restart and shutdown.
Because L429 calls SIGTERM to kill process in graceful restart logic.
And so a hook point wrong recieved SIGTERM.
What do you think about that it should be a method which hook after graceful shutdown?

Because L429 calls SIGTERM to kill process in graceful restart logic.

Use start_server --signal-on-hup=XXX to change the signal that gets sent when HUP is sent to start_server

I got it. Thank you!!!
Close this PR.


Ensure that matches are not scrolled into after the findbar has been closed (PR 10100 follow-up)

This is something that I noticed while testing PR #10183, and it probably deserves a separate PR rather than being lumped in with those changes since it's a direct follow-up to PR #10100.

/botio-linux preview

/botio-linux preview

Looks good; thank you! It's also good to see that the find code is becoming much more readable lately.


Integrate embedded Mono runtime and MSBuild into OmniSharp

For the latest release of omnisharp-vscode, we have made significant changes to how OmniSharp runs that need to be integrated back into omnisharp-roslyn. The following are the key components the need to be integrated.

MSBuild: In order to properly target .NET Core, .NET Framework and Mono .csproj projects, OmniSharp must include MSBuild itself along with relevant targets and task. On Windows, this can be achieved with the Microsoft.Build.Runtime package. On macOS/Linux, we need a similar but different set of content. In omnisharp-vscode, this achieved by using a custom build from Xamarin's fork of MSBuild. Because both of these MSBuild variants target net46 but are completely different, we'll need custom build logic to pull them into OmniSharp.

Embedded Mono Runtime: omnisharp-vscode no longer uses .NET Core builds of OmniSharp. Instead, it runs OmniSharp as a net46 app. On Windows, it just runs on the installed .NET Framework. On macOS/Linux, it runs on an embedded Mono runtime with a set of Mono framework assemblies. There are three variants of the Mono runtime: one for macOS, one for Linux/x86, and one for Linux/x64.

Once the integration is complete, there should only be 5 different builds of OmniSharp:

Windows (x86 and x64)
OSX
Linux (x86 and x64)

In addition, OmniSharp will be able to support the following project types:

project.json (legacy)
.csproj targeting .NET Core (new)
.csproj targeting .NET Framework
.csproj targeting Mono

👍  I need to setup a meeting or time to discuss the changes again... summit was good, but we need to make a plan to consolidate things.
I think one part of that is to update the cake build script, something I was already thinking we should do.

Awesome! I've been working on some bash scripts to construct the Embedded Mono framework that I'd cobbled together by hand.

#705 gets much closer to this being integrated into OmniSharp.

And I kind of had half a thought in that last comment.
The historical complaint was the file watchers in mono were fairly buggy, if we were to switch to them now would the behavior be better (now that a lot of the code is shared from .NET Desktop).

It will be nice to see what the MsBuild that gets bundled will look like. My current hacked up MSBuild distro is based on the xamarin fork as has no nuget pack support.

@borgdylan: You have to pull in the NuGet pack SDK and add some magic ImportAfter and ImportBefore files to get that to work.
My fork is also based on the Xamarin fork. However, we don't care about things like pack support. For OmniSharp, we just need files and references.

The pack crashes so I did the package download for nothing


Fixing migration error due to "null" value in AddTimeSlotReferrenceToBooking

I couldn't get the app to work on my computer because of the "null: false" value inside the AddTimeSlotReferrenceToBooking migration file, so I deleted it for now. I'm creating a separate pull request so that we can rollback easily if this needs to be reverted.

I think this might have been your migration, not sure @RobertLikesCoding letting you know just in case something breaks on your side, so that you know exactly where the change was. I removed "null: false".


OLS-1205: Bump-up Mypy to version 1.13

Description
Bump-up Mypy to version 1.13
The CI failure is fixed (unable to install all the packages due to conflict)
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[x] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-1205
Closes #

/hold

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.99%. Comparing base (110cb1a) to head (4ed0ee0).
Report is 30 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1836      +/-   ##
==========================================
- Coverage   94.95%   93.99%   -0.97%
==========================================
  Files          61       61
  Lines        2793     2829      +36
==========================================
+ Hits         2652     2659       +7
- Misses        141      170      +29

see 2 files with indirect coverage changes

/retest

/test e2e-ols-cluster-4-16

/unhold

/override "Red Hat Konflux / lightspeed-service-on-pull-request"
/approve

/lgtm

/test e2e-ols-cluster-4-17


Merge props / wrap components

Hi, 👋
This is more of a PureScript question than anything else, but still figured this is the best place to make it
How can I merge props like in js?
function Loading (extras) {
   return (<Video autoPlay {...extras} />)
}

but in PS
mkLoading
  :: forall attrs attrs_
   . Union attrs attrs_ Props_video
  => Effect (Record attrs -> React.JSX)
mkLoading = do

  React.component "Loading" \extras -> React.do

    pure
      ( DOM.video
          ( merge extras
              { autoPlay: true
              , loop: true
              , muted: true
              , playsInline: true
              , height: "24"
              , className: "loading"
              , children:
                  [ DOM.source
                      { type: "video/webm"
                      , src: "./assets/loader.webm"
                      }
                  , DOM.source
                      { type: "video/mp4"
                      , src: "./assets/loader.mp4"
                      }
                  ]
              }
          )
      )

This is a type error
No type class instance was found for

    Prim.Row.Union t0
                   t1
                   ( _aria :: Object String
                   , _data :: Object String
                   , about :: String
                   , acceptCharset :: String
                   , accessKey :: String
                   , allowFullScreen :: Boolean
                   , allowTransparency :: Boolean
                   , autoFocus :: Boolean
                   , autoPlay :: Boolean
                   , capture :: Boolean
                   , cellPadding :: String
                   , cellSpacing :: String
                   , charSet :: String
                   , children :: Array JSX
                   , classID :: String
                   , className :: String
                   , colSpan :: Int
                   , contentEditable :: Boolean
                   , contextMenu :: String
                   , controls :: Boolean
                   , crossOrigin :: String
                   , dangerouslySetInnerHTML :: { __html :: String
                                                }
                   , datatype :: String
                   , dateTime :: String
                   , dir :: String
                   , draggable :: Boolean
                   , encType :: String
                   , formAction :: String
                   , formEncType :: String
                   , formMethod :: String
                   , formNoValidate :: Boolean
                   , formTarget :: String
                   , frameBorder :: String
                   , height :: String
                   , hidden :: Boolean
                   , hrefLang :: String
                   , htmlFor :: String
                   , httpEquiv :: String
                   , icon :: String
                   , id :: String
                   , inlist :: String
                   , inputMode :: String
                   , is :: String
                   , itemID :: String
                   , itemProp :: String
                   , itemRef :: String
                   , itemScope :: Boolean
                   , itemType :: String
                   , key :: String
                   , keyParams :: String
                   , keyType :: String
                   , lang :: String
                   , loop :: Boolean
                   , marginHeight :: String
                   , marginWidth :: String
                   , maxLength :: Int
                   , mediaGroup :: String
                   , minLength :: Int
                   , muted :: Boolean
                   , noValidate :: Boolean
                   , onAbort :: EffectFn1 SyntheticEvent Unit
                   , onAnimationEnd :: EffectFn1 SyntheticEvent Unit
                   , onAnimationIteration :: EffectFn1 SyntheticEvent Unit
                   , onAnimationStart :: EffectFn1 SyntheticEvent Unit
                   , onBlur :: EffectFn1 SyntheticEvent Unit
                   , onCanPlay :: EffectFn1 SyntheticEvent Unit
                   , onCanPlayThrough :: EffectFn1 SyntheticEvent Unit
                   , onClick :: EffectFn1 SyntheticEvent Unit
                   , onCompositionEnd :: EffectFn1 SyntheticEvent Unit
                   , onCompositionStart :: EffectFn1 SyntheticEvent Unit
                   , onCompositionUpdate :: EffectFn1 SyntheticEvent Unit
                   , onContextMenu :: EffectFn1 SyntheticEvent Unit
                   , onCopy :: EffectFn1 SyntheticEvent Unit
                   , onCut :: EffectFn1 SyntheticEvent Unit
                   , onDoubleClick :: EffectFn1 SyntheticEvent Unit
                   , onDrag :: EffectFn1 SyntheticEvent Unit
                   , onDragEnd :: EffectFn1 SyntheticEvent Unit
                   , onDragEnter :: EffectFn1 SyntheticEvent Unit
                   , onDragExit :: EffectFn1 SyntheticEvent Unit
                   , onDragLeave :: EffectFn1 SyntheticEvent Unit
                   , onDragOver :: EffectFn1 SyntheticEvent Unit
                   , onDragStart :: EffectFn1 SyntheticEvent Unit
                   , onDrop :: EffectFn1 SyntheticEvent Unit
                   , onDurationChange :: EffectFn1 SyntheticEvent Unit
                   , onEmptied :: EffectFn1 SyntheticEvent Unit
                   , onEncrypted :: EffectFn1 SyntheticEvent Unit
                   , onEnded :: EffectFn1 SyntheticEvent Unit
                   , onError :: EffectFn1 SyntheticEvent Unit
                   , onFocus :: EffectFn1 SyntheticEvent Unit
                   , onGotPointerCapture :: EffectFn1 SyntheticEvent Unit
                   , onInvalid :: EffectFn1 SyntheticEvent Unit
                   , onKeyDown :: EffectFn1 SyntheticEvent Unit
                   , onKeyPress :: EffectFn1 SyntheticEvent Unit
                   , onKeyUp :: EffectFn1 SyntheticEvent Unit
                   , onLoadStart :: EffectFn1 SyntheticEvent Unit
                   , onLoadedData :: EffectFn1 SyntheticEvent Unit
                   , onLoadedMetadata :: EffectFn1 SyntheticEvent Unit
                   , onLostPointerCapture :: EffectFn1 SyntheticEvent Unit
                   , onMouseDown :: EffectFn1 SyntheticEvent Unit
                   , onMouseEnter :: EffectFn1 SyntheticEvent Unit
                   , onMouseLeave :: EffectFn1 SyntheticEvent Unit
                   , onMouseMove :: EffectFn1 SyntheticEvent Unit
                   , onMouseOut :: EffectFn1 SyntheticEvent Unit
                   , onMouseOver :: EffectFn1 SyntheticEvent Unit
                   , onMouseUp :: EffectFn1 SyntheticEvent Unit
                   , onPaste :: EffectFn1 SyntheticEvent Unit
                   , onPause :: EffectFn1 SyntheticEvent Unit
                   , onPlay :: EffectFn1 SyntheticEvent Unit
                   , onPlaying :: EffectFn1 SyntheticEvent Unit
                   , onPointerCancel :: EffectFn1 SyntheticEvent Unit
                   , onPointerDown :: EffectFn1 SyntheticEvent Unit
                   , onPointerEnter :: EffectFn1 SyntheticEvent Unit
                   , onPointerLeave :: EffectFn1 SyntheticEvent Unit
                   , onPointerMove :: EffectFn1 SyntheticEvent Unit
                   , onPointerOut :: EffectFn1 SyntheticEvent Unit
                   , onPointerOver :: EffectFn1 SyntheticEvent Unit
                   , onPointerUp :: EffectFn1 SyntheticEvent Unit
                   , onProgress :: EffectFn1 SyntheticEvent Unit
                   , onRateChange :: EffectFn1 SyntheticEvent Unit
                   , onScroll :: EffectFn1 SyntheticEvent Unit
                   , onSeeked :: EffectFn1 SyntheticEvent Unit
                   , onSeeking :: EffectFn1 SyntheticEvent Unit
                   , onSelect :: EffectFn1 SyntheticEvent Unit
                   , onStalled :: EffectFn1 SyntheticEvent Unit
                   , onSubmit :: EffectFn1 SyntheticEvent Unit
                   , onSuspend :: EffectFn1 SyntheticEvent Unit
                   , onTimeUpdate :: EffectFn1 SyntheticEvent Unit
                   , onTouchCancel :: EffectFn1 SyntheticEvent Unit
                   , onTouchEnd :: EffectFn1 SyntheticEvent Unit
                   , onTouchMove :: EffectFn1 SyntheticEvent Unit
                   , onTouchStart :: EffectFn1 SyntheticEvent Unit
                   , onTransitionEnd :: EffectFn1 SyntheticEvent Unit
                   , onVolumeChange :: EffectFn1 SyntheticEvent Unit
                   , onWaiting :: EffectFn1 SyntheticEvent Unit
                   , onWheel :: EffectFn1 SyntheticEvent Unit
                   , playsInline :: Boolean
                   , poster :: String
                   , prefix :: String
                   , preload :: String
                   , property :: String
                   , radioGroup :: String
                   , readOnly :: Boolean
                   , ref :: Ref (Nullable Node)
                   , resource :: String
                   , role :: String
                   , rowSpan :: Int
                   , scoped :: Boolean
                   , seamless :: Boolean
                   , security :: String
                   , slot :: String
                   , spellCheck :: Boolean
                   , src :: String
                   , srcDoc :: JSX
                   , srcLang :: String
                   , srcSet :: String
                   , style :: CSS
                   , suppressContentEditableWarning :: Boolean
                   , tabIndex :: Int
                   , title :: String
                   , typeof :: String
                   , unselectable :: Boolean
                   , useMap :: String
                   , vocab :: String
                   , width :: String
                   , wmode :: String
                   )

while applying a function video
  of type Union @Type t0 t1
            ( _aria :: Object String
            , _data :: Object String
            , about :: String
            , acceptCharset :: String
            , accessKey :: String
            , allowFullScreen :: Boolean
            , allowTransparency :: Boolean
            , autoFocus :: Boolean
            , autoPlay :: Boolean
            , capture :: Boolean
            , cellPadding :: String
            , cellSpacing :: String
            , charSet :: String
            , children :: Array JSX
            , classID :: String
            , className :: String
            , colSpan :: Int
            , contentEditable :: Boolean
            , contextMenu :: String
            , controls :: Boolean
            , crossOrigin :: String
            , dangerouslySetInnerHTML :: { __html :: String
                                         }
            , datatype :: String
            , dateTime :: String
            , dir :: String
            , draggable :: Boolean
            , encType :: String
            , formAction :: String
            , formEncType :: String
            , formMethod :: String
            , formNoValidate :: Boolean
            , formTarget :: String
            , frameBorder :: String
            , height :: String
            , hidden :: Boolean
            , hrefLang :: String
            , htmlFor :: String
            , httpEquiv :: String
            , icon :: String
            , id :: String
            , inlist :: String
            , inputMode :: String
            , is :: String
            , itemID :: String
            , itemProp :: String
            , itemRef :: String
            , itemScope :: Boolean
            , itemType :: String
            , key :: String
            , keyParams :: String
            , keyType :: String
            , lang :: String
            , loop :: Boolean
            , marginHeight :: String
            , marginWidth :: String
            , maxLength :: Int
            , mediaGroup :: String
            , minLength :: Int
            , muted :: Boolean
            , noValidate :: Boolean
            , onAbort :: EffectFn1 SyntheticEvent Unit
            , onAnimationEnd :: EffectFn1 SyntheticEvent Unit
            , onAnimationIteration :: EffectFn1 SyntheticEvent Unit
            , onAnimationStart :: EffectFn1 SyntheticEvent Unit
            , onBlur :: EffectFn1 SyntheticEvent Unit
            , onCanPlay :: EffectFn1 SyntheticEvent Unit
            , onCanPlayThrough :: EffectFn1 SyntheticEvent Unit
            , onClick :: EffectFn1 SyntheticEvent Unit
            , onCompositionEnd :: EffectFn1 SyntheticEvent Unit
            , onCompositionStart :: EffectFn1 SyntheticEvent Unit
            , onCompositionUpdate :: EffectFn1 SyntheticEvent Unit
            , onContextMenu :: EffectFn1 SyntheticEvent Unit
            , onCopy :: EffectFn1 SyntheticEvent Unit
            , onCut :: EffectFn1 SyntheticEvent Unit
            , onDoubleClick :: EffectFn1 SyntheticEvent Unit
            , onDrag :: EffectFn1 SyntheticEvent Unit
            , onDragEnd :: EffectFn1 SyntheticEvent Unit
            , onDragEnter :: EffectFn1 SyntheticEvent Unit
            , onDragExit :: EffectFn1 SyntheticEvent Unit
            , onDragLeave :: EffectFn1 SyntheticEvent Unit
            , onDragOver :: EffectFn1 SyntheticEvent Unit
            , onDragStart :: EffectFn1 SyntheticEvent Unit
            , onDrop :: EffectFn1 SyntheticEvent Unit
            , onDurationChange :: EffectFn1 SyntheticEvent Unit
            , onEmptied :: EffectFn1 SyntheticEvent Unit
            , onEncrypted :: EffectFn1 SyntheticEvent Unit
            , onEnded :: EffectFn1 SyntheticEvent Unit
            , onError :: EffectFn1 SyntheticEvent Unit
            , onFocus :: EffectFn1 SyntheticEvent Unit
            , onGotPointerCapture :: EffectFn1 SyntheticEvent Unit
            , onInvalid :: EffectFn1 SyntheticEvent Unit
            , onKeyDown :: EffectFn1 SyntheticEvent Unit
            , onKeyPress :: EffectFn1 SyntheticEvent Unit
            , onKeyUp :: EffectFn1 SyntheticEvent Unit
            , onLoadStart :: EffectFn1 SyntheticEvent Unit
            , onLoadedData :: EffectFn1 SyntheticEvent Unit
            , onLoadedMetadata :: EffectFn1 SyntheticEvent Unit
            , onLostPointerCapture :: EffectFn1 SyntheticEvent Unit
            , onMouseDown :: EffectFn1 SyntheticEvent Unit
            , onMouseEnter :: EffectFn1 SyntheticEvent Unit
            , onMouseLeave :: EffectFn1 SyntheticEvent Unit
            , onMouseMove :: EffectFn1 SyntheticEvent Unit
            , onMouseOut :: EffectFn1 SyntheticEvent Unit
            , onMouseOver :: EffectFn1 SyntheticEvent Unit
            , onMouseUp :: EffectFn1 SyntheticEvent Unit
            , onPaste :: EffectFn1 SyntheticEvent Unit
            , onPause :: EffectFn1 SyntheticEvent Unit
            , onPlay :: EffectFn1 SyntheticEvent Unit
            , onPlaying :: EffectFn1 SyntheticEvent Unit
            , onPointerCancel :: EffectFn1 SyntheticEvent Unit
            , onPointerDown :: EffectFn1 SyntheticEvent Unit
            , onPointerEnter :: EffectFn1 SyntheticEvent Unit
            , onPointerLeave :: EffectFn1 SyntheticEvent Unit
            , onPointerMove :: EffectFn1 SyntheticEvent Unit
            , onPointerOut :: EffectFn1 SyntheticEvent Unit
            , onPointerOver :: EffectFn1 SyntheticEvent Unit
            , onPointerUp :: EffectFn1 SyntheticEvent Unit
            , onProgress :: EffectFn1 SyntheticEvent Unit
            , onRateChange :: EffectFn1 SyntheticEvent Unit
            , onScroll :: EffectFn1 SyntheticEvent Unit
            , onSeeked :: EffectFn1 SyntheticEvent Unit
            , onSeeking :: EffectFn1 SyntheticEvent Unit
            , onSelect :: EffectFn1 SyntheticEvent Unit
            , onStalled :: EffectFn1 SyntheticEvent Unit
            , onSubmit :: EffectFn1 SyntheticEvent Unit
            , onSuspend :: EffectFn1 SyntheticEvent Unit
            , onTimeUpdate :: EffectFn1 SyntheticEvent Unit
            , onTouchCancel :: EffectFn1 SyntheticEvent Unit
            , onTouchEnd :: EffectFn1 SyntheticEvent Unit
            , onTouchMove :: EffectFn1 SyntheticEvent Unit
            , onTouchStart :: EffectFn1 SyntheticEvent Unit
            , onTransitionEnd :: EffectFn1 SyntheticEvent Unit
            , onVolumeChange :: EffectFn1 SyntheticEvent Unit
            , onWaiting :: EffectFn1 SyntheticEvent Unit
            , onWheel :: EffectFn1 SyntheticEvent Unit
            , playsInline :: Boolean
            , poster :: String
            , prefix :: String
            , preload :: String
            , property :: String
            , radioGroup :: String
            , readOnly :: Boolean
            , ref :: Ref (Nullable Node)
            , resource :: String
            , role :: String
            , rowSpan :: Int
            , scoped :: Boolean
            , seamless :: Boolean
            , security :: String
            , slot :: String
            , spellCheck :: Boolean
            , src :: String
            , srcDoc :: JSX
            , srcLang :: String
            , srcSet :: String
            , style :: CSS
            , suppressContentEditableWarning :: Boolean
            , tabIndex :: Int
            , title :: String
            , typeof :: String
            , unselectable :: Boolean
            , useMap :: String
            , vocab :: String
            , width :: String
            , wmode :: String
            )
           => Record t0 -> JSX
  to argument (merge extras) { autoPlay: true
                             , loop: true
                             , muted: true
                             , playsInline: true
                             , height: "24"
                             , className: "loading"
                             , children: [ ...
                                         , ...
                                         ]
                             }
while inferring the type of video ((merge extras) { autoPlay: ...
                                                  , loop: ...
                                                  , muted: ...
                                                  , playsInline: ...
                                                  , height: ...
                                                  , className: ...
                                                  , children: ...
                                                  }
                                  )
in value declaration mkLoading

where t0 is an unknown type
      t1 is an unknown type
PureScript(NoInstanceFound)

Thank a lot for your time and this lib ✨

The way Union is used in the DOM modules is a little bit of a hack which could make this difficult to do. Essentially, it leaves one of the two inputs to Union completely unused, so the compiler is free to assume anything it wants to about it. This works in the DOM module where the implementation is in FFI, but that argument is completely unusable within PureScript.
You could maybe accomplish this with an unsafeCoerce though.. maybe in your call to merge you can merge (unsafeCoerce extras) ...? I'm not on a computer where I can easily play with it at the moment.

I just ran into this. Did anyone find a better way?

This is what I get after cleaning up the inferred type for @codingedgar's original example. It seems to work as intended, though I can't say I fully understand the row type constraints 😅 Try PureScript example here
import Prelude

import Effect (Effect)
import Prim.Row (class Nub, class Union)
import React.Basic.DOM as DOM
import React.Basic.DOM.Generated (Props_video)
import React.Basic.Hooks (Component)
import React.Basic.Hooks as React
import Record (merge)

-- These are the attributes that are pre-supplied by the `mkLoading` wrapper
type DefaultAttrs =
  ( autoPlay :: Boolean
  , children :: Array React.JSX
  , className :: String
  , height :: String
  , loop :: Boolean
  , muted :: Boolean
  , playsInline :: Boolean
  )

mkLoading
  :: forall attrs attrs_ extras unioned
   . Union attrs attrs_ Props_video
  => Union extras DefaultAttrs unioned
  => Nub unioned attrs
  => Component (Record extras)
mkLoading = do

  React.component "Loading" \extras -> React.do

    pure
      ( DOM.video
          ( merge extras
              { autoPlay: true
              , loop: true
              , muted: true
              , playsInline: true
              , height: "24"
              , className: "loading"
              , children:
                  [ DOM.source
                      { type: "video/webm"
                      , src: "./assets/loader.webm"
                      }
                  , DOM.source
                      { type: "video/mp4"
                      , src: "./assets/loader.mp4"
                      }
                  ]
              }
          )
      )

Maybe another option, if you don't want to declare the DefaultAttrs type (and don't mind the compiler warning about the missing type annotation on mkLoading):
mkLoadingWithDefaults
  :: forall attrs attrs_ extras defaults unioned
   . Union attrs attrs_ Props_video
  => Union extras defaults unioned
  => Nub unioned attrs
  => Record defaults
  -> Component (Record extras)
mkLoadingWithDefaults defaults = do
  React.component "Loading" \extras -> React.do
    pure (DOM.video (merge extras defaults))

mkLoading = mkLoadingWithDefaults
  { autoPlay: true
  , loop: true
  , muted: true
  , playsInline: true
  , height: "24"
  , className: "loading"
  , children:
      [ DOM.source
          { type: "video/webm"
          , src: "./assets/loader.webm"
          }
      , DOM.source
          { type: "video/mp4"
          , src: "./assets/loader.mp4"
          }
      ]
  }


How can I get it to work in IE?

I'm asking because I can't find any relevant documentation anywhere.
The editor does not load at all in IE.
The first reason was that loading the colorSyntax plugin with curly braces was incompatible,
so I removed it
Then the editor was loaded in IE, but writing was blocked. what's the reason?

@Kyung-A
The editor works in IE.
If it doesn't work, please provide more information on how it doesn't work with detailed code and some screenshots.


Owning this project to test Azure webhook of functions

first comment on the issue

second comment

fourth comment

fifth comment !!! great

sixth comment>>>

seventh comment !!

eighth comment !!! worked1


chore: Update .codegen.json with commit hash of codegen and openapi spec

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6808

Relevant Lines:
8559

💛  - Coveralls


consider a better name for "emulate scrolling in fullscreen buffers"

From #15: @prevent-scroll-for-fullscreen-alternate-buffer now actually enables scroll for those buffers, by emulating it.
Find a better name for this option.

My current best idea is @emulate-scroll-for-no-mouse-alternate-buffer.

Sounds OK to me :) I wonder if it might be worth enabling it by default? I suspect that the majority of people installing the plugin will want scrolling to "just work" in tmux, rather than compatibility with old tmux versions. Not a big deal, though, since the README isn't long.

I wonder if it might be worth enabling it by default?

Yeah, I agree. But up until now, the default options have all been set to emulate the pre-2.1 behavior.
I've been considering changing the defaults to just be the best/most natural behavior, but I don't want to break people's configurations... I'm not sure how to make that change?

Fixed in 5e4c864.

I'm not sure most would consider it a break. If they've installed the plugin and left everything at default behaviour, it's probably because they're not too fussed about the behaviour, and if anything will probably be in for a pleasant surprise on upgrade. Those that specifically want compatibility with old tmux behaviour (do we know these people exist?) will probably be fussy enough that they'll notice the change immediately and refer to the README to modify their config.


I can't put characters in 0.52h

Describe your bug here.
In 0.52h, I can't write character names or pose names, please help Shadow.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I made characters in it.

click r then retry

@keanu64github what do you mean how does that help

Click the “R” key on your keyboard, and try again.

Same, it won't let me input any text when i zoom in/out

@AlansGames no it wont left me type anyway

@keanu64github ok

It only works for me when you're character editing in the main menu

@keanu64github thanks


 To run them, pytest command is enoug
I tried to test pretty much all of the features that manim currently has. Don't hesitate to tell if some miss.
Functioning :
See #34 and #97.
For performances purpose it just compares the last frame with a previously-rendered one (and not a frame every n seconds, as it was mentioned in #34. On my computer, it takes around 30 seconds.
Adding a new test
I created the function utils.set_test that is intended to be used when we add a new feature.
I think that we should create a section in the wiki to explain how to create a new test and mention it in #127.
For the moment I marked this PR as a draft since it uses some stuff (see conftest.py) that will be completely rewritten when #98 is merged.
closes #28 closes #34 closes #97

As a lot of things depend on when this PR is merged, I propose to merge it now.
All of the suggestions that were said here were all very good and I'm working on them, but don't concern the core of tests.  I will do another PR.

what are the tests_cache and tests_data directories for? Shouldn't Travis or whatever automatically generate those folders? Then they shouldn't be in the repo and should be in .gitignore
Also, should we follow guidelines and also add typings to the testing_utils.py file?

These files are the whole point of the tests. tests_data contains the previously rendered frames that serve for the comparison (if the frames match, then all good and if not, a thing had been changed). Thus, in essence, it can't be generated by Travis itself.
tests_cache is the cache used sometimes in the tests. In that case, for the moment, only TexTest uses it, because the purpose of this test is not to test the caching functionality of manim. That is tested somewhere else, in an end-to-end test.
About typing stuff, maybe you're right but that's not the correct PR to do that, I think.

These files are the whole point of the tests. tests_data contains the previously rendered frames that serve for the comparison (if the frames match, then all good and if not, a thing had been changed). Thus, in essence, it can't be generated by Travis itself.

I see. In this case, the files should be stored elsewhere in my opinion, such as in a separate branch or site or whatever, then we should have Travis fetch those.

tests_cache is the cache used sometimes in the tests. In that case, for the moment, only TexTest uses it, because the purpose of this test is not to test the caching functionality of manim. That is tested somewhere else, in an end-to-end test.

Same comment as above ^

About typing stuff, maybe you're right but that's not the correct PR to do that, I think.

You're probably right, but what about documentation following the guidelines?

I see. In this case, the files should be stored elsewhere in my opinion, such as in a separate branch or site or whatever, then we should have Travis fetch those.

To be honest, I don't think this is a good idea. For two main reasons :

This seems to be complicated to set up and .. maybe it is not worth it. But I'm not an expert, so maybe I'm wrong here.
We have to think of when someone adds new functionality or modify one, one must be able to add/modify a frame contained in test_data. With this system, this would make the thing not simple.

But why do you want this? Is there like a convention or something? Or is it just cleaner ?
For documentation following the guidelines, you are totally right. I will commit asap.

But why do you want this? Is there like a convention or something? Or is it just cleaner ?

I simply thought it would be cleaner in a way, given that we will all be cloning this repo (+ users downloading, soon) so I thought it would be a good idea to have a lot of otherwise irrelevant "bloat" yk. There probably are alternatives here, but we gotta think this through

Then if you find a way that would be nice, I would suggest doing a new PR

The test cache files are an integral part of the testing system we have setup. I think they should be in this repo, in the tests directory.
@huguesdevimeux you do raise a good point. Most of our comments were not about the core testing system that this is setting up. Can I ask you to please extract the standing discussion points and making separate issues for those that warrant it?
If you think this is ready to be merged, then say so and I'll merge it.


Added a return error code, with appropriate error handling for authentication errors

Whenever an authentication error occurs, return HTTP Status FORBIDDEN.

Issue with the acorn API throwing weird exceptions (not sure why, but just catching LoginFailedException doesn't return the right code.)


Publish to npm

Is this published on npm? Searched and couldn't find it.

Let me give you a backstory :) This is the whole reason I created this project. It was supposed to 'proofread' one very specific group of documents. And if you'll look into the source code you'll find stuff specific for these docs (e.g. custom dictionary ). Proofreader is super small (~100LOC) and unimpressive (it just prints out results from two other projects), it wasn't meant for general public :) I'm OK though with making it a bit more general if people find it useful, but the big question is "how?":

should I move all custom stuff (dictionaries, html tags that are processed) to a settings file? How would that work for npm install proofreader -g scenario?
should I just create grunt/gulp wrappers for 'write-good' and 'nodehun' and abandon 'proofreader'?
should I do something else?

I'm open for ideas.

I ended up making it a bit more general and publishing it to NPM. All custom settings were moved to a settings file.


[IOTS-240] It would be better if the server could let the devices know when an HTTP event was not processed as a valid event

According to the HTTP receiver implementation found in the arduino sample, the receiver responds with a 200 OK for any request conforming to the expected format. As this is the case a 200 is sent regardless of validity of the data being sent(invalid json payloads, invalid device id query params etc).  It would be better if the server could let the devices know that the event sent was not processed as a valid event. Reference: https://wso2.org/jira/browse/IOTS-240

This is removed hence closing, HTTP receiver is handle through loT core


Pybind11

This branch replaces Boost Python with pybind11. This allows easier installation, easier distribution, and---last but not least---Python 3 support (fixes #14).

Great work!


Lift M.ANC.Sockets.Common to .NET Standard 2.0

Part of https://github.com/aspnet/Coherence-Signed/issues/533

@natemcmaster,
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


Increase todrive max cell count

https://support.google.com/drive/answer/37603?hl=en

Not that the docs are ever wrong (cough) but did you test this limit?

Not directly. I have a user in Sweden where Gam wouldn't upload a file as a sheet because of the cell count limit; it was uploaded as a CSV file. He went into drive and successfully converted it to a sheet.
<EMAIL_ADDRESS>
On Oct 8, 2017, at 7:50 AM, Jay Lee<EMAIL_ADDRESS>wrote:
Not that the docs are ever wrong (cough) but did you test this limit?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jay0lee/GAM/pull/615#issuecomment-335011662, or mute the thread https://github.com/notifications/unsubscribe-auth/AIU8L3JtzLlyWXAFfVG9tLP017m0nW5yks5sqOFAgaJpZM4PxtTj.

Can you test even with junk data not pulled from API? I feel like I tried to bump limit at one point and it failed to convert via API even though UI could.
Other option would be to remove limit, always yet convert and disable convert on retry if it fails with the limit error but that assumes limit failure returns a unique write and not something like a 5xx which would also need testing.

Jay,
$ gam user admin print filelist fields appdatacontents,cancomment,canreadrevisions,capabilities,copyable,createddate,description,editable,explicitlytrashed,fileextension,filesize,foldercolorrgb,fullfileextension,headrevisionid,iconlink,id,lastmodifyinguser,lastmodifyingusername,lastviewedbyme,md5,mime,modifiedbyme,modifieddate fields name,originalfilename,ownedbyme,ownernames,owners,parents,quotabytesused,restricted,shareable,shared,sharedwithmedate,sharinguser,size,spaces,starred,thumbnaillink,title,trashed,userpermission,version,viewed,viewerscancopycontent,webcontentlink,webviewlink todrive tdtitle "AdminFiles"
Getting all Drive Files/Folders that match query ('me' in owners) for<EMAIL_ADDRESS>Got 460 Drive Files/Folders for<EMAIL_ADDRESS>Got 920 Drive Files/Folders for<EMAIL_ADDRESS>Got 1380 Drive Files/Folders for<EMAIL_ADDRESS>Got 1840 Drive Files/Folders for<EMAIL_ADDRESS>Got 2300 Drive Files/Folders for<EMAIL_ADDRESS>Got 2760 Drive Files/Folders for<EMAIL_ADDRESS>Got 3220 Drive Files/Folders for<EMAIL_ADDRESS>Got 3680 Drive Files/Folders for<EMAIL_ADDRESS>Got 4140 Drive Files/Folders for<EMAIL_ADDRESS>Got 4600 Drive Files/Folders for<EMAIL_ADDRESS>Got 5060 Drive Files/Folders for<EMAIL_ADDRESS>Got 5520 Drive Files/Folders for<EMAIL_ADDRESS>Got 5980 Drive Files/Folders for<EMAIL_ADDRESS>Got 6440 Drive Files/Folders for<EMAIL_ADDRESS>Got 6900 Drive Files/Folders for<EMAIL_ADDRESS>Got 7360 Drive Files/Folders for<EMAIL_ADDRESS>Got 7820 Drive Files/Folders for<EMAIL_ADDRESS>Got 8149 Drive Files/Folders for<EMAIL_ADDRESS>Rows: 8149, Columns: 75, Cells: 611175
Uploaded as sheet successfully.
Ross
<EMAIL_ADDRESS>
On Oct 8, 2017, at 8:03 AM, Jay Lee<EMAIL_ADDRESS>wrote:
Can you test even with junk data not pulled from API? I feel like I tried to bump limit at one point and it failed to convert via API even though UI could.
Other option would be to remove limit, always yet convert and disable convert on retry if it fails with the limit error but that assumes limit failure returns a unique write and not something like a 5xx which would also need testing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/jay0lee/GAM/pull/615#issuecomment-335012616, or mute the thread https://github.com/notifications/unsubscribe-auth/AIU8L_fKmH_VBhvbyaoE94NLowx2GmjDks5sqORegaJpZM4PxtTj.

I tested with 2m cells also and it works, go over that though and you hit an API error.
Can you remove the temp gam.py~ from this PR before I merge?


added metadata view in mitm\web

Description
closes #5704

Added metadata viewer in mitm\web.

Checklist

[x] I have updated tests where applicable.
[x] I have added an entry to the CHANGELOG.

I don't think any test is required in this case

I assume you or the editor you're using were doing some automatic code formatting. This makes it hard to focus on the actual changes. We should definitely clean this up at some point (e.g. mixed single/double quotes or missing spaces) but it would be better not to have these changes in this PR.

I tried to have the proper formatting for web but there is no formatter config available
Maybe in the web we can use prettier for web

I've opened https://github.com/mitmproxy/mitmproxy/issues/5984 to fix this in the future. For now I recommend disabling any formatting your editor does. That's a recommendation I would give in general when contributing to a project. Formatting changes make PRs unnecessarily noisy. Unrelated code should not be touched.

Ok i will submit make the changes and push it

ignore: to make it easy to compare changes
made this commit to revert the changes to original formatting
changes made in mitm web
made the changes without formatting

Perfect, I think that's good for a first iteration. Two small changes:

We should allow any type of metadata, so I'd check for null (None in Python) and throw everything else into JSON.stringify. Fun fact, strings are already rendered because Object.keys('foo') is [ '0', '1', '2' ]
Indent the JSON, e.g. JSON.stringify(flow.metadata, null, 4)

@Prinzhorn
i have messed up my fork by clicking on discard button when updating my fork
which closed this PR do you mind opening it again
I have made the changes you asked in 1st iteration


MWE for 718

using DataFrames,Gadfly,Colors
function test()
df = readtable("test_df.csv");
slope_act = df[:slopes];
y_inter_act = df[:intercepts];
x = hcat(y_inter_act,slope_act)';
e1,e2,counts = hist2d(x',collect(0:1:100),collect(-10:.2:10));
# produces 24
maximum(counts)
p1 = plot(layer(y=slope_act,x=y_inter_act,Geom.histogram2d(xbincount=100,ybincount=100)),
Guide.title("slopes vs intercepts from Geom.histogram2d"),
Guide.xticks(ticks=[0,25,50,75,100]),Guide.yticks(ticks=[-10,-5, 0, 5,10]),
Theme(panel_fill=RGB(.5,.5,.5)));
draw(PDF("example1.pdf",6inch,4inch),p1);
x_range_small = collect(0:1:100);
y_range_small = collect(-10:.2:10);
e1,e2,counts = hist2d(x',x_range_small,x_range_small);
mids_x = collect(0.5:1:99.5);
mids_y = collect(-9.9:.2:9.9);
intercepts = reshape(repmat(mids_x,1,100),10000);
slopes = reshape(repmat(mids_y,1,100)',10000);
max_v = floor(maximum(counts)/2);
e1,e2,counts = hist2d(x',x_range_small,y_range_small);
counts = reshape(counts,10000);
p2 = plot(layer(x=intercepts,y=slopes,color=counts,Geom.rectbin),
Guide.title("slopes vs intercepts from Geom.rectbin"),
Guide.xticks(ticks=[0,25,50,75,100]),Guide.yticks(ticks=[-10,-5, 0, 5,10]));
draw(PDF("example2.pdf",6inch,4inch),p2);
non_zero = counts.!=0;
intercepts = intercepts[non_zero];
slopes = slopes[non_zero];
counts = counts[non_zero];
p3 = plot(layer(x=intercepts,y=slopes,color=counts,Geom.rectbin),
Guide.title("slopes vs intercepts from Geom.rectbin - zero counts removed"),
Guide.xticks(ticks=[0,25,50,75,100]),Guide.yticks(ticks=[-10,-5, 0, 5,10]));
draw(PDF("example3.pdf",6inch,4inch),p3);
end

Can you:

put this in #718 where it belongs
wrap the code with triple-backticks and indent properly... this is unreadable

Ok, that worked.
Do you have any advice as to how to get the data frame that instigates the apparent problems better and more clearly than any random data I was able to muster uploaded in the issue?
Cut and past into a comment didn’t seem practical - since it’s almost 8K pairs of points.
I tried renaming the .csv to .txt, zipping it and changing the suffix, etc.
Stephen

On Oct 7, 2015, at 3:35 PM, Tom Breloff<EMAIL_ADDRESS>wrote:
Can you:
• put this in #718 where it belongs
• wrap the code with triple-backticks and indent properly... this is unreadable
—
Reply to this email directly or view it on GitHub.

Closed in favor of #718. Thanks for the example, that made it easy.

Glad it helped.
Is there a more githubbish way to provide data files - the only thing that seemed even remotely possible was to submit a pull request with just the data file? I can’t imagine how often this will be important but it seems like if there is a way to do it, it would be great to know about it ahead of time.
Stephen

On Oct 15, 2015, at 8:49 PM, Daniel C. Jones<EMAIL_ADDRESS>wrote:
Closed in favor of #718. Thanks for the example, that made it easy.
—
Reply to this email directly or view it on GitHub.

You can post individual files on gist, which is probably the most githubbish way to do that. I don't mind having it emailed to me either. That makes it harder for anyone else to fix it, but it's generally me who needs to fix these sorts of things anyway.


Vim language server gives error

When running vim .vimrc I get the following error.
".vimrc" 110L, 3340B
LSP server exited with status -1
Error detected while processing BufRead Autocommands for "*"..function lsp#lsp#AddFile[23]..<SNR>22_StartServer[39].
.<SNR>22_InitServer[73]..<SNR>22_AsyncRpc:
line   24:
E630: ch_sendexpr(): Write while not connected

This error only shows for vim files. My vim lsp config is
		\	 filetype: 'vim',
		\	 path: '/usr/local/bin/vim-language-server',
		\	 args: ['--stdio']
		\      },

Any idea why I might be seeing this?

It works fine for me. Can you provide the relevant snippet around line 24?

I think the vim-language-server is exiting before the plugin could connect to it.  Can you try running the Vim language server manually from the command line with the argument "--stdio" and see whether the server runs successfully?


[$500] mWeb-IOU- In distance request, merchant section shows distance@rate/mile

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.81-4
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Go to https://staging.new.expensify.com/
Tap on a Workspace chat
Tap plus icon
Select request money --- Distance
Enter start and finish way points
Tap next and note "distance" and "merchant" section

Expected Result:
The "distance" section must show distance@rate/mile
and "merchant" section must be empty.
Actual Result:
The "distance" and "merchant" section shows the same details distance@rate/mile.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome
https://github.com/Expensify/App/assets/115492554/690cbb62-6abe-46a6-a2cb-bac6c635532f

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01f20eff3688173d74
Upwork Job ID:<PHONE_NUMBER>405523968
Last Price Increase: 2023-10-12

This is fixed in staging


Crash on Debian Wheezy with official 1.9.8 binaries

I'm experiencing reproducible crashes with the latest PhantomJS 1.9.x release on Debian Wheezy.
Here is the stack trace: http://pastebin.com/szVE735Y.
Any idea what is happening?

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2.0.


can you/how can you continue training?

Hi guys,
Is it possible to continue training from where it left off? I know it is a silly question. I know that it saves checkpoints after each epoch for generating the audio. Is there a way carry on training after it has been shutdown?
Thank you!  Starting to get alright results too

If you didn't mess with the code - it should continue training from the latest saved checkpoint.

When I type in python3 train.py and I print the current epoch it starts again from 1. Is there a way to check that it continues training?

As far as I remember, epochs aren't saved with the model. It's just a range that the code iterates over. You may want to check with tensorboard and see if your graphs start from scratch (they shouldn't)

@ahmed-tbox  yeah, you can see Supervisor in tensorflow. here is the guide.
https://www.tensorflow.org/versions/r1.0/api_docs/python/tf/train/Supervisor

@ahmed-tbox   it would continue training from the latest saved checkpoint.
you can see Supervisor in tensorflow. here is the URL.
www.tensorflow.org/versions/r1.0/api_docs/python/tf/train/Supervisor

@ahmed-tbox  it would continue training from the latest saved checkpoint.
you can see Supervisor in tensorflow . here is the guide.

Is it possible to continue training from another model that was run on a different machine? I used a machine that ran on 1 GPU with train.py and on the new machine I am using 2 GPUs with train_multi_gpus.py will that affect anything? What files do I need to transfer over if I need to?


Add transition effects to slides

Should be codable at the slide level and persist until the next value of the metadata item.
Experimentation shows both "ripple" and "reveal" work as effects.

Released as v3.4.


ARROW-3804: [R] Support older versions of R runtime

vctrs requires 3.1: https://github.com/r-lib/vctrs/blob/master/DESCRIPTION#L15, but no functionality makes use of 3.5, at least, not yet.
Fix for: https://issues.apache.org/jira/browse/ARROW-3804

@romainfrancois can you rerun the travis tests here? Not sure if the GITHUB_PAT got added to travis but at least we can retry.

I have modified this so that:

in the DESCRIPTION we express that this is supported for R >= 3.1
but on Travis testing it against released R

At some point we'll need to figure out a better strategy for testing the R package against various versions of R, supported platforms, etc ...

I would greatly appreciate it if this got merged in :)

@romainfrancois I've created an issue to test against multiple R versions in the nightlies: https://issues.apache.org/jira/browse/ARROW-5134


Turn off bell on the activity of other windows

Hello 👋
In iterm2 I am using "Flash visual bell" and for now it was working fine in terminal but it doesn't work well with tmux equipped with oh-my-tmux sending the bell signals on terminal outputs of other windows. I have tried setting tmux_conf_theme_window_status_activity_attr="none" and it turns off the underline on tab activity but the terminal is still flashing, so I guess bell signal is still sent.
That's why I wanted to ask you if there is a way to turn off the bell symbol for oh-my-tmux on the activity of other windows?

Hello @Jendker 👋
I think you want to play with tmux_conf_theme_window_status_format and tmux_conf_theme_window_status_current_format.
Try setting them to
tmux_conf_theme_window_status_format="#I #W"
tmux_conf_theme_window_status_current_format="#I #W"

Hello @gpakosz thank you for your answer!
Hmm that didn't quite help. I'm still getting the bell signal. Should I check it with iterm people?

I don't know what you mean by "I'm still getting the bell signal".
From the terminal, you can use tput bel to produce a bell and debug what's happening.

BTW,

but it doesn't work well with tmux equipped with oh-my-tmux sending the bell signals on terminal outputs of other windows

Do you observe a different behavior with and without Oh my tmux!?
You can test launching tmux with no configuration:
$ tmux -L test -f /dev/null

If I call tput bel I am getting the exact same effect as with oh-my-tmux on activity on another window - the beep in terminal.
I just checked after starting tmux without configuration as you suggested with
$ tmux -L test -f /dev/null

and then on activity in another window I don't get any beeping.
Would you recommend consulting this with iterm developers? I do appreciate your time.

Well what I know is that Oh my tmux! does only visual things.
You initially asked

That's why I wanted to ask you if there is a way to turn off the bell symbol for oh-my-tmux on the activity of other windows?

Yes you can, edit your .local customization file and use
tmux_conf_theme_window_status_format="#I #W"
tmux_conf_theme_window_status_current_format="#I #W"

Then relaunch tmux and Oh my tmux!

and then on activity in another window I don't get any beeping.

But now you're mentioning sound.

Start tmux with tmux -f /dev/null to skip Oh my tmux! loading.

Once done, start tmux with Oh my tmux!
See if there's a difference. The only difference I expect will depend on the values you chose for tmux_conf_theme_window_status_format and tmux_conf_theme_window_status_current_format.
Hope that helps!

I will continue from here and try to find a solution without disabling audible or visual bell. Thank you you so much for a quick response!


question

hey; i just bought the humidifier and found this plugin; I wanted to understand if this replace the firmware entirely with all the associated functions (like starting when the humidity is low, etc...)

It only repaces the firmware of the wifi module.
The whole business-logic of the humidifier is done by a different uC with its own firmware.
Wi-Fi module and the other uC talk to each other via uart

That is awesome!
I don't use home assistant, I use home bridge instead, I'm not sure if your firmware is already compatible with homebridge-mqtthing but I guess I can just modify to work with it, right?

No idea. I'm honestly not a big fan of that whole apple golden cage thing

No idea. I'm honestly not a big fan of that whole apple golden cage thing

Yeah I see. in the end it talks with using mqtt, I just need to configure the topics and the data format.
I'll let you know!

One annoying quirk of that humidifier is that it resets the target humidity to 54% every time you toggle between setpoint and any other option (low, med, high).
Your code might need to be aware of that

Is this not a problem with home assistant or is it a problem there as well?
Where is this bug coming from?

A related question: can I actually back up the firmware before flushing it, do you have any link that explain the procedure?

Where is this bug coming from?

The firmware of the device.

can I actually back up the firmware before flashing it?

No idea

Thanks then! 😉


Deploying is stuck on devnet

When deploying on devnet, the terminal says:"Deploying... This could take a while depending on the program size and network conditions.", and is stuck, even if it's a helloworld program.
Information:

F12, Console log: Buffer pk: ByqpbZVZmCZsU5WLCyTRE4NtiZcUKSaughJDfsQCAMnr
it seems there is no such issue on testnet

Unfortunately, it's because devnet is currently down.
Here are some links to track this issue:
https://explorer.solana.com/?cluster=devnet
https://twitter.com/SolanaDevnet/status/1781116618321608735
https://discord.com/channels/428295358100013066/749059399875690557/1230677600725368913
It would be nice to be able to display a notification of some sorts when the current cluster is down, but not sure what's the best way to decide if a cluster is down or not since it could just be an RPC that's down.

thanks a lot !!!


[ ThemeContext ] Dependency not aligned

On v4.0.0-alpha.7 release, dependency for @material-ui/styles was not aligned in package.json
When importing both core and styles v4.0.0-alpha.7 on my project, my ThemeProvider is not taken in consideration.

@timaxxer Do you bundle two different versions of @material-ui/styles?

In your package.json for core alpha7, you have dependency on styles alpha6. If I use styles alpha 7 in my project, the Theme context provider doesn’t push down the right context to your style alpha 6 dependency.
I fix my current problem by using style alpha 6. Ionly pointed the fact that maybe poeple using  both core alpha7 and styles alpha 7 will have theme problem

We are using ^ as the dependency range it maches more recent versions. It shouldn't be an issue.

Effectivly, I’ll try to figure the problem, thanks for the quick response

@timaxxer I was running into this conflict too and not understanding why this was happening yarn list @material-ui/styles:
├─<EMAIL_ADDRESS>│  └─<EMAIL_ADDRESS>└─<EMAIL_ADDRESS>
So I ended up removing @material-ui/styles from my package.json, getting rid of node_modules and re-installing @material-ui/core which resulted in yarn list @material-ui/styles:
└─<EMAIL_ADDRESS>
Not sure why @material-ui/core is not picking up 4.0.0-alpha.7 in its package.json per @oliviertassinari :
"@material-ui/styles": "^4.0.0-alpha.6",

We may need to keep them explicit on next releases?

@JeromeFitz You can run yarn check to detect packages that can be deduplicated. I would usually recommend manually patching the lockfile instead. We recently did this with our own in case you need some inspiration: #15260. You could also try out yarn-deduplicate. yarn v2 hopefully improves a lot of these edge cases.

Thank you @eps1lon .
I tend to always forget removing yarn.lock when going the route of throwing node_modules out (and not the first time with this alpha 😆 ).
Did those steps and am back in business with explicitly having @material-ui/styles in the package.json.

The simplest strategy is probably to remove the yarn.lock and to run a new installation. I use this strategy all the time.

It's what I find the simplest without any significant downsides.

This is a YOLO approach. Don't do this in production unless you actually want to vet ~2k line changes.

😆. If you have a great test suite, the capability to monitor issues and to quickly revert changes, it should be fine.

I was careful with the release of 4.0.0-alpha.8. I have increased the dependency to all the packages to alpha.8

I'm adding a warning as well as a FAQ about the problem.

The problem was reported multiple times. The pain is not likely to go away in the future. I would rather address it early. It's a good reminder that bundling everything in a single package is simpler. However, the separation of @material-ui/core with @material-ui/styles is an important step forward for us. I'm gonna apply the same solution than styled-components: https://github.com/styled-components/styled-components/pull/1412.

Thank you very much as always @oliviertassinari 💯

import React from 'react';
var ThemeContext = React.createContext(null);
export default ThemeContext;
I am using material UI while small  material  UI control  assigned in app.js  page and loading that  time am getting the issue


CDN Issue

I deployed umami by docker, first I use not modified Dockerfile to build docker image on Dockerhub, then pull & run Docker container use docker-compose to start up containers in my VPS.
When I visit http://ip:3000, no error occurred.
But when I try to use CDN to reverse proxy http://ip:3000 by https and visit https://cdn-domain:443, I get error on Dashboard page:

Then I use nginx to reverse proxy http://vps-ip:3000 to https://vps-domain:443 and visit https://vps-domain:443 , no error occurred.
Finally I use https CDN to reverse proxy https://vps-domain:443 and visit https://cdn-domain:443, the error is same as the picture.
When I use docker-composed up to start containers and use https://cdn-domain:443 to visit umami, I can see error logs like that:
umami    | PrismaClientKnownRequestError2: Failed to validate the query: `Unable to match input value to any allowed input type for the field. Parse errors: [Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at.DateTimeNullableFilter.gte`: A value is required but not set., Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at`: Value types mismatch. Have: Object({"gte": Null}), want: DateTime, Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at`: Value types mismatch. Have: Object({"gte": Null}), want: Null]` at `Query.findManypageview.where.pageviewWhereInput.created_at`
umami    |     at PrismaClientFetcher.request (/app/node_modules/@prisma/client/runtime/index.js:78537:15)
umami    |     at runMicrotasks (<anonymous>)
umami    |     at processTicksAndRejections (internal/process/task_queues.js:97:5) {
umami    |   code: 'P2009',
umami    |   clientVersion: '2.10.1',
umami    |   meta: {
umami    |     query_validation_error: 'Unable to match input value to any allowed input type for the field. Parse errors: [Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at.DateTimeNullableFilter.gte`: A value is required but not set., Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at`: Value types mismatch. Have: Object({"gte": Null}), want: DateTime, Query parsing/validation error at `Query.findManypageview.where.pageviewWhereInput.created_at`: Value types mismatch. Have: Object({"gte": Null}), want: Null]',
umami    |     query_position: 'Query.findManypageview.where.pageviewWhereInput.created_at'
umami    |   }
umami    | }
...
(Error repeat)

When I visit https://cdn-domain:443 on dashboard page, use "F12 - Network" can see two errors:
https://paste.ubuntu.com/p/zcdfrdnJ2B/
https://paste.ubuntu.com/p/Rj8WZbfRgr/
But when I use http://vps-ip:3000 or https://vps-domain:443 to visit umami, website page or "F12 network page" or logs are well,  no error occurred.
Please pay attention to this issue if you have time, Thanks a lot~

Finally I found the reason...
I use 又拍云(UPYUN) as my CDN provider, there is a "Parameters Follow(参数跟随)" function in its control panel.
By default the function is "Parameters do not follow (参数不跟随)" , it mains the parameters after the "?" in the user request URL will be ignored. So I can't get the correct information by CDN.
When I set "Follow all the Parameters (参数跟随)", this problem is solved.
I'm sorry, it's my own reason...🥺🥺


Use max rather than min to sort managed Pythons

Summary
See: https://github.com/astral-sh/uv/issues/5139 and https://github.com/astral-sh/uv/pull/5201#discussion_r1683636935.
Test Plan
Verified that 3.12 was chosen above 3.8 in:

cargo run -- python uninstall --all
cargo run -- python install 3.8 3.12
cargo run -- tool run -v httpx

\cc @j178


NIGHT/EXPID/TILEID = 20241015/258118-19/23041 : SKYCHI2PDF alerts and weird sframe

this tileid=23041 got two exposures (258118-19) on 20241015.
the qa has lots of {R,Z}SKYCHI2PDF alerts:

we usually ignore those if the data look fine.
the redshifts look ok to me, but I notice that the sframe for 258118 looks quite different than the one from 258119, even though they have similar exptimes and efftimes:
 NIGHT   EXPID  TILEID EXPTIME EFFTIME_SPEC
-------- ------ ------ ------- ------------
20241015 258118  23041  1516.7        169.0
20241015 258119  23041  1264.4        176.5

so I have marked this tile as "unsure" for now, until I can get feedback from people after the weekend.
ps: the spacewatch movie does not show anything particular for 258118 (https://data.desi.lbl.gov/desi/users/raichoor/main-status/spacewatch/spacewatch-20241015.mp4).

I agree with Anand that 258118 looks much worse than 258119 for no discernible reason.  It doesn't seem to affect redshifts but we usually react to SKYCHI2PDF issues and it looks bad.  So I would mark 258118 on night 20241015, tileid 23041 as bad and reprocess without that data, but keep 258119 which looks to have much smaller SKYCHI2PDF.
The one other thing I would remark is that the sky was very bright then.
https://telemetry.desi.lbl.gov/d/4Ut9C-3Zz/etc-telemetry?orgId=2&from=1729040599428&to=1729084666782

It's interesting that the sky ranged from 30 to 20 during that exposure; presuming the moon separation changed slightly but it's hard to imagine that that's important enough.
Note that both of these have EFFTIME_SPEC ~ 180 s so this tile will still be complete even after removing 258118.

@akremin: Can we please mark exposure number 258118 on night 20241015, tileid 23041 as bad and reprocess?

258118 has been marked as bad and tileid 23041 has been rerun with just exposure 258119 on night 20241015. Tsnr and nightqa have been updated.

@forero: I set the QA for the tile mentioned here (23041) back to none. This tile will now reappear in regular tile QA again. Can you please mark this tile as good when you run QA tomorrow, if it looks good and if you beat me to it?
Once you've done that, you can close this issue, thanks!

Done!


Make statics const

With recent compiler versions we get warnings for this code where it suggests using addr_of! to avoid taking the intermediate reference to a static mut variable.
However, there's no clear reason why these even need to be mut. Embassy-boot doesn't use mut. So let's change it so people copying this don't get that same unhelpful warning.

Ok, so my changes don't work, but also this file appears to be full of UB...
So I'm gonna close this PR for now


Bad performance when using async variants compared sync variants

Describe the bug
I have a scenario where i have a simple table where i have a ID and a long text column. When retrieving a single row by id the performance using the async api's got really bad. THe sync api's seem to work as expected.
To reproduce
Included a sample project but basically having these two pieces of code to compare. The desription and screenshot is ran from exact the sample included.
The used database is the LocalDB that comes with Visual Studio 2022
AsyncPerformanceProblems.zip
{
    // Read Sync
    var stopwatchSync = Stopwatch.StartNew();
    var readTextSyncCommand = connection.CreateCommand();
    readTextSyncCommand.CommandText = @"SELECT LongText FROM Example";
    using var readerSync = readTextSyncCommand.ExecuteReader();
    while (readerSync.Read())
    {
        stopwatchSync.Stop();
        Console.WriteLine($"Length: {((string)readerSync[0]).Length}; Took: {stopwatchSync.Elapsed}");
    }
}

and
{
    // Read ASync
    var stopwatchASync = Stopwatch.StartNew();
    var readTextASyncCommand = connection.CreateCommand();
    readTextASyncCommand.CommandText = @"SELECT LongText FROM Example";
    using var readerASync = await readTextASyncCommand.ExecuteReaderAsync();
    while (await readerASync.ReadAsync())
    {
        stopwatchASync.Stop();
        Console.WriteLine($"Length: {((string)readerASync[0]).Length}; Took: {stopwatchASync.Elapsed}");
    }
}

Resulting in this where the 11 minute read is the async version

Expected behavior
Expecting the async and sync have a similar performance

Yup, see https://github.com/dotnet/SqlClient/issues/593

@davesmits this is a known issue. As @Wraith2 has mentioned. If you agree and feel like issues are coming from same source please close this issue and lets focus and follow on the open one #593 .


[Menu] When exit animation is running pointer events still fire

Bug report
Current Behavior
When using an exit animation with a menu the pointer events to move focus still fire. This can make it hard to focus on something other than the menu/trigger when clicking a menu item
Expected behavior
Once I click on a menu item the events should no longer fire to manage focus
Reproducible example
Notice how logs still happen while the menu is closing
https://codesandbox.io/s/cool-feather-p4mqz5?file=/App.js
Suggested solution
We have a pretty common pattern in our app where we open/focus on something other than the trigger when clicking a menu item. This could be a popover, modal, or really anything else. In our code right now we constantly have to battle the menu's focus management to make it work for these cases. Two things I would want:

Events to move focus don't fire as the menu is running an exit animation (I can make a PR for this)
A prop on the menu item to not return focus to the trigger. I know I can wire this up through existing props but it's clunky and I have to repeat the same pattern everywhere

This looks like something we may want to handle generally for all components that can "close" via unmount animation.
Presence might be the right candidate here.


Larastan unexpectedly discovers RayServiceProvider (spatie/laravel-ray) required by orchestra/testbench and breaks existing tests

Larastan Version: 2.5.1
--level used: 9

Description
The other day, the following test suddenly broke in a library I am developing.
class ExampleTest extends TestCase
{
    // Note that there are no RefreshDatabase trait

    public function testExample(): void
    {
        config(['database.connections.mysql.' . PDO::ATTR_EMULATE_PREPARES => true]);
        $this->assertTrue((bool)DB::getPdo()->getAttribute(PDO::ATTR_EMULATE_PREPARES)); // false!?!?
    }
}

Analysis of the problem revealed the following:

Simply running vendor/bin/phpunit succeeds
If vendor/bin/phpunit is executed after vendor/bin/phpstan, it fails

I suspected that Larastan was corrupting the cache, and upon investigation found that Larastan had rewritten the following file with unintended content:

vendor/orchestra/testbench-core/laravel/bootstrap/cache/packages.php
vendor/orchestra/testbench-core/laravel/bootstrap/cache/services.php

In packages.php, I found a dependency spatie/laravel-ray on orchestra/testbench is discovered and cached. As a side effect, unexpectedly, DB::connection() is eagerly resolved in all tests.
I believe #1404 is related to this issue, but still reproduces it. As a workaround, I have introduced the following cache clearing.

https://github.com/mpyw/laravel-pdo-emulation-control/commit/c95308db797f40ab29d03cfb69d0e509a3534706

This has been fixes in the latest spatie/laravel-ray


When you mutate router.getCurrentQuery() it changes the internal state

I am working on a pagination component which works even without javascript.
I have code like this to create a href for a link on the page:
hrefForPage(page) {
    const router = this.props.router;
    const path = router.getCurrentPathname();
    const params = router.getCurrentParams();
    const query = router.getCurrentQuery();
    query.page = page;
    return router.makeHref(path, params, query);
  }

In my onclick handler I have code like this:
  handleClick(e, page) {
    e.preventDefault();
    const router = this.props.router;
    const path = router.getCurrentPathname();
    const params = router.getCurrentParams();
    const query = router.getCurrentQuery();
    if (query.page !== page) {
      query.page = page;
      router.transitionTo(path, params, query);
      searchForQuery(query);
    }
  }

But because I set page in the hrefForPage method I have changed the interal state of react-router. In my case this causes me not to be able to go to the last page since getCurrentQuery tells we are already on the last page.

1.0 (beta is on master) no longer has this method, you get new objects as props to your route components.


Web sockets(Backend)

Changes done to backend to make frontend real-time compliant.

@Shelly011s pls try to solve the conflit

@Ammoniya Done :+1:


Fix references page

[ ] Closes #xxxx (Replace xxxx with the GitHub issue number)
[ ] Tests added and passed if fixing a bug or adding a new feature
[ ] All code checks passed.
[ ] Added type annotations to new arguments/methods/functions.
[ ] Added an entry in the latest docs/release_notes/index.md file if fixing a bug or adding a new feature.
[ ] If the changes are patches for a version, I have added the on-merge: backport to x.x.x label.

Based on https://github.com/scverse/cookiecutter-scverse/pull/205

meeseeksdev backport to 1.0.x


i18n(pt-BR): create recipes/streaming-improve-page-performance.mdx

Description (required)
create i18n/pt-br/recipes/streaming-improve-page-performance.mdx

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

pt-br
recipes/streaming-improve-page-performance.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.