Pre-bundled dependency is bundled out of order

Describe the bug
When pre-bundling dependencies, it seems the vite:dep-pre-bundle plugin can cause ESBuild to bundle code out-of-order, leading to a runtime error.
More specifically, I have a minimal repro at MLoughry/vite-fluent-bundling-issue. Importing from both fluentui/react and @fluentui/react/lib/Pivot causes Pivot.js (which imports PivotBase from Pivot.base.js) to reference PivotBase before all of the code in Pivot.base.js executes.
Reproduction
https://github.com/MLoughry/vite-fluent-bundling-issue
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: Linux 5.4 Ubuntu 18.04.4 LTS (Bionic Beaver)
    CPU: (8) x64 Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
    Memory: 19.85 GB / 31.36 GB
    Container: Yes
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 14.15.4 - ~/.nvm/versions/node/v14.15.4/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v14.15.4/bin/npm
  npmPackages:
    vite: ^2.3.5 => 2.3.5

Used package manager: yarn
Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

This looks to be specific to esbuild, where bundle order is prioritizing export order over import order.
Logged here:
https://github.com/evanw/esbuild/issues/1433

Closing this as it's an upstream bug.


'openfhe.h' file not found by building make

Hallo
i use wsl Ubuntu 22.04
i build openfhe-development and want to build make python wrapper
my structure is:
/home/andre/openfhe-development
/home/andre/openfhe-python
i do these steps by installing:
cmake .. -Dpybind11_DIR=/home/andre/.local/lib/python3.10/site-packages/pybind11/share/cmake/pybind11
mkdir build
cd build
cmake .. -DOpenFHE_DIR=/home/andre/openfhe-development
make
but i get Error:
/home/evgen/openfhe-python/src/lib/bindings.cpp:10:10: fatal error: 'openfhe.h' file not found
#include "openfhe.h"
^~~~~~~~~~~
1 error generated.
make[2]: *** [CMakeFiles/openfhe.dir/build.make:76: CMakeFiles/openfhe.dir/src/lib/bindings.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:83: CMakeFiles/openfhe.dir/all] Error 2
make: *** [Makefile:136: all] Error 2
What can i do?

Hello, you can try add this line set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -I/path/to/your/openfhe/include") at the top line to your openfhe-python CMakeFiles.txt

@Rinoex hallo, i solved it other, but i am not sure if it is right
in open fhe development i done: sudo make install
in python wrapper i write
cmake .. -DOpenFHE_DIR=/usr/local/lib/OpenFHE
it looks like there are no errors
i set
export PYTHONPATH=(/home/evgen/openfhe-development/build/lib):$PYTHONPATH
and
export LD_LIBRARY_PATH=$PATH:/home/evgen/openfhe-development/build/lib
if i start ./simple-integers.py (in example/pke)
i get this:
./simple-integers.py: line 2: from: command not found
./simple-integers.py: line 7: syntax error near unexpected token (' ./simple-integers.py: line 7: parameters = CCParamsBFVRNS()'

@AndrUser65 - did you install the openfhe-development repo after building it ? Without that trying to build Python binding is not standard practice IMO

Hi I am also getting the same issue I have installed open fhe development repo and the examples of that is also working but in Python one I am getting the same issue. If you find any solution please let me know

@arcturusannamalai i solve this problem. it can be closed

@Sameeksha0709 did you build fhe development?
you can use docker. it is more easier

HI
I built the open-fhe development and it's working but in open-fhe python i am getting same error.  I am working on pi


If clause for template existence check

Can you please advice, is it possible to check template existence with if clause?
Below option does not work for me.
I created hook.env, but trying to call hook template that does not exist.
...
        env:
        {{- if eq (include "hook" .) "true" -}}
        {{ include "hook" . }}
        {{- end -}}

{{- define "hook.env" -}}
        env:
          - name: SOME_SECRET
            valueFrom:
              secretKeyRef:
                name: {{ .Release.Name }}-secret-key
                key: url
                optional: false
{{- end -}}

I am getting below error:
Error: UPGRADE FAILED: template: nginx/templates/hook.yaml:29:19: executing "nginx/templates/hook.yaml" at <include "hook" .>: error calling include: template: no template "hook" associated with template "gotpl"

Output of helm version:
version.BuildInfo{Version:"v3.8.2", GitCommit:"6e3701edea09e5d55a8ca2aae03a68917630e91b", GitTreeState:"clean", GoVersion:"go1.17.5"}
Thank you

@fox-md
no template "hook"

Do you have any templte "hook" by define?

Hi @yxxhero,
No, I do not. I would like to store below block in a chart library and to include it only if chart has template hook defined
        {{- if eq (include "hook" .) "true" -}}
        {{ include "hook" . }}
        {{- end -}}

Hi @fox-md,
If you know the name of the template you wish to check for (hook in your example), you can try the following:
{{- define "hookwrapper" -}}
{{- block "hook" . }}DEFAULT{{ end -}}
{{- end -}}

By calling include on "hookwrapper" you can determine if the hook existed, or if the block took effect. DEFAULT could be omitted, but then you wouldn't be able to tell if hook was defined and simply rendered nothing, or if hook was not defined.


@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/104773
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.0.0 -m "<description of version>" 61a338062e9ca33d17174b52b3524f3cfe05d8eb
git push origin v1.0.0


Use Byte Array Instead of String in Deserialization

During response deserialization Azure Core will convert the response byte stream into a String before passing it into the deserialization logic. Instead we should be passing the raw byte stream and letting the deserializer handle that. This will remove a temporary String that will be thrown away after deserializing.
Additionally, making this change will open up the option to more lazily read the network response in the future as converting to a stream requires for the entire message to be read.

@g2vinay, as we've been discussing offline we are going to target using InputStream/OutputStream as they offer lazier reading functionality than byte[] and may allow for optimizations where we don't read an entire request/response into memory if it is exceptionally large.


[Jira] Network Fails under New Authentication

Extension
https://www.raycast.com/raycast/jira
Description
The existing Jira extension functions correctly for me. However, after attempting the new extension and completing the authentication process, it fails to communicate through the API calls.
I am connected to a work VPN. As the Jira extension is primarily used for work, there is no need to switch to a new, incompatible version when the original one is functioning properly.
Please deprecate the new Jira extension and continue development on the old one, or somehow integrate the previous authentication method from the old Jira extension into this one. Thank you!
Steps To Reproduce

Install new Jira extension.
Authenticate in Jira.
Try running any Jira command.
See API communication failures.

Current Behaviour
API communication is blocked.
Expected Behaviour
API communication would work fine.

Do you get any specific errors? I'm wondering if this issue is a duplicate of #7104 or #7085.

@thomaslombart Hey Thomas, this is the flow of what happens after authenticating. Hopefully this helps:

And yes actually this seems like a duplicated issue from #7104 - I must've forgotten I created that one. Apologies for the duplicate.

Thanks for the additional details.

I am also using this at work with a VPN. The old version of the extension was working great. After upgrading, auth fails with this message:

Hoping this can be resolved, the JIRA extension is one of my favorite things about Raycast!

I am also facing the same issue under ZScaler

Could you try playing with those settings in the "Advanced" tab of the Raycast's preferences?

Tried using both the keychain, and a custom .pem cert provided by my company... Not only is it still failing, but now Raycast team has removed the original (better) extension that was working. Is the Raycast team trying to lose customers?

Update: After getting updated .pem files from the powers that be and using those in the Advanced Configuration (custom) setting, the extension is loading things once more! Hopefully this helps. Thank you.

Awesome! Hopefully we can drive this extension forward in the open now!


Fix blog post link

Summary
Updates link to blog post in reno prelude.
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.689%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1851

Relevant Lines:
1997

💛  - Coveralls

I wonder if a 0.7.1 release is required.

Indeed, we just saw in Qiskit Nature that without a new release tag, the prelude reno file will simply be filtered because its modification time is newer than any tag and, thus, will be filtered out. Rather than messing with the filter and reverting that, we now opted for https://github.com/qiskit-community/qiskit-nature/pull/1288 which should resolve this and have the prelude re-appear :+1:


setup production site

Need system to allow both dev and master branches to link with different databases, accessible under node_env dev and production, ideally without exposing sensitive api keys.
Useful links:
https://github.com/travis-ci/travis-ci/issues/6532
https://graysonkoonce.com/getting-the-current-branch-name-during-a-pull-request-in-travis-ci/
https://docs.travis-ci.com/user/deployment/firebase/
https://docs.travis-ci.com/user/environment-variables/

tried various solutions, ultimately travis scripts to populate variables based on git branches failed so opted for simpler option to look at host domain. Still can't fully figure out why but was a total time sink.
Additional links to help if ever reopening:
http://www.mikitamanko.com/blog/2014/10/19/travis-branch-specific-variable/
https://github.com/travis-ci/travis-ci/issues/7472


Update deprecated i18n loader module

The tests are failing because the module's code was not updated to refer to new name.
If you search for vue-i18n-loader you'll find one place in /src/index.js and couple in docs.

There was already previous and complete PR #578. Closing.


Qualys - [FAIL] ERROR: no such child: count

When trying to fetch the results of qualys with VulnWhisperer, I am getting the following error:

[FAIL] ERROR: no such child: count

As a user of qualysapi, I understand that this is an error of Qualys API changes that have not been updated in the qualysapi library, on top of which VulnWhisperer works, although I haven't seen any Issue related to this topic. Is this an issue that other VulnWhisperer users are meeting?
As details of my deployment, I still don't have the ELK stack deployed, as I was making sure first the data fetching from the scanners, and I have tried the qualys urls at https://www.qualys.com/docs/qualys-was-api-user-guide.pdf (URL to Qualys API Server) with no luck, discarding the endpoint.
No issues at all with Nessus.

Hey guys,
Might it be that I am talking about Qualys Vulnerability Management instead of Qualys Web Applications, and that they use the same endpoint even if they use different APIs for the job?
In that case, this would probably go with https://github.com/austin-taylor/VulnWhisperer/issues/51...

Closing issue as feature is on development by @pemontto , checking on it. Thanks @pemontto !


fix: Adds node_modules to the .gitignore file

Issue - #50

@seveibar Can you review this PR please?


Invariant Violation: requireNativeComponent:"ReactYoutube" was not found in UIManager

Hi there,
I'm a beginner in react native. I have been trying to play youtube videos in android. But I found this error "ReactYoutube" was not found in UIManager ". I can see someone maybe fixed the issue for IOS which I haven't tried though.
It will be really appreciated if someone can help me to fix it.
Thank you,

Same here, for me the error occurs using the start example provided

Same issue here
"react": "16.8.6", 	"react-native-youtube": "^2.0.0",         "react-native": "0.60.4",

Solved this issue by adding libraries in

add this and pod install and done!


JSDoc for methods with multiple signatures

First I've thought about union types but they can solve only part of the problem. Original discussion started here. In case codeplex had been abandoned, I copy my question here.
Please take a look at this function. https://github.com/digitalbazaar/forge/blob/master/js/rsa.js#L802-L885 As you can see from comments there are a lot of ways to use it. If I need to make a type definitions for it (actually I do) with JSDoc Intellisense support, then I have to copy general function description like 10 times. This will make my definition 3 times longer than source function and also very hard to modify. In libraries like forge almost all functions have being made that way.
Can you give me some tip about making definitions in such circumstances?

Surprisingly, I just run into this now. It's certainly surprising, I always assumed it worked automatically without having to duplicate comments. See https://github.com/types/npm-pug/pull/5#discussion_r78636341.
I would expect this to be a cascade. The first JSDoc description and params should be copied to the following overloads automatically, except you could override the description/param later on by writing it out explicitly. Is this is a reasonable change? If so, I'd be very interested in a trying to patch it if there's a pointer on where to get started. If only so I can avoid merging hard to maintain workarounds like duplicating documentation.

Related issue: https://github.com/Microsoft/TypeScript/issues/3294
It would be great if this worked as @blakeembrey described 👌

Any progress?

Definitely would love to see this implemented somehow. A function with 3 overloaded type definitions needs copy/paste for all three... not fun...

@MichaelTontchev you mean that you can define overload now and it will work but with more copy-paste? can you show?

Case here is a es5 class with a method member that is a candidate for method overloading. Using union types this member can be described as
/**
 * @todo See https://github.com/Microsoft/TypeScript/issues/407
 *
 * @param {string} name
 * @param {Function | BUFFERTYPE } [content]
 * @param {string} [type]
 * @return {Function | void}
 */
Runtime.prototype.createAttachment = function(name, content, type) {
...

In case of a Function for content, it should return a Function. In case of a BUFFERTYPE for content, it should return void.
Suggestion 1
Make overloaded definition in external d.ts(not on runtime.d.ts).
P.S. Tried to apply it on the js es5 class level or member method level, but found not way to accomplish that.
Suggestion 2
Make overload list definition in three comment blocks.
/**
 * @param {string} name
 * @param {Function} [content]
 * @param {string} [type]
 * @return {Function}
 */
/**
 * @param {string} name
 * @param {BUFFERTYPE} [content]
 * @param {string} [type]
 * @return {void}
 */
Runtime.prototype.createAttachment = function(name, content, type) {
...

P.S. Tried to apply it on the member method level, but only the first was considered by TS as method signature.

@mhegazy what kind of  feedback is missing?
IMO, everything is pretty straightforward:
export function A(a: string): string;
export function A(a: number): string;
/**
 * Overloaded comment only for this signature
 * @description overloaded description only for this signature
 */
export function A(a: string, b: string): string;
/**
 * @param b overloaded description for `b` argument only for this signature
 * @returns overloaded description for `return` only for this signature
 */
export function A(a: string, b: number): string;
export function A(a: number, b: string): string;
export function A(a: number, b: number): string;
/**
 * Default comment for function A
 * @description default description for A
 * @param a default description for `a` argument
 * @param [b] default description for `b` argument
 * @returns default comment for `return`
 */
export function A(a: string | number, b?: string | number): string {
    // implementation
}

So, each time when JSDoc is shown, it should merge default docs (that came from implementation in case of .ts file, or from most generic overload in case of .d.ts file) with docs that belong to particular overload, where last one takes precedence.

@mhegazy what kind of  feedback is missing?
IMO, everything is pretty straightforward:
export function A(a: string): string;
export function A(a: number): string;
/**
 * Overloaded comment only for this signature
 * @description overloaded description only for this signature
 */
export function A(a: string, b: string): string;
/**
 * @param b overloaded description for `b` argument only for this signature
 * @returns overloaded description for `return` only for this signature
 */
export function A(a: string, b: number): string;
export function A(a: number, b: string): string;
export function A(a: number, b: number): string;
/**
 * Default comment for function A
 * @description default description for A
 * @param a default description for `a` argument
 * @param [b] default description for `b` argument
 * @returns default comment for `return`
 */
export function A(a: string | number, b?: string | number): string {
    // implementation
}

So, each time when JSDoc is shown, it should merge default docs (that came from implementation in case of .ts file, or from most generic overload in case of .d.ts file) with docs that belong to particular overload, where last one takes precedence.

I'm curious as well.

Ran into this one, too.  Cascading down the first description would be the best, I think.  Would greatly reduce the size of .d.ts files that document overloaded functions (In my case, curried functions).

Complicating things even further, the new @deprecated tag would be ambiguous if appearing on the first signature; overloads are sometimes deprecated individually, but it's also common to deprecate an entire function.
As of the 4.0 beta, quick info says a function is deprecated if -- and only if -- the first signature has @deprecated. But the checker says a function is deprecated if any signature is deprecated. This is likely to change, but it illustrates how hard it is to find the correct behaviour.

For what it’s worth, JSDoc has an @inheritDoc tag; maybe it can be repurposed for TypeScript documentation?
I like the idea of cascading. If an overload has @inheritdoc, it would inherit everything from the overload above, but would also include any additional documentation. This would help in the case of the new @deprecated tag.
Example 1: basic @inheritDoc usage
interface Vector {
   /**
    * Add a vector to this vector.
    * @param v - a vector to be added
    * @return - the vector sum
    */
   plus(v: Vector): Vector;
   /**
    * @inheritDoc
    * @param v - a tuple of 3 numbers to be added
    */   // should inherit the description and @return tag, but not the @param tag
   plus(v: [number, number, number]): Vector;
}

Example 2: marking only last overload(s) as @deprecated
/** A function that does something. */
function foo(x: any): void;
/** @inheritdoc */
function foo(x: any, y: any): void;
/** @inheritdoc @deprecated */
function foo(x: any, y: any, z: any): void;
function foo(...args: any[]): any { /* implementation */ }

(This requires moving any deprecated overloads to the bottom, as we don’t want non-deprecated overloads to inherit the tag.)
/** A function that does something. */
function foo(x: any): void;
-/** @inheritdoc */
-function foo(x: any, y: any): void;
/** @inheritdoc */
function foo(x: any, y: any, z: any): void;
+/** @inheritdoc @deprecated */
+function foo(x: any, y: any): void; # need to move to bottom
function foo(...args: any[]): any { /* implementation */ }

I found you can just put the main declaration first, and the overloads after, like:
/** deserialize a componnet id from raw object */
static fromObject(object: ComponentIdObj, scope?: string) {
	// ...
}
/** provide scope separaetly, e.g. fromObject({ name: 'button' }, 'teambit.base-ui') */
static fromObject(object: Omit<ComponentIdObj, 'scope'>, scope: string): ComponentID;
static fromObject(object: ComponentIdObj, scope?: string): ComponentID;

VSC isn't showing the strikethrough for @deprecated overloads, though.

any progress?😀

There is sort of a way to do this.
You can create an interface with a single any member having the same name as your overloaded function and apply docs to that.  The downside is that @parameter docs don't seem to propagate correctly, at least not in VS Code.
interface Docs {
    /**
     * Documentation for `foo` function.
     * @param param1 Param 1 is important.
     * @param param2 So is param 2!
     * @returns A tuple of its arguments.
     *
     * @example
     * ```ts
     * const result = foo("hello", "goodbye");
     * ```
     */
    foo: any;
}

interface Overloads extends Docs {
    foo<T>(param1: T, param2: T): T[];
    foo<T, U>(param1: T, param2: U): [T, U];
}

Hovering over either overload shows the correct documentation (but keep reading after the pictures for a caveat):

And it shows correctly in the suggestion list, too:

The only downside is that you don't get parameter information at the call site:

So you still have to duplicate the parameter documentation for each overload if you want that.
interface Docs {
	/**
	 * Documentation for `foo` function.
	 * @param param1 Param 1 is important.
	 * @param param2 So is param 2!
	 * @returns A tuple of its arguments.
	 *
	 * @example
	 * ```ts
	 * const result = foo("hello", "goodbye");
	 * ```
	 */
	foo: any;
}

interface Overloads extends Docs {
	/**
	 * @param param1 Param 1 is important.
	 * @param param2 So is param 2!
	 */
	foo<T>(param1: T, param2: T): T[];
	/**
	 * @param param1 Param 1 is important.
	 * @param param2 So is param 2!
	 */
	foo<T, U>(param1: T, param2: U): [T, U];
}

Although notice that you lose the @returns and @example in this case.
Personally, if the parameter information would propagate correctly, and if adding documentation didn't lose some that was there before, I'd consider this issue resolved.  But I'm not actually sure if it's a TypeScript issue or a VS Code issue.

Something I noticed with higher order functions: since there is no way to have a JSDoc description show up in a tooltip when hovering over the return value of a function, using a workaround such as the one @P-Daddy suggested is going to totally obfuscate the little information the user had left: const foo: Overloads is not a tooltip I am happy to see, so I choose to bear with the duplication because a function signature is already something.
Now I would love it if there was a way to control how type aliases and interfaces show up in tooltips, but having some way to manage JSDoc duplication would also help.

https://github.com/microsoft/TypeScript/issues/51005 has a much clearer title: this title made me think it was a stale dupe of the issue for implementing @overload for use with JSDoc to declare types in JavaScript files.


ign -> gz CMake, Config, and Example Files migration : gz-cmake

See: gazebo-tooling/release-tools#698

Needs merge of https://github.com/gazebosim/gz-cmake/pull/273

NOTE: THIS MUST BE REBASE MERGED!! Files were moved!
Description
Migrates IgnXXX.cmake files, examples, and configured files.
Hard-tocks

ignition..in and ign..in files have been hard migrated since they're used internally. References to them in gz-cmake have also been migrated.

Tick-tocks

All IgnXXX.cmake files have been migrated to Gz.

Some downstream packages use IgnPython.cmake and IgnBenchmark.cmake, symlinks have been installed for tick-tocking (though warnings cannot be emitted.)

testing this branch for macOS and windows CI in https://github.com/gazebosim/gz-sim/pull/1586

looks like the IgnPython symlink doesn't work on windows:

 https://build.osrfoundation.org/job/ign_gazebo-pr-win/4711/

--- stderr: gz-math7
CMake Error at CMakeLists.txt:82 (include):
  include could not find requested file:

    IgnPython

could we install a dummy IgnPython file that just includes GzPython? it could probably include a cmake warning in that file (similar to our ignition/*/config.hh files)


"Beciu", "Bârseștii de Jos" and "Smârdan" are listed in the drop-down menu

Description:
"Beciu", "Bârseștii de Jos" and "Smârdan" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Beciu" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Beciu, TELEORMAN (Beciu)" and "Comuna Beciu, TELEORMAN".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Bârseștii de Jos" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Bârseștii de Jos, TELEORMAN (Beciu)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Smârdan" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Smârdan, TELEORMAN (Beciu)".


Fix remaining type test failures

Fixes the remaining type test failures. 🤞

Would you mind checking whether the errors are from the tests, or the codebase itself? I'm on mobile right now, so I can't.

The errors are from dtslint -- likely related to: https://github.com/color-js/color.js/pull/571#issuecomment-2195420830


Add device-restricted off to min brightness feature

In IKEA Zigbee implementation controllers have the ability to turn on the connected bulb (or light group) at minimum brightness if the action to increment brightness occurs (i.e. pressing the dedicated button for a E1810, turning the device to the right for a ICTC-G-1 etc.).
This PR implements the feature, which can be device restricted, since not all controllers which will be integrated in the future could be designed to have this capability.
The supports_from_off_to_min_brightness() method, which can be overridden by every controller, defines whether the device supports this feature or not. By default, devices will not implement this feature.
Also, I had to edit before_action() signatures, passing action arguments to the methods, something that could come in handy if more complex checks will have to be performed in the future.
I succesfully tested and enabled the feature on E1810 and E1743 controllers. I left the ICTC-G-1 unsupported since the integration is quite unstable and there are still issues with handling duplicate and unwanted messages.

Hi @xaviml,
I made some tests today with a E1810 and an IKEA bulb paired together and I confirm that, both with holding and clicking the brightness_up button when the light is off, the lamp is turned on at minimum brightness.
I updated the branch with the suggested changes, enabling the user to specify whether to enable this feature or not for the single app instance, and removed the defaults for E1810 and E1743 controllers.
If everything is fine and the PR is merged we should also update docs including the new feature.

@EPMatt Thanks you for your contribution! This will be included in the next release.

You're welcome @xaviml! 👍


Clusterable redirects

Thanks for contributing to Wagtail! 🎉
Please review the contributor guidelines and confirm that the tests pass in case of Python changes.

Hi @HalcyonChimera - please can you explain the purpose of this change?

I have the requirement of versioning the actual urls that point to a page; i.e if a page is moved, then a redirect is automatically created. With this I was able to use an InlinePanel so that redirects pointing at that page can be added/changed/removed from a given Page's promote panel. With only a ForeignKey, there is an error  has no attribute 'redirect_set'.

Thanks for the clarification! I have a feeling that this change will cause broken behaviour for existing users, though:

A user creates and saves a page (this will result in an empty list of redirects being saved within the PageRevision record, regardless of whether the admin form includes an InlinePanel for redirects)
They then set up redirects through the Settings -> Redirects area (which creates the redirect records immediately)
They make further edits to the page, and publish it (- the edits are based on the most recent PageRevision record, which has an empty list of redirects - and so publishing the page will cause the existing redirects to be deleted)

This is probably a general issue that would affect any model that's editable in two places - as an independent model, and through an InlinePanel. In this case you're probably better off setting up an independent "inline redirect" model that works separately to the wagtailredirects module, with its own middleware.

The issue with having it separate is that it will be confusing for editors to have two places to look in order to determine the redirects that apply to a given page. Maybe we should compare the revision with other redirects created since it was last saved and try to replay the changes  into the revision record before it is saved and throw growls that say 'there are conflicting redirects'?
I feel like duplicating the entire redirect functionality here isn't necessarily the best use of time, and this is a feature I think it makes a lot of sense to provide; there is already the ability to change the slug of a page in the promote panel, for example. Having the ability to control those changes in the same location has a certain ergonomics to it.
What other edge cases might there be in terms of migrations and or chronologically dependent actions?

The issue here is really that there are lots of different uses for redirects: preserving links when a page is moved, replacing an older site built on a different CMS, providing short/memorable links, doing tracking/analytics, providing a fixed link to changing resources (e.g. a monthly publication that has a redirect pointing to 'latest issue') and probably lots more that I haven't thought of. For some of those uses, it makes sense to tie redirects to a page's revisioning / publishing workflow; for others, it would be very much a backward step.
The current behaviour of wagtailredirects isn't the best fit for everything (indeed, people have created their own alternatives to it - see #655 for example), but existing users are relying on it to continue working in the same way, and I'd be very reluctant to make such a sweeping change to an established part of Wagtail.


Superfluous examples/boilerplates files

All of the boilerplates in examples/boilerplates technically don't need to be there, and all of the defaults are always generated from config.yml.

Commit 8b2f383 removes examples/boilerplates and makes sure tests/doctests don't rely on its existence.


Build node-driver-registrar using our own builder

For our FIPS requirements, we need all images to be built using our own builder.

/sem-approve

Could we also get this cherry-picked into the release-v3.24 branch as well?

/sem-approve

/sem-approve


Rewriting getting started commands for testing

This PR intends to remark the importance of building the frontend before running the tests.
Also it decorates the build commands for better readability .
It may be related to #636

Changed to npm run build:all and resolved an ambiguous test message due missing package name.


Help messages with dunders are rendered as bold instead of displaying literal __

Help messages with content that includes __XXXX__ is rendered bold instead of displaying the __ which is common for dunder variables.

example.py:1:22: F401 [*] `.version.__version__` imported but unused
  |
1 | from .version import __version__
  |                      ^^^^^^^^^^^ F401
  |
  = help: Remove unused import: `.version.version`

Found 1 error.
[*] 1 potentially fixable with the --fix option.

or
example.pyi:3:32: PYI016 Duplicate union member `Literal["__test__"]`
  |
1 | from typing import Literal, Union

2 |
3 | x = Union[Literal["__test__"], Literal["__test__"]]
  |                                ^^^^^^^^^^^^^^^^^^^ PYI016
  |
  = help: Remove duplicate union member `Literal["test"]`

Originally reported in https://github.com/astral-sh/ruff/issues/5697#issuecomment-1631623181

This came up once before, in response IIRC @MichaReiser said we should look into replacing the annotate-snippets crate which has some unusual behavior (like this).

See https://github.com/rust-lang/annotate-snippets-rs/pull/54

Closed by https://github.com/astral-sh/ruff/pull/8646.


The episde rewards in each traning step varies greatly, is it normal?

I am training the highway with PPO based on rliib. In rllib, each training step consists of multiple episodes. I notice that the sum of rewards in each episode varies greatly. I wonder whether it is normal for this simulation bed. By the way, can you provide the best parameters for the highway, or other env if possible? Thanks!

Hi! I guess this is 'normal' in the sense that it just shows that learning a good (and non-trivial) policy with a 0% collision rate is difficult, at least with the default observation. And if you have a probability p of getting a collision, you should expect a variance of p(1-p) relative to the best return (e.g. if sum of rewards is typically around 20 and p=5%, then we can expect expect a std of about +/- 5)
I have not run many PPO experiment, so I don't really have any best parameters to recommend.
I would only encourage you to try different types of observations and/or models, see e.g. this comparison


add ability to pick custom year and month

Hi,thanks for this library.
I think one feature this library needs is the ability to select particular year or month without sliding.
something like this for example:

@simti this feature has been added in #10. You can use it now!😊


[ENH]: Added Prettier for Code Formatting

Add Prettier for Code Formatting
Thank you for contributing to our project! Please provide a summary of your changes and reference any related issues below.
Issue Number: Fixes #34
🛠 Type of Change

[ ] 🐛 Bug fix
[x] ✨ New feature
[ ] 🚨 Breaking change
[ ] 📚 Documentation update

✅ Checklist
To ensure a smooth review process, please check off each item as you complete it:

[x] Code Style: My code adheres to the project’s style guidelines.
[x] Self-Review: I have reviewed my own code and made improvements.
[x] Comments: I’ve added comments to explain complex or non-obvious parts of the code.
[x] Documentation: I’ve updated the documentation to reflect my changes.
[x] Warnings: My changes introduce no new warnings.
[x] Tests: I’ve added tests to verify that my changes work as expected.
[x] Passes Locally: All new and existing unit tests pass on my local machine.

Changes
Added Prettier Configuration:
.prettierrc: Added for consistent code styling.
package.json: Included Prettier scripts for formatting and checking.
package-lock.json: Updated to reflect the addition of Prettier.
Formatted Codebase: Applied Prettier formatting to existing files to ensure consistency.
We appreciate your contributions! If you have any questions or need further assistance, feel free to reach out.

i have added a pr of eslint so in future if we use eslint will prettier override eslint??
if doesnt do can you add that ? @Riya267

i have added a pr of eslint so in future if we use eslint will prettier override eslint?? if doesnt do can you add that ? @Riya267

Yes, Prettier and ESLint can sometimes conflict depending on the rules and plugins you use. To prevent conflicts and ensure consistent formatting, you should integrate Prettier as a plugin in your ESLint configuration. This setup ensures that Prettier and ESLint complement each other effectively.

@Riya267 thanks

@Riya267 my eslint pr has been merged
as i can see you pr is conflicting too much so please kindly close this pr and re do the work and later open a new pr

@Riya267 my eslint pr has been merged as i can see you pr is conflicting too much so please kindly close this pr and re do the work and later open a new pr

no need for new pr as conflicts are resolved now

@Riya267 is prettier over writing eslint..have you tested ?

no its over writing


Avoiding an inbox deadlock on heartbeats

There is a very specific edge case where if a heartbeat attempts to generate actor and provider data and either the actor module or the provider module are currently in the middle of processing something that can take a long time, or worse, when a ping is requested it emits an ad hoc heartbeat at or near the time of a regular interval heartbeat .... we can create a situation where calling :get_instance_id or :get_link_name etc on the OTP process can time out.
We've already indicated that when host contents get extremely large, the "old" format of the heartbeat data expands too much. There was even a TODO in the code to change this. By changing it so heartbeats don't actually make a call (which drops a message into an OTP process inbox) to each actor process and each provider process during a heartbeat, we now include actor count in a map and simply include a list of providers.
Anything downstream that consumes the previous heartbeat data format will need to be modified accordingly.
The actors field is now a map from string to int (pk -> count), and the providers field is now a simple list of objects with the link_name and public_key fields.
{
  "data": {
    "actors": {
      "MB2ZQB6ROOMAYBO4ZCTFYWN7YIVBWA3MTKZYAQKJMTIHE2ELLRW2E3ZW": 10
    },
    "friendly_name": "wandering-meadow-5880",
    "labels": {
      "hostcore.arch": "aarch64",
      "hostcore.os": "macos",
      "hostcore.osfamily": "unix"
    },
    "providers": [
      {
        "link_name": "default",
        "public_key": "VAG3QITQQ2ODAOWB5TTQSDJ53XK3SHBEIFNK4AYJ5RKAX2UNSCAPHA5M"
      }
    ],
    "uptime_human": "1 minute, 32 seconds",
    "uptime_seconds": 92,
    "version": "0.60.0"
  },
  "datacontenttype": "application/json",
  "id": "d6737096-d572-400f-9242-d319ee54b8cf",
  "source": "NA2JERGCC6YGFOG662T3JYSWCDYWIJ2BBKRFJIIMULX3FK44K775TYIJ",
  "specversion": "1.0",
  "time": "2023-01-17T20:48:18.037594Z",
  "type": "com.wasmcloud.lattice.host_heartbeat"
}

Modified this so that it now emits a backwards-compatible heartbeat as well as the new one (it doesn't cost any extra CPU). The backwards compatible heartbeat will be retired in a future version (e.g. it's a deprecated heartbeat).
[#2] Received on "wasmbus.evt.default"
{"data":{"actors":[],"friendly_name":"bouncing-water-7264","labels":{"hostcore.arch":"aarch64","hostcore.os":"macos","hostcore.osfamily":"unix"},"providers":[],"uptime_human":"37 seconds","uptime_seconds":37,"version":"0.60.0"},"datacontenttype":"application/json","id":"0815f259-264a-4860-94ba-cb37154c056c","source":"NAQ6ZCLSJ4N4RD2QO2QTXLT4NVWOF6CKX7L2ZB6TYM26BNZ2DE7G7XW4","specversion":"1.0","time":"2023-01-25T13:04:26.587754Z","type":"com.wasmcloud.lattice.host_heartbeat"}

[#3] Received on "wasmbus.evt.default"
{"data":{"actors":{},"friendly_name":"bouncing-water-7264","labels":{"hostcore.arch":"aarch64","hostcore.os":"macos","hostcore.osfamily":"unix"},"providers":[],"uptime_human":"37 seconds","uptime_seconds":37,"version":"0.60.0"},"datacontenttype":"application/json","id":"95843b31-9d43-4d2a-a04e-ebd01f92a53c","source":"NAQ6ZCLSJ4N4RD2QO2QTXLT4NVWOF6CKX7L2ZB6TYM26BNZ2DE7G7XW4","specversion":"1.0","time":"2023-01-25T13:04:26.587844Z","type":"com.wasmcloud.lattice.host_heartbeat.v2"}

Consequences: anything listening to the old heartbeat will get empty values for contract_id and instance Id. To my knowledge, nothing actually uses that information right now as it is obtained from querying inventory.

Just so we don't forget, this PR will be slated for the 0.61.0 release

I think now that we emit backwards compatible/deprecated heartbeats, we can put this in the 0.60 RC

It's not clear why all_actors_for_hb is a list that needs to be turned into a map, whereas all_providers_for_hb is a list that doesn't need to be turned into a map
Because the actors field in the output is actually a map (from string -> int), whereas the list of providers is actually a list of structs. I'll add type annotations.


⚠ Bofrost.lu has degraded performance

In b234183, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1904 ms

Resolved: Bofrost.lu performance has improved in 27368a7 after 16 minutes.


Problem in updating cell on didSelect.

First of all thank a lot for great library. Im using latest version of pod on Xcode v9.4.
Ive implemented everything as you mentioned in your demo projects and tutorial. Everything is running fine except one thing. Whenever i'm clicking on particular date, then that date is not selected. If i click again on different date then previous date is selected not current one. Same problem in Month and Year updation also.
I think there might be problem with willDisplay cell function as its not getting.
Please help and thanks in advance :)

did you implement the didSelect and willSelect function as shown in issue #553 ?

Yes i have.  Have you tested this with latest Xcode ?

not yet. will do so over the weekend. Has it been breaking since new XCode?

I think its related new update only. Im using JTApple since last night only so no idea.

hmm. re-read your problem. It doesnnt sound Xcode related.
got a sample project or github somewhere i can take a look at?

Make sure you selected "didSelectDate" and not "didDeselectDate" which would cause your issue.


Loading OPFS causes DataCloneError

Unhandled Promise Rejection: DataCloneError: The object can not be cloned. when showMapOpfs doesn't have !isSafari().
Possibly coming from idb related code based on the error stack, but it wasn't clear.

Still an issue with Safari 17.3


[Bug]: GitHub Discussions are disabled

What happened?
Opening a feature request fails because the link leads to GitHub discussions, which is not available.

Hello, I tried to fix the issue
This is what I did:
Modified the 'Request a feature' link in .github/ISSUE_TEMPLATE/config.yml to use GitHub issues instead of discussions, which are not available for this project. This change ensures that users can successfully submit feature requests.
I also created pull request: https://github.com/eighty9nine/filament-reports/pull/36

[!CAUTION]
Disclaimer: This fix was created by Latta AI and you should never merge before you check the correctness of generated code!
The fix provided by Latta AI might not be complete and it can serve as an inspiration.

This bug was fixed for free by Latta AI - https://latta.ai/ourmission
If you no longer want Latta AI to attempt fixing issues on your repository, you can block this account.


 When they tap on the button which launches the sign-in intent they get stuck.
Steps to reproduce:
I couldn't replicate it on my device.
Observed Results:
I guessed it might be related to Google Smart lock, so I asked the users to remove the credentials or app or even disable it but they didn't help.
Relevant Code:
  private void onLoginButton(View view) {
      ...
      startActivityForResult(buildSignInIntent(), RC_SIGN_IN);
      ...
  }

  @NonNull
  private Intent buildSignInIntent() {
      List<AuthUI.IdpConfig> selectedProviders = new ArrayList<>();
      selectedProviders.add(new AuthUI.IdpConfig.EmailBuilder().build());
      selectedProviders.add(new AuthUI.IdpConfig.FacebookBuilder().build());
      selectedProviders.add(new AuthUI.IdpConfig.GoogleBuilder().build());

      AuthUI.SignInIntentBuilder builder = AuthUI.getInstance().createSignInIntentBuilder()
              .setLogo(AuthUI.NO_LOGO)
              .setTheme(R.style.AppTheme)
              .setIsSmartLockEnabled(!BuildConfig.DEBUG /* credentials */, true /* hints */)
              .setAvailableProviders(selectedProviders);

      AuthMethodPickerLayout customLayout = new AuthMethodPickerLayout
              .Builder(R.layout.fragment_register)
              .setGoogleButtonId(R.id.custom_google_signin_button)
              .setEmailButtonId(R.id.custom_email_signin_button)
              .setFacebookButtonId(R.id.custom_facebook_signin_button)
              .setTosAndPrivacyPolicyId(R.id.custom_tos)
              .build();

      builder.setAuthMethodPickerLayout(customLayout);

      builder.setTosAndPrivacyPolicyUrls(Constants.TermsOfUseURL, Constants.PrivacyPolicyURL);

      return builder.build();
  }

We have released a new version with 8.0.1 and I'm waiting for feedbacks.

Same problem here using 8.0.1.

We had the same problem using 8.0.0, and as a workaround in one of the phones we use for testing, we cleaned the "google play services" cache and it resolves the issue.  The list of devices where we have the issue reported:
Xiaomi Redmi 9A/x64/Android 11 API 30
Vivo/x64/Android 12 API 31
com.firebaseui:firebase-ui-auth:8.0.0
com.google.firebase:firebase-bom:30.0.1

Digging deeper into the issue where the intent never shows the providers,  we found that the error has something to do with missing credentials in the Smart Lock for passwords and Connected Account at phone vaults.

We debugged all the transactions from launching the intent on the onCreate@KickoffActivity until the SignInKickStarter.javaL97
The execution got stuck at
https://github.com/firebase/FirebaseUI-Android/blob/5b6c9f01f5a674d754d8e9b1242197fe040086e7/auth/src/main/java/com/firebase/ui/auth/data/remote/SignInKickstarter.java#L97-L121
In the phone stack we started to see some exceptions as follows.

10-27 17:47:28.209  8195 30292 E AuthPII : [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/cclog
10-27 17:47:28.209  8195 30292 E AuthPII : aaky: Long live credential not available.
...
10-27 17:47:28.244  8195 30292 E AuthPII : Message is Long live credential not available.
10-27 17:47:28.244  8195 30292 E AuthPII : aaky: Long live credential not available.
10-27 17:47:28.244  8195 30292 E AuthPII : 	at kzz.a(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):8)
...
10-27 17:47:28.244  8195 30292 W Auth    : [GetToken] GetToken failed with status code: BadAuthentication
10-27 17:47:28.258  8195 30292 W Auth    : [GoogleAuthUtil] isUserRecoverableError status: BAD_AUTHENTICATION
10-27 17:47:28.259  8195 30292 W GoogleAuthUtil: Error when getting token

We believed that it has something to do with credential, therefore, in another physical phone, we changed the password on google's end and we removed the google play services mimicking the situation where the Oauth token is not available. Then we were able to reproduce the bug.

There's a special exception com.google.android.gms.auth.UserRecoverableAuthException in the same sequences of errors that we guess isn't handled by FirebaseUI. Might be a very rare situation to handle.

operation=List, opStatusCode=11005 [CONTEXT service_id=80 ]
10-27 17:47:46.706 15044 15507 W AsyncOperation: OperationException[Status{statusCode=Error retrieving oauth token, resolution=PendingIntent{4d2f308: android.os.BinderProxy@40e1aa1}}]
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at zdl.c(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):14)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at zdl.d(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):16)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at zdl.f(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):4)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at asna.er(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):1)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at asng.run(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):12)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at cljx.run(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):2)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at ablo.c(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):6)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at ablo.run(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):7)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at abqt.run(:com.google.android.gms<EMAIL_ADDRESS>(100300-480714934):0)
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at java.lang.Thread.run(Thread.java:764)
10-27 17:47:46.706 15044 15507 W AsyncOperation: Caused by: zcm: Error retrieving oauth token
10-27 17:47:46.706 15044 15507 W AsyncOperation: 	at zib.c(:com.google.android.gms<EMAIL_ADDRESS>(100300
...
10-27 17:47:46.706 15044 15507 W AsyncOperation: Caused by: com.google.android.gms.auth.UserRecoverableAuthException: BadAuthentication

Not being handle the exception com.google.android.gms.auth.UserRecoverableAuthException leads to the intent to never return the control the app and users get on a bad situation where the are waiting the activity to start or display an error message.

I'm also seeing this issue with 2 reports in the last couple of days - users unable to get into my app.
Device 1 (Confirmed): Samsung S21+ 5G / Android 12 / Google Play system June 1 2022
Device 2 (Reported not confirmed): Galaxy S10 / Android 12
Environment is:
implementation platform('com.google.firebase:firebase-bom:30.3.2')
implementation 'com.firebaseui:firebase-ui-auth:8.0.2'
implementation 'com.firebaseui:firebase-ui-firestore:6.1.0'
implementation 'com.firebaseui:firebase-ui-storage:6.4.0'
(with older versions of firestore and storage, I upgraded auth hoping that would address the issue)
    List<AuthUI.IdpConfig> providers = Arrays.asList(
            new AuthUI.IdpConfig.GoogleBuilder().build()
    );

    // Create and launch sign-in intent
    startActivityForResult(
            AuthUI.getInstance()
                    .createSignInIntentBuilder()
                    .setAvailableProviders(providers)
                    .build(),
            RC_SIGN_IN);

I had access to device 1 for a couple hours and was able to get some logs and try a few things.

Cleaning the "google play services" cache didn't resolve the issue for me
Tried updating Google Play system from June 1 2022 but was unable to (maybe that is the latest available for that device).
I was able to complete the authentication flow if I added ".setIsSmartLockEnabled(false)" to the AuthUI request but after login the app was unusable (a quick glance at the log revealed similar authentication type issues).

Any suggestions for workarounds?
Some snippets of the logs:
2022-10-28 20:20:25.081 20493-20756/? E/earn: ~~~ Channel {0} was not shutdown properly!!! ~~~
Make sure to call shutdown()/shutdownNow() and wait until awaitTermination() returns true.
java.lang.RuntimeException: ManagedChannel allocation site
at earm.(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):3)
at earn.(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):2)
...
at java.lang.Thread.run(Thread.java:920)
2022-10-28 20:20:25.082 1308-1541/? I/libprocessgroup: Successfully killed process cgroup uid 1000 pid 19150 in 11ms
2022-10-28 20:20:25.089 20654-22802/? E/AuthPII: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/login_manager
ywn: Long live credential not available.
at kyl.a(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):8)
at kyr.c(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):3)
...
2022-10-28 20:20:25.089 20654-22802/? E/AuthPII: Message is Long live credential not available.
ywn: Long live credential not available.
at kyl.a(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):8)
at kyr.c(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):3)
...
2022-10-28 20:20:25.089 20654-22802/? W/Auth: [GetToken] GetToken failed with status code: BadAuthentication
2022-10-28 20:20:25.095 20493-20756/? W/Auth: [GoogleAuthUtil] isUserRecoverableError status: BAD_AUTHENTICATION
2022-10-28 20:20:25.097 20654-31475/? E/AuthPII: [GoogleAccountDataServiceImpl] getToken() -> BAD_AUTHENTICATION. App: com.google.android.gms, Service: oauth2:https://www.googleapis.com/auth/login_manager
ywn: Long live credential not available.
at kyl.a(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):8)
at kyr.c(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):3)
...
2022-10-28 20:20:25.097 20654-31475/? E/AuthPII: Message is Long live credential not available.
ywn: Long live credential not available.
at kyl.a(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):8)
at kyr.c(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):3)
...
2022-10-28 20:20:25.108 20493-20756/? W/AsyncOperation: operation=List, opStatusCode=11005 [CONTEXT service_id=80 ]
OperationException[Status{statusCode=Error listing passwords, resolution=PendingIntent{2fb9331: android.os.BinderProxy@4dcca16}}]
at xox.c(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):14)
at xox.d(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):16)
....
Caused by: xny: Error listing passwords
at xrx.i(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):31)
at xtn.a(:com.google.android.gms<EMAIL_ADDRESS>(190400-481949630):45)

@thatfiredev Any update on this issue?

Any updates on a work-around or fix for this issue?
It's a gating issue for us as we have users unable to access the app/their data.
Thanks!

After @jftabord reproduced the bug on a demoFirebaseUI app and after we noticed the request was trying to access to credential at the Google Play Services/ Smart Lock
https://github.com/firebase/FirebaseUI-Android/blob/5b6c9f01f5a674d754d8e9b1242197fe040086e7/auth/src/main/java/com/firebase/ui/auth/data/remote/SignInKickstarter.java#L97-L121
We have found:

Deactive the Google Smart Lock   .setIsSmartLockEnabled(false) (true by default)  has solved the problem for our users. Here why:
The if block  statement has two conditions; I will omit the  willRequestCredentials because is normally true. The other one   getArguments().enableCredentials  is set by the<EMAIL_ADDRESS>which is also set by the Intent created by our apps.

So being the if block statement false the execution goes down through the method startAuthMethodChoice that returns the control to your app.
So basically, for some users, Smart Lock might fail and the Intent is not giving back control to the app that has launched it  (spinner rolling non-stop)  due to failures in the request.

@danielrrv Thanks for the info.
If the user disables smart lock is this a workaround?
Are you planning on pushing this change to FirebaseUI-Android , or did you just make the change for your app locally?
Thanks!

@neilpatrickadams update your app
com.firebase.ui.auth.AuthUI.getInstance()
.setIsSmartLockEnabled(false)
.setAlwaysShowSignInMethodScreen(true)

After @jftabord reproduced the bug on a demoFirebaseUI app and after we noticed the request was trying to access to credential at the Google Play Services/ Smart Lock
https://github.com/firebase/FirebaseUI-Android/blob/5b6c9f01f5a674d754d8e9b1242197fe040086e7/auth/src/main/java/com/firebase/ui/auth/data/remote/SignInKickstarter.java#L97-L121
We have found:
Deactive the Google Smart Lock .setIsSmartLockEnabled(false) (true by default) has solved the problem for our users. Here why: The if block statement has two conditions; I will omit the willRequestCredentials because is normally true. The other one getArguments().enableCredentials is set by the<EMAIL_ADDRESS>which is also set by the Intent created by our apps.
So being the if block statement false the execution goes down through the method startAuthMethodChoice that somehow returns the control to your app always.
So basically, for some users, Smart Lock might fail and the Intent is not giving back control to the app that has launched it (spinner rolling non-stop) due to failures in the request.

Life saver!

when smart lock is enabled and used to launch the sign in flow in 8.0.2 when there is no internet connection it runs off into a loop in the sign in activity and just gives a dim screen. Without smart lock when there is no internet connection the sign in provider flow pops up and reports snackbars check your internet connection as expected.

same issue on Samsung Galaxy tab A

when launches the sign-in intent i get stuck...with infinite loading (waiting 10 minutes and nothing appear).
in my code:
.setIsSmartLockEnabled(true)
.setAlwaysShowSignInMethodScreen(true)
.gradle:
implementation platform('com.google.firebase:firebase-bom:31.1.0')
implementation 'com.google.firebase:firebase-analytics-ktx'
implementation 'com.google.firebase:firebase-crashlytics'
implementation 'com.google.firebase:firebase-analytics'
implementation 'com.google.firebase:firebase-config'
implementation 'com.google.firebase:firebase-auth'
implementation 'com.google.firebase:firebase-firestore'
implementation 'com.google.firebase:firebase-storage'
implementation 'com.google.firebase:firebase-messaging'
implementation 'com.google.firebase:firebase-inappmessaging-display'

implementation 'com.firebaseui:firebase-ui-auth:8.0.2'
implementation 'com.firebaseui:firebase-ui-storage:8.0.2'

implementation 'com.google.android.gms:play-services-auth:20.4.0'

....
...
....

when i click on  back button
A sign-in error occurred.
                 v4.j: Unknown error
                 	at com.firebase.ui.auth.KickoffActivity.onActivityResult(SourceFile:66)
                 	at android.app.Activity.dispatchActivityResult(Activity.java:8316)
                 	at android.app.ActivityThread.deliverResults(ActivityThread.java:5237)
                 	at android.app.ActivityThread.handleSendResult(ActivityThread.java:5285)
                 	at android.app.servertransaction.ActivityResultItem.execute(ActivityResultItem.java:51)
                 	at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
                 	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
                 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2251)
                 	at android.os.Handler.dispatchMessage(Handler.java:106)
                 	at android.os.Looper.loop(Looper.java:233)
                 	at android.app.ActivityThread.main(ActivityThread.java:8068)
                 	at java.lang.reflect.Method.invoke(Native Method)
                 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:631)
                 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:978)

https://github.com/firebase/FirebaseUI-Android/issues/2067

If you have recently upgraded to AGP 8.0 or if you have enabled android.enableR8.fullMode=true then this might fix it for you:
https://github.com/firebase/firebase-android-sdk/issues/2124#issuecomment-920922929


boards: qemu_cortex_r5: Remove ignore tags for working tests

While the Cortex-R arch port does not currently support memory
protection and userspace, the memory_protection and userspace test
tags should not be ignored because doing so can unintentionally disable
other relevant tests.
Signed-off-by: Stephanos Ioannidis<EMAIL_ADDRESS>

what happened here? did something go wrong?

what happened here? did something go wrong?

@nashif "Scancode / Scan code for licenses (pull_request)" kept failing for some reason (probably a GitHub issue). #24290 includes this.


How to unfold DropdownButton menu only downward

This is my code for the DropdownButton menu:
import 'package:flutter/material.dart';
import 'package:percent_indicator/percent_indicator.dart';
import 'package:crypti/main.dart';

// TODO: Change place of Next button since keyboard will appear in screen normally
// TODO: force keyboard in screen (also in simulator)
void main() {
  runApp(MaterialApp(
    theme:
    ThemeData(accentColor: Colors.black87),
    home: ThirdRoute(),
  ));
}

class ThirdRoute extends StatefulWidget {
  @override
  _ThirdRouteState createState() => new _ThirdRouteState();
}

class Coin {
  int id;
  String name;

  Coin(this.id, this.name);

  static List<Coin> getCoins() {
    return <Coin>[
      Coin(1, 'Bitcoin'),
      Coin(2, 'Ethereum'),
      Coin(3, 'Ripple'),
      Coin(4, 'Litecoin'),
      Coin(5, 'EOS'),
    ];
  }
}

class _ThirdRouteState extends State<ThirdRoute> {

  List<Coin> _coins = Coin.getCoins();
  List<DropdownMenuItem<Coin>> _dropdownMenuItems;
  Coin _selectedCoin;

  @override
  void initState() {
    _dropdownMenuItems = buildDropdownMenuItems(_coins);
    _selectedCoin = _dropdownMenuItems[0].value;
    super.initState();
  }

  List<DropdownMenuItem<Coin>> buildDropdownMenuItems(List coins) {
    List<DropdownMenuItem<Coin>> items = List();
    for (Coin coin in coins) {
      items.add(
        DropdownMenuItem(
          value: coin,
          child:
          Text(
            coin.name,
            style: TextStyle(
                fontSize: 18.0,
                color: Colors.black87,
                fontWeight: FontWeight.bold
            ),
          ),
        ),
      );
    }
    return items;
  }

  onChangeDropdownItem(Coin selectedCoin) {
    setState(() {
      _selectedCoin = selectedCoin;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Stack(
        fit: StackFit.expand,
        children: <Widget>[
          Container(
            decoration: BoxDecoration(
                color: Color.fromRGBO(34, 139, 34, 0.4)),
          ),
          Positioned(
            top: 0.0,
            left: 0.0,
            right: 0.0,
            child: AppBar(
              backgroundColor: Colors.transparent,
              elevation: 0.0,
            ),
          ),

          Column(
            crossAxisAlignment: CrossAxisAlignment.start,
            children: <Widget>[
              Padding(
                padding: EdgeInsets.symmetric(vertical: 50.0),
              ),
              Padding(
                padding: EdgeInsets.fromLTRB(20.0,16.0,0.0,0.0), // left, top, right, bottom
                child: LinearPercentIndicator(
                  width: MediaQuery.of(context).size.width - 50,
                  animation: true,
                  lineHeight: 20.0,
                  animationDuration: 2000,
                  percent: 0.4,
                  center: Text("40.0%"),
                  linearStrokeCap: LinearStrokeCap.roundAll,
                  progressColor: Colors.greenAccent,
                ),
              ),
              Padding(
                padding: EdgeInsets.fromLTRB(40.0,16.0,0.0,0.0),
                child: Text("Select the coin you want to be paid in",
                  style: TextStyle(
                      fontSize: 35.0,
                      color: Colors.white,
                      fontWeight: FontWeight.w400
                  ),
                ),
              ),
              Padding(
                padding: EdgeInsets.fromLTRB(160.0,0.0,0.0,12.0),
                child: DropdownButton(
                  value: _selectedCoin,
                  items: _dropdownMenuItems,
                  onChanged: onChangeDropdownItem,
                ),
              ),
              Text('Selected: ${_selectedCoin.name}'),
            ],
          ),
        ],
      ),
    );
  }
}

Instead of having the DropdownButton menu unfolding both up and down, I would like to have it unfold only downward so it doesn't overlap the title on my screen. Current situation:

Could someone help me with this?


Fix broken az devops auth

Please make sure the code is following contribution guidelines in CONTRIBUTING.md

[ ] : This PR has a corresponding issue open in the Repository.
[x] : Approach is signed off on the issue.

@roshan-sy

can you take a look at this file https://github.com/Azure/azure-devops-cli-extension/blob/master/azure-devops/azext_devops/azext_metadata.json (and it's history) and see if we should update that as well ?
can you share the validation done for this pull request ?

I don't think it is a good idea to try every Azure CLI account, as this may cause unexpected user credential to be used.
Instead, only the default/selected (subscription, tenant, user) combination should be used to get an access token. If that token doesn't have access, we should explicitly switch account with az account set.

Maybe good next time to have a good PR description. Now it is not clear to me:

What was the original problem
What is the proposed solution
What are the test cases that are run

In my case I am still not able to use AAD authentication against Azure DevOps. Using az cli 2.30.0 and devops extension 0.22. Also see https://github.com/Azure/azure-cli/issues/20529

Maybe good next time to have a good PR description.

Completely agree.


🧹 remove defunct variable DISABLE_MD_LINTING

Changes
removes a dead variable from presubmit-tests.sh
/kind cleanup
Addresses: https://github.com/knative/hack/issues/200

Going to close & reopen to rerun checks

/assign @navidshaikh


Current error with VRC Creator Companion 3.1.11

Text format:
Packages\com.blep.vrc-expression-utility\Editor\Utility.cs(33,5): error CS0103: The name 'ImageDownloader' does not exist in the current context

Fixed ❤


Failed run android simulator : com.android.builder.testing.api.DeviceException: Timeout getting device list.

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:installDebug'.

com.android.builder.testing.api.DeviceException: Timeout getting device list.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug
option to get more log output.

BUILD FAILED
Total time: 1 mins 42.749 secs
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html
spent lot of time in setting up environment but now i am stuck here  , My emulator working fine appropriate build tools installed
Help !!

i think it's maybe the gradle script problem,i have't check this code .but you can follow this:
1.start your genymotion launch page,where you can creat your virtual devices.
Settings --> ADB --> Use custom Android SDK tools ,set the location you used before
2.restart genymotion and run adb devices,you will get the right devices,run react-native run-android
intresting! nothing changed yet,yes. you are right.then?
3.go to the project you just creat "AwesomeProject",goto app/build/outputs/apk,drag the app-debug.apk to the genymotion.now it works ,you can edit the index.android.js file,and double R on the genymotion,but now the react-native run-android still get Error.
hope someone can get the really problem
by the way my colleagues did'nt get this Error.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/failed-run-android-simulator-comandroidbuildertestingapideviceexception-timeout-getting-device-list
Product Pains has been very useful in highlighting the top bugs and feature requests:
https://productpains.com/product/react-native?tab=top
Also, if this issue is a bug, please consider sending a pull request with a fix.


Uploaded Images Show as Placeholder

Describe the Bug
Uploaded/inserted images are rendering as a placeholder image, both on the edit and saved page views.

Steps to Reproduce

Enter edit mode for a page.
Upload an image to the page via copy & past, drag & drop, or the Insert Image dialog.
Select image to insert (if using the Insert Image dialog)

Expected Behaviour
Uploaded images to render and be viewable in the browser.
Screenshots or Additional Context
The generated thumbnail is visible in the Insert Image dialog, however the generated scaled-1680- image renders as a placeholder.

Clicking on the image link attempts to open the original in another tab, but this again renders as a placeholder. However directly calling the thumbnail (https://site.domain/uploads/images/gallery/2022-08/thumbs-150-150/bookstacktest.JPG) is successful.

The browser dev tools networking tab suggest that the images are being served successfully.

The dev tools console shows no 404, or other errors.  However, the console in Edge does show the following warning.

(The link forwards to a chrome issue https://bugs.chromium.org/p/chromium/issues/detail?id=846170)
The original image, and the auto generated visions (scaled-1680- & thumbs-150-150), are all being correctly stored in storage/uploads/images/gallery/yyyy-MM/... , and display correctly when downloaded and viewed locally. They can also be successfully managed (e.g. deleted), from the in editor Image dialogue.
Browser Details
Firefox (103.0.2), Chrome (104.0.5112.81), Edge (104.0.1293.54), Opera (89.0.4447.91), Vivaldi (5.4.2753.33)
Exact BookStack Version
v22.07.1
PHP Version
8.0.17
Hosting Environment

BookStack Version: v22.07.1
PHP Version: 8.0.17
MySQL Version: 8.0
Webserver: nginx/1.14.2
OS: Debian GNU/Linux 10 (buster)

The site is hosted on an Azure App Service (Linux) instance, using the default PHP 8 container.
The site sits behind the default app service gateway/ssl proxy, and nginx has been configured to serve from the /public folder.
Images are configured to serve from local_secure storage, and the storage/uploads folder is mounted from an Azure storage file share - permission are broad for testing (0777 nobody/nogroup).
Auth is via the Azure AD third party authentication option.

Hi @MrMKJ,
Does this behavior occur for all types of images?
I'm wondering if this behavior could occur if an image was uploaded with an incorrect extension.
The image shown is named as "JPG" but appears to be a screenshot which would typically be png.
The thumbnails may work since they'd be specifically re-encoded as jpeg, to match the extension, during the upload process.

Hi @ssddanbrown
Thanks for getting back to me so quickly!
The reason I was uploading jpg was to try to test with formats other than PNG.
As you can see from the screen-shot below, the issue manifests for PNG & JPG - however for some PNG files the thumbnail is also not rendering.

Again the dev tools console shows no 404 errors, while networking suggests all images are being successfully served to the client.

Additionally, if I download the contents of the gallery locally, all the images - original and generated - are viewable.

Thanks for confirming @MrMKJ. Could you:

Share/attach the testpng.png file, just so I have an exact failing case to work with.
On one of the failing images, can you click the entry in the displayed network area of the devtools and share what the "Response" tab shows.

HI @ssddanbrown
The response tab shows no data for the request.

Here is the testpng.png file requested.

Sorry for the late response. I still cannot reproduce this. I think it's likely that certain webserver-level config is affecting things here.
Can you provide a full view of the cookie and header tabs for a failing image, obfuscating any key values within?

Hi @ssddanbrown
Thanks again for getting back to me on this issue!
Here are the headers & cookies tab screenshots you requested...

Additionally, as I didn't include it earlier, here is the nginx config...
server {
    #proxy_cache cache;
    #proxy_cache_valid 200 1s;
    listen 8080;
    listen [::]:8080;

    absolute_redirect off;

    root /home/site/wwwroot/public;
    index index.php index.html index.htm;

    server_name example.com www.example.com;

    client_max_body_size 100M;

	location / {
        try_files $uri $uri/ /index.php$is_args$query_string;
	}

    # redirect server error pages to the static page /50x.html
    # error_page   500 502 503 504  /50x.html;
    # location = /50x.html {
    #     root   /html/;
    # }

    # Disable .git directory
    location ~ /\.git {
        deny all;
        access_log off;
        log_not_found off;
    }

    # Add locations of phpmyadmin here.
    location ~ \.php$ {
        fastcgi_split_path_info ^(.+?\.php)(|/.*)$;
        fastcgi_pass <IP_ADDRESS>:9000;
        fastcgi_index index.php;
        include fastcgi_params;
        fastcgi_param HTTP_PROXY "";
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_param PATH_INFO $fastcgi_path_info;
        fastcgi_param QUERY_STRING $query_string;
        fastcgi_intercept_errors on;
        fastcgi_connect_timeout         300;
        fastcgi_send_timeout           3600;
        fastcgi_read_timeout           3600;
        fastcgi_buffer_size 128k;
        fastcgi_buffers 4 256k;
        fastcgi_busy_buffers_size 256k;
        fastcgi_temp_file_write_size 256k;
    }
}

I normally use the default Apache/php7.4 image, but this can be problematic for some Laravel apps, as it relies solely on htaccess files for the /public folder redirect, and offers no coinvent way of re-writing the the apache site config files - with the nginx/php8 image this can be achieved with a start-up script to re-write the site config.

Can't see anything wrong in the above. Thought it could be something specific to the nginx/php handling but I copied the config to my own environment and could not reproduce the issue.
Running out of ideas, almost feel like the connection is being dropped azure side before data is sent.
Could you maybe show the "Timing" tab for a non-working image request? Just to maybe get an idea of what might be happening to these requests.

Hi There,
I have the same issue, but for some reason it only happened to one of my pictures I included in my book. See Screenshot attached. I deleted the old pic, made a new screenshot, uploaded it and used this one instead of the old, broken one. Now it's working fine again. I am not sure why this problem came up with this one picture but not with others.

@nhmw-bnovak If it's reproducible feel free to open a new specific issue for your case.
Since there hasn't be a response for a while from the issue author I'm going to go ahead and close this off.


Use dynamic key mapping

One improvement to make here would be to not have the cycle., site., etc statically set in the code, as these are not actually the full list of potential keys. Currently in Hestia the different Node types can be found on https://www.hestia.earth/schema/ looking at the top-level entries in the menu. But this could evolve over time... so having a code that works on any kind of Node would be ideal

I adjusted the code and added two extensible dictionaries - one with the filter criteria to get the information per node, one with the sequential statements to merge the nodes. Of course, the dictionaries can be in separate files (e.g., with the full list of potential keys) that can be loaded into the code, but I wanted to keep it all in one place for now. Since I only have the input.csv and output.csv as examples to work with, I can only guess how well it will work with the entire dataset.


chore(main): release 2.156.2

:robot: I have created a release beep boop
2.156.2 (2024-12-10)
Bug Fixes

anchor button height (#4891) (7048c4c)
audit log integrations for versioned environments (#4876) (486bcd1)
pre-commit: refactor prettier hook (#4902) (cbecde7)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v2.156.2
:sunflower:


pythonPackages.lxml: 4.6.2 -> 4.6.3, addressing CVE-2021-28957

Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2021-28957
Haven't done a full re-eval yet, have a feeling I'm going to have to retarget this at staging..
Things done

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

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

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

The fix is basically the only patch in 4.6.2 -> 4.6.3, so can happily just cherry-pick to 20.09

/rebase staging

Haven't done a full re-eval yet, have a feeling I'm going to have to retarget this at staging..

Yep!  Rebased/retargeted now.

python38Packages.pandas builds for me on macos 10.14 (tested before the staging switch though)

Result of nixpkgs-review pr 117788 at 7b1807e8 run on x86_64-linux 1

742 packages marked as broken and skipped:

adobe-reader
adoptopenjdk-hotspot-bin-13
adoptopenjdk-hotspot-bin-14
adoptopenjdk-jre-hotspot-bin-13
adoptopenjdk-jre-hotspot-bin-14
adoptopenjdk-jre-openj9-bin-13
adoptopenjdk-jre-openj9-bin-14
adoptopenjdk-openj9-bin-13
adoptopenjdk-openj9-bin-14
agdaPackages.iowa-stdlib
...

19089 packages skipped due to time constraints:

AusweisApp2
EBTKS
EmptyEpsilon
Fabric
MIDIVisualizer
MMA
OSCAR
OVMF
OVMF-CSM
OVMF-secureBoot
...

21 packages built successfully:

cryptsetup
desktop-file-utils
fontconfig
gd
glib (gnome2.glib ,gnome3.glib)
gtk-doc (gnome2.gtkdoc)
gts
hidapi
libfido2
libusb1
libva-minimal
lvm2
openssh
python38Packages.fontforge
python38Packages.lxml
shared-mime-info
systemdMinimal
wayland
wayland-protocols
xlibsWrapper (xorg.xlibsWrapper)
xorg.libXft

@ofborg eval

manual probably fails because the mass rebuild.


Upgraded Python dependencies in HuggingFace HTTP server sample

Motivation and Context

Upgraded Python dependencies in HuggingFace HTTP server sample to address security issues.
Verified that HTTP server works as expected after dependencies upgrade.
Description

Upgraded joblib to 1.2.0.
Upgraded torch to 1.13.1.
Upgraded Pillow to 9.3.0.
Upgraded Werkzeug to 2.2.3.
Upgraded numpy to 1.22.

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

the diff is empty, just me?

Not sure what's wrong with the diff, but I checked out the pr and the dependencies matched the versions in the description.

@dluc @mkarle For some reason, GitHub doesn't catch requirements.txt diff, it thinks that it's a binary file. That's why I put list of upgraded dependencies and their versions in PR description.

Updated the requirements.txt to UTF-8, which git suddenly understood to be non-binary. Dependabot then picked up and resolved all the vulnerabilities. Closing this one, as I fear it might convert requirements.txt back to its original UTF-16 encoding.


Additional documentation

Address bash version in mac, document required dependencies in Ubuntu, and document an additional step for using credhub

I was able to confirm that bash 3.2.57 works with v0.7.0
But there is another issue, after bucc is installed (Using BUCC section) with 3.x, 4.x and 5.x still:
$ source <(bucc env)
/Users/dashaun/bucc/bin/bucc: line 312: echo: write error: Broken pipe

@dashaun Thanks


chore: update template to use Openshift 4 versions

This will also need to be done for the master branch(node 12), but we can do that when ubi node 12 comes out?
I don't think it makes sense to update node 8 since it is going EOL next month

We need to replicated that for all the examples including "-redhat" ?

Yea


Update CHANGELOG.md

update the changelog for the typo.

hmm, when I meant the changelog (for https://github.com/DLR-RM/stable-baselines3/pull/72), I meant the one in SB3 (cf CONTRIBUTING guide).


[🐞] service-worker.js pre-populates the cache for some bundles that are not present on the current page

Which component is affected?
Qwik Rollup / Vite plugin
Describe the bug
This is a bug first encountered in Qwik UI in preview and prod. It seems to me to be a build issue, not sure if it's Rollup, Vite or the optimizer.
When our application has multiple entry files and multiple context providers, it seems that the service worker starts fetching and pre-populating the cache for some bundles that are not needed on the page.

As showcased in the screenshot, I understand that the context.id-DK1jWIYg.js containing the "context-2" context is downloaded through the service-worker and placed in the cache for later use. Is this the intended behavior? I feel like Qwik should be smart enough to understand that context-2 is not needed on page /1, and therefore should only be loaded on page /2.
Reproduction
https://github.com/maiieul/qwik-service-worker-dowloads-external-bundles
Steps to reproduce

pnpm i
pnpm preview

System Info
System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M2
    Memory: 5.92 GB / 24.00 GB
    Shell: 3.7.0 - /opt/homebrew/bin/fish
  Binaries:
    Node: 21.7.3 - /opt/homebrew/bin/node
    npm: 10.5.0 - /opt/homebrew/bin/npm
    pnpm: 8.14.0 - /opt/homebrew/bin/pnpm
    bun: 1.1.0 - ~/.bun/bin/bun
  Browsers:
    Chrome: 124.0.6367.62
    Safari: 17.4.1
  npmPackages:
    @builder.io/qwik: ^1.5.2 => 1.5.2
    @builder.io/qwik-city: ^1.5.2 => 1.5.2
    undici: * => 6.13.0
    vite: ^5.1.6 => 5.2.9

### Additional Information

_No response_

Heads up 👆
The Qwik UI issue above (https://github.com/qwikifiers/qwik-ui/issues/719) might give more context on the consequences of this issue.

I had that issue because of Cloudflare cache I used. Are you using cloudflare?

@notcod I provided a reproduction that shows this behavior on pnpm preview. But we do encounter a related issue in qwik UI that might be caused by cloudflare.

I checked the code and it's working as expected.
generateLinkBundles is populating the system to prefetch bundles related to links.
I also found a dependency here, context.id imports are in the same file.
Anyway, that file will be download in any case because of the prefetch mentioned before.

So I'm closing this issue for now, feel free to re-open it if it's still an issue for you.
Thanks @maiieul

Thanks Giorgio for looking into this! I'm going to re-open because I think your screenshot actually also describes the issue here.
I don't think that

should be included on route /1, where this code isn't needed as far as I can tell.
In the reproduction, the context-ids code is written in separate files (e.g. https://github.com/maiieul/qwik-service-worker-dowloads-external-bundles/blob/main/src/routes/1/context.id.tsx). But even if it was written in the same file, it should be possible for Qwik to output each context related code into separate bundles, no?
This might not seem like a big issue on this reproduction, but on bigger apps it might mean downloading a lot more code than necessary. If it's only contextProvider code, then maybe it's not that big of a deal. But if it's code that touches context, then the leak could potentially lead to 2 or 3 times more code loaded on the client, and maybe even executed if there are visible tasks.

Can you try with the new service worker pls?

We had tried that on Qwik UI as well with Jack but that didn't change much. I'll try with the reproduction here.

Can you try with the new service worker pls? PrefetchGraph PrefetchServiceWorker

I tested with the latest Qwik code and the new Service worker and it's working correctly.
There is no evidence of "page 2 things" in the page 1 route and vice-versa.
So I'm closing this issue, more than happy to help you in the Qwik UI project for that.


Better close icon

Related: http://stackoverflow.com/questions/5353461/which-font-for-css-x-close-button
Looks equals but is different 😄

Thx


coqPackages.{ssreflect,mathcomp}: 1.6.1 -> 1.6.2

Motivation for this change
Things done

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

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

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

This breaks mathcomp for Coq 8.4:
nix-build-coq8.4-mathcomp-1.6.2.drv-0/math-comp-mathcomp-1.6.2/mathcomp/ssreflect/eqtype.v", line 3, characters 0-44:
Error: Cannot find library mathcomp.ssreflect.ssreflect in loadpath
make[1]: *** [Makefile.coq:404: ssreflect/eqtype.vo] Error 1

Indeed, this is an upstream regression. I reported it, a new release is going to happen in the coming days. I'll update this PR once it is available. Better not merge it until then.

Looks like there is now a 1.6.3 tag: https://github.com/math-comp/math-comp/releases/tag/mathcomp-1.6.3.
Does this fix the issue with Coq 8.4?

Math-Comp 1.6.4 has been released now.

Math-Comp 1.6.4 has been released now.

I don't think it's been announced yet, but maybe I missed it.

I don't think it's been announced yet, but maybe I missed it.

I don't follow the proper list to see the announcement, I think but coq/opam-coq-archive#220 has been merged. If it is in OPAM, I don't see why it shouldn't be in nixpkgs.

Indeed, I don't know why they didn't announce the release. Will update this today.

Superseded by https://github.com/NixOS/nixpkgs/pull/31354


Testing branch 3.2.0 gives black screen on android 6.0.0.

I noticed lots of PRs were merged on this branch and was trying to test it on our existing ionic app. The app launches fine but ends up with black screen. Dont see any console errors. For me looks like a css issue but our app works fine with this plugin repo from master branch.

Do you apply z-index on publishers or subscribers? If so the cams are behind the webview as described here: https://github.com/opentok/cordova-plugin-opentok/blob/3.2.0/docs/README.md#positioning-the-cameras-behind-or-before-webview

I dont have publisher / subscribers on home page. The ioinic view/page which has publisher and subscriber is not initialized.  A button navigates from home view to call view and the call view page initiates a call and hence the opentok session.

I think I understand it. When you start your app the homepage is black. This is because of a issue with the scrolling on Android. In this PR: https://github.com/opentok/cordova-plugin-opentok/blob/3.2.0/docs/README.md#positioning-the-cameras-behind-or-before-webview
We are working on a solution on this with a different scrolling mechnism. Therefore 3.2.0 is not yet released. If you would like to test it give the HTML body a fixed height in pixels.
Do not use 3.2.0 in production yet. As I said a solution will follow.

ok I will give it a try. Any idea when 3.2.0 will be ready to use?

@primashah @mark-veenstra and his team are working on some PRs so we will release 3.2.0 as soon as we have the scrolling fixed

@primashah are you still seeing the black screen?

Otherwise you can test this branch, it contains a different scrolling solution and removes the black screen issue (and other scrolling issues).
Do not use it in production since it will be deleted as soon as it is merged into the main branch/repository.

@mark-veenstra : I will test it some time and let you know.
@msach22 havent got chance to test again after creating this issue. As @mark-veenstra  is suggesting, I will try to test on the branch he recommends and post my observations here.

@ph-shah thanks for letting me know!

We tested 3.2.0 out and there were no issues. Please re-open and provide logs if issue persists


Next steps results in 404

The link Extend your subnet to Azure using vendor solutions. results in a 404.
I am unable to find the link in the Microsoft organization nor can I find "LISP" in the MicrosoftDocs org.

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

ID: c221d52e-1959-7c59-fbb4-2e7690d5ed03
Version Independent ID: ee419d0c-0243-d5b2-44fd-96857015b793
Content: Subnet extension in Azure
Content Source: articles/virtual-network/subnet-extension.md
Service: virtual-network
GitHub Login: @anupam-p
Microsoft Alias: anupand

@srjennings Thanks a lot for bringing this to our notice, our team will review it and fix the document accordingly.

Link is fixed.
#please-close

Thank you!!!
On Sat, Apr 30, 2022, 17:50 PRMerger16 @.***> wrote:

Closed #73579 https://github.com/MicrosoftDocs/azure-docs/issues/73579.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/73579#event-6528572148,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYYHEUWYPI5GTEQ7W2GGKPLVHW2LTANCNFSM42XWJ6FQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Please close Ren and npm as whale. Signedandsealed uJenny token @PRMerger16


Add Penetration Testing Books

What does this PR do?
Add resource(s)
For resources
Description
Penetration Testing Books
Why is this valuable (or not)?
It is a hand-on book on how to do penetration testing
How do we know it's really free?
it is available on internet
For book lists, is it a book? For course lists, is it a course? etc.
it is a book
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!

Fix #7909

this is the publisher: https://nostarch.com/pentesting
Not free. No Starch distributes DRM free books, which is great, support them.


Add missing PlayPropsConfig definition and some missing properties of…

Add missing PlayPropsConfig definition and some missing properties of the Sound object

@gyohk could you review this PR?

This fix seems no problem.
Thank you for correction.

@gyohk thanks!
@jsaelhof thanks mate!


HBASE-28923 Prioritize "orphan" blocks for eviction inside BucketCache.freespace (#6373)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 55s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
4m 39s

branch-2 passed

+1 :green_heart:
compile
3m 45s

branch-2 passed

+1 :green_heart:
checkstyle
0m 45s

branch-2 passed

+1 :green_heart:
spotbugs
1m 50s

branch-2 passed

+1 :green_heart:
spotless
0m 52s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 15s

the patch passed

+1 :green_heart:
compile
3m 35s

the patch passed

+1 :green_heart:
javac
3m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 43s

the patch passed

+1 :green_heart:
spotbugs
1m 57s

the patch passed

+1 :green_heart:
hadoopcheck
24m  0s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
1m 12s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 16s

The patch does not generate ASF License warnings.

50m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6416/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6416

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux e8fde922a0fe 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 54bb18768f430b55c8730bb2662a4f80a2cab6a0

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6416/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 35s

branch-2 passed

+1 :green_heart:
compile
0m 46s

branch-2 passed

+1 :green_heart:
javadoc
0m 26s

branch-2 passed

+1 :green_heart:
shadedjars
4m 52s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 24s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
javadoc
0m 26s

the patch passed

+1 :green_heart:
shadedjars
4m 49s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
250m  0s

hbase-server in the patch passed.

272m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6416/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6416

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 2b1494aacd3c 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 54bb18768f430b55c8730bb2662a4f80a2cab6a0

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6416/1/testReport/

Max. process+thread count
4466 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6416/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


[apply-login-partner-changes] - After build profile, the account verification step layout is broken at frontend

Describe the bug
Not able to read the validation screen after build profile is created
To Reproduce
Steps to reproduce the behavior:

Go to build profile, complete form, Save
Click on Login
Complete username and password
See screen is not clear, layout is broken, not readable

Expected behavior
Screen should be clear to user
Screenshots

fix UI @robert-dm

Fixed @eslamzaaki


Parameters sometimes are converted to strings, sometimes not

task.set_parameters(abc=123) // wrote an int
print(type(task.get_parameter("General/abc")))  // str
print(type(task.get_parameter("General/badparam", 456))) // int

This is completely counterintuitive. Whatever I write, I should always read the same, no casting to str.

Hi @iirekm,
You're correct - the current implementation always converts to string when storing in the backend, but when using get_parameter with a default value, it will not touch the default, simply return it as is.
I think it's more generic that way - what do you think?

It's not generic, it's very surprising. The generic way in python and any language except bash is using real objects, not strings.

Hi @iirekm
get/set parameters are kind of API level access (hence lack of type/casting).
A preferred way would be do to the following:
params = dict(abc=123)
task.connect(params)

This way when executed remotely and changing the argument 'abc' in the UI it will be converted back to integer,
A few more examples are here


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2730 ms

Resolved: Bofrost.at performance has improved in 8041a31 after 21 minutes.