When I run Sample app make a mistake.

hi,
root@ubuntu# ./SampleApp ../../Integration/AlexaClientSDKConfig.json DEBUG9
Running app with log level: DEBUG9
2017-10-12 08:42:19.906 [  1] I ConfigurationNode:initializeSuccess
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechSynthesizer,name=Speak,handler=0x8da86f0,policy=BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=ClearQueue,handler=0x8da9768,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=Stop,handler=0x8da9768,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=AudioPlayer,name=Play,handler=0x8da9768,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechRecognizer,name=ExpectSpeech,handler=0x8da7f48,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=SpeechRecognizer,name=StopCapture,handler=0x8da7f48,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Alerts,name=DeleteAlert,handler=0x8daa788,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=Alerts,name=SetAlert,handler=0x8daa788,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=System,name=SetEndpoint,handler=0x8de90d8,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  1] I DirectiveRouter:addDirectiveHandlers:action=added,namespace=System,name=ResetUserInactivity,handler=0x8da7d3c,policy=NON_BLOCKING
2017-10-12 08:42:19.942 [  2] I AlertsCapabilityAgent:executeScheduleNextAlertForRendering::no work to do.
#############################
Connecting...
#############################
2017-10-12 08:42:23.539 [  3] I StateSynchronizer:requestingContext:reason=connectionStatusChanged,receivedStatus=CONNECTED
##################################################
Performing post connect actions...
##################################################
2017-10-12 08:42:25.312 [  4] I StateSynchronizer:messageSentSuccessfully
########################################
Alexa is currently idle!
########################################
Home directory not accessible: Permission denied
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (MIXER,'AC97 2ch->4ch Copy Switch',0,0,0): No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (MIXER,'AC97 2ch->4ch Copy Switch',0,0,0): No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (PCM,'IEC958 Playback PCM Stream',0,0,0): No such file or directory
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (PCM,'IEC958 Playback PCM Stream',0,0,0): No such file or directory
ALSA lib setup.c:548:(add_elem) Cannot obtain info for CTL elem (PCM,'IEC958 Playback PCM Stream',0,0,0): No such file or directory
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
Home directory not accessible: Permission denied
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused
Home directory not accessible: Permission denied
ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
#    #     #  #####      #####  ######  #    #
# #   #     # #     #    #     # #     # #   #
#   #  #     # #          #       #     # #  #
#     # #     #  #####      #####  #     # ###
#######  #   #        #          # #     # #  #
#     #   # #   #     #    #     # #     # #   #
#     #    #     #####      #####  ######  #    #
   #####                                           #
  #     #   ##   #    # #####  #      ######      # #   #####  #####
  #        #  #  ##  ## #    # #      #          #   #  #    # #    #
   #####  #    # # ## # #    # #      #####     #     # #    # #    #
        # ###### #    # #####  #      #         ####### #####  #####
  #     # #    # #    # #      #      #         #     # #      #
   #####  #    # #    # #      ###### ######    #     # #      #

+----------------------------------------------------------------------------+
|                                  Options:                                  |
| Tap to talk:                                                               |
|       Press 't' and Enter followed by your query (no need for the 'Alexa').|
| Hold to talk:                                                              |
|       Press 'h' followed by Enter to simulate holding a button.            |
|       Then say your query (no need for the 'Alexa').                       |
|       Press 'h' followed by Enter to simulate releasing a button.          |
| Stop an interaction:                                                       |
|       Press 's' and Enter to stop an ongoing interaction.                  |
| Info:                                                                      |
|       Press 'i' followed by Enter at any time to see the help screen.      |
| Quit:                                                                      |
|       Press 'q' followed by Enter at any time to quit the application.     |
+----------------------------------------------------------------------------+
t
2017-10-12 08:42:31.513 [  5] I DirectiveProcessor:setDialogRequestIdLocked:oldValue=,newValue=b1764b01-4cc0-44a4-99e5-9471ceec2fa9
############################
Listening...
############################
2017-10-12 08:42:37.346 [  3] I DirectiveSequencer:onDirective:directive={"namespace:"SpeechRecognizer",name:"StopCapture",messageId:"6e577cc8-9221-4248-b262-8b96f3349a72",dialogRequestId:""}
2017-10-12 08:42:37.347 [  6] I DirectiveRouter:preHandleDirective:messageId=6e577cc8-9221-4248-b262-8b96f3349a72,action=calling
2017-10-12 08:42:37.348 [  7] I DirectiveRouter:handleDirective:messageId=6e577cc8-9221-4248-b262-8b96f3349a72,action=calling
###########################
Thinking...
###########################
2017-10-12 08:42:37.357 [  4] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################
Alexa is currently idle!
########################################

Hi snailwft,
This looks like a setup issue - all those lines of ALSA trace should not occur.  Can you please refer to this page:
https://github.com/alexa/avs-device-sdk/wiki/Linux-Quick-Start-Guide#minimum-requirements-and-dependencies
and pay particular attention to audio components.  You probably need to install or update some components.  Let us know if this solves your problem.

hi @dhpp
what't wrong with this
Thinking...
###########################
2017-10-12 08:42:37.357 [ 4] I InProcessAttachmentReader:readFailed:reason=SDS is closed
########################################

In my ubuntu, gst-play-1.0 XXX. Mp3 is work normal, and aplay XXX. Wav is normal, can you send a Sample app to run the normal log to me?

@snailwft solve ? me too

I found this to be a normal phenomenon, starting with no microphones, not normal testing, and then I plugged into a microphone and said "what's your name" to the microphone, and he said"my name is alexa."

@snailwft ALSA lib confmisc.c:674: (snd_determine_driver) could not open control for card 0 encountered in the operation process?


Compatibility check and testing for Node.js 14 and 16

Dear Adapter developer,
Node.js 14 is now available for a year and Node.js 16 was release just some days ago and will become LTS by October 2021. We plan to update the ioBroker Node.js recommendation (currently 12.x) to 14.x later this year.
Please check your adapter with Node.js 14 especially, and ideally also directly with Node.js 16
Please add both versions to the adapter testing which is executed on commits.
If your adapter requires a certain minimum version of Node.js please set the 'engine' setting in package.json accordingly! Please also do this if the adapter is not able to work in certain Node.js versions, so that ioBroker can prevent users from installing te adapter if not compatible!
On questions please talk to us at https://github.com/ioBroker/ioBroker.js-controller/issues/1138
Please close the issue after you checked it.
Thank you very much for your support!

Travis only throws errors with node16 and Windows.
But it works on my computer with node16 and windows.


Enable complex number types for tile op

I've enabled complex64 and complex128 on the CPU for tf.tile and added them to the tests.

Can one of the admins verify this patch?

@tensorflow-jenkins test this please


What's the purpose of the related EmployeeSpecification in ModelWithLookupComplexRepository.Create?

This method is misleading, and a test, ModelWithLookupComplexTests.FoulLookupTable is wrong (as in: what is it testing? That the signature on the repository is wrong?)
The main issue is that the FoulLookup test creates an entity graph and persists this through the ModelWithLookupComplexRepository.Create(). However, as the method changes the entity, saving the graph thus will also save the related entity, so both the new Employee and the related EmployeeClassification entity are saved (as both are changed, employee is new and its associated EmployeeClassification has been changed (FoulLookup, line 179)
If the related entity EmployeeClassification shouldn't be persisted, then the repository should clearly tell me that. However as microORMs don't do graph persistence this isn't really visible, and the EF Core repository reads a new instance of the passed in EmployeeClassification entity (of course otherwise the test would fail, but this makes no sense at all. No-one in production would use it this way. )
I can of course tell my framework not to persist things recursively and the test will pass. That's not the point: this is a 'recipe' book for people who want to see how things are done. IMHO the whole point of the test and repository is wrong and doesn't teach anyone anything other than how not to do it.

Same thing with the update. I now have to block recursive graph updates everywhere because some microORM can't deal with this and the test explicitly pushes a change in a related entity to the repository. Sorry, what's the point of these repositories anyway if they can't deal with related entities :D yeah I know DDD the book blablabla, that's why some people write books and others write software.

This use case covers scenarios where you explicitly don't want recursive saves. For example, when the child object(s) represent lookup tables that the user doesn't have permission to edit.
I see this from time to time in "REST" frameworks where you always pass around objects instead of just keys.

There's going to be another use case where you explicitly do want recursive saves. So turning it off globally might not be your best option.
I realize that this is a frustrating use case, but in a way that's the point. This is the kind of stuff developers fight with from time to time.

Ok makes sense. I've limited the persistence in these particular repositories to a single entity to make sure things work ok, although I do think the main problem is the whole repository concept which is always a problematic affair (what to do with related entities in that case is a debate that never ends :) ).
I can set the related entity also to readonly in my model, but that's in this case not useful as the same entity is also used for updates :)

Can be closed. :)


TypeError 'int' object is not iterable when doing a third attic create for local repository

Host is Opensuse 13.2
Python 3.4
Attic 0.16
I've checked https://github.com/jborg/attic/issues/171 and think it is not the same isssue  as msgpack is 0.4.6
This host had some VM client issues prior to this issue but I've run attic check and there were no issues reported.
attic create --stats $REPOSITORY::localhost-`date +%Y%m%d` / --exclude={"/sys","/proc","/dev","/run","/export/backups","/export/install",/mnt}
Traceback (most recent call last):
File "/usr/bin/attic", line 3, in
main()
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 730, in main
exit_code = archiver.run(sys.argv[1:])
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 720, in run
return args.func(args)
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 129, in do_create
self._process(archive, cache, args.excludes, args.exclude_caches, skip_inodes, path, restrict_dev)
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 178, in _process
os.path.join(path, filename), restrict_dev)
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 178, in _process
os.path.join(path, filename), restrict_dev)
File "/usr/lib64/python3.4/site-packages/attic/archiver.py", line 164, in _process
archive.process_file(path, st, cache)
File "/usr/lib64/python3.4/site-packages/attic/archive.py", line 402, in process_file
ids = cache.file_known_and_unchanged(path_hash, st)
File "/usr/lib64/python3.4/site-packages/attic/cache.py", line 259, in file_known_and_unchanged
self._read_files()
File "/usr/lib64/python3.4/site-packages/attic/cache.py", line 130, in _read_files
for path_hash, item in u:
TypeError: 'int' object is not iterable

Looks like the cache for that repo is corrupted somehow - can you just delete the cache and retry?
cat repo/config  # find out the REPOID
rm -rf ~/.cache/attic/REPOID

That's fixed it thank you very much.


Support JSON and JSONB types as escaped strings

Currently, json/b columns are excluded from the schema
Enable them, and treat them as escaped strings

Is there anything we can do presently to enable this manually?

json/jsonb types are currently disabled because, by default, they render as actual json objects through the graphql api, rather than json represented as escaped strings.

Is there anything we can do presently to enable this manually?
no, but we expect them to be supported officially inside a few weeks

@olirice is there a PR in the works to demonstrate the support? Definitely need this functionality!

sorry for the slow reply @levimichael
There is not currently a PR. If I remember right this got yanked because it needed some touchups before the first version of pg_graphql went GA and we ran out of time (vs it being hard to implement)
I'll take a look tomorrow and open a PR or follow up

Q:

Would query-only support be useful to you or do also need to write to a json/b field?

Just want to chime in and mention that write support is important to my use case. For reads and writes, right now I’m just using the Postgrest API via the JS client for this specific table and GraphQL for everything else because of that limitation

Would query-only support be useful to you or do also need to write to a json/b field?

I will need writes as well. Not super urgent right not but I will appreciate being able to use this!


update news

👷 Deploy Preview for across processing.

Name
Link

🔨 Latest commit
d61faf029f941b927854d17b9409b8fd21ffca8f

🔍 Latest deploy log
https://app.netlify.com/sites/across/deploys/65108112edf7060008c713bd


update nightly pull, remove polygon tolerance, update pathAPI using d…

update nightly pull using dask etl
remove polygon tolerance as it is unused now
update pathAPI using dask etl datastore for regional annotation requests

Codecov Report

Merging #181 (0667ba6) into master (2ebb7ec) will decrease coverage by 0.05%.
The diff coverage is 42.85%.

@@            Coverage Diff             @@
##           master     #181      +/-   ##
==========================================
- Coverage   51.98%   51.92%   -0.06%
==========================================
  Files          58       58
  Lines        5352     5381      +29
==========================================
+ Hits         2782     2794      +12
- Misses       2570     2587      +17

Impacted Files
Coverage Δ

data_processing/common/GraphEnum.py
100.00% <ø> (ø)

data_processing/common/constants.py
100.00% <ø> (ø)

...ta_processing/pathology/common/annotation_utils.py
0.00% <0.00%> (ø)

...refined_table/regional_annotation/dask_generate.py
0.00% <0.00%> (ø)

data_processing/common/DataStore.py
46.66% <25.92%> (-1.65%)
:arrow_down:

data_processing/pathology/common/build_geojson.py
70.34% <44.44%> (-1.19%)
:arrow_down:

...pathology_annotations/get_pathology_annotations.py
67.53% <90.00%> (+2.82%)
:arrow_up:

data_processing/common/Node.py
93.40% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add structural templates as alternative to text placeholders

Fixes https://github.com/argoproj/argo/issues/1293 : "Argo should provide a (limited) set of functions available in templates to support basic tasks like string modification."
Argo's text placeholders are limited and is not flexible enough .
Even with the current very limited placeholder support, it's impossible to call some programs that use go format templates (e.g. docker) since their templates clash with Argo syntax.
I have experience with many custom text-based templating languages and all of them were painful or impossible to use for some cases.
The solution is to use structural templates. There are many advantages of structural templates over text-based templates:

Templating system is very easy to extend.
No need to reinvent the wheel and write a complicated fragile parser that's still going to break.
Templates do not conflict with any verbatim texts.

With structural templates we can even support multiple templating engines.
Structural templates utilize the language that Argo workflows already use - YAML.
Here is a pretty complex example that uses concat and substring to construct the full image name  out of the base image name and the shortened revision:
command: [
  docker,
  tag,
  {inputValue: source-image},
  {concat: [{inputValue: image-name}, ':', {substring: {str: {inputValue: revision}, count: 6}]}
]

P.S. {inputValue: source-image} is the structural equivalent of "{{inputs.parameters.source-image}}".
Here is an example of structural templating in a component/template definition: https://github.com/kubeflow/pipelines/blob/5043ec78afc63506ce70fca01d2936928cb0fedb/components/gcp/automl/create_dataset_for_tables/component.yaml#L109

This is fixed by Expression Tag Templates in v3.


City is not defined

app.getForecast(city.key, city.label); // city is not defined anywhere in the same code or steps till step 5 so the execution is throwing runtime error.

never mind, I missed this line - it's there so closing this issue.
app.selectedCities.forEach(function(city) {


PySolFC: 2.0 -> 2.6.4

Motivation for this change
2.0 was released in  2010-06-09 . It seems like an unmaintained derivation.
CC @kierdavis
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-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)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pysol

@GrahamcOfBorg build pysolfc

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: pysolfc
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Unexpected error: command failed with exit code 1 on x86_64-linux (full log)
Attempted: pysolfc
Partial log (click to expand)
100   280  100   280    0     0    942      0 --:--:-- --:--:-- --:--:--   939
100   274  100   274    0     0    300      0 --:--:-- --:--:-- --:--:--   300
100   276  100   276    0     0    258      0  0:00:01  0:00:01 --:--:--     0
100   272  100   272    0     0    222      0  0:00:01  0:00:01 --:--:--   222
100   274  100   274    0     0    198      0  0:00:01  0:00:01 --:--:--   198
100  125k  100  125k    0     0  65215      0  0:00:01  0:00:01 --:--:-- 65215
fixed-output derivation produced path '/nix/store/d248z5jzi73906r0nnv2cfacq069bpv5-PySolFC-Cardsets-2.0.tar.bz2' with sha256 hash '05w9cwd0i2r7bfzng006wiknbydk6k0nwgjvxdgb22lwczskplda' instead of the expected hash '19vwykrj72bygli8a6krdv9kwkhc4rj5lknqcgjbgcwi04vdd263'
copying path '/nix/store/gk7b105bphmd8a984i2p17iy135zqqzv-python2.7-pygame-1.9.4' from 'https://cache.nixos.org'...
cannot build derivation '/nix/store/ams4y5y5kk5k8vwks2vkq3z6icg96wyy-PySolFC-2.4.0.drv': 2 dependencies couldn't be built
error: build of '/nix/store/ams4y5y5kk5k8vwks2vkq3z6icg96wyy-PySolFC-2.4.0.drv' failed

Unexpected error: command failed with exit code 1 on aarch64-linux (full log)
Attempted: pysolfc
Partial log (click to expand)
100 15648  100 15648    0     0  20035      0 --:--:-- --:--:-- --:--:-- 20035
100 15648  100 15648    0     0  19807      0 --:--:-- --:--:-- --:--:-- 19807
100 15649  100 15649    0     0  18049      0 --:--:-- --:--:-- --:--:-- 18049
100 15649  100 15649    0     0  17864      0 --:--:-- --:--:-- --:--:-- 17864
100  143k  100  143k    0     0   127k      0  0:00:01  0:00:01 --:--:--  127k
100  143k  100  143k    0     0   126k      0  0:00:01  0:00:01 --:--:-- 47.5M
fixed-output derivation produced path '/nix/store/fdjx0lmaybln6vrl6mazb7v9261m59vi-PySolFC-Cardsets-2.0.tar.bz2' with sha256 hash '1yk5d59wc3bch32npsbyp54a8m92878d0815viln88mgxkm5nb2f' instead of the expected hash '19vwykrj72bygli8a6krdv9kwkhc4rj5lknqcgjbgcwi04vdd263'
fixed-output derivation produced path '/nix/store/86gf56x3wxdgpgsc7i65s3xbmi2ay5ip-PySolFC-2.4.0.tar.xz' with sha256 hash '1cvmvlp3ymxs7gyrgqjqcbjmsh1gp6n37j74nd2ddy0w2pcqj7z9' instead of the expected hash '0dcc8izmlqcl7swk4gidp3bvbmjxqppriyl4c9v3vb21v09kjsa4'
cannot build derivation '/nix/store/5x3ga3lc2hpq5l9f3j7w0bh1mrr9pgr6-PySolFC-2.4.0.drv': 2 dependencies couldn't be built
error: build of '/nix/store/5x3ga3lc2hpq5l9f3j7w0bh1mrr9pgr6-PySolFC-2.4.0.drv' failed

the hash are good, sf is always a nightmare. i spent so many hours on such SF download issue, and have no good feedback from nixos maintainer, when i skip mirror:// syntax or others tricks.

This doesn't build on my local machine either - looks like I get a different hash every time I try.

yes it's ALwAYS the same known bug, lot of mirrors just give you an htlm error page. mirror:// syntax is a bad idea for SF, but i never sucess to convinct anyone. I can put a known working mirror  but another maintainer would complain i'm too silly to not have using mirror:// syntax, it happens ...

Thanks for doing this. I'll try and find some time to test and review this
PR soon.
Don't feel you have to stick to sourceforge and/or mirror:// if you think
there's a better way. More generally, feel free to propose any other
changes that would make this derivation easier to work with in future.
For what it's worth, I don't actively track this software for new releases,
or any of the other packages that I'm listed as maintainer on. I do aim to
keep on top of nixpkgs issues and PRs however, so if you want to see the
package updated and/or changed feel free to just open an issue (and tag me
in it so I get an email), rather than feeling that you're forced to do the
legwork yourself.
On Mon, 20 Aug 2018, 00:04 Bignaux Ronan<EMAIL_ADDRESS>wrote:

yes it's ALwAYS the same known bug, lot of mirrors just give you an htlm
error page. mirror:// syntax is a bad idea for SF, but i never sucess to
convinct anyone. I can put a known working mirror but another maintainer
would complain i'm too silly to not have using mirror:// syntax, it happens
...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/45347#issuecomment-414162395, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAznVES52mYpu1Q6t9NzhkVk72_2s1Syks5uSe75gaJpZM4WDErQ
.

you can simply replace mirror by https://versaweb.dl.sourceforge.net . You can also restore a  wrapProgram mecanism to avoid .py suffix as i'd temporary removed that.

This derivation fix non-working desktop file, python 3 and so ...


Solve bug in SpinRanges when indexing a phantom with a BitVector

This worked:
obj.motion = Translate(5e-4, 6e-4, 7e-4, TimeRange(0.0, 1.0), SpinRange(obj.x .> 0))
But this did not work, and it was not tested:
obj = obj[obj.x .> 0]
When executing this second line, the resulting phantom had lost its motion. Two additional method definitions for the intersect_idx function inside SpinSpan.jl can solve this.
I also use this PR to solve a bug in get_spin_coords(m::Motion). I initialized the displacement buffers as follows:
 ux, uy, uz = x .+ 0*t, y .+ 0*t, z .+ 0*t
And this is not correct, since it unnecessarily adds the initial positions to the displacements.
This is how it is solved:
 ux, uy, uz = x .* 0*t, y .* 0*t, z .* 0*t

I believe you can also use similar(a, M, N).
I will wait until the tests pass!

I still see some AMDGPU tests failing

I think it's a random error that has nothing to do with the code.

You are right, I re-run that job, to see if it is fixed.


stack level too deep during test (rails <IP_ADDRESS>, devise 4.2.0)

Hello! When I run this test:
describe 'GET /new' do
    context 'when user not login' do
      it 'redirect to login path' do
        get :new
        expect(response).to redirect_to login_path
      end
    end
end

it crushes with error 'stack level too deep' (loop redirect)
But when I run app in browser it work great!

@mr-koww Could you provide a sample application that reproduces the error?


The implementation of Countable on the CachingIterator is causing the UniqueEntityValidator to always fail

BC Break Report

Q
A

BC Break
yes

Version
2.5.0

Summary
In the 2.5.0 release the CachingIterator was improved to implement the Countable interface. However, the implementation is such that the internal pointer of $this->items will be at the end after counting due to the call to $this->exhaustIterator();. The means that calls to valid will fail after counting.
This is problematic as it's tripping up the UniqueEntityValidator from the Symfony Bridge. See https://github.com/symfony/symfony/blob/6.4/src/Symfony/Bridge/Doctrine/Validator/Constraints/UniqueEntityValidator.php. The check for valid on line 166 will always fail given the count on line 163.
Either there should be a reset after counting or alternatively a bug would have to be submitted to the Symfony project. Given the inbuilt ArrayIterator remains valid after after counting, I'd suggest that counting should leave a valid iterator as valid and the bug is here.
Previous behavior
The CachingIterator worked fine with the UniqueEntityValidator from the Symfony Bridge
Current behavior
The CachingIterator causes the UniqueEntityValidator to always validate without error when there is exactly one existing matching entity.
How to reproduce
use Doctrine\ODM\MongoDB\Iterator\CachingIterator;
use PHPUnit\Framework\TestCase;

class CachingIteratorTest extends TestCase
{
    public function testCountCausesValidToFail(): void
    {
        $iterator = new CachingIterator(new \ArrayIterator([1,2,3]));
        $this->assertTrue($iterator->valid());
        count($iterator);
        $this->assertTrue($iterator->valid());
    }
}

Thanks for the report @jasonw-i6! Adding this to next patch release's backlog.
Ideally we should also add a test to https://github.com/doctrine/DoctrineMongoDBBundle


Icons element in the VAST tester

Hello,
Can you please tell me if the the tool available here: https://vasttester.iabtechlab.com/#/ has Industry Icon Support. If not, do you happen to know where I can test this feature? I tried on all the other VAST testers/validators I found but I can't make the Adchoice icon appear.
https://zutils.zedo.com/vastvalidator/#/vastInspector
https://www.vastinspector.com/
My VAST XML is:
<VAST version="3.0">
    <Ad id="20011">
        <Wrapper>
            <AdSystem version="4.0">iabtechlab</AdSystem>
            <VASTAdTagURI><![CDATA[https://raw.githubusercontent.com/InteractiveAdvertisingBureau/VAST_Samples/master/VAST%203.0%20Samples/Inline_Linear_Tag-test.xml]]></VASTAdTagURI>

            <Error>http://example.com/error</Error>

            <Impression>http://example.com/track/impression</Impression>
            <Creatives>
                <Creative id="5480" sequence="1">
                    <CompanionAds>
                        <Companion id="1232" width="100" height="150" assetWidth="250" assetHeight="200" expandedWidth="350" expandedHeight="250">
                            <StaticResource creativeType="image/png">
                                    <![CDATA[https://www.iab.com/wp-content/uploads/2014/09/iab-tech-lab-6-644x290.png]]>
                            </StaticResource>
                            <CompanionClickThrough>
                                <![CDATA[https://iabtechlab.com]]>
                            </CompanionClickThrough>
                        </Companion>
                    </CompanionAds>
                    <Linear>
                        <Icons>
                          <Icon program="AdChoices" width="50" height="50" xPosition="left" yPosition="top">
                            <StaticResource creativeType="image/png">
                              <![CDATA[https://youradchoices.com/DAA_style/YAC/Icon_White_Box.png]]>
                            </StaticResource>
                          </Icon>
                        </Icons>
                    </Linear>
                </Creative>
            </Creatives>
        </Wrapper>
    </Ad>
</VAST>

Thanks!

Icon support is a to-do, unfortunately. Sorry that the UI does not make that clear!
With Zedo and potentially other testers, I think what you may be experiencing is shortcomings around adding icons via a VAST wrapper. If I dump your <Icons> element into the sample <InLine> directly instead of using a <Wrapper>, Google's Video Suite Inspector does show the icon. With your wrapper code, it doesn't.
I take it you're looking to reliably add an icon via a wrapper tag though? It would definitely be interesting to have a support matrix for this and other features in various players and testers.

Thank you for the answer.
Yes, ideally I would like to add the icon via the wrapper tag. But at least I know now that my request should work with a player that has this feature enabled.


Would you please consider providing another way to use TorchStudio like TensorBoard or Kite?

Hi, guys,
I am wondering whether you would consider providing another way to use TorchStudio like Tensorboard or Kite;
I mean, maybe there could be some python APIs that we could call so as to present the results in the TorchStudio, in which way, we could write codes in PyCharm and use TorchStudio like TensorBoard.
Thanks sincerely for the wonderful features of TorchStudio!
Looking forward to your reply.

Considering it the other way, what features from TensorBoard and PyCharm would you like to see in TorchStudio ?

Hi @divideconcept ! Please give me some time to organize my thoughts.


UI5 Demo Kit: Walkthrough doesn't work with localized i18n files

OpenUI5 version:
"minUI5Version": "1.108.0"
Browser/version (+device/version):
Chrome/119.0.6045.124 Lenono ThinkPad X1/Windows 11/22621.2428
Any other tested browsers/devices(OK/FAIL):
None
URL (minimal example if possible):
https://sdk.openui5.org/topic/df86bfbeab0645e5b764ffa488ed57dc
User/password (if required and possible - do not post any confidential information here):
n/a
Steps to reproduce the problem:

Go through the UI5 Demo Kit walkthrough guide up to and including step 8
Instead of using a generic i18.properties file, use two localized files, e.g. i18n_de.properties and i18n_en.properties with translated texts (as described in the "webapp/i18n/i18n.properties (New)" section).
Start the app

What is the expected result?
Depending on the browser language the respective translated texts should be shown.
What happens instead?
The i18n properties file is not respected at all. The texts shown are the technical fallback texts.

Any other information? (attach screenshot if possible)
When looking at the console in the browser dev tools error messages are shown stating that neither i18n.properties nor i18n_en_US.properties are found. So I tried naming the files i18n_en_US.properties and i18n_de_DE.properties. The error messages about i18n_en_US.properties not found did not appear then, but the app still did not load the texts from the properties file.

Hi @KaiRoesner,
thats interesting. I have downloaded step 8 and placed a new file "i18n_en.properties" in the "webapp/i18n" folder and changed the texts. For me it works as expected. Could you share your project please?

Step 10 of the tutorial uses the supportedLocales setting in the manifest.json. It only contains the empty string (representing the default properties file). If you add more language files, you have to update the list of supported locales. The runtime uses this information from the manifest to avoid useless requests to the server.
This however does not explain the requests for en-US that you saw initially.

Confirmed by @KaiRoesner via email, that changing the supportedLocales from [""] to ["de", "en"] requests correctly the translated files.


Frontend backend separation

⚠ @Nacho114 @dgengler6  this will require your attention in your current PR as it involves changes in pretty much all files again. We should coordinate our efforts in order to minimise the amount of extra work. I already had to basically recode everything I did before the exams because my branch had diverged too much which was super time-consuming. I am sure you do not have the same situation.
Description of the contributions
Modularisation and refactoring of NotFound.vue and the vue files inside the components/upload directory. Indeed they were lacking modularity and the code was hard to read and debug (especially for the upload frames).
This refactoring also allowed me to solve different upload files and testing bugs mentioned in earlier issues.
Standardise  notations in Vue files (following Vue standards)

Uppercase props:
a. Task => task.
b. Id => id.

Reactive hooks:
a.  v-on: becomes @. E.g. v-on:click="() => trainModel(titanic)" becomes  @click="() => trainModel(titanic)".
b.  v-bind: becomes :. E.g. v-bind:task="task" becomes  :task="task".

Restyle diagrams of @Nacho114
The container divs were not properly spaced and did not meet the platform requirements, design-wise.
See the screenshot below for the updated version

Separate front end backend code :
Intro
This PR aims to prepare the way for the introduction of the CLI feature. The only step that will be left to do is to define a separated memory system that works with node.js (i.e. indexedBD is not available).
Implementation details
In order to achieve a complete separation between interface and implementation, we need to define a series of JavaScript classes abstracting the behaviour currently inside the Vue files through a programming interface in the form of methods. These methods will then be called by the Vue component at the appropriate time to respect the specifications of the platform.
To be consistent with the architecture proposed in the earlier modularisation steps, a Trainer and a Tester classes are defined. TrainingFrame component will instantiate Trainer object to handle the training process and similarly for testing. Both Trainer and  Tester are subclasses of an abstract class named  Actor.
To obtain a correct implementation, the Trainer and Tester objects must have access to the processing functions of the tasks they are trained/tested on. Previously, these functions were defined in the corresponding Vue component (e.g. CSVTrainingFrame) and then passed as props to their child TrainingFrame/TestingFrame. This behaviour is not possible anymore since we aim to be separated from the UI. The solution is to define a specific helper per task. In the code, this is referred to as the TaskHelper abstract class. Each subclass must implement the following functions:

dataPreprocessing: wrapper for the underlying task.preprocessing function.
makePredictions:  wrapper for the underlying task.predict function.
`predictionsToCsv: converts the predictions of the machine learning model into a valid CSV format.

The new architecture is summarised in the following figure:

Note: that this particular abstraction will greatly simplify the process of allowing the users of the platform to specify preprocessing JavaScript routines directly via the task creation form and therefore propose new data types.

Last aspects to work on
This is quite a large PR so I thought it would be interesting to give some time to process it and hopefully give me some feedback and/or find bugs.

I already noticed that the training of MNIST has some issues. I don't really know what the problem is yet but I suspect it is again related to the weird relationship between two-way binding for reactivity in Vue and TFLS. I already had a similar problem with the Titanic task and it was not that simple to solve.
I will probably add more documentation into the helpers/task_definition/README.md file to explain what code should be added to create a new Datatype Task.
I think that there could be some confusion related to the use of the task word in the platform. Indeed, it is currently used both for a task such as MNIST (e.g. in the tasks.json file in the server) and a data type like image or csv (e.g. we have task.js and TaskFrame.vue).  I think it would be good to use a clear different terminology because we can have different tasks that have the same underlying task datatype.
The ImageTestingFrame.vue is completely outdated and needs to be refactored (similarly to the containers/upload files).

Thanks for the very well documented PR!
I like the abstraction of the actor, but the name is too general so it's not clear what it does. I read an article not too long ago about this, how names should be succinct but also informative. For instance it's tempting to call something utils or helpers, but it's not clear at all what such a package would do.
Instead of Actor, what about ModelActor? (or if you have another proposal).

Most things seems to be working, currently debugging cifar-10, data loader is not working properly.

Tested feai / deai, everything seems work good now. The separation has the right abstraction.


]ListPackages could act on an install folder as well

Currently ]ListPackages requires a Registry (local or via http[s]) as argument, but it could also act on an install folder.
That makes it easier to check which packages are currently installed in a folder.

Implemented in version 0.61.0


Strange behavior of NeighborSampler

Here is the code that produces result that I don't understand at all:
https://gist.github.com/WeirdKeksButtonK/d6c4436f5fdaa19def5feda346742c16
By the following line:
sampler = NeighborSampler(data, size=1.0, num_hops=1, batch_size=2, bipartite=False)

I mean "Choose two random nodes (batch_size=2), add all their neighbors to the subgraph (by size=1.0 I mean 100%) and stop (num_hops=1)". In other words, I expect subgraph.b_id to equal [0, 1] (because shuffle=False) and subgraph.n_id to equal [0, 1, 2, 3] (because (1, 2) are neighbors of 0 and (2, 3) are neighbors of 1).
However, the result is so far from my expectations that I think I completely misunderstand the algorithm :) What is the correct interpretation of how NeighborSampler works?
torch==1.4.0
torch-cluster==1.5.3
torch-geometric==1.4.3
torch-scatter==2.0.4
torch-sparse==0.6.1
torch-spline-conv==1.2.0
numpy==1.18.1

That looks correct to me. Note that n_id collects all edges that point to these nodes (that is the usual message passing flow). If you want the behaviour you described, pass flow='target_to_source' to the sampler class.

Oh, I see, thank you for the answer!


🐛 Bug Report: Invalid prisma.config.update()

👟 Reproduction steps
Update stack with docker-compose.
👍 Expected behavior
It's work :)
👎 Actual Behavior
Don't start container.
Logs:
Running seed command ts-node prisma/seed/config.seed.ts ...
Environment variables loaded from prisma/.env
Listening on port 3000 url: http://<IP_ADDRESS>:3000
PrismaClientUnknownRequestError:
Invalid prisma.config.update() invocation in
/opt/app/backend/prisma/seed/config.seed.ts:198:27
195     value: existingConfigVariable.value,
196   }) != JSON.stringify(existingConfigVariable)

→ 198   await prisma.config.update(
{
Error occurred during query execution:
ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(SqliteFailure(Error { code: ReadOnly, extended_code: 8 }, Some("attempt to write a readonly database"))), transient: false })
at zr.handleRequestError (/opt/app/backend/node_modules/@prisma/client/runtime/library.js:122:8480)
at zr.handleAndLogRequestError (/opt/app/backend/node_modules/@prisma/client/runtime/library.js:122:7697)
at zr.request (/opt/app/backend/node_modules/@prisma/client/runtime/library.js:122:7307)
at async migrateConfigVariables (/opt/app/backend/prisma/seed/config.seed.ts:198:7) {
clientVersion: '5.0.0'
}
An error occurred while running the seed command:
Error: Command failed with exit code 1: ts-node prisma/seed/config.seed.ts
🌐 Browser
Chrome

Please see the note in the release notes:

⚠ Warning
As the Docker image doesn't use the root user anymore, you might change the data directory permissions.
This can be done with sudo chown -R your-user data

Thanks.
But I have only one user on my VPS: root.
I created a second user, gave him permissions. Everything worked.

Just for the files: pingvin-share uses user id 1000 and group id 1000. So a sudo chown -R 1000:1000 data with data as the data directory will work.
Since uid 1000 and gid 1000 is the default for the first user on most Linux systems, the data directory is owned by that user. Keep this in mind on a multi-user system.


ExpressiveCard is not exported

What package(s) are you using?

[X ] Cloud & Cognitive
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description
I see ExpressiveCard is available in the storybook: https://ibm-cloud-cognitive.netlify.app/?path=/story/cloud-cognitive-canary-cards-expressivecard--clickable
But when I try to use it in the code, it shows this error:
error - ./components/Connect/AddDatasourceTearsheet/AddDatasourceTearsheet.tsx
Attempted import error: 'ExpressiveCard' is not exported from '@carbon/ibm-cloud-cognitive'.
@dcwarwick suggested me to open this bug, so this component will be included in the latest release soon.
Thank you!

@davidmenendez ExpressiveCard and ProductiveCard are in the package-settings.js as public components, but are not currently exported: they need adding to packages/cloud-cognitive/src/components/index.js and _index.scss so they can be used from our published package.
@jinzih Just to note that ExpressiveCard and ProductiveCard have been started, but not yet reviewed and released, so they are in "Canary" state, which means they need explicitly enabling with the feature flag as we discussed earlier, and they are still subject to changes including breaking changes as we review them technically and with the design team. They are on our priority list for review and release, though, so I hope they will move out of Canary status before too long.


Error running twistlock with jaeger-operator:1.17.0

Hi
Having trouble running twistlock with jaeger-operator:1.17.0. This works as expected:
docker pull jaegertracing/jaeger-operator:1.16.0
./twistcli images scan -u scanner -p Jenkins01 --address https:// --vulnerability-threshold critical --details docker.io/jaegertracing/jaeger-operator:1.16.0
but when I try (note the pull) :
docker pull jaegertracing/jaeger-operator:1.17.0
./twistcli images scan -u scanner -p Jenkins01 --address https:// --vulnerability-threshold critical --details docker.io/jaegertracing/jaeger-operator:1.17.0
it errors out:
ERRO 2020-03-16T15:49:51.992 Failed to find packages found errors while searching for rpm packages failed to run command: {rpm [-qal --dbpath var/lib/rpm --queryformat
%!{(MISSING)name}$$%!{(MISSING)version}$$%!{(MISSING)release}$$%!{(MISSING)license}$$%!{(MISSING)installtime}
] /}, out: arguments to --dbpath must begin with '/'
exit status 1
, err:exit status 1
INFO 2020-03-16T15:49:51.992 Searching for special files jaegertracing/jaeger-operator:1.17.0
Anybody have any ideas?

I don't have any experience with twistlock, but I know that we changed the base image between 1.16 (centos) and 1.17 (registry.access.redhat.com/ubi8/ubi). Would you be able to run it against those base images?

@jahlinxjah feel free to reopen once you provide more info. I am closing this for now as we don't have required data to investigate the issue.


Requested changes for September 2018 release.

Removed module maps for CommonCrypto since it is now natively exposed to Swift in Xcode 10.
Replacing flatMap which has been deprecated in some use cases for compactMap.
Fix for intercepting successful issuer add URL in WKWebView.

I updated xcode to version 10. build clean succeeds, but test fails at /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/usr/include/CommonCrypto/module.modulemap:1:8: error: redefinition of module 'CommonCrypto' module CommonCrypto [system] [extern_c] {        ^ Could you take a look?

In my PR, I've removed the module maps for CommonCrypto because it's no longer necessary in Xcode 10 and causes the above redefinition failure. Could you please check that the CI build included my changes?


bug(@vtmn/react): VtmnDropdown onChange is not working

Hi,
It seems that the onChange method for the VtmnDropDown doesn't work at all ?
I've took the original sample from the Decathlon design website and nothing happen when we change the values....
Any ideas ?

Hello @JulienGaudet,
Thanks for your request.
Can you please give us more detail regarding the implementation (React, Svelte or Vue) and version?
For your information, as written in our README, React, Svelte & Vue libraries are maintained by the community as we don't have any budget to maintain them, unfortunately... But we can accompany you in making a Pull Request or connect you with contributors.
Thanks for your help.
https://github.com/Decathlon/vitamin-web/blob/main/CONTRIBUTING.md

Hello @lauthieb,
Of course, we use the package : "@vtmn/react": "0.54.3"
And for the implementation, we've litteraly copy and paste the code from : https://www.decathlon.design/726f8c765/v/0/p/42d824-dropdown/b/28931f
And nothing happen on the onChange method. We've managed to make the component work by using onClick method on each VtmnDropDownItem, but I don't think that is the right way to do it.
I have several components that I could integrate at @vtmn/react such as DatePicker, DateRange, Table...
But unfortunately I do not have the time to add it properly to the package for now. Maybe in a few month when our product will be in a stable version.
Have a nice day :)

Hi @JulienGaudet,
You're right from what I understood the only way to handle onChange events is by passing an onChange handler for each child of VtmnDropdown.
I've made a pull request in order to be able to pass an onChange prop directly in the VtmnDropdown.
Have a nice day :smile:


feat(PDS-58): Headings

Description
Headings components implementation
Issue ticket number and link
Componente Headings
TODO Checklist

[x] Support for Ellipsis

We need to add Apache licenses on each file.


Gear button doesn't work for empty folder

VS Code Insiders:
Windows (but might be problem on macOS as well)

open empty folder in VS Code
switch to debug viewlet
press gear icon

Observe: nothing happens.
This error shows up in the dev console:

Fixed on latest out of source a15c15d958


fix(KFLUXBUGS-1786): git provider of gitlab.cee.redhat.com is gitlab

Fixes
KFLUXBUGS-1786
Description
When people create component and specify the git source as 'https://gitlab.cee.redhat.com/test.git', the git provider should be auto-filled as 'gitlab'.
Type of change

[ ] Feature
[x] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

create component
input the https://gitlab.cee.redhat.com/test.git as the git repo url
click the 'show advanced git' to ensure the 'gitlab' is shown as the git provider annotation.

Browser conformance:

[x] Chrome
[x] Firefox
[ ] Safari
[ ] Edge

FYI, after confirmed with the reporter, it is ok to close the PR directly. Thank you for your attention.

Close it now.


can python-etcd support ectd api v3?

This would be awesome, any plans or updated? Can anyone recommend some mature python etcd client library?

I think it's better to mention it in the documentation. It took me a while to figure out this package doesn't support api v3.

This version of python-etcd will only work correctly with the etcd server version 2.0.x or later. If you are running an older version of etcd, please use python-etcd 0.3.3 or earlier.

found the reason why it doesn't work with etcd-3.4:

Make etcd --enable-v2=false default
etcd --enable-v2=false is now the default.

This client only works with v2 api.


Added Hyva as technology

Hyva has become a well know new front-end of Magento 2, you can find sites using it here: https://hyva.io/showcases
The technology is way different from a normal Magento front-end and Wappalyzer does not always recognize this, for example this is https://www.limburgiavlaai.nl/ :

Thanks!


Fix secret access for some email sending functions

Broken via #418. Omitting these meant that our "market closed" emails and our "thanks for paying us money" emails were not operational.

Np, thanks for fixing!
Seems it might also have prevented people from gaining mana they paid for, if stripeWebhook wasn't running? If so, we would need to transfer those people Manifold Dollars.


Does Python-App SDK for TTN module support HTTP Protocol

Does Python-App SDK for TTN module support HTTP Protocol ?
Currently we are facing issues with MQTT Protocol while accessing TTN servers using TTN python Library
In corporate world due to the security issues they have given us the provision only for HTTP.
Now I would like to know, Does the Python-App SDK support for HTTP protocol also ?

No. The only way to get your data from TTN is to use the MQTT protocol or to use one or more of the available integrations.
Also note that the SDKs are supposed to run on servers (which should have unrestricted access to the internet). Those servers then expose the data to end users (which may be behind a corporate firewall).


M+ fonts bug

M+ Thin font not working anymore!
MacOS Sierra 10.12.5 macbook pro 2013
Atom 1.17.2

Sorry about that, 3.0.1 should fix this

Yes, thank you very much


Update consume-com.md

The example code does not build using the current instructions given. It generates two errors: -
-> C2039:  'get_unknown': is not a member of 'winrt'
-> C3861:  'get_unknown': identifier not found.
I was able to resolve this by adding '#include <Unknwn.h>' to the pch.h file.

@MathewBenson : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@stevewhims : Thanks for your contribution! The author(s) have been notified to review your proposed change.


ModelBuilder being thread safe?

Hello,
This here is not really an issue but more of a question, but since I have not found anything helping on the internet and the mighty search engine of your choice, I wanted to ask that in here.
I know, that per design, EF Core was not meant to be thread safe. I totally get that point of isolation for the DbContext instances, but I was wondering, why also the model building already seems to be impacted by that.
Background
In order to speed up start-up time for an application, I wanted to do 2 queries in parallel, using 2 distinct DbContexts. Basically, each of them reflects a "Bounded Context Database" in my domain, one mapping to environment settings (user settings, stored UI layouts, ...) in the database and one mapping to system settings (system passwords, ...).
So when I fire up the application, I wanted to start two tasks, one going to the environment settings to fetch already the layout stuff and user settings, and one going to the system settings, to check on correct passwords etc.
Problem
Both tasks would create the underlying DbContext on their own, so the DbContext is created at that thread. But somehow, it seems, that the actual model-building under the hood of EF Core is done differently or not "per" thread or "per DbContext".
When I execute my application, from time to time it crashes with the following error:
System.InvalidOperationException: Cannot create a DbSet for 'EvaluationSettings' because this type is not included in the model for the context.

Having a look at my logs however reveals, that the entity was registered at the context previously.

Thread 18 is for the system stuff and registeres SystemInformation and Variable at its context and calls "EnsureCreated"
Thread 16 is for getting culture settings etc and registers Evaluation, EvaluationSettings, ... at the context and calls "EnsureCreated"

Afterwards, thread 16 (getting the system culture from the EvaluationSettings entity) fails.

When I do debug that issue and try to get the insights of the model-builder, I see, that only the Evaluation type is known to the DbContext model builder. The rest somehow is gone.

Question
Could it be, that because 3 threads are calling "EnsureCreated" in parallel, only those entities get a model in the context, which were registered at that point of time?
It seems, that on that level, there is no isolation of "this model belongs to that context", right?
Anybody has a possible solution to that?
Or a suggestion how to solve that?
Version
EF Core 2.2.1

I did ask the question also on SO: https://stackoverflow.com/q/55488880/8504288

@hkoestin Since EnsureCreated is manipulating the database schema, it must not be called concurrently from multiple threads. Even if we did allow two threads to call into it concurrently, this would only work if one of the threads blocks, which is what you are already seeing for model creation. Continuing with the model, it is built once and cached because generally building the model can be slow. By default, models are cached based on the DbContext type, but this can be configured. So you could build two models in parallel if you wanted to. In general this is unlikely to be good for perf.

@ajcvickers thank you for your feedback. I see, that there is no point in seeking for a performance boost in this topic. Will just call the ensure created once. I see, that model building is quite costly and that is the reason why EF tries to cache it etc.
However, the models which needs to be built are very specific to the DbContext, namely only the registered entities in that very DbContext. Why isn't there a mechanism in place, which sort of isolates the models per db-context type? Then, model building (also for huge mappings with tons of entities etc.) can happen on a very small and limited subset (each DbContext). The database facade would need to have a cache in place, which of the models for which DbContext were already build etc.
I tried something different now: one DbContext pointing to SQLite, one pointing to SQL Server. There, building works in parallel. At least, out of maybe 20 runs, I did not see an issue.


[fix](mysql catalog) Fixed exception in dorisTypeToDoris when using MySQL catalog.

When using specific MySQL JDBC packages (such as mysql-connector-java-8.3.0), their CHAR or VARCHAR metadata strings lack the (len) suffix.
Consequently, related queries will result in errors due to attempts at converting CHAR to int.

This pr ensures compatibility with the metadata formats of both CHAR and VARCHAR types by providing the maximum lengths.

run buildall


Add implementation for the CLIENT KILL command

The goal of this PR is to propose an implementation of the CLIENT KILL command
This solution handles all syntax written in the document, the first one using CLIENT KILL IP: port, and the other one using filters, we use type for deducing which one we need to call for handling compatibility with the server on < 2.8.12 version.
If we have only an address, a port, and an optional lamba, we choose the CLIENT KILL IP: port, if we have at least one filter we choose the second one.
Lot of prototypes are implemented, but two are important, the first one with only a variadic template for filters, and the other one with std::string host, int port, ... prototype.
Lot of stuffs are handled in the compile time, for example the solution launch a static_assert if the lambda is not the last argument when we call the function member for keeping a sense with the other function member of the API. Also, if we call the function member using only a lambda, etc...
Also the implementation is create in an another file, because we use template, we don't really want to polluate the header file.
If we send a bool, we check the SKIPME option
if we send an integral, it's the client ID.
if we send a client_kill::type who has several value like normal, master, pubsub and slave correspond to the type of the client.
Here an example of utilisation of client_kill

#include <cpp_redis/cpp_redis>

#include <iostream>
#include <sstream>
#include <string>

int main()
{

  cpp_redis::redis_client client;
  client.connect("localhost", 6379);

   // client kill ip:port
  client.client_list([&client](cpp_redis::reply& reply) {

      std::string addr;
      std::stringstream ss(reply.as_string());

      ss >> addr >> addr;

      std::string host = std::string(addr.begin() + addr.find('=') + 1, addr.begin() + addr.find(':'));
      int port = std::stoi(std::string(addr.begin() + addr.find(':') + 1, addr.end()));

      client.client_kill(host, port, [](cpp_redis::reply& reply) {
          std::cout << reply << std::endl; // OK
      });

      client.commit();
  });

  client.commit();
  std::this_thread::sleep_for(std::chrono::seconds(1));

  if (not client.is_connected()) // in case if the client didn't kill himself during the test
    client.connect("localhost", 6379);

  // client kill filter
  client.client_list([&client](cpp_redis::reply& reply) {

      std::string id_str;
      std::stringstream ss(reply.as_string());

      ss >> id_str;

      uint64_t id = std::stoi(std::string(id_str.begin() + id_str.find('=') + 1, id_str.end()));
      client.client_kill(id, false, cpp_redis::client_kill::type::normal, [](cpp_redis::reply& reply) {
          std::cout << reply << std::endl; // 1
      });

      client.commit();
  });

  client.commit();

  std::this_thread::sleep_for(std::chrono::seconds(1));
  return 0;
}

Hey,
Sorry for the late answer and thanks for the great work!
I just checked on windows and it compiles perfectly fine, Travis is ok and the code is clean, so it's super cool :)
I'll just push a small change on your branch to adjust coding style (run clang-format, adjust the client_kill by removing the inheritance but instead using an ipp file).
I should merge this by tomorrow!
Thanks again :)

Changes are OK, waiting for travis.

Good to go, merging!

This checkin-specifically variadic_template.hpp-breaks compatibility with Visual Studio 2013.


Zowe.org stopped collecting the Google Analytics information

At the 1st of July Google discontinued currently used Universal Analytics in favor of Google Analytics 4. As such there is no data collected for the zowe.org webpage.
The action is needed on the administrator part in the analytics.google.com to migrate to the Google Analytics 4.
The explanation of the procedure is available here: https://support.google.com/analytics/answer/9744165?sjid=13942840066435787662-EU#zippy=%2Cin-this-article

The latest change allowed us again to get at least basic data but we still miss the information about the additional URL pieces such as what release was requested.

The change was made and we collect the basic info again.


Please grant me write access to this repository so I can create release branches -- and then PR to those release branches

Summary
The content below is basically the same as in this AsyncAPI Slack post.
@Pakisan & @derberg : per @fmvilas 's suggestion in the AsyncAPI Slack, I'm formally requesting write permission for this repository so that I can create release branches -- and then issue PRs from my own fork to those release branches.
(If I'm reading the GitHub docs correctly, write permission is required to create branches.)
I'm not looking to code-review until I get more familiar with this code-base. Towards that end, please separately see my PR that makes the two of you CODEOWNERS so that you are the ones who approve of PRs.
Why do I want to create release branches?

I use this plugin heavily at the moment
Understandably, I'd rather run off of a code-reviewed release version than a self-built one
At the moment I need two release branches created so I can roll the revs and submit PRs:

one for IntelliJ IDEA 2022.2.4 -- as @Pakisan said he wanted to tackle that first before going to the 2022.3.x releases
one for IntelliJ IDEA 2022.3.1
...and who knows when IntelliJ IDEA 2023.x will drop
...plus once a PR for IntelliJ IDEA 2022.2.4 is approved, I have waiting this PR for IntelliJ IDEA 2022.3

About me

I've contributed multiple PRs to this plugin, both before and after it became an AsyncAPI-owned repo.
My LinkedIn
My personal Github
My work Github

In summary
Please consider this request to grant me write privileges for this repo so I can take care of rev rolls -- and then all the two of you need to do is review and approve the PRs.
Thank you!

 I know you were looking for help, we shared this "call for help" from official AsyncAPI accounts, and looks like it finally happened. Please have a look and lemme know how I can help.


NPM IP package warning overstates danger

See https://github.com/indutny/node-ip/issues/136#issuecomment-1941462942

You're only vulnerable to anything remotely close to what the advisory talks about if:
You have a vulnerable version of ip in your deps
and you or your dependencies use the isPublic() function
and that function is used to guard something sensitive
and the input you pass to isPublic() is user input
Only then, you have a problem.

I've opened this PR https://github.com/github/advisory-database/pull/3531 to change the advisory to better represent the actual situation.

Looks like this issue was resolved in our community contributions UI, so I'll go ahead and close this issue. Thanks to both of you!


cmd/link: TestBuildForTvOS failing on darwin-amd64-11_0

https://build.golang.org/log/91e8c2d60784a2c561e285e0d3ac9b204be6e8c2:
--- FAIL: TestBuildForTvOS (11.69s)
    link_test.go:312: [/tmp/buildlet/go/bin/go build -buildmode=c-archive -o /tmp/buildlet/tmp/TestBuildForTvOS1814397663/001/lib.a testdata/testBuildFortvOS/lib.go]: exit status 1:
        -buildmode=c-archive not supported on ios/arm64
FAIL
FAIL	cmd/link	24.797s

(attn @golang/ios)

This started failing as of CL 464339 (CC @ianlancetaylor), which marked -buildmode=c-archive as unsupported on ios due to the integration tests for that feature failing when run by cmd/dist.

I do not understand why the test is failing on only darwin-amd64-11_0 and not the other darwin/amd64 builders. @golang/release, is there an intentional difference in this builder as compared with the others?
The test skips itself if xcrun is not found in $PATH — perhaps our setup instructions for the builders are missing some step to include that tool?

From a quick look at https://farmer.golang.org/builders and the BuildConfig entries in x/build/dashboard, the only intentional and documented difference between darwin-amd64-11_0 and other darwin/amd64 builders is its macOS version. All other differences are incidental.
xcrun seems to be present on darwin-amd64-11_0 and darwin-amd64-12_0 that I quickly tried, but it's likely the problem is along those lines.

This test was originally added in CL 168321 for #22395.
It appears that ios support was explicitly maintained in carchive_test.go at some point, because skips were added for #13701, #19320, #31722, and #33384. So I think the intent is for the buildmode to be supported on this platform; it's a shame that the integration test failures were masked by the cmd/dist bug for so long. 😞

xcrun seems to be present

There is a subsequent check for an appletvos SDK specifically — maybe that's the difference?
(https://cs.opensource.google/go/go/+/master:src/cmd/link/link_test.go;l=285-288;drc=4f467f10820e78add23bf5ddeb1de521aa6f8864)

The test is once again passing on darwin-amd64-11_0. I've filed #58231 to follow up on the builder configuration issue separately.


Razor _Layout support?

Hello!
I'm guessing in the examples but I did not find anything referring to navigation and layout reuse as the first Blazor prototypes did. Do we have support for these features in this release?

These are tracked as #2 and #3.


Multi-select Delete doesn't work

Date - 12/3/19
Steps:

Go to any Resource page (Service, router, etc...)
Check the checkbox to select all resources on that page (Make sure there is more than one selected)
Click on Delete button

Results:  Nothing happens.  A confirmation with the resource names in a list should show up.

Date - 12/5
Verified fixed


Adding a second layer from the new editor uses first layer columns for interactivity

If I enter the new editor with a map that has a single dataset layer with table cities_subset(and base map), then, from the new editor add a layer with other table educacion, an error occurs when instantiating the map, because the second table is using the first table's columns for interactivity.
Here's the (abbreviated) MapConfig that the editor tries to instantiate:
{
  "layers": [
    {
      "type": "cartodb",
      "options": {
        "cartocss": "...",
        "cartocss_version": "2.1.1",
        "interactivity": [ "cartodb_id", "_feature_count", "iso2", "name", "population" ],
        "sql": "select * from cities_subset"
      }
    },
    {
      "type": "cartodb",
      "options": {
        "cartocss": "...",
        "cartocss_version": "2.1.0",
        "interactivity": [ "cartodb_id", "_feature_count", "iso2", "name", "population" ],
        "sql": "SELECT * FROM educacion"
      }
    }
  ],
  "dataviews": { },
  "analyses": [ ]
}

Notice the interactivity columns are the same for both maps (and are those of cities_subset.

I feel this doesn't happen anymore, does it @alonsogarciapablo?

I don't think so. I'm closing it. Let's reopen it if we encounter this again.


Add warning/exit for Az.Resources 5.3.0 service principal provisioning error

Az Resources graph-related calls broken yet again...

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


Stepped Tracker v1

### Checklist
- [ ] Density (HD, MD, LD, TD)
- [ ] Mode (Light, Dark)
- [ ] Fill (Primary, Secondary, Tertiary)
- [ ] State (Default, Hover, Selected/Active, Disabled, Read-only, Other)
- [ ] Controlled API
- [ ] UITK accessibility parity (screen reader + keyboard interactions)

### Deliverables
- [x] Characteristics spec
- [x] Interactions spec, where necessary
- [ ] In Code & Figma (Component + Guide)
- [ ] Supporting site documentation

### Features
- [ ] Horizontal oreintation
- [ ] Basic stepped tracker (Default, In progress, Complete)
- [ ] Label truncation + tooltip support

Dependency:

Color update requires basic validation
Progress Indicators

June 30 - kick off 6/30

@joshwooding @bhoppers2008 @ivan-calderon
Could I get clarification on something. Is it possible to move onto a step without the previous one being completed. E.g. something like: (complete, incomplete, active, incomplete)?
✓-----ο-----●-----ο
I could see this being useful if some steps are skippable, or if you're able to fill out the steps out of order, but I couldn't see this behaviour in the UITK examples

@joshwooding @bhoppers2008 @ivan-calderon
Could I get clarification on something. Is it possible to move onto a step without the previous one being completed. E.g. something like: (complete, incomplete, active, incomplete)?
✓-----ο-----●-----ο
I could see this being useful if some steps are skippable, or if you're able to fill out the steps out of order, but I couldn't see this behaviour in the UITK examples

@el-dav would suggest pushing to a later version... my rationale is that navigating forward and backward through non-consecutive steps is probably something worth supporting but will require extra work (both dev and design). I'd opt to keep as a strict linear flow for the time being and enhance it with non-consecutive navigation at a later date.

For me I'd ideally want it to be considered earlier as currently the UITK implementation can be a bit confusing.
For example:
<SteppedTracker activeStep={2}>
  <TrackerStep completed={false} />
  <TrackerStep  />
  <TrackerStep  />
</SteppedTracker

Shows: ✓-----✓-----●
Also...
<SteppedTracker activeStep={0}>
  <TrackerStep />
  <TrackerStep />
  <TrackerStep  completed={true} />
</SteppedTracker

does show: ●-----ο-----✓ but the lines are dotted rather than bold

@joshwooding @bhoppers2008 @ivan-calderon
Could I get clarification on something. Is it possible to move onto a step without the previous one being completed. E.g. something like: (complete, incomplete, active, incomplete)?
✓-----ο-----●-----ο
I could see this being useful if some steps are skippable, or if you're able to fill out the steps out of order, but I couldn't see this behaviour in the UITK examples

NP, I can take that into consideration and explore this further. Paul and Nav did a great job creating indication pattern icons; and that can be useful in this case. However, I don't see that implemented on V1 because that will require a deeper analysis on: the characteristics, what tokens to apply, what tokens are missing, if current indication icons fulfill this component's needs, potential effects on behavior and interactions (clickable elements, keyboard navigation, accessibility consideration for inactive steps), and few other things. So the initial construction will be linear I guess.

@el-dav is it likely to affect the api now? In that case, it would be worth agreeing the user stories (ie., what would the interaction requirement be) to limit breaking changes in the future. But otherwise I agree with Ivan. v1 should be the most basic reasonable implementation that we can release and get feedback on.

@bhoppers2008 It could affect the API.
For example:

If a step is only complete or not we might have a prop called completed which could be true or false
If however we might have more states e.g. default, started, completed then we'd probably instead have a prop called state which could take three values of default, started or completed.

It's also possible that even if we don't need to update the API, the behaviour of the component could change which i would regard as a breaking change. E.g. if:
<SteppedTracker activeStep={2}>
  <TrackerStep completed={false} />
  <TrackerStep  />
  <TrackerStep  />
</SteppedTracker>

went from ✓-----✓-----● to  ◐-----✓-----●

@bhoppers2008 It could affect the API.
For example:

If a step is only complete or not we might have a prop called completed which could be true or false
If however we might have more states e.g. default, started, completed then we'd probably instead have a prop called state which could take three values of default, started or completed.

It's also possible that even if we don't need to update the API, the behaviour of the component could change which i would regard as a breaking change. E.g. if:
<SteppedTracker activeStep={2}>
  <TrackerStep completed={false} />
  <TrackerStep  />
  <TrackerStep  />
</SteppedTracker>

went from ✓-----✓-----● to ◐-----✓-----●

If it's going to impact the build now, then write out the stories with @ivan-calderon to future proof for coming versions. Those stories can then be the requirements to spec out when we get to that version. It's not a feature we need to build out now though.

@joshwooding

July 14 - review PR comments and address accordingly

21/07 - review comments addressed, ready for re-review. design to review changes to spacing. Ivan to create Figma guidance. will send to content to review

12/07 - PR has been approved by dev and design and merged

July 24

Characteristics for V1 are complete (I'll be cleaning up the file)
Component's Figma branches (Light and Dark) are WIP
Component Figma guide is WIP
The goal is to have all the above completed today and ready for a final review.
Dev complete - in labs
Component doc with content for review

Note: Potential changes in the component design (alignment) shouldn't impact V1. For now, research scoping doesn't include those proposed changes. So, that won't affect the current design

Stepped tracker design files for reference:

Stepped tracker specs (I've cleaned the file)
LIGHT stepped tracker
DARK stepped tracker libraries
Stepped tracker Figma guide

July 25 - Dev: PR has been approved so should be merged imminently (re:remove some functionality from UITK); designs awaiting final review/approval from Ben today

Design review complete... component and guide looks good but we should hide the features that aren't v1 for the time being as MCP at interested in the component and it should reflect what's in prod. Other than that, the component and guide are good to merge.
A couple of questions raised for a new issue/ subsequent release:

Is step-active ok rather than in-progress for current step ( @ivan-calderon to check with Tara).
Should we use 'to-do' icon for steps that aren't started?
Should 'draft' icon be reserved for steps that aren't complete but have been passed and should it be --status-info-foreground (as the pattern)?

Released to labs.
Several queries around behaviour currently being looked at.

to catch up on docs e/ @james-nash @ivan-calderon @el-dav re template.

August 2 - released in labs; storybook docs complete; mdx to be filed with relevant examples during component docs sprint week

Figma component and guide published internally and externally.


[DropdownMenu] no way to "flip" content instead of shifting in v1.0.0

Bug report
Current Behavior
I'm in the process of upgrading to dropdown-menu to 1.0.0 and noticed a small change in behaviour.
On version 0.1.6 it used to switch 'align' when collision was there but now it just moves moves content slightly along the axis.
Is there a way to switch to previous behaviour?
On attached screenshots you can see that data-aligned was changed to 'end' when collision occurs but 1.0.0 keeps 'start'
0.1.6

1.0.0

Expected behavior
I'd like to have a way to disable shifting content and prefer Flip when collision occurs
Reproducible example
CodeSandbox Template
Suggested solution

Introduce a new prop to control it?
Maybe avoidCollisions can be converted to enum, e.g. avoidCollisionsMode: 'off' | 'flip' | 'shift' | 'auto'
Additional context
The issue is based on discussions:
https://discord.com/channels/752614004387610674/803656530259738674/1001062835306119218
https://discord.com/channels/752614004387610674/803656530259738674/1001064659119509545
Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-dropdown-menu
1.0.0

React
n/a
16.14

Browser
Brave
Version 1.40.113 Chromium: 103.0.5060.114 (Official Build) (x86_64)

Assistive tech

Node
n/a

npm/yarn

Operating System
MacOs
12.4

@benoitgrelard This came up in Discord and I was re-examining our decision to always Shift along one axis, it makes sense for ContextMenu but I can see the argument for having it on DropdownMenu in some situations.

It seems potentially we need to give more flexibility/access to the underlying floating-ui configuration.

Yeah, it would be great if we could opt into flip semantics for any component that uses react-popper internally (instead of shift).

Got into another use-case in which I want to shift dropdown content along side axis instead of flipping.
So the problem occurs when the dropdown content can't fit on any side. It just stays at the default side and it's impossible to reach to items that are off-screen.
Would be nice if dropdown could switch to 'shift' mode an try to fit itself on screen. Even if it moves above he trigger it's still better than invisible items, imo

Hey @MikeYermolayev yes, this is a different issue than shifting, rather an issue of size constraining.
As you have discovered, this is something we have implemented already but just haven't released.
In the meantime you can rely on the equivalent "private" popper variable if you want, and if you promise to update it later to use the dropdown menu one once we release 😉

Yep, I upgraded to release candidate instead 😅
Works good so far 👍🏻

Yep, I upgraded to release candidate instead 😅

Or that! 🙂

Works good so far 👍🏻

🎉

If I'm reading correctly, @MikeYermolayev 's sizing issue is handled (and is released now, I believe?) but as far as I can tell, there still isn't a solution for extending control of avoidCollisions (e.g. 'off' | 'flip' | 'shift' | 'auto' as OP suggested)
I found a number of issues (many closed) related to this, but I also don't see any active branches or PRs to address this -- am I missing something? Or is this still an outstanding issue?

@akattow yep, that's right. It's not possible to control how collisions should be avoided

@MikeYermolayev yes, I know, but I'm wondering if that is still something that is under consideration or active development? It's been brought up in multiple issues

@benoitgrelard just to make sure I'm not missing anything here: what if there simply isn't enough space in the viewport to show the full dropdown menu?
Is it possible to have the dropdown resize when meeting the edge of the viewport, similarly to this example from floating UI ? That would allow to show scrollbars internally to the dropdown, so that all items can be accessed

@ciampo https://www.radix-ui.com/docs/primitives/components/dropdown-menu#constrain-the-contentsub-content-size


Add demo for ConstraintLayout feature for chains with margins

Margins and chains (in 1.1)
When using margins on elements in a chain, the margins are additive.
For example, on a horizontal chain, if one element defines a right margin of 10dp and the next element defines a left margin of 5dp, the resulting margin between those two elements is 15dp.
An item plus its margins are considered together when calculating leftover space used by chains to position items. The leftover space does not contain the margins.

A basic feature, not required or could be combined with an existing screen.


Limit 'from' length to 64 chars to ensure conformity with the Hipchat API

@fabxc : 'from' can be longer than 64 chars which results in a bad request to the Hipchat API and a dropped notification. This change is supposed to cap the length of 'from' to ensure that the alertmanager never sends something that is too long and does not comply with the API.
Still very new to go so if there is a way to solve this better I'm happy to look into it. :)

Good catch.
As @brian-brazil said a function would be nice. It could then also truncate with a ... suffix so it doesn't look like some sort of bug to the user.

Superseded by #449


Location of Listener class so it will listen forever

I'd like to use this gem to handle PG NOTIFYs from another project's db. Seems like an ideal use case. However, I don't understand where I should run the Listener class so it will run forever in my Rails project.
If I run it on demand, with a timeout, it defeats the purpose of "listening" to the PostgreSQL DB's notifys.
I'm using Puma, which is multithreaded so should I just place the Listener Class in an initializer and it will block a single worker? Should I use sidekiq instead?
Thanks in advance on any clarity you can provide.

That's a good question. I've only ever used this as part of a separate, long-running process that would run alongside your web process and worker for sidekiq, etc.
For example this gem contains a rake task to run a separate process that will listen to a PG table and enqueue jobs to Sidekiq https://github.com/ezcater/sidekiq_publisher/blob/master/lib/sidekiq_publisher/runner.rb#L19-L28.
It may be possible for you to run the Listener in a Thread in one of your existing processes so that it does not block, but I have not attempted this. If you went with this approach you'd have to consider error handling to ensure that the Listener keeps running and that errors from it do not take down the process.


Request — Open automatically?

Is it possible if openings links could be opened automatically?

I'd love to be able to do this, although it may have to be built directly into Figma. I'll try and do some research though on if I can detect a url on-click vs checking the clipboard.

Josh, it's you!! 😆 Awesome no worries man. This is super helpful already. Thanks!

We now have this as native functionality within Figma.
https://www.figma.com/blog/figma-desktop-app-improvements/

We now have this as native functionality within Figma.
https://www.figma.com/blog/figma-desktop-app-improvements/


Update/Add Haskell compilers on virtual runner

Tool information

Tool name: ghc & cabal
Add or update? update
Desired version: ghc-8.10.4, ghc-9.0.1, cabal-<IP_ADDRESS>
Approximate size: ~200MB
Area for Triage:
Haskell

Question, Bug, or Feature?:
Feature, using newest version of compiler and build tool
Virtual environments affected

[X] Ubuntu 16.04
[X] Ubuntu 18.04
[X] Ubuntu 20.04
[X] macOS 10.15
[X] macOS 11.0
[X] Windows Server 2016 R2
[X] Windows Server 2019

Can this tool be installed during the build?
Yes
Tool installation time in runtime
Seconds
Are you willing to submit a PR?
Yes, but not sure how.

Hi @recursion-ninja!
We install cabal and 2-3 latest Haskell versions through ghcup installer. These particular versions will be deployed next week. The recommended way is to install a specific Haskell version is via https://github.com/actions/setup-haskell action.
I'm going to close the issue, but feel free to contact us if you have any concerns.
Thank you!


Question: Does the log.options work for concurrent requests

I'm a bit confused of how setting invocation specific data to the global log.options works. Let's consider the following case:

Request 1 (R1) comes in
R1 sets the global log.options.meta.event = event; (event is specific to R1)
R1 makes some async call and control is given to event loop
Request 2 (R2) comes in
R2 sets the global log.options.meta.event = event; (here event is specific to R2)
R2 makes async call and control is given to event loop
R1 resumes to execution and makes a log.info('R1')call
--> The log row contains log message 'R1' but the meta.event is from R2 ?

Have I understood this correctly? To me it seems that we just cannot use global instance to set request specific stuff. Instead, we should create an own instance of logger for each request and pass the logger as function argument downstream.
EDIT: This case assumes that the same NodeJS instance is used to serve multiple requests. AFAIK this is how Lambda (and also e.g. Azure functions) works. If we had completely separate NodeJS instances for each call, we'd not have this problem.

@ronkot What you have provided is correct in terms of how the global options would work although that wouldn't be the way you'd want to set metadata for a single log message. Each of the log methods has the ability to take in metadata to include with the log message. For example:
log.info('R1', { event });

The global options should be used to set values that do not change. You can set data within log.options.meta and that will be merged with any metadata that was to be passed in via a log method.

Ah, I understand. Thanks for clarification :) I just got baffled when read the first code example in README.