404 error when using useFileSystemPublicRoutes = false

When useFileSystemPublicRoutes is set to false and there is no custom route for path, but page-based route exists, nextjs will render that page on client instead of 404.
Steps to reproduce:

Take custom-server  example
Replace const app = next({ dev }) in server.js with
const app = next({ dev, conf: {  useFileSystemPublicRoutes: false } })
There's now no route for /
Start the server, hit localhost:3000
Server serves 404 (it flashes for a moment), then client takes over and re-renders /pages/index.js component. Browser console contains Warning: React attempted to reuse markup

So with this option behavior on server and client is not consistent, and it doesn't look like it should work this way.

I've also run into this issue.
This useFileSystemPublicRoutes: false seems to be useless — it stops the server from setting up matching routes for the file names, but the next client still attempts to use a PageLoader to pull in the chunk for the file-named pathname at runtime.
So when a request comes in for a named page e.g. pages/foo.js:

Server correctly 404s
_error component is correctly rendered
Next client attempts to fetch the chunk for /foo (this shouldn't happen)
Client-side re-renders, causing chaos

What should probably happen is that when _error is rendered, it should have the same behaviour as if pages/foo.js doesn't exist.
This is tough though, as you will probably still want to load the foo.js chunk on another—valid—page.
One solution is that a flag is passed down to the error page, so it doesn't attempt to load a named chunk (foo.js in our case), but just the error chunk.
This will solve the flash-404, but this won't work for client-side routing (where the client wouldn't start from an error page).
But this would be fine as long as you don't make a bad link.
I'll give it a go and open a PR.

Any updates on this? I'm using a custom server to redirect /:username to ./pages/user.js,  but like what @GennadyPonomarev has described, it didn't work as expected.

Hmm seems I did it wrong, this could fix my issue:
server.get('/:username', (req, res) => {
    return app.render(req, res, '/user', {
      username: req.params.username
    })
  })

My app:
<Link href="/user?username=egoist" as="/egoist">
  egoist
</Link>

I just ran into this as well, playing with one of the examples (ssr caching) to make it use koa.
In the example, /blog should be invalid, and /blog/first should work.
useFileSystemPublicRoutes = false

is ignored by the client-side code.
I worked around the problem by renaming pages/blog.js to pages/blog2.js and fixing my code a bit, just to hide /blog a little better. So now at least /blog is a proper Next 404, but /blog2 is still available and it's a mix of my blog2.js content and formatted as a Next error page.

I've got a small example at https://ssr-caching-koa-amateehwho.now.sh/ (and source).
useFileSystemPublicRoutes is set false in next.config.js.
First, the actual problem can be seen at https://ssr-caching-koa-amateehwho.now.sh/blog2. Note that there is a /pages/blog2.js file.
A correct 404 is https://ssr-caching-koa-amateehwho.now.sh/blog. We have no /pages/blog.js file.
Actual posts are at https://ssr-caching-koa-amateehwho.now.sh/blog/first for example but I'm making use of a custom server to handle routing and map /blog/:id to the /pages/blog2.js file (passing the id parameter).

I'm currently still experiencing this in 5.0.0.
@timneutkens I see you've added the label: good first issue. Do you have any pointers on where to look for this?
I'll try to submit a PR to fix this.

@thomhos it's actually not easy to fix, removed the label 👍, I'd have to investigate it further to come up with a solution.

Ah, I just submitted a PR which seems to fix the problem for me locally. I guess we should close that as well?

I encountered the same problem in 5.0.0

Any updates? This is a very annoying issue.

My two cents on this (since I asked for useFileSystemPublicRoutes in the first place):

If you're using useFileSystemPublicRoutes: false and a custom router, (perhaps/IMO) it's up to you to guard against client-side navigation to 404'd pages. We do that by maintaining a routes file, and only ever generating links from those routes (we use route-parser). We also wrap Link so that anything passed to our wrapped Link goes through the routes file to find a match, and behaves as we expect if it doesn't find one (throw an error, in our case).

const Route = require('route-parser');

const routes = {
  exampleRoute: {
    route: new Route('/user/facing/route(/)'),
    template: 'file-system-route',
  },
};

module.exports = routes;

import React from 'react';
import { find } from 'lodash';
import Link from 'next/link';

import routes from '../../routes';

export default ({ href, children, passHref }) => {
  const matchingRoute = find(routes, definition => definition.route.match(href));

  if (matchingRoute) {
    return (
      <Link as={href} href={`/${matchingRoute.template}`} passHref={passHref}>
        {children}
      </Link>
    );
  }

  // Attempted to Link to a non-existant route, throw.
  throw new Error('Link: Bad route.');
};

I don't think this is super-unreasonable since you're using Next in a customized way; our company has had very few problems with that approach.

I think a bigger issue is around popstate; Router uses it directly to kick off navigation in the history, so you could a) go to a 404'd page on the server that corresponds to a filesystem route, b) click on a link on the 404 page to client-side navigate to a real page, and c) click "back" on the browser UI to see that page even though it should be 404ing.

One way to skirt this is to disable client-side navigation on your error pages, however is sensible in your situation, since if you're guarding against bad routes error pages should be the only way to enter a bad route into history.
Alternatively, we could add configuration to allow end-users to inject some functionality at the start of Router's onPopState() handler, which would allow you to test for an invalid destination before allowing Router to process the request.
The latter would be nice since it'd allow for a guarantee that the Router can't behave in ways that your custom routing doesn't like, but the former is something you could today do w/o a patch to the core library.

The issue of the development build refreshing a 404 / rendering the filesystem route is probably separate issue to think through... I've manually disabled a lot of the development mode stuff since it was handier for us to be able to have the same error pages on dev and prod. 🤔

@gcpantazis The problem is that you can have something like
.
└── pages
    └── dashboard
    │   └── index.js
    └── landing
        └── index.js

And then have some custom routing like:
router.get('/', (req, res) => {
  if (!req.isAuthenticated()) {
      return next.render(req, res, '/dashboard', req.query);
  }
  next.render(req, res, '/landing', req.query);
});

So that logged-out users see a landing view, and logged-in users see a dashboard.
This works fine when hitting / as expected.
But if any user goes to /dashboard or /landing they will see these views (though it will likely throw some errors along the way). The expected behavior is that by setting useFileSystemPublicRoutes: false the routes must be defined manually, but they are still accessible via the browser.

For what it's worth, it looks like the case mentioned by most of the reporters here (i.e., server renders a 404s then flashes to an unexpected client-rendered page) was fixed incidentally as of 5.0.1-canary.5 (and specifically by #3749).
There's a few other cases that we could consider:
Explicit navigation:

Create a Link that corresponds to a file-system route, even though you disabled it via useFileSystemPublicRoutes.
Click on that Link.
See the page, even though useFileSystemPublicRoutes: false implies you shouldn't.

popstate:

Go to a URL that corresponds to a file-system route, even though you disabled it via useFileSystemPublicRoutes. Get a 404 from SSR.
Click on a link that takes you something else via client-side navigation.
Hit "back" on the browser.
You'll see the file-system route render instead of a 404.

Of the two, I'd say the first is maybe not a huge concern, since as you've opted to replace Next's default routing you should be responsible for client-side navigation to bad URLs. The second I think is a bigger issue (and perhaps can be a separate issue, since as far as I can tell most of the reporters' problems will be resolved in 5.0.1).

@thomhos made a PR for it: https://github.com/zeit/next.js/pull/3777

Rebased and tried that patch, @timneutkens. Unfortunately I think #3777 only fixes the issue described here because it breaks client-side altogether (removes the route to the bundles, i.e. ['/_next/:buildId/page/:path*.js'] if useFileSystemPublicRoutes: false).
I think I have an alternate solution; I'll put it together when I get to the office.

Hi guys, I realize now as well that #3777 was a very naive approach to the problem, I was hoping to kickstart it a bit and come to a solution together :)
Let me know if you need any help, I haven't looked into this for a while.

@timneutkens ping on ☝ before it gets stale! 🙇

The case mentioned in the issue topic is actually solved in next@canary. Thanks new 404 logic.

Creating a new issue for @gcpantazis's comments on other cases.

#4008


Add ability to disable admin API

We should have a conditional on the Admin API controllers such that if something like ilpv4.connector.admin_api is not set to true, then the Admin API is not enabled.

Make sure to disable whatever auth protects this endpoint when admin api is disabled. See SecurityConfiguration.configure


Refactor the event queue

Current dependencies on/for this PR:

main

PR #188   👈

This comment was auto-generated by Graphite.


Fix corner case with Apache HTTP client v4 + RestEasy.

Fix Apache Http Client interception bug when creating an anonymous class of SSLConnectionSocketFactory. When creating an anonymous class getDeclaredField will not return the needed socketFactory attribute. This is the behavior of RestEasy for some cases, see https://github.com/resteasy/Resteasy/blob/main/resteasy-client/src/main/java/org/jboss/resteasy/client/jaxrs/engines/ClientHttpEngineBuilder43.java#L128
Fix https://github.com/httptoolkit/jvm-http-proxy-agent/issues/2

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.David Vieira seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Proof-of-stake instead Proof-of-work

Stratum detect verge daemon as POS not POW,
also errors in debug.log
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED
received block<PHONE_NUMBER>53b30898ca
Postponing 521 reconnects
REORGANIZE
REORGANIZE: Disconnect 367 blocks; 000000028f337f664cb5..00000000005943dc690d
REORGANIZE: Connect 6483 blocks; 000000028f337f664cb5..0000000003cee7f69cfc
ERROR: ConnectBlock() : UpdateTxIndex failed
ERROR: Reorganize() : ConnectBlock 00000003db4d9f497ae6 failed
InvalidChainFound: invalid block=000000034453b30898ca  height=291044  trust=97919604092  date=03/21/16 04:49:39
InvalidChainFound:  current best=00000000005943dc690d  height=284407  trust=97135061726  date=03/21/16 16:02:13
ERROR: SetBestChain() : Reorganize failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

@digegold not sure why your stratum detected it as PoS, as the pools that we have currently arent having that issue. we are aware that there is a large reorg happening. this is happening to alot of scrypt coins right now. we have a large hashpower hitting our network and forking, then reorg. a new multi algo release will be available soon that should help us.

yeah that is a reorg, but it failed.. we're switching to multi algo soon, shouldnt see any reorgs after that. not sure why your stratum is detecting it as PoS, maybe because nTime?

this is from debug.log:
ThreadRPCServer started
ThreadMessageHandler started
ThreadStakeMinter started
CPUMiner started for proof-of-stake
ThreadOpenConnections started
ThreadOpenAddedConnections started

right, its disabled though, there is no stake reward. just nTime. what pool?

It is my local UNOMP pool with 13 coins, all detected as POW accept VERGE
Pool verge Thread 1 started for verge [XVG] {scrypt}
Network Connected:      Mainnet
Detected Reward Type:   POS
Current Block Height:   292852
Current Connect Peers:  12
Current Block Diff:     607229003.6380467
Network Difficulty:<PHONE_NUMBER>.618263
Network Hash Rate:      481.45 GH
Stratum Port(s):        3018, 3048, 3268
Pool Fee Percent:       0%
Block polling every:    1000 ms
This output from getmininginfo:
"blocks" : 292851,
"currentblocksize" : 8373,
"currentblocktx" : 11,
"difficulty" : 15442.62102689,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" :<PHONE_NUMBER>43,
"pooledtx" : 11,
"testnet" : false
This output from getinfo:
"version" : "v<IP_ADDRESS>-beta",
"protocolversion" : 60017,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 292851,
"timeoffset" : 53,
"moneysupply" :<PHONE_NUMBER>9.99999619,
"connections" : 12,
"proxy" : "",
"ip" : "X.X.X.X",
"difficulty" : 15442.62102689,
"testnet" : false,
"keypoololdest" :<PHONE_NUMBER>,
"keypoolsize" : 102,
"paytxfee" : 0.10000000,
"errors" : ""

right, i just said theres nTime, but no stake reward. are you not able to mine it?

No, stratum detect it as POS:
Detected Reward Type: POS
and verge daemon will reject solved blocks.
All other coins works fine

try putting gen=0 and reservebalance=0 and staking=0 in the .conf?

you have other pos/pow coins working on your pool?

Only POW, 12 other coins, all work fine

After change .conf still detect as POS. Look like blockchain stuck on block 284542

Sorry block=292,852

this is latest output from debug.log:
getblocks 287022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00030320b39c9e58
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 284022 to<PHONE_NUMBER>3cd4d68adb limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 286022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00067e1f004ce73e
getblocks 284022 to<PHONE_NUMBER>24b84fe40b limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 286522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00000254465c9bba
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 284022 to<PHONE_NUMBER>24b84fe40b limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 286022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00067e1f004ce73e
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 286022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00067e1f004ce73e
getblocks 286522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00000254465c9bba
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 286522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00000254465c9bba
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 287022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00030320b39c9e58
getblocks 284022 to<PHONE_NUMBER>24b84fe40b limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 286022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00067e1f004ce73e
getblocks 286022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00067e1f004ce73e
getblocks 284022 to<PHONE_NUMBER>3cd4d68adb limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 286522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00000254465c9bba
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 286522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00000254465c9bba
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 284022 to<PHONE_NUMBER>24b84fe40b limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
getblocks 284522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00026316a6d291c7
getblocks 284022 to<PHONE_NUMBER>24b84fe40b limit 500
getblocks stopping at limit<PHONE_NUMBER>00002aab9095b2ac
getblocks 285522 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>00044a074f688e5a
getblocks 285022 to<PHONE_NUMBER>0000000000 limit 500
getblocks stopping at limit<PHONE_NUMBER>0002eb42f13705af
^C

yes the chain is stuck on 292853 right now. we are switching to multi algo in a week. not sure why you cant set it up, we are on about 10 different pools right now. and i set it up on a unomp pool as well. do you have the getblocktemplate rpc stuff set up correctly?

I'm not sure what are you mean by "getblocktemplate rpc stuff"
This is the RPC calls from stratum:
ThreadRPCServer method=getinfo
ThreadRPCServer method=validateaddress
ThreadRPCServer method=getdifficulty
ThreadRPCServer method=getinfo
ThreadRPCServer method=getmininginfo
ThreadRPCServer method=submitblock

Here is error from daemon:
ThreadRPCServer method=submitblock
ERROR: CTransaction::CheckTransaction() : txout.nValue below minimum
ERROR: CheckBlock() : CheckTransaction failed
ERROR: ProcessBlock() : CheckBlock FAILED

oh, you'll have to code unomp to allow batch rpc requests, or use different pool software. unomp isnt compatible with ppc clones by default. you just need to write code to detect when a coin is missing batch rpc and implement a batch rpc shim into daemon.js


Social Media Icons | Improvement

Greeetings!
When we hover over the social media logos on the website, the color changes to #f53f2b.
However, according to branding guidelines changing the color of these logos is not permitted.
References:

GitHub Branding Guidelines - Changing the colors is not permitted
Twitter Branding Guidelines - Logo can only be used in either blue or white color and for black too permission is required from their team
LinkedIn Branding Guidelines - Changing the colors is not permitted

Suggested Improvements:

We can either add colored logos for all the aforementioned logos or upon hovering them change them to their original colors. However, the latter option does not fall in accordance with the Twitter Branding Guidelines.
We could use a mail icon / Gmail logo in place of the @ logo, it confused me too at first when I thought of what the icon is for.

Do suggest any changes or further improvements.
It'll be super if I could be assigned this issue.
Thanks and regards,
Pooja Gera

i can do that assign me this task

Hello @osamakhan552 I am not the maintainer of this project, I was hoping to work on this and opened the issue for the maintainer's due consideration.

Hi, i have made some new change for the brand logo. I follow their brand guidelines. Maybe you can check my pull request. Thank you!

assigined

hey can you assign this issue to me.

If issue is still there..Please assign to me. I will try my best.

Kindly assign me for this sir!


Upgrading Elasticsearch Application When Using Service Fabric Azure Files Volume Driver Causes An Elasticsearch Node To Die

I have an Elasticsearch applcation with 3 nodes on Azure (Each elastic node is in a Service Fabric Service). I installed Service Fabric Azure Files Volume Driver on the cluster. I am able to successfully deploy the Elasticsearch application. However, when I redeploy the application, without making any changes, one of the services is in an error state. It also fails to restart.
I don't think that this is a problem with Elasticsearch becuase the output of the Elasticsearch
logs do not indicate so. From the logs, it looks like all 3 elastic nodes are upgraded successfully.
However, as soon as the 3rd node completes upgrading, the first node just stops.
 It seems that either Service Fabric or the Volume Driver is sending the kill signal.
Furthermore, I'm not able to restart the service. I able to restart any of the other two elastic nodes. I would imagine that if an application fails, I can just simply have Service Fabric restart it. This makes me think that Service Fabric is not causing this issue.
Lastly, when I remove the volume plugin from the services, I can successfully deploy and redeploy.
I can only conclude that there is a bug with Service Fabric Azure Files Volume Driver.

Hi duncan-G,
did you solve the problem? Do you know if it is possible to run applications with high memory consumption in Service Fabric (~20 GB)
Regards,
Chris

The problem that I was having was that docker was in a bad state in one of
our Service Fabric nodes. For some reason docker volumes were not deleted
when stopping or restarting the elasticsearch application. Because of this,
the volume driver was then unable to communicate with azure storage and
this would kill the elasticsearch service because the service couldn't
access it's state. Everything started working again after manually deleting
all the extraneous docker volumes.
As for high memory consumption applications, I do not know if it's
possible. However, Microsoft uses service fabric and so I imagine it's
possible.
On Mon, Apr 27, 2020 at 11:35 PM christopher-ux<EMAIL_ADDRESS>wrote:

Hi duncan-G,
did you solve the problem? Do you know if it is possible to run
applications with high memory consumption in Service Fabric (~20 GB)
Regards,
Chris
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/service-fabric/issues/417#issuecomment-620410207,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHKIX7ZHUMMAF3ECYLZRQ3TROZ2MPANCNFSM4JOCSTHQ
.

--
Duncan Gichimu


ROCm 3.3.0 breaks support for Navi in kernel mode.

Hello,
I am fully aware that Navi ASICs aren't supported officially on ROCm but I was using 3.1.1 and it was working just fine in kernel mode while using 19.30/19.50 OpenCL drivers from amdgpu-pro.
With latest 3.3.0 that support has broken.
[13805.914117] failed send message:     RunBtc (58)     param: 0x00000000 response 0xffffffc2
[13805.914119] RunBtc failed!
[13805.914186] [drm:amdgpu_device_init [amdgpu]] *ERROR* hw_init of IP block <smu> failed -62
[13805.914188] amdgpu 0000:07:00.0: amdgpu_device_ip_init failed
[13805.914190] amdgpu 0000:07:00.0: Fatal error during GPU init
[13805.914192] [drm] amdgpu: finishing device.
[13805.922829] [drm] psp command (0x2) failed and response status is (0x117)

Using any firmware blobs does not fix the problem, it still fails here in hw_init of smu block.

Update:
Applying this fixed the problem.
https://www.spinics.net/lists/amd-gfx/msg45307.html
Still smu is resetting several times and I get this message:
[   12.460543] [drm] psp command (0x2) failed and response status is (0x117)
[   17.225730] [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
[   17.225749] [drm] PSP is resuming...
[   17.396400] [drm] reserve 0xd00000 from 0x81fe000000 for PSP TMR
[   17.465573] amdgpu 0000:07:00.0: RAS: ras ta ucode is not available
[   17.471453] SMU is resuming...
[   17.473421] SMU is resumed successfully!
[   17.474048] [drm] kiq ring mec 2 pipe 1 q 0
[   17.480699] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[   17.481092] [drm] JPEG decode initialized successfully.
[   17.481120] amdgpu 0000:07:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[   17.481124] amdgpu 0000:07:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[   17.481127] amdgpu 0000:07:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[   17.481130] amdgpu 0000:07:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[   17.481132] amdgpu 0000:07:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[   17.481135] amdgpu 0000:07:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[   17.481137] amdgpu 0000:07:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[   17.481140] amdgpu 0000:07:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[   17.481143] amdgpu 0000:07:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[   17.481145] amdgpu 0000:07:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[   17.481148] amdgpu 0000:07:00.0: ring sdma0 uses VM inv eng 12 on hub 0
[   17.481151] amdgpu 0000:07:00.0: ring sdma1 uses VM inv eng 13 on hub 0
[   17.481153] amdgpu 0000:07:00.0: ring vcn_dec uses VM inv eng 0 on hub 1
[   17.481156] amdgpu 0000:07:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 1
[   17.481159] amdgpu 0000:07:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 1
[   17.481161] amdgpu 0000:07:00.0: ring jpeg_dec uses VM inv eng 5 on hub 1
[   17.671292] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
[   17.766702] [drm] UVD and UVD ENC initialized successfully.
[   17.912687] [drm] VCE initialized successfully.
[   31.205389] random: crng init done
[   31.205391] random: 7 urandom warning(s) missed due to ratelimiting
[   66.459800] input: PC Speaker as /devices/platform/pcspkr/input/input3
[   80.191405] [drm] psp command (0x2) failed and response status is (0x117)
[   83.214502] [drm] PCIE GART of 512M enabled (table at 0x0000008000000000).
[   83.214515] [drm] PSP is resuming...
[   83.384254] [drm] reserve 0xd00000 from 0x81fe000000 for PSP TMR
[   83.453236] amdgpu 0000:07:00.0: RAS: ras ta ucode is not available
[   83.459117] SMU is resuming...
[   83.461229] SMU is resumed successfully!
[   83.461854] [drm] kiq ring mec 2 pipe 1 q 0
[   83.468173] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[   83.468323] [drm] JPEG decode initialized successfully.
[   83.468352] amdgpu 0000:07:00.0: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[   83.468356] amdgpu 0000:07:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[   83.468358] amdgpu 0000:07:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[   83.468361] amdgpu 0000:07:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[   83.468363] amdgpu 0000:07:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[   83.468366] amdgpu 0000:07:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[   83.468369] amdgpu 0000:07:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[   83.468371] amdgpu 0000:07:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[   83.468374] amdgpu 0000:07:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[   83.468377] amdgpu 0000:07:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[   83.468379] amdgpu 0000:07:00.0: ring sdma0 uses VM inv eng 12 on hub 0
[   83.468382] amdgpu 0000:07:00.0: ring sdma1 uses VM inv eng 13 on hub 0
[   83.468385] amdgpu 0000:07:00.0: ring vcn_dec uses VM inv eng 0 on hub 1
[   83.468387] amdgpu 0000:07:00.0: ring vcn_enc0 uses VM inv eng 1 on hub 1
[   83.468390] amdgpu 0000:07:00.0: ring vcn_enc1 uses VM inv eng 4 on hub 1
[   83.468392] amdgpu 0000:07:00.0: ring jpeg_dec uses VM inv eng 5 on hub 1

But it works as expected.

I am sorry for the off-topic. Is there a possibility that using ROCm with OpenCL drivers from amdgpu-pro could help running ROCm on Hawaii (see #1006 )?

This is different. You can sure use rocm kernel driver with amdgpu-pro opencl but reverse is not possible(tested it long time ago and it worked for one vega only). But why mixing while amdgpu-pro provides decent hawaii support? Hawaii problem is not in kernel driver AFAIK.

OK, now I see. Thanks!

@vvsteg did you manage to get your gfx701 to work with amd-gpupro drivers?

@forgetso No, I did not. Recently, I have read  some information about the relevant technical problems https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/open-source-amd-linux/1184064-radeon-rocm-3-5-released-with-new-features-but-still-no-navi-support?p=1184303#post1184303

Thanks @ddobreff and all for reaching out via this defect/issue.
We can not comment on Navi/hawaii as we do not support them.
Thank you.


A stemmer for Ukrainian

Hello.
Is it possible to add a stemmer for the Ukrainian language?
UPD: I've found this: https://github.com/Tapkomet/UAStemming

This is a thin wrapper around snowball stemmer which IMO does support  Ukrainian. If a new version comes up with support, I'll gladly update this packge.

If so it would be great :)

Unfortunately, I don't see any progress on this issue.
BTW, https://github.com/snowballstem/snowball/issues/130

The above issue in snowball is still open. Once they implement Ukrainian I'll gladly update the package.

Done in v0.6.0 (updated snowball to 2.2.0)


feat(connector): [Fiserv] Currency Unit Conversion

Type of Change

[ ] Bugfix
[x] New feature
[ ] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description

Addressing Issue: #2225
Modified two files in hyperswitch/crates/router/src/connector/

fiserv.rs

Implement get_currency_unit function
Modify ConnectorIntegration implementations for Fiserv

fiserv/transformers.rs

Implement FiservRouterData<T> structure and functionality
Modify implementation for FiservPaymentsRequest and FiservRefundRequest

Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

We need to create a payment using Fiserv and test the currency unit from connector response and connector dashboard.
Checklist

[x] I formatted the code cargo +nightly fmt --all
[ ] I addressed lints thrown by cargo clippy
[ ] I reviewed the submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

LGTM!

Hey @SagarDevAchar  ,
Thanks a bunch for all your contributions! We've got a little something for you to show our appreciation.
Just take a moment to fill out this form, and get ready for some awesome swag coming your way.
Thanks!


Set the expiry time in JWT (exp) in seconds

Description:

Set the expiry time in JWT (exp) in seconds
Handle the scenarios where validity period it not specified and specified as -1 (non-expiring token)

Fix : https://github.com/wso2/carbon-apimgt/pull/5534


Updating field 'Specimen ID' to 'Test ID'

Related Issue or Background Info

#3482

Changes Proposed

Changing a field name on the test results.

Screenshots /

Demos
Checklist for Author and Reviewer
Infrastructure

[x] Consult the results of the terraform-plan job inside the "Terraform Checks" workflow run for this PR. Confirm that there are no unexpected changes!

Design

[x] Any UI/UX changes have a designer as a reviewer, and changes have been approved
[x] Any large-scale changes have been deployed to test, dev, or pentest and smoke-tested by both the engineering and design teams

Content

[x] Any content changes (including new error messages) have been approved by content team

Support

[x] Any changes that might generate new support requests have been flagged to the support team
[x] Any changes to support infrastructure have been demo'd to support team

Testing

[x] Includes a summary of what a code reviewer should verify

Changes are Backwards Compatible

[x] Database changes are submitted as a separate PR

[x] Any new tables that do not contain PII are accompanied by a GRANT SELECT to the no-PHI user
[x] Any changes to tables that have custom no-PHI views are accompanied by changes to those views
(including re-granting permission to the no-PHI user if need be)
[x] Liquibase rollback has been tested locally using ./gradlew liquibaseRollbackSQL or liquibaseRollback
[x] Each new changeset has a corresponding tag

[x] GraphQL schema changes are backward compatible with older version of the front-end

Security

[x] Changes with security implications have been approved by a security engineer (changes to  authentication, encryption, handling of PII, etc.)
[x] Any dependencies introduced have been vetted and discussed

Cloud

[x] DevOps team has been notified if PR requires ops support
[x] If there are changes that cannot be tested locally, this has been deployed to our Azure test, dev, or pentest environment for verification

I’d like the Spanish version to be given the same spacing treatment as the English version, but this one is good to go for now

Hey @vz3 the reason the Spanish version does that is to fit everything on one page, just like the English version. I see more empty space on the right in the Test Details section, we can increase the label max width even more to accommodate for longer Spanish titles.

Bumping the max-width to 20 fits the id + name on a single line, but for positive tests the pdf still runs over into a second page


Tweak the relayMessage Function to Cost Roughly the Same for All Scenarios

Previously, the relayMessage function still left in the ability to relay directly from a block. Because this results in certain message emitting fuel blocks to be cheaper to relay from, it could incentivize a mad rush situation on particular blocks on the Fuel side, which would cause bad user experience. The function should remove this rare although meaningfully cheaper option.

Resolved by #33


Filter Illegal Header Fields

According to the OpenApi Spcec there are certain header parameters, that are not allowed as part of the regular parameters specification in the Swagger Spec.  These Headers (Accept, Content-Type and Authorization) are described using other OpenApi fields.
The FastEndpoints Swagger generation should respect/filter that, when processing properties marked with FromHeader.

it doesn't seem to be enforced for even minimal apis. just tried the following:
app.MapGet("/test", ([FromHeader] string accept) => Results.Ok(accept));

nswag generated a header parameter without any complains.
i pasted the generated swagger.json into https://editor.swagger.io/
no complains there either.
so i'm not sure if FE needs to worry about it if nobody else pays any attention to it...
swagger ui seems to just ignore any values entered in to these input boxes anyway.

Well I was going to create an Issues there too, just started here, because you generally try to make things better than the others :-)
And it would be pretty easy to implement in OperationProcessor.Process, shouldn't it?
Some people/projects are pretty picky, when it comes to the formal correctness of specs. So I currently had to remove the headers in question from the typed Request object and access them by Context.Request instead...

yeah i'll guess we should do it.
i'll add it when i get a chance...
if you'd like to do a PR, that would be fine too...

@drothmaler This has been implemented in v<IP_ADDRESS>-beta


Submission 20220919-cotmae

@msmarco-bot

@msmarco-bot - Hi, I just submitted a new commit that holds 1000 hits per query. Would you please consider reevaluating our submission? Thanks so much.

@msmarco-bot - Hi, sorry to bother you again. It seems that the URLs for the paper & code of COT-MAE were redirected to the wrong site (https://microsoft.github.io/MSMARCO-Passage-Ranking-Submissions/leaderboard/github.com/caskcsg/CoT-MAE)

Hi, sorry to bother you again. The URLs for COT-MAE were redirected to the wrong sites by an unexpected URL prefix (https://microsoft.github.io/MSMARCO-Passage-Ranking-Submissions/leaderboard/). It seems that this prefix was added by your system, and we don't have it in our submission. Could you please fix them by removing the URL prefixes? Thanks again. (Change 'https://microsoft.github.io/MSMARCO-Passage-Ranking-Submissions/leaderboard/arxiv.org/abs/2208.07670' to 'arxiv.org/abs/2208.07670'; 'https://microsoft.github.io/MSMARCO-Passage-Ranking-Submissions/leaderboard/github.com/caskcsg/CoT-MAE' to 'github.com/caskcsg/CoT-MAE')

@msmarco-bot - Sorry to bother you again. I didn't reserve my encryption key file ''20220919-cotmae.key.bin". Could you please send this file to my email? My email is<EMAIL_ADDRESS>thank you very much!


Write the extension to use those hooks

Fahad Zaheer

hey I'm Urooj Fatima. Excited for this project

Hello, Its Syed Umer Tariq !!

Hi, I am the new Operations Manager Steve from Vancouver Team.

Hi! It's Rafsun.

Hi! I'm Abdul Manan. I'm excited to work on this project!

Hi! I am Abdullah. Excited for this project !!

Hi! I am Waleed, excited to work on this project

Hi I am Talha and I am excited to start working on this project

Hi,
Jawad Ali here
Excited

First identify the hooks offered by the application. The hooks can be methods or functions.
Write your own code that will be executed in these functions or methods. The code should be designed to modify the behavior of the application.
Register your extension with the application so that it is notified when we call those methods.
Provide documentation or examples of how your extension can be used to modify the behavior of the application.

Here is a general overview of how an extension that uses hooks might work:
-Identify the point in the system where the extension needs to modify behavior. This could be an input or output point, an action, or a decision.
-Determine if a hook is available at that point. If so, review the documentation to understand how to use the hook and what input/output parameters are required.
-Write the extension code to use the hook. This could involve writing a new function or modifying an existing one to incorporate the hook.
-Test the extension to ensure that it works as expected. This could involve testing with various input/output scenarios or testing the extension with the system in different configurations.
-Provide documentation for the extension so that other developers know how to use it.
-Share the extension with others who may benefit from it. This could involve publishing it to a repository or marketplace or sharing it directly with other developers.

We will begin by identifying the available hooks in the MariaDB application, which can be in the form of functions or methods. Next, we will write our own code that will be executed within these hooks to modify the behavior of the application as desired. After writing the code, we will need to register our extension with the application to ensure that it is notified when the relevant methods or functions are called.

In order to get started with the extension for using the hooks we need to look for points where there is need of hooks and after identifying those points we will create hooks which will be user-defined functions to perform required actions at those points. Lastly, we need to verify the results of our hooks whether it's producing the desired results after which we need to integrate those hooks in our extension after which there will be a need for documentation of all the functionalities in the extension and ultimately the extension will be made public by publishing it to some repository and share with extension marketplace.

To write an extension to use hooks in MariaDB, you will need to have a good understanding of the MariaDB architecture and how the various hooks work.
So, I am sharing a link with you from which you can learn MariaDB architecture.
Architecture Readme


clean up links and add link verification

There's a link verification failure here: https://dev.azure.com/azure-sdk/public/_build/results?buildId=485450&view=logs&jobId=a129effc-2dd1-54d1-fb5a-ad7bdc0e851d&j=a129effc-2dd1-54d1-fb5a-ad7bdc0e851d&t=ccad100f-2904-5913-2083-c525ad929a03
Looks like something is urlencoding the ampersands separating query parameters in the URL to &:
?utm_source=badge&utm_medium=badge&...

To:
?utm_source=badge&utm_medium=badge&

@danieljurek Actually the link to the gitter channel is broken since we don't have a gitter channel with that name yet https://gitter.im/azure/azure-sdk-for-cpp

@RickWinter -- Probably makes sense to set up a gitter for the repo or remove the link


oneDAL Extratrees Classifier and Regressor Integration

Description
This introduces the scikit-learn-intelex ExtraTreesRegressor and ExtraTreesClassifier objects which can patch similarly named scikit-learn ensemble methods.
Changes proposed in this pull request:

ExtraTreesRegressor
ExtraTreesClassifier

This is good workaround or first iteration of ExtraTrees implementation. On these branch we can test ExtraTrees implementation.
But further it is better to have common ForestClassifier on preview.ensemble, and inherited Extratrees from there

@icfaust Previously we were discussed on restructuring preview.ensemble code and have ExtraTrees support in sklearnex:

move most of the logic from preview RandomForestClassifier to ForestClassifier (RandomForestRegressor to ForestRegressor)
inherited for:
RandomForestClassifier <- ForestClassifier
ExtraTreesClassifier <- ForestClassifier
RandomForestRegressor<- ForestRegressor
ExtraTreesRegressor <- ForestRegressor
Since we are first time releasing ExtraTrees support on both CPU and GPU in sklearnex, let's have it on not  in preview section.
for onedal4py also moving codes to RandomForestClassifier to ForestClassifier (RandomForestRegressor to ForestRegressor) works fine

Currently I see just code duplication from RandomForestClassifier/Regressor for ExtraTrees
Could you please bring some updates?

The following was agreed upon in the architecture meeting:

A minimally-modified version of preview/ensemble will be used for ExtraTrees for 2023.2 This will not be in preview.
An investigation into onedal/ensemble/forest.py's depth first search performance will occur
A refactor of the ExtraTrees will occur for integration of oneDAL RF, therby taking it out of preview
A possible new versioning structure for older sklearn versions will be investigated and proposed, which may handle all legacy issues

Note that the status of GPU support was not discussed. How GPU algorithms are verified and tested is not something we've nailed down. I think it would be vital for you to have a discussion with @Alexsandruss @inteldimitrius @napetrov first.

/intelci: run

@samir-nasibli @KulikovNikita please review

/intelci: run

Sklearn test failures need fix:
FAILED ensemble/tests/test_forest.py::test_forest_classifier_oob[X1-y1-0.65-array-ExtraTreesClassifier]
FAILED ensemble/tests/test_forest.py::test_memory_layout[float64-ExtraTreesRegressor]
FAILED ensemble/tests/test_forest.py::test_memory_layout[float32-ExtraTreesRegressor]
FAILED tests/test_common.py::test_estimators[ExtraTreesClassifier()-check_no_attributes_set_in_init]
FAILED tests/test_common.py::test_estimators[ExtraTreesClassifier()-check_classifiers_train(readonly_memmap=True)]
FAILED tests/test_common.py::test_estimators[ExtraTreesClassifier()-check_classifiers_train(readonly_memmap=True,X_dtype=float32)]
FAILED tests/test_common.py::test_estimators[ExtraTreesClassifier()-check_requires_y_none]
FAILED tests/test_common.py::test_estimators[ExtraTreesRegressor()-check_no_attributes_set_in_init]
FAILED tests/test_common.py::test_estimators[ExtraTreesRegressor()-check_supervised_y_2d]
FAILED tests/test_common.py::test_estimators[ExtraTreesRegressor()-check_fit_idempotent]
FAILED tests/test_common.py::test_estimators[ExtraTreesRegressor()-check_requires_y_none]
FAILED tests/test_common.py::test_check_param_validation[ExtraTreesClassifier()]
FAILED tests/test_common.py::test_check_param_validation[ExtraTreesRegressor()]

/intelci: run

It seems as though test_memory_usage.py has a banned_list which includes the RF algorithms. As this is based on the same code, it will fail for the same reasons. Please see https://github.com/intel/scikit-learn-intelex/blob/master/sklearnex/tests/test_memory_usage.py#L91.  I will temporarily add ExtraTreesRegressor and ExtraTreesClassifier to this list, but these all need to be investigated immediately.


[html] Improve auto completion of html closing tags

For html closing tags, auto completions will show after typing </, can they show after typing < and needn't type /, and then the cursor is positioned between > and < after auto-completing?

Many editors all did this, like Komodo Edit.

@aeschli Not sure if this is low hanging

@osjn do you mean to have the closing tag be a higher priority than other tag auto-completions? Enabling this:

Type

Type <
Press enter to auto-complete /div>

Related: https://github.com/Microsoft/vscode/issues/877

@Tyriar not mean that, just the mean of providing for auto completion, and the affect after auto completing. As below:

type

type<
needn't press enter, it becomes

, and the cursor is between > and <
Resources:
`1. Komodo Edit
Brackets`

@osjn  This Extension would nearly meet with your requirement. It will automatically add closing tag when you type in the closing bracket of the opening tag.

@formulahendry thank you so much...

Not sure when we added that, but closing proposals are shows also right after <.
Note they only show up if there are tags to be closed.

There's a related issue: #38880


Repository no longer updating automatically?

Thanks for maintaining this mirror vjousse!
It appears to have stopped updating, as the last commit to your mirror was on 4 December 2011, while (according to http://svn.symfony-project.com/branches/1.4/CHANGELOG) 1.4.16 was released on 13 December 2011?

Mostly because there is now an official repo here: https://github.com/symfony/symfony1

OOOO fantastic!!


Feature 83 add back/cancel button to hom page.kt

Scaffolding added to HomePage.kt

@kkennedy-gh Is the plan to bring the bar to the top and place everything that is currently above the bar into where the lazy column is? In other words, you've staged it below the current page before baking it in? Looks like we will also have scrolling ability with this?!


Document sequelize associations

We should formally document how you do associations on the sequelize page.
A lot of it was discussed in this issue https://github.com/feathersjs/feathers-sequelize/issues/12 and the corresponding PR https://github.com/feathersjs/feathers-sequelize/pull/14#

Closed by<PHONE_NUMBER>e16a0e76808b7bf21f5cceb103f60d


Oracle User function in a SQL query is not working

Describe the bug
Trying to use Oracle function call in a SELECT query and cannot parse the statement.
To Reproduce
Steps to reproduce the behavior:

Example SQ - select r.*, test.numeric_function (  p_1 => r.param1
, p_2 => r.param2 )  as resultaat2
from results r
Parsing this SQL using JSqlParser with this statements
Exception - Cannot parse

Expected behavior
A clear and concise description of what you expected to happen.
System

Oracle 11g
Java Version - 8
JSqlParser version - 4.1

This parameter name mapping via => is not (yet) possible.


Blog app - Add forms

In this PR 🤖:

Created a method called current_user to make current user data available to all controllers ✔.

It returns the first user from the database ✔.

Created forms to perform the following functions 🔖:

Creates a Post on behalf of the current_user ✔.
Create a comment on behalf of the current_user ✔.

Allowed Users to add likes to Posts 👍🏻

.

Thanks, @medaminedev66  for your review. I've applied your requested changes. Also, I recorded a video showing the functionality of the likes button.
https://user-images.githubusercontent.com/95060298/178795854-e302ff8d-fc0c-44e6-8a1a-09352be4eca1.mov


sift-cli not included in Sift Workstation appliance

I have noticed that the sift-cli to update sift, is not presently included in the appliance.
Additionally, when running the update at present it throws the following error
sansforensics@siftworkstation: ~
$ sudo sift update

<EMAIL_ADDRESS>(Note, Also tried the same with the current stable release, v1.8.5)
sift-version: v2020.2.0

mode: desktop
downloading v2020.2.0

downloading sift-saltstack-v2020.2.0.tar.gz.asc
downloading sift-saltstack-v2020.2.0.tar.gz.sha256
downloading sift-saltstack-v2020.2.0.tar.gz.sha256.asc
downloading sift-saltstack-v2020.2.0.tar.gz
validating file sift-saltstack-v2020.2.0.tar.gz

Hashes for sift-saltstack-v2020.2.0.tar.gz do not match. Expected: , Actual: b6c7fa985070fa6c7749893913de6319490ecd02c90479171f4162d0d716a650  /tmp/sift-saltstack-v2020.2.0.tar.gz
Error: Hashes for sift-saltstack-v2020.2.0.tar.gz do not match. Expected: , Actual: b6c7fa985070fa6c7749893913de6319490ecd02c90479171f4162d0d716a650  /tmp/sift-saltstack-v2020.2.0.tar.gz
at validateFile (/snapshot/sift-cli/sift-cli.js:400:11)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async downloadUpdate (/snapshot/sift-cli/sift-cli.js:467:3)
at async run (/snapshot/sift-cli/sift-cli.js:706:5)
at async main (/snapshot/sift-cli/sift-cli.js:761:5)

----- PLEASE READ ----------------------
A lot of failures are caused by the apt system being locked
or unhealthy.
Before opening an issue in GitHub, please check to see if
your apt system is healthy.
Try running 'apt-get update' then remove any packages that
aren't used by running 'apt-get autoremove'
I managed to get it working by using the pre-release update
$ sudo sift upgrade --pre-release

<EMAIL_ADDRESS>sift-version: v2020.2.0

mode: desktop
downloading v2020.7.1

downloading sift-saltstack-v2020.7.1.tar.gz.asc
downloading sift-saltstack-v2020.7.1.tar.gz.sha256
downloading sift-saltstack-v2020.7.1.tar.gz.sha256.asc
downloading sift-saltstack-v2020.7.1.tar.gz
validating file sift-saltstack-v2020.7.1.tar.gz
validating signature for sift-saltstack-v2020.7.1.tar.gz.sha256
extracting update sift-saltstack-v2020.7.1.tar.gz

Thanks for pointing this out, will verify for the next build we publish.


[ISSUE #6598] Fix pop cause out memory error when message store not writeable

What is the purpose of the change
close #6598
Add return value for appendCheckPoint to determine whether to release message byte buffer.

Codecov Report

Merging #6623 (8410785) into develop (ea8b9d9) will decrease coverage by 0.02%.
The diff coverage is 25.92%.

@@              Coverage Diff              @@
##             develop    #6623      +/-   ##
=============================================
- Coverage      43.11%   43.09%   -0.02%
+ Complexity      8997     8991       -6
=============================================
  Files           1107     1107
  Lines          78287    78297      +10
  Branches       10202    10206       +4
=============================================
- Hits           33755    33744      -11
- Misses         40314    40331      +17
- Partials        4218     4222       +4

Impacted Files
Coverage Δ

...cketmq/broker/processor/PopBufferMergeService.java
33.10% <0.00%> (-0.24%)
:arrow_down:

...rocketmq/broker/processor/PopMessageProcessor.java
36.88% <30.43%> (-0.74%)
:arrow_down:

... and 14 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Make migration keys more unique

Originating issue: IBMPrivateCloud/roadmap#62995
Previously, in multi-Pak migration where two Paks migrate from one common install of Common Services to two separate installs, one Pak's migration activity written back to MongoDB was indistinguishable from another's, which led to a race condition where the first Pak to migrate would be successful and the second would fail due to skipping all of the documents that had been migrated by the first Pak.
This change uses the services namespace as a part of the key written to the migrated MongoDB documents to avoid this naming collision between migrations.

Cloing this PR in favor of https://github.com/IBM/ibm-iam-operator/pull/830


go.mod: Use uwu-tools/magex

What type of PR is this?
/kind cleanup
/area dependency
What this PR does / why we need it:

go.mod: Use uwu-tools/magex (ref: https://github.com/uwu-tools/magex/releases/tag/v0.10.0)
go.mod: Update github.com/uwu-tools/magex to v0.10.0

Signed-off-by: Stephen Augustus<EMAIL_ADDRESS>/assign @jeremyrickard @cpanato
cc: @kubernetes-sigs/release-engineering
Which issue(s) this PR fixes:

Special notes for your reviewer:
Does this PR introduce a user-facing change?

- go.mod: Use uwu-tools/magex (ref: https://github.com/uwu-tools/magex/releases/tag/v0.10.0)
- go.mod: Update github.com/uwu-tools/magex to v0.10.0

@kubernetes-sigs/release-engineering -- We need to do similar updates to our other projects; can I ask someone to work on this?

https://github.com/kubernetes-sigs/bom
https://github.com/kubernetes-sigs/release-sdk
https://github.com/kubernetes-sigs/tejolote/blob

ref: https://cs.k8s.io/?q=carolynvs%2Fmagex&i=nope&files=&excludeFiles=&repos=

@kubernetes-sigs/release-engineering -- We need to do similar updates to our other projects; can I ask someone to work on this?

https://github.com/kubernetes-sigs/bom

https://github.com/kubernetes-sigs/release-sdk

https://github.com/kubernetes-sigs/tejolote/blob

ref: https://cs.k8s.io/?q=carolynvs%2Fmagex&i=nope&files=&excludeFiles=&repos=

Will do

@kubernetes-sigs/release-engineering -- We need to do similar updates to our other projects; can I ask someone to work on this?

https://github.com/kubernetes-sigs/bom
https://github.com/kubernetes-sigs/release-sdk
https://github.com/kubernetes-sigs/tejolote/blob

ref: https://cs.k8s.io/?q=carolynvs%2Fmagex&i=nope&files=&excludeFiles=&repos=

all done

all done

Thanks so much, @cpanato!!


add machine424 and rexagod  to OWNERS

Also move Joao to emeritus.
cc @jan--f @machine424

And @marioferh too

/lgtm


bigger unread dots, and make them show up on mobile

Makes the orange dot bigger like in the designs, and also gets it to show up on mobile.


CIP-0088 | Introducing Policy Intent Classification

Frontends can use intent classifications to filter which assets they allow on their platform. For example, "NFT" marketplaces can choose to allow only "collectible" classification. DEXs can allow "trading" and "governance" classifications. Bond marketplaces can focus on a "Bond" classification. These are just examples of course, and the classification strings themselves can be community-created (options mainly set by minting platforms who build the initial CIP-88 registration for new minting policies) so that a list of allowed classification strings doesn't have to be maintained by CIP editors. DEXs will require legacy support for the Cardano Token Registry, however for future token listings they can rely on the policy intent classification in the policy's CIP-88 registration.
Proposed for both CIP-25 and CIP-68 as referenced under CIP-88. Can be added to other CIPs that have different genres of assets.

Sorry for the delay on leaving a comment here @BrockCruess. Is the thought here to have clearly defined classifications?
Generally speaking, in order to reduce ambiguity in CIP-88 I took the approach that "well defined" values should use integer-based indexes to prevent common typos and spelling errors.
Some of the language based on your comment above seems to suggest that this is a more broad "categorization" of the types of token in which case I could see justification that it should instead be an array of values but then this raises the issue of inconsistent "categorization" across marketplaces and how to define and maintain a community-curated list of categories and their associated spellings/indexes.
I fail to see much value-add here if this is just yet another free-form label that may actually introduce more complications and exceptions to rules if people publish data that does not follow a "marketplace-accepted" classification.

@Crypto2099 pre-defined and expandable categories with assigned integers was my original intention for this idea, but in our private discussion about it you had mentioned that you were opposed to a "whitelist" of classification options.
if you've changed your mind on that we could work out the best way to maintain a list of valid classifications and if someone comes up with a new category a simple pull request could have it merged and active. we'd just need a way to notify front ends to allow the new option in their registration tools. or find a way to have the registration tools detect new category options in main branch (my personal fav idea).
or we keep it this way and do as you originally recommended and have explorers/front ends build synonym lists to translate synonyms and spelling errors into the valid option. but that seems like a lot of work for front ends.
i'm open to explore any option that makes this idea work, as i really think it'll be valuable for asset filtration in the long run as hundreds of thousands to millions (to billions?) of new assets are minted to chain in the future and front ends either have to see all of them and build/store data for all of them, or filter them manually.

@BrockCruess we have to move this on the path toward closure if we don't have a firm justification for making changes to CIP-0088.  It's been 6 months since your stating (https://github.com/cardano-foundation/CIPs/pull/739#issuecomment-1925301746) you are "open to ideas" about the exact implementation & we do need more than that to proceed through the CIP process.
From that point of view this looks (potentially) Abandoned so I'm tagging it as such.  We can throttle it back to Waiting for Author if @BrockCruess you can identify & post any specific issues you are trying to solve or demonstrate before progressing the CIP.  In any case please try develop your case more if you would still like to keep this PR open.

@rphair the issues I'm trying to solve seem clear to me and the commits demonstrate the simple addition to the metadata. I haven't heard back from @Crypto2099 regarding the preference of an integer-based index (a whitelist of acceptable inputs) over a user-defined string that relies on the platforms to determine which strings they accept. Further progression of this PR does rely on that decision, and an editor should probably make that call as you guys would know better than I would. I do personally agree that an integer-based index would work best and that was my initial idea for this addition. If an index format is should be added to this PR please let me know or please recommend a simple format as my first attempt may not be ideal and will require revisions anyways.
I'm happy to edit my existing commits with example integers in the meantime.

Thanks for the update @BrockCruess ... changing tag accordingly back to Waiting for Author.  Ideally we should never need a Waiting for Editor tag but we need something more specific than "Waiting for Someone other than Author".  It's one of the process issues that we're trying to settle in tagging these proposals & thanks for your status update in any case.
@Crypto2099 I trust that you will respond as the author has requested & keep interacting until that point is settled? 🙏

@Crypto2099 it seems we are waiting for you to respond here.  Since we have no "Waiting for Editor" tag we may have to leave it here in half-life unless @BrockCruess can make a case for these changes that everyone can understand.  In the meantime we don't have enough of a consensus to modify CIP-0088 as suggested here.
I hope the 2 of you can work it out & if that isn't done in a reasonable amount of time then we should probably close this.  (If any third parties are following this proposed change & think it would be beneficial, please post here in the meantime.)


Packet logging

We want to implement packet logging to allow better debugging of applications
Given the significant difference between logging ( high level code paths ) and packets ( everything sent from it to server we will make the following assumptions:

we log everything that comes to server, before permissioning and auth
we log updates once for all clients, and not multiple times
we use a separate section in config specially for packet logging that doesn't interfere with logger
we use a custom file logger to write since Winston does funky stuff
we assume anything with access to packet logs has access to confidential data. We could  omit just aiuth messages payloads if needed.
if being run on a non production server for says we would still need log rotation. We can do so by using Linux rogtotats on Linux boxes, windows will probably require custom rotation logic
file logger should be swappable, since some loggers work via network/UDP
show warning on startup recommending against usage in performance and production environments

packetLogger:
  name: default
  Filepath: ../logs/packet.txt

#287

Changing to a won't fix due to performance issues for general usage.


[T4A3][T16-B2]ZhaoDingfan

Ready for review.

Avoid accumulating unrelated changes into a single PR.
Tip: If you are currently on branch1 and want to create a new branch2, you need to switch back to master branch before creating branch2. If not, changes in branch1 will appear in the PR created from branch2 later.
The child classes should have made use of the parent class' constructor instead of duplicating code in both classes.

@ZhaoDingfan Some comments added. Please close the PR after reading comments.


Warning creating ingress, after I had deleted it

/kind bug
What versions of software are you using?

I forgot about an old ingress url (created during a previous test against another kube) and did an odo push, so I deleted it and pushed again. It still said it was trying to create it.
Actual behavior
deboer-mac:node2 deboer$ odo url list
Found the following URLs for component node2
NAME           STATE      URL                                       PORT     SECURE     KIND
node2-3000     Pushed     http://node2-3<IP_ADDRESS>.3.nip.io     3000     false      ingress
deboer-mac:node2 deboer$ odo url delete node2-3000
? Are you sure you want to delete the url node2-3000 Yes
 ✓  URL node2-3000 removed from component node2

To delete the URL on the cluster, please use `odo push`
deboer-mac:node2 deboer$ odo push

...
Creating Kubernetes resources for component node2
 ✓  Waiting for component to start [13s]
 ⚠  Unable to create ingress, missing host information for Endpoint http-3000, please check instructions on URL creation (refer `odo url create --help`)

Expected behavior
I would have expected an error deleting the url or no output, not 'unable to create ingress' when it didn't exist anymore.

Thinking about it, maybe this is just the standard warning that it couldn't determine the host and couldn't auto-create an ingress? Still, it was confusing to me that I got the same message when I had a url created with an incorrect host and when I had deleted it and didn't have one.

/lifecycle frozen

/lifecycle frozen

in v3 this is not going to be a problem anymore, as odo is not going to automatically create Ingress or Routes. Odo will use port forwarding this won't be a problem there.


useRoute()  problem

Version
4.0.0-rc.3
Reproduction link
https://gitee.com/Jmysy/pear-admin-ant
Steps to reproduce
const route = useroute();  watch (route, function() { do something })
What is expected?
Use useRoute() Api to monitor route changes.
What is actually happening?
After the local operation is normal, the interface will be stuck and the CPU will soar, but no error message will be reported

英文使用翻译, 会有些曲解本意，此处原文来表达我的意思： watch(useRoute(),function(){ }) 此方式监听路由，本地开发调试时没有问题的，打包之后该方式会造成浏览器卡死

Use watch(() => route) or { deep: true } option for the watcher.

Please, next time consider using the forum, the Discord server or StackOverflow for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂


add ImageBackground typings for update react-native 0.50

cc @styled-components/typers
@mkasten Thanks for the contribution! It looks like the react-native typings will need updating: https://travis-ci.org/styled-components/styled-components/jobs/298992746

Navigator component was deprecated in react native, we need to remove it.

I think Navigator was removed in v3?

@probablyup this was already addressed before. I’m not sure though why the ImageBackground type is gone


Max: Setting tweaks on Review Family

Changelog Description

Bug fix of not being able to publish the preferred visual style when creating preview animation
Exposes the parameters after creating instance
Add the Quality settings and viewport texture settings for preview animation
add use selection for create review

Additional info
Some shading issue possibly exists in the first two frame if you are using Max version elder than 2024.
Testing notes:

Launch Max
Create Review Instance
Choose your preferred settings
Publish

When changing size percentage to any other value and hit Enter key it shows a bit weird error msg

That's not an error but it's the Help dialog (question mark) top right at the publisher. I have seen artists here getting the same, that the "Enter" button sometimes triggers the Help dialog to show when pressing enter when in a text or number field. It'd be a separate issue for @iLLiCiTiT to maybe take a look at.
However, I myself have been unable to reproduce this consistently - but another artist here got it all the time. I'm not sure why. I tested it in Maya and the artist reported it in Houdini - it might be that the focus events behave different in Houdini and Max making this issue pop up?

All shading types seems working for Review but the Percent of Output doesnt have any effect on the output resolution of the rendered sequence.
Need to be addressed.

but the Percent of Output doesnt have any effect on the output resolution of the rendered sequence.

Which version of Max did you test in? Since I believe the implementation in the code differs between Max 2023 and below and Max 2024 and up. As such I'd recommend testing the PR in both older and a new version to be sure both implementations work.

I have tested in max 2024

@LiborBatek can you test in Max 2024 one more time to ensure the code changes won't break anything? @antirotor can you do a final check for it before the merge?
Thanks!


The job has been abandoned because agent  did not renew the lock. Ensure agent is running, not sleeping, and has not lost communication with the service.

Hello Visual Studio Team Services Team,
we face the problem that in a real high frequency our build job with build vNext crashes. The error message is that the agent could not renew the lock.
Our build agent is installed on a local windows 2008R2 server. We attached the worker and also the agent logs as text files. Also we made two screenshots where you can see that the console crashed while executing our build job. The problem occurs in different steps when our build job is running. Sometimes
the build agent crashes while the deployment of the test agent is started. Sometimes it crashes when the solution is build (for running the integration tests later) and also sometimes the agent crashes while the integration tests are executed. We already uninstalled the build agent and reinstalled it. But that didn't fixed
the problem. It is really important for us that this problem get fixed because we have 1000 Integration Tests that should run every night. But the last 10 times it never finished successfully.

Worker_20170324-200007-utc.txt
agent_log.txt
With kind regards
Florian Ertelt, labs
Account Name: http://lupusalpha.visualstudio.com
Agent Version: 2.110.0
Agent.OSVersion: 6.1.7601

@Nitin the app crash screenshot point to the DTAExecutionHost, can you take a look?

@k3flo are you running build agent and test agent on same machine? This is currently not-supported scenario.
If you are using different test agent machine, please can you let us know the Test Agent version and Attach the Event Viewer logs?

@nigurr yes were running the build and test agent on the same machine. We moved the test agent to another machine but now we are facing another error with the testrunner (https://github.com/Microsoft/vsts-agent/issues/891). The test runner crashes every run after some time.


No forumdb database is available in standalone

There is no forumdb database available in standalone container. The below is the preview of \l command.

I see you are running docker. Here are the steps you can take to get the forum db in standalone.

cd docker-images/
Run bash run-pg-docker.sh - Create the standalone container
Run docker cp setup standalone_learn_postgresql_1:/setup - Copy the setup scripts into the container
Run docker exec -it standalone_learn_postgresql_1 /bin/bash -c "sh /setup/001-create-database-users.sh" - Runs the create user script
Run docker exec -it standalone_learn_postgresql_1 psql -U postgres - Open an interactive psql session in the container
\i /setup/002-forum-database.sql - Run the forum database sql file to create the forumdb.

Hope this helps!!!

@subbuk987 I see you are running docker. Here are the steps you can take to get the forum db in standalone docker container.
cd docker-images/
Run bash run-pg-docker.sh - Create the standalone container
Run docker cp setup standalone_learn_postgresql_1:/setup - Copy the setup scripts into the container
Run docker exec -it standalone_learn_postgresql_1 /bin/bash -c "sh /setup/001-create-database-users.sh" - Runs the create user script
Run docker exec -it standalone_learn_postgresql_1 psql -U postgres - Open an interactive psql session in the container
\i /setup/002-forum-database.sql - Run the forum database sql file to create the forumdb. \I(include) command to run the SQL file.
Hope this helps!!!

There is no forumdb database available in standalone container.

The three databases postgres and template0,template1 are the default installation. In short, something went wrong during the docker initialization. I suggest you to start from scratch deleting all the storage on the filesystem related to the docker image and let the container re-initialize itself. Otherwise, follow the suggestions from @NathanBeesley

Thanks @NathanBeesley . Your approach worked for me. Also, Thanks @fluca1978 for your swift response. I'm Enjoying the book. I'm Closing the issue.


complete makefile commands and add GH Actions for CI

separating issues so going to create a new issue for GH Actions


public/vendor/laralvel-admin *.css *.js files showing 403 (Forbidden: Access is denied.)

Laravel Version: 5.6
PHP Version: 7.1
Laravel-admin: #.#.#

Description:

Steps To Reproduce:
it works ok in local environment.
but in azure, it will show the 403 (Forbidden: Access is denied.) error
GET https://jeryphp-laravel-admin.azurewebsites.net/vendor/laravel-admin/AdminLTE/bootstrap/css/bootstrap.min.css 403 (Forbidden: Access is denied.)

@13127755587 Looks like you resolved the issue because I was able to access the file and your login page.

how to solve?

@asterism612 I raised a support case in Azure, and they told me to add a tag in the web.config file

Can you share the solution with us? Tks


Develop 2.0 merge from cql to elm and develop (2)

ℹWork for #371 and #386
Background
Prior to this PR, develop was merged into develop-2.0, and develop was merged into cql-to-elm.
This PR merges cql-to-elm and 'scopes' into develop-2.0. These branches deviated significantly over the past 4 or more months and merging them all back into one, is quite a challenge.
Remarks

Updated the solution filter file Cql.slnf, to include the three new projects related to cql-to-elm
Removed the folder Cql.Firely.Test, since it only had one unit test without any assertions
The CqlOperatorBinder method binding logic had to be expanded. Previously only the inner generic argument was matched to the generic parameter, but now the argument itself is also tried. Meaning, previously when the input argument is CqlInterval and the parameter is T, then only CqlDate was tried on T. Now, CqlInterval is also tried.
Added missing closing on CqlInterval operator
ElmAsExpression must also take an argument for strictness
Base test in CqlToElmTests must use LibraryExpressionBuilder instead of ExpressionBuilder
The Lambda method was removed on ExpressionBuilder, but the CqlToElmTests still use it, so had to put an extension method for it there. Also, the ExpressionBuilderContext.TranslateArg method had to be opened from private to internal, to make this work
The generated C# has many places where null is cast to a type. Must be fixed in issue #387 387.
Always convert to result type when translating elements in ExpressionBuilderContext.TranslateElement. This is especially important when two arguments are passed to Equals, since it expects the argument types to be the same
Fix ExpressionBuilderContext.ConceptRef by returning the type of the actual conceptRef, and not hard-coded CqlCode[] (#386)
Small fix in CqlOperatorsBinder.
Regenerate all C#

CMS Integration Tests
Running the integration tests (a separate repo from this) returns the following results:

Tests passing before merge: 902 / 1822 (47%)
Tests passing after merge: 1247 / 1822 (68%)

Questions

Why is the length of a null string, null, but the length of a null list is zero? See tests LengthNullString and LengthNullList. The logic for Length can be found in CqlOperators.Length(string?) and CqlOperators.Length<T>(IEnumerable<T>?). I added the LengthNullString test in code and in the xml tests as well
There are 2 XmlTests, one in CoreTests, the other in CqlToElmTests. The one in CoreTests is empty? My guess is the CqlToElmTests.XmlTests is replacing CoreTests.XmlTests and thus the latter must be removed?

🎉


(maint) Allow beaker host to be set using ip, hostname or vmhostname

:+1:  :)

Changing this to be a utility function


alignment with newline as last character

when the text of a StSt ends in a newline (\n) the alignment in the frames rect is a bit strange (too far to the top and right).
not a big deal but maybe as easy to solve as to remove the newline.
thanks

thanks for the report! actually was just working on a similar issue with multi-line text so this should be fixed in the next minor release, probably later this week


Question about "operation pending time"

I am not sure if this is a bug or anything, so I ignored the issue template 🙏.
I searched other issues, and googled, didn't find related-issues 🤔.

Here is my question, I had a key binding <leader>e, the leader key is space
  { "<leader>e", ":call VSCodeNotify('workbench.view.explorer')<cr>" },

In vscode, if I pressed leader(space), then about 500ms passed, the behaviour similar to cursor go right, just like this GIF.

so I want to know is, is there any way to increase the "operation pending time"?

:h timeoutlen


Opening one jupyter notebook causes opening of others previously used .ipynb files

Hello! I am using VScode to work on the remote server using conda environments and jupyter notebooks. I noticed that when I close the window with jupyter notebook tabs, the next time I open the window and try to open one notebook, the whole bunch of notebooks opens as well and it gets really laggy for a moment.

VSCode Version: 1.48
OS Version: macOS Catalina 10.15.6
currently files.hotExit : "off"

Steps to Reproduce:

Close a window with opened jupyter notebook tabs
Open a new window and open one of the notebooks

Does this issue occur when all extensions are disabled?: Yes/No
No

/extPython


replaceReducer not working when upgrading to version 4 of redux

What is new in redux v4?
My code was working with redux v3.x.
But, when upgrading with redux v4, replaceReducer didn't update the reducers.
Where can I know about how to use replaceReducer with redux v4?
Meanwhile, I will be using redux v3.x
This is the implementation BTW, https://github.com/sabbiu/dynamic-reducers-for-react

The implementation for replaceReducer is still here at https://github.com/reactjs/redux/blob/4a215fb74167675485df7d6d2fb1197a184cc461/src/createStore.js#L210-L217, and we've got tests that are all presumably passing .  What behavior are you seeing?  What do you mean by "didn't update the reducers" ?

In my store, https://github.com/sabbiu/dynamic-reducers-for-react/blob/master/src/store.js, I am adding a function to store.
store.asyncReducer = {};
store.injectReducer = (key, reducer) => {
    store.asyncReducers[key] = reducer;
    store.replaceReducer(createReducer(store.asyncReducers));
    // redux v3.x gives me new store
    // redux v4 doesn't.. it gives the same old store
    console.log(store.getState());
};

This is my function for createReducer
import { combineReducers } from "redux";
import { reducer as formReducer } from "redux-form";
import PostsReducer from "./reducer_posts";

const createReducer = asyncReducers =>
  combineReducers({
    posts: PostsReducer,
    form: formReducer,
    ...asyncReducers
  });

export default createReducer;

This is related to Redux DevTools. Disabling the extension fixes this issue for me. Still investigating.

I just got a report of this behavior from someone working through my Educative "Practical Redux" course:

Reducers hmr is not working with redux 4. the tutorial uses an older version, but this may be worth mentioning

My guess is this might be related to the change in the action for replacing. Maybe DevTools handles INIT action specially.

Yup

That's interesting, because https://github.com/reduxjs/redux-devtools/issues/391 and https://github.com/zalmoxisus/redux-devtools-instrument/pull/17 make it look like there were changes already done to handle this.

@markerikson The extension doesn't seem to have that fix though.

I have same issue; i have uninstall extension, and problem persist... replaceReducer still bugged.

redux-devtools-instrument is waiting for this PR to be merged in.

Still have this problem, and disabling the @redux-devtools/extension does not work for me.

@JoaoAlmeida-Kununu this issue was closed 6 years ago.
If you're having problems, please file a new issue with a reproduction or a Replay ( https://replay.io/record-bugs ).


Where as in the Ember UI, option "Require ALL of" is available

The ember UI is actually incorrect in how it has interprets the scheduling rules, so there will be no "Require all of" in the dashboard UI.


Interoperability with bevy .ttf AssetLoader

Currently crate uses its own asset loader for a font.
This may be desired eventually too, but it may overlap with bevy standard loader. It could not be used, since there is no way to expose the font-bytes (needed for ttf2mesh).

Fixed by #15


Cannot destructure property 'subscription' of 'undefined' as it is undefined  at handlePaymentMethodRequired

Hi,
I have been trying to implement this checkout-single-subscription
What is working :

Integration Card :<PHONE_NUMBER>424242
Integration Card :<PHONE_NUMBER>003184 (3DS)

Failure :

Integration Card :<PHONE_NUMBER>003178.

** Expected **  : retrieve the error message insufficient funds
** Explanation ** : The logs (see index) are able to throw the right error Your card has insufficient funds. However the error catching in the creatsubscription function fails.

Catching 8 in createSubscription = TypeError: Cannot destructure property 'subscription' of 'undefined' as it is undefined.
at handlePaymentMethodRequired (Checkoutform.js:103)

I had to create a default error   showCardError({ error: { message: 'Your card was declined.' } });. because I wasn't able to use the thrown erros.

export default function CheckoutForm(props) {
    const [priceId, setPriceId] = React.useState('price_1GqywBC2ahMs23DqyBiAZLZG');
    const [openedSuccessModal, setOpenedSuccessModal] = React.useState(false)
    const[openErrorSnack,setOpenSnack] = React.useState(false)
    const[errorMessage,setErrorContent] = React.useState('')

  const stripe = useStripe();
  const elements = useElements();

function showCardError(event) {
  console.log("showCardError")
  if (event.error) {
    setErrorContent(event.error.message)
    setOpenSnack(true)
  } else {
    setErrorContent('event.error.message')

  }
}

function retryInvoiceWithNewPaymentMethod(
  customerId,
  paymentMethodId,
  invoiceId,
  priceId
) {
  console.log("retryInvoiceWithNewPaymentMethod")
  return (
    fetch('http://<IP_ADDRESS>:8000/api/user/retry_subscription/', {
      method: 'post',
      headers: {
        'Content-type': 'application/json',
          Authorization: `Bearer ${props.token}`
      },
      body: JSON.stringify({
        customerId: customerId,
        paymentMethodId: paymentMethodId,
        invoiceId: invoiceId,
      }),
    })
      .then((response) => {
        return response.json();
      })
      // If the card is declined, display an error to the user.
      .then((result) => {
        if (result.error) {
          console.log("1 throwing in retryInvoiceWithNewPaymentMethod")
            console.log("1 result=",result)
          // The card had an error when trying to attach it to a customer.
          throw result;
        }
        return result;
      })
      // Normalize the result to contain the object returned by Stripe.
      // Add the addional details we need.
      .then((result) => {
        return {
          // Use the Stripe 'object' property on the
          // returned result to understand what object is returned.
          invoice: result,
          paymentMethodId: paymentMethodId,
          priceId: priceId,
          isRetry: true,
        };
      })
      // Some payment methods require a customer to be on session
      // to complete the payment process. Check the status of the
      // payment intent to handle these actions.
      .then(handleCustomerActionRequired)
      // No more actions required. Provision your service for the user.
      .then(onSubscriptionComplete)
      .catch((error) => {
        console.log(" catching 2 in retryInvoiceWithNewPaymentMethod :",error)
        // An error has happened. Display the failure to the user here.
        // We utilize the HTML element we created.
        showCardError(error);
      })
  );
}

function handlePaymentMethodRequired({
  subscription,
  paymentMethodId,
  priceId,
}) {
  console.log("handlePaymentMethodRequired")
  if (subscription.status === 'active') {
    console.log("considered active in handlePaymentMethodRequired")
    // subscription is active, no customer actions required.
    return { subscription, priceId, paymentMethodId };
  } else if ( subscription.latest_invoice.payment_intent.status === 'requires_payment_method') {
    console.log("subscription.latest_invoice.payment_intent.status=",subscription.latest_invoice.payment_intent.status)
    // Using localStorage to manage the state of the retry here,
    // feel free to replace with what you prefer.
    // Store the latest invoice ID and status.

    // faire des vraies variables de ça, car comme ça = de la merde
    localStorage.setItem('latestInvoiceId', subscription.latest_invoice.id);
    localStorage.setItem('latestInvoicePaymentIntentStatus', subscription.latest_invoice.payment_intent.status);
        console.log("11 throwing in handlePaymentMethodRequired")
      console.log("11 custom_throw=",{ error: { message: 'Your card was declined.' } })

    throw { error: { message: 'Your card was declined.' } };
  } else {
    return { subscription, priceId, paymentMethodId };
  }
}

function handleCustomerActionRequired({
  subscription,
  invoice,
  priceId,
  paymentMethodId,
  isRetry,
}) {
      console.log("handleCustomerActionRequired")

  if (subscription && subscription.status === 'active') {
        console.log("subscription exists and subscription.status ===active in handleCustomerActionRequired")

    // Subscription is active, no customer actions required.
    return { subscription, priceId, paymentMethodId };
  }

  // If it's a first payment attempt, the payment intent is on the subscription latest invoice.
  // If it's a retry, the payment intent will be on the invoice itself.
  let paymentIntent = invoice ? invoice.payment_intent : subscription.latest_invoice.payment_intent;

  if (paymentIntent.status === 'requires_action' ||  (isRetry === true && paymentIntent.status === 'requires_payment_method')) {
    console.log("paymentIntent.status:",paymentIntent.status)
    console.log("paymentIntent.client_secret:",paymentIntent.client_secret)

    return stripe
      .confirmCardPayment(paymentIntent.client_secret, {
        payment_method: paymentMethodId,
      })
      .then((result) => {
        if (result.error) {
          console.log("4")
          console.log("Throwing 4 in handleCustomerActionRequired =",result)
          // Start code flow to handle updating the payment details.
          // Display error message in your UI.
          // The card was declined (i.e. insufficient funds, card has expired, etc).
          console.log("result ")
          throw result;
        } else {
          if (result.paymentIntent.status === 'succeeded') {
            console.log("result.paymentIntent.status:",result.paymentIntent.status)
            console.log("in handleCustomerActionRequired")
            // Show a success message to your customer.

            setOpenedSuccessModal(true)
            localStorage.removeItem('latestInvoiceId')
            localStorage.removeItem('latestInvoicePaymentIntentStatus')

            // There's a risk of the customer closing the window before the callback.
            // We recommend setting up webhook endpoints later in this guide.
            return {
              priceId: priceId,
              subscription: subscription,
              invoice: invoice,
              paymentMethodId: paymentMethodId,
            };
          }
        }
      })
      .catch((error) => {
        console.log("6")
        console.log("Catching 6 in handleCustomerActionRequired=",error)
        showCardError(error);
      });
  } else {
    // No customer action needed.
    return { subscription, priceId, paymentMethodId };
  }
};

  function onSubscriptionComplete(result) {
    console.log("onSubscriptionComplete")
    console.log("result.subscription.status=",result.subscription.status)
    if (result.subscription.status === 'active') {

      setOpenedSuccessModal(true)
      localStorage.removeItem('latestInvoiceId')
      localStorage.removeItem('latestInvoicePaymentIntentStatus')

  }
}

  function createSubscription({ customerId, paymentMethodId, priceId }) {
  return (
    fetch('http://<IP_ADDRESS>:8000/api/user/create_subscription/', {
      method: 'post',
      headers: {
        'Content-type': 'application/json',
          Authorization: `Bearer ${props.token}`

      },
      body: JSON.stringify({
        customerId: customerId,
        paymentMethodId: paymentMethodId,
        priceId: priceId,
      }),
    })
      .then((response) => {
        return response.json();
      })
      // If the card is declined, display an error to the user.
      .then((result) => {
        if (result.error) {
                            console.log("7 throwing in createSubscription ")
                              console.log("7 result=",result)

          // The card had an error when trying to attach it to a customer.
          throw result;
        }
        return result;
      })
      // Normalize the result to contain the object returned by Stripe.
      // Add the addional details we need.
      .then((result) => {
          //console.log("return=",result)
        return {
          paymentMethodId: paymentMethodId,
          priceId: priceId,
          subscription: result,
        };
      })

      // Some payment methods require a customer to be on session
      // to complete the payment process. Check the status of the
      // payment intent to handle these actions.
      // // If attaching this card to a Customer object succeeds,
      // // but attempts to charge the customer fail, you
      // // get a requires_payment_method error.
      // // No more actions required. Provision your service for the user.
        .then(handleCustomerActionRequired)
        .then(handlePaymentMethodRequired)
        .then(onSubscriptionComplete)
        .catch((error) => {
        // An error has happened. Display the failure to the user here.
        // We utilize the HTML element we created.
        console.log("8")
        console.log("Catching 8 in createSubscription =",error)
        showCardError({ error: { message: 'Your card was declined.' } });
      })
  );
}

  function createPaymentMethod(cardElement, customerId, priceId) {
  return stripe
    .createPaymentMethod({
      type: 'card',
      card: cardElement,
    })

    .then((result) => {
      if (result.error) {
        console.log("9 in createPaymentMethod")
        showCardError(result)
      } else {
          let latestInvoiceId = localStorage.getItem('latestInvoiceId');
        let latestInvoicePaymentIntentStatus =  localStorage.getItem('latestInvoicePaymentIntentStatus')

        if (latestInvoiceId && latestInvoicePaymentIntentStatus==='requires_payment_method'){
            retryInvoiceWithNewPaymentMethod(customerId, result.paymentMethod.id, latestInvoiceId,priceId)
        }

        else  createSubscription({
          customerId: customerId,
          paymentMethodId: result.paymentMethod.id,
          priceId: priceId,
        });
      }
    });
}

  const handleSubmit = async (event) => {
    // We don't want to let default form submission happen here,
    // which would refresh the page.
    event.preventDefault();

    console.log("priceId=",priceId)
    console.log("customerId=",props.customerId)

    if (!stripe || !elements) {
      // Stripe.js has not yet loaded.
      // Make sure to disable form submission until Stripe.js has loaded.
      return;
    }

      await createPaymentMethod(elements.getElement(CardElement),props.customerId,priceId)
   };

  return (
    <form onSubmit={handleSubmit}>
      <FormControl component="fieldset">
  <FormLabel component="legend">Plan</FormLabel>
  <RadioGroup aria-label="product_id" name="product_id" value={priceId} onChange={(event)=>setPriceId(event.target.value)}>
    <FormControlLabel value="price_1GvhOFC2ahMs23Dqf7E83kTk" control={<Radio />} label="EXPENSIVE Plan" />
    <FormControlLabel value="price_1GqywBC2ahMs23DqyBiAZLZG" control={<Radio />} label="Veterinary Plan (15.99 / mois)" />
  </RadioGroup>
</FormControl>
      <CardSection/>
      <button disabled={!stripe}>Save Card</button>
<ModalSuccessPayment is_open={openedSuccessModal} setIsOpen={setOpenedSuccessModal} text ={<Emoji text=" 🎉 Your payment has been accepted and your subscription started" />} {...props}/>
      {/*{snack}*/}
      <Snackbar open={errorMessage.length > 0} autoHideDuration={600000} message={errorMessage}/>
    </form>
  );
}

Thanks for writing in @lgm-dev
It looks like you're implementing a Subscription flow with Elements rather than Checkout. This sample is specifically showing how to use Stripe Checkout: https://stripe.com/docs/checkout
Do you mind reaching out too support with these details so they can guide you as this isn't related to this sample?
support.stripe.com/contact or the engineers on IRC: #stripe on Freenode.


Add files via upload

Uhm... first of all, I doubt this was code reviewed appropriately, because if that was the case you would have seen that this sketch is in the totally wrong place and uncompilable.


Retain session state across ODB bounces

Right now we store some session state (chosen tabs, opened treeviews for example) in Slots. If you bounce the browser, you lose this state. Similarly, if you navigate panes.  We should be storing all of this in SessionState objects that are appropriately scoped (so that the same piece of UX in the hierarchy always ends up with the same identity) so that we don't lose this state.

A couple of things about this:

If there is some unique, persistent id for a given SessionState on the server side, we can store this in the browser's localStorage and, when a page loads/reloads, attempt to use that information to grab the initial state from the server. This is a common practice in frontend land.
We should think about how we want to differentiate between single-client state (ie, things that matter for just one specific user) and "global" client state (ie where some change or event on the server side updates every client's view). We can and probably should make this a part of the WS lifecycle refactor by introducing "channels" to outbound websocket messages. One channel could be updates on the UI of specific users and another to broadcast to other users.

yes, we can give a uuid to each session, no problem. Right now I have
some brittle thing I put in that tries to figure out which session we were
in based on the order in which we bounce, but obviously retaining it would
be much much better.
this is already taken care of, in the sense that we have a
"SessionState" object, which acts like a 'Slot', and which can be used to
store this, and then we have things in the ODB which are global. So the
semantic model for this is already in place.  I think the issue is that
right now SessionState doesn't have a rich enough model to understand that
if you have a tree view, you have scoped buttons, so how do you give a
persistent name to each button so that when it goes away and then comes
back it knows which session-state slot to look in?

On Fri, Jun 28, 2019 at 12:35 PM Eric Gade<EMAIL_ADDRESS>wrote:

A couple of things about this:

If there is some unique, persistent id for a given SessionState on
the server side, we can store this in the browser's localStorage and,
when a page loads/reloads, attempt to use that information to grab the
initial state from the server. This is a common practice in frontend land.
We should think about how we want to differentiate between
single-client state (ie, things that matter for just one specific user) and
"global" client state (ie where some change or event on the server side
updates every client's view). We can and probably should make this a part
of the WS lifecycle refactor by introducing "channels" to outbound
websocket messages. One channel could be updates on the UI of specific
users and another to broadcast to other users.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/APrioriInvestments/nativepython/issues/111?email_source=notifications&email_token=AB6OHBBQLDLUOZX6OVW7EQ3P4Y4UXA5CNFSM4H3CSHH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2R7JI#issuecomment-506797989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6OHBF2MBFVSCBZV6T6GBTP4Y4UXANCNFSM4H3CSHHQ
.


System keyboard can only be opened as a default type.

The system keyboard type is currently hardcoded into MixedRealityKeyboardBase.ShowKeyboard(string, bool).

It would be preferable if the keyboard type was passed as a parameter, provided that MRTK actually handles different types of keyboard.
It is a bad UX design to open a default keyboard when e.g. the given input field only accepts numeric input.

Due to #7944 we do not plan to make it a parameter for now.


CFAlertDialog - Reborn.

New changes:
Types: Notification, Alert, Bottom sheet.

Separate animations for presentation and dismissal for each type.
Swipe to dismiss on the Notification type.
Demo project to highlight all the available features.

Customisable Features:

Icon, title and message(with alignment).
Action button types Neutral, Positive, Negative(with alignment).
Background color.
Dismiss on background tap.
Add custom header/footer views.
Items list (Simple, Single-select, Multi-select).

@neha-gehani Made the requested improvements and added a few comments. Please check.