Update instructions to say Python 3.9

As per https://github.com/hifi/heisenbridge/blob/9cbb062/.github/workflows/build-and-test.yml#L14.

Thanks!


Update build-a-logs-data-source-plugin.md

The changes are the same as in approved and merged https://github.com/grafana/grafana/pull/74752

The formatting issues that this PR was intended to fix apparently only appear in Hugo not in this Docusaurus site. Closing.


Add PublicLab.org to listOfProjects.js

Now with capitalized letters.

ok. Thanks.

Awesome sorry I got bogged down - much appreciated!


🔀 :: develop 병합

Codecov Report

Merging #121 (c5af2eb) into main (071ad30) will decrease coverage by 9.03%.
The diff coverage is 8.16%.

@@             Coverage Diff              @@
##               main     #121      +/-   ##
============================================
- Coverage     47.00%   37.96%   -9.04%
- Complexity       83       84       +1
============================================
  Files            42       52      +10
  Lines           417      540     +123
  Branches         18       24       +6
============================================
+ Hits            196      205       +9
- Misses          210      325     +115
+ Partials         11       10       -1

Impacted Files
Coverage Δ

...semicolon/gspass/controller/TeacherController.java
0.00% <0.00%> (ø)

...om/semicolon/gspass/controller/UserController.java
0.00% <0.00%> (ø)

...n/java/com/semicolon/gspass/dto/TokenResponse.java
25.00% <ø> (ø)

...om/semicolon/gspass/dto/school/SchoolResponse.java
16.66% <0.00%> (-3.34%)
:arrow_down:

...com/semicolon/gspass/dto/teacher/GradeRequest.java
0.00% <0.00%> (ø)

.../semicolon/gspass/dto/teacher/PassTimeRequest.java
0.00% <0.00%> (ø)

.../gspass/dto/teacher/SchoolInformationResponse.java
0.00% <0.00%> (ø)

...colon/gspass/dto/user/UserInformationResponse.java
0.00% <0.00%> (ø)

...semicolon/gspass/dto/user/UserRegisterRequest.java
85.71% <ø> (-1.79%)
:arrow_down:

.../java/com/semicolon/gspass/entity/grade/Grade.java
0.00% <0.00%> (ø)

... and 29 more

Continue to review full report at Codecov.

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


Set KV Cache update as static method

This solves torch compile issue related to using self argument in HQT patched module

https://github.com/huggingface/optimum-habana/pull/1160


Workers and Resources: Soviet Republic is out of early access

Since 21 Jun, 2024

@arcataroger friendly bump :)

@EmilOJ Thanks so much for the bump! I totally missed this, sorry :)


Helix.Helix version 23.03

[ x ] Have you signed the Contributor License Agreement?
[ x ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ x ] This PR only modifies one (1) manifest
[ x ] Have you validated your manifest locally with winget validate --manifest <path>?
[ x ] Have you tested your manifest locally with winget install --manifest <path>?
[ x ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

@wingetbot waivers Add Validation-Executable-Error

I'm not able to find the cause for this error. It installs and runs normally on a Windows 11 VM.

Note for future reference: this package accepts commands in a way similar to VI, and the exit command is a similar :q! - be sure to press the Esc key to exit insert mode beforehand.

Automatic Validation failed with:

Standard error:  Exception during executable launch operation System.AggregateException: One or more errors occurred. (The specified executable is not a valid application for this OS platform.)  ---> System.ComponentModel.Win32Exception (216): The specified executable is not a valid application for this OS platform. --- End of stack trace from previous location where exception was thrown ---    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

So the x86 version should probably be removed.

I will make a new pull request without x86 version.


WRP-4568 : Do not allow NaN to enter the parameters of the css calc()

Checklist

[x] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[x] At least one test case is included for this feature or bug fix
[x] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Css Nan value is changed in calc function after chromium 99.
It caused the scroller thumb style to break.
(--scrollbar-thumb-progress value is  (1-1) *NaN)
Resolution

Check if the denominator is zero to prevent NaN from entering the --scrollbar-thumb-progress calculation.
Add a css variable to check if scroll is valid

Additional Considerations
Links
http://clm.lge.com/issue/browse/WRP-4568
Comments
Enact-DCO-1.0-Signed-off-by: SJ RO<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: sjro:white_check_mark: alexandrumorariu:x: enact-adminYou have signed the CLA already but the status is still pending? Let us recheck it.


Segmentation fault with FSS

Hi,
I have got couple of crashes with fss (one in worker and another in combiner).
Thanks,
Venu

@venu we actually recently fixed an issue with FSS functionality, and this is likely the same issue that has been fixed in master. We haven't published that fix in a new official release but we will today. That should fix your issue here.
I'll report back here once we've published a new official release.

@derekjn thats a great news, will wait for the release! +1

@venu we just published 0.9.8u3:
I'll leave this open for a while so you can verify that the release update indeed fixes the issue. Please let us know here, thanks!

Thank you so much for the quick release.
Looks like it's working fine now, I will get back to you, if its comes back again.

@venu great, thanks for reporting!


Release v1.0.0

Coverage remained the same at 100.0% when pulling 5a8781e3fa878a134a774f3a9e9951b1634f4d0e on SijmenHuizenga:release-1.0.0 into 6f28821135d49cfc7a04aa4d938c51794a4e2401 on dbader:master.

Coverage remained the same at 100.0% when pulling 5a8781e3fa878a134a774f3a9e9951b1634f4d0e on SijmenHuizenga:release-1.0.0 into 6f28821135d49cfc7a04aa4d938c51794a4e2401 on dbader:master.


Docker container high ram usage

Docker Container High RAM Usage
Issue Description
The current Docker container is exhibiting high RAM usage, consuming 8GB of RAM upon a clean start.
559a56af7ba4   linkding   0.01%     8.108GiB / 62.72GiB   12.93%    1.99kB / 0B   827kB / 0B   8

linkding  | Operations to perform:
linkding  |   Apply all migrations: admin, auth, authtoken, background_task, bookmarks, contenttypes, sessions
linkding  | Running migrations:
linkding  |   Applying contenttypes.0001_initial... OK
linkding  |   Applying auth.0001_initial... OK
linkding  |   Applying admin.0001_initial... OK
linkding  |   Applying admin.0002_logentry_remove_auto_add... OK
linkding  |   Applying admin.0003_logentry_add_action_flag_choices... OK
linkding  |   Applying contenttypes.0002_remove_content_type_name... OK
linkding  |   Applying auth.0002_alter_permission_name_max_length... OK
linkding  |   Applying auth.0003_alter_user_email_max_length... OK
linkding  |   Applying auth.0004_alter_user_username_opts... OK
linkding  |   Applying auth.0005_alter_user_last_login_null... OK
linkding  |   Applying auth.0006_require_contenttypes_0002... OK
linkding  |   Applying auth.0007_alter_validators_add_error_messages... OK
linkding  |   Applying auth.0008_alter_user_username_max_length... OK
linkding  |   Applying auth.0009_alter_user_last_name_max_length... OK
linkding  |   Applying auth.0010_alter_group_name_max_length... OK
linkding  |   Applying auth.0011_update_proxy_permissions... OK
linkding  |   Applying auth.0012_alter_user_first_name_max_length... OK
linkding  |   Applying authtoken.0001_initial... OK
linkding  |   Applying authtoken.0002_auto_20160226_1747... OK
linkding  |   Applying authtoken.0003_tokenproxy... OK
linkding  |   Applying background_task.0001_initial... OK
linkding  |   Applying background_task.0002_auto_20170927_1109... OK
linkding  |   Applying background_task.0003_auto_20210410_1529... OK
linkding  |   Applying background_task.0004_auto_20220202_1721... OK
linkding  |   Applying bookmarks.0001_initial... OK
linkding  |   Applying bookmarks.0002_auto_20190629_2303... OK
linkding  |   Applying bookmarks.0003_auto_20200913_0656... OK
linkding  |   Applying bookmarks.0004_auto_20200926_1028... OK
linkding  |   Applying bookmarks.0005_auto_20210103_1212... OK
linkding  |   Applying bookmarks.0006_bookmark_is_archived... OK
linkding  |   Applying bookmarks.0007_userprofile... OK
linkding  |   Applying bookmarks.0008_userprofile_bookmark_date_display... OK
linkding  |   Applying bookmarks.0009_bookmark_web_archive_snapshot_url... OK
linkding  |   Applying bookmarks.0010_userprofile_bookmark_link_target... OK
linkding  |   Applying bookmarks.0011_userprofile_web_archive_integration... OK
linkding  |   Applying bookmarks.0012_toast... OK
linkding  |   Applying bookmarks.0013_web_archive_optin_toast... OK
linkding  |   Applying bookmarks.0014_alter_bookmark_unread... OK
linkding  |   Applying bookmarks.0015_feedtoken... OK
linkding  |   Applying bookmarks.0016_bookmark_shared... OK
linkding  |   Applying bookmarks.0017_userprofile_enable_sharing... OK
linkding  |   Applying bookmarks.0018_bookmark_favicon_file... OK
linkding  |   Applying bookmarks.0019_userprofile_enable_favicons... OK
linkding  |   Applying bookmarks.0020_userprofile_tag_search... OK
linkding  |   Applying bookmarks.0021_userprofile_display_url... OK
linkding  |   Applying bookmarks.0022_bookmark_notes... OK
linkding  |   Applying bookmarks.0023_userprofile_permanent_notes... OK
linkding  |   Applying sessions.0001_initial... OK
linkding  | 2023-12-15 11:04:55,160 INFO Current journal mode: delete
linkding  | 2023-12-15 11:04:55,163 INFO Switched to WAL journal mode
linkding  | There is already a secret key in `secretkey.txt`
linkding  | 2023-12-15 11:04:55,856 INFO Skip creating initial superuser, LD_SUPERUSER_NAME option is not defined
linkding  | [uWSGI] getting INI configuration from uwsgi.ini
linkding  | [uwsgi-static] added mapping for /static => static
linkding  | [uwsgi-static] added mapping for /static => data/favicons
linkding  | *** Starting uWSGI 2.0.20 (64bit) on [Fri Dec 15 13:04:55 2023] ***
linkding  | compiled with version: 8.3.0 on 29 July 2023 09:26:19
linkding  | os: Linux-6.6.7-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 14 Dec 2023 03:45:20 +0000
linkding  | nodename: 559a56af7ba4
linkding  | machine: x86_64
linkding  | clock source: unix
linkding  | detected number of CPU cores: 12
linkding  | current working directory: /etc/linkding
linkding  | writing pidfile to /tmp/linkding.pid
linkding  | detected binary path: /opt/venv/bin/uwsgi
linkding  | !!! no internal routing support, rebuild with pcre support !!!
linkding  | setgid() to 33
linkding  | setuid() to 33
linkding  | your memory page size is 4096 bytes
linkding  | detected max file descriptor number:<PHONE_NUMBER>
linkding  | building mime-types dictionary from file /etc/mime.types...565 entry found
linkding  | lock engine: pthread robust mutexes
linkding  | thunder lock: disabled (you can enable it with --thunder-lock)
linkding  | uWSGI http bound on :9090 fd 4
linkding  | uwsgi socket 0 bound to TCP address <IP_ADDRESS>:39617 (port auto-assigned) fd 3
linkding  | Python version: 3.10.6 (main, Aug 23 2022, 08:58:52) [GCC 8.3.0]
linkding  | Python main interpreter initialized at 0x557505fb6a00
linkding  | python threads support enabled
linkding  | your server socket listen backlog is limited to 100 connections
linkding  | your mercy for graceful operations on workers is 60 seconds
linkding  | mapped 274608 bytes (268 KB) for 4 cores
linkding  | *** Operational MODE: preforking+threaded ***
linkding  | WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x557505fb6a00 pid: 1 (default app)
linkding  | *** uWSGI is running in multiple interpreter mode ***
linkding  | spawned uWSGI master process (pid: 1)
linkding  | spawned uWSGI worker 1 (pid: 16, cores: 2)
linkding  | spawned uWSGI worker 2 (pid: 18, cores: 2)
linkding  | *** Stats server enabled on <IP_ADDRESS>:9191 fd: 14 ***
linkding  | spawned uWSGI http 1 (pid: 20)

@GreatVoid29A I'm also having problems in my rasbperry pi 4 model b with 8gb of ram:
malloc(): Out of memory [core/utils.c line 1801]
!!! tried memory allocation of<PHONE_NUMBER> bytes !!!
respawned uWSGI http 1 (pid: 353)

in my case linkding never goes up, the container is kept into a zombie state.
@sissbruecker any idea?
thanks a lot and have a nice weekend!

This is a dupe of https://github.com/sissbruecker/linkding/issues/453, check the thread there for a workaround.


[.NET] Update dependency libraries

Package needs to have the following dependencies updated from 5.0.0 to 6.0.x

Microsoft.Extensions.Caching.Memory
System.Collections.Immutable

Thanks for the suggestion. But this is currently on hold as it is a breaking change.


[MI-2177][Documentation]: Updated readme files

Updated readme files

@ayusht2810 no need to review both the developer doc and main readme files as the same changes of the main readme file is copied in the developer doc


Duplicate cheatsheets while autocompleting at $HOME

Thanks for submitting a bug report. Please provide the following information:
A description of the problem
I have a symlink ($HOME/.cheat) to another folder containing cheatsheets ($HOME/user/git/dotfiles/.cheat). If I press tab twice to autocomplete while I'm at $HOME, lots of cheatsheets are duplicated. This does not happen in other directories.
Autocomple at $HOME:

Autocomplete in other directories:

I'm using the completion script with oh-my-zsh, all components are the last available here at the repository.
cheat version info
4.2.0
cheat configuration info

The output of cheat -d
Community: /home/user/git/dotfiles/.cheat/community
Work:      /home/user/git/dotfiles/.cheat/work
Personal:  /home/user/git/dotfiles/.cheat/personal

The contents of your conf.yml file

# The editor to use with 'cheat -e <sheet>'. Defaults to $EDITOR or $VISUAL.
editor: nvim

# Should 'cheat' always colorize output?
colorize: true

# Which 'chroma' colorscheme should be applied to the output?
# Options are available here:
#   https://github.com/alecthomas/chroma/tree/master/styles
style: monokai

# Which 'chroma' "formatter" should be applied?
# One of: "terminal", "terminal256", "terminal16m"
formatter: terminal16m

# The paths at which cheatsheets are available. Tags associated with a cheatpath
# are automatically attached to all cheatsheets residing on that path.
#
# Whenever cheatsheets share the same title (like 'tar'), the most local
# cheatsheets (those which come later in this file) take precedent over the
# less local sheets. This allows you to create your own "overides" for
# "upstream" cheatsheets.
#
# But what if you want to view the "upstream" cheatsheets instead of your own?
# Cheatsheets may be filtered via 'cheat -f <tag>' in combination with other
# commands. So, if you want to view the 'tar' cheatsheet that is tagged as
# 'community' rather than your own, you can use: cheat tar -f community
cheatpaths:

  # Paths that come earlier are considered to be the most "global", and will
  # thus be overridden by more local cheatsheets. That being the case, you
  # should probably list community cheatsheets first.
  #
  # Note that the paths and tags listed below are just examples. You may freely
  # change them to suit your needs.
  - name: Community
    path: ~/.cheat/community
    tags: [ community ]
    readonly: true

  # Maybe your company or department maintains a repository of cheatsheets as
  # well. It's probably sensible to list those second.
  - name: Work
    path: ~/.cheat/work
    tags: [ work ]
    readonly: false

  # If you have personalized cheatsheets, list them last. They will take
  # precedence over the more global cheatsheets.
  - name: Personal
    path: ~/.cheat/personal
    tags: [ personal ]
    readonly: false

OK, I just saw this in the README:
Directory-scoped Cheatpaths

At times, it can be useful to closely associate cheatsheets with a directory on your filesystem. cheat facilitates this by searching for a .cheat folder in the current working directory. If found, the .cheat directory will (temporarily) be added to the cheatpaths.

So changing the symbolic link to .cheats instead of .cheat and chaning the config accordingly fixes this. My bad!
I'm closing the issue now. Thank you anyway!!

Aha. Yeah, you're not the first user to get tripped up by this, unfortunately. I should probably improve the visibility of this feature, given that it can be a "gotcha" otherwise.
I'm glad you were able to work this out. Thanks for the detailed bug report!


Updated package-lock.json with official mirrors

Currently, the package-lock contains a dead mirror making booting up the tool impossible.
I have regenerated the lockfile to include the official mirror (registry.npmjs.org) so the start script works properly again

Thank you! Must've been from that one time I used a different computer 😅


Fix issue with longer post counts getting truncated

Before:

After:

Tried it with longer content too

@ehmadzubair please review

:+1:


Update gem dependencies

Summary
This PR updates faker gem dependencies.

Unfortunately you're trying to update the Fakerbot dependencies and we're moving the code to its own repository inside our new organization. Closing this for now. Thanks!

@vbrazo Cool! Thanks!


Update to hunter v0.20.64 and rename Sugar -> sugar

Sugar was apparently renamed to sugar in hunter, but the version of Leathers in hunter still depends on Sugar. This breaks hunter_add_package(Leathers)
This pr attempts to fix the dependency after which a new version of Leathers can be released and added to hunter.

Thanks, I will work on update in Hunter.


Allow scan storage providers to express that they only work for packages (not projects)

I just retried to use ClearlyDefined to curate missing copyrights. This worked perfectly for all gradle packages, but still not for yarn.
I used the config as described in the readme:
ort:
  scanner:
    storages:
      clearlyDefined:
        serverUrl: "https://api.clearlydefined.io"

    storageReaders: ["clearlyDefined"]

I only found this warning in the logs:
10:54:09.568 [main] WARN  org.ossreviewtoolkit.scanner.storages.ClearlyDefinedStorage - Could not obtain ClearlyDefined coordinates for package 'Yarn::package.json:'.
10:54:09.572 [main] INFO  org.ossreviewtoolkit.scanner.ScanResultsStorage - Read 0 scan result(s) for 'Yarn::package.json:' from ClearlyDefinedStorage in 12.518556ms.

It seems that clearly defined is not applied on the npm Libraries behind package.json of the project node.
Can this be curated by any other ORT config than this mentioned above?
Thank you very much.

This worked perfectly for all gradle packages, but still not for yarn.

Note that there is no such thing as "Yarn packages"; Yarn is an alternative package manager for NPM packages.

Could not obtain ClearlyDefined coordinates for package 'Yarn::package.json:'.

That's more or less expected. What happens here is that ORT looks for stored scan results at ClearlyDefined for the Yarn project you're analyzing / scanning. But as ClearlyDefined only has results for packages that have already been published, it cannot have results for the source code of your unpublished project.
For Yarn projects, the ORT id's type is "Yarn". But as soon as you would publish the package for the project to an NPM registry, ORT would consider that package id's type to be "NPM".

What happens here is that ORT looks for stored scan results at ClearlyDefined for the Yarn project you're analyzing / scanning.

@mnonnenmacher do you have a good idea how we could limit certain scan storage implementations to only package entities?

For Yarn projects, the ORT id's type is "Yarn". But as soon as you would publish the package for the project to an NPM registry, ORT would consider that package id's type to be "NPM".

Thank you very much for your explanation. So it would only help for the cases with missing copyrights to add these via curations, as this feature branch would suggest.

do you have a good idea how we could limit certain scan storage implementations to only package entities?

@sschuberth I think best would be if the storage implementations had a property for that, then the scanner could take this into account when fetching scan results.
@schvvarzekatze Please also note that you have configured ClearlyDefined as a scan results storage above, to get curations from ClearlyDefined you need to configure it as a package curation provider, see:
https://github.com/oss-review-toolkit/ort/blob/13f5dd27592b20956cf359f4c83645a9dd3a2111/model/src/main/resources/reference.yml#L39-L68

I think best would be if the storage implementations had a property for that, then the scanner could take this into account when fetching scan results.

You mean like simply also passing the ScanContext to readStoredResults or so?

I think best would be if the storage implementations had a property for that, then the scanner could take this into account when fetching scan results.

You mean like simply also passing the ScanContext to readStoredResults or so?

Ping @mnonnenmacher.

This should probably be implemented as part of https://github.com/oss-review-toolkit/ort/issues/6603.

I think best would be if the storage implementations had a property for that, then the scanner could take this into account when fetching scan results.

You mean like simply also passing the ScanContext to readStoredResults or so?

Yes, for example.

This should probably be implemented as part of https://github.com/oss-review-toolkit/ort/issues/6603.

To me, these are two independent tasks. I also wonder if we still need this ticket as the description is mixing curation providers with scan storages.

I also wonder if we still need this ticket as the description is mixing curation providers with scan storages.

Is it? I don't see how. Anyway, I'd like to keep this open as a reminder that we should have something like "capabilities" for a scan storage provider to express whether it makes sense to query it for project scan results in the first place.

I also wonder if we still need this ticket as the description is mixing curation providers with scan storages.

Is it? I don't see how.

The description starts with "I just retried to use ClearlyDefined to curate missing copyrights".

The description starts with "I just retried to use ClearlyDefined to curate missing copyrights".

Ah, right. The quoted log though comes from scan storages. I believe there simply was no difference made by the OP between the ClearlyDefined curation and ClearlyDefined scan storages, assuming that enabling the one would also enable the other.
Anyway, probably no public scan storage would ever contain results for projects, but only for packages, so querying these for projects could be avoided.


full support for every light sources

Add support for PointLight, SpotLight, AmbientLight,HemisphereLight and RectAreaLight. See https://github.com/Smithsonian/dpo-voyager/pull/215.
It enables physicallyCorrectLights (as advised in THREE manual), that's supposedly a breaking change but I couldn't find a case where it made a significant visual difference.

I updated the branch to leave out the azimuth/elevation change that might need further discussion.
The only change that would modify anything in existing scenes with only directional lights would be the addition of:
camera.near = 0.5*ins.shadowSize.value/100;
camera.far = 400*ins.shadowSize.value/100;

into source/components/CDirectionalLight.ts. I think it should always be the case that near/far plane scales with the light size, unless we want to have a dedicated setting, which is probably overkill given how shadows are generally not a huge concern for most users.
Support for Rect Light is very rough, it would require more code and some additional settings to use properly but I'm not yet convinced there is an use case for it that would justify the additional work.
As soon as this is merged I can update the companion PR for dpo-voyager to integrate those lights into the CV* system. I think it will be useful to once again split the work between "minimal integration" that should be merged when possible, and new UI features that might require discussion or some iterations to get them right.

What were the constants in
camera.near = 0.5*ins.shadowSize.value/100;
camera.far = 400*ins.shadowSize.value/100;

based on?
Would it be better to set these values (for any light) in at the scene level where we know the real bounds?

It was supposed to be "relative to defaults". However the default for far is 500, not 400...
As I am writing this, I realize the mapping isn't right anyways because those defaults are based on an orthogonal camera from -5 to 5 (so a shadowSizeof 10 in this system).
Defining "good" controls for this kind of things is tricky and depends on the use case. I absolutely didn't want to add another setting that might not be justified in the long run, thus the reuse of shadowSize. IMO shadowSize could be removed entirely in favor of a scene-controlled shadow size adjustment that would individually tune every parameters to the scene bounds, if such a system existed.
I'm in favor of keeping the existing shadowSize for now, fixing my formula to scale according to defaults, and leave the question of removing shadowSize to another time.
Let me know if that's OK with you and I will update accordingly.

One more question before merging. Per https://discourse.threejs.org/t/updates-to-lighting-in-three-js-r155/53733 when Three.js moved to physically correct lights, the 'normal' intensity values dropped significantly (factor of PI). This means our current 0-1 intensity scale no longer is appropriate. Due to the huge number of legacy scenes we have, the intensity value for directional lights has been artificially scaled back to original levels since that update so our lighting stays consistent until we can do a migration and update units appropriately. I think this would create a misalignment in intensities between light types. Not really an issue for our implementation at the moment, but might be good to have some consistency.


Consider configuration in frontend, remove JQuery

@phil-pona Can you test the POST requests before merging?

LGTM, Thanks


Simplify worker registration lifecycle.

Issue Number
#1292
Overview
This PR adjusts the worker registration life cycle so that creating and registering a worker is now a single operation, rather than a two-step operation.
Whereas previously callers would need to first call newWorker followed by insert, they now only need to call register.
In addition, we now provide automatic garbage collection of stale worker references from the registry, so that attempting to look up a previously-registered but prematurely-terminated thread will result in Nothing.

So if a worker terminates, it will be removed from the in-memory registry?

That is correct.

listWallets uses the in-memory Registry keys as source. If a worker were to terminate, the wallet would then go missing in Daedalus. Is that the most desirable behaviour? :thinking:

That is a very good point. I'll make a note on issue #1292 about this.

bors r+


napi port

I think this is what you wanted?

the node I deleted as I was just cleaning up and It must've gotten caught in the crossfire

will make changes later,but right now I have to focus on one of my projects

No problem i'll close it then you could do another PR if you wish


reference design implementation failed

When I used "python FINN/bin/finn --device=pynqz1 --prototxt=FINN/inputs/cnv-w1a1.prototxt --caffemodel=FINN/inputs/cnv-w1a1.caffemodel --mode=synth" to try the framework with Vivado 2018.2, It reported place_design ERROR.
log:
Phase 1.2 IO Placement/ Clock Placement/ Build Placer Device
ERROR: [Place 30-640] Place Check : This design requires more RAMB36/FIFO cells than are available in the target device. This design requires 144 of such cell types but only 140 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
ERROR: [Place 30-640] Place Check : This design requires more RAMB18 and RAMB36/FIFO cells than are available in the target device. This design requires 384 of such cell types but only 280 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
ERROR: [Place 30-640] Place Check : This design requires more RAMB36E1 cells than are available in the target device. This design requires 144 of such cell types but only 140 compatible sites are available in the target device. Please analyze your synthesis results and constraints to ensure the design is mapped to Xilinx primitives as expected. If so, please consider targeting a larger device.
INFO: [Timing 38-35] Done setting XDC timing constraints.
Phase 1.2 IO Placement/ Clock Placement/ Build Placer Device | Checksum: 1497648bb
Time (s): cpu = 00:00:22 ; elapsed = 00:00:15 . Memory (MB): peak = 3569.887 ; gain = 0.000 ; free physical = 7360 ; free virtual = 478279
Phase 1 Placer Initialization | Checksum: 1497648bb
Time (s): cpu = 00:00:22 ; elapsed = 00:00:15 . Memory (MB): peak = 3569.887 ; gain = 0.000 ; free physical = 7361 ; free virtual = 478279
ERROR: [Place 30-99] Placer failed with error: 'Implementation Feasibility check failed, Please see the previously displayed individual error or warning messages for more details.'
Please review all ERROR, CRITICAL WARNING, and WARNING messages during placement to understand the cause for failure.
Ending Placer Task | Checksum: 1497648bb
Time (s): cpu = 00:00:22 ; elapsed = 00:00:15 . Memory (MB): peak = 3569.887 ; gain = 0.000 ; free physical = 7367 ; free virtual = 478285
INFO: [Common 17-83] Releasing license: Implementation
60 Infos, 21 Warnings, 0 Critical Warnings and 5 Errors encountered.
place_design failed
ERROR: [Common 17-69] Command failed: Placer could not place all instances
INFO: [Common 17-206] Exiting Vivado at Mon Apr 22 05:28:05 2019...
[Mon Apr 22 05:28:06 2019] impl_1 finished
wait_on_run: Time (s): cpu = 00:13:35 ; elapsed = 00:15:15 . Memory (MB): peak = 1694.383 ; gain = 0.000 ; free physical = 7590 ; free virtual = 478508
INFO: [Common 17-206] Exiting Vivado at Mon Apr 22 05:28:06 2019...
cp: cannot stat '/tmp/finn-build-7wMqOe/finnaccel/finnaccel.runs/impl_1/procsys_wrapper.bit': No such file or directory
Traceback (most recent call last):
File "FINN/bin/finn", line 192, in
process_args(args)
File "FINN/bin/finn", line 92, in process_args
generate_hardware(net, dev, gen_bitfile=True)
File "FINN/bin/finn", line 161, in generate_hardware
ret.synthesis_bitfile()
File "/app/FINN/FINN/backend/fpga/backend_util.py", line 71, in synthesis_bitfile
subprocess.check_call(["sh", self.getBitfileSynthScriptPath()], cwd=self.path)
File "/usr/lib/python2.7/subprocess.py", line 190, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['sh', '/tmp/finn-build-7wMqOe/make_pynq_bitfile.sh']' returned non-zero exit status 1
resource report post synthesis:

Resource
Utilization
Available
Utilization %

LUT
40210
53200
75.58

LUTRAM
2148
17400
12.34

FF
49600
106400
46.62

BRAM
192
140
137.14

DSP
38
220
17.27

By the way, the bin file FINN/bin/finn shows it supports VU9P device which has more BRAM resource as I know, but when I was tring to use this parameter, it didn't work.  The vivado-hls had created the VU9P BlackBoxjam IP successfully, but the "FINN/backend/fpga/scripts/make-pynq-vivado-proj.tcl" only support pynqz1.

Different Vivado versions make different decisions about resource allocation. Your options are to use 2017.1 or to scale the usage of BRAM by scaling down the parameter "BRAM_PROPORTION = 1" https://github.com/Xilinx/FINN/blob/e6d44508b4f7c6ac8e2c6929f2ffa85ea5761708/FINN/core/config.py#L52

thanks for you reply. I tried to set BRAM_PROPORTION = 0.7/0.8, it didn't work. I am installing the 2017.1..
using the command "python FINN/bin/finn --device=vu9p --prototxt=FINN/inputs/cnv-w1a1.prototxt --caffemodel=FINN/inputs/cnv-w1a1.caffemodel --mode=synth" didn;t work. it seems the FINN framework only supports a PYNQ type FPGA board,  am I correct?

For now we only support the PYNQ backend. The vu9p functionality hasn't been released.
Are you still running out of BRAMS?

Yes, 2018.2 vivado reported the same utilization as before.

I'm closing all issues relating to the v.01 version in preparation for the new release. Please note that v0.1 is now deprecated and unsupported.


Student Authentication

Explore OpenID or ECP for authentication

@alexhwu BTW our central campus just announced they were adding OpenID (OIDC) support to our UCD authentication system, and since it's a pretty popular standard I think that'd be a good direction to support

@srkirkland Can you forward along the announcement so I can share with the other teams here? Thanks.

@alexhwu Sure, probably the best place would be http://developers.ucdavis.edu/events/2016/11/08/duo-cas/, which links to the PDF presentation our central campus tech unit gave about changes to campus auth in the works (http://developers.ucdavis.edu/media/meetings/7/duo-with-cas.pdf).  OAuth 2.0/OIDC announcement on page 8.

@srkirkland Thanks. Shared it with others. OAuth2/OpenID is on the roadmap and also looking at SAML-to-JWT as alternative to OIDC. Estimated completion of a dev env for SSO ECP is end of 2016.

@srkirkland We have a test ECP setup and @i8wu is able to get a SAML token from it. Working on getting an OAuth access token from the API manager using the SAML token.

@a6wu awesome.  I'd like to try something similar w/ OIDC/OAuth directly from a local provider too once you get the scaffolding working.  Are you using the Linking library to open a webpage and then using that to callback to the app?  Also, I'm assuming you are going to just create a redux user store and store the user info in there, right?

@srkirkland We're probably going to just use fetch/request instead of the Linking library. I think storing the SAML and or OAuth tokens in a redux store would be good, but for the username/password I'm looking into using this react-native-keychain.

@i8wu the tokens sound like a good idea, but why would you ever want to store the username/pass?  Seems like a recipe for future security issues.  Instead you could just have the oauth token last a long time, or keep the token as well as a refresh token and just refresh it as needed.

I don't think we can refresh the token if the user is out of app. And if they have to re-login every time the app might feel a bit clunky? The module seems to use iOS keychain natively and Android's account manager natively I think, so it should be fairly secure. Although, if this method really is insecure we can explore options with the tokens.

@i8wu Ok so this must be something with the AWS API manager that I've just never seen before?  When you use OAuth via something like GitHub or Facebook, you just store the token and then that's it, no need for passwords or refreshing or anything.

@srkirkland The UCSD APIs we want to use aren't on AWS, they're managed by WSO2

@i8wu I thought I read you got a SAML token from your UCSD APIs and then were going to get an "OAuth access token from the API manager using the SAML token".  Then all you'd need to do is to store that oauth access token and not worry about refreshing or passwords.

@srkirkland The SAML is from our SSO authentication, do oauth tokens not need to be refreshed? I actually don't know much about them, but I was led to believe that they do need to be refreshed once in a while.

@i8wu depends on how the OAuth tokens are setup, but most providers these days don't bother with refreshing oauth tokens.  GitHub and Twitter for example has them never expire, other providers might have them expire after a few years.

@srkirkland I try double checking with out API middleware guys then, thanks for the heads up!

@srkirkland Our API OAuth access token expires at about 20 minutes. SAML assertion also is set to expire, though at a much longer timeframe. On premise API manager is from WSO2 which currently is planned to house the student data API. We're using AWS API Gateway currently but hope to reduce it to just one API product.

Going with ECP for authentication. If a more straightforward method with OpenID presents itself we will be exploring that option.


add DocumentReference.parent and DocumentReference.getCollections

both methods are visible on nativeInstance but not on the Dart class.

DocumentReference.parent and DocumentReference.collection(path) have been added. I don't see getCollections in the docs though.
Closing as resolved. Feel free to submit new issue if you have more feedback.


Upgrade dependencies

Upgrade dependencies to latest versions.
As part of the AWS SDK upgrade, changes were necessary to handle the requirement integers and bools must be pointers.

@soapiestwaffles Unit tests continue to pass successfully. Changes have been tested on bucket that had over half a million objects.

Thank you! Looks great to me!

will release 1.1.4 shortly!


Could not execute dotnet restore on project names with spaces

🐛 Bug Report
We are using NuKeeper on a solution with a project name with spaces. Only the NuKeeper will fail while executing dotnet restore with following message:
dotnet restore 07 - Implementation.csproj
Command dotnet failed with exit code: 1

MSBUILD : error MSB1008: Only one project can be specified.
Switch: Implementation.csproj

For switch syntax, type "MSBuild -help"

Updates failed NuKeeperException : Command dotnet failed with exit code: 1

MSBUILD : error MSB1008: Only one project can be specified.
Switch: Implementation.csproj

For switch syntax, type "MSBuild -help"

Expected behavior
NuKeeper should accept project file names with spaces in it and use quotation while executing dotnet restore.
Reproduction steps
Execute NuKeeper on a solution with spaces in the csproj name.
Configuration
Version: 0.34.0
Platform if applicable:

[x] :hammer_and_wrench: NuKeeper CLI
[ ] :sparkles: GitHub
[ ] :robot: AzureDevops
[ ] :checkered_flag: Bitbucket
[ ] :earth_americas: Gitlab
[ ] :tv: Gitea
[ ] :whale: Docker

The issue seems here: https://github.com/NuKeeperDotNet/NuKeeper/blob/9c14d8bfce6239218c87bd2fe6d8bc3f98892fa6/NuKeeper.Update/Process/DotNetUpdatePackageCommand.cs#L44

Can anyone review & accept my PR #1093 to fix this issue

The PR has been merged. Thanks!


How to set max Width?

You might not need to set a max width as you can resize the image to what you want when crop it. For example:
$().cropper('getCroppedCanvas', {
  width: 960
});


Build fails on Windows 10 and Linux (Ubuntu 20.04.4 LTS)

Hi everyone,
I tried to build the image using docker as suggested. But it fails on both Windows 10 and Linux systems. Has anyone any idea how to fix this?
I have attached failed build log for reference.
install_log.txt
Thanks!

Have you tried using the simple version, instead of the old complex version?
https://github.com/firedrakeproject/firedrake/blob/master/docker/Dockerfile.firedrake

Looks like it's failing on loopy for some reason.
I tried to reproduce this after running docker image prune and docker container prune but it built successfully for me.  I'd second trying to build using the official images first to see if it's an issue with ours or something else.

Hi guys,
I was able to build the docker image successfully after overhauling my entire docker installation (Windows 10; using the Dockerfile in this repo).
I think torch(v1.10.0) dependency might have been deprecated (as it raised an error for me, but a v1.11.0 built without error. Is there a hard dependency for torch v1.10.0 ? )
Thank you for the suggestions.

I have not tried it out, but I don't think the dependency on Torch 1.10 is hard - the changes between 1.10 and 1.11 are minimal. Have sadly got no real experience with building on Windows..

Glad you got it working!  I don't know why it wasn't >=1.10 - let me just double check with RLlib and I'll fix it if there's no problem there.

@jcallaham Did you already remove Torch 1.10 from the build file? And if so is it necessary to update another part of the docker file where it says which torch to be installed?
Asking because I tried to rebuild last night to get the newest parts of the repo onto my local docker image and I got the error:
#20 41.07 ERROR: Could not find a version that satisfies the requirement torch==1.10.0 (from versions: 1.11.0, 1.12.0, 1.12.1)
#20 41.08 ERROR: No matching distribution found for torch==1.10.0

update:
found what needs to be changed in the requirements.txt file.
Final line is still torch==1.10.0. Question still is which should we use (from versions: 1.11.0, 1.12.0, 1.12.1)?
I will be building using 1.11.0 for the time being.


UX: be able to see issues to fix in meditor modal window

ATM the workflow is - click on "issues" icon or sidebar (in DLP redesign #857) to see which issues are detected, click "Fix issues" and user then ends up in meditor which feedback or easy way to see what issues they were.
A quick workaround would be to place the same omnipresent (across meditor views) icon with modal appearing upon click which would list those issues to be fixed.

Good idea.


Add template for checking for unapproved npm dependency licenses

A task and GitHub Actions workflow are provided here for checking the license types of npm-managed project dependencies.
On every push and pull request that affects relevant files, the CI workflow will use Licensed to check:

If the dependency licenses cache is up to date
If any of the project's dependencies have an unapproved license type.

Approval can be based on:

Allowed license type
Individual dependency

@nex3 this is one of the project infrastructure components I mentioned during our convo. Reviews are welcome 😃


Adding new Trusted Profile Analyzer QSG

This PR adds two new Quick Starts guides for the Service Preview release of the Trusted Profile Analyzer (TPA):

tpa-searching-for-vulnerability-information
tpa-scanning-an-sbom-file

These are to be added to the Learning Resources section under Application and Data Services.
Fixes: Jira doc issue TC-332

/ok-to-test

I'm closing this PR, and I opened a new one. Sorry for any confusion I've caused.


reduce docker image size 😉

When creating a great application we generally do small mistakes in Dockerfile. Try to find out some of our mistakes and we will merge your pull request.
How to build our docker docker image
How to Not Be the Engineer Running 3.5GB Docker Images
Possible improvements:

move to pydocker to write beautiful multi-line commands
remove commented code
remove unused apps, like vim, mc, etc.
use smaller base image: minimal ubuntu. NOTE: On Dockerhub, the new Ubuntu 18.04 LTS image is now the new Minimal Ubuntu 18.04 image
docker multistage builds

@blockspacer Thanks for providing the "possible improvements" section along with the issue description.
I would like to help you with this issue. Can i take this up ?

@blockspacer Thanks for providing the "possible improvements" section along with the issue description.
I would like to help you with this issue. Can i take this up ?

Yes of course @ThirumlaDevi !

@blockspacer I just want to confirm this with you, along with reference notes you also have a lot of commands commented out in you Dockerfile, I just want to get clearance if this commented code/ unneeded reference notes comments can be removed, cause you might probably use some of the commented code in certain scenarios. I understand that even if I remove certain commented code, you can certainly look into the history if the commit and still get the commands, but that might be too much.
I just wanted to cross verify this with you.

@ThirumlaDevi
It is good idea to remove unneeded code, thank you.

@blockspacer
I am having issues with building the original docker image. I followed the documentation recommendation for building and running docker image.
I hope the below error logs helps
#18 685.4 DEBUG :rest_client_common.py[156]: REST: ping: https://conan.bintray.com/v1/ping [2020-10-13 10:50:49,370]
#18 686.4 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:50,361]
#18 686.4 DEBUG :rest_client_common.py[183]: REST: get: https://conan.bintray.com/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:50,361]
#18 687.3 DEBUG :rest_client_common.py[156]: REST: ping: https://api.bintray.com/conan/bincrafters/public-conan/v1/ping [2020-10-13 10:50:51,247]
#18 688.3 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:52,227]
#18 688.3 DEBUG :rest_client_common.py[183]: REST: get: https://api.bintray.com/conan/bincrafters/public-conan/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:52,227]
#18 688.6 DEBUG :rest_client_common.py[156]: REST: ping: https://api.bintray.com/conan/skypjack/conan/v1/ping [2020-10-13 10:50:52,511]
#18 688.8 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:52,760]
#18 688.8 DEBUG :rest_client_common.py[183]: REST: get: https://api.bintray.com/conan/skypjack/conan/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:52,760]
#18 689.1 DEBUG :rest_client_common.py[156]: REST: ping: https://api.bintray.com/conan/milerius/doom_strong_types/v1/ping [2020-10-13 10:50:53,049]
#18 689.4 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:53,302]
#18 689.4 DEBUG :rest_client_common.py[183]: REST: get: https://api.bintray.com/conan/milerius/doom_strong_types/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:53,302]
#18 689.7 DEBUG :rest_client_common.py[156]: REST: ping: https://api.bintray.com/conan/aardappel/flatbuffers/v1/ping [2020-10-13 10:50:53,630]
#18 689.9 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:53,884]
#18 689.9 DEBUG :rest_client_common.py[183]: REST: get: https://api.bintray.com/conan/aardappel/flatbuffers/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:53,885]
#18 690.2 DEBUG :rest_client_common.py[156]: REST: ping: https://api.bintray.com/conan/manu343726/conan-packages/v1/ping [2020-10-13 10:50:54,145]
#18 690.5 DEBUG :rest_client.py [58]: REST: Cached capabilities for the remote: ['complex_search', 'checksum_deploy', 'revisions'] [2020-10-13 10:50:54,401]
#18 690.5 DEBUG :rest_client_common.py[183]: REST: get: https://api.bintray.com/conan/manu343726/conan-packages/v2/conans/search?q=conan_build_helper%2F%2A%40conan%2Fstable&ignorecase=False [2020-10-13 10:50:54,402]
#18 690.7 ERROR: Error loading conanfile at '/opt/cxtpl/tools/.tmp/conan_openssl/conanfile.py': Version range '~=0.0' from requirement 'conan_build_helper/[~=0.0]@conan/stable' required by 'python_require' could not be resolved in local cache
#18 690.8 Elapsed time: 6 s. (time), 0.002653 s. (clock)
#18 690.8 CMake Error at tools/buildConanThirdparty.cmake:155 (message):
#18 690.8   (conan_install_target)
#18 690.8
#18 690.8         Bad exit status 1
#18 690.8 Call Stack (most recent call first):
#18 690.8   tools/buildConanThirdparty.cmake:201 (conan_install_target)
#18 690.8   tools/buildConanThirdparty.cmake:263 (conan_build_target_if)
#18 690.8
#18 690.8
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c set -ex   &&   cd $WDIR/cxtpl   &&   if [ "$NO_SSL" = "True" ]; then     echo 'WARNING: GIT SSL CHECKS DISABLED! SEE NO_SSL FLAG IN DOCKERFILE'     &&     ($GIT config --global http.sslVerify false || true)     &&     ($GIT config --global https.sslVerify false || true)     &&     ($GIT config --global http.postBuffer<PHONE_NUMBER> || true)     &&     ($GIT config --global url."https://github.com".insteadOf git://github.com || true)     &&     export GIT_SSL_NO_VERIFY=true     ;   fi   &&   if [ "$GIT_CA_INFO" != "" ]; then     echo 'WARNING: GIT_CA_INFO CHANGED!
# Give docker the rights to access X-server
sudo -E xhost +local:docker

# build Dockerfile
sudo -E docker build --no-cache \
  --build-arg GIT_WITH_OPENSSL="" \
  --build-arg NO_SSL="False" \
  -t cpp-docker-cxtpl .

Please provide command that was used to build Docker image.

DEPRECATED. USE INSTEAD: https://github.com/blockspacer/flex_squarets_plugin


grok: Fix panic when encountering optional fields

Closes #5008

Just tested out this branch at commit 9c4d65f and indeed it fixes the panics for both the repro cases shown in #5008 so it's a functional 👍 for me!


Spawn child process and creatie server in it

Is it possible something similar to node cluster module
`cluster = require('cluster');
if (cluster.isMaster) {
cluster.fork();
cluster.on('fork', function(worker) {
newPID = worker.process.pid;
console.log(worker.process.pid);
});
cluster.on('exit', function(worker, code, signal) {
cluster.fork();
});
}
if (cluster.isWorker) {
//create server here and logic to restart process with process.exit(1);
});
}`

When we have child and master process and we could restart server with simple endpoint /restart in which we are calling process.exit(1) - ( in node.js this works properly )

Absolutely! :-) What you're asking for is way beyond the scope of this low level child-process component, but I don't see why it wouldn't be possible to build something like this on top of this component :+1:
I'm not currently aware of any package that provides this out of the box, but if you happen to find or build one, make sure to let us know.
I hope this helps :+1:


external_modules_updates_available retains updates for deleted modules

REDCap 9.5.32, PHP 7.4.6
Through strange circumstances [1] we ended up with six external modules installed on our production server that we did not want. REDCap found that two of these had updates available. I deleted all six external modules, but REDCap is still prompting us to apply these two updates for external modules that no longer exist on the system.
Value of external_modules_updates_available in redcap_config: {"729":{"name":"redcap_entity","version":"2.3.5","title":"REDCap Entity"},"744":{"name":"shazam","version":"1.3.8","title":"Shazam"}}
[1] We use separate web and database servers. In testing a planned migration from an old web server to a new web server, the new web server was connected to one of our staging databases. That staging database had the six external modules installed. REDCap apparently saw database entries for those external modules but no matching directories on the filesystem, so retrieved the six external modules and copied them to the file system. Later, after the migration of the web server, the new web server was connected to our production database. REDCap apparently saw the six external modules in the filesystem and added entries for the external modules into the database. REDCap then found that two of the external modules had updates available, and so added those updates to the external_modules_updates_available configuration.

PR #340 should fix this.  Thanks very much for reporting it!


Test

Reason for Change:

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

Test


Added support for enum.protocols feature

Addresses #171.
Creates a new enum.protocols option that is used to drive protocol conformance for enums of strings, which are the only currently supported enum variety. Currently does not do any of the redundant protocol stripping that entities.protocols does.

@liamnichols I believe this both addresses the test failures and your feedback. The PR suddenly got huge because I needed to regenerate snapshots, since protocols are sorted by name now.

@liamnichols any update on this?

Any update on this PR? I would like to add Sendable on enum like we can do on entities.protocols 🙏

Any update on this ?


Add Chakra Transitions Component

All Submissions:

[x] Have you followed the guidelines stated in CONTRIBUTING.md file?
[x] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

New Feature Submission:

[x] Have you linted your code locally prior to submission?

After these steps, you're ready to open a pull request.
This Pr add the Chakra Transitions component, along with Fade, ScaleFade, Slide, SlideFade and Collapse to provide simple transitions.
Fixes #1050

It seems you need to run poetry run ruff check . and then commit again. If you want, I can help you set up your editor so that ruff violations get highlighted automatically.

It seems you need to run poetry run ruff check ., fix the violations and then commit again. If you want, I can help you set up your editor so that ruff violations get highlighted automatically.

Sure, please do, I have joined the discord server

In that case please message me there, name is the same as it is here.


scipy.stats.poisson.interval gives the wrong result

scipy.stats.poisson.interval gives the wrong result
for the example below it gives (1,14), whereas (0,14) is expected
The interval (1,14) does not cover at least 0.99 of the distribution, as can be checked using the cdf method, hence the answer is wrong.
Reproducing code example:

import scipy
print(scipy.__version__)
from scipy.stats import poisson

alpha = 0.99
expected = 6.298487833
pint = poisson.interval(alpha,expected)
covered = poisson.cdf(pint[1],expected)-poisson.cdf(pint[0],expected)

print(pint)
print(covered)
print("Correct" if covered >= alpha else "Incorrect: {} is less than {}".format(covered, alpha))

# in this case I would expect (0, 14) as the interval:
poisson.cdf(14,expected)-poisson.cdf(0,expected)

Output:
1.2.0
(1.0, 14.0)
0.9843652848169578
Incorrect: 0.9843652848169578 is less than 0.99
0.9959487309808245

Scipy/Numpy/Python version information:

1.2.0 1.15.4 sys.version_info(major=3, minor=7, micro=2, releaselevel='final', serial=0)

AFAIR, the interval points are inclusive
i.e. for discrete the lower tail probability is cdf(low - 1) and not cdf(low) which puts the low point in the tail and outside the interval

AFAIR, the interval points are inclusive
i.e. for discrete the lower tail probability is cdf(low - 1) and not cdf(low) which puts the low point in the tail and outside the interval

Ah yes, indeed, thanks for your reply. Closed


Add option to import computer parameters from a CSV file.

Add a switch to New-PISysAuditReport to accept a CSV file with computer parameters so that users do not need to make separate piauditparams calls to declare components to audit.

Added in #112


Add a PrivacyInfo file

Duplicate https://github.com/apple/swift-protobuf/issues/1529
Just hasn't been a release with it yet, likely to happen soon.


Remove redundant nil check in WalkGitLog

From the Go specification:

"1. For a nil slice, the number of iterations is 0." https://go.dev/ref/spec#For_range

Therefore, an additional nil check for before the loop is unnecessary.

Example: https://go.dev/play/p/xCk3Oba1R_0

Thanks for the PR!
For anyone reviewing this, it is easier when you hide the whitespace: https://github.com/go-gitea/gitea/pull/26773/files?diff=unified&w=1


Added exit code information message to master process and resolved signals propagation issue.

reinstallSignals had duplicated code with installSignals.
There is no need to continue when select_stream returns false, occasionally receives SIGPIPE which should be ignored.
Added pcntl_async_signals(true); cause when running Workerman as a library, signals wont reach Workerman nor the master service wrapping Workerman.
These code changes are in production environment, and service is now working without problems.

Hi akotulu,
Thank you for your pr. But this pull request cannot be merged because it seems to have several bugs.

When stream_select returns false, it may indicate that a timer is about to run, so we cannot directly end the current loop.
When reinstalling a signal, static::$globalEvent must be used to install the signal, otherwise, when using event libraries such as Events, Swoole, or Ev, the signal may not be received properly.
Asynchronous signals should not be used. Signals should be uniformly processed after each event loop to avoid disrupting the execution flow of the business during processing. For example, if the business receives a SIGINT signal during processing and ends the process prematurely, it may result in incomplete business execution.

Thank you for the feedback. I will remove these modification and  test again. I've implemented a Wrapper class on top of Workerman to handle different messages and communicate with other services. There are 3 Wrapper Workerman master instances in one server having single slave to transmit WS messages. In the future, these Wrappers can be installed on dedicated machines. Problem arouse using default PHP select event. It occasionally received SIGPIPE and restarted the services. It may have been caused by Monit tool watching over pm2 and pm2 actually running Wrapper instance. Both tools spam PID file every 10ms. Everything worked on my Docker replica of production server, but when uploading to actual server, everything started to restart. I have disabled Monit for now and using only pm2. Service is running as it should without any restarts.
Also PHP's default select somehow runs out of FD indexes after two weeks (services need to be restarted), here is the error
Message: stream_select(): You MUST recompile PHP with a larger value of FD_SETSIZE.
It is set to 1024, but you have descriptors numbered at least as high as 7993.
 --enable-fd-setsize=8192 is recommended, but you may want to set it
to equal the maximum number of open files supported by your system,
in order to avoid seeing this error again at a later date.

To fix it I've built a libevent select library. Hope it will resolve the issue.
I will do a new pull request with only Log changes. Cause its really helpful to see when service restarted what Signal it received.


 Text Formatting

ISO paper for this feature: P0645R10
Not implemented yet as of 2/19/2021

moved to quest


Is it possible to replicate whatsapp call receiving behaviour

Using this plugin I was able to show time sensitive notification with the default ringtone.
I used
defaultRingtoneType: DefaultRingtoneType.Ringtone,
importance: NotificationImportance.High,
locked: true

Here is a preview

But I couldn't complete following two

Keep this notification for a longer period of time ( until the ringtone stops or for a fixed time such as 20 sec )
When the screen is off ( in lock ), wake up screen

Please guide me in the right direction

Yes! This is the next feature that ill release. But for now im working with receiving background notifications. Only after that (0.0.7 version) ill be able to develope this new feature.

@rafaelsetragni This feature is related to Notification.CATEGORY_CALL, right? How long will it take to implement?

I need to release the 0.0.7 version and finish the companion plugin to receive push notifications from Firebase. I gonna need 2-3 months to get at this point.

Its already available at version 0.6.14 with two versions: Messaging and Messaging Group.

Hi there,
`    any development on
await AwesomeNotifications().createNotification(
    wakeUpScreen: true,
    category: NotificationCategory.Call,
),`

I have been waiting since your last comment on Sep 21, 2021.
Thanks in advance for the plugin.

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


CI: reshuffle two Windows Azure CI jobs, and don't run 'full' on both

The Python 3.10 test was timing out a lot, and there's no reason to run the full test suite on all three 64-bit test jobs.
Python 3.9/3.10 are switched here to preserve the full test suite run on 3.10 with ILP64 BLAS. If 3.10 and 3.8 pass, then 3.9 full will be fine too.

This is happy now, failures are unrelated. The build times for the four Windows jobs are in the 33-43 minutes range. Not sure if that's due to low load on Azure today (it's a holiday across the world), but it's certainly encouraging.

This is happy now, failures are unrelated. The build times for the four Windows jobs are in the 33-43 minutes range. Not sure if that's due to low load on Azure today (it's a holiday across the world), but it's certainly encouraging.

thanks Ralf


Add support for empty topic names.

CZO - Design Discussion
CZO - API Design Discussion

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

It'd be great to receive an initial review on this.

We'll stash all the commits in one, kept it separate for the ease of review and re-iterating on different chunks.

Currently, I have ignored tests and documentation. -- that'll be quick to do if implementation looks fine.

The only left part is related to narrows:

/messages/matches_narrow
match_subject field in GET /messages response.

API Docs part is done. Working on tests.

I prefer this split out as written, so don't squash the commits.

Updates in the recent push:

Addressed review comments
Added first commit as per yesterday's discussion in CZO.
Wrote commit messages.

Last Update

In the recent push, added code in the 3rd commit so that narrowing to "general chat" works properly.
git diff

diff --git a/zerver/lib/narrow.py b/zerver/lib/narrow.py
index 437914cfce..a7698cc967 100644
--- a/zerver/lib/narrow.py
+++ b/zerver/lib/narrow.py
@@ -49,6 +49,7 @@ from zerver.lib.streams import (
     get_stream_by_narrow_operand_access_unchecked,
     get_web_public_streams_queryset,
 )
+from zerver.lib.topic import maybe_rename_general_chat_to_empty_topic
 from zerver.lib.topic_sqlalchemy import (
     get_followed_topic_condition_sa,
     get_resolved_topic_condition_sa,
@@ -900,6 +901,20 @@ def can_narrow_define_conversation(narrow: list[NarrowParameter]) -> bool:
     return False

+def update_narrow_terms_containing_empty_topic_fallback_name(
+    narrow: list[NarrowParameter] | None,
+) -> list[NarrowParameter] | None:
+    if narrow is None:
+        return narrow
+
+    for term in narrow:
+        if term.operator == "topic":
+            term.operand = maybe_rename_general_chat_to_empty_topic(term.operand)
+            break
+
+    return narrow
+
+
 # This function implements the core logic of the `with` operator,
 # which is designed to support permanent links to a topic that
 # robustly function if the topic is moved.
diff --git a/zerver/tests/test_message_topics.py b/zerver/tests/test_message_topics.py
index 4970102a15..cc0ba8d9f7 100644
--- a/zerver/tests/test_message_topics.py
+++ b/zerver/tests/test_message_topics.py
@@ -405,6 +405,7 @@ class EmptyTopicNameTest(ZulipTestCase):
         }
         result = self.client_get("/json/messages", params)
         data = self.assert_json_success(result)
+        self.assert_length(data["messages"], 2)
         for message in data["messages"]:
             self.assertEqual(message["subject"], Message.EMPTY_TOPIC_FALLBACK_NAME)

@@ -414,9 +415,28 @@ class EmptyTopicNameTest(ZulipTestCase):
         }
         result = self.client_get("/json/messages", params)
         data = self.assert_json_success(result)
+        self.assert_length(data["messages"], 2)
         for message in data["messages"]:
             self.assertEqual(message["subject"], "")

+        get_params = {
+            "allow_empty_topic_name": "false",
+            "anchor": "newest",
+            "num_before": 2,
+            "num_after": 0,
+            "narrow": orjson.dumps(
+                [
+                    {"operator": "channel", "operand": "Denmark"},
+                    {"operator": "topic", "operand": Message.EMPTY_TOPIC_FALLBACK_NAME},
+                ]
+            ).decode(),
+        }
+        result = self.client_get("/json/messages", get_params)
+        data = self.assert_json_success(result)
+        self.assert_length(data["messages"], 2)
+        for message in data["messages"]:
+            self.assertEqual(message["subject"], Message.EMPTY_TOPIC_FALLBACK_NAME)
+
         # Fetch using `/messages/{message_id}` endpoint.
         result = self.client_get(
             f"/json/messages/{first_message_id}", {"allow_empty_topic_name": "false"}
diff --git a/zerver/views/message_fetch.py b/zerver/views/message_fetch.py
index e9f91bfbb2..c1654c5c05 100644
--- a/zerver/views/message_fetch.py
+++ b/zerver/views/message_fetch.py
@@ -25,6 +25,7 @@ from zerver.lib.narrow import (
     is_spectator_compatible,
     is_web_public_narrow,
     parse_anchor_value,
+    update_narrow_terms_containing_empty_topic_fallback_name,
     update_narrow_terms_containing_with_operator,
 )
 from zerver.lib.request import RequestNotes
@@ -145,6 +146,7 @@ def get_messages_backend(
         anchor = parse_anchor_value(anchor_val, use_first_unread_anchor_val)

     realm = get_valid_realm_from_request(request)
+    narrow = update_narrow_terms_containing_empty_topic_fallback_name(narrow)
     narrow = update_narrow_terms_containing_with_operator(realm, maybe_user_profile, narrow)

     num_of_messages_requested = num_before + num_after


Line numbers clashing with Query on first load

This issue pertains to the following package(s):

[ ] GraphQL Playground - Electron App
[ ] GraphQL Playground HTML
[x] GraphQL Playground
[ ] GraphQL Playground Express Middleware
[ ] GraphQL Playground Hapi Middleware
[ ] GraphQL Playground Koa Middleware
[ ] GraphQL Playground Lambda Middleware

What OS and OS version are you experiencing the issue(s) on?
Mac 10.13.6
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
v1.7.4
What is the expected behavior?
When the playground loads up for the first time, I should be able to select the query/mutation text box and write my query/mutation.
What is the actual behavior?
When the playground loads up for the first time I can select the text box however the line numbers are in the way and the text overlaps with the text I am writing.
What steps may we take to reproduce the behavior?
Require the playground in a React app using patternfly's Tab container (with the playground as a TabPane) and navigate to the playground.
The only way to fix this is to open a new tab which (sometimes) fixes the allignment across all tabs.

Can you create a minimal for reproduction of this problem? In normal react version everything works.


[Feature Request] Extend import functionality

Currently, the following import capabilities are possible

only relative paths are allowed.
import of an entire main block with {block} import {file}, e.g. images import 'imports/images.nss'
import within the main blocks

var
static
dynamic
not sure about set, set/theme, etc.

Please consider implementing the support for (if not already supported):

absolute paths,
at least local ones, starting with a drive letter, i.e. C:\some\path\config.nss or D:\config.nss.
This is required for the use of expressions like @user.appdata.
expressions (variables and functions)
e.g. @sys.programdata, @user.appdata or user-defined functions available in the current scope.
globing
e.g. to include all files in a directory: C:\some\path\*.nss.
Or, if globing is too complex, then maybe if the path points to a directory, include all *.nss files in that directory.
In either case, sort the files alphabetically before processing.
importing shell block
i.e. shell import {file} (unless -register {config.nss} is implemented).

import  set/theme

It is already being added

import of an entire main block with

This was also supported 2 days ago

absolute paths

This issue has been fixed

expressions (variables and functions)

Expressions can be used with import

globing and 4. importing shell block

I will try to implement this suggestion
This link has the last build that was developed
https://nilesoft.org/download/shell/debug.zip

Thank you, @moudey!

import of an entire main block with

This was also supported 2 days ago

I have tested with both v1.8.2 as well as v<IP_ADDRESS> and was not able to import the var block in the following manner:
shell
{
	var import 'metaworx/var.nss'

	// all the other blocks.
}

However, it works like so, with the exact same file (metaworx/var.nss):
shell
{
	var
	{
		import 'metaworx/var.nss'
	}

	// ..
}

absolute paths

This issue has been fixed

Awesome! Works perfectly. 👍

expressions (variables and functions)

Expressions can be used with import

Jep. I don't know why I couldn't get it to work. But works now. 👍

globing and 4. importing shell block

I will try to implement this suggestion

Ok. Thank you.

Another thing I've noticed: When there is a import in an already imported file, then I need to add an extra closing curly bracket } at the end of the intermediate file.
As an example:
shell.nss
shell
{
	var
	{
		mwxConvertMedia =<EMAIL_ADDRESS>	}

	// ..

	dynamic
	{
		import 'metaworx/convert.nss'  //   <== 1st level import. All is good in this file.
	}

	// ..
}
//  <== Since this is the top-level file, there is no need for an extra closing curly bracket.

metaworx/convert.nss
// show this menu on the desktop and taskbar
menu(
	title     = 'Convert'
	type      = 'desktop|taskbar'
	separator = 'both'
	image     = \uE0DA
)
{
	import "convertSubmenu.nss"  //  <== 2st level import.
                                     //      This import raises an error, if the file
                                     //      does not have an additional closing
                                     //      curly bracket } at the end
}

// show this menu also in the explorer on all directories ending with "abc"
menu(
	title     = 'Convert'
	type      = 'directory'
	find      = '*abc'
	separator = 'both'
	image     = \uE0DA
)
{
	import "convertSubmenu.nss"  //  <== 2st level import.
                                     //      This import makes no difference,
                                     //      since there is already another import

}
}  //  <== Note this extra closing curly bracket.
   //        Without this, I would get the following error:
   //       [error] line[x] column[y], MenuType expected "convert.nss"

convertSubmenu.nss
item(
	title  = 'Some info'
	vis    = label
	col    = 0
)

separator

item(
	title     = 'Default'
	image     = \uE259
	cmd       = @mwxConvertMedia
	args      = '--default "" @sel.path.quote'
)

item(
	title     = 'Medium'
	image     = \uE257
	cmd       = @mwxConvertMedia
	args      = '--medium "" @sel.path.quote'
)
//  <== Since there is no import in this file, there is no need for an extra closing curly bracket.
//      If there was another import also in this file, then the bracketwould be required.

Happy to create a separate github issue for this. Shall I?

Happy to create a separate github issue for this. Shall I?

Yes, because I am currently developing the import, it would be good to stand on this issue

Thank you, @martin-rueegg . I am currently working on fixing these issues

Hi @martin-rueegg, Please check the import tag issues with this build
shell.nss
import 'imports/extended.nss'

extended.nss
var {
    import 'var.nss'
}

set {
    import 'set.nss'
    static.image=2
    //theme {import 'theme.nss'}
}

images {
    import 'images.nss'
}

static {
    import 'static.nss'
}

dynamic {
    import 'dynamic.nss'
}

or
extended.nss
var import 'var.nss'
set import 'set.nss'
images import 'images.nss'
static import 'static.nss'
dynamic import 'dynamic.nss'

Hi @moudey
Thank you so much for this! I've tested several scenarios; here the results of my tests.

shell.nss
The following works:
// works. But not recommended. See below.
import 'imports/extended.nss'

However, I would suggest to not support this syntax, as it is not consistent with the requirement, that the import tag should either

be enclosed in an other section (shell in this case), and then not having the section's name in front of the keyword:
section { import 'file.nss' }, or
it should name the section before the import keyword like so:
section import 'file'.

See https://nilesoft.org/docs/syntax#import
In fact, the latte is currently not supported for the root file. Hence the following does not work:
// does not work
shell import 'imports/extended.nss'

This is something I would recommend to change, as explained above.
But then again, this works:
// works
shell {
    import 'imports/extended.nss'
}

Which is great as it follows the suggested syntax! And it allows to have the system-defined config files to be included, and then also the user's extended scripts:
shell {
    // system provide files, which may be overwritten during updates
    import 'imports/extended.nss'

    // my own customization,
    var import<EMAIL_ADDRESS>Shell/var.nss'
    dynamic import<EMAIL_ADDRESS>}

Awesome!

extended.nss
All combinations in extended.nss work perfectly!
Nothing more to say. Other than: Fantastic!

Non-existent import file
Currently, an import instruction that points to a non-existing file, makes the whole thing fail. I would recommend for this case to only write a warning to the log file but then simply ignore the missing file.
IF you would ignore that, you could, for example, ship the following shell.nss with your software ...
shell {
    import 'imports/extended.nss'

    import<EMAIL_ADDRESS>}

As such, the user could simply create a file in %USERPROFILE%\shell.nss and add their customization there.

Multiple inclusion of the same file
It is now no longer possible, to include the same config file multiple times. This is probably to avoid recursion.
However, it is very helpful as you can do sort of modules/snippets, that you want to include in different places. E.g. I have a sub-menu with some dynamic items, that I have included in several dynamic menus. This saves me a lot of writing and maintenance.
In order to allow the inclusion of the same file at different locations, and still prevent circular-reference, you could maybe employ something like an array, where you store the absolute paths of the included files, but also remove them again at the end of every file. And before every import of a new file, check it against the entries in the array.

shell.log
It's great to see the imports here. Is that only for debug builds? - Very helpful indeed.
If in a standard distribution this would not work, then it would be great if this could be enabled, eg. by reloading the configuration with Shift+Ctrl+Right-Click on the Taskbar, rather than just Ctrl+Right-Click.
The log file shows import, just after already imported. Minor issue, but could create confusion.

Conclusion / Summary
Awesome work! Thanks again.
Suggestions:

[ ] In shell.nss, remove Support for import 'imports/extended.nss'
[ ] In shell.nss, add Support for  shell import 'imports/extended.nss'
[ ] Ignore non-existing config files with a warning in the log file, rather than aborting the entire parsing
[ ] Allow re-import of the same config file, if it does not lead to recursion (see above on how that could be implemented)
[ ] Maybe enable import logging with Shift+Ctrl+Right-Click on the Taskbar
[ ] (Minor) fix to not report a "successful" import after a import has actually failed (due to non-existing file or recursion)
[ ] Also fix the issue, where an additional closing bracket would cause explorer to crash (see https://github.com/moudey/Shell/issues/187#issuecomment-1460721355)

Hope this helps. Happy to later update the documentation.
Thanks!


operator-no-unspaced: fix signed parameter in a function call inside …

fix signed parameter in a function call inside interpolation
fixes bug https://github.com/kristerkari/stylelint-scss/issues/450

Looks great! Thanks

@airyboy Looks like you are using your fork's master branch for the changes, and it's including the changes from comment-no-empty to this pull request too. Would it be possible for you to use branches for your changes instead of master?

@kristerkari sure, sorry, I haven't been using github for a while

I created PR #465, this PR should be closed


Causes function calls to lose their highlighting

Under Monokai and "C" style, function calls are highlighted in blue.  Under Monokai and "C Improved" style, function calls remain white.

This is the intended behavior. Only special (a.k.a. support) functions are highlighted (like printf). Remaining are left as is.

I see.  Is there some way to change this?  Would be great if there was color settings somewhere.

Well, customizing syntax definition files is always a pain, I'm afraid the only way is to modify tmLanguage file directly. However, I believe that the current behavior should be left as is, to be consistent with syntax definitions of other languages, and to make the highlighting more informative by emphasizing library functions. So, I'm probably not going to change this, at least in the master.
To be clear, I would likely add an option for a user to be able to customize this, among with other highlighting aspects, if I could. But again, I don't know how to achieve this without doing some magic like generating tmLanguage on the fly.
If the highlighting really annoys you, you could fork the repo and change the regex that define a function call:
		<key>call</key>
		<dict>
			...
				(?= # don't consume to recognize support functions
				    (?: [A-Za-z_]\w*+ | ::[^:] )++
				    (?:\s|/\*.*?\*/)*+ \( )

... to something like this:
				((?: [A-Za-z_]\w*+ | ::[^:] )++)
				(?= (?:\s|/\*.*?\*/)*+ \( )

And add a pattern capturing that group and associating it, for example, with support.function.custom.c scope:
			<key>beginCaptures</key>
			<dict>
				<key>1</key>
				<dict>
					<key>name</key>
					<string>support.function.custom.c</string>
				</dict>
			</dict>

This should do the trick!

Awesome thanks, I'll do that.  You may want to add that to some README or something.

You're welcome, thanks for reporting this.
OK, I'll consider mentioning the issue in Dropped features section of README, and I'll leave this open until I get some spare time to do that.

Thanks for C Improved. It's very useful!
On Feb 3, 2015 5:21 PM, "Eldar Abusalimov"<EMAIL_ADDRESS>wrote:

You're welcome, thanks for reporting this.
OK, I'll consider mentioning the issue in Dropped features section of
README, and I'll leave this open until I get some spare time to do that.
—
Reply to this email directly or view it on GitHub
https://github.com/abusalimov/SublimeCImproved/issues/11#issuecomment-72772555
.

Done

BTW, the default behavior is now reverted to highlight all function calls (as it used to be in the standard C package), so this issue can be considered as fixed.


Docs: use github README as docs frontpage

It renders correctly locally, but I don't think we can test it on readthedocs without actually pushing it


Odd isInSubnet behavior

> new Address4("<IP_ADDRESS>/16").isInSubnet(new Address4("<IP_ADDRESS>"))
false

Is that expected? it seems isInSubnet won't actually tell you whether or not some address is contained by a range of ips represented by a CIDR. Is there another method from that?

False alarm. Sorry! I just got the direction wrong (it's in fact address.isInSubnet(subnet)). The documentation is a little confusing regarding the expected relation.

sorry for the poor docs! i'll leave this issue open until i have a chance to clarify them :)


Change image_size to 256

Hi,
I want to change image_size to 256. Do I need to change the value of n_bits and n_bins?
Another question I want to ask is the meaning of the code from lines 111 to 116 in https://github.com/rosinality/glow-pytorch/blob/master/train.py#L111
Thank you
Viet Nguyen

In the paper authors used 5 bits for 256px.
And image * 255 is to rescale value ranges for args.n_bits < 8, as image is in [0, 1].

In the https://github.com/rosinality/glow-pytorch/blob/master/train.py,
After line 109 image is in [0,1]. After line 111 image is in [0,255]. After line 114 image is in [0,31.875]. After line 116, image is in [-0.5,0.5]. Am I right? Why don't we just change from [0,1] to [-0.5,0.5] directly?

No, it is different as it is multiplied with 255 (not 256) and floor is applied.

Okay, I understand. So I change the image_size to 256 instead of 64 so that the image size becomes (3,256,256). Do I need to change any value, e.g n_bits,..?

I think it is safe to use the settings in the paper. (5 bits)

Yeah, thank you very much!

Hi, when I change  the image_size to 256 instead of 64 so that the image size becomes (3,256,256), some errors occured, can you share your code?


AAI Miners

i noticed that the AAI Miners can mine the deep core patches
and the "Zoner" indentifys the patches as an ore
Is it wanted like that?
Factorio 0.16.51
Mod Version: 1.11.4
(Windows 10)

Hello,
Thanks for the report, that's not explicitly expected. I guess AAI Miners are coded to mine any ore. I'll check if AAI has a way to specify a restriction. Indeed deep core ore is designed to be mined specifically with its mining machines, especially in the case of required sulfuric acid.
Regards

After checking AAI code there doesn't seems to be an easy way to prevent this sorry.
I guess you can "manually" add a condition to ignore specific tiles in your AAI scanner circuit as a workaround.

Gotcha, so the problem is that you have AAI miners going to mining zones put on top of deep core ores where I guess you have deep core miner on ? Maybe you could instead put a "no go zone" with the zone planner tool and again add a circuit to ignore them ?
Means you'll have to put ignore zone on all deep core ore tho so it might not be an optimal workaround.
I'll dig a bit more if I can find another solution.

Problem was i had not researched the deep ore miner and all that stuff, and now i have AAI not installed anymore
(performance reasons, really bad AI (miners, haulers all get stuck in some wall or transportbelt) and that the deep ore patches only spawn when some ore is / got mined, and my setup always check if there is this ore, when yes do nothing (place the same zone as before) and otherwise delete the zone ...)

Just in case it could be usefull I've made a test to not place zones if a specific building is also present, it works. Just add a combinator in the scanner output before any other processing.

i know, but like i said, i didnt had it researched (i couldnt build these buildings)

Yeah, it just a workaround :)
The AAI Miner do actually mine the deep ore patches so it still working until you have the deep core miner.
Although the patch is infinite so it can be considered unbalanced in a way but properly preventing it would be much work for the minor issue it is.


SignalR integration with actor model

We have an useful reference at https://github.com/Horusiath/AkkaDemos/tree/master/cluster-sharding/Demo.Web

We can link it with GraphQL in backend and frontend as well
https://github.com/sangria-graphql/sangria-subscriptions-example
Link with issue #5

Awesome projects that fully support .NET with GraphQL.NET
https://github.com/JacekKosciesza/StarWars


Contrast Security Solution

Solution including workbook, data connector and analytics rules for review.

Requires further refinements.


fix type declaration of private fields in cvat-canvas which are possibly null

Motivation and context
some private fields of classes used in cvat-canvas are type-declared as non-null, whereas they are actually assigned the null value.

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Thank you for the contribution!


highlight server duration on trace summary page

It is helpful to tell at a glance how network latency affected a trace.
This change shows a highlight at the bottom of each span that contains
both client and server timings. The highlight shows what duration of the
span was spent in the server.
I arrived on this highlight style after a few other attempts. It keeps the
span text readable and uses the color for the next depth (which
hopefully makes it more intuitive).
Related to issue #196, but probably not everything envisioned.

@wadey what's your current thinking on this? @eirslett etc?
I recognize this is over 1.5years old. should we pull this in or close it?
(closing in 3 days unless I hear back)

I still think this is a good idea, but I need to re-do it in a way that makes sense for the new UI. I'll close this pull request and open a new one once I have done that (we are still running a very old version of Zipkin internally and we need to update to latest).

ack. thanks for the response!


TempDir RemoveAll cleanup: unlinkat ... application.db: directory not empty

Context
We're trying to eliminate test flakes in this repo. A flake just occurred
--- FAIL: TestSquareSizeIntegrationTest (107.50s)
    square_size_test.go:47: setting up square size integration test
    network.go:48: tearing down testnode
    rpc_client.go:39: stopping tmNode
    rpc_client.go:45: tmNode has stopped
    rpc_client.go:99: removing addrbook.json
    rpc_client.go:99: removing genesis.json
    rpc_client.go:99: removing node_key.json
    rpc_client.go:99: removing priv_validator_key.json
    rpc_client.go:105: removing /tmp/TestSquareSizeIntegrationTest3506[33](https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:34)4195/001/.celestia-app/config
    testing.go:1225: TempDir RemoveAll cleanup: unlinkat /tmp/TestSquareSizeIntegrationTest35063[34](https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:35)195/001/.celestia-app/data/application.db: directory not empty

Occurrences

https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:27
https://github.com/celestiaorg/celestia-app/actions/runs/7189162265/job/19580189334#step:4:30

I would assume the other directories are also not empty, right?
Perhaps we need to apply:
https://github.com/celestiaorg/celestia-app/blob/e0edb4cf0d89a08c46c5634d653e44a77d1d517c/test/util/testnode/rpc_client.go#L39
to the data directory as well

Hmm can try that. So far the flakes are only for .celestia-app/data so I think your suggestion could resolve


Works but does some weird stuff in the background

When i run fancontrol and have this plugin installed. it starts spawning python processes and constantly use 7MB/s or more on the disk. i have added some screenshots.

was for the wrong plugin


Installation instructions may need update

When attempting to install the package per the instructions, I get an error:
ubuntu@ubuntu-xenial:~/go$ go get github.com/p4tin/goaws
package github.com/p4tin/goaws: no buildable Go source files in /home/ubuntu/go/src/github.com/p4tin/goaws

I have very little knowledge of Go, but it looks like it was caused by commit 69bc0b0ebdad036edf8facd57ebf60050c74b002, which removed all the .go files from the project root.
Perhaps the installation instructions need to be updated?

Instead of a "go get", just clone the project and use the command: 'go run app/cmd/goaws.go' to run it in dev mode.  or else you can just use the docker image.