Proposals for NextAuth 2.0

Proposal for NextAuth 2.0
The following proposal is what is planned for NextAuth 2.0. Some of these features have already made it into 1.5. Others are in progress. It is an active work in progress but there is no fixed ETA yet.
Comments and feedback are welcome.
Updated 29 May, 2018.
Simpler Configuration
The core rationale for NextAuth 2.0 is to make it much simpler to use, so that instead of 3 configuration files all you will need is to use it is to do something like this:
const next = require('next')
const nextAuth = require('next-auth')

require('dotenv').load()

const nextApp = next({
  dir: '.',
  dev: (process.env.NODE_ENV === 'development')
})

nextApp
.prepare()
.then(() => {
  return nextAuth.load(nextApp, {
     serverUrl: process.env.SERVER_URL,
     port: process.env.PORT,
     functions: NextAuth.Functions(process.env.CONNECTION_STRING),
     sessions: NextAuth.Sessions(process.env.CONNECTION_STRING),
     email: {
       from: process.env.EMAIL_FROM,
       host: process.env.EMAIL_SERVER,
       port: process.env.EMAIL_PORT,
       username: process.env.EMAIL_USERNAME,
       password: process.env.EMAIL_PASSWORD
     },
     providers: {
       "Facebook": {
         provider: NextAuth.Facebook,
         id: process.env.FACEBOOK_ID,
         secret: process.env.FACEBOOK_SECRET
       },
       "Twitter": {
         provider: NextAuth.Twitter,
         id: process.env.TWITTER_ID,
         secret: process.env.TWITTER_SECRET
       }
     }
   })
})
.then(response => {
  console.log(`Ready on http://localhost:${response.port}`)
})
.catch(err => {
  console.log('An error occurred, unable to start the server')
  console.log(err)
})

It will include built in support for at least Mongo DB and MySQL and use the connection string to detect database type (e.g. checking if it starts withmongodb:// or mysql://).
It will still be possible to define your own functions to integrate with another database. Having examples for both an SQL and NoSQL database should make it easy to create adapters for other databases.
New Features
Changes to Session Storage and CSRF Tokens
There are some changes to the way session storage will be handled:

The implementation of Cross Site Request Forgery tokens will switch to the Double Submit Cookie method, which does not require a server side session.

A session in a databases will only be created for a user when they log in, to reduce database load - this also helps provide some protection against trivial Denial of Service attacks.

CSRF will be an option, and it will be possible to set it to null or to explicitly pass a method which can be used to disable it on white listed routes if required.

NextAuth Pages

Built in 'white labeled' pages for displaying a sign in dialog and linking/unlinking accounts.

Built in 'white labeled' pages for callbacks, error handling and email token messages.

These will be the default but you will specify your own URLs if you wished:
pages: {
  signin: "/signin",
  callback: "/callback",
  checkEmail: "/check-email",
  error: "/error"
}

## NextAuth Components
We will also expose the components used to make these pages (e.g. <NextAuth.SignInButton/>, <NextAuth.SignOutButton/>), to make it easier to add them to a site.
Going further, a basic page will also be exported as NextAuth.React.Component to automatically add session data to every page if used in place of React.Component when declaring a page. It will otherwise work exactly like a React page in Next.js.
Example
import React from 'react'
import { NextAuth } from 'next-auth'

export default class extends NextAuth.React.Component {
  render() {
    if (this.props.session) {
      return(
        <React.Fragment>

You are logged in as {this.props.session.user.name || this.props.session.user.email}.

          <NextAuth.SignOutButton/>
        </React.Fragment>
        )
    } else {
      return(
        <React.Fragment>

You are not logged in.

          <NextAuth.SignInButtons/>
        </React.Fragment>
      )
    }
  }
}

These components will take options like <NextAuth.SignInButtons className="btn btn-primary"> to allow them to be easily styled. They will be simple HTML elements with perhaps (optional) JavaScript behaviour bound to them.
Built in Database support

Bundled strategies for both session and user databases - including as an in-memory DB, Mongo DB and MySQL.

It will still be possible to define your own methods for other session and database stores (and this will be easier than it is now - so it shouldn't matter which SQL or NoSQL DB you are using).

The session and user database stores will not have to be the same database or even the same type of database.

Internally, the functions might change to make this easier, so that instead of general purpose database methods like update() and insert() they might be named after actions such as createUser(), linkProvider(), unlinkProvider(), generateSigninToken(), etc.
This will mean slightly more functions will need to be defined than in 1.x, but they will be explicit in functionality so that they can be more single purpose and easier to adapt to different databases.
If the database type in the connection string is one of the supported types, it will load the appropriate config, connect (and check the table structure if an SQL database, creating tables and columns as required if they don't existing) then return pre-configured strategy so it "just works" out of the box.
NextAuth will of course need to be updated to only start once the promise returned by NextAuth.Functions() and NextAuth.Sessions() had returned

Provider configuration will be much simpler for common providers.

We'd only bundle support for a few simple commonly used strategies - such as Facebook, Twitter and Google, but you'd still be able to define your own for any oAuth provider - the same way they are already configured for NextAuth.
Optional parameters for each Provider will include:

callback - A URL that can be defined for each provider; this has already been added to 1.x as a requested feature since this was written.
seralize - A function to normalize user objects from third party services.

Additionally, it will be easier to add support for password and/or two factor based authentication. Functionality for this has been added to 1.x but the support for this will improve.
Better NextAuth Email

Built in email templates.

I'd like to include nice looking HTML email templates for sending emails and bundle nodemailer.
This behaviour should of course still be able to be overridden as it is now.
~Bundle NextAuthClient~
~I'd like to expose NextAuthClient directly in NextAuth (as NextAuth.Client) if this can be done simply and cleanly.~
~It will provide a simpler way to use NextAuth and ensure both will be updated easily and were always in sync.~
NextAuth.Client is now already available in 1.x as it made sense to simplify how it was used and didn't require major changes client side.
The bundler for NextAuth.Client may change at some point, as there are some issues with newer webpack releases that mean it no longer generate isomorphic libraries that also run in service workers correctly (so for now we are not using the latest-and-greatest webpack to build it, as older versions work fine for universal apps) but even if we do that shouldn't change how it is used.
Rollup is one option and is much simpler, though it doesn't support Hot Module Replacement (HMR) and that might be a problem.

To clarify, there is no planned release timeframe for 2.0 yet - and 1.x is will continue to see new feature work before 2.0, as some good feature requests for things like localStrategies and other options have come in that are easy to deal with without any breaking API changes required, so they will likely get priority.

Some work has already been done by others to add better database support for 1.5 - specifically MySQL support - and we may just share that in the interim, if we can get it documented, ready to share and they agree.
For 2.0 though, we are thinking of increasing the number of discrete database calls, with the trade off being they do specific things and ultimately requires less code (and simpler code), especially when interacting with SQL databases.
As a result of them being easier to write, it would include built-in support for at least both Mongo DB and MySQL out of the box.
This is an example of the sort of methods a DB driver for NextAuth 2.0 would need to support:
https://github.com/iaincollins/next-auth/blob/version-2.0/src/function/mysql.js
Feedback welcome!

Thanks for the feedback!
I agree it's too complicated as it is, but am very glad for the feedback I've gotten and issues the existing implementation has raised.
I've been focused on making progress on another commercial projects (which uses next-auth) and looking forward to revisiting it for 2.0 soon.

Hi @falleco thank you for asking and for reaching out - and to everyone else for feedback.
After a long period of dormancy - mostly due to the evolving nature of Next.js and Now.sh over the last year - I've picked up work on NextAuth 2.0!

tl;dr Much of this has been done already this week (as of v2.0 beta 10) and the rest is coming soon! Closing this thread, follow the NextAuth 2.0 announcement for updates.


Update Modules “partner_fax”

Automatically generated by Decap CMS

@yajo @florenciafrigieri
@dreispt @sbidoul
My test PR.
I added an image to see how it is render.
Here are my notes :
1. Images / Markdown
I noticed that I cannot add an image if I use the Markdown.  I only can do it with Rich Text.

Is it going to be a problem because the Read me files are in Markdown?

I don't think so because in my understanding, we will not be synchronizing the documentation from the CMS to GtiHub files but only in the other way.  So at first, all readme modules will be synchronized / copied from GitHub to the CMS and then, we will not send the update made from the CMS to GitHub.

Will it be possible to upload images in Markdown / by drag & drop?

2. Name of the PR
I imagine it will be possible to have the PR named following the rules?
Example : [17.0][IMP] name of the module : improve ReadMe
Or will it be necessary?
3. Fields Name of the module + Name
Can we put the 2 fields name in the CMS in "Read only" mode so nobody can change it (voluntarily or not)?

One more thing, it seems that the preview does not show my modifications and when I click on the link, I arrive at the main page, not at the module page.

I noticed that I cannot add an image if I use the Markdown. I only can do it with Rich Text.

Is it going to be a problem because the Read me files are in Markdown?

Not really. The rich text mode itself writes markdown behind the scenes. You can switch to the rich text, add the image, and then go back to markdown if that's what you want to use. Otherwise you can write the code directly in the markdown editor.
In any case, the main use case is to have a rich text editor. If you want to use markdown you are supposed to know what you're doing, more or less.

I don't think so because in my understanding, we will not be synchronizing the documentation from the CMS to GtiHub files but only in the other way.  So at first, all readme modules will be synchronized / copied from GitHub to the CMS and then, we will not send the update made from the CMS to GitHub.

Yep. The READMEs will just point to the docs, so there's nothing to worry about.

Will it be possible to upload images in Markdown / by drag & drop?

That's a limitation from decap-cms itself. You could ask in https://github.com/decaporg/decap-cms directly.
In any case, the media library has its benefits too. I guess that it won't be so hard once you get used to it. It will require a good tutorial for sure.

I imagine it will be possible to have the PR named following the rules? Example : [17.0][IMP] name of the module : improve ReadMe
Or will it be necessary?

I think we should forget about those guidelines for this particular repo.
This is just a wiki that happens to be storing its database in Git. But you don't usually give namely descriptions to changes in other wiki systems.

Can we put the 2 fields name in the CMS in "Read only" mode so nobody can change it (voluntarily or not)?

We can't, because then nobody could add a new module with its name. The reviewer will have to care about that.

One more thing, it seems that the preview does not show my modifications

I could see them:

However it seems it has a bug that doesn't actually render the Markdown into HTML.
I can fix that.

and when I click on the link, I arrive at the main page, not at the module page.

Yep, it's just a new snapshot of the full website, with your changes included. You have to navigate to the page you're changing.
After all, netlify doesn't know if you're pushing the PR from decap-cms or from normal git operations. And in that case, you could be changing more than one page with the same PR.
We would need a nice tutorial too to let reviewers know how to review PRs.

The render problem is fixed in 1c6d34bc0a2b64e973913bce68cec685da34b19f. If you could rebase the PR, you'd get it.

@TumbaoJu I managed to configure this repo so that you have now an "update branch" button that will rebase this branch. Click on it and you will trigger a new build. Once built, you should see the image bug fixed correctly. Would you try please?

Done!


Add timestamp to message

While sending message add timestamp to the message object and display it on UI.

Hi. I can get this done. I have worked with live chat using WebSockets. Please assign me this issue!

@all-contributors please add @abhishek-aa for code.


Add analog literals

C++ has analog literals: http://www.eelis.net/C++/analogliterals.xhtml
Given the LiveScript philosophy of adding syntactic sugar for everything, I suggest analog literals are added to LiveScript.

:(


compilation of third-party OpenCV static libraries succeeded with ubantu, but failed to run.

I build the code on ubantu, this is my binding.gyp file
{
"targets": [{
"target_name": "first",
"sources": [
"./cc/first_nan.cpp"
],
"include_dirs": [
"<!(node -e "require('nan')")",
],
},
{
"target_name": "opencv",
'conditions':[[
"OS=="linux"",{
"libraries": [ "/home/t/opencv/opencv-3.4.2/build/lib/libopencv_world.a" ],
}
]],
"type": "static_library",
"sources": [
"./cc/rotate.cpp"
],
"include_dirs": [
'./cc',
"/home/t/opencv/opencv-3.4.2/build/lib"
]
}]
}
this is run result, i dont konw how to do  plz help me..
thanks
node: symbol lookup error: /home/t/chromosomeServer/build/Release/first.node: undefined symbol: _ZN2cv6String8allocateEm

Closing, not a node-gyp issue. You need to link properly against opencv, just passing the path to the archive isn't sufficient. Look up the -l and -L flags in man cc.


create type 2 (EIP-1559) txs

related to https://github.com/superfluid-finance/superfluid-sentinel/issues/96

first type-2 tx: https://polygonscan.com/tx/0xb6d3cb5ecdeacb2411319f08c11d9066e80540e6a3e1371ea479784f6cf82879
For type-2 txs, we don't need the gasprice up-bidding, but can just set the configured limit for maxFeePerGas.
I've set maxPriorityFeePerGas to a value slightly higher than the web3.js default of 2.5 gwei bcs my gut feeling tells me that may help in situations of sudden demand spike.
Even without bidding, we probably want to leave a tx re-broadcast logic in place if a tx remains pending for too long.
If a chain has EIP-1559 activated can be checked by looking if blocks have a field baseFeePerGas.
Currently, all SF supported chains have it afaik.
Also, we should add logic to not broadcast any tx at all as long as the current baseFee (block.baseFeePerGas) exceeds the sentinel set MAX_GAS_PRICE. If it broadcasts anyway, there's a high chance that it will just remain pending and fail later, while another sentinel with higher limit already did the liquidation.


check-config: Don't check DEVPTS_MULTIPLE_INSTANCES for kernel upper than 4.7

DEVPTS_MULTIPLE_INSTANCES is removed from kernel 4.7, by:
commit eedf265aa003b4781de24cfed40a655a664457e6
devpts: Make each mount of devpts an independent filesystem.
We should skip checking this flag for kernel upper than 4.7.
Signed-off-by: Zhao Lei<EMAIL_ADDRESS>

Does not seem to work with an extraversion suffix on the kernel config, I get WARNING: kernel_version_ge: get config_version failed with kernel 4.4.17-moby.

Hi, justincormack
Thanks for check and report, the script use following head lines in config file
to get its kernel version.

Automatically generated file; DO NOT EDIT.
Linux/x86 4.4.17-moby Kernel Configuration

I modified the kernel version to yours 4.4.17-moby, but had not
reproduced the problem.
Could you paste head lines of your kernel config to help me investigate?
Thanks!

Oddly the config files doesnt have the extraversion
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 4.4.17 Kernel Configuration
#

Hi, justincormack
Thanks four your help.
I paste your config header in my config, and see no error...
Could you run following command in your env?
CONFIG=[path_of_your_config_file]
echo "Config: $CONFIG"
echo "grep result:"
grep '^# Linux/.* Kernel Configuration$' "$CONFIG"
echo "cut retult:"
grep '^# Linux/.* Kernel Configuration$' "$CONFIG" | cut -d' ' -f3
echo "done"
Thanks

Ok, it is an issue that you are running grep on /proc/config.gz, elsewhere it uses zgrep which works. But I don't understand how the script is supposed to work with either compressed and uncompressed configs, as it doesnt seem to check whether the file is compressed or not.

Hi,  justincormack
Thanks for notice.
Patch is updated to support .gz config files.

ping

ping @justincormack PTAL!

LGTM

ping @tianon could you have a quick peek as well? :heart:

There are other places in this script that we're already doing comparisons based on kernel version -- I think they all need to be consistent. :+1:

Hi, @tianon, I hadn't see comparisons based on kernel version in the script, could you tell me where?
Thanks!

@zhaoleidd sorry for the delay. You can find example of versions check in that script by words kernelMajor and kernelMinor. You should use your function there. Thanks!

It's also worth noting that we cannot rely on the .config file comments for scraping the kernel version -- for example, if someone copies their .config from an older kernel and only runs menuconfig but not oldconfig, the comment does not get updated.

Why not just do it as we did for other configs which have the same needs: https://github.com/docker/docker/blob/master/contrib/check-config.sh#L226-L238

Hi, @Hqhq, there are two way in current script to do different check on different version of kernel config:
1: as in https://github.com/docker/docker/blob/master/contrib/check-config.sh#L226-L238
If a config is replaced in new kernel config, we can do check like:
if is_set OLD_CONFIG; then
report_ok
elif is_set NEW_CONFIG; then
report_ok
else
report_ng
fi
But unfortunately in case of current patch, the config was just removed in new kernel,
and we can't distinguish is the config is "removed in new kernel" or "not set in old kernel"
or "not exist in very old kernel".
2: Use "$kernelMajor" and "$kernelMinor" which is already in the script, but they are
get from "uname -r", it is version of current-running-kernel, not config's kernel version.
Supposing we are building a new kernel in a stable linux release, we need to check
is the config file's content fits to kernel version of config file.
btw, some other place using "$kernelMajor" and "$kernelMinor" in this script maybe also
need to be fix.

@zhaoleidd it's a known issue that we're testing the runtime kernel version, but we test other runtime parameters as well (mounted cgroup hierarchy, for example), and the .config comment is not reliably updated (and is the only indication of "version" in the .config file), so that's why we use uname rather than scraping the comment.  The primary use case of this script is for testing the "current" environment for Docker support (and/or diagnosis on why Docker or some particular feature therein might not be working).
Having a function for making kernel version comparisons easier is fine, but it needs to use the existing method of version detection (however flawed -- there isn't really a better solution that will work in all cases).
It might even make sense to still list config values that don't appear to be supported by our current kernel version with a message stating as such so that we get all the same information regardless of kernel version.  Thoughts?

Ping

This already got merged in https://github.com/docker/docker/commit/228ee16df3d738efaf001309370b26561c49edd6
So closing... sorry I didnt notice before this was resolved.
This script is really designed to be used at runtime, for diagnosis, so I think the kernel detection method with uname is fine.


FAILURE_REASON_NO_ROUTE | Cannot send Sats from Zap wallet using Zap Technologies Channel.

Setup wallet and deposited BTC. Open recommended channel (Zap Technologies) and committed some Sats. Paid fast transaction fee, and have 6+ confirmation on chain. Channel is online.
I'm trying to send funds to another Lightning Network wallet (android app called Muun). I generate an invoice and try to send using Zap Wallet but get error:
"Transaction error details
FAILURE_REASON_NO_ROUTE
All possible routes were tried and failed permanently. Or were there no routes to the destination at all."
How can I use Zap to send funds using this channel?
If I cant send funds using this channel, how do I get my Sats back?

LND couldn't route your transaction in this case. Make sure you have some other channels opened to well-connected nodes. Also, on the receiving side you need to have inbound liquidity (i.e., channels open TO you, not FROM you) or else you won't be able to accept payments.

I am also experiencing the exact same issue. I tried to establish new channels and I get the following


add json traversal support.

Trying to figure out what we can do, what we should do, and how this can be scoped and explained.

JSON path syntax is supported by all 3 built-in dialects. So having a type-safe JSON path builder is a no-brainer.
scope->JSON path is supported by MySQL & SQLite, PostgreSQL only supports simple references or indices there.
scope->something->something is only supported by PostgreSQL.
->> is supported by all 3 built-in dialects. Since -> is sometimes "JSON represantation" and not real values, we should only support ->> for now, since it aligns all dialects' outputs.
json_extract(scope, JSON path) is supported by MySQL & SQLite with slight differences in output type, PostgreSQL supports something similiar-ish with jsonb_path_query(scope, JSON path).

Done implementing:

Easy access to JSON traversal via existing eb.ref - simply add ->> or ->>$ operator as 2nd argument and chain away with .key(key) & .at(index) methods.

.select((eb) => eb.ref('nicknames', '->>').at(5).as('sixth_nickname'))
.where((eb) => eb.cmpr(eb.ref('profile', '->>').key('created_at'), '>', now))

Allow creating PostgreSQL (& SQLite) arrow chains (e.g. column->'key'->>0) with ->>, but also classic JSON paths (e.g. column->>'$.key[location]') (MySQL & SQLite) ->>$ in a dialect agnostic way (meaning no specific compiler code).
Keeping it simple with just ->> as JSON arrows  (e.g. no -> operator support), provides alignment across the core dialects as far as what the result looks like at runtime (after JSON parsing or receiving parsed from underlying driver).
in Database interface, define your json columns as objects/arrays or ColumnType with first slot being objects/arrays. Need to make sure users of prisma-kysely & kysely-codegen can override whatever is generated for arrays and json columns with manual interfaces. We also support optional keys (key?: type), the inferred result type would be nullable.

interface Person {
  nicknames: string[],
  profile: {
    created_at: string;
  },
  other_nicknames: ColumnType<string[], string, string>,
  profile: ColumnType<{ created_at: string }, string, string>
}

JSONPathBuilder can allow creating standalone JSON paths in the future, e.g. as arguments of sql json functions. maybe even expose it in ExpressionBuilder?
Some dialects might require a JSON parsing plugin, should we have one in the core? at the very least provide an example for it in a recipe for this.
Should we offer a non-type-safe way to do the same from sql.ref? Might be a low hanging fruit by simply using JSONPathBuilder<any> (haven't checked yet).

I like the idea of a JSON path builder, but I'm not the biggest fan of the jxp('column', '->>', callback) syntax. Seems overly complex. Did you consider something like
jsref('column').key('foo').key('bar').at('baz')

you wouldn't be able to specify the operator, but could that be given as an optional second argument?
jsref('column', '->').key('foo').key('bar').at('baz')

I like the idea of a JSON path builder, but I'm not the biggest fan of the jxp('column', '->>', callback) syntax. Seems overly complex. Did you consider something like
jsref('column').key('foo').key('bar').at('baz')

you wouldn't be able to specify the operator, but could that be given as an optional second argument?
jsref('column', '->').key('foo').key('bar').at('baz')

I'm probably missing some future use cases you had in mind for the jxp function...

Yeah I wasn't feeling jxp because of PostgreSQL. It would force wrapping hell to achieve something like col ->> key ->> key.
I like your suggestion, will play around with it more.

New idea pushed, still rough:
eb.ref('column', '->>').at(0).key('key').as('alias')

Should compile to:

PostgreSQL

"column"->>0->>'key' as "alias"

MySQL

`column`->>'$[0].key' as `alias`

SQLite

"column"->>'$[0].key' as "alias"

Thinking about enhancing WYSIWYG by adding a ->>$ operator option for MySQL/SQLite, and removing dialect specific compilation. 🤔

Looking good thus far, need "more nested" test cases, and typing tests. 😌

Some updates:

unit tests are pretty much done.
array traversal should always be nullable. there's no guarantee an item i exists. we won't support tuples and readonly array literals - that just adds unnecessary type complexity right now.
added .at('last') (supported in MySQL) and .at('#-1') (supported in SQLite) as ways to access items in the end of an array. we also support .at(-1) (supported in PostgreSQL).
in case there's nested traversal in "multi-arrow" syntax, PostgreSQL forces that only the last operator can be ->>, so we'll go with that by default, even though SQLite supports both forms.

Ready for review. 😮💨
Will add more test cases, mainly for usage without ColumnType and usage in non-select clauses.

Should we add tests that this works correctly with the CamelCasePlugin? The nested keys should be mapped depending on the maintainNestedObjectKeys config.

Haven't thought about that one, will try adding these now.

Should we add tests that this works correctly with the CamelCasePlugin? The nested keys should be mapped depending on the maintainNestedObjectKeys config.

Haven't thought about that one, will try adding these now.

Maybe we should merge this first and implement the camelCase stuff as a separate PR? We could release a new version after we get this merged?

Maybe we should merge this first and implement the camelCase stuff as a separate PR? We could release a new version after we get this merged?

Yeah, let's go! 🚀

Documentation in the Kysely docs site for this would be phenomenal!


Add TIRS SSM model for Landsat 8 to the Level 1 packaged metadata

One additional ancillary source needs to be added in the yaml file for LS8 product from the main LPGS log file (landsat-processor.log)
ga-metadata.yaml:
……
ancillary_quality: DEFINITIVE
ancillary:
cpf:
……………………..
access_dt: 2016-05-18 18:13:19
modification_dt: 2014-11-26 13:03:32
checksum_sha1: b59e3585757e2a09937a7b8482786c205354807e
ssm:
name: xxxxxxx
uri: /g/data/v10/eoancillarydata/sensor-specific/LANDSAT8/TIRS-SSM/xxxxxxxxx
…….
And, how do you define the field “ancillary_quality” – I assume that if all ancillary = definitive, then DEFINITIVE?
In LS8 case, ssm may not be DEFINITIVE. We could add “TIRS_SSM_MODEL” (from MTL) in yaml file. If TIRS_SSM_MODEL  =  Preliminary, then ancillary_quality is not DEFINITIVE.
ga-metadata.yaml:
……
ancillary_quality: DEFINITIVE
ancillary:
cpf:
……………………..
access_dt: 2016-05-18 18:13:19
modification_dt: 2014-11-26 13:03:32
checksum_sha1: b59e3585757e2a09937a7b8482786c205354807e
ssm:
name: xxxxxxx
uri: /g/data/v10/eoancillarydata/sensor-specific/LANDSAT8/TIRS-SSM/xxxxxxxxx
And, how do you define the field “ancillary_quality” – I assume that if all ancillary = definitive, then DEFINITIVE?
In LS8 case, ssm may not be DEFINITIVE. We could add “TIRS_SSM_MODEL” (from MTL) in yaml file. If TIRS_SSM_MODEL  =  Preliminary, then ancillary_quality is not DEFINITIVE.

I'm increasingly thinking a single 'ancillary_quality' value is too inflexible, and prone to problems as more things are added in the future (such as this TIRS SSM).
I've instead recorded quality against each ancillary record individually, so that we can decide lazily how to classify the quality as a whole. That existing quality field will still exist in LS5/7 for backwards compatibility, though.
Sound ok?

Sounds good

Implemented in 00d98c9f28dc07e18560f2e10d0d09a61517e980, 84aa8dbd519005eb8a37ac1e91c646cdfd9e87d8, fb85600ef8d0872b06e0aebb98f9fdc626522ada


Runelite weird bug

Please check if your issue is not a duplicate by searching existing issues
Describe the bug
I'm really not sure what I would say is happening with this bug thats why I decided to make my own post about it.
To Reproduce
It starts as soon as I use any of the side plugins.
Expected behavior
https://gyazo.com/eb7c5f6ac6f6db860406d730ca3b789d
Screenshots
https://gyazo.com/eb7c5f6ac6f6db860406d730ca3b789d
Environment (please complete the following information):

OS: Windows 10
RuneLite version: <IP_ADDRESS>
Launcher version: 2.1.3

Additional context
N/A

https://github.com/runelite/runelite/wiki/Disable-Hardware-Acceleration


[add] model for panel data

Thanks for the great list.
I would suggest the following three points:

Synthetic Control Method
This is a relatively traditional econometric approach developed by Abadie. I added it because it was frequently used in causal inference in the public policy field.

Synthetic Difference in Differences
This is a recently published paper. As the name suggests, the model is a successful fusion of "Synthetic Control Method " and "Difference in Differences", which gives the impression of being more sophisticated.

Causal Impact
This model is frequently used in marketing-related fields. Since the idea is a natural extension of the Synthetic Control Method, it is included in the same table.

Thank you.

Thanks a lot for your contribution!


complete assignment1

I have done my homework .
If you find that the second commit is just what first commit missing, use git amend instead.

Hi bro !

I've added  some feature to complete this assignment
Fix all error in coding style that you lead me
Review agian for me bro. Thanks ^^

Hi bro !

Fix coding style again . Help me check it , Thanks ^^


Improve handling of bad requests to the SFAPI

Today if a sub-request to the SFAPI fails in Hydrogen via context.storefront.query, the developer is presented with something like this:
TypeError: SWR in sub-request failed: disturbed
    at consumeBody (/Users/joshlarson/src/github.com/jplhomer/hello-josh/node_modules/undici/lib/fetch/body.js:269:15)
    at consumeBody.next (<anonymous>)
    at Response.text (/Users/joshlarson/src/github.com/jplhomer/hello-josh/node_modules/undici/lib/fetch/body.js:369:24)
    at Response.text (/Users/joshlarson/src/github.com/jplhomer/hello-josh/node_modules/@miniflare/core/src/standards/http.ts:338:38)

This isn't a super great message. It's likely happening because we apply a default SWR cache policy to all requests, and the exception is being caught in there instead of elsewhere.
Ideally, we should display the actual error from SFAPI (e.g. 400 bad token) or something.

Running into a similar error message from a different source. This happens when I input my valid shopify credentials that were working fine for Hydrogen v1.
TypeError: disturbed
    at consumeBody (project_root/node_modules/undici/lib/fetch/body.js:269:15)
    at consumeBody.next ()
    at Response.text (project_root/node_modules/undici/lib/fetch/body.js:369:24)
    at Response.text (project_root/node_modules/@miniflare/core/src/standards/http.ts:338:38)
    at c8 (project_root/node_modules/@shopify/hydrogen/src/routing/redirect.ts:79:24)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at le (project_root/node_modules/@shopify/hydrogen/src/routing/redirect.ts:79:24)
    at d14 (project_root/node_modules/@shopify/hydrogen/src/routing/redirect.ts:79:24)
    at getFeaturedData (project_root/app/routes/($lang)/featured-products.tsx:17:16)
    at loader7 (project_root/app/routes/($lang)/featured-products.tsx:11:15)
    at callRouteLoaderRR (project_root/node_modules/@remix-run/server-runtime/dist/esm/data.js:37:16)
    at callLoaderOrAction (project_root/node_modules/@remix-run/router/router.ts:3067:14)
    at async Promise.all (index 0)
    at loadRouteData (project_root/node_modules/@remix-run/router/router.ts:2732:19)
    at queryImpl (project_root/node_modules/@remix-run/router/router.ts:2519:20)
    at Object.queryRoute (project_root/node_modules/@remix-run/router/router.ts:2459:18)


Round variant not displaying album artwork correctly

Album artwork does not conform to the ellipse of the Round variant. The corners are visible and extend beyond the border.

I believe this issue is intended for the PlayMusic repo


Improve booking Collection

Once the booking is confirmed by the mentor, that time slot for that mentor should be disabled so no new user can book a meeting in the same time slot.

Either Disable or completely remove the button. While you are at it also improve the contrast of the button on hover!
The edits need to made in how we are storing the availability data collection in the backend and then the date-picker component in the front-end.

Hi Rishabh,
I would love to work on this. I have a few questions for you:

Does the timeslots/sessions have to be of exactly 1 hour? Can it be more or less than one hour(example 30 min, 45 min)?

Does the start_hour have to be  perfect 10:00 or 12:00or  23:00 etc. Can the mentor set it to something like 13:15(whenever the functionality is made for mentors to select time)

Currently it looks like the availability of a mentor in a particular day is recurring(meaning if a mentor is available on a monday, then he/she will be available for all the mondays for two months). Is this the intended behavior or do we need a change here as well? Because mentors may not be available for the same day/time for two different weeks.

My current solution would be to store an array of available timeslots for each mentor where an available timeslot will be an object with start_time and end_time (unix time stamps or Date objects with GMT value). Tis will also solve the time conversion problem (https://github.com/Rishabh-malhotraa/Vita/issues/18). What do you think?

Hey Milan, all this was made in just two weeks for Microsoft's hackathon. I did not put much thought into the backend logic, but better late than never, right? :P

Does the timeslots/sessions have to be of exactly 1 hour? Can it be more or less than one hour(example 30 min, 45 min)?

It should either be 30 minutes, 45 minutes, or 1 hour, and the mentor would set this when specifying his/her time preferences(All this validation need to be done on the front-end while requesting timeslots from the user).
Obviously, once both the mentor and mentee are in a video call, it does not really matter how long the session duration is. They can continue the session for as long as they like.
But once the booking is confirmed, we would use this data to create a calendar event, send it to both the Mentor and Mentee an .ics file in the mail. Better even if both mentor and mentee have given calendar access while signup (functionality for all this need to be implemented),  we should directly create an event on Google calendar using the Google Calendar API

Does the start_hour have to be perfect 10:00 or 12:00or  23:00 etc. Can the mentor set it to something like 13:15(whenever the functionality is made for mentors to select time)

start_hour should be a multiple of 15
12:00 12:15 12:30  12:45 should all be valid start_hours which the mentor could specify.

Currently it looks like the availability of a mentor in a particular day is recurring(meaning if a mentor is available on a monday, then he/she will be available for all the mondays for two months). Is this the intended behavior or do we need a change here as well? Because mentors may not be available for the same day/time for two different weeks.

Yes, I would like this to be recurring just like Calendly, I don't want the person to constantly update his timetable, it should ideally be done once and could be edited by the mentor if that time slot does not make sense anymore.
Additionally, whenever a mentee requests a 1-1 session, the mentor would always have the option to propose a new time slot, if the time does not make sense.

Few more improvements I would like to make
I would also like to add functionality to limit the number of sessions per day.
For example, if the mentor has specified only 1 session per day, after a confirmed booking, we should show that entire day as unavailable.
Make a given timeslot as unavailable once it has been booked.
If the mentor has given calendar access, we should automatically block certain additional time slots, if he has an event scheduled during that time.
There should be some extra validation to sanitize the inputs, like start_time should be always before the end_time.
The difference between the start_time and end_time should never exceed 24 hours.
Handling the edge case when converting the time to a different time zone would split available time slots into two days, for example, if a mentor is in the USA west coast, and has available time slots from 10:00 - 14:00, converting that to IST would split this into two different days DAY 1 - > 22:00-> 24:00  Day 2: 0:00 AM - 2:00
These are some which I can think of at the top of my mind, do let me know if you can think of some other edge cases.

My current solution would be to store an array of available timeslots for each mentor where an available timeslot will be an object with start_time and end_time (unix time stamps or Date objects with GMT value). This will also solve the time conversion problem (#18). What do you think?

Epoch time does not make sense since we are storing available time slots based on Day of the week, but I need to do some more research on this, maybe shifting axis to week 1 of epoch work, but I am not sure?
{
  "Monday": [
    {
      "start_time":  Date(),
      "end_time": Date()
    }
  ]
}

One of the flaws of this method would be converting time slots in different time zones would be a pain in the neck because a Monday timeslot for one timezone could be a Tuesday timeslot for another.
I will love to know if there is a more efficient data structure that fits our use case better.
Maybe not store segment available time slots as by days, but just store them in an array, in a normalized way. I would love to know your inputs.

Hi Rishabh,
Sorry for the late reply.
Yes, I agree with you. We can simple store timeslots in an array in normalized way instead of doing it by days. So something like this ->
{
  ...
  "time_slots": [
    {
      "start_time":  Date(),
      "end_time": Date()
    } ,
    {
       "start_time":  Date(),
       "end_time": Date()
    }
  ]
}

Here Date can be an epoch as well. What do you say?

Please add GSSoC'22 label to it and assigned it to me


Adding a shader material to a drawable gives an exception error

when you try to add it to a drawable instead of a drawable model

wdym about Adding a shader material to a drawable ?
You mean in your empty ? or your mesh ?
Does the Sollumz Type of the mesh is "Drawable model" ?

i mean the drawable object, the empty
yes
instead of asking you could test it instead and not wait 6h lol

Reproduced on last main commit


L&S - Billiard Bluffs (trees) art assets

Again easier to think of these as trees as that's an easy way to place them in the world - although these definitely would fit more like boulders in the world :-)
Simple large sphere made out of multiple smaller shaped blocks. Similar to the #541 poker trees, maybe the shapes from there can be used for the billiards too (although we still need the "corner" rounded shapes)
Reference: http://forum.movingblocks.net/attachments/map-png.1021/

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/486363-l-s-billiard-bluffs-trees-art-assets?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5279&utm_medium=issues&utm_source=github).

Moved to https://github.com/Terasology/LightAndShadow/issues/17.


Bump version to 0.0.279

@charliermarsh I think we should merge before releasing https://github.com/astral-sh/ruff/pull/5950


DISTINCT keyword in MS SQL Server throws error

If you can and you've not already worked on it, feel free to assign it to me.

That's fine, Zaahid. I will take care of this. If you have time, please look at the problem with columns/keys we saw on Thursday.
Thanks,
Armenak

Issue was fixed.

This issue is fixed.


New doc for creating and deleting users in SSO admin console

@rgodfrey, Are there limits on the number of users that can be created?
Also, are you aware of any prerequisites for RH-SSO that we should mention? (I can try to track this info down if you don't know offhand)
TIA!

@rgodfrey, Thanks for the review! Agree completely with those changes (I thought of product name part after I submitted the PR) and will make the changes

Per Rob G., there are not any enforced limits on the number of users that can be created using this method.


[release-1.14] use custom merge logic for ProxyConfig

Please provide a description of this PR:
Fix #41111

@fatedier: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

integ-security_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-security

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

integ-security_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-security

release-test_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test release-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

integ-security_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-security

release-test_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test release-test

integ-ipv6_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-ipv6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

integ-security_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-security

release-test_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test release-test

integ-ipv6_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@fatedier: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-telemetry_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-telemetry

integ-operator-controller_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-operator-controller

unit-tests_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test unit-tests

integ-security_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-security

release-test_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test release-test

integ-ipv6_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-ipv6

integ-pilot-istiodremote_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test integ-pilot-istiodremote

lint_istio_release-1.14
75197e593f64f9b2e9e1fbb9c011e79a27a7914a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


New release for Xcode6.3 & cocoapods?

Latest Pod is not compiling in Xcode 6.3

Using pod from git is a valid workaround :
pod 'PKHUD', :git => "https://github.com/pkluz/PKHUD.git"

Any news about a future update?

Bump :)
@pkluz

:+1:

+1

Any news for a future bump up?
https://github.com/pkluz/PKHUD/issues/32#issuecomment-97021458 seems to work till then..


Install RequireJsNet.ResxToJs using NuGet is not possible

Hello, I am getting an issue trying to install RequireJsNet.ResxToJs using NuGet.
VS 2015, version of RequireJsNet.ResxToJs 2.0.8
Severity	Code	Description	Project	File	Line	Suppression State
Error		'.', hexadecimal value 0x00, is an invalid character. Line 1, position 1.			0
Screenshot https://gyazo.com/c371ac1d035b22d9af5e72b6a5b353b4

I've tested this with the newest version 2.2 and it's working, please try to update NuGet and Vs.NET


zt-attachments and zotero-key, Does them exist by default?

in the zt-field.eta, I didn't configure these two, but they exist

I think, its not configurable because plugin has one complete template that we can't edit. We can just change the available .eta files.

Is there any way to delete the two fields? I don't need it at all.


Error Handling

Start breaking things so the errors pop up and the whole thing doesn't crash.

I've had this running upwards of a month straight with no hiccups, so I'll close this overarching handling issue.


Enhancing the UI and color combination of homepage

I've updated the UI of the Homepage and have done the following changes:

- I've corrected the color of the div below the about us section in homepage, and have placed it instead inside the pet-cards section as a separate element.

- I've enhanced the size of several headings in homepage and added the antialiasing and smootherning effects. Also, some headings, such as the "About Us" had **hover:underline** property as default which wasn't functioning. I've fixed that and replaced the underline with overline, which gives much better view.

- I've also correct the colors of buttons and other elements in the footer section of the index page.

Please mention issue number

Please mention issue number

Hi @akshitagupta15june I'm sorry for this, I've added the issue just now. Please have a look! Thank you!


‘Running fzf installer ...’ show a while but fzf.zip hasn't been download finished

Hello,
Several months ago, I have made a pull request #1845 which create a file which name is install.ps1 to download fzf.zip automatically at Windows system.
Not recently but also before, I have found 'Running fzf installer ...' will show a while but actual fzf.zip hasn't been download finished yet. I have look into the folder %temp%，the file fzf.zip will be download partly and then will be deleted.
It seems like the function fzf#install() has only been called in a short time.

Because if I use powershell windows to directly excute the following commands:
$url = "https://github.com/junegunn/fzf-bin/releases/download/0.21.1/fzf-0.21.1-windows_amd64.zip"
$temp = $temp=$env:TMP + "\fzf.zip"
(New-Object Net.WebClient).DownloadFile($url, $ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath("$temp"))
The file fzf.zip will be download successful inside %temp% folder. So that I think should be the problem from plugin\fzf.vim.  Could you help to check this issue?

Hello,
 Today I try to directly use the command "powershell -ExecutionPolicy Bypass -file install.ps1", and got the following issue at my laptop,  there is one error which said "Error: Access is denied". But no any notice when this error actual happen if invoke install.ps1 from fzf.vim's function fzf#install.

  So the issue from fzf.vim should there is no error notice when error actual happen, another issue should be caused by my laptop environment which I have to solved it by myself.

Can you fix the formatting of your post? It's hard to read. Normal paragraphs should not start with spaces. And see https://help.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax#quoting-code to learn how to format code blocks.

@junegunn , I have just fixed the issues via modify the install.ps1 which is created by my previous pull request. I will make a new pull request when I have time.

https://github.com/junegunn/fzf/commit/9d7480ae3c109358ea0979626c6c9f68c79111c8#diff-24d9d57e35df5afce7890f2400917919R137
script is nnot escaped for the current shell.


Rolling plots improvements

I'm trying to improve on the CPU usage for the rolling plots and made a number of improvements, though it's not perfect yet:

Fixed a bug with closing the paths in EZPlot, and made it a little more memory efficient, and no longer needing write access to the data buffers being passed to it.
Trigger all drawing directly from the Csound callbacks, which actually makes for a faster scrolling plot and saves having to manage locks.
Allow to specify an inspectable property to set the refresh rate for these plots, in an effort to gain control over how often the drawRect: method gets called.
Also another little tweak to the iOS run script.

I think it's obvious that the EZPlot drawing code is woefully inefficient as is - it tries to draw a lot more line segments that are really needed (one for each sample in the buffer, two if you include the mirrors). So that takes a lot of CPU to do very little visible to the user. I'll try to improve on this tomorrow...

The CPU usage is still high with rolling histrory of 2048 hardcoded maybe we just need to expose this length to be easily changed in IBDesginable, etc.

Yeah, we could do that but I'm gonna take a shot at improving the way the drawing is done here. That's the crux of the issue - for every redraw, it draws thousands of line segments, many of which will never be visible. Maybe we can even have some kind of bitmap cache so that only the new samples are drawn.


filters/core - augment resource count filter to check for percentage of resources affected

In most cases restricting the number of resources affected isn't viable when managing multiple AWS accounts as the number of resources varies across accounts. Updating or adding a new filter similar to resource-count would be useful to limit the percentage of resources affected.
Proposed syntax:
policies:
  - name: s3-limit-impact
    resource: s3
    filters:
      - type: resource-percentage
        percentage: 0.5
    actions:
      - type: delete

custodian.filters.WARNING Resource Percentage 100% - 1 of 1 resources exceeds 50%, exiting.

incidentally done as a top level policy attribute to match existing limit, filters don't really have access to the population count, just the filtered set. also given its safety belt, its nicer define outside of the policy syntax. so new proposed syntax is
policies:
  - name: s3-limit-impact
    resource: s3
    max-resources-percentage: 50
    actions:
      - type: delete

which will bail if more than 50 percent of the total resources in the account will be affected.


AttributeError: 'Units' object has no attribute 'noqueue'

when it is in the 0.12，the code is ok.
when it is in the 4.11，the code cannot work.
AttributeError: 'Units' object has no attribute 'noqueue'
ERROR:sc2.main:Error: 'Units' object has no attribute 'noqueue'
ERROR:sc2.main:Resigning due to previous error
--- on_end called ---
Result.Defeat
INFO:root:Result for player 1 - Bot SentdeBot(Protoss): Defeat

I think you mixed up the pysc2 and python-sc2 (from this repo https://github.com/Dentosal/python-sc2) libraries. This is the repository of the library from deepmind pysc2. Your code is not related to it.


Fixed #30910 -- Added system check to warn on duplicate check constraints.

https://code.djangoproject.com/ticket/30910

Closing as per ticket. Thanks all.


bot menu in Microsoft Teams are Not support on mobile app

This is very bad user experience for mobile

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

ID: f73ba47e-c894-2751-cb58-0b6d8d1c59f2
Version Independent ID: 4b88ea6f-86fa-c99f-4c6f-3dddb2bf5739
Content: Add a bot menu - Teams
Content Source: msteams-platform/concepts/bots/bots-menus.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

@best0032001 This is something we are working on but do not have a timeline to share.


Update express-middleware.js

prom-client returns Promise.  Need to handle promise in express middleware.
Resolves #61

Found this issue today when tried to upgrade prom-client.

Yea, I'm using my own version of prom client now with express.  If someone ones to pick this up feel free, I'm going to close this.

That's the spirit!
https://github.com/PayU/prometheus-api-metrics/pull/65/files


Fix-opening-closing

Fix opening and closing operation

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 46.54%. Comparing base (5c32a1a) to head (f652a8e).

Files with missing lines
Patch %
Lines

clic/src/tier2/opening.cpp
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #397   +/-   ##
=======================================
  Coverage   46.54%   46.54%
=======================================
  Files         199      199
  Lines        3848     3848
  Branches     1767     1767
=======================================
  Hits         1791     1791
  Misses        692      692
  Partials     1365     1365

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Run file

This creates the run file.
Standard usage would be
python run.py -i sources.json -o path/to/output/folder -ca
Where -ca stands for copy and convert audio (maybe it should be called caca?)
Another option is -gas -> generate audio symlinks, which can be used when the source audio is available and already .wav
This will

Generate the folder structure
Convert all .pdf and .pptx to txt and place at the correct place
Convert all audio to .wav and palce at the correct place
Standardize the audio and text names with the help of a mappings file.

The output from a test source has been reviewed and gotten thumbs up from asr-person.

When running run.py without a specific sources.json file, this is what happens. It stops in a random place at least to me a casual viewer. This is why I'm not super for it unless it have been instructions or errors:
(python3-venv) judyfong@terra:speech-corpora-toolkit$ srun python3 run.py
srun: job 128271 queued and waiting for resources
srun: job 128271 has been allocated resources
Traceback (most recent call last):
  File "/home/staff/judyfong/repos/speech-corpora-toolkit/run.py", line 364, in <module>
    main()
  File "/home/staff/judyfong/repos/speech-corpora-toolkit/run.py", line 334, in main
    sources = source_handler.get_sources()
  File "/home/staff/judyfong/repos/speech-corpora-toolkit/source_handler/handler.py", line 128, in get_sources
    mapping_file = source[Headers.MAPPING_FILE]
KeyError: 'mapping_file'

Also there is no such thing as a source.url only a source.rss_feed_url. The error message should also make it clear it's the RSS feed url is missing too so the user of the script knows what's wrong.
As a feature for the run script it should be possible to automatically delete existing output directories if the user wishes with a Yes or No command. I'll put this as an issue since it's a feature and not a bug.

Color me convinced that the "test_data.json" is not suitable as a default input. And since the no suitable data is supplied, then we should require a proper input.

Also there is no such thing as a source.url only a source.rss_feed_url. The error message should also make it clear it's the RSS feed url is missing too so the user of the script knows what's wrong.

This needs to be addressed @staffanru

Cool, I've changed the warning message and attribute checked.  Also updated the initial text in the file since it was no longer correct.


draft request for error handling with expected

I'm opening this for us to discuss.

+1+1+1+1+1+1+1

7


Configurable Microsoft login endpoints

Hi - SSOReady currently has this hardcoded Microsoft login endpoint:
  const microsoftRedirectUri = new URL(
    "https://login.microsoftonline.com/common/oauth2/v2.0/authorize",
  );

Some high-security environments have a different endpoints such as login.microsoftonline.us and login.microsoftonline.mil.
Could SSOReady make the Microsoft endpoint (or at least the TLD) configurable?

Will look into it!

@JohnCMoon Are you aware of any alternative Microsoft OAuth servers I could use than login.microsoftonline.com? It seems like login.microsoftonline.us is limited to GCC High / DoD, and it's not clear to me that I would be able to test with it.
Alternatively, I can do one of the following:

Just put up an optimistic PR that assumes the hostname of a Microsoft OAuth server is as interchangeable as I might hope. You can then try running the result yourself against an alternative hostname. I don't love putting up Docker images that I can't fully test, but in this case the risk is pretty limited. I can revert if the change fails or if I don't hear back.
We can work on this together offline. This would be pretty similar to option (1), but instead of me publishing Docker images that you pull down and test, you build them locally and test. If it works, I'll publish them.

Either option presumes that you have access to GCC High / DoD. But I'm guessing you wouldn't ask if you didn't. I defer to your judgement here.

I agree it's unlikely there's an open .us endpoint you could use outside of an enterprise that has access already.
I think of the options above, number 1 would make the most sense to me. Especially if it's just an optional environment variable like MICROSOFT_OAUTH_LOGIN_ENDPOINT or something like that.
If you like, I'd be happy to test the PR before merging. I'm fine to build the docker images myself.

I've pushed up a temporary modified build of the ssoready-app image at ulysse/ssoready-tmp:ssoready-90-app on hub.docker.io. That image accepts a new env var: APP_MICROSOFT_OAUTH_AUTHORIZE_URL. Functionally, the default value for that new setting is https://login.microsoftonline.com/common/oauth2/v2.0/authorize. I think that's all we need here, everything else is configurable?
You'll need to create a new OAuth client in order to test this. If that test works for you, I'll put up and merge a PR to mainline that functionality.

Thanks Ulysse - I've been swamped the last few days but will hopefully get a chance to test this week.

Sounds good! No rush.

@JohnCMoon, you reckon you'll get the chance to try this out at some point?
Definitely no obligation / expectations here, obviously. Just curious.

Hi @ucarion, thanks for the patience! I'm finally getting around to testing this out (had a kid in the interim!). I tried running your image, but looks like it's an ARM64 image:
The requested image's platform (linux/arm64) does not match the detected host platform (linux/amd64/v3)

I don't have access to an ARM64 dev platform... do you think you could provide an x86 image (or a branch I could build)?

Sorry, my bad! I'm building these artifacts locally, and defaults are making everything happen on arm64 unless I remember to build for a different platform. Try ucarion/ssoready-tmp:ssoready-90-app-bis (note the username changes from ulysse to ucarion versus my last suggestion).
Also, the code change in question is up on this draft PR: https://github.com/ssoready/ssoready/pull/137

Thank you - it looks like that works properly when I use https://login.microsoftonline.us/common/oauth2/v2.0/authorize! It asks for permissions and redirects to the callback URI as expected.

Excellent! I'm going to move forward with #137. Glad it's working for you.

Oh and mazel tov, @JohnCMoon!


CSCETSIN-558: Fix issue with Qvain Light button.

The issue is only due to mistake in fixing issues in test.
Removed the import for the separator because it should not be used.
No side effects.

The problem should be resolved when merging to test.


Improve the release process for Java

Okay! So we definitely need to improve and simplify the release process. Me and @pselle have been discussing this on Slack and I definitely feel that we both feel that the release process is too complicated. Some of the bad points:

Before the release we have to update the JavaDocs/Site and correct IOpipeConstants.
It is not automatic and requires that we run a script to release locally and with the proper environment variables.
The build had failed today and it created a tag which required CircleCI to clear the repository cache so CircleCI no longer saw that tag, we also were not able to release a different version because we have to release our SNAPSHOT version.

Ideally the best solution would be one of these:

Tag the release where the build system picks that up and performs a release from it.
Modify a single file or similar which the build system picks up and performs a release from it.

It should be done to make it work on CircleCI 2.0 since 1.0 is very soon near end of life (there is issue #38).
If a release cannot be made then it should back off and not try to modify repository again and push anything that cannot be reverted. Cancelled or failed releases should not cause the repository to get stuck like it did before with the tag issue.
I think for safety if we can, we can clone the repository to a temporary directory and perform the release work there if we make any commits. Then if the release worked then push the commits to master so that way the cached repository does not get messed up, it should check out hopefully. Maybe if there are multiple commits that would be made, maybe we can just have them squashed into a single commit.
I think one thing we can do automatically is that perhaps we can split off the JavaDocs and instead put that into another repository or a non-repository location (iopipe.com?). Essentially have a hook that when there is a new commit to master it runs the JavaDoc and site build and stores that. That way we do not need to run commits and the JavaDoc would always be up to date on master. If we want to go a step further the script could also mirror tags in the main repository for releases if that is important anyway. At least then we would not have to worry about running the JavaDoc ever and having that complicate pulling and the release process.
This message is already pretty long so I will put this down for now and add another reply following this.

Okay for this, I definitely want to split off the Maven Site/JavaDoc and move it into another repository.

Well, the JavaDocs clutter the repository and they are only updated before every release so they are quite static. It is nice to have the JavaDocs available but they should not be in this repository.
The optimal solution would for them to be at say: https://iopipe.com/javadoc, which would be updated per release.
But I am all for dropping the docs from the repository.

Ok, we can drop them if they're making Circle 2.0/release improvements complicated. They're still of course, user-generatable

The Java release process could be further improved by having a setup where we only need to tag a release in GitHib. For now CircleCI 2.0 support is going to be pushed in so that way it is there because we do have a deadline on it.
See:

https://github.com/iopipe/iopipe-java/pull/92#issuecomment-402829699
https://github.com/iopipe/iopipe-java/pull/92#issuecomment-402845835
https://github.com/iopipe/iopipe-java/pull/92#issuecomment-403853778
https://github.com/iopipe/iopipe-java/pull/92#issuecomment-403953074

Moved this to Release 1.9.0, for the logging plugin going to take up the opportunity to get this done for a small project (a logger plugin plugin), then when it works adapt it to this repository.

Moved this to the 1.10.0 release since there will not be enough time for this and it is too risky to hold off on a release when it is ready to go out.

Update, since working on the logger adapters I have figured out how to do this with the minimal set of changes. Apart from changing the code there needs to be a way to store the version number in a resource so that the constants can be read and reported to IOpipe accordingly for the correct agent version.


Nothing happens

When I issue a command, eg ".ls" -- I get nothing. Is there some way to view logs or some such?
I am using alfred 3 and iterm 3

Is your iTerm.app stored in your Applications folder? I was in your situation until I realized I never moved the app from my Downloads directory. The script should work as-is if you move iTerm.app into /Applications, or you can modify the script by replacing every instance of \":Applications:iTerm.app\" with \"iTerm\", which worked fine for me with iTerm.app in ~/Downloads

I have this same problem Iterm 2 version 3.0.4. Doesn't do anything.

If you're using iTerm 2 make sure to rename your application to iTerm from "iTerm 2", or change the script to call "iTerm\ 2"

@Geostant, you are correct. Actually when you download iTerm the binary (as far as I have always tested) will only be called 'iTerm'. What I have seen happen most often, is the when an old/existing iTerm binary exists in the extracted location (usually Downloads), MacOS automagically appends a 2 to the binary (making it look like 'iTerm 2') which hence stops the script from working.
See for example here:

Then when you extract a second time:

And if you were to keep going:

So the script itself, relies on the binary simply being called 'iTerm' which is the default name of the binary, permitting it is extracted into a folder where no such binary called 'iTerm' already exists.
Cheers,
Stuart

@stuartcryan .......Ha ha ha :)
I was living in a lie all my life thinking that I actually have iTerm and iTerm 2 (which are different)
That clears a lot 👍

@geostant No worries, it seems to come up really often, I might have to throw something on the front page for it.
It is an unfortunate quirk that will hopefully resolve itself as more people become aware (fingers crossed.

$ cd /Applications
$ ln -s iTerm\ 2.app iTerm.app

@geostant Thanks! Worked!
Although I do suggest to change it in the script. Stays synced with alfred when you move to new machines or even export your configs with alfred. You might actually forget to rename the iTerm2 app:)

Hello everyone,
Stuart no longer has the time to maintain these scripts, and as such has been kind enough to transfer the repository to me. I’ve shortened the code, made it always open a command in a new iTerm tab, and removed support for older iTerm version.
You might know me as vitor from the Alfred Forums or if you’ve ever contributed to Homebrew Cask.
I’m reviewing issues and pull requests right now, so apologies if you’ve received this message more than once.
If I close an issue with a problem that still occurs in the new version, please open a new issue.
Try the new script.


Never use !important in library css

You set the min-height of the button with an important flag. bad practice. solid directive though.

Hey @kyleicebreaker,
Yeah I pretty much agree. At that time, it was a compromise between my lousy CSS knowledge + deadline of the project which require that directive.


notebook editors not rendering correctly

Steps to Reproduce:

open a notebook
:bug: cells are not rendered correctly

TypeError: Cannot read properties of undefined (reading 'minimapWidth')
    at EditorScrollbar._setLayout (editorScrollbar.ts:119:80)
    at new EditorScrollbar (editorScrollbar.ts:71:8)
    at new View (view.ts:161:21)
    at CodeEditorWidget._createView (codeEditorWidget.ts:1861:16)
    at CodeEditorWidget._attachModel (codeEditorWidget.ts:1763:36)
    at CodeEditorWidget.setModel (codeEditorWidget.ts:498:9)
    at ReplEditor.setInput (replEditor.ts:443:26)
    at async EditorPanes.doSetInput (editorPanes.ts:449:4)
    at async EditorPanes.doOpenEditor (editorPanes.ts:255:34)
    at async EditorPanes.openEditor (editorPanes.ts:132:11)

seems fixed now


extension in the Utils.swift should be marked as public

extensions and methods in Utils.swift should be marked as public so you don't have to repeat in demo project.

This is something that was considered. The reason why we are not doing it is because exporting these helper methods might cause conflict if you use libraries like SwifterSwift. Feel free to grab the file and put it into your own projects. or include a helper library like SwifterSwift


Storage identification functions

[x] idToChunks(id: number): Array
[x] idToPath(id: number): string
[ ] pathToId(path: string): number

See https://github.com/metarhia/common/pull/146 @SemenchenkoVitaliy here is two function to convert identifier to storage key, you can implement third one.


chore(deps): update containernetworking/azure-cns docker tag to v1.6.0

This PR contains the following updates:

Package
Update
Change

containernetworking/azure-cns
minor
v1.4.52 -> v1.6.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2566

Relevant Lines:
3613

💛  - Coveralls

Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (v1.6.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


How to get object in response body in autogenerated swagger.json file

The method @requestBody has a String parameter contents which I am converting into object but while generating the swagger.json it is converting it into String as type. So, what is the proper annotation for that?
@RequestMapping(value = "/{keyId}/{id}/content", method = RequestMethod.POST)
    @ResponseBody
    @ApiOperation(value = "")
    public Model save(@PathVariable("keyId") String keyId,
                              @PathVariable("id") String id,
                              @RequestBody String contents) {
            ObjectMapper om = new ObjectMapper();
            contents = JsonSanitizer.sanitize(contents);
            SaveFruitModel payload = om.readValue(contents, SaveFruitModel.class);
}

"post" : {
        "tags" : [ "Model" ],
        "summary" : "",
        "description" : "",
        "operationId" : "save",
        "parameters" : [ {
          "name" : "keyId",
          "in" : "path",
          "required" : true,
          "type" : "string"
        }, {
          "name" : "id",
          "in" : "path",
          "required" : true,
          "type" : "string"
        }, {
          "in" : "body",
          "name" : "body",
          "required" : false,
          "schema" : {
            "type" : "string"
          }
        } ],

Here I am getting "type":"string" under schema but I want here the type object or the class name so what is the proper annotations for this.

I think there is another issue that addresses this problem. Will update the number when I find it


VM: String.== inlining and code issues

_OneByteString.== is often inlined, sometimes leading to slower code.
E.g. in dart2js, *SourceLocation.== calls *Uri.==
*Uri.== inlines calls to _OneByteString.==, inlining one step, leaving a call to _StringBase.==
class _OneByteString extends _StringBase implements String {
  ...
  bool operator ==(Object other) {
    return super == other;
  }

_StringBase.== has worse code that _OneByteString.== because (1) there is no intrinsifier (2) _StringBase.== is polymorphic in both receiver and argument (_OneByteString/_TwoByteString), so each iteration of the code unit comparison loop has a dispatch on each string type.

In Dartium, the code in the _StringBase.== loop is much worse.  Each call to  other.codeUnitAt(i) has a 4-way dispatch to four calls to _StringBase.codeUnitAt. I'm not sure why these are not lowered to indexed load instructions.
I extended the intrinsifier for _StringBase.codeUnitAt to handle external strings (https://chromiumcodereview.appspot.com/1868323002/).
I ran a table sorting workload on Dartium.
The change eliminates the 11% of time spent in Native String_codeUnitAt and total ticks by 13%.
Open to discussion, but what I think should be done:

[ ] Extend intrinsifiers for _StringBase.codeUnitAt to cover all kinds of string (all architectures).

[ ] Fully intrinsify String.==

[ ] Understand why the crazy 4-way dispatch above happens and fix it (either generate indexed loads or just call _StringBase.codeUnitAt once. I have found this pattern inlined up the call chain into ~20 callers)

[ ] Revisit the  super == other definitions on subclasses. Most strings can be found not-equal on the basis of length without knowing the kind of string. Perhaps the == operation can be factored into a type and length test that gets inlined and an intrinsified body test that is not inlined.

This is the CL I used to get the 11% speedup: https://chromiumcodereview.appspot.com/1868323002/
While this is probably worthwhile on its own, it does seem like a symptom of a problem with ==.

There seems to be an underlying issue with inlining. I'll take a look.
Independent of that, I think the intrinsic code would be good to have.

Re intrinsics: I uploaded https://codereview.chromium.org/1961393002/ which handles all string types for codeUnitAt.
@rakudrama How can I test if I also get the reported 11% speedup?

Closing this as the original biggest performance bottleneck (runtime call) has been fixed.


Adding pattern45.c

Related Issue
Closes: #166
Describe the changes you've made ✍
Hey Vishal, Ive added the c version of pattern 45 to the appropriate folder.
Screenshots (if any) 📸

oh my bad i didnt see that one, one second.


Explore Slab and/or de-duplicating Vertex in graph

Vertex is bigger than one pointer.

Did not produce a significant perf win.


Conformance: remove labels from junit reporter output

The junit conformance reports now include labels by default that break the web site rendering. Rather than complicate the rendering with label parsers, this stops them from being included.

@jdolitsky, the other option I considered was updating your go-junit parser to separate labels from the test name.


Store note in secure temp while editing

Instead temporarily store the note inside RAM.

@bndw this also slightly changes the behavior:
We no longer check the return error of os.Remove (which is good imo, it shouldn't fail to save the note if it can't remove the temp file)

This looks cool- can you elaborate on your license choice and implications/expectations of pick using securetemp?

After chatting offline it sounds like we're ok on the licensing concerns. If you resolve the conflict I'll gladly merge.

Rebased. I have also moved the library to my own go-gettable server. This required a change to our Makefile, as it wasn't properly handling 2-part URLs (domain/name/project vs. domain/project)

Sounds good (since we're committing the vendor folder, hosting from your own server is OK with me)


[ERR_MODULE_NOT_FOUND] [ESM] Vite doesn't bundle internal dependencies

Describe the bug
With ESM, the electron-squirrel-startup dependency can't be found if it's in dependencies (it works if I move it into devDependencies):

require.resolve (Node < 20.6.0) example; src/main.ts file:
import { createRequire } from 'node:module'
import { fileURLToPath } from 'node:url'

const require = createRequire(import.meta.url)
const __dirname = path.dirname(fileURLToPath(import.meta.url))

try {
  // Handle creating/removing shortcuts on Windows when installing/uninstalling.
  require.resolve('electron-squirrel-startup/package.json')
  // OR require.resolve('electron-squirrel-startup/package.json', { paths: [__dirname] })
  app.quit()
} catch (error) {
  // Ignore
  console.log('Ignore error: ', error)
}

Console output:
  Ignore error:  Error: Cannot find module 'electron-squirrel-startup/package.json'
  Require stack:
  - C:\template-electron-vite\.vite\build\main.js
      at Module._resolveFilename (node:internal/modules/cjs/loader:1152:15)
      at s._resolveFilename (node:electron/js2c/browser_init:2:120699)
      at Function.resolve (node:internal/modules/helpers:190:19)
      at file:///C:/template-electron-vite/.vite/build/main.js:8:12
      at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
      at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
      at async loadApplicationPackage (file:///C:/template-electron-vite/.yarn/unplugged/electron-npm-31.0.0-df97707901/node_modules/electron/dist/resources/default_app.asar/main.js:129:9)
      at async file:///C:/template-electron-vite/.yarn/unplugged/electron-npm-31.0.0-df97707901/node_modules/electron/dist/resources/default_app.asar/main.js:241:9 {
    code: 'MODULE_NOT_FOUND',
    requireStack: [ 'C:\\template-electron-vite\\.vite\\build\\main.js' ]
  }

import.meta.resolve (Node.js >= 20.6.0) example; src/main.ts file:
try {
  // Handle creating/removing shortcuts on Windows when installing/uninstalling.
  import.meta.resolve('electron-squirrel-startup/package.json')
  app.quit()
} catch (error) {
  // Ignore
  console.log('Ignore error: ', error)
}

Console output:
Ignore error:  Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'electron-squirrel-startup' imported from C:\template-electron-vite\.vite\build\main.js
    at packageResolve (node:internal/modules/esm/resolve:861:9)
    at moduleResolve (node:internal/modules/esm/resolve:934:18)
    at defaultResolve (node:internal/modules/esm/resolve:1164:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:365:17)
    at Object.resolve (node:internal/modules/esm/initialize_import_meta:30:25)
    at file:///C:/template-electron-vite/.vite/build/main.js:6:15
    at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async loadApplicationPackage (file:///C:/template-electron-vite/.yarn/unplugged/electron-npm-31.0.0-df97707901/node_modules/electron/dist/resources/default_app.asar/main.js:129:9) {
  code: 'ERR_MODULE_NOT_FOUND'
}

I did a try with other dependencies such as react and solid-js.
Stack
Electron Forge + Electron + Vite + ESM + Plug'n'Play (PnP) + Typescript
Reproduction
https://github.com/rtritto/template-electron-vite
Steps to reproduce

git clone https://github.com/rtritto/template-electron-vite.git
cd template-electron-vite
yarn
yarn start

System Info
System:
    OS: Windows 11
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.3.0 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium 126
    Internet Explorer: 11

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

FYI @merceyz

Is this specific to the electron setup? It feels like it has different requirements for dependency handling, which Vite doesn't have an opinion about. I think you should report this upstream.


Experimental cloud operations client

What was changed

Added client.CloudOperationsClient

Only one method for now, CloudService(), but has room for high-level wrappers if we ever want them

Added client.DialCloudOperationsClient() and client.CloudOperationsClientOptions
Added integration test as just a smoke test to confirm cloud client works

(was blocked by https://github.com/temporalio/api/pull/378, but now updated)

This PR superseded this issue https://github.com/temporalio/sdk-go/issues/1172 correct?

Yes, closing that one now.

Updated API version. @anekkanti - can you review?

I think we also should make samples for each SDK showing how to use the cloud API

CI can't do the cloud test from forks because it requires secrets. I am going to close this and push to a local branch so the cloud test will run.


Make bad disk detection more robust

-Report disk I/O failure synchronously.
-Fix a signed/unsigned bug when checking disk I/O result. -Rename a couple of symbols for clarity.

@moonchen This has merge conflicts, probably because of #10269 ? Can you make a branch PR for 9.2.x please?

@moonchen This has merge conflicts, probably because of #10269 ? Can you make a branch PR for 9.2.x please?

Created: #10625


TR-OPEN "Getting Started", Introducing Open Ethical Committee Permissions as an early first step of Open Science

Project info
Title:
TR_OPEN "getting started", Introducing Open Ethical Commitee Permissions as a first early step of open science
Project lead:
Maria Geraldine Veldhuizen, Twitter: @margaveldhuizen Mattermost: @maria_veldhuizen
Project collaborators:
Melvin Selim Atay, Twitter: @i_am_mel_dev , Mattermost: @selimatay
Registered Brainhack Global 2020 Event:
Brainhack Ankara, "Hello world!"
Project Description:
Brainhack Ankara Project For Introducing Open Ethical Committee Permissions as an introductory step of open science. Goal is to create a resource for early career researchers in Turkey to start public sharing data. We would be compiling examples for applications to ethical committees, examples of language in informed consent, list of universities and ethical committees that have approved public data sharing, resources and links to relevant regulations.
To start we are going to learn and brainstorm with the experts in the field of data  privacy and sharing.
We know that Open Brain Consent has done tremendous job on opening up the practices for data collection for ethical committees. There is  a Turkish Translation available for data user agreement and ultimate GDPR which would be useful to anyone who needs them. Establishing applicable practices providing local resources forming a consensus on language, style necessary tools and  establishing the routes are also necessary for applicable solutions. That is why we are opening this project as a first local step for open science.
Data to use:
We would be compiling the local resources and example procedures which would lead more open data collection procedures locally.
Link to project repository/sources:
https://github.com/brainhack-ankara/TR-OPEN_getting-started
Goals for Brainhack Global 2020:
Provide a simple website with an understandable basic concepts. This goal may or may not meet within the time range of Brainhack Global but that is the ultimate goal of the project.
Good first issues:

You can join us as translators, preferably [EN/TR-TR/EN].
You can share your schools / institutions / work places ethical committee examples and we can brainstorm together how to provide a way for open data collection practices.

Skills:
Reading, writing and translating in Turkish.
We are also open to anyone who wants to experiment on git and simple website making

Tools/Software/Methods to Use:
We would be using git, and .md documents and probably would be in need  providing of nice visuals of tabular data for the future which may be used to support the claims of the researcher who may need ethical committee approval.

Communication channels:
TR-Open "getting started" mattermost channel
Video channel: Our jistsi info is at  the mattermost
Project labels
guideline development:
ethical committee, etik kurul, documentation, brainstorming, community building, bhg:ankara

I'm going to hashtag all of the labels I need my project to be indexed in:
guideline development:
#ethicalcommittee, #etikkurul, #documentation, #brainstorming, #community building

Project labels

Type of project:
documentation

Project development status:
#0_concept_no_content,

Topic of the project:
Introducing Open Ethical Committee Permissions as an early first step of open science

Tools used in the project:
Git

Tools skill level required to enter the project (more than one possible):
#no_skills_required

Programming language used in the project:
no_programming_involved,

Modalities involved in the project (if any):
none

Git skills reuired to enter the project (more than one possible):
#0_no_git_skills, 1_commit_push, 2_branches_PRs

[ x] I added all of the labels I want an associate to my project

Project Submission
Submission checklist
Once the issue is submitted, please check items in this list as you add under ‘Additional project info’

[x] Link to your project: could be a code repository, a shared document, etc.
[x] Goals for Brainhack Global 2020: describe what you want to achieve during this brainhack.
[x] Flesh out at least 2 “good first issues”: those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document.
[x] Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill. Use the issue labels for this purpose.
[x] Chat channel: TR-Open "getting started" mattermost channel
[x] Video channel: We have a jitsi room available info is at our mattermost channel

Optionally, you can also include information about:

[ ] Number of participants required.
[x] We want to introduce and compile standard templates to be used as an example for early career researchers who wants to start to collect open data and needs reliable resources for ethical committee applications in Turkey.
[ x] Provide an image of your project for the Brainhack Global 2020 website.

[x] By helping us you would be a  contributor and your contributions would be shown at our website. listing members on a contributing page.
[ -] Provide links to onboarding documents if you have some: None

Umm... how can I add brainhack ankara label?

Dear @i-am-mel-dev thank you very much for the submission, this project sounds awesome! Would you like to provide an image for your project to showcase in your card to make it to your project-specific? Please add the image to the top or anywhere of the issue, then we are good to go. Thank you 🎉

Supra! I am publishing it! Thank you so much 🤗

Supra! I am publishing it! Thank you so much 🤗

Thank youuuu! It's so exciting!


WIP - TraceID, SpanID, ParentID are strings instead of uint64

Working on issue #10 .
I think I may still have some code cleanup to do.

Coverage increased (+0.4%) to 78.633% when pulling 0b585cd2f7344301826123c838d153837c9a7ead on gnahckire:IdsToStrType into afeff3e3b94f7f35cbf22221c48256a92a2ecc4f on Nordstrom:master.


The extension no longer works

With the new twitter update, the extension no longer works. I hope this is fixed, as the new twitter is terrible...
If you could add:
Remove the star thing (Always show latest tweets)
Show followers on the home screen
Show new tweets in the tab
That would be awesome, thanks!

In case it helps, you can still restore the good old twitter web-UI using solutions like this https://github.com/zaszthecroc/fix-my-twitter one for example, as very many prefer anyway, exactly because "the new twitter is terrible".


ci: firebase

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Code style update
[x] Build or CI related changes
[ ] Documentation content changes

@nsbarsukov
https://taiga-ui--pr2898-splincode-ci-firebas-97rkv1ea.web.app/components/action#vertical


Correctly handle passing ObjRefs by value to distributed functions

Consider a remote function
@ray.remote([ObjRef], [])
def f(objref):
    return

If we call f(objref), then the argument objref should be passed by value. However, currently, the scheduler will attempt to ship the corresponding object and get_arguments_for_execution in worker.py will attempt to pull the object.

This is a duplicate of #34.