[Bug?]: Assets with names containing international characters don't work in prod on cloudflare-pages

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Assets named with international characters do not load in prod, at least when using the cloudflare-pages preset.
Expected behavior 🤔
Assets named with international characters work consistently in dev and prod using any preset.
Steps to reproduce 🕹
Steps:

Image files src/assets/서아.webp and src/assets/seoa.webp exist
Import them and use them in img tags
Note that both images show up in dev, but when deployed to prod, at least on cloudflare, the seoa.webp image loads correctly while the 서아.webp image is broken.

I haven't yet tested this using other presets so I'm not sure whether or not this issue is exclusive to cloudflare-pages.
Context 🔦
I am trying to import images such as 서아.webp named with international characters and use them in img tags.
Your environment 🌎
No response

Hello!! @rvlzzr :)
fix: #1607
Rename files with international characters to use ASCII characters, or URL-encode the filenames in your code. This prevents Cloudflare Pages from misinterpreting the filenames and ensures they load correctly in production.

I think this is actually an issue with cloudflare pages. I'm not using SolidJS, but I managed to reproduce it yesterday when deploying a pages app with different wrangler versions, a directory I have was getting uploaded with a unicode character on its filename (ú) changed to 0xFFFD (�).
Both deployment and GET requests with url-encoding were working fine for months until this last deployment (which was the first deployment in a few weeks). Luckily when I downgraded wrangler to 3.67.1 it worked for me, but I think it was just a coincidence as it later failed with 3.67.1 and now it's working even with 3.73.0.

fix: https://github.com/solidjs/solid-start/issues/1607

@neehhaa06 it that link correct? It's pointing to this same issue

It works correctly using Astro. https://anydrop.com/ is just a basic astro app deployed with wrangler pages deploy dist.  The images with and without international characters both load correctly as expected. I don't see why it should be possible for Astro but not for SolidStart.
export default defineConfig({
  output: 'server',
  adapter: cloudflare()
});

---
import Seoa from '../assets/geurimjaseoa.webp';
import 서아 from '../assets/서아.webp';
---

    <meta charset="utf-8"/>
    <link rel="icon" type="image/svg+xml" href="/favicon.svg"/>
    <meta name="viewport" content="width=device-width"/>
    <meta name="generator" content={Astro.generator}/>
    <title>Astro</title>

Seoa

서아

Hey, I probably wasn't clear enough, but from my experience this is an issue that happens sometimes when uploading files to Cloudflare Pages. I'm not using solid, but I have an app that worked correctly for months, except that on some of my last deployments my file names got incorrectly changed. My file path changed from something like assets/próprio/cropped.png to assets/pr�prio/cropped.png`, however after retrying the deployment some times it eventually worked as expected.
My guess is that you got unlucky with your Solid deployment, but lucky with Astro.
To confirm that, I suggest that you try verifying the files that got uploaded to Cloudflare Pages.

Open the Cloudflare Dashboard on https://dash.cloudflare.com
Click on Workers & pages
Select your project
Find the deployment you did with Cloudflare pages that was failing to load the images and click on "View details"
On the "Assets uploaded" tab, expand the assets directory (or wherever is the image) and check the filename. If my guess is correct, you should find ��.webp
If your dist/build directory is still there, compare to the image name there to see if SolidStart generated the correct image name.

Another thing you can try is deploying again now and see if it happens to work (you can deploy to a preview branch by adding e.g. --branch development)
My guess is that there's some Cloudflare server that's misconfigured or running different software/version that's screwing up the encoding.

Hmm.. this is lower level than we are handling since we don't serve the assets. Nitro is where I'd probably look to see if there is a similar issue for cloudflare-pages.

I just tried Nuxt and it works correctly there as well. I don't see Nitro doing anything wrong here.

I notice that in dist/_routes.json Nuxt does wildcard excludes:
{
  "version": 1,
  "include": [
    "/*"
  ],
  "exclude": [
    "/_nuxt/*",
    "/favicon.ico",
    "/robots.txt"
  ]
}

Whereas the _routes.json generated by Solid-Start lists each excluded file individually. I'm not sure what piece is responsible for generating _routes.json but could it be modified to use wildcard excludes like Nuxt? Perhaps the individual excludes for files containing these characters aren't encoded the way Cloudflare expects here?

That's a good hint. Vinxi uses Nitropack directly which probably differs from how Nuxt does.

It seems like the issue I hit and pointed out above with corrupted uploads is unrelated to this one, sorry for the confusion.
I managed to reproduce this issue and I can confirm that in this case the assets were uploaded correctly, have the same encoding when comparing the asset in "assets uploaded", the exclude in the "invocation routes" and the  tag, but the function is still called when trying to get that image.

Perhaps the individual excludes for files containing these characters aren't encoded the way Cloudflare expects here?

Yeah, it does seem like the issue happens when matching the request path with the exclude, either because of a different encoding or because Cloudflare doesn't international characters as expected in their matching system. I haven't been able to find anything related online.


Clubs Page Responsiveness

Make sure you have read the CONTRIBUTIONS AND SETUP guidelines before working on this issue.

Fix 1:

For TABLET and MOBILE view i want to have the cards size smaller than what it is now.

Fix 2 :

For DESKTOP view i want to have a much more gap between the NAVBAR and the Cards.
In case of any issues do tag me in #milan channel there and we can talk about it !!

I would like to contribute to this under JWOC.

I would like to contribute to this under JWOC.

Go ahead.
After done , tag me in DISCORD's #milan channel before making a Pull Request.
Assigning this to  you.


Removed coffee Event, and changed location of gdg and clc

Removed the coffee events, and moved google developer Groups along with canada learning code to community events

If you want a github hack too you can say comment: this pr fixes #165 and #163
and then when I merge this pr it will automagically close those issues


format the output

Can you write an example of how to format the output check area text.

I'm not sure about this issue. Anyway, you can check the output text files in the result folder.


removal of custom type in proto

Remove of custom type in proto
*update in  grpc blockchain_service.go

The best way to address this issue is defining a new type for hash. Now hash is a byte array (slice). We can make a new type (fixed length of byte array, since the hash has fix length) and defining a method for converting hash to hex string.


Task - No error of exceeding limit when changing title of existing task & system message posted

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.53-2
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Navigate to any report
Click on "+" > Assign task
Enter title and finish creating a task
Open the created task
Click on Title and change to anything > 100 characters
Click on "Save"

Expected Result:
The error is displayed in the title editor that the field is exceeding limit of 100 characters, and user can not save the long title
Actual Result:
The error is not displayed in in the title editor, the title gets updated briefly, user is returned to the task report, and the system message of updated title is posted. There is only one error message in the task report that the title is too long
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/7009c399-32b6-4595-8b56-701c751f082f
View all open jobs on GitHub

We think that this bug might be related to #vip-vsp

@kevinksullivan  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I would put this in VIP-VSB, since it's tied to task management. I would put this as a LOW issue in terms of priority though, because this is only an issue AFTER the task is created, and the error works well when creating the task with > 100 characters

Proposal
Please re-state the problem that we are trying to solve in this issue.

Task - No error of exceeding limit when changing title of existing task & system message posted

What is the root cause of that problem?

We do not validate the task title length if its length is greater than 100.

What changes do you think we should make in order to solve the problem?

The exceeding limit character is a common error, and is used in whole the app, but currently, we handle it manually. For example, with the task description, we need to handle it in the validate function as below:
https://github.com/Expensify/App/blob/ddf9e7ae25fcc9b0a2516ed341947ad38130b36f/src/pages/tasks/TaskDescriptionPage.tsx#L38-L46
And we need to do a similar thing with other forms we need to limit the character, leading to duplicate logic.
So my solution is, we will let the FormProvider component handle it automatically. below is the details.
First, we need to create a new variable, named maxLengthError, to differentiate itself from the maxLength
Then, add the below logic to this one:

            Object.entries(trimmedStringValues).forEach(([inputID, inputValue]) => {
                if (inputValue && inputPropsRef.current[inputID].maxLengthError && inputValue.length >inputPropsRef.current[inputID].maxLengthError ) {
                    ErrorUtils.addErrorMessage(validateErrors, inputID, ['common.error.characterLimitExceedCounter', {length: inputValue.length, limit: inputPropsRef.current[inputID].maxLengthError}]);
                }
                })

In the above, inputPropsRef stores all the input props.
Then, if we need to limit the character, for example, in this case is task title, just need to use:

                            <InputWrapper
                                maxLengthError={100}

What alternative solutions did you explore? (Optional)

Also, we can just need to add maxLength={100} to this one to prevent user from typing more than 100 characters

@thesahindia Do you have any feedback about my proposal (which will reduce redundant code in future)?

@thesahindia can you elaborate on why the selected proposal was chosen? I'm not particularly knowledgeable on our standards for forms and would be curious to hear if there was anything specifically that made you choose one proposal over the other?
@Krishna2323 please refrain from using accusatory language. This is a community and everyone deserves to be given the benefit of the doubt so we can make the best software possible.

Reducing the price of this since it is a low priority bug and is a fairly simple.

@blimpich Currently, the logic to validate the max length limit is handled separately. Or to put it another way, we need to call it for each input field we need to limit length. That leads to the duplicate logic. So we also should consider handling it generally, as I mentioned here

Yes I think we should consider handling it generally, though I'm not sure how big of a lift that would be. If we went with that we would ideally also change all existing instances of where we create limits for text inputs to use the new format you propose right? I'm not sure how big of a change that would be or if it would be high risk for regressions. Again, I'd like @thesahindia's thoughts on this.

If we do like that, IMO, I suggest 2 options:

Option 1: There are ~15 existing instances and we can update them to use the new format.
Option 2: Only apply the new format to fix the current issue, and will use that format in future components

@thesahindia What about this comment? Can you help check it

Yes. I think we should handle this generally ASAP because, in the future, there will be more and more similar inputs created, in that time, it is difficult for us to refactor the max length logic. There are two options for us mentioned here

Payment summary:

@thesahindia - $250
@Krishna2323 - $250 (completed in NewDot)

@thesahindia please complete the checklist above and we can close this out, thanks!

$250 approved for @thesahindia


[9.x] Improve performance of Arr::prependKeysWith()

Improve the performance of Arr::prependKeysWith();

No benchmarks included.


Interrupting progress bar breaks future printing

This is pretty consistently breaking printing on my system:
julia> import Term.progress: track, ProgressBar, update, start, stop

julia> loop = collect(1:10);

julia> for i in track(loop)
           sleep(0.5)
       end
Running... ● ━━━━━━━━━━━━━━━━━━                                            ●  3/10  30 %
^CERROR: InterruptException:
# ... < truncated >

julia> for i in track(loop)
           sleep(0.5)
       end

julia> import Term: install_term_logger

julia> @info "working"
[ Info: working

julia> install_term_logger();

julia> @info "not :-("

julia>

It seems that even println() stops working after this, though the default logging seems unaffected.

As noted in the docs, progress bar temporarily re-directs stdout. If the ProgressBar is not correctly stopped it will not restore stdout correctly.
I think there should be a clearer warning in the docs about this since it might not be clear from the current text. Also perhaps this shouldn't be the default behavior.

Yeah, this behavior seems undesirable. I wonder if there's a way to fail more gracefully, or at minimum have a way to wrench back normal behavior.

Yeah, that's true.  In Python the solution would be to have a context manager for the progress bar.  Perhaps the solution is to encapsulate the progress bar in a do block 🤔

I agree with @kescobo here as this is quite a bummer for me.
Introduces a bit of brittleness into the REPL such that I worry that if my code is not fully correct, it'll break printing and I have to restart my REPL session - which for me can be a rather large productivity hit.
So were you thinking about syntax like this @FedeClaudi ?
import Term.progress: track

myvec = collect(1:5)

ProgressBar(; N = length(myvec)) do pbar
     for i in myvec
        println(i)
        update(pbar)
     end
end

This wouldn't be so bad I don't think as you still create a ProgressBar object that is referenced to pbar such that you can then arrange it in a given panel.
Although perhaps you had something else in mind!
I hope this issue gets addressed soon - happy to assist in testing where I can. 😄

Hello,
Please note that this:
import Term.progress: ProgressBar, update

pbar = ProgressBar(; N=100, redirectstdout=false)

for i in 1:100
    update(pbar)
    i % 25 == 0 && break
end
print("out")

and this
import Term.progress: ProgressBar, update, stop

pbar = ProgressBar(; N=100)

for i in 1:100
    update(pbar)
    i % 25 == 0 && break
end
stop(pbar)
print("out")

work. Of course in the second case you can't make sure that stop(pbar) is reached in case of an error while in the loop.
So you can use the progressbar confidently before a new version comes out.
I'm currently stuck finding a clever way to reshape text, but I'm close to finishing that. After that a new version of Term will come out which just features 'under the hood' improvements with performance. I'm hoping by the end of the weekend to have it out.
After that I will start working on the progress bar functionality and this will be one of my first concerns.

When https://github.com/FedeClaudi/Term.jl/pull/62 is merged stdout will not be re-directed by default, although it will remain as an option. I'd still like to find a way to have it as default but being able to fail gracefully.


Created zh-traditional.json for Traditional Chinese

There was a translation for Simplified Chinese, but not for Traditional. I added it so the app could be more accessible for people living in Taiwan/Hong Kong/Macau.

Thank you @ducdamchi for the contribution 🙇♂
I will surely merge this in before the next release 🤝
I'll try to merge this in before 2025 when I resume work on VHA 🤞


one frame

if I can test the model to estimate the gaze only input one frame?

Hi!
The current version of the code expects 3 input text files, as well as the image, with the following information of the image:

CCS_3D_info: 3D information of the face (head pose and 3D landmarks) wrt the Camera Coordinate System. In the Test folder the example is computed with OpenFace; for instance, you can use their OpenFaceOffline.exe Windows executable to easily extract this information.
landmarks: 3D landmarks from Bulat et al. 2017. Their instructions are quite clear as well.
calibration: camera matrix. If you don't have the camera parameters, you can use a dummy matrix like so:

[1.2*image_width, 0.0, image_width/2],
[0.0, 1.2*image_width, image_height/2],
[0.0, 0.0, 1.0]

You can follow the examples in the Test folder to check the required format.
Anyway, I'm currently preparing a new version of the code which will have all the steps integrated, so that you just need to use one image as input and the code will compute all the necessary pre-processing steps as well as estimate gaze. It should be ready by mid July, so if you're in a hurry I suggest you try the current version, otherwise wait till the new one is out :).
Best,
Cristina

ooooooooook!
Thank you very much!
It had helped me a lot, and I can run in one frame now.


[5.2] Adding carbon helper function

Allows for a cleaner syntax when dealing with Carbon instances. You can easily use any of the Carbon methods:
$now = carbon();

$date = carbon('2016-07-27');

$formatted = carbon()->format('Y-m-d H:i:s');

Would prefer to hold off on this.


Zip Archive Abstraction plus Minor tweaks for factor file generator

Description

Here's the zip archive abstraction I spoke about. The main entry is through Archive.OpenRead and Archive.OpenWrite and you can pass it an enum value picking which underlying implementation will be used -- figured it may be handy -- factor file generator set up to pull from command line or config if value present. A super awesome thing in here is the ArchiveCache which allows you to 'checkout' a zip instance and 'return' it -- like it's a freakin' library book! This support lockless multi-threaded read scenarios.
Related Issue

See #2378
Motivation and Context

These changes are in support of the new factor file generation/supplementation/projection application.
Requires Documentation Change

No.
How Has This Been Tested?

Probably not well enough, really need to see days tick by w/ the ticker plant properly emitting non-finalized events.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description or feature-<issue#>-<description>

There are core issues in the application of mono zip libraries which cause corrupt zips and thread explosions which aren't fully understood; and rather than understanding them fully we've pulled in three separate zip libraries and applied them in various ways. I think to merge this is building layers on top of that poor initial decision and cleaning up the compression libraries should be done in a more thoughtful way disconnected from the Live-Corporate events issue.
So as tempting as it is to merge it to continue the march of progress I know we'll just be installing bad patterns for the future that we'll need to undo. And rather than debating the zip implementation here; I'll close this for now as too much code unrelated to the Live-Corporate events issue and open issue (https://github.com/QuantConnect/Lean/issues/2435) to continue archive clean up later.


chore: Add update script and explanation

Changes

chore: Add update script and explanation

Note: Knobot will be enabled afterwards this PR is merged and script present.
/cc @rhuss

Also depends on to work as expected https://github.com/knative-sandbox/kn-plugin-source-kamelet/pull/201.

Some proof read corrections, otherwise fine. Thanks!

@rhuss ready for the next round. 🙏


Terminal closes itself unexpectedly from time to time

Windows Terminal version
1.21.2911.0
Windows build number
10.0.22631.3880
Other Software
No response
Steps to reproduce

Start the terminal app
Let it run with one or two tabs open running console applications

Expected Behavior
Terminal should stay open until I close it.
Actual Behavior
Terminal closes itself from time to time, also stopping all running console applications. Last time was last night at 2024-10-28 01:50 +0100. I have no event log of this but it could be once in a few months. All other applications are still running, nothing else stops unexpectedly.

If it's an auto-update situation and the Store app force-closes the Terminal, then there's a serious problem here. The Store must not have the power to randomly kill other apps whenever it wants. If that's what it does, I'll have to force-disable those updates. I expect it to be at least so cooperative and inform me that it wants to install an update and requires the Terminal to close. If I can't afford to stop all currently running console apps (which might do long-running work), I must have the ability to defer this for arbitrary time.
I'd appreciate it doing its updates when I also let Windows Update run. Then I'm aware that a reboot is needed and all apps are closed, so I'll only do that when possible. IIRC, PowerShell (the new one) is also only updated along with Windows Updates, so Terminal should do just the same.

Alas, this actually came up in a mail thread while I was out. For my own reference: "Subject: RE: UpdateWhileInUse issue follow-up"
tldr of that thread is that we didn't update our manifest entirely correctly. Sounds like just adding the new property () wasn't good enough. We'll also need to set our MaxVersionTested to 10.0.26100.0.
This alas will have other, unexpected consequences (apparently), so we will need to do quite a bit of validation on our side.

Good to hear that you know what's happening and what might fix it.
Until this is fixed, can I selectively prevent Terminal from being updated automatically? Without disabling all app updates altogether? Or can I only shut down the whole thing all at once? I remember Android has auto-update settings per app (not that auto-update would actually reliably do anything there, but at least the option is there). Couldn't find that in Windows or the Store app now.

Still happening.

Until this is fixed, can I selectively prevent Terminal from being updated automatically? Without disabling all app updates altogether? Or can I only shut down the whole thing all at once? I remember Android has auto-update settings per app (not that auto-update would actually reliably do anything there, but at least the option is there). Couldn't find that in Windows or the Store app now.

I would also like to know this.

No info yet. I've disabled the automatic updates in Windows Store. Like I already did for Windows altogether. Considering Microsoft's ever-decreasing updates quality, extra carefulness is due. Never let it update when it wants to interrupt your work. Do it shortly before new updates appear. By then most issues should be sorted out.

Alas, not that I'm aware of. This has been one of rougher edges with the Store as long as I can remember. Updating our manifest is the only way I know how to fix this. Just a bummer that the magic keyword here needed a second magic keyword that we didn't know about, and has other possibly unexpected consequences 😕


feature: ignore min_width when there isn't enough space

If i want open a lot of splits i will get that error:

But i need use min_width option, because without it, my not focused splits will be too small.

This is a tough one. We will need to keep track of N number of splits open and the W width of the users display.
We can then take W/N and check if it is < min_width. If so, we can reduce min_width by an increment. But this can lead us to other issues. Let me think about a solution


Binary search way of solving painters partition problem

Painters partition problem is a very famous problem of DP . But it can be solved easily using binary search algorithm.
link for problem : https://www.interviewbit.com/problems/painters-partition-problem/

I want to work on this issue if it is seen as good contribution to add .Can i be assigned this issue .Please review.

I want to work on this issue if it is seen as good contribution to add .Can i be assigned this issue .Please review.

@vaishnavijha please get started.

@vaishnavijha please get started.

Please check the pull request raised to this issue

Please check the pull request raised to this issue


[Improvement] In JdbcConfig.java version number are repeated

What would you like to be improved?
Version number are repeated. Note other files also do this.
How should we improve?
Change to use static variables.

there is one mistake in the title of PR #2054 which not fix this issue, can you correct the title of PR 2054? @codeHysteria28 thx.

there is one mistake in the title of PR #2054 which not fix this issue, can you correct the title of PR 2054? @codeHysteria28 thx.

What is an actual mistake ? Thx

there is one mistake in the title of PR #2054 which not fix this issue, can you correct the title of PR 2054? @codeHysteria28 thx.

What is an actual mistake ? Thx

The title of PR #2054 should remove "[#1927]", you can remove it.

there is one mistake in the title of PR #2054 which not fix this issue, can you correct the title of PR 2054? @codeHysteria28 thx.

What is an actual mistake ? Thx

The title of PR #2054 should remove "[#1927]", you can remove it.

Should be updated now 😎 thanks for pointing it out ...


Preview Client Error

wM...artPreview com...0.thetaclient.thetaClientDemo  E  com.ricoh360.thetaclient.PreviewClientException: Permanent Redirect
at com.ricoh360.thetaclient.PreviewClientImpl.responseStatus(PreviewClient.kt:367)
at com.ricoh360.thetaclient.PreviewClientImpl.access$responseStatus(PreviewClient.kt:73)
at com.ricoh360.thetaclient.PreviewClientImpl$responseStatus$1.invokeSuspend(Unknown Source:14)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                Which api i need to use @japboy @yohei @togacy @mhirose @okafuku

@dhivya29
Sorry for the delay in responding.
Do you still need help with this issue?

No
On Thu, 29 Feb, 2024, 10:52 am 松岡 侑凛, @.***> wrote:

@dhivya29 https://github.com/dhivya29
Sorry for the delay in responding.
Do you still need help with this issue?
—
Reply to this email directly, view it on GitHub
https://github.com/ricohapi/theta-client/issues/59#issuecomment-1970424653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEUY6AYTJPPVCCYPWZAPR7DYV25JHAVCNFSM6AAAAABAS5W2YGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGQZDINRVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Website link to "The Squidbags Present: Al" is broken

on the Play page the link to The Squidbags Present: Al leads nowhere.

The official page of the game is down, but the game is still on itch.io. Here I leave the link:

Fixed the link


added another way to create secret from 'kubectl create'; added some Q…

…OL improvements for linux users

Hey there! @YAMLcase, looks like you haven't signed the CLA yet. Could I please have you do that? https://github.com/kubernetes/community/blob/master/CLA.md

Hi @YAMLcase .
Would you check that you have signed the CLA?

sorry about the wait, I had to recover my linux foundation account.  signed it.

Heya @YAMLcase! Thanks a bunch for this contribution. I'm of the opinion that these contributions don't belong in the main docs, given we try not the document external tools of any kind. However, I can totally see this working as a blog post specifically for Linux folks. What do you think?
Tagging @celestehorgan and @jimangel for your thoughts/opinions here.

@natalisucks Thanks for the tag! I agree with this; I'm not sure it's appropriate for the main documentation. @YAMLcase, here's some documentation on submitting a blog post if you need it https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/

👋 @YAMLcase .
I plan to close this pull request.
At any time, you can reopen this PR.
/close


Simple template renders None values as string "None"

When using simple template, rendering None values results as a string which is "None", instead of this shouldn't it render an empty string ?
This behavior makes, need of additional code in form processing.

@defnull It seems like this again is an issue.
from bottle import template
print(template('{{foo}}', foo=None))

Outputs None for me using  0.12.9.


Temperature/pH overflow in reaction filters

See attached screenshot.

Do you remember which page this occurred on? It should be a page with no temperature or pH information.

Done


SSL: WRONG_VERSION_NUMBER

Integration error, something swears on ssl:
[homeassistant.config_entries] Config entry<EMAIL_ADDRESS>for yandex_station integration not ready yet: Cannot connect to host yandex.ru:443 ssl:default [[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1002)]; Retrying in background

I decided on my own, there was a problem in the block lists on the dns server


refactor: new buffer abstractions in decoders

Introduce LanceBuffer, copy-on-write version designed for interoperability
between arrow_buffer::Buffer, bytes::Bytes, and Vec (and their mutable counterparts).  Use this to remove some copies on the decode path (the value decoder is now truly zero-copy).
Introduce the DataBlock and a concept of "data layouts".  Use this to simplify decoding pathways.

Codecov Report
Attention: Patch coverage is 70.00000% with 96 lines in your changes missing coverage. Please review.

Project coverage is 79.35%. Comparing base (a23ba62) to head (5a46d47).

Files
Patch %
Lines

rust/lance-encoding/src/data.rs
59.43%
34 Missing and 9 partials :warning:

rust/lance-encoding/src/encodings/physical/fsst.rs
0.00%
27 Missing :warning:

rust/lance-encoding/src/buffer.rs
62.85%
13 Missing :warning:

...ust/lance-encoding/src/encodings/physical/basic.rs
76.92%
0 Missing and 3 partials :warning:

...ance-encoding/src/encodings/physical/dictionary.rs
86.36%
1 Missing and 2 partials :warning:

.../lance-encoding/src/encodings/logical/primitive.rs
86.66%
0 Missing and 2 partials :warning:

...st/lance-encoding/src/encodings/physical/binary.rs
90.00%
0 Missing and 2 partials :warning:

...encoding/src/encodings/physical/fixed_size_list.rs
71.42%
0 Missing and 2 partials :warning:

rust/lance-encoding/src/decoder.rs
85.71%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2648      +/-   ##
==========================================
- Coverage   79.38%   79.35%   -0.04%
==========================================
  Files         221      222       +1
  Lines       64718    64544     -174
  Branches    64718    64544     -174
==========================================
- Hits        51376    51217     -159
+ Misses      10377    10352      -25
- Partials     2965     2975      +10

Flag
Coverage Δ

unittests
79.35% <70.00%> (-0.04%)
:arrow_down:

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

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


Add a new IF variation ifValid returning TRUE if any valid value including zero.

Reported by ansley b manke on 8 Jul 2011 21:09 UTC
Billy Kessler came to us in frustration, having spent time remembering that in an expression
LET mask = IF var THEN 1

the IF returns FALSE if the variable is zero-valued as well as if it's missing. We've always felt that geophysical variables wouldn't often be exactly zero, but of course there are situations where for instance an instrument might always return zero below some threshold, so there would be lots of valid zero values.
We wrote to the Users List
http://www.pmel.noaa.gov/maillists/tmap/ferret_users/fu_2011/msg00465.html
and made sure the documentation clarifies this, but also talked about adding a new keyword to make this really easy. For instance, IFV for ifValid.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1868

Comment by ansley.b.manke on 8 Jul 2011 23:49 UTC
I have done this - it was fairly straightforward.
yes? LET r =  {1,2,0,1,,3}

! Classic IF is false for MISSING and for zero:

yes? LIST  r, IF r THEN 1,  IF r THEN 1 ELSE 2
             X: 0.5 to 6.5
 Column  1: R is {1,2,0,1,,3}
 Column  2: EX#2 is IF R THEN 1
 Column  3: EX#3 is IF R THEN 1 ELSE 2
             R   EX#2   EX#3
1   / 1:  1.000  1.000  1.000
2   / 2:  2.000  1.000  1.000
3   / 3:  0.000   ....  2.000
4   / 4:  1.000  1.000  1.000
5   / 5:   ....   ....  2.000
6   / 6:  3.000  1.000  1.000

! IFV is false only for MISSING data.

yes?


switched Skyline from legacy Prosit server to new Koina framework

changed PrositConfig_development.xml to koina.proteomicsdb.org since Koina is freely accessible
added new models supported by Koina (ms2pip_2021_HCD, Prosit_2020_intensity_CID, Prosit_2020_intensity_HCD, Prosit_2023_intensity_timsTOF, Deeplc_hela_hf, AlphaPept_rt_generic) except for TMT, crosslinking, and CCS
switched from Tensorflow to Triton
centralized HasPrositServer() function
fixed PrositSkylineIntegrationTest to explicitly encode C+57 to make test validation code simpler
added BiblioSpecLite.WriteDebugMgf() function to make it easy to view library peaks in an external program
added new ModifiedSequence constructor that constructs from a modified sequence instead of unmodified sequence and list of mods
added AssertEx.LibraryEquals (didn't end up using it though)

Should I rename all the Prosit stuff in the code to Koina? Or Predict[ion]?

Depends on how specific it is to Koina now, or it was to Prosit. If you feel you now have generalized interfaces that could serve other predictors, those can be named "Predict[ion]". Anything that seems highly specific to Koina should probably be named for Koina. I guess the ultimate test will be in Bo implementing SkylineAI so that we have multiple prediction options and not just multiple models and settings on a single predictor.

@brendanx67 did you get a chance to try out this PR?

I have completed buddy-testing UI review of the new Koina interface. It looks good and works nicely in the cases I usually demo during courses/workshops. Full code review coming soon.

Shall I go ahead and merge this @brendanx67 ?

Yes!
On Thu, May 9, 2024 at 11:00 AM Matt Chambers @.***>
wrote:

Shall I go ahead and merge this @brendanx67
https://github.com/brendanx67 ?
—
Reply to this email directly, view it on GitHub
https://github.com/ProteoWizard/pwiz/pull/2900#issuecomment-2103159407,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBWUCIBVMB5LWLECXODJTZBO2VBAVCNFSM6AAAAABES7A4M2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBTGE2TSNBQG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Matt, it looks like you did not include the Settings.settings file into this PR. I see new Koina properties in the Settings.designer.cs file, but when I add a setting of my own the Koina ones disappear.

Matt, it looks like you did not include the Settings.settings file into this PR. I see new Koina properties in the Settings.designer.cs file, but when I add a setting of my own the Koina ones disappear.

I'll make a PR to fix this.


callbackWaitsForEmptyEventLoop breaks in 0.0.13

Because we deepcopy context, the getter/setter are called for callbackWaitsForEmptyEventLoop instead of copying the getter/setter themselves. We need to preserve the getter/setter behavior such that callbackWaitsForEmptyEventLoop=false works correctly.

fixed with https://github.com/iopipe/iopipe/pull/24


Clean up qhull wrapper in third_party

This PR remove code from third_party qhull wrapper that is not used.

LGTM


Implement LayerNorm

🙏 Describe the pull request
LayerNorm is implemented.
✅ Checklist

[x] Code follows the project's coding conventions and style.
[x] Tests have been added or updated to cover the changes.
[x] Documentation has been updated, if necessary.

역전파 구현 중 입니다.

@ansteve @mejai1206 리뷰 부탁드립니다.


Fix parseImage function to correctly set registries

Context:
We detected that proxies were not correctly been used by noe. We
found some issues in the parseImage function:

the registry had to literally match so if you had a proxy set for docker.io registry if it used something.docker.io it would not replace with the proxy.
It did not stop after finding the relevant proxy, this lead to tests correctly passing without showing issues.

What does this PR?

Add regex so it matches all subdomains of proxy registry domain.
Stops looking for proxies once it finds one.
Fix the relevant tests so it tests more cases.

Closing it since this approach is not desired.


Wrong cursor on hover

If you use vertical split and solid splitter the cursor on hover is horizontal instead of vertical.

This is a bug in the demo. Thanks for reporting it!  It should be fixed in the source and on the published demo.


MWPW-143783 - [Marquee] block enhancement - Support for logo | label 'lockup'

In Milo I want to be able to author a logo | label 'lockup' in the marquee and have it looks great in all offered variants and authoring usages.

Added supporting styles to accommodate lockup authoring marquee

Resolves: MWPW-143783
Draft URLs:

Before: https://main--milo--adobecom.hlx.page/drafts/rparrish/marquee-lockup?martech=off
After: https://rparrish-marquee-lockup--milo--adobecom.hlx.page/drafts/rparrish/marquee-lockup?martech=off

Libs URLs:

blocks/marquee: https://rparrish-marquee-lockup--milo--adobecom.hlx.page/docs/library/blocks/marquee?martech=off
kitchen-sink/marquee: https://rparrish-marquee-lockup--milo--adobecom.hlx.page/docs/library/kitchen-sink/marquee?martech=off

Live BACOM pages:

https://main--bacom--adobecom.hlx.page/products/magento/magento-commerce?milolibs=rparrish-marquee-lockup
https://main--bacom--adobecom.hlx.page/products/genstudio?milolibs=rparrish-marquee-lockup
https://main--bacom--adobecom.hlx.page/products/experience-manager/sites/aem-sites?milolibs=rparrish-marquee-lockup

@ryanmparrish there seems to be some failing nala tests, could you look into them?


Felipe add linter

This PRs "fixes" the code style following AirBNB coding style which is forced by eslinter package.

Looks good

l00ks g00d


Enable ssl

https://github.com/parvardegr/sharing/issues/19
As we're using express instead as server, just enable the ssl accordingly.

please use "squash and merge" when you want to merge this PR. (or other PRs :) )

please use "squash and merge" when you want to merge this PR. (or other PRs :) )

Well noted.


Add Custom Auth Access Token lifetime

Feature appears to exist in the on-box FTD API, but still need to research whether it works against FMC


VSCode will freeze when opening this JSON file

VSCode Version: Code - Insiders 1.7.0-insider (bbda59212ba3c603addfaa4854b35801fe04d92e, 2016-10-14T06:11:29.547Z)
OS Version: Windows_NT ia32 10.0.14946
Extensions: donjayamanne.python-0.4.2, ms-vscode.latex-0.1.3, redhat.java-0.0.5, seanmcbreen.MDTools-1.0.0, seanmcbreen.Spell-0.8.6, Shan.code-settings-sync-2.3.1

Steps to Reproduce:

download this file
right click it and open it with vscode
vscode will freeze until it says "not responding"

It seems that something with JSON colorizer is to blame.

Can't reproduce on Linux (elementary OS 0.3.2 Freya (64-bit))

Can it be reproduced on Windows?
In my Windows 10, if I directly open the file in a new window, I find the code is not colorized, and not editable too.
It's quite similar to this previous issue #6677
What's more, I find that if you open a simple JSON file at first, for example,
{
  "foo": "bar"
}

this simple file will be colorized as we expect, then open the relatively large file I provided (in the same window, by dragging or File > Open File), it then will work well.

I can reproduce on Windows 10 bbda592, but no longer on c613e1bddce6a544fdf7fcfe2fc0a59626d8195d
Looks like a duplicate of #13667


Update changelog and bump verson for hal release 0.3.0

It's been a bit more than a month, I think we're due for a release.
Lots of new code + docs and it would be nice for it to be on crates.io and docs.rs

Are we doing cargo-publish on the BSPs, or just the HAL?

We haven't published any of the BSPs yet, but I think it's time that we should.


Killing multiple tasks in the UI doesn't work

It sends 1 request per task it wants to kill, but the first command locks the app and all subsequent request until the first is done will fail because the app is locked. This requires a new endpoint that takes a list of task ids and kills them all. An issue for such an endpoint is here: https://github.com/mesosphere/marathon/issues/1206

See https://github.com/mesosphere/marathon/commit/4d692cf987d36d2abfc44943a5cf4f53bbcc1678

Actually, it seems like the DELETE to /tasks has been replaced by a POST to /tasks/delete : https://github.com/mesosphere/marathon/blob/4d692cf987d36d2abfc44943a5cf4f53bbcc1678/changelogs/changelog_0.8.0-0.8.1.md#new-endpoint-delete-v2tasks


Pass arguents to worker

Hi! :)
I need to pass simple arguments to a worker. Somewhat like that:
max = 42;

var w = new Worker(function () {
    for (var i = 0; i < max; i++) {
        // Do something...
    }
}

max is in a different context than what is accessible from within the worker. How can I pass its value (or alternatively, the main context) to the worker?
The only way I would see is to use w.postMessage(max) after creating w, and have the thread inside of w block until it receives this first message. But that seems rather inelegant.

You could capture the value in the function:
max = 42;

var w = new Worker(function () {
   var maximum = max; 'or just the value
    for (var i = 0; i < maximum; i++) {
        // Do something...
    }
}

Thank you! I've never heard of this mechanism before.
When I try it though, I just get a ReferenceError: max is not defined from the line var maximum = max;.
Also, could you explain what you mean by 'or just the value?

Sorry, you have to use let not var in the function to capture the value of max in the function scope.  This should work.
max = 42;
var w = new Worker(function () {
let maximum = max;
'or just the value let maximum = 42;
for (var i = 0; i < maximum; i++) {
// Do something...
}
}

You're right.  That doesn't work with workers.  You will probably need to pass in the argument with a post message (I verified this worked by running it):
var Worker = require("tiny-worker");

var x = 3;
var fun = function (max) {
    let a = max;
    let maxi = a;
    for (var i = 0; i < maxi; i++) {
        console.log(i)
    }
};

var w = new Worker(function() {
    self.onmessage = function (ev) {
        postMessage(ev.data);
    }
});

w.onmessage = function(ev) {
    fun(ev.data);
    w.terminate();
}

w.postMessage(x);

another method would be to pass the arguments in the args parameter like in child_process.fork() of the node.js api, form which the worker class is derived. (https://nodejs.org/api/child_process.html#child_process_child_process_fork_modulepath_args_options)
this should roughly look like this:
let Worker = require("tiny-worker");

let max = 42;
let w = new Worker(function() {
    console.log(process.argv)
}, [max]);

//or with execArgv
let w2 = new Worker(function() {
    console.log(process.execArgv);
}, [], {execArgv: [max]});

The reason this is needed, is because the function inside the Worker definition is created and executed in another process, where the max variable doesn't exist. (therefore the ReferenceError)
So the value must explicitly be passed, if you want a more reference style variable (e.g. updating on change), you need to solve that via messages, with getters and setters.

Hi,
You'd do it the same as you work with a browser Worker; you'd postMessage() data between the domains. See https://github.com/avoidwork/tiny-worker#creating-a-worker-from-a-function for an example.

Thank you all for your help!
I still have some questions, unfortunately, but these probably exceed this thread. I will ask them elsewhere.

feel free to start a new issue, someone might be able to help.


chore: release 1.5.1

:robot: I have created a release *beep* *boop*
1.5.1 (2019-05-17)
Bug Fixes

adding additional labels could potentially break CHANGELOG generation logic (#133) (75933dd)
if we generate a CHANGELOG with only a header, don't open a PR (#132) (ba68930)

Release is at https://github.com/googleapis/release-please/releases/tag/v1.5.1

The release build has started, the log can be viewed here. :sunflower:

The release build failed! Please investigate!


Make back to top link focusable

Make sure you can tab to the back to top link even when it's invisible, this is consistent with how the skip link works.
Closes #899

You can preview this change here:
Built with commit 40f7bcf5d142fc2a1a943158addfee2d3988c44c
https://deploy-preview-926--govuk-design-system-preview.netlify.com

Nice work - this might be worth a little blog post - must be a common issue with 'back to top' links


uid xxxxx cannot explicitly add accounts of type: xxxxxx

i'am using react native 0.61.5 and getting that error, even when i use package name for account name parameter

Hi, same problem. I corrected it by adding
        <service android:name="com.example.accounts.GenericAccountService">             <intent-filter>                 <action android:name="android.accounts.AccountAuthenticator" />             </intent-filter>             <meta-data android:name="android.accounts.AccountAuthenticator" android:resource="@xml/authenticator" />         </service>
In the section "application" in Android/app/src/main/AndroidManifest.xml.
And a file authenticator.xml in Android/app/src/main/res/xml/authenticator.xml
with in
<?xml version="1.0" encoding="utf-8"?> <account-authenticator         xmlns:android="http://schemas.android.com/apk/res/android"         android:accountType="com.tagncar"         android:icon="@mipmap/ic_launcher_round"         android:smallIcon="@mipmap/ic_launcher_round"         android:label="@string/app_name"/>
here is the documentation for the options
https://developer.android.com/training/sync-adapters/creating-authenticator
I hope I've helped you.

This means the account you're trying to read was written by an app with a different signature than the one trying to read. Learn more here: https://developer.android.com/reference/android/accounts/AccountManager


For clusters provisioned with rancher2 TF provider, nginx ingress comments are injected into cluster yaml when editing via the UI

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

provision downstream cluster using rancher2 TF provider
edit new downstream cluster in the Rancher UI

Result:
The cluster won't be able to be saved as nginx ingress comments are injected into the cluster yaml and need to be removed to be able to save. The screenshot below has an example of this issue
Other details that may be helpful:

Environment information

Rancher version: v2.4.5
Installation option: HA

Cluster information

Cluster type: Custom
Kubernetes version: v1.17.5

gz#11486

It seems like because the addon in the cluster.yaml has the word "ingress", it's injecting additional comments into the cluster.yml.
How do we decide how to add comments into the yaml when editing the yaml? @westlywright

The final decision on this was to remove comments from the edit cluster yaml.

Rancher version: v2.4.5
I used the rancher terraform quickstart aws provider. It setups a rancher server with a custom downstream cluster. You can check it here: https://github.com/rancher/quickstart/tree/master/aws
After the cluster becomes active and I tried navigating to Cluster Edit -> Edit as YAML -> Edit the cluster name -> Save
I am able to save the new config. Not able to reproduce.
@rosskirkpat is there a terraform configuration file or specific configuration that we can use to reliably reproduce this issue?
cc @westlywright

@izaac I never mentioned that but the root cause has nothing to do with the TF provider, you just need another key in the cluster config that has ingress in it. I was able to reproduce by doing the following:
Create cluster
Edit Cluster as yaml, after the addon_job_timeout key place the following (ensure the indentation matches the aforementioned timeout key)
addons: |-
  ---
  apiVersion: networking.k8s.io/v1
  kind: NetworkPolicy
  metadata:
    name: test-network-policy
    namespace: default
  spec:
    podSelector:
      matchLabels:
        role: db
    policyTypes:
    - Ingress
    - Egress
    ingress:
    - {}

Save the cluster.
Edit the cluster and select the yaml view again. It was at this point you'd see the comments get inserted above ingress mentioned in this ticket. With the new code, you should not see any comments from Rancher in the file.

Reproduced in 2.4.5 with the steps provided by @westlywright

Rancher version: v2.5-head (12/10/2020) baf4867
Rancher version: master-head (12/10/2020) 46b0df4
There aren't any more comments in the Edit as YAML view.
Editing and adding the yaml with ingress keywords doesn't inject any comments.
I am able to save the 2.4.5 code and edit and save again without issues.


[SPARK-46135][PYTHON][DOCS] Fix table format error in ipynb docs

What changes were proposed in this pull request?
After pr https://github.com/apache/spark/pull/44012, the output format of some 'ipynb' tables displayed in HTML format has been disrupted. The pr aims to fix table format error in ipynb docs.
Before:

After:

Why are the changes needed?
Fix bug.
Does this PR introduce any user-facing change?
Yes, only for docs.
How was this patch tested?
Manually test.
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @itholic @HyukjinKwon

Nice fix! +1 for https://github.com/apache/spark/pull/44049#discussion_r1408578398, otherwise it looks good to me.

Merged to master.


Poster presented at IMDIS 2016 in Gdansk

Coverage remained the same at 86.56% when pulling 5735cf32905f9718d77d424470c584df27755611 on MBARIMike:master into a4e2f7a9e08505596f976ebbe533fd39d165e594 on biofloat:master.

Coverage remained the same at 86.56% when pulling 5735cf32905f9718d77d424470c584df27755611 on MBARIMike:master into a4e2f7a9e08505596f976ebbe533fd39d165e594 on biofloat:master.


missing /website/_assets/js/flow.js

I follow README under /website to install and see errosr:
      GitHub Query: releases for facebook/flow
                    couldn't find file 'flow.js'
  Liquid Exception: couldn't find file 'flow.js' in try/index.html
jekyll 3.1.6 | Error:  couldn't find file 'flow.js'

solved
I download flow.js from https://flowtype.org/assets/flow.js and put into /website/_assets/js/, then fixed

this file is built from source via make js (from the root dir, not /website) and then needs to be copied from bin/flow.js to _assets/js/flow.js. IMO we should add a Makefile to website/ that does this as part of make or make serve or whatever.

@mroch I get it. Thanks so much.

Now that gh-pages is dead, is there any automated process left for updating flow.js when a new revision comes out? The current live version on https://flowtype.org/try/ appears to be a few releases old.

@STRML it's updated by Travis automatically and tracks master. seems to be up to date right now, but maybe Travis was failing for a while when you looked?

Thanks - perhaps a README in the folder should indicate this? I must have just caught a fluke.


Update dependencies and swap to Config module

Updates:

[x] google_api_storage -> 0.34 (thanks @rschef!)
[x] waffle -> 1.1.8
[x] update from Mix.Config to Config (thanks @rschef!)
[x] ex_doc
[x] dialyxir
goth not included as that includes other changes (see #2)

Cherry-picked 1 commit from @rschef's original PR (petermueller/waffle_gcs#20) on the old repo.

@ulissesalmeida, let me know if this makes sense to you.
I added a GCS bucket to the repo secrets so we can get it running tests again.


Cannot read property 'entries' of undefined

[x ] bug report
I am submitting this as a bug because there is no clear and definitive answer on how to troubleshoot this issue. It seems to be effecting developers in different ways and / or for different reasons.
Command
- [ x] generate

Versions
npm --version 5.6.0
macOS --version High Sierra
Angular CLI: 6.1.4
Node: 8.11.4
OS: darwin x64
Angular: 6.1.3
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker
Package                           Version
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        0.6.8
@angular/cli                      6.1.4
@angular/pwa                      0.6.8
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.8
@schematics/update                0.7.4
rxjs                              6.2.2
typescript                        2.9.2
webpack                           4.8.3
Repro steps
ng generate command fails for all types component, module, etc, with the following dreaded error:
Cannot read property 'entries' of undefined
with the debug flag, i am seeing this:
at new FilteredTree (/Users/mike/myapp/node_modules/@angular-devkit/schematics/src/tree/filtered.js:13:18)
Maybe it is worth digging into @angular-devkit to figure this out myself. :/
Mention any other details that might be useful
I have already tried removing the node_modules directory and re-installing.
Also tried removing node, npm and angular-cli all together followed by clean installs of each.
In my particular case...
Important to note, that ng serve and ng build are functioning correctly despite the problem with generate.
Also, generating a new project works, as well as using generate within the new project directory OK, so where do i begin to troubleshoot this issue in my existing project?
ANY help greatly appreciated.

I think this might be a duplicate of the issue #11885.

Hi @martinbdz i created this issue because that issue you are referring to is different. This problem seems to be effecting people in different ways. His issue is different from mine.
What id like to see here is a clear set of instructions on how to begin troubleshooting this error.

I am having this issue as well, but only for some of the schematics; the reducer schematic is working correctly. I am also on a mac.

In filtered.js, line 13 where the error was triggered, and the following forEach loop exists:
[...root.entries()].forEach(([path, entry]) => {
            if (filter(path, entry)) {
                this._tree.set(path, entry);
            }
});

Can anyone explain what this loops through? What constitutes an 'entry' ? Understanding this might help in understanding why the CLI is failing to generate files.

@gitdisrupt , I had the same issue, I tried to update @angular/pwa package to version ~0.7.5, and this resolved the problem for me.

I had the same issue. In my case, it was outdated angular.json. Try to rename "targets" keys in angular.json to "architect".
Before:
      "schematics": {
      },
      "targets": {
        "build": {
       ....

After:
      "schematics": {
      },
      "architect": {
        "build": {
      ....

Same here  ng g c components/test  works fine, but ng g c components/test --spec=false don't.
No idea how to solve this, any advices would be appreciated.
Angular-cli: 6.2.2
Node: 8.12.0
npm: 6.4.1
typescript: 2.9.2
OS: Windows 10

I solved my specific case.
The issue was due to an incompatibility in my angular.json file.
My project was originally generated using an older version of the Angular CLI. Offhand i could not tell you the exact version number, but i can tell you it was around the release of Angular v4.
The key takeaway being that i had originally generated my project with the --skip-tests flag which set the "schematics" accordingly in the original angular-cli.json file in a format not compatible with Angular v6.
The --skip-tests flag when used along with ng new had set my schematics as follows:
"schematics": {
        "@schematics/angular:component": {
          "styleext": "scss",
          "spec": false
        },
        "@schematics/angular:class": {
          "spec": false
        },
        "@schematics/angular:directive": {
          "spec": false
        },
        "@schematics/angular:guard": {
          "spec": false
        },
        "@schematics/angular:module": {
          "spec": false
        },
        "@schematics/angular:pipe": {
          "spec": false
        },
        "@schematics/angular:service": {
          "spec": false
        }
      }

I had since upgraded my project to Angular 6 manually, using the guide provided, but there was no mention of this particular issue needing adjustment.
Removing those schematics solved my problem. I just set it to the default:
"schematics": {}
And with that I am now again able to generate all types, service, component, module etc, albeit if i do not want spec files generated moving forward, i need to use the --no-spec flag along with the generate command each time. That is until i can find out how to correctly configure the schematics for Angular v6.
Its possible the correct configuration would need to follow the conventions outlined here:
https://github.com/angular/angular-cli/blob/v6.0.0-rc.8/packages/%40angular/cli/lib/config/schema.json#L71
As mentioned in my comment above, this error seems to fire in varying ways, so i suspect that if anyone else is seeing this error for another reason, it seems to me that digging through your angular.json file is likely a good place to start digging.

@gitdisrupt , I had the same issue, I tried to update @angular/pwa package to version ~0.7.5, and this resolved the problem for me.

This actually worked for me updated my @angular/pwa to "^0.10.4", hope this will help other people.

I had the same problem and updating @angular/pwa worked for me

I've tried all fixes outlined above (updated pwa, cli, and devkit) I already had "architect" not "target".  We inherited this project and thus the angular.json configuration, so I don't know if they made any weird changes but I looked through the guide on . I'll past the file below, if anyone can take a look and let me know if they see anything out of the ordinary that would be great. I did notice that my defaultCollection under the cli parameter is  "@ionic/schematics-angular", but I dug into those and it's just pointing back to the angular schematics for the modules.
{
  "$schema"<EMAIL_ADDRESS>  "version": 1,
  "defaultProject": "app",
  "projects": {
    "app": {
      "root": "",
      "sourceRoot": "src",
      "projectType": "application",
      "prefix": "app",
      "schematics": {},
      "architect": {
        "build": {
          "builder": "@angular-devkit/build-angular:browser",
          "options": {
            "progress": false,
            "outputPath": "www",
            "index": "src/index.html",
            "main": "src/main.ts",
            "polyfills": "src/polyfills.ts",
            "tsConfig": "src/tsconfig.app.json",
            "assets": [
              {
                "glob": "**/*",
                "input": "src/assets",
                "output": "assets"
              },
              {
                "glob": "**/*.svg",
                "input": "node_modules/@ionic/angular/dist/ionic/svg",
                "output": "./svg"
              },
              {
                "glob": "**/*.json",
                "input": "config",
                "output": "assets"
              },
              {
                "glob": "**/manifest.json",
                "input": "src",
                "output": "."
              },
              {
                "glob": "**/service-worker.js",
                "input": "src",
                "output": "."
              }
            ],
            "styles": [
                "src/global.scss",
                "src/app.scss",
                "node_modules/ngx-toastr/toastr.css"
            ],
            "stylePreprocessorOptions": {
              "includePaths": [
                "src"
              ]
            },
            "scripts": []
          },
          "configurations": {
            "production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                }
              ],
              "optimization": true,
              "outputHashing": "all",
              "sourceMap": false,
              "extractCss": true,
              "namedChunks": false,
              "extractLicenses": true,
              "vendorChunk": false
            },
            "dev": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.dev.ts"
                }
              ],
              "optimization": false,
              "outputHashing": "none",
              "sourceMap": true,
              "extractCss": true,
              "namedChunks": true,
              "extractLicenses": true,
              "vendorChunk": true
            },
            "test": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.test.ts"
                }
              ],
              "optimization": false,
              "outputHashing": "none",
              "sourceMap": true,
              "extractCss": true,
              "namedChunks": true,
              "extractLicenses": true,
              "vendorChunk": false
            }
          }
        },
        "serve": {
          "builder": "@angular-devkit/build-angular:dev-server",
          "options": {
            "browserTarget": "app:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "app:build:production"
            },
            "dev": {
              "browserTarget": "app:build:dev"
            },
            "test": {
              "browserTarget": "app:build:test"
            }
          }
        },
        "extract-i18n": {
          "builder": "@angular-devkit/build-angular:extract-i18n",
          "options": {
            "browserTarget": "app:build"
          }
        },
        "test": {
          "builder": "@angular-devkit/build-angular:karma",
          "options": {
            "environment": "test",
            "fileReplacements": [{
              "replace": "src/environments/environment.ts",
              "with": "src/environments/environment.test.ts"
            }],
            "main": "src/test.ts",
            "polyfills": "src/polyfills.ts",
            "tsConfig": "src/tsconfig.spec.json",
            "karmaConfig": "src/karma.conf.js",
            "styles": [
              "styles.css"
            ],
            "scripts": [],
            "assets": [
              {
                "glob": "favicon.ico",
                "input": "src/",
                "output": "/"
              },
              {
                "glob": "**/*",
                "input": "src/assets",
                "output": "/assets"
              }
            ]
          }
        },
        "lint": {
          "builder": "@angular-devkit/build-angular:tslint",
          "options": {
            "tsConfig": [
              "src/tsconfig.app.json",
              "src/tsconfig.spec.json"
            ],
            "exclude": [
              "**/node_modules/**",
              "**/*.json",
              "**/e2e/**"
            ]
          }
        },
        "ionic-cordova-build": {
          "builder": "@ionic/ng-toolkit:cordova-build",
          "options": {
            "browserTarget": "app:build"
          },
          "configurations": {
            "production": {
              "browserTarget": "app:build:production"
            }
          }
        },
        "ionic-cordova-serve": {
          "builder": "@ionic/ng-toolkit:cordova-serve",
          "options": {
            "cordovaBuildTarget": "app:ionic-cordova-build",
            "devServerTarget": "app:serve"
          },
          "configurations": {
            "production": {
              "cordovaBuildTarget": "app:ionic-cordova-build:production",
              "devServerTarget": "app:serve:production"
            }
          }
        }
      }
    },
    "app-e2e": {
      "root": "e2e/",
      "projectType": "application",
      "architect": {
        "e2e": {
          "builder": "@angular-devkit/build-angular:protractor",
          "options": {
            "protractorConfig": "e2e/protractor.conf.js",
            "devServerTarget": "app:serve"
          }
        },
        "lint": {
          "builder": "@angular-devkit/build-angular:tslint",
          "options": {
            "tsConfig": "e2e/tsconfig.e2e.json",
            "exclude": [
              "**/node_modules/**",
              "**/e2e/**"
            ]
          }
        }
      }
    }
  },
  "cli": {
    "defaultCollection": "@ionic/schematics-angular"
  },
  "schematics": {
    "@ionic/schematics-angular:component": {
      "styleext": "scss"
    },
    "@ionic/schematics-angular:page": {
      "styleext": "scss"
    }
  }
}

Upgraded @schematics/angular to the angular version installed solved to me the problem.


#1: add support for horses in database initialization

changed

/paulo - can you please review this pull request?

/paulo - can you check now?


Undefined DepthEngine::kModelFilename

Hello!
First of all thanks for the samples.
I am trying to use reconstruction_depth_to_3d but I get the following issue:
/mnt/external/cv/opencv_sample/reconstruction_depth_to_3d/depth_engine.cpp:40: undefined reference to `DepthEngine::kModelFilename'
/mnt/external/cv/opencv_sample/reconstruction_depth_to_3d/depth_engine.cpp:47: undefined reference to `DepthEngine::kModelFilename'
Any idea why?
Thanks in advance!

Derp. Found out why!


Problem with datepicker position

Datepicker doesn't appear at the position of datepicker input. The left and top value of datepicker css is incorrect.

When I npm install the package, the nepaliDatePicker.js uses position() to get the left and top value but the file in github uses offset() to get those values.

@ad1199  Because of I forget to upgrade version in npm, you get the different code from Github and npm install package. Now I have upgade version in npm.
And thanks for the comment..:+1:

Thank you! @sanishmaharjan


Why do some strange particles appear when the line width is set to 20

Why do some strange particles appear when the line width is set to 20，It looks like it is caused by the generateRandomParticle method in the postProcessingPosition file，I don't know how to fix it

Same issue when i want to change to webgl2 and use my data source from json file


[BSO] Have the bot DM when +givebox is ready

🚀 Feature Proposal
What the title says. Would be really helpful for those who exchange boxes daily!

and why not just set a reminder? skyra is pretty useful that way. even Carl-bot on other servers. getting a DM from the bots for 2 things rather than daily available for patrons would get confusing in my honest opinion. because people see the DM from OSB or/and BSO they know it's daily ready.

Theres a few reasons why it'd be better for BSO to dm the reminder, rather than using another bots reminder.


Update InstallingAndServicing.md

The directions for VS 2015 and VS 2017 should be the same now.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows-iotcore/commercialize-your-device/InstallingAndServicing.md
:white_check_mark:Succeeded

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


Closing connections to peers

I'm starting a timer in init_worker_by_lua_block() and checking upstream peer health via http.
If a peer is not healthy, I set its 'down' flag to 1. Which routes new connections to other peers. However, old connections are not closed and clients keep using the non-healthy peers.
Could you please point me to any examples on how I can close existing connections to one of the peers from the timer handler?

@racktear I'm not sure I understand what you are talking about given so little info. Maybe you should just debug your own Lua code for your own issues?

Let me clarify.
I have one upstream with 2 peers and I'm implementing a custom health check of those peers. The health check works in a timer handler, and makes periodic http requests to both of those peers to determine whether they are healthy. Then using the result of those requests, I'm marking the peers as either healthy or not healthy. The incoming traffic will go to one of the healthy peers.
To do that I've ported the implementation of set_peer_down from lua-upstream-nginx-module to support streams. Initially I expected that if I set the 'down' flag on the peer, nginx will not route new connections to that peer, and it will close existing connections to it. The latter appears to be false. Which is not a bug at all, but just an implementation detail of nginx.
Now I'm just looking for a way to somehow in addition close all existing connections to the peer when I detect that it's not healthy. Do you know if there is a way to do so from the timer handler?

@racktear No, it should be your request handlers closing the connections themselves. You cannot do that directly from within the timer handler, which is unsafe per se. Your timer handler should only notify those affected request handlers in some way.

@agentzh my problem is that I don't serve content by lua blocks. I just use proxy_pass.
So looks like I'm out of luck with pure lua solutions :(

@racktear Actually you can do that with pure lua solution. The problem is that you are not using pure Lua solution for proxying.

Answering my own question. Just in case people google for this. There is really no easy way to force close the upstream connection from lua. But I've made a patch to ngx_stream_proxy_module.c that checks for the 'down' flag in the data handler, ngx_stream_proxy_process(). If the flag is set, the proxy process terminates the connection gracefully.
Here's the patch:
https://gist.github.com/racktear/4be8934f015d523aa85dcdca47478241
This way one can manage stream proxying from lua, relying on nginx upstream mechanisms.


Improve bindings debug information when a binding in the where clause is missing.

I just upgraded our project from knex 0.10.0 to 0.11.7 and noticed the new bindings check on the where clause, great work but I think it can be improved.

[2016-07-06T12:03:13.983Z] ERROR: u-rest-js/13896 on Macintosh-128k.local: Undefined binding(s) detected when compiling SELECT query: select "Student".* from "Student" where "Student"."id" = ? and Student.removed = ? limit ?
Error: Undefined binding(s) detected when compiling SELECT query: select "Student".* from "Student" where "Student"."id" = ? and Student.removed = ? limit ?
at QueryCompiler_SQLite3.toSQL (/Users/user/GIT/u-base/node_modules/knex/lib/query/compiler.js:78:13)

Since i'm running in debug mode it would be useful to have a bindings array to debug which binding is missing in the query. Maybe the standard debug object can be added to the error? This was the debug object I got using knex 0.10.0 which makes it clear for me that "Student"."id" is undefined and that is what I should fix.

{ method: 'select',
options: {},
bindings: [ undefined, 0, 1 ],
sql: 'select "Student".* from "Student" where "Student"."id" = ? and Student.removed = ? limit ?' }

This needs some extra thought before implementing something. I intentionally only included the actual query string due to cases where you may have a massive query with tons of bindings. I agree bindings would be great to have in there tho. Preferably the .toString() of the querybuilder would be the best, but that too will throw this error. :smirk:
Another idea I had in mind, which im not sure is really optimal, is to create an "initiation stack" when a query builder is initiated. That way we could technically even point directly to the part of the users code that is sending undefined values to knex. Maybe this is overkill tho.
Would work by appending this to the Raw's constructor (and any other builder)
Error.captureStackTrace(this, this.constructor)

This would be great to have, and the initiation stack would be AMAZING -- it can be really frustrating to have knex tell me something is wrong, but not give me either the data I passed in or a stack trace showing where in my code to look.  I have a very large webapp with lots of moving parts and backend supporting tasks, so I wind up having to look at the unbound query string output and think backwards: "where in the code do we do something like this?", and sometimes have to check a few different places since I don't have the data bindings to help.
I would caution about calling Error.captureStackTrace every time a query builder is initiated, however -- I believe there is significant overhead to that call.  If it could be toggled on as an option for debugging though, it would be great.

I've thought a bit more about this (due to use cases for it occurring during my work), and if there is enough concern about keeping large numbers of bindings around that the default needs to be the current behavior of NOT keeping the bindings, then maybe it should be an initialization setting.  Unless there's some overhead I'm not thinking about, I know in my code we never have so many bindings that their usefulness for troubleshooting would be trumped by the performance hit.
Really there are 2 separate feature requests here, but both serve the goal of making knex errors easier to troubleshoot when you don't know what query/code actually caused the error: data bindings and initiation stack.  I think they would both be VERY useful enhancements -- the initiation stack would be useful in situations where the data bindings aren't the issue, though the added overhead is higher.  My suggestion is to make each of them a separate initialization setting.  This us because honestly both of those features would, I think, be useful far more often than simply turning on full debug: true and seeing all queries, or turning on a knex:<something> logger; these new options would just be used to enhance the info on error objects.  Something like dataBindingsOnError: true and reportInitiationStack: true.

I am also having issues debugging raw queries without being given the parameters. It's a real headache.

The bindings are since 2016 logged whenDEBUG=knex:bindings / DEBUG=knex:*. I know this doesn't solve much for production use.
I don't think adding the bindings in plaintext to the error message is such a good idea since generally error messages will be logged to some error log file and the bindings can contain very sensitive information in some cases. Showing the SQL without bindings at least does not expose any sensitive information.
Stacktraces is an issue in and of itself and is an area where we can maybe improve a bit. Currently being discussed in terms of async/await in #2500 .


node-pre-gyp: provide target architecture explicitly

CI is not really checking anything here, I think this can go in.


Add an 'access_ip' for openstack resources to the terraform inventory builder script

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Report
The OpenStack README.md recommends to ignore invalid TLS certificates, which is a security issue. This recommendation stems from the fact that the terraform dynamic inventory script does not provide access_ip for OpenStack resources. This resolves that issue, and removes the offending section in the README.
Environment:

Cloud provider or hardware configuration:
OpenStack

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):

NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Version of Ansible (ansible --version):

  config file = /home/twexler/dev/kubespray/ansible.cfg
  configured module search path = [u'/home/twexler/dev/kubespray/library']
  ansible python module location = /home/twexler/dev/kubespray/env/local/lib/python2.7/site-packages/ansible
  executable location = /home/twexler/dev/kubespray/env/bin/ansible
  python version = 2.7.15rc1 (default, Apr 15 2018, 21:51:34) [GCC 7.3.0]

Kubespray version (commit) (git rev-parse --short HEAD):
90d8f7aa
Network plugin used:
Calico
Copy of your inventory file:
It's dynamic, generated by the aforementioned inventory script
Command used to invoke ansible:
ansible-playbook --become -i inventory/kubespray-test/hosts cluster.yml
Output of ansible run:
It's not something I can post publicly due to company policy.
Anything else do we need to know:
This stems from the discussion in #3588

/lgtm
/approve
Thanks

should it be added here too:
https://github.com/kubernetes-incubator/kubespray/blob/c304a6fe15418765125cd402b460e8a10372661f/contrib/terraform/terraform.py#L687
?

@ant31 Actually, in examining that code a little further, I believe that's where I wanted to make this change. I'll update the PR accordingly.
Question: Why am I getting a failure in the ci-authroized check? It seems to also be preventing the whole pipeline itself from succeeding?

Gotcha. Thanks @ant31!


Curious nix version-dependent evaluation problem

On my other Arch machine (still) running Nix 1.11.7, running nix-env -f . -qaP > /dev/null gives:
error: syntax error, unexpected $undefined, expecting IND_STR or DOLLAR_CURLY or IND_STRING_CLOSE, at /home/tmtynkky/opt/nixpkgs/pkgs/os-specific/linux/bcc/default.nix:29:27

1.11.15 is fine with that file.

system: "x86_64-linux"
host os: Linux 4.9.53-1-lts, Arch Linux, noversion
multi-user?: no
sandbox: no
version: nix-env (Nix) 1.11.7
channels(tmtynkky): "nixpkgs-18.03pre119009.6d1317ab31"
nixpkgs: /home/tmtynkky/.nix-defexpr/channels/nixpkgs

It's interesting that you've decided to fix it :) The same issue was reported in #30834.

I've checked that bcc in stable is not affected and your fix does not have to be backported.

I've checked that bcc in stable is not affected

For what it's worth, I believe Mac is (or was when I installed it) on an unstable channel by default.


Ordering of decorations from different extenstions

I have a vs code extension that uses the decoration api to set decoration at a given range  displaying markdown when hovering over that line. Intellisense a very popular vs code extension shows markdown when hovering over the same range as well. How can one order those markdowns? Currently, intellisense markdown is shown last. I want the markdown of my extension to be shown last instead because intellisense is more important. I don't think the api provides any way to order these markdowns from different extenstions. If that is true, how does vscode determine the order? Could we add an ordering option to the api?

@jrieken any update on this? Unfortunately its a blocking element in our VS code extension development

Extensions cannot influence the order and we don't want to allow them to do that because, naturally, extension authors want their contribution to show at the most prominent place.

Thanks for your response. I would tend to disagree that extension authors want their contribution to show at the most prominent place in every scenario, especially when something like Intellisense is a vital feature for any developer using VS Code. Could you shed some light on how VS code prioritizes the ordering internally @jrieken ?

Could you shed some light on how VS code prioritizes the ordering internally @jrieken ?

It depends on each feature

@jrieken since @FredCoenis in fact asking for his extension to show in a less prominent place that the built-in contributions perhaps you could reopen this ticket as bug that 3rd party extension contributions are showing at the most prominent place than Intellisense?


usage of this package for Inner eml data in ParseEmailFilesV2 vs. ParseEmailFiles and saving as incident file attachment

I'm not sure where to open this issue, apologies in advance.
We currently use ParseEmailFiles which uses older code implementation and we know it is deprecated.  However, ParseEmailFilesV2 which uses this parse-emails python package no longer saves the Inner eml file as a file attachment to the incident which we need to have in our playbook.  We are not able to utilize ParseEmailFilesV2 because of this change using this python package.  The previous implementation of code inside ParseEmailFiles saves all nested attachments as files to the incident.
for reference:
https://github.com/demisto/content/blob/7d85de4e9199699106debb2d0ee3b84f82c8efbd/Packs/CommonScripts/Scripts/ParseEmailFiles/ParseEmailFiles.py#LL3345C32-L3345C32
ParseEmailFilesV2 is working great with this package to identify the correct Inner eml and uses that data in context, however we no longer get the Inner eml file saved to the incident as a file attachment.
Would it be appropriate for this package to have the EmailParser class be able to return the Inner eml file content so that ParseEmailFilesV2 can add support for saving the Inner eml file as an incident file attachment.
https://github.com/demisto/parse-emails/blob/c2a23ba17047136116419c2bba1bb002a3df8675/parse_emails/handle_eml.py#L243
ParseEmailFilesV2 already has a function to save files as an attachment to the incident, we just need EmailParser to be able to return the file content when Inner eml is being used.
https://github.com/demisto/content/blob/7d85de4e9199699106debb2d0ee3b84f82c8efbd/Packs/CommonScripts/Scripts/ParseEmailFilesV2/ParseEmailFilesV2.py#L48
I hope I explained this issue well enough.  Thanks!

Hi @cah-zachary-rouse
Thanks for the update and sorry for the late reply.
According to my test, the ParseEmailFilesV2 already returns the internal email as an attachment to the war room

If you still see different behavior, please attach an email file that this is happening.


Searching in a linked list

Related Issue
issue #823
Proposed Changes

Change 1
make a file of cpp code for searching an element in linked list in both iterative as well as in recursive way with proper comments and mentioning time and space complexity with neccessary information in easy and understandable way.
Chnage 2
Update README.md in accordance to the the file searching in a linked list.

Checklist

[x] ✅ My code follows the code style of this project.
[x] 📝 My change requires a change to the README.
[x] 🎀 I have updated the README accordingly.
[x] 👀 I have read the CONTRIBUTING document.
[x] ✨ I have added tests to cover my changes.
[x] 🚩 All new and existing tests passed.
[x] 🌟 ed the repo

code image
1.

2.

3.

Output image
when node is present in a given linked list

when node is not present in a given linked list

If you have done searching on Singly Linked List...then put your changes into S-SinglyLinkedList Folder

changes done 👍
I have deleted the both files from the main Linked list folder and add them in singly linked list folder.

sorry..but we are not allowed to take PR with lots of commits...create a fresh PR with fewer commits..I am closing it now


v2 - Alter Database Failures aren't Retried

Note: I'm not convinced that we need to add retry logic here, but let's chat about this. Creating this issue just to ensure that we don't forget about it.
Link to deployment logs where I ran into this issue:
https://github.com/zijchen/sql-action-samples/runs/8026524238?check_suite_focus=true#step:4:1202
Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 42008, Level 16, State 120, Line 5 ODBC error: State: HY000: Error: 0 Message:'[Microsoft][ODBC Driver 17 for SQL Server]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.'.
Error SQL72045: Script execution error.  The executed script:
IF EXISTS (SELECT 1
           FROM   [sys].[databases]
           WHERE  [name] = N'$(DatabaseName)')
    BEGIN
        ALTER DATABASE [$(DatabaseName)]
            SET ALLOW_SNAPSHOT_ISOLATION OFF;
    END

Error SQL72014: Core Microsoft SqlClient Data Provider: Msg 5069, Level 16, State 1, Line 5 ALTER DATABASE statement failed.
Error SQL72045: Script execution error.  The executed script:
IF EXISTS (SELECT 1
           FROM   [sys].[databases]
           WHERE  [name] = N'$(DatabaseName)')
    BEGIN
        ALTER DATABASE [$(DatabaseName)]
            SET ALLOW_SNAPSHOT_ISOLATION OFF;
    END

@chlafreniere Before we forget, can you add the OS platform and auth type you were using?

Oh, absolutely. Is this what you'd need, @zijchen?
ubuntu-latest (currently points to ubuntu 20.04)
Authentication=ActiveDirectoryDefault

Closing this issue due to no repro. We call sqlpackage directly so if something's not retried, the logic lies in sqlpackage anyway. Feel free to reopen if issue persists and we can investigate further.


Zero value invoices don't display the amount paid after settled

Description
Any amounts invoices are showing an incorrect amount.
Expected Behavior
The invoice amount should be correct.
Actual Behavior
Any amounts invoices always show 0 for the amount.
Steps to Reproduce

Create an invoice with 0 sat

Pay it with n sat with n > 0

You balance is not updated, in the tx list you see a payment of 0 sat, the channel balances are not updated

Your Environment

Zap Desktop version: master

Hey @Fi3, thanks for filing an issue.
I'm having trouble understanding the problem your facing. What exactly is the issue? I've tried to reproduce what you've described above and all my invoices are showing correct amounts.

I create an invoice and I put 0 satoshis as amount, so an invoice that start with lntb1p (tried only in testnet).
From another client I pay the invoice and with an amount that is not 0 (ex 50000 sat)
In the tx list I can see a received payment for that invoice but the amount is 0 instead of 50000.

Ah, understood. 0 value invoices don't display the amount that is paid after they are settled

@Fi3 I'm unable to reproduce this issue.
What I tried:

Got the QR code on https://tippin.me/@mrfelton
Opened in Zap
Entered a custom payment amount of 1000 Satoshis and paid the invoice

Lightning payment of 1000 sats shows up in the activity list
Clicking on the payment to see the details showed the amount as 1000 sats
Balance decreased by 1000 sats
Please note that 0 value on-chain transactions do sometimes show in the transaction list which are a bi-product of some lnd internals. I wonder if it's one of these that you are seeing?

@mrfelton
I think that you are trying the other way around. I create the 0 value invoice from Zap, and then I pay it from another wallet.
In the tx list I have:
Received payment                                        + 0 tsatoshis
1:29 PM                                                       $0.00

If I click on the tx I get the right tx values:
                           Received
                      Lightning Payment
------------------------------------------------------------
Amount                                             tsatoshis
                                                         500
------------------------------------------------------------
Current value                                            USD
                                                        0.03
------------------------------------------------------------
.....

Also the wallet amount and the channel balances shows a value that is not updated.

@Fi3 Are you using Zap's built in lnd node, or are you connected to your own lnd node? If so, what lnd version are you running?

@Fi3 I was able to reproduce and have a fix in https://github.com/LN-Zap/zap-desktop/pull/2053
In my testing though, the wallet balances are updated correctly (with lnd 0.6). What version of lnd are you using?

@mrfelton ty
Im using Zap's built in lnd node, the Zap vesrion is 0.4.1.


Installation on RHEL 6.7

Hi, I have a server machine (without root access), and want to install Torch on it. Torch dependency file only support Ubuntu, Ferdora, etc, but not Redhat. I wonder how I can do it. Many thanks!

Let me be more specific. I checked the 'install-dep' file, and found most of dependencies are available on my machine. But I got the complaint as follows,
Error: Failed installing dependency: https://raw.githubusercontent.com/rocks-moonscript-org/moonrocks-mirror/master/lzmq-0.4.3-1.src.rock - Could not find expected file zmq.h, or zmq.h for ZMQ -- you may have to install ZMQ in your system and/or pass ZMQ_DIR or ZMQ_INCDIR to the luarocks command. Example: luarocks install lzmq ZMQ_DIR=/usr/local
I also installed zero-mq 3.2.5 and lua-zmq, but it seems still not working. I wonder if I should include the installed files in the environment path as LUA_PATH or somewhere else. Thanks!

Hi all, I found the solution myself. We need to declare the path of ZMQ in 'install.sh' to make the library files accessible.
export PATH=$OLDPATH # Restore anaconda distribution if we took it out.
if [[ uname == "Darwin" ]]; then
cd ${THIS_DIR}/extra/iTorch         && $PREFIX/bin/luarocks make OPENSSL_DIR=/usr/local/opt/openssl/
else
cd ${THIS_DIR}/extra/iTorch         && $PREFIX/bin/luarocks make ZMQ_DIR=\YOUR ZMQ PATH'
fi
export ZMQ_DIR=/homeappl/home/gcao/local/
Hope it helps!


Allow switch statements in TemplateMark

This issue extends #588.
Requested functionality:
Extend TemplateMark so that more complex conditional statements can be used in a bidirectional way. That is, so that users can draft and parse with greater flexibility. This could be done by allowing switch statements.
Switch statements
For example, in JavaScript a switch statement is written as:
switch(colourVariable){
  case "yellow":
  ...
  break

  case "red":
  ...
  break

  case "blue":
  ...
  break

  default:
  ...
  break
}

Maybe this could be written as: {{#switch colourVariable}}{{#case yellow}} ... {{#case red}} ... {{#case blue }} ... {{#default}} ... {{/switch}}

Hi! I would like to work on this feature. Can you please guide me how to get started?

Hello, I would like to work on this, can you please guide me on how to get started!

@OliverTod @DianaLease  Hello, I would like to work on this, can you please assigned me this issues


Surprise: Make a web component to try out Monkey code

Now that we have a fully working implementation of Monkey in Dart, the logical next step is to build something like the REPL for the web.

And exactly timed as a birthday present for @mrnugget, the author of 'Writing an interpreter in Go':
Here comes the  web component! :D https://github.com/mreichelt/monkey-shell


feat: Add nep-413 signMessage in WELLDONE Wallet

Description
Add nep-413 signMessage in WELLDONE Wallet.

Hi, @sunny0529 just checking if there's any plan to address the comment, or if there's anything unclear about my suggestion.

The PR looks good to me now, @sunny0529 thank you for submitting this PR and addressing the comments.


Adjust anchor scroll in docs to show actual line.

The fixed header isn't accounted for when scrolling to anchor points so the original anchor text is obscured.
I would actually prefer to remove the fixed header instead of merging this PR. If it's ok to remove the fixed header let me know and I can do that instead!

LGTM


AlternativeFunctions: suggest using wp_(un)slash()

The WP wp_slash() and wp_unslash() functions are capable of (un)slashing both strings, as well as (nested) arrays, while the PHP native functions can only handle strings.
For input variables, you typically encounter arrays in forms. For instance when a checkbox or dropdown field can accept multiple values. however, the usage of arrays in input variables is definitely not limited to those examples.
With that in mind, I'd like to suggest adding a recommendation to use these functions instead of the PHP native ones to the AlternativeFunctions sniff.
Refs:

https://developer.wordpress.org/reference/functions/wp_slash/
https://developer.wordpress.org/reference/functions/wp_unslash/
http://php.net/manual/en/function.addslashes.php
http://php.net/manual/en/function.addcslashes.php
http://php.net/manual/en/function.stripslashes.php
http://php.net/manual/en/function.stripcslashes.php

@WordPress-Coding-Standards/wpcs-admins Anyone has an opinion on this proposal ?

I agree. I think the original purpose being wp_unslash() and wp_slash() was that in the eventual case that magic quotes could be turned off, that these functions could then no-op. I doubt that will ever happen, but if it does, using these functions will ensure that things don't break.

The other side of what @westonruter pointed out is that these functions should really only be used in the context of dealing with magic quotes. Unrelated slashing and unslashing operations shouldn't use them.

Unrelated slashing and unslashing operations shouldn't use them.

Well, for slashing/unslashing related to database operations, the functions shouldn't be used either as prepared SQL should be used instead.
Let's gather some examples of situations in which it would be preferred to use the PHP native functions over the WP versions. Depending on the examples, either the sniff could try to account for the context in which the functions are used or this PR will be closed.


Code scrolls instead of finding, switches to Normal instead of Copying

Issue Type: Bug
When I launch MSVSCode it won't let me edit the python script unless I switch from
-- Normal --
to
-- Insert --
the cursor turns from a block to a line.
Ctrl + F scrolls instead of finding, although the Key binding for find is Ctrl + F.
Ctrl + C returns it from Insert back to Normal.  Which means I can't copy and paste code into a report
MSVSCode version 1.35.1 (system setup)
VS Code version: Code 1.35.1 (c7d83e57cd18f18026a8162d042843bda1bcf21f, 2019-06-12T14:30:02.622Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz (4 x 2893)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
5.86GB (2.45GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

vscode-test-explorer
hbe
2.12.1

vscode-python-test-adapter
lit
0.3.8

MagicPython
mag
1.1.0

python
ms-
2019.6.22090

cpptools
ms-
0.23.1

python
tht
0.2.3

vim
vsc
1.8.1

The behavior is contributed by the Vim extension you are using. If you are using VSCodeVim, it has options to allow you to override this behavior.


Page contents link location

when navigating to page contents i.e. /docs/view/default/solutions/copilot_solutions_lvweslp2/_index.md#copilot-studio-formerly-power-virtual-agents
the title of the section being linked is hidden above the top banner

it appears that we are using the MDXContent component to create the page content. h2's and h3's etc are created by this and the relevant id's are added to the tags so that the links can be anchored. The problem is that it's slightly off, probably due to some css elsewhere. A solution could be to apply custom css (something like scroll-margin-top: 20px) to the MDXContent so it navigates to the correct place

found this pretty tricky so far. Seems like a lot of the functionality is hidden away via the component so may need to find out if part of the css is causing the offset and fix it from there

https://github.com/AirWalk-Digital/airview-next/pull/53 fix for the issue


OSASINFRA-3572: WIP: handle DNS record for Ingress for OpenStack on AWS

What this PR does / why we need it:
Improve CI workflow where we'll be able to run multiple clusters at the same time leveraging the external DNS operator for the Ingress DNS records.

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-openstack

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-openstack

/test e2e-openstack


Lexical or Preprocessor Issue (Xcode): 'fpdfview.h' file not found

Launching lib/ksmart/main.dart on iPad6 in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: NJT84644HS
Running Xcode build...
Xcode build done.                                           25.5s
Failed to build iOS app
Could not build the precompiled application for the device.
Lexical or Preprocessor Issue (Xcode): 'fpdfview.h' file not found
/Users/zengchanghuan/.pub-cache/hosted/pub.flutter-io.cn/pdfrx-1.0.82/src/pdfium_interop.cpp:4:9
Uncategorized (Xcode): Command SwiftCompile failed with a nonzero exit code
Error launching application on iPad6.
flutter --version
Flutter 3.22.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 761747bfc5 (2 months ago) • 2024-06-05 22:15:13 +0200
Engine • revision edd8546116
Tools • Dart 3.4.3 • DevTools 2.34.3

When I use version 1.0.82, I keep reporting the above error, using 1.0.81 is fine.

Same issue is reported several times; #219, #199, #138, and #12.
Clear all the caches like .pub_cache, build/ an d such (by flutter clean) may fix the issue.