[Unity 2018.3.6f1] Unity freezes when adjusting Fractal Power value in Mandelbulb scene

This is a wonderful demonstration of what Unity is capable of. Thank you for sharing it.
When adjusting the Fractal Power value in the Mandelbulb scene, Unity will freeze. If adjusted in the editor out of play mode, in the editor in play mode, or in a build of the scene, the editor/build will freeze.
I tried only incrementing the Fractal Power on a button hold, and it would run fine until I pressed the button. The value would increment slightly, and the bulb would visually adjust, then the editor/build would freeze.
Also, the script associations in the scene (1 on Main Camera, and 2 on its child object Camera) were broken.

I've just discovered that rotating the main camera in the Mendelbulb scene will cause a similar freeze of the editor.

I guess that's something to do with the amount of computation required to render such scene. I was monitoring my gpu usage while moving camera in the Mendelbulb scene and at the moment of freeze gpu usage rocketed to 100%

@sliterok The same GPU usage spike occurs on my 1080Ti, however I did some further testing and found out that if I disable the FractalMaster script on the camera, move the camera coordinates away from where it is located in the scene and re-enable it, the crash in editor also occurs.

Oddly enough, Unity will still exit just fine using the X in the top left to close the application without need for a force close via task manager.
I've been looking at the Fractal Compute Shader code to see if there was anything that stood out as something that could be cleaned up, but I've only just begun learning shader programming, so I don't think I'm the man for the job.

I've added a max march step count to the mandelbulb shader, which will hopefully resolve this. Please let me know if it's still crashing and I'll reopen the issue.

Hello Seb and others. I am having a similar problem. I have a compute shader under unity which is helping me to calculate some data to acelerate marching shadows. In the moment I increase the internal loops a little bit the compute is not slower. It just gets frozen. Do you know if there is a limit in the internal loops in a shader or maybe a limit in time or something. Its really hard to debug the problem. Thanks a lot!! :)


[xmr] Error(s) refreshing network stats: One or more errors occurred.

Description
been running xmr pool for almost 3 days  but recently I could see some error message from pool log
Steps to Reproduce
1 - Setup XMR main chain
2 - Connect Clients on MiningCore.
3 - Wait for blocks
Expected behavior
no error showing in pool log
Actual behavior
[What actually happens]
not sure whats happening here,
Reproduces how often
this error will show up every 2 - 3  hour
[What percentage of the time does it reproduce?]
Version
v 3.0
Additional Information
##error log:
[2018-10-07 18:17:26.0362] [W] [xmr] Error(s) refreshing network stats: One or more errors occurred. (Unexpected character encountered while parsing value: <. Path '', line 0, position 0.) (Code -500)
[2018-10-07 18:17:26.0362] [E] [xmr] System.NullReferenceException: Object reference not set to an instance of an object.
at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186 System.NullReferenceException: Object reference not set to an instance of an object.
at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186    at MiningCore.Blockchain.Monero.MoneroJobManager.UpdateNetworkStatsAsync() in /userA/miningcore/src/MiningCore/Blockchain/Monero/MoneroJobManager.cs:line 186
###xmr config
{
"id": "xmr",
"enabled": true,
"coin": {
"type": "XMR"
},
"hasLegacyDaemon": false,
"enableInternalStratum": false,
"externalStratums": [
{
"url": "tcp://<IP_ADDRESS>:6000",
"topic": "Monero"
}
],
"address": "45P3tNGKfBTR2Kt7wtz9zHZrpt6Yg3RaDPpeF88TJYU14Q5sYBTHWucKPsCTpShRosgp7wyjzXHqZTRgaCuCPR6kHDgiQVz",
"rewardRecipients": [
{
"address": "45P3tNGKfBTR2Kt7wtz9zHZrpt6Yg3RaDPpeF88TJYU14Q5sYBTHWucKPsCTpShRosgp7wyjzXHqZTRgaCuCPR6kHDgiQVz",
"percentage": 0.75
}
],
"blockRefreshInterval": 500,
"jobRebroadcastTimeout": 10,
"clientConnectionTimeout": 600,
"banning": {
"enabled": true,
"time": 600,
"invalidPercent": 50,
"checkThreshold": 50
},
"ports": {
"3092": {
"listenAddress": "<IP_ADDRESS>",
"difficulty": 1,
"name": "ASIC Mining",
"varDiff": {
"minDiff": 1,
"targetTime": 15,
"retargetTime": 90,
"variancePercent": 30
}
}
},
"daemons": [
{
"host": "<IP_ADDRESS>",
"port": 18081,
"user": "user",
"password": "password"
},
{
"host": "<IP_ADDRESS>",
"port": 18082,
"user": "walletuser",
"password": "password",
"category": "wallet"
}
],
"paymentProcessing": {
"enabled": true,
"minimumPayment": 0.1,
"payoutScheme": "PPLNS",
"payoutSchemeConfig": {
"factor": 2
},
"minersPayTxFees": true
}
},

im actually using Latest miningcore  2018 from master . sorry for the typo

miningcore 2018?

yes the one that i clone from master (https://github.com/coinfoundry/miningcore)  few days  ago


Notification image, title and icon color and xxxhdpi icons support

Adds support for:

Notification images (Android and iOS).
Title and icon colour (Android).
Normal + silhouette icons (Android).
xxxhdpi icons in non-scheduled notifications (Android).
Fixes notifications not popping up when at not set (iOS).

Also cleans some unused, duplicated and/or debugging code.

Thanks very much for this! I am actually currently rewriting the Android side quite heavily to allow for interactive notifications. Once that’s pushed I’m sure this can no longer be merged (there are conflicts with master already, according to GitHub).

@EddyVerbruggen Thanks for the quick response. For now, I just generated a tarball for our project, so it's fine if you don't merge it, but I guess it would be easier to incorporate these changes if you add them while you are working on the refactor than if I have to do it later once you are done with that.
Another option would be to merge this now and have another release later once you finish the refactor, with these changes included too.

@EddyVerbruggen JFYI, I have added some more changes to:

Automatically add an image thumbnail on Android that goes away when expanded. See https://developer.android.com/training/notify-user/expanded.
Rename the icon params to icon, silhouetteIcon and thumbnail (as I think the old names (largeIcon) are misleading). This is a breaking change as that also means there's no default value anymore for the "large icon".
Swap the subtitle or title for the body on iOS, as notifications without a body are not displayed.

Once you finish with the changes on Android I could redo this changes if you haven't included them already. Also, let me know if you want me to move some of the changes on iOS to a separated PR, as those could probably be merged already, or if you need help with anything else.

I think I'll have to manually add your changes because my dev version is way off of master unfortunately. I'll cherrypick where I can and add you as a collaborator in package.json. THANKS!

Working in integrating these changes. color has been done, and image is almost done as well. Note that if the image is too large (byte size) an TransactionTooLargeException is thrown that has been documented in this PR. I was able to work around this issue by conditionally resizing the image (if larger than 320px on either axis.


undefined method `tc_profile_url'

Hi,
I'm new with LTI and have been playing with this TP example but I'm getting the following error:
NoMethodError (undefined method `tc_profile_url' for #<IMS::LTI::Models::Messages::BasicLTILaunchRequest:0x007f85e82bbdd8>):
  ims-lti (2.0.0.beta.41) lib/ims/lti/models/messages/message.rb:178:in `method_missing'
  ims-lti (2.0.0.beta.41) lib/ims/lti/services/tool_proxy_registration_service.rb:11:in `tool_consumer_profile'
  /Users/rrodriguez/.rvm/gems/ruby-2.1.6@lti/bundler/gems/rails_lti2_provider-42ea6bad1c94/lib/rails_lti2_provider/tool_proxy_registration.rb:12:in `initialize'
  /Users/rrodriguez/.rvm/gems/ruby-2.1.6@lti/bundler/gems/rails_lti2_provider-42ea6bad1c94/lib/rails_lti2_provider/controller_helpers.rb:19:in `new'
  /Users/rrodriguez/.rvm/gems/ruby-2.1.6@lti/bundler/gems/rails_lti2_provider-42ea6bad1c94/lib/rails_lti2_provider/controller_helpers.rb:19:in `registration_request'
  activesupport (4.1.6) lib/active_support/callbacks.rb:424:in `block in make_lambda'
  activesupport (4.1.6) lib/active_support/callbacks.rb:143:in `call'

I have tried with lti_tool_consumer_example as consumer and the IMS LTI Tool Consumer emulator. I'm using the /register endpoint.
Looks like it is some method missing in the ims-lti gem.
Any ideas?
Thanks!

I'm getting the same error. Using the following repos and http://localhost:3000/register as the Provider launch url being submitted to the consumer tool. Any ideas on fixing the error?

https://github.com/instructure/lti_tool_provider_example
https://github.com/instructure/lti_tool_consumer_example

I am getting the same error too

same


Vijay Mehrotra ..Solved the issue number #130455.

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Thanks for your interest in contributing to Flutter. Unfortunately, since 1) the name of the asset manifest file used for web will likely change again very soon^1 and 2) this PR is missing a description, tests, and CLA, I am closing this PR.


Greek language assets

Added files for Greek language. This includes the needed words from Research:Revision scoring as a service/Word lists/el and some extra ones.

Codecov Report

Merging #317 into master will increase coverage by 0.06%.
The diff coverage is 95.34%.

@@           Coverage Diff            @@
##           master   #317      +/-   ##
========================================
+ Coverage   84.94%    85%   +0.06%
========================================
  Files         231    233       +2
  Lines        7394   7437      +43
========================================
+ Hits         6281   6322      +41
- Misses       1113   1115       +2

Impacted Files
Coverage Δ

revscoring/languages/tests/test_greek.py
100% <100%> (ø)

revscoring/languages/greek.py
86.66% <86.66%> (ø)

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 ebf4f81...d21ce45. Read the comment docs.

Thanks for doing this


Rendering of placeholders in edit view is broken

I'm using the following structure in a project:
{% block content %}

        {% placeholder intro %}

                {% placeholder content %}

                    {% placeholder footnotes %}

            {% placeholder internal-links %}
            {% placeholder external-links %}
            {% placeholder ads %}

{% endblock content %}

Sadly neither the placeholder content nor the placeholder footer show up in the edit view.

I think it is related to the css-styles of .article-content and #sidebar. Below are the rendered root-tags of the placeholders.

.article-content {
margin-top: 60px;
position: relative;
padding-right: 25px;
clear: both;
}

#sidebar {
width: 188px;
float: left;
margin-top: -4px;
margin-right: -214px;
margin-left: 26px;
}

I'm using
Django==1.6.5
django-cms==3.0.3

Postponing after 3.1 as it requires rethinking of structure mode

hi .. i kinda have the same bug i think
i have a base template with placeholder1
and a default template with show_placeholder (which shows the header) and placeholder2
now when i switch to the structure view of any page based on the default template, the cms sometimes displays the placeholder1, but most of the times it does not and static/cms/js/modules/cms.structureboard.js fails because the dragarea is not rendered and thus the positioning of placeholders is fucked up

i found a quick fix tho - which even cant hurt having it in the vanilla code:
in cms.structureboard.js _resizeBoard() below
area = $('.cms_dragarea-' + id);
add this line:
if (area.length == 0) return;
this way the editor is usable again .. im just not able to edit stuff in the referenced header placeholder, but this i can do by switching to the header page .. so its still possible

This has been addressed in 3.2 :)


Onchain payment never marked paid once lightning invoice is cleaned up

Reported here: https://github.com/lnbits/satspay/issues/74
Depends on PR: https://github.com/lnbits/satspay/pull/73 (fix will be merged and released after v1.0 is out)

closes #74


Unable to open default browser from WSL

Windows Version
Microsoft Windows [Version 10.0.19045.3324]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu 20.04
Other Software
aws-cli/2.2.17 Python/3.8.8 Linux/<IP_ADDRESS>-microsoft-standard-WSL2 exe/x86_64.ubuntu.20 prompt/off
Repro Steps
Run aws sso login
Expected Behavior
Expecting default browser to open
Actual Behavior
The terminal outputs:
Command '/usr/bin/x-www-browser' requires the chromium snap to be installed.
Please install it with:

snap install chromium

Running snap install chromium gives:
error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory

Diagnostic Logs
No response

Turns out uninstalling chromium did the trick:
sudo apt-get purge chromium-browser
rm -rf ~/.config/chromium/


Redefined fields extension to allow filtering on any property in document

The fields extension provides the ability to specify individual fields that should be included or excluded but only applied to properties, and also defined a boolean to specify whether geometry should be included as well.
The new definition allows you to specify any field in the JSON document (including root-level fields), but requires that you provide the full JSON path.  Eg, to include only id, bbox, cloud cover, and datetime, you would populate the include array with id,bbox,properties.eo:cloud_cover,properties.datetime.

@matthewhanson and @hgs-msmith + @hgs-truthe01 - could you all review this? Michael + Tim - we talked about this on our last call, out of the discussion on #383. Matt and Josh both felt this worked well for them, but we definitely wanted your input on it.

@cholmes I can see the benefit of including the full path here. I do worry that it is not in sync with the query extension now. Perhaps we should concede that one as well and use properties.{name} there as well.

@hgs-truthe01 We did talk about that (not being in sync with the query extension). I'm ok with them being different.  For fields, it really is best to be able to specify any field, property or not, for inclusion or exclusion, so the property. is necessary.
However, for the query extension the properties are the fields that users will want to query on. There are some exceptions at the top level (id, geometry, maybe assets), but these are typically objects not strings or numbers, so the standard querying isn't defined. So instead for those special fields we have additional search terms (e.g., intersects for querying geometry), and don't need the query search term to include them.
I'm good with this PR, any other opinions?

@matthewhanson - you want to merge this when you're ready? Just want to be sure it doesn't conflict with your other PR. Sorry for not getting this merged sooner.

Thanks, merging and will resolve conflicts with other PR


Question: batch or asynchronous uploading of apk in android publisher api.

I need to upload few apk files(30mb each) of one application using publishing api and update track. I want to upload it asynchronously or using batch request to get less request time. Is it possible?
I use concurrent ruby for asynchronous requests, but it does not give me improvement of time.
 def update_apk(apk_list, track)
    version_codes = apk_list.map do |path|
      promise {
        log("updating apk #{path}")
        @android_publisher.upload_apk(
            @package_name,
            @current_edit.id,
            upload_source: path
        ).version_code
      }
    end

   zip(*version_codes).then do |vc|
      log("updating tracks with version codes: #{vc}")
      @android_publisher.update_track(
          @package_name,
          @current_edit.id,
          track,
          Androidpublisher::Track.new(track: track, version_codes: vc)
      )
    end
  end

Async uploads are not supported by this client library. There's nothing in the android publisher API for batching either.


Java Script Error

JavaScript Error TypeError Cannot Read the properties of undefined (hide) @ Browser Window

It looks like this is a duplicate of #389

@bike-bill I agree, this is at least related. @Prakash71322 hope you don't mind if I close here. If this isn't solved with the fix in the other issue, we can reopen here.


RCON not found for server ...

Installed the latest version of the Panel. Followed all the instructions in the documentation. However, when a server is added, the panel displays the message: RCON not found for server <ip>:<port>. The server info will be pulled without RCON, meaning that player and advanced information modals will not be shown. Consider using our official plugin to get more information and features.
However, the RCON on the server is functioning perfectly, as confirmed through several RCON clients. I have tested it without any issues, even using the same IP. I am unsure where the problem lies. The CSS-Plugin was also installed on the server, but it did not resolve the issue.

Hey, are you still facing this error? can you open a discord thread in our discord server?


added cleaned chunk 1

This is the clean version of chunk 1 for যা দেখেছি যা বুঝেছি যা করেছি (#12 )

Please check the changes. See if they are necessary, if so then please change it, otherwise send pr

Fixed all issues that you listed. Found more issues and fixed them as well.
I have uploaded a complete list of corrections to our Wiki.


Disable a rule entirely

Currently it's possible to do something like
groups:
- name: rules
  rules:
  - alert: test
    expr: foo{}
  - alert: testDisable
    override: [test]
    expr: foo{bar="baz"}
    enabled: false

and you'll get one rule with foo{bar!="baz"}.
But I'd like to be able to write something like
groups:
- name: rules
  rules:
  - alert: test
    expr: foo{}
  - alert: testDisable
    override: [test]
    enabled: false

and have the rule be removed from the output completely. Currently running alert-overrider on this panics:
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running]:
main.extractFilterExpressions({0x0, 0x0})
        /Users/marks.polakovs@couchbase.com/code/prometheus-alert-overrider/main.go:96 +0x68
main.NegateFilterExpression({0x0, 0x1114385})
        /Users/marks.polakovs@couchbase.com/code/prometheus-alert-overrider/main.go:121 +0x25
main.AlertFile.Override({{0xc000098840, 0xc0000c5f70, 0x10405f1}}, {{0xc0000b0600, 0xb}, {0x0, 0x0}, {0x0, 0x0}, {0x0, ...}, ...})
        /Users/marks.polakovs@couchbase.com/code/prometheus-alert-overrider/main.go:70 +0x19f
main.main()
        /Users/marks.polakovs@couchbase.com/code/prometheus-alert-overrider/main.go:201 +0x385

Is there a way to disable a rule completely? If not I could try writing a PR for it.

What would be the case for this? Isn't removing the rule entirely a better solution?
Your suggestion is to remove the rule entirely when no expression will be specified, correct? I'm okay with that if you have a relevant case for it.


creating categories  have error

whenever i create new categories it generates an error Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_general_ci,IMPLICIT) for operation '=' after error happens whenever i travel back category  is created

https://github.com/bagisto/bagisto/issues/2807


allow custom classes to be specified in config

Allows custom ServiceContainer and WorkerContext classes to be specified via config values
Deprecates the kwarg interface for specifying these because they cannot be used in conjunction with the nameko run command

@davidszotten this is ready for a round of review when you have a chance

curious what your use-case for replacing these is

Our use-case is for a custom ServiceContainer class.
We deploy our services to multiple regions and need slightly different behaviour in each, but don't want to maintain different branches or codebases. For example, it's only valid to write to the database in one region.
The custom container supports an "entrypoint blacklist", a configuration level way to disable certain entrypoints, so we can deploy the same codebase in all regions and tweak the behaviour via config.

ok. do you also use a custom worker context? (does that definitely need to be configurable. ofs used that to transition to nameko, but have you come across use-cases beyond that?)

We don't have a custom WorkerContext, but we can't get rid of it without another change:
WorkerContext.context_keys specifies which bits of the context data get passed from call to call, and the only way to set it is with a subclass. It's an odd API though. I'm not sure why we need a distinction between data on the worker context and context_data, which is the subset that matches the keys.

@davidszotten as discussed in the offline meetup, I've removed WorkerContext.context_keys and the ability to (directly) customise the worker context class.

@davidszotten this is ready for another round

👍


[BUG/Help] window,cpu版本使用chatglm-6b-int4提示错误：AttributeError: 'NoneType' object has no attribute 'int4WeightExtractionFloat'

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
AttributeError: 'NoneType' object has no attribute 'int4WeightExtractionFloat'
Expected Behavior
No response
Steps To Reproduce

Environment
- OS:windows 10
- Python:3.9
- Transformers:4.27.1
- PyTorch:2.0.0
- CUDA Support (`python -c "import torch; print(torch.cuda.is_available())"`) :

Anything else?
No response

解决了吗


Change the favicon

The current favicon is from Chripy, I think the instructions here will help: https://chirpy.cotes.page/posts/customize-the-favicon/

Addressed in 6dc94b5?


Translated using Weblate (Galician)

Currently translated at 14.1% (19 of 134 strings)
Also added Japanese.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/347/
Build Log
last 5 lines
[...truncated 42 lines...]
   at hudson.model.Executor.run(Executor.java:240)
[ANALYSIS-COLLECTOR] Skipping publisher since build result is FAILURE
Notifying upstream projects of job completion
Setting status of 54174785f0bad4b1dac7ca673d5c62e8faf2d137 to FAILURE with url http://jenkins.terasology.org/job/TerasologyPRs/347/ and message: Merged build finished.

Uh oh, something went wrong with the build. Need to check on that


that should do it

Codecov Report

Merging #307 (ac16563) into main (a63625a) will decrease coverage by 10.09%.
The diff coverage is 61.53%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@             Coverage Diff             @@
##             main     #307       +/-   ##
===========================================
- Coverage   80.82%   70.74%   -10.09%
===========================================
  Files          79       73        -6
  Lines        1747     1702       -45
===========================================
- Hits         1412     1204      -208
- Misses        335      498      +163

Files Changed
Coverage Δ

ext/MPIExt.jl
0.00% <0.00%> (-94.88%)
:arrow_down:

src/evaluation/benchmark.jl
56.09% <93.75%> (+4.19%)
:arrow_up:

src/traits/parallelize.jl
75.00% <100.00%> (ø)

... and 31 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Managing compute engine heap

As documented here:
https://docs.sonarqube.org/display/SONAR/Java+Process+Memory
This is just simply enabling setting heap parameters for CE heap (for web and ES it was already there).

Hi @dejo1307 This PR needs spec tests for it to be merged.


handleBaseTag dies hard when any of the Parse fails.

https://github.com/PuerkitoBio/gocrawl/blob/639cda895f34579b33a74d068cf4c69bb1777248/worker.go#L361
It does not check errors.

Indeed, thanks for reporting.

Thanks for the quick fix!


[RAINCATCH-1276] Update documentation and example to include JWT strategy

Motivation
There is no documentation that covers token based authentication in PassportJS module. Our example does not cover this either. We need to provide information on how we use token based authentication.
Description
Update the documentation and the example to provide information on token based authentication and the JWT Strategy.
Progress

[x] Update documentation
[x] Update README file

Additional Notes
Related JIRA - https://issues.jboss.org/browse/RAINCATCH-1276

@JameelB We will need to review existing passport docs to include that as well.

Changes Unknown when pulling 016acdb3506d27c766af1664b210c735c9d67ccb on JameelB:RAINCATCH-1276 into ** on feedhenry-raincatcher:master**.

Changes Unknown when pulling 016acdb3506d27c766af1664b210c735c9d67ccb on JameelB:RAINCATCH-1276 into ** on feedhenry-raincatcher:master**.

Changes Unknown when pulling 1d25177fc7ea41a86a709ed8b488aae67a14a5e0 on JameelB:RAINCATCH-1276 into ** on feedhenry-raincatcher:master**.


Add topology sorting

I suggest Kahn's algorithm for topology sorting. (https://en.wikipedia.org/wiki/Topological_sorting)
Please don't hesitate to give honest feedback. (I'm still a novice rustician)

be advised that it already exists as petgraph::algo::toposort - are there important differences?

My bad. Havn't seen the function.
Reject this PR.
I'm going to read and use your solution.
If you're willing to give me feedback on my solution. You're welcome.


Y16 calibration format test

Tracked on [RSDEV-724]
Porting an existing D400 test from Cpp to Python.

Let's also delete the old cpp test file, no need anymore right?

Please remove


Make sure we don't put invalid data into tagmappings table

This adds NOT NULL constraints to a bunch of columns that should never have null-values. Makes it easier to spot mistakes.
https://trello.com/c/7tcrUgcz

:shipit:


what about treeview component with checkbox？

I need a treeview component, could you provide this kind of component? ^_^

Please read the guidelines for posting issues -- this isn't likely to make it in in the short term though.
It should be relatively simple to implement yourself -- try this: https://github.com/chenglou/react-treeview

A tree view implemented using material-ui: https://github.com/helfi92/material-ui-treeview.

It's work in progress: https://material-ui.com/components/tree-view/.

@helfi92 https://github.com/helfi92/material-ui-treeview seems to implement a side nav pattern. Are you using it in this context?

https://firefox-ci-tc.services.mozilla.com/hooks is how I'm using it. What do you mean by side nav pattern?

Ah interesting, thanks, it's used both as a side nav menu and an accordion like component.

I also need a treeview component with checkbox!

@asim47 We track it in #17407.

@oliviertassinari  Thank you.

Ah interesting, thanks, so it's used both as a side nav menu and an accordion like component?

Correct.


Data consumers can easily discover and review metadata for a dataset in cellxgene explorer

Story
Data consumers can easily discover and review metadata for a dataset in cellxgene explorer.
The dataset drawer in cellxgene explorer was designed to share  schema metadata for a dataset. Originally, this included both collection and dataset metadata, but collection metadata was deprecated in v1.1.0 of the schema. The dataset metadata duplicates features in the portal A Collection view which has columns for the most important metadata: Tissue, Assay, Disease, and Organism.
The original design was extended to include singleton categories. There is an open question of whether these values need to be surfaced.
@pablo-gar also reported that the ontology ID for organism is always empty.
The drawer is not discoverable by consumers. No publisher has inquired about "missing" metadata for either case during pre-production reviews. A redesign and user review is required.
UX Design
Design
Prototype

@hthomas-czi - The current UX design separates some ontologies from their labels. For example, PATO (the ontology) is listed separately from the Disease label. Uberon is the ontology for Tissue. What's the rationale for this design in comparison to using a hover for a label to display its ontology or the status quo which has an ontology column:

@brianraymor No good reason. I sketched out two more concepts. What do you think about these?

I prefer the hover for the ontology (when available) which is what we discussed potentially for the left sidebar in the future.

@hthomas-czi - why is organism included with collection information rather than the dataset metadata? Similarly, do you want the other collection links (titled Project Links) to be separated out from the collection information including the DOI link?

@brianraymor Good questions. What do you think about this design?

@hthomas-czi - better, but wouldn't we want to observe the link ordering that we established in collections - so Contact before DOI for example?
If we're including collection Description should we truncate? Some of the descriptions are quite lengthy.
For the dataset metadata, what is the ordering? It looked sorted until Organism was added to the top.

@brianraymor

better, but wouldn't we want to observe the link ordering that we established in collections - so Contact before DOI for example?

Good call.

If we're including collection Description should we truncate? Some of the descriptions are quite lengthy.

Agreed. I'm thinking we could truncate at four lines, but don't have a strong opinion.

For the dataset metadata, what is the ordering? It looked sorted until Organism was added to the top.

I was just following the current ordering but now that you mention it, it does seem to be alphabetical except for "Organism." My best guess is that was considered more important than everything else? I think it makes sense to keep it all alphabetical.

During the June 14 meeting, we reviewed potential ways to improve the discoverability of the dataset drawer:

Open the dataset drawer by default when a user is referred to a CXG from an external site (rather than the cellxgene data portal)
Move the i menu button - perhaps closer to the dataset breadcrumb

No action required at this time.


[5.2] Check for date or other casts when plucking

In reference to #13582, this updates the Eloquent query builder to check for date or other casts when performing a pluck (in addition to get mutators).

Just noticed this is on 5.2 branch. Can you send this to 5.3 when you get a chance? Don't want to break applications out there on 5.2 that aren't expecting this.


samples: google_iot_device: Remove "command line" and replace with config.c

There is no "command line" in Zephyr RTOS. "Command line" which was
used previously is an artifact of a special-purpose, testing target
"native_posix", not portable to any other Zephyr target.
So, instead provide config.c file, where a user can define all needed
application parameters (which previously were passed on "command
line"). As such a file contain credentials, it should be never put
under version control. This commit includes a template file,
config.c.in, which can be copied by a user to config.c, and needed
values filled in.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

Based on the discussion in https://github.com/atigyi/zephyr/issues/3#issuecomment-521633236 , and a prerequisite to getting this sample running on "real" Zephyr device, like qemu_x86 (native_posix is not a real Zephyr device in that regard).

What I'd generally suggest is to completely remove this "command line" handling, i.e. remove code which is so far wrapped in #if 0 in this PR. Then, apparently rename commandline.h to config.h.

Rebased on the latest base branch.
@atigyi, This would be on critical path to https://github.com/atigyi/zephyr/issues/2, please share your feedback.

@atigyi : Ok, so I refactored this based on your comments - effectively, went full on with removing command line parsing, and replaced it with C-based config file, down to references in the code comments. As usual, tested with BOARD=native_posix.
Let me know how that looks.

@atigyi, Pushed a change based on your last round of comments (specifically, copyright header/include in config.c.in).

Please check this comment too.

Please check this link-error comment too.

Ah, right.

Update: don't we miss the following line in the CMakeLists.txt?
configure_file(${APPLICATION_SOURCE_DIR}/src/config.c.in ${APPLICATION_SOURCE_DIR}/src/config.c)

Ok, tested. With the line added above and config.c.in filled in properly

Well, I'm not familiar with that CMake command. In my list, what's needed to be done is:

Before building:
Copy config.c.in to config.c
Fill in actual connection config in config.c

Editing config.c.in directly should be discouraged - this file is under version control, so it's possible to inadvertently commit it with other changes, then push to public or otherwise not-enough-restricted repo, then we have credentials leak.
So you're right that README should be updated, working on that.

So you're right that README should be updated, working on that.

Pushed update as a separate commit, we'll yet need to squash things around later anyway.

Please check this link-error comment too.

Ah, right.

Update: don't we miss the following line in the CMakeLists.txt?
configure_file(${APPLICATION_SOURCE_DIR}/src/config.c.in ${APPLICATION_SOURCE_DIR}/src/config.c)

Ok, tested. With the line added above and config.c.in filled in properly

Well, I'm not familiar with that CMake command. In my list, what's needed to be done is:

Before building:
Copy config.c.in to config.c
Fill in actual connection config in config.c

Editing config.c.in directly should be discouraged - this file is under version control, so it's possible to inadvertently commit it with other changes, then push to public or otherwise not-enough-restricted repo, then we have credentials leak.
So you're right that README should be updated, working on that.

First of all - and after README update - this is now clear and a good solution and I can accept it.
But the .c.in suffix mislead me. .h.in / .c.in file extensions are occupied by the configure_file cmake functionality. First sentence of the description says: "Copy a file to another location and modify its contents." Actually this is the two bullet points mentioned above, but in an automated fashion (which isn't necessarily better).
And about the accidental credentials leak: a new file config.c or a modified existing file config.c.in both are a single step from git-staging (git add or git stage) and then git-commit. Maybe git add is used less frequently. But I don't see significantly larger thread against credentials leak with the manual steps.
Please just consider if this solution is better with auto-copy and fill or manual. I searched for it, no Zephyr sample uses cmake's configure_file so far but internals do.

But the .c.in suffix mislead me. .h.in / .c.in file extensions are occupied by the configure_file cmake functionality.

Ah, I see. And not exactly. ".in" suffix is a well-known convention for "template" files where things needs to be replaced to get the actual file sans ".in". Where possible, replacement happens automatically. Where not, e.g. where user credentials are needed, it needs to be copied and edited by a user. It's universal convention not tied to any tool. CMake just appear to follow well-known naming convention with its own adhoc meaning. Github gives 158 million hits when searching for "config.h.in": https://github.com/search?q=config.h.in&type=Code , and majority of those hits aren't related to CMake.

are a single step from git-staging (git add or git stage) and then git-commit. Maybe git add is used less frequently.

Well, those are 2 steps ;-). "git add" is used much less frequently. How many people process git commits is "git commit -a", which just shoves anything changed into single commit, voila. Running "git add &;lt;file>" is quite a departure from that simple course.

Please just consider if this solution is better with auto-copy and fill or manual. I searched for it, no Zephyr sample uses cmake's configure_file so far but internals do.

I think it's good idea to follow what other samples do and not rely on CMake peculiarities. CMake is quite a recent addition to Zephyr build system. And if it was changed once, it can be changed again, and then CMake-specific features will complicate migration and maintenance.
Also mind that the purpose of this patch is to get rid of the code not supported by target other than native_posix, and move on to other problem precluding it to run on other targets, and not perfectalize configuration handling. It's quite possible that when we get stuff actually working, we'll think: "Oh, we want those params to be set via Kconfig". Or maybe we'll be asked to do that during upstream code review...


W-14775713 | Java 17 runtime compatibility changes

The main work comes from https://github.com/mulesoft/mule-json-module/pull/196 which addresses some Reflective Access issues for the Json Tools library.

@alexandru-babei-softvision, Apologies for the delay, I was reviewing the resource releaser and left some comments, including on parts not modified by you. Please take a look and share your thoughts, especially regarding the interrupted exceptions. The resource releasers aim for best-effort cleanup, so overlooking these exceptions might be an option, yet I'm curious about your perspective. Also, the removal of access-modifying statements caught my attention. Are they deemed unnecessary now, or were they ever?"

We can definitely make some improvements to make the code more maintainable and handle the thread interruption scenarios.
I think it makes sense to quickly catch up anyone reading this who hasn't been fully in the loop with the changes discussed in https://github.com/mulesoft/mule-json-module/pull/196. The short version is that the reflection usage in JSON module with regards to the JSON Tools library was definitely needed before, in order to access the private class members involved in working around the thread leak issue.
Since we wanted to avoid breaking backwards compatibility, which could have involved either replacing the library or deprecating the schema versions supported by the library, we had to come up with several proposals for changing how the library behaves without impacting the rest of the functionality.
We came up with a creative solution, which we also described in a tech spec, where we modify the library classes at compile time during shading, making the class members that we need to change as public and non-final, right before the shader performs package relocation.
You can also see this behaviour being tested in JsonToolsReflectiveAccessTestCase.xml where we load the shaded classes and make sure that the class members are public.
The reflective access test case plays an important role in making sure that the custom shader is always invoked during compilation and that the class members are compatible with the reflective access performed at runtime.

Sorry for my previous question... that's what I get for watching the Pull Request in stages and after two days of watching the first stage I didn't remember the changes seen before.
Approved


Battery unknown

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
if Battery full from a Device, it will displayed unknown. And if Battery low, it will display on.
can it make it display correctly full or low ?
Describe the solution you'd like
see Screenshot
https://ibb.co/LJgtYTh
Describe alternatives you've considered
n/A
Additional context
n/A

It is displayed correctly for me. The condition should show as 'normal' if the battery has sufficient charge. Although I haven't figured out when the status is shown as low in Hassio. A device keeps showing up as 'low' in the Livisi app Reported, but in Hassio he is still on 'nornal'

It is displayed correctly for me. The condition should show as 'normal' if the battery has sufficient charge. Although I haven't figured out when the status is shown as low in Hassio. A device keeps showing up as 'low' in the Livisi app Reported, but in Hassio he is still on 'nornal'

for me it displayed unknown when full. See screenshot.
What for SHC you are use?

I have the same error. I don't get a battery indicator either.
SHC 2.0 with new firmware 8.17 - <IP_ADDRESS>5

Yep, you're right. I broke this with the rewrite. Fixed in 1.4.2


MacOS client app got stuck in the loading screen

Describe the bug
The Mac client app got stuck in the loading screen. User claims that last time it started to work after a few reboots but now nothing works (the same situation is with Portals app that he is currently subscribed to).
Screenshots

Environment (please complete the following information):

OS: MacOS Catalina 10.15.7
Desktop app version (if applicable): 4.2.1

Additional context
App & Node logs
logs.zip

The issue was fixed by logging in as admin (or user with admin privilegies) and running the Mysterium app. The same window pop up asking for the pass to install the helper utility and after writing the pass (this time the admin pass, the user has managed to enter the app interface.)
Update: _This is a workaround for Mac users, logged as a normal user without administration privileges, that got stuck in the initial screen asking to install the helper and looping there for ever. _
1. Open a Terminal Window
2. su - admin  (where “admin” is a account with Administration privileges
3. You will be asked for the “admin” pass. Input it
4. sudo /Applications/MysteriumVPN.app/Contents/MacOS/MysteriumVPN
5. You will be asked for the “admin” pass. Input it
6. The App should start now


Update DistributionInfo.json

Making adjustments for SLES-12 & SLES-15 as well as adding Tumbleweed.

Closing in favor of https://github.com/microsoft/WSL/pull/9562 - thanks!


⚠ Bofrost.fr has degraded performance

In 26ca485, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1308 ms

Resolved: Bofrost.fr performance has improved in 3c352c1 after 7 minutes.


Checking process blocked mysterious

After issue npm-check, the process start checking, but blocked on random dependency.
e.g.

$ npm-check
[] Checking registry for helmet - complete.

Checking always...
Maybe it's not my network problem.

Interesting, thanks for creating an issue @micooz.
The one it is listing isn't necessarily the one it is blocked on because all of the network connections are run at once.

Are you able to share your package.json so I can try it?
Are you just using node modules from the public registry or are you using a private registry, github, or something else?

Hi, @dylang. I'm using another public registry, but after I change it to npm official, the process blocked again.
Here is my package.json:
package.txt
Sorry for github don’t support json file type. Please change it to .json manually.

I'm able to use your package.json file without problems.

What version of node are you using?
How's your internet connection?
What was the other public registry you were using?

Hello, @dylang

My node version is v5.9.1
I'm China, internet connection broken from time to time, but shadowsocks is a workaround
I'm using registry=https://registry.npm.taobao.org/ to speed up my npm process

Great, thanks @micooz for all that information.
Next version I'll added a concurrency check so not to open so many connections at the same time. Hopefully that will help.


Documentation for asynchronously uploading large videos (Duration: 0.5 ~ 140 sec)

Currently available in Japanese. Translation required.

Qiita - TwitterAPIのアップロード系エンドポイントまとめ (140秒動画対応)

These features are internally supported


BFS

Breadth First Search algorithm.
Referencing #4

The same issue of #11. Try to fix those issues to got the pull request merged in.


Some way to edit documentation page configuration within the hyde.yml file

Something I realize now that we're missing is a way to edit documentation settings from the Yaml configuration file. Not sure what the best way to do this is though.

Asking ChatGPT:
GPT Prompt
I have a framework which provides a set of config files as follows:
config/hyde.php
config/docs.php
config/markdown.php

I also have a feature which allows the user to define the settings in config/hyde.php in a Yaml file stored as hyde.yml. I am now looking to allow the settings in the config/docs.php file in the hyde.yml file. What would be the most elegant way to incorporate this?

Response
One possible solution is to use a nested structure in the Yaml file, where each config file is represented by a key and its settings are represented by nested keys. For example:
hyde:
  setting1: value1
  setting2: value2
docs:
  setting3: value3
  setting4: value4
markdown:
  setting5: value5

Follow up prompt:
I thought of that too, but the addition must be fully backwards compatible.

In that case, you could provide a default value for the docs key in the hyde.yml file, which will only be used if the user explicitly defines it. For example:
hyde:
  setting1: value1
  setting2: value2
  docs:
    setting3: value3
    setting4: value4
markdown:
  setting5: value5

Note: It doesn't seem like it understood my request.

Another alternative is to have a docs.yml file but at that point we lose the whole point with having a single easily modifiable file. So I think a top-level docs entry would be best. Or possible, a special prefix to distinguish it. Sadly, I closed GPT and the history feature is broken. But I'll start hacking on this, the prefix is easy to change later.

Another alternative is to have a docs.yml file but at that point we lose the whole point with having a single easily modifiable file. So I think a top-level docs entry would be best. Or possible, a special prefix to distinguish it. Sadly, I closed GPT and the history feature is broken. But I'll start hacking on this, the prefix is easy to change later.

I feel like it's a bit "hacky" to add an extra key, which is not mapped to one in the hyde.php config file. An alternative that would be compatible, is to support all configuration options by checking if the entire file is indented.
So a file like this:
setting1: value1
setting2: value2

Would have the current behaviour
But a file like this:
hyde:
  setting1: value1
  setting2: value2

would allow for more options. For example
hyde:
  setting1: value1
  setting2: value2
docs:
  setting3: value3
  setting4: value4
markdown:
  setting5: value5

Depending on the underlying implementation this could be automatically enabled for any arbitrary config file, even allowing vendor configs to be used. Maybe by checking the top-level key with the global root config keys.

First implementation POC will probably be just checking if a hyde key is set in the top level. Next step is to support other options, such as only providing the docs config.


Improve authentication and logout request input params API

This PR is made of:

an AuthRequest refactoring extracted from #307
a LogoutRequest refactoring picked from my own fork (for which I hadn't provided any PR yet because it was relying on other changes)

Benefits of this refactoring:

it polishes the AuthnRequest, LogoutRequest and Auth APIs: all those overridings were honestly cluttering the API and they were not easily extensible
it improves library evolution: any future evolution of this library which requires to add further input parameters to the AuthnRequest and LogoutRequest generation process, may simply extend AuthnRequestParams and LogoutRequestParams without the need to further touch the API of  AuthnRequest, LogoutRequest and Auth classes (or to provide even more overridings); this allows, for instance, to implement #329 by simply adding a new property to AuthnRequestParams (and of course adjust the generation process) without the need to provide new overloadings
it improves extensibility: in combination with the postProcessXml mechanism introduced in #321 (*), any consumer application which needs to extend this library, may pass to AuthnRequest and LogoutRequest constructors a proper input params extension, which will also be passed to postProcessXml, so that an overriding of the latter will allow for proper XML manipulation and/or extension based on the actual custom input params
further Auth extensibility improvement, which leverages this rafactoring, can be provided: I already anticipated he idea in https://github.com/onelogin/java-saml/issues/265#issuecomment-812631694 and I may provide a separate PR for that if this is accepted and merge

(*) Please note that this PR also brings a change in postProcessXml API for AuthnRequest and LogoutRequest, letting it receive the input parameters as well. I think this is fine since the postProcessXml has not been released yet, so we should still be on time for this.

Just a clarification: the change is 100% backward compatible: all those Auth.login, Auth.logout, AuthnRequest and LogoutRequest constructor overloadings have been deprecated (to ease migration), not removed. You may then consider their removal sooner or later, depending on requirements.


credentials_json is not stored in the .env file

credentials_json is not stored in the .env file
When I use
meltano config target-bigquery set credentials_json [value],
it isn't storing the credentials in the .env file. Instead, it is plain text.
Desired outcome:

Create .env if it doesn't exist
Store it credentials_json in the .env file.

I dont think I can fix this on my side. Maybe it needs a PR to the hub repo


feat(GatewayThreadMemberUpdateDispatchData): add guild_id extra field

Please describe the changes this PR makes and why it should be merged:
Reference Discord API Docs PRs or commits:

https://github.com/discord/discord-api-docs/pull/4228

Upstream PR merged


Request Builder

Previously, I had attempted to make the code more functional by constructing the request only when needed instead of using RestRequest as a wrapper around URLRequest as it was pre-api update. It turns out the requests using QueryItems were passing because the request in the callback was different from the one actually sent.
Since were already using a class and storing several reference types, the reference model makes more sense. I have reverted to the previous system to address this issue.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@bcfe1ca). Click here to learn what that means.
The diff coverage is 52.47%.

@@            Coverage Diff            @@
##             master       #6   +/-   ##
=========================================
  Coverage          ?   44.63%
=========================================
  Files             ?        7
  Lines             ?      587
  Branches          ?        0
=========================================
  Hits              ?      262
  Misses            ?      325
  Partials          ?        0

Flag
Coverage Δ

#SwiftyRequest
44.63% <52.47%> (?)

Impacted Files
Coverage Δ

Sources/SwiftyRequest/RestRequest.swift
57.34% <52.47%> (ø)

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 bcfe1ca...97cd51a. Read the comment docs.


Role based done

…ing, students can only see their related things and proffessors cannot access courses but can see all students.

@SA-10125 please give me the log-in credentials you used on your system for the student management website

!bounty 400

!bounty 300


Overhaul library database for ML and other analysis procedures

I kind of backed us into a corner with the way the library database is set up because it is all clean processed spectra. Many machine learning procedures would benefit from the use of unclean spectra in the library and some matching procedures might perform better too. It could also be that we want to allow people to propose a "better cleaned" version of the library spectra in the app. We would need to have the raw spectra loaded somewhere in the app to pull that off. Thinking about a new library structure which has Raw_Spectra, Clean_Spectra, Sample_ID, and Peak_Number columns. If we rewrite some of the code we can get around the current need to have a peaks only version of the library (which is creating some duplication of data), by having the peak number only correspond to the peak locations and put NA where there is no peak. It would be nice if we could then create a tool in Open Specy where people can adjust the "Clean_Spectra" values for the matches by reprocessing the "Raw_Spectra" column.  The adjustments would be sent to MongoDB and we would need to review them. I also want to add the preprocessing parameters we used from Open Specy to clean the spectra into the metadata. The metadata view right now is pretty bad when there is too much metadata. Perhaps we can add some onhover information or something else for the metadata so that the metadata doesn't bleed across the screen.

[x] Create new library format.
[ ] Integrate into shiny app and function workflows in app.
[ ] Improve metadata display when there is a lot of metadata.
[ ] Develop a user cleaning tool for users to clean the database.
[ ] Integrate a mongodb alert system.

Check out these resources for improving the metadata. They will join CAS numbers with common names of many materials.
https://docs.openrefine.org/manual/wikidata
https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine

I really like the idea of making the raw spectra a part of the Open Specy library. But maybe we can get around changing the current library structure too much. Although MongoDB certainly has many advantages, migrating the library would mean:

lots of changes to the current code base that will probably break something
an extra load of work to keep the old structure alive until the majority of package users has switched to the new version
the DB architecture will make off-line use much more difficult

In my opinion, I wouldn't call it duplication of data but rather modularization :wink: In it's current form, package users can only download the library they need and both package and app users might save some computation power if cleaned and raw spectra are not loaded simultaneously.
Having said this, I'd rather suggest adding the raw spectra as separate library files (raman_raw.rds and ftir_raw.rds) to OSF and supplement the metadata rds files with information on the cleaning parameters. The dropdown radio buttons under "Identify Spectrum" would then get an extra option for the raw spectra.
What do you think?

Hey Zacharias,
Yeah, that makes sense to me and sounds like a good workflow for adding the
raw spectrum into our current workflow. I will need to look into how raw
spectrum searches are best conducted. I know that they can produce a ton of
unexpected matches when using correlations because it fits more to the
baseline than it does to the peaks. However, that kind of fit may be what
someone wants for assessing a match to a fluorescence signal.
Warm Regards,
Win
On Wed, May 26, 2021 at 8:14 AM Zacharias Steinmetz <
@.***> wrote:

I really like the idea of making the raw spectra a part of the Open Specy
library. But maybe we can get around changing the current library structure
too much. Although MongoDB certainly has many advantages, migrating the
library would mean:

lots of changes to the current code base that will probably break
something
an extra load of work to keep the old structure alive until the
majority of package users has switched to the new version
the DB architecture will make off-line use much more difficult

In my opinion, I wouldn't call it duplication of data but rather
modularization 😉 In it's current form, package users can only download
the library they need and both package and app users might save some
computation power if cleaned and raw spectra are not loaded simultaneously.
Having said this, I'd rather suggest adding the raw spectra as separate
library files (raman_raw.rds and ftir_raw.rds) to OSF and supplement the
metadata rds files with information on the cleaning parameters. The
dropdown radio buttons under "Identify Spectrum" would then get an extra
option for the raw spectra.
What do you think?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy/issues/80#issuecomment-848855936,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU4JO6VH42OAHQA64VDTPUF7BANCNFSM45A6CFJQ
.

--
´¯·.¸¸.·´¯·.´¯·.¸¸.·´¯ツ ------------------------------
Win Cowger
PhD Candidate, Environmental Sciences: Soil and Water
University of California, Riverside
NSF Graduate Research Fellow
Research Advisor to 5 Gyres https://www.5gyres.org/advisors/
Data Advisor to Let's Do It World https://www.letsdoitworld.org/
Contact Info
515-298-3869  | @.***
Websites
www.openspecy.org
www.wincowger.com
http://andrewgray.ucr.edu/people/wcowger.html

What about limiting matches from raw data to peaks only?

I'm not sure I have seen that used in other software so I don't know how
well it would be understood by the user. Do you have any examples of that
type of reference database design?
On Fri, May 28, 2021, 12:40 AM Zacharias Steinmetz @.***>
wrote:

What about limiting matches from raw data to peaks only?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy/issues/80#issuecomment-850218561,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJUYE3CXYVUQXDEQ2Q33TP5CHJANCNFSM45A6CFJQ
.

No .. it was just an idea.

Oh ok yeah, definitely something to think about though.
On Tue, Jun 1, 2021, 12:02 AM Zacharias Steinmetz @.***>
wrote:

No .. it was just an idea.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy/issues/80#issuecomment-851877877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJUZI3QY6MMEPEDTT7DLTQSAZRANCNFSM45A6CFJQ
.

I recently noticed that the Chabuka library still has some CO2 signals in it. Definitely worth taking another look at to clean up a little more when we go back through.

Moving this to the top of my list now, it is the most requested feature from users and I think it will improve the accuracy of the tool. Might merge with #96 too so that we can speed up the analysis simultaneously.

The first task is done, a new dataset has been added to the library database. The raw format is the most similar form of metadata and spectra to the raw datasets as I can currently get it. Next, I need to clean up that raw format into something which is more machine learning readable.

The first task is done, a new dataset has been added to the library database. The raw format is the most similar form of metadata and spectra to the raw datasets as I can currently get it. Next, I need to clean up that raw format into something which is more machine learning readable.

@ardcarvalho The dataset we spoke about is mostly ready now.

The first task is done, a new dataset has been added to the library database.
Just to confirm that these new libraries are not yet downloaded with  get_lib(), right?

Just to confirm that these new libraries are not yet available through get_lib(), right?

Nope, they shouldn't. Only files that fit the pattern below are downloaded:
https://github.com/wincowgerDEV/OpenSpecy/blob/b5a89a3a35482f282761f6b5b951b7f89576f59a/R/manage_lib.R#L105-L110
Maybe we should put some more thought into how we best manage the library files in the future in order not to mess with the local installations of people. Spontaneously, I could imagine

Adding a version tag to the files and make get_lib() download the latest/a specific version that fits the package installation.
Putting new library files into a new folder with a new OSF node key and we just switch out that key once we want the people to use the new library together with a new package version.

What do you think? My current preference would be option 2 but I may have not thought it through yet.

Only files that fit the pattern below are downloaded:

Ah, thanks. So, if I understood it correctly, it's basically due to the "raw" in the file name?

What do you think? My current preference would be option 2 but I may have not thought it through yet.

Changing the library implies in changing the package version?
If functions are affected by a new library - not sure it's the case - I would go for a possibility that allow a lib version that fits package installation (option 1, I guess).

Ah, thanks. So, if I understood it correctly, it's basically due to the "raw" in the file name?

Yes, exactly.

Changing the library implies in changing the package version?
If functions are affected by a new library - not sure it's the case - I would go for a possibility that allow a lib version that fits package installation (option 1, I guess).

It depends on the kind of change. If the table structure is changed, we might need to adapt the package code accordingly. If just some new spectra are added, the older package versions should work just fine.
Option 2 would also allow us to link specific library and package versions with one another (using different OSF nodes). But it could make the file handling easier than with option 1.

Great discussion. I've been thinking about this too. I'm trying to figure
out what the best strategy will be in the future if there are rapidly
expanding libraries. I'm thinking once we get this ml model running for
classification we actually won't need to have people download the libraries
any more. We can just have them download individual spectra that they want
to look at when they want to look at it. It could make the tool a lot
lighter on folks devices and make the database query faster. The drawback
would be is they couldn't easily use it offline.
On Wed, Dec 15, 2021, 9:15 AM Zacharias Steinmetz @.***>
wrote:

Ah, thanks. So, if I understood it correctly, it's basically due to the
"raw" in the file name?
Yes, exactly.
Changing the library implies in changing the package version?
If functions are affected by a new library - not sure it's the case - I
would go for a possibility that allow a lib version that fits package
installation (option 1, I guess).
It depends on the kind of change. If the table structure is changed, we
might need to adapt the package code accordingly. If just some new spectra
are added, the older package versions should work just fine.
Option 2 would also allow us to link specific library and package versions
with one another (using different OSF nodes). But it could make the file
handling easier than with option 1.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/wincowgerDEV/OpenSpecy/issues/80#issuecomment-994890100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGMUJU5AENL7LLPYKCIVM4DURCWKLANCNFSM45A6CFJQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Fix UI:select_menu_item

#381

@willothy @ThePrimeagen what do you think, guys?

so i have accidentally done some of these works.  i didn't realize about this.  so we are going to have some issues.
i am trying to think through the split mappings and select options, if you want to make the change and then update the pr i am glad to look through things.

@ThePrimeagen Now it only fixes the UI:select_menu_item behavior. I'm not sure if I'll have time to work on the mappings. So you can merge this small change right now

pr is out of date.  issue already resolved

issue already resolved

w8, what? Problem solved? With what? I think the problem still occurs, are you sure the behavior I was talking about here is fixed?
https://github.com/ThePrimeagen/harpoon/pull/392#issuecomment-1848697502

^ not resolved, split mappings still do not work without this fix. The menu needs to be closed before the item is selected.


[BUG] User has system:admin/system_index permission, but cannot search documents in the custom system index.

What is the bug?
I've set the permission system:admin/system_index on internal_index_manager role for reading the custom system index.
The user (binding internal_index_manager role) can write documents and the _search API works, but it cannot search documents (no hit items).
Only super admin can search documents.
Is this by design? If it was intentional, I wonder the reason.
How can one reproduce the bug?
config
plugins.security.system_indices.enabled: true
plugins.security.system_indices.permission.enabled: true
plugins.security.system_indices.indices: [".my-system-index"]

role
internal_index_manager:
  reserved: true
  hidden: true
  description: ""
  index_permissions:
    - index_patterns:
        - ".my-system-index"
      allowed_actions:
        - "*"
        - "system:admin/system_index"

user
manager:
  hash: "{hash}"
  reserved: true
  opendistro_security_roles:
    - "internal_index_manager"
  description: ""

CAT indices
health status index                  uuid                   pri rep docs.count docs.deleted store.size pri.store.size
yellow open   .my-system-index U-HWdSsKTi2oqcrVNgPqfQ   1   1          1            0     10.4kb         10.4kb

SEARCH result
GET https://{ip}:{port}/.my-system-index/_search
Authorization: Basic {user_token}

{
  "took": 3,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 0,
      "relation": "eq"
    },
    "max_score": null,
    "hits": [] // cannot read documents. no hit item.
  }
}

What is the expected behavior?
expected SEARCH result
{
  "took": 4,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 1,
      "relation": "eq"
    },
    "max_score": 1.0,
    "hits": [
      {
        "_index": ".my-system-index",
        "_id": "1",
        "_score": 1.0,
        "_source": {
          "field": "value"
         }
       }
     ] // want to get hit items of the custom system index
  }
}

What is your host/environment?
$ cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.7 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.7"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.7 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/red_hat_enterprise_linux/8/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.7
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.7"

Plugins: 2.11.1

Do you have any screenshots?
Do you have any additional context?

[Triage] Hi @llilyy, thanks for filing this issue. To my knowledge, this behavior is not intentional. Thanks for your really detailed reproduction steps. Someone will take a look and update with findings or a correction for the bug.

@scrawfor99
It appears that the document is removed at the point below.
If it is not intentional, this part needs to be modified.
https://github.com/opensearch-project/security/blob/main/src/main/java/org/opensearch/security/configuration/SecurityIndexSearcherWrapper.java#L111-L114

After inspecting the test cases and adding a little bit of logging, I am positive that the feature is working, I'm closing out this issue.   If you alter the test case in a way that aligns with your scenario please push it to a fork or create a fresh pull request to help respark discussion around this feature.  Thanks!
See this comment for more details on proof this is working as expected [1].

[1] https://github.com/opensearch-project/security/pull/4201#issuecomment-2034567932

When will it be merged? I need it.

@Swalloow Thanks for checking in on this issue - it looks like it will be part of the upcoming OpenSearch 2.14 release.


Token rewrite

Hi Nick, I think we should rename the token.py because token is a standard library and it confuses the computer. I got an error and this is a thread with this discussion. Maybe we can change it to prsvtoken.py? This is what I am using for schema API script.


Streamlining useAsyncStoryblok to nuxt's useAsyncData

Description
In the latest versions useAsyncStoryblok returns only the story. You cannot control the useAsyncData that is inside the useAsyncStoryblok at all. For example, you would like to instruct lazy or client only fetching.
To be more in line with the way nuxt composables like useAsyncData or useFetch work the useAsyncStoryblok should return the object that contains the usual data, pending, etc properties. One could also provide the AsyncDataOptions for the composable.
This would be a breaking change and thus needs more discussion.
I can submit a PR for this if the idea sounds solid.
Suggested solution or improvement
This implementation of useAsyncStoryblok should work as described above.
import { useStoryblokApi, useStoryblokBridge } from "@storyblok/vue";
import type { ISbStoriesParams, StoryblokBridgeConfigV2, ISbStoryData } from '@storyblok/vue';
import { useState, onMounted, useAsyncData } from "#imports";
import { type AsyncDataOptions } from "#imports";

export const useAsyncStoryblok = async (
  url: string,
  apiOptions: ISbStoriesParams = {},
  bridgeOptions: StoryblokBridgeConfigV2 = {},
  asyncOptions: AsyncDataOptions = {}
) => {
  const storyblokApiInstance = useStoryblokApi();
  const uniqueKey = `${JSON.stringify(apiOptions)}${url}`;
  const story = useState<ISbStoryData>(`${uniqueKey}-state`);

  onMounted(() => {
    if (story.value && story.value.id) {
      useStoryblokBridge(
        story.value.id,
        evStory => (story.value = evStory),
        bridgeOptions,
      );
    }
  });

  return await useAsyncData(
    uniqueKey,
    () => {
      return storyblokApiInstance
        .get(`cdn/stories/${url}`, apiOptions)
        .then((r) => r.data.story)
    },
    asyncOptions
  )
};

This could be then called like this (from playground folder):
const { data: story, pending } = await useAsyncStoryblok(`vue/articles/${path.params.slug}`, {
  version: "draft",
  language: "en"
}, {},
{ server: false, lazy: true, dedupe: "defer" }); // <- any asyncData options to give the control to the dev

Additional context
No response
Validations

[X] Follow our Code of Conduct

Created the PR after all...

thanks - need this too. Also the current implementation loses any error context from the storyblok fetch and doesn't throw any errors too

Hi @jrutila thanks for reaching out! Can you confirm for me if the PR I linked is correct?
Since this introduces a breaking change let me discuss it internally with the team on how would be the best approach. 🙏


NDT_CUDA get nan result.

My system info:
pcl 1.12.1
eigen 3.4.0
CUDA 11.6
cudnn 8.3.2
gcc 11.2.0
My cmake argument:
cmake .. -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_STANDARD=17 -DCMAKE_INSTALL_PREFIX=/opt/ros/noetic -DBUILD_VGICP_CUDA=ON

Hi I am currently using fast_gicp to do some prior locating work.  Using the pointclouds provided by the repo, the NDT_CUDA algorithm still produces non-nan result.
The two pointclouds used by me:
pcd.zip

It seems the source is too apart from the target, and optimization is broken because there is completely no overlap. I'm not sure why other methods don't get corrupted, but I think any method can get broken in this setting.

It seems the source is too apart from the target, and optimization is broken because there is completely no overlap. I'm not sure why other methods don't get corrupted, but I think any method can get broken in this setting.

However on I found that align pointclouds provided by this repo also produces same result. I don't know whether this relates to PCL version, cause I found that current code in the repo is a bit incompatible with pcl v1.12.

Have you solved this problem?  I suspect it is related to the versions of eigen and cuda

Have you solved this problem? I suspect it is related to the versions of eigen and cuda

Yes, I found that PCL 1.12 is not compatible with this library. I downgrade PCL to 1.10 and everything works well. I think there might be some bugs with PCL 1.12. Besides, I am using archlinux.

thanks, i am using orin(aarch64), cuda11.4

thanks, i am using orin(aarch64), cuda11.4,pcl1.10.0, it still get nan result(ndt cuda)...

Hi @whuzs. Did you solved the problem?
I am currently using PCL 1.11.1 and Jetpack r35.1, but no problem using this library.


QG4: TRG 5.11 Upgradeability

Helm Chart Version: 0.1.5
App Version: 0.2.2-M1
Recommend to implement GitHub workflow to test helm chart upgradeability of the application.
More information you can find HERE.
Manual local test from 0.1.4 to 0.1.5 was successful hence marking the check as completed.

Hi @tomaszbarwicki,
many thanks for testing. If this fine now, please close that issue. Many thanks!


Option to hide file extensions

I propose the introduction of a setting that allows hiding the file extension in the notes title. This shouldn't create much confusion, since documents and drawings are easily distinguished by their icon. Either way, this may be an opt-in setting to avoid a bad UX for current users.

related to: https://github.com/lockbook/lockbook/issues/2936


Add jshint and fix some tests

Hey, I added jshint with a config that has no deprecated style rules (I'd add jscs in another PR if you want) and fixed some tests. I had to deactivate a few though, since they did not work as intended and there might be more. But I did not find the time to fix them yet.
I guess you'd all agree on the used jshint rules or are there any that you think should be removed again?

Why did these particular tests begin to fail with this PR?

The failing tests are async and the done was missing

It is a shame these weren't found before the 1.0.0 release. We should evaluate whether these fixes should go in before we promote our 1.0.0 release to latest.

@BridgeAR I'm excited to pull in jshint, two comments:

could we make it so that we run the jshint as a pretest event in scripts, and fail tests if someone breaks the style? Otherwise my experience has been that people rarely run npm run jshint.
request the second, could we move the refactoring work that is being done on tests into a separate pull, I don't like that a bunch of tests are being set to skip as part of this pull, I'd rather that the tests were updated and fixed in a separate pull request.

@erinspice the 1.0.0 has already been promoted to latest from next. If we do find any actual issues we can release 1.0.1, my guess would be it's just tests that need fiddling -- all tests were green prior to this pull, curious how adding jshint outlined problems in these tests? was it complaining about an unused callback or something @BridgeAR?

I'll add jshint as task before the tests run. That way you're sure everything passes
That's fine to me. The issue with them is though, that they did not work at all before (like one of them is a test that tried to check if the parameters are valid and the expectation was, that passing undefined as a key would throw. That is not the case though and it'll only throw in case of a wrong number of parameters. We could add a pre check in the code to check that no key may be undefined for those tests).

I did not find any issues in the code itself, so only the tests were flaky. When I added jshint I saw at least one place where the callback was not defined, so I checked other places too and found some broken tests. The only real code change I did was converting a string to a number in one place and that was only for consistency.

@BridgeAR we could also set the tests to skip in this pull, but not land this pull until we land a separate pull against this branch that fixes the tests?

I incorporated the feedback and changed the behavior of set, setex and mset so that they'll throw on undefined keys / values as suggested in the tests. This is a BC though (do you want to use semver?) but I'm uncertain if anyone would want to insert null or undefined values without converting them to a string beforehand. And there's another issue, since this behavior should likely also be the same for msetnx, setnx and others that are not yet handled. So a alternative would be to remove those tests and keep the old behavior as it was.
I did not fix the subscribe test yet, since until now I'm uncertain how that really works as I always get an Connection in subscriber mode, only subscriber commands may be used error even though the commands used seem to be subscriber commands... would you be so kind and have a look at that one?

@BridgeAR unfortunately, I am leaving today to be out of town until Monday. I wonder if @bcoe has time to check it out?

@BridgeAR great work. Except for my comment regarding the breaking change, I think this is pretty much ready to land. Could you outline in the issue specifically which tests have a problem, so that we can create better test cases?

@bcoe I'll remove the BC and fix the tests in a separate PR.

I reverted the BC and removed all broken tests from the PR. They will be handled in another PR. So this should be good to go.


"github.com/chrislusf/raft" appears unmaintained; maybe switch to "github.com/hashicorp/raft"?

github.com/chrislusf/raft have no issue tracker and no recent activity. The project that was originally forked is unmaintained.
Raft implementation is complex enough to use stable, mature and well maintained library.
Perhaps switching to github.com/hashicorp/raft would make sense?

SeaweedFS is only using leader election in raft. No other features needed.
It's better to stick with a stable version, not something always changing.

Please reopen. Reducing dependency on a dead code is a good idea.
Beware of unmaintained libraries. One can not even file a bug report against obsolete library.
It is a basic common sense to avoid needless forking as you increasing your maintenance burden by maintaining your own and only fork of the legacy project.

I disagree here. It is a critical piece and does not and should not change. Forking it is similar to pin it to a particular version. Unless we have a solid test suite, I do not want to risk all user's data with an upgrade mistake for this.
Also, the github.com/chrislusf/raft and github.com/hashicorp/raft are very different now.


About model training

Hello, how can I train on a single GPU instead of using DistributedDataParallel training?

Hi, you can run python xxx.py directly.


Javadoc publication

When Javadocs are officially published, update the dokka configuration with the final URL of the javadocs for each module so that links can be maintained.

[ ] Determine javadoc URL for each module

many apologies for the configuration delay
i have now updated the documentation serving to serve from
http://kotlin.binary-array-ld.net
this should give a stable root for the documentation
i have also put up a PR to update the readme  #46

Do we know where the Javadoc for each module will be hosted?

@simonoakesepimorphics
can we define a location based on this stable root?
is
http://kotlin.binary-array-ld.net/javadoc
useful
is there a pattern we should look to follow for this?
many thanks
mark

@marqh That will be fine as a root, but we will also need separate locations for each module because the javadoc artifacts are generated separately. So something like /javadoc/binary-array-cli, /javadoc/binary-array-lib would be suitable.

This is closed by #49


Challenges running Chorus 000 Kata

First of all, very cool project, thanks!
I'm trying to run Chorus, but got stucked. I first tried the 000 Kata, in here, running the transform_data.py results in an error "ModuleNotFoundError: No module named 'tqdm'", which I fixed by changing the command to:
docker run -v "$(pwd)":/app -w /app python:3 sh -c "pip install tqdm && python3 ./opensearch/transform_data.py icecat-products-w_price-19k-20201127.json transformed_data.json"
But I then get this other error in the script:
File "/app/./opensearch/transform_data.py", line 27, in
json_obj.get('locale') == "us" and
^^^^^^^^^^^^
AttributeError: 'str' object has no attribute 'get'
I also tried to run the 000 Kata directly with ./quickstart.sh but then I get:
Connecting to esci-s.s3.amazonaws.com (esci-s.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2024-11-28 16:49:11 ERROR 403: Forbidden.
Can I get some help to overcome this? I'd really like to test this out.

Hi @Franborat,
we recently switched to an alternative dataset and that causes the first Kata to be outdated. Sorry for that. This needs updating.
Apparently the dataset we use was temporarily not available. To me it looks like it is available again now. So running the quickstart.sh script should work again. Can you give that another try and give feedback if that's resolved?
Thanks!

Thanks for confirming that it works now!
The frontend is very basic at the moment, you are absolutely right: we only have a search bar and two filters (a brand filter and a product type filter).
The algorithm picker will work once we merge #127 into main. With that a user can switch between keyword, neural search and hybrid search.
Is that what you meant with "not fully coded" or did I misunderstand you there?
So we have very basic functionality but the frontend could definitely do with some improvements, so if you want to contribute that would be awesome! Is there anything in particular that you were thinking of?

Oh! I realized that the front-end was not loading well on my side. I now can see the filtering by brands and by product types, as well as the add to cart - before idk why it was not loading and that's why I thought the front-end was on the process of being built.
I'll be doing the the Katas and getting familiarized with the project, which overall looks very cool.
Thank you!

Sounds great!
We just merged #127 into main which has some improvements, so I recommend you pull the latest version and maybe start fresh.
I'll close this issue for now since you overcame the quickstart.sh issue. Feel free to open issues as you see them rising. And of course feel free to open PRs with improvements :)
Thanks for checking out Chorus!

closing this one


[camera] White balance lock feature support.

Use case
I would like to create a camera app that can locked exposure and white balance, but Flutter's camera plugin only have exposure setting function.
Proposal
Both iOS and Android seem to provide a way to lock the white balance.
iOS
WhiteBalanceMode.locked
Android
CaptureRequest.CONTROL_AWB_MODE_OFF

Hi @mutsuyuki, Thanks for filing the issue. Looks like a valid feature request to allow users to lock the exposure.

Hi @mutsuyuki, Thanks for filing the issue. Looks like a valid feature request to allow users to lock the exposure.

To be exact it should be possible to not only lock exposure and white balance, but also set a fixed exposure and white balance (not just lock after auto exposure/wb). This is especially required when you have a fixed camera setup with fixed lights and you know you will always want consistent settings.

@sactor any update on how did you achieve this ?

@sactor any update on how did you achieve this ?

I didn't, I just said what I need. I'm still hoping this will get implemented. I'm currently stuck with non-flutter camera app because I can't lock the white balance on Flutter (with ease). I don't have the resources for a more custom solution just to have it work on Flutter.

Can @mutsuyuki please specify a workaround or way to do it till the time this feature is added. Or if we can use a nightly build for it I'd be happy to use it, really require this feature urgently.


envoy_cc_library: add export of foo_with_external_headers

Description: Add a parallel native.cc_library to envoy_cc_library
for external projects that consume Envoy's libraries. This allows the consuming
project to disambiguate overlapping include paths when repository overlaying is used,
as it can now include envoy headers via external/envoy/...
Risk Level: Low
Testing: N/A
/cc htuch

/assign htuch


Local content store with label store

What is the problem you're trying to solve
I have been using the Containerd client communicating through the socket to read blob data from disk. This has worked until I started benchmarking and realized that there was a lot to be desired with the performance. After some digging I realized that when creating a ReaderAt for a blob it will read chunks of bytes when reading all of the data. This works well with small blobs but becomes noticeably slow with larger blobs >1Gb.
I had the idea to use a local content store which would allow reading blobs directly from disk. This comes with benefits like zero copy operations when copying blobs between a reader and writer. The downside with this solution is that the label store would not work as it is located in the metadata Bolt DB. As far as I can see I can not find an implementation for the label store which would work.
contentStore, err := local.NewStore("/var/lib/containerd/io.containerd.content.v1.content")
if err != nil {
    return nil, err
}
client := containerd.New(sock, containerd.WithDefaultNamespace(namespace), containerd.WithServices(containerd.WithContentStore(contentStore)))

Describe the solution you'd like
It would be useful to have a default label store implementation that would work with the Containerd GRPC API, so that a local store could be used with a remote label store. I am not sure if a blob label API even exists yet, so the implementation may be a bit more challenging than expected.
An alternative solution would be to look at a more efficient  method to read blobs over the Containerd socket. I am not sure if this is possible as all communication is done over GRPC.
Additional context
No response

It looks like this method might be useful<EMAIL_ADDRESS>It creates a local content store, using a label store that you provide.

The problem is that it is not possible to provide a LabelStore. Frist of all as far as I can see ther is no exported LabelStore implementation. Second of all the internal local content store in Containerd uses BoltDB to store labels. This blocks any attempt to create a custom LabelStore implementation that attempts to read from BoltDB.
The option right now seems to be to avoid any functionality that relies on layer labels. Alternatively keeping a separate content store that is only used for reading layers.


The PERF rules for ruff make this plugin crash (version 1.0.7)

If you want to use the PERF rules for ruff, this plugin crashes with the following error:
LSP-ruff: error: TOML parse error at line 70, column 5
   |
70 |     "PERF",  #  Perflint
   |     ^^^^^^
Unknown rule selector: `PERF`

I checked the versions of ruff and ruff-lsp for this plugin and they are outdated, the current versions are:
ruff==0.0.272
ruff-lsp==0.0.32

and so far the latest versions are:
ruff==0.0.277
ruff-lsp==0.0.35

I manually updated the previous libraries at ~/.cache/sublime-text/Package Storage/LSP-ruff and the PERF rules worked without any problem.
There is already a dependabot PR for upgrading them at https://github.com/sublimelsp/LSP-ruff/pull/25, but those are not the latest either.

Merged #25 and published a new release which should show up on Package Control shortly.
We follow the version of ruff that ruff-lsp uses for compatibility reasons, see here:
https://github.com/astral-sh/ruff-lsp/blob/43e60ebf060a924a205349920d501f57bfab1a44/pyproject.toml#L39.

Thank you! I think with that should be enough to fix the crash.
From my side I will keep updating the ruff version manually, because the releases are very frequent with bugfixes and features https://github.com/astral-sh/ruff/releases


Depend on Sanctuary Type Classes

Replaces show with Z.toString
Replaces ap, map, bimap and chain with curried Z equivalents

Fixes part of #4

Current coverage is 100% (diff: 100%)

No coverage report found for master at 1d5eaa9.

Powered by Codecov. Last update 1d5eaa9...a29f199

I'm excited to see this!
:deciduous_tree:


Add EuTimer to implement timeout for EuRxManager

Related Issue : #200
Previous PR : #218

I tried to checkout branch with Android Studio's Git UI, but I clicked Delete Branch by mistake... So my previous PR was automatically closed 😥
New Improvement

Added overloaded listen() that can accept the arguments for timeout
Added test code for listen()

I applied your reviews! Thank you!!


pull request for e2e test at 01/29/2017 06:26:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


⚠ Bofrost.at has degraded performance

In f3244e2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 922 ms

Resolved: Bofrost.at performance has improved in 7bfbe23.


[Feature]  ADD new message queue components

建议新增消息队列组件，方便与其他业务系统交互
It is recommended that new message queue components be added to facilitate interaction with other business systems.

good idea,
please update or add description in English for global users！
thank you！

+1 mark

@iamnotgay Could you give more descriptions?


Entering a remote URI requires reopening the kernel selector

Maybe this is timing based, but if I pick a remote server, wait 10 seconds and then 'select kernel', I don't see the remote kernels.
I have to repick select kernel to see them again.

This will be fixedc with the new kernel picker


[T2A2][T10-A2] Hu JingRui

Ready for review

Looks very similar to the T2A5 commit you have. Next time for each change do a commit and create the pull requests accordingly. It is easier to review and give comments then. Thanks


latency in message publish to pubsub

Hi,
I am using cloud function to publish a message from cloud function to pub/sub service using node.js library.
The package version is as following:
{
"name": "talk2Slack6",
"version": "0.8",
"dependencies": {
"@google-cloud/pubsub": "^0.19.0"
}
}
My cloud function received the data in JSON at 20:22:00 PST but reported successful publish to pub/sub topic at 20:23:20 PST. A delay of 1 and 1/2 minute seems unusually high.
Here is the snipped of the cloud function logs.
2018-07-08 20:23:20.572 PDT
talk2Slack6
e22x91c3qli8
Message<PHONE_NUMBER>19428 published Successfully!!
2018-07-08 20:22:00.782 PDT
talk2Slack6
e22x91c3qli8
Function execution took 281 ms, finished with status code: 200
2018-07-08 20:22:00.692 PDT
talk2Slack6
e22x91c3qli8
User : U212BDYKD posted this message - It was that which gave promise that in due time the weights should be .....
2018-07-08 20:22:00.501 PDT
talk2Slack6
e22x91c3qli8
Function execution started
Thank you for looking into it.
Ashish Kumar

I've also observed one order of magnitude increase in subscription latencies going from 0.18 to 0.19. With 0.18 we had highly predictable latencies which we lost when moving to 0.19. I am pretty sure there was a regression somewhere in this regard. We had to pin 0.18 in our dependencies since we require low predictable latencies.

@stephenplusplus I haven't been keeping up with Cloud Functions, but we've seen a lot of latency issues there, do you think this is related?

It could be, however, it sounds likes 0.19 could have introduced a regression. Are there any commits you think that could have been a factor?

The unpredictable high latency is for subscriptions is still an issue several months and releases later (I've just tested with 0.22.1). This means that we're stuck with version 0.18.0 because our application requires predictable low latency. Is this issue being looked at all?

@JustinBeckwith do we have an issue or anything to track GCF cold start performance? I think this is mostly the same as #397 otherwise.

Update: with latest (0.24.1) Node.js PubSub module we're no longer having issues with high and unpredictable subscription latency.

@pmcnr-hx that is great news, thanks for letting us know! I'm going to close #397 and we can keep this around as a GCF specific issue.

@ak-org just wanted to check on this since we've made some changes as the client has evolved. Is this still an issue?

Hi, I haven't used the service in past few weeks. You can go ahead and close the issue. If I find something, I will report back.


[TVMScript][FIX] Disable show_object_address in printing by default

The new feature of printing object addresses is introduced in #15579. It's an excellent feature for debugging, but it should not be turned on by default.
cc @Lunderberg @junrushao

Thank you for the fix.  This was intended to be disabled by default.


feat: add showSpace method

Description
Added showSpace method to open the Messenger with the specified space. The functionality of spaces is pretty fresh in the Intercom API, so I'm not sure if this is the best way to do it. I'm happy to change it if there's a better way.

This is awesome, big thanks! I'll review it asap :)