Running exporter as non-root? sudo for calls to smartctl?

I was wondering if it was really necessary to run the whole smartctl_exporter as root. This is even promoted via the provided systemd unit https://github.com/prometheus-community/smartctl_exporter/blob/master/systemd/smartctl_exporter.service
I know smartctl does seem to require this (https://github.com/smartmontools/smartmontools/issues/205).
But maybe there is a way to not require for the exporter to run as root but to just call a privileged smartctl?
Is the good old sudo the right approach? Just by setting smartctl.path to sudo smartctl.path maybe?

You can easily switch various [https://www.redhat.com/sysadmin/systemd-secure-services security features] of the systemd service to see what works and what not. I don't see an advantage in adding another layer with sudo...

Adding sudo to the exporter is not going to happen.
As suggested by @lahwaacz, if you figure out how to configure systemd to improve the security, PRs are welcome!

@frittentheke FYI prometheus-smartctl-exporter.service in AUR
If you can test it, tune it, PR it - it can be part of smartctl_exporter tarball

I see my provocation of creativity by just mentioning sudo worked :-). Thanks for taking the quest to reduce the privileges seriously and let's see if there is something that could work for most installs.

The AUR service unit looks very promising! Unfortunately I am not able to test/pull at this time.
The full documentation of these options can he found here: https://www.freedesktop.org/software/systemd/man/systemd.exec.html
Note that not all distros ship the latest Systemd, so newer options may result in warnings in the journal. However, in my experience it is backward-compatible without issue (you may not get all of the security features but still as many as possible).

I'm looking for a secure way to run the exporter too. These privileges are required for smartctl:

CAP_SYS_RAWIO capability to be able to access raw devices;
disk user group, which owns all the disks.

So you can add these lines to the systemd unit:
[Service]
...
CapabilityBoundingSet=CAP_SYS_RAWIO
AmbientCapabilities=CAP_SYS_RAWIO
Group=disk
...

But this set of privileges may lead to privilege escalation since root filesystem is accessible for writing. So sudo with limiting sudoers configuration still looks more secure.


puppet: statuspage-pusher uses zulip.conf for page_id.

This was changed midway through the implementation, from reading it from zulip-secrets.conf, and a couple locations still reference the secrets path.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Merged, thanks for cleaning this up @alexmv!


elaborate one solution to "how to go_to_definition in new split window"

with helps of @mjlbach in gitter, I figured out the following solution;
then he suggested i add it to the nvim-lspconfig's wiki, as i am not a native english speaker, and the code seems not fine, i hestated to do it;
so i just put it in here
local function goto_definition(split_cmd)
  local util = vim.lsp.util
  local log = require("vim.lsp.log")
  local api = vim.api

  local handler = function(_, method, result)
    -- stolen from $VIMRUNTIME/lua/vim/lsp/callbacks.lua

    if result == nil or vim.tbl_isempty(result) then
      local _ = log.info() and log.info(method, "No location found")
      return nil
    end

    if split_cmd then
      vim.cmd(split_cmd)
    end

    if vim.tbl_islist(result) then
      util.jump_to_location(result[1])

      if #result > 1 then
        util.set_qflist(util.locations_to_items(result))
        api.nvim_command("copen")
        api.nvim_command("wincmd p")
      end
    else
      util.jump_to_location(result)
    end
  end

  return handler
end

vim.lsp.handlers["textDocument/definition"] = goto_definition('split')

Thanks! I added it to the wiki.

@mjlbach This was working fine all along until I updated to the latest nightly and it no longer works.
Any thoughts on what might have changed?  It looks like the custom handler is not getting invoked at all.
Thanks.

Probably this:

https://github.com/neovim/neovim/pull/30982

Thank you, that seems like it.
Not sure if there is a fix needed in lspconfig to handle this change, or if I should rework how I'm using this.
Previously I was setting handlers:
local handlers = {
    ["textDocument/definition"] = goto_definition('split'),
}

and passing handlers into require('lspconfig').SERVER.setup()

I think what you actually what is to use the default "jump to definition" mappings. So in nightly, tagfunc is set to to vim.lsp.tagfunc. So you should just be able to use <c-]> to jump to definition, or <c-w><c-]> to jump to definition in a split. See :help CTRL-] and :help CTRL-W_].
Otherwise your best bet is probably to create your own vim.lsp.buf.definition() function. Wrap it. Or see if there's anything you can do with vim.lsp.buf.definition({ on_list = function(opts) ... end }).

See :help 'splitright' and :help 'splitbelow' as well.


chore(writing-a-loader): added data sharing details

describe your changes...
Added detailed explanation about how to share data among loaders in writing-a-loader section

cc @montogeek I made those changes you suggested 👍

Agree that formatting is not necessary, only format violations or clear mistakes (trailing spaces, double quotes in js etc). Additions of newlines or adding trailing commas to snippets is not necessary and only adds overhead in reviewing.
I suggest we simplify the addition into single paragraph of text, i couldnt see second way of doing it even though it stated there are two ways to pass data, please see suggesting and tell me WDYT

I guess I forgot to remove those two ways !! initially I added two ways , the other one was using pitch method. But it seems that's not the ideal recommended way!
I will make those changes you suggested :


Remove assert from google change in resp

Google seems to have changed the response header
removing the assert seems to unbreak the library
Would like to see what they are sending now

going to ignore the test for now as I think it's related to #83 which has to be resolved by refreshing the auth token


Added Mancy

The 32 bit version is broken just now because one of the JS files isn't packaged.

Interesting!


Disambiguate CREATE ROLE ... USER and GROUP

Rather than assume ROLE and USER are synonyms in the parser, let's parse them separately and allow upstream crates to treat them the same if they desire
Per comment https://github.com/sqlparser-rs/sqlparser-rs/pull/598/files#r981277941 on contribution from @blx

cc @blx

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

27 of 40 (67.5%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 85.501%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tests/sqlparser_postgres.rs
11
12
91.67%

src/ast/mod.rs
4
6
66.67%

src/parser.rs
12
22
54.55%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
10102

Relevant Lines:
11815

💛  - Coveralls


Boot a verified rootfs image via dm-verity

This changes the rootfs to a verity image.
https://docs.kernel.org/admin-guide/device-mapper/verity.html
The verity root hash is added to the ramdisk and checked at boot time when mouting the rootfs. The rootfs will be mounted and the system will boot only if the hash in the ramdisk matches the root hash from the verity image.
Built and runtime tested on Verdin iMX8MP, Colibri iMX6, Colibri iMX7 and Verdin AM62.

@rborn-tx @jsrc27 this is ready to be reviewed, but I marked as a draft because it depends on a couple of changes on the BSP side.
You can review, but please don't merge it yet.

LGTM as well.

@rborn-tx @jsrc27 thanl you both for the review.
I will leave this as a draft until the required changes on the BSP are merged. As soon as they are merged, I will merge this one.

@rborn-tx @jsrc27 Since you both already reviewed this, I am merging now.
There were two patches pending at the BSP side.
One of them was about changing the class that generates the Tezi image. This one was merged. See https://git.toradex.com/cgit/meta-toradex-bsp-common.git/commit/?h=kirkstone-6.x.y&id=0513615cb0383d7ac0695e865884897493339d62.
The other one was about adding two layers (meta-security and meta-perl) to the default bblayers.conf file from the BSP. This one was rejected (but still under discussion).
For now, I will just add to the documentation the information about the dependencies. I am working on the documentation and will submit another PR soon.


How to make plain_text_input field as read only

Description
Describe your issue here.
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x ] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x ] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:
Please let us know is there a way to make plain_text_input field as read only
Expected result:
What you expected to happen
Actual result:
What actually happened
Attachments:
Logs, screenshots, screencast, sample project, funny gif, etc.

Any news about this feature request?


[Feature] Make storeValue synchronous by evaluating the updateStored immediately

Description
Store Value is an async function today but people generally think of it as a synchronous function. There is also no callback to this function and introducing one would muddle the function signature. The correct solve seems to be to provide an evaluated data tree once a synchronous action that manipulates the data tree such as storeValue is executed

@Nikhil-Nandagopal should we be allowing an option to keep this async as well? All functions should be able to run async if we are to not hit performance issues in the future.

I suggest a wrapper function that takes a list of functions as parameters and executes them in sequence. This would allow for a flexible solution where needed while keeping the async by default paradigm.

Hey guys, thanks for weighing in here. I just wanted to clarify that all code executed is always done so asynchronously from the UI so that we never hang the UI. This is just about making the storeValue synchronous in that context so it's easier to write
{{ storeValue("key", "value"); showAlert(appsmith.store.key); }} Rather than having to chain these values. They will be executed asynchronously as a whole but synchronously relative to each other :)

If you have multiple widgets subscribing and you're using it as a parameter for an api you can quickly get situations with inconsistent data being displayed.
The current approach is okay for simple uses but limits the usefulness of the store quite severely.
Took me 3 days of active use before I stumbled upon a couple of edge cases.

Hey @thebf ,
I understand the problem you're facing. The solution I'm proposing is to allow the following code to execute correctly
{{ storeValue("key", "value"); API1.run(); }}

where API1 is reading a value from the store and is still receiving a consistent value. Could you point out where you see this would limit the usefulness? This code is executed entirely asynchronously but API.run is executed synchronously after storeValue. Basically, the entire binding is executed async but the API is run only after storeValue completes.

I misread at first, that would be a good solution.


Fix module in msg of type_check

Jenkins, test this please 🙇

Related:  #7795

Jenkins CI test (for commit 1fa8d8f84cb0223a1f77bc8eb1138c42de8f0f28, target branch master) failed with status FAILURE.

LGTM


Move reviews from core into local

WIP - see PR in core for progress

Cheers - those are done.
That just leaves the outstanding questions from the core PR.

Should be all those changes done


python312Packages.faraday-plugins: 1.18.2 -> 1.19.0

Diff: https://github.com/infobyte/faraday_plugins/compare/refs/tags/1.18.2...1.19.0
Changelog: https://github.com/infobyte/faraday_plugins/releases/tag/1.19.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

8 packages built:

faraday-agent-dispatcher
faraday-agent-dispatcher.dist
faraday-cli
faraday-cli.dist
python311Packages.faraday-plugins
python311Packages.faraday-plugins.dist
python312Packages.faraday-plugins
python312Packages.faraday-plugins.dist


Creating secure note object fails due to required password field

Your environment

Terraform Provider Version: v2.0.0

Connect Server Version: 1.7.2

CLI Version: 2.30.0

OS: Pop!_OS 22.04 LTS

Terraform Version:
Terraform v1.9.4
on linux_amd64
+ provider registry.terraform.io/1password/onepassword v2.0.0
+ provider registry.terraform.io/barnabyshearer/dockerhub v0.0.15
+ provider registry.terraform.io/hashicorp/google v5.40.0

What happened?

Attempting to create a secure note generated this error message:
│ Error: Provider returned invalid result object after apply
│
│ After the apply operation, the provider still indicated an unknown value for
│ onepassword_item.devtokens.password. All values must be known after apply, so
│ this is always a bug in the provider and should be reported in the provider's
│ own repository. Terraform will still save the other known object values in
│ the state.

Then when I added a password field, I got a second error:
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to onepassword_item.devtokens, provider
│ "provider[\"registry.terraform.io/1password/onepassword\"]" produced an
│ unexpected new value: .section[0].field[0].type: was cty.StringVal("string"),
│ but now cty.StringVal("STRING").
│
│ This is a bug in the provider, which should be reported in the provider's own
│ issue tracker.

What did you expect to happen?

I expected a secure note to be created without a password field, and I expected the provider to either internally translate the case of the type or to use an enum to validate acceptable type values.
I also sort of expected the "required" password field to appear in the created item, but there is no password field after it's created.  I'm ok with that, though. ;)
Steps to reproduce

Try to create a secure_note item without a password field
Observe error
Add a placeholder password field
Observe that "type = string" in the field is a new error
upper-case the type to STRING
Observe that the created resource does not have a password field even though the provider insists that field is required

resource "onepassword_item" "devtokens" {
  vault = var.op_automation_vault

  title    = "developer tokens"
  category = "secure_note"
  section {
    label = "dev_tokens"
    field {
      label = "a field"
      type  = "string"
      value = "a value"
    }
  }
}

Notes & Logs

I suppose this is technically two separate bugs.

Hey @dannysauer! 👋🏻
What you might be experiencing when it comes the the feeling of the password being required is the bug at #173. This has been solved in the version 2.1.0, which is also the latest version of the provider.
As for the second element that you've identified, that is indeed a bug. A quick mitigation for it is, as you've mentioned, changing the type to STRING. Thank you for catching this. 😄

Oh, that's awesome!  Sounds like I have a bug in the Renovate config which is supposed to be updating the 1password provider in my Terraform. :D

Confirmed that deleting the item and recreating without a password field works for me with the new provider.  Though, I ran into #97 in the process, so had to delete the item from the state before recreating. ;)
Thanks, @edif2008.  Should I open a new bug for the case sensitivity thing, or retitle this one?

To keep it clean and clear, I think it might be better to to open a new issue, since this one started off as not being able to create a Secure Note item without a password and in the process the additional bug was found.
Once you make that new issue, I will close this one.
Thank you again for your great cooperation and providing valuable feedback to further improve the Terraform provider. 😄


Added SBOM Generator tool to pipeline

Cyber EO SBOM :
Pipelines that publish things to production need to be able to generate SBOM.
Details: https://microsoft.sharepoint.com/:w:/t/USEOonImprovingCybersecurity/EduvCsx46t5EpcL2F8ApnwMBCn8yiHZeOsWiWNs2B_s-lQ?e=aOlXoA

/azp run


crown beside top user in ulist

yw

These things are perfect ideas for plugins

These things are perfect ideas for plugins

there too many plugins

These things are perfect ideas for plugins

there too many plugins

no such thing

These things are perfect ideas for plugins

there too many plugins

no such thing

yes there is and this isnt big enough to make a plugin


Docker support

[x] Create a Dockerfile

[x] Create github action to build and push image to dockerhub (see comment thread for approach)

@scheung38 - api develop docker image available as gsscogs/linked-data-repository:develop
all it does currently is serve "hello world" at port :3000


[FEATURE] Embed downloadable binaries at compile time

Is your feature request related to a problem? Please describe.
It is not a problem, but just an idea I had. Imagine you custom build goshs  and provide binaries in a folder called files for example. Now every file in there will be compiled and shipped with the binary. So now when starting goshs you have a route like /files for example and then you can find your embedded files there.
Describe the solution you'd like

Implement feature backend
Implement feature frontend

This would need a new "container" to show the embedded content
This could be false by default and just be shown with a flag for example

Describe alternatives you've considered
N/A
Additional context
I had the idea when watching IppSec's most recent video. He was using chisel and needed to ship it to the target. So I thought wouldn't it be nice to just start goshs and have that binary embedded. That would save some time, because you will not need to copy the file from somewhere to somewhere and then start a web server. On the other hand you would need to rebuild goshs any time you want to add or update a tool.

Has been implemented


POC: add support for IntegrationTestScenario v2alpha1

Add v2alpha1 as storage version
Add ResolverRef with Resolver(String) and Params([]v2alpha1.PipelineParameter, use v2alpha1.PipelineParameter as a workaround because an issue of using Params([]tektonv1beta1.Param) has not been fixed, see unittest https://github.com/redhat-appstudio/integration-service/actions/runs/4602777005/jobs/8132117159?pr=139#step:18:56 in https://github.com/redhat-appstudio/integration-service/pull/139) under IntegrationTestScenario.Spec
Add webhook and conversion to convert between different versions
Update the api version to v2alpha1 in controller and files

Codecov Report
Patch coverage: 48.27% and project coverage change: -0.48 :warning:

Comparison is base (ecadc8d) 71.68% compared to head (ac59e1a) 71.20%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   71.68%   71.20%   -0.48%
==========================================
  Files          25       29       +4
  Lines        2320     2358      +38
==========================================
+ Hits         1663     1679      +16
- Misses        503      526      +23
+ Partials      154      153       -1

Impacted Files
Coverage Δ

api/v1alpha1/integrationtestscenario_conversion.go
0.00% <0.00%> (ø)

api/v2alpha1/integrationtestscenario_conversion.go
0.00% <0.00%> (ø)

api/v2alpha1/integrationtestscenario_webhook.go
0.00% <0.00%> (ø)

helpers/integration.go
70.00% <66.66%> (ø)

api/v2alpha1/integrationtestscenario_types.go
100.00% <100.00%> (ø)

controllers/pipeline/cache.go
100.00% <100.00%> (ø)

controllers/pipeline/pipeline_adapter.go
63.58% <100.00%> (ø)

controllers/scenario/scenario_adapter.go
72.34% <100.00%> (+6.78%)
:arrow_up:

controllers/scenario/scenario_controller.go
89.13% <100.00%> (+10.86%)
:arrow_up:

controllers/snapshot/snapshot_adapter.go
54.48% <100.00%> (-4.32%)
:arrow_down:

... and 1 more

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Rule is missing dependency declarations for the following files included by 'flatbuffers/src/flatc_main.cpp':

Dear all,
On my Google Coral device. I am facing the problem in building up the CPP packages.
When I compile with the following command, I faced the following logs errors.
bazel build --sandbox_debug --subcommands --experimental_repo_remote_exec --compilation_mode=opt --define darwinn_portable=1 --action_env PYTHON_BIN_PATH=/usr/bin/python3 --cpu=k8 --embed_label='TENSORFLOW_COMMIT=f394a768719a55b5c351ed1ecab2ec6f16f99dd4' --stamp --crosstool_top=@crosstool//:toolchains --compiler=gcc //tflite/public:libedgetpu_direct_all.so
Could you let me know, what possibile go wrong ?
 ERROR: /root/.cache/bazel/_bazel_root/9433fbfc721f4a1cbf318e36d08e72c4/external/flatbuffers/src/BUILD:40:11: undeclared inclusion(s) in rule '@flatbuffers//src:flatc':
this rule is missing dependency declarations for the following files included by 'flatbuffers/src/flatc_main.cpp':
  '/usr/lib/gcc/aarch64-linux-gnu/10/include/stddef.h'
  '/usr/lib/gcc/aarch64-linux-gnu/10/include/stdarg.h'
  '/usr/lib/gcc/aarch64-linux-gnu/10/include/stdint.h'
1606495016.102742809: src/main/tools/linux-sandbox.cc:152: calling pipe(2)...
1606495016.103021967: src/main/tools/linux-sandbox.cc:171: calling clone(2)...
1606495016.104219364: src/main/tools/linux-sandbox.cc:180: linux-sandbox-pid1 has PID 26445
1606495016.104645223: src/main/tools/linux-sandbox-pid1.cc:434: Pid1Main started
1606495016.105035537: src/main/tools/linux-sandbox.cc:197: done manipulating pipes
1606495016.106281030: src/main/tools/linux-sandbox-pid1.cc:176: working dir: /root/.cache/bazel/_bazel_root/9433fbfc721f4a1cbf318e36d08e72c4/sandbox/linux-sandbox/7/execroot/libedgetpu
1606495016.106442717: src/main/tools/linux-sandbox-pid1.cc:208: writable: /root/.cache/bazel/_bazel_root/9433fbfc721f4a1cbf318e36d08e72c4/sandbox/linux-sandbox/7/execroot/libedgetpu
1606495016.106493352: src/main/tools/linux-sandbox-pid1.cc:208: writable: /tmp
1606495016.106530588: src/main/tools/linux-sandbox-pid1.cc:208: writable: /dev/shm
1606495016.106884676: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /
1606495016.106953062: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /dev
1606495016.106998658: src/main/tools/linux-sandbox-pid1.cc:279: remount rw: /dev/shm
1606495016.107035653: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /dev/pts
1606495016.107070053: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /dev/hugepages
1606495016.107104474: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /dev/mqueue
1606495016.107141334: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys
1606495016.107180005: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/kernel/security
1606495016.107229045: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup
1606495016.107277721: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/unified
1606495016.107324331: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/systemd
1606495016.107370886: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/cpuset
1606495016.107411457: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/net_cls,net_prio
1606495016.107451942: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/freezer
1606495016.107618904: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/memory
1606495016.107674390: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/hugetlb
1606495016.107717970: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/cpu,cpuacct
1606495016.107762801: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/blkio
1606495016.107805441: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/devices
1606495016.107848056: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/pids
1606495016.107900687: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/fs/cgroup/perf_event
1606495016.107946207: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/kernel/debug
1606495016.107987598: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /sys/kernel/config
1606495016.108024938: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /proc
1606495016.108061894: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /run
1606495016.108104854: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /run/lock
1606495016.108143054: src/main/tools/linux-sandbox-pid1.cc:279: remount ro: /run/user/0
1606495016.108212115: src/main/tools/linux-sandbox-pid1.cc:279: remount rw: /root/.cache/bazel/_bazel_root/9433fbfc721f4a1cbf318e36d08e72c4/sandbox/linux-sandbox/7/execroot/libedgetpu
1606495016.108258786: src/main/tools/linux-sandbox-pid1.cc:279: remount rw: /root/.cache/bazel/_bazel_root/9433fbfc721f4a1cbf318e36d08e72c4/sandbox/linux-sandbox/7/execroot/libedgetpu
1606495016.108295021: src/main/tools/linux-sandbox-pid1.cc:279: remount rw: /tmp
1606495016.108327936: src/main/tools/linux-sandbox-pid1.cc:279: remount rw: /dev/shm
1606495016.108471473: src/main/tools/linux-sandbox-pid1.cc:363: calling fork...
1606495016.109281946: src/main/tools/linux-sandbox-pid1.cc:393: child started with PID 2
1606495037.652245081: src/main/tools/linux-sandbox-pid1.cc:410: wait returned pid=2, status=0x00
1606495037.652407947: src/main/tools/linux-sandbox-pid1.cc:428: child exited normally with code 0
1606495037.702402378: src/main/tools/linux-sandbox.cc:233: child exited normally with code 0
Target //tflite/public:libedgetpu_direct_all.so failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 23.925s, Critical Path: 22.02s
INFO: 7 processes: 7 internal.
FAILED: Build did NOT complete successfully
make: *** [Makefile:97: libedgetpu-direct] Error 1

Thank you
Kind Regards
Arun

Hi Namburger,
Following is the environment:
Target processor:
Texas Instruments ARM AM 6548 (+Secure Boot), 2 GB DDR4 RAM
Quad Core processor (AM6548 HS)
2 GB RAM (DDR4)
16GB eMMc
included battery for RTC
preinstalled Simatic Industrial OS 2.0 (incl. License) on the eMMc
OS
It is based on Debian 9 (Long Term Support Kernel)
USB Google coral device is attached with the IOT device.
Kind Regards
Arun

hi again -
Sorry, what I meant to ask was which binary target are you building and on what platform are you building from?
The Makefile that we provided can only be built on an x86_64 machine and it can cross compiles for these architectures.
you may want to use our provided docker image to ensure the environment has all required dependencies:
make DOCKER_IMAGE=debian:buster DOCKER_CPUS="k8 armv7a aarch64" DOCKER_TARGETS=tests docker-build

FYI, this repo is now deprecated in favor of pycoral and libcoral, it can still be made to work, but you'll have to use our egacy runtime package. Just making sure that you are aware of that?

Thanks for the help Namburger.
I will check this once, and will update soon here.

Hi Nam,
I am still doing it,
Could you explan, what is "but you'll have to use our legacy runtime package". Is there disadvantage of using this package over building ourselves?
Also would like to understand "deprecated in favor of pycoral and libcoral," some of my team is using PyCoral, and it works well with EdgeTPU. It means, we should/shouldn't use pycoral?
Could you explan little more on this?
Kind Regards
Arun

Hi Nam,
I am sorry to mix the question with already running one. You may direct me to some link for this.
I need one help in understanding the Google Coral device usages as a commerical product.
Could you point me some reference/document which can help me to understad the software components/packages, dependencies and libraries that require software licensing if we plan to sell it as a companion hardware.
Thank you
Kind Regards
Arun

@arun-kumark Sorry, I mean that this repo is deprecated and you should pursuit pycoral (for python) and libcoral (for c++) intead of this repo entirely. Here is the full release notes: https://coral.ai/news/updates-11-2020

I need one help in understanding the Google Coral device usages as a commerical product.
Could you point me some reference/document which can help me to understad the software components/packages, dependencies and libraries that require software licensing if we plan to sell it as a companion hardware.

@usbguru tag team on this one :)

@arun-kumark
When you buy a Coral device from Google, it is understood you are prototyping or shipping a commercial product.  The primary software libraries you will use are these:
https://github.com/google-coral/pycoral
https://github.com/google-coral/libcoral
https://github.com/google-coral/libedgetpu
https://github.com/tensorflow/tensorflow
Each of these are open source with the Apache 2.0 license.  Your legal team can determine if that license is suitable for your business model.
OpenCV is another library you may want to use: https://github.com/opencv/opencv this uses the Apache 2.0 license.
Gstreamer is another popular library: https://github.com/GStreamer/gstreamer this uses the GPL2 license.

Thank you for listing the packages. I will take it forward with my legal team.
thanks again :)


No private frameworks with iOS SDK 9.3

There is a big problem: With Xcode 7.3 Apple removed all private frameworks from the iOS SDKs, so at the moment BeeTee is not working!
We could embed a previous version of the BluetoothManager.Framework, but this is no long-term solution, because then we are not able to use the a current version of it.
Any other ideas?
Unfortunately, due to my current workload I am not able to work on this issue at the moment. Someone else?

May I ask anywhere to get the previous version of BluetoothManager.Framework?

Could this be fixed by pulling BluetoothManager.framework off of a device?

If you'd be willing to post this as a question on stack overflow, I can give you a detailed answer. Be sure to use the tag 'iphone-privateapi' (as well as 'iOS', of course), and I'll see it. I got it working.

Here you go. :-)

Hi guys!
First of all: thanks to all taking time to write down all these great instructions - but just one question. Is this thing still working in iOS10, or Apple blocked execution of such networks completely? On ios 9.3 on iPhone 5 this thing is working, but on iOS 10 and iPhone 6 for instance, it does not work. I have tracked down where the problem might be:
    // ADDED CODE BELOW
    libHandle = dlopen("/System/Library/PrivateFrameworks/BluetoothManager.framework/BluetoothManager", RTLD_NOW);
    BluetoothManager* bm = [MDBluetoothManager bluetoothManagerSharedInstance];

When bluetoothManagerSharedInstance is called in the iOS9 a message "Connecting to BT server appears". On iOS 10 this never happens. The instance of BluetoothManager is successfully created.

Thank you for your investigations. But I believe it won't work for iOS 10 and newer.

It's still working for me on iOS 10.1.1. iPhone 7.

That's great news! Still the same procedure or did you do something different?

I didn't change anything. Other than updating to the latest iOS SDK and rebuild.

In the new version released today I switched to dynamic loading. So

no header copying
more stability over all iOS versions (including iOS 10 (tested))
cookies for everyone.

The latest code does not work on iOS 10.1.1

Please be more precise: What is not working?
I developed on iOS 10.1.1, so it does work.

Please be more precise @cybertk: What is not working?
I developed on iOS 10.1.1, so it does work.

With the code snippet in README,
beeTee.enableBluetooth() fails to lighten the bluetooth logo in Control Center.
But while I toggle the bluetooth manually, I can get the notification like PowerChanged and ConnectabilityChanged

Thanks for reporting. I think I already know why. I will fix it these days.


How can create a separate server bundle?

This starter is Awesome, really nice work!
My only wish is that the server was packaged in a separate bundle so that I can put some api keys in there. So basically I would have all the separate chunks for client side code and then one bundle for the server - so that I can put sensitive info in there (api keys).
I see that basically the server runs with require('server') in the src/index file and that nodemon is watching it.
I'm trying to wrap my head around how I can use Webpack to do this -
Would I need to start a second instance of webpack for the server  - any ideas or suggestions?

@redlinecodes If you want to optimize the boosting of your web app by server-side bundle, you need to do:

Create server-side webpack config
Adjust script command to access the bundled server-side file in production

There're many resources of SSR bundled that you can find on internet such as this one

@wellyshen - thanks! Again, really nice work - its clean and simple :)

@wellyshen - 1 more quick question. Is the /src/tools/webpack/hooks.js file - is that all the css processing for the server side? All that would need to be included in a webpack config for a server-side bundle?

@redlinecodes It's assets runtime bundler for SSR. I think them already in the webpack config. If you bundle SSR for production. You can skip the hook.js by env.


feat: Add deps.includeSourcemap

This option allows to control if inline source maps should be included in dependencies. This is useful when debugging inline dependencies. It was discussed in https://github.com/vitest-dev/vitest/pull/6041#discussion_r1668253799
To get correct line numbers you need to specify dependencies you wish to debug in deps.includeSourcemap and configure outFiles in .vscode/launch.json like this:
 {
   // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
   "version": "0.2.0",
   "configurations": [
     {
       "type": "node",
       "request": "launch",
       // ...
       "outFiles": [
         "${workspaceFolder}/**/*.(m|c|)js",
         "!**/node_modules/**",
+        "${workspaceFolder}/node_modules/**/date-fns/**/*.js"
       ]
     }
   ]
 }

fixes #5605
Description

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
[x] Ideally, include a test that fails without this PR but passes with it.
[x] Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

[x] Run the tests with pnpm test:ci.

Documentation

[x] If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

[x] Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

I don't believe this PR will be necessary once https://github.com/vitejs/vite/pull/19004 is merged. The problem was upstream (in Vite), where the SSR transform was not preserving the line offset of the original code. When the line offset is preserved, you don't need a sourcemap, since the SSR transform doesn't indent anything (which means the column offset is unaffected).

You're probably right @aleclarson! Thanks for looking into it.
I'll keep this PR open but as a draft just in case for some reason yours won't be merged or for some reason won't fix #5605 :)

Hey @bgoscinski, to be clear, my Vite PR absolutely fixes #5605. I tested with your reproduction 😄

Oh perfect! I'll take your word for it then :)


Bug Report

Hello !
I've installed the mod, bur ther rises an error launching the program (mod not working)
The error is :
[Message:   BepInEx] BepInEx <IP_ADDRESS> - DSPGAME
[Info   :   BepInEx] Running under Unity v2<IP_ADDRESS>89476
[Info   :   BepInEx] CLR runtime version: 2.0.50727.1433
[Info   :   BepInEx] Supports SRE: True
[Info   :   BepInEx] System platform: Bits64, Windows
[Message:   BepInEx] Preloader started
[Info   :   BepInEx] Loaded 1 patcher method from [DSPInfiniteResourceNodes <IP_ADDRESS>]
[Info   :   BepInEx] 2 patcher plugins loaded
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Info   :   BepInEx] Patching [Assembly-CSharp] with [DSPInfiniteResourceNodes.DSPInfiniteResourceNodes]
[Info   :DSP Infinite Resource Nodes] Infinite resources patch applied for miners.
[Info   :DSP Infinite Resource Nodes] IL_0532: ldloc.s V_24
[Info   :DSP Infinite Resource Nodes] IL_05e1: ldloc.s V_24
[Info   :DSP Infinite Resource Nodes] IL_0603: ldloc.s V_24
[Error  :DSP Infinite Resource Nodes] ERROR: The Dyson Sphere Program appears to have been updated.  The Infinite Resource Nodes mod needs to be updated.  Until then Icarus will consume node resources.
[Message:   BepInEx] Preloader finished
[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 0 plugins to load
[Message:   BepInEx] Chainloader startup complete
Result is :
Ore ressources running out, saw this on : stonec, copper
Are u able to send a helpful answer or correct this issue ?
Best regards and thank's for help
Norbert

@Nosta54 Thank you for the report.  I'll get on it right now.

@Nosta54 Looks like this issue is only impacting Icarus.  The miners aren't consuming resources.  I'll have this fixed today.  I'll implement a more robust solution that is less prone to game updates.

@Nosta54 Issue fixed in release v1.1.0.  This fix should also be less susceptible to breaking when the game updates in the future.  I've also added something to make it easier for me to monitor for breakages while I'm in a mode where I want to consume resources so I can find out about this type of issue sooner.  Thank you again for bringing this to my attention.

Hello,
I,ve updated to the new version.
I thank you very much for correcting this 'bug ( *gg )
thanks for the very nice work.
have a nice weekend
greetings from
Germany
Norbert
-----Ursprüngliche Mitteilung-----
Von: GreyHak @.>
An: GreyHak/dsp-infinite-resource-nodes @.>
Cc: Nosta54 @.>; Mention @.>
Verschickt: Fr, 19. Mrz 2021 21:16
Betreff: Re: [GreyHak/dsp-infinite-resource-nodes] Bug Report (#1)
@Nosta54 Issue fixed in release v1.1.0. This fix should also be less susceptible to breaking when the game updates in the future. I've also added something to make it easier for me to monitor for breakages while I'm in a mode where I want to consume resources so I can find out about this type of issue sooner. Thank you again for bringing this to my attention.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Redis support in caching layer

We recently introduced Memcache as a cache backend for the API. We decided to use the MemJS  library because this is the only option supporting SASL authentication, that's a requirement when using Heroku add-ons.
Unfortunately, we had an outage this week that was linked to MemJS and we lost confidence in it.
We would like to open our options and add support for Redis in our caching abstraction library (together with Memcache and LRUCache).
This will be tested then evaluated. At some point, we'll eventually set it as the default in production.

Completed!


Fix SugarSS Editing Error

Why

There was some test code in the syntax file that was causing an error
when a user began editing a SugarSS file.

This change addresses the need by

Removing the offending test code.
Issue #1

Thank you! 😄

You're welcome, just glad it was an easy change :smile:


Is this library can work on "older API"?

API Level 18 (Android 4.3, JELLY_BEAN_MR2) or later. If your app targets older Android, you should add below line to AndroidManifest.xml:
<!-- Only supports API >= 18 -->
<uses-sdk tools:overrideLibrary="net.ypresto.androidtranscoder" />

, for which this line?

minSdkVersion in your build.gradle is lower than 18, you should add uses-sdk line to suppress build error.
But even if you add this line, android-transcoder cannot run on older Androids.
You should wrap transcode code as below:
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN_MR2) {
  // run android-transcoder here.
} else {
  // show error message or etc.
}


Follow symlinks?

Just recently discovered igrep and it scratches one of my itches that was very hard to get rid of for me. Thanks for making this.
I was wondering if you'd be willing to add -L/--follow option that allows to follow symlinks; currently the dir symlinks aren't searchable if pointing outside of the searched directory subtree.

Sure thing, it will be available in a next release.

That's great, thanks a lot!


Documentation and examples suggestions

As a continuation of the conversation under this stackoverflow topic I'd like to suggest some improvements to documentation and examples.
1

A couple of complete basic sample apps (separate from the existing examples) that implement the method A and method B in their simplest form, without headers, animations, fast scroller etc.
(these should be given separate sample apps or implementation tutorials)

2

Finish the examples Simple item selection, SINGLE selection mode and How to use.

The XML samples contain some inconsistencies, while the Java code is not sufficient to implement the item selection or single selection fully.
There are small indications of what methods need to be used in text descriptions, yet Java code would be much easier to pick up.
Without displaying code for the whole application, these first-step tutorials should cover all code necessary to implement Flexible Adapter in its simplest form, without needing to refer to example apps.
I suggest going step by step by the tutorials starting from an empty activity, seeing where it leads to and what's missing to have a working product.

3

A guide to what needs to inherit what.
Fact that the model used by FlexibleAdapter is containing a ViewHolder is a significant change to how normal RecyclerView.Adapter works (where ViewHolder and model are separate entities) and should be outlined in detail.
Also the Item Interfaces are not documented at all, whilst the classes are expected to implement them.

4

Create library's API reference.

5

The current example app could use refactoring. I understand its purpose of demonstrating various functionalities of the library, yet they are so heavily intertwined that it requires extensive study to distinguish which code is responsible for which feature.
One of the most apparent examples is the SimpleItem.
From reading the code I'm guessing it is used to demonstrate the following functionalities: serialisation, being draggable, swipeable, expandable, searchable, animation, filters, flip view (which also isn't mentioned anywhere in docs), handles, and containing the ViewHolder. That last thing was the only piece of information I was looking for, and I assume is the only required information from that list that would help to get started, while every thing else seems like an extra.
Also there seem to be inconsistencies here too, where for instance SimpleItem suggests to extend directly from AbstractFlexibleItem, yet iteslf extends from AbstractModelItem. Surely, digging through you can see the first in turn extends the second, yet that's not very consistent there.

6

Proofreading

Most importantly - I'm very positive about this project, I think it's great! Exactly because it is such a great library it is even more unlucky it lacks a good documentation. It does contain a ton of very useful code, simplifying and extending the RecyclerView. Linking the ViewHolder and the model seems like a great idea. Nonetheless, I gave up after a day of working around the example app and sparse docs to get simplest selection working, though it surely may be my deductive skills being below average.
Whilst the code seems to provide a great functionality, lack of supporting documentation may hide it from a far greater bunch of devs using it in their apps - and they should use it!

Hi @Voyz, what a long message :-) it means that you really want to help, I appreciate it.
Before I reply on the single points, please keep in mind that, in general, I had few time in the previous months, but I will try to modify the demo App, to make the code clearer to understand also for a newbie in Android. However, all these changes will take some months, because I am the only one working on it. Consider that 4 months ago the demo app was only a single activity. Then, lib grew and I decided to keep what I already had adding some fragments... I believe it is much better now.
But I also agree that now, the examples are too much linked each other's, that leads to a confusion for a person not familiar with Android (it's always difficult to read the code of others by the way).
Point 1) I agree, but instead of making 2 new separated apps to maintain, install and present around, I would prefer to keep the idea of the separating the examples in the same App, maybe 2-3 activities, but this time, independent from all the rest.
Point 2) I'm sorry that you commented the version 4.2 for the single selection. That part in the Wiki is well separated from 5.0 and I do not maintain it anymore. I'm focusing on the new version (I will remove 4.2 pages, when the new part is ready, I can't now).
If you check better I already started to update and add the new wiki pages for version 5.0. However your remarks for the Selection Tutorial will be taken into account when I will rewrite it.
Point 3-4) You will not believe but in these days I was thinking to that.
Point 5) It is linked to the point 1.

I will try to make fragments more independent from the activity.
FlipView is my other library, everything is in that project.
The reason why SimpleItem extends AbstractModelItem is because I use the same object for multiple examples, so maybe I will create more items dedicated only for a single example, the reason is also written in the comment of the classes.
Selection was clear and well easy to understand in the code with versions prior to 5, only because there were only 3-5 functionalities. Now, it is still simple, but it is not well visible as you suggested.

As your last consideration, I would like this library becomes a central reference for the Adapter for many developers, unfortunately I have few time to dedicate and to reorganize the code in such way. However, I don't give up, a step by step I will do it.

Hey @davideas, thanks for your reply. It all seems I've joined in to the situation in an unlucky moment of transition between 4.x and 5.x. I understand your library has grown very quick which is great, and naturally needs time to get everything documented. I'm glad you agreed with me on some points and explained some of my questions. As for particular points:

Either way in fact, as long as the app demonstrates a basic implementation it should be a great starting point. In fact, it seems that Method A is sort of the way to go for FlexibleAdapter since 5.x, why not deprecate Method B entirely? And this way one example app will be even more specific and easy to understand.

Sure, I understand. I'd suggest maybe removing the misleading examples and wiki sections in that case. It's probably better to be left out with no information than with incorrect information.

Great

Great!

Once again, it all makes sense, I know the feeling of pushing the library forward, sometimes it gets a little out of hand. It's certainly good to have the examples of all the functionalities. Maybe once understanding the basics, the all-in-one example app is not that difficult to go through in order to learn the advanced features, yet like we noticed, the simple use case is not quite visible.

Best of luck and thanks for replying. If you come up with some simpler examples and more thorough tutorials I'd be happy to give them a test and give you feedback if you'd like that.

@Voyz, I started to review the documentation entirely, what do you think? :-)

@davideas Hey mate, sorry for a delay, been away for a while.
The new documentation is a big step forward, well done!

I think name ViewHolder is easily clashing with the RecyclerView.ViewHolder if import android.support.v7.widget.RecyclerView; is present. I changed it to MyViewHolder to make it non-ambiguous and the generic name to VH.
VH generic is required to extend RecyclerView.ViewHolder, which implies following class declaration
public class Item<VH extends Item.MyViewHolder> extends AbstractFlexibleItem<VH>

But then, VH passed as a generic type of the Item class can not be instantiated in createViewHolder function:
@Override
public VH createViewHolder(FlexibleAdapter adapter, LayoutInflater inflater,
                                   ViewGroup parent) {
    return new VH(inflater.inflate(getLayoutRes(), parent, false), adapter);
}

which required casting MyViewHodler to VH like so
@Override
public VH createViewHolder(FlexibleAdapter adapter, LayoutInflater inflater,
                           ViewGroup parent) {
    return (VH) new MyViewHolder(inflater.inflate(getLayoutRes(), parent, false), adapter);
}

Why is MyViewHolder passed on as a generic type anyway? Wouldn't it be easier to just declare item as follows:
public class Item extends AbstractFlexibleItem<Item.MyViewHolder>

I've modified the wiki page to reflect these changes along with a little more information to get started.

Hi @Voyz, thanks for the modifications, I've adapted a little, to have initialization explanation at the top.
regarding

@davideas Great! I'm glad I could help, I think the setting up page gives a clear indication on getting started

The XML samples contain some inconsistencies, while the Java code is not sufficient to implement the item selection or single selection fully.

That's really true. Since yesterday i am trying to import to my own project the instagram header sample and yet i could not finish it.
I am almost giving up to trying to use this library. I just want one feature that is the header stick in recycler view, but the sample project has a lot of stuff.
One of the main reasons that i could not do it, is the use of  "samples.flexibleadapter.R" library that is auto generated (i dont know how to do that kind of class in my own project) in ProgressItem, InstagramItem, InstagramHeaderItem.

@7robertodantas, at the beginning of the review it might appear complex, Let me show you how is designed the demoApp (in the wiki there's a page dedicated to it).

We have the MainActivity which extends most of the listeners from the Adapter like clicks, undo and updates (etc.), the Activity also supports the ActionMode for multi selection. The instance of the Adapter is also received from the fragments for the current example displayed.
The Fragments represents the single examples (use cases) how the Adapter can be configured and they extend the AbstractFragment for the common functions.
Depends which use case is selected, the list of items are generated at run time using the DatabaseService, and yes, some items are reused in different examples.
Then we have the new ViewPagerActivity for the example of sticky headers with ViewPager.

For sticky headers, you need to prepare the items for Headers (IHeader or AbstractHeaderItem) and the normal item (ISectionable or AbstractSectionableItem)which has the header reference inside, (I suggest the abstract classes). Then you design the layouts for both of these items, which auto generate the R class.
Then you need something to generate these items in a list, that is your "database".
Then you setup the Adapter by passing the copy of that list. The rest of the configuration for sticky headers is in the Wiki page for Headers and Sections and in the fragment.
You only extend the FlexibleAdapter if you need more customization, otherwise you can use it directly.
Consider always that, there are the Wiki pages + the javaDoc of the classes for each method.
Consider also that this version is still in beta and that I'm alone, the wiki has to be completed and reviewed again a bit. If you need specific help, you can open a new issue.

@davideas
Thank you so much!! This last comment was very helpful. Although I have looked at the wiki was still a little confused by some additional complexities of the sample project. But with this simple and straightforward comment I could understand better.

Setting Up section of the Tutorial does not provide complete code to set up project. For example, in the initializing code, the code snippet is provided without context.
// Initialize the RecyclerView and attach the Adapter to it as usual recyclerView.setAdapter(adapter);
Where should the initialization code be placed? How should "recyclerView" be declared? It would really help new users if all the code required to get Flexible Adapter up and running was included. All the user would need to do is copy and paste. Once a user understands the basic functionality and has something up and running, the more complex customizations and usage will start making sense a lot faster.
Thanks for reading this feedback and your work on this library. I hope to be able to use it soon!

@searchy2, I count that the users of this library knows how RecyclerView works, if not they should read more about it, since it is an official component of Android, not mine.

@davideas I did not understand that this library was just an Adapter extension. I thought it was a complete RecyclerView replacement. My mistake!

With RC2 release the Method A has been deprecated and removed from wiki
Many the wiki pages have been reviewed, the remaining will be updated soon.
DemoApp has been revisited a bit, even if the basic architecture remains the same, but considering the period this issue was created, a lot has been done.
PS. However, with RC3 I will try to simply again the examples, adding new ones and completely rewrite the demoApp, it is in the to do list, so I consider closed this issue.


mat-input border thickness is inconsistent

Bug, feature request, or proposal:
Bug
What is the expected behavior?
All mat-input elements have the same bottom border thickness.
What is the current behavior?
Border thickness changes based on position on screen. When multiple input are stacked in a form, some have a thin border, and others have a thick border. Likely a rounding issue.
What are the steps to reproduce?
This issue repros in the official Angular Material example:
https://stackblitz.com/angular/earyoagkgodo?file=app%2Finput-form-example.ts
Resolution: 3840x2160
Windows DPI: 150%
Browser: Chrome
Browser Zoom: 100%
What is the use-case or motivation for changing an existing behavior?
Look & Feel - Consistency
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
I repro on 5.1.1 and 5.2.3. Haven't been able to try other versions.
Is there anything else we should know?
If I change .mat-form-field-underline height to 0.6px, all of the lines have the same thickness.

@mmalerba yes that seems to work.
Although, I noticed that the issue doesn't appear in stackblitz, even without the scale factor fix.
I don't know why...


Syntax  Error unexpected identifier

Syntax not clear from documenation
Description:
When trying to send a command to obs websocket. I get following error. I think my syntax is somehow not ok. But I am not too much into Promises right now. Can u help me? Also it would be nice if u could bring some light on the args that are supported. How does a typical args look like?
Steps to Reproduce the Issue (if applicable):

Install packages and copy code below into a function and execute it.
...
...

Versions Used (if applicable):

obs-websocket-js version: 0.7.0
obs-websocket plugin version: 4.0.0
obs-studio version: 20.0.1
node.js 8.5

Extra Information / Code Samples / etc:
`C:\project\startstop\modules\obs.js:36
obs.send('StartRecording', {args}, callback(err, data)) returns Promise
^^^^^^^
SyntaxError: Unexpected identifier
at createScript (vm.js:74:10)
at Object.runInThisContext (vm.js:116:10)
at Module._compile (module.js:537:28)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Module.require (module.js:517:17)
at require (internal/module.js:11:18)
at Object. (C:\project\startstop\modules\socketio.js:3:11)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Module.require (module.js:517:17)`

I have now figured out that the first command works and sends data back. If I want to Set something I get an error saying UnhandledPromiseRejectionWarning
obs.GetPreviewScene().then(data => {   console.log(data); });
obs.SetCurrentProfile('blumen').then(data => {   console.log(data); });
With this command I want to load profile 'blumen'

Promises are a way to allow something to happen later, out of order.
So in your sample there you'd want something like
obs.send('StartRecording', {})
      .then(function(data) {
            // StartRecording doesn't return any information, but now we know that obswebsocket acknowledged and performed it.
     })
     .catch(function(error) {
            // If there was some kind of error, such as you not being authenticated then this would happen.
    });

async/await are kind of the next generation of promises though. Rather than having to use then and catch you get the option to write more normal looking code.
try {
    let data = await obs.send('StartRecording', {});
    // data would be empty, but the above "waits" until it gets a response.
} catch (error) {
    // Again, this would probably be not authenticated.
}

Also it looks like you were sending {args},
Just want to make sure you recognize that those are what are defined in https://github.com/Palakis/obs-websocket/blob/master/docs/generated/protocol.md#setcurrentscene
So for SetCurrentScene I'd need something like this
obs.send('SetCurrentScene' { 'scene-name': 'scene1' });

Thankyou for your help.
Gesendet mit der GMX iPhone App
Am 18.08.17 um 16:53 schrieb Brendan Hagan

Promises are a way to allow something to happen later, out of order.
So in your sample there you'd want something like
obs.send('StartRecording', {})
      .then(function(data) {
            // StartRecording doesn't return any information, but now we know that obswebsocket acknowledged and performed it.
     })
     .catch(function(error) {
            // If there was some kind of error, such as you not being authenticated then this would happen.
    });

async/await are kind of the next generation of promises though. Rather than having to use then and catch you get the option to write more normal looking code.
try {
    let data = await obs.send('StartRecording', {});
    // data would be empty, but the above "waits" until it gets a response.
} catch (error) {
    // Again, this would probably be not authenticated.
}

--
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub:
https://github.com/haganbmj/obs-websocket-js/issues/67#issuecomment-323375571


Fix minor typos in INSTALLATION.md

Stumbled upon some minor errors in INSTALLATION.md.

Thanks, merged!


add example nb for hf transformers integration

Description
Supersedes #116
Add example notebook for HuggingFace Transformers Integration
❔ This change

[x] adds a new feature
[ ] fixes breaking code
[ ] is cosmetic (refactoring/reformatting)

✔ Pre-merge checklist
Mark which items have been completed:

[x] Refactored code (sourcery)
[x] Tested code locally
[x] Added code to GitHub tests (notebooks, scripts)
[x] Updated GitHub README

🪝 Run the following to both pre-commit hooks and JupyterLab (turn on format on save)

[x] Stripped outputs from notebooks - (nbstripout)
[x] Sorted imports - (isort)
[x] Formatted code - (back)

📄 Update documentation
Coordinate with @normandy7

[ ] Updated content in the docs
[ ] Added to all relevant docs index pages (e.g., Examples, Integrations intro, Model training index)
[ ] Added to examples README

🧪 Test Configuration

OS:
Python version: 3.9.12
Neptune version: 0.16.7
Affected libraries with version:

transformers==4.22.0 datasets==2.5.1 torch==1.12 scipy==1.6.3 scikit-learn==0.24.0

✔ Post-merge checklist
These tasks should be done after the code is merged to main. Create a subtask under the main ClickUp task to have these on your radar and share the subtask here.
Post-merge subtask: (ClickUp/JIRA task name)

[ ] Update relevant blogs with impacted code/functionality (Contact @Patrycja-J for the list of blogs)
[ ] Add functionality under the Neptune column of the competitor comparison sheet (Coordinate with @SiddhantSadangi)
[ ] Update integration README (Contact @Patrycja-J)

@SiddhantSadangi Thanks for updating the branch with updated timeouts.

@kshitij12345 now that the scripts execute within ~3 mins, I think we can increase the epochs to 5

@kshitij12345 , @normandy7
I think the huggingface-integration project would be a better place to log runs than quickstarts.
This is currently not open to anonymous logging and has some old runs by @twolodzko and @Raalsky , but we should be able to delete them and add neptuner to this project to anonymous logging.
Let me know what you think.

@SiddhantSadangi fine for me.

Except for Windows Python 3.8 failure, all other failures are expected.
Windows Python 3.8 failure looks flaky connection issue: https://github.com/neptune-ai/examples/actions/runs/3151258425/jobs/5124997271

Windows Python 3.8 failure looks flaky connection issue: https://github.com/neptune-ai/examples/actions/runs/3151258425/jobs/5124997271

yeah, re-run succeeded

@normandy7 This is merged.
Can you update the checklist once the docs are updated?
Also, let's mention Transformers instead of HuggingFace in the index for consistency


Use tree height instead of chunk limit for merkleizer

More closely matches implementation and avoids generic bloat.
Renamed to avoid accidental limit-vs-height confusion.

https://github.com/nim-lang/Nim/pull/23188 should fix the CI issue in devel which this triggered.

@tersec indeed it did: https://github.com/status-im/nim-ssz-serialization/actions/runs/7490848447 thanks!


Keep getting repeated timeout

I'm trying to enroll with ykfde-enroll -d /dev/sda2 -s 2
Around once a second I get a new
Yubikey core error: timeout
   Remember to touch the device if necessary.

message, and the light on my yubikey goes on. I tap it and it continues to show the same output, and ~5 seconds later the light on my yubikey goes on again. Any ideas?

Fixed by running ykpersonalize -2 -ochal-resp -ochal-hmac -ohmac-lt64 -oserial-api-visible


Linter warning BCP334 is not correct when using several string functions.

Bicep version
0.22.6
Describe the bug
I am receiving a BCP334 warning for a case that cannot occur. I am starting the name with the static value of stflow.
Warning BCP334: The provided value can have a length as small as 0 and may be too short to assign to a target with a configured minimum length of 3.

To Reproduce
var flowLogStorageName = take(replace(toLower('stflow${resourceName}${uniqueString(resourceGroup().id, resourceName)}'),'-',''),24)
resource flowLogStor 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  name: flowLogStorageName
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
  location: location
  properties: {
    minimumTlsVersion: 'TLS1_2'
  }
}

Additional context
Add any other context about the problem here.

There are two workarounds you can use:

You could disable this diagnostic:var flowLogStorageName = take(replace(toLower('stflow${resourceName}${uniqueString(resourceGroup().id, resourceName)}'),'-',''),24)
resource flowLogStor 'Microsoft.Storage/storageAccounts@2023-01-01' = {
  #disable-next-line BCP334
  name: flowLogStorageName
  kind: 'StorageV2'
  sku: {
    name: 'Standard_LRS'
  }
  location: location
  properties: {
    minimumTlsVersion: 'TLS1_2'
  }
}

Or you can reorder the functions in the expression a bit:var flowLogStorageName = take(toLower('stflow${replace(resourceName, '-', '')}${uniqueString(resourceGroup().id, resourceName)}'),24)

Fixing the analysis here will be a bit tricky. Because the value of resourceGroup().id can't be calculated at compile time, toLower('stflow${resourceName}${uniqueString(resourceGroup().id, resourceName)}') is represented in the type system as a string with at least 19 characters. Since replace doesn't know the exact value of the first argument, it's assuming that the string could be entirely composed of '-' characters.
The type system currently only knows about string literals (like 'stflow') or strings with optional min/max lengths; there could be a separate string type introduced that is aware that is has literal segments.

Sounds like by design to me.  The message is a warning and does say "could be".  The proper fix it is the disable-next-line.

This warning breaks my ADO build because it's uses BuildQualityChecks to ensure no new warnings. I could suppress this one in one way or another, but I'd like it not to be emitted in the first place. Here's my file:
param dcResourceGroupName string
param clusterPrefix string
param stamp string
param environment string
param location string

var azureRegionLookup = {
  westus: {
    azureRegionAbbreviation: 'wus'
  }
  westus2: {
    azureRegionAbbreviation: 'wus2'
  }
  westus3: {
    azureRegionAbbreviation: 'wus3'
  }
}
var storageAccountName = '${clusterPrefix}${stamp}${environment}${azureRegionLookup[location].azureRegionAbbreviation}os'

resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
  name: storageAccountName
  scope: resourceGroup(dcResourceGroupName)
}

Proposal: since the warning says "may" and my resource is marked as existing, should the warning be not emitted?

@abatishchev The type system could be updated to detect that azureRegionLookup[location].azureRegionAbbreviation is 'wus' | 'wus2' | 'wus3' | error, though I expect that will be complex to implement. As a workaround, would an empty string really be an acceptable clusterPrefix, stamp, or environment? Adding @minLength(1) to any one of those declarations would ensure that the storage account name is at least three characters.

Adding @minLength(1)

Sure, this makes sense and is the simplest one, would clearly hint the validation system that the sum length is >3
But what about this one:

Proposal: since the warning says "may" and my resource is marked as existing, should the warning be not emitted?

Why to run validation on existing resources in the first place? If it exists, then it's valid by definition.

Why to run validation on existing resources in the first place? If it exists, then it's valid by definition.

True, but the deployment would still fail if it tried to query a storage account with a two-letter name (which is what the existing declaration will cause ARM to do). This could be incorrect if an RP's validation rule was added after the existing resource was created, and the resource was grandfathered in. E.g., if Storage were to up the minimum length to 4 characters for new accounts, they would probably not force users with 3-character account names to recreate them.
That seems fairly niche, though, so I'd like to see more upvotes before we commit to this.

True, but the deployment would still fail if it tried to query a storage account with a two-letter name

reference() would fail with a simple 404, because the resource doesn't exist because it cannot. The call would fail at ARM, won't even reach the RP so it won't have a chance to run the validation.


Spring.NET 2.0 release

You guys mentioned months ago this was going to be released months. When is 2.0 targeted to be released officially and the Nuget package updated?

This will likely be officially 2.0 GA this coming weekend.

+1

+1
Em quarta-feira, 28 de janeiro de 2015, Erick Lombardo <
<EMAIL_ADDRESS>escreveu:

+1
—
Reply to this email directly or view it on GitHub
https://github.com/spring-projects/spring-net/issues/82#issuecomment-71949808
.

Finally. Good to know.

+1

+1. Cant wait.

Will this release support NHibernate 4?

Yes, that support is already in the MASTER branch and so would be included in any subsequent release.
-Steve B.
-----Original Message-----
From: "piolo108"<EMAIL_ADDRESS>Sent: 2/2/2015 1:56 PM
To: "spring-projects/spring-net"<EMAIL_ADDRESS>Cc: "Steve Bohlen"<EMAIL_ADDRESS>Subject: Re: [spring-net] Spring.NET 2.0 release (#82)
Will this release support NHibernate 4?
—
Reply to this email directly or view it on GitHub.=

Just as an update to this issue, we've just posted an updated RC2 build to NuGet.
Our thinking is that its been so long since the RC1 release that there have actually been many updates/changes since the RC1 release.  This makes RC1 unable to function as an actual Release Candidate.
Assuming that no deal-breakers are uncovered by anyone from the RC2 build, our plan is now release 2.0.0GA approximately 2 weeks from now.

I've noticed that the RC 2 Nuget packages have a common.logging dependency of >= 1.2.0. Shouldn't that get changed to 3.0?

Ouch -- nice catch, yes, I'll update that immediately.  Thank, this sort of
oversight is exactly the sort of thing that RC is designed to catch!
Cheers,
-Steve B.
Steve Bohlen
<EMAIL_ADDRESS>http://blog.unhandled-exceptions.com
http://twitter.com/sbohlen
On Tue, Feb 3, 2015 at 3:12 PM, chrisdrobison<EMAIL_ADDRESS>wrote:

I've noticed that the RC 2 Nuget packages have a common.logging dependency
of >= 1.2.0. Shouldn't that get changed to 3.0?
—
Reply to this email directly or view it on GitHub
https://github.com/spring-projects/spring-net/issues/82#issuecomment-72724949
.


[toGamut] Ensure toGamut always returns a color object

Calling toGamut() with a color that is already in gamut for the specified color space would return the original color parameter which may or may not be a color object.
For example calling toGamut("red", "oklch") would return "red" instead of a color object.
This change ensures that a color object will always be returned.

Nice catch, thanks!


HTTP refactor, add CA and Headers functionality

Really interesting ideas here @FolMing, let's do a braintrust! Would be great to share your ideas with folks and compare/contrast with other libraries out there and the lessons learned from them. Have you looked at Go's net/http package? I think it is a relatively modern library we can build on.

Really interesting ideas here @FolMing, let's do a braintrust! Would be great to share your ideas with folks and compare/contrast with other libraries out there and the lessons learned from them. Have you looked at Go's net/http package? I think it is a relatively modern library we can build on.

Let's do it!
I did not look into other libraries, I was thinking only about how to implement what @rjhuijsman specifically wanted.


need to search option in map

need to search option in map

Please use for this feature other Leaflet plugins like Leaflet-Search or another from this list: https://leafletjs.com/plugins.html#search--popups


indicatif bug causes lack of output on msys and potentially other shells

Until https://github.com/mitsuhiko/indicatif/issues/60 is fixed, we should probably stop using indicatif in wasm-pack, because it completely breaks the experience for a large swath of windows users.

i would prefer a solution that gracefully degrades for consoles we know we can't support. @alexcrichton says that cargo does this in many areas so we can use that as an example. i would prefer that solution to simply removing the progressbar entirely.

Digging more into https://github.com/mitsuhiko/indicatif/issues/60 only using indicatif seems like it suffers another bug, printing zero output when output is piped somewhere else. I believe that means if you try to pipe wasm-pack output to a log file, for example, then nothing will get printed at all. That I believe is also quite serious and in need of fixing, although I don't know whether that's classified as another indicatif bug or an indicatif feature.

this should be remedied by by the update to the console crate which will be handled by #319

Ah unfortunately the issue isn't 100% fixed from wasm-pack's perspective I think. There's still two issues I believe:

First is that the output on MSYS2 is unfortunately still not great. I suspect this is a bug still in either indicatif or console, but the progress bar doesn't update the current line but rather updates the next line:

| [1/8] Checking crate configuration...
  [1/8] Checking crate configuration...
| [2/8] Adding WASM target...
  [2/8] Adding WASM target...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...
/ [3/8] Compiling to WASM...
| [3/8] Compiling to WASM...
\ [3/8] Compiling to WASM...
- [3/8] Compiling to WASM...

There's still a bug with wasm-pack (not indicatif) that when indicatif is turned off due to stderr not being a tty then no output comes out. For example wasm-pack build 2>&1 | tee out.log provides no output. (this is something that wasm-pack will need to handle, not indicatif I believe)

I've opened https://github.com/mitsuhiko/indicatif/issues/62 for the indicatif/console bug

Development seems to be very slow on Indicatif, or it's abandoned. I think you might want to consider an alternative.

@c-edw I would love to get help maintaining it. It's very actively used i just don't have too many issues with it that I update it regularly.

It also causes issues when running tests in CI (e.g. CircleCI) with stdout-capturing:

Is there a way to turn that off? Is there some sort of "interactive shell" detection that fails in this case?

That is a different issue. I fixed msys support a while back so it prints now.

@mitsuhiko you're right. And wasm-pack uses version 0.9 (released in January). So I guess this issue could probably be closed?

we are now tracking this via #298


Fix a few issues we encountered in production, add some tests, switch to v8

Changes in this PR
Most of the changes in this PR are the addition of tests! Changes to the actual logic are honestly fairly small.
We had made quite a few changes and I wanted to contribute those back to this repo. I can split the PR up if you'd like so just let me know!
(copious comments were added to the code to help explain changes 😄 )

We had issues with the unsub logic when we hit production. It seems that the current code can produce an invalid index exception. To fix this, the logic was modified and some tests added to ensure that we properly remove subscribers and if no subs are left we remove the subscription altogether.
The lock that is acquired is only removed upon timeout. This isn't really an issue per se but is for our use-case. We invalidate some of the data we cache and also allow some updates. They're very infrequent but the lock being held for a set period of time could lead to  timeouts if deletions and Gets happened quickly enough. The fix here was to delete the lock after we've generated our cached value.

In doing this I realized there could be a very very brief window where a lock is acquired but the value was already cached. To account for this I added a Get before we generate the value. This adds some overhead that may or may not be worth. I'll let you decide. The scenario seems incredibly unlikely but is possible and the additional Get does avoid it (I think)

Tests were added to go red -> green for the issues explained above. They could probably be implemented a bit better and not do .Sleeps but it saved me some time so I went with it. The tests use testcontainers to hit a dockerized Redis instance.
Swtiched the code to use redis v8 from go-redis. This is probably questionable, but we use v8 and needed this library to work with it. v8 has the benefit of being able to pass a context in for redis queries but you'll notice I just used context.Background() for now and ignored that. It's not perfect but it should be functionally equivalent to what this library did before. I don't now this for certain but I would expect that v8 is more likely to be used in production by others as well. Let me know if you'd like me to remove this change though!

Hi! I've seen this PR, I'll need a bit of time to read it carefully, sorry!


Hotfix saveAndSelectAccount (#1462)

Thanks for the fix @marcinbodnar. @vgrichina I think we should try to get this fix into production today? @marcinbodnar can you prepare a PR for stable?


Improve multiline labeling for tooltips in doughnut charts

Change the default doughnut chart tooltip callback to better handle multiline labels. I put the value on the first line. I think this is fine since it matches how the color box is drawn in the label.
Fixes #3269
After Changes

Looks good. I think we could even get rid of  defaultConfig.tests.js  and move these tests next to the associated classes (e.g. bubble chart default config in controller.bubble.tests.js, etc.). If it make sense, we can do that later of course.

yeah, these are becoming much more chart specific so we can move them into the controller tests at some point


Add new WsFederation package

See https://github.com/aspnet/Security/pull/1639

Actually, this will most likely break Universe. You also need to update the submodule that contains this package.


Wrong snippet

This snippet does not work:
def recognizing_handler(e : speechsdk.SpeechRecognitionEventArgs) :
    if speechsdk.ResultReason.RecognizingSpeech == e.result.reason and len(e.result.text) > 0 :
        print("Recognized: {}".format(result.text))
        print("Offset in Ticks: {}".format(result.offset))
        print("Duration in Ticks: {}".format(result.duration))

See result is not defined. You need
def recognizing_handler(e : speechsdk.SpeechRecognitionEventArgs) :
    if speechsdk.ResultReason.RecognizingSpeech == e.result.reason and len(e.result.text) > 0 :

        print("Recognized: {}".format(e.result.text))
        print("Offset in Ticks: {}".format(e.result.offset))
        print("Duration in Ticks: {}".format(e.result.duration))

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

ID: 60841ff0-31da-de3e-49f5-cba9479f0780
Version Independent ID: a8a2444a-9abb-d5bc-bdcc-aad55a658f2d
Content: Get speech recognition results - Speech service - Azure AI services
Content Source: articles/ai-services/speech-service/get-speech-recognition-results.md
Service: azure-ai-speech
GitHub Login: @eric-urban
Microsoft Alias: eur

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

@SeryioGonzalez
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


Group Academic Assessments in SPED Referral pdf

This is part of https://github.com/studentinsights/studentinsights/issues/8.
The Academic Assessments section in the pdf is randomly sorted. Instead, group these test results by test and subject. Keep the ACCESS tests at the top because they're of most importance to our users. That might happen if you're alphabetizing anyway.

Closed by https://github.com/studentinsights/studentinsights/pull/574


Remove a N+1 on /services/explorer for large flat trees when fetching non-existent children

Purpose or Intent
Removes an N+1 on flat service trees.  Effects are much more noticeable where N is large (~ 10k)
Overview
This is there query that is added:
SELECT "services"."id"
FROM "services"
WHERE "services"."ancestry" IS NULL
  AND CAST(coalesce("services"."ancestry") AS bigint) IN (SELECT id FROM services);

Which basically returns an array of ids that have children.  This can then be used to determine if x_get_tree_service_kids should even be executed on each of the children.
Metrics
Before

ms
queries
rows

~50k
17,157
77,764

After

ms
queries
rows

~43k
7,677
77,764

Links
This is similar to https://github.com/ManageIQ/manageiq/pull/11046, but doesn't remove existing functionality of the tree (improving the algorithm v.s. reducing the algorithm's scope).

@miq-bot add_label performance ui

@miq-bot add_label performance, ui

ping @kbrock
I like it :+1:
But previously using SQL was discouraged especially specific features that need not be present in all SQL databases.
But I surely support taking maximum from PostgreSQL.

@martinpovolny First off, thanks for taking a look at this, even though I am 99% sure that we will be closing it in favor of either #11166 or #11171 since they don't require an extra query and a memoized variable.
That said, both COALESCE and CAST are at least available in MySQL 5.7, as well as bigint, and because this is written in AREL, this should translate to that DB just fine

Those two functions are also available in SQLite, though, the bigint datatype is not... not that SQLite is a valid datastore for MIQ anyway, but still.

Closing in favor Keenan's PR.


Allow direct imports to reduce bundle size.

Webpack 2 does not remove a lot of unused modules from my bundle so direct import remain the best solution to reduce bundle size.
The doc page was heavily inspired by https://github.com/ReactTraining/react-router/blob/v3/docs/guides/MinimizingBundleSize.md

Codecov Report

Merging #2893 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #2893   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          68      67    -1
  Lines        1404    1407    +3
======================================
+ Hits         1404    1407    +3

Impacted Files
Coverage Δ

src/createFieldArray.js
100% <100%> (ø)

src/createReduxForm.js
100% <100%> (ø)

src/createFormValueSelector.js
100% <100%> (ø)

src/createValues.js
100% <100%> (ø)

src/createFields.js
100% <100%> (ø)

src/immutable.js
100% <100%> (ø)
:arrow_up:

src/createField.js
100% <100%> (ø)

src/index.js
100% <100%> (ø)
:arrow_up:

src/createReducer.js
100% <100%> (ø)

... and 6 more

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 cda2572...f83c9af. Read the comment docs.

Can you check #2315, please?
Over there guys think the bundle size problem is related to lodash.
BTW, what a huge PR!

For me since I was also using lodash, it is shared so that is not a problem. The problem was the factory index files that prevented direct imports.

Wow! That's an impressive PR!
Well done. Thank you for your time.

@ruiaraujo Is there some advantage to doing
import { default as Foo } from './somedir/Foo'

over
import Foo from './somedir/Foo'

??
The latter is less explicit, but much more readable, in my opinion.

Oops, nevermind. They are EXPORT statements. There, now we've both made absentminded mistakes on this PR. :-)

Ugh. ☹ In retrospect, you really should have git mv'd reduxForm.js to createReduxForm.js, and then created a new reduxForm.js, as this PR has wiped all annotation history from the file, since all the complex code now exists in a brand new file. Oh well... live and learn...
(I probably would not have thought to do this either.  I'm just only realizing this in retrospect.)

Hmm, does git mv actually help with that problem?
git mv is just a mv + git add which was what I did.
On Mon, May 8, 2017 at 6:52 PM Erik Rasmussen<EMAIL_ADDRESS>wrote:

Ugh. ☹ In retrospect, you really should have git mv'd reduxForm.js to
createReduxForm.js, and then created a new reduxForm.js, as this PR has
wiped all annotation history from the file, since all the complex code now
exists in a brand new file. Oh well... live and learn...
(I probably would not have thought to do this either. I'm just only
realizing this in retrospect.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/erikras/redux-form/pull/2893#issuecomment-299923971,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASi2VlvUXP-_lr6YzvgmYa9T274gZ4vks5r30g9gaJpZM4NSz2A
.

Hmm... So it is. I was under the impression that it would preserve the history of the file. I swear I've seen it do that before. Perhaps it only works if you don't immediately add another file with the old name...? Oh well.
Nevermind then. 😄

Is there a timeline for this getting released. :-) ?

Published as v6.7.0.

Interesting PR, two minor things

You need a space in the markdown after ##, currently it looks like in the picture above
There's no mention on how to use this together with immutable.js

@piuccio It is the same thing to use it with immutable, just add immutable.

just add immutable

where?
redux-form/es/whatever/immutable
redux-form/es/immutable/whatever
I suppose it's the first one, but it would be nice to have it in the doc

Hi, I'm noticing that the Babel plugin doesn't work well with actions:
WARNING in ./src/foo/bar.js
23:23-30 "export 'default' (imported as 'actions') was not found in 'redux-form/es/actions'

My import:
import { actions, Field, reduxForm } from 'redux-form';
const { reset } = actions;

This can be worked around from the user's end by changing the import statement, but I was wondering if it would be a good idea to add a default export to es/actions that contains all the actions. I think the import pattern I'm using is fairly standard, and the change would help users optimize their bundles with minimal refactoring.
Alternatively, if this is happening because I'm doing something wrong, please let me know. Thanks!

@erikras What is that createValues.js and values.js? Why it's not documented? Can I use it do access the form field values or you plan to remove that on the future?


is it bug

Caused by: java.lang.ClassNotFoundException: Didn't find class "com.sjtu.yifei.route.RouteService"
why do i click the textview with the demo, it happen bug. are you sure it is ok?can the project run?

你为啥不能运行我不能确定原因，app-release.apk就是demo运行的


fix(tangle-dapp): Fix blank screen after the page is mounting

Summary of changes
Provide a detailed description of proposed changes.

Fix blank screen after the page is mounting
Format code

Proposed area of change
Put an x in the boxes that apply.

[ ] apps/bridge-dapp
[ ] apps/hubble-stats
[ ] apps/stats-dapp
[x] apps/tangle-dapp
[ ] apps/testnet-leaderboard
[ ] apps/faucet
[ ] apps/zk-explorer
[ ] libs/webb-ui-components

Reference issue to close (if applicable)
Specify any issues that can be closed from these changes (e.g. Closes #233).

Closes #2451

Screen Recording
If possible provide a screen recording of proposed change.
https://github.com/user-attachments/assets/a5e2f926-3a8c-40ed-9680-63de37e7f732

Code Checklist
Please be sure to add .stories documentation if any additions are made to libs/webb-ui-components.

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Nice fix 👌


Release 1.0.13 breaks rspec

When testing a cookbook that includes the docker cookbook, since 1.0.13 we get errors like this:
================================================================================
Recipe Compile Error in /tmp/d20150831-7686-1rjxsb9/cookbooks/docker/libraries/matchers.rb
================================================================================

NoMethodError
-------------
undefined method `allowed_actions' for Chef::Resource::DockerContainer:Class

Cookbook Trace:
---------------
  /tmp/d20150831-7686-1rjxsb9/cookbooks/docker/libraries/matchers.rb:15:in `block in <top (required)>'
  /tmp/d20150831-7686-1rjxsb9/cookbooks/docker/libraries/matchers.rb:5:in `each'
  /tmp/d20150831-7686-1rjxsb9/cookbooks/docker/libraries/matchers.rb:5:in `<top (required)>'

Relevant File Content:
----------------------
/tmp/d20150831-7686-1rjxsb9/cookbooks/docker/libraries/matchers.rb:

  8:
  9:      if Gem.loaded_specs['chefspec'].version < Gem::Version.new('4.1.0')
 10:        ChefSpec::Runner.define_runner_method(name)
 11:      else
 12:        ChefSpec.define_matcher(name)
 13:      end
 14:
 15>>     resource.allowed_actions.each do |action|
 16:        define_method("#{action}_#{name}") do |resource_name|
 17:          ChefSpec::Matchers::ResourceMatcher.new(name, action, resource_name)
 18:        end
 19:      end
 20:    end
 21:  end
 22:

If I explicitly pin the cookbook version to 1.0.12, everything works fine. This seems to be related to this commit: https://github.com/bflad/chef-docker/commit/4fd3083d3844a292039c0aa8882c2068676b5f7b

There's a new one...
specs pass on my laptop (ChefDK 0.7.0) https://gist.github.com/someara/7d5d98e5bb75f69c9a07
I noticed that Travis is broken with (different a error message), which I chocked up to mismatched ChefDK versions, and was planning on investigating later.
Can you try 1.0.16 and let me know relevant versions?
-s

Ah, o.k., the errors only seem to be seen with ChefDK 0.6.2 or smaller, i.e. with Chef <= 12.3. Upgrading to 0.7.0 helped, my tests are running fine with that.

Good to know! thanks!

the method allowed_actions was introduced here: https://github.com/chef/chef/commit/236570dc9605ac312b44508b1c3a6a0e7c19b4dc


Request to remove d.ifengimg.com from blacklist

Hi, can you please have d.ifengimg.com removed from blacklist? It serves the whole site's thumbnails of news at www.ifeng.com. I checked my blacklist and finally found out that it is blocked in yours. To whitelist the domain of d.ifengimg.com is harmless.
Thank you for your time.

ping @jawz101 for assist 👍

thanks.  Removed.  At one point a long time ago I merged an Asian list that seemed to have good coverage of that region and that was probably left over.  I wish I could scrub out some of those false positives.

yes for sure, but it is a chaos for an Asian list, there is a limited restriction for privacy, and it will take a lot of efforts to make it work properly. Some can cause problem dramatically, I did and still testing out all my browsing record monthly.
here is a blacklist I am using for Chinese region: https://github.com/privacy-protection-tools/anti-AD, they update daily I suppose.
Thank you for your help.


Login to twitch fails

When I go to authenticate Twitch Leecher with my Twitch account, it takes me to the login page. But when I input my information and hit enter, it tells me the browser is unsupported and so I cannot login. Can this be fixed?
If there's more info you need, let know.
Sophie

Thanks for reporting!
What version of Twitch Leecher DX are you using? This Bug was fixed in version 3.0.1, if you're using an older version, please update to a newer version. If you are using 3.0.1 or newer, please tell me what brower you are using or try another browser.
Hope this helps!


Add the Maui.Graphics website to the repository details

I wasn't finding information in the README how to actually use the library, but I found the Maui.Graphics website, which also links to the official documentation.
I think the Maui.Graphics website should be put in the repository details, and that the documentation should be linked to from the README.

Hi @bmitc and project owners (@jonlipsky)
I registered https://maui.graphics a while ago because I kept trying to search for documentation about this library but .graphics is a top level domain so my browser would try to go to that URL and timeout. To be clear, I'm an open source maintainer who enjoys making .NET apps, and I'm not affiliated with Microsoft.
At one time I considered putting quickstarts and code examples on the site, but I don't think I'm the best person to create/maintain/represent idiomatic use cases for this library at this time, so I am currently just linking to the best official documentation page I'm aware of.
If this group has a better recommendation for what should be at that URL, I welcome the input!
PS: I noticed when people tweet the phrase "maui.graphics" it automatically hyperlinks to that page (e.g., https://twitter.com/jonlipsky/status/1529185387846873088)
PPS: I heard @jamesmontemagno mention the domain on Merge Conflict episode #302, so I welcome input from him too

Thanks for the heads up on that @swharden. It looked so nice, that I just assumed it was official. 🙂 So yea, up to the project maintainers on that aspect.
After actually reading the official documentation, it's only from the perspective of using Maui.Graphics from Maui itself, but I think that at a minimum it should be included somewhere in the README.

Thanks for the heads up on that @swharden. It looked so nice, that I just assumed it was official.

haha, thanks! 🚀

After actually reading the official documentation, it's only from the perspective of using Maui.Graphics from Maui itself

I'm not aware of any official documentation about how to use Maui.Graphics in non-Maui apps. The topic seems highly relevant since .NET 6 deprecated cross-platform support for System.Drawing.Common and one of Microsoft's recommended actions is to use this library instead.
I put some Maui.Graphics Quickstart pages on C# Data Visualization showing how I use this library in Console, WinForms, and WPF apps that you may find useful.

@jonlipsky Thanks for the information! I was at least hoping that is the case. So as to not distract from this documentation related issue, I've posted a question regarding that in the discussions section: https://github.com/dotnet/Microsoft.Maui.Graphics/discussions/466
I've been meaning to ask that question anyway. Although I'm concerned that there's too much fragmentation for .NET graphics libraries and GUI frameworks, as mentioned here https://github.com/dotnet/Microsoft.Maui.Graphics/discussions/272, I'm still trying to do due diligence in considering all alternatives for existing .NET graphics solutions.

Repository is no longer under development. See https://github.com/dotnet/Microsoft.Maui.Graphics/pull/496#issuecomment-1375104121.


Allow cleaning up the temp files on exit.

By default, the server leaves relatively large files around in the temp directory. Especially when using a LocalZooKeeperRule, this can quickly fill up tmp space. This optionally allows the rule to clean up after itself.

Nice! In my opinion, cleanup should actually be the default (and only) behavior, rather than putting it behind a flag. Thoughts, @justinuang?

@ortschun because I forgot that existed. I'm happy to implement a recursive delete if we'd rather not take the dependency - in general, I prefer library tested solutions to my own, but understand if a goal is to keep dependencies down :)
@punya Agreed - I kept the behavior the same, but would be in favor of having default be clean up (and possibly only behavior). The reason I thought you might not want to clean up is because you might want to use those files to debug after the fact - I don't know enough about ZK to know if that's useful or not (since they appear to be binary)

Ping! this will really help out our project - otherwise each local build leaves ~2GB of data in temp

lgtm after the indentation is fixed!

@justinuang are you going to make a new release?

Jacob, can you confirm that master works for you? (There is a small gradle wrapper jar issue we need to fix. I posted a comment on that PR).


A Question About the Environment

Cant it run on Windows? It seems to work only on Linux

I tried to run under windows, but failed

At times it was able to run on Windows. I do not remember what platform specific problems are still present, and I certainly don't know what issues may have appeared since I stopped maintaining it.