Cannot start container "permission denied" on file in config folder

I'm getting this error no matter if I set the config to a local folder or a NFS share(both brand new dirs).

The file that throws the "Permission denied" error is always made by 0:0(root:root) when inspecting permissions, despite me setting the UID and GID to 3000:3002(nicksc:Docker). Manually changing the permission on the failing file does not fix the error.
root@truenas[/mnt/Alpha/Docker/jdownloader2/cfg]# ls -l
total 81
drwxrwx--- 2 nicksc Docker   3 Jan 25 00:18 laf
-rw------- 1 root   root   140 Jan 25 00:46 org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json
-rwxrwx--- 1 nicksc Docker  50 Jan 25 00:18 org.jdownloader.gui.jdtrayicon.TrayExtension.json
-rwxrwx--- 1 nicksc Docker  43 Jan 25 00:18 org.jdownloader.gui.notify.gui.BubbleNotifyConfig.json
-rwxrwx--- 1 nicksc Docker  54 Jan 25 00:18 org.jdownloader.gui.views.linkgrabber.addlinksdialog.LinkgrabberSettings.downloaddestinationhistory.json
-rwxrwx--- 1 nicksc Docker  52 Jan 25 00:18 org.jdownloader.gui.views.linkgrabber.addlinksdialog.LinkgrabberSettings.json
-rwxrwx--- 1 nicksc Docker  42 Jan 25 00:18 org.jdownloader.settings.GeneralSettings.json
-rwxrwx--- 1 nicksc Docker  36 Jan 25 00:18 org.jdownloader.settings.GraphicalUserInterfaceSettings.json

How do you create the container ?  Can you share your docker run command or compose file, etc ?

Docker compose. This is the entire file - except "" which indicates some info I've removed:
version: "3.8"
services:
jdownloader-2:
hostname: jdownloader2
container_name: jdownloader2
image: jlesage/jdownloader-2:v22.11.1
environment:
- DARK_MODE=1
- MYJDOWNLOADER_EMAIL=
- MYJDOWNLOADER_PASSWORD=****
- MYJDOWNLOADER_DEVICE_NAME=****
- TZ=Europe/Berlin
- LANG=en_US.UTF-8
- USER_ID=3000
- GROUP_ID=3002
ports:
- "5800:5800"
volumes:
- type: volume
source: jdownloader2-config
target: /config
volume:
nocopy: true
- type: volume
source: download
target: /output
volume:
nocopy: true
networks:
LAN:
ipv4_address: ****
restart: unless-stopped
volumes:
jdownloader2-config:
driver_opts:
type: nfs
o: addr=,nolock,soft,rw
device: :/mnt/Alpha/Docker/jdownloader2
download:
driver_opts:
type: nfs
o: addr=,nolock,soft,rw
device: :/mnt/Alpha/Download/downloads
networks:
LAN:
external: true

The error you get really seems to be related to NFS.  The NFS server should allow access from both root and from the user defined by USER_ID/GROUP_ID.  When starting, initialization is done by the root user.  Then the remaining actions are done by the non-root, defined user.
Also, are you sure you get the exact same error when not using NFS ?

I just can't see the error coming from NFS. I have 8 other containers that use the exact same permissions on the exact same shares, without issue.
But you are right, I'm not getting the same error when not using NFS. What I am getting is an error on the same file:
[cont-init   ] 55-jdownloader2.sh: jq: error: Could not open file /config/cfg/org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json: No such file or directory

Why is initialization done by root user?

Init scripts part of the startup of the container are run as root because they have to perform actions requiring root access.  For example, they setup Linux users and groups, initialize system configuration files, install packages, etc.
Currently, init scripts don't behave differently if they write to /config or to another part of the system.  One of the last init script makes  sure that all files under /config are owned by the user defined by USER_ID.

What NFS server are you using ?  And what is the configuration you are using to restrict user?

I'm using an NFS share mapped to /mnt/nfs/media/.
This is my docker-compose.yml - nothing fancy
version: '3'
services:
  jdownloader-2:
    container_name: jdownloader-2
    image: jlesage/jdownloader-2:latest
    ports:
      - "5800:5800"
      - "8297:8297" #added for custom httpAPI
    environment:
      - PUID=1000 # make sure this matches your user UID
      - PGID=1000 # make sure this matches your user GID
    volumes:
      - "./config:/config:rw"
      - "/mnt/nfs/media/jdl:/output:rw"
    restart: unless-stopped

@NickSChristiansen, I partially reproduced your issue by using a Linux NFS server with the following export:
/srv/nfs *(rw,sync,no_subtree_check,root_squash,insecure)

However, because any action done by root is denied, the startup of the container fails much sooner than in your case.  So I would still be interested in your NFS server configuration to make sure that a potential solution covers all cases.

Theis is my export settings, with 3000 being the "nicksc" user.
(sec=sys,rw,anonuid=3000,no_subtree_check)

Don't you need to also set anongid  to 3000 to match your Docker user ?
The root_squash option is enabled by default, meaning that requests from root are mapped to the configured anonymous user (i.e. the one set by anonuid /anongid).
Without anongid, the anonymous group should default to nogroup (65534).  This is what I see from my side.

With this export (1000 being my user that I also use for USER_ID / GROUP_ID):
/srv/nfs *(sec=sys,rw,anonuid=1000,anongid=1000,no_subtree_check)

I only get this message, which doesn't prevent the container from loading:
[cont-init   ] 55-jdownloader2.sh: mv: can't preserve ownership of '/config/cfg/org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json': Operation not permitted

On my TrueNAS NFS share, the group defaults to root evidently, as the file who's permission are taken over by root user are also taken over by the root group(0:0).
Is your user(1000) part of the root group? Or has root-like access? Because "nicksc" is only part of groups I created. No root nor admin groups.
Adding anongid=3002 gets me the same error as previously:
[cont-init   ] 55-jdownloader2.sh: jq: error: Could not open file /config/cfg/org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json: Permission denied

On my TrueNAS NFS share, the group defaults to root evidently, as the file who's permission are taken over by root user are also taken over by the root group(0:0).

Adding anongid=3002 gets me the same error as previously:

Yeah this is strange.  According to your export config, you should never have files owned by root in the NFS share.
Looks like the export config doesn't do anything ?

Is your user(1000) part of the root group? Or has root-like access? Because "nicksc" is only part of groups I created. No root nor admin groups.

No, this is a standard user that is only part of group 1000.

Tried to reproduce with TrueNAS without success.
I installed TrueNAS in a VM.  A created dummy pool, a user test (1000/1000) and enabled NFS with the following settings:

On the client machine, I mounted the NFS share like this:
sudo mount -o nolock,soft,rw <IP_ADDRESS>:/mnt/MyPool/NFSShare /mnt/local_nfs3

Then I create and start the container:
docker run --rm -ti -e USER_ID=1000 -e GROUP_ID=1000 -e<EMAIL_ADDRESS>-e MYJDOWNLOADER_PASSWORD=test -v /mnt/local_nfs3:/config:rw jlesage/jdownloader-2

Also, make sure that on the server, the directory exposed to NFS is owned by 3000:3002(nicksc:Docker).

@crbon, not sure where PUID and PGID are coming from, both they are not used by this container. See https://github.com/jlesage/docker-jdownloader-2#environment-variables.

Mistake on my end. Must have come across when I switched from another docker image

The dataset, and the permissions:

The share:

And now the export looks like this with the group included:
(sec=sys,rw,anonuid=3000,anongid=3002,no_subtree_check)

The mount is created by the docker compose file, which is the same as the one I posted before, but here it again just for good measure:
version: "3.8"
services:
  jdownloader-2:
    hostname: jdownloader2
    container_name: jdownloader2
    image: jlesage/jdownloader-2:latest
    environment:
      - DARK_MODE=1
      - MYJDOWNLOADER_EMAIL=****
      - MYJDOWNLOADER_PASSWORD=****
      - MYJDOWNLOADER_DEVICE_NAME=****
      - TZ=Europe/Berlin
      - LANG=en_US.UTF-8
      - USER_ID=3000
      - GROUP_ID=3002
    ports:
      - "5800:5800"
    volumes:
      - type: volume
        source: jdownloader2-config
        target: /config
        volume:
          nocopy: true
      - type: volume
        source: download
        target: /output
        volume:
          nocopy: true
    networks:
      LAN:
        ipv4_address: ****
    restart: unless-stopped
volumes:
  jdownloader2-config:
    driver_opts:
      type: nfs
      o: addr=****,nolock,soft,rw
      device: :/mnt/Alpha/Docker/jdownloader2
  download:
    driver_opts:
      type: nfs
      o: addr=****,nolock,soft,rw
      device: :/mnt/Alpha/Download/downloads
networks:
  LAN:
    external: true

I've also tried creating the mounts outside of the compose file, but I get the same result.

And ls -ld /mnt/Alpha/Docker (server/TrueNAS side) shows the correct ownership?

Yep

Whoops, sorry!
I stripped the ACL's and forgot to reapply them... D'oh!

Here is the permission, after the ACLs are reapplied:

... Though I have no idea who user 770 is, as that user doesn't exist on TrueNAS...

Ok and now that this is fixed, do you still have issue with the container not starting ?  Make sure that all files have the correct owner before starting it...

Humm, there is something wrong that I cannot identify.
During the container initialization, there are other files written to /config as root.  So I'm not sure why /config/cfg/org.jdownloader.api.myjdownloader.MyJDownloaderSettings.json is more problematic than other files.  The NFS server config is good and should translate all requests done by root to the correct user.  If on the server side you still see the file as owned by root, then maybe there is an active ACL somewhere?
Could you try with another NFS share ?

So I tried making a new dataset, applying nicksc:Docker with rwx and got the same error.
Then I tried making a pool, with a new dataset and applying nicksc:Docker with rwx and now it works... (╯°□°)╯︵ ┻━┻
Sorry for the confusion. The issue is clearly on my end - maybe there was an ACL on the pool level overwritting the new ones I set on the dataset or something. I honestly have no idea. I'll nuke the pool, recreate it and hope that clears the issue.

I have a similar error on start after moving to from linux/amd64 to linux/arm64:
Openbox-Message: 16:11:29.496: Unable to make directory '/config/xdg/cache/openbox': Permission denied

All files generated so far in config volume have root:root as owner, I think something is messed up there...

Are you also using a NFS share for the config folder ?

I finally figured out what was causing the problem for me:
When re-using existing certificates by mounting them read-only in volumes like this:
volumes:
  - "$CERT_PATH/key.pem:/config/certs/web-privkey.pem:ro"
  - "$CERT_PATH/fullchain.pem:/config/certs/web-fullchain.pem:ro"

It causes conflicts when docker-compose tries to take ownership as it is read-only.
This problem could be bypassed by providing TAKE_CONFIG_OWNERSHIP=0 as environment variable.
But if starting docker-compose with sudo it means the data-volume is created and owned by root.
This causes the error as described above.
A workaround is to stop the service when the error occurs and take ownership of the data-volume with the current user:
sudo chown -R $(id -u):$(id -g) <path/to/data-volume>
// or
sudo chown -R $(whoami):$(whoami) <path/to/data-volume>
// e.g. on ubuntu
sudo chown -R ubuntu:ubuntu <path/to/data-volume>

Afterwards restart the service and the setup-process should work and continue.
I finally did fix the issue by running the service with domain-mapping behind a nginx-reverse proxy. It allows me to disable secure-connection by removing SECURE_CONNECTION=1 from docker-compose.yml as Nginx will handle SSL, my config:
# Connection upgrade for reverse proxy
map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}

# web access to jDownloader2
server {
  listen 80;
  server_name <sub.domain.org>;

  location / {
    proxy_pass http://jdownloader:5800;
  }

  location /websockify {
    proxy_pass http://jdownloader:5800;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_read_timeout 86400;
  }
}


Add Weekly C# Digest

Newsletters/Weekly C# Digest - Weekly C# Digest
Weekly email newsletter with manually curated top 5 links from the .NET community.

I like it, but I don't know if it fits with "A collection of awesome .NET libraries, tools, frameworks, and software.".
Let's wait a little and see what other members of the community think

awesome-ruby has a resource section, so would something like that work?

vote for inclusion in the list, in "Resources" section, for example.

Vote for "Resources" section

Ok Resources have it. @jakubgarfield if you could update the PR to reflect this, I'll happily merge it ;)

thanks @pleb, I amended the previous commit to keep the git log tidy.


License

I just wanted to let you know that I have used your code to create a not very pretty but practical online version of your scraper here: http://tech189.duckdns.org/memrise/
I would like to check whether I have attributed you sufficiently.
Thanks!

No problem, I've added your real name.

all good!
Radomirs Cirskis MCDBA, MCAD C#, MCSD .NET C#, ZCE PHP5, MCSD VB6 ...
M: +64 221 221 442 | E<EMAIL_ADDRESS><EMAIL_ADDRESS>[image: View my profile on LinkedIn] http://nz.linkedin.com/in/nad2000
On Sun, May 6, 2018 at 1:14 AM, tech189<EMAIL_ADDRESS>wrote:

Closed #1 https://github.com/nad2000/memrise-scraper/issues/1.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nad2000/memrise-scraper/issues/1#event-1611330375,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK0ckOFWcDwtRE4RT6C5hvg-O05tQoVks5tvc_qgaJpZM4Trwkt
.


fix of darwin + chrome-remote situation

reverting unwanted change of behavior on osx + remote chrome reported by r-roos

@filiprichtarik @luciano-renzi I have updated the branch with the suggested update I made earlier. Please review

this nut is for luciano to crack
i understand your code, i understand even why chrome-remote does not trigger the condition ('chrome'==browser_definition['name']
is in this case 'chrome'=='chrome-remote' and returns false as expected)
but i have no idea how it works with remote browsers
and for the point of removing the workaround when 2.44 is out, we cannot
we can only change the logic so it'll check chromedriver version too, otherwise everyone who doesn't have latest driver will have the issue back

Hi @filiprichtarik your remark about not wanting to remove the work around triggered to look a bit closer to this issue. If you look at the current patch it is also silly all other version prior to driver 2.4.3 and chrome 70 are affected.
Regarding looking about more into detail. it seem we can retrieve a lot of information from the driver.capabilities, enough in fact to specifically target release version where we want to skip the maximize window feature.
Some debugging example of running chromedriver 2.4.3 & chrome 70.

Now when using a remote driver

I propose we rework the workaround to specifically target the affected versions of chromedriver & chrome

As @r-roos points out, the instance of the WebDriver has a dictionary of the capabilities used by it. This should be used here to stop maximizing the browser when it's running on mac locally or on a mac node regardless of the OS running Golem.
I tested the following condition and it looks good to me:
is_mac = 'mac' in driver.capabilities.get('platform', '').lower()
if not ('chrome' in browser_definition['name'] and is_mac):
    driver.maximize_window()

We can add a version check once this is fixed. In the meantime, there are alternatives to maximizing Chrome. I'll add a comment in the ticket explaining.

Added my fix :-) It's tested in Chrome remote in and a macOS node. It's not tested in macOS local
@r-roos I'll leave this open in case you want to test that scenario

@luciano-renzi your latest change seem to work well.
Tested

Chrome local on a mac -> no window maximizing
chrome-remote & chrome_zalenium of the settings posted earlier, which will maximize the window


fix: More REST transport fixes

Generate an empty unit test  method even if the method is not supported in a particular transport. Bazel fails test execution, if the test class has no @Test methods. In case if there is a service with only unsupported methods, and we do not generate unit tests for those, we would get an empty unit test, which will fail execution in our automatic bazel build pipeline.

For fields of google.protobuf.Value type set an actual value for it (to avoid non-set vs null value differences after json serialization/deserializaiton roudtrip). This looks like an issue in protobuf support of google.protobuf.Value type in JSON and not specific to GAPIC.

@blakeli0 PTAL, this is the last PR I need to submit before rolling our regapic


AIML Integration

Hi everyone,
Great tool!
I was wondering if there was any consideration for adding in the ability to use AIML files?
I guess these can be converted to JSON files but that seems like a big work around.
Thanks!

This is a great idea. I would be more than happy to add direct support for this. I will need to look into the AIML spec a bit fist as it looks like they support a few things like wildcard input which ChatterBot currently does not support.

Awesome!
I have been thinking about this issue with the wildcards and would be very interested in hearing about the approach you come up with. I feel like it may be similar to your ClosetMatchAdapter class but probably a lot more complicated. I was even thinking that each topic can get a class like TimeLogicAdapter with some NaiveBayesClassifier but that is probably overkill.
Also, a lot of the AIML files (https://github.com/drwallace/aiml-en-us-foundation-alice) have a notion of saved state. For example, you can tell the bot your name and then it saves that fact and can recall it later in the conversation. Is something like this supported in the current code?
BTW, I have been poking around a bit and found an open source AIML parser and bot: https://github.com/creatorrr/pyAIML
They have a pretty complex parser and string matcher in the files AimlParser.py and PatternMgr.py

Hi,
There is another project (https://github.com/cosimoiaia/pyAiml-2.0) is in very early stages , for AIML 2.0 it is a porting of program-AB (JAVA).
With pyAIML, I believe can be treated like  any other logic adapter.
What you think ?

@davizucon Looks promising, definitely something to look in to.

@davizucon
Yes, it was pretty easy to use aiml as a logic adapter. I used the AIML interpreter here: https://github.com/creatorrr/pyAIML, which is AIML 1.0.1 standard. It was tricky to calculate the confidence level of the reply  though, as it is not part of the AIML standard.

@gopiwh0 did you go any further with integration?

from future import unicode_literals
from chatterbot.logic import LogicAdapter
from chatterbot.conversation import Statement
import aiml
class AIMLEvaluation(LogicAdapter):
"""
"""

def __init__(self, **kwargs):
    from nltk import NaiveBayesClassifier

    self.kernel = aiml.Kernel()
    self.kernel.learn("standard/std-65percent.aiml")

def process(self, statement):
    from chatterbot.conversation import Statement

    responseData = self.kernel.respond(statement.text.lower())
    response = Statement(responseData)

    response.confidence = 1
    return response

I've was reminded about AIML recently and I just wanted to record a brief though about a possible direction for supporting it in ChatterBot.

It would be easy to add a field to mark Statements that contain AIML.
A filter would have to be created to control when AIML responses are used.
I'm not certain about how the AIML statements should be evaluated, but I'm fairly sure a custom logic adapter would be need for this so that the AIML responses could be processed into statement text.

Did anyone come up with a direct method for learning custom AIML files?


fix(chat): add messages for external files sharing errors

Description:

add error message for publish action
add error message for share action

Issues:

Issue #1984

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Automate catalog push and remove it from manual release steps

(I only partially tested, need to run an actual release to fully validate)

thanks, let's test this with rc4

/approve


incorrect export of locals

if there is a ch in local class like: :local .gсh  - loader will strip all after ch,
so {g: 'generatedClassName'} will be exported
strange stuff.. :)
:local(.withSearсhButton)
  :local(.allOptions)
    display none

:local(.withSearсhButton)
  color red

:local(.сhButton)
  color green

outputs
Object {withSear: "app-main-components-SearchBar-gg---withSear---psEQw", allOptions: "app-main-components-SearchBar-gg---allOptions---1UsCx"}
config:
css-loader?minimize=false&localIdentName=[path][name]---[local]---[hash:base64:5]
tried versions 0.15.3, 0.15.5

I first thought: what a weird issue... And I could reproduce it when copying your .withSearсhButton class, but it's fine when I type .withSearchButton ;).
The solution: Your с is not an ASCII c. It just looks like one... No idea how you typed it, but try to use the c key of your keyboard instead :smile:
"с".charCodeAt(0)
> 1089
"c".charCodeAt(0)
> 99

oh, this is some IDE bug imo, i typed a lot of variants. This is russian C, he-he.
thanks :)


[adding] adr to generate user jwt inside the client using scoped keys

Signed-off-by: Matthias Hanel<EMAIL_ADDRESS>

Need go run main.go > README.md

LGTM


Updating OAuthClient API based on latest service swagger

Updated the TokenAPI.json swagger file, and generated (for the first time), the autorest clients and supporting classes for this swagger. Then I updated the tests and BotFrameworkAdapter to use these methods.
I ran the unit tests and also did manual testing against production DirectLine:
-GetToken
-SignIn flow (with and without the magic code)
-SignOut
-GetAadTokens

I've followed up with @Jeffders to figure out what to do with this PR.


Raise MSRV to 1.79.

I need to raise the MSRV to 1.79, can this be completed to testing?

Summary by CodeRabbit

Chores

Updated GitHub workflow to set up Rust with a specific version before the build step.
Updated required Rust version from 1.74 to 1.79 in the Cargo.toml file.

It looks like you're doing okay!


trimmomatic needs MINLEN parameter

I'm running into a few cases where trimmomatic produces trimmed reads that are just a few bases long. Those can then map thousands or even tens of thousands times to contigs assembled by Trinity. In turn, that means that the bowtie2 quantification step is unable to complete in a reasonable amount of time since it is using -a. The solution is to add MINLEN:36 (I picked an arbitrary number) to the call to trimmomatic.

Thank you for pointing this out. I will include this in the next release.


Track context count

Provide a visual cue to indicate how long someone has been holding context in a lane.

This PR introduces "floating" as a way of visualizing who has been in the lane longer.  The longer you are in the lane, the less you float.

Closing since there hasn't been movement on this in a long time.


Stop injecting 'workspace' in the hawtio-ui tree component

The workspace resource from hawtio-jmx is being injected in the hawtio-ui tree component with the intention of being notified about node selections. The correct way for hawtio-jmx to be notified about node selections is via the onSelect callback.

I'll try to fix this one.

Should be fixed by now.


cmd/go: use slice expression a[x : x] where cap(a) is x should cause panic

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

$ go version
1.12.3

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/cholerae/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/cholerae/Documents/gopath"
GOPROXY=""
GORACE=""
GOROOT="/Users/cholerae/Documents/gopath/go"
GOTMPDIR=""
GOTOOLDIR="/Users/cholerae/Documents/gopath/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/cholerae/Documents/gocode/ByteGraph/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/1q/bn5v_zpd5qzc4dlg3bbp2psm0000gn/T/go-build647264484=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

https://play.golang.org/p/XT4xCSpIylL
What did you expect to see?
Panic at line 9.
What did you see instead?
Panic at line 10.

Working as intended. If cap(x) is N, then the slice expression [0:N] gives the whole slice since the indexing is open on the right. [N:N] is just a special case that slices off the empty slice at the end.


Half of the earth

Sorry the community is too slowly to open.
My project is rely on the terrain,
but I use terrainProvider.readyPromise.then(function(value){console.log(value)}),
also cann't solve the problem like below picture.
Any help, thank you.
Cesium Version 1.78

I meet the same question. Have you fix it?


Prettier Warning/Errors

https://buildkite.com/seek/hirer-contracts-api/builds/1972#
Recently bumped up an API to Skuba 3.15.2. We got this error when running yarn lint.

Re-running it again worked however we get left with some warnings:
(node:30) Warning: File descriptor 32 closed but not opened in unmanaged mode
--
  | (Use `node --trace-warnings ...` to show where the warning was created)
  | Prettier │ Processed 85 files in 10.27s.

Ran --trace-warnings on local and got the following:
➜ node --trace-warnings node_modules/.bin/skuba lint
(node:33523) Warning: File descriptor 43 closed but not opened in unmanaged mode
    at Object.closeSync (node:fs:530:11)
    at Object.closeSync (/Users/schung/repos/hirer-contracts-api/node_modules/graceful-fs/graceful-fs.js:74:20)
    at getInterpreter (/Users/schung/repos/hirer-contracts-api/node_modules/prettier/index.js:12674:30)
    at Object.inferParser (/Users/schung/repos/hirer-contracts-api/node_modules/prettier/index.js:12691:25)
    at getFileParser (/Users/schung/repos/hirer-contracts-api/node_modules/prettier/index.js:25444:36)
    at _getFileInfo (/Users/schung/repos/hirer-contracts-api/node_modules/prettier/index.js:25484:29)
    at getFileInfo (/Users/schung/repos/hirer-contracts-api/node_modules/prettier/index.js:25407:10)
    at async Promise.all (index 2)

Ooh, that's a very useful stack trace. Looks like something is going wrong here: https://github.com/seek-oss/skuba/blob/v3.15.2/src/cli/adapter/prettier.ts#L126-L127
Is it possible to pinpoint whether a particular file is causing the issue with yarn lint --debug?

Comes from this file in Prettier 🤔

Not sure if it's any particular file, when I deleted buildkite.yml it would show up on another file so it may just be an asynchronous warning.

On indie-graphql-server this gets triggered by .github/CODEOWNERS and no other file. I’m not sure if this is related to the EBADFs that occasionally break its build.

^ is pretty bizarre. The indie-graphql-server warning is indeed triggered exclusively on .github/CODEOWNERS, and only when running the relevant Prettier/graceful-fs code in a worker thread.


"List" should be a default option in the insert menu

Since that that cannot be user-specified, we should provide it and add it to the bottom of his insert menu, above "More"

This is non-trivial, because the value parser used in the descriptor file parsing recognizes the map as ATTRIBUTE_OTHER_JAVASCRIPT and not JSX_MAP_EXPRESSION

I'm gonna unblock this


App name as label

Instead of putting it in the metric name, make the app a label.

Sorry for the delay reviewing this, I'm seeing some missing metrics when I test these changes and I'm trying to work out if that's the fault of these changes or not.
One of the metrics that's missing in my tests, for example, is host_count, which appears in the application_summary part of the app list, rather than in the main metric data (see the application_list.json file in _testing).

On 04/08/15 18:00, James Findley wrote:

Thanks for doing this, and sorry it's taken so long, I've found the root
of my issues and they were unrelated, as it turns out.

Oh, thanks!
Sorry for not replying to your earlier mail, I just have had no time for
verifying that!
--
Martín Ferrari (Tincho)


[New game]: Hedgehog Havoc

🎮 Game Request
Game logic and basic description : The player takes control of a fearless bunny on a mission to gather as many delicious carrots as possible. But beware! The field is crawling with prickly hedgehogs, determined to stop your veggie quest.
Point down the features
Game points : The longer the player avoids those hedgehogs, the FASTER their score grows! Every safe second earns a bigger score boost!
 Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


add support for editorconfig

instead of requiring explicit configuration for indentation, support editorconfig
https://editorconfig.org
there is a vscode editor config plugin, I'm not certain whether it's possible to ask it for its settings if it's installed, if it is I'd be ok with that.

Hi @xenoterracide, have you tried JS/TS Import/Export Sorter which does exactly what you want?

I have not... but does it work with the eslint rule as well? we are using eslint, prettier, and editorconfig in conjunction with each other.


onSelect handler not triggering in V4.0.0

Describe the bug
Since V4.0.0 when selecting a payment option the onSelect event is not being triggered.
To Reproduce
Steps to reproduce the behavior:

Setup a Dropin component with an onSelect handler.
Open up your browser and go to the payment panel.
Click on a payment option (switch from iDeal to Credit Card for example).
See if the onSelect handler is being called.

Expected behaviour
I expect the onSelect handler to be called.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop

OS: MacOS 11.2.2
Browser: Chrome
Version: 88.0.4324.192

Additional context
It did work before migrating to V4.0.0, I might have missed something in the docs, but I see it's still mentioned here: https://docs.adyen.com/online-payments/drop-in-web#step-2-add-drop-in

Hi @PizzaPete,
Thanks for reaching! In v4.0.0, we've reorganized a bit how to configure components. In this case, as this is an exclusive event of Drop-in, we now expect it on the Drop-in configuration object, it would look like this:
checkout.create('dropin', {
  onSelect: () => {}, // Drop-in configuration only has props related to itself, like the onSelect event.
});

Please check our migration guide to v4.0.0 to know more about these changes, hope this helps!

@marcperez thanks for your reply.
I missed the migration guide, thanks for pointing that out. Got the onSelect working now.

Great! Happy it works now.
We've just updated our release notes here on Github with a link to the migration guide so it's a bit easier to find 👍

hi @marcperez I stumbled upon this because we're working on our migration as well. I noticed that onSelect only seems to fire for the selection of the parent payment method itself (e.g. ideal / credit card / paypal etc.) but not when the actual choice of bank (e.g. abn / ing etc.) changes within the ideal payment method. Am I missing something? This used to work before 4.0.0


Pass Domain through on EKS Provision for Route53 Permissions

When we provision an EKS cluster, we create a Route53NodeInstancePolicy in our cloudformation script that allows full access from the node to administer the route53 records.
See: https://github.com/crossplaneio/crossplane/blob/3bc975537fe11b104779c0deac5d57ed8bf53bd2/pkg/clients/aws/eks/eks.go#L252
Note configuration notes here:
https://github.com/kubernetes-incubator/external-dns/blob/master/docs/tutorials/aws.md
We should improve the security model by limiting to the domain that cluster should operate on:

Pass domain name through from claim
Resolve domain name to actual hosted zone id
Pass hosted zone id to cloudformation script in eks.go client to limit scope of permissions in aws role.

Let us revisit EKS design, specifically as it pertains to components: master, workers, security, and authz.
The initial (first glance) though, I don't think we should assume that all EKS clusters will be configured with External-DNS by default, hence, if this issue is driven primarily by this use case then I think we should carefully consider ramifications. I am not opposed to entertaining the possibilities of provisioning all EKS clusters (or all managed Kubernetes Clusters) with External-DNS support by default, but I think this topic warrants a wider discussion scope.

Fully agree, by configurable in this ticket I would expect that no
permission would be granted to manage any domain if the domain wasn’t set
and that domain would be optional.
On Fri, May 24, 2019 at 1:01 AM Illya Chekrygin<EMAIL_ADDRESS>wrote:

Let us revisit EKS design, specifically as it pertains to components:
master, workers, security, and authz.
The initial (first glance) though, I don't think we should assume that all
EKS clusters will be configured with External-DNS by default, hence, if
this issue is driven primarily by this use case then I think we should
carefully consider ramifications. I am not opposed to entertaining the
possibilities of provisioning all EKS clusters (or all managed Kubernetes
Clusters) with External-DNS support by default, but I think this topic
warrants a wider discussion scope.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/crossplaneio/crossplane/issues/491?email_source=notifications&email_token=AABPWI2UITIOC3QQCSLQFCTPW6OFZA5CNFSM4HOBEJAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWEO3NI#issuecomment-495513013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABPWI5PBVJIL4436VAANP3PW6OFZANCNFSM4HOBEJAA
.


Remove ssl_cert_loader.  Certifier is more complete version.

Yes, this was the plan when we started work on the Certifier plugin.

I'm ok with this, not sure if it's necessary to have a discussion on dev@ or Summit first? I don't know if anyone is actually using this plugin...


Can't run clasp run since there is no way to generate local Oauth Credentials

Expected Behavior
Documentation describes how to generate OAuth credentials to allow clasp run to work properly
Actual Behavior

Do not see Apps Script API as an option when generating OAuth keys in the Google Cloud Console
I've followed documentation, and the steps outlined here

Steps to Reproduce the Problem

Enable Apps Script API: https://console.cloud.google.com/marketplace/product/google/script.googleapis.com
Create a new OAuth Credential: https://console.cloud.google.com/apis/credentials/oauthclient
Look in the dropdown menu for the "Apps Script API" type

Specifications

Node version (node -v): 16.13.1
Version (clasp -v): 2.4.1
OS (Mac/Linux/Windows): Mac M1

i was following the wrong docs. correct docs are here: https://github.com/google/clasp/blob/master/docs/run.md#setup-instructions


jwt_authn: add a fuzz test for http filter jwt_authn

Signed-off-by: Wayne Zhang<EMAIL_ADDRESS>Add a fuzz test.   It is for https://github.com/envoyproxy/envoy/pull/23617
Risk Level: None
Testing:  Add fuzz tests
Docs Changes: None
Release Notes:  None

/retest


Gitlab JUNIT parsing problems

A failed testcase is overlooked by gitlab.
This is due to https://gitlab.com/gitlab-org/gitlab-ce/issues/51087 as they currently ignore the errors tag.

Fixed on gitlab's side at https://gitlab.com/gitlab-org/gitlab/issues/23992.


[JSG] Use SetAccessorProperty() in registerReadonlyPrototypeProperty()

This mirrors the approach used for registerPrototypeProperty().

Merging this – there were no failing upstream tests and the updated V8 version looks stable.


Add front-end assets support

There should be support for functions like:

[ ] uglifyjs()
[ ] jshint()
[ ] uglifycss()
[ ] unsass()
[ ] unless()

Hi,
i'm not sure backend languages like PHP should deal with front end resources,
let's tools like grunt or bower actualy "do the job".
I see a lot of usages for a PHP task runner, like:

[ ] launch the tests
[ ] check for the quality & security: sensiolabs-security-tool
[ ] apply some tools for esthetics and standards: php-cs-fixer ...

Take a look at the lot of commands that Symfony framework provide: the majority should be removed and be moved inside a task runner like Fred or dum (my task runner not yet released).
What do you think ?

Hi,
i'm not sure backend languages like PHP should deal with front end resources,
let's tools like grunt or bower actualy "do the job".
I see a lot of usages for a PHP task runner, like:

[ ] launch the tests
[ ] check for the quality & security: sensiolabs-security-tool
[ ] apply some tools for esthetics and standards: php-cs-fixer ...

Take a look at the lot of commands that Symfony framework provide: the majority should be removed and be moved inside a task runner like Fred or dum (my task runner not yet released).
What do you think ?

I see 2 use cases for Fred. One is the front-end stuff (I don't want people to have to install nodejs for that), this replace Assetic. The other is what you mention, replacing lots of commands from the frameworkbundle which don't belong there. I'm already working on a FredBundle, to provide this.

I see 2 use cases for Fred. One is the front-end stuff (I don't want people to have to install nodejs for that), this replace Assetic. The other is what you mention, replacing lots of commands from the frameworkbundle which don't belong there. I'm already working on a FredBundle, to provide this.

Ok, this sounds good to me :+1:

Ok, this sounds good to me :+1:

What's your plans for implements this functions ?

@romqin I'm still a bit thinking about the scope of Fred. I created it for doing simple tasks, like creating a new blog post for my static website. However, I want it to be usable with Symfony too.
As it's a PHP runner, I agree with @mickaelandrieu that it should also support common PHP tasks. The way I do PHPspec at the moment is executing the PHPspec "binary" for each file in the iterator. What I'm thinking about is creating some sort of BufferIterator for things like this, it would save each file path in an array and only execute the callback for the last array item. This can then run the test and return a new iterator for the result. However, I'm not sure yet this is possible with iterators (as you need to go from n items (the test files) to 1 (the result)).
The result will then be something like:
$fred->task('test', function () use ($fred) {

    $fred->load(Finder::create()->files()->names('*Spec.php')->in(__DIR__.'/specs'))
        ->then(phpspec())
        ->dist(phpspecReport(STDOUT));

});

@mickaelandrieu A simple counter-example to your statement about limiting fred to php tasks only:
If you take grunt (for example), you have plugins for both sass and imagemagick. However, none of these tools are actually made in JS. They are, respectively, a ruby library and a compiled binary file.
Another example: Even though nodejs is a javascript interpreter, its main focus is to run backend tasks (it includes a servlet, i/o management, etc.). I don't see how this differs to PHP in any way.

Hi,
agree to @csarrazi point, I don't say we "never" should use fred for this kind of  frontend stuff, I say many others tools exists and are very great, so why re-invent the wheel ?
I like a lot project like Jolicode Symfony generator because they use the best tool for each use case, without regard of the technology: what do you think of this kind of project ?


[CI] Changes to docker file of frontend

Description
CI Workflow added namely, docker-image.yml runs the automation for command:
docker-compose -f docker-compose.dev.yml build

Fixes #87
Type of Change:

Testing CI/CD

Bugs: N.A.
New Feature: :heavy_check_mark:
Documentation: N.A.

How Has This Been Tested?

Checklist:

[x] My PR follows the style guidelines of this project
[ ] I have performed a self-review of my own code or materials
[x] I have commented my code or provided relevant documentation, particularly in hard-to-understand areas
[ ] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

Thanks @amino19 for contributing Formica!


Refactoring of IconBrandColor - nps.today certified connector

Refactored IconBrandColor
added .venv to .gitignore

When submitting a connector, please check the following conditions for your PR.

[ X] I attest that the connector works and I verified by deploying and testing all the operations.
[ X] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[X ] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a logo.

Hi @sriyen-msft - anything new?

Hi @sriyen-msft - anything new?

Just saw your PR at my repo. File has been reverted. Sorry for the misunderstanding, the "Outdated" tag confused me.


Remove v1alpha1 in v0.31.0

v1alpha1 version of the descheduling policy has been deprecated for many releases now. It's time to remove it from the code base and focus on v1alpha3.
Removal announced on sig-scheduling dev list: https://groups.google.com/g/kubernetes-sig-scheduling/c/OyFjkDntuhg/m/GVjD4gpaBAAJ?utm_medium=email&utm_source=footer
1.30 k8s release scheduled for Wednesday 17th April 2024: https://www.kubernetes.dev/resources/release/#summary
TODO:

[ ] - remove v1alpha1 types from the code
[ ] - remove v1alpha1 -> v1alpha2 conversion code
[ ] - remove any mention of v1alpha1 type from the documentation (probably just mentioning v1alpha1 was removed in 0.31.0)
[ ] - announce v1alpha1 removal on sig-scheduling dev list + descheduler changelogs

fyi- Warning should land in v0.30 and should be noted in the release notes: https://github.com/kubernetes-sigs/descheduler/pull/1337

/remove-lifecycle stale


X Ray Image Query Missing Test Cases

Two additional kinds of tests ought to be added to the X Ray Image Query:
Testing output messages when sending results to an output directory
After the X Ray Image Query runs, it gives an output message saying where it put your files and what their names are. However, inside the test suite, this output message only appears when the output directory is set to the current directory. Why this happens should be discovered and addressed, and new tests should be added for this behavior.
Testing catching conduit error when writing blueprint output
Conduit throws an exception when writing fails. An easy way to reproduce this is to ask conduit to write to a directory with read only permissions. However, using python's OS library inside the test suite to set directory permissions causes the test suite to crash. The cause of this should be discovered and addressed, and new tests should be added for this behavior.

Ok, I was able to get the test suite to create directory /tmp/baddir, but the silent failing issue is still a problem.

Sunspots must have caused my first issue; they seem to mostly be working now?

See #17846 for more information about Testing catching conduit error when writing blueprint output

The first issue occurred because the test suite wrote to a large absolute path, and the x ray query would write that path to a small buffer, causing a SEGFAULT.


How to ignore library text colors?

Thank you!

android:tag=":aesthetic_ignore" doesn't work?

Gradle dependent library can not be modified, only as a module import to edit it?

https://github.com/afollestad/aesthetic#ignoring-views


Messages per second from Custom listener [5685]

Is it possible to get the number of messages received per second on a given topic using the custom listener.
--
Jimmy

Each subscriber has a single topic associated; thus, the SubscriberListener interface provided on creation will receive a:
    virtual void onNewDataMessage(Subscriber* sub)

callback each time a message on this topic is received from whatever publishers this subscriber has discovered.
There is no delay between message reception and the corresponding callback. If you want to calculate the rate of reception I'm afraid you will have to do the math yourself by generating a collection of reception times.

I was hoping I can get this using the EDP Reader which lists the number of publisher and subscribers that are active per topic. Then it can be used for diagnostics - I already have something similar in my application.

EDP only can help you reporting how many publishers and subscribers deal with a given topic. It doesn't provide any user traffic info. You don't need EDP to know the publisher associated with a given sample.
When you create a subscriber for a given topic it matches all publishers which share topic with him (and have compatible QoS). Then you are forced to use either:
bool Subscriber::readNextData(void* data,SampleInfo_t* info)
bool Subscriber::takeNextData(void* data,SampleInfo_t* info)

to retrieve the samples. In both cases the info argument sample_identity member provides you the GUID_t from this sample publisher. That allows you to calculate the message rate for each individual publisher of the topic of interest.


Need NPM release?

I noticed 2.0.1 is tagged and contains the notifyPropertyChange fixes, however npm still lists 1.0.14 as the current release.
Can this be released? Also you may want to add ember-notify-property-change-polyfill to dependencies to maintain compatibility with ember < 3.1.
https://emberjs.com/deprecations/v3.x/#toc_use-notifypropertychange-instead-of-propertywillchange-and-propertydidchange

sorry about this but there has been a change from paper-input-mask to ember-paper-input-mask and you would need to use the new NPM name @lucacorti


Golang build tags

It seems there is no way to specify build tags for Go.
Would you be open to a PR to add this capability? If so, would GOOGLE_GOTAGS work for the env var name?

I haven't used Go build tags in the past so this isn't something I am very familiar with. But, I think this should already be supported with the GOOGLE_GOGCFLAGS  env var: https://cloud.devsite.corp.google.com/docs/buildpacks/go#compilation_flags
I think you would need to do something like:
pack build sample-go --builder=gcr.io/buildpacks/builder \
  --env GOOGLE_GOGCFLAGS="-tags=foobar"

@matthewrobertson thanks for your response.
GOOGLE_GOGCFLAGS is used for -gcflags which is limited to the go tool compile options.
However, I just saw in the docs that GOFLAGS (without a GOOGLE_ prefix) is supported so I think that would work. I actually ended up switching to manual builds for better control / smaller images but hopefully this would help anyone interested in using buildpacks with build tags in the future.


Crossref Published dates represented inconsitently across work types

Published date parsing seems incocnistent across different Crossref content types:
For example, JournalArticles always return the Published date as a YYYY-MM-DD string.
However other contents seem to also include trailing time info. Here are examples:

10.6019/pxd046288 (Database)
10.1007/10390457_56 (BookChapter)
10.7717/peerj.3953/table-1 (Component)
DOI:10.15760/honors.1246 (Dissertation)
10.1109/vlsic.2004.1346548 (ProceedingsArticle)

In each case the published date  seems to include trailing time info as well.
For example, with the last item in the above list:
commonmeta convert --from crossref "10.1109/vlsic.2004.1346548"

results in:
{
  "id": "https://doi.org/10.1109/vlsic.2004.1346548",
  "type": "ProceedingsArticle",
  "container": {
    "type": "Proceedings",
    "title": "2004 Symposium on VLSI Circuits. Digest of Technical Papers (IEEE Cat. No.04CH37525)"
  },
  "contributors": [
    {
      "type": "Person",
      "givenName": "J.W.",
      "familyName": "Lee",
      "contributorRoles": [
        "Author"
      ]
    },
    {
      "type": "Person",
      "familyName": "Daihyun Lim",
      "contributorRoles": [
        "Author"
      ]
    },
    {
      "type": "Person",
      "givenName": "B.",
      "familyName": "Gassend",
      "contributorRoles": [
        "Author"
      ]
    },
    {
      "type": "Person",
      "givenName": "G.E.",
      "familyName": "Suh",
      "contributorRoles": [
        "Author"
      ]
    },
    {
      "type": "Person",
      "givenName": "M.",
      "familyName": "van Dijk",
      "contributorRoles": [
        "Author"
      ]
    },
    {
      "type": "Person",
      "givenName": "S.",
      "familyName": "Devadas",
      "contributorRoles": [
        "Author"
      ]
    }
  ],
  "date": {
    "published": "2004-10-26T09:47:24Z"
  },
  "identifiers": [
    {
      "identifier": "https://doi.org/10.1109/vlsic.2004.1346548",
      "identifierType": "DOI"
    }
  ],
  "license": {},
  "provider": "Crossref",
  "publisher": {
    "id": "https://api.crossref.org/members/263",
    "name": "Widerkehr and Associates"
  },
  "references": [
    {
      "key": "ref4",
      "id": "https://doi.org/10.1145/586110.586132"
    },
    {
      "key": "ref3",
      "id": "https://doi.org/10.1109/9780470544365"
    },
    {
      "key": "ref6",
      "title": "IC Identification Circuit Using Device Mismatch",
      "publicationYear": "2000"
    },
    {
      "key": "ref5",
      "id": "https://doi.org/10.1109/csac.2002.1176287"
    },
    {
      "key": "ref2",
      "title": "Identification and Authentication of Integrated Circuits",
      "publicationYear": "2003"
    },
    {
      "key": "ref1",
      "publicationYear": "2001"
    }
  ],
  "titles": [
    {
      "title": "A technique to build a secret key in integrated circuits for identification and authentication applications"
    }
  ],
  "url": "http://ieeexplore.ieee.org/document/1346548/"
}

What is very odd- is that the date in the JSON above ("2004-10-26T09:47:24Z") seem to be  extracted from the :
2004-10-26T09:47:24Z
Which is the date the record was createed, not the date the item was published.
http://api.crossref.org/works/10.1109/vlsic.2004.1346548/transform/application/vnd.crossref.unixsd+xml

The issue is simply one of granularity—some dates (e.g., "published") can be partial, and the original metadata doesn't include a time component. However, it would be good if all dates (partial or otherwise) were represented consistently, even in string form. So, for example:

"2024-12-01" -> "2024-12-01 00:00:00 +0000 UTC"
"2016-06" -> "2016-06-01 00:00:00 +0000 UTC"
"1965" -> "1965-01-01 00:00:00 +0000 UTC"
"2017-11-07T08:18:33Z" -> "2017-11-07 08:18:33 +0000 UTC"


Change Link to FAQ page on Why NavBar Link (#302)

This PR changes the link on the Why NavBar link to /denver-learn-more (#302).
The About component is no longer used, and it was deleted.
Multiple other components used styling from _About.scss, so to more clearly represent this usage, I changed it to to a partial _info. References to "about" in classNames have now been changed to "info".

@hoop71
I agree with you about the conventions. I added the underscore because it looks like _form and _button are used across multiple components in the same way that _info is used.
At first glance, the components that do not use an underscore seem to refer to one specific component.
I would need to spend more time seeing if that pattern holds true (I imagine it doesn't).

Looks good.  Squash and Merge please

On previous teams, I’ve always followed the pattern that another person on the team merges the PR into master.
If that’s not the process we're following, I can squash and merge since the changes are approved and checks are passed.

Go ahead and so the deed.  you know best how to comment the squash commit message.
Also add 'Connect #302' in your message to have the waffle board auto update


Add Comox Valley Regional District

Closes: https://github.com/openaddresses/openaddresses/pull/6447

For #6076


Confusing warning: trace writer payload rejected by edge: 403 Forbidden

After upgrading to latest version of dd-trace node package, we have been experiencing loads of similar errors in logs:
2022-12-28 14:50:55 UTC | TRACE | WARN | (run.go:261 in Warnf) | Trace writer payload rejected by edge: 403 Forbidden

When tracing this down from the code-base it does look as if this is shown when some event type is not supported.
We're only seeing this in staging where we do not have DD_TRACE_ENABLED configured which makes me wonder if this is expected behaviour of the extensions (when initiated and having some environment variables not provided or tracing turned off?).

Solution already found. In our case it was an issue of our API key (DD_API_KEY) being connected to an account created for domain datadoghq.eu where the default setup will probably communicate with datadoghq.com instead.
Solved by defining: DD_SITE=datadoghq.eu

Solution already found. In our case it was an issue of our API key (DD_API_KEY) being connected to an account created for domain datadoghq.eu where the default setup will probably communicate with datadoghq.com instead.
Solved by defining: DD_SITE=datadoghq.eu

Thanks @allanpaiste - Took me forever to solve this one.


Rancher Monitoring: ClusterRole settings missing

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Activate the cluster monitoring in Rancher 2.4.5. Then check exporter-kube-state-cluster-monitoring logs
Result:
Following errors are seen in the logs:
E0626 08:36:05.291099 1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.ValidatingWebhookConfiguration: validatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "validatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
E0626 08:36:05.388810 1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
E0626 08:36:05.389499 1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.MutatingWebhookConfiguration: mutatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
E0626 08:36:05.435740 1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.VolumeAttachment: volumeattachments.storage.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "volumeattachments" in API group "storage.k8s.io" at the cluster scope
Other details that may be helpful:
If I add the missing ClusterRoles to exporter-kube-state-cluster-monitoring, the errors disappear.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.5
Installation option (single install/HA): HA

The bug is reproduced in Rancher v2.4.5 single-install
monitoring version 0.1.1
E0626 17:49:39.814477       1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.MutatingWebhookConfiguration: mutatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
E0626 17:49:40.296305       1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.NetworkPolicy: networkpolicies.networking.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope
E0626 17:49:40.595377       1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.ValidatingWebhookConfiguration: validatingwebhookconfigurations.admissionregistration.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "validatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
E0626 17:49:40.708028       1 reflector.go:156] pkg/mod/k8s.io/client-go@v0.0.0-20191109102209-3c0d1af94be5/tools/cache/reflector.go:108: Failed to list *v1.VolumeAttachment: volumeattachments.storage.k8s.io is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "volumeattachments" in API group "storage.k8s.io" at the cluster scope```

this bug does NOT exist in monitoring v0.1.0

in  monitoring v0.1.0
exporter-kube-state:
  enabled: false
  apiGroup: "monitoring.coreos.com"
  image:
    repository: rancher/coreos-kube-state-metrics
    tag: v1.8.0

V.S.
in  monitoring v0.1.1
exporter-kube-state:
  enabled: false
  apiGroup: "monitoring.coreos.com"
  image:
    repository: rancher/coreos-kube-state-metrics
    tag: v1.9.5

BUT, the rbac.yaml are the same in both versions

here is the list of missing permissions
 list resource "volumeattachments" in API group "storage.k8s.io" at the cluster scope
 list resource "mutatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
 list resource "validatingwebhookconfigurations" in API group "admissionregistration.k8s.io" at the cluster scope
 list resource "networkpolicies" in API group "networking.k8s.io" at the cluster scope

The chart is available in dev-v2.4 branch

the bug fix is validated on Rancher:v2.4.6-rc3 with monitoring chart v0.1.2
the branch of system-chart is dev-v2.4 by default
The abovementioned errors are gone in the logs of exporter-kube-state-cluster-monitoring

wait for validating the issue in rancher:master

the bug fix is validated in Rancher:master-3286-head with monitoring chart v0.1.2
the branch of system-library is dev-v2.4 by default
The abovementioned errors are gone in the logs of exporter-kube-state-cluster-monitoring


[TritonGEN] Add triton_gen.cache_control operation

Add triton_gen.cache_control operation to represent SPV_INTEL_cache_controls decorations in MLIR.
This operation does not convert to any operation in a different dialect, as it supports translation straight to LLVM IR as metadata.
triton-translate is a new tool used to test this translation.

This is a highly experimental PR. Not ready to merge at all, as this is just a POC. Missing:

Cache control values verification
Check this works in the pipeline (translation interface is properly registered)
Support more than one annotation by not overriding MD if present

Instead of expressing cache control at the pointer, the new proposal is to express at the memory operation (https://github.com/KhronosGroup/SPIRV-LLVM-Translator/pull/2566#issuecomment-2116734834).

Instead of expressing cache control at the pointer, the new proposal is to express at the memory operation (KhronosGroup/SPIRV-LLVM-Translator#2587).

Updated implementation. This is ready to review now.

Given that the new design has cache control on the memory operation instead of the pointer, would it make sense for TritonGEN to add an attribute instead of a new operation that express the cache control on the pointer?

Given that the new design has cache control on the memory operation instead of the pointer, would it make sense for TritonGEN to add an attribute instead of a new operation that express the cache control on the pointer?

The cache control is a property of the load/store operations rather than the ptr used by those operations. So I think the attribute is a better way to go.

The cache control is a property of the load/store operations rather than the ptr used by those operations. So I think the attribute is a better way to go.

My fear is that MLIR transform passes may drop these attributes, as these are not guaranteed to be preserved. That's why I went with this design.

My fear is that MLIR transform passes may drop these attributes, as these are not guaranteed to be preserved. That's why I went with this design.

It is the same concern for metadata on memory operations too. Do you think there is a high chance that attributes would be dropped in practice?

My fear is that MLIR transform passes may drop these attributes, as these are not guaranteed to be preserved. That's why I went with this design.

It is the same concern for metadata on memory operations too. Do you think there is a high chance that attributes would be dropped in practice?

That will depend on how late in the pipeline these are added. The only way we can make sure these are added is if the operation is to be added as part of a conversion to LLVM dialect pattern. Otherwise, even if we have an operation foo converting to llvm.store, we will not guarantee the attributes will be carried over in the conversion to llvm.store.

The cache control is a property of the load/store operations rather than the ptr used by those operations. So I think the attribute is a better way to go.

My fear is that MLIR transform passes may drop these attributes, as these are not guaranteed to be preserved. That's why I went with this design.

Got it, however the chance is small because we aren't running any transformations on the TritonGEN code

The cache control is a property of the load/store operations rather than the ptr used by those operations. So I think the attribute is a better way to go.

My fear is that MLIR transform passes may drop these attributes, as these are not guaranteed to be preserved. That's why I went with this design.

Got it, however the chance is small because we aren't running any transformations on the TritonGEN code

Yeah, I was thinking more on:

That will depend on how late in the pipeline these are added. The only way we can make sure these are added is if the cache control information is to be added as part of a conversion to LLVM dialect pattern. Otherwise, even if we have an operation foo correctly annotated and converting to llvm.store, we cannot guarantee the attributes will be carried over in the conversion to llvm.store.

If the cache control is to be set only when creating the corresponding llvm.load/store operation, the attribute approach might work.

Are we fine with current approach or do we wanna switch to using discardable attributes in operations? @whitneywhtsang @etiotto

Are we fine with current approach or do we wanna switch to using discardable attributes in operations? @whitneywhtsang @etiotto

My preference is attributes in operations.

My preference is attributes in operations.

The 2D block load operation in the TritonGen dialect already has an attribute for the cache control. When we lower that operation into a call we cannot pass the cache control as an argument because the "builtin" call we need to generate does not have that argument. Instead of taking the cache control as an argument we need to generate metadata and attach it to the function call.
Can we do that cleanly ?

The 2D block load operation in the TritonGen dialect already has an attribute for the cache control. When we lower that operation into a call we cannot pass the cache control as an argument because the "builtin" call we need to generate does not have that argument. Instead of taking the cache control as an argument we need to generate metadata and attach it to the function call.

With the changes I've just pushed, that'd involve attaching an attribute to the call operation as in the examples.


None check server cloud create branch

What's in this PR?
Make sure that we get the cloud or server subscription correctly
Tested on stage and works a treat
Why
There is a bug on create-branch when it doesn't work because we return the wrong subscription
BEFORE FIX

AFTER FIX

This was deployed?


[Bug] Too few arguments to function Illuminate\Database\Eloquent\Relations\HasOneOrMany

Bug report
What I did
Acessed create page from a crud having relation to another object
What I expected to happen
Open the page
What happened
Get this error:
Too few arguments to function Illuminate\Database\Eloquent\Relations\HasOneOrMany::__construct(), 0 passed in D:\xampp\htdocs\backpack\vendor\backpack\crud\src\app\Library\CrudPanel\Traits\Relationships.php on line 345 and exactly 4 expected
What I've already tried to fix it
Input an attribute named entity in my  array
Is it a bug in the latest version of Backpack?
yes, backpack/crud 5.0.3 and backpack/pro 1.0.7
After I run composer update backpack/crud the bug... is it still there?
yes
Backpack, Laravel, PHP, DB version
backpack/crud 5.0.3
backpack/pro 1.0.7
Laravel 9.0.2
PHP 8.0.11
DB: Postgresql
When I run php artisan backpack:version the output is:
PHP 8.0.11 (cli) (built: Sep 21 2021 18:26:06) ( ZTS Visual C++ 2019 x64 )
Copyright (c) The PHP Group
Zend Engine v4.0.11, Copyright (c) Zend Technologies
LARAVEL VERSION:
v9.0.2@4c7cd8c4e95d161c0c6ada6efa0a5af4d0d487c9
BACKPACK VERSION:
5.0.3@c14eaca0d10c3a37280786d65cebf735235850d6

Exact same issue here when using a BelongsTo relationship when setting up custom searchLogic for a column.

Thanks guys! @pxpm Looks like our fix for fields in 5.0.3... broke the columns 😅 Could you please take a look?

OK, let me share the relationship parts of the Models here.
Customer:

    /**
     * all invoices for this customer
     *
     * @return HasMany
     */
    public function invoices(): HasMany
    {
        return $this->hasMany('App\Models\Invoice');
    }

Invoice:
    /**
     * the customer this mandate belongs to
     *
     * @return BelongsTo
     */
    public function customer(): BelongsTo
    {
        return $this->belongsTo('App\Models\Customer');
    }

InvoiceCrudController->setupListOperation():
        $this->crud->addColumn(
            [
                'name'     => 'customer_id',
                'label'    => __('invoices.customer'),
                'escaped'  => false,
                'type'     => 'closure',
                'function' => function($entry) {
                    $admin_id = Config::get('settings.xyz_administration_id');
                    return $entry->customer->moneybird_name . ' customer->xyz_customer_id . '" target="_blank">';
                },

                'searchLogic' => function ($query, $column, $searchTerm) {
                    $query->orWhereHas('customer', function ($q) use ($column, $searchTerm) {
                        $q->where('xyz_name', 'like', '%'.$searchTerm.'%');
                    });
                }
            ],
        );

@pxpm I manually patched the Relationships Trait per your PR and it fixes the issue. Thanks for the quick fix!

Pfiew! Merged & tagged https://github.com/Laravel-Backpack/CRUD/pull/4181. So a composer update should fix it for you guys.
Thanks again for submitting this 🙏

thanks, problem solved :)


fix: shutdown runtimes explicitly when LSP shutsdown

fix: shutdown runtimes explicitly when LSP shutsdown
This should hopefully help with the tests, as they often spit out "blah
blah overlapping partitions blah blah" with regard to the clustered
nodes that are started. In test, we start many many nodes all connected
to the main node, which is the test application.
Copied some code from @zachallaun from #165

Current dependencies on/for this PR:

main

PR #172   👈

This comment was auto-generated by Graphite.


Don't override cmake cxx standard when already set by the user

Basically this is https://github.com/grpc/grpc/pull/22938 with a fixed typo.
Fixes https://github.com/grpc/grpc/issues/22125,

Recreated the PR without typo in https://github.com/grpc/grpc/pull/22976

Known failures:
https://github.com/grpc/grpc/issues/22978
https://github.com/grpc/grpc/issues/22968


Render branch cleanup

Here are some proposed cleanups to the current code.
Note: Please double check the math logic etc.

Simplified some arguments to functions
Added docstrings/comments here and there
Cleaned up redundant functions
Avoid usage of private ._ordered but use the .ordered() classmethod on some of the pxr usdview arg classes.
And also a lot of PEP08 cleanup

Let me know what you think - please comment if you disagree with certain choices.
Note that I purely looked at the code - not at where things are placed and whether the functionality in the end is what we need.

As of:
https://github.com/Sasbom/usd-qtpy/commit/880e37645335335adabebe0ef0354746dbc31125
nearly every cleanup has been implemented, and bugtested.
There are some things I kept in there, such as specifying the precision of transformation operations,
and some ordering which, when redone, gave some issues.
Thank you!

Aren't those actually the default values you're passing? Basically, redundant arguments?

The default precision for an operation added without arguments is XfromOp.PrecisionFloat, I ran a little experiment.
>>> from pxr import Usd
>>> stage = Usd.Stage.CreateInMemory()
>>> from pxr import UsdGeom
>>> prim = UsdGeom.Xform.Define(stage,"/xform")
>>> op = prim.AddRotateXOp()
>>> op.GetPrecision()
UsdGeom.XformOp.PrecisionFloat

Do we care about the double precision? Why do we care about forcing a higher precision in this instance?

Do we care about the double precision? Why do we care about forcing a higher precision in this instance?

I think so,
Assume someone needs to render a turntable that turns very very slowly, to showcase a large scene,
I would assume it's in best interest to keep the precision of the rotation as high as possible.
The values themselves are interpolated between frames, but ultimately rely on the precision of the place where the computed value of the operator is stored, so having floating point errors occur wouldn't be great, as sometimes the rotation spacing could be off.
I feel like specifying the precision to be the highest on the operator that is essential to a turn table,
just the one that turns stuff, is not a bad deal.
It'd be different we'd be dealing with a whole transformation matrix with 16 values, that'd be too much,
but a single rotation only has to store 1.

Fine with me, felt to me more like anticipating a problem that in reality wouldn't really become a quantifiable problem. I mean, what type of floating point precision's we are talking here, these are like 1e-6 values in degrees?
Anyway, don't care too much. Was just wondering whether we had good reason to explicitly set it higher, as if you were working around a current issue but that's not the case.
Thanks!

Fine with me, felt to me more like anticipating a problem that in reality wouldn't really become a quantifiable problem. I mean, what type of floating point precision's we are talking here, these are like 1e-6 values in degrees?
Anyway, don't care too much. Was just wondering whether we had good reason to explicitly set it higher, as if you were working around a current issue but that's not the case.
Thanks!

I just have nightmares about running into floating point precision errors while adjusting sliders in Houdini x)
That's about it, I don't wanna risk anything when it doesn't impact performance


Error rendering settings

The settings are not rendered, instead the message “error rendering settings” is shown.

Same problem occurred to me. Can't change trigger keyword.

Same for me

There should've been an update released last night to address this issue - can you refresh and see if you still see it?

I did a refresh, uninstalled the extension, cleared the local cache, refreshed again and installed the extension, but the error is still there

Are you able to pop open the console and report what error is being thrown?

The plugin Query Builder shows the settings. This plugin is made by you (@dvargas92495) as wel isn't it? Maybe this clarifies something.

It doesn't as I still don't know what the error is and the settings appear on my end. If you hit CMD+OPT+I to open the developer tools and go to console, what are the red messages that appear?

Let me know if you also need the log of this error.

Running into the same error on a brand new install of smartblocks after a refresh. This error logs on every single keystroke for me

Nice okay, I was able to reproduce and have it under review https://github.com/Roam-Research/roam-depot/pull/52

Issue solved! Thanks!

that would be unexpected since the change is still under review...


Rust UDF error

I have built a Rust UDF and added the function to Singlestore database using this command
CREATE FUNCTION <function name> AS WASM FROM HTTP 'https://<>.wasm'  with WIT from HTTP 'https://<>.wit'
when I ran select function(1,2,3) AS Result observing this error
ERROR 2654 UNKNOWN_ERR_CODE: Wasm module instantiation failed with error. unknown import: env::__extenddftf2 has not been defined
Can someone help me fix this issue?

Hi.  That error means that the wasm module is expecting the host (the database, in this case) to provide it with an implementation of that function.  SingleStore doesn't current supply any imports except what's included in WASI.  A couple of questions for you:

When you compiled, did you use the version of Rust included in this dev container?  Could you paste the compile command you used?

What 3rd party libraries are you including in your module?  Would it be possible for you to attach your Cargo.toml file here?

Yes, I have used the dev container.
[dev-shell]:~/src % cargo wasi build --lib --release    Compiling version_check v0.9.4    Compiling memchr v2.5.0    Compiling libc v0.2.135    Compiling autocfg v1.1.0    Compiling libm v0.2.5    Compiling semver v1.0.14    Compiling proc-macro2 v1.0.46    Compiling quote v1.0.21    Compiling unicode-ident v1.0.5    Compiling tinyvec_macros v0.1.0    Compiling anyhow v1.0.65    Compiling syn v1.0.102    Compiling pulldown-cmark v0.8.0    Compiling cfg-if v1.0.0    Compiling bitflags v1.3.2    Compiling byteorder v1.4.3    Compiling id-arena v2.2.1    Compiling unicode-xid v0.2.4    Compiling stable_deref_trait v1.2.0    Compiling unicode-segmentation v1.10.0    Compiling regex-syntax v0.6.27    Compiling smallvec v1.10.0    Compiling wasi v0.11.0+wasi-snapshot-preview1    Compiling wit-bindgen-gen-rust-wasm v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling glob v0.3.0    Compiling pkg-config v0.3.25    Compiling log v0.4.17    Compiling once_cell v1.15.0    Compiling async-trait v0.1.57    Compiling thiserror v1.0.37    Compiling lazy_static v1.4.0    Compiling robust v0.2.3    Compiling unicase v2.6.0    Compiling ahash v0.7.6    Compiling ahash v0.8.0    Compiling num-traits v0.2.15    Compiling tinyvec v1.6.0    Compiling hash32 v0.2.1    Compiling getrandom v0.2.7    Compiling heck v0.3.3    Compiling geographiclib-rs v0.2.1    Compiling unicode-normalization v0.1.22    Compiling jobserver v0.1.25    Compiling aho-corasick v0.7.19    Compiling rustc_version v0.4.0    Compiling hashbrown v0.12.3    Compiling cc v1.0.73    Compiling heapless v0.7.16    Compiling regex v1.6.0    Compiling approx v0.5.1    Compiling float_next_after v0.1.5    Compiling float-cmp v0.6.0    Compiling wit-parser v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling libh3-sys v0.1.3    Compiling rstar v0.9.3    Compiling wit-bindgen-gen-core v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling geo-types v0.7.7    Compiling libh3 v0.1.8    Compiling wit-bindgen-gen-rust v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling h3ron-h3-sys v0.15.1    Compiling geo v0.22.1    Compiling thiserror-impl v1.0.37    Compiling wit-bindgen-rust-impl v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling wit-bindgen-rust v0.1.0 (https://github.com/bytecodealliance/wit-bindgen.git?rev=60e3c5b41e616fee239304d92128e117dd9be0a7#60e3c5b4)    Compiling h3ron v0.15.1    Compiling h3index v0.1.0 (/home/ravi/src)     Finished release [optimized] target(s) in 19.08s   Optimizing with wasm-opt
I am trying to build udf to convert lat and lon to h3index. The code I have tested with is available here https://github.com/K4Mobility/singlestore-h3index-udf

Thank you for providing this information.  I'll investigate and get back to you soon.

In the h3ron project, I found the following comment (from https://github.com/nmandery/h3ron/blob/main/h3ron/examples/compile_to_wasi/Makefile):
# 128 bit floats are not supported by rust. See https://github.com/rust-lang/compiler-builtins .
# This manifests in errors like:
#
# ```
# wasmtime ../../../target/wasm32-wasi/debug/compile_to_wasi.wasm
# Error: failed to run main module `../../../target/wasm32-wasi/debug/compile_to_wasi.wasm`
#
# Caused by:
#     0: failed to instantiate "../../../target/wasm32-wasi/debug/compile_to_wasi.wasm"
#     1: unknown import: `env::__extenddftf2` has not been defined
# ```
#
# To resolve this we link to the runtime library included in the SDK:
export RUSTFLAGS:=-C target-feature=-crt-static -C link-arg=-L$(WASI_SDK_PATH)/lib/clang/14.0.4/lib/wasi -C link-arg=-lclang_rt.builtins-wasm32

Based on this, in the SingleStore development container, I set the RUSTFLAGS environment variable like this:
export RUSTFLAGS='-C target-feature=-crt-static -C link-arg=-L/opt/wasi-sdk/lib/clang/14.0.4/lib/wasi -C link-arg=-lclang_rt.builtins-wasm32'

Then, I deleted the target directory and rebuilt:
rm -rf target
cargo wasi build --release --lib

This allowed me to successfully run the function in the database:
MySQL [pete]> select h3index(3.4, 4.5, 4);
+----------------------+
| h3index(3.4, 4.5, 4) |
+----------------------+
|<PHONE_NUMBER>13773567 |
+----------------------+
1 row in set (0.119 sec)

Nice. It works. Thank you very much!


README.md: add Comet ML logo

In support of 0.10.0 release!

How is this badge useful for Composer users?
The comet_ml badge is rendered in a row with Composer badges, the comet_ml badge looks like it does not fit there.
As a note, there is no badge for other supported tools such as wandb.
I suggest to rethink this. It would be better to have this in a section with "supported tools".

No problem. I'm closing this PR.


ffmpeg Rendering giving error

Hi,
I got the script to work for a couple of recordings but after that it is giving me continuous error for any recording I am running it for. Here is the error
`[Error] Failed rendering downloable video for BBB presentation  {
args: Namespace(input='/var/bigbluebutton/published/presentation/ID', output='/var/bigbluebutton/published/presentation/ID/video.mp4'),
format: 'mp4',
docker: true,
workdir: './tmp/dataMoEDif'
}
Error: Command failed: ffmpeg -hide_banner -loglevel error -f concat -i ./tmp/dataMoEDif/slides.txt -threads 1 -y -filter_complex "[0:v]fps=24, scale=800:-2[out]" -map '[out]' -strict -2 -crf 22 -pix_fmt yuv420p ./tmp/dataMoEDif/slides.mp4
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at renderVideo (/home/bigbluebutton/modules/slides.js:317:18)
at module.exports.renderSlides (/home/bigbluebutton/modules/slides.js:13:15)
at async module.exports.createPresentationVideo (/home/bigbluebutton/modules/presentation.js:10:20)
at async module.exports.createVideo (/home/bigbluebutton/modules/processor.js:20:26)
at async run (/home/bigbluebutton/index.js:10:9) {
status: null,
signal: 'SIGKILL',
output: [ null, ,  ],
pid: 117,
stdout: ,
stderr:
}
`
Can anyone help me out with it ?
Thanks

Hello, exactly the same issue here. Thanks

Same error here.

@tilmanmoser .. Please can you leave a comment regarding it or some guidance in helping fix this issue is highly appreciated.
Thank you.

What is your environment, where you run it?
I see the same problems with bbb-video-download on ubuntu 18 on a BBB 2.4.0 host.
If I process the videos with bbb-video-download on ubuntu 16 on a BBB 2.3.16 host, the processing succeeds.
ffmpeg gets killed from oom-killer:
Jan  5 05:52:53 bbb-27-29 kernel: [72337.405981] [20806]   997 20806 14432304 13469022 115712000   905227             0 ffmpeg
Jan  5 05:52:53 bbb-27-29 kernel: [72337.405982] Out of memory: Kill process 20806 (ffmpeg) score 904 or sacrifice child
Jan  5 05:52:53 bbb-27-29 kernel: [72337.406179] Killed process 20806 (ffmpeg) total-vm:57729216kB, anon-rss:53876088kB, file-rss:0kB, shmem-rss:0kB
Jan  5 05:52:54 bbb-27-29 kernel: [72338.557187] oom_reaper: reaped process 20806 (ffmpeg), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

I have no changed the following to make it working again until a real fix is availlable:
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -1,8 +1,8 @@
-FROM node:12-alpine
+FROM node:12-alpine3.11

Why does the newer ffmpeg get all this memory until OOM hits?

I faced same error and oom killer killed the ffmpeg process . thanks to @christmart  for his suggestions.
I think it is because of ubuntu version. I had two containers with this base image FROM node:12-alpine  on both ubuntu 16 and ubuntu 18. old version works correctly but on ubuntu 18 it has error.

Should be re-opened and merged :-|

I have now changed the following to make it working again until a real fix is availlable:
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -1,8 +1,8 @@
-FROM node:12-alpine
+FROM node:12-alpine3.11

Why does the newer ffmpeg get all this memory until OOM hits?

I have now changed the following to make it working again until a real fix is availlable:
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -1,8 +1,8 @@
-FROM node:12-alpine
+FROM node:12-alpine3.11

Why does the newer ffmpeg get all this memory until OOM hits?

Can confirm- this worked perfectly. Before patch, it was using upwards of 20GB of RAM and still dying with OOM. ~1G now for the same video.

I have now changed the following to make it working again until a real fix is availlable:
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -1,8 +1,8 @@
-FROM node:12-alpine
+FROM node:12-alpine3.11

Why does the newer ffmpeg get all this memory until OOM hits?

I have now changed the following to make it working again until a real fix is availlable:
--- a/src/Dockerfile
+++ b/src/Dockerfile
@@ -1,8 +1,8 @@
-FROM node:12-alpine
+FROM node:12-alpine3.11

Why does the newer ffmpeg get all this memory until OOM hits?

Can confirm- this worked perfectly. Before patch, it was using upwards of 20GB of RAM and still dying with OOM. ~1G now for the same video.


Bower package name not consistent

In the bower.json it's URIjs but the readme says to run bower install uri.js. Both work (not sure how?).

yes, this stems from a time where capitals were still allowed in bower/npm. We'll fix this with version 2 (whenever we start tackling it).

I have just renamed the package to urijs in npm (was URIjs) and bower (was uri.js).
new on npm: urijs
old on npm URIjs
➜  bower search uri.js
Search results:

    uri.js git://github.com/medialize/URI.js.git
    URIjs git://github.com/medialize/URI.js.git
    urijs git://github.com/medialize/URI.js.git (<---)

Does this mean old references do not work any longer in bower and npm or is there some kind of automatic redirection?

The old reference ("URIjs") will still work - up to the the version 1.16.1

Hm yes that's what I figured. But now automatic checks for newer versions won't work and users might not be informed about a newer URIjs version.
How about publishing a final 1.16.2-URIjs-renamed-to-urijs version?

You can deprecate versions with a message (I'm pretty sure you can deprecate all versions too)

Hm yes that's what I figured. But now automatic checks for newer versions won't work and users might not be informed about a newer URIjs version.

True. Furthermore most of the reasons that made me rename the package are void. In a little while someone will be joining the npm team who might make this "meta project maintenance" stuff a priority topic. we'll see what they'll come up with to get me/us out of this mess.

How about publishing a final 1.16.2-URIjs-renamed-to-urijs version?

I thought that's what I did.

You can deprecate versions with a message (I'm pretty sure you can deprecate all versions too)

just ran
npm deprecate URIjs@"< 1.16.2" 'package renamed to "urijs" (lower-case), please update accordingly'

The issue that finally got me to rename the package was that URIjs was not showing any download numbers, and dependent packages anymore. Because npm moved to lower-case package names a while ago, and various issues with that have not been treated with any priority (at least it did not feel that way), I decided to simply side-step this and any future issue by renaming the package.
As of now the stats are back (except for historic download numbers, but whatever). Making the entire renaming thing kinda pointless. I'm going to crawl back under the rock I came from - have a good day ;)

OK than, thanks for the explanation :)


Stop anchor click propagation

Fixes #54 by calling MouseEvent.stopPropagation() inside a click event handler for the invisible anchor element. The handler removes itself once executed.

Hello @rndme, have you had a moment to review this? Do you need more information about the issue?


[Translate ru] feedback -> book

I remember that you don't need a translate .yaml files, but I think it will be more comfortable for Russian speakers to see a menu on Russian language.
Anyway, it is not a critical thing. so you can just close this PR)
Check out a review request at GitLocalize

Thanks for the contribution! Due to the way DevSite works, we can't translate _book.yaml, _project.yaml, _toc.yaml, _footer.yaml, _redirects.yaml, _upper-tabs-*.yaml files. I'm going to close this for now. Thanks


Feedback on fork activities.

Hi, not sure how to raise this without some kind of author coms so feel free to delete/whatever if you don't want this here.
I forked this repo a few weeks ago and already have some players pulling from my fork.
I don't have an issue with that but I didn't, really to the fork to do anything other than to tweak the code for fun and learn how to use lua/oc in general, certainly not for pushing out updates. Some of the things i've done aren't really anything other than me playing with lua concepts etc.
If you want to contact me directly to discuss feel free to do so via the discord, name username (AtomicGrog#7956)

Hello,
This project was originally just a tool for my personal Minecraft world.
I'm glad anyone would take time to understand my code and do any sort of improvement on it. I'm not play Minecraft at the moment and I don't see myself maintaining this project.
If you want me to add your fork in the README file of this repo, please let me know.
I will change the license of this project to MIT when I have free time, which basically means you can do whatever you want with the code as long as you address the original author and include the same LICENSE file.
Another unrelated thing, I've noticed your fork a few weeks back, I noticed that you just gave up on commit comments. This is not a request, but I would be glad of you could write proper comments when commit.
Best regards.
xyqyear

A sorry re: commits.
I was essentially using it as a method of uploading to the robot ie. Save change to github and then download change with ./install.lua ordinarily i'd do it via a dev branch but as i thought i'd just be playing with the code didnt see much benefit in comments.


revert: Fix: Markdown hyperlinks with parenthesis take first closing parenthesis as final

Reverts usememos/memos#1213

What is the bug caused?

What is the bug caused?

Please check the #1250
I'd like to revert the change in this release and find a better way to fix it.


CIS Non Standard Ports initial commit

A New PR
THANK YOU - We love to get PR's and really appreciate your time and help to improve this module
Accepting a PR
Before we accept the PR - please confirm that you have run the tests locally to avoid our automated build and release process failing. You can see how to do that in our wiki
https://github.com/sqlcollaborative/dbachecks/wiki
Please confirm you have 0 failing Pester Tests
[X] There are 0 failing Pester tests
Changes this PR brings

CIS Test for SQL instances to installed on non default ports

Close #654
Please add below the changes that this PR covers. It doesnt need an essay just the bullet points :-)

Thank you @tboggiano


access sikulixapi.jar on macOS

I tried to use Jpype1 to automate GUI with 'sikulixapi.jar' on macOS.
This package works well when I imported it  on my java project, but had problem when I used Jpype1 to access it.
Here is my code:
`from jpype import *
startJVM(get_default_jvm_path(), '-ea', r'-Djava.class.path=somepath/sikulixapi.jar')
Screen = JClass('org.sikuli.script.Screen')
s = Screen()
`
When the code ran into 'Screen = JClass('org.sikuli.script.Screen')', my program was in deadlock. Not any responses unless ending the python process.
OSX: 10.12(x64)
python: 3.6
Jpype1: latest
JDK: 1.8.0_171(x64)
I'm looking forward to your suggestions，thanks.

I got the sikulixapi.jar on this site:
https://launchpad.net/sikuli/sikulix/1.1.2

Best guess, the jar was trying to unpack a series of dll or shared libraries during the load phase the lead to an internal deadlock or some other failure.  It is not a pure jar code but is attempting to push native libraries into the system and then execute them.  I would recommend trying to run the command using pure java first to see if the error is coming from within the jpype layer or the java.  Based on the type of actions I am seeing it do I am guessing that the behavior is correct.  Jpype called the class loader on the class object and it never returns because it an internal deadlock in the jar.
When I tried it hit an internal problem and failed with a reasonable error code.
java.io.IOException: Access is denied
        at java.io.WinNTFileSystem.createFileExclusively(Native Method)
        at java.io.File.createTempFile(File.java:2024)
        at java.io.File.createTempFile(File.java:2070)
        at org.bridj.Platform.createTempDir(Platform.java:710)
        at org.bridj.Platform.<clinit>(Platform.java:227)
        at org.bridj.BridJ.register(BridJ.java:191)
        at org.sikuli.util.SysJNA$WinKernel32.<clinit>(SysJNA.java:23)
        at org.sikuli.script.RunTime.addToWindowsSystemPath(RunTime.java:1034)
        at org.sikuli.script.RunTime.libsExport(RunTime.java:992)
        at org.sikuli.script.RunTime.init(RunTime.java:738)
        at org.sikuli.script.RunTime.get(RunTime.java:312)
        at org.sikuli.script.RunTime.get(RunTime.java:122)
        at org.sikuli.script.RunTime.get(RunTime.java:337)
        at org.sikuli.script.Region.<clinit>(Region.java:23)
Traceback (most recent call last):
  File "testSik.py", line 3, in <module>
    sik = jpype.JClass('org.sikuli.script.Screen')
  File "/home/nelson85/devel/open/jpype/jpype/_jclass.py", line 91, in __new__
    return _JClassNew(args[0])
  File "/home/nelson85/devel/open/jpype/jpype/_jclass.py", line 147, in _JClassNew
    javaClass = _jpype.PyJPClass(arg)
jpype._jclass.UnsatisfiedLinkError: org.bridj.Platform.sizeOf_ptrdiff_t()I

Simple code like the following should be all that jpype is executing.   We just load the class and then list the declared methods and fields.  If you can do this successfully from within pure java then it could be a jpype issue.   If it is a jpype issue, I would recommend recompiling with TRACING enabled and submit the trace log here.
public class MyTest
{
   public static void main(String[] args)
   {
      Class screenClass = java.lang.Class.forName("org.sikuli.script.Screen");
      // Then test code to list declared methods and fields
   }
}

Hi,
I did it successfully within pure java on Mac and also successful on Windows used the same python code.
The tracing info stoped here.
 </B> <!-- JPTypeManager::findClass -->
</B> <!-- JPypeModule::findClass -->
<B msg="PyJPClass::__dealloc__" >
</B> <!-- PyJPClass::__dealloc__ -->
<B msg="PyJPClass::__dealloc__" >
</B> <!-- PyJPClass::__dealloc__ -->
<B msg="PyJPClass::__dealloc__" >
</B> <!-- PyJPClass::__dealloc__ -->
<B msg="JPJavaEnv::NewGlobalRef" >
  <M>JPJavaEnv::NewGlobalRef :<PHONE_NUMBER> =><PHONE_NUMBER></M>
</B> <!-- JPJavaEnv::NewGlobalRef -->
<B msg="JPJavaEnv::NewGlobalRef" >
  <M>JPJavaEnv::NewGlobalRef :<PHONE_NUMBER> =><PHONE_NUMBER></M>
</B> <!-- JPJavaEnv::NewGlobalRef -->
<B msg="JPJavaEnv::NewGlobalRef" >
  <M>JPJavaEnv::NewGlobalRef :<PHONE_NUMBER> =><PHONE_NUMBER></M>
</B> <!-- JPJavaEnv::NewGlobalRef -->
<B msg="JPypeModule::findClass" >
  <M>JPypeModule::findClass : org.sikuli.script.Screen</M>
  <B msg="JPTypeManager::findClass" >
    <M>JPTypeManager::findClass : org.sikuli.script.Screen</M>

I would like to offer you a jar copy if you want, thanks.

Hmm,  seems like the exact same jar that I tried to run with.  The failure point is at the find class method in jni.  The fact that it worked fine on a PC from python makes me suspect that it is something they have placed in the dynamic native routines.
I do not currently have access to a Mac.  My route to debugging this would be to get the source code for the jar and adding some information to try to trace down the loader routine.   JPype just called the jni find class routine and waited for a response which did not happen, so it must be on the java side.  Also you may want to verify that  JVM used by python is the same as the one you tested with for pure python.

I got the sikulixapi.jar on this site:
https://launchpad.net/sikuli/sikulix/1.1.2

I meet the same issue. do you have any solutions yet?

I tried to use Jpype1 to automate GUI with 'sikulixapi.jar' on macOS.
This package works well when I imported it on my java project, but had problem when I used Jpype1 to access it.
Here is my code:
`from jpype import *
startJVM(get_default_jvm_path(), '-ea', r'-Djava.class.path=somepath/sikulixapi.jar')
Screen = JClass('org.sikuli.script.Screen')
s = Screen()
`
When the code ran into 'Screen = JClass('org.sikuli.script.Screen')', my program was in deadlock. Not any responses unless ending the python process.
OSX: 10.12(x64)
python: 3.6
Jpype1: latest
JDK: 1.8.0_171(x64)
I'm looking forward to your suggestions，thanks.

I meet the same issue. do you have any solutions yet?

Unfortunately it remains as it is.  I can't debug something that works for me.


Update ISO branding with new RockNSM logos.

@jeffgeiger is this done and just needs to be closed?

Completed w/ devel commit e947cc148435f07965138b8c6112d89c3664d49d