Moving features into experimental

All experimental and non-experimental features are listed in the help section:
% ./qir/qat/Apps/qat
Usage: /Users/tfr/Documents/Projects/qat/Debug/qir/qat/Apps/qat [options] filename

Component configuration - Used to disable or enable components

--disable-validation-configuration                Disables Validation configuration. Default: false
--disable-llvm-optimisation                       Disables LLVM optimisations. Default: false
--disable-transformation-rules                    Disables Pass configuration. Default: false
--disable-grouping                                Disables Grouping quantum instructions. Default: false

Base configuration - Configuration of the quantum adoption tool to execute a specific behaviour.

--load                                            EXPERIMENTAL. Load component. Default:
--apply                                           Applies a profile to transform the IR in correspondence with the profile. Default: false
--validate                                        Executes the validation procedure. Default: false
--profile                                         Sets the profile. Default: generic
--S                                               Emits LLVM IR to the standard output. Default: false
--O0                                              Optimisation level 0. Default: false
--O1                                              Optimisation level 1. Default: false
--O2                                              Optimisation level 2. Default: false
--O3                                              Optimisation level 3. Default: false
--verify-module                                   Verifies the module after transformation. Default: false
--experimental                                    Enables experimental features. Default: false
--dump-config                                     Prints the configuration to the standard output. Default: false

Transformation rules - Rules used to transform instruction sequences in the QIR.

--[no-]optimise-result-one                        EXPERIMENTAL. Maps branching based on quantum measurements compared to one to base profile type measurement. Default: true
--[no-]optimise-result-zero                       EXPERIMENTAL. Maps branching based on quantum measurements compared to zero to base profile type measurement. Default: true
--[no-]use-static-qubit-array-allocation          Maps allocation of qubit arrays to static array allocation. Default: true
--[no-]use-static-qubit-allocation                Maps qubit allocation to static allocation. Default: true
--[no-]use-static-result-allocation               Maps result allocation to static allocation. Default: true
--[no-]disable-reference-counting                 Disables reference counting by instruction removal. Default: true
--[no-]disable-alias-counting                     Disables alias counting by instruction removal. Default: true
--[no-]disable-string-support                     Disables string support by instruction removal. Default: true

Validation configuration -

--[no-]allow-internal-calls                       Whether or not internal calls are allowed. Default: true
--save-validation-report                          Saves the validation report to specified filename. Default:

LLVM optimisations - Enables specific LLVM optimisations before and after transformation.

--unroll-loops                                    Aggressively unroll loops. Default: false
--[no-]allow-partial                              Enables or disables partial unrolling. When disabled only full unrolling is allowed. Default: true
--[no-]allow-peeling                              Enables or disables loop peeling. Default: true
--[no-]allow-runtime                              Enables or disables unrolling of loops with runtime trip count. Default: true
--[no-]allow-upper-bound                          Enables or disables the use of trip count upper bound in loop unrolling. Default: true
--[no-]allow-profile-based-peeling                Enables or disables loop peeling basing on profile. Default: true
--full-unroll-count                               Sets the max full unroll count. Default: 1024
--unroll-opt-level                                Sets the optimisation level for loop unrolling. Default: 3
--only-when-forced                                If true, only loops that explicitly request unrolling via metadata are considered. Default: false
--forget-scev                                     If true, forget all loops when unrolling. If false, forget top-most loop of the currently processed loops. Default: false
--always-inline                                   Aggressively inline function calls. Default: false
--inlining-parameter                              Number of code lines acceptable when inlining. Default:<PHONE_NUMBER>
--[no-]eliminate-constants                        Uses LLVM pass to eliminate constants. Default: true
--[no-]eliminate-dead-code                        Uses LLVMs aggressive dead code elimination. Default: true
--[no-]eliminate-memory                           Maps memory into registers where feasible. Default: true
--use-llvm-opt-pipeline                           EXPERIMENTAL. Disables the the default pipeline. Default: false
--opt-pipeline-config                             EXPERIMENTAL. LLVM passes pipeline to use upon applying this component. Default:

Pass configuration - Configuration of the pass and its corresponding optimisations.

--[no-]delete-dead-code                           EXPERIMENTAL. Deleted dead code. Default: true
--[no-]clone-functions                            EXPERIMENTAL. Clone functions to ensure correct qubit allocation. Default: true
--[no-]transform-execution-path-only              EXPERIMENTAL. Transform execution paths only. Default: true
--max-recursion                                   EXPERIMENTAL. Defines the maximum recursion when unrolling the execution path Default: 512
--assume-no-except                                EXPERIMENTAL. Assumes that no exception will occur during runtime. Default: false
--reuse-qubits                                    EXPERIMENTAL. Use to define whether or not to reuse qubits. Default: false
--reuse-results                                   EXPERIMENTAL. Use to define whether or not to reuse results. Default: false
--entry-point-attr                                Specifies the attribute indicating the entry point. Default: InteropFriendly
--[no-]annotate-qubit-use                         Annotate the number of qubits used Default: true
--[no-]annotate-result-use                        Annotate the number of results used Default: true

Grouping quantum instructions -

--[no-]separate-circuits                          EXPERIMENTAL. Whether or not to separate quantum and classical circuits Default: true

@troelsfr Could you please ensure that all APIs (and also doc comments, but I don't mind if these get gradually updated) follow American standard spelling? While that is not a reflection of who the tool is for, overall it is nicer and less surprising for users to have some consistency across all out tools.

Sure. I will pick this up on Monday.
On Sat, 26 Feb 2022, 04:11 Bettina Heim, @.***> wrote:

@troelsfr https://github.com/troelsfr Could you please ensure that all
APIs (and also doc comments, but I don't mind if these get gradually
updated) follow American standard spelling? While that is not a reflection
of who the tool is for, overall it is nicer and less surprising for users
to have some consistency across all out tools.
—
Reply to this email directly, view it on GitHub
https://github.com/qir-alliance/qat/pull/58#issuecomment-1051527011, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMHDXQGH3D6WUWXIBZZBDU5BAGPANCNFSM5PD27RJQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Code changes look good, but one thing that took me a while to piece together is that experimental features effectively have two default settings: one default when experimental is not provided and one when it is. The help description of these parameters is a little confusing in that regard, because it describes some parameters as default true and it makes it seem as if some experimental features are enabled by default for normal operation. Perhaps some additional text on the --experimental parameter itself to clarify that any features that are marked EXPERIMENTAL are disabled if the top level --experimental param is not provided?

Yes, this is a good suggestion. I will make this change today.


ensure job requeues have the correct paramters

The ReindexModelJob re-queues itself but was not doing so with the right parameters.  This adds a test to catch such issues next time.

Thank you @thenapking


Boss idea: Tiny/SpiritBreaker/Ursa/EarthSpirit mix Needs Lore

Boss idea: The Boss is like tiny, someone that hits hard but slow, and has a passive like Spirit Breaker. Phase 1: The boss fights champions like bosses do in Reborn, but gains a stack of impatience per second, all stacks of impatience are removed when the boss autoattacks someone. When the stacks of impatience hits 5, the boss charges the lowest hp champion (point charge) and bashes. The boss also has a sweeping attack that knockbacks a significant amount. For each 5% of hp lost, the boss slams down, dealing aoe damage, and stalagmites drop from the sky. When they drop, they deal no damage but stun heroes, and can be destroyed after they fell. When the hero is knocked backed into a stalagmite, it takes extra damage.  If the boss charges and hits a stalagmite, the stalagmite is destroyed. The charge deals bonus damage, increased range and increased speed per stalagmite destroyed.
Phase 2: At about 50% hp, the boss starts tossing stalagmites for damage, and each toss brings down 3 stalagmites too. Auto attacks and aoe swipes start adding stacks of concussion, which each stack increasing the duration of stuns dealt to the hero.
Phase 3: at about 10% hp, all stalagmites require additional hits to be destroyed, the boss gains an ability to consume stalagmites for damage reduction (physical and magical), which stacks (10% per stalagmite).

First off, let me start by saying I like his idea a lot. I do have a few questions and concerns which I will now list:

What else, if anything, does Impatience do besides triggering the charge?
Is Sweeping Attack the only knockback he has? Shouldn't there be more?
You didn't mention if his Charge causes a small knockback like Spirit Breaker. If so, you should indicate this in the description. What if it actually Skewered them through the rocks as well?
Slam causing falling rocks is a very interesting mechanic. I like it. It creates a mood.
Am I correct in assuming that the Charging through rocks mechanic behaves very similarly to Earth Spirit's Rolling Boulder?
Rock Toss is very interesting. Does he pick up rocks from the map or are they created by the toss? Also can he toss players?
I don't think Concussion is interesting at all. There are better ways to increase the difficulty at phase 2. One of many option would be to introduce a slow effect on his Slam.
Consuming rocks for damage reduction isn't very interesting either. The "Quick, kill all the rocks!" minigame is a time-consuming chore which might be a complete waste of time if he ends up eating rocks faster than you can kill them. It's a very convoluted way of giving him a very simple benefit: increased sustain. Don't get me wrong.  But I don't like the mechanic it introduces or the way it changes what was a very fun encounter into a boring minigame.

I think your idea is incredibly cool. Possibly just make the description a bit more clear and concise. I like phase 2's Toss mechanic but phase 3 could be entirely redone imho.
Then again, these are all just my opinions. i could be wrong.

Marblehardt

Lore
Forged in tectonic collisions billions of years ago, our lineage descended from the mighty Titans themselves. Peering high above the highest clouds or tumbling down waterfalls deep into the river's abyss, we are the pillars of the Earth. The mighty kings carve at our bones erecting altars in honour of their foolish conquests - and fall to dust. We gaze nobly onward as entire scores of civilizations perish before the mighty green hills, scarcely noticed.
The astral plain trembles with the unfathomable force of a world's impending destruction. The haze of uncertainty is lifting and a terrifying reality renders itself clear against a blood red sky. Not since the great cataclysm of creation has the world born witness to a war amongst Angels. Yet, the world will not die... for we will not allow it.

Phase 1 is great. Not so much a fan of the rest but we can figure that out later.

warpdragon, I'm pretty sure they mostly want Catholic mythology, or else mythology, and not generic fantasy creations. I notice all of your introduced lore ideas so far don't actually touch on lore as it relates to mythology, and several of your lore suggestions to ideas which other people have introduced ignore the mythos as introduced by the character name.

We are going with a biblical/religious theme. Frankly for boss ideas I don't want you to post any lore. I don't care about that. Give me mechanics and nothing else.

I've found that lore is good inspiration for thinking of advanced mechanics. Like, the Larunda stage 1 idea. That kind of mechanic would be way at the back of my mind if I didn't have a 'girl who talks to the point of hurting of people'.

For Warpdragon

Currently that's all that impatience does, playing on the idea that the heroes have to bring the fight to him.
There is also knockback from his autos, which will also deal increased damage if it hits a stalactite.
3&5. That's a good point. I was considering the charge to be a point cast so the players can dodge out of the way. The interactions with the stalactites are exactly like the earth spirit's boulder ability. I'm thinking about adding a certain debuff if the boss charges into the arena wall. During the charge I planned for more SB charge than for skewer, but that would be cooler.
Sweeeet.
Picks up a nearby stalactite, throws it and creates more stalactites. Ideally yes heroes can be thrown too, and stalactites are formed to "cage" the hero.
Concussion is to enable the boss to perma-stun a single target. Demanding the team to rotate the tanking characters.
When I planned this, it was more of a Consuming Rocks if they are in reach. So ideally there are going to be people who try to rid the area of stalactites during the previous phases, and letting the Boss charge would be more punishing than in the previous phases. (and of course the protection stacks remove over time)
Awesome lore btw

Only Phase one was good, and we haven't really gone anywhere with it. Closed.


Glue model wizard

Can call wizard with the following
this.stack.push({
class: 'foam.nanos.crunch.ui.ScrollSectionWizardView',
ofList: [
'net.nanopay.sme.onboarding.BusinessOnboarding',
'net.nanopay.sme.onboarding.USBusinessOnboarding'
],
argsList: [{ userId: userId, businessId: businessId }, { userId: userId, businessId: businessId }]
});
addresses: https://nanopay.atlassian.net/browse/CPF-2140

merged in CrunchWIP - don't need this PR anymore


Add option to send messages with enter button (#1070)

Adds a new setting (default off), so users can send messages with the enter key of the soft keyboard instead of the dedicated send button.
Pull Request Checklist

[x] Changes has been tested on an Android device or Android emulator with API 16
[x] UI change has been tested on both light and dark themes
[x] Pull request is based on the develop branch
[x] Pull request updates CHANGES.rst
[x] Pull request includes screenshots or videos if containing UI changes
[x] Pull request includes a sign off

Hi @lixmal,
Thanks for the PR, it's merged and will be available in the next release
Benoit


Improve gitignore file comments and organization.

🗣 Description

Add a comment describing what the files does.
Add sections to organize patterns.
Add a pattern that developers may use to quickly ignore files private to their development environment.

💭 Motivation and context

I'd like to propose a pattern that we can use to quickly ignore files in our development environments.
I've found that sometimes I have the need for a scratch file, or a configuration that I'm testing locally that I don't want to end up under version control.
I've been using *-mine.*
This allows me to have files like TODO-mine.md, docker-compose-mine.yml, or secrets-mine.json  to live locally without fear of them making it into the repo.
A quick Google search didn't turn up any related proposals for something like this.   We could also use *-ignoreme.*,*-nocommit.*, *-yourmom.*
Pros:

Easy to use
Short and meaningful
Shouldn't ignore files inadvertently: e.g., hexanitrodiphenylamine.py

Cons:

Could inadvertently ignore a file: e.g.,land-mine.yml
Doesn't work with extension-less files : e.g., LICENSE-mine

Alternatives:

I could just set this in my ~/.gitignore_global file, and then git config --global core.excludesFile ~/.gitignore_global
(I'll probably do that as well)

🧪 Testing

Works for me!
📷 Screenshots (if appropriate)

✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All relevant repo and/or project documentation has been updated
to reflect the changes in this PR.
[x] All new and existing tests pass.

I don't like this. It's too dangerous, since it could exclude something important.
This feels to me like a personal preference that should be handled in your local global git configuration. As a result I suggest closing this PR unmerged.
"It's a no from me dog."

Yes, It could exclude something important.  But that is an easy fix.  I'd rather err on the side of excluding something instead of including it.
I'm fine with setting this in my globals if there is no value in this for anyone.
I checked that my IDEs are smart enough to honor that.
I would like to merge the comments still since we do have people using the skeletons as their first interaction with git.
I do not want to abandon this PR entirely.

I also like the comments and would like to add them. I don't have a strong preference, but would err or the side of the convenience exclusions as a personal setting.

...would err or the side of the convenience exclusions as a personal setting.

:point_up_2:


Update Font awesome classes to extend * instead of html

Originating from this bug - https://github.com/patternfly/patternfly-org/issues/1270
We need to use an extend because SASS will not let you import inside of a conditional. Let's change it so that the fa includes extend * instead of html. That will also reduce the specificity to just the fa classes.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update circe-core, circe-generic, ... to 0.14.1

Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-jawn
io.circe:circe-literal
io.circe:circe-parser
io.circe:circe-pointer

from 0.14.0-M3 to 0.14.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

labels: library-update, semver-pre-release

Codecov Report

Merging #7 (438d346) into main (2c20046) will increase coverage by 2.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main       #7      +/-   ##
==========================================
+ Coverage   76.39%   79.15%   +2.76%
==========================================
  Files          17       17
  Lines         572      547      -25
  Branches       20       29       +9
==========================================
- Hits          437      433       -4
+ Misses        135      114      -21

Impacted Files
Coverage Δ

...in/scala/io/circe/schema/validation/Compiler.scala
97.59% <0.00%> (-0.05%)
:arrow_down:

...a/io/circe/schema/validation/ValidationError.scala
12.50% <0.00%> (+5.83%)
:arrow_up:

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 2c20046...438d346. Read the comment docs.


Worker thread is not stopped when Unreliables.retryUntilSuccess times out

Unreliables.retryUntilSuccess is currently implemented so that the worker thread never stops calling the lambda if the future times out.
PR: https://github.com/rnorth/duct-tape/pull/5

Released #5 as duct-tape 1.0.8.
Thank you for the contribution @greenbird-chr, and apologies again for the delay.


Error while using generic joins for self joins (using intermediate collection)

Petar,
Thanks for all the work in meteor-kitchen. It is an extremely well thought out code generator. I am trying to write most of the code in the meteorkitchen for easy maintainability and pretty much getting everything that I have a need for supported so far. I had a use case for generic joins and was quite delighted to find that generic joins are supported directly.
I have noticed an issue while using generic joins to create self joins. I use an intermediate collection for this and specify both left and right collections and their primary keys in each document. It is working perfectly fine except when I use it to create a join with the same collection. e.g. left collection = right collection (with different ids for the test case). In this case I get this error at server
Exception from sub <query name> id <some id> Error: Publish function returned multiple cursors for collection <right collection>.
I am new to meteor and haven't yet figured out how to display an object or cursor at the server end so I did not debug much as to which cursors are being returned. I think it would be trivial to do that. It is this method .publishJoinedCursors in the publish code that is causing this.
Workaround : I just used "mrt:smart-publish" package. It works fine. But I have to override the meteorkitchen code for this.

Hi @paplet , perak:joins ppackage is written in rush and I am currently working on a new kitchen-GUI (in the same time improving kitchen-CLI), so I'll need to replace perak:joins with something else (or improve it to be bug-free and useful). It will be solved soon (in next 2-3 weeks). Until then... what to say... use "tricks" if you can.

Thanks @perak, its not a show stopper and the workaround is working perfectly. Thanks again for your help. Just a question, I am using only the kitchen-CLI and have never used the GUI. So should I post any issues/feature requests in this repository or the CLI?

This repository is fine. :+1:

This fork https://github.com/ljack/meteor-joins/tree/patch-1  fixes perak:joins to support multiple cursors for the same collection. I've used it successfully.

@ljack ,
Sorry for my ignorance, but I have no idea how I can use the patch. I downloaded the zip file, can you help where do I go from here?
Thanks.

You need to install it as meteor local package.
Basically: (from https://dweldon.silvrback.com/local-packages and memory)
cd your-meteor-project
mdir local_packages
cd local_packages
git clone https://github.com/ljack/meteor-joins.git (or maybe unzip here?)

should do it. If not make sure that the correct version of perak:joins is installed and the environment variable PACKAGE_DIRSpoints to the local_packages dir. You can check in your-meteor-project/.meteor/versions/ the version of perak:joins your project is using.

After I merge this, you'll be able to use it as normal package, but I need to find some time to test PR first...


feat: add BTC HDWallet

hdwallet into
hdwallet derive process

Well done, thank you for your contribution.
you can reply if you want enter develop group


Part 2 Step 2 should indicate that Not Available is not considered a failure

FAIL: <IP_ADDRESS>.b - An OBD ECU reported active/previously active fault DTCs count not = 0/0
Reported active fault count = -1
Reported previously active fault count = -1
is the same behavior as was observed in part 1, <IP_ADDRESS>.
I’m leaning toward,
No OBD ECU reported active/previously active fault DTCs count = 0/0
in both spots
As some secondary OBD ECU, May not support DM2 and will report 0/FF (all faults are 1 trip faults and primary ECU supports DM2/DM23 reporting).
Indeed, Systems were not required to add support for DM2 where none was provided before as evidenced by if supported in, <IP_ADDRESS> Fail criteria (if supported):

6.1.3 DM5: Diagnostic readiness 1
<IP_ADDRESS> Actions:
a. Global4 DM5 (send Request (PGN 59904) for PGN 65230 (SPN 1220)).
b. Create 'OBD ECU'5 list (comprised of all ECUs that indicate 0x13, 0x14, 0x22, or 0x23 for OBD compliance) for use later in the test as the “OBD ECUs”.
<IP_ADDRESS> Fail criteria:
a. Fail if no ECU reports as an OBD ECU.
b. Fail if any ECU responds with a NACK (for PGN 65230).
<IP_ADDRESS> Warn criteria:
a. Warn if more than one ECU responds with a value for OBD compliance where the values are not identical (e.g., if one ECU reports 0x13 and another reports 0x22, if one reports 0x13 and another reports 0x11).
6.2.2 DM5:  Diagnostic  readiness  1
<IP_ADDRESS> Actions:
a. Global  DM5 (send Request  (PGN 59904) for PGN  65230  (SPNs  12181223)).
b. Display  monitor readiness  composite  value  in  log for OBD ECU replies  only.
<IP_ADDRESS> Fail/warn criteria:
a. Fail/warn  per  the section  A.6 Criteria for Readiness  1  Evaluation.
b. Fail  if  any  OB D  ECU 27 reports  active/previously  active fault DTC count  not  =  0/0.
c. Warn  if  any  individual  required  monitor,  except  Continuous  Component  Monitoring  (CCM)  is  supported  by  more than  one  OBD  ECU.

I thought <IP_ADDRESS>.b would be updated as:
"No OBD ECU reported active/previously active fault DTCs count = 0/0"

This is now included above

The corrected text for 3.0.0 shall reflect
6.2.2 DM5: Diagnostic readiness 1
<IP_ADDRESS> Actions:
a. Global DM5 (send Request (PGN 59904) for PGN 65230 (SPNs 12181223)).
b. Display monitor readiness composite value in log for OBD ECU replies only.
<IP_ADDRESS> Fail/warn criteria:
a. Fail/warn per the section A.6 Criteria for Readiness 1 Evaluation.
b. Fail if no OBD ECU [27] reports active/previously active fault DTC count = 0/0.
c. Warn if any individual required monitor, except Continuous Component Monitoring (CCM) is supported by more than one OBD ECU.

<IP_ADDRESS>.b now says:
b.	Fail if no OBD ECU reports active/previously active fault DTC count = 0/0.


About network

 for stage_index in range(0, stage_number):             for conv_index in range(len(kernel_size_set)):                 layers.append(                     nn.Sequential(                         nn.Conv1d(channel, channel, kernel_size_set[conv_index], stride_set[conv_index], dilation=1, bias=True),                         nn.BatchNorm1d(channel, momentum=0.1)                     )                 )         self.stage_layers = nn.ModuleList(layers)
stage_number : 2  len(kernel_size) : 3         2*3 = 6

At the end of your paper,  ( Conv + BatchNorm + LReLU + Dropout ) or (Conv + BatchNorm + LReLU + Dropout + Adap AP) only have three layers ,not six layers.
Why?

Another question !!    In  pooling_shrink_net(base_model):
self.expand_conv = nn.Conv1d(in_features, channel, kernel_size=3, stride=2, bias=True)
However, in your paper, kernel_size = 1 , stride =1 , channel = 2048(not 1024,in your code) !!
I look forward to your answer!!

Thanks for your question, in here we use a little different settings with paper's.

In paper we just show the block strcuture, in one block there are three layers, but in experiments you can set different block numbers. And also, 1 stage(3 layer) is also works here, you can also use 1 stage to get same performance like h36m data. But 2 stage setting is rubuster in more cases so I set 2 as default number.
When you increase the channel number to 2048, the error will be lower around 52mm like what we show in the paper, but it requires more training time and model file storage(around 600mb rather than 100mb currently). So in the opensource version, I want to find a balance between performance and user-convenience so I choose the number 1024.


Revert "Fix bundle override in ManageIQ::Environment"

ManageIQ/manageiq#15585 unfortunately broke Travis in all provider repos, as bundle update doesn't take --path.
I'm testing a better fix (env BUNDLE_PATH), but until @Fryguy or @bdunne wake up to discuss that, I hope someone can merge this revert.

Travis fails with unrelated(?) spec failures, but should be scrutinized whether the revert is causing some havoc like getting old dependencies...
OK, now I'm confused.  https://travis-ci.org/ManageIQ/manageiq/jobs/254787502#L315 still runs
bundle install --jobs=3 --retry=3 --path=${BUNDLE_PATH:-vendor/bundle}

which this PR was supposed to undo?! 😕

kubernetes travis OTOH works against this:
https://travis-ci.org/cben/manageiq-providers-kubernetes/jobs/254829751

Closing in favor of #15589


Replaced OpenSSL for hash functions and AES

This change pulls SHA1, SHA256, SHA512, RIPEMD160 and AES code into the library, into a crypto subdir.
SHA1 is a conversion to C of the C++ code in bitcoin core.  Tests for standard test vectors have been added.
AES has been moved into the ccoin lib, along with wrappers exposing similar behavior to the OpenSSL calls.  Tests for this have been added, with test data generated by the old OpenSSL code to ensure that behavior has not changed.
This change will almost certainly conflict with the secp256k1 PR, so naturally I'll rebase whichever one, depending on which gets merged first.  I wanted to put this up anyway so it can be reviewed and discussed.

Coverage decreased (-1.9%) to 72.869% when pulling ea631ee172c1203a417d6a3387150c737667c296 on dtebbs:sha_ripemd160_aes into 43047f8cfea439f89df85edc684f5cdc0f9b7c8f on jgarzik:master.

Hi @dtebbs,
I see that as well as libsecp256k1  @sipa has written his own implementation of several crypto functions:
https://github.com/sipa/Coin25519/tree/master/src/crypto
Although they do not seem to have had many updates recently.
There is also the CT-AES module available in the bitcoin-core Github repository that can easily be added as a submodule or whatever.
I'm not sure if there is any advantage to using these over the ones you have chosen but they are written by bitcoin core developers and all use a MIT license.

The code is Coin25519 was a very short lived experiment, ages ago. Please don't use it for anything.
Bitcoin Core has its own naive implementations of cryptographic functions in https//github.com/bitcoin/bitcoin/tree/master/src/crypto. Those are well reviewed and well tested. It also includes ctaes as a subtree.

Hi Duncan,
Just a suggestion but should AES code be placed in the libccoin library?
https://github.com/dtebbs/picocoin/blob/sha_ripemd160_aes/lib/Makefile.am#L8-L14
AES is used by the wallet which should probably not be part of the core library. Here's how I did it in my fork of picocoin:
https://github.com/libbitc/libbitc/blob/master/lib/Makefile.am#L60-L66
I create a convenience library for AES. The plan is to eventually create a separate wallet library containing the AES code.

You guys might also want to have a look at https://github.com/libbtc/libbtc

@libbitc Yeah, that makes sense.  Actually, I was thinking of crypto as a kind of utility module or lib, but I see the point that aes could be split out.

@jonasschnelli yes, libbtc looks good and seems to be taking a similar direction to libccoin.  (and great name, btw :)
I'm interested in developing the client framework functionality in picocoin (which I think you've dropped from libbtc).  In any case there should be value in combining efforts if possible.

@dtebbs: I'm also interested in the client features. Check out the wallet format (liblogdb) and there are some client/wallet branches (https://github.com/jonasschnelli/libbtc/commit/742c886dfbb685bd6aa1241be7a6d56918445679).
I'd like to see a full featured SPV client built into libbtc with an optional compile flag in future.

I had similar objectives in mind when I forked picocoin into libbitc.
There is a lot of similarities between libbtc and picocoin but I chose to fork picocoin because it has the network functionality ready to go and also has some clients already written.
My short term goal with libbitc is to get it to pass most of the more recent bitcoin core tests and then passing those updates back into picocoin. When Jeff created picocoin a few years ago he used the then available tests from bitcoin core. I don't think they have been updated in picocoin much since then.
My mid-term goal with libbitc is to expand the wallet to use Jonas'  liblogdb.
Longer term I plan to add LMDB for the block database.
I agree with Duncan, there is always value in combining efforts if possible.

Needs rebase.

Coverage decreased (-1.2%) to 73.031% when pulling 5d233bed108b4892fef2ae5d9b46cfde5385c2ce on dtebbs:sha_ripemd160_aes into b36c27f07a987b7aa6525353d6bbfe124058c447 on jgarzik:master.

Coverage decreased (-1.2%) to 73.031% when pulling 5d233bed108b4892fef2ae5d9b46cfde5385c2ce on dtebbs:sha_ripemd160_aes into b36c27f07a987b7aa6525353d6bbfe124058c447 on jgarzik:master.

I've rebased the changes on to latest master

Closing; merged similar pull from @aido


AB#9145 Assessment Scoring Fields

Some unit tests could be added for this too.

hi @AndreGAot -- i have now pushed the unit test for this ticket. thanks.


Superset deployment

Overview
This PR contains superset configuration and cloud deployment changes for our data exploration tool.
Testing
How did you make sure this worked? How can a reviewer verify this?
# To-do list
- [ ] If updating analyses or data processing functions: make sure to update or write data validation tests (e.g.,  `test_minmax_rows()`)
- [ ] Update the [release notes](../docs/release_notes.rst): reference the PR and related issues.
- [ ] Ensure docs build, unit & integration tests, and test coverage pass locally with `make pytest-coverage` (otherwise the merge queue may reject your PR)
- [ ] Review the PR yourself and call out any questions or issues you have
- [ ] For minor ETL changes or data additions, once `make pytest-coverage` passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and [run relevant data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation) using `pytest` and `--live-dbs`.
- [ ] For significant ETL, data coverage or analysis changes, once `make pytest-coverage` passes, ensure the full ETL runs locally and [run data validation tests](https://catalystcoop-pudl.readthedocs.io/en/latest/dev/testing.html#data-validation) using `make pytest-validate` (a ~10 hour run). If you can't run this locally, run the `build-deploy-pudl` GitHub Action (or ask someone with permissions to). Then, check the logs on the `#pudl-deployments` Slack channel or `gs://builds.catalyst.coop`.

Thanks for all the great feedback! I pinned the docker base image version, updated auth0 env var instructions and set docker compose env var defaults. I also created some draft issues that I'll flesh out tomorrow.

You're hitting a bunch of this error in CI:
ERROR test/integration/glue_test.py::test_unmapped_utils_eia - TypeError: ForwardRef._evaluate() missing 1 required keyword-only argument: 'recursive_guard'

Which is related to dagster / python version incompatibilities: https://github.com/dagster-io/dagster/issues/22985


[Global] Error handling

Right now, errors just print to log. Notifications? User feedback?

Server side errors so app doesnt break?


Code generation does not add template parameters for struct name when calling static methods

Let's say I have the following Jakt code:
import extern "my_generic.h" {
   extern struct Generic<T> {
      function create(secret: T) throws -> Generic<T>
      function get_secret(this) -> T
   }
}

function main() {
    let generic = Generic::create(secret: 42i32)
    println("The answer to everything is: {}", generic.get_secret())
}

It will typecheck and generate:
#include <lib.h>
#include <my_generic.h>
namespace Jakt {
ErrorOr<int> main(Array<String>) {
{
// Generic::create doesn't have a template arguments
const Generic<i32> generic = TRY((Generic::create(static_cast<i32>(42))));
outln(String("The answer to everything is: {}"),((generic).get_secret()));
}
return 0;
}

} // namespace Jakt

Here, the typechecking is correct. It inferred correctly that I have created a Generic<i32>, and that Generic<T>::create throws. The problem is that codegen did not add the template arguments in Generic::create, and this confuses clang++:
❯ clang++ -w -I. -I<path/to/runtime> test.cpp -std=c++20
test.cpp:6:35: error: 'Generic' is not a class, namespace, or enumeration
const Generic<i32> generic = TRY((Generic::create(static_cast<i32>(42))));
                                  ^
./my_generic.h:5:8: note: 'Generic' declared here
struct Generic {
       ^
test.cpp:6:20: error: no viable conversion from 'void' to 'const Generic<i32>' (aka 'const Generic<int>')
const Generic<i32> generic = TRY((Generic::create(static_cast<i32>(42))));
                   ^         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
./my_generic.h:5:8: note: candidate constructor (the implicit copy constructor) not viable: cannot convert argument of incomplete type 'void' to 'const Jakt::Generic<int> &' for 1st argument
struct Generic {
       ^
./my_generic.h:5:8: note: candidate constructor (the implicit move constructor) not viable: cannot convert argument of incomplete type 'void' to 'Jakt::Generic<int> &&' for 1st argument
2 errors generated.

Clang fails at recognizing Generic as a struct, since it's really a template. Here are the contents of ./my_generic.h:
#include <Jakt/Error.h>

namespace Jakt {
template<typename T>
struct Generic {
    static ErrorOr<Generic<T>> create(T value);
    T get_secret() const;
};
}

The correct behavior should use Generic<i32>::create(static_cast<i32>), i.e instantiating the template explicitly.

Tracked it down to typechecker not filling the namespace.generic_parameters attribute in the resolved namespace. I tried checking if the last namespace was a struct then reference its generic_parameters array, but this doesn't resolve the T.


Not able to set custom 22-char device id

I have succesfully cloudcut my smart socket (no flashing yet, just cutting), and the cloudcutter set some random 20-chars deviceid.
I am now trying to use it with tinytuya and tuya-local, but they both fail to communicate with the device and I believe I know why:
Originally (ie. before the cut) the deviceid was 22-chars and I AFAIK tinytuya uses this count to decide which protocol it should use.
So, now I am trying to set the original deviceid (via -d parameter), but cloudcutter doesn't seem to like it:
Using DeviceId bfe4983bae6083f0e0a9hc and LocalKey 3Q1voW28pldTEyPc

usage: cloudcutter exploit_device

       [-h]

       [--output-directory OUTPUT_DIRECTORY]

       [--deviceid DEVICE_ID]

       [--localkey LOCAL_KEY]

       profile

       verbose_output

cloudcutter exploit_device: error: argument --deviceid: invalid check_arg value: 'bfe4983bae6083f0e0a9hc'

Oh no, something went wrong with running the exploit! Try again I guess...

Is there a reason why one cannot set 22char deviceIds?

The 20 vs 22 length shouldn't be the issue with TinyTuya, as the protocol it falls back to should work fine, that has been pretty well tested.  It's just not an area much research/testing has been done.  You are welcome to attempt to change the length restrictions.  I think the worst that could happen is the exploit doesn't work, in which case it remains at the previous device id.

Could you point me to the appropriate place in the code where this is defined?

https://github.com/tuya-cloudcutter/tuya-cloudcutter/blob/cdc29466cd279bf569dba2d8c3370cd309fa097d/src/cloudcutter/__main__.py#L397

Just to follow-up on this - I was not able to set the id, but the reason for this was very poor connectivity to the device - I was getting "802.1X supplicant took too long to authenticate" most of the time. This wasn't cloudcutter fault, it was like that before - i think my wifi dongle is dying slowly :).
I eventually was tired of trying and ended up flashing esphome.


BMFont binary format

I noticed that the BMFont-related API uses data strings (not Stream) and doesn't support loading BMFont binary format at the moment. I added binary format support, a couple lines of code to LoadBMFont where it expects a Base64-encoded string. Base64 seems pretty universal and reasonably efficient without requiring custom encoding on the user's part. Alternatively, adding functions that accept Stream data would probably be the most efficient solution.

thanks @tadashibashi!


[Device] TuYa ZS06

Please use the template and fill in all the data requested below!
Device description
Which device would you like to be supported in this plugin?
TuYa ZS06
Supported in Zigbee2MQTT?
Is this device already supported by Zigbee2MQTT / zigbee-herdsman-converters?
Yes it is supported
Device model / Exposes information
Provide the device model (also known as exposes information) for this particular device, as published to zigbee2mqtt/bridge/devices by Zigbee2MQTT.
[
  {
    "type": "switch",
    "features": [
      {
        "type": "binary",
        "name": "state",
        "property": "learn_ir_code",
        "access": 2,
        "value_on": "ON",
        "value_off": "OFF",
        "description": "Turn on to learn new IR code"
      }
    ]
  },
  {
    "type": "text",
    "name": "learned_ir_code",
    "property": "learned_ir_code",
    "access": 1,
    "description": "The IR code learned by device"
  },
  {
    "type": "text",
    "name": "ir_code_to_send",
    "property": "ir_code_to_send",
    "access": 2,
    "description": "The IR code to send by device"
  },
  {
    "type": "numeric",
    "name": "linkquality",
    "property": "linkquality",
    "access": 1,
    "unit": "lqi",
    "description": "Link quality (signal strength)",
    "value_min": 0,
    "value_max": 255
  }
]

Missing features/functionality
Its not supported
Suggested services and characteristics
I want to add my air conditioner

Unfortunately, I don't think I can support this device in this plugin, as the usage really depends on the IR device learned and I can't make a "one size fits all" conversion for this device.
If possible, I would suggest to use homebridge-mqttthing for this particular device instead.

I've got this device as well, and though I understand it may not be feasible to support it natively, is there a way to send the codes that i've learned with it?

is there a way to send the codes that i've learned with it?

That should be possible with homebridge-mqttthing


TextInputEditText missing

package id="Xamarin.Android.Support.Design" version="<IP_ADDRESS>" targetFramework="monoandroid71"
Xamarin.Android Version (eg: 6.0):
<IP_ADDRESS>
Operating System & Version (eg: Mac OSX 10.11):
Win10
Support Libraries Version (eg: 23.3.0):
<IP_ADDRESS>
Describe your Issue:
TextInputEditText class is missing. Was there in v25.3
Steps to Reproduce (with link to sample solution if possible):
Include any relevant Exception Stack traces, build logs, adb logs:
https://developer.android.com/reference/android/support/design/widget/TextInputEditText.html

Did you try <IP_ADDRESS>?


[excel] (Samples) Make prerequisite note more prominent

This is based on a customer verbatim around not finding the Automate tab after starting one of the samples.

Docs Build status updates of commit c91beb9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resources/samples/samples-overview.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Make it easy to find out the k8s and flux version

Closes #2285
Closes #2328

I've added a namespace to the GetVersionRequest object to make TestGetVersion pass because it could not find the flux-system namespace without it. So, for the test I create a new namespace or if the namespace is not provided default to flux-system (wego.DefaultNamespace constant). If anyone knows how to improve this and the issue with nested ifs (will add a comment), I'm all ears. 🙂

UPDATE: Removed the namespace field from GetVersionRequest (switched to listing namespaces) and fixed nested ifs based on @ozamosi 's suggestions.

I've copy-pasted the test for GetImpersonatedDiscoveryClient from the test for GetImpersonatedClient. I am not sure what this API does and what exactly should be tested, maybe it should be modified.

Also removed the following from the copied test, maybe it should be put back (this part was failing because the number of found namespaces in the copy-pasted part was 0 instead of 1 or 2):
t.Run("checks all namespaces in the cluster when through the filtering", func(t *testing.T) {
	g.Expect(nsChecker.FilterAccessibleNamespacesCallCount()).To(Equal(1))

	_, _, nss := nsChecker.FilterAccessibleNamespacesArgsForCall(0)
	nsFound := 0
	for _, n := range nss {
		if n.Name == ns1.Name || n.Name == ns2.Name {
			nsFound++
		}
	}

	g.Expect(nsFound).To(Equal(2))
})

@ozamosi @chanwit also, maybe I can use the VersionLabelKey from the flux.go instead of app.kubernetes.io/version to get the label value?

@ozamosi @chanwit also, maybe I can use the VersionLabelKey from the flux.go instead of app.kubernetes.io/version to get the label value?

Sounds good!

@ozamosi @chanwit added grabbing a namespace from the list of namespaces. For testing, I create a new namespace with required key because the flux-ns namespace available during testing doesn't have a Flux version.
Also moved creating scoped client, getting Flux and K8s version to separate functions, based on @ozamosi 's suggestion.
@chanwit just in case added checking for nil when getting the version from labels.
@joshri I've added displaying Flux and Kubernetes versions in the footer. Also added noWrap to the Text component and  removed neutral30 color specified for some footer elements because it is already specified for the whole footer, it looks like, the elements already inherit this color from footer. If it is wrong, can move it back.
Spaced elements based on the draft design in the UI ticket description to make it consistent with current styling of the Footer component. Please let me know if styling/spacing/whatever is wrong.

@ozamosi @chanwit also, would it be possible to filter for Version label key with any value? Or only filtering by specific values is possible?
opts := client.MatchingLabels{
    coretypes.PartOfLabel: FluxNamespacePartOf,
    flux.VersionLabelKey: <any value>
}

Right now I am filtering labels only by coretypes.PartOfLabel: FluxNamespacePartOf, and then loop through the result and find a label which has flux.VersionLabelKey key.

@ozamosi OK, thank you, got it, will add the changes now.


Old UI option not working

I dislike the fact that this moves the lyrics button over to the right sidebar and i've used other forks of SpotX before but they only got rid of the popups, not the actual between-song ads and i know that the old ui option fixes the lyrics button however when i use it in the terminal command it says "Warning: Old UI not supported in clients after v<IP_ADDRESS>1...". how can a get around that?
also, i saw that there was older updates of this repo that say they work with my version of spotify (<IP_ADDRESS>7) such as this and i was wondering if using that would do it. i don't know how to get that one though so i can't test it. i can program but i don't know much about shell scripting at all.

Any other forks of SpotX are either unofficial, outdated or use commands from this repo. Windows is https://github.com/SpotX-Official/SpotX and mac/linux is https://github.com/SpotX-Official/SpotX-Bash
The title of this issue is misleading -- as the error message stated, the Old UI option requires <IP_ADDRESS>1 or earlier.  If you had a supported client, it would work. You being unable to use something does not mean the script is broken.. you just haven't read through the README and FAQ.

Uninstall current client, install <IP_ADDRESS>1. This is what the -V <version> flag is for.
Stay on current version (or any recent version) and enable developer mode and toggle the experimental feature to disable moving lyrics into the right sidebar. You want to disable enableRightSidebarLyrics

The README and FAQ explain everything outlined in this response. Read it. Apply it.
Things covered in the README and FAQ do not belong here.


[Video] Add Conv3D layer

We are missing some layers to support the export of models from Keras fully. One of them is the Conv3D layer. A detailed description of the layer can be found here

[ ] add layer class to the  package using Conv2D as a reference implemntation
[ ] add documentation
[ ] add test
[ ] add export function  ModelSaver.kt)
[ ] add import function (see ModelLoader.kt
[ ] (optional) create an example

This issue depends on the results of the #59

I can take it after the merge of #59


The preview panel displays as blank if sort by one column against union.avro file

Storage Explorer Version: 1.31.0
Build Number: 20230810.9
Branch: rel/1.31.0
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Ventura 13.5 (Apple M1 Pro)
Architecture: x64/x64/arm64
How Found: Ad-hoc testing
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Upload the file (union.avro).
Select the file -> Click 'Preview'.
The preview panel opens -> Sort by one column.
Check whether the preview panel displays correctly.

Expected Experience
The preview panel displays correctly.
Actual Experience
The preview panel displays as blank.
Additional Context

This issue doesn't reproduce for other avro files.
This issue also reproduces for ADLS Gen2 blob containers/file shares.
Here is the record:

Verified this issue on the build 20240117.1. Fixed.


Nerf_to_world.json

Hi, is it available to share the method to create nerf_to_world.json for self-sampled data?

Hi, the nerf_to_world.json calibration is based on your setup. If you already have ground truth transforms in transforms.json, then you can use the inverse of the dataparser_transforms.json that nerfstudio writes which contains the scale and transformation shifts applied to the poses.
Otherwise, you will need to find the calibration.

Closing this issue, feel free to reopen if you have are still encountering problems.

Hi, how can I get the inverse of the dataparser_transforms.json？ Is there a formula？

Hi, the nerf_to_world.json calibration is based on your setup. If you already have ground truth transforms in transforms.json, then you can use the inverse of the dataparser_transforms.json that nerfstudio writes which contains the scale and transformation shifts applied to the poses.
Otherwise, you will need to find the calibration which you can do using traditional calibration methods.

Hello,could you explain the method of obtaining Nerf_to_world.json in more detail?  I have never been able to make my own Nerf_to_world.json, which resulted in incorrect point sampling in the workspace.The current explanation is too difficult for me！

Hi, please open a new issue if you are encountering problems. We have some additional details on how to calibrate here: https://github.com/f3rm/f3rm/issues/15#issuecomment-2067306367
If there are any individual steps you want clarification on there, you can comment on that issue.

Sorry to bother you. May I ask why there is no scale in nerf_to_world.json?

The scale is embedded in the 4x4 matrix in nerf_to_world.json.


Binary from AppVeyor unavailable

So I looked around a bit, and I couldn't find any way to put my hands on the dinput8.dll file. Like, when I go on the AppVeyor page, it just says "The build job does not contain any artifacts." via the link in the description on github, or when I try on the nexus page of the fps mod, the link says "Project not found or access denied."
Soo if anyone could help me, I would love it 👌
Please ;-;

I will usually put mirrors up here: http://praydog.com/projects/


Fix product sorting

I want to merge this change because...

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-1971 Use errors field and drop Errors


Protractor with Version 5

HI,
I know this library comes with protractor version 4, some of my test cases are not working since I wrote my test script using protractor version 5 functions.
Is there a way to upgrade protractor to version 5 in this library?
Thanks

I would also like for everything to get upgraded to current versions.


[stable/locust] Reference master replicas from values

Description
Reference master replica count from values so users may scale a load test down (including the master node) without uninstalling the chart.
Checklist

[x] Title of the PR starts with chart name (e.g. [stable/mychartname])
[x] I have read the contribution instructions, bumped chart version and regenerated the docs
[ ] Github actions are passing

OK nice, thanks @chamilto 🎉 But you also need to update the README, see contribution docs.

Hey! Sorry about that - looks like I had bumped the chart version after I ran the README gen. Fixed.


Add tests to make sure release won't be easily broken

Release tests are currently broken.
From @mattdelco, "the tests complain that there wasn't a specific sha to test against, which was because the manifest.xml isn't present, which is because the build failed, which is because someone modified the archive creation script."
We should add some unit tests to cover the things that the release process cares about, and prevent people from merging things that can break the release process. And these tests need to be clear about what is broken, and what in the release process needs to be fixed.
Without these, we will only be seeing release failures late and we have to reactively fix the pipeline.

Why don't we consolidate release/build tool, and make a review by
release/test team mandatory using CODEOWNERS?
On Fri, Feb 2, 2018 at 10:02 AM Andy Lai<EMAIL_ADDRESS>wrote:

Release tests are currently broken.
From @mattdelco https://github.com/mattdelco, "the tests complain that
there wasn't a specific sha to test against, which was because the
manifest.xml isn't present, which is because the build failed, which is
because someone modified the archive creation script."
We should add some unit tests to cover the things that the release process
cares about, and prevent people from merging things that can break the
release process. And these tests need to be clear about what is broken, and
what in the release process needs to be fixed.
Without these, we will only be seeing release failures late and we have to
reactively fix the pipeline.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3105, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJGIxjCAe2DMBWvGxxD5_aWbJdnEQZ0dks5tQ0jngaJpZM4R3iRB
.

Yes I like that idea. =)
On Fri, Feb 2, 2018 at 10:45 AM, Kuat<EMAIL_ADDRESS>wrote:

Why don't we consolidate release/build tool, and make a review by
release/test team mandatory using CODEOWNERS?
On Fri, Feb 2, 2018 at 10:02 AM Andy Lai<EMAIL_ADDRESS>wrote:

Release tests are currently broken.
From @mattdelco https://github.com/mattdelco, "the tests complain that
there wasn't a specific sha to test against, which was because the
manifest.xml isn't present, which is because the build failed, which is
because someone modified the archive creation script."
We should add some unit tests to cover the things that the release
process
cares about, and prevent people from merging things that can break the
release process. And these tests need to be clear about what is broken,
and
what in the release process needs to be fixed.
Without these, we will only be seeing release failures late and we have
to
reactively fix the pipeline.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3105, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJGIxjCAe2DMBWvGxxD5_
aWbJdnEQZ0dks5tQ0jngaJpZM4R3iRB>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/3105#issuecomment-362669371, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkOvcuxnS1DFEYISdtH5VcOoSTdh5ks5tQ1bDgaJpZM4R3iRB
.

While we're quoting me lets also include this other quote:
a way to get greater consistency between CI and CB is to:

add a "make sidecar.deb docker.save istio-archive" for the istio repo to CI
or
add the items from #1 to the "artifacts" target in the istio repo.

#2 is probably cleaner and avoids the need to keep greenbuilds in sync with istio (or makes it easier to keep the "artifacts" target consistent with cloud_builder.sh [or perhaps just have cloud_builder.sh use the artifacts target). I saw mostly "chicken" about changing the artifacts target since I don't know who else uses it (nor why) and I was trying to limit the scope of how disruptive my large PR would be.


Override diff time

It'd be nice if there was a way to override the diff time. There are times when I'm less interested about the time between debug calls and more interested about the time it took to do something. I'm not sure what the best way to do this would be but here are a couple ideas:
const debug = require('debug')('app:controller');
debug.markTime();
//... Some long running task
debug('Task complete');
// => app:controller Task complete +2s

const debug = require('debug')('app:controller');
const hirestime = require('hirestime');
const getElapsed = hirestime();
//... Some long running task
debug('Task complete', { time: getElapsed() });
// => app:controller Task complete +2s

Otherwise with the current implementation limitations, output looks something like this:
const debug = require('debug')('app:controller');
const hirestime = require('hirestime');
const getElapsed = hirestime();
//... Some long running task
debug(`Task complete took ${getElapsed()}`);
// => app:controller Task complete took 12ms +2s

Or you have to make two debug logs which still isn't ideal
const debug = require('debug')('app:controller');
debug(`Start task`);
//... Some long running task
debug(`Task complete`);
// => app:controller Start task +5s
// => app:controller Task complete +12ms

It's not a major issue but it'd be so much prettier to have only my custom timing displayed and color coded.
What are your thoughts?

I should also mention, I'd be happy to submit a PR on this.

:-1: this would introduce so much extra code for a use-case that is mis-using the library.
Please don't seek to change these readouts as it reduces their usefulness and trustworthiness.

It's one line of code actually
debug.markTime = () => (prevTime = new Date());

So you override the entire debug context's timer? How is that useful for anyone?

Yes, it's the equivalent of calling debug with no output. How is that harmful? It's useful because I can see how long something took to run.

Use a different namespace if you want different times. I don't think we'll do this - it's almost definitely an anti-pattern.


Suggestions about the Peek utility

Description of the new feature / enhancement
Hi,
As a user of QuickLook, I'd like to make three sugestions for the Peek utility (I'm currently running PowerToys 0.70.0):

Support for more formats (audio, video, Microsoft Office and LibreOffice documents, etc.). I presume the list of supported formats will grow over time.

I'd like to be able to peek on a file by just pressing SPACE, but the settings won't allow me to do that. SPACE is what I press in QuickLook and also the key by default (as far as I know) in MacOS, which is where this type of feature has been taken from. Having to press a combination of keys would make my life more complicated (I currently use CTRL+SPACE and ALT+SPACE, so adding Windows+SPACE would make this area of my keyboard too crowded). As a user, I should be able to decide the key I want to use for each utility.

In QuickLook, when I'm peeking on a document, I can click UP or DOWN and move to the previous or following document. This is quick and convenient.

Thanks for this new feature, which I'm hoping will keep getting beter and better.
Scenario when this would be used?
When peeking on files on File Explorer.
Supporting information
No response

3. In QuickLook, when I'm peeking on a document, I can click UP or DOWN and move to the previous or following document. This is quick and convenient.

Actually it's all the directional keys. This the one thing why I keep using Quicklook. It's by far the best advantage of the original macOS implementation, even though it's not perfect even in QuickLook.
The other useful feature I find in Quicklook (msi version) that Peek doesn't appear to support is previewing in any File Explorer dialog, especially. This is useful to check a file's content just right before you're attaching it to an email for example.

In QuickLook, when I'm peeking on a document, I can click UP or DOWN and move to the previous or following document. This is quick and convenient.

For photo preview, I think it's better to change to left/right arrow.

In QuickLook, when I'm peeking on a document, I can click UP or DOWN and move to the previous or following document. This is quick and convenient.

For photo preview, I think it's better to change to left/right arrow.

I think both combinations of keys should be allowed. In my particular case, File Explorer is in Detail mode, so when I move from one file to another, I actually go up or down.

It seems on Peek you cannot be use on Select File Window when you're trying to upload a file on the browser, while QuickLook can.

There are certain features that may make or not make sense on paper and it's hard to know whether they are for us unless we try them. That's what I did with QuickLook and, after a while, I was convinced the feature was useful to me.
Having said that, for this feature to be useful, two conditions need to be met:

The shortcut must be simple: that's why I suggested allowing just the SPACE. It's a long key, quick to press and easy to remember.

To close the window with the peak of the document, you should also be able to press SPACE again. It's essential to make sure this feature is easy and quick to use.

Of course, this is all subjective, but I'm talking about what's worked for me with QuickLook.

Yeah keyboard shortcut for this isn't ideal.
I was multi-selecting folders in Windows Explorer and Peek popped up. No indication it was coming from PowerToys and the window title was an unhelpful "WinUI Desktop"
Had to disable it, otherwise can't get anything done

Hey friends, this has multiple asks in it.  I feel they all have tracked asks. One issue per request else it becomes near impossible for us to track asks.
/dup https://github.com/microsoft/PowerToys/issues/26210 is tracking the office file ask.


Is it possible that we can add -mprefer-agnostic compile option for VSETVL optimization of RVV?

Consider this following case:
https://godbolt.org/z/oTWvrsGhE
Code:

void f (void * restrict in, void * restrict out, int n, int cond)
{
  size_t vl = 101;
  for (size_t i = 0; i < n; i++)
    {
      vint8mf8_t v = __riscv_vle8_v_i8mf8 (in + i, vl);
      __riscv_vse8_v_i8mf8 (out + i, v, vl);
    }

  for (size_t i = 0; i < n; i++)
    {
      vuint8mf8_t index = __riscv_vle8_v_u8mf8 (in + i + 300, vl);
      vfloat32mf2_t v = __riscv_vle32_v_f32mf2 (in + i + 600, vl);
      v = __riscv_vle32_v_f32mf2_tu (v, in + i + 800, vl);
      __riscv_vsoxei8_v_f32mf2 (out + i + 200, index, v, vl);
    }
}

GCC by default enable VTYPE && POLICY fusion of vsetvli as long as they are compatible:
f:
        beq     a2,zero,.L1
        li      a3,101
        mv      a4,a1
        add     a6,a0,a2
        mv      a5,a0
        vsetvli zero,a3,e32,mf2,tu,ma
.L3:
        vle8.v  v1,0(a5)
        addi    a5,a5,1
        vse8.v  v1,0(a4)
        addi    a4,a4,1
        bne     a5,a6,.L3
        addi    a0,a0,300
        addi    a1,a1,200
        add     a2,a0,a2
.L5:
        addi    a4,a0,300
        vle32.v v1,0(a4)
        addi    a4,a0,500
        vle8.v  v2,0(a0)
        vle32.v v1,0(a4)
        addi    a0,a0,1
        vsoxei8.v       v1,(a1),v2
        addi    a1,a1,1
        bne     a2,a0,.L5
.L1:
        ret

I believe most of the cases, that GCC codegen is better.
However, for some vendor RVV CPU which has vector register renaming
&& vsetvli special optimization (vsetvli execution latency almost consume 0 cycle most of the time),
I believe this following codegen is better:
f:
        beq     a2,zero,.L1
        li      a3,101
        mv      a4,a1
        add     a6,a0,a2
        mv      a5,a0
        vsetvli zero,a3,e32,mf2,tu,ma
.L3:
        vle8.v  v1,0(a5)
        addi    a5,a5,1
        vse8.v  v1,0(a4)
        addi    a4,a4,1
        bne     a5,a6,.L3
        addi    a0,a0,300
        addi    a1,a1,200
        add     a2,a0,a2
.L5:
       vsetvli zero, a3, e8, mf8, ta, ma
        addi    a4,a0,300
        vle32.v v1,0(a4)
        addi    a4,a0,500
        vle8.v  v2,0(a0)
       vsetvli zero, zero, e32, mf2, tu, ma
        vle32.v v1,0(a4)
        addi    a0,a0,1
        vsoxei8.v       v1,(a1),v2
        addi    a1,a1,1
        bne     a2,a0,.L5
.L1:
        ret

I think fusing VTYPE is always optimal, for example:
https://godbolt.org/z/dfx93jzrv
code:
void f (void * restrict in, void * restrict out, int n, int cond)
{
  size_t vl = 101;
  for (size_t i = 0; i < n; i++)
    {
      vint8mf8_t v = __riscv_vle8_v_i8mf8 (in + i, vl);
      __riscv_vse8_v_i8mf8 (out + i, v, vl);
    }

  for (size_t i = 0; i < n; i++)
    {
      vuint8mf8_t index = __riscv_vle8_v_u8mf8 (in + i + 300, vl);
      vfloat32mf2_t v = __riscv_vle32_v_f32mf2 (in + i + 600, vl);
      __riscv_vsoxei8_v_f32mf2 (out + i + 200, index, v, vl);
    }
}

optimal codegen:
f:
        beq     a2,zero,.L1
        li      a3,101
        mv      a4,a1
        add     a6,a2,a0
        mv      a5,a0
        vsetvli zero,a3,e32,mf2,ta,ma
.L3:
        vle8.v  v1,0(a5)
        addi    a5,a5,1
        vse8.v  v1,0(a4)
        addi    a4,a4,1
        bne     a5,a6,.L3
        addi    a0,a0,300
        addi    a1,a1,200
        add     a2,a0,a2
.L5:
        addi    a4,a0,300
        vle8.v  v1,0(a0)
        vle32.v v2,0(a4)
        addi    a0,a0,1
        vsoxei8.v       v2,(a1),v1
        addi    a1,a1,1
        bne     a0,a2,.L5
.L1:
        ret

However, Policy fusion is not always the optimal, Is it resonable adding such compile option (-mprefer-agnostic) to disable tail Policy && mask policy
fusion in vsetvli ?
Thanks

That's highly depended on the uarch, so I would prefer just tie to -mtune like other cost model for GCC, but I think it's harmless to just add that in GCC first to see if that's useful, then implement to LLVM and then document that option here.
Personally I would prefer do not document those optimization option in this repo since those flags are compiler-dependent, and just document for necessary common interface here like -march, -mabi and -mcmodel here.

Agreed.  This is going to be dependent on multiple features of the uarch.
So I think the question is whether or not any such implementations exist or will exist in the near future.  If not, then let's not complicate things right now.  If it looks like such architectures are on the horizon, then we might as well be prepared for them.
I don't think this will affect Veyron V2.


Make the README build badge report only on main branch status

For the build badge in the README:

Use an image which reflects the status of the CI workflow only for the main branch
Put a link that opens the workflows directly on the CI workflow for the main branch

I think it makes more sense for the badge to only reflect the status of the main branch. It's "normal" for PR builds to fail (sometimes 😅 ), and I assume we don't want the main README to be red in that case.

@caarmen: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/


Revert "RC1+MV " - Backup

Reverts hmcts/ccd-definition-store-api#456

Hi @hemantt, what's the purpose of this PR?


[NEW] Notify new message in the chat room

When seeing older messages the users are unable to know when a new message arrives in the chat room. It will be nice if, when not showing the most recent message (i.e the scroll isn't at the bottom of the view), notify the user about a new message arrival.

Hi, I would like to contribute to this issue, I have some experience with Android, could you guide me further.

That's great @shubhsherl !
We have a channel in our server that we discuss everything related to the Android app. Could you join us there?
Here are the orientation of how we think about the behaviour of this feature: https://open.rocket.chat/channel/androidnativeapp?msg=ceGsrnJFtoFz3E6Lt
This is important too: https://open.rocket.chat/channel/androidnativeapp?msg=K9hN7WRZzT2D6Kyx5
Thanks for you interest!


controller callback

Hi,
I'm a student and I'm trying to use MuJoCo for robot motion control.
I'm looking for some help with "mjcb_control”. I was wondering whether there is any way to write some controller, like "void someController(const mjModel* m, mjData* d, double XXX)". Here, 'XXX' is some extra control information, for example reference torque. But the pointer of such function cannot be assigned to mjcb_control. Any  help will be appreciated! Thanks!

mjData has a userdata field. You declare it by adding
<size nuserdata="n"/>

to your model XML which will allocate a field of n mjtNums (doubles). Then you can put whatever you want in data->userdata.


test success

Type: Other
Summary:
test success
Details:
test success
Resolution:
test success
Affected definitions:

external-dns-management ae804dcb1b3a49ded12169c694130993c68ced9f

You can review the change introduced to the full definition at ClearlyDefined.


Error: The process '/usr/bin/rsync' failed with exit code 255

Bug Description
A clear and concise description of what the bug is.
My Action Config
on:
  push:
    # !!!!!!! TODO Fill Out !!!!!!!

My Action Log
   # Paste Log here

Bug Description A clear and concise description of what the bug is.
My Action Config
on:
  push:
    # !!!!!!! TODO Fill Out !!!!!!!

My Action Log
   # Paste Log here

You need to set the folder user ownership at your server.

Make sure the destination directory is owned by the user running rsync.
Use chown to change ownership if needed. For example:
sudo chown -R user /path/to/destination

"user" is your server username

Also if you do not have the rsync installed in your linux server, you need to run
sudo apt update && sudo apt install rsync -y

Hey @michellavezzo I managed to get it working after installing Rsync—thank you so much!
Regarding ownership permissions, I encountered a similar issue while using LAMP Packaged by Bitnami on a Lightsail VPS. I couldn't create files until I stumbled upon this fix:
sudo chown -R bitnami:daemon /opt/bitnami/apache/htdocs
sudo chmod -R g+w /opt/bitnami/apache/htdocs

Do you think this setup should work fine?
I've got another question about the rsync options. It appears that the deployment doesn't work when specifying exclusions without these options: --archive --verbose --compress --human-readable --progress --delete-after. Are these necessary? If so, any idea why?
Thanks in advance for your help! 🙏

Hey @michellavezzo I managed to get it working after installing Rsync—thank you so much!
Regarding ownership permissions, I encountered a similar issue while using LAMP Packaged by Bitnami on a Lightsail VPS. I couldn't create files until I stumbled upon this fix:
sudo chown -R bitnami:daemon /opt/bitnami/apache/htdocs
sudo chmod -R g+w /opt/bitnami/apache/htdocs

Do you think this setup should work fine?
I've got another question about the rsync options. It appears that the deployment doesn't work when specifying exclusions without these options: --archive --verbose --compress --human-readable --progress --delete-after. Are these necessary? If so, any idea why?
Thanks in advance for your help! 🙏

To be honest, I don't know how to answer your questions hehe, but I hope a good citizen has his answers.

Can any one check the below image and help me on it. I am setting CI/CD for AWS ec2. Trying to solve the error for more than 2 days but am not getting the proper solution on the internet 😥.
Thank you in advance.

@Aatmik-Sanghvi  can you share me your workflow code ?

@Aatmik-Sanghvi try this one and don't forget to give ur TARGET PATH permissions
"on": push
name: Publish Website
jobs:
  web-deploy:
    name: "\U0001F680 Deploy Website Every Commit"
    runs-on: ubuntu-latest
    steps:
      - name: "\U0001F69A Get Latest Code"
        uses: actions/checkout@v3
      - name: "\U0001F4C2 Sync Files"
        uses: SamKirkland/web-deploy@v1
        with:
          target-server: "${{ secrets.DEPLOY_HOST }}"
          remote-user: "${{ secrets.DEPLOY_USER }}"
          private-ssh-key: "${{ secrets.DEPLOY_PRIVATE_KEY }}"
          destination-path: ~/htdocs
          rsync-options:
            --archive --verbose --compress --human-readable --progress --delete-after
            --exclude=.git* --exclude=.git/ --exclude=README.md --exclude=readme.md
            --exclude=webpack.config.js
            --exclude=.gitignore --exclude=config.php --exclude=secrets.php --exclude=node_modules/ --exclude=.vscode/
            --exclude=package.json --exclude=package-lock.json --exclude=purgecss.config.js --exclude=tailwind.config.js
            --exclude=input.css --exclude=composer.json --exclude=composer.lock --exclude=content/uploads/ --exclude=install.php --exclude=App/Ajax/install.php --exclude=webpack.config.js --exclude=App/logs/ --exclude=update_bd.sql

@mimoudix sure here it is,
`
name: Laravel Deployment to AWS EC2
on:
push:
branches:
- master
jobs:
deploy:
name: Deploy Laravel to EC2
runs-on: ubuntu-latest
steps:
  # Checkout the code
  - name: Checkout Code
    uses: actions/checkout@v2

  # Deploy files to EC2
  - name: Deploy to EC2
    uses: easingthemes/ssh-deploy@main
    env:
      SSH_PRIVATE_KEY: ${{ secrets.SSH_PRIVATE_KEY }}
      REMOTE_HOST: ${{ secrets.EC2_HOST }}
      REMOTE_USER: ${{ secrets.EC2_USERNAME }}
      TARGET: "/var/www/html/my-book-mate"
      ARGS: "-o StrictHostKeyChecking=no"

  # Run Laravel artisan commands
  - name: Run Laravel Artisan Commands
    run: |
      ssh -o StrictHostKeyChecking=no<EMAIL_ADDRESS><< 'EOF'
      cd /var/www/html/my-book-mate
      php artisan migrate --force
      php artisan cache:clear
      php artisan config:cache
      php artisan route:cache
      EOF

`


feat: github pages with eleventy

switching to nunjucks of the main page of the site (on development stage)

Ok, looks like github stalled on the checks, I'll try to kick it...

:tada: This PR is included in version 3.0.0-beta.7 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.7.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Text-transform rules doesn't work

uppercase, capitalize, lowercase seems to doesn't work. Even trough the shortcut
unocss v0.9.0
vitesse-nuxt3 template
same with vitesse-lite (also tested with unocss v0.4.9 and v0.7.7)

see https://github.com/antfu/unocss/blob/main/packages/preset-uno/src/rules/static.ts#L57:
export const textTransforms: Rule[] = [
  ['case-upper', { 'text-transform': 'uppercase' }],
  ['case-lower', { 'text-transform': 'lowercase' }],
  ['case-capital', { 'text-transform': 'capitalize' }],
  ['case-normal', { 'text-transform': 'none' }],
]

I intentionally didn't support them is I thought Tailwind's convention is too general - but giving the fact that we are already trying to support all utilities from Tailwind, I am fine to have them. PR welcome

see https://github.com/antfu/unocss/blob/main/packages/preset-uno/src/rules/static.ts#L57:

How to make it work? In my nuxt.config.ts i've already using presetUno()
export default defineNuxtConfig({
buildModules: [
'@vueuse/core/nuxt',
'@unocss/nuxt',
'@pinia/nuxt',
],
unocss: {
presets: [
presetUno(),
],
},
})

just use case-upper, case-capitalize...

@ztxone just use case-upper, case-capitalize...

ohh) Sorry for that silly question.
Big thanks for rapid reply!


Enhance tc_gen to support file lists for the -genesis and -track command line options.

Describe the Enhancement
Enhance tc_gen to support file lists for the -genesis and -track command line options.
Time Estimate
1 day.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
No sub-issues required.
Relevant Deadlines
None
Funding Source
None
Define the Metadata
Assignee

[X] Select engineer(s) or no engineer required: John Halley Gotway with George McCabe to review.
[X] Select scientist(s) or no scientist required

Labels

[X] Select component(s)
[X] Select priority
[X] Select requestor(s)

Projects and Milestone

[X] Review projects and select relevant Repository and Organization ones
[X] Select milestone

Define Related Issue(s)
Consider the impact to the other METplus components.

[X] METplus, MET, METdb, METviewer, METexpress, METcalcpy, METplotpy
No impacts.

Enhancement Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above.
[ ] Fork this repository or create a branch of develop.
Branch name:  feature_<Issue Number>_<Description>
[ ] Complete the development and test your changes.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Close this issue.

The usage statement for tc_gen to indicate that -genesis and -track can be set to file_lists:
Usage: tc_gen
	-genesis path
	-track path
	-config file
	[-out base]
	[-log file]
	[-v level]

	where	"-genesis path" is one or more ATCF genesis files, an ASCII file list containing them, or a top-level directory with files matching the regular expression "atcf_gen" (required).
		"-track path" is one or more ATCF track files, an ASCII file list containing them, or a top-level directory with files matching the regular expression ".dat" for the verifying BEST and operational tracks (required).
		"-config file" is used once to specify the TCGenConfig file containing the desired configuration settings (required).
		"-out base" overrides the default output file base (./tc_gen) (optional).
		"-log file" outputs log messages to the specified file (optional).
		"-v level" overrides the default level of logging (2) (optional).


package updates and making it compatible with codesandbox.io

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   70.86%   70.86%
=======================================
  Files           6        6
  Lines         127      127
  Branches       17       17
=======================================
  Hits           90       90
  Misses         34       34
  Partials        3        3

Impacted Files
Coverage Δ

src/Rule.jsx
100% <ø> (ø)

src/controls/ValueEditor.jsx
100% <ø> (ø)

src/QueryBuilder.jsx
46.37% <ø> (ø)

src/controls/ValueSelector.jsx
100% <ø> (ø)

src/RuleGroup.jsx
100% <ø> (ø)

src/controls/ActionElement.jsx
100% <ø> (ø)

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 130607c...3a4a743. Read the comment docs.


Zoom out the camera to fix a log depth bug in ModelExperimental tests

This branch makes a small tweak to one test to ensure it runs even in environments where log depth is disabled. We have internal code where this becomes a problem.
To test this, you need to change Scene.js line 214 so that this._logDepthBuffer = false, not context.fragmentDepth. This will cause the test to fail because the camera zooms in so far it begins to clip:
@sanjeetsuhag could you review?

Thanks for the pull request @ptrgags!

: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.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

For more background, this isn't really a log depth bug, rather when log depth is enabled it uses a 0.1 meter near plane and when disabled it uses a 1 meter near plane. The test was zooming close enough to the model that it started to clip through the near plane and not pick the model when log depth was disabled.


sync to live

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/windows-iotcore-docs, working directory: W:\lrrt-s, target branch: live, target branch commit: c82efa041fcb67bdc03d0da4e67a43fd8392fcf1, source branch: master, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/TOC.md
:white_check_mark:Succeeded

windows-iotcore/Troubleshooting.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Change link to band website to open new tab

I was watching the Rough Francis video and clicked on the "Band Website" link and had the stream interrupted. We were already doing it for the social stuff but I guess I missed adding it to the band's website.
Also congrats on the new gig! It's a fun one!

Great catch. Thanks, Matt!


sap.ui.table.Table: visibleRowCountMode:Auto and variable row heights causes scrollbar to get clipped

OpenUI5 version: latest
Browser/version (+device/version): All common browsers, latest versions
Any other tested browsers/devices(OK/FAIL):
URL (minimal example if possible): http://jsbin.com/mocuke/2/edit?html,css,output
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:
1.Use scrollbar to scroll all the way down through the list.
2.Note that about 1/2 of the scrollbar gets clipped at the bottom, and the remaining rows are not scrolled into view.
What is the expected result? Expected that the scrollbar would be scaled appropriately and not get clipped.
What happens instead? The scrollbar changes height during the scrolling and doesn't seem to account for the variable row heights.
Any other information? (attach screenshot if possible)

Hello cmastandrea,
i added another internal ticket for this issue:<PHONE_NUMBER>
We will take a look at this issue and get back to you here.
Thanks for reporting all these issues to us, that's great!
Kind Regards,
Michael

Hi cmastandrea,
unfortunately we can't provide a fix here due to how the table is designed to work, let me try to give some details:
The tables of the sap.ui.table library aim for huge amount of data (i.e. lots of rows). Since it would break the performance to have own controls for each row, the table simply reuses the controls of the rows. It's just the context which is changed by scrolling. Since there is no real scroll area, the table can just only take the length of the binding, the number of visible rows of the table and the current height of the table (influenced by the controls of the row template and their current content) and calculate a scrollbar length which gets applied. This happens in a delayedCall of 250ms - therefore it can happen in unlucky circumstances that the scrollbar length is not set correctly. However, when the row height remains stable, this delayedCall gives a real performance boost. Maybe you've noticed that the table never clips a row, it always shows the complete control - this exactly due to the concept of reusing controls.
I understand that you dislike the current behavior of changing table height, scrollbar length and sometimes not reaching the last row of the table (caused by different row heights). Hence I'd propose to use the sap.m.Table for variable row heights. The sap.m.Table could be placed inside a scroll container with a fixed height. However, the sap.m.Table is not meant for mass-data since it would render the complete data as a table. You can reduce the margins of the controls inside the sap.m.Table by setting the style class sapUiSizeCompact to make the m.Table better fit on desktops.
Best regards
Sebastian


✨ [REQUEST] planka kanban board

Checked

[X] If a new addon, I have checked on  Google that such as addon doesn't already exists
[X] If a new feature, I have searched in the discussions & issues that it was not already covered

Which addon?
planka
https://planka.app/
Is your feature request related to a problem? Please describe
no, more a small wish :)
Describe the solution you'd like
a package from: https://raw.githubusercontent.com/plankanban/planka/master/docker-compose.yml

Since the new todo possibilities in home assistant this is not needed anymore


Deprecate experimental preprocess mode

We had this preprocess mode for a while which has been replaced by our ISTF/Sweetsour effort. The old approach was deeply flawed and is borderline unusable.
I still see people from time to time who are switching it on, believing that it would work as intended.
This task involves the deprecation (and future removal potentially) of this mode, so that we can delete its bundles.
The tasks under this umbrella issue are:

[ ] Deprecate preprocess bundle (add warning)
[ ] Remove preprocess bundle (in a future major, separate PR)
[ ] Remove preprocess code and flag from babel plugin

@kitten Can I work on this one?

Yes please!

@Samatar26 Absolutely! And please let me know if you need any help 🙌

@kitten Hi ~ I'm very curious about the progress of the ISTF since I read the article you wrote. Could you mind to open a issue to introduce the great works you have done ?
It's amazing 😍 and I'm waiting for the appearance of the implementation, but I can't know any state changes about it, so sad 🙈. I'll appreciate that if you can introduce more progress about the ISTF, thx ~

@chengjianhua hiya :) the latest progress can be seen on the Sweetsour repo. https://github.com/kitten/sweetsour
I’m mindful of posting any kind of timeline as I don’t have time to work on it continuously. That being said the parser itself is pretty much done and the next idea on how to proceed might be #1617

@kitten Was surfing the issues and saw this. I know @Samatar26 is working on it, but was just wondering if this block is what you're talking about:
https://github.com/styled-components/styled-components/blob/75502fbf1f1fb413eeafd3f9f4cadfe06f646df6/sandbox/server/webpack.config.js#L33

@rodocite no, specifically what we're referring to is:

https://github.com/styled-components/styled-components/tree/master/no-parser
https://github.com/styled-components/styled-components/tree/master/src/no-parser
https://github.com/styled-components/styled-components/blob/master/rollup.config.js#L149-L162
https://github.com/styled-components/babel-plugin-styled-components/tree/master/src/css
https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/visitors/noParserImport.js
https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/visitors/templateLiterals/preprocess.js
https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/utils/options.js#L9
https://www.styled-components.com/docs/tooling#preprocessing

The deprecation warning is in place, so we'd only need someone to jump onto updating the babel plugin now :+1:

@kitten working on it :+1:

It's dead and deleted


move Rule* tests into separate testsuite

we should move all RuleTests* within https://github.com/staabm/phpstan-dba/tree/main/tests/default (and their corresponding Fixture/data/config) into a new main/tests/rules/  test-suite.
this would help separating the different phpstan-dba feature and therefore ease finishing https://github.com/staabm/phpstan-dba/pull/261

on it


[PHPCS parser] fix invalid classname error

[x] Fixes errors in parser
[x] add unit tests (!)
[x] implement line

@Maffooch could you take a look at it?


Added Footer Section  with Social Icons

This pull request introduces a new footer section with social icons to improve the website's layout and user experience.
Changes made:

Added footer section: A responsive layout using grid structure.
Social icons added: WhatsApp, Discord, and LinkedIn with proper hover animations.

Screenshots :

Kindly resolve the merge conflicts, and I'll merge it.

Could you please add the gssoc-ext and Hacktoberfest labels to this pull request


Cluster topology submission bug fixes and swappable class loader policy support.

Added swappable class loader policy selection to topology submission form
Added configurable selection of log level to topology submission form
Added momentjs date support to UI elements
Added historic log search in cluster log search
Added topology kill dialog with wait time in seconds similar to native Storm UI
Added more streamflow namespaced properties for injection in spouts and bolts
Fixed numerous bugs

Looks good to me.


+process_task_trigger_queue, process_task_service

Lambda + container function is in process_task_service.

Ugly problem #1: Deployment depends on digest that comes after docker push. This means every time we push, we have to manually copy and paste the digest into serverless.yml.
Ugly problem #2: Lambda VM prevents container runtime from writing to working directory, possibly due to Lambda limitation of "must write to /tmp". Lambda should treat containers as stand alone without conventional Lambda restrcctions.

Plus additional changes from Tianxiang in cachefile.py.
Check if upload file exists.
Use None in optional parameters.


Geimaj/pending transactions UI

looks good! will review properly once conflicts are fixed and ui/pendingTransactions are properly integrated into modal, but should be good to merge then.

looks good! will review properly once conflicts are fixed and ui/pendingTransactions are properly integrated into modal, but should be good to merge then.


icons go down

hey. seems like the generetor load files or icons 2 or 3 times and all the icons in my project go down a little bit, some one know this problem?
thanks

@alexp193 can you create minimum reproducible test repo, also i think we should rewrite this plugin to loader, it should be faster and cachable

i think the plugin just add more height to icons and they turn down.. you have any idia why its happaning ?
and what is it test repo and how i can reproducible this test?

@alexp193 Maybe this option solve you problem https://github.com/itgalaxy/webfont#centerhorizontally https://github.com/nfroidure/svgicons2svgfont#optionscenterhorizontally

i dont know whare find it...


KeyError when using QueryType.SEMANTIC in search_client.search()

I am writing to report an issue I encountered while running "chat-read-retrieve-read.ipynb" in VS notebook. When calling the search_client.search() function with QueryType.SEMANTIC, I receive a KeyError: 'SEMANTIC'. I suspect that the issue might be related to the enumeration class QueryType not having the 'SEMANTIC' member, or there is an issue with the case-insensitivity of the enumeration member lookup.
Here is the code snippet where I call the search_client.search() function:
search_client.search(search,
filter=filter,
query_type=QueryType.SEMANTIC,
query_language="en-us",
query_speller="lexicon",
semantic_configuration_name="default",
top=3)
The error message I receive is:
KeyError: 'SEMANTIC'
I would appreciate it if you could help me understand the cause of this error and how to resolve it. If the issue is related to the absence of the 'SEMANTIC' member in the QueryType enumeration class, please let me know the correct member name to use. If there is an issue with the enumeration member lookup, I would appreciate any guidance on how to address it.
Please let me know if you need any additional information to diagnose and resolve this issue.
Thank you for your assistance.
Minimal steps to reproduce

run "chat-read-retrieve-read.ipynb" in VS notebook

OS and Version?

Windows 11

Versions

Python 3.9.2

I have the same issue

Nevermind, mine is working now, you just have to install the beta.
You can do that by entering this in your terminal:
"pip install azure-search-documents==11.4.0b3"
if you are using anaconda you have to do the same thing, anaconda doesn't have the right version yet.
The solution i found


Feedback

Glad to see you developing this! It works when I run it- nice job.
My main question- are the input files intended to be like .Rmd- ie. mostly text and math with some blocks of code, or should they remain executable as scripts?
Here are some things to think about:
Consider using the argparse module from the standard library if you'd like to be able to extend this with more flags, etc.
In validation you could go ahead and raise ValueError.
Use 4 spaces for indents- see pep8.
I like how you're building the regexes programmatically.
People will know you're more serious about this if you write a test suite. This is easier the sooner you do it.
The operation below would commonly be done using the with statement (a context manager which can handle exceptions):
infile = open(input_file_name, "r")
script = infile.read()
infile.close()

becomes
with open(input_file_name, "r") as infile:
    script = infile.read()

All you need to do is switch to the print function and you'll have Python 3 compatibility:
clarks-MacBook ~/junkyard/txt2pynb $ 2to3 txt2pynb.py
RefactoringTool: Skipping implicit fixer: buffer
RefactoringTool: Skipping implicit fixer: idioms
RefactoringTool: Skipping implicit fixer: set_literal
RefactoringTool: Skipping implicit fixer: ws_comma
RefactoringTool: Refactored txt2pynb.py
--- txt2pynb.py (original)
+++ txt2pynb.py (refactored)
@@ -36,7 +36,7 @@
                        if re.search(md_start, line) != None:
                                mdFlag = True
        if codeFlag or mdFlag:
-               print 'ERROR: Code or md tags not closed in script'
+               print('ERROR: Code or md tags not closed in script')
        return order;

 def content_strip(line, output_file):
RefactoringTool: Files that need to be modified:
RefactoringTool: txt2pynb.py

Thanks for the feedback!! I am very new to python, so this feedback is extremely helpful.
The idea was to have the input python script remain executable, hence all markdown blocks are commented out. That way a single script can be used to make a notebook for a talk or run batches on a server.
I'm glad you brought up validation, I'd like to add some error messages and other things as well. That will be coming soon.
Thanks again!

Cool. Was thinking a bit more about it - you probably want to use the json module from std. library as well.


Document temp_field_data props

Might be useful to document somewhere what these three values mean. The field_data structure seems pretty important for our testing framework, so it would be good to have documentation about what it should contain.
Originally posted by @niharikasingh in https://github.com/plocket/docassemble-cucumber/pull/192#discussion_r607093192

These are actually the temp_field_data props I think. They're not the final field_data props. Still, they should be documented a bit better.