POOL-857 Cypress Integration tests

Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 12 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 375 bytes | 375.00 KiB/s, done.
Total 4 (delta 2), reused 0 (delta 0)
error: RPC failed; curl 52 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

Not sure what broke but I can't push to this branch.. Rather than dealing with that I opened a new PR #30

Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 12 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 375 bytes | 375.00 KiB/s, done.
Total 4 (delta 2), reused 0 (delta 0)
error: RPC failed; curl 52 LibreSSL SSL_read: SSL_ERROR_SYSCALL, errno 60
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
Everything up-to-date

Not sure what broke but I can't push to this branch.. Rather than dealing with that I opened a new PR #30


gitlabmr windows not work

Before submitting your bug report

[X] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS: Windows 11
- Continue: v0.9.212 (pre-release)
- IDE: VSCode
- Model: qwen2.5

Description
When use @gitlab-mr
Error getting context items from gitlab-mr
becase ; is not valid syntax on cmd.exe
Error: Command failed: cd c:\Users\dens\Project\cliphub; git branch --show-current
https://github.com/continuedev/continue/blob/70d9bc5d52f328d94867a7eb08a41ace3ad06c17/core/context/providers/GitLabMergeRequestContextProvider.ts#L68
To reproduce

Go to continue
Use @gitlab-mr

Log output
Error: Command failed: cd c:\Users\denis\Project\cliphub; git branch --show-current
���⥬� �� 㤠���� ���� 㪠����� ����.

	at genericNodeError (node:internal/errors:984:15)
	at wrappedFn (node:internal/errors:538:14)
	at ChildProcess.exithandler (node:child_process:423:12)
	at ChildProcess.emit (node:events:519:28)
	at maybeClose (node:internal/child_process:1105:16)
	at ChildProcess._handle.onexit (node:internal/child_process:305:5)

https://github.com/continuedev/continue/commit/3aee3ca08cf621d4b2b52b04d185110c79221a8a just fixed here

Will be in next release!


Private fields of a generated struct needs to be public

I was trying to make an adjustment to the rust-libp2p codebase which uses rust-protobuf, however got a few compiler errors, one of which is due to a private field of a public struct in a generated rpc_proto.rs file: [rustc] field `name` of struct `rpc_proto::TopicDescriptor` is private. The problem is that this field needs to be public in order to use it for the topic ID in rust-libp2p. FMI see https://github.com/libp2p/rust-libp2p/issues/473#issuecomment-421889795.

You should be able to use .get_name() instead of .name

Thanks, that indeed works!


Username recovery:  Swagger docs on Account Recovery REST APIs points to old document

In [1]  "swagger docs on Account Recovery REST APIs" link loads an old documentation. Please point to the latest documentation
[1] https://docs.wso2.com/display/IS540/Username+Recovery

Fixed in doc versions 5.4.0, 5.4.1 and 5.5.0


[Bug]: Consistent sizing of grid images when results are limited

Contact Details
No response
What happened?
When we have <1 normal row of images they get huge

Version
current
What browser did you experience the the problem on?
No response
What operating system are you using?
No response
Relevant log output
No response

This is fixed with some of the newer changes to the grid.
Screenshot:


Release 1.6.6

Hi!
First of all, thanks a lot for your project!
I see that last release was done in January and there is a plenty of commits since then. Is there a blocker the prevents next version to be released?

for some reason the go get -u github.com/swaggo/swag/cmd/swag pulling the 1.6.6... but this version are breaking the swag init....
looking right now.. this 1.6.6 version are not released...
anybody with this same problem???
1.6.6. - "cannot parse source files"
1.6.5. - it's ok.

me too, go get github.com/swaggo/swag/cmd/swag downloading "github.com/swaggo/swag v1.6.6", but short command options almost undefined, such as -g:
swag init -g cmd/main.go
Incorrect Usage: flag provided but not defined: -g

NAME:
swag init - Create docs.go

USAGE:
swag init [command options] [arguments...]

OPTIONS:
   --generalInfo value       Go file path in which 'swagger general API Info' is written (default: "main.go")
   --dir value               Directory you want to parse (default: "./")
   --exclude value           exclude directories and files when searching, comma separated
   --propertyStrategy value  Property Naming Strategy like snakecase,camelcase,pascalcase (default: "camelcase")
   --output value            Output directory for all the generated files(swagger.json, swagger.yaml and doc.go) (default: "./docs")
   --parseVendor             Parse go files in 'vendor' folder, disabled by default (default: false)
   --parseDependency         Parse go files in outside dependency folder, disabled by default (default: false)
   --markdownFiles value     Parse folder containing markdown files to use as description, disabled by default
   --generatedTime           Generate timestamp at the top of docs.go, true by default (default: false)
   --help, -h                show help (default: false)

2020/05/21 09:54:52 flag provided but not defined: -g

but v1.6.5 is ok and has the "-" short command options:
swag init --help
NAME:
   swag init - Create docs.go

USAGE:
   swag init [command options] [arguments...]

OPTIONS:
   --generalInfo value, -g value       Go file path in which 'swagger general API Info' is written (default: "main.go")
   --dir value, -d value               Directory you want to parse (default: "./")
   --propertyStrategy value, -p value  Property Naming Strategy like snakecase,camelcase,pascalcase (default: "camelcase")
   --output value, -o value            Output directory for all the generated files(swagger.json, swagger.yaml and doc.go) (default: "./docs")
   --parseVendor                       Parse go files in 'vendor' folder, disabled by default
   --parseDependency                   Parse go files in outside dependency folder, disabled by default
   --markdownFiles value, --md value   Parse folder containing markdown files to use as description, disabled by default
   --generatedTime                     Generate timestamp at the top of docs.go, true by default

I've spotted this as well. Should it be filed as a separate issue?

I did a quick check, regression is due to 86e76b764018c8e0dc882f0756e665dafe42b662

we just released v1.6.6, please raise a new issue if any.

I raised at https://github.com/swaggo/swag/issues/711

@can3p thank you for point out the root cause.

this release seems to still be causing issues for me https://github.com/swaggo/swag/issues/712#issuecomment-635627539


TypeScript typings issue

Hi!
First of all thank you for creating this hook, it really adds a lot of value!
The TypeScript types appear to have some issues. The x and y coordinates should use number instead of the upper-case Number to allow for arithmetic operations.
I can create a pull request if you'd like.
Best regards,
Peter

@peterjuras Thanks, sure, go for it, I'll be glad to merge it.


Add option UnspecifiedDateTimeKindBehavior.IsUnspecified

Looking at issue #129. There are some cases where an unspecified datetime is really that, deliberately unspecified, and we expect it to be correctly serialized to Iso8601 without the zone specified.
Unfortunately this is not possible as ALL datetimes are converted to UTC and serialized as such.
Please consider adding UnspecifiedDateTimeKindBehavior.IsUnspecified.

I agree with AxelMarquez, that would be very useful. Please consider adding this option.


File.lines() terminates on empty lines

I compiled and ran test/pony/files/files.pony, and it surprised me that when I did this:
./files test/pony/files/files.pony
. . . I only got the first line (use "files") printed. Now I see the reason in class FileLines in packages/files/file.pony:
fun ref has_next(): Bool => line.size() > 0
I find this behaviour counterintuitive, and not very useful.

Thanks! This bug was accidentally introduced recently. Fixed now.


[WIP] Add wasm32-unknown-unknown support through stdweb

[ ] stdweb APIs (there a couple web APIs used in the emscripten backend that aren't yet available)

[x] DPI
[ ] Pointer lock
[ ] Main loop

[ ] Interrupt the main loop when necessary
[ ] Set the main loop (stdweb callbacks must be 'static, but winit callbacks have no such restrictions

[ ] Touch events
[ ] Fullscreen
[ ] Show / hide mouse

[ ] Delete callbacks when the window is dropped
[ ] Tested on all platforms changed
[ ] Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
[ ] Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
[ ] Created an example program if it would help users understand this functionality

Comment out the main loop until a good solution to the 'static problem

Changing the closure to be 'static is actually included in the plans formulated in #459, which is certainly recommended reading.

Followed the recommendation and did some reading, very interesting!
Funnily enough, yielding control of the main loop and only getting called back from the browser is what I've done with quicksilver. If winit adopts this model it would make my life much easier! 😄
Should I delay work on this backend until EventLoop 2.0? And can I help with EventLoop 2.0?

Should I delay work on this backend until EventLoop 2.0?

That's what I'd recommend, since having people waiting for me is the only way I'm going to be able to motivate myself to implement EventLoop 2.0.

And can I help with EventLoop 2.0?

I'm not familiar with Emscripten at all, and the discussion in #459 makes it clear that there are important details, so if you're able to migrate that backend it would be a big time save.
As it stands, @Osspial (who claimed the Windows backend for this rewrite) hasn't been around, and @vberger (who does all the Wayland stuff) has been busy. So, by default I'm the one handling all of the backends... I actually don't think that's too much of a problem, but it's undeniably going to be time consuming.
I've also been working on gamepad support, though what order all of this will happen in is anyone's guess.

I'm only familiar with emscripten inasmuch as I know the web APIs it interfaces with, but I'll be happy to pitch in and try to learn.
For the gamepad stuff, are you going to be integrating / working off of the gilrs crate? I've been meaning to look into getting Mac and web support started for it, but it's slipped my mind.

Can I come with a suggestion since you're working on this: Please add the locations for clicks/touch events instead of letting the user to store state to manage them.
Right now I gotta do
                  ElementState::Pressed => {
                      .....
                    }
                    ElementState::Released => {
                     .........
                    }

Read in the last state (values) from WindowEvent::CursorMoved
It's not the best design, and afaik SDL2 doesn't have that way. It actually gives the locations.

Closed in favor of #797


Optional parameters aren't really optional for create

--end-ip-address and --start-ip-address are listed as optional, but I've never seen it work without them.

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

ID: a0ed8c3b-f42d-2421-a563-d09ec7b67ac0
Version Independent ID: bcdaeb1b-e343-2336-d394-e32f8d867ab2
Content: az sql server firewall-rule
Content Source: latest/docs-ref-autogen/sql/server/firewall-rule.yml
Service: sql-database
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to service team


Change yarn to npm in TravisCI config

@ddavidebor Would it be possible to chat on gitter or some other platform about this?

Yes but I do not think I am the most competent person in the matter here.
I mostly followed CI and app building, I have a limited understanding of
jupyterlab peculiarities regarding all the node modules behind the app.
Il gio 12 apr 2018, 18:46 Declan Kelly<EMAIL_ADDRESS>ha
scritto:

@ddavidebor https://github.com/ddavidebor Would it be possible to chat
on gitter or some other platform about this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jupyterlab/jupyterlab_app/pull/158#issuecomment-380871181,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIot_g1uFFnXqkVTngH80HyAvVwnWF9tks5tn4THgaJpZM4TFtz1
.

Closing in favour of new PR.


Improve the way we deliver Examples in command line #15869

Just fixing the order of the Examples block. I don't know if this what you guys think should be the right way. Comments in how to improve it.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:lordzero0000/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Thanks! I think I'm good with moving the examples section down (after the "reference" sections).
However, it looks like your PR changes the indenting of various lines, causing the rendered output of the Markdown to be messed up (code blocks no longer being code blocks, lists no longer being lists etc.). Markdown heavily relies on indentation for formatting, so you need to be very careful there.
To verify your PR is working correctly, you can test the rendered output of the docs, by running make docs from the root of your repository (see the docs README)

@lordzero0000 I'm going to close this PR for now, because it's currently not mergable. Please let us know if you're still interested in working on this, thanks!


fix typos

fix typos

Summary by CodeRabbit

Documentation

Corrected typos and improved consistency in code examples for better clarity and readability.

Hi @omahs, thanks for your contribution!


Add Pico Display Pack 2.8 and fix SPI for st7789 on Pico2

This adds libraries/pico_display_28 along with a demo that displays the FPS in examples/pico_display_28
Also updated drivers/st7789 as per #985 / #1005
Full repo build impossible owing to hardware/rtc.h not existing for Pico2 when it hits breakout_encoder_wheel (about to raise issue) so just built and tested pico_display_28

Why do we need a specifix example for 2.8? I thought is was exactly the same as the 2 but physically larger.

Why do we need a specific example for 2.8? I thought is was exactly the same as the 2 but physically larger.

It is't a carbon copy. It changes the text from "Hello World" to one that displays the Frames Per Second which is calculated on every update so has a benefit not present in other demos (as none of them do FPS)

The baud rate is dependant on the device in modified driver/st7789.hpp

Yeah I saw that I was just wondering if the faster baud rate also works on Pico 1.

Yeah I saw that I was just wondering if the faster baud rate also works on Pico 1.

I most sincerely doubt it (might give it a go tho)
The baud rate is tied to the system clock and those values are 1/2 device clock frequency (Pico 1 should be 66.5 for 1/2 freq - might be worth a try) although the docs say 16us apparently

Sorry, it's been a busy time and I haven't got 'round to testing this yet 😬
Nonetheless, this is appreciated thank you!

In fact you really need that header defining the RGB pins cause they were changed for that display.

Thank you!


Installation of Nunaliit

I am unable to finish installing Nunaliit (on Mac OSX El Captian).  I have downloaded the most recent tar.gz file from Maven, and have downloaded and installed all of the prerequisite programs (CouchDB, ImageMagick, etc.).  I have uncompressed the Nunaliit tar.gz (2.2.5).  I do not know how to proceed from this point, and the documentation on the wiki (under "Installing Nunaliit") is unclear to me.  I am a novice with command-line programs, and would appreciate any assistance in completing the installation.

Were you able to complete the steps mentioned here?
https://github.com/GCRC/nunaliit/wiki/Installation#installing-nunaliit

I was able to complete everything except for the section 'Installing Nunaliit.'  I tried entering the commands in the text box (below) in my terminal window in the same way I installed some of the prerequisite programs, and it did not recognize the commands.
cd /usr/local
tar -zxvf nunaliit2-couch-sdk-X.Y-nunaliit.tar.gz
chmod -R o+r,o+x nunaliit2-couch-sdk-X.Y-nunaliit
export PATH=$PATH:/usr/local/nunaliit2-couch-sdk-X.Y-nunaliit/bin
I also tried opening the nunaliit file within the bin folder of the uncompressed Nunaliit package that I downloaded, and it gave me an error (see below)
2016-01-26 11:26:15,620[ERROR]: Error: No command provided. Try 'help'.
java.lang.Exception: No command provided. Try 'help'.
at ca.carleton.gcrc.couch.command.Main.execute(Main.java:119)
at ca.carleton.gcrc.couch.command.Main.main(Main.java:57)
Error: No command provided. Try 'help'.
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.
[Process completed]
As I said, I am a novice using this type of program, so I may just be missing a step that those who are more experienced would have recognized in the instructions provided, but I am unable how to proceed.  Any assistance would be greatly appreciated

Hi,
I am not a developer, but have been using Nunaliit for some time, so may be able to help.
If I recall, the nunaliit command requires an argument.  for example:
/usr/local/nunaliit2-couch-sdk-X.Y-nunaliit/bin/nunaliit help
OR simply
nunaliit help (assuming that you PATH statement is working)
As a start, you can try this and see if you are presented with more meaningful output.  I will look for follow up messages.
On Jan 26, 2016, at 11:28 AM, wanderer33third<EMAIL_ADDRESS>wrote:

I was able to complete everything except for the section 'Installing Nunaliit.' I tried entering the commands in the text box (below) in my terminal window in the same way I installed some of the prerequisite programs, and it did not recognize the commands.
cd /usr/local
tar -zxvf nunaliit2-couch-sdk-X.Y-nunaliit.tar.gz
chmod -R o+r,o+x nunaliit2-couch-sdk-X.Y-nunaliit
export PATH=$PATH:/usr/local/nunaliit2-couch-sdk-X.Y-nunaliit/bin
I also tried opening the nunaliit file within the bin folder of the uncompressed Nunaliit package that I downloaded, and it gave me an error (see below)
2016-01-26 11:26:15,620[ERROR]: Error: No command provided. Try 'help'.
java.lang.Exception: No command provided. Try 'help'.
at ca.carleton.gcrc.couch.command.Main.execute(Main.java:119)
at ca.carleton.gcrc.couch.command.Main.main(Main.java:57)
Error: No command provided. Try 'help'.
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
Deleting expired sessions...none found.
[Process completed]
As I said, I am a novice using this type of program, so I may just be missing a step that those who are more experienced would have recognized in the instructions provided, but I am unable how to proceed. Any assistance would be greatly appreciated
—
Reply to this email directly or view it on GitHub.

Since many of the error messages I was receiving were some form of "file or directory not found", the comment 'assuming that your PATH statement is working' made me think there was something I was missing about using the command line.
I ended up finding this website - http://coolestguidesontheplanet.com/add-shell-path-osx/ - which helped me figure out how to change my PATH (like I said, huge novice).
My problem was that I was not changing the 'usr/local' after cd to my actual PATH, and had not changed the file names (specifically the 'X.Y' placeholder for the file version) to the filename that I had downloaded.  Once I realized how these parts needed to be changed (through trial and error and how-to websites) I was able to finish the installation.  Or at least I have gotten to the point where I am able to move into the 'Using Nunaliit' section of the Atlas Builder Documentation where I can start creating a test atlas.
Thank you very much for everyone's assistance


Sender & Subject on separate lines

Expected behavior
Sender and Subject to be on separate lines when previewed is set to 0 and show contact pictures is off.
Actual behavior
I did not see a closed or open issue for Dave's original question in the google mailing list, and I also would like to see this addressed.
https://groups.google.com/forum/#!searchin/k-9-mail/sender$20and$20subject|sort:date/k-9-mail/rNYa5Or-LKw/GmbxaoG1AwAJ
When we set preview lines to 0, and turn off "Show Contact Pictures". The e-mails in the folders crams the sender & subject lines into a single line. This is an issue as the sender and subject lines are then limited to about 8 characters each in portrait mode.
Steps to reproduce

set preview lines to 0
turn off "Show Contact Pictures"
refresh the account

Environment
K-9 Mail version: 5.208 (Google Play)

So here's the fields behind the scenes with everything visible.

When you select a preview line we seem to just put the sender inside the preview and hide the Sender field.

Part of me thinks the bad bit of behaviour is actually merging the sender and the preview.
Part of me thinks the component needs better options
Part of me hates having lots of options

Setting preview lines to 0 has historically enabled single line mode. I believe it was added because some people like(d) to optimize for number of messages on the screen instead of touch usability. But that was during a time where phones had DPADs and/or hardware keyboards. It's probably time to get rid of the single line mode.

I actually appreciate the single line mode.  As others have expressed in the mailing list, I do not need the preview lines but just the sender and subject.  As for the narrow sender and subject columns in portrait mode reported in this Issue, perhaps try landscape mode.
Anyhow, my true comment concerns a setting: Global -> Display -> Correspondent above subject.  Assuming Preview lines is 0, hence single line mode, the above setting lays out subject in the first column then sender in the next column, which to me seems opposite.
Is this a separate issue?  Can you point me to the relevant code?  I can try updating it and creating a pull request.  Thanks for your attention.

This is fixed in K-9 Mail 5.7xx.


Load test stuck in initialization

Brief summary
I have a ConfigMap and K6 CRD which I am applying to a local cluster, via a helm chart, in order to kickstart a load test and it is running as expected, no problems there. However, when applying those same helm charts to a staging cluster on the cloud the tests never get run and the CRD seemingly get stuck in a scheduled state.
k6-operator version or image
ghcr.io/grafana/operator:latest
K6 YAML
apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: ingestion-load-shedder-2022-09-2
spec:
  parallelism: 10
  script:
    configMap:
      name: ingestion-load-shedder-configmap
      file: script
  separate: false
  runner:
    metadata:
      labels:
        type: k6-operator-runner
        run-identifier: ingestion-load-shedder-2022-09-2
    resources:
      limits:
        cpu: 400m
        memory: 500Mi
      requests:
        cpu: 400m
        memory: 500Mi
    env:
      - name: API_KEY
        value: ...
  starter:
    metadata:
      labels:
        type: k6-operator-starter
        run-identifier: ingestion-load-shedder-2022-09-2

Other environment details (if applicable)
No response
Steps to reproduce the problem
I apply a configMap and the K6 CRD using helm charts:
ConfigMap
apiVersion: v1
kind: ConfigMap
metadata:
  name: ingestion-load-shedder-configmap
  labels:
    app.kubernetes.io/name: load-testing
    helm.sh/chart: load-testing-0.3.0
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/instance: load-testing
data:
  script: |-

    import http from 'k6/http';
    import { check } from 'k6';

    export const options = {
      scenarios: {
        constant: {
          executor: 'constant-arrival-rate',
          rate: 2500,
          timeUnit: '1m',
          duration: '5m',
          preAllocatedVUs: 1000,
        },
    }
    ... rest of k6 script

K6 CRD
apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: ingestion-load-shedder-2022-09-2
spec:
  parallelism: 10
  script:
    configMap:
      name: ingestion-load-shedder-configmap
      file: script
  separate: false
  runner:
    metadata:
      labels:
        type: k6-operator-runner
        run-identifier: ingestion-load-shedder-2022-09-2
    resources:
      limits:
        cpu: 400m
        memory: 500Mi
      requests:
        cpu: 400m
        memory: 500Mi
    env:
      - name: API_KEY
        value: ...
  starter:
    metadata:
      labels:
        type: k6-operator-starter
        run-identifier: ingestion-load-shedder-2022-09-2

Expected behaviour
When running this locally against a local test cluster the test runs successfully which is what I expect in staging cluster. State of cluster after tests are complete
> kubectl get configmap
NAME                               DATA   AGE
ingestion-load-shedder-configmap   1      146m

> kubectl get k6
NAME                               AGE
ingestion-load-shedder-2022-09-2   146m

> kubectl get pods
NAME                                                         READY   STATUS      RESTARTS   AGE
k6-operator-1664374051-controller-manager-8664ddfc47-56nv8   2/2     Running     0          6h58m
ingestion-load-shedder-2022-09-2-initializer-6tgxq           0/1     Completed   0          145m
ingestion-load-shedder-2022-09-2-starter-2qtln               0/1     Completed   0          144m
ingestion-load-shedder-2022-09-2-1-fh4nj                     0/1     Completed   0          145m
ingestion-load-shedder-2022-09-2-2-lqd66                     0/1     Completed   0          145m

> kubectl logs k6-operator-1664374051-controller-manager-8664ddfc47-56nv8
INFO	controllers.K6	Reconcile(); stage = 	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Initialize test	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to initialization	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Initializer job is ready to start with image `ghcr.io/grafana/operator:latest-runner` and command `[sh -c k6 archive --log-output=none /test/script -O ./script.archived.tar  && k6 inspect --execution-requirements --log-output=none ./script.archived.tar]`	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Waiting for initializing pod to finish	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	k6 inspect: {External:{Loadimpact:{Name: ProjectID:0}} TotalDuration:1m30s MaxVUs:1000 Thresholds:map[]}	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to initialized	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = initialized	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Creating test jobs	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Launching k6 test #1	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Runner job is ready to start with image `ghcr.io/grafana/operator:latest-runner` and command `[k6 run --quiet --execution-segment=0:1/2 --execution-segment-sequence=0,1/2,1 /test/script --address=<IP_ADDRESS>:6565 --paused --tag instance_id=1 --tag job_name=ingestion-load-shedder-2022-09-2-1]`	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Launching k6 test #2	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Runner job is ready to start with image `ghcr.io/grafana/operator:latest-runner` and command `[k6 run --quiet --execution-segment=1/2:1 --execution-segment-sequence=0,1/2,1 /test/script --address=<IP_ADDRESS>:6565 --paused --tag instance_id=2 --tag job_name=ingestion-load-shedder-2022-09-2-2]`	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to created	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = created	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Waiting for pods to get ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	0/2 pods ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 pods ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	ingestion-load-shedder-2022-09-2-service-1 service is not ready, aborting	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 pods ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	ingestion-load-shedder-2022-09-2-service-2 service is not ready, aborting	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 pods ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to started	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = created	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Waiting for pods to get ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 pods ready	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Reconcile(); stage = started	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Waiting for pods to finish	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	0/2 jobs complete	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 jobs complete	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to finished	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = started	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Waiting for pods to finish	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	2/2 jobs complete	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Changing stage of K6 status to finished	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
INFO	controllers.K6	Reconcile(); stage = finished	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}

> kubectl describe k6/ingestion-load-shedder-2022-09-2
Name:         ingestion-load-shedder-2022-09-1
Namespace:    k6-operator
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: load-testing-1664390454
              meta.helm.sh/release-namespace: k6-operator
API Version:  k6.io/v1alpha1
Kind:         K6
Metadata:
  Creation Timestamp:  2022-09-28T18:40:56Z
  Generation:          1
  Managed Fields:
    API Version:  k6.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      ...
    Manager:      helm
    Operation:    Update
    Time:         2022-09-28T18:40:56Z
    API Version:  k6.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      ...
    Manager:         manager
    Operation:       Update
    Subresource:     status
    Time:            2022-09-28T18:40:56Z
  Resource Version:  106832
  UID:               2d57e55b-069b-4753-a6c8-4ce2ea9152ae
Spec:
  Parallelism:  2
  Runner:
    Env:
      Name:   API_KEY
      Value:  ...
    Metadata:
      Labels:
        Run - Identifier:  ingestion-load-shedder-2022-09-1
        Type:              k6-operator-runner
    Resources:
      Limits:
        Cpu:     400m
        Memory:  500Mi
      Requests:
        Cpu:     400m
        Memory:  500Mi
  Script:
    Config Map:
      File:  script
      Name:  ingestion-load-shedder-configmap
  Separate:  false
  Starter:
    Metadata:
      Labels:
        Run - Identifier:  ingestion-load-shedder-2022-09-1
        Type:              k6-operator-starter
Status:
  Stage:  finished
Events:   <none>

Tests ran successfully. Status.Stage for the K6 CRD is finished
Actual behaviour
Initializer get spawned and crashes, no subsequent workers or starters are spawned. State of cluster at this point:
> kubectl get k6
NAME                               AGE
ingestion-load-shedder-2022-09-3   50m

> kubectl get configmap
NAME                               DATA   AGE
fcdfce80.io                        0      36d
ingestion-load-shedder-configmap   1      2d2h
kube-root-ca.crt                   1      36d

> kubectl get pods
NAME                                                 READY   STATUS      RESTARTS   AGE
ingestion-load-shedder-2022-09-3-initializer-dxlsn   0/1     Completed   0          51m
k6-operator-controller-manager-6cdcf8cd9c-7w4xp      2/2     Running     6          43h

> kubectl logs k6-operator-controller-manager-6cdcf8cd9c-7w4xp -c manager
request.go:621] Throttling request took 1.034699401s, request: GET:https://<IP_ADDRESS>:443/apis/extensions/v1beta1?timeout=32s
INFO	controller-runtime.metrics	metrics server is starting to listen	{"addr": "<IP_ADDRESS>:8080"}
INFO	setup	starting manager
leaderelection.go:242] attempting to acquire leader lease  k6-operator/fcdfce80.io...
INFO	controller-runtime.manager	starting metrics server	{"path": "/metrics"}
leaderelection.go:252] successfully acquired lease k6-operator/fcdfce80.io
DEBUG	controller-runtime.manager.events	Normal	{"object": {"kind":"ConfigMap","namespace":"k6-operator","name":"fcdfce80.io","uid":"d82c8d17-43bf-4cdd-9638-5ca2483cbeee","apiVersion":"v1","resourceVersion":"1464687926"}, "reason": "LeaderElection", "message": "k6-operator-controller-manager-6cdcf8cd9c-7w4xp_0aacf971-ec10-4960-8253-540716101587 became leader"}
INFO	controller	Starting EventSource	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "source": "kind source: /, Kind="}
INFO	controller	Starting EventSource	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "source": "kind source: /, Kind="}
INFO	controller	Starting Controller	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6"}
INFO	controller	Starting workers	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "worker count": 1}
INFO	controllers.K6	Reconcile(); stage = initialization	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-3", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = initialization	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-3", "namespace": "k6-operator"}

However I noticed that the manager container had restarted quite a few times so looked at logs of previously crashed pod
> kubectl logs k6-operator-controller-manager-6cdcf8cd9c-7w4xp -c manager --previous
INFO	controllers.K6	Reconcile(); stage = initialization	{"k6": "k6-operator/ingestion-load-shedder-2022-09-2"}
DEBUG	controller	Successfully Reconciled	{"reconcilerGroup": "k6.io", "reconcilerKind": "K6", "controller": "k6", "name": "ingestion-load-shedder-2022-09-2", "namespace": "k6-operator"}
INFO	controllers.K6	Reconcile(); stage = 	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}
INFO	controllers.K6	Initialize test	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}
INFO	controllers.K6	Changing stage of K6 status to initialization	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}
INFO	controllers.K6	Initializer job is ready to start with image `ghcr.io/grafana/operator:latest-runner` and command `[sh -c k6 archive --log-output=none /test/script -O ./script.archived.tar  && k6 inspect --execution-requirements --log-output=none ./script.archived.tar]`	{"k6": "k6-operator/ingestion-load-shedder-2022-09-3"}

So it seems to me that that last line is causing the pod to crash for some reason. The same did not happen locally. When inspecting the K6 custom resource I get
> kubectl describe k6/ingestion-load-shedder-2022-09-3
Name:         ingestion-load-shedder-2022-09-3
Namespace:    k6-operator
Labels:       app.kubernetes.io/managed-by=Helm
Annotations:  meta.helm.sh/release-name: load-testing
              meta.helm.sh/release-namespace: k6-operator
API Version:  k6.io/v1alpha1
Kind:         K6
Metadata:
  Creation Timestamp:  2022-09-28T20:26:08Z
  Generation:          1
  Managed Fields:
    API Version:  k6.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      ...
    Manager:      helm
    Operation:    Update
    Time:         2022-09-28T20:26:08Z
    API Version:  k6.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      ...
    Manager:         manager
    Operation:       Update
    Time:            2022-09-28T20:26:08Z
  Resource Version:<PHONE_NUMBER>
  UID:               f4c6564a-3caa-46a2-8ff3-4da6876ce9f0
Spec:
  Parallelism:  2
  Runner:
    Env:
      Name:   API_KEY
      Value:  ...
    Metadata:
      Labels:
        Run - Identifier:  ingestion-load-shedder-2022-09-3
        Type:              k6-operator-runner
    Resources:
      Limits:
        Cpu:     400m
        Memory:  500Mi
      Requests:
        Cpu:     400m
        Memory:  500Mi
  Script:
    Config Map:
      File:  script
      Name:  ingestion-load-shedder-configmap
  Separate:  false
  Starter:
    Metadata:
      Labels:
        Run - Identifier:  ingestion-load-shedder-2022-09-3
        Type:              k6-operator-starter
Status:
  Stage:  initialization
Events:   <none>

Of note, the Status.Stage is stuck in an initialization stage. Any ideas on what might be happening and/or how to debug this further?

I think I facing the same problem here :(

I was able to resolve this. The k6-operator-controller-manager had run out of memory
> kubectl get pod k6-operator-controller-manager-6cdcf8cd9c-7w4xp --output=yaml
...
- containerID: containerd://7832b6bd26232b5dbfc6114fcff6e881e20b7ee7aea22e3d8383a1eb159a218a
    image: ghcr.io/grafana/operator:latest
    imageID: ghcr.io/grafana/operator@sha256:97fef2753dcef151bd5b29864074c3dffadd54837bc33b995cc6ea44779f9af0
    lastState:
      terminated:
        containerID: containerd://2166944558bea0c699c6e0814f0946e1b4253b44cb3f521ac9efd5ded6d5c6ab
        exitCode: 137
        finishedAt: "2022-09-28T20:26:11Z"
        reason: OOMKilled
        startedAt: "2022-09-28T19:32:52Z"
    name: manager
    ready: true
    restartCount: 6
    started: true
    state:
      running:
        startedAt: "2022-09-28T20:26:13Z"
...

Increasing the memory of the manager resolved my issues


Unreal crashes when i press "play level"

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description
ive done all the steps successfully including building in visual studio and loading the project up in unreal engine.
But when i press play on any of the levels provided, ureal crashes straight away.
Steps to Reproduce
1.Unzip
2.Genereate visual studio files
3.Rebuild on ZEDSamples in viual studio
4.Launch zedsamples.uproject - (unreal 5.1.1)
5. Press play button inside unreal engine.
...
Expected Result
Level plays, camera loads and starts tracking.
Actual Result
unreal crashes - Crash report below.
LoginId:abf2da2840833c5a30f902bba2297cd6
EpicAccountId:fc9f86e4226e4ac4adea77b7d5badba4
Unhandled Exception: 0xc06d007e
KERNELBASE
UnrealEditor_Stereolabs!__delayLoadHelper2() [D:\a_work\1\s\src\vctools\delayimp\delayhlp.cpp:312]
UnrealEditor_Stereolabs!_tailMerge_sl_zed_c_dll()
UnrealEditor_Stereolabs!USlCameraProxy::OpenCamera() [C:\Work\zed-UE5-main\Plugins\Stereolabs\Source\Stereolabs\Private\Core\StereolabsCameraProxy.cpp:223]
UnrealEditor_ZED!AZEDPlayerController::ZedReady() [C:\Work\zed-UE5-main\Plugins\Stereolabs\Source\ZED\Private\Core\ZEDPlayerController.cpp:432]
UnrealEditor_ZED!AZEDPlayerController::Internal_OpenZedCamera() [C:\Work\zed-UE5-main\Plugins\Stereolabs\Source\ZED\Private\Core\ZEDPlayerController.cpp:423]
UnrealEditor_ZED!TBaseUObjectMethodDelegateInstance<0,AZEDPlayerController,void __cdecl(void),FDefaultDelegateUserPolicy>::Execute() [C:\Program Files\Epic Games\UE_5.1\Engine\Source\Runtime\Core\Public\Delegates\DelegateInstancesImpl.h:601]
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_Engine
UnrealEditor_UnrealEd
UnrealEditor_UnrealEd
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
UnrealEditor
kernel32
ntdll
ZED Camera model
ZED2i
Environment
Processor	13th Gen Intel(R) Core(TM) i9-13900K   3.00 GHz
Installed RAM	64.0 GB (63.7 GB usable)
System type	64-bit operating system, x64-based processor
GFX             Nvidia 4090 (desktop)

Anything else?
Ive run the Zed diagnostics several times with all green ticks.

I have the same issue with the ZED-M. I have a RTX 3080, but everything else (even CPU) matches this issue. I'm using VS2022, but left the compiler at v142. ZED SDK version is 4.0.7 with CUDA 12.1. My camera works fine in any other app which uses it.

@Instant-Sage @BanTheRewind
Please try using Unreal 5.2.
The repo was just updated to reflect this compatibility issue, sorry for the inconvenience.

Hi, @SLJLMacarit , thank you for the reply and update.
Ive downloaded latest repo, Built it with visual studio 2019. and now i get the following error when i press play inside unreal:
GPU Crashed or D3D Device Removed.
Use -d3ddebug to enable the D3D debug device.
Check log for GPU state information.
Unreal crash report:
LoginId:abf2da2840833c5a30f902bba2297cd6
EpicAccountId:fc9f86e4226e4ac4adea77b7d5badba4
Fatal error: [File:D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 873] CurrentQueue.Fence.D3DFence->GetCompletedValue() failed at D:\build++UE5\Sync\Engine\Source\Runtime\D3D12RHI\Private\D3D12Submission.cpp:939 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_REMOVED
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_D3D12RHI
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

@Instant-Sage That's a Dx12 issue, please switch to Dx11 for the time being.
I'm actively working on the release notes and troubleshooting mentioning this, and on the temporary fix. There will be a release soon with all this mentioned.
Going back on my word for 5.2 (didn't think you'd be this fast haha), we'll migrate to 5.3 soon, for the sake of not downloading UE5 every couple of days, please try using 5.3, it should work with some slight changes. You can find them on the ue5.3 branch.

Hi, thank you or the quick comment. I was just coming back to say that i found this thread - https://community.stereolabs.com/t/crash-when-using-unreal-engine-zedsamples/2651/8
And changed the project setting from DX12 to DX11 and its now working fine. - Ill try the 5.3 and let you know how that works.
Thank you.

On the ue5.3 branch, I needed to add "HeadMountedDisplay" to PrivateDependencyModuleNames in "zed-UE5\Plugins\Stereolabs\Source\Stereolabs\Stereolabs.Build.cs" to fix a missing header error. Now I'm puppeting a robot with my ZED-M in UE 5.3.1. Thank you!

Hi @SLJLMacarit. I cant generate visual studio files for the 5.3 version as i get this error below:
Generating VisualStudio2019 project files:
Discovering modules, targets and source code for project...
Visual Studio 2019 does not support .NET 6.0 C# projects, these projects will not be added to the generated solution.
Please generate the Visual Studio 2022 solution if .NET 6.0 C# project support is required.
Microsoft platform targets must be compiled with Visual Studio 2022 17.4 (MSVC 14.34.x) or later for the installed engine. Please update Visual Studio 2022 and ensure no configuration is forcing WindowsTargetRules.Compiler to VisualStudio2019. The current compiler version was detected as: 14.29.30152
When i switch to unreal v 5.2 - it succesfully geerates visual studio files which i can then build.

Ok so the project file kept trying to generate files with VS2019 - even though i had it uninstalled.
The fix that worked for me is to add this line:

VisualStudio2022

Into the Buildconfiguration.xml file which lives here:
C:\Users\Admin\AppData\Roaming\Unreal Engine\UnrealBuildTool


lock/unlock all button

make it easier to lock / unlock all of the hashpairs

Rejecting this, I don't think it's useful enough to bother and it would clutter the interface further.


Wrongly recognized Django url pattern

Below description is copied from my stackoverflow post.
Intorudction
I've implemented rest API using django-rest-framework.
I've decided to implement batch operations, where ids were neccessary, in two ways:

By sending ids in url, separated with '/':
url(r'^tubes/(?P<ids>(([0-9]+/)+))$', manage_tubes, name='manage_tubes'),

Example request:

http://<IP_ADDRESS>:8000/tubes/0/1/10/

By sending ids in POST body as a json array:
url(r'^tubes/(?P<operation>(create|delete|get))/$', manage_tubes_json, name='manage_tubes_json'),

Example request:

http://<IP_ADDRESS>:8000/tubes/get

with following body:

[0, 1, 10]

This works well, but I've problem with django-rest-swagger. Actually with swagger UI.
Problem
Swagger didn't recognized my url patterns very well...
It sees urls as follows:

/tubes/{ids}+))

(redundant '+))' )

POST /tubes/{operation})/

(redundant ')' )

Is my urls.py file incorrect or maybe I should define url paramters somehow?

Yes, same as this. For me the pattern is -
^(?P<session>[\d\-]{5})/(?P<entity>(cluster|block|district|assembly|parliament|pincode))/$

and the UI shows -
/api/{session}/{entity})/

This is breaking the API doc.

I don't think this is something that can done, and I suggest considering following a more restful pattern, specifically, using HTTP methods to capture "operations" rather than the URI.
Something like:
url(r'^tubes/(?P<operation>(create|delete|get))
Should be
GET /tubes (list)
DELETE /tubes/
POST /tubes (create)
GET /tubes/ (individual object)
As for the second example, something more "restful" would mean using a query parameter or filter for the entities, or, making the routes based on the resource.
i.e. /session?entity=cluster
or /cluster/session


[HOTFIX] Add logins authentication for hdfs file interpreter

What is this PR for?
When attempting to login to a webhdfs file system with credentials as in:
https://<username>:<password>@<host>:<port>
We get a ava.io.IOException: Server returned HTTP response code: 401 for URL: ....
This has to do with how Java authorizes a URL.  A simple fix is applied to handle this.
What type of PR is it?
Improvement
Todos

[x] - Apply Patch

What is the Jira issue?
No JIRA issue, this was required functionality for a use case. I expect others will require this too.
How should this be tested?
Login to a webhdfs that requires authentication.  It works.
Screenshots (if appropriate)
Questions:

Does the licenses files need update?
No
Is there breaking changes for older versions?
No
Does this needs documentation?
I don't think so- the intuitive way to pass username/login is https://user:password@host.  This makes that work.

The codes look simple. @cloverhearts Can you help me review it?

I have a question.
Webhdfs that will enable authentication through any set of Hadoop?
I've tested this pr.
but, this pr and not merged master branch both normalize. working well.
Please share your authentication settings.
It would be helpful to me to test.
Thank you.

@cloverhearts
Not going to pretend I'm an expert on HDFS- here's my use case, and I am happy to offer further explanation.
I have a BigInsights Cloud Cluster I set up on IBM BlueMix .  They have a free 30-day trial if you want to set one up to test.
I hacked on it for about an hour, this was what made it work.  Can you tell me more about what authentication settings you're looking for please?  I'm happy to help, but I don't know enough about it to know how to answer your question.  Further, I can set up a dummy one and provide you creds, but I'd rather do that non-publicly.

@cloverhearts @jongyoul Any way to try this one out?

closing this- lol at "hotfix"


How to redirect the index / after setting noPrefixDefaultLocale

Hello,
i have problem:

i set noPrefixDefaultLocale to false
in the description:
By default, paths generated for the default language don't contain a locale prefix, set this option to false to disable this behavior

so the generated routes like this, good:

[
  {
    path: "/en/",
    component: _3237362a,
    name: "index-en"
  },
  {
    path: "/fr/",
    component: _3237362a,
    name: "index-fr"
  }
]

then when starting the app, do not redirect to index it shows 404 page not found error!!!
http://localhost:port/ -> error
http://localhost:port/en  -> index page with English

what i want is some setting that change the default language after setting noPrefixDefaultLocale: false
or add another auto generated route like this of the default language:

[
  {
    path: "/",
    component: _3237362a,
    name: "index-en" // the default language!!! or redirectRootToLocale content!!
  },
  {
    path: "/en/",
    component: _3237362a,
    name: "index-en"
  },
  {
    path: "/fr/",
    component: _3237362a,
    name: "index-fr"
  }
]

i think this : redirectRootToLocale: 'en' must work every time.
the problem as description said:
Specify a locale to which the user should be redirected when visiting root URL (/), doesn't do anything if noPrefixDefaultLocale is enabled

so make redirectRootToLocale work every time to solve this as i think!!
and thank you :).

Same problem here, the route generation it's OK, show 404 if I tried to access without language on url, I added this options from docs to detect and autoredirect to browser language:
detectBrowserLanguage: true, redirectCookieKey: 'redirected', useRedirectCookie: true
But don't work, still showing 404 without redirect

Hey guys! Thanks for reporting this, the option's handling was a bit restrictive indeed, you should be able to achieve what you want with<EMAIL_ADDRESS>:)

I test it now on clean browser instance with<EMAIL_ADDRESS>but on my case still showing 404 without redirect to language.
This is my module configuration:
    ['nuxt-i18n', {
      locales: [
        {
          code: 'en',
          iso: 'en-US',
          name: 'English',
          langFile: 'en.json'
        },
        {
          code: 'es',
          iso: 'es-ES',
          name: 'Español',
          langFile: 'es.json'
        }
      ],
      defaultLocale: 'en',
      noPrefixDefaultLocale: false,
      loadLanguagesAsync: true,
      langDir: 'locales/',
      detectBrowserLanguage: true,
      redirectCookieKey: 'redirected',
      useRedirectCookie: true
    }],

This issue are present too when I try to access to one of my pages without language code, not only with the index, for example, if I try to access to http://localhost:3000/en/news it works as expected, same if I try with 'es' but if I try to access to http://localhost:3000/news show 404 like the case of the index.

Woops sorry @MitsuhaKitsune, I read your comment too fast and assumed your problem was the same as @NadhirBoukhenifra 😅
Could you give v2.8.1 a try? It should cover your use case.

Tested<EMAIL_ADDRESS>on clean browser instance, now the root path are redirected as expected very nice job ^^
The other routes still with a little issue, now when I try to access to http://localhost:3000/news don't show the 404 error but I get redirected to http://localhost:3000/en instead http://localhost:3000/en/news

Thanks @MitsuhaKitsune, I like your approach and I'll implement it asap :)
I'm planning on refactoring the module's code sometime to make it more scalable but I'm kinda waiting on Nuxt 2.0 to be released as it will bring better support for ES6 which should facilitate modules' development.

I have more things to make nuxt better, but I think this should implemented on nuxt core instead i18n, actually nuxt have a duplicated content problem on his routes too, for example:
/news/ and /news both are valid and the same route, but for SEO it's a big problem, should be more strict and generate only one mode, for example if it's a folder generate only a /foldername/ and don't allow access without final slash /foldername (instead access make a 301 redirection to /foldername/ or show 404, both are valid for SEO) and for single vue files make only the /filename as valid without the final slash.
I gona try to learn about modules and try to send PR to you and nuxt to help with this things, I read the documentation on https://nuxtjs.org/api/configuration-modules but I still don't know how I can debug the module startup, I tried to put some console.log('test') but don't show anything on console.

If you want to work on the module's code, I'd recommend you clone the source into your project, in a directory that's being watched in dev mode. You can change your nuxt.config.js to use the local module instead of the one in node_modules/, ie:
// nuxt.config.js

module.exports = {
  modules: ['./modules/nuxt-i18n', {}]
}


mongo:3.0.6 will not work on circleci

mongo:3.0.6 will not run within the Docker environment on CircleCI. For a minimal example, see:

https://circleci.com/gh/bitglue/mongo-gosu-bug/2
https://github.com/bitglue/mongo-gosu-bug

It appears the issue is that gosu attempts to fchown all the open FDs, and for whatever reason on CircleCI this is not possible.
I'm still looking into exactly what FDs these are, but it would seem reasonable to me there might be any number of FDs a process may have open which are not fchownable.

I haven't looked this issue closely, but CircleCI is running docker inside LXC container and the chown of FD in LXC container seems restricted.

I wonder what the motivation for the change to gosu was, anyway. I'd think CircleCI aside, not all filesystems support chown (or any concept of ownership at all), and there's not even a guarantee that a file descriptor is a regular file anyway: it may be a socket, or a pipe, etc. It looks like gosu might handle the pipe and socket cases by ignoring EBADF, but the comment suggests the reasoning is something else.
Besides, changing my file permissions is not a behavior I'd expect in a tool for changing users, nor does it appear to be documented anywhere. I wouldn't be surprised if there are a few security problems introduced by this change.

Hi, i think i'm having a similar problem:
i try to run a rocketchat server with docker with these two commands:
docker run --name db -d mongo mongod --smallfiles
docker run --name rocketchat -p 80:3000 --env ROOT_URL=http://localhost --link db:mongo -d rocket.chat

the creation of the mongodb server fails with following log:
error: failed switching to "mongodb": fchown fds permission denied

I'm running CentOS 7 with Docker version 1.7.1, build 446ad9b/1.7.1
Can someone help me getting it up and running?

@dominikmueller for now you can work around the issue by using the previous version of the mongo image:
docker run --name db -d mongo:3.0.5 mongod --smallfiles

Awesome! :) Many Thanks @bitglue - worked with 3.0.5 :+1:

Looks like Docker Hub has been updated and our builds are working now. Thanks for the prompt fix!


Logs are sometimes broken

Sometimes empty deletion logs
Sometimes edit logs on unedited messages

Empty message logs seem to be mostly for deleted messages sent by Pylon → blacklist id from logging

Should be fixed, will reopen if issues persist


Documentation on how to run program with gotollvm and which llvm and gotollvm versions to use

f17ba8c77083(gollvm) и 2c5590adfe09(llvm)


Conway Genesis  additions

Description

Closes https://github.com/input-output-hk/cardano-ledger/issues/3652

Adds two fields to ConwayGenesis:  Constitution and Committee
Updates Conway Translation to create EnactState using the two new fields from ConwayGenesis
Also added a trivial JSON gold test, to prevent accidental changes of the json serialization

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

Wow, it seems I don't understand at all how to use Crypto, EraCrypto, Era, ConwayEra  in a correct way (the fact that it compiles is not sufficient for that)!
I will try to deduce from your corrections, @lehins , thank you!


Sending FIO Fails silently when sending whole balance

I opened up the dev tools and read the error message. I couldn't send my entire balance because of the tx fee. When I tried to send, though, it just refreshed the page doing nothing.

Ah good catch. We should probably change that to show the deduction of the fee and only allow a maximum of the total available - fee.
I'll tag this issue for an upcoming release.


Preview is not rendering when editing in markdown

Category
Bug
GitBook.com
What is the current behavior?
When editing in markdown, the preview pane does not show anything.
What is the desired behavior?
The markdown should be rendered.
Additional information
benyohaiphysics
https://www.gitbook.com/book/benyohaiphysics/aqa-9-1-physics/edit#/edit/master/README.md?_k=k54a08

@benyohaiphysics this seems to work for me
Document Mode

Raw Mode


Easy Language selector landing page

Primitive audience
Limited range of navigation
Less retention window
Explicit direction is better than implied
Initial language support:

English
Hindi
Nepalese
Bhutanese
Punjabi
Bengali
Urdu
Arabic

Completed language selector with initial language support choices available:
https://user-images.githubusercontent.com/114235095/199523233-be726cd2-a85f-4d41-93e1-49d071da6d30.mp4

design iteration on this has been finished by @isidoravladic
cc @Shirinzaboli


Series.dt.tz_localize() changes the dtype to object

import pandas as pd
index = pd.date_range("2015-01-01", "2015-10-1", freq="W-SUN")
s = pd.Series(index)
print index.dtype
print s.dtype
print index.tz_localize("utc").dtype
print s.dt.tz_localize("utc").dtype

here is the output:
datetime64[ns]
datetime64[ns]
datetime64[ns]
object

s.dt.tz_localize("utc") is an array of Timestamp objects instead of int64 with datetime64[ns] dtype.

Yes, the datetime64 numpy dtype doe snot support timezone information. For this reason, when the user explicitly wants such information in a series, it is converted to an object array of Timestamps (which can hold this information). This is a current limitation of numpy.
But note that there is undergoing work to have such support in pandas, see #10477


🐛 [firebase_auth] FirebaseAuth.instance.idTokenChanges() isn't firing an event after the JWT expires

Bug report
FirebaseAuth.instance.idTokenChanges() isn't firing an event after the JWT expires using the latest core (1.10.0) and latest auth (3.2.0) with the latest flutter stable (2.5.3). Previously, at least under firebase_auth version 1.x.x., an event would fire after the JWT expires which happens every hour.
Steps to reproduce
1- listen to idTokenChanges
FirebaseAuth.instance.idTokenChanges().listen((event) {
      print('current time: ${DateTime.now()}');
      FirebaseAuth.instance.currentUser
          .getIdTokenResult()
          .then((res) => print('expirationTime: ' + res.expirationTime.toString()));
    });

2- wait until the expiration time (an hour).
3- no further events are fired.
Expected behavior
After the JWT expires, which has a lifetime of one-hour, FirebaseAuth.instance.idTokenChanges() should fire an event to indicate that the token has expired and it has been refreshed. As it was mentioned before, this was the behavior previously but I'm not sure when it has changed.
Additional Context

I've tested this with iOS only.

Force refreshing manually by calling FirebaseAuth.instance.currentUser.getIdTokenResult(true) or FirebaseAuth.instance.currentUser.getIdToken(true) would cause an event to fire.

The same issue applies to FirebaseAuth.instance.userChanges().

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 2.5.3, on macOS 11.6 20G165 darwin-x64, locale en)
    • Flutter version 2.5.3 at /Users/osaxma/fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 18116933e7 (4 weeks ago), 2021-10-15 10:46:35 -0700
    • Engine revision d3ea636dc5
    • Dart version 2.14.4

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/osaxma/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5.1, Build version 12E507
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.61.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.28.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • 9DA2058E-7269-416B-991F-BA92DE851CE6 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • macOS 11.6 20G165 darwin-x64
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 95.0.4638.69

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
- args 2.3.0
- async 2.8.1 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- cached_network_image_platform_interface 1.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.0.1 [flutter flutter_cache_manager cached_network_image_platform_interface]
- characters 1.1.0
- charcode 1.3.1
- clock 1.1.0
- collection 1.15.0
- crypto 3.0.1 [collection typed_data]
- diff_match_patch 0.4.1
- fake_async 1.2.0 [clock collection]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase_auth_platform_interface 6.1.4 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.2.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.1.0 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.2.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_storage_platform_interface 4.0.6 [collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.1.0 [async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- flutter_blurhash 0.6.0 [flutter meta pedantic]
- flutter_cache_manager 3.1.2 [clock collection file flutter http path path_provider pedantic rxdart sqflite uuid]
- flutter_lints 1.0.4 [lints]
- flutter_plugin_android_lifecycle 2.0.3 [flutter]
- http 0.13.4 [async http_parser meta path]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- idb_shim 2.0.1 [sembast collection path js meta]
- intl 0.17.0 [clock path]
- js 0.6.3
- linkify 4.1.0
- lints 1.0.1
- markdown 4.0.0 [args charcode meta]
- matcher 0.12.10 [stack_trace]
- meta 1.7.0
- nested 1.0.0 [flutter]
- octo_image 1.0.0+1 [flutter flutter_blurhash]
- path 1.8.0
- path_provider 2.0.5 [flutter path_provider_linux path_provider_macos path_provider_platform_interface path_provider_windows]
- path_provider_linux 2.1.0 [flutter path path_provider_platform_interface xdg_directories]
- path_provider_macos 2.0.2 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.3 [ffi flutter meta path path_provider_platform_interface win32]
- pedantic 1.11.1
- platform 3.0.2
- plugin_platform_interface 2.0.2 [meta]
- process 4.2.3 [file path platform]
- process_run 0.12.2+1 [path collection charcode string_scanner yaml meta args pub_semver synchronized]
- pub_semver 2.1.0 [collection meta]
- rxdart 0.27.2
- sembast 3.1.1 [meta path synchronized]
- sembast_sqflite 2.0.0+1 [sembast sqflite_common meta collection]
- sembast_web 2.0.1+1 [sembast idb_shim]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- sqflite 2.0.0+4 [flutter sqflite_common path]
- sqflite_common 2.0.1+1 [synchronized path meta]
- sqflite_common_ffi 2.0.0+3 [sqlite3 sqflite_common synchronized path meta]
- sqlite3 1.2.0 [collection ffi meta]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- synchronized 3.0.0
- tekartik_app_flutter_sqflite 0.4.1 [flutter sqflite sqflite_common_ffi sqflite_common process_run]
- term_glyph 1.2.0
- test_api 0.4.2 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- uuid 3.0.5 [crypto]
- vector_math 2.1.0
- web_socket_channel 2.1.0 [async crypto stream_channel]
- win32 2.2.9 [ffi]
- xdg_directories 0.2.0 [meta path process]
- yaml 3.1.0 [collection source_span string_scanner]

Using Auth on its own will refresh the token if it has expired, only before doing operations that requires a fresh idToken, are you using other FlutterFire packages alongside Auth, such as Firestore?

Hi @pr-Mais
I'm only using firebase_storage alongside firebase_auth and firebase_core.

And you were getting new events with the exact same environment (with storage only), before updating the packages?

I believe the behavior that I'm expecting came from a project where firebase_firestore and firebase_analytics were among the packages. So it makes sense now.
Since firebase_auth on its own isn't supposed to emit idTokenChanges events when the JWT expires, I'll close the issue.
Thank you for your time and the clarification.


Allow to modify the estimation of number of sides required to draw an ellipse / circle.

All the ellipses I draw in my projects need more polygon sides to look smooth. This is because I use units, so ShapeDrawer might think a circle has a radius of 4 pixels when it's actually 80 pixels. (PPU (pixels per unit) being 20 in this case)

You can set how big a pixel is in world units using setPixelSize(), so it can get a better estimate. So in your case you'd set it to 1/20 (units per pixel).
There's also an updatePixelSize() method, which is supposed to calculate the pixel size for you based on the projection matrix of the batch.
Let me know if they work! I haven't tested it with that large of a difference between world units and pixels yet, so it would be good to know if it works as intended.
Now that you mention it, I probably should have used a setPixelsPerUnit() method instead of its inverse since PPU is the normal ratio, maybe I'll add it in an update.

Thanks! Didn't see the updatePixelSize() methods, dunno how I missed that. They both work perfectly!


Allow multiple clients to use the same Transformer stream

Fixes #106.

Just wondering if I'm missing anything, but data streams should behave like any other iterator in Python, right? Or does "undefined" behaviour mean something different here?

What I'm trying to convey here is that users should not use data streams for more than one purpose, e.g. training and monitoring with the same data stream. Even though data streams behave like any other iterator in Python, I don't think transformers behave as one would expect, as demonstrated by the following piece of code:
import numpy

from fuel.datasets import IndexableDataset
from fuel.streams import DataStream
from fuel.schemes import SequentialScheme
from fuel.transformers import Mapping

def run(bug=True):
    constructor = DataStream.default_stream if bug else DataStream
    dataset = IndexableDataset(numpy.arange(100))
    dataset.default_transformers = ((Mapping, [lambda d: (2 * d[0],)], dict()),)
    data_stream = constructor(dataset, iteration_scheme=SequentialScheme(100, 10))
    iterator_1 = data_stream.get_epoch_iterator()
    iterator_2 = data_stream.get_epoch_iterator()
    for batch in iterator_2:
        pass
    next(iterator_1)

The problem is Transformer instances maintain a child_epoch_iterator attribute that is set when their get_epoch_iterator method is called. In that piece of code, the two client iterators unknowingly share the same child iterator if the data stream happens to be a Transformer instance.
I've seen many people get bit by this (myself included), and I think a proper warning in the documentation would be a good thing.

It seems like the child_epoch_iterator ought to be owned by the iterator, in order to at least make it possible for the data stream to remain stateless (there's no contract that this is the case, of course, but it should probably be the default unless the user knows they're doing otherwise?).

@dwf @bartvm I decided to go ahead and fix this once and for all.
I implemented a new TransformerDataIterator class whose constructor expects a child_iterator argument in addition to the transformer itself. The Transformer.get_data method now expects a child_epoch_iterator argument which is passed by TransformerDataIterator.
This has the effect of moving ownership of the child epoch iterator from the stream to the iterator. Now that transformers are stateless, we can finally safely re-use data streams at multiple places in the code. This means no more weird StopIteration exceptions when you accidentally re-use the main loop data stream for monitoring! :smile:

Hold on guys, what will happen if the user creates two iterators from a transformer that uses a stateful data stream, like e.g. a datastream over a TextFile? It seems like they will silently share the state...

@rizar I suppose it's a question of whether we want the stream object or the iterator object to be stateful, or both. Often, the situation is straightforward enough that the latter is clearly preferable. There are situations where it's not, though, see #310.
It seems like there's value in being able to separate a (stateless) description of a pipeline with the act of sucking things through that pipeline.

There are other stateful transformers, such as the Cache transformer.
Perhaps on the long term the solution is to take the same approach as we do with datasets, storing the state of a pipeline separately from the actual transformer instances. You could imagine a single object, owned by the iterator, holding the state of all the transformers. When you call __next__ on the iterator, this stateful object is passed to all the get_data requests of each transformer which can read and write to the state. This way several iterators of the same pipeline can have entirely separated states.
Did that make sense?

Yes, it does. It's unclear to me why you'd want a single state object and not want to encapsulate it as one per transformer though, since you already have such state objects: the iterator. So the iterator, when querying the stream object, passes a state object (call it a "context", maybe, since that's what people call containers of stateful nonsense with no better descriptor) that consists of the child iterator that it's receiving data from and whatever state the stream object needs to do its thing.
Anyway, this PR clearly doesn't quite fit the bill.

I think we're talking about the same thing, but just to clarify: DataIterator.__next__ does something like
class DataIterator(six.Iterator):
    def __init__(self, data_stream):
        self.data_stream = data_stream
        self.context = defaultdict(lambda: defaultdict(dict))

    def __next__(self):
        data = self.data_stream.get_data(self.context)

And then stateful transformers and streams do something like:
class StatefulTransformer(Transformer):
    def open(self, state):
        state['file'] = open('some_file.txt')

    def get_data(self, context, request=None):
        if not context[self]:
            self.open(context[self])
        return context['file'].readline()

I think I understand what you're getting at. I'll try to come up with a tentative implementation in the near future.


Possible Simplified Rails Configuration

Hey react_on_rails team,
Love the work you've put into the gem and I've made great use out of it over the last year ❤. My Rails and Webpack configurations have evolved since I first installed the gem. I've got it to the point where there is actually very little configuration needed on either side and have extracted the Asset Pipeline/Webpack integration into a bare bones plugin. I thought I'd drop you guys a note to see what you think about this alternate configuration and if you'd be open to possibly changing the way react_on_rails works.
https://github.com/rupurt/webpack-sprockets-rails-manifest-plugin
IMHO the biggest win from the simplified configuration is the ability to use standard Rails view helpers to load Webpack build assets directly and skip the Asset Pipeline while still leveraging all the Webpack goodness such as finger printing, HMR.
<% # app/views/layouts/application.html.erb %>
<% # Use rails helpers in the same way you normally would with sprockets %>
<!DOCTYPE html>
<html lang="en">
  <head></head>
  <body>
    <%= javascript_include_tag "webpack-application-bundle" %>
  </body>
</html>

// client/bundles/webpack-application.js
alert("Howdy, I'm a Javascript file downloaded from public/assets");

I've also extracted a second plugin which helps reduce the friction of requiring Webpack assets within asset pipeline files for legacy apps. https://github.com/rupurt/webpack-copy-after-build-plugin

I'll check this out over the weekend. In the meantime, any comments on: https://github.com/shakacode/react_on_rails/pull/671

@justin808 It seems like it's the exact same idea. https://github.com/rupurt/webpack-sprockets-rails-manifest-plugin#how-does-it-work describes how sprockets-rails can map logical paths to file system paths that end up getting served out of public.
I'll play around with https://github.com/mikechau/sprockets-stats-webpack-plugin and come up with 2 example repos so we can compare & contrast the 2 techniques. If sprockets-stats-webpack-plugin already handles all of this I'm more than happy to abandon my plugin and move forward with sprockets-stats-webpack-plugin

@justin808 I've added an example app along with the steps required for webpack-sprockets-rails-manifest-plugin. https://github.com/rupurt/react_on_rails_simplified_configuration_examples/tree/master/greenfield
I'll add extra examples for:

Working with a legacy app that uses sprockets
Webpack dev server config for HMR
Contrasting configurations for sprockets-stats-webpack-plugin

@rupurt Fabulous!

@rupurt Please let me know how this is going!

@justin808 I added examples for HMR & a contrasting setup for the sprockets-stats-webpack-plugin.
From what I can tell they are very similar.
sprockets-stats-webpack-plugin has support for the integrity hash but has a more complicated setup that doesn't use base webpack config settings.
webpack-sprockets-rails-manifest-plugin doesn't support the integrity hash but doesn't require much config.
Lmk what you think and how you want to proceed

Hi @rupurt! Please see https://github.com/rails/webpacker/issues/139. Very soon, we won't be putting Webpack assets through the rails asset pipeline!
I hope we can work together on this transition!
Maybe take a look at https://github.com/gauravtiwari/webpacker-example-app.
CC: @gauravtiwari.


Async function to return stream from of into_stream methods.

In one of our projects, we need to implement an ObjectStore trait form another crate backed by Azure storage account.
Conceptually this looks something like:
pub type FileMetaStream =
    Pin<Box<dyn Stream<Item = Result<FileMeta>> + Send + Sync + 'static>>;

pub struct AzureFileSystem {
    client: DataLakeClient,
}

fn convert<T>(response: ListPathsResponse) -> FileMetaStream {
    todo!()
}

impl ObjectStore for AzureFileSystem {
    async fn list_file(&self, prefix: &str) -> DFAccessResult<FileMetaStream> {
         let (file_system, prefix) = match prefix.split_once("/") {
            Some((file_system, prefix)) => (file_system.to_owned(), prefix),
            None => (prefix.to_owned(), ""),
        };

        let stream = self
            .client().
            .clone()
            .into_file_system_client(file_system)
            .list_paths()
            .directory(prefix)
            .into_stream()
            .flat_map(|f| convert(f.unwrap()));

        Ok(Box::pin(stream))
    }
}

Here the compiler complains, that the returned future does not implement Sync. To make sure, I experimented with some other operations that implement into_stream from the cosmos crate, which seems to display similar behaviour.
Trying to debug this I went through several permutations of further constraining types on Pageable etc with Send and Sync, but to no avail.
Any guidance how to further debug this, or where to look for a mitigation would wonderful :).
@rylev @ctaggart

Pageable should probably enforce that it is Send + Sync. It can do this by enforcing that T, E, and F in its definition are Send + Sync. You might run into issues though as I'm not sure all of our stream implementations are in fact thread safe, so you might get additional compiler errors. I'll try to take a deeper look ASAP.
cc @yoshuawuyts

I was kind of blocked on this issue and @rylev's suggestion seemed simple enough and took a shot at adding the additional trait constraints here - https://github.com/avranju/azure-sdk-for-rust/commit/18ebbfcf33a2956b1071173648440ff048da1d87. It doesn't seem to have broken anything and cargo test seems to pass in all crates (checked that since pageable.rs is in core) and my app seems to build fine with this change in place. If this looks good I am happy to turn it into a PR.

@avranju, yes, please submit a PR.

Ack. #784

tested with latest release and its fixed now :)

Hello, I have a similar issue with Pageable<GetBlobResponse, azure_core::Error>, which doesn't implement Sync. How can I wrap that stream in something similar to FileMetaStream shown in the example?


User not notified when creating a new EVC using a disabled interface

While adding a new EVC using one or more endpoints that are disabled on Kytos, the Web Interface creates the EVC without any warning, just the usual message showing the EVC was created.
We can see the EVC as "Not Active" by checking the Web Interface.
Checking the Kytos logs, we can see that the EVC wasn't deployed:
2024-01-24 14:26:11,081 - WARNING [kytos.napps.kytos/mef_eline] [evc.py:740:deploy_to_path] (Thread-442602) EVC(fb4b6602ea7a40, Vlan_699_Loop_test_temp) was not deployed. No available path was found.
A user/admin can be led to believe there is something wrong with the network, but it is just a matter of enabling the interface or not using it.
Also, even if the interface is later enabled, the EVC will work only after a redeploy.

Hi @RenataFrez, thanks for bringing this up. Yes, that's the currently behavior.
We can provide stronger validation guarantees if it's not desirable to even allow the EVC to be created if an UNI is disabled. Sometime ago, a related discussion was started on issue https://github.com/kytos-ng/mef_eline/issues/332, please check it out.
I believe the first step is indeed to map the rest of the use cases / scenarios where network operators do not want to allow an EVC creation then it can get implemented, also let us know the priority of this issue and we can eventually prioritize it.

I'll leave this on 2024.1 to keep on our radar to be discussed in the next planning


Not compatible IPad touch

Works prefect but not iPad safari. Obviously it not recognizes the $document.on('click') event. My solution was detect it iPad then 'touchstart'. As below:
var ua = navigator.userAgent,
event = (ua.match(/iPad/i)) ? "touchstart" : "click";
$document.on(event, eventHandler);

Thanks for the tip @sitedisks, if you would like to issue a pull request with that fix I can bring it in that way, else I will add it to the list of fixes for the next version.

No worries, @IamAdamJowett Just add touch features in your next release through. Cheers.

Duplicate of https://github.com/IamAdamJowett/angular-click-outside/issues/20


Issue-Recompile

Automated Review Comments
Issues in index.d.ts:

(9, 'Line exceeds 80 characters')
(9, 'Hardcoded string found')
Issues in index.js:
(2, 'Hardcoded string found')
(5, 'Line exceeds 80 characters')
(6, 'Line exceeds 80 characters')
(25, 'Hardcoded string found')
(35, 'Hardcoded string found')
(55, 'Hardcoded string found')
(60, 'Line exceeds 80 characters')
(60, 'Hardcoded string found')
(62, 'Hardcoded string found')
(64, 'Hardcoded string found')
(66, 'Hardcoded string found')
(69, 'Hardcoded string found')
(71, 'Hardcoded string found')
(75, 'Line exceeds 80 characters')
(75, 'Hardcoded string found')
(76, 'Line exceeds 80 characters')
(78, 'Hardcoded string found')
(84, 'Line exceeds 80 characters')
(88, 'Hardcoded string found')
Issues in tx-validator.ts:
(7, 'Hardcoded string found')
(9, 'Line exceeds 80 characters')
(21, 'Hardcoded string found')

I got it.


Spurious panic after IOAPIC initialization

Spotted in https://github.com/hermitcore/libhermit-rs/commit/1a3f1fd6d8a874fdb1d1a7ba9bab209732b36a23 – https://git.rwth-aachen.de/acs/public/hermitcore/libhermit-rs/-/jobs/2121733
[0][INFO] IOAPIC v17 has 24 entries
[0][INFO] Disable IOAPIC timer
[1][!!!PANIC!!!] /root/.rustup/toolchains/nightly-2021-09-29-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:1337: insertion index (is 1) should be <= len (is 0)
[1][INFO] Number of interrupts
[1][INFO] Shutting down system

Another case in https://github.com/hermitcore/libhermit-rs/commit/925514c4eb743136d29fe8a0fdf10a05a9eb3917.

Found again in https://github.com/hermitcore/rusty-hermit/commit/2f7bed9cf7edb099ba58ec233d28527fb1380932

Found again in https://github.com/hermitcore/rusty-hermit/commit/2f7bed9cf7edb099ba58ec233d28527fb1380932

Again in https://github.com/hermitcore/libhermit-rs/pull/325#issuecomment-1005119647.

This seems to happen more often now.
I can't reproduce this locally, so I opened https://github.com/hermitcore/libhermit-rs/pull/326 to gather more information.

Closed by https://github.com/hermitcore/libhermit-rs/pull/509.


Reference non-schema document root

Problem
This implementation doesn't handle non-schema roots.  This means that references that expect to be resolved from the open api root, can't be resolved.
Hack
I had a (probably hacky/bad) idea of how to resolve this: implement the open api doc type as a schema and its properties (at least the ones that hold schemas that need to be referenced) as keywords.  You can see a step toward this in the screenshot.
I'm not expecting this to go anywhere; just wondered if it'd work, and it kinda does.  I think I'd rather implement some mechanism where you can imbed a schema in a non-schema.
Proposals
(Re-)Introduce IRefResolvable or similar
This solution would be to provide an interface that can be implemented that defines what's required to resolve references.  Then JsonSchema implements that and the open api doc type can implement it as well.  (I actually just got rid of IRefResolvable with my update to v4 because I figured out how to do all that resolving internally.)
Update SchemaRegistry to handle non-schema roots
SchemaRegistry currently expects documents to be a JSON Schema.  This doesn't necessarily need to be the case.  Just need to figure out how to do this and not break everything else.

Related to #343


Add Questions section to README

I need to redo the contact section to questions and make the email and username create links to my profile and instructions on how to reach me.

Finished


Analyzer/FE error recovery for wrong number of setter parameters

Consider the following erroneous code:
// ERROR: setters must have exactly one parameter
void set badSetter(int a, double b) {
  var x = a + b;
}
void main() {
  badSetter = 1;
}

The current analyzer handles badSetter by reporting an error and creating an "impossible" element model in which the setter has two parameters.  This allows for fairly graceful recovery; for instance, the reference to double in the declaration of the bogus parameter b correctly points to the declaration of double in the SDK.  And the reference to b inside the method is correctly resolved to the extra parameter, and it even has the expected type of double.  However, this graceful recovery comes at a cost: when analyzing any code that makes reference to a setter (such as the code in main), the analyzer must be prepared for the possibility that the setter in question has any number of parameters (possibly even zero).
The front end handles this differently: it creates a kernel representation of the setter in which the two parameters are replaced with a single synthetic parameter having type dynamic and name #synthetic.  The upside to this is that it doesn't need any special case logic to analyze the reference to the setter in main.
But the downside is that it's not clear how to integrate this with the analyzer without losing the graceful error recovery.  Currently the way analyzer/FE integration works is that the analyzer element model is built from the kernel representation, which means that an element gets created for badSetter that has only one parameter.  Later, when the file is examined in more detail, an unresolved AST is created in which badSetter has two parameters, and a visitor (DeclarationResolver) tries to bind the declarations in the AST to their corresponding elements.  That visitor throws an exception because of the mismatch in parameter counts.
We could get past the exception by making the visitor tolerate a mismatch in parameter counts by, say, ignoring extra parameters found in the AST.  But there would be two follow-on problems:

Since the kernel representation of badSetter has just a single parameter whose type is dynamic, there's no way for the analyzer to resolve int and double to their corresponding declarations; that information has been lost.
When we then tried to analyze the body of the setter, there would be no element for the reference to b to refer to.  (Possible workaround: maybe we could pretend that b is a local variable declaration).

I'm probably missing something super obvious, but I have to ask.
The DeclarationResolver has the Kernel AST and the Analyzer AST in its hand and it walks the Kernel AST to create elements and then walks the Analyzer AST to read resolution information out of the resolution store and into the elements.
Why doesn't it walk the Analyzer AST to create elements?
In this example, we'd have the setter element with both parameter elements.  Then the problem is simply to ensure that we record resolution information for both parameters on the front end.

Two reasons that won't work:

The analyzer AST is heavyweight, so we only create it when we need to analyze a given file.  The elements are lighter weight, and we need them whenever a thing is referred to.  So if badSetter and main are in different files, and we analyze main first, we have to create the element for badSetter, and we don't have the AST to refer to.

There are some scenarios involving bazel where we don't have access to the AST at all, since analysis is running inside a bazel sandbox, and we have declared to bazel that the analysis for a given file only depends on that file and a summary of its dependencies.  We can't depend on the source files for the dependencies, because that would cause nuisance rebuilds; and if we declare that we don't depend on the sources for the dependencies, then bazel won't allow us to access them.

The CFE integration work is suspended, so this will not be addressed.


Tuning of chunkSize for LZ4 Compression Algorithm to gain performance in Indexing

Is your feature request related to a problem? Please describe.
Currently, there are two compression algorithms in place for OpenSearch, i.e LZ4 and zlib. In this, LZ4 is the default compression algorithm. Within this implementation, the default chunkSize used for LZ4 is 8kB. The idea is to set this value of chunkSize to 16kB to improve indexing throughput.
Initial benchmarking of the 8kB vs 16kB chunkSize is resulting in 2.5-3% gains in P50 throughput with the http_logs dataset.
Upon increasing the value of chunkSize to 16kb, the gains that we are observing are primarily due to lesser flushes being triggered upon indexing.
Describe the solution you'd like
A filter compressor can be introduced on top of the current lz4 implementation. This filter compressor will essentially use the underlying LZ4 algorithm but with a configurable chunkSize. Additionally, this chunkSize can also be introduced an index setting.
cc: @mgodwan @backslasht @shwetathareja

Good stuff! Any downsides? I am assuming varying chunk size produce the same output, so this can potentially even be dynamic? Are there other options in the compression codecs that we should expose at the same time?

As a well written issue with a promising improvement to OpenSearch I'm marking this as triaged.  It would be great to see a pull request and more details

@dblock
There could be one possible downside that we will be loading a larger chunk in memory at a time. Apart from that, the search latencies and merge performances are comparable for both chunk sizes in the initial runs. We are working on experiments and monitoring to quantify any impact.
Yes, the chunk size can be dynamic.
Other than chunk size, we have opportunity to expose blockShift (the log in base 2 of number of chunks to store in an index block) and maxDocsPerChunk (the maximum number of documents in a single chunk). We can try out the behavior by tweaking these parameters as well.

I think we should expose both.
When I say "downside" I didn't mean "tradeoff". I think it's absolutely great that we offer users a way to trade off speed (latency) for space (memory usage) - there are no downsides to that!

This is related to #3354.

I propose we add a dynamic index setting for chunk size.

I've performed some benchmarks with 8K and 16 Block sizes with LZ4 (default) compression codec with HTTP Logs Dataset.
I've observing around 3% improvement with HTTP Logs Dataset in the average throughput, around 4% reduction in storage size.

During benchmarks, I enabled some instrumentation specifically around compression

Cumulative latency for the compression improved with 16K Block size.
Sharing the POC implementation for enabling block sizes and instrumentation around compression over here
I also observed good improvements in the total merge sizes and the merge latencies as well for the 16 Block size with instrumentation in my local setup.


Nested profiles not supported with A/AAAA record aliases

Doc should clarify that A/AAAA record aliases pointing to Traffic Manager do not support nested profiles. See https://www.yammer.com/azureadvisors/#/threads/show?threadId=183025779269632

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

ID: d55c6a33-a21f-e8b6-da9b-f071d0db1df9
Version Independent ID: 87388983-e525-89a7-2048-585c6bd0927d
Content: Azure DNS alias records overview
Content Source: articles/dns/dns-alias.md
Service: dns
GitHub Login: @vhorne
Microsoft Alias: victorh

@jtuliani , Thanks for your feedback. We are looking into this query and will update you as soon as possible.

@rohinkoul , I have added you to the conversation to update the doc accordingly.

Any news about the issue?
How can I join https://www.yammer.com/azureadvisors/#/threads/show?threadId=183025779269632 thread?

Hi - I've assumed ownership of this article. I am reassigning the issue to myself. We currently have a large backlog of GitHub issues so I'm prioritizing these and working them as I am able.  Please reply to this thread if you are still experiencing an issue with the article that is referenced, or if you feel the issue can be closed now.  Thanks! #reassign:greg-lindsay

This is being tracked as internal content issue: 96176
#please-close

#please-close

#please-close


upterm: init at 0.4.6

Motivation for this change
Add upterm to nixpkgs
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

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

1 package built:

upterm

Result of nixpkgs-review pr 102276 run on x86_64-darwin 1

1 package failed to build:

upterm

@SuperSandro2000 sorry for the long lack of updates. I added myself as maintainer and disabled the tests.

Result of nixpkgs-review pr 102276 run on x86_64-darwin 1

1 package built:

upterm

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

1 package built:

upterm

Thanks to those who provided feedback but i don’t intend to use/maintain this package anymore. Feel free to pick this up if you would like to maintain it.


Added italics and bold styling markdown syntax features

Fixes #23
My intention was to implement additional syntax features for the markdown files such as italics and bold. They should be transformed into html properly and right now they are not.
My solution is to replace all markdown styling symbols with the corresponding html elements. In markdown, *sample text* or _sample text_ are used to display the sample text in italics and **sample text** or __sample text__ are used to display the sample text in bold. Therefore, for html, they have to be transformed into  and  elements respectively. I integrated my code into the existing markdown module. I combined it with the links replacement part as it uses the same technique.
I also added new lines to the testing markdown files to check my features.

@rokaicker Could you please review my pull request?

@rokaicker, yes, sure!
The overview now contains information about the supported markdown styling features.


Add indication that Search will only search in open files when no folder is open

It is not clear that only open file are searched even when it seems obvious in hindsight.

It now says "Only opened files will be searched..."


Chatbot Integration

Describe the solution you'd like
Have a simple chatbot that is capable of answering general/common user questions regarding things like "how to upload dataset into the training sandbox", "why is my training failing" in order to interactively provide debugging strategies.
The chatbot should have a mode called "Talk to a DLP Developer". When this mode is clicked, the user should be able to schedule a Calendly meeting with a DLP Developer to discuss the issue.
Setup Instructions (what branch to work off of)
Run the following commands
git checkout dev
git pull origin dev
git checkout -b chatbot-integration

FYI: If you are not able to immediately run git checkout dev, make sure you commit your changes in the current branch or run git stash and then run the above commands

we have calendly support if user submits feedback. we can expand on this potentially