discuss: everything is a resource?

Straigt from gitter: https://gitter.im/cs3org/REVA?at=5d722b48ae44a841248d3e73
Hm thinking about the list of incoming, outgoing, trashed and favorite files (and folders) they all look like special storages to me ... the difference is that they only have a single collection with references to other resources in it ...
they could be known to the storage registry ... which presents the list of storages a user has access to ... one of them being the current user home (or his private files) under /home, incoming shares as /shares/incoming, outgoing shares as /shares/outgoing, accepted shares as /shares/accepted ..., trash as /trash, favorites as /favorites, tagged files as /tagged///.../
Jörn Friedrich Dreyer @butonic 11:53
but they actually all just render a collection of references
this is what we did when moving the different custom api calls under the dav endpoint in owncloud
same for versions ... there we actually introduced a meta namespace that we could use for other things as well. it uses /dav/meta//v to list versions end uses /dav/meta//v/ to reference specific versions
Jörn Friedrich Dreyer @butonic 11:58
hm
probably worth discussing at the conference
Hugo Labrador @labkode 13:47
I see a concern in your model: you are tyring to model every piece of the CS3 apis to webdav resources
Jörn Friedrich Dreyer @butonic 14:17
no to storage providers ... the question is if we want to expose metadata as a filesystem or if we want to ad dedicated apis for them
Hugo Labrador @labkode 15:27
the cs3 apis expose APIS for trashbin and versioning
you are mapping those to webdav using custom paths: files-trashbin, files-versions
am I right?
Jörn Friedrich Dreyer @butonic 15:27
yes ...
it pulls the metadata into the virtual filesystem tree
Hugo Labrador @labkode 15:27
I don't think for long term that will best approach for you to follow
you are exposing these functionality as webdav resources, that people can "sync"
Jörn Friedrich Dreyer @butonic 15:28
no
Hugo Labrador @labkode 15:28
i.e they are normal webdav endpoints
if I do a propfind from Finder there, I will get the files locally
same if you want to expose favourites or other infomation
In our case we won't use the phonix webdav endpoint bur rather the grpc directly
and if you want to stick to http, the easiest woudl be to consume a grpc-http JSON gateway
Jörn Friedrich Dreyer @butonic 15:31
people only sync the /dav/files/ tree
Hugo Labrador @labkode 15:32
But these same people have access to the trashbin endpoint, if I got it correctly
Jörn Friedrich Dreyer @butonic 15:32
right so in the future we need to extend the cs3 api should we eg want to implement a service that lists metadata for a user
Hugo Labrador @labkode 15:33
yes, and I think you have already an issue open that listcontainer could return metadata associated with that resource
I think that should be enough
for listing favourites, comments, any metadta attached to a resource
Jörn Friedrich Dreyer @butonic 15:33
why not represent metadata as resources and use storage providers that implement the necessary functionality
it may not work for everything, but it certainly is flexible enough to handle anything I can currently think of.
even search could be implemented that way
versions and trashed files are resources ... we should treat them that way.
maybe something to discuss at the conference
it is definitely somthing we think we did right when revisiting the apis in owcloud
Hugo Labrador @labkode 15:36
In your case that will mean that resource operations needs to be namespaced and not enforce by the semantic of the API
by that I mean, that currenlty you can call ListVersions and you know that you receive the versions of a file
in you case, you will call ListContainer(/versions) and you will return resource types with the type set to "version", that enforces that /versions must be enfornced across the implemtors of the APIs for getting versions
Jörn Friedrich Dreyer @butonic 15:37
yes ... in reva we also have an implicit virtual file tree where we mount storages for a user
Jörn Friedrich Dreyer @butonic 15:52
so for the new /dav endpoint in owncloud we hav several namespaces:
/dav/files// - which is the users home
/dav/meta/ - which allows accessing metadate, currently only versions using /dav/meta//v
/dav/trash-bin// to list the trashbin. in the cs3 api we could return references to paths
/dav/avatars//. to get an avatar for the user - I think here a /dav/users//avatar/. would have been the better choice. It would allow listing users and their properties
I am not saying that we did everything correct, but instead of defining a protobuf spec for eg listing all the above we could repurpose the storage provider ... as a resource provider ...
Then we only need to agree on the type of resource that is listed but avatar pictures are just images. trashbin and versions also list files. users and groups would be interesting because if you want to list the properties of a user ... you could model each property as a (text) file/folder / reference
same goes for user roles ...
Hugo Labrador @labkode 15:55
I have two questions:
Jörn Friedrich Dreyer @butonic 15:55
could be handled with a resource provider
Hugo Labrador @labkode 15:55

Why /dav/meta/fileid does not follow the  convetion

Jörn Friedrich Dreyer @butonic 15:56
because it needs to uniquely identify a resource ... and the fileid is stable
Hugo Labrador @labkode 15:56
2) Those urls work for user-based paths, but imagine a project space that is a not attached to a user, how would you reprensent it?
/dav/project/<project_name>/trash-bin?
and so on?
so for 1) that means that a storage provider for a user will store the favourite information for another user?
Jörn Friedrich Dreyer @butonic 15:57
/dav/projects/ would probably be a more stable way ... but in general i think username and a unique id are interchangeable
oh cool idea
/dav/users/jfd/favorites would be a collection of references
and yes it would be implemented by a separate resource provider, one for listing users and their metadata
you can change the implementation as an admin by mounting a different resource provider to different locations in the virtual tree
that I am using the /dav prefix here is just legacy
but I think we should be able to com up with a good namespace especially to get the group storages or project spaces mounted properly
IIRC some solutions call it places
Jörn Friedrich Dreyer @butonic 16:03
so we could use that as a namespace for storages, eg /places/home/, /place/
same for shares? /shares//incoming outgoing ... well if they are different from places ...
anyway ... this feels right but it just erupted out of me ... so I may need a good round of discussion about this ... at the conference ;-)

I think a certain amount of confusion comes from the different namespaces in every api:
ocdav uses /dav/files/<username or id?> to point to the users home folder
cs3 uses a Reference, which can be a path or a ResourceId, which by design consists of an opaqe storageid and an opaqueid. the storageid is used to rout requests to the correct storage provider without having to do an additional lookup as is the case with the path based reference. reva has a storage registry that allows mounting different storage providers in the namespace.
The question is what do you see when doing a ListCollection with / as the path?
at cern you see /eos, /afs and /projects or something in that regard
The result of ListCollection(ReferencePath('/')) is the root of the CS3 virtual namespace.
we dont have that in webdav
we directly start at the users home folder, which contains a virtual tree that uses mount points to present a single big tree over multiple storages
the ocdav service translates between these two namespaces

The cs3 api uses a namespace for its path based references. If we can agree that the first path segment is reserved to namespaces like /eos, /afs or other storage implementations (?) I can see two other namespaces:

/home for a posix native storage that respects the freedesktop.org conventions for eg trashbin and thumbnails. PR welcome
/som - Storage Object Model: used to expose metadata about files, users and groups.

contains sub namespaces for different resources:

/som/storages/<base62(storageid)>/node/<base62(nodeid)> to access metadata of a resource, maybe call it resource? but I'd like to keep the graph terminology ;-)

can be used to list the existing chunks, eg. /som/storages/<base62(storageid)>/node/<base62(nodeid)>/chunks?
can be used to list the queue progress, /som/storages/<base62(storageid)>/queue/<base62(queueid)>?

/som/users/<base62(userid)> to access user metadata

can be used to list user notifications, eg. /som/users/<base62(userid)>/events?
can be used to acces the user avatar, eg. /som/users/<base62(userid)>/avatar?

size as optional request parameters to the GET request


Update debugger.md for rc2

This checkin updates debugger.md to what I believe we will want for RC2 ship.
There are still a few steps in here which aren't correct quite yet. My next
checkin will add the work arounds which are needed until we ship.

@caslan @Andrew-MSFT @Johnkemnetz please review

Here is the formatted version of the MD file if you would rather review that --
https://github.com/gregg-miskelly/omnisharp-vscode/blob/UpdateDocs/debugger.md

Not sure if "Debugging code compiled on another computer" section is needed. We already mention enabling portable pdbs in "Windows Only" build step in the section right before it.
Do we want to refer to running "Debug: Download Debugger" command in the First time setup section?

LGTM

@caslan, here are my thoughts -
RE Debugging code compiled on another computer - personally I think this section is still useful since the first section had a 'Windows only' label, and this text is useful even if you are just consuming a Windows-built library.
RE Download Debugger - personally I would rather just have people have this happen automatically. But I am happy to change this if others thinks it improves the experience.

When we set up the aka.ms, does it always point to the dev branch version of this doc? When we merge this into the dev branch won't the master branch then point here, "breaking the instructions" for what we officially have in master? Does this matter at all?

http://aka.ms/vscclrdebugger points at master.

never mind then.

Here are my doc plans in full:

Dev: Get the file to look like at RC2 release (no special instructions for fetching the CLI) -- that is what this PR is trying to do.
Dev: add in temporary instructions (install C# extension from GitHub, install .NET CLI in new way)
Master: edit the page to point at dev branch version for folks who want to use newer builds of the CLI
Dev: take an FI from master, ignore all changes
RC2-Doc: Take FI from dev branch
RC2-Doc: Undo the change from step 2.
Wait until we are ready to push RC2 to the gallery
Merge RC2-Doc->Dev, Merge Dev->Master, extension goes live on gallery

Looks good! A few comments:

Under "Your Feedback" can we say "File bugs and feature requests **here **[link you already have] and join our insiders group to help us build great tooling for dot net core [link to http://landinghub.visualstudio.com/dotnetcoreinsiders]"
Under "Prerequisites" you list .NET Core RC2, but also have steps for how to install dotnet CLI. I think the wording just needs to be more along the lines of "only works with the RC2 version of dotnet core"
Prerequisites: Is it any version and SKU of Windows?
Under "First Time Setup" you may want to clarify that people only need to do step 1 from the Dotnet CLI getting started instructions--the rest are about initializing a new sample project.
First Time Setup step 3: How do I know what version of the extension I have?
"Once for each project" step 3: I suggest a small tweak here to clarify what the tasks file is actually doing--eg. "Tasks.json configures Visual Studio Code to run the dotnet CLI build so that your program is automatically up-to-date each time you go to debug it."
Same place: Can we mention that there are three configurations by default in the launch.json file--one for command line, one for web, and one for attaching to a running process? Each one is included as a template/sample for common debugging scenarios and you can modify these configurations to meet your particular debugging needs.

@johnkemnetz I made a bunch of changes based on your feedback. I followed what you suggested except for the multiple launch configuration thing - I thought that made more sense as its own step. Let me know what you think.

Looks good. I'm not parsing this sentence though:
Tasks.json configures the command line tool to run to build your project.
Maybe:
Tasks.json is used to configure the command line tool to generate a build each time you debug your project.

Finial set of changes are now on https://github.com/gregg-miskelly/omnisharp-vscode/blob/rc2-debugger-docs/debugger.md
I don't think we want to go through the dev branch though. So I am abandoning this PR.


[WIP] Auth: Add support for emulator

Adds support for Authentication emulator.
Extracted the URL building to UrlFactory that supports emulator URL that is prefixed to the original URL.
I can add emulators to CI so this is actually tested against the emulator at least.

@nbransby Added an emulator to tests, though this could use more polish (I will take a look at it bit more).
I plan to work on implementing the some of the other FirebaseAuth methods after this PR.


Feature request: support '--reference-liquibase-catalog-name' and '--reference-liquibase-schema-name' parameters

Search first

[X] I searched and no similar issues were found

Description
Liquibase already supports properties:
--default-catalog-name
--default-schema-name

--reference-default-catalog-name
--reference-default-schema-name

--liquibase-catalog-name
--liquibase-schema-name

Thus, there is no support for:
--reference-liquibase-catalog-name
--reference-liquibase-schema-name

Steps To Reproduce
There is no way to specify a separate schema and/or catalog for reference connection that is different to schema and/or catalog of the target connection.
Expected/Desired Behavior
There is support for:
--reference-liquibase-catalog-name
--reference-liquibase-schema-name

Liquibase Version
4.20
Database Vendor & Version
ALL
Liquibase Integration
NONE
Liquibase Extensions
NONE
OS and/or Infrastructure Type/Provider
ALL
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

These arguments would be used for:

In diff/generate-changelog operations, how to compare knows the databasechangelog/lock table names and schemas in the reference database if they are differently named than in the target database
In snapshot-reference, what the databasechangelog/lock table names and schemas are to skip. Currently just liquibase-catalog-name and liquibase-schema-name is used for this, so would need to deal with the case of people specifying both and failing if they are different?

Is there any other usage I'm forgetting?

Mmm yeah this is not working. As of 4.26 at least
Unexpected argument(s): --reference-liquibase-schema-name=secure
Unexpected argument(s): --output-schemas=secure
There might be others that are LISTED in --help for a command but really don't go past the args validation

Thanks for advising @aprognimak ! We will review that.

@tati-qalified are you able to reproduce it?

Ah btw just to clarify - it works when passing the config value via ENV variable or I guess liquibase.properties file would work too (again, as per the diffChangeLog --help) - there's mention in the fine logs about value pickup, but it never even gets past commandline validation if passed via cmdarg.
I am also not sure which other parameters for other commands behave like this, at least outputSchemas does for sure and unfortunately I can't build and run all the integrations at the moment.

Hello @aprognimak - which command are you using that is showing this error? And if you try using --referenceLiquibaseSchemaName=secure (camel case), does it work?

Heh okay this is actually a bit more interesting, I just don't have the time to debug step-by-step, but the gist of it -

If I use commandline "liquibase [all arguments here, including command-specific args] diffChangeLog" the app spews the error about those 2 unknown parameters if present (output-schemas and reference-liquibase-schema-name). If I do not include those "unknown" parameters the thing runs fine and all the rest command-specific arguments are recognized.
If I use "liquibase diffChangeLog [arguments here] parameters are found and taken into consideration and stuff runs just fine

Parameter name case doesn't matter in either cases pardon the pun.
Case 1 is interesting because that's how I found this behavior - liquibase-gradle-plugin uses this to construct cmdline with which it then calls liquibase (all args first, then command name)
Also despite --help explicitly says "command arguments come after command" it works either way just not with the parameters above, makes me think there's some commandline processing flow issue so either it should not work at all or I dunno.
Hope I'm clear, sorry about the initial confusion

Also despite --help explicitly says "command arguments come after command" i

@aprognimak thanks for the detailed explanation, it helps a lot. Requirement for positional commands was dropped sometime ago, so seems we may have a bug parsing them (at least new commands).

@aprognimak it took me a while to navigate through the code and get the history of that . TLDR:  follow  --help directions of  "command arguments come after command" .
Long story: the parameter options that are accepted before any command like 'diffChangelog"  are listed as global legacy commands  and are there for backwards compatibility - new commands are not added to this list. So as output-schemas and reference-liquibase-schema-name are new parameters they need to come after diffChangelog .
Interesting thing: there is a legacy option called --output-schemas-as that should work before the command but not after that as it got renamed to output-schemas .
About  liquibase-gradle-plugin : this is currently under refactoring and I'm in touch with the maintainer , so will ask him to fix it if not fixed it .


Dedicated S3 bucket per log_source

At the moment, only a single S3 bucket seem to be supported as the ingestion bucket.
It would make integration more frictionless if it was possible to define an ingestion bucket per defined log_source. Perhaps make it optional, so that if it isn't specified, the default ingestion bucket will be used.
One use-case is CloudTrail logging, where the organisation already has a S3 bucket with CloudTrail. Being able to point matano at that bucket would avoid the cost of either having CloudTrail send to multiple buckets, or the delay/cost associated with reading from the main bucket and copying to the ingestion bucket.

If I I  understand correctly, this is already supported :)
We call it "bring your own bucket" and it is configured via the ingest.s3_source parameters for bucket_name and key_prefix.
The idea is that we support a Matano managed bucket based ingestion by default for all log sources, but for use cases where there is a pre-existing one  you can onboard it via this configuration (e.g. onboard Cloudtrail).

I read that part of the docs, and the way that I read it is that you can bring exactly one bucket. So all your log sources sourced through an S3 bucket would have to be from that bucket?
Imagine an org that has one bucket for CloudTrail logs, and one bucket per region for Load Balancer logs (since they have to be in the same region as the load balancer).
Or am I misinterpreting the docs, and it's already supported to bring a dedicated bucket to each individual log source?

Yes, it is supported to bring an individual bucket per log source if you use BYOB. Each log source can use a different bucket in the ingest.s3_source configuration.

In that case, I'll close this ticket! Thank you!


Public Docker Container?

Has anyone packaged BindCraft into a public Docker container?

There is some information in these threads:
https://github.com/martinpacesa/BindCraft/issues/64
https://github.com/martinpacesa/BindCraft/issues/23


[Typescript] ListSubheader reject ListItem as component prop

"No overload matches this call."

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Raise a typescript error.
Expected Behavior 🤔
Accept the following props without complaining:
<ListSubheader component={ListItem} divider>

Steps to Reproduce 🕹
https://codesandbox.io/s/create-react-app-with-typescript-c7fcp
Steps:

Try this with typescript enabled:

<ListSubheader component={ListItem} divider>

See this frustrating red line under ListSubheader?

Context
I ran into this trying to make the subheader similar to my list items.
It works well, but I wondered why was typescript complaining. I checked the docs that say:

If you encounter a component that rejects its component props in TypeScript please open an issue.

So here it is.
Your Environment 🌎

Tech
Version

Material-UI
latest

React
16.9.0

IDE
VSCode

TypeScript
3.6.3

i'm taking a look at this, as i'm just learning typescript so it makes sense for me to read trough what you guys are doing :clap:

@cvolant On a side note, the issue use case looks wrong.


Look into automatically importing recipes from websites

There's probably a Python library to parse the hrecipe microformat that many recipe sites use.

Can now print recipes to the terminal if available on a website in the correct format. See https://pypi.org/project/recipe-scrapers/ for compatable sites.


Add dockerize, dev defaults

Stuff for umbrella repo uktrade/data-hub

Can one of the admins verify this patch?


Extend report function

Also mention:

Versions of pygfx and wgpy-py
Version of wgpu-native

Implemented


(feat): Add Gitlab CI/CD pipeline for chaos-exporter

Signed-off-by: Udit Gaurav<EMAIL_ADDRESS>This PR includes the complete setup of Gitlab CI/CD pipelines for chaos-exporter repository.

The pipeline is of three stages:

setup: The cluster setup stage
build: The build stage which contains the task of the running of BDDs.
cleanup: The cluster cleanup stage.

View Pipeline

Can we fix the build stage (an issue/fix would be helpful)


Doc validator/client split

Still under development currently.

This should be ready to doc now.  Nothing special needed on the beacon chain side, there's a validator-client subcommand to run the validator.
Most important point is that the validator keys should only be provided to the Validator Client - definitely never ever pass the validator keys as CLI args to both the beacon node and the Validator Client or it will run the validators in both and get you slashed.


feature: S3C-3568 List Accounts

Upgrade client version
Implement List Accounts
Unit tests for List Accounts

Testing Strategy:
Create the mock AccountServicesClient objects for each service to make sure all the APIs run in parallel with separate mock behaviors

Hello saitharunthodupunuru,
My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.
Status report is not available.

Waiting for approval
The following approvals are needed before I can proceed with the merge:

the author

2 peers

squashed review commits

/approve

In the queue
The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.
The changeset will be merged in:

:heavy_check_mark: development/1.0

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.

Any commit you add on the source branch will trigger a new cycle after the
current queue is merged.
Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.
The following options are set: approve

I have successfully merged the changeset of this pull request
into targetted development branches:

:heavy_check_mark: development/1.0

Please check the status of the associated issue S3C-3568.
Goodbye saitharunthodupunuru.


Duplicated service displayed under MixedRealityToolkit hierarchy (Service Inspector)

https://github.com/microsoft/MixedRealityToolkit-Unity/issues/5968
The issue here is that the facades themselves are persisted to disk when saving (because they are just game objects that exist in the scene)
This change makes it so that the act of saving will cause us to delete those facades (and then also not generate new facades until the save has completed).

/azp run


fix(docker): add missing serve args

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

GitHub release
v0.12.1
v0.12.1

Your semantic-release bot :package::rocket:


Update the handle of OffsetOutOfRangeError.

Set self._fetch_offset = self.auto_offset_reset and let _retry_fetch() to do the do_fetch().
Fix https://github.com/ciena/afkak/issues/57

@rthille  @twm  ^_^

@rthille  Updated tests to check the value change of consumer._retry_call and  the reset offset fetch request sent when auto_reset_offset equals to earliest/latest; raise the error when auto_reset_offset is set to None.

Changes look reasonable now. Not sure why the builds are failing, and I don't have time to dig in further... @twm @zsuzhengdu

Most of the test failures seem to be #36 (test_throughput). This one is new to me, though:
ERROR: afkak.test.test_client_integration.TestAfkakClientIntegration.test_consume_none
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/ciena/afkak/afkak/test/testutil.py", line 88, in wrapper
    return func(self)
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/nose/twistedtools.py", line 169, in wrapper
    raise exc_type(exc_value).with_traceback(tb)
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/nose/twistedtools.py", line 143, in errback
    failure.raiseException()
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/twisted/python/failure.py", line 467, in raiseException
    raise self.value.with_traceback(self.tb)
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/twisted/internet/defer.py", line 1416, in _inlineCallbacks
    result = result.throwExceptionIntoGenerator(g)
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/twisted/python/failure.py", line 491, in throwExceptionIntoGenerator
    return g.throw(self.type, self.value, self.tb)
  File "/home/travis/build/ciena/afkak/afkak/test/test_client_integration.py", line 59, in test_consume_none
    fetch_resp, = yield self.client.send_fetch_request([fetch], max_wait_time=1000)
  File "/home/travis/build/ciena/afkak/.tox/py35-int-snappy-murmur/lib/python3.5/site-packages/twisted/internet/defer.py", line 1418, in _inlineCallbacks
    result = g.send(result)
  File "/home/travis/build/ciena/afkak/afkak/client.py", line 498, in send_fetch_request
    returnValue(self._handle_responses(resps, fail_on_error, callback))
  File "/home/travis/build/ciena/afkak/afkak/client.py", line 566, in _handle_responses
    _check_error(resp)
  File "/home/travis/build/ciena/afkak/afkak/common.py", line 774, in _check_error
    raise error
afkak.common.UnknownTopicOrPartitionError

  py27-lint: commands succeeded
  py27-unit: commands succeeded
  py27-unit-snappy: commands succeeded
  py27-unit-murmur: commands succeeded
  py27-int-snappy-murmur: commands succeeded
  pypy-lint: commands succeeded
  pypy-unit: commands succeeded
  pypy-unit-snappy: commands succeeded
  pypy-unit-murmur: commands succeeded
  pypy-int-snappy-murmur: commands succeeded
  py35-lint: commands succeeded
  py35-unit: commands succeeded
  py35-unit-snappy: commands succeeded
  py35-int-snappy: commands succeeded
  congratulations :)


Denizen Integration

Adds support for Denizen Custom Items by using denizen:scriptname

I need to solve an issue with crafting, then this should be ready

I can't find the problem here, It all looks fine. Are you able to guide me in the right direction?


[Item Alias] a: t

 Issue by [Trimatix#2244]

Originally opened via discord command
Issue type: New item alias

The item
a
New alias
t

test passed, closing


Usage of features

Hi @SophieHYe
It seems that the entity that prepares the features for Repairnator RepairnatorFeatures does not consider the Contextual Syntactic features (i.e., the also named S4R features ).
Here, the code calls to the P4J and later to the ADD.
https://github.com/SpoonLabs/coming/blob/63f470665df627b6ebcba90f809dd1a3e0cda4af/src/main/java/fr/inria/coming/codefeatures/RepairnatorFeatures.java#L151
This way of extracting the features is different than that one uses in the paper, which uses the FeatureAnalyzer.
Am I missing something?
Thanks!

FYI, removed outdated RepairnatorFeatures in #262.


Interested in working with AutoPkg for Windows?

Hi Andrew,
just saw your project. That is a really cool thing.
I am working in the same field, but we use
AutoPkg for Windows.
A few guys have ported the original AutoPkg to Windows, which was not that hard, because it is written in Python. The intention is to port this fork back to the main project ASAP.
What i like the most so far with AutoPkg, that there is already a huge developer and user base on the Mac-side, from which we can profit.
So, i concentrated mostly on building processors for specific task around the Windows Installer field.
Are you maybe interested to merge your project with AutoPkg for Windows?
That would give you more time to focus on the (huge) field around importing and configuring stuff on SCCM.
What do you think about this?
BR, Nick

Hello,
I appreciate the invitation. I will definitely be checking out Autopkg for Windows, but I will not be merging with that project at this time. Thank you!


after installing 2.20.2 update of specto

I cannot play any movie as in when i click on a movie or tv show it says specto encountered an error please check log file. I can search movies/tv shows but cannot get to search sources, instantly i get an error log when i select a movie/tv show episode. MAC jarvis latest kodi (not beta version).
I have attached the log file screenshot if need be.
Thanks.

same here. "specto-...fork error. please check log for details." after selecting any episode or movie.

Uninstall specto , now after you do that go back to. Kodi main screen , hover over system - file manager - add sources - click on None and add this repo http://filmkodi.com/repository and name it Specto , after you add that , go back to kodi main screen and click on system - add-ons - install from Zip - Specto folder - Repository.filmkodi.com.zip , install it , then after that go to install from repository and you will see filmkodi.com-MRKNOW open it and go to video-addons , you should see Specto to install

i had it installed like this from the first version of specto. anyway I did uninstall and reinstall from filmkodi repository...nothing changed. still getting the same error. thanks.

Join The chat room , so we can talk about http://chatwing.com/Karnage11

@StopperN12 Join my chat when you get a chance

i will be back in about an hour and and half

Please update specto to last version 2<IP_ADDRESS>.
10 minutes ago I added new servers so the update should go without problems

hey mrknow

I get the same error message for every show/movie but the latest update appearing 2.20.2


Health and safety info

Hi!
As discussed Edith and myself have been reviewing the info that we could include on the health and safety page. Edith found out that ACM conferences typically include the following 3 type of info:

Privacy Policy: https://www.acm.org/privacy-policy
Code of Ethics and Professional Conduct: https://www.acm.org/code-of-ethics
Policy Against Harassment at ACM Activities: https://www.acm.org/about-acm/policy-against-harassment

Is that something we can do as well for ACM REP?

Thanks @cmaumet, I will include the above links in the conduct page. Anything you want to change/add to the health page?

LGTM! Thank you @carlosmalt!


questions on using make_list.py and im2cc to create dataset

I want to use the script train_imagenet.py in ./example/image-classification to train ILSVRC2012 dataset. I have downloaded the dataset and tried the instructions in page http://mxnet.readthedocs.org/en/latest/python/io.html to prepare the dataset.
After using the script make_list.py in ./tools to process the dataset, the command indeed generates a .lst file. However, the item format in the .lst is different from the format shown in the instruction page.
integer_image_index \t label_index \t path_to_image
The second segment label_index is 0 for all items in the .lst, but not the real label index. A sample file is attached. Is this correct?
Actually, I am quite curious how does the script make_list.py abstract the labab index for a jpeg image.
Thanks for your help!
sample_lst.txt

make_list.py is inconsistent with im2rec.py. Try the latter one.

you should add a argument 'recursive'

you need --recursive=true


Alert - cluster-alerting cannot deploy after add an alert

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Spinning up a GKE cluster.
Config notifier and add an alert group included an alert rule.

Result:
cluster-alerting cannot deploy.

Other details that may be helpful:

Rancher server log

[ERROR] ClusterAlertRuleController c-9rjsz/car-k8b5x [cluster-alert-rule-deployer] failed with : failed to get Alertmanager Deployment information, statefulsets.apps "alertmanager-cluster-alerting" not found, [cluster-alert-rule-controller] failed with : Failed to get service for alertmanager, service "cattle-prometheus/alertmanager-operated" not found

Cluster message

   message: ‘failed to ensure monitoring project name: failed to move Namespace cattle-prometheus
     into a Project: Operation cannot be fulfilled on namespaces “cattle-prometheus”:
     the object has been modified; please apply your changes to the latest version
     and try again’

Seems its lack of monitoring-operator

Environment information
03/06/2019 master

Can not reproduce  in master 3/26. Closing it.


Support numpy like repr function

Reopen #2431 .
This PR breaks backward compatibility.

I also implemented str function.
ex.
>>> a = numpy.array([1., 2.])
>>> print(a)
[ 1.  2.]
>>> v = Variable(a)
>>> print(v)
variable([ 1.  2.])
>>> v = Variable(a, name='x')
>>> print(v)
variable x([ 1.  2.])

Thanks! Your proposal is a nice implementation.
And I added testcase when  shape==(0, 0),

Only at Python 2.7 in Windows, shape is displayed in the form of shape(0L, 0L).
Is it better to branch test by os.platform?
And I don't understand why travis failed. Could you help me?

Only at Python 2.7 in Windows, shape is displayed in the form of shape(0L, 0L).
Is it better to branch test by os.platform?

Yes, please do that.
As for travis failure, I think you should have double blank lines instead of just one (at line 1131 of test_variable.py).

Thanks for your advise.
I don't know the reason why longint is used, and cupy may have different results.

Thank you for your review.
I fixed test name inappropriate test names.
Sorry for inconvinience.

Thank you for the fix!
LGTM!


installer error

Change colorscheme in basic.vim file, do something else instead of desert

You can change it in my_configs.vim 👍


Rotten Flesh has no aspects

Not sure if an intended feature, or possible mod interaction, but in the pack I'm using Rotten Flesh has 0 aspects. Have tried disabling/removing mods to find interactions, but with no success at this time.

Issue found to be duplicate of #975 and therefore closing this.


Fix transaction pool & network issues

Network has too short memory of what peer has what transaction (needs to remember at least 2 full block of transactions).
We should not resubmit transactions that are found both in enacted and retracted block since they are included in the chain despite being part of the retracted block.

it already worked before like this

not true in general case, runtime is not obliged reject duplicated transactions

it already worked before like this

not true in general case, runtime is not obliged reject duplicated transactions

I did not say that this is a bad pr, however all frame runtime's would reject duplicates. Okay not for some unsigned transactions, but that is the reason I said "nice optimization" ;)


Allow calling without username argument

Fixes https://github.com/brutasse/django-ratelimit-backend/issues/31
Unfortunately this breaks a test and I'm not sure what to do about that:
FAIL: test_custom_backend_no_username_key (tests.test_backends.RateLimitTests)
Custom backend with missing username_key
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/mnt/nfshome/plotly/django-ratelimit-backend/.tox/py27-django18/local/lr
    return test_func(*args, **kwargs)
  File "/mnt/nfshome/plotly/django-ratelimit-backend/tests/test_backends.py", ly
    self.assertRaises(KeyError, self.client.post, url, wrong_data)
AssertionError: KeyError not raised

I see that this is testing that a broken backend that does not define a username_key but does not use username results in an error. Unfortunately for the case of OAuth 2 bearer tokens, there's nothing analogous to a username. There's just a token, which takes the place of both a username and password, and tokens should not be logged on failure.
@brutasse @treyhunner Do you have any suggestions on what to do about this?
The test that's failing was added back in https://github.com/brutasse/django-ratelimit-backend/pull/7 .  How important is it to detect a missing username_key? If someone leaves this out by accident I think it's likely that they'll notice when they check their logs and see None where they were expecting an email address or whatever. But I'm open to other suggestions!

Here's another idea: define a no_username attribute that makes authenticate skip the username.
So:
if self.getattr(no_username):
    username = '[no username]'
else:
    username = kwargs.get(self.username_key)

Then, so ratelimit-backend can be used out of the box with OAuth bearer tokens, also add a class to backends.py:
class RateLimitOAuthModelBackend(RateLimitMixin, ModelBackend):
    no_username = True

@brutasse If this sounds OK I can update this PR and write a test for the new behaviour.

After further thought I'm convinced https://github.com/brutasse/django-ratelimit-backend/pull/32#issuecomment-321599918 is the right way to go. I'll open a new PR with that solution.


Orchestration Aborted Error while doing gulp build

I am getting below error when I do gulp build command. I took this solution from my colleague and did npm install. What is the reason for this?

In addition to the above, is this a clean/new project with no changes? Share your package.json? Not enough information provided to help much at this point...

@andrewconnell below is my package.json file.
This solution is for SP2019.
{
  "name": "aamvasp-fx-solutions-v-1-0",
  "version": "0.0.1",
  "private": true,
  "engines": {
    "node": ">=0.10.0"
  },
  "scripts": {
    "build": "gulp bundle",
    "clean": "gulp clean",
    "test": "gulp test"
  },
  "dependencies": {
    "@microsoft/sp-core-library": "1.4.0",
    "@microsoft/sp-lodash-subset": "1.4.0",
    "@microsoft/sp-office-ui-fabric-core": "1.4.0",
    "@microsoft/sp-webpart-base": "1.4.0",
    "@types/es6-promise": "0.0.33",
    "@types/react": "15.6.6",
    "@types/react-dom": "15.5.6",
    "@types/webpack-env": ">=1.12.1 <1.14.0",
    "react": "15.6.2",
    "react-awesome-modal": "^2.0.5",
    "react-dom": "15.6.2",
    "tippy.js": "^4.3.5"
  },
  "devDependencies": {
    "@microsoft/sp-build-web": "1.4.1",
    "@microsoft/sp-module-interfaces": "1.4.1",
    "@microsoft/sp-webpart-workbench": "1.4.1",
    "gulp": "~3.9.1",
    "@types/chai": ">=3.4.34 <3.6.0",
    "@types/mocha": ">=2.2.33 <2.6.0",
    "ajv": "~5.2.2"
  },
  "resolutions": {
    "@types/react": "16.4.2"
  }
}

Below with npm list -g --depth=0

@andrewconnell I have added my solution to visual studio online. If I download that package and run the 'npm ithengulp build` then it is throwing this error.

Can't tell what the issue is based on the provided information. Clearly something to do with TypeScript... that could be because of dependencies.
Have you created a brand new SPFx project for SP2019, with no edits, and tried building it? If that works, it's something wrong with your project. If it doesn't work, it's something wrong with your workstation.
I notice you're running old versions of the following

@microsoft/generator-sharepoint (but upgrading this won't make much of a difference)
Node (you're on v8... you should be able to use Node v10, the current LTS version even though you're using SPFx v1.4.1) <<< this could very well be the root of the issue...
npm (full major version behind)

Strange thing is I have created this solution in my machine and worked perfectly. Then I have pushed this to Visual Studio online. I have shared this solution to client. Client is trying to build from his end which is failing. Now I have downloaded, from VS online to another folder then executed npm i  then gulp build which is giving error, but same solution i have pushed from another folder which is working.

Well, something is clearly different between the two projects on your machine if one works & one doesn't. Use a diff tool to examine the two package.json files, examine the lock files for the package manager you use, use a diff tool to do a deep comparison of the two folders, etc ... something is definitely different.
I'm going to close this as resolved as you have one working so there's action to take...


Fix behavioural differences due to return type and handle constant string literal inputs differently for COALESCE function

Description
Behavioural differences mentioned below have been found out better PG Coalesce and T-SQL Coalesce function.

Consistency in return datatype i.e., for the same set of input datatypes T-SQL should return consistent return datatype as shown in below example

-- T-SQL
select coalesce(cast(8 as smallint), cast(1 as bit))
go
~~START~~
smallint
8
~~END~~
select coalesce(cast(1 as bit), cast(8 as smallint))
go
~~START~~
smallint
1
~~END~~

-- BBF

select coalesce(cast(8 as smallint), cast(1 as bit))
go
~~START~~
smallint
8
~~END~~
select coalesce(cast(1 as bit), cast(8 as smallint))
go
~~START~~
bit
1
~~END~~

When the input is constant string literal i.e., T-SQL should take short circuit evaluation meaning unnecessary arguments should not be evaluated

-- T-SQL
1> SELECT COALESCE(NULL, 1, 2, 'I am a string')
2> go

-----------
          1

(1 rows affected)

-- BBF
1> SELECT COALESCE(NULL, 1, 2, 'I am a string')
2> go
Msg 22, Level 16, State 1, Server BABEL, Line 1
invalid input syntax for integer: "I am a string"

This change adds a new function select_common_type_for_coalesce_function to choose the return datatype which will be called from tsql_select_common_type_hook whenever the caller function is T-SQL COALESCE.
Issues Resolved
[BABEL-726]
Engine PR : https://github.com/babelfish-for-postgresql/postgresql_modified_for_babelfish/pull/345
Signed-off-by: Sai Rohan Basa<EMAIL_ADDRESS>Test Scenarios Covered

Use case based - babel_726.sql

Boundary conditions - Yes

Arbitrary inputs - Yes

Negative test cases - Yes

Minor version upgrade tests -

Major version upgrade tests -

Performance tests - N/A

Tooling impact - N/A

Client tests - N/A

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>
Details

43 of 43 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 72.964%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tds/src/backend/tds/tdsresponse.c
1
79.82%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
41207

Relevant Lines:
56476

💛  - Coveralls


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^3.13.0 remove ^3.12.1 (devDependencies.ava)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Websocket Closing After 1 Minute

First, I love this module thank you for making the Mendix Websockets as easy as possible.
On deployment of our application, the websocket is closing after one minute exactly. I have set to 0 timeout time on the startup of the websocket but it is still closing. I only have this issue when deployed (both on Mx Cloud and Mx4PC) when running locally it stays connected.
Any help would be appreciated!

Hi BWeinbergImpact,
This is the first time Im hearing about this.
Do you have the KeepAlive setting turned off or do you have specific changes in runtime settings surrounding sessions?
https://docs.mendix.com/refguide/custom-settings/#web-client-settings

I created a new application, downloaded ez websockets, copied the way the test application was setup, and deployed it to Mendix free app. It still closes after 1 minute.
https://testwebsockets102-sandbox.mxapps.io/

Thanks for showing me, I have no idea how noone (including me) noticed this before.
It seems like there is some sort of server configuration which cleans up idle connections.
I will use the coming week to implement a keepalive mechanism, which I expect to publish next sunday.

Awesome, thank you!
Is it possible to get a backport of that fix for Mx 9 LTS (9.24.25) when you get it fixed?

I've been working on some necessary refactoring, and I'm happy to report that I've succesfully implemented the keepalive mechanism. There are still a few final details and some configurability options that I want to include before publishing the final results to the marketplace, so it will take a little longer to get it out.
If you're interested, check out the latest commit for a preview

Awesome, thank you!
Is it possible to get a backport of that fix for Mx 9 LTS (9.24.25) when you get it fixed?

If there more demand for it I might consider

Small update, finished all the devwork, improved DX experience now that sessionTimeout is irrelevant for most usecases
Tested on free tier mendix cloud and looks like its working as expected 😄
Also switched sending literal "ping" and "pong" strings down the line for the built-in websocket protocol ping and pongs, so that they won't clog up your devconsole traffic
Because I've changed up the whole thing I need to update the docs, after that I will publish

Just published the new version, with proper keepalive mechanism,
enjoy, and thanks for helping me make the module even better! 😄
https://marketplace.mendix.com/link/component/205276

Thank you for the quick turnaround!


adopt apiVersionEnum which will filter out unnessary apiversions

Fix https://github.com/microsoft/typespec/issues/4110
TCGC will filter out the apiVersions for sdk emitters, and give out an api-version Enum:

filter out the api-version later than the default api-version specified

filter out preview api-version when the target api-version is stable version.

This PR will use the tcgc apiVersion Enum type to do the api-version filter.

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

autorest.csharp regen preview pr: https://github.com/Azure/autorest.csharp/pull/4981


EditorInterface.set_main_screen_editor doesn't work if open_scene_from_path has been called before

Godot version
4.1.2.stable
System information
Godot v4.1.2.stable - Windows 6.3.9600 - Vulkan (Forward+) - dedicated GeForce GT 1030 () - AMD Ryzen 5 3600 6-Core Processor (12 Threads)
Issue description
When creating a plugin that adds a dock to the editor, the method set_main_screen_editor stops working if an scene has been previously opened with open_scene_from_path
PS: I don't know why Godot reports my Windows version as 6. It's 8.1
Steps to reproduce

Create a plugin that adds a dock to the interface
Add a Control that triggers a function in the dock script
Change the main screen using set_main_screen_editor
Open a scene using open_scene_from_path
Try and change the main screen again

Minimal reproduction project
godot_test.zip

Similar issue occurs when calling edit_node after set_main_screen_editor so I suspect modifying the interface with EditorInterface in general is broken


zodToJsonSchema tries to evaluate .preprocess with undefined passed in

To reproduce, use https://github.com/Firfi/zod-to-json-schema-preprocess-bug
For such code as
const idParser = z.preprocess(
  (uuid) => {
    if (typeof uuid !== 'string') throw new Error(`Expected string, got ${typeof uuid}: ${uuid}`);
    const [type, id] = uuid.split('SEPARATOR');
    return { type, id };
  }, z.object({ type: z.string(), id: z.string() }));

zodToJsonSchema(idParser) will be evaluated all right, however
if I do
const idParser2 = z.object({
  id: idParser
})

zodToJsonSchema(idParser2) starts passing undefined into preprocess (as my uuid var)
I wonder if that's expected behaviour and why it happens only when a parser is used inside z.object

I've added a note about this issue in the readme. Closing this for lack of activity in the meantime but let's keep an eye on the issue in Zod


Set the right account type

updated the config of account types
updated the code
added unverified (-1)

 Fix account type in the og preview


test: migrate messages to snapbox

What does this PR try to resolve?
Part of https://github.com/rust-lang/cargo/issues/14039.
Migrate following to snapbox:

tests/testsuite/messages.rs

:umbrella: The latest upstream changes (presumably #14243) made this pull request unmergeable. Please resolve the merge conflicts.

:umbrella: The latest upstream changes (presumably #14299) made this pull request unmergeable. Please resolve the merge conflicts.

@bors r+

:pushpin: Commit f9026f188436dde10b55b12cd1a20345e5f86a8a has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit f9026f188436dde10b55b12cd1a20345e5f86a8a with merge b9e432ad04d194f66a62a761f7189b335efa7518...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing b9e432ad04d194f66a62a761f7189b335efa7518 to master...


Update quick report PAW "host" link in PAx reports using TM1Py

Hi
I am looking to find out if there is a function within TM1py v1.5 to update quick report PAW "host" link in PAx reports using TM1Py. If this functionality currently doesnt exist and if it is possible via REST API, can this be added to enhancements list for next releases. Currently when we move between environments, only way to change the host link is to go into each excel file and change the host link for all quick reports in PAX.
Happy to provide more context into the use case if required.
Thanks
Vishu

Pax reporting functionality is not available via the tm1 server api. Those types of things can be handled via the Pax vba api, and you should look to build something using that.
Ryan Clapp
Sr. Manager
AWS FinTech
Sent from my mobile device
On Jul 16, 2020 1:32 PM, vishwesh999<EMAIL_ADDRESS>wrote:
Hi
I am looking to find out if there is a function within TM1py v1.5 to update quick report PAW "host" link in PAx reports using TM1Py. If this functionality currently doesnt exist and if it is possible via REST API, can this be added to enhancements list for next releases. Currently when we move between environments, only way to change the host link is to go into each excel file and change the host link for all quick reports in PAX.
Happy to provide more context into the use case if required.
Thanks
Vishu

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/issues/289, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEK7GZQ3WSQQQ5ZN7BBWZVTR35PJXANCNFSM4O44LHEA.

Got it, thanks for quick response - will look into the PAx VBA API.
Regards
Vishu

Hi @vishwesh999, Hi @rclapp,
I don't think this approach necessarily leads to a dead end.
I took a closer look at the xlsx files of the quick reports and found that the relevant information (server) is stored inside a JSON in a named range.
The key is tm1\\_0_H.
With a python excel library like openpyxl we can manipulate this value (without actually opening the file with excel).
Below you find a sample.
Obviously, with TM1py we can retrieve any applications as an xlsx file - and send it back to TM1.
More analysis is needed in order to assess the feasibility, but I will re-open this issue for now.
from openpyxl import load_workbook

wb = load_workbook('excel.xlsx')
defined_name = wb.defined_names[r"tm1\\_0_H"]

del wb.defined_names[r"tm1\\_0_H"]

defined_name.attr_text = defined_name.attr_text.replace(
    "http://rb-paw-x.prod.cubewise.com/",
    "http://rb-paw-x.dev.cubewise.com/")

wb.defined_names.append(defined_name)

wb.save("excel2.xlsx")


u32and should accept err

Similar to https://github.com/0xPolygonMiden/miden-vm/issues/1264 , but for the instructions u32and. The VM halts if the operands are not u32, and a error code would be benefitial.

There are actually quite a few instructions that can trap for various reasons, and have this issue. One can work around this specific case by using u32assert.err=ERR on the operands at least, but that's definitely a pain.
I think the larger issue of being able to pinpoint where an error/assert was triggered will need to be solved with debug info. Without debug info, even when you can specify an error code, it is still not particularly helpful in quickly finding the cause. With debug info, we can at the very least provide the location in the original source code, and in cases where we have sources available, we can even render the source snippet that is relevant. More importantly, it would work well across all instructions, whether the error is explicitly triggered with an assert, or implicitly triggered by the semantics of a specific instruction.
Maybe we should add a tracking issue for that, where we can work out the details, and link all these issues to that one?

@bitwalker sounds good to me 👍

One note: adding error codes to instructions which also support immediate values may be a bit tricky (or at least may require modifying syntax a bit). So, this may conflict a bit with #1301.

@bobbinth I think it could be an either or situation:
u32assert.err=ERR
u32and.0xFF

OR
u32and.err=ERR

In other words, validating the sole operand for the immediate variant is trivially done with u32assert.err=ERR, so we probably don't need to support both at the same time.

We could do the same for both operands:
u32assert2.err=ERR
u32and

And this will actually be faster than using u32assert as u32assert is just syntactic sugar on top of u32assert2 (so, u32assert2 takes 1 cycle while u32assert takes 3 cycles).

Ah right, always forget about u32assert2!

@bobbinth @bitwalker So what is our approach? Do we stick with an u32assert2 and bitwise ops without immediate values? Or though it is preferable it will be still good to have immediate values for bitwise operations?

IMO if one has to choose, it makes sense to support immediates first, error codes second, since one can use assertions before an op to obtain useful errors and therefore get the best of both worlds. But I think a compromise here is to simple make it an either/or situation, i.e. you can either use immediate operands, or specify an error code, but you can't do both. This lets you choose an option that is most appropriate for the situation.
I do think we could support both at the same time, by requiring the .err=CODE to always precede all immediate operands, so you'd have something like u32and.err=EINVAL.0xFF - it's a bit syntactically noisy though, so I wonder if anyone would prefer writing that versus the slightly more verbose, but less dense version with two instructions.
Thoughts?

I agree, I think that an either/or compromise is a good solution for now indeed.
Supporting them both at the same time looks a little overloaded for me, but I can't come up with a better solution. Also I think that an ordering of the immediate value and an error code can be any: AFAIK lalrpop allows to parse them in any order. Motivation for this is that user probably won't remember the correct ordering, so it will be more user-friendly to support both. But it will make parsing more complex, so I don't have a strong preference here.

Here are my thoughts:

I don't think we need to support syntax where we specify both an immediate value and an error code.
We could support either/or (i.e., either immediate value or error code), but I'm also not sure the extra complexity is worth the benefit we are getting.
We could also just keep things as they are. This does not add any more complexity to the parser/assembler, and does not make things any more complicated for the user while adding only 1 extra cycle. Specifically:

u32assert2.err=SOME_ERROR
u32and

Is not all that much worse than:
u32and.err=SOME_ERROR

And actually makes the condition for the error a bit more explicit.
Basically, unless someone has a strong preference for the second option above, I'd rather just close this issue.

Based on the discussion above, closing this as not planned.


Duplicate nicknames

This isn't a big deal, but we probably want to protect people from accidentally overwriting files, i.e. e.renter.Files[nickname] already exists. I'm not sure what the best way to do this is. We could make ClientProposeContract throw an error, but then you can't overwrite at all. Maybe a client-side warning would be better. Do we have a process in place for deleting files/early termination of contracts? My feeling is that the proper interaction is:

"That nickname is already in use. Overwrite? (Y/N)"
If Y: create the new contract and call Delete() on the old contract
If N: cancel

We may also want to do away with nicknames entirely. Most cloud storage applications don't use them, preferring instead to just use the original filename.

There's nothing wrong with the backend supporting nicknames and the frontend ignoring that fact.
You can't overwrite nicknames on the backend, because you can't delete things. We can add some functionality to rename stuff though.


ci: add nodejs v16 to test matrix

Checklist

[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

Pull Request Test Coverage Report for Build 786652889

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.554%

Totals

Change from base Build 732863793:
0.0%

Covered Lines:
408

Relevant Lines:
408

💛  - Coveralls

tks! LGTM


Cstruct thumbprint

Fixes #43
There' some duplicated code after this that should be removed to use the same implementation as thumbprint.

@Lupus please look at this PR, is this what you would expect for thumbprint?

Yes, looks great! Thanks! :)


Heading references should be explicit about punctuation

Identifiers are added automatically to any headings that do not have explicit identifiers attached to them. The identifier is formed by taking the textual content of the heading, removing punctuation (other than _ and -), replacing spaces with -, and if necessary for uniqueness, adding a numerical suffix

it's not clear how Unicode-aware this is; this could mean that only ASCII punctuation is stripped (leaving other Unicode characters verbatim) or it could mean that all characters that aren't _, -, letters, and numbers are all stripped. This should probably be clarified. Personally, I feel that the best approach would be to simply declare that while implicit references are stripped, unless an explicit {#ID} attribute is added, the reference can be replaced with anything.
Personally, I think that simply relying on {#ID} is best, since people can still use the implicit references and if they need to make a reference that's stable outside the document, they can explicitly define one.

In the current implementation, only ASCII punctuation is stripped...mainly because Lua doesn't have good built-in unicode support.  But your idea of telling people that they shouldn't have any definite expectations about automatically generated ids, and should always use an explicit id when they want to enable linking to a section from outside a document, is probably a sensible one!


Path Manager 2

Rebasing was giving me serious problems, so I resorted to creating a new branch off of Devel. Old PR can be found here.
All that really remains is deciding on what desired airspeed we should set for cruising state. Will talk to y'all on Tuesday about that tho.

Tuesday's meeting is cancelled for finals. Hardcode 25 m/s airspeed. It'l have to be something we tune later, but that's a decent first guess


Help needed: Implementing "Sign in with Google" in .NET MAUI

Is there an existing issue for this?

[x] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
Hi dotnet,
I am currently learning .NET MAUI and trying to implement the "Sign in with Google" feature. However, I am facing some difficulties, as I need to do this without using Microsoft Azure, as per my teacher's recommendation.
Could you please guide me on how to implement this feature or share any resources or sample code that could help? I would greatly appreciate your support!
Thank you in advance for your time and help.
Best regards,
Nazrin
Describe the solution you'd like
Hi dotnet,
I am currently learning .NET MAUI and trying to implement the "Sign in with Google" feature. However, I am facing some difficulties, as I need to do this without using Microsoft Azure, as per my teacher's recommendation.
Could you please guide me on how to implement this feature or share any resources or sample code that could help? I would greatly appreciate your support!
Thank you in advance for your time and help.
Best regards,
Nazrin
Additional context
Hi dotnet,
I am currently learning .NET MAUI and trying to implement the "Sign in with Google" feature. However, I am facing some difficulties, as I need to do this without using Microsoft Azure, as per my teacher's recommendation.
Could you please guide me on how to implement this feature or share any resources or sample code that could help? I would greatly appreciate your support!
Thank you in advance for your time and help.
Best regards,
Nazrin

Hello! Unfortunately this request is outside of the scope of our support, your question is more suited for the https://stackoverflow.com/ forum or our tech community forum https://learn.microsoft.com/answers

Thank you for answering my question


Conformance granularity?

As I'm working through implementing some of the write operations, I've been thinking about whether it might be worthwhile to consider some kind of qualification to the Conformance mark -- particularly for pre-existing repositories (like IGC, Atlas, and others) that are (probably all?) likely to only support a subset of the open metadata types rather than all of them...
Should we make it clear somewhere / somehow with which subset of the open metadata types a given repository is Conformant?
I think this would be very valuable for anyone shopping around for repositories, to be able to consider how broad its support is for the open metadata types of interest to a particular use.  Just seeing that a repository is broadly Conformant (but not qualifying for which open metadata types) leaves it open to misinterpretation that a Conformant repository can carry out its conformed activities on all open metadata types.
Taking IGC as an example, I would hope to achieve:

profile
types

Metadata sharing
for 10's of open metadata types across entities, classifications and relationships

Metadata maintenance
for ~5 open metadata entity types, ~5 classifications and ~10 relationships

Non-conformance
for 100's of open metadata types

Marking IGC as "conformant" for metadata sharing (without any qualification) when it only supports a small percentage of the types doesn't answer the user question of "I need it to share information about instances of type X, can it do that?"
Same when marking IGC as "conformant" for metadata maintenance (without any qualification) when it only supports an even smaller percentage of the types (eg. "I need it to maintain information about instances of type Y, can it do that?")

Which implies to me that if we go in the more granular (type-by-type) direction, it would be ideal to have this separation against each of the profiles themselves -- as even in the same repository the types that conform to one profile vs another may differ...
I'm assuming that we probably get to this level of granularity in the CTS itself by cycling through the types that we detect a given repository tells us it can handle; but I'm not sure we're "rolling it up" into a reported form?  (Trying to go through the entire CTS output would be pretty arduous to answer the basic questions above...)

@cmgrote This was considered when we put the conformance mark together.  The mark is showing that the repository can safely added to the cohort.  In addition there is the report from the tool that goes into the detail of which requirements are covered - it would be this report that is used to compare repositories and is the qualification that you are asking for.
The good thing about the CTS is that anyone can run it - so if an organization is comparing repositories, they can run (or ask the vendor to run) the CTS as part of the procurement process.

Is there an easy way to generate a list of the types that are supported by a given repository? (Not a runtime question - i.e. not using getAllTypes() :0-)

Is there an easy way to generate a list of the types that are supported by a given repository? (Not a runtime question - i.e. not using getAllTypes() :0-)

I'll have a deeper look once the broader set of CTS changes are in, but I thought the CTS already makes use of getAllTypes() as one of its early steps to determine what types to use when invoking other methods -- if so, then there is implicitly a list of types that the CTS is testing against, and that we could therefore report from the CTS.
So I think all of that detail is in the CTS, I'm just keen on investigating whether there's a sub-report or the like that we could create that "rolls up" this summary on a type-by-type basis for easier digestion than reading through all of the detailed tests 😉

Agreed - it's the availability of the generated digest/report that I was asking about

Looking at the spring module for the CTS I can see the following URLs:
(GET) /report - returns the whole enchilada
(GET) /report/test-cases/{testCaseId} - will report on an individual testcase
(GET) /report/test-cases/failed - will report on all failed test cases
(GET) /report/workbenches/{workbenchId} - provides info on level of conformance for given workbench
My system is in the middle of a full CTS run at the moment but when it has finished I will experiment with the above

I think the API is close but does not quite provide what we are looking for.
You can interrogate the CTS server to give the results of a given test case - but that requires that you specify the type that was being tested, as the testCaseId in the above URL is formed like this:
repository-entity-lifecycle-Asset
The above example is specifying the entity lifecycle test case for the type Asset.
If you GET from that URL you will get something the following, but you would have to od once per type. I think we are seeking a summary of 'types that this repository supports'.
http --json --pretty all  GET localhost:8080/servers/CTS1/open-metadata/conformance-suite/users/garygeeke/report/test-cases/repository-entity-lifecycle-Asset | tee /tmp/cts_result
{
"class": "TestCaseReportResponse",
"relatedHTTPCode": 200,
"testCaseResult": {
"class": "OpenMetadataTestCaseResult",
"discoveredProperties": {
"Asset soft delete support": "Enabled",
"Asset undo support": "Disabled"
},
"notSupportAssertions": [],
"successMessage": "Entities can be managed through their lifecycle",
"successfulAssertions": [
"repository-test-case-base-01: Repository connector supplied to conformance suite.",
"repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
"repository-test-case-base-01: Repository connector supplied to conformance suite.",
"repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
"repository-test-case-base-01: Repository connector supplied to conformance suite.",
"repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
"repository-entity-lifecycle-01: Asset new entity created.",
"repository-entity-lifecycle-02: Asset new entity has createdBy user.",
"repository-entity-lifecycle-03: Asset new entity has creation time.",
"repository-entity-lifecycle-04: Asset new entity has correct provenance type.",
"repository-entity-lifecycle-05: Asset new entity has correct initial status.",
"repository-entity-lifecycle-06: Asset new entity has correct type.",
"repository-entity-lifecycle-07: Asset new entity has local metadata collection.",
"repository-entity-lifecycle-08: Asset new entity has version greater than zero.",
"repository-entity-lifecycle-09: Asset new entity is known.",
"repository-entity-lifecycle-10: Asset new entity summarized.",
"repository-entity-lifecycle-11: Asset new entity retrieved.",
"repository-entity-lifecycle-12: Asset new entity is unattached.",
"repository-entity-lifecycle-13: Asset entity status updated.",
"repository-entity-lifecycle-14: Asset entity new status is Active",
"repository-entity-lifecycle-15: Asset entity with new status version number is 2",
"repository-entity-lifecycle-16: Asset entity can not be set to DELETED status.",
"repository-test-case-base-01: Repository connector supplied to conformance suite.",
"repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
"repository-test-case-base-01: Repository connector supplied to conformance suite.",
"repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
"repository-entity-lifecycle-17: Asset entity properties cleared to min.",
"repository-entity-lifecycle-18: Asset entity with min properties version number is 3",
"repository-entity-lifecycle-21: Asset entity deleted version number is 4",
"repository-entity-lifecycle-22: Asset entity no longer retrievable after delete.",
"repository-entity-lifecycle-23: Asset entity restored ",
"repository-entity-lifecycle-24: Asset entity restored version number is 5",
"repository-entity-lifecycle-25: Asset entity retrieved following restore ",
"repository-entity-lifecycle-26: Asset entity purged."
],
"testCaseDescriptionURL": "https://egeria.odpi.org/open-metadata-conformance-suite/docs/repository-workbench/test-cases/repository-entity-lifecycle-test-case.md",
"testCaseId": "repository-entity-lifecycle-Asset",
"testCaseName": "Repository entity lifecycle test case",
"unsuccessfulAssertions": []
}
}

I'm not suggesting this rolled-up view already exists, I'm suggesting adding it 🙂

I suspect I'll have my hands full just trying to get Atlas and IGC running and then conformed within the new CTS -- pushing this back to 1.3...

Still seems like a good thing to do - keeping open


Start of best practices docs

DO NOT MERGE - NOT DONE YET

Is 050 ready to go?  Or still in progress?

I merged in master, and I'm cleaning it up now a bit more.

Cool - I deployed my changes, even though the PHP examples are wrong.  At least until I get some more PR's/merging done over in the PHP sdk.

I think that is a pretty good start, but needs more detail, and I need to take up the client/query side more.
However, those improvements could be their own PR's, this is meant to start the docs on this, not finish them.

Sounds good to me.  Merging!


CM-2425_changelog

LGTM

Code Coverage is 82.7%, details at https://s3.amazonaws.com/rs-code-coverage/rsc/2016-08-30_746_Coverage-82.7.txt (sometimes the URL can take a few minutes to be available)


Contentbox running Coldbox 7 (errors)

Hello!
I tried to run this module (thankfully installed successfully) in order to create a calendar in Contentbox running Coldbox 7, but i met several severe errors from getModel deprecated to other type of errors. Have you tested if it works properly in Contentbox running Coldbox 7?
Regards

I also share my box.json. Sorry for saying Coldbox 7 beforehand!
{
    "name":"ContentBox Modular CMS Installer",
    "version":"5.3.0",
    "location":"https://downloads.ortussolutions.com/ortussolutions/contentbox/5.3.0/contentbox-installer-5.3.0.zip",
    "author":"Ortus Solutions<EMAIL_ADDRESS>    "slug":"contentbox-installer",
    "shortDescription":"A ColdBox site configured and deployed with ContentBox CMS",
    "type":"cms",
    "keywords":"cms,content management,modular cms",
    "homepage":"https://www.contentboxcms.org",
    "documentation":"https://contentbox.ortusbooks.com",
    "repository":{
        "type":"git",
        "url":"https://github.com/Ortus-Solutions/ContentBox"
    },
    "bugs":"https://ortussolutions.atlassian.net/browse/CONTENTBOX",
    "createPackageDirectory":false,
    "license":[
        {
            "type":"Apache2",
            "url":"http://www.apache.org/licenses/LICENSE-2.0.html"
        }
    ],
    "contributors":[
        "Joel Watson<EMAIL_ADDRESS>        "Brad Wood<EMAIL_ADDRESS>        "Curt Gratz<EMAIL_ADDRESS>    ],
    "dependencies":{
        "coldbox":"^6.0.0",
        "contentbox":"~5.3.0",
        "commandbox-dotenv":"*",
        "commandbox-cfconfig":"*",
        "commandbox-migrations":"*",
        "cbmodule-fullcalendar":"^1.1",
        "cbmodule-photogallery":"^1.1"
    },
    "devDependencies":{},
    "installPaths":{
        "coldbox":"coldbox/",
        "contentbox":"modules/contentbox/",
        "cbmodule-fullcalendar":"modules/contentbox/modules_user/fullCalendar/",
        "cbmodule-photogallery":"modules/contentbox/modules_user/photoGallery/"
    },
    "ignores":[],
    "cfmigrations":{
        "schema":"${DB_DATABASE}",
        "connectionInfo":{
            "class":"${DB_CLASS}",
            "connectionString":"${DB_CONNECTIONSTRING}",
            "bundleName":"${DB_BUNDLENAME}",
            "bundleVersion":"${DB_BUNDLEVERSION}",
            "username":"${DB_USER}",
            "password":"${DB_PASSWORD}"
        },
        "defaultGrammar":"AutoDiscover@qb"
    },
    "scripts":{
        "contentbox:migrate":"migrate up migrationsDirectory=modules/contentbox/migrations",
        "contentbox:migrate:up":"run-script contentbox:migrate",
        "contentbox:migrate:down":"migrate down migrationsDirectory=modules/contentbox/migrations",
        "install:2021":"!cfpm install zip,orm,mysql,postgresql,sqlserver,document,feed"
    }
}

Regards


Changes for 0.2.0 release

Updates build and readme files only.

Current coverage is 80.73%

Merging #33 into master will not affect coverage as of 629806d

@@            master     #33   diff @@
======================================
  Files           12      12
  Stmts          493     493
  Branches        97      97
  Methods          0       0
======================================
  Hit            398     398
  Partial          0       0
  Missed          95      95

Review entire Coverage Diff as of 629806d

Powered by Codecov. Updated on successful CI builds.

Merged.


fix(action): Specify Python version directly

Fix crash when running slack-templates action from other repositories. The setup-python action incorrectly prepends the path of the calling action checkout to the given python-version-file. Hence, the Python version file is only found correctly when slack-templates is called within this repository. Work around this bug by passing python-version instead without creating a Python version file at all.

Corrected the verb "check out" to the noun "checkout" in the commit message, which doesn't warrant a second look.


GD crashes when opening the Geode menu

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
Geode Version
3.0.0 Alpha
Mods Installed
[cant retrieve because no crash window popped up]
Steps to Reproduce

Installed Geode 3.0.0 Alpha to get mods back
Open Geode (works)
Close it for a while, then open again
GD crashes
Decide to install it with VS runtime
GD crashes again
Uninstall it altogether again
Install Geode without VS runtime
Open GD (works)
Open Geode menu
Menu does not show
GD freezes for about 2 seconds then crashes
No crash window

Crash Report
No response
Additional Information
No response

Download the resources and extract them to Geometry Dash/geode/resources/geode.loader

@hiimjustin000 i am having the same problem. I did what you said and it still has the same problems.

Show me crashlog

it crashes but it doesnt give me crashlog, even when i look in my crashlog folder nothing new is in there

ok wait I just found something
if i have no mods in my mods folder it lets me go in there?

Yes it does

yeah wait i tried something
without mods it works
with some mods it works
therefore it probably is a mod that is causing the issue and not geode
@wind40 whats ur mods folder?

nvm i found it its the Texture Loader mod
i do not think this is a geode thing?

Quiero jugar online


Remove static instance of ActorRuntime

Description
This change removes a mutable static instance - this is low-hanging
fruit design improvement and helps us make these features more flexible
in the future.
Issue reference
Contributes to: #416
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation (n/a)

I rebased it, if you want to take another quick look


Explore using Streamlit to host a data analysis dashboard

https://streamlit.io/

New repo setup to create Streamlit app. I think we can close this.

I still need to commit the code to an OPD repo. What should we call it?

Maybe OPD Explorer? I'm flexible if you have ideas.


Pods in pending state

I installed kne as per document and tried to deploy nokia 2srl-certs topology. It has been on pending state for 15 minutes. am i missing something? this is the message i get;
INFO[0002] Node "r2" resource created
INFO[0002] r1 - generating self signed certs
INFO[0002] r1 - waiting for pod to be running

Not sure if you have already but I would suggest taking a look at the troubleshooting guide: https://github.com/openconfig/kne/blob/main/docs/troubleshoot.md
If you cannot find a solution after going through that guide then please post more details (the pod logs, etc.)

Thank you. checked the logs and it was insufficient cpu. deleted some namespaces and worked fine.
Is there any other documentation available? which are the vendors supported right now? can we get the container image from any vendor and deploy through kne?

the examples dir show examples with other vendors: https://github.com/openconfig/kne/tree/main/examples
currently we support cisco, arista, nokia, and juniper (along with keysight ixia for traffic gen)
you'll have to reach out to each vendor to access their containers (besides nokia which the un-licensed version is open sourced)

Hi Alex,
Thanks for the response.
I am trying to create a topoogy for the arista device from exaples folder and getting the following error. Looks like access denied error while accessing the container. I created an user account in arista portal. How do i fix this access error?
Events:
Type     Reason     Age                From               Message

Normal   Scheduled  97s                default-scheduler  Successfully assigned ceos/r1 to kne-control-plane
Normal   Pulled     97s                kubelet            Container image "networkop/init-wait:latest" already present on machine
Normal   Created    97s                kubelet            Created container init-r1
Normal   Started    97s                kubelet            Started container init-r1
Normal   Pulling    41s (x3 over 82s)  kubelet            Pulling image "ceos:latest"
Warning  Failed     40s (x3 over 80s)  kubelet            Failed to pull image "ceos:latest": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/ceos:latest": failed to resolve reference "docker.io/library/ceos:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning  Failed     40s (x3 over 80s)  kubelet            Error: ErrImagePull
Normal   BackOff    12s (x3 over 56s)  kubelet            Back-off pulling image "ceos:latest"
Warning  Failed     12s (x3 over 56s)  kubelet            Error: ImagePullBackOff
Thanks,
Jaya
Sent from Outlookhttp://aka.ms/weboutlook

From: Alex Masi @.>
Sent: Tuesday, January 10, 2023 1:01 AM
To: openconfig/kne @.>
Cc: Jaya Srikanth @.>; Author @.>
Subject: Re: [openconfig/kne] Pods in pending state (Issue #285)
the examples dir show examples with other vendors: https://github.com/openconfig/kne/tree/main/exampleshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenconfig%2Fkne%2Ftree%2Fmain%2Fexamples&data=05|01|jasrik%40microsoft.com|1721287585a64717089c08daf2e938b5|72f988bf86f141af91ab2d7cd011db47|0|0|638089380739900811|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=cWQ9fhCu7Qs%2Bc2hbLqz75n0sEuga9%2FTb%2BW2yRX2A3NQ%3D&reserved=0
currently we support cisco, arista, nokia, and juniper (along with keysight ixia for traffic gen)
you'll have to reach out to each vendor to access their containers (besides nokia which the un-licensed version is open sourced)
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenconfig%2Fkne%2Fissues%2F285%23issuecomment-1376932346&data=05|01|jasrik%40microsoft.com|1721287585a64717089c08daf2e938b5|72f988bf86f141af91ab2d7cd011db47|0|0|638089380739900811|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=8oqw2xrC6AfZ8OSMfVpNWBZxySUwqfFta9MaY9hIaJE%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV5MBYY27KYD3Z3Y4LIUVVDWRUQNPANCNFSM6AAAAAATV6RE24&data=05|01|jasrik%40microsoft.com|1721287585a64717089c08daf2e938b5|72f988bf86f141af91ab2d7cd011db47|0|0|638089380739900811|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=eOxiVfi9X868EeU1RSdwX2zV20Q%2BxRSozjrTcehT%2FDk%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>

This error message is indicating that ceos:latest cannot be found on dockerhub. You'll have to first docker pull the image from arista's portal and then load it into the kind cluster as ceos:latest. See the docs here: https://github.com/openconfig/kne/blob/main/docs/create_topology.md#container-images


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


no tmux session/window is spawned

I've configured test repo like this:
[merge]
	tool = kakmerge
[mergetool "kakmerge"]
	trustExitCode = true
	cmd = env LOCAL=\"${LOCAL}\" BASE=\"${BASE}\" REMOTE=\"${REMOTE}\" MERGED=\"${MERGED}\" kakmerge

Invoking git mergetool spawns no new tmux session or window.
I'm on macOS, iterm2 and tmux v3.1c

Thanks for the report, it's indeed broken for me too. I'll look into it!

Thanks for the report, it's indeed broken for me too. I'll look into it!

I released a fix. Note that the documentation was incorrect, the cmd bit is unnecessary, you should only need path. This is what I have in my configuration:
[merge]
    tool = kakmerge

[mergetool "kakmerge"]
    trustExitCode = true
    path = kakmerge

I released a fix. Note that the documentation was incorrect, the cmd bit is unnecessary, you should only need path. This is what I have in my configuration:
[merge]
    tool = kakmerge

[mergetool "kakmerge"]
    trustExitCode = true
    path = kakmerge


Loginbox too small on HiDPI displays

Is there an existing issue for this?

[X] I have searched the existing issues

Operating system
Arch
Installation method
Package Manager (from OS)
Betterlockscreen & Dependency-Versions
Betterlockscreen: version: v4.2.0 (dunst: true, feh: true)
i3lock: version aur-e8b9943 (2023-03-31) © 2010 Michael Stapelberg, © 2015 Cassandra Fox, © 2021 Raymond Li
Version: ImageMagick 7.1.1-15 Q16-HDRI x86_64 21298 https://imagemagick.org
Copyright: (C) 1999 ImageMagick Studio LLC
License: https://imagemagick.org/script/license.php
Features: Cipher DPC HDRI Modules OpenCL OpenMP(4.5)
Delegates (built-in): bzlib cairo djvu fftw fontconfig freetype heic jbig jng jp2 jpeg jxl lcms lqr ltdl lzma openexr pangocairo png raqm raw rsvg tiff webp wmf x xml zip zlib
Compiler: gcc (13.2)
dunst version: 1.9.2
feh version 3.10
Compile-time switches: curl exif inotify help magic stat64 verscmp xinerama
[B] Betterlockscreen

Bug description
The loginbox and the font are too small on HiDPI displays. This could potentially be fixed by using a fontsize config variable. I noticed the script semi-hardcodes the width and height of the loginbox, in the sense that it expects a specific font size, or rather 3 specific fontsizes (fontlg, fontmd, fontsm), 2 of which (fontmd, fontsm) can either be deduced from fontlg or would be also provided as config variables:
width=$(logical_px 340 1)
height=$(logical_px 100 2)

I believe that this should not be hardcoded anymore, but also should depend on the display's width and height.
If you feel like this is a good approach, please let me know and I will try to open a PR, however please note my time budget is really low.
Steps to reproduce
# ~/.config/betterlockscreenrc

# default options
display_on=0
span_image=false
lock_timeout=300
fx_list=(dim blur dimblur pixel dimpixel color)
dim_level=40
blur_level=1
pixel_scale=10,1000
solid_color=333333
wallpaper_cmd="feh --bg-fill"
quiet=false

# default theme
loginbox=00000066
loginshadow=00000000
locktext="Type password to unlock..."
font="CaskaydiaCove Nerd Font"
fontsize=80
ringcolor=ffffffff
insidecolor=00000000
separatorcolor=00000000
ringvercolor=ffffffff
insidevercolor=00000000
ringwrongcolor=ffffffff
insidewrongcolor=d23c3dff
timecolor=ffffffff
time_format="%H:%M"
greetercolor=ffffffff
layoutcolor=ffffffff
keyhlcolor=d23c3dff
bshlcolor=d23c3dff
veriftext="Verifying..."
verifcolor=ffffffff
wrongtext="Failure!"
wrongcolor=d23c3dff
modifcolor=d23c3dff
bgcolor=000000ff

#
# expert options (change at own risk!)
#

# i3lockcolor_bin="i3lock-color"      # Manually set command for i3lock-color
# suspend_command="systemctl suspend" # Manually change action e.g. hibernate/suspend-command

# i3lock-color - custom arguments
# lockargs=() 						  # overwriting default "(-n)"
# lockargs+=(--ignore-empty-password) # appending new argument

Relevant log output
No response

Nevermind, the issue is clearly handled, I didn't update my wallpapers properly...


Should we change controller to "async-controller" to match name of deployment?

In cmd/controller/main.go:
func main() {
	sharedmain.Main("controller",

Closed by #36


pipeline_annotations pep8 error

Dear All,
I have just fixed a problem with the installation script of the CGATPipelines (thanks @jscaber!).
However, the master branch of the CGATPipelines is failing due to a pep8 error:
https://travis-ci.org/CGATOxford/CGATPipelines/jobs/67868390#L1790
Could you please have a look?
Many thanks,
Sebastian.

Fixed & sent pull request.
Jakub
On 06/22/15 17:56, Sebastian Luna Valero wrote:

Dear All,
I have just fixed a problem with the installation script of the
CGATPipelines (thanks @jscaber https://github.com/jscaber!).
However, the master branch of the CGATPipelines is failing due to a
pep8 error:
https://travis-ci.org/CGATOxford/CGATPipelines/jobs/67868390#L1790
Could you please have a look?
Many thanks,
Sebastian.
—
Reply to this email directly or view it on GitHub
https://github.com/CGATOxford/CGATPipelines/issues/40.