Strange behavior: API Gateway is serving a binary

Up version
0.1.10
Description
I'm trying to run this project (https://github.com/franciscocpg/react-semantic.ui-starter/tree/up-deploy, important to use branch up-deploy here) with up, but it's generating a strange binary at https://gdwoyj0la9.execute-api.us-east-1.amazonaws.com/development/.
I've tried to reproduce this problem locally in two ways but I couldn't.
First way

I've cloned up and checkout it to tag v0.1.10 and cloned the project that I mentioned above.
I cd to the project react-semantic.ui-starter folder and checkout the branch up-deploy.
Then I ran go run $GOPATH/src/github.com/apex/up/cmd/up-proxy/main.go inside the project react-semantic.ui-starter folder and accessed http://localhost:${PORT} in a browser successfully.

Second way

I've cloned up and checkout it to tag v0.1.10 and cloned the project that I mentioned above.
I've changed zip.go and added a line after zip.Close() to write the zip file to a temp folder (ioutil.WriteFile("/tmp/test.zip", buf.Bytes(), 0644))
I cd to the project react-semantic.ui-starter folder and checkout the branch up-deploy.
I ran go run $GOPATH/src/github.com/apex/up/cmd/up/main.go to generate /tmp/test.zip (After generating the file I've cancelled the deploy).
Then I unzip the generated file, ran ./main and accessed http://localhost:${PORT} in a browser successfully.

By sucessfully I mean this page is loading correctly in the browser (I was expecting https://gdwoyj0la9.execute-api.us-east-1.amazonaws.com/development/ to load this page too).
So it looks like up-proxy is working and I have no idea why API gateway is serving this binary.
Any thoughts on that?

hmm I'll take a look!

hmm it's been building for ~6m hahaha, if we can reproduce it with something smaller that'd be aweome

hmm it's been building for ~6m hahaha

A loooottt of dependencies. First time build is slow.  :turtle:
Here is my hack. I ran npm i && DIST_PATH=./dist/client/en npm run build && rm -rf node_modules && npm i --production just once and then I change up.json like this:
{
  "name": "react-semantic-ui-starter",
  "hooks": {
    "build": "exit 0"
  }
}

I wonder if Node is compressing AND my proxy is compressing

But if this is happening, shouldn't my second approach reproduce the problem? :thinking:
Now that you mentioned, I'm going to try to reproduce using node v6.10.

closing for now, can't spend too much time with huge codebases but if you can reproduce let me know, using 8.x might help https://github.com/apex/up-examples/tree/master/oss/node-8


[DevTools / JS / Get Started / (2) Triggered The Breakpoint]

Can't trigger the breakpoint ' function onClick() { '  on step two of js debugger demo. I keep getting the event listener click that I just created so the step through doesn't appear to be working as it should in the next step. I've tried incognito, updating to chrome 57, and disabling  lastpass/abp. See here for incognito screenshot:

Any help would be appreciated :)

Hey @dshiling thanks for reporting. You've got an extension that is intercepting your clicks, I assume that's what you mean by lastpass/abp.
So, if I understand correctly, you set the click event breakpoint, then click Add Number 1 and Number 2 on the demo, and then it pauses on the location provided in the screenshot.
From there, have you tried clicking Resume Script Execution. DevTools will continue executing until it encounters another click event. It should eventually land on the line of code mentioned in the tutorial.
Make sense?

Thanks to contributions like yours I updated the feedback response (the section that provided you the link to report this issue) describing how to get past this scenario :)

Thank you for your help! Worked like a charm and glad to know I could provide some decent feedback :)


No reshape rope

Proposed changes
Gives  a small bump on TPS to avoid the two reshapes:
On M2 Ultra (1)

Prompt
Generation
Memory

Pre
430.603
73.586
4.108

Post
430.470
75.072
4.108

I was going to try and squeeze a proper ND implementation but for the sake of not letting this stagnate I will land it and follow up with that.


Deprecate non-standard environment global, introduce system.properties

For Ringo 4 we should deprecate the missleading environment global variable and replace it in the system module. Instead of providing access to the environment, the variable hosts the Java system properties which are an instances configuration.
Instead introduce a new properties (= java.lang.System.getProperty()) export next to env (= java.lang.System.getenv()) in the system module.
There is not intend to remove environment for now.

🙈 This has been used to detect Rhino-based environments, see #88
typeof environment === "object" && ({}).toString.call(environment) === "[object Environment]"

Afais the global environment is only part of Rhino's shell, and not available in the normal global scope.


swiper/vue missing type declarations

This is a (multiple allowed):

[ ] bug
[x] enhancement
[ ] feature-discussion (RFC)

I see that Swiper has already types for swiper/react component included. I would be really cool to add type definitions for swiper/vue component as well. This would allow us to integrate swiper in vue.js projects with typescript easier.

I'm willing to work on this feature with a little guidance from maintainers.

Swiper Version: v3.6.5
Platform/Target and Browser Versions: Typescript

If this helps anyone I wrote a skeleton typings file to get it to atleast work with a typescript vue project:
swiper-t.d.ts
declare module 'swiper/vue' {
  import _Vue from 'vue';

  export class Swiper extends _Vue {}

  export class SwiperSlide extends _Vue {}
}

@GerryWilko you're welcome to contribute :)

@GerryWilko you're welcome to contribute :)

@vltansky Apologies I meant to come back to this and create a PR. I just dropped this in as a comment temporarily. I'll raise a PR tomorrow! 😀

@vltansky Apologies I meant to come back to this and create a PR. I just dropped this in as a comment temporarily. I'll raise a PR tomorrow! 😀

I've raised a PR for this file. I did a bit of testing and it didn't seem to affect the React typings.

I've raised a PR for this file. I did a bit of testing and it didn't seem to affect the React typings.

In the meantime, how we can use swiper in vue 3/typescript project?

@NabilFr use this shim:
declare module 'swiper/vue' {
  import { DefineComponent } from 'vue'

  export const Swiper: DefineComponent<any, any, any>
  export const SwiperSlide: DefineComponent<any, any, any>
}

@david50407 I think you should make a PR with this shim :eyes:

@giuliano-oliveira this shim only provides simple definition of swiper/vue module without details (like props, slots, etc)
IMO, this shim is a workaround, this project still need full type definitions for Vue.

Was this closed because typescript support was added?

The proper (i.e. more maintainable) way to do this would probably be to convert the component to TypeScript.
Having separate, manually written typings is a recipe for disaster in the long run, imo.
I'd be willing to work on the conversion, if the maintainers are okay with it. I'll do some preliminary exploration on my end, based on how the Angular component builds itself, and report back once I have something.

Version: "swiper": "7.3.4"
has declare module 'swiper/vue'  shim? No, but if add, it work.
Still error! Type '{ delay: number; }' is not assignable to type 'undefined'.ts(2322).


DNM: test rdo zuul CI for stable branches

Depends-On: https://review.rdoproject.org/r/17601

check-rdo

check-rdo

check-rdo


MSID: 90096 Version: 1 DOI: 2<IP_ADDRESS>1074

"msas": "Neuroscience"
"msid": "90096"
"preprintDoi": "10.1101/2<IP_ADDRESS>1074"
"Reviewed Preprint posted": "2023-09-18"
"Sent for peer review": "2023-06-27"
"Posted to bioRxiv": "2023-06-12" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1074v2/")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v1/by-publisher/elife/get-by-manuscript-id?manuscript_id=90096)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/90096/v1)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>1074)
[x] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/90096/v1/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/90096)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/90096

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/90096

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/90096/v1/90096-v1.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/90096)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

Publisher names missing from book reference; elocations missing from reference list


test-consensus: add MiniProtocolFatalException

This PR is intended to make it easier to debug test failures due to unexpected exceptions (ie fatal exceptions) from the miniprotocol threads in test-consensus.

Seems fine so long as nothing above this layer is explicitly expecting unwrapped exceptions.

Seems fine so long as nothing above this layer is explicitly expecting unwrapped exceptions.

Yep: this is defining .Network, which is currently (and planned to be) only used in the .BFT, .PBFT, .LeaderSchedule, .Praos, .RealPBFT, etc modules: those that run the protocol testing setup and then check QuickCheck properties. None of those are catching anything right now.
bors r+

bors retry


cache value of accessibilitySupport so status bar entry is correct regardless of event timing

fix #172690
fix #172688

I misunderstood when I read cache because typically the storage service is where we do that. I will try that approach

@bpasero I feel like the approach I took is wrong and it's not working. How am I supposed to get the status here?
https://github.com/microsoft/vscode/blob/39954d2fef55d47a0d44553a0d4c0907e4f1e221/src/main.js#L470

@rzhao271 suggested this should maybe go in onReady instead. thoughts @bpasero ?
https://github.com/microsoft/vscode/blob/39954d2fef55d47a0d44553a0d4c0907e4f1e221/src/main.js#L469

@deepak1556 from your comments, I thought this was more than a UX/status bar item issue. But in my testing, it's just that.


Cannot parse privateKey: Unsupported OpenSSH private key type: ssh-ed25519

Is this a similar or duplicate feature request?

[x] Yes: https://github.com/liximomo/vscode-sftp/issues/45 but It has been closed, but this still doesn't work, but can be fixed easily I think, see below
[ ] No

Is your feature request related to a problem? Please describe.
id_ed25519 keys are not accepted with Cannot parse privateKey: Unsupported OpenSSH private key type: ssh-ed25519 error
Describe the solution you'd like
This issue in ssh2 repo: https://github.com/mscdex/ssh2/issues/352 says that this has been solved:

Full Ed25519 support now available in ssh2 v0.8.3 when used with node v12.0.0.

So I suppose a simple ssh2 update would solve this?
Does this project help you?

[x] Not yet, I only use id_ed25519 keys for ssh at this point. Would be awesome if this would work!
[ ] Yes. SFTP IS AWESOME!

Not until VS Code ship with node v12

Looks like VS Code is using Node.js v12 now :-)


Minimum universal react API

Hi, I've been working on https://github.com/guidsen/react-simple-universal that solved the boilerplate involved with universal React Apps.
I'm really curious about your thoughts about this and would love to have some help evolving this repo.

@guidsen what are your suggestions?


window.$crisp.is is not a function

I am working on a React application, on which I have installed crisp-sdk-web. Sometimes, randomly, I can't open the chat anymore, and I have the following error message in the console, while sometimes, everything works perfectly. The behavior seems random:
I did call Crisp.configure() with the uuid in my App.tsx.
main.fd36622d.js:2 Uncaught TypeError: window.$crisp.is is not a function
    at e.isChatOpened (main.fd36622d.js:2:1515822)
    at onClick (main.fd36622d.js:2:3023326)
    at onClick (main.fd36622d.js:2:3002732)
    at Object.De (main.fd36622d.js:2:2260503)
    at Be (main.fd36622d.js:2:2260657)
    at main.fd36622d.js:2:2280557
    at Mr (main.fd36622d.js:2:2280651)
    at Lr (main.fd36622d.js:2:2281066)
    at main.fd36622d.js:2:2286508
    at uu (main.fd36622d.js:2:2350177)
    at Re (main.fd36622d.js:2:2259635)
    at Vr (main.fd36622d.js:2:2282360)
    at Gt (main.fd36622d.js:2:2266756)
    at qt (main.fd36622d.js:2:2266540)
    at HTMLDivElement.r (main.fd36622d.js:2:2935323)

Can you please provide all your code?

My App.tsx
...
import { Crisp } from 'crisp-sdk-web';
...

Crisp.configure('xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx');

const App = () => {
  return (
    ...
  );
}

export default App;

En suite, j'ai un bouton dans une bottom bar. C'est quand je clique sur ce bouton, que parfois, de manière aléatoire, j'ai le message d'erreur window.$crisp.is is not a function
        <BottomNavigationAction
          showLabel
          icon={<ChatIcon className={classes.icon} />}
          label={'Chat'}
          onClick={() => {
            Crisp.chat.isChatOpened() ? Crisp.chat.close() : Crisp.chat.open();
          }}
          style={{
            minWidth: 60,
            padding: 0
          }}
        />

No i'm not. React only. On the other hand, the issue occurs only when the project is built, but never in dev.

Could it be a linter issue?
Seems you are not using the configure in a lyfecyle hook, so it could be possible the builder tries to evaluate the code, even if it’s not mounted in the dom.
Baptiste Jamin

On 9 Feb 2023, at 10:12, RobinChailley @.***> wrote:
No i'm not. React only. On the other hand, the issue occurs only when the project is built, but never in dev.
—
Reply to this email directly, view it on GitHub https://github.com/crisp-im/crisp-sdk-web/issues/11#issuecomment-1423862686, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGTRQ3ZYPIAKPPRFQ2WOULWWSYJFANCNFSM6AAAAAAUWIV3RU.
You are receiving this because you commented.

I tried to use the configure function in a life cycle hook, but it does not change anything.
However, I found that the error occurred after browsing via a Link, or whatever, from react-router-dom.
If I browse the app using a , I don't get the error.
If I console.log() into my window.$crisp browser console before I've navigated using react-router-dom, then I get this result:
{push: ƒ, get: ƒ, set: ƒ, is: ƒ, on: ƒ, ...}
which seems to be the expected result, and it works, then "is" is indeed a function. On the other hand, if I console log again, but after navigating with react-router-dom, I have this result there :
[Array(2), Array(2), Array(2), Array(2), Array(2), Array(2)]
And so the error "window.$crisp.is is not a function".

I might have the same issue on a Next.js project. Calling methods only on client side.
When I call CrispSdk.chat.isVisible(), it does (very often) trigger following error :
TypeError: window.$crisp.is is not a function
    at e.isVisible

crisp-sdk-web: 1.0.12

@RobinChailley @loiclouvet Have you found a solution?

Hey!
Do you run the latest SDK version?

@baptistejamin 1.0.20, but in my situation Chat is opening on the second try :/

Would it be possible to get more context?
It could be possible you are trying to call Crisp methods way before the window is ready

@baptistejamin
In global component (layout.tsx) I configure Crisp.
`  useEffect(() => {
Crisp.configure(CRISP_WEBSITE_ID, { safeMode: true })
if (window.__layout.initialData.user) {
  Crisp.user.setAvatar(window.__layout.initialData.user.avatar)
  Crisp.user.setNickname(window.__layout.initialData.user.username)
  Crisp.session.setData({
    userKey: window.__layout.initialData.user.userKey,
  })

  Crisp.chat.onChatOpened(() => {
    Crisp.session.setData({
      userKey: window.__layout.initialData.user.userKey,
    })
  })
}

}, [])`
Then I'm checking if Crisp is injected and I'm rendering HelpButton
{Crisp.isCrispInjected() && <HelpButton key="helpButton" />}
HelpButton component has handle click function
  const handleAvailableCrispIconClick = () => {     if (chatOpen && isDesktop) {       Crisp.chat.close()       setChatOpen(false)     } else {       Crisp.chat.open()       setChatOpen(true)     }   }
And renders button
    <button         className="flex h-19 w-19 items-center justify-center rounded-full border border-gold-400 bg-navy-750 shadow-[0_0px_50px_rgba(221,169,73,0.15)] transition-all hover:border-gold-300 hover:shadow-[0_0px_50px_rgba(221,169,73,0.4)]"         onClick={handleAvailableCrispIconClick}       >         {chatOpen && isDesktop ? (           <motion.div             key="close"             initial={{ opacity: 0, rotate: 30, scale: 0.75 }}             animate={{ opacity: 1, rotate: 0, scale: 1 }}             exit={{ opacity: 0, rotate: 30, scale: 0.75 }}             transition={{ duration: 0.3 }}           >             <CloseIcon className="h-8 w-8 text-gold-500" />           </motion.div>         ) : (           <motion.div             key="open"             initial={{ opacity: 0, scale: 0.75 }}             animate={{ opacity: 1, scale: 1 }}             exit={{ opacity: 0, scale: 0.75 }}             transition={{ duration: 0.3 }}           >             <HeadphoneIcon className="h-8 w-8 text-gold-500" />           </motion.div>         )}       </button>

Hi, our agents are offline at the moment. Please leave a message and we will get back to you as soon as possible.

@baptistejamin any update? :)

@SzymonNiemiec @baptistejamin did you figure out what was causing this?

In general such issues are because of server side rendering Sent from my iPhoneOn 9 Apr 2024, at 10:38, Deepit Patil @.***> wrote:
@SzymonNiemiec @baptistejamin did you figure out what was causing this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Request for explanation of how to run the code

Could you please provide a more detailed explanation of how to run the code, especially for the pre-computation part of the paper?
I suppose the pre-computation time in the code is "Time to compute all KZG openings" by running single_opening.rs.
But I did not see any place that can use the precomputed SRS data.

The precomputation part is not callable per se, but for every run we check if we can load the precomputation from file, and if not we generate the openings and then store it.
https://github.com/caulk-crypto/caulk/blob/main/src/multi/mod.rs#L705-L730

Yes, I do see this part for multi-openings. How about for the single opening?

I think we did not implement it for the single.

If I run the single opening with the following operations, am I getting the result in Table 4 in the paper?
What is the bitsize of the degree of the polynomial inside the commitment?
16
Time to setup single openings of table size 65536 = 66.2134808s
Time to KZG commit one element from table size 65536 = 11.3296164s
Which position in the vector should we open at?
1
Should we open all possible positions? Opening all possible positions is slow.  Please input either YES or NO
YES
Time to compute all KZG openings 6590.5532914s

I changed the test machine with better performance and get similar results in the paper! Thanks for the help.


Omnisharp doesn't find System on Dotnet SDK >= 3.0

Issue Description
When I open a Project with OmniSharp and the target Framework is set to 2.1, it works perfectly, but if i go higher than that (>= 3.0), it just says "The type or namespace name 'System' could not be found". It works perfectly when I press F5, or do dotnet run
Steps to Reproduce
Create any .NET Core >= 3.0 project and try to use Omnisharp
Expected Behavior
It should work on any .NET Core version
Actual Behavior
It doesn't and can't find any .NET Core classes
Logs
OmniSharp log
Post the output from Output-->Starting OmniSharp server at 7/19/2020, 8:38:47 PM
    Target: /home/noah/soda-lake-s-share/code/c#/hi
OmniSharp server started with Mono 6.10.0.
Path: /home/noah/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/OmniSharp.exe
PID: 119169
    Starting OmniSharp on arch 0.0 (x64)

    DotNetPath set to dotnet

    Located 2 MSBuild instance(s)
        1: Mono 16.4 - "/usr/lib/mono/msbuild/Current/bin"
        2: StandAlone 16.4 - "/home/noah/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin"

    Registered MSBuild instance: Mono 16.4 - "/usr/lib/mono/msbuild/Current/bin"
        CscToolExe = csc.exe
        CscToolPath = /home/noah/.vscode/extensions/ms-dotnettools.csharp-1.22.1/.omnisharp/1.35.3/omnisharp/.msbuild/Current/Bin/Roslyn

    Detecting Cake files in '/home/noah/soda-lake-s-share/code/c#/hi'.

    Could not find any Cake files

    No solution files found in '/home/noah/soda-lake-s-share/code/c#/hi'

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Detecting CSX files in '/home/noah/soda-lake-s-share/code/c#/hi'.

    Could not find any CSX files

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110

    Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140

    Loading project: /home/noah/soda-lake-s-share/code/c#/hi/hi.csproj

    Configuration finished.

    Omnisharp server running using Stdio at location '/home/noah/soda-lake-s-share/code/c#/hi' on host 119063.

    Successfully loaded project file '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'.

    Adding project '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Update project: hi

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Loading project: /home/noah/soda-lake-s-share/code/c#/hi/hi.csproj

    Successfully loaded project file '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'.

    Update project: hi

    hi: Did not find 'Microsoft.NETCore.App' in lock file.

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Loading project: /home/noah/soda-lake-s-share/code/c#/hi/hi.csproj

    Successfully loaded project file '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'.

    Update project: hi

    Queue project update for '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'

    Loading project: /home/noah/soda-lake-s-share/code/c#/hi/hi.csproj

    Successfully loaded project file '/home/noah/soda-lake-s-share/code/c#/hi/hi.csproj'.

    Update project: hi

    Queue analysis for all projects.</details>

C# log
Post the output from Output-->-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded '/home/noah/soda-lake-s-share/code/c#/hi/bin/Debug/netcoreapp3.1/hi.dll'. Symbols loaded.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Console.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Threading.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Loaded '/usr/share/dotnet/shared/Microsoft.NETCore.App/3.1.3/System.Runtime.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.

Environment information
VSCode version: 1.47.2
C# Extension: 1.22.1
Mono Information
        OmniSharp using global mono :6.10.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.103
 Commit:    6f74c4a1dd
Runtime Environment:
OS Name:     arch
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /usr/share/dotnet/sdk/3.1.103/
Host (useful for support):
Version: 3.1.3
Commit:  ed88943d24
.NET Core SDKs installed:
2.1.808 [/usr/share/dotnet/sdk]
3.1.103 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.NETCore.App 2.1.20 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-dotnettools
1.22.1

looks like you have an outdated installation of global Mono. please update to at least 6.4 (ideally 6.10)

looks like you have an outdated installation of global Mono. please update to at least 6.4 (ideally 6.10)

I already have Mono 6.10

OmniSharp using global mono :6.10.0

yes but it must be missing the necessary msbuild (16.3+)

~ $ pacman -Q | grep msbuild mono-msbuild 16.6.xamarinxplat.2<IP_ADDRESS>.43-1

I am not very familiar with Arch but we have only partial support for ot though see https://github.com/OmniSharp/omnisharp-roslyn#introduction
what your log shows is that the global mono you have doesn't have correct new msbuild bundled, hence the problem
what you need is the equivalent of mono-devel for Ubuntu

I believe that Arch has a msbuild-stable package that is known to work.

ah thanks @JoeRobich I couldn't find that.
I updated the instructions here https://github.com/OmniSharp/omnisharp-roslyn/pull/1859

I replaced mono-msbuild with mono-stable, and it hasn't changed anythin g

I can confirm that I'm experiencing this too. msbuild-stable sadly doesn't seem to resolve anything.
This issue also persists on the flatpak version

I have this issue on macOS. Using stable mono 6.10, tried 6.12 too, but no go. I can only get OmniSharp 1.23.4 to provide partial IntelliSense for dotnet core projects. It can't handle any references to System.Threading.* using the global mono but it does work if I change to "omnisharp.useGlobalMono": "never".
I'd leave it at that but I can't use the never setting as it is only allowed in user and not workspace. I also use Unity and that requires real mono, the internal Omnisharp version will not function.
Basically, in order to keep working, I can only have one project open at a time and I have to swap the omnisharp.useGlobalMono setting to and from always and never before changing projects.  I wish I understood the real issue so I could address it.

the problem is the incompatibility between the lowest MSBuild version required by the new .NET Core SDKs (16.7+) and the version available in any publicly available Mono (16.6)
the bundled Mono of Omnisharp is something we build ourselves so it has 16.8 and hence it works with latest.NET Core including  .NET 5.0
you can find more info here https://github.com/OmniSharp/omnisharp-vscode/issues/4007#issuecomment-677405332 and here https://github.com/mono/mono/issues/20250

Thanks so much @filipw! I was able to configure an environment that works for Unity and DotNet Core at the same time with your information.
Here is what I had to do to work in VSCode in both Unity and DotNet core without changing the Omnisharp.useGlobalMono setting several times a day. The following setup also allows me to have Unity and DotNet Core projects open at the same time.

Downgrade all dotnet core projects to 3.0 (minor pain)
Set "Omnisharp.useGlobalMono": "always" in my VSCode user settings (can't use workspace)
Downgrade OmniSharp to version 1.22.0, later versions work in DotNet but not in Unity, I get tons of errors for dlls that can't be found


remove the return at the end of the testing function

I removed the return at the end of the testing function, test_sampler_stretch(), in the test_stretch.py file. Now this function should be compatible with pytest format.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.42%. Comparing base (4634c53) to head (56314ef).
Report is 8 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
+ Coverage   95.61%   96.42%   +0.81%
==========================================
  Files           2        2
  Lines         114      140      +26
==========================================
+ Hits          109      135      +26
  Misses          5        5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


If can't decode audio stream from video file , raise tuple index error

I met this error a few times, later as I checked , the reason is can't decode audio stream from video https://github.com/guillaumekln/faster-whisper/blob/1562b02345c8587eff1c6694b28c7f91f5c20ec2/faster_whisper/audio.py#L18C5-L18C17 , maybe due to some format issue , some videos can be opened for playback, but can't decode audio.
for these kinds of errors , is it better to raise some exception
so we can catch it and display some message for end user.

Can you post the actual error and traceback you are getting? If you can also share the video file that produces the error that would be helpful.

: tuple index out of range
Traceback (most recent call last):
segments, info = model.transcribe(
File "D:\scoop\apps\miniconda3\current\envs\v2sub-fastwhisper-dev\lib\site-packages\faster_whisper\transcribe.py", line 239, in transcribe
audio = decode_audio(audio, sampling_rate=sampling_rate)
File "D:\scoop\apps\miniconda3\current\envs\v2sub-fastwhisper-dev\lib\site-packages\faster_whisper\audio.py", line 51, in decode_audio
for frame in frames:
File "D:\scoop\apps\miniconda3\current\envs\v2sub-fastwhisper-dev\lib\site-packages\faster_whisper\audio.py", line 97, in _resample_frames
for frame in itertools.chain(frames, [None]):
File "D:\scoop\apps\miniconda3\current\envs\v2sub-fastwhisper-dev\lib\site-packages\faster_whisper\audio.py", line 84, in _group_frames
for frame in frames:
File "D:\scoop\apps\miniconda3\current\envs\v2sub-fastwhisper-dev\lib\site-packages\faster_whisper\audio.py", line 74, in _ignore_invalid_frames
yield next(iterator)
File "av\container\input.pyx", line 202, in decode
File "av\container\input.pyx", line 134, in demux
File "av\container\streams.pyx", line 117, in av.container.streams.StreamContainer.get
/
IndexError: tuple index out of range
https://github.com/guillaumekln/faster-whisper/assets/2059858/a876e7c4-ca52-4d00-8487-d5d0c7723fd9

It looks like the file has no audio stream. Here the error raised by the FFmpeg CLI:
$ ffmpeg -i out.mp4 -ar 16000 -ac 1 -c:a pcm_s16le output.wav
[...]
Output file #0 does not contain any stream


keras.applications does not include a ResNet18 model

In the example in the ReadMe, ResNet18 is used. However, while this model is available in torchvision, it is not available in keras. Thus, the example should rather use ResNet50 which is available in available in keras, torchvision, and paddle.

@guenthermi ah good catch, can you raise a PR and fix it?


Services fields do not match accepted variables

The following are not being accepted as configuration variables for local_calendar.create_event service call: start_date_time, end_date_time, start_date, end_date...  Service call still requires dtend and dtstart.

Thanks yes the services.yaml file looks wrong as it was copied from Google calendar and not following the new format.


Boilerplate update and update for BB 1.3.2

Solved the compilation issues by simply updating babel boiler plate to the latest. Instead of using webpack (as in normal boilerplate) we are using rollup (upgraded from esperanto) for a cleaner build. Required quite a bit of changes to the gulp file for building. Testing is directly ported from boilerplate with the exception of exposing _ and Backbone globals in test environment
/cc @jmeas you may be interested in the gulpfile changes (using rollup instead of webpack for build ping https://github.com/babel/generator-babel-boilerplate/issues/319)
fixes #245
ping https://github.com/marionettejs/backbone.marionette/issues/2930

:+1:

@megawac this seems to be just building the first 1 and not cycling through the matrix

@jmeas you may be interested in the gulpfile changes (using rollup instead of webpack for build

Very cool. Thanks for doing all that work!


Uncaught TypeError: PIXI.particles.Emitter is not a constructor

Hey,
I've installed pixi-particles via NPM.
I imported it to my project like that:
import * as PIXIParticles from 'pixi-particles';
Then I created my emitter like that:
let emitter = new PIXI.particles.Emitter(...)
However I get an error console: "Uncaught TypeError: PIXI.particles.Emitter is not a constructor"
It's like I can't use the lib and I don't know why ? I'm a bit new with NPM things and I struggle with this problem.
I'm using pixi.js 4.8.7
Thanks in advance for your help

If you are requiring/importing then you should be using new PIXIParticles.Emitter(). (I should add a note to the readme).


Resolved lib file bundling

Fixes issue #14

@tr1ckydev, you have closed my PR without as much as a thank-you, explanation or discussion. Then you implement my fix, ignore package.json and do not included me as a contributor? This is very rude of you.

@citkane Hey, I am extremely sorry for the behavior. I don't remember clearly, why I might have closed it. I'm still getting a hang of collaborating on open source projects. I added you as contributor in latest commit.

This PR code comparison will clean up once the Prettier houskeeping PR is merged. The relevant change is at line 22 of ffi.ts.


Update the link to "Underscore Template library"

The link to the "Underscore Template library" at: https://github.com/softlayer/ember-cli-jsdoc/blob/0597aa2ac046d25cd8a5cf35e7747266ce28ea35/jsdocTemplates/default/README.md needs to be updated.

It is also broken on https://github.com/jsdoc3/jsdoc/tree/master/templates/default, which is where this content came/comes from


Support kubeletConfiguration.failOnSwap and kubeletConfiguration.memorySwap in Provisioner spec

Description
What problem are you trying to solve? Set failOnSwap=false and memorySwap=... on kubelet configuration.
How important is this feature to you? It's necessary for us to be able to use swap memory on Karpenter-controlled nodes.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Yes, that's exactly what I'm asking to configure.
I'm currently using Karpenter v0.27, does it mean I have to upgrade to v0.32 to be able to use the the v1beta1 APIs?

/remove-lifecycle rotten

Going to close this one in favor of https://github.com/aws/karpenter-provider-aws/issues/5833. I think Cloud Providers will be opening specific issues for adding support for additional kubelet config fields since there is a plan to shift the location of this stanza at v1 (see https://github.com/kubernetes-sigs/karpenter/issues/758#issuecomment-1971592904)


Rename device

As a user I would like to be able to rename a device.

This is nice to have but not very important.


fix: 404 page support static translation

Notion ticket link

Fix 404 page, some wrapper components not translated

Implementation description

Use static props function to support translations as shown here

Steps to test

go to any 404 page with locale set. test with all locales. we should no longer see things like "nav.signInNow" but rather the actual text.

Checklist

[X] My PR name is descriptive and in imperative tense
[X] I have run the linter
[X] I have requested a review from the PL, and/or other devs who have background knowledge on this PR or who will be building on top of this PR

LGTM. How come ja/common.json and ja/form.json are included but empty?

SDC does not have JP translators so those files will remain empty for now. i18n is smart enough to fallback to english


Was stuck on "Preparing Windows"

Microsoft PowerToys version
v0.66.0
Installation method
GitHub
Running as admin
No
Area(s) with issue?
General
Steps to reproduce
Had no problem with this superb suite.
The problem was that my Win 10 Pro was stuck at every boot to "Preparing Windows".
I tried so ,many ways to restore any old image to no avail, it seems that in that mode you cant ask for this for a privilege reason or what not.
I figured I will remove installed 'everything'; updates or what not to get the system back.
So, that is why I tried, without success, to remove 'Power Toys'. It was a deluge of errors when I restarted Windows.
It did not solve my problem. And since then reboots with your popup to inform you of this.
What saved my machine was the program RegHunter from EnigmaSoft which from which I done multiple images, one image from late December 2022, the first I tried from my saved images did the trick, perfect restoration.
I include the file you want:
2023-01-22.txt
✔ Expected Behavior
Trying to remove everything that I recently installed to solve the "Preparing Windows' problem
❌ Actual Behavior
Only a very scary moment full of removal messages
Other Software
No response

Not able to repro this, going to close. Let us know if you see this again!


Bridge.Collections 1.3.3 not compatible with Bridge 15.7

The current nuget package available for Bridge.Collections (1.3.3) was compiled using Bridge 15.3. As a result, the JS file embedded in the Bridge.Collections assembly is not compatible with the recent changes to array creation in 15.7. A new nuget package that contains assemblies built with Bridge 15.7 is needed to be able to use Bridge.Collections with the latest version of Bridge.

Thanks for bringing this to our attention. We will update all the Bridge Framework projects and release new NuGet packages. Should be complete within 24 hours (or less).

Excellent. Thank you for the quick response.

Hi @ddaspit – Can you make a Deck sample that demonstrates a failing scenario?
I've been running tests locally, but I just want to double check your case is working before closing this issue.

Here is a simple example.

Should be working now.
Bridge.Collections 1.3.4 has been released to NuGet.
Hope this helps.


Deduplicate temp targz creation in ztoc/testutils.go.

Combined duplicate temp targz generation funcs + helpers within ztoc/testutils.go. into util/tar.go . Util/tar.go has 2 functions (BuildTar + BuildTarGz), which both return tar(gz) io.Reader. Since some integration tests require targz file paths to be returned a WriteTarGz function has been added to create a targz file from an io.Reader.
Signed-off-by: Yasin Turan<EMAIL_ADDRESS>Issue #, if available:
Fixes: #355
Description of changes:
Testing performed:
make test && make integration
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Most of the integration test failures appear to be from #382, and the TestSociCreateSparseIndex failure looks like a transient network mishap.


MatthewsCorrelationCoefficient

This is still in progress about (https://github.com/tensorflow/addons/issues/457). I'm trying to use colab to compare&test to make sure the correctness.

Hi @Squadrick, may I have your suggestions about the revision?

Hi @Squadrick, can you please help review?

Hi @WindQAQ, can you help review this?

Hi @WindQAQ, I think this metric may be okay to review, can you help review this?


HierarchyId support

Migrated @zgabi 's fork on codeplex (many thanks) which (I think) is the source of the NuGet Package EntityFrameworkWithHierarchyId to GitHub and reverted changes related to changing the public assembly key and NuGet package Id.
As stated in feature request #339, community contributions for features that the EF team is not planning to implement themselves can still be considered as most of it would be already done.
( I am not the original author, I am only trying to add this contribution to the EF code base so it has the possibility to support the data type without any hacks/workarounds. It would be a shame if it is lost when CodePlex goes down. )

@rbeurskens,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@rbeurskens, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, .NET Foundation Pull Request Bot

@rbeurskens I've updated my fork. Now it is on github, too. Could you please recreate from this fork?
https://github.com/zgabi/EntityFramework6/commits/master
Not only merged the latest upstream code. HierarchyID changes are based on spatial (geography, geomerty) codes, which was already supproted by EF. It was changed in the last years, and now I updated the same changes in the HierarchyID classes. For example "annotations" parameter was added to the ColumnBuilder, and some code comment style was also changed, so I make it similar:)
I separated the changes to 2 commits, you need to make a PR from this state:
https://github.com/zgabi/EntityFramework6/tree/f86943e1e3b2cfc0b3e7fb8ba4334bff95f0567b
The next commit is the "Package rename and assembly signing changes", it it not needed.

@zgabi I pulled your fork and rebased this PR branch on it ( replacing the original commits with the one you linked )

What else needs to happen before this can be merged? I still need to do anything?

@rbeurskens Sorry this has taken a long time to get to. The team is currently focused on the EF Core 2.1 release. As that work wraps up we have some EF Designer work to do, and as soon as that is complete we will start working on the next EF6 release, including reviewing community pull requests.

Thanks for your response. I understand. I Just wanted to make sure I didn't forget something.

Good day, how goes the development of this feature? Is there anything I can do to help speed along the process?

@millsy013 --Development-- has been completed by @zgabi .
It is now a matter of review and approval by the EF team so it can be included in the next EF6.x release, however they have other priorities right now. (as explained by @ajcvickers) I don't think we as community can do anything in this process as it can be seen as a final quality check by Microsoft.
I don't have a clue for an ETA for the next (official) EF6.x version on NuGet, but the good news is: there will be one and the project is still maintained. All we can do for now is wait, I guess.

@ajcvickers I see there is a lot of activity on issues for the next release going on. Could you please re-open the issue #339 related to this PR so we can get in indication if/when this is considered to be reviewed/included in a release? (currently it is just closed without a milestone or any status flag)
Thanks.

This has now been merged. Thank you for your patience!

Thank you. Apologies for pushing it a bit.

Thank you.


Show menu in target app?

Is it possible to show menu interactively whilst I'm searching for it?

Affinity recently removed the help search menu in their 2.5 apps
Finbar is a decent workaround

But could it show me where the menu item is?
Perhaps by AppleScripting the opening of the menus in the target app?
Perhaps as an option+enter when choose a menu? So then I can see it, learn, and action it myself.

Hi Matt!

I did consider adding an option to “reveal” a menu item in the hierarchy, but I found out it requires a significant amount of work. Unless requested by additional customers, I’ll have to put in the backlog for now. However, I’m working on a similar feature, intrinsic to Finbar, that might satisfy you in this sense.
Why do you consider Finbar merely a “decent” workaround? I want your experience to be excellent. I’d love to hear what could be improved (other than the aforementioned request).

P. S. — Affinity removing the help menu has to be in some way or another a violation of the HIG. I’d contact them if I was a user of their products.
Roey

What I meant by "decent" (bad choice of word) is that Finbar is a workaround to an issue that shouldn't really exist. App developers as high profile as Affinity shouldn't be removing the help search menu just because their help files so bad they are crashing.
Also, I generally use Cmd+Shift+/ (aka Cmd+?) in all apps, so Finbar hasn't been very sticky for me.
And I've experimented with an Alfred workflow https://alfred.app/workflows/benziahamed/menu-bar-search/

I see, thanks for clarifying. I’m saddened by the fact Finbar isn’t enticing enough for you to ditch Cmd+?, but hopefully what I’m working would change that, so stay tuned. I’ll leave this issue open until I implement what’s needed, and I’d love to hear your feedback then.

Looking forward to it!


Relicense under dual MIT/Apache-2.0

This issue was automatically generated. Feel free to close without ceremony if
you do not agree with re-licensing or if it is not possible for other reasons.
Respond to @cmr with any questions or concerns, or pop over to
#rust-offtopic on IRC to discuss.
You're receiving this because someone (perhaps the project maintainer)
published a crates.io package with the license as "MIT" xor "Apache-2.0" and
the repository field pointing here.
TL;DR the Rust ecosystem is largely Apache-2.0. Being available under that
license is good for interoperation. The MIT license as an add-on can be nice
for GPLv2 projects to use your code.
Why?
The MIT license requires reproducing countless copies of the same copyright
header with different names in the copyright field, for every MIT library in
use. The Apache license does not have this drawback. However, this is not the
primary motivation for me creating these issues. The Apache license also has
protections from patent trolls and an explicit contribution licensing clause.
However, the Apache license is incompatible with GPLv2. This is why Rust is
dual-licensed as MIT/Apache (the "primary" license being Apache, MIT only for
GPLv2 compat), and doing so would be wise for this project. This also makes
this crate suitable for inclusion and unrestricted sharing in the Rust
standard distribution and other projects using dual MIT/Apache, such as my
personal ulterior motive, the Robigalia project.
Some ask, "Does this really apply to binary redistributions? Does MIT really
require reproducing the whole thing?" I'm not a lawyer, and I can't give legal
advice, but some Google Android apps include open source attributions using
this interpretation. Others also agree with
it.
But, again, the copyright notice redistribution is not the primary motivation
for the dual-licensing. It's stronger protections to licensees and better
interoperation with the wider Rust ecosystem.
How?
To do this, get explicit approval from each contributor of copyrightable work
(as not all contributions qualify for copyright, due to not being a "creative
work", e.g. a typo fix) and then add the following to your README:
## License

Licensed under either of

 * Apache License, Version 2.0, ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0)
 * MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT)

at your option.

### Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any
additional terms or conditions.

and in your license headers, if you have them, use the following boilerplate
(based on that used in Rust):
// Copyright 2016 gtk Developers
//
// Licensed under the Apache License, Version 2.0, <LICENSE-APACHE or
// http://apache.org/licenses/LICENSE-2.0> or the MIT license <LICENSE-MIT or
// http://opensource.org/licenses/MIT>, at your option. This file may not be
// copied, modified, or distributed except according to those terms.

It's commonly asked whether license headers are required. I'm not comfortable
making an official recommendation either way, but the Apache license
recommends it in their appendix on how to use the license.
Be sure to add the relevant LICENSE-{MIT,APACHE} files. You can copy these
from the Rust repo for a plain-text
version.
And don't forget to update the license metadata in your Cargo.toml to:
license = "MIT OR Apache-2.0"

I'll be going through projects which agree to be relicensed and have approval
by the necessary contributors and doing this changes, so feel free to leave
the heavy lifting to me!
Contributor checkoff
To agree to relicensing, comment with :
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

Or, if you're a contributor, you can check the box in this repo next to your
name. My scripts will pick this exact phrase up and check your checkbox, but
I'll come through and manually review this issue later as well.

[ ] @Blei
[ ] @Esption
[x] @GuillaumeGomez
[ ] @LordSentox
[ ] @PhnxRbrn
[ ] @SimonSapin
[ ] @StephanvanSchaik
[ ] @TobiasBales
[ ] @adamcrume
[x] @bpbp-boop
[ ] @briankropf
[ ] @buster
[x] @cjgreenaway
[ ] @dndanik
[x] @frewsxcv
[ ] @gekola
[ ] @gkoz
[ ] @glennw
[ ] @gsingh93
[x] @honorabrutroll
[ ] @insanebits
[ ] @jeremyletang
[x] @jgillich
[ ] @jmvrbanac
[ ] @kennytm
[x] @lidavidm
[ ] @ltratt
[ ] @lucaswerkmeister
[ ] @mathijshenquet
[ ] @mitaa
[ ] @mjkoo
[x] @oakes
[ ] @oli-obk
[ ] @osa1
[ ] @pd40
[x] @pshendry
[x] @ptersilie
[x] @rnestler
[ ] @simias
[x] @steveklabnik
[ ] @umurgdk
[x] @zploskey

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
(Just to be clear: this only applies to my contributions to this repository. Let’s hope this disclaimer doesn’t confuse the bot…)

@lucaswerkmeister yeah, the bot doesn't get confused across repositories.

No, I was just wondering if the entire comment has to be just that phrase and nothing else, or if I’m allowed to add stuff.

Oh, yeah, it looks for that sentence as a sub-string, adding stuff is fine.

Cool, thanks!

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

|I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to chose either at their option.|
On 2016-01-10 02:39 PM, cmr wrote:

|I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to chose either at their option.|

--
Paul

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

FWIW I find the lack of notice, use of a bot and forcing our hand like this rude.

I'm a bit confused by that comment.

What would notice be given about? That I was going to do this? Why?
I'm handling ~1800 repositories. Without a bot this is impossible, and I do think it's important.
Why is this forcing your hand? Feel free to close the issue without ceremony, as stated in the first sentence.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I know you've closed the issue, but I'd rather you had my approval anyway:
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
This only applies to my contributions to this repository.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
This only applies to my contributions to this repository.

I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.


'Critical dependencies' error

I use webpack for bundling my project. Table works fine but I get the following warnings/errors in the console http://prntscr.com/bpa9xj
Looks familiar to https://github.com/webpack/webpack/issues/196

Interesting, I don't use webpack myself but I will definitely look into this. I suspect its something to do with the SystemJS registry.

Please retry, I'm using webpack now and not having issues :)


⚠ ClamAV has degraded performance

In 718f705, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in 1d34c8d.


Link to system libraries and headers on Linux (Debian)

Summary
This PR adds a new make flag: SYS_LIBS=true, which allows the Math library to link against system-installed libraries, rather than building them locally.
At the moment this is only tested on Debian/Ubuntu, since I'm working on packaging cmdstan into .deb files for distribution. Once that packaging process is stable I'll add and test the functionality for the other distros.
This is tested working against the following packages and versions:

libboost-math-dev (>=1.74)
libeigen3-dev (>=3.3.9)
libtbb-dev (>=2020.3)
libsundials-dev (>= 4.1)
opencl-headers (>= 3.0~2020)

This approach is (currently) not compatible with MPI, since the Boost binaries in Ubuntu/Debian aren't built with MPI.
Tests
Currently N/A, but could be good to add. But I'm not sure how that would interact with the current workflow.
Side Effects
N/A
Release notes
Added functionality to link against system libraries on Debian-based Linux distributions
Checklist

[x] Math issue #2518

[x] Copyright holder: Andrew Johnson
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

@andrjohns TBB_LIB and TBB_INC environment variables allow linking to system (or, optionally, any external) TBB library (#2257). So, either respect them regardless of SYS_LIBS or deprecate them.

Good point. I might change the current approach to optionally allow setting the include and library paths (like TBB_LIB and TBB_INC) for all libraries, otherwise it defaults to the system installed ones (/usr/include and /usr/lib).
I need to make some larger changes as well, so I'll close this PR for now so it doesn't clog up the list

Good point. I might change the current approach to optionally allow setting the include and library paths (like TBB_LIB and TBB_INC) for all libraries, otherwise it defaults to the system installed ones (/usr/include and /usr/lib).

Sounds good. I assume that it will default to building from the internal sources if SYS_LIBS is undefined. If SYS_LIBS=true and the paths aren't defined, I wouldn't default to /usr/lib, just add -l<library> to LDLFAGS (without path, assuming that the library directory is already in LD_LIBRARY_PATH) since some x68_64 systems (e.g., Ubuntu) has different directory structure -- especially if using rpath to designate the run-time search path.


--https mode causes issues in dev by trying to connect to wss://localhost:24678

Describe the bug
In --https mode, the site is served at https://localhost:3000 and so the Vite websocket connection that is attempted fails, because it tries to make it at wss://localhost:24678 when it exists at ws://localhost:24678. This results in the page being periodically reloaded.
Logs
Firefox can’t establish a connection to the server at wss://localhost:24678/.
[vite] server connection lost. polling for restart... client:340:13
[vite] connecting...

To Reproduce
npx svelte-kit dev --https
Open console and/or network logs and wait. Turn on timestamps on the console to help see what's happening. The page refresh rate seems to vary widely, and I haven't figured out what causes that to happen.
Expected behavior
I don't think we can force an HTTPS page to load a non-secured websocket, so we'll have to figure out how to serve a secure websocket over that port. This will also still probably cause issues because it will be a self-signed cert. I don't know how to resolve this.
Severity
High. HTTPS mode is not very usable if the browser refreshes periodically.
Additional context
I told you HTTPS mode was a mistake and you didn't believe me.

I just got this, using npm run dev -- -H on SvelteKit v1.0.0-next.70. On Chrome it refreshes about every 4 secs, no logs apart from [vite] connecting...; in Firefox it refreshes about every sec and I got this log just once:

Details

...then for some unknown reason it seems to start working (no refreshes).

I told you HTTPS mode was a mistake and you didn't believe me.

Well, in my case I'm testing the Web Bluetooth API in Chrome which requires HTTPS so I'm glad for the -H option! :)

This is just part of a larger issue with not being able to reach the hmr (?) server on that port. Rich had suggested trying to disable it when in https mode, but really it would be better if the port were configurable, if you could disable there feature separately from enabling https mode, and if its existence was documented for people who are e.g. running Kit inside Docker. Also ideally the whole page wouldn't reload when the server can't be reached.

Vite lets this websocket server be configured with https://vitejs.dev/config/#server-hmr so we should be able to disable it and have a command line argument to control it.

I've attempted to add an hmr: false to the server object at https://github.com/sveltejs/kit/blob/ccb8825fd97d7f23ee961b30077e1a2bf1a53b42/packages/kit/src/core/dev/index.js#L103-L106 and the browser is still trying to connect to wss://localhost:24678/ so I'm not sure what's up with that or where else I might need to change something.

This problem has stopped me dead in my tracks. I'm working on a new project w/ oauth and I need an https callback to receive my login token. I hope this gets addressed soon but I'm open to workarounds in the meantime. Thank you.

In case it helps, in plain Vite + Svelte projects, simply setting the server works (with HMR). e.g., https://github.com/small-tech/site-vite-svelte/blob/main/vite.config.js#L17
I just tried the same thing with SvelteKit and the vite server setting is being ignored. (e.g., with the following config, the server is still being started on http://localhost:3000).
const os = require('os')
const fs = require('fs')
const path = require('path')
const static = require('@sveltejs/adapter-static');
const pkg = require('./package.json');

// Note: the local TLS certificates will have been created at
// the post-install stage of npm install.
const certDirectory = path.join(os.homedir(), '.small-tech.org', 'auto-encrypt-localhost')
const cert = fs.readFileSync(path.join(certDirectory, 'localhost.pem'))
const key = fs.readFileSync(path.join(certDirectory, 'localhost-key.pem'))

/** @type {import('@sveltejs/kit').Config} */
module.exports = {
  kit: {
    // By default, `npm run build` will create a standard static app.
    // You can create optimized builds for different platforms by
    // specifying a different adapter
    adapter: static({pages: '.generated', assets: '.generated'}),

    // hydrate the <div id="svelte"> element in src/app.html
    target: '#svelte',

    files: {
      assets: '.kit/static',
      lib: '.kit/src/lib',
      routes: '.kit/src/routes',
      template: '.kit/src/app.html'
    },

    vite: {
      ssr: {
        noExternal: Object.keys(pkg.dependencies || {})
      },
      server: {
        port: 444,
        https: {key, cert}
      }
    }
  }
}

Opening port 24678 on the server and forwarding it in VSCode resolved the issue for me and enabled auto-reload. I use it with remote development with VSCode in Docker containers.
You want to see something like this in the Chrome console:
client.ts:43 [vite] connecting...
client.ts:43 [vite] connected.

This error in the console says there is something wrong with the Vite connection:
WebSocket connection to 'ws://localhost:24678/' failed:

Some background information
SvelteKit uses Vite for its hot module reload (HMR) feature. This uses a WebSocket that uses a different port than the one opened with Sveltekit (default 24678, but it is configurable, but the configuration seems to not apply with SvelteKit). When you fire up SvelteKit using npm run dev it starts the server and creates a Vite WebSocket that listens to connections.
Related topics

An Devilbox issue has a similar discussion
There seems to be still some Websocket issues when using HTTPS and Vite that are actively resolved.

https://github.com/sveltejs/kit/issues/581#issuecomment-805398830 hinted at a way that seems to work for me:

Adding the following to svelte.config.cjs fixed the issue for me (so it uses ws instead of wss and port 3001)

	kit: {
		vite: {
			server: {
				hmr: {
					protocol: 'ws',
					port: 3001
				}
			}
		}
}

Overriding the port doesn't appear to be necessary. Overriding the protocol only seems to be possible when accessing the site via https://localhost:.... I think there are special rules about localhost being considered a trusted origin, even unencrypted, so the browser lets an HTTPS site access an unencrypted websocket on localhost. If I navigate to https://<IP_ADDRESS>:..., I get the endless reloading, I believe because the browser refuses to connect to the unencrypted websocket on <IP_ADDRESS>.

Is there any reason to have a secure socket for HMR while testing?  This socket is only used to notify the client to reload modules, to display an error overlay panel, etc.  I believe that the web socket protocol can/should always be 'ws'.
If no protocol ('ws' or 'wss') is specified in vite.server.hmr.protocol, Vite will set the protocol according to its dev server protocol:  'http' --> 'ws', or 'https' --> 'wss'.
The current workaround is set the protocol manually in svelte.config.js, as described by @mankins:
kit: {
	vite: {
		server: {
			hmr: {
				protocol: 'ws',
			}
		}
	}
}

Would it be acceptable for SvelteKit to ensure that the protocol is always set to 'ws'?
I ran a little test with this change, which doesn't interfere with other HMR configurable settings, such as setting the port.  It worked for me:
//  kit/src/core/dev/index.js  -- around line 105
			server: {
				...user_config.server,
				middlewareMode: true,
				hmr: { ...user_config.server?.hmr, protocol: 'ws' }
			},

Please advise if I'm stepping on anyone's toes or being redundant.

That's better than nothing, but as I noted above, if you run afoul of the browser's mixed content rules, it will still cause infinite reloading.

I believe I have a solution, while learning a lot about https and web sockets along the way.
In Vite's web socket implementation (vite/src/node/server/ws.ts), there is an undocumented option to receive the server reference that's created by the invoking application (in this case, SvelteKit).  If a server is specified, it will attach the upgrade, connection and error handlers.
The challenge is to pass the reference of SvelteKit's server into Vite.  The server reference needs to be passed in the config -- but the current code creates the config before the server is started.  (i.e., 'vite.createServer' is called before 'get_server' in kit/src/core/dev/index.js)
I don't think that switching the order makes a difference -- at least it didn't in my testing.  After making the switch, I also changed the following code:
// kit/src/core/dev/index.js
			server: {
				...user_config.server,
				middlewareMode: true,
				hmr: {
					...user_config.server?.hmr, server: this.https ? this.server : undefined
				}
			},

I also needed to change svelte.config.js to change the HMR port to 3000:
				hmr: {
					port: 3000
				},

and, I ran using svelte-kit dev -H --host <my-dev-server's-ip-address>
The two big questions are:

Will the Vite team give its blessing that 'server.hmr.server' is available for general use
Would switching the order of calling vite.createServer and get_server have any side-effects

I was able to access the server using my Android phone and a spare laptop.

If interested, I have a proposal (with source changes and a README.md to explain them) to solve the issue, without reordering the 'mainline' dev process as described in my previous comment:  Proposal
Let me know if I can help in any way.

@Conduitry @JBusillo Might it just be a better use of time to settle with the workaround (running at localhost instead of <IP_ADDRESS>), since the --https option is almost always used to test in localhost?

PR #1517 addresses the web socket connection issues that allows using 'localhost', '<IP_ADDRESS>', or an exposed network IP address (using the --host option).  There are users who want to test using external devices (smartphones, tablets) using SSL while running the dev server on their desktop/laptop.  The workaround does not address these use cases.
The PR already has been coded and tested, and is now pending review, approval and deployment by the maintainers.  I don't see much additional time spent on this issue/PR.  However, I defer any further decisions to the maintainers.

@JBusillo Ok, I didn't notice your PR! Great work, and I do agree with you, for instance with this PR i will be able to test Web Authentication API on my iOS phone, which I couldn't do before. Thanks a lot, hope the PR gets merged ASAP :)

I think I have a related issue -- I'm using SSL but of course not within SvelteKit itself, that seems crazy. SSL in front of it. So I spin up the dev server on 3000, put stunnel in front on 3001 or something, but now the call for insecure ws websocket of 24678 fails due to mixed security. I'm just looking for a way to make it serve the websocket on the different port than the client is looking for it on, so I can connect it together with stunnel or something similar.

I do have a jury rigged setup that works based on having two machines. I develop and run on my workstation and view in a web browser on my laptop, so I can ssh -L tunnel from my laptop 24678 to my workstation 24679, then stunnel on my workstation from 24679 to 24678. A zig and a zag. But I'd like to be able to do this on one machine.

Here's a workaround that may work: PR 1517
It's messy, but hopefully a better solution will be implemented.

For my case, if they accept my PR in Vite is resolves. https://github.com/vitejs/vite/pull/3578

This is fixed in<EMAIL_ADDRESS>- Thanks @JBusillo!

I was having this issue due to using an Nginx reverse proxy with a HTTPS upgrade using a custom port (SvelteKit was using its default port 3000). Is there an easy way to have the client initiate a websocket connection using the same port as the browser @JBusillo?
For anyone in a similar situation to me, for now make sure the SvelteKit port matches the forwarded port. And note that at least for now, Apple doesn't support TLS 1.3 with websockets, so you need to make sure there's TLS 1.2 support.


Correct installation command in README

Signed-off-by: laurentsimon<EMAIL_ADDRESS>closes https://github.com/slsa-framework/slsa-verifier/issues/237

Oops! Thank you! That was in an outstanding PR


Capture os signal for exiting in CLI and do proper cleanup

Currently, if you ctrl + c to exit the CLI, it will leave the terminal in a messed up state as we didn't properly shut down liner.  We can easily capture this and shut down gracefully.

The same again. rigjht now with versio <IP_ADDRESS> under CentOS 6.7 64bit :

SHOW DIAGNOSTICS;
name: build

Branch  Build Time                      Commit                                          Version
0.9.6   2015-12-10T23:40:23+0000        6d3a8603cfdaf1a141779ed88b093dcc5c528e5e        <IP_ADDRESS>

This seems to work. It looks like it was fixed by 81658de.


clarify spot instance pricing

a high enough max bidding price (confusingly named --cloud-spot-price) is required to get a spot instance
after a spot instance is running:

if the spot price rises above the maximum (specified above), AWS EC2 interrupts your spot instance
also, AWS can (and does) often interrupt it anyway (regardless of your bidding price) unpredictably
So basically there's no way to make spot instances never interrupt. Instead you need to either use on-demand (costs $$$ more ongoing), or program some recovery logic (costs time/dev effort one-time)

what about other cloud providers?
what are the conditions for resuming? what does the user need to do (#207)?

Would this go into an existing doc somewhere?


Harbor 2.3.3 missing from projects.registry.vmware.com/tce/main:0.9.1 as shown in Docs

The docs call out the installation and use of Harbor 2.3.3, however, there is no ability to install 2.3.3 since the docs call out installing the repository of projects.registry.vmware.com/tce/main:0.9.1. I'm assuming Harbor 2.3.3 is not in projects.registry.vmware.com/tce/main:0.9.1. So how does one install it?
Bug Report
The package management docs specify using projects.registry.vmware.com/tce/main:0.9.1 as the repo to install. However, that repo does not have Harbor 2.3.3 and only has Harbor 2.2.3 available.
kendrickc@kendrickc-a01 harbor % tanzu package available list harbor.community.tanzu.vmware.com
- Retrieving package versions for harbor.community.tanzu.vmware.com...
  NAME                               VERSION  RELEASED-AT
  harbor.community.tanzu.vmware.com  2.2.3    2021-07-07T18:00:00Z

Expected Behavior
Harbor version 2.3.3 should be available.
Steps to Reproduce the Bug
Follow the docs.
$ tanzu package repository add tce-repo \
  --url projects.registry.vmware.com/tce/main:0.9.1 \
  --namespace tanzu-package-repo-global
tanzu package available list harbor.community.tanzu.vmware.com

Screenshots or additional information and context
n/a
Environment Details

Build version (tanzu version): v0.2.1
Deployment (Managed/Standalone cluster): Managed
Infrastructure Provider (Docker/AWS/Azure/vSphere): AWS
Operating System (client): Mac OS

Diagnostics and log bundle
n/a

This may be due to lack of versioning in our docs so far. The last official release did not include harbor 2.3.3, but has since been added in https://github.com/vmware-tanzu/community-edition/pull/2413
This will be available with the next release (currently planning for early December, though that may change). But ultimately the "fix" for this is to make sure we have release-versioned docs.

Got it. Yes, it is a bit confusing. Having parity of what's in the docs vs what's available would be good. closing this.


Uncaught Error: tunneling socket could not be established, cause=connect ETIMEDOUT <IP_ADDRESS>:80

[Enter steps to reproduce:]

...
...

Atom: 1.16.0 x64
Electron: 1.3.13
OS: Microsoft Windows 7 Professional
Thrown From: Atom Core
Stack Trace
Uncaught Error: tunneling socket could not be established, cause=connect ETIMEDOUT <IP_ADDRESS>:80
At stream.js:74

Error: tunneling socket could not be established, cause=connect ETIMEDOUT <IP_ADDRESS>:80
    at ClientRequest.onError (/app.asar/node_modules/tunnel-agent/index.js:176:17)
    at ClientRequest.g (events.js:286:16)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at Socket.socketErrorListener (_http_client.js:308:9)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at emitErrorNT (net.js:1272:8)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Commands
  3x -8:31.3.0 core:confirm (input.hidden-input)
 10x -8:00.8.0 core:backspace (input.hidden-input)
     -7:00.8.0 core:confirm (input.hidden-input)
  9x -6:21.3.0 core:paste (input.hidden-input)
     -2:40.1.0 fuzzy-finder:toggle-buffer-finder (input.hidden-input)
     -2:39.7.0 core:paste (input.hidden-input)
     -2:38.3.0 core:confirm (input.hidden-input)
     -1:54.8.0 core:paste (input.hidden-input)
     -1:53.9.0 core:confirm (input.hidden-input)
     -1:29.8.0 core:paste (input.hidden-input)
     -1:21.8.0 core:backspace (input.hidden-input)
     -1:21.1.0 core:confirm (input.hidden-input)
  3x -1:19.9.0 core:backspace (input.hidden-input)
     -1:19.1.0 core:confirm (input.hidden-input)

Non-Core Packages
atom-runner 2.7.1
file-icons 2.1.4
git-clone 0.2.0
git-plus 7.8.0
highlight-line 0.12.0
highlight-selected 0.13.1
open-in-browser 0.5.0
pretty-json 1.6.3
rest-client 1.3.1
set-syntax 0.3.2
sync-settings 0.8.1
turbo-javascript 1.4.0

Thanks for the report!  Can you confirm a few things for us?

what were you doing at the time of the error?
is the error is reproducible?
if reproducible, do you see the error in safe mode (atom --safe)?


Added build-android script

I am now using -i~ but git status gives:
(use "git add ..." to include in what will be committed)
build.ninja~

Also I am not able to rebase the branch correctly.

@swift-ci please test

@swift-ci please test

@amraboelela There was another change recently from @johnno1962 that was merged yesterday regarding Android support: #1189
Can you rebase the changes on top of these and test that your changes still make sense? I'm not sure if there's overlap (the lack of conflicts suggests not) but it would be worth verifying it for Android support.
Separately, if you're interested, you can configure your git repository with git config pull.rebase true which means whenever you do a pull, it'll automatically rebase it instead of creating merge nodes. This makes it much easier to keep up-to-date with the branches :)
If you're doing local changes, you might also want to use git config rebase.autostash true - this allows you to a pull in place while not losing your local changes.
 Hope that's of interest!
Finally, keep up the good work. I know there's been a lot of back-and-forth on this, as well as delays, for which I apologise. I am working to clear the backlog and want to merge these changes in so keep going👍🏻

All good now?

@alblue did Apple assign you the task of "cleaning out" all the PR in Foundation? :)
what about swift  repo, I have a related PR there needs to get moving: https://github.com/apple/swift/pull/11870
and in libdispatch: https://github.com/apple/swift-corelibs-libdispatch/pull/302

@alblue did Apple assign you the task of "cleaning out" all the PRs in Foundation? :)

No, I'm just trying to help clear out the queue :)

One other thing might help - there's two sorts of changes here; stubbing out APIs that don't work on Android, and the build script to help build it. Can we split those into two PRs? The build-script and the .gitignore can go in one and the fixes to help it build in another.
In swift's apple/swift#11870 repo there seems to be a proposal of moving towards a CMake instead of autotools for building the code. Is that an approach we can think of using here?

If we don’t include those changes, the build would give errors, so they should go together.

The cmake proposal is for libdispatch I think. But the cmake script is not ready yet, so I suggest to keep the autoconf build script for now.

If we don’t include those changes, the build would give errors, so they should go together.

I was thinking, maybe we commit the code changes first, then have the build script as a dependent change.

The cmake proposal is for libdispatch I think. But the cmake script is not ready yet, so I suggest to keep the autoconf build script for now.

OK. We don't have a CMake list for now in foundation, so that makes sense. It would be interesting to know how much it would be to convert it to CMake in the future. Maybe that's something that @compnerd could advise with.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test and merge

Yeaaah :)
Thank you @alblue


Bar margins - Ability to vertically position bar text

Pretty self-explanatory. Currently all text rendered to the bar is snapped to the top, that creates uneven empty space when the font size doesn't match the current bar size. To circumvent that, a new parameter to set the bar margin is created.
I tried messing with the bar rendering itself to make it automatically center but couldn't find a neat solution, so I settled on making it a custom parameter.
how to configure:
    context.AddBar(new BarPluginConfig()
    {
        //* Bar config
        ...
        BarMargin = 5,
        ...
    }

before:

after:

I need to figure out how to make github not show a bunch of unnecessary commits in my PRs 😒

Or more simply, just always create your PRs based on latest commits in workspacer git master :smile:


Having a terrible time trying to install.

When I run "composer install" I get this:

Installation request for jcupitt/vips 1.0.2 -> satisfiable by jcupitt/vips[v1.0.2].

jcupitt/vips v1.0.2 requires ext-vips >=0.1.2 -> the requested PHP extension vips is missing from your system.

I look at php-info, and vips installed...
Then I re-run pecl install vips and it turns out I have a different version installed.
pecl/vips is already installed and is the same as the released version 1.0.8
So, I switch the version in my composer.json file, re-run "composer install" and I get this:
Problem 1
- The requested package jcupitt/vips 1.0.8 exists as jcupitt/vips[dev-add-array-access, dev-add-header-get, dev-add-throws-decls, dev-dev, dev-master, 1.0.x-dev, dev-use-travis-containers, dev-vips-8.6, v0.1.2, v1.0.0, v1.0.1, v1.0.2] but these are rejected by your constraint.
I followed your directions and end up version conflicts.  How do I fix?
Any help is much appreciated.
Wyatt

Hello @wyatt121, sorry it's causing you trouble.
I would uninstall all the pecl vips stuff you have on your machine, it sounds like you have several versions on there, and just reinstall the latest 1.0.8. You can check that it's correct with:
$ php -i | grep -i vips
/etc/php/7.1/cli/conf.d/vips.ini
vips
vips property => value
Vips headers version => 8.6.0
Vips library version => 8.7.0
Vips ABI version => 51.0.9
... etc.

So I have php 7.1 and the pecl vips extension built against vips 8.6, although I'm actually running the 8.7 binary. But they are compatible, so I'm OK.
I'd leave your composer.json on php-vips v1.0.2.

Ok.  I'm still having a tough time.  I set up a fresh Digital Ocean droplet and installed NGINX/PHP.
From my understanding, I need to install these packages in this order:
https://github.com/jcupitt/libvips
https://github.com/jcupitt/php-vips
https://github.com/jcupitt/php-vips-ext
The instructions are not very straightforward.  I believe I followed them perfectly.  Can I just use apt-get for everything?  I'm assuming by using apt-get I'm getting wrong/conflicting versions.  Do you guys have a step by step tutorial to install the 3 packages above in order on an Ubuntu/PHP/NGINX machine?
I'm running Ubuntu<IP_ADDRESS>
PHP Info:
http://img1.hometownapparel.com/info.php
My composer error output:
composer require jcupitt/vips
Using version ^1.0 for jcupitt/vips
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- jcupitt/vips v1.0.2 requires ext-vips >=0.1.2 -> the requested PHP extension vips is missing from your system.
- jcupitt/vips v1.0.1 requires ext-vips >=0.1.2 -> the requested PHP extension vips is missing from your system.
- jcupitt/vips v1.0.0 requires ext-vips >=0.1.2 -> the requested PHP extension vips is missing from your system.
- Installation request for jcupitt/vips ^1.0 -> satisfiable by jcupitt/vips[v1.0.0, v1.0.1, v1.0.2].

Just FYI... I'm hoping to run this code at bottom of this page...
https://stackoverflow.com/questions/49681709/is-imagemagick-the-fastest-way-to-overlay-images-how-do-i-make-faster-or-is-the?noredirect=1#comment86400081_49681709

You should be able to install with just:
$ sudo apt install libvips-dev
$ sudo pecl install vips

Just like any PHP module. I'll make a 16.04 VM and try it.

Oh, I've not tried with nginx, I've always just used apache. I'll try.

This seems to work for me:
FROM ubuntu:xenial

RUN \
  apt-get update && \
  apt-get install -y \
    build-essential \
    libvips-dev \
    nginx \
    php7.0-dev \
    php-pear

RUN \
  pecl install vips

RUN \
  apt-get install -y \
    composer

# enable vips at the cli
RUN \
  echo "extension=vips.so" > /etc/php/7.0/mods-available/vips.ini && \
  ln -s /etc/php/7.0/mods-available/vips.ini \
        /etc/php/7.0/cli/conf.d/20-vips.ini

WORKDIR /data

Did you enable the vips extension for the cli? composer will need that.

Here's a complete example:
https://github.com/jcupitt/docker-builds/tree/master/php-vips-ubuntu-16.04
Sadly it doesn't work for your exact use case, since the libvips packaged with Ubuntu 16.04 is too old and does not have the composite operation.
I would switch to something like Alpine, which has up to date packages, or build libvips yourself from source.
There's a script to build libvips from source here:
https://github.com/jcupitt/ruby-vips/blob/master/install-vips.sh
which I use for Travis CI. That should be simple to add to your droplet.

Holy Cow!  I got it to work through composer!!!  Turns out I was missing extension=vips.so  /etc/php/7.0/cli/php.ini as you suggested above.
Loading composer repositories with package information
Updating dependencies (including require-dev)

Installing psr/log (1.0.2)
Downloading: 100%

Installing jcupitt/vips (v1.0.2)
Downloading: 100%

Writing lock file
Generating autoload files

Hi,
So I load up my test script, and I run into some problems.  My t-shirt w/ overlay are not being displayed, instead, I get this little outline box in the center of the screen.
Have you seen this little box before?
http://img2.hometownapparel.com/pics/test.php
`<?php
require DIR . '/vendor/autoload.php';
use Jcupitt\Vips;
$base = Vips\Image::newFromFile('blank-tshirt.jpg');
$overlay = Vips\Image::newFromFile('GOSHEN.svg');

// make the overlay the same size as the image, but centred and moved up
// a bit
$left = ($base->width - $overlay->width) * 0.5;
$top = ($base->height - $overlay->height) * 0.45;
$overlay = $overlay->embed($left, $top, $base->width, $base->height);

$out = $base->composite2($overlay, "over");

header("Content-Type: image/jpeg");
echo $out;

exit();

?>
`

Progress! I just see a "this image cannot be displayed" message on your test page.
Did you build your own libvips? As I said, the libvips in ubuntu 16.04 is too old and won't work for you -- it's missing the composite operator.
I think your choices are:

Wait for Ubuntu 18.04, the new LTS version. This replaces 16.04 and is due out before the end of the month. There are final betas available now.

Stick with 16.04, but make your own libvips (see below).

Switch to something like Alpine, which has a more up to date package system.

Re. making your own libvips, I updated my example Dockerfile:
https://github.com/jcupitt/docker-builds/tree/master/php-vips-ubuntu-16.04
So it now builds a custom libvips for 16.04. It seems to work for me at least.

Hi,
Yes, I compiled my own version of libvips.  I included the .configure file above.  The test composite overlay script runs without error output.  Yet, the parsed image is not correct.  Any idea?
Wyatt
Image output:

Oh, sorry, I missed that.
I found my php was adding extra ^M characters (ie. after every ^N it inserted a ^M). Could that be happening to you? Perhaps it's possible to tag as binary somewhere?

Hi,
I don't think it's a weird character issue.  I'm just writing the code in VI.   My php.info file shows 8.6.3 of vips is installed.
What do you mean by this?    "Perhaps it's possible to tag as binary somewhere?"
Wyatt

It worked!!!!  It worked!!!  Holy cow!  It worked!  Thank you so much for your help!
http://img2.hometownapparel.com/pics/test.php
Wyatt

FYI.  During my initial tests, your software is 9-10x faster than ImageMagick!  I couldn't be happier right now.  Your software has allowed me to complete solution.  I was very afraid ImageMagick would not be fast enough, and I was going to have to invest in A LOT of computing resources.  Your software saved me big time.  Congrats!  Keep up the amazing work.  More people need to know your libraries.

With ImageMagick I was using the -geometry option that allowed me to scale the SVG and place on the t-shirt with x,y coordinates.  All the t-shirts base graphics will be the same size, but different pieces of apparel will require different size/placement locations.  What is the best/fastest way to place the SVG overlay in an exact position with an exact size using libvips?
"composite GOSHEN.svg blank-tshirt.jpg -geometry 600x700+456+335 JPG:-"

Use the scale load option to size it, use embed (as above) to set the position.
To calculate the scale, you can load twice. When you do newFromFile, libvips will not load or render any pixels, it just decodes the image header. All pixel handling is delayed until the pixels are actually requested.
$image = Vips\Image::newFromFile("somthing.svg");
$base_width = $image->width;

That will give you the "natural" width of the SVG in pixels, the size you'd get if it were to be rendered at scale 1. So you can calculate the scale you need like this:
$target_width = 200.0;
$scale = $target_width / $base_width;
$image = Vips\Image::newFromFile("something.svg", ["scale" => $scale]);

And now it's exactly 200 pixels across.

Hiya, could you open a new issue? This is getting off install problems.

Will do.  Also deleting my comment above.


Added tests for vro + some minor enhancements

Merged vroli and vroops into just vro

NOTE: Tests are more for code coverage then testing functionality.
Either a live server or requests-mock should be used in the future
to ensure functionality is working as expected.
Also note -- authentication should be added to this shim.

Coverage increased (+1.9%) to 79.157% when pulling c63305c0e029fbe5836c081bcf8bf888e755c97a on vro into e589b10dd5438b464825000bf8d9ac950cc2ab14 on master.

Also note -- authentication should be added to this shim.

Steve, I'm using .netrc for the authentication.  Reason for this is to keep credentials out of the code.  If desired, I guess I could do something like have a configuration script so that credential sets could be saved in a secure file.  I'm open to whatever makes sense but I don't think people like having credentials stored in code?

Ah, I should have checked the readme. So .netrc takes precedence whether you define basic auth in the shim or not. Given these are meant to be sample shims with a low barrier to entry (e.g. so may not know what .netrc is) I added it for consistency. Also learned about OAuth and SSO so added support for them as well -- let me know what you think of the changes John.

Note the travis failure is safe to ignore -- it is fixed in the jira pull request


binance key error???

Hi, i have this problem.
my api key and secret key is the true. not false. but the bot give error. why??
I change my api key and secret key that's doesnt work.
I have ccxt
I try with cmd same issue
soo why this problem???
https://prnt.sc/AjKUhgSWG2hC

Key not valid


Add profiiles to the spec

Since the spec is getting about 3x bigger, maybe we should clearly define levels so that implementations can start small.

core-only, does not include tags/refs.  This greatly reduces the API surface of a library.
binary-only, only implements binary format
text-only, only implements textual format

Another flag might be bounds checks (for example a C library that tracks the end of the range vs one that only has pointer)

I think this would expand the adoption of nibs beyond web and other higher-power application environments.  Makes me wonder just how small a parser could get (nibs RPC over IR between attinys? :) )