toot: 0.18.0 -> 0.19.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/toot/versions.
meta.description for toot is: '"Mastodon CLI interface"'.
Release on GitHub
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/mbk0df2fq30ysv6iz9bcmzpvyv5pas0d-toot-0.19.0/bin/.toot-wrapped passed the binary check.
/nix/store/mbk0df2fq30ysv6iz9bcmzpvyv5pas0d-toot-0.19.0/bin/toot passed the binary check.
2 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 0.19.0 with grep in /nix/store/mbk0df2fq30ysv6iz9bcmzpvyv5pas0d-toot-0.19.0
directory tree listing: https://gist.github.com/622ae78d0b503c65010d26d3865c9049
du listing: https://gist.github.com/d981a4f9501f01f1a67da8a69562b530

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout bf940defbbb54b678ab4688562ee13a1cc1be938 && nix-shell --pure -I nixpkgs=. -p toot

Success on aarch64-linux (full log)
Attempted: toot
Partial log (click to expand)
collected 29 items

tests/test_api.py ...                                                    [ 10%]
tests/test_auth.py ....                                                  [ 24%]
tests/test_config.py .....                                               [ 41%]
tests/test_console.py ................                                   [ 96%]
tests/test_version.py .                                                  [100%]

========================== 29 passed in 2.37 seconds ===========================
/nix/store/81r9cpnhlr0kij6xym7wkadxxvkp5gbh-toot-0.19.0

Success on x86_64-linux (full log)
Attempted: toot
Partial log (click to expand)
collected 29 items

tests/test_api.py ...                                                    [ 10%]
tests/test_auth.py ....                                                  [ 24%]
tests/test_config.py .....                                               [ 41%]
tests/test_console.py ................                                   [ 96%]
tests/test_version.py .                                                  [100%]

========================== 29 passed in 0.47 seconds ===========================
/nix/store/mbk0df2fq30ysv6iz9bcmzpvyv5pas0d-toot-0.19.0

Success on x86_64-darwin (full log)
Attempted: toot
Partial log (click to expand)
collected 29 items

tests/test_api.py ...                                                    [ 10%]
tests/test_auth.py ....                                                  [ 24%]
tests/test_config.py .....                                               [ 41%]
tests/test_console.py ................                                   [ 96%]
tests/test_version.py .                                                  [100%]

========================== 29 passed in 0.47 seconds ===========================
/nix/store/8b5ggid54n5r27vnfc1a5mj57h8d4jdy-toot-0.19.0


Add a brew cask

It would be very useful to have it available through brew.

Thanks for suggestion!
Unfortunately this app is not notable enough to be accepted in main casks repository (under 30 forks, 30 watchers, 75 stars - https://docs.brew.sh/Acceptable-Casks).
But we can create own tap. I'll look into it (also open for PRs).
Until then - you can install Mac App Store version from terminal with help of https://github.com/mas-cli/mas:
mas install<PHONE_NUMBER>

Thanks @ealeksandrov. That would be interesting to create our own tap. I prefer the standalone version to be able to use the system media keys.


WIP: Declaration Chains and Redeclarations

This is a first jab at implementing re-declarations. It is not quite finished yet, but rather provides the basic framework for it. It later needs to be tied in with the ScopeManager to deal with the actual (re)-definitions.

I will mark this as blocked until we reach a decision about #280


Implemented marginal log likelihood for parallel Kalman

Calculation details: https://www.overleaf.com/read/mwsmdyqycynn

Looks great, thanks! Maybe you add add the math writeup to a gist (or an arxiv note), and add a link to it?

The comments from "michael" are actually from kevin - github has messed up our id's!.

Cool trick!

Cool trick!

Could you clarify what you mean by that?
I guess one thing to note is that I've found the log normalizer computation to be numerically very sensitive, so it will give different results for mathematically equivalent formulations. I don't have a ton of experience in numerical stuff like this so I think there definitely could be room for improvement/more experimentation.

I typically compute the filtering mean and cov, then compute the observation predictive mean and cov, and compute the log-likelihood elementwise using vmap, like here
https://github.com/EEA-sensors/sqrt-parallel-smoothers/blob/16d9bbd5aa021be5f88277d3c87242b2c9a7bd53/parsmooth/parallel/_filtering.py#L57
I was wondering how efficient the "explicit" method was compared to doing this crude thing

Interesting. Haven't done this comparison in terms of numerical accuracy and computational time. Definitely interesting to try out since this should have the same computational complexity...

That’s a good point. You can compute log p(y_t | y_{1:t-1}) in parallel for all t. I’m not sure areay sums automatically use a parallel reduction on GPUs, but they certainly could. In any case, I’d be surprised if the final summation was the most costly computation.

On Nov 3, 2022, at 2:25 PM, matthew9671 @.***> wrote:

Interesting. Haven't done this comparison in terms of numerical accuracy and computational time. Definitely interesting to try out since this should have the same computational complexity...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.


Neovim Formating with pretier doesn't work in .astro files

📚 Subject area/topic
Neovim Formater Integration with Astro
📋 Page(s) affected (or suggested, for new content)
https://docs.astro.build/en/editor-setup/#other-code-editors
📋 Description of content that is out-of-date or incorrect
The current documentation for setting up Prettier and LSP with Neovim does not include necessary configuration details in the package.json for formatting .astro files.
Description
After setting up Prettier and the LSP for Neovim, formatting doesn't work correctly. It took a day to resolve this issue, and it was eventually fixed with help from the Astro Discord community member @Grahf. To save others from similar frustration, please add the following configuration to the documentation:
"prettier": {
  "astroAllowShorthand": true,
  "overrides": [
    {
      "files": "*.astro",
      "options": {
        "parser": "astro"
      }
    }
  ],
  "pluginSearchDirs": [
    "."
  ],
  "plugins": [
    "prettier-plugin-astro"
  ]
}

🖥 Reproduction in StackBlitz (if reporting incorrect content or code samples)
No response

Hi @f-amine ! I'm glad you eventually got this working!
Would you like to make a PR to add this information yourself to the docs page? I could see adding it to the bottom of the page, in the Prettier section, maybe like:
Prettier for Neovim
To configure Prettier for Astro in Neovim, use the following configuration:
"prettier": {
  "astroAllowShorthand": true,
  "overrides": [
    {
      "files": "*.astro",
      "options": {
        "parser": "astro"
      }
    }
  ],
  "pluginSearchDirs": [
    "."
  ],
  "plugins": [
    "prettier-plugin-astro"
  ]
}

Do you think this would be a helpful addition? If so, I'd be happy to receive a PR to the docs page!

Okey I can do that, I'm gonna look for the specific file for that and make a PR right now

Amazing @f-amine - Quick tip - you can just go to that page in docs and click "edit this page" and you'll be taken right there!  🙌

sent a pr, thanks for the fast reply !!


Remove unit tests from pr_check and add local bonfire config file

Secure Coding Practices Checklist Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[ ] Input Validation
[ ] Output Encoding
[ ] Authentication and Password Management
[ ] Session Management
[ ] Access Control
[ ] Cryptographic Practices
[ ] Error Handling and Logging
[ ] Data Protection
[ ] Communication Security
[ ] System Configuration
[ ] Database Security
[ ] File Management
[ ] Memory Management
[ ] General Coding Practices

Codecov Report

Merging #197 (a3d34d7) into master (209c0c9) will increase coverage by 25.49%.
The diff coverage is 70.91%.

@@             Coverage Diff             @@
##           master     #197       +/-   ##
===========================================
+ Coverage   50.14%   75.63%   +25.49%
===========================================
  Files          13       23       +10
  Lines         357      669      +312
===========================================
+ Hits          179      506      +327
+ Misses        178      163       -15

Impacted Files
Coverage Δ

clean_expired_records.py
0.00% <0.00%> (ø)

historical_system_profiles/mgmt_views/v0.py
100.00% <ø> (ø)

kafka_listener.py
0.00% <0.00%> (ø)

standalone_flask_server.py
0.00% <ø> (ø)

wsgi.py
0.00% <ø> (ø)

..._system_profiles/notification_service_interface.py
35.00% <35.00%> (ø)

...ical_system_profiles/baseline_service_interface.py
39.13% <39.13%> (ø)

historical_system_profiles/archiver.py
57.50% <57.62%> (+57.50%)
:arrow_up:

...torical_system_profiles/drift_service_interface.py
66.66% <66.66%> (ø)

historical_system_profiles/db_interface.py
78.68% <76.00%> (+12.02%)
:arrow_up:

... and 26 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 25660b4...a3d34d7. Read the comment docs.

We can go back to master with notifications-backend as per success with https://github.com/RedHatInsights/system-baseline-backend/pull/224


Adding async function invocation capability

Signed-off-by: Tihomir Surdilovic<EMAIL_ADDRESS>Many thanks for submitting your Pull Request :heart:!
Please specify parts this PR updates:

[x ] Specification
[x ] Schema
[x ] Examples
[ ] Extensions
[ x] Roadmap
[ ] Use Cases
[ ] Community
[ ] TCK
[ ] Other

What this PR does / why we need it:
Adds async function invocation capability

Allows functions to be invoked async.
Example for functionRef:
  "actions":[
      {
       "functionRef": {
        "invoke": "async",
        "refName": "emailFunction",
        "arguments": {
         "customer": "${ .customer }"
        }
       }
      }
     ],

Example for SubFlow:
  "actions":[
      {
       "subFlowRef": {
        "invoke": "async",
        "onParentComplete": "continue",
        "workflowId": "customeronboardingworkflow",
        "version": "1.0"
       }
      }
     ],

@tsurdilo So sorry man, was away for a week and forgot to come back to you on that. Yeah sure, fine by me, though I don't really see the point in the case of http or event related actions


Getting started with python in Blender

Getting started with python in Blender.
Proposed article introduction.
Blender is a free and open source 3D modeling program. Modeling, rigging, animation, simulation, rendering, compositing, and motion tracking are all supported, as well as video editing and game production.Python allows you to automate activities with blender's built-in tools to speed up productivity and provide functionality that would otherwise be impossible to achieve manually.
Key takeaways

introduction to scripting in blender.
-importing modules into blender.
create addons in blender
the merits of using python in blender

Article quality
This article provide an indepth guide on scripting python in blender .What make it stand out from the rest is how it geared to create best practice when using python in blender. it also aims to explain the content in beginner friendly manner.
References
N/A

Introductory aspects to this topic/your key takeaways seem to be well covered in other blogs and official docs. Feel free to suggest another topic. Thanks


Migrating sayar/fabrikate-kafka-sample into a samples directory

Creating and starting a new subdirectory with examples and supporting documentation for fabrikate related deployments and use cases.
First example is a Stateful Kafka Deployment through the Strimzi Operator, backed by a manual Portworx configuration, and Kafka Connect support.
Related to https://github.com/microsoft/bedrock/issues/534

Also, would it be possible to rebase this into a single commit? or do you have important info in the commits?

I'll defer to you @evanlouie and @andrebriggs , but it would be nice to preserve history for us to rollback some configurations if we ever need to. The history is also available in in the original repo: https://github.com/sayar/fabrikate-kafka-sample

I'm leaning toward rebase, don't like having so much noise in the history.
But if you either of you (@mtarng @andrebriggs) see value in having it, feel free to merge.

oh, nice catches @evanlouie


CHW/ANC SubTask - User can assign a head of household

The Head of Household is the mom but can be updated. Core caregiver is defined as the mom
1.5 days FTE + 20% buffer

The flow can not map exactly as mentioned on mockups. Since Family is a person so the registration of family and members would be separate as in #276 . ANC Registration is gettign updated with this https://github.com/opensrp/fhircore/issues/416 .

https://github.com/opensrp/fhircore/pull/547 - Family , head and member registration was done with this PR https://github.com/opensrp/fhircore/pull/547. We can not change HHH for now. At what point we should change it and what should be the flow. i.e. we need to make deallocate first and allocation next in same flow
@f-odhiambo

Let's start a new issue or changing HHH


Fix tcc build, remove PACK macro

There was no definition of the macro for compilers that were not gcc, clang or msvc. While it would be easy to add one, a better approach is to switch to memcpy() and avoid type punning altogether.
Fixes: https://github.com/quickjs-ng/quickjs/issues/270

The PACK macro was ugly indeed.  Does the assembly look good in the code generator?

Yes, it's pretty much what you'd expect on x86: a single load or store.
(You have to look pretty hard because the get and put functions all get inlined themselves too.)


No font scaling on SSFF tracks

Font scaling on window resize does not work for the message Zoom in to see countour(s) on SSFF tracks.

most of the scaling stuff is done inside the ssffTrack directive using the Drawhelperservice while the text "Zoom in to see.." is being generated inside the drawssff directive (where the values are drawn, if there are any)
should we move the "zoom in" i.e. the else block (lines 214-230 in drawssff.js) into ssffTrack also ? which already watches viewState.timelineSize or should we leave it there ? 'cause all the markup stuff is also there ?
or do you think it belongs to the actual values and it should stay where it is ?
(but then we also have to watch viewState.timelineSize inside drawssff, which is currently not the case)


buildkit sets the difference between the pod startup time of nydus packages and nydusify converted nydus packages

In the beginning, I used nydusify to convert Nydus packages based on oci, and the pod startup time was about 13s. Later, in order to save packaging time, I used buildkit for packaging, and the pod startup time was 20s+. I found that the startup time of the packages in buildkit was much slower than that of nydusify to convert Nydus packages.

Thanks for reporting, we will investigate it, you can also try nydusify 2.2 if you have any time, thanks.

cc @ccx1024cc

It's about compatibility.
Images from nydusify 2.2 works inefficiently with 2.1 binaries, including nydusd, nydus-image. We pay more attention to correctness, instead of performance, for this case. That is, complete upgrade is required.

@xiangshen123 Could u list the versions of nydusify, nydus-image, nydusd before and now?

@ccx1024cc root@ym-test2-k8s-nodes3:/usr/bin# nydusd --version
Version:        v2.1.3
Git Commit:     24c3bb9ab213ab94dfbf9ba4106042b34034a390
Build Time:     2023-01-19T02:26:07.782135583Z
Profile:        release
Rustc:          rustc 1.61.0 (fe5b13d68 2022-05-18)
root@ym-test2-k8s-nodes3:/usr/bin# nydus-image --version
Version:        v2.1.3
Git Commit:     24c3bb9ab213ab94dfbf9ba4106042b34034a390
Build Time:     2023-01-19T02:26:07.782135583Z
Profile:        release
Rustc:          rustc 1.61.0 (fe5b13d68 2022-05-18)
root@ym-test2-k8s-nodes3:/usr/bin# nydusify --version
Nydusify version
Version         : v2.1.3
Revision        : 24c3bb9ab213ab94dfbf9ba4106042b34034a390
Go version      : go1.18.9
Build time      : 2023-01-19T02:21:43


Documentation - HTTP Load balancer active service policies is marked as list, but must be only one policy

The documentation shows that the item "Policies" is an ordered list : https://registry.terraform.io/providers/volterraedge/volterra/latest/docs/resources/volterra_http_loadbalancer#active-service-policies
But you have to set it up as a block :
Working code :
  active_service_policies {
    policies {
      name      = "ves-io-allow-all"
      namespace = "shared"
      tenant    = "my-tenant"
    }
    policies {
      name      = "ves-io-next-policy-set"
      namespace = "shared"
      tenant    = "my-tenant"
    }
  }

Expected code according to documentation :
  active_service_policies {
    policies = [
    {
      name      = "ves-io-allow-all"
      namespace = "shared"
      tenant    = "my-tenant"
    },
    {
      name      = "ves-io-next-policy-set"
      namespace = "shared"
      tenant    = "my-tenant"
    }
    ]
  }

The Terraform SDK used for this was originally designed for Terraform v0.11 and earlier and so it doesn't support configuration constructs that those older Terraform versions didn't support, and Terraform v0.11 and earlier didn't support lists of objects in the way you are intending here.
We can instead treat this like a documentation bug and specify that we need a list of policy blocks instead of an An ordered list of references to service_policy objects.

Yes, i would even say a map of policy blocks as you have to set it between { } and not [ ]
With an example added with multiple policies this should be enough.
Thank you for your answer


Wait until daemon is responding

Since the daemon runs preflights, it can take a while before the daemon becomes responsive to requests. In the tray we could wait until the socket is available
... or prevent the preflights to run, and allow this to be programmatically checked by an API call?

https://github.com/code-ready/tray-electron/blob/30da0b7877066d6384998468d235a508f5766906/main.js#L350-L368


hi,A new brand gpon stick

hi,TWCGPON657 is hard to find in taobao,They are all out of stock.According to the seller, it takes three months or more to re-produce.but after a hard search, I found a new similar brand in Singapore.It seems that it should be very niche
Although it is more expensive, I have checked with the seller and it also uses Realtek chips,I think it's supposed to be the same thing as TWCGPON657.The package I ordered is on the way.I'll run some tests on it when I get it.Anyway,thanks for your more information in here.
BTW since lowyat.net is no longer accepting new user registrations, I'm leaving a message here.
https://dimiks.store/product/universal-gpon-epon-onu-ont-sfp-stick-module/

@bluehj777
Hi,
I didn't know TWCGPON657 is out of stock 😶 ... Maybe many users find out that TWCGPON657 can use V2801F firmware on the cheap?
The stick you bought is V2801F, and Dimiks are not from Singapore, it was from Ukraine, because I bought my first stick.
Build Quality
V2801F
I have explore inside V2801F hardware, found out using same/recycle case as DFP-34X-2C2 and very few thermal pad, in prolong use in hot weather, my V2801F died due to excessive heat.
You need buy a fan to control V2801F overheating
V2801F firmware are very stable and highly compatible many OLT vendor, if didn't work, simply use OMCI_FAKE_OK 1 and will work!
TWCGPON657
I also explore inside of TWCGPON657, thermal well build and less heat compared with V2801F
TWCGPON657 firmware can cause lock up, not stable, this very reasons I update firmware V2801F into TWCGPON657 hardware.

Is it a Ukrainian company registered in Singapore？
https://dimiks.store/about-us/
Anyway, this is the only place I can get it at the moment. Many normal electronic goods in China are now out of stock because of chips.

I got a parcel from Ukraine,
I live in Malaysia, delivery from Singapore to Malaysia just take 1 - 2 days only, but mine take 3 weeks to arrive,

I see...


Vanilla furniture expanded power patch

After testing the mod for some time I could not find any issues with it

Looks fine. A small nitpick, can you move the anonymous method to declared method? Just to make the nesting smaller.

I've changed that in this and my other PR. The third mod I was working on doesn't require it, but it'll be a little bit more before I can make a PR as I believe I'll have to make a SyncWorker (after I figure out how to make it).

Looks fine. I'll squash.


Enable Kotlin Lint on project

given the documenation is in place enable swift lint and solve warnings and errors

[x] Add Ktlint build step
[x] verify that CI works with the present changes

The Bitrise build for the new app runs both ktlint and detekt during builds, so this issue is now resolved.


Fix #35 support multiple notifications.

Coverage increased (+0.03%) to 97.645% when pulling c5aa30b140f035ae2e7551eec464a82aa2a62233 on multiple into 52b09c5a66c53786de3189955268c3dbd28f8682 on master.


Autoplay option like the YouTube

Add the autoplay of related music after the play
which would continue on playing the music

Thanks @hawaassunil for a suggestion.
We would surely work on this playing a related music just after the current music finishes.

commit b3c69f1
added this feature onto!


Set PATH prepend after user init file runs

Summary
This applies to devbox shell only. We defer the path prepending until after any user init file is run. For devbox run, we set the path before creating the new shell.
How was it tested?
DEVBOX_FEATURE_UNIFIED_ENV=1 devbox shell
echo $PATH
# inspect that .zshrc path prepends appear AFTER the nix paths

did I understand correctly?
yes!

why do we not run shellrc for devbox run? is it because the shellrc is for interactive shells whereas devbox run is non-interactive?

yes!  I guess it's a design decision to run bashrc (I'm using "bashrc" interchangeably here, even if the user isn't running bash), for usability. It does introduce a vector of non-reproducibility between shell and run, but I think that's ok.


Syntax for Translating Collections

I've tried many combinations of syntax to translate a collection. I would very much appreciate if someone can post a working example.
I have the following in my config.yml -
collections:
cookies:
output: true
layout: cookies
My cookies folder in: _i18n/en/_cookies
I'm trying to read the collection using various permutations of the example below, with no success:
{% for item in site[site.lang].cookies %}
Any help is greatly appreciated.

I've also tried placing the collections folder in the root of the site with no success: _cookies

Check out my attempt to get translated collections working here:
https://github.com/Anthony-Gaudino/jekyll-multiple-languages-plugin/issues/72#issuecomment-317072673

Also looking for collection support.
Moving the collection inside the _i18n folder does not seem to enable the collection.


Magic number verification failed for page

OrientDB Version: 3.0.21
Java Version: 1.8.0_144
OS: windows 10
Expected behavior
Actual behavior

Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: Windows OS is detected, 262144 limit of open files will be set for the disk cache.
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO:<PHONE_NUMBER>8 B/16325 MB/15 GB of physical memory were detected on machine
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: Detected memory limit for current process is<PHONE_NUMBER>8 B/16325 MB/15 GB
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: JVM can use maximum 3628MB of heap memory
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: Because OrientDB is running outside a container 12% of memory will be left unallocated according to the setting 'memory.leftToOS' not taking into account heap memory
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: OrientDB auto-config DISKCACHE=10,737MB (heap=3,628MB os=16,325MB)
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: System is started under an effective user : test
Jun 30, 2019 1:29:32 PM com.orientechnologies.common.log.OLogManager log
INFO: Allocation of 163202 pages.
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
INFO: WAL maximum segment size is set to 6,144 MB
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
INFO: Page size for WAL located in Z:\PortableApps\eclipse-oxygen-2\workspace\orientdbtest.\db\test is set to 4096 bytes.
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
WARNING: Storage 'test' was not closed properly. Will try to recover from write ahead log
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
INFO: Looking for last checkpoint...
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
INFO: Checkpoints are absent, the restore will start from the beginning.
Jun 30, 2019 1:29:33 PM com.orientechnologies.common.log.OLogManager log
INFO: Data restore procedure is started.
Jun 30, 2019 1:29:34 PM com.orientechnologies.common.log.OLogManager log
WARNING: Record com.orientechnologies.orient.core.storage.impl.local.paginated.wal.cas.OEmptyWALRecord{lsn=OLogSequenceNumber{segment=1, position=18}} will be skipped during data restore
Jun 30, 2019 1:29:34 PM com.orientechnologies.common.log.OLogManager log
INFO: 1 operations were processed, current LSN is OLogSequenceNumber{segment=1, position=18} last LSN is OLogSequenceNumber{segment=2, position=18}
Jun 30, 2019 1:29:34 PM com.orientechnologies.common.log.OLogManager log
WARNING: Non tx operation was used during data modification we will need index rebuild.
Jun 30, 2019 1:29:36 PM com.orientechnologies.common.log.OLogManager log
WARNING: Record com.orientechnologies.orient.core.storage.impl.local.paginated.wal.cas.OEmptyWALRecord{lsn=OLogSequenceNumber{segment=2, position=18}} will be skipped during data restore
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: Storage data recover was completed
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: Storage 'plocal:Z:\PortableApps\eclipse-oxygen-2\workspace\orientdbtest.\db/test' is opened under OrientDB distribution : 3.0.21 - Veloce (build 1d8b0c01ca8fe12a516bba355681e3ec8b218d1d, branch 3.0.x)
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Wait till indexes restore after crash was finished.
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'ORole.name' is a durable automatic index and will be added as is without rebuilding
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'ORole.name' was added in DB index list
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'OUser.name' is a durable automatic index and will be added as is without rebuilding
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'OUser.name' was added in DB index list
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'dictionary' is a durable non-automatic index and will be added as is without rebuilding
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'dictionary' was added in DB index list
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'OFunction.name' is a durable automatic index and will be added as is without rebuilding
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Index 'OFunction.name' was added in DB index list
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} 4 indexes were restored successfully, 0 errors
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Indexes restore after crash was finished.
size: 675
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
SEVERE: $ANSI{green {db=test}} Magic number verification failed for page 1425 of pupil.pcl.
Jun 30, 2019 1:29:39 PM com.orientechnologies.common.log.OLogManager log
SEVERE: $ANSI{green {db=test}} Magic number verification failed for page 1425 of pupil.pcl.
java.lang.Exception
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.dumpStackTrace(OWOWCache.java:2306)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.verifyMagicAndChecksum(OWOWCache.java:2264)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFileContent(OWOWCache.java:2164)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.load(OWOWCache.java:1137)
at com.orientechnologies.orient.core.storage.cache.chm.AsyncReadCache.lambda$doLoad$0(AsyncReadCache.java:150)
at java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1853)
at com.orientechnologies.orient.core.storage.cache.chm.AsyncReadCache.doLoad(AsyncReadCache.java:147)
at com.orientechnologies.orient.core.storage.cache.chm.AsyncReadCache.loadForRead(AsyncReadCache.java:115)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperation.loadPageForWrite(OAtomicOperation.java:111)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.loadPageForWrite(ODurableComponent.java:129)
at com.orientechnologies.orient.core.storage.cluster.v1.OPaginatedClusterV1.addEntry(OPaginatedClusterV1.java:1720)
at com.orientechnologies.orient.core.storage.cluster.v1.OPaginatedClusterV1.createRecord(OPaginatedClusterV1.java:502)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.doCreateRecord(OAbstractPaginatedStorage.java:4547)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.commitEntry(OAbstractPaginatedStorage.java:5133)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.commit(OAbstractPaginatedStorage.java:2161)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.commit(OAbstractPaginatedStorage.java:1993)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.internalCommit(ODatabaseDocumentAbstract.java:2732)
at com.orientechnologies.orient.core.storage.impl.local.OMicroTransaction.doCommit(OMicroTransaction.java:363)
at com.orientechnologies.orient.core.storage.impl.local.OMicroTransaction.commit(OMicroTransaction.java:166)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentEmbedded.endMicroTransaction(ODatabaseDocumentEmbedded.java:799)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentEmbedded.executeSaveRecord(ODatabaseDocumentEmbedded.java:789)
at com.orientechnologies.orient.core.tx.OTransactionNoTx.saveNew(OTransactionNoTx.java:244)
at com.orientechnologies.orient.core.tx.OTransactionNoTx.saveRecord(OTransactionNoTx.java:174)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.saveInternal(ODatabaseDocumentAbstract.java:2099)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.save(ODatabaseDocumentAbstract.java:2064)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.save(ODatabaseDocumentAbstract.java:85)
at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:2169)
at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:2160)
at com.orientechnologies.orient.core.record.impl.ODocument.save(ODocument.java:118)
at test.Test.main(Test.java:34)

Steps to reproduce

public static void main(String[] args)
{
try (OrientDB odb = new OrientDB("embedded:./db", OrientDBConfig.defaultConfig()))
{
odb.createIfNotExists("test", ODatabaseType.PLOCAL);
ODatabaseSession db = odb.open("test", "admin", "admin");
db.getMetadata().getSchema().getOrCreateClass("pupil");
long size = db.countClass("pupil");
System.out.println("size: "+size);
long t = System.currentTimeMillis();
db.declareIntent(new OIntentMassiveInsert());
for (int i=0; i<1000000; i++)
{
OElement doc = db.newElement("pupil");
doc.setProperty("id",size+i);
doc.setProperty("json", randomString());
doc.save();
if (i % 100 == 0)
{
System.out.println(System.currentTimeMillis()-t);
t = System.currentTimeMillis();
db.commit();
}
}
}

}

force stop the JVM while the program is running.
then restart

PS: adding: java option -Dstorage.useWAL=false does not help.

PS: 		conf.getConfigurations().setValue(OGlobalConfiguration.USE_WAL, false);
neither

Hi, I see that check points are absent in WAL did you run load with WAL disabled ? If so please enable WAL and run again. WAL is used to restore database after crash it should not be disabled.

Hi, WAL is on:

public static void main(String[] args)
{
OrientDBConfig conf = OrientDBConfig.defaultConfig();
conf.getConfigurations().setValue(OGlobalConfiguration.USE_WAL, true);
try (OrientDB odb = new OrientDB("embedded:./db", conf))
{
odb.createIfNotExists("test", ODatabaseType.PLOCAL);
ODatabaseSession db = odb.open("test", "admin", "admin");
if (!db.getMetadata().getSchema().existsClass("pupil"))
{
OClass c = db.getMetadata().getSchema().createClass("pupil");
c.createProperty("id", OType.LONG);
c.createIndex("idx_pupil_id", OClass.INDEX_TYPE.UNIQUE, "id");
}
long size = db.countClass("pupil");
System.out.println("size: "+size);
long t = System.currentTimeMillis();
db.declareIntent(new OIntentMassiveInsert());
for (int i=0; i<1000000; i++)
{
OElement doc = db.newElement("pupil");
doc.setProperty("id",size+i);
doc.setProperty("json", randomString());
doc.save();
if (i % 100 == 0)
{
System.out.println(System.currentTimeMillis()-t);
t = System.currentTimeMillis();
db.commit();
}
}
}

}

INFO: $ANSI{green {db=test}} 5 indexes were restored successfully, 0 errors
Jun 30, 2019 7:56:55 PM com.orientechnologies.common.log.OLogManager log
INFO: $ANSI{green {db=test}} Indexes restore after crash was finished.
size: 208
Jun 30, 2019 7:56:56 PM com.orientechnologies.common.log.OLogManager log
SEVERE: $ANSI{green {db=test}} Magic number verification failed for page 453 of pupil.pcl.
Jun 30, 2019 7:56:56 PM com.orientechnologies.common.log.OLogManager log
SEVERE: $ANSI{green {db=test}} Magic number verification failed for page 453 of pupil.pcl.
java.lang.Exception
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.dumpStackTrace(OWOWCache.java:2306)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.verifyMagicAndChecksum(OWOWCache.java:2264)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFileContent(OWOWCache.java:2164)
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.load(OWOWCache.java:1137)
at com.orientechnologies.orient.core.storage.cache.chm.AsyncReadCache.lambda$doLoad$0(AsyncReadCache.java:150)

I see I will try to reproduce that, if that will not be possible on my side, I will ask for the broken database.

Reproduced and fixed, tried several times and all is OK on my side. I will push in an hour. Will you able to build code from the branch or I need to provide you new build?

Hi, @rzorzorzo do I need to provide you a special distribution to test this issue?

hello,
i will try to build it. i hope i will have time for this on the weekend.

tested with maven build 3.1.0-M3. all OK.

Cool thank you. We release 3.0.22 in a couple of days.


Add an image to use models/gemini-pro-vision, or switch your model to a text model.

Description of the bug:
When I use the model gemini-vision-pro, I only give it the text . I will give me that bug. How can I solve it ?
Actual vs expected behavior:
No response
Any other information you'd like to share?
No response

If you want to use text, use gemini-pro. If you want to use images, using gemini-pro-vision. You are free to switch between them as necessary.

+1


:; in terminal while installing

Type: Bug
While installing packages or creating react app in terminal when the installation begins the :; this symbol is running instead of [......./] installation and loading is not visible
VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz (4 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
7.90GB (2.70GB free)

Process Argv
--crash-reporter-id 2679159f-51bb-4fe7-bb33-9308f2bb258a

Screen Reader
no

VM
0%

Extensions (23)

Extension
Author (truncated)
Version

better-comments
aar
3.0.2

airship-react-snippets
air
0.0.8

html-class-suggestions
And
1.2.1

codeium
Cod
1.8.36

vscode-markdownlint
Dav
0.55.0

es7-react-js-snippets
dsz
4.4.3

gitlens
eam
14.9.1

vscode-html-css
ecm
2.0.9

prettier-vscode
esb
10.4.0

auto-rename-tag
for
0.1.10

code-runner
for
0.12.2

copilot
Git
1.188.0

copilot-chat
Git
0.15.1

autocorrect
hua
2.6.4

vscode-edge-devtools
ms-
2.1.5

sublime-keybindings
ms-
4.1.10

vscode-css-peek
pra
4.4.1

LiveServer
rit
5.7.9

es7-react-js-snippets
rod
1.9.3

indenticator
Sir
0.7.0

vscode-icons
vsc
12.7.0

vscode-todo-highlight
way
1.0.5

JavaScriptSnippets
xab
1.8.0

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
da93g388:31013173
pythoncenvptcf:31043158
fchga941:31038042
pythonprt:31039817
dwnewjupytercf:31039676

was this resolved?

Looks like the app is using braille symbols to show progress, the font you are using does not feature monospace braille and therefore it it leaking into the following cell. This is working as designed from our perspective.

I didn't change anything. It just started with the recent update
Corey McCoy
On Sun, Sep 22, 2024, 10:23 AM Daniel Imms @.***> wrote:

Looks like the app is using braille symbols to show progress, the font you
are using does not feature monospace braille and therefore it it leaking
into the following cell. This is working as designed from our perspective.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/212418#issuecomment-2366836433,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWE5I7MJSIURR4MF5ZFNMTZX3OIXAVCNFSM6AAAAABHQC5AD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRWHAZTMNBTGM
.
You are receiving this because you commented.Message ID:
@.***>

@CoreyMcCoy it's hard to say what caused it to happen on your end, but it's valid that it's showing up like this as we do not do any special rendering of the braille chars. The fix is to tweak your fontFamily setting.

I'll try it. But again "I" didn't change anything. It was working fine
prior to the update. Installing packages before the update worked as it
always had. So it is on your end
Corey McCoy
On Mon, Sep 23, 2024, 7:22 AM Daniel Imms @.***> wrote:

@CoreyMcCoy https://github.com/CoreyMcCoy it's hard to say what caused
it to happen on your end, but it's valid that it's showing up like this as
we do not do any special rendering of the braille chars. The fix is to
tweak your fontFamily setting.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/212418#issuecomment-2368057317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEWE5I6NJOOGWGHH2IFMOFTZYABYNAVCNFSM6AAAAABHQC5AD6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRYGA2TOMZRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@CoreyMcCoy could be in the OS, could be an Electron/Chromium update, could be an extension messing with settings, could be us. Hard to say exactly. It's a waste of time trying to look into this imo since it's literally working as designed, depending on the font setting.


Security Medical Kit

Short description

A simple addition of a reskinned and bigger combat medkit made for security use that can only hold medical items.
Why we need to add this

I think it looks cool, and it helps a bit with space management as brigmedic as you get a round-start empty medkit to stuff your meds into that fits nicely in the 2x2 hole left in your belt.
Media (Video/Screenshots)

https://github.com/user-attachments/assets/848ebe89-d474-428d-81a3-e1772ebd18e2
Checks

[x] I do not require assistance to complete the PR.
[x] Before posting/requesting review of a PR, I have verified that the changes work.
[x] I have added screenshots/videos of the changes, or this PR does not change in-game mechanics.
[x] I affirm that my changes are licensed under the Starlight Fork License and grant permission for use in this repository under its conditions.

Changelog

:cl: Killer Tamashi

add: Added BrigKit to roundstart Brigmedics.

Tested. Brigmedic spawns with brigkit in backpack and the files have been moved to the folders within the _Starlight directory

merge master(Starlight), fix crlf error

Yeah I don't know how to fix the CRLF error. Can someone look at the file?


remove light returns unworkable image

Hi,
I've been using the same code for removing light (using the division technique) with the supplied pattern.pgm file (Chapter 6, I am using OpenCV 4.0.1).
The result is as follows:

You can see that in the removedLight window the nut is barely noticeable which obviously causes our threshold to return all ones.
Applying a simple subtraction of pattern - img gives a better result but after Extract Features I'm losing the center hole of the nut is this normal? I though that the CCOMP will retain the inner contours, without it the area feature is going to be skewed...

I'd appreciate your help!

Hi, sorry to reply so late.
I use the following command:
./bin/Chapter5 ../data/test.pgm ../../Chapter_06/data/pattern.pgm --lightMethod=1

And works properly, what is your execute command for light removal division?


Allow use of relative and speed properties for InputEventScreenDrag on Windows

Fixes #28319

This fixes my project, which was based off of Godot 3.1.1-stable.

Thanks!

And congrats for your first PR :)


Remove tilde prefix from compact output

Resolves #32
prettyMilliseconds(1337, {compact: true});
//=> '1s'

Question: In this PR, I removed the ~ from the output when compact: true, as described in the issue. I noticed that the unitCount option also adds a ~ prefix to its output. Should it be removed as well?

Should it be removed as well?

Yes


dotnet: october 2024 releases

We now explicitly used the declared SDK to build VMR stage0.  This allows the binary and source-built packages to be upgraded independently.  It also makes automating updates possible, since we don't have to search for a version of Private.SourceBuilt.Artifacts that matches the binary SDK.
2024-10-12T11:12:26.5215196Z Some new/changed Nix files are not properly formatted
2024-10-12T11:12:26.5216488Z Please go to the Nixpkgs root directory, run `nix-shell`, then:
2024-10-12T11:12:26.5218648Z nixfmt 'pkgs/development/compilers/dotnet/8/bootstrap-sdk.nix' 'pkgs/development/compilers/dotnet/9/bootstrap-sdk.nix'

These are the only nixfmt failures, and I'd like to leave them unformatted for now, to match the other SDKs, since they are generated.
Cc: @NixOS/dotnet
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.

  I could move it to a separate PR if you prefer.
It could be reproduced by rolling back dotnet 9 to rc.1 and running nix-shell maintainers/scripts/update.nix --argstr package dotnetCorePackages.dotnet_8.vmr.  I assume it's just because the upgrade process writes enough to stderr to cause it.
I tested:

updating dotnet 8/9
updating mailpit in order to cover 'commit' in package['supportedFeatures'].
forcing a failure to make sure stderr gets printed and goes in the log file
removing newVersion and files from the output to test those fallback code paths

@corngood do you know if this update fixes the issue mentioned on https://github.com/NixOS/nixpkgs/pull/342299#issuecomment-2378263002?

nixpkgs-review result
Generated using nixpkgs-review.


Redux

Here's redux wired up. I added a trivial test button that displays a string that says 'logged in!', even though it doesn't really do anything. But it goes through redux correctly, so feel free to replace it with actual functionality.

This looks good Casey! I will merge this in with mine and make another PR so we can work off of that version.


ChiP-Seq pipeline: adapter trimming requires "trimmed" folder to be created during the run, but it is not

(cc @LMannarino)
As the subject says, adapter trimming (I'm mentioning the ChiP-Seq because I've done it, but might affect other runs). needs a trimmed directory to be created during the run in the work directory. However, at the moment this does not occur, and thus the pipeline fails (version 9.6.0; unfortunately I'm tied to stable releases due to a policy that has been requested to me).

Hi @lbeltrame and @LMannario,
sorry about the issue. I cannot reproduce this for that version. I got the trimmed folder in the run directory and the trimmed files. Maybe the logs/config files help to debug the issue you are having? Maybe it is some option related to the trimming step.
cheers

This is a part of the error shown:
 File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/multi.py", line 86, in run_multicore
    for data in joblib.Parallel(parallel["num_jobs"])(joblib.delayed(fn)(x) for x in items):
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 804, in __call__
    while self.dispatch_one_batch(iterator):
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 662, in dispatch_one_batch
    self._dispatch(tasks)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 570, in _dispatch
    job = ImmediateComputeBatch(batch)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 183, in __init__
    self.results = batch()
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/joblib/parallel.py", line 72, in __call__
    return [func(*args, **kwargs) for func, args, kwargs in self.items]
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/utils.py", line 51, in wrapper
    return apply(f, *args, **kwargs)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/multitasks.py", line 31, in trim_sample
    return sample.trim_sample(*args)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/sample.py", line 57, in trim_sample
    out_files = trim_adapters(data)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/bam/trim.py", line 29, in trim_adapters
    return _trim_adapters(to_trim, out_dir, name, config)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/bam/trim.py", line 44, in _trim_adapters
    out_files = _cutadapt_trim(fastq_files, quality_format, to_trim, out_files, config)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/bam/trim.py", line 60, in _cutadapt_trim
    do.run(cmd.format(**locals()), message)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 21, in run
    _do_run(cmd, checks, log_stdout)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/bcbio/provenance/do.py", line 95, in _do_run
    raise subprocess.CalledProcessError(exitcode, error_msg)
subprocess.CalledProcessError: Command 'set -o pipefail; /mnt/data/bcbio/anaconda/bin/cutadapt --times=2 --quality-base=33 --quality-cutoff=5 --format=fastq --adapter=AGATCGGAAGAG --adapter=CTCTTCCGATCT  --minimum-length=25  -o /mnt/data/projects/LPS190-2/LPS190-2_analysis/work/trimmed/CTRL.trimmed.fastq.gz /mnt/data/projects/LPS190-2/raw_data/CTRL_R1.fastq.gz
Traceback (most recent call last):
  File "/mnt/data/bcbio/anaconda/bin/cutadapt", line 10, in <module>
    cutadapt.main()
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/cutadapt/scripts/cutadapt.py", line 524, in main
    writer = open_writer(options.output, options.paired_output)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/cutadapt/seqio.py", line 679, in open
    return fastq_handler(file1)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/cutadapt/seqio.py", line 528, in __init__
    file = xopen(file, "w")
  File "/mnt/data/bcbio/anaconda/lib/python2.7/site-packages/cutadapt/xopen.py", line 176, in xopen
    return buffered_writer(gzip.open(filename, mode))
  File "/mnt/data/bcbio/anaconda/lib/python2.7/gzip.py", line 34, in open
    return GzipFile(filename, mode, compresslevel)
  File "/mnt/data/bcbio/anaconda/lib/python2.7/gzip.py", line 94, in __init__
    fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: '/mnt/data/projects/LPS190-2/LPS190-2_analysis/work/trimmed/CTRL.trimmed.fastq.gz'

And the reason is because trimmed doesn't exist. Trimming options are the same as the illumina-chipseq template provided by bcbio.

Hi @lbeltrame ,
I was looking at the code, and this folder is created by transaction_file function. I only see a problem if the temporary directory is set up somewhere else, then this folder doesn't get created in the work directory. I forced the creation of the folder there.
The only other option I can think of is some kind of error just before the command runs with the file system avoiding to get this directory there.
I don't know if this commit can get into the release like a patch if you want to use it (since you mention that only can use release version). I will mention to @chapmanb.
thanks and hope this fixes it

Luca -- you can't test fixes on development versions? We don't do patches of releases, but could certainly roll a new release some point relatively soon. There are a couple of more things that need to go in and then we could do. In the short term, can you install a development version separate from your production version to ensure Lorena's fixes resolve your issue?

Unfortunately after issue #1067 hit us hard (but I no longer see that, luckily), I got requested to avoid upgrading unless needed (= stable versions only), and there are no real "development" machines (I handle them all myself on a best-effort basis).
I'll see about upgrading one of the clusters and try again when I get around to it.

Luca;
Understood. You don't need a separate development machine, but could install a development version of bcbio into a different directory, then put that in your PATH when testing. You'd have to symlink data directories to avoid downloading twice but otherwise that's the easiest way to test fixes but maintain a production install for your runs. Hope this helps.

It should be fixed in the last release, let me know if you have any other problem.
thanks a lot @lbeltrame


Remove counterproductive call to 'cat' in setup script

Description and Motivation
Including a call to 'cat' in these scripts nullifies the purpose of the setup-wrapper.sh script, which moves error logs to the output file.
Change type

[x] Bug fix
[ ] New feature
[ ] Enhancement
[ ] Breaking change (breaks backward compatibility)

Checklist:

[ ] All tests passed
[x] The code follows the code style and conventions of this project
[ ] The change requires a change to the documentation
[ ] I have updated the documentation accordingly

This change is

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: zadixon sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@zadixon does the log include secrets?

I've updated the PR description to better reflect the goal of preventing the logging of secrets. Sorry about the wording, I meant that by catting the output of the .log file, the setup-wrapper.sh script was effectively not doing anything different than if the script hadn't been there at all, which meant that the call itself was counterproductive with regard to the purpose of the script.
I agree that this is a short-term fix and doesn't address the underlying problem. However, I'd also argue that we shouldn't have our scripts be capable of producing logs with secrets to begin with. These secrets get logged because they are echoed to stdout due to the set -ex command that is run at the beginning of setup.sh. When the script fails, all stdout and stderr content is grabbed by ARM. I'm of the opinion that secrets shouldn't be in stdout/stderr to begin with.
At the same time, whether we can reasonably expect third party solutions to not expose secrets in this way is an important consideration, and I agree that we should see if the ARM team has any experience with generically avoiding logging secrets while still allowing us to gather useful logs.


added a toggle switch in setting section which changes the content's theme

give @Sweety1621 75 points


Storybook default webpack config does not support CRA v2 w/ CSS modules

Bug or support request summary
From https://storybook.js.org/configurations/custom-webpack-config/:

The default Webpack config of Storybook is balanced for a medium-size project (specially created with Create React App) or a library.

I am assuming that this means that Storybook's default webpack config should be able to handle a new project created by CRA. CRA v2 now has opt-in support for CSS modules. When I created a new CRA project using CRA v2.0.4, I used CSS modules to style a component; however, the component styles do not appear when displaying the component in Storybook.
If this means that I need to extend Storybook's webpack config to add CSS module support, please close this issue. However, it's unclear if Storybook is meant to work out-of-the-box with CRA if this is the case. I can make a PR to add documentation around this if Storybook will not add CSS module support out of the box like CRA v2 has.
Steps to reproduce
I have a reproducible example in this repo.

Create a project with npx create-react-app my-app
Add Storybook to the project with getstorybook
Create a component that imports a CSS module.
Render the component in a Storybook story.

If you import the component that uses CSS modules into App.js and run yarn run start, you can see that the styles are applied correctly. However, if you run Storybook with yarn run storybook, the styles do not apply.
Please specify which version of Storybook and optionally any affected addons that you're running
package.json
{
  "name": "storybook-css-module",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "react": "^16.5.2",
    "react-dom": "^16.5.2",
    "react-scripts": "2.0.4"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "storybook": "start-storybook -p 9009 -s public",
    "build-storybook": "build-storybook -s public"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": [
    ">0.2%",
    "not dead",
    "not ie <= 11",
    "not op_mini all"
  ],
  "devDependencies": {
    "@storybook/react": "^3.4.11",
    "@storybook/addon-actions": "^3.4.11",
    "@storybook/addon-links": "^3.4.11",
    "@storybook/addons": "^3.4.11",
    "babel-core": "^6.26.3",
    "babel-runtime": "^6.26.0"
  }
}

Affected platforms
Tested in Chrome v69
Screenshots / Screencast / Code Snippets (Optional)
Repo: https://github.com/matthamil/storybook-css-module-CRA2
Text component when running yarn run start:

Text component when running yarn run storybook:

Work summary
Add CSS module support to Storybook's webpack config.
Where to start
Take a look at ./src/Text.js and ./src/Text.module.css. The CSS module includes one class .text which applies a red color and 2rem font-size to whatever element is using .text.
Acceptance criteria
Default storybook webpack config can handle CSS modules out of the box.
Who to contact
anyone familiar with Storybook's default webpack config.

For anyone else who created a CRA v2 project that uses CSS modules, I extended the default webpack config by doing the following:

create a webpack.config.js file in the .storybook directory
Add the following CSS module rule:

// ./.storybook/webpack.config.js
const cssModuleRegex = /\.module\.css$/;

module.exports = {
  module: {
    rules: [
      {
        test: cssModuleRegex,
        loaders: [
          require.resolve('style-loader'),
          {
            loader: require.resolve('css-loader'),
            options: {
              importLoaders: 1,
              modules: true,
              localIdentName: '[name]__[local]___[hash:base64:5]'
            }
          }
        ]
      }
    ]
  }
};

Now CSS modules should work for your CRA + Storybook project.

If we are talking about compatibility with CRA2, I think we need to support as much as possible by default. For example, in @storybook/angular, we do recognize that there is a usage of angular-cli and we try to use its configuration as much as possible.
So extending the custom webpack.config.js is kinda workaround.
Do you want to PR the better CRA2 compatibility for css modules?

@igor-dv I can take this on. Depending how it goes, I may be able to take on #4298 as well.
Just a quick question, would you want me to update examples/cra-kitchen-sink to<EMAIL_ADDRESS>as part of this PR?

I can take this on

That will be cool 👍

would you want me to update examples/cra-kitchen-sink to<EMAIL_ADDRESS>
I would say yes

Thanks for the snippet @matthamil
For anybody who wants to use SCSS modules, you can modify it slightly to use:

module.exports = {
  module: {
    rules: [
      {
        test: sassModuleRegex,
        loaders: [
          require.resolve('style-loader'),
          {
            loader: require.resolve('css-loader'),
            options: {
              importLoaders: 2,
              modules: true,
              localIdentName: '[name]__[local]___[hash:base64:5]'
            }
          },
          require.resolve('sass-loader'),
        ]
      }
    ]
  }
};

@chadfawcett please join our discord: https://discord.gg/sMFvFsG
So we can help you faster.

@igor-dv @chadfawcett and I discussed and he's on board what we think should be done.
We could use your advice and expertise about presets!
We came up with the idea of creating a CRA2 preset.
what do you think of that idea?
where should such a bit of code exist?
how do we use it? will it be added for all apps with react? or can we filter for CRA only?

I like the preset idea. The similar preset for angular is located in @storybook/angular. It detects that we are using angular-cli and changes things accordingly. If we can make the same for react, that'd be great. At least while the "custom" presets are not publicly exposed.
How can we detect that somebody is using cra ?

@robcaldecottvelo You've tried the alpha? I thought the fragment syntax should be supported there.
We're releasing 4.0.0 rc today

Hello, I am trying out the latest version of storybook (4.0.0-rc.0) and I was wondering if the sass and css modules support should work out of the box or do I need to do something special? I am getting the errors:
info @storybook/react v4.0.0-rc.0
info
info => Loading static files from: /Users/xxx/Development/Projects/yyy/zzz/version-2/dashboard-v2/public .
info => Loading presets
ERR! Error: Cannot find module 'babel-loader/package.json' from '/Users/xxx/Development/Projects/yyy/zzz/version-2/dashboard-v2'

Hmm, now it complains about babel-loader missing but yarn add babel-loader --dev seems to fix it for now. Let's see for how long :)

@weyert you'll need to do something special for now. Per the conversation earlier in this thread, it was decided that compatibility with CRA2 (which includes support for sass & css modules out of the box) will be included in the future.

Sorry, somehow I thought it was included as part of today's release!

@weyert Further discussion can be found on the PR https://github.com/storybooks/storybook/pull/4405

for anyone else who comes across this I had issues with sass-loader not liking the being used twice, so i came up with this solution
module.exports = (BaseConfig, env, defaultConfig) => {
  const rules = [];
  // Do this because sass-loader does not like it when there are
  // multiple declarations of it in rules.. and we want css modules
  // turned on
  defaultConfig.module.rules.forEach(rule => {
    const testCssString = "myscss.scss";
    const regex = RegExp(rule.test);
    if(!regex.test(testCssString)){
      rules.push(rule);
    }
  });
  defaultConfig.module.rules = rules;

  defaultConfig.module.rules = [
    {
      test: /\.scss$/,
      include: srcDir,
      loaders: [
        "style-loader",
        {
          loader: "css-loader",
          options: {
            importLoaders: "1",
            localIdentName: "[name]__[local]___[hash:base64:5]",
            modules: true,
          }
        },
        "sass-loader"
      ]
  },
      {
        test: /\.svg$/,
        issuer: {
          test: /.jsx?$/
        },
        use: ['@svgr/webpack']
      },
  ...rules
  ]

This is how I ended up getting css modules to work
// .storybook/webpack.config.js

const setCssModulesRule = rule => {
  const nextRule = rule;
  const cssLoader = rule.use[1];  // admittedly lazy, but the array was mixed types 🤷♀
  const nextOptions = { ...cssLoader.options, modules: true }

  cssLoader.options = nextOptions;
  return nextRule;
}

module.exports = async ({ config, mode }) => {
  const rules = config.module.rules.map(rule => {
    const isCssRule = rule.test.toString().indexOf('css') !== -1;
    let nextRule = rule;

    if (isCssRule) {
      nextRule = setCssModulesRule(rule);
    }

    return nextRule;
  });

  config.module.rules = rules;
  return config;
};


Feature: Multiple Users

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
This feature, would add the ability to have the main user, (admin user) to add other users, and the main user has the ability to give these users permissions, so they can only view the monitors, status pages etc. Or they can have management permissions, such as add, remove, edit
Fixes #128
Type of change
Please delete any options that are not relevant.

New feature (non-breaking change which adds functionality)
This change requires a documentation update (it could, but it really depends, will leave this here though)

( Just up for discussion and the okay from the project owner (@louislam) before I make any code, as the PR Rules go so none of these apply atm
Checklist

[ ] My code follows the style guidelines of this project
[ ] I ran ESLint and other linters for modified files
[ ] I have performed a self-review of my own code and tested it
[ ] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[ ] My changes generate no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

This feature I agree that will put Uptime Kuma into another level.
However, my answer is simply no. I don't recommend anyone working on it in this stage because it is a super super big task.

Server + Frontend more than 150+ files have to modify in order to handle different permissions I believe.
Add new components for managing users, permissions and user roles.
A lot of discussions on how to define permissions. (e.g. If User A created a monitor, should it be visible to Admin? If Admin created a monitor, should it be visible to User A?)
Security, there are a lot of API key such as notifications inside Uptime Kuma. Read-only user should not see it?
Testing and reviewing all changes are always hardest part.

Didn't mention there are still so many pull requests I haven't reviewed yet. I think I will put my time on them first.

Well, I will say I begun this as a test to see it was even possible, I created ways to add sun users, remove them and let them login, now I haven’t looked at permissions but the way I was going to add them, a proper way, would use way less than 150 files, but If you still want a pause on this I can close it

@ItIzJR Would it be possible for you to share what you have done so far? It might help in making a decision if we can see how you are planning to implement this.

Would you like images or code examples?

You could probably just commit it (you can always revert the commit later), or you could copy in some examples.

And you just want what I have done? Which is adding / deleting sub users and logging them in?

Yeah, just something so that we can see in code how you are thinking about implementing multiple users.

It didn't import correctly for some reason, so until I get back on tomorrow it'll have to be this way, if you check the repo for this under the "main" branch, the files will be in the areas with the commit message "sub user files"

and... I just realized I forgot to include the most important part when I committed them, which was the login stuff, hopefully this will get you the main idea of how I will be planning on implementing these files though, also if you want I can also come up with the best way of implementing permissions, with as few changes as possible, while being secure as possible, I have actually done this before so I don't think it will be too hard.

I just realized I forgot to include the most important part when I committed them

I see nothing changed in File changed tab.

That would be due to the weird way GitHub imported it, whenever I get back from work if I have time I’ll fix it, but like I said the changes are in the files with “sub user files” in the main branch if you want to manually look at them, Ik it takes a lot more time, or you can wait till I get it to be fixed.

Alright I have added all the files into main and they show up under the changes

I see the problem here. The reason we cannot see the commits is because they have been made on the main branch of your repo but this PR is for the master branch of your repo. If you just change the branch this PR comes from we will be able to see the changes

Oh I didn’t notice that I’ll update it real quick, then I have to go but that gives you guys time to take a look

I guess GitHub decided it's gonna be GitHub and not let me change it..?

Alright I just merged it should be good

just my 2cents.
If you build something like this you need to plan for support of different authentication methods in mind for example LDAP/AD etc

just my 2cents. If you build something like this you need to plan for support of different authentication methods in mind for example LDAP/AD etc

Yes, definitely, the support (or at least designing/planning to support) of external authentication systems is a must, especially if we want to future proof.

Already had that in mind, and ill get the code up today for you to look at

Hi, because Uptime can only create one user, there is one case: if we can't contact the admin (especially 2FA is enabled), then it seems there is no way to log in to Uptime. Maybe provide a way to account recovery?

Sorry for my delay, I’ll get the code situated asap, been a busy week at work. I would definitely be able to implement that, thanks for the suggestion, and that is if they end up approving this.

Is this going to be worked upon?

@louislam In terms of a permissions system, could we do something a bit like OAuth scopes? E.g: monitor:read, monitor:write and so on. For another example of these, you can have a look at the GitHub personal access tokens. This would allow us to just have all the scopes for a user in the database (schema to be determined) and then each page simply checks to see if the user has the required scope for that specific page. This would also probably make it fairly simple to implement the permissions levels for OAuth in future if that is desired. This would put the requirement to validate permissions on the individual pages instead some centralised place, making it more scalable (in my opinion). This would also allow admins fine grained control over user permissions. I would be interested to hear what you, and others think.
P.s. Should we use some sort of discussion system where people can discuss the big changes that don't quite fit into issues (like user permissions). Perhaps enabling GitHub discussions could be an option?

Why not just start without permission system and make all users admin at first?

Uptime kuma is light-weight enough to use multiple instance for different stuffs, and the minimal support for multi-user is enough for most(maybe up to 80%) cases.
This would be easier to impl, with less effort and less effect of current codebase(maybe less than 20% compared to with permssion system).
This would have less UI/UX or design work, make it much acceptable by louislam

Gonna be honest forgot this was open, Louis didn’t seem to be a fan of having someone make this so I privately made it myself so that I could use the feature I wanted, if anyone else were to want this I could help them with implementing it, but it has multiple user and permission system already.

Why not just start without permission system and make all users admin at first?

Uptime kuma is light-weight enough to use multiple instance for different stuffs, and the minimal support for multi-user is enough for most(maybe up to 80%) cases.
This would be easier to impl, with less effort and less effect of current codebase(maybe less than 20% compared to with permssion system).
This would have less UI/UX or design work, make it much acceptable by louislam

Just make my thought clear: we need to push things forward, and build from small part maybe useful enough, also acceptable by louislam with less UI/UX and design stuff.
What I really want to do is introduce this awsome feature into Uptime Kuma, in a way louislam would like it.
Sorry to bother you, but let me ping @louislam cause I want to know your opinion.

Just make my thought clear: we need to push things forward, and build from small part maybe useful enough, also acceptable by louislam with less UI/UX and design stuff.
What I really want is introduce this awsome feature into Uptime Kuma, in a way louislam would like it.
Sorry to bother you, but let me ping @louislam cause I want to know your opinion.

Yeah I gotcha, I’ve got a working version and the only UI added is a sub user management system and permission system, all we would need is Louis’s approval and then I could move the private repo into the one for this pr.

please add this feature.

How do i install ItIzJR's multi user uptime-kuma it just says:
error: pathspec '1.19.2' did not match any file(s) known to git

@ItIzJR Could you close this PR?
https://github.com/louislam/uptime-kuma/pull/3571 implements the same feature, but is more mature
⇒ has a chance of getting merged ^^


Allow client to request specific png format

In certain scenarios it would be very useful being able to get the tiles in PNG32 (or 24) instead of PNG8.
The reason is that at times you need to be absolutely certain that the colors generated in cartoCSS are persistent, for example, when you do canvas processing of the tiles and need to encode values in the color palette. Currently the colors vary slightly from tile to tile

Taking this one!

Oh yeah!
http://i.imgur.com/gsFyUXe.gifv

This was implemented in 1.2.0 release.

Big kudos to @dgaubert !!! :ship: ing :it:


memory.x & build.rs in the library's crate

0.5
STM32F411CEUx, but I suppose any MC with RAM size different from 20 KiB is affected
Display resolution and interface: not applicable

Description of the problem/feature request/other
Seems like the provided memory.x file overrides the user-provided memory.x file when building a binary using the cortex-m-rt crate. Do you think it might be possible to exclude both build.rs and memory.x files from the crate's library package?
Test case
Add ssd1306 = "0.5" to the target's Cargo.toml
#[cortex_m_rt::entry]
fn main() -> ! {
    const LARGE_ARRAY: [u8; 40 * 1024] = [0; 40 * 1024];
    loop {}
}

Expect a hardfault. One might need to use flip-link to actually see the hardfault when the seemingly segmentation fault occurs.
Removing ssd1306 from dependencies resolves the problem.
It seems like the link.x script provided by the cortex-m-rt crate simply includes any memory.x found, and since the build.rs you provide adds a viable link search path, the user-defined memory.x is ignored. It can be simply proved by removing the user's memory.x and observe the compilation succeeds.

Please see #144 for a possible solution

Please see #144 for a possible solution

Something seems off here. A user provided memory.x should never be overridden and the included one should never be used in user projects. In fact I've used the published crates in a quite a few projects (including one which runs on an MCU which only has 6kB of RAM and 32kB of flash) and non-STM MCUs which have different addresses so a use of the included memory.x would have resulted in easily noticeable fatal errors. This would mean there has either been a severe regression in this crate or something else is wrong in your environment.

Something seems off here. A user provided memory.x should never be overridden and the included one should never be used in user projects. In fact I've used the published crates in a quite a few projects (including one which runs on an MCU which only has 6kB of RAM and 32kB of flash) and non-STM MCUs which have different addresses so a use of the included memory.x would have resulted in easily noticeable fatal errors. This would mean there has either been a severe regression in this crate or something else is wrong in your environment.

A user provided memory.x should never be overridden

How could that be enforced? link.x from the cortex-m-rt simply includes a memory.x without any path hints: https://github.com/rust-embedded/cortex-m-rt/blob/3a2ae355a272246dd3650f415fbb3895deb19571/link.x.in#L23
And I guess it is up to the linker to find the file, perhaps it simply tries various paths it is provided with. The build.rs provided by ssd1306 adds a linker search path: https://github.com/jamwaffles/ssd1306/blob/09e7982c08505121b7d54fa6d9aef979aa67b53b/build.rs#L10
So in the end it is up to the order in which paths are scanned to decide which memory.x is finally included. But it's just my speculations, I might be absolutely mistaking.
Anyhow, I'll try to set up a clean environment and reiterate the building process to find out whether my local environment is somehow twisted.
Thanks for a fast response btw :)

A user provided memory.x should never be overridden

How could that be enforced? link.x from the cortex-m-rt simply includes a memory.x without any path hints: https://github.com/rust-embedded/cortex-m-rt/blob/3a2ae355a272246dd3650f415fbb3895deb19571/link.x.in#L23
And I guess it is up to the linker to find the file, perhaps it simply tries various paths it is provided with. The build.rs provided by ssd1306 adds a linker search path: https://github.com/jamwaffles/ssd1306/blob/09e7982c08505121b7d54fa6d9aef979aa67b53b/build.rs#L10
So in the end it is up to the order in which paths are scanned to decide which memory.x is finally included. But it's just my speculations, I might be absolutely mistaking.
Anyhow, I'll try to set up a clean environment and reiterate the building process to find out whether my local environment is somehow twisted.
Thanks for a fast response btw :)

So, steps to reproduce:

Set up a fresh project:

$ cargo install cargo-generate
$ cargo generate \
  --git https://github.com/knurling-rs/app-template \
  --branch main \
  --name test-ssd1306

Install flip-link: $ cargo install flip-link
Add the required target: $ rustup target add thumbv7em-none-eabihf
Modify Cargo.toml, .cargo/config and other files to use the required MCU. All the required changes can be found by running $git grep TODO
Try to build the project: $ cargo build. The build will fail with the following error:

  = note: rust-lld: error: /test-ssd1306/target/thumbv7em-none-eabihf/debug/build/cortex-m-rt-c8fd83f10c447ef5/out/link.x:23: cannot find linker script memory.x
          >>> INCLUDE memory.x
          >>>         ^

So far it is expected.
6. Add ssd1306 = "0.5" dependency to the project's Cargo.toml
7. Build the project with $ cargo build. The build succeeds!
$ cargo build
    Updating crates.io index
  Downloaded byte-slice-cast v0.3.5
  Downloaded display-interface-i2c v0.4.0
  Downloaded display-interface-spi v0.4.0
  Downloaded display-interface v0.4.0
  Downloaded embedded-graphics v0.6.2
  Downloaded ssd1306 v0.5.0
  Downloaded 6 crates (2.6 MB) in 1.08s (largest was `ssd1306` at 2.5 MB)
   Compiling display-interface v0.4.0
   Compiling byte-slice-cast v0.3.5
   Compiling ssd1306 v0.5.0
   Compiling embedded-graphics v0.6.2
   Compiling display-interface-i2c v0.4.0
   Compiling display-interface-spi v0.4.0
   Compiling test-ssd1306 v0.1.0 (/test-ssd1306)
    Finished dev [optimized + debuginfo] target(s) in 4.37s

Please note, that no user-provided memory.x exists in the project.
8. Let's verify that a memory.x file provided by the ssd1306 crate exists and remove it:
$ find . -name 'memory.x'
./target/thumbv7em-none-eabihf/debug/build/ssd1306-7856f396f8c230ad/out/memory.x
$ find . -name 'memory.x' -delete

Force re-linking by touching all the rust files in the project and try to build it again:

$ touch **/*.rs
$ cargo build

And it fails with the linking error as before:
  = note: rust-lld: error: /test-ssd1306/target/thumbv7em-none-eabihf/debug/build/cortex-m-rt-c8fd83f10c447ef5/out/link.x:23: cannot find linker script memory.x
          >>> INCLUDE memory.x
          >>>         ^

I've performed all the steps in a docker container, so the environment is as clean as possible :)

So, steps to reproduce:

Set up a fresh project:

$ cargo install cargo-generate
$ cargo generate \
  --git https://github.com/knurling-rs/app-template \
  --branch main \
  --name test-ssd1306

Install flip-link: $ cargo install flip-link
Add the required target: $ rustup target add thumbv7em-none-eabihf
Modify Cargo.toml, .cargo/config and other files to use the required MCU. All the required changes can be found by running $git grep TODO
Try to build the project: $ cargo build. The build will fail with the following error:

  = note: rust-lld: error: /test-ssd1306/target/thumbv7em-none-eabihf/debug/build/cortex-m-rt-c8fd83f10c447ef5/out/link.x:23: cannot find linker script memory.x
          >>> INCLUDE memory.x
          >>>         ^

So far it is expected.
6. Add ssd1306 = "0.5" dependency to the project's Cargo.toml
7. Build the project with $ cargo build. The build succeeds!
$ cargo build
    Updating crates.io index
  Downloaded byte-slice-cast v0.3.5
  Downloaded display-interface-i2c v0.4.0
  Downloaded display-interface-spi v0.4.0
  Downloaded display-interface v0.4.0
  Downloaded embedded-graphics v0.6.2
  Downloaded ssd1306 v0.5.0
  Downloaded 6 crates (2.6 MB) in 1.08s (largest was `ssd1306` at 2.5 MB)
   Compiling display-interface v0.4.0
   Compiling byte-slice-cast v0.3.5
   Compiling ssd1306 v0.5.0
   Compiling embedded-graphics v0.6.2
   Compiling display-interface-i2c v0.4.0
   Compiling display-interface-spi v0.4.0
   Compiling test-ssd1306 v0.1.0 (/test-ssd1306)
    Finished dev [optimized + debuginfo] target(s) in 4.37s

Please note, that no user-provided memory.x exists in the project.
8. Let's verify that a memory.x file provided by the ssd1306 crate exists and remove it:
$ find . -name 'memory.x'
./target/thumbv7em-none-eabihf/debug/build/ssd1306-7856f396f8c230ad/out/memory.x
$ find . -name 'memory.x' -delete

Force re-linking by touching all the rust files in the project and try to build it again:

$ touch **/*.rs
$ cargo build

And it fails with the linking error as before:
  = note: rust-lld: error: /test-ssd1306/target/thumbv7em-none-eabihf/debug/build/cortex-m-rt-c8fd83f10c447ef5/out/link.x:23: cannot find linker script memory.x
          >>> INCLUDE memory.x
          >>>         ^

I've performed all the steps in a docker container, so the environment is as clean as possible :)

I know it's a little bit late, but let me thank you @therealprof @jamwaffles and other people involved for the great crate!

I know it's a little bit late, but let me thank you @therealprof @jamwaffles and other people involved for the great crate!

Any time! Thank you for the kind words :blush:

Any time! Thank you for the kind words :blush:


[PeerAddressManager] Add inbound connections to the address book

Yeah but we cannot assume what the peers listening port is, notice it connects inbound on port 1749
Perhaps the port on the AddressFrom is the listening port?
In anycase we need store the PeerEndpoint but not sure with what listening port

This now looks more correct to me.

This looks good in theory, but note that there are situations where it will not work.
E.g. if we are behind a router that NATs incoming connections to its own IP address. This will result in the inbounds all having PeerEndPoint IP address 192.168.x.y, say, with varying ports. The AddressFrom could be anything. These variations will then pollute the peer database and offer little utility to the node.
A somewhat contrived/uncommon scenario, but something to be aware of.

@zeptin good point! Will the NAT not always assign 192.168.x.x ? I.e. in a range? We could check AddressFrom for intranet addresses like these and range filter them?
In other words if AddressFrom is a Loopback or falls in a 192.186 range then we use PeerEndpoint?
It might not be exact but at least we are filtering more unwanted addresses?

Not really related to this PR but PeerAddressManagerBehaviourMode enum is marked as [Flags], but the values for that enum are 0,1,2,3 and therefore it can't be used as flags. Also enum contains AdvertiseDiscover which is supposed to be combination for Advertise and Discover, so there is no need for that enum to be marked [Flags]- it already has combined states defined there without flags.

@noescape00 yes good spot, @fassadlr will remove the flags from that enum in another PR.
We also need to check that we ban based on IP only and not port and IP


[WIP] Update to hyper 0.12

I've updated shiplift to Hyper 0.12.
The biggest problem was the hyperlocal dependency, which hasn't been updated in several months.
One issue caused by this is the fact that hyper::Uri cannot parse unix socket URIs starting with a /. "unix:///foo".parse().unwrap() will always trigger a parse error.
In order to update this crate to 0.12, hyperlocal must also be updated to hyper 0.12. I've done that in softprops/hyperlocal#11, which has not landed yet.
This merge request cannot be merged until the hyperlocal PR has been merged and released to crates.io.
I also added support for the 304 Not Modified status code, which I encountered from Docker whilst creating containers.

Wow awesome! I'll dig into both these changes starting with hyperlocal. This is a hide weight off my shoulders

Wow awesome! I'll dig into both these changes starting with hyperlocal. This is a hide weight off my shoulders

No problem, thanks for writing such a great library!
Here's a few extra notes on this PR

We should probably remove the ownedtokio_reactor::Core from Transport

Because you cannot nest cores, this means that all Docker API calls made using this crate will fail with a tokio runtime error the moment a future spawned by one core attempts to spawn another future on a different core.
https://stackoverflow.com/questions/50644880/cannot-recursively-call-into-core-when-trying-to-achieve-nested-concurrency
This makes using shiplift in networking software running tokio impossible
One idea off the top of my head is to modify Transport and Docker so that a core (or maybe a Handle or Remote?) can be passed in when building the Docker object. Perhaps leverage the builder pattern and default to creating an owned core when a custom core is not specified.

I'm only testing over TCP on my machine, we should test Unix sockets before merging
I've got another WIP branch adding support for TCP upgrades and container streaming. This makes it possible to interactively stream stdout/stderr (possibly multiplexed) and stdin. My usecase is to spawn docker containers and run isolated, interactive shell sessions. I am using TCP because Docker does not support upgrades over Unix sockets. I'll probably push that PR up once this one lands so I don't have to rebase lots.

heads up published hyperlocal with the hyper version upgrades in<EMAIL_ADDRESS>

Hi, is there anything I can do to help this move forward? In particular, I'm interested in the handling of the 304 status code which I've run into as well...

Also, I gave this branch a try but my app hangs on startup, presumably when trying to connect to the docker daemon over a Unix socket. I haven't investigated much yet but I'll see if I can figure out what's wrong.

So I did a bit of digging. The "good" news is I can reproduce it simply by running the shiplift's examples, i.e. cargo run --example images hangs (although for some reason cargo run --example containers works for me, which is a bit puzzling).
I think I've tracked down the code that hangs to this line: https://github.com/softprops/shiplift/pull/88/commits/1b8e837ba25fd3eb4a042bb41083804de7c8c283#diff-ec7d691b5cafdc631a44bf41efa29e95R114
The wait() in particular triggers all kinds of alarm bells in my head (especially reading the documentation), but I don't know enough about hyper/tokio/futures yet to know what's wrong with it.
The fact that it works for cargo run --example containers makes me think that it might have something to do with the size of the response, i.e. the problem occurs if there is more than one Chunk to stream from the response...
I'll keep investigating a bit, but any help is welcome :)

@abusch sorry, I hadn't seen your comments on here earlier!
@abusch has opened #91 which subsumes this. It looks like they've probably fixed the hanging.
I'm gonna close this in favour of #91


css updates and about me changes

👷 Deploy Preview for joharehawkinslofthouse processing.

Name
Link

🔨 Latest commit
938dd145c160c13cc0e5653e197c5b06881793d2

🔍 Latest deploy log
https://app.netlify.com/sites/joharehawkinslofthouse/deploys/661d7b57b417b900081d7552


iframe support in version 2.5.4

Hello,
Lately I updated SQLpad in version 2.5.4
The issue occurred is that some graphs I had added as iframes currently do not work due to the fact that iframe support was blocked.
Can you please assist on this?

Sorry about that @creichn - This probably happened when the security settings were tightened in 2.5.0. Do you happen to know what version you installed by chance?
If you used npm to install, you should be able to downgrade back to 2.4.2 with npm install -g<EMAIL_ADDRESS>I'll take a look into disabling the iframe security restriction since that was a common use of the single chart display modes.

Thank you very much @rickbergfalk .
Indeed I used npm to install version 2.5.4.
Before downgrading to version 2.4.2 , would it be possible to let me know approximately when you think you will be able to disable the iframe security restriction ?
I am asking since I need the feature of "Require Login for Table/Chart Links" (so if I downgrade I will lose the feature)

I will see if I can get a new release published in the next day or two. I think I have it fixed in master, but haven't built a setup to test it

Thanks I appreciated it!
I've published 2.5.5 to npm and docker. Hopefully should resolve your issue. I didn't set up a test environment to confirm, but I'm fairly certain the frameguard protection is what did it, and that is being rolled back in 2.5.5. Let me know how it goes - for now I'll close this issue

Hello @rickbergfalk . I installed the latest release 2.5.5. Indeed the iframe worked. The only problem appeared is that some graphs I have prepared in the past do not work after the update.
So despite the fact that queries return results, it seems as if that the graphs cannot identify the column names. The result is that I get a message "not in query result"

So even though my result returns data (image below)

I get a message "not in query result" when trying to see the chart.
This graph was working properly before the update.

Sorry about that! This was from me fixing a different chart related issue I came across, and didn't think about the case you're experiencing. Going to revert that commit and publish a new patch version - will attempt fixing the charting in a separate release

@creichn 2.5.6 is now available via usual channels.


ToC...

Most of what I was making them for can be done now the way it's laid out (except the broadsheet, but I can do that with another mod).
What was bothering me now was the table of contents.  I want to have pages that are not listed (with the pages that are to still have the correct page number), and I'd like to have the page numbers on the right hand side (with no "." after them)... so I did this (see attachment), depth 2 pages are indented and depth 3 pages are not listed in the ToC but the page numbers are correct :) AND on the right :D.
(I also adjusted the page size a little and played with the scrollbars, like the even page scrollbar is now on the left...)
storyteller.css.changefileextensionforstupidgitupload.txt

hey, been a minute...
I figured out how to make the edit buttons work, when you change pages (immediately after) call:
super._activatePageListeners();

@Benjaneer Wow, I never got round to solving this problem. I will try your advice, thanks!


Using riverpod instead of provider under the hood

Hello everyone,
I was planning to use stacked package for my future projects and i was going through documentation
I saw that under the hood provider is being used
I have this doubt that
What if riverpod is used under the hood instead of provider
Riverpod solves some problems of the provider, The author also agrees to this.
I feel riverpod will be a good transition
What do you guys say ?

Hey @OmkarDabade If there is not any particular issue with the current implementation we won't spend time migrating provider to riverpod, If you have a specific issue you want to talk about please don't hesitate to open a new issue


Go SDk for IoT Hub

Thank you for your contribution and feedback! Help us review faster by providing the following information:
This issue is a: (mark with an x)

[ ] bug report
[x] request for new sample
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Steps to reproduce:
Currently the Open API specification for IoT Hub is available but the sdk does not seem to support it. I was going to write a sample for the same but want to confirm if there is something already on the roadmap?
Errors and log messages:
Expected behavior:
OS and Go versions:

1.8

Further info:

i'm interested in this too.
basically, i'd like an example of creating, listing and creating devices.

Hi @rojer and @niksacdev, we're looking into this. Are you looking for libraries to manage the hub itself, or for a device library? Thanks!

@joshgav i need the equivalent of az iot hub device-identity create. basically, to replace this shell-out with an API call.
ideally, i want to remove the requirement of having users install az and perform az login, so auth flow needs to be handled in some way as well. for AWS, if creds are not in the usual place, i ask them to obtain token and key from the dashboard.

I was happy to see this committed in July 2018! Any updates?

um... yeah, committed what exactly? is this available now?

Any updates?


Membership in AMP AC

Hi @ampproject/ac
I would like to nominate myself to join AMP Advisory Committee. I was previously the facilitator of AMP UI & Accessibility Working Group and a full time contributor to AMP.
I no longer work on AMP full time (and not at Google anymore) however I believe my background, experience and interested in a user-first Web makes me a good candidate to serve in AMP AC. If accepted to join, I will be in my personal capacity and expressing my own opinions and not of my employer (LinkedIn).
Please let me know what the next steps are and If I can provide more information for my candidacy.
Thanks!
/cc @ampproject/tsc

Hi @aghassemi. This is timely. :)
Mind filling-in the form so applications stay anonymous and everyone is on an equal footing? Thanks!


fix(dashboardeditor): pass along src for new uploads

Summary

For new uploads the src was never passed along in the callback due to it not being in availableImages. This makes one minor change to only check card changes against available images if the image is not flagged as new.

Acceptance Test (how to verify the PR)

If you debug the imagecard story on a new upload, you'll see that the src is passed through whereas before it was not

:tada: This PR is included in version 2.141.0-next.47 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Usabilla(on Flutter) crash on Android 7

Hi, can you please check this error on Android 7

Hi @tjuros01,
Thank you for reaching out & we apologise for the delay on this.
Our SDK targets Java8 and uses components available from Android API 26, therefore if your app targets previous Android versions, you need to enable desugar support to have compatibility with Java 8. You can read more about this in Google's guidelines.  and this Flutter documentation might also help.
Let us know if you have questions!
Kind regards,
Édua

Hi @tjuros01
I'm not sure if you are still experiencing this issue, but given its stale status I'll close it.
Feel free to reopen it (or another one) if you experience other issues


parametrize topic names

When you are working with more than one NAO, and you need to control them with the same pc, its common to use namespaces for each robot. Using topic name as parameter you can define different topics to control each robot

Yes, but you can also simply run
ROS_NAMESPACE=nao1 roslaunch blablabla
and
ROS_NAMESPACE=nao2 roslaunch blablabla
No ? It would seem much easier to me than having two parameters to set.

Ok. I agree with you the two parameters are not necessary. Right know in
your code booth subscribers are defined in the following manner:
self.goal_sub = rospy.Subscriber('/move_base_simple/goal', PoseStamped,
self.goalCB)
self.cvel_sub = rospy.Subscriber('/cmd_vel', Twist, self.cvelCB)
You have defined with '/' first, so you are defining as absolute topic path
and although I change the namespace it does not change.
I propose change it to the following:
self.goal_sub = rospy.Subscriber('move_base_simple/goal', PoseStamped,
self.goalCB)
self.cvel_sub = rospy.Subscriber('cmd_vel', Twist, self.cvelCB)
In this way when you define a group autamitically is renamed to
"namespace/cmd_vel"
2016-06-23 17:41 GMT+02:00 Surya Ambrose<EMAIL_ADDRESS>
Yes, but you can also simply run
ROS_NAMESPACE=nao1 roslaunch blablabla
and
ROS_NAMESPACE=nao2 roslaunch blablabla
No ? It would seem much easier to me than having two parameters to set.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ros-naoqi/naoqi_bridge/pull/57#issuecomment-228092025,
or mute the thread
https://github.com/notifications/unsubscribe/APTedq14vBE4El7H2MUVqhMBQoVtvTVOks5qOqlAgaJpZM4I8s6t
.

This seems a much better solution to me :)


Removes unnecessary clone() in both calculator examples.

As a clone() action is expensive, it takes compute time, avoiding it is preferred, I would think. Both calculators have this unnecessary clone() function call of the label.

Yes indeed. Thank you!