Steps to reproduce the issue:
#!/usr/bin/env bash

#set -x

# Reinit the environnement
docker rm -f felix1 felix2 felix3
docker network rm application1
docker network rm monreseau

# Create a new network application
docker network create application1
docker network create monreseau

# Run a new container tomcat
docker run -d -P --name felix1 --net=application1 tomcat:8.0.32-jre8
# All is good. We can reach the exposed port 8080

# Run a second container and connect it to the wrong network
docker run -d -P --name felix2 tomcat:8.0.32-jre8
docker network connect application1 felix2
# No way to reach the exposed port :-(

# Run a third container and connect it to the good network
docker run -d -P --name felix3 tomcat:8.0.32-jre8
docker network connect monreseau felix3
# All is good. We can reach the exposed port 8080

# Display info
docker ps

Describe the results you received:
No way to reach the exposed port for felix2 without a docker network disconnect application1 felix2
The name application1 is not valid for creating a network.
It is strange because it is not a keyword for docker
Describe the results you expected:
I hope the have the same behaviour that with felix1 or felix3 : use the exposed port normally.
We can run a container with a not valid name for network as application1 without problem but we cannot connect the container to a such named network.
Additional information you deem important (e.g. issue happens only occasionally):
I think it is not the length of the keywork application1 but the term application.
Always reproduced. I will try to inspect the source code between libnetwork and docker engine.
Thanks a lot. Best regards,
Nicolas

@zepouet can you please try the RC image of the upcoming 1.11 release and confirm if you still see this issue ? https://github.com/docker/docker/releases/tag/v1.11.0-rc2 ?

@mavenugo Thanks but no I just try but always the problem.
docker info
root@sandbox:~# docker info
Containers: 3
 Running: 3
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.0-rc2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 30
 Dirperm1 Supported: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: host bridge null
Kernel Version: 3.13.0-77-generic
Operating System: Ubuntu 14.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.955 GiB
Name: sandbox
ID: KUMJ:7K6Z:MWRI:CAC7:L5ME:MXI6:3C66:H5U3:OTDA:W6S4:TGL5:WUUW
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/

docker version
root@sandbox:~# docker version
Client:
 Version:      1.11.0-rc2
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   388f544
 Built:        Fri Mar 25 19:53:02 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.0-rc2
 API version:  1.23
 Go version:   go1.5.3
 Git commit:   388f544
 Built:        Fri Mar 25 19:53:02 2016
 OS/Arch:      linux/amd64

@zepouet
I followed the reproduction steps you reported (thanks for that) using the latest docker image from master.
I no longer see the problem. Things seems to work as expected now.
$ docker ps
CONTAINER ID        IMAGE                COMMAND             CREATED             STATUS              PORTS                     NAMES
0279ecd06559        tomcat:8.0.32-jre8   "catalina.sh run"   3 minutes ago       Up 3 minutes        <IP_ADDRESS>:32771->8080/tcp   felix3
9aef263e80b1        tomcat:8.0.32-jre8   "catalina.sh run"   4 minutes ago       Up 4 minutes        <IP_ADDRESS>:32770->8080/tcp   felix2
befd28d1c256        tomcat:8.0.32-jre8   "catalina.sh run"   5 minutes ago       Up 5 minutes        <IP_ADDRESS>:32768->8080/tcp   felix1
$
$ docker port felix1
8080/tcp -> <IP_ADDRESS>:32768
$ docker port felix2
8080/tcp -> <IP_ADDRESS>:32770
$ docker port felix3
8080/tcp -> <IP_ADDRESS>:32771
$
$ docker network ls
NETWORK ID          NAME                DRIVER              SCOPE
c2e8929e7b87        application1        bridge              local
a306b727db25        bridge              bridge              local
a0dd2c482ce4        host                host                local
dc5823f8e9c9        monreseau           bridge              local
2de0510ceb5c        none                null                local
$ docker network inspect application1  --format='{{range .Containers}}{{.Name}}{{end}}'
felix2felix1
$ docker network inspect monreseau  --format='{{range .Containers}}{{.Name}}{{end}}'
felix3
$ curl localhost:32768 | grep Copyright
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11230    0 11230    0     0  1275k      0 --:--:-- --:--:-- --:--:-- 1370k

Copyright ©1999-2016 Apache Software Foundation.  All Rights Reserved

$
$ curl localhost:32770 | grep Copyright
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11230    0 11230    0     0   824k      0 --:--:-- --:--:-- --:--:--  843k

Copyright ©1999-2016 Apache Software Foundation.  All Rights Reserved

$
$ curl localhost:32771 | grep Copyright
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 11230    0 11230    0     0   839k      0 --:--:-- --:--:-- --:--:--  843k

Copyright ©1999-2016 Apache Software Foundation.  All Rights Reserved

$

Can you please take a look and confirm.
Thanks

ping @zepouet

closing because we didn't get a reply, but feel free to comment if this is still an issje

Hello
Sorry I will test and comme back in few days
Thanks
Le 29 oct. 2016 10:09, "Sebastiaan van Stijn"<EMAIL_ADDRESS>a
écrit :

closing because we didn't get a reply, but feel free to comment if this is
still an issje
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker/issues/21654#issuecomment-257078242,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOHZachEOU7rs6I4bwlB7bZJ8JJym0Pks5q4v9OgaJpZM4H7vgK
.


SOQL Issue with 'User'

When I typed the following line:
client.query('SELECT Id FROM User')
I get the following exception:
undefined method 'description' for #<User:0x007fff35b69fb8>
Is that intended or a bug?

False alarm.  I had a model that was named "user.rb" so it was conflicting with the generated User class by this gem.  I renamed my user model to something else and all's golden.

FYI, You can also set client.sobject_module to instruct the client to materialize classes in a module other than the global namespace.
cf. http://rubydoc.info/github/heroku/databasedotcom/master/Databasedotcom/Client#sobject_module-instance_method

That's awesome.  Thanks for sharing!


translatelocally: update, fix aarch64, add model pkgs

Description of changes
This updates translatelocally to the latest version,
fixing build for aarch64.
This also adds a package set of translation models to be used with the program.
This is tested in a simple test in passthru.tests.
See individual commits for more details.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2940


Fix external symbols related to keys ec, ecx, sm2, dh & dsa

Partial fix for #12964
This adds ossl_ names for the following symbols:
ec_*, ecx_*, ecdh_*, ecdsa_*, sm2_*
dsa_check_pairwise, dsa_check_params, dsa_check_priv_key, dsa_check_pub_key, dsa_check_pub_key_partial,
dsa_do_sign_int, dsa_ffc_params_fromdata,
dsa_generate_ffc_parameters, dsa_generate_public_key,
dsa_get0_params, dsa_key_fromdata, dsa_new_with_ctx, dsa_pkey_method, dsa_sign_int
dh_new_by_nid_ex, dh_new_ex, dh_generate_ffc_parameters, dh_generate_public_key,
dh_get_named_group_uid_from_size, dh_gen_type_id2name, dh_gen_type_name2id,
dh_cache_named_group, dh_get0_params, dh_get0_nid,
dh_params_fromdata, dh_key_fromdata, dh_params_todata, dh_key_todata,
dh_check_pub_key_partial, dh_check_priv_key, dh_check_pairwise,
dh_get_method, dh_buf2key, dh_key2buf, dh_KDF_X9_42_asn1,
dh_pkey_method, dhx_pkey_method

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

EC got a bit large due to the number of existing ec functions that were already in 1.1.1
It might be easier to review by commits

Had to rebase.. Changes are in the last 2 fixups to fix recently added internal symbols for ec and dh.

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Had to rebase due to pkey ctrl changes.. Last commit fixes the new files.

@paulidale can you reapprove please

Rebasing again - should not need reapproval.. I think I will just merge this soon as this is causing many rebases..

Go for it.

Thanks for reviewing. Merged to master.


Unable to compile native extensions in OS X "El Capitan"

Hi! I got the following output when I tried to gem install redcarpet -v '3.3.3' on my macbook running OS X 10.11.
/usr/local/opt/rbenv/versions/2.1.5/bin/ruby extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling autolink.c
compiling buffer.c
buffer.c:110:45: warning: passing 'const struct buf *' to parameter of type 'struct buf *' discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
        if (buf->size + 1 <= buf->asize || bufgrow(buf, buf->size + 1) == BUF_OK) {
                                                   ^~~
buffer.c:59:21: note: passing argument to parameter 'buf' here
bufgrow(struct buf *buf, size_t neosz)
                    ^
1 warning generated.
compiling houdini_href_e.c
compiling houdini_html_e.c
compiling html.c
compiling html_smartypants.c
compiling markdown.c
markdown.c:2838:43: warning: passing 'const uint8_t *' (aka 'const unsigned char *') to parameter of type 'uint8_t *' (aka 'unsigned char *') discards qualifiers [-Wincompatible-pointer-types-discards-qualifiers]
                if (codefences_enabled && (is_codefence(document + beg, doc_size - beg, NULL) != 0))
                                                        ^~~~~~~~~~~~~~
markdown.c:1391:23: note: passing argument to parameter 'data' here
is_codefence(uint8_t *data, size_t size, struct buf *syntax)
                      ^
1 warning generated.
compiling rc_markdown.c
compiling rc_render.c
compiling stack.c
linking shared-object redcarpet.bundle
ld: library not found for -lgmp
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [redcarpet.bundle] Error 1

make failed, exit code 2

In particular, the line ld: library not found for -lgmp seemed odd to me. I didn't think that GMP was a dependency, so I poked around in the ext/ directory and discovered that extconf added -lgmp to my cflags for some reason even though it's not mentioned in extconf.rb or anywhere.... Now that I've written this much, is this maybe an extconf bug? Not sure. I've already written this much already so....

try this https://github.com/Homebrew/homebrew/issues/20041#issuecomment-18395843
Try brew uninstall gmp; brew install gmp and/or brew unlink gmp; brew link gmp.

That worked. Thanks!

well, fine 👍🏻

27 окт. 2015 г., в 5:17, max thom stahl<EMAIL_ADDRESS>написал(а):
That worked. Thanks!
—
Reply to this email directly or view it on GitHub https://github.com/vmg/redcarpet/issues/523#issuecomment-151345090.

Hi!
Do you guys have this problem with installing 3.3.2 without gmp please ? This seems pretty strange that this problem is only spotted now!

I ran into this same issue using

OS X 10.11.1
Ruby 2.2.3p173 (installed via Rbenv)
gmp-6.0.0a (installed via Homebrew)

Reinstalling gmp did not help.

@robin850 I tried installing 3.3.2 as well and got the same error (if that was your question)

Just read https://github.com/Homebrew/homebrew/issues/13197 and reinstalled Ruby.
Worked for me.

Okay, I don't think this problem is related to Redcarpet ; this is certainly a larger problem with C extensions in general. I honestly don't know GMP at all but it is a required dependency for Ruby on my computer (running Arch Linux) so I think it's involved during the compilation process of native extensions.
Feel free to ask to reopen if I'm wrong, thanks for reporting everyone! :-)

Yeah I was suspicious about it actually because it's hard for me to believe that GMP is a dependency of Redcarpet. I'm not sure why you'd need arbitrary-precision math to parse markdown files. Was posting here thinking it might be something else. Thanks for responding so quickly!


define own custom command

Hello,
i work with docker under windows 10 and dockerdesktop.
I have a simple question.
Can i define my docker commands ?
Your sincerly
Stephan Krauß

yes, press c or menu x / Run predefined custom command.
Currently there is only login to container's shell but you can add any your command.
Open config by pressing o and then add to it's end:
customCommands:
  containers:
  - name: bash
    attach: true
    command: docker exec -it {{ .Container.ID }} /bin/sh
    serviceNames: []
  - name: Your new custom command
    attach: true
    command: docker top {{ .Container.ID }}
    serviceNames: []


If maps/xxx/layers contains tablename with quotes requests fail

While fixing issue #4001 I noticed that backend will return table names with format "user-name".table_name (with double quotes) if the username has a dash/minus. This is ok for SQL calls and the like, but the editor will inmediatelly perform calls to for example http://org.localhost.lan:3000/u/usera/api/v1_1/tables/%22user2%22.table_name, generating an error.
The editor is smart enough to recover and request again properly, but repeating requests and leaving the errors.
My guess is that editor should take into account this quotes and remove them only if going to do http requests (because every SQL operation must retain the quotes). If you think otherwise we can discuss how to fix this at the backend Layer Presenter class.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Re-run fastpath with historical data

Lowered estimate to 13: first chunk of work is to rerun the fastpath only over one year.

Reingestion for year 2019 is currently running. https://github.com/ooni/pipeline/pull/318 is related

I believe we have interrupted the re-ingestion, due to running out of disk space on the hkgmetadb.
Moving it back to in-progress column.

Blocked until both HKG and AMS get a disk space increase.

I added as blocker: https://github.com/ooni/backend/issues/423

Done as part of https://github.com/ooni/backend/issues/437


Clear DNS Cache

I regularly need to clear the DNS cache on the Mac by using terminal commands or a program like CleanMyMac. It would be great if this app had an option to do this within the Cleanup section along side the XCode Derived Data option.
These are the typical terminal commands that need to be run to perform this clearing:

For macOS High Sierra and later - sudo killall -HUP mDNSResponder
For macOS El Capitan - sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

@nomadjimbob Thank you for the suggestion. I think a shortcut action may meet your demand. You could share the shortcut to the shortcuts gallery in OnlySwitch. It's easier to publish, everyone can get this feature without a new release.
Learn about how to contribute shortcuts to the gallery:
https://github.com/jacklandrin/OnlySwitch/blob/main/ShortcutsGalleryContributing.md

If you couldn't contribute to it, I can share it from me.

I ended up setting it up by shortcut which works great. I'm happy to add it in through a PR.
Just noticed, 09cb781f40b2736ca8dc1ecd540ce95db39390ff moved the location of ShortcutsMarket.json to /OnlySwitch/Resource/ShortcutsMarket/ShortcutsMarket.json. The documentation you linked still has it listed at /OnlySwitch/ShortcutsMarket/ShortcutsMarket.json. If you can let me know which is correct and I can go from there.

/OnlySwitch/Resource/ShortcutsMarket/ShortcutsMarket.json is correct. You can fetch my newest code, then pull request.

I've merged your pr, but I find a bug of mine. I moved the location of ShortcutsMarket.json, but I didn't modify the URL of the request this JSON. I'll fix it in version 2.3.4.

2.3.4 is released.


Updated zoom slider style

Why do we need a new style here? Can you explain a little bit?

Why do we need a new style here? Can you explain a little bit?

The new style looks like the zoom slider from word, wordpad. It makes more sense and also looks aesthetically pleasing.

Ok, first, thanks for doing this and it looks not bad to me. There are two concerns I have:

I do not like adding more and more custom resources since it might be broken or look wrong on different versions of the OS. All existing custom resources I have added so far are all tint color related or similar reason. I did not actually change their look in anyway because I wanted to keep it the same as the system controls are look like. Everything we do differently will result or cause issues on newer version of the system.

If the control changes or have new features added in new Windows SDK, we have to update the resource as well. And that requires human resource and could be troublesome.

I would suggest let's keep using default control as much as possible and make it easier for us in terms of time and also overall consistency.

Ok, first, thanks for doing this and it looks not bad to me. There are two concerns I have:

I do not like adding more and more custom resources since it might be broken or look wrong on different versions of the OS. All existing custom resources I have added so far are all tint color related or similar reason. I did not actually change their look in anyway because I wanted to keep it the same as the system controls. Everything we do differently will result or cause issues on newer or older version of the system (Like the AppBar height issue we faced earlier).
If the control changes or have new features added in new Windows SDK, we have to update the resource as well. And that requires human resource and could be troublesome.

I would suggest let's keep using default control as much as possible and make it easier for us in terms of time and also overall consistency.

I have only removed the tint and modified the thumb design, this shouldn't cause any issue in older systems or in future.

Ok, first, thanks for doing this and it looks not bad to me. There are two concerns I have:

I do not like adding more and more custom resources since it might be broken or look wrong on different versions of the OS. All existing custom resources I have added so far are all tint color related or similar reason. I did not actually change their look in anyway because I wanted to keep it the same as the system controls. Everything we do differently will result or cause issues on newer or older version of the system (Like the AppBar height issue we faced earlier).
If the control changes or have new features added in new Windows SDK, we have to update the resource as well. And that requires human resource and could be troublesome.

I would suggest let's keep using default control as much as possible and make it easier for us in terms of time and also overall consistency.

I have only removed the tint and modified the thumb design, this shouldn't cause any issue in older systems or in future.

I am planning to use WinUI at certain point so I wan to keep resource changes as minimum as possible. We should use default design as much as possible for consistency as well unless it is not functional or needed by app logic/ux. Just my 2 cents here.

I am planning to use WinUI at certain point so I wan to keep resource changes as minimum as possible. We should use default design as much as possible for consistency as well unless it is not functional or needed by app logic/ux. Just my 2 cents here.

This should work with WinUI, here is a comparison of the changes:

Rest is up to you, if you don't think this isn't necessary for app ux then let's not do it. Otherwise you can keep this open until WinUI is implemented.

Let's wait for WinUI to become solid before merging. I don't see it drastically better than what we have right now.


Zone.js error: Zone already loaded.

Please provide us with the following information:

OS?

Windows 10.

Versions.

node 6.9.1.

Repro steps.
ng new test-universal --universal --link-cli
ng serve
The log given by the failure.
D:\Documents\GitHub\test-universal\node_modules\zone.js\dist\zone.js:25
throw new Error('Zone already loaded.');
^
Error: Zone already loaded.
at D:\Documents\GitHub\test-universal\node_modules\zone.js\dist\zone.js:25:15
at D:\Documents\GitHub\test-universal\node_modules\zone.js\dist\zone.js:638:3
at Zone.Zone.zoneSpec._properties (D:\Documents\GitHub\test-universal\node_modules\zone.js\dist\zone.js:9:68)
at Object. (D:\Documents\GitHub\test-universal\node_modules\zone.js\dist\zone.js:12:2)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.requ
The entire stack trace is masked by the other Webpack logs on Powershell.
Mention any other details that might be useful.

It looks like zone.js is loaded in angular2-universal-polyfills and the local polyfills.ts. I was able to avoid the issue by commenting the import './polyfills.ts'; line in server.ts.

@DavidRouyer I introduced it because of #1. I'll double check this with @gdi2290.
@gdi2290 I referenced the polyfills because of customization of polyfills. I think I should remove some of the imports in a --universal project. Or should I remove it completely in a --universal project?

ya just having angular2-universal-polyfills or ./polyfills works but not both


Additional VMware Tanzu Kubernetes  Grid Resources

Typo: Tanzzu
Lab link should go straight to the lab. You can use this https://labs.hol.vmware.com/HOL/catalogs/lab/10659

added the link


Enable Travic-CI and add a test

Adds tests for the password building based on the results from
a mocked out getch() method
Converts the getch() methods to function variables so they can
be mocked for testing

So if you want to include this you'd obviously have to enable travis for this repo; I don't see why you wouldn't want to have some sort of testing in place.  It makes it a lot easier to see intended behavior and can be expanded later to potentially mock out more of the os level features and test the error handling.

LGTM
Keep it coming! :)


Detect conflicting settings when using EnrichEF

Fixes https://github.com/dotnet/aspire/issues/2524
Microsoft Reviewers: Open in CodeFlow

Just for Npgsql for now to validate the fix. I think the way the execution strategy is checked is too brittle (passing a null! DbContext).
@AndriySvyryd @roji

/backport to release/8.0-preview5


Add Windows builds...

...and update to 3.2.0.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


fix/open_url: resolve missing features and other minor issue

Integrated missing features
Resolve cross platform open url issue
UI fixes

r? @krishnaIndia
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Remove dependency on six

https://github.com/Azure/azure-sdk-for-python/issues/26893.
Ref: https://github.com/Azure/azure-sdk-for-python/pull/25565

[ ] azure-ai-anomalydetector
[ ] azure-appconfiguration  - code gen
[ ] azure-security-attestation
[ ] azure-ai-language-questionanswering
[ ] azure-communication
[ ] azure-containerregistry - test only?
[x] azure-cosmos
[ ] azure-eventgrid
[x] azure-eventhub
[ ] azure-ai-ml
[ ] azure-monitor
[ ] azure-search-documents
[ ] azure-storage
[ ] azure-data-tables
[ ] azure-ai-translation-document
[ ] azure-media-videoanalyzer-edge

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.56599855,Azure.Identity:0.18130244,Service Bus:0.10542601'

#30613

Are there any updates on the progress here? Can the community help in any way?


Numeric graph signal operations

Currently, there needs to be clear distinction between graph signal objects and extraction of their .np fields.
Reframe code so that, when signal operations are employed, their respective .np fields are used in their place.
This can help write comphrehensible high-level code.

Feature added.


Automatically deploy to gh-pages

Hi,
This PR automatically builds and deploys to gh-pages branch (if on master), and also makes it easier to build the page locally for others. In the current state, it will overwrite the gh-pages branch with a single root commit each time, but this can also be changed to keep the history if you prefer. (The history of current gh-pages is kept either way, because it is merged into master).
This also contains the changes from the other two PRs. Originally, I wanted to wait until these PRs are merged and then post this one as a follow-up but I simply open it now before I forget.
Edit: Oh, I forgot, it also contains one commit to add syntax for language intersection (which isn't really a regex). If you would like to merge only part of this, let me know and I can remove the corresponding commits.

The auto-deploy part of this is good, but I definitely don't want to include the additional syntax, and I don't think it's worth converting to es modules (which is a breaking change). If you pare this down to just the auto-deploy part I'd happily merge it.

The auto-deploy part of this is good, but I definitely don't want to include the additional syntax, and I don't think it's worth converting to es modules (which is a breaking change). If you pare this down to just the auto-deploy part I'd happily merge it.

Sure, I can understand. I've removed the two commits and force pushed it without this. I recommend to merge with a merge commit (no squashing) if you want to keep the history of gh-pages branch.

Changed it according to your request.

Thanks! I'm not worried about preserving history from the gh-pages branch, given what's there, so just gonna squash.


Support for .NET Standard 2.0 and 2.1

Main focus of this PR is to introduce .NET Standard support as a preview feature and make absolutely sure the .NET 6 & 8 support is not affected at all.
We take advantage of 2.1 APIs and we can create follow up PRs to improve .NET Standard performance for both 2.0 and 2.1.
InboxSub WeakRef changes for 2.0
There are minor changes for 2.1 but 2.0 seems to lack quite a few APIs so changes in this class might require a little more scrutiny.
TLS Support
Most of the APIs doesn't seem to be available in netstandard hence TLS support will be limited in targets using netstandard. However the important thing is to make sure net8.0 isn't affected at all.
Tests
There are no changes to the existing tests to make sure no regressions happen. Only couple of tests are deleted related to now unused classes in the library.
The new 'Platform' test targets .NET Framework 4.8.1 and uses netstandard2.0 version of the library. These tests broadly covers all the libraries demonstrating that netstandard target works as expected at least for the basic functionality.
Idea is eventually merge all the tests and run them for all the targets for best platform coverage.
  So we don't have to put it all over the place?
#if NETSTANDARD2_0 || NETSTANDARD2_1
global using NATS.Client.Core.Internal.NetStandardExtensions;
#endif


Handle no/partial landcover coverage due to low/high latitudes

This PR adds support to no/partial landcover coverage due to low/high latitudes. If these cases are detected, instead of raising an error, the execution will go on. This PR also adds three metadata fields to indicate the coverage of the ancillary inputs: DEM_COVERAGE, LANDCOVER_COVERAGE, and WORLDCOVER_COVERAGE.

Thank you, @nemo794 !


added encryption and metadata to artifact upload

Issue #, if available:
Description of changes:
This enhancement will allow users to choose an encryption type while uploading the GDK artifact(s) to s3 or if chosen the  code will lookup the default bucket encryption type and use that.  This enhancement also will allow users to add metadata to the artifact(s) that are being uploaded.
Supported Encryption Values:
alias : Which would use a kms key alias for encrypting the gdk artifact
example
"publish": {
    "bucket": "this-is-a-test",
    "region": "us-east-1",
    "encrypt": {
        "server_side_encryption": "aws:kms",
        "kms_key_id": "alias/gdk-test"
    }
}

kms key arn : This option would use a kms key arn for encrypting the gdk artifact
example :
"publish": {
    "bucket": "this-is-a-test",
    "region": "us-east-1",
    "encrypt": {
        "server_side_encryption": "aws:kms",
        "kms_key_id": "arn:aws:kms:us-east-1:###########:key/aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
    }
}

kms key id : This option would use a kms key id for encrypting the gdk artifact
example :
"publish": {
    "bucket": "this-is-a-test",
    "region": "us-east-1",
    "encrypt": {
        "server_side_encryption": "aws:kms",
        "kms_key_id": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee"
    }
}

MetaData usage:
Example :
"publish": {
    "bucket": "this-is-a-test",
    "region": "us-east-1",
    "metadata": {
        "key1": "value1",
        "key2": "value2",
        "key3": "value3"
    }
}

Why is this change necessary:
A number of company's require a bucket policy to which will deny unencrypted object uploads. The metadata enhancement will make it easier deployment solutions like the Connected Device Framework (CDF) to deploy a GreenGrass component to a device.
How was this change tested:
User tested.  I setup a number of scenarios by creating a gdk-config.json file per test.  I also needed to setup S3 bucket default encryption a few different ways for my tests.
Any additional information or context required to review the change:
Checklist:

[ ] Updated the README if applicable
[ ] Updated or added new unit tests
[ ] Updated or added new integration tests
[ ] Updated or added new end-to-end tests
[ ] If your code makes a remote network call, it was tested with a proxy
[x] You confirm that the change is backwards compatible

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for your contribution.
PR looks good to me. But to proceed further, you need to make the following changes along with addressing the comments.

Update the commit messages to match the conventional commits format for the GitHub workflow checks to pass. You can also refer to the previous commits of this repository.

Add relevant unit tests and integration tests to maintain the code coverage of the repository so the codecov can pass.

Once you're done with 1 and 2, one of the Greengrass engineers will add UATs (mainly test data) for the same.

Let us know if you need more information.

Just following up on this to make sure no updates are needed on my side.

ExtraArgs parameter in s3 client upload_file operation takes a JSON object as the input. So, instead of adding individual keys from this ALLOWED_UPLOAD_ARGS list to the gdk-config.json file, the idea is to add a new key called s3_upload_file_args under publish in gdk config file that takes ExtraArgs JSON object directly as ExtraArgs is already validated by s3 client upload_file operation.
The following is the output of gdk component publish command when used with invalid s3_upload_file_args as follows in the gdk-config.json
      "publish": {
        "bucket": "<BUCKET_NAME>",
        "region": "<AWS_REGION>",
        "s3_upload_file_args": {
          "Meta": {
            "Key": "Value"
          }
        }
      }

=============================== ERROR ===============================
Could not publish the component due to the following error.
Failed to publish new version of component with the given configuration.
Error while uploading the artifacts to s3 during publish.
Invalid extra_args key 'Meta', must be one of: ACL, CacheControl, ChecksumAlgorithm, ContentDisposition, ContentEncoding, ContentLanguage, ContentType, ExpectedBucketOwner, Expires, GrantFullControl, GrantRead, GrantReadACP, GrantWriteACP, Metadata, ObjectLockLegalHoldStatus, ObjectLockMode, ObjectLockRetainUntilDate, RequestPayer, ServerSideEncryption, StorageClass, SSECustomerAlgorithm, SSECustomerKey, SSECustomerKeyMD5, SSEKMSKeyId, SSEKMSEncryptionContext, Tagging, WebsiteRedirectLocation


chore: add rust ffi integration tests to CI

As we write Rust code called by Go via FFI we should run integration tests against it. Once we delete the Go code we can delete the go_integration job in favor of the Rust FFI one
Test plan: Make sure that integration tests run on CI

Does this need to be its own job or can we just make the regular integration-tests do this?

It can be, that just means the integration test job will be longer running since we'll be rebuilding turbo serially. The Rust cache should stay around and save us some time, but I'll verify.

Any way we can move this a shared action and make the only diff here the env var setting to prevent drift?


Support for aggregation pipelines in updates

Hi there,
It seems that aggregation pipeline as argument to an update operation is not implemented yet in mongomock. That feature was introduced in version 4.2 of MongoDB.
Best regards,
Gustavo Sousa

FYI, I have started a patch for this... A PR should be coming soon...

Any updates on this? Would love to have this supported


Overwrites existing layers attached to function

This package appears to remove existing layers that have been attached to the functions you enable the insights for
We are using the serverless-python-requirements and attaching these requirements using another layer. We also have a custom layer that we add to our functions.
When we add this package, the cluoudformation json that results has overridden the layers for the function and only contains the LambdaInsightsExtension layer

On further investigation I can see what the problem is.
The function addLambdaInsightsToFunctions appends the insights layer to the function layers if it contains any. However, it ignores any layers defined at the service level.
The serverless-python-requirements package also doesn't seem to play nicely either so I will still have to do a workaround for this to work in our setup.

Closing this as it is a duplicate of this issue


Is it possible to reduce file size

Hey,
me again, when building the app with the library included the download size (size of the packed apk) and the usage on device increase dramatically:

Since we have to deal with small devices (from a memory perspective) every megabyte counts. Is there a way to reduce the usage of the native libraries?
I am not in to native libraries yet but may we could have a "common" library instead of increasing the size by 4 when including the native libs for every system architecture.
If i can support in any way just let me know!
Best regards
Martin

I just found an interesting blog post about that topic you might find interesting:
https://realm.io/news/reducing-apk-size-native-libraries/
We will tinker around with different apk files per architecture (also linked in the original article):
https://developer.android.com/studio/build/configure-apk-splits.html
I will keep you up to date about the progress on this our side!

Yeah, I referenced that article in AndroidJSCore.
There is not much I can do with libnode.so.  It is what it is.  I stripped everything out of it that had any bulk (especially ICU which is a pig).  However, I have to say that I am surprised that libliquidcore.so is the same size.  It should be nowhere near that big.  I may have unintentionally left all the symbols in it.  I'll take a look at it.  That should reduce the size dramatically.
As you rightly note, if you are really concerned about APK size, you will need to do an APK split.  I had considered publishing separate libraries for each arch, plus one big one multi-arch one for those who aren't concerned about size, but I never really got around to it.

No Worry the size of ibliquidcore.so is only the smallest one here (1.2 MB compared to lobnode.so 17.7 mb).
We are currently using libliquidcore via gradle.
To split the apk's i will have to include the library as described in
"Building the LiquidCore Android library"?

Maybe.  I haven't actually tried it.  It may be possible to do the APK split from the app itself.  Android Studio may be smart enough to ignore anything not related to the ABI.

Ok we will check it out and keep you up to date! thank you!

Just came across this when working with React Native: https://developer.android.com/studio/build/configure-apk-splits.html
This is a step-by-step how-to from Google.

Update on this:  Version 0.3.0 reduces the size of the library by half by removing explicit support for 64-bit architectures (they can use the 32-bit versions without issue), and stripping out the debugging symbols.  So the current aar is ~15MB.  My goal is to get it under 10MB.  I think there several other opportunities for reduction.

I was able to squeeze out another ~1.5MB by re-using the built-in Android SQLite implementation, rather than compiling sqlite3.c into the project.  The footprint (not rolled into a release yet) is now at 13.3MB.  Running out of opportunities for reduction, though.


Deprecate jumpahead in get_random_state

The jumpahead argument in pisa.utils.random_numbers.get_random_state does not result in independent sequences of output numbers if the random state is used to generate random numbers. It doesn't even reliably move the sequence of output numbers ahead by the given number, because calling rand does not mean that the internal Mersenne twister is really moved by one step (and really, we don't have access to numpy internals and shouldn't make such assumptions anyway).
A function that minimally implements the behavior of the PISA method is:
def get_poisson_sequence(size, seed=0, jumpahead=0):
    rs = np.random.RandomState(seed=seed)
    rs.rand(jumpahead)

    return rs.poisson(size=size)

With the right settings for jumpahead, we can repeat sequences exactly after a few initially different numbers:
get_poisson_sequence(15, seed=0, jumpahead=1)
>>> array([2, 1, 3, 2, 1, 0, 0, 5, 1, 1, 2, 0, 1, 1, 2])

get_poisson_sequence(15, seed=0, jumpahead=3)
>>> array([1, 1, 2, 2, 1, 0, 0, 5, 1, 1, 2, 0, 1, 1, 2])

We should deprecate jumpahead, as people can be mislead and use it to generate trials that they think are independent. My suggestion is to raise an Exception (no one cares about warnings) with instructions about how to fix the problem (by using a different seed instead of jumpahead).

good catch! Let's do what you suggest and raise an exception if anyone uses this feature and disable it

This hasn't been implemented, right?

Yeah this can trip people up when they make pseudo-data trials and they wonder why their trials don't look so independent. If this is still a thing then yes it should definitely get fixed! 😅

Interestingly, the OG version of the unit test, using jumpahead worked :thinking:

It doesn't always fail to produce independent series. That's the terrible thing about it. :D


[Release-1.0] Setup Authentication With Apple

We currently have Spotify authentication setup and now need Apple. This is required by Apple currently.
We also would like to user Apple Music for creating playlists and things of that nature. The current issue with this is there is no "straight forward" way to do this in React Native. We will need to implement some NativeModules to get this thing work. Currently this task should include:

[x] Authenticate with Apple using Firebase
[x] Create social platform for user in Firebase
[x] Create user with Apple creds in Firebase

What We Did Today

Setup dev environment for both Android and iOS

What We Will Do Next Time

[ ] Enable Apple Sign In Button
[ ] Create Social Platform on AppleAuth

What We Did Today

Setup client to call custom firebase for apple music auth
Setup Golang template to render html page in browser

What We Will Do Tomorrow

[ ] Continue creating HTML page for authing Apple Music User
[ ] Get proper token back and create social platform and Firebase user

What We Did Today

Continued working on the template in Golang
Found our new flow of how we are going to handle the Apple Auth (see above)
Realized we will need to make the "choose username" UI

What We Will Do Tomorrow

[ ] Setup Getting Apple Developer Token
[ ] Calling Authorize Service For Apple Music
[ ] Deep linking back into Grüvee with the access token

What We Did Today

Continued on the track for obtaining a Developer Token. Realized we actually need to create our own JWT
Pulled in a library to create a JWT in Golang
Halfway through the implementation of this

What We Will Do Next Time

[ ] Finish creating JWT to call Apple Music API
[ ] Calling Authorize Service For Apple Music
[ ]  Deep linking back into Grüvee with the access token

What We Did Today

Continued with JWT stuff. WOW so much learnings here haha
Got the JWT created (almost) ran into signing issue

What We Will Do Next Time

[ ] Convert PrivateKey into proper format
[ ] Send key over to Golang Template
[ ] AUTH WITH APPLE USER

What We Did Today

Converted PrivateKey from file to proper format
Sent JWT data over to template
Also added the ability read JWT token from DB

What We Will Do Next Time

[ ] Fix broken JWT
[ ] Setup refresh for JWT
[ ] Create social platform with Apple Auth Token

What We Did Today

Got the deep link stuff working for AppleAuth. This gets the Apple Music MusicUserToken and passes it back to our clients

What We Will Do Next Time

[ ] Finish setting up the SocialPlatform for Apple Auth
[ ] Setup refresh for our JWT
[ ] Create Firebase user for our new Apple Music user

NOTE:
Need to add an expiration time on the Apple Music User Token

What We Did Today

Designed a new layout for how we want to create our social Platform, firebase user, and JWT for Apple Dev Token
Implemented, but not tested, the token generation

What We Will Do Next Time

[ ] Finish setting up the SocialPlatform for Apple Auth
[ ]  Setup refresh for our JWT
[ ] Create Firebase user for our new Apple Music user

New design for Apple Auth Flow

What We Did Today

Designed new flow for Apple Sign / Apple Music Auth (See above ^)
Implemented the Apple Sign in portion
Started to move onto Choose username component

What We Will Do Next Time

[ ] Create "ChooseUsername" component
[ ] Add this to the navigation flow for both Spotify and Apple Music

At the beginning of trying to setup our new views, the react-native-navigation library was giving us pains again.... It's time to switch to React-Navigation. I think this needs to happen now as the app is still relatively small. Going to do that now before continuing on here.

HERE IS THE NEW FLOW:

Sign in with Apple ID (Standard, built in flow here)
Move onto changing username
Once person creates a playlist, prompt messaging saying that Grüvee can create playlists on your behalf! Would you like this?
If yes, go through Apple Music sign in else, do nothing!

What We Did Today

We worked on adding logic for Create Username view
Setup Firebase query to check for usernames
Currently running into some debounce weirdness

What We Will Do Next Time

[ ] Finish up create username view
[ ] Set it up to work with Spotify auth as well
[ ] Actually create Apple User

What We Did Today

Continued working on the create username view
Setup the proper logic for button state and showing/hiding availability message
Realized we need to add a DisplayName field to user doc to properly search for username

What We Will Do Next Time

[ ] Update DB and services to utilize new DisplayName Field
[ ] Lowercase username field
[ ] Add button logic for Apple Auth sign in

What We Did Today

Update DB and services to utilize new DisplayName Field
Lowercase username field
Add button logic for Apple Auth sign in
Ran into some Firestore Rules issues for Apple Sign in

What We Will Do Next Time

[ ] Fix Firestore rules for Apple Auth
[ ] Verify Apple User login/logout works
[ ] Setup Apple Music Sign in flow

What We Did Today

So we ran into a pretty annoying issue with authentication and apple provider today. It looks like it may require us to setup a new db/auth flow for the app. In another comment I am going to post my findings.

What We Will Do Next Time

[ ] Setup new auth flow kappa.

The Issue
When authenticating with a service provider associated with Firebase, a UID is created for us automatically and we can’t change it. That leaves us with issues in our Firebase Rules to go ahead and access certain documents. Since the custom authenticated users have the proper ID’s.
Potential Solution
Create a new collection that maps firebase auth users to their documents. IE:
Firebase User UID: 1234567 —> Firebase User Doc {id: apple:999999}
That would mean all our Firebase rules will probably have to change and the way we fetch documents will probably also have to change.

What We Did Today

Today we literally worked on button styling for Apple Auth and Spotify
It looks SICK and seems to be good to go on both iOS and Android

What We Will Do Next Time

[ ] Finish up Apple Music flow for getting Apple Music API Token
[ ] Probably need to get a head start on Firebase rules. BIG YIKES.

Apple Music Prompt Flows:

When creating playlist, prompt user to auth with Apple Music

Send to Golang rendered view
Auth
Create playlist on users behalf

After authing with Apple Music we will need some flag to not prompt the auth again

If creating new playlist, we should check this flag
If flag is true (saying we have already tried to get user to auth) then don't show prompt and go through proper creation
Else show prompt and go through auth if accepted

What We Did Today

Starting setting up Apple Music Auth
Creating new stack view so we can navigate to Golang Function for Apple Music Auth

What We Will Do Next Time

[ ] Add proper .p8 file back to Golang project
[ ] Get Apple Music Token and store in DB
[ ] CREATE PLAYLIST IN APPLE MUSIC

What We Did Today

Fixed up the the Golang Template for our Apple Music Auth (FIRST TRY)
Cleaned up a lot of the flow for Apple Music Auth in general and it's looking CLEAN
Started working on adding Apple Music Playlist creation in Golang function

What We Will Do Next Time

[ ] Finish up Golang work for setting up Apple Music API call to create playlist
[ ] We need to look at the bugs list in our Bear Notes

What We Did Today

We now have Grüvee creating a playlist on an Apple Music account via API (SICK)
Fixed some issues with our flow on calling creating a social playlist
Pretty much cleaned up Golang function for creating playlist

What We Will Do Next Time

[ ] Finish up logic for creating a playlist after Apple Music Auth
[ ] We need to look at the bugs list in our Bear Notes

What We Did Today

Finished up the logic for all the scenarios of adding a playlist after Apple Music auth
This included updating redux actions and saving playlist name in asyncsStorage

What We Will Do Next Time

[ ] Fix all the bugs logged in our Bear notes
[ ] Plan what next steps we need to take for collaboration between Apple Music user and Spotify

What We Did Today

Knocked out 6 bugs that popped during Apple Auth
Things are looking SWEET.

What We Will Do Next Time

[ ] We still have two bugs to handle. Let's finish up
[ ] One of the bugs includes deploying stuff to Firebase. Need to figure out a way to grab versions from a different branch
[ ] Planning for next feature before beta launch!

What We Did Today

Started fixing issue with our AppleAuth user being null
Found another bug with Android Deeplinking and sign in
Looked at the broken song links and no issues so far

What We Will Do Next Time

[ ] Finish up the Spotify Deeplink bug
[ ] Figure out AlgoliaSearch local setup for Firebase Functions
[ ] Firebase rules
[ ] Plan next feature to build!

What We Did Today

Fixed Spotify Deeplink Bug (YAY)
Spent a lot of time trying to get AlgoliaSearch to run locally. Decided to just not worry about it
Setup PR for ServerSide functions

What We Will Do Tomorrow

[ ] Finish up PR for Firebase functions
[ ] Deploy Firebase functions
[ ] Do a sanity check of functions
[ ] Setup Firebase Rules

So some notes:

In CreateAppleDevToken function, we need to store our .p8 file in a storage bucket.
In our Firebase function we will need to grab these file from our bucket to mint our token
Security rule behind this is we should probably just be admin

What We Did Today

Finalized Firebase Storage for .p8 file
Deployed new function with with changes
Tested out Apple Auth Flow and realized we are now missing AuthTemplate file which may require us to updated this in Storage as well. RIP.

What We Will Do Next Time

[ ] Figure out AuthTemplate file issue
[ ] Deploy changes
[ ] Firebase rules maybe?

What We Did Today

Today we spent the entire stream trying to test our production app
We had no luck as there seems to be some weird issues with pointing to production from our dev device

What We Will To Next Time

[ ] Firebase Rules
[ ] TEST AND MOVE ON

All the issues we were having last week with accessing the new functions in prod is like 75% fixed now. I had to move two functions from the client to Firebase Functions as there was no authentication at the point of calling these queries so gotta do em in the cloud! Just have to deal with a few more firebase rules (all the actions for playlists and such).
Then we will need to deploy two more functions to the cloud, update the firebase rules and then we can move on hahaha

What We Did Today

Deployed new Firebase functions
Tested prod and things are working great!
Continued on with Firebase Rules (Getting close)

What We Will Do Next Time

[ ] Finalize Firebase Rules
[ ] Do a full test pass on prod app version
[ ] Move onto next feature!

What We Did Today

Worked through some Firebase Rules stuffz
Still have a bit of logic to figure out here... We started writing a new trigger function that would allow us to link the FB provider logins with user documents, but realized we don't have the request.auth.id to link in the new collection

What We Will Do Next Time

[ ] Look into this new trigger function and see if we can do it through a regular http-request function
[ ] Get these dumb firebase rules done with
[ ] Move onto next feature

What We Did Today

We re-wrote the trigger function to be just a regular http-request function that is called from the client
Updated the client to call this when signing in as an Apple user for the first time
Updated all Firebase Rules (THEY ARE ALL WORKING. POGGERS.)
Started looking at a potential bug with Apple Music Token Refresh

What We Will Do Next Time

[ ] We need to deploy new Firebase function
[ ] Do full test suite in Prod with Apple Sign in
[ ] Move onto next feature!

We are finally done.... WOW.


Better file renaming experience

aside from #254 which adds support for renaming files on usage side, there are other options to improve file renaming experience.

vscode/lsp supports a notification on file renaming. (client sends a file-renamed event to server) we can ask user to rename the module usages or rename usages directly.

add a command (like the one we have for creating interface) to rename a module.

@amiralies do you think the current excellent functionality for renaming is lacking?
Even if one were to add a specific commend to rename a module, user would need to first imagine that such a command exists, and then discover it. Not sure about the overall value.

Yeah i'm not sure about that too.
but currently there's no way to rename a module semantically from the module (file) itself.
The notification way may be more useful.
Scenario:

User renames the file
a popup asks the user if he wants to rename references to that file

but i'm not sure if it's possible to implement since the compiler tries to compile renamed module immediatly.


Sample code to initialize the scanner with this library

Hi there! Do you have an example of how to initialize the scanner before using the callback examples in the readme documentation? I see references to "NOTE: You must register a callback to initialize the hardware." but no example for that.
Thanks!

The example in the readme should be all you need.  Let me know if you've seen those and still aren't sure what to do.

Hi Blake,
Thanks for your prompt reply! The part I’m confused on is this example:
document.addEventListener("deviceready", function(){
...
captuvo.registerScannerCallback(function(barcode){
       console.log("Barcode scanned: " + barcode);

       //TODO: handle barcode/label type
   });
   //This function will send the first readable track
   captuvo.registerMagstripeCallback(function(track){
        //track 1 uses carets as dividers (NOTE: won't work if track 2 is read)
        if (track.indexOf("%B") == 0) {
          track = track.split('^');

          var cc = {
             number : track[0].substr(2), //strip leading %B
             name : track[1].trim(),
             expr : '20' + track[2].substr(0,2) + '-' + track[2].substr(2,2)
          };
        } else {
          //handle track 2
        }

   });

Where does the device itself - captuvo - get defined/initialized? I’m curious where that part of the code is.
Rob Brennan |<EMAIL_ADDRESS>Phone<PHONE_NUMBER>
Skype The.Rob.Brennan
Web         http://www.therobbrennan.com

On Jan 26, 2015, at 7:34 PM, Blake Byrnes<EMAIL_ADDRESS>wrote:
The example in the readme should be all you need. Let me know if you've seen those and still aren't sure what to do.
—
Reply to this email directly or view it on GitHub https://github.com/BlueFletch/cordova-plugin-honeywell-captuvo/issues/1#issuecomment-71584633.

Hi Rob,
When you call captivo.registerScannerCallback, it will activate the hardware under the covers. You should not need to do anything else. Hope that answers your question!
Blake
Sent from my iPhone

On Jan 26, 2015, at 8:36 PTheRobBrennan<EMAIL_ADDRESS>wrote:
Hi Blake,
Thanks for your prompt reply! The part I’m confused on is this example:
document.addEventListener("deviceready", function(){
...
captuvo.registerScannerCallback(function(barcode){
console.log("Barcode scanned: " + barcode);
//TODO: handle barcode/label type
});
//This function will send the first readable track
captuvo.registerMagstripeCallback(function(track){
//track 1 uses carets as dividers (NOTE: won't work if track 2 is read)
if (track.indexOf("%B") == 0) {
track = track.split('^');
var cc = {
number : track[0].substr(2), //strip leading %B
name : track[1].trim(),
expr : '20' + track[2].substr(0,2) + '-' + track[2].substr(2,2)
};
} else {
//handle track 2
}
});
Where does the device itself - captuvo - get defined/initialized? I’m curious where that part of the code is.
Rob Brennan |<EMAIL_ADDRESS>Phone<PHONE_NUMBER>
Skype The.Rob.Brennan
Web http://www.therobbrennan.com

On Jan 26, 2015, at 7:34 PM, Blake Byrnes<EMAIL_ADDRESS>wrote:
The example in the readme should be all you need. Let me know if you've seen those and still aren't sure what to do.
—
Reply to this email directly or view it on GitHub https://github.com/BlueFletch/cordova-plugin-honeywell-captuvo/issues/1#issuecomment-71584633.

—
Reply to this email directly or view it on GitHub.

Oh yeah. For some reason I was thinking that there was an initialization phase that had to occur.
One final question (I promise) - were you able to get the callback to fire more than once? In a very simple app, I was able to get the callback to fire once, but it failed to run on subsequent scans of the same barcode. Any idea what I might be missing perhaps?
I really do appreciate your time on this. I love the plug-in; just want to make sure I'm using it correctly =)
document.addEventListener("deviceready", init, false);
var resultDiv;
function init() {
resultDiv = document.querySelector("#results");
// Honeywell SL42 scanner
captuvo.registerScannerCallback(function(barcode){
    //console.log("Barcode scanned: " + barcode);
    resultDiv.innerHTML = "Barcode scanned: " + barcode;
    //TODO: handle barcode/label type
});

}

Solved! Figured it was best to just create a function and have it re-register for the callback:

document.addEventListener("deviceready", init, false);
var resultDiv;
var counter = 0;

function init() {
    resultDiv = document.querySelector("#results");
    prepareScannerToReceiveBarcodeData();
}

// Honeywell SL42
function prepareScannerToReceiveBarcodeData(){
	captuvo.registerScannerCallback(function(barcode){
        resultDiv.innerHTML = "Barcode scanned [" + counter + "]: " + barcode;
        counter++;    // ...just to prove that we're successfully calling back our function multiple times

        // TODO: handle barcode/label type
        /* Super secret processing */

        // Add the callback handler again
        prepareScannerToReceiveBarcodeData();
    });
}


Update ext/waktu solat

Fix some issue and logic on menubar
Monotone icon in menubar

Hi 👋
Wouldn't it be better to always show the icon instead of only when there is not recent prayers?

Hi 👋,
I've make changes to address that, but is it ok that checking based on user preference that one still remain? mean if icon enabled in preference we always display the icon otherwise we just display text based notification on event similar to Calendar extension 👉👈.

That should be fine 🙂

Is this ready for review then?


Add method calls for HazeList in main, necessary helper methods.

Add method calls for HazeList in main, necessary helper methods and tests for them in main and HazeList.
Main tests are also slightly modified to make them work with the new functionality.

Obvjously the the small modifications on mainTest broke something. Im going to leave this open for now and hopefully someone else can help to figure out why that is.
Program seemed to be working fine when I ran it so I don't think its anything in the HazeList or in the CommandSwitch.


Can not build app

Describe the bug
Build app by command  yarn tauri build or by  yarn tauri build --debug, get error says file .cargo-lock is locked by another process. However I don't find any process is accessing to that file.
yarn tauri dev works well. The built debug .exe file works as well.
To Reproduce
Steps to reproduce the behavior:

Generate new tauri project following official instruction.
Build app by   yarn tauri build or by  yarn tauri build --debug
See error as following

PS F:\forrrest-digital-garden-tiddlywiki> tauri build --verbose
[tauri]: running build
 app:spawn Running "cargo tauri-bundler --features embedded-server --release --verbose" +0ms

   Compiling tauri v0.11.1
   Compiling tiddlywiki-desktop-rs v0.1.0 (F:\forrrest-digital-garden-tiddlywiki\src-tauri)
error: couldn't read F:/forrrest-digital-garden-tiddlywiki/src-tauri/target/release/.cargo-lock: The process cannot access the file because another process has locked a portion of the file. (os error 33)
     --> F:\forrrest-digital-garden-tiddlywiki\src-tauri\target\release\build\tauri-5327b7eb78ed3479\out/data.rs:15185:128
      |
15185 | ...::Compression::None, include_bytes!("F:/forrrest-digital-garden-tiddlywiki/src-tauri/target/release/.cargo-lock") as &'static [u8])),
      |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      |
      = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

error: could not compile `tauri`

To learn more, run the command again with --verbose.
error: `Result of `cargo build` operation was unsuccessful: exit code: 101`

 app:spawn Command "cargo" failed with exit code: 1 +0ms

 app:tauri (runner) ⚠  [FAIL] Cargo CLI has failed +0ms

 app:tauri Shutting down tauri process... +1ms

Expected behavior
Build success.
Platform and Versions (please complete the following information):
Operating System - Windows_NT(10.0.19042) - win32/x64
Microsoft Edge - 44.19041.423.0_neutral__8wekyb3d8bbwe
Node.js environment
Node.js - 15.14.0 ( Get the same error on 14.16.1)
tauri.js - 0.14.1
Rust environment
rustc - 1.51.0
cargo - 1.51.0
tauri-bundler - 0.9.4
Global packages
NPM - 7.7.6
yarn - 1.22.10
App directory structure
/.git
/.idea
/node_modules
/src-tauri
/tiddlers
App
tauri.rs - 0.11.1
mode - embedded-server
build-type - bundle
CSP - default-src blob: data: filesystem: ws: http: https: 'unsafe-eval' 'unsafe-inline'
distDir - ../
devPath - ../
Additional context
I tried to reinstall rust, yarn, and tauri. No luck.
Today I will try to re-install MSBuild and C++ tools. Will update later.
A closed issue https://github.com/tauri-apps/tauri/issues/932 encounters the same error.

Since you are running the Alpha version, I am going to close this issue - the Beta.rc is literally in the process of being published and we will not support Alpha.
Please see:
https://github.com/tauri-apps/tauri/issues/1253


Miscellania Timer, "How much time remaining until cash runs out"

Basically what the title says.
Im always forgetting how many days or hours i have left, and adding a count down timer based on how much cash you have left vs what it takes per day would be awesome

Can be viewed on login as of 2d5d490b50d39bc53ba5ca6da257d3e1f2f9ff03


Batch OCR Invoice PDFs and extract text to input into web based fields - can but hard

Hi! I am currently trying to develop a RPA system where invoices that were scanned manually(into PDF) are OCR-ed and specific text are then extracted for filling up fields in a web-based form. I was wondering if TagUI is able to do this?
A little background, I'm currently a uni student interning and was given this task to perform. I came across your tool while studying and was really impressed and am trying to use it for the task listed above.
Thank you for your help!!

Hi @Domsdorm see below link for a full solution and demo of what you mentioned. It is an automation script to solve Automation Anywhere Week 4 RPA challenge. The tough part is from converting from the unstructured image data into structured data. This is very tough to get right, and involve a lot of trial and error and work. You can see below link to know more about the considerations and options to do this.
https://github.com/kelaberetiv/TagUI/issues/1093#issuecomment-907996687

Thanks @kensoh for the reply! Currently am trying to bypass the firewall that my company has by using the steps you have told me about in the telegram group. I Will update if I run into any troubles when doing the code.
Really appreciate you taking your own free time to help. Cheers!

Currently am trying to run the code for the Week 4 RPA challenge but OpenJDK is needed, is there anyway to bypass this?
Also is there a way to check in the script if the invoice data(for example Invoice number) is correctly being pulled?

For 1st question, need OpenJDK / Java 64-bit to do the part on opening file explorer to choose file. But there is workaround, you can use r.upload() to choose the file without opening the file browser (criteria needed by organiser for the challenge). See this solution from another user - https://github.com/DanielCCF/BotGamesAA/blob/master/Week4/Solution-Python.py#L125
For 2nd question, this RPA package requires user to know Python. I'm assuming that you are new to Python that's why you ask this. Because the answer is already written in the Python script itself, the OCR of the image files and extracting the individual data like invoice number. This automation is hard to understand and do without Python knowledge. Most of it is Python programming knowledge, only some are RPA concepts related to this tool.

Yupp I'm not from a CS background but am interested in learning more. Thank you for your patience tho 😅

Currently I am trying to select a drop down option (incoming WO) using . I am able to select the main header but am unable to select the Incoming WO option.

')
r.click('//[@aria-haspopup="hauptMenu:submenu:12"]')
r.wait(1)
r.click('//[@tabindex=""-1">Incoming WO<"]
Is there a way to select that option? Or by using r.click(x, y). If using r.click(x, y) is possible, how do I know which x,y values to input.

You can try if using the r.select() works - see more on usage and examples in API section.


docs: update readme logo

Description

Update the README.md logo/banner

Related issue(s)
Resolves https://github.com/asyncapi/diff/issues/89

closed and reopened to see if we can trigger handing ci

/rtm


Suppress ValueError on lxml.etree._Comment objects

See https://github.com/Morgan-Stanley/pyfixmsg/issues/3 for details.

Fix will be applied by MS OSS team.


⚠ Bofrost.de has degraded performance

In c8cc10f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1521 ms

Resolved: Bofrost.de performance has improved in de3e0d7 after 6 minutes.


feat: allow port from env

Provides an alternate way to set the tcp port (or a default) from an environment variable rather than strictly by argv.

What's the use case?

To start next-ls with a port without needing to build command line arguments. My use-case is for starting from iex -S mix for development, however it can be useful in "prod" environments where argv may not be able to be passed.
It's more in-line with other configuration options existing as environment variables rather than command options (NEXTLS_AUTO_UPDATE and NEXTLS_BINPATH).

I think i'd be more inclined just to include another bin script, eg bin/iex or bin/start-iex
#!/usr/bin/env bash

cd "$(dirname "$0")"/.. || exit 1

iex -S mix run --no-halt -e "Application.ensure_all_started(:next_ls)" -- "$@"

would that accomplish your use case?

Using scripts under bin is a less optimal way of working with mix and iex. I was going to also turn that script into a mix alias/task after this PR is processed.
Again; it would be useful to have an alternative (or a user-provided default) to dealing with argv.

Using scripts under bin is a less optimal way of working with mix and iex

can you elaborate?
I am mostly prodding at this because I am attempting to glean the utility of this patch, but I think you are assuming that your statement here is self-evident.

can you elaborate?

Coming from Phoenix, rather than using a series of scripts under bin/ for common tasks like starting the server; the project uses mix through custom tasks and aliases in development.
For example, some common tasks that are mix tasks or aliases:

mix phx.server

Starts the phoenix application and all servers in the tree

mix phx.digest

to digest and compress static files for release

mix ecto.setup

is an alias for running multiple mix tasks together, these are ecto.create, ecto.migrate, and run priv/repo/seeds.exs

Which can then be additionally ran through iex, such that iex -S mix phx.server lets the developer test with in REPL, manually recompile() without restarting the server if needed, or prod and observe the system as it is running.
These are tasks that are isolated in scope to working with Elixir, rather than explicitly writing scripts that will be platform dependent; even within linux not everyone has bash by default. Just include another script for single line commands like that only goes so far before you have a directory filled with them, and mix is already working from the root directory that contains mix.exs. If you wanted to not litter scripts in that directory and try to unify their existing functionality you would then have to put together and deal with more complicated logic in bash, before even thinking of other platforms.
How this interacts with the port argument;
In development, starting the server is:

bin/start --port 9000
bin/start_iex --port 9000

Based on what you proposed

bin/start_iex_ash --port 9000

Potential future, based on that

bin/start_iex_fish --port 9000

Potential future, based on that

mix -- --port 9000
iex -S mix -- --port 9000

Now with the change in this PR, instead it is:
export NEXTLS_PORT=9000 (or windows equivalent)
Now port is set as 9000 for all further commands.

bin/start

Start from the script (excluded from windows)

mix

Start with mix

iex -S mix

Start with mix in iex

mix nextls.server or iex -S mix nextls.server

no_halt and Application.ensure_all_started from bin/start can be stored here, in this theoretical task which is a later proposed change that is not in the scope of this discussion.

And this change works with the original script, such that the a default port can be passed.
export NEXTLS_PORT=8999

bin/start

Starts with tcp port 8999

bin/start --port 9000

Starts with port 9000 instead

bin/start --stdio

Starts as stdio instead

bin/start --port asdf

Will still error

NEXTLS_PORT=asdf bin/start

will still error

NEXTLS_PORT=asdf bin/start --port 9000

will start on 9000 since the command arg as been passed

It's more flexible and shouldn't get in the way of existing functionality.

thanks for elaborating!
it seems to me like there isn't really a use case yet, as you explained the goal is more aligned with being more like phoenix (which i'm not sure entirely applies, as the phoenix mix tasks are used by a project consuming phoenix, not phoenix itself).
I'd be happy to reconsider if you find this extremely inconvenient during future contributions. but to me, it mostly seems like a way to not type a extra characters when starting the server locally.

It was something I found inconvenient during testing, with regards to how System.argv() was passing empty arrays instead of args when I directly started via mix and iex; as mix does have a bug with parsing arguments, which burrito ran into before.
Using NEXTLS_PORT=9000 mix  was meant to fix that issue.
I'll look into something else.


Where to map slack resources to my own org's resources when oauth completes?

Description
Hi there. My team is building a new slack app with slack bolt. I was looking for guidance on a particular question. We are currently building out the oauth flow which redirects to our own application after the user accepts the application scopes so that we can authenticate the user in our platform before completing oauth with slack. After authenticating the user in our platform we complete the oauth flow which eventually triggers the installationStore's storeInstallation method per example below:
installationStore: {
    storeInstallation: async (installation) => {
      if (installation.isEnterpriseInstall) {
        // support for org wide app installation
        return await database.set(installation.enterprise.id, installation);
      } else {
        // single team app installation
        return await database.set(installation.team.id, installation);
      }
      throw new Error('Failed saving installation data to installationStore');
    },
    ...
  },

The problem that I am facing is that when I store the installation I also want to be able to link up the relationships between the slack user and the user I know in my own application (i.e. slack user id <> my orgs user id). However, there is nothing that I can pass into this callback from the request that would allow me to do that. What I would like to be able to do is read from the request so I can pull out org specific information that I can use when storing tokens. For example
storeInstallation: async (request, installation)
Would appreciate feedback from this request or perhaps a suggestion on how to best handle this problem.
Thanks!
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[X] enhancement (feature request)
[X] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[X] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[X] I've read and agree to the Code of Conduct.
[X] I've searched for any related issues and avoided creating a duplicate issue.

Hi @TroutZen,
Thanks for reaching out and clearly explaining your use-case!
At the moment, @slack/bolt-js and @slack/oauth don't provide a built-in way for you accomplish your goal. However, your issue has sparked a nice discussion between some of the Bolt framework maintainers. I think we'd all like to see more flexibility, so that you easily add some before/after logic to an installation.
For now, I've labelled this as a question but I think we can turn it into a discussion when we have a loose proposal. Currently, the discussion is considering a beforeInstallation and afterInstallation callback that provides access to {req, resp, installOptions}.
If you have any initial thoughts, feel free to drop them here!

Thanks @mwbrooks, I think passing in req, resp, installOptions would allow us to accomplish our goals in this scenario. I should note that we are using custom koa endpoints that delegate calls into installer.handleCallback because of the need to perform some custom logic before bolt's internals take over. In this scenario it would nice if we could pass in custom args that eventually get passed into storeInstallation, but that feels like a much more specific / nuanced use case.
The only additional thing I might add is that we considered adding some of this logic to installer.handleCallback's success callback, but also ran into challenges there because the success callback was not async and because the success callback also did not have access to req or res.

Hi @TroutZen, thanks for your prompt reply here!

In this scenario it would nice if we could pass in custom args that eventually get passed into storeInstallation, but that feels like a much more specific / nuanced use case.

If I understand your use case correctly, enhancing the storeInstallation method does not work for you in the best way. Slack app installations are done when your app performs an oauth.v2.access API call with given code query parameter. The storeInstallation method is supposed to be called after an installation completes. Even if you don't store the tokens and its metadata, the installations are already successfully completed.
If you are thinking to revoke the installation (by calling auth.revoke API method) in storeInstallation method, it may work in some situations. That being said, obviously it's not a straight-forward solution.
This is why our team discussed the necessity to introduce a new method like beforeInstallation (although we haven't decided to work on it in the short term).

ran into challenges there because the success callback was not async

Thanks for the input. We've been aware of this but changing this is a breaking change. In future major version upgrades, we may improve it.

Hello @TroutZen, did you find a solution to map your installation with you own org data?
I'm facing the same problem, I can't find a way to link a slack installation to our data.

@RomainCscn Currently, the @slack/oauth package does not provide any easy way to achieve your global. We are planning to add new callbacks that Michael mentioned above https://github.com/slackapi/bolt-js/issues/1211#issuecomment-973283010
Due to other priorities, we didn't have the bandwidth to work on it but recently I started using my time for the OAuth package improvements including this task.
It won't take long but we cannot tell when we can ship the new features yet. If you need an immediate solution, one workaround that I have to suggest is to go with your own implementation reusing some parts of the OAuth package such as the authorize URL generation. With this way, you can set any cookies to your end-user's browser session. That would be much easier way. I hope this helps.

https://github.com/slackapi/bolt-js/pull/1391 enables a new way to handle this use case. Since the next version, developers can utilize installPathOptions.beforeRedirection and callbackOptions.beforeInstallation to do additional validation and so on.
Checking "Persisting data during the OAuth flow" section in https://slack.dev/node-slack-sdk/oauth would be helpful to understand how to use those callback functions.
Let me close this issue as the one that will be resolved in v3.11 release milestone.

@RomainCscn If everything goes well, we can ship it within a few business days! I've done with all the remaining pull requests for the release and am waiting for reviews by other maintainers. At least, we can release beta or RC version in the time frame.


Share speech URLs on File and Channel pages

New PR for #1028 @tzarebczan @liamcardenas
This creates <ViewOnWebButton> with a GLOBE icon and uses it on <FilePage> and <ChannelPage>
Also fixes ~10 eslint errors

I am not sure what's going on with this conflict in src/renderer/scss/component/_form-field.scss
What Github tells me is a problem on lines 54-58 is not a problem locally

Can you rebase and get this up to date?

@seanyesmunt Tired of adding buttons to the show page yet? haha Wonder how this fits in with your changes to file actions. I'll try to give it a whirl today.


Portuguese translation

Benjamin Coe posted on twitter. I hope this helps and good luck :)

Thank you so much @codemonkey3045!
Note that the following y18n keys will change with PR #222:

"not enough arguments following: %s" -> "Not enough arguments following: %s"
"invalid json config file: %s" -> "Invalid JSON config file: %s"

And I see you've already taken care of the other inconsistencies ("json" -> "JSON" and uncapitalized error messages). Awesome!
If you don't get a chance to update the locale keys in pt.json, I can take care of it when we merge. Thanks again! :smiley:

@codemonkey3045 \o/ you rock!

Besides the additional es.json file, this looks good to me. :+1:

@codemonkey3045 this is awesome, can't wait to unveil at braziljs, would you mind deleting es.json from your commit -- we made a few edits to this language file and merged it on another branch.

Closing this in favor of #227. Thank you, @codemonkey3045, for the translation! :monkey_face:


Setuptool bug to watch

Installing as developper (pip install -e .) makes a warning:
l2t_train_model.py -h:
DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
import('pkg_resources').require('dwi-ml==0.1.0.dev0')
In my environment:
cat bin/l2t_train_model.py:  The buggy line is: import('pkg_resources').require('dwi-ml==0.1.0.dev0')
See their PR: https://github.com/pypa/setuptools/issues/3878

Indeed, pkg_resources is deprecated. I don't see pkg_resources being imported explicitly in dwi_ml, so after searching a bit, here's what I'd try:

Try with another more recent version of setuptools.
From the below issues/posts, it looks like it is through pip that this happens, so by using a more recent version of pip we may solve the problem (in any case, each time we use pip and there is a newer version, pip suggests us to install it):
https://github.com/pypa/pip/issues/11975
https://stackoverflow.com/questions/76043689/pkg-resources-is-deprecated-as-an-api/76044568#76044568
Also related:
https://github.com/pypa/pip/pull/11997
https://github.com/opentensor/bittensor/issues/1487

We can discuss tomorrow/Monday/next week if none of the above works for you.

Thanks!

My pip version is already the latest (23.2.1)
I had setuptools 68.0.0. I upgraded to 68.2.2 and reinstalled dwi_ml, it didn't fix it.

If it can help, here is my file my_env/bin/dwiml_visualize_logs.py:
# EASY-INSTALL-DEV-SCRIPT: 'dwi-ml==0.1.0.dev0','dwiml_visualize_logs.py'
__requires__ = 'dwi-ml==0.1.0.dev0'
__import__('pkg_resources').require('dwi-ml==0.1.0.dev0')
__file__ = '/home/local/USHERBROOKE/rene2201/my_applications/scil_vital/dwi_ml/scripts_python/dwiml_visualize_logs.py'
with open(__file__) as f:
    exec(compile(f.read(), __file__, 'exec'))

So was the pip version different in the new environment wrt the previous one?
As for the las error, if there is somewhere a grearer than or equal, I guess pip will try to install the latest version, and some other dependency may have made pip download the latest version under the hood. Easiest would be to make the dwi_ml version match the one in scilpy, as, even if unnlikely, the latrer may impact more end users.

(The requests version is now updated and the issue is not fixed, so I deleted previous comments. I can't reproduce a "clean" environment anymore.).


Make task states dynamic

Download task types from onedev.

@am7c7
Implemented
Unfortunately task types in Intellij are limited to
    BUG,
    EXCEPTION,
    FEATURE,
    OTHER;

Let me know if this mapping makes sense
        return switch (type) {
            case "Task", "New Feature" -> TaskType.FEATURE;
            case "Bug" -> TaskType.BUG;
            default -> TaskType.OTHER;
        };

I'm sorry for the miscommunication, I meant Task States ("open", "closed", etc.)

OneDev has no concept of closed tasks. It just define states, and user tells OneDev which state they are caring about. So at Intellij side, the plugin setting UI needs to have a setting to let user choose which states are considered "closed", and relevant operations can use this setting to do things right, such as "include closed" when open tasks, or the state switching to when "close the active task", etc.
Task states can be obtained via settings api:
https://code.onedev.io/~help/api/io.onedev.server.rest.resource.SettingResource/getIssueSetting
Also when I open a new task at Intellij side, no corresponding issues are opened at OneDev side. Is this intended behavior of the plugin?

Also OneDev issue has custom fields (such as type/priority etc). The plugin may have a setting to let user specify values of these custom field when open/close a new task. Field settings can also be retrieved via above api.

@robinshine Thanks, I've figured out most of that by reading the OneDev source code.
We're using the 'Closed' state for now

Also when I open a new task at Intellij side, no corresponding issues are opened at OneDev side. Is this intended behavior of the plugin?

Current version of the plugin is built around the Task API (some docs here https://intellij-support.jetbrains.com/hc/en-us/community/posts/207098975-Documenation-about-Task-Api) which only provide a limited set of actions. See also https://github.com/JetBrains/intellij-community/blob/master/plugins/tasks/tasks-api/src/com/intellij/tasks/impl/BaseRepository.java and related classes

Also when I open a new task at Intellij side, no corresponding issues are opened at OneDev side. Is this intended behavior of the plugin?

Tasks can be used without servers in Idea. The "Create new task" doesn't seem to be intended to create a task/issue on the server. I think it assumes that tasks/issues are created on the server by other means.

We're using the 'Closed' state for now

We dont have an 'Open' state and dont have an 'Closed' state. Both are named differently because we have a whole state transition workflow defined in OneDev. For us 'Open' would be 'Ready to implement' and 'Closed' would be 'Committed'

@jnehlmeier Looks like I have to add an option to select the 'Closed' state(s). Is the 'Open' (initial state) the first one on the state list in your case?
@am7c7
At the same time from what I see in the code, these states are not actually used by the Tasks API directly, so it's no big deal. The only place where the 'Closed' state is used is filtering by 'Closed' tasks (Include closed tasks), but this part is handled by our code.
There are two possible solutions:
A) Add the ability to select 'closed' states in the UI
B) Add additional user-configurable 'query' for the 'Closed' tasks

Also when I open a new task at Intellij side, no corresponding issues are opened at OneDev side. Is this intended behavior of the plugin?

Tasks can be used without servers in Idea. The "Create new task" doesn't seem to be intended to create a task/issue on the server. I think it assumes that tasks/issues are created on the server by other means.

Got it!

@alex-sc If we create a new issue in Onedev it has the state "new" (which is the first state in the list of states). From this state the issue moves through multiple states until it ends up in "ready for implement". At that stage developers can pick up the issue. That is why I would treat that state as the 'open' state in IntelliJ.
For 'closed' issues we also have multiple states: 'wont fix', 'committed' and 'released'. Also from a developer point of view issues that are assigned to other developers are kind of closed because a developer cannot work on them.
I think the most flexible would be to have two queries: one for open issues and one for closed issues and the plugin then merges both results if closed issues should be included in the IntelliJ UI.


Elasticsearch org separation

I changed the search module to create a separate index for each organization.
This has some implications: Data without an organization related to it will no longer be able to be indexed and testing for non existing indicators does not work anymore at this point (because it requires a workflowlevel1 to be associated to an indicator but this is only possible if an object exists, therefore an indicator would be created). see test_delete_unexisting_indicator_raises_exception

Sorry used the wrong branch

Coverage increased (+1.5%) to 50.62% when pulling 7229210fe0aa93f22d10636cd639324f8b8849a2 on elasticsearch-org-separation into b312d3103b52c451ac4e2d16386cc73e14c098de on master.

For next time: you don't need to close the PR, just click on "Edit" and change the branch.


Unsup SimCSE for Different Batch Sizes

Dear Author,
thank you for sharing this amazing piece of work :) 👍
I have a question about the paper where it says:
"We carry out grid-search of batch size ∈ {64, 128, 256, 512} and learning rate ∈ {1e-5, 3e-5, 5e-5} on STS-B development set and adopt the hyper-parameter settings in Table A.1.  We find that SimCSE is not sensitive to batch sizes as long as tuning the learning rates accordingly, which contradicts the finding that contrastive learning requires large batch sizes."
The part "as long as tuning the learning rates accordingly." concerns me. For batch size of 512, what learning rate would you recommend (for unsupervised SimCSE)? It seems like it is not that easy to figure it out 😢  In your experiments, what learning rates did you use for different batch sizes to confirm such insensitivity?
Thank you in advance! :)

Hi,
We simply tried all combinations of (64, 128, 256, 512) x (1e-5, 3e-5, 5e-5) and picked the best. We provided the combinations we used in Appendix A of our paper.

Thank you! :)


Unable to play audio file from asset and getting MissingPluginException error

I'm trying to play audio file from asset in Flutter windows application, but it is giving the MissingPluginException error
I have created a directory named assets and place .mp3 file in that directory
This is my code snippet:
  AudioCache audioCache = AudioCache();

playSound()
{
    audioCache.play('tone.mp3', isNotification: true);
}

This is my pubspec.yaml file code:
    - img/
    - assets/tone.mp3

On execution of this code the following exception appears:
[ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: MissingPluginException(No implementation found for method play on channel xyz.luan/audioplayers)
#0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:175:7)
<asynchronous suspension>
#1      AudioPlayer.invokeMethod (package:audioplayers/src/audioplayer.dart:151:20)
<asynchronous suspension>
#2      AudioPlayer.play (package:audioplayers/src/audioplayer.dart:173:20)
<asynchronous suspension>
#3      AudioCache.play (package:audioplayers/src/audio_cache.dart:164:5)
<asynchronous suspension>

flutter doctor output is:
D:\Code\test>flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.2, on Microsoft Windows [Version 10.0.19044.1645], locale en-PK)
[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.9)
[√] Android Studio (version 2020.3)
[√] Connected device (3 available)
[√] HTTP Host Availability

• No issues found!

I don't get the reason of this error. In the main features table of documentation, it shows support for windows.
Please help me to solve this issue.

Guessing you're still on 0.20.1, which doesn't support Windows.
v1 hasn't officially landed yet, but can be used by adding audioplayers: ^1.0.0-rc.1

Thanks alot. It workedd


cpu priority macos

you can define a process to have high priority (kind of real time) in macos
have you given any thoughts to do this for this library ?
i have streaming drop when the cpu spikes due to other activiy

I feel like this is out of scope of this library


Resources requests/limits for NATS cluster CRD

Hi guys!
Is there any possibility to set a container resources (req/lim) for NATS cluster?

I'm looking for that option as well. Is there anything possible with the spec.podTemplate key?

You can use podPolicy spec.pod to set the container resource limits.
spec:
  pod:
    resources:
      limits:
        cpu: "200m"
        memory: "500Mi"
      requests:
        cpu: "100m"
        memory: "100Mi"

Seems like this has been answered. Closing for now, feel free to reopen if necessary.


html to xlsx export format problem in column

when i export html  data to xlsx i cant say that column should be formatted as text. my problem is, i have telephon number with 0 at first and its exported in excel to:
4,94335E+12 instead of for example<PHONE_NUMBER>410
i tried in  tag: 00001234
and i tried

both not works :(
i use this script:
https://redstapler.co/sheetjs-tutorial-html-table-to-excel/

Make sure you are using the latest version of the library: https://unpkg.com/xlsx/dist/xlsx.full.min.js will serve the latest version on NPM.
Small demo https://jsfiddle.net/5fqkgs9d/


Final Shout crash on player death

Crash log: https://gist.github.com/DaedalusGame/5c6c6c93981b7907f014591a6b6fc2cd
Seems to happen anytime a player with the Final Shout enchant dies, but said player has very very low health, so I'm not convinced it just happens when one dies.

Ah, simple sidedness issue. Easy fix, expect it out in a bit.

It's up.


node_exporter: 0.18.1 -> 1.0.0

Motivation for this change
https://github.com/prometheus/node_exporter/releases/tag/v1.0.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This change is

@GrahamcOfBorg test prometheus


Asyncio example does not run

I was investigating using this library. I've had Consul running and tried to run the asyncio example script from the docs by copying and pasting it into a file.
I expected it to run but if failed and reported the following error:
demo.py:8: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead
  def go():
Traceback (most recent call last):
  File "demo.py", line 26, in <module>
    loop.run_until_complete(go())
  File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "demo.py", line 15, in go
    response = yield from c.kv.put(b'foo', b'bar')
  File "/consul-demo/venv/lib/python3.8/site-packages/consul/base.py", line 3018, in put
    assert not key.startswith('/'), \
TypeError: startswith first arg must be bytes or a tuple of bytes, not str

The error is caused because the put function has an assert statement to check whether the key begins with the string '/'. However, the arguments being passed to the function are bytes which causes the error.
Arguments used in other example scripts are all strings. I'm assuming that the API used to take either bytes or strings but changed to only strings at some point and this particular example script did not get updated to reflect a recent change to only use strings.
It seems like a docs update is needed.

After fixing the input args problem mentioned above, by changing the args to strings (b'foo' -> 'foo' and b'bar' -> 'bar'), I encountered another two problems running the example script.
The first problem was that after calling the get function the returned value was actually a bytes object, whereas it was a string when the put function was called. I'm not sure what to recommend here - the behaviour is confusing. I have since run the synchronous example script from the docs (under the heading "Standard") and it too produces a bytes object - whereas the docs indicate that it returns a string.
The second problem was in the delete step which deletes key foo2. This fails - because the steps previously added a key called foo.
Change
    response = yield from c.kv.delete(b'foo2')

to
    response = yield from c.kv.delete(b'foo')

Looks like some bit-rot in the docs examples.

Because python2 response.content return a str ,when python3 response.content return bytes
You are right ,the document has not been updated or differentiated accordingly, so please do not worry that it will be revised in the future

Hey guy, would you be interested in giving me a PR

Which part is in need of a pull request? I was able to compile the asyncio example without editing the library. Is it just the docs?

Pretty sure it is just a docs problem. When a user tries to follow them they result in an error.

Yea, I copied the code from the old repository before finding this. I couldn't really get that compile without editing the example. I'll look into this if I have some free time.


Added installation info for this.

The package is called "nosegae" in pip.
Feel free to delete or reformat the output I included for reference.

I am closing this due to #12

Thank, Trii.


Security fix: Changes the default API endpoint to the https version

While the previous http endpoint that was used by default does redirect to the https version, I think it would be a lot safer to not depend on that.
Also, and correct me if I'm wrong, but by the time we receive the redirect response from the server we have already sent of the payload in plain-text http for any man-in-the-middle to read?

Ah, good catch, thanks. (Didn't notice Mandrill had released an https endpoint, but glad they did.)
Anyone wanting an immediate fix (or stuck on an older version of Djrill for some reason) can achieve the same thing by adding this to their settings.py:
MANDRILL_API_URL = "https://mandrillapp.com/api/1.0"  # note the 's'

And yes, you're correct that the current http-->https API redirect could have exposed the plaintext contents of your Mandrill API calls, if the network path from Djrill to the Mandrill API servers is vulnerable to MITM.

Released to PyPI in djrill==1.3