Inference

how to do inference?

Did you post the final models?

I did a straight run of this repo, unmodified (except for the obvious run parameters), on the cloud using one L40S. Results with the checkpoints/log/final model/inference code/online demo is posted at huggingface here: https://huggingface.co/lemonteaa/nanogpt-speedrun
(No claim that the codes are bug free though as I just ask AI to code it up quickly with some manual coding on the non core part)

I think gpt-fast will do a lot of help


Fix for error "Can't return an ElementFinder from an async function" in TS 3/4

Fixes ElementFinder so that protractor can be used with Typescript v3, v4.
Typescript fails to compile when ElementFinder is returned from an async function. This is because of optional property "then" present on ElementFinder. Previously this property was removed in #1926 but re-added back in #3835 as an optional. So I suggest that this property be removed again so that protractor can be used with Typescript version 3 and onward.

@googlebot I signed it!

r

@awaisraad Thanks for fixing this.Which version of protractor has this fix?

@debajyoti3061 this pr has not been approved, hence has not been merged into master.

@debajyoti3061 I have removed my PR because the email was different in commits and the one with which I signed SLA.


clang-tidy report converter now supports clang17 fixit format

clang-tidy version 17 introduced a new fixit diagnostic formatting. The report converter is now prepared to parse this new format. It also still supports the old format.

Fixes #4047

With the suggested changes, this looks fine for 6.23, but for 6.24 we should consider dropping the conversion from "random meaningless stdout text" to plist in favour of "well-formatted message and fix YAML" to plist. For a very long time now, Clang-Tidy was capable of dumping the structure of the created diagnostics (all the notes, warnings, and fixits, see https://github.com/llvm/llvm-project/blob/llvmorg-17.0.0/clang-tools-extra/test/clang-tidy/infrastructure/export-diagnostics.cpp!) in YAML.


Fix links in Readme.md and CONTRIBUTING.md

Overview
Fixed links in Readme.md and CONTRIBUTING.md files. I omitted an issue for this because this fix is just for documentations. 🙏
Test
I confirmed that I jumped to the correct pages by those fixed links using browser.

Looks good to me. Thanks!


Version Packages

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Minor Changes

c1eaeee: Added new tokens for slider. Deprecated old slider tokens.

Run report for 351d8ac1
Total time: 34.2s | Comparison time: 33s | Estimated loss: 1.2s (3.5% slower)

Action
Time
Status
Info

🟩
SetupNodeTool(18.13.0)
4.1s
Passed

🟩
InstallNodeDeps(18.13.0)
12s
Passed

🟩
SyncNodeProject(tokens)
0.9ms
Passed

🟩
RunTarget(tokens:build)
16.3s
Passed

🟩
SyncNodeProject(visualizer)
0.2ms
Passed

🟩
RunTarget(tokens:generateDiffResult)
1.8s
Passed

🟩
RunTarget(tokens:noop)
8.2ms
Passed

🟩
RunTarget(visualizer:noop)
1.8s
Passed

Touched files
.changeset/curvy-ravens-tell.md
packages/tokens/CHANGELOG.md
packages/tokens/package.json


Wrong version of Java manual

Java 14 is installed, but the link on the Firefox Bookmarks Toolbar is to the Java 11 documentation.

Added links to current resources, replacing the outdated Java link.


fix merge main/v1 workflow

What this PR does:

Needs commit
Workflow fails on the merge with following:Committer identity unknown

*** Please tell me who you are.

Run

  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"

Solution from https://github.com/actions/checkout#push-a-commit-using-the-built-in-token.

Works now:

success action: https://github.com/stargate/stargate/actions/runs/4254689855
created PR: https://github.com/stargate/stargate/pull/2460

@jeffreyscarpenter can you approve?


Confusing package with name "all" on pypi

When typing
pip install --upgrade all

I expected to upgrade all existing installed packages. Instead a package named "all" was installed. This package https://pypi.org/project/all/ doesn't provide any information on what it does and who the author is. Because of the confusing name, I suggest this package should be renamed or maybe removed from pypi.

Thank you. This project has been pulled by administrative action.
Primarily based on the concern of typosquatting such a command invocation.


feat: add Astar zKatana testnet

Add Astar zKatana chain data to

react-dapp-v2
react-dapp-v2-with-ethers
react-dapp-v2-with-web3js

Modify EIP155Colors, EIP155ChainData, EIP155Metadata objects, and add logo image to ./public/assets

Adding @glitch-txs and @ganchoradkov as co-reviewers for visibility

Hi @bkrem , sorry for the delay.
Added the zKatana config to wallet packages.


improve: thread-safe idempotent informer event source start

this will allow to multiple threads wait idempotently for the start of an informer event source

Can you elaborate on what this changes, please?

Converted it to draft (meant it that way originally), until not finished.
The reason for this is related to dynamic registration, if in a reconciliation multiple event sources are registered dynamically possible of same name from different thread (and also different type), it is hard to make that efficient ATM. Thus to not make all the threads possibly wait in the synchronized block of here. One way to do this si to query if the ES is already registered. But if registered does not mean it is started. By this change, calling the start method should ensure that it is started (in a thread-safe way) and also simultaneously waiting for the other thread if that is starting the event source. We can look on this as a lock striping.


[HUDI-7111] Fix performance regression of tag when written into simple bucket index table

Change Logs
After upgrade the version to 0.14.0, the performance of the Spark job, which is written into a simple bucket index table, is regressing.

The reason is in the PR#4480, the refactor of bucket index introduce two unnecessary stages in tag for simple bucket index.
List<String> partitions = records.map(HoodieRecord::getPartitionPath).distinct().collectAsList();
Impact
NA
Risk level (write none, low medium or high below)
None
Documentation Update
NA
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@danny0405 This regression was existed since version 0.12. Should we address the problem also in versions 0.12, 0.13, and 0.14?


Revisit README.md and add link to the awesome list

Integrate the upcoming awesome list and make our README.md welcome page more user friendly:

display the Chart.js logo (SVG)
center the logo, tagline and badges
add a "release" badge linking to the "installation" page
remove the "maintainabilty" badge (not really useful and actually not in our favor)
add the "awesome" badge linking to the upcoming awesome repository
remove the "installation" section which is an incomplete duplicate of this page
replace the "documentation" section by the documentation TOC
merge the "contributing" and "building" sections
add a link to our samples (was previously missing)

Inspired from the datalabels plugin README.md, the render can be seen here

I don't think codeclimate should be removed from PRs. Its ok to remove here, but I'd look forward for adding it back some day.

This PR doesn't disable CodeClimate, it removes the "maintainability" badge which is, I think, not useful to display on the home page. First because our score is quite low due to a lot of technical debt issues but also because it doesn't really mean something for our users (we could disable all rules and get the highest score).
I agree with @kurkle, we should not remove the CC integration on PR, neither change the configuration. I don't think it's false positive (e.g. with your last PR) but instead, cases where we are modifying existing code. So I think it's fine since it encourages us to refactor and/or simplify the existing code.
Also, I don't think the CC integration is "noisy". It only displays a status report that we are free to ignore if we judge it's not important or related to the PR. It also doesn't block from merging the PR. Something that would be great from GH would be an additional "warning" status: "it succeeded but with some warnings".

As discussed with @etimberg, we are going to thanks n8agrin directly from our Twitter account so I removed the whole "Thanks" section.


Small refactoring

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
✔

@darkdef please update from master.

Thank you! 👍


after sign the apk, update fail

this is my steps;

cordova-hcp server
change my own url
cordova-hcp build
cordova build android --release
use 360signer to sign the apk
isntall the signed apk
change smthing and  cordova-hcp build
copy the www dir to my own url related dir
BUT. nothing change on my app.

There should not be any difference if app is build for release or debug. When you build it for debug - you sign it with debug key. When you build for release - you sign with release key. And that's it.
Have you tried the same flow with debug app? And are you using local-dev-addon for that? If you do - in the case of release you will not get instant reloads when you change something in the www folder. Depending on your configuration - plugin will download updates when app is launched, and install it on the next start (if you don't use JS API).
So, try to reproduce the issue with the debug app first. Also, you can try and use JS API to debug a release version of the app.
But if you don't see any updates - most likely there is something wrong with the setup:

wrong url to the chcp.json;
app can't reach it;
chcp.manifest or chcp.json doesn't contain updates;
or the updates are actually loaded - you just need to restart the app.

hi, thank you for yor help
the problem has been resolved!
the problem is  my wrong operation,  I did not config the config.xml ,I just change the .chcpenv file .
my wrong operation can run the debug app successfully,but failed in release app


pull request for e2e test at 11/22/2016 14:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


[Snyk] Security upgrade gatsby from 3.3.0 to 4.22.0

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

starter/package.json
starter/yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Denial of Service (DoS) SNYK-JS-DATALOADER-8248488
  641

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

👷 Deploy Preview for taupe-cassata-172709 processing.

Name
Link

🔨 Latest commit
3a59f7d81a3b7e7407d9b6590b134c882c22c9cd

🔍 Latest deploy log
https://app.netlify.com/sites/taupe-cassata-172709/deploys/6721c52580709b000838e831


containerlab: 0.44.3 -> 0.45.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/srl-labs/containerlab/releases.
meta.description for containerlab is: Container-based networking lab
meta.homepage for containerlab is: https://containerlab.dev/
meta.changelog for containerlab is: https://github.com/srl-labs/containerlab/releases/tag/v0.45.1
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.45.1 with grep in /nix/store/8qss22jrxrdhirjrf2yf25xwcfvx88y5-containerlab-0.45.1
found 0.45.1 in filename of file in /nix/store/8qss22jrxrdhirjrf2yf25xwcfvx88y5-containerlab-0.45.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
containerlab

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8qss22jrxrdhirjrf2yf25xwcfvx88y5-containerlab-0.45.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A containerlab https://github.com/r-ryantm/nixpkgs/archive/2885fdbdead497cea16f6b2ac377d9744ebc3af2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2885fdbdead497cea16f6b2ac377d9744ebc3af2#containerlab

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8qss22jrxrdhirjrf2yf25xwcfvx88y5-containerlab-0.45.1
ls -la /nix/store/8qss22jrxrdhirjrf2yf25xwcfvx88y5-containerlab-0.45.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

containerlab

Maintainer pings
cc @Janik-Haag for testing.

Result of nixpkgs-review pr 257781 run on x86_64-linux 1

1 package built:

containerlab


surjectionproof: fail to generate proofs when an input equals the output

If any ephemeral input tag equals the ephemeral output tag (i.e. an input asset is exactly equal to the output asset), verification will fail due to an unexpected interaction between our surjectionproof logic and the underlying borromean ring siganture logic. However, our generation code still allows creating proofs like this, "succeeding" in creating bad proofs.
Since we cannot fix the verification side without hardforking Liquid, fix the generation side to fail in this situation.

utack bf18ff5a8c6295cb7db6e2989aefd6a78df7720f LGTM


componentDidMount was called before DOM attached

Hi, I appreciated your work on explaining React internal.
But I think there is something wrong about life-cycle.
https://gist.github.com/vanhtuan0409/b3bdfb7bfdb50edd45269a95e846c69f
The above snippet shows that componentDidMount was called before real DOM is attached to the document.
In the real version of React, I think componentDidMount is ensured to be called after the DOM was attached

@vanhtuan0409 thanks for notifying me! I did a little investigation and found that source of my inspiration - Preact - had the same issue:
https://github.com/developit/preact/issues/65
I am going to investigate it and try looking for a nice and tiny solution.

As I think, React split the process into 2 phase. Render phase and Commit phase. Life Cycle might be triggered in Commit phase after the whole DOM tree was constructed.

@vanhtuan0409 You're absolutely write - but stuffing stuff in 160 lines of code can be hard sometimes 😄

Sure It will be too much for a simplified version of React 😃
Tks for the article anyway

I think that the most straightforward solution is to defer it for the next cycle using setTimeout(() => this.componentDidMount(), 0) - whole tree will be already rendered in that case, but I am not sure if that is the best fix 🤔

Hey I opened a PR to address this issue https://github.com/sweetpalma/gooact/pull/4
My idea is that we can attach VDOM element as soon as it was created. Then we can incrementally attach its children later.
Not sure if I broke anything, if you have time then take a look

Great - I like it, made a few touch ups and added you AUTHORS list. Thanks for contribution!


Set "autonomy_realm_identity_management_system" based on host group definitions

For example, if samba_domain_controller group is defined, autonomy_realm_identity_management_system = "samba"

Completed with 7064225


Deleted The File

I deleted the .vscode file and added it to the gitignore list. Hoping it does not break anything since from what I heard it just sets up custom settings in vscode

This went through.  Some items are not selectable, like .10.   One of them sent my eyes into shock.


memorytest/linkingtest

I think these are good but if someone could also test this that would be great :)

Sorry about not getting to this sooner, it's been a busy week for me. I'll merge this now :)


Remove redundant rust dir

Which issue does this PR close?

N/A
Rationale for this change

Simplify the project structure by removing the redundant rust folder. In a future PR, I plan on moving the ui/scheduler files into the scheduler module.
What changes are included in this PR?

Remove rust folder and update build and docs

Are there any user-facing changes?

Noi

cc @mingmwang @Ted-Jiang @avantgardnerio


What's the process to contribute as an outsider

Hi Chandresh
Glad, that you asked this question. You can create a fork and and make your changes and create a pull request. Thats all simple :)


mapping class to  Array

Hi I have the following issue. in my json response I have a arrayList called included. I am trying to map my object to the objects in the ArrayList. The object is getting mapped (the id is there) but the attributes are not getting mapped though. Can you help on this ?

Can you provide me an example json to reproduce this behavior?

Sure !
{
"data": [
{
"type": "students",
"id": "1WKXBU",
"attributes": {
"firstName"<EMAIL_ADDRESS>"lastName": "",
"address": "",
"registeredAt":<PHONE_NUMBER>110
},
"relationships": {
"application": {
"data": {
"type": "applications",
"id": "IH2QYE"
}
}
}
},
{
"type": "students",
"id": "Q5W3GW",
"attributes": {
"firstName"<EMAIL_ADDRESS>"lastName": "",
"address": "",
"registeredAt":<PHONE_NUMBER>110
},
"relationships": {
"application": {
"data": {
"type": "applications",
"id": "DP9SYT"
}
}
}
},
{
"type": "students",
"id": "AUKNPN",
"attributes": {
"firstName"<EMAIL_ADDRESS>"lastName": "",
"address": "",
"registeredAt":<PHONE_NUMBER>110
},
"relationships": {
"application": {
"data": {
"type": "applications",
"id": "56U5C1"
}
}
}
},
{
"type": "students",
"id": "OEOTMB",
"attributes": {
"firstName"<EMAIL_ADDRESS>"lastName": "",
"address": "",
"registeredAt":<PHONE_NUMBER>551
},
"relationships": {
"application": {
"data": {
"type": "applications",
"id": "L3MI5I"
}
}
}
}
],
"included": [
{
"type": "applications",
"id": "IH2QYE",
"attributes": {
"appliedAt":<PHONE_NUMBER>615,
"status": "in-progress",
"matchingScore": 0
}
},
{
"type": "applications",
"id": "DP9SYT",
"attributes": {
"appliedAt":<PHONE_NUMBER>161,
"status": "in-progress",
"matchingScore": 0
}
},
{
"type": "applications",
"id": "56U5C1",
"attributes": {
"appliedAt":<PHONE_NUMBER>581,
"status": "new",
"matchingScore": 2.129279788309624
}
},
{
"type": "applications",
"id": "L3MI5I",
"attributes": {
"appliedAt":<PHONE_NUMBER>869,
"status": "in-progress",
"matchingScore": 37.31343283582089
}
}
]
}
For some reason I cannot map the attributes of "applications". But I get the object though

Thanks! Will check this in a moment.

Sure ! Thanks in advance !

I tried your json out with these classes:
Student.java
public class Student extends Resource {

  @SerializedName("firstName")
  public String firstName;

  @SerializedName("registeredAt")
  public long registeredTimestamp;

  @Relationship("application")
  public Application application;

  @Override
  public String toString() {
    return "FirstName: " + firstName + "\nApplication: " + application;
  }
}

Application.java
public class Application extends Resource {

  @SerializedName("status")
  public String status;

  @SerializedName("matchingScore")
  public int matchingScore;

  @SerializedName("appliedAt")
  public long appliedTimestamp;
}

MainActivity.java
Deserializer.registerResourceClass("students", Student.class);
    Deserializer.registerResourceClass("applications", Application.class);
    Morpheus morpheus = new Morpheus();

    try {
      JsonApiObject object = morpheus.parse(getJsonString());
      for (Resource resource : object.getResources()) {
        Student student = (Student) resource;
        Log.d("Test", "" +
            "StudentName: " + student.firstName + "\n" +
            "StudentRegistered: " + student.registeredTimestamp + "\n" +
            "Application Status: " + student.application.status + "\n" +
            "Application Score: " + student.application.matchingScore + "\n" +
            "Application AppliedTS: " + student.application.appliedTimestamp);
      }
    } catch (Exception e) {
      e.printStackTrace();
    }
  }

The log will output your data of the student and the application.
Can you check If you forget some configuration?

I have used the exact configuration. But I dont get the attributes though.Please check this

Do you have an mismatch between the datatype in the json and the type of your variable?
If there is a e.g. a Number in the json and you want to match it to String, then it will fail and all values will have a null value.

This is the class I have created

Hi.. I actually figured out the issue. It is the data types. Thanks for helping me out


Data set acquisition

I am very interested in your experiment and want to repeat it. Could you please give me the data set used in the experiment? thank you

You can download it yourself if you want to. You first need to register an account at ADNI and then follow the instructions we have here.

I followed your steps to download the data, but I could not find the data you mentioned when selecting the data.such as select the "MPR; GradWarp; B1 Correction; N3; Scaled" ones

You should select "Pre-processed" in IMAGE TYPES sub-menu, instead of "Original".
We fixed the README, thanks for catching that. See if you can browse the correct images now.

You should select "Pre-processed" in IMAGE TYPES sub-menu, instead of "Original".
We fixed the README, thanks for catching that. See if you can browse the correct images now.

Thank you


GG1 - Improve SMC ergonomics

Pretty shifty as of now, probably forward things like telemetry into the callbacks.

The idea I had for this was too complicated and could be replaced with something that can already be done with the existing code.


make the badges of single type and add some more

Description
The badges are of different type (see the image). Add some more badges to the top of readme.md file, since the badges will be colorful and more attractive than the text the users will like it and after linking the badges it will also help them to navigate to different sections/ webpages like PRs, issues, contributors, etc.
Describe the solution you'd like

I will add some more badges and also will add links related to them so that the README.md file will look more interactive and awesome.

[ ] I will align them to the center
[ ] I will add some more badges
[ ] I will add links to the badges
[ ] I will make them all of single type

Work under/as

[x] LGMSOC
[ ] Contributor

@starlightknown should I make these changes??

sure go ahead


fix: pnpm nested versioning pattern

Solve this issue.
https://github.com/siketyan/loxcan/issues/101

Released in v0.8.1.


Please add release note screen replacement on iPhone 8 may result in no touch

sorry but I know no other way of helping people like myself be protected from updating their iPhone to iOS 16 only to find that the jailbreak doesn’t work even though it’s listed as working.
And remember, everyone with this phone if they are on another iOS below 15 would have to update and future restore down to iOS 16.x if they want to try testing this jailbreak.
This is a pretty big deal. It seems as if an iPhone 8+ will not run this jailbreak if your screen has been replaced. this should at least be added to a black list of non working devices. iE that’s the exact model with a screen replacement I was going to update to iOS 16 to try this out, that would’ve been a big mistake as I would’ve ruined this device
screens get replaced all the time and after the fact, making this model of phone really a no go for this jailbreak!
SOLUTION! having the ability to respring into jailbreak would solve it for this hardware. This is the last and fastest iPhone that still has the checkrain exploit making it a very important device

This is not an issue with the jailbreak, it just breaks after a userspace reboot, even if the jailbreak isn't activated, therefore it's not fixable.

Yes I get that. I was imploring you to put a notice on your jailbreak release page about that limitation on that hardware so that people don’t update and try to jailbreak only to find that it does not work on their device.
We don’t want people needlessly updating to iOS 16 in hopes of a jailbreak on this device only to find that they just updated the device that is no longer jailbreakable

none of the versions supported by dopamine are updatable-to anyways. Also this probably only affects bad replacement screens.

Also, every iPhone 6s Plus can currently be updated to the latest iOS and jail broken on Dopamine too. This is the test device I have been running for the past eight days. Incredibly enough, even the 15.8.1 still has the TrollStore Coretrust bug as well!
I updated when 15.8 was signing. Future restore is supported for just about all iOS on this model of phone as well
Sent from my iPhone

On Feb 26, 2024, at 11:25 AM, Evan @.***> wrote:
It’s a narrow window, and yet it applies to all a11 devices right now
<image0.png>
Sent from my iPhone

On Feb 26, 2024, at 10:58 AM, @.*** wrote:

If I use future restore, I can currently successfully use the blobs I have for 16.6 to update my 8plus device. First update to 16.7.5 current, then future restore will let me use my blobs to go back to 16.6 or 16.61 which dopamine supports.
I suppose I could take the risk and try it assuming that my legitimate screen replacement done by a professional in town might not have the same problem…
Then I would have if touch still didn’t work in the graveyard to test for the future and add to the pile of verified iPhone 8 Plus with screen replacement stuck on iOS 16 with no jailbreak… It is just a backup device…
I was indeed going to do this because this jailbreak is actually much more stable so far than taurine ios 14 which had constant resprings with no rhyme or reason on 2 different 8plus 14.4, 14.7.1, and 2 different 6splus , never had any reboots though. Resprings would happen spontaneously and just about every context you can imagine, about once every day to once every three days to twice a day.
Your jailbreak hasn’t done any of those things in my uptime is now eight days 16 hours
Sent with Spark

On Feb 26, 2024, 5:09 AM -0800, Lars Fröder @.***>, wrote:
none of the versions supported by dopamine are updatable-to anyways. Also this probably only affects bad replacement screens.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

<Image.png>


Throw an appropriate exception if createComponent fails

Note that PooledEngine already throws a RuntimeException with an appropriate message "Class cannot be created (missing no-arg constructor)", instead of returning null.
Engine.create still catches the Exception and throws aCreateComponentException for consistency between the two Engine types.

Other than some cosmetic issues with long exception class declaration, it's great. Thanks for some tests to cover this use case.

I've noticed you made the PR into the master branch rather than develop. I won't revert the changes, but please add new features to develop first.

Ah yes, sorry about that @czyzby!

It's OK, thanks again for the quick fix. ;)


Creating pull request after adding a function in project.

Created subtract function and corresponding test file to add functionality of subtraction in project.

Nice work @sonutiwari ! In future, you could make separate PRs for each task so that they can be merged independently.
Since we want to keep the mistakes in the tests for other participants to use, we wouldn't be merging this PR. Hope the practice was good nevertheless 😄


[1497] Fixes ToS checkbox logic [master]

Resolves #1497

Enables ToS checkbox for self-created users
Disables ToS checkbox for all users(admins) modifying other users
Now clarifies Editing Profile vs Editing User on Edit Page
Edits tests to match

making a separate PR for v5.5 momentarily

Cherry-picked from the v5.5 branch

Unblocked now that #1510 was merged in.

cherry-picked from #1510

Great, merging. Please update the CHANGELOG for v6.0.0, thanks!


sse4.2: string comparison functions lacking good documentation

The sse4.2 string comparison intrinsics are useful but very complex. Most (if not all) would benefit from examples and a descriptions of the effects the various modes have on the function.

Mostly just to make sure I don't forget to circle back and do this once I get sse4.2 covered

Worked on this some last night. Should have a WIP PR in shortly to get some early feedback

Fixed in https://github.com/rust-lang-nursery/stdsimd/pull/94! (although please let me know if I'm wrong)

Yeah, I'm good with closing it here. I might circle back to document some of the other functions later.


Substitute Miniproject: maintain list of tags

Maintain list of tags, recreated each time a tag is added.

Fixed by 08f4d0b240156a9b60c977b8060afe51ec627ea3


Fix locationBuilder docs

Migrate to 0.14.0 version, RoutesLocationBuilder provides state parameter.

Nice catch @definev
Thanks for the PR! :tada:


BETSEE <IP_ADDRESS> (Lucky Levin) released.

Significant changes include:

Python >= 3.5 required. In accordance with the looming end-of-life
(EOL) of Python 3.4, BETSEE now strictly requires at least Python 3.5.
Simulator phase queueing. Simulator phases (e.g., seed, simulation)
may now be independently queued and dequeued such that the end user
clicking the simulator-specific start button now sequentially runs
each currently queued simulator phase.
Simulator phase running. Simulator phases (e.g., seed, simulation)
may now be independently run, paused, resumed, and stopped in a robust
manner leveraging our newly introduced thread pool API.
Simulator progress. Feedback metadata is now contextually displayed
(in quasi-realtime) for the current simulator state:

Percentage-based progress.
Human-readable terse status.
Human-readable verbose substatus.

Simulator widget synchronization. The internal state of all simulator
widgets is now explicitly synchronized against the external state of
both the simulator as a whole and the currently running simulator
phase if any, substantially improving the User eXperience (UX).
Placeholder text excised. Placeholder simulation configuration tree
items (e.g., "Dynamic Channels", "Network") have now been dynamically
pruned at runtime, dramatically improving usability.
Font sizes normalized. The BETSEE GUI was initially developed on a
high-DPI system, which understandably resulted in substantially
smaller font sizes than desirable on standard DPI systems. Font sizes
are now normalized to conform to standard aesthetic expectations.
Stylesheet simplified. The global application stylesheet has now been
sanitized, simplified, and streamlined: AKA, 3S.
Thread pool API. The new "betsee.util.thread.pool" subpackage now
implements a rather efficient, portable, multithreaded framework for
independently starting, stopping, pausing, and resuming an arbitrary
number of arbitrary long-running threads. This framework largely
obsoletes all prevailing low- and high-level Python and Qt
parallelization APIs, including (but presumably not limited to):

"multiprocessing.dummy".
"threading".
"PySide2.QtConcurrent".
"PySide2.QtCore.QFuture".
"PySide2.QtCore.QRunnable".
"PySide2.QtCore.QThread".
"PySide2.QtCore.QThreadPool".
Note that this framework is effectively unencumbered by the Global
Interpreter Lock (GIL), assuming worker threads that routinely defer
to the canonical QBetseeThreadPoolWorker._halt_work_if_requested()
method to enable user responsiveness. Naturally, all BETSEE-specific
worker threads satisfy this sensible constraint.

Installation instructions conda-fied. Installation instructions have
been significantly streamlined to leverage the newly released Anaconda
package for BETSEE, kindly hosted by the non-profit conda-forge
organization. The obsolete Ubuntu-specific installation script has
been removed.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


pbrsa_secretkey_import does not seem to be able handle the output of pbrsa_secretkey_export

FAILED:<PHONE_NUMBER>01280:error:06000066:public key routines:OPENSSL_internal:DECODE_ERROR:/src/fastly/h2o/boring_src/crypto/evp/evp_asn1.c:164:

I was doing some transformations to the data.  Passing the same bytes from export to import works fine.


EPG URL

Hi @parker1992 - following our conversation here https://github.com/pierre-emmanuelJ/iptv-proxy/issues/120 it is understood that your repo does not support xtream and that's fine since I have access to an m3u- and an epg file. I am still however having trouble understanding how you are proxying epg data if no epg file is defined. Would you mind clarifying where/how I can define the EPG url using your repo?
Thanks

Nevermind, just read your repo description and it seems that I need to include the URL manually in my m3u. Would it be possible to have this as an env variable?
Cheers

The m3u should have a line such as '#EXTM3U url-tvg="http://url-to-epg.com/epg"' which will have the URLs prefixed to go through the proxy.
If you have a separate EPG that's not in the m3u and want to provide that separately, that's in coach's PR which I'll review tonight.
Also for URLs within the EPG which I'm not sure what those are needed for, coach's PR addresses those too.

Perfect, it all makes sense now :)
Thanks for your help on this. Cheers

@coach1988
Released this as 0.2.0


Fixed RegExp to match channels when guessing the win file version

Current RegEx matches all versions and doesn't respect channels.
E.g.:
someapp-0.0.2-beta3-full.nupkg matches 0.0.2 and requests a tag v0.0.2 which doesn't exist. RegEx should match 0.0.2-beta3 or 0.0.2-beta.3.
Currently win implementation is broken when using channels and this PR fixes it.

and requests a tag v0.0.2 which doesn't exist
This was made for my specific workflow – https://github.com/Aluxian/Whatsie/releases. In my case, tags never include the channel. Would it work if you did the same?

Also, my guess is that this will break for anyone not including the channel in the tag.

Check the example regex. Channel in tag is totally optional and the provided regex shouldn't break anything (it even supports multiple versioning schemas). We have a requirement to have versioning like this:
v0.0.1-beta1, v0.0.1-beta2,... v0.0.1-stable
v0.0.2-beta1, v0.0.1-beta2,... v0.0.2-stable

It is optional, but that means that if it is there, it'll match it. Not that for users like you it'll match and for others won't.
My point is: if I merge this, for files like someapp-0.0.2-beta3-full.nupkg, it'll always look for tag v0.0.2-beta3. But only you have that tag.


Fix typos

Changes

Linear: https://linear.app/thirdweb/issue/INF-171/
Here is the problem being solved.
Here are the changes made.

How this PR will be tested

[ ] Open the dashboard and click X. Result: A modal should appear.
[ ] Call the /foo/bar API. Result: Returns 200 with "baz" in the response body.

Output
(Example: Screenshot/GIF for UI changes, cURL output for API changes)

Looks good.
For future PRs, If you can also update the PR Description to not be the default template and fill in your changes details :)


chore: update stream-http

Ping

:+1: I'm experiencing a lot of issues with Webpack bundling both v2 and v3 of readable-stream. Most of my dependencies (through2, split2) have switched to readable-stream@3 so now would be a good time to get Webpack on the readable-stream@3 horse as well.
(readable-stream@3 is a transitive dependency of stream-http@3)

Ping

This is a breaking change so this can't be merged


owner,scheduler(ticdc): fix some typos and add log

What problem does this PR solve?

Issue Number: ref https://github.com/pingcap/tiflow/issues/5039
What is changed and how it works?
fix some typos and add log.
Check List
Tests

No code

Code changes
None
Side effects
None
Related changes
None
Release note
None

/label require-LGT1
Since it just fixes typos and adds logs, marking it only takes one 👍.

/run-all-tests

/run-all-tests

Codecov Report

Merging #5040 (87301c5) into master (687e248) will decrease coverage by 0.3801%.
The diff coverage is 53.8789%.

Flag
Coverage Δ

cdc
61.2227% <45.3475%> (+0.6241%)
:arrow_up:

dm
51.3864% <87.3949%> (-1.0832%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #5040        +/-   ##
================================================
- Coverage   56.1240%   55.7438%   -0.3802%
================================================
  Files           522        524         +2
  Lines         65325      67272      +1947
================================================
+ Hits          36663      37500       +837
- Misses        25094      26074       +980
- Partials       3568       3698       +130

/merge

/run-kafka-integration-test


add new params and fix issues

fix the .
add param for id

Just to clarify: the . is a great way to denote subs collections that are belong to a main collection. So we are changing from:
repos.pulls to repos_pulls which both represent the something: "pull requests under repos"
this is mainly due to this . notation runs into some problem with cube.js so we have to name the collection using the underscore instead of .
going forward we should be conscious of this decision that _ represent sub collections. So we don't run into some confusing names like "repos_pull_requests" for example.

forgot to mention thanks for the contribution @chenz4027  :100: :+1: :1st_place_medal:


Create HCA Login

As a user of the HCA CLI, I would like to login into the CLI in a intuitive way, so I may use service that require authentication.
Defintion of Done

Remove hca dss login
Remove hca query login
Use a single token for all authenticated request in the hca
add hca login

Heads up to @kozbo and @kislyuk that these changes will affect your cli commands.

tagging a few others. @hannes-ucsc @jessebrennan @DailyDreaming

Using the revoke endpoint in auth0 will revoke all refresh tokens give to that user by auth0 not just the one provide in the request. We should make a complete logout optional.
def logout(revoke=False)
    """ Logout the user, if revoke is true, all refresh tokens issues
         to that user for the hca will be revoked."""
    pass

We should also make it clear when logging in that a refresh token is not required and should only be used on secure machines.

depends on https://github.com/HumanCellAtlas/dcp-cli/pull/417

Can we return an error message from hca dss login telling the user to use hca login?


⚠ Bofrost.at has degraded performance

In 2d52ac4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1074 ms

Resolved: Bofrost.at performance has improved in c07f2d6 after 6 minutes.


Feature/workerpipe

-- added jenkinsfile for worker app

Currently, it only has a working spec for build job. using mock steps for rest of this jobs.

Cancelling pull request


DirectX Injection

Hooking into directX dll to capture screen and display overlays

Removing due to being unrealistic and cluttering up the issues section


filter-sql-expression quotes

Create/Update a rule using Powershell and the Azure CLI you may need to wrap the rule in double quotes as an example:
az servicebus topic subscription rule create --resource-group myresourcegroup --namespace-name mynamespace --topic-name mytopic --subscription-name mysubscription --name myrule --filter-sql-expression "myproperty='myvalue'"

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

ID: 6fd5960a-ea47-7542-6837-3e4e49e95d0a
Version Independent ID: c8a9f5b6-2a2f-4820-3be4-c87e3896a6b7
Content: az servicebus topic subscription rule
Content Source: src/command_modules/azure-cli-servicebus/azure/cli/command_modules/servicebus/_help.py
Service: service-bus
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Quoting behavior is shell-dependent and we do not generally attempt to alter it in the CLI. I read this as a general comment or observation vice a specific ask, so I will close this GitHub issue. If there is an ask, we can reopen it.


Don't generate a default export for ES modules that don't have one

I think this might fix #224

Oh, failing tests. Trying to run them locally, both current master and with my patch, I get an error like
/home/marijn/tmp/rollup-plugin-commonjs/test/test.js:50
async function executeBundle ( bundle, { context, exports } = {} ) {
      ^^^^^^^^
SyntaxError: Unexpected token function

Which seems like an acorn configuration issue? Will try to guess what's going wrong and rely on CI to test.

Fixed one of the tests, but the remaining failure is more involved -- it breaks because hasDefaultExport is (incorrectly) false for the sample module.exports = { default: 'foobar', __esModule: true }. Should we try to make it smarter, or is it, since this can never be determined with full accuracy, better to try and find an approach that doesn't break when the detection goes wrong?

Hm, this solution is not really coherent—it's mixing up two interpretations of what default export means (CJS module.exports vs ES export default), and it only fixed my use case by incident. Closing this PR, let's continue in #224


Allow multiple inline model comment blocks (Thompson method)

Probably by having Stata search for a given name on the first line of the block, rather than just the first one with "data {"

This is one of the problems with trying to embed one programming
language's program as a string in another programming language.  We
try to recommend not doing that, despite having some lingering examples
that do it that people then just copy.

On Aug 18, 2015, at 11:44 AM, Robert Grant<EMAIL_ADDRESS>wrote:
Probably by having Stata search for a given name on the first line of the block, rather than just the first one with "data {"
—
Reply to this email directly or view it on GitHub.


Thank you. I will change this in the next release.

Implemented with 84bcf7c67a048cbd19cd5fea1e91f459e5ed0695


Made some changes to deprecated selectors

I didn't fix everything cause I didn't know how to test it.  I just changed some of what atom was complaining about.

Thanks. In the 0.9.0 release. :+1:


Spring boot based project+knife4j has no offline document of swagger. json

Spring boot based project+knife4j has no off the shelf offline documents of swagger. json, only online documents, similar to this format. Yes No

Hi @zyd6,
If we interpet your problem correctly, you say that a Spring boot based project+knife4 does not have a swagger json available that CNFuzz can interpret?
Currently it is required for CNFuzz to function that the REST API in question publishes a swagger json, else CNFuzz does not understand how to fuzz the web api.
I hope this answers your question.

ok thanks


Improve interoperability with 3rd party libraries

🚀 Feature Proposal
Allow 3rd party libraries to use immerable feature without depending on immer package.
Motivation
I'm making a library that deals with immutable objects. One of the functions is like this: update(fn: (state: T) => T): void. My problem is that the state object may contain lazily computed getters, i.e.
{
  get someProp() {
    if (!propInitialized) initProp()
    return prop
  }
}

If an end-user use immer's produce to get a next state, it would forcibly evaluate all getters, which is not desirable. So I did a trick with inheritance and hide all getters behind a prototype. Now produce doesn't evaluate getters, but at the same time it requires immerable property on a state object. Also, I don't want to make users of my library to depend on immer package, so I can not directly import it in my lib.
Right now immerable is defined as a private symbol. A minor change of it to public would solve an issue.
Can this be solved in user-land code?
Yes, by changing just one line. Symbol() -> Symbol.for()
Example
// a file in my library

// no immer import

const immerable = hasSymbol
	? Symbol.for("immer-draftable")
	: ("__$immer_draftable")

// not a final code
export const wrap = (proto, own) => {
  const res = Object.assign(Object.create(proto), own)
  res[immerable] = true
  return res
}

The latest Immer version uses Symbol.for now


OpenVPN - Client Specific Overrides - Virtual network routes are not applied

Before you add a new report, we ask you kindly to acknowledge the following:

[x ] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x ] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue_

Describe the bug
A clear and concise description of what the bug is, including last known working version (if any).
If you set up an OpenVPN remote access (Client/Server) solution with TLS and "Client Specific Overrides" activated, the network routes for the additional IPv4 Tunnel Network and interfaces are not written to the routing table.
(1) If you join the VPN without Client Specific Overrides everything works fine.
(2) If you join the VPN with Client Specific Overrides the ipconfig is correctly applied and used by the VPN Client.
Reply-packets from other network devices addressed to the additional overwritten "IPv4 Tunnel Network" are sent to the Default Gateway instead of the source VPN interface.
For more details please visit the opnsense forum:
https://forum.opnsense.org/index.php?topic=25737.0
OPNsense version details:

OPNsense 21.7.5-amd64
FreeBSD 12.1-RELEASE-p21-HBSD
OpenSSL 1.1.1l 24 Aug 2021

Last known working version:

unknown

To Reproduce
Steps to reproduce the behavior:

Set the firewall rules under Firewall -> Rules for all interfaces to:

=> Allow ANY to ANY with ANY Service/Protocol

Create a new vpn server under VPN -> OpenVPN -> Servers

Device Mode: tun
Interface: WAN
Local port: 1194
Server Mode: SSL/TLS + UserAuth
Backend for authentication: LDAP via Synology NAS
TLS Authentication: Enabled (Auth+Enc)
IPv4 Tunnel Network: <IP_ADDRESS>/24
IPv4 Local Network: <IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24
Type-of-Service: true
Duplicate Connections: true
Dynamic IP: true
Address Pool: true
Topology: false
DNS Default Domain: true, lastname.local
DNS Servers: <IP_ADDRESS>
Force DNS cache update: true
Prevent DNS leaks: true
Force CSO Login Matching: true

Configure two users on your LDAP-Server:

=> prename.lastname

Configure a "Client Specific Override" for the second user:

servers: select the VPN server from above
diffrent IPv4 Tunnel Network: <IP_ADDRESS>/24
Redirect Gateway: true
Server Definitions: true
DNS Default Domain: lastname.local => same as in VPNserver settings
diffrent DNS Servers: <IP_ADDRESS>

Connect to the vpn-server with the second user with CSP profile

Expected behavior
A clear and concise description of what you expected to happen.
Both users should be able to communicate with other network devices.
Instead the user with active CSP cannot receive reply packets, because the firewall routes them to the default gateway.
Network <IP_ADDRESS>/24 is an unknown network and interface <IP_ADDRESS>/32 is not known by the firewall.
Describe alternatives you considered
A clear and concise description of any alternative solutions or workaround you considered.
I´ve tried to manually add the routes for the <IP_ADDRESS>/24 network, but thats not permitted.
I´ve tried it with VIPs linked to the ovpn interface, but that had no impact.
Screenshots
Feel free to ask me, if you need some specific details.
Relevant log files
If applicable, information from log files supporting your claim.
Feel free to ask me, if you need some specific details.
Additional context
Add any other context about the problem here.
Nothing to add.
Environment
Software version used and hardware type if relevant, e.g.:

OPNsense 21.7.5-amd64

FreeBSD 12.1-RELEASE-p21-HBSD

OpenSSL 1.1.1l 24 Aug 2021

Intel(R) Celeron(R) CPU J3455 @ 1.50GHz (2 cores)

Virtual Machine on a Synology DS1019+ device

most likely same as https://github.com/opnsense/core/issues/5296, in which case the solution can be found in the ticket.

most likely same as #5296, in which case the solution can be found in the ticket.

Hello Schellevis,
thank you for your fast reply.
I´ve searched trough all cases, before I´ve created this ticket.
In Ticket #5296 the solutions says:
=> Activate "Force CSO Login Matching"
I want to refer to the settings section for the vpn server in my ticket, where I mentioned that this option is set to true.
The ip settings are also correctly set at client side. I did a packet capture and I saw, that it seems to be a routing problem.
Best regards

To make things more clear I have added a draw of the vpn traffic flow:
green: packet is sent, path is correct
red: packet is coming back, path turns wrong
purple: path that I would expect to happen
No NAT in between. IP adresses in the packet are correct set.

Just dropping some notes here, but the most important part in the other ticket actually is (https://github.com/opnsense/core/issues/5296#issuecomment-948329595)

Best check the openvpn logs after login, since client specific overrides can be dynamic (radius for example), these are generated during login.

If you're using client specific overrides, knowing the are being generated and used is the most important part in my humble opinion.

Here´s a full OpenVPN-Log with replaced personal data.
CSO part begins at line 3304 user you should focus on is prename1.lastname.
openvpn_cleared.log
For me there is nothing special to see. Everything looks correct.
@noseshimself
I think this is the cause of the error. You probably have the same problem.

The /32 CIDR should just indicate that its a single IP instead of a whole network. On some devices you need to specify it that way. Just forgot to add the /32 to the Default Gateway and OPNsense IP in the drawing. Another fail of my side is that the random host in reality is behind the default gateway which holds the static backroutes to the opnsense for the vpn. But traffic flow is fine till packets come back from destination host to vpn source over opnsense.

ZIP-File in the attachment contains a packet capture from WAN and OVPN interface.
I´ve started a Domain Lookup from my mobilephone which is connected from vpn with CSO active.
Lookup is against Google Public DNS-Server <IP_ADDRESS> searching for DNS-Records of www.google.de.
The capture clearly shows answer packets arrive at WAN interface, but they are not forwarded/routed to the ovpn interface from opnsense itself.
Packetcapture.zip

reading the original issue again, I'm not sure if the assumption that a route should be created is correct. The tunnel network itself is point to point, so it will only accept traffic originating from <IP_ADDRESS> to the other end (easy to test using ping from the machine and bind to the openvpn interface).
You could try to add <IP_ADDRESS>/24 as remote network as well, manually register routes using the advanced text field or use static routes.

reading the original issue again, I'm not sure if the assumption that a route should be created is correct. The tunnel network itself is point to point, so it will only accept traffic originating from <IP_ADDRESS> to the other end (easy to test using ping from the machine and bind to the openvpn interface).

The openvpn interface is not selectible from the list at the diagnosis tools:

If the vpn tunnel would only accept source traffic from <IP_ADDRESS> (VPN Gateway), opnsense should do a NAT.
But instead (as seen in the packet capture) the real vpn-client-address <IP_ADDRESS> is used.
Or did you mean something diffrent? Maybe I can´t follow you here at the moment.

You could try to add <IP_ADDRESS>/24 as remote network as well, manually register routes using the advanced text field or use static routes.

Register as remote network
I haven't tried this yet, thinking that this option is only for S2S VPN tunnels.
But I will soon give you an answer on this.
The advanced text field
"This option will be removed in the future due to  being insecure by nature. In the mean time only full administrators are  allowed to change this setting."
Static routes
The OpenVPN interface is not selectible from the list while configuring a gateway. A gateway is needed to create a static route entry. I´ve tried that before.

You could try to add <IP_ADDRESS>/24 as remote network as well[...]

Just tried that. It dosn´t work. Same problem still exists.

Static routes
The OpenVPN interface is not selectible from the list while configuring a gateway. A gateway is needed to create a static route entry. I´ve tried that before.

You can assign the interface in Interfaces->Assignments, after which you should also be able to ping from it by the way

You can assign the interface in Interfaces->Assignments, after which you should also be able to ping from it by the way

Yes. I´ve already assigned it. But I also needed to enable the interface itself. Last time i did this, it messed up with non accessible network devices. This time it´s the same.

When the ovpn interface is set to enable, OPNsense applies NAT to all VPN-devices and routes the traffic back to the default gateway. Even users without CSP are not able to ping or use devices from the vpn.

Same thing happens, if I directly try to ping my smartphone from VPN-Interface itself:

PING-Requests for my phone (in this case <IP_ADDRESS>) go to the MAC-Adress of my default gateway.


Add support for source links on GitHub enterprise instances

This adds support for GitHub Enterprise source URLs found in the list of git ls-remote --get-url.
The updated regex checks for URLs like github.acme.com instead of just github.com, and then uses the matched hostname when generating the source URLs.
I didn't add any tests for this as I'm not sure what your testing strategy is/I couldn't find a testing file for just this module. Happy to try and add this in though if required!
Should be backwards compatible with old URLs.
Fixes https://github.com/TypeStrong/typedoc/issues/249, which was closed in favour of https://github.com/TypeStrong/typedoc/issues/129.
This doesn't entirely solve https://github.com/TypeStrong/typedoc/issues/129, but closes the gap on allowing GHE to work out of the box.

I had a look at writing some tests, and can get one that would test that it defaults to github.com, but I can't work out how to stub out the internal ShellJS module and make it return whatever I want (so I could fake having a certain remote on a git repo):
import * as github from './../lib/converter/plugins/GitHubPlugin';
import Assert = require('assert');

describe.only('GitHubRepository', function() {
    let repository = new github.Repository('', '');

    describe('Application', function() {
        describe('contructor', function() {
            it('must default to github.com hostname', function() {
                Assert.equal(repository.gitHubHostname, 'github.com');
            });
        });
    });
});

Any ideas @aciccarello ?

I figured it out, with a small refactor. Should be good to go @aciccarello!

@aciccarello Any thoughts on this? Thanks!

Sorry for not following up on this @tomratcliffe. I'm hoping to look at it this week.

Thanks for your contribution @tomratcliffe!


fix: modify wait conditions

modify wait conditions so that everything spins up with make all-up
delete resources on teardown, fixing problems with kind cluster deletion
shorten jq command by filtering on namespace==default
remove line breaks in the middle of jq command which were causing issues for me
clean up README
add extra port mappings to kind config, allowing services to be exposed via nodeport for kind demo
add nodeport for redpanda console, removing need to port forward for demo

That s awesome


Launching BIDScoin 3.7.0 app from the menu tested

I tested the launching of BIDScoin 3.7.0 from the menu. The main utils (bidsmapper, bidscoiner) seem to work fine.
Can be included in next release.

ok, I added it to the next release: https://neurodesk.github.io/docs/neurodesktop/release-history/


Cleanup python generation

Remove some trailing whitespace
Slightly sort imports
Replace is_oneway() calls with a bool

Thanks for your patch @jamesbroadhead, in order for us to accept a pull request we need to have a jira ticket associated with it. Please see our contributing guide at http://thrift.apache.org/docs/HowToContribute


mbedtls: 2.9.0 -> 2.10.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/mbedtls/versions.
These checks were done:

built on NixOS
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_udp_proxy_wrapper.sh had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_aescrypt2 passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_crypt_and_hash had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_generic_sum had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_hello passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_dh_client had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_dh_genprime had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_dh_server had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ecdh_curve25519 passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ecdsa had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_gen_key had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_key_app passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_key_app_writer had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_mpi_demo passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_pk_decrypt passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_pk_encrypt had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_pk_sign had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_pk_verify had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_decrypt had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_encrypt had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_genkey passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_sign passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_sign_pss had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_verify had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_rsa_verify_pss had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_gen_entropy passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_gen_random_ctr_drbg passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_gen_random_havege passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_dtls_client had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_dtls_server had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_mini_client had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_client1 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_client2 had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_fork_server had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_mail_client passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_server had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_server2 had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_benchmark passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_selftest had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_ssl_cert_test passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_udp_proxy had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_zeroize had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_pem2der passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_strerror passed the binary check.
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_app had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_req had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_write had a zero exit code or showed the expected version
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_crl_app passed the binary check.
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_req_app passed the binary check.
18 of 49 passed binary check by having a zero exit code.
0 of 49 passed binary check by having the new version present in output.
found 2.10.0 with grep in /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0
directory tree listing: https://gist.github.com/a14a6f7f932021b4c72aa2a56d3cafc8
du listing: https://gist.github.com/d1d619564617178d839c99f546be2911

meta.description for mbedtls is: '"Portable cryptographic and SSL/TLS library, aka polarssl"'.
cc @wkennington @fpletz for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout cf40f4cb93c81399fce16b4838e43939c1c8e890 && nix-shell --pure -I nixpkgs=. -p mbedtls

Success on x86_64-linux (full log)
Attempted: mbedtls
Partial log (click to expand)
shrinking /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_app
shrinking /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_req
shrinking /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_cert_write
shrinking /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_crl_app
shrinking /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin/mbedtls_req_app
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/lib  /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0/bin
patching script interpreter paths in /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0
checking for references to /build in /nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0...
/nix/store/q18bxf7hgbdqa9w5di6ndcf3xs28r6h5-mbedtls-2.10.0

Success on x86_64-darwin (full log)
Attempted: mbedtls
Partial log (click to expand)
test_suite_xtea ................................................... PASS
------------------------------------------------------------------------
PASSED (61 suites, 6533 tests run)
installing
install flags: SHELL=/nix/store/9gghkkqhn6v7dvpf2319qvrxkkw03vwr-bash-4.4-p19/bin/bash SHARED=1 DLEXT=dylib DESTDIR=\$\{out\} install
post-installation fixup
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/prhwrmr7sh4bizvsig0dfxdx6kd9jjsn-mbedtls-2.10.0/lib  /nix/store/prhwrmr7sh4bizvsig0dfxdx6kd9jjsn-mbedtls-2.10.0/bin
patching script interpreter paths in /nix/store/prhwrmr7sh4bizvsig0dfxdx6kd9jjsn-mbedtls-2.10.0
/nix/store/prhwrmr7sh4bizvsig0dfxdx6kd9jjsn-mbedtls-2.10.0

Success on aarch64-linux (full log)
Attempted: mbedtls
Partial log (click to expand)
shrinking /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/bin/mbedtls_crypt_and_hash
shrinking /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/bin/mbedtls_aescrypt2
shrinking /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/lib/libmbedcrypto.so.2
shrinking /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/lib/libmbedx509.so.0
shrinking /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/lib/libmbedtls.so.10
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/lib  /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0/bin
patching script interpreter paths in /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0
checking for references to /build in /nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0...
/nix/store/7sappflz76sfxjp6n9ncgwnr45xr7307-mbedtls-2.10.0


Various bug fixes

Codecov Report

Merging #626 (824ca7f) into dev (45f7f87) will decrease coverage by 1.08%.
Report is 51 commits behind head on dev.
The diff coverage is 40.68%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##              dev     #626      +/-   ##
==========================================
- Coverage   72.03%   70.96%   -1.08%
==========================================
  Files         121      122       +1
  Lines       16146    16508     +362
==========================================
+ Hits        11631    11715      +84
- Misses       4515     4793     +278


Adding a NotFound Handler to a route group

Hi,
I'm trying to add a specific NotFoundHandler (or NotAllowedHandler) to a specific group of routes. My use case is that I have an API sitting at /api and a frontend website at / and I want to be able to separate the not found handlers : one will be a JSON response with informative info, the other a nice HTML template with a "Ooops" message in it.
Is this possible ?
Thanks a lot

You should have on notFoundHandler that handles both cases but provides a different response for each.
When a handler is being invoked, it gets passed Request, Response and Exception. You could have logic that looks at the Uri and decides whether it returns a JSON formatted response or calls your renderer to display some HTML depending on the path.
class ErrorHandler
{
    public function __invoke(Request $request, Response $response, $exception)
    {
        $uri = $request->getUri();
        $path = $uri->getPath();
        $payload = [
            'code' => $exception->getCode(),
            'message' => $exception->getMessage();
        ];

        if (strstr($path, '/api')) {
            return $response->withJson(
                $payload,
                $exception->getCode(),
                JSON_PRETTY_PRINT
            );
        } else {
            return $this->renderer->render($response, "/myError.php", $payload);
        }
    }
}

Hi — thanks for your response. It definitely works but I can't use my middleware that does the same thing for normal pages, so it feels like duplicating the code for nothing. I was hoping that one could attach the handler per group or per route, a bit like a middleware.
Guess I'll create a kind of general service to stay DRY
thanks again
BR

Would you be able to post a sample of your middleware so we can better understand what it does? I have a feeling that some code may not be in the right place hence why you'd have to duplicate it in the error handler.

I'm using https://github.com/akrabat/rka-content-type-renderer to render different formats, and I would like my notFound or notAllowed handler to use them too.
Here is some code so you can understand the whole picture. The part I have a feeling I will need to duplicate is the middleware, that checks the format header, modify it according to params in case and do a few more things to the response afterwards
 $this->slimApp->group('/api', function () use ($renderer) {
        $this->get('/platforms', function($request, $response) {
             $platforms = /* some array with data */
             $response = $renderer->render($request, $response, $data);
             return $response->withStatus(200);
       });
       /* more api routes & methods */
  })->add(function ($request, $response, $next) {
        $request = $request->withHeader('Accept', 'application/json'); // default
        $format = $request->getParam('format');
        if ($format) {
            $mapping = [
                'html' => 'text/html',
                'xml' => 'application/xml',
                'json' => 'application/json',
            ];
            if (isset($mapping[$format])) {
                $request = $request->withHeader('Accept', $mapping[$format]);
            }
        }

        $response = $next($request, $response);

       /* Some other things I do on the response */

        return $response;
  });

Thanks a lot for your time !

I think that you are using the wrong approach here.
I would use global middleware instead of route specific middleware
If you could put a gist with all the moving parts together I would be able to assist you better also.
Here is an example:
class ContentTypeMiddleware
{
    private $defaultContentType = 'application/json';
    private $allowedContentTypes = [
        'html' => 'text/html',
        'xml' => 'application/xml',
        'json' => 'application/json',
    ];

    public function __invoke(Request $request, Response $response, $next)
    {
        $request = $this->resolveContentType($request);

        /**
         * Process All Middleware
         */
        $response = $next($request, $response);

        /**
         * Set Accept Header Before Responding To The Request
         */
        $contentType = $request->getAttribute('contentType');
        $response = $response->withHeader('Accept', $contentType);

        return $response;
    }

    private function resolveContentType(Request $request)
    {
        $contentType = $this->defaultContentType;
        $resolvedContentType = $request->getParam('format');

        if (
            $resolvedContentType
            && isset($this->allowedContentTypes[$resolvedContentType])
        ) {
            $contentType = $resolvedContentType;

        }

        /**
         * Here we add an attribute to the request object in case we need to modify the final content type elsewhere in our application
         * The final Accept header will be set from this variable
         */
        $request->withAttribute('contentType', $contentType);

        return $request;
    }
}

/**
 * Add our middleware globally so every request will be processed with it
 */
$app = new \Slim\App($settings);
$app->add(new ContentTypeMiddleware);

/**
 * Routes
 */
$app->group('/api', function () use ($renderer) {
    $this->get('/platforms', function ($request, $response) {
        $data = [];
        $response = $renderer->render($request, $response, $data);
        return $response->withStatus(200);
    });
});

/**
 * Run App
 */
$app->run();

Thanks for the code, I understand the concept of the $contentType var that can be modified in the route to change the behavior, but my problem is within the notFound handlers, not the conventional routes.
In fact the underlying problem is that the notFound handlers do not have access to the route (it's empty, by design), so I cannot decide whether or not the notFound was triggered inside the api group or not. That's why I wanted a notFound handler per group, but it doesn't exist;
Basically I'll do something like that in the middleware and in the notFound Handler I guess, though it's clearly not ideal :
$isApiRoute = (substr($request->getUri()->getPath(), 0, 4) === 'api/');

But it works. I have to duplicate the code, that's what I wanted to avoid but it seems unavoidable in my case.

Did you set determineRouteBeforeAppMiddleware to true in your App settings?
That way you will have access to the route object in your middleware.
Also, if you did a gist with the relevant parts of your code, it would be much easier for me to help.
There's absolutetly no need to repeat code.

This issue is really old. I believe it has also been answered; so I am going to close it. if you feel as if you still need support please reopen.


How to represent Other Contact information

How should we represent the fields other contact name / other contact phone / other contact relationship in the call modal?

I think that should just pull the additional information if available. Pretty straightforward.
Maybe something like a smaller title like “Alternate:  PersonZ (xxx-xxx-xxxx) - Mother" directly under the PT’s name and phone in the modal. - @lwaldsc @eheintzelman

How about additional instructions after "Call [PT NAME] now" and before the phone number.
If the patient is the primary contact, something like, "You can call this patient directly."
If other contact, something like, "Mary Miller (mother) is the primary contact for this patient."
Do we need to have a way to identify what phone number is primary?
Would like design input from @mebates

Having this in place for deploy would be helpful I think -- tagging as such

Let's roll with this as follows:

If there's an other contact on the patient, display '{Other contact name} ({other contact relationship}' is the primary contact for this patient -- phone {other contact phone}' in red
Otherwise do nothing

I think we can fine tune this down the line, and would prefer it be in place for showtime.


policy based or claim based on pure web assembly client

Hi,
(experimenting with blazor - new to it, and looking to see if I can migrate an existing site to blazor)
this page is great and really helpful! - but is there any info or details on implementing policy based authorisation when you are in a purely client based app. So, where you don't have the startup.cs to define policies? (can they be defined somewhere in a client app?)
If using just claims instead (which I can happily extract in a purely client based scenario without issue) - then is seems that the AuthorizeView (wonderful as it is) - only accepts a policy (instead of a required claim). If the authorize view could accept a collection of required claims - then I could still use the that component to achieve something similar to a policy (if not then I think I need to create either a custom component)

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

ID: c9942b0a-a7fb-0d34-9201-af0963affa9e
Version Independent ID: 19770710-5225-a1ea-e082-65da6ba4a49a
Content: ASP.NET Core Blazor authentication and authorization
Content Source: aspnetcore/security/blazor/index.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @AlexSapple ... Yes! ... and I've actually been working all day today on new guidance for part of that scenario.
I'm going to put up an issue tomorrow with many details about using Azure AD groups and roles claims for authz in Blazor WebAssembly apps (both standalone and the hosted types).
I'll leave your email in my Inbox and then ping you tomorrow on the issue that I put up. The issue is going to be for discussion with management on what and where we'll be covering the concepts (and even if I'm doing it right! :smile:).
Suffice to say here for now ... yes, you can add policies ... like this :point_down:
builder.Services.AddAuthorizationCore(options =>
{
    options.AddPolicy("CustomPolicy", policy => policy.RequireClaim("groups", "213b6935-a839-49e8-86e0-acc7d1cd1582"));
});

... in Program.Main. That one that I just put there shows how to use a security groups claim from Azure AD (a custom group created for an app) that comes down when the manifest is updated to groupMembershipClaims is set to SecurityGroup. Anyway ... that's just a tidbit ... I'll have a lot more detail and examples on the issue for discussion tomorrow.
I'm going to close this, but I will ping u tomorrow. I'm sure you'll find my post tomorrow afternoon helpful, especially if you're going to be doing anything with Azure AD and Blazor WebAssembly. Caveat tho: I do need engineering to look it over and make sure that I'm not creating any code smells 👃 ... actually ... when it comes to security, I sometimes create more of a :poop: code STINK :poop: 😵 ... We'll see soon enough!

Thanks so much,
that's brilliant - and really appreciated the quick reply and detailed answer!! - really great :)
regards,
Alex.

From: Luke Latham<EMAIL_ADDRESS>Sent: 06 April 2020 22:42
To: dotnet/AspNetCore.Docs<EMAIL_ADDRESS>Cc: AlexSapple<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dotnet/AspNetCore.Docs] policy based or claim based on pure web assembly client (#17633)
Hello @AlexSapplehttps://github.com/AlexSapple ... Yes! ... and I've actually been working all day today on new guidance for part of that scenario.
I'm going to put up an issue tomorrow with many details about using Azure AD groups and roles claims for authz in Blazor WebAssembly apps (both standalone and the hosted types).
I'll leave your email in my Inbox and then ping you tomorrow on the issue that I put up. The issue is going to be for discussion with management on what and where we'll be covering the concepts (and even if I'm doing it right! 😄).
Suffice to say here for now ... yes, you can add policies ... like this 👇
builder.Services.AddAuthorizationCore(options =>
{
options.AddPolicy("CustomPolicy", policy => policy.RequireClaim("groups", "213b6935-a839-49e8-86e0-acc7d1cd1582"));

});
... in Program.Main. That one that I just put there shows how to use a security groups claim from Azure AD (a custom group created for an app) that comes down when the manifest is updated to groupMembershipClaims is set to SecurityGroup. Anyway ... that's just a tidbit ... I'll have a lot more detail and examples on the issue for discussion tomorrow.
I'm going to close this, but I will ping u tomorrow. I'm sure you'll find my post tomorrow afternoon helpful, especially if you're going to be doing anything with Azure AD and Blazor WebAssembly. Caveat tho: I do need engineering to look it over and make sure that I'm not creating any code smells 👃 ... actually ... when it comes to security, I sometimes create more of a 💩 code STINK 💩 😵 ... We'll see soon enough!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dotnet/AspNetCore.Docs/issues/17633#issuecomment-610052255, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHHSCGPQH7MKIKBTNM64WCLRLJEEBANCNFSM4MCTSJYA.


implement polynomial sqrt

https://math.stackexchange.com/questions/324385/algorithm-for-finding-the-square-root-of-a-polynomial

https://math.stackexchange.com/a/1854191/118612 into Sum::Sqrt


include/zone/export.h may not get created if GNU make uses --shuffle mode

Hi, I am investigating a bug in Gentoo, #936119, which is happening in an automated tinderbox build where the include/zone/export.h file isn't getting created during the compilation phase if GNU make employs its --shuffle option, which will cause it to "simulate non-deterministic build order in parallel makefiles".
I suspect the tinderbox build does this as a build fuzzer to find obscure failure modes, but it got me looking at the nature of this one file, and I'm puzzled why it's being created at build time by the Makefile, when there doesn't seem to be anything conditional about it.  The file should always get created if the normal flow of make targets happen (all -> libzone.a -> EXPORT_HEADER).  Nor is the #include line in include/zone.h that pulls in zone/export.h itself conditional.  So I feel like this file should always exist and the specific target that creates it in the Makefile logic be removed, but I wanted to see if there's some undocumented reasoning why it's set up this way first.

Hi @Kumba42! The has to with how simdzone is included in NSD. If built as a standalone project via CMake, the export header is generated using GenerateExportHeader so that dllexport/dllimport on Windows and is automatically correct (dll vs. lib). On other platforms it takes care of the visibility attribute, though it's not as important to actually use the library. We chose to include simdzone in NSD as a submodule and link it statically for convenience. Of course, in that scenario we don't care about visibility and so I simply added a Makefile rule to create a dummy header. Looking at the Makefile, I think making the *OBJECTS targets depend on the header rather than libzone.a should solve the problem?

Looking at the Makefile, I think making the *OBJECTS targets depend on the header rather than libzone.a should solve the problem?

I gave this a test and used the same shuffle seed in the failure log I have, and that doesn't appear to work.  It failed compiling on a different object file with that change (src/haswell, specifically).  What does appear to work with that seed and other random seeds is making $(EXPORT_HEADER) the first dependency of the 'all' target, before 'libzone.a':
--- a/simdzone/Makefile.in.orig
+++ b/simdzone/Makefile.in
@@ -33,7 +33,7 @@ EXPORT_HEADER = include/zone/export.h

 .PHONY: all clean

-all: libzone.a
+all: $(EXPORT_HEADER) libzone.a

 clean:
 	@rm -f .depend
@@ -45,7 +45,7 @@ distclean: clean
 realclean: distclean
 	@rm -rf autom4te*

-libzone.a: $(EXPORT_HEADER) $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)
+libzone.a: $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)
 	$(AR) rcs libzone.a $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)

 $(EXPORT_HEADER):

Not sure if this would impact other build targets, though.  I have a FreeBSD system that I tested this change on, and seems to be okay with it.

I think if you put it as a dependency of all it doesn't signal that it's needed to compile the objects(?)
Can you give this a try?
diff --git a/Makefile.in b/Makefile.in
index 5cf81a7..4754591 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -50,22 +50,22 @@ maintainer-clean: realclean
 devclean:
        @rm -rf config.h.in configure

-libzone.a: $(EXPORT_HEADER) $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)
+libzone.a: $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)
        $(AR) rcs libzone.a $(OBJECTS) $($(WESTMERE)_OBJECTS) $($(HASWELL)_OBJECTS)

 $(EXPORT_HEADER):
        @mkdir -p include/zone
        @echo "#define ZONE_EXPORT" > include/zone/export.h

-$(WESTMERE_OBJECTS): .depend
+$(WESTMERE_OBJECTS): $(EXPORT_HEADER) .depend
        @mkdir -p src/westmere
        $(CC) $(DEPFLAGS) $(CPPFLAGS) $(CFLAGS) -march=westmere -o $@ -c $(SOURCE)/$(@:.o=.c)

-$(HASWELL_OBJECTS): .depend
+$(HASWELL_OBJECTS): $(EXPORT_HEADER) .depend
        @mkdir -p src/haswell
        $(CC) $(DEPFLAGS) $(CPPFLAGS) $(CFLAGS) -march=haswell -o $@ -c $(SOURCE)/$(@:.o=.c)

-$(OBJECTS): .depend
+$(OBJECTS): $(EXPORT_HEADER) .depend
        @mkdir -p src/fallback
        $(CC) $(DEPFLAGS) $(CPPFLAGS) $(CFLAGS) -o $@ -c $(SOURCE)/$(@:.o=.c)
        @touch $@

@Kumba42, I issued a PR for this. I believe it'd be the fix for the issue, but if I build just simdzone with the --shuffle flag it doesn't trigger. I'll test by building as part of NSD and report back.

A quick test locally didn't trigger the issue. I'll merge #218 to the main branch. Please let me know if it works for you, it'd be good to have this fixed in the upcoming 4.10.1 NSD release.

I think if you put it as a dependency of all it doesn't signal that it's needed to compile the objects(?)
Can you give this a try?

This one works.  My original idea actually didn't -- forgot to start w/ a clean directory when doing my tests.

Happy to hear it's fixed. Thanks for taking the time to report :+1:


Adjust DevHub Typography and configure Typography.js

After the implementation of typography.js the typography across the devhub platform was changed.
To do:

Figure out how typography.js works to customize site wide typography and implement these changes on Devhub/Design System
Work with @sheaphillips to figure out how this configuration works

This configuration would ultimately be the typography package available to product teams as one option.
Definition of done:

Typography.js is built to reflect the typography guidance outlined on the design system
Typography across DevHub is consistent

@orinevares Can you make sure any reference to google api for Noto is replaced with the font files?

Yes, I was reading and seems like this is the way to embed font file locally.
https://stackoverflow.com/questions/28279989/multiple-font-weights-one-font-face-query
It seems to get messy and repetitive if we were to include this on every CSS sheet for every component so I'm thinking of doing one CSS file for the all the files and including it on the typography page while deleting all the google references. Thoughts? @dlevineBC

Is this because the iframes can't reference files outside of the frame? Can the font just be called from the typography.js instance?

I'll have to follow up with Shea on this. He's away until Monday. I'm also thinking how to present the locally hosted fonts on the documentation code for users of the design system to see.

Hi everyone,
I updated the typography.js file to include the proper typographic scale. (accidentally committed to master - sorry Patrick). The changes are not reflected on DevHub and after looking into this briefly with Shea last week it seems like there is some more granular CSS that is overwriting the typography.js specifications. I can start an initial look into possible sources of the setting being overwritten but @patricksimonian  if you know exactly where this might be let me know.


Phpsmoke

Codecov Report

Merging #1610 into master will increase coverage by 0.07%.
The diff coverage is 96.35%.

@@             Coverage Diff              @@
##             master    #1610      +/-   ##
============================================
+ Coverage     86.77%   86.85%   +0.07%
- Complexity     4168     4184      +16
============================================
  Files           408      408
  Lines         16711    16785      +74
  Branches       1797     1802       +5
============================================
+ Hits          14501    14578      +77
+ Misses         1715     1709       -6
- Partials        495      498       +3

Impacted Files
Coverage Δ
Complexity Δ

.../codegen/viewmodel/testing/SmokeTestClassView.java
80% <ø> (ø)
3 <0> (ø)
:arrow_down:

...ransformer/java/JavaGapicSampleAppTransformer.java
47.61% <100%> (ø)
6 <1> (ø)
:arrow_down:

...transformer/php/PhpPackageMetadataTransformer.java
100% <100%> (ø)
4 <1> (ø)
:arrow_down:

...nsformer/java/JavaGapicSurfaceTestTransformer.java
98.27% <100%> (ø)
31 <0> (ø)
:arrow_down:

...e/api/codegen/transformer/InitCodeTransformer.java
94.49% <100%> (ø)
63 <0> (ø)
:arrow_down:

...oogle/api/codegen/util/ruby/RubyNameFormatter.java
95.45% <100%> (+4.54%)
17 <1> (+1)
:arrow_up:

...e/api/codegen/transformer/TestCaseTransformer.java
92.76% <100%> (ø)
38 <0> (ø)
:arrow_down:

...m/google/api/codegen/transformer/SurfaceNamer.java
75.46% <75%> (-0.01%)
180 <0> (ø)

...e/api/codegen/transformer/php/PhpSurfaceNamer.java
90.14% <88.88%> (-0.6%)
38 <5> (+5)

...le/api/codegen/gapic/MainGapicProviderFactory.java
93.11% <92.3%> (ø)
14 <0> (ø)
:arrow_down:

... and 7 more

Continue to review full report at Codecov.

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


default allow-nothing AuthorizationPolicy has highest precedence

Bug Description
I'm trying to apply allow-nothing AuthorizationPolicy policy in the istio-system namespace which is supposed to be applied for all namespaces and block all requests which are not explicitly allowed with AuthorizationPolicy.
Or at least this is my understanding according to these docs:

https://istio.io/latest/docs/concepts/security/#allow-nothing-deny-all-and-allow-all-policyThe following example shows an ALLOW policy that matches nothing. If there are no other ALLOW policies, requests will always be denied because of the “deny by default” behavior.

Note the “deny by default” behavior applies only if the workload has at least one authorization policy with the ALLOW action.

https://istio.io/latest/docs/concepts/security/#policy-targetA policy applies to the namespace in the metadata/namespace field. If set its value to the root namespace, the policy applies to all namespaces in a mesh. The value of the root namespace is configurable, and the default is istio-system.

When I try to access my app which is exposed using gateway and virtual service I get RBAC: access denied which tells me that the namespaces AuthorizationPolicy is not working or it has has lower priority.
Steps to reproduce:

install istio 1.11.3
apply allow-nothing policy to istio-system namespaceapiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: allow-nothing
spec:
  action: ALLOW

apply allow AuthorizationPolicy for some deployment in different namespaceapiVersion: security.istio.io/v1beta1
kind: AuthorizationPolicy
metadata:
  name: enable-access
  namespace: test-app
spec:
  action: ALLOW
  rules:
  - to:
    - operation:
        methods: ["GET"]

Is this a bug or I'm missing something?
Version
k version --short
Client Version: v1.21.0
Server Version: v1.21.5

istioctl version
client version: 1.11.3
control plane version: 1.11.3
data plane version: 1.11.3 (4 proxies)

Additional Information
No response

I think this works as expected. Deny all policy applies to all proxies in the mesh, including the ingress gateway. The allow rule only apply to the sidecars within test-app namespace. The access denial for your request is from the ingress gateway, where no allow rule is applied.

thanks for the confirm!


Need help in data processing

Hello, your work is wonderful and it seems helpful to me in aav screen.
However, when I run your code, I found that there is demo-read-count only, and most of the reads are 1, which is not a good dataset for learning, did I do something wrong? I process the code using the following commands:
python ../src/pre_process.py demo pre -r -c -p 2
python ../src/pre_process.py demo post -r -c -p 2

The output of "demo_pre_counts.csv" is something like this:
|seq|	count|
----|-----|
1	SHPKRC*	|35
2	HQQPEHR	|10
3	PPTTRAP	|5
4	SSWHSFN	|2
5	TVTNCLI	|2
6	LRYHSLA	|2
7	SRICFLA	|2
It's very strange, for the count is too small to use.
Can you give me a help or update a new demo?

Hello, your work is wonderful and it seems helpful to me in aav screen.
However, when I run your code, I found that there is demo-read-count only, and most of the reads are 1, which is not a good dataset for learning, did I do something wrong? I process the code using the following commands:
python ../src/pre_process.py demo pre -r -c -p 2
python ../src/pre_process.py demo post -r -c -p 2

The output of "demo_pre_counts.csv" is something like this:
seq	count
1 SHPKRC*	35
2 HQQPEHR	10
3 PPTTRAP	5
4 SSWHSFN	2
5 TVTNCLI	2
6 LRYHSLA	2
7 SRICFLA	2
It's very strange, for the count is too small to use.
Can you give me a help or update a new demo?

Hi! I am having the same issue. Did you get that fixed? Hope to hear from you, thanks!

这是来自QQ邮箱的自动回复

您好，已收到邮件。Mail received

Hi, apologies for the slow response. The demo data files included in the code release are small “toy” example files that each contain only 1000 reads and are not the full pre/post sequencing datasets. However, if you were to apply the code to your sequence datasets, it should work as expected. We have elected not to include our full pre/post sequencing datasets due to proprietary reasons. That is, disclosure of sequences would preclude any subsequent IP protection of those sequences, which would as a result prevent any of them from being used in clinical development to help patients. We hope you find the code helpful in your research.


Add a top-level CLI for search

This PR adds a first version of a top-level CLI for running search. It supports all single-step models integrated so far, as well as both MCTS and Retro* as choices for the search algorithm. Both of these algorithms have reasonable defaults set; for now these don't depend on the single-step model, but after tuning I will add model-specific defaults.
As for the output from search.py, there are two considerations:

On one hand, it's convenient for search.py to have options to extract and plot some routes right away, in order to be able to get search results by running a single script.
On the other hand, after investigating the outputs, one may realize that while the search might have been successful, the extraction parameters should be adjusted, to e.g. avoid certain reaction steps or extract further routes. Thus, it is useful to be able to rerun the extraction without redoing the search.

To get best of both worlds, I propose for search.py to both extract and plot some routes (unless num_routes_to_plot = 0) as well as dump the full graph (for optional further analysis or re-extraction).

Would it be good to add some stats across target molecules here (e.g., average reaction model calls or time cost for the first solution)?

I think this doesn't hurt; I can add it.


0.20版本windows打包和mac打包发现apk大小不一致！大佬们什么原因

同样的打包配置，我本地是windows本。服务器是mac本，用gradle assembleRelease命令打包，发现服务器打的apk包里的so库大小比windows大很多。哪位大佬知道？最初我以为是AS3.0自动压缩so导致，当我本地配置了不压缩后，重新打包还是和之前的大小一样大。
packagingOptions{
doNotStrip "/armeabi-v7a/.so"
}
另外，我发现自己本地打包时，下面的两个目录的so库大小也不一直。

感谢你的反馈，Weex目前是隶属于Apache Software Foundation的项目，因此在Gtihub渠道我们鼓励使用英文反馈问题。下面我将使用Google Trasnlate将你的问题翻译成英语，并以英语回答。

Question Description: 0.20 version of windows packaging and mac packaging found apk size is inconsistent! What are the reasons for us?

I can't tell you what happened exactly as I am not a committer of NDK, but generally speaking, this problem is caused by stripping. As you can see, the size of many shared libraries are different, not only Weex. Change /armeabi-v7a/.so to /armeabi-v7a/*.so will give you what you want.


Minimum Api Version is 21

It should be 18 atleast
Error:Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : uses-sdk:minSdkVersion 16 cannot be smaller than version 21 declared in library [com.hlab.fabrevealmenu:fab-reveal-menu:1.0.4] D:\gradle\caches\transforms-1\files-1.1\fab-reveal-menu-1.0.4.aar\cfbe3134ff7dab05e863daea447b358f\AndroidManifest.xml as the library might be using APIs not available in 16
Suggestion: use a compatible library with a minSdk of at most 16,
or increase this project's minSdk version to at least 21,
or use tools:overrideLibrary="com.hlab.fabrevealmenu" to force usage (may lead to runtime failures)

Hi @chnouman, please use older version 1.0.3 for support from api 16

with 1.0.3 it was giving error dear.