update user preferences handler to accept JSON instead of form data

Description
This PR adds ability to persist user preferences for extensions.
Notes for Reviewers

Modifies how POST /api/user/prefs
Example JSON object:

{
    "loadTestPrefs": {
        "c": 1,
        "t": "200s",
        "gen": "fortio"
    },
    "anonymousUsageStats": false,
    "anonymousPerfResults": false,
    "usersExtensionPreferences": {
        "hideToolbar": true,
        "showOnZoom": false
    }
}

Signed commits

[x] Yes, I signed my commits.

Codecov Report

Merging #4737 (6098e22) into master (5915d34) will decrease coverage by 6.95%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4737      +/-   ##
==========================================
- Coverage   32.32%   25.37%   -6.96%
==========================================
  Files          61       61
  Lines        5116     5116
==========================================
- Hits         1654     1298     -356
- Misses       3034     3500     +466
+ Partials      428      318     -110

Flag
Coverage Δ

gointegrationtests
?

unittests
25.37% <ø> (ø)

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

Impacted Files
Coverage Δ

mesheryctl/internal/cli/root/system/start.go
1.11% <0.00%> (-58.52%)
:arrow_down:

mesheryctl/internal/cli/root/system/restart.go
2.50% <0.00%> (-47.50%)
:arrow_down:

mesheryctl/internal/cli/root/system/status.go
0.00% <0.00%> (-47.44%)
:arrow_down:

mesheryctl/internal/cli/root/system/update.go
1.05% <0.00%> (-34.74%)
:arrow_down:

mesheryctl/internal/cli/root/system/stop.go
1.78% <0.00%> (-23.22%)
:arrow_down:

mesheryctl/internal/cli/root/system/check.go
1.39% <0.00%> (-22.38%)
:arrow_down:

mesheryctl/internal/cli/root/system/logs.go
3.29% <0.00%> (-20.88%)
:arrow_down:

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 55c3409...6098e22. Read the comment docs.

@DelusionalOptimist, @MarioArriaga92, with this change, we'll need to update the end-to-end user preferences test - https://github.com/meshery/meshery/runs/4448911173?check_suite_focus=true

@DelusionalOptimist will there be any changes required in the UI now that we have essentially changed the expected Content-Type?

@utkarsh-pro I suspect this is why the ui integration test is failing. // @Abhishek-kumar09

Yeah UI changes would be needed. The UI probably has some values hard coded which are sent as form data. Some changes such that it can parse and send json would be needed. I have attached a sample object in the PR description.

Yeah UI changes would be needed. The UI probably has some values hard coded which are sent as form data. Some changes such that it can parse and send json would be needed. I have attached a sample object in the PR description.

@Abhishek-kumar09, tag. You're it.

@utkarsh-pro there are default values for user preferences set by the Local Provider. This endpoint should be able to respond with those default values. Is this something that you can look into?


Update isb_cgc_data.rst

sorry, I didn't realize there was still this old mention of the "201607_beta" dataset ;-)

Thank you @smrgit !!


django branch master renamed to main, needs to be accomodated

As of March 9, 2021, Django renamed its master branch to main.
Here is the link to the conversation and announcement in the mailing list
This is causing a variety of errors while run asv commands. Defaults for git commands etc need to be changed to fix this.

Thanks for the report.
Would you like to have a go at fixing this? I think it should be a matter of finding the right setting in the JSON file?

Fixed in a065f1d22d64e2b1f554796299f0c36fa84d1341
@muskanvaswan -- do you want to have another look at this?

turns out, the reason that fix wasn't working for me was that it didn't recognise the change in the asv.conf.file. Deleting the cache folder did the trick eventually


Linear decay instead of cosine

Hi @epwalsh
Contrary to most of the models, OLMO followed linear LR decay instead of cosine. It would be interesting to observe the ablations. Can you post them if ablations are ready or post your observations here ?

@ayushbits we'll probably write about this in our upcoming "training details" paper. In the meantime I can give you my opinion, but take this with a grain a salt since our ablation at the 7B scale is not quite finished:

We used a linear decay at the time for our 7B because we didn't know which would work better, and it was a little safer to use linear instead of cosine since cosine initially keeps the learning rate higher for longer.
Since then we've discovered other reasons why some of our early experiments had spikes, and we're now a lot more confident in our ability to find stable hyperparameters. If we knew then what we do now we'd have probably used cosine.
But so far it seems like it really doesn't matter that much, and AFAIK there's no theoretical justification for either (though there is a theoretical justification for an inverse square root schedule - Will Merrill has a paper about this - but that's not as popular in practice).

Thanks Pete @epwalsh for the detailed explanation. Helps a lot !

Thanks Pete @epwalsh  for the detailed explanation. Helps a lot !

Marking the items prior to Feb 29th as "closed".


Regression: on demo site, after login, the main page doesn't load

(Login seems to be working fine, I entered<EMAIL_ADDRESS>and demo as credentials.)
Screenshots are from Firefox Nightly 122 and Chromium 112.

Some error logs.
TypeError: s.substring is not a function
    at OverviewTasksProgress (index-80ad44adf5badcc9.js:1:511)
    at Xh (framework-0c7baedefba6b077.js:9:60990)
    at x (framework-0c7baedefba6b077.js:9:119445)
    at Vk (framework-0c7baedefba6b077.js:9:99130)
    at framework-0c7baedefba6b077.js:9:98997
    at Jk (framework-0c7baedefba6b077.js:9:99004)
    at Ok (framework-0c7baedefba6b077.js:9:95760)
    at Hk (framework-0c7baedefba6b077.js:9:94316)
    at J (framework-0c7baedefba6b077.js:33:1364)
    at MessagePort.R (framework-0c7baedefba6b077.js:33:1894)

TypeError: s.substring is not a function
    at OverviewTasksProgress (index-80ad44adf5badcc9.js:1:511)
    at Xh (framework-0c7baedefba6b077.js:9:60990)
    at x (framework-0c7baedefba6b077.js:9:119445)
    at Vk (framework-0c7baedefba6b077.js:9:99130)
    at framework-0c7baedefba6b077.js:9:98997
    at Jk (framework-0c7baedefba6b077.js:9:99004)
    at Ok (framework-0c7baedefba6b077.js:9:95760)
    at Hk (framework-0c7baedefba6b077.js:9:94316)
    at J (framework-0c7baedefba6b077.js:33:1364)
    at MessagePort.R (framework-0c7baedefba6b077.js:33:1894)

Hi @alurm,
I've launched a new website: https://demo.oktopus.app.br, can you see if it solved the problem? If so, mark this comment as answer and close the issue.
Thanks in advance.

Hi @leandrofars, I can't check that, since it's not logging in for me when using the demo credentials.

I'm sorry @alurm , forgot to register demo user, now it's available.


gps command for precise locations

Include a command that allows to navigate to a precise position.
Syntax:
/gpslocation <location>
Example usage:
/gpslocation 10 ~ -19
Will create a temporary node for the target location and connect it to the closest node.
Includes:

[x] Config value for max distance to closest node to prevent the path to go through e.g. walls or mountains.
[x] Wiki page for new command
[x] Config value to allow smart evaluation that prefers nodes that are not blocked against nodes that are closer but blocked. Is already implemented to calculate the closest node from the player position if the player uses /gps.
[x] -1 as max distance interpreted as no limitation
[x] Permission check and permission node in plugin.yml

Completed with v4, where the most optimal algorithm is used that finds the closest edge


⚠ Bofrost.be has degraded performance

In 7870056, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1165 ms

Resolved: Bofrost.be performance has improved in 791cb34.


Do not run /_stats endpoint tests on backend of a tiered topology.

Signed-off-by: Prajakta Purohit<EMAIL_ADDRESS>We see a couple of failing /_stats endpoint tests only on the backed of the tiered setup. These should not be run unless use is on standalone or the frontend of a tiered setup.
Adding config and conditionals around to ensure this behaviour.
Check List

[ ] New functionality includes tests
[ ] All tests pass
[ ] All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/master/CONTRIBUTING.md#developer-certification-of-origin-dco

Building at: https://buildkite.com/chef/chef-a1-master-omnibus-adhoc/builds/16#a7fae87a-63f9-4e4c-b9e0-bb9998bea8d4


Error : You must download() an article first!

Mandatory

[x] I read the documentation (readme and wiki).
[x] I searched other issues (including closed issues) and could not find any to be related. If you find related issues post them below or directly add your issue to the most related one.
[x] I confirm that this bug report does not report on a specific news site where news-please does not work. Please keep in mind that news-please is a generic crawler so it is expected that it will not work for all sites well or even at all.

Describe the bug
While using the news-please as library we are getting error "You must download() an article first!"
To Reproduce
here is the code,
url='https://www.nytimes.com/2017/02/23/us/politics/cpac-stephen-bannon-reince-priebus.html?hp'
article = NewsPlease.from_url(url)
print(url)
print(article.title)

Log
detailed error is here,
{
  "errorMessage": "You must `download()` an article first!",
  "errorType": "ArticleException",
  "requestId": "d80ca965-31a1-4944-aedd-0e2e5aa891e5",
  "stackTrace": [
    "  File \"/var/task/main.py\", line 6, in lambda_handler\n    article = NewsPlease.from_url(url)\n",
    "  File \"/var/task/newsplease/__init__.py\", line 110, in from_url\n    articles = NewsPlease.from_urls([url], timeout=timeout)\n",
    "  File \"/var/task/newsplease/__init__.py\", line 134, in from_urls\n    results[url] = NewsPlease.from_html(html, url, download_date)\n",
    "  File \"/var/task/newsplease/__init__.py\", line 95, in from_html\n    item = extractor.extract(item)\n",
    "  File \"/var/task/newsplease/pipeline/extractor/article_extractor.py\", line 63, in extract\n    article_candidate = extractor.extract(item)\n",
    "  File \"/var/task/newsplease/pipeline/extractor/extractors/newspaper_extractor.py\", line 33, in extract\n    article.parse()\n",
    "  File \"/var/task/newspaper/article.py\", line 191, in parse\n    self.throw_if_not_downloaded_verbose()\n",
    "  File \"/var/task/newspaper/article.py\", line 529, in throw_if_not_downloaded_verbose\n    raise ArticleException('You must `download()` an article first!')\n"
  ]
}

I have deployed this code sample on lambda and trying to run. Also installed latest version of news-please.
Versions (please complete the following information):

Linux
Python Version - 3.9
news-please Version - 1.5.22

Intent (optional; we'll use this info to prioritize upcoming tasks to work on)

[x] personal
[ ] academic
[ ] business
[ ] other

same situation here

looking into this now


Document Improvement: aliyuncli ecs CreateInstance documentation

Documentation of creating instance should be more detailed for the sake of the usability of this sub-command.
No successful demo of what a right CreateInstances should be like make the process of test command fail and retry painful.

Documentation of creating instance should be more detailed for the sake of the usability of this sub-command.
No successful demo of what a right CreateInstances should be like make the process of test command fail and retry painful.

Hi, this issue has been around for a long time now, we suggest you uptate to the lastest version of CLI and try again. If you have any questions, please contact us.
Thank you for your attention to AliCloud CLI Project.


Update magic string for Mozilla CSS tests syncing

CC @dbaron

I see https://github.com/web-platform-tests/wpt/pull/12596


Added ExaltedMC

General:

[x] The pull request title is descriptive. (ex. Added Lunar Network, not Updated servers.json)
[x] The pull request does not contain any unrelated commits.  (ex. commits from previous pull requests)

Mapping Additions or Updates:

[x] No changes were made to the file's formatting.
[x] There are no syntax errors.
[x] There is no pre-existing mapping matching my id.
[x] My field values match your requirements.
You can view our patterns here: servers.schema.json, or take a look below and complete the field checklist:

[x] id: a lowercase string (ex. myserver)
[x] name: a string (ex. MyServerPvP)
[x] addresses: an array with lowercase strings (ex. ["my.server", "your-server.com"])

You do not need to specify subdomains, Lunar Client services automatically detect them.

[x] primaryAddress: an address (ex. my.server)
[x] minecraftVersions: an array with Minecraft versions as strings (ex. ["1.18", "1.19"])
[x] primaryMinecraftVersion: a Minecraft version as a string (ex. 1.18)

Logo Additions or Updates:

[x] My image is a png file.
[x] I uploaded my image to the logos directory.
[x] My image has a transparent background and is square (1:1 aspect ratio).
[x] My image is 512 pixels in width and height.
[x] My image's file name matches its mapping id.

Done.

Done.
On Tue, Aug 16, 2022 at 6:32 PM Jordan @.***> wrote:

@.**** requested changes on this pull request.
Please add the server logo to the 'logos' directory.
—
Reply to this email directly, view it on GitHub
https://github.com/LunarClient/ServerMappings/pull/457#pullrequestreview-1074437098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2RKOJUZKXGSSZ2B7FXVFHLVZO7BPANCNFSM56T3NS6Q
.
You are receiving this because you authored the thread.Message ID:
@.***>


Update scala-library to 2.13.8

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

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

Superseded by #125.


Redirect remote failures to /home/error

#1165 The remote auth components like Facebook or OIDC have never handled remote failures gracefully. E.g. if a user declines permissions to your app then an exception is thrown and the client gets a 500 error.
OAuth and OIDC define some standard error fields and we currently use these to generate a detailed exception message. This takes that one step further and generates a redirect to /home/error with those error fields as query parameters.
Sending this initial PR to see if this is a change we're willing to take for 2.1. If so then I'll add a few more tests and clean it up.
Here are some notes on the behavior of individual providers:
Google
- Doesn't even ask for consent? It only ask you to select an account.
Facebook
- https://www.facebook.com/settings?tab=applications
- GET /signin-facebook?
- error=access_denied&
- error_code=200&
- error_description=Permissions%20error&
- error_reason=user_denied&
- state=CfDJ8JQ7RNKCadBHk4_sI5UNfETy2xdPTigkm_jCBShuc9asO__-yHcEa_3dizjzX2PVb2IAPdODytGjkySQsU8HxmWRI3i3PO-9tXRQEocO8mkCz16pxAqdcdOdWpsfx2i9EMqMdpnCeTwmHjHvhlRqZ5IBqgTbbFQWhBHkhbILKzECS8lZ6DYJneLziBS-Fn10PrLe4w_EGLO1_dr5a5qp2MI HTTP/1.1
Twitter
- https://twitter.com/settings/applications
-  GET /signin-twitter?denied=vBzGPQAAAAAAu4omAAABYKRNrBY HTTP/1.1
Microsoft
- https://account.live.com/consent/Manage
- GET /signin-microsoft?
- error=access_denied&
- error_description=The%20user%20has%20denied%20access%20to%20the%20scope%20requested%20by%20the%20client%20application.&
- state=CfDJ8JQ7RNKCadBHk4_sI5UNfESFOFwEQvoQNcB5iKIYymQ9rjkvRwSlJQIwMbFv59pAQEXo8Nrs1KSLKQUBaSQ7d1rPMgTZUnr8RGap2Ej5npXBDTHQtEgeBMJyzjOT2YTHvJqQGu0KLT0yHZFsI912UDqY8tsWEyXIp_9pdzxPj9mKWF1fXvI-5fG3vvElWSslNI_jInsFUIAtRPYspbGkTTc HTTP/1.1
Github
- No cancel button
- https://github.com/settings/applications
@PinpointTownes how well do the other providers you've seen map to this?

@PinpointTownes how well do the other providers you've seen map to this?

In theory, both the OAuth2/OIDC specs encourage redirecting the user agent back to the client application's redirect_uri when an error occurs as long as it's safe to do so (i.e the client_id/redirect_uri couple was valid).
In practice, there are 3 main schools of thought:

There are providers that redirect the UA back to the RP for all errors (except for invalid client_id/redirect_uri).
There are providers that redirect the UA only for a few errors like access_denied and directly render an error page for everything else (e.g invalid scope or unsupported response type).
There are providers that refuse to redirect the UA for security reasons and always render an error page. In this case, pressing the back button is the only way for the UA to get back to the RP.

It's hard to give precise numbers as every provider does its own sauce, but 2) and 3) are probably the most common ones.
There's nothing you can do if the provider decides to adopt the 3rd approach, but the other cases should be handled by what you've implemented as part of this PR.

The only thing I'm not super comfortable with is adding the error/description to the "remote error endpoint path" URL as it may encourage folks to create an error page displaying the error/description as-is. And we all know what happens when we do that... :sweat_smile:

@Tratcher looks like a few guys are interested by my suggestion. Time to revive this PR?

Not yet, we'll revisit for 2.2.

Alright (please move https://github.com/aspnet/Security/issues/710 to the 2.2 milestone so you don't forget :smile:)


Update "Download CSV" button design

During Sprint 6 usability testing, we observed that users were unfamiliar with the CSV terminology.
To Do:

[x] Add an icon or update the language in the “download CSV” button to add familiarity for those who know what Excel is but are unfamiliar with the CSV term

Once design is ready, we will shift this ticket to engineering.


Add FrancesCoronel's Portfolio

Adding my portfolio after getting an email about this project! ✨

@FrancesCoronel
Awesome! ✨
Thanks :)

@all-contributors please add @FrancesCoronel for code


Type annotations for the examples

I looked through most of the examples provided by Equinox, and it seems like only bert.ipynb is completely annotated with jaxtyping: both function and dataclass declarations. Some other examples have partial annotations, and some have no annotations at all.
Possibly it would be better to have the same level/style of annotations for all the examples?
From #456 it seems that there is no automatic typechecking for the examples, might be nice to introduce this too? However, this would probably require quite some work: one would need to refactor all the examples, so that they have requirements.txt of some sort, otherwise I don't think it would be possible to typecheck anything.
Overall, I cannot really think about any sufficiently good solution for automatic typechecking, so I am wondering what is your opinion.

So the reason for this is just that Equinox predates jaxtyping, so many of its examples were written before jaxtyping existed. I'd be happy to take PRs updating these where appropriate. This hasn't really been a priority just because I'd quite like the examples to focus on Equinox, rather than any other library, so we'd need to think where it makes most sense to add it in. (Not in the introductory examples, in particular.)
As for running the typechecking. One fairly easy possibility would be to add (a spruced-up version of) this snippet into jaxtyping, and then call it at the end of the script. That's definitely pretty hacky though, I'm not sure that's behaviour I want to encourage in a pedagogical example. We could maybe add it in, along with some way to hide particular cells from the HTML conversion? (We use mknotebooks to do this at the moment.) Then we get the safety without the user-facing hackiness... !
Happy to take a PR implementing any part of this.

Hello I would like to do this, I have never used JAX, but I am well versed in PyTorch and Tensorflow. I would like to get some learning experience with JAX while being productive. I can write the docs which will help me learn more about JAX and equinox. Can I go ahead with it? If yes is there a contributing guideline here (I couldn't find any)?

You can find the contribution guideline at CONTIBUTING.md. For the typechecking you might want to use jaxtyping IPython hooks, something like this:
import jaxtyping
%load_ext jaxtyping
%jaxtyping.typechecker beartype.beartype

Using the hook is preferred over the solution proposed by Patrick, since the hook was introduced precisely to simplify use of jaxtyping in the notebooks.
About going ahead - cannot really say anything for certain, since this is the project of Patrick :) But since it was mentioned that PRs are welcome, you probably can open a PR. To make sure that you are doing everything correctly it might make sense to start with type annotating only a single notebook, and then asking for a review.

Ok sounds good! Thank you for the direction.

Chiming in here -- I'd like to avoid using jaxtyping in the "introductory"/"features" notebooks, to avoid frontloading too much information at once.
I'd be very happy to use it in any of the "advanced" notebooks though.

unet.ipynb, deep_convolution_gan,ipynb, vision_transformer and score_based_diffusion.ipynb seem to fit this description?

Yup!


FALCON-1842 Falcon build failed in Jenkins at OozieFeedWorkflowBuilde…

…rTest (Balu Vellanki)

+1 for the patch.

+1. Will commit shortly.


Crash on 1.8

The game crashes at startup during the copyright screen. Was working on previous versions of the game.

Yes, as said above, it doesn't let you go past the first (copyright) screen about Universal etc and in conclusion the game crashes.

The modkit does not work with this latest version of Jurassic World Evolution. You'll need to either remove the modkit (by deleting the files that you copied into the game directory) or use a previous version of the game. Deleting the dxgi.dll / d3d11.dll should be enough, but you can also delete the other files associated with the devkit as well. If you happened to delete the wrong files, you can reinstall them with the "Verify Integrity" option: https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

Is this something that can be fixed or is the concept of this mod no longer viable?

Hey "Pathos0925" Can i pay you to get this updated to work again for this update?

Will be an update for us? Plsease :D


easily add one or more experiments

new coldata and new samplemap

refer to: https://github.com/BiocPy/MultiAssayExperiment/commit/1036dab0fc625dc3bc26802c38a5a3a0bf96e831


Add Tu Lap Hight School

School website: https://c3tulap.edu.vn/about/

@haitv282 Regrettably, this request has signs of the domain being not owned by the school. I have to close it without merging.
Please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
Thank you for your understanding!


Improve Hashlink/C documentation

Explain how to install the hashlink haxelib package
Explain how to generate Visual Studio project files

Mention HASHLINK environment variable: https://github.com/HaxeFoundation/hashlink/issues/473

Thanks!


Warnings in sfm_landmark.hpp

The compiler complains about initialization order:
/home/labo/Install/openMVG/include/openMVG/sfm/sfm_landmark.hpp: In constructor ‘openMVG::sfm::Landmark::Landmark(const Vec3&, const Observations&, const RGBColor&)’:
/home/labo/Install/openMVG/include/openMVG/sfm/sfm_landmark.hpp:69:16: warning: ‘openMVG::sfm::Landmark::obs’ will be initialized after [-Wreorder]
   Observations obs;
                ^
/home/labo/Install/openMVG/include/openMVG/sfm/sfm_landmark.hpp:68:19: warning:   ‘openMVG::image::RGBColor openMVG::sfm::Landmark::rgb’ [-Wreorder]
   image::RGBColor rgb;    //!> the color associated to the point
                   ^
/home/labo/Install/openMVG/include/openMVG/sfm/sfm_landmark.hpp:59:3: warning:   when initialized here [-Wreorder]
   Landmark(const Vec3& pos3d,

In constructor initializer lists, member must/will be initialized in the same order as they were declared in the class. The solution is to either reorder members in the class declaration, or reorder initializer lists.

yes my bad. you can move the rgb member at the end (it's been the last to be added if we want to use a chronological order)


Test for RT #125488

So far phase POST has had problem when in-loop
I'm not sure if the plan number is right(for I fudge one test), besides, if I fudge the test in the right way.
It should be mention that POST not always see no outer $_
https://github.com/perl6/roast/blob/e10d7819126d10a2731ecf00f0dcfd5abf595b56/S04-phasers/pre-post.t#L81-L95

POST should not see $, at least from what I can understand. $ in POST is set to the return value of the block:
perl6 -e 'say (for ^2 { POST .say; 42 })'

42
42
(42 42)

@AlexDaniel am I supposed to remove this subtest on POST
https://github.com/perl6/roast/blob/4355702fc69d7bfa9cda8b808c885e881f646a9d/S04-phasers/in-loop.t#L163-L169
and say that the ticket is totally resolved?

Yeah.


Improve handling of special tokens in Dictionary

https://github.com/pytorch/fairseq/blob/eb68afca0208a040d4e91eceae86f5f22ca24b04/fairseq/data/dictionary.py#L178-L190
When loading dict.txt that already contains special tokens such as <s> or <pad> (which are added by default in sentencepiece), these tokens appear twice in the fairseq dictionary.
They are added once in Dictionary.__init__() and a second time from the dict.txt file in Dictionary.add_from_file().
This causes weird behaviours e.g. when using the model in https://github.com/huggingface/transformers.
Ideally Dictionary would not add the special tokens manually when loading an external dict.txt that already contains them (such as in https://github.com/huggingface/transformers).
But I am afraid that this can break backward compatibility for people who already trained models with this "duplicated special tokens bug".
For instance:
>> print([fairseq_model.task.dictionary[i] for i in range(15)])
['<s>', '<pad>', '</s>', '<unk>', '<unk>', '<s>', '</s>', ',', '▁the', ...]

In the fill_mask() method for roberta, this is what happens:
>> tokens = self.task.source_dictionary.encode_line(
       '<s> ' + text_spans_bpe,
       append_eos=True,
       add_if_not_exist=False,
   )
   print(tokens)
tensor([[    5,  1285, 32004,     2]])

With the first token 5 being the <s> that was added as a string and matched to the token from dict.txt and the last token 2 corresponding to dictionary.eos().

Cross-referencing related bugs in HuggingFace Transformers: https://github.com/huggingface/transformers/pull/2065

I think we should go a step further and remove all implicit special tokens, and only use explicit special tokens.
One nice way to handle backward compatibility is to add a header line to new dict.txt files indicating the version. Under the new version all special tokens are explicit, but if there is not header then we fall back to the old logic (where extra special tokens are added implicitly).
What do you think @louismartin?

Yes that would definitely solve it.
Not sure there's a better way to handle backward compatibility.
Thanks!

So sorry to interrupt. At the bpe process of pretraining, is it right that fariseq did not do special preprocessing to special tokens like "" or "" ?  For example, the token ”“ in "A has done  to B" would be viewed as something like separate "" by bpe.
I am not sure whether I think it right. Thank you!


Virtualized list does not scroll selected item into view on pointer click

🐛 Bug Report
Hello! Virtualized listboxes do not properly restore the scroll position / scroll the selected item into view. It looks like it has something to do with the view caching / recognition inside a virtualized listbox item. We ran into the same issue with an in house virtualized 'picker,' but the same issue is evident on the React Spectrum Asynchronous Picker when viewing a long list. This appears to only happen when using a pointer, probably due to the modality check in the useEffect. Using a keyboard to interact with the same element always scrolls it into view.
🤔 Expected Behavior
Clicking on a select to open it should always scroll the selected item into view.
😯 Current Behavior
Every other open of the useSelectableCollection starts at the beginning of the list. You can replicate this by again using the React Spectrum Asynchronous Picker and clicking on the picker multiple times. It will alternate between scrolling it into view, and starting at the beginning of the list.
💁 Possible Solution
The modality check for pointers in the above example (modality check in the useEffect) seems to only scroll the selected item into view if modality isn't a pointer, which conflicts with opening it repeatedly with a pointer. It appears to be due to views being cached and invalidated after the first open as the other useEffect cannot find the view (since it has been destroyed), doesn't focus automatically due to the modality check above, and focuses the container instead with focusWithoutScrolling.
Something like below can be used as a workaround inside the Picker, Select, etc, to forcefully reset the visible rect and have the virtualizer re-handle layout:
useEffect(() => {
    if (!state.isOpen) {
      if (layout.virtualizer) {
        layout.virtualizer.visibleRect = new Rect();
      }
    }
  }, [state.isOpen, layout.virtualizer]);

🔦 Context
When opening a select, users like to see the currently selected item in view so adjacent ones can be selected and the appearance of the currently selected item is still visible and doesn't appear like it's been unselected.
💻 Code Sample
Can be seen on the  React Spectrum Asynchronous Picker.
🌍 Your Environment

Software
Version(s)

react-spectrum
latest

Browser
Chrome 108

Operating System
MacOS

🧢 Your Company/Team
Other

Thanks for bringing this up, this looks to be a regression. There seems to be some kind of race condition where  !isFocusWithin.current here is returning false occasionally, seemingly due to the order in which useSelectableItem calls .focus on the actual list item (causing this to set isFocusWithin as true) versus this blur setting isFocusWithin as false because the focusedView doesn't exist yet as you noted.
Will need to find some time to deep dive for the cause of this regression, will keep your proposed solution in mind. Ideally Virtualizer would notify when it has finished constructing its visible view perhaps, or maybe we can delay focusing the list item until the scrollIntoView part of Virtualizer has executed

@ozguruysal looks like applying a max height onto the ListBox ul fixes the issue: https://codesandbox.io/s/pensive-architecture-3d9pvi. Still digging to see why exactly, mind filing a separate issue since this code is separate from the virtualizer code when handling scrolling the focused key into view?

Thank you @LFDanLu, opened a separate issue.

Looks like this was fixed by https://github.com/adobe/react-spectrum/pull/6527 as well


Compatibility with dynamic parameters

is there a way I can use "Register-ArgumentCompleter" together with "DynamicParam" ?

I don't think dynamic parameters are special, so it should just work.


[BUG] Tag translation for fit-in-transform and fit_is_empty not working as intended

Describe the bug
My trafo still used the old tag fit-in-transform: False, but when I did my_trafo.get_tag("fit_is_empty") it returned True, so seems translation is not working in this direction. The problem is I guess here:
https://github.com/alan-turing-institute/sktime/blob/68c359f7afd070ce4778cc1e2937b3d92913129f/sktime/base/_base.py#L430
It only translates in one way.
The translation is needed in the BaseTransformer here:
https://github.com/alan-turing-institute/sktime/blob/68c359f7afd070ce4778cc1e2937b3d92913129f/sktime/transformations/base.py#L277
Reproduce

from sktime.transformations.base import BaseTransformer

class Featureizer(BaseTransformer):
    _tags = {
        "fit-in-transform": False,
        "transform-returns-same-time-index": True,
        "skip-inverse-transform": True,
        "univariate-only": False,
        "X_inner_mtype": ["pd.DataFrame"],
        "y_inner_mtype": ["pd.Series"],
        "scitype:y": "univariate",
        # "fit_is_empty": False,
        # "scitype:X": "multivariate",
    }

    def __init__(self, transformer, fh, suffix=None):
        self.transformer = transformer
        self.fh = fh
        self.suffix = suffix
        super(Featureizer, self).__init__()

    def _fit(self, X, y=None):
        pass

    def _transform(self, X, y=None):
        return X

from sktime.datasets import load_longley
from sktime.transformations.series.exponent import ExponentTransformer
from sktime.forecasting.base import ForecastingHorizon
from sktime.forecasting.model_selection import temporal_train_test_split

y, X = load_longley()
y_train, y_test, X_train, X_test = temporal_train_test_split(y, X)
fh = ForecastingHorizon(y_test.index, is_relative=False)

featureizer = Featureizer(ExponentTransformer(), fh=fh)
featureizer.fit(X_train, y_train)
featureizer.transform(X_test, y_test)
featureizer.get_tag("fit_is_empty")
featureizer.get_tag("fit-in-transform")

I looked into this and I think this is expected behaviour.
Why: BaseTransformer has a default set of "fit_is_empty" being True, so all transformers inherit the tag.
If the tag is available, it is not overridden by its alias.
I think this is expected behaviour? Since the "right" tag, if found together with the "old" tag, should have precedence.
Or do you think this is unintuitive?
In any case, simply change the tag to the new one and all should be fine.

yes I chnged to new one and it works fine.

ok, so we can close then?


NTR:	PMID:24583014

abnormal protein localization to kinetochore in mitotic anaphase
increased duration of the APC complex  (present in anaphase)
(How do we do this? stability?)
decreased protein degradation during mitotic anaphase

increased duration of the APC complex (present in anaphase)

Does this mean the APC is present for longer than normal? If so, I'll have a think about how to word the name ("duration of complex" doesn't make sense, but "duration of complex presence" might work).

Yes it usually disappears in anaphase.

abnormal protein localization to kinetochore during mitotic anaphase FYPO:0007401
abnormal protein complex organization during vegetative growth FYPO:0007402 (grouping term)
increased duration of anaphase-promoting complex presence FYPO:0007403
decreased protein degradation during mitotic anaphase FYPO:0007404


shorter representation of graph connections

concats from and storeName into a string.

Thank you. You are right about it being tricky, having composed values is a hassle, but I feel like it's worth it. We are stuck between human and machine readable here.

i think it's a balance - i kept candidates decomposed, because these are computed values that are never visible to the human... the graph nodes should prioritize the reader (not the developer)...


Confuse on SessionEventLoopGroup.routeCommand method

As you know,routeCommand method would be invoked to handle mqtt request.
I am confused about whether the processing order needs to be guaranteed for MQTT protocol requests. If it needs to be ensured, then the following code segment
if (Thread.currentThread() == sessionExecutors[targetQueueId]) {             SessionEventLoop.executeTask(task);             return PostOffice.RouteResult.success(clientId, cmd.completableFuture()); }
will result in a probability of unordered request processing.
Additionally, considering the places where the routeCommand method is invoked, I can deduce that the above code will not be executed. If it won't be executed, then why is this code segment written?

This bit of code happens when the thread that wants to add a command to a queue is the thread that handles the queue the command is added to. This only happens for Acknowledge messages, which should have priority and skip the queue.

This bit of code happens when the thread that wants to add a command to a queue is the thread that handles the queue the command is added to. This only happens for Acknowledge messages, which should have priority and skip the queue.
I cannot find in the source code where the EventLoop thread is used to handle the addition of commands. Therefore, I believe the above code will never be executed

This bit of code happens when the thread that wants to add a command to a queue is the thread that handles the queue the command is added to. This only happens for Acknowledge messages, which should have priority and skip the queue.

I cannot find in the source code where the EventLoop thread is used to handle the addition of commands. Therefore, I believe the above code will never be executed

Indeed, this currently also happens for Publish commands if the publisher is on the same thread as the receiver. And this indeed causes these publishes to jump the queue.
There are cases where the command must jump the queue. For instance the SessionRegistry::remove() has the goal of cleaning up the queues. If this happens because the client re-connected with cleanSession=true, this will be called from the same thread, and it should probably happen directly (not entirely sure there).
We may have to add a flag to indicate the action should jump the Queue or not.

be

Indeed, this currently also happens for Publish commands if the publisher is on the same thread as the receiver. And this indeed causes these publishes to jump the queue.
There are cases where the command must jump the queue. For instance the SessionRegistry::remove() has the goal of cleaning up the queues. If this happens because the client re-connected with cleanSession=true, this will be called from the same thread, and it should probably happen directly (not entirely sure there).
We may have to add a flag to indicate the action should jump the Queue or not.

I debugged the source code and realized that you were right. I will close the issue. Thank you for your patient response.


Migrate drawing board to webgl or canvas

Currently we are working with single threaded system that is extremly inefficient for a dynamic canvas.
2 obvious options come up:

canvs (html object)
webgl (multithreaded gpu)

closing for archiving


NegotiationContext.DefaultModel is not null when action returns null model

Prerequisites

[x] I have written a descriptive issue title
[x] I have verified that I am running the latest version of Nancy
[ ] I have verified if the problem exist in both DEBUG and RELEASE mode
[x] I have searched open and closed issues to ensure it has not already been reported

Description
In Nancy 1.x when the model returned from an action is null, so is NancyContext#NegotiationContext.DefaultModel. I took advantage of that fact to return 404 for null models.
In Nancy 2.0 in such a scenario the DefaultModel is a Response object. Debugger displays OK text/html nad the response is actually empty.
Steps to Reproduce

Return null from an action
Inspect NancyContext#NegotiationContext.DefaultModel in an After pipeline hook.

Here's a gist with minimal reproduction.
System Configuration

Nancy version: 2.0-barneyrubble
Nancy host

[ ] ASP.NET
[x] OWIN
[ ] Self-Hosted
[ ] Other:

.NET Framework version: 4.5.2

There must be something in your code that is setting NegotiationContext.DefaultModel. I had a look at our code and it's only being used 3 times, directly, in our code and only 2 of those places are set operations

I also took you minimal reproduction and ran it on 2.0.0-clinteastwood

As you can see it is null. As far as I know we have not made any changes to that code in quite some time

Thank's for checking this out.
For the record, I double checked with barneyrubble and the gist fails there. I then ran against clinteastwood and it works fine.
¯_(ツ)_/¯

😄

You know what, I've just been thinking about this, and maybe a PR with test is in order to ensure there is no regression. After all there was something wrong with Barney Rubble.

You know what, I've just been thinking about this, and maybe a PR with test is in order to ensure there is no regression. After all there was something wrong with Barney Rubble.

@tpluscode sure we'd be happy to take such a PR

@tpluscode sure we'd be happy to take such a PR


Scaled sprite's hitbox overlaps with tiles

Describe the bug
When a sprite is scaled, it looks like the hitbox is off by a few pixels causing the sprite to bleed over into walls a little bit
To Reproduce
Steps to reproduce the behavior:

Load this project in beta: https://makecode.com/_8aqbDugDqEH8
See how the cat's image overlaps with the ground by a few pixels

Expected behavior
When resizing, the hitbox should contain the entirety of the sprite.
Screenshots

Hm, this looks like it's hitting this existing edge case that we added in mainly to accommodate animations: https://github.com/microsoft/pxt-common-packages/blob/master/libs/game/sprite.ts#L376-L377
The reason this was added in was because we would get lots of cases where you would get constant jitters from the animation changing the size by ~ 1px.
we should maybe have a way to explicitly set the hitbox (e.g. pass in a 'hitbox override' img that takes precedence over the current image) and think about getting rid of the current hack but it could make some existing games jittery & possibly have some weird interactions (e.g. if their jump logic in a 2d platformer checks on vy == 0 to make it so you can only jump when you're standing on a platform, it's possible that they will get a non-0 vy on certain frames when the hitbox changes and it 'falls' 2 pixels to the ground, so it would miss the button press / jump while standing still)

@jwunderl with scaling we shouldn't have to fully recalculate the hitbox since the pixels aren't changing (just simple multiplication); we should just bypass this function entirely


Test pysat mag vect

Changed the arctan function in Fortran File. The sign and values of the result are now consistent with the atan2() method in Python.

Replaced by an updated pull request.


Is it possible to preload a model into the Coral Edge TPU and keep it there for some time?

For a software project, I want to do object detection with many individual images over some time (hours/days).
When using the Coral Edge TPU Accelerator (USB) on a RasPi 4 (4 GB) with the Raspberry Pi OS (I tested versions with Debian 10 or Debian 11), the performance for analyzing single images by just using the CPU is faster compared with using the Coral TPU.
Here, some measurements of this code

Without the Coral USB Accelerator:
$ time python3 TFLite_detection_image_modified.py \
--modeldir=/home/pi/model_2021_07_08 \
--graph=detect.tflite \
--labels=/home/pi/model_2021_07_08/labelmap.txt \
--image=testimage.jpg

real	0m1,174s
user	0m1,236s
sys	0m0,754s

With the Coral USB Accelerator:
$ time python3 TFLite_detection_image_modified.py \
--modeldir=/home/pi/model_2021_07_08 \
--graph=detect_edgetpu.tflite \
--labels=/home/pi/model_2021_07_08/labelmap.txt \
--edgetpu \
--image=testimage.jpg

real	0m3,831s
user	0m1,118s
sys	0m0,729s

I also tried a loop over 170 images and the result was a real time less than 2 minutes without the Coral Edge TPU Accelerator (USB) compared with more than 10 minutes when using the Coral TPU.
The reason is probably as mentioned here and on other places like here: the first inference on Edge TPU is slow because it includes loading the model into Edge TPU memory. Thus when using the Coral USB Accelerator to several image files, the model is loaded into the TPU memory for every image file. This overhead does occur just a single time when a video file or stream is processed.
If this is the root cause for the bad performance, I see only two possible solutions:

Copy the model into the Coral TPU memory in advance and avoid loading it for every image (is this possible?) or
Provide a stream instead of single images.

If these assumptions are correct, is using the Coral TPU useful at all for analyzing single images?
Is it possible to speed up the process of loading the model into Edge TPU memory?
Can I load a model into the Edge TPU memory and keep it there for some time?
Thanks for any help.

Yes, It is possible to load a model into the Edge TPU. The script you are using also loading model into interpreter for only once when passing image directory as input. Can you please share the detect.tflite model you are using. Thanks!

But I never execute the script for a group of images. Only for single image. The most recent one.
The workflow is: I create an image with the camera and execute the script for object detection for exactly this new image. And I do this this in an infinte loop.
The question is: Can I load the model into the Edge TPU memory and keep it there for some time?
And can I do object detection for a single image file without loading the model prior into the Edge TPU memory by telling to use the already uploaded one?

Okay, I think, It is not possible to preload a model into the Coral Edge TPU and keep it there for some time.
We can pass images in image directory or stream of images to avoid loading it for every image.
Feel free to check the streaming examples from this repo: https://github.com/google-coral/examples-camera. Thanks!

But this way (if I collect a number of images and do the object detection when I have a number X of images available), it is no longer "real time". I still hope there is another solution that includes working with single images but still performs well.

Yes, It is possible to load a model into the Edge TPU. The script you are using also loading model into interpreter for only once when passing image directory as input. Can you please share the detect.tflite model you are using. Thanks!

The total script execution is more for single image when running edgeptu model is because of the time taken to make edgeptu interpreter line vs cpu tflite interpeter.

From what I can gather you have some other process which is saving images into a folder and then you trigger your python script to run inference on the images in that folder? Instead of creating a new edgetpu interpreter every time, you need to have a long running script that creates the interpreter, loads the model then loops indefinitely processing images as they become available.

@cdrose This is a very good idea. Probably the approach that requires the least change to my existing software. I will try this way.

@hjonnala As you suggested, I did some timing tests to find out where most time is lost, and responsible is not the line where the invoke-operation happens:
interpreter.invoke()
This operation (here) costs approx. 2.75 seconds on a Raspberry Pi 4:
    interpreter = Interpreter(model_path=PATH_TO_CKPT,
                              experimental_delegates=[load_delegate('libedgetpu.so.1.0')])

This finding does not change anything (I still need to rewrite my code), but it is worth knowing.

Feel free to reopen if you have any questions. Thanks!


Morphdom 2.0

For now each component is a class to avoid clearing html.
We could use morphdom to reduce components to functions returning html.

Nah, I’m fine.


incsearch not works in NVIM v0.10.0

See https://github.com/neovim/neovim/issues/28800

incsearch works for me in vscode-neovim with Nvim 0.10. I type something, it highlights as I type, and navigates to the first match.
what symptoms are you seeing? https://github.com/neovim/neovim/issues/28800 mentions low-level details.

Sometimes it works normally. You can try this in the JSON file (settings.json).


chore: Switch from edx-sphinx-theme to sphinx-book-theme

The edx-sphinx theme is being deprecated, and replaced with sphinx-book-theme.
This removes references to the deprecated theme, replaces them with the new
standard theme for the platform, and updates the theme configuraiton to use the
new theme.
Testing instructions:

Run make docs or make html in the docs directory and see that the docs are generated properly and use the sphinx-book-theme

See https://github.com/openedx/edx-sphinx-theme/issues/184

Thanks for the pull request, @xitij2000!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
This is currently a draft pull request. When it is ready for our review and all tests are green, click "Ready for Review", or remove "WIP" from the title, as appropriate.

:+1:

[N/A] I tested this: doesn't have docs
[x] I read through the code

@xitij2000 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


remove incorrect comment

As far as I can tell, "no messages available" is impossible -- we size our message pool such that there's always a message.
Pre-merge checklist
Performance:

[ ] Compare zig benchmark on linux before and after this pr.# benchmark results before
...

# benchmark results after
...

OR

[X] I am very sure this PR could not affect performance.

bors r+


iOS 9 not working

Hi,
the plugin is not working in iOS9, it doesn't open.
Any updates for this?

We're using it on iPhone with iOS9 and haven't found any issue. It behaves the same as 8.4 for us.


feat(tests): add expect and toBe resources

Closes #154
What I managed to add is expect and toBe resources, however test() resource is not defined, despite that it's declared in index.d.ts file.  Also, test (and other test-related resources) are missing in jestEnvironment.global dictionary.
It's possible that extra steps are needed, for example adding a piece of code like:
  const jasmineFactory = runtime.requireInternalModule<
    typeof import('./jasmine/jasmineLight')
  >(JASMINE);
  const jasmine = jasmineFactory.create({
    process,
    testPath,
    testTimeout: globalConfig.testTimeout,
  });

  const env = jasmine.getEnv();
  const jasmineInterface = jasmineFactory._interface(jasmine, env);
  Object.assign(environment.global, jasmineInterface);

(source: https://github.com/facebook/jest/blob/master/packages/jest-jasmine2/src/index.ts#L44)
This code snippet is ugly, so I didn't dare to add it to our code.  I suggest we just content ourselves with expect and toBe.
Here is how an error looks - as if it was a pure jest:

Ideally your screenshot would show the problematic AskScript code. That's probably something that will require more iterations on this integration. For this PR let's keep it simple

Ideally your screenshot would show the problematic AskScript code. That's probably something that will require more iterations on this integration. For this PR let's keep it simple

Good idea for future enhancements. Filing it as https://github.com/xFAANG/askql/issues/291

@czerwinskilukasz1 thanks for creating issues for follow ups. I do think actually that these two points should be fixed here:

[ ]  allow .test.ask to run independently (no .test.result.ts etc)

By the way, if we allow .test.ask to run independently, shouldn't .test.result.ts and .test.args.ts be renamed to .result.ts and .args.ts, because they are used for .ask and not for .test.ask?

By the way, if we allow .test.ask to run independently, shouldn't .test.result.ts and .test.args.ts be renamed to .result.ts and .args.ts, because they are used for .ask and not for .test.ask?

Maybe, let's figure this out on a separate issue

By the way, if we allow .test.ask to run independently, shouldn't .test.result.ts and .test.args.ts be renamed to .result.ts and .args.ts, because they are used for .ask and not for .test.ask?

Maybe, let's figure this out on a separate issue

Filing as https://github.com/xFAANG/askql/issues/293


Refactor group and metadata functionality to support different types of indexes

This PR refactors the infrastructure for TileDB groups and metadata that are used to represent indexes.  It builds on, and supersedes, work started in lums/sc-37627/indexivfflat-group-schema, which was not turned into a PR.  Once #162 and #173 are merged, the changes in this PR should be fairly self-contained and reasonably-sized.
Features

The refactoring includes a (shallow) class hierarchy that builds on the base index_group and index_metadata classes.
We use CRTP to extend the index_group and index_metadata classes.  CRTP provides static polymorphism and also allows the base and derived classes to call each other's members.
The URIs for arrays in a group are relative to the group URI (this differs from the Python).

Operational Overview

A TileDB-Vector-Search index is represented by a TileDB group, which in turn comprises the arrays necessary for using the index.
Any TileDB index class contains a group index class that provides the API for storing and retrieving data and metadata for the index.
Index group classes for specific indexes are derived from index_group and the corresponding metadata classes are derived from index_metadata

The class for the flat l2 index is flat_l2_index defined in flat_l2_index.h.  It uses the base group and metadata classes, index_group and index_metadata, which are respectively defined in index_group.h and index_metadata.h
The class for the ivf flat index is ivf_flat_index, defined in ivf_flat_index.h.  It uses the group class ivf_flat_index_ group, defined in ivf_flat_group.h and ivf_flat_index_metadata, defined in ivf_flat_metadata.h.  ivf_flat_index_group and ivf_flat_index_metadata respectively derive from index_group and index_metadata.

The functions that the "derived" classes need to provide to index_group are

append_valid_array_names_impl();
create_default_impl();

These are invoked by the base class for inserting the names of the arrays that will comprise the group, and for creating the corresponding TileDB arrays.

The functions that the "derived" classes need to provide to index_metadata are

metadata_string_checks_impl()
metadata_arithmetic_checks_impl()
json_to_vector_impl()
vector_to_json_impl()
dump_json_impl()

These functions provide reading and writing of metadata for the associated derived group.

To support updates to arrays in the index, all of the arrays in a group have an extent of MAXINT.  The actual size of the data stored in each array is kept as metadata within the group.

IVF Flat Index

The arrays in the TileDB group for an IVF Flat index are

partition_centroids
partition_indexes
shuffled_vector_ids
shuffled_vectors

The metadata maintained for the base Index are

// The first group are replicated from the Python API
base_sizes                       // A list of sizes
dataset_type                   // What this dataset is for ("vector_search")
dtype                                // A string representing the python type of the vector features
index_type                       // A string indicating what type of index this is ("IVFFlat")
ingestion_timestamps    // A list of timestamps at which data was originally ingested, or re-ingested from updates
storage_version              // What version of the index ("0.3")
temp_size                        // Size of the temporary storage

index_kind                         // An int corresponding to C++ enum for type of index (string is better in this case)
feature_datatype              // An int representing the TileDB datatype enum for the vector features
feature_type                      // A string representing the Python type of the vector features
id_datatype                        // TileDB datatype enum for vector ids
id_type                               // Python type of ids

Lists are kept in json arrays.

Additional metadata maintained for the IVF Flat Index are:

partition_history               // List of partition sizes for each timestamp
px_datatype                       // TileDB datatype enum for partition indices
indices_type                      // Python type of partition indices

Although the types of the features, ids, indices, and so forth can be read from the corresponding arrays, we keep that information as metadata so that we don't have to incur the overhead of opening an array just to check its type.
There is some redundancy in terms of the information that is stored.  In a future PR we should streamline this.  There is danger in the use of the enum for index_kind -- it is not versioned and so could change if the enum definition is changed.

Notes

A group representing an IVF Flat Index for the "siftsmall" example has been added to the repository.  The arrays within the group are not compatible with the non-updatable arrays used for testing of queries, etc. since the group arrays have infinite extent and the non-updatable arrays do not.  The default for opening a TileDB array representing a matrix or a vector is to use the extents as the matrix or vector dimensions.  Functions using the "infinite extent" arrays obtain the dimensions from the metadata and pass the dimensions explicitly to the matrix and vector readers.
The PR currently only contains the group and metadata mappings for version 0.3, but infrastructure is in place to support other versions (older and newer)
The PR should be compatible with the Python API for FlatL2 and IVFFlat indexes (version 0.3), though this has only been lightly tested
PR #173 has been merged into this PR (and #162 was merged into #173).
There are placeholders for flat pq and vamana indexes.  When those are implemented, the corresponding group and metadata classes will be created.  The derived functionality for the ivf flat index is not very large; we expect the classes for other indexes to be similarly straightforward.

Superseded by #221.


update all services and compose files to latest in Docker Hub

Confirm that all of the docker images in both our own deployment and also in sample docker compose files all use the latest and greatest.

Done - published signing service for did:web.


[Feature Request]: Please add sipeed RV BL702 board as mcu target to run examples

Please add  "sipeed RV plus Debugger BL702" board support as mcu target.
It would allow for the favorable setup with two sipeed BL702 boards: one as mcu and one as debugger.
Also Iam looking for the way to connect two boards as JTAG debugger for one another. If you know the correct wiring please let me know.
Thank you

bl702 default JTAG pin are list：TMS(GPIO0)、TDI(GPIO1)、TCK(GPIO2)、TDO(GPIO9),so if you wants to connect two boars as JTAG debugger for one another,you should connect one TMS、TDI、TCK with another TDI、TDO、TMS，then there is TDO with TCK left, TDO is GPIO9,and is led0 on rv debugger ,its location is align with TMS pin on board,so you need to solder a wire to the resistor right on the right side of the led and link this pin to JTAG TCK. Finally ,you can debug with two boards.

https://bbs.bouffalolab.com/d/61-rvddebuggeropenocdbl706/7
There are pictures in this post to illustrate, you can refer to it.


Fix NWC support detection

It worked with Mutiny because Mutiny only supports pay_invoice so the resulting array only contained a single element with value pay_invoice.
With wallets that supported multiple methods, the single element no longer matched pay_invoice.
https://github.com/stackernews/stacker.news/assets/27162016/1ad2e5a2-e48c-419d-a099-a643ccf524d5
I think that's what every stacker encountered with red indicators but no error message since there is indeed no toast if pay_invoice support was not detected.

Woot. Lfg

This did not fix for me when using https://github.com/benthecarman/nostr-wallet-connect-lnd
It seems you are separating by comma, but the nip defines it as space separated

Have a fix for alby: https://github.com/getAlby/nostr-wallet-connect/pull/247

Could just parse with split(' ') after parsing with split(,) and then both would work, right?

Yes that's kind of what ben did in #855.
But you can't do it exactly like you described:
> "foo,bar".split(",")
[ 'foo', 'bar' ]
> "foo,bar".split(",").split(" ")
Uncaught TypeError: "foo,bar".split(...).split is not a function


Update dependencies for Kotlin 1.3-M2

Update Kotlin version to 1.3-M2
Update kotlinx.coroutines-core to 0.25.3-eap13

Fixes #19

Thanks! I'll release later or tomorrow or Monday

Any news on this update?

Tomorrow. I have other releases to make. Thanks for the poke!


feat: Resampling Benchmarks and Quirks

Closes #15 #21 #41

Requires #53

I don't think we need this PR. I think that we should include a link to the gist of the notebook though. Where do you think this should go? https://gist.github.com/mogwai/a5df03e89ab33bc0a5648965280d5445


Add renovate.json configuration

What does this PR do?:
This PR adds the renovate.json configuration for the registry repo. The configuration will cover 2 things:
Stack image updates
The renovate bot will look inside the registry directories for devfile.y(a)ml files and try to update an image (looking for "image:") tag. For every different image found it will create a new PR. So if two different stacks use the same image, one PR will be created updating both image tags. On the other hand if we have 2 different images to update, it will create a PR for each one of them. Note, that images with "latest" tag will not be updated.
In order to remove the usage of variable values or latest (1 case) version, some tags have been updated to a fixed value. For nodeJS 16 the version was taken from all other stacks using the same image. On the first run, renovate should create a PR to update all of them.
Github Actions
Renovate will also look on every run, to update any deprecated github actions. All updates for github actions will be included on the same PR.
Documentation
The contributing.md guide was updated in order to emphasize to the usage of non-latest image tags when creating new stacks
Next steps
After merging this PR we need to follow all instructions here in order to add the registry project to the self hosted renovate bot.
Which issue(s) this PR fixes:
fixes https://github.com/devfile/api/issues/1139
fixes https://github.com/devfile/api/issues/1138
PR acceptance criteria:

[x] Contributing guide
Have you read the devfile registry contributing guide and followed its instructions?
[ ] Test automation
Does this repository's tests pass with your changes?
[x] Documentation
Does any documentation need to be updated with your changes?
[x] Check Tools Provider
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)

How to test changes / Special notes to the reviewer:

/retest

/retest

/retest

Aside from the feedback looks good! You also might need to contact the stack owners for approval on these stack changes.
cc: @BethGriggs @ajm01

@michael-valdron thanks for the review
I've updated the PR with the suggested changes and I've added @BethGriggs & @ajm01 as reviewers

@scottkurz @mezarin Also tagged the java-liberty stack owners to review

I have sent DMs to both @BethGriggs and @ajm01 under the Kubernetes community slack workspace, I would say give them an additional day or so to respond.

/lgtm

@ajm01 @mezarin and @scottkurz kind reminder for the review request of this PR :) Thanks a lot!

Hi, I'm sorry this slipped past us and I'm just noticing this now.
The bigger issue here is that we have not been very current in updating the Liberty stack images, (the last one was <IP_ADDRESS>).  Whether this change is made or not, our image is still almost two years old at this point.  Perhaps we need to consider abandoning our custom image and building a devfile based on a well-known Java/Maven image with a "tools"-type of component.
I'm getting ahead of myself.  Let's ignore that bigger issue though and just talk through the PR here:
If I understand it correctly, this might not be of too much value given the way the four Liberty stacks are maintained at the moment.   They use special-purpose Liberty images developed for devfile use cases (for purposes such as caching Maven dependencies in the image) rather than more general Liberty images.
So for the team updating these stack images, it's not too much more work to send a PR to this devfile registry repo at the same time.
That said, maybe it's still nicer to manage the versions getting updated via renovate and not having this extra PR to approve and merge.
The only problem though is that the two Gradle stacks use the liberty-version variable in the run command:

commandLine: echo "gradle run command"; {{gradle-cmd}} -Dgradle.user.home=/.gradle libertyDev -Pliberty.runtime.version={{liberty-version}} -Pliberty.runtime.name=wlp-javaee8 -Pliberty.runtime.group=com.ibm.websphere.appserver.runtime --libertyDebug=false --hotTests --compileWait=3

So updating the image version without updating this version variable as well could lead to a confused experience.
Not sure where that leaves us.   Maybe we should just exempt the Liberty stacks?

Hi, I'm sorry this slipped past us and I'm just noticing this now.
The bigger issue here is that we have not been very current in updating the Liberty stack images, (the last one was <IP_ADDRESS>). Whether this change is made or not, our image is still almost two years old at this point. Perhaps we need to consider abandoning our custom image and building a devfile based on a well-known Java/Maven image with a "tools"-type of component.
I'm getting ahead of myself. Let's ignore that bigger issue though and just talk through the PR here:
If I understand it correctly, this might not be of too much value given the way the four Liberty stacks are maintained at the moment. They use special-purpose Liberty images developed for devfile use cases (for purposes such as caching Maven dependencies in the image) rather than more general Liberty images.
So for the team updating these stack images, it's not too much more work to send a PR to this devfile registry repo at the same time.
That said, maybe it's still nicer to manage the versions getting updated via renovate and not having this extra PR to approve and merge.
The only problem though is that the two Gradle stacks use the liberty-version variable in the run command:

commandLine: echo "gradle run command"; {{gradle-cmd}} -Dgradle.user.home=/.gradle libertyDev -Pliberty.runtime.version={{liberty-version}} -Pliberty.runtime.name=wlp-javaee8 -Pliberty.runtime.group=com.ibm.websphere.appserver.runtime --libertyDebug=false --hotTests --compileWait=3

So updating the image version without updating this version variable as well could lead to a confused experience.
Not sure where that leaves us. Maybe we should just exempt the Liberty stacks?

Hey! No worries! I think the best options would be to exclude for now those stacks from the automation.
I think we can re-visit those stacks once we have more releases. This way we can have also the time to investigate a solution to use renovate with variables like liberty-version.
Just tfyi, with the current workaround the reviewer would be responsible to update the liberty-version variable value in case of a renovate update.
I'll come back shortly and exclude those stacks from this PR.
cc @michael-valdron  @scottkurz

@scottkurz & @michael-valdron I've reverted all updates to "liberty-related" stacks. I've also added a rule in renovate.json to ignore the paths of these stacks just to unnecessary error logging on the renovate runner.


AttributeError: module 'tensorflow' has no attribute 'session'

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or a feature request.
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 (64bit)
TensorFlow installed from (source or binary):
TensorFlow version (use command below): 1.4
Python version: 3.6
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Why in tensorflow 1.4 when running validating command in sess = tf.session() Line gives this error? is Session attribute changed in 1.4 version of tensorflow compare to previous versions Like 0.12?
Source code / logs

import tensorflow as tf
hello = tf.constant ('hello, tensorflow!')
sess = tf.session ()
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'tensorflow' has no attribute 'session'

tf.Session has an upper-case S.

I have the problem too,my tf version is 1.13.1,I use tf.Session,but can't run
AttributeError: module 'tensorboard' has no attribute 'Session'

So do I ...
and my code is:

sess = tf.Session()
Traceback (most recent call last):
File "", line 1, in
AttributeError: module 'tensorflow' has no attribute 'Session'

import tensorflow as tf
#Session used in tensorflow 1.*
#when you use tensorflow 2.* you can try the following codes
g = tf.Graph()
with g.as_default():
a = tf.constant(3.14)
b = tf.constant(10)
c = tf.constant("Hello world!")
with tf.compat.v1.Session(graph=g) as sess:
print(sess.run(a))
print(sess.run(b))
print(sess.run(c))


Pool Connections

Pooling connections will improve performance--especially when using encryption which makes opening a connection more expensive. (Part of #412)
This would also allow us to make CreateFunction(), etc. calls persist between closing and re-opening a connection obviating the need for #354.

@bricelam would this also be an excuse to implement auto-prepared statements (assuming it isn’t implemented yet)?

Nice... If you work on prepared statements, consider also persisting them across pooled open/close, otherwise they're useless in short-lived connection scenarios.

@divega  Is someone having a hard look a SqlClient for these performance improvements, would likely hit a wider audience?


How about xls ?

Is there any tips de convert xlsx to xls ?
Thank you ?

Not with this library, sorry.


feat: Add dynamic completion for --cpu-family

What does this fix or implement?
It's fairly easy to misconfigure a server or k8s node pool by using a CPU family that is not available in the datacenter.
I've added a completer that fetches a datacenter if the corresponding flag was already provided and completes according to what is available.
When --datacenter-id is not specified, the default list is returned.
This should make interactive usage of ionosctl a bit less error prone.
Checklist

[x] PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
[x] Tests added or updated
[ ] Documentation updated
[x] Sonar Cloud Scan
[ ] Changelog updated and version incremented (label: upcoming release)
[ ] Github Issue linked if any
[ ] Jira task updated

Returning the default list when no datacenter ID is provided is great. I tested this and it works very well!
Thank you for your awesome contribution! :tada:


External npm packages

Hello
Does the grafana plugin allow for bringing in external npm plugins?
Thanks

@yosiasz Do you have a specific plugin in your mind? The library has to be compiled and loaded with the plugin to use.
Apache ECharts panel already included the most popular extension, and we can add more if required.

Gotcha, I was just asking in general. There was a question on grafana about FFT and that got my wheels spinning. Thanks

https://community.grafana.com/t/how-to-add-custom-transformation/79963

@yosiasz It should be possible, and I replied as well.
Thank you.


Docs don't have link styling

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Links on the docs looks 100% like text. For example the word "why" in the screenshot is a link.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
Visit https://draftjs.org/docs/getting-started.html and try to find any of the links
What is the expected behavior?
Links should at least have an underline or a distinct color. I wanted to create a PR but the problematic CSS is not part of this project.
a {
  color: #3B3738;
  text-decoration: none;
}

.mainContainer .wrapper a,
.inner .projectIntro a {
  text-decoration: none;
}

The react docs use both underline and a light background color. I recommend to do the same.

Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
n/a

Looks like this is fixed now, possibly due to the recent Docusaurus update.


Wrong numbers for numbered list in tutorial #5 - Identify users

Tutorial #5
Under Add Email/Password Sign In via Firebase Authentication
The numbers for numbered list are wrong. It should be-
Before your application can access the Firebase Authentication APIs on behalf of your users, you will have to do enable it:

Go to the Firebase console and open your project.
Open the Authentication page and click the "Sign-in Method" tab. Then enable the Email/Password authentication provider.
Press save.

@iulukaya This one is for you!


Additional plot line styling options

Description
This PR adds additional line styling options.
As requested in DSEGOG-192, the user can now change the marker style (and size):

Currently the marker size range is set to 1-10.
Available marker styles: circle, cross, crossRot, dash, line, rect, rectRounded, rectRot, star, triangle and None.
User can also change the line width:

Again, the range is set to 1-10.
Additionally, marker colours can be changed independently of the plot line:

Testing instructions

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage

Agile board tracking
connect to DSEGOG-192

Changed the custom NumberInput to MUI's TextField, removed the marker colour option and made the requested formatting changes.


Set-cookie headers get overridden

Hi,
I really like the library so far, but I have one issue regarding multiple headers with the same key.
A lot of web servers/frameworks, when returning multiple cookies, send multiple Set-cookie headers in the response, but because of this piece of code (because a map instead of a keyword list is used) the headers get overridden.
Is there a workaround around this (I'm using the hackney adapter)?
I would be glad to fix this, just point me in the right direction :)

Well, I've decided to make the headers a Map simply because it is convenient (i.e. resp.headers["content-type"] syntax), but this does has a cost of overriding duplicate headers.
I think I'd like to keep that as the default (unless there is some other nice solution), but there should be a way to override this behaviour.
For now I have two ideas:

Make the Normalize middleware optional (which will break all current code using tesla)
Save raw headers into Tesla.Env so that they can be accessed when needed.

I guess the 2 would be better (could maybe be even generalized as env.raw_response). Let me know what do you think of that.

I like the option 2 more, but correct me if I'm wrong: the env.raw_response would be different depending on the adapter you are using?
Maybe make a way to provide your own normalize functions when building a client (actually when injecting the middleware)?

Yes, the raw_response would depend on adapter (not perfect ofc)
I think we could split Normalize middleware into NormalizeBody /
NormalizeHeaders etc and the have a module attribute @normalize false to
prevent injection of all middlewares so that one can choose what to
include.
Having said that I am not a big fan of "magic by default that can be turned
off" . Maybe there should be a HeadersMap middleware extracted and
mentioned in the readme.
@hodak @smoku Any opinions on this one?
On Sat, 24 Dec 2016 at 01:02, Bogdan Habic<EMAIL_ADDRESS>wrote:

I like the option 2 more, but correct me if I'm wrong: the
env.raw_response would be different depending on the adapter you are
using?
Maybe make a way to provide your own normalize functions when building a
client (actually when injecting the middleware)?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/teamon/tesla/issues/37#issuecomment-269058617, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAfk2dV4Cmh8N3zTQY9qAE4FQsRTTysks5rLGEtgaJpZM4LVHRo
.

@teamon maybe you could add something like this (I can clean this up and add tests if needed) :)

I gave this some more thought: how about letting the default_middleware function be overridable, and keep the rest of the code like in my previous comment?

Hey @BogdanHabic, sorry for the delay 🎄 (I'll also be off since tomorrow until 3.01)
The longer I think about this one the more convinced I am to make a breaking change in favour of Tesla.Middleware.HeadersMap optional middleware. In the README the first example of a client is already using three middlewares (BaseUrl, Headers and JSON) and I think one more should not be a big issue - I definitely should add some more comments to that first example anyway.
This way it is explicit that headers will be a map and there is no need for overrides.
I'll get back on that later next week and check the impact of such change in my production projects.

Hey @teamon, happy holidays!
If I can help in any way, do let me know. :D

Questions / TODOs:

[ ] How big is the impact on existing codebases?
[ ] How to make Headers middleware work with both Map and List?
[ ] Should Normalize middleware still convert headers to String & downcase?
[ ] How to handle headers access required by middlewares like JSON?
[ ] Improve README

@BogdanHabic After giving this a lot of thoughts, to implement the first option (switch to map) would result in:

How big is the impact on existing codebases?

changing all calls to env.headers["foo"] into something like Tesla.get_header(env, "foo") - not cool, but not that crazy or impossible

How to make Headers middleware work with both Map and List?

possible matching both cases and using appropriate modules functions (List/Map)

Should Normalize middleware still convert headers to String & downcase?

probably not, but that would make headers lookup much slower

How to handle headers access required by middlewares like JSON?

all access would have to go via Tesla.get_header(env, name)

Any other downsides?

pattern matching on headers map is out, no more this

Considering all the above I'm more in favour of providing env.orig_headers :: [{String.t, String.t}] plus a utility function Tesla.get_orig_header(env, name) that would perform a case-insensitive search in the orig_headers list.
Btw @amatalai, does this use case match any of the :private ones?

@teamon I like the solution you described.
Just a quick question: Why would the search be case-insensitive?
If you need the original headers, not the normalized ones, I would assume you would also know the casing of the header?

Arr, you're right (it's late...). I guess we don't really need that function at all (using Enum.find/filter should be enough)

@teamon You could also store it as a map where the key is the header, and the value is a list of header values.
That way you get quick lookup, and for headers you know have just value you can use hd (or wrap it into a get_single_orig_header).

@teamon yes, things like :raw_headers and/or :raw_body is what I would like to store inside env.private :)

Are there any workarounds for now? I'm working with a webserver that sends multiple Set-Cookie headers and I'm new to the lib so I couldn't think of a quick solution.

@edupc Easiest/fastest workaround which I can imagine right now is to fork Tesla and change normalize middleware to save raw headers in env.opts.
Something like this:
# this code wasn't tested in any way
defmodule Tesla.Middleware.Normalize do
  def call(env, next, _opts) do
    env2 =
      env
      |> normalize
      |> Tesla.run(next)

    env2
    |> Tesla.put_opt(:raw_headers, env2.headers)
    |> normalize
  end

...
end

Btw I'm planning to make some proposal PR in next few days that will cover both this issue and #48

@amatalai Thank you, it seems I had to check the result of Tesla.run(next) for errors, but that and a little change to one of the tests was enough to get it working. I'll be waiting for a proper solution :)
This was the exact changes if someone is interested:
# lib/tesla/middleware/core.ex
defmodule Tesla.Middleware.Normalize do
  def call(env, next, _opts) do
    env2 =
      env
      |> normalize
      |> Tesla.run(next)

    case env2 do
      env2=%Tesla.Env{} ->
        env2
        |> Tesla.put_opt(:raw_headers, env2.headers)
        |> normalize
      other ->
        normalize(other)
    end
  end

  ...
end

Hey guys,
I fixed this issue by populating duplicate headers as a list in the headers map:
https://github.com/farhadi/tesla/commit/048391f6e7906ad735b1dc8f91fa3d9a5770cf77
let me know what you think.
I can write tests if the solution is acceptable to be merged.

How about the ability to prepend middleware? Then one could do some work before Normalize and tuck whatever is needed away into env.

Apropos to this discussion: https://stackoverflow.com/questions/4371328/are-duplicate-http-response-headers-acceptable

How about the ability to prepend middleware? Then one could do some work before Normalize and tuck whatever is needed away into env.

I think duplicate headers like set-cookie are too common to be handled manually, the library should support them by default.

I'm sorry @farhadi, but your solution is not acceptable - it leads to almost nondeterministic behaviour of headers map values being sometimes lists and sometimes binaries requiring the end user to check for both cases.
I think the only reasonable approach here is to make a breaking change, with Normalize returning headers as map(binary => [binary]) plus a separate, backward-compatible middleware SingleHeaders (draft name) that would use only first value for each header thus preserving the current behaviour.

If the map(binary => [binary]) path is chosen I would be more than willing to add it (I actually have a fork that is already doing this, I would just need to clean it up).

I'm 95% percent convinced this is the best way to go. One thing that I'm not sure how to handle yet is how to make other middleware like JSON work correctly when used with or without SingleHeader middleware.
On 23 Jun 2017, 23:18 +0200, Bogdan Habic<EMAIL_ADDRESS>wrote:

If the map(binary => [binary]) path is chosen I would be more than willing to add it (I actually have a fork that is already doing this, I would just need to clean it up).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

What about having a DuplicateHeader middleware which accepts a list of headers that should be returned as a list while keeping others as strings?

Why not just have a utility function which would check if the header exists in the map, and if it does, returns the result of List.first(headers["key"]) or nil if the header doesn't exist?
That way the JSON middleware will instead of accessing the map directly use the helper instead.

With #104 in place it is now possible to do something like this:
defmodule Client do
  use Tesla

  def new do
    Tesla.build_client [], [
      :keep_original_headers
    ]
  end

  def keep_original_headers(env, next) do
    env = Tesla.run(env, next)
    Tesla.put_opt(env, :original_headers, env.headers)
  end
end

and then
iex> env = Client.new |> Client.get("http://google.com")
iex> env.opts[:original_headers]
[{'cache-control', 'private'}, {'date', 'Sat, 07 Oct 2017 16:38:24 GMT'},
 {'location',
  'http://www.google.pl/?gfe_rd=cr&dcr=0&ei=AAPZWfGtM-Sv8weEg4igDg'},
 {'content-length', '268'}, {'content-type', 'text/html; charset=UTF-8'},
 {'referrer-policy', 'no-referrer'}]

@BogdanHabic would that solve your issue?

Yup, the post middleware helps me solve my issue. Thanks!
Pozdrav / Best regards,
Bogdan Habić
On Sat, Oct 7, 2017 at 6:40 PM, Tymon Tobolski<EMAIL_ADDRESS>wrote:

With #104 https://github.com/teamon/tesla/pull/104 in place it is now
possible to do something like this:
defmodule Client do
use Tesla
def new do
Tesla.build_client [], [
:keep_original_headers
]
end
def keep_original_headers(env, next) do
env = Tesla.run(env, next)
Tesla.put_opt(env, :original_headers, env.headers)
endend
and then
iex> env = Client.new |> Client.get("http://google.com")
iex> env.opts[:original_headers]
[{'cache-control', 'private'}, {'date', 'Sat, 07 Oct 2017 16:38:24 GMT'},
{'location',
'http://www.google.pl/?gfe_rd=cr&dcr=0&ei=AAPZWfGtM-Sv8weEg4igDg'},
{'content-length', '268'}, {'content-type', 'text/html; charset=UTF-8'},
{'referrer-policy', 'no-referrer'}]
@BogdanHabic https://github.com/bogdanhabic would that solve your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/teamon/tesla/issues/37#issuecomment-334948234, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFHZaSxJpVryxZSD_dz0iHLDD7Hq4cDUks5sp6mIgaJpZM4LVHRo
.


main: Make runner script and update results script executable

This allows us to drop the `python' prefix.

I have no idea what happened here.


Makefile instead of tool.sh?

A makefile's purpose perfectly fits replacing tool.sh.
While tool.sh gets the job done, it is not the most convenient way.
From a programmer's point-of-view, we need to write the command parsing logic ourselves.
But from a user's - ./tool.sh something isn't more convenient than make something.
Of course, this is just nitpicking at the details. It isn't a real issue or anything.

Will look into it.
I was also looking at tox (with tox.ini file) and it looks ideal for python projects. Any experience with that?

I do. But unless we introduce tests and requirements, we don't need to create multiple virtual envs (using tox).


Import JSON sample

Adding a import JSON sample in R.

[celebrate]     Jennifer Jo Simeon reacted to your message:

From: MeWu-IDM @.>
Sent: Monday, October 28, 2024 8:12:13 PM
To: InstituteforDiseaseModeling/data_access_library @.>
Cc: Jennifer Jo Simeon @.>; Author @.>
Subject: Re: [InstituteforDiseaseModeling/data_access_library] Import JSON sample (PR #6)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@MeWu-IDM approved this pull request.
—
Reply to this email directly, view it on GitHubhttps://github.com/InstituteforDiseaseModeling/data_access_library/pull/6#pullrequestreview-2400110278, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BKEGILCWJTHGZJCA2PLYOOTZ52LB3AVCNFSM6AAAAABQYEQ6V6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMBQGEYTAMRXHA.
You are receiving this because you authored the thread.Message ID: @.***>


Refactor the whole lib

Overview
This library had some issues, let's refactor it.
Replace Expo by a React Native example app, bridged by a custom Metro config.
Test Plan

[x] Example project works on Android.
[x] Example project works on iOS.

This is unmerged since March and paralyzes any further contributions until it is merged. Is it fair to assume this project is deprecated?


[RFC] merge pull request vs squash and merge

Is there a way to make squash and merge the default behaviour when we press the GREEN button?

It’s already the default afaik

I don't think so. https://github.com/mne-tools/mne-python/commit/c6e62d6c11c557cd69ce0b4e88bb17b5ca8c47dd is a merge commit that it should not be there if I had taken more care when clicking the green button

You can disable options, but I don't think we want to do that. IIRC it defaults to whatever you as a maintainer did in your previous green-button-click.


Refactor and migrate suse pipelines to upstream repo

Is your feature request related to a problem? Please describe.
Parent Issue: https://github.com/SUSE/kubecf/issues/220
This task requires following pipelines to be moved to upstream repo:

cf-deployment
external-releases
buildpacks

Describe the solution you'd like
The plan is to keep the pipelines compatible while addressing following items in upstream repo:

Make required changes in deployment script for it to deploy updated pipelines.
Redundancy while building release images must be addressed.
Ability to build multiple release versions using a simple yaml structure needs to be implemented.
Ability to bump releases must be introduced.

Additional context
This task is subject to following items:

Gain access to IBM infrastructure(using lastpass) to deploy and test pipelines.
Make all the required secrets available for the pipelines to be deployed.
Make sure concourse versions are compatible.

Based on feedback from @troytop we might have to re-scope this task to keep the two pipelines separate while figuring out a mechanism to share the pipeline codebase.

Based on recent developments, the home for these pipelines should be:https://github.com/cloudfoundry-incubator/kubecf/tree/master/.concourse

As per @viovanov we can rename the cf-operator-ci repo to kubecf-ci and make that home for all release image related pipelines.

@bikramnehra we have an internal story related to buildpacks pipeline for the coming sprint so I do not know the impact that moving them will have. Let me sync with @thardeck about it.

As discussed, broken the task in two chunks - other task is: https://github.com/cloudfoundry-incubator/kubecf/issues/601


run tests in SauceLabs

Your polyfill is awesome! It's important for you to test it in many browsers to make sure that it works.
I've added support to run tests in many browser which provide SauceLabs. Here is results of my latest launch.

There is many fails in the last test Match results from browsers with native support. If you want to run tests in yourself, you should create an account on SauceLabs and set your API key as described in grunt-saucelabs readme.
You can add it into travis as encrypted environment variable
Always glad to help!

Thanks for the compliments and the very relevant nudge on CI cross-browser testing.  I'll try to take a closer look at this PR sometime this week and get it rollin' live. :+1:

Thanks, this really helped me identify why the polyfill wasn't behaving the same as the native method. See #7 for details.
That said, I went ahead and changed the setup to use Karma for running the tests both locally (configured primary for a Mac with lots of browsers installed :wink:) and on SauceLabs during the TravisCI process. We'll see what the results of the next build look like.... :grimacing:


Maintainer wanted

I'm currently reviewing PRs on a best-effort basis, which may take a month or so. If someone is willing to co-maintain this, that'd be great.

I'd be willing to co-maintain. We depend on this transitively through https://github.com/rust-lang/rust-bindgen so I don't want to see it abandoned.

I'm happy to help out too, for the same reason. Not sure I can do active development, but I should've time for reviews and so on :)

@jethrogb Do you still need comaintainers?

Both @jrmuizel and @emilio were added as co-maintainers


Reading and training concurrently

I would like to explore the possibility of reading data in one thread and training a model in another thread. For instance we should be able to read from a CSV file in one thread and train a model in another thread at the same time. While the model is training on one mini-batch, the next mini-batch can be prepared at the same time. AFAIK this is what PyTorch's DataLoader is for.
I've had a quick at it but it didn't bring any performance boost. Here is the code:
import concurrent.futures
import itertools
import queue

from creme import compose
from creme import datasets
from creme import linear_model
from creme import metrics
from creme import preprocessing

def produce(q, stream):

    for batch in stream:
        q.put(batch)

    q.put(queue.Empty)

def consume(q, model, metric):

    while True:
        batch = q.get()
        if batch == queue.Empty:
            break
        for x, y in batch:
            yp = model.predict_one(x)
            metric.update(y, yp)
            model.fit_one(x, y)

metric = metrics.ROCAUC()

model = compose.Pipeline([preprocessing.StandardScaler(), linear_model.LogisticRegression()])

X_y = datasets.CreditCard().take(20000)

q = queue.Queue(maxsize=1)

def chunk_input_stream(input_stream, chunk_size):
    while True:
        chunk = list(itertools.islice(input_stream, chunk_size))
        if chunk:
            yield chunk
        else:
            return

with concurrent.futures.ThreadPoolExecutor(max_workers=2) as executor:
    executor.submit(produce, q, chunk_input_stream(X_y, 32))
    executor.submit(consume, q, model, metric)

And here is the "straightforward" version:
from creme import compose
from creme import datasets
from creme import linear_model
from creme import metrics
from creme import preprocessing

metric = metrics.ROCAUC()

model = compose.Pipeline([preprocessing.StandardScaler(), linear_model.LogisticRegression()])

X_y = datasets.CreditCard().take(20000)

for x, y in X_y:
    yp = model.predict_proba_one(x)
    metric.update(y, yp)
    model.fit_one(x, y)

print(metric)

I'm not an expert in parallel computing, from what I know Python multithreading only executes one thread at any given time. See here and here for detailed explanations

Yep I totally get that. But, if a job is I/O dependent (such as reading a CSV file from the disk), then concurrency can help.

IMO the problem here is that our program isn't spending significant time waiting for something to happen to benefit from concurrency... sorry if I'm wrong, I'm not very experienced with those things

Yeah you're probably right!

I'm happy to close this now. Reading speed was bothering me a bit, but now that we have implemented stream.Cache reading is less of a bottleneck.


Add optimized motion profile for straight trajectories

Add an optimized trapezoidal or s-curve motion profile that doesn't use numerical integration and its corresponding follower.

Implemented in branch dev/main and should be stable. Will probably be merged after dynamic followers are implemented.


How to get total number of stored records?

I'm using the flat file dictionary.
Is there a way to query the total number of records stored without having to create a cursor and iterate over all records?

The system does not maintain a count of the number of records by default. You could add a count variable to one of the data structures and maintain it when inserts/deletes occur.


Add ftdetect check for .hugo_build.lock

This commit adds an additional file type detection check to ensure html files will get the proper htmlhugo file type if saved before adding any template delimiters.  I find myself in this situation all the time.
This proposed check searches recursively upward from the directory of the current file for a .hugo_build.lock file and succeeds if found.
The original checks have been left to support pre-0.89.0 versions of Hugo.

Thanks!


Remove TextSerializerFactory in API 5+

As it stands, it's been deprecated since API 3.x and remains deprecated in 4.x. It's current uses are strictly for the legacy formatting code usages, which honestly should be done in the implementation alone, not in the API.
I suppose @Minecrell would have more to say about its removal.

@gabizou I disagree on legacy formatting codes being implementation-only. Not everything uses § or &, and there should be a way to create a new FormattingCodeTextSerializer:
public interface FormattingCodeTextSerializer extends SafeTextSerializer {

    static FormattingCodeTextSerializer create(char character) {
        return Sponge.getRegistry().createFormattingCodeTextSerializer(character);
    }

It has always been deprecated in terms of that it is not recommended to use for new projects, however that is not an indicator that it should be removed. It's provided for plugins to use for converting older configurations etc.

Isn't is deprecated because the equivalent functionality can be achieved with TextSerializers.formattingCode?
Sponge.getRegistry().getTextSerializerFactory().getFormattingCodeTextSerializer('&');
// Same as
TextSerializers.formattingCode('&');

Oh, if you're referring to that, then yes - it is. The factory itself is deprecated because it is only the accessor for the implementation, it shouldn't be used by plugins directly.


Video quality is so terrible in Pakistan and south asian region, that i am frstrated also no updates for months now

Please could you update the voice quality and video quality

It's better to submit a new ticket to agora support for this issue.

i wish i could send, but having weird build errors in xcode 13 :( due to agora pods

Can you raise another issue of the build errors cause it's off-topic of this issue?


Fix version in composer json

Pull Request Test Coverage Report for Build 49

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 58.947%

Totals

Change from base Build 43:
0.0%

Covered Lines:
56

Relevant Lines:
95

💛  - Coveralls