Update to diesel 2.0

When changing the version to 2.0, the build fails with
> rustup run stable cargo build
    Updating crates.io index
   Compiling version_check v0.9.4
   Compiling syn v1.0.107
   Compiling serde v1.0.152
   Compiling proc-macro-error-attr v1.0.4
   Compiling proc-macro-error v1.0.4
   Compiling serde_derive v1.0.152
   Compiling diesel_derives v2.0.1
   Compiling serde_json v1.0.91
   Compiling diesel v2.0.3
   Compiling diesel_json v0.1.1 (/home/jayvdb/rust/diesel_json)
warning: #[sql_type] attribute form is deprecated
  = help: use `#[diesel(sql_type = sql_types::Jsonb)]` instead

warning: #[sql_type] attribute form is deprecated
  = help: use `#[diesel(sql_type = sql_types::Jsonb)]` instead

error[E0107]: this struct takes 1 generic argument but 2 generic arguments were supplied
  --> src/lib.rs:84:38
   |
84 |         out: &mut diesel::serialize::Output<W, Pg>,
   |                                      ^^^^^^    -- help: remove this generic argument
   |                                      |
   |                                      expected 1 generic argument
   |
note: struct defined here, with 1 generic parameter: `DB`
  --> /home/jayvdb/.cargo/registry/src/github.com-1ecc6299db9ec823/diesel-2.0.3/src/serialize.rs:35:12
   |
35 | pub struct Output<'a, 'b, DB>
   |            ^^^^^^         --

For more information about this error, try `rustc --explain E0107`.

Just noting https://github.com/terry90/diesel_as_jsonb does support diesel 2.  It doesnt havent any tests, but very limited experimentation suggests it works.  I havent yet compared the feature sets.

New version with necessary changes released:
diesel_json = "0.2.0"


New doc comment syntaxt

A very simple implementation of new doc comment syntaxt. This just "replaces" /** and */ with <* and *>, it does not provide any better highlighting for the content of the comment.
The important changes are in grammar.js & src/scanner.c, the rest is autogenerated.
Closes: #11

Nice one! Thanks @tomaskallup


Add support for Protocol Info objects

What?
Fixes #41
Fixes #42
Fixes #164
Proposal
ProtocolInfo objects are opaque objects that may be used by tools to perform/add protocol-specific operations/features. Although the object is opaque from a specification point of view, we'll maintain a catalog of protocolInfo objects, so they are standardized across tools but don't compromise the specification. That doesn't stop anyone to use custom protocolInfo objects, at the expense of creating the tooling to support them.
ProtocolInfo objects can be attached to:

Channels: Describes protocol-specific information about the channel, e.g., queue name, exchange name or partition number.
Operations: Describes protocol-specific information about the operation. Example: noAck (AMQP).
Messages: Describes protocol-specific information about the message. Examples: protocol headers/properties like QoS (MQTT), delivery_mode (AMQP), message key (Kafka), etc.

Reusing protocolInfo objects will be possible through traits (#108) and overlays (#107).
Missing things

[x] ~Add to Markdown version of the specification.~
[x] ~Add to JSON Schema version of the specification.~

@RobertDiebels @gmr ☝ early draft of the new feature to support protocol-specific information.

@RobertDiebels @gmr ☝ early draft of the new feature to support protocol-specific information.

+1 for the traits compatibility. Re-using protocol-info seems super useful.

BTW, there's already a proposal for traits: https://github.com/asyncapi/asyncapi/issues/108.


Instatus

Do you want to add or update the vendor? Adjust the title accordingly!
How to use? Fill the yaml file below!

name: Use the vendors name
base_pricing: Use the vendors cheapest available price suitable for teams/companies. A plan limited to less than 10 users may not be suited for companies.
sso_pricing: Use the vendors cheapest price that includes SSO.
scim_pricing: Use the vendors cheapest price that includes SCIM.
pricing_scheme: How is the pricing? Is it per user per month? Per month?
pricing_sources: Add a link or a note to where you got the pricing from. One per line.
notes: If you need to clarify pricing, please add a note.
free_sso_providers: Do they support free SSO providers like Google, Apple, Github etc.? One per line.
updated_at: yyyy-mm-dd of the day you filed this.
vendor_url: Use the vendors public website

---
base_pricing: 20
currency: USD
free_sso_providers:
  - Google
name: Instatus
notes:
pricing_scheme: per month
pricing_sources:
  - https://instatus.com/pricing
scim_pricing: unknown
sso_pricing: 300
updated_at: 2024-01-09
vendor_url: https://instatus.com

Fantastic contribution, @pjsmits! Thank you!


Spring integration

Want must be done to use NILS in a Spring / Spring Boot environment?
Can we provide a Bean / Controller or something?
At least a documentation how to use NILS in Spring / Spring Boot should be written.

Integration is available under the new repo 'nils4spring'.
See https://github.com/codepulsar-com/nils4spring


Missing dependency in requirements.in

Looks like install dependency tqdm defined in setup.cfg is missing from requirements.in file.
It is however included 'by sheer luck' in requirements.dev as it is a dependency of twine.
On a side note, blake is duplicated.

I'm not fan of copy-pasting things, I don't want to maintain two lists of requirements, they'll get out of sync.
Install requirements should stay in install_requires, and developement requirements should stay in requirements-dev.txt.
I bet you've found a missing tqdm because you followed the Contributing section in the readme, if so, what about adding a pip install -e . in it? It would provide the developer with a working powrap (with install_requires satisfied).
The only "bad" part of it is: we're not pinning install requirements (for developer uses, not for end users, so just to reproduce bugs from a dev env to another dev env). If we need to pin them we could easily pip-compile setup.py. Then we could also add -r requirements.txt in requirements-dev.in to have a common, full, pinned, list of dependencies, which is nice to reproduce bugs (from a dev env to another dev env only, again, not from a user env to a dev env, as a user can have different set of version installed, a user don't use a specific venv for each command), but I think it's too convoluted for a small project.

Ohh got it, I have a typo in the README file, it tells to install requirements-dev.in instead of requirements-dev.txt :(


Expose option to customize text style on CupertinoActionSheetAction

Proposal

It is recommended to modify CupertinoActionSheetAction to expose its Style interface to avoid code redundancy

@NaCoLiu
Can you provide a use case where it would require you expose Style interface that helps to avoid code redundancy.

Just want to expose its Style interface, otherwise you need to set a layer of Style on the outside

The style used is defined here: https://github.com/flutter/flutter/blob/d147e52d6ae09c73947f1e98e5e522e02a865297/packages/flutter/lib/src/cupertino/dialog.dart#L1283

Hi Team,
I’m still a bit unclear on this issue. Are we required to expose a custom style property? Could you confirm if my understanding is correct?

Correct.

Hi @victorsanni, I don’t believe SwiftUI or UIKit exposes functionality to modify the text of an AlertDialog or ActionSheet. Is this change essential to include in the Flutter framework?

Thanks for you proposal. As far as I see in my experiment on XCode, SwiftUI doesn't really support modifying the text styles (they don't apply them even if you specify.) I don't think this is a direction we'd like to pursue, but if you find it useful in your projects, you can still open a PR and let's discuss about it.


Error on gulp after DDEV v1.21.4 upgrade [1h]

Seems like the problem is due to nvm-defined node version is not being picked up.

A workaround for this is to ddev ssh and then gulp.

Found something similar reported on DDEV Github: https://github.com/drud/ddev/issues/4499

9358a3d fixed this, but not sure it's the best approach.
@AronNovak what do you think?

@anvmn It's more or less okay, ddev's nvm handling is not so stable across releases, tweaks like this are unfortunately needed from time to time.

Oddly, no changes in nvm handling for some time. But it is in fact hard.

But, of course...

https://github.com/drud/ddev/issues/4499#issuecomment-1419989916


Demo directory for link prediction via random walks contains a very large amount of code

Description
demos/link-prediction/random-walks contains a utils module which contains a substantial amount of code.
We should move as much of this into the core library as possible, since moving this into the library means:

the code is much easier to maintain, and can be tested independently from the demos
it's easier to reuse it across more notebooks
a user can follow/copy the demo notebook without having to dig into / copy a whole mini module shipped alongside the demo

User Story
As a data scientist
I want to use stellargraph functions to help me do link prediction instead of more code shipped with a demo
So that my job is easier
Done Checklist

[ ] Produced code for required functionality
[ ] Tests written and coverage checked
[ ] Code review performed
[ ] Documentation on Google Docs  (if applicable)
[ ] Documentation in repo
[ ] Version number reflects new status
[ ] CHANGELOG.md updated
[ ] Team demo

Not only does this contain a large amount of code, but it seems to contain its own implementation of node2vec https://github.com/stellargraph/stellargraph/tree/develop/demos/link-prediction/random-walks/utils/node2vec (taken seemingly directly from https://github.com/aditya-grover/node2vec) rather than using the one in the library.


0.2.1bump

version bump
updated poetry, added python 3.8 to release actions

coverage: 84.257%. remained the same
when pulling 33569356ea144a74c833adcfc4e56acff2dd5d0f on 0.2.1bump
into b77f515063be00afee3a2d2683e6119146913ae2 on develop.


Nuclear Module

Dunno if this is right place to write down, but i created a package called nuclear-module to act as a glue to bind each part of a nuclear-js module.
Module pattern is already shown as best practice in the docs, i've been creating different modules with the same boilerplate already. So i created it: https://github.com/usirin/nuclear-module and published to the npm under nuclear-module.
It is mainly how I, and my colleagues in my company, write down nuclear-js modules. It expects you to write your store handlers and actions in a slightly different way.
Disclaimer: By no means I am saying this should be the way to go, but i am simply asking feedback from the community.
As a community, we can take action to come up with a defacto solution for exporting nuclear-js modules, which can be a foundation for community-driven modules.

Hi @usirin this is really clever and very convenient if you want to be able to inject a reactor into a module instead of having a singleton.
Perhaps one suggestion I would make is to have stores be an object so one can easily tell what path of the registered stores for a module without going deep into the code.
module.exports = NuclearModule({
  stores: {
    count: require('./stores/counter')
  },
  actions: require('./actions'),
  getters: require('./getters')
})

I like the convention and declarativeness of the way actions and stores are created,

Hello @jordangarcia thanks for the feedback. It's much appreciated!
About store registration issue; we were using the same approach at the beginning, but probably as a matter of preference, we liked it to see the initial getter path in the store declaration.
I guess you are right, since using array also removes the possibility of reusing a store (even though it looks like it's an edge case), using an object looks like a better option.
Also I think we can start compiling down a list of modules that can be used in a pluggable fashion for each project. (e.g authentication module, rest api cache module, component state module, dev tools, etc.). I think this module pattern can open up a really simple way of sharing our application code with each other, and hopefully improve our products with community driven modules (possibly with an opinionated framework).

@usirin this looks great. I've also had same feelings about modules and I was wondering why it's not something mandatory in NuclearJS. Than I realized that NuclearJS is better to stay as it is and we, the users should find betters solutions to integrate it in our codebases.
I have something similar with your approach, I must say that is in it's early stages, but it started after getting feedback from colleagues that were complaining about the boilerplate in stores declaration.
Here is the source code: https://github.com/raulmatei/frux/tree/develop/src
Here is an example: https://github.com/raulmatei/frux/tree/develop/examples/counter
This is not a nuclear module system as yours, and it's also coupled to the rendering system (which is React in this case). I have a plan to clean it up and add tests as soon as I'll get some free time. But the feeling is that (as you've said) we have the right tools on our hands, and we can share ideas to move NuclearJS more closer to other Flux implementations, and by this I mean  creating an ecosystem of shareable modules and addons to bring more people to use it.
@balloob has also some great ideas in his https://github.com/balloob/home-assistant-js/ project and maybe there are others which are using it with different patterns that may be worth to share.
Raul.

Sorry for late reply, last 3-4 months has been really busy for me, but I was putting so much thoughts on how I can improve things at nuclear-module project especially after i used it in many other packages and private/personal pojects, and drafted an issue in usirin/nuclear-module#5 to sum up what I have in my mind. If you guys can read and give feedback, it would be appreciated so much.


Transaction history entries for shielding transactions are showing incorrect amounts

Describe the issue
Please provide a general summary of the issue you're experiencing
In Nighthawk, I autoshield my funds and expect to see a wallet event for it. I see an outgoing txn with the proper memo, but the amounts are wrong.
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Launch Nighthawk 2.0
Import a wallet with transparent funds or create a new wallet and send transparent funds to it
When the transparent funds are available to spend, swipe to the transparent balance tab in the home balance carousel.
Observe the "Shield now". Press it.
Tap the "Great!" button to confirm shielding
Observe that your transparent balance is now correct at 0 ZEC (or TAZ if using testnet)
Find the outgoing transaction in the list of recent events, or navigate to the full transaction history by tapping "View transaction history"
Observe the transaction details

Expected behaviour
Tell us what should happen
I expect to see the correct net value delta of the transaction at the top, as well as in a line item at the bottom.
Actual behaviour + errors
Tell us what happens instead including any noticeable error output (any messages
displayed on-screen when e.g. a crash occurred)

Instead of the correct amount, I see what appears to be only the fee.

App Version: 2.0.0
iOS Version: iOS 17
Device: (if applies) N/A

Any extra information that might be useful in the debugging process.

If you need to see the value of the shielded output, this is available from the transaction outputs. But I think it would be confusing to show the full shielded amount as received.

@tw0po1nt given what I've described above, is there any action that needs to be taken here, or can this be closed?

This can be closed. How to resolve the UX confusion can be discussed further in Discord


Add the ability to put HTML in

Lead image caption should allow HTML.

Fixed. See e78b9e2ba860f886b65396acde6a7f958becb332.


Upstream Dynamo Backend to Torch

Add a hook in the Torch repo to secure the namespace "tensorrt" and have it point to "torch_tensorrt"
Add necessary imports and skipped tests
Raise a PR in Torch to add this functionality

See https://github.com/pytorch/pytorch/pull/104426


Are there plans of adding matrix params?

I'm looking to use router-store in my effects, but there doesn't appear to be any non convoluted way to route by matrix params. Kind of a deal breaker for me at the moment, is support for this planned?

Support for an array of commands will land with #12


add auto building

This is a bit different from the ninetails system.
What you first do, is create a tag that starts with v, like this from https://dev.to/erikhofer/build-and-publish-a-multi-platform-electron-app-on-github-3lnd where I got this system from:

Then, a draft PR should come up in your releases. Edit the description and stuff, then release it!

You won't make the release yourself, you just make the git tag from the cli/github desktop and push it. Then Electron Forge can handle all the rest, creating the release with binaries. Then you can edit the description and release it :smile:

Thanks!

Can you try it?

@webdev03
you cant make a tag without makin a release

You can.

Just run npm version minor or whatever npm version it automatically adds a tag too.

You have to create tags via github

and it does not let you

You can use https://user-images.githubusercontent.com/75148774/147155381-9476f789-b01e-47c8-8c1a-534733c9b46b.png

npm ERR! Git working directory not clean.
npm ERR!

Look, can I give you some steps

"npm version" shows the version of NPM

npm version 0.4.0 will work.

https://github.com/webdev03/ninetails/tree/v2.3.0 this tag was made with the CLI.

Hmm, that's weird

LMAO
i got it to work but ur GH action is a failure.
dont upload broken PRs.

I made a fix for it. For some reason, while I was typing, my editor broke it. So sorry!! :sob:


Map indexed access get operator to method invocation

While the Kotlin index access get operator is an operator, its syntax is more like a regular method invocation, with the difference that the method name (get) is implicit and that the arguments appear inside square brackets rather than regular parentheses. Also, under the hood, this will of course get mapped to a method invocation (which is also mostly true for Kotlin's other operators).
This commit changes the parsing to map the get operator to a J.MethodInvocation rather than a K.Binary and adds an IndexedAccess marker to it, so that it can get printed correctly again.
Fixes: #233

@traceyyoshima I felt pretty confident about this one, so I went ahead and merged it. We can always revert / fix later. I hope you are fine with that!


Bug: wavelets.center_frequency yields negative frequency with large mu and small scale

The following example returns wc = -3.1354 but according to the specs it should be nonnegative, unless I'm misunderstanding something.
from ssqueezepy import wavelets, Wavelet
wavelet = Wavelet(("morlet", {"mu":14.0}))
_ = wavelets.center_frequency(
    wavelet,
    scale=np.array([1.0]),
    kind='peak',
    N=1024,
    viz=1
)

Thanks for the report.
Current imlpementations of center_frequency, time_resolution, and freq_resolution are discretized approximations of underlying continuous-time parameters. This is a flawed approach (I didn't know better at the time), and I may improve it eventually to base on discrete logic.
The problem here specifically is that the wavelet isn't "well-behaved" at this scale - meaning, its lowest frequency goes either to left of FFT bin 1, or its highest frequency to right of Nyquist. The well-behaved range can be found as:
from ssqueezepy import Wavelet
from ssqueezepy.utils import cwt_scalebounds

wavelet = Wavelet(("morlet", {"mu":14.0}))
cwt_scalebounds(wavelet, N=1024, preset='maximal')
# (4.081687670534748, 4545.465174704532)

Granted it still shouldn't return a negative, so it's an unhandled edge case.


defining faces in the wrong direction can cause wrong ordering

it is possible to create 2 .fold files that are exactly equal except for the order of the arrays inside faces_vertices (meaning the only difference is whether the faces are defined clockwise or counter-clockwise), where one of them is displayed correctly in linefolder and the other is not.
In this zip file, there is an example of 2 such files, with the _rev file being the one that is displayed correctly.
foldedstates.zip
Both files are being displayed correctly on https://edemaine.github.io/fold/examples/foldviewer.html, which is why i assume the issue is not with the files

Yeah, that seems like a bug. The flat-folder code expects something stronger than the FOLD spec: that faceOrder face indices are increasing, i.e., [f, g, o] has f < g, so my guess is the code doing the conversion is incorrect.

The code handling faceOrder conversion was definitely wrong (it was multiplying a boolean and an integer which is not advisable to say the least). I believe this should be fixed now.


Build failure: vscode-langservers-extracted

Steps To Reproduce
Steps to reproduce the behavior:

build vscode-langservers-extracted-4.10.0

Build log
error: builder for '/nix/store/ywzzbc1z5ncfma0zczgbbss2xz8n0x5d-vscode-langservers-extracted-4.10.0.drv' failed with exit code 2;
       last 10 log lines:
       >   npx browserslist@latest --update-db
       >   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
       > [BABEL] Note: The code generator has deoptimised the styling of /nix/store/nxhv489xhhlm3bxql87y599x2mlf8wnf-vscodium-<IP_ADDRESS>83/lib/vscode/resources/app/extensions/html-language-features/server/dist/node/htmlServerMain.js as it exceeds the max of 500KB.
       > Successfully compiled 1 file with Babel (4116ms).
       > Browserslist: caniuse-lite is outdated. Please run:
       >   npx browserslist@latest --update-db
       >   Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
       > Successfully compiled 1 file with Babel (2287ms).
       > babel:
       >   /nix/store/nxhv489xhhlm3bxql87y599x2mlf8wnf-vscodium-<IP_ADDRESS>83/lib/vscode/resources/app/extensions/markdown-language-features/server/dist/node does not exist
       For full logs, run 'nix log /nix/store/ywzzbc1z5ncfma0zczgbbss2xz8n0x5d-vscode-langservers-extracted-4.10.0.drv'.
error: 1 dependencies of derivation '/nix/store/q9a0w8xcf2hnyycrnpwlpld6l9q9s35i-init.lua.drv' failed to build
error: 1 dependencies of derivation '/nix/store/lfcggrah128mp7bg97mi0dn8i5v8va9n-neovim-0.9.5.drv' failed to build
error: 1 dependencies of derivation '/nix/store/2g81ismj5721i51csxayg3sinq3islmx-system-path.drv' failed to build
error: 1 dependencies of derivation '/nix/store/7l6jp3d7lj51fw6v7hci4mkcwmjjmg5i-nixos-system-nixos-24.05.20241012.a3f9ad6.drv' failed to build

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
➜ nixos (master) ✗ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.2, NixOS, 24.05 (Uakari), 24.05.20241006.ecbc1ca`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - nixpkgs: `/nix/store/5cypwijbjdxmr4i7ckpq1in7f09547fc-source`

I turned off nixvim which was using the package for now using vim no plugins lol

I have also seen this.

Build Log
@nix { "action": "setPhase", "phase": "unpackPhase" }
Running phase: unpackPhase
unpacking source archive /nix/store/036vik9b785i8i45h9yrnljzarzwbds9-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
Running phase: patchPhase
Executing npmConfigHook
Configuring npm
Validating consistency between /build/source/package-lock.json and /nix/store/b6dybbi3057hbaldcl0p5zpxzrfsnnm1-vscode-langservers-extracted-4.10.0-npm-deps/package-lock.json
\\\Installing dependencies

added 629 packages, and audited 630 packages in 4s

55 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
patching script interpreter paths in node_modules
<EMAIL_ADDRESS>interpreter directive changed from "#!/bin/sh" to "/nix/store/516kai7nl5dxr792c0nzq0jp8m4zvxpi-bash-5.2p32/bin/sh"
node_modules/npm-run-all/node_modules/semver/bin/semver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/npm-run-all/node_modules/which/bin/which: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/npm-run-all/bin/npm-run-all/index.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/npm-run-all/bin/run-p/index.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/npm-run-all/bin/run-s/index.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/package-json/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/read-pkg/node_modules/semver/bin/semver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/@babel/cli/node_modules/semver/bin/semver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
<EMAIL_ADDRESS>interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/is-ci/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/is-docker/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/json5/lib/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/rc/cli.js: interpreter directive changed from "#! /usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/browserslist/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/rimraf/bin.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/which/bin/node-which: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/babel-plugin-polyfill-corejs2/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/he/bin/he: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/pidtree/bin/pidtree.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/open/xdg-open: interpreter directive changed from "#!/bin/sh" to "/nix/store/516kai7nl5dxr792c0nzq0jp8m4zvxpi-bash-5.2p32/bin/sh"
node_modules/regjsparser/node_modules/jsesc/bin/jsesc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/regjsparser/bin/parser: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/typescript/bin/tsc: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/typescript/bin/tsserver: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/vscode-languageserver/bin/installServerIntoExtension: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/make-dir/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/semver-diff/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/core-js-compat/node_modules/semver/bin/semver.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/import-local/fixtures/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/np/source/cli-implementation.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
node_modules/np/source/cli.js: interpreter directive changed from "#!/usr/bin/env node" to "/nix/store/k5inwzpp6a0295pd3nfckk9hq8wmifhz-nodejs-20.15.1/bin/node"
rebuilt dependencies successfully
patching script interpreter paths in node_modules
Finished npmConfigHook
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
Running phase: updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
Running phase: configurePhase
no configure script, doing nothing
@nix { "action": "setPhase", "phase": "buildPhase" }
Running phase: buildPhase
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
[BABEL] Note: The code generator has deoptimised the styling of /nix/store/nxhv489xhhlm3bxql87y599x2mlf8wnf-vscodium-<IP_ADDRESS>83/lib/vscode/resources/app/extensions/css-language-features/server/dist/node/cssServerMain.js as it exceeds the max of 500KB.
Successfully compiled 1 file with Babel (6525ms).
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
[BABEL] Note: The code generator has deoptimised the styling of /nix/store/nxhv489xhhlm3bxql87y599x2mlf8wnf-vscodium-<IP_ADDRESS>83/lib/vscode/resources/app/extensions/html-language-features/server/dist/node/htmlServerMain.js as it exceeds the max of 500KB.
Successfully compiled 1 file with Babel (8305ms).
Browserslist: caniuse-lite is outdated. Please run:
  npx browserslist@latest --update-db
  Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating
Successfully compiled 1 file with Babel (4944ms).
babel:
  /nix/store/nxhv489xhhlm3bxql87y599x2mlf8wnf-vscodium-<IP_ADDRESS>83/lib/vscode/resources/app/extensions/markdown-language-features/server/dist/node does not exist

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.2, NixOS, 24.05 (Uakari), 24.05.20241012.a3f9ad6`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - nixpkgs: `/nix/store/0283cbhm47kd3lr9zmc5fvdrx9qkav8s-source`

Looks like this build error will be addressed by #348035.

I turned off nixvim which was using the package for now using vim no plugins lol

if you set inputs.nixvim.inputs.nixpkgs.follows = "nixpkgs" in your flake, try disabling it temporarily.

Since the linked Merge Request was already merged, what can I do to fix the build on my local setup?
I already tried nix-channel --upgrade but it didn't change anything to the issue.

@tuxflo Try pulling the package vscode-langservers-extracted from nixpkgs-unstable. That seems to work for me.

Closing, #348035 was merged & the channel has advanced (tracker).


Unable to "Execute smart contract function (incurring gas cost)" with uint arguments

This issue is for a: (mark with an x)
- [x] bug report

Minimal steps to reproduce

Define a SmartContract with a function which takes two number (uint) arguments (see https://gist.github.com/StefH/97f306be11e906c5fce3aa3b99d79eb5)

Run the logic app an the "Execute smart contract function step" fails with 400.

And the error is:
{
  "status": 400,
  "message": "Encountered RPC error when establishing communicating with the blockchain network -32000: gas required exceeds allowance or always failing transaction\r\nclientRequestId: c7b85c9f-5480-44c2-80cd-47deaa8fd1e6",
  "source": "blockchainethereum-we.azconn-we.p.azurewebsites.net"
}

It seems that the two arguments provided, are passed as strings instead of numbers?

Expected/desired behavior
Able to call the function.

Sorry : I used wrong Contract Address...


Col-0 for Grid System

We need urgent this feature.
.col-xxl-0{
    display: none !important;
}

/* X-Small devices (portrait phones, less than 576px)*/
@media (max-width: 575.98px) {
    .col-0{
        display: none !important;
    }
}

/* Small devices (landscape phones, less than 768px)*/
@media (max-width: 767.98px) {
    .col-sm-0{
        display: none !important;
    }
}

/* Medium devices (tablets, less than 992px)*/
@media (max-width: 991.98px) {
    .col-md-0{
        display: none !important;
    }
}

/* Large devices (desktops, less than 1200px)*/
@media (max-width: 1199.98px) {
    .col-lg-0{
        display: none !important;
    }
}

/* X-Large devices (large desktops, less than 1400px)*/
@media (max-width: 1399.98px) {
    .col-xl-0{
        display: none !important;
    }
}

This would duplicate our .d-none utility (which is responsive) so I don't think we'll do that.
Any argument for this?

Agreed with @ffoodd, closing out.

I think this is useful, so you can use:
This:

insted of this:

I think it'w useful for the creation of a grid view.
See the difference:
Before:

After:

You're only switching our mobile-first utilities to desktop first, that's why you save a class in that case. It doesn't relate to your .col-0 suggestion.
This is not how we handle both utilities and grid, so it doesn't match our core principles.


Tools get broken with newer kernels

Since many of our tools rely on kprobes and kernel struct types, it may (and it does) happen that they stop working with newer kernels. I'd like to use this bug to settle on approaches that we can take to avoid/resolve such problems.
Existing problems:

#1896: mdflush.bt stops working due to struct bio change
#1895: tcpdrop.bt stops working due to GCC change (kprobe is inlined)
#2127: bio*.bt tools stop working due to renamed kprobes and a struct moved to a different header

We'll need a number of approaches to resolve the individual problems. So far, I can think of these:

If a kprobe is removed, it is usually possible to find a different one to attach to. We can solve this in a script by attaching to all potential kprobes which will display a warning but it'll work. We might want to add an option to ignore non-existing kprobe warnings and use that in scripts to improve user experience.
Move of a struct to a different header could be solved by relying on BTF rather than on header includes. This is proposed by #1823.
Change in a struct type is more difficult to resolve. We could add a way to somehow check if a field exists in a struct (using BTF).

Thoughts? Any more ideas of what can break and how to approach it?

I'd suggest taking the same approach as BCC does: if it's not simple to support multiple kernel versions in a single script, then we just keep the most recent one in tools/ and provide scripts for old kernels in tools/old/.
@fbs @danobi @brendangregg any thoughts on this?

Multiple versions of the same script seems like the only sane way to me. If it's easy to support multiple kernels in the same script, that's great and we should do that. If there's enough skew, we can copy paste the script and add a comment in the old script saying something like "works on kernel A.BB - C.DD".

Maybe we can use the LINUX_VERSION_CODE macro? Something like
#include <linux/version.h>

BEGIN {
#if (LINUX_VERSION_CODE < KERNEL_VERSION(5,0,0))
  printf("bar\n");
#else
  printf("baz\n");
#endif
}

... though it does not work now:
a.bt:4:1-49: ERROR: syntax error, unexpected preprocessor directive, expecting }
#if (LINUX_VERSION_CODE < KERNEL_VERSION(5,0,0))
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Personally I'm not that happy with all the preprocessor tricks. I see the preprocessor more of an implementation detail. Its there to import header files so we can use those types. We just don't have a way to 'restrict' it so you can 'use' it for these purposes too.
With the move to BTF on the kernel side and us adding DWARF support for uprobes we can probably drop clang and the stuff that comes with it for a lighter build. Header parsing can be quite slow too, you never know what header is imported by the header you need, the network tools we have suffer from it.
Conditional compilation is also not without issues as you basically have multiple different bits of the same code which do (not) get compiled based on some conditions. So making sure every path is syntactically valid etc is hard.
But I do not have  a better solution than just multiple version either.

Maybe we can use the LINUX_VERSION_CODE macro? Something like

Unfortunately that does not work for backported kernels. The version number can be a big lie when features/code is backported to an older version kernel.


Finalized core XSD should be uploaded to the public website in the conventional location

Prior to going GA we should make sure that ehcache-core.xsd file is uploaded to the conventional location on the website relative to it's XML namespace.  Someone with more XML knowledge than me can probably determine exactly what behavior/location that is.

The class-level javadoc in org.ehcache.xml.XmlConfiguration needs to be updated to include a reference to the schema location.

Propose to inspire ourselves from what's done in Spring:

Main XSD

Schema namespace: http://www.ehcache.org/v3
Schema location: http://www.ehcache.org/schema/ehcache-core-3.0.xsd

XA xsd

Schema namespace: http://www.ehcache.org/v3/tx
Schema location: http://www.ehcache.org/schema/ehcache-tx-ext-3.0.xsd

javax.cache xsd

Schema namespace: http://www.ehcache.org/v3/jsr107
Schema location: http://www.ehcache.org/schema/ehcache-107ext-3.0.xsd

with each namespace having a basic landing page that lists the relevant XSD files.

After discussion with @jhouserizer agreed to use xml as the folder name for schema files, to align with Quartz

PR ehcache/ehcache.org-site#30 has been merged


Could you please help me add the retweeter api?

I added the following codes for the retweeter API.
After I used the retweeter API once with account's cookie, Twitter lock my account.
Could you please help me add the retweeter api and tell me the reason?

func (s *Scraper) RetweetsUsers(tweetId string, maxTweetsNbr int, cursor string) ([]*Profile, string, error) {
if maxTweetsNbr > 200 {
	maxTweetsNbr = 200
}

req, err := s.newRequest("Get", "https://twitter.com/i/api/graphql/_D6CD5GX3VTL4ZzoAjJjGA/Retweeters")

if err != nil {
	return nil, "", err
}

req.Header.Set("content-type", "application/json")

variables := map[string]interface{}{
	"tweetId":                tweetId,
	"count":                  maxTweetsNbr,
	"includePromotedContent": false,
}

features := map[string]interface{}{
	"rweb_tipjar_consumption_enabled":                                         true,
	"responsive_web_graphql_exclude_directive_enabled":                        true,
	"verified_phone_label_enabled":                                            false,
	"creator_subscriptions_tweet_preview_api_enabled":                         true,
	"responsive_web_graphql_timeline_navigation_enabled":                      true,
	"responsive_web_graphql_skip_user_profile_image_extensions_enabled":       false,
	"communities_web_enable_tweet_community_results_fetch":                    true,
	"c9s_tweet_anatomy_moderator_badge_enabled":                               true,
	"articles_preview_enabled":                                                true,
	"tweetypie_unmention_optimization_enabled":                                true,
	"responsive_web_edit_tweet_api_enabled":                                   true,
	"graphql_is_translatable_rweb_tweet_is_translatable_enabled":              true,
	"view_counts_everywhere_api_enabled":                                      true,
	"longform_notetweets_consumption_enabled":                                 true,
	"responsive_web_twitter_article_tweet_consumption_enabled":                true,
	"tweet_awards_web_tipping_enabled":                                        false,
	"creator_subscriptions_quote_tweet_preview_enabled":                       false,
	"freedom_of_speech_not_reach_fetch_enabled":                               true,
	"standardized_nudges_misinfo":                                             true,
	"tweet_with_visibility_results_prefer_gql_limited_actions_policy_enabled": true,
	"rweb_video_timestamps_enabled":                                           true,
	"longform_notetweets_rich_text_read_enabled":                              true,
	"longform_notetweets_inline_media_enabled":                                true,
	"responsive_web_enhance_cards_enabled":                                    false,
}

if cursor != "" {
	variables["cursor"] = cursor
}

query := url.Values{}
query.Set("variables", mapToJSONString(variables))
query.Set("features", mapToJSONString(features))
req.URL.RawQuery = query.Encode()

var timeline RetweetTimeLine

err = s.RequestAPI(req, &timeline)
if err != nil {
	return nil, "", err
}

users, nextCursor := timeline.parseUsers()

if strings.HasPrefix(nextCursor, "0|") {
	nextCursor = ""
}

fmt.Println("retweet task", "len(users)", len(users), "nextCursor", nextCursor)

return users, nextCursor, nil

}

I guess the problem is 	"includePromotedContent": false,
but I do not have a account to verify.

I have been managing 20 accounts per IP address without receiving a ban for several months.
How many API do you use?

hi @wade-liwei! added GetTweetRetweeters method.
how often you did requests? make sure you set at least 5 seconds between requests scraper.WithDelay(5)
my telegram bot still using the same 20 accounts for average ~3800-4000 requests per hour (wich is 50 request per 15 min per account). it's a year now without any account banned.

Thank you so much.
But my boss ask me to use the twitter API(the paied API).
So I have to give up your solution again. (we need to request many API interfaces, not only one)
Anyway, thank you.

Thank you so much.
But my boss ask me to use the twitter API(the paied API).
So I have to give up your solution again. (we need to request many API interfaces, not only one)
Anyway, thank you.


Update IoT team member list

@jsquire I can't merge this. IIRC some changes (like those that don't touch an SDK) don't trigger any gates and therefore can't be merged by mere mortals such as myself. Can you help merge this one?

/check-enforcer override


Typo

For instance, if your domain is named aadds.contoso.com, the certificate's subject name must be *aadds.contoso.com
Should be, "*.aadds.contoso.com" the period is missing

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

ID: 325a9114-36b2-a6b3-d0a4-19c522b7abf0
Version Independent ID: cbd84d9f-fbfd-d97d-9826-26947f64d18a
Content: Tutorial - Configure LDAPS for Azure Active Directory Domain Services
Content Source: articles/active-directory-domain-services/tutorial-configure-ldaps.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@jonwbstr Thanks for the feedback! We are currently investigating and will update you shortly.


Fix zlib vulnerability CVE-2022-37434

Context
Changes proposed in this pull request
Guidance to review
Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 Snyk Failure on Publish, Register


Add TEST_ARGS variable and fail fast E2E on CI

Add the variable to allow passing any arbitrary arguments to the E2E tests, and set to fail fast by default on the CI.
This will save time on CI in case of test failures, and could be disabled when necessary.
On local invocations, the default behavior will remain running all tests, but the flag can be passed explicitly if desired.
Resolves https://github.com/submariner-io/enhancements/issues/45
Signed-off-by: Mike Kolesnik<EMAIL_ADDRESS>

I guess it just proved itself :)
https://github.com/submariner-io/shipyard/actions/runs/3739671285/jobs/6347156836

This was backported to 0.,14 as #1085
Backporting to 0.13 has too many conflicts and will not be performed


[OpenCLML] CLML Profiling fixes corresponding to OpenCL Timer recent …

Dynamic creation of command queue (#11180) breaks OpenCLML profiling as OpenCLML stores ref. for command queue and reuse later.
Now, we access the command queue from work space always rather storing internally.
Thanks for contributing to TVM!   Please refer to guideline https://tvm.apache.org/docs/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.

cc @echuraev

@masahi can you take a look and merge it ?


Add DB Index

Current Implementation
Flyway PostGreSQL script
Suggested Enhancement
Under the db/migration/postgres folder add a SQL script, using the CREATE INDEX command, to create a DB Index.
Expected Benefits
Indexes are primarily used to enhance database performance

@AndresFelipeRG Is this a duplicate of #191?


Move error test for recognized but unsupported function to intepreter list

The txt-based tests are run in both the Power Fx repository and in Power Apps for compatibility checks. A new test was recently added that checks for an error in the C# interpreter for a function that doesn't exist in that interpreter, but is defined in Power Apps - so it will fail on that host. This change moves this test to the interpreter-only list.

✅ No public API change.

✅ No public API change.


Add support for k range frames in Window operator

k Range frameshttps://github.com/facebookincubator/velox/pull/7669 explains the functionality.
Note : Will have a follow up PR for tests with null range values.

@mbasmanova : Have revised the k range frames logic to always do a top-down search as previously discussed. PTAL.

@aditi-pandit Aditi, thank you for working on this. Overall looks good. Do we need to update some docs? I'm having a hard time reading the tests. Can you explain what is being tested and how? Any known gaps in testing?

@mbasmanova : I looked at documentation more closely and realized that window frame processing is not explained at all in WindowNode in operators.rst. There is no explanation for IGNORE NULLs as well. But on second thoughts I feel that all this is better suited for a blog post that we can link from here. wdyt ? This topic seems complex enough for a blog post imo.
About the tests : k Range frames in Presto require the planner to compute a range column (current order by value +/- k range variations based on preceding/following and asc/desc) and that is specified in the WindowNode spec for Velox. But for DuckDB we can simply state the original k range clause without having to compute this additional column. So the tests basically construct the k-range columns with different variations of preceding/following with asc/desc.
I need to add mroe tests with NULL values. However, there were too many variations for that with the current tests and DuckDB semantics as well. So I will have subsequent PRs for them.

@mbasmanova : Have addressed the review comments and tests. PTAL.

@aditi-pandit

I looked at documentation more closely and realized that window frame processing is not explained at all in WindowNode in operators.rst. There is no explanation for IGNORE NULLs as well. But on second thoughts I feel that all this is better suited for a blog post that we can link from here. wdyt ? This topic seems complex enough for a blog post imo.

Blog post would be nice but it is not a replacement for documentation. We need documentation first.

@aditi-pandit

I need to add mroe tests with NULL values. However, there were too many variations for that with the current tests and DuckDB semantics as well.

I suggest to invest into adding Fuzzer coverage for window functions and using Presto as source of truth.

@aditi-pandit

I need to add mroe tests with NULL values. However, there were too many variations for that with the current tests and DuckDB semantics as well.

I suggest to invest into adding Fuzzer coverage for window functions and using Presto as source of truth.

@mbasmanova : Fuzzer coverage is an independent effort I feel. The testing approach definitely benefits window functions.
At this point, as this is the last piece of the feature left, it would be good to add the hard-coded testing with result vectors skipping DuckDB.

@aditi-pandit

I looked at documentation more closely and realized that window frame processing is not explained at all in WindowNode in operators.rst. There is no explanation for IGNORE NULLs as well. But on second thoughts I feel that all this is better suited for a blog post that we can link from here. wdyt ? This topic seems complex enough for a blog post imo.

Blog post would be nice but it is not a replacement for documentation. We need documentation first.

@mbasmanova : I will send out a separate PR that enhances documentation for frames. There are multiple gaps that need to be covered.

@aditi-pandit

I looked at documentation more closely and realized that window frame processing is not explained at all in WindowNode in operators.rst. There is no explanation for IGNORE NULLs as well. But on second thoughts I feel that all this is better suited for a blog post that we can link from here. wdyt ? This topic seems complex enough for a blog post imo.

Blog post would be nice but it is not a replacement for documentation. We need documentation first.

@mbasmanova : The documentation PRs are ready Window frames with empty frameshttps://github.com/facebookincubator/velox/pull/7650 and k Range frameshttps://github.com/facebookincubator/velox/pull/7669. PTAL.

@aditi-pandit

I looked at documentation more closely and realized that window frame processing is not explained at all in WindowNode in operators.rst. There is no explanation for IGNORE NULLs as well. But on second thoughts I feel that all this is better suited for a blog post that we can link from here. wdyt ? This topic seems complex enough for a blog post imo.

Blog post would be nice but it is not a replacement for documentation. We need documentation first.

@mbasmanova : I will send out a separate PRs that enhances documentation for frames. There are multiple gaps (like empty frames etc) that need to be covered.
Window frames with empty frameshttps://github.com/facebookincubator/velox/pull/7650 and k Range frameshttps://github.com/facebookincubator/velox/pull/7669.

@aditi-pandit

Will condense it in a commit message post review.

Perhaps, it is time to address this.

The feature is explained in the documentation now.

@aditi-pandit, could you do a code rebase and resolve the code conflict?

@aditi-pandit, could you do a code rebase and resolve the code conflict?

Done. Thanks @PHILO-HE.

Hi @mbasmanova, can this PR be merged? I will do some follow-up work for SparkSQL based on this PR. Thanks!

@mbasmanova : I have refactored the tests and added documentation. PTAL.

Got a linter warning:

Also,

Got a linter warning:

Updated

Also,

Updated

Thanks @mbasmanova for the review. Have addressed the comments and fixed the linter warnings.


Fix some outstanding flake8 issues

... So that I can use my git push flake8 hook!

Codecov Report

Merging #1207 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1207   +/-   ##
=======================================
  Coverage   96.93%   96.93%
=======================================
  Files          49       49
  Lines        2282     2282
=======================================
  Hits         2212     2212
  Misses         70       70

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 631a435...57d7a3d. Read the comment docs.


Battery levels are not displayed

The battery level of any Xioami device is not detected. Neither in version 0.7.13 nor in version 0.7.14, why is that?

the sensors that I understand that the battery should be marked for me are:
lumi.sensor_ht.v1 (temperature and humidity sensor)
lumi.sensor_magnet.v2 (door and window sensor)
lumi.sensor_motion.v2 (motion sensor)
lumi.sensor_wleak.aq1 (Flood Sensor)
Does anyone have any idea why they don't show battery?

Does no one else have this same problem, is it just me?

On my side I can see the battery displayed but information is useless as it's always 100%

Only my Zigbee switch seems to display proper information of battey

I have changed integration to connect my HA to my xioami computers in local network. I have left hass-xiaomi-miot for the non-zigbee devices, but I have connected the zigbee devices with the native integration and it seems to work much better.


Facet search is case-sensitive

Describe the bug
In DSpace 7.x, when you use the search box to find facets, if you hit enter (rather than selecting one of the facets offered), the case of the term you entered affects your results.
To Reproduce
Steps to reproduce the behavior:

Conduct a broad search to find facetable results.
Choose a text-based facet (e.g. subject or type, not issue date).
Enter a term in the facet's search box. Make sure it matches a valid facet term (from the type-ahead options), but use lower-case. A current good example in the demo7 sandbox is "fiction" as a subject or "journal" as an item type.
Do not select one of the type-ahead options presented, but instead hit enter.

Expected behavior
You should see the same results as if you selected a matching facet value. Instead, the labels at the top of your search results and in the facet box present a capitalized facet value, but you get only results where the metadata was entered in lower-case (typically none)
See screenshots...
filter-subject-lower-case:

filter-subject-lower-case-results:

filter-subject-upper-case:

filter-subject-upper-case-results:

Definitely seems like a bug.  Pulling this over onto our 7.6 maintenance board in the hopes that it's something small & easy to fix.  If analysis proves it's a more complex fix, then this might need to move to 8.0
In any case, needs a volunteer.


Pretrained for ViT-S/14 or ViT-S/16

Thank you for your excellent works!
I want to implement this pretrained on my research with limited resource machine. Could you release pretrained weights for ViT-S/14 or ViT-S/16?
My email<EMAIL_ADDRESS>

Also hope that we can use Vit-S version as soon as possible

Coming soon!

Coming soon!

Is there any update with ViT-S yet?

I'm also waiting for the new models🤔

Hi. Any updates?


Links with Multiple Visual Elements with Different Colors Don't Render Correctly

Using RViz 1.12.15, if a link has multiple visual elements, the first visual element renders with the specified material color.  The remaining  visual elements render as black.  The model I used was processed with Xacro but I examined the generated URDF and the materials were specified correctly for the link.

@TimCraig could you provide a reproducible example? That will help this be investigated, thanks!

Here's a simple file with two links and one joint.  The base_link has 3 visuals each consisting of a cylinder 1 meter tall and half a meter in diameter spaced along the x-axis.  They should be red, green, and blue.  The green one in the middle displays properly while the other two show up in RViz as black.  I've included a screenshot.   Running ROS Kinetic on Ubuntu Mate 16.04 in a VirtualBox on Windows 10.
color_problem.zip

thanks for the example, we will test it out when we get a chance

This was fixed in #1079 and released into 1.12.5


Tags are not converging idempotently

They keep re-creating existing tags

@tyler-ball hmm.  Do the tag specs fail too?

I just ran the specs and they are passing. Could you provide a bit more detail so I can take a look? Thanks!

I was running a local cookbook to see these errors - I've got a PR incoming with an updated ref_full.rb which includes tags on everything.


Python free programming course en - Scrimba

What does this PR do?
Add resource(s)
For resources
Description
Adding Python free Course
Why is this valuable (or not)?
Free python course provided interactively
How do we know it's really free?
It is on a public website that allows everyone to access this course
For book lists, is it a book? For course lists, is it a course? etc.
It's a course
Checklist:

[X] Read our contributing guidelines.
[X] Search for duplicates.
[X] Include author(s) and platform where appropriate.
[X] Put lists in alphabetical order, correct spacing.
[X] Add needed indications (PDF, access notes, under construction).
[X] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


bcsandbox docker container with AAD auth

I created a new container (using navcontainerhelper <IP_ADDRESS>) and set it up with AAD auth. I am using the latest microsoft/bcsandbox:us as the image. I then use the Create-AadAppsForNav commandlet to create the app.
When I try to sign on, I get authenticated properly to the AD and it goes back to the sign in page for BC and then I receive "An error has occurred". Nothing else. In the event log, I see the following
Error accessing Website
Type: System.InvalidOperationException
Message: Incorrect Content-Type:
StackTrace:
at Microsoft.AspNetCore.Http.Features.FormFeature.ReadForm()
at Microsoft.Dynamics.Nav.WebClient.Controllers.AuthenticationController.d__6.MoveNext() in s:\repo\src\platform\client\web\Prod.Client.WebCoreApp\Controllers\AuthenticationController.cs:line 0
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.TaskOfIActionResultExecutor.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.d__24.MoveNext()
Source: Microsoft.AspNetCore.Http
Any guidance as to what is missing or what is happening?
thank you
Peter

Did you reconfigure Service Tier and Web Client with the information returned from Create-AadApps...?

I have double and triple checked the configuration and I do think that I have updated everything.

The code I use in the ARM templates is here: https://github.com/Microsoft/nav-arm-templates/blob/master/SetupNavContainer.ps1
Look at these lines:
        $AdProperties = Create-AadAppsForNav -AadAdminCredential $Office365Credential -appIdUri $publicWebBaseUrl -IncludeExcelAadApp -IncludePowerBiAadApp
        $auth = "AAD"
'Write-Host "Changing Server config to NavUserPassword to enable basic web services"
Set-NAVServerConfiguration -ServerInstance nav -KeyName "ClientServicesCredentialType" -KeyValue "NavUserPassword" -WarningAction Ignore
Set-NAVServerConfiguration -ServerInstance nav -KeyName "ExcelAddInAzureActiveDirectoryClientId" -KeyValue "'+$AdProperties.ExcelAdAppId+'" -WarningAction Ignore
Set-NAVServerConfiguration -ServerInstance nav -KeyName "ValidAudiences" -KeyValue "'+$AdProperties.SsoAdAppId+'" -WarningAction Ignore -ErrorAction Ignore
' | Add-Content "c:\myfolder\SetupConfiguration.ps1"

Which basically sets up the aad apps and adds a setupconfiguration with the right parameters to the script overrides.
/Freddy

Thank you Freddy. By removing the container and redoing everything again and then doing only the setups that you did (I believe it was the valid audience that was missing, but still didn't work) it started working in the new container.
I'll close this then, since it was user error I think.


feat(v2): Extract/translate hardcoded labels from classic theme

Motivation
We want some theme hardcoded labels to be translated:

"edit this page"
pagination (next/previous, new post/old post...)
code block copy/copied
read more
...

This is not yet an exhaustive list, some labels remain to be translated but are more complicated to handle:

labels  with interleaved variables like "{time} min read time" or "last updated by {author} on {date}"...
date formatting
tags (we'll translate these when we have tags on docs and we have factorized a bit the theme code => less future i18n breaking changes)
... probably others
we probably want to translate all hardcoded aria labels as well

Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
tests + preview + i18n dogfooding

Can we provide something like a language pack with messages already translated out-of-box (French/Russian for now)?

@lex111 I'd like to but don't really have an idea on how to do that yet 😅 if you have an idea let me know.
Maybe the themes could have some kind of default translation packs or something? would probably require a new lifecycle api

I was thinking just in the classic theme directory to add an i18n folder with code.json files for each supported locale, or is that a bad option? And if the user hasn't provided their translation of the message - we use the default localization from classic theme. We need to add "support for the code.json file" to themes, I suppose.


Question: Will asynchronous threads be changed to synchronous execution?

python3 -m nuitka --version:
1.8.6
Commercial: None
Python: 3.8.10 (default, May 26 2023, 14:05:08)
Flavor: Debian Python
Executable: /home/.venv/protest/bin/python3
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 20.04.6
Version C compiler: /usr/bin/gcc (gcc).

I use code similar to the following in flask:
def async_thread(f):

    @wraps(f)
    def wrapper(*args, **kwargs):
        t = Thread(target=f, args=args, kwargs=kwargs)
        t.start()

    return wrapper

I  want to change the synchronous method to asynchronous execution through the decorator.
However, after compiling with nuitka, when I ran it, I found that the asynchronous mode had been changed back to synchronization.
python3 -m nuitka --show-progress --quiet --disable-ccache --module app --include-package=app --nofollow-imports --remove-output --no-pyi-file --clang

Does nuitka not support using asynchronous threads in this way? Or are there any special parameter options that I missed?
At the same time, I found that flask_mail could not send emails in the compiled execution program. What was the reason for this?

It seems you first and foremost missed that reports need a minimal reproducer, not just a code sample.

It seems you first and foremost missed that reports need a minimal reproducer, not just a code sample.

Ok. Here is a simple example:

import os
import time
from functools import wraps
from threading import Thread

from flask import Flask
from flask_mail import Mail, Message
from flask_restx import Resource, Api
from dotenv import load_dotenv

load_dotenv(".env", override=False)

class Config:
    MAIL_SERVER = os.environ.get("MAIL_SERVER")
    MAIL_PORT = os.environ.get("MAIL_PORT")
    MAIL_USE_TLS = os.environ.get("MAIL_USE_TLS")
    MAIL_USERNAME = os.environ.get("MAIL_USERNAME")
    MAIL_PASSWORD = os.environ.get("MAIL_PASSWORD")
    MAIL_DEFAULT_SENDER = os.environ.get("MAIL_DEFAULT_SENDER")

app = Flask(__name__)
app.config.from_object(Config)
mail = Mail(app)
api = Api(
    app,
    doc='/doc',
    version='0.0.1',
    titles="Flask Test Demo",
)

def async_thread(f):
    @wraps(f)
    def wrapper(*args, **kwargs):
        t = Thread(target=f, args=args, kwargs=kwargs)
        t.start()

    return wrapper

@async_thread
def do_something():
    print("To do...")
    time.sleep(10)
    print("Done.")

@async_thread
def send_simple(to_email):
    print("Start to send email...")
    with app.app_context():
        msg = Message(
            "Hello",
            sender=app.config["MAIL_DEFAULT_SENDER"],
            recipients=[to_email]
        )
        msg.body = "testing"
        msg.html = "<b>testing</b>"
        mail.send(msg)
    print("Send over.")

@api.route('/hello')
class HelloWorld(Resource):
    def get(self):
        # something to do
        do_something()
        return {'hello': 'world'}

@api.route('/email/<string:email>')
class SendSimple(Resource):
    def post(self, email):
        send_simple(email)
        return {"result": f"email has been sent to {email}"}

if __name__ == '__main__':
    app.run(debug=True, port=5000)

The dependency packages are as follows:
Flask==2.3.2
flask-restx==1.1.0
Flask-Mail==0.9.1
python-dotenv==0.14.0
nuitka==1.8.6

Nuitka used as follows:
python3 -m nuitka --show-progress --quiet --disable-ccache --module app.py --nofollow-imports --remove-output --no-pyi-file --clang

he app runs as follows:
uwsgi --http :9090 --thunder-lock --module app:app

Go to http://<IP_ADDRESS>:9090/doc for testing.
After doing the above, I found problems with asynchronous threads and sending emails.

Which way of finding problems will make the problem visible?

Which way of finding problems will make the problem visible?

When I tested these two interfaces, I found that the thread seemed to be suspended.
The thread did not exit after 10 seconds, and the previous one would not end until the second same request.
The interface for sending mail does not actually perform sending.
I describe it this way, is it acceptable?

I am having a hard time to get data files to work here. I kind of have high doubts that you know what you were doing, since you must have copied files manually, and who knows how well. I am adding these, but flask_restx is having strange ideas about where it wants to find them it seems, not the typical package or I am being dumb.

I have updated factory, but I never came close to observing what you claim, which is also very likely wrong anyway. I believe you were jumping to conclusions. I added the data files and both APIs seem to work fine in quick succession, which is I guess sufficient evidence of threads being used. Not sending email properly is possible, but in pure Python your program was giving a bunch of errors, to me, so I will just ignore it now.

I will track this issue until 1.9 release which should be soon, and then likely delete it, since it seems very invalid in all claims made.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

I have updated factory, but I never came close to observing what you claim, which is also very likely wrong anyway. I believe you were jumping to conclusions. I added the data files and both APIs seem to work fine in quick succession, which is I guess sufficient evidence of threads being used. Not sending email properly is possible, but in pure Python your program was giving a bunch of errors, to me, so I will just ignore it now.

Maybe you should check the information printed on the console after calling the two APIs, and you may have new insights.
As for getting a bunch of errors in pure python? I did not find that the python version in my environment is 3.8.10.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

Thank you for your reply, but I tried it, and the final performance of the factory branch does not seem to have changed. Of course, my previous conclusion may not be so accurate, it is just a guess. The title is indeed inappropriate, but the problem does exist. Pass It can be seen from the console output that 'Done' is not printed after 10 seconds. There is indeed a problem with the performance of the asynchronous thread. This is actually the main problem at present.
Thanks again for your quick reply, I'll try other solutions as well.

keep in mind your thread is a not actually asynchronous, it's still synchronous but it's added to a thread, that being said, i work a lot with concurrent proxified requests, threaded and actual asynchronous requests, i have never observed nuitka change the behavior of how they're executed, i'm with kay on this, this isn't something that's happening on the nuitka side.

keep in mind your thread is a not actually asynchronous, it's still synchronous but it's added to a thread, that being said, i work a lot with concurrent proxified requests, threaded and actual asynchronous requests, i have never observed nuitka change the behavior of how they're executed, i'm with kay on this, this isn't something that's happening on the nuitka side.

That's right. It's not really asynchronous, it's just formal. But before and after compilation, judging from the execution results, there seems to be a problem with the newly opened thread after compilation, and this is exactly the problem that needs to be solved.

can you make an MRE that doesn't involve any of the flask overhead?

I honestly cannot play around with a web GUI to find potential issues. It was interesting to learn of flask_restx it's pretty neat, I have used postman before I think, years ago as an external solution. But anything that involves me guessing what the expected outcome is clearly is a nogo. I didn't have errors in my console output that did not already appear with Python. I think it hates mail not being setup.
This adds to this not being minimal, since it obviously depends on your setup. I am not here to debug that. And your claimed issue, I feel like I may have heard of it before if true.

keep in mind your thread is a not actually asynchronous, it's still synchronous but it's added to a thread, that being said, i work a lot with concurrent proxified requests, threaded and actual asynchronous requests, i have never observed nuitka change the behavior of how they're executed, i'm with kay on this, this isn't something that's happening on the nuitka side.

That's right. It's not really asynchronous, it's just formal. But before and after compilation, judging from the execution results, there seems to be a problem with the newly opened thread after compilation, and this is exactly the problem that needs to be solved.

can you make an MRE that doesn't involve any of the flask overhead?

I plan to use nuitka to compile the flask application. Therefore, I cannot bypass flask.
However, I tested and found that if it is compiled into an executable binary file alone, there does not seem to be this problem. I am trying to combine it with click.
As for the problems with module compilation, I will find time to remove flask and test it separately.

The data file things are part of the 1.9 release I just made.


[mongo] Handle error when getting replica set metrics on mongos

What does this PR do?
Adds additional error handling with collecting replica set metrics to avoid an exception when collecting metrics from mongos, which is expected not have access to the replSetGetStatus command
Motivation
Customer using mongos reached out when an exception was thrown in the check during the collection of replica set metrics
Testing Guidelines
An overview on testing
is available in our contribution guidelines.
Versioning

[x] Bumped the check version in manifest.json
[x] Bumped the check version in datadog_checks/{integration}/__init__.py
[x] Updated CHANGELOG.md. Please use Unreleased as the date in the title
for the new section.
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
This partially reverts a change that was necessary when the pymongo dependency was bumped to 3.5

Hi guys,
what's the status of this PR? I am facing the issue that I can not monitor a mongo instance without replicas.
I get the following error instance #2 [ERROR]: 'replSetGetStatus is not supported through mongos' and I think this PR would fix it and let the other checks pass.
Looking forward

@dixonscottr @ofek thanks for merging it so quickly. Can you tell me, how I can get the latest version of the integrations? Does a new version of dd-agent has to be published? I am using dd-agent in kubernetes... Thanks!


captha

Unhandled exception in thread started by <function check_errors..wrapper at 0x7fafe24db730>
Traceback (most recent call last):
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/utils/autoreload.py", line 225, in wrapper
fn(*args, **kwargs)
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/core/management/commands/runserver.py", line 113, in inner_run
autoreload.raise_last_exception()
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/utils/autoreload.py", line 248, in raise_last_exception
raise _exception[1]
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/core/management/init.py", line 327, in execute
autoreload.check_errors(django.setup)()
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/utils/autoreload.py", line 225, in wrapper
fn(*args, **kwargs)
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/apps/registry.py", line 89, in populate
app_config = AppConfig.create(entry)
File "/home/normsoftware/project/sampath/lib/python3.5/site-packages/django/apps/config.py", line 90, in create
module = import_module(entry)
File "/home/normsoftware/project/sampath/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 956, in _find_and_load_unlocked
ImportError: No module named 'captcha'

Yes I got the same problem, can anyone fix it? I'm a physics teacher and beginner in programming, gonna use this to make website at my school.  Thanks!

Hi @Sebastian-Rydzewski, would it be possible if you could attempt to remove the captcha from the Django application? I currently am unable to fix this issue and don't see myself fixing this issue until next month.

Hey @bartmika, unfortunately I have my own projects tying down my free time, if I get a chance to take a look at it before you do I'll let you know.  I just can't at this time.

Hi @gdsuta, I've submitted latest code which uses more recent libraries. Can you try installing and see if it fixes the problem? Please make sure you run under the following:

Python 3.6
Postgres 10
Latest PIP
Latest VirtualEnv

In addition I wrote the following devops articles on how to set it up for DigitalOcean.

https://github.com/AcademicsToday/academicstoday-django/wiki/1-Setup-Project-on-DigitalOcean-CentOS-7

https://github.com/AcademicsToday/academicstoday-django/wiki/2-CentOS-7-additional-improvements

https://github.com/AcademicsToday/academicstoday-django/wiki/3-CentOS-7-Backup-and-restore-proceedure

Let me know if it helps!


Deploy your first container app using the ARM template

Page showing how to deploy Container Apps using arm template

Hi @aryll - Thank you for your contribution. The content team will review your pull request.

@craigshoemaker Is this an area you work with? Could you take a look or let me know who covers container apps? Thanks.

@craigshoemaker  @ktoliver any update on that one?

Hi, @aryll! Thanks so much for your contribution to the docs. I am going to #please-close this PR as the we're working on our content strategy for the quickstarts and we're headed in a different direction for this content.


[FEATURE] append appid= parameter to .well-known configuration url (t…

fixes #151

Hello, thanks for the PR! @bernhardberger, do you think you could resolve the conflicts so we can get this merged and released? Thanks!

Hello, thanks for the PR! @bernhardberger, do you think you could resolve the conflicts so we can get this merged and released? Thanks!

It's just a minor conflict, I'll look into it later today


Updated UnsafeMutablePointer intializers

Fixes issue #7 - updated pointer initializer.

Note, I should point out I stumbled upon this within another dependency of Vapor. TurnstileCrypto's BCrypt has a few updates.  Looks like they you guys were already in touch :)
Might make sense for that project to instead use this repo as a dependency?

Thanks!


bootstrap fails on manjaro (arch linux based distro) and ubuntu

I am getting the following error message: undefined symbol: node_module_register*
atom-shell-starter$ script/bootstrap
Node: v0.12.0
npm: v2.7.1
Installing build modules...
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">=0.8","npm":"1"} (current: {"node":"0.12.0","npm":"2.7.1"})
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":">= 0.6.0 < 0.11.0"} (current: {"node":"0.12.0","npm":"2.7.1"})
child_process: customFds option is deprecated, use stdio instead.
npm WARN engine<EMAIL_ADDRESS>wanted: {"node":"0.8.x || 0.10.x"} (current: {"node":"0.12.0","npm":"2.7.1"})
child_process: customFds option is deprecated, use stdio instead.
child_process: customFds option is deprecated, use stdio instead.
Installing apm...
child_process: customFds option is deprecated, use stdio instead.
child_process: customFds option is deprecated, use stdio instead.
child_process: customFds option is deprecated, use stdio instead.

module.js:356
  Module._extensions[extension](this, filename);
                               ^
Error: /home/albertmatyi/work/tmp/atom-shell-starter/apm/node_modules/atom-package-manager/node_modules/git-utils/build/Release/git.node: undefined symbol: node_module_register
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/albertmatyi/work/tmp/atom-shell-starter/apm/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:8:16)
    at Object.<anonymous> (/home/albertmatyi/work/tmp/atom-shell-starter/apm/node_modules/atom-package-manager/node_modules/git-utils/lib/git.js:359:4)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)

I've also tried

installing iojs-bin from AUR, and got other error messages, and was unable to build
sudo script/bootstrap giving the same error
using a vagrant machine (ubuntu 14.04 & node 0.10.37), but then the machine just simply crashed - several times - when I tried to use script/bootstrap. Without any suspicious errors in the console or syslog.
installing the official atom-shell release and starting the app with atom . but then it complained about invalid app (see output below)

atom-shell-starter$ atom .
[15377:0321/111323:ERROR:browser_main_loop.cc(170)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
Error opening app
The app provided is not a valid atom-shell app, please read the docs on how to write one:
https://github.com/atom/atom-shell/tree/master/docs

Question
Anyone had similar issues, or could point me in the right direction on how I could use this package?
Additional notes:

I've set python2.7 config option both locally and globally npm config set python python2.7 (-g)

This is because you're using node 0.12.x - install 0.10.x instead

Confirmed, installing v0.10.x resolves this.


fatal error

gettin this:

Warning: require(vendor/autoload.php): failed to open stream: No such file or directory in C:\Users\UTENTE-PC\get-started-php\index.php on line 22

Fatal error: require(): Failed opening required 'vendor/autoload.php' (include_path='.;C:\php\pear') in C:\Users\UTENTE-PC\get-started-php\index.php on line 22

I'm on windows 10, with php 7.4

Same issue

Hi,
I can´t try the get started app. I setup all. And get fatal error "Exit status 223" and "Error staging application: App staging failed in the buildpack compile phase"
I´m new in IBM Cloud. Php 8 installed with XAMPP in my PC. Can anyone help? Thanks.

Make sure you have executed the php composer.phar install command.


Build docker incrementally by default

This speeds up docker build time drastically. It still possible to disable this by setting DOCKER_INCREMENTAL_BUILD to 0 (and this is what should be done on the CI).
/cc @icecrime @tianon @cpuguy83 @aaronlehmann
This PR doesn't change anything for the CI, i.e. the CI still builds it using -a, a.k.a force rebuilding of packages that are already up-to-date..
🐸
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>

1 nit, but LGTM.

btw windows has unrelated failure:
16:32:47 ----------------------------------------------------------------------
16:32:47 FAIL: docker_cli_ps_test.go:309: DockerSuite.TestPsListContainersFilterAncestorImage
16:32:47
16:32:47 docker_cli_ps_test.go:380:
16:32:47     checkPsAncestorFilterOutput(c, out, filter.filterName, filter.expectedIDs)
16:32:47 docker_cli_ps_test.go:396:
16:32:47     c.Assert(actualIDs, checker.HasLen, len(expectedIDs), check.Commentf("Expected filtered container(s) for %s ancestor filter to be %v:%v, got %v:%v", filterName, len(expectedIDs), expectedIDs, len(actualIDs), actualIDs))
16:32:47 ... obtained []string = []string{}
16:32:47 ... n int = 1
16:32:47 ... Expected filtered container(s) for sha256:fe9ff0cb9b9dd5b636bbd0222c5d678abefc206d94e11da239dc1f2fb92bdf00
16:32:47 runtime: failed to create new OS thread (have ancestor filter to be 1:[d22a2c34a537175da06b3dddea65a85da4f27667edfe947390c59088a099a505], got 0:[]

ping @jhowardmsft

LGTM

:tada:


Support Today Widget?

I saw the discussion of #14 .
Now is it possible to take a snapshot on Today Widget?
I tried to test the below command:
instruments -w 'iPhone 6 (8.3 Simulator)' -D '/tmp/snapshot_traces/trace' -t 'Automation' /tmp/snapshot/build/TodayWidget.appx -e UIARESULTSPATH '/tmp/snapshot_traces' -e UIASCRIPT './snapshot_widget.js'

And the widget launches!
I haven't researched the source code in depth. Just let you know about this possibility.
What do you think?

Sorry, I don't know if it's possible to run UI Automation code on widgets.


onSubmitHook carries out own redirection

Hi,
I have the definition is as follows onSubmitHook: atSubmit.
var atSubmit = function (error, state) {
  console.log("at submit");

  if (!error) {
    if (state === "signUp") {
      FlowRouter.go('justRegistered');
    }
    if (state === "signIn") {
      checkEmailIsVerified();
      var redirect;

      redirect = Session.get('redirectAfterLogin');
      if (redirect !== null && typeof redirect !== 'undefined') {
        if (redirect !== '/login') {
          FlowRouter.go(redirect);
        }
      }
    }
  }
};

After debugging, I can see that the FlowRouter.go(redirect); gets called, but the AccountsTemplates.submitCallback = function(error, state, onSuccess) runs, and onSuccess is undefined.
From the documentation Guide snap below, I am deducing that once in the state check, am already logged in.
if (state === "signIn") {
      // Successfully logged in
      // ...
    }

Why does the onSuccess not actually get set and therefore another redirection gets carried out by AccountTemplates ?
Thank you

+1


Switch to test proxy

Why was this passing before?

With the legacy framework we would record the requests before they were actually sent over the wire, so we didn't get to see effects that HttpClient/HttpWebRequest would have on the request. With the Test Proxy, the recording happens after the request goes through the transport layer to the proxy.

Why was this passing before?

With the legacy framework we would record the requests before they were actually sent over the wire, so we didn't get to see effects that HttpClient/HttpWebRequest would have on the request. With the Test Proxy, the recording happens after the request goes through the transport layer to the proxy.

Does that imply an issue in our code that what goes over the wire is different based on the framework?

Why was this passing before?

With the legacy framework we would record the requests before they were actually sent over the wire, so we didn't get to see effects that HttpClient/HttpWebRequest would have on the request. With the Test Proxy, the recording happens after the request goes through the transport layer to the proxy.

Does that imply an issue in our code that what goes over the wire is different based on the framework?

In this case, I don't think so because it isn't really correct to send an If-Match with an empty string, so I don't think there is a need to normalize the behavior between the different frameworks.

Why was this passing before?

With the legacy framework we would record the requests before they were actually sent over the wire, so we didn't get to see effects that HttpClient/HttpWebRequest would have on the request. With the Test Proxy, the recording happens after the request goes through the transport layer to the proxy.

Does that imply an issue in our code that what goes over the wire is different based on the framework?

In this case, I don't think so because it isn't really correct to send an If-Match with an empty string, so I don't think there is a need to attempt to normalize the behavior between the different frameworks.

I guess my question was really around is this the tip of the iceberg that illustrates an issue that might affect other scenarios?  I would imagine that the payload over the wire is by design supposed to be the same in all frameworks?  If not why not, and if so then who is to say this is the only difference?  It might be worth us using this repro to investigate and uncover the root cause to verify one way or the other if this is isolated to just this one specific case or does it more broadly affect other cases as well.

Why was this passing before?

With the legacy framework we would record the requests before they were actually sent over the wire, so we didn't get to see effects that HttpClient/HttpWebRequest would have on the request. With the Test Proxy, the recording happens after the request goes through the transport layer to the proxy.

Does that imply an issue in our code that what goes over the wire is different based on the framework?

In this case, I don't think so because it isn't really correct to send an If-Match with an empty string, so I don't think there is a need to attempt to normalize the behavior between the different frameworks.

I guess my question was really around is this the tip of the iceberg that illustrates an issue that might affect other scenarios? I would imagine that the payload over the wire is by design supposed to be the same in all frameworks? If not why not, and if so then who is to say this is the only difference? It might be worth us using this repro to investigate and uncover the root cause to verify one way or the other if this is isolated to just this one specific case or does it more broadly affect other cases as well.

There certainly have been other differences that we've uncovered between the different transports - e.g. setting of content-type, content-length, cookies, and expect header. In general we've tried to align the behavior with HttpClient as it is the more modern stack. I think you raise a fair point and I'm happy to file an issue to investigate this difference further. I don't think we need to block the migration on this though, and I've already confirmed with @archerzz that leaving the If-Match header as null is the correct thing to do for the particular test.


Expose Ganache Options

The constructor should accept available Ganache options for customization.
See: https://github.com/trufflesuite/ganache#startup-options

Added! :)


Add more test cases data and test codes to ensure quality.

As we need to support more use cases and features, we added a lot of test cases datas to support more use cases, we also need to add test code and test cases to ensure the quality of the project.

Merged


merge flo-contrib and flo

clean up pom.xml
pass typesafe config to TerminationHookFactory
add flo-styx with TerminationLogging
upgrade libs
get logback completely out of the picture

@NatashaL @bergman PTAL

@honnix the error handling seems like it covers all cases. Both if there's an exception thrown and if the error is contained. Don't see what more we can do about it for now.
I think this is good for now. Any more comments or 👍  ? cc @bergman


Fix missing non-image augmentation in pooling augmenters

Codecov Report

Merging #428 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #428      +/-   ##
==========================================
+ Coverage   96.05%   96.06%   +0.01%
==========================================
  Files          34       34
  Lines       10707    10734      +27
==========================================
+ Hits        10284    10311      +27
  Misses        423      423


Panes should be resizable with the mouse

Probably depends on #991 getting done first
Drag a separator to (recursively) resize the panes that are separated by that separator.

Assigning to myself for now. I imagine it won't be too difficult. If anybody would like to take a crack at it though, feel free to let me know and we could just do a handoff. 😊

One idea I have would be to not even require a user to target a potentially thin separator, but while holding down Alt (to retain the theme with the pane key bindings) and dragging the mouse up and down over one horizontally split pane, resize that one height wise. And the same when moving the mouse left and right over a vertically split pane.

It would be nice if, while resizing, a percent or pixel adornment showed up that indicates the new sizes for both panes.

Any update on this? Its the one thing missing for me.

Nope. We'll make sure to update this thread when there is. In the meantime, might I recommend the Subscribe button?

That way you'll be notified of any updates to this thread, without needlessly pinging everyone on this thread ☺

still waiting for this

still waiting for this, almost 4 years passed...

Yep, we haven't had a chance to loop back on this, though we'd love the the contribution if you're interested!

Note
Walkthrough

Last time I tried this was in https://github.com/microsoft/terminal/compare/main...dev/migrie/f/drag-panes. IIRC, there were some scaling issues with mouse drags in XAML islands back then. I think those are mostly resolved these days.
Carlos also tried this again in dev/cazamor/drag-panes. I don't know how successful that was.

I don't think it'd be terribly difficult to resurrect the same approach (but base it off main since my original branch is nearly 4 years old now.

Massively agree with this new feature! Resizing via the keyboard is annoying. Also there are currently too many keyboard shortcuts to remember for an old man such as myself :>

I think dragging the panes is the wrong UX.  The alternative is to make the drag bar thicker and waste terminal space. I propose an alterative. We already have

to change the font size.  If we add

and instead of changing font size, it resizes the pane. The location of the mouse itself gives the hint as to where to resize. left, right, up down.

I agree. We need this feature

Punted to 1.23.

hi is this working and available in stable version ? how do i drag pane divider in windows terminal ? do i have to press Alt or any other keyboard key while dragging pane divider ?


Added OPEN_SOURCE_EVENTS.md

Fixed #1769

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Added OPEN_SOURCE_EVENTS.md
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Please add the gssoc and level labels to this! 😅


Switching camera to front not working with Swift4 Branch Demo

Switching camera to front camera not working with Swift4 Branch Demo.

@jpowang @Awalz
Its this code
       return AVCaptureDevice.devices(for: AVMediaType(rawValue: mediaType)).first```
Its not filtering for device position like before.

```swift
return AVCaptureDevice.devices(for: AVMediaType(rawValue: mediaType)).filter { $0.position == position }.first```