Clarify ARL Form 1 process

The Major Review process includes "File an ARL Form 1". Instructions for filing the ARL form 1 include:

This information will be used both for publicity purposes, and by a supervisor and others to decide if it is time for a project to be subjected to another major review.

This is confusing because supervisors, in the process of a major review, will decide if a major review process is necessary.
Please clarify the intent of this passage.

The issue is that the developers can decide on their own that they want a major review as this may boost their performance ratings.  The supervisor can take a look at what they write and decide that they haven't really produced anything worth the effort of another major review, and so kills the major review.  Any thoughts on how to express that?

The main vulnerability is in this sentence:

In the process described in this document, the primary purpose of the ARL Form 1 is for OPSEC review, but it also serves the secondary purposes of describing releases for publicity and metrics.

So that means developers are incentivised to pollute the major review pipeline with unnecessary changes to things which affect OPSEC (e.g. switch from SHA-192 to SHA-256 for something that does not matter.)

But, the ARL Software Release Process may already have the antidote:

The major review process MUST be followed if any of the following are true:
...
It has been more than 1 year since the last time a major review has been done and the project is still active (material is being published to the public).

If ARL performs performance reviews only annually then gaming the system (unnecessary major reviews) would not be necessary since you already get a review once a year.
Maybe at the end of the year there will be a pile to do. But since

Publishing software as a regular business practice is new territory for ARL, and how to measure a project's impact on the general public is still a matter for debate.

we can probably cross that bridge when we come to it.

Recommendation
Change:

This information will be used both for publicity purposes, and by a supervisor and others to decide if it is time for a project to be subjected to another major review.

to:

A supervisor will use the filed ARL Form 1 to decide if the major review process is necessary or if, instead, the minor review process will be followed.

OK, I see your concerns now.  I'm not concerned because of how the incentives are structured; a developer only gets credit for the work they've generated since the last major review and its impact since the last major review.  So if developer makes a meaningless change and tries to do another major review, their metrics won't improve at all for the second review.
That said, there is a constant (and moderately high) cost to performing a major review in the amount of time it takes.  So my expectation is that while they can attempt to game the system, it will cost more than it will gain.  Especially as the supervisors catch on, get annoyed, and start giving them less and less credit for poor work.
As for the wording, I can see your point about clarity.  I do want to inform people that it can be used for publicity purposes as well as for evaluation purposes though; any thoughts on how to state all that clearly?

Who uses it for publicity purposes? I would put it like this:

A supervisor will use the filed ARL Form 1 to decide if the major review process is necessary or if, instead, the minor review process will be followed. Also, [THE PUBLICITY OFFICER] may use information from the ARL Form 1 for publicity purposes.

I like it!  The official name for [THE PUBLICITY OFFICER] at ARL is The Public Affairs Office (PAO).
Do you want to do a pull request (so you get credit), or do you want me to add it in directly?  You know my preference is that you get credit for your work, but it's up to you...

PR coming.

Just merged it in, I'm going to close this issue.


Bumping Teku Version for Gnosis Capella fork

Bumps Teku version to 23.6.2 to pull in changes related to Gnosis capella fork. This fork is scheduled to take place within 24 hours at epoch 648704 (current epoch).
Discord context.
Gnosis operators will need to add --Xnetwork-capella-fork-epoch=648704 - if we support this via Teku or from Mainnet capella that is fine, we just need to let Gnosis Chain users know or if they will need any additional tweaking.

Added additional config in the end-to-end network config used in our ATs required by changes Teku libs


Invalid gpio pin specified

I am using Arrow DragonBoard 410c to handle some interrupts on the GPIO pins. However, as I try to execute the example python script it says "Invalid GPIO pin Specified". I have tried changing the gpio pin to other number like 25, 26, 30 but nothing works. Where can I get the GPIO mapping for dragonboard 410c?
Also, I was unable to install nodejs-dev in my board due to presence of libnode-dev. I presumed that it will be necessary only if I use nodejs scripts and should not matter otherwise. Can that be the reason for this issue?

You don't show what examples you are running or how you have installed mraa so it is difficult for people to debug what your issue is. As some general instructions:
GPIOs are labelled "GPIO-A" through "GPIO-L" on the DragonBoard 410c
You can look up what the pin number using mraa. For example:
$ sudo python3
Python 3.5.3 (default, Sep 27 2018, 17:25:39)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import mraa
>>> mraa.getGpioLookup('GPIO-I')
31

An example of an interrupt might be:
from signal import pause
import mraa
btn2 = mraa.Gpio(31)
btn2.dir(mraa.DIR_IN)
btn2.edge(mraa.EDGE_FALLING)
btn2.isr(mraa.EDGE_FALLING, print, 'Test on btn2')
pause()

How I build and install mraa for python3:
sudo apt install git build-essential swig3.0 python3-dev cmake

git clone https://github.com/intel-iot-devkit/mraa.git
cd mraa
mkdir build
cd build/
cmake -DBUILDSWIG=ON \
      -DBUILDSWIGPYTHON=ON \
      -DBUILDSWIGNODE=OFF \
      -DBUILDSWIGJAVA=OFF \
      -DCMAKE_INSTALL_PREFIX=/usr \
      ..
make
sudo make install

Hope that helps.

Hi, Thank You for your reply. I had used the general instructions given in the readme for ubuntu. While building the error I was getting was regarding nodejs-dev installation. It said that it already has libnode-dev which is replacing nodejs-dev. I tried removing libnode-dev but wasn't able to.
However, even after all this I tried importing mraa in python and it did not throw an error after which I tried the example code given in examples/python/gpio_advanced.py and it said Invalid gpio pin specified.
I thought that it is related to the nodejs because that is the only thing missing in this but I wasn't sure.
I also tried your said instructions for making but when I pass those config commands in cmake I get the following error:
`-- INFO - NODE_ROOT_DIR is /usr/include/nodejs
CMake Error at /usr/share/cmake-3.13/Modules/FindPackageHandleSt
andardArgs.cmake:137 (message):
Could NOT find Nodejs (missing: NODEJS_INCLUDE_DIRS) (found ve
rsion
"10.15.2")
Call Stack (most recent call first):
/usr/share/cmake-3.13/Modules/FindPackageHandleStandardArgs.cm
ake:378 (_FPHSA_FAILURE_MESSAGE)
cmake/modules/FindNodejs.cmake:95 (find_package_handle_standar
d_args)
src/javascript/CMakeLists.txt:1 (find_package)
-- Configuring incomplete, errors occurred!                     `
As it is visible it is throwing error regarding nodejs which I guess is the root problem here.

And when I tried to follow your code for the list of GPIO pins, I got the following error:

`Python 2.7.16 (default, Apr  6 2019, 01:42:57)
[GCC 8.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more informa
tion.

import mraa
for i in range(ord('A'), ord('L')+1):
...     pin = 'GPIO-{}'.format(chr(i))
...     num = mraa.getGpioLookup(pin)
...     print(pin, num)
...
Traceback (most recent call last):
File "", line 3, in
File "/usr/lib/python2.7/dist-packages/mraa.py", line 469, in g
etGpioLookup
return _mraa.getGpioLookup(pin_name)
ValueError: Gpio name GPIO-A is not valid                        `

Hi,
So I was able to build the mraa into my board and I tried that PinLookup code again but it threw an error saying mraa has no attribute 'getGpioLookup'
What does that mean? I mean apart from the fact that it can't find it in spite of it ben built?
I had also tried the same code on python2.7 and 3.4

What version of the OS are you using?
It might be worth posting a question over on the 96Boards forum for DragonBoard 410c:
https://discuss.96boards.org/c/products/dragonboard410c

Its Debian Buster 10 with kernel version as 4.14.0-qcomlt-arm64

I have no experience of building on that OS and kernel. I am still on:
$ uname -a
Linux linaro-developer 4.9.56-linaro-lt-qcom #1 SMP PREEMPT Mon Oct 16 12:29:10 UTC 2017 aarch64 GNU/Linux

But I am guessing with an updated kernel version the max that would have changed is the linking of the files when they get called. And given that all the supporting files are already installed and built on the machine, it should be possible to reconfigure the link file

And one thing that I couldn't understand is why is it trying to check for linkit board when it is installed on dragonboard? I tried removing that part in the code and it shifted to the next line checking for Omega2 board. It should just stop at 96boards

I have no experience of building on that OS and kernel. I am still on:
$ uname -a
Linux linaro-developer 4.9.56-linaro-lt-qcom #1 SMP PREEMPT Mon Oct 16 12:29:10 UTC 2017 aarch64 GNU/Linux

BTW This is also linaro OS only. Just the kernel version is upgraded


Change label for default location filter

We've received a significant amount of feedback that the "Everywhere" filter is confusing for users. They expect to see all meetings there, not just in-person meetings (which includes hybrid). We've addressed this in our meeting finder FAQ but I think there may also be a (hopefully) small fix with a meaningful UX pay-off: change the label from "Everywhere" to "Any location". This does two things:

It makes it clearer what this filter is for.
It harmonizes the label with that of the other filters.

Small reconciliation with https://github.com/code4recovery/react/issues/77#issuecomment-716935348: I reference the label of "Cities" there; "Locations" is probably better since it's more generic and I assume Intergroups are treating regions/sub-regions differently.
Thoughts?

We've realized that absent a significant redesign of TSML, we need to accept that our users associate online meetings with physical locations. In order to keep our data clean and manageable, we have added an extra field on our Meetings table: TSML_remote_meeting_neighborhood. (We already had a field for TSML_remote_meeting_county so that the approximate location for online meetings required by Meeting Guide would reflect the county where the meeting started since a lot of folks from Marin meetings were frustrated that it showed "San Francisco".)
region and subregion are populated in the following order:

if the meeting is attached to a physical location (in Airtable terms: a record on the Meetings table is attached to a record on the Locations table), region and subregion will inherit the city and neighborhood (in the case of San Francisco) or "Marin" and the city (if the location is not in SF).
if the meeting is not attached to a physical location, it then is populated by TSML_remote_meeting_county and TSML_remote_meeting_neighborhood, both of which are fields on the Meetings table.
if we lack either, it will not be counted in the location dropdown — this only applies to meetings which started post-COVID and have always been exclusively online.

This is better than our original solve which was to have a "Remote" region. This didn't work well primarily because hybrid meetings could only be in the Remote, SF, or Marin region (which was a very confusing UX).
I still think changing the label to "Anywhere" is a small improvement to harmonize the labels (all the rest start with "Any") but regardless the dropdown is now functioning the way folks expect it too.

Hey @leggomyinfo - this can be configured during initialization to be any string you'd like:
https://github.com/code4recovery/react/blob/master/src/i18n/en.js#L34
var tsml_react_config = {
  strings: {
    en: {
      region_any: 'Any Location'
    },
  },
};

I think I'd prefer Any Location as well, but is setting this in the configuration good enough?

seeing as i'm making changes today, i went with "Anywhere" -- it seems like a better fit since a) it's shorter and b) Location is used elsewhere to mean a meeting location, rather than a regional geographic area.


cmd/go: go buildid actionID part is not reproducible with clean cache

What version of Go are you using (go version)?

$ go version
go version go1.20.3 linux/amd64

Does this issue reproduce with the latest release?
Yes, but it looks like it's a regression from go1.19.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/smira/.cache/go-build"
GOENV="/home/smira/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/smira/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/smira/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/smira/sdk/go1.20.3"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/smira/sdk/go1.20.3/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.20.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/smira/Documents/talos/go.mod"
GOWORK="/home/smira/Documents/talos/go.work"
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1337074187=/tmp/go-build -gno-record-gcc-switches"

What did you do?
$ git clone https://github.com/siderolabs/talos.git
$ cd talos/internal/app/init
$ go build -o /tmp/init1
$ go clean -cache
$ go build -o /tmp/init2
$ go tool buildid /tmp/init1
sKFzCzkNqNstkxeVQjx6/ur3V8IjUjAaSiSK8FRyf/GkeyU-h8TOuClgbmrAfr/wuYOkIb0eDRiRJoM6Gof
$ go tool buildid /tmp/init2
TzIKQctZITh9Dzu1A0R2/3Z-ERPrw_PhIW3bIu8R2/GkeyU-h8TOuClgbmrAfr/wuYOkIb0eDRiRJoM6Gof

What did you expect to see?
The buildid stays the same.
What did you see instead?
The buildid changes every time I run a build with a clean cache.
The contentID part stays the same, but actionID is always different.
I can't reproduce it with other Go programs, but Talos source code exhibits this issue.
If I repeat the same steps e.g. with go1.19.4, the buildid stays the same.
I noticed this issue initially with our Dockerized build environment, but I reduced it down to a single binary.
If inspected with diffoscope, the only actual difference in the binary is the buildid itself:
├── readelf --wide --notes {}
│ @@ -1,4 +1,4 @@
│
│  Displaying notes found in: .note.go.buildid
│    Owner                Data size 	Description
│ -  Go                   0x00000053	GO BUILDID	   description data: 73 4b 46 7a 43 7a 6b 4e 71 4e 73 74 6b 78 65 56 51 6a 78 36 2f 75 72 33 56 38 49 6a 55 6a 41 61 53 69 53 4b 38 46 52 79 66 2f 47 6b 65 79 55 2d 68 38 54 4f 75 43 6c 67 62 6d 72 41 66 72 2f 77 75 59 4f 6b 49 62 30 65 44 52 69 52 4a 6f 4d 36 47 6f 66
│ +  Go                   0x00000053	GO BUILDID	   description data: 54 7a 49 4b 51 63 74 5a 49 54 68 39 44 7a 75 31 41 30 52 32 2f 33 5a 2d 45 52 50 72 77 5f 50 68 49 57 33 62 49 75 38 52 32 2f 47 6b 65 79 55 2d 68 38 54 4f 75 43 6c 67 62 6d 72 41 66 72 2f 77 75 59 4f 6b 49 62 30 65 44 52 69 52 4a 6f 4d 36 47 6f 66
├── strings --all --bytes=8 {}
│ @@ -1,8 +1,8 @@
│ -sKFzCzkNqNstkxeVQjx6/ur3V8IjUjAaSiSK8FRyf/GkeyU-h8TOuClgbmrAfr/wuYOkIb0eDRiRJoM6Gof
│ +TzIKQctZITh9Dzu1A0R2/3Z-ERPrw_PhIW3bIu8R2/GkeyU-h8TOuClgbmrAfr/wuYOkIb0eDRiRJoM6Gof
│  /lib64/ld-linux-x86-64.so.2
│  []A\A]A^A_
│  [A\A]A^]
│  []A\A]A^A_
│  SUATAUAVAWH
│  A_A^A]A\][

A few more notes:

Not cleaning the cache between the rebuilds produces identical buildid.
Adding  -ldflags "buildid=" provides reproducible buildid.

Could be #59571, perhaps?
Or, since you are building with CGO_ENABLED, perhaps your C toolchain does not support reproducible builds (compare #56896). What C compiler are you using?

Could be #59571, perhaps?

yes, we do use generics, but go1.19 doesn't show this behavior.
What is the best way for me to check for this? I'm not sure how can I easily see what goes into actionID so I can diff between the builds.

Or, since you are building with CGO_ENABLED, perhaps your C toolchain does not support reproducible builds (compare #56896). What C compiler are you using?

For this case I was building on latest Ubuntu, so pretty much gcc which ships with it.
But I tried with CGO_ENABLED=0 as well, and it behaves same way. The issue started for me in our hermetic build environment which is completely reproducible, but I reduced it back to regular go build invocation.

This is almost certainly #59571. Go 1.19 didn't have the bug. Go 1.20 does. The easiest thing to do is wait for #59571 to be fixed and then see if you still have the problem.

@rcs thank you, verfied with gotip, the problem is fixed.
We'll be waiting for go1.20.4!


Support for conda python build pack ?

Is there a support for conda version of python build pack ?
https://github.com/paketo-buildpacks/miniconda

Conda is not supported today. Please share your use case so we understand how that'd help you.

@gitricko interesting. Can you tell me a bit more about where those apps will be deployed? will they be deployed onto a k8s cluster? cloud run? cloud functions? some other destination?
If you're just looking for a straightforward way to containerize without writing Dockerfiles, you could definitely use the Paketo buildpacks to build your projects and then deploy those images on to a GCP service.
With the GCP buildpacks project, we're really honing in on the quality of our existing buildpacks and shipping reliable updates to our new builders (see https://github.com/GoogleCloudPlatform/buildpacks/discussions/271). Unfortunately, this means we don't have as much headroom to take on in new buildpacks.
We are, however, looking at ways where folks can utilize Paketo/Heroku/other community buildpacks on-top of our base images. We're still in the early stages of investigating that work, but hoping we can share more details on that soon

@gitricko interesting. Can you tell me a bit more about where those apps will be deployed? will they be deployed onto a k8s cluster? cloud run? cloud functions? some other destination?
If you're just looking for a straightforward way to containerize without writing Dockerfiles, you could definitely use the Paketo buildpacks to build your projects and then deploy those images on to a GCP service.
With the GCP buildpacks project, we're really honing in on the quality of our existing buildpacks and shipping reliable updates to our new builders (see #271). Unfortunately, this means we don't have as much headroom to take on in new buildpacks.
We are, however, looking at ways where folks can utilize Paketo/Heroku/other community buildpacks on-top of our base images. We're still in the early stages of investigating that work, but hoping we can share more details on that soon

We are looking into evaluating Kf and one of the interesting google has build is that your buildpack has the least vulnerabilities as compared to paketo.

We are looking into evaluating Kf and one of the interesting google has build is that your buildpack has the least vulnerabilities as compared to paketo.

Glad to know our recent security work is paying off ;)
Would you be looking for the equivalent of something like the Paketo miniconda buildpack? We're not currently looking to build additional buildpacks, but we are exploring options on how we might be able to let users inject community buildpacks in addition to the GCP builders. Would your organization be open to mixing-and-matching buildpacks? We would not be able to provide technical support on the miniconda buildpacks

Would you be looking for the equivalent of something like the Paketo miniconda buildpack? We're not currently looking to build additional buildpacks, but we are exploring options on how we might be able to let users inject community buildpacks in addition to the GCP builders. Would your organization be open to mixing-and-matching buildpacks? We would not be able to provide technical support on the miniconda buildpacks

What do you mean by mixing and matching buildpacks ? We just need miniconda and no support really is needed - it is just miniconda.

I would love to see the support for conda packages as well because libraries like geopandas are very difficult to install with only pip, they require additional system dependencies.


Remove volatile flag

The volatile flag of Variable has been used for saving the cost of constructing a graph when backprop is not needed. This approach is enough when a user who configures the volatility can access to all the input of the forward computation, but it cannot be used otherwise. We need a different approach with which we can disable the graph construction without modifying all the forward computation itself.
The no_backprop_mode is recently added, and can be used as above if all input variables have volatile=AUTO. Based on my experiences, this is enough for any use cases of volatile mode and is much easier to use. This proposal is to remove the volatility flag and make Variable behave like the current volatile=AUTO mode by default, whose graph construction behavior can be configured by a thread-local flag (like the current no_backprop_mode).

I tried to remove volatile flag from variable and to use config.enable_backprop instead. But i feel we cannot detect mixed volatility with this method. How do you think about this problme?
with chainer.no_backprop_mode():
    x = func()
y = x + 1

IMO, any computations done with backprop mode enabled should build a computational graph. So, in the above case, func does not build a graph, but y = x+1 builds. I think there will be less chance of messing up two opposite attempts, "I want to backprop this part" and "I only want to do inference of this part", if we do not use volatile flag.

Therefore, I think we do not need to store _volatile anymore. I might be missing some important case, so let me know if you find one.

If I would like to fine-tune part of a network, I need to set the volatile attribute of the input variable to off and on after the frozen part. How would that be possible if volatile flag were to be removed?

Execute the frozen part in the no-backprop mode, and run the rest in the usual mode. For example, the following code for v1
x.volatile = 'on'
h = frozen_part(x)
h.volatile = 'off'
y = finetune_part(h)

is written in v2 as
with chainer.no_backprop_mode():
    h = frozen_part(x)
y = finetune_part(h)

or equivalently
chainer.config['enable_backprop'] = False
try:
    h = frozen_part(x)
finally:
    chainer.config['enable_backprop'] = True
y = finetune_part(h)

Thanks, the new version is definitely clearer.
On Mar 29, 2017 11:07, "Seiya Tokui"<EMAIL_ADDRESS>wrote:
Execute the frozen part in the no-backprop mode, and run the rest in the
usual mode. For example, the following code for v1
x.volatile = 'on'
h = frozen_part(x)
h.volatile = 'off'
y = finetune_part(h)
is written in v2 as
with chainer.no_backprop_mode():
h = frozen_part(x)
y = finetune_part(h)
or equivalently
chainer.config['enable_backprop'] = Falsetry:
h = frozen_part(x)finally:
chainer.config['enable_backprop'] = True
y = finetune_part(h)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pfnet/chainer/issues/2013#issuecomment-289960125, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABJTn0alscpXqPfni6GVn4js_9lSdHloks5rqbzFgaJpZM4LOyYe
.

Fixed via #2356


the console example SioCharDemo.exe crashes in the code " sio::client h;"

I just complied the SioCharDemo.exe in my pc and it is running good, but if run it in another pc (i don't know if it is influenced by the OS version or bits, the compiling pc is win10 64bit the running pc is win7 64bit ),the SioCharDemo.exe is crashed on exit. Has anyone meet the same problem?

Hi... I am facing a similar kind of a problem. The destructor of sio::client calls sync_close and I get a segmentation fault. I don't know what am I missing. This is random though. Sometimes it crashes and sometimes not. I suspect the boost::thread to be the culprit


<EMAIL_ADDRESS>do not work on deno runtime?

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
I try to import openai on my netlify edge function, it works well days ago, but today it raises:
error: Uncaught (in promise) Error: Module not found<EMAIL_ADDRESS>       const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
       at __wbg_new_15d3966e9981a196 (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm.generated.js:417:19)
       at <anonymous> (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm_bg.wasm:1:93412)
            at <anonymous> (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm_bg.wasm:1:1499594)
            at <anonymous> (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm_bg.wasm:1:1938165)
            at __wbg_adapter_40 (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm.generated.js:231:6)
       at real (file:///opt/buildhome/node-deps/node_modules/@netlify/edge-bundler/deno/vendor/deno.land/x/eszip@v0.40.0/eszip_wasm.generated.js:215:14)
       at eventLoopTick (ext:core/01_core.js:183:11)

Note that I found /denonext/resources.js missing from esm.sh. I don't know if this is related.
To Reproduce
new a netlify edge function with just
import OpenAI from "https://esm.sh/openai"

and deploys it
Code snippets
No response
OS
Windows
Node version
deno
Library version
openai v4.12

Thanks for the report, we'll take a look.
On Sat, Oct 21 2023 at 1:35 AM, Muspi Merol @.***>
wrote:

Confirm this is a Node library issue and not an underlying OpenAI API issue

This is an issue with the Node library

Describe the bug
I try to import openai on my netlify edge function, it works well days
ago, but today it raises:
error: Uncaught (in promise) Error: Module not found @./denonext/resources.js".
const ret = new Error(getStringFromWasm0(arg0, arg1));
^
at __wbg_new_15d3966e9981a196 @.@./eszip_wasm.generated.js:417:19)
at  @.@./eszip_wasm_bg.wasm:1:93412)
at  @.@./eszip_wasm_bg.wasm:1:1499594)
at  @.@./eszip_wasm_bg.wasm:1:1938165)
at __wbg_adapter_40 @.@./eszip_wasm.generated.js:231:6)
at real @.@.***/eszip_wasm.generated.js:215:14)
at eventLoopTick (ext:core/01_core.js:183:11)
Note that I found /denonext/resources.js missing from esm.sh. I don't
know if this is related.
To Reproduce
new a netlify edge function with just
import OpenAI from "https://esm.sh/openai"
and deploys it
Code snippets
No response
OS
Windows
Node version
deno
Library version
openai v4.12
—
Reply to this email directly, view it on GitHub
https://github.com/openai/openai-node/issues/393, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFL6LQBL6VORHMSMULDYFDYANNILAVCNFSM6AAAAAA6J45C5KVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2TKMZTGQYDENQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sorry about this, we're reenabling deno support now and should have it released within a few days.

Hey, sorry about this. Can you try import OpenAI from 'npm:openai@4'?
Even import OpenAI from<EMAIL_ADDRESS>seems to work for me on a Deno Deploy playground, so perhaps it was just a caching issue or something?

@rattrayalex I tried your example of import OpenAI from<EMAIL_ADDRESS>and I'm also getting the same problem. Also, your link to the Deno playground is a 404. I am not using an import map. Deno version 1.37.2.
Supabase CLI 1.106.1
Version 1.30.3 is already installed
Bundling scene-description-to-image-prompt
Error bundling function: exit status 1
file:///Users/tf/Projects/ds/supabase/functions/import_map.json
file:///Users/tf/Projects/ds/supabase/functions/scene-description-to-image-prompt/index.ts
error: Uncaught (in promise) Error: Module not found<EMAIL_ADDRESS>      const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
    at __wbg_new_8d2af00bc1e329ee (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:513:19)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1559899)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1398157)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1895031)
    at __wbg_adapter_40 (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:229:6)
    at real (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:213:14)

Importing an older version works fine:
import OpenAI from<EMAIL_ADDRESS>

Thanks for writing in @fi5u . Sorry for the 404; here's a public playground: https://dash.deno.com/playground/fair-goose-52
Given this code:
import OpenAI from 'npm:openai@4'
import {VERSION} from 'npm:openai@4/version'
import {VERSION as v413} from<EMAIL_ADDRESS>
const client = new OpenAI({apiKey: 'TODO'})

Deno.serve((req: Request) => new Response(`OpenAI Version ${VERSION}, can also import ${v413}`));

I see this result:
OpenAI Version 4.14.0, can also import 4.13.0

Can you try an equivalent in Supabase and share the result? I'm not familiar with their offering and how it might be different from vanilla Deno Deploy (or how to get started with a function on their platform).

@rattrayalex Thanks for the response. When trying your example with Supabase, as before, it fails to bundle (output below). I'm new to both Supabase and Deno so I'm not sure what's happening here. I'm ok sticking with the working v.4.11 until this is fixed.
Version 1.30.3 is already installed
Bundling scene-description-to-image-prompt
Error bundling function: exit status 1
file:///Users/tf/Projects/ds/supabase/functions/import_map.json
file:///Users/tf/Projects/ds/supabase/functions/scene-description-to-image-prompt/index.ts
error: Uncaught (in promise) Error: Module not found "npm:openai@4".
      const ret = new Error(getStringFromWasm0(arg0, arg1));
                  ^
    at __wbg_new_8d2af00bc1e329ee (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:513:19)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1559899)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1398157)
    at <anonymous> (https://deno.land/x/eszip@v0.35.0/eszip_wasm_bg.wasm:1:1895031)
    at __wbg_adapter_40 (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:229:6)
    at real (https://deno.land/x/eszip@v0.35.0/eszip_wasm.generated.js:213:14)

I tried serving the Supabase Edge Function locally. This uses Supabase edge-runtime. I'm using edge_runtime version 1.22.3 which has Deno version 1.37.1. Still running into the same error.

Thank you very much @aar2dee2 and @fi5u for the detailed reports. I've passed this along to the folks at Deno.
@fi5u out of curiosity, the import that's working for you is this, correct?
import OpenAI from<EMAIL_ADDRESS>

@rattrayalex My working import looks like this:
import OpenAI from<EMAIL_ADDRESS>

@rattrayalex My working import looks like this:
import OpenAI from<EMAIL_ADDRESS>

This is working for me too! Thanks @fi5u

We've released v4.15.3 to deno.land/x/, which you can use like so:
import OpenAI from<EMAIL_ADDRESS>
We're working to also publish 4.16.0, which contains the changes from DevDay's announcements, shortly.

We've released v4.15.3 to deno.land/x/, which you can use like so:
import OpenAI from<EMAIL_ADDRESS>

This works in Supabase Edge Functions. Thanks a ton!

Thank you for confirming!
We've now also published v4.16.1 which includes today's api releases.
Going forward, we'll be publishing to demo.land/x/openapi

Wanted to see if anyone else was able to get the latest deno openai 4.16.1 version working on a supabase edge function. When trying to stream chunks, I consistently seem to only get 1 part back that looks like this:
{
  id: "chatcmpl-8IPirfnuikMfsLCSj3uxhXPmqeU7k",
  object: "chat.completion.chunk",
  created:<PHONE_NUMBER>,
  model: "gpt-4-0613",
  choices: [
    {
      index: 0,
      delta: { role: "assistant", content: "" },
      finish_reason: null
    }
  ]

but then nothing else.
Streaming was working okay when using<EMAIL_ADDRESS>

@joshling1919 can you open that as a separate issue, and share the code you're using to make the request?

@rattrayalex @fi5u Fun fact that's not published anywhere on the internet, Supabase's server-side for edge functions isn't running a version of Deno that supports npm: flagging.  Gotta use esm.sh or similar, which is a problem when it doesn't play nice as with this issue.  The only real hint for this is that they tell you to use esm.sh to import supabase-js in one of the edge function tutorials.
No point in going to Deno, their stuff is all working.  Supabase just won't update their edge function configuration to support npm packages for some reason.  Thanks for creating a dedicated Deno build, that's the only thing that's been reliable for me so far.

Great news, esm.sh has fixed their bug and this package can now be imported via esm.sh in Deno like so:
import OpenAI from "https://esm.sh/openai";

https://www.val.town/v/rattrayalex/VERSION

also added a testing ensure this package wouldn't break in future updates

import OpenAI from "https://esm.sh/openai";

this works with Supabase Edge Functions! 🚀


Box zoom causes popups to not respond to click events

Zooming in on a map using the box zoom (shift + drag) causes popups to not respond to click events.  There is a JSFiddle that demonstrates this issue at the following link.
http://jsfiddle.net/3LLtqLsq/2/

Open the JSFiddle link
Click on some of the objects that have been added to the map, notice popups work for these objects.
Zoom into the map using box zoom (shift + drag)
Click the objects on the map, popups are no longer displayed

The issue appears to be related to this bit of code in _draggableMoved: function (obj) at line 2179 in the leaflet-src.js.
return (obj.dragging && obj.dragging.moved()) || (this.boxZoom && this.boxZoom.moved());

It seems that after box zoom is used, (this.boxZoom && this.boxZoom.moved() always evalutes to true and the DOM event is not fired.
I think the fix may be to add this._moved = false to BoxZoom._onMouseUp() around line 7620, but there may be more to it than that.

Duplicate of #3026.


wvtag fails to open some valid files without the .wv extensions

Copy a valid WavPack file to /tmp/f, /tmp/1, /tmp/1.wv.
/tmp/f is readable as expected:
$ wvtag -q -l /tmp/f

APEv2 tag items:   1 (93 bytes used)
encoder:           Lavf58.29.100

/tmp/1 is not:
$ wvtag -q -l /tmp/1
can't open file

strace shows that wvtag tries to open /tmp/1.wv instead...
And if I add a .wv file extension, it works:
$ wvtag -q -l /tmp/1.wv

APEv2 tag items:   1 (93 bytes used)
encoder:           Lavf58.29.100

I'm on ArchLinux with latest WavPack:
wvtag --version
wvtag 5.2.0
libwavpack 5.2.0

I tried on a couple Linux distros and was not able to reproduce the exact behavior you're seeing. Are you sure you don't have some "f"s and "1"s mixed up?
That said, however, there is an issue with all the WavPack command-line programs in that they cannot handle filenames without extensions because if a filename is entered without an extension they add a default (like .wv in your case). See the wvtag usage:
WVTAG [-options] file[.wv] [...]
This behavior is not very Linuxy but it came from Windows. Is this a showstopper in some way? The only solution I can think of that wouldn't break a lot of stuff would be add an option to force filenames to be interpreted literally (--literally or --literal-filenames or --no-default-extensions).

Are you sure you don't have some "f"s and "1"s mixed up?

Indeed I must have mixed up my test, all files without extensions cause the error.

That said, however, there is an issue with all the WavPack command-line programs in that they cannot handle filenames without extensions because if a filename is entered without an extension they add a default (like .wv in your case). See the wvtag usage:
WVTAG [-options] file[.wv] [...]

That line tells me the .wv extension is optional, so files without it should be accepted. Also on my system man wvtag shows: wvtag [-options] INFILE....

This behavior is not very Linuxy but it came from Windows. Is this a showstopper in some way?

I love WavPack, and this is free software so I can't complain. :wink:
But this is definitely weird behavior unexpected for such a program. I don't know any command line encoder that does that.

The only solution I can think of that wouldn't break a lot of stuff would be add an option to force filenames to be interpreted literally (--literally or --literal-filenames or --no-default-extensions).

I'm not sure the added complexity and flags would not be worse that the current behavior.
In other words, I think the sane default behavior would be to not add an extension if the input file name does not have any, but if you can't change it for legacy reasons, then so be it, you can close this issue.

That said, however, there is an issue with all the WavPack command-line programs in that they cannot handle filenames without extensions because if a filename is entered without an extension they add a default (like .wv in your case). See the wvtag usage:
WVTAG [-options] file[.wv] [...]

That line tells me the .wv extension is optional, so files without it should be accepted.

What that line means is that specifying the extension is optional. I can't understand why it would be good to have WavPack files with the extensions removed. Is that a thing?
I just looked and I could add simply -l (except for wvtag, which uses that) to accept filenames literally, and it really doesn't add too much complexity because it would only apply to someone who ran into this issue. I will consider that for the next release.
And yeah, I can't just change the behavior to not add the extension because that would break the world. And checking with and without adding the extension sounds like a dangerous hack; what if both exist?
BTW, this is an alternative if you really get stuck:
$ wvtag -l - < /tmp/1

What that line means is that specifying the extension is optional.

So it allows passing a file name that is not the input file name.

I can't understand why it would be good to have WavPack files with the extensions removed. Is that a thing?

Nothing is removed. I pass a filename x and somehow wvtag decides that it is smarter than me, that it should definitely rather be x.wv, and it adds an extension implicitly, which causes it to fail for no good reason.
It's generally a good thing for programs to assume the user knows what he/she is doing. Especially if this is a command line program, I mean this is not a phone app with autocomplete where you should favor typing ergonomics and such.
If I followed this flawed logic, I suggest you also hardcode the output directory as ~/Music because after all, people are encoding music, right? What could possibly go wrong, it's definitely a nice feature to have!
Also you seem to be missing that command line programs are most likely called from other programs (scripts) rather than users.
If you want the whole context for my use, here it is:
I have a program for my own use that takes an input audio track (that can be in a lossy or lossless format), applies a bunch of complex audio transformation pipeline, and then plays the result. Because the conversion is slow, the result is saved in a cache, as Vorbis if the input track is a lossless file (to save space), or as WavPack if input is lossy (to avoid a second lossy conversion and degrade quality). The file name in the cache is a MD5 hash of all the transformation parameters, so its for example something like this 79/aeb79bffc923fd2e54416207090941.
Then next time I run the program with the same parameters, the cache file is just played. I don't have an extension because the file name must be the same if the format is Vorbis or WavPack. Also an extension would be completely useless anyway because the player (mpv/ffmpeg) does not rely on it at all.

I just looked and I could add simply -l (except for wvtag, which uses that) to accept filenames literally, and it really doesn't add too much complexity because it would only apply to someone who ran into this issue. I will consider that for the next release.

Honestly do what you feel is right, I can work around this issue easily.
To me it seems also wrong to have an opt in switch to restore a sane behavior, and I don't think I have ever met a command line program that implicitly changes the input path.
So if there is no solution you can safely close this issue, I won't be mad, and I value you work.


Using  Facebook Prophet Model for Daily Births Forecasting using Machine Learning

Daily Births Forecasting using Machine Learning.

Collect and process datasets regarding child births
develop and analyze various ML models along with Facebook Prophet Model.
perform hyper-parameter tuning to optimize performance

@UppuluriKalyani , i did not find any similar issues though


package-templatespecs-2019-06-preview tag added

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.

adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@changlong-liu , could you help to check the config for track2 sdk? thanks.

/azp run automation - sdk

Hi @RodgeFu @Tiano2017 , the python track2 config looks fine.
And the mis-reported breaking changes in track1 is fixed after this PR is merged: https://github.com/Azure/azure-sdk-for-python/pull/12211


Published Fetch xsd is an old version?

The fetch xsd published here does not allow include use of 'options' attribute or 'latematerialize' attribute, but according to this other page, it should!
Our requirement is to validate the fetch xml entered by a user against the xsd and it seems the published xsd is older than what is available.

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

ID: 40fba020-a32b-6e31-9c76-a4226187b059
Version Independent ID: 70388ff8-9442-84c7-0a56-ff397cb65109
Content: FetchXML schema (Microsoft Dataverse) - Power Apps
Content Source: powerapps-docs/developer/data-platform/fetchxml-schema.md
Service: powerapps
Sub-service: dataverse-developer
GitHub Login: @mayadumesh
Microsoft Alias: jdaly

@AgileXRM I am looking into getting the latest schema.

@AgileXRM The published schema has been updated.


add new dataset and how to set parameters

Hello @Yzichen
In this project, I add the new open source lane detect dataset (OpenLane-v1), but I have some question would like to ask you:
for new dataset (OpenLane), how to set FixedCrop params crop=(0, y_start, img_w, img_h)? my img_w=1920 img_h=1280, I don't know how to set y_start.
In addition, In ./mmlane/dataset/xx_dataset.py, how to set params h_samples?  h_samples=list(range(y_start, img_h, y_step)), so how to set y_start and y_step?
If you could give me some idea, I would be very grateful.
Thanks.

I think y_start just needs to make sure that it's truncating an irrelevant region, such as the sky.
The y_start in h_samples is just the same as FixedCrop's. For y_step, I usually simply set it to 10.

By the way, I just read your FastBEV a couple days ago. pretty coincidental, haha.


OS X: "Error: EMFILE: too many open files, watch" when running tests

Is this a bug report?
Maybe. This may well not be a create-react-app issue as such, but hoping someone could point me in the right direction.
Environment
Environment:
  OS:  macOS High Sierra 10.13.3
  Node:  10.1.0
  Yarn:  1.6.0
  npm:  5.6.0
  Watchman:  Not Found
  Xcode:  Not Found
  Android Studio:  Not Found

Packages: (wanted => installed)
  react: ^16.4.0 => 16.4.0
  react-dom: ^16.4.0 => 16.4.0
  react-scripts: 1.1.4 => 1.1.4

Steps to Reproduce

npx create-react-app new-app
Add the following dependencies to package.json:

"dependencies": {
    "@material-ui/core": "^1.0.0",
    "@material-ui/icons": "^1.0.0",
    "classnames": "^2.2.5",
    "react": "^16.4.0",
    "react-dom": "^16.4.0",
    "react-router-dom": "^4.2.2",
    "react-scripts": "1.1.4",
    "recompose": "^0.27.1",
    "typeface-roboto": "^0.0.54"
  },
  "devDependencies": {
    "@storybook/addon-actions": "^3.4.5",
    "@storybook/addon-knobs": "^3.4.5",
    "@storybook/addon-links": "^3.4.5",
    "@storybook/addon-notes": "^3.4.5",
    "@storybook/addons": "^3.4.5",
    "@storybook/react": "^3.4.5",
    "babel-core": "^6.26.3",
    "babel-runtime": "^6.26.0",
    "cypress": "^2.1.0",
    "react-test-renderer": "^16.4.0"
  },

Run yarn test

Expected Behavior
Tests are executed.
Actual Behavior
$ yarn test
yarn run v1.6.0
(node:1262) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
$ react-scripts test --env=jsdom
2018-05-30 13:31 node[1264] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2018-05-30 13:31 node[1264] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2018-05-30 13:31 node[1264] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: EMFILE: too many open files, watch
    at FSEvent.FSWatcher._handle.onchange (fs.js:1352:28)
Emitted 'error' event at:
    at FSEvent.FSWatcher._handle.onchange (fs.js:1358:12)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Other
I've tried first raising the limit of open files to 65536, but still get the above error:
$ ulimit -a
...
open files                      (-n) 65536
...

Any ideas on how to work around this? Thanks!

The easiest thing would be to install watchman:
$ brew update
$ brew install watchman

If you don't have brew, do this first:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Thanks, that fixes the problem -- what's the story on this one, out of interest?

Machines vary, but there is a limit to the number of open files -- if you use sudo it might fix it, but that's a meh fix.
Lots of people don't hit this until they start depending on a ton of dependencies, which is why there's not many issues about it.
Watchman is specially designed to watch arbitrarily large number of files without issue, and people normally install it by the time their applications grow to such a large size because Jest recommends it in the docs somewhere iirc.

Anyway, the important part of the backstory is that newer versions of Jest watch files differently now to prevent this issue, and that version is available in the 2.0 beta.
1.0 is using an older version of Jest which a patch-release isn't going to be cut for.


Repositories pull button doesn't work after failure

when you click the pull button it changes the repository commit hash to HEAD

the commit HEAD what is stored in the DB and is meant to trigger the pull

if the pull fails for any reason then it is left as HEAD so clicking the pull button doesn't change the DB

hence no further actions are taken

changing another field like description triggers the pull to succeed, as the database change is detected and the commit is still set to HEAD

we should probably have a time stamp field update so a change is always detected, this would require a change to models adding a field like (last_pulled) which the controller can update when Pull is clicked regardless of the state of the commit field
@caspiano I would value your thoughts on this as I might have simplified things here

Closed by #28


Sync eng/common directory with azure-sdk-tools for PR 9328

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/9328  See eng/common workflow

API change check
API changes are not detected in this pull request.


[Serialization] Allow loading modules built on some SDK variants

When restricting loading swiftmodules to the SDK used to build them, an exception should be made for modules built against an SDK that is a subset of the SDK used when loading the module. For example, a module built with the macOS11 SDK should be loadable by a client targeting the macOS11.secret SDK. In such a case, the swiftmodule file is more likely to be reliable.
This check is still gated behind the ENABLE_RESTRICT_SWIFTMODULE_SDK env var on the driver side. Loosening this check should make it easier to land it. However, this is still not a recommended configuration so we might want to remove this accepted use case in the future and bring back the requirement for an exact SDK name match.
rdar://92827584

@swift-ci Please smoke test

@swift-ci Please smoke test


Configure gt using custom host and port

I'm running seagoat-server in the cloud and want to configure gt to use an external host and port instead of http://<IP_ADDRESS>:35257. Please consider adding this feature.

I would definitely want to add this feature. Actually if you need it urgently, or you would like to contribute you, feel free to create a pull request. I can help you get it merged asap.
It's not so complicated to do this as this only affects the CLI.
I am explaining here how to implement it to make it easy for you. As a first step you can add a new flag/option to supply the remote server URL:
https://github.com/kantord/SeaGOAT/blob/4b6e74a06bf8ff02c0ca2a4e0c4df963d42636ea/seagoat/cli.py#L68-L107
then, you just need to make sure that that argument is used instead of getting the server info here:
https://github.com/kantord/SeaGOAT/blob/4b6e74a06bf8ff02c0ca2a4e0c4df963d42636ea/seagoat/cli.py#L120-L121
A further improvement could be to create support for config files, and then in those config files there could be a configuration option to match a local folder with a remote server URL so that it always uses the remote server by default.

I am adding good first issue on this one as well, as a releasable implementation can be created without knowledge of the project structure using the information I shared above. Also testing should be easy, you can take inspiration in test_cli.py.

I would also like to note that it should be possible to create a feature that allows local users to import data from a remote server to avoid having to analyze the entire repository locally. Actually you should already be able to do this manually by simply copying the cache folder from the server to the local machine. This would have the added benefit that the users are still able to search their local changes, and even when they are not connected to the internet. And it should also be faster by saving the network overhead
Also I am working on creating a web-based GUI as well, using that your users will be able to search your repositories using SeaGOAT without installing anything on their computer: https://github.com/kantord/SeaGOAT-web

Now that configuration files are supported, this should be even more trivial to implement!


in node require

Please specify:
In node,
const produce = require('immer');
....

TypeError: produce is not a function

Try const produce = require('immer').default

Closing as question has been answered.


Embed only certain lines

I have implemented a solution to embed only certain lines. It introduces two new arguments. See https://github.com/myroslambda/embed-like-gist/commit/890c829e26e396b207bd3c0e3bb2324d0cd263f7
The only thing that does not work is line numbering. I know where to put it, but the PR in highlighjs-line-numbers has not been accepted yet: https://github.com/wcoder/highlightjs-line-numbers.js/pull/65
Would it make sense to add this to the project, and maybe to ping  https://github.com/wcoder/ and ask if that PR can be accepted?

I got a message that that PR was accepted in highlightjs-line-numbers, so this one would only require one small change. If you think it can be accepted I can make the change in my fork and send a PR.
@yusanshi ?

Good job! Thanks a lot. 😃
Since it was integrated into 2.8.0, using this will be fine.
<EMAIL_ADDRESS>Also, maybe we should add two input boxes in 404.html.
Btw, sorry for my late reply. I noticed this issue, but I'm quite busy you know😅

OK. I will prepare and send a PR. Thank you!

Hey guy, #6 is merged so I'll close this issue.
Anyway, thanks you!😁

That's ok. I have been really busy and did not have time to send the PR. Thank you!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


model

Excuse me
The original tiny-yolo model filter number is 16-32-64-128-256-512-1024-1024
Why is the filter number used here 16-64-64-128-256-512-512?
And more accurate than the tiny-yolo model

The network model is inspired by the original tiny-yolo model, but we performed channel pruning in the last 2 layers, as well as increasing number of channels in the second layer to recover accuracy and fully exploit the parallelism of the overlay.


Support formatting JSON

Currently, I don't believe if you use the JSON encoder, you can format it, it would be awesome if this was the case.

It could possibly look something like this
refresh_rate: 30 seconds
appenders:
  stdout:
    kind: console
    encoder:
      kind: json
      pattern: "{d(%Y-%m-%d %H:%M:%S)} - {m}{t}{T}{n}"
root:
  level: info
  appenders:
    - stdout

``1

It will be better to support add custom key when using JSON encoder, it will be able to link Filebeat and ELK Stack directly for analysis.

Thanks.  Alex

@Ruijuan-Cao can you give an example?

Firstly, thanks for your reply, and I'm very sorry to see this so late.
For example, I need a new customized key-value "type-xxx“ in log for analysis, I didn't find any guidance document to add a new key, so I tried to pretend like that by this
let str = "hello,test\",\"type\":\"xxx";
info!(target:"app", "{}", str);

but all msg including double quotation marks is treated as message by escape character.
And the output is shown below：
{
    "time":"2020-06-04T20:59:19.946833+08:00",
    "message":"hello, test\",\"type\":\"xxx",
    "module_path":"spot::statics::clog",
    ...
}

but what I want is like that：
{
    "time":"2020-06-04T20:59:19.946833+08:00",
    "message":"hello, test",
    "type":"xxx",
    "module_path":"spot::statics::clog",
    ...
}

So, I want to know if there is any way to do this.（Maybe this is a bit stupid requirement🤦♀)
Thank you very much.

Sorry, been away for a while. I still think this would be a great thing to have. Everyone else still interested @estk @Ruijuan-Cao ?

Any update on this feature?

@caoruijuan13 the log crate does not have a notion of structured logging, I would suggest that you use an empty formatter and serialize the json output yourself. Using a separate log target you can filter out your custom serialized logs to a separate appender.

Hi! I'm finding evidence that json formatting is supported in closed issues and here, yet there is no support for that in docs and code from stackoverflow itself isn't working.

I'm very interested about this feature. It should be awesome if i can use any stored MDC variable in the formatted json output.
Is currently a workaround to create a custom encoder?


Windows Installation Fails While Installing pyinotify: inotify is not available on win-amd64

Hi!
running pip install moya on Windows fails with this message::
inotify is not available on win-amd64
inotify is a Linux program, not available on Windows. Moya requires pyinotify, which is, apparently, available only for Linux (https://github.com/seb-m/pyinotify#dependencies)
However, you state that Moya should run on Windows (http://docs.moyaproject.com/0.5/en/installation.html#windows).
Is there a workaround available?
Thanks!

Hi,
I've just pushed version 0.5.3, which fixes that and a few other issues. It should run on Windows now. Let me know if works for you...
Will

Thanks! Installed like a charm. The only quirk is that lxml has to be installed separately, but that's no problem with these wheels http://www.lfd.uci.edu/~gohlke/pythonlibs/#lxml
Thanks again!

Great. lxml is a pain on Linux as well. Will add that to the docs.


Release 2.0.0 to npm

2.0.0 was released on GitHub but npm doesn't include it.
/cc @jedwards1211
When jscodeshift-find-imports is released on npm can we at the same time update jscodeshift-add-imports.
Right now jscodeshift-add-imports pulls in an older version of ast-types that I'd like to get rid of.

Okay, something must have thrown off semantic-release, I'll see if I can sort this out and upgrade ast-types as well.

Maybe I confused it with jscodeshift-add-imports. The issue about ast-types remains. jscodeshift is currently multiple versions behind in jscodeshift-find-imports

I think what you meant is that jscodeshift-add-imports wasn't using version 2 of jscodeshift-find-imports.  I released new versions of both though with jscodeshift 0.11.0 (really wish people would stop using version 0...).  Can you upgrade and confirm that everything is fixed for you?
Btw sometimes with yarn at least to ensure I get the latest version of a transitive dep, I have to remove the primary deps and then add them back, yarn upgrade --latest doesn't always upgrade the transitive deps.

argh hang on, I accidentally published jscodeshift-find-imports with @types/jscodeshift as a dev dep

Actually I think ast-types should be 0.14.1 if all the transitive deps work correctly, but I'm running into this issue: https://github.com/benjamn/ast-types/issues/425

Do you know if<EMAIL_ADDRESS>will work for you?

In 0.x any minor bump is considered breaking so package managers won't pull in 0.11 if you declare ^0.6. You have to declare ^0.11. So removing the lockfile entries wouldn't have done anything here.
While I don't think you should ever use >= it should fix my specific problem. Will check back tomorrow.

I guess I should use ^0.7.0 || ^0.8.0 || ....  0.x packages are so inconvenient to work with...I was worried if I left jscodeshift as a primary dependency it might cause other issues?
I did that in jscodeshift-add-imports for 0.7.x up to 0.10.x since it breaks with jscodeshift 0.11.0.

Can't tell if the following releases actually contain breaking changes or not:

forgot to close this

forgot to close this


Fix ViewTeammateCommand to take in GitUserName

Resolve #236

Codecov Report

Merging #310 (2f7bc81) into master (d4b9259) will decrease coverage by 0.03%.
The diff coverage is 57.14%.

@@             Coverage Diff              @@
##             master     #310      +/-   ##
============================================
- Coverage     69.63%   69.60%   -0.04%
  Complexity      929      929
============================================
  Files           136      136
  Lines          3086     3086
  Branches        416      416
============================================
- Hits           2149     2148       -1
- Misses          790      791       +1
  Partials        147      147

Impacted Files
Coverage Δ
Complexity Δ

...ss/logic/commands/project/EditTeammateCommand.java
79.01% <ø> (-0.26%)
8.00 <0.00> (ø)

...ss/logic/commands/project/ViewTeammateCommand.java
33.33% <57.14%> (ø)
2.00 <1.00> (ø)

...ddress/logic/parser/ViewTeammateCommandParser.java
62.50% <57.14%> (-8.93%)
2.00 <1.00> (ø)

Continue to review full report at Codecov.

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


ImageInspectError on installing gitkube (gitkube install) on minikube

Environment ?
minikube version
minikube version: v0.26.1

$ gitkube version
v0.2.0

What did I do?
gitkube install
What I Expected to see?
Gitkube running peacefully
What did I see instead?
$ k get po -n kube-system
NAME                                    READY     STATUS              RESTARTS   AGE
default-http-backend-ddb2s              1/1       Running             2          2d
etcd-minikube                           1/1       Running             0          26m
gitkube-controller-cc586fcb-zfk8b       0/1       ImageInspectError   0          23m
gitkubed-6dc69968c5-zwqg5               1/1       Running             0          23m
kube-addon-manager-minikube             1/1       Running             2          2d
kube-apiserver-minikube                 1/1       Running             0          26m
kube-controller-manager-minikube        1/1       Running             0          26m
kube-dns-86f4d74b45-9qfxb               3/3       Running             7          2d
kube-proxy-kjncs                        1/1       Running             0          25m
kube-scheduler-minikube                 1/1       Running             2          2d
kubernetes-dashboard-5498ccf677-cxhrm   1/1       Running             6          2d
nginx-ingress-controller-csqzz          1/1       Running             4          2d
storage-provisioner                     1/1       Running             6          2d
tiller-deploy-5f789bd9f7-zmt8g          1/1       Running             2          2d

$ k describe po gitkube-controller-cc586fcb-zfk8b -n kube-system
....
....
Events:
  Type     Reason                 Age                From               Message
  ----     ------                 ----               ----               -------
  Normal   Scheduled              21m                default-scheduler  Successfully assigned gitkube-controller-cc586fcb-zfk8b to minikube
  Normal   SuccessfulMountVolume  21m                kubelet, minikube  MountVolume.SetUp succeeded for volume "gitkube-token-klm4g"
  Warning  Failed                 6m (x71 over 21m)  kubelet, minikube  Error: ImageInspectError
  Warning  InspectFailed          1m (x93 over 21m)  kubelet, minikube  Failed to inspect image "hasura/gitkube-controller:v0.2.0": rpc error: code = Unknown desc = Error response from daemon: readlink /var/lib/docker/overlay2: invalid argument
`

Hmm weird. What version of docker are you running? Which OS?

$ docker version
Client:
 Version:       17.12.1-ce
 API version:   1.35
 Go version:    go1.9.4
 Git commit:    7390fc6
 Built: Tue Feb 27 22:13:43 2018
 OS/Arch:       linux/amd64

Server:
 Engine:
  Version:      17.12.1-ce
  API version:  1.35 (minimum version 1.12)
  Go version:   go1.9.4
  Git commit:   7390fc6
  Built:        Tue Feb 27 22:20:43 2018
  OS/Arch:      linux/amd64
  Experimental: false

$ uname -a
Linux minikube 4.9.64 #1 SMP Fri Mar 30 21:27:22 UTC 2018 x86_64 GNU/Linux

$ cat /etc/*-release
NAME=Buildroot
VERSION=2017.11
ID=buildroot
VERSION_ID=2017.11
PRETTY_NAME="Buildroot 2017.11"
NAME=Buildroot
VERSION=2017.11
ID=buildroot
VERSION_ID=2017.11
PRETTY_NAME="Buildroot 2017.11"

Image inspect errors seem to be caused due to the runtime and not the container per se. Do you mind updating minikube to the latest version (0.28) and trying this out?

It seems there are no problems. :peace_symbol:
$ minikube version
minikube version: v0.28.0

$ k get po -n kube-system
NAME                                        READY     STATUS    RESTARTS   AGE
default-http-backend-59868b7dd6-dgjlw       1/1       Running   0          2m
etcd-minikube                               1/1       Running   0          2m
gitkube-controller-cc586fcb-tfrtp           1/1       Running   0          1m
gitkubed-7874c94957-fg7xj                   1/1       Running   0          1m
kube-addon-manager-minikube                 1/1       Running   0          2m
kube-apiserver-minikube                     1/1       Running   0          1m
kube-controller-manager-minikube            1/1       Running   0          2m
kube-dns-86f4d74b45-kxmwv                   3/3       Running   0          2m
kube-proxy-qs8sj                            1/1       Running   0          2m
kube-scheduler-minikube                     1/1       Running   0          2m
kubernetes-dashboard-5498ccf677-bx888       1/1       Running   0          2m
nginx-ingress-controller-67956bf89d-rx462   1/1       Running   0          2m
storage-provisioner                         1/1       Running   0          2m


Keep the API key in memory

I can assign the API key as shown in the documentation:
Streak.api_key = 'secret_key'
# do something with the API

problem is this seems to be scoped per method. If I set the key in an initializer it will be lost by the time I call the save method below.
class Something
  def initializer
    Streak.api_key = 'secret_key'
  end

  def save
    # do something with the API, API key no longer set
  end
end

Is there a way to set the API key without assigning the key in each method separately, in an environment variable or configuration file for example?

@cimm Try adding the key to an ENV variable.  I used figaro and it works perfectly.

@cimm You need to change initializer to initialize.


Mirror with "Merge faces" option throw an Exception

When using the Mirror tool, with the  "Merge faces" option,  taking the top surface of a cylinder  as the datum,throw an exception:

This is an OCCT issue. I have filed a ticket there (33421), the fix should be included in the next release.


Related to logging of model states in mujoco

Hi,
I'm an undergraduate student and I'm currently planning to work on a project for benchmarking physics engines.
I am interested to know if there is a feature available for logging the model states (eg: position, orientation, velocity, etc) for simulation duration in mujoco. if there is a functionality available, please let me know in which format the log files get stored.
Thank you

https://mujoco.readthedocs.io/en/latest/computation/index.html#the-state


BigBank - SystemContext - Relations

Hi Team,
Here we are trying to understand if the structurizr  is generating the diagram in the correct way comparing to the c4model definition that you can find it here > https://c4model.com/#SystemContextDiagram
Reading the c4 definition, we understood that the system in focus will be placed in the middle of the diagram, blue coior, and all direct relations will be drawn on the diagram resulting to this:

Now let's suppose that the mainframe and the email system talk to each other, I added this line mainframe -> email "sends mail "IMAP" to the BigBank sample at line 53, and the result is:

As you can see there is a connection between mainframe and email system showing on the systemcontext of Internet Banking Systems
Looking to the C4model definition it looks like this is an incorrect behaviour because the connection between mainframe and email are not related to the internet banking system.
Is this a bug? Or we are misunderstanding the c4 definition?

The second diagram is showing more relationships than is necessary, but it's still a System Context diagram, because it's showing the software system in scope, and the people + software systems around it.

Perfect @simonbrowndotje
I consider this a BUG because that connection between mainframe and email isn't part of the context of Internet Banking.
I will take a look at the source code and see if I can fix it.

I can point you to the code that implements include *, but this isn't a bug. There are times when it's important to show relationships where the software system in scope isn't the source or destination. You can see an example of this above - the system context diagram for the Internet Banking System includes the relationship between the E-mail System and the Personal Banking Customer. That's useful to include here, because it helps tell a story.
If you need to remove any relationships that include * adds by default, you can use the DSL exclude statement to exclude them.


Created CompositeDispatcher

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Tests pass?
✔

The composite dispatcher may be used in Debugger package.
It needs to aggregate any PSR event dispatcher with our own or any PSR.

Good one 👍


Flexible keymap (hotkeys / shortcut)

the important key to achieve it in flexible and reliable way is to have two things:

list of possible events to rpc.emit 1
one place to bind keys to those events

1 Note: rpc bus should be the only way to broadcast key events).
Initial array of events can be collected from lib/index.js#L38-L129: like split request vertical or  split request horizontal, etc.
Then in config we can do smth like this:
keymap: {
 "CmdOrCtrl+Alt+Left": "prev pane req",
}

where keys are electron accelerators and values are those events for rpc to emit/receive.
After that, we need to modify attachKeyListeners() lib/containers/hyper.js#L38-L76 to not bind hardcoded keys, but instead to pick up keys and events from keymap:
// mousetrapify needs to be more advanced, for sure, but this is enough for now
const mousetrapify = key => key.replace('CmdOrCtrl', 'mod').toLowerCase();
Object.keys(this.config.keymap).map(item => {
  const accelerator = item;
  const event = this.config.keys[key];
  keys.bind(
    mousetrapify(accelerator),
    () => {
      if (focusedWindow) {
          focusedWindow.rpc.emit(event);
      }
    }
 );
})

Also, Hyper needs to verify that this.config is merged object similar toObject.assign({}, defaultConfig, ...[pluginsAndThemesConfigs], userConfig)
Thats it.

One interesting benefit of proposed approach is that you can update menu accelerators very easy and smooth. just needs to write a function which will lookup desired accelerator by key event relevant to that menu item. 2, 3

2 because right now keeping hotkeys in a menu relevant is a fragile mess
3 findAccelerator is pretty simple function:

const findAccelerator = event => Object.keys(this.config)
  .map(key => { key, value: this.config[key] })
  .find({ value } => value === event)
  .key

Result

widely commons keymap sets can be distributed via plugins
always relevant hotkeys in menu to briefly lookup forgotten keybindings
with list of events and keymap to them it will be possible to "view all keyboard shortcuts" (fix #814)
user gets fully customizable key bindings 🎉 (fix #251 and #657)

what do you think?

i want to discuss this approach before i will start implementation, so any feedback is welcomed: ideas, questions, concerns, problems, etc

@leo @CodeTheory @ekmartin @rauchg what do you think?

I'm not sure if it's a good idea to bind keybindings to rpc directly. Far from all combinations have an rpc event connected to them at the moment, so not sure if that's a good direction to go.
Why not have a separate keymap file that maps a string key to a combination? I.e. 'split-vertical': 'Cmd+D'. That way the keymap config could be used both in the menu decorator and in the hyper container.
We could then expose the keymap to plugins in the same way we do with a regular config.
Example would be: keys.bind(keyMap['move-right'], moveRight).

I'm not sure if it's a good idea to bind keybindings to rpc directly.

maybe its not a good idea, but rpc as a central piece of code for key bindings — is the best point i could think of. To be honest, in the end it can be not a rpc, but any central broadcast communication api. It just happens, that rpc is what we have now.

Far from all combinations have an rpc event connected to them at the moment, so not sure if that's a good direction to go.

We can add them later, once proposed changes will be in place, it should be easy.

Why not have a separate keymap file that maps a string key to a combination?

main reason against two files over one, is simplicity: harder to show/sync your settings with two configuration files You may think that configuration file with a whole keymap will be too hard to read, though to cure this problem we need to think careful about sane default keymap.

I.e. 'split-vertical': 'Cmd+D'. That way the keymap config could be used both in the menu decorator and in the hyper container.

Exactly! I'm all for that as i mentioned in proposal.
Need to note, that keybinding: rpcEvent have to be reversed, because relation is not one keybinding to multiply rpcEvents, but quite opposite — one rpcEvent to many keybindings. And hey, its how its done in Atom, which i cant blame for blame for bad keymap decisions.

We could then expose the keymap to plugins in the same way we do with a regular config.

Yep!

Example would be: keys.bind(keyMap['move-right'], moveRight).

Kinda, as far as pairs are revered you have to do smth like this:
Object.keys(this.config.keymap).map(accelerator => {
      const event = this.config.keys[key];
      keys.bind(
        mousetrapify(accelerator),
        () => { rpc.emit(event); } // kinda
     );
    })

tldr:

one file is simpler than two
for this feature to work we need broadcast mechanism, lets start with rpc for now
pair should be keybinding: event

I'll argue for an approach to keybindings that guarantees sensible rebinding and/or unbinding.  A concrete example:
When using iTerm2, I rebind the ⌘1 through ⌘9 keys globally (across all profiles).  Instead of their normal function of switching the first nine iTerm2 tabs, they instead are bound to emit <prefix>-<num> which switches between tmux windows.  I.e. I use tmux so heavily that I prefer the normal Command bindings to treat tmux windows like tabs.
Another frustration of some keybinding systems (vim, I'm lookin' at you) is that not all bindings are first-class and/or introspectable.  I.e. there's no command or API that can ask such questions as:

What are all the currently active keybindings?
What key(s) are bound to operation <foo>?
What operation(s) are bound to key-sequence <bar>?
(Bonus points) Where did a given binding come from?  (e.g. user config, plugin baz, etc.)

These operations aid both config debugging and discoverability.

@jwhitley After and if proposed change will land in master. All keybindings will be declared in one keymap object, and it will be possible to redefine them in your config.keymap

bad news everyone, Hyper has two rpc, one for Electron and one for Renderer processes, and you cant share them. problem here is that key bindings in ./lib/containers/hyper.js can be used to emit event only to to Renderer's rpc, while actual rpc responsible for hotkeys is Electron's one

on the other not, there is another way

This PR #925 is another approach, i was talking about

@rauchg can i ask you to move labels from #925 PR into this original issue? Priority: High, Status: Community feedback wanted, Status: In Progress. And share your thoughts about last label

@iamstarkov I switched the label

Plz add request inside issue: ppot#11

Referring to the label "In progress", is this issue actively being worked on? All i could find was @iamstarkov closed PR.

@andrroy look at  https://github.com/ppot/hyper/issues/11

and yes it is in progress

here https://github.com/zeit/hyper/pull/1509

close in #1876


Remove @modulz/design-system

Finish removing @modulz/design-system
Use Untitled Sans files which don’t have the macOS @1x hinting problem
Declare Untitled Sans Medium as "bold" ("medium" is kept for backwards compatibility in primitive demos until we do a pass on them at some point)
Make sure styles that still use Stitches can be SSR'd
Visual tweaks on Primitives homepage

Do we need to tweak any other ddetails given the change to glyph scaling? here are the primitives feature lists on my x1, they feel pretty tight now:

@andy-hook I prefer it with the font being a hair tighter tbh, but it could be somewhat different on your screen. We also didn't tweak anything when updating it in WorkOS UIs. Could you do before/after screenshots of what you are seeing?
Here's what I'm seeing, before:

After:

before/after
List:

Longform:

We also didn't tweak anything when updating it in WorkOS UIs

You're right, and I remember now having a similar discussion then. The nature of the issue means that we can't tweak on one density without affecting the other anyway.
The new long form looks good to me, it's only the feature lists that feels like they need a touch more margin between the items.
Regardless, I think we should move forward as this is the same discussion as last time 😄

it's only the feature lists that feels like they need a touch more margin between the items

Yeah these look overly tight @2x too, I think the issue was just a bit masked @1x before. Making the gap a bit larger:


[Bug] Poor Launcher scaling

## About this report
Essentially this :

In Ubuntu 20.04.2 LTS, the launcher scaling was pretty terrible without turning on Custom UI scaling in the default. And even then, it did not allow itself to be pinned into the corners or rescalled.

Only grabbing it with the windows + left click hold managed to drag it fully into view.
I do not know much about making this sort of software, but i believe it could use to have custom UI scaling by default.

Looks like the OS reports screen DPI incorrectly. What is your resolution, physical display size, and scaling in Gnome?

I will answer you once i get back to my machine. I don't have access over the weekend.

I have two screen, both are 16:9. The first one is a laptop screen :
Hp probook 650 g4 - 39.62 cm (15.6 in) diagonal LED-backlit FHD IPS eDP anti-glare LED-backlit, 45% sRGB, 220 nits
The second one is a fixed screen :
https://iiyama.com/gl_en/products/prolite-b2483hs-b3/
1920 x 1080 - 24", 61cm
As for your question regarding scaling in gnome, i am not sure how to find that as i am only a recent user of Ubuntu. I can tell you the display scale is set to 100%.
I hope this help. I'll be around to answer any question.

So, your primary display is 15.6" and 1366x768 pixels. That works out to 100 DPI (you can check by running xdpyinfo | grep resolution).
I see now. DPI is not the problem here, your screen is just not tall enough (in pixels). The launcher window is too large for it,
but it still wants to use 100% scaling because the screen DPI is close to the standard 96 due to its small size.
Just set the scaling to 87.5% and have fun. Sorry, but your setup is kind of an edge case. Not many devices have these low resolutions today. When laying out the UI, I knew something like this would come up, but there was no way to make it more compact and still work well on all scales, so this is how it will have to stay.

Hi.  I've also ended up running into this issue, and i was just as confused when i booted the application for the first time.  If it's not possible to fix this issue, would it be possible to include some sort of notice in the readme for this repository informing people about this?

Perhaps the scale detection logic can check whether the inferred scale makes the window taller than the vertical resolution. It won't be perfect, though, so I am not sure this is worth implementing. Maybe a simple note will indeed be better.
For statistics, what is your screen resolution and system UI scale?

I'm running at 1080p 16:9 at 60hz.  I can't seem to figure out what my system UI scale is.

Maybe you know what your screen diagonal is? E.g. 17", 22", etc.

I can't find any information in my system settings, but i measured it and it looks to be a little over 31.5cm w/o bezels and approximately 36cm with bezels (I don't know how this is measured normally)

I have this same problem.
14", 1920 x 1280, scaled 120%
Manjaro:latest-stable, GNOME 43
Launcher refuses to respect DE's Alt-click-drag.
[update]
The weird sizing thing only happened on first run.  By quitting out of the launcher (killing it via GNOME's overview), and re-launching, the sizing magically fixed itself.  It still refuses to respect the alt-click-drag thing, though.


When resuming suspended threads, Bugsnag does not respect suspend_count

Describe the bug
In crash and app hang scenarios, Bugsnag suspends threads in order to capture stacktraces at the time events occur. I was perusing the Darwin documentation and noticed this detail for thread_suspend:

To resume a suspended thread, use thread_resume. If the suspend count is greater than one, thread_resume must be repeated that number of times. Link

The Bugsnag SDK iterates over the suspended the threads and calls thread_resume, but it doesn't appear to respect the suspend_count. Should it? As is, can this result un-resumed threads?
All said, I'm not sure if there's really an issue here, but It seems at least possible(?) that the system crash tooling could also suspend threads resulting in a suspend_count higher than 1.
Steps to reproduce
N/A
Environment

Bugsnag version: 6.16.1
CocoaPods version: N/A
Carthage version (if any): N/A
iOS/tvOS/macOS version(s): iOS 15.5
Simulator or physical device: Either
Xcode version: Xcode 13.4
Swift version (if applicable): N/A

Example Repo

[ ] Create a minimal repository that can reproduce the issue
[ ] Link to it here:

Example code snippet
# (Insert code sample to reproduce the problem)

Error messages:

Hi @cwalo
As you correctly mentioned Bugsnag does suspend threads at the point of error capture. While the Darwin documentation does mention the possibility of the suspend count being greater than 1, when Bugsnag resumes the threads we are simply resuming the threads that we suspended. In other words we are undoing our increment.  This also means that any threads that may have already been suspended at the point Bugsnag calls thread_suspend would return to their previous state rather than Bugsnag incorrectly resuming them.


Add 358 geocoding renamed file to release 7.7.3

This change is

This PR LGTM Keghani. Thanks :)

Please click on "Add your review" and approve, otherwise this can't be merged since the master branch is protected.
Then merge.


added advisoriesPath cmd line support

Also update in-line docs in lib/check.js like I did? https://github.com/nodesecurity/nsp/pull/64/files#diff-0e9a53fc6808cd403458fe3c3dfb431fL42

and update usage/check.txt

@reedloden thanks, good catch.
With our pull requests combined.

Should be done. Once @nlf gives it a quick look over I'll minor rev and publish

:+1: looks good to me

Did you notice the spec failure on Node 0.10.x?

Specifically https://drone.andyet.com/nodesecurity/nsp/15/1 (@evilpacket)

Yup, we are going to use a polyfill for isAbsolute before the push to maintain 0.10 support for now.

On Dec 2, 2015, at 11:25 AM, Reed Loden<EMAIL_ADDRESS>wrote:
Specifically https://drone.andyet.com/nodesecurity/nsp/15/1 https://drone.andyet.com/nodesecurity/nsp/15/1 (@evilpacket https://github.com/evilpacket)
—
Reply to this email directly or view it on GitHub https://github.com/nodesecurity/nsp/pull/65#issuecomment-161406062.


docs(): add a link to Angular-Translate Quality

Hi!
I use Angular Translate in our web application and I have developed a NodeJS library to verify the quality of our translation files. This humble pull request is about adding a link towards the project. Feedback is obviously welcome.

@vincent-zurczak  Thank you, great tool!


Clean before bintray upload.

Try git clean before publishing.

@mccheah please squash commits that are not merges from upstream


list index out of range error while running main.py

Hi DongjunLee,
My stack is python3.6
tensorflow1.4
hb-config0.3.3
pycharm IDE 2017
I am impressed by working with your code.I'm currently  working with RNN.I have gone through your code which is written using High level API'S like Estimators,Dataset and Experiment,But i'm facing error while running main.py file as follows....
Traceback (most recent call last):
File "/home/PycharmProjects/conversation-tensorflow-master/main.py", line 38, in
Config(args.config)
File "/home/virtual-3.6/lib/python3.6/site-packages/hbconfig/init.py", line 23, in call
self.config = self.read_file(fname)
File "/home/virtual-3.6/lib/python3.6/site-packages/hbconfig/init.py", line 32, in read_file
config_file = config_files[0]
IndexError: list index out of range
Kindly resolve this issue at the earliest..
Thanks in advance.

Hi @sushmas88
Thank you for issuing!
First of all, maybe the error was due to typo when you entered the config name.
If you enter the config name correctly, there will be no problem. :)
I'll fix it right now

I fixed this issue and deploy to pip.
you can upgrade hb-config with this command.
pip install --upgrade hb-config

My issue in not resolved by doing above changes. Below is the link right now i'm working on-
here
Now, i'm getting following error in main.py file as follows...
File "main.py", line 38, in
Config(args.config)
File "/home/virtual-3.6/lib/python3.6/site-packages/hbconfig/init.py", line 25, in call
self.config = self.read_file(fname)
File "/home/virtual-3.6/lib/python3.6/site-packages/hbconfig/init.py", line 32, in read_file
raise FileNotFoundError(f"No such files start filename '{fname}'")
FileNotFoundError: No such files start filename '/home/sushma/PycharmProjects/conversation-tensorflow-master/config/check_tiny.yml'
Please resolve this...

Hmm..
@sushmas88 could you check the config file exist?
file path is '/home/sushma/PycharmProjects/conversation-tensorflow-master/config/check_tiny.yml'

yes. config file is exactly in  that path only.

Did you enter this command?
python main.py --config check_tiny --mode train
if you entered this command and config file that start file name as 'check_tiny' didn't not exist,
hb-config raise error message like this FileNotFoundError: No such files start filename check_tiny'
can you check it again?

@DongjunLee
/PycharmProjects/conversation-tensorflow-master$ python3.6 main.py --config /home/sushma/PycharmProjects/conversation-tensorflow-master/config/check_tiny.yml --mode train
i'm giving this command in pycharm terminal but the error remains same.
i have kept that check_tiny.yml in my pycharm directory.
please do resolve this..

I understand the problem. :)
just enter this command.
python3.6 main.py --config check_tiny --mode train
not
python3.6 main.py --config /home/sushma/PycharmProjects/conversation-tensorflow-master/config/check_tiny.yml --mode train
I will fix it can enter the full path of config.

@DongjunLee
Thanks Now its working...

Thanks :)


ERROR: Failed building wheel for aardwolf

Cannot install on arch NetExec,
tryed with pip, pipx and poetry
Python 3.12.3
6.9.4-zen1-1-zen Archlinux

@Ayanashi Can you provide some more information? Where does it fail? What's the output when it fails?

I had this issue as well earlier today on Arch after upgrading my system. Couldn't install NetExec via pipx because aardwolf install was failing and that I needed to set my Rust toolchain to a stable release channel.
I ran the following command and then was able to proceed with a normal install without issues:
rustup default stable
pip3 install aardwolf --break-system-packages
pipx install git+https://github.com/Pennyw0rth/NetExec

@Ayanashi If this resolves your install problem please accordingly close this issue. Thank you

If that works we can add it to the install instructions ^^ @Ayanashi please confirm if that worked or not.

Suggest Work! thanks

@Marshall-Hallenbeck We have a few people here validating the fix worked. If you could add to the install instructions that would be great


Disable "Include in course grade calc" checkbox when item is not assigned to category

When creating (or editing) a GB item, disable the "Include in course grade calculations" checkbox if a category has not been selected for the item. Once a category is selected, enable the checkbox.

Just to confirm, does this behaviour only apply when the Gradebook has been setup with "Categories & Weightings"? Or should it apply also when "Categories Only" is selected?

If the original Gradebook is to believe, then we want to disable the "Include in course grade calculations" checkbox when category is empty for both "Categories Only" and "Categories & Weightings".

Confirmed


documents: integration with Flask-IIIF

[ ] extend Flask-IIIF to read bytestream
[ ] legacy fallback for recid:{recid} and/or recid:{recid}-{filename} and/or {document.uuid}

--
cc @blixhavn @egabancho @drjova

Maybe we can get a 403 or something if the requested thumbnail is on a restricted document we don't have access to?


DOC: Add more docstrings to public methods (close #87)

Codecov Report

Merging #90 (f569664) into develop (48cff86) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop       #90   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           31        31
  Lines          844       887   +43
=========================================
+ Hits           844       887   +43

Impacted Files
Coverage Δ

pfhedge/nn/modules/hedger.py
100.00% <ø> (ø)

pfhedge/instruments/__init__.py
100.00% <100.00%> (ø)

pfhedge/instruments/american_binary.py
100.00% <100.00%> (ø)

pfhedge/instruments/base.py
100.00% <100.00%> (ø)

pfhedge/instruments/european.py
100.00% <100.00%> (ø)

pfhedge/instruments/european_binary.py
100.00% <100.00%> (ø)

pfhedge/instruments/lookback.py
100.00% <100.00%> (ø)

pfhedge/instruments/underlier.py
100.00% <100.00%> (ø)

pfhedge/nn/modules/bs/_base.py
100.00% <100.00%> (ø)

pfhedge/nn/modules/bs/american_binary.py
100.00% <100.00%> (ø)

... and 5 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 48cff86...f569664. Read the comment docs.


feat(default-theme): Add pagination for placed orders

Changes
This PR closes https://github.com/vuestorefront/shopware-pwa/issues/379

update response after fetching orders from API.
update logic handling pagination for useCustomerOrders
update default limit for defaultApiParams
update UI for orders component.

Checklist

[x] Pagination component is visible on orders history page
[x] default pagination params are consistent with the default settings (10 per page)
[x] consider: do not show pagination if orders collection is less than 11

@patzick
this is because we repeat nuxt-child 3 times. Each time the route changes, the current page will be rendered 3 times, but only show 1, the remaining pages are hidden.
I can solve this problem by the below solution. How do you think ?


Duplicate chunks throw an error

If you setContent with repetitive data on a collection, an error is thrown when trying to get that content again.
 TypeError: Cannot read properties of undefined (reading 'length')
    at reduce (/etebase-js/src/Crypto.ts:36:49)
    at Array.reduce (<anonymous>)
    at concatArrayBuffersArrays (/etebase-js/src/Crypto.ts:36:26)
    ...

It looks like the index list and/or chunks created here are the issue (the indices are pointers at the original chunks array, but the chunks array is mutated here, so the pointers are incorrect?)
The following tests illustrate the issue (large files are fine, small files are fine, but repetitive data (that would result in chunks that would be deduplicated) throws the error
describe.only("chunking files", () => {
  it("Duplicate Chunks", async () => {
    const collectionManager = etebase.getCollectionManager();
    const col = await collectionManager.create(colType, {}, "");

    const buf = randomBytesDeterministic(10 * 1024, new Uint8Array(32)); // 10kb of psuedorandom data
    const content = JSON.stringify([buf, buf, buf, buf]);

    await col.setContent(content);

    await collectionManager.transaction(col);
    const decryptedContent = await col.getContent(); // <---
    /*
  TypeError: Cannot read properties of undefined (reading 'length')
    at reduce (/etebase-js/src/Crypto.ts:36:49)
    at Array.reduce (<anonymous>)
    at concatArrayBuffersArrays (/etebase-js/src/Crypto.ts:36:26)
    ...
  */

    const out = to_string(decryptedContent);
    expect(out).toEqual(content);
  });

  it("Regular Chunks", async () => {
    const collectionManager = etebase.getCollectionManager();
    const col = await collectionManager.create(colType, {}, "");

    const buf = randomBytesDeterministic(100 * 1024, new Uint8Array(32));
    const content = JSON.stringify(buf);

    await col.setContent(content);

    await collectionManager.transaction(col);
    const decryptedContent = await col.getContent();

    const out = to_string(decryptedContent);
    expect(out).toEqual(content);
  });

  it("Small file, no chunks", async () => {
    const collectionManager = etebase.getCollectionManager();
    const col = await collectionManager.create(colType, {}, "");

    const buf = randomBytesDeterministic(10, new Uint8Array(32));
    const content = JSON.stringify(buf);

    await col.setContent(content);

    await collectionManager.transaction(col);
    const decryptedContent = await col.getContent();

    const out = to_string(decryptedContent);
    expect(out).toEqual(content);
  });
});

I'll do a PR with a fix shortly

Let me know once the PR is ready and I'll take a look. I wonder if this also affects the Rust code (and thus every other library).

Did you mean to close this?

No! I didn't think merging the PR into a fork would close it.


bugfix of sentinel module

issue: https://github.com/alibaba/cloud-native-app-initializer/issues/87

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.burui seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Would you please sign the CLA first?


moving GoogleLifeSciencesExecutor to be executors/google_lifesciences.py

This is an extension to #382 to move the Google Life Sciences executor out of the current init.py in the executors folder and into it's own file. Since we only import the executor in scheduler.py we just need to update the one import there. I also did my best to remove un-used imports in both files.
Signed-off-by: vsoch<EMAIL_ADDRESS>

PR number 400! How cool is that!


_WD_UpdateDriver - better error handling

Pull request
Proposed changes
This PR is a fix for the issue catched by : n3wbie AutoIt forum member, and reported here.
Checklist
Put an x in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!
This is simply a reminder of what we are going to look for before merging your code.

[x] I have read and noticed the CODE OF CONDUCT document
[x] I have read and noticed the CONTRIBUTING document
[ ] I have added necessary documentation or screenshots (if appropriate)

Types of changes
Please check x the type of change your PR introduces:

[x] Bugfix (change which fixes an issue)
[ ] Feature (change which adds functionality)
[ ] Code style update (formatting, renaming)
[ ] Refactoring (functional, structural)
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
If $sInstallDir contains incorrect path for example / was used instead \ then _WD_UpdateDriver() function breaks the scripts on:
"Z:\!!!_SVN_AU3\UDF_Forum\Other_Members\Official_AutoIt_Forum\WebDriver\wd_helper.au3" (1433) : ==> The requested action with this object has failed.:
$oNameSpace_Install.CopyHere($FileItem, 20)
$oNameSpace_Install^ ERROR

What is the new behavior?
it properly reports error
_WD_UpdateDriver: Error = 18 : Extended = 13 : Result = False

Additional context
I work togeher with n3wbie to find out where the issue is.
n3wbie  after my help desribe the issue in this post:
https://www.autoitscript.com/forum/topic/205553-webdriver-udf-help-support-iii/?do=findComment&comment=1497385
I was able to replicate it on my side, and thus I was able to make a fix for this UDF function.
System under test
not related

Should use an enum for the @extended status codes. 😉

To master and thus to opera

Ok... will you be adding enums or didn't you want to leave it as-is for now.

Ok... will you be adding enums or didn't you want to leave it as-is for now.

As it is.
Or add this to task list as a post refactoring things to do before relase.
I need to think little more about.


change FFTW_URL to ftp source

closes #320

I tested locally and it works, however travis fails to get the fftw file from ftp. Any ideas?

very long time ago we had the same problems I belief. Their ftp server is probably not very stable. Or Travis blocks it. Or whatever... stick to http I guess

Ok, then I Will need to change fftw version as they removed 3.3.5 from http.

Can put it elsewhere, e.g. or website. You've done that before

it seems the file is back on http://www.fftw.org/fftw-3.3.5.tar.gz so I will close the PR.