[BUG] Unable to scan with csv file from command line

Problem Area
[X ] Modernization Scanner: something went wrong...
Expected or Desired Behavior
I'm using the command line to perform a scan on a batch of sites in a csv file.
SharePoint.Modernization.Scanner.exe -i 12345678-abcd-abcd-abcd-123456789012 -z xyz.onmicrosoft.com -f xyz.pfx -x NotTheP@ss -t xyz -m WorkflowWithDetailsOnly -v sites.csv
Observed Behavior
The scanner initiates a complete tenant scan as if no csv file was specified.
Steps to Reproduce
- Start the scan from the ui with the csv file specified. No Problem
- Start the scan from the command line pointing to an inexisting csv file. Error: Failed to find csv file with urls. Please check file path provided.
- Start the scan from the command line pointing to a csv file. Full tenant scan starts.

Reproduced and confirmed by Microsoft. (version <IP_ADDRESS>)

@SVG4365
You need to drop the -t when you scope the scan via a CSV file

@jansenbe
Confirmed, Thank you!


Add syntax for module atoms

Add:
Example:
mod "Some.Module"

->
Some.Module

I'm not sure if I understand it correctly. Can you explain it? What is use case for that?

@Baransu Right now every uppercase type changes to snake case atoms:
Type -> :type. But sometimes in rare cases there is a need to express a module atom like Module, for example when passing a name to a process.
In Elixir module atoms are still regular atoms but they are:

Resolved through aliases
Prepended with Elixir.

Closed in favour of #140


[Proof] Introduce SparseMerkleRangeProof

Motivation
This proof intends to prove that a range of things exist in a sparse Merkle tree. Given that when restoring the state tree, we always go from left to right, so at any point in time a list of siblings on the right is sufficient to prove the everything on the left.
The verification is a bit complex... The basic idea is that when we have the full list of leaves for a sparse Merkle tree, we can compute the common prefix length of each adjacent key pairs and find out which pair consists of the left child and right child of the same parent. Then we can compute their parent and reduce the problem. Note that we are just doing this in unit tests to test the get_range_proof method, the real verification will be a little bit different.
Have you read the Contributing Guidelines on pull requests?
No.
Test Plan
CI.
Related PRs
None.

Have you read the Contributing Guidelines on pull requests?
No.

We should probably start taking this a little more seriously.
我不知道怎么读 seems better.
Jokes aside, I'd definitely like to give this a review before it ships.

:umbrella: The latest upstream changes (presumably 3d577356a92a364b2cf2549b9f6f488a44a27b2d) made this pull request unmergeable. Please resolve the merge conflicts.

:v: @wqfish can now approve this pull request

@bors-libra r=msmouse

:pushpin: Commit 936804e has been approved by msmouse

:hourglass: Testing commit 936804e8db56d309889798a8a63c94f443f46fa0 with merge d4ddf559195e6d124ec827eb5cd08344e922c865...

:hourglass: Testing commit 936804e8db56d309889798a8a63c94f443f46fa0 with merge 73f14ce0c94e9b50582e50fc49d37e08ba6a6756...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: msmouse
Pushing 73f14ce0c94e9b50582e50fc49d37e08ba6a6756 to master...


Add VPC Flow Logs capabilities

Description
This PR addresses issue #23 and adds the ability to enable VPC Flow Logs within the module.
The implementation tries to offer the user all the possibilities to configure Flow Logs while trying to keep the module interface as simple as possible.
This PR extends the complete VPC example with the default behaviour (push logs to CloudWatch while having the module create all the necessary resources for that), and adds 4 new Flow Logs specific examples that illustrate how other configurations can be achieved.
I made an implementation decision to keep the module interface simpler at the cost of having to run terraform twice (using -target) to make sure log destinations (or IAM role) exist before actually creating the VPC with Flow Logs enabled. The alternative would be to add at least two more boolean arguments to the module and then always specifying those in combination with providing actual log destination (or IAM role). I've kept that decision in a separate commit so it is easier to revert in case people find it better to have those extra boolean flags.

Hi, Miguel!
Thanks for this great pull-request!
There are just a few things which I'd like to change to make this more compatible with the rest. One of it is that there should be no need to run apply with -target. All examples should follow - init, plan, apply, destroy cycle.
Another one is that there is terraform-aws-s3-bucket module which can be used as an example.
I will update the code and fix a couple of minor spelling mistakes during this week.

Thanks for looking into this Anton. Please do let me know if I can help with the modifications you think should be made.

Hi, what's the hold up on this? Can i help with something?

Nothing from my part @nicolaevladescu. I think @antonbabenko still wants to work this out better before merging.

Yes, I started looking into it and have been testing it in detail earlier this week. I think we will get it merged during next week.

I've just tried the changes in this PR and think that it would be great if they could get incorporated into the VPC module.
Thanks for your work on this, @miguelaferreira!

I continue working on this pull-request.
I now need this feature for my paying customer who has to pass CIS - 2.9 – Ensure VPC flow logging is enabled in all VPCs.

🎉 v2.26.0 has been just released with VPC Flow Log supported.
Thanks @miguelaferreira for your work. I have combined several examples related to the VPC flow log into one and removed dependency on S3 bucket module, so that bucket should always be created outside of this module if the user wants to push logs there.
Please let me know if there are any issues.

@antonbabenko Updating to 2.26 results in an error during apply for me:
Error: Invalid index

  on .terraform/modules/default_vpc/terraform-aws-modules-terraform-aws-vpc-2ac8bf5/outputs.tf line 1008, in output "vpc_flow_log_id":
1008:   value       = aws_flow_log.this[0].id
    |----------------
    | aws_flow_log.this is empty tuple

The given key does not identify an element in this collection value.

Fixed in 8554bfd.
v2.27.0 has been just released.


If the disk size is specified as a decimal number the generated metad…

…ata.json file is invalid resulting in a broken vagrant box.  Wrapped this in the awk int() function to only print the integer part of the disk size.

add please comment to code
it is important information

Added a comment.  Let me know if its what you wanted to see or if you'd rather it be worded differently.

Thanks.
--
Josh Smith
KD8HRX
Email/jabber<EMAIL_ADDRESS>Phone:<PHONE_NUMBER>(c)
Sent from my iPhone.

On Oct 6, 2015, at 12:00 AM, Dmitry Vasilets<EMAIL_ADDRESS>wrote:
Merged #474.
—
Reply to this email directly or view it on GitHub.


pre_trained model of ResNet-50?

nice work!
Follow your implement of ResNet, could you provide the per_trained model of ResNet-50 and others ?  I just see ResNet-101 in your README.

Hi, we did not implement our U2PL with ResNet-50 backbone, so we could not provide checkpoint of R50.
Maybe you could try using official ResNets.


Can I pass in a <math> element and get back rendered node?

I’m rendering my math using a custom element that listens to an input of a <textarea>. MathJax doesn’t penetrate the shadow DOM when typesetting. So I’m wondering if I can simply pass in the <math> node that my custom element generates, receive the typeset <mjx-container> node and handle attaching it to the parent node my self?

With shadow roots being more widely available as time goes on, can we have a builtin solution for this?
For example I'd like to have a component like:
<text-math>
lim[x -> 0, 2*x + 3]
</text-math>

This component would have a human readable ASCII language, which would converted into mathml.

Currently the existing suggested solution on the other thread is pretty heavy weight.
It'd be nice if we could just do something like this:
const renderer = new MathJaxRenderer(this.#shadowRoot, { output: new SVG() });

// When child text content changes
renderer.setMathML(mathMLText);

@Jamesernator indeed that is my use case as well (see here). In particular I’m trying to polyfill this playground, the static components are easier.
Using @dpvc’s recommendation above you can inject the polyfilled chtml (or SVG) into the custom element (or simply replace the custom element). But I haven’t found a clean way to do it yet, keep running into issues where I duplicate the element on each interaction, or reaction is one interaction behind the user input. Another minor issue that I could live with, was that I had a hard time figuring out how to keep my preferred math font face.
@Jamesernator I gave up trying to fix these issues a while back as I was busy doing other things. Now I have more time to focus on my mathup project and I might give it another stab. I’ll let you know if I find a clean way to polyfill custom elements that output MathML.

Oh so I actually got a working way of this a while ago, this is all that it is to convert MathML into MathJax:
import { browserAdaptor } from "mathjax-full/js/adaptors/browserAdaptor.js";
import { RegisterHTMLHandler } from "mathjax-full/js/handlers/html.js";
import { MathML } from "mathjax-full/js/input/mathml.js";
import { mathjax } from "mathjax-full/js/mathjax.js";
import { CHTML } from "mathjax-full/js/output/chtml.js";
import onChildrenChange from "./onChildrenChange.js";

const adaptor = browserAdaptor();
// eslint-disable-next-line new-cap
RegisterHTMLHandler(adaptor);

const fontURL = new URL("./fonts", import.meta.url).href;

/* This sheet is due to a bug/design flaw in shadow dom that prevents
   any @font-face rules specified in shadow root sheets to have any effect */
const fontFaceRules = document.createElement("style");
document.head.append(fontFaceRules);

export default class MathJaxElement extends HTMLElement {
    readonly #shadowRoot = this.attachShadow({ mode: "closed" });

    constructor() {
        super();

        this.#shadowRoot.innerHTML = `

        `;

        onChildrenChange(this, () => void this.#render());

        this.#render();
    }

    get #content(): HTMLElement {
        return this.#shadowRoot.getElementById("content")!;
    }

    #render(): void {
        const mathML = this.innerHTML.trim();

        const mmlInput = new MathML();
        const chtmlOutput = new CHTML({
            fontURL,
        });

        const html = mathjax.document("", {
            InputJax: mmlInput,
            OutputJax: chtmlOutput,
        });

        const element = html.convert(mathML);

        const stylesheet = chtmlOutput.styleSheet(html) as HTMLStyleElement;

        this.#content.innerHTML = "";
        this.#content.append(stylesheet, element);

        for (const rule of stylesheet.sheet?.cssRules ?? []) {
            if (rule.type === CSSRule.FONT_FACE_RULE) {
                fontFaceRules.sheet?.insertRule(rule.cssText);
            }
        }
    }
}

<math-jax>
  <math>

  </math>
</math-jax>

The main trickyness was actually the fact that @font-face currently can't be defined inside the shadow root, so you need to rip out any @font-face rules and put them in a document-level stylesheet. There's an open bug in Chrome so that looks to be fixed soonish, not sure if other browsers suffer the same behaviour.


Allow Unicode-DFS-2016 license

Description
Allow Unicode-DFS-2016 license
unicode-ident which is used by serde added the Unicode-DFS-2016 license in version 1.0.2.

Review Checklist

[ ] Code contains useful comments
[ ] (Integration-)Test cases added (or not applicable)
[ ] Documentation added (or not applicable)
[ ] Changelog updated (or not applicable)
[ ] Cargo.toml only contains references to git tags (not specific commits or branches)

Once the review is done, comment bors r+ (or bors merge) to merge. Further information

bors merge


Patch release 0.4.0 for the latest fix

https://github.com/kubernetes-sigs/lws/releases/tag/v0.4.1


Error 403 on HTTP-01 challenge

Hello.
I'm trying to use kube-lego with nginx controller.
I used echoserver as explained in the example.
However the HTTP-01 challenge fails :
time="2016-09-21T18:33:14Z" level=warning msg="Error while obtaining certificate: Errors while obtaining cert: map[mydomain.com:acme: Error 403 - urn:acme:error:unauthorized - Invalid response from http://mydomain.com/.well-known/acme-challenge/OHTuEazqigcmn1x-kSXMmzWnHNRJTrLFNfB0kZL7Py8: \"CLIENT VALUES:\r\nclient_address=('10.x.x.x', 47151) (10.x.x.x)\r\ncommand=GET\r\npath=/.well-known/acme-challenge/OHTuEazqigcmn1x-k\"\nError Detail:\n\tValidation for mydomain.com:80\n\tResolved to:\n\t\t104.y.y.y\n\tUsed: 104.y.y.y\n\n]" context=acme

It looks normal as the echoserver catches the request and respond something not related to the token specified in the url.
How is that possible ? Is there something that I forgot or something missing in the doc ?

Hello, what version of the nginx-ingress-controller you have deployed? The latest one, 0.8.3? I see the same problem as you with 0.8.3. Try 0.8.1, that one works for me. Now I'm trying to find out where is the problem...

One more thing, do you use the --watch-namespace option with nginx-ingress-controller ?

Hi @stibi

what version of the nginx-ingress-controller you have deployed? The latest one, 0.8.3?

Yes. I used the 0.8.2 but couldn't make it work. Now 0.8.3 is deployed.

do you use the --watch-namespace option with nginx-ingress-controller

Yes.

0.8.2 is affected too, the problem is with the --watch-namespace…without the option, it works.
I guess the namespace restriction somehow break the events listening in the nginx controller.
If you check the nginx.conf, there is for example no ACME challenge location rules (/.well-known/acme-challenge/...). That's why the certificate request is not validated and issued.
I don't understand the whole thing yet, I have to check the nginx ingress controller code, but maybe someone here could explain it in more details.

Filtering on a namespace is not yet supported for kube-lego. If you only want to run kube-lego in a single namespace you could move kube-lego into that namespace.

Thanks @simonswine For each of my staging env (handled with namespaces) I need to deploy a kube-lego instance. Is that correct ?
Is filtering on a namespace planned for a future kube-lego release ?

I have this same 403 issue but with GKE. I also see it responding with a 200 to the request and returning Resolved to:\n\t\t104.y.y.y\n\tUsed: 104.y.y.y\n\n.

Though I think I'm missing something based on https://blog.jetstack.io/blog/kube-lego/ since that says kube-lego sets up a separate ingress that is to serve the response for /.well-known/acme-challenge/ and mine is going to the echoserver. It looks like @pdoreau 's is as well based on the output, \"CLIENT VALUES:\r\nclient_address=(

I am having a similar issue, although I use the GKE L7 ingress. Basically, the kube-lego pod is logging reachability failures, as reachability tests are routed to my web server which responds with a 404 error:
time="2016-11-02T16:37:56Z" level=debug msg="testing reachablity of http://www.realtime-music.com/.well-known/acme-challenge/_selftest" context=acme host=www.realtime-music.com
time="2016-11-02T16:37:57Z" level=warning msg="wrong status code '404'" context=acme host=www.realtime-music.com
time="2016-11-02T16:37:57Z" level=warning msg="Error while obtaining certificate: reachabily test failed for this cert"

@tsloughter @aknuds1 It works well on my side after adding kube-lego deployment under the namespace of the pods I want to secure.

@pdoreau You mean kube-lego should not be in its own namespace?

@aknuds1 I'm using nginx-controller with --watch-namespace option. To make everything work, I used the same namespace everywhere : my pods (and services...), the ingress ressource, the nginx-controller and the kube-lego deployment


Allow filepaths to be specified for assets

Currently I can only create sub-folders in the x-assets folder which is placed in the same place as the PSD file.
It would be very helpful if I could specific the exact file path i'd like each asset to end up in — and not necessarily within an x-assets folder.
I'm sure a straightforward syntax could be found to do this. It would be most helpful for updating and managing assets in an automated fashion. In my case where PSDs are stored locally, and assets end up in a remote repository pushed out to a CDN.
Jim

+1! Why are we still forced to output to this *-assets directory? I have a hacked version which omits that prefix so that I can for example output multiple .psd assets to the same folder, but obviously it gets reset every time there's an update to Photoshop and I have to go hacking it again.

I've mentioned this elsewhere but, this is forces a manual step in an otherwise automated process.


Adding configurability to the interceptor's HTTP round tripper

Removing hard-coded values in the http round tripper's configuration in the interceptor, and replacing them with values that can be set via environment variables in the interceptor

This PR has been submitted as a draft because it relies on #206. It should not be reviewed or merged until that one it. It will be converted to a non-draft PR after that happens.
Update: #206 is merged and this PR is taken out of draft mode. It is ready for review.

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)
[x] Any necessary documentation is added, such as:

README.md
The docs/ directory
The docs repo

[x] Expose configs on helm chart

Fixes #248
cc/ @yaron2

Checked this. All good to be merged.

Thanks @ajanth97


update documentation for Coq 8.16 and new Platform release

Since the new Coq 8.16 Platform is out, I update the documentation on installing VLSM. In particular, itauto is now part of the Platform, so those who use Platform installers and scripts can build VLSM right away.
8.15 also has known soundness bugs, which, although they are very unlikely to affect us, points to recommending 8.16 going forward.

I decided that we should fully switch to 8.16 and Stdpp 1.8.0, since there will otherwise have to be developer effort to support both 8.15 and 8.16. However, then we will need some assistance to get this merged.


Heading does not have anchor

Hi, I really like your program and it is by far my favorite among the alternatives I have found on the Internet. However, I found that anchor does not work like in other tools. I am new to this. If you are still maintaining this repo, could you tell me how to fix it?
For your reference, I have noticed that alternative tools render headings to anchored titles like:
api
. How do I apply it to the renderer? (Pardon me if this is a dumb question, I just start to learn React recently) Thank you very much!

This uses the commonmark-react-renderer library for rendering markdown, so any issues like this would be from that library.


Port to 1.37

Could you please port the mod to 1.37 ?
Thanks

I can't do testing myself since I don't have a Quest on hand, but here's the untested pre-release if you'd like to try for yourself: https://github.com/rcelyte/MappingExtensions/releases/tag/0.24.0-pre0

Thank you very much, I'll tell you if it works or not

I'll tell you when I can becuase right now MBF is freaking out with it, it throws me this error : "Failed to import file: Error: Failed to parse manifest Caused by: QMOD specified schema version 1.2.0 which was newer than the maximum supported version 1.1.0. Is MBF out of date, or did the mod developer make a mistake?" So I asked them if MBF was outdated or not

Just imported the unreleased port to my quest 2 through Mods Before Friday, ill update in a moment

amazing!! it works perfectly! ill provide a rather laggy vid in a bit. it works for me! :D

So... video?

It works for me. Thx ! (Quest3+Questpatcher(scotland2)+Manually added via MBF)

released.


Fix SMTP/FTP subsystem for case-sensitive file names

Currently the whole command is made UPPERCASE, because some servers may refuse them otherwise, but by doing this you're breaking file names for case-sensitive filesystems (e.g. ext-family, the majority of the *nix servers).
Example: cmd argument equals "list /world/"
Result: "LIST /WORLD/" will be sent and the server will respond that "/WORLD/" directory doesn't exist, because lowercase ~= uppercase
This patch will fix it to return "LIST /world/" and the server will find the path on it's side.
Introduced in: https://github.com/diegonehab/luasocket/commit/bce60be30fe8e9c1b0eb33128c23c93d7bca5303#diff-52829881345969821da3e6b836f35bc5
PS: I hope the one-liner is okay.
PPS: I can't believe I've found such an old bug (yet at the expense of roughly 2 hours)

Oh snap, the bug I had was introduced by the applying program:
https://github.com/moteus/lua-ftp/blob/master/lua/ftp.lua#L74
Everything is fine then.


Update Composer dependencies (2024-01-22-00-16)

Visual regression test passed!
View the visual regression test report


Change “copy all” to “copy last”

When I want to copy notations from the output list of the tool it should say Copy Last instead of Copy all with the additions of the batch section on this tool.

i like this idea, however i would change the verbage to "Copy Outputs" to be explicit about what the user is putting onto the clipboard when they copy, to me "Copy Last" is not the clearest way to convey to the user what they are copying. @topowright , thoughts?

This may be a non issue if @kgonzago/ @adgiles are able to move the copy icon to the output header row. It should make more sense what you're copying at that point.

FYI: Based on #343, the buttons have been moved to the output header row.

closing this. verified that @kgonzago moved the copy button and add format button to the output header, no need to change the verbage of the button, since it is now in the output header, i feel it is obvious what it is copying


Causes zotero to die.

So, I just started having the problem described at https://forums.zotero.org/discussion/49570/an-error-has-occured-please-restart-zotero-report-1776248202/ - basically zotero was unusable. When I tried removing better-bibtex, the problem resolved itself. Perhaps a recent zotero change has broken something?
Copied from there:
I just tried starting Zotero stand-alone after transferring my home directory from another laptop, and I'm now getting a the message in the title in the table view of every collection. I can see all of the collections in the side-bar.
Zotero starts fine inside inside Firefox, if Zotero stand-alone is closed. I've tried closing everything and re-opening.
I'm using version <IP_ADDRESS> (the latest standalone version). I'm using <IP_ADDRESS> in firefox.
I submitted error report<PHONE_NUMBER>. The contents were:
[JavaScript Error: "bad script XDR magic number"]
[JavaScript Error: "bad script XDR magic number"]
[JavaScript Error: "uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [mozIStorageConnection.executeSimpleSQL]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://zotero/content/xpcom/db.js :: Zotero.DBConnection.prototype.query :: line 149"  data: no] [QUERY: update betterbibtex.autoexport set collection = (select 'library:' || libraryID from groups where 'group:' || groupID = collection) where collection like 'group:%'] [ERROR: no such column: collection]"]
[JavaScript Error: "State check failed due to transaction in progress"]
[JavaScript Error: "State check failed due to transaction in progress"]
[JavaScript Error: "Cannot start a DB transaction from a different wait level"]
[JavaScript Error: "Error: Transaction in progress in Zotero.Sync.Server._checkSyncUser" {file: "chrome://zotero/content/xpcom/sync.js" line: 652}]

version => <IP_ADDRESS>, platform => Linux x86_64, oscpu => Linux x86_64, locale => en-US, appName => Zotero, appVersion => <IP_ADDRESS>, extensions => LyZ (2.1.7, extension), Paper Machines (0.4.6, extension), Abbreviations for Zotero (1.0.140, extension), Zotero automatic export (<IP_ADDRESS>, extension), ZotFile (4.1.5, extension), Zotero LibreOffice Integration (3.5.9.SA.<IP_ADDRESS>, extension), Zotero Better Bib(La)Tex (0.9.36, extension), Shockwave Flash (<IP_ADDRESS>0, plugin), VLC Web Plugin (, plugin), Zotero Scholar Citations (1.8.4, extension, disabled)

O_o that was quick, thanks! How can I test it?

Simply let it upgrade.


usbd-hid 0.7 fails to build after 0.8 releases

The 0.8 releases appear to break builds that depend on usbd-hid 0.7 or 0.6. Here's a reproduction:
cargo new --lib foo && cd foo
cargo add<EMAIL_ADDRESS>cargo build

Here's the build failure:
   Compiling usbd-hid-macros v0.6.0
error[E0277]: the trait bound `usbd_hid_descriptors::MainItemKind: From<std::string::String>` is not satisfied
   --> /Users/mciantyre/.cargo/registry/src/index.crates.io-6f17d22bba15001f/usbd-hid-macros-0.6.0/src/spec.rs:512:43
    |
512 |             self.set_item(name, item_kind.into(), settings, bits, quirks);
    |                                           ^^^^ the trait `From<std::string::String>` is not implemented for `usbd_hid_descriptors::MainItemKind`, which is required by `std::string::String: Into<_>`
    |
    = help: the trait `From<&str>` is implemented for `usbd_hid_descriptors::MainItemKind`
    = help: for that trait implementation, expected `&str`, found `std::string::String`
    = note: required for `std::string::String` to implement `Into<usbd_hid_descriptors::MainItemKind>`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `usbd-hid-macros` (lib) due to 1 previous error

cargo tree output

foo v0.1.0 (/tmp/foo)
└── usbd-hid v0.7.0
    ├── serde v1.0.204
    ├── ssmarshal v1.0.0
    │   ├── encode_unicode v0.3.6
    │   └── serde v1.0.204
    ├── usb-device v0.3.2
    │   ├── heapless v0.8.0
    │   │   ├── hash32 v0.3.1
    │   │   │   └── byteorder v1.4.3
    │   │   └── stable_deref_trait v1.2.0
    │   └── portable-atomic v1.6.0
    └── usbd-hid-macros v0.6.0 (proc-macro)
        ├── byteorder v1.4.3
        ├── proc-macro2 v1.0.86
        │   └── unicode-ident v1.0.12
        ├── quote v1.0.36
        │   └── proc-macro2 v1.0.86 (*)
        ├── serde v1.0.204
        ├── syn v1.0.109
        │   ├── proc-macro2 v1.0.86 (*)
        │   ├── quote v1.0.36 (*)
        │   └── unicode-ident v1.0.12
        └── usbd-hid-descriptors v0.8.0
            └── bitfield v0.14.0

919616b9b65e89b4c9c8a4adcfe1af7870c891c7 shows that usbd-hid-macros 0.6 is allowed to depend on any version of usbd-hid-descriptors starting from 0.1.2. In this reproduction, usbd-hid-macros selects usbd-hid-descriptors 0.8.0 as its dependency. These seem to be incompatible.

I'm sorry about that, I had a >=x dependency on one of the internal crate which blew up. This is fixed in the 0.8 series.

@twitchyliquid64 Sorry for the ping, but the issue seems still here. I'm using usbd-hid 0.7, and here is the build log: https://github.com/HaoboGu/rmk/actions/runs/9969247462/job/27545878943

Can you try 0.8?

Can you try 0.8? Does that work?

No. That's because I'm using the crates.io version of embassy-usb, which uses<EMAIL_ADDRESS>Here is the log:
error: failed to select a version for `byteorder`.
    ... required by package `usbd-hid-macros v0.6.0`
    ... which satisfies dependency `usbd-hid-macros = "^0.6.0"` of package `usbd-hid v0.7.0`
    ... which satisfies dependency `usbd-hid = "^0.7.0"` of package `embassy-usb v0.2.0`
    ... which satisfies dependency `embassy-usb = "^0.2"` of package `rmk v0.2.2 (/Users/haobogu/Projects/keyboard/rmk/rmk)`
versions that meet the requirements `~1.4` are: 1.4.3, 1.4.2, 1.4.1, 1.4.0

all possible versions conflict with previously selected packages.

  previously selected package `byteorder v1.5.0`
    ... which satisfies dependency `byteorder = "^1.5"` of package `usbd-hid-macros v0.8.0`
    ... which satisfies dependency `usbd-hid-macros = "^0.8.0"` of package `usbd-hid v0.8.0`
    ... which satisfies dependency `usbd-hid = "^0.8"` of package `rmk v0.2.2 (/Users/haobogu/Projects/keyboard/rmk/rmk)`

failed to select a version for `byteorder` which could resolve this conflict

I wrote the first version of this in 2020, in the first few months of writing Rust, and foolishly put the >= specifier on the inter-crate version specifiers. This exploded a few days ago when the macros crate was no longer compatible with all older versions.
I don't really know a way to fix this without everyone upgrading to usbd-hid 0.8 :(
If anyone has any ideas for how to fix this for the 0.6 or 0.7 series please let me know. Sorry again.

I break my users all the time. You're in good company.
My approach in https://github.com/imxrt-rs/imxrt-hal/pull/169 was to simulate the release of a 0.6.1 usbd-hid-macros package. Here is the change I made. That fixes my builds, and my quick firmware test still worked. I'm not sure if it fixes everything for everyone else, but folks can try it out by adding
[patch.crates-io.usbd-hid-macros]
git = "https://github.com/imxrt-rs/usbd-hid.git"
branch = "patch-imxrt-hal-0.5"

into their project's Cargo.toml.
Is there concern with releasing a 0.6.1 version of usbd-hid-macros, a release that removes the >= specifier? You'll need to select the correct branch point for cutting the release. (Don't do what I did: hastily select a commit from 2 days ago when 0.6.0 was release nearly 2 years ago.)

Hmmm, yeah I can do that. I think crates lets you release patches of old minor versions?
Afaict everyone thats broken was using 0.6 ?

Can you try 0.6.2? Just pushed it.

Could you push a 0.7 update? thanks

Just did, can you test @HaoboGu ?

0.7.1

Just did, can you test @HaoboGu ?

I just tested, worked well! Thanks a lot!

Yay!!!


upcoming: [M3-7602] - Update AGLB Configuration Add Certificate Drawer

Description 📝

Updates the AGLB "Add Certificate Drawer" based on alpha tester feedback and collaboration with UX

Changes  🔄

Main Changes

Changes wording of Apply to Add when referring to adding a certificate to a HTTPS configuration ✏
Removes the ability to add many certificates at once to a Configuration at once. The drawer now just allows you to add one certificate at a time ❌
Allows the user to create a certificate from the configurations page 🆕

Extra Bonus Changes

Adds missing loading state to the create certificate drawer 🔄
Adds cancel button to create certificate drawer for completeness and consistency

Preview 📷

Before
After

How to test 🧪
Prerequisites

Use the dev environment
Login to the dev-test-aglb account

Verification steps

Go to http://localhost:3000/loadbalancers/13/configurations
On any HTTPS configuration, test the new drawer by clicking Add Certificate

Verify you can add an existing certificate
Verify you can remove a cert from a configuration
Verify you can create a new certificate from within the "Add Certificate" drawer
If you need a TLS Certificate to test with, ask me in Slack!

As an Author I have considered 🤔

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[ ] ➕ Adding a changeset
[ ] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[ ] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

I did work with Daniel on this UX. We decided that opening the Create Drawer on top of the Add Drawer was good because it allows us to re-use the Create Certificate flow. It enables the user to create a new certificate without leaving this page (and without chaining requests)
I didn't realize that the backdrop got darker though, that definitely seems bad. We might want to revisit that @cpathipa


[badge] Add the info about stroke after the latest conversations

See the complete conversation here:
https://adevinta.slack.com/archives/C03FVU53XU5/p1691584968126769

To complete this ticket: I add the topic of the size of the "no count" to change it to 8px rather than 12 px

The "no count" version has been changed to 8px 👍

Ready ✅


Batch Prediction Error

i try to run batch prediction with command:
"python deepdenoiser/predict.py --format=mseed --model_dir=model/190614-104802 --data_dir=test_data/ --data_list=test_data/testing.csv --sampling_rate=100 --plot_figure --save_signal --save_noise"
but getting an error:
Traceback (most recent call last):
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 136, in <module>
    main(args)
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 129, in main
    pred_fn(args, data_reader, log_dir=args.output_dir)
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 81, in pred_fn
    X_batch, fname_batch, t0_batch = sess.run(data_batch)
  File "D:\miniconda3\lib\site-packages\tensorflow\python\client\session.py", line 968, in run
    result = self._run(None, fetches, feed_dict, options_ptr,
  File "D:\miniconda3\lib\site-packages\tensorflow\python\client\session.py", line 1191, in _run
    results = self._do_run(handle, final_targets, final_fetches,
  File "D:\miniconda3\lib\site-packages\tensorflow\python\client\session.py", line 1371, in _do_run
    return self._do_call(_run_fn, feeds, fetches, targets, options,
  File "D:\miniconda3\lib\site-packages\tensorflow\python\client\session.py", line 1397, in _do_call
    raise type(e)(node_def, op, message)  # pylint: disable=no-value-for-parameter
tensorflow.python.framework.errors_impl.InvalidArgumentError: Graph execution error:

Detected at node 'Input_Batch/IteratorGetNext' defined at (most recent call last):
    File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 136, in <module>
      main(args)
    File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 129, in main
      pred_fn(args, data_reader, log_dir=args.output_dir)
    File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 56, in pred_fn
      data_batch = data_reader.dataset(args.batch_size)
    File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\data_reader.py", line 801, in dataset
      dataset = tf.compat.v1.data.make_one_shot_iterator(
Node: 'Input_Batch/IteratorGetNext'
Incompatible shapes at component 0: expected [?,3,1,31,1202,2] but got [1,3,1,31,1201,2].
         [[{{node Input_Batch/IteratorGetNext}}]]

Original stack trace for 'Input_Batch/IteratorGetNext':
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 136, in <module>
    main(args)
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 129, in main
    pred_fn(args, data_reader, log_dir=args.output_dir)
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\predict.py", line 56, in pred_fn
    data_batch = data_reader.dataset(args.batch_size)
  File "D:\QuakeFlow\DeepDenoiser\deepdenoiser\data_reader.py", line 801, in dataset
    dataset = tf.compat.v1.data.make_one_shot_iterator(
  File "D:\miniconda3\lib\site-packages\tensorflow\python\data\ops\iterator_ops.py", line 440, in get_next
    flat_ret = gen_dataset_ops.iterator_get_next(
  File "D:\miniconda3\lib\site-packages\tensorflow\python\ops\gen_dataset_ops.py", line 3036, in iterator_get_next
    _, _, _op, _outputs = _op_def_library._apply_op_helper(
  File "D:\miniconda3\lib\site-packages\tensorflow\python\framework\op_def_library.py", line 797, in _apply_op_helper
    op = g._create_op_internal(op_type_name, inputs, dtypes=None,
  File "D:\miniconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 3800, in _create_op_internal
    ret = Operation(

this is my input data:

The reason might be found in these two lines of code: if np.mod(data.shape[-1], 3000) == 1:  # 3001=>3000 and data = data[..., :-1]. Commenting them out should allow the program to run successfully.Please forgive my poor English QAQ

The reason might be found in these two lines of code: if np.mod(data.shape[-1], 3000) == 1: # 3001=>3000 and data = data[..., :-1] （←in data_reader.py）. Commenting them out should allow the program to run successfully.Please forgive my poor English QAQ

Hello，I tried the methods you suggested, but the issue still persists.Are there any other solutions?


python3Packages.MechanicalSoup: fix alias

Motivation for this change
Alias was backwards and would shadow the actual module.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build python3Packages.mechanicalsoup
Fixes a regression caused by #124978, cc @fabaff

Result of nixpkgs-review pr 125426 at ca97ae96 run on aarch64-linux 1

2 packages built successfully:

python38Packages.mechanicalsoup
python39Packages.mechanicalsoup


Change "date", "person", and "address" parameters

Is your proposal related to a problem?
From @cascadianblue
The annotator_type parameter takes inputs (date, person, address) that are out of line with anything else, as far as a I can tell.
Describe the solution you'd like
Could they be changed to text_date, text_person_name, and text_physical_address to be more in line with the rest of NLP Sandbox?
This will impact the controllers, evaluation code, and client.

This would have to be updated:
nlp-cli tool annotate-note

It seems that we have two types of tools:

This client defines annotator_type that takes these values:

date
person
address

The NLP Sandbox Schemas defines four Tool APIs that are expected to return Tool.toolType with these values:

nlpsandbox:date-annotator
nlpsandbox:person-name-annotator
nlpsandbox:physical-address-annotator
nlpsandbox:phi-deidentifier

I would recommend for this client:

Rename annotator_type to tool_type (an annotator is a sub-type of tools)
Use in the client the type values: nlpsandbox:date-annotator, etc.

Note that I didn't define Tool.toolType as an enum in the schemas. The motivation is that external organizations may come up in the future with their own type of tools that are still compatible with the NLP Sandbox schemas. Obviously this org would also extend the NLP Sandbox Client to add support for their new type of tool.
@thomasyu888 @cascadianblue

@cascadianblue If applicable, your implementation of the PHI Deidentifier should also rely on nlpsandbox:date-annotator, etc.

There happens to be a one-to-one correlation of tool_type to annotation type. E.g.
text_physical_address -> nlpsandbox:physical-address-annotator
text_date -> nlpsandbox:date-annotator
is this necessarily going to always be true for all tool types?

@cascadianblue If applicable, your implementation of the PHI Deidentifier should also rely on nlpsandbox:date-annotator, etc.

@tschaffter the phi-deidentifier uses the annotation type convention (e.g. text_date) in its response when it passes the annotations on to the client: https://github.com/nlpsandbox/nlpsandbox-schemas/blob/5e0e07af21d1faa816425723b7ed17791426cf27/openapi/phi-deidentifier/components/schemas/AnnotationSet.yaml . Should this be changed to the tool type convention (e.g. nlpsandbox:date-annotator)? I'm not sure how (well) this would work

There happens to be a one-to-one correlation of tool_type to annotation type. E.g.
is this necessarily going to always be true for all tool types?

@cascadianblue It's difficult to confirm. Why?

Should this be changed to the tool type convention (e.g. nlpsandbox:date-annotator)? I'm not sure how (well) this would work

This wouldn't work. It's better to have the tool type and name of the output returned loosely coupled instead of rigidly.
@thomasyu888 Let's go with using tool type (e.g. nlpsandbox:abc) to identify a type of tool.

@tschaffter, just to confirm if you are ok with cli like this

Evaluate prediction
nlp-cli evaluate-prediction
Usage: nlp-cli evaluate-prediction [OPTIONS]

  Evaluate the performance of a prediction file. Example prediction and
  goldstandard files are found in test/data/new_prediction.json and
  test/data/new_goldstandard.json respectively.

Options:
  --pred_filepath PATH            Prediction filepath  [required]
  --gold_filepath PATH            Gold standard filepath  [required]
  --output PATH                   Specify output json path
  --tool_type [nlpsandbox:date-annotator|nlpsandbox:person-name-annotator|nlpsandbox:physical-address-annotator]
                                  Type of Tool to evaluate.  [required]
  --help                          Show this message and exit.

Annotate Note
nlp-cli tool annotate-note
Usage: nlp-cli tool annotate-note [OPTIONS]

  Annotate a note with specified annotator

Options:
  --annotator_host TEXT           Annotator host.  [required]
  --note_json PATH                Clinical notes json  [required]
  --output PATH                   Specify output json path
  --tool_type [nlpsandbox:date-annotator|nlpsandbox:person-name-annotator|nlpsandbox:physical-address-annotator]
                                  The type of tool.  [required]
  --help                          Show this message and exit.

@thomasyu888 What is saved to the output folder? Is the response displayed in the terminal after running the command?
This CLI looks great!

@tschaffter Its not a folder, it's the path to the json.  So if you wanted to get the results of an annotation in json it would be:
nlp-cli tool annotate-note --output /path/to/my/json.json


Setting onMessage on a WebView overrides existing values of window.postMessage

Using v5.0.6 with RN 0.57.29
I get the above titled error whenever the webview opens. Changing the uri to https://www.google.com doesn't post a problem. Is it because the current uri is being redirected?
const injectedJavascript = `window.ReactNativeWebView.postMessage('hi');`;
onMessage(event) {
    console.log(event.nativeEvent.data);
  }
<WebView useWebKit={false} source={{ uri: 'https://login.microsoftonline.com/' }}
 injectedJavaScript={injectedJavascript} onMessage={this.onMessage} />

You sure you rebuilt native after updating?

It's window.ReactNativeWebview.postMessage not window.ReactNativeWebView.postMessage

@tapir I was only ReactNativeWebview by mistake in 5.0.0 and was fixed instantly to ReactNativeWebview as specified in the patch notes.
Please also avoid this kind of messages. I maintain this in my free time without any remuneration, calling my work ridiculous is just... w/e

@tapir I was only ReactNativeWebview by mistake in 5.0.0 and was fixed instantly to ReactNativeWebview as specified in the patch notes.
Please also avoid this kind of messages.  I'm sorry it sounded that way. I do appreciate your work. It's just that I value compatibility above everything else and was surprised to notice it by chance.

Saved my day. Could not notice that in version 5.0.0 and documentation, this is spelt differently.
@Titozzz Thanks a lot for maintaining it. I see that you have been very active in helping all of us here.


Fix deprecation warning

Fixes
[DEPRECATION WARNING]: State 'installed' is deprecated. Using state 'present' instead.. This
feature will be removed in version 2.9. Deprecation warnings can be disabled by setting
deprecation_warnings=False in ansible.cfg.

Please release this to Galaxy


fix(doc): upgrade hertz version and fix readme

What type of PR is this?

optimize: upgrade hertz version and fix README doc
What this PR does / why we need it (English/Chinese):

upgrade hertz version
fix README

Which issue(s) this PR fixes:

LGTM


Use core from existing mask when setting processor affinity

As discussed in #817, this change sets the processor affinity to the lowest core id of the existing affinity mask. This will solve cases where the core id 0, which was previously used, is not available (e.g. in virtualized environments).
(fixes #817)

Just tested and recreated issue and proved this fixes it :+1:


IbeaconScanner Speed customizing

how to change scanner speed? i use raspberry pi 4 model B and HM17
hm17 send signal set up 300ms but scanner couldnt how can i fix it?

You can pass custom scan parameters:
BeaconScanner(..., scan_parameters={interval_ms=10, window_ms=10})


Create find duplicate characters in a string.java

Program to find duplicate characters in a string.

how is this related to FizzBuzz?
Please check out the ReadMe before contributing.


Menu ordering on OS X doesn't match system patterns

On OS X, most apps have a similar pattern of menus:

The general pattern is: File, Edit, (Format), View, Application menus, Window, Help. However Atom uses File, Edit, Selection, Find, View, Packages, Window, Help.

I think View should probably be next to File and Edit.
Apologies if this is a duplicate, I tried searching but I couldn't find anything.

:+1:  on Atom   File   Edit   View   Selection   Find   Packages   Window   Help

This is also backed up by the OS X Human Interface Guidelines.

Perfect, I was looking for those guidelines but couldn't find them. Thanks!


Various fixes for mypy, to reduce error count

Some of these "break" the typing interface, so this PR belongs in v1.1

Codecov Report

Merging #1057 (771c361) into master (d7dff3f) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1057   +/-   ##
=======================================
  Coverage   88.09%   88.10%
=======================================
  Files          51       51
  Lines        7210     7212    +2
=======================================
+ Hits         6352     6354    +2
  Misses        858      858

Flag
Coverage Δ

unittests
88.10% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

lark/lark.py
85.11% <100.00%> (ø)

lark/lexer.py
94.67% <100.00%> (ø)

lark/load_grammar.py
92.66% <100.00%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

It was surprisingly difficult to install Python 3.6


Enable Search menu actions for any panel/plugin that supports/uses the find/replace widget

...
Perhaps related is that the Search menu items are greyed out, even after the correct behavior is restored. "Replace text" and "Go to line..." should certainly be context dependent (greyed out for IPython Console), but shouldn't "Find text", "Find next", and "Find previous" be selectable for any widget that supports the Search widget?

Originally posted by @mrclary in https://github.com/spyder-ide/spyder/issues/22453#issuecomment-2349676529

Some other related comments: https://github.com/spyder-ide/spyder/issues/22453#issuecomment-2518605552


[Bugs] SMF startup failed with some staticPools value

Describe the bug
In SMF, some staticPools and pools configuration cause start error.
To Reproduce
Try to start SMF with configuration file followed:
info:
  version: 1.0.7
  description: SMF initial local configuration

configuration:
  smfName: SMF # the name of this SMF
  sbi: # Service-based interface information
    scheme: http # the protocol for sbi (http or https)
    registerIPv4: <IP_ADDRESS> # IP used to register to NRF
    bindingIPv4: <IP_ADDRESS> # IP used to bind the service
    port: 8000 # Port used to bind the service
    tls: # the local path of TLS key
      key: cert/smf.key # SMF TLS Certificate
      pem: cert/smf.pem # SMF TLS Private key
  serviceNameList: # the SBI services provided by this SMF, refer to TS 29.502
    - nsmf-pdusession # Nsmf_PDUSession service
    - nsmf-event-exposure # Nsmf_EventExposure service
    - nsmf-oam # OAM service
  snssaiInfos: # the S-NSSAI (Single Network Slice Selection Assistance Information) list supported by this AMF
    - sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
        sst: 1 # Slice/Service Type (uinteger, range: 0~255)
        sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
      dnnInfos: # DNN information list
        - dnn: internet # Data Network Name
          dns: # the IP address of DNS
            ipv4: <IP_ADDRESS>
            ipv6: 2001:4860:4860::8888
    - sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
        sst: 1 # Slice/Service Type (uinteger, range: 0~255)
        sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
      dnnInfos: # DNN information list
        - dnn: internet # Data Network Name
          dns: # the IP address of DNS
            ipv4: <IP_ADDRESS>
            ipv6: 2001:4860:4860::8888
  plmnList: # the list of PLMN IDs that this SMF belongs to (optional, remove this key when unnecessary)
    - mcc: 208 # Mobile Country Code (3 digits string, digit: 0~9)
      mnc: 93 # Mobile Network Code (2 or 3 digits string, digit: 0~9)
  locality: area1 # Name of the location where a set of AMF, SMF, PCF and UPFs are located
  pfcp: # the IP address of N4 interface on this SMF (PFCP)
    # addr config is deprecated in smf config v1.0.3, please use the following config
    nodeID: <IP_ADDRESS> # the Node ID of this SMF
    listenAddr: <IP_ADDRESS> # the IP/FQDN of N4 interface on this SMF (PFCP)
    externalAddr: <IP_ADDRESS> # the IP/FQDN of N4 interface on this SMF (PFCP)
  userplaneInformation: # list of userplane information
    upNodes: # information of userplane node (AN or UPF)
      gNB1: # the name of the node
        type: AN # the type of the node (AN or UPF)
      UPF: # the name of the node
        type: UPF # the type of the node (AN or UPF)
        nodeID: <IP_ADDRESS> # the Node ID of this UPF
        addr: <IP_ADDRESS> # the IP/FQDN of N4 interface on this UPF (PFCP)
        sNssaiUpfInfos: # S-NSSAI information list for this UPF
          - sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
              sst: 1 # Slice/Service Type (uinteger, range: 0~255)
              sd: 010203 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
            dnnUpfInfoList: # DNN information list for this S-NSSAI
              - dnn: internet
                pools:
                  - cidr: <IP_ADDRESS>/16
                staticPools:
                  - cidr: <IP_ADDRESS>/32
          - sNssai: # S-NSSAI (Single Network Slice Selection Assistance Information)
              sst: 1 # Slice/Service Type (uinteger, range: 0~255)
              sd: 112233 # Slice Differentiator (3 bytes hex string, range: 000000~FFFFFF)
            dnnUpfInfoList: # DNN information list for this S-NSSAI
              - dnn: internet
                pools:
                  - cidr: <IP_ADDRESS>/16
                staticPools:
                  - cidr: <IP_ADDRESS>/24
        interfaces: # Interface list for this UPF
          - interfaceType: N3 # the type of the interface (N3 or N9)
            endpoints: # the IP address of this N3/N9 interface on this UPF
              - <IP_ADDRESS>
            networkInstances:  # Data Network Name (DNN)
              - internet
    links: # the topology graph of userplane, A and B represent the two nodes of each link
      - A: gNB1
        B: UPF
  # retransmission timer for pdu session modification command
  t3591:
    enable: true     # true or false
    expireTime: 16s   # default is 6 seconds
    maxRetryTimes: 3 # the max number of retransmission
  # retransmission timer for pdu session release command
  t3592:
    enable: true     # true or false
    expireTime: 16s   # default is 6 seconds
    maxRetryTimes: 3 # the max number of retransmission
  nrfUri: http://<IP_ADDRESS>:8000 # a valid URI of NRF
  #urrPeriod: 10 # default usage report period in seconds
  #urrThreshold: 1000 # default usage report threshold in bytes

logger: # log output setting
  enable: true # true or false
  level: info # how detailed to output, value: trace, debug, info, warn, error, fatal, panic
  reportCaller: false # enable the caller report or not, value: true or false

Expected behavior
Start SMF correctly
Environment (please complete the following information):

free5GC Version: e48e933dde6bad3a83f6cd327003eeba6992abfa
OS: Ubuntu 20.04.6 LTS
Kernel version: 5.15.0-88-generic
go version: 1.21.4

Log File
$ ./bin/smf
2023-11-10T11:39:54.885897982+09:00 [INFO][SMF][Main] SMF version:
        free5GC version: v3.3.0-22-ge48e933
        build time:      2023-11-10T02:30:52Z
        commit hash:     1be93089
        commit time:     2023-10-12T12:41:27Z
        go version:      go1.21.4 linux/amd64
2023-11-10T11:39:54.886178718+09:00 [INFO][SMF][CFG] Read config from [./config/smfcfg.yaml]
2023-11-10T11:39:54.889381300+09:00 [INFO][SMF][CFG] Read config from [./config/uerouting.yaml]
2023-11-10T11:39:54.890219675+09:00 [INFO][SMF][Main] Log enable is set to [true]
2023-11-10T11:39:54.890262707+09:00 [INFO][SMF][Main] Log level is set to [info]
2023-11-10T11:39:54.890288908+09:00 [INFO][SMF][Main] Report Caller is set to [false]
2023-11-10T11:39:54.890356317+09:00 [INFO][SMF][CTX] smfconfig Info: Version[1.0.7] Description[SMF initial local configuration]
2023-11-10T11:39:54.890427614+09:00 [INFO][SMF][CTX] Endpoints: [<IP_ADDRESS>]
2023-11-10T11:39:54.890477954+09:00 [FATA][SMF][Init] exclude static Pool[<IP_ADDRESS>/32] failed: exclude uePool fail: reserve range should in [171704321, 171769854]
$

@ShouheiNishi
You can try SMF's PR 89

@ShouheiNishi
Thanks for your PR. I will review it.


Enable column-search for a few columns in the puzzles table.

Tested locally -- see screenshots below.
Original page:

Basic column filter works:

It filters on the right column:

Combinations of filters also work:

Niiice!! Looks great.
One thing (only somewhat related): do you have a preference of whether the first column is titled "Puzzle" or "Name". I believe @rawxfish had called it "Name" originally. I was fine with that and the only reason I changed it to "Puzzle" was because I was testing Heroku deployment and wanted to make some small change that was very visible in the UI. I think I like the heading "Name" better (I think puzzle is implicit about everything on Small Board) and wanted to ask what other people thought.

I think either "Name" or "Puzzle" is fine -- we can change it back.
On Tue, Dec 3, 2019 at 4:03 AM Anthony Hsu<EMAIL_ADDRESS>wrote:

Merged #38 https://github.com/cardinalitypuzzles/smallboard/pull/38
into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cardinalitypuzzles/smallboard/pull/38?email_source=notifications&email_token=AALN2UL4T65T6W2OIJ3NWU3QWZDKXA5CNFSM4JUTOVG2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOVHNWWXA#event-2849729372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALN2UI4OSB6ZY6VIQSZZFLQWZDKXANCNFSM4JUTOVGQ
.


[communities] make the main communities page

Background:
there isn't any communities page
ToDo:

Add the communities page
Add it to the navbar

Example:

Notes:

Map non interactive in the first iteration, just viewable and only for the desktop
Do NOT implement the communities search yet, implement a button which triggers this modal instead, in case of question please ask me

@jesseallhands text for the communities page?


Conda-build 3, update, fix up

This recipe has gotten a bit stale. This PR rolls up the conda-build 3 migration and the bump to the latest version, plus build fixes and improvements.
This may not build on macOS yet, but I need to push it here to be able to test it on my machine.

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.

@conda-forge/staged-recipes I'm not sure if the existing maintainer of this package is going to be very responsive; would appreciate a merge if it looks good and we don't hear anything very soon. This is blocking an update to gtk2 (PR #1).

Hi @notestaff - Are you still interested in maintaining this feedstock?  I'd be great if you are! If we don't hear back from you (one way or the other) in 5 days, I'll go ahead and merge this.

May want to look at PR ( https://github.com/conda-forge/gdk-pixbuf-feedstock/pull/5 ) to see if there is anything else needed for migration.

Thanks all :)


A suggestion for git

Hi authors,
Thanks for your great work and make it available for the community.
I suggest that you can use .gitignore to ignore the update of some cache files like pycache. So that it will be more clear for us to identify your update.
Best

Thanks for your suggestion, and I will fix this problem soon.

Hello, the author. Maybe this file here can help a lot.

Hi there, the file does help a lot, thanks.


vs403191  - Unable to cast COM object of type

It would probably be useful to link/incorporate this article, to help people experiencing this issue:
https://learn.microsoft.com/en-gb/archive/blogs/dau-blog/how-to-solve-unable-to-cast-com-object-of-type-microsoft-office-interop-excel-applicationclass-to-interface-type-microsoft-office-interop-excel-_application

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

ID: bf4c6dd3-d2d2-0d41-9958-d3f7d85b5c05
Version Independent ID: e5e4a28f-30b8-0dab-b94b-d94fe6d341fe
Content: Resolve common Azure DevOps Office integration issues - Azure Boards
Content Source: docs/boards/backlogs/office/tfs-office-integration-issues.md
Service: azure-devops-boards
GitHub Login: @chcomley
Microsoft Alias: chcomley

Thank you for the great idea, @fowl2. I've updated the article accordingly.


API version to support Metric Dataplane Subscriptions in Azure Monitor Private Link Scopes

ARM (Control Plane) API Specification Update Pull Request
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I have reviewed the general guidance on the spec PR review process: https://aka.ms/specprreview.
[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data-plane related specifications.
[x] I commit to follow the Breaking Change Policy.
[X] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can request review from an ARM API Review board.

ARM API changes review

If you want for the ARM team to review this PR, you must add the ARMReview label.
The automation may automatically add the ARMReview label, if appropriate.
If this happens, proceed according to guidance given in GitHub comments also added by the automation.

Breaking change review
If you have any breaking changes as defined in the Breaking Change Policy,
follow the process outlined in the High-level Breaking Change Process doc.
Getting help

For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For additional help, see https://aka.ms/azsdk/support/spectools.

Hi @qinjoshua! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

Hey @qunjoshua.. can you please add the version of the file that contains the previous version of the privatelinkScopes_API file as a base commit as is called out here before start the ARM review ?

I see that your team does not renew all files for a new api version. This is not recommended since this will lead to SDKs only having some apis in the release. Is there a reason why you do not renew all the files ?

Hi @raosuhas , thank you for taking a look at my PR.
I've added a base commit that just replicates the previous version of the API that I'm updating. Let me know if that looks good
I'm new to the team and this is my first Swagger docs update, but my understanding is that my Team only renews files for the APIs that we're updating in the newest version because those are the only files being change. In this case, I only plan to modify the private links API. I am not sure why this is not recommended, as other APIs will continue to work using whatever their latest version is.
Let me know if there's anything else I need to do.

This one looks like you're declaring the Location header incorrectly per openapi

❌ unacceptable kind of an object to dump [object Error] | "role":"Model Validation","url":"https://github.com/Azure/azure-rest-api-specs/blob/e7f921b92fbc7c9aff11ee68d60a25f21809809c/specification/monitor/resource-manager/Microsoft.Insights/preview/2023-06-01-preview/privateLinkScopes_API.json"

@rkmanda All required validations should be successfully completed, as previously discussed in the email thread. Please take a look at the changes and approve as soon as you can.

[Please answer questions and remove ARMChangesRequested tag]

There seem to be some new linter errors show up now (either because of changes or because some linter issues got fixed):
❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Insights/preview/2023-06-01-preview/privateLinkScopes_API.json#L929 |
❌ XmsEnumValidation | The enum types should have x-ms-enum type extension set with appropriate options.Location: Microsoft.Insights/preview/2023-06-01-preview/privateLinkScopes_API.json#L1089

This avocado warning sounds like its caused by an accidental oversight?

The example JSON file is not referenced from the swagger file.
readme: specification/monitor/resource-manager/readme.md
json: preview/2023-06-01-preview/examples/PrivateLinkScopedResourceUpdatePlatformMetrics.json

/azp run

I see there are still ModelValidation issues around the casing for the enums. Please advise on how to make my enums case-insensitive - otherwise, validation issues should be resolved

I see there are still ModelValidation issues around the casing for the enums. Please advise on how to make my enums case-insensitive - otherwise, validation issues should be resolved

Doesn't it just want you to case it as 'Resource' instead of 'resource' in the examples? Would there be a problem with doing that?

For Semantic I think there are also maybe one or two places where you need to fix
          "readonly": "true",

to
          "readonly": true,

?

@TimLovellSmith since the API accepts case-insensitive kind, I don't want it to be labeled as case-sensitive in the swagger docs. Also not certain this is the case but it looks like all the other enum examples I've looked at uses uppercase definitions.

This looks a little strange: https://github.com/Azure/azure-rest-api-specs/pull/24590/checks?check_run_id=17758414025

please update here to your new apiversion

please update here to your new apiversion

I believe that is addressed here: https://github.com/Azure/azure-rest-api-specs/pull/24590/files#:~:text=- Microsoft.Insights/preview/2023-06-01-preview/privateLinkScopes_API.json
I don't intend to change the settings for older tags, let me know if there is something you'd like me to change

please update here to your new apiversion

@kazrael2119 I believe that is addressed here: https://github.com/Azure/azure-rest-api-specs/pull/24590/files#:~:text=- Microsoft.Insights/preview/2023-06-01-preview/privateLinkScopes_API.json
I don't intend to change the settings for older tags, let me know if there is something you'd like me to change

Do you mean in the future, there will be a composite apiversion like 2023-04-01 which contains all services with their new apiversion? So you don't want to change the setting for older version?
For JS, we have so many duplicate schemas in monitor. like these: https://github.com/azure-sdk/azure-sdk-for-js/pull/5546/files#diff-b4f88d7279e423e43b8b4d038d99dfdd2290d798e0e96815fd72ce98cf331da2R147-R152
And some of them may be related with your service and other service. Do you think it's good to fix these duplicate schemas in the next composite apiverison?
If yes, I think we can approve js breaking in this pr

Hi @rkmanda
This PR was not merged earlier due to a delay in a partner service implementing their changes. At this point, however, we are getting close to GA and we need to merge this PR from before. Can you reopen the pull request?

@JeffreyRichter @rkmanda I think perceived version number age is probably starting to be a concern if this is for a new API - is this preview version number okay to carry on with?
/cc @qinjoshua

2023-06-01-preview? Azure doesn't have any policies about the api-version date being related to an actual date. Just that newer versions always have a later date and that preview and stable versions not share the same date. So I'm OK with 2023-06-01-preview coming out now. @rkmanda , any concerns from your end?

Hey bot, don't close the PR please - we're waiting on corresponding changes from a partner team before the rest api can be updated

We are still waiting for response from partner team before this can be merged

We are ready to merge

/azp run

2023-06-01-preview? Azure doesn't have any policies about the api-version date being related to an actual date. Just that newer versions always have a later date and that preview and stable versions not share the same date. So I'm OK with 2023-06-01-preview coming out now. @rkmanda , any concerns from your end?

@jeffrichter Newer how, or on what date, exactly? The reason I'm asking is that it seems like there are some newer versions than this now, since the PRs are not getting merged in version order. @qinjoshua Do the newer versions include these changes also?

Got

This is the latest API version for microsoft.insights/privatelinkscopes, although it might not be the latest api version in microsoft.insights overall

The repo tooling is setup to work best when new api-versions build on top of the previous api-version. Our breaking change tooling leverages this, for example.
Teams should not be inserting api-versions in between other versions. I don't know how well things will work if this is attempted. At a minimum, people like you & me looking at the folder will be confused as to what is going on.
Maybe I need more summarized context as to what is being attempted with this PR to weigh in properly?

Hi @JeffreyRichter ,
What happened here is that this feature was finished about a year ago and was waiting for changes to be implemented and rolled out in a partner team before it could be released publicly. That turned out to be about a year-long wait; during that time, the new API version was already released, but the documentation was not. We are finally ready to roll out the REST API documentation for this new feature, which is why the new API version we're releasing is chronologically from last year.
Separately from that, the Microsoft.Insights provider is unique in that it is shared by multiple teams, and as a result has inconsistent version numbers across different resources. For instance, the latest version of Microsoft.Insights/dataCollectionEndpoints is not the latest version of Microsoft.Insights/privateLinkScopes. We do have an exemption for this inconsistency, since it is impossible for us to coordinate version numbers across every team that uses our namespace. As a result, even though 2023-06-01-preview is unfortunately not the latest version in Microsoft.Insights, it is the latest version of Microsoft.Insights/privateLinkScopes.


Requests Section

A request page which will contain the name, linkedIn profile and the requests of the user.
@yash982000 please assign it to me.

A request page which will contain the name, linkedIn profile and the requests of the user.
@yash982000 please assign it to me.

Done and merged..!!


trigger netlify deploy nightly

This sets up a job to run at 00:00 UTC every day, which rebuilds the site from the mochajs.org branch.  This keeps the list of supporters up-to-date.  It relies on a secret env var to do its thing.
Will try to figure out how to test this...

Yeah, I don't know how to test this.  Maybe we just merge it and see if it does anything.

The reason is because we (I?) tend to get a fair amount of email from people wondering why their logo isn't on the site.  Since we're only fetching the logos and links at build time now, we need a nightly job to keep it up-to-date.

Yeah, I don't know how to test this. Maybe we just merge it and see if it does anything.

Why not configure it to run on a push action once. When you see it works, you can remove the push action.

Coverage remained the same at 93.578% when pulling cdb1d7efa879759ebe4ee9ef41c4ceda425787af on boneskull/netlify-nightly-deploy into dc26e903cc1630c08b349dbf7853527c27f5f2ed on master.

I want to merge this, but given that all deploys seem to be failing atm, that needs fixing first

hmm, maybe it's fixed now.

I think mochajs.org needs fast-forwarding.

OK, I see why it's breaking.  See https://github.com/mochajs/mocha/pull/4339
The svg's on OC's side are broken


Pause/Resume screen and widget refresh?

I've found that the timer-based synchronous hybrid micropython driver performs better on ESP32 than the async version.  But when setting many display settings for various elements on screen, the update is relatively slow and clunky as elements are moved, text/colors/alignments/opacity/etc. are changed, etc. — all visibly.  This is likely because the time to perform the updates is long compared to the interrupt-driven timer tick interval.  Changes are not "coalesced".
I was surprised to find that LVGL didn't itself offer a pause/resume feature to pause refreshes (unless I'm missing it) while various on-screen elements are reconfigured.
So I hacked one together by abusing the scheduled and max_scheduled event loop parameters:
def pause():
    global paused
    if disp and not paused:
        disp.event_loop.scheduled = disp.event_loop.max_scheduled # Stop lv.task_handler() calls
        paused = True
        return True
    return False

def resume():
    global paused
    if disp:
        disp.event_loop.scheduled = 0 # Resume them
        paused = False

So I can:
display.pause()
#many LVGL widget updates
display.resume()

This really smooths out changes to widgets on screen, and improves speed.  But is there a cleaner way to do this?  If not, would it be sensible to implement some pause/resume logic in the hybrid drivers?

Thanks, that makes sense.  Letting asyncio handle the event loop would also have this characteristic.  It's easy to overwhelm the one asyncio event loop in MP though, so I've found timer-interrupt performs better.
By default micropython hybrid drivers update every 40ms. With slow displays and some interface niceties for calling back into the C-code, it seems updates can span ticks.  Once one tick gets "caught in traffic", the slowness of the display update likely means many will.  But I believe an option/config in the hybrid driver to avoid calling task_handler() during some period would do the trick.  That's effectively what my hack does.

Thanks.  I have a flag which, when set, refuses to "disable again".  But great idea for nesting calls!  That will simplify things.  It might also then be possible to wrap this in a context manager (with lv_utils.disable_refresh: or similar) and not worry about nesting.
RE speed, I just assumed ESP32/uPy and my slow SPI display (ST7789) were the issue.  I do tend to update maybe 15-25 attributes for a few widgets on screen in one go, including positions, font size, colors, alignment, recolor, text, bg image source (which reads a .bin from slow flash).  Would you expect this to happen all within one tick on an ESP32?  To me it wasn't surprising that this takes some time; loading one 240x135 .bin takes maybe 300-400ms.  And since I'm not double-buffering, it's also not perhaps surprising that once one tick gets passed, LVGL tries to sync the display to the current "half-finished" layout, additional ticks arrive, and so on.  I haven't tried freezing or native code (but freezing commonly updated code does defeat one of the main strengths of MPY IMO!).
I have overloaded the normal API with custom __getattr__ and __setattr__ which translate some values and makes it much simpler to work with LVGL from micropython (see this gist if interested).  I wonder if that's adding much overhead to the pure set_style_xxx_yyy() calls.
I'm not using any event callbacks, it's really time-based and button-driven "scene" changes that were quite disjointed without a disable/enable wrap, and work pretty well with them.
If you are interested I could attempt a small demo case that illustrates changes spanning a tick.


enum Result is conflicting with Swift.Result type

Describe the bug
Using the data model conflicts with Swift.Result type and leads to a compiler error.
It can be resolved by explicitly using "Swift.Result".
But it would be nice if the types would not conflict, especially not with such a central one.
Expected behaviour
Using the data model does not conflict with Swift.Result type.
Possible Fix
Rename enum Result to something different.

@ArturFriesen in this version we don't support Swift.Result, because in our architecture implementation in returning object we can receive not one Error, it's may be array of Error's


Way to draw text

is there any function to draw text with breadx?
quick search gave me xcb_image_text_8

The proper way of drawing text is to load whichever font you want (I've found rusttype to be a good tool for this), convert whichever glyphs you want to draw into images, convert those images into Pixmaps with create_pixmap_from_image, and use copy_area to copy those glyph-images onto your window or pixmap or what-have-you.
Yes, the xcb_image_text_8 request has an equivalent in breadx, but I haven't gotten around to implementing a convenience method for using it. This is partly because the breadth of the X11 API is exhausting to implement in its entirety, and partly because the native string drawing API is counterproductive to use. It uses a font format that no one else uses and is generally hard to port to other platforms. No serious application has used it since the 90's.
That being said, if this is not a serious application, I cannot stop you from doing:
use breadx::auto::xproto::ImageText8Request;
let text = String::from("This is the text I want to draw");
let request = ImageText8Request {
    drawable: win.into(),
    gc,
    x: 10,
    y: 10,
    string: text.into(),
    ..Default::default()
};
conn.exchange_request(request)?;


[logs] Support Shift JIS encoded files

What does this PR do?
Adds Shift JIS (Japanese) encoding support when tailing from file.
It can be enabled by adding encoding: shiftjis in a log configuration.
About Shift JIS: wikipedia
Motivation
Japanese versions of Windows uses Shift JIS as a primary encoding for Japanese.
Logs from apps and package softwares in Shift JIS cannot be handled by Datadog directly,
So currently, users need to forward logs to fluentd once, and translate to utf-8 with fluentd plugin, then forward them to Datadog.
With this patch, those users can send Shift JIS logs directly via Datadog agent.
Additional Notes
Shift JIS is written as ShiftJIS, Shift_JIS and Shift-JIS. The underscore and hyphen might be annoying for users to configure correctly, so I chose no hyphenation shiftjis as an option string in the configuration.
Describe how to test/QA your changes
Tail files encoded in Shift JIS.
On linux system, generate some log lines with Shift JIS encoded message.
echo "日本" | iconv -t shift_jis | logger
logs:
        - type: file
          path: "/var/log/syslog"
          service: syslog-test
          source: syslog
          encoding: shiftjis

for Windows, I used tomcat. Set Java locale in bin\catalina.bat as the following
set "JAVA_OPTS=%JAVA_OPTS% -Duser.language=ja -Duser.region=JP"
and set log file encoding in the conf\logging.properties.
1catalina.org.apache.juli.AsyncFileHandler.encoding = SJIS
Then logs\catalina*.log will be written in Shift JIS. Encoding can be confirmed with editors.

With current released agent, Shift JIS logs are shown with garbled characters like the following

With this patch, logs show up as expected.

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] The appropriate team/.. label has been applied, if known.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the config template has been updated.

Hi, thank you for your review! I updated as followings,

Replaced option string shiftjis with shift-jis
Added some comment in pkg/logs/input/file/tailer.go
Reformatted with gofmt

Awesome, thanks for the contribution!  I also added a docs link.  And I added shift-jis to my upcoming tech talk on encodings :)

Thank you, @djmitche !!


nlohmann_json: disable tests for now since they timeout

Motivation for this change
Should fix https://github.com/NixOS/nixpkgs/issues/72890 and https://github.com/NixOS/nixpkgs/issues/72717
Workaround for https://github.com/nlohmann/json/issues/1816
Please backport to 19.09 ASAP since the channel is blocked by this!
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Please backport with git cherry-pick -x 7456f19b40ddd9008275e75c9258e9c3bad38f66 onto the release-19.09  branch and send a PR :)


GestureDetector widget's onScale also detects onPan gesture

Steps to Reproduce

Execute flutter run on the code sample
gesture pan ( drag on screen )

I checked the occur in stable and master
Expected results:
onScale does not detect the gesture
Actual results:
onScale detect the gesture
https://user-images.githubusercontent.com/7422251/172003966-8a8ac6d0-a1fe-45b6-af6a-c2bc870f9023.mp4

Code sample
// ignore_for_file: unused_import

import 'package:flutter/material.dart';
import 'package:mangaplotter/lang_localizations.dart';

class SamplePage extends StatefulWidget {

  SamplePage(): super();

  @override
  SamplePageState createState() => SamplePageState();
}

class SamplePageState extends State<SamplePage> with WidgetsBindingObserver {

  @override
  void initState() {
    super.initState();
  }

  @override
  void dispose() {
    super.dispose();
  }

  int index = 0;
  @override
  Widget build(BuildContext context) {
    return GestureDetector(
      child: Container(
        color: Colors.red.withAlpha(100),
        height: 500, width: 400,
      ),
      onTapUp: (_){
        showSnakeBar("onTapUp");
      },
      // onPanStart: (_){
      //   showSnakeBar("onPanStart");
      // },
      onScaleStart: (_){
        showSnakeBar("onScaleStart");
      },
      onLongPressStart: (_){
        showSnakeBar("onLongPress");
      },
    );
  }

  void showSnakeBar(String message){

    ScaffoldMessenger.of(context).showSnackBar(
      SnackBar(
        duration: Duration(seconds: 1),
        content : Text( message, )
      )
    );
  }
}

Logs
[✓] Flutter (Channel master, 3.1.0-0.0.pre.1101, on macOS 12.4 21F79 darwin-x64, locale ja-JP)
    • Flutter version 3.1.0-0.0.pre.1101 at /Users/hata/Desktop/develop/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1f53fcd92b (10 hours ago), 2022-06-03 20:58:10 -0700
    • Engine revision 14194cbef3
    • Dart version 2.18.0 (build 2.18.0-167.0.dev)
    • DevTools version 2.14.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/hata/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] Connected device (3 available)
    • hataのiPad (mobile) • 6ed5d4adb492208befce2e5102f6a47aefbe7c82 • ios            • iOS 15.4.1 19E258
    • macOS (desktop)    • macos                                    • darwin-x64     • macOS 12.4 21F79 darwin-x64
    • Chrome (web)       • chrome                                   • web-javascript • Google Chrome 102.0.5005.61

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Scale is a superset of pan.
See the GestureDetector documentation: https://github.com/flutter/flutter/blob/fb57da5f945d02ef4f98dfd9409a72b7cce74268/packages/flutter/lib/src/widgets/gesture_detector.dart#L167
/// Pan and scale callbacks cannot be used simultaneously because scale is a
/// superset of pan. Simply use the scale callbacks instead.

Has this specification been around since 2.0?

Hi @hatano0x06, this is working as intended for the reason specified above https://github.com/flutter/flutter/issues/105359#issuecomment-1146648729

ok
thanks
please close this issue


Refactor: restructure core widget

Wasn't entirely complete with what I wanted to pull out from core.py but the idea was separate the widgets from each other instead of it feeling like we were adding stac_discovery onto the biomass_layers

@jjfrench am I right that this is refactoring (renaming core to base_layer, putting the histogram stuff frombase_layer to biomass_layers.histograms and the biomass stuff from base_layer to biomass_layers.biomass_widget) but not changing any behavior or fixing bugs ? If so looks good to me. Otherwise, I haven't digged much into this code in the past so can't review the details, but, I guess you tested locally that things are still working as expected after these changes (looks like we don't have any test) ?

@emileten Right, core -> base_widget and pulled out histogram/biomass_layers from core into the biomass_layers widget. I tried to keep the functionality the same so I added histogram_on_click to pass the button event through and of course, some references to self became the class. Aside from that, nothing else added.

@emileten Right, core -> base_widget and pulled out histogram/biomass_layers from core into the biomass_layers widget. I tried to keep the functionality the same so I added histogram_on_click to pass the button event through and of course, some references to self became the class. Aside from that, nothing else was added.

@abarciauskas-bgse , do you have thoughts on this PR?


Improve explosion logs

About the PR

Enable explosion logs
Add explosion types to their logs
Add causes to IThresholdBehavior
Add causes/triggerer to a bunch of explosion logs
Remove an explosion type that doesn't seem to be needed due to other explosion logs
Add logs for damage from explosions to entities with either mind or explosive component

Now also includes a sneaky power cell update. Small/med/large are now about 56/78/90 base at the epicenter. No CL because spoilers, also I've never seen anyone use this feature. 36e3743
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

need


Structure inventory samples should be consistent across flood scenarios

https://github.com/HydrologicEngineeringCenter/HEC-FDA/blob/b28616e688540d279c999c05c3adb91909c7be0c/fda-model/stageDamage/ImpactAreaStageDamage.cs#L208
It appears that FDA2 is doing a whole new set of structure inventory realizations for each flood frequency/WSE. Should we be doing that though? If bob's house is 15% more vulnerable to flood damage than most of that occupancy type, and that occupancy type is actually say 5%+ our expected value, that is going to be true for bob's house equally when it gets hit with a 10 year event as with a 500 year event.
If we don't correlate these structure realizations across flood events we would be allowing them to vary based on flood event, for example bob's house varying in foundation height based on the flood that hits it. While FDA is not a discrete event model, and this is unlikely to really matter much in the final distributions, It seems like iterating through flood event scenarios inside of the iterations loop rather than vice versa, and generating a fixed realization of the inventory for each iteration to be used for all flood events in that iteration, would not only be conceptually more accurate, it would also dramatically speed up computes by reducing the number of inventory samples generated by a factor of the number of flood events analyzed.

it seems like the sampled structure should be held constant across the entire domain of the frequency curve for a given relationship.

I'd like to pursue this ASAP. @Brennan1994 we'll want to think about this together because the approach conflicts with your preference to do one profile at a time. Maybe we can figure out how to satisfy both concerns?


Prepare for new release of Bitbucket

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6257126974, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6257128999, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/6257131463.

The task will be addressed in #321.


todo(ui): Add codegen for graphql types on front end

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Closing this for now, this needs some rework and more thought and hasn't been a recent priority.


DNN Support for dilated convolutions

Hello all!
First I want to send my gratitude to all the people working on this great library. It is one of my favourite ML/image processing libraries out there.  I specially like the DNN part of it it is so much easier to use then some of the others out there and that you can drive it directly in C++ is great!
However I did notice there are some holes in functionality and I was wonder in particular if there is any future plan to add dilated convolutions option to the current DNN convolution layer.
I hacked in some support myself to see if they do make a difference so I changed the dnn_segmentation example to  add them. Unfortunately my hack would require all examples to be rewritten as there are now two additional parameters in the con layer.
Here are some example images using a trained head segmentation dataset testing it on some celebA images with and without dilation and you can see some decent improvements by just using dilation (that's the only change I didn't touch the network structure itself so far)
Non dilated example 1
Dilated example 1
Non dilated example2
Dilated example 2
Non dilated example3
Dilated example 3
Non dilated example4
Dilated example 4

Thanks, glad you like dlib :)
I'm not sure, I think @OranjeeGeneral was maybe adding one?   It's definitely something that would be nice to have.

Hello Davis thanks for your answer.
I see. well I can offer my changes if that helps but as I said I don't see how they can be added without having to change every example out there as I had to add two template parameters to the con layer and unlike methods/functions you can not have const literal values in templates. This makes it sound like a big breaking change. Also it only works with CuDNN 6 and higher.

Right, don't submit that in a PR.  If there really is no way to upgrade the
con layer without breaking existing stuff then the right thing to do is to
just add a new layer type for this.  Although I would expect you could just
add two new optional template arguments to con.  You can certainly have
default literal values in templates.  The existing con layer already has
them even.

Ah silly me of course I just have to move the new parameters to the end of the template definition because they are the only ones with default values then and then it works without having to change the existing examples and so on.
But the other issue that it works only with CuDNN >=6 still remains. As only with these version they changed the convolution layout to support it, is that an issue? Problem I think would be that PREPROCESSOR definition is currently not reachable in layers.h

That's fine.  People can get a runtime error if they pass a dilation value
other than 1 and are using an old version of cuDNN.

I'm also very interested of having a dilated convolution feature.
I'm looking at the code and it looks easy, just want to make sure:
Basically, the only thing to do is here:
cudnn_dlibapi.cpp +875, add some int dilate_x, dilate_y parameters exposed in the con_ layer, right?
So basically instead of having this:
```
CHECK_CUDNN(cudnnSetConvolution2dDescriptor((cudnnConvolutionDescriptor_t)conv_handle,
padding_y, // vertical padding
padding_x, // horizontal padding
stride_y,
stride_x,
1, 1, // must be 1,1
CUDNN_CROSS_CORRELATION)); // could also be CUDNN_CONVOLUTION
I would need something like:

            CHECK_CUDNN(cudnnSetConvolution2dDescriptor((cudnnConvolutionDescriptor_t)conv_handle,
                    padding_y, // vertical padding
                    padding_x, // horizontal padding
                    stride_y,
                    stride_x,
                    **dilate_y, dilate_x,**
                    CUDNN_CROSS_CORRELATION)); // could also be CUDNN_CONVOLUTION

Am i missing something or is this the idea?

Thanks,

@edubois
Unfortunately it isn't that easy as that. First this only adds support to CUDA path so you need to find a default backup for CPU the easiest choice would be only support dilation factors to be 1,1.
Also you need to add another parameter to the layer so and add defaults otherwise all existing network definition would stop working when encountering this new conv layer
But it gets worse as unfortunately dilation also has an impact on the padding of the convolution layer, the padding needs to be enlarged by the dilation factor and here the real problem comes in. As now you can no longer use CUDA trained models with NON-CUDA. As the serialization of the model doesn't match up.
So it is all a bit of a mess. I guess the best solution is to add CPU support for dilation as well and then all these problems go away.

Yes, the cuda side is easy.  But a complete PR needs to include a CPU implementation.

Well I guess if speed isn't such a major concern the easiest way for the CPU implementation would be to  enlarge the convolution kernel with zeros.

Don't do that.  Speed isn't a huge deal, but let's not be crazy :)


PHP Libraries

Hi owners,
I was wondering if you would accept a php jwt library as a contribution (probably together with some framework integration packages).  There are quite a few libraries out there already, yet, i am not really satisfied with their quality which I am really concerned about. Also, the implementations using these libraries are also not really good, so I intend to provide a full solution for the PHP community.
Regards,
Mark

HI @sagikazarmark,
send me an mail and I will setup a repo for you and grant you ownership.
We welcome every jwt implementation in any language.


Suggestions (Implemented)

#23 WIP - points 1-4 implemented

package: move dependencies to dev and peer
react components: remove constructor calls, use default syntax
lint: sort rules by logic, enforce react components sorting

regarding points 5-6, we could think together how to best approach this. do u know how to test performance?
I currently don't have access to iOS devices, so actually not using the project. I'm helping this since I need it on Android, so I want to expedite the process :)

@goldylucks Thank you for PR.
I just tested it out ,and seems like there is no difference . resolveAsset is a simple function and i guess that will not drop performance

gotcha. so atm I say let's just merge this. points 5-6 r not critical anywayz.
btw, the two types of tests failed for me with a fresh clone and npm i
Also, how did u test the performance difference?

@goldylucks you can use Systrace.  if you can help us to release android version that would be great. @gevorg94 will check this on device tomorrow. Btw tests should not fail. please look why it happens

Cannot find module 'ReactNativeDefaultInjection' from 'setup.js'
happens after cloning master

@shahen94 I can take a swing at it if provided some pointers. haven't done any work on RN core or authored any plugins that interface with native components

Any reason this is not merged?

@goldylucks Please fix the tests, they shouldn’t fail, after that we’ll check the PR

@goldylucks please put babels back to dependencies, we are having a lot of errors because of this.
I think you need to put react back to dependencies too for passing tests successfully.

Sorry for not getting back at you sooner.
Dependencies are a big no no for npm packages, using peer is better, especially for react
If your tests require react, put it in devDep, not dep.
Does this makes sense?


Fix link to index.css

@thachhoang thanks Thach!

The GitHub Pages site didn't seem to build correctly, all the resources links are currently 404, like: http://joelittlejohn.github.io/jsonschema2pojo/resources/public/lib/codemirror-compressed.js

Yeeeeaaah.
I've tried to re-run the built but received a timeout again. Either GitHub is applying a new timeout, or the contents of gh-pages has got large enough to hit some build timeout, or GitHub is having some issues at the moment. I'm going to do a little more research and see if I can get this to build ASAP.

Looks good now after another re-run.