[Possible Bug] Spec file path not getting cached when using  ?

So I have a strange issue. I run retest in the docker container with the command
retest 'spring retest rspec <test>'

Running rspec with spring to speed up test initialization works fine.
Also, doing a save on any "*_spec.rb" file immediatelly reruns the spec. This is also fine.
However, when saving changes on an "*.rb" file, it takes about 5 seconds for the corresponding spec to run each time. Spring seems to work fine (spec starts executing, Spring reports it being preloaded, but only after the initial 5 seconds), so I was thinking - is it possible the file path to the spec file is not cached, and retest needs to search for the file each time we save?
Rails <IP_ADDRESS>
Ruby 3.0.3

Okay, some further findings. It seems this doesn't happen all the time. Some files (and their respective spec files) run immediately, while other files have a kind of delay before running
As an example, this takes a few seconds to start after saving:
decorator/spree/some_view.rb

saving the spec file starts tests immediatelly.
However, after saving:
/service/any_file_here.rb

The specs run instantaneously.
Another thing I've noticed, if there is no corresponding spec file, retest will instead start running specs from a filename with a similar name, instead of letting us know the spec file is missing.

Hi @VlatkoGoljevacki
Sorry for the late response, I found your issue by chance. Somehow I missed a notification from GitHub.
Thanks for raising an issue.
Slow run

Okay, some further findings. It seems this doesn't happen all the time. Some files (and their respective spec files) run immediately, while other files have a kind of delay before running

The behaviour seems to be difficult to reproduce but I did realise that sometime it's a bit slow too. Would you be able to capture a video/gif of the behaviour you're witnessing?
There are few leads I can think of:

Maybe we don't cache the file properly.
Maybe the gem listen takes a longer time to identify a change.
Maybe it depends on how many ruby files we're watching.

Would you be able to count the number of .rb files you have on your repository, please?
Something like this would work. In this example I've run this command on the retest repository. This command find all the files in the current directory, filter only the ruby files and count them
find . -type f | grep .rb | wc -l
225

Rerun a test file when not found

Another thing I've noticed, if there is no corresponding spec file, retest will instead start running specs from the previously cached file path, instead of letting us know the spec file is missing.

Currently this is a feature not a bug :joy: Here are the running rules
It will only run a 404 if there was no previous command run.
Initially retest used to listen to all file changes. This was done so that when changing any other files than a .*rb file (like .json or .yml) during a refactoring you would still be running the previous test and make sure you wouldn't break what you were refactoring.
Since we only listen to .rb files now, I understand that the behaviour is confusing. I will look into this and see what would be a better behaviour when no tests is found :+1:

I looked at the listen gem and there is a logger with a debug options.
You could run and maybe find something relevant when the run starts to slow down? I'll try this as well when working.
LISTEN_GEM_DEBUGGING=debug retest 'spring rspec <test>'

Hey @AlexB52
There are 1454 .rb files in my repo. I'm also using the Spree e-commerce gem, which is famous for using "decorators", i.e. modules which are prepended to a named class to update/change its functionality.
A lot of this "slowness" appears when running tests on class that was decorated this way. I still have to check if this is the only time the problem appears.
When using the listen gem debugger, I get the following output.  Important to note, this does not happen with all files, only some. Still searching for a pattern.
Here's a gif as well (withou the debug log). First save is "_spec.rb", second save is ".rb", third save is "_spec.rb" again.

@AlexB52 Ok I think I figured out the problem (if not the solution).
I looked into the "log/development.log" at what was happening and it seems the app is re-initializing (i.e. running Spring has no effect when saving the ".rb" file).

I'm not entirely sure whether this is retest at play here. Looking at your gif if you see Test File Selected: <file_path> means that listen was triggered, the test file has been found and the command has been run.

I looked into the "log/development.log" at what was happening and it seems the app is re-initializing (i.e. running Spring has no effect when saving the ".rb" file). Only this time it's not outputting to STDOUT.

Would you say it takes the same amount of time to run your spec as if spring was not involved?
I wonder if the use of prepend requires some reloading which would reset spring and reload the app. I've definitely experienced and read something similar about extend in the past in Ruby but can't reproduce it and can't find it anywhere online so that this with a grain of salt.

@AlexB52 Hah, you're right, that reloads spring (it appears it's a partial reload). A full one takes about 18 seconds, and the new one 9-10 seconds.

@VlatkoGoljevacki Sounds good, let me know how this goes :+1:

I'll close this issue as I think this is an expected Spring behaviour and not related to Retest.


Unable to open LeadSeason.eu inside of local net.

Changing CloudFlares's proxy off from LeadSeason.eu made it unable to be opened in local net.
Now tries to open opnsense instead.
❌ Your service LeadSeason.eu went down. ❌
Service Name
LeadSeason.eu
Service URL
https://leadseason.eu/
Time (Europe/Helsinki)
2024-01-31 22:25:25
Error
Hostname/IP does not match certificate's altnames: Host: leadseason.eu. is not in the cert's altnames: DNS:opnsense.localseason.eu
Yesterday at 10:25 PM

Possible fix:
Change opnsense.localseason.eu to point <IP_ADDRESS>
Make opnsense listen only on the <IP_ADDRESS> IP

Yeap that did the trick.


Idea: warn when a re-exported name is imported

Consider a library like this:
# lib/__init__.py
from .exceptions import LibError
from .client import Client

__all__ = [
    "Client",
    "LibError",
]

# lib/exceptions.py
class LibError(Exception): ...

# lib/client.py
from .exceptions import LibError

class Client:
    def some_method(self):
        if something.bad:
            raise LibError("thou shalt not pass")

Then the user code imports these names:
from lib import LibError  # OK, explicitly re-exported

from lib.exceptions import LibError  # OK, that's where it's defined

from lib.client import LibError  # WARN: lib.exceptions.LibError is re-exported via lib.client

from lib.client import Client  # OK

The reason to warn is that lib.client can change, for example to raise exception.MoreSpecificError instead, which would not be a breaking change is MoreSpecificError inherits from LibError.
However, in that case, LibError may no longer be re-exported via lib.client.
Thus user code that depends on LibError name being present on lib.client is mistaken.
Ideas how this could be implemented:

get the __qualname__ for the imported name
check if the import path is different from qualname
check if the imported name is also available at lib top level or
check if the imported name is available at some intermediate level between lib and qualname
suggest a more direct import

Related to Mypy's no_implicit_reexport feature:

https://github.com/python/mypy/issues/10198


Using react material UI (or other UI libraries) with goja

Hey, this is pretty cool package!
Ive been playing with this, and its very nice, great for a Go developer to build an app with a react front end.
However I have been struggling to get Material UI react to work with it, and infact I tried also Semantic UI but that failed within similar errors. I decided to concentrate on Material.
Reading a couple of issues here, this seems to be the place the error is occuring - the error is:
init JSVM static/build/bundle.js
panic: TypeError: Object has no member 'createContext' at bundle.js:43829:49(35)

goroutine 53 [running]:
main.newJSVM.func1(0xc000080c00)
	/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/react.go:207 +0x4aa
github.com/dop251/goja_nodejs/eventloop.(*EventLoop).RunOnLoop.func1()
	/Users/alex/go/pkg/mod/github.com/dop251/goja_nodejs@v0.0.0-20200128125109-2d688c7e0ac4/eventloop/eventloop.go:111 +0x31
github.com/dop251/goja_nodejs/eventloop.(*EventLoop).runInBackground(0xc000447160)
	/Users/alex/go/pkg/mod/github.com/dop251/goja_nodejs@v0.0.0-20200128125109-2d688c7e0ac4/eventloop/eventloop.go:129 +0x6c
created by github.com/dop251/goja_nodejs/eventloop.(*EventLoop).Start
	/Users/alex/go/pkg/mod/github.com/dop251/goja_nodejs@v0.0.0-20200128125109-2d688c7e0ac4/eventloop/eventloop.go:88 +0x3f

I have attempted to use yarn to update the package.json (as I read in another issue that might be the problem, I am now using the package.json
{
  "name": "go-starter-kit",
  "version": "0.1.0",
  "description": "",
  "scripts": {
    "eslint": "eslint *.js client",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "olebedev",
  "license": "MIT",
  "dependencies": {
    "@material-ui/core": "^4.10.2",
    "autoprefixer": "^6.7.7",
    "babel-core": "^6.24.1",
    "babel-eslint": "^7.2.2",
    "babel-loader": "^6.4.1",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-polyfill": "^6.23.0",
    "babel-preset-es2015": "^6.24.1",
    "babel-preset-react": "^6.24.1",
    "babel-preset-react-hmre": "^1.1.1",
    "babel-preset-stage-0": "^6.24.1",
    "babel-runtime": "^6.26.0",
    "css-loader": "^0.28.0",
    "eslint": "^3.19.0",
    "eslint-plugin-react": "^6.10.3",
    "expose-loader": "^0.7.1",
    "express": "^4.15.2",
    "extract-text-webpack-plugin": "^1.0.1",
    "file-loader": "^0.11.1",
    "json-loader": "^0.5.7",
    "normalize.css": "^6.0.0",
    "postcss-functions": "^2.1.0",
    "postcss-loader": "^1.3.3",
    "precss": "^1.4.0",
    "proxy-middleware": "^0.15.0",
    "react": "^15.5.4",
    "react-dom": "^15.5.4",
    "react-email-editor": "^1.1.1",
    "react-helmet": "^5.0.3",
    "react-lite-ui": "^1.0.3",
    "react-redux": "^4.4.8",
    "react-router": "^3.0.5",
    "react-router-dom": "^5.2.0",
    "redux": "^3.6.0",
    "redux-logger": "^3.0.1",
    "redux-saga": "^0.16.0",
    "style-loader": "^0.16.1",
    "svgo-loader": "^1.2.1",
    "url-loader": "^0.5.8",
    "webpack": "^1.12.13",
    "webpack-dev-middleware": "^1.10.1",
    "webpack-hot-middleware": "^2.18.0",
    "whatwg-fetch": "^2.0.3",
    "when": "^3.7.8"
  },
  "babel": {
    "presets": [
      "es2015",
      "react",
      "stage-0"
    ],
    "plugins": [
      "transform-runtime"
    ],
    "env": {
      "dev": {
        "presets": [
          "react-hmre"
        ]
      }
    }
  },
  "eslintConfig": {
    "rules": {
      "indent": [
        2,
        2
      ],
      "quotes": [
        2,
        "single"
      ],
      "linebreak-style": [
        2,
        "unix"
      ],
      "semi": [
        2,
        "always"
      ],
      "react/jsx-uses-react": 2,
      "react/jsx-uses-vars": 2,
      "react/react-in-jsx-scope": 2
    },
    "env": {
      "es6": true,
      "browser": true,
      "node": true
    },
    "parserOptions": {
      "ecmaFeatures": {
        "jsx": true,
        "modules": true
      },
      "sourceType": "module"
    },
    "plugins": [
      "react"
    ]
  },
  "main": "index.js",
  "repository": "git@github.com:olebedev/go-react-starter-kit.git"
}

I also got rid of the vendor approach to pinning and have been using Go Modules. My Go Modules looks like
go 1.13

require (
	github.com/dgrijalva/jwt-go v3.2.0+incompatible
	github.com/dlclark/regexp2 v1.2.0 // indirect
	github.com/dop251/goja v0.0.0-20200526165454-f1752421c432
	github.com/dop251/goja_nodejs v0.0.0-20200128125109-2d688c7e0ac4
	github.com/elazarl/go-bindata-assetfs v1.0.0
	github.com/elazarl/goproxy v0.0.0-20200426045556-49ad98f6dac1 // indirect
	github.com/elazarl/goproxy/ext v0.0.0-20200426045556-49ad98f6dac1 // indirect
	github.com/fatih/structs v1.1.0
	github.com/gin-gonic/gin v1.6.3
	github.com/go-sourcemap/sourcemap v2.1.3+incompatible // indirect
	github.com/itsjamie/go-bindata-templates v0.0.0-20170313182150-78f87e838df0
	github.com/jinzhu/gorm v1.9.13
	github.com/joho/godotenv v1.3.0
	github.com/nu7hatch/gouuid v0.0.0-20131221200532-179d4d0c4d8d
	github.com/olebedev/gojax v0.0.0-20170318114811-bb153be84336
	github.com/spf13/viper v1.7.0
	github.com/urfave/cli v1.22.4
	golang.org/x/oauth2 v0.0.0-20200107190931-bf48bf16ab8d
	google.golang.org/api v0.26.0
	gopkg.in/elazarl/goproxy.v1 v1.0.0-20180725130230-947c36da3153 // indirect
)

Would love some help getting Material working with this, thanks @dop251 !

Hey @amlwwalker, it looks like there is a problem with the bundle itself. Can you confirm that was built and all the main function available locally?
You can verify it Node.js:
const bundle = require('./path/to/the/bundle');
bundle.main({ url: '/', headers: {}, uuid: '1' }, (...args) => {
	console.log(args);
})

Hey, thanks for responding
I think i've done as expected:
 ~/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit   amlwwalker/upgrade-engine ●✚  node
Welcome to Node.js v13.9.0.
Type ".help" for more information.
> const bundle = require('/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js');
Uncaught TypeError: _react.default.createContext is not a function
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43829:36)
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43837:31)
    at __webpack_require__ (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:20:30)
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43800:45)
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43812:31)
    at __webpack_require__ (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:20:30)
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43783:41)
    at __webpack_require__ (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:20:30)
    at Object.<anonymous> (/Users/alex/go/src/github.com/amlwwalker/email-gmail/gin-react-starter-kit/server/data/static/build/bundle.js:43390:41)
> bundle.main({ url: '/', headers: {}, uuid: '1' }, (...args) => {
... console.log(args);
... })

Interestingly however, the project seems to be yours

Yeap, and the https://github.com/ntquan1704/gin-react-starter-kit is a fork of my project as well. That's why I answer here.

oh cool!
Have you got any ideas what I might be doing wrong? I am more used to Gin that Echo (if that's the one you are referring to). However does yours work with Material without this error? All support appreciated!

@olebedev I managed to have another look at this.
I cloned the project you mentioned and added import Button from '@material-ui/core/Button'; to the router/index.js
then i changed the render() function to
  render(
      <Button variant="contained" color="primary">
        Hello World
      </Button>,
  document.getElementById('app')
  );

and I get:
webpack built a54c988079af730a3efb in 6406ms
webpack building...
webpack built 18e9f9945c00883feec8 in 687ms
init JSVM static/build/bundle.js
panic: TypeError: Object has no member 'createContext' at bundle.js:45087:49(35)

goroutine 11 [running]:
main.newJSVM.func1(0xc000516180)
	/Users/alex/go/src/github.com/amlwwalker/email-gmail/new-gin-react-material-test/server/react.go:207 +0x4aa
github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop.(*EventLoop).RunOnLoop.func1()
	/Users/alex/go/src/github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop/eventloop.go:109 +0x31
github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop.(*EventLoop).run(0xc0010364c0, 0xc001036a01)
	/Users/alex/go/src/github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop/eventloop.go:116 +0x70
created by github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop.(*EventLoop).Start
	/Users/alex/go/src/github.com/amlwwalker/email-gmail/new-gin-react-material-test/vendor/github.com/dop251/goja_nodejs/eventloop/eventloop.go:87 +0x44
Error: socket hang up
    at connResetException (internal/errors.js:609:14)
    at Socket.socketOnEnd (_http_client.js:463:23)
    at Socket.emit (events.js:333:22)
    at endReadableNT (_stream_readable.js:1201:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)

Looking at line 45087 in bundle.js I see var ThemeContext = _react.default.createContext(null);
Have you any suggestions as to why this might be happening?
I ran yarn upgrade-interactive to update all the packages in the package.json to see if new packages would solve it but same error.


Problems with metric_freq parameter in Python Package

Hello,
I tried to use metric_freq parameter, but it doesn't work.
Placing metric_freq = 10 I expected metric appears in [Output] field every 10th tree but is appears on the every iteration. Could you kindly advise what goes wrong? Thank you

The metric_freq  only work for cli version.
For python package, you can set
verbose_eval : bool or int
    Requires at least one item in evals.
    If `verbose_eval` is True,
        the eval metric on the valid set is printed at each boosting stage.
    If `verbose_eval` is int,
        the eval metric on the valid set is printed at every `verbose_eval` boosting stage.
    The last boosting stage
        or the boosting stage found by using `early_stopping_rounds` is also printed.
    Example: with verbose_eval=4 and at least one item in evals,
        an evaluation metric is printed every 4 (instead of 1) boosting stages.

in the lgb.train .

Thank you!


remove primary_for_device in data migration

Closes: #4104
What's Changed

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

@timizuoebideri1 I fixed the flake8 failures for you since I had your branch checked out to review the changes


feat(contracts): change MAX_COMMIT_SCALAR and MAX_BLOB_SCALAR to 1e18

Purpose or design rationale of this PR
This PR change the value of MAX_COMMIT_SCALAR and MAX_BLOB_SCALAR to 1e18, since we are sure they won't have larger values.
PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[x] feat: A new feature

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] No, this PR doesn't involve a new deployment, git tag, docker image tag
[ ] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change
[ ] Yes

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

Project coverage is 54.30%. Comparing base (ba77a74) to head (e3e9d75).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1354   +/-   ##
========================================
  Coverage    54.30%   54.30%
========================================
  Files          156      156
  Lines        11922    11922
========================================
  Hits          6474     6474
  Misses        4953     4953
  Partials       495      495

Flag
Coverage Δ

contracts
56.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Can't reproduce the results!!!

Hi, firstly, thanks for your contribution, but i can't reproduce the results as you mentiond 31.3 for AP and 55.5 for AP_50%   on val dataset of Cityscape.  I use the recently updated code and 4 GPUs follow the train_alternate_mask_fpn.py script, everything works fine and got 26.4 for AP and 50.0 for AP_50%.

Have you recently pull the latest master to fix the mask flip bug?

Yes, i've  used the  latest master.

##################################################
what           :             AP         AP_50%
##################################################
person         :          0.292          0.601
rider          :          0.245          0.643
car            :          0.483          0.728
truck          :          0.212          0.325
bus            :          0.369          0.516
train          :          0.200          0.369
motorcycle     :          0.164          0.460
bicycle        :          0.183          0.498
average        :          0.269          0.518
Hi， I got this result.

Hi, @fighting-liu @501177639
I'm working on this, I found a mistake made in code refinement. I will make a PR to fix it soon.

My result even worse:
what           :             AP         AP_50%
##################################################
person         :          0.275          0.578
rider          :          0.237          0.638
car            :          0.485          0.731
truck          :          0.192          0.305
bus            :          0.369          0.517
train          :          0.128          0.340
motorcycle     :          0.132          0.381
bicycle        :          0.166          0.464
average        :          0.248          0.494

I just fix it. Please pull the newest version. Refer to PR #66.
I got the result below with factor=0.03 and default configuration.
I'm now trying factor=0.02, it seems better than 0.03. So I set factor=0.02 in the PR.
##################################################
what           :             AP         AP_50%
##################################################
person         :          0.293          0.611
rider          :          0.228          0.614
car            :          0.483          0.720
truck          :          0.236          0.355
bus            :          0.484          0.667
train          :          0.366          0.581
motorcycle     :          0.164          0.402
bicycle        :          0.182          0.497
--------------------------------------------------
average        :          0.305          0.556

Ok, i will try it again and report my results here later!

@Zehaos I got this result with the latest PR (factor = 0.02):
##################################################
what           :             AP         AP_50%
##################################################
person         :          0.288          0.602
rider          :          0.227          0.620
car            :          0.475          0.708
truck          :          0.251          0.392
bus            :          0.427          0.600
train          :          0.281          0.559
motorcycle     :          0.172          0.417
bicycle        :          0.177          0.506
average        :          0.287          0.550
I used 8 GPUs so I doubled the base learning rate to 0.008. Could that be a problem?

@jiang1st  I got the same result with you.
@Zehaos Why do you think factor 0.02 is better? Seems that we get a little lower mAP.

Hey, guys, The original code has a small performance gap with our pretrained model.( ~ 1% drop on AP100, no effect on AP50). With commit #82, the code now should reproduce our result on cityscapes dataset.

Hi @Zehaos, thank you for your prompt reply. What is "factor" used for?  To control the magnitude of gradients coming from the mask branch?

@jiang1st Exactly.

@Zehaos Is it a common practice to adjust this parameter? I didn't see it anywhere in the original paper. Besides, why did you set it to 0.03125 ? Thanks.

@jiang1st It is not mentioned in the paper. In my opinions, it is important to re-weight the additional branch. We set it to 0.25 originally, 0.03125 = 0.25/8. (because of code refinements)

@Zehaos Hi Zehao, I got this result. Possibly because I doubled the base_lr with 8 GPUs? I also notice you are using base_lr = 0.004 with 4 GPUs (Original paper use 0.01 with 8 GPUs). Is there any suggestion on adjusting base_lr and actual batch_size during training process? Thanks a lot.
##################################################
what           :             AP         AP_50%
##################################################
person         :          0.324          0.631
rider          :          0.262          0.656
car            :          0.493          0.722
truck          :          0.235          0.379
bus            :          0.454          0.635
train          :          0.257          0.522
motorcycle     :          0.161          0.404
bicycle        :          0.200          0.527
average        :          0.298          0.559

@jiang1st There is class imbalance problem( AP of truck, bus and train is unstable). According to AP of person and car, it is normal of your result.
In detection task, people tend to use larger batch size(Faster:2, FPN:16, MegDet:256). We set a batch size much smaller than the original paper, maybe a larger batch size can make some improvement.

@Zehaos What's your strategy to adjust the base learning rate (based on the batch size)? Can you offer me some advice? Thank you.

We have reproduced the reported results by our latest codes.  Please pull the newest version, thanks.
##################################################
what : AP AP_50%
##################################################
person : 0.326 0.637
rider : 0.267 0.656
car : 0.494 0.727
truck : 0.285 0.401
bus : 0.469 0.644
train : 0.303 0.562
motorcycle : 0.181 0.428
bicycle : 0.202 0.532
average: 0.316 0.573


The QEMU-based VM registered with limactl start-at-login in launchd does not start.

Description
launchd only sets the PATH environment variable to /usr/bin:/bin:/usr/sbin:/sbin, so limactl fails to start because it cannot find qemu-system-<arch>.
The VM can be started by adding the following configuration to io.lima-vm.autostart.<instance>.plist:
	<key>EnvironmentVariables</key>
	<dict>
		<key>PATH</key>
		<string>/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
	</dict>

It would be beneficial if one of the following were done:

The above configuration is automatically added to io.lima-vm.autostart.<instance>.plist.
The path to the QEMU to be used can be set in lima.yaml, and limactl can utilize it.
An equivalent to the QEMU_SYSTEM_<ARCH> environment variable can be set in lima.yaml, and limactl can utilize it.

Thanks,

This needs to go in _config (somewhere), and not be recorded in the instance lima.yaml


optimize  the pauses of commas and full stops

Self Checks

[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.
Hope to optimize the full stop. In terms of pausing, in Chinese, it feels that the pauses of commas and full stops are the same, resulting in long texts that do not sound cadenced. GPT-Sovits can achieve a better pause for the full stop in long texts to improve the listening experience.
希望优化句号。方面的停顿,中文方面感觉逗号和句号的停顿都一样的,导致长文本,听起来没有顿挫,GPT-Sovits可以实现句号 切,长文本,听感停顿做的好点
2. Additional context or comments
No response
3. Can you help us with this feature?

[X] I am interested in contributing to this feature.

@PoTaTo-Mika Is there a solution to this problem?


⚠ ClamAV has degraded performance

In b2ade4c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 318 ms

Resolved: ClamAV performance has improved in 59590b5.


Hello

hi. Do you think your plugin will fit this socket?
https://www.homewizard.com/shop/wi-fi-energy-socket/

Hi @Prokopchini, this plugin focusses on your overall power consumption. You can use this plugin for Homewizard socket support


Function is called every time when use -context option.

Hi,
When .go file is specified with -context option, and once function f() on .go file is called,
it is called every time even if it is not inputed f().
ex.
env
OS : Mac OS Catalina 10.16.3
Runtime : Go 1.13.6
context.go
package main

import "fmt"

func start() {
	fmt.Println("exec context.go .")
}

$ gore -context context.go
gore version 0.5.0  :help for help
added file context.go
gore> start()
exec context.go .
gore> fmt.Println("on REPL.")
exec context.go . // called 'start()'  again implicitly.
on REPL.
9
nil
gore>

Thanks.

This is a limitation due to the fact that gore is not a real read-eval-print loop tool. See https://github.com/motemen/gore#faqcaveats, #67.


Feature request: Jump/Copy/Replace from/to the splitted pane

One of idea's cool features is splitting the edit window horizontally/vertically.

It would be very nice if emacsIDEA can Jump/Copy/Replace text from/to the splitted pane(s) as well.

Good idea, will put this feature request in backlog.
meanwhile, pull request is always welcome.

@Centaur checkout new release 1.4.2.   Thanks for your ideas.

Wow, Godspeed!


Add logo to mailables

Added the Laravel.io logo to mailables. Mail received now looks like:

Hey @driesvints, it turns out you can't use the embed method when using markdown mailables so I've left it as per @joshuamabina's initial PR, but rebased against master and re-published the templates to bring them up to date with Laravel.

@joedixon is it necessary to publish all templates? I think the default ones are used when you omit them, no? Maybe just publish the ones we're overriding?

I think the default ones are used when you omit them, no?

I think so too, I'll do some testing later 👍

There's a downside and upside from doing that. Upside is we get bug fixes. Downside is that we miss bugfixes in the overwritten file and if for some reason the template ever changed throughly layout-wise then we wouldn't know until we saw an email ourselves. For example: the template in 7.0 will get a fresh layout.

I'm assuming that will be in the release notes though?

@joedixon actually checking with Taylor on that one.

Removed unmodified mail views and also made the colour of the CTA match those on the site.

@joedixon can you merge master into this branch before I merge it? Looks good btw!

Nvm. Merged it 👍
Thanks @joedixon and @joshuamabina for this! Glad we finally got this merged.


Refactoring results in duplicate param name in method signaure, while adding a param

Expected behavior
Should add param with param value given to refactor command.
Steps to reproduce

Refactor Vowels in English language are "" "end" "n" to Vowels in English language are "" "end" "n" "n1"

Expected: String vowelString, String argEnd, String argN, String argVowelstring
Actual: String vowelString, String argEnd, String argN, String argN1

Gauge version
0.4.1

@sguptatw please check if this is still relevant.

@Apoorva-GA : The issue still persists

Steps to reproduce
Refactor Vowels in English language are "" "end" "n" to Vowels in English language are "vowelstring" "end" "n" "n1"
Expected: String argVowelstring, String argEnd, String argN, String argN1
Works fine with latest Gauge-IntelliJ nightly : 0.3.7.nightly-2017-08-18

Refactor to Vowels in English language are "vowelstring" "end" "n1""n" "n". Now the parameter names generated are duplicates

Fix should be available in gauge-java nightly > 31-08-17


Assets don’t update when deployed on release branch

Cache cannot be automatically purged after a release of production version, which causes SRI integrity error and therefore assets cannot be loaded correctly.
Seems like beta version on gh-pages is not affected.

expect to be fixed using service worker.

delayed and expected to be implemented v2.x

current workaround: purge caches in Cloudflare dashboard.


Add convenience methods for integration testing the ECS

What problem does this solve or what need does it fill?
Integration testing is important, but our existing tools for it are boilerplate-heavy.
What solution would you like?
There are a few patterns that come up very regularly, and should be supported directly on the App and World:

assert that the resource of the given type matches the provided value
assert that all components that match a query match the given tuple of values
assert that the number of entities returned by a query is n

Each method on App should just call the underlying method on World.
What alternative(s) have you considered?
These helper methods can be written entirely externally. However, this is suboptimal because:

friction is one of the largest barriers to testing
this code is going to be exactly the same across all serious products created with Bevy
Bevy itself should be integration tested, and would benefit from these ergonomics improvements

Additional context
This pattern is very useful when combined with manually calling app.update() in your integration tests.
#3786 would make organizing these sorts of ergonomics methods more convenient.
I've also written a number of tools for input-mocking that are very useful, but those should be considered in a separate issue / PR.

I'm going to tackle this one :)


Update dotnet-howto-choose-migration.md

Fixed a simple mistake that I noticed while reading the docs.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/dotnet-howto-choose-migration.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fixed all unit tests.

Fixed all unit tests. #3

Fixed #3; Fixed #5;

Fixes Cleancodefactory/NetCoreBundling#3
Fixes Cleancodefactory/NetCoreBundling#5


external subtitles not loading through smb or ftp

I'm using X-plore File Manager to load my movies through smb or ftp and play in JustPlayer on my Firestick 4k max. It's working nice but my external subtitles (.srt) not loading.

The combination of X-plore and SMB works and loads subtitle file on my phone. How about some other device of yours, does it work from your phone? What are the filenames of the video and subtitle?

Same thing on my phone. Filenames are the same (video and sub). Maybe this is SMB1 problem? Strange, in Kodi everything is ok.

It could be SMB1 thing. It depends on the path structure / how file managers expose the path in uri. Kodi manages SMB on its own so it's something different. You could try other player that loads external subtitles over network (I know MX Player does) and check if that works with X-plore.

Ok I've done some testing and for me it was X-plore fault. For example with MiXplorer everything is ok, so I'll stick with it.
Anyways, thx for help!


docs on subscriptions not ideal

Take a situation where you have a subscription A, who's parameters will be obtained from subscription B.
One way of achieving that I know of would be using dynv - for which the docs say " This argument exists for
historical reasons and is borderline deprecated these days."
(re-frame.core/subscribe  [::A args] [(re-frame.core/subscribe [::B])])
What the docs don't say is what this has been deprecated in favour of - that is the first issue that I would like to see addressed.
For a situation like this, I would reach for reg-sub-raw - for which the docstring says: "This is a low level, advanced function.  You should probably be using reg-sub instead."
I found that last bit quite off-putting, so I didn't look into it as early as I should have done and went down the dynv route - which gets tricky when you also have C, D.. and more dependent-parameterized subs. For the situation described, reg-sub-raw is the right solution afaik.
(rf/reg-sub-raw ::A
  (fn [_db [_ args]]
    (ratom/reaction
      (when-let [a @(rf/subscribe [::B args])]
        ;do stuff
        ))))

The docstring does also link to http://day8.github.io/re-frame/flow-mechanics/ which was helpful - and set me on the right path eventually :).  I would suggest the docs said something along the lines of : reg-sub-raw should only be used when dealing with more advanced use cases such as ... xyz.. maybe mention the above scenario or something more general?
Thanks

Hey, thanks for the feedback. It's been a while.
I added mention of reg-sub-raw and the signal function into dynv's explanation. Feel free to reopen this ticket if you feel more could be done.

looks good. thanks


Deal better with approximate/uncertain dates

Currently, a fixed (precision-dependent) and arbitrary amount of fuzziness is added to approximate/uncertain dates. This is used to return a date range that can be used for filtering, but it's a pretty basic interpretation.
Properly, the level of uncertainty will be a curve that ramps continuously between 1.0 ("the given date is a certain match for the EDTF range") to 0.0 ("the given date is certainly not a match").
Open questions:

How are these fuzzy ramps defined? We might get some non-arbitrary results from crowdsourcing interpretations of whether a given date is 'circa' another date, etc. But we're likely to want to find a simple ramping equation.
Are curves significantly more useful than just padding a strict date range? It will allow us to return queries to "Show me works made around 1929" sorted by confidence. Is that a real-world use case?
How can we implement fuzzy matching in a db-efficient format?

Hi, thank you for this library. Still checking out EDTF, but it looks like it solves a lot of issues I've been having. I know other implementations exist, but our main backend language is Python (and this seems like one of the more complete implementations anyway).
I have done research on querying fuzzy time intervals that might be of interest, have a look at http://samm.univ-paris1.fr/IMG/pdf/paris2014.pdf or https://www.researchgate.net/publication/266750215_Modelling_Imperfect_Time_in_Datasets. If you can read Dutch, have a look at http://lib.ugent.be/fulltxt/RUG01/001/418/820/RUG01-001418820_2010_0001_AC.pdf. We have implemented this for postgresql in a fairly efficient way, see https://github.com/OnroerendErfgoed/pgSFTI for a native C implementation and https://github.com/koenedaele/pgFTI for a pure SQL implementation (based on Postgis).
When implementing solutions like these I have found that the main hindrance is user adoption. Something like fuzzy sets (what my work is based on) is very hard to understand to most art historians and archaeologists. But I'm thinking that capturing information as EDTF and then generating Fuzzy Time Intervals from them might work very well.
I have no good solution for translating from ca. 1905, to a fuzzy time interval. (Does that mean probably in 1905, but possibly in 1904 or 1906; or does that mean somewhere between 1900 and 1910 but probably more towards the middle). I think it's inherently contextual and hard to solve for eavery use case.


[FEATURE] Support bump branch whitelist

Is your feature request related to a problem? Please describe.
Commonly, you want to prevent git bump from the non-main branch.
Describe the solution you'd like
Add a whitelist to the config:
bump_branch_whitelist = ["main"]

Then bumping from dev branch:
$ cog bump --auto
You are currently on branch `dev` which is not in the bump branch whitelist.
Supported branches:
  - main

Describe alternatives you've considered
You can add a manual script in pre_bump_hooks:
pre_bump_hooks = [
  # Prevent bumping from non-main branch
  """
  sh -c "[[ \\"$(git rev-parse --abbrev-ref HEAD)\\" != \\"main\\" ]] && echo \\"[error] you can only bump version on main branch\\" && exit 1"
  """
]

But it's quite long and seems like a common enough feature to be built in.

closed by #165
coming in next release


[flutter_tools] FormatException parsing XCDevice._getAllDevices

On stable/2.5.1
In daemon command.
Thread 0 main threadFormatException: FormatException: Missing expected digit (at character 3)[-[SimLaunchHostConnection _onQueue_launchInstanceUnload:]_block_invoke:302...  ^
at _ChunkedJsonParser.fail(convert_patch.dart:1405)
at _ChunkedJsonParser.parseNumber(convert_patch.dart:1269)
at _ChunkedJsonParser.parse(convert_patch.dart:937)
at _parseJson(convert_patch.dart:40)
at JsonDecoder.convert(json.dart:506)
at JsonCodec.decode(json.dart:157)
at XCDevice._getAllDevices(xcdevice.dart:115)
at <asynchronous gap>(async)
at XCDevice.getAvailableIOSDevices(xcdevice.dart:227)
at <asynchronous gap>(async)
at IOSDevices._onDeviceEvent(devices.dart:103)
at <asynchronous gap>(async)

Another stacktrace:
Thread 0 main threadFormatException: FormatException: Unexpected character (at character 2)[+[SimLaunchHostClient launchHostClientForRuntime:error:]:82] ERROR : Faile... ^
at _ChunkedJsonParser.fail(convert_patch.dart:1405)
at _ChunkedJsonParser.parseNumber(convert_patch.dart:1272)
at _ChunkedJsonParser.parse(convert_patch.dart:937)
at _parseJson(convert_patch.dart:40)
at JsonDecoder.convert(json.dart:506)
at JsonCodec.decode(json.dart:157)
at XCDevice._getAllDevices(xcdevice.dart:115)
at <asynchronous gap>(async)
at XCDevice.getAvailableIOSDevices(xcdevice.dart:227)
at <asynchronous gap>(async)
at IOSDevices._onDeviceEvent(devices.dart:103)
at <asynchronous gap>(async)

Instead of giving valid output it's showing a crash trace from the xcdevice call on stdout instead of the expected stderr.  I don't see any results when I google that SimLaunchHostClient symbol.  Let's just log it as an error and continue, since it's possible the user doesn't care about iOS device discovery, and we don't want to block them from, say, debugging on a simulator on their Android device.

Although, from daemon that log message wouldn't be very obvious...

Also, wow, it crashed, logged to stdout, and still returned a 0 error code.
https://github.com/flutter/flutter/blob/57efbd5310bd1ed604b3ede2a7073fef47654d00/packages/flutter_tools/lib/src/macos/xcdevice.dart#L114-L118


[kusa1251] change (delete/merge with [hoav1238]) request

The coding for Kusaghe-Njela [kusa1251] cites (exclusively) "Davis 2003 A Grammar of the Hoava Language, Western Solomons". Not only does this source seem to reflect a different language (Hoava [hoav1238]), but this other language is already coded in GB. The coding for "both" languages seems nearly identical, but with some slight differences in the comments.

Thanks for your comment @barlowrussell . We've been discussing this over at glottobank/grambank as well and found a resolution.
Just in general, if there is a variation between sub-varieties below the language level we do separate sheets, however, small the difference.

To recap the discussion over at glottobank/grambank for this public repos:
Nataliia noted:
kusa1251 is coded based on a grammar for hoav1238: Davis 2003 is a source listed for Hoava on glottolog. The running language name used in the Davis 2003 grammar is also Hoava and not Kusaghe-Njela. Please check.
Hedvig found that Naomi had submitted this to Harald a while ago:
In regards to Hoava, there is a misclassification in Glottolog. Davis discusses the lack of difference between Hoava and Kusaghe and says they are the same language (2003:8). There is some discussion on how speakers believe they are the same language, and how Tryon and Hackman (1983) misclassified them upon inaccurate data. A single language called 'Hoava-Kusaghe' with three dialects (Hoava, Kusaghe and Njela) is more accurate.
Harald said that this is in a glottolog to do-list:
thanks for the sheets and for the explanation re Hoava and Kusaghe. I completely agree with you and I will change the next edition of Glottolog accordingly.
The matter is currently lying with Harald at Glottolog.


Add collection FractalCube

Does recursive inscription affect operation?

Please check your json file. @FractalCubes
And the twitter account is restricted.

We have submitted the review for several days and may have been misunderstood and reported by the user

Due to the review process, it has been postponed for a long time

Can the document indicate where the problem lies?


Fathom::Client can't be found

Well, this is weird. Fathom can be resolved but not Fathom::Client. Any idea what could be going on here?
➜  rails git:(open-startup) ✗ bundle exec rails c
Loading development environment (Rails 7.0.1)
[1] pry(main)> Fathom::Client
NameError: uninitialized constant Fathom::Client
from (pry):1:in `__pry__'
[2] pry(main)> Fathom
=> Fathom

Also, amazing that you have a gem for this! I need to do a single fetch for one metric and this looks perfect. Thank you!

Well, it might help if I include the right gem...
Note for future self: this gem is fathom_api, not fathom!

Ahh thanks @joemasilotti! Sorry I didn't see this until now!


[event-hubs][service-bus][core-amqp] fix incorrect logging

In Event Hubs, we found that sometimes the connection id a consumer or producer was using was logged incorrectly as a previous connection id.
Here's a link to discussion around this in PR #14844
https://github.com/Azure/azure-sdk-for-js/pull/14844/files/3a27f381d503f07db136d10e70aabdb0912d448a#r615148008
In some cases, especially where we call the retry method, we were copying the connectionId value from our connection context into a new object we passed to retry. What this meant was that if our context updated the connection id, such as when a disconnect is encountered and a new connection is created, the options passed to retry would still reference the original copy, not the new value.
This issue is meant to be used to identify the places where we copy the connectionId value and convert it to a getter. This needs to be verified in core-amqp, event-hubs, and service-bus.

Potential idea: enhance the logger to carry the "log prefix" data and a way to refresh it. This would simplify some of our internals a bit where we pass around the prefix and eliminate this problem at the source.


Error: EMFILE, too many open files '/home/ubuntu/***/views/auth'

I get the following error if too many user visit my sever:
[36mverbose [39m: Shutting down socket server...
Error:
  code: 'EMFILE',
  path: '/home/ubuntu/***/views/auth',
  syscall: 'readdir' }
 [31merror [39m: Sending 500 ("Server Error") response:
 Error: EMFILE, too many open files '/home/ubuntu/***/views/auth'
    at Object.fs.readdirSync (fs.js:665:18)
    at Glob._readdir (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:662:20)
    at Glob._process (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:446:15)
    at Glob.iterator (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:181:10)
    at Array.forEach (native)
    at new Glob (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:179:22)
    at glob (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:57:11)
    at Function.globSync [as sync] (/home/ubuntu/***/node_modules/sails/node_modules/glob/glob.js:76:10)
    at globPath (/home/ubuntu/***/node_modules/sails/lib/hooks/http/view.js:17:15)
    at exists (/home/ubuntu/***/node_modules/sails/lib/hooks/http/view.js:23:10)
    at SailsView.lookup (/home/ubuntu/***/node_modules/sails/lib/hooks/http/view.js:40:6)
    at View (/home/ubuntu/***/node_modules/sails/node_modules/express/lib/view.js:44:20)
    at new SailsView (/home/ubuntu/***/node_modules/sails/lib/hooks/http/view.js:32:15) { [Error: EMFILE, too many open files '/home/ubuntu/***/views/auth']
  errno: 20,
  code: 'EMFILE',
  path: '/home/ubuntu/***/views/auth',
  syscall: 'readdir' }

My Sails version: 0.10.5
I increase the ulimit -n from 1024 to 2048 but I think this is not a real solution.

@RSSGergelyMunkacsy Perhaps too many users is a good problem to have.  You aren't alone in the scalability woes of having to update ulimit settings.  That actually is the first thing I do when I setup new VMs because I am typically building apps that expect over 1k users hitting them at one time.  I don't consider it to be a problem as it is naturally part of my solution to set that number about 64k.

So, is this an issue/error or did @crh3675 clear things up? Can we close this?


moves file structure from psr-0 to psr-4

Coverage decreased (-74.9%) to 25.128% when pulling ab4b92c850b710157b19646a7127d31b0faa9afb on feature/psr-4 into b25f29de532f2920a7e2c91f74bb180f3d97e953 on master.


APCu support for PHP 8.0

Describe the bug
setup-php reports ✗ apcu Could not install apcu on PHP 8.0.0 while the latest version of APCu supports PHP 8.0:
https://pecl.php.net/package-info.php?package=APCu&version=5.1.19
Version

[ ] I have checked releases, and the bug exists in the latest patch version of v1 or v2.
[x] v2
[ ] v1

Runners

[x] GitHub Hosted
[ ] Self Hosted

Operating systems
runs-on: ubuntu-18.04
PHP versions
8.0
To Reproduce
name: Build

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]

jobs:
  build:
    name: Build

    runs-on: ubuntu-18.04

    strategy:
      matrix:
        php:
          - version: "7.4"
            allow-fail: false
          - version: "8.0"
            allow-fail: true

@dbalabka
Fixed, please try again
Test workflow: https://github.com/shivammathur/test-setup-php/actions/runs/372170734/workflow
- name: Setup PHP
  uses: shivammathur/setup-php@v2
  with:
    php-version: '8.0'
    extensions: apcu

Works. Thanks!


Please invite me to the community

Name
LittlyPony
Additional Context
No response

Invitation sent to join the GitHub Organization. Welcome to Infraform 🎉Please check your mail to accept the invitation sent by GitHub! 🤖About usInfraform is an open source solution for serverless platforms, it is designed for developing solutions and enhancing creators to create their infrastructure 💻 Great to have you in our community ✨ Looking forward to your valuable contributions! 🤓 You can also check our community ✨ Github ✨ LinkedIn 💜 You can also share our community with other folks who want to learn about development, DevOps, tech, and contribute together and with us 👉💜👈

Welcome to the team!


Migrate to Google Analytics 4

Extremely low priority, given that we aren't maintaining this project at the moment.
In any case, the Universal Analytics account currently in use will stop collecting data on 1 July 2023. This is the Analytics 4 account that would replace it:
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-B6TJS8QEE3"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-B6TJS8QEE3');
</script>

Actually, nevermind, it seems like if we do nothing, Google may generate a new Analytics 4 property that reuses the old site tag. Let's wait and see.


Fix relative paths with bundleDependencies=false

When bundleDependencies is turned off, webpack is configured to bundle all modules imported via relative path.
It works well for import paths like './some/file' but fails for imports traversing the dir structure up, like '../some/file'.
In most cases it would still work well, because of the additional fallback (which checks whether node can resolve this module at all). However, in rare cases this fallback fails (see https://github.com/angular/universal/issues/1792)
Closes: #18493

@googlebot I signed it!

Thanks for the super quick feedback @alan-agius4  - quite impressive!

@alan-agius4 I have a followup question though.
While the PR seems to fix the specific issue I was facing, I'm wondering if there are more cases that could fail like that.
As I mentioned, despite the incomplete original check for partial path, the builds tend to work well.
The reason is that if this check returns false, the code below has an extra check - tries to resolve the path via require.resolve. But this resolve call is performed in the context of server.ts file, not in the context of the compiled module.
Hence, in my case the "../../../utils" path was successfully resolved! Because it matches utils from angular_devkit itself
<EMAIL_ADDRESS>
Do you think it's possible that this check can potentially give false positives for some arbitrary user module alias, if it also happens to match some internal module from devkit?

@amakhrov, glad you hear that you had a good experience contributing to the Angular CLI. 😁
I do think that there are some rare edge cases, where using require.resolve(request) might cause undesired behavior. A more correct way would be to changing the resolutions paths to use the workspace root path. require.resolve(request, { paths: [wco.root] }).


Icons have a super low resolution

I have an HiDPI display and the icons look veeery pixelated. Is it possible to have some higher resolution icons? I can't find any SVG source file.

Ah, no, the icons are bitmaps that are generated by programatically joining together the 'subicons', which are also bitmaps (and they are pretty small bitmaps seeing as I want to be able to squish 4 'subicons' into each icon in order to show all the status information).
I've been planning on making them SVGs and programatically joining them using some SVG library, but I haven't done this yet.

I've updated the icons to be svgs. They are not the prettiest icons ever, but it should be an improvement. Could you let me know if it looks better on the high DPI display?

Now they don't show up at all lol

Maybe you should simply provide the bitmaps (i.e. use inkscape to raster-ize them), but also provide a 48x48 version as 24x24@2x like some themes do.

🤔🤔🤔🤔

Much better now!

Thank you!

Thanks and well spotted!
I was just copying example code from the svgutils docs that used strings with 'cm' the size, and I changed it to 'px' and it worked...not sure why that makes any difference (worked for me!) but glad it's fixed for you!

I tried to save it from Inkscape as optimized SVG and the plugin complained about an unrecognized "px" string.
There it is 😅


008.sh UPF Capacity Scaling

Draft 008.sh script for UPF scaling

/ok-to-test

Hey @rravindran123 can you sign the CLA for fixing the CI task?

/check-cla

/check-cla

/easycla

@rravindran123 Looks like some commits were made with your other GH account which does not have the EasyCLA signed. Can you sign that for your other account too?

Awesome, looks great. I'll add an issue to remind us to add in two more checks in a follow on PR.
/approve
/lgtm

FYI: https://github.com/nephio-project/nephio/issues/311 for follow up work


Tooling: NPE in BuildProgressLogger

The original request can be found at https://youtrack.jetbrains.com/issue/IDEA-176336

I have been using IntelliJ with gradle but upgrading IntelliJ to 2017.2 is causing problems. When I try and load the project in IntelliJ with both gradle 4.0 and 4.0.1, I get the following error:

Error:Could not run build action using Gradle distribution 'https://services.gradle.org/distributions/gradle-4.0.1-all.zip'.

I get this error when I try to do a project refresh.

Caused by: org.gradle.internal.exceptions.LocationAwareException
    at org.gradle.initialization.DefaultExceptionAnalyser.transform(DefaultExceptionAnalyser.java:74)
    at org.gradle.initialization.MultipleBuildFailuresExceptionAnalyser.transform(MultipleBuildFailuresExceptionAnalyser.java:47)
    at org.gradle.initialization.StackTraceSanitizingExceptionAnalyser.transform(StackTraceSanitizingExceptionAnalyser.java:30)
    at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:68)
    at org.gradle.tooling.internal.provider.SessionFailureReportingActionExecuter.execute(SessionFailureReportingActionExecuter.java:42)
    at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:50)
    at org.gradle.tooling.internal.provider.SetupLoggingActionExecuter.execute(SetupLoggingActionExecuter.java:30)
    at org.gradle.launcher.daemon.server.exec.ExecuteBuild.doBuild(ExecuteBuild.java:67)
    at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.WatchForDisconnection.execute(WatchForDisconnection.java:37)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.ResetDeprecationLogger.execute(ResetDeprecationLogger.java:26)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.RequestStopIfSingleUsedDaemon.execute(RequestStopIfSingleUsedDaemon.java:34)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:74)
    at org.gradle.launcher.daemon.server.exec.ForwardClientInput$2.call(ForwardClientInput.java:72)
    at org.gradle.util.Swapper.swap(Swapper.java:38)
    at org.gradle.launcher.daemon.server.exec.ForwardClientInput.execute(ForwardClientInput.java:72)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:55)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:62)
    at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)
    at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
    at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
    at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
    at org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
    at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
    at org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46)
    at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: java.lang.NullPointerException
    at org.gradle.internal.progress.BuildProgressLogger.beforeComplete(BuildProgressLogger.java:87)
    at org.gradle.internal.progress.BuildProgressFilter.beforeComplete(BuildProgressFilter.java:107)

Your Environment
IntelliJ 2017.2
Gradle 4.0 and 4.0.1

The OP said that the clean install of IDEA helped: https://youtrack.jetbrains.com/issue/IDEA-176336#comment=27-2334538
So, you can close the issue if you wish.

Hhmm, for now I'd probably close the issue. Please reopen the issue if you see this happening again.

I also have the same problem using gradle wrapper:
Error:Could not run build action using Gradle distribution 'https://services.gradle.org/distributions/gradle-4.0.1-all.zip'.

@sprengerst Do you get the same stacktrace (NPE at BuildProgressLogger.java:87)?
Is there a chance that you can provide a reproducible example?

@jjohannes
I'm sorry it's based on company sources, I think it has to do with the update to 4.0.1.
Now I downgraded back to 3.5 and Intelli Idea asks for:
Error:com/android/builder/model/NativeAndroidProject : Unsupported major.minor version 52.0. Please use JDK 8 or newer.
and interprets my gradle project as Android project.
It's pretty confusing, because it worked very good with 3.5 for a long time, after updating to 4.0.1 in gradle wrapper it errored. I also reinstalled everything and used a local gradle distribution, with the same result. I will investigate further and post details if I encounter some.

@sprengerst thanks for investigating further. If you have any insights that you can not share here, feel free to send a mail to jendrik at gradle.com.

@jjohannes One thing that could be interesting is that "gradlew" is working correctly, this issue happens only at pressing the "Sync" btn in Intellij Idea, so maybe this is could be an Intellij 2017.2 issue. I will try to downgrade Idea.

The idea downgrade did it. Now I'm running at 2017.1.5 instead of 2017.2. I have to work a little bit now, lost too much time on this atm ^^, but maybe this could also be a hint for you @jjohannes. Is gradle plugin working on 2017.2 at all?

@sprengerst  it's a different problem: https://youtrack.jetbrains.com/issue/IDEA-176192

@CrazyCoder kk. Thanks for this link.


Components registered with the name "filter" silently fail

Version
2.2.6
Reproduction link
https://jsfiddle.net/50wL7mdz/24931/
Steps to reproduce
Create a component and register it with the name "filter", then try to use it. No errors are thrown, but the component is never instantiated (<filter> elements are never "Vueified").
What is expected?
The <filter> element should be detected and the registered component created correctly, or an exception should be thrown.
What is actually happening?
Silent failure. The <filter> component never gets created, and no exception is thrown.

Seems to happen with "map" too, so I'm guessing it's related to the Array.prototype methods of the same name.

map is a reserved HTML element and filter is an SVG element. Therefore both are prohibited. If you run the fiddle with the development console open you should see the warning message in there.

Use the development build during development.


Support Julia 1.8

Please update https://github.com/JuliaCI/GCBenchmarks/blob/902c74f43760030d2d156b26a9aa8417677ba754/.buildkite/pipeline.yml#L9 with 1.8, 1.9


bump hm-rega to 3.0.47 / hm-rpc to 1.15.19

adapter check Check hm-rpc OK

hm-rega
3.0.47 created 08.08.2023

1000 user
OK

hm-rpc
1.15.19 created 8.8.2023

1000 user
OK


openssl command not found in Azure CLI 2.43.0 docker image

Symptom
The latest Azure CLI 2.43.0 docker image doesn't contain openssl command anymore.
> docker run -it mcr.microsoft.com/azure-cli
0c12bf6c7b2f:/# openssl
bash: openssl: command not found

This causes failure if a user's workload relies on openssl command.
Root cause
According to Alpine Linux 3.17's release history:
https://alpinelinux.org/posts/Alpine-3.17.0-released.html

OpenSSL 3.0 is now the default OpenSSL version. OpenSSL 1.1 is available via the openssl1.1-compat package.

openssl package in alpine:3.17 is now OpenSSL 3.0:
> docker run -it alpine:3.17
# apk search openssl
...
openssl-3.0.7-r0

OpenSSL 3.0 is not compatible with cryptography 3.3.2 which Azure CLI currently uses. For compatibility with cryptography, we now installs openssl1.1-compat:

https://github.com/Azure/azure-cli/pull/24768

openssl1.1-compat installs /usr/bin/openssl1.1 command:
# apk add openssl1.1-compat
# apk info --contents openssl1.1-compat
openssl1.1-compat-1.1.1s-r0 contains:
usr/bin/openssl1.1
# command -v openssl1.1
/usr/bin/openssl1.1

Because openssl package is not installed anymore, /usr/bin/openssl command is not available.
For the released docker image, Azure CLI (az command) is the only tool that is guaranteed to work. The availability of other tools or packages are not guaranteed. If you rely on a certain tool or package such as openssl, you have to manually install it with apk add before using it.
However, it is still a good practice for us to explicitly mention such changes. For example:

https://github.com/Azure/azure-cli/pull/21206

Proposed solutions

Install openssl, either in the docker image by us or by your own workload. This will make openssl command available again, but this may introduce other breaking changes as openssl 3.0 may not be backward compatible with openssl 1.1, even though they share the same name.
Switch to using openssl1.1 in your workload, until you have fully tested openssl 3.0 works as expected with your workload.
Temporarily use Azure CLI 2.42.0 docker image until we add openssl in Azure CLI 2.44.0.
We make a symbol link for openssl that points to openssl1.1 in the docker image, but this is very difficult to maintain and introduces more inconsistency and complexity.

Additional information
https://github.com/Azure/azure-cli/pull/22864 unpinned the base image Alpine Linux version. Now I am more inclined not to do so, as Alpine Linux frequently introduces breaking changes. We should also declare the version update in our history notes if we update the underlying base image version. However, a side effect is that CVEs of the base image can't be fixed automatically and quickly, which is the original motivation for unpinning it.

A really good description about openssl issue

openssl-dev conflicts with openssl1.1-compat-dev:
# apk add openssl-dev
ERROR: unable to select packages:
  openssl-dev-3.0.7-r0:
    breaks: openssl1.1-compat-dev-1.1.1s-r0[!openssl-dev]
    satisfies: world[openssl-dev]

I agree that Azure CLI (az command) is the only tool that is guaranteed to work.
The image should only contains the main program to keep it small and simple. The official Best practices for writing Dockerfiles also suggests Don’t install unnecessary packages. I think the right thing to do is remove it from docker in breaking window.
In Python-alpine Dockerfile, the building dependencies are added in the build-dep virtual package and removed after Python is built.

apk add --no-cache --virtual .build-deps
apk del --no-network .build-deps; \

We have released a new image for 2.43.0 that has openssl installed. You may run docker pull to get the updated 2.43.0 image or use the latest version (currently 2.44.1).

Why did you remove openssl after version 2.53.1?
We still need it.


feat(AdvanceSteel): Converting AS Slab to Speckle

Description & motivation

Converting Advance Steel Slab object to Speckle
Organize Speckle objects for Advance Steel into different files

Changes:

To-do before merge:

Screenshots:

Validation of changes:

Checklist:

[ ] My pull request follows the guidelines in the Contributing guide?
[ ] My pull request does not duplicate any other open Pull Requests for the same update/change?
[ ] My commits are related to the pull request and do not amend unrelated code or documentation.
[ ] My code follows a similar style to existing code.
[ ] I have added appropriate tests.
[ ] I have updated or added relevant documentation.

References

@teocomi I think it´s ok


UWP: Make buttons' hover emphasis consistent

The emphasis applied to some buttons when hovering over them with a mouse cursor differs a bit.
Consider making these the same.

@nCastle1 looks like this change got picked up and is addressed with the latest builds:


Faithfully transmit and adhere to time_format across functions

In many places, default format is used even though a user-specified format exists.

Please mind https://github.com/sanskrit-coders/jyotisha/issues/73 as you go about fixing this 🙏

fixed via ad3fac75bbefd90e12bd74d34220441ea7db79a5 and 81e5a885a6b3a47d5cd6ceb82b4a2b9e219774b5


MINIFICPP-2251 Make OPENSSL and CURL mandatory

MINIFICPP-1872 Unify test utilities

Remove OpenSSL and Curl options and make them part of the libminifi core
Remove http extension and make it part of libminifi core and InvokeHTTP processor part of standard-processors
Move HTTP tests as part of libminifi integration tests
Extract test library in libminifi, with separate integration and unit test library
Make test utilities part of the test library
Move all tests to their proper unittest or integrationtest folder in libminifi
Convert integration tests to use the catch2 framework and remove executable parametarization

https://issues.apache.org/jira/browse/MINIFICPP-2251
https://issues.apache.org/jira/browse/MINIFICPP-1872

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

@szaszm I agree MINIFI_OPENSSL and ENABLE_CURL should now no longer be minifi_options, they must be enabled in order to successfully build libminifi. However, for the case of building libarchive, we can build libarchive with openssl enabled set to true or false. Did you make it mandatory for minifi extensions that use openssl?
In my PR-1775 for MINIFICPP-2346: I do note about the critical minifi options that must be enabled to successfully build libminifi. I found that ENABLE_OPENWSMAN, ENABLE_CIVET must also be ON for libminifi to build succssfully. Those 4 minifi options are the minimum to build libminifi C++ core-minifi, mainexe and standard processors.

I also mention about the options that must be enabled to build GTESTs. Furthermore, I am wrapping up testing enabling all the remaining extension.

@szaszm I agree MINIFI_OPENSSL and ENABLE_CURL should now no longer be minifi_options, they must be enabled in order to successfully build libminifi. However, for the case of building libarchive, we can build libarchive with openssl enabled set to true or false. Did you make it mandatory for minifi extensions that use openssl?
In my PR-1775 for MINIFICPP-2346: I do note about the critical minifi options that must be enabled to successfully build libminifi. I found that ENABLE_OPENWSMAN, ENABLE_CIVET must also be ON for libminifi to build succssfully. Those 4 minifi options are the minimum to build libminifi C++ core-minifi, mainexe and standard processors.
* I also mention about the options that must be enabled to build GTESTs. Furthermore, I am wrapping up testing enabling all the remaining extension.

@james94 how did you find the ENABLE_OPENWSMAN must be ON for libminifi build to succeed? I managed to build it successfully without it and it should be a separate extension that should not have any effect on the core libminifi.
We also had some discussions in the past if civetweb should be part of the core libminifi, but we decided not to due to the following reasons:

It is not actually required by core libminifi, it is only needed for the tests and some of the extensions. If you build libminifi with SKIP_TESTS=ON and turn off civetweb extension the libminifi should build successfully
We had some concerns about the civetweb codebase so we may replace it in the future with a different library, so we would rather not include it in the core libminifi

@lordgamez hi,
when I was talking about ENABLE_OPENWSMAN, I think I was more referring to the combination of libminifi "core-minifi" and MiNiFi Main's  minifiexe being dependent on the following external libs being enabled: ENABLE_OPENWSMAN, ENABLE_OPENSSL, ENABLE_CIVET, ENABLE_CURL. Also SKIP_TESTS was set to ON.
Yes I do agree with you some of these externa libs like ENABLE_OPENWSMAN shouldn't impact libminifi "core-minifi".
I will get back to you as I am adding conan v2 updates on top of your branch with my new branch MINIFICPP-2346-P1.


Dockerize the application

[x] Ensure all dependencies are in the requirements.txt
[x] Make it runable in docker

Nice job!


Design document comments

Excellent job on the user requirements and component design. If you have a major change in direction, you should update the document. Otherwise, do you final updates at the end of the project to communicate clearly what you actually did.

all design documents are complete. closing the issue.


Reported number of targetted IoT Edge devices for a deployment is incorrect

Today I've noticed that the number of targetted devices for an IOT Edge deployment in Azure IoT Hub is incorrect:

This overview shows that 8 devices are targetted, but in fact, this deployment only targets half of that amount:

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

ID: 877a68cb-b6ad-52a2-64ff-2965e936b3a0
Version Independent ID: 07f38c9a-bafb-bfeb-01e9-cfc420d844b5
Content: Deploy modules at scale in Azure portal - Azure IoT Edge
Content Source: articles/iot-edge/how-to-deploy-at-scale.md
Service: iot-edge
GitHub Login: @PatAltimore
Microsoft Alias: patricka

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

We are looking into this.

I have multiple IoT Hubs, all deployed using the same ARM template but to different Azure Subscriptions.  (One subscription per environment [dev, tst, ...]).
The issue occurs on our IoT Hub in Production.  Obviously, I cannot just delete and re-create that IoT Hub.  This specific IoT Hub is deployed in West Europe.
Previously, this issue did not occur on this IoT Hub.  When I go into the details of the deployment, the reported amount of targetted devices is correct, however, on the deployment overview, the reported amount is double of what it should be.  (I can see the same happening for all the deployments that I have on that IoT Hub).
I also have an acceptance environment where I have an IoT Hub deployed, also in West Europe.  The same issue occurs there.
Then, I have 2 IoT Hubs in the dev and test environments.  These IoT Hubs are deployed in North Europe.  On the North Europe Iot Hubs, the issue does not occur.

t Europe where the issue occ

@fgheysels Looks like the issue needs deeper investigation to identify why the West Europe Region's IoT Hub is having issue with the target deployment device count!
Did you try to submit any technical Support ticket to Microsoft? if not already, I would suggest to do that as this is impacting your Production workload/
Please let us know immediately if you need any further help with support ticket and we would be happy to assit, before we close this thread.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.
Please also do visit Microsoft Q&A the home for technical questions and answers at Microsoft.

@SatishBoddy-MSFT I have opened a support ticket but it seems that the support ticket has also been closed without any further ado.


Panic when Registration is dropped from non-main thread

We have a project, which uses mio + tokio-core + futures + futures-cpupool to implement some network protocol (basically - sending and responding to messages). Everything works fine, but on rare occasion (too rare actually -it is a big problem to reproduce it), our main thread (which polls tokio-core event loop) panics with next stack (it is about v0.6.4, but on latest master issue remains):
  10:     0x5579b378c5af - mio::poll::Poll::poll::hc960007ac1ed502f
                        at /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/obj/../src/libcore/macros.rs:21
                        at /home/svyatonik/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.6.4/src/poll.rs:816
                        at /home/svyatonik/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.6.4/src/poll.rs:744
                        at /home/svyatonik/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.6.4/src/poll.rs:654
                        at /home/svyatonik/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.6.4/src/poll.rs:251
  11:     0x5579b37863df - tokio_core::reactor::Core::poll::h43f4b499158d6eeb
                        at /home/svyatonik/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-core-0.1.4/src/reactor/mod.rs:272

So this unwrap leads to panic:
https://github.com/carllerche/mio/blob/master/src/poll.rs#L816
Giving that head in this unlink method is actually ReadinessQueueInner::head_all_nodes, I have examined poll.rs to find how it is changed. Here I have found one suspicious method.  head_all_nodes is set to None here:
https://github.com/carllerche/mio/blob/master/src/poll.rs#L702
And it only filled back with Some couple of lines above:
https://github.com/carllerche/mio/blob/master/src/poll.rs#L710
I have a test for this situation in this commit:
https://github.com/svyatonik/mio/commit/58e535e6081573db98b546247f3af6c1c1f0b974
If you'll run it with reset && cargo test -- drop_registration_from_non_main_thread, it will fail eventually.
But I'm still not sure - if that's a RegistrationQueue issue, or is it improper usage? Is it OK to drop Registration-s from cpupool threads, or not?
If it is not OK, then I will probably move this issue to futures-rs, because sometimes it is actually dropped from other threads - I have reproduced it while debugging. Drop is starting here:
https://github.com/alexcrichton/futures-rs/blob/futures-cpupool-0.1.2/futures-cpupool/src/lib.rs#L267

There's a chance that the situation is opposite - drop occurs in main thread && new Registration is created in one of cpupool threads. But that single time I have got this situation in gdb was just after the drop from cpupool thread.

Seems bad! I will investigate.

Alright, the panic happens locally. I'm going to dig in now :)

I have a solid hunch as to what the issue is, that being said even the test case takes a while (an hour) to trigger... so it is hard to be sure.

This should be fixed on master.


why the field name namespace is a reserved keyword?

What's the reason having namespace be reserved keyword. Trying to make metric bond definition where metric has a namespace. Forced to use non human readable ns or long metricNamespace. Both options feel wrong

"namespace" is a keyword in both C++ and C# and cannot be used to name an identifier. The following C++ struct will not compile:
struct foo {
    bool namespace;
};

Nor will the following C# class:
class foo {
    bool namespace { get; set; }
}

The original architecture of Bond and the current implementation don't have a way to rename a struct or field when generating code for a specific language, so to avoid generating code that will not compile, Bond reserves the union of the C++ and C# keywords (and some other keywords that is uses itself) as reserved identifiers.
This could be worked around in C# only by using the @ prefix for the name. The following C# class does compile:
class foo {
    bool @namespace { get; set; }
}

Since the @ prefix is not a general solution to the problem in all languages, I'd be hesitant to implement it for just C#. I don't want to make it easy to accidentally define a schema that only works in one language. That defeats much of the point of a cross-language library like Bond.


[RFC] Use the revive checker for style checks

Unlike the rather strict golint tool the revive tool is configurable and will allow us to incrementally improve things and/or leave suboptimal items in place for backwards compatibility. This initial pr adds configuration for revive and uses it in the Travis CI config and Makefile.

If acceptable, this item sort of supersedes issue #82 which requires all golint issues to be fixed at once (and permits no disagreement).


Islands (place=island)

Tracking issue for islands. Available in the tiles as point features (representing some sort of centroid).

Only available from z8, which is only useful for the smallest of islands. Needs OMT fix. There's also ‘rank’ but an explicit numeric value of “what’s the area in fractions of a map tile” is probably the most useful. osm-carto won’t label both Ireland and Great Britain at any common zoom level, for instance.
I think OMT ignores place=islet.
Islands can be coterminous with administrative boundaries at all levels, populated places, and protected areas. In many cases this would land the labels right on top of each other. Adjusting the label placement with text-variable-anchor and text-radial-offset possibly zoom dependent, might be smart.
There's also a place=archipelago multipolygon, but it's not in the tiles and the best use of these shapes might be to generalize as curving text lines.
I won't claim to have looked at lots of paper maps but italic text for natural features is also used for water features, feels right.

Experimental screenshots and osm-carto screenshots without further commentary:

I'd note a few other landforms that should probably be labeled similarly to islands:

natural=cape
natural=peninsula
natural=isthmus

Unlike islands, most of these are mapped as nodes instead of areas, which makes it difficult to gauge their relative importance. Rendering labels relative to these features' size and extent in Americana would incentivize mappers to convert more of them to areas (like I did with the Ungava Peninusla).


How can I get mentions that are not part of a cluster but still have high unary scores?

Hi @kentonl ,
Apart from the coreference clusters, I also want to extract mention spans that are not present in any cluster (i.e. singletons) but had high unary scores. How can I do this?
Does the kernel you wrote (coref_kernels.so) only extract the spans with high unary scores?
Thanks,

Yes, that kernel only outputs spans with high unary scores, but you shouldn't need to touch that at all.
Without changing any modeling code, the spans with high unary scores (specified by this cutoff: https://github.com/kentonl/e2e-coref/blob/master/experiments.conf#L29) should be available to you via top_span_starts and top_span_ends at https://github.com/kentonl/e2e-coref/blob/master/predict.py#L32.


Suggestion navigation is broken when selectionMode = never and there is only one suggestion in the list

Type: Bug
Open new document. Set editor.suggest.selectionMode = never. Type test  now start typing tes the editor will show suggestion (with only one test in the list). Now pressing down arrow should select the available suggestion, but it can not be done.
On the other hand if you type test test1 and then start typing tes the list will contain two items and selection works as expected - when you press down arrow the first item is selected and you can navigate the list with down arrow and up arrow
VS Code version: Code 1.75.1 (441438abd1ac652551dbe4d408dfcec8a499b8bf, 2023-02-08T21:32:34.589Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
31.70GB (20.47GB free)

Process Argv
--disable-extensions .

Screen Reader
no

VM
0%

Extensions disabled

@jrieken with the setting set to "never" is it expected that there is one selected by default? I didn't have to arrow down for this to happen 🤔


Flow running multiple times: some of these flows are time consuming and expensive. Probably need to double check if the statements are written in the correct order.

https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#activate-the-flows

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

ID: 9fe69498-a485-5379-97ff-53fbe029f11a
Version Independent ID: 5b3f9705-9e49-1575-4ae7-0293d12b739c
Content: Set up core components - Power Platform
Content Source: power-platform/guidance/coe/setup-core-components.md
Service: power-platform
Sub-service: guidance
GitHub Login: @manuelap-msft
Microsoft Alias: mapichle

Please raise any issues related to the CoE Starter Kit functionality itself here: https://github.com/microsoft/coe-starter-kit/issues/new?assignees=Jenefer-Monroe&labels=coe-starter-kit&template=coe-starter-kit-bug.yaml&title=[CoE+Starter+Kit+-+BUG]+your+issue
The issues here are just for documentation.


transparent-hugepage - correct exit status when file is missing

The previous patch resolves trying to write to file if not there, however, the ls (check) throws exit 2.  This version will correctly return exit 0 if file does not exist,,, and still properly handle it when the file does exist.
the transparent-hugepage file does not exist on AWS Ubuntu precise and trusty images.

Looks good. Thanks for the submission!


Manually roll engine to unred the tree

Devicelab is currently red because of the mDNS issue.  This rolls us to the fix for that in the engine.
flutter/engine@0a8bd9dd6 Fix mDNS for iOS13 (flutter/engine#13451)
flutter/engine@d8d5e43e0 [fuchsia] [packaging] Fuchsia tree expects nested bz2 archives (flutter/engine#13482)
flutter/engine@1af0e585b Disabled GPUThreadMerger tests. (flutter/engine#13480)
flutter/engine@21c049e20 Print the output (flutter/engine#13479)
flutter/engine@a5243c024 use check_output instead of check_call so that exceptions show the output. (flutter/engine#13478)
flutter/engine@1eb15c12f Revert 78a8ca0f62b04fa49030ecdd2d91726c0639401f (flutter/engine#13467)
flutter/engine@8997f3481 Fix stale platform view gr context on iOS (flutter/engine#13469)
flutter/engine@55e8ef901 [fuchsia] Bundle unstripped SO files in fars (flutter/engine#13466)
flutter/engine@c604fd439 Pass the automaticallyRegisterPlugins flag to the FlutterEngine constructor in FlutterActivityTest (flutter/engine#13468)
flutter/engine@fb4366e52 [web] Get the size from visualviewport instead of window.innerHeight/innerW… (flutter/engine#13462)
flutter/engine@c882439cb Automatically register plugins in FlutterEngine. (flutter/engine#43855) (flutter/engine#13455)
flutter/engine@d33b91837 Reland "fix fml_unittes is not run during presubmit (flutter/engine#13395)" (flutter/engine#13426)

This will have to land on red - @jonahwilliams @zanderso

We updated the devicelab to use devices compatible without this change, so doesn't have to be landed on red anymore.  Will keep it open anyway since it's almost through tests.


A.01.validate

This issue has been extracted from the issue list on:https://ies-svn.jrc.ec.europa.eu/issues/2685
Comment
The ATS requires validation against three different XSD schema versions (at least one should pass). It is not clear how to determine which schema to use to validate the document.
Proposed Change
The ATS should perhaps clarify that this is on the basis of the declared namespaces in the XML document (see also issue 10 on GitHub), i.e.:
If the document declares http://www.isotc211.org/2005/srv, use http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd.
But otherwise, it is unclear what to use. The official schema for http://www.isotc211.org/2005/gmd is http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd or http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd, but in the context of Discovery services, INSPIRE also uses http://schemas.opengis.net/iso/19139/20060504/gmd/gmd.xsd. It is unclear how to select the schema document. Which schema document does the MD TG require?

see also this issue https://github.com/inspire-eu-validation/ats-metadata/issues/1
maybe @AntoRot can advise?

It's a hard issue :)
IMO, the reference version of GML to be considered should be only 3.2.1 that is the only defined in a published ISO Standard and not in a draft (see  also #31).
If so, the schema required should be only http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/gmd/gmd.xsd or http://schemas.opengis.net/iso/19139/20070417/gmd/gmd.xsd, that are only valid for datasets and dataset series.
But as far as the services are concerned, the matter is not solved in this way.
In Italy, since the version of GML mentioned above is required, we locally referenced the official ISO TS 19139 schema adding the srv namespace. We also suggested to not include any schemaLocation in the xml header (that only for services metadata).
So, a possible solution could be that proposed by Peter Parslow in #95, i.e. JRC could host a local repository of the schema for services metadata in order to take into account only the ISO TS 19139 and the official version of GML and have a valid URL for the schemaLocation.

OK but what about http://schemas.opengis.net/csw/2.0.2/profiles/apiso/1.0.0/apiso.xsd ?

Since che apiso.xsd schema imports the 2006 version of gmd.xsd and srv.xsd, also this issue is unsolved yet. Really for a long time, as we know: see the still pending change request to OGC here https://portal.opengeospatial.org/files/?artifact_id=37400 or the post http://lab.usgin.org/groups/csw-debug-blog/ogc-schema-issues-relation-csw.
In the last part of the mentioned post, a possible solution is suggested by the editor of the CSW ISO AP (i.e. validating the frame (e.g. GetRecordsResponse) and the content (ISO19139) separately).
But IMO, the best (abstract?) proposal could be the following:
OGC itself could host the repository for services metadata (instead of JRC, as proposed in the previous comment) and so the apiso.xsd schema could refer to it and to the last version of gmd.xsd.
To achieve this result, I think that the role of JRC could be very important.
Alternatively, JRC could do that to be used across INSPIRE.
I see no other way to solve the issue.

There are practical solutions for the schemas issues and I do not see a real benefit of having unofficial versions of the schemas available online as I do not think they can be endorsed by any other organisations other than those which own them.
For example, I cannot find any more online the eden schemas published by IGN.
I think the core issue is the one about ISO AP 1.0 referencing the 2006 version.
I also see no big value in validating a whole GetRecordsEnvelope or, similarly, a whole feature collection.


@conda-forge-admin, please add bot automerge

[ ] I read the conda-forge documentation and could not find the solution for my problem there.

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/nsls2-detector-handlers-feedstock#2.


Fixing the specs

This PR fixes the specs by addressing the markdownlint warnings (although this didn't work completely) and updating to the latest version of Katex (which did almost completely, solving the breaking in And section), and then substituting $ for \wedge (which made all of LaTeX magically compile again).

Basically this
https://katex.org/docs/error.html


Problems related to implicit/explicit access to Context

Currently, there are two way to access the reference to Context during hadling or polling the task as follows:
fn handle(cx: &Context) -> impl Future<Item = Output, Error = Error>  {
    // 1. explicit access using a borrow passed as an argument of the handler function.
    //    This reference cannot be used inside of the future which will be returned at the end of handler.
    let some_future = some_function(cx.global().state::<SomeValue>());

    some_future.and_then(|value| {
        // 2. implicit access via (scoped) thread local storage.
        Context::with(|cx| { ... })
    })
}

There are the following problems in such system:

Implicit access via thread local storages cannot track the lifetime of the instance of Context.  Some errors due to using the reference to Context at the outside of its lifetime will cause as runtime errors.

At async/await syntax in the RFC, the lifetime of returned anonymous type is shorter than the all lifetimes in the arguments.  This means that the following lifetime bounds will added:
async fn handler<'a>(cx: &'a Context) -> Result<Output, Error> { ... }
// ... will be expanded to
fn handler<'a>(cx: &'a Context) -> impl Future<Output = Result<Output,Error>> + 'a { ... }

Since the future returned by the handlers needs to be managed for longer than 'a, such a lifetime bound should not be added.

The way for accessing to Context seems to be required, without using the scoped TLSs.

Candidate 1: Moves the ownership of Context to the handler.

Pros:

Probably resolves the above problems
Workarounds for accessing the value of Context (like TLS) becomes unnecessary

Cons: The handler is responsible for returning the instance of Context:fn handler(cx: Context) -> impl Future<Output = (Result<Output, Error>, Context)> + 'static { ... }
// or
async fn handler(cx: Context) -> (Result<Output, Error>, Context) { ... }

This case is worse affinity with existing syntax (like ?) and not ergonomic.

Candidate 2: Always uses the implicit access.
fn handler() -> impl Future<Output = Result<Output, Error>> + 'static { ... }
// or
fn handler() -> Result<Output, Error> { ... }

Pros: The problems around lifetime bounds caused by async/await! syntax will be resolved
Cons: The problems of tracking lifetimes by using scoped TLS will still remain

Currently, Tsukuyomi uses an abstraction of asynchronous computation by using a trait Future which emulates the definition of Future in the standard library. I'll extend the signature of this trait to receive a contextual information during polling Futures (it is analogous to the updates at futures2).
trait Future {
    type Output;

    fn poll(&mut self, cx: &mut future::Context) -> Poll<Self::Output>;
}

where future::Context is a struct for holding the contextual information during polling the value of Future, corresponding to task::Context in the standard task system. The definition of future::Context is effectively a wrapper of task::Context:
struct Context<'a> {
    input: &'a mut Input,
    ...
    task: &'a mut task::Context,
}

Since the value of Context can only be accessed via Future::poll, the process to parse the incoming request or to retrive from global state need to be implemented as a Future.
async fn handler() -> Result<String, Error> {
    let query = await!(parse_request())?;
}

fn parse_request() -> impl Future<Output = Result<Query, Error>> + 'static { ... }

The current iteration (0.2) uses the implicit access via (modified) scoped-TLS.


Refactor specSyntax

The use of before/after each deltas is confusing.

This is slightly better after some refactoring. Would like a new implementation.


fix: remove tokio_unstable

Removes tokio_unstable Builder, turns the thread name into a tracing span, still enforces using fedimint_core's spawn and spawn_local.

Successfully created backport PR for releases/v0.3:

#5213


Building a menu item never returns true if the menu item is active.

I'm attempting to open a modal when my menu item is clicked on, however build never seems to return true. I've tested the modal works by using a regular button. Perhaps I'm just missing something?
Code:
let is_clicked = imgui::MenuItem::new(im_str!("New"))
  .shortcut(im_str!("Ctrl + N"))
  .build(ui);
if is_clicked {
  ui.open_popup(im_str!("Create"));
}

Seems like it's my mistake.


Error on run

Hi!
I'm getting an error message while running the CMAKE action.
It was working fine before.
Download action repository 'lukka/run-cmake@v0'
##[error](Line: 34, Col: 14):
##[error](Line: 34, Col: 14): Unrecognized named-value: 'env'. Located at position 1 within expression: env.RUNVCPKG_VCPKG_TRIPLET
##[error]Fail to load /home/runner/work/_actions/lukka/run-cmake/v0/action.yml
Edit: was pointing out to a private repository, removed.

Fixed. Was using an outdated version.
Changing to @v2 worked out!


[#4558] Add mapper for JvmGcType & ThreadState

#4558

Codecov Report

Merging #5625 into master will decrease coverage by 0.04%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5625      +/-   ##
==========================================
- Coverage   40.44%   40.39%   -0.05%
==========================================
  Files        2870     2874       +4
  Lines       86602    86649      +47
  Branches    11453    11452       -1
==========================================
- Hits        35022    35002      -20
- Misses      48542    48606      +64
- Partials     3038     3041       +3

Impacted Files
Coverage Δ

...ctor/mapper/thrift/stat/ThriftJvmGcTypeMapper.java
0% <0%> (ø)

...r/mapper/grpc/event/GrpcAgentEventBatchMapper.java
0% <0%> (ø)
:arrow_up:

...r/mapper/thrift/event/ThriftThreadStateMapper.java
0% <0%> (ø)

.../mapper/thrift/event/ThriftThreadDumpBoMapper.java
0% <0%> (ø)
:arrow_up:

...int/collector/mapper/grpc/GrpcJvmInfoBoMapper.java
0% <0%> (ø)
:arrow_up:

...ector/mapper/grpc/event/GrpcThreadStateMapper.java
0% <0%> (ø)

...lector/mapper/grpc/event/GrpcAgentEventMapper.java
0% <0%> (ø)
:arrow_up:

.../collector/mapper/grpc/stat/GrpcJvmGcBoMapper.java
0% <0%> (ø)
:arrow_up:

...collector/mapper/thrift/ThriftJvmInfoBoMapper.java
0% <0%> (ø)
:arrow_up:

...lector/mapper/thrift/stat/ThriftJvmGcBoMapper.java
0% <0%> (ø)
:arrow_up:

... and 18 more

Continue to review full report at Codecov.

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


Roadmap in separate markdown file, linked to from Readme

Previously discussed in https://github.com/spatialos/UnityGDK/pull/12

(1) IMHO, it's better in its own doc.
(2) It needs a title at this level #.
(3) It would be better in the docs directory rather than a top-level directory.
(4) 'First look' doesn't tie in with the words 'pre-alpha' so we need to say when 'first look' is available from and what date this roadmap applies from (because it will change).