oci-image-tool: rough sketch

We need a tool to make it easy for people to validate and play with an OCI Image.
Basic validation tool that can parse and inspect all of the objects inside of the OCI Image spec
$ oci-image-tool validate serialized-image.tar
$ oci-image-tool validate manifest.json
$ oci-image-tool validate config.json
json: cannot unmarshal object into Go value of type types.Env

Unpack an image on disk (dependency on https://github.com/opencontainers/image-spec/issues/23)
to a OCI runtime bundle:
$ oci-image-tool create-runtime-bundle path/to/image path/to/bundle
$ oci-runtime path/to/bundle

Details:

We should probably use the bog standard cobra CLI library: https://github.com/spf13/cobra
We can steal some of the code form the actool: https://github.com/appc/spec/tree/master/actool

not to be confused with https://github.com/opencontainers/ocitools ?

@vbatts I think we should rename ocitools to ocirtool or something. It is already focused on the runtime.

@vbatts I will work on renaming it oci-runtime-tool with @mrunalp

@s-urbaniak is going to work on this one

@s-urbaniak you can steal validation code from here: https://github.com/opencontainers/image-spec/pull/41

@philips great, thanks, this will keep me busy the next few days. Mind assigning this to me (or give privileges to do so)

@vbatts @philips How about moving github.com/opencontainers/ocitools to github.com/opencontainers/runtime and create a github.com/opencontainers/image repo for the implementation of this very issue?
The directory structure could be:
$GOPATH/src/github.com/opencontainers/runtime
 ├─ cmd
 │  ├─ runtimetest
 │  └─ oci-runtime-tool
 └ ... oci runtime pkg API src ...

and for the image concerns an equivalent:
$GOPATH/src/github.com/opencontainers/image
 ├─ cmd
 │  ├─ oci-image-examples
 │  ├─ oci-image-json
 │  └─ oci-image-tool
 └ ... oci image pkg API src ...

@s-urbaniak I think keeping the tool with the spec is good. It means overtime spec changes come with working code for handling the schema. Honestly I hope we can merge ocitool back into the runtime repo at some point.

@philips I am writing a basic validation function now, stealing ideas from actool.
Validation in a first rough sketch would include:

oci-image-tool validate --type config: simple validation of application/vnd.oci.image.serialization.config.v1+json
oci-image-tool validate --type manifest: simple validation of application/vnd.oci.image.manifest.v1+json, or application/vnd.oci.image.manifest.list.v1+json (auto-detected)
oci-image-tool validate --type image: as sketched in per https://github.com/opencontainers/image-spec/issues/23#issuecomment-212636147

I am implementing it using auto-detection in mind as per actool such that the user can actually omit --type ....
Next commands to implement would be:

unpack: as discussed per OOB this would be a simple deflate mechanism considering all the layers in an image file.
create-runtime-bundle: Create a runtime bundle as per https://github.com/opencontainers/runtime-spec/blob/master/bundle.md

@s-urbaniak LGTM, LMK when you get something going and I can look at a branch or WIP PR.

Moving to v0.2.0 as we are fixing upstream packages like the go json schema library and I don't want to block a release.

@s-urbaniak are you working on create-runtime-bundle next?

@philips yes, that's the plan :-)

Closing this out in favor of #99 as most of the features except that one have landed.


Completed 11

Check out a review request at GitLocalize

Thanks for the contribution! Due to the way DevSite works, we can't translate _book.yaml, _project.yaml, _toc.yaml, _footer.yaml, _redirects.yaml, _upper-tabs-*.yaml files. I'm going to close this for now. Thanks


ui shows transcoding while it is ripping

Description
ui shows transcoding while it is ripping. not much more to say

Can you attach your log file from the job ?

Can you attach your log file from the job ?

here is the log
Goldeneye.log

here is the log
Goldeneye.log

Can you change your log level to DEBUG in your arm.yaml
From what i can tell from the log it is transcoding, so the UI is showing correct information, but without seeing the DEBUG log i cant really pinpoint the issue.

Can you change your log level to DEBUG in your arm.yaml
From what i can tell from the log it is transcoding, so the UI is showing correct information, but without seeing the DEBUG log i cant really pinpoint the issue.

ok but it has not started writing the output file yet so i dont think it is transcoding.
also it will need to wait for the next disk. i have changed it to debug but it has not switched so i assume i need to restart to take effect.

ok but it has not started writing the output file yet so i dont think it is transcoding.
also it will need to wait for the next disk. i have changed it to debug but it has not switched so i assume i need to restart to take effect.

No you dont need to restart for the debugging to change levels. It will update with the next disc.

No you dont need to restart for the debugging to change levels. It will update with the next disc.

As far is i can tell this is working as intented.

As far is i can tell this is working as intented.

yes this is working as intended. i had it set to transcode directly from the disk.

yes this is working as intended. i had it set to transcode directly from the disk.


[zh] Localize 'security_chaos_engineering'

[ ] Localize the content/en/security_chaos_engineering.md to content/zh-cn/ in dev-zh.

Can i work on this issue?

Of course. Please go ahead!

I'll translate this, assign it me, ths. @Jacob953

solve by https://github.com/cncf/glossary/pull/1091


Service catalog wizard link goes to wrong place

Sorry for such a minor issue, I think this link labelled 'view Documentation'  should take you to enmasse documentation, rather than the github repo page. ( or at least the documentation link of the README )
for both standard and brokered wizards.

same (wrong destination) link here

I'd suggest a suitable target would be http://enmasse.io/documentation/

Service broker will be removed in 1.0.


Lumina Screenshot fails to forewarn the user when discarding unsaved data

This issue was initially observed when, working as user 'test', I used the Save As button to supposedly save to a directory that is owned by a different user ('bbsadmin-l'):
$ ls -dl /usr/home/bbsadmin-l/Public
drwxr-xr-x  2 bbsadmin-l  bbsadmin-l  3 20 Nov 09:06 /usr/home/bbsadmin-l/Public
$

The loss of data was not realised until after the user had logged out, so I logged in and made the issue reproducible in another way.
Steps

launch Lumina Screenshot
observe the window of the application
log out

Expected

either (a) a prompt to save data; or (b) automated save to a nonvolatile area of the file system

Actual result

without warning, loss of data.

Alternative steps to dataloss

launch Lumina Screenshot
key Escape.

Thought
If (b) is acceptable then I suggest either of these formats –
~/Pictures/yyyy-MM-dd-hh-mm-ss screenshot.png
~/Pictures/yyyy-MM-dd hh-mm-ss screenshot.png
– of the two, the second format will probably be easier on the eye if, over time, the user allows an 'automated collection of shots' to become large.

A) I dont know if it really makes sense to prompt the user to save.  Once a
user makes a screenshot they are ~instantly~ presented with the option to
save.  If they decide not to, why should the application pester them again
to do it?  I'd get annoyed rather fast if everytime I wanted to shut down
the application without saving (intentionally), it wanted to prompt me
again to save.
B) The problem is that since we use ZFS, if a user has snapshots enabled,
they will just eat space for screenshots that aren't wanted.  Sometimes a
user will take multiple screenshots to get the layout just right, what you
are suggesting here will save multiple copies of the image to their home
dir which they may not want at all.
The reason applications like lumina-text-edit have the save warning and
lumina-screenshot doesnt is that doing another screenshot takes a few
seconds... retyping something will take much longer and you may not be able
to get the wording exactly correct.
Personally I dont think an OS should hold a users hand and warn them at
every turn if they dont do something.  But I'll leave this one to Ken to
decide.
Also your suggested file formats are exactly the same.
On Sun, Nov 20, 2016 at 5:21 AM, Graham Perrin<EMAIL_ADDRESS>wrote:

This issue was initially observed when, working as user 'test', I used the
Save As button to supposedly save to a directory that is owned by a
different user ('bbsadmin-l'):
$ ls -dl /usr/home/bbsadmin-l/Public
drwxr-xr-x  2 bbsadmin-l  bbsadmin-l  3 20 Nov 09:06 /usr/home/bbsadmin-l/Public
$
The loss of data was not realised until after the user had logged out, so
I logged in and made the issue reproducible in another way.
Steps

launch Lumina Screenshot
observe the window of the application
log out

Expected

either (a) a prompt to save data; or (b) automated save to a
nonvolatile area of the file system

Actual result

without warning, loss of data.

Alternative steps to dataloss

launch Lumina Screenshot
key Escape.

Thought
If (b) is acceptable then I suggest either of these formats –
~/Pictures/yyyy-MM-dd-hh-mm-ss screenshot.png
~/Pictures/yyyy-MM-dd hh-mm-ss screenshot.png
– of the two, the second format will probably be easier on the eye if,
over time, the user allows an 'automated collection of shots' to become
large.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/trueos/lumina/issues/310, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEcEp2YG45sj7yhkwx3rTkuDYZPQiLmLks5rAB86gaJpZM4K3gI_
.

Really, it's not pestering.

I'd get annoyed rather fast if …

Imagine the annoyance caused by loss; when an unexpectedly discarded screenshot will be difficult or impossible to reproduce.

… your suggested file formats are exactly the same.

Nope, please take a second look :)

I'm not sure I understand how someone could 'accidently discard' a
screenshot.  Its not as if the application does anything else.  It's sole
purpose it to make a screen capture.  If someone opens the program to
capture a screen shot and then chooses not to save it... why would they be
surprised by it not being saved?   Once you take a screenshot, the option
to save it is immediately presented to the user.
On November 20, 2016 9:30:09 AM Graham Perrin<EMAIL_ADDRESS>wrote:

Really, it's not pestering.

I'd get annoyed rather fast if …

Imagine the annoyance caused by loss; when an unexpectedly discarded
screenshot will be difficult or impossible to reproduce.

… your suggested file formats are exactly the same.

Nope, please take a second look :)
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/trueos/lumina/issues/310#issuecomment-261781565

My first impression of this issue: the accident was made by the application, not the person.
When Save As fails to save and the user is not warned that save failed, that seems (to me) like a bug.

When does 'Save As' fail? I don't see anything in the code that would cause
such a thing to happen, so if that is happening I need to figure out why.
If you're talking about a situation where a user tries to save the file to
a location that they don't have write access too... that's not an
application failure, but a user failure.
On Sun, Nov 20, 2016 at 11:24 AM, Graham Perrin<EMAIL_ADDRESS>wrote:

My first impression of this issue: the accident was made by the
application, not the person.
When Save As fails to save and the user is not warned that save failed,
that seems (to me) like a bug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trueos/lumina/issues/310#issuecomment-261787963, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEcEp0b5AAPc6fDyxVzCjRfMLT66VIhSks5rAHRPgaJpZM4K3gI_
.

user failure.

I doubt that we'll agree. I put myself in the shoes of users, maybe newcomers to TrueOS, who will have little or no knowledge of file systems, modes, ACLs and so on.

Lumina Screenshot aside, for a moment: consider Insight, which offers the (Limited Access) hint when the user browses to a directory where access is limited. Helpful features such as that should be welcomed.

I'm deferring this one to Ken to make a decision on.

I have an idea that could satisfy both of you:
In the "View/Edit" tab of Lumina Screenshot, one could add the hint "Screenshot hasn't been saved yet" in the line below the "Save As" button; and that this hint only disappears after a successful saving through the "Save As" button or with Phototonic.
(Though I don't know if Phototonic or an other program chosen as default screenshot editor can inform Lumina Screenshot about a successful saving).
This is also unobtrusive and useful for the case that I make a screenshot, don't save it, and make another screenshot immediately: here the next screenshot erases the former screenshot so that a warning would be necessary too - but a pop-up warning "Would you like to save the old screenshot?" would ruin the making of the next screenshot if I wanted to capture a time-critical event on screen.
(So a pop-up warning that covers all cases unobtrusively isn't possible anyway).
Alternatively Lumina Screenshot could create a Screenshot folder in the home directory of the user and autosave every screenshot to that folder.
But I would make such a function optional so that a user can switch it off or on by ticking an entry "Autosave to Screenshots folder in home directory" in a newly created "Option" menu next to Lumina Screenshot's "File" menu.

Some more info about my sentence
"(Though I don't know if Phototonic or an other program chosen as default screenshot editor can inform Lumina Screenshot about a successful saving)."
from my last comment:
In the "View/Edit" tab of Lumina Screenshot, if I click on the "Launch Editor" button, the screenshot file is saved in the folder /Pictures. So one could think: "Now it's ok to remove the hint "Screenshot hasn't been saved yet" from Lumina Screenshot's "View/Edit" tab".
But if I choose "Delete" in Phototonic, this file is erased.
Therefore it would be necessary for Lumina Screenshot to notice such an erasure of the file by Phototonic so that it can show the hint "Screenshot hasn't been saved yet" again.
In the end I guess that the creation of such a functionality would be a bit too labor-intensive.
So I think the optional autosave alternative I mentioned in my last comment would be easier to create.

Basically I think this whole conversation boils down to one main issue:
When the screenshot fails to get saved when the user requests it (for some reason, such as no write permissions on the designated folder), the utility does not warn the user that the save routine failed.
I just fixed this in commit https://github.com/trueos/lumina/commit/61ec083ea62121a9eba88c4bd46f10be9b367f81
The screenshot utility is not designed for managing all of the users pictures, nor should it care what the user does with the screenshot file at a later date or in other utilities (that is where an app like phototonic comes in as a "manager" of the users image files).
By the same token (and as q5sys already mentioned) more often than not people take multiple screenshots before they get one that is "just right" that they want to save - so automatically saving every screenshot into the user's "Pictures" directory (or anywhere else) is probably not a good idea because it basically adds more work on the user to keep their directories clear of unwanted files rather than only saving what the user wanted in the first place. Similarly, the autosave functionality will bypass any edits that the user wants to perform on the screenshot before saving it on the system, so that is another reason we should probably skip that option as well.

Thanks.
My viewpoints stem partly from the Mac tradition, learnt decades ago, of the computer saving without fail in response to a single action: Shift-Command-3. A shot with an aural metaphor: the sound of the shutter of a camera.
With Lumina there's the visual metaphor of a camera, and I expect whatever's on the roll of film (or digital alternative) to be kept, saved by default until I actively choose (at a later time or date) to discard selected items. One simple action: click.

Call me old-fashioned :-)


Add PSNR

@fchollet

You'll need to format the code with sh shell/format.sh

Looking good! Please resolve merge conflicts and we can merge the PR.


python3 support

Currently, python3.4 is not supported, and it should be. I am currently testing this through the properties repo dev docs: https://travis-ci.org/3ptscience/properties/builds/136561533

this closed with #2


[WIP] Add arbitrary language support

Description
This pull request adds the ability to run any code snippet if you have the appropriate kernel installed on your machine. See Screenshot at the bottom for a visual.
Usage
In order to run a code snippet for a particular language, you need the following:

You need the proper kernel installed
You need to add the proper language identifier by adding the language in the code blocks prepended by 'jupyter-'

```jupyter-python
from random import randrange

print("Hello from Python!")
print(randrange(100))
```

The reason for this small change is so the plugin doesn't need to run on every code block that just so happens to align with an installed kernel. As I write this I realize this isn't a great reason for this change so feel free to veto this item - it can be changed quite easily.
Issues
One issue I have with this is making the post processor reusable for different languages. The main issue revolves around this snippet on line 97 of main.ts:
async postprocessor(src: string, el: HTMLElement, ctx: MarkdownPostProcessorContext) {
  const extractLanguageFromClass = (str: string) => str.split('-').pop();
  const kernel = this.settings.kernels.get(extractLanguageFromClass(el.classList[0]));
  if(!kernel)
	  return;

As far as I know, the only way to differentiate between languages using the same post processor is to grab the class list out of the HTMLElement and extract the language from the first entry. So far this is consistent but this feels quite hacky. I would love to know if there is an alternate solution.
To Do's

[x] Integrate Setup Scripts (the pre-work is done but there is currently nothing in place to add or change them - doesn't seem right to add functionality that removes a key feature of the plugin)
[ ] Verify plugin works on Linux and Mac
[x] Configure plugin to pull new .py file from github (similar to obsidian-jupyter.py) OR rework to use command line from main.ts instead of having another file

Screenshot

Update
652e934 adds the ability to add/edit setup scripts for each language. All kernels that were found during onload will have a new section in the Settings Tab:

See #66.


Fix CORS headers for Meteor 1.3 Cordova

Looks related to https://github.com/mizzao/meteor-timesync/issues/41
I get this error during meteor run android after upgrading to Meteor 1.3:
XMLHttpRequest cannot load http://<IP_ADDRESS>:3000/cfs/servertime. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:12280' is therefore not allowed access.

same here. any update @lorensr ?

@guillim is this fixed for you when you remove wizonesolutions:canonical?

@lorensr I removed wizonesolutions:canonical, and unfortunately cfs still gives me CORS errors, so I removed cfs and it now works fine.


added list to map page

Looks ok.  A couple of changes:   The property list should include the city in addition to the property name.  I'm thinking we should sort the list by city.  We should zoom the map when the user selects a property.

The state summary doesn't include city names, only coordinates. Not sure if you'd rather change that or get the city names from the asset details

Map bounds/zoom is done. I'll start a new branch for the php work.


Fedora 38 - detected unhandled Python exception in '/lib64/security/howdy/compare.py'

Hello!
I've just installed Howdy on a Fedora 38 installation via the copr repository. I've setup pam.d/sudo to use howdy and, after manually setting the right /dev/videoX device in the configuration, the webcam effectively activates when a sudo command is being prompted. The problem is that it will fail and fallback to the password method.
journalctl reports me the following:
apr 24 14:48:58 plungedcopper [14430]: Attempting facial authentication for user elegos
apr 24 14:49:01 plungedcopper python3[14432]: detected unhandled Python exception in '/lib64/security/howdy/compare.py'
apr 24 14:49:01 plungedcopper [14430]: Failure, unknown error1
apr 24 14:49:01 plungedcopper abrt-server[14498]: Package 'howdy' isn't signed with proper key
apr 24 14:49:01 plungedcopper abrt-server[14498]: 'post-create' on '/var/spool/abrt/Python3-2023-04-24-14:49:01-14432' exited with 1
apr 24 14:49:01 plungedcopper abrt-server[14498]: Deleting problem directory '/var/spool/abrt/Python3-2023-04-24-14:49:01-14432'

I don't know how to view that unhandled exception honestly (Fedora doesn't have /var/log/auth.log or similar).
May you please help me?
Thanks :)

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): Fedora 38
Howdy version (sudo howdy version): 2.6.1

Ha! Found the error. I tried to run python3 compare.py elegos and actually I saw what resulted being the problem:
libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
MFX: Can't initialize session

The issue is that apparently I had to install the nvidia-vaapi-driver package.

I also had the same symptom on Fedora 38, but my exception was a little different:
Traceback (most recent call last):
  File "/lib64/security/howdy/compare.py", line 283, in <module>
    make_snapshot("SUCCESSFUL")
  File "/lib64/security/howdy/compare.py", line 55, in make_snapshot
    snapshot.generate(snapframes, [
  File "/usr/lib64/security/howdy/snapshot.py", line 54, in generate
    os.makedirs(abpath + "/snapshots")
  File "<frozen os>", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/usr/lib64/security/howdy/snapshots'

This was resolved by running sudo howdy snapshot, which created the non-existing directory. Everything worked properly after that!

I also had the same symptom on Fedora 38, but my exception was a little different:
Traceback (most recent call last):
  File "/lib64/security/howdy/compare.py", line 283, in <module>
    make_snapshot("SUCCESSFUL")
  File "/lib64/security/howdy/compare.py", line 55, in make_snapshot
    snapshot.generate(snapframes, [
  File "/usr/lib64/security/howdy/snapshot.py", line 54, in generate
    os.makedirs(abpath + "/snapshots")
  File "<frozen os>", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/usr/lib64/security/howdy/snapshots'

This was resolved by running sudo howdy snapshot, which created the non-existing directory. Everything worked properly after that!

Nice! I had the same problem and running the snapshot resolved it.

I also had the same symptom on Fedora 38, but my exception was a little different:
Traceback (most recent call last):
  File "/lib64/security/howdy/compare.py", line 283, in <module>
    make_snapshot("SUCCESSFUL")
  File "/lib64/security/howdy/compare.py", line 55, in make_snapshot
    snapshot.generate(snapframes, [
  File "/usr/lib64/security/howdy/snapshot.py", line 54, in generate
    os.makedirs(abpath + "/snapshots")
  File "<frozen os>", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/usr/lib64/security/howdy/snapshots'

This was resolved by running sudo howdy snapshot, which created the non-existing directory. Everything worked properly after that!

Thanks!!! This solved it for me!

I also had the same symptom on Fedora 38, but my exception was a little different:
Traceback (most recent call last):
  File "/lib64/security/howdy/compare.py", line 283, in <module>
    make_snapshot("SUCCESSFUL")
  File "/lib64/security/howdy/compare.py", line 55, in make_snapshot
    snapshot.generate(snapframes, [
  File "/usr/lib64/security/howdy/snapshot.py", line 54, in generate
    os.makedirs(abpath + "/snapshots")
  File "<frozen os>", line 225, in makedirs
PermissionError: [Errno 13] Permission denied: '/usr/lib64/security/howdy/snapshots'

This was resolved by running sudo howdy snapshot, which created the non-existing directory. Everything worked properly after that!

Thanks! This and the ConfigHowdy bash script did the trick.


Move CLI to commander

I ended up down kind of a weird road on this before coming back to reality. "Interchange" and the CLI itself are in separate files now. This is a result of thinking I needed to do something with commander that ended up being wrong. If you're not happy with this I can revert that portion.
However, I decided to commit it this way because it opens up the possibility of using interchange programmatically in the future. I tested as much as I could and everything seems fine.

Bonus, check out this lovely --help
notbook at notbook in ~/git/nodebots-interchange on commander
$ interchange -h

  Usage: interchange [options] [command]

  Commands:

    list|l                          Lists all of the available firmwares
    ports|p [options]               Lists all of the attached boards and their ports
    read|r [options]                Read firware info from port
    install|i [options] [firmware]  Test

  Options:

    -h, --help     output usage information
    -V, --version  output the version number

notbook at notbook in ~/git/nodebots-interchange on commander
$ interchange install -h

  Usage: install|i [options] [firmware]

  Test

  Options:

    -h, --help               output usage information
    -a, --board <board>      Type of board/AVR
    -p, --port <port>        Serial port board is attached to
    -f, --firmata            Install firmata version of firmware
    -i, --address <address>  Specify I2C address

Ooh nice one. Will check out your branch shortly and have a look at the code
On Wed, Nov 11, 2015, 12:55 Derek Wheelden<EMAIL_ADDRESS>wrote:

Bonus, check out this lovely --help
notbook at notbook in ~/git/nodebots-interchange on commander
$ interchange -h
Usage: interchange [options] [command]
Commands:
list|l                          Lists all of the available firmwares
ports|p [options]               Lists all of the attached boards and their ports
read|r [options]                Read firware info from port
install|i [options] [firmware]  Test

Options:
-h, --help     output usage information
-V, --version  output the version number

notbook at notbook in ~/git/nodebots-interchange on commander
$ interchange install -h
Usage: install|i [options] [firmware]
Test
Options:
-h, --help               output usage information
-a, --board <board>      Type of board/AVR
-p, --port <port>        Serial port board is attached to
-f, --firmata            Install firmata version of firmware
-i, --address <address>  Specify I2C address

—
Reply to this email directly or view it on GitHub
https://github.com/ajfisher/nodebots-interchange/pull/13#issuecomment-155630281
.

Looks pretty good other than those little nits which were largely mine anyway ;P
After that's done I'll merge it.


Expose an oncePageLoaded function

Expose a function that takes a callback and invokes it once and once only. Resolves #16

If the page has already loaded, the callback should be invoked immediately
If the page is still loading, as soon as it has finished both loading and processing any clientside JavaScript, it should invoke the callback
If the page has failed to do anything 6 seconds after the initial page load and the callback has yet to be invoked, it will be invoked.

👍


cadl, upgrade emitter-package.json

Description
Upgrade to cadl compiler 0.40 related packages.
All SDK Contribution checklist:

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

General Guidelines and Best Practices

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

Testing Guidelines

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

/check-enforcer reset

/check-enforcer override


Unexpected promisified pipeline behavior when the plugin is included

Expected behavior:
Pipeline completion without issues.
Actual behavior:
The task fails upon the promisified pipeline reaching an instance of CompileStream the plugin's createProject method returns with the error (as the task is still registered):

Did you forget to signal async completion?

I narrowed down the issue to the gulp-typescript plugin, as the same promisified pipeline finishes successfully without it.
Non-promisified version of the pipeline also fails. However, the same task but connected via chaining of pipe methods works as expected.
Since CompileStream inherits from stream.Duplex, I am not sure what can be the problem. finish and end events are emitted. Order of events is also normal for the pipeline flow (pipe -> resume -> finish -> unpipe -> end -> pause).
Your gulpfile:
import { dest, series, src, watch } from "gulp";
import * as aprep from "gulp-append-prepend";
import * as rename from "gulp-rename";
import * as ts from "gulp-typescript";
import * as ug from "gulp-uglify";
import { pipeline } from "stream";
import { promisify } from "util";
import GulpClient = require("gulp");

const asyncPipe = promisify(pipeline);

const config = {
  globs: {
    front: {
      src: ["src/js/**/*", "!src/js/**/*.json"],
      dest: "html/",
    },
  },
  tsconfig: {
    front: "./src/js/",
  },
};

const projectPath = `${config.tsconfig.front}tsconfig.json`;

const project = ts.createProject(projectPath);

const transpileFrontendJs: GulpClient.TaskFunction = async () => {
  await asyncPipe(
    src(config.globs.front.src),
    project(),
    ug({ output: { webkit: true } }),
    rename({
      extname: ".html", //apps script treats .js files as .gs
    }),
    aprep.prependText(`<script type="text/javascript">`),
    aprep.appendText(`</script>`),
    dest(config.globs.front.dest)
  );
};

export const frontend = series(transpileFrontendJs);

const watchOpts: GulpClient.WatchOptions = { ignoreInitial: false, delay: 2e3 };

export default () => {
  return watch(config.globs.front.src, watchOpts, frontend);
};

tsconfig.json
Parent tsconfig.json:
{
  "compilerOptions": {
    "noImplicitThis": true,
    "forceConsistentCasingInFileNames": true,
    "removeComments": true,
    "module": "none",
    "moduleResolution": "node",
    "types": ["node", "google-apps-script", "materialize-css"],
    "target": "es2019",
    "lib": ["ESNext"],
    "pretty": true,
    "experimentalDecorators": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "noImplicitReturns": true,
    "strict": true,
    "noErrorTruncation": true,
    "checkJs": true
  },
  "exclude": ["clsp.js", "src/js"]
}

Child tsconfig.json:
{
  "extends": "../../tsconfig.json",
  "compilerOptions": {
    "types": ["gapi", "materialize-css"],
    "lib": ["DOM", "ESNext"],
    "module": "none",
    "target": "es5",
    "moduleResolution": "node"
  },
  "include": ["*.ts"],
  "exclude": []
}

Environment
Relevant dependencies:
"devDependencies": {
    "gulp": "^4.0.2",
    "gulp-append-prepend": "^1.0.8",
    "gulp-autoprefixer": "^7.0.1",
    "gulp-inject": "^5.0.5",
    "gulp-rename": "^2.0.0",
    "gulp-typescript": "^6.0.0-alpha.1",
    "gulp-uglify": "^3.0.2",
    "ts-node": "^9.1.1",
    "typescript": "^4.1.2",
}

I found this happened when I upgraded from Node.js v12 → v14. I had to use stream-to-promise to get around it.


Fix array syntax in code samples

FYI: Failing pipeline is unrelated to my changes.

@keichinger the CI is a little bit flacky because of algolia and githubs pull_request_target which is required which has some race conditions.
Thx for your fixes.


Interrupting hexyl with ^C leaves ugly remnant

It should probably handle SIGINT and terminate the output as if it was EOF (but maybe with some mark):
│00001410│ 57 37 f9 ae 0b ae 6c 8a ┊ df 0e d8 20 15 f1 d7 f6 │W7××•×l×┊×•× •×××│
│00001420│ a5 5e 99 b0 bd bf 22 a7 ┊ b2 e0 ab ^C             | ×^×××"×┊×××^C   |

This is what ctrl-c looks like on Mac OS X

If somebody has an idea how to fix this, let me know.

Well, part of the problem is synchronous handling of ctrl+c. If you move process exit into the handler, the situation improves. I'm not sure what's actually safe to be called from a signal handler in Rust though (normally described in: man 7 signal-safety).
It's still a bit of a problem, I assume because of stdout buffering. May need some uglier tricks to work around (setbuf?).

A possibly related issue is that on MacOS, when running hexyl without any input the application can't be terminated. Like this:

@secworks That looks like a different bug to me (thank you for reporting it). It would be great if you could create a new ticket.

With the changes in #84, this is now open again. In my terminal and on zsh, this is not an issue. But apparently it causes problems in some terminal/shell combinations.

@sharkdp Have you tried using alternative buffer when opening the application ?
The smcup / rmcup capability of the terminal ?

I'm not sure what that means?

echo is when you press a key it displays on the terminal, but i think it is already disabled otherwise any key would be visible on a press

Echo is enabled. I can still type stuff while I run cat /dev/zero | pv -q -L 16 | hexyl (read zeros at a rate of 16 bytes per second)

@bjorn3 You are right
I've been able to test it with little bash (does not work on zsh)
orig=$(stty -g)
stty -echo
hexyl /dev/urandom
stty $orig

And it doesnt show the ^C anymore

I'm closing this due to inactivity. And because I can not reproduce this on my machine. Please feel free to comment in case it should be re-opened.


Undefined default value for the color trait

Since the latest improvement in traitlets default value validation by @takluyver , we need to set the default value of Color to Undefined for the following code to not raise a TraitError.
Otherwise, the default value  ''  for the base Unicode trait type will be instantiated and validation will raise a trait error.
from ipywidgets import Widget, Color
from traitlets import List

class Foo(Widget):
    bar = List(trait=Color())

Foo()

Looks good to me.


pull request for e2e test at 12/21/2016 09:15:19

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


Update s2i GH action to add latest tag

@pabrahamsson Does the new GitHub action auto-tag latest or do we have to tell it to do that?

It will use the sha & latest by default
https://github.com/redhat-cop/github-actions/blob/v2/s2i/action.yml#L35-L38


dart2js: add a "stable" namer under a flag

Our frequency namer might not be stable enough for incremental builds and sending diffs of js code. It might be worth having a second namer under a flag to support this use case.
One possibility is for such namer to consume names picked on previous runs of the compiler. So on a first run we do frequency naming, and a subsequent compiler run consumes a table of names that we picked before and only uses the frequency namer for new symbols that we haven't seen before.

I think using previous names tends to complicate the build process.
It will work very well for small changes, but it will tend to drift away from the ideal.
We should try and make the frequency namer stable first.
Names are allocated in order, either by first-reference, or by frequency.
The main problem is that if an element moves ahead of other elements, all the following elements get different names.

Frequency naming will do this for a small change that adds a named element, or does +1 on the usage count. There are a huge number of elements with two references, e.g. closure classes, so this always happens.
Plain naming is less sensitive, but will cause a massive difference if some new code is compiled ahead of other code, e.g. add new SplayTreeMap(); to the start of main.

I think we could make the namer more stable by bucketing elements into those that get names like x, xx, xxx. Elements should have a preferred name in the bucket, perhaps from a hash code derived from the name or other infrequently changed attributes (especially anonymous closures).  Names are allocated in decreasing frequency order, given their preferred name unless it is taken.
A potential downside of this scheme is that instead of names like 'aa1', 'aa2', etc, we will get names spread across the bucket. Perhaps this could be helped by having sub-buckets that better match the power-law like distribution of frequencies.

I have noticed that some names are unstable because the elements are not easily distinguished.
In some apps there are many hundreds of generated libraries, all with the same top-level elements, e.g. a bool visited flag. These are all used the same number of times, have the same name etc, so

the initial hashcode used in renaming is the same
in frequency-based renaming they are all clustered together without any hint to distinguish them.

In the past we used library tags to distinguish them. We might need to do something deterministic based on the tail of the library URI.


update for applying patches

When applying a patch, the code was directly changing this.values (the directly accessed values in the config object).  This has a couple problems

This would not run the changed event lifecycle for the config in process applying the patch.  Even with refresh this' values would get changed, the store updated, refresh broadcast and the subscriber would then compare current's (this') values to those in the store.  They would of course be the same since step 1 was to update this.values.
This approach was also not symmetrical wrt set and delete.  Those operations would only update the store and then rely on refreshing to get the changes into this.values.

This problem was preventing the inmemory configuration from being controlled by cc.

Hi @jeffmcaffer, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor. If you're full-time or an intern, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@willbar said it's good


Broken link in docs/setup.md for migrations

https://github.com/vierge-noire/cakephp-fixture-factories/blob/main/docs/setup.md

Fixed


world name appear when quick start game

Contains
Fixes #3583 by showing the world name in worlds&biomes and in description box of world when game is quick start

How to test

Click on Single Player and quick start a game

Start Playing a game and exit to main menu

Again Click on Single player and then Click on your last Played game

Click on details then Click on World&Biomes you will be able to see the name of world

Click on the name of world you will be able to see the name in Module description

Outstanding before merging

[ ] * Still could allow for custom names (where the player can name the world what they would like instead of "main" or "Perlin-1").

Hooray Jenkins reported success with all tests good!

@jellysnake removed "==true" and thanks for the review

Hooray Jenkins reported success with all tests good!


Type checker rewrite in Kind2

Why are you removing all these functions?

Closed due to the split of the source code into two PRs #50 and https://github.com/Kindelia/Wikind/pull/32.


Update build configuration

webpack local dev server

ChangeSet:

Removed obsolete bower and travis configuration
addded circle ci configuration with (test and NPM release steps)
refactored the project structure to follow the other frontend projects.
added local webpack server setup to view the demo page.

Silence from frontend guild == consent :slightly_smiling_face:


Update InventoryTransactionPacket, ContainerOpenPacket (ContainerType enum), TextPacket (Type Enum)

Merged in c7f634fb273d6bf512f6920eb0b49d10ed45b7cb.  Only change I made was to uncomment writing hasNetworkIds when serialising.

Derp, not sure how I missed that.


Unknown method resource_name

Asana task Devise devise_mapping and resource_name

This also contains an upgrade to rspec-rails because that is needed to support controller spec (with views) with Rails 6.


Update agents-overview.md

Docs Build status updates of commit 73bb6d3:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/azure-monitor/agents/agents-overview.md
:bulb:Suggestion

Details

articles/azure-monitor/agents/agents-overview.md

Line 94, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 124, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Elitebook 8470p New install Ventura 13.3 - No Bluetooth

Before I had Monterey and the wifi was not working ( I have a BCM943224HMS which supposedly was compatible with Monterey but no go. Bluetooth would work fine). Now using the new tools from your github I installed Ventura, everything is working awesome, but now I do have Wifi but no Bluetooth.

Any ideas on how to fix the bluetooth? I installed exactly as you showed in the videos.
I include my EFI to see if theres anything I could change to get the bluetooth working?
EFI.zip

I know its same for me I disable the card Bluetooth in bios then I use a dongle compatible for now

Bug Fix
Add this kext then Enable it.
Reactivate Bluetooth in bios then unplug dongle USB Bluethoot
BrcmFirmwareData.kext.zip


App Crashes when asking for Camera Permission on Android

I have not been able to find a way around this - this is currently crippling my app.
Unity 2021.3.31f1
Android 12, 13 tested
Call Stack for Android crash
E  Build fingerprint: 'samsung/a14xmue/a14xm:13/TP1A.220624.014/A146U1UEU4BWI5:user/release-keys'
E  Revision: '0'
E  ABI: 'arm'
E  Timestamp: 2023-11-30 09:37:17-0800
E  pid: 5683, tid: 5870, name: Thread-109  >>> com.VisualMusicDesign.SeeMusic <<<
E  uid: 10279
E  signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
E      r0  00000000  r1  000016ee  r2  00000006  r3  a8239bd8
E      r4  a8239be8  r5  a8239bd0  r6  00001633  r7  0000016b
E      r8  00000000  r9  ffffffff  r10 a8239bd8  r11 00000000
E      ip  000016ee  sp  a8239bb8  lr  eb08651f  pc  eb086532
E  backtrace:
E        #00 pc 00062532  /apex/com.android.runtime/lib/bionic/libc.so (prop_area::map_prop_area_rw(char const*, char const*, bool*)+254) (BuildId: f734bc7ed94a319ed18ede42bc901098)
E  managed backtrace:
E        #00 (wrapper managed-to-native) UnityEngine.AndroidJNI:CallStaticObjectMethod (intptr,intptr,UnityEngine.jvalue[])
E        #01 UnityEngine.AndroidJNISafe:CallStaticObjectMethod (intptr,intptr,UnityEngine.jvalue[]) <0x27>
E        #02 UnityEngine.AndroidReflection:GetMethodMember (intptr,string,string,bool) <0x11b>
E        #03 UnityEngine._AndroidJNIHelper:GetMethodID (intptr,string,string,bool) <0x5f>
E        #04 UnityEngine.AndroidJNIHelper:GetMethodID (intptr,string,string,bool) <0x2b>
E        #05 UnityEngine._AndroidJNIHelper:GetMethodID<ReturnType_REF> (intptr,string,object[],bool) <0x43>
E        #06 UnityEngine.AndroidJNIHelper:GetMethodID<ReturnType_REF> (intptr,string,object[],bool) <0x3b>
E        #07 UnityEngine.AndroidJavaObject:_Call<ReturnType_REF> (string,object[]) <0x87>
E        #08 UnityEngine.AndroidJavaObject:Call<ReturnType_REF> (string,object[]) <0x33>
E        #09 UnityEngine._AndroidJNIHelper:GetSignature (object) <0x56b>
E        #10 UnityEngine._AndroidJNIHelper:GetSignature (object[]) <0x67>
E        #11 UnityEngine._AndroidJNIHelper:GetMethodID (intptr,string,object[],bool) <0x1f>
E        #12 UnityEngine.AndroidJNIHelper:GetMethodID (intptr,string,object[],bool) <0x2b>
E        #13 UnityEngine.AndroidJavaObject:_CallStatic (string,object[]) <0x67>
E        #14 UnityEngine.AndroidJavaObject:CallStatic (string,object[]) <0x23>
E        #15 UnityEngine.Android.Permission:HasUserAuthorizedPermission (string) <0xb7>
E        #16 VideoKit.Devices.MediaDevice:g__GetPermissionStatus|27_3 (string) <0x13>
E        #17 VideoKit.Devices.MediaDevice:CheckPermissionsAndroid (VideoKit.Internal.VideoKit/PermissionType,bool) <0x2f>
E        #18 VideoKit.Devices.MediaDevice:CheckPermissions (VideoKit.Internal.VideoKit/PermissionType,bool) <0x27>
E        #19 VideoKit.Devices.AudioDevice:CheckPermissions (bool) <0x17>
E        #20 MIDIControl/HEGACJCNODG:MoveNext () <0x47>
E        #21 System.Runtime.CompilerServices.AsyncTaskMethodBuilder:Start<MIDIControl/HEGACJCNODG> (MIDIControl/HEGACJCNODG&) <0xbb>
E        #22 MIDIControl:GCIEKGPBOJB () <0x9f>
E        #23 MIDIControl/EOMKNNJCMHP:MoveNext () <0x43>
E        #24 System.Runtime.CompilerServices.AsyncTaskMethodBuilder:Start<MIDIControl/EOMKNNJCMHP> (MIDIControl/EOMKNNJCMHP&) <0xbb>
E        #25 MIDIControl:EKCLABCFMMJ () <0x9f>
E        #26 System.Threading.Tasks.Task`1<TResult_REF>:InnerInvoke () <0x53>
E        #27 System.Threading.Tasks.Task:Execute () <0x2b>
E        #28 System.Threading.Tasks.Task:ExecutionContextCallback (object) <0x47>
E        #29 System.Threading.ExecutionContext:RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) <0x1bb>
E        #30 System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool) <0x2b>
E        #31 System.Threading.Tasks.Task:ExecuteWithThreadLocal (System.Threading.Tasks.Task&) <0x103>
E        #32 System.Threading.Tasks.Task:ExecuteEntry (bool) <0xc3>
E        #33 System.Threading.Tasks.Task:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () <0x17>
E        #34 System.Threading.ThreadPoolWorkQueue:Dispatch () <0x213>
E        #35 System.Threading._ThreadPoolWaitCallback:PerformWaitCallback () <0x3f>
E        #36 (wrapper runtime-invoke) :runtime_invoke_bool (object,intptr,intptr,intptr)
E  Forwarding signal 6
A  Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 5870 (Thread-109), pid 5683 (Design.SeeMusic)
---------------------------- PROCESS ENDED (5683) for package com.VisualMusicDesign.SeeMusic ----------------------------

The crash happens when checking either:
AudioDevice.Discover()
VideoDevice.Discover()
or checking permissions for either audio or video devices.

Wondering if the 0.0.18 alpha released tonight includes a fix for this?
(I know you had previously mentioned on email to look for a fix in the alpha coming beginning of this week)

No but this is up next, will follow up on ETA. I've had some delays come up from other issues devs have raised.

Thank you

Is there any chance there could be an alpha with a fix for this before Monday?
Thank you

@pnostudiodeveloper working on it right now, will post updates as I have them.

Hey @pnostudiodeveloper can you test out VideoKit 0.0.18-alpha.2? Follow the install instructions here. Happy weekend!

It's working!  Thanks very much.

Sounds good.

Closing this ahead of the 0.0.18 update.


centro seim

@Miguuuelz22 Please provide us with:

the school official website URL
the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

@Miguuuelz22 You might miss my previous comment. Please react.

@Miguuuelz22 I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the aforementioned issue. Thank you for your understanding!


merge #123 with master (upgrade foreground-child, spawn-wrap).

merge of #123 with master.

Awesome, thanks!


[core] Enforce checkstyle for core

Fixes #895.

This should fail Travis CI tests until the other PRs are merged. This change can then be rebased and tested again.

Specifically requires:

#915
#916
#917
#918

We are so close. If Travis passes that means we are good with checkstyle on core!


Migrate from deprecated repos to the community one

The Kubernetes project is deprecating the repositories the module uses to install the binaries. The module should adopt the new community repositories.
Reference: https://kubernetes.io/blog/2023/08/31/legacy-package-repository-deprecation/
https://github.com/sighupio/fury-kubernetes-on-premises/blob/9c1af6becbb6452e1712d9049f3eaf73d6943b2a/roles/kube-node-common/vars/main.yml#L5

fixed in #73


no exit confirmation when VS window close button pressed

Issue Type: Feature Request
Hello,
It would be nice to ask the user if she or he really wants to exit the VS, when the close button is pressed on the application frame. It could be pressed accidentally also.
Thank You , Andras
VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T10:55:45.459Z)
OS version: Windows_NT x64 6.1.7601

/duplicate of #14710
In particular see https://github.com/microsoft/vscode/issues/14710#issuecomment-316562950 for a suggestion.


Make boxed title's horizontal position more customizable

In v1.1.0 boxed title has a boxed-align which changes horizontal alignment, but it only has 5 fixed positions. A custom position using float (or ratio) should be added where 0 is equal to start and 1 is equal to end. Related issue: #13 (with some config examples).

It makes sense to me 🧐
This could be a good change to implement with #13 changes. As I said there, I will look at the code for a possible refactorization of boxed titles drawing.

Update:
As in #13 was mentioned, an offsetoption is intended to be added. So, the issue with custom position can be considered solved, and its implementation discussion moved to #13 🎉.


When I was doing inference, I used init_detector to report this error : TypeError: CascadeRCNN: ResNet: init() got an unexpected keyword argument 'init_cfg'

C:\Users\12481.conda\envs\mmd\python.exe C:/Users/12481/Desktop/win/WIN/pre_mult.py
Traceback (most recent call last):
File "C:\Users\12481.conda\envs\mmd\lib\site-packages\mmcv\utils\registry.py", line 51, in build_from_cfg
return obj_cls(**args)
TypeError: init() got an unexpected keyword argument 'init_cfg'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\12481.conda\envs\mmd\lib\site-packages\mmcv\utils\registry.py", line 51, in build_from_cfg
return obj_cls(**args)
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\detectors\cascade_rcnn.py", line 25, in init
pretrained=pretrained)
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\detectors\two_stage.py", line 26, in init
self.backbone = build_backbone(backbone)
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\builder.py", line 39, in build_backbone
return build(cfg, BACKBONES)
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\builder.py", line 34, in build
return build_from_cfg(cfg, registry, default_args)
File "C:\Users\12481.conda\envs\mmd\lib\site-packages\mmcv\utils\registry.py", line 54, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
TypeError: ResNet: init() got an unexpected keyword argument 'init_cfg'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:/Users/12481/Desktop/win/WIN/pre_mult.py", line 17, in
model = init_detector(config_file, checkpoint_file, device='cuda:0')
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\apis\inference.py", line 39, in init_detector
model = build_detector(config.model, test_cfg=config.get('test_cfg'))
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\builder.py", line 77, in build_detector
return build(cfg, DETECTORS, dict(train_cfg=train_cfg, test_cfg=test_cfg))
File "c:\users\12481\week2_mmdet\mmdetection-2.11.0\mmdet\models\builder.py", line 34, in build
return build_from_cfg(cfg, registry, default_args)
File "C:\Users\12481.conda\envs\mmd\lib\site-packages\mmcv\utils\registry.py", line 54, in build_from_cfg
raise type(e)(f'{obj_cls.name}: {e}')
TypeError: CascadeRCNN: ResNet: init() got an unexpected keyword argument 'init_cfg'
Process finished with exit code 1

Maybe you can refer to https://github.com/open-mmlab/mmdetection/issues/5734
Do not set init_cfg and pretrained at the same time in your config.


Broken link: manpage of caffeinate

The link to the man of caffeinate is broken: https://github.com/vitorgalvao/alfred-workflows/tree/master/CoffeeCoffee

Thank you. Apple keeps breaking their documentation links, so I’ll just remove it.
For reference, it’s this.


breaking changes & punch list

This is the start of a list of breaking changes between Nushell and engine-q.
Breaking Changes for Usage

idx
Nushell
engine-q

1
if { } { }
if { } else { }

2
str trim -rc (char nl)
str trim -r -c (char nl)

3
config.toml
config.nu

4
let-env FOO = $nothing
hide $FOO

5
$nu.home-dir
$nu.home-path

6
$nu.temp-dir
$nu.temp-path

7
config commands
$config

8
$nu.env
$nu.env is now $env

9
$nu.path
$env.PATH/$env.Path <- can do more in config.nu

10
$nu.lang
$scope.commands

11
str to-int
into int

12
$nu.env.PROMPT_COMMAND is a string
$env.PROMPT_COMMAND is a block

13
get (has auto flatten)
get doesn't auto flatten

14
to json
to json is formatted as 'pretty'

15
environment variable is a string
environment variable can be any value

16
tags
tags is now metadata

17
bigint/bigdecimal
engine-q uses machine i64 and f64

18
File, Dir in ls
file, dir in ls

19
binaryview
binaryview has been removed (it may be an optional plugin in the future)

20
textview
textview is removed. Install bat to view source files, or pipe the output into less

21
dataframe
dfr

22
shells: active, name, path columns
shells: active, path columns

23
cd is now scoped
current directory now comes from PWD in $env. Changing directory in a block or custom command no longer changes the caller's directory. To do this, return a table that the caller can use to update their env

24
reduce $acc $it
reduce $it.acc $it.item (temporary, needs parser support)

25
char branch, char segment
char nf-branch, char nf-segment (chars that start with nf- are from nerdfont fonts)

26
save --append
We're (hopefully temporarily) removing append as it needs a bit more design before it's ready

27
wasm supported
wasm support currently not started

28
enter <filename>
engine-q only supports entering directories

29
str to-decimal
into decimal

30
'ff' | str to-int -r 16
'ff' | into int -r 16

31
pivot
renamed to transpose

32
term size -w -t
term size -c -r

33

34

35

36

37

38

39

40

Breaking Changes for Commands and Parameters

idx
breaking changes
e-q resolution
Yes = fix/No = won't fix

1
alias missing parameter equals
equals is not a parameter in engine-q
No, e-q parser works differently

2
alias missing parameter rest
rest renamed to initial_value
No, e-q parser works differently

3
all? missing parameter condition
condition renamed to predicate

4
ansi gradient missing parameter rest
rest renamed to column path (* space in param name)

4
ansi strip missing parameter rest
rest renamed to column path (* space in param name)

5
any? missing parameter condition
condition renamed to predicate

6
append missing parameter row value
row value renamed to row

7
binaryview with parameter bytes
removed from engine-q
No

8
binaryview with parameter lores
removed from engine-q
No

10
binaryview with parameter skip
removed from engine-q
No

11
cd missing parameter directory
directory renamed to path

12
compact missing parameter rest
rest renamed to columns

13
config get with parameter get
removed from engine-q
No

14
config remove with parameter remove
removed from engine-q
No

15
config set with parameter key
removed from engine-q
No

16
config set with parameter value
removed from engine-q
No

17
config set_into with parameter set_into
removed from engine-q
No

18
cp missing parameter src
src renamed to source

19
cp missing parameter dst
dst renamed to destination

20
dfr aggregate missing parameter operation
operation renamed to operation-name

21
dfr cum with parameter type
cum renamed to cumulative

22
dfr cum with parameter reverse
cum renamed to cumulative

23
dfr select with parameter rows
select renamed to get

24
dfr select with parameter rest
select renamed to get

25
dfr last missing parameter n_rows
n_rows renamed to rows

26
dfr melt missing parameter value_name
value_name renamed to value-name

27
dfr melt missing parameter variable_name
variable_name renamed to variable-name

28
dfr open missing parameter no_header
no_header reamed to no-header

29
dfr open missing parameter infer_schema
infer_schema renamed to infer-schema

30
dfr open missing parameter skip_rows
skip_rows renamed to skip-rows

31
dfr pivot missing parameter pivot column
pivot column renamed to pivot-column

32
dfr pivot missing parameter value column
value column renamed to value-column

33
dfr sample missing parameter n_rows
n_rows renamed to n-rows

34
dfr show with parameter tail
show renamed to to-nu

35
dfr show with parameter n_rows
show renamed to to-nu

36
dfr to-csv missing parameter no_header
no_header renamed to no-header

37
date format missing parameter format
format renamed to format string (* space in param name)

38
def missing parameter name
name renamed to def_name

39
drop nth missing parameter row number
row number renamed to rest

40
empty? with parameter rest

fixed with #764

41
empty? with parameter block

fixed with #764

42
enter missing parameter location
location renamed path

43
exit missing parameter code
code renamed to exit-code

44
for missing parameter var
var renamed to var_name

45
for missing parameter in
in is not a parameter in engine-q

46
for missing parameter value
value renamed to range

47
g missing parameter index
index renamed to shell-number

48
if missing parameter condition
condition renamed to cond

49
if missing parameter then_case
then_case renamed to then_block

50
if missing parameter else_case
else_case renmaed to else_expression

51
insert with parameter column
insert replaced with update comand that inserts if missing

52
insert with parameter value
insert replaced with update comand that inserts if missing

53
keep missing parameter rows
rows renamed to n

54
keep until missing parameter condition
condition renamed to predicate

55
keep while missing parameter condition
condition renamed to predicate

56
let missing parameter name
name renamed to var_name

57
let missing parameter equals
equals is not a parameter in engine-q

58
let missing parameter expr
expr renamed to initial_value

59
let-env missing parameter name
name renamed to var_name

60
let-env missing parameter equals
equals is not a parameter in engine-q

61
let-env missing parameter expr
expr renamed to initial_value

62
ls missing parameter path
path renamed to pattern

63
nth missing parameter row number
row number renamed to rest

64
open missing parameter path
path renamed to filename

65
open missing parameter encoding
moved encoding to decode `

66
prepend missing parameter row value
row value renamed to row

67
select missing parameter columns
columns renamed to rest

68
skip missing parameter rows
rows renamed to n

69
skip until missing parameter condition
condition renamed to predicate

70
skip while missing parameter condition
condition renamed to predicate

71
str to-datetime with parameter rest
str to-datetime replaced with into datetime

72
str to-datetime with parameter format
str to-datetime replaced with into datetime

73
str to-datetime with parameter timezone
str to-datetime replaced with into datetime

74
str to-datetime with parameter offset
str to-datetime replaced with into datetime

75
str to-decimal with parameter rest
str to-datetime replaced with into decimal

76
str to-int with parameter rest
str to-int replaced with into int

77
str to-int with parameter radix
str to-int replaced with into int

78
to json missing parameter pretty
pretty missing because it defaults to pretty

79
where missing parameter condition
condition renamed to cond

80
wrap missing parameter column
column renamed to name

81
zip missing parameter block
block renamed to other

Punch List
This is a punch list of things that need to be added/fixed to existing functionality.

[x] the -i part of do -i
[x] the -al part of ls -al
[x] the -n part of table -n
[x] the -n part of each -n
[x] the -n part of for -n
[ ] the -s part of help
[x] the - part of cd -
[ ] syntax highlighting in Examples of --help
[x] piped input to a custom command (def)
[ ] open file.txt | skip 10 | take 100 | into binary -> pretty hex
[x] some thing

Just Different

Update config settings in real time without having to exit and relaunch nushell. let $config = ($config | update edit_mode vi)

Other
main command in scripts
If the script contains main it will be ran after all the script is executed. It also accepts arguments from the command line. You can run it like this: nu foo.nu arg1 --flag and if the script contains a hashbang/shebang line (#!/usr/bin/env nu): ./foo.nu arg1 --flag.

Not sure where else to ask this - but wondered if it should be documented about now needing to decode utf-8 a lot of things that previously just worked when piping to str. I reviewed #570 but didn't find any documentation that clearly marks this as a breaking change - especially given the number of external commands requiring parsing to nushell and even though they return plain "strings" they are treated as ByteStreams and need to be decoded.

I think we should have a heuristic that searches for the null character in the first x bytes and if finds it make it binary, otherwise make it text.


Add valid-package-file-require rule

This adds a rule that ensures file paths passed to require are valid
within the context of package modules. These can differ from files paths
commonly used in CommonJS modules in that they require the file
extension at the end, and need the ./ prefix for files that are
required from the same directory or farther down in the directory
structure.
This is especially useful for code that is written to be compatible both in a ResourceLoader context and in a webpack or node, such as https://github.com/wmde/WikibaseDataModelJavaScript.

LGTM, asking for others to chime in.

LGTM. I think we may want to move this rule also to eslint-plugin-wikimedia because adding a suffix doesn't seem like a bad idea for Node.js in general as well.
It makes the code less prone to ambiguity, avoids various logic routines Node.js would have to run (including the reading of package.json for sub directories to look for a main property).
It also makes it more aligned with the future import and export syntax which has been spec'ed so far to explicitly and intentionally not allow autocompletion for file imports.

We use this already at WMDE and it works great. It's time to upstream it.

@Krinkle This rule should will be added to eslint-config-wikimedia/mediawiki.json. I think you are suggesting we also add it to eslint-config-wikimedia/node.json or eslint-config-wikimedia/common.json?
(nb eslint-plugin-wikimedia doesn't exist)

Yeah, (and yes, eslint-config-wikimedia). Meaning, not specific to MW/RL code.


Redirect to article page rather than home after clicking "Sign in or sign up to add comments on this article"

🚀 feature request
Relevant scope
What is the scope of this request?

[X] Frontend specs
[ ] Backend specs
[ ] Other... Please describe:

Description
 A clear and concise description of the problem or missing capability...
Visit an article signed out. It shows "Sign in or sign up to add comments on this article.". Click sign in and sign in. It redirects you to home / instead of the article. Tested on https://demo.realworld.io and https://react-redux.realworld.io/
Describe the solution you'd like
 If you have a solution in mind, please describe it.
Redirect to the article you were in, not home.
Describe alternatives you've considered
 Have you considered any alternative solutions or workarounds?

That's great that you mention that.
How about in the future spec the login and register are not any distinct routes anymore, but buttons which opens modals?
To have modals in the spec, to show of how portaling works is I think a good idea anyway.
Why I dislike having auth as routes:

these routes are only valid depending on your current auth-state
these are not really sharable url's
they pollute the browser history, the back-button will lead you to a page which isn't valid/relevant anymore

Why I think modals for login/register are superior:

the user stays on the same page, no weird remembering where the user came from is necessary
browser-history only has valid and relevant pages in it
showing of how to implement portals in any given tech

Yes, that would not be a bad option I think. Notably for me my general concern is to make the logged out website viewable without JavaScript, so no problem with the login URL being a JS-only button. I guess someone would just need to sit down and make a reference POC if there's strong support for it.


Fix flags for KCM in 1.22 version

Issue #, if available:
Description of changes:
Fixes couple of broken flags in KCM for 1.22 version for guest clusters.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Haha, these functions will be more and more as we support more and more  older versions of K8s as new versions get released upstream.  Unfortunately we are stuck with this currently but I encourage us to move in the direction of cutting release branches like upstream and not support these kind of functions in Head, if possible.

Haha, these functions will be more and more as we support older versions of K8s as new versions get released upstream. Unfortunately we are stuck with this currently but I encourage us to move in the direction of cutting release branches like upstream and not support these kind of functions in Head, if possible.

How will that look when we want to create different Kubernetes versions? As these will be different binaries for operator based on Kubernetes versions.

Haha, these functions will be more and more as we support older versions of K8s as new versions get released upstream. Unfortunately we are stuck with this currently but I encourage us to move in the direction of cutting release branches like upstream and not support these kind of functions in Head, if possible.

How will that look when we want to create different Kubernetes versions? As these will be different binaries for operator based on Kubernetes versions.

Well I was saying same binary for upstream supported versions of k8s and not having to maintain same binary for non-supported upstream versions of K8s, so that if someone wants to test something on older versions they can surely do so by building/downloading that release binary and do the testing.


Debug

May I ask why do we want to see this even in debug logs? It's like 50 entries per second, would it ever be useful with such high frequency?
Sometimes we print debug info in Sui to help debug stuff, and I suspect this will get in our way (at least for devnet).

yes we can remove some of the logs. It brings 50 entires per second because of the default parameters we use in Narwhal/Sui, otherwise it is arbitrarily slow.


Revert :read-only selector back to [readonly]

Reverts twbs/bootstrap#33642. Fixes #33860, fixes #33925.

why isn't there a design difference between read-only and disabled?

The difference between disabled and readonly is that read-only controls can still function and are still focusable, whereas disabled controls can not receive focus and are not submitted with the form and generally do not function as controls until they are enabled.

The idea of using bootstrap is that the designs of the web pages are similar and in the best of cases that the elements are intuitive; so being an end user and seeing a disabled or read-only field, I'm not getting any visual feedback...
would it be possible to use a specific pointer for each type of situation?
for example field disabled can use cursor: not-allowed;
for example field read-only i have not find a default cursor, and cant find any related icon in BS ICON but i search in other solution and find one that i can use in a custom from FontAwesome:
for example font awesome have this icon:

in the end I was hoping that this could be fixed within BS as part of its visual aid to the end user.

@arcanisgk Please don't add unrelated comments to closed pull requests. You won't likely get a reply from anyone. This was also addressed to an extent in https://github.com/twbs/bootstrap/pull/36499 and will ship soon.


org_tensorflow download error

Hi,I'm trying to compile the android apk with bazel on my ubuntu pc.
Now ,i'm facing some problems while doing this.
Downloading org_tensorflow error:

proxy : qv2ray in linux, (I'm i China mainland)
Problem: not able to go throw org_tensorflow 's download

So ,I've tried  to download org_tensorflow.tar.gz via firefox by the url showed to me.
And then ,I hope to copy it to the folder which was showed when bazel dumped.
But things did not work still.
the command line is just :
 bazel -c opt ....(same to the command in turtial in andorid)  --keep_going
And I tried to put the tar.gz file to org_tensorflow folder .but things didn't changed.
hoping for your help!

Well ,the vpn is not very stable ,and its speed is low (~10kb/s)
While downloading the tar ,It's ~3MB/s

Hi @Lr-2002, Could you please mention the steps followed to reproduce the above error. Did you use mediapipe in the above for installation? If yes then share the error logs .

Well,sorry ,the problem is not settled until now.I'm still seeking for solutions.
And now ,I'd better to state it more precise:

When did the problem happened?
With bazel to build the android sample
using command ```bazel build -c opt --config=android_arm64 --keep_going mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu:handtrackinggpu

    The error log:
    ```
    ERROR: An error occurred during the fetch of repository 'org_tensorflow':
   Traceback (most recent call last):
	File "/home/lr-2002/.cache/bazel/_bazel_lr-2002/858766351c9bf1877743094e06ee32df/external/bazel_tools/tools/build_defs/repo/http.bzl", line 111, column 45, in _http_archive_impl
		download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/tensorflow/tensorflow/archive/c67f68021824410ebe9f18513b8856ac1c6d4887.tar.gz] to /home/lr-2002/.cache/bazel/_bazel_lr-2002/858766351c9bf1877743094e06ee32df/external/org_tensorflow/temp172222072687291382/c67f68021824410ebe9f18513b8856ac1c6d4887.tar.gz: Premature EOF
ERROR: no such package '@org_tensorflow//tensorflow': java.io.IOException: Error downloading [https://github.com/tensorflow/tensorflow/archive/c67f68021824410ebe9f18513b8856ac1c6d4887.tar.gz] to /home/lr-2002/.cache/bazel/_bazel_lr-2002/858766351c9bf1877743094e06ee32df/external/org_tensorflow/temp172222072687291382/c67f68021824410ebe9f18513b8856ac1c6d4887.tar.gz: Premature EOF

What things did i do?

Download the tensorflow.tar.gz mentioned
copy it into the folder and replace the former tar.gz
rerun the command mentioned.
But things didn't changed .

What's my environment?

bazel 3.7.2
mediapipe updated.
VPN via qv2ray in China (not very stable)

My problem:
How to fix the problem ?

Well ,upto now ,things has been better while new problem occured

The former problem was solved by

re-open a folder to re-do the process (indeed it fixed lots of problems which was not setlled former)

A new problem happend :

ERROR: Analysis of target '//mediapipe/examples/android/src/java/com/google/mediapipe/apps/handtrackinggpu:handtrackinggpu' failed; build aborted: Analysis failed
The $ANDROID_NDK_HOME is ../Sdk/ndk/<version> while the bazel detected the ../Sdk/ndk-bundle which is not ok

And I deleted the ndk-bundle but noting changed.
I'm still seeking for a solution ,plz

What's more :
The ndk and sdk are all installed by Android Studio
And using the setup_android_sdk_ndk.sh ,it showed :
Bazel will locate Android SDK and NDK automatically.```
It doesn't seem that ndk could be a problem?

Well ,things have been better with close the terminal and reopen it

Then I faced the problem duplicate keyword argument: path
just turn to WORKSPACE and delete the path duplicated

Thanks for sharing the clear details. Could you please look at this reference.

Oh ,Yeah ,thanks a lot
I'll try it latter
BTW,sorry for being late to reply

As we see your query addressed,  We are closing this issue now. Feel free to reopen if the same issue exists. Thanks


iCreate an issue

i have copy my serverpod project from window to mac it give me this error.
Unhandled exception:
Null check operator used on a null value
#0      new DatabaseConfig._ (package:serverpod_shared/src/config.dart:142:37)
#1      new ServerpodConfig (package:serverpod_shared/src/config.dart:61:31)
#2      new Serverpod (package:serverpod/src/server/serverpod.dart:242:14)
#3      run (package:pmdccolleges_server/server.dart:14:15)
#4      main (file:///Users/zakaullah/Development/Pmdc_Zaka_final/Pmdc-Serverpod/pmdccolleges_server/bin/main.dart:6:3)
#5      _delayEntrypointInvocation. (dart:isolate-patch/isolate_patch.dart:295:33)
#6      _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:192:26)

It is possible that a variable has a value that is null and that you are using the bang (!) operator on it. The bang operator is a shorthand for throwing when your value is null. You could make sure that it is not null by guarding against null with if (value == null) ....
Take a look at run (package:pmdccolleges_server/server.dart:14:15) and (file:///Users/zakaullah/Development/Pmdc_Zaka_final/Pmdc-Serverpod/pmdccolleges_server/bin/main.dart:6:3) your error should be located somewhere there.

cc @lrhn the flutter repo has a nice way of handling support requests. I think the sdk repo would benefit from implementing something similar, see: https://github.com/flutter/flutter/issues/new/choose i.e. they suggest asking on e.g. stack overflow.

Github templates sounds like a job for infrastructure or people with opinions. @athomas @mit-mit
For the current question, the error happens in package:serverpod_shared, so the owners of that would be the ones in a position to fix it (https://github.com/serverpod/serverpod/issues).
In this case, the "fix" would probably at most be to do input validation and throw a more informative error.
Looking at the code, the data-base configuration being loaded seems to be missing a name entry in the YAML file.

@itsjustkevin Should we copy some of the templates from Flutter here?

@athomas sure we can do that.  I opened https://github.com/dart-lang/sdk/issues/51747 to keep the discussion out of the current issue.


Many columns on the framework tree stuck since yesterday morning

It looks like many machines are idle, but no work is starting:

@yusuf-goog on call

The root cause is https://github.com/flutter/flutter/issues/122117.
The hanging yellow boxes prevents back filling.
Working to vacuum those stale statues.

Backfilling started.

@keyonghan can we close this one?

Yes. Root cause is still being investigated/worked on.


Provide further details on "how to edit the WunderWay"

Provide a short checklist / or enhance the step-by-step for editing the WunderWay in a fork and local branch.
This should also cover the Issue- / PullRequest-workflow and give advise on specialties (e.g. keywords to close issues)
References:

https://github.com/blog/1506-closing-issues-via-pull-requests
https://help.github.com/articles/closing-issues-via-commit-messages/

This is a duplicate of #83. I have moved my last comment over.


Feature/update marshmallow

Updates marshmallow to 3.0.0rc9 and related dependencies.
Based on the dates of the released versions, I decided to go to v3 even though it is an rc version and picked the most recent one: https://github.com/marshmallow-code/marshmallow/releases
I have 3.0.0b7 in requirements because as far as I can tell I am not using any features from anything above it.
Still need to run the e2e tests and most likely modify the missing value for the api.

Codecov Report

Merging #306 into master will not change coverage.
The diff coverage is 93.33%.

@@           Coverage Diff           @@
##           master     #306   +/-   ##
=======================================
  Coverage   64.34%   64.34%
=======================================
  Files          48       48
  Lines        3200     3200
=======================================
  Hits         2059     2059
  Misses       1141     1141

Impacted Files
Coverage Δ

relay/api/schemas.py
95.23% <ø> (ø)
:arrow_up:

relay/api/fields.py
83.92% <93.33%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

It seems to me that when I run the e2e test from this pr: https://github.com/trustlines-protocol/clientlib/pull/239
with or without this commit: https://github.com/trustlines-protocol/relay/commit/68b670dd5dc1db892bd0c347ed56bd0a26cb1047
on this branch, the result is the same. But I may be tired.

I would have expected that we also have to change the way we specify the default value. But it seems to work and we have a test case now for it, so I am gonna merge it.


Notebooks: add multi_connection field to notebook metadata

This PR adds the multi_connection field to notebook metadata and moves the loading content metadata logic into a separate method in NotebookModel.

Pull Request Test Coverage Report for Build 519228051

13 of 19 (68.42%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 43.282%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/notebook/browser/models/notebookModel.ts
13
19
68.42%

Totals

Change from base Build 519209320:
-0.01%

Covered Lines:
24621

Relevant Lines:
52081

💛  - Coveralls

Pull Request Test Coverage Report for Build 519228051

13 of 19 (68.42%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 43.282%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/services/notebook/browser/models/notebookModel.ts
13
19
68.42%

Totals

Change from base Build 519209320:
-0.01%

Covered Lines:
24621

Relevant Lines:
52081

💛  - Coveralls

@Charles-Gagnon This boolean will be checked before rendering a connection dropdown in each cell (this dropdown will only be rendered if the notebook is in multi-connection mode). When a new notebook is created, the user can change to multi-connection mode before adding any connections.
multi_connection_mode might be a better name here - I'll update it.

@Charles-Gagnon This boolean will be checked before rendering a connection dropdown in each cell (this dropdown will only be rendered if the notebook is in multi-connection mode). When a new notebook is created, the user can change to multi-connection mode before adding any connections.
multi_connection_mode might be a better name here - I'll update it.

Tests 😄 ?

@chlafreniere will add tests in a separate PR :)

@lucyzhang929 ok. looking forward to them 😄


Test for https://github.com/defunctzombie/fixjs/pull/7

This test fails with https://github.com/defunctzombie/fixjs/commit/b96dba78d701ada3102f076a135f1f073a8fcf84
And passes with https://github.com/defunctzombie/fixjs/commit/5010c720b1f3a8d71c5cda80945aa7c0bf1ba882
But it seems there are some problems when running all the test files in parallel if the buffered string is too long.

Hi, Could you integrate this pull request? Thanks!

small comment. Once that is resolved please squash the commits (we only need one commit for this). Thanks!

Done! Thanks :+1:


Google registration not working with django-allauth 0.55.2

Hi there,
After updating to django-allauth 0.55.2 (which is theoretically supported by dj-rest-auth[with_socials] ) I started getting errors when trying to register on my website via Google.
The problem is appearing in the line: 160 on dj_rest_auth/registration/serializers.py
ret = complete_social_login(request, login)

I did some digging and I think it's somehow connected to the latest update in 0.55.2 django-allauth in a property that the mentioned function uses:
def complete_social_login(request, sociallogin):
    assert not sociallogin.is_existing
    ...

This has changed from:
    @property
    def is_existing(self):
        """Account is temporary, not yet backed by a database record.
        """
        return self.account.pk is not None

to:
    @property
    def is_existing(self):
        """When `False`, this social login represents a temporary account, not
        yet backed by a database record.
        """
        return self.user.pk is not None

@itsdkey What error are you getting exactly? Was it something like this?
save() prohibited to prevent data loss due to unsaved related object 'app'.

My teammate and I ran into some issues with the Google integration and ended up having to subclass the SocialLoginSerializer in order to make sure that the login endpoint for Google accepted a "refresh_token" as well as a "expires_in" property. Something we changed in that process seems to have addressed the above error, I'll try to dig more into it tomorrow.

The error was an AssertionError with no message (because of the first statement in complete_social_login function).

Oh I'm sorry, that's a different issue than I ran into. 😬

+1
This is the django-allauth commit that made this change : https://github.com/pennersr/django-allauth/commit/6c10cda1fe35d3d275bdedc6bee1e3f382f54401
For now downgraded dj-rest-auth back to 4.0.1 as a resolution.

Update on this: As a part of https://github.com/pennersr/django-allauth/issues/3446 , django-allauth has fixed this in 0.58.1 already. This might happen for applications that are using UUID as pk for user model.

@Aniket-Singla Thanks you a lot(after spend approximately 7 hours )!!! It's really fixed =)
I have User model with UUID primary key and  after restore default id field it start work
My example of using django-allauth and dj-rest-auth
users/views.py
class GoogleLoginRedirect(RedirectView):
    url = "https://accounts.google.com/o/oauth2/v2/auth?redirect_uri=<REDIRECT_URL(WITH OUT SLASH IN THE END)>&prompt=consent&response_type=code&client_id=<CLIENT_ID>&scope=openid%20email%20profile&access_type=offline"
    permanent = True

    def get_redirect_url(self, *args, **kwargs):
        return self.url

import requests
class GoogleCallback(View):
    def get(self, request, *args, **kwargs):
        code = request.GET["code"]
        response = requests.post("http://localhost:8000/dj-rest-auth/google/", json={
            "code": code
        })

        django_response = HttpResponse(
            content=response.content,
            status=response.status_code,
        )
        for k, v in response.headers.items():
            django_response[k] = v

        return django_response

django-allauth = "~0.56.1"
dj-rest-auth = "~5.0.2"

You are using 0.56 -- there was an issue that was fixed in 0.57.0 (see https://github.com/pennersr/django-allauth/issues/3446#issuecomment-1732051830)

Great, it works! I think we can close this issue then.


Initialize state

A basic initialization of the state of app, which will be handle by Redux state container. It could be considered as a simple starting point, which sketch

room
participants
messages

Please, keep in mind that, after a brief discussion, we decided to structure the state ecosystem following an approximation to the ducks modular approach proposal.

Rules
A module...

MUST export default a function called reducer()
MUST export its action creators as functions
MUST have action types in the form npm-module-or-app/reducer/ACTION_TYPE
MAY export its action types as UPPER_SNAKE_CASE, if an external reducer needs to listen for them, or if it is a published reusable library.

https://github.com/erikras/ducks-modular-redux#rules

There are other approaches on top of that, using directories, but we want to start with a file per duck.

A long article about React & Redux & Ducks (not completely read yet, but seems interesting)
https://medium.com/swlh/the-good-the-bad-of-react-redux-and-why-ducks-might-be-the-solution-1567d5bdc698


Closes-Bug: 5

Description: Improves the README with more finer details
This fix addresses the following details in installation & Setup
of Service Fabrik Broker:

Adds a reference to motivation behind Service Fabrik Broker
Adds Table of Contents
Updates the docker installation url for ubuntu
Adds a step to manage docker as a non-root user. This is
required else you hit socket connection errors.
Adds a step to deploy cloud foundry.
Adds a step to install cf cli

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ashish Jain seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fix admins

Coverage increased (+0.2%) to 96.241% when pulling 769a03874ea80836e731ba8ff6a0fec82f2cdd15 on fix_admins into 731e45fe29be0260f49d548e059623982f320a10 on master.

Coverage increased (+0.2%) to 96.241% when pulling 769a03874ea80836e731ba8ff6a0fec82f2cdd15 on fix_admins into 731e45fe29be0260f49d548e059623982f320a10 on master.


Reset history

I think we should consider resetting the history on this project.  We started as a straight clone to ease the transition, but now that we've transitioned to a more permanent structure, there isn't a whole lot of benefit to keeping history on all of vendor as a for instance.
Keeping the old history is hiding the real actors in this repo from people searching through.
@k82cn, what do you think?

can you filter-branch out nearly everything?

can you filter-branch out nearly everything?

The only way I know to do that is to start over from kube/kube.  Knowing the end state I could use filter-branch --subdirectory-filter and then copy th ecurrent state of the repo over and force push.
Is there a cleaner way?

Not that I know of.
On Wed, Sep 28, 2016 at 4:13 PM David Eads<EMAIL_ADDRESS>wrote:

can you filter-branch out nearly everything?
The only way I know to do that is to start over from kube/kube. Knowing
the end state I could use filter-branch --subdirectory-filter and then copy
th ecurrent state of the repo over and force push.
Is there a cleaner way?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kube-mesos-framework/issues/21#issuecomment-250328415,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACDCFHDu1S0j_8xH_489WCHi3iRuDNMks5quvSCgaJpZM4KJSPe
.

@k82cn I'm inclined to do this tomorrow to help with the ability to inspect the project.  I'll save history on stuff from contrib/mesos

Agree with you to clear up the history :). Thanks very much.

Alright, here goes.  There's no way to do this other than a force push.  I've created a branch here: https://github.com/kubernetes-incubator/kube-mesos-framework/tree/unfiltered-history which I think will survive the push, but which we should remove when we're sure we're happy with the new history.

I think it worked and the result looks a lot cleaner.


4th task is unclear in the documentation

Hi @andrejrakic the 4th task is a bit confusing , MonitorMockLending is to be deployred on the liquidity chain or other chain ?

To deploy the MonitorMockLending.sol smart contract you can use deploy-monitor-mock-lending task:

@andrejrakic roger that , I tried but got error. I would like to confirm the lpsc address in the below code is the address of the liquidity chain or the other chain ?
npx hardhat deploy-monitor-mock-lending
--min-health-factor <MIN_HEALTH_FACTOR_BEFORE_LIQUIDATION_SAVING_IS_TRIGGERED>
--router <CCIP_ROUTER_ADDRESS>
--lending-address <MOCK_LENDING_ADDRESS>
--token-address <REPAY_TOKEN_ADDRESS>
--on-behalf-of <YOUR_EOA_ADDRESS>
--lpsc <LPSC_CONTRACT_ADDRESS>
--liquidation-chain-selector <LIQUIDATION_CHAIN_SELECTOR>
--link <LINK_TOKEN_ADDRESS> # Optional

@andrejrakic what should be the repay token address ?


Custom component

Purpose of PR

Adding a custom component
The component is not yet wired up to Contentful, but all the graphql is in place

Did not mean to create this pull request


pull request for e2e test at 01/02/2017 06:45:16

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


Get error "TypeError: utf8 is not a function"

Triggering condition:
When Buffer.alloc and the Buffer.allocUnsafe function are polyfilled by other modules, and the version of node is less than v4.5.0.
Cause:
The Buffer.from method isn't realized until v4.5.0, but it is a function befor v4.5.0.
I think you maybe already know this and use two methods ,Buffer.alloc and Buffer.allocUnsafe, also added in v4.5.0 as auxiliary conditions to judge if the environment is modern.
Is it better to judge the version of node or try the from method to judge if it is really usable?

Reproduction:
Run the code below in node v4.4.7
var cfb = require('cfb');
var bf = require('buffer-from');
console.log(bf('test'));

This only happens when loading the cfb library before, which can only lead me to believe that they are modifying something global within the buffer 🤔

#7 should fix this...

@LinusU
I tried this fix, it works fine in this case.


Create user search bar

Should include a normal search bar to pass as a query to amazon.search() and a dropdown menu for the different search indexes

8431ae27ac791b1982b15e00759da13d137265a9


Feature request - additional arguments to write_object

It would be nice to be able to specify additional arguments for specific format in write_object. The desired state would be to be able to run something similar to
df.to_csv(file_name, index=False)

Similarly to how engine is solved I can imagine either expanding format_options or adding a new argument, e.g. format_kwargs and then have smth like
write_object(url, df, format="csv", format_kwargs={"index": False}

I have to admit that I don't like this :), including the already present engine etc. This is a wrong abstraction, where we are putting fsql in front of existing different incompatible layers, forcing it to adopt all their API idiosyncracies
what I'd like to do instead is to get a get_file_descriptor(url) which you would then use in any function you like (df.to_csv, df.to_parquet, etc); or, in case we'll ever support partitioned writing, to have write_partitioned_df(url_base, partition_columns, single_partition_writer: Callable[[fd, df], None])


fix: downlevel .d.ts files for compat with older TS versions

Summary
We shouldn't force consumers to update to TS 3.8. This will downlevel the d.ts files so it works down to TS 3.4.
Fixes #9703
Closes #9704

Test plan
I'll publish a canary and try to build with an older version of TS.
EDIT: Seems to work. This is with<EMAIL_ADDRESS>

Codecov Report

Merging #9705 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9705   +/-   ##
=======================================
  Coverage   64.94%   64.94%
=======================================
  Files         288      288
  Lines       12184    12184
  Branches     3020     3022    +2
=======================================
  Hits         7913     7913
  Misses       3634     3634
  Partials      637      637

Continue to review full report at Codecov.

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

the definition files aren't that large. But yes, it'll make the package bigger

@thymikee we could do something to replace the 3.8 definitions with 3.4 compatible ones?

If that doesn't degrade DX then I'm all in 👍

It'll degrade DX for consumers, but not for us (as we'll still work on the source). See caveats (semantics): https://github.com/sandersn/downlevel-dts/blob/master/README.md
No big ones though, so possibly worth it?

Worth it IMO

PR welcome 😀 Last caveat is that we have to ditch declarationMap, but that's broken anyways since we don't publish source files


No support for --option=value

A lot of commands use this syntax, not sure how standard it is, but I think supporting it would help prevent confusion.

Not sure if this matches your requirement? https://github.com/c9s/CLIFramework

ConsoleKit also supports this syntax. It is fairly common in specific categories of console applications, but it is much more common to see this syntax being used in my experience e.g. --key value


Feedback for "Developing Your First Application" - not correct rendered link

https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/bc8d5c0598774f87a54cb63cb6abecc6.html?locale=en-US&version=Cloud
The link to the CAP starter scenario in the Markdown file is correct but however, gets broken by the rendering of the Help Portal → (https://help.sap.com/docs/link-disclaimer?site=https%3A%2F%2Fdevelopers.sap.com%2Fmission.cp-starter-extensions-cap.html). Not sure who is responsible and should have a look on it. (The second link is working, for the third one we are still in contact with @Joysie, cause the linked tutorials are no longer on developers.sap.com.)

Best regards,
Iwona

Confirmed by @Joysie the rendering issue was resolved.


Optional argument for passing on existing files

optional argument on unzipItem in order to not throw an exception when a duplicate file is extracted. This happens when the zip contains __MACOSX entries
Fixes #
Changes proposed in this PR

Tests performed
Further info for the reviewer
Open Issues

Thank you for your pull request.
While existing files are probably the most likely use case for a "skip item" feature, there are some other scenarios where skipping certain items could be useful (e.g. just overwriting newer files or ignoring files that start with a certain pattern - .DS_Store for example).
So instead of adding an additional parameter, a more flexible approach would be to implement a delegation mechanism similar to FileManagerDelegate.
Before extracting an item, the unzipItemAt: method should send a fileManager:shouldUnzipItemAtURL: message to its delegate and only proceed if the delegate returns true.


Add flaky mark to network tests in CI

Add a flaky mark to tests with network mark to rerun if fails
Closes #918
Changelog-friendly one-liner: Add a flaky mark to network tests in CI
Contributor checklist

Provided the tests for the changes.
[x] Gave a clear one-line description in the PR (that the maintainers can add to CHANGELOG.md on release).
[x] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

@atugushev
Do you have any suggestions to test this?

@peymanslh

Do you have any suggestions to test this?

I think you can open a new demonstration PR based on the current and add with a separate commit the following tests:

wich fails constantly, to test that CI fails if reruns count has reached, for example:

@pytest.mark.network
def test_always_fails():
    assert False

wich fails randomly, to test that CI not fails if reruns count has not reached (may require to increase temporarily reruns), for example:

@pytest.mark.network
def test_flaky():
    import random
    assert random.choice([True, False])

Thanks you so much @peymanslh for this! No more randomly failed network tests anymore.

@peymanslh
Works like a charm 👍 https://travis-ci.org/jazzband/pip-tools/jobs/597224620