[incubator/jaeger] Add agent-sidecar to query, OWNERS, update requirements and README

What this PR does / why we need it:

Added optional agent sidecar to query as per https://github.com/jaegertracing/jaeger-kubernetes/blob/da2225061c4e619c66854e69603b8d5799d55bcc/jaeger-production-template.yml#issuecomment-458042080

We need an OWNERS file per repo. Added myself as we are currently using this in production at Transit.

Removed "Upgrading" section from README that I added previously. Seeing that this chart is still incubating, backwards incompatible changes are to be expected.

Updated requirements cassandra and es.

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] title of the PR contains starts with chart name e.g. [stable/chart]

closing, will open a new PR


element-{web,desktop}: 1.11.10 -> 1.11.12

Description of changes
ChangeLogs:

https://github.com/vector-im/element-web/releases/tag/v1.11.11
https://github.com/vector-im/element-web/releases/tag/v1.11.12

Also, it has apparently been forgotten to regenerate yarn.lock on the release, element-web failed to build like this initially:
yarn install v1.22.19
[1/4] Resolving packages...
error Couldn't find any versions for "browser-request" that matches "^0.3.3" in our cache (possible versions are ""). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

To fix this, I decided to apply a patch with the proper yarn.lock and the problem is gone now. We should be careful however on the next update, so I added a warning to the update.sh-script to remind myself (or whoever will do the next update).
I'll leave it as-is now assuming that the issue fixes itself at the next time, a developer runs yarn. Also, I'm tired of having to chase dependency errors whenever I touch this package.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 198146 run on x86_64-linux 1

3 packages built:

element-desktop
element-desktop-wayland
element-web

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

element-desktop-wayland:

Package is missing a meta section.
If the package is using runCommand please make sure to inherit or create a meta section.
got build log for '/nix/store/73qysja4vgvlxw9vp6axk7s1fayyhzc0-element-desktop' from 'daemon'
When evaluating attribute ‘element-desktop-wayland’:
warning: unused-argument
Unused argument: paths.
Near pkgs/build-support/trivial-builders.nix:442:12:
    |
442 |          , paths
    |            ^

element-web:

got build log for '/nix/store/cfd95amgd4s9xyzaykrxai35841rcv9i-element-web-1.11.12' from 'daemon'
When evaluating attribute ‘element-web’:
warning: unused-argument
Unused argument: runCommand.
Near pkgs/applications/networking/instant-messengers/element/element-web.nix:3:3:
  |
3 | , runCommand
  |   ^


Add a wiki: Disney Dreamlight Valley Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://disneydreamlightvalley.fandom.com/wiki/Disney_Dreamlight_Valley_Wiki
Link to destination (independent) wiki: https://dreamlightvalleywiki.com/Dreamlight_Valley_Wiki

The destination wiki is well ahead of the origin wiki (716 vs. 4,271 content pages) and page content/quality is more up-to-date.

Added in commit https://github.com/KevinPayravi/indie-wiki-buddy/commit/b97038054167a3d18d891054494be237393c41e0

Now available in version 2.3.0


Workflow addition of Pause/Resume and Purge

Description
Added in support for Pause, Resume, and Purge for workflow
Due to a naming mismatch in a few methods, the associated runtime change for this PR is here: https://github.com/dapr/dapr/pull/6296
Issue reference
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

@halspang sorry that this wasn't included in the PR description, but we planned to have a whole host of breaking changes in the v1.11 release. Some of what you're seeing here was outlined in: https://github.com/dapr/dotnet-sdk/issues/1027


change func Handle panic->info,when http: multiple registrations

When I use http.HandleFunc()  to registrations function more times,it happen panic.
I think it return more better than happen a panic

I signed it!

I signed it!

Hi @Bin-DuS - The PR seems to have some additional code than just returning instead of panic'ing. In any case, changing the panic behavior to just return will be a breaking change at this point. And I believe the decision to panic was made deliberately.
If you believe this behavior should be changed, I would request you to open an issue and discuss there. Once it's approved, then we can make the change. Thank you.


Missing distro ASCII: OpenWRT

Would be nice to have it in neofetch. Original OpenWRT ASCII is located in file /etc/banner, can be useful.

This PR adds the ascii logo, the only issue is that it's a lot longer than the other logos so the info might not fit on the screen. Are there any alternate logos?
https://github.com/dylanaraps/neofetch/pull/315

There's also this alternate logo with WIRELESS FREEEDOM below it, let me know which variant you like.
"\
${c1} _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
         |__| W I R E L E S S   F R E E D O M
"

It's good without. I thought so, that it will be a bit too wide


Issue when running npm run production

Laravel Mix Version: 0.8.8
Node Version (node -v): 6.9.1
NPM Version (npm -v): 4.0.5
OS:

Description:
Getting production compile error during the UglifyJs call. Everything works find when I run npm dev, but when I run npm run production it fails.
Steps To Reproduce:
Here is my package.json
{
  "private": true,
  "scripts": {
    "dev": "cross-env NODE_ENV=development webpack --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch": "cross-env NODE_ENV=development webpack --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "hot": "cross-env NODE_ENV=development webpack-dev-server --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    "production": "cross-env NODE_ENV=production webpack --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
  },
  "devDependencies": {
    "axios": "^0.15.3",
    "babel-helper-vue-jsx-merge-props": "^2.0.2",
    "babel-plugin-syntax-jsx": "^6.18.0",
    "babel-plugin-transform-vue-jsx": "^3.3.0",
    "bootstrap-daterangepicker": "^2.1.25",
    "bootstrap-sass": "^3.3.7",
    "font-awesome": "^4.7.0",
    "highcharts": "^5.0.7",
    "imports-loader": "^0.7.0",
    "jquery": "^3.1.0",
    "laravel-mix": "^0.8.0",
    "lodash": "^4.16.2",
    "moment": "^2.17.1",
    "numeral": "^2.0.4",
    "tether": "^1.4.0",
    "vee-validate": "^2.0.0-beta.22",
    "vue": "^2.0.1",
    "vue-multiselect": "2.0.0-beta.13",
    "vue-resource": "^1.2.0",
    "vue-strap": "github:wffranco/vue-strap",
    "vue-tables-2": "^0.4.20",
    "vue-toastr": "^2.0.5",
    "vue2-dropzone": "^2.1.8",
    "vuejs-datepicker": "^0.6.2"
  }
}

The offending file
<template>

        <v-server-table url="/accounts" :columns="columns" :options="options"></v-server-table>

</template>

Also, this is the only thing I'm changing from the default configuration. I need to do this because vue-tables-2 plugin uses some jsx files to help generate the templates.
mix
.webpackConfig({
    module : {
        rules: {
            test: /\.jsx?$/,
            loader: 'babel-loader' + mix.config.babelConfig(),
            exclude: /node_modules(?!\/(vue-tables-2|vue-pagination-2))/,
            query: {
                presets: [
                    "es2015"
                ]
            }
        }
    }
})

It fails at the data() { line. I'm not sure why it would fail there, when it seems to work everywhere else. I'm assuming this is something to do with UglifyJs, but can't tell what's going on here. Any ideas?

If you remove your custom webpackConfig settings, will it compile properly? Excluding the jsx bits.

No, if I remove all the the components that require that loader and then change the config to not have that, it still doesn't compile.

Sorry, I should mention that it just fails in a different spot. It fails on a different data() line in another component.

That makes me think that Babel isn't compiling properly for you. Do you have a custom .babelrc file in your project root by any chance? We use our own, if you're not already using a custom version. It needs to have:
// .babelrc
{
   'presets': [
      ['es2015', { 'modules': false }]
   ]
}

That was it, I didn't think to check for one. I added that to my babelrc file and it all compiled correctly. Thank you!


Fix #1947: Rewrite calls to print.

Review by @sjrd.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2292/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2973/
Test PASSed.

Weren't you going to un-import Predef.{print, println}?

That's all.

There is a small problem when importing  Predef.{print, println} with import Predef.{print => _, println => _} it seems that the default import Predef._ gets overwritten by this one. This causes a couple of other methods to fail because they can't find some implicit conversions. Such as:
[error] /Users/nastucki/GitHub/scala-js/ir/src/main/scala/org/scalajs/core/ir/Printers.scala:444: value until is not a member of Int
[error]           for (dim <- lengths.size until tpe.dimensions)
[error]                                    ^
[error] /Users/nastucki/GitHub/scala-js/ir/src/main/scala/org/scalajs/core/ir/Printers.scala:845: value to is not a member of Int
[error]         for (i <- 1 to dims)
[error]                     ^

I could rewrite everything more explicitly but I would consider this approach a bit hacky.

What about this:
import scala.Predef.{print => _, println => _, _}

(note the last _).

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2297/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2978/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2304/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2987/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2305/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2988/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2308/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2991/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2307/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2990/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2306/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2989/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2313/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2996/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2309/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2992/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2314/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2998/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/2315/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/2999/
Test PASSed.

LGTM


Create mailing lists for mentees and mentors

Is this initiative still open, I had applied for a mentee quite some time ago, any updates thanks.


Test client CA certificate install and delete

Test client CA certificate install and delete

Code checked in - https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/13046/


glib: 2.70.2 -> 2.70.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for glib is: "C library of programming buildings blocks"
meta.homepage for glib is: "https://www.gtk.org/"
meta.changelog for glib is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin/bin/gapplication had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin/bin/gsettings had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin/bin/gio had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin/bin/gdbus had a zero exit code or showed the expected version
0 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 2.70.3 with grep in /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin
found 2.70.3 in filename of file in /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin

Rebuild report (if merged into master) (click to expand)

18938 total rebuild path(s)

14920 package rebuild(s)

14900 x86_64-linux rebuild(s)
4038 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
ArchiSteamFarm
AusweisApp2
CHOWTapeModel
ChowCentaur
ChowKick
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
EBTKS
EmptyEpsilon
HentaiAtHome
MIDIVisualizer
MMA
OSCAR
OVMF
OVMFFull
PageEdit
R
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL2_ttf_2_0_15
SDL_Pango
SDL_gfx
SDL_gpu
SDL_image

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A glib https://github.com/r-ryantm/nixpkgs/archive/559a657dbf02d7f216873fe515f739bb710eeb12.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin
ls -la /nix/store/g5w9c889mq6ab6r72skx65ag5immg9cz-glib-2.70.3-bin/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @hedning @jtojnar @dasj19 @maxeaubrey @lovek323 @7c6f434c for testing.

@ofborg eval

Changes look okay:

Overview of changes in GLib 2.70.3

Several important fixes to FD handling in gspawn (#2503, #2506, #2580)

Several important fixes to GDBus message and GVariant parsing of invalid data (#2557, #2572)

Fix potential data loss due to missing fsync when saving files on btrfs (!2437)

Bugs fixed:

#2503 gspawn.c may clobber target fds
#2506 gspawn.c fails to close child_err_report_fd if it is duped to avoid conflation with one of the target_fds
#2557 Arrays of zero-element tuples with non-zero length lead to infinite loops in g_dbus_message_new_from_blob
#2572 Check for GVariant recursion depth before recursing
#2580 gspawn doesn't set CLOEXEC if close_range fails unexpectedly
!2394 Backport !1968 “gspawn: Fix file descriptor conflation issues” to glib-2-70
!2415 Backport !2412 “paramspec: fix unref annotation” to glib-2-70
!2437 Backport !2425 “gfileutils: Remove outdated BTRFS fsync optimization from set_contents” to glib-2-70
!2444 Backport !2435 “gspawn: Report errors with closing file descriptors between fork/exec” to glib-2-70
!2455 Backport !2454 gdbusmessage and gvariant fixes to glib-2-70

Translation updates


Removing Puppetfile from repository.

The Puppetfile contains the mod puppetlabs/apache, which is causing apache to be still installed when the module is used with puppet-librarian. Removing Puppetfile will cause apache to be no longer installed by the librarian.

:+1:

Bump

I have removed the Puppetfile and update the Puppetfile.lock


Error to login to webapp in Locust

I want locust to be able to login to my web application and start to click in the links inside the web application.
With this code I just get activity for the front page with the login and i don't get any notification from inside the application.
Code:
import random
from locust import HttpLocust, TaskSet, task
from pyquery import PyQuery

class WalkPages(TaskSet):
    def on_start(self):
        self.client.post("/", {
            "UserName"<EMAIL_ADDRESS>            "Password": "2Password!",
            "submit": "Sign In"
        })
       self.index_page()

@task(10)
def index_page(self):
    r = self.client.get("/Dashboard.mvc")
    pq = PyQuery(r.content)
    link_elements = pq("a")
    self.urls_on_current_page = []
    for l in link_elements:
      if "href" in l.attrib:
        self.urls_on_current_page.append(l.attrib["href"])

@task(30)
def load_page(self):
    url = random.choice(self.urls_on_current_page)
    r = self.client.get(url)

class AwesomeUser(HttpLocust):
    task_set = WalkPages
    host = "https://myenv.beta.webapp.com"
    min_wait = 20  * 1000
    max_wait = 60  * 1000

I get the follow msg in the terminal after the first round.
[2015-02-13 12:08:43,740] webapp-qa/ERROR/stderr: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 267, in run
self.execute_next_task()
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 293, in execute_next_task
self.execute_task(task["callable"], _task["args"], *_task["kwargs"])
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 305, in execute_task
task(self, _args, *_kwargs)
File "/home/webapp/LoadTest/locustfile.py", line 31, in load_page
url = random.choice(self.urls_on_current_page)
File "/usr/lib/python2.7/random.py", line 273, in choice
return seq[int(self.random() * len(seq))]  # raises IndexError if seq is empty
IndexError: list index out of range
[2015-02-13 12:08:43,752] webapp-qa/ERROR/stderr: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 267, in run
self.execute_next_task()
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 293, in execute_next_task
self.execute_task(task["callable"], _task["args"], *_task["kwargs"])
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 305, in execute_task
task(self, _args, *_kwargs)
File "/home/webapp/LoadTest/locustfile.py", line 31, in load_page
url = random.choice(self.urls_on_current_page)
File "/usr/lib/python2.7/random.py", line 273, in choice
return seq[int(self.random() * len(seq))]  # raises IndexError if seq is empty
IndexError: list index out of range
[2015-02-13 12:08:43,775] webapp-qa/ERROR/stderr: Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 267, in run
self.execute_next_task()
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 293, in execute_next_task
self.execute_task(task["callable"], _task["args"], *_task["kwargs"])
File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 305, in execute_task
task(self, _args, *_kwargs)
File "/home/webapp/LoadTest/locustfile.py", line 31, in load_page
url = random.choice(self.urls_on_current_page)
File "/usr/lib/python2.7/random.py", line 273, in choice
return seq[int(self.random() * len(seq))]  # raises IndexError if seq is empty
IndexError: list index out of range

I am also facing same error,
[2015-07-31 15:51:23,258] JADEHOL1366/ERROR/stderr: Traceback (most recent call last):   File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 264, in run     self.schedule_task(self.get_next_task())   File "/usr/local/lib/python2.7/dist-packages/locust/core.py", line 325, in get_next_task     return random.choice(self.tasks)   File "/usr/lib/python2.7/random.py", line 273, in choice     return seq[int(self.random() * len(seq))]  # raises IndexError if seq is empty IndexError: list index out of range

@casidos this part of the error list clearly says what's wrong:
File "/home/webapp/LoadTest/locustfile.py", line 31, in load_page
url = random.choice(self.urls_on_current_page)
File "/usr/lib/python2.7/random.py", line 273, in choice
return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty
IndexError: list index out of range

It means that the list you're trying to build - self.urls_on_current_page - is empty.
@echorohit did you decorate your tasks with the @task  decorator?
Without that, it never queues up the tasks and hence the error.

Your tasks need to be methods of the WalkPages class.


How can I export to Solidity

How can I export to Solidity

Hello, this is not supported yet, you may follow #12 for progress.


Fix: Remove meatball button and add truncate to sort button

Overview

Remove meatball button and add truncate to sort button
Screen Captures

https://github.com/nishiki-tech/nishiki-frontend/assets/99148565/2bce0047-b23a-40d4-86cf-1efaf45f5667
References

Notes

Assignee Checklist:

[x] The naming convention of the PR title is correct (See the comment at the top of this template)
[x] The base branch is correct (See: Types of Branches)
[x] The branch name follows the Branch Naming Conventions
[x] The correct assignees and reviewers have been designated for this PR
[x] The coding style follows the Coding Style Guide
[x] All the related issues are associated with this PR
[x] All criteria in the associated issues are met (please tick the checkboxes)
[x] My changes do not generate new warnings or errors (especially in the console)

Reviewer Checklist:

[ ] Double-check the "Assignee Checklist"
[ ] The code follows the generic best practices and our Coding Style Guide
[ ] The code is well-commented and easy to understand
[ ] The UI changes accurately reflect the provided design

@kanta1207 @ShoeheyOt
Could you review this PR when you have a moment?

@kanta1207 @ShoeheyOt
Thank you for your propmt reviews!


Uncaught TypeError: Cannot read property 'LongText' of undefined

Hi,
I am attempting to use the recline.js SlickGrid demo on my page, but I keep getting the following error in my console:

Google and looking around at other issues haven't been helpful, so I must surmise I'm doing something wrong... and it's probably incredibly simple.  I'm just a bit stumped.
Any tips on how to resolve this?

I know, this issue is closed but I had the same issue as Wes and I think it's worth dropping a note about  it. Actually the error with LongText in line 183 is a mistake in view.slickgrid.js. There are no editors Slick.Editors.LongText or Slick.Editors.Text (just look up slick.editors.js). Solution: Change Lines 183 to 185 of view.slickgrid.js to:
      'string': Slick.Editors.LongTextEditor,
      'integer': Slick.Editors.IntegerEditor,
      'number': Slick.Editors.TextEditor,

@manfredk great spot - would you be up for submitting a pull request here to fix this.

@rgrp After reviewing my comment above, I've noted that my supposed solution above actually missed the point. I followed the recline grid view tutorial - and the actual reason why there were no editors was that a a reference to slick.editors.js is missing in the tutorial (see: http://okfnlabs.org/recline/docs/tutorial-views.html), like
<script type="text/javascript" src="vendor/slickgrid/2.0.1/slick.editors.js"></script>

Who's maintaining the tutorial? If it's on github I could submit a pull request .

@manfredk Could you try the example at https://github.com/mattfullerton/recline-view-slickgrid-demo? As you can see from the discussion above I had no problems eventually after having this same problem, but I also see that my grid is not editable.
@rgrp Could you merge master into gh-pages so that the link to the demo is on the site? Or give me access.
@manfredk If that doesn't solve it, or if you need to include that file to get editing to work, or if you would like to improve the tutorial, I think the places you need to look at are:
https://github.com/okfn/recline/blob/master/docs/tutorial-views.markdown
and
https://github.com/okfn/recline/blob/master/docs/tutorial-views.markdown
Although I see the editors file is already listed in the main dependencies list!:
https://github.com/okfn/recline/blob/master/_includes/recline-deps.html
So at some point someone must have thought we needed it. In the tech docs for the slickgrid view, the editable option is shown (http://okfnlabs.org/recline/docs/src/view.slickgrid.html), I imagine if I added this to the example, it would fail without the dependency. The only mystery is why anyone starting from scratch would have this problem. I suspect that the default value of editable went from true to false at some point, so that the release creates this problem but master does not.

@mattfullerton invitation sent to labs team which will give you access.

Thanks - is merged now
On 17 Feb 2015 19:51, "Rufus Pollock"<EMAIL_ADDRESS>wrote:

@mattfullerton https://github.com/mattfullerton invitation sent to labs
team which will give you access.
—
Reply to this email directly or view it on GitHub
https://github.com/okfn/recline/issues/432#issuecomment-74726401.

@mattfullerton i did as in my second comment and that solved the problem for me. I have not tried yet to make the grid editable - I was just putting it together in a first try to show data in the grid.
I've checked the demo you've set up, but the dependency to slick.editors.js is missing there as well (in index.html ... no time to try it out. I'll have a look at the tutorial though (tomorrow).

Yes, the dependency is missing, sort of unpurpose (we should decide whether to add it if editable parameter requires it, as I expect it does - I have no time today to test :-))
The philosophical question is whether to include it anyway so that people don't hit this cryptic error when they innocently make their grid editable. The best thing would be to detect the problem and give a warning, and probably to include the dependency with a comment in the demo.

In my case, I did not intentionally try to make the grid editable - I just
used the setup as proposed in the demo.
The error is hit in recline.js on line 3244, which is referencing the
slickgrid editors. The editors are referenced in any case, whether
columnEditors are configured or not - if no columnEditors are given it just
initializes the typeToEditorMap to the default editors.
I suppose that what you have in mind is that - when no columnEditors are
configured - the editors should not be initialized at all, but that's not
the case.
On Wed, Feb 18, 2015 at 9:35 AM, Matt Fullerton<EMAIL_ADDRESS>wrote:

Yes, the dependency is missing, sort of unpurpose (we should decide
whether to add it if editable parameter requires it, as I expect it does -
I have no time today to test :-))
The philosophical question is whether to include it anyway so that people
don't hit this cryptic error when they innocently make their grid editable.
The best thing would be to detect the problem and give a warning, and
probably to include the dependency with a comment in the demo.
—
Reply to this email directly or view it on GitHub
https://github.com/okfn/recline/issues/432#issuecomment-74829489.

--

Manfred Kipfelsberger, Schwabacher Str. 129, 90763 Fürth
web: http://www.cen-seo.de, email<EMAIL_ADDRESS>Tel. 0151-270 20 866, skype: manfred.kipfelsberger

Nearly three months later, and I've had a chance to look into this again, and found the problem. There was a mixture of two Slickgrid versions in the folder. If you included the minimized one (old Slickgrid), the problem did not occur. If you only included the new version (introduced so that we could use some plugins), it caused this error. I'm working on a branch (https://github.com/okfn/recline/tree/fix-slickgrid-mixups) where the version is upgraded and all old code removed, and all tutorials etc. updated, but 4 tests are failing even though my simple page based on the tutorial is working (with slick.editors being required, as correctly pointed out by @manfredk). I'm changing the title of the issue and reopening.

Slickgrid had changed how it deals with column titles which was what was causing the tests to fail. I've replaced them.


Unable to automatically accept skype call

Conversation details
Is there any way to automatically accept skype calls with this library? if No, It would be very helpful to have this feature.

SkPy handles messaging only (i.e. text and attachments) -- voice/video calling is not included.


no function in self host gitbook

I installed this plugin but didn't see the + symbol in the right side as official gitbook
Can it be used in self host gitbook?

The feature only works if you host your book on gitbook.com.
In the **Settings **page, scroll down to Features, Inline Comments should be enabled.

It would be a great if we see this feature in self hosted gitbook. Is there any hope?
I'm planning to use gitbook for self hosted software requirements artifacts.
Confluence must die!

or some plugin like https://tsi.github.io/inlineDisqussions/ will be great too :)

Thanks for these links! In my case it needs something more advanced. I would like to connect each comment to certain git tag and something like requirement id, and then to have ability of fetching comments by tags and ids.

Thanks for publishing your find, @changsijay!  It'd be nice if this were officially supported.


Post Elaboration, information is lost

Test Case: ArianeElab
RHS expression on line 19 thru' 28 are replaced with constants and the original expressions are lost.
Original source:
    localparam VLEN       = (XLEN == 32) ? 32 : 64;
    localparam PLEN       = (XLEN == 32) ? 32 : 56;

    localparam IS_XLEN64  = (XLEN == 32) ? 1'b0 : 1'b1;
    localparam ModeW      = (XLEN == 32) ? 1 : 4;
    localparam ASIDW      = (XLEN == 32) ? 9 : 16;
    localparam PPNW       = (XLEN == 32) ? 22 : 44;
    localparam vm_mode_t MODE_SV = (XLEN == 32) ? ModeSv32 : ModeSv39;
    localparam SV         = (MODE_SV == ModeSv32) ? 32 : 39;
    localparam VPN2       = (VLEN-31 < 8) ? VLEN-31 : 8;

As per the UHDM model:
    localparam VLEN              =  64;
    localparam PLEN              =  56;

    localparam IS_XLEN64         = 1;
    localparam ModeW             = 4;
    localparam ASIDW             = 16;
    localparam PPNW              = 44;
    localparam vm_mode_t MODE_SV = 8;
    localparam SV                = 39;
    localparam VPN2              = 8;

Original source includes the term XLEN and those expressions are required to build results for operations like "Find All References".

 If expressions are kept symbolically, then no constant propagation can be done and no elaboration can be done.
If you need to do find all references, you can look at the non-elaborated UHDM for the modules: vpiAllModules instead of the vpiTopModules (elaborated view).
Note that unfortunately, packages are also fully elaborated, so all params/local params will be constant propagated in packages. There is no view for packages that contain the original expressions, maybe we can add that.

There is no view for packages that contain the original expressions, maybe we can add that.

For LS, original text in the source will be a requirement for number of features. This will need to be retained in the UHDM hierarchy or provide some other access to this information.

Fixed by #2677


Including ls.unveilhooks.js via script tag breaks browser

Describe the bug
If you include the unveilhooks plugin using a script tag, the browser will report "Uncaught ReferenceError: require is not defined". This is because require() does not exist in the browser/client-side JavaScript. I believe this issue was created when the plugin was modified to support AMD loaders. See:
if(typeof module == 'object' && module.exports){
factory(require('lazysizes'));
} else if (typeof define == 'function' && define.amd) {
define(['lazysizes'], factory);
} else if(window.lazySizes) {
globalInstall();
} else {
window.addEventListener('lazyunveilread', globalInstall, true);
}
As a workaround I removed the first 2 else if statements.
To Reproduce
Provide a url where the bug can be reproduced. (Use for example: jsbin, codepen, jsfiddle.net or codesandbox.io
Steps to reproduce the behavior:
To reproduce the error load lazysizes and the unveilhook plugin using the source tag in the browser and attempt to load a bg image with lazysizes.
In what environment (browser/device etc.) does this bug happen/not happen:
Mac OS / Chrome 83

@alex9000
Thanks for the issue. I would need a test case that demonstrates the issue.

I couldn't reproduce the issue in JS Bin, but it did break in Chrome.

@alex9000
I think there is a little bit more to it, because I can not think how this alone will break Chrome. I hope you can somehow replicate the issue and give me all required steps to reproduce it properly. Otherwise I will close this issue.

Hi @aFarkas I can't reproduce it in JS Bind or codepen, so go ahead and close it.


Fix example test namespace deletion

use e2e package delete function that stops waiting once namespace is terminating

going to force merge to hopefully fix CI issues over the weekend


UmbracoCms 8.0.0 constraint

Can't install Umbraco.ModelsBuilder.Ui 8.0.2 NuGET package because UmbracoCms 8.0.0 constraint to Umbraco.ModelsBuilder.Ui (= 8.0.1)

Yes - twitted about it yesterday : although ModelsBuilder 8.0.2 has been released on NuGet and Visual Studio MarketPlace, it won't be usable before we release the next patch release of Umbraco (quite probably, 8.0.1) - because it requires fixes in Umbraco. So... it wouldn't even run on Umbraco 8.0.0.
Stay tuned ;-)

My bad ... should follow you on twitter :P


build: Switch to ubuntu-latest for builds

This code does not have any dependencies that are specific to any specific
version of ubuntu.  So instead of testing on a specific version and then needing
to do work to keep the versions up-to-date, we switch to the ubuntu-latest
target which should be sufficient for testing purposes.
This work is being done as a part of https://github.com/openedx/platform-roadmap/issues/377
closes https://github.com/openedx/edx-cookiecutters/issues/478

It looks like this might be broken because the underlying tests were assuming that Python 3.8 would always be available but since newer versions of Ubuntu don't have it by default, tests are failing.  It looks like when this repo was updated to test with python 3.11, the underlying cookiecutters were not themselves updated to run on Python 3.11/3.12.
That work will need to be done and python 3.8 support properly dropped before we can cleanly do this update.

Ah, thank you! Missed those!


Add function to tokenize text stories and split into batches

The test is right now two cases for text input and tokenized input, lmk if there's anything to add to it

@joshuawe I added the docstrings to the functions,
the first two functions extend_deque() and make_new_samples() serve as two helper functions;
I noticed that the failing check is for the pytest in

tests/eval/test_token_labelling.py:2: in
import spacy
E   ModuleNotFoundError: No module named 'spacy'

Hi @siwei-li , will check your updated code.
The error that we currently see (Link) is not because of the missing spacy module (I assume that your error message was from your local machine).
Following the link we see that beartype raised a type error in the extend_deque(). It seems the parameter text_stories expected the type list[str] but got something like list[int].

E   beartype.roar.BeartypeCallHintParamViolation: Function delphi.train.dataset_tokenization.extend_deque() parameter
text_stories=[[1581, 1327, 61, 300, 3003, 1427, 1029, 2570, 1736, 3552, 3170, 635, 3551, 91, 3052, 2560,...]] violates type hint
list[str] under non-default configuration BeartypeConf(claw_is_pep526=True, is_color=None, is_debug=False,
is_pep484_tower=False, strategy=<BeartypeStrategy.O1: 2>, warning_cls_on_decorator_exception=<class
'beartype.roar._roarwarn.BeartypeClawDecorWarning'>), as list index 11 item list [3638, 2316, 723, 505, 3953, 325, 742, 2799,
3320, 4063, 159, 3931, 3300, 3072, 3636, 2544, ...] not instance of str.```

The script for HF is added @jettjaniak
(Uploaded the tokenized 'stories' dataset to https://huggingface.co/datasets/delphi-suite/batched-tokenized-stories)


update CallOptions to use struct format

The current version uses the @call(.always_tail) format for the CallOptions. The latest Zig version - https://ziglang.org/documentation/0.10.0/#call - has a Struct for it.
The current version, when compiling a simple program, threw the following:
C:\Users\pyro\Code\game\.gyro\zgl-ziglibs-github.com-d7b06c09\pkg\binding.zig:1829:19: error: expected type 'builtin.CallOptions', found '@TypeOf(.enum_literal)'
    return @call(.always_tail, function_pointers.glClearColor, .{_red, _green, _blue, _alpha});
C:\Users\pyro\scoop\apps\zig\current\lib\std\builtin.zig:594:25: note: struct declared here
pub const CallOptions = struct {
                        ^~~~~~
referenced by:
    clearColor: C:\Users\pyro\Code\game\.gyro\zgl-ziglibs-github.com-d7b06c09\pkg\zgl.zig:217:12
    main: C:\Users\pyro\Code\game\src\main.zig:33:11
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

C:\Users\pyro\Code\game\.gyro\zgl-ziglibs-github.com-d7b06c09\pkg\binding.zig:1913:19: error: expected type 'builtin.CallOptions', found '@TypeOf(.enum_literal)'
    return @call(.always_tail, function_pointers.glGetError, .{});

With the following changes, the code compiles.

That would be a backport from 0.11 (indev) to 0.10 (release). You need to go back to a commit that is compatible to 0.10. zgl officially does only track master

Got it boss. Did not know that. These kind of information would be nice to have in the README. And I think most people installs the stable version of the compiler and it cannot be expected that they should find a compatible commit with their version. For example, if you'd have a stable branch which is in line with 0.10, that'd be nice.
If they want to use your library, they can't. While this is your repository and your rules, it just makes using this library not straightforward.


Split test output for better readability

The problem:
The results from all the tests are printed as one giant wall of text, making it difficult to identify which test outputted what. You can use ctrl+f to manually search for the test name, but this is not ideal.

My suggestion:
Separate test output by which test they belong to. Let users navigate directly to the test output by clicking on the test name in list of tests.
Example:
# Test 1 : a new stack should have a length of zero
 <test 1 results>

# Test 2  : popping from an empty stack returns an error
<test 2 results>

Thanks for the report. We have been thinking about this for a while too. See #420 for details.

:warning: Rambling ahead ⚠
Our current solution reads the stdout from the docker container running the tests.
Scores are included in this output as JSON strings. Each test emits one (or potentially multiple) score JSON strings, e.g.:
{"TestName":"TestRoundRobinAG","Score":169,"MaxScore":169,"Weight":30}

These are parsed by the server and are used to generate the scores shown in the frontend:

Example output from running tests in docker container:
=== RUN   TestStacksAG/SafeStack

{"TestName":"TestStacksAG/SafeStack","Score":15,"MaxScore":15,"Weight":1}
--- FAIL: TestStacksAG (0.00s)
    --- PASS: TestStacksAG/SliceStack (0.00s)
    --- FAIL: TestStacksAG/CspStack (0.00s)
    --- PASS: TestStacksAG/SafeStack (0.00s)
=== RUN   TestStackSliceAllocationAG
=== RUN   TestStackSliceAllocationAG/SliceStack

{"TestName":"TestStackSliceAllocationAG/SliceStack","Score":5,"MaxScore":5,"Weight":1}
=== RUN   TestStackSliceAllocationAG/CspStack
    stack_ag_test.go:94: Size() = -1, want: 200
    stack_ag_test.go:100: Pop() = <nil>, want: 199

{"TestName":"TestStackSliceAllocationAG/CspStack","Score":5,"MaxScore":15,"Weight":10}
=== RUN   TestStackSliceAllocationAG/SafeStack

{"TestName":"TestStackSliceAllocationAG/SafeStack","Score":15,"MaxScore":15,"Weight":1}
--- FAIL: TestStackSliceAllocationAG (0.00s)
    --- PASS: TestStackSliceAllocationAG/SliceStack (0.00s)
    --- FAIL: TestStackSliceAllocationAG/CspStack (0.00s)
    --- PASS: TestStackSliceAllocationAG/SafeStack (0.00s)
FAIL
exit status 1
FAIL    dat320/lab6/stack       0.017s

This output is displayed in the frontend (excluding the JSON strings, as those are removed during parsing on the server).
One alternative we've considered is to have the test output be entirely JSON:
$ go test -json

{"Time":"2024-11-01T10:25:48.951166571+01:00","Action":"start","Package":"dat320/lab4/scheduler"}
{"Time":"2024-11-01T10:25:48.958919028+01:00","Action":"run","Package":"dat320/lab4/scheduler","Test":"TestFIFOScheduler"}
{"Time":"2024-11-01T10:25:48.958987608+01:00","Action":"output","Package":"dat320/lab4/scheduler","Test":"TestFIFOScheduler","Output":"=== RUN   TestFIFOScheduler\n"}
{"Time":"2024-11-01T10:25:48.959066551+01:00","Action":"output","Package":"dat320/lab4/scheduler","Test":"TestFIFOScheduler","Output":"--- PASS: TestFIFOScheduler (0.00s)\n"}
{"Time":"2024-11-01T10:25:48.959099154+01:00","Action":"pass","Package":"dat320/lab4/scheduler","Test":"TestFIFOScheduler","Elapsed":0}

This way we could parse and associate the output for a given test with it's corresponding score object.
However, this approach will most likely require a separate parser for each language, as they likely do not use the same JSON schema. Some languages might not support JSON output at all without some third-party library. e.g. C# seem to use XML rather than JSON.
Another alternative is to use the currently unused TestDetails field of Score:
message Score {
    uint64 ID           = 1;
    uint64 SubmissionID = 2 [(go.field) = { tags: 'gorm:"foreignKey:ID"' }];
    string Secret       = 3 [(go.field) = { tags: 'gorm:"-"' }];  // the unique identifier for a scoring session

    string TestName    = 4;  // name of the test
    string TaskName    = 5;  // name of task this score belongs to
    int32 Score        = 6;  // the score obtained
    int32 MaxScore     = 7;  // max score possible to get on this specific test
    int32 Weight       = 8;  // the weight of this test; used to compute final grade
    string TestDetails = 9;  // if populated, the frontend may display these details
}

Teachers creating tests will then have the responsibility for emitting failed test cases on a per-test basis in the emitted JSON score string.
In the case of Go tests we could create a wrapper for Errorf and Fatalf in the kit package on score to add failures to TestDetails
Some quick testing:
func Errorf(t *testing.T, sc *score.Score, format string, args ...interface{}) {
	t.Errorf(format, args...)
	sc.TestDetails += fmt.Sprintf(format, args...)
	sc.TestDetails += "\n"
}

func TestStacksAG(t *testing.T) {
    ...
    sc := scores.MaxByName(t.Name())
    defer sc.Print(t)
    ...
    case "Size":
        f got := stack.Size(); got != test.wantSize {
            sc.Dec()
	    Errorf(t, sc, "%s(%s) = %v, want: %v", action, test.args[index], got, test.wantSize)
	}
    case "Push":
	stack.Push(test.args[index])
	if got := stack.Pop(); got != test.args[index] {
	    sc.Dec()
	    Errorf(t, sc, "%s(%s); Pop() = %v, want: %v", action, test.args[index], got, test.args[index])
	}
	stack.Push(test.args[index])
    case "Pop":
	if got := stack.Pop(); got != test.wantElem {
	    sc.Dec()
	    Errorf(t, sc, "%s(%s) = %v, want: %v", action, test.args[index], got, test.wantElem)
	}
    }
    ...
}

// sc.Print()
{
    "TestName":"TestStacksAG",
    "Score":0,
    "MaxScore":39,
    "Weight":1,
    "TestDetails": "Size() = -1, want: 0\nSize() = -1, want: 0\nPush(Item1); Pop() = \u003cnil\u003e, want: Item1\nSize() = -1, want: 1\nPop() = \u003cnil\u003e, want: Item1\nSize() = -1, want: 0\nPush(i1); Pop() = \u003cnil\u003e, want: i1\nPush(k2); Pop() = \u003cnil\u003e, want: k2\nPush(x4); Pop() = \u003cnil\u003e, want: x4\nSize() = -1, want: 3\nPop() = \u003cnil\u003e, want: x4\nSize() = -1, want: 2\nPop() = \u003cnil\u003e, want: k2\nSize() = -1, want: 1\nPop() = \u003cnil\u003e, want: i1\nSize() = -1, want: 0\nPush(x); Pop() = \u003cnil\u003e, want: x\nPush(y); Pop() = \u003cnil\u003e, want: y\nSize() = -1, want: 2\nPop() = \u003cnil\u003e, want: y\nSize() = -1, want: 1\nPop() = \u003cnil\u003e, want: x\nSize() = -1, want: 0\nSize() = -1, want: 0\nSize() = -1, want: 0\n"
}

Which can then be shown in the frontend. Example without any particular styling or thought behind it, and some UTF madness:


feat: New after_init_cli_run_handlers hook

Resolves #575
TODO:

[ ] Tests
[ ] Docs

Codecov Report

Merging #578 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #578   +/-   ##
=======================================
  Coverage   99.73%   99.73%
=======================================
  Files          41       41
  Lines        2669     2673    +4
  Branches      431      431
=======================================
+ Hits         2662     2666    +4
  Misses          3        3
  Partials        4        4

Flag
Coverage Δ

#unittests
99.73% <100.00%> (+<0.01%)
:arrow_up:

Impacted Files
Coverage Δ

src/schemathesis/cli/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Best way to have API Auth [question]

I my Auth Controller as
const login = yield basicAuth.validate(email,password);
 if (login) {
   const user = yield User.findBy('email',email);
   //TODO Generate API access token
   var token = yield request.auth.generate(user);
   user.apiTokens().save(token);
   response.cookie('token',token,{
     //TODO set secure for production
     //secure:true,
   });

   response.send({success:true,cookies:request.cookies()})
   return
 }

And my API Route as
Route.group('api',function () {
  Route.resources('user','api/UserController');
}).prefix('/api/v1').middleware('auth:api');

But after login in and writing a token cookie and still get Invalid Auth Error when accessing the route.
What am i missing? Is there a better way to do API auth?

@Nigeltiany Just make sure to format questions as per specs define here https://guides.github.com/features/mastering-markdown/.
Next, I don't understand why are you using Basic Auth + API Auth together?

@thetutlage What would be a better way to do it?

Does sending a post request to a route that has the methodconst isLoggedIn = yield request.auth.check()

check the database for username and password from the request?

Does api config section in config/auth.js allow setting different fields to be used for authentication with the auth.check() function?

I used basic auth to check if a user credentials exist, the api auth to assign a token, send it as a cookie then save it to the database.

You must only use one authentication technique to give access to restricted routes. When using basicAuth your customers will have to login, since basicAuth is stateless authentication.
Read this http://security.stackexchange.com/questions/755/how-does-basic-http-auth-work
In Adonis you can make use of the auth middleware
Route.group('api',function () {
  Route.resources('user','api/UserController');
}).prefix('/api/v1').middleware('auth:basic');

Now any request that does not have basic auth headers will be denied by the middleware itself. And authenticator will take care of validating the credentials for you.

Thanks, but i'm not there yet.
I want API auth for users that are registered, that is, users that have provided a valid username and password.
After confirming a user credentials exist. I want to give them a token which they are supposed send back on every request enabling them to access the rest API.
How should i go about that with regard to AdonisJS.

Okay, you should render a login form where a user will enter their credentials and if their credentials are correct, you will return a response with the API token or JWT token, and then they can make use of that token for future requests.
Checkout this sample controller for same https://github.com/adonisjs/adonis-rally/blob/develop/app/Http/Controllers/UsersController.js
The login page will not use any authentication, since it needs to be publicly accessible.

Thank you very much @thetutlage
That clears the fog for me.

One more thing.
how best to redirect to a route with the acquired token in the request header?

@Nigeltiany response.redirect('location') can be used to redirect the request. Closing feel to open issues for specific issues 😄

Is it possible to revoke jwt tokens. Where are they currently stored?

I'm with this same doubt.

Where is a jwt tokens they stored, As for Local Storage I already know, I refer to the database!

JWT tokens are not stored. Read more about JWT in the official page. JWT tokens are created with user information on the token payload, and expiration date. You then set that token to the front end as a cookie OR on the payload and save it on localStorage. If you want to check to which user that token belongs to, you can encode the token with some user specific data and decode it and you will get that users data


Implement configuration reference generation

In my opinion there should be a way to automatically generate a configuration reference for my Django project when using django-configurations so that I can easily include it in project documentation without just referencing some source file.

I was thinking of a workflow like the following:
from configurations import Configuration, values

class MyConfiguration(Configuration):
    DEBUG = values.BooleanValue(default=True)
    SECRET_KEY = values.SecretValue(description="The django secret key", reference="https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-SECRET_KEY")
    IS_AWESOME_FEATURE_ENABLED = values.BooleanValue(description="Enables the awesome feature because of which you want to run this application")

manage.py create-configuration-reference --format github-markdown-table --out ./configuration-reference.md

Key | Type | Default | Description
--- | --- | --- | ---
DEBUG | [bool](https://django-configurations.readthedocs.io/en/stable/values/#configurations.values.BooleanValue) | True |
SECRET_KEY | [secret](https://django-configurations.readthedocs.io/en/stable/values/#configurations.values.SecretValue) | *not set* | [reference](https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-SECRET_KEY): The django secret key
IS_AWESOME_FEATURE_ENABLED | [bool](https://django-configurations.readthedocs.io/en/stable/values/#configurations.values.BooleanValue) | *not set* | Enables the awesome feature because of which you want to run this application

Which renders as

Key
Type
Default
Description

DEBUG
bool
True

SECRET_KEY
secret
not set
reference: The django secret key

IS_AWESOME_FEATURE_ENABLED
bool
not set
Enables the awesome feature because of which you want to run this application

I am willing to implement and maintain this feature if it is desired.
I am also open for discussions about the details.

Seems like a good idea to me but since you wrote this over 3 years ago I am not sure if you are still interested in doing it?
If you are lets have a discussion otherwise close this issue.

I still think, this is a good thing to have but right now I have other things on my plate. I'll close this then.

I would not bpother... this project seems doomed since the projects leads do not respond and the Jazzband owner seems to want to be unwilling to let people help
https://github.com/jazzband/help/issues/379


AV-62638: Implement a low level storage for all Istio Objects

This patch introduces a low level Istio Object store.
There should be an upper layer on top of this store that would
abstract this store and provide object specific access.
There are two levels of locking implemented:

All namespace level lock. This will be used when we obtain
the objects of a specific namespace from the global store.
Namespace lock. This will be used, when we want to update
objects inside a given namespace.

Each of these stores will be initialized per object_type in the
future patches. Unit tests are added for some scenarios.

I will have a virtual_service wrapper over this store tomorrow to give a better idea on how this is meant to work.


[Task]: Implement future semtype in runtime

Description
Relevant section in the spec
Describe your task(s)
No response
Related area
-> Runtime
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Added with #43279 via #43251


Biome replacer not working when nature's spirit is presentt

Version: 1.20.1
How to reproduce:
Step 1: create a modpack with Natures Spirit, Biome Replacer and Terrablender (If forge make sure to get sinytra connector, forgified fabric api, connector extras and the fabric version of terrablender and biome replacer)
Step 2: Add "minecraft:cherry_grove > minecraft:taiga" to your biome_replaceer.properties
Step 2: Generate two worlds, with and without natures spirit
Step 3: Locate a cherry grove on the NS world and then go to the same coords on the non-NS world
heres my latest log in case it can help figure out why this is happening
https://mclo.gs/adISdSU

This is a longstanding TerraBlender issue, and I'm not really sure how I can fix it. I asked for help over on TerraBlender's issue tracker, hopefully they'll point me in the right direction.

ah thanks, whats strange is that its only happening with NS for me... like BOP seems to work


chore: update streamChatCompletion.py

recieved -> received

Thanks! I should really invest in searching for a good spell checker lol.


GFLW Driver Error appear when run realsense-viewer on RK3588s(Ubuntu 20.04 LTS focal, kernel version 5.10)

Required Info
How to solve GFLW Driver Error on rk3588s when run realsense-viewer?

Camera Model
D455

Firmware Version
<IP_ADDRESS>

Operating System & Version
Ubuntu20.04 LTS focal

Kernel Version (Linux Only)
5.10.160

Platform
RK3588s

SDK Version
2.55.1

Language
C++

Segment
others

Issue Description
I compiled the SDK from source, circumventing the incompatibility with the kernel version 5.10.
command:
 cd realsense2/bin
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$PWD:/home/firefly/realsense2/lib/
./realsense-viewer

log:
GLFW Driver Error: GLX: No GLXFBConfigs returned
GLFW Driver Error: GLX: Failed to find a suitable GLXFBConfig
Could not initialize offscreen context!

It appears that the corresponding config file cannot be located. Do you have any effective troubleshooting methods?

links:
https://wiki.t-firefly.com/zh_CN/Firefly-Linux-Guide/first_use.html#an-zhuang-glx-ku

Specific solutions：
sudo apt install -y libgl1-mesa-glx libgl1-mesa-dri libglx-mesa0
sudo reboot

works!

My development board is from Firefly, and this GLFW driver issue is related to the board manufacturer.
If you are still unable to resolve the issue, we recommend contacting the development board manufacturer.


Setup postgres locally

https://devcenter.heroku.com/articles/heroku-postgresql#local-setup

Install Postgres App.

Run psql (make sure it's running on port 5432)

execute commands:

CREATE USER <user>;
CREATE DATABASE <db_name> OWNER <user from line above>;

Should have dev and test databases

Done.


update geoviews URL in docs

Suggesting an update geoviews URL
(this was automatically forked via GitHub "edit" feature and for some reason this branch picked up some other grammar suggestions made previously)

Thanks @cranmer ! No worries about the other commits — that's an artifact of the stable branch.
And good to have you as an xarray contributor!

one small step :-)


HDD requirement in VM types

If you intend to use Azure Elastic SAN Preview or Azure Disks with Azure Container Storage, then you should choose a [general purpose VM type](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes-general) such as standard_d4s_v5 for the cluster nodes. The VMs must have standard hard disk drives (HDD), not SSD.

What does "must have" mean?
If my understanding is correct, we are not able to specify the disk type such as HDD of the node when creating an AKS cluster. So, I’m confused.
If VM types support HDD such as standard_d4s_v5, does it meet the requirements?

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

ID: 485b103b-8fd6-09be-7bcb-8624c4233324
Version Independent ID: 8ed7fc4a-ba14-0653-2867-89d647c34228
Content: Quickstart for installing and configuring Azure Container Storage Preview with Azure Kubernetes Service (AKS)
Content Source: articles/storage/container-storage/container-storage-aks-quickstart.md
Service: storage
Sub-service: container-storage
GitHub Login: @khdownie
Microsoft Alias: kendownie

@torumakabe
Thanks for your feedback! We will investigate and update as appropriate.

@torumakabe
In the context you mentioned, "must have" means that the specified VM type, such as standard_d4s_v5, is required to meet the given requirements. Specifically, it states that the VMs used for the cluster nodes should be of a general-purpose type and should have standard hard disk drives (HDD) rather than solid-state drives (SSD).
However, you are correct in pointing out that when creating an AKS (Azure Kubernetes Service) cluster, you don't have direct control over specifying the disk type for the underlying nodes. The disk type is determined by the AKS cluster's node pool configuration, and by default, AKS uses VMs with SSD storage.
In the case of AKS, you cannot enforce the requirement of using VMs with HDD storage for the cluster nodes directly during cluster creation. The choice of VM type and disk type is managed by AKS itself based on the node pool configuration.
Therefore, if your specific requirement is to use HDD storage for your cluster nodes when using Azure Elastic SAN Preview or Azure Disks with Azure Container Storage, you may need to consider alternative approaches such as provisioning your own VMs and configuring them as Kubernetes nodes outside of the AKS service. This would allow you to have more control over the VM types and disk types used for your cluster nodes. However, managing the cluster manually in this way would require additional administrative effort and would not benefit from some of the automated management features provided by AKS.

@AjayBathini-MSFT Thanks for your comment.
If alternative ways are necessary to meet the requirements stated in this document, I believe those steps should be clearly explained. As far as I know, I cannot add the VM to AKS nodepool using az aks nodepool add command.
Also, I don't want to use HDD if this requirement is not necessary.
By the way, I tried the Azure Disk pattern, and the Quickstart was successful without the alternative way you mentioned. I specified standard_d4s_v5 and the default Premium SSD.

@khdownie
Can you add your inputs on above query.

@torumakabe I think the confusion here comes from data disks vs OS disk. It's the data disks that need to be HDD, not the OS disk, and I've (just now) clarified this in the docs. I think for standard_d4s_v5 VM you get Premium SSD for the OS disk with no temp storage. And it sounds like you didn't add any data disks because you don't have that level of control. Am I understanding correctly?

@khdownie When creating an AKS cluster or node poll, it is not possible to create a Data disk. Therefore, I understood the phrase "must have" as a requirement for an OS disk when I first read this document.
I would understand if the expression could be rewritten as follows.
If you want to use HDDs in Azure Elastic SAN Preview or Azure Disks, please choose a VM type that allows it such as standard_d4s_v5.

@torumakabe thank you for raising this issue. I believe we can provide better, more specific guidance around this requirement. I am checking with engineering and will update the docs and this issue soon.

@torumakabe the docs were misleading/wrong regarding the HDD guidance, and I have removed it. You should be fine with your VM configuration. Again thank you for reporting this.

#please-close


[Request] Gateway discovering

Hey. First of all, nice library, since I have problems with Lightify's cloud this is perfect. One thing that would be a nice addition to this library is gateway discovering. Basically nmap_ing_ the network and searching for IP with port 4000 running, is it possible to implement?

According to this:
https://github.com/noctarius/lightify-binary-protocol
...discovery is accomplished through mDNS (AKA Bonjour).


better describe developer advantages in docs & Readme

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
7059

Relevant Lines:
9768

💛  - Coveralls


refactor: state & performance

State

added ValueState and MapState which wrap a BehaviorSubject and a Map.
added factory functions to wrap state creation to keep it flexible.

Performance

Run DOM changes outside of NgZone (with direct DOM manipulation)
Set OnPush change detection for default components

@all-contributors please add @danzrou  for doc, code, ideas

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Inconsistent WCS keywords in output cube

Hello,
When running an input cube scene through HSIM3 I get inconsistent WCS entries in the output cube.
The input cube has the following wavelength WCS entries:
CRVAL3  =      19381.215277778 / Coordinate value at reference point
CRPIX3  =                  1.0 / Pixel coordinate of reference point
CUNIT3  = 'Angstrom'           / Units of coordinate increment and value
CTYPE3  = 'wavelength'         / Coordinate type code
CDELT3  =      2.4305555551181 / Coordinate increment at reference point
CD1_1   =            -4.18E-06
CD2_2   =             4.18E-06
CD2_1   =                  0.0
CD1_2   =                  0.0
CD3_3   =               2.4305
CD3_1   =                  0.0
CD3_2   =                  0.0
CD1_3   =                  0.0
CD2_3   =                  0.0
CDELT1  =             4.18E-06
CDELT2  =             4.18E-06
But the output cubes have the following entries:
CRVAL3  =                1.951 / Coordinate value at reference point
CRPIX3  =                    1 / Pixel coordinate of reference point
CUNIT3  = 'micron  '           / Units of coordinate increment and value
CTYPE3  = 'wavelength'         / Coordinate type code
CDELT3  = 0.000141405610155732 / Coordinate increment at reference point
CD3_3   =               2.4305
Here the CD3_3 and CDELT3 are incompatible, and ds9 produces erroneous wcs when opening the cube in wavelength.
And for the spatial coordinates:
CRPIX1  =                    1 / Pixel coordinate of reference point
CRPIX2  =                    1 / Pixel coordinate of reference point
CUNIT1  = 'mas     '           / Units of coordinate increment and value
CUNIT2  = 'mas     '           / Units of coordinate increment and value
CTYPE1  = 'RA---TAN'           / Coordinate type code
CTYPE2  = 'DEC--TAN'           / Coordinate type code
CRVAL1  =            -1904.148 / [arcsec] Coordinate value at reference point
CRVAL2  =            -2084.148 / [arcsec] Coordinate value at reference point
LATPOLE =                 90.0 / [deg] Native latitude of celestial pole
BUNIT   = 'erg/s/cm2/um/arcsec2' / data unit type
RADESYS = 'FK5     '
CD1_1   =            -4.18E-06
CD2_2   =             4.18E-06
CD2_1   =                  0.0
CD1_2   =                  0.0
CD3_3   =               2.4305
CD3_1   =                  0.0
CD3_2   =                  0.0
CD1_3   =                  0.0
CD2_3   =                  0.0
CDELT1  =                 20.0
CDELT2  =                 20.0
Here again the CDELT1 and CDELT2 are inconsistent with the CD1_1 and CD2_2 entries.
This makes ds9 being confused about the pixel scale and overall RA / DEC coordinates.
Johan

Thanks for reporting this problem.
It is now fixed in a4bed528c472f3005024d91303321645b919be60


Hardhat Test Suite for Predeploys

Test suite for predeploys
If we want to add to CI we could do so in Acala repo
Relates to #92

Stale


Ipad Pro. Minor Misalignment Issues

Minor misalignment seen when doing exploratory testing on iPad Pro.
Checkout steps, product list pages.
OS: iOS 11.0.3.
Browser: Safari
See attached images.

duplicate of other tickets


Allow value types to be cached and injected as dependencies

Resolves https://github.com/ppy/osu-framework/issues/6157
Consider this an RFC.
The way structs are handled right now is a mess. If I (as the person who wrote all of this) can't understand how they're handled, then I don't think anyone can. And my confusion is the result of two conflicting thought processes:

CancellationToken is somehow a special type. How is it so?
The way I view structs is as always being initialised, whether in a "zeroed" state or otherwise (unless they're nullable).

Every value type is a special type that can only be cached by osu!framework. CancellationToken is doubly special because it sometimes arrives in load(), and sometimes doesn't, depending on whether you're in an async-load context. So the only proper way to use BDL with CancellationToken is to make it nullable.
In my opinion, if you want to cache and resolve a value-type dependency and accept whatever footguns that comes with (by-val copies, you can't cache multiple ints, etc), then you should be able to do so. But the framework should retain predictable semantics, which for me means matching the C# spec - ValueType = default! is a zero-initialised struct. This is a simplification of semantics to me.
New semantics:
Get<int>() => 0;               // Allowed
Get<int?>() => null;           // Allowed
Cache<int>(0);                 // Allowed
Cache<int>(null);              // Disallowed
Cache<int?>(0);                // Warning in NRT contexts
CacheAs<IInterface>(MyStruct); // Allowed - boxed.
Cache<object>(null);           // Exception
Cache<object?>(null);          // Exception + warning in NRT contexts

Is this something I foresee being used? No. It's just for the sake of clarifying semantics.

Why are tests failing here? I'd expect failures in the sourcegen path until a package bump or something, but the reflection path is failing too?

Reading the OP:
Cache<int?>(0);                // Warning in NRT contexts

Why would this warn? Looks like perfectly legal code to me...

Why would this warn? Looks like perfectly legal code to me...

Because caching null is not allowed 1 2, therefore attempting to cache a may-be-null value warns about that.

Almost thinking all of these tests need to be rewritten...


examples: Create example with filtering capabilities

Create an example that uses the container collection and trace
collection packages to filter events by container.

Sadly, I was not able to run it, but it seems correct:
$ sudo ./exec --containername foo
WARN[0000] Runtime enricher (containerd): couldn't get current containers

I think there was a problem in the version I pushed: trace-exec is not a valid name for a tracer. (it seems that - is not allowed as the name of an eBPF map...). It was also missing error handling around tracerCollection.AddTracer() so that's probably why you didn't see any error. Would you mind trying again?


Using Ionide with 32 bit TypeProviders does not work

To use the Fsharp.Data TypeProvider for MSACCESS 2016 you need to install either the Access Database Engine 2010 in 32bit or 64bit (Microsoft.ACE.OLEDB.12.0).
Visual Studio runs in 32bit and uses FSI with 32bit that is shipped with Visual Studio so you cannot use the 64bit version of the Access Database Engine otherwise you will get the error: The Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine
The Ionide plugin for VSCode uses FSIANYCPU and as my Window 7 is a 64 bit machine it will run in 64 bit. This will not work with the 32 bit Access Database Engine. You will again get the error The Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine
As a workaround I tried to rename the fsi.exe form the sdk folder (on 64bit Windows it is C:\Program Files (x86)\Microsoft SDKs\F#\4.1\Framework\v4.0\fsc.exe) to fsianycpu.exe (so you make it 32 bit) then you can use fsi and msbuild in VScode and Visual Studio. But you will still get red lines saying the The Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine. The same error as mentioned before that you will get when using the wrong 64 bit ADB /32bit VS combination.
So it looks like the red lines are generated by a tool using anycpu -> 64bit, too.
Do you know what tool is used for it? Is it e.g. fsautocomplete from the user/.vscode folder that is used for this? There is just one fsautocomplete (anycpu) so you cannot do the workaround by renaming the 32bit exe to the exe file.
In short you currently have three options:

User 64bit providers and just use VSCode and you are fine. VS no fun
Use 32bit providers and use Visual Studio and you are fine. VSCode no fun
Rename the fsi.exe as described and use VS without problems and VSCode with red lines everywhere but it will still compile and you can use the FSI.

If someone is starting with F# often they will come with a C# and Visual Studio background. To help them starting to use the great features of Ionide we should find a solution for this scenario. Otherwise they will not only stop VSCode but also might stop using F# at all as most of the F# Community seems to use Ionide but they are not able to use it in those scenarios.
Any suggestions what to do? Or maybe there is a solution/configuration in Ionide that I missed which just needs a better documentation?
VSCode: 1.18.0
Ionide-FSharp: 3.12.2
VS: 2017
FSharp.Data: 2.4.2

@2moveit
to change the  fsi used you can use this setting
  // The path to the F# Interactive tool used by Ionide-FSharp
  "FSharp.fsiFilePath": "",

about intellisense (that's by fsautocomplete), i'll check

Thanks @enricosada for the hint with the settings. I set the settings to:
"FSharp.fsiFilePath": "C:\\Program Files (x86)\\Microsoft SDKs\\F#\\4.1\\Framework\\v4.0\\fsi.exe"
and it works now without renaming but still the prob with intellisense.

@2moveit issue is fsautocomplete, as you said, fsac is compiled as AnyCPU.
i checked but i didnt found a good way to run a .net console app (compiled as AnyCPU) as 32bit. There is a workaround using CorFlags.exe but is not that good for end users.
please open an issue in https://github.com/fsharp/FsAutoComplete/issues/ maybe we can just compile fsautocomplete.exe as 32bit too (just the exe) so can be bundled in ionide.

Thanks @enricosada. I've just opened the issue: https://github.com/fsharp/FsAutoComplete/issues/249

Closing it here since it's tracked in FSAC repo


Document constraints of Viewer's continuous read behavior, fix related test

What
Our ability to load files as they are written is limited by both flushing & notification behavior of OS & filesystem.
This is now documented on the save methods.
See also

https://github.com/notify-rs/notify/issues/422

Also, fixes a test that failed because of this on Windows (nightly ci).
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!
[x] If have noted any breaking changes to the log API in CHANGELOG.md and the migration guide

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

Talking with some of the other folks we should call out windows specifically to be known to be susceptible to this issue


Add nFlow

Adds an entry for nFlow.

@jsyrjala can you resolve conflicts here ?

Conflict is now resolved


v4 -> v3 Code Example/Retain Question

I have a question on the Bindings > NSObject example?
To start, let's call the first code example (the one with the print call) Example A.
I don't see why the fact that viewModel outlives the the View Controller means that I need to manually dispose of the observation.
It would seem (under v3 memory conventions, at least) that the closure would be the one responsible for retaining viewModel.name and, presumably, the closure would get autoreleased at the end of viewDidLoad.
I can't figure out how, in this example, viewModel and View Controller memory lifetimes are related, and what, in any of that implementation, requires the manual observation disposal.
Do you think you could offer any guidance on what I might be missing? I'd really appreciate it!

Given that the view model instance outlives the view controller, think of what would happen if you do not dispose the observation. If you do only the following in viewDidLoad:
viewModel.name
      .observe { name in
        print(name)
      }

Everything would still work, but name changes would be printed even when your view controller gets destroyed.
In v3 we had that unfortunate Bond class that was managing binding/observing, keeping it alive as long as the Bond instance is alive.
In v4 everything is changed and observings/bindings are alive until they are disposed. UIKit extensions will automatically dispose bindings when they are destroyed. For example, anything binding to UILabel's bnd_text property will be disposed when that label is destroyed.
That being said, you usually don't want your view models outliving the view controllers. If you stick to that rule, you won't have to worry about disposing observers.

Another way is to look at the method signature. Any observer is registered with following method:
func observe(observer: EventType -> Void) -> DisposableType

The closure we pass in there will stay registered until dispose() is called on the returned disposable.

@srdanrasic Thanks for your helpful reply! That helped a lot to clarify.
Re: your first comment - Sorry, is the call to print in the code example a class method inside the view controller or the Swift Standard Library function (i.e. the old println from Swift 1.2)?
Also, in our app's architecture, our view controllers don't necessarily have knowledge of whether the view model will outlive the view controller. Does this mean we would have to append .disposeIn(bnd_bag) to all view model bindings, in this case?
Re: your second comment - Just to be sure I understand, are you saying the closure that's passed into observer() will be strongly retained by the receiver (i.e. the EventProducer) until dispose() is called?

print is part of Swift 2.0 standard library. println is deprecated.

Also, in our app's architecture, our view controllers don't necessarily have knowledge of whether the view model will outlive the view controller. Does this mean we would have to append .disposeIn(bnd_bag) to all view model bindings, in this case?

You would have to manually dispose observations made with observe method. You would not have to manually dispose bindings established with bindTo method because those are disposed automatically.
I see you understand the observe method correctly:

Just to be sure I understand, are you saying the closure that's passed into observer() will be strongly retained by the receiver (i.e. the EventProducer) until dispose() is called?

That's right.
Method bindTo uses observe internally, but also handles the disposable by attaching it to the passed bindable object so it gets disposed when the bindable is destroyed.
Here is how it works. Anything that conforms to the BindableType can be passed into bindTo method of an Observable (EventProducer). BindableType protocol defines one method that can be used to get a sink (a closure) used to send events to that object. It accepts a Disposable that it should dispose when it's destroyed.
public protocol BindableType {
  typealias Element

  /// Returns a sink that can be used to dispatch events to the receiver.
  /// Can accept a disposable that will be disposed on receiver's deinit.
  func sink(disconnectDisposable: DisposableType?) -> (Element -> ())
}

Now to bindTo method. It receives an object conforming to BindableType protocol. First, it creates a Serial Disposable. It's a disposable that can dispose itself plus some other disposable. Then is gets the sink from the received object passing it the serial disposable at the same time. That means that when the bindable gets destroyed it will also dispose our serial disposable. Next, we register an observer that passes events to the bindable using the given sink and we save the returned disposable as the other disposable of our serial disposable. In effect, observe's disposable will be disposed when the serial disposable gets disposed and as I already said, serial disposable will be disposed when the bindable is destroyed. Finally, serial disposable is returned if you, for some reason, want to cancel binding before the bindable is destroyed.
public extension EventProducerType {
  public func bindTo<B: BindableType where B.Element == EventType>(bindable: B) -> DisposableType {
    let disposable = SerialDisposable(otherDisposable: nil)
    let sink = bindable.sink(disposable)
    disposable.otherDisposable = observe { value in
      sink(value)
    }
    return disposable
  }
}

EventProducer (and so Observable) conforms to BindableType and UIKit extensions are just plain Observables so you get automatic disposing out of the box.
Hope this helps.

Aha! Ok, I get it now!
Thank you so much for the helpful reply and the awesome work with Bond. :)

Closed as outdated.


[hotfix] [docs] Fix broken link to FLINK-7811

This fixes a broken hyperlink on page https://ci.apache.org/projects/flink/flink-docs-release-1.4/start/building.html#scala-versions

merging.


Update awcrt version to 0.19.10

Update to the latest version of the awscrt.

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

Comparison is base (3f645d1) 93.46% compared to head (7cd6fac) 93.37%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3053      +/-   ##
===========================================
- Coverage    93.46%   93.37%   -0.09%
===========================================
  Files           66       66
  Lines        14007    14007
===========================================
- Hits         13091    13079      -12
- Misses         916      928      +12

see 5 files with indirect coverage changes

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


Add ability to send the "typing" event in the outcomes array.

Right now, we can send DM messages back to the user.
But, it would be nice to be able post a "typing" event (indicating that the bot is typing). This gives users comfort, particularly when processing the message might take a little while.
The event structure (from the Slack API docs):
{
"id": 1,
"type": "typing",
"channel": "C024BE91L"
}
So, similar to sending a DM, but just a different JSON structure needs to be sent.

I think it is like:
{ "type" : "user_typing", "channel": "C034RYTR5", "user": "U674BETY" }
The 'user_typing' event is sent to all members of a channel when a user is typing a message in that channel.


WebServer takes controller_prefix

this should be modified to take a list called controller_prefixes so it is consistent with everything else

I've removed all the WebServer stuff in the new ASGI codebase


wkhtmltopdf Exception: QFont::setPixelSize: Pixel size <= 0 (0)

Intermittently when calling an action that uses "ActionAsPdf" Wkhtmltopdf throws an exception "QFont::setPixelSize: Pixel size <= 0 (0)" and stops working.

            ActionAsPdf apdf = new ActionAsPdf("action")
            {
                FileName = Guid.NewGuid().ToString() + ".jpg",
                PageHeight = 630,
                PageWidth = 1200
            };

i always do this but give me this error;
Exception Details: System.Exception: QFont::setPixelSize: Pixel size <= 0 (0)
QPainter::begin(): Returned false
Error: Unable to write to destination
Exit with code 1, due to unknown error.

Is there a way to shrink images with some custom switch?


Guzzle based fetcher

add a guzzle based fetcher, as this is more and more the php worlds primary http lib

Actually I am currently on it.
Implementation will look like/act like the curl version.

it should replace both versions, to keep maintenance low

done by Bavragor in pullrequest #32
thanks


get fatal error

Describe the bug
When i clone the project and run the go run main.go  I got this error
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
main.main()
	/home/azibom/Desktop/go/awesome-cli/main.go:22 +0x2d2
exit status 2

what is the problem?

Hi @azibom ,
Many thanks for the bug report. The new self-update feature causes this problem. I am doing an urgent fix and update you asap.

Hi @azibom ,
Can you please pull and try again?

Hi @umutphp

Hi @umutphp

Hi @umutphp ,  It works right now  Thanks for your supporting and your nice project :))

Many thanks for your support too :)


Graphql starting point merge from nest graphql server

Converted code from https://github.com/icanbwell/graphql-insurance-claims.  Code retro fitted and converted to JS.  Not in any way an ideal or complete implementation of graphql but a starting point to unblock poc project by running this endpoint on fhir server rather than the completed implementation in a standalone server.  Project time boxed and meant as a starting point considerable more work needed to make this production ready.  Scope of time box met here with only one query supported.  This also runs with the intention of not interfering with any current features of fhir server.

Thanks for creating this PR, @michaelrbooth !  Please add unit tests and specify types of parameters/variables.
Here's an example of a unit tetst: https://github.com/icanbwell/fhir-server/tree/master/src/tests/practitioner/graph
And here's an example of specifying parameter and variable types:
https://github.com/icanbwell/fhir-server/blob/313e624e287d9c7501bfe80f0ebcdb4f77bc4667/src/utils/index.util.js#L18
https://github.com/icanbwell/fhir-server/blob/313e624e287d9c7501bfe80f0ebcdb4f77bc4667/src/services/base/base.service.js#L784

@michaelrbooth how does this handle authentication and authorization?

it handles auth the same way as rest requests, just passing through the credentials and having that code provide the same functionality as a REST request


enable kryptowire scanning on the master branch

Motivation
Enable kryptowire binary scanning
Description
Push the release binary to kryptowire on the master branch
Progress

[x] Done Task

ping @danielpassos mind taking a look?


introduce typescript, tsx, jsx support to LSP server using babel parser, with tests

introduces typescript, tsx and jsx support via babel parser plugins
#1263 by @zth is an alternative to solving this problem which also supports reasonml, and potentially other  a non-ast branch by @zth using regular expressions should  be reconsidered.
-tests for typecript and tsx added
getQueryAndRange changed to parseDocument, and made override-able as parse by startServer.

Does this do the same job as https://github.com/Quramy/ts-graphql-plugin?
If yes, are there any usage docs that I can refer to? 🤔

yes! the only difference now is that it will handle ts/tsx files when you open them. still need to get vscode workspaces configured correctly to read all the embedded graphql

to add, the typescript language plugin is still valuable for a lot of cases.

This looks good to me! This will allow people who want to support other languages than the mainstream ones (like ReasonML for me) to do that through replacing parseDocuments.  👍

@zth last commit here fixes that bug i saw in discord, otherwise looks like everything is working fine! I've had some issues with setting up our example extension, but i think i understand what I'm missing after working with yours and @divyenduz 's more carefully.


strict-type-predicates: false positive for mapped template types

Bug Report

TSLint version: 5.9.1
TypeScript version: 2.7.0-dev.20180110
Running TSLint via: (pick one) CLI & VS Code

TypeScript code being linted
const testDeepReadonly = <TThing extends { optional?: string }>(thing: Readonly<TThing>): string => {
	if (thing.optional === undefined) { // [strict-type-predicates]: Expression is always false.
		return "undefined";
	}

	return thing.optional;
};

with tslint.json configuration:
{
    "rules": {
        "strict-type-predicates": true,
    }
}

Actual behavior
TSLint assumes thing.optional is a (concrete?) real type, rather than extending ?: string.
Expected behavior
It shouldn't.
This might be related to #2944 and fixed by #3417. I haven't looked into it much.

feel free to comment if this is still an issue for you and i'll re-open.


Invalid transaction

Steps to reproduce:

Clone repository:
git clone --branch nextjs-typescript https://github.com/austintgriffith/scaffold-eth.git

Start hardhat:
cd scaffold-eth
yarn install
yarn chain

Deploy contracts
cd scaffold-eth
yarn deploy

Start frontend
yarn dev

I have Metamask configured. The frontend works for other methods like "Fetch Greeting" and "Send Funds From Local Hardhat Chain".
When I click the button to set the greeting, I get the error "Invalid transaction".
With a quick troubleshooting I've noticed that the call fails in the following method in `packages/hardhat/node_modules/hardhat/internal/hardhat-network/provider/modules/eth.js:
async _sendRawTransactionAction(rawTx) {
    // We validate that the tx is not legacy nor eip-2930 here
    // because otherwise the catch logic below gets too tricky
    // This can happen because of an EIP-2718 tx that's not EIP-2930,
    // which we don't support, or because the input is just completely invalid
    if (rawTx[0] <= 0x7f && rawTx[0] !== 1) {
        throw new errors_1.InvalidArgumentsError(`Invalid transaction`);
}

The if condition is not satisfied because rawTx[0] is equals to 2.

I checked how _sendRawTransactionAction is called.
The following snippet is the call (I've added the console.log):
case "eth_sendRawTransaction":
    console.log("params:", params);
    console.log("...this._sendRawTransactionParams(params): ", ...this._sendRawTransactionParams(params));
    return this._sendRawTransactionAction(...this._sendRawTransactionParams(params));

params: ['0x02f8d3827a690a8501dcd650008501dcd65000828b22945fbdb2315678afecb367f032d93f642f64180aa380b864a4136862000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000054141414141000000000000000000000000000000000000000000000000000000c080a0e62fd225600888ef78ab8b4eb20609f21b8f37b41076e02f2b01ea61d703aad3a03f14cc7e8a2870b3321142812ad7d773606f87040b89fa56ab2cb4d9aeee6dce']
...this._sendRawTransactionParams(params):  <Buffer 02 f8 d3 82 7a 69 0a 85 01 dc d6 50 00 85 01 dc d6 50 00 82 8b 22 94 5f bd b2 31 56 78 af ec b3 67 f0 32 d9 3f 64 2f 64 18 0a a3 80 b8 64 a4 13 68 62 ... 164 more bytes>
That's why the rawTx is 2.


#31: Add MIT license

sorry for the delay, have been working on other projects! this looks great to me, I don't know anything about licenses but it looks reasonable

sorry for the delay, have been working on other projects! this looks great to me, I don't know anything about licenses but it looks reasonable

Without adding any license you are not allowing others to copy your code (it's your copyrighted work), so it's pretty important to have it in all projects.
Thanks for adding it! 🎉

No problem at all, thanks for the help


Shelly1 temperature addon

Dear friends, is it possible or planned to read out external temperatures?
I'm testing a Shelly 1PM with temperature addon and only get the internal temperature.
Thanks a lot!

Me again... let me clarify my question:
I'm looking for a way to inject the switching thresholds of the temperature automation in the Shelly with the temp.addon.
Reading out is no problem, I found it in ojects, sorry..
Tkanks, again!

Ah ok… so you want to set the thresholds… l will try to implement it.

please check  the example settings.json in the example folder of version 7.2.0

Works fine! Just tested, Thank You!


Add resize of TTY by SIGWINCH signal

Very simple approach to solve https://github.com/calleerlandsson/pick/issues/115, but works here (so far) without any flaws ...

Hi,
I appreciate the effort but I think we should go ahead and solve this is
step by step, your previous PR is a good first step. Please checkout
#213.
As for SIGWINCH, the only place where it should be allowed is during
the first call to read(3) in get_key. This approach will (hopefully)
require less churn. I'm willing to give a try once #213 is in.

OK, another approach (https://github.com/DBOTW/pick/commit/f08d779b6a481de32e8fd3e1f2811c781c1eb2c2) with less "churn" in the source, but breaks most tests ... is using select the "right way" to do it? Any comments/help on this will be very appreciated ...

Nice, I have something similar in my tree. Checkout the sigwinch
branch.

Great! This should definitely be merged!

Can we close this in favor of #213 by now?

Of course!


Feature Request: Add the ability to show date/time on taskbar

It would be great to have the ability to show date and time on the taskbar (with varied configuration options) for users who want to use this app an a complete replacement to the standard clock ... especially ones like who are using explorerpatcher

It's very hard to create any custom button that allows you to display date and time on the taskbar. The goal of my app is to deliver functionality of calendar and agenda.


feat: load package prop when --config is package.json

Closes #79

Done.

Thanks @azz, looks great.
@sudo-suhas: Do you want to merge this now?

When can this feature be released? Thanks!

@calebeby cosmiconfig 3.0, which includes this bug fix, has now been released to npm.

Awesome, thank you so much!


Add nuget authentication to source index template

The template https://github.com/dotnet/arcade/blob/main/eng/common/templates/job/source-index-stage1.yml is currently not supporting authentication, which now is needed because astra is still private.
This is causing the following error:
System.AggregateException: One or more errors occurred. (Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/internal/_packaging/dotnet-libraries-internal/nuget/v3/index.json.)
D:\a\_work\1\s\artifacts\toolset\restore.proj : error :  ---> NuGet.Protocol.Core.Types.FatalProtocolException: Unable to load the service index for source https://pkgs.dev.azure.com/dnceng/internal/_packaging/dotnet-libraries-internal/nuget/v3/index.json.
D:\a\_work\1\s\artifacts\toolset\restore.proj : error :  ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).

this was reported in teams: https://teams.microsoft.com/l/message/19:afba3d1545dd45d7b79f34c1821f6055@thread.skype/1696011282938?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=4d73664c-9f2f-450d-82a5-c2f02756606d&parentMessageId=1696011282938&teamName=.NET Core Eng Services Partners&channelName=First Responders&createdTime=1696011282938
In order to fix this we need to add nugget authentication: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/nuget-authenticate-v1?view=azure-pipelines&viewFallbackFrom=azure-devops to the template  https://github.com/dotnet/arcade/blob/main/eng/common/templates/job/source-index-stage1.yml
as this is a private repo we need to add source indexing

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

We are still hitting this. Have we made any progress on figuring out what might be causing this?

The root cause is understood. The repo has a feed that requires authentication in their Nuget.config. This is not expected for public .NET repos, so we never hit this when source indexing the other repos.
Thinking about this scenario, do we want to enable it in the first place? I don't think we ever want to source-index private repos, or repositories that are not buildable due to requiring authentication in the nuget.config.

I think we should close this for now. In this particular case it seems like it's a scenario we don't want to enable as it could cause mixed signals if a private repo or a repo that contributors would need to auth against shows up in the source indexer.
If we get another scenario where we need to consider authenticating against private feeds when indexing we could revisit.


added the Minimalist NavBar

Fixes Issue🛠#854

Closes #854
Description👨💻
Added the navbar files to the components folder and updated the html file as well
Type of change📄

[] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How this has been tested✅

Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷
https://github.com/Rakesh9100/Beautiify/assets/137754636/7807f06a-a2d8-4412-9a81-b4b9ef419af3

@Rakesh9100 Done!!
please assign the other issue as well


fix swagger

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

work moved here: https://github.com/hmcts/wa-task-management-api/pull/228