fix(KFLUXBUGS-1416): FBC fragment released to the wrong OCP version

This commit adds the placeholder {{ OCP_VERSION }} to the indexes used by the FBC Release pipeline e2e test.
Required by https://github.com/konflux-ci/release-service-catalog/pull/502
Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/approve
/lgtm

/retest

/retest

/hold

@jinqi7 can you unhold this one? If this is not merged I can't merge the https://github.com/konflux-ci/release-service-catalog/pull/502

/retest

/retest

@jinqi7 can you unhold this one? If this is not merged I can't merge the konflux-ci/release-service-catalog#502

ignore my previous comment. Found another issue.

@theflockers , you can '/unhold' also. I think your PR need to be merged first.

/retest

/retest

I think you need to change the default value to "development" in line since your PR has not promoted to "staging" branch.

/retest

/test

I think you need to change the default value to "development" in line since your PR has not promoted to "staging" branch.

Is that new? I did not touch this line.

/unhold

/retest


Custom Topojson display different between converted Geojson and PowerBI

I am trying to convert the topojson and combine floor plans into one topojson to use in PowerBI. But the coverted geojson displayed with extra geometry. Any idea why and how to fix it?

Closing as this seems like an issue with your input data.  Feel free to re-open and include a snippet of data.


Smaller italian optimizations

Description
I have added some smaller optimizations on italian language.
Checklist

[X] I have read the Contribution Guidelines
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new warnings
[X] I have read the section Add New Translation Tags (for new translation tags only)

I'll let @albanobattistella review this and decide :)

I'll let @albanobattistella review this and decide :)

thanks, work in progress...

I'll let @albanobattistella review this and decide :)

Hi,
you can merge  the last one.
Thanks.


Kafka : remove noise from logging EOF messages in Kafka parser

We keep seeing a lot of these on normal client (produce/consume) connection close.
We should not be logging valid EOF as errors.
level=error msg="Unable to parse Kafka request; closing Kafka request connection" error=EOF id="rx:<IP_ADDRESS>:57590-><IP_ADDRESS>:10551<->tx:closed"

Fixes: #3792
Signed-Off-By: Manali Bhutiyani<EMAIL_ADDRESS>Kafka : remove noise from logging EOF messages in Kafka parser

test-me-please

test-me-please

test-me-please

backport https://github.com/cilium/cilium/pull/3811


add starter code for rework project

This PR adds all of the HTML we need for the rework study guide application


Fix Gitlab References on templates

Address several templated reference to gitlab:

Already done for 1.9.x templates.


Support for Alpine Linux Arm

Currently libraries are shipped for musl-x64 and linux-arm, but not musl-arm (or arm64).
Would be nice to have them to support alpine deployments on RPI devices. Thanks!
Related #192 #214

I've started on this and should have some PRs next week 🙏

Two PRs sent 💪

I think these changes are available in prerelease 2.1.0-pre20220427180151, now on nuget.

Thanks!
We've moved off musl now so I'm not in a position to test.


Existing champion cannot sign charter

Giustina is appearing in the list of users in manage dojos having not signed the charter.
When she logs in she can't find anywhere to sign it.

fixed. will be deployed later on today


plt.plot hangs

In the following example given in README, my lisp hangs for more than 1 minute when I call (pycall "plt.plot" [elided]). I could not locate the cause. But I can tell that #'import-module works well, since if I skip pycall and just do (pycall "plt.show"), it works as expected. On the other hand, I have also tried to plt.plot in a python repl; it works fine as well.
PY4CL2-CFFI> (import-module "matplotlib.pyplot" :as "plt")
T
PY4CL2-CFFI> (pycall "plt.plot"
                     (iota 10)
                     (mapcar (lambda (x) (* x x))
                             (iota 10)))
#(#<PYTHON-OBJECT :type <class 'matplotlib.lines.Line2D'>
  Line2D(_line0)
 {1006670F83}>)
PY4CL2-CFFI> (pycall "plt.show")
#<PYTHON-OBJECT :type <class 'NoneType'>
  None
 {1006672273}>

Can you confirm that running it straight from the REPL works fine, but running it from an emacs buffer causes lisp to hang? Can you check the output in *inferior-lisp* buffer?
I can confirm this issue and the cause seems to be simply that matplotlib does not play nice with multithreaded environments. In the future, I might provide an option to have a single-threaded python calling, so all calls to python (except perhaps the finalizers) will be made by the same thread that initiated it. This would avoid the issue.
For the time being, you can set (setf swank:*communication-style* nil) in ~/.swank.lisp and see if the issue is resolved.

Thanks for the input. So after setting communication-style on the fly in the lisp repl, and call ply.plot (again in the lisp repl) hangs the lisp too. Here's the message in *inferior-lisp*
2024-02-20 06:52:25.299 sbcl[34754:6081902] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow drag regions should only be invalidated on the Main Thread!'
*** First throw call stack:
(
)
libc++abi: terminating with uncaught exception of type NSException
fatal error encountered in SBCL pid 34754 pthread 0x16f95f000:
maximum interrupt nesting depth (8) exceeded

Error opening /dev/tty: Device not configured
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>

So after setting communication-style on the fly in the lisp repl
...
NSWindow drag regions should only be invalidated on the Main Thread!

I'm not sure if the variable takes effect if set on the fly. Can you try setting it from ~/.swank.lisp?

I guess calling python from a single thread has its drawback too, right? That's why you want to make it an option, but not default. If that's the case, how would the user know ahead of hanging that if they should switch to single-thread mode?

I might end up making it the default; I will need to check how jupyter notebooks or other python environments behave though.

Recent commits up to d3df012789b1ab46dccb3b21ed59f0633e21b860 (and any more recent) should have added preliminary support for single-threaded mode. This is essentially an alternate system/package "py4cl2-cffi/single-threaded".
This shadows a number of exported symbols from "py4cl2-cffi" and provides their single-threaded counterparts. The intended usage is that one calls (py4cl2-cffi/single-threaded:pystart) instead of (py4cl2-cffi:pystart). Following that, function and macro calls for symbols in the package py4cl2-cffi/single-threaded would communicate to python using a single thread.
Either of the two below should work now:
(defpackage :my-package
  (:use :cl)
  (:local-nicknames (:py :py4cl2-cffi/single-threaded)))

(in-package :my-package)

;; Option 1: Use directly
(py:import-module "matplotlib.pyplot" :as "plt")
(py:pycall "plt.plot" '(1 2 3) '(1 2 3))
(py:pycall "plt.show")

;; Option 2: Use through a lisp function and package
(py:defpymodule "matplotlib.pyplot" nil :lisp-package "PLT")
(plt:plot '(2 3 4) '(32 43 23))
(plt:show)

I'll add more tests in the future.
Barring any bugs, it should be backward compatible with any exisiting use of py4cl2-cffi, so long as the first call to (pystart) happens through (py4cl2-cffi/single-threaded:pystart) instead of (py4cl2-cffi:pystart).
I'm not making this default, because this has a slight performance penalty. In addition, multithreaded usage cannot be done away completely. Lisp garbage collection relies on finalizers which, at least on SBCL, can be called through any thread.

If that's the case, how would the user know ahead of hanging that if they should switch to single-thread mode?

Currently, the only option to know this is to know beforehand how one's python packages behave in multithreaded environments.

I will need to check how jupyter notebooks or other python environments behave though.

This still remains.


Missing packages + invalid property name

Describe the bug
Hi! First and foremost, a huge thank you for sharing your code. It has been incredibly helpful to me. I just wanted to report an issue that arises when following your tutorial step-by-step; there are missing packages.

Of course, the issue can be easily resolved with pnpm add element-plus and pnpm add vxe-table, but I'm uncertain if these libraries should be added as project dependencies in the repository.
If they aren't necessary for some reason, please feel free to close this issue. And once again, thank you!

property name in events is incorrect isReadonly should be isReadOnly - here  https://github.com/Lionad-Morotar/toast-ui-calendar-vue3/blob/dev/play/src/mock-data.js#L16C5-L16C15 and here https://github.com/Lionad-Morotar/toast-ui-calendar-vue3/blob/dev/play/src/mock-data.js#L25

Steps to reproduce
In totally new env after git clone:

pnpm install
pnpm serve

Environment Info
MacOs

Used Package Manager
pnpm
Validations

[X] Read the Readme.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

Aha, thanks a lot~ I'll fix that !


Web-Specific Fixes for onValueChange and Deprecated React Methods

Web-Specific Fixes for onValueChange and Deprecated React Methods
Changes:

Web-Specific onValueChange: Adjusted onValueChange in RNCSliderNativeComponent.web.tsx to trigger only during user interactions, addressing platform-specific inconsistencies (issue #562).
Deprecated React Methods: Updated Slider.tsx and RNCSliderNativeComponent.web.tsx, replacing deprecated StyleSheet.compose with array syntax.

These updates fixes an inconsistency in the web platform and improves compatibility with newer React versions.
Related Issue: #562

Sorry for the recent series of updates. Initially, I patched this package for personal use and subsequently decided to submit a PR. While the original sources were Ok, there were some minor issues with linting and test snapshots. I have now addressed these issues.

@landabaso No need to apologize :) These are just two commits, especially both with awesome commit messages and good input 👍
I will take a look at this PR sometime this week, is that OK with you?

Thanks. No problem on the timing. I'm currently using a patched version and testing it across iOS, Android, and Web. I'll keep you updated if anything comes up, but it seems solid right now.


Fix remarkjs-pdf timeout

I was annoyed to have the CI red because of the remarkjs-pdf timeout so I commented it out in https://github.com/INRIA/scikit-learn-mooc/commit/b92c7cf7b1a40fbd16518bd5f30c70b379207532.
If you have time to look at it @brospars maybe by patching remarkjs-pdf to have a bigger timeout (as you did in your PR to remarkjs-pdf) or using decktape to generate the PDF (as mentioned in the remark.js doc here), that would be much appreciated.
Originally posted by @lesteve in https://github.com/INRIA/scikit-learn-mooc/issues/14#issuecomment-646691960

The issue is deeper than that. Even without timeout overfit.html won't load on chrome (tested locally on chromium). It's due to htmlark inlining all images.

If we move all figures to /figures and remove htmlark it could work.

I am afraid I am not following (probably because this web stuff is not my area of expertise ...), maybe you open a PR and get feed-back from @GaelVaroquaux who did this part originally?

Probably this can be closed since #23 was merged.


VS2019 warn about switch->fall-through but doesn't recognize the attribute

The article describes that VS2017 doesn't warn about fall-throughs in switch statements and therefor the attribute [[fallthrough]] has no effect.
Wath's not mentioned is that VS2019 does warn about those possible mistakes, but the attribute still doesn't have any effect, so it's useless to annotate intended fall-throughs.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c2eb231e-d120-ad82-539c-f30baa904815
Version Independent ID: ea724ca8-bc1c-f154-c122-0217f6280590
Content: Attributes in C++
Content Source: docs/cpp/attributes.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@A-x-S
I'm sorry it's giving you trouble. Unfortunately, I can't reproduce the effect you describe. The VS 2019 compiler doesn't have a warning about implicit fallthrough. There are only warnings about improper use of the [[fallthrough]] attribute: either C5051 (must use /std:c++17 or later) or C4468 (attribute must be followed by a case or default label). These worked as described in the docs in my testing.
The code analysis engine does have such a warning: C26819. It detects and warns on unannotated fallthrough if /std:c++17 or later is applied. As far as I can tell, it works as intended. If you have a case where it doesn't work, then you can report a problem on Developer Community, since that would be considered a product issue.
Test rig, adapted from cppreference:
C:\Users\corob\Documents\Projects\curiosity\fallthrough>type fallthrough.cpp
void f(int n) {
    void a(), b(), c();
    switch (n) {
    case 1:
    case 2:
        a();
        [[fallthrough]];
    case 3: // no warning on fallthrough
        b();
    case 4: // compiler may warn on fallthrough
        if(n < 3) {
            c();
            [[fallthrough]]; // not followed by label
        }
        else {
            return;
        }
    default:
        [[fallthrough]]; // ill-formed, no subsequent case or default label
  }
}

C:\Users\corob\Documents\Projects\curiosity\fallthrough>cl /EHsc /c /nologo /Wall /permissive- /analyze /analyze:plugin EspxEngine.dll /std:c++17 fallthrough.cpp
fallthrough.cpp
fallthrough.cpp(13): warning C4468: 'fallthrough': attribute must be followed by a case label or a default label
fallthrough.cpp(19): warning C4468: 'fallthrough': attribute must be followed by a case label or a default label
C:\Users\corob\Documents\Projects\curiosity\fallthrough\fallthrough.cpp(10) : warning C26819: Unannotated fallthrough between switch labels (es.78).

I'm closing this as not repro, but I'll reopen it if you have an example where the behavior doesn't match the documentation.


10.0.19041.3570 - listening OK, running OK, installed OK, supported OK - no multi user access

I have an issue where rdpwrap reports everything is running fine, but when a remote user logs in, it logs out the current user
Any ideas how to prevent this? I'm wondering if KB5031356 is causing the issue?
Sadly I don't know how to remove KB5031356 as I don't get an uninstall option like I do for other updates

I have the same problem

As a temporary fix, try uninstalling Windows Security Update KB5031356 and reboot. You should now be able to get multi-user access

10.0.19041.3570

One termsrv.dll version = ONE opened issue for one architecture. This issue will closed as duplicate (I'm have permissions to do this ;))

listening OK

This is correct, otherwise you would not be able to connect via RDP.

installed OK, supported OK

Offsets is exists in local rdpwrap.ini and RDP Wrapper is installed

KB5031356 as I don't get an uninstall option

Uninstalling updates is off-topic here.

no multi user access

Try:

Download RDP Wrapper 1.6.2 and extract this to any directory.
Place rdpwrap.ini in the same directory.
Open CMD as administrator
Execute this commands

cd C:\path\to\directory\
rdpwinst -u -k
rdpwinst -i

Enjoy!

Original message: https://t.me/rdpwrap/49131

Duplicate of https://github.com/stascorp/rdpwrap/issues/2359


Redirection should not happen for post requests

I have an application that is maintained by a different company that does a post request to a tool of ours.
If we redirect them we lose the post body

I just saw that I might be able to use: feat: added redirect ignore glob support

We have resolved this as of v3.0.0 released to npm :tada:
There are two new options added redirectIgnoresNonGetMethods (Boolean, defaults to true) and stringify (Object for qs.stringify, and has sensible industry standard defaults of { addQueryPrefix: true, format: 'RFC1738', arrayFormat: 'indices' }).  As of v3.0.0 all non-GET requests will NOT be redirected to locale specific path.  If you wish to turn this behavior off, pass new I18n({ redirectIgnoresNonGetMethods: false }).
npm install @ladjs/i18n@latest

or with yarn:
yarn add @ladjs/i18n@latest

Note that we have also version bumped deps in @ladjs/web and @ladjs/api as well, you can install the latest with @ladjs/web@latest and @ladjs/api@latest.
Let me know if you find any further issues, thanks so much!


Revised with accurate Float configuration details

Updated to advise users how they can configure Float SSO without requiring Float Support using the Float Team Settings.

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

@jeevansd Changes look good to me, could you please sign-off

#sign-off


Execution of Katana Benchmarking

Related Main Issue: Benchmarking Dojo's Storage Efficiency in Terms of Gas Usage
Objective
The purpose of this sub-issue is to establish a comprehensive guide for benchmarking using Katana, the high-speed local Starknet node tailored for local development alongside Dojo.
Background
Katana, as described in the official documentation, is built to bolster local development with Dojo. Its speed and integration capability make it a prime tool for assessing the efficiency of storage operations, especially in a localized development environment.
Tasks

Exploration of Katana's Benchmarking Features:

Investigate and document the functionalities and parameters of Katana conducive for benchmarking.
Develop a step-by-step guide showcasing how to effectively run benchmarks using Katana.

Collecting and Storing Benchmark Results:

Devise a methodology to extract benchmark results from Katana.
Introduce a structured format for capturing and storing these results for analysis.

Interpretation and Reporting:

Identify primary metrics to assess from the benchmark results.
Propose a coherent and comprehensive reporting template to showcase the findings.

Expected Outcome
By the conclusion of this sub-issue, we envision having an established protocol for performing benchmarks using Katana. This will not only help in understanding storage efficiency but also contribute to the broader goal set in the main issue.

Initial research

Tests can be easily deployed into locally or remotely running Katana instance
Then the starknet_estimateFee method from the API can be used to fetch it in straightforward manner.

Differences from initial research:

estimateFee is rarely used, needs singature and would need some implementation
execute is simple to do with cli or sozo as a dependency
starknet_getTransactionReceipt run after execute is trivial to implement and containts information about gas

{
    "jsonrpc": "2.0",
    "method": "starknet_getTransactionReceipt",
    "params": ["0x61c0f0bb7b4d514d44dea673824acf270c00f750c5525a50403a0d94d6f3afa"],
    "id": 1
}


Incorrect type generation with optional route parameters

In<EMAIL_ADDRESS>I have a route aaa.$aId.(,bbb.$bId).(,ccc.$cId)+page.marko in order to support the URL structure:
/aaa/$aid/ccc/$cid
/aaa/$aid/bbb/$bid/ccc/$cid
/aaa/$aid/bbb/$bid
/aaa/$aid

This results in 4 permutations generated in .marko-run/routes.d.ts below, which confuses the typechecking of $global.params. Deleting the 3 shorter permutations calms Typescript down.
declare module "../src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko" {
  namespace MarkoRun {
    export { NotHandled, NotMatched, GetPaths, PostPaths, GetablePath, GetableHref, PostablePath, PostableHref, Platform };
    export type Route = Run.Routes["/aaa/:aid"];
    export type Context = Run.MultiRouteContext<Route> & Marko.Global;
    export type Handler = Run.HandlerLike<Route>;
    export const route: Run.HandlerTypeFn<Route>;
  }
}

declare module "../src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko" {
  namespace MarkoRun {
    export { NotHandled, NotMatched, GetPaths, PostPaths, GetablePath, GetableHref, PostablePath, PostableHref, Platform };
    export type Route = Run.Routes["/aaa/:aid/bbb/:bid"];
    export type Context = Run.MultiRouteContext<Route> & Marko.Global;
    export type Handler = Run.HandlerLike<Route>;
    export const route: Run.HandlerTypeFn<Route>;
  }
}

declare module "../src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko" {
  namespace MarkoRun {
    export { NotHandled, NotMatched, GetPaths, PostPaths, GetablePath, GetableHref, PostablePath, PostableHref, Platform };
    export type Route = Run.Routes["/aaa/:aid/bbb/:bid/ccc/:cid"];
    export type Context = Run.MultiRouteContext<Route> & Marko.Global;
    export type Handler = Run.HandlerLike<Route>;
    export const route: Run.HandlerTypeFn<Route>;
  }
}

declare module "../src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko" {
  namespace MarkoRun {
    export { NotHandled, NotMatched, GetPaths, PostPaths, GetablePath, GetableHref, PostablePath, PostableHref, Platform };
    export type Route = Run.Routes["/aaa/:aid/ccc/:cid"];
    export type Context = Run.MultiRouteContext<Route> & Marko.Global;
    export type Handler = Run.HandlerLike<Route>;
    export const route: Run.HandlerTypeFn<Route>;
  }
}

Thanks for the report, this should be fixed in 0.2.2.
The types for a page or handler that supports multiple routes will now be the union of all the routes they support, similar to how middleware and layouts worked.

Hmm, 0.2.2 looks like it should work. Yet mtc complains differently now:
src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko:2:18 - error TS2339

  1 | $ const {
> 2 |   params: { aid, bid, cid },
    |                  ^^^ Property 'bid' does not exist on type '{ aid: string; } | { aid: string; bid: string; } | { aid: string; bid: string; cid: string; } | { aid: string; cid: string; }'.
  3 | } = $global;
  4 |
  5 | $ console.log({ aid, bid, cid })

src/routes/aaa.$aid.(,bbb.$bid).(,ccc.$cid)+page.marko:2:23 - error TS2339

  1 | $ const {
> 2 |   params: { aid, bid, cid },
    |                       ^^^ Property 'cid' does not exist on type '{ aid: string; } | { aid: string; bid: string; } | { aid: string; bid: string; cid: string; } | { aid: string; cid: string; }'.
  3 | } = $global;
  4 |
  5 | $ console.log({ aid, bid, cid })

@rturnq Should I raise a separate issue with mtc there? Or do you think the remaining issue is in this repo?

This is expected (though not ideal) because the type of MarkoRun.Context for this page will be a union of all the routes it handles. Without discriminating the union TypeScript then only knows the parameters which are available to all union members. You can discriminate using the route property and the params will be narrowed
$ {
  if ($global.route === '/aaa/:aId') {
    $global.params.aId //string
    $global.params.bId //undefined
    $global.params.cId //undefined
  } else if ($global.route === '/aaa/:aId/bbb/:bId') {
    $global.params.aId //string
    $global.params.bId //string
    $global.params.cId //undefined
  }
}

This was originally designed to support layouts and middleware where this type of discrimination would make more sense but I see how it is quite inconvenient here.
I think we can do better by typing the params as a superset where in each union member the missing params would be typed as undefined. This should allow everything to narrow as it currently does and also give access to the non-narrowed types as string | undefined.
I'll re-open this issue and try to get a fix out soon.
P.S. Meta data will have the same problem but I'm not sure what can be done for that at the moment. We are thinking about forcing meta data to be objects and allowing them to be defined anywhere and merged together. If we did that I think this same change could work for meta as well.

Thanks for looking into this. I look forward to the fix.
I learnt something new... I don't usually do unions of interfaces, only basic types

Without discriminating the union TypeScript then only knows the parameters which are available to all union members


html documents served are downloaded

http-server example on this page
https://stackabuse.com/how-to-start-a-node-server-examples-with-the-most-popular-frameworks/
Tell us about your environment

exact http-server version: 0.12.1
Node version: 12.16.2
Platform: Win10

Other information (related issues, suggestions for a fix, etc):
Just learning about the server but when it goes to serve the example page it downloads it instead of displaying it. Does this in both Chrome and Firefox (latest versions). Any chance you could explain what I am doing wrong if this is my issue? Thanks.

I can at least confirm the Firefox behavior, it's working on chrome (latest)

What does the file you're trying to serve look like? Does it have the file extension .html? Do other servers serve it properly?

Thanks for your reply. This is happening on both Chrome and Firefox.
This is the code of index.html. It was originally a visual studio code template, but I added to it to see if that helped.
            Hello from http-server
Hello from http-server

index.docx

Is the file actually called index.docx? If so, that makes it a Microsoft Word document, which should be downloaded. There isn't really any way for a regular web server to serve a file like that.

No, I just put it into a docx file so you can see it - I couldn't upload
the html file.
Thanks
On Mon, Apr 27, 2020 at 11:02 PM Jade Michael Thornton <
<EMAIL_ADDRESS>wrote:

Is the file actually called index.docx? If so, that makes it a Microsoft
Word document, which should be downloaded. There isn't really any way for a
regular web server to serve a file like that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/http-party/http-server/issues/623#issuecomment-620042672,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTBA4ZWTGRCPCU7MGUBC4DROWNBLANCNFSM4ML2UI5A
.

This is probably a problem with the http response header. Maybe Chrome fixes it, but firefox doesn`t

Seems like a duplicate of https://github.com/http-party/http-server/issues/657 . A complete list of response headers might help debugging this.


Added one link for medium article

Hello @meetzaveri!
Unfortunately, the part of docs you attempt to update in this PR is no longer present in the docs.
Let me close this PR as outdated. Please feel invited to create new PRs for other open issues, thank you!


Accuracy issue when playing a WaveSurfer region

Accuracy issue when playing a WaveSurfer region
Hi,
I'm having accuracy issues when attempting to play the wave during a specific duration
I'm editing a webapp designed to edit subtitles for videos. I'm using React/Redux with Wavesurfer and regions to display audio regions on a canvas on which the waveform is drawn. The wave is rendered via a React Component whose props exclusively come from Redux state and actions.
I'm trying to implement a feature allowing the user to play the wave on a region's duration, i.e. from a region.start time to a region.end time.
To do so, I am basically setting the wave's current time to the starting time, then playing the wave while setting a timeout duration equal to the region's duration, before pausing the wave.
The problem is, it seems the wave does not pause systematically at the exact time I want. Assuming I want to play the part corresponding to the moment a video's protagonist says Hello World from the sentence Hello World what's up, I'm going to hear Hello Worl... of Hello World wh... from time to time when playing this part repeatedly.
All of this is summarized in the JS function below :
import hrtime from 'browser-process-hrtime';
import NanoTimer from 'nanotimer';
import {
  setTime,
  play,
  pause,
  updateTranscript,
} from '../actions';

// [...]

function playRange(start, duration, activeCueId, resetTime) {
  return (dispatch, getState) => {
    // [...]
    // Here I am setting the start time into Redux Store,
    // which in turns sets the current time of the wave
    // this wave being rendered by a React Component taking
    // the redux store `start` attribute as a prop
    dispatch(setTime(start));

    window.playRangeTimer = new NanoTimer();

    // Here I'm setting the wave's playing attribute to true via the redux store
    dispatch(play());

    // Last but not least,
    // I'm setting a timeout with a duration equal to the region's duration
    // before pausing the wave via an action dispatch to the Redux Store - again
    const countDown = (duration * 1000).toFixed(2) + 'm';
    window.playRangeTimer.setTimeout(
      () => {
        dispatch(pause());
        dispatch(setActiveCue(cue));
        dispatch(setTime(Number(parseFloat(start + duration).toFixed(2))));
        dispatch(setTime(resetTime));
      },
      '',
      countDown,
    );

    return window.playRangeTimer;
  };
}

Resources

Frontend: React.js / Redux
Wavesurfer.js version(s): Wavesurfer 2.0.5 and react-wavesurfer 0.8.6.
Browser: Chrome Version 68.0.3440.106 (64 bits)

Notes

I've been trying to reduce the level of inaccuracy on multiple levels :

I've made sure the computation of the start and end time return accurate values when adding float numbers to one another, by rounding the result to the 2nd decimal
I've replaced the classic setTimeout, which seems to present accuracy issues,  with a supposedly more accurate timer

Is dispatching a Redux action a possible cause of delay in the code execution?
Would the browser's performance be an issue as well?
Would the video's FPS impact the accuracy as well ? And by extension, would the browser be an issue on that matter?
Possibly related to https://github.com/katspaugh/wavesurfer.js/issues/379 ?

Wavesurfer.js version(s): Wavesurfer 2.0.5

why not use latest (2.0.6) or try master.

thanks @thijstriemstra we will give a try with 2.0.6

We tried to update wavesurfer with the 2.0.6 versin but didn't solve our problem. We don't know what to try next :-/ Any advice ?

I've replaced the classic setTimeout, which seems to present accuracy issues, with a supposedly more accurate timer

@virtualflo, what about #1007?
or #1281?

@thijstriemstra thank you for your help.
We didn't have the time to solve this problem for the last weeks but we should make some test this week.
For information we are using the Region plugin.

some accuracy adjustments to regions plugin will be included in v3.1.0

@thijstriemstra great news! Thanks for the update. When do you plan to deploy the v3.1.0?

@virtualflo see #1751

Hello, I am having a similar issue. Has anything been found on this?

I am guessing this might be related to the following lines on wavesurfer.js/src/plugin/regions/region.js
I am not sure why time is being rounded to tens of a second. This is causing issues when working with audio at 1s or 2s length.


Report exception to sentry

It would be useful to have dashboard exception reported to sentry.
We should investigate if react has something useful for that.

https://docs.sentry.io/platforms/javascript/guides/react/
seems like there is react integration in sentry


Microsoft BizSpark

Microsoft BizSpark
Microsoft Bizspark or Bizspark One
Describe the product
Microsoft program that provides support, Azure credits and free licenses to selected Microsoft products to software entrepreneurs and start ups including Office 265, MSDN(Microsoft Developper Network) Subscription for teams etc. providing the benefits and the perks to the selected members of this program for a term of 3 years.
Initial release date of the product
November of 2009
Discontinuation date of the product
Feb 2018
Relevant links

Original urls:- https://www.microsoft.com/bizspark/ https://bizspark.microsoft.com/
Internet Archive:- https://web.archive.org/web/20090228042650/https://www.microsoft.com/bizspark/
Before closing:- https://web.archive.org/web/20170930070352/https://bizspark.microsoft.com/

Additional context
After discountinung the program, They launched Microsoft for Startups. (https://www.microsoft.com/startups)

So... researching BizSpark, it appears it was just rebranded as Microsoft for Startups? Is there a particular nostalgia for BizSpark brand or a distinct offering that was killed along with the BizSpark brand for this program?

As far as I understand, BizSpark was more of a discounted subscription offering than an actual product. It just gave you access to other actual products.
If that understanding is correct, I wouldn't personally add this to the list, as starting to list these types of offerings will quickly dilute the graveyard with temporal subscription offerings, rather than actual products that offered functionality, that was then lost by Microsoft discontinuing/killing it.
There are still plenty of ways to obtain other subscription to the same products that BizSpark provided.
My personal take. I guess BizSpark could be an exemption, because it has been offered for a long time and many businesses made use of this program.

If that understanding is correct, I wouldn't personally add this to the list, as starting to list these types of offerings will quickly dilute the graveyard with temporal subscription offerings, rather than actual products that offered functionality, that was then lost by Microsoft discontinuing/killing it.

Makes sense

I appreciate you all resolving this and agree. Adding BizSpark seems like it would open the door to other discount programs Microsoft offers in nonprofit, education, and healthcare industries for example rather than actual products. The Graveyard should primarily focus on the actual enterprise, developer, and/or consumer products of Microsoft rather than programs offering those programs.  A software equivalent would be Windows Essentials (a bundle of products) versus Windows Movie Maker and Windows Live Writer.
Some exceptions may occur, but it seems we agree this is not a particular example.  Love the contribution to discussions though!


rtorrent: New package 0.9.6

Added new package, inspired from https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/rtorrent.

I don't want to see it in msys-packages


Using variables

I'm using mdsvex and my markdown pages have variables:
---
layout: componentLayout
title: My Title
breadcrumb_title: My-breadcrumb
dir: Components
description: 'My description'
---

I can use them for some cases:
<MetaTags
  title={breadcrumb_title}
  titleTemplate="%s | Flowbite-Svelte"
  description={description}
...

But not in {{}}:
openGraph={{
    ...
    title: {title}, // this won't work
    description: {title},// this won't work
    images: [
      {
        ...
        alt: {title} // this won't work
      }
    ],
    site_name: 'Flowbite-Svelte'
  }}
  twitter={{
    ...
    title: {title},// this won't work
    description: {description},// this won't work
  ...
  }}

How can I use variables in {{}}?

Ok, I just needed to use a back tick:
openGraph={{
    title: `${title}`,
    description: `${title}`,
    images: [
      {
        url: `https://example.com?title=${breadcrumb_title}`,
        width: 800,
        height: 600,
        alt: `${title}`
      }
    ],
   ...
  }}


BUG: compatibility issue with TFP 0.7.0

InferPy does not work with TFP 0.7.0 because the rv_all list has been removed. For example, when importing InferPy:
import inferpy as in

I get
  File "[...]/InferPy/inferpy/models/random_variable.py", line 32, in <module>
    distributions_all = generated_random_variables.rv_all
AttributeError: module 'tensorflow_probability.python.edward2.generated_random_variables' has no attribute 'rv_all'

The packages installed are:
tensorflow==1.14.0
tensorflow-estimator==1.14.0
tensorflow-probability==0.7.0

Closed in 26c03b71729d92103f7f77a6dc7c6c3bb67a43f3


The interface of the Search in options is broken.

Problem Description
The interface of the Search in options for command + shift + f is broken. Please see the photo below.

Version

Spyder version: 5.4.3

Hey @ryohei22, thanks for reporting. I think this is a Mac only problem because I'm not observing it on Linux or Windows.
@mrclary, could you confirm that?

I don't see it on macOS either. I use this feature frequently with many versions (dev, release, etc.) and have not encountered it. But I explicitly tested it on Spyder 5.4.4 (standalone)

@ryohei22, may I ask how you have Spyder installed and whether your architecture is Intel or M1? In any case I recommend updating to our standalone application version 5.4.4: https://github.com/spyder-ide/spyder/releases/download/v5.4.4/Spyder.dmg

This could be a Qt/PyQt issue. @ryohei22, please update to PyQt 5.15 and try again.

Thank you for your replies!
At first, I answer the questions.

how you have Spyder installed and whether your architecture is Intel or M1?

I installed Spyder through conda. I list some information about my environment below.
(Note: I checked the Spyder, Qt, and PyQt versions from About Spyder in the app.)
Environmental Info

Spyder version: 5.4.3  (conda)
OS: macOS Ventura 13.4.1
Chip: Apple M1

After that, I tried updating Spyder to 5.4.4 with conda. However, still I have the problem.
Environmental Info

Spyder version: 5.4.4  (conda)
Qt version: 5.15.2
PyQt5 version: 5.15.7

The next step would be to try the standalone installer as @mrclary mentioned but we're curious about what makes this happen, right.

@ryohei22, thanks for checking the update. We could check a few more things.

Can you check if you have Rosetta installed?$ pgrep -lf oahd

If this returns anything, then you have Rosetta installed, otherwise you don't. I don't think you need Rosetta installed, but I'm just curious whether it may be playing a role.
Can you check your current environment for arm64 and mixed channel packages?$ conda list -c

You should see a long list of packages installed indicating channel and architecture, for exampleconda-forge/osx-arm64::qt-main-5.15.8-hcac2fde_14
conda-forge/osx-arm64::qt-webengine-5.15.8-hc1a9d58_1

Some packages may indicate noarch and that's okay, but if the channels show main and conda-forge, this may be causing an issue.
Can you try to install Spyder in a completely new environment?$ conda create -n spy -c conda-forge --override-channels python=3.10 spyder=5.4.4
$ conda activate spy
$ spyder

I've tested the above on my M1 mac and did not see the reported issue. I have Rosetta installed, so it could either be that you have Spyder installed in a mixed source environment (conda-forge + main + ...) which might be breaking Spyder for you, or Rosetta is making Spyder work properly for me.

Spyder version: 5.4.4  (conda)
Python version: 3.10.12 64-bit
Qt version: 5.15.6
PyQt5 version: 5.15.7
Operating System: macOS-13.2.1-arm64-arm-64bit

@mrclary, thank you for your advice.

Can you check if you have Rosetta installed?

Apparently, I have Rosetta installed.
(base) ryohei@MacBook-Pro-3 ~ % pgrep -lf oahd
369 /usr/libexec/rosetta/oahd

Can you check your current environment for arm64 and mixed channel packages?

I saw some packages from channel conda-forge but not main,  and several packages are from pypi. Most of the packages show defaults and I guess this means main. I listed all of the packages with conda-forge below.
(base) ryohei@MacBook-Pro-3 ~ % conda list -c
conda-forge/osx-64::ca-certificates-2023.5.7-h8857fd0_0
conda-forge/noarch::certifi-2023.5.7-pyhd8ed1ab_0
conda-forge/osx-64::conda-23.5.2-py38h50d1736_0
conda-forge/osx-64::debugpy-1.6.7-py38h4cd09af_0
conda-forge/noarch::google-api-python-client-2.94.0-pyhd8ed1ab_0
conda-forge/noarch::google-auth-httplib2-0.1.0-pyhd8ed1ab_1
conda-forge/noarch::gspread-5.7.1-pyh1a96a4e_0
conda-forge/noarch::httplib2-0.22.0-pyhd8ed1ab_0
conda-forge/noarch::ipykernel-6.24.0-pyh5fb750a_0
conda-forge/osx-64::ipython-8.4.0-py38h50d1736_0
conda-forge/noarch::jupyter_contrib_core-0.4.0-pyhd8ed1ab_0
conda-forge/noarch::jupyter_contrib_nbextensions-0.7.0-pyhd8ed1ab_0
conda-forge/osx-64::jupyter_highlight_selected_word-0.2.0-py38h50d1736_1005
conda-forge/noarch::jupyter_latex_envs-1.4.6-pyhd8ed1ab_1002
conda-forge/noarch::jupyter_nbextensions_configurator-0.6.1-pyhd8ed1ab_0
conda-forge/noarch::jupyterlab_code_formatter-2.2.1-pyhd8ed1ab_0
conda-forge/noarch::oauth2client-4.1.3-py_0
conda-forge/osx-64::openssl-1.1.1u-h8a1eda9_0
conda-forge/noarch::pylint-venv-3.0.2-pyhd8ed1ab_0
conda-forge/noarch::python-lsp-server-1.7.4-pyhd8ed1ab_0
conda-forge/noarch::python-lsp-server-base-1.7.4-pyhd8ed1ab_0
conda-forge/osx-64::python_abi-3.8-2_cp38
conda-forge/noarch::spyder-notebook-0.4.1-pyh1a96a4e_0
conda-forge/noarch::spyder-terminal-1.2.2-pyhd8ed1ab_1
conda-forge/noarch::spyder-vim-0.1.0-pyhd8ed1ab_0
conda-forge/noarch::uritemplate-4.1.1-pyhd8ed1ab_0
conda-forge/noarch::yapf-0.33.0-pyhd8ed1ab_1

Can you try to install Spyder in a completely new environment?

Lastly, I tried creating a new environment as you told me,  and now I don't see the problem anymore! This means packages from different channels caused it, right.
I appreciate your help! I would like to have Spyder in my base environment, so I'll reconstruct it. I think this is the fastest way to do that. If you have anything that you want to make sure more, please feel free to let me know.

I saw some packages from channel conda-forge but not main, and several packages are from pypi. Most of the packages show defaults and I guess this means main. I listed all of the packages with conda-forge below.

I'm sure that was the problem. Mixing conda and pip is generally not good and base libraries can be incompatible under some circumstances.

Lastly, I tried creating a new environment as you told me, and now I don't see the problem anymore! This means packages from different channels caused it, right.

Yep. particularly mixing conda and pypi.

I appreciate your help! I would like to have Spyder in my base environment, so I'll reconstruct it. I think this is the fastest way to do that. If you have anything that you want to make sure more, please feel free to let me know.

That should work. I recommend using our standalone application in order to avoid this type of issue in the future. But the next best option is to have a dedicated Spyder environment.
I'm glad it's working for you now!


Drawing a Bounding Box Around the Detected Face

I just need som information on what the function RetinaFace.detect_faces return.
{'face_1': {'score': 0.9993057250976562,
  'facial_area': [751, 294, 765, 312],
  'landmarks': {'right_eye': [757.8388, 301.72882],
   'left_eye': [763.83203, 301.46323],
   'nose': [762.1515, 305.3767],
   'mouth_right': [758.4781, 308.56125],
   'mouth_left': [763.1256, 308.4889]}}}

So if my image is 512x1024 (heightxwidth), what does these numbers (coordinates?) represent?
And my target is to draw a box around that detection, say using cv2.rectangle (either need top-left and bottom-right coordinates, or top-left and height and width), how would I do so? I tried playing around with the facial area key, but couldn't get the box around the face.
Also, landmarks is  [757.8388, 301.72882], if this is a coordinate, 757 is already out of my image canvas (512)?
Just some basic doubts, thanks :)

these are directly x and y coordinates


controllercmd: Only observe config file if provided

Since providing --config to a controller is optional, the config file should not be observed if unspecified.
This is required for https://github.com/openshift/service-ca-operator/pull/88

/lgtm
/approve


Issues with results when page count gets high (original #565)

This issue has been migrated from the CC Search Frontend repository
Author: kgodey
Date: Sat Jul 25 2020
Labels: 🏷 status: label work required,🙅 status: discontinued,🛠 goal: fix

Email from an API consumer:
I found that we get some error messages from the CC Search API where the page parameter is high, e.g. +170. For page=169 we still get the results, but for bigger numbers it returns an Internal system error 500 (or 502) even though the page_count is not exceeded.
The example I was going with had the following parameters:

text: "trees"
source: "wikimedia,thorvaldsensmuseum,thingiverse,svgsilh,statensmuseum,spacex,smithsonian,sketchfab,sciencemuseum,rijksmuseum,rawpixel,phylopic,nypl,nasa,museumsvictoria,met,mccordmuseum,iha,geographorguk,floraon,flickr,europeana,eol,digitaltmuseum,deviantart,clevelandmuseum,brooklynmuseum,bio_diversity,behance,animaldiversity,WoRMS,CAPL,500px"
page: 170

When page=169 I get the following metadata:
result_count: 10000
page_count: 250

Another example is:

text: "machine%20learning"
source: "wikimedia,thorvaldsensmuseum,thingiverse,svgsilh,statensmuseum,spacex,smithsonian,sketchfab,sciencemuseum,rijksmuseum,rawpixel,phylopic,nypl,nasa,museumsvictoria,met,mccordmuseum,iha,geographorguk,floraon,flickr,europeana,eol,digitaltmuseum,deviantart,clevelandmuseum,brooklynmuseum,bio_diversity,behance,animaldiversity,WoRMS,CAPL,500px"
page: 201

When page=200 I get the following metadata:
result_count: 10000
page_count: 250

Original Comments:
Issue author dhirensr commented on Mon Jul 27 2020:

I tried to reproduce the same error for the first query = trees ,same sources , page 170 was failing sometimes with 502 bad gateway and sometime's it worked with Postman, and also sometimes it's failing with smaller page numbers like page =100 ,150 etc
I guess this error is being caused due to server getting overloaded and isn't a bug in the code.
source

aldenstpage commented on Thu Aug 06 2020:

It looks like the cause of this is inefficient link rot validation. If you jump straight to page 170 before any other similar requests have been made and cached, the result is that the server walks through every image in the prior pages and sends a HEAD request. That means 3400 HEAD requests for q=trees&page=170! This times out and you get a gateway error. The good news is that most people start on page 0 and work their way up to it; if you take that approach, the page works since the cache is warmed up.

It is absolutely necessary to validate all of the prior images exist in order to prevent inconsistent result pagination.
I would classify this as a minor bug, as the overwhelming majority of users do not paginate deeply or make cold jumps to the end of the search results. To fix it would requires overhauling image validation to be more efficient, which is feasible but will take some time due to the complexity in this area.
Here are our options:
Preferred

Explicitly don't let users paginate so deeply. Nobody is going to care if we only expose the first 20 pages of results. Easy and cheap.

BONUS: Reduce technical debt in the image validation area. I recommend scrapping this bitmask validation cache and instead making Elasticsearch aware of link rot at the last moment; that way we can leave the complexity of ensuring result consistency to Elasticsearch. This will be harder than you think it will be because it is a performance sensitive problem.

Less preferred

Buy bigger EC2 instances with more network bandwidth and cores for making concurrent validation requests. This is probably limited by number of maximum concurrent requests that each server allows. Easy, expensive, uncertain.
Use a cluster of dedicated servers for performing link validation. Hard, expensive.
source

kgodey commented on Thu Aug 06 2020:

Nobody is going to care if we only expose the first 20 pages of results. Easy and cheap.

This was a bug that X5gon ran into, they are using our API to power their image search for OER. So someone cares. :)
source
aldenstpage commented on Thu Aug 06 2020:

Yes, one exception! But we should have an alternative option for people who are looking to bulk scrape our whole catalog, such as a data dump or a bulk load endpoint. The search endpoint is optimized for finding the best results for your search query, not bulk downloads. I would also expect that the deeper you go, the worse the results are.

You'll find that other search products often limit the result set as well.
source

This issue was fixed (as described) in #859. Further work will happen to improve dead link validation but at the moment this issue as described is no longer a problem.


Provide better healthchecks

Proposal
Follow-up to #25. Once https://github.com/wiremock/wiremock/issues/2164 is implemented in WireMock Core and added to the WireMock Docker, it would be nice to adapt the code to use better healthcheck endpoint for newer versions of the container image
References
No response

While https://github.com/wiremock/wiremock/issues/2164 is not implemented , as noted by @wallid , we need another health check that would at least verify that the instance can serve some mock endpoints. It will be also useful for any 2.x tests
I suggest the following:

If any withMapping() method is passed, note that the mappings should be present
If so, also verify the response of /__admin/mappings and ensure that the response is not null

Now we can do better healtchecks starting from WireMock 3.0

@oleg-nenashev I can take this up

Go for it

started working on the same. I will raise PR in sometime.

@oleg-nenashev created PR for the same.


Don't link to repos, link to branches from repo text

In the sidebar, repo text now links to repo-branch, branch text is no longer a link:

On the starred branch dashboard, same idea:

/cc @jhaber

:dancers:


update supportModelType, gpt-4-turbo-2024-04-09, gpt-4-turbo

This pull request extends the supportModelType library by adding two new models: gpt-4-turbo-2024-04-09 and gpt-4-turbo.

Thank you for maintaining this project


[bug] size change callback from _MeasureSize not working with AnimatedSize

To Reproduce
class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> with SingleTickerProviderStateMixin {
  String text = "Back Layer 1";
  double height = 100;

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: "Backdrop Example",
      theme: ThemeData(
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: BackdropScaffold(
        appBar: BackdropAppBar(
          title: Text("Backdrop Example"),
          actions: <Widget>[
            LayoutBuilder(
              builder: (context, constraints) => IconButton(
                icon: Icon(Icons.terrain),
                onPressed: () {
                  setState(() {
                    height = 200;
                    text = "Back Layer 2";
                  });
                },
              ),
            ),
          ],
        ),
        stickyFrontLayer: true,
        backLayer: AnimatedSize(
          vsync: this,
          duration: Duration(milliseconds: 200),
          child: Container(
            height: height,
            child: Center(child: Text(text)),
          ),
        ),
        frontLayer: Center(
          child: Text("Front Layer"),
        ),
      ),
    );
  }
}

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Additional context
Reported by: @proninyaroslav

@proninyaroslav Test the fix against fix/measure_size branch.

Works great, thanks.


Update stdev-transact-sql.md

Make OVER clause optional.

@daschall : Thanks for your contribution! The author, @edmacauley, has been notified to review your proposed change.


[BUG] Ui to standard when Authelia is used

The bug
Thanks for UpSnap!
I'm using it on Docker with NPM (NGINX Proxy Manager) and want to use it behind Authelia as an additional layer of security.
However, when I add the Authelia code in NPM, open UpSnap via it and log in, the UI appears, but without my set up devices (+ my favicon is gone). When I remove the Authelia code again, everything loads normally again. Apparently UpSnap is not compatible with Authelia.
Since I don't know how UpSnap works, I hope one of you can tell me which part of Authelia (see below) is interfering with UpSnap.
This is the Authelia config for NPM:
include /snippets/authelia-location.conf;

location / {
    include /snippets/proxy.conf;
    include /snippets/authelia-authrequest.conf;
    proxy_pass $forward_scheme://$server:$port;
}

I have attached the files mentioned in the script. (I have renamed it to .txt so that GitHub will accept it)
authelia-authrequest.txt
proxy.txt
authelia-location.txt
I am very grateful for any help! <3
The OS that UpSnap is running on
Docker
Version of UpSnap
4.2.12 (newest)
Your docker-compose.yml content
version: "3"
services:
  upsnap:
    container_name: upsnap
    image: ghcr.io/seriousm4x/upsnap:4
    network_mode: host
    restart: unless-stopped
    volumes:
      - /data/upsnap:/app/pb_data
    entrypoint: /bin/sh -c "./upsnap serve --http <IP_ADDRESS>:4444"

Reproduction steps
Install UpSnap
Setup some Devices in the UI
Add the Authelia Code to NGINX Config

Additional information
No response

i was able to further identify the problem. it is due to the following line in "authelia-authrequest.conf":
auth_request /internal/authelia/authz;
the command ensures that users have to log in if they are not logged in.
In addition, here is the error from the browser console:

(these are the lines mentioned in the error. once underlined in red and once marked in blue)

I hope that someone can help me!
PS: I have seen that the author of the repo is from Germany... Wir können auch gerne auf Deutsch weiter schreiben, ich komme auch aus Deutschland 👋

Haven't used authelia yet, but make sure websockets are working. That's what upsnap relies on.
Also try 4.2.13-beta.2 as this fixed an issue with settings_public which you also mentioned.

Hey! Authelia user here that has just figured out the (very simple) reason why it wouldn't work. You need to forward your Authorization headers. Not sure how you would do it in NPM, but in your Location directive you need to add the following:
proxy_set_header Authorization $http_authorization;
proxy_pass_header Authorization;


Make BufferedIO#read respect the sync attribute

Fixes #1306

The problem that sync? seems to be only for writing:

Turns on/off IO buffering. When sync is set to true, no buffering will be done (that is, writing to this IO is immediately synced to the underlying IO).

So this doesn't seems to be the right fix for this. Instead seek should drop the read buffer (it doesn.

Superseded by #1303


fix: introduce constraint on cryptography version

Introduce an upperbound constraint on the package cryptography to resolve the problems caused by the latest release 42.0.0.
Additional info on the breaking changes and the errors can be found here.
Closes #234

exceeded by https://github.com/italia/eudi-wallet-it-python/pull/236
this PR will be closed


Add CSV upload for course information (on Admin's page for maintaining courses)

User Story
As a admin I can upload courses from a csv so that I don't have to type them all in.
Acceptance Criteria

[ ] 'Upload CSV' button exists and only shows up for admins
[ ] 'Upload CSV' button correctly updates the courses page and database with courses based on the csv uploaded

Implementation Todos
Front end:

[ ] 'Upload CSV' button exists and calls backend to do CSV uploading
[ ] If file is not a csv, show an error and description of error on the front end.

Back end:

[ ] Endpoints for CSV upload that correctly update course table with new courses that are parsed from CSV
[ ] Errors returned if file is not a CSV, if CSV is malformed, or any other issues.

Testing:

[ ] 'Upload CSV' button front end tests
[ ] Back end tests for uploading CSV endpoints
[ ] Back end tests for database getting updated with correct information
[ ] All previous tests pass

You can refer to proj-mapache-search of how they do their csv uploads


Allow filtering examples by language

Some examples are available in multiple languages; some only in one. It would be nice to have an option to filter by language.
A simple option would be to just add the language to the tags (either manually or automatically).

I guess we want that filtering both in the in-viewer examples browser and on https://www.rerun.io/examples/real-data


Travis Integration

There's been some talk about integrating travis-ci to partially automate merging pull requests.  Here's some ideas.

[x] Provide a link to the build so reviewers can test and read the doc without pulling.
[x] Run the tests.  Even if we have to run the non-WebGL tests only to start.  We can do better over time with different browsers, platforms, GPU vendors, etc.  Perhaps js-test-driver and BrowserStack are useful.
[x] Publish new releases to npm
[ ] Make the latest version of master available on the website downloads page (Not 100% sure if this is a good idea)
[x] Warning if the build fails
[x] Warn if doc build has warnings or errors.  The doc build might need some optimizations.
[x] Run JSHint

Other ideas:

[ ] Run code coverage and warn if coveraged decreased.  Or warn if coverage for the new code is poor.

Or at least include a link to the build instrumented for coverage so it can be ran manually.

[ ] Is it possible to get reliable test performance?  If so, warn if the new/modified tests significantly slowdown the tests.
[ ] If CHANGES.md was not updated, provide a reminder to ask if it needs to be.
[ ] If files were added/removed/modified in ThirdParty and LICENSE.md was not updated, provide a reminder to ask if it needs to be.
[ ] If we don't have a CLA for the github user and the commits are not signed, provide a reminder about the CLA. CC #574
[ ] Warn if new public members do not have reference doc.

This could be of interest, for example, to check the GitHub username against a database of users who signed the CLA: https://developer.github.com/v3/repos/statuses/

@mramato is there any low-ish hanging fruit here that @ggetz could look at for the code sprint?

Publish new releases to npm

FYI, this is just going to be an automatic part of the build process, and nothing to do with Travis.

Related to #3571.

@mramato OK to close this as duplicate with the ESLint, etc. work @omh1280 is doing this summer?


Ensure errors thrown from submit handler are not silenced

Fixes https://github.com/erikras/redux-form/issues/3303
In the very likely case that an error is encountered during a submit callback we need to be able to reliably detect any failures.
This restores the correct behavior stated in the documentation:

Submits the form. [You'd never have guessed that, right?] Returns a promise that will be resolved when the form is submitted successfully, or rejected if the submission fails.

This will revert the change made in https://github.com/erikras/redux-form/pull/3227, but throwing the error is a far better compromise that benefits a much larger set of redux-form users. It's possible to silence errors in your own code, but not possible to recover discarded errors from inside an isolated context in a lib.

Hi @10xjs, @erikas,
While I 100% agree with this pull, errors should not be swallowed, I'm wondering how we are supposed to consume the error thrown here?
At the moment the error I throw in asyncValidate is not handled anywhere and ends up in the console. I'd love to catch the error, but I can't find anywhere to catch what this change throws.
Any tips?

@dave-irvine I haven't used asyncValidate myself, but I believe that you are able to catch its errors with the onSubmitFail prop. (https://github.com/erikras/redux-form/blob/master/src/handleSubmit.js#L107)

Hi @10xjs, unfortunately no matter what you do in onSubmitFail, https://github.com/erikras/redux-form/blob/master/src/handleSubmit.js#L109 rejects with the errors, which are then subsequently thrown by your change. :(

I wonder if we need a new onAsyncValidationFail prop?


NSErrorFailingURLStringKey

NSErrorFailingURLStringKey=https://graphic-arts.bamaying.com/ceres/yawe/196/6dd10a9af1e54f379634c7809f5b5112?e=1619078222&token=whETJFhhtd1CpA5EMMxs9v5Tfaphcruefy_iSzeS:VfGzUcj35sA4mBieuEZyj_N6xuw=

NSLocalizedDescription=A server with the specified hostname could not be found.

NSLocalizedDescription=A server with the specified hostname could not be found.

That errors means you have some DNS issue. It is either your device or the DNS provider. So I suggest try to check the network first...


Provide a title for the chart in the chart options?

Is there a way to add a title to the chart?

Currently, it's not provided via options. I think it can be added, if it will be demanded by community.

When this feature will be available?

+1


How to compile Ruby gems with native extensions?

I am trying to compile a bunch of gems with native extensions like grpc, but it fails with:
third_party/abseil-cpp/absl/time/internal/cctz/src/time_zone_lookup.cc:26:10: fatal error:
'CoreFoundation/CFTimeZone.h' file not found
#include <CoreFoundation/CFTimeZone.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [Makefile:768:
/Users/dpetrovs/ghq/github.com/platogo/pas/.devenv/state/.bundle/ruby/3.2.0/gems/grpc-1.57.0/src/ruby/ext/grpc/objs/opt/third_party/abseil-cpp/absl/time/internal/cctz/src/time_zone_lookup.o]
Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory
'/Users/dpetrovs/ghq/github.com/platogo/pas/.devenv/state/.bundle/ruby/3.2.0/gems/grpc-1.57.0'
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/nix/store/jwh59hk8szbi06zgcvshzr9bp7pdwwyx-ruby-3.2.2/bin/$(RUBY_BASE_NAME)

extconf failed, exit code 1

My env:
ProductName:		macOS
ProductVersion:		14.3
BuildVersion:		23D56
devenv: 0.6.3
nix (Nix) 2.19.3

I also had to explicitly set to use clang and clang++ as the compilers so other gems would actually compile.
{
  env.CC = "clang";
  env.CXX = "clang++";

  languages = {
    ruby = {
      enable = true;
      bundler.enable = true;
      version = "3.2.2";
    };
    nix.enable = true;
    java.enable = true;
  };

  # https://devenv.sh/packages/
  packages = [
    pkgs.curl
    pkgs.dynamodb-local
    pkgs.git
    pkgs.git-crypt
    pkgs.gnupg
    pkgs.imagemagick
    pkgs.libffi
    pkgs.libpqxx
    pkgs.lua
    pkgs.nodejs
    pkgs.yarn
    pkgs.gnumake
    pkgs.pkg-config
    pkgs.ruby.devEnv
    pkgs.libyaml
    pkgs.libcxxabi
    pkgs.grpc
    pkgs.openssl
  ] ++ lib.optionals pkgs.stdenv.isDarwin (with pkgs.darwin.apple_sdk; [
    frameworks.CoreFoundation
    frameworks.Security
    frameworks.SystemConfiguration
  ]);
}

It seems to be complaining that it cannot find CoreFoundation, even though I add it?

Upd: linking to #966

Does it reproduce with #745?

Could you try with 1.0.1 that was released yesterday?


Fixing addProvider function, 'authProviders' was not getting updated

The fix for adding custom providers (https://github.com/fullstackreact/react-native-oauth/pull/70) was not working for me. Below line was used to merge providers in "addProvider" function
Object.assign({}, authProviders, provider);
Above statement merges objects "authProviders" and "provider" into a new object which is returned by the above statement when '{}' is passed as the first argument.

Hi ! did you manage to get it work @rajchourasia ?

@ydeshayes yes I did.
Check out my repo https://github.com/rajchourasia/react-native-goodreads-login


fs/NVS: NVS is not compatible with flash memories which have 0x00 as erased

This is informative issue, not a bu really
NVS design assumes 0xff as memory erased state. So it will doesn't work on devices which has 0x00 as erased byte state (e.g. some stm32 embedded. and native_posix with the flash simulator )
To Reproduce
Try NVS sample using native_posix target
[EDIT]: native_posix was fixed
Try NVS sample using a target which have 0x00 as erased byte flash value.

The solution https://github.com/zephyrproject-rtos/zephyr/pull/25947 does not seem to work correctly.

@de-nordic , might this be caused by line 417 in flash_simulator.c that initializes flash to 0xff ?

@de-nordic , might this be caused by line 417 in flash_simulator.c that initializes flash to 0xff ?

Thanks @Laczen! That may be the case, I will check this.

@de-nordic , might this be caused by line 417 in flash_simulator.c that initializes flash to 0xff ?

There was a problem, but still this is not the root cause.

@de-nordic , might this be caused by line 417 in flash_simulator.c that initializes flash to 0xff ?

There was a problem, but still this is not the root cause.

Do you have an idea where it fails?

@de-nordic , might this be caused by line 417 in flash_simulator.c that initializes flash to 0xff ?

There was a problem, but still this is not the root cause.

Do you have an idea where it fails?

I narrowed it to nvs_read_hist, where it returns -ENOENT, due all conditions evaluating to 1.
I still do not understand operation of NVS good enough to write more on the subject.

@de-nordic, I am a bit puzzled, did you run the test before the merge ? -> I was looking at what would be different from your local test and the automated test.

@de-nordic, I am a bit puzzled, did you run the test before the merge ? -> I was looking at what would be different from your local test and the automated test.

Yes I did. I run both of the nvs tests each time I have updated something. I do not know why it did pass prior.

@de-nordic, I am a bit puzzled, did you run the test before the merge ? -> I was looking at what would be different from your local test and the automated test.

Yes I did. I run both of the nvs tests each time I have updated something. I do not know why it did pass prior.

OK, maybe it is in the 0x00 overlay file (< 0x00 > instead of <0x00> ?)

I have printed out the values that are used for initialization of simulated flash and they are 0.
Booting from ROM..Optimal CONFIG_X86_MMU_PAGE_POOL_PAGES 6
Intitlizing to 0
*** Booting Zephyr OS build zephyr-v2.3.0-607-g16763ff9b6db  ***
Running test suite test_nvs
===================================================================
START - test_nvs_init
I: 5 Sectors of 1024 bytes
I: alloc wra: 0, 3f0
I: data wra: 0, 0
 PASS - test_nvs_init
===================================================================
START - test_nvs_write
I: 5 Sectors of 1024 bytes
I: alloc wra: 0, 3f0
I: data wra: 0, 0
wlk 3f0 3f0
wlk.id 0 1
wlk_ate.len 0
cnt 0 0
1
1
wlk 3e8 3e8
wlk.id 0 1
wlk_ate.len 0
cnt 0 0
1
1

    Assertion failed at WEST_TOPDIR/zephyr/tests/subsys/fs/nvs/src/main.c:100: execute_long_pattern_write: (len == sizeof(rd_buf) is false)
nvs_read unexpected failure: -2
 FAIL - test_nvs_write

Intitlizing to 0 comes from the flash driver.

Same run but on the non-0x00 test:
ESC[0mSeaBIOS (version rel-1.12.1-0-ga5cab58-dirty-20200202_184651-8999447e980d-zephyr
)
Booting from ROM..Optimal CONFIG_X86_MMU_PAGE_POOL_PAGES 6
Intitlizing to ff
*** Booting Zephyr OS build zephyr-v2.3.0-607-g16763ff9b6db  ***
Running test suite test_nvs
===================================================================
START - test_nvs_init
I: 5 Sectors of 1024 bytes
I: alloc wra: 0, 3f0
I: data wra: 0, 0
 PASS - test_nvs_init
===================================================================
START - test_nvs_write
I: 5 Sectors of 1024 bytes
I: alloc wra: 0, 3f0
I: data wra: 0, 0
wlk 3f0 3f0
wlk.id ffff 1
wlk_ate.len ffff
cnt 0 0
1
0
wlk 3e8 3e8
wlk.id 1 1
wlk_ate.len 200
cnt 1 0
0
0
 PASS - test_nvs_write

@de-nordic, it seems that even the first write fails, in the flash_simulator there is a suspicious line at 261-262:
/* only pull bits to zero */
*(FLASH(offset + i)) &= *((uint8_t *)data + i);

shouldn't this be changed ?

@Laczen Yes, you have identified the problem correctly. This is the line. NVS requires no changes. I will fix this and extend testcases for flash simulator.

This issue has been solved, closing.


It is possible to send an array with keys as $arguments in publish method ?

I try to send an array with keys like this:
//this will not work
$this->session->publish('com.myapp.position_updated', array('user'=>12,'level'=>10));

//but this will work
$this->session->publish('com.myapp.position_updated', array(1,1,1));

This is the error I got in my webpage when trying with keys:
Potentially unhandled rejection [3] {"error":"com.example.update_position.error","args":[""],"kwargs":{"xdebug_message":"\nInvalidArgumentException:  in C:\\Users\\xxxx\\PhpstormProjects\\Thruway2\\vendor\\voryx\\thruway\\src\\Thruway\\Message\\Traits\\ArgumentsTrait.php on line 72

Do I'm missing something ?

All associative arrays are converted to objects when serialized through json_encode. Because JSON does not have a way to represent associative arrays and objects differently, there is not much that you can do to get around if.
In order to use it as an array, you would need to cast it back once it is in your procedure.
$myRpcEndpoint = function ($args) {
    $myAssociativeArray = (array)$args[0];

    // ... rpc stuff
};

$encoded = json_encode(array('user'=>12,'level'=>10));

var_dump($encoded);
// outputs: string(22) "{"user":12,"level":10}"

$decoded = json_decode($encoded);

var_dump($decoded);
// outputs:
// class stdClass#1 (2) {
//   public $user =>
//   int(12)
//   public $level =>
//   int(10)
// }

var_dump((array)$decoded);
// outputs:
// array(2) {
//    'user' =>
//    int(12)
//    'level' =>
//    int(10)
// }

Sorry, I misread your original question.
The arguments need to be sent as a non-associative array (array without string keys). If you wrap your array inside another array (send it as the first argument) it will pass through (although it will get converted to an object in the process as stated above).
$this->session->publish('com.myapp.position_updated', array(array('user'=>12,'level'=>10)));

Thanks for this fast response, I'll try it.

It works like a charm. Thank a lot!


Cypress e2e test fails from newly created project with vue cli and git-bash

Version
3.0.5
Node and OS info
node v8.9.3, npm 5.5.1,git-bash (Git version 2.19.1), Windows 7
Steps to reproduce
From git-bash in Windows.
Create a project with vue cli.
vue create hello-world

Use those vue-cli plugins : vue-router, vuex, sass, babel, eslint, unit-jest, e2e-cypress
cd hello-world
npm install

Run e2e test
npx vue-cli-service test:e2e --headless

What is expected?
Passing end to end from tests/e2e/specs/test.js
What is actually happening?
$ npx vue-cli-service test:e2e --headless
npx: installed 1 in 1.447s
Path must be a string. Received undefined
<EMAIL_ADDRESS> INFO  Starting e2e tests...
 INFO  Starting development server...
 DONE  Compiled successfully in 7436ms 17:07:31
  App running at:
  - Local:   http://localhost:8080/
  - Network: http://<IP_ADDRESS>:8080/

  App is served in production mode.
  Note this is for preview or E2E testing only.

================================================================================
  (Run Starting)
  ┌────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:  3.1.0                                                            │
  │ Browser:  Electron 59 (headless)                                           │
  │ Specs:    1 found (test.js)                                                │
  └────────────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────────────

  Running: test.js... (1 of 1)
(node:12836) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
 ERROR  Failed to compile with 1 errors17:07:45

 error

Entry module not found: Error: Can't resolve 'D:\hello-world\tests\e2e\specs\integration\test.js' in 'D:\hello-world'

When I run cypress GUI I get the same issue.
The configuration I get is the following :
{
animationDistanceThreshold: 5,
baseUrl: 'http://localhost:8080',
blacklistHosts: null,
chromeWebSecurity: true,
defaultCommandTimeout: 4000,
env: {},
execTimeout: 60000,
fileServerFolder: '',
fixturesFolder: 'tests/e2e/fixtures',
hosts: null,
integrationFolder: 'tests/e2e/specs',
modifyObstructiveCode: true,
numTestsKeptInMemory: 50,
pageLoadTimeout: 60000,
pluginsFile: 'tests/e2e/plugins/index.js',
port: null,
reporter: 'spec',
reporterOptions: null,
requestTimeout: 5000,
responseTimeout: 30000,
screenshotsFolder: 'tests/e2e/screenshots',
supportFile: 'tests/e2e/support/index.js',
taskTimeout: 60000,
testFiles: '**/*.*',
trashAssetsBeforeRuns: true,
userAgent: null,
video: true,
videoCompression: 32,
videoUploadOnPasses: true,
videosFolder: 'tests/e2e/videos',
viewportHeight: 660,
viewportWidth: 1000,
waitForAnimations: true,
watchForFileChanges: true
}

I have this error:

Running completion hooks...error: '@cypress/webpack-preprocessor' should be listed in the project's dependencies, not devDependencies (import/no-extraneous-dependencies) at vue-store-locator\tests\e2e\plugins\index.js:3:17:
1 | // https://docs.cypress.io/guides/guides/plugins-guide.html
2 | /* eslint-disable import/no-extraneous-dependencies global-require */

3 | const webpack = require('@cypress/webpack-preprocessor');
|                 ^
4 |
5 | module.exports = (on, config) => {
6 |   on('file:preprocessor', webpack({

error: Unexpected require() (global-require) at vue-store-locator\tests\e2e\plugins\index.js:7:21:
5 | module.exports = (on, config) => {
6 |   on('file:preprocessor', webpack({

7 |     webpackOptions: require('@vue/cli-service/webpack.config'),
|                     ^
8 |     watchOptions: {},
9 |   }));
10 |

error: '@vue/cli-service' should be listed in the project's dependencies, not devDependencies (import/no-extraneous-dependencies) at vue-store-locator\tests\e2e\plugins\index.js:7:21:
5 | module.exports = (on, config) => {
6 |   on('file:preprocessor', webpack({

7 |     webpackOptions: require('@vue/cli-service/webpack.config'),
|                     ^
8 |     watchOptions: {},
9 |   }));
10 |

@SLMNBJ This is an unrelated issue. Caused by a missing comma in the generated file. Please manually add that comma to your file: https://github.com/vuejs/vue-cli/commit/4e90afe18980f0f288908a7f7ef0974dc5a4545f#diff-1c4d741ece51a603d9d28f55c9d1e306

Why did you run this command using npx? npm run test:e2e should suffice.
Please update your npm. Could be this issue: https://github.com/zkat/npx/issues/144 which has been fixed in https://github.com/npm/npm/pull/19608 and shipped with npm v5.8.0

I got this problem too, both headless and GUI. I ran it on Node 8.12.0, NPM 6.4.1, Yarn 1.10.1.
Output as a reference:
E:\Repositories\repo-name (master -> Github)
λ yarn test:e2e --headless
yarn run v1.10.1
$ vue-cli-service test:e2e --headless
 INFO  Starting e2e tests...
 INFO  Starting development server...

 WARNING  Compiled with 2 warnings                                                                                18:48:20

 warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  app (350 KiB)
      js/chunk-vendors.19368321.js
      css/app.b7b6aaa9.css
      js/app.3e498f3d.js

 warning

webpack performance recommendations:
You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
For more info visit https://webpack.js.org/guides/code-splitting/

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

  App is served in production mode.
  Note this is for preview or E2E testing only.

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:    3.1.0                                                                              │
  │ Browser:    Electron 59 (headless)                                                             │
  │ Specs:      1 found (test.js)                                                                  │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running: test.js...                                                                      (1 of 1)
(node:38848) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
 ERROR  Failed to compile with 1 errors18:49:09

 error

Entry module not found: Error: Can't resolve 'E:\Repositories\repo-name\tests\e2e\specs\integration\test.js' in 'E:\Repositories\repo-name'

@sodatea I ran it with npx in order to use --headless

I upgraded to npm 6.4.1 and node 10.12.0 and still get the same result.
My guess would be that git-bash for windows might mess the path but I don't know enough of it's internal to actually try things about it.
By the way, I tried it on a linux machine and it works fine. But unfortunately, I can't use this machine yet for development purpose.

@marc-bouvier You can also use npm run test:e2e -- --headless

Am also getting this error on Windows 10, have run from git-bash and from within the Vue GUI, both times output is:
 INFO  Starting development server...

 DONE  Compiled successfully in 3481ms                                                                                8:39:39 PM

  App running at:
  - Local:   http://localhost:8081/
  - Network: http://<IP_ADDRESS>:8081/

  App is served in production mode.
  Note this is for preview or E2E testing only.

 Use new API on `.hooks` instead
 ERROR  Failed to compile with 1 errors20:39:57

 error

Entry module not found: Error: Can't resolve 'D:\project\tests\e2e\specs\integration\test.js' in 'D:\project\'

It seems to be adding an additional folder to the file path? D:\project\tests\e2e\specs\integration\test.js doesn't exist, D:\project\tests\e2e\specs\test.js does.
Here's my config:
animationDistanceThreshold: 5,
baseUrl: 'http://localhost:8081',
blacklistHosts: null,
chromeWebSecurity: true,
defaultCommandTimeout: 4000,
env: {},
execTimeout: 60000,
fileServerFolder: '',
fixturesFolder: 'tests/e2e/fixtures',
hosts: null,
integrationFolder: 'tests/e2e/specs',
modifyObstructiveCode: true,
numTestsKeptInMemory: 50,
pageLoadTimeout: 60000,
pluginsFile: 'tests/e2e/plugins/index.js',
port: null,
reporter: 'spec',
reporterOptions: null,
requestTimeout: 5000,
responseTimeout: 30000,
screenshotsFolder: 'tests/e2e/screenshots',
supportFile: 'tests/e2e/support/index.js',
taskTimeout: 60000,
testFiles: '**/*.*',
trashAssetsBeforeRuns: true,
userAgent: null,
video: true,
videoCompression: 32,
videoUploadOnPasses: true,
videosFolder: 'tests/e2e/videos',
viewportHeight: 660,
viewportWidth: 1000,
waitForAnimations: true,
watchForFileChanges: true}

Here's the complete debug logs of running the same project on both Windows & macOS:
https://gist.github.com/sodatea/ffd402ed21a32cb49448da3c886d212d
By searching cypress:server:preprocessor getFile we can see 3 matches in each log and it is the first one that's causing the error.
On Windows the output is
Mon, 15 Oct 2018 03:05:48 GMT cypress:server:socket watch test file 'integration\\test.js'
Mon, 15 Oct 2018 03:05:48 GMT cypress:server:socket will watch test file path 'tests\\e2e\\specs\\integration\\test.js'
Mon, 15 Oct 2018 03:05:48 GMT cypress:server:preprocessor getFile C:\Users\soda\test-vue-cli\hello-world\tests\e2e\specs\integration\test.js

Note that the second line, cypress did not replace the integration\\ with empty string as expected (https://github.com/cypress-io/cypress/blob/93966e30db6fd1c7a2e7defdbfbb5127e06570f7/packages/server/lib/socket.coffee#L76).
So I think it's a duplicate of https://github.com/cypress-io/cypress/issues/712, which has been fixed in https://github.com/cypress-io/cypress/pull/2400 but not yet shipped.


Very confusing quick start Error: theme basic-reason not found

I have tried the instruction from the quick-start and ran into this error :
npm install -g bs-platform
bsb -init my-first-app -theme basic-reason # --> Fails here
cd my-first-app
npm run start

I don't think I'm supposed to get this error, previous to that bsb has been installed correctly using npm I can provide further details if needed to diagnose what's going on here.
Here is the ouput during the installation of bsb :
/usr/bin/bsb -> /usr/lib/node_modules/bs-platform/bsb
/usr/bin/bsc -> /usr/lib/node_modules/bs-platform/bsc
/usr/bin/bsrefmt -> /usr/lib/node_modules/bs-platform/bsrefmt
/usr/bin/bstracing -> /usr/lib/node_modules/bs-platform/lib/bstracing

><EMAIL_ADDRESS>postinstall /usr/lib/node_modules/bs-platform
> node scripts/install.js

ninja binary is already cached and installed:  /usr/lib/node_modules/bs-platform/linux/ninja.exe
checkoutput: BuckleScript 8.3.1 ( Using OCaml:4.06.1+BS )
 ocaml version 4.06.1+BS
Prebuilt compiler works good
+<EMAIL_ADDRESS>added 1 package from 1 contributor in 8.46s

bsb -init my-first-app -theme basic-reason
Making directory my-first-app
Available themes:
basic
generator
minimal
node
react-hooks
react-starter
tea
Error: theme basic-reason not found

Getting that too. Very anti-climatic.

Found any workaround or fix @mblarsen ?

It seems that the theme has indeed been dropped https://github.com/rescript-lang/rescript-compiler/pull/4640
It really makes me feel that ReasonML and BuckleScript will not work together for a long time, it's really concerning...

The only workaround is not installing the latest bs-platform (@8.2.0) and use the "basic-reason".

There is no other possibility than just not installing the latest bs-platform at the moment? @davesnx
Is there any way that the change on rescript-lang/rescript-compiler#4640 would get reversed ?
I just don't understand what is the motivation behind the removal of this theme, like it's being used by devs and I don't think it's breaking anything in their codebase hence why remove it ? I'm clueless to this.
But in the end I'm really just a beginner here so I could be wrong about all the above.

I just don't understand what is the motivation behind the removal of this theme, like it's being used by devs and I don't think it's breaking anything in their codebase hence why remove it ? I'm clueless to this.

I'm just like you, totally puzzled by the whole ReScript rebranding 😕
It seems that the ReScript team is trying to remove all tracks of "ReasonML" from the doc and the tooling to make it less confusing for the newcomers. Ironically, it's even more confusing, especially since many existing libraries and docs all point to ReasonML, and that ReasonML as a brand, is still way stronger than ReScript...
To make it clear, if someone wants to use BuckleScript, they have to use ReScript or get a degraded experience if they use ReasonML/OCaml (no themes, no updates (the OCaml version used by the compiler is still 4.06 when the lastest version of the official compiler is already 4.11, no docs, etc...). For the native developments though, Dune is a very nice tool and it supports ReasonML out of the box 😄
(Funnily enough I created an issue earlier: https://github.com/facebook/reason/issues/2634 to get some clarification from the ReasonML team regarding the support of the language for the web as it seems ReasonML might be used mostly with the native OCaml compiler from now on).

Hey @AkechiShiro!
Not sure the template is what you're looking for, but Spin has a template for ReScript: https://github.com/tmattio/spin-rescript
It supports both Reason and ReScript syntaxes.
I'm happy to work on other ReScript templates if this one does not quite suit your needs. Hope it helps 🙂

hi @AkechiShiro , this is an unexpected breakage
Fixed in https://github.com/rescript-lang/rescript-compiler/pull/4808
I did not watch this repo, if you have any issues, feel free to report in rescript-compiler repo.

The whole Installation page needs to be rewritten. Reason advertises itself as a natively compiled language, but refers to BuckleScript (wrong name), and still contains a ReScript quickstart guide.
If you check out the ReScript Installation section, you will see that we changed our getting started workflows.

Thanks for the cleaner explanation.

We removed the installation instructions on the ReasonML docs and forward users to the ReScript docs.
(See latest PR)

We removed the installation instructions on the ReasonML docs and forward users to the ReScript docs.
(See latest PR)


Nuke migrating tips content since it is now obsolete.

@calbach does it seem reasonable to remove this documentation?

I'd like to leave it up for now. We still have a few stragglers who are migrating and we haven't officially turned it down yet. Definitely keep this PR pending though. I think we should merge it in about 3 months.


allow to disable report rate limiting through configuration

Added configuration key that disable rate limiting.

Hello,
I am not sure I understand the use case for this?
Not rate-limiting reports will kill your App's performance by spawning lots of background upload tasks, while not providing any additional information.
Thanks!

I think this should be the decision of the application. You are right that in most cases, this might result in degraded performance. But there are cases (for example, small apps with a few network requests) this it will not affect performance. I am still thinking of whether or not we will use it - I wanted to know on each violation so we can have a better understanding of the impact to our users. But I am didn't decided yet if I will do it with verbose reports, or specific logs from api calls failures. So, to summarize that, I would like  to have the option to enable it, in case we decide to go with it. Does it make sense?

Hello,
Thanks for the clarification.
It still doesn't feel like the right way to do this, so for now I don't think I will merge this PR. For instance, what you could do is use the vendor identifier in the report to count the number of devices that received an error. I still do not think that getting a report for every single failure provides any additional information that's useful to the developer. Let me know if there is something I missed.
Thanks!

As it still unclear to me which approach is better, I will agree with you for now. I will update if I will notice we need more information that what we have today. Also, looking back, I am sorry - I should have open an issue first.

Sounds good and no worries about the PR!


Reduce quality image

Describe the bug
After upload image reduce quality image
Original:

after upload:

after upload through mini_magick:

Server (please complete the following information):

Linux: Ubuntu 20.04.5 LTS
rails: 7.0.8
ruby-vips: 2.2.0

Desktop (please complete the following information):

Linux: Archlinux
Browser chrome
Version  119.0.6045.159

Hello @strangerxx,
Just turn up the quality setting. For example:
$ vips copy berries.jpg x.jpg[Q=90]

To make:

Though images like this should really be stored as PNG, not JPG.

Hello @strangerxx,
Just turn up the quality setting. For example:
$ vips copy berries.jpg x.jpg[Q=90]

To make:

Though images like this should really be stored as PNG, not JPG.

Thank you @jcupitt. But I don't understand why so low quality default. I will see setting Active Storage.

libvips uses the JPEG standard default of 75. You can change the default to 90, but then all your JPEG files will become huge. For example:
$ vips copy k2.jpg x-90.jpg[Q=90]
$ vips copy k2.jpg x-75.jpg[Q=75]
$ ls -l x*
-rw-r--r-- 1 john john 271536 Nov 16 10:58 x-75.jpg
-rw-r--r-- 1 john john 502270 Nov 16 10:58 x-90.jpg

A factor of two difference in filesize for this photo.
A better solution is not to use JPG for this type of image. PNG would be better quality, would maintain transparency, and would be smaller.

@jcupitt Thank you. I understand and will use other format.

For this type of small synthetic image, palette PNG is a good choice:
$ vips copy berries.jpg x.jpg[Q=90]
$ vips copy berries.jpg x.png[strip,palette]
$ ls -l x*
-rw-r--r-- 1 john john   3897 Nov 16 11:02 x.jpg
-rw-r--r-- 1 john john   2937 Nov 16 11:02 x.png

Smaller, and looks better:

@jcupitt  and webp?

It'll be bigger than palette PNG, but webp lossless is often a good choice, yes.

Ok, thank you


Restore the auth/user endpoint used by QFieldCloud

Task linked: DEV-3393 Restore auth/user endpoint


Requirements require updating

Currently, the minimum version insetup.py is Python 3.6, but the minimum Python version for stk is 3.9. This means that users of stko are forced to used outdated versions of stk.

Done by #149


query works in BQ but not through Quix

CREATE TEMP FUNCTION jsonObjectKeys(input STRING)
RETURNS Array
LANGUAGE js AS """
return Object.keys(JSON.parse(input));
"""
;
select
jsonObjectKeys ( '{"a":1,"b":2}'  ) AS ports
from temp.hed_test

merged a fix that should add support to bigquery functions :


libarchive: Update to 3.3.1

I needed some packages on my system to build libarchive, so I added them to the makedepends.
Most of the previous patches are now in upstream, which is awesome.

The makedepends you added should be removed as they are part of base-devel.
Ah, that explains the difference between my msys install and the build bots, I pushed a new patch that with them removed.


Use dep for dependencies

Make setup and predictable builds easier for contributors by locking to
a set of dependencies. Some of the dependencies have been locked to
specific commits on master in order to accomodate projects that do not
ship releases often such as cobra and gomock (see
https://github.com/spf13/cobra/issues/259 for details).

Change mockgen commands to use a -source flag to explicitly point to
the files in vendor for generating mocks. This, for some reason, fixes
a bug in gomock whereby it uses the vendor path as the import path
which breaks some dependencies.
See https://github.com/golang/mock/pull/28 for more details.

Addresses #21.


Does not support appdistribution:distribute command

Getting the following error:
[!] firebase_cli_path: /home/circleci/repo/firebase does not support the appdistribution:distribute command. Please download (https://appdistro.page.link/firebase-cli-download) or specify the path to the correct version of firebase
The version downloaded does have the command.
Any ideas?

Switched to not defining and letting the which fastlane command handle. Works now!

could you explain this am facing this issue


Add support for user-supplied palette + indexed pixel input

Quantizing (palette computation + remapping RGB to indexed) is a slow
process.  If the gif encoder inputs already happen to be indexed
(which it often is when say encoding pixel art into gif anims), this
whole process can be skipped.
This patch allows specifying a palette once on GIFEncoder creation and
makes it possible to pass indexed inputs to GIFEncoder.addFrame.
This is somewhat of a prototype.  Can clean this up if it looks like
this has a chance to be merged.

Sorry for the slow reply, was on vacation. Will review by the end of next week. Seems fine at a glance

Looks good to me. What were the ideas you had for clean-up?
I think before I land I'll readjust everything so it's all var's still for consistency as well as add documentation but it sounds like you had other ideas

Now indexed vs rgb pixel data is heuristically detected based on pixels array length.  A more orthogonal implementation would support all these 3 options:

RGB pixels, compute palette, quantize
RGB pixels + input palette, quantize to given palette (not supported in my patch)
indexed pixels + input palette, basically just pass through everything (this is what I added)

Option 2 would be nice to have as the API would be a bit more orthogonal.
But #3 is what I was after I needed in https://github.com/nurpax/petmate so I just implemented that. Probably makes sense to just merge after any clean up you might have in mind.

Maybe gifencoder options could have a pixelFormat field which could be either RGBA, RGB (can’t recall which you have now) or indexed. This would be explicit and similar to what other imaging apis might have.

I'd prefer to stick to a consistent RGBA input format to avoid changing the API too much. I'm more considering this repo to be in stable API mode than anything else due to my lack of time
I think I'm realizing that the custom palette lookup might be a pain to implement so I'll take some more time to think about it. I'll reply again by the end of next week

Sorry for the delay. I've sided with keeping the PR mostly as is but making the API flexible for option (2) in the future
This should look like:
var gif = new GIF({palette: ...});
gif.addFrame({
  indexedPixels: true
}, [0, 1, ...]);

No need to update anything on your end. I'm going to implement these changes on top of the PR to minimize future back/forths

Okay, done with the updates and released it in 0.7.0
As a heads up, the calculation for palSize was incorrect -- it's always 7 due to using an 8-bit color table. GIFEncoder.js was correcting this inside of analyzePixels:
I also adjusted the palette code to properly represent what the software is currently doing which is writing a new palette every frame
var gif = new GIF(10, 10);
var palette = [0x00, 0x00, 0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF];
gif.addFrame([
  0, 1, ...
], {
  palette: palette,
  indexedPixels: true
});

I'm happy to accept a PR which makes it not do that but I felt it was lying through its teeth
Thanks for the PR and quick back/forths!