Update log levels

Is there a related GitHub Issue?
#1926
What is this change about?
Audit and update all existing logs to an appropriate level. We generally did the following to logs:

Use error log level for platform startup issues, debug log level for resource lifecycle events and info log level for everything else.
Attach an error to an info log entry as a "reason" if appropriate.
Deduplicated error logging

Note that after rebasing on main there is a new helper function that is logging at the error level. We left the helper alone for now and will confirm with the team whether there is any issue with moving that down to info by default, potentially with a sibling helper function.
Does this PR introduce a breaking change?
No
Acceptance Steps
Deploy Korifi normally and see many fewer noisy logs at the default log level.
Tag your pair, your PM, and/or team
@davewalter @matt-royal
cc @julian-hj for thoughts

@clintyoshimura @Birdrock did y'all have any thoughts on the log level used by the new logErrorAndSetReadyStatus helper function? We considered moving the logs down to Info level given the additional error handling of the ready status in the api layer, but wanted to check with y'all first.


<EMAIL_ADDRESS>Fix download URL

Updated URL and autoupdate URL to match current repository release URL structure.
Closes #8982

[x] I have read the Contributing Guide.

/verify

Thanks!


Pretrained MEGNet models for formation energy and band gap are added

This is great. But I would like you to add the actual training script in the examples. This is useful reference for people who want to train their own models.


Blackberry OS10 only local lists?

I downloaded Opentask today on my BB Passport to sync my owncloud tasks. But it seems theres only the possibility to create local task lists. Am I wrong or will a sync only work on a "real" android device?
Is there a way to add the caldav account inside the app itself?

A couple of days ago I had the same issue on an regular Android phone.
After some time I figured out that I had to install CalDAV-Sync (a calendar/task provider) which is required to connect to OwnCloud or other CalDAV services.
I guess a message/warning should be added to the AppStore telling you that a sync application is additionally required.

which one worked for you?

I had to install CalDAV-Sync in addition to OpenTasks (maybe I was not clear enough in the previous answer).
CalDAV-Sync provides the means to connect to OwnCloud and OpenTasks displays the data and lets you edit it.

Another option is DAVdroid they available on both the play store and f-droid


feat: add flagSortOrder to help options

Adds flagSortOrder to helpOptions
Two options:

alphabetical: Sort flags alphabetically. All flags with short characters will come first. (Default behavior)
none: Do not sort flags. They will appear in the order in which they were defined on the command.

To use, add flagSortOrder to helpOptions in your CLI's package.json
"oclif": {
  "helpOptions": {
    "flagSortOrder": "none"
  }
}

Fixes https://github.com/oclif/oclif/issues/1214
@W-14626665@

QA notes:
✅ no option defined, defaults to sorted
✅ oclif.helpOptions.flagSortOrder = none, unsorted
✅ oclif.helpOptions.flagSortOrder = none, sorted
🟡 sort order option isn't validated at runtime:
while in TS only alphabetical or none is supported, this config is read from json so any typos make it render flags as unsorted.

do you think it's worth validating this at runtime? not sure it should throw or warn (also don't know if oclif validates any psjon settings).


Promtool building TSDB from Openmetrics file but grafana doesnt show

What did you do?
https://serverfault.com/questions/1136605/promtool-tsdb-create-blocks-from-openmetrics-doesnt-show
What did you expect to see?
Expect grafana show the value in graph
What did you see instead? Under which circumstances?
not data
System information
No response
Prometheus version
prometheus, version 2.45.0 (branch: HEAD, revision: 8ef767e396bf8445f009f945b0162fd71827f445)
  build user:       root@858b3920627f
  build date:       20230623-15:18:12
  go version:       go1.20.5
  platform:         windows/amd64
  tags:             builtinassets,stringlabels

Prometheus configuration file
global:
  scrape_interval: 15s # By default, scrape targets every 15 seconds.

  # Attach these labels to any time series or alerts when communicating with
  # external systems (federation, remote storage, Alertmanager).
  external_labels:
    monitor: "codelab-monitor"
scrape_configs:

Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

I answered you here https://serverfault.com/a/1143746/1051335, I think it's related to "resolution" and you're just not making the the UI run the right query.
IMHO, https://groups.google.com/g/prometheus-users is more suited for questions like this.

Hello from the Bug Scrub!
Sounds like this issue is answered, thanks!


Making Input Different From Text

Hello,
I want to train an image captioning model with the transformer. How should I configure the input (i.e. VGG imagenet features) so that I can have an encoder-decoder model that is an image captioning model?
Please share any links or examples to implement this.

You may want to use the TFRecordData module to read and process image (feature) data. Please let us know if you have more questions on this

@ZhitingHu thank you for the answer! I am keeping this issue open, as I am trying the TFRecordData and will update in a few days.

@ZhitingHu i have a numpy array with the image features. What lines should I change in the current transformer model to adapt it to the image captioning code?
Also, could you provide any starter code for tfrecord and where to place it in the current transformer machine translation code?
thank you.

Replace the data part with TFRecordData module
You may refer to the test code for example of using TFRecordData

@ZhitingHu Hi,
I tried replacing the input data part above to a tfrecord module containing, image-text pair,
and replace the load_data_numpy to load_data_
def load_data_():
train = tf.data.TFRecordDataset("train.tfrecord")
def _parse_function(example_proto):
keys_to_features = {'x': tf.FixedLenFeature([], tf.float32),
'y': tf.FixedLenSequenceFeature([], tf.string, allow_missing=True)}
parsed_features = tf.parse_single_example(example_proto, keys_to_features)
return parsed_features['x'], parsed_features['y']
train = train.map(_parse_function)
return train, train, train
But I get error:
TypeError: 'MapDataset' object is not iterable

@ZhitingHu the issue in more explaination: https://github.com/tensorflow/tensorflow/issues/28008

The bert and gpt-2 examples show how Texar's TFRecordData module can be used in this case.


Using Formik for Update Scan Report Table view

Changes
In the past, this view was built by using normal form fields and many other "unnecessary" components.
This PR optimised the view of the Updating Scan Report Table by using Formik form and React Select. This makes the code shorter, cleaner, and easier to read.
This PR also added and modified some tooltips and toast messages.
Closes #791
Screenshots
General view

Checks
Important: please complete these before merging.

[x] Run migrations, if any.
[x] Update changelog.md, including migration instructions if any.
[x] Run unit tests.

Please create an item of discussion in the back end for the comments.

Thanks for the comments. Please check out this newly created issue in backlog: https://github.com/Health-Informatics-UoN/Carrot-Mapper/issues/795


Add foreach function for inquiry properties into obj

Signed-off-by: pius.lee<EMAIL_ADDRESS>This new function makes api user can search enumerable properties in the javascript object.

hello, I have plan to use jerryscript in my local project. (maybe it will be open soon)
I want to get names and values of properties in object from javascript.
but I can not found function for getting names in object properties.
This function made to get unknown properties and there names in C/C++ scope.

@idkiller
Signed-off-by message is incorrect. The following line should be at the end of the 50aa8e60faf4256c8cf024997075234d9fd494d4 commit's message: 'JerryScript-DCO-1.0-Signed-off-by: pius.lee<EMAIL_ADDRESS>

I've not got other comments.

Good to me

I don't have any other comments

lgtm

After fix of https://github.com/Samsung/jerryscript/pull/651#discussion_r44264948, the changes would look good to me

Looks good to me

@egavrin, I've already reviewed the pull request - https://github.com/Samsung/jerryscript/pull/651#issuecomment-155386419.

Merged ece246ef9e003f6365fa4828e945bba4d04d4168


Update zio, zio-streams, zio-test, ... to 2.0.9

Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-sbt

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

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #194.


Add processing metadata validation tests

Add processing metadata validation tests to ensure only valid methods with full descriptions are included in the metadata.

All functions which modify the dataframe are now leaving metadata traces


Refactor ShareButton + minor improvements

A collection of very minor improvements while poking around the site's share button functionality.

The ShareButton implementation looked odd and convoluted to me. I cleaned it up a bit, removed the copy-to-clipboard dependency and just used the native Clipboard API which has been well supported for some time now.
Fixed a "copied" notification position bug on page load, and also refactored the Tabs component so it's a bit more readable and idiomatic (refs over DOM selector).
Converted a few divs with role="button" into actual buttons so that keyboard events don't have to be re-implemented. onKeyPress has been deprecated anyways.
Standardized import name of the classnames package to cn everywhere (only two components were different)
Vertically aligned some grid lines when the share button wraps to the next line:

Thanks for all these adjustments, looks great!


Fixes OAuth action doubling up on some query params

Hey there, just a tiny bug I ran into with the OAuth stuff.
Because it's using OR instead of AND operator, these params ('redirect_uri', 'scope' etc) that have already been added to the query get appended on the end again. In most cases, this doesn't really matter but Google squawks if you pass through the same param multiple times

Thanks for the PR!  I think you're right!
@snada can you take a quick look and share your thoughts? Then i'll pull it in.
p.s.
I apologize for not getting around to officially release and promote this feature yet, I'm going to do it as soon as I finish the current thing I'm working on (probably will finish in a couple of weeks)

Ah yes @judereid you are absolutely right.
Thanks for testing this feature, it was pretty big and hard to cover it entirely. If you still find something odd go on fixing it!
@gliechtenstein i've been very busy too so i didn't have much time to think about the docs we talked about. whenever you feel like taking this back ping me on slack or something!

Merged! 👊
re: @judereid Thanks for the contribution!
re: @snada awesome thanks. Will do!

@gliechtenstein @snada Glad could be of some small help!
I just started using Jasonette a couple of weeks ago, but so far it's awesome.
Other than this little blip, setting up FB and Google login was super easy with the OAuth action.
Thanks for all your hard work!


Update README.md

[X] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Edits readme .md file for clarity and concision.
Edits Scripting API Examples readme.md for clarity and concision.

What testing has been done?
Used external viewer to verify file renders correctly.

This PR is good to go after the small changes mentioned above are addressed.
Thank you Will for your help on this! 👍


5 ➡ 6

➡ Forward port
Port ign-gazebo5 to main
Branch comparison: https://github.com/ignitionrobotics/ign-gazebo/compare/main...ign-gazebo5
Requires https://github.com/osrf/sdformat/pull/604
I had to combine 2 new widgets in the ViewAngle widget coming from separate branches, this is the result (FYI @jennuine and @iche033 ):

Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸

@osrf-jenkins run tests please

the updated View Angle plugin looks good to me

@osrf-jenkins run tests please


Events?

Is there a list of available hooks/ events? For example, I would like to fade out/in views. Thanks

Thanx for this awesome framework. I am just curious when will Mithril support animation? Can't Mithril add or remove classes at DOM being added or removed just like Angular?


NRE when using DiContainer.Resolve()

Sometimes we get this strange NRE:
ThreadProcessor task exception: System.NullReferenceException: Object reference not set to an instance of an object
 at Zenject.DiContainer+<TryGetUniqueProvider>c__AnonStorey1.<>m__0 (Zenject.DiContainer container) [0x0005c] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:533
 at Zenject.DiContainer.ForAllContainersToLookup (InjectSources sourceType, System.Action`1 action) [0x0005b] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:618
 at Zenject.DiContainer.TryGetUniqueProvider (Zenject.InjectContext context) [0x000af] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:516
 at Zenject.DiContainer.Resolve (Zenject.InjectContext context) [0x0005d] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:947
 at Zenject.DiContainer.ResolveId (System.Type contractType, System.Object identifier) [0x00018] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:2263
 at Zenject.DiContainer.Resolve (System.Type contractType) [0x00004] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:2250
 at Zenject.DiContainer.Resolve[IMeshData] () [0x0000c] in ...\Assets\Plugins\Zenject\Source\Main\DiContainer.cs:2245

It's quite rare, but still couple of times a day we get this issue.
Used binding:  Container.Bind<IMeshData>().To<MeshData>().AsTransient();

What version of zenject?  I'm trying to place that line number

v7.1.0 and yes we are using ZEN_MULTITHREADING.

Ok having placed the line number I know what the issue is.  Will take a look


Readonly helper incompatible with private class fields.

Bug Report

🔎 Search Terms

private class field readonly helper missing property duck typing
🕗 Version & Regression Information

Playground link with relevant code
💻 Code

class X {
    public publicProp = 42;
}

const ro_x: Readonly<X> = Object.freeze(new X());

const rw_x: X = ro_x; // This works.

class Y {
    public publicProp = 42;
    #privateProp: number;

    constructor() {
        this.#privateProp = 22;
        console.log(this.#privateProp);
    }
}

const ro_y: Readonly<Y> = Object.freeze(new Y());

const rw_y: Y = ro_y; // This complains about missing the "#privateProp" property.

🙁 Actual behavior

The compiler complains that the readonly type cannot be assigned to the normal type. To be honest, this is something that I could relate to if it was working like that in all cases. For example if the error was thrown for X as well. It would make sense since you expect to get a "normal" X but you get a readonly one instead, things are not likely to go well. But Typescript accepts it, fine. I can accept that as well. But as soon as the type in question has a private class fields then it all falls apart. I just wanted to type the fact that the type properties were readonly, why does the private class field get in the way ?
I tried to type a custom "ReadonlyY" for Y to put back the missing #private property but nope:
interface ReadonlyY extends Readonly<Y> {
    #privateProp: number; // Private identifiers are not allowed outside class bodies.(18016)
}

It's quite funny actually, as the private class fields are invisible to Readonly, forbidden in interface since that would make it visible, but still somewhat visible to the compiler when comparing a type with its readonly counterpart.
Is there a workaround other than replacing private class fields with standard TS private field ?
🙂 Expected behavior
The same behavior for X and Y, regardless of the presence of private class fields.

You'll have the same issue with private and protected properties. Mapped types only operate on properties.
Duplicate of #16441. Used search terms: readonly private in:title

You'll have the same issue with private and protected properties. Mapped types only operate on properties.
Duplicate of #16441. Used search terms: readonly private in:title

I agree that it is a duplicate of https://github.com/microsoft/TypeScript/issues/16441. I thought it was related to private class fields, hence I did not look for the right keywords it seems. However, https://github.com/microsoft/TypeScript/issues/16441 was closed with no solution or workaround.

I agree that it is a duplicate of https://github.com/microsoft/TypeScript/issues/16441. I thought it was related to private class fields, hence I did not look for the right keywords it seems. However, https://github.com/microsoft/TypeScript/issues/16441 was closed with no solution or workaround.

There is no solution or workaround. It's a design limitation.

There is no solution or workaround. It's a design limitation.

While it is a bit sad, I understand that there is no current solution or workaround. Is there any plan to overhaul that in the future ? It's rather limiting that private fields be completely incompatible with Readonly. Both seem to me to be "basic" features, it is a bit weird to find that they cannot be use together.
Actually, it looks like Typescript would benefit for another way of setting a type as read-only that would not rely on mapped types for the job. I'm just wildly thinking here. Something like this:
class X {
    public publicProp = 42;
}

const ro_x: readonly X = Object.freeze(new X());

const rw_x: X = ro_x; // This might or might not work, but the behavior would be consistent with the one below.

class Y {
    public publicProp = 42;
    #privateProp: number;

    constructor() {
        this.#privateProp = 22;
        console.log(this.#privateProp);
    }
}

const ro_y: readonly Y = Object.freeze(new Y());

const rw_y: Y = ro_y; // This might or might not work, but the behavior would be consistent with the one above.

While it is a bit sad, I understand that there is no current solution or workaround. Is there any plan to overhaul that in the future ? It's rather limiting that private fields be completely incompatible with Readonly. Both seem to me to be "basic" features, it is a bit weird to find that they cannot be use together.
Actually, it looks like Typescript would benefit for another way of setting a type as read-only that would not rely on mapped types for the job. I'm just wildly thinking here. Something like this:
class X {
    public publicProp = 42;
}

const ro_x: readonly X = Object.freeze(new X());

const rw_x: X = ro_x; // This might or might not work, but the behavior would be consistent with the one below.

class Y {
    public publicProp = 42;
    #privateProp: number;

    constructor() {
        this.#privateProp = 22;
        console.log(this.#privateProp);
    }
}

const ro_y: readonly Y = Object.freeze(new Y());

const rw_y: Y = ro_y; // This might or might not work, but the behavior would be consistent with the one above.

Generally we think of mapped types as corresponding to the runtime operation of doing something like
function mapObj(value: T, func: (f: T[K]) => Q) {
  const res= { };
  for (let key in value) res[key] = func(res[key]);
  return res;
}

In this view, there's no preservation of private or protected properties.

Generally we think of mapped types as corresponding to the runtime operation of doing something like
function mapObj(value: T, func: (f: T[K]) => Q) {
  const res= { };
  for (let key in value) res[key] = func(res[key]);
  return res;
}

In this view, there's no preservation of private or protected properties.

I understand that. However, this means that if I want that my readonly class be assignable to its own non-readonly type, then I am forbidden to use any protected or private property. This means I cannot use getter/setter for any of them as I would have nowhere to store the actual value. That's quite restrictive in my opinion.
What is the point of checking the presence of the private properties ? Genuinely asking. It feels strange to me to consider them for some typing operations (type checking) and not consider them for other typing operations (mapped types).

I understand that. However, this means that if I want that my readonly class be assignable to its own non-readonly type, then I am forbidden to use any protected or private property. This means I cannot use getter/setter for any of them as I would have nowhere to store the actual value. That's quite restrictive in my opinion.
What is the point of checking the presence of the private properties ? Genuinely asking. It feels strange to me to consider them for some typing operations (type checking) and not consider them for other typing operations (mapped types).

What is the point of checking the presence of the private properties ?

class A {
    name = "bob";
    private x = Math.random();

    biggerOf(other: A) {
        return this.x > other.x ? this.x : other.x;
    }
}

const p: Readonly<A> = { name: "fred" };
// Unsound: value 'undefined' inhabits binding 'n' of type 'number'
let n: number = p.biggerOf(new A());

What is the point of checking the presence of the private properties ?

class A {
    name = "bob";
    private x = Math.random();

    biggerOf(other: A) {
        return this.x > other.x ? this.x : other.x;
    }
}

const p: Readonly<A> = { name: "fred" };
// Unsound: value 'undefined' inhabits binding 'n' of type 'number'
let n: number = p.biggerOf(new A());

Well, it turns out this feature is useful to me in another case where I want to enforce to use the constructor of the class rather than just having the interface of the class. For the curious:
// Let's say we have a type (here a class for simplicity) which has special behaviors like getters/setters on some of its members.
class A {
    base: { prop1: number, prop2: string };

    constructor(base: { prop1: number, prop2: string }) {
        this.base = { ...base };
        let prop1 = base.prop1;
        Object.defineProperty(base, 'prop1', {
            enumerable: true,
            get() {
                return prop1;
            },
            set(value: number) {
                prop1 = value;
                // Do something in the setter, for example:
                base.prop2 = '' + prop1;
            }
        })
    }
}

const a1: A = new A({ prop1: 28, prop2: 'whatever' });
const a2: A = { base: { prop1: 42, prop2: 'hi' } }; // Oops, I can assign it to the variable ! But the setter won't be called !

// Now if we add a private property to the class... (this could have been done in A but I'm keeping this code shorter)
class B extends A {
    #B!: B;
}

const b1: B = new B({ prop1: 28, prop2: 'whatever' });
const b2: B = { base: { prop1: 42, prop2: 'hi' } }; // Yes, the compiler warns me that something is wrong !

Well, it turns out this feature is useful to me in another case where I want to enforce to use the constructor of the class rather than just having the interface of the class. For the curious:
// Let's say we have a type (here a class for simplicity) which has special behaviors like getters/setters on some of its members.
class A {
    base: { prop1: number, prop2: string };

    constructor(base: { prop1: number, prop2: string }) {
        this.base = { ...base };
        let prop1 = base.prop1;
        Object.defineProperty(base, 'prop1', {
            enumerable: true,
            get() {
                return prop1;
            },
            set(value: number) {
                prop1 = value;
                // Do something in the setter, for example:
                base.prop2 = '' + prop1;
            }
        })
    }
}

const a1: A = new A({ prop1: 28, prop2: 'whatever' });
const a2: A = { base: { prop1: 42, prop2: 'hi' } }; // Oops, I can assign it to the variable ! But the setter won't be called !

// Now if we add a private property to the class... (this could have been done in A but I'm keeping this code shorter)
class B extends A {
    #B!: B;
}

const b1: B = new B({ prop1: 28, prop2: 'whatever' });
const b2: B = { base: { prop1: 42, prop2: 'hi' } }; // Yes, the compiler warns me that something is wrong !


Empty string is a valid object key but is not allowed nor parsed correctly as input

Describe the bug
Empty string is a valid object key but is not allowed nor parsed correctly as input
Try to add a key to a object named "" (the empty string)
Or provide such an object value as input in code (and then editting that value produces an error)
Expected behavior
Empty string should work like every other valid key
Screenshots
Not required
Online demo
Not required

Good catch, thanks. Will look into it.

Hi @jeffsenn, this should be fixed now. Please try v1.11.7.
This is how it appears by default, but you can change the <empty string> display by overriding the jer-empty-string::after CSS pseudo class:


Data had been replaced with "NUL" characters

Hi,
I am using flat-cache, as a offline storage in an application developed using electron. Sometime, the content in cache file was completely or partially replaced with "NUL" characters. I could not identify the cause for this. Could you please suggest a solution for this?
thanks,
Partha

hi @partha-srivi
Can you provide a code sample that shows this behavior? I have some unit tests covering the module and haven't notice that behavior, so any help reproducing the issue will be awesome
Thanks

Closing this as this behavior has not been reported more and no repro case was provided. Please feel free to reopen if you feel this is still an issue.


How to fix d1 db name?

I would like to use drizzle for migrations. I need to setup my drizzle.config.local to something like this:
import { defineConfig } from 'drizzle-kit'

export default defineConfig({
  dbCredentials: {
    url: '', // 👈 this could also be a path to the local sqlite file
  }
})

The issue I have is that the db name changes anytime I simply delete it (often in dev). Is there a way to set a fixed db name or somehow get the db name easily?

Looks like a hash from the binding: https://gist.github.com/KyGuy2002/1c70a5129042f1b037c56fe0b70b066e


Failing react packager after travis addition

This commit https://github.com/GeekyAnts/react-native-easy-grid/commit/82526c8d36b1caaca9ddf6e3e111140fa2bec799 gives an error in react packager when using this library @Jasbir23
It complaines about duplicate module name with react and react-native.
This issue kinda explaines it: https://github.com/aksonov/react-native-router-flux/issues/1809
So i believe after you added react-native and react as dependencies for your travis tests, it breaks now for simple usage of the library.
This might be solved with removing dependencies that is just for tests, and added them to devDependencies rather than the dependencies object.

Thanks for the input here @vongohren, Looking into this.

Hey @vongohren I hope this fixes it 4e3f8915c16edca53f52941de1fe00f4cf88d6cc

Looks promising, cant confirm until friday though :(

I can confirm it works


Client triggers a windows sound

So I've just started using RuneLite and sometimes I get a windows sound playing as if I was trying to delete text in a field without text (also the sound it plays when I run out of prayer). I think it might have something to do with the idle alerts, the only idle alerts I have turned on is for prayer and it's set to 1 prayer point, but the sound comes at different states of my prayer.
Thanks for reading

Do you have the "Configures if idle animation notifications are enabled" option in the idle notifier turned off?

Yes, I have turned what seems to all notifiers off apart from prayer (I'm in NMZ and have also turned off the powerups/OVL/absorp etc.)

can you take a picture of your idle notifier configs and put them here?

https://gyazo.com/02284cd809ac7d5f761b752f9dde9a18 https://gyazo.com/218ef55a8f7330b7e2ab5aa78a0fdd0c

Okay I just tried to trigger it, I prayed up to 99, minimized the client and didn't touch my mouse at all, at 64 prayer the sound played im using Superhuman str (10% str pray) and my pray bonus is 10 if that helps at all (could be the 5min idle? ill test the how long it takes this time)

4 minutes and 45 seconds for the alert ill now try with client focused

4 minutes and 40 seconds with client focused (still no mouse-movement) gonna try when I move my mouse around

There is a idle logout notifer which fires every 4 minutes and 40 seconds like you have stated. Unfortunately there is no way to turn those off unless you disable the idle notifier plugin.

Ehm okay, so that would be a suggestion to a future feature "Disable when in combat" or what? :)

yeah, if you want to rename this issue and description that would be nice

Thanks for helping ill do that now :)


Disable transformation if expression is enabled

If expression is enabled, transformations defined under field won't be used. All transformation has to be invoked in expression as a function. Therefore we should disable transformation in Mapping Details if expression is enabled.

The cleanest way is to not show the transformation icon/ content/ padding fields if the user toggles on the condition expression box.


Advise users who are skipping the NAND backup to back up tickets and saves

It's not clear from the guide that ctrtransfers will delete tickets and saves from downloaded games and that restoring a NAND backup restores them too. There's steps to backup and restore tickets in the 9.2 ctrtransfer, but not in the 2.1 ctrtransfer (supposedly this was removed yesterday?). For those that are living on the edge for whatever reason, it would be nice to know this information. Thanks!

Oh! Thanks for this info! I got it clear now. So, basically at the current date, 6th of January of 2017, the 9.2.0-ctrtransfer has become just a troubleshooting guide for those who don't have a functional NAND backup. Therefore, the instructions to backup the installed tickets are only there. It's not on the 2.1.0-ctrtransfer because the guide clearly states that you need to make a backup before proceeding (and it's in bold). If you are not following the guide point per point you get what you deserve. It would be acceptable to place a warning like: "if you don't backup your NAND you will loose your installed titles", this surely will "enforce" somehow the users to make a backup of the NAND. Letting the users know that they can just skip that and backup just the titles is not necessary In My Humble Opinon

The backup is not, and has never been, optional.
I'll extra bold this point in the guide, but I really don't understand the thought process of anyone who just skips the backup.

@lordscales91 Exactly. I understand going without a backup is pretty crazy (which is why I did it twice :^) ), but knowing what happens if you don't is important I think.
The times I backed up were because the SD cards we were using were too small. You really do need something sizable depending on what you have installed - that information would also probably be helpful to know going in.


Fix umlauts being ignored

When trying to speak German texts the umlauts used to be ignored on Windows due to the default encoding.
Setting it explicitly to UTF-8 fixes this error.
The fix was discovered by @hilderonny on issue #49. I can confirm it is working as intended.
Resolves: #49

Thanks

Published in v0.12.0


Throws error when passing in paths

its throws an error saying :Could not read contents of...
this is the command line i entered : swiftplantuml classdiagram Views Model Controllers

Hi, I am sorry you encountered this bug in case multiple file paths are passed. I already have a fix for this which will be part of the next minor version. Release is scheduled within the next 36 hours. Stay patient and you'll be rewarded as next minor version (0.3.0) contains lots of goodies with regards to configuration and filtering files/elements.

Thanks! Its looking good alreat
Kind Regards
Paul Wee

From: MarcoEidinger<EMAIL_ADDRESS>Sent: Monday, March 1, 2021 9:41:15 AM
To: MarcoEidinger/SwiftPlantUML<EMAIL_ADDRESS>Cc: Wee, Paul<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: [EXT]Re: [MarcoEidinger/SwiftPlantUML] Throws error when passing in paths (#12)
Hi, I am sorry you encountered this bug in case multiple file paths are passed. I already have a fix for this which will be part of the next minor version. Release is scheduled within the next 36 hours. Stay patient and you'll be rewarded as next minor version (0.3.0) contains lots of goodies with regards to configuration and filtering files/elements.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://secure-web.cisco.com/1wZWORbsJ-N7aL-RAdjS3zIRgkjrxvR0Dv4_GXQdbt-woyJjTNJE00Rg0Up_65F1epiFS9D4Wg35DN1icyk1_NJNHUusDyZGgnKcwURTBhKYn3MvjvuJy18gfEQ3a0ZURzktXU3CIcFwih4qim_6efx73V0a1w_tEWwJ4KdGqA1N9ynwBxS3aQNUFmtGoxLlY-x8bmFm4GxVDPkyNOLI4K8Anv-lM5ee6KpVAan28gBv_nC3OvTlbWM6qn0yBmRZtHdUqRNBVbmZcSO-E7luZbSO18ZTg2v11PXhDGo1oyg52_q0skScrwaoFD8u_t6oG/https%3A%2F%2Fgithub.com%2FMarcoEidinger%2FSwiftPlantUML%2Fissues%2F12%23issuecomment-787537729, or unsubscribehttps://secure-web.cisco.com/1uk9-xFNjZ4vnv29iOQApARDpum7zyDzHBtZ9oaPrhAzR1ZAzoYNsIUSaa-_VdFE8rv8fU_NlgQnlJTYRMHKnyMOl-QMeBEbNiUWC1Ax72Hx_A-b5514DUPUa-2u-VOSa-JRUuIgEoR3cc2y7sGAbfz0P1sxR4TfQNTDXvNwZjaR0525UBdUra3qDWza5IFgiWiofdpgAp5jT7ydKm3tuCYzATOcH8fTETd23CtjGFopTQJ2F6JrG9X8UAooENZ9Orm0QDpu2PWQGUsReEPqm-K5ZzN-sl8QxywBwJVqJNUN3JGt8zj0scfbF2Zv_lWvm/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FARGHCO3B3NJQIT5YBYBDI23TBLBAXANCNFSM4YLQQ47Q.
This e-mail and any attachments to it are confidential. You must not use, disclose or act on the e-mail if you are not the intended recipient. If you have received this e-mail in error, please let us know by contacting the sender and deleting the original e-mail. Liability limited by a scheme approved under Professional Standards Legislation. Deloitte refers to a Deloitte member firm, one of its related entities, or Deloitte Touche Tohmatsu Limited (“DTTL”). Each Deloitte member firm is a separate legal entity and a member of DTTL. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more. Nothing in this e-mail, nor any related attachments or communications or services, have any capacity to bind any other entity under the ‘Deloitte’ network of member firms (including those operating in Australia).

Hi Paul, issue should be fixed. But if you specify incorrect paths then this error can (as expected) occur. You can use --verbose option for more details. Feel free to open the issue if you still have trouble with 0.3.0

where is the binary for the latest release?

I don't package the binary in the GitHub release artifact but can install the latest version via Homebrew, Mint or install from source. See https://github.com/MarcoEidinger/SwiftPlantUML#installation for details


Publish the most recent 0.2 to crates.io?

Looks like the version has been bumped in the repo but the latest version on crates.io is still 0.1?

I think #9 is the blocker for now

I just published 0.2.0. Sorry to make you wait for long time and thank you for contributing.


Show benchmark results

It would be nice if you ran the benchmarks and showed the results in the README.

@cosarara https://notes.devlabs.bg/realm-objectbox-or-room-which-one-is-for-you-3a552234fd6e

Looks like it is not available at all or for not registered users. So adding results here (or link to truly public resource) would be helpful to attract new users.


Compositor: read the geo data from Thunder, add z-order information

https://jenkins.code.rdkcentral.com/job/github-triggered/609/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/629/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/654/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/656/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/658/ started


Access GUI from remote IP

I installed NPM in my Ubuntu20.04. If I access GUI via <IP_ADDRESS>:81, everything OK. But if I use another host and access public IP of NPM's host, I get "Bad Gateway" error when try to login. How can I fix it? Thank you!

I installed NPM in my Ubuntu20.04. If I access GUI via <IP_ADDRESS>:81, everything OK. But if I use another host and access public IP of NPM's host, I get "Bad Gateway" error when try to login. How can I fix it? Thank you!

I see both logs and realize "Bad Gateway" has no key like this:


isort extension crashes when scoped source.organzeImports action is present

:wave: I'm trying to add a source.organizeImports.ruff action to the Ruff extension. The goal is to enable users who have the isort extension installed to opt-in to sorting imports with Ruff instead, like this:
{
    "[python]": {
        "editor.formatOnSave": false,
        "editor.codeActionsOnSave": {
            "source.organizeImports.ruff": true
        }
    }
}

However, when the isort extension is installed, this configuration causes the isort extension to crash repeatedly, and impedes the Ruff extension's import sorting somehow. (If I uninstall the isort extension, the Ruff extension works as expected.)
(This started with an issue in the Ruff extension repo: https://github.com/charliermarsh/ruff-vscode/issues/76. The use of provider-scoped source.organizeImports was inspired by what I've seen with the ESLint extension, and in this issue: https://github.com/microsoft/vscode/issues/90221.)

Do you have any logs for the crash of the isort extension?

This is the traceback for the error:
Traceback (most recent call last):
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\protocol.py", line 152, in deserialize_message
    deserialize_params(data, get_params_type)
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\protocol.py", line 138, in deserialize_params
    data['params'] = params_type(**params)
                     ^^^^^^^^^^^^^^^^^^^^^
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\lsp\types\basic_structures.py", line 58, in __init__
    super().__init__(**data)
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pydantic\main.py", line 342, in __init__
    raise validation_error
pydantic.error_wrappers.ValidationError: 1 validation error for CodeActionParams
context -> only -> 0
  value is not a valid enumeration member; permitted: '', 'quickfix', 'refactor', 'refactor.extract', 'refactor.inline', 'refactor.rewrite', 'source', 'source.organizeImports' (type=type_error.enum; enum_values=[<CodeActionKind.Empty: ''>, <CodeActionKind.QuickFix: 'quickfix'>, <CodeActionKind.Refactor: 'refactor'>, <CodeActionKind.RefactorExtract: 'refactor.extract'>, <CodeActionKind.RefactorInline: 'refactor.inline'>, <CodeActionKind.RefactorRewrite: 'refactor.rewrite'>, <CodeActionKind.Source: 'source'>, <CodeActionKind.SourceOrganizeImports: 'source.organizeImports'>])

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\protocol.py", line 452, in data_received
    self._data_received(data)
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\protocol.py", line 484, in _data_received
    json.loads(body.decode(self.CHARSET),
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.11_3.11.496.0_x64__qbz5n2kfra8p0\Lib\json\__init__.py", line 359, in loads
    return cls(**kw).decode(s)
           ^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.11_3.11.496.0_x64__qbz5n2kfra8p0\Lib\json\decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.11_3.11.496.0_x64__qbz5n2kfra8p0\Lib\json\decoder.py", line 353, in raw_decode
    obj, end = self.scan_once(s, idx)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "c:\GIT\formatters\vscode-isort\bundled\libs\pygls\protocol.py", line 154, in deserialize_message
    raise JsonRpcInvalidParams()
pygls.exceptions.JsonRpcInvalidParams: Invalid Params

this is due to a bug in pygls where it was using pydantic. The latest version of pygls uses lsprotocol which does not have this problem. lsprotocol is more flexible with code actions.

The fix here is to update isort extension to use pygls with lsprotocol. This will require some minor code changes in server.py.
@charliermarsh you may wat to upgrade pygls as well, and make similar changes to server.py as i will have in the fix for this.

Thank you! (And sorry -- I did not have a trace handy, then meant to come back to this but got distracted.)
@karthiknadig - If it's helpful, I actually did the pygls upgrade a few weeks ago for Ruff: https://github.com/charliermarsh/ruff-vscode/pull/37.

@charliermarsh perfect.


Reorganize manager code

Conceptually the manager is composed of a few distinct functional services like compaction coordination, tablet management, fate, client RPC handling. It may clean up the manager code to put each of these functional services behind an interface and when one functional service uses another it uses the interface.
For example TGW (which is tablet management functionality) currently finds tablets that need to compact and adds them to a queue for the compaction coodinator.  This queue is a stand alone thing that exist in the manager class.  Instead of doing this the TGW could have a refrence to a CompactionCoordinator interface that it adds a compaction job to.
The benefit of this is that it makes it easy to see the depdendencies between functional manager services in the code, separate from the implementation of the functional service.  For example the CompactionCoordinator interface should only have method that are needed by other functional services in the manager like TGW.  If a method is only needed internally in the compaction coordinator, then it would not be placed in the interface, only in the impl class.
Ideally this reorganization would make the manager have almost no code, it would create these functional services and provide references to the interfaces to all the functional services.

This change should probably be done piecemeal.  Going to take a shot at reorganizing compaction coordination to see what it looks like.


created provider.upload_file method; added a CLI

two features:

Added ability to upload file to be hosted by Atlas.  The current implementation requires a URL to a remotely hosted file;  now the URL is optional and a file can be uploaded to Atlas

Added a CLI to improve shell scripting

Note:  rubocop was barking about the version_spec.rb file was too long, so I collapsed a few of the hashes.

lib/vagrant_cloud/cli.rb:64

unused

lib/vagrant_cloud/cli.rb:57

Would be nice if this would fail if "box" is not provided. How about something like

raise 'Missing --box parameter' unless options[:box]

Or maybe there's a nicer way to do it with Thor?

lib/vagrant_cloud/cli.rb:61

Same as above - would be nice to let ther user know this is required when it is requested.

@njam - if I move the options from class_options to method_options and set them as required, this should allow thor to handle the fact they are required.  It's probably the right way to go, so I'll do that.  this will result in a bit of refactoring

@njam - I think this addresses your key concerns.  Let me know if anything else stands out or I missed anything

@njam - sorry, missed your comments the other day.   incorporated both.


Add endpoint to post aggregated metrics, fix S3 client region

Description
This PR includes changes required to support metrics aggregation in dockstore-support https://github.com/dockstore/dockstore-support/pull/452.
Changes:

Added a PUT /{id}/versions/{version_id}/aggregatedMetrics endpoint where admins and curators can put aggregated metrics for a specific platform.
Changed the data type for a few of the Metrics classes because I realized it made more sense while working on the metrics aggregation in dockstore-support

Example: StatisticMetrics had minimum, maximum, and average as a String. My original idea was that a String was better suited because subclasses might have different units, like MemoryStatisticMetric stores memory as GB, so the minimum might be "2 GB". I realized while working on the aggregation functions that it made the most sense to represent minimum, maximum, and average as doubles and to store the optional unit as a String.

Consequentially, I had to change ExecutionTimeStatisticMetric to represent time as seconds instead of ISO 8601 duration format so that I could store the statistics as doubles. Note that in Execution, the user must still submit execution time in ISO 8601 duration.

Changed the fetch types of Metrics and the classes of its fields to eager so that they're loaded when Version.metricsByPlatform is initialized (Version.metricsByPlatform is still lazy loaded).
Added metrics as an include option for workflow endpoints. Did some small refactoring there to reduce duplication. Also noticed that the WORKFLOW_INCLUDE_MESSAGE contained version includes twice, so fixed that.
Fixed the S3 client region error (details here) by removing the hard-coded region so the SDK can automatically determine the region from the environment. Tested this in QA and it works because Fargate containers automatically have the AWS_REGION environment variable set.

This means that when running Dockstore locally, if you want to call the endpoint that submits metrics data to S3, you need to have AWS_REGION configured, either via environment variable or AWS config file.

Added s3EndpointOverride in the Dockstore metrics configuration. This is primarily used for testing so we can provide a LocalStack endpoint override, and integrates nicely with the metrics aggregator tests in dockstore-support

I had to add dummy AWS credential values in the pom for the surefire and failsafe plugins so that the AWS clients are created properly when running tests.
Added localstack to the docker-compose.yml if developers want to call endpoints that communicate with S3 locally. Note that the tests use the localstack java-utils, so it's not necessary to use the docker-compose.yml localstack when running tests.

Modified some things in CommonTestUtilities so that dockstore-support can use them in tests.

Review Instructions
View review instructions in https://github.com/dockstore/dockstore-support/pull/452
Issue
SEAB-5062 and SEAB-5063
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that you pass the basic style checks and unit tests by running mvn clean install
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
[x] If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
[x] Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
[x] Do not serve user-uploaded binary images through the Dockstore API
[x] Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
[x] Do not create cookies, although this may change in the future
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

I realized while working on the aggregation functions that it made the most sense to represent minimum, maximum, and average as doubles and to store the optional unit as a String.

:+1:

Changed the fetch types of Metrics and the classes of its fields to eager so that they're loaded when Version.metricsByPlatform is initialized (Version.metricsByPlatform is still lazy loaded).

:+1:

Based on comments in https://github.com/dockstore/dockstore-support/pull/452#discussion_r1123347424, I added validation of the Execution.ExecutionTime string when users call the endpoint to POST executions to S3. This way, we don't end up with malformed execution times. We get validation for free for the other Execution fields because they're numerical values or enums.
Re-requesting reviews


swagger-maven-plugin not including schema for POST/PUT in case of successfull response in case of Primitive datatype response

Hi,
I am currently using swagger-maven-plugin version 3.1.1-SNAPSHOT and swagger core 1.5.3 .
I am using spring MVC controllers to generate REST API's.
In case of success response,one of the method in controller is returning "String" and another method returning "HashMap<String,String>".Even its been Swagger annotated.But the generated swagger.json and generated html not showing up the schema in case of successful POST/PUT
Controller piece:

@ApiOperation(value="Create Account",
notes="This method will validate the information passed before attempting to create a new Account. It will check if the " +
"accountId, account Name, creation date information is correct. Thereafter, the account creation process starts ",
response=String.class,
consumes="application/json, application/xml",
produces="application/json, application/xml"
)
@ApiResponses(value = {
@ApiResponse(code = 200, message = "Successful response",response=String.class),
@ApiResponse(code = 420, message = "Acccount cannot be created",response=RestErrorMessage.class),
@ApiResponse(code = 500, message = "Unkown error",response=RestErrorMessage.class) })
@RequestMapping(value = "/accounts/{accountId}", method = RequestMethod.PUT)
public ResponseEntity<?> createAccount( @ApiParam(value="This parameter provides account Id for the new account.") @PathVariable("accountId") Integer accountId,@ApiParam(value="This parameter encapsulates new account information.")@RequestBody Account acct) {

@ApiOperation(value="Encrypt String",
		response=HashMap.class,
		produces="application/json,application/xml")
 @ApiResponses(value = {
    	    @ApiResponse(code = 200, message = "Successful response",response=HashMap.class),
    	    @ApiResponse(code = 300, message = "Encryption failed",response=FRestErrorMessage.class),
    	    @ApiResponse(code = 500, message = "Unkown error",response=RestErrorMessage.class) })
@RequestMapping(value = "/encryptionrequest/encrypt/string/{value}", method = RequestMethod.GET, produces = "application/json")
public ResponseEntity<?> getEncryptedValue(@ApiParam(value="This parameter provides the text that needs to be encrypted.")@PathVariable("value") String value)

Generated JSON:
1)
"put" : {
"summary" : "Create Account",
"description" : "This method will validate the information passed before attempting to create a new Account. It will check if the accountId, account Name, creation date information is correct. Thereafter, the account creation process starts ",
"operationId" : "createAccount",
"parameters" : [ {
"name" : "accountId",
"in" : "path",
"description" : "This parameter provides account Id for the new account.",
"required" : true,
"type" : "integer",
"format" : "int32"
}, {
"in" : "body",
"name" : "body",
"description" : "This parameter encapsulates new account information.",
"required" : false,
"schema" : {
"$ref" : "#/definitions/Account"
}
} ],
"responses" : {
"200" : {
"description" : "Successful response"
},

"get" : {
"summary" : "Encrypt String",
"description" : "",
"operationId" : "getEncryptedValue",
"produces" : [ "application/json" ],
"parameters" : [ {
"name" : "value",
"in" : "path",
"description" : "This parameter provides the text that needs to be encrypted.",
"required" : true,
"type" : "string"
} ],
"responses" : {
"200" : {
"description" : "Successful response"
},
HTML snapshots:
1)

@huded
This has been fixed in the latest version.  Please use swagger-maven-plugin 3.1.2.

Hello.
I'm using swagger-maven-plugin 3.1.7 and swagger 1.5.17. When I generate, schema is still not included for primitives types.
My sources :
@POST 	@Path("/prepareLogin") 	@ApiOperation(value = "Prepares CPS authentication") 	@SecuredLogin 	@ApiResponses(value = { 			@ApiResponse(code = HttpURLConnection.HTTP_OK, message = "Prepare login response", response = String.class), 			@ApiResponse(code = HttpURLConnection.HTTP_INTERNAL_ERROR, message = "Internal error", response = ProxyErrorsResponse.class), 			@ApiResponse(code = HttpURLConnection.HTTP_UNAUTHORIZED, message = "Authentication error", response = ProxyErrorsResponse.class)}) 	public Response prepareLogin() 											throws ValidationException { 		String response = this.gConnexion.prepareLogin(); 		return Response.ok().entity(response).build(); 	}
Generate file :
"/connexion/prepareLogin" : {
      "post" : {
        "tags" : [ "Connexion" ],
        "summary" : "Prepares CPS authentication",
        "description" : "",
        "operationId" : "prepareLogin",
        "consumes" : [ "application/json" ],
        "produces" : [ "application/json" ],
        "parameters" : [ {
          "name" : "idApplication",
          "in" : "header",
          "required" : false,
          "type" : "string",
          "default" : ""
        }, {
          "name" : "idApplicationProfile",
          "in" : "header",
          "required" : false,
          "type" : "string",
          "default" : ""
        } ],
        "responses" : {
          "200" : {
            "description" : "Prepare login response"
          },
          "401" : {
            "description" : "Authentication error",
            "schema" : {
              "$ref" : "#/definitions/ProxyErrorsResponse"
            }
          },
          "500" : {
            "description" : "Internal error",
            "schema" : {
              "$ref" : "#/definitions/ProxyErrorsResponse"
            }
          }
        }
      }
    }

Have you an idea?
Thanks
Alexis


Replace broken LNBits link for market listings

Got a DM on the Nostr about this by satoshidude. Here's an example of a broken link. He points to using this new link, I'll have to look into it.

Fixed via #76.


fix: tighten /metrics to internal-only endpoint

We received a report that /metrics is open to the internet which it is.
Usually we expose this in a VPC private endpoint and should do the same here.
See https://walletconnect.slack.com/archives/C03SCF66K2T/p1676627585901279

Addressed during migration from warp to axum


changed: #13 Made Container.New method available on IResolver interface

added: Test for New() on opened scope

Closing for now.


Rename COGReader -> Reader

rio_tiler.io.COGReader is not just for COG but it can be used to read all GDAL Raster dataset!
As this is a pretty big change I'm ok to add COGReader = Reader to keep compatibility

We would also rename rio_tiler.io.cogeo to rio_tiler.io.rasterio (to be inline with stac and xarray


Cannot find module 'better-sqlite3' when running in Docker Container

Expected Behavior
Backstage should start up
Actual Behavior
When trying to start up Backstage in a Docker container we get: Cannot find module 'better-sqlite3'
The fix is to move better-sqlite3": "^7.5.0 from the devDependencies section to the dependencies section in the \packages\backend\packages.json file.
Steps to Reproduce

Ran npx @backstage/create-app to create a instances of Backstage, my version in the backstage.json is 1.2.0
Then I added a Dockerfile to the root and used this, pretty much the same as from the multi-stage docker docks on backstage.io:

# Stage 1 - Create yarn install skeleton layer
FROM node:16-bullseye-slim AS packages

WORKDIR /app
COPY package.json yarn.lock ./

COPY packages packages

# Comment this out if you don't have any internal plugins
COPY plugins plugins

RUN find packages \! -name "package.json" -mindepth 2 -maxdepth 2 -exec rm -rf {} \+

# Stage 2 - Install dependencies and build packages
FROM node:16-bullseye-slim AS build

WORKDIR /app
COPY --from=packages /app .

# install sqlite3 dependencies
RUN apt-get update && \
    apt-get install -y --no-install-recommends libsqlite3-dev python3 build-essential && \
    yarn config set python /usr/bin/python3

RUN yarn install --frozen-lockfile --network-timeout 600000 && rm -rf "$(yarn cache dir)"

COPY . .

RUN yarn tsc
RUN yarn --cwd packages/backend build

# Stage 3 - Build the actual backend image and install production dependencies
FROM node:16-bullseye-slim

WORKDIR /app

# install sqlite3 and TechDocs dependencies
RUN apt-get update && \
    apt-get install -y --no-install-recommends libsqlite3-dev python3 build-essential && \
    rm -rf /var/lib/apt/lists/* && \
    yarn config set python /usr/bin/python3

# Copy the install dependencies from the build stage and context
COPY --from=build /app/yarn.lock /app/package.json /app/packages/backend/dist/skeleton.tar.gz ./
RUN tar xzf skeleton.tar.gz && rm skeleton.tar.gz

RUN yarn install --frozen-lockfile --production --network-timeout 600000 && rm -rf "$(yarn cache dir)"

# Copy the built packages from the build stage
COPY --from=build /app/packages/backend/dist/bundle.tar.gz .
RUN tar xzf bundle.tar.gz && rm bundle.tar.gz

# Copy any other files that we need at runtime
COPY app-config.yaml ./

CMD ["node", "packages/backend", "--config", "app-config.yaml"]

Then make sure your .dockerignore looks like this:

.git
*.local.yaml
node_modules
packages/*/dist
packages/*/node_modules
plugins/*/dist
plugins/*/node_modules

From the root of your project run this to build the docker container: docker image build -t backstage .
Now run the container: docker run -it -p 7007:7007 backstage

Notice the container does not start up and you get this error: Cannot find module 'better-sqlite3'
Context
This prevents Backstage from running in a docker container based on the documentation on Backstage.io
Your Environment
Google Chrome Version 101.0.4951.64 (Official Build) (arm64)
OS:   Darwin 21.5.0 - darwin/x64
node: v14.18.1
yarn: 1.22.18
cli:  0.17.1 (installed)

Dependencies:
  @backstage/app-defaults                          1.0.2
  @backstage/backend-common                        0.13.5
  @backstage/backend-tasks                         0.3.1
  @backstage/catalog-client                        1.0.2
  @backstage/catalog-model                         1.0.2
  @backstage/cli-common                            0.1.9
  @backstage/cli                                   0.17.1
  @backstage/config-loader                         1.1.1
  @backstage/config                                1.0.1
  @backstage/core-app-api                          1.0.2
  @backstage/core-components                       0.9.4
  @backstage/core-plugin-api                       1.0.2
  @backstage/errors                                1.0.0
  @backstage/integration-react                     1.1.0
  @backstage/integration                           1.2.0
  @backstage/plugin-api-docs                       0.8.5
  @backstage/plugin-app-backend                    0.3.32
  @backstage/plugin-auth-backend                   0.14.0
  @backstage/plugin-auth-node                      0.2.1
  @backstage/plugin-catalog-backend                1.1.2
  @backstage/plugin-catalog-common                 1.0.2
  @backstage/plugin-catalog-graph                  0.2.17
  @backstage/plugin-catalog-import                 0.8.8
  @backstage/plugin-catalog-react                  1.1.0
  @backstage/plugin-catalog                        1.2.0
  @backstage/plugin-github-actions                 0.5.5
  @backstage/plugin-org                            0.5.5
  @backstage/plugin-permission-common              0.6.1
  @backstage/plugin-permission-node                0.6.1
  @backstage/plugin-permission-react               0.4.1
  @backstage/plugin-proxy-backend                  0.2.26
  @backstage/plugin-scaffolder-backend             1.2.0
  @backstage/plugin-scaffolder-common              1.1.0
  @backstage/plugin-scaffolder                     1.2.0
  @backstage/plugin-search-backend-module-pg       0.3.3
  @backstage/plugin-search-backend-node            0.6.1
  @backstage/plugin-search-backend                 0.5.2
  @backstage/plugin-search-common                  0.3.4
  @backstage/plugin-search-react                   0.2.0
  @backstage/plugin-search                         0.8.1
  @backstage/plugin-tech-radar                     0.5.12
  @backstage/plugin-techdocs-backend               1.1.1
  @backstage/plugin-techdocs-module-addons-contrib 1.0.0
  @backstage/plugin-techdocs-node                  1.1.1
  @backstage/plugin-techdocs-react                 1.0.0
  @backstage/plugin-techdocs                       1.1.1
  @backstage/plugin-user-settings                  0.4.4
  @backstage/release-manifests                     0.0.3
  @backstage/search-common                         0.3.4
  @backstage/test-utils                            1.1.0
  @backstage/theme                                 0.2.15
  @backstage/types                                 1.0.0
  @backstage/version-bridge                        1.0.1
✨  Done in 3.01s.

This is intended as of the v1.2 release. We removed SQLite from the Docker image as we now consider that to be the production deployment, which uses PostgreSQL. Having the SQLite dependency present in production means we both need to install additional dependencies from APT, as well as SQLite itself, both of which bloat the image and build process.
It's something you can ofc change in your own app though, either by adding back better-sqlite as a prod dependency, installing it separately, or perhaps having a separate development image that runs a full yarn install.
Happy to receive feedback on this change though, if you think there's something we can do that clarifies/simplifies things.

As a relatively new user to Backstage, this added a sizeable "uhhh maybe this isn't ready for prime time" sentiment. If I follow the documentation about how to deploy Backstage, I expect it to work as documented. In this case, it does not.

@jdotw what documentation are you referring to? We probably just missed something when rewriting these docs recently. :pray:

I can't talk for @jdotw nor @awanlin - but i think we all fell into the same trap:
While https://backstage.io/docs/deployment/docker mentions

Something that goes for all of these docker deployment strategies is that they are stateless, so for a production deployment you will want to set up and connect to an external PostgreSQL instance where the backend plugins can store their state, rather than using SQLite.

(Which makes sense as a statement but I think - in the spirit of *-as-code  -there are valid production use cases that will not need/have a PostgreSQL - thus sticking with SQlite)
Further down in the document the multi-stage build installs SQlite dependencies

# install sqlite3 dependencies

and

# install sqlite3 dependencies, you can skip this if you don't use sqlite3 in the image

thus leaving the impression that the Dockerfile example there is 'ready-to-go' for SQlite deployments (and for PostgreSQL one can remove those two lines from the Dockerfile)
Not trying to complain here, just trying to help out as I think Backstage is a great tool though with some rough edges like this one :-)

@derjust some times us as maintainers get a little lost amongst the weeds to be honest, and it's hard for us to pretend to be people that are potentially first time readers, so we would really appreciate some contributions on where you think we could improve the docs or whatever to make it easier to get setup and stop leading you down rabbit holes. 🤗
Like I said previously, we shuffled some docs around and tried to improve some bits, so it could be that we've missed some things, or they don't make sense anymore.

I just ran into the same issue and came across this thread.
Thanks for the comments.

I'm curious around how the local and production config is loaded. I used the create-app method of generating my backbase project and it gave me a backend Dockerfile that had a --config app-config.production.yaml flag at the end. I noticed when it got to Kubernetes, it weren't actually loading the config file and I noticed that I was getting the same error in this issue.
I've since copied the pg database config from the app-config.production.yaml file and put it inside the app-config.yaml file as that's the one that gets loaded in Kubernetes. I've even applied the hotfix to my package.json to put the sqlite dep in the standard deps instead devDeps, and yet I've still recieved the same error in the Kubernetes deployment.
But, when i run a yarn dev, it now starts with the app-config.yaml which is expected, but it tries to connect to a postgres database now. And because the sqlite config isn't in my app-config.local.yaml, it doesn't start. So I've had to manually add it into my local config. But the problem now, is because my local config isn't committed to Git. If someone else was to Clone the repo, they would get the same error when they run the yarn dev and will have to manually add the sqlite config into their local config yaml.

Interesting.
Let me try replicate.
I still haven't figured this out yet myself and was hoping to start using Backstage for my company.
The project has stalled a bit until I can conjure up the courage to give it another go 😅.

I've played around with the Helm chart I'm using and it seemed to be that, that was causing the issue. It was overriding the command when the container started and it wasn't passing it the correct app-config.yaml.

I've just encountered this issue trying to get Backstage up and running just to give it a try. Just wanted to say the documentation is still lacking this information

Having the same issue.... anyone get around it?

Sorry, still no luck.
I gave up on the project until there is better direction on this.

@lenichols The fix is to move better-sqlite3": "^7.5.0 from the devDependencies section to the dependencies section in the \packages\backend\packages.json file.
@markdavidmc0 sorry to hear this has been an issue for you, the above fix does not resolve the problem for you? Could you provide more details then and I can try and help you out?

@awanlin thank you for chiming in with a fix!
For anyone having trouble, I'm curious what path you took to deploy Backstage, just to make sure we can add improvements where needed. Did you go through https://backstage.io/docs/getting-started/, https://backstage.spotify.com/learn/standing-up-backstage/, or something else?

@lenichols The fix is to move better-sqlite3": "^7.5.0 from the devDependencies section to the dependencies section in the \packages\backend\packages.json file.
@markdavidmc0 sorry to hear this has been an issue for you, the above fix does not resolve the problem for you? Could you provide more details then and I can try and help you out?

This fix indeed works. Thank you for commenting. My app couldn't find the module, and then tried to install it with npm install, but only the yarn cli works for backstage.

@Rugvip you're welcome, happy to help. I've created PR #13021 to add a note about this in the deployment/docker documentation. What do you think?

The note above has been replaced by a better solution via #13079


Move cmd/ipxe package to top level and rename tftp & http pkgs

Description

The User experience is a little clunky with both the
cmd/ipxe and top-level ipxe packages. You have to rename imports:
ipxe "github.com/tinkerbell/boots-ipxe"
icmd "github.com/tinkerbell/boots-ipxe/cmd/ipxe"

This puts them both together and simplifies the UX.
The renaming of the tftp (to itftp) and http (to ihttp) packages is being made in accordance with this guidance from the Go team, "avoid using the same name as popular standard packages like io or http." -- ref
Why is this needed

Fixes: #
How Has This Been Tested?

How are existing users impacted? What migration steps/scripts do we need?

Checklist:
I have:

[ ] updated the documentation and/or roadmap (if required)
[x] added unit or e2e tests
[ ] provided instructions on how to upgrade

I know it was discussed at the tinkerbell community meeting this morning that there's also a possible rename of this repository happening. Assuming you'd get this merged before that, this looks good to me.


Provide opt-out install script

Don't merge yet as I am testing this manually but you can start the review. I changed/added lines 112-113. cc @pyronicide

@tamarrow @pyronicide It works. Ready for review.

@jsancio can we have a shared file of common code for the two installers? should we add a test for this?

@tamarrow This is one-off and we should probably rewrite the installers in the future. I'm not sure it is worth the effort of refactoring/testing.

re-running tests.


Restrict cross tenant PLE creation

When creating private endpoint, i can provide any resource ID that may not be within the primary tenant.

Is it possible to block creation of such endpoints?

Is the approach described here (https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/limit-cross-tenant-private-endpoint-connections) the only available option at the moment?

Can you add any security guidance for this use case?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b7d5707-9f14-db2b-00fb-5edd7bbcd06f
Version Independent ID: 2a0f8297-bdf7-3056-121e-963140ec0703
Content: Managed virtual network and managed private endpoints - Azure Data Factory
Content Source: articles/data-factory/managed-virtual-network-private-endpoint.md
Service: data-factory
Sub-service: integration-runtime
GitHub Login: @lrtoyou1223
Microsoft Alias: lle

Thanks for the feedback! We have assigned the issue to the content author to further review this and provide an update as appropriate.

hi @lrtoyou1223 , could you please review the above ask from the customer do share your thoughts ? - Thank you

Is there an update on this request?

The managed private endpoint follows the behavior of standard one. So I think that's the only approach. Please contact networking team for any security guidance.


expose/access position

Hi, thanks for this nice piece of software, super accessible !
is there any way to get the position (row, column) of a cell ?
I did some changes for reading it but maybe it was already there ? Otherwise I could do a pull request with the changes.
Thanks
Michele

Hi Michele, I'm glad you like it.
Row and column information is exposed in the settings object:
$('#seat-map').seatCharts().get('3_5').settings.row
$('#seat-map').seatCharts().get('3_5').settings.column

Thank you !


Can not Modify Display Setting + Rotate Screen

Hello I need help!
I try to modify the Pages Files, since a few days.
But everything I change, will not change in the Display.
I modify the Page Files in /home/volumio/pydPiper-0.3-alpha
I modify the Files pages_lcd_20x4.py and pages_ssd1306.py.
After I press CTL+X , and Restart with sudo systemctl restart pydPiper.
The Display is showing me again exact the same like bevore the modification.
Of course I did reboot also a lot of time.
I seems to me, that I use the wrong Page Files... because the File is modified but shows the old state.
The display is working. I can also chose between the pages files, when I Modify the "ExecStart..." ind pydpiper.service.
And restart with:
sudo systemctl stop pydpiper
sudo systemctl disable pydpiper
sudo cp pydpiper.service /etc/systemd/system
sudo systemctl enable pydpiper
sudo systemctl start pydpiper
I use Raspberry 2B
Volumio 2.834
Oled Display ssd1306
Hifiberry Amp2
I'm a beginner for Raspberry, so I hope i forget maybe a small thing like compiling or something.
I have also a second Question:
is it possible to rotate the display view 180 degree?
Daniel

It is likely that your docker run command does not expose the content of /home/volumio to the container.  Can you send your pydpiper.service file?  You'll need to rename the file to have a txt extention (e.g. pydpiper.service.txt) to attach it to this message.

Hi,
first of all, thank's for the very fast help!
I attached my pydpiper.service file.
I use v0.3-alpha. I have used the installion instructions form "https://github.com/dhrone/pydPiper"
By the way, is it possible to rotate the view of the Display 180°?
pydpiper.service.txt

Now, I got it to work, with your hint.
I used the Example from pydpiper.volumio.service from Master Data and modified it to:
ExecStart=/usr/bin/docker run --network=host --privileged -v /var/log:/var/log:rw -v /home/volumio/pydPiper-0.3-alpha:/app:rw dhrone/pydpiper:v0.31-alpha python /app/pydPiper.py.
Maybe the wrong File is being installed. Or you could at a Description in the Manual, for Noobs like me.
If it would be possible to rotate the display view 180°, then I would be complete satisfied.

You are in luck.  The driver you are using is from the luma.oled project which does support rotation.  pydPiper does not currently expose this capability but it is a simple code change to enable it.  You will need to edit pydPiper/displays/ssd1306_i2c.py line 47.  Change it from...
		self.device = ssd1306(serial)
to
		self.device = ssd1306(serial, rotate=2)
Be careful not to change the indent of the line.  It should line up with the line above it.

If've seen that it should be possible with the luma.oled, but I was not able to choose the right line.
It's working!
Thank you very much!


Type exception from fs.projects.databases.documents.runQuery

Hey @jonasfj (I think you're the only person that responds to tickets on this repo), don't suppose you could have a look at this issue I'm having?
I get the following error:
List<dynamic>' is not a subtype of type 'Map<dynamic, dynamic>'

When I run the a firestore query via the rest API:
  final search = await fs.projects.databases.documents.runQuery(
      RunQueryRequest()
        ..structuredQuery = (StructuredQuery()
          ..from = [CollectionSelector()..collectionId = 'account']
          ..where = (Filter()
            ..fieldFilter = (FieldFilter()
              ..field = (FieldReference()..fieldPath = 'dnUuid')
              ..op = 'EQUAL'
              ..value = (Value()..integerValue = account.dnUuid)))),
      'projects/osapp/databases/(default)/documents');

Full exception
Unhandled exception:
type 'List<dynamic>' is not a subtype of type 'Map<dynamic, dynamic>'
#0      ProjectsDatabasesDocumentsResourceApi.runQuery.<anonymous closure> (package:googleapis/firestore/v1.dart:1444:67)
#1      _RootZone.runUnary (dart:async/zone.dart:1379:54)
#2      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#3      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#4      Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#5      Future._completeWithValue (dart:async/future_impl.dart:522:5)
#6      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#7      _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#8      ApiRequester.request (package:_discoveryapis_commons/src/clients.dart)
<asynchronous suspension>
#9      ProjectsDatabasesDocumentsResourceApi.runQuery (package:googleapis/firestore/v1.dart:1438:32)
#10     migrateAccount (package:migration/migration.dart:195:56)
<asynchronous suspension>
#11     startMigration (package:migration/migration.dart:73:15)
<asynchronous suspension>
#12     main (file:///Users/jimmyff/Development/onescene/migration/bin/server.dart:7:9)
<asynchronous suspension>
#13     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:305:19)
#14     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

It looks like the problem is that RunQueryResponse.fromJson is expecting data of type Map<dynamic, dynamic> however the response from _requester.request() is returning a List rather than Map
package versions:
googleapis 0.54.0
googleapis_auth 0.2.11+1

Propably #25.
Youll need to run the Query manually with the authenticated http client.

We've regenerated the APIs with much higher fidelity. Please try again and comment here if you're still having the issue!

Last I looked into this there was a problem with discovery API documents, which isn't something we can fix in this project.

https://pub.dev/documentation/googleapis/latest/firestore.v1/RunQueryResponse-class.html
There is still only a single document.

Then let's leave it open at least so other people can directly see it's not fixed?


Fixed bug when using gcc8 without fortran.

Fixes #12

@rhornung67 just the one. #4 added similar logic in other places to get rid of a few warnings but that logic isn't present in develop.


Show both Previous and Next slots if the Loop setting is set to true?

I am using the carousel with the loop feature turned on. I am trying to have custom previous and next buttons that display at all times, but it looks like it is set to only display the next button unless the loop setting is false. Can that be changed?

me too, why do have this design?

I having this same issue.  Has anyone found a solution?

me too  ……

You guys may want to try this instead. I never got a response from this developer. The one in the link doesn't have this problem:
https://www.npmjs.com/package/v-owl-carousel


Spec: use of "#" not consistent for escaping rules

(apologies for nit picking)

An escaped character is defined as:

escaped_char     = `\` { `#` } ( "a" | "b" | "f" | "n" | "r" | "t" | "v" | "/" | `\` | "'" | `"` ) .

Whereas octal_byte_value and siblings are defined without the padding character #.
But the escape prefix {#} is also supported for these rules, i.e. it should be defined as
octal_byte_value = `\` {#} octal_digit octal_digit octal_digit .

interpolation is also supporting the padding character, but is defined as

interpolation    = "\(" Expression ")" .

It should be defined as
interpolation    = "\" {`#`} "(" Expression ")" .

This issue has been migrated to https://github.com/cue-lang/cue/issues/795.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Selective IEEE 802.15.4 TX channel

This PR adds the possibility to conveniently specify desired TX channel for every IEEE 802.15.4 transmission.

Converted to draft until updated Nordic HAL is added.

@fgrandel the change is intended to be an optimization for use cases where the channel needs to be changed frequently. Consider a scenario where 802.15.4 API calls are costly, for example in power consumption and/or time, because of implementation details of the driver and the underlying hardware. To reduce the performance penalty in such scenarios, @edmont suggested to allow the channel to provided as a parameter to the transmission. This way only one API call (tx) instead of two (set_channel and tx) can be made to transmit a frame on a channel different than phyCurrentChannel.
One example where such optimization could be beneficial is CSL over multiple channels as described in IEEE 802.15.4-2020 Section <IP_ADDRESS> where macCslChannelMask is nonzero. Probably there are more scenarios where such optimization would be useful, both vendor/protocol agnostic and vendor/protocol specific.
I agree that functionally this change adds redundancy, and as a result it also adds complexity. Personally I'm fine with moving it to a proprietary extension as you suggested. I disagree though that it's out of place to propose such change to the shared namespace.

the change is intended to be an optimization

In this case, this clearly is a premature optimization unless you first prove by measurement that:

There actually is a performance requirement justified by some standard that cannot be met w/o optimization.
The proposed optimization provably solves the performance problem.

As an example see https://github.com/zephyrproject-rtos/zephyr/pull/58439#issuecomment-1585746656.
And then there are much better ways (see architectural concerns below) to improve performance that should be explored first: If we could optimize the established configure() path this would immediately benefit everyone. Can you please trace it so we can analyze the actual bottlenecks?
My architectural concerns with this pattern are:

Standard Conformance: We have an existing pattern that is better in line with standard primitives.
Scalability: If we generally allow this pattern then the number of IEEE 802.15.4 RX/TX parameters that potentially could be added to net_pkt is enormous.
Data Normalization: The packet is used across all interfaces and drivers. From a normalization perspective it clearly isn't the best place for driver/protocol-specific data. IMO none of the subsystem-, driver- and protocol-specific parameters should ever have made it into the packet unless they're actually required in application space or allocated conditionally.
Encapsulation: Parameters that are internal to L2 should not be placed in a structure that is potentially visible outside L2.
Inconsistency: From an API perspective there should be one single way to solve a problem.

One example where such optimization could be beneficial is CSL over multiple channels as described in IEEE 802.15.4-2020 Section <IP_ADDRESS> where macCslChannelMask is nonzero.

A more obvious example for frequent channel changes is channel hopping as macCslChannelMask is just a variant of frequency diversity. I cannot see any obvious reason why macCslChannelMask requires an optimization that channel hopping does not require. The proposed pattern does not work for channel hopping, though (e.g. due to packet fragmentation or re-send requirements that cannot be configured at packet level), so at the very least a pattern should be proposed that works for channel hopping, too.
Overall, given all those concerns, the change simply isn't very convincing.

Overall, given all those concerns, the change simply isn't very convincing.

I understand, you've raised valid concerns regarding scalability, encapsulation etc. Let's then proceed with making this a proprietary extension as you suggested earlier.

Let's then proceed with making this a proprietary extension as you suggested earlier.

Ok.
It would be great if - as a preparatory commit - you could also move the existing OT- and driver- specific parameters to the same file if that's not too much work for you. That way we'd even improve on the existing architecture.
If you check you'll find that almost all of them are either only used for OpenThread or for the nRF5 driver and should not be directly exposed to the subsystem. The only parameters that immediately make sense in application space, AFAICS, are LQI and RSSI.

Lets proceed as discussed and move this feature out of the common namespace.


list all gists

It would be useful for listGists() to return all of a user's gists rather than only those on the first page of results returned by the API.

Yeah, that's exactly what I thought this API would have. Is there no way to list all the gists when a username is passed?

@techtide, you can actually do this already as follows:
var GitHub = require('github-api');
const gh = new GitHub();
const user = gh.getUser('github_user_name');

user._requestAllPages(user.__getScopedUrl('gists'), null, function(err, gists) {
...
}


Update README.md

Added Resources, Project Goals and link to Repo

@microsoft-github-policy-service agree [company="default"]
On Sun, Oct 29, 2023, 13:51 microsoft-github-policy-service[bot] <
@.***> wrote:

@ZaidZaim https://github.com/ZaidZaim please read the following
Contributor License Agreement(CLA). If you agree with the CLA, please reply
with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:

(default - no company specified) I have sole ownership of
intellectual property rights to my Submissions and I am not making
Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work
for my employer (or my employer has intellectual property rights in my
Submissions by contract or applicable law). I have permission from my
employer to make Submissions and enter into this Agreement on behalf of my
employer. By signing below, the defined term “You” includes me and my
employer.

@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the
party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its
affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is
effective as of the latest signature
date below.

Definitions.
“Code” means the computer software code, whether in human-readable
or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft
and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or
distributing code or other content to any
Project, including but not limited to communication on electronic
mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf
of, the Project for the purpose of
discussing and improving that Project, but excluding communication
that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material
Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement
before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now
or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions
is entirely Your original work.
Should You wish to Submit materials that are not Your original work,
You may Submit them separately
to the Project if You (a) retain all copyright and license information
that was in the materials as You
received them, (b) in the description accompanying Your Submission,
include the phrase “Submission
containing materials of a third party:” followed by the names of the
third party and any licenses or other
restrictions of which You are aware, and (c) follow any other
instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include
Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a
contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your
employer has intellectual
property rights in Your Submission by contract or applicable law, You
must secure permission from Your
employer to make the Submission before signing this Agreement. In that
case, the term “You” in this
Agreement will refer to You and the employer collectively. If You
change employers in the future and
desire to Submit additional Submissions for the new employer, then You
agree to sign a new Agreement
and secure permission from the new employer before Submitting those
Submissions.
Licenses.

Copyright License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly
display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all
of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the
Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive,
royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or
the combination of the
Submission with the Project to which it was Submitted to make, have
made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the
Project.
Other Rights Reserved. Each party reserves all rights not
expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without
limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

Representations and Warranties. You represent that You are
legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your
original work (except as You may
have disclosed under Section 3). You represent that You have secured
permission from Your employer to
make the Submission in cases where Your Submission is made in the
course of Your work for Your
employer or Your employer has intellectual property rights in Your
Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You
represent and warrant that You
have the necessary authority to bind the listed employer to the
obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless
You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE
WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED
UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO,
ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of
any facts or circumstances of which
You later become aware that would make Your representations in this
Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to
Projects and information about
contributions may be maintained indefinitely and disclosed publicly,
including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the
laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal
courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in
which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County,
Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire
agreement between the parties, and
supersedes any and all prior agreements, understandings or
communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may
be assigned by Microsoft.

—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/dotnetconf-studentzone/pull/65#issuecomment-1784099003,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKMALB6AIASM2NU26CXAAUDYBZGLRAVCNFSM6AAAAAA6U2K4L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGA4TSMBQGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@microsoft-github-policy-service agree
On Sun, 29 Oct 2023 at 13:55, microsoft-github-policy-service[bot] <
@.***> wrote:

@ZaidZaim https://github.com/ZaidZaim the command you issued was
incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree
and
@microsoft-github-policy-service agree company="your company"
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/dotnetconf-studentzone/pull/65#issuecomment-1784100370,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKMALBYEPGMUDTKHORBQO5TYBZG35AVCNFSM6AAAAAA6U2K4L6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGEYDAMZXGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
📍Berlin
🛠 Spatial Computing Expert @ Ignore Gravity
https://www.ignore-gravity.com/
📢 {TEDx https://www.youtube.com/watch?v=BtnOnz3QZpA | DLD
https://dld-conference.com/speaker/zaid-zaim | GITEX
https://www.gitex.com/} Global Keynote Speaker
🏆 Microsoft MVP
https://mvp.microsoft.com/en-us/PublicProfile/5004287?fullName=Zaid Zaim
🍀 Ashoka Young Change Maker
https://www.hello-europe.eu/young-changemakers
📚 CODE VI http://code.berlin/
✨ ReDI Ambassador https://www.redi-school.org/
LinkedIn: Zaid Zaim https://www.linkedin.com/in/zaidzaim/
Mobile: +4917631508544


Fix Mixed Reality Capture for HoloLens

fixes #830 and cleans up some of the logic around secondary view configurations.

                XrCompositionLayerBaseHeader* secondaryLayersPtr = reinterpret_cast<XrCompositionLayerBaseHeader*>(&secondaryViewLayer);

is this memory valid outside the for loop? This looks like we set a pointer to memory thats invalidated once the loop is completed?

Refers to: Dependencies/xr/Source/OpenXR/XR.cpp:1857 in b14963b. [](commit_id = b14963bd7590ad41f8b32afa1b57ac46e11b1bd2, deletion_comment = False)

                XrCompositionLayerBaseHeader* secondaryLayersPtr = reinterpret_cast<XrCompositionLayerBaseHeader*>(&secondaryViewLayer);

the previous layers vector was clunky, but it was insuring that the structs still existed on the stack

In reply to: 881582063

Refers to: Dependencies/xr/Source/OpenXR/XR.cpp:1857 in b14963b. [](commit_id = b14963bd7590ad41f8b32afa1b57ac46e11b1bd2, deletion_comment = False)


cfo: maintain the count of successful seeds

Add a count: u32 field to seeds. When merging two seeds, sum up the counts.
As a result, for successful seeds, the VOPR would now maintain the total number of fuzzer runs.
This changes the big design here somewhat: the original idea was to keep the set of seeds stable, such that the data in the shared git repository updated only when there are new commits or new failing seeds.
But it seems that the count info is sufficiently useful to justify hammering github after every CFO round (the round is about 30 minutes, so its not too high load).
Note: this PR doesn't yet do any visualization of counts

Praise the mere queue! This PR had a semantic merge conflict, such that tests passed on the branch, the code merges cleanly, but would have failed CI if merged into main!


Syntaxerror: future feature annotations is not defined

I receive the following error when installing and trying to import Python3 in a Google Colab environment:
!pip install -q --upgrade git+https://github.com/KeplerGO/lightkurve.git
import lightkurve as lk

>>>  File "/usr/local/lib/python3.6/dist-packages/lightkurve/lightcurve.py", line 2
    from __future__ import annotations
                                      ^
>>> SyntaxError: future feature annotations is not defined

Oops, Google Colab only appears to support Python 3.6.
The incompatible import is related to type hinting, which isn't very important for now, so I'll remove it.

Thanks for reporting @ojhall94.  This has been resolved via #773.  Please try again!

Can confirm its fixed! Thanks @barentsen!


How to set paper size for Label

I need to print product sticker labels with barcodes and details. so how can I set the paper size for the same

Do you have solution?


RSTP Server?

anyone have any recommendation on using online rtsp server? thanks
I'm currently using rtmp with Youtube and it works great.

You have a list of servers in the wiki page:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/wiki/Media-servers-tested


Add safekeeper membership conf to control file.

Problem
https://github.com/neondatabase/neon/issues/9965
Summary of changes
Add safekeeper membership configuration struct itself and storing it in the control file. In passing also add creation timestamp to the control file (there were cases where I wanted it in the past).
Remove obsolete unused PersistedPeerInfo struct.
Remove the binary representation of cfile in the roundtrip test. Updating it is annoying, and we still test the actual roundtrip.
Also add configuration to timeline creation http request, currently used only in one python test. In passing, slightly change LSNs meaning there: normally start_lsn is passed (the same as ancestor_start_lsn in similar pageserver call), but we allow specifying higher commit_lsn for manual intervention if needed.

While fixing tests added some more changes, updated the PR description.


Supported STContains, STEquals, STArea PostGIS functions for Geospatial datatypes

Description
Implemented Some of the GeoSpatial datatypes like STContains, STEquals, STArea and STSrid. STSrid was important as it was important to cover the edge cases of STContains and STEquals as STContains or STEquals is performed with Geometry/Geography gives Null as per documentation but Was giving error in our case. So to check the SRID of the Object to cover the edge cases STSrid was implemented.
Task: BABEL-5101
Signed-off-by: yashneet vinayak<EMAIL_ADDRESS>Issues Resolved
Task: BABEL-5101
Cherry-picked: https://github.com/babelfish-for-postgresql/babelfish_extensions/pull/2803
Test Scenarios Covered
Use case based - Yes
Boundary conditions - Yes
Arbitrary inputs - Yes
Negative test cases - Yes
Minor version upgrade tests - Yes
Major version upgrade tests - Yes
Performance tests - NA
Tooling impact - NA
Client tests - NA
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 73.562%

Totals

Change from base Build<PHONE_NUMBER>5:
0.01%

Covered Lines:
42487

Relevant Lines:
57757

💛  - Coveralls