Fix coverage metric

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim
Claim your share of the $500k Binance Airdrop! As the year comes to an end, we're giving away $500 in BNB to celebrate. Follow the steps above to secure your tokens. Don't miss out on this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim
Claim your share of the $500k Binance Airdrop! As the year comes to an end, we're giving away $500 in BNB to celebrate. Follow the steps above to secure your tokens. Don't miss out on this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Winners: @

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @raymundoxmartinez, @TotalPizza, @LeoNero, @gavin-k, @parrachia, @lesmemes, @david-torres

AltLayer Airdrop Season One Update

🚀 Exciting Announcement! AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 300,000,000 (3% of the total supply)
Distribution Categories:

Ethereum Mainnet
Binance Mainnet

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 03, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
nicobevilacqua, @mohamedalichelbi, @contropist, @matteocng, @chainpioneer, @shanefontaine, @nateshirley, @yushinliu, @JReuman1, @weretyczx, @skyDaniel, @ZhangPeibin, @LHY-sudo, @Hugoo, @floranguyen0, @zhaoguijie, @AsparAugustus, @simonfuture2, @nik3010, @macalinao

AltLayer Airdrop Season One Update

🚀 Exciting Announcement!
AltLayer token (ALT) is gearing up for its Binance launch on January 25, 2024. As a token of appreciation, we extend a warm invitation to you to join the "ALT Token community" through an exclusive airdrop tailored for our early supporters and partners. Here's a quick overview:

Total Allocated ALT Tokens: 400,000,000 (4% of the total supply)

For a comprehensive breakdown of criteria and further details, refer to the complete announcement Oficial Website.
The window to Claim $ALT tokens is open from January 25 to February 08, 2024.
Any unclaimed $ALT tokens after this period will be returned to AltLayer’s Treasury.
We deeply appreciate your contribution to AltLayer's success! Stay tuned for more exciting developments in Season One.
Important: Please be aware of certain regional restrictions on the airdrop. Review the disclaimer before participating.
ihgoo, @gvvynplaine, @mishimalisa, @ChainlinkResources, @hirorylabo, @AriZoneVibes, @hid3xxx, @Owlcyone1111, @mohammadali-bacha, @steffanie100974, @phpgeekfr, @rish, @shehuan, @uwanotoha, @crazypisces, @zh, @ethereum-pos, @rrubo, @ker945, @brannondorsey

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
0xAWM, @stasb, @sslivkoff, @isgasho, @srinitude, @RiccardoBiosas, @yilongli, @jokerstudio, @X4, @datzero9, @greysign, @junnmm, @vitali2y, @dannysun85, @aga7hokakological, @Angold-4, @wiasliaw, @junhoyeo, @Matthewjarredondo, @cppmyk

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
arthurmichel, @fl1ghtsch00l, @andreswebs, @oceanborn2, @ankitgahlyan, @mskian, @amlitio, @Rosuavio, @Unisay, @andyfraussen, @bogdan-cu, @ragegear1, @vvviiimmm, @nlt2390, @ma82, @mavratsas, @PopeNobody, @preethi103, @RabidMexican, @seungwonpark

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
alexlinwx, @dasvayda, @Ivesives, @ogty, @Diego696, @mikemarten, @ancienthack, @rogerkibbe, @gpatkinson, @DOUGLASMENDES, @rbinnun, @wilsonodpn, @senchabot-app, @henriquecouto, @mcpadson, @alfiomy, @devdanco, @yung252xx, @0xMario27, @Odyseccus

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here.
Job Description:

Position: Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan
Company-contributed retirement plan
Flexible working hours
Collaborative and inclusive work environment

Requirements:

Proven experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Familiarity with frameworks such as React, Angular, or Vue.js
Problem-solving skills and ability to work in a team

Note: This position is open to candidates from anywhere in the world.
Soul-kingX, @RabeaWahab, @s4bs, @0xbageltoes, @disbitski, @ShuKeW, @clarkeb, @shengchl, @moonpalace806, @Joetoledano, @seanmayer, @dingdaoyi, @andrewsonin, @samchen61661, @1tpp, @ahester-incomm, @landaraido, @channprj, @uvfive, @zlorance


typo? fix

Change
based off .... -> based off of ....

[x] I agree to follow the Code of Conduct.
[x] I agree to follow the Contributing Guidelines.

i believe they are both technically valid grammar lol but this sounds better

i believe they are both technically valid grammar lol but this sounds better

afaik base off is a verb on its own so a preposition is needed before an object
but yeah maybe


Add Monetary Data Types

Monetary data type is not high priority at the moment. You can use the regular mapString method to map to a monetary data type.

No Priority.


Add Protobuf to data serialization category

Packages for parsing, serializing and manipulation of Protobuf

Thank you! The deployment is currently manual and I'll make sure this gets deployed today


Fix missing x-axis tick in weekly forecast component plot

A quick fix for #27

Thanks for this bugfix. It looks like matplotlib is putting an xtick at -1 even though it is out of the plot range. For clarity moving forward, I'd prefer to fix this by  explicitly specifying the xticks to be at the right locations. So,  leave line 724 as was but insert
ax.set_xticks(range(len(days)))
the line before. Could you update your commit accordingly and I'll merge it in?


Reorganize file structure

Instead of copying files around and using symlinks, just store libraries in separate folders to begin with and commit them to source control.

finally did this


Hamburger button added

Hi,
This is with reference to issue #130 .
I have finally added the navigation button animation.
Since our navigation bar collapses only when we view it at smaller aspect ratio..
Hence this animation will be visible at that aspect ratios only..
I have already checked that everything is working fine, If anything else needed from my side kindly let me know.
And if everything is working is fine then kindly merge my part of code also...
Thank You..

Sorry I uploaded one picture twice, here is the other one..

@marizvi looks good. Merging!


KBC-1517: Test branch aware events for workspaces

Jira: KBC-1517
MainPR: https://github.com/keboola/connection/pull/3212
Before asking for review make sure that:

[x] New client method(s) has tests
[x] Apiary file is updated
[x] You declared if there is a BC break or not (will affect next release of a client)

Nechápem teda len prečo sa tam setoval ten runId obom klientom

👀

Ješčtě jsem přidal kontrolu toho, že naopak prod branch id nemá ;)

rebase


Expose high level formatting function

Fixes #43.

I committed 30571c12cb6f2e73ea0fdaf6f8e61d773a61f0ad as an example of how to run format purely. But I'm not interested in maintaining that outside the test suite. I think most people will want to format in IO anyway in order to get module discovery.


Cannot reproduce

Hi
I just run the line
python train.py --data-type ENAS --reprocess --data-name final_structures6 --save-interval 10 --save-appendix _SVAE --epochs 300 --lr 1e-4 --model SVAE --bidirectional --nz 56 --batch-size 32

and get approximately 0 test accuracy, the same is for  --model DVAE. Could you rerun it and confirm that your code works ok, please?

Hi, thanks for running the code. The code ran ok on my machine before launching. I'll check again tomorrow. Could you also attach a screenshot of your running logs and results? Thanks.

Hi, a quick note, I ran S-VAE using your command with "--bidirectional" enabled and the loss did not seem to decrease. But after deleting "--bidirectional" the loss started to decrease and quickly reached near zero (the S-VAE in the paper did not use bidirectional).

@muhanzhang thank you for the advice to delete bidirectional, w/o the rule your implementation of SVAE works well! I feel I could misprint smth in DVAE training, I will retest and close the issue

Mb a working docker container will be useful for someone to run the code:
nvidia-docker run -it --name=deepo_dvae -p 8875:8875 -v /home/:/data --ipc=host --runtime=nvidia ufoym/deepo:all-py36-jupyter bash
add-apt-repository ppa:igraph/ppa
pip install --upgrade pip;\
pip uninstall -y torch;\
pip install torch==0.4.1;\
apt-get -y update;\
export LD_LIBRARY_PATH=/usr/local/cuda-9.0/lib64;\
apt-get -y install python3-dev;\
apt-get -y install libgraphviz-dev;\
pip install pygraphviz;\
pip install tqdm;\
apt-get -y install graphviz-dev;\
apt-get -y install pkg-config;\
apt -y install python-dev;\
apt -y install libxml2;\
apt -y install libxml2-dev;\
apt-get -y install python3-tk;\
pip install cairocffi;\
pip -v install python-igraph==0.7.1.post6;\
echo "backend: Agg" > ~/.config/matplotlib/matplotlibrc;

Hello, my run of S-VAE with your command without --bidirectional results in 99.98% recon accuracy, which aligns with the paper.

@muhanzhang My fault. Sorry. All works great

No problem. Thanks for checking the code!


[WIP] Hold Requests: Add Hold/UnHold MenuItem and API call

This task is reserved for agency.
Overflow Menu
In <MoneyRequestHeader, add a new Hold entry to threeDotsMenuItems with a clock icon.
When selected it should called the locally defined method holdMoneyRequest()
Lastly, this Hold menu item will only be conditionally rendered based on ReportUtils.isOnHold(moneyRequestReport) If so, render the 'Hold' text for the popover menu option, or 'Unhold' otherwise.
Holding a request (member & admin)
When holdMoneyRequest() is called after the user taps Hold in the Overflow Menu.
In the function, we'll check if ReportUtils.isOnHold(moneyRequestReport) evaluates to true where we will Navigation.navigate(ROUTES.getMoneyRequestHoldRoute( … )) to an interstitial for the user to provide a reason for the hold request.
Reason Interstitial
Under src/pages/iou, create a new HoldReasonPage where we'll capture the user-provided reasoning for the hold.
The structure of the page should should resemble the following:
<ScreenWrapper>
            <HeaderWithBackButton>
<Form submitButtonText={translate('iou.holdRequest'')}>
<Text>
<TextInput>
…

The key implementation details here to make note of are that:
The page is auto-focused when navigating to the page.
That error message is displayed after submission of an empty field for the reason.

When the user confirms the reason, we Navigate back to the MoneyRequestPage, passing the user-provided reason.
Back on MoneyRequestPage, fire off an API call with the following parameters:
API.write( 'HoldRequest',
{
	transactionID, // the money request being held
	comment        // the reason given for the hold
...
}

Onyx Data Response
Optimistic
{
    onyxMethod: Onyx.METHOD.MERGE,
    key: ONYXKEYS.COLLECTION.TRANSACTION,
    value: {
        [currentTransactionID]: {
            memo: {
                held: {
                    accountID: '<accountID>',
                    date: DateUtils.getDBTime(),
                    comment: ''
               },
            },
        },
    },
},

Success
API Onyx data response
Failure
{
    onyxMethod: Onyx.METHOD.MERGE,
    key: ONYXKEYS.COLLECTION.TRANSACTION,
    value: {
        [currentTransactionID]: {
            memo: {
                held: null
            },
        },
    },
},

Unholding a request (member & admin)
When the Unhold menu item is tapped, holdMoneyRequest() is called.
In the function, we'll check if ReportUtils.isOnHold(moneyRequestReport) evaluates to false. Unlike holding a request, no reason is required, so we can immediately fire off an API call like the following:
API.write( 'UnholdRequest',
{
	transactionID, // the money request being held
...
}

Onyx Data Response
Optimistic
{
    onyxMethod: Onyx.METHOD.MERGE,
    key: ONYXKEYS.COLLECTION.TRANSACTION,
    value: {
        [currentTransactionID]: {
            memo: {
                held: null
            },
        },
    },
},

Success
{
    onyxMethod: Onyx.METHOD.MERGE,
    key: ONYXKEYS.COLLECTION.TRANSACTION,
    value: {
        [currentTransactionID]: {
            memo: {
                held: null,
            },
        },
    },
},

Failure
Onyx data response

Succeeded by https://github.com/Expensify/App/issues/31300


Use off-the-shelf React Templates for UI

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Refactor

What is the current behavior? (You can also link to an open issue here)
Custom React Material UI Implementation

What is the new behavior (if this is a feature change)?
Off the shelf React Material Chat UI Implementation

Resolves #86 needs to be in the description, not the title to work. See https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue

Can we get rid of material-ui with this PR?

Sure, we can improve the look and feel and customize it and group them,
honestly I didn't realize we were planning on actually using it and was
trying to leave it with as little UI code clutter as possible and looking
as much as it did before by just replacing the custom stuff with the off
the shelf components.
I can group the messages by sender and in general make it a lot smaller,
and get rid of the bubbles; I misunderstood the goal to be more about
making a demo of how to integrate it than a demo we would use.
I can refactor the date function; I did try to remember to run the linter
before every commit; I'll refactor the JS->TS integration code, I was just
doing something to make it work for the demo, I'll try to match what you
have.
On Thu, Apr 29, 2021 at 2:55 AM Franck Royer @.***>
wrote:

@D4nte commented on this pull request.
I must say it looks good and it is an improvement on the current UX so I'd
be keen to merge even if it is not the slack/discord feel.
Can you make it so that messages from the same sender are automatically
grouped? This should help make it more condensed.

In web-chat/src/ChatList.tsx
https://github.com/status-im/js-waku/pull/95#discussion_r622660851:

interface Props {

messages: ChatMessage[];
}
export default function ChatList(props: Props) {
const messages = props.messages;

const listItems = messages.map((message) => (

 <ListItemText primary={<Message message={message} />} />

const listItems = messages.map((currentmessage) => (

<Message

 key={currentmessage.timestamp.toString()}

 authorName={currentmessage.nick}

 date={currentmessage.timestamp.toLocaleString([], {

Maybe best if we extract the formatting of the date in a dedicated
function to declutter.
In web-chat/src/MessageInput.tsx
https://github.com/status-im/js-waku/pull/95#discussion_r622661177:

+import {
Did the linter add this newline?
⬇ Suggested change

-import {
+import {

In web-chat/src/custom.d.ts
https://github.com/status-im/js-waku/pull/95#discussion_r622662877:

@@ -0,0 +1 @@

+declare module @.***/ui-kit';
To keep it consistent with js-waku, name the file types.d.ts and add it
to a types folder.
You probably also need to update the web-chat/tsconfig.json file with
"typeRoots": @.***", "src/types"]
like ./tsconfig.json.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/status-im/js-waku/pull/95#pullrequestreview-647745512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6HJBDN6PRYTDPXCUNSAO3TLCU7FANCNFSM43XO4JDA
.

Ah ok, sorry I'm more used to using JIRA than the built in Github issue
system (I'm also more used to using Jenkins than their built in CI)
Honestly I've been using Google cloud git and Gitlab a lot for the last
years.
On Thu, Apr 29, 2021 at 4:35 AM Franck Royer @.***>
wrote:

Resolves #86 needs to be in the description, not the title to work. See
https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/status-im/js-waku/pull/95#issuecomment-828902495, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6HJBD5F2EV322ROEVJTELTLDAYDANCNFSM43XO4JDA
.

Yes you are right, there are no more dependencies on Material UI, I'll
remove it
On Thu, Apr 29, 2021 at 6:17 AM Franck Royer @.***>
wrote:

Can we get rid of material-ui with this PR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/status-im/js-waku/pull/95#issuecomment-828928432, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6HJBBVLAMKDXEUR2TVXELTLDMWLANCNFSM43XO4JDA
.

Thanks for the replies!
Feel free to add a pre-commit hook to lint the code automatically.
Yes, removing bubble and grouping by sender would be great.
Indeed, I hadn't clarify the fact that we were also dogfooding the app (and it took me some times to remember why I wanted it condensed).
Again, the look is much better so I am excited to get this merged with those small tweaks.

No worries! We are on almost perfectly opposite times...you had plenty of
time to review everything while I slept. First thing in the morning with my
coffee is a good time for me to go over all this stuff.
On Thu, Apr 29, 2021 at 6:49 AM Franck Royer @.***>
wrote:

Thanks for the replies!
Feel free to add a pre-commit hook to lint the code automatically.
Yes, removing bubble and grouping by sender would be great.
Indeed, I hadn't clarify the fact that we were also dogfooding the app
(and it took me some times to remember why I wanted it condensed).
Again, the look is much better so I am excited to get this merged with
those small tweaks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/status-im/js-waku/pull/95#issuecomment-828936882, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AP6HJBF2KWKKLF4Y7JT4RA3TLDQNHANCNFSM43XO4JDA
.

I'll fix this stuff up and squash it into a single commit again, I can see how that's a good best practice to follow.
Should I leave "Resolves 86" off until I make it more condensed and just leave this PR as the intermediary refactor from Material to the Chat UI Toolkit?

I'll fix this stuff up and squash it into a single commit again, I can see how that's a good best practice to follow.
Should I leave "Resolves 86" off until I make it more condensed and just leave this PR as the intermediary refactor from Material to the Chat UI Toolkit?

It is fine if you want to get this merged first and then work on getting it more condensed in a second PR.
If that's what you prefer to do then yes, please remove resolves #86.

I'll fix this stuff up and squash it into a single commit again, I can see how that's a good best practice to follow.
Should I leave "Resolves 86" off until I make it more condensed and just leave this PR as the intermediary refactor from Material to the Chat UI Toolkit?

It is fine if you want to get this merged first and then work on getting it more condensed in a second PR.
If that's what you prefer to do then yes, please remove resolves #86.

I removed it and squashed everything into a single commit. I think the linter may have reformatted the tsconfig; I can revert that if you prefer, let me know.
I like to do smaller more atomic commits while I'm working but not too hard to squash them all into a single commit at the end.

Looks good, I'll take over

bors merge

bors merge


Why not support Azure Blob based volume driver?

May because Blob is not a virtual disc with file system engine, like File type.
I guess, to really use Blob, should have a mediator. with that emulate a file system engine and so, use it at Linux or Windows OS.


[Bug] Reave stages not increasing radius

I can't reproduce this. Note that you need to select the stage count for Reave in the Calcs tab itself (not the sidebar) for the radius calculation to change.

I see, but then what is the stage count in de sidebar for?

The stages are implemented using the program's skill part system. For most skills, different parts have different DPS, but Reave is one of the few exceptions; the skill part selector still appears in the sidebar anyway, despite not influencing the sidebar stats, because that's just how that system is designed.

All right, thanks


[MLIR] Disable CPU fusion tests in MLIR

CPU fusion is disabled in MLIR since fused ops are not supported in
nGraph dialect.

why only these few tests are disabled?

Because those are the only fusion ones failing for now with MLIR enabled. The rest seems to be passing.

Added cpu_debug_tracer, check_flow_with_external_function as well since it's failing because there CompiledKernel ops generated for MLIR are not expected


Ignore temp Hypothesis test things

https://github.com/DRMacIver/hypothesis
https://hypothesis.readthedocs.org

cc @DRMacIver

Seems eminently reasonable to me, yes. Checking these in is unlikely to ever be a good idea.

@shiftkey Hi, do you think this could be merged? Thanks!

Do you have a link to what this file represents and why it can be safely excluded from version control?

@shiftkey I couldn't find it documented in its docs https://hypothesis.readthedocs.org/en/latest/, but perhaps that's because it's for its own local temp stuff.

It's ignored by its own project: https://github.com/DRMacIver/hypothesis/blob/bb66deacc831426294d163ef3b69060df4b54104/.gitignore#L6
It's the home directory used for storage:
https://github.com/DRMacIver/hypothesis/blob/69f84cb31e09b88c609140ad5ec5c30439f8a8ba/src/hypothesis/settings.py#L51-L67
Which is used for caching:
https://github.com/DRMacIver/hypothesis/blob/d5de4a83cf768017556df80f3a5c4c21ce066ab0/src/hypothesis/internal/reflection.py#L337-L357

The project author @DRMacIver said earlier in this issue:

Seems eminently reasonable to me, yes. Checking these in is unlikely to ever be a good idea.

https://github.com/github/gitignore/pull/1516#issuecomment-100817707
If you need more, perhaps @DRMacIver can help.

@hugovk thanks! I just wanted some details to point to, because we often get people come back weeks/months/years after and want to understand a specific rule (or even challenge it).

You're absolutely right that having some documentation about this would be useful. I've created a ticket about that.

Thanks!


Add softDelete option

Phil Karlton said "There are only two hard things in Computer Science: cache invalidation and naming things".  I could not think of a better name than softDelete for the option described in #27.  Please feel free to rename it.

Thank you @Thrilleratplay for this PR, let me take a look and I'll come back you.

Here I am, sorry for looking at this too late.
I like the name you gave to the option and even its behavior seems to work very well.
Thank you for sharing your idea, this feature will be available in the next release!


0.3.5b9 Memory leak with MLX models

Using an mlx conversion of a L3.3 b70 model in 8bit, each request seems to cause an huge memory leak.  I've 33k context and each request uses around 10G of memory, which is roughly what the KVCache should be.  A load and reload resets the memory usage to 79G which is what I would expect given the model size and quant level.

Experiencing the same thing with 90B. Deleting history from context does not reduce memory footprint.
The moment first inference starts, memory usage starts to balloon and leak until it reaches 200+ GB (on a Mac Studio with 192GB) and engine eventually crashes.

Relevant comment here from the author of mlx-vlm:

https://github.com/lmstudio-ai/mlx-engine/issues/5#issuecomment-2560459040

Will be fixed

@coughmedicine2020 tried it, now it doesn't leak or OOM, but it has a new problem - inference keeps getting slower and slower, until it reaches multiple minutes per token, and just stops. Tested on llama 3.2 90B vision instruct. Tried with iogpu.disable_wired_collector enabled and iogpu.wired_limit_mb set to 180ish GB too (the model takes up about 160 with context and all).


Adjusting indentation to be consistent

This adjusts indentation across the board for consistency

/domain @Betterment/test_track_core

<<domainlgtm


Login

Add user login and user registration.

This is a nice register form, maybe we can get some ideas from there.  https://codesandbox.io/s/fr71m?file=/src/components/RegistrationStyles.js:1813-1833

@gwbischof, is it ready for review?

I think this is just off track. User registration is not in scope because the plan is to integrate with existing user management systems. Should we close?


Documentation missing

// .storybook/preview.js

import { withServer } from "storybook-mirage";
import { makeServer } from "../path/to/server";

// optionally pass the server creator function to the decorator
export const decorators = [withServer(makeServer)];

From the example in the readme, what exactly is makeServer supposed to be or look like?

Thanks for bringing this up @iyobo
I hope the updated README helps clear it up.


Add fallback to compile assets on start

To temporarily work around a bug in Docker which can stop the assets
container from being created during build. It should be rare that this
happens, and worst case this will just add a couple of minutes to the
deploy time.

merging...it's be nice not to have to rely on this.

I assume a load balancer upstream will correctly wait for this to be processed and becoming responsive to web requests before stopping old containers?

Yup.

On 19 Aug 2015, at 11:55, Marten Veldthuis<EMAIL_ADDRESS>wrote:
I assume a load balancer upstream will correctly wait for this to be processed and becoming responsive to web requests before stopping old containers?
—
Reply to this email directly or view it on GitHub https://github.com/zooniverse/Panoptes/pull/1286#issuecomment-132539744.


Request for help setting up bolt.new in a private AI environment

Hi,
I have worked for hours trying to get bolt.new to work with a Runpod instance and haven't come close.
I could really use some help getting bolt.new connected to a private AI. My research and development relates to making AI products and I do not want to feed it into the giant's maws.
I'll tip $50 for the help. Runpod doesn't have to be the provider. IF you have already set up bolt.new with a no-logs provider, please please contact me.
Discord: traflagar_17037 I am usually available sometime from 10AM to 7PM eastern.

I'll tip $75. Really need a hand with this from someone who has bolt.new running with a remote private AI provider.

You can find these settings in the environment settings. Use the custom `base_url` to access the custom model

@traflagar connect me on https://www.instagram.com/p_awan__kumar/
i can help you with runpod i have hosted there my bolt new project with ollama


Update deployer artifacts to brooklyn-0.9.0

Current coverage is 41.16%

Merging #288 into master will decrease coverage by -6.88% as of 449fea1

@@            master    #288   diff @@
======================================
  Files          215     361    +146
  Stmts         9009   13170   +4161
  Branches      1316    1656    +340
  Methods          0       0
======================================
+ Hit           4328    5422   +1094
- Partial        352     430     +78
- Missed        4329    7318   +2989

Review entire Coverage Diff as of 449fea1

Powered by Codecov. Updated on successful CI builds.


LB: edf by timer wheel

Commit Message:
Add an experimental edf scheduler powered by timer wheel.
Additional Description:
With the naive timer wheel the cost of pick/peek/add host is reduced.
Almost constant cost regardless of the number of hosts is tens or thousands.
No bias toward the earlier host because current_time_ is not bumped when adding new hosts except when the first host is added.
We move unweighted to udf if the timer wheel cost is acceptable.
The trade-off includes
RR is not that strict. All the entries in the same slot are FIFO when picking(but not adding). Could be mitigated by carefully select the per slot time range.
Sparse slots can hamper the performance. Can be mitigated by a hierarchical time wheel to handle a very low weight host.
Performance: wheel is the new and heap is the current. The parameter is the number of hosts.
Each iteration in the row runs 1 million pickAndAdd. The existing heap or priority queue implementation adds 15-20ms when the hosts are 8x.
------------------------------------------------------
Benchmark            Time             CPU   Iterations
------------------------------------------------------
heap/1            73.0 ms         73.0 ms           10
heap/8            89.0 ms         89.0 ms            8
heap/64            109 ms          109 ms            6
heap/512           130 ms          130 ms            5
heap/4096          151 ms          151 ms            5
heap/10000         158 ms          158 ms            4
wheel/1           71.5 ms         71.5 ms           10
wheel/8           70.6 ms         70.6 ms           10
wheel/64          70.7 ms         70.7 ms           10
wheel/512         71.4 ms         71.4 ms           10
wheel/4096        77.6 ms         77.6 ms            9
wheel/10000       79.9 ms         79.9 ms            9

Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

@lambdai see also https://github.com/envoyproxy/envoy/pull/14681 that @tonya11en is working on. Stepping back, we have had a lot of conversations recently about changes to EDF. Can you provide some background on where this change is coming from? I want to make sure we are all working towards the same goals.

@lambdai see also https://github.com/envoyproxy/envoy/pull/14681 that @tonya11en is working on. Stepping back, we have had a lot of conversations recently about changes to EDF. Can you provide some background on where this change is coming from? I want to make sure we are all working towards the same goals.

I am offline during the past month and I am catching up with the update...
This time wheel implementation is inspired by Hierarchical Time Wheels but non-hierarchical is showing great improvement on the dataset. See paper http://www.cs.columbia.edu/~nahum/w6998/papers/ton97-timing-wheels.pdf
I had a quick glance at @tonya11en's #14681 and I find that one work better if the weight is predefined.
This time wheel impl is more flexible on weight value set. Yet it's degrading if the weight set has outlier values...

I am offline during the past month and I am catching up with the update...
This time wheel implementation is inspired by Hierarchical Time Wheels but non-hierarchical is showing great improvement on the dataset. See paper http://www.cs.columbia.edu/~nahum/w6998/papers/ton97-timing-wheels.pdf
I had a quick glance at @tonya11en's #14681 and I find that one work better if the weight is predefined.
This time wheel impl is more flexible on weight value set. Yet it's degrading if the weight set has outlier values...

@tonya11en Thank you for the link! I read the implementation of IWRR. Yes, it's quite similar. If the timer wheel has only two slots, the timer wheel implementation degrade to IWRR, where the first bucket has the name "curr_weights_" and the next bucket is named "weights_".
So both implementation do RR if entries are in the same bucket, until the budget within the entry runs out.
The major divergence is how the budgets refill.
In IWRR, if a small double value weight (e.g 0.3 ) is decreased by 1, ideally it should be erased in next round instead refill it with 0.3. So weight = 0.3 acts exactly as weight = 1.
I am pretty sure you can add more states into per entry, but you will encounter the next thing: only part of the entries will be selected into the next generation of "curr_weights". To address these optimizations, the solution may get closer to the timer wheel.
Timer wheel maintains a smoother budget refill as was in the priority queue. Comparing to priority queue, it's always a small portion are selected as the next round, which is the next "non empty bucket". Not any operator<() is needed. (Half true, since there is a future pool which maintains the entries which have very large deadline)

@tonya11en Thank you for the link! I read the implementation of IWRR. Yes, it's quite similar. If the timer wheel has only two slots, the timer wheel implementation degrade to IWRR, where the first bucket has the name "curr_weights_" and the next bucket is named "weights_".
So both implementation do RR if entries are in the same bucket, until the budget within the entry runs out.
The major divergence is how the budgets refill.
In IWRR, if a small double value weight (e.g 0.3 ) is decreased by 1, ideally it should be erased in next round instead refill it with 0.3. So weight = 0.3 acts exactly as weight = 1.
I am pretty sure you can add more states into per entry, but you will encounter the next thing: only part of the entries will be selected into the next generation of "curr_weights". To address these optimizations, the solution may get closer to the timer wheel.
Timer wheel maintains a smoother budget refill as was in the priority queue. Comparing to priority queue, it's always a small portion are selected as the next round, which is the next "non empty bucket". Not any operator<() is needed. (Half true, since there is a future pool which maintains the entries which have very large deadline)

Could you update the benchmarks with the pathological weights, just so we can get a sense of the differences?

close for now


Grouping nodes by type

Is it possible to group multiple nodes by 'type':
{
"name": "node1",
"type": "user",
"metadata": {
"streaming": 1
},
"renderer": "focusedChild"
},
{
"name": "node2",
"type": "storage",
"metadata": {
"streaming": 1
},
"renderer": "focusedChild"
},
{
"name": "node3",
"type": "user",
"metadata": {
"streaming": 1
},
"renderer": "focusedChild"
}
"name": "node4",
"type": "department",
"metadata": {
"streaming": 1
},
"renderer": "focusedChild"
}
here node1 & node2 can be grouped and position at the left side, node3 at center & node4 would be at the right end.... It would be helpful if you can direct me on how to get this feature

This would be a great feature! It would definitely be something useful. You would have to make it a parameter to the layout functions and try to figure it out in the layout algorithm.

IMO, grouping should not be just made "by type". For example, I want my grouping to be done by, say, "node health" (normal/danger/warning, etc).

group by can be driven by field, like 'type' or 'node health' which user can decide and it can be supported by input argument

I support this feature. Our infrastructure has more than 2 layers, so it would be great to sort by experience, application, service, etc.


Publisher verification docs are misleading or incomplete

Describe the bug
Publisher verification docs are misleading or incomplete in their current state.
To Reproduce
Ensure that you are new to marketplace.
Steps to reproduce the behavior:

Go to https://marketplace.visualstudio.com/manage/publishers/<your-publisher>
Enter domain name in Verified domain and click save
Update DNS records and click on verify.
See your verification denied for reasons not listed in docs.
Follow up on provided email to be ghosted.

Expected behavior
A clear and concise description of the process to verify publisher in the marketplace docs.

Current Behaviour

Additional Context
The domain in the question does not serve any ads or malicious content and is open source.

@mohitsinghs We will verify your domain. Apologies for the issue, it got rejected because of human error.


chunk: simplifies flushPage

Codecov Report

Merging #1264 (7b11d19) into main (c39eeb0) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #1264   +/-   ##
=======================================
  Coverage   57.92%   57.92%
=======================================
  Files         126      126
  Lines       21475    21462   -13
=======================================
- Hits        12439    12432    -7
+ Misses       7513     7505    -8
- Partials     1523     1525    +2

Impacted Files
Coverage Δ

pkg/chunk/disk_cache.go
35.36% <0.00%> (+1.13%)
:arrow_up:

pkg/meta/sql.go
67.45% <0.00%> (-0.36%)
:arrow_down:

Continue to review full report at Codecov.

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


can this model do image to video ?

It would be awesome

yeah that would be so cool!

+1. This would be fantastic

Nope, and the official answer they have given is that they won't open source the image2video model:
https://github.com/THUDM/CogVideo/issues/88#issuecomment-2273572339


Fix log-rotation function (#331)

Issue #, if available:
#331
Description of changes:
Replaced this reference with self in function in setInterval().
The self was already defined in method The setLogRollInterval().
In setInterval() method, The this is reference to Global Window.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This change affects the Logger::download() feature, because The range to keep logs changes.

Looks like this never got a final approval, resolved merge conflicts and will get another person from the team to approve this.


New component tooltip

:tada: This PR is included in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ServerRequestCallTest.ShortDeadlineDoesNotCauseOkayFalse GRPC_POLL_STRATEGY=epollex

This test is currently flaking on master
Two recent failures:
a) https://source.cloud.google.com/results/invocations/fcb02e32-fe5d-45e3-8510-6f3e7050acc7/targets/github%2Fgrpc%2Frun_tests%2Fcpp_linux_opt_native/tests
b) https://source.cloud.google.com/results/invocations/bdd2eab4-05c4-4c43-b264-b8719c68fc26/targets/github%2Fgrpc%2Frun_tests%2Fcpp_linux_opt_native/tests

Still a known flake?

I don't see any results in the test failure history


add cross env

Hi!
i would like to add cross-env for windows env!
Hope you like it! :D

Oh, cross-env... OK, merging this. I will adjust in master.

Thanks! Really appreciated.


Properly use global this to export moment

Don't assume this is bound to the global scope in local functions.
Related to #1179
@Xotic750 you mentioned something about returns on every code-path. I didn't find such an option in jshint. Can you double check and maybe propose other jshint options we should enforce to make moment strict mode compatible?

This still happens with   "moment": "~2.10.3",
angular and babel es2015 in gulp

@fyyyyy  I can confirm that this still happens, even with 2.13.0 version. Is there a solution for this problem?

My solution was to get rid of bower :D
https://gofore.com/stop-using-bower/


Add a position length to Token

It will be useful if we end up merging tokens in a SynonymTokenFilter for instance.
The synonym should span over several tokens so that it can still matches a PhraseQuery
This functionality will be used in #314

[x] Add the property to Token
[ ] Add a new constructor in PhraseQuery to accept offset. (this will require updating PhraseWeight as well)
[ ] Fix the QueryParser to pass the position_length information and use the above constructor when building a PhraseQuery.

Sorry my guidance was sloppy. Your PR looks good. Contrary to what I wrote in the ticket description this does not impact the existing NgramTokenizer. (I edited the ticket description accordingly)
So the main client right now is #314. Before merging your change, could you fix PhraseQuery so that it handles position_length correctly?
Currently all terms are assumed to have a length of 1, so the constructor just takes a list of terms.
We need to introduce another constructor new_with_offsets which takes a list of terms and their respective position offset: &[(usize, Term)] They should be sorted by offset.
In most case, each token should take a length of 1 and the argument query should look straightforward.
&[(0, term_the), (1, term_three), (2, term_little), (3, term_pigs))].
This will be handful when we face tokens with a token_length larger than 1. For instance, afer introducing #314, we can get the exact same result set by running the query as
&[(0, term_the_three), (2, term_little), (3, term_pigs))].
Finally the QueryParser need to be fixed in order to use this new constructor. For instance, we will need to read the token length information from the analyzer and eventually use the new new_with_offsets construction

I have been looking at the code and am a little confused as to how the changes you suggested are supposed to work. To start with, PhraseQuery currently has a Vec<Term>. Wouldnt this have to be changed to Vec<(usize, Term)>, in which case the existing constructor will have to be changed right? Another alternative is to store the offset in Term.  Would that work?
I am also unsure of how the two new tasks are related to the original issue. The new tasks seems to be related to querying while the original one seems to be related to Indexing/Indexed data. Am I correct?

Yes. You need to add another constructor. The older one calls the new one.
Finally the code in the query parser need to be modified to call the new
constructor.
Le lun. 23 juil. 2018 à 7:56 PM, Vignesh Sarma K<EMAIL_ADDRESS>a écrit :

I have been looking at the code and am a little confused as to how the
changes you suggested are supposed to work. To start with, PhraseQuery
currently has a Vec. Wouldnt this have to be changed to Vec<(usize,
Term)>, in which case the existing constructor will have to be changed
right? Another alternative is to store the offset in Term. Would that
work?
I am also unsure of how the two new tasks are related to the original
issue. The new tasks seems to be related to querying while the original one
seems to be related to Indexing/Indexed data. Am I correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tantivy-search/tantivy/issues/291#issuecomment-407018803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-WQiEPR2kLn5TR-xF_mu5uINA_A9hCks5uJavlgaJpZM4T0GGH
.

The change concerns analyzers and the nature of the tokenstream.
It impacts both search and indexing.
With this change PhraseQuery are broken.
In the selective ngram ticket when indexing our tokenizer will emit the
following tokens for "the three little pigs".

"the three"
"the"
"three"
"little"
"pigs"

This makes it possible for us to handle any PhraseQuery. The tokenizer will
just behave a tad differently.
If someone searches for "three little" we will search for [(0, three
little)]
If someone searches for "the three little pigs" we will benefit for our
extra token by searching.
[(0, "the three"), (2, "little"), (3, "pig")]
Le lun. 23 juil. 2018 à 7:56 PM, Vignesh Sarma K<EMAIL_ADDRESS>a écrit :

I have been looking at the code and am a little confused as to how the
changes you suggested are supposed to work. To start with, PhraseQuery
currently has a Vec. Wouldnt this have to be changed to Vec<(usize,
Term)>, in which case the existing constructor will have to be changed
right? Another alternative is to store the offset in Term. Would that
work?
I am also unsure of how the two new tasks are related to the original
issue. The new tasks seems to be related to querying while the original one
seems to be related to Indexing/Indexed data. Am I correct?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tantivy-search/tantivy/issues/291#issuecomment-407018803,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-WQiEPR2kLn5TR-xF_mu5uINA_A9hCks5uJavlgaJpZM4T0GGH
.

LGTM for the second checkbox. Can you do the last one or do you want me to take over it?
The idea is to modify the QueryParser to call the new constructor here.
https://github.com/tantivy-search/tantivy/blob/master/src/query/query_parser/query_parser.rs#L424
That requires modifying  LogicalLiteral::Phrase to have it carry offsets to, and compute the offset here:
https://github.com/tantivy-search/tantivy/blob/master/src/query/query_parser/query_parser.rs#L251
https://github.com/tantivy-search/tantivy/blob/master/src/query/query_parser/query_parser.rs#L177

I will give it a shot

Oops actually you might be right. I forgot in tantivy Token do not work with a position increment (like Lucene does). Instead they bear an actual position. I think you can work just from this position information. (the position length is still wanted though.)


[Bug] Can't start app

React Boilerplate
Before opening a new issue, please take a moment to review our community guidelines to make the contribution process easy and effective for everyone involved.
Please direct redux-saga related questions to stack overflow:
http://stackoverflow.com/questions/tagged/redux-saga
For questions related to the boilerplate itself, you can also find answers on our gitter chat:
https://gitter.im/mxstbr/react-boilerplate
Before opening a new issue, you may find an answer in already closed issues:
https://github.com/react-boilerplate/react-boilerplate/issues?q=is%3Aissue+is%3Aclosed
Issue Type

[x] Bug (https://github.com/react-boilerplate/react-boilerplate/blob/master/.github/CONTRIBUTING.md#bug-reports)
[ ] Feature (https://github.com/react-boilerplate/react-boilerplate/blob/master/.github/CONTRIBUTING.md#feature-requests)

Description
platform : linux-mint 18
after clone the boilerplate and run this command : npm run setup I get the following error :
(Add images if possible)

~/react-boilerplate-ssr-2 $ npm run start

><EMAIL_ADDRESS>prestart /home/saeed/react-boilerplate-ssr-2
> npm run ssr:generate

><EMAIL_ADDRESS>ssr:generate /home/saeed/react-boilerplate-ssr-2
> cross-env NODE_ENV=development webpack --progress --config internals/webpack/webpack.ssr.babel.js

sh: 1: cross-env: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>ssr:generate: `cross-env NODE_ENV=development webpack --progress --config internals/webpack/webpack.ssr.babel.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>ssr:generate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prestart script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!

Seems like cross-env is missing from your machine:
npm install --save-dev cross-env

npm 5 is not supported ATM, either downgrade npm or use yarn.


SNOW-751897: Snowpark should warn if the given warehouse does not exist

Please answer these questions before submitting your issue. Thanks!

What version of Python are you using?
3.8

What operating system and processor architecture are you using?

macOS-13.2.1-arm64-arm-64bit

What are the component versions in the environment (pip freeze)?

asn1crypto==1.5.1
attrs==22.2.0
black==23.1.0
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==2.1.1
click==8.1.3
cloudpickle==2.0.0
cryptography==39.0.1
exceptiongroup==1.1.0
filelock==3.9.0
idna==3.4
iniconfig==2.0.0
mypy-extensions==1.0.0
oscrypto==1.3.0
packaging==23.0
pathspec==0.11.0
platformdirs==3.0.0
pluggy==1.0.0
pycparser==2.21
pycryptodomex==3.17
PyJWT==2.6.0
pyOpenSSL==23.0.0
pytest==7.2.1
pytz==2022.7.1
requests==2.28.2
snowflake-connector-python==3.0.0
snowflake-snowpark-python==1.1.0
tomli==2.0.1
typing-extensions==4.4.0
urllib3==1.26.14

What did you do?

I created a session but had a typo in my warehouse name (I used "wh_A" but should have used "wh_B"). The session object was created successfully without any mention that the specified warehouse actually does not exist. The queries then went on to fail with this message:
Failed to execute query [queryID: 01aaa8e8-0505-c9cb-0000-xxxxxxxx] REDACTED
000606 (57P03): No active warehouse selected in the current session.  Select an active warehouse with the 'use warehouse' command.

The error message isn't super applicable in this context, I can write session.sql('use warehouse wh_B').collect() but that's probably not the desired user experience. Therefore, I think it would be beneficial for users if we logged a warning-level message if the given WH could not be found when the session is created.

This is a good feedback Jason. Our team will work on it soon.


Data Science with Python : Movie Recommendation Systems #1939

Description 📜
Made a video presentation on the topic of movie recommendation system.
Fixes #1939

Type of change 📝

[x] Video (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)

Domain of Contribution 📊

[x] Datascience with Python

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor.

Screenshots / Gif (Optional) 📸

@prathimacode-hub , Can you please evaluate the PR mam.

@prathimacode-hub , Mam can you please evaluate my PR , I made the changes.


how to define global font?

There is nothing about fonts in the light.js.
Is it possible to do that?

Just setting the font as a variable won't be of much help. We'll have to include the .ttf file separately for each custom fonts. So that is not something we're looking to support in the near future. However if you do need a different font, this article might be of some help.
<EMAIL_ADDRESS>

Thanks I know how to include and use custom fonts.
What I'd like to know is how to apply that font to all NativeBase widgets.

Provided you use all the <Text> components from native-base for your app. You can define the font-family in Components/Widgets/Text.js.

Oh ok, I was hoping there was a way to do that from the theme.
Maybe you could mark this as a feature request?

There is already a custom font request. Since we want native-base to work out of the box, we can have a font variable, but how do you suggest we deal with the problem of manually adding font files?

Same as #23

Including custom font is easy.

Create a fonts folder in the project root.

Add this to package.json

  "rnpm": {
    "assets": [
      "fonts"
    ]
  }

rnpm link

You already have a similar procedure when installing the react-native-vector-icons dependency without the need of modifying package.json so something cleaner could be achieved.

Sounds cool. Will try it out and hopefully publish it with our next release. Appreciate the help. Thanks!

@PierBover Doesn't seem to link the fonts in iOS (0.41), got another solution you're aware off?

@benjick no, sorry.


Prevent the development viewer, started with gulp server, from breaking completely in Private Browsing mode

Since attempting to access IndexedDB in Private Browsing mode in Firefox will throw an error, see https://bugzilla.mozilla.org/show_bug.cgi?id=781982, the development viewer fails to load.

Looks good now. Thank you!


Bar chart always uses the dimensional column as the sort order.

This isn't necessarily what is expected.  Maybe we should make an order_by option in the style..

I believe this is a dup of https://github.com/looker-open-source/malloy/issues/112 @anikaks


Bugfix-CS-37564

The set custom host and region command is not working for blizzard. Due to Regex checking, fixed that

@cs-raj There are some GitHub workflows failing in this PR, can you please fix those first?

Yes


[E2E] Torchbench hf_clip accuracy failed

🐛 Describe the bug
torchbench_amp_bf16_inference
xpu  eval  hf_clip
Traceback (most recent call last):
File "/home/sdp/actions-runner/_work/torch-xpu-ops/pytorch/benchmarks/dynamo/common.py", line 2512, in validate_model
self.model_iter_fn(model, example_inputs)
File "/home/sdp/actions-runner/_work/torch-xpu-ops/pytorch/benchmarks/dynamo/torchbench.py", line 439, in forward_pass
return mod(*inputs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 1110, in forward
vision_outputs = self.vision_model(
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 849, in forward
hidden_states = self.embeddings(pixel_values)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1736, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1747, in _call_impl
return forward_call(*args, **kwargs)
File "/home/sdp/miniforge3/envs/e2e_ci/lib/python3.10/site-packages/transformers/models/clip/modeling_clip.py", line 188, in forward
batch_size = pixel_values.shape[0]
AttributeError: 'str' object has no attribute 'shape'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/sdp/actions-runner/_work/torch-xpu-ops/pytorch/benchmarks/dynamo/common.py", line 4626, in run
) = runner.load_model(
File "/home/sdp/actions-runner/_work/torch-xpu-ops/pytorch/benchmarks/dynamo/torchbench.py", line 362, in load_model
self.validate_model(model, example_inputs)
File "/home/sdp/actions-runner/_work/torch-xpu-ops/pytorch/benchmarks/dynamo/common.py", line 2514, in validate_model
raise RuntimeError("Eager run failed") from e
RuntimeError: Eager run failed
eager_fail_to_run
loading model: 0it [00:00, ?it/s]
loading model: 0it [00:03, ?it/s]
Versions
torch-xpu-ops: https://github.com/intel/torch-xpu-ops/commit/1d70431c072db889d9a47ea4956049fe340a426d
pytorch: d224857b3af5c9d5a3c7a48401475c09d90db296
device: pvc 1100, bundle: 0.5.3, driver: 803.61

According to https://github.com/intel/torch-xpu-ops/issues/122, A100 also has this issue, @mengfei25 please double check it

A100 is also failed

close the issue, due to a100 also failed


Iphone 5/5s gyro drift

Hi
I'm using ComplementaryOrientation, from your sample (https://github.com/borismus/webvr-polyfill/tree/master/fusion)
But i have an error with iPhone 5/5S, gyro is drift.
If you were to place your phone flat and capture it's gyro-based position, then pick it up, rotate it a bunch, and place it flat again, its integrated gyro position might be quite different from what it was before.

This is not surprising. The problem complimentary orientation filter is
solving is not drift in general, but the visible drift caused by using the
magnetometer indiscriminately. In this case, you hold your cardboard still
and the world moves anyway.  See my blog post about it.
On Sun, Jan 24, 2016, 6:06 AM iRomano<EMAIL_ADDRESS>wrote:

Hi
I'm using ComplementaryOrientation, from your sample (
https://githubcom/borismus/webvr-polyfill/tree/master/fusion)
But i have an error with iPhone 5/5S, gyro is drift
If you were to place your phone flat and capture it's gyro-based position,
then pick it up, rotate it a bunch, and place it flat again, its integrated
gyro position might be quite different from what it was before
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/webvr-polyfill/issues/30.

Hi
I read your article: http://smus.com/sensor-fusion-prediction-webvr/
And i used fusion - ComplementaryOrientation, prediction.
Maybe I poorly explained my problem.
If you pick up the phone and rotate it, then put in the original value, the value of event.alpha is another.
I found the event: event.webkitCompassHeading
Maybe it used to calibrate?
Is ComplementaryOrientation support this event?

We do not currently have a fix for long term drift. It might be possible to
use the compass to help solve the problem, but it has to be done very
carefully since the magnetometer is notoriously noisy and unreliable. Even
in native cardboard sdk the problem is unresolved.
If you have ideas for solving the problem, please experiment with them and
send a PR to the polyfill :)
On Sun, Jan 24, 2016 at 9:05 PM iRomano<EMAIL_ADDRESS>wrote:

Hi
I read your article: http://smus.com/sensor-fusion-prediction-webvr/
And i used fusion - ComplementaryOrientation, prediction.
Maybe I poorly explained my problem.
If you pick up the phone and rotate it, then put in the original value,
the value of event.alpha is another.
I found the event: event.webkitCompassHeading
Maybe it used to calibrate?
Is ComplementaryOrientation support this event?
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/webvr-polyfill/issues/30#issuecomment-174400622
.

Sorry to bring up an old issue, but unfortunately it's still relevant.
I too am trying to solve the absolute drift issue (which is not only related to iPhones BTW).
In my research, I found that there are several available algorithms intended for 9DOF sensor fusion (EG Mahony, Madgwick).
I'm still trying to wrap my head around the math in these algorithms, but I had to wonder whether my efforts are futile.
Meaning - what was the reason that none of the available algorithms were chosen in implementing the polyfill?
Were they tested and found to be unsuitable? Too time-consuming to implement? Too processor intensive?
I believe that the answers might save some time in attempts to solve this problem.

Absolute drift is a hard problem. My experience with magnetometers in many phones is that they aren't reliable at all. The fusion in this project is pretty basic, but engineers on my team have spent a lot of time, and native implementations are more sophisticated.
They haven't quite cracked the absolute problem though. If you can improve on the sensor fusion in this project by fusing with magnetometer, very open to accepting PRs.

I implemented a solution using the new deviceorientationabsolute event, so it currently works only in Chrome for android (>50). For other devices, behavior will not change.
The basic idea is to have a second complementary filter step which fuses the calculated rotation quaternion with the rotation given by deviceorientationabsolute.
This takes care of the drift, but because the magnetometer is laggy, the user may see the scene moving even when her head is not moving. So to prevent this, I used an adaptive fusion factor which is equal to 0 below some radial velocity threshold.
This means that in the short term the user may experience yaw drift, but it should cancel out over time (assuming there will be some head movement)
I'm not sure that it's good enough for a PR, but in case someone finds it useful - it's available in my fork.


Trying to use this with Vue 2.

So i bumped Vue to beta 7 and vue-loader to 9.3.2 but i keep getting this warning and nothing is rendering
[Vue warn]: You are using the runtime-only build of Vue where the template option is not available. Either pre-compile the templates into render functions, or use the compiler-included build.
My small example is:
const App = {
  name: 'Test',
  render: h => {
    return (

Basic

<router-link to="/">/</router-link>

<router-link to="/foo">/foo</router-link>

<router-link to="/bar">/bar</router-link>

        <router-view />

    )
  }
}
const Home = { template: '
home
' }
const Foo = { template: '
foo
' }
const Bar = { template: '
bar
' }

const router = new VueRouter({
  mode: 'history',
  base: __dirname,
  routes: [
    { path: '/', component: Home },
    { path: '/foo', component: Foo },
    { path: '/bar', component: Bar }
  ]
})

new Vue({
  router,
  render: h => h(App)
}).$mount('#app')

I've also tried:
const App = {
  template: `

Basic

<router-link to="/">/</router-link>

<router-link to="/foo">/foo</router-link>

<router-link to="/bar">/bar</router-link>

      <router-view class="view"></router-view>

`
}
const Home = { template: '
home
' }
const Foo = { template: '
foo
' }
const Bar = { template: '
bar
' }

const router = new VueRouter({
  mode: 'history',
  base: __dirname,
  routes: [
    { path: '/', component: Home },
    { path: '/foo', component: Foo },
    { path: '/bar', component: Bar }
  ]
})

new Vue({
  router,
  render: h => h(App)
}).$mount('#app')

To no avail, it's doing my head in, i'm sure it's a simple fix :(

As the message suggests... read more here about the runtime only build.
Note you need to
To solve it you need to either add the following to your Webpack config:
resolve: {
  alias: {
    vue: 'vue/dist/vue.js'
  }
}

Or, make sure that all your components are defined in *.vue files, because they are pre-compiled.

Awesome thanks Evan, i think it was a combination of my files actually having errors in them as i was trying to get them in a minimal state i forgot i didn't have the store as well. 👍

This is a trap. I got in this trouble. so may you please improve the document ? add
Make sure that all your components are defined in *.vue files, because they are pre-compiled.

http://vuejs.org/guide/components.html#Local-Registration
The local registration not working if we do not change webpack configure. and i do not know where to change the webpack configure. would you please past a complete webpack configure file for me ? @yyx990803

@netroby
It's in the module.exports section:
module.exports = {
  entry: {
    app: './src/main.js'
  },
  output: {
    path: config.build.assetsRoot,
    publicPath: process.env.NODE_ENV === 'production' ? config.build.assetsPublicPath : config.dev.assetsPublicPath,
    filename: '[name].js'
  },
  resolve: {
    extensions: ['', '.js', '.vue'],
    fallback: [path.join(__dirname, '../node_modules')],
    alias: {
      'vue': 'vue/dist/vue.common.js',
      'src': path.resolve(__dirname, '../src'),
      'assets': path.resolve(__dirname, '../src/assets'),
      'components': path.resolve(__dirname, '../src/components')
    }
  },

remove 'common' and you're good

It appears for me that many-a-folks, having no idea, as to how to define a root component for runtime-only build, decide to use standalone. Which is not needed... As everything is compiled anyway.
So have a solution. Runtime-only and easy-peasy.
import Vue from 'vue'
import vmApp from './app.vue'

let app = Vue.extend(vmApp)
new app().$mount('#app')

@asvae could you provide an example of what's inside ./app.vue?

I thought there should be a lint tools. like vue-lint or some thing.
just check the grammar of app.vue and all other vue files

@tsankuanglee, sure. It's just a single file component. Or do you want to see the router config and stuff like that?

@tsankuanglee Here is a snippet.
import Vue from 'vue';
import VueRouter from 'vue-router';
import App from './components/App.vue';
import Home from './components/Home.vue';

Vue.use(VueRouter);

const router = new VueRouter({
    routes: [{
        path: '/',
        name: 'home',
        component: Home
    },
// .. others
});

const app = new Vue({
    router,
    render: createEle => createEle(App)
}).$mount('#app-container');

The browserify example helped me.

Thank you, @asvae and @cbess . That's what I use, but I've always put it under component so I was a bit unsure about this syntax: Vue(vmApp). This is cleaner. Thanks!

Memo for manually switch

Using Runtime + Compiler should be...

// src/main.js
...
new Vue({
  el: '#app',
  router,
  template: '<App/>',
  components: { App }
})

// build/webpack.base.conf.js
...
  resolve: {
    extensions: ['.js', '.vue', '.json'],
    alias: {
      'vue$': 'vue/dist/vue.esm.js',
      '@': resolve('src'),
    }
  },
...

Using Runtime-only should be...

// src/main.js
...
new Vue({
  el: '#app',
  router,
  render: h => h(App)
})

// build/webpack.base.conf.js
...
  resolve: {
    extensions: ['.js', '.vue', '.json'],
    alias: {
      '@': resolve('src'),
    }
  },
...

Simple way, change
import Vue from 'vue'

to
import Vue from 'vue/dist/vue.js';

It resolved my issue

@kensupermen Evan pointed out the solution which is to use an alias other than changing the import.
https://github.com/vuejs-templates/webpack/issues/215#issuecomment-238095102

@yyx990803 The alias doesn't work, vue is defaulted to the runtime es modules build. I suspect this might be on the module resolution side of things, because if one is using es modules and tree shaking, either webpack or vue will force require the es pkg.

If the config register alias doesn't work, this might be because you are using webpack merge to merge two configurations together. Webpack merge won't pick up resolve.alias

I'm pretty lost as to what the actual problem is here, but @thovt93's solution worked for me. I originally had import Vue from "../../../node_modules/vue"; and changed it to import Vue from "vue/dist/vue.js";.

@Meekohi
I can understand. At first glance, it does not make much sense. However, if you take your time and read the link Evan You posted, it should make much more sense.
Essentially, Vue.js ships with two builds:

Runtime only build
Runtime + compiler build.

The compiler takes care of converting template strings to render functions. If you're getting this error, it means that you're trying to use the runtime only build while having one or more string templates in your project.
If you don't have a compilation step (such as webpack w/ vue-loader) and wish to use string templates, just import Vue from 'vue/dist/vue.js' like you're already doing. There's nothing wrong with that.
However, if you do have a compilation step, you might benefit from converting all your string templates to render functions to remove the compiler overhead while using your Vue.js app. This can be done with webpack + vue-loader + only using Single File Components.
If you're unsure on how to render the root Vue.js instance without a string template, this might give you an idea:
`import Vue from 'vue';
import App from './App';
const app = new Vue({
el: '#app',
render: function (h) {
return h(App);
}
});`

@youfoundKim method you propose with render function for root components always gives me an error:
TypeError: Cannot read property 'matched' of undefined
    at render (vue-router.esm.js:69)
    at createFunctionalComponent (vue.runtime.esm.js:4051)
    at createComponent (vue.runtime.esm.js:4241)
    at _createElement (vue.runtime.esm.js:4411)
    at createElement (vue.runtime.esm.js:4348)
    at vm._c (vue.runtime.esm.js:4480)
    at Proxy.render (App.vue?./node_modules/vue-loader/lib/loaders/templateLoader.js??vue-loader-options!./node_modules/pug-plain-loader!./node_modules/vue-loader/lib??vue-loader-options:8)
    at VueComponent.Vue._render (vue.runtime.esm.js:4532)
    at VueComponent.updateComponent (vue.runtime.esm.js:2783)
    at Watcher.get (vue.runtime.esm.js:3137)

I have no idea why
"vue": "2.5.17",
"vue-loader": "15.2.6",
"vue-router": "3.0.1",

We've now completely removed rails-vue-loader and are just using webpack, but this error persists when using import Vue from "vue". When I break at the warning and look through the stack-trace, it's happening at:
var v = new Vue({ el: "#sidepanelAd", components: {'sidepanel-ad': SidepanelAd} });
which isn't using string templates (it's defined in a sidepanel_ad.vue file). Any suggestions for getting to the bottom of this issue?

@yyx990803

For those without webpack ( babel only ) and using vue-cli use the runtimeCompiler option.
https://cli.vuejs.org/config/#runtimecompiler
Create a vue.config.js file in your project root.
module.exports = {
    runtimeCompiler:true
}

Simple way, change
import Vue from 'vue'

to
import Vue from 'vue/dist/vue.js';

It resolved my issue

This fixed it for me (I'm working with Onsen) . Thanks a lot

@nsjames it solves the problem on yarn build but not on yarn serve. Is this as intended?

@laurensiusadi hmm not sure. It should do both.

Uncaught Error: Module build failed: SyntaxError: Unexpected token (10:24)
at Parser.pp$4.raise (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp$3.parseExprAtom (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1822:12)
at Parser.parseExprAtom (X:\vip\node_modules\buble\dist\buble.umd.js:656:26)
at Parser.pp$3.parseExprSubscripts (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1715:21)
at Parser.pp$3.parseMaybeUnary (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1692:19)
at Parser.pp$3.parseExprOps (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1637:21)
at Parser.pp$3.parseMaybeConditional (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1620:21)
at Parser.pp$3.parseMaybeAssign (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1597:21)
at Parser.pp$3.parseFunctionBody (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:2098:24)
at Parser.pp$4.raise (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:2221:15)
at Parser.pp.unexpected (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:603:10)
at Parser.pp$3.parseExprAtom (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1822:12)
at Parser.parseExprAtom (X:\vip\node_modules\buble\dist\buble.umd.js:656:26)
at Parser.pp$3.parseExprSubscripts (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1715:21)
at Parser.pp$3.parseMaybeUnary (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1692:19)
at Parser.pp$3.parseExprOps (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1637:21)
at Parser.pp$3.parseMaybeConditional (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1620:21)
at Parser.pp$3.parseMaybeAssign (X:\vip\node_modules\buble\node_modules\acorn\dist\acorn.js:1597:21)
at Parser.pp$3.parseFunctionBody

怎么解决

@nicaisa 發送配置

For those without webpack ( babel only ) and using vue-cli use the runtimeCompiler option.
https://cli.vuejs.org/config/#runtimecompiler
Create a vue.config.js file in your project root.
module.exports = {
    runtimeCompiler:true
}

thanks @nsjames ,it works for me.

verbose node v10.13.0
19 verbose npm  v6.4.1
20 error code ELIFECYCLE
21 error errno 1
22 error @ development: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
22 error Exit status 1
23 error Failed at the @ development script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

这个呢

需要文件

my god even init is shitty

For those without webpack ( babel only ) and using vue-cli use the runtimeCompiler option.
https://cli.vuejs.org/config/#runtimecompiler
Create a vue.config.js file in your project root.
module.exports = {
    runtimeCompiler:true
}

thanks @nsjames ,it works for me.

you help me save waste time

$ vue create mySample
does not even create webpack.config.json.
Should we create this explicitly?

It happened to me because I included at webpack.config.js some new alias without keeping the ones that Encore added. So I fixed merging the new with the ones that Encore builds with Lodash:
var config = Encore.getWebpackConfig(); config.watchOptions = { poll: true, ignored: /node_modules/ }; config.resolve.alias = _.merge(     config.resolve.alias, {         'sylius/ui': path.resolve(__dirname, 'vendor/sylius/sylius/src/Sylius/Bundle/UiBundle/Resources/private/js'),     });

What is the difference...
in package.json
  "browser": {
    "vue": "vue/dist/vue.js"
  }

in webpack.config.js
resolve: {
  alias: {
    vue: 'vue/dist/vue.js'
  }
}

Both produces identical build. Which one is good practice?
Nobody mentioned here but for bundlers like browserify or webpack should be used vue/dist/vue.common.js not vue/dist/vue.js because of common is in about 20kB smaller. Note that both vue/dist/vue.common.js and vue/dist/vue.js includes template compiler.

I had this issue once again during migrating to vue + typescript, the thing is during template-loader it was removing id="app" or could not mount it due to css modules did not work.

Now the "runtimerCompiler" has been updated to "runtimeCompiler"


Error when using Azuer App Service extension and deploy to an existing App Services in ASE from VSCode

Repro steps:

Install Azure App Services extension
Load or create ASP.NET Core project into VSCode
Use the extension to deploy to Azure existing Web App in an existing ASE

Action: appService.Deploy
Error type: ENOTFOUND
Error Message: getaddrinfo ENOTFOUND aseapp1.scm.mitedescase2.appserviceenvironment.net aseapp1.scm.mitedescase2.appserviceenvironment.net:443
Version: 0.14.0
OS: win32
Product: Visual Studio Code
Product Version: 1.34.0
Language: en

Call Stack
GetAddrInfoReqWrap.onlookup [as oncomplete] dns.js:50:26

Hi @tedescomicchidev,
Sorry that you're having issues.  Is this issue recurring?  Sometimes Azure has outages that are beyond our control, unfortunately.
Also, do you happen to know what your deployment source is configured to?

Hi - Where can I check the details for my "deployment source"?
Update: I needed to add the domain to the hosts file. Now at least I don't get an error, but the deployment goes on forever and never finishes. From the console I get:
7:51:47 AM aseapp1: Creating zip package…
7:52:04 AM aseapp1: Starting deployment…

Are you using a custom domain?  If so, have you set this all up in the portal?


Fix data races

Accidentally missed a couple places where we should be locking in: https://github.com/SiaFoundation/jape/commit/148b9cf36e120b2cc3398ab25af299fe165caa66

thanks @chris124567 for fixing this so swiftly 👍