PACKAGES: mod-timespace

Use this: https://pub.dev/packages/flutter_google_places
So in mod-main when asking use to pick their location we just make it visual and detect their location. SO much easier for us and them for now.
If we can get country and city and lat long out of the thing then we are good
Works on Web and Native so all good.
Can someone check this and let me know.
Then we can do the fancy country picker and minio backend for the data later, as we are out of time for delibery.

https://pub.dev/packages/flutter_google_places is not possible due to cors issues
https://github.com/fluttercommunity/flutter_google_places/issues/93

still to do:

The return result should be output to the screen if in debug mode.
Lat, long, all address data it gives.
Make it a name value list please.
clean up mod-main userinfo as right now it was only added to the current list

endpoint
It is actually still working, but my personal ip got blocked. Did not enforce time delay between the requests... So may still the way to go but enforcing the delay?

All done including request delay enforcement + a debug flag to show coordinates from selected location


Deploy to grafana using grizzly

Use the example from here to add the ability to build and deploy to grafana directly using grizzly

Now being done within the grafana-configuration repository


[Crash] EXC_BAD_ACCESS in bsg_kscrashstate_i_onIntegerElementon Bugsnag startup, attempting to load persistent state of crash context

Expected behavior
Calling -[Bugsnag startBugsnagWithApiKey:] doesn't crash.
Observed behavior
Calling -[Bugsnag startBugsnagWithApiKey:] crashes.
Steps to reproduce
Unsure, but this is happening on application launch. We call -[Bugsnag startBugsnagWithApiKey:] in the AppDelegate.
The crash is happening here, in bsg_kscrashstate_i_onIntegerElement in the call to strcmp. name is NULL, which seems to be the issue.
Version
5.13.3, 5.14.1 (possible that earlier version are affected)
Stack trace

Thanks, @jessesquires. Looking into it.

Which version were you using before 5.14.1?

@kattrali We were on 5.13.3, which also experiences the issue. (Will update original comment)

@jessesquires Can you send me a crash report from a device via<EMAIL_ADDRESS>? I've found some potential leads but haven't reproduced this case. In general, reading/writing to disk seems to be working correctly when using 5.14.1 (and with stored reports generated on 5.13 and earlier).


Expo project crashes during MapView rendering

Attempted import error : 'requireNativeComponent' is not exported from 'react-native-web/dist/index'
Hello everyone, i'm using the module 'react-native-maps' on my Expo project (React Native). Until a few days ago everything worked well, but not anymore. When i try to open a screen that use MapView component, my app crashes without leaving logs or error messages. Thus i tried to open the project in web browser and it showed me this error:

It seems that MapView is missing something called nativeComponent. I am pretty confused because i was able to use this module perfectly and now this problem came out without reasons and without changing my code.
Environment info

react-native info output:
 System:
    OS: Windows 10 10.0.17763
    CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
    Memory: 3.10 GB / 7.92 GB
  Binaries:
    Node: 13.7.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.13.6 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-191.8<IP_ADDRESS>10548
  npmPackages:
    react: ~16.9.0 => 16.9.0
    react-native: https://github.com/expo/react-native/archive/sdk-36.0.0.tar.gz => 0.61.4

Library version: 0.26.1
Steps To Reproduce

I have a simple button which, if pressed, it opens the map
after pressing the button the application crashes without logs

Reproducible sample code

Here's my code:
 <MapView style={styles.map}
    showsUserLocation= {true}
    region={{
        latitude: this.state.latitude,
        longitude: this.state.longitude,
        latitudeDelta: 0.3,
        longitudeDelta: 0.3
   }}>
{this.state.dataSource.map(event =>
    <MapView.Marker
      key = {event.id}
      coordinate={{
      latitude: event.location.latitudine,
      longitude: event.location.longitudine,
      latitudeDelta: 0.4,
      longitudeDelta: 0.4
    }}
    title = {JSON.stringify(this.state.latitude)}
    description = {event.description}/>
)}
</MapView>

Did you update any module? Did you run pod install ?

No, should i? What does pod do?
It's weird because i ran the project with an emulator and another smartphone and the problem doesn't appear.

Sorry, ignore me, I didn't see you are on Android.
Try to delete the app form device and try again maybe ?
But I can't help much, this is Expo, and it's somehow outside the scope of this repo

Unforunately deleting app from devide didn't solve the problem. At this point I believe that I will continue to work on another device :joy::joy:

Hello I am using expo and I have the same issue where the rendering of the map causes the app to crash. I am not sure what I have to provide so for now I will just show my package.json and app.js file. Theres some extra stuff like react-navigation.
Package.json
{
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "eject": "expo eject"
  },
  "dependencies": {
    "@react-native-community/masked-view": "0.1.6",
    "@react-navigation/native": "^5.1.6",
    "@react-navigation/stack": "^5.2.13",
    "expo": "~37.0.3",
    "expo-camera": "^8.2.0",
    "expo-image-picker": "^8.1.0",
    "expo-location": "^8.1.0",
    "expo-permissions": "^8.1.0",
    "react": "~16.9.0",
    "react-dom": "~16.9.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz",
    "react-native-gesture-handler": "^1.6.1",
    "react-native-maps": "^0.27.1",
    "react-native-safe-area-context": "^0.7.3",
    "react-native-screens": "~2.2.0",
    "react-native-web": "~0.11.7"
  },
  "devDependencies": {
    "babel-preset-expo": "~8.1.0",
    "@babel/core": "^7.8.6"
  },
  "private": true
}

App.js
import * as React from 'react';
import { Button, View } from 'react-native';
import { NavigationContainer } from '@react-navigation/native';
import { createStackNavigator } from '@react-navigation/stack';
import MapView from 'react-native-maps';

function HomeScreen({ navigation }) {
  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <MapView />
      <Button
        title="Button"
        onPress={() =>console.log('hi')}
      />
    </View>
  );
}

const Stack = createStackNavigator();

export default function App() {
  return (
    <NavigationContainer>
      <Stack.Navigator>
        <Stack.Screen name="Home" component={HomeScreen} />
      </Stack.Navigator>
    </NavigationContainer>
  );
}

An update, since I am using this package for a class project I had one of my group members run the project on an iOs simulator with expo, we received an error about package uuid-js not being installed.  So we ran npm i uuid-js, deleted package-lock.js and node_modules folder, reinstalled with npm install and everything works now.
It seems the key fix was the uuid-js package, although I am unsure what happened to cause it to not be there nor why running the app on an android app just crashes the expo without any errors or warnings.

The problem was solved simply by uninstalling and reinstalling Expo from my device.

closing as solved


fix some compiling waning/error, fix future test

Please, extract the conflicting part and I will do the merge of the non-conflicting parts


Consider renaming ConfigureWebHost and ConfigureWebHostDefaults

Looking at the template now I wonder if we should name ConfigureWebHostDefault => ConfigureWebHost and ConfigureWebHost => ConfigureWebHostCore. I want to use the good name for the meta package and have some other name for the underlying API that isn't really usable without more dependencies (like an IServer). I'd like to get this done for preview3 but if we can't agree on some name then we can move it to preview4.
cc @Tratcher @glennc @muratg

https://github.com/aspnet/AspNetCore/blob/06d7fe73a995000ce79007e03785ee77d4dbb508/src/ProjectTemplates/Web.ProjectTemplates/content/EmptyWeb-CSharp/Program.cs#L21-L26
I like the current names, they're consistent and tell you you're getting a bundle of things.

I don't, should we bring in an unbiased 3rd party?
cc @DamianEdwards

To add to this, the thing that made me second guess the name was the fact that if you try to use it without calling adding a server throws, yet it's the most attractive name just doesn't work by default.

This isn’t a breaking change


feat(forge): add createWallet() cheat code for new Wallet struct

Motivation
Issue https://github.com/foundry-rs/foundry/issues/4790

Solution
Add the struct Wallet to contain its privateKey, addr, publicKeyX, and publicKeyY.
createWallet was added to create Wallet's and sign, and getNonce were also added to as helpers for Wallet

@pmerkleplant what was your original use case for pubkeys? Mainly asking because there's three ways we can represent them, and I'm wondering if we should choose one and you can convert between them as needed (maybe tricky in solidity), or just give all 3 in the Wallet struct (but that feels cluttered)
// Approach 1
uint256 publicKeyX;
uint256 publicKeyY;

// Approach 2
bytes publicKey; // 0x04{x}{y}

// Approach 3;
bytes compressedPublicKey; // 0x02{x} or 0x03{x}

@pmerkleplant what was your original use case for pubkeys?

Our use case is to aggregate public keys, i.e. perform elliptic curve point addition. We also have to derive the Ethereum address of the resulting public key.
We hope that the cheatcode makes our fuzzing test suite faster, in which we receive sets of random private keys and compute and aggregate their public keys.
Therefore, the most suitable approach for us would be the first/currently implemented one, i.e. receiving the x and y Affine coordinates as uints.
I would personally argue against approach 3 as the y coordinate would need to be computed again, making even deriving the Ethereum address computation heavy and error-prone.
@mds1 Out of curiosity, could you elaborate on where approach 2 is coming from? Is this a format standardized somewhere?
@trevorgjohnson Many thanks for the work so far!

Therefore, the most suitable approach for us would be the first/currently implemented one, i.e. receiving the x and y Affine coordinates as uints.
I would personally argue against approach 3 as the y coordinate would need to be computed again, making even deriving the Ethereum address computation heavy and error-prone.

Got it, thanks. I have a use case as part of ERC-5564/ERC-6538 where we may store compressed public keys in a registry, but starting with the x/y coordinates and compressing/uncompressing in solidity shouldn't be too bad, so I'd be ok with moving forward with the current approach for the Wallet struct

Out of curiosity, could you elaborate on where approach 2 is coming from? Is this a format standardized somewhere?

This is a convention from Standards for Efficient Cryptography Group where:

uncompressed pubkeys are 65 bytes (0x04 prefix + 32 byte x-coordinate + 32 byte y-coordinate
compressed pubkeys are 33 btyes (0x02 OR 0x03 prefix + 32 byte x-coordinate, where 0x02 means the y value is even, and 0x03 means it's odd

It's used by popular libs such as ethers.js and noble-secp256k1. You can read more about it and find references to more data in mastering ethereum here

I rebased the current version of `master

Hello @Evalir @mattsse, just wanted to check and see if you guys have had a chance to check out the newest changes to this PR yet. Thanks!

Please add :)

ah whoops, we let this go stale but i think there's still interest here. @trevorgjohnson sorry! mind fixing the conflict to give this a review?

ah whoops, we let this go stale but i think there's still interest here. @trevorgjohnson sorry! mind fixing the conflict to give this a review?

No worries! The conflicts should be resolved in d7bcc7d

Amazing! just need forge-std PR + book update


Widen extended commit message under "..."

Use all available width for extended commit message under "..." instead of GH's 770px:

Changed to none.


Reference block time may be invalid

Location: funder.go, timeout.go
When we fund, we wait for blocktime + challengeDuration before we cancel the context. In some situations this can cause unwanted behavior. For example, when the block tick time is larger than the challenge duration, the BlockTimeout is immediately canceled with the next block, even it the next block arrives within the expected time frame.

The challenge duration should always be at least 3 block-times. Otherwise the user risks losing funds.
This looks more like incorrect usage to me.

@ggwpez  After thinking about it, I agree.
However, the restriction on the challenge duration is not self-explaining and also not checked by the framework. Do we document it somewhere?


Vugel support for Vite

This looks really interesting and works great, but only webpack is supported via vue-loader. It would be great if it could work with Vite.
Thanks

Hm, to use Vugel you need to use a custom compiler, so it would depend on being able to register a custom compiler for Vite

Thanks @RobbinBaauw I have also created an issue on vite side. Is compiler=xxx syntax supported currently or is this something unofficial? I know of custom block support in both Vite and Vue-loader, but couldn't find any reference to custom compiler support.

This is added in the following PR: https://github.com/vuejs/vue-loader/pull/1645
Didn't know of custom blocks, am trying to figure out a way to make it possible that way! I'm almost there

Added ESM support :)

@RobbinBaauw great stuff. Now when you made it work with Vite via  custom block  is this better than original <template compiler=xxx? It seems that this is closer to existing standards and hence we can get away without adding additional vue/vite level constructs.

I don't think so. The way I implemented this custom block (for now only for Vite but it should be doable similarly for vue-loader) is by overwriting the render function. I think this is quite a hack, if you for example add a <template> block this will fail. A much better way would be to override the compiler of the component, but this is not possible with custom blocks because you can only emit code, which means that you can't pass references to such compiler.
Another issue is a bit less fundamental: I had some ESM problems with Vue (same as in my last comment), so I made it a hardcoded path. I don't have the time nor enough knowledge on ESM to improve this currently. Any ideas?
To conclude: for development with Vite this should be plenty, but when actually putting an app in production I wouldn't really want to use this, hence I hope the vue-loader thing is going to get merged and a similar setting for Vite might be better too.

Something like this could also work: https://github.com/RobbinBaauw/vite/commit/9f76f26eafb1267f25485fac5e52b856627a789b

@RobbinBaauw this is really cool stuff. Will be good to discuss both these approaches on Vite repository and probably worth to proceed with pull request to get more feedback.

@RobbinBaauw Seems like we have a green light now. Support for custom compiler options have just been added to vite and it's rollup plugin. Here it is.

Great! Then we have https://github.com/vuejs/rollup-plugin-vue/pull/368, https://github.com/vuejs/vue-loader/pull/1645 and https://github.com/vitejs/vite/pull/488

Closing, feel free to reopen if you have any more questions.

@RobbinBaauw will be probably also great to get the example you had reimplemented with new way provided by latest vite change, to make sure all holds together and nothing was missed. I have used that example yesterday to put some basic demo together, but was stuck with broken v-for. Hopefully, with this there will not be such issues.
i have to say, this is all really amazing stuff. I was overjoyed when managed to get vugel working in my simple vue-vite demo yesterday. To have both DOM/Canvas/WebGL updates controlled by Vue reactivity this opens huge amount of new possibilities. Once this becomes stable I am sure there will be plenty of applications using this. Currently to make canvas changes in Vue application is like taking cold shower, you have to leave comfort of data binding provided by vue and do things old way. This will allow for the same DSL used for DOM by Vue to be used also for Canvas/WebGl. Really shows power of Vue3 and also have to say Tree2D/Vugel seems to be very fast. Kudos to everyone who made this possible @RobbinBaauw, @basvanmeurs, @yyx990803,  @underfin and everyone else.

I think we can convert our example repository to Vite once https://github.com/vitejs/vite/pull/488 gets merged. You can see our current webpack config there as well.
It is indeed very fast, we are using it internally to build a new product (which is where most of the testing of Vugel will come from, as we don't have a test suite on this repo) and we have been surprised as to what is possible.

Hi guys! I'm working on making a Pixi.js renderer for Vue. Since it's very convenient to have HTML + canvas rendered within one app, it should work with HTML elements.
These PRs you listed seem very helpful, just they're not merged for a very long time. Is there anything moving on there?

It seems that you'll have to write your own plugin for Vite: https://github.com/vitejs/vite/tree/main/packages/plugin-vue#options

Thanks, will check it out :+1:


Hide pause, fast forward in UI

Is it possible to hide these buttons already?

The dev builds at the link below have an autohide feature you can enable in the settings.
https://github.com/skylersaleh/SkyEmu/pull/143
When it is turned on, the buttons will auto hide when playing a game if there is no other panels open. Let me know if that is what you are looking fo.

It is! Thank you!


Fix clippy lints and a compiler warning

Clippy lints fixed automatically using cargo +nightly clippy --fix -Z unstable-options
Compiler warning was:
Compiling swaywsr v1.1.1
warning: derive helper attribute is used before it is introduced
  --> src/config.rs:12:3
   |
12 | #[serde(default)]
   |   ^^^^^
13 | #[derive(Deserialize)]
   |          ----------- the attribute is introduced here
   |
   = note: `#[warn(legacy_derive_helpers)]` on by default
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #79202 <https://github.com/rust-lang/rust/issues/79202>

Thanks for the PR!


Convert all wrong type return JSON to specific type

Say I am facing this situation: The server might somehow return a wrong type from server, eg, Int,
How can I force cast the wrong Int type into the correct String type?
In my case, I will get an typeMismatch error, when running into the second decoded object.
Error Messages
List all the error messages or warnings you are seeing, if any.
Sample JSON
{"result":
[
    {
      "title": "Title1",
      "balance": "1234" // or somehow might be 1234
    },
    {
      "title": "Title2",
      "balance": 1234
    }
]}

Models
All models involved, including their Decodable implementations.
struct User {
  title: String,
  balance: String
}

extension User: Decodable {
  // ...
}

Argo Version
_example: Argo 4.1.2
Dependency Manager
examples: Carthage, Cocoapods, git submodules, copied code, etc.

Ideally this shouldn't happen. If you control the API you should definitely try to ensure that objects are sent back with a consistent type for a specific key.
That being said: You can handle this on the client side by leveraging Alternative. In your case, if you want to store the result as a String, it's fairly straightforward because you don't need to handle potential failures when converting to Int. Maybe something like:
// this can be put wherever you want, based on preference
extension Int {
  static func toString(_ int: Int) -> String {
    return "\(int)"
  }
}

extension User: Argo.Decodable {
  static func decode(_ json: JSON) -> Decoded<User> {
    return curry(User.init)
      <^> json <| "title"
      <*> (json <| "balance") <|> (json <| "balance).map(Int.toString)
  }
}

FWIW, you could use String.init(describing:) too:
(json <| "balance").map(String.init)

oh yeah right sure

Closing now. Thanks!

@gfontenot Oh I figure out the alternative operator <|> need to wrap a parenthesis to work around.

Ah, yeah, I still don't have a great mental-model for the operator precedence (which is why I'm proposing removing some of them)


Identity state not synching across tabs

Repro -

2 tabs open Arcade home page, and a Skillmap (neither logged in)
Go through the entire Skillmap and complete it (to earn the badge, but don't log in)
On the Arcade home page tab, log in
Go to Profile page

Behavior - don't see the recently completed Skillmap badge in User's Profile
Expected behavior - should know this is the same user who has completed the Skillmap in the other tab
Workaround - refreshed the Skillmap tab and showed logged in user, then refreshed the Arcade Home page tab, then badge showed up in User Profile.

@eanders-ms this should be fixed by the latest skillmap sync fixes right?


🐛(eleventy-plugin-local-respimg) Respect loading attr set on  tags

Also updates tests

Closes #31

👋 @Snugug Could you check this PR and make a new release if things are okay?

Sorry, between the holidays and personal stuff the past couple weeks got away from me. Will look at everything Monday

Sorry for the delay on this! Was launching http://chromeos.dev/ which ate my time on this. Back on this, now, though.

Thanks @Snugug for merging. It would be great if you could publish a new version of this plugin.

Hey @Snugug nudging to make a release. 🥺  The last release on NPM was in June.


add item-view layout for alarm

The item view is split into two rows:

TOP ROW (with a width greater than the bottom row)
1) Time of the alarm on left.
2) A toggle button on the right.

BOTTOM ROW
1) Left side has 7 letters - SMTWTFS
2) Right side has a kebab menu ( triple vertical dots menu option)

Hey, can I take up this issue?


Add issues template

I would like to add a issues template in this repository. I believe that having a standardised template will help streamline the contribution process, ensuring that all necessary information is included and making it easier for maintainers to review issues.
Could you please assign this issue to me under GSSOC'24.

Go for it @suhanipaliwal

Please assign this issue to me. You still haven't added me as the assignee.


mgmt, upgrade trafficmanager 2022-04-01

live test pass
manual code https://github.com/Azure/azure-sdk-for-java/commit/7bf3d59f72b2ba06f5a6e8039e232e2023023a05
Rename swagger EndpointType to EndpointTypes, as it conflict with our handwritten enum class.
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

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


Sort filter drop down with Intro first.

A while back we resorted the filter drop down to be in alphabetic order.  This puts "Intro" records at the bottom of the filter drop down list.  Users would like "intro" to come at the beginning of the list
DoD:
When filtering "Intro" comes at the top of the dropdown instead of the bottom of the list.
Details:

Looks good in  - v1.10 build 228-f43ba9b.


Feature suggestion: treat prototype assignments like merging type declarations

I would like better native support for code of this nature:
function impl1() { // implementation A for myVirtualMethod
    this.x = 1; // this is treated as global object or any
}

function impl2() { // implementation B for myVirtualMethod
    this.y = 1; // no type-safety, compiler doesn't know what 'this' will be bound to.
}

export class Base {
    public myVirtualMethod() {}

    public x: number;
}

export class Derived1 extends Base {
    // can't assign function to myVirtualMethod here to override method
}
Derived1.prototype.myVirtualMethod = impl1; // override method with function

export class Derived2 extends Base {}
Derived2.prototype.myVirtualMethod = impl2; // override method with function

The code above works, but has a couple of drawbacks, which I think are resolvable:
The compiler has no way of knowing what this pointer should be in impl1 and impl2

I would like a way to redefine what type this is for functions.
It would also be nice if the compiler could detect if this contract is not honored (e.g., the function is invoked without a receiver, or is assigned to a method on a class which does not match the interface)
Possibly infer an interface for the receiver of the function if none is declared

Possible syntax:
function impl1() overrides Base.myVirtualMethod {}
function impl1(): this implements Base {}
function impl1() { const this: Base; }
The compiler won't let you define a method by assigning a function, so you must assign to the prototype instead

It may be nice to have a way to designate that certain properties are intended to be assigned to the prototype, from inside the class body
I would like way to declare a method but define the body through assignment

Possible syntax:
public myVirtualMethod() = impl1; // Parentheses distinguish this from a property assignment.
public myVirtualMethod() = null; // pure virtual method (runtime error to invoke, no compile time check)
Type checking:
impl1(); // Type error: Window does not implement { x: number }
this.y = 1; // Type error: Base does not implement { y: number }
public myVirtualMethod() = impl2; // Type error: Derived1 does not implement { y: number }
impl2.call( new Derived1 ); // Type error: Derived1 does not implement { y: number }

Sounds like a combination of several dupes: #229 #3694 #3442

@kitsonk Fair enough for #229 and #3694.  #3442 refers to overloading instead of overriding, so I think it's different.
I don't see the second part, "override by assignment," in any of those.

Ah, I see, you then are looking for mixins/traits (#311) or some sort of abstract class (#6, #2947).  The way you are doing it, by directly modifying the prototype will mean the current scope is always a bit of a challenge.

I want:
function bar() {}
class Foo {
  public bar() = bar;
}

to have the same output as
function bar() {}
class Foo {}
Foo.prototype.bar = bar;

Along with the benefits of type checking.  I think the scope is much smaller than some of the other proposals.  No new keywords: it's basically sugar for something that already works.  To make type checking easier, there can be a requirement that the value assigned must be a compile-time constant.
The assignment might reference a function, a static method of another class, or null or undefined (thus implementing a "pure virtual" method).  It may override a method of a parent class or it may be a new method altogether.

The request here is to essentially make directly assigning to .prototype analogous to an actual type declaration as far as type checking is concerned.

In theory, if it is reasonably achievable in typescript, it solves some of the issues around "natively" supporting Mixins and Traits (as well as Decorators would modify the type declaration, which they don't currently).
@danquirk do you think a reasonable proposal has a chance?

@kitsonk I haven't really chatted with anyone else on the team about this in depth yet so I don't want to make any promises I can't keep :)
At first glance this is definitely a bit outside what we normally do as far as flow control based semantics and such but it does serve a real use that many people would benefit from. I wonder how much ES6 classes will eventually obviate the need for direct prototype assignment in new code (obviously that still leaves a ton of existing JS that could benefit from this). Some might argue this sort of code is on the more dynamic side of the world which we generally try to allow but don't always support incredibly well (ex dynamic assignment/expandos typed as any).

On the other hand, the work we're doing in the JS intellisense branch to pick up define and require calls (in non-TS code) might set a good precedent for how these things might work in the future.

I wonder how much ES6 classes will eventually obviate the need for direct prototype assignment in new code (obviously that still leaves a ton of existing JS that could benefit from this).

@danquirk yes, but you might assuming that ES Classes will support the right sort of design patterns.  I for one remain unconvinced that ES Classes will head the direction everyone wants to go, and even then, it might take a while to get something agreed.
I know TypeScript is trying to do its best to be "future proof" and not meddle in things that might break in the future, but I suspect having a mechanism of extending the typing of a prototype won't interfere with future standards and get a lot of us who don't believe traditional OO inheritance is the right pattern off your backs. :wink: If we wanted to do composition, or traits, factories, or whatever, we could be the "Wizard of Oz" behind the curtains to ensure that our downstream consumed code was type safe.

Right, my concern here re:ES6 was not really future incompatibility and just musing on the general ROI of any work here if we expect people to move to ES6 classes in short order. There's definitely some opportunity here for TypeScript to just infer the right thing from a pattern that people are already commonly using, although as far as things like traits and mixins I'd prefer something a little more explicit/declarative than a mess of prototype assignments magicing up a type somewhere.

@danquirk I would too, but #311 is closed. :cry: The main reason was, if I understand correctly "we are going to wait for ECMAScript to take the lead..."  It is hard to wait for TC39 to try to use and deliver other design patterns.
But if this sort of "modifying the prototype type" were allowed, I, as a middle man, could produce some of this functionality... I will admit @bryanforbes and I have been doing a lot of thinking about composition, factories, traits and mixins for Dojo 2.  While union and intersection types will help us out, being able to modify the type of the prototype, would make it challenging for us, but we would be able to deliver a clean API that allowed use of the pattern without breaking TypeScript.

We've implemented this for JavaScript, but don't see a need to do it for modern TypeScript code. Many better alternatives exist


Propagate Django Admin customizations

If the user of the application customizes various aspects of the Django Admin site through variables like site_header, site_header, etc. (see Django Admin docs) these customizations get lost on the Constance Admin pages. Constance does not pick up these customizations and the Admin templates revert to defaults.
Django Admin includes a function called each_context which:

Returns a dictionary of variables to put in the template context for
every page in the admin site.

This patch uses each_context when building the context for the changelist_view function. This way, Django Admin customizations get propagated to the Constance Admin pages.
This patch also changes the way the context dictionary is built, from using the {} syntax to using the dict syntax. The dict synatax facilitates the use of each_context directly when building the dictionary. This is consistent with its use in Django Admin, see here, here, and here.

👍


Unclear tutorial paragraphs

"Now this is another story: this time choose' is a Transient primitive. It stops the current thread and launches a new thread for each of the elements in the list. Since the main thread dies, the computation could finish before the launched threads complete. This is the reason for the name "transient": because it manages transient threads. This is why it is called keep. It prevents the program from exiting when the main thread dies. exit escapes the keep block."

Exit is just an identifier, right? So what actually escapes? And why can the computation only finish because the main thread dies?

"In this applicative expression, both async operations run in parallel, within different threads. When the first finishes, it inspect the result of the other. If it has no result yet, the inspecting thread stores its result and dies. When the other thread finishes, it sees the result of the previous one. Then, it completes the applicative expression and prints the result. The computation brought to async runs in the IO monad:"

Too many words are used to identify threads here, including "other", "inspecting thread" and "previous one". This paragraph would benefit from a sequence diagram.

"It produces the same result, but this time, the original thread is the one that runs the IO computation of the second term, instead of dying."

What is meant by "original"? Why not just say "main"? Also, why call it "second term"? It could be given a name and it would be easier to refer to.

"Actually, a Cloud computation is a transient one, with a very thin layer that assures that the type system makes the program aware of the need to log and recover intermediate results, in order to re-create the closures at the remote node."

The last sentence is very complicated, and  how can the type system tell any program anything? Does the Cloud cloud monad force logging? If so, this sentence could be made simpler.

"Unlike Cloud Haskell and other distributed frameworks that use static closures, Transient distributed programs don't need to be identical in all nodes, neither do the nodes have to share the same architecture. It is enough to share the same snippet of code that is called."

What is meant by architecture? CPU architecture?

Thanks. These comments are invaluable. I want to make it as clear and precise as possible. If possible for beginners.  I have made the changes. Can you verify that they are ok?

Yep, looks better.


[#748] adding a single yaml for installing operator

@howardgao providing a single yaml for installling the operator is a very good feature. Strmizi also has a similar feature, it has an endpoint do dynamically create  a single yaml, see https://strimzi.io/quickstarts/:
kubectl create -f 'https://strimzi.io/install/latest?namespace=kafka' -n kafka

The latest endpoint is defined in https://github.com/strimzi/strimzi.github.io/blob/main/.functions/namespace/namespace.js
A static single yaml has the following drawbacks:

another static file to check and update
we would need one for namespaced installations and another for cluster installations

i may have this wrong, but was the default from the sdk to create a single yaml and we had some scripts to split it up? It looks kike we now have a script to put it back together?

By default, operator-sdk init scaffolds a cluster-scoped operator and only provides the Makefile target deploy to deploy the operator to a K8s cluster, see https://sdk.operatorframework.io/docs/building-operators/golang/operator-scope/
I see your points, a single yaml for cluster-scoped operator makes sense.

i may have this wrong, but was the default from the sdk to create a single yaml and we had some scripts to split it up? It looks kike we now have a script to put it back together?

Yes it basically comes from the sdk make target, we only need to output it to a single static file for easy access. (for local dev you can just use make deploy to deploy a cluster-scoped opr in one go)


decision tree ?

Hi @pymacbit, thank you for you contribution. There appears to be a conflict - perhaps your MR is based on an outdated fork? Will you be able to resolve it?

Just resolved it. Have a look on it.
On Fri, 10 Apr 2020 at 11:47, Alexey Grigorev<EMAIL_ADDRESS>wrote:

Hi @pymacbit https://github.com/pymacbit, thank you for your
contribution. There appears to be a conflict - perhaps your MR is based on
an outdated fork? Will you be able to resolve it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexeygrigorev/data-science-interviews/pull/56#issuecomment-611896538,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHEQOR32OGIVR5IGSSPTXKTRL22ZDANCNFSM4MFBMIMA
.

Thank you!

Thanks you :) , Looking forward to contribute more.
Have a nice day. Stay Safe. TC
Regards,
Yatindra
On Fri, 10 Apr 2020 at 11:59, Alexey Grigorev<EMAIL_ADDRESS>wrote:

Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexeygrigorev/data-science-interviews/pull/56#issuecomment-611899584,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHEQOR2ITYSNU5DL3WZHIBLRL24EHANCNFSM4MFBMIMA
.


[Feature] Add index file for components folder

This will make it possible to export compound components via the IDE.
Using Select as a example, by default it can be exported like this
import * as Select from '~/components/ui/select'

But we can move on to named exports with index.ts re-export approach:
~/components/index.ts:
export * as Select from './select';

Usage anywhere now:
import { Select } from './components/ui'

@Xelson
In v.0.7.0 the CLI will handle index files. Please give it a shot.


Added Shrewsbury High School GDST

@cgodbold lib/file/lib/domains/net/gdst/shr.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@cgodbold First stage of verification passed, official domain is shrewsburyhigh.gdst.net as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://shrewsburyhigh.gdst.net/

@cgodbold Thank you for your patience while waiting for a review and processing your request. Pull request merged.


charmap encoding issue

when trying to use russian
log
Traceback (most recent call last):
File "", line 198, in run_module_as_main
File "", line 88, in run_code
File "D:\Scripts\pyvosklivesubtitle.exe_main.py", line 7, in
File "D:\Lib\site-packages\pyvosklivesubtitle_init.py", line 3982, in main
partial_result_file.write(text)
File "D:\Lib\encodings\cp1252.py", line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_table)[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
UnicodeEncodeError: 'charmap' codec can't encode characters in position 0-3: character maps to

I fixed this problem by changing my system's default encoding to UTF-8


Design polishes part B

[x] Workspace card, menu few pixels smaller and badge slightly bigger than menu
[x] Update terminal icon from mock, get svg from Lou
[ ] Update terminal icon on left side menu (EDIT from Liz: is this a good idea? Should users be able to access the terminal outside of a workspace?)
[x] 'Built on' sizing and color
[ ] Autofocus needs blue outline when active, first active
[x] Vertically align the workspace title and description in list view
[x] When cloning workspace, move info about inherited auth domains below Auth Domain, move info about Auth Domain inheritance below drop down - Show to Lou
[x] Workspace clone button in menu, update icon to menu
[x] Menu in workspace summary have same three dots but in white

Also added design updates to left nav bar (fixed margins, font weights, and naming to match invision)

Edit: removed adding terminal access to left side menu after consultation with Brad


QueueIter returned by Device::new is confusing

Currently Device::new returns a QueueIter which is documented as the queues produces when creating a device. However it seems that the iterator is just the first queue in the queue family used to create the device. Is it intended to be this?

I'm not sure where the confusion is. Creating a device generates queues, and this iterator returns them.
Right now all the examples only use one queue, so obviously the iterator only returns one element.

Currently vk::DeviceQueueCreateInfo's queueCount attribute is priorities.len().
priorities is defined only once for each queue family, which means the queueCount for every queue family is only one. How could I ask for multiple queues for every device created?
Maybe I misunderstood something?

So I think the queue_families param of Device::new should be having type of I: IntoIterator<Item = (QueueFamily<'a>, Vec<f32>)> ?

If you want multiple queues from the same family, you're supposed to pass the same family to Device::new() multiple times.
Eg. Device::new(..., vec![(my_family, 1.0), (my_family, 0.5)]);

Wouldn't passing the same family multiple times return the same queue (the first queue in the family) multiple times? I thought that vkCreateDevice returns different queues from a family, each assigned with a priority

BTW it seems to be not recommended to feed multiple vkDeviceQueueCreateInfo with the same queue family.
https://www.reddit.com/r/vulkan/comments/4nb5jx/why_does_initialization_fail_here/?st=j4fbt66d&sh=bb671eab

Maybe what's confusing is that vulkano's API is higher-level than the raw vkCreateDevice: https://github.com/tomaka/vulkano/blob/24fe5b18975c401d70f1aecf444317fc49a5c2f7/vulkano/src/device.rs#L205-L243
It was designed this way so that the elements of the iterator returned by Device::new match the elements of the iterator passed to the function.

oh, I finally understand the code here.... Maybe some documentation is needed here. Thanks for your quick explanation.


closes #2: atomic file save with backup

Implemented per request using rename.
As implemented, it also create netrc.### backup files before saving in addition to the tempfile.
Behavior easily disabled by passing , false to atomic_write.

Run options:

# Running tests:

....................................

Finished tests in 0.271142s, 132.7718 tests/s, 199.1576 assertions/s.

36 tests, 54 assertions, 0 failures, 0 errors, 0 skips

Closing due to inactivity and due to no longer merging cleanly. Please re-open if you'd like to revisit.


Add RPi assets post Dockercon

Hi @ManoMarks ,
I had a request from @jrburcio to link out to the RPi workshop I put together for Dockercon. I've also had lots of interest around Docker and the RPi recently so wanted to put together some core links to help people get started.
(All of the linked posts are in a lab/tutorial format.)
This was the "5 things" post over the weekend:
https://twitter.com/alexellisuk/status/863380405680001024
Alex

Hi Alex,
Since these are all hosted external to the Labs repo, let's instead put them on the /README.md under Community tutorials. In the future, if we come up with a larger set of community tutorials we want to link to, we can create a separate categorized page.

Hi @ManoMarks  No problems, I've made the amendments and re-pushed.


add sensitive option to galera cookbook resources

https://github.com/sinfomicien/mariadb/blob/v0.3.0/recipes/galera.rb#L120
This FC issue is now closed and merged : https://github.com/acrmp/foodcritic/issues/233
please add sensitive where it needs to be :)
Thanks for this cookbook !

I just put in a PR for this, I also added sensitive to the preseed template resource since it has root passwords as well, can you take a look a the PR and see if there are other resources that shout have the sensitive flag set on?

Seems the foodcritic i use in Travis is not supporting the feature. If the latest Gem is OK, could you (@Rockstar04) update the Gemfile to the good version (So foodcritic will not warm in Travis).

Fixed, sensitive property has been added where appropriate.


fix: correct sass options for sass-loader 8

When using<EMAIL_ADDRESS>the Nuxt defaults will break it's usage due to a validation error.
ValidationError: Invalid options object. Sass Loader has been initialised using an
options object that does not match the API schema.
 - options has an unknown property 'indentedSyntax'. These properties are valid:
   object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? }

That's because the API has changed and distinct sass options are no top-level keys anymore but belong into the sassOptions object.
Problem: This will likely break sass-loader<=7.x.y
What should we do regarding this issue?

Add a note that we implicitly bump sass-loader to ^8.0.0? (We can't control that)?
Grab the version of the installed sass-loader and set the defaults based on it?
Add a note that ppl using<EMAIL_ADDRESS>have to update the stuff on their own?

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly. (PR: #)
[ ] I have added tests to cover my changes (if not applicable, please state why)
[ ] All new and existing tests are passing.

Related
https://github.com/vuejs/vue-cli/issues/4513

Grab the version of the installed sass-loader and set the defaults based on it?

That could be NICE!

Codecov Report

Merging #6460 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6460   +/-   ##
=======================================
  Coverage   95.61%   95.61%
=======================================
  Files          79       79
  Lines        2693     2693
  Branches      697      697
=======================================
  Hits         2575     2575
  Misses        101      101
  Partials       17       17

Flag
Coverage Δ

#e2e
100% <ø> (ø)
:arrow_up:

#fixtures
50.64% <ø> (ø)
:arrow_up:

#unit
92.31% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

packages/config/src/config/build.js
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Thread related mobile APIs are thread name based

This makes the assumption that thread names are unique. I don't think we can assume that once we launch shared threads. These APIs should be thread id based.

Also makes me think we should add an isDefaultThread to the Thread or ThreadItem object so we can identify which thread is the default one.

Hmm, actually no. A 'default' thread is a concept of the mobile app, we should put that state there, not in the Go layer. But that leaves the question, what if you delete the app, then re-install and recover your textile wallet in the future? How would we know which thread is the default thread?

Maybe we need the option for the client (the app) to specify the thread id when creating the thread. This messes up the use of public keys as thread id, but re purposing the public key like that is a fragile idea because of use cases like this.

pasting from slack for posterity:
Might be easier to chat about this but you can create a thread with a mnemonic or private key, but not public
That would cause issues
Also there’s a unique index on name
But doest have to match between peers
It’s sorta cosmetic - not important part of a thread
Was thinking that if you have to recover, you just get some generic naming like thread1 thread2 etc
Then some ui to rename your stuff

So if I'm invited to a thread that has the same name as a thread that already exists on my phone, I'll have to rename one of them?


Allow vector arguments to contain negative numbers

Without this PR, you can't use negative numbers in a Vector2 argument, for example, (-2, 1) will give this error:
ERROR: Failed to parse vector argument: Bad formatting: "(-2, 1)"

However, with this PR it works!

Looks good, thanks!


[TC-LWMS-3.1] SDK has to be implemented for LaundryModeSelect Cluster

Summary:
All-clusters-app has to be enabled with below mentioned Command :

[ ] ChangeToMode

All-clusters-app has to be enabled with below mentioned Attributes :

[ ]  SupportedModes
[ ]  CurrentMode
[ ]  OnMode

GitHub hash of the SDK that was being used
https://github.com/project-chip/connectedhomeip/commit/fa07cc9b30478d5f481db486507d738fae124017
Platform
raspi
Platform Version(s)
RPI - 4, 8GB RAM

Duplicate of combination of https://github.com/project-chip/connectedhomeip/issues/27232 and https://github.com/project-chip/connectedhomeip/issues/27772


A question on theme support

I tried to implement a "dark theme" by setting up the primary, secondary and background color like described here: https://material.io/develop/web/theming/color
But the $background variable is ignored in aurelia-mdc and the application keeps still "light".
@use "@material/theme" with (
    $primary: #f00,
    $on-primary: #ff0,
    $secondary: #f0f,
    $on-secondary: #0ff,
    $background: #333,
    $surface: #aaa,
    $on-surface: #0f0,
);

The bridge does not do anything with styles. I've applied the theme above to the demo app and the background does get set to the variables

I had a brief look at the MDC sass files and the background is not used anywhere, I think you are supposed to set it manually on the controls you need
    background-color: var(--mdc-theme-background);

It looks like the whole mdc theming is broken.

It doesn't follow the documentation. Defining $text-primary-on-light fails, but described at "Material theme keys with theme.property()"
in _theme-color.scss is defined

$on-surface: if(contrast-tone($surface) == 'dark', #000, #fff) !default;

which would result on a black color on a dark surface, which doesn't make any sense.
3.
.body {
    background-color: var(--mdc-theme-background);
}

doesn't work for me.
I'm currently unable to support a dark theme without deeper unterstanding of the material theme or manually overriding a lot of styles.

Perhaps, MDC repository would be a better place for this question as I doubt many eyes will see it here.

Yes you are right. I just want to know if anyone was able to create a dark theme.
I created a bug ticket here: https://github.com/material-components/material-components-web/issues/7340 and it looks like that many people having issues with that.


train pretrained model from scratch

Hi, I have 150 hours of clean audio at 44 kHz in MP3 format, featuring multiple male and female voices. I would like to train a pre-trained model from scratch.
Do I need to split the audio by different voices and include transcriptions, or can I train the pre-trained model directly without splitting and transcriptions?
Thanks!

answered on discord


Use spx nuget package for all workflow operations, replace insecure s…

…et-env usage

Is there test report summary ?

      creds: ${{ secrets.AZURE_CREDENTIALS }}

This is fine for now, but long term we might want to look at a different way.
For other Azure CLI tasks I have used, they use the name of a "service connection" that defines the credentials to you.
We might want to update our YAML task to use the same way.
Either way, I think there is something we are suppose to do at the end of our yaml file to sign out and clear these cached credentials, so that you're not left signed into Azure after your agent a release back to the agent execution pool.

Refers to: .github/workflows/speech-train-data-ci-cd.yml:76 in 0ec0047. [](commit_id = 0ec0047c41950e264b3de85cf7637e852722a69b, deletion_comment = False)

Is there test report summary ? I am asking because it is difficult to say how the changes actually work

@jhakulin For this example run I've attached the test result file
example_test_result.txt


Continuous login

Thank you for the great plug in.
I have a question. I get continuous log in notifications in the log:
e.g.
[2018-12-12 15:00:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:00:17] [Security System] Logged into Alarm.com as ...
[2018-12-12 15:11:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:11:17] [Security System] Logged into Alarm.com as ...
[2018-12-12 15:22:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:22:17] [Security System] Logged into Alarm.com as ...
[2018-12-12 15:33:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:33:17] [Security System] Logged into Alarm.com as ...
[2018-12-12 15:44:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:44:17] [Security System] Logged into Alarm.com as ...
[2018-12-12 15:55:14] [Security System] Logging into Alarm.com as ...
[2018-12-12 15:55:17] [Security System] Logged into Alarm.com as ...
Is this operating as expected or is this not to be expected? And if not, any ideas where I should look to stop this behavior?
Thank you.

This is partially expected. I need to see about turning these off in the logs. However you will also notice this with the Alarm.com native app as well, it will show that the you are logging in from the web, over and over again.

Yes, I see that in the app. Is this because the plug in has to continuously ping the back end?

Yes. It does this about every 10-11mins.
As noticed from trial and error with the Alarm.com web api, we have these constants initially set in the plugin code:
const AUTH_TIMEOUT_MS = 1000 * 60 * 10 // (milliseconds * seconds * minutes)
const DEFAULT_REFRESH_S = 60 // (seconds)

Authentication & Polling Process:

We authenticate with the API and get a session ID that is supposed to be valid for roughly 10 minutes, then it becomes invalid (so we set a 10 minute timer).
Then, using the session ID, we poll every minute for device changes (we try to not do this too often as we can get flagged as spamming the api servers).
If the poll command checks that the 10 minute timer is done, we need to reissue a new session ID and continue polling.

I finally got some time to update the plugin with regards to hiding messages in the logs. There were some initial efforts from the original FrontPoint code to configure the polling interval time, however I have expanded it to include the authentication timeouts as well. Please use with careful discretion as this could possibly flag your account for API hammering and disable the endpoints altogether.
Please see the readme for the new additions on how to configure the polling as well as how to change the level of logging to hide the entries in your logs.

Thanks mike. Will this reflect in NPM as well?
On Dec 23, 2018, 11:03 PM -0500, Mike Kormendy<EMAIL_ADDRESS>wrote:

I finally got some time to update the plugin with regards to hiding messages in the logs. There were some initial efforts from the original FrontPoint code to configure the polling interval time, however I have expanded it to include the authentication timeouts as well. Please use with careful discretion as this could possibly flag your account for API hammering and disable the endpoints altogether.
Please see the readme for the new additions on how to configure the polling as well as how to change the level of logging to hide the entries in your logs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes. I have now released it as an update.


fixed issue 3407 - module doc for qiskit.quantum_info

Summary
Fixes #3407
Details and comments
Added module-level documentation to qiskit.quantum_info by updating qiskit/quantum_info/init.py. Added short comments and one or two examples for each class.

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

I've got the error below when running the check on qiskit-terra. Any suggestions on how I could resolve it? Thanks!


Azure Compute SDK Changes for ProtectedSettingsFromKeyVault

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Hi @kamusta-msft , could you please fix the failed tests?

@Yao725
I ran the tests locally and they pass. failing with:
System.Collections.Generic.KeyNotFoundException : Unable to find a matching HTTP request for URL 'GET /subscriptions/e37510d7-33b6-4676-886f-ee75bcc01871/providers/Microsoft.Compute/locations/eastus2euap/publishers/MicrosoftWindowsServer/artifacttypes/vmimage/offers/WindowsServer/skus/2012-R2-Datacenter/versions?$top=1&api-version=2021-11-01'. Calling method Item().

/azp run


pipe-rename: 1.4.0 -> 1.4.1

Motivation for this change
https://github.com/marcusbuffett/pipe-rename
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 147765 run on x86_64-linux 1

1 package built:

pipe-rename


Macros?

Should there be macros so programmers can extend the syntax?

Almost definitely yes.
Any ideas on how to go about implementing this? I'm thinking a sort of macro header at the beginning of a program describing how the AST of the real program should change.

Any ideas on how to go about doing this? I'm thinking a sort of macro header at the beginning of a program describing how the AST of the real program should change.

I'm not sure what you mean. But you could do something like having a macro be a function which takes some AST stuff as input and returns some AST stuff.

Right, so I'd do something like this:
macros${
  transform(arr('VARIABLE_IDENTIFIER', 'yield'), {
    return(arr('FUNCTION_CALL', arr('VARIABLE_IDENTIFIER', 'sleep'), 0);
  });
$}

Which would transform this:
print('Hello');
yield;
print('World');

Into this:
print('Hello');
sleep(0);
print('World');

(Of course, that's not a good use case of yield, but I don't feel like copying and pasting my yield example -- see this.)
Maybe you could also have something like this:
macros${
  transform(arr('VARIABLE_IDENTIFIER', $any), { # ... # });
$}

In which $any is an (environment) variable defined by Tulun before running the macros. It represents that a VARIABLE_IDENTIFIER that is followed by anything should be modified by this script.
And then you could have more complicated things like arr('FUNCTION_CALL', arr('VARIABLE_IDENTIFIER', $any)), etc.
But I think it'd be good to start with what the example at the top.

Speaking of which, there should be a funtion parse or getAST or something like that which takes a string and parses it into an AST like Tulun would.
That way you could replace the above with
macros${
  transform(getAST('yield'), {
    return(getAST('sleep(0)'));
  });
$}

Probably wouldn't be terribly difficult to do, either! See this: https://github.com/liam4/tlnccuwagnf/blob/master/src/run.js#L7-L11


BUG: A feature is missing in the result of force_plot

Issue Description
The number of parameters in 'featureNames' and the number of parameters in 'features' do not match. To be more precise, one feature is missing exactly as a result of plot.data.
Everything works fine until this point. I can't understand what can be the problem.
Minimal Reproducible Example
import shap

explainer = shap.TreeExplainer(loaded_model.named_steps['trained_model'])
train_full_pipe = loaded_model[:-1].transform(cleaned_dataset)
shap_values = explainer.shap_values(train_full_pipe)
idx = 0
plot = shap.force_plot(explainer.expected_value, shap_values[idx,:], train_full_pipe.iloc[idx,:], link='logit')

>> plot.data

{'outNames': ['f(x)'],
 'baseValue': -3.3778029260784237,
 'outValue': -3.2176744023008674,
 'link': 'logit',
 'featureNames': [...], #shape=133
 'features': {...}, #shape=132
  'plot_cmap': 'RdBu'}

train_full_pipe.iloc[idx,:].shape
>> (133,)

shap_values[idx,:].shape
>> (133,)

### Traceback

_No response_

### Expected Behavior

_No response_

### Bug report checklist

- [X] I have checked that this issue has not already been reported.
- [X] I have confirmed this bug exists on the [latest release](https://github.com/shap/shap/releases) of shap.
- [ ] I have confirmed this bug exists on the [master branch](https://github.com/shap/shap/blob/master/CONTRIBUTING.md#installing-from-the-master-branch) of shap.
- [ ] I'd be interested in making a PR to fix this bug

### Installed Versions

'0.44.1'
'0.41.0'

Turns out it's expected: here


Concurrent grammar and non-grammar requests

System Info
1.4.3 and https://github.com/huggingface/text-generation-inference/pkgs/container/text-generation-inference/192173353?tag=sha-0d72af5
Information

[X] Docker
[ ] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
Steps to reproduce:
1 - While true grammar text generation request.
2 - At the same time, in another process, run a non-grammar text generation request.
3 - Both fail with a server error.
TGI container logs:
2024-03-21T09:01:53.354872Z ERROR text_generation_launcher: Method Decode encountered an error.
Traceback (most recent call last):
  File "/opt/conda/bin/text-generation-server", line 8, in <module>
    sys.exit(app())
  File "/opt/conda/lib/python3.10/site-packages/typer/main.py", line 311, in __call__
    return get_command(self)(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/typer/core.py", line 778, in main
    return _main(
  File "/opt/conda/lib/python3.10/site-packages/typer/core.py", line 216, in _main
    rv = self.invoke(ctx)
  File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/conda/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/typer/main.py", line 683, in wrapper
    return callback(**use_params)  # type: ignore
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/cli.py", line 89, in serve
    server.serve(
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 235, in serve
    asyncio.run(
  File "/opt/conda/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 636, in run_until_complete
    self.run_forever()
  File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 603, in run_forever
    self._run_once()
  File "/opt/conda/lib/python3.10/asyncio/base_events.py", line 1909, in _run_once
    handle._run()
  File "/opt/conda/lib/python3.10/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/opt/conda/lib/python3.10/site-packages/grpc_interceptor/server.py", line 165, in invoke_intercept_method
    return await self.intercept(
> File "/opt/conda/lib/python3.10/site-packages/text_generation_server/interceptor.py", line 21, in intercept
    return await response
  File "/opt/conda/lib/python3.10/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py", line 82, in _unary_interceptor
    raise error
  File "/opt/conda/lib/python3.10/site-packages/opentelemetry/instrumentation/grpc/_aio_server.py", line 73, in _unary_interceptor
    return await behavior(request_or_iterator, context)
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/server.py", line 146, in Decode
    batch = self.model.batch_type.concatenate(batches)
  File "/opt/conda/lib/python3.10/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/models/flash_causal_lm.py", line 593, in concatenate
    next_token_chooser = HeterogeneousNextTokenChooser.from_pb(
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/tokens.py", line 471, in from_pb
    return HeterogeneousNextTokenChooser(
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/tokens.py", line 269, in __init__
    HeterogeneousGrammarLogitProcessor(
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/logits_process.py", line 558, in __init__
    fsm = GrammarLogitProcessor._cached_compile_fsm(
  File "/opt/conda/lib/python3.10/site-packages/text_generation_server/utils/logits_process.py", line 518, in _cached_compile_fsm
    fsm = RegexFSM(schema, tokenizer)
  File "/opt/conda/lib/python3.10/site-packages/outlines/fsm/fsm.py", line 121, in __init__
    self.states_to_token_maps, self.empty_token_ids = create_states_mapping(
  File "/opt/conda/lib/python3.10/site-packages/outlines/caching.py", line 74, in wrapper
    result = cached_function(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/outlines/fsm/fsm.py", line 103, in create_states_mapping
    regex_fsm, _ = make_deterministic_fsm(regex_pattern.to_fsm().reduce())
  File "/opt/conda/lib/python3.10/site-packages/outlines/fsm/regex.py", line 165, in make_deterministic_fsm
    new_alphabet = BetterAlphabet(new_symbol_mapping)
  File "/opt/conda/lib/python3.10/site-packages/outlines/fsm/regex.py", line 17, in __init__
    assert anything_else in self._symbol_mapping
AssertionError

2024-03-21T09:01:53.358415Z ERROR batch{batch_size=2}:decode:decode{size=2}:decode{size=2}: text_generation_client: router/client/src/lib.rs:33: Server error:
2024-03-21T09:01:53.359712Z ERROR compat_generate{default_return_full_text=true compute_type=Extension(ComputeType("1-nvidia-geforce-rtx-4090"))}:generate{parameters=GenerateParameters { best_of: Some(1), temperature: None, repetition_penalty: Some(1.2), frequency_penalty: None, top_k: None, top_p: None, typical_p: None, do_sample: false, max_new_tokens: Some(1024), return_full_text: Some(false), stop: [], truncate: None, watermark: false, details: true, decoder_input_details: false, seed: None, top_n_tokens: None, grammar: None }}:generate:generate_stream:infer:send_error: text_generation_router::infer: router/src/infer.rs:705: Request failed during generation: Server error:
2024-03-21T09:01:53.359751Z ERROR compat_generate{default_return_full_text=true compute_type=Extension(ComputeType("1-nvidia-geforce-rtx-4090"))}:generate{parameters=GenerateParameters { best_of: Some(1), temperature: None, repetition_penalty: Some(1.2), frequency_penalty: None, top_k: None, top_p: None, typical_p: None, do_sample: false, max_new_tokens: Some(1024), return_full_text: Some(false), stop: [], truncate: None, watermark: false, details: true, decoder_input_details: false, seed: None, top_n_tokens: None, grammar: Some(Json(Object {"properties": Object {"age": Object {"title": String("Age"), "type": String("integer")}, "name": Object {"title": String("Name"), "type": String("string")}}, "required": Array [String("name"), String("age")], "title": String("Test"), "type": String("object")})) }}:generate:generate_stream:infer:send_error: text_generation_router::infer: router/src/infer.rs:705: Request failed during generation: Server error:

Expected behavior
Concurrent grammar and non-grammar requests working smoothly as expected.

I have had this error too with text generation inference v1.4.3.

Also had this with v1.4.3, crashes my app because I am doing async requests with grammar and no grammar... is this fixed in the newest release?

docker  ghcr.io/huggingface/text-generation-inference:1.4.4
Encountered the same problem as above.

So this PR solved multiple concurrent grammar requests, but not a mix of Grammar with none Grammar? https://github.com/huggingface/text-generation-inference/pull/1610

That's correct. Looks like @drbh just opened a PR to address this today! :)
https://github.com/huggingface/text-generation-inference/pull/1676

So this PR solved multiple concurrent grammar requests, but not a mix of Grammar with none Grammar? #1610

closing since this is fixed by https://github.com/huggingface/text-generation-inference/pull/1676

Confirmed fix, great job guys and thanks!


[FEATURE] Add specs for notifications namespace

Part of Adding missing API specs issue

[ ] /_plugins/_notifications/channels: ["GET"]
[ ] /_plugins/_notifications/configs: ["GET","POST","DELETE"]
[ ] /_plugins/_notifications/configs/{config_id}: ["GET","PUT","DELETE"]
[ ] /_plugins/_notifications/feature/test/{config_id}: ["GET","POST"]
[ ] /_plugins/_notifications/features: ["GET"]

After https://github.com/opensearch-project/opensearch-api-specification/pull/169 and https://github.com/opensearch-project/opensearch-api-specification/pull/217 I still see there is one API missing, as it's not listed on the doc page.
/_plugins/_notifications/channels: ["GET"].
I could try adding it.

there you go!


[2.7.x] HARVESTER: Remove External Harvester Cloud Credentials Support

Summary
Remove External Harvester Cloud Credentials Support

Occurred changes and/or fixed issues

https://github.com/harvester/harvester/issues/3319

Technical notes summary

Remove clusterType radio button
Remove kubeconfig content textarea

Areas or cases that should be tested

Cluster Management -> Cloud Credentials
Cluster Management -> Create Harvester -> Machine Pools

Areas which could experience regressions

Screenshot/Video

Hi, @mantis-toboggan-md. There have a PR that needs you to review, Thx!


Add new dweet button

Closes #27

Great! Thanks :)
Minor nitpick:
The media numbers might need a little bit on tweaking, I managed to get into the following states:
Firefox:

(Firefox seems to never get into (+) New for some reason)
Chrome:

Microsoft Edge:
Surprisingly works flawlessly! :)
Note that all of the states above were only a few pixels wide, so just a little bit of margin for error should do it.


Switch to new test function approach for dynamic loading

Use the new test function approach which just landed in premake-core to decide when the module should be loaded (a configuration exists which has set its language to "D").

Thanks! I was just about to do this :)


[Bug]: Access Denied when connecting to SharePoint Online using Interacive authentication

What happened?
It seems that Microsoft is blocking some Microsoft's first-party apps from connecting SharePoint Online.
1950a258-227b-4e31-a9cf-717495945fc2
How to reproduce it
Monkey365 fails with authorization error after successfully connecting to SharePoint Online, due that the ClientId used (Microsoft Azure PowerShell ClientId) is blocked by Microsoft. The following error response is returned:
{"error":"invalid_request","error_description":"App is not allowed to call SPO with user_impersonation scope"}

Additional context
Both Client credentials and certificate authentication flows are not affected by this issue.

It's now fixed on dev branch. It will be merged to main branch asap


Docker image for 0.5.0 version

What about docker image for the new version?
There is Dockerfile in the repository,  but it requires already built files.
Docker multi-stage build (https://docs.docker.com/engine/userguide/eng-image/multistage-build/) can be used here for.

Hi @mastak,
it's on my todo list :-) Many things has changed since the last release and it will require some re-thinking. If you have experience with Docker and you like to propose some solution, feel free.
I'll try to get it done soon, however cannot guarantee when
Cheers
Luca

Hi @lfoppiano,
I'm not very familiar with Java, but I can help with docker.
I see that there are should be 2 files, but how I can build them from source?:
ADD ./grobid-home/target/grobid-home-${GROBID_VERSION}.zip /opt
COPY ./grobid-service/target/grobid-service-${GROBID_VERSION}.war /var/lib/jetty/webapps/ROOT.war```

@mastak you need to know a bit of building on java actually, we don't have a war build anymore, but I'm not sure it's perhaps good to add it back for the docker image.
In the meantime if you use the docker image with tag 0.4.4 you will have roughly the same features, in version 0.5.x we have changed build method (gradle) and we added a framework.
Cheers
Luca


Broken sampleRateShading and differentiating SSAA from MSAA

Setting VkPipelineMultisampleStateCreateInfo::sampleShadingEnable = VK_TRUE; and VkPipelineMultisampleStateCreateInfo::minSampleShading = 1.0f; should enable supersampling, but it does not. It just behaves like regular multisampling.
Either this is a bug and it should be fixed or MoltenVK shouldn't claim to support VkPhysicalDeviceFeatures::sampleRateShading.
Hardware is Apple M1, macOS Monterey

The VkPhysicalDeviceFeatures::sampleRateShading feature enables two capabilities in Vulkan:

If sample shading is enabled, an implementation must invoke the fragment shader at least max(VkPipelineMultisampleStateCreateInfo::minSampleShading × VkPipelineMultisampleStateCreateInfo::rasterizationSamples, 1) times per fragment (Vulkan spec).

sampleRateShading [...clip...] This also specifies whether shader modules can declare the SampleRateShading capability (Vulkan spec).

Metal supports the second capability (super-sampling in the presence of Per-Sample builtins in the shader), but not the first (forced supersampling without such builtins):

The implementation may decide to only execute the code that depends on the per-sample values to execute per-sample and the rest of the fragment function may execute per-fragment (Apple MSL doc).

If minSampleShading is not zero, MoltenVK already actually attempts to declare no-op usage of Per-Sample builtins in the MSL shader, in an attempt to force that first requirement, but unfortunately Metal optimizes them away and does not run any part of the shader Per-Sample.
Disabling VkPhysicalDeviceFeatures::sampleRateShading would fix the app expectations for the first Vulkan requirement above, but unfortunately, per the second Vulkan requirement above, would also set an app expectation that Per-Sample builtins cannot be used in a shader.
I've opened a discussion in the Portability extension about adding a VkPhysicalDevicePortabilitySubsetFeaturesKHR::supportMinSampleShading capability, that would allow an app to query this functionality.
Finally, to help possibly justify to Apple that the behavior should be changed, what is your use-case for wanting supersampling when the shader does not make effective use of the Per-Sample builtins?

Thanks for the detailed response, I wondered if it's something Metal can't support.

The use case is to enable SSAA without having to do anything special with the shaders. I maintain vkQuake for which there is more than enough GPU power to just brute force SSAA on everything.

And you find a noticeable visual difference with SSAA over MSAA in that situation? More than just the edge anti-aliasing that MSAA is focused on? Where does SSAA show better visuals over MSAA in your environment?
I'm curious, because it would help validate a possible request for Apple to support forced SSAA.

Yes of course there is a noticable difference. Shading aliasing is a thing, even more so with modern PBR techniques. Most people use temporal super sampling to deal with that, but that has it's own quality problems (mainly ghosting).

@alyssarosenzweig suggests a fix here.


Disallow column references in ROWS/RANGE

Fixes #5514.
Added warning to Window Function Syntax section stating that variables are no longer valid in ROW/RANGE clauses.
Do we want an example too? Not sure how much attention we want to bring to this, as our behavior before this change was undocumented and not postgres-like.

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/50a1813331a4c3886212e4cdd9cd891e2e599969/
Edited pages:

v19.2/window-functions.md

 but I don't really think this is necessarily worth documenting (but I'm biased towards not documenting things)

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @justinj)

I kind of agree... I'm going to close this and the issue.


[Bug]: PHP 7.3 sintax error in setupcontroller

What happened?
hello
i have this error with php 7,3 when i try to install on shared hosting
Parse error: syntax error, unexpected 'string' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) in /home/mhd-01/www.yyy.net/htdocs/setup/classes/SetupController.php on line 26
anyone can help me please...
What did you expect to happen?
Parse error: syntax error, unexpected 'string' (T_STRING), expecting function (T_FUNCTION) or const (T_CONST) in /home/mhd-01/www.zzz.net/htdocs/setup/classes/SetupController.php on line 26
Version
3.0.6
What browser are you seeing the problem on?
Firefox
Relevant log output
No response

7.3 is no longer a supported platform (PHP itself no longer supports it). Please update to 7.4 or higher.

i'm not able to update to 7.4

7.3 is no longer a supported platform (PHP itself no longer supports it). Please update to 7.4 or higher.

i'm not able to update to 7.4, my hosting not support it. is possible to have an old installer?

You can download an old release from GitHub releases and install using composer.


Switch fails with null value

Steps to reproduce
$var = get-process | out-null
switch ($var) {
  $null { write-host NULL }
  default { write-host DEFAULT }
}

In my specific case, I assign $var to the output of a native command that, in some expected cases, doesn't return anything.
Note that explicitly assigning $var = $ null appears to be not the same thing and doesn't trigger the issue.
Expected behavior
Expecting the switch to be evaluated and the $null clause honored.
Actual behavior
The switch is entirely skipped.
Environment data
PSVersion                      6.2.2
PSEdition                      Core
GitCommitId                    6.2.2
OS                             Microsoft Windows 10.0.18362
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

$var won't contain $null with the code you've given. In will continue PowerShell's "nothing" value - AutomationNull. This value indicates no value whatsoever, not even $null.
If Out-Null generated a $null, then this sequence would create output:
$items | Out-Null | % { 42 }

This is because $null is a perfectly valid pipeline value and would continue down the pipe.
Out-Null follows the idea of redirecting to /dev/null on Linux where no output is generated at all. A $null value is still a valid output value, however.
Even knowing this, I do not think there is a way to examine that with a switch statement. A switch statement iterates it's input, and will process arrays one item at a time. AutomationNull indicates to PowerShell that no iteration is to occur -- not in the pipeline, nor a foreach statement, etc., So the switch behaves the same.

Ok, now I'm confused.
I'm in my actual code I'm assigning to the output of some native command:
$var = az network dns record-set list [...] --query  -otsv
that returns a list or nothing, if there's nothing to return.
I was assuming that in that case the variable got assigned to $null.
Actually, after that assignment, the following works fine:
    if ($var -eq $null) {
        Write-Host "something"
    } elseif ($var -eq $something) {
        Write-Verbose "somethingtoo"
    } else {
        Write-Host "somethingelse"
    }

So why, is the first if actually working?

An if statement doesn't iterate like a switch does, it's just a direct comparison as written.
AutomationNull is by definition equivalent to $null in a direct comparison, so that's why the if statement works.
It does appear the assignment results in truly nothing rather than $null, yeah. Unusual, really, most native utils output something.

Actually, the output (or lack there-of) of the command is quite normal. Simply the command has nothing to do/say or, in my specific case, the query result is empty.
If I get it right... the "AutomationNull" is equal to "unassigned"?
I find confusing that an assigment to something that is "nothing" results in an unassigned variable.
In what cases the output of a native command can result in a $null assignment?

If I get it right... the "AutomationNull" is equal to "unassigned"?

More like "no results".  It acts a bit differently than an unassigned variable in some cases.  It's a bit like how a SQL query could return a literal NULL value or just not find any matching results.
AutomationNull is like a mix between an empty collection (e.g. @() )and $null. A bit closer to an empty collection than $null.

@EPinci the output of a native command cannot result in a true $null assignment, because native commands only deal with text output. You can get "nothing", you can sometimes in odd cases get an empty string value ( [string]::Empty or '' ), or a string containing just whitespace.
Native commands don't deal with the CLR, so they don't have the ability to pass a $null value to another utility like PowerShell.


Possibly change from marked to remarkable?

Remarkable looks to have better options, more features, CommonMark support, etc. Consider using this as the built in Markdown compiler for previewing.

I use CommonMark in my website.
I don't like a big markdown editor, so the common function is ok.
So, in my opinion, don't import too many thing in this editor.

I do see that remarkable's min file is 93.7 KB vs marked's 19.1 KB. Not sure if it's possible to trim it down, but it would be bundled into SimpleMDE and it would replace marked.

+1 for this. It will be very nice to use simpleMDE for CommonMark.


Add missing containerId prop to all MiradorMenuButton instances

This had the effect of making button popovers disappear in fullsscreen mode, since the popovers would be  rendered as a child of the body element, which was not in fullscreen scope.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #40   +/-   ##
=======================================
  Coverage   86.88%   86.88%
=======================================
  Files          15       15
  Lines         686      686
  Branches      217      217
=======================================
  Hits          596      596
  Misses         85       85
  Partials        5        5

Impacted Files
Coverage Δ

src/components/settings/ColorWidget.js
93.33% <ø> (ø)

src/components/settings/OverlaySettings.js
98.46% <ø> (ø)

src/index.js
0.00% <ø> (ø)

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 7899639...6347c5a. Read the comment docs.


feature/481 Initial Commit for Cryptocash.Ui Phase1 Skeleton Layout

#481 This PR is for initial skeleton layout of Cryptocash.Ui Phase 1 - so that we can agree how to further slice into template Ui controls for Nox.Generator output
Note:
1 - Yaml config hasnt been added until we agree the Yaml definitions - (example default config has been coded for now into MainLayoutBase) related ticket see #484
2 - PR can be used to agree how to separate out razor into sub Nox.Ui templates for example the Navigation Links and Header sections for now
3 - AzureAd Authorization code has been commented out for now until YAML config agreed (within Program.cs)
4 - Have added Generated folders as an example to be agreed of handling generated content - idea being that the razor page is created (ie: Bookings.razor) and uses the generic page base to handle logic (ie: ApiManagementPageBase in an attempt to reduce Generator output.
5 - Have added a way for child controls to trigger a change in global data  - see ApiManagementPageBase.UpdateHeaderApiName() - to be agreed if this is best approach for child components to trigger and change data globally for other child/parent components with BlazorServer code - see related ticket https://github.com/NoxOrg/Nox.Ui.Sandbox/issues/1
6 - I'll add Docker support under a different ticket see #497
7 - Have left in for now ConfigurationHelper as it is probably useful later on
thanks DanHo

Overall looks good to me. I'd add some small comments below:

I would rename ApiManagement folder for generated file to something like Pages. Cause in fact every entity is managed by API call and and it's not ApiManagement itself. We can always discuss it, but I'd suggest something like this:

Generated/Pages/
├── Booking/
│   ├── BookingsList.cshtml
│   ├── BookingCreate.cshtml
│   ├── BookingEdit.cshtml
│   └── BookingDetails.cshtml
├── Employer/
│   ├── EmployersList.cshtml
│   ├── EmployeeCreate.cshtml
│   └── ...
└── ...

I would also rename ApiManagementPageBase but couldn't come up with a right name.
Maybe it would make sense to rename generated files to *.g.razor, *.g.cs so we can understand what we expect to be generated by Nox and what should Nox users (actually developers) add by themselves.
Based on the previous point, I think it would be good to create a rough README file and put there everything that should be done in the project manually. I know things are going to change many times, but it could be a draft version for now.

#481 PR Requested Changes
1 - As per Anna's request have changed folder structure to /Generated/Pages (plus Components & Data) - might still need discussion if so lets create a meeting to discuss - for example Add and Edit may be modal popup components rather than pages in whole - also have kept root Pages folder to hold index, _host root pages etc to not break blazor
2 - Changed 'Generated' files to include .g.razor or .g.cs
3 - Readme will be added on a separate ticket once Config agreed see #501
4 - Requested changes made to .proj file
5 - Removed extra .sln file
6 - For now have included Customer and Employee entities to tie in with initial Cryptocash.Api project - havnt included Employer as probably safe to assume for this POC only dealing with 1 employer ie: Cryptocash


Socket not raising error on write while there is no connection

I noticed that after successful login, when connection become down and i tried to write something to socket, client not raising any error, for example sending ping messages etc.
As a result of this, i don't know if i am connected and if message became delivered:
client.logged?

always returns true, but messages are lost.

inactive - closing


Fail, no socre after that

After game it says "failed to load your score" or something like that, so i got no xp and didnt get progress for that "tile" and it restarts after that

Me too, my game finish and back to the map but no xp :/

You do get exp, it's just delayed because of how we log it.

If it delayd, why i didnt got xp for 6 games that i played on high risk tiles?

After 20h of play on the same planet, using always the latest version of the script and chrome, I gained only a few thousand XP during only specific times at the start and after that absolutely 0 for the next 16-18h... Switching to other scripts started giving me XP right away. There seemed to always be a steam error at the end of most, if not every game which required a browser reload.


Support configure election timeouts

Add support so users can configure leader election related timeouts through command flags.
Default lease duration is 15s and renew deadline is 10s. However in certain environments with lots of controller pods it might longer occasionally. Defaults for them stay the same as before, and this PR only adds a way to configure them if users want to.

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

Comparison is base (c5441fa) 77.75% compared to head (abd8ef3) 77.75%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #382   +/-   ##
=======================================
  Coverage   77.75%   77.75%
=======================================
  Files          19       19
  Lines        1699     1699
=======================================
  Hits         1321     1321
  Misses        305      305
  Partials       73       73

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


Add landing pages for Azle/Kybra

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

I assume you are getting the build error because the Rewards API does not return a samples section. I made a quick fix here: https://github.com/dfinity/portal/pull/2466 but we should probably follow up with @olaszakos

I assume you are getting the build error because the Rewards API does not return a samples section. I made a quick fix here: #2466 but we should probably follow up with @olaszakos

This was fixed in this PR: https://github.com/dfinity/portal/pull/2467


Auth route

This PR:

Adds the ability to add auth for routes using the checkJwt function.
Add debugging messages for auth0 env variables.
Allows for Auth0 JWT tokens that are generated client side to be passed API routes.
Refactors Authentication route.
Remove unnecessary auth test file for authentication route.
Updates contributors guide with current set up info

😒 It seems to be failing to due to an an improperly merged pull between this branch and main. I'll fix this a little later today or sometime tomorrow.

After a bit of merge conflict fixes, should be good for review now 🎉


Save default mesh as a resource file

The default mesh is now a resource loaded from a .tres file instead of building it manually each time on _init(). This reduces the script size by almost 80 lines with no drawbacks that I can think of.
I converted the _build_default_mesh() function into a separate file which saves the mesh as a resource in the addon folder, just in case it is still considered useful.

IIRC the change in the 2nd commit was because without duplicating the mesh at runtime, the nodes would spam git diffs after each map save.


Update translations

This PR adds translations for new strings, and fixes a few ambiguities due to singular/plural expression differences between EN/TR.

Emir Sarı wrote:

This PR adds translations for new strings, and fixes a few ambiguities
due to singular/plural expression differences between EN/TR.

Please source the cleanup.vim script.  This removes the line numbers
from the file, so that patches are not messed up by changes in line
numbers and show the actual changes in the text.
--
I'd like to meet the man who invented sex and see what he's working on now.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Emir Sarı wrote:
This PR adds translations for new strings, and fixes a few ambiguities due to singular/plural expression differences between EN/TR.
Please source the cleanup.vim script. This removes the line numbers from the file, so that patches are not messed up by changes in line numbers and show the actual changes in the text.
…

Sorry, forgot that!

I'll include it, thanks.