Unable to Use Pcntl.php on Windows Server 2008 R2

Good evening,
I am trying to install Cachet on my Windows Server 2008 R2 box. Unfortunately, one of the PHP dependencies to run Cachet is 'pcntl.php', which is not compatible on Windows. This is to run 'Boris'.
Is there any way that the program could be changed to be compatible for Windows or there is an alternative .dll I can use that has the same effect? Do I need to run Boris to for Cachet to work or are there maybe some lines in the composer.lock file I can remove?
Thanks,
Theo.

Are you doing this under IIS?

@jbrooksuk No. Xampp.

Weird, since my colleague is able to run another Laravel app under Xampp with zero problems. It may be one of the dependencies (aside from Boris) is requiring it.

Skype? You can add me theo.bearman and we can try and work it out. According to my command line it's Boris.

I'm unavailable today, but could spend some time looking tomorrow night with you? Unless of course @GrahamCampbell has any ideas?

I'm not around tomorrow night I'm afraid. No chance you could have a quick peek now?

Unfortunately not, I'm afraid. I'm currently at work and no access to a Windows machine.

Labelled as "help wanted" though in case anybody can pick this up in the mean time.

This is a screenshot of my command line if it helps.

since this is a windows kernel problem, there is no easy way to solve this. we will have to replace this dep with an alternate one.

Actually, you could try out the L5 branch @TheoBearman, as I believe this doesn't use Boris anymore?

@jbrooksuk I'll give it a go now.

Ok. It has installed but now the php artisan migrate command isn't working.
This is the command line:

The env.php is made up of the following:
`<?php
return [
'DB_DRIVER'   => 'mysql',
'DB_HOST'     => 'localhost',
'DB_DATABASE' => 'cachet',
'DB_USERNAME' => 'cachet',
'DB_PASSWORD' => 'INTENTIONALLY BLANK',
];`

You need to create a database on your host called cachet (as taken from your config).

@jbrooksuk I have.

Ok, rather than using localhost, try <IP_ADDRESS> as the host.

Ah, sorry the config in L5 has changed. Check out https://github.com/cachethq/Cachet/blob/L5/.env.example

@jbrooksuk Ok, the .env.php file now contains:
APP_ENV=local
APP_DEBUG=true
APP_KEY=SomeRandomString

 DB_DRIVER=mysql
 DB_HOST=localhost
 DB_DATABASE=cachet
 DB_USERNAME=cachet
 DB_PASSWORD=secret

CACHE_DRIVER=apc
SESSION_DRIVER=file
QUEUE_DRIVER=sync

MAIL_DRIVER=smtp
MAIL_HOST=mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=null
MAIL_PASSWORD=null

And I am getting the same error.

You don't need the .php extension.

Ok, that worked. Now look at this....

You shouldn't install Cachet under a directory, can you move it to a sub-domain?

@jbrooksuk Not really no.

Unfortunately we can't really do much then as the whole system relies on not being under a sub-directory.

@jbrooksuk I'll look into it.

Not really no.

Laravel doesn't even support subdirectory installs officially anyway.

@jbrooksuk Got it working, thanks!.
You may want to put somewhere in the docs to use the L5 branch for setup instead of the master branch if you are using Windows Server.
Thanks so much.
Theo.

We'll be fully switching to the L5 branch soon anyway.

@jbrooksuk What about this now?

Currently undocumented (although explained in the blog post), is that the API is now versioned in the URL; https://status.theobearman.com/api/v1/incidents

Ok. Also, is there a way that I can change the links to direct to the ssl version. For example as by default it links to the http version

https://status.theobearman.com/auth/login
Everything is relative, so if you're on HTTPS, all links will follow HTTPS.

I am using Cloudflare Flexible SSL so the links to not follow HTTPS as default apart from on the status page which I have setup in Cloudflare.

I am using Cloudflare Flexible SSL so the links to not follow HTTPS as default apart from on the status page which I have setup in Cloudflare.

You haven't setup your trusted proxies correctly.

@GrahamCampbell Where do I set that up and what do I need to put in?

Something like this: https://i.starbs.net/NaO7.

@GrahamCampbell Can you send me that file? Where do I put it into my Cachet install?

@GrahamCampbell ?

It is actually within Cachet, https://github.com/cachethq/Cachet/blob/L5/config/trustedproxy.php

@jbrooksuk So I just have to update that file with the Cloudflare IPs from the screenshot above?

I believe so. They were up to date at one point. If you could make it a PR that'd be brilliant.

PR?

@jbrooksuk @GrahamCampbell In any case, I uncommented `'proxies' => '*', and the SSL issue has still not resolved.

Can you open this as a new issue please.


How to disable "The stdout and stderr logs"

This log file is created by default. I don't want to do that. How to disable this log file during running test. Please help.

Any particular reason these logs are bothering you?

When i'm running test, sometime it delay (about 10 seconds) and then continue running. I don't want to create that log file, unless i'm getting any error that I want to know.

I'm pretty sure it's the time the script waits for the app to install and launch, nothing to do with logs.
Try running test with --loglevel verbose to see exactly what happens while the script is halting.

Any news? Please provided the logs requested.


Adding Analytic Rules to Flare Solution

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

@jctaillandier / @v-atulyadav, adding this PR as the analytic rule is already approved in this PR

Looks good. Thanks!

Looking into this

Will provide an update on this ASAP.

Hi @v-sabiraj, please change status of rule.

I want the rule to be disabled by default upon solution deployment.

@jctaillandier, there will be issue in visibility of the rule as template if we make that value disable.

Hi @jctaillandier, please respond on @v-sabiraj comments. Thanks.

I cant push to this branch for obvious reasons, but I replicated here
https://github.com/Azure/Azure-Sentinel/pull/7420

Close this PR as @jctaillandier raised a new PR#(https://github.com/Azure/Azure-Sentinel/pull/7420) for the same.


Add color setting support to text formatter

This PR add a simple color change feature to the text formatter. All current default behaviours stays as they are. How to set up a different color map added to the examples/basic/basic.go.

I like the idea, but I think the implementation could be finetuned. I'm a bit bothered that you're making the colors public.

The color constants should be public because you are using them from your own main application.

How about keeping them private and having a SetLevelColor method:

Having to worry about a full color map is weird too. If I were to change the level colors, I would probably be changing a single one, where you require changing them all (possibly to the same) or nothing.

The SetLevelColor() method is a good idea - cleaner and easier for the users. Still i would keep the colors public to be able to use them.

Right now, we're only holding the list of colors we need as you can't change them.
But as we start implementing that, there might be requests of handling 256 colors range. Then, the public constants become a huge mess.
Furthermore, logrus is a logging library, not a terminal configuration one. Holding a full list of all bash color codes really seems superfluous.
I'd say that if you're trying to change those colors, you need to know about bash colors codes (we can put a link in the documentation about them) and can handle integers.

I reintegrated the master and added a func (f *TextFormatter) SetLevelColor(l Level, c int) method with example.
I still let the color constants public because in my opinion it is more conspicuous to have a small set of defaults for  inexperienced users in place. The color constants are only the basic ones and I see no reason why the should grow in this library.
But if this should be a "no go" i can change them back to private.

I'm sorry, but the more I think about it, the more I really don't think the colors should be public.
It's very easy to do so, but making them private later would be quite harder (as well as renaming them, if we change the default color for example).
Also, why do we still need to be able to set a full ColorMap?
The SetLevelColor method should be the only needed API.
Small changes are much better and more likely to be merged, as they are seen as less risky and much easier to maintain in the future.

Any further comments for this PR?

Sorry for the delay.
I'm trying to clear issues and PRs, and I'm still on the straightforward ones. So anything which isn't has less priority.


[Feature] Text Formula LOWER

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
Formula LOWER is not implemented
Solution
Implement formula LOWER
Reference https://support.microsoft.com/zh-cn/office/lower-函数-3f21df02-a80c-44b2-afaf-81358f9fdeb4

@jackpk235 :l can solve it


0.86.x it is not possible to connect with the Homematic IP cloud

Home Assistant release with the issue:
0.86.1 & 0.86.2
Last working Home Assistant release (if known):
0.85.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hassio
Component/platform:
https://www.home-assistant.io/components/homematicip_cloud/
Description of problem:
Sine 0.86.1 it is not possible to connect with the Homematic IP cloud for first integration. If I start to add the HmIP component I am asked for the serial number / Name /Pin. Normally afterwards a window should popup and ask for pressing the blue button on the access point. This window is missing and a error occur "Homematic Server not reachable".
Additional information:
Workaround: Confirm the S/N & Pin windows in parallel with pressing the blue button (repeatedly). This is time-critical and mostly needs more then one try.

Same issue here but workaround does not seemto work - subjective impression is that the abort server not reached error appears faster when pressing blue button - any news on this ?

If you push the blue button fast. You get a connection. But in past the assistant show a picture to push the button and wait.

It worked after 5 More attempts - glad to havve found the post here. Cheers

Duplicate of #20386?

Thanks for the help to connect - most elements work as I hoped - appologies if a follow-up question is missplaced, new here and could not find anywhere else:
is there a way to read the alarm state ?
Have a work around since Conrad Connect has a read out of the general alarm state - but would be a much more elegant solution to read within home assistant directly.
Thanks  Cheers

You can see the state in Entity  alarm_control_panel.external.
https://github.com/ciotlosm/custom-lovelace/tree/master/alarm_control_panel-card

Thanks for the quick response - I saw this and found how to arm/disarm the system with it - what I still do not see how it allows to read a triggered alarm - e.g. broken in in armed state - would like to have hue lights to react to a triggered alarm alongside the HomeMatic IP sireen


posted at doesn't automaically give you a timestamp

So, if I add a new post to mysite, I have to manually type in the posted at time.
Running the latest from master nova

Well, if you leave it empty it should get set automatically. But yeah, I agree it should be prefilled with the current time, too.

Getting Invalid Date on my posts as well.

I've made some changes to the postedAt field on Posts collection recently. I have no error posting/editing with a normal account and an admin account. How did you get an invalid date value?

I'm on the master branch. Funny thing is out of the 3 posts I've created, 1 actually has a date. I'm on the Sydney time zone which is GMT +10...

checked out the devel branch and ran npm install again, then now I have the the date field showing in the post edit page. Issue seems fixed...

Cool!


<EMAIL_ADDRESS>Attempted import error: 'withStyles' is not exported from '@material-ui/core/styles'.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Should not happen.
Expected Behavior 🤔

I'm not really sure, I think it should import withStyles from @material-ui/styles.
Steps to Reproduce 🕹

Steps:

Simply install @material-ui/labs and use one of the examples from https://material-ui.com/components/autocomplete/

Context 🔦

Use Autocomplete component.
Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: macOS 11.3
  Binaries:
    Node: 15.10.0 - ~/.nvm/versions/node/v15.10.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.5.3 - ~/.nvm/versions/node/v15.10.0/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
    Edge: Not Found
    Firefox: 89.0.2
    Safari: 14.1
  npmPackages:
    @emotion/react: ^11.4.0 => 11.4.0
    @emotion/styled: ^11.3.0 => 11.3.0
    @material-ui/core: ^5.0.0-alpha.36 => 5.0.0-alpha.36
    @material-ui/icons: ^5.0.0-alpha.15 => 5.0.0-alpha.37
    @material-ui/lab: ^4.0.0-alpha.58 => 4.0.0-alpha.58
    @material-ui/private-theming:  5.0.0-alpha.35
    @material-ui/styled-engine:  5.0.0-alpha.34
    @material-ui/styles: ^4.11.4 => 4.11.4
    @material-ui/system:  5.0.0-alpha.36
    @material-ui/types:  6.0.1
    @material-ui/unstyled:  5.0.0-alpha.35
    @material-ui/utils:  5.0.0-alpha.35
    @types/react: ^17.0.0 => 17.0.9
    react: ^18.0.0-alpha-e6be2d531 => 18.0.0-alpha-e6be2d531
    react-dom: ^18.0.0-alpha-e6be2d531 => 18.0.0-alpha-e6be2d531
    typescript: ^4.1.2 => 4.3.2

Closing, Autocomplete is no longer in @material-ui/labs, https://next.material-ui.com/components/autocomplete/ it's now on @material-ui/core/Autocomplete

This is because your dependencies don't match:

@material-ui/core: 5.0.0-alpha.36
@material-ui/lab: 4.0.0-alpha.58


oEmbed endpoint does not give html of embed

The "html" member of the response is not part of the OembedInformation class.

I have opened PR and it has been accepted. Issue should now be resolved.


Terminal dimensions aren't correct when zoom level is high

Repro:

Set window.zoomLevel to 2'
Try repro https://github.com/microsoft/vscode/issues/135804

Stale, work has happened in this area since.


useUtc not working correctly, thowing error

I tried to use useUtc but it's throwing an error.  If useUtc is enabled it should use getUTCMonth.
 if (result.getMonth() !== month) {
            throw Error(`Invalid date "${date}" for month with index "${month}".`);
        }

{
     provide: NGX_MAT_DATEFNS_DATE_ADAPTER_OPTIONS,
     useValue: {
       useUtc: true
     }
   },

 ERROR Error: Invalid date "1" for month with index "5".
    at NgxDateFnsDateAdapter.createDate (ngx-mat-datefns-date-adapter.js:95)
    at MatMonthView._init (datepicker.js:998)
    at SafeSubscriber._next (datepicker.js:891)
    at SafeSubscriber.__tryOrUnsub (Subscriber.js:183)
    at SafeSubscriber.next (Subscriber.js:122)
    at Subscriber._next (Subscriber.js:72)
    at Subscriber.next (Subscriber.js:49)
    at MergeMapSubscriber.notifyNext (mergeMap.js:70)
    at SimpleInnerSubscriber._next (innerSubscribe.js:10)
    at SimpleInnerSubscriber.next (Subscriber.js:49)

Thanks! Seems like a bug. I'll look into it and make a fix.

A PR has been opened for this: #16


Fd test rebase

ForwardDiff's compile time has become really slow, but the next version of Optim depends on upgrading ForwardDiff.  This PR removes ForwardDiff from the main inference by using analytic derivatives for the KL divergences.  It also factors out the ForwardDiff-based tests into a separate file which is only run optionally.

Looks like a merge gone bad...some << characters in the commit perhaps?

Don't merge this yet.  The rebase re-added some tests that I had removed.  I think an interactive rebase after a merge (of your recently committed PR) may not actually be so slick.

Rebase once more? Or we can just start doing this in the future if you prefer, and just want to be done...

I rebased and tried to push, but it said
error: failed to push some refs to 'https://github.com/jeff-regier/Celeste.jl'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.

This makes sense, but I thought based on your previous comment that I could rebase and push like this.  Am I doing something wrong?

I'm not sure.... probably something about doing rebase to apply changes to
master to your branch. We can certainly wait until next time to worry about
keeping the history tidy. We might want to have a policy of only making
commits to master with passing unit tests. But please just merge this pr
whenever you're happy with it
On Thu, Aug 11, 2016, 3:07 PM Ryan<EMAIL_ADDRESS>wrote:

I rebased and tried to push, but it said
error: failed to push some refs to 'https://github.com/jeff-regier/Celeste.jl'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
This makes sense, but I thought based on your previous comment that I
could rebase and push like this. Am I doing something wrong?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jeff-regier/Celeste.jl/pull/267#issuecomment-239308394,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIieCxXkHAgiLfWV9RAgTHiAj3Z-8LTRks5qe50ogaJpZM4Jikyd
.


Add recipe_runs/register/{id} route

This PR adds a recipe_runs/register/{id} route which uses repository dispatch to invoke https://github.com/pangeo-forge/registrar, which in turn registers a recipe as a Prefect Flow with Prefect Cloud.
It is based on this example from Pangeo Gallery that @rabernat pointed me to for reference.

Yikes this commit history is not correct...


Update Building.md to mention how to build a release configuration

Building.md doesn't currently mention explicitly how to build in a release configuration.
This is largely fine, since very few people would ever want to build macOS or Windows in non-debug, since there are pre-built releases available.
However, for Linux users, where the only way to play the game is through compiling it yourself, having the default build type be debug is a footgun for poor game performance.
It would be nice to have an explicit note in Building.md as to how you can build the game in release, and that you should do so if compiling on Linux to actually play the game, not develop.
An alternate (possibly poor) idea would be to have the default build be release in Linux only, still defaulting to debug for non-linux builds. Users would then have to explicitly opt into a debug build in Linux, which might be a more reasonable behavior.
I'd make the PR to update it myself right now, but I'm both tired and busy so this issue is a note to myself to add it.

675508bb542268704e3a39d80fac9adeeee41808

@poco0317 That commit never made its way into master

An update has not released, thus nothing has been merged to master.


Add auth support for cluster

this needs a  freeReplyObject(reply); at https://github.com/vipshop/hiredis-vip/blob/e0f35f111b5c1b3413e664d4ea96a0b44cbe3ff7/hircluster.c#L2540-L2541 to prevent memory leakage

this needs a  freeReplyObject(reply); at
https://github.com/vipshop/hiredis-vip/blob/e0f35f111b5c1b3413e664d4ea96a0b44cbe3ff7/hircluster.c#L2540-L2541
to prevent memory leakage

Thank you for your suggestion. I have fixed this problem.


test: upgrade Chromedriver, troubleshooting Travis test failures

Jira
http://vjira2:8080/browse/BDS-2140
Summary
Attempt to fix intermittent build failures on Travis.
 Some failures point to a chromeDriver error. Try upgrading chromeDriver to latest stable version to see if it is the root problem.
How to test
master consistently builds successfully on Travis.

@colbytcook @remydenton @adamszalapski , I'm merging this PR unapproved into master to troubleshoot the failing Travis build. It's been difficult to debug, and I want to see if updating chromeDriver fixes other test failures. 🤞

PR was released with v2.24.0


Recording - Group Channel/ iOS - Retrieve number of members who haven't read a message

MembersUnReadMessageGroupChannel
Click ‘Create’ to create new group channel
Under ‘Choose member’, add users & select ‘OK’
Click on ‘Channel Name’ box to input channel name
Name channel ‘Holiday Party’
Click ‘Create’
Click ‘Holiday Party’ to enter conversation

Joyce: We should start planning our holiday party. Feel free to throw out any ideas!

Click on message above, show Message info & Unread By: users in the group channel

Ready

@justinbaldwin
https://drive.google.com/file/d/1qMkXsR165hN29aMnsGTZW8NmjLGcJhVc/view?usp=sharing

@chrischabot ready for review

@petru-gherghel please change the text to "Let's start planning our holiday party here!"

@justinbaldwin
https://drive.google.com/file/d/1lt2a3GaYcuwah_sYUSpgBAi0kKtCbYD1/view?usp=sharing

@michellewong27 @chrischabot
Ready for review: https://drive.google.com/file/d/1lt2a3GaYcuwah_sYUSpgBAi0kKtCbYD1/view?usp=sharing


#3438 Fixing search focus issue

… redirects to gallery
Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #3438
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried to respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

pay 50 usd


List members bindings

libxmtp supports listing group members, but we don't currently expose it in the bindings to FFI callers.

I see @nakajima already has this in a branch. Will assing to him.


Dev

Create new logic for table.yaml and suppression.yaml. And fixed bug for JSRunner.

@george-moberly ready


Not working with 223

Tried bumping the version which allowed it to load with no exceptions but doesn't seem to work

So it sounds like plugin is working but the language server/language server functionality is not. When you open a .jsonnet/.libsonnet file, does a green/red/yellow circle appear on your bottom toolbar? Ex:

Also, was it a bump to the plugin version or the language server version? The update feature for the language server binary itself can have issues but it would surface an error.

I guess it's more about the IDE verion.
Not compatible with the version of your running IDE (GoLand 2022.3.1)

I'm not even able to activate it:

My version:
IntelliJ IDEA 2022.3.1 (Ultimate Edition)
Build #IU-223.8214.52, built on December 20, 2022
Runtime version: 17.0.5+1-b653.23 x86_64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 13.0.1

223.* IDEs should be working with the new v0.0.10 release. The update should be available on plugin store tomorrow.

Hey ya'll. So v0.0.10 allowed the plugin to work in 223.* IDEs but the Jsonnet Language server wasn't being started (due to deprecation/removal of startup activity extension). v0.1.0 was released today which includes a change to use the new method for starting up/handling the language server. You can review the fix in this PR.
So far it's working for me on 2022.3.1 (build #GO-223.8214.59). So marking this one as resolved. I apologize for taking so long on fix. Feel free to reopen if it's not working for some 223.* version. And of course, any other problems please open up another issue.


Stub extensions.

@nipunn1313 can you take a look please? This is blocking us from typing our code using protobuf extensions.

Looks good! Thank you @pcorpet!. Sorry for the delay - I was out of town last week, but I'm back now.


ArgumentOutOfRangeException with multiple TagWith calls

var tag1 = nameof(QueryOnlyMultipleTagWiths);
var tag2 = "Second tag";

var query = _ctx.Friends
                .TagWith(tag1)
                .TagWith(tag2)
                .ToList();

Specifically when the second predicate is at the end of the generated SQL. The CmpStr method has a bug when startIndex + compare.Length is longer that sql and it returns true for endsWithAnd.
The above test case also exhibits another bug where the second predicate to be removed from the SQL is wrapped with parens: WHERE (N'!__tag!' == N'tag text') but the removal code doesn't take this into account and the resulting SQL contains W) in it.

Good catch, thank you for the pull request!

Thanks José!

Hi José, it seems the 1.0.3 NuGet package still has the old version of the code. If it's not too much trouble could you please make a new release with this bug fixed?
Thank you

Oops, sorry! I've just published the 1.0.4 package.
Please let me know if you find new issues.
Thanks for reporting!


Add initial cohort of Jupyter Distinguished Contributors

Adds the Distinguished Contributors section above the SC.

Not sure why I don't have a picture... let me know what you need :)

If you merge this, I can show my Dad. Otherwise, he won't believe me :)

Thanks everyone!


decouple core by entities

Coverage decreased (-1.8%) to 96.026% when pulling c7e2717c8d83b57089b9ab0851f72c0f4fbde3f0 on redesign into 7314522abc49acea931583e61b3d8a9a11d420a0 on master.


AWS Batch containerProperties.resourceRequirements as strings

Closes #4806
Seems like part of the cause was that the tests were building a containerProperties argument, but then discarding it. Maybe it was a git merge that went wrong some time in the past? Anyway, I've updated it so it actually tests what is intended - which failed as per the issue. Fixed that by coercing the fields to the appropriate types.
I've also removed the randomisation, so that the tests are deterministic and reproducible. It only covers one combination of vCPU and memory, but I think thats enough. Note that AWS Batch on Fargate uses partial vCPUs which might be a bit unexpected, so thats why it is testing 0.25 for vCPU via resourceRequirements.

Codecov Report

Merging #4809 (0486ad3) into master (bcf2eeb) will decrease coverage by 0.05%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master    #4809      +/-   ##
==========================================
- Coverage   95.09%   95.04%   -0.06%
==========================================
  Files         586      586
  Lines       62189    62487     +298
==========================================
+ Hits        59138    59389     +251
- Misses       3051     3098      +47

Flag
Coverage Δ

servertests
36.14% <14.28%> (-0.06%)
:arrow_down:

unittests
94.98% <85.71%> (-0.05%)
:arrow_down:

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

Impacted Files
Coverage Δ

moto/batch/models.py
89.23% <85.71%> (-0.22%)
:arrow_down:

moto/resourcegroupstaggingapi/models.py
83.66% <0.00%> (-1.47%)
:arrow_down:

moto/rds2/exceptions.py
96.92% <0.00%> (-1.08%)
:arrow_down:

moto/route53/responses.py
96.51% <0.00%> (-0.50%)
:arrow_down:

moto/sns/models.py
96.82% <0.00%> (-0.40%)
:arrow_down:

moto/sqs/models.py
96.75% <0.00%> (-0.18%)
:arrow_down:

moto/config/models.py
99.21% <0.00%> (-0.14%)
:arrow_down:

moto/ssm/models.py
94.21% <0.00%> (-0.12%)
:arrow_down:

moto/rds2/models.py
84.63% <0.00%> (-0.11%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Initialize Initial Frontend

Frontend: React + TypeScript + Vite + ShadCn
Rationale: Cant get ShadCn to work with React without Vite so need to reinitialize entire frontend

PS qx I imported all your frontend in 🥹

Current Structure of frontend
Assets: Image Gifs etc
Components: Custom (Plug and Play Components by yourself), UI (Components imported from ShadCn or some self-created components mentioned in shadcn documentation)
css: stylesheets (By right should split into multiple different css files but hey!)
lib: util and helper files (If you need to define any interfaces that is useful else where like iDictionary)
models: TypeScript models
views: Full page views
Some Additional Files i can think of for future addition
services: API services and logics
context: for state management (Speaking of which do we need redux for global state management kinda dw to pass context everywhere?)
store: If redux we put everything here
routes: Routing configurations
Currently Missing
Dockerfile

LGTM ! thanks for organising the entire frontend folder !!👍 big ups


Remove istio-egress from kubernetes quick start guide.

Fixed https://github.com/istio/istio.github.io/issues/792
/cc @rshriram

CLAs are in place.


How to locally build bootstrap-unlit?

I want to use the bootstrap-unlit Method 4b with custom colors.
How can I build it?
There is no gulp-task and if I change the sassSrc2 to unlit, I get an error because some files like variables-save-alt do not exist.

Oh.  Darn.  My fault.   I'd did a _* in my gitignore file and they were never committed.  Thanks for the spot - fixed now.

It works, thanks. Good work on the project ;)


Stack Trace is Truncated

:warning: The stack trace in IE11 is truncated to 1030 bytes, making this nearly impossible to use when you have a very long stack trace to comb through.
:warning: Even console.trace() outputs no more than 1031 bytes! That's so useless!

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

ID: a75dd21d-d850-a972-3fde-7db8fec9b02a
Version Independent ID: ffef8042-7b5a-0449-999c-ca8a6e9b72de
Content: stack Property (Error) (JavaScript)
Content Source: scripting-docs/javascript/reference/stack-property-error-javascript.md
Service: unspecified
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

Sorry for the delay. @Mikejo5000 you are correct in that the stack property is not a standard, so the overriding concern is interoperability with other implementations.
@liminzhu can comment on whether Chakra error.stack still exhibits this behavior. If it's just IE11, then as long as the limitation is documented, I think no action is required.

This behavior is gone in Edge/Chakra.


Added 3D Surface Plotter Calculator

@Rakesh9100
Fixes Issue🛠
#1245
Closes #1245
Description👨💻
Added : Plot 3D surfaces for given functions.
Inputs: Function definition in two variables (x, y).
Outputs: 3D plot of the surface, key points of interest (e.g., maxima, minima).
Type of Change📄

[X ] New feature (non-breaking change which adds functionality)

Checklist✅

[X ] I am an Open Source contributor
[X ] I have performed a self-review of my code
[ X] My code follows the style guidelines of this project
[X ] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

Pls work on these by making the new commits in this same PR @pandeyji711

Rename your folder to 3D-Surface-Plotter-Calculator and make the necessary changes.
Rename app.js to script.js.
Add a README.md file of your calculator in your folder.

@Rakesh9100 ok

Pls work on these by making the new commits in this same PR @pandeyji711

Rename your folder to 3D-Surface-Plotter-Calculator and make the necessary changes.
Rename app.js to script.js.
Add a README.md file of your calculator in your folder.

@Rakesh9100
I have done all necessary changes.

@Rakesh9100 This PR is reviewed & can be merged.


Make sure program information shows up on on WPNA records

On openvault2, neither the WPNA interview records nor the program records reflect the cataloging effort Leah vividly recalls. OV3 should capture this information.

@mccalluc @afred
I talked with Leah, and have taken steps to correct the metadata records.
Please close this ticket, or please give me permissions to close tickets in this repo.  Thanks!


Pack Untilize gives bad PCC when block_ct_dim < full_ct_dim

Describe the bug
for Conv unit test, block_ct_dim=1, full_ct_dim = 2, pack_untilize gives garbage PCC, when set block_ct_dim= full_ct_dim=2, PCC is good.
To Reproduce
Steps to reproduce the behavior:

Go to yugao/pack_untilize
Run pytest tests/ttnn/unit_tests/operations/test_new_conv2d.py::test_unet_conv_wh
To get rid of the PCC error, comment out the hard-coded out_subblock_h_ntiles = 1; out_subblock_w_ntiles = 1;  in
ttnn/cpp/ttnn/operations/conv/conv2d/conv2d.cpp

fyi @mywoodstock


server usage?

Hi,
I'm scoping riot for usage at my company and this is so far the best way i've seen to construct riot tags, however, we need to render on the server and I'm not seeing any example of server support. Can this be done?

I'm not acquainted with server-side rendering, but I guess in theory it should be possible.
Do you have any example to look at?

Here is a rather elaborate example which I found which accomplishes the whole "isomorphic/universal" javascript thing I'm after
https://github.com/ListnPlay/riot-isomorphic
You'll notice there's a tag factory which resembles what you have going in RiotTS, but it's less complete concept I believe.

related :
http://riotjs.com/guide/#server-side-rendering


Sdk3 path graph

I am playing around with this continuous graph vs. the discrete points.  I've tried to make it clean enough to merge, but it will make automated testing more difficult, so no hard feelings if this doesn't go anywhere.  I'd also be open to adding a config option.

Apples to apples:

Actually that's interesting.  It looks like I need to fix the light-weight dot line.  I'll fix that and update the PR.

Fixed.

When doing thought (and some code) experiments for a watch face that I was planning, I considered creating a PDC on the phone and pushing it to the Pebble in a message.  The PDC allows sub-pixel accuracy for points, which might be nice in a more compact display such as one where a larger time area showed dates or more pump status.

Looks good to me! One thing that jumps out is that the final point needs to make more obvious contact with the right edge of the graph; otherwise my brain is telling me there's missing data, so the "recency is obvious from the graph" heuristic breaks down.
As for automated testing, I don't mind running it through both aplite and basalt. Hopefully I'll get a chance to add screenshot diffing soon, so the process won't rely on manual inspection. At that point, the more coverage, the better. Have you tried running this through the test/do_screenshots.sh flow? For now you'll have to change test/util.py to make it run on basalt. I'm wondering how missing points will look; the fixed-width square points make it easy to see the extent of missing data.

Yeah, it could be very cool to create the PDC on the phone. My biggest concern is that you can't manipulate the graph on the Pebble to indicate when you lose phone connectivity, or accurately render the staleness of cached data when switching back to the watchface. Keeping all the staleness logic on the Pebble has made things easy to reason about, too. It may be worth sacrificing that for the flexibility of doing more in JS, like a log scale, dynamic bounds, and colors.
One quick win when the graph is more compact is choosing point width/height dynamically based on the bounds. Exposing layout options in the configuration page is the Very Next Big Feature, and then it will definitely be worth playing with some layout test cases to see where and how the graph can be made to look better.

You're right about the margin issue.  I'm just not sure how to extend the last few pixels.  Gaps work fine, but it needs to be over a bit more.  Any suggestions?

I could always shift the x coords over one and double the initial reading.

It turns out that nothing fancy needed to happen.  The collection-of-rects drawing addresses the left-most part of the box, while the path addresses the right-most point.  Changing GRAPH_POINT_SIZE * (1 + i + padding) to GRAPH_POINT_SIZE * (i + padding) fixes everything.

I personally prefer the collection-of-rects, but if you want it, I'm happy to include this as an option in the config page. I ran through the test suite and found two issues:
http://attorney-tailors-81503.bitballoon.com/basalt-not-smooth/screenshots.html
http://attorney-tailors-81503.bitballoon.com/basalt-smooth/screenshots.html
TestErrorCodes - points not showing up when there are discontinuities
TestTrimmingValues - looks like the y values are higher by 1 pixel (this could well be the result of a bug in my code, whose assumptions you're relying on)
I made a couple fixes to get tests running under Basalt. I still have to clean the tests up a bit to automagically run against both platforms, but for now you can override this line to get the same output as I gave above.
(Yay tests!)

I'm in the process of debugging Pebble's emu-app-config.  It hasn't worked for me since I experimented with some websocket clients.  I think I got a broken version installed.
I think the off-by-one-pixel problem is because the rectangles are specifying the edge of a region vs. the center of a line, which for a 3-pixel-wide line will be one pixel.  The missing points are a problem because a single point doesn't specify much of a line.  I'll have to think about what the right solution is to that because it isn't immediately apparent what the right thing to do is when there isn't any data.  Maybe isolated points should be small circles.  The other option is to interpolate a line, but I hate to imply data that isn't there.


Request for Classiq Final Assignment

PR Description

Some notes

[ ] Please make sure that you placed the files in an appropriate folder

[ ] And that the files have indicative names.

[ ] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[ ] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

Well done!
Score: 8/10


Make opening properties flyout simpler

Currently, the only way to open the properties editor for pipeline nodes is to right-click a node and select "Properties" from the context menu. Once the properties editor is open, single-clicking another node will switch to the properties editor for that node.
A few ideas to make opening the properties editor faster / more straightforward:

One idea is to open the properties editor on double-click. However, the pipeline editor currently opens the file that a node represents when that node is double-clicked, so it might be confusing to change that behavior for users.
Another idea is to open the properties editor on single-click (regardless of whether the properties editor is already open). This could cause issues if someone doesn't want the properties editor to be open (because of screen real estate) and they aren't able to easily keep it closed.
My suggestion: It could be good to have a toggle in the toolbar to open or close the properties editor. Then, if someone wants to quickly open the editor, it's as simple as clicking the toggle and single-clicking the node they want to edit.

@marthacryan I believe this issue is already resolved with the new toolbar button that opens properties?


Included writeup for Teams DLP E5 license enforcement

We need to mention the impact of E5 license enforcement that is planned to go live by end of week - 9/23. The new part is just a short description and the existing follow up link will provide more information.

Docs Build status updates of commit 6360366:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/dlp-microsoft-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@JohanFreelancer9

Docs Build status updates of commit 495899d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/compliance/dlp-microsoft-teams.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@JohanFreelancer9

@chrfox Please merge this PR. Thanks

@tanaybaldua - Hi, thanks for making this update.  We never publish guidance about what may or may not be coming in the future as dates and plans slip. Can you please re-write this to account for what the licensing/functionality is right now. Then when it does change, it can be updated.

Hi Chris, we have heard your views on the future plan and thus have decided to not have any update done on this page as Iicensing guidance is already present. I will come back to you in case we have to update anything else. thanks for time and support.


Select * from movie not working

I am using an alternate DB browser: https://www.etl-tools.com/database-browser/overview.html
I can see the tables and contents, for example, from oscar table:

But movie table is empty...
Correction if I run
select * from blu05.movie limit 1

Works. But some records have apparently a character that outputs an error, that comes up when reading with limit 100, for example:
"character with byte sequence 0xe6 0x91 0x87 in encoding "UTF8" has no equivalent in encoding "WIN1252""
Any clue?
Thanks

Seems related to this:
https://stackoverflow.com/questions/42130110/character-with-byte-sequence-0x9d-in-encoding-win1252-has-no-equivalent-in-enc

I can read it with pd.read_sql_query. The problem seems to be id = 30, that has Chinese or other similar chars...

The problem seems to be that the SQL client is trying to read the database data using the WIN1252 (encoding instead of UTF-8), while WIN1252 doesn't know how to handle Chinese characters.
You can check in the client's preferences if there is an option to select a different encoding.
If that doesn't work, or it seems too much time consuming, go ahead and do it all with pandas 🐼!

Works on Pandas :)


Rename Angular 1 to AngularJS and Angular 2 to Angular

hi @benvinegar

one of the diffs looks funky because I switched the file names:
angular.rst -> angularjs.rst
angular2.rst -> angular.rst

Looks good, but I think we should clarify that "Angular" is "Angular 2+" somewhere. The naming scheme is newly introduced and I'm not sure everyone will piece it together.

Looks good, but I think we should clarify that "Angular" is "Angular 2+" somewhere. The naming scheme is newly introduced and I'm not sure everyone will piece it together.

I added https://github.com/getsentry/raven-js/pull/928/commits/b43bcd99c876726a9f38acde5dcdffd735bd1707 and https://github.com/getsentry/raven-js/pull/928/commits/476e57588dd2edf8700e2c0059ce77764f71f91d to address this

These docs are pulled into Sentry using some convoluted scheme ... I just need to make sure changing the file paths won't mess something up otherwise lgtm.


Add instructions for authors for Strain and Variation sections

We want to capture genotype info for strains, variations, and transgenes, also species.
Add a sentence to explain to authors how to enter the  data:
Enter the strain name followed by genotype followed by species, separated  by comma.
e.g. PMD153, (vhp-1(sa366) II; egIs1 [dat-1p::GFP]), C. elegans
@draciti find a couple of examples for alleles, one CRISPR and a regular one
find also an example for transgenes

Text for New Alleles box:
e.g. dpy-5(e61), C.elegans
CRISPR alleles: e.g. bus-50(e5001[bus-50::gfp]), C. elegans
Text for New Strains box:
e.g. PMD153, (vhp-1(sa366) II; egIs1 [dat-1p::GFP]), C. elegans
Text for New Transgenes box:
e.g.: eaIs15, [Ppie-1::HIM-5::GFP::pie-1], C. elegans
@vanaukenk  please take a look.
A couple of questions:

In the proposal at the beginning of the ticket wa wanted to add a sentence such as: Enter the strain name followed by genotype followed by species, separated by comma.
Are we still keeping the sentence or shall  we simply put the example?
Do we need to check in with Paul D to see if the examples are ok? I took  the  allele examples from the WB  nomenclature page.
For transgenes do we want to include an extrachromosomal example as well?

Thanks

Thanks @draciti   These look good.
For the questions:

I'd keep the sentence; it could be helpful.  And maybe we should even write a sentence for alleles (and transgenes), e.g. Enter the gene name followed by the allele in parentheses; for CRISPR alleles, include the knock-in construct.  (If that makes sense).
We could always double-check with Paul D. just to make sure these look okay and maybe also to see if we need to update the WB nomenclature page to include CRISPR alleles.
Good idea - an extrachromosomal example, if curators will want them, would be good.

Writing the updated text here not to lose track, will also send to Paul D via email:
Text for New Alleles box:
Enter the gene and allele name followed by species, separated by comma.
e.g. dpy-5(e61), C.elegans
For CRISPR alleles include the knock-in construct, followed by species, separated by comma.
e.g. bus-50(e5001[bus-50::gfp]), C. elegans
Text for New Strains box:
Enter the strain name followed by genotype followed by species, separated by comma.
e.g. PMD153, (vhp-1(sa366) II; egIs1 [dat-1p::GFP]), C. elegans
Text for New Transgenes box:
Enter the transgene name followed by genotype followed by species, separated by comma.
e.g.: eaIs15, [Ppie-1::HIM-5::GFP::pie-1], C. elegans
For extrachromosomal arrays: sqEx67, [rgef-1p::mcherry::GFP::lgg-1 + rol-6], C. elegans

@valearna below the text suggestions, approved by Hinxton:
Text for New Alleles box:
Enter the gene and allele name followed by strain and species, separated by comma.
e.g. flu-4(e1004), CB1004, C.elegans
For CRISPR alleles include the knock-in construct, followed by species, separated by comma.
e.g. bus-50(e5001[bus-50::gfp]), C. elegans
Text for New Strains box:
Enter the strain name followed by genotype followed by species, separated by comma.
e.g. PMD153, (vhp-1(sa366) II; egIs1 [dat-1p::GFP]), C. elegans
Text for New Transgenes box:
Enter the transgene name followed by genotype followed by species, separated by comma.
e.g.: eaIs15, [Ppie-1::HIM-5::GFP::pie-1], C. elegans
For extrachromosomal arrays: sqEx67, [rgef-1p::mcherry::GFP::lgg-1 + rol-6], C. elegans

To discuss: ask to  specify species only for non elegans entities?
@valearna @vanaukenk

Also, do we want authors to add strains for the CRISPR alleles as well?

Instructions updated below:
Text for New Alleles box:
Enter the gene and allele name followed by strain and species, separated by comma.
e.g. flu-4(e1004), CB1004, C.elegans
For CRISPR alleles include the knock-in construct, followed by strain and species, separated by comma.
e.g. hmg-3(bar24[hmg-3::3xHA]), BAT1560, C. elegans
Text for New Strains box:
Enter the strain name followed by genotype followed by species, separated by comma.
e.g. PMD153, (vhp-1(sa366) II; egIs1 [dat-1p::GFP]), C. elegans
Text for New Transgenes box:
Enter the transgene name followed by genotype followed by species, separated by comma.
e.g.: eaIs15, [Ppie-1::HIM-5::GFP::pie-1], C. elegans
For extrachromosomal arrays: sqEx67, [rgef-1p::mcherry::GFP::lgg-1 + rol-6], C. elegans

As an author, I think I would find it easier if instructions were uniform, regardless of species.

Sounds good

Can Paul D implement a check to make sure entities will be captured correctly?
example, if an author does not include a strain
e.g. flu-4(e1004), C.elegans
Can  the script recognize that there is only one comma and output a warning  that one of the required fields is missing?
@Paul-Davis

@draciti I'm sure we can handle it

Enter the gene and allele name followed by strain and species, separated by comma.
e.g. flu-4(e1004), CB1004, C. elegans.
For CRISPR alleles include the knock-in construct, followed by strain and species, separated by comma.
e.g. hmg-3(bar24[hmg-3::3xHA]), BAT1560, C. elegans.

Change text:
Enter one transgene per line.  If possible,...
that applies to transgenes, strains, alleles explanatory text.
Also, New transgenes section C.  elegans should be italicized.

Looks good. Closing


Adds details about Docker Registry support

These details would be useful to operators looking to integrate their particular flavor of private docker registry.

Thank you, ryanmoran


Audio Not Working

I'm on an Acer C720. I recently attempted to use RetroArch, only to find out that it would not output sound. I then realized nothing else would output sound. I tried the update method under common issues, it did not work. I tried making another chroot with XBMC as the DE, because I knew that would have a menu that would output sound, in order to make sure the problem was with Crouton/the chroot itself, as opposed to RetroArch and my inability to work the music player that comes with LXDE. Rather than having its normal clicky sound effect, XBMC's menu sound effect was staticky. I then installed VLC and attempted to run audio. It worked at first, but when I changed the volume in VLC, the audio was horrible and staticky. After searching around for a solution, I decided to perform a powerwash and just do everything over again. Still, the problem persisted. I installed VLC, tried to play audio, and when I changed the volume, the audio turned staticky and horrible. Keep in mind, throughout all of this, Chrome OS played audio perfectly.
The current output of croutonversion is as follows:
crouton: version 1-20150730171703
release: trusty
architecture: amd64
xmethod: xorg
targets: lxde,extension
host: version 7077.111.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.1.11 #1 SMP Tue Jul 28 15:00:32 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

This might be Issue https://github.com/dnschneid/crouton/issues/1590

Not sure, might be....


Incorrect numbering in TAP reporter output.

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
~- [ ] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.~
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
I did some experimenting to see how mocha's TAP reporter deals with errors in before and after hooks. I was able to produce a test file in which the number of defined tests is 5, the number of reported tests on the # tests line in the TAP output (and also in the test plan) is 7, and the highest test ID in the output is 4. This seems incorrect. I'd expect all these numbers to be equal to 5.
Every version of the TAP protocol spec says that TAP data should not repeat test IDs, and suggests that those parsing TAP data should consider it a test error when this happens. This seems fine (but not ideal) where a before or after hook may fail and cause a test ID to be repeated to indicate the result of the test separately from indicating the failure of a hook. However, this shouldn't impact the total number of tests in the summary or in the test plan. In addition, this logic seems to be spilling over incorrectly to reduce the number of IDs to 4 when 5 tests are defined, and we can see them all having run in the TAP output.
Steps to Reproduce
Run this test.js file with mocha -R tap test.js.

test.js (click to expand)
describe('throwing before', () => {
  before(() => {
    throw new Error('bad')
  })
  it('works', () => {
  })
  after(() => {
  })
})

describe('throwing during', () => {
  before(() => {
  })
  it('works', () => {
    throw new Error('bad')
  })
  after(() => {
  })
})

describe('throwing after', () => {
  before(() => {
  })
  it('works', () => {
  })
  after(() => {
    throw new Error('bad')
  })
})

describe('throwing before and during', () => {
  before(() => {
    throw new Error('bad')
  })
  it('works', () => {
    throw new Error('bad')
  })
  after(() => {
  })
})

describe('throwing after and during', () => {
  before(() => {
  })
  it('works', () => {
    throw new Error('bad')
  })
  after(() => {
    throw new Error('bad')
  })
})

Expected behavior:

output (click to expand)
not ok 1 throwing before "before all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:3:11)
      at processImmediate (node:internal/timers:466:21)
not ok 2 throwing during works
  bad
  Error: bad
      at Context.<anonymous> (test.js:15:11)
      at processImmediate (node:internal/timers:466:21)
ok 3 throwing after works
not ok 3 throwing after "after all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:27:11)
      at processImmediate (node:internal/timers:466:21)
not ok 4 throwing before and during "before all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:33:11)
      at processImmediate (node:internal/timers:466:21)
not ok 5 throwing after and during works
  bad
  Error: bad
      at Context.<anonymous> (test.js:46:11)
      at processImmediate (node:internal/timers:466:21)
not ok 5 throwing after and during "after all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:49:11)
      at processImmediate (node:internal/timers:466:21)
# tests 5
# pass 1
# fail 4
1..5

Actual behavior:

output (click to expand)
not ok 1 throwing before "before all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:3:11)
      at processImmediate (node:internal/timers:466:21)
not ok 1 throwing during works
  bad
  Error: bad
      at Context.<anonymous> (test.js:15:11)
      at processImmediate (node:internal/timers:466:21)
ok 2 throwing after works
not ok 3 throwing after "after all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:27:11)
      at processImmediate (node:internal/timers:466:21)
not ok 3 throwing before and during "before all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:33:11)
      at processImmediate (node:internal/timers:466:21)
not ok 3 throwing after and during works
  bad
  Error: bad
      at Context.<anonymous> (test.js:46:11)
      at processImmediate (node:internal/timers:466:21)
not ok 4 throwing after and during "after all" hook for "works"
  bad
  Error: bad
      at Context.<anonymous> (test.js:49:11)
      at processImmediate (node:internal/timers:466:21)
# tests 7
# pass 1
# fail 6
1..7

Reproduces how often: 100% of the time.
Versions

The output of mocha --version and node_modules/.bin/mocha --version: 9.2.2
The output of node --version: v17.7.1
Your operating system

name and version: Linux 5.13.0-35-generic #40-Ubuntu SMP Mon Mar 7 08:03:10 UTC 2022
architecture (32 or 64-bit): x86_64

Your shell (e.g., bash, zsh, PowerShell, cmd): bash
Your browser and version (if running browser tests): N/A
Any third-party Mocha-related modules (and their versions): None
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version): None

I think this is all working as expected so closing as type: question. But I don't use TAP much myself and may be wrong. Please point out mistakes so we can re-open if they exist! 😄

I'd expect all these numbers to be equal to 5.

7 tests comes from 5 it tests + 2 failing afters. This is a "feature": a good number of users intentionally put assertions in after blocks, essentially making them an ancillary test to the original one.

Every version of the TAP protocol spec says that TAP data should not repeat test IDs ... a before or after hook may fail and cause a test ID to be repeated

Taking from TAP 14 specification:

Test Point IDs should be unique within the TAP Document. Harnesses may warn about repeated Test Point IDs or treat them as a test failure, but must not treat a Test Point with a re-used ID as a non-TAP line.

Per RFC 2119:

SHOULD   This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

It seems to me that the after blocks satisfy that "valid reasons" criteria here. The alternatives are:

Have after blocks always auto-increment Test Point IDs

Not desirable: would cause unexpectedly large numbers in test suites that use them for cleanup

Have after blocks only auto-increment Test Point IDs on failure

Not desirable: would cause in unpredictable numbers


Revert "GA release for NetworkTraversal (#26758)"

This reverts commit 61813fe0e600e4812ad0329a5e8a15db37efa36b.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API changes have been detected in Azure.Communication.NetworkTraversal. You can review API changes here


Finalization design #3

Makes as few decisions as possible and leaves everything up to the user.
Instead of having any direct finalization support, "simply" allows the user to stop collection at exactly the end of the marking phase and examine things.
Adds a finalize (indirect) method on Arena, and a new Finalization context which is currently Mutation but with two new powers:

The ability to check whether a GcWeak was "dead" at the start of the current finalization call
The ability to "resurrect" a GcWeak to preserve it this cycle (even without being upgraded and stored).

Entirely punts on ordering and queueing and leaves everything up to the user, BUT it is just powerful enough to implement finalizers and Java style ReferenceQueues and ephemeron tables and finalization ordering and many other things that parts 1 or 2 (or both) struggled with.

I have tested it in piccolo and am now using it to successfully implement Thread finalizers, so it seems to work pretty well!

Simplified API as per discussion on discord, we're just dropping the Finalization context entirely for now, it doesn't really add that much as is.
Other than that it's the same fundamental design which is still very simple.
At this point, the amount of actual meaningful code added is pretty small, it's mostly leaking a little more information and also a lot of new comments explaining things.

Undid some of the simplification for reasons outlined in the last commit message, which I'll copy here:

It makes documenting everything a little easier and prevents some misuses. When you call MarkedArena::finalize, you are examining the arena that WAS fully marked at the start of MarkedArena::finalize, and you know that in this state GcWeak::is_dead and GcWeak::resurrect have at least some meaning (that they were at least true at the beginning of the current MarkedArena::finalize call). Also, GcWeak::resurrect now always does something because we're always in the internal Mark phase.
The more important reason, it allows a user to protect against any resurrection funny business by a downstream user preventing access to MarkedArena. This is useful for libraries which want to provide a garbage collected arena but need to limit resurrection or at least control the precise order to maintain correctness.

This has been discussed to death so it's been agreed that it's time to merge this, we still have plenty of time to change the API again before another crates.io release.


Fix code climate badges [Test-Reporter]

Codecov Report

Merging #41 into development will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           development    #41   +/-   ##
==========================================
  Coverage          100%   100%
==========================================
  Files                9      9
  Lines              199    199
==========================================
  Hits               199    199

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 815d8ac...129cfc4. Read the comment docs.


Help required with the plugin and BlazeMeter - okHttp conflict error

I need help with below error. Issue is occurring when I am trying to to execute the test in BlazeMeter. Error is occurring only when JSR223 is used for scripting. Without JSR223, it is successfully writing data to influx dB.
Version:
JMeter 5.5
Java 11
2022-09-14 01:19:55,217 ERROR o.a.j.JMeter: Uncaught exception in thread Thread[StandardJMeterEngine,5,main]
java.lang.NoSuchMethodError: 'okhttp3.HttpUrl okhttp3.HttpUrl.get(java.lang.String)'
at retrofit2.Retrofit$Builder.baseUrl(Retrofit.java:506) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at com.influxdb.client.internal.AbstractInfluxDBClient.(AbstractInfluxDBClient.java:108) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at com.influxdb.client.internal.AbstractInfluxDBClient.(AbstractInfluxDBClient.java:79) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at com.influxdb.client.internal.InfluxDBClientImpl.(InfluxDBClientImpl.java:98) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at com.influxdb.client.InfluxDBClientFactory.create(InfluxDBClientFactory.java:261) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at com.influxdb.client.InfluxDBClientFactory.create(InfluxDBClientFactory.java:180) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at io.github.mderevyankoaqa.influxdb2.visualizer.influxdb.client.InfluxDatabaseClient.setupInfluxClient(InfluxDatabaseClient.java:148) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at io.github.mderevyankoaqa.influxdb2.visualizer.InfluxDatabaseBackendListenerClient.setupInfluxClient(InfluxDatabaseBackendListenerClient.java:257) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at io.github.mderevyankoaqa.influxdb2.visualizer.InfluxDatabaseBackendListenerClient.setupTest(InfluxDatabaseBackendListenerClient.java:178) ~[jmeter-plugins-influxdb2-listener-2.4.jar:2.4]
at org.apache.jmeter.visualizers.backend.BackendListener.testStarted(BackendListener.java:325) ~[ApacheJMeter_components.jar:5.5]
at org.apache.jmeter.visualizers.backend.BackendListener.testStarted(BackendListener.java:280) ~[ApacheJMeter_components.jar:5.5]
at org.apache.jmeter.engine.StandardJMeterEngine.notifyTestListenersOfStart(StandardJMeterEngine.java:218) ~[ApacheJMeter_core.jar:5.5]
at org.apache.jmeter.engine.StandardJMeterEngine.run(StandardJMeterEngine.java:396) ~[ApacheJMeter_core.jar:5.5]
at java.lang.Thread.run(Thread.java:829) ~[?:?]
Possible root cause is conflicting okHttp versions:

DEBUG Engine.s3downloader] objects for download: [s3.ObjectSummary(bucket_name='blazemeter-gcp', key='masters/64396587/tests/11513296/Notes_Spectre.jmx'), s3.ObjectSummary(bucket_name='blazemeter-gcp', key='masters/64396587/tests/11513296/jmeter-plugins-influxdb2-listener-2.4.jar'), s3.ObjectSummary(bucket_name='blazemeter-gcp', key='masters/64396587/tests/11513296/okhttp-4.10.0.jar')]

2022-09-14 01:19:28,392 INFO o.j.r.JARSourceHTTP: Downloading: https://search.maven.org/remotecontent?filepath=com/squareup/okhttp3/okhttp/3.10.0/okhttp-3.10.0.jar
2022-09-14 01:19:28,392 INFO o.j.r.PluginManagerCMD: Downloading okhttp...

Hi @roddasrinivas, wow will take a look. Have you reproduced this on the local PC?
BR,
Mike

Hello Mike,
Problem is on Blazemeter only. On local PC it is working fine. Is it possible to change okHttp jar version on plug-in? so there won't be any conflict between okHttp versions.
Best Regards,
Srinivas

The problem - I do not see any issues on local PC,  or any warnings with that. We have okHttp as part of the 'influxdb-client-java' used to push data to InfluxDB. Its Java world :)))

As you can see we have no okHttp as part of dependencies.
On some installations, we had a problem like you posted https://github.com/mderevyankoaqa/jmeter-influxdb2-listener-plugin/issues/16 (the solution was described in the ticket). The workaround is described.
I'm happy to help but I got stuck with that I have no env. to reproduce this.
BR,
Mike


Fix: make  Webhook resource-type subscription compatible

Webhooks are not compatible with Subscriptions since version 8.0.0
The current Webhook.php is missing compatibility for the resource type 'subscription'.
Here you can see on developer.paypal.com how a webhook can send this resource type:

The resource itself is structurally compatible with Subscription.php.
You can see this with this example JSON here:

I tested it with the changes below, and it works.
Before, the serializer would default the resource property to null.
Affected Versions
The changes need to be implemented for older versions as well. They should be applied to all versions from 8.0 onward.
I hope this information is sufficient.
Thank you for your work.

Dear Maintainers,
First of all, thank you for your continuous efforts in maintaining this project.
I wanted to kindly bring your attention to this Pull Request, which addresses compatibility issues with the Webhook resource-type subscription. This fix is quite important for us, as our Shopware plugin relies on it to function correctly. Without this update, our plugin may not work properly.
We understand you might be busy, but we would greatly appreciate it if you could review this pull request at your earliest convenience.
Thank you very much for your time and consideration.
Best regards, Riccardo Neutag

@Neodraccir It's merged, thanks for your contribution :blue_heart: :tada: Just be aware that we're not releasing it right away.


added-war-convo-bg-and-glasses-interactions

im not sure if im using pull requests correctly but is this okay?

oh also this is the bg image


SCICD-702: Bootprep Summary

Provide a summary of the bootprep commands that were run.  This allows a user to be able to re-run the commands without having to run iuf.

it would be good to add the sample output to the PR description


[fb-package] Improvements in speed and clarity to contingency pipeline

Description
Decrease memory usage by filtering out low-sample size groups before aggregations are produced.
Changelog

Create megacounties and for all geolevels drop too-small groups before aggregation step. Reduces resource use when spawning threads.
Replaces bracket filtering with dplyr::filter for speed and intuitive handling of NAs

Changes originally introduced here were separated out into #952 and #934 for shorter and more focused PRs.


Page refresh nukes the current user

I want to be able to survive a page refresh meaning that the user will remain logged in.
For some reason this does not work, have I missed something?

Yes, you most likely missed sth.
Please post questions like this on stackoverflow.com and if you actually find a bug in the library open an issue and make sure you include enough information so that people can reproduce the bug and eventually fix it.

Ok, I've made a fresh install using ember-cli and the latest ember-simple-auth, copy-paste the dummy app, and when I refresh, I need to log in again. Whats the catch?


chore(ci): re-enable storybook, remove experimental

Re-enable CI deployment for React storybook. This should be merged in after a v6 route is setup.
TODO

[ ] v6 route for React is setup and published with v6 codebase

v6 published using the v6 branch at: http://v6-react.carbondesignsystem.com


Determine what to do with cross-apphosts in installer MSI builds

When building SDK installers on x64 or x86, the apphost from arm64 and x86/x64 (alternate arch) are included. This won't be possible to do as-is in the VMR build, as those are built in different legs. This will require a build at the join point. There is some conjecture these can simply be removed, as they are for C++/CLI support when C++/CLI didn't support PackageReferences.

/cc @ViktorHofer @jkoritzinsky @marcpopMSFT

Part of #3739

Note that package reference support is still not enabled by default for cppcli apps. If it were ever added, we could probably remove these as it would be able to download the app hosts by default. Note that all SDK tests today for cppCLI enable package reference support in the tests in order to download the apphosts in the test run (as the stage 2 and stage 0 runtimes don't match). @olgaark for plans around cppcli projects


Offline.options + AMD

Offline.options can now be defined before including offline.js
setTimeout(init, 0) trick is not working using AMD so it will be particulary usefull in this case

can you rebase this off master so we can merge this in?

it should be ok

sorry but can you do it again, the transpiled javascript file is annoying.

is it ok for you ?

yea looks good


Element behind is overlapping react-modal

Summary: Part of the element from the background is overlapping even if react-modal is present.
I'm using react-dates from Airbnb and part of the component of the calendar such as navigation button and help button (green question mark) is overlapping even when the react-modal is presented. Everything else works fine.
Does anyone have an idea why this is happening?

There may be a better solution by the package author, but you could set the z-index style on the overlay. You can put something in your CSS like:
.ReactModal__Overlay {
    z-index: 1000;
}

That worked for me. Let me know how it goes.

Hi @matthew-matvei , thank you so much for the solution. It was really silly of me for not thinking to modify the z-index. Definitely appreciate the quick fix to the problem.
Would also be curious to find out what was the root cause to the problem as I'm relatively new in React development. Thanks again!

No worries.
Apparently, React decides Z-index based on the component's order in the render tree. Given that it's likely you'll have other components down the line from where the modal is placed, I guess you'll probably have something overlapping by default (unless there's something else we've both neglected ;-) )

@darylong is this a fix for your issue? If so, you can close this.
@matthew-matvei Thank you!

@diasbruno no worries!

Yes the issue is now fixed thanks to @matthew-matvei. Will be closing now, thanks!

There may be a better solution by the package author, but you could set the z-index style on the overlay. You can put something in your CSS like:
.ReactModal__Overlay {
    z-index: 1000;
}

That worked for me. Let me know how it goes.

It also worked for me! Cool!

Managing the z-index is not something package should handle...It would be completely speculative to know the right option for all projects, so...better handle on a project basis.

Also, this only happens on projects that already messed with the default DOM layering, or, have particular needs to manually handle layering.


Replace legacy logo with latest that taked from official webui-logo repo

Replace legacy logo that might cause a legal issue with latest was placed in webui-logo.
All list of repos that affected by this issue: https://github.com/webui-dev/deno-webui/pull/48 , https://github.com/webui-dev/website/pull/30 , https://github.com/webui-dev/python-webui/pull/20

Weird -- Github only shows a deletion, but then shows 0 lines have been deleted or added 🤔.

If I am correctly understood behavior of git, git will not count non-text file (like a image) changes as lines. So it's showing no deletion/addition.


[Feature request] Dynamic splitfuse from Deepspeed (2x throughput)

Hi, putting this here:
https://github.com/microsoft/DeepSpeed/tree/master/blogs/deepspeed-fastgen
The latency & throughput increase is significant though the comparisons are against vLLM. It seems like TRT does batching a bit differently so unsure if this can equally apply here.

Hey @0xymoro Thanks for sharing!!
Yes, splitfuse is an impressive advancement from Deepspeed, one we were also working as well! Our implementation will be a little different due to difference in batching strategies, but the idea of chunking the prefill is the same! Likely will land in the next few releases.

Hey @0xymoro, Chunked attention is now part of v0.7.1! We're still working on an example so I'll leave this open until that's done!

Hi @0xymoro !, Chunked context will be part of TensorRT-LLM v0.8. Thank you for your support!

Hi @0xymoro ! Chunked context will be part of TensorRT-LLM v0.8. Thank you for your support!

Hi, @Shixiaowei02 Thanks for your great job! How can i use Chunked context in TensorRT-LLM? Is there any docs?


[marketplace] Add time-to-live to stored blocks as part of a request

Blocks stored as part of a provider's storage request need a ttl on the blocks so they are not deleted, as per https://github.com/status-im/codex-research/pull/161.

This should already be part of the functionality - https://github.com/status-im/nim-codex/blob/main/codex/stores/blockstore.nim#L47-L54, the repostore already support this out of the box.