Add your MoJ email address to your Github account

Your access to the ministryofjustice GitHub organisation will be revoked if you don't add a @digital.justice.gov.uk, @justice.gov.uk, @cica.gov.uk or @hmcts.net email address to your GitHub account. This is an automated process please do not change any settings, only make the email change in your settings area.

Hi
I no longer do any work for the MoJ, so please go ahead and revoke my
access.
Regards,
Scott Edwards
On Tue, 18 Jan 2022 at 17:40, Nick Walters @.***> wrote:

Your access to the ministryofjustice GitHub organisation will be revoked
if you don't add a @digital.justice.gov.uk, @justice.gov.uk, @cica.gov.uk
or @hmcts.net email address to your GitHub account. This is an automated
process please do not change any settings, only make the email change in
your settings area.
—
Reply to this email directly, view it on GitHub
https://github.com/ministryofjustice/no-verified-domain-email-repo/issues/176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS5FUYPZHWXPAO2ELCYKLDUWWQXVANCNFSM5MHZEASQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were assigned.Message ID:
@.***>


Conversion Tests

Need to add tests for conversions to make sure there are no regressions. For color enum, alpha and individual colors.

Good call. This would ideally be in #43, but it should at least be done before 0.2.1.


Generate a single piece of data

It would be nice to be able to create one piece of data instead of a struct or array.
Something like mockData.string() or mockData.oneOf( "foo:bar" ).

Yes!  Just found and started using this capability, so it's in the latest build. :)


Uncaught Error: Cannot read property 'object' of undefined TypeError: Cannot read property 'objec...

[Enter steps to reproduce below:]

typed keystroke d-w

Atom Version: 1.11.2
Electron Version: 1.4.4
System: linux 4.8.4-1-ARCH
Thrown From: vim-mode package, v0.65.1
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (/usr/lib/electron/resources/electron.asar/browser/objects-registry.js:44:28)
at EventEmitter. (/usr/lib/electron/resources/electron.asar/browser/rpc-server.js:315:31)
at emitMany (events.js:127:13)
at EventEmitter.emit (events.js:201:7)
at WebContents. (/usr/lib/electron/resources/electron.asar/browser/api/web-contents.js:219:13)
at emitTwo (events.js:106:13)
at WebContents.emit (events.js:191:7)
At /home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:276

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (/usr/lib/electron/resources/electron.asar/browser/objects-registry.js:44:28)
    at EventEmitter.<anonymous> (/usr/lib/electron/resources/electron.asar/browser/rpc-server.js:315:31)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (/usr/lib/electron/resources/electron.asar/browser/api/web-contents.js:219:13)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)
  at metaToValue (/usr/lib/electron/resources/electron.asar/renderer/api/remote.js:217:13)
  at Clipboard.write (/usr/lib/atom/src/clipboard.js:70:34)
  at VimState.module.exports.VimState.setRegister (/home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:333:22)
  at Delete.Operator.setTextRegister (/home/rdodd/.atom/packages/vim-mode/lib/operators/general-operators.coffee:54:15)
  at Delete.execute (/home/rdodd/.atom/packages/vim-mode/lib/operators/general-operators.coffee:88:8)
  at VimState.module.exports.VimState.processOpStack (/home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:279:23)
  at VimState.module.exports.VimState.processOpStack (/home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:271:10)
  at VimState.module.exports.VimState.pushOperations (/home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:237:8)
  at atom-text-editor.commands.(anonymous function) (/home/rdodd/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/lib/atom/src/command-registry.js:260:29)
  at /usr/lib/atom/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/lib/atom/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/lib/atom/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
  at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/lib/atom/src/window-event-handler.js:114:36)
  at HTMLDocument.<anonymous> (/usr/lib/atom/src/window-event-handler.js:3:61)

Commands
     -0:33.4.0 nuclide-diff-view:open (atom-text-editor.editor.vim-mode.normal-mode)
     -0:00.6.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.4.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.4.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)

Config
{
  "core": {
    "customFileTypes": {
      "source.ini": [
        ".buckconfig",
        ".hgrc",
        ".flowconfig"
      ],
      "source.json": [
        ".arcconfig",
        "BUCK.autodeps"
      ],
      "source.python": [
        "BUCK"
      ]
    },
    "disabledPackages": [
      "tree-view",
      "linter",
      "minimap"
    ],
    "telemetryConsent": "no"
  }
}

Installed Packages
# User
atom-beautify, v0.29.13 (inactive)
ex-mode, v0.13.0 (inactive)
file-icons, v1.7.23 (active)
haskell-grammar, v0.4.0 (active)
highlight-selected, v0.11.2 (active)
language-babel, v2.46.0 (active)
language-graphql-lb, v0.1.0 (active)
language-ini, v1.16.0 (active)
language-ocaml, v1.1.2 (active)
language-rust, v0.4.8 (active)
language-swift, v0.4.0 (active)
language-thrift, v1.0.2 (active)
linter, v1.11.18 (inactive)
linter-eslint, v8.0.0 (active)
linter-scss-lint, v3.0.4 (active)
merge-conflicts, v1.4.4 (active)
minimap, v4.25.6 (inactive)
nuclide, v0.178.0 (active)
nuclide-format-js, v0.0.36 (inactive)
pigments, v0.37.0 (active)
sort-lines, v0.14.0 (inactive)
tool-bar, v1.0.1 (active)
vim-mode, v0.65.1 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (inactive)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

Electron Version: 1.4.4

This is an unoffical Atom distribution. Please uninstall and reinstall from https://atom.io or file this issue to the ones that package your version of Atom.


unknown enum constant Include.NON_NULL and Failed to load class “org.slf4j.impl.StaticLoggerBinder”

I'm following the official OpenCage Geocoder Java Tutorial.
I've add JOpenCage dependency as it says using these gradle instructions:
repositories {
jcenter()
}
dependencies {
compile ("com.byteowls:jopencage:replace.with.version")
}
For this reason, my Gradle project build.gradle file will be:
build.gradle file
plugins {
id 'java'
}
group 'org.example'
version '1.0-SNAPSHOT'
repositories {
mavenCentral()
jcenter()
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.12'
compile("com.byteowls:jopencage:1.3.0")
}
This is my Main class for testing forward and reverse geocoding:
public class Main {
public static void main(String[] args) {
     forwardGeocoding();
}

public static void forwardGeocoding() {
    JOpenCageGeocoder jOpenCageGeocoder = new JOpenCageGeocoder("XXX");

    JOpenCageReverseRequest request = new JOpenCageReverseRequest(41.40015, 2.15765);
    request.setLanguage("es"); // prioritize results in a specific language using an IETF format language code
    request.setNoDedupe(true); // don't return duplicate results
    request.setLimit(5); // only return the first 5 results (default is 10)
    request.setNoAnnotations(true); // exclude additional info such as calling code, timezone, and currency
    request.setMinConfidence(3); // restrict to results with a confidence rating of at least 3 (out of 10)

    JOpenCageResponse response = jOpenCageGeocoder.reverse(request);

    // get the formatted address of the first result:
    String formattedAddress = response.getResults().get(0).getFormatted();

    System.out.println(formattedAddress);
}

}
and this is the output (note that formattedAddress is printed successfully but there are some warnings and errors):
14:23:10: Executing task 'Main.main()'...
Task :compileJava UP-TO-DATE Task :processResources NO-SOURCE Task :classes UP-TO-DATE
Task :Main.main() Travessera de Gràcia, 142, 08001 Barcelona, España
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0. Use '--warning-mode all' to show the individual deprecation warnings. See https://docs.gradle.org/6.5/userguide/command_line_interface.html#sec:command_line_warnings
BUILD SUCCESSFUL in 1s 2 actionable tasks: 1 executed, 1 up-to-date SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. 14:23:12: Task execution finished 'Main.main()'.

We should fix these errors.

This build message is more a warning than an error. It does not prevent anyone using the lib. But I'm happy to accept a PR for this.
See https://github.com/moberwasserlechner/jopencage#fix-a-bug-or-create-a-new-feature

I do it myself in #39


CTF challenge from docs is broken

When running ItyFuzz against an on-chain deployed CTF, I encountered the following error:
thread 'main' panicked at src/evm/onchain/endpoints.rs:791:29:
fail to get block timestamp
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace```

Seems to be a connectivity issue with the public RPCs. You can use ETH_RPC_URL=https://xxx ityfuzz ... to specify the RPC you would like to use. We recommend using Infura or Quicknode


Dev Server crashes after creating project

Hey,
wanted to try out this generator since I want to use Express with TS.
However whenever I create a new project with eg new new_project and select Typescript or Typescript + MVC, cd into the project and type npm run dev I get the following output:

Node Version: 21.7.0
package manager: npm
view: pug

I faced this issue today as well. It appears that ESM modules are not loaded properly for the distribution version as if you run node --experimental-specifier-resolution=node .express/www.js manually, you'll get something like:
% npm start

><EMAIL_ADDRESS>start
> node app.js

node:internal/modules/run_main:129
    triggerUncaughtException(
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/homedir/esm-test/foo/bar' imported from /homedir/esm-test/app.js
Did you mean to import "./foo/bar.js"?
    at finalizeResolution (node:internal/modules/esm/resolve:265:11)
    at moduleResolve (node:internal/modules/esm/resolve:933:10)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND',
  url: 'file:///homedir/esm-test/foo/bar'
}

Node.js v20.16.0

And it's caused by import usersRouter from "./routers/users"; line in generated dist/app.js.
If you repalce it with import usersRouter from "./routers/users.js"; it works fine.

Based on discussion in microsoft/TypeScript#52412 you can make a quick and drity workaround by:

Setting following properties in compilerOptions of your tsconfig.json (you might need to overwrite some):

    "module": "Node16",

    "moduleResolution": "Node16",

Changing import usersRouter from "./routers/users"; to import usersRouter from "./routers/users.js"; in your src/app.ts.

After that it should compile and work - but that's a workaround.

This package is under developing right now. I`ll try to remake this package in general and make huge patch with new functions, commands and bug fixes. Main goal - make simillar to @nestjs/cli package for ExpressJS developers.


Memory leak of pulsar-function-go library regarding time.NewTimer()

Describe the bug
There is a memory leak in the pulsar-function-go library.
I reported an issue regarding the package(#5589), but this report is another one.
It is related to KillAfterIdleMs configuration value. If I set the value to 0, time.NewTimer() function has occupied more memory indefinitely. Refer to pprof  result of that below.
# go tool pprof -top http://localhost:6060/debug/pprof/heap
Fetching profile over HTTP from http://localhost:6060/debug/pprof/heap
Saved profile in /root/pprof/pprof.simple-worker.alloc_objects.alloc_space.inuse_objects.inuse_space.713.pb.gz
File: simple-worker
Build ID: 2a730ff40dbea9318c3ce868f33ecc2e69304de8
Type: inuse_space
Time: Nov 12, 2019 at 12:27pm (KST)
Showing nodes accounting for 31.29MB, 100% of 31.29MB total
      flat  flat%   sum%        cum   cum%
      30MB 95.88% 95.88%    31.29MB   100%  time.NewTimer
    1.29MB  4.12%   100%     1.29MB  4.12%  time.startTimer
         0     0%   100%    31.29MB   100%  github.com/apache/pulsar/pulsar-function-go/pf.(*goInstance).startFunction
         0     0%   100%    31.29MB   100%  github.com/apache/pulsar/pulsar-function-go/pf.Start
         0     0%   100%    31.29MB   100%  main.main
         0     0%   100%    31.29MB   100%  runtime.main
         0     0%   100%    31.29MB   100%  time.After

If I set KillAfterIdleMs value higher than 0, the memory leak didn't appear.
In order to fix this issue, I investigated the source code and I could find the code that caused the problem. Fortunately, It seems has been fixed now. So I will send a pull request for that.
To Reproduce
Steps to reproduce the behavior:

Prepare a pulsar cluster with standalone mode.
Prepare a simple pulsar function worker. Refer to the codes below.

$ cat simple-worker.go
package main

import (
        "context"
        "fmt"
        "net/http"
        _ "net/http/pprof"

        "github.com/apache/pulsar/pulsar-function-go/pf"
)

func main() {
        // go routine for pprof
        go func() {
                fmt.Println("%+v", http.ListenAndServe("localhost:6060", nil))
        }()

        pf.Start(testFunction)
}

func testFunction(ctx context.Context) {
        fmt.Printf("Hello\n")
}

Prepare a conf.yaml file for the function worker.

---
pulsarServiceURL: "pulsar://sunkwan-devpc:6650"
instanceID: 0
funcID: "ed5f48f4-8e76-4d30-8b88-6eea1ff3cbf3"
funcVersion: "12f361a0-67e5-4404-8177-8c328a33e3db"
maxBufTuples: 1024
port: 0
clusterName: "standalone"
killAfterIdleMs: 0
tenant: "public"
nameSpace: "default"
name: "func-concat"
className: ''
#logTopic: 'persistent://public/default/func-concat-logs'
logTopic: ''
processingGuarantees: 0
secretsMap: ''
runtime: 0
autoAck: true
parallelism: 3
subscriptionType: 0
timeoutMs: 0
subscriptionName: ''
cleanupSubscription: true
sourceSpecsTopic: "persistent://public/default/func-concat"
sourceSchemaType: ''
receiverQueueSize: 1
#sinkSpecsTopic: "persistent://public/default/func-concat-output"
#sinkSpecsTopic: ""
#sinkSchemaType: ''
#cpu: 1
#ram:<PHONE_NUMBER>
#disk:<PHONE_NUMBER>0
#maxMessageRetries: 0
#deadLetterTopic: ''
#regexPatternSubscription: false

Execute the simple pulsar function worker by command line below.

./simple-worker --instance-conf-path ./conf.yaml

Send messages to the input topic consecutively.
Check the memory usage and heap status using pprof.

# go tool pprof -top http://localhost:6060/debug/pprof/heap
Fetching profile over HTTP from http://localhost:6060/debug/pprof/heap
Saved profile in /root/pprof/pprof.simple-worker.alloc_objects.alloc_space.inuse_objects.inuse_space.713.pb.gz
File: simple-worker
Build ID: 2a730ff40dbea9318c3ce868f33ecc2e69304de8
Type: inuse_space
Time: Nov 12, 2019 at 12:27pm (KST)
Showing nodes accounting for 31.29MB, 100% of 31.29MB total
      flat  flat%   sum%        cum   cum%
      30MB 95.88% 95.88%    31.29MB   100%  time.NewTimer
    1.29MB  4.12%   100%     1.29MB  4.12%  time.startTimer
         0     0%   100%    31.29MB   100%  github.com/apache/pulsar/pulsar-function-go/pf.(*goInstance).startFunction
         0     0%   100%    31.29MB   100%  github.com/apache/pulsar/pulsar-function-go/pf.Start
         0     0%   100%    31.29MB   100%  main.main
         0     0%   100%    31.29MB   100%  runtime.main
         0     0%   100%    31.29MB   100%  time.After

Expected behavior

Memory usage of pulsar worker process shouldn't be grown indefinitely.

Screenshots
N/A
Desktop (please complete the following information):

OS: Ubuntu 18.04

Additional context
N/A

@Sunkwan-Kwon Thanks for the fix.

Is there any update for merging?


Having an AP with an ssid containing the minus symbol

I currently need to access a wireless Network wih an ssid like CompanyWifi-F8D7 and everytime i try to  find an already saved profile with find('wlan0','CompanyWifi-F8D7') (python library) it returns None. I already dived into the code and i think i've found the reason: your regex used in scheme_re on line 179 only allows \w characters, which doesn't include "-" symbols.
I'm not sure if it is solved that easily so i would really appreciate your reply. Below my interfaces file:
auto lo
iface lo inet loopback
allow-hotplug wlan1
iface wlan1 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp
#auto eth0
#iface eth0 inet static
#address <IP_ADDRESS>
#netmask <IP_ADDRESS>
#gateway <IP_ADDRESS>
iface wlan0-CompanyWifi-F8D7 inet dhcp
wireless-channel auto
wireless-essid CompanyWifi-F8D7
iface wlan0-CompanyWifi-F8F7 inet dhcp
wireless-channel auto
wireless-essid CompanyWifi-F8F7
I'm running a debian wheezy on a raspberry pi (raspbian)

Hi @mqus!
Thanks for trying out wifi.
I tried to address the problem with the regex in the improve_scheme_re. Could you try it out and let me know if it helps?
I don't have access to a wireless network with a hyphen in it right now so I can't test it. But you let me know if it works and then I'll merge it. Sound good?

Thanks for answering, @rockymeza!
I tried the changes you committed by changing the source code in /usr/local/lib/python3.2/dist-packages/wifi/scheme.py (which isn't exactly the proper way but it was the easiest method for me. i installed the libs via pip)
I had changed my interfaces file before, because it sped up the connection process when not using python:
iface wlan0-CompanyWifi-F8D7 inet static
wireless-channel auto
wireless-essid CompanyWifi-F8D7
address <IP_ADDRESS>
netmask <IP_ADDRESS>
iface wlan0-CompanyWifi-F8F7 inet static
wireless-channel auto
wireless-essid CompanyWifi-F8F7
address <IP_ADDRESS>
netmask <IP_ADDRESS>
and tried it in python3 with the lines
scheme = Scheme.find('wlan0', 'CompanyWifi-F8D7')
scheme.activate()
It throws the following error:
Traceback (most recent call last):
File "", line 1, in
File "connectTest.py", line 13, in connect
scheme.activate()
File "/usr/local/lib/python3.2/dist-packages/wifi/scheme.py", line 159, in activate
return self.parse_ifup_output(ifup_output)
File "/usr/local/lib/python3.2/dist-packages/wifi/scheme.py", line 166, in parse_ifup_output
raise ConnectionError("Failed to connect to %r" % self)
wifi.exceptions.ConnectionError: Failed to connect to Scheme(interface='wlan0', name='CompanyWifi-F8D7', options={'wireless-channel': 'auto', 'netmask': '<IP_ADDRESS>', 'wireless-essid': 'CompanyWifi-F8D7', 'address': '<IP_ADDRESS>'}
But to my surprise, the wifi is correctly connected anyway...

Hi,
Can you send me the output of ifup wlan0=wlan0-CompanyWifi-F8F7. It looks like the code that parses that output is failing.
If you don't feel comfortable posting it on github, you can send it to my email, same username as my github (at) gmail.com.

Sorry for taking so long. i had no access to the hardware for some time...
Well, I tried the line and it successfully connected but it gave no output at all.

Hi @mqus,
Sorry I sort of fell off the map. What distro are you using?

Also, can you give me the output of ifup --version?

Sorry for letting this drop by the wayside. It should be fixed in wifi 0.3.7  If not, let me know.


Polish typeahead in watch mode

Improve keyboad support in typeahead(copy/paste, ctrl-a, ctrl-b, etc) #2596
Typeahead Arrow selection #2589
Truncate typeahead results when there is not enough space #2597

thanks for creating this issue to track typeahead improvements.

I removed this milestone from Jest 20. We'll be able to do all but one (better keyboard support). I don't want to block the release because of that.

Closing this master task, the one outstanding task is still open.


actionbar.css monaco editor fail

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯

error - ../../node_modules/monaco-editor/esm/vs/base/browser/ui/actionbar/actionbar.css
@mui/toolpad-app: [dev:*next] Global CSS cannot be imported from within node_modules.
@mui/toolpad-app: [dev:*next] Read more: https://nextjs.org/docs/messages/css-npm
@mui/toolpad-app: [dev:*next] Location: ....\node_modules\monaco-editor\esm\vs\base\browser\ui\actionbar\actionViewItems.js

@mui/toolpad-app: [dev:*prisma] ma.prisma @mui/toolpad-app: [dev:*prisma] @mui/toolpad-app: [dev:*prisma] ✔ Generated Prisma Client (4.3.1 | library) to .\prisma\generated\client in 191m @mui/toolpad-app: [dev:*prisma] s @mui/toolpad-app: [dev:*prisma] @mui/toolpad-app: [dev:*function-runtime] [watch] build finished, watching for changes... @mui/toolpad-app: [dev:*react-devtools] [watch] build finished, watching for changes... @mui/toolpad-app: [dev:*next] event - compiled client and server successfully in 1557 ms (1545 modules) @mui/toolpad-app: [dev:*next] wait  - compiling... @mui/toolpad-app: [dev:*next] event - compiled client and server successfully in 226 ms (1545 modules) @mui/toolpad-app: [dev:*typings] yarn run dev:typings exited with code 0 @mui/toolpad-app: [dev:*next] wait  - compiling /middleware... @mui/toolpad-app: [dev:*next] event - compiled successfully in 52 ms (43 modules) @mui/toolpad-app: [dev:*next] wait  - compiling /_toolpad/[[...index]] (client and server)... @mui/toolpad-app: [dev:*next] (node:20220) [DEP_WEBPACK_MODULE_ISSUER] DeprecationWarning: Module.issuer: Use new ModuleGraph API @mui/toolpad-app: [dev:*next] (Use node --trace-deprecation ...to show where the warning was created) @mui/toolpad-app: [dev:*react-devtools] [watch] build started (change: "../../../../../package.json") @mui/toolpad-app: [dev:*function-runtime] [watch] build started (change: "../../../../../package.json") @mui/toolpad-app: [dev:*react-devtools] [watch] build finished @mui/toolpad-app: [dev:*function-runtime] [watch] build finished @mui/toolpad-app: [dev:*next] error - ../../node_modules/monaco-editor/esm/vs/base/browser/ui/actionbar/actionbar.css @mui/toolpad-app: [dev:*next] Global CSS cannot be imported from within node_modules. @mui/toolpad-app: [dev:*next] Read more: https://nextjs.org/docs/messages/css-npm @mui/toolpad-app: [dev:*next] Location: ..\..\node_modules\monaco-editor\esm\vs\base\browser\ui\actionbar\actionViewItems.js @mui/toolpad-app: [dev:*next] Could not find files for /_toolpad/[[...index]] in .next/build-manifest.json @mui/toolpad-app: [dev:*next] Could not find files for /_toolpad/[[...index]] in .next/build-manifest.json
Expected behavior 🤔
No response
Steps to reproduce 🕹
Steps:
1.download your project
2.add .env
3. Run
"dev": "dotenv cross-env FORCE_COLOR=1 lerna -- run dev --stream --parallel --scope @mui/toolpad-core --scope @mui/toolpad-components --scope @mui/toolpad-app",
4. open localhost:3000
5. create project
6. edit project
7.  faild
Context 🔦
I get this error after first run  your project
Your environment 🌎
System:
OS: Windows 10 10.0.22000
Binaries:
Node: 16.14.2 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.19.1 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: Not Found
Edge: Spartan (44.22000.120.0), Chromium (105.0.1343.42)
npmPackages:
@emotion/react:  11.10.4
@emotion/styled:  11.10.4
@mui/base:  5.0.0-alpha.96
@mui/core-downloads-tracker:  5.10.4
@mui/icons-material:  5.10.3
@mui/lab:  5.0.0-alpha.98
@mui/material:  5.10.4
@mui/monorepo: https://github.com/mui/material-ui.git => 5.10.5
@mui/private-theming:  5.10.3
@mui/styled-engine:  5.10.4
@mui/system:  5.10.4
@mui/toolpad-app:  0.0.18
@mui/toolpad-components:  0.0.18
@mui/toolpad-core:  0.0.18
@mui/types:  7.2.0
@mui/utils:  5.10.3
@mui/x-data-grid:  5.17.1
@mui/x-data-grid-generator:  5.17.1
@mui/x-data-grid-premium:  5.17.1
@mui/x-data-grid-pro:  5.17.1
@mui/x-date-pickers:  5.0.0
@mui/x-date-pickers-pro:  5.0.0
@mui/x-license-pro:  5.17.0
@types/react:  18.0.19
react:  18.2.0
react-dom:  18.2.0
typescript: ^4.8.2 => 4.8.2

Hey @kzmKZuzmo, I've just tried reproducing this but couldn't get the error. Could you please specify each step you took to end up in this situation?
What I've done on my side was:

Git clone repo
Ran yarn install
Ran yarn dev
Opened toolpad app on the url reported in terminal
Got no errors that you mentioned

Were there any other steps you took inside app? any specific page that you visited?

yes, I can open the app on browser its work

but when I trying the edit the project I got this error... (secondTest|test > edit > error screen)

Hey @kzmKZuzmo We would need more info about your environment, example issue for reference to the information that would be helpful.

check it (its updated)

@kzmKZuzmo Could you try with this change #1042?

@kzmKZuzmo Could you try with this change https://github.com/mui/mui-toolpad/pull/1042?

This works 👍


QUESTION

This is a custom auth server for minecraft?

Yes, but now I haven't time to develop it :(


Upgrade to .NET 8

Suggested new feature or improvement
Upgrade to the latest .NET 8 LTS.
Scenario
.NET 8 brings much performance enhancements and stability.
Additional details
https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-8

I'd be glad to take this one on since I just finished the .NET 8 upgrade of PowerToys.

@snickler  here is the current branch @dhoehna is working on.  https://github.com/microsoft/devhome/tree/user/dhoehna/UpgradingToDotNetEight


SX126x devices can't join to the network

I cannot join our devices with SX1262 chips to the Helium network. The same devices joins without issues to TTN and ChirpStack. Also the same devices configured for EU868 region joins without issues to Helium. Logs on gateway and in the console indicates that there is some communication but in device logs I don't see any return communication from gateway.
We have own router and console - OUI 38 (but we also cannot join to Helium hosted console)
Devices connects through two data only gateways (Tektelic Kona Micro):

US915 13DbLDgruSUwYtj197FG8HJW3LeDDpSSioNHbjYSkFwM8t5evJo
AU915 12zDAeurUkXQA2avG3bL7rY34DWN8GVSfxGso4o5wrsPn1rDWp9

Our devices firmware uses Mbed OS stack and sx126x library. I would also add that the devices with SX1261 chips and firmware based on the same sx126x library joins to Helium network in EU/US/AU regions without issues.
Device log:

Gateway log:

Console:

After further investigation it looks like we have problem with all devices based on SX126x chips and also EU868 region. Devices that worked just a few weeks ago, now cannot join. We didn't change anything in our firmware.
Maybe it is related somehow to this issue https://github.com/helium/router/issues/818?

Thanks for providing this information, we are able to replicate the issue and working on a fix. This is high priority for the team.

A new hotspot firmware (2<IP_ADDRESS>) was released yesterday along with a fix to this issue. Once your hotspot firmware is updated, please check to see if it resolves your issue. Thanx!

No, still no luck.
I've tested with two EU868 hotspots:
Bobcat - genuine-orchid-penguin
DIY alpha - flaky-tortilla-skunk - x86 + Tektelic Kona Micro GW
In Console I see that sometimes elegant-pine-wombat hear our devices, but it doesn't change anything. Still can't join.

Did you verify they were running latest firmware? It takes time for manufacturers to upgrade their fleet.

Yes. Both miners have latest software (2<IP_ADDRESS>_GA).

Yes. Both miners have latest software (2<IP_ADDRESS>_GA).

I just wanted to bump up the issue.
Our nodes still have big problems to join to the network. Last 2 days we was testing many nodes (US915) with data only hotspot with newest gateway-rs release (Bent Shadow Barbel - 13DbLDgruSUwYtj197FG8HJW3LeDDpSSioNHbjYSkFwM8t5evJo). Sometimes they joins, but very rare and after many hours of Join Accept/Join Request loop.
At the same time, there is no problem here with join to TTN and Chirpstack network servers.

From the logs you've posted, it looks like you're not using the default Semtech nor Helium lora_pkt_fwd service to connect  to your concentrator. Is that correct? If true, can you tell me what you are using, instead?

Hi. Just to be clear, the message from @yosensi was from me (I just forgot to relog on github).

What gateway is involved? (b58 address)

What region parameters was the gateway configured for? (US915? AU915?)
We are in Europe, so it's hard to get regular US915 hotspot, so to test the US915 region we have data-only hotspot Bent Shadow Barbel - 13DbLDgruSUwYtj197FG8HJW3LeDDpSSioNHbjYSkFwM8t5evJo. At the beginning  we used Tektelic Kona Micro and packet-forwarder from its firmware and gateway-rs ipk from github, but a week ago we bought RAK2287 and we tested it on RaspberryPi using lora_pkt_fwd from RAK repository and from Helium repository sx1302_hal. Still no luck. In EU868 region, our devices usually connects to Flaky Tortilla Skunk (112UAdX6YKxHLU7Rh41vLCbEk2seyGfu58rnx1YTraKWtPvYwMmw  diy onboarded in alpha program) and Genuine Orchid Penguin (11FcxvupW1Xgs4q25Ag8DUqLt5XNxk45RPwLaLE5ysqtDVVq9J4  - currently we have it in our office)

What device was being serviced? Does it match the region of the gateway?
We are producing many LoRa devices. The old ones with SX1261 chips work without any issues. Ww only have problems with devices with SX1262 chips, they are connect to TTN and our self-hosted ChirpStack Lora Network Server, of course the region of devices matches the gateway region.

What is the router (OUI 38 here) trying to send in those downlinks? What channel mask is it returning?
The router (OUI 38) is deployed on kubernetes cluster.
I don't know how to check what channel mask is it returning by router. Can you explain me how to check it?

Again, @grabtom, please answer one at a time.
The picture labelled "gateway.log": please tell me all of the above for this picture.
The picture labelled "device.log": please tell me all of the above for this picture.

Okey, sorry. I will try to explain.
When I reported the issue a month ago we were testing our devices on both - US915 and AU915 frequencies. I gave addresses of both gateways in the message.
Log images in the first message were taken while testing AU915 frequency.
gateway.log
The log comes from the data-only hotspot Melted Quartz Meerkat (12zDAeurUkXQA2avG3bL7rY34DWN8GVSfxGso4o5wrsPn1rDWp9).
This is a Tektelic Kona Micro gateway with factory firmware and gateway-rs package from github.
Packet forwarder configuration:
    "SX1301_array_conf":[
        {
        "board_freq_band": "AU915",
        "SX1301_conf":[
        {
            "chip_enable": true,
            "chan_multiSF_0": { "chan_rx_freq": 916800000, "spread_factor": "7-10" },
            "chan_multiSF_1": { "chan_rx_freq": 917000000, "spread_factor": "7-10" },
            "chan_multiSF_2": { "chan_rx_freq": 917200000, "spread_factor": "7-10" },
            "chan_multiSF_3": { "chan_rx_freq": 917400000, "spread_factor": "7-10" },
            "chan_multiSF_4": { "chan_rx_freq": 917600000, "spread_factor": "7-10" },
            "chan_multiSF_5": { "chan_rx_freq": 917800000, "spread_factor": "7-10" },
            "chan_multiSF_6": { "chan_rx_freq": 918000000, "spread_factor": "7-10" },
            "chan_multiSF_7": { "chan_rx_freq": 918200000, "spread_factor": "7-10" },
            "chan_LoRa_std" : { "chan_rx_freq": 917500000, "bandwidth": 500000, "spread_factor": 8 },
            "chan_FSK"      : { "chan_rx_freq": 917500000, "bandwidth": 250000, "bit_rate": 100000 }
        }
        ],
        "lbt_enabled":false,
        "lbt_threshold":-80,
        "loramac_public":true
        }
    ],
    "gateway_conf": {
        "gateway_ID": "647fdafffe00833f",
        "server_address": "localhost",
        "serv_port_up": 1680,
        "serv_port_down": 1680,
        "keepalive_interval": 10,
        "stat_interval": 30,
        "push_timeout_ms": 100,
        "forward_crc_valid": true,
        "forward_crc_error": false,
        "forward_crc_disabled": false
    }
}

device.log
The log comes from our device configured on the AU915 frequency. It seems to me that the frequencies on both pictures match.

Thank you! This is very helpful.

Considering the Hotspot Melted Quartz Meerkat (12zDAeurUkXQA2avG3bL7rY34DWN8GVSfxGso4o5wrsPn1rDWp9), which is running gateway-rs and its Tektelic Kona Micro gateway, the packet forward configuration you've given appears to be incomplete.
I can't find anything which directs the gateway about its transmit frequencies. Is the JSON you've attached the entire JSON?  I'm wondering if your gateway can't send out the join ACCEPT response because it can't transmit at all.

This is the whole configuration of packet forwarder and it works when I use it with Chirpstack, so I assume that is not gateway problem. I wrote in next messages I wrote that the we have problems also with EU868 and US915. We have regular EU868 hotspots here, so I don't think it's a problem with incorrect gateway configuration.

There's clearly some sort of interaction that's incompatible here, not necessarily the fault of the gateway itself. I'd like to get to the bottom of that. So, to that aim, is there more to the configuration of the gateway?

No there isn't. It is the only configuration file of packet forwader in that gateway.

Alright. Is there any other Hotspot you have access to that can give you detailed logs like the one you used for "gateway.log"? It would be incredibly helpful to see the output of lora_pkt_fwd on from sx1301/1302 and the gateway-rs logs at the same time.

Hi there. I'm sending bunch of logs.
console-event-debug.json.txt - debug JSON from our Console
device.log - log from lora device
helium_gateway.log - gateway_rs(https://github.com/helium/gateway-rs)
lora_pkt_fwd.log - lora packet forwarder (https://github.com/helium/sx1302_hal/)
Packet forwarder and gateway-rs are running on Raspberry Pi3 with RAK2287 concentrator.
Packet forwarder config:
{
    "SX130x_conf": {
        "spidev_path": "/dev/spidev0.0",
        "lorawan_public": true,
        "clksrc": 0,
        "antenna_gain": 0, /* antenna gain, in dBi */
        "full_duplex": false,
        "precision_timestamp": {
            "enable": false,
            "max_ts_metrics": 255,
            "nb_symbols": 1
        },
        "radio_0": {
            "enable": true,
            "type": "SX1250",
            "freq": 904300000,
            "rssi_offset": -215.4,
            "rssi_tcomp": {"coeff_a": 0, "coeff_b": 0, "coeff_c": 20.41, "coeff_d": 2162.56, "coeff_e": 0},
            "tx_enable": true,
            "tx_freq_min": 902000000,
            "tx_freq_max": 928000000,
            "tx_gain_lut":[
                {"rf_power": 12, "pa_gain": 1, "pwr_idx": 4},
                {"rf_power": 13, "pa_gain": 1, "pwr_idx": 5},
                {"rf_power": 14, "pa_gain": 1, "pwr_idx": 6},
                {"rf_power": 15, "pa_gain": 1, "pwr_idx": 7},
                {"rf_power": 16, "pa_gain": 1, "pwr_idx": 8},
                {"rf_power": 17, "pa_gain": 1, "pwr_idx": 9},
                {"rf_power": 18, "pa_gain": 1, "pwr_idx": 10},
                {"rf_power": 19, "pa_gain": 1, "pwr_idx": 11},
                {"rf_power": 20, "pa_gain": 1, "pwr_idx": 12},
                {"rf_power": 21, "pa_gain": 1, "pwr_idx": 13},
                {"rf_power": 22, "pa_gain": 1, "pwr_idx": 14},
                {"rf_power": 23, "pa_gain": 1, "pwr_idx": 15},
                {"rf_power": 24, "pa_gain": 1, "pwr_idx": 16},
                {"rf_power": 25, "pa_gain": 1, "pwr_idx": 17},
                {"rf_power": 26, "pa_gain": 1, "pwr_idx": 19},
                {"rf_power": 27, "pa_gain": 1, "pwr_idx": 20}
            ]
        },
        "radio_1": {
            "enable": true,
            "type": "SX1250",
            "freq": 905000000,
            "rssi_offset": -215.4,
            "rssi_tcomp": {"coeff_a": 0, "coeff_b": 0, "coeff_c": 20.41, "coeff_d": 2162.56, "coeff_e": 0},
            "tx_enable": false
        },
        "chan_multiSF_0": {
            /* Channel 8, 903.900 Mhz */
            "enable": true,
            "radio": 0,
            "if": -400000
        },
        "chan_multiSF_1": {
            /* Channel 9, 904.100 Mhz */
            "enable": true,
            "radio": 0,
            "if": -200000
        },
        "chan_multiSF_2": {
            /* Channel 10, 904.300 Mhz */
            "enable": true,
            "radio": 0,
            "if": 0
        },
        "chan_multiSF_3": {
            /* Channel 11, 904.500 Mhz */
            "enable": true,
            "radio": 0,
            "if": 200000
        },
        "chan_multiSF_4": {
            /* Channel 12, 904.700 Mhz */
            "enable": true,
            "radio": 1,
            "if": -300000
        },
        "chan_multiSF_5": {
            /* Channel 13, 904.900 Mhz */
            "enable": true,
            "radio": 1,
            "if": -100000
        },
        "chan_multiSF_6": {
            /* Channel 14, 905.100 Mhz */
            "enable": true,
            "radio": 1,
            "if": 100000
        },
        "chan_multiSF_7": {
            /* Channel 15, 905.300 Mhz */
            "enable": true,
            "radio": 1,
            "if": 300000
        },
        "chan_Lora_std": {
            /* Channel 65 (fat channel), 912.6 Mhz */
            "enable": true,
            "radio": 0,
            "if": 300000,
            "bandwidth": 500000,
            "spread_factor": 8
        },
        "chan_FSK": {
            /* disabled */
            "enable": false,
            "radio": 0,
            "if": 300000,
            "bandwidth": 250000,
            "datarate": 100000
        }
    },
    "gateway_conf": {
        "gateway_ID": "AA555A00000000AA",
        /* change with default server address/ports */
        "server_address": "<IP_ADDRESS>",
        "serv_port_up": 1680,
        "serv_port_down": 1680,
        /* adjust the following parameters for your network */
        "keepalive_interval": 10,
        "stat_interval": 10,
        "push_timeout_ms": 100,
        /* forward only valid packets */
        "forward_crc_valid": true,
        "forward_crc_error": false,
        "forward_crc_disabled": false,
        /* GPS configuration */
        "gps_tty_path": "/dev/ttyAMA0",
        /* GPS reference coordinates */
        "ref_latitude": 0.0,
        "ref_longitude": 0.0,
        "ref_altitude": 0
    }
}

@grabtom this is a really good start. Thank you! There's one glaring issue with this set of logs, however: the times don't coincide.
Your lora_pkt_fwd log was taken around 2022-09-01T12:28:00 UTC.
Your console_event_debug.json.txt was taken around 2022-09-01T12:56:21 UTC.
This 30 minute gap makes it hard to ascertain what was really going on in all places during your test. I can tell that we aren't looking at the same packets from both ends because the RSSI/SNR figures don't match either.

I think we may be getting closer to the heart of the matter. The console is not sending the JOIN_ACCEPT to your device at the same frequency it appears to be listening on.
In the example below, we see that your device sent an initial JOIN on the channel 65 (frequency 904.6 MHz), using Data rate 4 (SF8BW500) and then proceeded to listen for RX1 on 923.900 MHz. The console logs, however, show that the console transmitted the JOIN ACCEPT on 925.100 MHz.
Device
[2022-09-01 14:28:54]  [DBG ][LMAC]: TX: Channel=65, TX DR=4, RX1 DR=13
[2022-09-01 14:28:56]  [DBG ][LMAC]: RX1 slot open, Freq = 923900000
[2022-09-01 14:28:59]  [DBG ][LMAC]: RX2 slot open, Freq = 923300000

Console
{
    "category": "join_accept",
    "data": {
      "devaddr": "38090048",
      "fcnt": 0,
      "hotspot": {
        "channel": 8,
        "frequency": 925.1,
        "id": "13DbLDgruSUwYtj197FG8HJW3LeDDpSSioNHbjYSkFwM8t5evJo",
        "lat": 42.4738454813747,
        "long": -73.81504609626082,
        "name": "bent-shadow-barbel",
        "rssi": 30,
        "snr": 0,
        "spreading": "SF7BW500"
      },

Good point. Any ideas why Console is sending JOIN ACCEPT at the wrong frequency?
Anyway, I see that every second JOIN ACCEPT matches the frequency to the device.
Any thoughts?

We do have a correction pending in our LoRaWAN library for US915 which will likely fix this issue.  Link to modified US915https://github.com/helium/erlang-lorawan/pull/21
The config for AU915 appears correct.  Can somebody confirm whether this same issue exists for AU915 or not?

Reference to Library update PR
https://github.com/helium/router/pull/862

We seem to be having a similar problem with two new sensors - by similar I mean the JOIN_ACCEPT frequency doesn't match the JOIN_REQUEST frequency. I've attached the JSON from the console (VIP console v2.2.23)
JoinAcceptSoilevent-debug.json.txt
JoinRequestSoilevent-debug.json.txt

@lketchersid - For most plans, but especially AU915 and US915 we would never expect the Join Request frequency to match the Accept frequency.  We would expect them to be different.


Create a definitive list of bug bounty programs and their OSS organizations

I think it would be a good idea to create a list of bug bounty programs and their OSS organizations so we can give CodeQL developers an opportunity to test their queries against bug bounty eligible repos.

Big fan of this idea. I was considering doing something like this in a GitHub collection.
https://github.com/collections

I didn't know about collections! I have a list somewhere of a bunch of bug bounty programs and their github repos. I'll try to find that in the next few days. Also the bounty-targets-data can be of some potential help.


Is there a way to parse and save default experiment data from the XML in the modelDescription struct?

@ThummeTo
CC: @ChrisRackauckas

Not yet, but its pretty easy to add. I will do so in the next update!
We will parse the value as part of the modelDescription-struct and use it as default value for fmiSetupExperiment (instead of the current values 0.0 and 1.0 if this information is part of the model description.
Sounds good @sharanry ?
Best regards!

Much appreciated!
Also, tolerance is also often available as part of the default experiment metadata.

Fixed in 0.3.8 (coming soon).
The values from the ModelDescription are the deafult values for fmiSimulate (and other simulation commands).
You can access the values via:
fmu.modelDescription.defaultStartTime
fmu.modelDescription.defaultStopTime
fmu.modelDescription.defaultTolerance


Cant run npm run setup-firebase

Describe the bug
it says that it doesnt find the script to run it
To Reproduce
Steps to reproduce the behavior:
I just followed the readme and im getting the error
Expected behavior
like the readme would say to enter a certain path after
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Can you show the full content of the debug file npm generated after this error? Did you run npm install before runing that script?

@MateoKruk I did use npm install before and here is the full debug
0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli   'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli   'C:\\Users\\darkb\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli   'run', 1 verbose cli   'setup-firebase' 1 verbose cli ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: setup-firebase 4 verbose stack     at run (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:155:19) 4 verbose stack     at C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\lib\run-script.js:63:5 4 verbose stack     at C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:116:5 4 verbose stack     at C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:436:5 4 verbose stack     at checkBinReferences_ (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:391:45) 4 verbose stack     at final (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:434:3) 4 verbose stack     at then (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:161:5) 4 verbose stack     at ReadFileContext.<anonymous> (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\read-package-json\read-json.js:350:20) 4 verbose stack     at ReadFileContext.callback (C:\Users\darkb\AppData\Roaming\npm\node_modules\npm\node_modules\graceful-fs\graceful-fs.js:123:16) 4 verbose stack     at FSReqCallback.readFileAfterOpen [as oncomplete] (fs.js:257:13) 5 verbose cwd C:\Users\darkb\Desktop\TRU-POS-master\functions 6 verbose Windows_NT 10.0.19041 7 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\darkb\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "setup-firebase" 8 verbose node v12.18.2 9 verbose npm  v6.14.5 10 error missing script: setup-firebase 11 verbose exit [ 1, true ]

@MateoKruk Im new to programming, is the script setup-firebase made by you ? and if so how is it made?

@MateoKruk I finally found the issue. Firebase init changed some of the files you had originally, so i took your original files on github and replaced them ( all of them )

Good news! So you can have context the script setup-firebase runs the following command: node setupProject.js. The setupProject.js file is a little script that creates the DB on your Firebase account :).

Thank you so much! How did you guys do this project, did you have react experience before?

Pretty much it was my first real React project! @tpiaggio is a experienced developer and with his help it was much easier to build the project.
But all in all React and Firebase are great beginner friendly technologies to build awesome projects. If you want some guidance don't hesitate to ask and I can show you some awesome online courses :).


java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator

Are you in the right place?

For issues or feature requests related to the code in this repository file a Github issue.
For general technical questions, post a question on Google Groups.

Whats your runtime?

Dozer version: 6.5
OS version: Windows
JDK version: 8

Whats the problem?
Steps to reproduce:

Created Dozer configuration
Autowired Mapper in service class

Observed Results:
{"WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./v4" => "java.lang.RuntimeException: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'byodCompatibilityService' defined in VFS resource ["/C:/Users/uo721452/git/cst/target/cst/WEB-INF/classes/com/sprint/cst/customer/byod/ByodCompatibilityService.class"]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dozerMapper' defined in class path resource [com/sprint/cst/ui/care/config/DozerConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator (Module "deployment.cst.war" from Service Module Loader): org/osgi/framework/BundleActivator
Caused by: java.lang.RuntimeException: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'byodCompatibilityService' defined in VFS resource ["/C:/Users/uo721452/git/cst/target/cst/WEB-INF/classes/com/sprint/cst/customer/byod/ByodCompatibilityService.class"]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dozerMapper' defined in class path resource [com/sprint/cst/ui/care/config/DozerConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator (Module "deployment.cst.war" from Service Module Loader): org/osgi/framework/BundleActivator
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'byodCompatibilityService' defined in VFS resource ["/C:/Users/uo721452/git/cst/target/cst/WEB-INF/classes/com/sprint/cst/customer/byod/ByodCompatibilityService.class"]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dozerMapper' defined in class path resource [com/sprint/cst/ui/care/config/DozerConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator (Module "deployment.cst.war" from Service Module Loader): org/osgi/framework/BundleActivator
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dozerMapper' defined in class path resource [com/sprint/cst/ui/care/config/DozerConfiguration.class]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator (Module "deployment.cst.war" from Service Module Loader): org/osgi/framework/BundleActivator
Caused by: java.lang.NoClassDefFoundError: Failed to link com/github/dozermapper/core/osgi/Activator (Module "deployment.cst.war" from Service Module Loader): org/osgi/framework/BundleActivator"}}
Expected Results:
JBoss start up successful
Link to GitHub repo with Unit test
The easiest way for us to fix issues, is if you provide a GitHub repo, using the latest release and a simple unit test.

@jrichmond4 ; still an issue?


ItemsControl: template recreated multiple times

I'm submitting a...
Bug report
Current behavior
When using an ItemsControl, item templates are created multiple times.
Resources used by extra items seem to be not properly released.
ListView seems to be affected as well.
Expected behavior
Item template should be instantiated only one time.
If recreated, resources need to be properly released.
Minimal reproduction of the problem with instructions
Environment
Nuget Package:
Uno.UI 1.42.0-dev.392
Affected platform(s):

[X] iOS
[X] Android
[ ] WebAssembly
[ ] Windows
[ ] Build tasks

Visual Studio

[X] 2017 (version: )
[X] 2017 Preview (version: )
[ ] for Mac (version: )

Relevant plugins

[ ] Resharper (version: )

Internal issue: https://nventive.visualstudio.com/Umbrella/_workitems/edit/139686

Some investigation results:

Items?.Clear(); in OnItemsSourceChanged triggers SetNeedsUpdateItems(), which causes 2 calls on UpdateItems instead of 1
ItemsPanelRoot.Children.UpdateWithResults in UpdateItems() does not compare items (or their containers) properly, which causes performance issue as everything is recreated each time
ResetDataContextOnFirstLoad in ContentPresenter causes subsequent calls for unknown reason, as DataContext is cleared then reset with same content

@jeromelaban @baptiste-nv any idea if this has been fixed?

Confirmed fixed (see tests in https://github.com/unoplatform/uno/pull/4609).


Upgrade kyotocabinet version from 1.2.78 to 1.2.80

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

Upgrade kyotocabinet version from 1.2.78 to 1.2.80
Change Log

SPECS-EXTENDED/kyotocabinet/kyotocabinet.signatures.json
SPECS-EXTENDED/kyotocabinet/kyotocabinet.spec
/cgmanifest.json

Does this affect the toolchain?

NO
Associated issues

N/A

Links to CVEs

N/A

Test Methodology

local build

@microsoft-github-policy-service agree company="Microsoft"


revert: prepare for 3.12.2 release

This commit reverts the template changes done for 3.12.2 release.

@mergifyio queue


JdbcWriter output datatypes should be customizable

The default behaviour today for instance is to use SQL type FLOAT for OPL FLOATs. Howerver, precision on FLOAT depend on database, and one may want to customize that type anyway.
We should be able to customize it without editing the code and recompiling.

I think we should do things in a completely different way. At the moment, the JdbcWriter explicilty

drops the table
recreates the table from scratch
fills the new table
That makes a lot of assumptions about the database layout and adds some unnecessary limitations. Suppose for example you don't want to create a new table for the results but want to update an existing table (for example, in a table of employees you want to fill the "working days" column). That is not possible. To fix that I think we should extend the syntax for writing. Instead of
addWriteMapping("Result", "result");
the user should be able to say
addWriteMapping("Result", "UPDATE result WITH (?, ?, ?) WHERE name=?")
That is, the user can provide a full SQL statement that tells how to update. Parameters are filled from left to right (or we can allow some magic). That gives maximum flexibility.
Of course, we would then also have to provide a way that a user can drop/create tables in case they don't exist.

If we implement all of the above then we don't have to worry about the types. The user will pick the correct types in the SQL statement and we only have to use setLong(), setDouble() and setString() in the JDBC API (depending on the type of the tuple field).

How about this: instead of just allowing for some output mapping, we allow to customize more parameters for the output.
We can add a method to set the parameters for the output:
addOutputParameters(String oplTable,
   boolean dropTable,
   String createStatement,
   String updateStatement)

addWriteMapping(table, statement) will have the same behaviour than currently and will just call: addOutputParameters(table, true, null, null) (the nulls for createStatement and updateStatement means use default ones)
We currently use only PreparedStatements. Maybe it's worth adding the possibility to use NamedPreparedStatements UPDATE result with (:x, :y, :z) WHERE name=:name (we would map the OPL tuple fields or just :value for scalar). This will  address your use case where one wants to update a row instead of just inserting.

Using names prepared statements sounds like a very good idea. But I think we should also support "regular" prepared statements: if a user wants to write an array or a singleton value he probably does not want to use a named statement. Also using names will incurr slightly more overhead when writing a large number of elements.
For the other things: what you suggest will work. However, I'm afraid that whatever we do, there will be a usecase that we don't cover. So the most flexible thing would be to just provide a way that allows executing any SQL statement. In the old days we had the DBExecute function for this.

Yes sure, we can support both anonymous and named prepared statements.
As for a DBExecute equivalent, I see nothing that prevents us from providing an equivalent. I'll go ahead and add that too.

Sample https://github.com/IBMDecisionOptimization/OPL-jdbc-custom-data-source/tree/master/examples/studio_integration adresses the issues around creating/updating databases
Named parameter prepared statements are not yet implemented, should be shortly.
	// create result table
	db.execute("DROP TABLE result");
  	db.execute("CREATE TABLE result(oil VARCHAR(30), gas VARCHAR(30), blend FLOAT, a FLOAT)");

    // write results to database
  	db.update("items", "INSERT INTO result(oil, gas, blend, a) VALUES (?,?,?,?)");

https://github.com/IBMDecisionOptimization/OPL-jdbc-custom-data-source/pull/17 adresses named parameter prepared statements. One can now write something like:
db.update("items", "INSERT INTO result(oil, gas, blend, a) VALUES (:oil, :gas, :blend, :a))


update etl. fix dup key mongo

update etl. fix dup key mongo

Coverage increased (+0.001%) to 75.87% when pulling de29c55bc765b396f88dd70cee17bb38a33f425b on adityahenanda:dev into 8559c53b10c1c8048bf410acb3fe795fb69fe0e1 on danliris:dev.


Minimum working example Utah brain

Hi @tripaanu do you want to work together at all on this item this week (17-20 Oct 2022)?
Background  and links to the two FE meshes.
Action - Perform simulation and analysis on the two meshes:

32,248 elements (coarse)
244,136 elements (refined)

Hi Chad,
Sorry, couldn't respond sooner- I will work on it this week.
Best
Anu
On Mon, Oct 17, 2022 at 4:40 PM Chad B. Hovey @.***>
wrote:

Assigned #19 https://github.com/autotwin/mesh/issues/19 to @tripaanu
https://github.com/tripaanu.
—
Reply to this email directly, view it on GitHub
https://github.com/autotwin/mesh/issues/19#event-7605727600, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3RIEEP6FDR6CQQXDBNSK5LWDW2S5ANCNFSM6AAAAAARHNYX3Q
.
You are receiving this because you were assigned.Message ID:
@.***>

@tripaanu
Confirmation and TODO

Correct:

the two models are cell_050_050_050.inp and cell_100_100_100.inp
(assumed correct for now) models are in millimeters length scale
one material (i.e., one "section"), and assigning as gray matter for now, homogeneous, isotropic

To do

I can get you the "skull" of both of these models this afternoon (on 18 Oct 2022)

Q and A
You asked "Please let me know if I am using the wrong files or missing something."

Answer: You are using the correct files.  I don't see anything that is missing, aside from the need for the skulls, which I will get to you as soon as I am able this afternoon.

Regarding, "Also, I can scale the models in meters myself but it might be easier to just scale it right when you are creating the mesh file. Let me know if that works for you - I am good either way."

Answer: I agree, scaling should be perfect upstream, at the mesh representation.  We will refine this issue moving forward.  For now, the main goal is to automate the process.  Refinements later integrate in a trivial manner once our process is automated.

@tripaanu What is your requirement on the interface between the interior of the skull and the exterior of the brain?
Specifically, are you expecting node-to-node contact, wherein the interior surface nodes tie 1-to-1 to the exterior nodes of the brain?

Hi Chad,
Yes, I do need node-to-node contact between the brain and the skull.
Best
Anu
On Tue, Oct 18, 2022 at 5:17 PM Chad B. Hovey @.***>
wrote:

@tripaanu https://github.com/tripaanu What is your requirement on the
interface between the interior of the skull and the exterior of the brain?
Specifically, are you expecting node-to-node contact, wherein the interior
surface nodes tie 1-to-1 to the exterior nodes of the brain?
—
Reply to this email directly, view it on GitHub
https://github.com/autotwin/mesh/issues/19#issuecomment-1283014760, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3RIEEJVHKSHCCZPJ65ROZ3WD4HWRANCNFSM6AAAAAARHNYX3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tripaanu Afternoon update:  It is a new requirement (which is of course fine bc this is work in progress) to have node-to-node contact between interfacing materials.  Prior to today, I had envisioned node-to-surface (a more general interface).  So, I will need probably another day to rework our sculpt_stl_to_inp.py script.
@calehma I will update the sculpt_stl_to_inp.py on a branch separated from the main branch.  So, my dev work won't interfere with your current IGEA case study.

@tripaanu here is a preview of how things to come to you.  Attached are two images that were done with Sculpt via the Cubit GUI.  I want to implement this manual workflow into the automated sculpt_stl_to_inp.py, so I need some time for additional (multi-material) implementation.
My Q to you is this: If the meshes (brain and outer) came to as shown in these images, does this meet a specification you can simulate with?  Thank you.

Zoomed image with brain highlighted in yellow and outer not highlighted.

Hi @tripaanu
I uploaded two .inp files, details here (on a branch called multi-matl):
https://github.com/autotwin/mesh/tree/multi-matl/doc/T1_Utah_SCI_brain

Hi Chad,
I will work on it today and let you know if I run into any roadblocks- so
far it looks good.
Best
Anu
On Wed, Oct 19, 2022, 7:39 PM Chad B. Hovey @.***>
wrote:

Hi @tripaanu https://github.com/tripaanu
I uploaded two .inp files, details here (on a branch called multi-matl):
https://github.com/autotwin/mesh/tree/multi-matl/doc/T1_Utah_SCI_brain
—
Reply to this email directly, view it on GitHub
https://github.com/autotwin/mesh/issues/19#issuecomment-1284705274, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3RIEEIZWAPPHUCR6CQA6NTWECBC7ANCNFSM6AAAAAARHNYX3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

@tripaanu I am interested if you would like to have a Teams discussion on this item this week?

@tripaanu with cc to @carlsenrw @elejeune11
I have nodesets now created on the blocks (finite element meshes) automatically from within our Python scrip that runs Sculpt on isosurfaces (see 1bb036a5ee8ae71bb9085e7ff307bdf4740abffa).
Also, I have created an examplar problem called two_spheres that is exactly the same as the Utah brain model (two materials, inner and outer), but a simplified verison of the Utah brain model.
I would like to see if @tripaanu can use the two_spheres (see https://github.com/autotwin/mesh/tree/main/doc/two_spheres) example to

Define the outer block as rigid skull and the inner block as brain, does the same ABAQUS error exist as with the Utah model?
Use the nodeset on block 2 alone (without the outer block), and slosh the inner brain using boundary conditions alone.

Do you have time to work on this item this week (21, 22, 23 Nov 2022)?  We could do a Teams screenshare.
Thanks.

Hi @tripaanu
Do you have availability 11/30 or 12/01 to discuss?  Here are discussion points:

brain only and brain + outer both not working for coarse and fine resolutions:
Hex element count reference:

file
brain
outer
total

cell_size_4.inp
34,341
60,973
95,314

cell_size_2.inp
244,105
403,494
647,599

two_spheres example works reference:

Manually (e.g., with the Cubit GUI) meshing just the brain with cell_size = 8 gives a floating element:

@tripaanu with cc to @carlsenrw and @elejeune11
I have redone the "brain only" models at cell_size = 2 mm (fine) and cell_size = 4 mm (coarse) refinement levels, now including a nodeset on the surface of the brain.
You can get the two ABAQUS input files from two links on this page (circled in yellow on the screenshot below):
https://github.com/autotwin/mesh/blob/main/doc/T1_Utah_SCI_brain/README.md
Here is a screenshot of that page, with the links cell_050_050_050_v02.inp and cell_100_100_100_v02.inp shown in blue.

Can you please try the brain slosh analysis again with these input files?  Thank you.

Hi Chad,
Thank you for fixing this! I will run the jobs this week and update.
Best
Anu
On Thu, Dec 1, 2022 at 10:34 AM Chad B. Hovey @.***>
wrote:

@tripaanu https://github.com/tripaanu with cc to @carlsenrw
https://github.com/carlsenrw and @elejeune11
https://github.com/elejeune11
I have redone the "brain only" models at cell_size = 2 mm (fine) and cell_size
= 4 mm (coarse) refinement levels, now including a nodeset on the surface
of the brain.
You can get the two ABAQUS input files from two links on this page
(circled in yellow on the screenshot below):
https://github.com/autotwin/mesh/blob/main/doc/T1_Utah_SCI_brain/README.md
Here is a screenshot of that page, with the links cell_050_050_050_v02.inp
and cell_100_100_100_v02.inp shown in blue.
[image: Screen Shot 2022-12-01 at 8 24 23 AM]
https://user-images.githubusercontent.com/1473854/205093634-15b1c845-6c45-42c3-b50f-3dfb0d1e20a8.png
Can you please try the brain slosh analysis again with these input files?
Thank you.
—
Reply to this email directly, view it on GitHub
https://github.com/autotwin/mesh/issues/19#issuecomment-1333948113, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A3RIEEPKHU7P7MEEPKNR4FTWLDAQBANCNFSM6AAAAAARHNYX3Q
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @tripaanu (cc @elejeune11 @wangyrmu @carlsenrw )
Briefly, I have been working this week to get adaptivity working.  Adaptivity in Sculpt is a strategy to create small sized element sizes near features, esp with curvature (e.g., surface gyri/sulci), and then transition to larger elements toward the interior of the domain (brain).  But, many of the trials either had either 10s of millions of elements (too many to start), or had negative MSJ values.  I will continue to investigate.  The levers/settings that can be used with Sculpt is large, and the process quickly becomes combinatoril!
Ball still in my court.  Have to pause an attend to other deliverables on other projects for a few days.
ttyl.  cbh

@tripaanu (cc @carlsenrw @wangyrmu @CompMechPitt )
For your reference, here is the documentation for how I created the new candidates meshes of cell size 8, 4, and 2.
Please find the .inp files here: Dropbox/scratch/UTAH_SCI_brain/

cell size
link to .inp file on Dropbox

8
https://www.dropbox.com/s/1be50nw9nq6hofb/cell_size_8.0_2023-05-22_UTC_20_50_44_794153.inp?dl=0

4
https://www.dropbox.com/s/xxn7fsq772qxfjv/cell_size_4.0_2023-05-22_UTC_20_50_44_795467.inp?dl=0

2
https://www.dropbox.com/s/lnn6a0u2ji2jozo/cell_size_2.0_2023-05-22_UTC_20_50_44_796321.inp?dl=0

These .inp files are generated from @elejeune11 new .stl file T1_Utah_SCI_brain_5_16_2023_20_25.stl

Notes on @tripaanu email update of 2023-06-07-0903 (copy to @carlsenrw and @wangyrmu ):

Cell size 4 and 2 also failed at early time similar to cell size 8 simulations (with RMU material properties and time time constant from 0.0014 [RMU] to 0.0250 [Terpsma et al.]).
Cell size 8 with bulk modulus from D = 9.132e-10 [RMU] to D = 2.28e-10 does complete (but strain distribution is different from RMU mesh model All_Hex_dec.inp).
Impression: Mesh is fine, but material properties may need updates.

Chad's impression: a fully working image to analysis workflow is a priority, thus simulation completion is a priority.  Material properties research is a secondary priority.


Run single Test in VSCode is slower with .Net CLI 2.0 because of restore

dotnet cli 2.0 automatically restores before building when executing dotnet build or dotnet test. I can understand why, but still I have been adding --no-restore to all our build scripts and VSCode tasks.
Going through the code Omnisharp-Roslyn code, I noticed that the CLI is also called with build: https://github.com/OmniSharp/omnisharp-roslyn/blob/e18913e887144119c41d60f1842e49f8e9bfcf72/src/OmniSharp.DotNetTest/VSTestManager.cs#L51
Calling with --no-restore is possible here, but not sure what you think is best from a functionality standpoint? In my opinion, during development, these tasks should be as fast as possible.

Thanks @tverboon. You're right, that's probably the right thing to do here. However, the "restore" on build is supposed to be very quick (milliseconds).

Yes, in our case it's typically between 30 and 50 milliseconds per project. We have around 10 projects in the dependency graph, in that case it takes between 300 and 500 ms.
It's not possible to just add --no-restore in this line, because there needs to be a check for the dotnet version. Not sure if it's cached somewhere, otherwise starting the dotnet process to get the version, makes it potentially even slower for projects with less project dependencies.

Yup, I was already thinking about needing a version check. We do check the version earlier, so we should be able to pass that along.


The URL changes with every new version

Hi!
Thank you for this good work!
But the hard coded URL seems to change with every new version. You used
https://www.pei.de/SharedDocs/Downloads/DE/newsroom/dossiers/evaluierung-sensitivitaet-sars-cov-2-antigentests.pdf?__blob=publicationFile&v=71
but since last monday (31. Jan. 2022) the version at the end changed to 77 (?v=77)
Maybe an URL without the version parameter will always deliver the latest version:
https://www.pei.de/SharedDocs/Downloads/DE/newsroom/dossiers/evaluierung-sensitivitaet-sars-cov-2-antigentests.pdf?__blob=publicationFile

Hi @ikarisan,
Thanks for the feedback. I appreciate it. It seems that the version number in the url does not have any effect. The downloaded file will always be the same. However, I've removed the version parameter from the query, because it is not needed.
Also, I missed that there was an update of the data. Thanks for the hint! Now, I've configured my server to check for new data daily and use it when available. Hopefully, that will work.


Fix text alignment in dm help output.

The explanation of 'manifest' was intended one tab to far.

Thanks! Merging it.


First pass at bundling

This does not determine the synchronous behavior at all, nor does it allow for the bundler to be flushed/cancelled yet.

Merging after squashing the commits due to the above changes.

Aargh. Looks like the repo going public while this was open was... unpleasant. Will refork, reapply, and commit...

Closing this as a duplicate of #2.


docs: fix typos

Found via codespell -H

@kianmeng, thank you.
I would omit changing the docs/contributing.html file though, as this file is generated (python -m docs) -> I'm thinking about removing the generated html files altogether, while also fixing the generator that currently doesn't output \n in between the top level <body> elements...

Merged manually (omitting the html file): dd8de86fa.
In the previous commits, I have also resolved the historical problems within the docs folder as mentioned above...

@pbodnar Noted, and sorry I missed out the message.


Mm/nth dow

Here are some leap day tests.  Many other invalid forms are caught by the regex format checker, so only adding these which get caught by the switch to timegm.
@mm-binary You can use these if you like to address the feedback from @tfoertsch.

@mm-binary Could you look this over and see if it works for you?  It fixes the algorithm for finding the first of the month and includes a test (largely designed by @tfoertsch) to demonstrate that it gets things right.


PuppetPad Keep logging in and out

Provide Your Network Information

Where is the location of your server? (i.e. City, or In/Out China) Canada
Which cloud platform(AliYun/Qcloud/DigitalOcean/etc) are you using? Home Internet -- Bell

I don't have the details now, but keep this as a placeholder for the problem that people have been seeing.
The old log that I had:
When it happens, it seems that the communication with sever is extremely difficult. For e.g., the syncContactsAndRooms request should be sent right after login, but it'll take 5 minutes after login to fail:
22:20:03 INFO Wechaty start() v0.17.117 is starting...
22:20:03 INFO Wechaty initPuppet() using puppet: padchat
Contact<me> login
22:25:36 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}

Moreover, after such warning, no WX message can be received, and after 2 hours (20:19 ~ 22:19), it error out:
20:19:13 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
22:19:02 WARN PadchatRpc initWebSocket() ws.on(close) 1006
22:19:02 WARN PuppetPadchat startManager() manager.on(reset) for ws.on(close, 1006. Restarting PuppetPadchat ...
Contact<me> logout
22:19:02 WARN PuppetPadchatManager startCheckScan() checkScanLoop() exception: Error: WebSocket is not open: readyState 3 (CLOSED)
22:19:02 WARN PuppetPadchat startManager() manager.on(reset) for startCheckScan() checkScanLoop() exception. Restarting PuppetPadchat ...
22:19:02 WARN PadchatRpc initWebSocket() ws.on(error) Error: connect ECONNREFUSED <IP_ADDRESS>:8788
Error: Error: connect ECONNREFUSED <IP_ADDRESS>:8788

Lots of WX messages should have been logged to the console during this period.
Such logging in and out went on and on until I broke it out in the morning, after the whole night not getting any normal wx message logged.
To duplicate:
I was just using the vanilla https://github.com/Chatie/wechaty-getting-started/blob/master/examples/starter-bot.js with PuppetPadchat.

It will be easy to debug if you could enable WECHATY_LOG=silly for your program for detailed log messages.

Yeah, I know, that's why I said, "I don't have the details now, but keep this as a placeholder".
I'll have a new phone in a week or so, then I can give it another go.

@suntong Hello, can you reproduce it with the latest version of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

I was about to give it a try when I saw a flurry of reports claiming that the latest code is still having the same problem. So I think I'd better defer to their detailed bug report instead.

Close this issue because the padchat has been deprecated already.


certificate issue casting youtube

Hi there! Thanks so much for this project!
I'm able to cast_site successfully but casting returns the following error. For example when I run the README example:
$ catt cast "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)> (caused by URLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1056)')))
Error: Remote resource not found.

Some details:

Operating System: macOS 10.14.2
catt was installed with pip3

I tracked this error down as something that has also occured in youtube-dl [github issue]. I separately installed youtube-dl and got the same certificate error and then added the suggested workaround (adding the flag --no-check-certificate to the youtube-dl command) which then worked to download the video. Adding this in case it helps in some way.

Would it be possible to get an example commandline? I've tried every variant I can think of and can't get catt to accept/pass through this option.
For example,
catt -d "Office Home" cast --ytdl-option --no-check-certificate' <url>
seems like it should work but gives:

Error: Invalid value for '-y' / '--ytdl-option': --no-check-certificate is not a valid key/value pair.

and trying to "fake it" with things like "--no-check-certificate=1" doesn't work (but doesn't give the same error, either).
Stumped as to how to format unary flags through -y in catt!

@benmargolin You need to use youtube-dls internal option names. This really should be in readme.
catt -d "Office Home" cast -y "nocheckcertificate=true" <url>

Good call, I've added that. Thanks to both of you!


App is blocked by Google

I tried using gcalcli list for the first time and it opened a browser tab asking for verification. After choosing the account I got the following page:

Not sure if this is intended or known. I tried this with my personal account and my University's account and I got the same result in both scenarios. I tried using the --noauth_local_webserver option and got the same result after logging in.
Not sure how to solve it, and I couldn't find any similar issues online.
I am tried using both gcalcli and gcalcli-git found on the AUR.

Your best bet is to follow the steps here to get your own API keys: https://github.com/insanum/gcalcli#login-information
Though I have a problem with that where it keeps logging me out and making me re-authenticate every week or so. I may need to get it verified for it to stick.

Your best bet is to follow the steps here to get your own API keys: https://github.com/insanum/gcalcli#login-information
Though I have a problem with that where it keeps logging me out and making me re-authenticate every week or so. I may need to get it verified for it to stick.

Maybe. I tried creating an API key like the README suggests, but then I get this error page:

I haven't used the Google auth API in a long time, so I don't know what has changed or what needs to be done.

Maybe. I tried creating an API key like the README suggests, but then I get this error page:

I haven't used the Google auth API in a long time, so I don't know what has changed or what needs to be done.

In the Cloud Console go to OAuth Consent Screen -> Edit App -> Click continue twice to get to "Test users" and you should be able to add your email.

In the Cloud Console go to OAuth Consent Screen -> Edit App -> Click continue twice to get to "Test users" and you should be able to add your email.

tldr; OAuth worked for me, but only in Chromium, not in Firefox.
Steps, loosely following comment https://github.com/insanum/gcalcli/issues/497#issuecomment-592948891
1. Google Developers Console https://console.developers.google.com

create a new project, e.g., gcalcli

2. + Enable APIs and Services"

enable `Google Calendar API"
go back to project gcalcli in Developers Console

3. Credentials section in left menu

"+ Create Credentials" > OAuth client ID
Application type Desktop App
name gcalcli
The credentials produced here are needed in step 5

4. OAuth consent screen section in left menu

I was restricted to choose "External users"
OAuth consent screen

App name": e.g., gcalcli
User support email: e.g., put your own gmail address
App domain: leave all blank
Developer contact information: put your own gmail address

Scopes: choose all calendar API related stuff plus more if necessary - I did trial and error here ...
Test users: again I put my own gmail address here
Summary: click "Back to dashboard" at bottom
leave Publishing status as Testing so your own gcalcli is not published to the world

5. call gcalcli from command line

Use credentials from step 3 here in cli command, e.g. for Google agenda view: gcalcli --client_id "your client ID ending in ...apps.googleusercontent.com" --client_secret "your client secret" agenda
as my default browser is Firefox I had to copy the URL after Your browser has been opened to visit: (shown in shell after above command) and open it in chromium > follow steps and give permissions to gcalcli
in shell, Google calendar agenda is shown

SO easy! :'D

tldr; OAuth worked for me, but only in Chromium, not in Firefox.
Steps, loosely following comment https://github.com/insanum/gcalcli/issues/497#issuecomment-592948891
1. Google Developers Console https://console.developers.google.com

create a new project, e.g., gcalcli

2. + Enable APIs and Services"

enable `Google Calendar API"
go back to project gcalcli in Developers Console

3. Credentials section in left menu

"+ Create Credentials" > OAuth client ID
Application type Desktop App
name gcalcli
The credentials produced here are needed in step 5

4. OAuth consent screen section in left menu

I was restricted to choose "External users"
OAuth consent screen

App name": e.g., gcalcli
User support email: e.g., put your own gmail address
App domain: leave all blank
Developer contact information: put your own gmail address

Scopes: choose all calendar API related stuff plus more if necessary - I did trial and error here ...
Test users: again I put my own gmail address here
Summary: click "Back to dashboard" at bottom
leave Publishing status as Testing so your own gcalcli is not published to the world

5. call gcalcli from command line

Use credentials from step 3 here in cli command, e.g. for Google agenda view: gcalcli --client_id "your client ID ending in ...apps.googleusercontent.com" --client_secret "your client secret" agenda
as my default browser is Firefox I had to copy the URL after Your browser has been opened to visit: (shown in shell after above command) and open it in chromium > follow steps and give permissions to gcalcli
in shell, Google calendar agenda is shown

SO easy! :'D

I tried what @aurisnoctis said. However, I couldn't be successful. Is there any other way around to make this work out?
Thank you.

I'm using Firefox and it gives me the option to continue with a warning:

Thanks @aurisnoctis Really helpful.

I had been using this awesome app for about a month, and suddenly today, Google tells me that the app is blocked, and there's nothing I can do to get it authenticated.  I had already set it up with my own GCP OAuth credentials, using .gcalclirc and it was working fine.   Also, "Allow less secure apps" setting on my Google Account is "ON".   I don't understand, I've been developing Google Cloud Platform apps for a few years and I was always given the option to "continue" and "allow" the app, now there is just no option, only a "Blocked" message.  Any ideas?

I solved this issue using the following resources:

Make sure to turn on your Google account's setting for "Allow less secure apps"
Visit Google's "Display Unlock Captcha" page and click "Continue" to remove the security block.

Hello all,
what about generating a token from this page ? https://myaccount.google.com/apppasswords
Could it solve this problem ? I think gcalcli is not ready to use such token but it could be a great improvment.

Same issue. I'm trying to read my schedule from my work account, where I can't change any of the above settings.

I tried this guide for creating the client id and client secret and it worked flawlessly. I didn't even have to run "DisplayUnlockCaptcha" nor enable Less Secure Apps.
https://github.com/aristosv/google_auth

I think the readme of this project should state a bit more clearly that you may have to do a 5+ step guide to authorize this app. Currently, it implies that only OAuth2 will be needed and anything else is optional.

Just chiming in here that yes, the problem is still blocking simple usage of gcalcli, but on the other hand, the complicated process above does still work when applied with some flexibility. Google keeps changing the dashboards of the relevant API management, so it's hard to feel confident that you are doing the right thing. :)   Thank you, @AurisNoctis

Additional information…
I've been using gcalcli for about a week.  I had authorized it to access one of my two Google accounts (my personal account) following the steps in the documentation.  It was an awkward process, but I somewhat understand the complexities of working with Google's security.
After using gcalcli for about a week, today I tried to use it to access the calendar belonging to my other Google account (my account in my employer's enterprise).  In Google Calendar, long ago I gave each of my Google accounts mutual access to their calendars.  I tried to use the gcalcli authorization for my personal account to add an event to my work account.  At first, I got the following stack trace…
Traceback (most recent call last):
  File "/Users/lsloan/homebrew/bin/gcalcli", line 33, in <module>
    sys.exit(load_entry_point('gcalcli==4.3.0', 'console_scripts', 'gcalcli')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/gcalcli/cli.py", line 181, in main
    gcal.QuickAddEvent(
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/gcalcli/gcal.py", line 1294, in QuickAddEvent
    new_event = self._retry_with_backoff(
                ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/gcalcli/gcal.py", line 112, in _retry_with_backoff
    return method.execute()
           ^^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/googleapiclient/_helpers.py", line 130, in positional_wrapper
    return wrapped(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/googleapiclient/http.py", line 923, in execute
    resp, content = _retry_request(
                    ^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/googleapiclient/http.py", line 191, in _retry_request
    resp, content = http.request(uri, method, *args, **kwargs)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/oauth2client/transport.py", line 186, in new_request
    credentials._refresh(orig_request_method)
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/oauth2client/client.py", line 761, in _refresh
    self._do_refresh_request(http)
  File "/Users/lsloan/homebrew/Cellar/gcalcli/4.3.0_3/libexec/lib/python3.11/site-packages/oauth2client/client.py", line 819, in _do_refresh_request
    raise HttpAccessTokenRefreshError(error_msg, status=resp.status)
oauth2client.client.HttpAccessTokenRefreshError: invalid_grant: Token has been expired or revoked.

Thinking that it might be a temporary problem, I tried again.  This time, gcalcli opened the following address in a web browser…
https://accounts.google.com/o/oauth2/v2/auth?client_id=«REDACTED».apps.googleusercontent.com&redirect_uri=http%3A%2F%2Flocalhost%3A8080%2F&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar&access_type=offline&response_type=code

In the Google page that opened, I selected my account name when prompted.  The next page showed me the familiar message others have mentioned…
This app is blocked
This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access.

I'm not certain whether this was caused by my token being expired/revoked as mentioned in the first error message or maybe it was triggered by trying to access my work account calendar from my personal account.

I've made some modifications in a fork using newer auth methods. Download a creds.json & put it in ~/.config/gcalcli/ - details in the update README.
I'm not providing support, but you can see if it works for you (it works for me).
Be warned this is a quick 30 minute hack, I suggest creating a virtualenv and installing it in there. Also it used my existing ~/.gcalcli_oauth file (not sure why currently) so I moved it to start a new auth flow.
I suggest inspecting the diffs, no guarantees this won't wipe all your appointments!
https://github.com/jamespo/gcalcli

Alright, I'm removing the broken client ID from the app entirely in #707 while making the setup process a little friendlier. I'm pretty sure that takes care of all loose ends here, but please reach out with a fresh issue if you're still seeing problems not related to that broken client ID.


improvement  examples/charRNN

I try use "examples/charRNN" for more real text but very quickly  prediction stop working
Time Taken: 1m9.662684024s      Cost: NaN       Perplexity: NaN
It will be nice to have some hints to improve result. Maybe change some parameters?
I have file  6.1M size to elaborate.
My  scope arrive to result near:
https://github.com/karpathy/char-rnn

Closing this. The reference LSTM is Olivier Wulveryck's package: https://github.com/owulveryck/lstm


ModuleBuildError : 'SassError: Undefined function.'

Getting the following error while compilation. I added scss to my angular.json and done all the necessary imports and configurations.
Error: ./node_modules/ngx-tagify/styles/tagify.scss Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js): ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js): SassError: Undefined function.     ╷ 267 │                     $size: math.div(-$tagMargin, 2);     │                            ^^^^^^^^^^^^^^^^^^^^^^^^     ╵<EMAIL_ADDRESS>267:28  @import   node_modules\ngx-tagify\styles\tagify.scss 1:9      root stylesheet
[IMAGE]

The math.div sass function is defined in the scss of the core library @yaireo/tagify/src/tagify.scss L267. It seems like, you are running an older project. math.div has been introduced in<EMAIL_ADDRESS>which was released 6 months ago. Hence, updating your sass dependencies should resolve your issue (https://stackoverflow.com/questions/67857768/sass-math-div-function-is-undefined-in-angular-app-but-is-defined-in-angular-li). Upgrading Angular should also help.


Disable exif rotation while taking pictures

Steps to Reproduce
1.setup cameraawesome using any example given
2.click a photo
3.You will observe ,the captures image will get automatically rotate to portrait mode.
Issue : when the phone is parellel to the ground ,the camera orientation changes and its very hard to scan any documents or something
Expected results
A flag like gps info in exifConfig to disable exif rotation on native side
Actual results
Cant find any flag to disable exif rotation
About your device
All devices

Any updates on this?

Sorry you are right this should be optionnal.
Will look how to make it.
Either would you like to work on this?

@g-apparence Is this planning to be added on upcoming release?


tk apply crashes by creating Role from helm chart

Using helm chart 0.33.1 from timescaledb-single https://github.com/timescale/helm-charts/tree/main/charts/timescaledb-single
crashes with
$ tk apply environments/dev-new/
Error: got an error while extracting env `environments/dev-new`: found invalid Kubernetes object (at .hex_deploy.hex_deploy.timescaledb.role_hex_timescaledb.rules.[0].apiGroups): missing attribute "apiVersion"

apiGroups:
    - ""
resources:
    - services
verbs:
    - create
    - get
    - list
    - update
    - patch
    - delete
    - watch

Using helm template  prints an valid yaml file.
an older version of this template 0.27.0 is working without a problem
output of 0.27.0 with tk eval
$ tk eval environments/dev/ | jq .hex_deploy.hex_deploy.timescaledb.role_hex_timescaledb
{
  "apiVersion": "rbac.authorization.k8s.io/v1",
  "kind": "Role",
  "metadata": {
    "labels": {
      "app": "hex-timescaledb",
      "app.kubernetes.io/component": "rbac",
      "app.kubernetes.io/managed-by": "Helmraiser",
      "app.kubernetes.io/name": "hex-timescaledb",
      "app.kubernetes.io/version": "0.27.0",
      "chart": "timescaledb-single-0.27.0",
      "cluster-name": "hex-timescaledb",
      "heritage": "Helm",
      "release": "hex"
    },
    "name": "hex-timescaledb",
    "namespace": "dev"
  },
  "rules": [
    {
      "apiGroups": [
        ""
      ],
      "resources": [
        "configmaps"
      ],
      "verbs": [
        "create",
        "get",
        "list",
        "patch",
        "update",
        "watch",
        "delete"
      ]
    },
    {
      "apiGroups": [
        ""
      ],
      "resources": [
        "endpoints",
        "endpoints/restricted"
      ],
      "verbs": [
        "create",
        "get",
        "patch",
        "update",
        "list",
        "watch",
        "delete"
      ]
    },
    {
      "apiGroups": [
        ""
      ],
      "resources": [
        "pods"
      ],
      "verbs": [
        "get",
        "list",
        "patch",
        "update",
        "watch"
      ]
    },
    {
      "apiGroups": [
        ""
      ],
      "resources": [
        "services"
      ],
      "verbs": [
        "create",
        "get",
        "list",
        "update",
        "patch",
        "delete",
        "watch"
      ]
    }
  ]
}

output of 0.33.1

tk eval environments/dev/ | jq .hex_deploy.hex_deploy.timescaledb.role_hex_timescaledb
{
  "rules": [
    {
      "apiGroups": [
        ""
      ],
      "resources": [
        "services"
      ],
      "verbs": [
        "create",
        "get",
        "list",
        "update",
        "patch",
        "delete",
        "watch"
      ]
    }
  ]
}

used tk version v0.26.0
Is this a bug in tanka, creating/converting to jsonnet roles?

Can you show the Jsonnet code for this?

Could it be that you override the role rules in jsonnet but that the Role name changed? This commit gives me an indication that it changed: https://github.com/timescale/helm-charts/commit/d26fefe4a93ace9d54a3cab18f5bc6a3908e477f

@Duologic thanks for your hint.
That was the problem.
I added a role rule patch at the end of my libsonnet file and the change in timescale helm broke my deployment.


install error if inside /root

Hi
I had a strange error. If I wanted to install in /root/teset folder then I got the following error:
https://gist.github.com/minutuslausus/97043119dade7dffe058
I could solve it, but it was annoying to debug

Hi, do you get the same error if you install in other location, say /tmp?

No. It works both in my home dir both in /tmp

Perhaps it is the directory permission that npm is unable to create a scripts directory in /admin on install?
Does it create node-sass directory at all after it fails the installation?

hm, strange
https://gist.github.com/minutuslausus/6f0d8bd2daa99f9335a3
it creates node_modules with my base user as owner (puffy) and then bin owned by root
I thought the process should inherit the rights of the user

Unfortunately, that part of installation process we don't control. This is not undoable, but this is a very rare use-case which I think should be addressed by npm folks: https://github.com/npm/npm.
Alternatively, I would suggest you to install nvm or update node to use latest version of node.js v0.12.0, which packs with npm v2.5.1 and retry. Perhaps they have already fixed it.

this can be true, but seems unlikely to me
I have this package.json: https://gist.github.com/minutuslausus/f11ff2867793147870bd
and all of them works without any problem
on the other hand I am far from an expert, so you could be right :)
right now, my problem is solved (I moved the folder)

Great! We I try to reproduce this issue once we are done with other build related stuff. :)

The pre-release v3.0.0-pre is out. See the breaking changes in README.
npm install<EMAIL_ADDRESS>
To see the runtime coverage matrix, see node-sass-binaries readme: https://github.com/sass/node-sass-binaries/#node-sass-binaries.


Update UGDG Naren

Codecov Report

Merging #263 (c7f03e1) into master (8bbaa9e) will not change coverage.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.