Change all Proof-of-Work references to Proof-of-Wow

In order to signal our support for Elon and join the fight against wasteful energy consumption, this PR changes all references to dirty proof--of-work to "proof-of-wow"

In order to signal our support for Elon and join the fight against wasteful energy consumption, this PR changes all references to dirty proof--of-work to "proof-of-wow"

Allow me to elaborate.  Similar to when GOdDARD created the original vision for rockets, and the majority of Americans were still anti-science clowns laughed at him, until he won the war against the Nazis and shipped the first multistage, liquid fueled rocket.
Egod, I mean Doge, is the first energy efficient and fast implantation of a decentralized currency. Until a solid proof of stake, non-centralized system, is in production, fully vetted, and fully tested — we are sticking with rocket-bound pups.
If you have nothing to add, but clown behavior, then maybe fork this and ship your own rockets. But if you’re just adding more wasteful entropy to the universe, please do it somewhere with less value before presenting it as something good. Good is the key.
thank you,
The light 💡

Very science wow. Much approval

I would sugget "Proof-of-Woof" instead!

I would sugget "Proof-of-Woof" instead!

Much approve.

Also don't do just replace "work" by "wow" but:
proof-of-work => proof-of-woof
proof of work => proof of woof
proofofwork => proofofwoof

i prefer Proof-of-Power

i am going to get this to run successfully even if I have to sell my hodl to pay the bills in the meantime

success.
now running dogecoind with proof-of-wow

PoWoof

why would anyone approve these changes?  you are all over the place when naming variables, some uppercase some lowercase... set a standard and stick to it.. Id delete this PR and start over.

NACK. This makes it harder to port changes upstream from Bitcoin's code base.

well we can't use bitcoin's code base anymore because Elon is depending on doge core devs to remove wasteful energy use and PoW. did y'all not get the check in the mail? https://twitter.com/elonmusk/status/1392974251011895300

why would anyone approve these changes? you are all over the place when naming variables, some uppercase some lowercase... set a standard and stick to it.. Id delete this PR and start over.

upper/lower is the same as before. maybe 1 or 2 accidental changes.

@willwooten

well we can't use bitcoin's code base anymore

You'd have to throw away pretty much all of Dogecoin then because Dogecoin is 90+% Bitcoin's and Litecoin's code.  And what do you propose as an alternative that doesn't involve massively changing the architecture of the project?

renaming variables doesnt change the functionality of them.. this is still POW youre just trying to be clever and name it something else, like calling an apple and orange instead.

Updated upper/lowercases as requested

You'd have to throw away pretty much all of Dogecoin then because Dogecoin is 90+% Bitcoin's and Litecoin's code. And what do you propose as an alternative that doesn't involve massively changing the architecture of the project?

i was unaware of this thank you.
Proof-of-Wow isn't Proof-of-Work. That is the proposal.

Changed all references to Proof-of-Woof

This change it is one of the best actions I've ever seen to fight climate change, please merge this PR as soon as possible!

Where are the unit tests that prove you are saving the world?

Where are the unit tests that prove you are saving the world?

we'd need an oracle to input global temperature data

If you guys care about Doge, you sure are making it look extremely bad.  If you dont know how to develop, or how to create proper pull requests, all you are doing is hurting the project ;)   Once again, renaming variables DOES NOT change the way this functions.. its STILL PROOF OF WORK.   so unless you want to show Elon what type of folks are trying to update this, you are much better off deleting this PR and actually implement this into PoS or a brand new type of blockchain that doesnt require energy consumption like PoW.  If the Dev behind this github account merged this into MAIN..  id consider this project beyond dead than as this is not one step forward to help make Doge more energy efficient, but steps backwards.

If you guys care about Doge, you sure are making it look extremely bad

Proof-of-Woof is funny tho

@willwooten

well we can't use bitcoin's code base anymore

You'd have to throw away pretty much all of Dogecoin then because Dogecoin is 90+% Bitcoin's and Litecoin's code. And what do you propose as an alternative that doesn't involve massively changing the architecture of the project?

take a bunch from qtum, a utxo chain (a lot of Bitcoin code) with added PoS, an account attraction layer and an evm compatible vm. no clue how difficult or even if possible but much wow if it were

I only read the title, but LGTM!

I understand your dedication and that youve invested many hours trying to help out, but the thing is just to rename some variable, and create a whole new concept with absolutely no backing to how it will be any different proof-of-concept, doesnt help this project at all.  You have 18 different commits.. when honestly this should be 1 commit - and it should have taken you less than 5 minutes to implement with a simple sed -i 's/change/changeto/' /dogecoin/*  thus it shows you are way over your head and understand this is constructive criticism and if you really cared about this project you would delete this pull request and take a step away from github but still give support.

this is hilarious

sigh...i have failed to pass the checks.
good times were had though.
anyone that takes doge seriously, lol.

ACK, with this new variable name Doge will finally become the store of value, medium of exchange AND unit of account that the world both needs and deserves. Thank you for your contribution @willwooten, much applause. I look forward to your future variables renamings.

Not to disrespect, I do understand doge attracts mass users, but other than enthusiastic about holding doge for investment, this place should be given non-joke but only full serious development-oriented attention. Things running behind to serve those DeFi, and this wallet have much greater things to be concerned about regarding to performance, security, etc to name a few. If majority of developers enjoy joking and sending funny PRs (even enjoy approving it) then the moment of rugpulls, or security hole we all saw in those DeFi space could creep in to this project.
I believe it's better for the project's outlook and to continue attracting new well-intended contributors by keeping your enthusiastic elsewhere outside of this project. With all due respect.

it's extremely sad that devs in here take doge seriously and think my search and replace all was a serious attempt at devolopment. jfc.
the code should be absurd as possible, regardless if it makes it hard to copy bitcoin's updates. unless the maintainers actually do something doge will be taken by musk et al and made a corporate toy.
that news story came out that "the devs" aka the 4 maintainers of this github were in contact with Elon since 2019. Great chance to fill your bags knowing a billionaire would start pumping them.

There's been too much going on like this it's impossible to discern satire anymore.

isn't doge satire itself?

There's been too much going on like this it's impossible to discern satire anymore.

isn't doge satire itself?

You're probably right, because I was laughing all the way to the bank! 💲💲💲

You're probably right, because I was laughing all the way to the bank! heavy_dollar_signheavy_dollar_signheavy_dollar_sign

congrats dumping a copy pasta of bitcoin on teenagers

This is just beautiful. Entertainment of highest caliber, just like this coin.
Thanks for the laughs.

I have invented a consensus tx approval mechanism inspired by your proof of work and xrp validator system.  Doge 2.0 rough copy lol


Domain range of ContinuousPiecewiseLinearFunction

Currently, the ContinuousPieceWiseLinearFunction limits domain values to the interval [0.0, 1.0]. This is well suited for catching errors in the original use of these functions (offset-functions for Arc, Bezier, and other Curves that are generated as a function of a t-value that runs from 0.0 to 1.0).
Other than that particular use, I see no reason for limiting the domain to [0.0, 1.0]. In fact, the entire range covered by double could be permitted (except for NaN, and infinity values).
As these functions will be enhanced with various operators (plus, minus, times, etc.), shall we drop the domain range restriction?
The only immediate problem would be the proposed reverse operator. This can easily be handled by a way more general operation that does any linear remapping of the domain. The proposed reverse operation could than be written as remapDomain(from, to, scale) with parameters 0, 1, -1.
N.B. the reason for ruling out infinity values is that interpolating between a finite domain value and an infinite domain value would be problematic.

@WJSchakel : what are your thoughts on this?

I agree with dropping the limitation. There is one other use-case that will change. Currently the idea of the sub(double, double) method is to rescale that to the [0...1] domain. That would then need to become a chained call: sub(from, to).remapDomain(from, to, 1.0 / (to - from)). We might opt to instead provide a normalizeDomain(from, to) which does exactly that.

Limitation dropped.


undefined type forgotten in types.js

First thanks a lot for your wonderful type script !!!
I used it in Blockly@rduino and it works fine.
But in 'types.js', line 168 I added a code for testing if nextblock.connection is null
Blockly.Types.getChildBlockType = function(block) {
  var blockType = null;
  var nextBlock = block;
  // Only checks first input block, so it decides the type. Incoherences amongst
  // multiple inputs dealt at a per-block level with their own block warnings
  while (nextBlock && (nextBlock.getBlockType === undefined) &&
         (nextBlock.inputList.length > 0) && (nextBlock.inputList[0].connection != null)) {
    nextBlock = nextBlock.inputList[0].connection.targetBlock();
  }

I d'ont know if you prefer...

Thanks a lot for the additional check!
I will be unavailable for a few weeks from tomorrow and wouldn't want to rush it, but I'll definitely have a proper look at this one once I'm back.


Master

Added the solution and approach as a documentation
format for easy understanding

Added the solution and approach as a documentation
format for easy understanding


Add Skeletal PPP

Create skeletal version of individual Project Portfolio Page
Details

Just headings enough for now

Notes

Follow details in CS2103T website

Completed


tukan/cicada (no expansion delay / animation / nv.d3.css) fixes

no expansion delay / animation  -> https://github.com/opnsense/core/issues/2554
nv.d3.css fixes
other small fixes

Good morning. Ready for pull or wait? :)

https://forum.opnsense.org/index.php?topic=9825.0

if it is this problem then it is a common problem. does he mean that? https://github.com/opnsense/core/issues/2747

It's fine with the default theme, only appears with our themes.

@fichtner please wait with the pull.
@marjohn56 Screenshot?

And it's there with any number of columns. This is mine with 3 columns.

@fichtner  - I seem to be making a habit of throwing in spanners at the last minute. 🤔

I'll fix the firewall widget tomorrow. I think this is a core issue with the widget structure itself.

Merged, thanks!

Okey dokey. I'll go and update rebellion  to match René's changes.

@marjohn56 you're right.
But it's kinda weird because you've taken over the css code from opnsense theme 1: 1.
the problem should not occur with you, too
@fichtner in the production environment, the problem really only occurs in our(dark, cicada, tukan) themes. in the development environment for all themes (also opnsense). strange

prod: (opnsense theme)

development: (opnsense theme)

@fichtner thx for mergin!

@marjohn56 you're right.
But it's kinda weird because you've taken over the css code from opnsense theme 1: 1.
the problem should not occur with you, too
@fichtner in the production environment, the problem really only occurs in our(dark, cicada, tukan) themes. in the development environment for all themes (also opnsense). strange

perhaps it's the way the widget is pulling in the other themes.

@opnsenseuser  - As you say, Rebellion is basically Opnsense theme with colour changes, so it's a little odd. I'll wait on any changes to Rebellion until they've worked their way into the default theme.

I'll fix the widget. All other widgets are fine so I blame that one. ;)


Code snippet widget disappears

1.0.0 rc0

Create and save a code snippet
Click "Delete the code snippet" icon
Click CANCEL (aka don't delete code snippet) - the widget listing code snippets disappears

I had to restart JL to get the widget back

This looks like its caused by some awkward promise handling. That is our delete dialog doesn't send the server request to delete on CANCEL, but it still runs the client side update that removes the associated code mirror "editor"

lgtm in 1.0.0 rc1


traffic distribution: move to API repo

Also, the chart accidentally made it a label -- its an annotation,
though.
Fails until https://github.com/istio/api/pull/3328

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test gencheck

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

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test gencheck

unit-tests-arm64_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test unit-tests-arm64

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

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

Test name
Commit
Details
Required
Rerun command

gencheck_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test gencheck

unit-tests-arm64_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test unit-tests-arm64

unit-tests_istio
b75bbdfee330f6cca903be20fbce766c33895e9d
link
true
/test unit-tests

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

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.


Chip longClick, doubleClick

WHAT
Support for more click events types
WHY
https://github.com/google/horologist/issues/1822#issuecomment-1894417911
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

@garanj any advice on how to implement it without two a11y nodes?


Add 'extend' capability for tasks

Features Description
Add a new 'extend' attribute for tasks to enable it to extend any other task.
This will enable to create a 'template' task from which actual implementations with few changes extend from.

#201

You'll want to document that an explicit private = false is necessary in this situation:
[config.modify_core_tasks]
private = true
namespace = "default"

[tasks.kcov]
extend="default::coverage-kcov"
private = false

If someone's used to thinking in terms of object-oriented programming, it probably won't occur to them that you can change something's public/private status when extending it, they'll run into this error, and then mistakenly conclude that it's impossible:
[cargo-make] INFO - Using Build File: Makefile.toml
[cargo-make] INFO - Task: kcov
[cargo-make] INFO - Profile: development
[cargo-make] ERROR - Task kcov is private
[cargo-make] WARN - Build Failed.

I was actually caught by that assumption for a moment.

I'll add this to the docs.


FancyZones margin

Description of the new feature / enhancement
FancyZone uses finite margin around panes. This should be able to change to zero so that users can use full area of the display.
Scenario when this would be used?
It is used when the windows are aligned on.
Supporting information
No response

Hi @MasaYan24, is disabling the space around zones not what you need?

@dedavis6797
Thanks for your reply.
Yes, that's what I wanted! Thank you!
Closing this issue.


Switch to new syntax for union types

Apollon requires Python >= 3.10. So, rewrite all union types that include None with the new union operator |. Types of the form Union[T, None] should become T | None.

Fixed in 5202e96f85f1d1ecee2f66d4cc1dd603cd808ccd


bug: Cant change tint of a image in dynamic

What's happening?
When I change the tint color for the active tab, it remains the same as the initial color that was set.
Reproduceable Code
<TurboImage
              source={{ uri: 'https://i.ibb.co/qsghqnX/addPost.png' }}
              style={{ width: size, height: size }}
              tint={focused ? COLOR.PRIMARY : COLOR.BLACK}
              resizeMode="contain"
            />

Relevant log output
nothing

Device
iPhone xs
TurboImage Version
1.17.1
Can you reproduce this issue in the TurboImage Example app?
No, I cannot reproduce the issue in the Example app

Thanks for raising this issue. I did a test, seems it only happens on iOS.  I will create a new version with the fix.
https://github.com/user-attachments/assets/2db3db44-28c6-46e4-b6a0-88fa87c83b93
    <View style={styles.container}>
      <Card
        source={{
          uri: 'https://placedog.net/300/300?id=121',
        }}
        style={styles.image}
        cachePolicy="dataCache"
        onStart={handleStart}
        onSuccess={handleSuccess}
        onCompletion={handleCompletion}
        tint={tint ? 'red' : 'black'}
        placeholder={{
          blurhash: 'UBIr4u9}00Rj?yEzxu%LIQ%1%6xt-ks,tAIU',
        }}
      />

      {start && <Text>Start at {Date()}</Text>}
      {information?.width && <Text>width: {information?.width}</Text>}
      {information?.height && <Text>height: {information?.height}</Text>}
      {information?.source && <Text>source: {information?.source}</Text>}
      {completion && <Text>Complete at {Date()}</Text>}
      <TouchableOpacity onPress={() => setTint(!tint)}>
        <Text style={{ fontSize: 32 }}>Change Tint Color</Text>
      </TouchableOpacity>
    </View>

dynamic tint color in iOS
https://github.com/user-attachments/assets/10155751-a957-4ee6-b909-fbdcfd06c781

Let me know if you still have this issue with v1.17.2 😃


When the menu is selected in the side menu bar, the order of menu options changes and flashes

In the next release, we will remove this plug-in request.

In the next release, we will remove this plug-in request.


Missing icon in Material Symbols

Describe the bug
The icon trophy is not working with the material-symbols fonts (with any version: normal, variable, rounded...).
Using google font it works. I found this issue, maybe the fontsource version is not updated? https://github.com/google/material-design-icons/issues/1514
Steps to Reproduce

    <link<EMAIL_ADDRESS>rel="stylesheet" />

    check
    trophy

This code doesn't render the trophy icon (the check icon works):

Expected behavior
Replace with the google font:
<link href="https://fonts.googleapis.com/css2?family=Material+Symbols+Rounded" rel="stylesheet" />
The expected result is:

Version
5.0.16
OS
macos 14, windows 11
Browser
safari, edge, chrome
Additional context
No response

can i work on this issue please

can i work on this issue please

Sure! The first thing I recommend is to check the source metadata we generate via google-font-metadata. We automatically update icons with a script so if our version differs from what Google’s APIs are serving, maybe something is wrong with our script.

package_2 symbol is bad also

I think #902 has fixed this. Can anyone confirm? This may have just been an issue with our website rather than the NPM package itself.

With material-symbols-outlined is ok for trophy and package_2 symbols
Thanks a lot


[BUG]  Bicep Azure Spring Cloud Bicep error:  Java 17 not supported for type Jar

Describe the bug
When attempting to execute an Azure Spring Cloud Bicep template, the following error message is generated and information about the deployment is not written to the console:
{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"DeploymentFailed\",\r\n        \"message\": \"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.\",\r\n        \"details\": [\r\n          {\r\n            \"code\": \"BadRequest\",\r\n            \"message\": \"{\\r\\n  \\\"error\\\": {\\r\\n    \\\"code\\\": \\\"BadArgument\\\",\\r\\n    \\\"message\\\": \\\"Invalid arguments: properties.source.runtimeVersion with value Java_17 is not supported for type Jar\\\",\\r\\n    \\\"target\\\": null,\\r\\n    \\\"details\\\": [\\r\\n      {\\r\\n        \\\"code\\\": \\\"BadArgument\\\",\\r\\n        \\\"message\\\": \\\"properties.source.runtimeVersion with value Java_17 is not supported for type Jar\\\",\\r\\n        \\\"target\\\": \\\"properties.source.runtimeVersion\\\",\\r\\n        \\\"details\\\": null\\r\\n      }\\r\\n    ]\\r\\n  }\\r\\n}\"\r\n          }\r\n        ]\r\n      }\r\n    ]\r\n  }\r\n}"}]}}

Also seeing the message in the output immediately after the command is issued:
C:\Code\myproj\bicep\modules\spring-cloud\spring-cloud.bicep(65,23) : Warning BCP036: The property "runtimeVersion" expected a value of type "'Java_11' | 'Java_8' | 'NetCore_31' | null" but the provided value is of type "'Java_17  '". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
C:\Code\myproj\bicep\modules\application-insights\app-insights.bicep(29,21) : Warning BCP036: The property "Application_Type" expected a value of type "'other' | 'web'" but the provided value is of type "'java'". If this is an inaccuracy in the documentation, please report it to the Bicep Team. [https://aka.ms/bicep-type-issues]
I'm not sure if this is an issue with NubesGen, Bicep, or Azure Spring Cloud.  I've previously created an Azure Spring Cloud instance with Java 17 by hand, but this is my first time to create it with Bicep.
To Reproduce
Steps to reproduce the behavior:
On nubesgen.com:

Specify Bicep template
Select Application Type: Spring Boot Application
Select App size: Basic
Select Database: Azure SQL Database / Serverless
Check Application Insights
Download the Bicep templates
run the command

az deployment sub create --name 'demo{environment}' --location eastus --template-file main.bicep

Expected behavior
Information about the deployment should be generated
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: 'nubesgen-version': '0.11.4'

Additional context
if Java_17 is changed to Java_11 in spring-cloud.bicep the deployment information is successfully generated

Noticed my local Bicep installation needs to be upgraded.  Will upgrade and follow up.

Issue still happens after upgrading bicep locally.

Hi @jimbethancourt,
Thanks for reporting that issue.
I'll have a look at it.

There is a discrepancy between the bicep documentation and how the portal create things.


NodeJS: Pnpm can not install oxc-parser on Linux images

While the root cause users may encounter already has an open PR: https://github.com/pnpm/pnpm/pull/8431
It might be good to know that the distributed oxc-parser node binding may cause issues for machines using Linux and pnpm together. The optional package @oxc-parser/binding-win32-arm64-msvc has its libc property set to null, and that causes installation through pnpm to fail.
This is @oxc-parser/binding-win32-arm64-msvc package.json:
{
  "name": "@oxc-parser/binding-win32-arm64-msvc",
  "version": "0.24.2",
  "main": "parser.win32-arm64-msvc.node",
  "license": "MIT",
  "author": "Boshen and oxc contributors",
  "bugs": "https://github.com/oxc-project/oxc/issues",
  "homepage": "https://oxc.rs",
  "repository": {
    "type": "git",
    "url": "https://github.com/oxc-project/oxc.git",
    "directory": "npm/oxc-parser"
  },
  "files": [
    "parser.win32-arm64-msvc.node"
  ],
  "cpu": [
    "arm64"
  ],
  "os": [
    "win32"
  ],
  "libc": [
    null
  ]
}

I don't think you guys need to update anything, potentially not including platform properties if they're set to null. I'm hopeful my pnpm PR will be merge and fix the code that causing the expiation. More can be read in the PR: https://github.com/pnpm/pnpm/pull/8431
But FYI that setting the libc property to null causes issues, apparently.

This like a bug on our end setting libc to null.

The latest version no longer has null in the libc field https://www.npmjs.com/package/@oxc-parser/binding-win32-arm64-msvc/v/0.25.0?activeTab=code


Make "species" a required/defining key for footprints

What is your issue?
For species with short lifetimes, footprints need to take into account the lifetime of the substance.
Currently, "short_lifetime" has Boolean values, and is automatically set to True only for Radon. Any time a species is passed when standardising a footprint, we should look up the lifetime of that species, and if it is short, regard that footprint as short lifetime.
We need to decide on what "short" means, and also whether we want to record the lifetime in the metadata, since this could be looked up based on the species.
If a species isn't short lifetime, we record its species as "inert"; if species is passed as an argument to standardise_footprints and the species is inert, we will warn the user.

We need to decide on what "short" means, and also whether we want to record the lifetime in the metadata, since this could be looked up based on the species.

So "short" as a first check would be <30 days. This is the species_info.json file I keep referencing. You'll tend to find that the lifetime won't be listed unless it's short-lived. Still worth knowing what short means though as you say.
The function I was talking about which can extract the lifetime is openghg.util.species_lifetime.


Why did you remove auxiliaryCommentBefore?

Just that. Because of that, for every class I test, I have to do this in order to fix the coverage:
expect(() => MyClass()).toThrow('Cannot call a class as a function');

Thanks.

cc @kittens ?


feature tests for parsing special characters

this commit has two failing tests because of the spaces
mixed in with the special characters.  if the spaces are removed
then the tests pass
failing tests

exec - brackets should be retained in the test
exec - special characters should be retained

related to #59

this can be closed if we merge https://github.com/bilal-fazlani/commanddotnet/pull/141

obsolete


Accuracy of data with 'fog' labels.

My supervisor and I have been trying to work with the ZOD dataset for the purpose of weather detection. We were using the RGB data, and as labels we had decided to use the 'scraped-weather' parameter from the meta data json file, because it has values such as 'clear', 'rain', 'snow' etc, which can be used as class labels. One of the class labels is 'fog', however it is not clear as to how they are classified, because they easily come under some of the other labels such as 'cloudy', 'rain' and 'snow'. There is no clear indication of fog, at least in RGB.

Hi.
As (somewhat) indicated by the name of the field, the data is scraped from online resources in post-processing. This unfortunately leads to metadata that is not correct. This is a limitation but I hope that you can still make use of the dataset.
However, if you are able to more accurately classify the weather of each frame (including fog etc.,), we would very much like to add it to the dataset. If you do so, please contact us either here or at<EMAIL_ADDRESS>


fix: add SohamRatnaparkhi

resolve #1117
Checklist for profile addition

[x] Name the PR fix: add <your-username>.
[x] You've added file named your-username.json in the profiles directory.
[x] You've linked the PR to the correct issue.

This PR adds/fixes
This PR involves the addition of my profile to awesome profiles.

Hi Devs,
Prettier / Prettier Linting check failed for this PR so, how can I pass the check.
Thank you!
__
  Summary: :question: I have a question

Add an end line. I had encountered the same problem.
- }
+ }
+

Add an end line. I had encountered the same problem.
- }
+ }
+

Thank you! I made committed the changes in my latest commit.
I am new to open-source. Can you tell me what should I do after adding the line and making a commit? Do I have to make new PR or anything of that sort?
Thank you!
__
  Summary: :question: I have a question

Thanks for contributing! Looks good to me.

Thank you!
__
  Summary: :ok_hand: This code looks good

No, everything looks good.
Wait for  a member to review it and merge it.

No, everything looks good. Wait for a member to review it and merge it.

Great, Thank you!
__
  Summary: :ok_hand: This code looks good

Hello Devs, any update on this PR?
Thank you!
__
  Summary: :question: I have a question

@Panquesito7 maybe you can help here

Hello Devs,
Can you help me in removing the linting error?
Thankyou!
__
  Summary: :question: I have a question

You can go a head and fetch the latest changes from upstream/main and merge them. After that, commit on this branch and it should go away.
Here is an example on how to update fork. Check it out

You can go a head and fetch the latest changes from upstream/main and merge them. After that, commit on this branch and it should go away. Here is an example on how to update fork. Check it out

Okay thankyou👍
__
  Summary: :ok_hand: This code looks good


Expired user access token error not logged to console

Azure DevOps Extensions
Generate Release Notes (Node Cross Platform)
Platform
Azure DevOps Services
Azure DevOps Server (TFS) Version
No response
Extension Version
No response
Describe the bug
Expired user access token error not logged to console when using test console. Program just exits.
Repo Steps
Use expired user access token in test console.
Expected Behavior
Errors like this are logged.
Logging Information
No response

I have a fix incoming.


Where to get Material ID or Material Info

Hi
As I understand it, we pass the material json file into the audio sensor and it 'assigns' materials according to their semantic labels. I was wondering where I can access the material of any object during runtime. How we have object_id and corresponding semantic_id, how can I have a similar material id or any identification for what material an object is if I read a semantic or RGB image via sensors?

You'll need to build a mapping from objects to materials and then look up materials based on the semantic segmentation results.


Better iPad compatibility

I would like to request a better iPad compatibility.
The "Submit" button should be much more left (se screenshot below). That way you could zoom in and handling would be easier.

@PhilipMay What's wrong with the current Submit position?

Do I understand correctly, you would like to zoom in a bit to see everything bigger, and when you do that, the Submit button goes out of the screen viewport? Thank you for that issue, we're working on the problem.

I was also thinking of a "one click mode" where you do not 1. select the radio button and 2. submit.
What about one single button you can click, then you get a short visual feedback and after 0.5 sec. the formular
gets submitted?

What about one single button you can click, then you get a short visual feedback and after 0.5 sec. the formular
gets submitted?

That's an interesting idea which makes sense in many cases of labeling with choices.

I am trying to load this on my iPad Air 5. My segmentation projects in label studio 1.5.0 simply wont load on either Safari or Chrome on iPad or iPhone, it just shows a resizing box loading animation. Is this supported? I would love to do brush segmentation with the iPad pencil.

Hello, try to use the latest develop branch please.

We fixed problem with Safari, turned out that it doesn't support regexps fully

@makseq same error. I removed all image layers, rebuilt a second time to be sure, cleared my cache, tried desktop and ipad... Safari still giving the same regex error.
Any chance you can provide instructions on running in dev mode without minification and with hot reloading and I can probably fix this myself.

Could you please use the develop image from our dockerhub directly? heartexlabs/label-studio:develop

@makseq are you able point to some instructions where I can start the frontend in dev mode so I can make changes so I can possibly give it a shot myself and then provide a PR?

@madhavajay Sure, you can start from this repo and instuctions: https://github.com/heartexlabs/label-studio-frontend#development -

@makseq I kind of got it working:
https://github.com/heartexlabs/label-studio-frontend/pull/802

@madhavajay Amazing! I've asked our frontend team to review &merge this!

@madhavajay if you could make a PR in the main label-studio repo with LSF builds, it would be great :-)

@makseq should we wait for the frontend pr to be checked and merged first incase it introduces some bugs?

I think you can make a build from the LSF PR without merging it to develop. Does it make sense?

@makseq do you mean create a PR on this repo with the updated files just for people to use but not to merge?

yes!

@madhavajay thanks for your contribution!
@makseq: please ping me when it is ready for tests :)

Any progress on this feature?


Fixed a bug in ipe/websocket.go

TotalConnections were growing infinitely; connection was not closed when a channel listener client refreshed or simply closed the browser tab.

I submit another patch instead of this, because I suspect that the err value there can be io.EOF too, depending on the platform. I'm not sure about this but we're better safe than sorry!


Fix python centos6 distribtest

Heads up: to fix the distribtest I needed to upgrade python to 2.7 and pull in https://centos6.iuscommunity.org/ius-release.rpm
Nevertheless, this makes all python linux distribtests pass.

PASSED: distribtest.python_linux_x64_fedora20 [time=26.5sec; retries=0:0]
PASSED: distribtest.python_linux_x64_wheezy [time=33.4sec; retries=0:0]
PASSED: distribtest.python_linux_x64_jessie [time=34.3sec; retries=0:0]
PASSED: distribtest.python_linux_x64_ubuntu1204 [time=35.4sec; retries=0:0]
PASSED: distribtest.python_linux_x64_opensuse [time=36.9sec; retries=0:0]
PASSED: distribtest.python_linux_x64_fedora22 [time=38.1sec; retries=0:0]
PASSED: distribtest.python_linux_x64_arch [time=38.6sec; retries=0:0]
PASSED: distribtest.python_linux_x64_fedora21 [time=43.3sec; retries=0:0]
PASSED: distribtest.python_linux_x86_jessie [time=45.3sec; retries=0:0]
PASSED: distribtest.python_linux_x64_centos7 [time=46.0sec; retries=0:0]
PASSED: distribtest.python_linux_x64_fedora23 [time=46.4sec; retries=0:0]
PASSED: distribtest.python_linux_x64_centos6 [time=47.1sec; retries=0:0]
PASSED: distribtest.python_linux_x64_ubuntu1404 [time=22.9sec; retries=0:0]
PASSED: distribtest.python_linux_x64_ubuntu1604 [time=22.9sec; retries=0:0]
PASSED: distribtest.python_linux_x64_ubuntu1504 [time=25.4sec; retries=0:0]
PASSED: distribtest.python_linux_x64_ubuntu1510 [time=25.3sec; retries=0:0]
SUCCESS: All targets built successfully.


Does the method to find knowledge aggregation pattern have any relevant papers to reference in NLP domain?

Hello, thank you for your great work!
I'm confused about the knowledge aggregation pattern and anchor token. Does it mean the number of paragraph which contains different meanings in LLM'response ?
As to the example below, the "knowledge aggregation pattern" is 2?
The image features a blue bowl filled with a delicious mixture of bananas, nuts, and oatmeal. The bowl is placed on a dining table, and a spoon is resting inside the bowl, ready to be used for enjoying the meal. In addition to the bowl of food, there are a few other items on the table. A bottle can be seen on the left side of the table, while a cup is positioned towards the top right corner. A book is also present on the right side of the table, adding to the cozy atmosphere of the scene.
Does the method to find "knowledge aggregation pattern" have any relevant papers to reference in NLP domain?
I'm wondering if this method can be transferred to judge Transition in Semantics in LLM's response.
Thank you for your time! And hope for your reply~
(My email is<EMAIL_ADDRESS>

Thanks for your interest! Your questions are quite valuable.
Q1: Does it mean the number of paragraph which contains different meanings in LLM'response ?
A1: No. Anchor token is the nature of LLM, you can find more explanations in [1].
Q2: As to the example below, the "knowledge aggregation pattern" is 2?
A2: No. Sorry I can hardly get what does 2 mean. Could you clarify it more clearly?
Q3: Does the method to find "knowledge aggregation pattern" have any relevant papers to reference in NLP domain?
A3: Yes. Please refer to [1, 2, 3].
Q4: I'm wondering if this method can be transferred to judge Transition in Semantics in LLM's response.
A4: Good point! I think it is a potential direction to figure out how anchor tokens help model preserve the logic in sequence.
[1] Label words are anchors: An information flow perspective for understanding in-context learning
[2] Vision transformers need registers
[3] An Image is Worth 1/2 Tokens After Layer 2: Plug-and-Play Inference Acceleration for Large Vision-Language Models


fix(nix): update path to hydra build for 2.24 and newer

Renovate currently fails to download Nix because the URL for the latest version has been updated.
WARN: Error updating flake.lock (branch="renovate/lock-file-maintenance")
{
  "err": {
    "cmd": "/bin/sh -c install-tool nix 2.24.1",
    "stderr": "",
    "stdout": "installing v2 tool nix v2.24\n[12:53:34.669] INFO (53): Installing tool<EMAIL_ADDRESS>failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist\nDownload failed, retrying\nDownload failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist\nDownload failed, retrying\nDownload failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist\nDownload failed: https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist\n[12:53:37.663] INFO (103): Downloading file ...\n    url: \"https://hydra.nixos.org/job/nix/maintenance-2.24/buildStatic.x86_64-linux/latest/download-by-type/file/binary-dist\"\n    output: \"/tmp/renovate/cache/containerbase/50789f3416da6a7a362045e5add6d2ba81fef302b1678eae91ab63978e430317/binary-dist\"\n[12:53:38.117] ERROR (103): Response code 404 (Not Found)\n[12:53:38.118] FATAL (103): Download failed in 454ms.\n[12:53:38.296] ERROR (53): Command failed with exit code 1: /usr/local/containerbase/bin/install-tool.sh nix 2.24.1\n[12:53:38.297] FATAL (53): Install tool nix failed in 3.6s.\n",

Changes:

Bumped the version of Nix used in tests to the latest. This replicates the issue.
Updated the Hydra URL for Nix v2.24+.

@sandydoo Hell of a timing: #3067. :sweat_smile:

@BenoitKnecht, we should've had a battle of the PRs! suffix vs path

@BenoitKnecht, we should've had a battle of the PRs! suffix vs path

@sandydoo Don't tempt me. :crossed_swords: :smile:


containerapp job support

I would like to deploy a containerapp job. I initially tried using the parameters but it runs az containerapp create, but for jobs it should be az containerapp job create.
I also tried with yaml but it crashed with ERROR: Containerapp type must be "Microsoft.App/ContainerApps".
Am I to understand that containerapp jobs are not supported? I was surprised that there were no indications about jobs whatsoever, and in https://learn.microsoft.com/en-us/azure/container-apps/azure-resource-manager-api-spec?tabs=yaml#container-app-examples (referenced in the README) jobs seem to be referenced.
I would like to either:

See clearly if containerapp jobs are not supported, in which case an alternative would be appreciated, or;
Give a working example of how to configure containerapp jobs in this action

Thanks!
https://learn.microsoft.com/en-us/azure/container-apps/jobs?tabs=azure-cli

I need this as well. There is no way to auto deploy container app jobs via git hub actions. Any help would be appreciated.

Just as an fyi I needed this as well and fell back to using the az cli directly.
You can create/update your container jobs using it, instead of using
- name: Deploy to container-apps
        uses: azure/container-apps-deploy-action@v1
        with:
          acrName: ${{ env.acr }}
          containerAppName: ${{ env.container_app }}
          resourceGroup: ${{ env.resource_group }}
          imageToDeploy: ${{ env.login_server }}/${{ env.image }}:${{ github.sha }}

you can use
- name: Deploy to container-apps-jobs
        uses: azure/cli@v2
        with:
          azcliversion: latest
          inlineScript: |
            az containerapp job update -n ${{ env.container_app }}-cron -g ${{ env.resource_group }} --image ${{ env.login_server }}/${{ env.image }}:${{ github.sha }}

Not great but should unblock you at least


Dependency to vulnerable Microsoft.AspNetCore.App.Runtime.win-x64 6.0.6 introduced in image 20221111.1

Description
The new image 20221111.1 seems to introduce some dependencies that are flagged as overdue by Component Governance (we are Microsoft-internal team). There were no dependency changes in our code.
[INFO] _________________________________________________________________________________________________________________________________________________
[INFO] |Security Alerts                                                                                |
[INFO] ||
[INFO] |Alert title                             |Affected component                      |Severity                      |Due date                      |
[INFO] |||||
[INFO] |CVE-2022-38013                          |Microsoft.AspNetCore.App.Runtime.win-x64 6.0.6|High                          |2022-10-31T10:39:30.0000000Z  |
[INFO] |||||
[INFO] |CVE-2022-38013                          |Microsoft.AspNetCore.App.Runtime.linux-x64 6.0.6|High                          |2022-11-21T01:48:55.3736348Z  |
[INFO] ||||_______________________|
After requesting an extension to the Component Governance alert, I have run a build from the same commit that worked before and got the Component Governance alert above. The only reason the build was not failed due to that is the extension I requested.

20221027.1 (good): https://dev.azure.com/crisai/SpeechServices/_build/results?buildId=107764&view=results
20221111.1 (bad): https://dev.azure.com/crisai/SpeechServices/_build/results?buildId=107775&view=results

Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Current image version: '20221111.1'
https://dev.azure.com/crisai/SpeechServices/_build/results?buildId=107752&view=results
Is it regression?
yes, 20221027.1, https://dev.azure.com/crisai/SpeechServices/_build/results?buildId=107686&view=results
Expected behavior
No dependencies introduced that result in Component Governance alerts
Actual behavior
Component Governance alerts with overdue vulnerability
Repro steps
Trigger a new build that picks up the new image.

@andreasjl https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-38013 looks like the cve is quite old, we are installing the latest version of vs studio so targeting any new image would not help for us

Hey @andreasjl,
Please provide more info about dependencies used in your project and steps to reproduce that issue. When I run sample project to test vulnerable packages "if exist" I found nothing.

Hello,
We do not have any explicit dependency to microsoft.aspnetcore.app.runtime.win-x64 or microsoft.aspnetcore.app.runtime.linux-x64. I believe, the package is pulled in by the project type defined in the .csproj

When doing a dotnet restore locally, only v 6.0.11 is restored. That is the same version we use for other Microsoft.AspNetCore packages, too.
We had a similar problem in our OneBranch build pipeline. There we could resolve the issue by changing the image from
cdpxwin1809.azurecr.io/global/obinfra/windows/1809/vs2019:latest
to
onebranch.azurecr.io/windows/ltsc2019/vse2022:latest

@erik-bershel @Fraegle responded on behalf of my team.

hello @andreasjl, we will be keep looking

@andreasjl is this still a problem?

The issue was the SDK version. The one in the global.json was too old. The global.json contained a parameter to roll forward, but that does not work in the ADO task.
We now updated the SDK Version in the global.json, so this is not an apparent problem.
Still, the ADO Task should respect the roll forward property of the global.json.

@Fraegle thanks! Going to mark it resolved then, as of the task itself. feel free to ask the azure-build-task team I believe. If you have any questions, feel free to reach us again!


Add support to run generic sidecars

This adds the ability run a custom sidecar alongside the vertica server.
A new property was added to the CR to allow this:  spec.sidescars[]
When the operator adds the new container, it will automatically include
the volume mounts that were added to the server container.  This way it
automatically has access to the same PV.
A new container was added for testing purposes.  Called the vlogger, it
will send output from vertica.log to stdout in a sidecar.  A few e2e
tests use this to ensure we can run with a sidecar.  This container is
not intended to be externalized in Vertica's dockerhub.
To allow this new image to be used in the e2e tests, the kustomize setup
was changed to allow for this image to be set.  Some of the VerticaDB specs
that we use for tests have a new kustomize-vlogger-image placeholder
for this purpose.

/run-e2e

"A new container was added for testing purposes. Called the vlogger, it will send output from vertica.log to stdout in a sidecar. " I understand the container was for testing purposes, I just have a very general question: does this container keep sending output to stdout or does it only send output for one time?

"A new container was added for testing purposes. Called the vlogger, it will send output from vertica.log to stdout in a sidecar. " I understand the container was for testing purposes, I just have a very general question: does this container keep sending output to stdout or does it only send output for one time?

Thanks for reviewing @ningdeng .  It will keep sending output to stdout.  Kubernetes will capture that in its own logging file.  But you have the ability to do kubectl logs on it etc.  A good depiction of what the sidecar does is here


fix: works with falsy value & third parameter for params function

falsy:
feathers-memory starts with 0 by default. With an keyHere or keyThere of 0: feathers-shallow-populate resulted in an empty $in: [] array.
This PR fixes this and adds a test.
third parameter:
My PR other PR for feathers-graph-populate allows app wide hooks for the params in populates. On the app wide hook you probably want to know from which service the hook is.
With this PR, the params function has the following parameters: (params, context, { path, service })

Thank you, @fratzinger

Released as<EMAIL_ADDRESS>


Replaceable consoles

Description
A console that is able to replace an another console with itself.
This will simplify transitioning from limine terminal to fbcon at early boot.

The problem was solved in more of a KISS way in 8e1701e5e61fe7c85e1c251b340a8dacb2f6faac


Some questions about json files from raw data and inputs of the 3D U-Net

Hello, authors. Your work is very exciting and meaningful! I have some questions about the details in the json file. How is point_coord selected? How are features of the volume, surface_area, radius gotten? Are they taken from the centerline file?
In addition, I have some questions about the inputs of the 3D U-Net. Since KP2 in one of the small isolated components can be found using morphological operations, we can randomly select a point in that small object as the center point of our subvolume. However, how can we locate 808080 subvolume of the disconnected point in KP1 part. Since the location of KP1 and KP2 components is unknown, how to develop a sampling strategy in the 3D U-Net.
I'm looking forward to your Pytorch implementation of keypoint detection. May I ask the release time? I believe your work will be of great significance for the task of pulmonary airways and vessels.
Best wishes!

@weihaoSun1999 Hello, Have you implemented this code yet？


fix: resolve error for webpack 5

the error is:
Should not import the named export 'version' (imported as 'version') from
default-exporting module (only default export is available soon)

Hello Antonio!
We have been discussing your PR and while it looks okay, it also seems odd that you're having any issue at all. We're actually going to be moving to a bundler system soon, too. I thought that in advance of changing the codebase, it makes sense to first understand if perhaps we can understand why the current setup is a problem for you. It's possible that we could fix it together in your project.
To paraphrase @marcoroth, ES modules are new-ish, but not so new that Webpack 5 shouldn't support them.
Are you running this with Webpacker 6 beta or something? I can say, for what it's worth, that Webpacker 5.4.3 works perfectly.

Yes I upgrade my rails app to use webpacker  6.0.0-rc.6


'vsts build queue' should queue for current branch if in a Git repository

vsts build queue would be much more useful if it defaulted to the current branch if the user is in a git repository. Also, having a git alias for it would make sense.

@bergmeister After discussion with the team, it was decided that there are cases where we do not want the default branch from the git repo, so we have pulled out the functionality that defaults it to your current git branch as its the safer of the two approaches.  I realize that there is merit in both behaviors.   I am looking into adding some logic, so that you can configure the behavior you desire.  Stay tuned, we will be investing more in the CLI soon.


Warning when compiling with Swift 5.2

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[x] I have read the wiki page and cheat sheet, but there is no information I need.
[x] I have searched in existing issues, but did not find a same one.
[x] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
In ImageDrawing.swift
let rowBytes = Int(CGFloat(cgImage.bytesPerRow))
the more stringent 5.2. compiler issues a warning:

Initialization of immutable value 'rowBytes' was never used; consider replacing with assignment to '_' or removing it

What
Should not issue warning
Reproduce
[The steps to reproduce this issue. What is the url you were trying to load, where did you put your code, etc.]
Other Comment
COCOAPODS: 1.9.0.beta.2
Kingfisher (5.13.0):

This should be fixed in #1393


Strange behaviour encoding "$" dollar symbol

I noticed this behaviour with encoding funtion:
If the input is "$ $" the output is "%24%20%24"
but if the input is "$$" the output is "56620"

It is a problem that occurs because of bash, the number that comes up is the session pid.


[Bug] Async Caching - object list can't be used in 'await' expression

Hello, I'm trying to use async mode - seeing this bug, can I get help ?  cc @tylerhutcherson
Code to repro
Create Index
def __init__(
        self,
        host=None,
        port=None,
        password=None,
        redis_url=None,
        similarity_threshold=None,
        use_async = False,
        **kwargs,
    ):
        from redisvl.index import SearchIndex
        from redisvl.query import VectorQuery

        print_verbose(
            "redis semantic-cache initializing INDEX - litellm_semantic_cache_index"
        )
        if similarity_threshold is None:
            raise Exception("similarity_threshold must be provided, passed None")
        self.similarity_threshold = similarity_threshold
        schema = {
            "index": {
                "name": "litellm_semantic_cache_index",
                "prefix": "litellm",
                "storage_type": "hash",
            },
            "fields": {
                "text": [{"name": "response"}],
                "text": [{"name": "prompt"}],
                "vector": [
                    {
                        "name": "litellm_embedding",
                        "dims": 1536,
                        "distance_metric": "cosine",
                        "algorithm": "flat",
                        "datatype": "float32",
                    }
                ],
            },
        }
        if redis_url is None:
            # if no url passed, check if host, port and password are passed, if not raise an Exception
            if host is None or port is None or password is None:
                raise Exception(f"Redis host, port, and password must be provided")
            redis_url = "redis://:" + password + "@" + host + ":" + port

        print_verbose(f"redis semantic-cache redis_url: {redis_url}")
        if use_async == False:
            self.index = SearchIndex.from_dict(schema)
            self.index.connect(redis_url=redis_url)
            try:
                self.index.create(overwrite=False)  # don't overwrite existing index
            except Exception as e:
                print_verbose(f"Got exception creating semantic cache index: {str(e)}")
        elif use_async == True:
            print("creating async semantic cache index")
            schema["index"]["name"] = "litellm_semantic_cache_index_async"
            self.index = SearchIndex.from_dict(schema, use_async=True)
            self.index.connect(redis_url=redis_url)
            try:
                self.index.create(overwrite=False)  # don't overwrite existing index
            except Exception as e:
                print_verbose(f"Got exception creating semantic cache index: {str(e)}")

Query index
        from redisvl.query import VectorQuery
        import numpy as np

        # query

        # get the messages
        messages = kwargs["messages"]
        prompt = ""
        for message in messages:
            prompt += message["content"]

        # convert to embedding
        embedding_response = await litellm.aembedding(
            model="text-embedding-ada-002",
            input=prompt,
            cache={"no-store": True, "no-cache": True},
        )

        print("async got embedding_response", embedding_response)

        # get the embedding
        embedding = embedding_response["data"][0]["embedding"]

        query = VectorQuery(
            vector=embedding,
            vector_field_name="litellm_embedding",
            return_fields=["response", "prompt", "vector_distance"],
        )
        print("async querying semantic cache", query)
        results = await self.index.aquery(query)
        print("async got results", results)

stacktrace
An exception occurred: Traceback (most recent call last):
  File "/Users/ishaanjaffer/Github/litellm/litellm/caching.py", line 972, in async_get_cache
    cached_result = await self.cache.async_get_cache(cache_key, messages=messages)
  File "/Users/ishaanjaffer/Github/litellm/litellm/caching.py", line 472, in async_get_cache
    results = await self.index.aquery(query)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/redisvl/index.py", line 106, in wrapper
    await check_async_redis_modules_exist(_redis_conn.client)
  File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/site-packages/redisvl/utils/utils.py", line 60, in check_async_redis_modules_exist
    installed_modules = await client.module_list()
TypeError: object list can't be used in 'await' expression

It looks like this doc is wrong

I needed to do this:
self.index = SearchIndex.from_dict(schema, use_async=True)
self.index.connect(redis_url=redis_url, use_async=True)

Hi @ishaan-jaff thanks for opening this! Will take a look today.
Fair warining -- we are rapidly approaching a 0.1.0 release, as up until now the package has been in pre-release mode. This new version will drop this week and contains a number of updates and improvements, including redis connection handling and async work.
You can see the latest state on the tip of this branch/PR:
https://github.com/RedisVentures/redisvl/pull/105
Apologies for the confusion. One of the core updates will be separating the SearchIndex and AsyncSearchIndex classes for ultimate clarity :)

this was fixed by adding this to my code - but I think it should be added to your docs @tylerhutcherson
self.index = SearchIndex.from_dict(schema, use_async=True)
self.index.connect(redis_url=redis_url, use_async=True)

@ishaan-jaff Given you are building this as an integration into your library, I'd strongly recommend waiting until our stable release at 0.1.0. You can pip install from the branch linked above.
The new and improved async flow will look like this:
from redisvl.index import AsyncSearchIndex

index = AsyncSearchIndex.from_dict(schema)
index.connect(redis_url)

await index.create()

await index.load(data)

...

when will 0.1.0 be out?

(I'll mark semantic caching as a beta-feature until then)

Targeting thursday or friday this week.

@tylerhutcherson Pylance keeps throwing errors in vscdode for all async and awaits.
"await" allowed only within async function Pylance


Advanced Search changes

As any user
I want Advanced Search to be intuitive to use
so that I can easily search for specific elements of a request

Assumptions & Scope
What is IN scope?
What is NOT in scope?
Acceptance Criteria
Scenario x: Remove default setting on Request Description button

GIVEN ... I am on the queue
WHEN ... I click on Advanced Search at the top of a queue and land on the page
THEN ... all buttons (request descrip, ID, Axis request, applicant, assignee or subject code) will be unselected (they'll be grey in colour and not filled in blue).
AND ... the apply search button will be inactive

Scenario x: Tool tip on request selection

GIVEN ... I am on the Advanced Search page
WHEN ... I click on Tool tip button (DESIGN NEEDED)
THEN ... information appears explaining that at least one criteria mustbe selected for search to work
AND ... the apply search button will be inactive

Scenario x: Perform a Key word Search / Activate Apply Search Button

GIVEN ... I am on the Advanced Search page
WHEN ... I enter in one or more key words
AND ... make at least one selection from the search categories (Request State, Request Status, Request Type, Date Range and/or Search by Public Body)
THEN ... The Apply Search button will become active

Scenario x: Buttons narrow the search

GIVEN ... I have performed a key word search and generated the search results
WHEN ... I select a button  (request descrip, ID, Axis request, applicant, assignee or subject code)
AND ... click Apply Search
THEN ... The search results will filter by the key word + button selection

Scenario x: Number of tags possible

GIVEN
THEN
WHEN

*Scenario x: Display search results # (DESIGN NEEDED)
...
Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)
Validation Rules? (If yes, list here)
Design
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/874445058
Definition of Ready

[ ] Is there a well articulated User Story?
[ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
[ ] If there is a user interface, is there a design?
[ ] Does the user story need user research/validation?
[ ] Does this User Story needs stakeholder approval?
[ ] Design / Solution accepted by Product Owner
[ ] Is this user story small enough to be completed in a Sprint? Should it be split?
[ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
[ ] Has the story been estimated?

Definition of Done

[ ] Passes developer unit tests
[ ] Passes peer code review
[ ] If there's a user interface, passes UX assurance
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Confirm Test cases built and succeeding
[ ] No regression test failures
[ ] Test coverage acceptable by Product Owner
[ ] Ticket ready to be merged to master or story branch
[ ] Developer to list Config changes/ Update documents and designs
[ ] Can be demoed in Sprint Review
[ ] Tagged as part of a Release
[ ] Feature flagged if required
[ ] Change Management activities done?

I've begun on the AC from the Adv Search discussion today, please feel free to refine further @lmullane
cc: @m-prodan @arielleandrews @JHarrietha-AOT @richard-aot @jadmsaadaot

@richard-aot - Do I need to write up two separate Issues... one for IAO users and one for ministry users?

One issue is fine, @Pilchar, Molly CITZ:EX @.***> We
will not miss ministry this time. :)
On Wed, Mar 16, 2022 at 11:45 AM molly pilchar @.***>
wrote:

@richard-aot https://github.com/richard-aot - Do I need to write up two
separate Issues... one for IAO users and one for ministry users?
—
Reply to this email directly, view it on GitHub
https://github.com/bcgov/foi-flow/issues/1688#issuecomment-1069459585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVTSVKM2FRDEOWVYBDB5MADVAIT3VANCNFSM5Q2JIQ4A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

x-ref ticket with #1654

I am unable to edit the issue itself to add the design link but here it is: https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/874445058

@richard-aot I need to update the AC for this one. We put a ballpark estimate of 5 on this for the purpose of planning, but let's connect on this one next week (Apr 4)

need to investigate unopened requests no longer showing unassigned in assignee column

@richard-aot. I've added the designs to the AC and verified that there was no change in the ACs for the first 4.
@JHarrietha-AOT, unclear to me what if there were any design or functionality changes for the last two ACs?

Thanks, @JHarrietha-AOT
I will remove scenarios 5 and 6 from this story. Could you please write a bug ticket for applicant names for general requests showing for ministry coordinators?
cc @richard-aot @KaraBeach @m-prodan @mpilchar

@lmullane I was looking at other advanced search tickets, I don't thinks the columns in the advanced search results matching the columns in that user groups queue was ever included in AC. So I wrote it as a story so it was easy to divide out what the columns should be for each user.
Let me know if you have any questions its: #1837

#1688 is ready for testing. Also increased the estimate to 8 to reflect the actual time took for this US.

Created bug #1871 to correct date ranges

Moving back into "ready for QA" column until I get confirmation from PO on functionality and can update AC for this one


chore: Remove CLI and UI code

Signed-off-by: Alex Collins<EMAIL_ADDRESS>Checklist:

[x] My organization is added to USERS.md.

``
--- FAIL: TestValidateExamples (0.05s)
Error:     validation_test.go:12: There was an error: Object has no key 'io.k8s.apimachinery.pkg.runtime.RawExtension'


FixEnhanced Security Checks for Audit Log File Names (#44612)

#44612

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

run buildall


_com_error in winrt::impl::consume_Windows_AI_MachineLearning_ILearningModelSessionFactory

I'm submitting a…
Bug report (I searched for similar issues and did not find one)
Current behavior
"_com_error at memory location" noise in check_hresult
Exception thrown at 0x00007FFFF08E4FFC in ml.exe: Microsoft C++ exception: _com_error at memory location 0x00000068814FAE90.
Exception thrown at 0x00007FFFF08E4FFC in ml.exe: Microsoft C++ exception: _com_error at memory location 0x00000068814FB1C8.
Exception thrown at 0x00007FFFF08E4FFC in ml.exe: Microsoft C++ exception: _com_error at memory location 0x00000068814FAE90.
Expected behavior
Not calling deviceToRunOn with null_ptr and polluting Debug Output with check_hresult messages
Minimal reproduction of the problem with instructions
LearningModelSession session = nullptr;
LearningModelBinding binding = nullptr;

...
session = LearningModelSession{ model, LearningModelDevice(LearningModelDeviceKind::DirectXHighPerformance) };
binding = LearningModelBinding{ session };
Environment
Windows Build Number:
22621.2361
Windows Feature Experience Pack 1000.22674.1000.0
11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz   2.69 GHz
App min and target version:
OS Version (Server, IoT Core, Desktop, etc):
Windows 11 Pro
Graphics Driver version:
NVIDIA GeForce RTX 3060
DxDiag:
WinMLTools specific:
- PyTorch / exported to ONNX (proprietary cannot share, belive to be the same on any onnx model)
- WinMLTools version:

Visual Studio
Microsoft Visual Studio Professional 2022 (64-bit) - Current
Version 17.7.4

Thanks for posting. This debug output is currently expected.


Replace isExpensifyCash param for sign up and tweak platform param for graphite timing

Please review @Julesssss / @stitesExpensify
cc @tgolen
Details
Replacing isExpensifyCash param with referer param, editing the referer param in one spot to be platform.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/149347
Related API PR: https://github.com/Expensify/Web-Expensify/pull/30044
Tests

Apply same branch on dev API
Verify you can sign in on all platforms

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[ ] iOS
[x] Android

Unable to test on iOS, so if anyone could verify that would be awesome 🙏

Unable to test on iOS, so if anyone could verify that would be awesome 🙏

p.s. When we merge this, let's CP the web PR.

p.s. When we merge this, let's CP the web PR.

Verified iOS sign in, checked the box ✅

Verified iOS sign in, checked the box ✅


Add open and close event emits

Overview
This Pull request includes open and close event emits, in order to inform the parent component when the the dropdown is opened.
Details
Added a watcher for the open state, in order to emit open or close event, when open changes to true or false accordingly.

@kazvaggos Thank you :tada:


Docs: Metadata database

This is a draft proposal for the metadata database. Includes:

New fields were added in the files table to include the "main" and "replica" location of the file.
Replace the locations table with the directories one to make it similar to the file system.
Replace the name column in the old locations table with the volume, parent_id and name columns in the new directories table.
Update the queries according to the new columns.

Please update the Worker volume structure as this or similar
/
├── files/
│   ├── [VOLUME_MOUNT_DATA_1]/
│   │   └── [FILE_UUID_X]
│   └── [VOLUME_MOUNT_DATA_2]/
│       └── [FILE_UUID_Y]
└── backups/
    ├── [VOLUME_MOUNT_BACKUP_1]/
    │   └── [FILE_UUID_X]
    └── [VOLUME_MOUNT_BACKUP_2]/
        └── [FILE_UUID_Y]


README : suggest adding 'what good looks like'

Firstly, thanks for building this !
I've been testing over the past releases and seen things evolving. I purchased one of the supported vacuums (SL60D) in the hope that the features (map and path) would appear, but given things are evolving difficult to understand what the 'expected behaviour' is (apart from looking at the Xiaomi extractor as a reference).
May I suggest adding into the README:

Which vacuum author is using for development.
A short picture (or video) showing what is seen on the card for the given release.

Thanks !

Thank you for the suggestions. Will definitely include it in the future!


"Could not append to the internal temporary file" When preparing TFDS imagenet dataset on TPU-VM

(1) please update the bug template to include instructs to get TF version properly python3 -c "import tensorflow as tf; print(tf.__version__)"
vs. TF 2.0 instructions in this bug template: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
The former yields : 2.6.0
(2)
System information
TPU-VM v3-8 with alpha 2.0 software and Colab Pro large memory instance.
This is a duplicate of #37132 , but I believe the details were not flushed out hence I'm writing a new Issue.
I use something like:
import tensorflow_datasets as tfds
source_dir='gs://MY_BUCKET/ILSVRC2012'
dest_dir='gs:/MY_BUCKET/ILSVRC2012_tf_records'
tfds.builder('imagenet2012',data_dir=dest_dir).download_and_prepare(
    download_config=tfds.download.DownloadConfig(
        manual_dir=source_dir))

In my use case I'm using TFDS and trying to write the TF records to a bucket using my TPU-VM (granted generously by TRC ❤ which has 100GB as a root drive so 50-ish GB free space). half way through it completely fills the disk and the process of preparing the TF records fails.
This happens because of the default behavior for the GFile async writes, which is to store some tmp files in /tmp like:
tmp_file_tensorflow_539_EDt0Pl                                 tmp_file_tensorflow_994_lWEmew
tmp_file_tensorflow_540_RdDgOX                                 tmp_file_tensorflow_995_yaqZEX
tmp_file_tensorflow_541_rwyIRz                                 tmp_file_tensorflow_996_HDijKz
tmp_file_tensorflow_542_XF4R0b                                 tmp_file_tensorflow_997_bxYY9g
tmp_file_tensorflow_543_EVoGfO                                 tmp_file_tensorflow_998_HRem23
tmp_file_tensorflow_544_ebDRzq                                 tmp_file_tensorflow_999_tPD8y1
tmp_file_tensorflow_545_LK3B02                                 tmp_file_tensorflow_99_A7tVko
tmp_file_tensorflow_546_MoRHwF                                 tmp_file_tensorflow_9_GI4Quq

with no ability to change it or override it IIUC, and TPU-VMs we can't edit fstab to mount another /tmp 😢
and changing dest_dir to a secondary disk doesn't help as TFDS insists on writing to /tmp
I tried to do this with Colab pro (which has 180-ish GB free space), managed to get away almost with the entire process and after 4h 47m 47s I get:
Downloading and preparing dataset imagenet2012/5.1.0 (download: Unknown size, generated: 155.84 GiB, total: 155.84 GiB) to /content/MY_MOUNTED_GCS_FUSE_BUCKET/ILSVRC2012_tf_records/imagenet2012/5.1.0...
Shuffling and writing examples to /content/MY_MOUNTED_GCS_FUSE_BUCKET/ILSVRC2012_tf_records/imagenet2012/5.1.0.incompleteROAOS5/imagenet2012-train.tfrecord
100%
1281166/1281167 [1:49:37<00:00, 305.35 examples/s]
Shuffling and writing examples to /content/MY_MOUNTED_GCS_FUSE_BUCKET/ILSVRC2012_tf_records/imagenet2012/5.1.0.incompleteROAOS5/imagenet2012-validation.tfrecord
100%
49999/50000 [12:36<00:00, 80.58 examples/s]
Shuffling and writing examples to /content/MY_MOUNTED_GCS_FUSE_BUCKET/ILSVRC2012_tf_records/imagenet2012/5.1.0.incompleteROAOS5/imagenet2012-test.tfrecord
100%
99999/100000 [19:05<00:00, 118.47 examples/s]
---------------------------------------------------------------------------
ResourceExhaustedError                    Traceback (most recent call last)
<ipython-input-4-08cf32753112> in <module>()
      4 tfds.builder('imagenet2012',data_dir=dest_dir).download_and_prepare(
      5     download_config=tfds.download.DownloadConfig(
----> 6         manual_dir=source_dir))

3 frames
/usr/local/lib/python3.7/dist-packages/tensorflow_datasets/core/dataset_builder.py in download_and_prepare(self, download_dir, download_config)
    416           self.info.download_size = dl_manager.downloaded_size
    417           # Write DatasetInfo to disk, even if we haven't computed statistics.
--> 418           self.info.write_to_directory(self._data_dir)
    419     self._log_download_done()
    420

/usr/lib/python3.7/contextlib.py in __exit__(self, type, value, traceback)
    117         if type is None:
    118             try:
--> 119                 next(self.gen)
    120             except StopIteration:
    121                 return False

/usr/local/lib/python3.7/dist-packages/tensorflow_datasets/core/utils/py_utils.py in incomplete_dir(dirname)
    343   try:
    344     yield tmp_dir
--> 345     tf.io.gfile.rename(tmp_dir, dirname)
    346   finally:
    347     if tf.io.gfile.exists(tmp_dir):

/usr/local/lib/python3.7/dist-packages/tensorflow/python/lib/io/file_io.py in rename_v2(src, dst, overwrite)
    622   """
    623   _pywrap_file_io.RenameFile(
--> 624       compat.path_to_bytes(src), compat.path_to_bytes(dst), overwrite)
    625
    626

ResourceExhaustedError: /content/MY_MOUNTED_GCS_FUSE_BUCKET/ILSVRC2012_tf_records/imagenet2012/5.1.0.incompleteROAOS5; Too many open files

Both issues in my head look like there are too many temp files being created (without cleanup) that it either fills the root drive or trips a requests quota.
Thoughts, Ideas, Advice?
@skye FYI.

@mjsML ,
Can you please try to test your code in latest stable tf v2.6 and let us know if the issue still persists.Thanks!

@tilakrayal when I run this
import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)

on my TPU-VM I get
unknown 2.6.0

on Colab I get
v2.6.0-0-g919f693420e 2.6.0

both unknown and v2.6.0-0-g919f693420e don't match the release's tag.
Regardless of the tf.version.GIT_VERSION I assume that the version number (being .0 not .0.foo) is the stable version?
If not do you recommend specific steps to upgrade TF and not break libtpu ?

There is already an issue open in tensorflow/datasets repository, you can refer to the temporary solution mentioned in the same issue.

I see, I'll try the workaround and will report back.

Hello,
I recently ran into the same issue when trying to use TensorFlow Datasets on a TPU-VM to create a dataset at ~400GB. The workaround that is linked above is solving an issue with too many open files, not an issue with the size of the files being saved to /tmp. I was able to work around this problem by creating a new persistent disk with enough space, and then mounting it to my TPU-VM /tmp folder.
It seems strange that creating a dataset on a Google Cloud Bucket from files stored in a Google Cloud Bucket requires you to be able to store an entire split of the dataset in the /tmp folder. Is this the desired behavior?
From what I can understand, this is to be able to shuffle the dataset before finally writing it to the final destination. If so, why is this the behavior even when using options such as shuffle_files=False to create the dataset?

Hello,
I just ran into the same problem when I tried to create a dataset at ~10TB. The mounting workaround cannot work for my situation as my persistent disk is not large enough. Is there any update on resolving this problem?

Hello,
I ran into the same problem as @redagavin. Did you find a work around?


import * as module name is a little strange

Previously import * as mod from ... was used, but now the example name looks a little strange.
Libraries with long names seem to cause problems like #790.

this also has a side effect of turning numbers into underscores which I reported separately https://github.com/jsr-io/jsr/issues/803


Upgrade to React 16

Fixes #9
No comment on the backwards compatibility of this change.

Would be better in peerdeps


Privilege Profile support

Replaces #2070
Related to #1964 #1944
Trying to resurrect the past attempts at this. The main requirements are selinux and credential spec which are blockers - seccomp and apparmor are nice to have.
I mapped what we have in docker's --security-opt in here. Since we need a couple of those options I figured I could port everything that's in there (that's why I left capabilities out for the time being).

Is this the right direction?
For credential spec, in docker we add an URI (either file://path or registry://key). Do we want to continue in the same direction or do we want to just embed the blob?
For SELinux, in docker we are using a micro format at the API level (--security-opt="label:user:USER"). Here I tried to make that strongly typed
For seccomp and apparmor, I'm assuming we're using a profile already loaded on the machine.

/cc @cyli @ehazlett @johnstep @aaronlehmann @dhiltgen @diogomonica @tiborvass

Further notes: In #1964 we were trying to group options by OS. I initially agreed but I feel like it might be overkill. It's relatively safe to assume that those options apply only to supported platforms.
After all, it's not just because you're running linux that SELinux or AppArmor options are going to work: you actually need host level support.

@diogomonica @cyli In the original PR, we were encapsulating those options into a "raw" object (which I assume paved the road to entitlements).
Could you shed some light?

For seccomp and apparmor, I assume the profiles are available locally.
Maybe at some point we might want to inject them (and I am not sure how feasible that is - I don't think we can just inject new stuff).
Anyway, that's not happening now for sure. Do we need to mark them as "local"? Or are we good with this interpretation?

For seccomp, we take the profile directly from the client.

@cpuguy83 say again? Where is it stored?

How #1722 relates to this PR?
Also, I guess CapAdd/CapDrop is intentionally omitted from this PR, but could you please elaborate the current plan about supporting CapAdd/CapDrop?

@aluzzardi example: --security-opt seccomp:/path/to/profile. In this case the profile would be on the client, it is read in and passed as configuration. The microformats of microformats.

@aluzzardi - Yes the original plan was for the privilege profile to contain a full list of the raw capabilities to be passed to the service, and the entitlements would be a UI feature that generated that list.
I think I may be behind on what we're currently planning on doing though - AFAIK for plugins, will the the spec object just be the raw object from docker?  If so, I think that includes the docker object HostConfig which includes the security opts, etc?  Is this going to work differently for containers in swarmkit, which would use this spec instead?

For credential spec, in docker we add an URI (either file://path or registry://key). Do we want to continue in the same direction or do we want to just embed the blob?

How about making this more strongly typed by making it a oneof? We can start with fields for a file path or registry path. If we decide to support embedding the blob, that could be a third field we add later.

For seccomp and apparmor, I'm assuming we're using a profile already loaded on the machine.

Sounds like another situation where we might appreciate having a oneof later.

@patricklang do you have feedback on this?

For credential spec, in docker we add an URI (either file://path or registry://key). Do we want to continue in the same direction or do we want to just embed the blob?

I think the question is whether we should persist with the current approach of requiring operator to distribute a file or registry setting on all hosts in the swarm where a service is to be run, or whether we should do something smarter to that on docker service create the docker CLI will read a credentialspec file on the current host and then the credentialspec is stored in swarm with the service metadata.

@n4ss @docker/security-team

@friism I don't think users like deploying extra files to hosts. The fewer the better - ie just install the Docker engine and your plugins, join the swarm and done. Pushing these through swarm also makes it easier if I want to redeploy a service with a different Active Directory service account. That way I don't need to update things stored on the hosts before deploying the service.

Few changes:

Renamed PrivilegeProfile to Privileges
Added a oneof for CredentialSpec
Removed AppArmor and Seccomp - out of the scope for now

Questions:

Should the oneof for CredentialSpec contains sub messages, such as FileReference and RegistryReference rather than just a string?
Should CredentialSpec be outside of Privileges, since it's not entirely privilege related?

Should the oneof for CredentialSpec contains sub messages, such as FileReference and RegistryReference rather than just a string?

Personally I think a string is fine. If we're referencing a local file, a file path seems like the right way to do that, and I don't expect we'd need to add more meta-information. If it turns out we do, we already have the oneof, so it's easy to add a new way to reference the file.

Should CredentialSpec be outside of Privileges, since it's not entirely privilege related?

I don't understand CredentialSpec well enough to give a good answer, but my understanding of these protos was that CredentialSpec was related enough to security/privileges to belong there.

I think normally this would be a registry reference?

@diogomonica Another question for you ... (and for you @dhiltgen ?)
This is what I have for SELinux:
	message SELinuxContext {
		string user = 1;
		string role = 2;
		string type = 3;
		string level = 4;
	}

I see there's also a label:disable - what is that and how should we represent it?

Updated with the implementation

lable:disable just means to disable selinux for that container.
Could handle with a oneof I guess? It's either disabled or specify the other options?

The label:disable bit is handled by the selinux library, btw.

on it

I've decided to remove the code from here, protos only.
The one and only implementation is docker/docker#32339
Can we agree on the protos and move on?
I would need an LGTM from someone from security (ping @docker/security-team @n4ss @diogomonica) and an overall datatype LGTM (ping @aaronlehmann @cpuguy83)
Once this PR is merged we'll shift the focus on the implementation details in docker/docker#32339

LGTM

LGTM

I tested credential-spec: https://github.com/docker/docker/pull/32339#issuecomment-291716997

Thanks @friism @cpuguy83 @aaronlehmann!
Merging by EOD - @diogomonica @n4ss @cyli Any chance of getting a quick review by then?

@aluzzardi will this allow us to pass client-sided full seccomp.json files to be used?

@aluzzardi sorry for the late review, LGTM
@diogomonica it will require an additional field in Privileges (https://github.com/docker/docker/pull/32339/files#diff-a8f1f5d69ceb8aca0cd086c7220c35f1R41), I guess.

@diogomonica seccomp and apparmor were dropped from this PR. SELinux and CredentialSpec only

Thanks everyone!

@aluzzardi is there a reason why it's SELinux only on linux? Or is it just a part.1 PR?


Fix recursive serialization issue that Eric found

This issue will not affect any users. But it will produce a nasty exception in the console if you try debugging Augury itself (which I am assuming very few people will)

Very nice

So in other words, it's not the router tree causing the issue, it was the dev tools, debugging the router tree which raised the exception.

No, it was caused by this flow:

Open an Angular 2 application with Augury closed
Do some stuff in the application that causes it to rerender itself a couple times
Open Augury

But there is no way this exception could affect use of the application in any way, because the frontend will request a tree on ngOnInit regardless and the offending message -- getting a diff for a tree that doesn't exist, because Augury wasn't open -- will essentially be discarded.

:shipit: 🚀


Override validity messages

@aFarkas
Hey @aFarkas, I'm trying to update webshims in an existing project to the latest version but I'm facing a few issues regarding the custom messages. They are basically not working anymore. Maybe I'm missing something.
I have setup a jsfiddle here to have a small example: http://jsfiddle.net/w2L4e5yg/1/
When hovering the textfield, the text is still the default text from the browser. In a previous version (1.8.13), it worked and we could update the text.
Could you point me in the right direction to get the same result as before?
Thanks.

@aFarkas I've created an example with the old version (1.8.12) to show you it worked before: http://codepen.io/anon/pen/QjeyXJ/?editors=101
Using Firefox, I can see the custom message:

But I can't find a way to get the same result with the latest version of webshims. Could you help?

@tleunen
The overrideMessages option is gone. It caused many many problems. I recommend, that you live with the customMessages option in combination with replaceValidationUI or the iVal.
As an alternative you try something like this:
var overrideMessage = function(){
	var changeMessage = function(){
		if(!this.title || $.data(this, 'validationTitle')){
			$.data(this, 'validationTitle', true);
			this.title = $(this).getErrorMessage();
		}
	};

	$(document).on('changedvaliditystate', function(e){
		changeMessage.call(e.target);
	});

	$('input:invalid:not([title]), select:invalid:not([title]), textarea:invalid:not([title])').each(changeMessage);
};

I don't really want to change the default behavior of the browser so I'll go with the second alternative you suggested. Thanks a lot!
I'm closing this issue now that an alternative has been found.


[REQ] Display current region when changing it.

when changing the region, only the "Worldwide" option is on the display, all others are obstructed by expandable item list.
Scroll the view to the currently active region and display it under its expanded category.
v2.16.3+202201232

This should now be solved, by being unnecessary with the new multi-trend support available in the latest beta, so closing this issue.


Add serialize and deserialize method for graph.

Codecov Report

Merging #103 (87d41f5) into main (1d2a541) will decrease coverage by 12.73%.
The diff coverage is 15.38%.

@@             Coverage Diff             @@
##             main     #103       +/-   ##
===========================================
- Coverage   78.05%   65.31%   -12.74%
===========================================
  Files          50       49        -1
  Lines        4511     4374      -137
===========================================
- Hits         3521     2857      -664
- Misses        990     1517      +527

Impacted Files
Coverage Δ

python/graphscope/framework/graph.py
82.67% <12.00%> (-9.34%)
:arrow_down:

python/graphscope/framework/context.py
83.01% <100.00%> (-0.47%)
:arrow_down:

python/graphscope/interactive/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/interactive/query.py
0.00% <0.00%> (-94.65%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
12.69% <0.00%> (-61.43%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
22.82% <0.00%> (-49.38%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
28.85% <0.00%> (-32.85%)
:arrow_down:

python/graphscope/analytical/app/triangles.py
80.00% <0.00%> (-20.00%)
:arrow_down:

python/graphscope/client/utils.py
79.16% <0.00%> (-16.92%)
:arrow_down:

python/graphscope/client/rpc.py
66.93% <0.00%> (-16.89%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #103 (87d41f5) into main (1d2a541) will decrease coverage by 12.73%.
The diff coverage is 15.38%.

@@             Coverage Diff             @@
##             main     #103       +/-   ##
===========================================
- Coverage   78.05%   65.31%   -12.74%
===========================================
  Files          50       49        -1
  Lines        4511     4374      -137
===========================================
- Hits         3521     2857      -664
- Misses        990     1517      +527

Impacted Files
Coverage Δ

python/graphscope/framework/graph.py
82.67% <12.00%> (-9.34%)
:arrow_down:

python/graphscope/framework/context.py
83.01% <100.00%> (-0.47%)
:arrow_down:

python/graphscope/interactive/__init__.py
0.00% <0.00%> (-100.00%)
:arrow_down:

python/graphscope/interactive/query.py
0.00% <0.00%> (-94.65%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
12.69% <0.00%> (-61.43%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
22.82% <0.00%> (-49.38%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
28.85% <0.00%> (-32.85%)
:arrow_down:

python/graphscope/analytical/app/triangles.py
80.00% <0.00%> (-20.00%)
:arrow_down:

python/graphscope/client/utils.py
79.16% <0.00%> (-16.92%)
:arrow_down:

python/graphscope/client/rpc.py
66.93% <0.00%> (-16.89%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

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

Please verify the correctness (or return error messages) for edge cases, e.g.,

serialized on 2 workers, deserialize from 3 workers.
serialized on 4 workers, deserialize from another 4 workers, but they sharing the same worker_0
serialization files are not complete, e.g., in one of the workers, the blob file is missing.
...

Please verify the correctness (or return error messages) for edge cases, e.g.,

serialized on 2 workers, deserialize from 3 workers.
serialized on 4 workers, deserialize from another 4 workers, but they sharing the same worker_0
serialization files are not complete, e.g., in one of the workers, the blob file is missing.
...


Ion overwrites astro.config.mjs

You have an existing Astro project
You execute sst init
astro.config.mjs gets transformed into a broken state

astro.config.mjs (before sst init)
import { defineConfig } from "astro/config";

import preact from "@astrojs/preact";

// https://astro.build/config
export default defineConfig({
  site: "https://example.com",
  integrations: [preact()]
});

astro.config.mjs (after sst init)
import { defineConfig } from "astro/config";
import aws from "astro-sst";

export default defineConfig({
  output: "server",
  adapter: aws(),
});

Yeah the sst init command is mostly designed for new projects. But it would be good if we could handle this.

we have a few issues open like this - should we instead print what the user needs to add to the config instead of adding it ourselves?

Yeah probably. Maybe just do it automatically for Next.js for now?


rev minor version

Task name: NuGetCommandV2
Description: Version Rev
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) NA
Attached related issue: (Y/N) NA
Checklist:

[X] Task version was bumped - please check instruction how to do it
[X] Checked that applied changes work as expected

This PR is needed because multiple PRs (#17163, #17311, #17265, #17325, #17297) rev'd the 2.214.x version around the same time. This caused merge conflicts on the task.json and the task.loc.json.
The automatic merge resolver for the final #17297 PR reverted the latest patch updates:
see https://github.com/microsoft/azure-pipelines-tasks/pull/17297/commits/6257fd59efcc081499dd52012267973e257760af

Thus the changes did not get deployed to master. Downloading 2.214.2 and 2.214.3 nupkg from the feeds show the code changes are not present:

Thus reving just the version to force the changes to be picked up and deployed.

Tested:


docs: fix typo

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Recursive mode with a single file is allowed (and doesn't work)

Recursive mode should only work if the target specified is a directory.

Closing due to inactivity.


Adds Member Checks Before Changing Voice

Closes #1309.
Checks is a user is a guild member, before performing guild operations (such as kicking from voice or removing roles) when using voice mute or general mute.

Coverage increased (+0.06%) to 56.637% when pulling df897e57ea0dbbaeb3e2a07a1e443c5b2df34c36 on HassanAbouelela:fix-voiceban-member-bug into 80df11be0fa588bf72d563772000aa38393330e9 on python-discord:master.

I think this is related with https://github.com/python-discord/bot/pull/1016

Ah, you're right, I didn't see that other issue.

Reopening, as this isn't actually a duplicate of #1016, and has been reported again in #1370. This handles a different error at a different stage from the one fixed in the other PR.

Reopening, as this isn't actually a duplicate of #1016, and has been reported again in #1370. This handles a different error at a different stage from the one fixed in the other PR.


About Fine-tune

Great work! But I have a question about fine-tune. Is there any way to fine-tune the pretrained model to fit video with not real human, like game video or CG?

You could prepare the data annotations like this. Mapping the keypoints if the definition is different from SMPL. As for SMPL shape parameters, you could fix the branch and estimate the global translation (maybe a post process is required).


[AutoRelease] t2-voiceservices-2023-02-20-55395(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/3804
Live test success

issue link:https://github.com/Azure/sdk-release-request/issues/3804

/azp run prepare-pipelines

/check-enforcer override

/check-enforcer override


OpenSSL link doesn't work

Brief description of your issue
I was trying to install OpenSSH, but winget fails to download it. The reason is that the link that winget uses is broken (https://slproweb.com/download/Win64OpenSSL_Light-1_1_1g.msi) the right one is this https://slproweb.com/download/Win64OpenSSL_Light-1_1_1h.msi
Steps to reproduce
winget install openssh
Expected behavior
OpenSSH installed
Actual behavior
Este aplicativo é licenciado para você pelo proprietário.
A Microsoft não é responsável por, nem concede licenças a pacotes de terceiros.
Downloading https://slproweb.com/download/Win64OpenSSL_Light-1_1_1g.msi
Ocorreu um erro inesperado ao executar o comando:
Download request status is not success.
0x80190194 : No encontrado (404).

Environment
[winget --info]
Windows Package Manager v0.2.2521 Visualização
Copyright (c) Microsoft Corporation. Todos os direitos reservados.

Windows: Windows.Desktop v10.0.19041.508
Pacote: Microsoft.DesktopAppInstaller v1.11.2521.0

Links
------------------------------------------------------------
Política de Privacidade https://aka.ms/winget-privacy
Contrato de Licença     https://aka.ms/winget-license
Avisos de Terceiros     https://aka.ms/winget-3rdPartyNotice
Home page               https://aka.ms/winget

@egionaryu Thanks for reporting your issue. However, this repository is about the actual winget cli rather than its packages. To report problems with packages please file an issue here https://github.com/microsoft/winget-pkgs/issues.
PS: In your description you mentioned OpenSSH - I assume you meant to write OpenSSL (that matches the title and URLs).


Add new parsers to foam.parse

This PR adds the following new functions to foam.parse:
implied(:any)
Implied makes no changes to the PStream object other than setting the value to the one specified.
chars1(:string)
Like Chars, Chars1 matches any character in the provided string. Unlike chars, this will report a Stream with a new value (the character that was matched).
untilEscaped(escape :ParserProperty, term :ParserProperty)
UntilEscaped matches any character until the pattern term, but will also consume with the pattern escape with priority over term. This is useful for parsing quoted strings and handling specific escape sequences.

Tagging @adamvy for review