Cache support

Hi,
It would be great if unirest had support for a pluggable cache, just like the browser's local cache.
I see many packages on npm that support specifying a TTL for each request - but I'd much rather take advantage of HTTP and actually read the response headers, and cache the response in memory for the appropriate amount of time (either expire, or max-age - age).
In a sense, this is very similar to a reverse-proxy. Do you think this could be part of unirest? Could it be some sort of plugin, where every request/response traverses the proxy and it decides whether to call the backend or returned cached data?
If the interface is nice & clean, I could imagine several implementation of that proxy, e.g. in memory, backed by Redis... Ideally they would each have smart limits depending on their constrains (memory limit, number of responses, LRU....).
Happy to help implement this if you think it would be useful.

this issue was actually raised from another company too, they could not use unirest-node bcz of no cache.

Thanks. Our current stop-gap solution is to call unirest, but wrap every call in a special handler to decide whether to make the call, cache the response, etc. Some built-in support would be amazing.

This is not something that is within the scope of the library, this should be done outside of the library (a plugin would be fine, separate repo), per use case basis.

Thanks. Our current stop-gap solution is to call unirest, but wrap every call in a special handler to decide whether to make the call, cache the response, etc. Some built-in support would be amazing.

This is the correct way to do it, as it is a per case basis, not everyone will have the same requirements or situation as yours.
Hence why being a plugin would be a better solution for this situation.

Fair point @Nijikokun. About a "plugin", I can imagine two different approaches:

we have to wrap unirest

This is pretty much what we currently do, but it quite painful to implement if you want caching across the board. If we want an easy drop-in solution, we could create a library that wraps unirest to support typical caching/proxy concerns.  On the downside it would have to delegate the entire unirest API. For example, in the end function below, the proxy would check if that request is in cache, call unirest if it's not, and cache the response on the way back before calling the callback.
var proxy = new InMemoryProxy();
proxy.get('http://awesome/api')
         .set('Accept', 'application/json')
         .end(function(res) {});

pluggable plugin support

This would let unirest take an optional reverse proxy to pass every request/response through. The proxy receives every Request object on the way out, and can optionally cancel them (e.g. if it was returned from cache), and gets every Response object on the way in as well.
unirest.get('http://awesome/api')
          .set('Accept', 'application/json')
          .through(myProxy)
          .end(function(res) {});

Also minor comment on not everyone will have the same requirements or situation as yours, I wouldn't think these are crazy requirements. We're talking about caching, which is one of the fundamental pillars of the web, and has well defined standards across browsers, reverse proxies, etc... But agreed that a plugin of some sort would make sure people can handle any type of requirements they have :smiley:

Plugins could be hooked like middleware, global plugins, and local plugins,
I like the .through but maybe it could be .plugin
On Wed, Feb 11, 2015 at 4:39 PM, Romain Prieto<EMAIL_ADDRESS>wrote:

Fair point @Nijikokun https://github.com/Nijikokun. About a "plugin", I
can imagine two different approaches:

we have to wrap unirest

This is pretty much what we currently do, but it quite painful to
implement if you want caching across the board. If we want an easy drop-in
solution, we could create a library that wraps unirest to support typical
caching/proxy concerns. On the downside it would have to delegate the
entire unirest API. For example, in the end function below, the proxy
would check if that request is in cache, call unirest if it's not, and
cache the response on the way back before calling the callback.
var proxy = new InMemoryProxy();
proxy.get('http://awesome/api')
.set('Accept', 'application/json')
.end(function(res) {});

pluggable plugin support

This would let unirest take an optional reverse proxy to pass every
request/response through. The proxy receives every Request object on the
way out, and can optionally cancel them (e.g. if it was returned from
cache), and gets every Response object on the way in as well.
unirest.get('http://awesome/api')
.set('Accept', 'application/json')
.through(myProxy)
.end(function(res) {});
—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/unirest-nodejs/issues/47#issuecomment-73996073
.

:+1: on plugin, which could be as simple as plugin.request(request) that returns true if the plugin handled it, and plugin.response(response) just before calling the end callback.

Closing since this was agreed to be a plugin

Hi @Nijikikun, I'm happy to help write the plugin... is there a plugin interface / system already? I thought that was the current blocker (e.g. no request.get('/foo').plugin(bar).send()). Given plugins are likely to want to inspect/manipulate both requests and responses, something similar to Connect/Koa middleware would be great.

I think I will open an issue to address perhaps a plugin specification, that way we can come up with something, I haven't had time to think about as of right now. Working on a new release with all these backlogged items


Devise Secret value Distribution

Distribution of devise_secret value
devise_secret allows AAD to send outgoing email.  We've been using SF's SMTP server (we are so bad) and now we are switching over to our own SMTP server which requires our own devise_secret.
Anyway, we need to address how to distribute the devise_secret to developers without putting it into the repo.
Problem:

a devise_secret can only be provisoned to developers by the Heroku admin
admins shouldn't have to do distribute the devise_secret value

Solution:

mitigate the distribution problem by NOT distributing the devise_secret
turn off access to SMTP related code when devise_serect not found
provide user/developer with console warning about the missing value.
setup a unit test to detect the missing devise_secret environment variable
point the developer to instructions on configuring an email solution

devise_secret allows AAD to send outgoing email

Does it?
My understanding is the secret is simply a pseudorandomly generated value ($ rails secret) used to encrypt account data on the server. I don't believe there is any risk involved in sharing a secret for local development as long as that secret is distinct from production.


Spellflags fix reorganization #1255

Regarding this issue, #1255 I think the issue is the length of the flags, I looked through the other flags and seems like there has been free 2 spaces.
I moved the two new ones there and now they work.
Thoughts?

Which def do you have in your scripts for no_elementalengine and randomdecay? Because the code in the source seems legit and for some reason those flags aren't yet been added in the x scriptpack

Which def do you have in your scripts for no_elementalengine and randomdecay? Because the code in the source seems legit and for some reason those flags aren't yet been added in the x scriptpack

It was added by xwerox by one of the monstrous PRs 😁 We probably forgot to add it in Xpack but I added it to mine scripts from changelog. I assumed its working, but few days ago find out sphere doest see it if set.

Removed followerslots fix from this PR.


I want to add a Summer-2023 internship from IBM INDIA

Hello sir ,
I'm Raman Kumar Gupta , with GitHub Id - Ramank2002
I did the contribution by adding  IBM Summer 2023 Internship Program | Project & Stipend Based Internship .
Kindly consider it , & for this I'll very grateful to you.
Thankyou.

you have added extra thing , delete mobile app development internship of internshala

I have deleted the Mobile app development internship of internshala as suggest by @avinash201199 sir.
Now please accept my pull request and merge it.
Thanking you,
Raman Kumar Gupta


Sync internal Stash-Repo to GitHub -> what happens in case of pull requests?

I take it, that this is not a two-way mirror. So what happens if we accept a pull request on GitHub? Sounds like the mirror would need to force push then? Is that assumption true? As soon as someone pushes something else to the mirror-repository it stops working?

No comments? Is this plugin no longer maintained?

Correct, it is not a two mirror.
An example git mirror command is:
git push --prune git@github.com:englishtown/stash-hook-mirror.git --force +refs/heads/*:refs/heads/* +refs/tags/*:refs/tags/*

https://github.com/englishtown/stash-hook-mirror/blob/develop/src/main/java/com/englishtown/stash/hook/MirrorRepositoryHook.java#L127


Switch to using Swift 2.1.1

Also need to update all the stuff in Jenkins.

There's a lot of duplication of the latest Swift version, we should keep that in a variable to share across the script.

build.sh still needs to be updated to work with ios-swift 2.1.1, the ios device tests & ios7-static.

:+1:


Fixing numbering of workflow steps (or remove numbering)

Currently we have two step 8's in main.nf ---
/**************************************************
| 8. TAXONOMIC ASSIGNMENT WITH KRAKEN - PRE-DEDUP |
**************************************************/
...
/**********************************
| 8. COLLATE AND PROCESS RESULTS |
**********************************/

Any reason to not just call the second one step 9?

This could also be a good point to consider how steps are labeled in main.nf. I think having numbers to refer to the big sections is quite useful for structuring how we document the pipeline in the README, and more generally having a way to refer to where in the general workflow something happens. But using numbers is a bit brittle/burdensome when we want to add a NF workflow or NF process, since we might then have to update all following numbers (I'm guessing that's what happened in this case).
I wonder if instead it might ultimately be better to just drop the numbers, and use the NF workflow and process names (rather than {Workflow#} for the section and {Workflow#}.{Process#} for the processes), since (I think) these names are already unique identifiers. So,
/**************************************************
| workflow CLASSIFY_READS_SUBSET - TAXONOMIC ASSIGNMENT WITH KRAKEN - PRE-DEDUP |
**************************************************/
...
/**********************************
| workflow PROCESS_OUTPUT - COLLATE AND PROCESS RESULTS |
**********************************/

(In this case I'd recommend not using capitalization for the description after the "-" to make it more distinguishable from the workflow name; the *'s already clearly mark this as a section header

I think the numbers (especially process numbers) are quite helpful for finding the right section of the document, but they sure are annoying to keep updated.
I expect we'll probably split out the big workflow file into multiple separate subworkflow files sometime soon, which will obviate the need for numbers entirely. In the meantime, I'll go fix the numbers.

I expect we'll probably split out the big workflow file into multiple separate subworkflow files sometime soon, which will obviate the need for numbers entirely. In the meantime, I'll go fix the numbers.

Yea, I was thinking this could be the way to go.
Am I right that processes are in principle independent of a workflow --- e.g. the same process could be used in multiple workflows?

The original request is now rendered moot by the module/subworkflow structure now implemented in the dev branch.
@mikemc:

Am I right that processes are in principle independent of a workflow --- e.g. the same process could be used in multiple workflows?

This is basically correct given a module structure like that implemented in the dev branch. The main caveat is that, rather than calling the same module multiple times in a workflow, you need to import in multiple times with different aliases and then call each alias exactly once. But that isn't a huge amount of additional overhead.


feat(RichTextEditor): add picasso-forms wrapper

FX-2511
Description
We are adding a new wrapper for the RichTextEditor in picasso-forms
How to test

Open the storybook for Form, there's an example for the RichTextEditor, check on submitting and the validations

Review

[ ] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-bot run all

@toptal-bot run all

@toptal-bot run deploy:documentation

@augustobmoura @TomasSlama when I checked the implementation of RichTextEditor, I couldn't see any callback props about onFocus and onBlur. WDYT about a solution like this:
    const { handleFocus, handleBlur } = useOnFocus({
      editorRef,
      toolbarRef,
      wrapperRef,
      onFocus: useCallback(() => {
        setIsEditorFocused(true)
        onFocus?.() // notify final-form that this input has been focused
      }, [setIsEditorFocused]),
      onBlur: useCallback(() => {
        setIsEditorFocused(false)
        onBlur?.() // notify final-form that this input has been blurred
      }, [setIsEditorFocused]),
      dispatch
    })

@TomasSlama when I type some values and delete them back, I can't see any empty state for the editor. I think it will bring doubts to the user. WDYT?
https://user-images.githubusercontent.com/7733167/158538527-e6d6a12d-0111-487d-a893-3e06dc51d7f4.mov
Suggestion: when I was working on another richtext editor wrapper, I was checking if any renderable text exists after each typing and calling onChange with an empty string if none of them left to notify form library that this editor has no value anymore. WDYT about my suggestion 🙂

@ozgurkececioglu good suggestion, I have created separated task for it https://toptal-core.atlassian.net/browse/FX-2549

@augustobmoura @TomasSlama when I checked the implementation of RichTextEditor, I couldn't see any callback props about onFocus and onBlur.

That is true, I forgot about wiring onFocus and onBlur. I will do it right now

@TomasSlama when I type some values and clear the input afterwards, I can't see any empty state for the editor. I think it will bring doubts to the user.

I noticed that problem and I would talk about it today with you guys. It looks like an issue in quill, it should be easily to workaround on our side

I can submit an empty field. That shouldn't be possible.
The way to reproduce this is:

Insert any text.
Delete all text.
Submit the form.


[FLINK-27119][tests] Use try-with-resources for JobMasters

Cut out from #19351.

@flinkbot run azure


Update the Go SDK roadmap for April 2020

Remove things that are complete, update things with an overall plan for the next few months to get Batch out of experimental.
Include date to better indicate freshness.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @aaltay @kennknowles @youngoli


Build Script Updates

References #116

[ ] Support launching Notebook without reinstalling

Experimented with different implementation options, spent way too long trying to debug bash script, put up PR.
[t:90]


Debug: Hovering on same object is not moving the hover

VSCode Version: Latest insiders
OS Version: OSX

Steps to Reproduce:
let obj = {field:1,b:2}

let test = ()=>{
    console.log(obj)
    console.log(obj.field)
    debugger
}
test()

In the video, I am trying to move the mouse over two occurrences of obj

This is a current limiation of the debug hover.
Closing this as will not fix since I do not think it is a big limitation. Actually might be prefereble in some cases


Completions take over a second to appear in a new file on a large project

Bug Report

🔎 Search Terms
auto completions complete suggestions performance slow vs code typing
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about performance

⏯ Playground Link
N/A
💻 Code

Clone and checkout https://github.com/unsplash/unsplash-web/tree/typescript-completion-performance, branch typescript-completion-performance. This is a private repository but I believe some members of the TS team already have access from debugging previous issues. If you don't have access, please send me your email address so I can provide access (TS team members only).
Run yarn to install TS
Open VS Code, navigate to the file app/helpers/my-test.ts and wait for TS to finish initialising

Type O. and wait for completions to appear.
🙁 Actual behavior
Completions should appear quickly.
🙂 Expected behavior
Completions appear slowly.
tsserver.log
https://user-images.githubusercontent.com/921609/123950498-a79a5600-d99b-11eb-8da0-24d2b1ee9199.mov
In the TS server log we can see that completions are slow:
Info 1961 [11:58:01.660] request:
    {"seq":8,"type":"request","command":"completionInfo","arguments":{"file":"/Users/oliverash/Development/unsplash-web/app/helpers/my-test.ts","line":3,"offset":2,"includeExternalModuleExports":true,"includeInsertTextCompletions":true}}
Info 1962 [11:58:01.660] Starting updateGraphWorker: Project: /Users/oliverash/Development/unsplash-web/tsconfig.app.json
Info 1963 [11:58:01.841] Finishing updateGraphWorker: Project: /Users/oliverash/Development/unsplash-web/tsconfig.app.json Version: 2 structureChanged: false Elapsed:<PHONE_NUMBER>9745893ms
Info 1964 [11:58:01.841] Different program with same set of files:: structureIsReused:: 2
Info 1965 [11:58:01.843] getCompletionData: Get current token: 0.007962003350257874
Info 1966 [11:58:01.843] getCompletionData: Is inside comment: 0.03854600340127945
Info 1967 [11:58:01.843] getCompletionData: Get previous token 1: 0.015626996755599976
Info 1968 [11:58:01.844] getCompletionData: Get previous token 2: 0.1929429993033409
Info 1969 [11:58:01.844] getCompletionsAtPosition: isCompletionListBlocker: 0.3775179982185364
Info 1970 [11:58:01.850] collectAutoImports: starting, not resolving module specifiers
Info 1971 [11:58:01.850] collectAutoImports: module specifier cache size: 0
Info 1972 [11:58:01.999] getSymbolToExportInfoMap: cache miss or empty; calculating new results
Info 1973 [11:58:02.589] getSymbolToExportInfoMap: caching results
Info 1974 [11:58:02.589] getSymbolToExportInfoMap: done in<PHONE_NUMBER>005813 ms
Info 1975 [11:58:02.847] collectAutoImports: done in<PHONE_NUMBER>001149 ms
Info 1976 [11:58:02.847] getCompletionData: Semantic work: 1002.4234960004687
Info 1977 [11:58:02.978] getCompletionsAtPosition: getCompletionEntriesFromSymbols:<PHONE_NUMBER>0213718
Perf 1978 [11:58:02.996] 8::completionInfo: elapsed time (in milliseconds) 1336.2221

The response for the completionInfo command contains an enormous body (see full log file) which seems to describe the exports for every single module in the TS project. I find this surprising considering we're only asking for the exports of one module.
I tested this in a fresh VS Code instance with no extensions.
I also tested this in a new folder and it was much faster.
tsserver.log
https://user-images.githubusercontent.com/921609/123950483-a36e3880-d99b-11eb-807e-140e4ecba225.mov

I think what you’re looking at is the completions request for when you typed O, not when you typed ., and we’re probably just not cancelling the previous request soon enough. Actually, I know we don’t check the cancellation token during some of those auto-import tasks that can potentially take a long time. If you look a bit closer at the server log, does that match what you’re seeing? One surefire test would be to restart TS Server after you’ve already typed O and let . be the first/only thing you type.

One surefire test would be to restart TS Server after you’ve already typed O and let . be the first/only thing you type.

Yes that's significantly faster!

I was hoping I could workaround the slowness by disabling auto imports / import suggestions, but from the logs it looks like TS still "collects" the auto imports regardless of these settings:
"typescript.suggest.includeCompletionsForImportStatements": false,
"typescript.suggest.autoImports": false,
"javascript.suggest.autoImports": false,
"javascript.suggest.includeCompletionsForImportStatements": false

"typescript.suggest.includeCompletionsForImportStatements": false should definitely work... https://github.com/microsoft/TypeScript/blob/837ed9669718fa3515aabc99974abe91f7254a3e/src/services/completions.ts#L1841

Are these two different settings or are they the same thing?

includeCompletionsForImportStatements
includeCompletionsForModuleExports

Perhaps VS Code needs to add a new setting to pass through the includeCompletionsForModuleExports setting to TS?

Oh yeah, those are different. includeCompletionsForImportStatements is for completions at import s|, added in 4.3. includeCompletionsForModuleExports is for auto-imports generally.

When I disable this, no auto-import related work shows up in the logs for me.

When I disable this, no auto-import related work shows up in the logs for me.

I just tested it again and I'm definitely seeing collectAutoImports take up a lot of time.
Here is a video to demonstrate. You can see that the relevant setting is disabled.
https://www.dropbox.com/s/wgfdw0aycg7g4bl/Screen Recording 2021-07-22 at 07.48.34.mov?dl=0
tsserver.log
Are you able to reproduce using my steps from the original post above, i.e. inside of the unsplash-web repo?

Ah, it’s on completion details that it’s building the map. Ok, I can fix that.

@OliverJAsh actually, I think I already did. The log you just sent me is for TS 4.3.4. I’m pretty sure I fixed that issue in #44713. Can you send me a log showing the issue with the nightly build, if it repros there? I think it shouldn’t.

I can confirm that this is fixed in the nightly. When I enable the setting I no longer see collectAutoImports in the logs. 🎉


[Misconfiguration?] Control + Tab in OSX displays popup, not switching

VSCode Version: Code - Insiders 1.16.0-insider (f1a3bc4f714123eaff5e15ad976d7f403cc1bfa2, 2017-08-11T05:08:07.764Z)
OS Version: Darwin x64 16.6.0 (macOS Sierra)

Steps to Reproduce:

Open 2+ files
Hit Control + Tab

A few releases ago Control + Tab used to work pretty well.  I mean, okay, well, you guys added a popup... but without focus! so I can't even use my arrow keys to choose the file (like in ST). This misbehavior (it wasn't working like this a few releases ago...) disrupts my current workflow and it is an unexpected change.
There's nothing in the settings either to restore the default behavior. Please stop playing around with hotkeys :(
Is there any way to fix this? Thanks!

@darkguy2008 you can navigate in that popup by just pressing the Tab key again and when you release you get to the editor.
There is another more stable popup with input box where arrow keys are working but I encourage you to try the Ctrl+Tab one

Hello @bpasero, actually I updated my VSCode to version Code - Insiders 1.16.0-insider (0b6da14128b4e61e331193f18786e8db2792a643, 2017-08-11T19:14:29.146Z) and the error seems to have been fixed. Somehow the previous version lost focus in the popup and releasing the Tab key didn't work :)


Enhancement - Swap Left Click and Right Click of Tray Icon

While using HotBin I've noticed that there is no option to change the left click and right commands for the tray. Coming from MiniBin and TrayBin I'm used to having the left click and right click commands reversed. Is there any way we can get an option to swap these commands?

Hello, dburow03. I appreciate your feature requests.
I will consider showing the Tray Menu on left-click instead of opening the Recycle Bin on-left click.
The lack of configuration and features is intentional. HotBin is simple access to the Recycle Bin from the System Tray.

In the next release, left-click and right-click will show menu, middle-click will open the recycle bin folder.
A future release might include percentage. Determining the percentage requires parsing the registry for each drive and calculating, and determining how the user's locale displays percentages – #%, %#, # %, or % #.
Thank you for your contribution.

https://github.com/warg0x4e/HotBin/releases/tag/<IP_ADDRESS>


How to deal with the integer values of RVQ

Hi author,
I've been experimenting with encoding audio using your fantastic method, and I noticed that the RVQ (Residual Vector Quantization) values I obtain are integers like the follows:

I'm curious if this is expected behavior. Additionally, I'm interested in using these encoded features for downstream tasks, but I'm unsure about how to adjust these integer values for training purposes. Would it be appropriate to apply normalization techniques such as min-max scaling or Z-Score normalization? The distribution of these encoded feature values is unknown to me, so I'm seeking guidance on how to handle them effectively for training.
Any advice or suggestions on how to deal with these encoded feature values would be greatly appreciated.
Thank you!

Hi, these integers simply correspond to the indexes of the codebooks in the different quantizers.
I don't really think you will be able to do anything interesting only with these indexes. Trying to do something with the codewords associated with these indexes should be more interesting in my humble opinion.


[FancyZones] Cannot drag maximized windows

Microsoft PowerToys version
0.67.1
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
FancyZones
Steps to reproduce

Maximize a window
Click on the title bar and start dragging

✔ Expected Behavior
Window unmaximizes and is draggable
❌ Actual Behavior
Nothing happens
Other Software
Microsoft Windows [Version 10.0.19044.2486]. Works on another Windows 10 version though.

Also happened at 0.67 - the fix at https://github.com/microsoft/PowerToys/pull/23926 did not fix the issue.

Same issue on Windows 11 22H2 22621.1105
Running as admin: yes
Issue on 0.67.0, installed via Windows Store
Then auto-updated to 0.67.1, same problem

It is possible that this isn't related to PowerToys. I am able to resolve the issue by re-enabling the Windows 11 "Snap Windows" feature.

With this disabled, I can't drop windows that are maximized.

Hi, thank you for reporting. Can you please attach a /bugreport to help me investigate the issue? Does it happen with any window or with specific apps? Tried to reproduce it locally with no luck.

The .zip file contains too much information to disclose to the public. I can share it privately.
@lazynooblet is right
With following setting on Windows 10, it works fine again:

In other words: If "Snap windows" is "Off" drag and drop of maximized windows does not work:

The setting can be found at "Settings" > "Multitasking"

Thanks for the clarification, with system snap off I can't drag maximized window either.
However, testing indicated that the issue could be reproduced without FancyZones running, and as such, it appears to be outside the scope of FancyZones' responsibility.


implementing set_authorizer

It allows to control unsecure query entered by user - during compilation of statement you can allow/deny any sql operation like select, insert, or create index.

This is awesome, and the code looks pretty perfect.  Thanks!
There's only one thing that I noticed that I think you forgot.  The Connection.Close() method needs to unregister its callback from the global "registry".  But since I took a while to get to this, I'll just accept this and add it.


Add an explicit expression threshold to dotplot

This also adds an option to calculate the mean only over the cells expressing given genes. I think these options give users more flexibility to binarize expression. For example, for z-score normalized data, a combination of expression_threshold=-1 and use_raw=False binarizes the expression using a cutoff value corresponding to one sd away from the mean.
Also the obs_bool = obs_tidy.astype(bool) was erroneous for scaled data without the .raw since both positive and negative values were mapped to True.

@fidelram; I gave you write access to the repo so that you can quickly merge PRs like this to your plotting API. It would still be great if bigger chunks of new functionality continued to come in PRs, which you could then merge yourself upon a brief check by any of us. Does that sound right?

@gokceneraslan Thanks for the PR. I hesitated in the past to add such functionality as this makes the definition of expression very ad hoc. However, I also noticed the pitfalls when you have only normalized data and the dotplot does not makes sense. Are you planning any further changes?
@falexwolf Thanks for giving me write access. I will use the new status responsible.

@fidelram Thanks, no further changes. I agree about the arbitrariness but I think it's good to provide a configurable implementation with reasonable defaults. This is also what we do in other functions like HVG.

Cool! Great to have you with write access, @fidelram! :smile:


Type inconsistency

https://github.com/googleapis/google-auth-library-nodejs/blob/89daaac8e1230935ed80733ac9c2cd89079e2f04/samples/idTokenFromServiceAccount.js#L47
The type does not contain this fuction something seems to be incorrect here.

Thanks for raising this issue @chaim0m, I will provide a fix shortly.


[New Port Request]

Library name: OpenSceneGraph
Library description: The OpenSceneGraph is an open source high performance 3D graphics toolkit, used by application developers in fields such as visual simulation, games, virtual reality, scientific visualization and modelling
Source repository URL: https://github.com/openscenegraph/OpenSceneGraph/tree/OpenSceneGraph-3.6.4
Project homepage (if different from the source repository): http://www.openscenegraph.org/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

sorry, my fault, it's already included.

sorry, my fault, it's already included.

I do not find it …

sorry, my fault, it's already included.

I do not find it …

I find it, it called osg, not openscenegraph.


Does it have the capability to learn.

Can It build on intelligence. And learn what its doing and slowly improve?

Yes the recent update has been focused on purely intelligence. However there is no "it" specific entity. The performance varies from language model to language model. Right now this mod performs the best with gemma2.
Which can of course remember past conversations, store conversations and whatever events happened in the world.
In the future update I am trying to build a "feedback loop" system where it can retrieve it's past actions and differ on what's right and what's wrong, and learn and build on that.
But yes so far you can have really intelligent conversations with the bot, or gemma2 in this case.

@EuphorianXD If you are interested in the technicalities of how it works, you can try reading the readme file!


Logging Worker Service Dependency Tracking

I am trying to use ILogger as its recommended that we don't directly inject TelemetryClient but I noticed some oddities doing this and perhaps I have configured something incorrectly.
In a nutshell, I am injecting ILogger and doing some logging. For example:
        using (var scope = this.logger.BeginScope(new Dictionary<string, string>
        {
            { "MyReference", "HelloWorld" }
        }))
        {
            this.logger.LogDebug("Foo");
            this.logger.LogInformation("Bar.");
            var response = await this.httpClient.PostAsync(..); // dependency tracking
        }

What I've noticed is that we don't get depedency tracking being aggregated for free like we do if it was an ASP.NET application. Am I missing something in terms of config? I can see trace lines but the dependencies tracked are against an entirely different operationId and not collated when searching it in the portal. How do I aggregate the two? The only way I have been able to do this is to use TelemetryClient directly when writing my logs.
For example, if I did the same thing  but injecting TelemetryClient in the trace lines and depedency calls are aggregated.
        var op = this.tc.StartOperation<RequestTelemetry>("MyReference", "HelloWorld");
        op.Telemetry.Id = "HelloWorld";
        op.TrackTrace("Foo");
        var response = await this.httpClient.PostAsync(..); // is tracked in AI

I have hooked in App Insights via services.AddApplicationInsightsTelemetryWorkerService();
Using:

NET Core 3.1.101
Microsoft.ApplicationInsights.WorkerService, Version="2.12.0"
Microsoft.Extensions.Hosting, Version="3.1.0"
Microsoft.Extensions.Logging, Version="3.1.0"

What I am expecting to see is when I search for "HelloWorld" in the AI Azure Portal it should aggregate all the logs made within that scope.

The approach using telemetry clients StartOperation is the right way of doing it as documented here:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/worker-service#net-corenet-framework-console-application
ILogger scopes cannot be used to group together telemetry.


make skfem.models a subpackage

An empty __init__.py in skfem/models makes Python recognize it as a subpackage.  For #19.

Thanks for this. It would be convenient to have an automated way to test the installation workflow. Also, the model subpackage should be expanded. I will make a new pip release later today or tomorrow and check that this is indeed fixed.


Run tests with fb v2 v3 and v4

Changes
Continuous integration in Github now tests:

building, clippy, code formatting
FirebirdSQL versions 2.5-ss 3.0 4.0
linking, dynamic_loading
client, embedded
coverage

This is a follow up to #25.

Follow up:

testing (v2, dynamic_loading) looks like a orange factor because testing (v2, linking) succeeded on same test.
testing (v4, linking) and testing (v4, dynamic_loading) are failing but the tests can fixed in further commits/PR.

The V4 versions are failing as the installed client library is version 3.0.2, but the firebird 4.0 needs the Srp256 authentication implemented only in client versions 3.0.4 and above

On my local computer:
I do not fear computers. I fear the lack of them.
    -- Isaac Asimov
 23:07:21  ~  🙂
👉 apt search firebird-dev
Sorting... Done
Full Text Search... Done
firebird-dev/focal,now <IP_ADDRESS>220.ds4-1build2 amd64 [installed]
  Development files for Firebird

 23:07:55  ~  🙂
👉 uname -a
Linux D2019599 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

But ubuntu-latest still defaults to ubuntu-18-04 according to the github docs:
Note: The Ubuntu 20.04 virtual environment is currently provided as a preview only. The ubuntu-latest YAML workflow label still uses the Ubuntu 18.04 virtual environment.

Options for now:

Disable v4 until github upgrades to ubuntu-20-04
Fix ubuntu-20-04 for testing and change it later when github upgrades.

Let's test with fixing ubuntu-20-04. If it doesn't work, we disable the V4 for now.

Upgrading from ubuntu-latest to ubuntu-20-04 installed version 3.0.5.
Most of the errors gone except this error.
Any clues?
(Also testing (v2, linking) still fails and testing (v2, dynamic_loading) don't for some unknown reason.)

I think the cargo tarpaulin can be removed from all jobs except the coverage one to reduce this kind of problem.
About the V2 dynamic, i don't know either.

I think the cargo tarpaulin can be removed from all jobs except the coverage one to reduce this kind of problem.

@jairinhohw

According to the Coveralls Github action documentation there is 2 modes of operation: Standard and Parallel.

The mode that used in the job testing is the parallel: true

Step Run cargo-tarpaulin generates the Lcov coverage file
Step Coveralls Parallel sends the partial coverage to coveralls.io

The mode that used in the job coverage is the parallel-finish:true

This jobs runs after the job testing
Step Coveralls Finished finishes the coverage in coveralls.io

By doing this way, we collect coverage for each configuration defined in the job testing:

This covers linking, dynamic_loading, v2, v3 and v4
As further improvement we can include embeddedlater.

I may have misunderstood something, off course.

There is just one remaining error:

This error is triggered by cargo tarpaulin on firebird=v4
The test failing is: test statement::linking::old_api_select ... FAILED. See the backtrace bellow.
The test fails both in linking and dynamic_loading.

Some possible options are:

Proceed with the test failing and fix later.
Exclude coverage from v4 and enable later after the test is fixed. (If someone would remember...)
Wait for the fix.
Get rid of coverage completely.

About the V2 dynamic, i don't know either.

This failue is Weird* !!!
The steps succeeds with dynamic_loading but fails with linking
The logs on the failure are shorter also.
It needs further investigation.

LOGS
Failing test on V4
---- statement::linking::old_api_select stdout ----
thread 'statement::linking::old_api_select' panicked at 'Error in the transaction: FbError { msg: "deadlock\nupdate conflicts with concurrent update\nconcurrent transaction number is 93", code: -913 }', src/statement.rs:433:9
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:78
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1076
   5: std::io::Write::write_fmt
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/io/mod.rs:1537
   6: std::io::impls::<impl std::io::Write for alloc::boxed::Box<W>>::write_fmt
             at src/libstd/io/impls.rs:176
   7: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   8: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   9: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:198
  10: std::panicking::default_hook
             at src/libstd/panicking.rs:215
  11: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:486
  12: rust_begin_unwind
             at src/libstd/panicking.rs:388
  13: core::panicking::panic_fmt
             at src/libcore/panicking.rs:101
  14: core::option::expect_none_failed
             at src/libcore/option.rs:1272
  15: core::result::Result<T,E>::expect
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libcore/result.rs:963
  16: rsfbclient::statement::linking::setup
             at src/statement.rs:433
  17: rsfbclient::statement::linking::old_api_select
             at src/statement.rs:286
  18: rsfbclient::statement::linking::old_api_select::{{closure}}
             at src/statement.rs:285
  19: core::ops::function::FnOnce::call_once
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libcore/ops/function.rs:232
  20: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/liballoc/boxed.rs:1076
  21: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/panic.rs:318
  22: std::panicking::try::do_call
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/panicking.rs:297
  23: std::panicking::try
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/panicking.rs:274
  24: std::panic::catch_unwind
             at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/panic.rs:394
  25: test::run_test_in_process
             at src/libtest/lib.rs:541
  26: test::run_test::run_test_inner::{{closure}}
             at src/libtest/lib.rs:450
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

failures:
    statement::linking::old_api_select

test result: FAILED. 17 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

Error: "Test failed during run"
##[error]The process '/usr/share/rust/.cargo/bin/cargo' failed with exit code 1

Failing test on V2
Status: Downloaded newer image for jacobalberty/firebird:2.5-ss
2ff45fd5168766b766fdab6e105c97d3972c0c372fb8b96bedb6209387661ab1
##[group]Run docker exec firebirdsql /bin/bash '/usr/local/firebird/bin/createAliasDB.sh' 'test.fdb' '/firebird/data/test.fdb'
docker exec firebirdsql /bin/bash '/usr/local/firebird/bin/createAliasDB.sh' 'test.fdb' '/firebird/data/test.fdb'
docker container restart firebirdsql
sleep 10
shell: /bin/bash -e {0}
##[endgroup]
Use CONNECT or CREATE DATABASE to specify a database
Statement failed, SQLSTATE = 28000
Your user name and password are not defined. Ask your database administrator to set up a Firebird login.
##[error]Process completed with exit code 1.

Successful test on V2
Status: Downloaded newer image for jacobalberty/firebird:2.5-ss
9fc96ffd6f3c036ba5d2188264714ffa6002d391cd3e9f4b57309d98e99dcb23
##[group]Run docker exec firebirdsql /bin/bash '/usr/local/firebird/bin/createAliasDB.sh' 'test.fdb' '/firebird/data/test.fdb'
docker exec firebirdsql /bin/bash '/usr/local/firebird/bin/createAliasDB.sh' 'test.fdb' '/firebird/data/test.fdb'
docker container restart firebirdsql
sleep 10
shell: /bin/bash -e {0}
##[endgroup]
firebirdsql
##[group]Run SQL='select RDB$CHARACTER_SET_NAME as charset_fbv2 from rdb$database;'
SQL='select RDB$CHARACTER_SET_NAME as charset_fbv2 from rdb$database;'
echo $SQL | isql-fb -bail -quiet -z -user SYSDBA -password masterkey 'localhost:/firebird/data/test.fdb'
shell: /bin/bash -e {0}
##[endgroup]
ISQL Version: LI-V<IP_ADDRESS>703 Firebird 3.0
Server version:
LI-V<IP_ADDRESS>139 Firebird 2.5
LI-V<IP_ADDRESS>139 Firebird 2.5/tcp (9fc96ffd6f3c)/P12
LI-V<IP_ADDRESS>703 Firebird 3.0/tcp (fv-az76)/P12

CHARSET_FBV2
===============================
UTF8

Pull Request Test Coverage Report for Build 206124397

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

Files with Coverage Reduction
New Missed Lines
%

rsfbclient-native/src/ibase.rs
3
25.0%

rsfbclient-native/src/connection.rs
25
56.59%

src/connection/mod.rs
25
45.45%

Totals

Change from base Build 202332703:
0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

I done with this PR.
Anybody has any considerations about these changes?

I think that it will be better to change the embedded feature to embedded_tests or something.
I'm approving the changes

I think that it will be better to change the embedded feature to embedded_tests or something.
I'm approving the changes

I'm unsure about what is the best approach related to conditional compilation and this features.
Certainly we can improve further this.

I think that it will be better to change the embedded feature to embedded_tests or something.
I'm approving the changes

I'm unsure about what is the best approach related to conditional compilation and this features.
Certainly we can improve further this.

I agree with the @jairinhohw. We can use prefixs like 'tests_' for features only useds in tests.

Pull Request Test Coverage Report for Build 207619332
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
37 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-8.6%) to 67.971%

Files with Coverage Reduction
New Missed Lines
%

src/connection/mod.rs
18
49.7%

rsfbclient-native/src/connection.rs
19
59.51%

Totals

Change from base Build 202332703:
-8.6%

Covered Lines:
851

Relevant Lines:
1252

💛  - Coveralls


PR 2/2: Add versioned docs

Sister PR to #509 -- please see there for information about this PR.

I know this PR looks huge, but it really just sets the gh-pages branch up to look like this.
The only file in this PR that could require a review is index.html. Everything else is autogenerated.


Trouble with hw_wordsim: Combining PPMI and LSA

In the second homework question for hw_wordsim, we are provided with the following instructions:
Gigaword with LSA at different dimensions [0.5 points]
We might expect PPMI and LSA to form a solid pipeline that combines the strengths of PPMI with those of dimensionality reduction. However, LSA has a hyper-parameter  𝑘  – the dimensionality of the final representations – that will impact performance. For this problem, write a wrapper function run_ppmi_lsa_pipeline that does the following:

1. Takes as input a count pd.DataFrame and an LSA parameter k.
2. Reweights the count matrix with PPMI.
3. Applies LSA with dimensionality k.
4. Evaluates this reweighted matrix using full_word_similarity_evaluation. The return value of run_ppmi_lsa_pipeline should be the return value of this call to full_word_similarity_evaluation.
The goal of this question is to help you get a feel for how much LSA alone can contribute to this problem.

The function test_run_ppmi_lsa_pipeline will test your function on the count matrix in data/vsmdata/giga_window20-flat.csv.gz.

When I construct run_ppmi_lsa_pipeline with the following steps, I get the wrong output:

Reweight input count_df using: ppmi_df = vsm.pmi(count_df, positive=True)
Perform LSA using: vsm.lsa(ppmi_df, k)
Calculate similarities

This leads to a similarity evaluation for men of 0.57. Not the expected 0.16
However, when I construct run_ppmi_lsa_pipeline using the following steps (without applying PPMI), I get the correct output:

Perform LSA using vsm.lsa(count_df, k)
Calculate similarities

This leads to the expected similarity for men of 0.16.
Is there a mistake in the instructions/expected results? Perhaps I did something wrong? Any and all help would be appreciated.

@AndrewLim1990 Many thanks for this! You're quite right: the test is incorrectly assuming an input raw count matrix. I suppose I need tests for these tests! I will push an update later today.

@cgpotts Awesome! Thanks for the update.

This is fixed now. Thanks again!


Fix publishing actions broken by upload-artifact@v4

actions/upload-artifact@v4 had a braking change preventing uploading to the same artifact.
Applied suggested migration: https://github.com/actions/download-artifact/blob/main/docs/MIGRATION.md

@Casyfill could you please take a look? I think I've fixed the issue with the new upload action. Let's try to merge and publish a new version.


Does coral work with 2 cameras on Raspberry Pi

Hi,
Because it is very difficult to get help from coral (you have to fill a long form on google docs) I want to ask here:
Does coral support two cameras for stereo vision?
If I connect 2 cameras to CM4IO board and coral to USB3, does it work?

Hi @kahlenberg could you please elaborate your use case for stereo vision with Coral? Do you have any tflite model that works with the current setup?

Hi,
I don't have any setup yet. I want to make a project with stereo camera for depth estimation.
I wonder if it is possible with coral and two raspberry cameras.

I think, its possible if your your project uses int8 tflite model as Coral USB accelerator used to  run edgeTPU models  (int8 tflite models that are compiled with compiler) for high-speed machine learning inferencing.


Add contributing guide

Hmm  this one does not have the template yet
Just the first version of the contributing guide, with the instructions for issues and PRs
#17 should be merged first
no tests related, this is only documentation

Also addressed @thaorell 's comments from the other repo.


sqrt(4) is ambiguous

https://godbolt.org/z/s57Tqba8o

I hit this today on v2.0.0-development. Any plans on tagging a new prerelease soon?

@dnmiller frankly, that tag isn't much better than main. It's occasionally keeping up with what is in main, I'm a long way from stabilising the API (It will change significantly before is settles down) and there's no special testing or bug-fixing going into the tag. If you're happy to use -v2.0.x-development_ then main -- or whatever SHA it points to today -- should be just as good.
However, I just pushed a v2.0.1-development and it seemed to work. Do you want to try that out?

That worked. Thanks!


Upgrade to Python 3.11

We are still running on Python 3.9.  Supposedly Python 3.11 benchmarks about 20% faster.  Note that Python 3.10 and greater require OpenSSL 1.1.1.

The numba package does not support Python 3.11 yet.

looks like Python 3.11 is supported by numba now.

looks like georgio needs to support 3.11

completed


safety check for null values

merge conflict

Ping, 7 months later. Could use keypather.flatten with what I'm currently working on.

At quick glance this looks good. I am out of town and flying tomorrow. Please bump if I forget

:+1:

<EMAIL_ADDRESS>


Add sentence embedding tool

Sentence Embedding for extracting relevant information
Summary
The prediction_sentence_embedding.py tool is a component of an AI Mech service registered on the Autonolas Mech Hub. The tool executes prediction requests submitted on the Mech Hub and returns a prediction estimation as output. For this the tool performs the following tasks:

Generate search engine queries based on prediction request using the OpenAI API
Submit the queries using the Google custom search API and extract URLs
Iterate over the URLs, extract and clean the text.
Apply spaCy NLP pipeline to the text and extract sentences
Generate sentence embeddings and calculate similarity scores between the prediction request question and each sentence
Concatenate and return the top sentences from each website along with release dates.
Use the extracted information as additional information within a prediction prompt template and pass the prompt to the OpenAI API.
Return the obtained probability estimations along with confidence and additional information utility in json format to the user.

Improvements
The following paragraphs explain relevant changes to the original code.
Generate search engin queries

Use the gpt-3.5-turbo model as it is cheaper and the task is not too advanced

Submit queries and extract URLs

Fetch up to 10 URLs from each query
Add up to three of the fetched URLs to a common set
Only add an URL if it not already present in the common set and if it does not end with ".pdf" (This prevents downloading and processing large files)

Extract and clean text from each website
Extract text

Add request session with user agent header
Allow redirects
Submit a head request before the get request to guarantee the URLs content type is 'text/html'

Clean text

Remove irrelevant html tags and replace them with " " to prevent that surrounding text is concatenated without separation
Remove consecutive occurrences of "." characters

Apply NLP pipeline and extract relevant sentences and release dates

Process the resulting text using a spaCy NLP pipeline and separate it into sentences
Remove duplicate and discard too short sentences that might carry no meaning
Extract the prediction deadline (market closing) date from the prediction request and look for occurrences within the text that could have been discarded due to sentence length. As these sentences could still carry relevant insights, concatenate them with some surrounding context and extract them.
Generate embeddings for the prediction request question and the extracted sentences using the spaCy embeddings model provided by langchain
Calculate the similarity scores (cosine similarity) between the question embedding and each sentence embedding
Sort the sentences descending by similarity score and concatenate them
Extract release and modification date of the websites text by looking for commonly known date identifiers within the html

Generate and submit prediction prompt

Concatenate the processed relevant information from each URL and pass it to the prediction prompt template
Add a variable to the template that represents the current timestamp as a reference time for the OpenAI model

Additional settings and features
OpenAI model settings
The maximum number of completion tokens is reduced to give additional information more room. The temperature for the URL query task is set higher as the results might be more divers, whereas the temperature for the prediction task is set lower as the results should be less variant and more predictable.
Prediction prompt
The prediction prompt is very specific and explains different usecases and how the prediction should be adjusted given these usecases. This leaves less room for unknown usecases and user promt variations. The prompt is specifically designed for a prediction with the binary outcomes "Yes" and "No".
Automatically cap additional information length
The tool calculates the sum of tokens in the prediction prompt template, the received prediction request and the number of tokens reserved for the OpenAI chat completion response and divides the remaining token number that can be used for additional information by the number of URLs that are scraped. This ensures a dynamic token cap for each website's extracted information and prevents model errors induced by exceeding the number of maximal allowed tokens.
Performance and Limitations
The tool has only been tested manually with limited ressources. Here are some qualitative observations comparing the performance between the GPT-4 and the GPT-3.5-turbo model. A quantitative data analysis has not been conducted yet. Thus, the observations are not representative for use in production mode.
GPT-4

Higher accuracy predicting the outcome of a prediction market question
Generates higher probability and confidence values for both outcomes → False positives lead to higher losses

GPT-3.5-turbo

Less accuracy predicting the outcome of a prediction market question
Generates lower probability and confidence values for both outcomes → False negatives lead to lower wins

Any suggestion for this PR @Adamantios ? It's been here for a long time, should we close it?

There is a lot of good work on it, ideally we address issues and merge.

There is a lot of good work on it, ideally we address issues and merge.

Yes, let's merge.

@jhehemann do you think we can merge main and bring this PR up to date?

@jhehemann do you think we can merge main and bring this PR up to date?

@dvilelaf Sure! I merged main and updated some functions. I also reorganized the directory structure to align with the author/customs logic. From my side this can be merged.
I think the checks fail because of issues not related to my code. If you have any suggestions, please let me know.

@jhehemann seems there are some licencing issues. They might be false positives, can you take a look? If they are false-positives, you can add the package here to ignore from the check.

@0xArdi aiohttp was updated and required a new package (aiohappyeyeballs) as dependency. It is licensed under PSF-2.0, so I added it to the tox.ini and updated poetry.lock. There were a few broken links in the readme which I replaced by updated links that work.
All checks pass except for the test. It seems that the api keys are not provided during workflow execution. If there is anything I can do, please let me know.


doc resource in Swagger

/doc response structure unclear (schema: object but no properties)
/doc/schemas/{id} - also add /doc/belgif/{id} ?

Wilcards can't be used for arbitrary subpath depth per OpenAPI spec.

GET /doc has been removed
Issue of listing all referenced schemas should be addressed more broadly outside scope of the demo API.


mkdir /mnt/hdd/electrum-personal-server -permission denied

bitcoin is not in the sudoers file.  This incident will be reported.
getting stuck here with this error while installing EPS. Please help

All sudo commands need to be run as user "admin". The other users are resticted from sudo permissions for security reasons.

It’s a raspiblitz setup had to edit sudoers to allow bitcoin as user to get it working. But having now issues running the server getting error as config file non existent despite following and editing saving the simple file do we have to specify datadir in the config file?

I am not familiar with the RaspiBlitz in detail, I suggest posting the question directly to their repository.
In general it's safe to assume that the "bitcoin" user is not supposed to be sudo. Isn't there a "admin" or "root" user for that purpose?

I used your guide to get EPS Installed which has user as bitcoin there is no separate guide fir raspi blitz EPS yet . I finally seem to get it working will keep you posted


Adding logo to the project

Description
Saturday, September 25, 2021 - v0.3.1
Added:

Closing https://github.com/pesos/browser-history/issues/161.
Logo for the project. Added author name in credits section of the README.md file.

Codecov Report

Merging #168 (f4a1dfa) into master (6453e69) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #168   +/-   ##
=======================================
  Coverage   87.81%   87.81%
=======================================
  Files           5        5
  Lines         476      476
  Branches       88       88
=======================================
  Hits          418      418
  Misses         35       35
  Partials       23       23

Flag
Coverage Δ

unittests
87.81% <ø> (ø)

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

Continue to review full report at Codecov.

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


importing package with same name as source package fails

Importing package with same name as used in source file causes resource leak and fails with:
import failed reading dir /Users/sev3ryn/cue/pkg/github.com/testuser/testpkg: readDir: open /Users/sev3ryn/cue/pkg/github.com/testuser/testpkg: too many open files:
    ./source.cue:4:2

To reproduce - consider folder structure like this
├── pkg
│   └── github.com
│       └── testuser
│           └── testpkg
│               └── test.cue
└── source.cue

source.cue:
package testpkg

import (
	t "github.com/testuser/testpkg"
)

id: string
body: t.Body

This was fixed a while back. Sorry for not having the commit handy.

This issue has been migrated to https://github.com/cue-lang/cue/issues/133.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


[WIP] Test go mod on prow-staging branch

This is using a new Istio-builder image with GO111MODULE=on set so should be ignoring vendor and using go modules. Wondering what will break...

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ericvn
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers: geeknoid, icygalz
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid @icygalz in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS
galley/OWNERS
pkg/OWNERS
prow/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ericvn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Failure:
 make push HUB=gcr.io/istio-testing TAG=5c713e0b7af3bb37078459f7561c4788b60fece2-e2e_bookinfo_envoyv2_v1alpha3
mkdir -p /home/prow/go/out/logs
STATIC=0 GOOS=linux  LDFLAGS='-extldflags -static -s -w' bin/gobuild.sh /home/prow/go/out/linux_amd64/release/istioctl-linux ./istioctl/cmd/istioctl
go: finding github.com/Azure/go-autorest v11.1.0+incompatible
go: finding github.com/googleapis/gax-go/v2 v2.0.4
go: finding github.com/ghodss/yaml v1.0.0
....
go: finding golang.org/x/sys v0.0.0-20190129075346-302c3dd5f1cc
go<EMAIL_ADDRESS>unknown revision v0.2.0
go: error loading module requirements
Makefile:355: recipe for target '/home/prow/go/out/linux_amd64/release/istioctl-linux' failed
make: *** [/home/prow/go/out/linux_amd64/release/istioctl-linux] Error 1

Failure (e2e-pilot-cloudfoundry-v1alpha3-v2):
+ exec prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
/usr/local/bin/entrypoint: line 14: /home/prow/go/src/istio.io/istio/prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh: No such file or directory

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Failure(release-test.sh): Also expected to fail
fatal: Remote branch prow-staging not found in upstream origin

Failure (istio-codecov):
bin/testEnvLocalK8S.sh ensure
Copying /home/prow/go/out/linux_amd64/debug/envoy-debug-542b4fda35046fc9dad5014dbe81f3d5969e63f7 to /home/prow/go/out/linux_amd64/release/envoy
Copying /home/prow/go/out/linux_amd64/release/envoy to /home/prow/go/bin/envoy
Downloading istio.deps from https://raw.githubusercontent.com/istio/proxy/542b4fda35046fc9dad5014dbe81f3d5969e63f7/istio.deps to /home/prow/go/out/linux_amd64/release/istio_proxy.deps
go: finding github.com/jstemmer/go-junit-report latest
go: downloading github.com/jstemmer/go-junit-report v0.0.0-20190106144839-af01ea7f8024
go: extracting github.com/jstemmer/go-junit-report v0.0.0-20190106144839-af01ea7f8024
Code coverage test (concurrency 6)
go: downloading fortio.org/fortio v1.3.0
go: downloading github.com/docker/docker v1.13.1
....
cover: unknown import path "istio.io/istio/pkg/features/pilot": cannot find module providing package istio.io/istio/pkg/features/pilot
make: *** No rule to make target 'localTestEnvCleanup'.  Stop.
vvv

Failure(unit-tests):
=== RUN   TestVersion/sdsclient
--- FAIL: TestVersion (0.28s)
    --- FAIL: TestVersion/pilot-discovery (0.04s)
        version_test.go:60: Field Version was invalid. Got: unknown.
        version_test.go:61: Field GitRevision was invalid. Got: unknown.
        version_test.go:62: Field User was invalid. Got: unknown.
        version_test.go:63: Field Host was invalid. Got: unknown.
        version_test.go:65: Field DockerHub was invalid. Got: unknown.
        version_test.go:66: Field BuildStatus was invalid. Got: unknown.
        version_test.go:67: Field GitTag was invalid. Got: unknown.
   ....
 --- FAIL: TestVersion/galley (0.04s)
        version_test.go:60: Field Version was invalid. Got: unknown.
        version_test.go:61: Field GitRevision was invalid. Got: unknown.
        version_test.go:62: Field User was invalid. Got: unknown.
        version_test.go:63: Field Host was invalid. Got: unknown.
        version_test.go:65: Field DockerHub was invalid. Got: unknown.
        version_test.go:66: Field BuildStatus was invalid. Got: unknown.
        version_test.go:67: Field GitTag was invalid. Got: unknown.
    --- FAIL: TestVersion/sdsclient (0.03s)
        version_test.go:60: Field Version was invalid. Got: unknown.
        version_test.go:61: Field GitRevision was invalid. Got: unknown.
        version_test.go:62: Field User was invalid. Got: unknown.
        version_test.go:63: Field Host was invalid. Got: unknown.
        version_test.go:65: Field DockerHub was invalid. Got: unknown.
        version_test.go:66: Field BuildStatus was invalid. Got: unknown.
        version_test.go:67: Field GitTag was invalid. Got: unknown.
FAIL
FAIL	istio.io/istio/tests/version	0.291s
Makefile:408: recipe for target 'version-test' failed

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-telemetry-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-telemetry-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Also noted that locally, running GOOS=linux GO111MODULE=on make clean init test-bins build docker  docker.push HUB=x TAG=y yields an error:
=> cleaning...
can't load package: package istio.io/istio: unknown import path "istio.io/istio": cannot find module providing package istio.io/istio
make: *** [clean.go] Error 1

Turning GO111MODULE to auto before calling go clean in the make file prevents the error.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-telemetry-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-mixer-k8s-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

prow/integ-telemetry-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-multicluster-e2e-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

The two integ-*-presubmit tests fail elsewhere.

    version_test.go:60: Field Version was invalid. Got: unknown.
    version_test.go:61: Field GitRevision was invalid. Got: unknown.
    version_test.go:62: Field User was invalid. Got: unknown.
    version_test.go:63: Field Host was invalid. Got: unknown.
    version_test.go:65: Field DockerHub was invalid. Got: unknown.
    version_test.go:66: Field BuildStatus was invalid. Got: unknown.
    version_test.go:67: Field GitTag was invalid. Got: unknown.

I made this test basically to catch this when we switched to go mod :slightly_smiling_face: should be an easy fix though in get_workspace_status.sh

/test istio-pilot-e2e-envoyv2-v1alpha3-master

@ericvn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-pilot-cloudfoundry-v1alpha3-v2.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-e2e-pilot-cloudfoundry-v1alpha3-v2-master

prow/e2e-bookInfoTests-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test e2e-bookInfoTests-envoyv2-v1alpha3-master

prow/release-test.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test release-test-master

prow/istio-unit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-unit-tests-master

prow/codecov.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-codecov-master

prow/integ-telemetry-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-telemetry-k8s-presubmit-tests-master

prow/integ-mixer-k8s-presubmit-tests.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test integ-mixer-k8s-presubmit-tests-master

prow/istio-pilot-multicluster-e2e.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-multicluster-e2e-master

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
5c713e0b7af3bb37078459f7561c4788b60fece2
link
/test istio-pilot-e2e-envoyv2-v1alpha3-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfoTests-envoyv2-v1alpha3-master

Cancelling this PR for now as it's getting stale. Will come back to this.


Touching programming connector messes up screen

Expected Behavior
Touching the connector on the bottom edge of the swadge should do nothing to the screen or functionality of the Swadge.
Actual Behavior
If your fingers or the connector are at all damp, or you're in a humid environment, touching the connector will make the screen glitch out.
Steps To Reproduce

Breathe on the connector like you're trying to clean off a grubby phone screen
Touch the connector

alternatively...

Lick the Swadge (at least, the programming connector)

Logs, Pictures, or Video
TBD

@cnlohr to look into i2c code.
At a minimum this can be mitigated by resetting the OLED when an i2c error is reported.

This has been fixed in software as best as we can. It's still a physical problem if you touch the contacts, but the OLED is less likely to corrupt, and will recover now.


⚠ Spryr has degraded performance

In cc587c1, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3084 ms

Resolved: Spryr performance has improved in a88df53 after 23 minutes.


Error 100: File exists - /vagrant

I followed the steps here and then used ./scripts/provision_cf
... all success ...
Deployment set to `/Users/grk/workspace/bosh-lite/manifests/cf-manifest.yml'
Config
/Users/grk/.bosh_config
Director
Name       Bosh Lite Director
URL        https://<IP_ADDRESS>:25555
Version    1.2559.0 (fe0b2436)
User       admin
UUID       c5f8d0da-f8ac-4918-a1a3-0a846fb97d09
CPI        warden
dns        disabled
compiled_package_cache enabled (provider: local)
snapshots  disabled
Deployment
Manifest   /Users/grk/workspace/bosh-lite/manifests/cf-manifest.yml

deploy_release
++ find /Users/grk/workspace/cf-release/releases -regex '.*cf-[0-9]{3}.yml'
++ sort
++ tail -n 1
MOST_RECENT_CF_RELEASE=/Users/grk/workspace/cf-release/releases/cf-171.yml
bosh upload release --skip-if-exists /Users/grk/workspace/cf-release/releases/cf-171.yml

$ bosh -n deploy
Getting deployment properties from director...
Compiling deployment manifest...
Director task 4
Started preparing deployment
Started preparing deployment > Binding deployment. Done (00:00:00)
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)
Done preparing deployment (00:00:00)
Started preparing package compilation > Finding packages to compile. Failed: File exists - /vagrant (00:00:00)

I've ran into this error because I've renamed the path of my project. This caused vBox to share a folder which was not existent. Changing the share inside vBox and reloading the VM solved it.

@acca You save me!! Thanks

I'm on vagrant 1.7.4, and in my case it was likely caused by me moving bosh-lite into a subfolder after 'vagrant up' had been run. As far as I can tell, just doing 'vagrant reload' solved it.

@ulsa I move the bosh-lite dir, so 'vagrant reload' is working.


Support to Swift 3

Is there any updates to timelines with becoming Xcode 8 beta 6 compatible?

We're working on it. We'll have the version ready soon.

Supported with SugarRecord 3.0
https://github.com/carambalabs/SugarRecord/releases/tag/3.0.0.alpha.1


Pulsar 0.4.7/ Helix 14.2 error you must restart XBMC before using pulsar

Hi guys,
I am running a Win7 64Bit PC and I have been using Pulsar for a few months now without any problems.
Since a few weeks the Pulsar Daemon does not start. When I try to open it it says "you must restart XBMC before using pulsar".
When I do this I get the same message over and over again.
I have tried:

Full reinstall of Kodi (deleting all)
Using different pulsar versions (0.4.6, 0.4.7, 0.5.0)
Search google for answers. I found guys with a similar problem on Raspberry PI. they fixed it by reinstalling Openelec. But since I am running Kodi on a windows PC I do not see the relevance.
I am not a total N00b but not a programmer either.

Of course I have my two settings turned on (services > remote control...)
This issue is driving me mad. Hopefully one of you more experienced guys knows how to help me fix my issue. My thanks will be endless. :)

Have you a special caracter in your Win7 account name ? Because I add the same problem and I fixed it in changing my Win7 account name (some tuto on the net).


[SYSTEMML-1622] Remove incubator from email references

Updated email addresses to systemml.apache.org (removed incubator) in pom, md, readme files.

LGTM. Thank you @gweidner!

Thank you Deron for reviewing!  I will merge and also push gh-pages.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/1497/


Add a user-changeable global variable for default verbosity

I guess, this is the right way to do this:
function __init__()
    global DEFAULT_VERBOSITY = Ref{Int}(1)
end

plus method to set/inspect?

I don't think this needs to be done in __init__(). It should be sufficient to just write somewhere in the package
const DEFAULT_VERBOSITY = Base.RefValue{Int64}(1)
default_verbosity() = DEFAULT_VERBOSITY[]
set_default_verbosity!(level) = DEFAULT_VERBOSITY[] = level


Improving DMO to read annotations from inherited class fields.

@pefernan Looks good... just a comment about returning null in AnnotationUtils.getClassAnnotations(..) (not that it should ever happen). You protect against the potential null value in FieldInfo already.

Jenkins please retest this.

+1 to merge (when green)

Thanks @pefernan !

Jenkins please retest this.


docs: Add Hugo standard and extended for proto.

Hugo has two version/editions thus I provide a plugin for both.
Thanks! Frederik Zorn

I ran the test locally now and everything worked. Please approve again.
Thanks

Thanks!


[Web][Chrome] Page Title not updating correctly for multiple BeamLocations

Describe the bug
After Upgrading to Flutter v.2.10.1 the update of the page titles stopped working correctly.
The app seems to update the titles correctly for the default title (provided in the Material App) and the titles provided for the first BeamLocation.
On some occasions, it looks like the correct PageTitle has been applied but it is immediately replaced with the "wrong" one (The first title of the first BeamLocation).
This issue is happening while debugging and in the production build (hosted locally and on the server). It seems that only chrome is affected.
I've tested the following browsers:

Chrome v.98.0.4758.82 [Fails]
Firefox v.97.0 [Pass]
Microsoft Edge v.98.0.1108.50 [Pass]

Beamer version: (e.g. v0.14.1, master, ...)
tested with 1.2.0 & 1.3.0
To Reproduce
Steps to reproduce the behavior:

Create an app with multiple BeamLocations
Run the app
Beam to a screen that is not part of the first BeamLocation
See error

Expected behavior
The page title should update correctly on all browsers
Additional context

Flutter Doctor Output
[√] Flutter (Channel stable, 2.10.1, on Microsoft Windows [VersiÃ³n 10.0.19044.1526], locale es-ES)
    • Flutter version 2.10.1 at C:\DEVELOPMENT\SRC\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (4 days ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\Lorenzo HG\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Build Tools 2017 15.9.30)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools
    • Visual Studio Build Tools 2017 version 15.9.28307.1321
    • Windows 10 SDK version 10.0.17763.0
    X Visual Studio 2019 or later is required.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[√] Android Studio (version 4.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 64-bit edition (version 1.64.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.34.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [VersiÃ³n 10.0.19044.1526]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 98.0.4758.82
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 98.0.1108.50

[√] HTTP Host Availability
    • All required HTTP hosts are available

BeamerDelegate used by my app
  final routerDelegate = BeamerDelegate(
    guards: [
      // App Guard
      BeamGuard(
        pathPatterns: [
          AppPaths.wildCard,
          SelectorPaths.wildCard,
        ],
        // return false to redirect
        check: (context, state) => context.read<SessionCubit>().isAuthenticated,
        beamToNamed: (_, __) => AuthPaths.signin.path,
      ),
      // Auth Guard
      BeamGuard(
        pathPatterns: [
          AuthPaths.wildCard,
        ],
        // return false to redirect
        check: (context, state) =>
            !context.read<SessionCubit>().isAuthenticated,
        beamToNamed: (_, __) => SelectorPaths.selector.path,
      ),
    ],
    initialPath: AuthPaths.signin.path,
    locationBuilder: BeamerLocationBuilder(
      beamLocations: [
        AuthLocations(),
        SelectorLocations(),
        AppLocations(),
        UnknownLocations(),
      ],
    ),
    notFoundRedirectNamed: ErrorPaths.unknwon.path,
  );

Possible related Flutter issues

https://github.com/flutter/flutter/issues/53568
https://stackoverflow.com/questions/69837969/page-title-keeps-changing-between-current-and-previous-page-flutter-web

Hey @Lorenzohidalgo
We talked about that in Discord and I might have some improvements in upcoming v1.4.0 I'm looking to release today, at least for

applied but it is immediately replaced

I think I managed to eliminate that behavior with my current local changes on Beamer, but haven't pushed it yet because I'm still experimenting.

Hi @slovnicki , I've just tested it with v1.4.0 and the issue still persists. The issue seems to be linked to beamToReplacementNamed since replacing it with beamToNamed seems to "solve" the issue.

Indeed. I can confirm it also happens on Chrome with a single BeamLocation, e.g. when using the simplest example at package/example. It works fine on Firefox.
Tested with Flutter v2.10.2

Hi @slovnicki this issue still persists with flutter 3.0.5. And it exactly like describe, beamToNamed works fine, beamToReplacementNamed. What i also can see is, that the url of the browser is flickering for a very very short moment and shows like the author of this issue described the wrong page and the wrong title afterwards


Fixing tests file to use output instead of out.

Pull Request Description
What issue does this change request address?
#361
What are the significant changes in functionality due to this change request?
Fixes tests file and minor problem with test.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?

Good question.  @alfoa ?

I think they were mechanincs tests... we can add  gold file s

Would you mind changing these to either "csv" or "UnorderedCsv" checks?  Then we can get this merged in without issue, I think.

The issue isn't set to be closed by this PR.  Is that intentional?

That was a mistake, it should close the issue.  Edited the merge request to do that.


Mimic oc10 user enabled as string in provisioning api

The oc10 user provisioning API uses a string for the boolean enabled flag. 😭
fixes https://github.com/owncloud/product/issues/181

hah, I'll just not make ocsBool public ...


implements configurable suggestion threshold for compliance entities.  adds mid-tier config value for suggestion threshold value

Codecov Report

Merging #1278 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1278   +/-   ##
=======================================
  Coverage   12.44%   12.44%
=======================================
  Files          28       28
  Lines         643      643
  Branches      137      137
=======================================
  Hits           80       80
  Misses        563      563

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 5cf18e5...b3c3321. Read the comment docs.

Coverage remained the same at 27.757% when pulling b3c3321bd67df68a466433d0e37c0ae876f843c8 on theseyi:sprint-7-23 into 5cf18e53c6a551cca0e17678ad49911f9182bc0c on linkedin:master.


Update adf.dashboardProvider.html

Added ControllerAs property of the edit view.

Thanks, but the documentation is generated: 6d2e0cdc.


Add slacklib package

This is a beautiful package! With documentation and everything, very nice :)
Might use it for a project someday :D


Unknown prop keys

After updating to React 15.2.1 from React 15.1.0, I'm getting this error Unknown Prop 'keys' warning in console.
Warning: Unknown prop keys on  tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
in div
in div (created by ReactList)
in div (created by ReactList)
in ReactList (created by BuildMap)
in div (created by BuildMap)
in div (created by BuildMap)
in BuildMap (created by BuildWrapper)
in div (created by BuildWrapper)
in BuildWrapper (created by Dashboard)
in div (created by Dashboard)
in div (created by Dashboard)
in div (created by Dashboard)
in div (created by Dashboard)
in Dashboard (created by RouterContext)
in div (created by Dashboard)
in Dashboard (created by Container(Dashboard))
....

react-list doesn't use a keys prop anywhere, so this is likely an issue with either your itemRenderer or itemsRenderer function.

I'm sorry, this was my mistake. I fixed it now


Podspec

Update podspec for Swift 4.2

Was wondering if there is a specific reason as to why podspec is not updated for Swift 4.2 yet?
As a workaround I'm currently using the Swift 4.2 update by setting the specific commit in my Podfile
like so
pod 'APNGKit', :git => 'https://github.com/onevcat/APNGKit.git', :commit => 'fdc3f971e1887c7bd547bb68c49fe845e8bfa1a3'

but instead I would like to be able able to just set it normally like
pod 'APNGKit', '~> 1.0.4'

Thanks in advance 🙏

Too busy recently. I would take a look it tonight maybe.

Tag 1.1.0 was created, with podspec updated for Swift 4.2.
Sorry for the delay!


Adding a get user method to the service.

Thank you. I’ll publish a new package on Monday.

Cool Thanks! I'm sure there's a bunch more to do.

this.user is never set correctly to this.app.getUser() and thus getUser method of service is always {}


Support scmResourceState in when clauses

Adds contextValue?: string to the SourceControlResourceState
Allows when clause in scm/resourceState/context menus to use scmResourceState

Example - I have hidden the "revert" item from the inline and context menu using a context clause like scmResourceState == opened

(I realise that the policy says that PRs are not accepted for backlog candidates, but the set of people who would actually benefit from this feature is very much larger than the set of people who would look for the issue on github and/or understand it well enough to upvote it!)
This PR fixes #86180

It's actually a perf issue if we create menus for each element. So... could we share them between elements if they have the same context key?

I'll have a look at that - my initial implementation was caching the resource state by resource using a map in ISCMResourceGroup and disposing them with the group (but I realised this was pointless as the menu was ultimately only generated once per resource anyway).
I could make that a map based on contextValue instead so there is one menu per context per group

@joaomoreno - updated with one resource per context

@joaomoreno now the endgame is done, could we look at merging this if the approach is ok?
(I wasn't 100% sure if the the proposed API was the right place for this)

@joaomoreno any chance of getting this moved on please?

@joaomoreno I'd like to add my voice to the request to get this merged. Or is there a reason it can't go in?

@mjcrouch I haven't looked at this too deeply (so take this with a grain of salt) -- but is there a need for the createResourceMenu/ISCMResourceMenu work? Since the menus are currently already loaded per-group for an individual resource, I would think that just by adding the new contextKeyService.createKey('scmResourceState', resource.contextValue) calls would be enough.
Is that not the case?

@eamodio thanks for reviewing - it's been quite a while since I wrote the code so I'm stretching my memory, but iirc there is currently just one menu for each group, and getResourceMenu returned the group menu
So in order to render different context items for different resource objects, we need to create a menu per contextValue in the group and then return the correct menu according to the contextValue on the object we've clicked.

@mjcrouch You might be right, but I would recommend giving it a shot to see if it works properly without it.

@eamodio I gave it a try (I think this may have been what I tried originally) - it does seem to work for the right click context menu, but does not work for the inline icons; they all end up with the same set of icons even if they have different contextValues.

Hrm, I think it has to do with the connectPrimaryMenuToInlineActionBar calls in scmViewPane.ts -- @joaomoreno will no better as to why that is special.

Assigning for August so I get a good look at this next week. 👍

just happened to notice https://github.com/microsoft/vscode/pull/104089 - suspect there may be a conflict when that gets merged

Yeah, for sure. No worries, I'll handle the conflicts. 👍

@mjcrouch That was great work 👏 I merged into the latest master and resolved all conflicts. There was a lot of refactorings on menus.ts for perf reasons.

thank you - this will really help to make my menus more usable :)