feat: Physical Settlement

-- Adding new settlement type
-- refactoring how settlement works (determined by margin engine)
-- removing PositionOptim struct (Cross Margin)
-- Adding PhysicalSettlement contract to Mixins
-- Adding PhysicalSettlement interface
-- renaming functions

Some other thoughts:

can we not have issuer id inside the product ID? because as long as you have this 1 to 1 relationship for tokenId vs issuer, these tokens are not fungible.
Alternative: keep track of how much of each "physical settle option" is exercised, so after the exercise window, you apply that to all seller. (if 30% of total supply is exercised, you get 70% back of your original collateral, and 30% in underlying or strike based on strike price)

Some other thoughts:

can we not have issuer id inside the product ID? because as long as you have this 1 to 1 relationship for tokenId vs issuer, these tokens are not fungible.
Alternative: keep track of how much of each "physical settle option" is exercised, so after the exercise window, you apply that to all seller. (if 30% of total supply is exercised, you get 70% back of your original collateral, and 30% in underlying or strike based on strike price)

I am already migrating the implementation to something similar to your second bullet point.

Couple things:

can you re-run forge snapshot so we have a better understanding of how this PR affects old cash settled option workflows?
Lots of functions can be declared as external instead of public
Big issue i see now is, you can issue a cash settle token and then transfer your account to another subAccount to get away from paying. This needs to be taken care of.
I like the idea of letting the engine handle both cash settle and physical settle options, but the code in Grappa._settle is unclear now how that is done (it should be explicit about calling functions on IPhysicalSettlement or ICashSettlement to indicate diff methods).
Also the whole point of having grappa is to make sure all engines payout with the same rule, so you should not move getPayout into each engine to implement.

yep
Because the function names were the same between PhysicalSettlement and CrossMarginEngine, having PhysicalSettlement called from CrossMarginEngine isnt allowed by the compiler if the PhysicalSettlement function is external. I updated the architecture to use internal function in PhysicalSettlement and in IPhysicalSettlement define the expected names.
You cant do that with Cash Settled, i believe i clarified with you that you meant Physical Settlement. Transferring was an issue because the token was storing the issuer id, but that no longer how it works.
I agree - this approach of making the settlement layer modular is proving to be a nice separation of responsibility. In another PR we should extract Cash Settled logic into its own abstract contract.
I do not agree on this point. By moving the "payouts" logic to base engine we allow margin engines to implement custom tokens (like debit spreads) without exposing every engine to this implementation. Grappa is still the registry and orchestrator of settlement but without overhead.

yep
Because the function names were the same between PhysicalSettlement and CrossMarginEngine, having PhysicalSettlement called from CrossMarginEngine isnt allowed by the compiler if the PhysicalSettlement function is external. I updated the architecture to use internal function in PhysicalSettlement and in IPhysicalSettlement define the expected names.
You cant do that with Cash Settled, i believe i clarified with you that you meant Physical Settlement. Transferring was an issue because the token was storing the issuer id, but that no longer how it works.
I agree - this approach of making the settlement layer modular is proving to be a nice separation of responsibility. In another PR we should extract Cash Settled logic into its own abstract contract.
I do not agree on this point. By moving the "payouts" logic to base engine we allow margin engines to implement custom tokens (like debit spreads) without exposing every engine to this implementation. Grappa is still the registry and orchestrator of settlement but without overhead.

I'd push back hard on point 5.
One of the main selling point of grappa is you use 1 token for all engine, as long as each engine has enough fund to payout. (implement payoutCash or something ), you can treat them as same products that would payout exactly the same at expiry.
Putting this logic into individual engines has several drawback:

add duplicate logic in engine (they are already big contracts, while grappa is smaller)
more gas cost on settlement because now you need to call each engine to settle token once per token, even tho the payout can be 0. (It used to batch calls to just 1 call if you settle several tokens with same payout token)
if each engine can define the payout, we no longer have any guarantee on what each token means, so the TokenType become completely useless and mean nothing to integrating projects.

To counter your point, a engine has the ultimate right to decide what token to mint, if you don't want debit spread, you should never create such a token from your engine.
If we just make Grappa the registry, the whole architecture should turn the other way around: there's no point of using grappa as settlement anymore, each engine just settle things any pay user on their own. And all engine would loss the nice relationship about working under the same framework, it would just be bunch of option protocols using "similar" token representation.

I'd push back hard on point 5. One of the main selling point of grappa is you use 1 token for all engine, as long as each engine has enough fund to payout. (implement payoutCash or something ), you can treat them as same products that would payout exactly the same at expiry.
Putting this logic into individual engines has several drawback:

add duplicate logic in engine (they are already big contracts, while grappa is smaller)
more gas cost on settlement: now you need to call each engine to settle token once per token, even tho the payout can be 0. (the payout call used to batched, so if you're settling several tokens with same payout token, it only calls the engine ones. ) This is extremely helpful for batch settling multiple long positions.
if each engine can define the payout, we no longer have any guarantee on what each token means, so the TokenType become completely useless and mean nothing to integrating projects.

To counter your point, a engine has the ultimate right to decide what token to mint, if you don't want debit spread, you should never create such a token from your engine.
If we just make Grappa the registry, the whole architecture should turn the other way around: there's no point of using grappa as settlement anymore, each engine just settle things any pay user on their own. And all engine would loss the nice relationship about working under the same framework, it would just be bunch of option protocols using "similar" token representation.

We don't really use 1 token for all engines. While each token may share similar characteristics (underlying, collateral, etc) it is always different because of the engineId that originated it. If it was the intention to make every token completely fungible across engines, then grappa would be the custodian of all assets and issue the same token everywhere. Thats of course not how it works / not how we want it to work.
With the introduction of DebitSpread token there is a weird cross over of logic between engines and grappa. While I completely agree that an engine can decide the type of token it issues, this should be scoped to established derivative primitives. This excludes DebitSpreads. In the real world a spread position is created by using two primitives. It itself is not a primitive, nor does it need to be. Just because two positions can be represented as a single fungible token in defi, does not mean it should.
I can get behind moving payout logic for established primitives back to grappa, for efficiency and transparency but it cant include DebitSpreads.
A compromise can be to establish a Token Type threshold that any value over 200 is a reserved type and the debts/payouts need to be retrieved from the issuing engine.

While each token may share similar characteristics (underlying, collateral, etc) it is always different because of the engineId that originated it

Agree that under the current (old) Grappa structure, each token will never be the same (not fungible), but rely on very little assumption:

with a shared settlement logic, it's guaranteed to pay out the same, if the issuing engine is solvent.

If you move any of the settlement logic into each engine, you break this assumption and ultimately just rely on all engine to "implement things correctly", which is not countable.

With the introduction of DebitSpread token there is a weird cross over of logic between engines and grappa

Can you elaborate a bit more? I don't see what is the "cross over of logic" here. This is how I think about it: what we're offering at grappa is we have a more complicated tokenType called CALL_SPREAD or PUT_SPREAD, and you as an engine provider can choose if you want to allow user to create this token. and this settle with the rule that cap at a max amount. The separation of logic is the same:

Grappa defines how token type is settled,
Each engine decides if user can mint one from it (or how that can be split up to 2 positions).

to me it is always clear how each module should look at a token: Grappa: how to settle, Engine: Can I margin this position or it's too complicated (can just ignore).

This should be scoped to established derivative primitives. This excludes DebitSpreads. In the real world a spread position is created by using two primitives. It itself is not a primitive, nor does it need to be. Just because two positions can be represented as a single fungible token in defi, does not mean it should.

I definitely don't agree with the conclusion here. While I agree "debit spread is not a primitive", it doesn't mean it cannot be a shared defined token type that we can apply settlement rule across engines. No one said Grappa is only supporting primitive like future and vanilla option, in fact debit spread is one of the most important feature that makes Grappa different from the rest of the option protocols.
One of the main reason is that: it lets people create a debit spread position without having to open accounts.
if you only have short token, the only way for you to trade debit spread (lets say 1500-2000 call spread) with someone else is to

create an account
buy the long cal (1500 call) from the counter party
mint the 2000 call from the account, and send it back to counter party
So in this trade, both sides need to open accounts on your engine.

But if you have debit spread as a token, because this token is always positive payout, you can just let the seller open a credit spread position (long  2000, short 1500), create this "debit spread token", and trade with any ERC1155 to ERC20 protocol (0x, Seaport..etc), without the "buyer" ever need to manage through engines.
Combine with the "grappa settles" feature, it means lots of user who just wants to long option / spread to be only relying on grappa: it only cares about checking if this is the right token address, and come to grappa to settle trades.
The spread token is in fact the ONLY feature Ribbon asked for when I started designing the system. If Ribbon as a DOV can sell spread, and MMs can buy without knowing how to deal with engine accounts, also using well tested token to token trading contracts, (as easy as its original auction) while "dramatically" improve capital efficiency from the vault side.
(a 1500 put might only be 10% more expensive than 1500-1000 put spread, but the later is 3x more capital efficient), this driven the capital efficiency of a DOV by 2.5+x.
That's why I implemented it in both FullMargin and Advanced Margin supports it. FullMargin was designed only for DOV use cases (always fully collateralized), and advanced margin is for AMM (rysk) to offset collateral on call and puts. Both teams I talked to wanted spread tokens, because of the capital efficiency improvement by introducing this easy concept.
(Rysk is selling simple token to user as AMM, and same example here, you can't sell spread by saying "you have to have an account to trade", because that's terrible UX compared to using a token representation. Also their AMM "wants" to sell spread more than simple options because it causes a lot less capital to be locked with only getting a little bit less in premium, affect the overall trading capacity)
So as one of the main selling points for Grappa, I'd definitely say it should be one of the "standard" token types. This tied back to the thing earlier about shared settlement logic in Grappa level, only with shared settlement logic on this token, AMMs can be built to exchange this token across different "engine types". (was dreaming bridging Ribbon and Risk liquidity back in the days 😂 )
So to wrap up, I really see lots of improvements with introducing debit spread. Even if my engine can't handle merging position into spread or splitting spread into long + short, I would want to support it solely because of capital efficiency improvements. I don't know who told you "they don't trade spread", but all DeFi option teams I talked to are trying to support this type. And not being a primitive is definitely a good reason to not have it.
(It's definitely not just fun!)


Apt installation method to readme.md

Hi, could you please add the APT package manager installation method.
apt install lolcat

We have something even better now!
Try sudo snap install lolcat
And please make noise in case it doesn't work 😋

Making noise - snap works but lots of folks would rather go either the gem route or the apt way - can readme include some alternatives for installation? Snap has lots of people unconvinced.

Problem with the alternative routes is that they
don't work reliably which results in user frustration.
The politics around snap are annoying, but for this type
of utility it's the least bad distribution method amongst the
currently available options.
Advanced users are of course free to install in any way they like
but for the time being the only officially supported method is snap.

@m-o-e I don't like snap, it installed too many unnecessary things, at least you should provide another option for me to install it besides snap.


Object is possibly 'undefined' when instantiating object during declaration

If attempting to instantiate an object during declaration, where the type of a property is optional/nullable, the type checker does not seem to understand that the property is actually set when trying to use it.
Does not work:
type Dummy = {
    options?: string[];
};
const a: Dummy = { options: [] };
a.options.push('test'); // <-- Object is possibly 'undefined', refering to a.options

Works:
type Dummy = {
    options?: string[];
};
const a: Dummy = {};
a.options = [];
a.options.push('test')

Would somebody be kind enough to explain if I'm failing to see some subtle detail here, or if this is perhaps intentional or a even a bug in the type checker?

This is intentional. When you annotate the declaration for a with Dummy, you’re throwing away all the information that the type checker checks about the innards of that object. It checks to make sure your declaration is consistent with the type annotation, but from then on, it just goes with your annotation: a is Dummy, and Dummy is not a narrowable type (in contrast to something like Dummy | undefined, in which we would try to track which of those types it might be), so it’s just always Dummy, and options is optional in Dummy.
There are lots of ways you could get around this, including the one you posted, but the first thing that comes to my mind is something like
function createDummy(): Dummy {
  const a: Required<Dummy> = { options: [] };
  a.options.push('test'); // No error because 'options' is required
  return a; // 'Required<Dummy>' satisfies 'Dummy'
}

You are getting errors Because in the type you have defined options can be undefined as well. May be below example can help
type Dummy = {
    options?: string[];
};

const a: Dummy = { options: [] };
a.options?.push('test');

Thank you for your thorough explanation @andrewbranch 👍 🙂


Add Support for AvailabilityResults and BrowserTimings

The failing check is due to the Azure token expiring. It's only good for 7 days at a time. Will regenerate one. But we'll need a long term solution.


Multiple Click() params fixes and right-click handling

Fixes https://github.com/OpenDreamProject/OpenDream/issues/1899
Partially addresses https://github.com/OpenDreamProject/OpenDream/pull/1926 by adding left=1 and implementing the button param.
Does not address https://github.com/OpenDreamProject/OpenDream/issues/1928

I tested button and it does not seem to include modifier keys or anything in BYOND, just which mouse button is being pressed.


Unresponsive Button in Header

So, I'm using side menu or drawer on my current project and I'm using NativeBase+react-native-router-flux. Everything works fine, the menu will open at swipe but I just found out that the menu won't open when I tap button that I put on header. I think there is something wrong with my function but After further investigation the button is not responding to tap/press.
Here is the code for header:
<Header style={{backgroundColor: '#f4c542', borderBottomColor: 'transparent'}} hasTabs>
  <Left>
    <Button transparent onPress={()=>Alert.alert("hamburger tapped")}>
      <Icon name='menu' />
    </Button>
  </Left>
  <Body>
    <Title style={{color: '#5b5b5b'}}>HOME</Title>
  </Body>
  <Right />
</Header>

and below is my AppNavigation.js structure:
<RouterWithRedux>
  <Scene key="modal" component={Modal}>
    <Scene key="root">
      //another scene
    </Scene>
  <Scene key="statusModal" component={StatusModal} />
  </Scene>

  <Router key="draw" component={SideMenu} open={false} hideNavBar={true}>
  <Scene key='main' component={Home} hideNavBar={true} />
   </Router>
</RouterWithRedux>

How can I make my button work?

Please check NativeBase-KitchenSink for working example

@EgaSetya Can you explain how fix your issue?

@EgaSetya Did you get your app running, referencing NativeBase KitchenSink?

@SupriyaKalghatgi Yeah after referencing on NativeBase KitchenSink and some searching, I actually got my app running. Thanks for the help


[DOC] Explain how to access the storage object

Is your feature request related to a problem? Please describe.
In the documentation on Assembly Script: https://docs.nearprotocol.com/docs/development/writing-smart-contracts we mention that all the interactions with the storage should happen via storage object, and link to the storage API docs:

Like with web servers, function calls are stateless. Any state that you want to save to the blockchain needs to be explicitly saved by interacting with the storage object.
This object provides an interface to the blockchain storage. It is a standard key-value store where keys are strings and the values can be multiple types including string, bytes, u64. Anything else needs to be first converted into these types.
See the storage docs and collections for the full reference.

We need to explain how to actually import and access the storage object. A simple example would be great.
Describe the solution you'd like
Add a simple example of a smart contract that uses raw storage (as opposed to persistent collections) and shows how to import storage and how to interface with it.

would it be sufficient to link existing examples in the docs?  or do we need a snippet of code inline here?
all of the following examples use storage, although limited to setString / getString and setBytes / getBytes

NEAR Wallet Integration
Implement an Oracle
Testing Smart Contracts


Example app not working

I cloned the repo into my computer and did the following steps: -

cd Example
npm start
I opened a separate terminal and typed "npm run android" but I got an error saying "node_modules" not found. When I tried "npm i", this is the error I get: -

Can you please tell me if I did any incorrect steps, or where I am going wrong?

If you want to Install it using yarn then there will be no error yarn install
If you want to Install it using npm like this npm i --legacy-peer-deps

Closing since it is actually working.


Basic README

I wanted to check out the UI branch but I haven't done anything in React.
Their getting started page suggests all you need is:
npm install -g react-tools && jsx --watch src/ build/
...but I didn't know what source or build to watch :disappointed:.
What npm dependencies are there? How to I install them and serve this up to a localhost?
@luqmaan @johntyree

Will add readme soon. Not much to see for now.
Npm install -g gulp
Npm install
Gulp clean && gulp
On Mon, Jun 8, 2015 at 11:28 PM Mateo Clarke<EMAIL_ADDRESS>wrote:

I wanted to check out the UI branch but I haven't done anything in React.
Their getting started page suggests all you need is:
npm install -g react-tools && jsx --watch src/ build/
...but I didn't know what source or build to watch [image: :disappointed:]
.
What npm dependencies are there? How to I install them and serve this up
to a localhost?
@luqmaan https://github.com/luqmaan @johntyree
https://github.com/johntyree
—
Reply to this email directly or view it on GitHub
https://github.com/open-austin/austingreenmap/issues/4.

it looks like babel https://babeljs.io/

also had to run
npm install gulp-symlink --save-dev

:+1:


feat: Add ability to specify existing IAM role for ECS task execution

Description

Add ability to specify existing IAM role for ECS task execution.
Motivation and Context

Allow module to be used in scenarios where IAM roles cannot be created or already exist.
Breaking Changes

No.
How Has This Been Tested?

module "atlantis" {
  ...

  ecs_task_execution_iam_role_arn = "arn:aws:iam::xxxxxxxxxxxx:role/xxxxxxxxxx"
}

Hello @antonbabenko, can you provide feedback on this PR? Wondering if there is any chance of getting this and my other PR (#127) merged or is it not in line with your goals for this project?

Hi @druchoo !
This PR and another looks pretty good, but I will be able to process them at the end of August.

@antonbabenko completely understand that you're busy. Would it be possible to add additional maintainers for this terraform module? This way the module can be continuously maintained without putting pressure on you.

@bryantbiggs Could you please take a look at this PR?
@nitrocode I was on vacation, but since June there are several of us ( @terraform-aws-modules/triage-supporters ) who can do code reviews and close issues.

@antonbabenko yes I can take a look this week.
@druchoo would you mind updating your branch with master please?

@bryantbiggs can you advise on how to fix the semantic check?

@druchoo I think it wants the Add to be lower case, I would try feat: add ability to specify existing IAM role for ECS task execution and if that doesn't work then feat: add ability to specify existing iam role for ecs task execution

@bryantbiggs, Should be good now. I was failing with trying to fix the merge and ended up force-pushing.

hey @druchoo I left some comments - please feel free to use the github-complete under the examples directory for testing. you test out your changes using that examples project (you'll just need to update for the existing IAM role name - no need to commit this change, just use it to validate your changes to the module)

@bryantbiggs, ok cool. thanks for reviewing. I don't think I'll be able to update and test for a few days though unfortunately.

@druchoo no worries - I have an idea I might put up in a PR tonight that will help solve this and some of the other issues around using existing resources. we can circle back to this when you get time


'ON DELETE CASCADE' not triggering

Hi,
I have ON DELETE CASCADE statements in my DDL that work when I run them on my Sqlite installation on my PC, but seem to not be triggered in the plugin.
I have also tried executing
await db.execute({statements:`
    BEGIN TRANSACTION;
    PRAGMA foreign_keys = ON;
   COMMIT TRANSACTION;`});

right after opening the db, but it makes no difference.
Are there any known limitation with ON DELETE CASCADE in the plugin?
If not, can you please show an example that you would expect to work?
Regardless, thank you for a great plugin!

Hi, thank you for the reply.I forgot to mention it in my first post, but I later updated it: I have tried that in different ways, but it makes no difference, unfortunately.
On Wednesday, May 27, 2020, 9:49:43 PM GMT+2, Fernando Leal<EMAIL_ADDRESS>wrote:

This could be it: PRAGMA foreign_keys=OFF in your device's database
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@accron-1 I found the issue, one have to set-up the pragma each time a connection to the db is made. So this is solved in the next release as soon as i can publish on npm which is quite hard those days.(timeout issue).
this is the way i tested
  /**
  * Test an ImportFromJson
  */
 async testImportFromJson():Promise<boolean> {
    return new Promise(async (resolve) => {
      let ret:boolean = true;
      let users = [];
      let is = '';

      for (let index = 0; index < 3; index++) {
        is = index.toString();
        users.push([
          index,
          'name ' + is,
          'surname' + is,
          Math.floor(Math.random() * (80 - 20)) + 20,
          new Date().getTime() / 1000 | 0
        ]);
      }
      const dataToImport: any = {
        database: 'testing',
        encrypted: false,
        mode: 'full',
        tables: [
          {
            name: 'users',
            schema: [
              { column: 'id', value: 'INTEGER PRIMARY KEY NOT NULL' },
              { column: 'email', value: 'TEXT UNIQUE NOT NULL' },
              { column: 'name', value: 'TEXT' },
              { column: 'age', value: 'INTEGER' },
              { column: 'last_modified', value: 'INTEGER' }
            ],
            indexes: [
              { name: 'index_user_on_name', column: 'name' },
              { name: 'index_user_on_last_modified', column: 'last_modified' }
            ],
            values: users
          },
          {
            name: 'messages',
            schema: [
              { column: 'id', value: 'INTEGER PRIMARY KEY NOT NULL' },
              { column: 'userid', value: 'INTEGER' },
              { column: 'title', value: 'TEXT' },
              { column: 'body', value: 'TEXT' },
              { foreignkey:'userid',value: 'REFERENCES users(id) ON DELETE CASCADE'},
            ],
            values: [
              [1,1,"test message 1","content test message 1"],
              [2,2,"test message 2","content test message 2"],
              [3,1,"test message 3","content test message 3"]
            ]
          }
        ]
      };

      let result: any = await this._SQLiteService.importFromJson(JSON.stringify(dataToImport));
      console.log('import result ', result)

      if(result.changes.changes === -1 ) ret = false;
      if(ret) {
        // create the async table
        result = await this._SQLiteService.openDB("testing");
        if(result.result) {
          result = await this._SQLiteService.createSyncTable();
          let sqlcmd: string = "SELECT * FROM users;";
          result = await this._SQLiteService.query(sqlcmd);
          sqlcmd = "SELECT * FROM messages;";
          let result1 = await this._SQLiteService.query(sqlcmd);
          if(result.values.length === 3 && result1.values.length === 3 ) {
          // Delete user with id = 2
            sqlcmd = "DELETE FROM users WHERE id = 2;";
            result = await this._SQLiteService.run(sqlcmd);
            console.log("after delete result.changes.changes ",result.changes.changes)
            sqlcmd = "SELECT * FROM users;";
            result = await this._SQLiteService.query(sqlcmd);
            sqlcmd = "SELECT * FROM messages;";
            result1 = await this._SQLiteService.query(sqlcmd);
            if(result.values.length === 2 && result1.values.length === 2 ) {
              console.log("*** ON DELETE CASCADE successfull *** ")
            } else {
              console.log("*** ON DELETE CASCADE failed *** ")
              ret = false;
            }

          } else {
            ret = false;
            console.log("importFromJson: Error number of users and messages not correct");
          }
        }
      } else {
          console.log("importFromJson: Error " + result.message);
      }
      resolve(ret);
    });
  }

Ya, if finally got it publish release 2.1.0-6. I would like to thank you for your contribution to debug. it helps. Do not hesitate to come back if you find a new issue

I just tried the updated version and everything works as expected now.
Thank you for the prompt fix, and thank you again for providing this important and awesome plugin!


neonvm-controller: Catch Reconcile() panics

In theory I think this could be done with some kind of middleware, similarly to our metrics collection. In practice, it's quite small, and probably more effort than it's worth to do the abstraction.
Resolves #827.

Haven't tested it yet, need to try that locally to check it works.

I'm more on the side of middleware approach and we already have a similar one.

Went with the middleware approach, via new file neonvm/controllers/catch_panic.go.
I think that satisfies both of your concerns?

lgtm!

Tested locally by forcing the controller to panic on every reconcile when the VM is running:
diff --git a/neonvm/controllers/virtualmachine_controller.go b/neonvm/controllers/virtualmachine_controller.go
index 0c4ae66..1868b6c 100644
--- a/neonvm/controllers/virtualmachine_controller.go
+++ b/neonvm/controllers/virtualmachine_controller.go
@@ -470,6 +470,10 @@ func (r *VirtualMachineReconciler) doReconcile(ctx context.Context, virtualmachi
             // do nothing
         }
     case vmv1.VmRunning:
+        if true {
+            panic("test panic!")
+        }
+
         // Check if the runner pod exists
         vmRunner := &corev1.Pod{}
         err := r.Get(ctx, types.NamespacedName{Name: virtualmachine.Status.PodName, Namespace: virtualmachine.Namespace}, vmRunner)


feat: lido gho

Showcase the idea of using the executor as a facilitator and minting.

For me this looks ok.


Flowplayer 7.2.0 splash needs two clicks to play

Migrated from flowplayer/flowplayer#1273

This is because in 7.2 conf.splash is not equivalent to conf.autoplay anymore


Update Makefile on sync submodule

As submodule currently does not support pin to commit, this creates problems when merging master to a local developing branch. If the commit in master might point to the new commit in submodule idl. But the local branch tracks the old commit.
The change removing the command of sync submodule and only two cases should run make sync-submodules:

Merge master
Current changes in the local branch require IDL changes

The buildkite should be fine as it do git clone every time and it should get the latest commit in master branch.

Coverage decreased (-0.2%) to 67.477% when pulling af081e064a5465f6366675d93dff3a29c6caa738 on submodule-update into 72a84fd927671e91e608f7e3b8f36dab5f2df518 on master.


tf.nn.embedding_lookup: unexpected behaviour with sharded params in "div" mode

The following code shows what appears to be a misbehaviour when trying to lookup sharded embeddings in "div" mode:
def test_shard_embedding_lookup(index):
   embeddings_1 = tf.constant([[0,0,0],[1,1,1],[2,2,2],[3,3,3]])
   embeddings_2 = tf.constant([[4,4,4],[5,5,5]])
   indices = tf.constant([index])

   with tf.Session() as sess:
      ret = sess.run(\
                  tf.nn.embedding_lookup(\
                     [embeddings_1, embeddings_2],\
                     indices,\
                     partition_strategy='div'\
                  )\
                )

test_shard_embedding_lookup(2) # [2,2,2]
test_shard_embedding_lookup(3) # [4,4,4] instead of [3,3,3]

Tested with

Python 3.6.5
TF 1.8

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Have I written custom code: No
OS Platform and Distribution: macOS 10.13.4
TensorFlow installed from: pipenv install tensorflow
TensorFlow version: 1.8
Python version: 3.6.5
CUDA/cuDNN version: N/A
GPU model and memory: N/A
Exact command to reproduce: see previous comment

Thank you for providing such a clear minimal case. I am able to replicate this behavior, and it appears to go back to at least version 1.0.0. I'll update when I know more.

@ccolby I cannot find the documentation you are referring to. Could you please attach here? Also, is there any reason for tf.nn.embedding_lookup not to be usable to un-balanced sharded tensors?

@syltruong I'm referring to the tf.nn.embedding_lookup documentation. That documentation describes how the two supported partitioning strategies work—"div" and "mod". It also clarifies that for the params argument:

Each element must be appropriately sized for the given partition_strategy

As for why tf.nn.embedding_lookup doesn't support arbitrary partitioning, it is most likely because the "div" and "mod" strategies cover the common use case of balanced partitions and are easy to compute. It is a simple and efficient formula to map from index to (partition number, index within partition). There is certainly no reason why you can't implement the more general case, but the code will be more complex, with more ops required to implement that index mapping.
@robieta I suggest closing this issue, since there is no bug. (I cannot do it.)
@syltruong Consider posting further questions to stackoverflow.

Thanks for your help. I learned a lot as well.


Closes #46

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
5
❗

❗ custom/widgets-meal-nutrients--hint-opened__[w1440px]:

Before
After

❗ custom/widgets-meal-nutrients--hint-opened__[w1920px]:

Before
After

❗ storybook/widgets-heart-rate--default__[w1440px]:

Before
After

❗ storybook/widgets-heart-rate--default__[w390px]:

Before
After

❗ storybook/widgets-meal-nutrients--default__[w900px]:

Before
After

Shot Type
Count
Status

Added
8
🟡

Deleted
0
❌

Regression
2
❗

🟡 storybook/components-button-group--custom-style__[w1440px] (click to expand)

Image

🟡 storybook/components-button-group--custom-style__[w1920px] (click to expand)

Image

🟡 storybook/components-button-group--custom-style__[w390px] (click to expand)

Image

🟡 storybook/components-button-group--custom-style__[w900px] (click to expand)

Image

🟡 storybook/components-button-group--default__[w1440px] (click to expand)

Image

🟡 storybook/components-button-group--default__[w1920px] (click to expand)

Image

🟡 storybook/components-button-group--default__[w390px] (click to expand)

Image

🟡 storybook/components-button-group--default__[w900px] (click to expand)

Image

❗ storybook/utility-responsive-image--responsive-image__[w1440px]:

Before
After

❗ storybook/utility-responsive-image--responsive-image__[w1920px]:

Before
After

Shot Type
Count
Status

Added
0
🟡

Deleted
0
❌

Regression
7
❗

❗ custom/widgets-linkstabbar--current-focus__[w1920px] (click to expand)

Before
After

❗ custom/widgets-meal-nutrients--hint-opened__[w1440px] (click to expand)

Before
After

❗ custom/widgets-meal-nutrients--hint-opened__[w390px] (click to expand)

Before
After

❗ custom/widgets-navbar-opened__[w1440px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w1440px] (click to expand)

Before
After

❗ storybook/widgets-heart-rate--default__[w390px] (click to expand)

Before
After

❗ storybook/widgets-meal-nutrients--default__[w900px] (click to expand)

Before
After


Ambigous query produced on upsert attempt

Environment

Elixir version (elixir -v): 1.3.2

Database and version: PostgreSQL 9.6.1

Ecto version (mix deps): 2.1.2

Database adapter and version (mix deps):

postgrex 0.13.0 (Hex package) (mix)
locked at 0.13.0 (postgrex) e101ab47

Operating system: Darwin Kernel Version 16.3.0

Current behavior
Trying to perform upsert with counter increase on conflict (unique constraint violation).
Migration:
create table(:people) do
   add :email, :string, null: false
   add :times_seen, :integer, default: 1
   timestamps
end

create unique_index(:people, [:email])

Upsert:
l = [%{email<EMAIL_ADDRESS>updated_at: now, inserted_at: now}]

"people"
|> Repo.insert_all(l,
  returning: [:id, :email],
  on_conflict: [
    inc: [times_seen: 1]
  ], conflict_target: :email)

Produces an error:
** (Postgrex.Error) ERROR 42702 (ambiguous_column): column reference "times_seen" is ambiguous

Query:
INSERT INTO "people" AS s0 ("email","inserted_at","updated_at")
VALUES ($1,$2,$3) ON CONFLICT ("email")
DO UPDATE SET "times_seen" = "times_seen" + $4
RETURNING "id", "email"

Bindings:
<EMAIL_ADDRESS>"2017-01-17 10:57:51", "2017-01-17 10:57:51", 1]

The problem with generated query seems to be:
SET "times_seen" = "times_seen" + $4

Expected behavior
SET "times_seen" = "s0"."times_seen" + $4

Failing test case:
    @tag :with_conflict_target
    test "on conflict with inc" do
      uuid = "6fa459ea-ee8a-3ca4-894e-db77e160355e"
      post = %Post{title: "first", uuid: uuid}
      {:ok, _} = TestRepo.insert(post)

      post = %{title: "upsert", uuid: uuid}

      TestRepo.insert_all(Post, [post], on_conflict: [inc: [visits: 1]], conflict_target: :uuid)
    end

Beautiful! I will work on a fix today and likely get a new v2.1 out as we have had other bug fixes lately.

I think the final query should rather be:
SET "s0"."times_seen" = "s0"."times_seen" + $4

so we include the table reference in all the places.

@michalmuskala just FYI, that query is not supported. You can't have "s0" on the left side of =.

Fixed on e25aed8. v2.1.2 coming out shortly. Thank you for reporting and the test case @aerosol!

@josevalim thank you, really appreciate your work!


Feature Request: Option treat "words containg underscore like foo_bar" as one word

As a programmer, I often use variables such as 'foo_bar' and 'latest_comments_for_user' in my Obsidian notes. It would greatly enhance my efficiency and comfort if these types of variable names could be auto-completed.
Thank you for developing such a useful Obsidian plugin.

Sorry for my late answer, @wafe.
I agree with you. I want to give it a try 👍

Since underscores are used in Markdown syntax, it's difficult for Various Complements to determine whether they signify names or formatting.
Therefore, we will introduce an advanced option to address this.

@wafe
Released in v9.2.0 🚀


[#103] Add ssh client support for remote execution

And document it

Confirmed that this works, but, y'know, still sort of experimental. Works just fine with local docker daemon as well.

Well, yes, but even more so... every commit gets run through the big machine - and every commit is releasable after a day or three of automatic testing.

Right, in the future we can add direct support for a list of remote hosts to which we can farm out jobs. Right now, we just use the local Docker client environment, and DOCKER_HOST can only be 1 value at a time. However, we can potentially build this into the context and/or other pieces of the library such that an API can farm out tasks appropriately by drawing from a list of hosts (in a file, given via an option, environment variable, etc.). For now, a wrapper script may be sufficient.


Added #hashCode()

I don't see any reason why I should add that. Next time maybe add why it is needed.


Add popular Bevy crates

Having some popular creates available in the same way the rust playground does would make the playground a lot more useful. All the crates used in the official Bevy examples should also be available.
Keeping builds fast
The rust playground will remove the dependencies if they are not used, however as far as I can tell they either have none or all. I don't think it would be to difficult to figure out what crates are being used by analyzing the code and toggle each dependency individually. Testing should be done to find whether this would make a difference.
Automatic updating
It's unrealistic manually update the images when each crate updates. The way the rust playground solves this is by building the images on a schedule each day. In our case this would mean building the images on a schedule every 24 hours and uploading the images to docker hub then pulling them on the bevy_compile_api server(s).
Problem
The playground allows for multiple versions of Bevy to be used. Most crates target the latest version of Bevy so if the crates updated each nigh once a version is no longer the latest it will very likely become incompatible with the crates.
A possible solution is to only update crates for the latest version of Bevy and lock the older versions to the last version when Bevy updated. This would also have the positive effect of only having to update the latest version each night, saving on compute and time.
One thing that needs to be addressed is the process when a new Bevy version comes out. Some crates will be update to support the latest version before the playground so we would need to make sure these quickly updated crates don't get added for the previous version.
Crates (thoughts wanted part)
The list of crates to be added, please comment if you think of a good addition. I don't want to have too many

rand*
rand_chacha*
serde* (not 100% on this, depends on if it affects build time, shouldn't do if it's not being used)
bevy_xpbd
big-brain
bevy_egui
bevy_hanabi
bevy_mod_picking
bevy_prototype_lyon
bevy_kira_audio

*included in official Bevy examples

leafwing-input-manager and bevy_mod_picking are great for this sort of gameplay-heavy prototyping :)


Unit test panics when run independently without makefile

On the main branch, one of the unit tests in pkg/codegen/utils_test.go panics when run without makefile
go test -timeout 30s -run ^TestRefPathToGoType$ github.com/oapi-codegen/oapi-codegen/v2/pkg/codegen
--- FAIL: TestRefPathToGoType (0.00s)
--- FAIL: TestRefPathToGoType/local-schemas (0.00s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x9a9217]
the root cause is in utils.go line 995, the spec is dependent on globalState having a valid spec in context

Looks like https://github.com/oapi-codegen/oapi-codegen/pull/1446 would fix this?


Arrow text background size is too large

The size of the text background of arrows seems to take into account the formatting tags present into the text.
Example:
{signal: [
{wave: 'P..................'},
{node: 'a....b'},
{node: 'c....d'},
{node: 'e....f'}
],
edge: [
'a<->b tframe',
'c<->d t>sub/sub<',
'e<->f tframe',
],
}

Related to: https://github.com/drom/tspan/issues/4


Implement linter in CI and provide local option to make PR discussions cleaner

I think it would make the review workflow a lot cleaner (and commits) if linting was done with something like ruby-lint.

Suggested: SuperLinter (CI) + RuboCop (local)


textarea: alternate width flex solution

After discovering diff textarea requirements than I had in mind the other day.

Looks like snapshots will need to be updated.

Was merged manually.


Allow send empty arrays through the trace exporter

What does this PR do?
Allow sending empty arrays due to some tracers send this kind of payloads to check agent's availability.
Motivation
Ensure compatibility with that feature.

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

Project coverage is 70.92%. Comparing base (962589d) to head (2402eb6).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #796      +/-   ##
==========================================
+ Coverage   70.81%   70.92%   +0.10%
==========================================
  Files         313      313
  Lines       45619    45747     +128
==========================================
+ Hits        32306    32444     +138
+ Misses      13313    13303      -10

Components
Coverage Δ

crashtracker
38.27% <ø> (ø)

crashtracker-ffi
5.71% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
92.06% <100.00%> (+0.68%)
:arrow_up:

data-pipeline-ffi
90.54% <100.00%> (+4.24%)
:arrow_up:

ddcommon
82.31% <ø> (ø)

ddcommon-ffi
65.52% <ø> (ø)

ddtelemetry
59.51% <ø> (ø)

ddtelemetry-ffi
22.46% <ø> (ø)

dogstatsd
89.45% <ø> (ø)

dogstatsd-client
79.77% <ø> (ø)

ipc
82.76% <ø> (-0.11%)
:arrow_down:

profiling
84.31% <ø> (ø)

profiling-ffi
77.55% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
40.56% <ø> (ø)

sidecar-ffi
1.18% <ø> (ø)

spawn-worker
54.37% <ø> (ø)

tinybytes
93.60% <ø> (ø)

trace-mini-agent
72.38% <ø> (ø)

trace-normalization
98.23% <ø> (ø)

trace-obfuscation
95.77% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.52% <ø> (ø)


Update Bug_Report.yml

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

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 77.935%

Totals

Change from base Build<PHONE_NUMBER>7:
0.0%

Covered Lines:
4341

Relevant Lines:
5570

💛  - Coveralls


⚠ Bofrost.fr has degraded performance

In 2aa01d7, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 941 ms

Resolved: Bofrost.fr performance has improved in 8b72006 after 6 minutes.


issue in building and deploying

Need help with two issues:

While building the terminal, I got 38 errors in file U8U16Test.cpp.
errors like this one:
syntax error: identifier 'length_error'
'length_error': is not a member of 'std'

I corrected these errors and the build was successful. Does this need to be added to documentation?

I faced some linking errors while deploying the Cascadia Package. The reason(I suppose) was this:
Build path is:
terminal\x64\Release
while deploying, it searches for some libs at this path:
terminal\bin\x64\Release
I copied and pasted the content of terminal\x64\Release to terminal\bin\x64\Release and it worked. But I am looking for a permanent solution. Can anyone help?

@DHowett Please help!!

Please search before filing new issues. This is already fixed in master, in #6226

@zadjii-msft #6226 is also fixing the second issue I am facing?

I don't really think the second one is a real issue - our build definitely intentionally places some things in both bin\x64\ and x64\, so I'd bet that the error from the first was causing the second error as well. If you apply the patch from #6226 and you're still getting build errors, share them here and I can (try) to help diagnose them.


Navbar overlaps with main content

When navigating the website by clicking on links in the Navbar, parts of the content are hidden behind the navbar. The appropriate padding or offset is not applied to the content.
After clicking a Navbar link, the content should be fully visible below the Navbar, without any overlap.
There should be a proper margin or padding between the Navbar and the content, ensuring that all sections are accessible.
I will make sure to resolve this issue.

@Jerusha547 Thanks for creating the issue in BuddyTrail!!! The issue has been assigned to you.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Attach before & after screenshots in your PR for clarity.
Include the issue number in your PR description for better tracking.

Contributors will start at Level 1, and their level will increase based on the quality and quantity of their contributions. The more effort and value you bring, the faster you'll progress. Put forth your best effort to unlock new levels and opportunities!
I'm excited to see your contribution as part of GSSOC EXTENDED 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀

Please assign this issue to me


Date-time picker view

Hi!
This PR enables the user to view a date-time picker after enabling it as a prop.
When enabled the time prop a footer will be showed in PickerDay

When clicked a new view is presented to the user

by clicking on the date you can return to the day view.

Coverage remained the same at 100.0% when pulling 8edf4ad78ccd788defb2d12946a3192c02051897 on AndreaMinato:master into de0fc75fe6f6572eebf47f94da20716ab7690cff on charliekassel:master.


A phone number of any length can be inputted in the add commands

Only numbers that are 8 digits long should be able to be added.

Fixed in #181


Try adding an additional condition to catch AutoMerge not being enabled

Microsoft Reviewers: Open in CodeFlow

Reset approval workflow.

This package installs and launches normally on a Windows 10 VM.

Reset approval workflow.


test: speed up core manager unreplicate tests

This change is not urgent.
On my machine, this cuts the time from ~12 seconds to ~1 second.

Seems like this is flaky. Abandoning!


Update README.md

Typo Error Corrected.

Hi,
I signed CLA.
Thanks,
Aftab Ansari
On Tue, Feb 16, 2016 at 10:15 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
Reply to this email directly or view it on GitHub
https://github.com/angular/angular.js/pull/14062#issuecomment-184761084.


[Screen Readers - Power Toys - Color Picker]: The Name property of a focusable element must not be null.

Microsoft PowerToys version
0.41.3
Running as admin

[ ] Yes

Area(s) with issue?
ColorPicker
Steps to reproduce
Test Environment:
OS: Windows 10 Version Dev
App version: 0.41.3
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows
Repro Steps:

Launch Accessibility Insights for Windows tool.
Open Power Toys Settings App.
Navigate to "Fancy zone" list item and activate it.
Run Accessibility Insights for Windows tool.
Observe the issue.

User Impact:
When standard controls from accessible technologies are not used and if the user interface elements are not used according to specification, Assistive Technologies (AT) will not be able to gather information about, activate(or set) and keep up to date on the status of user interface controls in the content.
WCAG Reference -> Priority 2
https://www.w3.org/TR/WCAG21/#name-role-value
Note:
Issue is repro on "Color Piker" dialog.
Note1:

Bug Attachments:

✔ Expected Behavior
The Name property of a focusable element must not be null.
❌ Actual Behavior
The Name property of a focusable element is null.
Other Software
No response

Resolved with the release of v0.43.0. Thanks @niels9001!


DNS-based CWNPs not reliable on hostnames with constantly changing IPs

When resolving DNS names that have a huge IP address pool (eg on AWS), the usual behaviour of DNS servers is to return a limited subset of IPs (say, 8 IP addresses) at random. When asked again, another set of random IPs is returned.
Currently the DNS cache is implemented in a way where the content of a DNS reply completely overwrites the cache entry for this hostname. This can lead to a race condition with concurrent DNS queries: When two pods query the same hostname in parallel, and the reply to the second pod's DNS query comes between the reply to the first pod's DNS query and the actual request to the target IP by the first pod, the IP may already be overwritten in the DNS cache and therefore also the firewall ruleset, making the request from the first pod fail.
A possible solution would be:
Store each IP in the DNS cache with its associated TTL value, add new IPs from subsequent replies instead of replacing the whole entry, and age out old IPs when they exceed their TTL.

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


fix(sider-menu): correct color on header in side menu dark mode

Describe pull-request
Correct color for close icons header part.
Solving issue
Fixes: #
How to test
1.Go to Storybook link below
2. Check in Header -> Inline Menu, switch to dark mode
Resize the window so the menu items are moved into the side menu
Open the menu and see that the color is the same as Figma.
Suggested test steps

[ ] Browser testing (Chrome, Safari, Firefox)
[ ] Keyboard operability
[ ] Interactive elements have labels.
[ ] Storybook controls
[ ] Design/controls/props is aligned with other components
[ ] Dark/light mode and variants
[ ] Input fields – values should be displayed properly
[ ] Events

Screenshots
Should look like this below.

While not technically requested by the JIRA issue, it would be nice if we could fix the borders I hightlighted in red here too ☝

Sure, I can fix them as well.


update-image-check-job

pr to update the check-image-version job to reflect changes in securesign/actions

/approve

/retest


[bug]: Update to 3.5.0 and not working

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
12gb
What version did you experience this issue on?
3.5.0
What happened?
I Just update and stop working, the Eternal "QUEUE"
Screenshots

Additional context
No response
Contact Details
<EMAIL_ADDRESS>

I'm not sure I understand the issue - are queue items not being processed?

same thing happened to me

@angeloshredder could you describe the behavior you're experiencing?

Is this bug report still relevant to be kept open? We're on v3.7 soon switching to v4.0 and we don't maintain older versions, right? Furthermore none of the users provided any feedback from December 2023.

@angeloshredder could you describe the behavior you're experiencing?

It was an old issue, now it's solved .. thanks


Reminder: dynamical directory updater

So far we only have an initial search directory. We have to implement updating routines.
There should be a bunch of strategies depending on the persistence handling.

only update an underlying database and recreate the complete directory periodically from the database.
attempt to update both on the fly within some transaction (? Ok, we could fall back to a complete directory recreation, if in trouble).
store data to the directory (no, we should not).
others

In progress. Tmp. messed the code up.

Done for a first step. Still in poc mode as the whole project so far.


docs: remove deprecated yaml key and misspelled value

serviceAccount is deprecated field according to the kubernetes API spec:
"serviceAccount": {
      "type": "string",
      "description": "deprecated; use serviceAccountName instead"
     },

and the value hibble-* misspelled.

@Khushbu-Parekh
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#assign-reviewer:schaffererin

#sign-off


PHP 8.x support

Hi,
Any plans to upgrade this package for it to be used with PHP 8.x? I cloned the repository and tried to modify the composer.json dependencies but it's not that simple if I want to properly test the package (phpbench doesn't run on PHP 8 either) although it works with the same examples in the Usage section.
Any change to publish an update? :)

It seems I have just forgotten to do it. I will try to fix this soonish.

Released as 2.0.0 which has PHP 8 support.


Errors generating error

With latest monolog-stackdriver installed and configured on the latest stable Laravel, when I switch logging to stackdriver and I get an error it returns the following.  It works fine when I switch logging back to stack but then I cannot log errors to google cloud logging.
"Error decoding message: Invalid argument supplied for foreach()",…}
exception: "Google\ApiCore\ValidationException"
file: "/var/www/mydomain/vendor/google/gax/src/Serializer.php"
line: 128
message: "Error decoding message: Invalid argument supplied for foreach()"
trace: [{file: "/var/www/mydoman/vendor/google/cloud-logging/src/Connection/Grpc.php", line: 331,…},…]
0: {file: "/var/www/mydomain/vendor/google/cloud-logging/src/Connection/Grpc.php", line: 331,…}
1: {file: "/var/www/mydomain/vendor/google/cloud-logging/src/Connection/Grpc.php", line: 138,…}
2: {file: "/var/www/mydomain/vendor/google/cloud-logging/src/Logger.php", line: 412,…}
3: {file: "/var/www/mydomain/vendor/google/cloud-logging/src/Logger.php", line: 380, function: "writeBatch",…}
4: {,…}
5: {file: "/var/www/mydomain/vendor/monolog/monolog/src/Monolog/Handler/AbstractProcessingHandler.php",…}
6: {file: "/var/www/mydomain/vendor/monolog/monolog/src/Monolog/Logger.php", line: 323, function: "handle",…}
7: {file: "/var/www/mydomain/vendor/monolog/monolog/src/Monolog/Logger.php", line: 541,…}
8: {file: "/var/www/mydomain/vendor/laravel/framework/src/Illuminate/Log/Logger.php", line: 174,…}
9: {file: "/var/www/mydomain/vendor/laravel/framework/src/Illuminate/Log/Logger.php", line: 87,…}
10: {file: "/var/www/mydomain/vendor/laravel/framework/src/Illuminate/Log/LogManager.php", line: 547,…}
11: {file: "/var/www/mydomain/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php",…}
12: {file: "/var/www/mydomain/app/Exceptions/Handler.php", line: 41, function: "report",…}
13: {,…}
14: {function: "handleException", class: "Illuminate\Foundation\Bootstrap\HandleExceptions", type: "->"}

It's just a standard exception error.  Nothing that should cause a log channel to fail.  I think this is happening with all 500 errors that Laravel generates.

We are also using the following packages.  It could be a combination of things. We are not having any luck trying to narrow it down to just one package.
https://github.com/kreait/firebase-php
https://github.com/kreait/laravel-firebase


Only accumulate text if it exists

I was getting this error:
> complete_choice["text"] += choice.get("text") E TypeError: can only concatenate str (not "NoneType") to str

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks @anjor nice catch :)
There's an equivalent line in the chat_wrappers.py for streaming API there so maybe we can fix it there as well

Thanks! :)
https://github.com/traceloop/openllmetry/blob/ac3a41832e775a2dc8654b2c19078c52e5477394/packages/opentelemetry-instrumentation-openai/opentelemetry/instrumentation/openai/shared/chat_wrappers.py#L197-L198
That already seems to have the check?

@anjor released v0.12.3


WW-5355 Use W-TinyLfu cache by default

WW-5355
I see very limited advantage to using the default cache over the LRU one? The eviction process is faster but at the cost of having to repopulate the whole cache from scratch!
Keen to hear other thoughts or anything I may have missed
Perhaps in the future we can move to a more advanced algorithm such as the ones provided by Caffeine, although I'm not sure how effective they'd be given the cache can be easily attacked.
--
As per the comments, I will be changing the default cache to a W-TinyLfu cache one (as implemented by Caffeine) instead.

@JCgH4164838Gh792C124B5

fwiw, this would change from a concurrent cache to a synchronized one. It looks like the original code replaced an unbounded concurrent map. The performance difference may be unacceptable of explain the concern without benchmarks/profiling.
Caffeine is very resilient to attacks, like hash flooding and being scan resilient. An independent analysis might be of interest, An evaluation of cache management policies under workloads with malicious requests.

Good call out @ben-manes, I completely glossed over the change from concurrent map to synchronised map (and its performance implications).
And thank you for that analysis on resistance to attacks.
In that case I may just go ahead and integrate Caffeine as it seems rather straightforward anyway.

Thank you for the well considered review @JCgH4164838Gh792C124B5
Yep I no longer intend to make LRU (backed by a synchronised LinkedHashMap) the default given the performance implications. And yes I intend to keep the cache implementation configurable, even with the implementation of Caffeine.
I think choosing a default cache size will always be a challenge as it is subject to multiple application-specific factors so the best we can do here is to encourage developers to adjust the cache size as needed.

I found that previously, struts.ognl.expressionCacheLRUMode=true was not reliable due to setter injection not guaranteeing the order of operations. I've thus refactored the code to use constructor injection.

I've taken care to maintain full API compatibility given that these classes are extension points and thus public API

Thanks @ben-manes, amended!

@lukaszlenart I've updated the PR description :)


KAFKA-14588 [2/N] ConfigCommandTest rewritten in java

This is second part of #15839  refactoring.
PR intention - split big PR in parts to simplify review.
PR contains tests of ConfigCommandTest rewritten in java.
Full PR #15417
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hello @chia7712
Second part of ConfigCommandTest refactoring ready for review.
Please, take a look.

JFYI I’m offline till Monday.
Will fix all possible comments after.

Hello @chia7712
I'm back online :)
Do you have any other comments for this PR?


Form updates on payment don't update values

Changing payment type (early bird, etc) doesn't update the values on the form.

Fixed under other tickets.


2022.1 kr260 platform bitstream generation not permitted.

HI all,
I have request a evaluation license for TSN IP core and enable the license with vivado license manager.

But it still comes out following issue while I trying to build the platfrom.
make platform PFM=kr260_tsn_rs485pmod JOBS=4

Any idea about this issue?
Thanks,
JH

Hi all,
After few days, I rebuild the project, and the bit stream could be generate properly.
It might needs to reboot or rebuild the project after adding a new license
Thanks,
JH

big brain xilinx provides IP in example image that doesn't work for normal users. $30k IP... what a joke. Sent an email to sales, weeks later still nothing.


Call commands by full path

Tested on Fedora29, it needs command's full path in order to work properly

is the issue fixed if you define the PATH variable in the script instead?
might be a simpler fix.


Adding ByDiscardingBody() decorator.

This issue is detailed in #117

Question, would this func be included in all Responder funcs in the SDK, or just in the ones that do not use the response body?

Just ones that don't use the body. Though, in theory it shouldn't hurt to add it everywhere.


After integrating Cypress code coverage into Nuxt3, the app is not working properly.

I'm using the Vite Istanbul plugin to integrate cypress code coverage into my nuxt3 app. I'm getting the code coverage report, but my Nuxt3 app is not being compiled and is not functioning properly.
In our most recent version, we have the following code inside the Vite-Plugin-Istanbul folder:
transform(srcCode, id, options) {
      if (!enabled || options?.ssr || id.startsWith(MODULE_PREFIX) || id.startsWith(NULL_STRING)) {
        return;
      }
      if (testExclude.shouldInstrument(id)) {
        const sourceMap = sanitizeSourceMap(this.getCombinedSourcemap());
        const code = instrumenter.instrumentSync(srcCode, id, sourceMap);
        const map = instrumenter.lastSourceMap();
        return { code, map };
      }
    }

Though I'm getting options.ssr value as both true & false for different files, when I run npm run dev, my app does not run properly, and an error message appears on the console, as shown in the screenshot below.

Hi @belwalshubham, thanks for the issue.
I will look into reproducing the issue and find out why this is the case.
It might be that the server rendered code is still transformed in some way.
Or maybe the hydration is somehow transformed in some way.
If you could provide a reproduction for the problem this would speed up the process.
I'll see what i can do.

@iFaxity  Thanks for the response. Here are my steps.
Nuxt3 Vite support for Cypress coverage instrumentation
I was trying to instrument the project code using the vite-plugin-istanbul npm package.
Inside the package.json, here are my package dependencies.
"@cypress/code-coverage": "^3.10.0",
"vite-plugin-istanbul": "^3.0.4",

Here's my nuxt.config.ts after installing the vite-plugin-Istanbul package:
vite: {
  vue: {
    template: {
      transformAssetUrls: true
    }
  },
  plugins: [
    istanbul({
      exclude: ['node_modules', 'test/', 'coverage/'],
      extension: [ '.js', '.ts', '.vue' ],
      cypress: true
    }),
  ]
},

Here is my cypress/support/e2e.ts file.
import '@cypress/code-coverage/support'

Here is my cypress.config.ts file.
import { defineConfig } from "cypress"
export default defineConfig({
  projectId: "x83arq", // TODO: hide this
  e2e: {
    baseUrl: "http://localhost:3000",
    setupNodeEvents(on, config) {
      require("@cypress/code-coverage/task")(on, config)
      return config
    }
  }
})

After running npm run dev, my UI interface crashed and was not getting complied properly. and an error message appears on the console, as shown in the screenshot above.

However, when I run npx Cypress open, it displays my Cypress code coverage report after the test is completed, but the main issue is that my UI is not functioning and is not being compiled properly.

@belwalshubham Thanks for the detailed repro and the repro code. This will help me look into the issue. Big thanks ☺👍.
I'll try to look into it before new years.

okay @iFaxity  let me know if you get something related to this issue .

hey @iFaxity  any update on this issue ?

Hi, I've setup the and the app seems to be working (have some errors as I cannot setup the Prisma database. However the app loads the login view and that I can view at least.
Debugging these sorts of issues are tricky as the code that is produced is sometimes vastly different. As Istanbul transforms a lot of the code to generate coverage. However the code seems to be entirely different with some of the imports.
Without the istanbul plugin the application loads all the pages/components by importing them directly.
However when the plugin is enabled the pages gets imported using resolveComponent from Vue.
Seems really strange how the outcome of the code is this different.
I will dig around some more see what code is slotted into Istanbul and what comes out. Maybe the istanbul plugin somehow runs before Vue/Nuxt's plugins and this is why this happens.
But havn't debugged this sort of issue before, so I will try to do my best.
Image 1, without Istanbul plugin

Image 2, with istanbul plugin

hey @iFaxity  thanks for your response , In my case, I'm unable to login because my entire login page is not rendered, leaving a blank screen, and this error appears on my screen, as shown in the screenshot below.. I believe you're correct; perhaps the Istanbul plugin runs before Vue/plugins Nuxt's, which is why this occurs.

hey @iFaxity please let me know if you get anything on this .

Hello, I've managed to hopefully find a fix for this now.
By telling the istanbul instrumenter to not compress the code it seems to be working, as the imports are not squashed together with app.vue which fixes the issue.
I will publish a fix within a day for this, just have to run some tests first before I push anything.

Please try the fix by using the @next tag when installing the package.
npm i --save-dev vite-plugin-istanbul@next

hey @iFaxity, thank you, the problem has been resolved

@belwalshubham. Great!
I will try to get it out as a 4.0.0 release soon.
As for now its only in a RC release.


ImportError: cannot import name 'Undefined' from 'pydantic.fields' (/usr/local/lib/python3.10/dist-packages/pydantic/fields.py)

Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 14, in
from fastapi import FastAPI
File "/usr/local/lib/python3.10/dist-packages/fastapi/init.py", line 7, in
from .applications import FastAPI as FastAPI
File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 15, in
from fastapi import routing
File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 21, in
from fastapi import params
File "/usr/local/lib/python3.10/dist-packages/fastapi/params.py", line 4, in
from pydantic.fields import FieldInfo, Undefined
ImportError: cannot import name 'Undefined' from 'pydantic.fields' (/usr/local/lib/python3.10/dist-packages/pydantic/fields.py)
I'm still using the Collab, as everything was still working fine up until today. Tried a fresh install, but that didn't remove the error.

Same thing, last cell in Google Collab
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 14, in
from fastapi import FastAPI
File "/usr/local/lib/python3.10/dist-packages/fastapi/init.py", line 7, in
from .applications import FastAPI as FastAPI
File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 15, in
from fastapi import routing
File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 21, in
from fastapi import params
File "/usr/local/lib/python3.10/dist-packages/fastapi/params.py", line 4, in
from pydantic.fields import FieldInfo, Undefined
ImportError: cannot import name 'Undefined' from 'pydantic.fields' (/usr/local/lib/python3.10/dist-packages/pydantic/fields.py)

maybe need pydantic

Same here. It was working about a half hour ago. Now, it is returning this error too.
I'm a Colab Pro user, btw.

Running into the same exact issue everyone here is reporting! Things were working last night, now they are no longer working, showing the same Pydantic error. Fresh install didn't change anything - something up with Pydantic?

fixed, update to the latest notebook

yep that fixed it for me, thank you!

@Jboby1 @mcqx4
I have encountered a similar event.
I tried pip install again, but it didn't improve the situation.
!pip install rembg --upgrade
!pip install pydantic --upgrade
!pip install fastapi --upgrade

Traceback (most recent call last):
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 14, in <module>
    from fastapi import FastAPI
  File "/usr/local/lib/python3.10/dist-packages/fastapi/__init__.py", line 7, in <module>
    from .applications import FastAPI as FastAPI
  File "/usr/local/lib/python3.10/dist-packages/fastapi/applications.py", line 15, in <module>
    from fastapi import routing
  File "/usr/local/lib/python3.10/dist-packages/fastapi/routing.py", line 21, in <module>
    from fastapi import params
  File "/usr/local/lib/python3.10/dist-packages/fastapi/params.py", line 4, in <module>
    from pydantic.fields import FieldInfo, Undefined
ImportError: cannot import name 'Undefined' from 'pydantic.fields' (/usr/local/lib/python3.10/dist-packages/pydantic/fields.py)

I will try this too!
https://github.com/TheLastBen/fast-stable-diffusion/issues/2468#issuecomment-1675157971

🤔
https://github.com/AUTOMATIC1111/stable-diffusion-webui/pull/12392

pip install pydantic==1.10.11

or
Latest version of 1.x series
pip install pydantic==1.8.2

I solved it this way 👌
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/11853#issuecomment-1646782938

Just use the latest notebook

Basta usar o notebook mais recente

I'm having the same problem for hours now with my google colab, the code just stops and gets stuck on that last line:
Installing pycloudflared
Launching Web UI with arguments: --share --disable-safe-unpickle --no-half-vae --xformers --enable-insecure-extension --gradio-queue
2023-08-12 00:24:09.592789: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2023-08-12 00:24:10.690399: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
Additional Network extension not installed, Only hijack built-in lora
LoCon Extension hijack built-in lora successfully
*** Error loading script: api.py
Traceback (most recent call last):
File "/content/microsoftexcel/modules/scripts.py", line 319, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/microsoftexcel/modules/script_loading.py", line 10, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/api.py", line 8, in
from modules.api.models import *
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config

*** Error loading script: batch_hijack.py
Traceback (most recent call last):
File "/content/microsoftexcel/modules/scripts.py", line 319, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/microsoftexcel/modules/script_loading.py", line 10, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/batch_hijack.py", line 7, in
from scripts import external_code
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/external_code.py", line 1, in
from internal_controlnet.external_code import *
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/internal_controlnet/external_code.py", line 9, in
from modules.api import api
File "/content/microsoftexcel/modules/api/api.py", line 19, in
from modules.api import models
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config

*** Error loading script: controlnet.py
Traceback (most recent call last):
File "/content/microsoftexcel/modules/scripts.py", line 319, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/microsoftexcel/modules/script_loading.py", line 10, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/controlnet.py", line 13, in
from scripts import global_state, hook, external_code, processor, batch_hijack, controlnet_version, utils
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/external_code.py", line 1, in
from internal_controlnet.external_code import *
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/internal_controlnet/external_code.py", line 9, in
from modules.api import api
File "/content/microsoftexcel/modules/api/api.py", line 19, in
from modules.api import models
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config

2023-08-12 00:24:21,667 - ControlNet - INFO - ControlNet v1.1.237
*** Error loading script: external_code.py
Traceback (most recent call last):
File "/content/microsoftexcel/modules/scripts.py", line 319, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/microsoftexcel/modules/script_loading.py", line 10, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/external_code.py", line 1, in
from internal_controlnet.external_code import *
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/internal_controlnet/external_code.py", line 9, in
from modules.api import api
File "/content/microsoftexcel/modules/api/api.py", line 19, in
from modules.api import models
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config

*** Error loading script: xyz_grid_support.py
Traceback (most recent call last):
File "/content/microsoftexcel/modules/scripts.py", line 319, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/microsoftexcel/modules/script_loading.py", line 10, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/xyz_grid_support.py", line 8, in
from scripts.external_code import ResizeMode, ControlMode
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/scripts/external_code.py", line 1, in
from internal_controlnet.external_code import *
File "/content/microsoftexcel/extensions/microsoftexcel-controlnet/internal_controlnet/external_code.py", line 9, in
from modules.api import api
File "/content/microsoftexcel/modules/api/api.py", line 19, in
from modules.api import models
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config

Calculating sha256 for /content/microsoftexcel/models/Stable-diffusion/chilloutmixni.safetensors: Traceback (most recent call last):
File "/content/microsoftexcel/launch.py", line 39, in
main()
File "/content/microsoftexcel/launch.py", line 35, in main
start()
File "/content/microsoftexcel/modules/launch_utils.py", line 394, in start
webui.webui()
File "/content/microsoftexcel/webui.py", line 393, in webui
shared.demo = modules.ui.create_ui()
File "/content/microsoftexcel/modules/ui.py", line 504, in create_ui
modules.scripts.scripts_txt2img.setup_ui_for_section(category)
File "/content/microsoftexcel/modules/scripts.py", line 433, in setup_ui_for_section
self.create_script_ui(script)
File "/content/microsoftexcel/modules/scripts.py", line 383, in create_script_ui
import modules.api.models as api_models
File "/content/microsoftexcel/modules/api/models.py", line 112, in
).generate_model()
File "/content/microsoftexcel/modules/api/models.py", line 97, in generate_model
DynamicModel.config.allow_population_by_field_name = True
File "/usr/local/lib/python3.10/dist-packages/pydantic/_internal/_model_construction.py", line 205, in getattr
raise AttributeError(item)
AttributeError: config
fc2511737a54c5e80b89ab03e0ab4b98d051ab187f92860f3cd664dc9d08b271
Loading weights [fc2511737a] from /content/microsoftexcel/models/Stable-diffusion/chilloutmixni.safetensors
Creating model from config: /content/microsoftexcel/configs/v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.

Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/charturnerv2.pt: a91b570185766ff71f242f83d5beb6d658348900edb706a2092ba23d6e1e2cf8
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad-picture-chill-75v.pt: 7d9cc5f549d7972f24803a3a9880a923fb9a1b68c1443da3ce1ff2f7eff25ae9
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad_prompt.pt: f9dfe1c982e2a1917054fa827ee1f981c6e6102984f981c691e4f8c817e292cb
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/ulzzang-6500.pt: 66d481a222ee4638e254a411890f2a8716e4ce5c3e1b1957891c7628bbdeac78
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad-artist.pt: 2d356134903e8f47bf6cf519bdf577cdcee42fc717ef264498162e94f130843a
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/pureerosface_v1.pt: dedb4322e42e360fe01775ba817be03ac6a6c307744562bb0d6759368bc681da
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad-image-v2-39000.pt: 5b9281d7c6adc221b8ea9067b678f4b6ff4cc94735e2d50885070380d5496037
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/21charturnerv2.pt: f253abb016c22dd426d6e482f4f8c3960766de6e4c02f151478bfb98f6985383
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/ng_deepnegative_v1_75t.pt: 54e7e4826d53949a3d0dde40aea023b1e456a618c608a7630e3999fd38f93245
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/epiCNegative.pt: 88b8f468357be0d90b993b6b5b4763b603244089b426f40fddcf96b070002f38
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad-hands-5.pt: aa7651be154c46a2f4868788ef84a92b3083b0c0c5c46f5012a56698bfd2a1ba
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/negative_hand-neg.pt: 73b524a2da121eb1b7ad04dea11da286277813120700ff8f1d8522516f7b30ab
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/nfixer.pt: aa5a14f467a8cb8660e92e97ca647ab90ef3aa00dc6da842ab735170347f78c7
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/Asian-Less-Neg.pt: 22d2f003e76f94dcf891b821a3f447f25c73b2e0542f089427b33ff344070a96
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/EasyNegativeV2.safetensors: 339cc9210f70ef842b716588373d95b52351d7e6d111b858e133e3b1e3bd8088
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/UnrealisticDream.pt: a77451e7ea075c7f72d488d2b740b3d3970c671c0ac39dd3155f3c3b129df959
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/rmadanegative402_sd15-neg.pt: ad488e18aa29f12e8fc18d1d2ccc041ff0052d4657c96f1b06cab880f4ba4f40
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad_pictures.pt: 522ac70ba997df4a911e4977e6a9790e7d15236596e8e0c8318330f2af4ab095
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/nartfixer.pt: a0504f05844290ac4d2de41d0338fb642548fb18efd8c6de7bb571ab1d60af89
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/nrealfixer.pt: d1193a5ecddb3b5b052f5efb1a74062dcd130a4060884eed439a605b9731c0ad
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/epiCRealism.pt:<PHONE_NUMBER>e4183d01f3aa7737ce952d15fc9e21da13fa0ecea1be4e8c166b10
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/BadDream.pt: 758aac44351557ccfae2fc6bdf3a29670464e4e4eabb61f08c5b8531c221649c
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/FastNegativeEmbedding.pt: 687b669d8234a418005ca9bfda93464b1721285b0a6a8d92490df0f02124ab7c
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/HyperStylizeV6.pt: a09539451c9161038c9ac0a322ad8ffafffb097a70874b65e31eb06f0bb2e412
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/CyberRealistic_Negative-neg.pt: 65f3ea567c04c22f92024c5b55cbeca580bc330c4290aeb647ebd86273b3ffb8
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad_prompt_version2.pt: 6f35e7dd816ae04bb3f774a9a17ebfbc50c0e3a53f69a9a40bed05936d3a3812
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/easynegative.safetensors: c74b4e810b030f6b75fde959e2db678c268d07115b85356d3c0138ba5eb42340
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/ulzzang-6500-v1.1.bin: 8c1af299c7e8c2283892a7ad61a5fe5574e88c9c2ee77cd0cdfc0615155fa315
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/badhandv4.pt: 5e40d722fc3d0c2decb62debfaf8058db30ccdae9ab00ff64b183907b435708e
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/verybadimagenegative_v1.3.pt: d70463f87042e2b5951c303542f3e171cf49af9b7df53b2f20779493786eb143
Calculating sha256 for /content/microsoftexcel/embeddings/embeddings/bad-artist-anime.pt: 5f7bea88750c97a0b8c9ba9f5bc0d13648c3a17a69aaac855903229d5f58c34b
Model loaded in 41.8s (calculate hash: 26.6s, load weights from disk: 0.6s, create model: 5.2s, apply weights to model: 5.1s, apply half(): 1.7s, move model to device: 1.8s, load textual inversion embeddings: 0.2s, calculate empty prompt: 0.5s).

@DohkoKlaus
Just use the latest notebook 😄
This commit seems to have resolved the issue.
https://github.com/TheLastBen/fast-stable-diffusion/commit/29b93fe5177246da92bab813e38c6044c36c8e89

@Jboby1 @mcqx4
pip install pydantic==1.10.11

or Latest version of 1.x series
pip install pydantic==1.8.2

I solved it this way 👌

this error happens after installed the controlnet extension, and this method cannot fix it for me, do you have any suggestion?

Hi guys, sorry in advance, I'm very much a noob to all this, is there a simple fix for this? I've spent hours trying fix this for this error:
ImportError: cannot import name 'Undefined' from 'pydantic.fields'
I've tried the fix above, and many other fixes involving modifying the 'requirements.txt' file, replacing the 'webui.py' file with fixed version, and I'm still banging my head against a wall with this error.
Can someone please advise what I might be missing? I have A1111 installed, and it works fine. Forge on the otherhand doesn't.
Cheers
Mark

ImportError: cannot import name 'Undefined' from 'pydantic.fields'
I've tried the fix above, and many other fixes involving modifying the 'requirements.txt' file, replacing the 'webui.py' file with fixed version, and I'm still banging my head against a wall with this error.
Can someone please advise what I might be missing? I have A1111 installed, and it works fine. Forge on the otherhand doesn't.

I'm having the exact same issue anytime I try to open Forge. Likewise, A1111 works fine.


fix: remove css override of white background on darkmode

@NoamGaash
Fix description:
Remove css override for white background that makes text unreadable while on Darkmode
How to test:

Go Dashboard/Gap patterns page
select start date that is earlier than end date.
A new Alert message should appear above the dates picker with validation error.
Change to Dark mode and check that background of the validation error alert is not white and that the message is clear.

Thank you!

@YuvalMasada when saving new baselines in the main branch, Eyes performs a conflicts check. I've probably misconfigured something, but the potential conflicts doesn't concern me. feel free to merge


Key generation with backup flow

When generating keys the following flow should be implemented.

Generate keys
User enters 6 digit pin code
User enters 8 digit+ passphrase (include strength meter & possibly a HIBP check)
AES256 encrypt keys + address using passphrase
Post to TIKI's backup service the hashed email, hashed pin code, and encrypted keys

implemented in https://github.com/tiki/login


如何让flutter编译出来的web，每个页面的链接都不一样？How do you get flutter to compile the web so that each page has a different link? Because I need to do a sharing function, to share the current page to others, and hope that others will open the product details page instead of the home page？

如何让flutter编译出来的web，每个页面的链接都不一样？因为我需要做一个分享功能，把当前页面分享给别人，希望别人打开后是商品详情页面而不是主页？
How do you get flutter to compile the web so that each page has a different link? Because I need to do a sharing function, to share the current page to others, and hope that others will open the product details page instead of the home page？

Use named routes for all the navigation and the name of the route will be added to the as a parameter to the links.
refer this for details on how to add named routes https://flutter.dev/docs/cookbook/navigation/named-routes

Hi @bianxiang
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Components Framework Error

Hello @pepcots,
I was fixing the Component framework of your Engine and I trembled with a strange error. All the commented code is in the COMPONENTS branch of our engine as I don't want to merge it yet until it works perfectly fine.
The thing is that Components are created in the ModelLoader::loadfromFile() method that returns a GameObject with its necessary components but once I try to add this GameObject as a child of scene->root (using emplaceChild) I find that the Components of the added GameObject have lost their owner pointer (that points to the GameObject created with them). The pointer is not NULL but is instead an strange name that I suspect is binary or something similar.
The Error happens when I call the method owner()->GetComponent() and does not find the Component because the owner() returns something strange. The catch here is that the owner()->GetComponent() that ends the code is one in the Mesh::drawModel() function but (strangely) is not the first I call.
I think that the problem lies in that in some point the code is not correctly moving the pointers but I am unable to find where or why.
Thank you,
Pol Celaya

Hi @pcelaya !
A part of moving the components you have to reasign the owner of the components.
If you can not do that, due to the owner being a reference, try with a pointer instead.


Fix refresh token flow in OIDC accounting for cookie split

Description
This PR fixes an issue with the refresh token workflow for OIDC after cookie splitting was introduced in 2.7.0. (Link to PR where cookie splitting was introduced: https://github.com/opensearch-project/security-dashboards-plugin/pull/1352)
The reason the flow was not working was because in the OIDC flow it would refresh the token in the isValidCookie call here. The implementation of isValidCookie in oidc_auth.ts calls on setExtraAuthStorage to save the new access token and split it into multiple cookies.
setExtraAuthStorage(
  request,
  `Bearer ${refreshTokenResponse.idToken}`,
  this.getExtraAuthStorageOptions()
);

Later on in authentication_type.ts it calls on buildAuthHeaderFromCookie which calls on getExtraAuthStorageValue to unsplit the cookies.
extraValue = getExtraAuthStorageValue(request, this.getExtraAuthStorageOptions());

When operated on the same request object, the getter to get the new access token is not fetching the updated value. This PR makes it so that it does not rely on cookie splitting on the request where the access token is refreshed.
Category
[Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation]
Bug fix
Issues Resolved
https://github.com/opensearch-project/security-dashboards-plugin/issues/1522
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @cwperks! First of all, my apologies for this regression. I'm quite surprised I haven't been bitten by this before - as you describe, when accessing the cookie within the same request, it still holds the previous value.
Thanks for looking into this!
I did come up with an alternative solution that I'd like to run by you. It does unfortunately include accessing the raw Hapi objects, but we already do that within the cookie splitting code, so I guess one more place doesn't hurt.
To my understanding, the Hapi request objects holds the cookie values in two different objects:

state
_states

state is what you get after the cookie header is parsed and I believe this is used when you get the cookie value via the sessionStorageFactory
_states is what is used internally by Hapi whenever a cookie is set
That said - when you set the cookie via the sessionStorageFactory it seems like the state object isn't updated with the new value and, like you noticed, you would still get the old cookie value even if you use sessionStorageFactory.asScoped(request).get() again to retrieve the cookie.
Instead, the new value resides in the _states object (and for the auth cookie also in request.auth.artifacts).
Then, upon the next request, the _states object is "flushed" and state is updated with the values from _states.
I haven't gone through all Hapi code yet, and I'm not sure when/how _states is flushed, so feel free to correct me if I'm wrong :)
Anyhow, with that in mind, we can change these lines https://github.com/opensearch-project/security-dashboards-plugin/blob/main/server/session/cookie_splitter.ts#L142-L144
into
if (rawRequest._states[cookieName]) {
     // Set if the value has been updated within the same request
      fullCookieValue = fullCookieValue + rawRequest._states[cookieName].value;
    } else if (rawRequest.state[cookieName]) {
      fullCookieValue = fullCookieValue + rawRequest.state[cookieName];
    }

The .value comes from the _states object looking like this as opposed to state's key: value:
cookie_name_abc: {
    name: 'cookie_name_abc',
    value: 'eJyrblablasomething'
  },

With this in place, all other changes can be dropped/reverted, which I'd say is the main advantage.
I've tested this locally, and I've also tested to make sure it doesn't affect any existing cookies (re: backwards compatibility).
I would appreciate your input on this - do you think this approach is worth pursuing?
If yes, we could discuss adding some more error handling and also how to test this properly so that regressions like this one doesn't happen again. And again, I'm very sorry for this. I did test the refresh flow, but must have done something wrong.

@jochen-kressin Thank you very much for the detailed explanation and proposed patch! I would be in favor of referencing the value from _states  given that this repo is already relying on the raw request, but I'd also like input from others as well.
@peternied @davidlago @RyanL1997 @scrawfor99 @cliu123 Any thoughts on relying on the raw _states (internal to hapi) to get the most update to date value after token refresh?

@jochen-kressin thanks for the detailed response, I'm sold

With this in place, all other changes can be dropped/reverted, which I'd say is the main advantage.

With this :100: % on board

@cwperks I'm onboard this too. Should we close this in lieu of @jochen-kressin 's PR?

Closing in favor of https://github.com/opensearch-project/security-dashboards-plugin/pull/1580


Don't hardcode prefix on version string

Don't prefixed user specified version with a "v", user should enter the exact version string.

I see this is due to the prefix mismatch between the releases and the packaging.

The PR attached will allow the user to enter in both v0.0.1 and 0.0.1 and it will work the same. If the the releases of the debugger file names to be something like daffodil-debugger-v0.0.5 then all that is need is to remove the .substring(1) attached to dapodilDebuggerVersion and now it will work with that. However for the input of task to run the debugger you string must enter a version 0.0.1 and will need to unless the zip file names end up getting changed.