[Bug]: jest-resolve doesn't read "exports" field

Version
27.5.1
Steps to reproduce
In packages/jest-resolve/src/defaultResolver.ts, jest search only for "main" field to resolve package without checking if a "exports" field defines which file to read. This is different than what Node.js does to resolve package. This cause problems when a module is "type:module" and has a "exports->require" to be able to use it in a CommonJS file.
Here is the relevant part of packages/jest-resolve/src/defaultResolver.ts
  return function packageFilter(pkg, packageDir) {
    let filteredPkg = pkg;

    if (userFilter) {
      filteredPkg = userFilter(filteredPkg, packageDir);
    }

    if (filteredPkg.main != null) {
      return filteredPkg;
    }

    const indexInRoot = resolve(packageDir, './index.js');

Expected behavior
Follow Node.js behavior
Actual behavior
Module foo is a commonjs module. It uses require('bar'). Module bar is a ES module:
{ "name": "bar", "type":"module",
   "main": "index.js",
   "exports": {
     "import": "index.js",
     "require": "index.cjs"
   }
}

Jest reads bar/index.js instead of bar/index.cjs
Additional context
No response
Environment
Linux Debian/sid

Duplicate of #9771.
Fixed in Jest 28


No notifications when someone leaves the workspace

Looks like this broke recently.  I only see notifications when people join the workspace, not when they leave.

This isn't broken anymore.


How make stream public but not config ?

I would like see the stream through internet without password, for example with cam_pic_new.php or min.php,
But I don't want that anybody can change any settings.
How can do that ?
Set the password at install or reinstall, is set for all access, stream include... :-(
Any help ? Thanks a lot.

You can set different views including the one with no access to settings via the user access levels described in the wiki.
Normally this is controlled by the user logging on to get a particular type of access, so one could have a general user / password with just the minimum view.
If you have one login for full access then any unknown user gets minimum access.

pbenaim,
I make web page with two acces : only view and view + setttings protect !
If you want it i can give you

Yes Please :-)
Merci Didier

give me some contact facebook/discord/mail, how you want and i send it
And after you can close this post (:
Tu es francais ?

If you think this is generally useful then please add a link to the change to the wiki or if it is an alternative index page then I could maybe add it into the distribution so that people could use it more easily.

It's juste alternative page index, is not really secure i haven't experince for do this ! you can see here : charlesrpi.ddns.net

give me some contact facebook/discord/mail, how you want and i send it
And after you can close this post (:
Tu es francais ?

Oui, Français 👌
But I don't want share here one way to contact me. Spam care 😒
Any other option?

sur discord c'est AngryDidierMasse#6899

@roberttidey Go see to charlesrpi.ddns.net:8000 and say me if you want it ( with theme personalisation :p )


Unable to install

Got this error below:
$ yarn global add @wcfactory/cli
yarn global v1.16.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.2.tgz: Request failed "404 Not Found"".
info
The issue below states that the 5.1.2 package was removed by the author and that there is a 5.1.3 package now
https://github.com/yarnpkg/yarn/issues/6690
I am going to try to do a pull request to see if I can fix this.

I anxiously await your PR

I obviously don't understand something that is occurring. I was able to install all of the dependencies individually, but still can't install the wcfactory. It seems like there is a problem with the wrong version given from a transitive dependency. More digging to come

I had to edit my yarn.lock file which was in ~/.config/yarn/global . It now says
<EMAIL_ADDRESS>  version "5.1.3"   resolved "https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.3.tgz#1ef89ebd3e4996557675eed9893110dc350fa080"   integrity sha512-sNvOCzEQNr/qrvJgc3UG/kD4QtlHycrzwS+6mfTrrSq97BvaYcPZZI1ZSqGSPR73Cxn4LKTD4PttRwfU7jWq5g==   dependencies:     ajv "^6.5.5"     har-schema "^2.0.0"
Problem solved


Fix OVTrainer for transformers >= v4.29.0

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Flushing Process.stdin causes Dart to exit without any message

@christopherfujino
Reproduction:
import 'dart:io';

Future<void> main() async {
  final process = await Process.start('false', const <String>[]);
  await process.exitCode;
  process.stdin.writeln('hello');
  try {
    await process.stdin.flush();
  } catch (err) {
    // handle error
    print('handle $err');
  }
  print('end');
}

The is no output at all on macOS or Linux (I haven't tested Windows)

cc @andrewkolos

I think that I understand why this is happening:

the process exit handler is destroying the _Socket that manages stdin.
_Socket.destroy sets _raw to null but does not close the IOSink used for write, etc.
Process.stdin.flush() invokes _SocketStreamConsumer.addStream, which will never complete its future if _raw == null.


feat(): release @next

Try to use
% npm i @capacitor-community/stripe@next
% npm i @capacitor-community/stripe-identity@next
% npm i @capacitor-community/stripe-terminal@next

Issues

close https://github.com/capacitor-community/stripe/issues/406
close https://github.com/capacitor-community/stripe/issues/407
close https://github.com/capacitor-community/stripe/issues/410

Note

remove stripeterminalLocalmobileVersion and add to stripeterminalTapToPayVersion.

If you produce a (next) package I am happy to test this today :)

If you produce a (next) package I am happy to test this today :)

Thanks. It will be ready within the next hour!

Released at next tag:
% npm i @capacitor-community/stripe@next
% npm i @capacitor-community/stripe-identity@next
% npm i @capacitor-community/stripe-terminal@next

You might want to add to the readme section for iOS that in app podfile you need to update platform to 14 as minimum
platform :ios, '14.0'

I have tested tap to pay on android and ios all is working well. Thats my only use case at the moment though unfortunately.

You might want to add to the readme section for iOS that in app podfile you need to update platform to 14 as minimum
platform :ios, '14.0'

Updated!: https://github.com/capacitor-community/stripe/pull/411/commits/5ca9519a690eedf704737a66b5067e3c029294e0

I have tested tap to pay on android and ios all is working well. Thats my only use case at the moment though unfortunately.

Thanks for tested. I have also tested it and it looks fine, so I will merge it. please understand that Terminal contains destructive changes, but Terminal is the RC version.

released! https://github.com/capacitor-community/stripe/releases/tag/v6.4.0

Great effort 👍🏻


Unset client cookies on session destroy

I think it's reasonable to unset cookies at client side whenever the session is destroyed. (At least actix-sessions does this.)
Also, in my opinion it's a much nicer experience to avoid panics, because that causes the response to hang and never arrive. Instead, on storage failure we should send back a 500 INTERNAL_SERVER_ERROR. Also added tracing errors to appropriate places.
Let me know what do you think about these changes.

This looks great! Thank you for putting it together. I have one question about the branch you mentioned but I'm happy to merge this as-is.

Version 0.2.0 is now available and includes these changes.


Dockerfile: set default value for TARGETPLATFORM to fix regression on build-docker.sh

Codecov Report

Merging #45 (33042cb) into main (7e6b140) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   46.64%   46.64%
=======================================
  Files          44       44
  Lines        5709     5709
=======================================
  Hits         2663     2663
  Misses       2706     2706
  Partials      340      340

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 7e6b140...33042cb. Read the comment docs.


Amazon mobile push app pops up frequently to foreground while running in background.

Although it is not a part of the samples here in this repository still I guess it is somewhat related as it is based on the AWS sdk fro android. The app would frequently pop up and minimize the active app. Here is the link   snsmobilepush.zip!

The sample isn't owned by the SDK. We will consider add a SNS sample in the future.


"Preview your comment" does not accurately reflect comment formatting

Here is a screenshot of an issue I recently submitted:

Here is a screenshot of the preview I was able to see prior to posting the issue:

And here is the comment itself:
The description for this kata is not gramatically sound and does a poor job of communicating the problem.
Specifically:
>We want to generate all the numbers of three digits that adding their corresponding ones equals to 10 and being all of them in increasing order (the numbers may have two or more equal contiguous digits)
They are 118, 127, 136, 145, 226, 235, 244, 334.
Make a function that receiving the total sum of digits and the number of desired digits, outputs the amount of all these possible numbers with the minimum and the maximum numbers. The case above should be:
find_all(10, 3) == [8, 118, 334]

This section needs to be heavily reworked. Here is a replacement which may better outline the problem:
_____
Make a list of all numbers _n_ such that:
- _n_ has _num\_digs_ digits
- the digits of _n_ sum to _sum\_dig_
- each digit of _n_ is either equal to or larger than the previous digit (when parsing _n_ from left to right)

find_all will return _a_ list [_a_, _b_, _c_] where:
- _a_ is length of the list of _n_s
- _b_ is the smallest _n_
- _c_ is the largest _n_

For example:
find\_all(10, 3) == [8, 118, 334]

As calculated from the list of _n_s [118, 127, 136, 145, 226, 235, 244, 334]

As you can see the 'rendered github-flavored markdown' isn't correctly rendered in the preview. Notable in this example are:

Missing single line breaks
Missing bullets

I believe the missing bullets may actually result from the missing single line break, as using a double line break prior to the bullets causes the preview to render the bullets correctly.

This is because two different markdown engines are used. The server side engine has been updated recently, but they're still inconsistent.
See #1640. That issue is a duplicate of this one, but I'm going to close this one because it's old.


Structs/Lists/Maps should be automatically rendered as JSON to templates

Summary
For webhook notification services, provide the ability to forward the entire Rollout as JSON.
Use Cases
We would like to decide which fields to use within our service that handles notification webhooks, rather than within the notification template. This would allow us to reduce the coupling between the template and the webhook handling service that consumes the notifications (which currently have to agree on the schema). It would also cut down on the boilerplate that exists in our template definitions, which looks like:
{
  "deployment_name": "{{.rollout.spec.workloadRef.name}}",
  "current_step_index": "{{.rollout.status.currentStepIndex}}",
  "replicas": "{{.rollout.status.replicas}}"
  ...
}

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

Alternatively or preferably, we could add a built-in  json and yaml functions so that users could do this explicitly. e.g.:
{{.rollout | json}}

I just saw in the code we use sprig, which contains a bunch of default functions
https://masterminds.github.io/sprig/defaults.html
So the following should be possible today:
{{.rollout | toJson}}

@WillSewell can you confirm?

That did the trick! Thank you. Would you like me to update the documentation to mention this?

Some times the rollout status condition has quotes, it may throw off unmarshalling


Accessibility of "Tooltips" for new users after a long press

There is no message/text pop-up  after long press on  the inbox(the one that opens up after clicking the notification) ,mentions(@), starred(⭐)etc

This sounds like potentially two issues:

(a) We should make sure the app is accessible for users who can't see well.
(b) We could have tooltips on long-press of the icons.

Looking at some other apps, I don't find many that do (b). Mostly if I long-press an icon, it just does the icon's action, the same as a normal press would.
(a) is important. I don't really know the status of it, because I don't know what tools people normally use to use a phone when they aren't able to see the screen well. Certainly a tooltip itself will often not help :wink:; though it might if someone has a certain level of visual impairment and has set their text size very large.
I'd be glad to see an issue where someone finds the upstream advice from Google and/or Apple for Android or iOS respectively, tries out the app the way someone would who's blind (or has other accessibility needs), and identifies things that don't work. Then also very glad to see PRs to fix those things.

I believe this bug is just b). The fact that the first word of the title is "Accessibility" seems to be merely an unfortunate happenstance: both here, and in the discussion in chat, it explicitly addresses new users, not any other class; and – as you note – its suggested action is at best unhelpful for users who need a nonvisual interface.
Refiling as a-onboarding.

... that said, tooltips on long-press probably wouldn't help new users, either. As noted above, that doesn't seem to be a thing most other apps do; they generally wouldn't be discovered by the users they'd be intended for.
Perhaps, as we so often do, we should take a cue from the webapp, and implement something like the popups it has for first-time users. An issue (or at least a chat thread in #mobile) along those lines would also be welcome!
But I don't think it's appropriate to transform this suggestion into that one. Closing.
(@harshbisle, if I've misinterpreted you – or if you'd just like to discuss this further for other reasons – please feel free to poke me in chat!)


Polar area: startAngle in degrees, 0 at top.

I rebased https://github.com/chartjs/Chart.js/pull/5919 against master. I didn't make any other changes. I think it's fine to submit as is. It will be nice for users to standardize our units in the options

Needs a rebase

Done


Release a new version with the deprecation warning at the top

The deprecation warning and a link to the package that supersedes this one is present in the README but hasn't been published to npm: https://www.npmjs.com/package/eslint-find-new-rules. I think it would be worthwhile to release a new patch with the warning.
Remember to re-invoke npm deprecate eslint-find-new-rules "Your deprecation message" after you do it.

Good point

Done

The deprecation message is cut off:
npm WARN deprecated<EMAIL_ADDRESS>This

I suspec you didn't wrap the message in quotes. :)

Thanks for testing it out. Fixed.


Viz Plugins and Widget Set

Hey guys ,  reading the to do , and this two feature would be really super awesome to have, so wanted to ask , do you guys have a product roadmap, and more importantly can we (as our business) help out, speed up the dev, Obviously we will commit everything back the open source branch.
Just wanted to see if we can help out getting them faster out there
All the best
Oz

Probably the best way to help is by gradually ramping up on the project and by contributing your way up to become an Apache committer. By taking on smaller tasks you free up the other committers that have more context and can take on more complex tasks like the ones you mentioned.
These things are on the roadmap but not on the immediate roadmap (unlikely to be done this quarter).
Check out the starter_task label https://github.com/apache/incubator-superset/issues?q=is%3Aopen+is%3Aissue+label%3Astarter_task , also the help_wanted and find task that you feel like you can take on and that would be useful in your environment.

Also I'm hoping we start publishing our roadmap out on Github. Folks from Airbnb, Lyft and Twitter meet every two weeks and we have meeting notes we could share. Coming up soon.

Cool thanks , we are working ins some stuff here as well but I'll get someone to look at the link and work on it ,
Cheers
Oz


cask-repair fix package_sha for brew fetch output

When switched from brew cask fetch to brew fetch --cask in #201  output is changed and is now printing sha256 as last line. This fixes sha256 calculation.
Previously this following error;
• audit for loopback: failed
 - sha256 string must be of 64 hexadecimal characters

Because of brew cask fetch command outputs;
ykursadkaya@YKKs-MacBook-Air: ~% brew cask fetch cyberduck
Warning: Calling brew cask fetch is deprecated! Use brew fetch [--cask] instead.

==> Downloading external files for Cask cyberduck
==> Downloading https://update.cyberduck.io/Cyberduck-<IP_ADDRESS>862.zip
Already downloaded: /Users/ykursadkaya/Library/Caches/Homebrew/downloads/f09cc72c465cbf599635002ca568ce633f1c01733f0926de7122b6735931c5a0--Cyberduck-<IP_ADDRESS>862.zip
==> Success! Downloaded to -> /Users/ykursadkaya/Library/Caches/Homebrew/downloads/f09cc72c465

and brew fetch command outputs;
ykursadkaya@YKKs-MacBook-Air: ~% brew fetch cyberduck
==> Downloading https://update.cyberduck.io/Cyberduck-<IP_ADDRESS>862.zip
Already downloaded: /Users/ykursadkaya/Library/Caches/Homebrew/downloads/f09cc72c465cbf599635002ca568ce633f1c01733f0926de7122b6735931c5a0--Cyberduck-<IP_ADDRESS>862.zip
SHA256: 3becbea9d43261e8b8ddc139164c5744bb5535602bf994d400aedf8767fc1f44

Thank you. Pushing a new formula version soon.


What is the motivation to not allow the traffic fraction to change?

In our application we have the possibility to change the traffic fraction. Since the only responsibility sixpack has is to not include the user in the test, I don't see why we wouldn't allow to change this value during the tests itself.
The reason for this is simple, you first start with a small subset of customers, say 10%. Afterwards you come more confident in your test and you want to raise it to 20%. The only thing that changes are the amount of people that get included in the test. The numbers do not change and the statistical influence of this change is zero.
Thoughts?

Here's a PR on one of our own branches of sixpack: https://github.com/blackskad/sixpack/pull/2
The only oddity I could find while looking at the code would be that the percentage could be changed in the interim so that the value, when showing the experiment in sixpack-web is not correct. This is however not a big deal. You could for example keep track if the number was changed during the course of the experiment and even provide historic data when it was changed. I understand this might cause conflicts with admins who want to know exactly when a certain amount of traffic was excluded so I'd love some input here as to what we could do to make this more flexible.

@nickveenhof that change looks good. Would you mind writing a unit test, and opening a PR against this repo

On it. I really appreciate your responsiveness @zackkitzmiller!

Added a PR #192

Any update?

Closed by #192.


Question: using client side certificate

Is there any way to pass custom arguments to the request, such as:
pfx: FileSystem.readFileSync('./certificate.pkcs12') ,
passphrase: 'pwd'
Because eventually the https.request({...}) would accept such parameters.

@bistvan Use an https.Agent.  Options passed to its constructor will be passed on to tls.connect() (which also takes options for tls.createSecureContext()).
const pfx = fs.readFileSync('cert.pkcs12');
const passphrase = 'thepassphrase';
const agent = https.Agent({ pfx, passphrase });
const res = await fetch(uri, { agent });

Options passed to its constructor will be passed on to tls.connect()

This does seem to be undocumented behaviour according to https.Agent docs. The documented way is to pass client certificate options to https.request, but node-fetch does not allow passing those in fetch's options.

I made a fork and added the cert/key variables to the getNodeRequestOptions(request) function the same as with agent.

Why is this topic closed? How are we meant to pass TLS options like pfx and passphrase to https.request if the agent property is already using the proxy agent?


Add first draft for frontend development

This is mainly a response to your salutations, using simple-yet-powerful brunch.io tooling to make sure we have all the goodies expected from 2016 frontend development without the hassles.
@rlustin Please review and merge.

Thanks for the salutations @Signez.
👍 LGTM


Star Wars Opposition

Mod size: ~6,9GB
Star Wars Opposition is a mod that adds loads of Star Wars units, vehicles and assets to Arma 3. In the same way we used the WW2 mod I would like to use this for Divisional optionals in the future.

This mod is a whole Arma work over! The allows for a lot of new assets that work very well with the integration into Arma. The assets are very well designed with less then a 5% drop in FPS from standard operation. This mod works well with other mods and is ready for use on the TG servers with approval.

Think this will just be a fun way for us to enjoy the game in a new way Approved


Mention License in project homepage?

Could you add a link/mention of the license https://github.com/LeaVerou/awesomplete/blob/gh-pages/LICENSE into the homepage http://leaverou.github.io/awesomplete/#download ?
Maybe here? https://github.com/LeaVerou/awesomplete/blob/gh-pages/index.html#L312

Is there a reason for it? I believe it’s standard practice these days to look in the repo for a LICENSE file, or the header of the JS file…

I've known people especially working in big companies to be particularly jumpy about licenses - e.g.. not wanting to download/unzip a distribution to look inside in case they find the wrong flavour of GPL or whatever on the inside. But in general the Web page provides enough information for people to get up-and-running without diving into Github, I thought a quick link would save people hunting around.

Well, I wouldn’t object to a pull request :)


Fix envoy filter matching logic

The current logic was inverted, causing the multicluster gateway setup to fail.
Signed-off-by: Shriram Rajagopalan<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: GregHanson, rshriram
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS [GregHanson,rshriram]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@rshriram: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rshriram: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
1dcb37b04dc9ba663f75cd3cdcb90e01b107ecd4
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e-envoyv2-v1alpha3


Fixed multiple column non-primary keys in DB_forge.

According to the User guide below code will generate a compound index.
$this->dbforge->add_key(array('blog_name', 'blog_label'));

But it generate two individual indexes.
This issue was also found in 2010.
http://codeigniter.com/forums/viewthread/175805/

Hi!
I noticed the same thing.

We also need to be able to specify a key name with that.


StackOverflowError while proving transfer-failure-1-a-spec.k

I built the KEVM and tried to run the command given at the end, namely ./kevm prove tests/specs/erc20/ds/transfer-failure-1-a-spec.k VERIFICATION and I have a StackOverflowError.
The output is:
[Error] Critical: Function evaluation triggered infinite recursion. Trace:
(StackOverflowError: null)
while evaluating function keccak
while evaluating function keccakIntList
while evaluating function keccak
while evaluating function keccakIntList

(and so on...)
How to fix that?

You need to provide additional arguments to ./kevm prove to run that proof. You can do:
make tests/specs/erc20/ds/transfer-failur-1-a-spek.k.prove

to see the extra arguments needed for that proof.

In particular, you need the arguments which make keccak and keccakIntList rules concrete, which will stop this infinite recursion.

Alright, it's working fine now. Maybe you could add that in the README for the future newcomers, they might find it useful. Thanks!


Application workflow, commands and YAML configuration (APP-13, APP-14, APP-15, APP-16)

First and subsequent launch workflow:

Auth
List repo (if have any tracked repos)
Add repo (if don't have any tracked repos)
Updating repos statistics

CLI commands (add, remove, list, config)
YAML configuration to store credentials and repos info (hash of password stored)

Updated

Even though I approved it, please also see all inline comments.


Krusha Size Problems

Reduce Krusha's size for all kongs (so they can fit in 5DS) or fix Krusha's underwater massive collision box

Thanksgiving report


Twitch notification, flood (don't panic, DON'T PANIC!)

the alert is repeated 5-10 times
offline, online, offline, online.. while I had no problem side Twitch

does it spam instantly, or once every 15 seconds?

Hm, i don't know because i don't watch (I was on stream)

One thing i guess could be happening is that Nadeko is following too much twitch streams and she gets blocked every so often from making api calls which results in her treating it as offline. I will look into this.

you can use a buffer depending on _id, if if does not change is that it does not send a message via Nadeko
https://github.com/justintv/Twitch-API/blob/master/v3_resources/streams.md#if-online

The correction is incomplete, but Nadeko did not say more than what you see in the image

up? @Kwoth

Nobody else reported this afaik since the update. I don't know what could cause the issue.

The problem would not come uppercase? or made to do this:
~twitch Glaived_Tv
~rms Glaived_Tv
~twitch Glaived_Tv

I'm not sure if it's helpful for me to say but I have the same problem with the bot as well. Just thought to say because you've said that nobody else reported about it besides the OP. NadekoBot still spams a lot of stream announcements during twitch streams even though they're still running and never down once. Not sure how would it be fixed however.

I've never encountered this issue. But I've only been using the bot since https://github.com/Kwoth/NadekoBot/releases/tag/v0.94. I'm gonna guess this can be re-closed unless @Glaived is still having trouble?

im having the same issue with the latest release.

@blownco on self hosted bot, or Nadeko?


Single Task  Training

I would like to know how you ensure the richness of prompts in a single task as well as the richness of a single task during the multitask phase. Do you have a fixed number of prompts for each task, or did you use GPT to generate a batch?

We used a fixed number of GPT-4 generated prompts for each single-instruction tasks and multi-instruction tasks


This is a test issue! it will be removed soon

this is a test issue - it helps our team verify the integration between github and other apps

This was a test - it will be closed, and maybe reopened, as needed for integration testing purposes :)


Compilation fails for PS4 targets

pls 2 halp

https://github.com/dots-tb/rePatch-reDux0/wiki/Debug-Info-for-Bugs-and-Modding
Can you please install ShipLog,
Create the folder ux0:dump,
Start the application with the DLC installed that causes the crash,
Then go into ShipLog's application and DUMP LOG BUFFER TO DISK,
Please upload that logger.txt.
Thanks.


[Feature request] Ability to mirror highlights, in the same order as on the page

In my workflow, highlights order is very important as it gives context to other highlights - crucial for long articles.
As I am aware that preserving order and existing edits is technically challenging, it's more of a mirror workflow, like https://github.com/jsonMartin/readwise-mirror . I don't edit those mirrored files, just reference them by persistent highlight id at the end.
Hypothesis is one of the few platforms that allow for extracting this order through the API.

Readwise makes use of it in https://github.com/readwiseio/obsidian-readwise, but it has many issues of its own and is an unnecessary intermediary.
So, it would be great if you could implement following story:

User selects "Ordered mirror mode" in the options
On sync:
Folder with highlights is deleted
Highlights are inserted as usual, but ordered based on the position in the API, from the lowest start position to the highest

I did some dirty changes to allow mirroring by deleting highlights before sync if someone is interested: https://github.com/yep-dev/obsidian-hypothesis-plugin/commit/67624d09a5284b9e3bda93d67971b0fd9d6fb383


(BOLT-125) Support verified SSL for WinRM connections

We now default to HTTPS connections for WinRM unless --insecure is
specified. This requires a CA certificate to be provided, which can be
done via the winrm ca-cert setting in the config file.
The WinRM connection now uses the appropriate default port depending on
whether it's connecting via HTTP or HTTPS (using ports 5985 and 5986
respectively).

I'm not sure a great way to test this... I don't think we can easily enable SSL in the vagrant environment (the winrm command-line isn't available in nano server?), and I'm unclear what machinations we would need to go through in appveyor to generate an SSL cert, enable winrm SSL, and make that cert available to the tests. Even the winrm gem itself only tests using a cert fingerprint (rather than a CA cert) in appveyor.
It may be easier to cover this functionality at the acceptance level.

I also don't know whether we actually want to default to secure when you're required to set up a config file to point at the CA cert.

This is the script I used to setup SSL on a host for local testing:
$ErrorActionPreference = "Stop"
$system = Get-WmiObject win32_computersystem
$fqdn = $system.DNSHostName.toLower()+".delivery.puppetlabs.net"
$c = New-SelfSignedCertificate -DnsName $fqdn -CertStoreLocation cert:\LocalMachine\My -KeyUsage CertSign
winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@{Hostname=`"$fqdn`";CertificateThumbprint=`"$($c.ThumbPrint)`"}"
$out = [System.Convert]::ToBase64String($c.RawData, "InsertLineBreaks")
echo "-----BEGIN CERTIFICATE-----"
echo $out
echo "-----END CERTIFICATE-----"

It appears the failing test on Ruby 2.0 may be due to a ruby bug causing slow resolution for the first (maybe???) DNS request. The bug was surfaced by this change because I removed the before(:each) { winrm.connect } call for tests which were trying to create error conditions (and thus ignoring that connect call anyway).
Unfortunately, that means that the very first connection the tests now try to make is for the one test that expects a DNS request to fail in a specific amount of time...
The simplest thing here is probably just to reorder the tests, since I don't think there's much we can do about the actual bug.

@nicklewis there are PowerShell equivalents of the winrm commands. Something like https://github.com/hhazeley/Azure-V2-Powershell-Scripts/blob/master/CustomScriptExtenstions/WinRMHTTPS-FC-Set.ps1 should work for Nano.

CLA signed by all contributors.

@Iristyle I'll check that out, thanks. The New-SelfSignedCertificate command also doesn't seem to be available. We could probably just pregenerate a cert and stick it in the repo though, for the vagrant case. I'll have to see what we can do to get ahold of the cert content in appveyor.

Yeah, pre-generating a well-known cert should be OK (there may already be something in the cert store on the image as well).  Looks like others ran into the same problem with New-SelfSignedCertificate missing - https://github.com/PlagueHO/LabBuilder/issues/86

I added some certs in resources/ and updated the Vagrantfile and appveyor to use them, so we now have a test of SSL! This should be good to go now.

Updated to address comments, should be good to go again


[Snyk] Upgrade org.jetbrains.kotlin:kotlin-reflect from 1.8.21 to 1.8.22

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.jetbrains.kotlin:kotlin-reflect from 1.8.21 to 1.8.22.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released a month ago, on 2023-06-07.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Utdatert


Run linkchecker regularly

at least one link on https://bids.neuroimaging.io/governance.html is broken --> https://predictablynoisy.com/rust-governance

Easy option is a preset guthub action:
https://github.com/Remi-Gau/eCobidas/blob/master/.github/workflows/check_md_links.yml

Thanks for the suggestion @Remi-Gau - I'll see if I can get it to work and fix some links.

Hmm...
It does detect some, but also gives some false positives.

https://github.com/bids-standard/bids-website/runs/2817770324

yes, currently working on it :)
I'll open a PR so you can see


Updates sdk_automl_video_action_recognition_batch.ipynb

File came in regression log. Unable to download executed notebook. When ran in local, file executed successfully.
Changes made:
Update notebook according to template

[X] Use the notebook template as a starting point.
[X] Follow the style and grammar rules outlined in the above notebook template.
[X] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[X] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[X] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[X] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

Error: Step #5: TIMEOUT
Step #5: ERROR: context deadline exceeded

Executed notebook cannot be downloaded, No such URL Error


RxList null check in the constructor

If RxList is instantiated with the constructor without provide the optional parameter:
RxList([List<E> initial])
Like:
RxList<Foo> foo = RxList();
the constructor will override the property "_list" with a null.
This can cause null pointer exception on methods such as
isEmpty
isNotEmpty
An easy fix is to pass an empty list to the constructor:
RxList<Foo> rxList = RxList([]);
But that isn't a good solution, the linter will not flat the use of the constructor without the optional value.

Hi, thanks for that!
Can you add it to Map and Set too?

Hi, thanks for that!
Can you add it to Map and Set too?

Sure

Thank's, LGTM


switching to some views navigates just by bringing the view uptype browser, strings view, triage view navigates

builds 4728
This might be a duplicate but just documenting some details here for now.
When splitting to a new pane and then selecting a new view in that pane, extra navigation events are made.
Guilty views:

byte overview
type browser (sometimes? Can't reproduce consisently)
strings view (navigates to the first string in the view)
triage view (goes to entry point)

Worse, some of those views create navigation events so you can use ESC to back up to the previous location they don't work at all.

Example repro steps:

Open any file
Split to a new pane
In the new pane, switch to triage view
Notice that the view navigates to the entry point


Support for A100

I forked a copy of habitat to test and add support for A100s here -- https://github.com/suhasjs/habitat
I've appended specs for A100-SXM4-40GB in analyzer/habitat/data/devices.yml:
A100:
  compute_major: 8
  compute_minor: 0
  max_threads_per_block: 1024
  max_threads_per_multiprocessor: 2048
  regs_per_block: 65536
  regs_per_multiprocessor: 65536
  warp_size: 32
  shared_mem_per_block: 49152
  shared_mem_per_multiprocessor: 163840
  num_sms: 108
  shared_mem_per_block_optin: 0
  mem_bandwidth_gb: 1555
  base_clock_mhz: 1410
  peak_gflops_per_second: 8341

I've also added A100 to analyzer/habitat/analysis/mlp/devices.csv:
A100,40,HBM2,1555,108,9.5,19.0,300.0

In addition, I've added A100 to list of DEVICES in experiments/run_experiment.py.
I'm unable to run profiling/gather raw data on A100s with these changes.
I tried CUDA_VISIBLE_DEVICES=0 bash experiments/gather_raw_data.sh A100 and it spit out the following errors:
root@phodgx1:/mnt/new_habitat# CUDA_VISIBLE_DEVICES=0 bash experiments/gather_raw_data.sh A100
Processing: dcgan+64
Cross-device prediction: A100 -> P4000
Predicting requires_grad_ on P4000
Predicting zero_ on P4000
0, 448, 0, 32
Traceback (most recent call last):
  File "run_experiment.py", line 247, in <module>
    main()
  File "run_experiment.py", line 239, in main
    run_dcgan_experiments(context)
  File "run_experiment.py", line 153, in run_dcgan_experiments
    run_experiment_config(
  File "run_experiment.py", line 110, in run_experiment_config
    predicted_trace = trace.to_device(device)
  File "/mnt/new_habitat/analyzer/habitat/analysis/trace.py", line 48, in to_device
    operations = [
  File "/mnt/new_habitat/analyzer/habitat/analysis/trace.py", line 49, in <listcomp>
    operation.to_device(dest_device, actual_predictor)
  File "/mnt/new_habitat/analyzer/habitat/analysis/operation.py", line 85, in to_device
    return predictor.predict_operation(self, dest_device)
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 89, in predict_operation
    self._wave_scale(operation.forward, dest_device),
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 117, in _wave_scale
    predicted_kernels = list(map(
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 118, in <lambda>
    lambda kernel: self._wave_scaling_strategy(
  File "/mnt/new_habitat/analyzer/habitat/analysis/wave_scaling/unified.py", line 30, in unified_wave_scaling
    return resimplified_wave_scaling(
  File "/mnt/new_habitat/analyzer/habitat/analysis/wave_scaling/resimplified.py", line 26, in resimplified_wave_scaling
    if (kernel.num_blocks // origin_wave_size == 0 and
ZeroDivisionError: integer division or modulo by zero

The errors are a result of origin_wave_size and origin_occupancy being set to zero in calculate_wave_info() in resimplified_wave_scaling.
Do I need to re-train the MLP predictors with A100 profiling data mixed in? I noticed there exists a file analyzer/habitat/analysis/mlp/train.py. Is this relevant?
Is this the right way to go about adding a new device type to Habitat? It would be great if you had a write-up on how to add a new device :) I would like to try out habitat with a couple more device types

Division by 0 error
The first issue is caused by an outdated version of cuda_occupancy.h being included in cpp/src/cuda/cuda_occupancy.h. This version of the header file does not recognize devices with computeMajor=8 and returns CUDA_OCC_ERROR_UNKNOWN_DEVICE. This causes the call to cudaOccMaxActiveBlocksPerMultiprocessor in calculate_wave_info to error and return 0, resulting in the division by 0 error.
The solution would be to replace cpp/src/cuda/cuda_occupancy.h with /usr/share/cuda/include/cuda_occupancy.h. I symlinked the file and was then able to run gather_raw_data.sh.

Yeah. You would have to collect runtime data for linear, bmm, conv2d, and lstm using the scripts in tools/recording. After that, combine the data with the existing measurements then retrain the MLP.
@geoffxy Do you still have the measurements for our existing devices?

Thanks @jimgao1 for helping with this! 😄

@geoffxy Do you still have the measurements for our existing devices?

Yep - I responded to our email thread.

@jimgao1 Thanks a ton for your help! I was able to compile Habitat successfully on a DGX-A100 system. Additionally, I'm able to run tools/recording/record*.py and run_experiment.py on two different GPU types (RTX2080Ti and Quadro RTX6000) and am able to generate predictions for all the models on these two GPU types.
@geoffxy I got your training data for the MLPs and added in training data for Quadro RTX 6000 and was able to train the MLPs to completion. However, this is where things start breaking down.
I tried to run a naive bash gather_data.sh A100 with the compiled habitat package and got the following error when processing GNMT:
Cross-device prediction: A100 -> QRTX6000
Processing: gnmt+16
Cross-device prediction: A100 -> P4000
Traceback (most recent call last):
  File "run_experiment.py", line 248, in <module>
    main()
  File "run_experiment.py", line 243, in main
    run_gnmt_experiments(context)
  File "run_experiment.py", line 193, in run_gnmt_experiments
    run_experiment_config(
  File "run_experiment.py", line 111, in run_experiment_config
    predicted_trace = trace.to_device(device)
  File "/mnt/new_habitat/analyzer/habitat/analysis/trace.py", line 48, in to_device
    operations = [
  File "/mnt/new_habitat/analyzer/habitat/analysis/trace.py", line 49, in <listcomp>
    operation.to_device(dest_device, actual_predictor)
  File "/mnt/new_habitat/analyzer/habitat/analysis/operation.py", line 85, in to_device
    return predictor.predict_operation(self, dest_device)
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 89, in predict_operation
    self._wave_scale(operation.forward, dest_device),
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 117, in _wave_scale
    predicted_kernels = list(map(
  File "/mnt/new_habitat/analyzer/habitat/analysis/predictor.py", line 118, in <lambda>
    lambda kernel: self._wave_scaling_strategy(
  File "/mnt/new_habitat/analyzer/habitat/analysis/wave_scaling/unified.py", line 30, in unified_wave_scaling
    return resimplified_wave_scaling(
  File "/mnt/new_habitat/analyzer/habitat/analysis/wave_scaling/resimplified.py", line 26, in resimplified_wave_scaling
    if (kernel.num_blocks // origin_wave_size == 0 and
ZeroDivisionError: integer division or modulo by zero

The script finished all the 3 configs for resnet, dcgan and inception, but errors out for gnmt (I was able to run the script without any errors on both the RTX2080Ti and Quadro RTX6000 GPU types).
I thought this was an issue with the MLPs not being trained for lstm kernels on A100s, so I tried to run python3 record_lstm.py A100 and that runs into a deadlock (process enters a sleep state and makes no progress after a point). Here's the output of record_lstm.py before it was killed on the A100s:
root@phodgx1:/mnt/new_habitat/tools/recording# CUDA_VISIBLE_DEVICES=2 python3 record_lstm.py A100
2022-08-15 23:01 INFO     Total configurations:<PHONE_NUMBER>00
2022-08-15 23:01 INFO     Total configurations after filtering: 200000
2022-08-15 23:01 INFO     Slice size: 200000
2022-08-15 23:01 INFO     --- Found 2 recordings in lstm-A100-0.sqlite, so skipping the first 1 configurations ---
2022-08-15 23:01 INFO     Warming up...
2022-08-15 23:01 INFO     Starting to record. This process records slice 1 of 1.
Killed

I was able to profile bmm, conv2d and linear on A100s using the supplied scripts, so lstm is the only one to fail. Any idea why this might be happening? I think there's an issue with the LSTM backend that PyTorch might be using on A100s since the issues only show up for GNMT.
P.S: Do I need to run record_conv2d.py  multiple times for a given GPU type? I see it samples a random 200k arg combinations and profiles them.. but not sure if I need to profile more than the 200k single slice..

Hi Suhas,
Division by 0:

Did you update the cuda_occupancy.h file in your habitat installation? I was able to get things to run after updating this file.

Unable to record LSTM:

What version of CUDA/PyTorch are you running? You can obtain the former with grep -A1 "CUDA SDK" /usr/local/cuda/version.json and the latter with pip freeze | grep torch. It might also help to attach the whole /usr/local/cuda/version.json file, since that includes versions for CUPTI, CUBLAS, etc.
I recall being able to record all 4 kernel types on an A100 instance on GCP. Are you running anything else simultaneously?

Thanks!


[tlul/xbar] Add blanking based on address

This has been spun out from the D2S review notes here https://github.com/lowRISC/opentitan/issues/10926.
We should look into whether we can add blanking based on address in reggen (reg_top). Consider putting the gating into the XBAR. Also need to think whether gating to zero is the right thing to do for all critical registers (e.g. invalid MUBI nibble pattern). Make a separate issue that tracks this (so that it does not gate clkmgr D2S).

So, What I said in the meeting(3/8/2022) was:
the peripheral xbar has only one requester (TL Host) if I remember correctly. So, if socket_1n broadcast the data (I am not sure), then all peripherals can see the data.
If we can add one more TL host (requester), then we can cover the peripheral to the default requester always unless it is selected. So, from the attacker point of view, they need to tackle two points (valid for socket_m1, valid inside register module) or three points (+ attenuate the response d_valid to avoid alert).
The thing I want to check is:
the secret information always remains in the main crossbar (crypto). If it is main crossbar, we can re-order dm_sba port to be the 0 index and cover the value without changing peripheral xbar.

@eunchan, can you take a look at the PR? In your mind, what's the difference between doing this blanking on the socket_1n vs socket_m1?
I'm doing it on the former right now.

@eunchan, can you take a look at the PR? In your mind, what's the difference between doing this blanking on the socket_1n vs socket_m1?
I'm doing it on the former right now.

Oh, changing socket_1n is also fine. I misunderstood that socket_1n broadcasts the signal to every downstream ports.

Address-based blanking has now been implemented in the xbar in https://github.com/lowRISC/opentitan/pull/11045.
However, we still plan to add spurious WE monitoring to the register nodes as discussed in this comment thread https://github.com/lowRISC/opentitan/pull/11045#discussion_r814145132.

Spurious WE monitoring has now been implemented as well so I think we can close this.

yep that's right. Still on my radar, i got half way through something and
had to drop it to focus on other things.
On Wed, Mar 23, 2022 at 5:13 PM Michael Schaffner @.***>
wrote:

Address-based blanking has now been implemented in the xbar in #11045
https://github.com/lowRISC/opentitan/pull/11045.
However, we still plan to add spurious WE monitoring to the register nodes
as discussed in this comment thread #11045 (comment)
https://github.com/lowRISC/opentitan/pull/11045#discussion_r814145132.
—
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/11036#issuecomment-1076939473,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2RSWWT4C4TLBKKST2R3TVBOXSXANCNFSM5PFBVLLA
.
You are receiving this because you were assigned.Message ID:
@.***>


TypeError: 'type' object is not subscriptable

Traceback (most recent call last):
File "bot.py", line 10, in
import Paginator
File "/home/hydra/.local/lib/python3.8/site-packages/Paginator.py", line 6, in
class Simple(discord.ui.View):
File "/home/hydra/.local/lib/python3.8/site-packages/Paginator.py", line 44, in Simple
async def start(self, ctx: typing.Union[discord.Interaction, commands.Context], pages: list[discord.Embed]):
TypeError: 'type' object is not subscriptable

Thanks for creating an issue, I'll look into this tomorrow.

Please reopen this issue with more information about this error.


Tool to apply patch file to binary

Will have the following arguments:

-i, --input: input file to patch
-p, --patch-file: patch file
-o, --output: output file
-f, --patch-format: patch format
-d, --diff: show hex diff (maybe)

cc @geoffreynolds

I have released this in v0.9.2. Here is the help text:
Usage: kobopatch-apply [OPTIONS]

Version: v0.9.2

Options:
  -h, --help                  show this help text
  -i, --input string          the file to patch (required)
  -o, --output string         the file to write the patched output to (will be overwritten if exists) (required)
  -p, --patch-file string     the file containing the patches (required)
  -f, --patch-format string   the patch format (one of: kobopatch,patch32lsb) (default "kobopatch")
  -v, --verbose               show verbose output from patchlib


Small dev's description have been fixed

@JasonDsouza212 Reduced the description. Check now.

This issue has been resolved, so I'm closing this pull request


twa: 1.8.0 -> 1.9.0

Motivation for this change
To close #72689 by providing a working alternative
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I have found two minor issues in this version of twa: https://github.com/trailofbits/twa/issues/66 and https://github.com/trailofbits/twa/issues/67. I'm expecting the author to fix these soon. If this PR has not been merged by that time, I will update the package version and PR title.

Upstream here: Thanks. I've cut 1.9.1 with both fixes.

Updated to 1.9.1 and retested. Upstream fixes confirmed.

@c0bw3b I moved makeWrapper to the nativeBuildInputs, also describing the change in the commit message.


EKS Control plane log query examples

Currently the EKS control plane section only quickly leads the user through where the CloudWatch log groups are. To show how this is actually useful in real like we should demonstrate leverage CW log query for real-life scenario.
Some examples of CW log queries can be found here:
https://aws.amazon.com/premiumsupport/knowledge-center/eks-get-control-plane-logs/
Figure out which examples are practical with the workshop cluster setup.

Could also show new live data feature in CW: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-live-data.html


Can't get it to work with Stylus: Module build failed: TypeError: path must be a string or Buffer

I am trying to upgrade to Vue 2 and can't get it to work with Stylus:
Module build failed: TypeError: path must be a string or Buffer
I know it was a bug with node 6 but stylus-loader has been fixed.
Does anyone have any clue please?
"stylus": "^0.54.5",
"stylus-loader": "^2.3.1",

node v6.7.0
npm 3.10.7

Please provide a minimal example that demonstrates the issue. Stylus is working fine for me. 😕

Oh, I have uninstalled npm with brew and install it again with n and it seems to be ok now!
Closing this for now. It's being really annoying me for a day. I will reopen with a repro if comes back.


Support local address option

Related: #50

Codecov Report

Merging #54 into master will increase coverage by 0.09%.
The diff coverage is 83.34%.

@@            Coverage Diff             @@
##           master      #54      +/-   ##
==========================================
+ Coverage   77.72%   77.81%   +0.09%
==========================================
  Files           8        8
  Lines         377      383       +6
==========================================
+ Hits          293      298       +5
- Misses         65       66       +1
  Partials       19       19

Impacted Files
Coverage Δ

attacker/attacker.go
67.45% <66.67%> (-0.05%)
:arrow_down:

main.go
80.56% <100.00%> (+0.56%)
:arrow_up:

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 cccdee3...3a078a5. Read the comment docs.

@markruler Hi, thanks for your contribution! Could you perform gofmt -s and then push again?


feat: upload resources modal

Description
https://github.com/DARPA-ASKEM/terarium/assets/16358728/6dc00941-22bf-4e98-bf67-0c07a5e353e0
https://github.com/DARPA-ASKEM/terarium/assets/16358728/08a5695a-fd6c-485b-83dd-c7ddb3f71af6
Resolves #1849

Are you leaving link importing for another PR?

Nope, added it!


Using custom endpoint URL?

As suggested on certstream website, non-experimental use should not use the public server and should setup separate certstream server. However, currently the URL wss://certstream.calidog.io is hard-coded into the library.
I suggest adding the URL endpoint parameter for CertStreamEventStream. I can contribute the code and update the example if needed.

Added PR for this: https://github.com/CaliDog/certstream-go/pull/11


Update translations from Crowdin

Description
This PR updates translations from Crowdin generated files. The en-US entries have been recently removed, probably a bug fix in the generation process.
Changes made
Self-explanatory.
Checklist

[x] APIs have been properly documented (if relevant).
[x] The documentation has been updated (if relevant).
[x] New unit tests have been written (if relevant).
[x] The demo has been updated (if relevant).

We have learned that the key .iTunesMetadataContentRating seems only working on tvOS to constraint content related to age restriction (see also: https://developer.apple.com/wwdc19/503).


Engine loop scales worse than expected

The engine loop (consisting of both Physics and Rendering) is a fair bit slower than I'd expect with the hardware it runs on, often fully maxing out a CPU core with a decent simulation; I suspect there's a lot of optimisations that could be done to help with this, such as better re-sim protection (perhaps only track 'changed state' particles rather than ALL rendered particles?).
We could also potentially implement a system to 'deactivate' buried particles, since if a particle is surrounded below (y + 1) or either side (x +/-) then it cannot possibly move, yet is still included within full physics computation.
And lastly, which is most effective but highly challenging; we could potentially think about multi-threading the engine, but due to it's high reliance on a singular state (how would we be able to simulate two particles at once on two separate threads without a 'desync' in physics determinism?) this may be fairly hard to do.
Live Task List:

[x] Optimise the re-sim protection by only tracking particle state changes.
[ ] 'Deactivate' still particles (i.e; unable to move) from the physics loop.
[ ] Introduce multi-threading in some form.

I'm currently working on this as I speak (re-sim protection optimisation) and thinking of other scaling solutions, but posting this both as a reminder to myself and to let anyone else contribute if desired. :heart:

:heavy_check_mark: Re-sim protection optimised!
It was a ridiculously simple improvement which I somehow glanced over - but this has introduced a huge speed-up for the engine in terms of scaling compared to previous levels, yay!


Fix issue with bokeh legends

Since bokeh 0.12.7 you can specify a column in the CDS to draw the legend from. This can result in issues like this when the Element label matches the column name:

Thanks to Bryan I found out that "if the legend name is also a column name you need to explicitly pass value(name)", so that's what I've done here.

Seems fine to merge once the tests pass.

This PR is now a wholesale rewrite of a lot of the bokeh plotting code. The new capabilities can be seen here: https://anaconda.org/philippjfr/legend/notebook
Improvements include:

legend_position options have been fixed (and are no longer in weird positions)
OverlayPlot now has a multiple_legends options which splits the legends
Find adjustment of legend position can be done using legend_offset option

Going to go ahead and merge this, it's a huge improvement in terms of positioning and for actual correctness.


feat: adding api to get k8s version in manifest.json

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

25 of 25 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.9%) to 80.241%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
2335

Relevant Lines:
2910

💛  - Coveralls


Support gcc dev branch builds

The following now works to list the available gcc development branches:
./install.sh -B gcc

and the following will build, for example, the gcc trunk:
./install.sh -b trunk -p gcc -i /opt

LGTM


RFC: Adopt an official Symfony support policy

Our official support policy for Symfony dependencies is kind of a mess:

Support for different Symfony libraries will very across modules and is inconsistent
We still ostensibly support ancient EOL version while not supporting more recent supported version
We don't take into consideration Symfony's support timeline

We also need to consider that many Silverstripe CMS project will also use Symfony for their own purpose and that there's value in supporting multiple release line simultaneously.
Proposed policy
Silverstripe CMS modules that require Symfony dependencies will minimally tracked the latest Symfony LTS release. Where practical, we will allow installation of other Symfony release line. In descending order of priority:

Older LTS releases while they are still supported
Latest supported non-LTS release.

@silverstripe/core-team Any views on this? The proposed policy is just what pop into my mind after a full ten minutes of thinking about it, so I'm not overly protective about it.

Based on the symfony support timeline, the MVP is to just change this sort of thing
from "symfony/cache": "^3.3 || ^4",
to just "symfony/cache": "^4.4",
Then, based on how different the API is, pop in ^4.4 || ^5.4 || ^6.0
Given the good level of unit test coverage we have now, we should be able to run 5.4 + 6.0 through a recipe-kitchen-sink CI run to get a decent level of confidence that things either work out of the box or don't

@silverstripe/core-team We're looking at upgrading our Symfony constraints in the 4.12 release (that might be release sometime in Sept/Oct). Having consensus on this RFC would be helpful. Could you answer those questions:

Do you think having a formal policy on this is sensible?
If yes, do you think my proposed policy is a good one?
If no, what other criteria do you think we should take into consideration?

I'm not strictly against a policy, though not having one allows us the flexibility to do these things as/when we can/need to. Simply from that perspective, I wouldn't adopt one. Having one forces more work upon the team.
On the other hand, though, it makes Silverstripe CMS as a product more dependable and professional.
50/50 from me.

I'm not too phased by the extra work, so far my experience with symfony has been it's quite easy to adopt new majors because they don't do too much BC changes between majors.  Even it if turns out to be a fair bit of work, I see adoption of 'more symfony' as desirable and worthwhile.
I read the work here as:

Drop 3 entirely (very easy)
Bump the minimum on everything to ^4.4 (very easy)
Adopt ^5.4 - run through a kitchen-sink style CI, fix until green
Adopt ^6.0 on php8+ - run through a kitchen-sink style CI, fix until green

+1 for me

I'm okay with this

In a way, having an actual policy would be less work because we wouldn't have to argue about how we handle various scenario and we wouldn't have to worry about breaking things for people who want to use Symfony version outside of our policy.

the number of combinations that you might want to support could quickly make running tests a nightmare though - @emteknetnz in your example of running tests against both symfony/cache versions 5.4 and 6.0, what if you add a couple of extra symfony packages with two versions - now if you want to test all combinations it becomes 6 runs through the test suite.
Or am I mis-understanding your suggestion there? Are you just saying there would be (e.g) two runs only - a run of every module at ^5.4 and with every module at ^6.0?
I'm generally in support if you think it will lower the effort, but I do wonder what happens when new symfony major versions come out - do we then violate our policies until we upgrade everything? Feels like it could hit at inconvenient times and mess with the release cycle/cadence.

Might need to read the fine print of Symfony support policy. At first glance, it looks like the x.4 minor is the last minor for each major release line and becomes the LTS version. So if we were to support ^6.0 for example, we're implicitly support v6.4LTS which hasn't been release yet.
So maybe the policy should be:

We support the latest LTS
Once a new major is release, we aim to support that relatively quickly (which sets us up for supporting the next LTS eventually)
Once we've added support for the new major release line, we drop support for the oldest LTS

This has been made redundant by https://github.com/silverstripe/silverstripe-framework/issues/10345


Related to #11 - Parameter passing

Thanks for the info regarding passing an actual FetchXML query to the report however my query was something much simpler.
For example if the report required me to pass the "Owner" for a required report how would I do so?
I've tried passing the Guid of the User however I end up getting errors with bad requests.
Thanks

What kind of report is it (out-of-the-box report, Report Builder, custom report created through Visual Studio)?  How is the report parameter set up?  Can you provide a screenshot of what the report looks like when you try to run it?

Closed due to lack of response.  Feel free to open this back up if you are still experiencing this issue.


helmfile deps is failing with Chart.lock: no such file or directory with helm 3.0.2

helmfile deps is failing with Chart.lock: no such file or directory with helm 3.0.2.
It happens because helmfile tries to access Chart.lock which is not there in 3.0.2.
The behavior was changes in https://github.com/helm/helm/pull/7009 and now charts without apiVersion: v2 are treated  as helm 2 carts and generate requirements.lock instead
Error:
in ./helmfile.yaml: unable to update deps: unable to resolve 1 deps: open /var/folders/k_/361cq75j2sgf6dxm6625422m0000gn/T/79305915    5/Chart.lock: no such file or directory
Steps to reproduce:
Repo with reproducible example

Clone repo with example: git clone git@github.com:Nitive/helmfile-deps-helm-301-bug.git
Install helm 3.0.1 and helm 3.0.2 with ./download-helm.sh linux-amd64 or ./download-helm.sh darwin-amd64
Run helmfile deps with helm 3.0.1 — success

$ ./test-helm301.sh

Adding repo stable https://kubernetes-charts.storage.googleapis.com
"stable" has been added to your repositories

Updating repo
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "csssr" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈

Updating dependency /var/folders/k_/361cq75j2sgf6dxm6625422m0000gn/T/041766349
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "csssr" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading docker-registry from repo https://kubernetes-charts.storage.googleapis.com
Deleting outdated charts

Run helmfile deps with helm 3.0.2 — error

$ ./test-helm302.sh

Adding repo stable https://kubernetes-charts.storage.googleapis.com
"stable" has been added to your repositories

Updating repo
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "csssr" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈

Updating dependency /var/folders/k_/361cq75j2sgf6dxm6625422m0000gn/T/793059155
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "csssr" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈Happy Helming!⎈
Saving 1 charts
Downloading docker-registry from repo https://kubernetes-charts.storage.googleapis.com
Deleting outdated charts

in ./helmfile.yaml: unable to update deps: unable to resolve 1 deps: open /var/folders/k_/361cq75j2sgf6dxm6625422m0000gn/T/793059155/Chart.lock: no such file or directory

@Nitive Thanks a lot for the detailed report!
This should be fixed on the helmfile side.

@Nitive I've fixed this in #1056 which is included since v0.98.1.
The example repository did help me a lot for reproducing the problem and testing the fix.
Thanks again for your support!

Thanks for a quick fix!


Feature: add line selection option

This adds the ability to pass in a selection to be highlighted. selection={{startLine: 2, endLine: 4}} both endLine and startLine are inclusive. To highlight a single line pass in the same line number for both start and end. Uses CodeMirror-activeline-background class under the hood to allow for theming.

LGTM
I could see a use case for an array of selections in the future, potentially.

@alexlande I wasn't sure about the API, I considered an array of lines. Maybe that's simpler and more flexible overall?
e.g. selectedLines={[1, 2, 6, 7, 8]} or selectedLines={[3]}

Oh yeah, that would be a lot more flexible, I think. (And would make way more sense than an array of selection objects, haha)

@alexlande switched to selectedLines: array API. Please re-review, thanks!

Ship it!
On Wed, Apr 6, 2016 at 4:45 PM Rob Gerstenberger<EMAIL_ADDRESS>wrote:

@alexlande https://github.com/alexlande switched to selectedLines: array
API. Please re-review, thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/FormidableLabs/component-playground/pull/62#issuecomment-206623703


adding base64_encoding transformer

Hum, why is this in the massa-sc-examples and not in the massa-sc-scripts or at least in the massa-sc-template?


fix:fix all frontend warnings

I don't know whether to deal with other warnings

@jakiuncle plz don't close and open PRs for the same thing: https://github.com/casdoor/casdoor/pull/975

ok


Remove horizontal scroll bar on show listings

Fixes issue https://github.com/wesbos/Syntax/issues/215.
Makes overflow rules more verbose and sets overflow-x to auto so the horizontal scrollbar only appears if it's needed just in case.
I didn't include changes to package-lock.json in the commit, I hope that's ok?

@Pixelrobin Thanks Michael! 👍🏼


Roadmap

[x] Support for bytes32 leaves #36
[ ] Support for custom internal hash #39
[ ] Leaf getters #43
[x] Linting #38

[x] Use eslint config (from the transpiler) #41
[ ] re-enable @typescript-eslint/no-explicit-any ?

[x] Non regression tests.

[x] migrate tests to ava and use snapshot ? #41

curious if we can get an rc for the SimpleMerkleTree?


"The given key was not present in the dictionary" error on nuget to Standard 2.0 class library.

Trying to NUGET EntityFramework 6.2 to Standard 2.0 class library project in VS 2017.
Expected: just referenced ef6 (or an understandable error message).
Result: error and output
Restoring packages for D:\cot\DashboardCode\Routines\Routines.Storage.Ef6\Routines.Storage.Ef6.csproj...
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at NuGet.Commands.TransitiveNoWarnUtils.ExtractTransitiveNoWarnProperties(RestoreTargetGraph targetGraph, String parentProjectName, HashSet`1 parentProjectWideNoWarn, Dictionary`2 parentPackageSpecificNoWarn, Dictionary`2 warningPropertiesCache)
   at NuGet.Commands.TransitiveNoWarnUtils.CreateTransitiveWarningPropertiesCollection(IEnumerable`1 targetGraphs, PackageSpec parentProjectSpec)
   at NuGet.Commands.RestoreCollectorLogger.get_TransitiveWarningPropertiesCollection()
   at NuGet.Commands.RestoreCollectorLogger.IsWarningSuppressed(IRestoreLogMessage message)
   at NuGet.Commands.RestoreCollectorLogger.Log(IRestoreLogMessage message)
   at NuGet.Commands.RestoreCollectorLogger.Log(ILogMessage message)
   at NuGet.Commands.LockFileBuilder.CreateLockFile(LockFile previousLockFile, PackageSpec project, IEnumerable`1 targetGraphs, IReadOnlyList`1 localRepositories, RemoteWalkContext context)
   at NuGet.Commands.RestoreCommand.BuildAssetsFile(LockFile existingLockFile, PackageSpec project, IEnumerable`1 graphs, IReadOnlyList`1 localRepositories, RemoteWalkContext contextForProject)
   at NuGet.Commands.RestoreCommand.<ExecuteAsync>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.Commands.RestoreRunner.<ExecuteAsync>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.Commands.RestoreRunner.<CompleteTaskAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.Commands.RestoreRunner.<RunWithoutCommit>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.PackageManagement.DependencyGraphRestoreUtility.<PreviewRestoreAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<PreviewBuildIntegratedProjectActionsAsync>d__74.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.NuGetPackageManager.<PreviewInstallPackageAsync>d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at NuGet.PackageManagement.UI.UIActionEngine.<GetActionsAsync>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at NuGet.PackageManagement.UI.UIActionEngine.<>c__DisplayClass7_0.<<PerformActionImplAsync>b__0>d.MoveNext()
Time Elapsed: 00:00:00.0640251
========== Finished ==========

Duplicate of #231 and also see #271


[WIP] feat(53461): Implement decorator metadata proposal

Fixes #53461

Should the emitDecoratorMetadata option be used to emit metadata for ES decorators?
The test samples were taken from the specification proposal-decorator-metadata
Playground

FYI @rbuckton

Ideally, we can take this for the 5.2 beta which has a deadline of this Friday. Let me know if you need me to help with any part of this PR to get it in this week.

@rbuckton Thank you so much for taking the time to review this PR 👍🏻. I have added the esnext.decorators library and made changes related to types and factory helpers. I have noticed that the super call is transformed into Reflect.get in classFields. I'm not entirely sure if this is okay, I will check it tomorrow…

@rbuckton I've merged changes from the main

It looks like one of your evaluation tests is failing.

@typescript-bot pack this

It looks like one of your evaluation tests is failing.

Yes. It due to https://github.com/microsoft/TypeScript/pull/54657#discussion_r1239009504

We should also add this to esnext.decorators.d.ts:
interface Function {
  [Symbol.metadata]?: object | null;
}

This is looking fairly close to ready, once the baselines are reviewed and accepted I'll hopefully be able to take a final pass and approve.

@rbuckton What are your thoughts on moving the following types from decorators.d to esnext.decorators.d?
interface Function {
  [Symbol.metadata]?: object | null;
}

It shouldn't be optional since it will already get the | undefined from the DecoratorMetadata type with the definition I suggested. Placing it in esnext.decorators makes sense given the dependence on Symbol.

oke, I've moved it to esnext.decorators.d.

It shouldn't be optional since it will already get the | undefined from the DecoratorMetadata type with the definition I suggested. Placing it in esnext.decorators makes sense given the dependence on Symbol.

I should have added more detail to this, but it was late. The main reason to not make it an optional property of Function is that we wouldn't be able to make it not optional in esnext (or es2024, etc.). There is a way to do that, but it would have been more complex and employ the same mechanism as DecoratorMetadata already does, i.e.:
type FunctionMetadata =
    typeof globalThis extends { Symbol: { readonly metadata: symbol } } ? {
        [Symbol.metadata]: DecoratorMetadataObject | null;
    } : {
        [Symbol.metadata]?: DecoratorMetadataObject | null;
    };

interface Function extends FunctionMetadata {
}

But I think the approach of just using DecoratorMetadata—which already includes this conditional—and leaving the property as non-optional is fine.


Fix read citation problem. Fixes #36

Coverage remained the same at 100.0% when pulling cba3c993d1ae1bdfa753d559cb61ddff416efdee on 36_read_citation into d82b39f7d213fc1ca15cde019bea5c3dca164a14 on DEV_0.7.0.


OS X Compiling errors with qt5 from homebrew

So, I originally had an issue running the qmake command, but after the inclusion of the icns file, that error has been resolved, and it is now replaced by:
/usr/local/Cellar/qt5/5.5.1_2/bin/uic mainwindow.ui -o ui_mainwindow.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic settingsdialog.ui -o ui_settingsdialog.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic infodialog.ui -o ui_infodialog.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic killdialog.ui -o ui_killdialog.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic chestview.ui -o ui_chestview.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic signview.ui -o ui_signview.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic findchests.ui -o ui_findchests.h
/usr/local/Cellar/qt5/5.5.1_2/bin/uic hilitedialog.ui -o ui_hilitedialog.h
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++ -c -pipe -std=c++11 -O2 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk -mmacosx-version-min=10.7 -Wall -W -fPIC -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -I/usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers -I/usr/local/Cellar/qt5/5.5.1_2/lib/QtGui.framework/Headers -I/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers -I. -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/OpenGL.framework/Headers -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/System/Library/Frameworks/AGL.framework/Headers -I. -I/usr/local/Cellar/qt5/5.5.1_2/mkspecs/macx-clang -F/usr/local/Cellar/qt5/5.5.1_2/lib -o main.o main.cpp
In file included from main.cpp:7:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/QApplication:1:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/qapplication.h:37:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qcoreapplication.h:38:
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:739:55: error: no type named 'u16string' in namespace 'std'
    static inline QString fromStdU16String(const std::u16string &s);
                                                 ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:740:17: error: no type named 'u16string' in namespace 'std'
    inline std::u16string toStdU16String() const;
           ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:741:55: error: no type named 'u32string' in namespace 'std'
    static inline QString fromStdU32String(const std::u32string &s);
                                                 ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:742:17: error: no type named 'u32string' in namespace 'std'
    inline std::u32string toStdU32String() const;
           ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1307:53: error: no type named 'u16string' in namespace 'std'
inline QString QString::fromStdU16String(const std::u16string &s)
                                               ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1310:13: error: no type named 'u16string' in namespace 'std'
inline std::u16string QString::toStdU16String() const
       ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1311:15: error: no member named 'u16string' in namespace 'std'
{ return std::u16string(reinterpret_cast<const char16_t*>(utf16()), length()); }
         ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1313:53: error: no type named 'u32string' in namespace 'std'
inline QString QString::fromStdU32String(const std::u32string &s)
                                               ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1316:13: error: no type named 'u32string' in namespace 'std'
inline std::u32string QString::toStdU32String() const
       ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1318:19: error: expected ';' after expression
    std::u32string u32str(length(), char32_t(0));
                  ^
                  ;
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1318:10: error: no member named 'u32string' in namespace 'std'
    std::u32string u32str(length(), char32_t(0));
    ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1318:20: error: use of undeclared identifier 'u32str'
    std::u32string u32str(length(), char32_t(0));
                   ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1319:75: error: use of undeclared identifier 'u32str'
    int len = toUcs4_helper(d->data(), length(), reinterpret_cast<uint*>(&u32str[0]));
                                                                          ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1320:5: error: use of undeclared identifier 'u32str'
    u32str.resize(len);
    ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qstring.h:1321:12: error: use of undeclared identifier 'u32str'
    return u32str;
           ^
In file included from main.cpp:7:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/QApplication:1:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/qapplication.h:45:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtGui.framework/Headers/qguiapplication.h:40:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qlocale.h:37:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qvariant.h:41:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qmap.h:40:
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qpair.h:62:44: error: no member named 'declval' in namespace 'std'
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && noexcept(std::declval<T2&>() = p.second))
                                      ~~~~~^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qcompilerdetection.h:1027:43: note: expanded from macro 'Q_DECL_NOEXCEPT_EXPR'
# define Q_DECL_NOEXCEPT_EXPR(x) noexcept(x)
                                          ^
In file included from main.cpp:7:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/QApplication:1:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/qapplication.h:45:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtGui.framework/Headers/qguiapplication.h:40:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qlocale.h:37:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qvariant.h:41:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qmap.h:40:
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qpair.h:62:52: error: 'T1' does not refer to a value
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && noexcept(std::declval<T2&>() = p.second))
                                                   ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qcompilerdetection.h:1027:43: note: expanded from macro 'Q_DECL_NOEXCEPT_EXPR'
# define Q_DECL_NOEXCEPT_EXPR(x) noexcept(x)
                                          ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qpair.h:42:17: note: declared here
template <class T1, class T2>
                ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qpair.h:62:55: error: expected expression
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && noexcept(std::declval<T2&>() = p.second))
                                                      ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qcompilerdetection.h:1027:43: note: expanded from macro 'Q_DECL_NOEXCEPT_EXPR'
# define Q_DECL_NOEXCEPT_EXPR(x) noexcept(x)
                                          ^
In file included from main.cpp:7:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/QApplication:1:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtWidgets.framework/Headers/qapplication.h:45:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtGui.framework/Headers/qguiapplication.h:40:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qlocale.h:37:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qvariant.h:41:
In file included from /usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qmap.h:40:
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qpair.h:62:57: error: expected expression
        Q_DECL_NOEXCEPT_EXPR(noexcept(std::declval<T1&>() = p.first) && noexcept(std::declval<T2&>() = p.second))
                                                        ^
/usr/local/Cellar/qt5/5.5.1_2/lib/QtCore.framework/Headers/qcompilerdetection.h:1027:43: note: expanded from macro 'Q_DECL_NOEXCEPT_EXPR'
# define Q_DECL_NOEXCEPT_EXPR(x) noexcept(x)
                                          ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [main.o] Error 1

So, as I said in the title, I installed qmake via homebrew instead of the recommended way of compiling it myself. Can you tell from this error message if that is the problem?

I got the same error, I had to re-install qt5 from homebrew with the -static flag set, and then it got a little further, now its complaining about:
glmap.cpp:454:33: error: use of undeclared identifier 'floor'
  scale = qMin(width, height) / floor(zoom);

The way to fix the glmap.cpp issue is to add an include for cmath. I also had to make some tweaks to the TerraFirma.pro file to get it to compile under El Capitan.
I have the application so that it compiles and runs, but it's not working. I get a grey screen with no graphics whatsoever. Feel free to see my forked repository, and look in the "mjarvis-osx-fixes" branch.
diff --git a/glmap.cpp b/glmap.cpp
index f8c789e..603c79e 100644
--- a/glmap.cpp
+++ b/glmap.cpp
@@ -12,6 +12,7 @@
 #include <QSettings>
 #include <QSurfaceFormat>
 #include "./uvrules.h"
+#include <cmath>

 /*
  * Drawing order:

Here's my full diff of what I've changed so far. Note that you will need to install to /usr/local instead of /usr, because of System Integrity Protection in OS X El Capitan. That's generally a best practice for Linux as well, IMHO. I also had to tell qmake to add the c++11 flag.
diff --git a/Terrafirma.pro b/Terrafirma.pro
index 4e7e238..169e2b5 100644
--- a/Terrafirma.pro
+++ b/Terrafirma.pro
@@ -1,4 +1,5 @@
 QT       += core gui
+CONFIG += c++11

 greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

@@ -86,9 +87,9 @@ RESOURCES += \
 DISTFILES +=

-desktopfile.path = /usr/share/applications
+desktopfile.path = /usr/local/share/applications
 desktopfile.files = terrafirma.desktop
-pixmapfile.path = /usr/share/pixmaps
+pixmapfile.path = /usr/local/share/pixmaps
 pixmapfile.files = terrafirma.png
-target.path = /usr/bin
+target.path = /usr/local/bin
 INSTALLS += desktopfile pixmapfile target
diff --git a/glmap.cpp b/glmap.cpp
index f8c789e..603c79e 100644
--- a/glmap.cpp
+++ b/glmap.cpp
@@ -12,6 +12,7 @@
 #include <QSettings>
 #include <QSurfaceFormat>
 #include "./uvrules.h"
+#include <cmath>

 /*
  * Drawing order:

All changes have been merged.. and I went ahead and made a binary for El Capitan, it's on the website.


(PUP-10440) Remove networking code from the indirector

Decouple the indirector from HTTP requests.

Remove client-side IndirectedRoutes#request_to_uri* methods
Remove networking code from abstract rest terminus
Remove networking code from indirected request
Remove certificate related rest terminii

Blocked on https://github.com/puppetlabs/puppet/pull/8241

CLA signed by all contributors.

jenkins please test this with servertests on redhat7-64a,ubuntu1804-64a,windows2019-64a


Document folding + real world example

This shows how to use the folding library with a real-world example.
The PR also documents the code and the interface.
The PR also makes suggestions to simplify the code.

Closing in favor of https://github.com/o1-labs/proof-systems/pull/1906


Infrastructure: Add Cosmos backup

AS AN Architect
I WANT the data in Cosmos to be recoverable in the case where the Cosmos service gets deleted and recreated with an empty database
SO THAT I do not have to manually re-register all the system participants
Configure Cosmos to use the built-in backup functionality
Acceptance Criteria

[ ] Update Terraform to provision Cosmos with backup enabled
[ ] Register some participants and manually test that data can be restored if Cosmos is re-provisioned
[ ] Add documentation to sign-post on how to perform a data restore

Terraform module for Cosmos backup
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/cosmosdb_account#backup
Suggested values
resource "azurerm_cosmosdb_account" "db" {

  backup {
    type = "Periodic",
    interval_in_minutes = 1440
    retention_in_hours = 192
    storage_redundancy = "Geo"
  }


[FEA] Support named arguments in aggregate Pandas UDFs

Is your feature request related to a problem? Please describe.
In Spark 4.0 Pandas UDFs can now take in named arguments.
Describe the solution you'd like
We should add support for named arguments. The input to AggregateInPandasExec has changed from a list of indices to a map.
Additional context
https://github.com/apache/spark/commit/df534c355d9

Verify that fallback happens appropriately.


Update impersonation_microsoft_credential_theft.yml

Description
Adding tolerance for all attachments are images or pdfs and if the body is null use message screenshot to run the NLU intent.
Associated samples
Link to samples that are affected by your change.

Sample 1

Associated hunts
If you ran any hunts with your rule, please link them here.

Hunt 1

/update-test-rules

/update-test-rules


John Olutubo: Pre-course

[x] Create this issue
[x] Look through the guides in your class repo
[x] Install softwares
[x] Install VSCode extensions
[x] Organize my computer
[x] GitHub setup
[ ] Prep work for Workflows Week 1

I Need Help with: What are you having trouble understanding? What parts of the homework are you struggling to complete?
I still need help with understanding the Linux subsytem.
What went well?: What has been successful so far? have you learned and/or completed so far this week?
The installations went well, and I have been able to understand to some extent the basic concepts and use of Git and GitHub.
What went less well?: What mistakes did you and/or your group make? What was difficult?
It was quite challenging to understand the Linux subsystem setup and also the GitHub, especially because they involve the use of CLI, which was completely new to me.
Lessons Learned: What did you learn this week that you will take with you into next week? It can be technical, a mindset, a study habit, anything!
I learnt the basics of GitHub and how to create an issue. I also reinforced my growth mindset that one can learn strange things eventually even though they might seem almost impossible at first.

Learning Objectives

GitHub:

[ ] 🥚 Creating Issues: You can create a new issue in a GitHub repository using an issue template. You can correctly use labels, milestones, and assignment to make your issue findable.

[ ]  🥚 Searching Issues: You can find issues in a repository by label, author, and milestone.

[ ]  🥚 Project Boards: You can use issues on a GitHub project board to track your class assignments and help your classmates when they need it.

-HYF Workflows:

[ ] 🥚 Check-Ins: You can use the check-in template to track your module learning objectives, your weekly progress (and to post a retrospective at the end of the module). You create one check-in issue per module in the class repo and each Thursday you add a check-in comment to it and the label for the corresponding week. After review, we add the checked label. No need to remove previous labels either. So as an example, after a 5 week module, you would have 5 comments and 5 labels added by you.
[ ] 🥚 Deliverables: You can create an issue for this module's deliverable and track your progress on the class project board. Each week, there are different assignments / deliverables. If it is an individual project, you create your own deliverable issue for it in the class repo. If it is a group project, the entire group creates 1 issue together in the class repo.
[ ] 🥚 Asking for Help: You can use the help-wanted template in your class repository's Discussion board to ask for help, and to help your classmates when they are blocked.

Your Computer:

[ ] 🥚 File System Management: You can create and organize a new folder in your personal computer for the materials you will study at HYF.

Visual Studio Code:

[ ] 🥚 Install and manage extensions

[ ]  🥚 Open a folder for editing

[ ]  🥚 Create new files/folders inside of the folder

[ ]  🥚 Edit files and save changes


Clearer error message on module name conversion

Adresses #25

Thanks a lot for your contribution, @petereon!
CI fail is unrelated.

Least I could do! Thanks for developing this amazing tool!


chore(plugins) Add missing maintainer to css-minimizer-webpack-plugin

describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
[ ] Do not abandon your Pull Request: Stale Pull Requests.
Remove these instructions from your PR as they are for your eyes only.

Thanks!


Create table indexes

In order to fasten queries, we should defined indexes for most tables
Per microservice :

[ ] users
[ ] dojos
[ ] events

duplicate of https://github.com/CoderDojo/community-platform/issues/972 meh


feat: filtered streams

Implementing https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/introduction

The v2 (post-Labs) documentation is here

The v2 (post-Labs) documentation is here

Oups you're right, just the link was wrong, but the implementation is correctly the V2 ;)


Docker - Environment Variables not working

With the latest release the environment variables passed in to the container no longer seem to be being used. In this case the poller is trying to login to <IP_ADDRESS> despite UP_UNIFI_URL being present.
docker inspect unifi-poller
            "Env": [
                ...
                "UP_UNIFI_URL=https://unifi.jamiewood.io",
                "UP_POLLING_INTERVAL=1m",
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
            ],

docker logs unifi-poller
2019/12/02 10:12:03 [INFO] UniFi Poller v1.6.0-553 Starting Up! PID: 1
2019/12/02 10:12:03 [ERROR] unifi controller: Post https://<IP_ADDRESS>:8443/api/login: dial tcp <IP_ADDRESS>:8443: connect: connection refused

Sorry, some of them were renamed to make maintenance easier. See here: https://github.com/davidnewhall/unifi-poller/wiki/Docker#environment-variables

...but that appears broken. Will look into it!

Yup, I managed to break this entirely while trying to make it easier to maintain. Shortly I'll put a fix in master branch - pulling the Docker latest tag will have the fix. We've identified a few things that need to be fixed in 1.6 so a 1.6.1 will likely be out later this week. Sorry about that!!

1.6.1 fixes this, but 1.6.2 is coming, so maybe just wait..


Publish to Maven Central

Hi,
first of all thank you for working on this project! The recursion is exactly the feature which is needed and all other improvements also.
Are you planning to publish this to maven central, so I can use the modified version without manual intervention?

nevermind... found it.

Yes, it's on maven central, on pro.verron.docx-stamper -> https://mvnrepository.com/artifact/pro.verron/docx-stamper

Thanks for the quick answer. BTW are you planning to integrate furhter features? Mainly the replacement of text in text-boxes is very important for us https://github.com/thombergs/docx-stamper/issues/97. I already asked the developer to create a PR, but maybe you already looked at it.

I am okay to integrate it, it's just not our team priority right now.
We'd have no reason to refuse a good PR with a covering test case, for this is a logical feature to implement for this library.
I'll work on a clear manifesto of what would be the wanted feature set.

Usually i make it available in the followinghours, but it is a manual step i didn't automated yet.
I like to keep room for testing the new version with some existing applications first.
It should be available in the coming hour.

Thanks, its out now


Failed import engine

[12/28/2023-18:54:49] [TRT] [W] CUDA initialization failure with error: 100


Added logic to prevent upscaling product images

@bummzack - could you give this a quick review? Do you see any problems with doing this?