finish migrating compiled package to Ceylon

Need to debug this commit ceylon/ceylon-ide-intellij@676d9cb.

Note that the work in @beae534653155b994d4eeeaf115e90c62d8ef676 and @3477731f718a7c830109be42fb22d90bc065a16f needs to be ported to the migrate_compiled branch.

I cherry picked your commit and fixed the conflicts that appeared on master, but didn't find any bug. I called Invalidate Caches + Restart, and everything was reindexed correctly.


Archive Failing

Whenever I archive with your SPM it fails. I was doing a little reading into the matter, and it seems that you're missing some things in your Package.swift file that is causing the problem.
platforms: [
.iOS(.v15)
],

Check the new release.
Please tell me if the error persists.


Put Error when using special symbol

When I put file to S3, if the path have special symbol (@ or chinese), it will fail and got following error message
S3 put error :  "SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method."
S3 put error :  "Error downloading<EMAIL_ADDRESS>- server replied: Forbidden"
Have someone encounter the same issue?
Please help me
Thanks.

Hello~ anybody here?


fix: articles/security/azure-security-threat-modeling-tool-cryptography.md

add missing code fence language
unescaped < character

@nschonni @jegeib - We're in the process of pulling this commit to the private repository so we can verify the updates on staging. We'll post a new private repo PR # shortly and then close this PR.

moved to https://github.com/MicrosoftDocs/azure-docs-pr/pull/65005


Julia 0.5->0.6

Hello,
This https://github.com/JuliaLang/julia/blob/release-0.6/NEWS.md should help migrating code from Julia 0.5 to 0.6
Using this GitHub bot
https://github.com/JuliaComputing/FemtoCleaner.jl
should help to remove a lot of deprecated syntax.
Here is build status https://travis-ci.org/aimacode/aima-julia/jobs/293646584
Kind regards

@femtotrader I have fixed all deprecation warnings encountered between v0.5 and v0.6 for Base.Test tests.


Feedback for “Public Goods Network”

hı team. it is my adress: 0x31EA583ac65CB402800979110Cc83025571ea810
8 days ago I used the mainnet pgn network. Everything seemed fine until I made a request to withdraw my money again while I was trading. yes, I know it will take 7 days, but it's been 8 days and it still hasn't arrived. I have about $45 ethereum left in the network. I also want to ask one thing. Do I need to prove the money to return to my layer 1 account. The room asks for a fee of 8 dollars. can you help me please?

We have instructions on this stated in our documentation and our Telegram channel:
https://docs.publicgoods.network/using-pgn/bridging-eth-to-pgn
Please make sure to review our available content before opening up issues like this.


apply travis only for master branch

I've enabled the github actions for Pull Requests here https://github.com/webpack/webpack.js.org/blob/master/.github/workflows/testing.yml, and we'll monitor it for a while before migrating those travis jobs running against pull requests to github actions.
As you can see in this PR that I'm currently keeping the job of master branch building to travis as it won't run frequently. Hopefully we can migrate it too in near future.

It's been 7 days since we enabled Github Actions. So far so good. I think it's time to merge this PR.


Question on Use Case

Would a use case be something where you have a chain of restaurants and you need an owner, a manager who may manage 1 or more locations (see reports and add employees to their locations only), and an employee who works at but doesn't manage 1 or more locations (no reports but submits when they last cleaned the grill for example)?  Would the Roles and Permissions work for that, or is there another way to integrate PHP-Auth into a hierarchy based system like that? Is there a best practice to integrate custom data like the list of restaurants in this case?

What you want is authorization, which is part of this library (in the form of the roles and permissions), as you suggested. So that would work.
But do you want authentication as well? That is, do you want employees/managers/owners to authenticate with a combination of email and password or username and password? Usually you want that. Because you can’t really have authorization if you have no authentication and thus cannot be sure who the user really is. For example, without authentication, the employee could just switch to the owner role. This library here has authentication – it’s the main part even.
As for your custom data like a list of restaurants, this is completely independent of this library. You can put your data into separate database tables and access it as you would without this library. Just wrap some checks with this library around the accesses.
Does that help?

Yes, that helps a lot. Thank you.  We do want both authentication and authorization and only really have basic authentication right now, so moving to PHP-Auth for authentication would definitely help make that more robust (and likely more secure and more tested) and adding in the authorization but not being limited by custom data sounds great.  I look forward to diving into this library and appreciate your work and helpfulness here!

Sounds good. Thank you!


Integration: Improve Chunk splitter + Relationships between chunks for python files / repositories

Description
A new feature has been added using rag-pychunk: Python Library to chunk your python files levereging the python programming language to improve two things:

Chunk size: make your chunk size dynamic, keeping in the same chunk a hole funcion, a hole class method, a hole class and block of code.
Chunk relationships: create relationships between your chunks other than Parent-Child and Prev-Next. NodeRelationship.REFERENCE has been created, which will include these relationships. These type of relationship can be used as well for example in pdfs when a chunk is referencing another chunk (example: In section 3.7 there is an explanation ... -> section 3.7 will need to be a NodeRelationship.REFERENCE for "self" node).

Motivation: leverage python programming language syntax to improve the Chunking + relationship part of the RAG pipeline. This logic can be used for all programming languages, since all of them have a defined syntax.
New dependency: rag-pychunk library.
Fixes # (issue)
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[x] No

Type of Change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Added new notebook (that tests end-to-end)

Suggested Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

I'm not sure we NEED to add a new relationship type for this? Wouldn't the property relationship just be parent or source?
I also think this should go as a new integration, rather than in core (i.e. in llama-index-integrations/node_parser)

I think it is needed because of this:

Imagine you have a class, let's call it class A, and it has several methods: method a1, a2, .... The methods will be child nodes of the parent node class A. Now imagine that the method a2 is called inside the method a1. If the Class A is the parent for both of this methods it wouldn't make sense to use the parent relationship to describe how these two methods are related.
Now imagine the following: you have two functions, function X and function Y. The function Y is called inside function X. Here it wouldn't make sense either to have a PARENT-CHILD relationship between those node. This situation would also apply for the Class A and its methods of the previous example: what if the class A is called in another file? What if its methods are called in other files?

If the relationship SOURCE is suited for this kind of relationships then it would not be needed to create REFERENCE relationships. But if SOURCE only describes: where does self node belong? Then, it would be better to define REFERENCE because of the situations I've explained above.


DOC: one can also run bbknn before louvain

It's definitely good to mention that the connectivity matrix can be provided another way. However, I'm not sure this function actually requires either of those, since you can pass the adjacency matrix.

Yup. I clarified that as well and merged it.


Consider rebasing "Main" branch as the large files in the history are clogging up cloning the repository

Looking at the commit history, lots of large files have been moved around the repository, this has caused the git history to be come clogged up and ridiculously oversized.
It took an extra ordinate amount of time to clone the project and longer to filter to the main branch.
Please consider rebasing to clear-out the history and move the "non-addressables" branch to a separate repo (linked) to save developers time cloning the project to investigate it.
P.S.
Great work on the project, looks awesome.

Hi,
When you mention extra ordinate amount of time to clone and filter, do you have more specifics time values? On our side it takes about 6-8minutes, considering that it's a large repo due to the assets it seems reasonable. Do you have to wait way longer than that?
As for the history, it's 6 commits (as of this moment) and the large files haven't moved since the initial commit. If you can provide more details, we will be happy to look into it more specifically.
We are glad you enjoy the project and we want to make sure you have the best experience testing it out.

Granted yes, the project is large with some large assets, but the git size is doubled due to the retention of the "pre-addressables" branch as well.
I'd recommend splitting out the "pre-addressables" branch in to a separate repo, then rebasing this branch based on its latest commit.  This should considerably cut down the size of the repo and speed up access to it.
(or drop/recreate the repo, links should be preserved, with just the current state)

Hi @SimonDarksideJ,
Thanks for the additional information. After looking more in depth about what you are reporting. What you are seeing is due to the use of git lfs, for the large file storage. In short, the lfs files are stored in the .git/lfs directory and they are also placed in the working directory where they are reference, which in the end does cause the whole clone directory to be 2x the lfs files plus the other files that aren't tracked by LFS. This also means that when any changes is done to a file tracked by lfs, only the referred lfs file will be downloaded instead of each iteration of a same file.
The non-addressables branch references the same lfs files and therefore doesn't add to the size. I want to note that most files from that branch have not been modified and are referencing the same version of the file.
You can find more information about git lfs here.
When cloning the repository clean, we see the directory with a size of 27.8 GB (which is what we expect from our above explanation), do you have a different experience?
We hope that this gives you a bit more clarity on the state you are seeing.

Fair enough, best to update the Readme to set consumers expectations for what they will be seeing/getting


Removed outdated deprecations

Fixes https://github.com/CesiumGS/cesium/issues/10355
Looks like we missed removing a handful of deprecations slated for a previous release. This removes Cesium3DTilesStyle.ready, Cesium3DTilesStyle.readyPromise, and Resource or string parameters for the Cesium3DTilesStyle constructor.

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.

Thanks @sanjeetsuhag. Updated the source code and the related specs.


Some gameplay related cvars changed

I changed some cvars because, in my opinion, the values that I choosed it's better for the gameplay.
download_all - because some community servers have custom sounds/models, like Freak Fortress 2 servers.
tf_hud_target_id_alpha - value 255 because it's better to see people info when playing (teammates or enemies if you are a Spy).
tf_medieval_thirdperson - value 0 because it's hard to trickstab when playing with the Spy and also when playing as Sniper with the Huntsman.
tf_dingalingaling and tf_dingalingaling_lasthit - value 1 for the two options because it will help newbies in the game.

mastercoms, I will close this pull request. There is anything else you want to say?

There are still changes that I can merge from here, I don't think it should be closed.

Thank you for your contribution to mastercomfig!


Initial data store function & class

This just adds the store to the repo and includes it so it can be used when refactoring / adding new features.

Coverage increased (+1.5%) to 83.568% when pulling 382b4fde2f3db889f95f5f4f6b35e15beb02fa13 on store into 400970da3948a1c70f45faf39261d92b04fcad89 on master.


exporting to fbx error

Hi there, when I tried exporting the npz file to fbx a weird error occurred...
KeyError: 'bpy_prop_collection[key]: key "f_avg_Pelvis" not found'
Error: Python script failed, check the message in the system console

Please make sure that you have downloaded the SMPL_m_unityDoubleBlends_lbs_10_scale5_207_v1.0.0.fbx from the official website. The bug is obvious. It reports that the joint name mismatching. You can directly check the name of your fbx in Blender.

Yeah, I have already downloaded  SMPL_f_unityDoubleBlends_lbs_10_scale5_207_v1.0.0.fbx and  SMPL_m_unityDoubleBlends_lbs_10_scale5_207_v1.0.0.fbx and yet I get this bug

Sorry for the unpleasant bugs. I have tested the code again. I can't re-implement your bugs.
This is the fbx I used. Hope it can help you.

Thanks!


Rename repositories.txt to https:/github.com/arduino-libraries/Servo

Hello @percyee472. If you will provide a detailed description of what you were trying to accomplish I'll be happy to help you out with it.


Create stream in an atomic transaction

create_stream_if_needed does:
https://github.com/zulip/zulip/blob/862061fa53ad085e1a528a26cc89e636485fb0b9/zerver/lib/streams.py#L105-L125
This has a window when the newly-created stream has no Recipient object, which can lead to odd exceptions.  We should create the interconnected Stream and Recipient objects in a single transaction, so that other reads can't find a stream with inconsistent state.

@mateuszmandera @abhijeetbodas2001 FYI.

Can I work on this issue?

@zulipbot claim!!


drop calendar is not on production?

but on canary works

seems prod worker is not up to date

seems prod worker is not up to date

@preschian

TYSM


Use Docker Compose to link apps

This deployment could probably use Docker Compose to link the apps. I'm just starting with Docker Compose, but it looks like this would be a good use case.

Oops, I didn't notice the Docker Compose config in sample/docker-compose.yml. 👍


DSM factory reset did not erase the M2 storage pool

Not sure if bug or feature, I'm testing my new DS423+ NAS and have been trying a number of things, included this fantastic script.
After satisfied with my testing I did a factory reset to start clean with the final config. I expected the M2 storage pool to be erased like the rest of SP created by DSM but no, after the setup was completed the M2 storage pool was there, safe and sound.
This kind of reset persistence is kind of scary. How is it possible?
DS423+ with Synology DSM 7.2.2-72806.
WD SN700 with 11150WD firmware, 4k native enabled.

It would seem to be bug, or feature, in DSM itself.
Can you run https://github.com/007revad/Synology_HDD_db then reboot and create the M2 storage pool and volume in storage manager. Then reset again and see if DSM deletes the M2 storage pool.
By the way, with a DS423+ you should use Synology_HDD_db instead of Synology_M2_volume

OK, I'll try that!

By the way, with a DS423+ you should use Synology_HDD_db instead of Synology_M2_volume

Really? I undestood that Synology_M2_volume was the main tool and Synology_HDD_db was to fix the SP after DSM updates plus some extras, seems I got it wrong.

So I did as explained.

Removed the M2 Storage Pool created by Synology_M2_volume
Cannot create new M2 SP due to non compatible drives.
Run Synology_HDD_db
Now I can create a M2 storage pool.
Factory reset
M2 storage pool is still there.
Remove the M2 storage pool.
Cannot create new M2 SP due to non compatible drives.

So it seems DSM will not touch the M2 storage pool in a factory reset, it only removes and overwrites the SPs in HDD drives. After factory reset it will just detect the M2 SP it and continue using it. Changes made by Synology_HDD_db are indeed reset.
So it is a you said a DSM thing. TBH I would prefer a factory reset to actually remove everything but has nothing to do with Synology_HDD_db or Synology_M2_volume, the scripts work perfectly.
Thanks for clarifying!

By the way, with a DS423+ you should use Synology_HDD_db instead of Synology_M2_volume

Really? I undestood that Synology_M2_volume was the main tool and Synology_HDD_db was to fix the SP after DSM updates plus some extras, seems I got it wrong.

Models that officially support M2 volumes


Special-case the Pants repo.

Until the scie-pants binary can actually be used by Pants developers in the Pants repo, it would be good if it could detect it was running in the Pants repo.
Perhaps with:
[bootstrap]
delegate = true

And then just run the ./pants script in the Pants repo.

If the goal is to make the ./pants script redundant, I think it would be better to just warn/error out, in lieu of an extra configuration which needs docs and a breaking config change if we want to eliminate it eventually.
If the goal is to always keep the ./pants script, then this feature would be nice.

I think it would be better to just warn/error out

The thing is, to warn / error out, there needs to be some signal. I was suggesting [bootstrap] delegate = true is that signal. Once you have the signal, you just call ./pants blindly. I don't see the need for docs - there is exactly 1 repo on earth that will have the knob and then remove the knob. The knob would not be documented in Pants, it would just not be aggressively errored out on as unknown. Could name it _delegate, __DELEGATE_YOU_DO_NOT_WANT_THIS_OPTION_IF_YOU_ARE_NOT_ME__ - what have you.

We could make the signal a marker file of some sort - anything. It just needs some cooperation from the Pants repo so I don't have to add crazy tea-leaf reading logic to scie-pants in the hot path.

I was originally wondering if maybe there was auto-delegation to a local ./pants script (regardless if it was the Pants mainline repo or not. But then something in the back of my head doesn't like blindly calling bash scripts by collocated name.
However, having that explicit
[bootstrap]
delegate = true

does make that concern go away 🤷🏽

The knob would not be documented in Pants

That's a good point - it doesn't need to be documented, because it's not really a user-facing API.

Ok, cool. Yeah, the scie-pants already suffers the cost of parsing pants.toml; so having the signal be there is definitely the most efficient and clear cut / will incur the least tech debt.

Counterpoint - running a pants release on the Pants repo allows Pants to be self-hosting, which has interesting benefits. E.g., once we add Rust support we could build the engine with Pants, and enjoy remote caching etc.
So if that's a direction we want to go in, maybe running pants in the pants repo should do what it implies.

I'm not sure I follow the "self-hosting" argument.
Are you suggesting that pants ... should invoke Pants as a regular project where as ./pants ... would be the development invocation to run Pants with the sources from disk as we do now?
If so, I would humbly suggest renaming so we have ./pants_from_sources .. or something similar to have it distinctly different from the regular invocation style of pants ...

Yeah, I'm suggesting that pants in the pants repo should run a pants release, and ./pants should do what ./pants_from_sources does in every other repo that has it, so I'd be fine renaming it. But other people may have other opinions on this... So I'm not suggesting we do either thing without buy-in.

Also, the linked PR suggests having scie pants delegate to ./pants as an opt-in feature, so we can do that first without closing the door on this down the line..

So if that's a direction we want to go in, maybe running pants in the pants repo should do what it implies.

Finishing that thought, it then needs to error if pants_version is not set in the Pants repo (or set it to latest stable). How exactly is that supposed to work @benjyw with our generally out of control deprecation cycles? Do we set pants_version to the latest mainline release with every mainline (~dev) release? And then if a new option is added + used in Pants own pants.toml do all devs who pull the new option on main find out with a config error and then switch to pants from sources?

FWIW I'm currently hacking on #30 which makes this even more untenable. At that point pants is pants_from_sources and it expects a ./pants script in the Pants repo (any name - name is not important!) - and that script is what is custom and runs pants from sources.

@kaos I thought your whole point was you wanted to be able to not question your muscle memory and always run pants everywhere to run the appropriate version of Pants. And in the Pants repo that's from sources for all normal purposes.

Correct, I do.
At the same time, if there's desire to do what Benjy suggested I could get on board that (if the details play out) merely observed that in order for my mind to cope with that, the dev incantation would need to be further away from the regular pants than just tacking ./ in front of it.. i.e. I'm willing to re-learn my mental muscles for that case. (to be clear, I'd rather not though :) )

I don't know exactly what the details would be, there would need to be some finessing. Maybe we take the most recent release, or the most recent stable release, or maybe indeed running from sources is the norm and running from a release is the exception, so we require you to set an env var with the version in order to run a release.
But the ability to run a released version of Pants in the pants repo is substantial (e.g., if we had Rust support we could avoid a ton of engine rebuilding), whereas having pants really invoke ./pants in that repo seems like sugar. So I don't want to foreclose on the former to support the latter. If they can coexist, fine.

Ok, that all already works just like any other repo. Define pants_version in pants.toml or via PANTS_VERSION. Afaict, the only way in which pants works differently in the Pants repo, is by shortcutting the pants from sources mechanism with the new config pseudo option @kaos added. You can still run from sources via env var too.

that all already works just like any other repo.

Not entirely true, though.
If you attempt to run with a released Pants, boom:
PANTS_VERSION=2.16.0.dev5 pants -V
Bootstrapping Pants 2.16.0.dev5 using cpython 3.9.15
Installing pantsbuild.pants==2.16.0.dev5 into a virtual environment at /Users/andreas.stenius/Library/Caches/nce/777744d4d26ad153bf39bb2f68dbc8d1a4f1067a710fa4c9e92087b110389d72/bindings/venvs/2.16.0.dev5
New virtual environment successfully created at /Users/andreas.stenius/Library/Caches/nce/777744d4d26ad153bf39bb2f68dbc8d1a4f1067a710fa4c9e92087b110389d72/bindings/venvs/2.16.0.dev5.
09:38:59.30 [ERROR] 1 Exception encountered:

Engine traceback:
  in select
    ..
  in pants.core.util_rules.environments.determine_local_environment
    ..
  in pants.core.util_rules.environments.determine_all_environments
    ..
  in construct_scope_environments_preview
    ..

Traceback (most recent call last):
  File "/Users/andreas.stenius/src/github/kaos/pants/src/python/pants/engine/internals/selectors.py", line 623, in native_engine_generator_send
[...]
  File "/Users/andreas.stenius/src/github/kaos/pants/src/python/pants/engine/internals/selectors.py", line 118, in __await__
    result = yield self
pants.base.exceptions.BuildConfigurationError: Version mismatch: Requested version was 2.16.0.dev5, our version is 2.16.0.dev6.

Use -ldebug for more logs.
See https://www.pantsbuild.org/v2.16/docs/troubleshooting for common issues.
Consider reaching out for help: https://www.pantsbuild.org/v2.16/docs/getting-help

due to:
https://github.com/pantsbuild/pants/blob/f807172caadc2c610aa7f8d48b06f58b7ef9d453/src/python/pants/option/options_bootstrapper.py#L286-L294

Oh, or I misread the "that all already works".. from scie-pants point of view, it indeed works. It's just Pants that doesn't cope with it.

Yeah, perhaps we could fix Pants here.

The proliferation of jim-crackery is wide: https://github.com/pantsbuild/pants/blob/main/src/python/pants/version.py#L13-L14

The proliferation of jim-crackery is wide: https://github.com/pantsbuild/pants/blob/main/src/python/pants/version.py#L13-L14

Oh, wow! wasn't aware of that one, but that could work.. but feels.. icky. :D

Yeah, there is already another ick:
https://github.com/pantsbuild/scie-pants/blob/41900c4733e221d17f76707cf005ab463bacf938/src/main.rs#L171-L175
That env var was intended for tests only, it just doesn't have the leading underscore to look as obviously icky. So there are paths forward here and the ick could be solidified with some code comments in Pants at the very least about production use of these knobs by scie-pants.

Aha, so I get the feeling the correct thing to do would be to provide _PANTS_VERSION_OVERRIDE={pants_version} if we have delegate_bootstrap and then continue to run the normal pants flow, as that would "cancel" the delegation to ./pants and provide the "fix" to work with a released version of Pants in the pants repo.
I can put up a PR for this later tonight.

That sounds about right to me.


Reference output must be last output?

I tried to build Simple Send transaction without omni APIs. It seems that when i changed the position of Referece Output, Reference Address changed as well.
What i expected:
Reference address: mtmMxDLE2hqAqDgEorJebcHYNMGefVdCJT
(pub:<PHONE_NUMBER>43b24d134fab43a299cb34dfb88c12)
Fee address: mqdMjb7zy58zzx5vpiF7vcbQUXhnNfpSgn
(pub: 6ee7520fb5dccdfb009d45ab1e84b3e3e357bba8)
Unexpected Case  (Reference output was not the last output):
"out": [
    {
      "value": "0.00000546",
      "scriptPubKey": "OP_DUP OP_HASH160<PHONE_NUMBER>43b24d134fab43a299cb34dfb88c12 OP_EQUALVERIFY OP_CHECKSIG"
    },
    {
      "value": "0.00000000",
      "scriptPubKey": "OP_RETURN 6f6d6e6900000000800000030000000000000014"
    },
    {
      "value": "950.98930044",
      "scriptPubKey": "OP_DUP OP_HASH160 6ee7520fb5dccdfb009d45ab1e84b3e3e357bba8 OP_EQUALVERIFY OP_CHECKSIG"
    }
  ]

result:
{
  "txid": "6479f25549d9c78b773a2440f716fee299d9985e144cff80e6dbb4d4423bb047",
  "fee": "0.00044550",
  "sendingaddress": "miRgAsB9CXXAQa5yLaApNjzC86W3s4JNAR",
  "referenceaddress": "mqdMjb7zy58zzx5vpiF7vcbQUXhnNfpSgn",  // wrong
  ...
}

Expected  Case  (Reference output was the last output):
"out": [
    {
      "value": "1000.98884948",
      "scriptPubKey": "OP_DUP OP_HASH160 6ee7520fb5dccdfb009d45ab1e84b3e3e357bba8 OP_EQUALVERIFY OP_CHECKSIG"
    },
    {
      "value": "0.00000000",
      "scriptPubKey": "OP_RETURN 6f6d6e6900000000800000030000000000000014"
    },
    {
      "value": "0.00000546",
      "scriptPubKey": "OP_DUP OP_HASH160<PHONE_NUMBER>43b24d134fab43a299cb34dfb88c12 OP_EQUALVERIFY OP_CHECKSIG"
    }
  ]

result:
{
  "txid": "4efd8233f29ac7f9334de1a59b861105e6ace34e07fe1ce4b6baaa8e347915f7",
  "fee": "0.00044550",
  "sendingaddress": "miRgAsB9CXXAQa5yLaApNjzC86W3s4JNAR",
  "referenceaddress": "mtmMxDLE2hqAqDgEorJebcHYNMGefVdCJT",   // right
  ...
}

My question is: Why the POSITION of reference output make difference reference address? And i can't find any rules of organizing Inputs/Outputs to build a correct transaction in spec.
Any help would be appreciated.

Hi @kevindaizj :
I hope it helps #836

So in Simple Send (Class C):

the sender is always the first input

the reference output is the latest one, which isn't change

Thanks, @santos177 . I am curious that why didn't omni group put this conclusion in spec.
.

Hi @kevindaizj, we're working on updating the specification to reflect these details.

So in Simple Send (Class C):

the sender is always the first input

the reference output is the latest one, which isn't change

Thanks, @santos177 . I am curious that why didn't omni group put this conclusion in spec.
.

How do you determine what is the change address ? If it is used in inputs ? What if I wan't to send the change to another address ?


SDK Version 5.0.0 auth timeout in not wifi status

What did you do?

open SFSafariViewController in line (url: access.line.me) and timeout (wifi status is okay)

What did you expect?

in LTE or 3G status is also okay

What happened actually?

open SFSafariViewController in line (url: access.line.me) and timeout (wifi status is okay)

Your environment?

LINE SDK version 5.0.1, Xcode version 10.1, iOS version 12.1, iPhone X.

@kor45cw Thanks for it.
We can reproduce this issue. It seems that this problem is not related to a certain network connection condition since I can reproduce it in both WiFi and LTE.
I believe that there is an issue in the navigating page after you allow the authorization. We are now investigating it!

@onevcat thank you
i think this problem is related in naver or line vpn
naver wifi, vpn -> load directly
lte, other wifi -> unloaded
plz check and update

Thanks for the additional information. I will ping you if we have any progress.

@kor45cw This should be fixed now. Can you confirm it?

@onevcat Yes, it works well. Thank you.

@onevcat Thanks! 👍


Migrate create fuels template from NextJS to Vite

Our current template bootstrapped dApp is templated in NextJS, based on conversations with @FuelLabs/devrel we have determined that a basic React template using vite would be more useful for devs.

Closing in favor of:

https://github.com/FuelLabs/fuels-ts/issues/2837
https://github.com/FuelLabs/fuels-ts/issues/2838


② [Currency selection] Add table view

📲 What
Paired with @Scollaco to add the SelectCurrencyViewController which is a table view that we push on to our navigation stack in order to select a preferred currency.
🤔 Why
This is part of a larger body of work to replace the current picker behaviour with a table view for selection.
🛠 How

Added UITableView programmatically (no xib) and used the Currency enum as a very simple datasource.

This is not our convention but we felt that a separate datasource class for this view was overkill and thought we would try this approach. We're very much up for discussion on whether or not this is okay to do!

Added a selection indicator also using basic UITableViewCells as this sufficient for what we needed (the checkmark is just using the cell's accessoryType property).

♿ Accessibility

We will address this in a separate PR.

✅ Acceptance criteria

[ ] When tapping the currency cell on the account screen you should be taken to this table view and see your current preferred currency selected.
[ ] Can select different currencies and the selection indicator moves to those cells.

🤖Related PR's for this feature
#568

 Change Currency Picker to new view with TableViewCells

I've noticed that the screen doesn't have a title (in the navigation bar)...should we add it or has it been added in one of the follow up PRs?

I've noticed that the screen doesn't have a title (in the navigation bar)...should we add it or has it been added in one of the follow up PRs?

Ah good point, I'll find out what it should be and add it 👍


Support persisting portainer data into external database

In case we can recover from machine crash safely without data losing.

I believe that this is related to https://github.com/portainer/portainer/issues/523
Closing as might be a duplicate and also, you can already persist the data outside of the Docker host where Portainer is running, by using a network shared filesystem for example.


Placeholder option (Select an Option) messes up images

When you add empty option tags <option></option> at the beginning of your select to show a "Select" placeholder:

...the first image is blank and the other images are reordered. These are what the correct images should look like:

This is what they look like when your first option is a placeholder:

As you can see, "test" doesn't have an image and "test2" has the image "test" should have. The "test2" image isn't displayed at all.

Change to this
$this.on("chosen:showing_dropdown", function showing_dropdown(evt, _chosen){
                    // summery
                    //      This function is triggered when the chosen instance dropdown list becomes visible
                    //  For Chose custom events: http://forwebonly.com/jquery-chosen-custom-events-and-how-to-use-them/
                    //
                    // evt: Event
                    //      The event object
                    // _chosen: Object {chosen:Chosen}
                    //      Contains the current instance of Chosen class
                    var optionWithImgCount = $(chosen.form_field).find('optgroup[data-img-src], option[data-img-src]').length;
                    if(optionWithImgCount > 0){
                        var lis = $(chosen.container).find('.chosen-drop ul li:not(:has(img))')
                        var options = $(chosen.form_field).find('optgroup, option');
                        var lIndex=0;
                        var endFor=lis.length;
                        for(var i = 0; i < endFor; i++){
                            var li = lis[lIndex];
                            var option = options[i];
                            var img_src = $(option).attr('data-img-src');

                            if(img_src != undefined){
                                lIndex++;
                                var template = html_template.replace('{url}',img_src);
                                $(li).prepend(template.replace('{class_name}','chose-image-list'));
                            }else{
                                lIndex--;
                                if(lIndex<0)lIndex=0;
                                endFor++;
                            }
                        }
                    }
                });

it's no excellent code but it's works

I ended up going in a different direction so didn't check if @bookin's code fixed the initial problem.
However, his code did seem to correct another problem. It's unclear when this problem began (maybe moving to jquery 2.1.3; maybe moving to chosen 1.4.1; maybe something else), but chosen selects that did not have any images for the dropdowns were causing all broswers to hang/timeout when the dropdown was clicked. I traced the problem to the if(img_src != undefined) block and substituted your code. The problem went away. Thanks.

Hi @c-prompt , @bookin , thanks for your contributing to the plugin, ... I've tried the code suggested by bookin but it would hang the browser if the option does not have an image but does have text, ..

I noticed the browser hang just recently and tried tracking down what started it, but was unable. I upgraded to JQuery 2.1.3 from 2.1.1 and also upgraded Chosen to 1.4.1, but when I rolled them back to see if I could find the cause of the hang, I still saw it. Once I changed to @bookin's code, the problem went away.

Thanks for that @c-prompt,
Currently the plugin uses jquery-1.7.1.min.js, maybe if I upgrade I will get the results you mentioned, ..
For now with the current setup,  @bookin code breaks it .. I'll dedicate some time in the near future to get to the bottom of this, ..

There is a much simpler solution to this issue. The problem is that these two arrays aren't matching up:
var lis = $(chosen.container).find('.chosen-drop ul li:not(:has(img))')
var options = $(chosen.form_field).find('optgroup, option');

The first array is returning only the HTML options with values and the second one is returning all options regardless if it has a value or not.
Since chosen placeholders use the empty option we just need to remove that option from the options array. Simply add this code after:
var lis = $(chosen.container).find('.chosen-drop ul li:not(:has(img))')
var options = $(chosen.form_field).find('optgroup, option');

options.splice(0, 1);

That will fix the issue and not hang the browser.

I tried @rayman813's suggestion but, on a dropdown with one item (with an image), it leaves the image off the dropdown until you select it.
With @rayman813's code:

With @bookin's code:

Here's what the dropdown activated looks like:

Thanks @rayman813 that solution worked nicely for me.


runtime: sweep increased allocation count

We have reports inside Google of crashes like:
runtime: nelems=34 nalloc=2 previous allocCount=1 nfreed=65535
fatal error: sweep increased allocation count

I've reproduced the problem and I have some confidence that it's a runtime or compiler bug, so I wanted to make sure that we had an external issue to represent the problem and track it as a release blocker. I'll update this as soon as we have detail that can be shared publicly.

CC @aclements

Current analysis suggests a bug in https://golang.org/cl/38091.  That adds a fast path for map assignment, and uses it for pointers among other values.  When a pointer is stored in the map, no write barrier is used.

I have another fix which just uses typedmemmove to write the keys. It's just a  2-line change.

FWIW, I've encountered a similar crash with go version go1.8 darwin/amd64:
runtime: nelems=9 nfree=0 nalloc=9 previous allocCount=1 nfreed=65528
fatal error: sweep increased allocation count
runtime: nelems=256 nfree=12 nalloc=244 previous allocCount=223 nfreed=65515
fatal error: sweep increased allocation count

https://golang.org/cl/38091 seems to have been committed in March, so after go 1.8 was released.

@andreimatei If you are seeing a problem with Go 1.8, then it is a different problem.  Please open a new issue with reproduction instructions.  Thanks.


On Mac, if VSC is hidden, then opening it from Terminal opens new window in background

On a Mac, open VSC, then hide it. Open Terminal, run code . to open the current dir in VSC. Assuming you have the setting to open it in a new window in VSC, then the new window will open in the background in VSC.

If someone has energy + an idea to look into, feel free.

Yes possibly an Electron issue. I haven't been able to find the relevant issue yet though.

This issue seems to originate from an upstream component and is not something VSCode can fix by making a change to the code. As such, I will go ahead and close it. If you can identify the component that is causing the issue, please report it upstream:

for UI, OS integration: https://github.com/electron/electron
for Rendering: https://bugs.chromium.org/p/chromium/issues/list
for file IO: https://github.com/nodejs/node

Thanks for understanding.


Projects Page Authenticated

The pictures are not loading. Can you please get the pictures to load?

done

@heldyboy Apparently, this is fixed. It's not clear why or what fixed it, but it's working now. Can you take a look and make sure? https://asrg.io/projects

@peterbogdan The images have disappeared again. WTF?


Guarded injection/interpolation and misc improvements

The main feature is that now injection (indirect) increments and interpolation (indirect) reads are "guarded" with suitable if-then-else constructs. These are transparently generated by the compiler leveraging ConditionalDimension.
A large set of fixes and improvement are also shipped, which touch many bits of the compilation pipeline. Among these:

More powerful ConditionalDimension (it now supports arbitrary conditions through the condition argument.
Simpler and more powerful clusterization (/ir/clusters/algorithms.py)
More general Cluster grouping (/ir/clusters/algorithms.py)
IntervalGroup's Intervals are now partially, instead of totally, ordered. This makes IterationSpace.merge much more powerful (it can now merge iteration spaces that couldn't be merged previously)
...

All these changes were somehow needed to make it possible using ConditionalDimensions within non-fd loops, such as those generated by SparseFunctions (eg, injection/interpolation loops)

Codecov Report

Merging #645 into master will increase coverage by 0.04%.
The diff coverage is 97%.

@@            Coverage Diff             @@
##           master     #645      +/-   ##
==========================================
+ Coverage   88.31%   88.35%   +0.04%
==========================================
  Files          91       91
  Lines        8899     8957      +58
  Branches     1780     1794      +14
==========================================
+ Hits         7859     7914      +55
- Misses        820      822       +2
- Partials      220      221       +1

Impacted Files
Coverage Δ

devito/dse/manipulation.py
94.93% <ø> (ø)
:arrow_up:

devito/data.py
75.87% <100%> (ø)
:arrow_up:

devito/dse/backends/basic.py
87.75% <100%> (ø)
:arrow_up:

devito/equation.py
84.61% <100%> (-1.1%)
:arrow_down:

devito/symbolics/extended_sympy.py
77.98% <100%> (+0.42%)
:arrow_up:

devito/ir/clusters/cluster.py
95.23% <100%> (+0.19%)
:arrow_up:

devito/mpi/halo_scheme.py
96.36% <100%> (+0.06%)
:arrow_up:

devito/ir/clusters/algorithms.py
97.24% <100%> (-0.1%)
:arrow_down:

devito/ir/equations/equation.py
91.08% <100%> (-1.37%)
:arrow_down:

devito/ir/support/utils.py
98.29% <100%> (ø)
:arrow_up:

... and 22 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 643a914...65ae238. Read the comment docs.

all good after offline discussion (leftovers addressed in a new imminent PR), merging


Error goes to the result!

Test:
r.table('test')
  .insert({ id: 'test' })
  .run()
  .catch(function(err) {
     console.log('err', err);
   })
   .then(function(result) {
     console.log('result', result);
  });

First run gives us a normal insert result.
Second run gives us
result { deleted: 0,
  errors: 1,
  first_error: 'Duplicate primary key `id`:\n{\n\t"id":\t"test"\n}\n{\n\t"id":\t"test"\n}',
  inserted: 0,
  replaced: 0,
  skipped: 0,
  unchanged: 0 }

instead of an error!

This is expected. RethinkDB doesn't return an error in this case but a result with the error.
One of the reason is that you could have one write that fails while another one succeed.

I'm not sure I follow here....if you only call insert once and first_error is defined, does the driver re-try again? If not wouldn't it be best to throw and error and then let the user catch it if they want it to silently fail?
My use case is with GraphQL and i'm trying to figure out error flow here. If I don't throw it myself GraphQL thinks it's a success:

     resolve(root, args) {
        return r.table('posts').insert(args, {returnChanges: true})
        .then((info) => {
          if (info.first_error) throw new Error(info.first_error)
          return info.changes[0].new_val;
        })
      }

Unless i'm missing something it seems like a config to opt into this behavior  would be beneficial.

This is RetinkDB's behavior
http://rethinkdb.com/api/javascript/insert/
To answer your question, the driver doesn't retry again after it gets an error.
If you want an error to be thrown if a write fail, you could write
r.table('test').insert({...}).do(function(result) {
  r.branch(
    result('errors').gt(0),
    r.error(result('first_error')),
    result
  )
})

Ok thanks!


WebInterface should check for correct return type

lymph fails when setting trace-id header in case the return type from WebInterface is not correct type. lymph should probably check for this and raise before.
Traceback (most recent call last):
  File "/home/eren.gueven/.virtualenvs/ars/local/lib/python2.7/site-packages/gevent/pywsgi.py", line 508, in handle_one_response
    self.run_application()
  File "/home/eren.gueven/.virtualenvs/ars/local/lib/python2.7/site-packages/gevent/pywsgi.py", line 494, in run_application
    self.result = self.application(self.environ, self.start_response)
  File "/home/eren.gueven/.virtualenvs/ars/local/lib/python2.7/site-packages/werkzeug/wrappers.py", line 291, in application
    return f(*args[:-2] + (request,))(*args[-2:])
  File "/home/eren.gueven/.virtualenvs/ars/local/lib/python2.7/site-packages/lymph/web/interfaces.py", line 114, in dispatch_request
    response.headers['X-Trace-Id'] = trace.get_id()
AttributeError: 'NoneType' object has no attribute 'headers'

Fixed in #288


PrestaShop 9 Compability + Namespace fix

Questions
Answers

Description?
Fixes the module's Namespace + compability for PS9

Type?
bug fix

BC breaks?
yes

Deprecations?
no

Fixed ticket?
N/A

How to test?
Install the module and try to access the "configure" page

I tried locally and it seems ok for me.

Validated by me and @nicosomb


Upgrade package Apollo Server

Apollo Server 3 has significant changes in the implementation of graphql api structure.

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Infineon] Update CYW30739 CSP and ot-ifx submodules for Thread 1.3 certification.

Problem
Infineon CYW30739 platform needs updating its submodules for Thread 1.3 support.
Change overview

https://github.com/Infineon/OT-Matter-30739A0/pull/3
https://github.com/Infineon/ot-ifx-release/pull/123

Testing
chip-tool pairing

rebased


sys/linux/init_alg.go: add new algorithms

Add new crypto algorithms from linux-next (future v5.5):

BLAKE2b and BLAKE2s
"-arm" implementations of ChaCha and XChaCha
"-arm" and "-neon" implementations of Poly1305

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6bfd3dd). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1515   +/-   ##
=========================================
  Coverage          ?   56.27%
=========================================
  Files             ?      142
  Lines             ?    26417
  Branches          ?        0
=========================================
  Hits              ?    14865
  Misses            ?    10843
  Partials          ?      709

Impacted Files
Coverage Δ

sys/linux/init_alg.go
0% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6bfd3dd...ad50597. Read the comment docs.

Does this blake2b also needs some config enabled in dashboard/config/upstream-kasan.config?

Does this blake2b also needs some config enabled in dashboard/config/upstream-kasan.config?

Yes, CONFIG_CRYPTO_BLAKE2S, CONFIG_CRYPTO_BLAKE2B, and CONFIG_CRYPTO_BLAKE2S_X86 should be added.


Just couple of the new items

Hey! Figured out how to add items and added some from last couple of updates!

Thanks, nice work!

Thank you))
How do I do it right? I'm not a programmer. Install your version and then mark the files in the folder?
Can you send me his e-mail and I'll talk to him?
--
Отправлено из Mail.ru для Android четверг, 22 февраля 2024г., 02:16 +10:00 от Jesse Niininen  @.*** :

Thanks, nice work!
—
Reply to this email directly,  view it on GitHub , or  unsubscribe .
You are receiving this because you are subscribed to this thread. Message ID:  @ github . com>


Update manifest list in index.html

Added three manifests from University College Dublin: large-format architectural elevations, historical map + geo bounding box data; geocoded historical photo

Coverage remained the same at 44.187% when pulling 6de03dd55817103ddca6e288883f2bd100b4382d on jbhoward-dublin:patch-4 into bd50c3cef17d3a17681576800db3b6aede9f1413 on IIIF:release2.1.


Update webapi.rst

fix language

Hi @srobati, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

That breaks the build
156Warning, treated as error:
157/home/travis/build/aspnet/Docs/aspnet/migration/webapi.rst:72: WARNING: Could not lex literal_block as "c#". Highlighting skipped.


lib.rs no longer handled by parcel-plugin-wasm.rs

Parcel use this plugin when import package using Cargo.toml, but it seems that lib.rs is no longer handled by this plugin.

Do you need this lib.rs support? I've removed the description in README.md now.


Mitigate algebraic attacks in RLN

This PR proposes a circuit revision to mitigate possible algebraic attacks that recovers a0 from shares computed at different epochs.
The main idea is to change a1 = Poseidon([a0, external_nullifier]) (whose value only depends on a0) to
hash = Poseidon([a0, external_nullifier])
a1 =  (hash % p1)*(hash % p2) % p

Intuitively, this corresponds to introducing two new variables x1, x2 so that a1 = (hash - x1*p1)*(hash - x2*p2) and whose value can be expressed by a polynomial with at least 3 variables (i..e a0, x1, x2), thus preventing algebraic attacks over a single share.
Few other observations related to such design choice:

p1 and p2 are chosen so that p1*p2 = p-1. In this way the final bit-size of a1 does not look biased;
We chose to use two p1 ~ p2[^1] reductions instead of a single p0 ~ p[^1], because otherwise we increase the probability that hash < p0 (or hash differ just by few multiples of p0 from and hash % p0 ), in which case a1 = f(a0) or a1 = f(a0) + r*p0 with small and guessable r.
The actual values of x1, x2 used in the share computation will randomly change at each epoch.

The changes implemented in this PR increases the number of constraints by 4.6%, for a total of 5779 (originally 5524).
Any feedback is welcome!
DISCLAIMER: This proposal is currently under exploration and did not go through an extensive security analysis yet.
[^1]: a ~ b means a and b have similar bit-size.

@curryrasul want to take a look at this as well

Great work @s1fr0 . The only thing I'm thinking about if the a1 is evenly distributed. The numbers are not co-prime, I'm not sure how it can affect the result. Maybe it's better to find prime p1 and p2 such as p1 * p2 ~ p.
Even in that case I'm not sure about even distribution.

So, as we discussed, we can update RFC with this info and not change the circuits.
Thanks a lot @s1fr0 for your work.


table 5901 Service Item No. On Validate trigger

Section 2 checks "Service Item No. ".  Would it make more sense to have it happen before Section 1?

The error in line 198 should be thrown regardless of "Service Item No." value, it could be blank or not, as this value cannot be changed in a linked line. This check should go first. Then if the line is not linked, the value can be blanked and should blank other fields (lines 219-222).


Host NFTs on IPFS

[x] Integrate a service to upload and host NFTs metadata on IPFS (Nft.school ~or Pinata~)
[x] add UI to enter metadata and select image for NFT
[x] anyway to list uploaded NFTs?
[ ] separate business login from UI (so that business logic can be reusable)
[ ] write tests

[ ] Code Refactoring

[ ] handle following errors:

Multer
nft.storage client


Solving failure remote repository at https://private-gitlab.com/x/k.git does not exist

What version of dep are you using (dep version)?
dep:
 version     : v0.4.1
 build date  : 2018-01-27
 git hash    : 37d9ea0
 go version  : go1.9.3
 go compiler : gc
 platform    : darwin/amd64

What dep command did you run?
$ dep ensure
What did you expect to see?
It working properly.
What did you see instead?
Solving failure: remote repository at https://private-gitlab.com/x/k.git does not exist, or is inaccessible: fatal: could not read Username for 'https://private-gitlab.com': terminal prompts disabled : exit status 128
More context
Building inside Docker using golang:1.10

What's the solution to this? Even I am getting the same error.

me too, what's the solution  ?

No solution?

What's the solution to this? I am getting the same error.
Working solution in linux:
[url "git@private.gitlab.com:"]
        insteadOf = https://git.gitlab.com/

but in macos doesn't work.

@krypto-code
Try my solution from previous comment.
It works both on Linux and OS X
[[constraint]]
  name = "private.gitlab.com/my_project/my_dep"
  source =<EMAIL_ADDRESS>  version = "2.0.3"

unable to read metadata: go-import metadata not found

@krypto-code
Try my solution from previous comment.
It works both on Linux and OS X
[[constraint]]
  name = "private.gitlab.com/my_project/my_dep"
  source =<EMAIL_ADDRESS>  version = "2.0.3"

You need to modify source like that:

I'm still have a same error on CI like
dep ensure
Solving failure:
	(1) failed to list versions for https://gitlab.com/basking/graphql-api.git: fatal: could not read Username for 'https://gitlab.com': terminal prompts disabled
```

try @s-kozlov and @viciss fix
[[constraint]]
name = "gitlab.com/basking/graphql-api"
source = "git@private.gitlab.com:my_project/my_dep.git"
version = "2.0.3"


changed support IRC server from Freenode to Libera

very minor change to readme to list correct IRC server network

While the change is correct, I wonder if we should mention IRC here at all, vs just saying "go to foreman community".
@ehelms @ekohl thoughts?

Should we link to https://theforeman.org/support.html instead?

is that the consensus ? change the link to the support link rather than the correct IRC link ?

Yes, please

done


feat(env): allow update of existing env vars

This allows you to update existing environment, and service environemnt variables.
It also fixes the create function for device service environment variables, which didn't match the API upstream.
In addition to the unit tests, I have tested all methods manually in another repo.

Okay if I merge @alethenorio ?


add roofline estimation of float8 gemm + overhead

Summary:
This PR adds a script to help estimate when it is expected to be faster to convert a torch.nn.Linear to float8, versus leaving it in bfloat16, for compute bound training use cases.
How we do this:

for bf16 and fp8 gemm time, use either benchmarks or roofline based on a percentage of peak compute bandwidth
for float8 overhead, enumerate the worst case of reads and writes performed by torch.compile, and convert to time by assuming we can achieve a percentage of peak memory bandwidth
compare (a) bf16_gemm_time and (b) fp8_gemm_time + fp8_overhead_time, and calculate the expected speedup.

Note that currently the gemm benchmarks require running a separate script, as documented in the argument descriptions.  We can make this nicer at a future time.
Test Plan:
python benchmarks/float8/float8_roofline.py \
    --outfile ~/local/tmp/20240813_del_del_dyn_bench_roofline.csv \
    --gemm_benchmarks_file ~/local/tmp/20240813_gemm_gpu_time_sweep_9_16.csv \
    --gemm_time_strategy benchmarks --model_torch_compile_limitations True \
    --scaling_type_input delayed --scaling_type_weight delayed \
    --scaling_type_grad_output dynamic | with-proxy gh gist create
- Creating gist...
✓ Created secret gist
https://gist.github.com/vkuzo/e3c4b274493140a7423c85d27863663a

Meta-only spreadsheet with more analysis, we should eventually OSS a vesion of this: https://docs.google.com/spreadsheets/d/1BpgGQjJwSmGen2QHukMmoCl7Ra5bgxAEQLEI0fma-Fs/edit?gid=195198894#gid=195198894
My tl;dr; from the analysis above:

the largest predictor of speedups of float8 gemms is M, K, N (not surprising).
handwavy estimates of where we should focus torch.compile + float8 improvements for per-tensor scaling:
a. getting torch.compile to be optimal for dynamic scaling: ~1.05x per-linear speedup vs dynamic worst-case
b. getting torch.compile to be optimal for delayed scaling: ~1.13x per-linear speedup vs delayed worst-case
c. after (a) and (b) are done, delayed scaling is expected to be 1.06x faster, per-linear, for large shapes
with current torch.compile behavior and for equal M, K, N, the breakeven point of float8 vs bf16 is somewhere between 2048 and 4096.  If we get to best case behavior, the breakeven point would move to slightly below 2048.  Of course, this is shape dependent.
this script should give a tighter estimate of which production model layers could benefit from float8.
with the current behavior of torch.compile, we don't expect speedups from delayed scaling vs delayed scaling.  Fixes in compile are needed to see more of benefit here.

Reviewers:
Subscribers:
Tasks:
Tags:

Noob question does sympy really speed up this script?

Not sure about speedup.  The reason I used sympy is to easily see the contribution of arbitrary M, K, N to memory overhead.


Can't install wlroots-rs

So, I try to install it as every single normal Cargo package by adding it to dependencies and building it, but it seems to fail with this package.
cargo build output:
Updating crates.io index
   Compiling amecomp v0.1.0 (/home/wizard/Projects/amethyst/amecomp)
error[E0433]: failed to resolve: could not find `utils` in `wlroots`
 --> src/main.rs:4:14
  |
4 |     wlroots::utils::init_logging(wlroots::utils::WLR_DEBUG, None);
  |              ^^^^^ could not find `utils` in `wlroots`

error[E0433]: failed to resolve: could not find `utils` in `wlroots`
 --> src/main.rs:4:43
  |
4 |     wlroots::utils::init_logging(wlroots::utils::WLR_DEBUG, None);
  |                                           ^^^^^ could not find `utils` in `wlroots`

error[E0433]: failed to resolve: could not find `CompositorBuilder` in `wlroots`
 --> src/main.rs:5:14
  |
5 |     wlroots::CompositorBuilder::new().build_auto(()).run()
  |              ^^^^^^^^^^^^^^^^^ could not find `CompositorBuilder` in `wlroots`

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0433`.
error: Could not compile `amecomp`.

To learn more, run the command again with --verbose.

How did you add wlroots-rs as a dependency? It's not hosted on crates.io currently, so you'll need a git submodule or similar mechanism


Containers using images built on Apple Silicon FAIL to boot

Bug encountered by Peer while testing on an M3 Mac.
The image was built on a braidnode project in the usual way
    rebar3 docker build
    docker push local/my_app grisp/my_app

Strange crash on braidnet:
2024-02-20T19:47:42.124 app[e784e666f0d778] nrt [info] 2024-02-20T19:47:42.123996+00:00 [debug] Container <<"d707b03f-9727-4ca9-b4dd-5426da907312">>: WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested

2024-02-20T19:47:42.207 app[e784e666f0d778] nrt [info] 2024-02-20T19:47:42.206705+00:00 [debug] Container <<"d707b03f-9727-4ca9-b4dd-5426da907312">>: exec /opt/foo/bin/foo: exec format error

2024-02-20T19:47:42.242 app[e784e666f0d778] nrt [info] 2024-02-20T19:47:42.241390+00:00 [debug] Container <<"d707b03f-9727-4ca9-b4dd-5426da907312">>, terminated with code 1 for reason: unknown

2024-02-20T19:47:42.242 app[e784e666f0d778] nrt [info] 2024-02-20T19:47:42.241540+00:00 [error] Generic server <0.5359.0> terminating. Reason: unknown. Last message: {#Port<0.2302>,{exit_status,1}}. State: {state,<<"d707b03f-9727-4ca9-b4dd-5426da907312">>,#Port<0.2302>}.

This might be because the Braidnode image was built to be ran on the same platform that was performing the build (Arm-based Macbook), but we later try to run it on a different platform (Amd64 Firecracker VM).
Does the --platform flag for docker build help?


maven-publish publishes jars with wrong extension for known jar packagings like 'ejb' in 5.6

Original report: https://discuss.gradle.org/t/changed-behaviour-in-maven-publish-between-5-5-and-5-6
Reproducing Example
plugins {
    id "java"
    id "maven-publish"
}
group = "mygroup"
version = "1.0.0"

publishing {
  publications {
    mavenJava(MavenPublication) {
      from components.java
      pom.packaging = "ejb"
    }
  }
}

When building with 5.5.1 the resulting files are:

~/.m2/repository/mygroup/ejbtest/1.0.0/ejbtest-1.0.0.jar
~/.m2/repository/mygroup/ejbtest/1.0.0/ejbtest-1.0.0.pom

When building with 5.6.2, the resulting files are:

~/.m2/repository/mygroup/ejbtest/1.0.0/ejbtest-1.0.0.ejb
~/.m2/repository/mygroup/ejbtest/1.0.0/ejbtest-1.0.0.pom

This is caused by the reimplementation of part of the publishing in #9445 and the absence of test coverage for this special casing of handling the 'packaging' attribute.

In Gradle 6 we will no longer automatically change the file extension of an artifact based on the pom packaging - see #10607. That change also fixes this issue.
In case we consider another patch release for the 5.x release line, the following commit can be picked to restore the 5.5 behavior: https://github.com/gradle/gradle/pull/10607/commits/a426d6eccab790c7333b08228c90eba2f7f64172

@jjohannes To make sure I understand clearly...
older than 5.6, we publish a jar but the POM would say packaging is ejb.
with 5.6, we publish a ejb and the POM would say ejb.
with 6.0, we publish a jar and the POM would say ejb.
From the commit above, it seems like there will be more changes in 6.0 to address non-jar publications?
Ignoring what we used to do, which is more correct/intended by Maven?  Should the packaging from the POM always match the extension of the published artifact or does it not really matter?

Adding my two cents here:
I'm the maintainer of a gradle-plugin which allows building maven-plugins with gradle and I just ran into the same problem. A maven-plugin has to publish a .jar file while the pom <packaging> has to be maven-plugin.
I therefore use something like this:
publishing {
  publications {
    mavenJava(MavenPublication) {
      from components.java
      pom.packaging = "maven-plugin"
    }
  }
}

This worked fine up until Gradle 5.5.1, but is broken with 5.6, 5.6.1 and 5.6.2
Therefore I'd answer this:

Should the packaging from the POM always match the extension of the published artifact or does it not really matter?

No, a mismatch between the pom <packaging> and the actual file extension is common practice in maven and should be supported by Gradle.

@big-guy you understood correctly.
@larsgrefer thanks for clarifying. It's correct what you wrote. There is just one gotcha, which eventually let to this regression.
If you use a "non-known" extension as packaging, Maven (and Gradle) also look for an artifact where the packaging is the extension. I believe that is a mechanism to allow discovery of "non-jar" artifacts as there is no other way in the POM format to define those.
So if you use something like classifier=foo, Maven (and Gradle) would find the .foo artifact. What is known or not known is hard coded in Gradle (and Maven I believe) - "jar", "ejb", "bundle", "maven-plugin" (known to refer to a jar).
The regression in 5.6 is that this list is not honored in our reimplementation of publishing. So for any packaging, the extension is now changed.
The general problem is that changing the extension late in the publishing process breaks other things in Gradle. That's why for 6.0 we want to get rid of this "magic" completely in the publishing plugin.
So in 6.0, if you set packaing=foo (not in the known list), you will still publish a jar by default. But you can always change the artifact when it is produced to get the same result as before. I.e., configure the jar task like jar.archiveExtension.set('foo').

Closing as this was merged to 5.6.3


Installation problem

I have installed, from Unitiy mod manager, UB.
However the mod does not work, or it rather is "not activated"
I get the message, see picture.
Feels like it has to do with "Unity program" or is it so?

Your UMM version isn’t compatible. Follow install instructions by letter with link to proper UMM.


Allow for "has" field in generated structure to be true/false in #define

What should the feature do?
In addition to allowing the author of a nanopb to declare a default value, this feature would be able to specify whether the field should be included by default or not.
An example of this in action would be:
message DataMessage {
  optional  State state = 1 [(nanopb).default_has = true] ;
  /* potentially more fields here */
}

Where State may contain sub-fields within it.
This, in turn, could compile to the following structure
/* Struct definitions */
typedef struct _DataMessage {
    bool has_state;
    State state;
} DataMessage;

/* Initializer values for message structs */
#define DataMessage_init_default                 {true, State_init_default};

In what situation would the feature be useful?
I am currently working on a project where it's useful to initialize all of a message's has_ fields to true (in both the top-level message and all submessages), but then subsequently be able to set the has_ boolean to false to avoid serializing that part of the protocol buffer and sending it over a transmission protocol.

Sounds reasonable.


Allow the default commit to run against to be configured

Use Case
For repositories whose mainline branch is not master (new Github projects now default to main, and some projects require pull requests against development or similar), allow the default target branch for pronto to be configured. If not configured, it remains master.
Notes
Similar to other congiruations, it can be specified in .pronto.yml (using default_commit) or by environment variable (PRONTO_DEFAULT_COMMIT).
The -c flag is still supported to specify a target commit. Nevertheless, configuring a default makes sense when the existing default master does not even exist in a project as is the case for many new Github repos.
Issue: https://github.com/prontolabs/pronto/issues/412

@mknapik  you've looked at some other config-related PRs, any time to give this one a quick glance? 🙏

Thanks for the contribution, @ozydingo! Sorry for the delay in reviewing :see_no_evil:


rename sti binary to s2i

Need to

[ ] have build produce an s2i binary instead of sti binary
[ ] have build produce a symlink sti that points to s2i
[ ] add logic to the CLI processing so that if the binary is invoked with the "sti" name, print a deprecation warning
[ ] update remaining doc to say s2i.

@gabemontero @soltysh fyi.

You have my full support in doing this, I'll buy you kofola for that :wink:

Vinea?

Deal, it can be even both :smile:

btw. @bparees do you have somebody interested in doing this?

@soltysh i kinda thought i might get to it, but no, no one has explicitly raised their hand.

Then I am, I still want to keep my no. 1 s2i commiter :crown: Besides I initiated that change some time ago, and I want to finish that. That will make @thesteve0 especially happy :smile:

this also includes updating all our images tests :-)

This is GH magic, I can see @mfojtik comment in my inbox, but no sign of it
on gh issue, lol.
@bparees can you add updating image tests to the list of actions?
On Tue, Jul 21, 2015 at 3:41 PM, Michal Fojtik<EMAIL_ADDRESS>wrote:

this also includes updating all our images tests :-)
—
Reply to this email directly or view it on GitHub
https://github.com/openshift/source-to-image/issues/244#issuecomment-123308709
.

He must have deleted his comment.

I deleted it because I realized that it is already noted in @bparees checklist :-)

It wasn't explicitly.


Expand/Collapse child item when clicked on header

Is it possible to expand/collapse item when clicked on header

Hi, @PankajRaincan. I plan to add expanding/collapsing items in the next version.

Hi, @PankajRaincan. Please try out new 1.1.0 version of the library with the feature of expanding/collapsing sections.

Yes..I will try it..thnx
On Mon, Jul 24, 2017 at 1:15 PM, Vladislav Zhukov<EMAIL_ADDRESS>wrote:

Hi, @PankajRaincan https://github.com/pankajraincan. Please try out new
1.1.0 version of the library with the feature of expanding/collapsing
sections.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zhukic/Sectioned-RecyclerView/issues/7#issuecomment-317344510,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbPl8f14pnhcDsZOFDsM_2zparYeiOSsks5sREuTgaJpZM4NVWJu
.

--
[image: RainCan] https://htmlsig.com/t/000001CDEBRD
Pankaj Jadhav / Android Developer
+91-9604525567
RainCan
+91-9595-767-767
403,Prime Square
Pimple Saudagar, Pune - 411027
http://www.raincan.com
[image: Twitter]  https://htmlsig.com/t/000001CE0CDP [image: Facebook]
https://htmlsig.com/t/000001CES087 [image: LinkedIn]
https://htmlsig.com/t/000001CD4SQG [image: Skype]
https://htmlsig.com/t/000001CCM9CV


Double middle click to zoom to extent of canvas

From @theoryshaw Another user pattern you see quick a bit with various architect/eng tools, is double clicking with the middle mouse button(or wheel) and it zooms to the extents of the contents.
Will need to calculate coverage of canvas before can do this

@theoryshaw: Does it zoom to contain just the contents, or does it zoom to include 0,0 and the contents?

Hey Jack, usually it zooms out to the extents of the contents.
not 0,0

Ok. Thanks Ryan. Will make it work like that.

Completed in 86be08c. Will mark as completed once wrote tested a merged with develop.


feat: Allow renaming exported ABIs

This allows users to rename their exported ABIs without any additional task hooks or filesystem reads. They can specify a rename function that receives the fully qualified name and returns a new name.

Specific use case for this?  Would it be more useful to pass the entire sourceName + contractName to the rename function?

Never mind the second question, I misread the code.

Specific use case for this?

Alone, this doesn't do much. But I plan to submit a couple more PRs:

The ability to specify an array of configuration for separate export logic
The ability to filter an ABI while exporting. This is necessary to export ABIs that are compatible with The Graph (which fails  on non-view or multi-dimensional functions in the ABI - ref https://github.com/graphprotocol/graph-cli/issues/588)

I'm trying to replace a bunch of custom logic in Dark Forest with this plugin, as we migrate to the Diamond pattern: https://github.com/darkforest-eth/eth/blob/master/tasks/compile.ts#L14-L88

@ItsNickBarry what do you think of this new approach? I'm a fan! I've also marked this as breaking since the flat option was removed.

I still don't see much use for the rename option (except for the flat setting), so I'd like to better understand the next steps you have planned before merging.  My primary concern is that the configuration schema might get too complex.
I also think I might want to keep the flat option - I'm working towards a sort of unification of my plugins, and flat has a parallel here: https://github.com/ItsNickBarry/hardhat-contract-sizer/issues/12
So right now I'm thinking that rename might be better implemented as an override of a save-abi-to-file subtask (yet to be added, but could be).
As for the subgraph issue, it's very disappointing to see a multi-billion-dollar project leave something like that unaddressed for so long.  No excuse, really.  I am in favor of providing a workaround here, but it should be kept on the periphery and its implementation should not affect core functionality of the plugin.

Hm, so you want me to back out these changes? As for overriding tasks, I'm trending towards being very much against them. What happens with task overrides is a cascading effect where multiple other projects do it and then you have to import them in a very specific order. This is a design flaw in hardhat and stops them from every supporting ESM without a rework.
Ideally, the plugins will provide common functionality as configuration and then anything exceptionally specialized will use an override. I don't believe Dark Forest is doing anything too far out of the ordinary (I've seen other projects doing much the same things).

As for your contract-sizer plugin, I don't think the flat option does quite the same thing because you aren't writing files to the filesystem, so conflicts will just be confusing, not destructive.

How would you feel if I implement the rest of my changes on top of this PR so you can see my plans for this rename option?

Hm, so you want me to back out these changes? As for overriding tasks, I'm trending towards being very much against them. What happens with task overrides is a cascading effect where multiple other projects do it and then you have to import them in a very specific order. This is a design flaw in hardhat and stops them from every supporting ESM without a rework.

Not saying that these changes are not acceptable, just that I need more time and information to make an informed decision.  Don't want to rush it, particularly with respect to breaking changes (also, it's been a long couple of weeks, so I'm not necessarily thinking as clearly as I would like).
I do see your point about subtasks, and have encountered issues with import ordering in the past.  However, I think that in 95% of cases, that only applies to built-in Hardhat subtasks.  If hardhat-abi-exporter exposes a subtask, only end-user Hardhat projects are expected to ever override it, so the task "inheritance" tree remains flat.  Still seems like a valid concern, because we cannot predict user behavior, so I will weigh it against the complexity of your proposed extension to the configuration.

How would you feel if I implement the rest of my changes on top of this PR so you can see my plans for this rename option?

Yes, I'd like to see either an explanation or an implementation, whichever you feel is easier.

As for your contract-sizer plugin, I don't think the flat option does quite the same thing because you aren't writing files to the filesystem, so conflicts will just be confusing, not destructive.

Both plugins should probably throw an error if the final output includes name conflicts (I'll look into it).  Ultimately, confusion is in itself destructive.  So if flat means "flatten file path before output" then I still think there's a strong parallel.  But don't worry about this either way, it's not a primary concern here.

I can try to describe it!
I'm in the process of migrating the Dark Forest contracts to the Diamond pattern, and in that process we combine all our Facet ABIs into a single ABI named DarkForest.json. We use a plugin I wrote for this: https://github.com/projectsophon/hardhat-diamond-abi
This is simple enough, with both plugins, we can write a hardhat.config.ts like this:
const config = {
  solidity: '0.8.10',
  diamondAbi: {
    // This plugin will combine all ABIs from any Smart Contract with `Facet` in the name or path and output it as `DarkForest.json`
    name: 'DarkForest',
    include: ['Facet'],
  },
  abiExporter: {
    // This plugin will copy the ABI from the DarkForest artifact into our `@darkforest_eth/contracts` package as `abis/DarkForest.json`
    path: path.join(packageDirs['@darkforest_eth/contracts'], 'abis'),
    runOnCompile: true,
    // We don't want additional directories created, so we explicitly set the `flat` option to `true`
    flat: true,
    // We **only** want to copy the DarkForest ABI (which is the Diamond ABI we generate) to this folder, so we limit the matched files with the `only` option
    only: [':DarkForest$'],
  },
};

export default config;

We want this entire ABI available for the game's dApp, but we also need to generate and export a version of that same ABI that is valid for the Dark Forest Subgraph (which is heavily used by the playerbase). So my goal is to allow separate "abi exporters", like such:
const config = {
  solidity: '0.8.10',
  diamondAbi: {
    // This plugin will combine all ABIs from any Smart Contract with `Facet` in the name or path and output it as `DarkForest.json`
    name: 'DarkForest',
    include: ['Facet'],
  },
  // This plugin config will copy the ABI from the DarkForest artifact into our `@darkforest_eth/contracts` package
  abiExporter: [
    // Generates the `abis/DarkForest.json` file for use in the game client
    {
      path: path.join(packageDirs['@darkforest_eth/contracts'], 'abis'),
      runOnCompile: true,
      // We are only generating one file so set the name to "DarkForest" explicitly
      rename: () => 'DarkForest",
      // We **only** want to copy the DarkForest ABI (which is the Diamond ABI we generate) to this folder, so we limit the matched files with the `only` option
      only: [':DarkForest$'],
    },
    // Generates the `abis/DarkForest_stripped.json` file
    {
      path: path.join(packageDirs['@darkforest_eth/contracts'], 'abis'),
      runOnCompile: true,
      // We are only generating one file so set the name to "DarkForest_stripped" explicitly
      rename: () => "DarkForest_stripped"
      only: [':DarkForest$'],
      filter: (abi) => subgraphAbiFilter(abi),
    },
  ]
};

export default config;

This will allow us to turn the same ABI into multiple exported ABIs and support both the game client and the subgraph.
So far we've just been doing this sort of logic by hooking the compile and generating the artifacts ourselves; however, integrating the Diamond ABI with TypeChain has run into the task hook ordering problem we were discussing. While trying to solve those issues, I thought it'd be helpful to combine efforts with already-released community plugins (Dark Forest has waaaaaay too much bespoke code).
Does this make sense? What do you think?

So my goal is to allow separate "abi exporters"

This part is really interesting.  As long as the abiExporter config key can accept either an object or an array of objects, I think it's good to add.  Started an implementation in PR #27.  Granted you access the the repository so that you can push to the development branch
I'm still not completely sure about this implementation of rename, but I think we can merge soon if I don't think of anything better.

It seems like rename is kind of redundant if each config object can specify a path.  Is it terribly inconvenient to just nest the exports in different directories?

The filter function is similar to something brought up in #20.  I was against it at the time, but if we can support multiple use cases with a single generic callback function, I think it's okay.

It seems like rename is kind of redundant if each config object can specify a path. Is it terribly inconvenient to just nest the exports in different directories?

I think that's fair. Putting things in different directories makes things a little weird for our published packages. I wonder if path could be changed to support what I was trying to do with rename? Maybe it could take a function, but if it is a string, it uses the current logic.

Let's keep both rename and flat, and throw an error if both are set.  I will make a final decision about flat before 3.0.0 release when I republish as @solidstate/hardhat-abi-exporter.

@ItsNickBarry I finally had a chance to update this as we discussed. Can you take a look?
I'd like to get this feature released so I can update the Dark Forest codebase.

Will review as soon as possible.

@phated Fixed the case where neither flat nor rename is specified, and in the process allowed both values to be set as long as flat is false.  If everything looks good, will merge and publish.

Released as 2.9.0.


Snackbars should go above the bottom bar.

I don't know if it was already reported, but when I implement this library and try to attach a snack bar like so:
Snackbar.make(bottomBar, "Some text", Snackbar.LENGTH_LONG).show();
I get this result (The snackbar overlays the bottom bar).
According  to the guidelines it should look like this.
And once again, thank you for this great and quick implementation.

For this, the bottom bar needs to be inside a coordinator layout. I think that the library doesn't have to care about that because is coordinator layout work . Hope that this doesn't break some flexibility

You can try attaching the BottomBar inside CoordinatorLayout by attaching it to a view that's directly inside it.
For example:
activity_main.xml
<CoordinatorLayout
    ...>
    <FrameLayout android:id="@+id/myContent" />
    <FloatingActionButton
    ...  />
    ...
</CoordinatorLayout>

MainActivity.java
bottomBar.attach(findViewById(R.id.myContent), savedInstanceState);

If you're using bottomBar.attach(this, savedInstanceState), give the Snackbar the CoordinatorLayout as the first parameter.
activity_main.xml
<?xml version="1.0" encoding="utf-8"?>
<android.support.design.widget.CoordinatorLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    android:id="@+id/myCoordinator"
    android:layout_width="match_parent"
    android:layout_height="match_parent">
    ...

</android.support.design.widget.CoordinatorLayout>

MainActivity.java
Snackbar.make(findViewById(R.id.myCoordinator), "Can you smell what The Rock is cooking?", Snackbar.LENGTH_LONG).show();

Works!

Awesome!

I used the co-ordinator layout as you said, but the snackbar never appeared
this.myCoordinator = (CoordinatorLayout) findViewById(R.id.myCoordinator);
this.bottomBar = (BottomBar) findViewById(R.id.bottomBar);
snackbar = Snackbar.make(myCoordinator, "This is a snackbar", Snackbar.LENGTH_INDEFINITE);
snackbar.show();
Am i doing something wrong here?

Hi @roughike, @rosenpin
I am using 2.1.1 version. Snackbar is not visible in anyway. How did you achieve this? Could you provide more detailed code, please? I could not find any method like BottomBar#attach()
That's my code:
Snackbar.make(coordinatorLayout, "message", Snackbar.LENGTH_LONG).show();

<android.support.design.widget.CoordinatorLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/activityHomeRoot"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:fitsSystemWindows="true">

    <include layout="@layout/layout_cci_toolbar"/>

    <FrameLayout
        android:id="@+id/activityHomeFrameLayoutContainer"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        app:layout_behavior="@string/appbar_scrolling_view_behavior"
        android:layout_marginBottom="@dimen/home_bottom_bar_height_without_shadow"/>

    <com.roughike.bottombar.BottomBar
        android:id="@+id/activityHomeBottomBar"
        android:layout_width="match_parent"
        android:layout_height="@dimen/home_bottom_bar_height"
        android:layout_gravity="bottom"
        style="@style/CCIBottomBar"/>

</android.support.design.widget.CoordinatorLayout>

<resources>

    <style name="CCIBottomBar">
        <item name="bb_tabXmlResource">@xml/home_bottom_bar_tabs</item>
        <item name="bb_activeTabColor">@color/colorPrimary</item>
        <item name="bb_inActiveTabColor">@color/gunmetal</item>
    </style>

</resources>

@rosenpin Could you provide your working layout xml?

@jkwiecien how are you displaying the SnackBar?

When I use android support library com.android.support:design:25.2.0,the snackbar won't work.is there any solution?


cannot load such file -- autotest upon require

My name is Maciej Mensfeld and I run a research security project called https://diffend.io.
While that's not a security issue, wanted to bring to your attention, that upon requiring of this gem (diffend does that to run a sandbox for security assessment of gems based on their behaviors), it fails with:

Traceback (most recent call last):
	2: from -e:1:in `'
	1: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- autotest-fsevent (LoadError)
	9: from -e:1:in `'
	8: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:156:in `require'
	7: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `rescue in require'
	6: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:168:in `require'
	5: from /home/app/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/autotest-fsevent-0.2.18/lib/autotest-fsevent.rb:4:in `'
	4: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
	3: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
	2: from /home/app/.rbenv/versions/2.7.2/lib/ruby/gems/2.7.0/gems/autotest-fsevent-0.2.18/lib/autotest/fsevent.rb:2:in `'
	1: from /home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
/home/app/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': cannot load such file -- autotest (LoadError)

which (probably) indicates, that XYZ is not present upon loading.
repro:
Gemfile

source 'https://rubygems.org'

gem 'autotest-fsevent'

steps:

bundle install
bundle exec ruby -e 'require "autotest-fsevent"'

You can't require autotest-fsevent, it's require autotest/fsevent as mentioned in the README.
Furthermore, this is a plugin for autotest, so it cannot be required standalone. You have to load a test suite runner and require this plugin in your ~/.autotest. There's no hard dependency in the gemspec since there are different test suite runners to chose from.

Thank you for the clarification.


Hello, in the training of the following mistakes, how to solve it

einops.EinopsError:  Error while processing rearrange-reduction pattern "b h (x y) d -> b h x y d".
Input tensor shape: torch.Size([2, 4, 900, 128]). Additional info: {'x': 26, 'y': 26}.
Shape mismatch, 900 != 676

x, y are determined by the fmap_size. You should set the fmap_size according to your dataset.


Add embedded document name support. ("name.first", "name.last")

Your module works great as long as you define your names in the base of the schema like this:
{first_name: String, last_name:String}
The second you want your schema to be like this:
{name : {first : String, last:String}}
You run into problems.
I wrote a function that fixes this. Either include it or add me to the repo and I'll make the changes.
var getProperty = function(key, doc) {                 var item = doc;                 var keys = key.split('.');                 var iterations = keys.length - 1;                 for (var i = 0; i < iterations; i++) {                     item = item[keys.shift()];                 };                 return item[keys[0]];// Returns a 'pointer' to the correct property.             }

@NomadGraphix the plugin has been updated to support what you were requesting.
Also, in the future, feel free to fork the repo and submit a pull request, contributions are welcome :)


[Feature]: to create and query sql queries based on questions asked by the user

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
The ability to create and sql queries and query the data based on questions asked by the user in English (natural/spoken language)
Why should this be worked on?
currently, AI/ML being a booming field this particular usecase has also seen a nice chunk of demand and for the product you offer this could be a nice add-on

@gkKshitij This is already available :) You can type /ai on the SQL query editor to summon Appsmith AI. You can read more about it here.

okay I tried querying this to chatbot and some customer service personnel as well but will test myself as well and respond here

It's not publicly available yet, but I would surely like to give it a try whenever it is available though


Implement printSchemaAndCapabilities, fix scalar type dependencies in schema response

This PR implements the printSchemaAndCapabilities cli command.
For this, we move the schema_response code into the common crate. We also move the configuration reading code into common
This PR also includes a bugfix for schema response generation:
We try to only return scalar types actually used by the tables in the configuration.
Scalar types may have aggregate functions returning other scalar types, for example sum(Int32) returns Int64, creating scalar dependencies.
These dependencies are now recursively accounted for.

One thing I just noticed is that your changelog doesn't have dates on the versions, which means it technically isn't following "keep a changelog". Versions should look like this:
## [1.1.1] - 2023-03-05

Also useful given your changelog update says the "Note the DDN CLI does not yet implement this"... knowing when this was written would be useful to readers.


Improve docs for logLevel and customLogger in ConfigParams

I was trying to filter out messages of a certain log level while using a custom logger. Unexpectedly, no filtering occurred at all.
After asking around on Slack about this, @Luis-omega identified the culprit:
config # _.customLogger >>> fromMaybe (logWithLevel config.logLevel)
https://github.com/Plutonomicon/cardano-transaction-lib/blob/develop/src/Internal/QueryM.purs#L325
When a customLogger is set, the logLevel is not used for filtering. I think this behaviour is a bit unintuitive and we should document it, at least.

I think we should also document if suppressLog works even with a customLogger or not.

@klntsky I'm not sure if I got this idea correctly. Do you mean to move the LogLevel out of the Message type used for the customLogger into the ConfigParams type? Because if I just add another LogLevel for the customLogger they would conflict each other, no?


return mime type to text

With Text Mime Type.
First Request: 509ms
Second+ Request: 30ms.
Without Text MimeType.
First: 649.
Second: 584
This is local only, and there is a small chance it breaks the backend, if so the backend will need to use a JSON.parse on the front end to get it from text format back to JS object styles. Its very difficult to test as its proxied via the frontend_server, and wiring them up locally is kind of a pain.

What is the impact of this change? Could you provide some latency before/after numbers, if that's what this is intended to speed up?

Hey, thanks, yeah honestly testing this will be a pretty big pain, I was never able to successfully wire everything up. I think its possible and I know how to do it but it would take kind of a long time, I think we should merge and test it on the dev server.

I'm not convinced we should do this, it is a json. https://stackoverflow.com/questions/4350753/advantages-of-using-application-json-over-text-plain

Closing this for now


sliderMove on horizontal swiper with mousewheelControl and freeMode doesn't fire

The sliderMove and slideChangeStart events do not fire when using a horizontal swiper with mousewheelControl : true and freeMode: true
I understand why slideChangeStart wouldn't fire since the slide technically isn't changing, but I would expect the sliderMove event to fire. Is this the expected behaviour?

Issue is closed because of outdated/irrelevant/not actual/needed more information/inactivity.
If this issue is still actual and reproducible for latest version of Swiper, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Support does not need to be contacted anymore, 10 sec is the new limit for payment extensions

See https://docs.commercetools.com/api/releases/2021-12-09-increased-maximum-timeout-for-payment-related-api-extensions

Thank you for contribution!


CPU is not supported

started the application writes:" Your CPU in not currently supported... Send this: AMD Ryzen 9 7900X3D 12-Core Processor".
Pity would be a good utility

Try handheld control panel
Best Regards,
Chris
WeChat: ProjectSBC
QQ:<PHONE_NUMBER>

From: Zakkitoway @.>
Sent: Tuesday, June 20, 2023 7:22:13 AM
To: project-sbc/Power-Control-Panel @.>
Cc: Subscribed @.***>
Subject: [project-sbc/Power-Control-Panel] CPU is not supported (Issue #39)
started the application writes:" Your CPU in not currently supported... Send this: AMD Ryzen 9 7900X3D 12-Core Processor".
Pity would be a good utility
—
Reply to this email directly, view it on GitHubhttps://github.com/project-sbc/Power-Control-Panel/issues/39, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASZ4DJK3J6OJL4NQIDN4IMLXMGBWLANCNFSM6AAAAAAZNEFG3Y.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Auto-upgrade to <IP_ADDRESS>

Base PullRequest
default branch (https://github.com/http4k/http4k-connect-examples/tree/master)
Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k_connect.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k_connect.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k_connect.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/build/src/bin

./upgrade_http4k_connect.sh <IP_ADDRESS>

Changed files

Changed 5 files:

connect-pattern/gradle.properties
custom-adapter-and-fake/gradle.properties
developing-openai-plugins/gradle.properties
extending-connect-adapters/gradle.properties
using-connect-adapters/gradle.properties

:octocat: Repo | :memo: Issues | :department_store: Marketplace


feat: make statless CNI to return an empty state when CNI GET API is …

…invoked

Reason for Change:
This change is needed for a scenario that StateMigration is enabled and dropGZ is using StatelessCNI.
In this scenario Stateles CNI should return an empty satate.

[X] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[X] relevant PR labels added

Notes:

/azp run Azure Container Networking PR

/azp run Azure Container Networking PR

this PR succeeded required runs. so merging this to unblock release


Changed index.html

Rectified 2 typos.

@ahsanbagwan, thanks for doing this. please squash your commits and we can merge this.


Server Side Rendering

@coreui\react\lib\Shared\layout\layout.js
document is not defined.how to solve it?

@coreui\react\lib\Shared\layout\layout.js
document is not defined

I am seeing same problem. Seeking workarounds/fixes! Thanks...

Hello everyone. Has anyone been able to fix this?

@kevinashworth Hello! Has anyone been able to fix this?

I am not aware of a fix. I'm still awaiting v3.
In November 2019, they messaged me about layout.js:

This is the follow-up.
Please disregard the previous message.
We can confirm the issue:

(node:12708) UnhandledPromiseRejectionWarning: ReferenceError: document is not defined
at Object. (node_modules/@coreui/react/lib/Shared/layout/layout.js:62:27)

We'll try to fix this in the next version of CoreUI 3 for React and port it back to v2 if possible.
Thanks for the heads-up.
CoreUI Team.

@kevinashworth Thank you!

Version 3 is now released, please let us know if you still have issues regarding SSR.


Remote Rendering Test Fix

Error message was changed to a more user friendly one in the service. This requires regeneration of recorded tests.

/azp run java - remoterendering - tests

API change check
API changes are not detected in this pull request.

/azp run java - remoterendering - tests

/azp run java - remoterendering - tests

Superseded by https://github.com/Azure/azure-sdk-for-java/pull/39403