Fix build for non-macOS platforms

Task usage requires iOS 133, tvOS 13, watchOS 6
watchOS 4 was too old for SwiftTreeSitter build

I would love to propose an idea to catch Package.swift platform target inconsistencies but I have no solution :)

I really appreciate this change, but I'm actually going to be removing this class anyways. Let's merge, but please don't rely on that.

I'm not using that. Just fixing local tests to verify I'm not breaking the rest :)


CSRF protection

Is your feature request related to a problem? Please describe.
We are using GraphQL mesh for our gRPC servers. We were thinking to add CSRF token for security purpose.
Describe the solution you'd like
One possible solution could be a plugin for Mesh to add CSRF token for all out going requests.
Describe alternatives you've considered
Alternative method could be something on our gRPC servers but using something on Mesh could be a huge help.

Added new docs about this;
https://the-guild.dev/graphql/mesh/docs/plugins/csrf


[Tooltip] Fix arrow demos

[x] I have followed (at least) the PR section of the contributing guide.

Please look over #16408 for details on the issue that this PR intends to fix.
Tagging @oliviertassinari as he is tracking issue #16408.
I have applied his suggested code changes keeping it on documentation level. I personally think keeping it at documentation level should be the way to go since tooltips with arrows are a completely custom thing and the issue only affects such tooltips. Since they are custom applying any fixes in library code risks breaking other parts when it really shouldn't.
Closes #16408

Thanks


Maybe a hidden no-defaults=1?


npm ERR! gyp: name 'openssl_fips' is not defined

Solution: https://github.com/nodejs/node-gyp/issues/2673#issuecomment-1196931379
• electron-builder  version=22.14.13
• rebuilding native dependencies<EMAIL_ADDRESS><EMAIL_ADDRESS>platform=darwin arch=arm64
⨯ cannot execute  cause=exit status 1
errorOut=npm ERR! code 1
npm ERR! path /Users/wks/Desktop/electron/terrasync/node_modules/ffi-napi
npm ERR! command failed
npm ERR! command sh -c node-gyp-build
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using<EMAIL_ADDRESS>npm ERR! gyp info using<EMAIL_ADDRESS>| darwin | arm64
npm ERR! gyp info find Python using Python version 3.8.9 found at "/Applications/Xcode.app/Contents/Developer/usr/bin/python3"
npm ERR! gyp info spawn /Applications/Xcode.app/Contents/Developer/usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/Users/wks/Desktop/electron/terrasync/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/wks/Desktop/electron/terrasync/node_modules/ffi-napi/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/wks/Desktop/electron/terrasync/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/Users/wks/.electron-gyp/11.5.0/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/Users/wks/.electron-gyp/11.5.0',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/Users/wks/Desktop/electron/terrasync/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/Users/wks/.electron-gyp/11.5.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/Users/wks/Desktop/electron/terrasync/node_modules/ffi-napi',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in ../node-addon-api/node_api.gyp while loading dependencies of binding.gyp while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: gyp failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/Users/wks/Desktop/electron/terrasync/node_modules/node-gyp/lib/configure.js:261:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:520:28)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
npm ERR! gyp ERR! System Darwin 21.5.0
npm ERR! gyp ERR! command "/usr/local/bin/node" "/Users/wks/Desktop/electron/terrasync/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /Users/wks/Desktop/electron/terrasync/node_modules/ffi-napi
npm ERR! gyp ERR! node -v v16.14.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR!      /Users/wks/.npm/_logs/2022-06-01T07_14_18_457Z-debug-0.log

                command=/usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js rebuild<EMAIL_ADDRESS><EMAIL_ADDRESS>                workingDir=

┌────────────────────────────────────────────────────────┐
│          electron-builder update check failed          │
│          Try running with sudo or get access           │
│          to the local update config store via          │
│ sudo chown -R $USER:$(id -gn $USER) /Users/wks/.config │
└────────────────────────────────────────────────────────┘
npm ERR! code 1
npm ERR! path /Users/wks/Desktop/electron/terrasync
npm ERR! command failed
npm ERR! command sh -c electron-builder install-app-deps
npm ERR!      /Users/wks/.npm/_logs/2022-06-01T07_14_16_686Z-debug-0.log

根据找到的资料在binding.gyp也添加了 ‘variables’:{'openssl_fips':0}

@cclauss  刚刚发现23天前我也像你们提过这个问题，但是貌似后续我解决了 ，当时是在windows上面。现在换了macos

node -v 16.14.0

I had the same issue with Node14. The version below node17 does not seem to match<EMAIL_ADDRESS>downgrade node-gyp to version "v8.3.0", the issue is solved for me.

I had the same issue with Node14. The version below node17 does not seem to match<EMAIL_ADDRESS>downgrade node-gyp to version "v8.3.0", the issue is solved for me.

In binding.gyp please try to add a line to
'variables' : {
    'openssl_fips': '',
}

gyp: name 'openssl_fips' is not defined while evaluating condition 'openssl_fips != ""' in binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1

I did not want to edit the binding.gyp file of a module that I was using. So I solved this problem by passing
"--openssl_fips=''" into the script I want to use, like npm install --openssl_fips=''

Does this solution solve all name 'openssl_fips' is not defined issues?

Does this solution solve all name 'openssl_fips' is not defined issues?

For my case yes. Had to make this change after updating node and npm to latest.

When using yarn it seems the --openssl_fips='' passed to yarn does not make a difference. If the issue happens in a dependency, editing binding.gyp in the node_modules/ directory gets reverted automatically. I ended up with a workaround that edits gyp's source code directly:
The gyp source code location is printed in the error message:
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/quark/.config/yarn/global/node_modules/node-gyp/lib/configure.js:285:16)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)

gyp seems to evaluate the binding.gyp as a Python script, I changed the builtin variables to evaluate the script:
diff --git a/gyp/pylib/gyp/input.py b/gyp/pylib/gyp/input.py
index 354958b..bb982eb 100644
--- a/gyp/pylib/gyp/input.py
+++ b/gyp/pylib/gyp/input.py
@@ -1190,7 +1190,7 @@ def EvalSingleCondition(cond_expr, true_dict, false_dict, phase, variables, buil
         else:
             ast_code = compile(cond_expr_expanded, "<string>", "eval")
             cached_conditions_asts[cond_expr_expanded] = ast_code
-        env = {"__builtins__": {}, "v": StrictVersion}
+        env = {"__builtins__": {"openssl_fips": ""}, "v": StrictVersion}
         if eval(ast_code, env, variables):
             return true_dict
         return false_dict

Here facing same issue:
yarn v1.22.19
node lts/gallium => 16.17.0
MacOS Monterey => 12.5.1
Workaround above https://github.com/nodejs/node-gyp/issues/2673#issuecomment-1196931379 did work fine
In addition I run both, yarn install and npm install.
yarn install
npm install --openssl_fips=''

@2812848295 Can this issue be closed?

env = {"__builtins__": {"openssl_fips": ""}, "v": StrictVersion}

This worked for me. Thank you

Hi. On Linux, node 18.7.0, building electron 20.0.3 for Element Matrix, none of the suggested solutions work.

What might be the solution for defining openssl_fips in gyp when not running npm install? Is there a node script.js equivalent? Passing in --openssl_fips='' does nothing (nor did I expect it to).
I can add "openssl_fips" : ""  to the variables section of binding.gyp, but the project I'm working with has sub dependencies with lots of .gyp files that I cannot edit. Nor does that seem like the ideal solution. Changing it in the top-level binding.gyp does not cause the variable to be
Is there another workaround?

Same issue here - adding yarn --openssl_fips='' does not work for me.

With Node 14 on Ubuntu 22.10, I solved this by downgrading npm to version 6 (npm install -g npm@6). Noticed the issue started as soon as I updated npm to version 9. The project was using yarn.

Had an issue on my Mac M1 with npm 8 (8.12.1) and node 14 and I managed to solved this by downgrading to npm 6 (latest-6).

I solved this downgrading node-gyp to version 8.4.1 ( yarn add<EMAIL_ADDRESS>-D) which used in electron version 9 native build scenario.

https://releases.electronjs.org/releases/stable says v22

For me, where the issue came from an electron project, upgrading electron and electron-builder to latest (23.1.4 and 23.6.0 respectively) solved the issue.

@arjunfulp You can avoid passing the flag in the npm install command by adding openssl_fips to the npm configuration:
npm config set openssl_fips ''

I solved by upgrading electron and electron-builder to latest & using node v13.14.0 via nvm.
I was building node-pty for edex-ui and i couldn't find any variable declaration in its binding.gyp.
using:
Python: 3.10.11
VS2017: (15.9.35027.97)
electron-gyp: 12.2.3

Please do not advocate that others use long archived software or unsupported versions of Node.js.

https://github.com/GitSquared/edex-ui
https://nodejs.org/en/about/previous-releases


Product random seed

Issue:
Trying to create repeatability by using pseudorandom number generation (with a saved random seed) so that we can reproduce issues
Summary of randomization changes...
Product Test (Population Clone Job)
-randomization ids
-date shift
-all controllable demographics randomization (demographics randomizer)
Checklist Test
-top measure shuffle
-criteria shuffle (data criteria selector)
Filtering Test
-age range (criteria picker)
Measure Test
-duplicating records

Looks like there are some Rubocop errors in this codebase that need to be fixed. if you run bundle exec overcommit --sign (only needs to be run once) then bundle exec overcommit --run you'll see the errors being thrown by Travis.

I believe all the rubocop/travis issues have been fixed and pushed. The rubocop autocorrect fixed some issues in files that I hadn't actually touched, but those changes didn't break the unit tests, so I ended up just pushing them up.


is there a directory option?

Apologies if I missed this - is there a way to send a directory through?
cssnano < builds/css/*.css
Thanks!

There's not a specific option to do that, you can use standard interfaces though :)
for f in ./builds/css/*.css; do cssnano $f; done

Does this work for you?

I'm using npm to run my scripts and I'm currently using this:
postcss -u cssnano --replace builds/css/*.css

which seems like cheating. It works, but I was wondering if there was a a pure cssnano way to do it.

Think that works because you're using the glob expansion in your shell?
@TrySound Do you think we need to offer glob support built in?

Don't have ideas :) But seems hacky. I don't like replacing at all.

I'd like this feature as well. It'd be nice to have src/css/vendor cssnano'd to dist/css/vendor. :)

Still no support for this? I would have thought this to be an essential/basic feature. Would be greatly appreciated if you could implement it! :)


Cleanup ibismanager from jobdefs

Closes #2863

There's a merge conflict.
Might also be an idea to create a getter for the ibismanager in the jobdef class.


how to configure swifts3 hostname as --endpoint ?

Hi Ka-Hing Cheung
I check the previous questions haven't found the relative answer yet.
Here is my question: Does goofys works with swift s3 ? and How can I configure swifts3 host as s3 --endpoint to allow to use goofys ?
For s3cmd
This is my s3cmd ~/.s3cfg
[default]
access_key = s3
host_base = cloud.swift.com
host_bucket = cloud.swift.com
secret_key = xxx
signature_v2 = False

This is s3 emulation layer test
$ s3cmd ls
2009-02-03 16:45  s3://testbucket

$ s3cmd ls s3://testbucket
2017-06-13 23:03     11358   s3://testbucket/LICENSE
2017-06-13 23:02       196   s3://testbucket/Makefile
2017-06-13 22:56      4365   s3://testbucket/NEWS
2017-06-08 23:42      1509   s3://testbucket/PKG-INFO
2017-06-13 22:57      4365   s3://testbucket/README.md
2017-06-13 23:08      6022   s3://testbucket/main.go

For goofys
This is my  ~/.aws/credentials
[default]
aws_access_key_id = s3
aws_secret_access_key = xxx

This is the goofys cmd I tried
$ goofys --endpoint http://cloud.swift.com/ testbuckets ~/goofys
2017/06/19 14:44:08.614494 main.FATAL Unable to mount file system, see syslog for details

This is tail syslog
$ tail /var/log/system.log
Jun 19 14:54:04 MacBook-Pro /usr/local/bin/goofys[22085]: main.ERROR Unable to access 'testbuckets': %!v(PANIC=runtime error: invalid memory address or nil pointer dereference)
Jun 19 14:54:04 MacBook-Pro /usr/local/bin/goofys[22085]: main.ERROR Unable to access 'testbuckets': invalid argument
Jun 19 14:54:04 MacBook-Pro /usr/local/bin/goofys[22085]: main.FATAL Mounting file system: Mount: initialization failed

Sorry if the question is too basic and I'm really appreciated your advice.
Thanks,
Johnny

Hi @chianingwang , just to clarify, in s3cmd I see your bucket name is testbucket but when you are mounting through goofys, you are specifying testbuckets, have you tried with testbucket?

@charudut ~ nice catch, sorry for the typo, i think i just paste it wrong.
$ goofys --endpoint http://cloud.swift.com/ testbucket ~/goofys
2017/06/19 20:36:19.378239 main.FATAL Unable to mount file system, see syslog for details

syslog
Jun 19 20:36:19 MacBook-Pro /usr/local/bin/goofys[33087]: main.ERROR Unable to access 'testbucket': RequestError: send request failed
	caused by: Head http://cloud.swift.com/testbucket/2z04ojkup4j70it7qu8fm9g10anfg6x4: dial tcp <IP_ADDRESS>:80: i/o timeout
Jun 19 20:36:19 MacBook-Pro /usr/local/bin/goofys[33087]: main.FATAL Mounting file system: Mount: initialization failed

Since i'm using swift s3, does it work for aws go sdk ? and what's endpoint should be in --endpoint

does cloud.swift.com support path-based requests instead of virtual host? Is there any reference on their swift implementation? (note that swift.com has nothing to do with openstack swift)

@kahing Thanks for your response, cloud.swift.com is our swift endpoint but running s3 emulation middleware to support s3 api. I think our swift s3 is supporting both , example as below.
### path style
host_bucket = <IP_ADDRESS>
host_base = <IP_ADDRESS>
### virtual hosted-style
host_bucket = %(bucket)s.swift.com
host_base = swift.com

is cloud.swift.com supposed to resolve to <IP_ADDRESS> or <IP_ADDRESS>? Note that in your earlier comment:
Jun 19 20:36:19 MacBook-Pro /usr/local/bin/goofys[33087]: main.ERROR Unable to access 'testbucket': RequestError: send request failed
	caused by: Head http://cloud.swift.com/testbucket/2z04ojkup4j70it7qu8fm9g10anfg6x4: dial tcp <IP_ADDRESS>:80: i/o timeout

I think it's just external ip and internal ip, I'm in vpn now. Sorry for confusing.

from the error, it would seem that goofys is not able to connect to <IP_ADDRESS>:80. Have you tried again with VPN?

@kahing ya , I try it again and configure /etc/host as well to make sure testbucket.cloud.swift.com align with internal ip <IP_ADDRESS>
2017/06/20 22:21:10.249643 main.FATAL Unable to mount file system, see syslog for details```

 ```Jun 20 22:21:10 MacBook-Pro /usr/local/bin/goofys[51444]: s3.ERROR code=RequestError msg=send request failed, err=Head http://testbucket.cloud.swiftstack.com/testbucket/m26wtde48bsjltwdadiyyrsjwco9k15p: dial tcp <IP_ADDRESS>:80: getsockopt: connection refused
Jun 20 22:21:10 --- last message repeated 1 time ---
Jun 20 22:21:10 MacBook-Pro /usr/local/bin/goofys[51444]: main.ERROR Unable to access 'testbucket': RequestError: send request failed
    caused by: Head http://testbucket.cloud.swiftstack.com/testbucket/m26wtde48bsjltwdadiyyrsjwco9k15p: dial tcp <IP_ADDRESS>:80: getsockopt: connection refused
Jun 20 22:21:10 MacBook-Pro /usr/local/bin/goofys[51444]: main.FATAL Mounting file system: Mount: initialization failed```

I might try to setup a test environment w/o `https` see whether I can make it work. Thanks for your kindly response.

dial tcp <IP_ADDRESS>:80: getsockopt: connection refused

Is the problem here

I setup a local swift with s3 emulation layer w/o https. It's working !
goofys --endpoint http://ss02.swiftstack.idv/ --region US jwangtest ~/goofys

@kahing and @charudut
Thanks all the helps

great! please update if you figured out why production wasn't working so maybe it will help other people

@chianingwang, glad you were able to get it to work!


Enable lwip PPPoS support

In PoC phase of my project I need to use ppp connection over GSM module, so
I successfully enabled lwip pppos api and I think it would be nice to add this feature to mainline.
What comes with this patch:

Fix some lwip pppos api bugs
Added PPP_SUPPROT parameter to lwip Kconfig
Added example pppos_client

Reviews welcome!
Adrian

Hi,
I changed code following to your comments.
In general, I'm not going to use other ip interfaces, however, I checked if wifi can somehow disturb PPP connection, and an only thing is default ip route setting. Wifi during initialization is setting itself as the default route, so, you have to take care of initialization sequence depending what default interface you want.
Btw: I thought about using two interfaces, but (maybe I'm wrong), I don't see in 'lwip' that multi IP source support is enabled (LWIP_HOOK_IP4_ROUTE_SRC), am I right?

What is the current status of this pull request ?

For me, OK. The code should be able to merge smoothly.

We're still keen to merge this into IDF, but it won't happen until after we take a branch for release v2.0 (any day now.)
Also we have to think through to what extent we (Espressif) support this. Because it's a core ESP-IDF feature, but not one we've tested ourselves or put into our internal QA process. I'm thinking we'll probably incorporate it and mark it as unsupported for now, although we may start supporting it more actively in the future (as it's an awesome feature!)

+1 on enabling this and making it part of the official IDF. At Pycom we are going to be using it very soon for adding cellular connectivity.

Though I dislike the me-too comments, +1 on supporting PPP as this can boost ESP32 deployments in the field.

Thanks everyone for being patient regarding this change.
I've rebased this branch on master and pushed it into our internal review/merge queue for further discussion.

Thanks again for bearing with us. This PR has been cherry-picked into master as 47c722d.


chore: improve all docs and best practices

this PR focuses on improving docs and open source best practices!

hey @excaliborr this PR is now mergeable! please check it

hi @0xGorilla can you check this out? only one approve is missing!

done! fixed! you can check it again @0xAustrian @excaliborr

@excaliborr @0xAustrian this PR can now be merged!

Hey @luislucena16  sorry for the late reply, we decided internally to not merge any docs/typo pr's for first time contributors, if you wanted to pick up feature work like adding support for biconomy paymaster like we talked about in the issue you are more then welcome to do so.


Improve website repo's README to include "getting started" instructions

Currently the README file doesnot have ample information, it'd be appropriate if we can add essential information like how to set the local hugo repository up? etc

FYI, this is the README for the website repo.  Should we have a readme there or use a shared one from the .github repo?

I think temporarily that should do and we can update it as and when we progress/make significant changes to the website based on the inputs of the team.

Sounds like a plan.


Keywords for interstitial ads

Is it possible to give keywords for interstitial ads? (to show more targeted ads)

yes, see the docs here:
https://github.com/floatinghotpot/cordova-admob-pro/tree/master/docs#targetting-options

Thank you for the quick response!
But does content URL support local urls in cordova? Because gender, child etc. is not my issue. Content is (I want to specify a keyword like "make up"). Or should I create an online url than point to it in my app?
Thank you again!

Try this:
AdMob.setOptions({
  customTargeting: {
    interest: ["make up"],
  },
});


Kous3106/add data

Added the data for the samples.

@ldanzinger Can you please review?

looks good


Show lessons and courses with softdeletes in admin

[x] Show lessons and courses with softdeletes in admin
[x] Add option force destroy when record delete(soft delete)

PR #22


Photon realtime issues

Importing into Unity at the moment in the latest LTS version throws a couple of errors I've not been able to resolve.
Library\PackageCache\com.community.netcode.transport.photon-realtime@1d5be27015\Runtime\PhotonRealtimeTransport.cs(260,30): error CS0115: 'PhotonRealtimeTransport.Initialize()': no suitable method found to override
and
Library\PackageCache\com.community.netcode.transport.photon-realtime@1d5be27015\Runtime\PhotonRealtimeTransport.Connection.cs(9,26): error CS0534: 'PhotonRealtimeTransport' does not implement inherited abstract member 'NetworkTransport.Initialize(NetworkManager)'
Is there an obvious fix to this?  Thanks.

It appears you have a newer version of Netcode for Gameobjects that is incompatible with the older version of Photon Realtime. You can check by comparing your manifest.json to /Packages/manifest.json.
We haven't yet tested the project with the latest packages, but we found a commit in Photon Realtime that addresses this exact problem.
You can either downgrade you Netcode for Gameobjects to pre5 or upgrade your Photon Realtime.

We're going to consider this issue resolved. If you are still having trouble, please let us know.

Updated to the newer version 2.0.1 of "Photon Realtime Transport for Netcode for GameObjects" which removed the issues above but throw in two new errors in Unity 2021.3.10f1.
Assets\SharedSpaces\Scripts\SharedSpacesSession.cs(28,25): error CS0176: Member 'NetworkManager.ServerClientId' cannot be accessed with an instance reference; qualify it with a type name instead
Assets\SharedSpaces\Scripts\SharedSpacesSession.cs(70,23): error CS0176: Member 'NetworkManager.ServerClientId' cannot be accessed with an instance reference; qualify it with a type name instead


Slash commands Spring like PoC

I'm just opening the PR so we can comment on it

Please read this document before commenting: https://perzoinc.atlassian.net/wiki/spaces/DevX/pages/2306802587/PLAT-11535+Slash+commands+arguments
Thanks

Implementation done in #600


Deserialization issue - object returned unset

I have a class of Customer:
public class Customer
    {
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public int Age { get; set; }
        public string Address { get; set; }
        public Customer()
        {
            FirstName = "First Name Test";
            LastName = "Last Name Test";
            Age = 30;
            Address = "Neverland";
        }
    }

From swagger - json string received as camel case (firstName instead of FirstName in Customer class):
"{\"firstName\":\"myName\",\"lastName\":\"myLastName\",\"age\":0,\"address\":\"myAddress\"}"
Because of this difference, my Customer object in not set with the values and contains the default values from the constructor.  Other serialization libraries can handle this scenario. Is there a solution in utf8json to handle camel-case string where my class contains pascal-case memers?

use attributes
[DataMember(Name = "firsName")]
public string FirstName { get; set; }

or you can set this option global by
// default serializer change to allow private/exclude null/snake_case serializer.
JsonSerializer.SetDefaultResolver(StandardResolver.AllowPrivateExcludeNullSnakeCase);


Querying unmatching fields

Would be nice to allow querying unmatching field ( « ! » for not equal) like :

beet list bitrate!:320000

See #819.


"Service Unavailable" from voip.ms outgoing

seems to happen in clusters. We got this from callcentric too, but in about a month of voip.ms we've gotten 12. What does the user get, a busy signal? User has tried again a few times. IP address is for sanjose.voip.ms.
What should we do about these, failover to a different voip.ms endpoint? Failover to callcentric?
[Dec 13 20:53:28] VERBOSE[11299][C-00000171] pbx.c:     -- Executing [s@macro-di
al:2] Dial("SIP/668-00000239", "SIP/voipms-oskar/...,300") in new stack
[Dec 13 20:53:28] VERBOSE[11299][C-00000171] netsock2.c:   == Using SIP RTP CoS
mark 5
[Dec 13 20:53:28] VERBOSE[11299][C-00000171] app_dial.c:     -- Called SIP/voipm
s-oskar/...
[Dec 13 20:53:40] VERBOSE[1302][C-00000171] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
[Dec 13 20:53:40] VERBOSE[11299][C-00000171] app_dial.c:     -- SIP/voipms-oskar-0000023a is circuit-busy
[Dec 13 20:53:40] VERBOSE[11299][C-00000171] app_dial.c:   == Everyone is busy/congested at this time (1:0/1/0)
[Dec 13 20:53:40] VERBOSE[11299][C-00000171] pbx.c:     -- Auto fallthrough, channel 'SIP/668-00000239' status is 'CONGESTION'
karl@eurydice:/opt/futel/backups/prod/2015-12/opt/asterisk/var/log/asterisk/old$ sudo grep 'Service Unavailable' messages-*
messages-20151120:[Nov 19 23:26:26] VERBOSE[1635][C-000000ad] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151205:[Dec  4 17:01:42] VERBOSE[1302][C-00000031] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151205:[Dec  4 17:02:14] VERBOSE[1302][C-00000032] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151207:[Dec  6 11:50:36] VERBOSE[1302][C-00000070] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151207:[Dec  6 11:51:36] VERBOSE[1302][C-00000072] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151207:[Dec  6 12:06:09] VERBOSE[1302][C-00000079] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151207:[Dec  6 12:29:13] VERBOSE[1302][C-00000099] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151211:[Dec 10 10:12:40] VERBOSE[1302][C-000000fd] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151212:[Dec 11 09:34:28] VERBOSE[1302][C-00000133] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151212:[Dec 11 09:34:55] VERBOSE[1302][C-00000134] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151214:[Dec 13 20:53:40] VERBOSE[1302][C-00000171] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060
messages-20151214:[Dec 13 20:57:19] VERBOSE[1302][C-00000176] chan_sip.c:     -- Got SIP response 503 "Service Unavailable" back from <IP_ADDRESS>:5060

We get a CONGESTION dialstatus after each of these, so we could retry.

we are now retrying once with same peer after congestion

we are now trying again with same provider twice more before giving up and reporting congestion.
01:39  stats 1 691
01:39  most frequent events last 1 days
01:39  outgoing-ivr:82 outgoing-dialtone-wrapper:66
outgoing-dialstatus-ANSWER:7
outgoing-dialstatus-tryagain:4 community-ivr:3
futel-information:2 outgoing-dialstatus-CONGESTION:2
directory-ivr:1 lets-consider:1 voicemail-ivr:1

still happening, this does not affect r2d2 since they're on callcentric, but prospective installation might not be enthused about answering questions about service

we don't use voip.ms for basic outgoing anymore, only operator and payphone shotgun. Hopefully we are avoiding the issue as of r45.


Raspberry Pi - "Connection Refused"

I'm trying to get this setup on a Pi and I keep getting this error when i try to run a test curl from a different machine (same network).
curl: (7) Failed connect to <IP_ADDRESS>:56780; Connection refused
I've verified the IP is correct and there is no error/warning when I run "lifx-http" from the Pi.
Any ideas? is this more related to the pi and/or ruby?  I have ruby 2.1.2 on the Pi.
thanks!

I've run into this problem and tried some of the above suggestions with no luck.
The problems seems to be Rack 1.6.0, downgrading the gem to 1.5.2 worked for me.
'''gem uninstall rack
gem install rack:1.5.2'''


How to generate the heatmap in Fig 10 ?

Hi !
This is an excellent work !
As shown in Fig 10 , i know the heatmaps are generated by Gradcam , but i don't know how to make it , so could u release the related code ?
And i noticed that those heatmaps are relevant to MME , so could i generate it by decoder? just like attention map?
Looking forward to your reply ！

I also want to ask this question.
When I tried to use tools/misc/vis_cam.py, I encountered the following problem:

Traceback (most recent call last):
File "/SimVG/tools/misc/vis_cam.py", line 224, in
main()
File "SimVG/tools/misc/vis_cam.py", line 167, in main
grayscale_cam = det_cam_visualizer(image, targets=targets, aug_smooth=args.aug_smooth, eigen_smooth=args.eigen_smooth)
File "SimVG/simvg/utils/det_cam_visualizer.py", line 268, in call
return self.cam(img, targets, aug_smooth, eigen_smooth)[0, :]
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/pytorch_grad_cam/base_cam.py", line 184, in call
return self.forward(input_tensor,
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/pytorch_grad_cam/base_cam.py", line 74, in forward
outputs = self.activations_and_grads(input_tensor)
File "SimVG/simvg/utils/det_cam_visualizer.py", line 430, in call
return self.model(x)
File "SimVG/simvg/utils/det_cam_visualizer.py", line 162, in call
loss = self.detector(return_loss=True, **self.input_data)[0]
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/mmcv/runner/fp16_utils.py", line 119, in new_func
return old_func(*args, **kwargs)
File "/SimVG/simvg/models/det_seg/base.py", line 25, in forward
return self.forward_train(img, ref_expr_inds, img_metas, **kwargs)
File "SimVG/simvg/models/det_seg/mix_detr_mb.py", line 54, in forward_train
losses_dict, output = self.head.forward_train(
File "/SimVG/simvg/models/heads/tgqs_kd_detr_head/tgqs_kd_detr_head.py", line 458, in forward_train
output = self.forward_general(x_mm, img_metas, cls_feat=cls_feat, text_feat=text_feat, text_mask=text_mask)
File "SimVG/simvg/models/heads/tgqs_kd_detr_head/tgqs_kd_detr_head.py", line 425, in forward_general
hidden_states, _ = self.transformer(x_mm, img_masks, query_embed, pos_embed)
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/SimVG/simvg/models/heads/tgqs_kd_detr_head/transformer.py", line 225, in forward
decoder_output = self.decoder(
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/SimVG/simvg/models/heads/tgqs_kd_detr_head/transformer.py", line 168, in forward
query = layer(
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "/SimVG/tools/detrex/detrex/layers/transformer.py", line 155, in forward
query = self.attentions[attn_index](
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
return forward_call(*args, **kwargs)
File "SimVG/tools/detrex/detrex/layers/attention.py", line 130, in forward
out = self.attn(
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1547, in _call_impl
hook_result = hook(self, args, result)
File "SimVG/simvg/utils/det_cam_visualizer.py", line 411, in save_activation
activation = self.reshape_transform(activation[0])
File "/SimVG/simvg/utils/det_cam_visualizer.py", line 69, in reshape_transform
activations.append(torch.nn.functional.interpolate(torch.abs(feat), max_shape, mode="bilinear"))
File "/home/li/.conda/envs/simvg/lib/python3.10/site-packages/torch/nn/functional.py", line 3959, in interpolate
return torch._C._nn.upsample_bilinear2d(input, output_size, align_corners, scale_factors)
RuntimeError: Non-empty 4D data tensor expected but got a tensor with sizes [1, 0, 20, 20]

我也想问这个问题。 当我尝试使用tools/misc/vis_cam.py (--target-layers: head.transformer.decoder.layers[2].attentions[0].attn ) 时，遇到了以下问题：

RuntimeError: 预期为非空 4D 数据张量，但得到的张量大小为 [1, 0, 20, 20]

When I try to set --target-layers to vis_enc.beit3.encoder.layers[11]. It worked, but the result was obviously wrong


Changes to appregistry and the HTTP appprovider service

To keep track of the changes left from https://github.com/cs3org/reva/pull/1785:

The token expiration time should not be a configurable parameter. Figure out a way to pass that to the HTTP layer without having to dismantle it
Coordinate with the web team to pass the view mode as a parameter to the GET call
Add the option to restrict view modes in apps itself

The changes to be made after the discussion today:

Need to add a new endpoint to the HTTP service which would return all the supported mime types along with the apps that they can be opened with. This would utilize the newly added ListSupportedMimeTypes CS3APIs call. The response would look like:

{
    "mime-types": [
        "text/markdown": [{app_name: "Codimd"}],
        "application/vnd.oasis.opendocument.text": [{app_name: "Collabora"}, {app_name: "OnlyOffice"}, {app_name: "MS Office"}],
        "application/vnd.oasis.opendocument.spreadsheet": [{app_name: "Collabora"}, {app_name: "OnlyOffice"}, {app_name: "MS Office"}],
        ...
    ]
}

Note that we're returning the mime types here instead of the extension because we can add custom types in reva itself and the clients don't need to know about those. Related https://github.com/owncloud/web/issues/5135
We can also return other stuff such as the link to a static asset representing the icon corresponding to the app. Some apps might want to execute some action (eg, via a JS script) so we need to see how those can be passed, but that can be decided later.

The open HTTP endpoint in reva needs to return app-specific (but agnostic to the app provider service) headers and form parameters which would be utilized by web to call the app URL. The main motive is to avoid passing these in the URL which can otherwise expose access tokens following the WOPI specs. After doing a requirement analysis of which apps we're planning on supporting, this payload seems to handle almost all such cases. @wkloucek can you add here your notes about what parameters each app expects?
The open request would have the following parameters

file_id
app_name (optional, in which case the default app is used; if default is not set, the first app in the list is used)
view_mode (optional, in which case we'll use the max permissions the user has on the resource)

To help web identify how the call has to be made to the app, an extra parameter method will be added. For example, two responses can look like:
{
    "app-url": "collabora.owncloud.com/loleaflet/u-u-i-d/loleaflet.html?src=...",
    "method": "POST",
    "form-parameters": {
        "access-token": "reva-token",
        "access-token-ttl": "when-reva-token-expires"
    }
}

{
    "app-url": "jupyterlabs.owncloud.com/src=...",
    "method": "GET",
    "headers": {
        "user-language": "en",
        "user-session-id": 1234
    }
}

The response from WOPI would also be in the form of a JSON object instead of the current way of encoding all parameters in the URI. cc @glpatcern

Based on the permissions and mime-type obtained from the PROPFIND response, the web will display the possible actions possible for each file. Currently, we don't have user-specific or group-specific information or user-defaults so all users and all storages have access to all allowed apps, but this will be the next step to be added. cc @wkloucek

We need to come up with a design to display all the specific actions in web. For example, for a word file, we have 3 apps x 3 view modes. Displaying 9 actions in the drop-down menu doesn't really make up a good UX.

Please add any other points that I might have missed @labkode @wkloucek @glpatcern

Thanks Ishank for the nice summary. Following your list:

I'll create a PR in the wopiserver, I expect we could provide a response to /wopi/iop/openinapp that fully matches the GRPC or HTTP AppProviderResponse, such as:

{
  "app-url" : "collabora.owncloud.com/...",
  "form-parameters" : { "access_token" : "xyz", "access_token_ttl": 123 }
}

(Side-note: who decides the method? shall we rather assume that if form-parameters are empty then method = GET, else POST?)

Just to report my comment: to simplify the UI, in first approximation for the Word case (3x3 actions) one could show a single View action (opens in the default app with READ_ONLY as viewMode) plus the 3 Open with <appname> actions (all in edit mode).

@glpatcern I think the token dismantling should happen in the driver, since the TTL would be decided by the reva token. Maybe wopiserver can just return the token itself.

(Side-note: who decides the method? shall we rather assume that if form-parameters are empty then method = GET, else POST?)

I think this should also be passed from the driver. That way we have a complete URL object being returned as part of the CS3APIs call (URL, form, headers, method). What do you think?

Just to report my comment: to simplify the UI, in first approximation for the Word case (3x3 actions) one could show a single View action (opens in the default app with READ_ONLY as viewMode) plus the 3 Open with  actions (all in edit mode).

+1

For the listing endpoint at /app/list/, we have
$ curl -v -k -X GET 'http://localhost:19001/app/list' | jq
{
  "mime-types": {
    "application/msword": {
      "app_provider_names": [
        "Collabora",
        "Microsoft Office 365"
      ]
    },
    "application/octet-stream": {
      "app_provider_names": [
        "Collabora",
        "Microsoft Office 365"
      ]
    },
    "application/pdf": {
      "app_provider_names": [
        "Microsoft Office 365"
      ]
    },
    "application/rtf": {
      "app_provider_names": [
        "Collabora",
        "Microsoft Office 365"
      ]
    },
    ...
  }
}

@glpatcern I think the token dismantling should happen in the driver, since the TTL would be decided by the reva token. Maybe wopiserver can just return the token itself.

You're absolutely right, my mistake. The wopiserver will definitely not dismantle the Reva token and will only return { "access_token" : "xyz"} - which is on its own not to be dismantled by Reva, so responsibilities stay separated.

I think this should also be passed from the driver. That way we have a complete URL object being returned as part of the CS3APIs call (URL, form, headers, method). What do you think?

Why not, but then if we want the driver to decide the method it could do so based on a config parameter, or on some kind of defaults. E.g. the wopi driver could default to POST (assuming all WOPI apps support it), the swan driver could default to GET, etc.

After doing a requirement analysis of which apps we're planning on supporting, this payload seems to handle almost all such cases. @wkloucek can you add here your notes about what parameters each app expects?

Collabora / MS Office Online (WOPI)

WOPIsrc
access_token
access_token_ttl (valid until -> unix timestamp milliseconds)
there are more parameters which could be used in the future and are already used by oC10: language, revisionhistory, title, closebutton

CodiMD ( (WOPI Bridge)

docid
userName
metadata
t (access token)

Etherpad (WOPI Bridge)

docid
metadata
t (access token)
apiKey
displayName

Only Office

filetype
key
title
url
document type

Jupyter / SWAN

?

@wkloucek I'll be discussing with @butonic today about a way to have finer controls for sharing permissions and I can fold in this requirement for view-only mode.

I concur we need a view-only "value" in the set of permissions, and I started to do some some work in this direction in the context of the deny permission implementation. Let's review what we have.

we could introduce some scope for the ListSupportedMimeTypes dependent on which client is requesting the list.

I think we can add this filtering to the HTTP service instead of CS3APIs as it doesn't really fit there.

HTTP response for Collabora, which supports POST
» curl -v -k -X POST 'http://localhost:19001/app/open?file_id=MTIzZTQ1NjctZTg5Yi0xMmQzLWE0NTYtNDI2NjU1NDQwMDAwOmZpbGVpZC1laW5zdGVpbiUyRnNhbXBsZS5kb2M=&view_mode=write&app_name=Collabora' -u einstein:relativity | jq

* Server auth using Basic with user 'einstein'
> POST /app/open?file_id=MTIzZTQ1NjctZTg5Yi0xMmQzLWE0NTYtNDI2NjU1NDQwMDAwOmZpbGVpZC1laW5zdGVpbiUyRnNhbXBsZS5kb2M=&view_mode=write&app_name=Collabora HTTP/1.1
> Authorization: Basic ZWluc3RlaW46cmVsYXRpdml0eQ==
> User-Agent: curl/7.29.0
> Host: localhost:19001
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Vary: Origin
< Date: Tue, 10 Aug 2021 14:43:19 GMT
< Content-Length: 1842
<
{
  "app_url": "https://collabora-online.cern.ch/byoa/collabora/loleaflet/78239aa/loleaflet.html?&WOPISrc=https%3A%2F%2Fcbox-wopiocis-01.cern.ch%3A8443%2Fwopi%2Ffiles%2F123e4567-e89b-12d3-a456-426655440000-ZmlsZWlkLWVpbnN0ZWluJTJGc2FtcGxlLmRvYw%3D%3D",
  "method": "POST",
  "form_parameters": {
    "access_token": "eyJ0eXAiOiJKV1QiLC...",
    "access_token_ttl": "1628693306"
  }
}

Response for CodiMD, which doesn't
» curl -v -k -X POST 'http://localhost:19001/app/open?file_id=MTIzZTQ1NjctZTg5Yi0xMmQzLWE0NTYtNDI2NjU1NDQwMDAwOmZpbGVpZC1laW5zdGVpbiUyRmEubWQ=&view_mode=write&app_name=CodiMD' -u einstein:relativity | jq

* Server auth using Basic with user 'einstein'
> POST /app/open?file_id=MTIzZTQ1NjctZTg5Yi0xMmQzLWE0NTYtNDI2NjU1NDQwMDAwOmZpbGVpZC1laW5zdGVpbiUyRmEubWQ=&view_mode=write&app_name=CodiMD HTTP/1.1
> Authorization: Basic ZWluc3RlaW46cmVsYXRpdml0eQ==
> User-Agent: curl/7.29.0
> Host: localhost:19001
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Vary: Origin
< Date: Tue, 10 Aug 2021 14:41:28 GMT
< Content-Length: 1824
<
{
  "app_url": "https://qa.cernbox.cern.ch/byoa/codimd/GkG6Q6WLEd4GeGc7fm7EQlQ31H8?metadata=https%3A%2F%2Fcbox-wopiocis-01.cern.ch%3A8443%2Fwopi%2Ffiles%2F123e4567-e89b-12d3-a456-426655440000-ZmlsZWlkLWVpbnN0ZWluJTJGYS5tZA%3D%3D%3Ft%3DeyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2Vya...&apiKey=testsecret&displayName=einstein",
  "method": "GET"
}

Wopiserver changes by @glpatcern: https://github.com/cs3org/wopiserver/pull/43

One thing we didn't talk about is what we should display in the New file dialog:

Technically we just have the mimetypes (see https://github.com/cs3org/reva/issues/1923#issuecomment-891908827) available, but these are not really user friendly (eg. create new application/vnd.oasis.opendocument.text doesn't come in handy for non technical people).
Do you have any ideas? Maybe add a human friendly file name to the mimetype? (I see L10N challenges incoming....)
cc @kulmann

@wkloucek maybe we can expand the mapping of mimetypes with a new field "display name" that is more user friendly?

@wkloucek maybe we can expand the mapping of mimetypes with a new field "display name" that is more user friendly?

there is PR on that in the CSapis: https://github.com/cs3org/cs3apis/pull/145/files. Will have a look next week

Yep, I just created that PR for this use case indeed


Update wasm-go.md

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


Implement Debug on most of the types

Can you please be a bit more specific? This is very difficult since [T; N] with N > 32 does not implement Debug.

Wow, seems like I was using {} instead of {:?}. Sorry...


fix(amplify-cli-core): extend js-yaml.JSON_SCHEMA to inherit json type conversions when parsing .yml cfn templates

Description of changes

Instead of creating a js-yaml schema that only contains conversions for cloudformation intrinsic
functions, we extend the built-in JSON-SCHEMA to inherit type conversions for bools, ints,
floats, etc.
See https://github.com/nodeca/js-yaml#load-string---options-
Issue #, if available

fix #7819
Description of how you validated changes

Parsed yaml cloudformation templates with boolean, number, and float values, and observed correct types in the returned object
yarn test
yarn lint

Checklist

[X] PR description included
[X] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you add some regression tests.

Yeah, for sure!


Installomator stuck in loop trying to quit older version of 1password7 for update

This may be related to #89, but I am also seeing issues when Installomator tries to update an older version of 1password7 that is running to install the newer version. The script appears to get stuck in a loop trying & failing to stop the various 1password7 components before updating. In my test case it was the main 1password7 app & the safari extension, but I've also see others report it flipping between the main 1password7 app and "1PasswordNativeMessageHost". There may be others as well. In my case, I confirmed in the process table the same PIDs remain running through multiple attempts to quit them via the pop-ups from the script. I have also attached output of the script stepping through my case to assist: 1pass.txt

Getting this same bug on my end, going to normal patch management of this app until this gets resolved

@andrewchenWP can you expand on what "normal patch management" you are using for 1Password7?

is this still an issue with v9.2 (and more importantly 1password8)?

I can confirm this is still an issue with v9.2 & 1password7. I have not yet installed/tested 1password8, though I expect the behavior will be the same.
I will also point out that while trying to test with v9.1 I found that killing the parent jamf process while Installomator was sleeping before re-checking if there were still any running processes resulted in jamf thinking Installomator had exited successfully when it had not. I can open up another issue for that, but below is the log I found in the jamf policy:

Script result: 2022-06-09 15:34:02 : REQ   :  : shifting arguments for Jamf
2022-06-09 15:34:02 : REQ   : 1password7 : ################## Start Installomator v. 9.1, date 2022-03-18
2022-06-09 15:34:02 : INFO  : 1password7 : ################## Version: 9.1
2022-06-09 15:34:02 : INFO  : 1password7 : ################## Date: 2022-03-18
2022-06-09 15:34:02 : INFO  : 1password7 : ################## 1password7
2022-06-09 15:34:03 : INFO  : 1password7 : BLOCKING_PROCESS_ACTION=tell_user
2022-06-09 15:34:03 : INFO  : 1password7 : NOTIFY=success
2022-06-09 15:34:03 : INFO  : 1password7 : LOGGING=INFO
2022-06-09 15:34:03 : INFO  : 1password7 : LOGO=/System/Applications/App Store.app/Contents/Resource
s/AppIcon.icns
2022-06-09 15:34:03 : INFO  : 1password7 : Label type: pkg
2022-06-09 15:34:03 : INFO  : 1password7 : archiveName: 1Password 7.pkg
2022-06-09 15:34:03 : INFO  : 1password7 : App(s) found: /Applications/1Password 7.app
2022-06-09 15:34:03 : INFO  : 1password7 : found app at /Applications/1Password 7.app, version 7.9.2, on versionKey CFBundleShortVersionString
2022-06-09 15:34:03 : INFO  : 1password7 : appversion: 7.9.2
2022-06-09 15:34:03 : INFO  : 1password7 : Latest version of 1Password 7 is 7.9.5
2022-06-09 15:34:03 : REQ   : 1password7 : Downloading https://app-updates.agilebits.com/download/OPM7 to 1Password 7.pkg
2022-06-09 15:34:08 : INFO  : 1password7 : found blocking process 1Password 7
2022-06-09 15:34:10 : INFO  : 1password7 : telling app 1Password 7 to quit
26:30: execution error: 1Password 7 got an error: User canceled. (-128)
2022-06-09 15:34:10 : INFO  : 1password7 : waiting 30 seconds for processes to quit
2022-06-09 15:34:41 : INFO  : 1password7 : found blocking process 1PasswordSafariAppExtension
2022-06-09 15:34:42 : INFO  : 1password7 : telling app 1PasswordSafariAppExtension to quit
42:46: execution error: 1PasswordSafariAppExtension.appex got an error: Can’t continue quit. (-1708)
2022-06-09 15:34:42 : INFO  : 1password7 : waiting 30 seconds for processes to quit
2022-06-09 15:35:12 : INFO  : 1password7 : found blocking process 1Password 7
2022-06-09 15:38:49 : INFO  : 1password7 : telling app 1Password 7 to quit
26:30: execution error: 1Password 7 got an error: User canceled. (-128)
2022-06-09 15:38:49 : INFO  : 1password7 : waiting 30 seconds for processes to quit

To update 1Password error-free, all web browsers must be quit and especially the LaunchAgent must be stopped before. We use this PR https://github.com/Installomator/Installomator/pull/574 with the new function LaunchAgentToStop (see https://github.com/Installomator/Installomator/pull/574#issuecomment-1152433059) and the following adjustments in the label:
1password7)
    name="1Password 7"
    type="pkg"
    downloadURL="https://app-updates.agilebits.com/download/OPM7"
    appNewVersion=$( curl -fsIL "${downloadURL}" | grep -i "^location" | awk '{print $2}' | sed -E 's/.*\/[0-9a-zA-Z]*-([0-9.]*)\..*/\1/g' )
    expectedTeamID="2BUA8C4S2C"
    LaunchAgentsToStop=( 2BUA8C4S2C.com.agilebits.onepassword7-helper )
    blockingProcesses=( "Safari" "1Password (Safari)" "1PasswordSafariAppExtension" "Google Chrome" "firefox" "1Password 7" "1Password Extension Helper" )
    ;;

Installomator-Logfile for this 1password7 label:
2022-06-13 19:18:52 : REQ   : 1password7 : ################## Start Installomator v. 10.0beta, date 2022-05-19
2022-06-13 19:18:52 : INFO  : 1password7 : ################## Version: 10.0beta
2022-06-13 19:18:52 : INFO  : 1password7 : ################## Date: 2022-05-19
2022-06-13 19:18:52 : INFO  : 1password7 : ################## 1password7
2022-06-13 19:18:53 : INFO  : 1password7 : BLOCKING_PROCESS_ACTION=tell_user
2022-06-13 19:18:53 : INFO  : 1password7 : NOTIFY=success
2022-06-13 19:18:53 : INFO  : 1password7 : LOGGING=INFO
2022-06-13 19:18:53 : INFO  : 1password7 : LOGO=/Library/Application Support/AAOC/AOAppIcon.icns
2022-06-13 19:18:53 : INFO  : 1password7 : Label type: pkg
2022-06-13 19:18:53 : INFO  : 1password7 : archiveName: 1Password 7.pkg
2022-06-13 19:18:53 : INFO  : 1password7 : App(s) found: /Applications/1Password 7.app
2022-06-13 19:18:53 : INFO  : 1password7 : found app at /Applications/1Password 7.app, version 7.9.4, on versionKey CFBundleShortVersionString
2022-06-13 19:18:53 : INFO  : 1password7 : appversion: 7.9.4
2022-06-13 19:18:53 : INFO  : 1password7 : Latest version of 1Password 7 is 7.9.5
2022-06-13 19:18:53 : REQ   : 1password7 : Downloading https://app-updates.agilebits.com/download/OPM7 to 1Password 7.pkg
2022-06-13 19:19:00 : INFO  : 1password7 : stopping 2BUA8C4S2C.com.agilebits.onepassword7-helper LaunchAgent
2022-06-13 19:19:00 : INFO  : 1password7 : found blocking process Safari
2022-06-13 19:19:04 : INFO  : 1password7 : telling app "Safari" to quit
2022-06-13 19:19:09 : INFO  : 1password7 : sending SIGTERM to PID 24228: /System/Library/PrivateFrameworks/SafariShared.framework/Versions/A/XPCServices/com.apple.Safari.SearchHelper.xpc/Contents/MacOS/com.apple.Safari.SearchHelper
2022-06-13 19:19:09 : INFO  : 1password7 : sending SIGTERM to PID 43992: /System/Library/PrivateFrameworks/SafariShared.framework/Versions/A/XPCServices/com.apple.Safari.History.xpc/Contents/MacOS/com.apple.Safari.History
2022-06-13 19:19:09 : INFO  : 1password7 : sending SIGTERM to PID 49563: /System/Library/PrivateFrameworks/SafariSafeBrowsing.framework/com.apple.Safari.SafeBrowsing.Service
2022-06-13 19:19:09 : INFO  : 1password7 : sending SIGTERM to PID 53856: /Library/Apple/System/Library/CoreServices/SafariSupport.bundle/Contents/MacOS/SafariBookmarksSyncAgent
2022-06-13 19:19:15 : INFO  : 1password7 : sending SIGKILL to PID 49563: /System/Library/PrivateFrameworks/SafariSafeBrowsing.framework/com.apple.Safari.SafeBrowsing.Service
2022-06-13 19:19:18 : INFO  : 1password7 : found blocking process Google Chrome
2022-06-13 19:19:24 : INFO  : 1password7 : telling app "Google Chrome" to quit
2022-06-13 19:19:29 : INFO  : 1password7 : found blocking process 1Password 7
2022-06-13 19:19:35 : INFO  : 1password7 : telling app "1Password 7" to quit
26:30: execution error: „1Password 7“ hat einen Fehler erhalten: Von Benutzer:in abgebrochen. (-128)
26:30: execution error: „1Password 7“ hat einen Fehler erhalten: Von Benutzer:in abgebrochen. (-128)
2022-06-13 19:19:45 : INFO  : 1password7 : sending SIGTERM to PID 6766: /Applications/1Password 7.app/Contents/MacOS/1Password 7
2022-06-13 19:19:53 : REQ   : 1password7 : no more blocking processes, continue with update
2022-06-13 19:19:53 : REQ   : 1password7 : Installing 1Password 7
2022-06-13 19:19:53 : INFO  : 1password7 : Verifying: 1Password 7.pkg
2022-06-13 19:19:54 : INFO  : 1password7 : Team ID: 2BUA8C4S2C (expected: 2BUA8C4S2C )
2022-06-13 19:19:54 : INFO  : 1password7 : Installing 1Password 7.pkg to /
2022-06-13 19:20:20 : INFO  : 1password7 : Finishing...
2022-06-13 19:20:30 : INFO  : 1password7 : App(s) found: /Applications/1Password 7.app
2022-06-13 19:20:30 : INFO  : 1password7 : found app at /Applications/1Password 7.app, version 7.9.5, on versionKey CFBundleShortVersionString
2022-06-13 19:20:30 : REQ   : 1password7 : Installed 1Password 7, version 7.9.5
2022-06-13 19:20:30 : INFO  : 1password7 : notifying
2022-06-13 19:20:30 : INFO  : 1password7 : Telling app 1Password 7.app to open
2022-06-13 19:20:31 : INFO  : 1password7 : Reopened 1Password 7.app as xy
2022-06-13 19:20:31 : REQ   : 1password7 : All done!
2022-06-13 19:20:31 : REQ   : 1password7 : ################## End Installomator, exit code 0```


fix($$sanitizeUri): Anchor data:image/ clause in regex.

The existing regex would pass image uris if "data:image/" appeared anywhere.

This was fixed in b7e82a33eee03fc683f982c6ee13d15d88b07f67


wine: Avoid rebuilding on any nixpkgs src change

Previously, the input here was inputs.nixpkgs. That meant that any change at all in nixpkgs, to any file, would result in a rebuild. Since we only depend on files in one dir, use builtins.path to filter nixpkgs to just that dir so that we only depend on changes to that dir, greatly minimizing unnecessary rebuilds.
Strictly speaking, this is only needed when the path is not used in an import (callPackage also being an import). However, there’s little downside to using this path instead for those as well, and it hopefully reduces the probability that someone will copy-paste a path using inputs.nixpkgs and use it in a non-import thereby causing the same problem again.

Great idea, thanks!


Update to sbt 1.8.3 and fix deprecation warnings

Closes #150

Abort, will leave sbt 0.13 support for now. Should probably drop in a 2.x (maybe once scapegoat supports scala 3?)


Update dependencies

Upgrade dependencies for build break.

Pull Request Test Coverage Report for Build 596985486

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.008%) to 43.464%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 594133608:
-0.008%

Covered Lines:
24937

Relevant Lines:
52550

💛  - Coveralls


Delete and unload model from server through API

Feature request
rasa NLU version (e.g. 0.7.3):
0.8.10
Used backend / pipeline (mitie, spacy_sklearn, ...):
spacy_sklearn
Operating system (windows, osx, ...):
Docker/Linux
Issue:
Add an REST DELETE API for deleting an available model. As of 0.8.10 the workaround is to delete the trained model folder from the parent /models folder.
The Delete API should not just delete the folder but clean up any internal data structures holding the model trained data - basically untrain the model.
Content of configuration file (if used & relevant):

That sounds like a good addition :+1:


Accessibility testing the download and confirm screens

Description/Scope:
Hoping to have manual accessibility testing done on the screens and interaction of the download and confirm screens
Acceptance Criteria:

[ ] Conduct test
[ ] Create tickets in the "New Issues" column, tagged with "a11y"
[ ] Outline impact of the issue and how it affects different PwDs
[ ] Tickets will be reviewed by PM for prioritization with recommendations from dev

Completed during testing last week.


Fade after win

Fades to black after killing the monster. Design document says white, but I could not get that working consistently with our existing capabilities. Still, we want some kind of fading in other places and this works quite well if we can not get fading to white to work properly.

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 ScriptManager.cpp#L115: Variable 'callstack' is assigned a value that is never used.
 ScriptManager.cpp#L116: Variable 'variables' is assigned a value that is never used.
 ScriptManager.cpp#L611: The function 'ClearBreakpoints' is never used.
 ScriptManager.cpp#L824: The function 'GetStringDeclarationID' is never used.
 ScriptManager.cpp#L830: The function 'GetScripts' is never used.

SonarQube analysis reported 6 issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 AncientFungus:LGEPR: Cppcheck cannot find all the include files (use --check-config for details)
 ScriptManager.cpp#L115: Variable 'callstack' is assigned a value that is never used.
 ScriptManager.cpp#L116: Variable 'variables' is assigned a value that is never used.
 ScriptManager.cpp#L611: The function 'ClearBreakpoints' is never used.
 ScriptManager.cpp#L853: The function 'GetStringDeclarationID' is never used.
 ScriptManager.cpp#L859: The function 'GetScripts' is never used.


Header elements not including margins matching GDS styles

GDS styles for heading-* classes have a margin-top set dependent upon the chosen size.  Currently these are not set by Header.

It appears that the manner in which heading elements are styled has changed, and that the base sass in https://github.com/alphagov/govuk-frontend/blob/master/src/globals/core/_typography.scss has a margin-top: 0 defined for headings
Will investigate further

Spoke to @Loque- about this yesterday, they appear to have a margin-bottom as well https://govuk-elements.herokuapp.com/typography/

check this out for instance, there's always a small margin between the herading and the start of the paragraph https://www.gov.uk/universal-credit

@hom-bahrani I'm currently working through a solution for spacing sections apart without resorting to applying margin-top to elements. It might take a while to get the spec down and an implementation that the majority approves on released on govuk-react, however I hope to have some concept ideas using the spacing constants that anyone could drop in and use in the meantime. Will update here as soon as I have something worth sharing!

@hom-bahrani I have created several examples for using the layout components, and spacing constants within govuk-react for rendering layout here: https://codesandbox.io/s/x917knwm4z
@stevesims I believe this implementation answers any concerns over the removal of margin-top from our components.


How/what to test when testing vue components

Hi,
I would like to contribute to the cookbook, regarding how and what to test when testing Vue components.
I wrote this for the vue-test-utils documentation recently. I also write a lot about testing Vue components here, so maybe something based on those articles.
The main things I want to convey are

what is in the scope of unit tests
when to mock/stub
common pitfalls

Edit: I do not know how to assign a label.

Sounds like a great addition! We'd love to have something like this in the cookbook. You probably already found it, but there's a template we ask people to work from in the cookbook section. Let me know if you need anything else to get started. 🎉

You did it! Congrats! Thank you for your contribution 🙏


Syntax errors in VisItLibraryDependencies.cmake with macOS .dmg

Describe the bug
After implementing the workaround suggested in #3807, I was able to use xmledit on my macOS platform. However, when trying to run cmake -DCMAKE_BUILD_TYPE:STRING=Debug -Wno-dev, the process fails:
(base) K-MBP% cmake -DCMAKE_BUILD_TYPE:STRING=Debug -Wno-dev
CMake Warning:
  No source or binary directory provided.  Both will be assumed to be the
  same as the current working directory, but note that this warning will
  become a fatal error in future CMake releases.

CMake Warning at /Applications/VisIt.app/Contents/Resources/3.0.1/darwin-x86_64/include/PluginVsInstall.cmake:133 (message):
  C compiler used for VisIt (/usr/bin/clang)

  differs from the one used for the current project!

  (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc)
  They may be incompatible.
Call Stack (most recent call first):
  CMakeLists.txt:4 (INCLUDE)

CMake Warning at /Applications/VisIt.app/Contents/Resources/3.0.1/darwin-x86_64/include/PluginVsInstall.cmake:139 (message):
  C++ compiler used for VisIt (/usr/bin/clang++)

  differs from the one used for the current project!

  (/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++)
  They may be incompatible.
Call Stack (most recent call first):
  CMakeLists.txt:4 (INCLUDE)

CMake Error at /Applications/VisIt.app/Contents/Resources/3.0.1/darwin-x86_64/include/VisItLibraryDependencies.cmake:32:
  Parse error.  Function missing ending ")".  End of file reached.
Call Stack (most recent call first):
  CMakeLists.txt:5 (INCLUDE)

CMake Error at CMakeLists.txt:5 (INCLUDE):
  INCLUDE could not find load file:

    /Applications/VisIt.app/Contents/Resources/3.0.1/darwin-x86_64/include/VisItLibraryDependencies.cmake

-- Configuring incomplete, errors occurred!

The errors do not occur with a Linux build of the same VisIt version on a cluster at Princeton. It seems as though the VisItLibraryDependencies.cmake file is mangled (missing closing quotation marks, parentheses, etc.)
Desktop

OS and version: macOS Mojave 10.14.6
VisIt Version: 3.0.1
cmake version 3.15.2

Hello Kyle,
These are known issues with 3.0.1 which have been resolved for our
upcoming 3.0.2 release. Unfortunately, I don't think there is a
workaround.
Kathleen
On Mon, 2019-08-26 at 14:18 -0700, Kyle Gerard Felker wrote:

I was able to get the cmake command to complete successfully by
commenting out the following 2x problematic lines in
VisItLibraryDependencies.cmake:
  * L32 set(cognomen_LIB_DEPENDS "general"
  * L41 set(mpicom_LIB_DEPENDS "general;
    ${VISIT_LIBRARY_DIR}/libpython2.7.dylib;general

but I don't know if this will just create issues later on in the build
process.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Chaitanya sbuttons

Fix watch command & Logo Added
watch for both less and sass for any changes anywhere included. lite-server added for live updates of the page
npm install to install all dependencies
npm start will compile,build and run the project in lite-server updating changes in live
Added Logos together with few alternatives

Hi @chaitanya4vedi thank you for the great work!
Can you please split the work for the two issues into two pull requests? i.e. keep this issue for fixing the watch command, remove the changes related to the logo and add them to a new issue. It's better to keep track of everything.
I'll edit the title as well to make it more related to the watch issue.

Also, there are changes in files like .idea, cache etc... if you can remove those changes from the pull request it would be great!

new pull request created for watch and logo individually

Done


Support model validation attributes in JsonPatch

When using JsonPatch, model validation attributes that are added to the class used as type parameter for JsonPatchDocument are not picked up when calling the ApplyTo-method.
It would be nice if the call to ApplyTo-method would also check against validation attributes added to the properties for which the PATCH operations are applied.

We don't plan to support this, but you can call TryValidateModel yourself.


Fix few custom visual shaders methods after StringName introduction

Hmm.. or maybe this is intended and should not be changed..


[WIP] ACN aea to open-aea

Proposed changes
changing aea-ledger-x to open-aea-ledger-x in connection.yaml's of the libp2p* modules
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[ ] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Codecov Report

Merging #114 (ca24f33) into main (9863c0e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #114   +/-   ##
=======================================
  Coverage   96.92%   96.92%
=======================================
  Files         301      301
  Lines       23920    23920
=======================================
  Hits        23185    23185
  Misses        735      735

Flag
Coverage Δ

unittests
96.92% <ø> (ø)

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

Continue to review full report at Codecov.

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


Rewrite all examples in the Literate format

[ ] GHZ
[ ] QFT
[ ] XEB
[ ] Finite temperature
[ ] Quantum state tomography
[ ] Quantum process tomography
[ ] VQE
[ ] Monitored quantum circuits

Any chance you've tried Weave?

I did not try it. But Literate works pretty well. Any specific reason you prefer one above the other?

No, I haven't really used either one. Whenever I've looked into this sort of thing I've come across both and didn't really understand the difference between the two. There is some discussion here: https://discourse.julialang.org/t/ann-literate-jl/10651/15
Just thought it was good to bring up the options before committing a lot of work to one or the other, in case there was some feature one had that the other didn't that we would miss out on.


Update log4cats-slf4j to 2.5.0

Updates org.typelevel:log4cats-slf4j from 2.4.0 to 2.5.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "log4cats-slf4j" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.typelevel", artifactId = "log4cats-slf4j" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report
Base: 88.79% // Head: 88.76% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (9288e14) compared to base (e8c2a3c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #355      +/-   ##
==========================================
- Coverage   88.79%   88.76%   -0.04%
==========================================
  Files          91       91
  Lines        2812     2812
  Branches      157      157
==========================================
- Hits         2497     2496       -1
- Misses        315      316       +1

Impacted Files
Coverage Δ

src/main/scala/kinesis/mock/cache/Cache.scala
83.58% <0.00%> (-0.18%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


User testing clean up

What?

Delete data simulation.
Delete persistence.
Delete event parsing.
Fix failing unit tests.
Disable failing tests for Wire.CursorType
Set PusherPlatform dependency to version 0.7.3.
Set Beams dependency to version 3.0.1.
Delete CryptoSwift dependency.
Remove unused Integration Tests target.

Why?
Delete unused code that should not be part of the finial implementation of the version 2 of the SDK.

          1 Warning

:warning:
Any changes to library code should be reflected in the Changelog. Please consider adding a note there. \nYou can find it at CHANGELOG.md.

  Generated by :no_entry_sign: Danger


Make DifferentiateWith compatible with ForwardDiff, clarify docs

DIT source

Clarify documentation of DifferentiateWith, mention compositions.

DIT extensions

Make DifferentiateWith compatible with ForwardDiff through Dual and AbstractArray{<:Dual} overloads

DI tests

Test DifferentiateWith for Zygote and ForwardDiff on the closurified backends, using FiniteDiff as substitute

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

Project coverage is 0.14%. Comparing base (5750b31) to head (3b472fc).
Report is 1 commits behind head on main.

:exclamation:  There is a different number of reports uploaded between BASE (5750b31) and HEAD (3b472fc). Click for more details.
HEAD has 55 uploads less than BASE

Flag
BASE (5750b31)
HEAD (3b472fc)

DIT
10
1

DI
46
0

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #487       +/-   ##
==========================================
- Coverage   98.51%   0.14%   -98.37%
==========================================
  Files         107      19       -88
  Lines        4298    1392     -2906
==========================================
- Hits         4234       2     -4232
- Misses         64    1390     +1326

Flag
Coverage Δ

DI
?

DIT
0.14% <ø> (-98.23%)
:arrow_down:

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

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


rodio::Source not satisfied error on implementation identical to example

Hello,
I'm writing a program with the hope that I can use redlux with rodio, and so I looked at the examples and just copied and pasted the m4a example to see how it worked - however, I can't seem to get it to compile, with the error

let decoder = Decoder::new_mpeg4(buf, size).expect("Error creating M4aDecoder");
the trait bound redlux::Decoder<std::io::BufReader<std::fs::File>>: rodio::Source is not satisfied
the trait rodio::Source is not implemented for redlux::Decoder<std::io::BufReader<std::fs::File>>rustc(E0277)
mod.rs(19, 17): the trait rodio::Source is not implemented for redlux::Decoder<std::io::BufReader<std::fs::File>>

Always appearing on the sink.append(decoder) line. More specifically, this is my implementation (essentially a copy/paste, but with an argument instead of a hard-coded path)
use redlux::Decoder;
use rodio::{OutputStream, Sink};
use std::fs::File;
use std::io::BufReader;

fn play_mp4(path: &String) {
    let file = File::open(path).expect("Error opening file");

    let metadata = file.metadata().expect("Error getting file metadata");
    let size = metadata.len();
    let buf = BufReader::new(file);

    let decoder = Decoder::new_mpeg4(buf, size).expect("Error creating M4aDecoder");

    let output_stream = OutputStream::try_default();
    let (_stream, handle) = output_stream.expect("Error creating output stream");
    let sink = Sink::try_new(&handle).expect("Error creating sink");

    sink.append(decoder);
    sink.play();
    sink.set_volume(0.25);
    sink.sleep_until_end();
}

The reason is that redlux depends on rodio 0.13.0, so using it with a version like 0.14.0 gives this error.
Not 100% sure if I should just publish a patch that adds rodio 0.14.* or something else

Fixed in 43b83580fdc68ad79e145ec26d5c1fc57148d0a5


fix(client): bundle types from @prisma/debug and @opentelemetry/api

Fix failing ecosystem tests by bundling the types.
Ref: https://github.com/prisma/prisma/pull/14537
Ref: https://github.com/prisma/prisma/pull/14533

Bug still exists after merging because the produced types aren't bundled correctly.


Handle 'P1 & P2 -> P3 & P4' expression.

This PR is a set of several changes regarding TypeExpr construction.

Handle P1 & P2 -> P3 & P4 expression
Previously, ArrowExpr had wrong assumption where LHS is already a TypeExpr, and RHS is TypeExpr or an another ArrowExpr (e.g. Int -> Int -> Int).
That was OK before SR-0095, but not now.
Instead, we should always recurse simplifyTypeExpr().
Now, (P1 & P2 -> P3 & P4) is successfully converted to TypeExpr as expected.
This resolves one of TODO in https://github.com/apple/swift/pull/5290

Adjust the precedence of -> operator
Previous FunctionArrowPrecedence was too low. = was stronger than ->.
_ = () -> Int was folded as:
(arrow
  (assign
    (discard_assignment_expr)
    (tuple_expr))
  (unresolved_declref))

Instead, it should be:
(assign
  (discard_assignment_expr)
  (arrow
    (tuple_expr)
    (unresolved_declref)))

Technically, this is a source breaking change.
But I think, we can assume no one rely on this behavior.

Recursively pre check folded sequence expression
try () -> Int is a single sequence expression. foldSequece() folds this as
(try (arrow (tuple) (declref 'Int'))). Since simplifyTypeExpr() can't handle this,
the ArrowExpr was not been converted to TypeExpr.
And since constraint system does not handle ArrowExpr at all, that used to cause Verifier error.
virtual std::pair<bool, Expr *> (anonymous namespace)::Verifier::walkToExprPre(swift::Expr *):
Assertion `(HadError || !M.is<SourceFile*>() || M.get<SourceFile*>()->ASTStage < SourceFile::TypeChecked) &&
"Arrow" "in wrong phase"' failed.

This change resolves that by recursively pre-check folded expression.

Never give up converting ArrowExpr to TypeExpr
1 -> Int case, folded as (arrow (integer_literal '1') (declref 'Int')).
Since integer literal can not be TypeRepr, previous behavior leave ArrowExpr AS IS.
Instead, we should construct TypeRepr as (function (error) (ident 'Int')).
So that we don't let ArrowExpr loose in wild.

Can you also add tests to stdlib/TypeName.swift to make sure these types print correctly too?

👍 @slavapestov done.

@swift-ci please smoke test

@swift-ci please smoke test.

Looks like the compiler crasher was resolved already by another PR.

https://github.com/apple/swift/pull/5878 introduced a conflict.
Rebased on the master.

@swift-ci Please smoke test


Make a first release before removing Python 2

I plan to clean a bit the test system (inspired by some work I did on enaml) and I will take advantage of this to remove all mentions of Python 2 compatibility (from the code and from the docs). As it may cause some issues to some people it would be best to get the 0.1.0 out first.
Is there any outstanding issue you would like to see fixed before @Ecpy/owners ?

Do the people in Lyon have an opinion on this ? @ncottet, @bhuard

I have no idea what you're talking about. What is the 0.1.0?
We agree that ecpy is not compatible with Python 2 anyway right?
Benjamin

For the time being ecpy supports Python 2. The idea is yo reduce the maintenance burden by only supporting Python 3.5 and 3.6 in the future. So I was suggesting to tag a release (version number 0.1.0) that would be the last to support Python 2 before cleaning up the codebase.

Ok great!
Le jeu. 5 oct. 2017 à 08:29, Matthieu Dartiailh<EMAIL_ADDRESS>a écrit :

For the time being ecpy supports Python 2. The idea is yo reduce the
maintenance burden by only supporting Python 3.5 and 3.6 in the future. So
I was suggesting to tag a release (version number 0.1.0) that would be the
last to support Python 2 before cleaning up the codebase.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Ecpy/ecpy/issues/115#issuecomment-334371078, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGIrosTOQI92XTcs6cIt4J5vHFv-aSudks5spHcvgaJpZM4Pg4az
.

We have been using Python 3 for Ecpy from the beginning so this will definitely not impact us. I think what you propose is the best way to do it.

Ok thanks. I will do this when I can find some time to do so then.

Done


Support Swift Tools Version 5+

Is your feature request related to a problem? Please describe.
The Package.swift specifies: // swift-tools-version:4.0
When creating Swift Package with out source code and only a XCFramework, with a dependency on this Swift Package, the generated swift interface files generate build errors when imported to a new project thru SPM: 'XMLIndexerDeserializable' is not a member type of 'SWXMLHash'
Describe the solution you'd like
Support for swift tools 5+ in the Swift Package.
Describe alternatives you've considered
Drop the supported swift tools version level in my own swift package to match, however, earlier version do not support XCFrameworks.
Additional context
Full transparency, I've had a hard time finding documentation and support (e.g. stackoverflow) specific to Swift Packages made of XCFramework binaries with dependencies on other swift packages. It is possible this is not the reason for build issues I am experiencing, but I am hoping this package can still take that step forward to support new swift tools versions.

So, I'm not sure I'm following... the Package.swift file (see https://github.com/drmohundro/SWXMLHash/blob/main/Package.swift#L1) has // swift-tools-version:5.3 at the top, but your comment says it has 4.0 in it? Am I misunderstanding?

So, I'm not sure I'm following... the Package.swift file (see https://github.com/drmohundro/SWXMLHash/blob/main/Package.swift#L1) has // swift-tools-version:5.3 at the top, but your comment says it has 4.0 in it? Am I misunderstanding?

Well, that is embarrassing. I was looking at your latest tagged release. I see now it is in main. I guess I just need to wait for a new release. Apologies for the confusion.

Well, that is embarrassing. I was looking at your latest tagged release. I see now it is in main. I guess I just need to wait for a new release. Apologies for the confusion.

No, no worries. And maybe the issue you're seeing is that I just need to tag the latest commit on main. To be honest, thus far most usage of the library has been through CocoaPods or Carthage which I know takes the git tag into account; however, I'm honestly not sure if Swift Package Manager uses that or not. If it looks like it does, then I can pretty easily add in a new minor tag version to take that into account, though.

No, no worries. And maybe the issue you're seeing is that I just need to tag the latest commit on main. To be honest, thus far most usage of the library has been through CocoaPods or Carthage which I know takes the git tag into account; however, I'm honestly not sure if Swift Package Manager uses that or not. If it looks like it does, then I can pretty easily add in a new minor tag version to take that into account, though.

I pushed a 5.0.2 tag up in the hopes that it resolves this. Here's hoping!

I'm closing this... feel free to comment if there is still anything going on with this, though.


update uswitch logo for new branding

Pre-submission checklist:
Uswitch recently had a brand refresh, this PR adds the new logo and updates the name to be capital U instead of S.
Please check each of these after submitting your pull request:

[N/A ] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[N/A ] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[N/A ] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~5 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Deploy preview for landscape ready!
Built with commit 932c02bfef3f7de3a5dd2c383b4cda8f6f204854
https://deploy-preview-1654--landscape.netlify.app

LGTM

Deploy preview for landscape ready!
Built with commit ae452fa07fd78daf3dbd8069e8eee6c0610ed6dd
https://deploy-preview-1654--landscape.netlify.app


give the gridsplitter a height so it is selectable

Maybe another one for the left/right split?

@Pilchie you mean add one? Isn't is only one GridSplitter in this view?

Yes, it might be nice to be able to adjust the width of the "Refinements" column too.
But I'll go ahead and merge this PR, since this is still goodness.


NIFI-7912 - Added a Denial of Service filter wrapper called NiFiDoSFi…

…lter to apply the DoS filter based on path.
NIFI-7912 - Working in cluster setup. Fixed tests and a log message.
NIFI-7912 - Changed log levels to debug.
NIFI-7912 - Added docs and default property to nifi.properties.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

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

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

I agree that the IP whitelisting is more representative of how the DoS should work rather than excluding the S2S paths. Testing this out it seems like the whitelist is only applied to the request rate tracking, as the timeout method onRequestTimeout() doesn't seem to call checkWhitelist(), confirmed by docs http://archive.eclipse.org/jetty/8.0.0.M1/apidocs/org/eclipse/jetty/servlets/DoSFilter.html

I agree that the IP whitelisting is more representative of how the DoS should work rather than excluding the S2S paths. Testing this out it seems like the whitelist is only applied to the request rate tracking, as the timeout method onRequestTimeout() doesn't seem to call checkWhitelist(), confirmed by docs http://archive.eclipse.org/jetty/8.0.0.M1/apidocs/org/eclipse/jetty/servlets/DoSFilter.html

That's a good point about DoSFilter.onRequestTimeout() still enforcing the maximum value as configured using the maxRequestMs.  With the addition of the new property nifi-web.request.timeout and one more property to exclude IP addresses or subnets from rate limiting, it seems like that should provide sufficient ability to configure the filter.

Thanks for making the documentation updates @thenatog!  With these changes, I am +1.  Do you have any additional feedback @turcsanyip?

@thenatog Thanks for the review changes!
@exceptionfactory I have no more comments, +1 from my side too.

@thenatog Thanks for the review changes!
@exceptionfactory I have no more comments, +1 from my side too.

Thanks for the confirmation @turcsanyip! Merging.


Unet with grayscale Image not working.

I am working on MRI dataset where the input and mask is a greyscale image. How to train the model for this particular case? and also if I don't want to use backbone how to do it.

I think you technically need a backbone, which acts as the encoder for the network. If you want to start from scratch, you could just load any backbone (like VGG16 by default), just not load the imagenet weights with it, and then set the entire model to trainable?

@JordanMakesMaps What if I don;t want to use encoder. I just want to use the unet model without using pretrained encoders. Just a simple unet without a backbone. Because here the unet is accepting channel 3 input image.

@ninjakx so if you don't want to use a pre-trained encoder, just don't load the imagenet weights. But by definition a Unet architecture consists of an encoder (which is one of the backbones) followed by a decoder which is a sort of mirror image of the encoder itself but in reverse doing upsampling operations instead of downsampling.
But if you're looking for some Unet architecture whose encoder is not a defined convolutional base (VGG, ResNet, DenseNet, EfficientNet), try checking out this repo, but the results are no where near as good as the ones from this repo.

@JordanMakesMaps you're very helpful as usual, thanks a lot for the answer!

@JordanMakesMaps I am currently working on the a dataset of grayscale images and i used no pre-trained model as a backbone when i am running my pipeline it executes without an error but the predicted mask images being saved are all black and don't show anything. I am very Confused about what should be my next step. Please help me out

Hi @ishreyaa07, walk me through how you're loading these images up as a dataset. Are they original 8-bit (0-255), are you stacking them so the dimensions are (w x h x 3)?
After you've trained the model and are making predictions, what's your process? How are you displaying the results and saving them. Are they actually all black (0's)? Please provide some code, otherwise there's not much I can help with.


Add GCCVER define to Toolchain.

Summary
We hope to find a common place to define GCCVER, so that it only needs to be specified once, which would undoubtedly be the most convenient. https://github.com/apache/nuttx/pull/14130#issuecomment-2408282192.  However, since GCCVER may be used in the Toolchain.defs of each architecture, we have to define GCCVER again.https://github.com/apache/nuttx/pull/14293#issuecomment-2415506922
Impact
Testing

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX requirements.
The provided information only includes a build error message and lacks essential details outlined in the NuttX PR requirements.
Here's what's missing:

Summary:  No information is provided about the purpose, functionality, or implementation of the change.
Impact: The impact on users, the build process, hardware, documentation, security, compatibility, and other considerations is entirely absent.
Testing:  While error logs are partially included, there's no context about the testing environment (host and target), the nature of the tests performed, or the expected behavior.

To meet the NuttX requirements, the PR needs to provide a comprehensive description of the change, its impact, and thorough testing evidence, following the template provided.

Please make some improvements for revert back commits and make each change more valuable, rather than revert,revert "revert",revert "revert "revert"" in daily work

please fixtheconflict, @cuiziwei1

@cuiziwei1 please fix the conflict.


Can you give access to S3 bucket to download v2.0.1.

I opened the link and then pressed the Linux link.
What I got I attached.

Thanks for pointing that out.  This issue is resolved now, but please let us know if you continue to see any issues!


[visionias.in] New site support

Checklist

[x] I'm reporting a new site support request
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that none of provided URLs violate any copyrights
[x] I've searched the bugtracker for similar site support requests including closed ones

Example URLs

Single video: http://visionias.in/student/videoplayer_v2/?id=4863202103131700

Description

WRITE DESCRIPTION HERE

pls help

The linked video needs an account. If someone decides to work on this, you'll have to provide suitable details. Or if you have any programming skills, you could study the developer instructions in the manual and try it yourself; help will be available.


add xHCI host dead troubleshooting

Hello, I want to contribute my solution about a problem trouble me a few months.
When STM32F freeze and not responding to Linux kernel, so kernel think it dead, reconnect USB won't make kernel re-check it.
I find the solution that we can use bind & unbind to make kernel re-check it.

This sounds more like a Linux kernel bug than something the user should have to deal with? Maybe file a bug report there? (Yes, I know that reporting bugs on the Linux kernel is an adventure. But the host controller really shouldn't "get stuck" here, I think, which is what it looks like is happening offhand.)

Well, I think I need time to check these,
but I feel it less seem a bug, it feel more like this is just how it currently work, which if not get device response just remove it and never check it.
Maybe other "full implement" device like mouse, will make some request when re-connect, so kernel mark it connected again.(just a guess, I just dive into hardware recently)
Should I close this merge, or just keep it here till I have time to check it?

Can leave it open for now. The messages look to me like the Linux host controller has gotten lost, but I could be wrong.


swift: Config for Swift Package build

Recently we have opened a new ThorVG for Swift repo: thorvg.swift.
Code will be migrated from a Swift fork thorvg-swift. You can see more details here at the GitHub issue on the repo.
In order to build the Swift Package, with the thorvg core as a submodule inside the thorvg.swift repo, the following changes need to take place for the upstream thorvg repo. These are what are currently allowing the thorvg-swift repo to build.
Note: I've marked this PR as draft because these changes are particular to the new thorvg.swift repo and are subject to change.
Config header file
When building the thorvg source using the meson build system, we spit out a config.h inside the output builddir/ directory. Many of the C++ source files refer to this at compile time.
Swift Package Manager doesn't follow the same paradigm, and requires all files to be present in the target directory at compile time. Thus, we need to generate a config.h file ahead of time so that SPM can see that header file and successfully build all of the C++ source files.
For time being, I've put this underneath the C API bindings folder, but am open to another destination for this file.
Symbolic link for inc folder
Swift Package Manager allows us to define a single path to the source code that we wish to build. We use the path parameter of this target function available to us inside the Package.swift manifest.
However, the umbrella file of the thorvg API (thorvg.h) is one step removed from the src directory. For more context, have a look at this diagram:
thorvg/
│
├── inc/
│ ├── meson.build
│ ├── thorvg.h <-- umbrella file
│
├── src/ <-- where the Swift Package path point to (everything we want to build)
│ └── ...

We need this umbrella file to be accessible by Swift Package Manager because many of the C++ files rely on that header file to build successfully. Currently, the meson build system takes care of this, but to get around this issue, we need to add a symbolic link inside the src/ directory pointing to the inc/ directory. After we do this, the package builds successfully.
I'm unsure how we get around this in a more elegant way without moving many of the files around, but this is the current solution that works.

@hermet @tinyjin I've now marked this PR as ready to review as @tinyjin and I have been collaborating on the Swift API as you can see here. And we're getting close to merging that PR! 🎉
For this PR, these are the minimal requirements to get the Swift Package building. As mentioned, where I've added the symbolic link and the config file may not be the best place to put them so would love your feedback as code owners of this repo 😄

@hermet thanks for the feedback ❤ That's a fair call. From memory, I wasn't able to perform a sort of "build step" from the SPM side, but let me take a look again. Because I agree, seems like something that should just happen at build time. Will report back soon. 👍

Good news - I've removed the symbolic link because we can point the Swift Package path to a layer higher to include the inc directory. I'll also push the changes to the thorvg.swift PR.
Last thing to figure out: the config.h file. Will report back and see if I can hack together a pre-build script or something.

An update: I've removed the config.h file and have created a pre-build script that consumers have to run in-order to copy the config file into the correct position to compile the Package. I will add more details in the PR here.

That means that this PR is now not making any changes on the thorvg repo and can thus be closed. 👍


tf_static not synchronized

Hi @TommyChangUMD do you expect /tf_static to be synchronized across the bridge?
Behavior that I'm seeing when using the parameter bridge is that the ros2 side sees all frames and in their proper transforms, whereas the ros1 side is missing many of the static frames altogether.
My parameter bridge yaml file (loaded on ros1 side) contains the following:
- topic: '/tf'
    type: 'tf2_msgs/msg/TFMessage'
- topic: '/tf_static'
  type: 'tf2_msgs/msg/TFMessage'
  queue_size: 1
  qos:
    history: 'keep_all'
    durability: 'transient_local'

My work around so far has been to do simply add static_transform_publishers and/or urdf links/transforms for the missing frames on the ros1 side.

Hi John,
Yes, I expect /tf_static to be synchronized across the bridge, although I have not tried it myself.
Let me try it and get back to you later.  In the meantime, it looks like you have a workaround that works reasonable well.

Hi John,
Yes, I expect /tf_static to be synchronized across the bridge, although I have not tried it myself.
Let me try it and get back to you later.  In the meantime, it looks like you have a workaround that works reasonable well.


Frontend/display service request image

Notes: If we don't want to use the store to stage an image, and instead want to upload a image every time a user takes a picture, then revert back to commit: 87fd9e3e039166fb5443d0fd85aacfaa94a8018d