rewrote all array prototype stuff to specific ROT.RNG methods

Hi again!  I took the time to remove the array prototypes that interfered and moved them into the ROT.RNG module instead.
The tests pass nicely - thank you so much for a very thorough test-suite!  ^_^

I am sorry for the time you wasted on this, but I am not going to accept this patch. For two reasons:

see https://github.com/ondras/rot.js/issues/83 for a more thorough discussion about why this adjustment is really not necessary,

you are introducing a compatibility-breaking change. There is quite some amount of rot.js-using code in the wild that relies on these prototypal enhancements; people are expecting this to work even if they update to a more recent rot.js version. We would be messing with a frozen API, something that is frowned upon hard.

I understand this, after your previous comment.
But at least I am happy and have a subsystem that does not interfere with
anything else while doing what it should.
If you get any other comments from people who might look for a similar
solution, please feel free to direct them to me.
On Sat, Jan 2, 2016 at 10:04 PM, Ondřej Žára<EMAIL_ADDRESS>wrote:

Closed #84 https://github.com/ondras/rot.js/pull/84.
—
Reply to this email directly or view it on GitHub
https://github.com/ondras/rot.js/pull/84#event-504044892.

Why not put this in a 1.0 branch?

Why not put this in a 1.0 branch?

Because I like the API as-is. Having the [a, b, c].random() is incredibly convenient. I intend to remove these methods only if they get standardized and replaced by a different official implementation.

It is accepted best practice to not modify core object prototypes. I have had problems with this as well and I know of at least 2 people that have had to modify rot.js to fix problems because of the methods added to the array prototype.
If you like adding methods to the Array prototype you should do that in project code, not in lib code intended to be used as a dependency by others.
Many js beginners use rot.js when learning js. It is doing them a disservice to have such poor practices in source code they are likely to learn from.
This is a trivial change that users of the lib should not have to undo themselves with their own branch of rot.

It is accepted best practice to not modify core object prototypes.

True. But the reason for this is to prevent naming collisions, not to clash with poor enumeration code. And I am willing to undertake the naming collision risk, as stated before.
(Note that this applies to Number.prototype.mod and String.prototype.{l,r}pad as well.)

I have had problems with this as well and I know of at least 2 people that have had to modify rot.js to fix problems because of the methods added to the array prototype.

Then perhaps you and those 2 people should have submitted an issue and discussed this problem? Fixing rot.js is a very poor solution and I am certain that there would be a better way to solve it.
Also, the fact that a solution was applied does not imply that the solution was good or that other solutions could not be better.

If you like adding methods to the Array prototype you should do that in project code, not in lib code intended to be used as a dependency by others.

Does this apply to polyfills for standard methods as well? Because these are regularly added to library code and noone is complaining. A logical consequence of this behavior is that the for p in arr iteration would be broken anyway. Iterating correctly is the way to go here.

Many js beginners use rot.js when learning js. It is doing them a disservice to have such poor practices in source code they are likely to learn from.

And my argumentation would be:

beginners use rot.js when learning js
I am fully aware of risks related to primordial prototype enhacements
with the knowledge of what and when might happen, I am pretty happy with the way these prototypes are enhanced
therefore, I am happy with how the code looks
therefore, I am happy if other write their code in the same manner
therefore, I am happy when beginners learn to follow this example (provided they understand what is really happening and going on under the hood)

This is a trivial change

The change, primarily, breaks backwards compatibility.

that users of the lib should not have to undo themselves with their own branch of rot.

Very true! They should fix their own code instead.
Please show me one particular example of a code that requires removing these enhacements from rot.js (and there is no other better way around).

Polyfills have a specified signature that should never change. If there is collision the behavior should be the same.
Example:
Using a lib that adds a Array.prototype.random method with a different signature or behavior than the rot.js implementation resulting in a collision.
With no standard specification for Array.prototype.random neither implementation can objectively argue to be more "correct", but one of them must be renamed and references refactored to avoid the collision.
I think the best solution to this problem would be to make a trivial change to the lib preventing this from being possible at all.
If you are pushing a point release breaking changes are inferred and previous versions remain accessible via npm.

:+1: To not catering to folks who want to enumerate improperly.

With no standard specification for Array.prototype.random neither implementation can objectively argue to be more "correct", but one of them must be renamed and references refactored to avoid the collision.

To quote myself from the #83:

As soon as the random or randomize methods get standardized, I will immediately remove my own variants from Array.prototype (as long as they differ from the official version)

The same also applies to the hypothetical scenario of another library implementing Array.prototype.random with a different signature and/or semantics.
Now the fun part is that rot.js is now almost four years old -- and yet I have never encountered a single naming collision with respect to primordial prototype enhancements.

I think the best solution to this problem would be to make a trivial change to the lib preventing this from being possible at all.

I think there really is no problem so far. Let's seek problem solutions aftery the problems arrive.


Add AppEngine pipeline tests

This PR adds AppEngine test data and the pipeline tests.

Thanks for the review. I have added a simple test for appengine.py.

Adding cla: yes label, as the PR & commit authors are googlers at the time of this PR was created.


Version 1.0.5 Does not parse logs for spark 2.1.0

Running the spark job (spark version 2.1.0) using --package successfully launches the sparklint server, but the sparklint server does not provide any information about how the job is running. It is stuck at "Completed 0/0" for the duration of the job.

User error, must forward through events in the new version.


activation, kernel, bias are all attributes in Dense

Current documentation only says Dense implements such math operation. It's unclear to user how to access kernel and bias.
It turns out, through reading the code, these are all attributes added in this layer.
kernel and bias are added in build(), while activation is added in the constructor.

@fchollet fixed


Kubean image missing vulnerabilities check

Describe the version
version about:

kubean

Describe the bug
Kubean image missing vulnerabilities check
How To Reproduce
Using trivy scan related images
Expected behavior
No HIGH & CRITICAL vulnerabilities
Screenshots and log

Additional context
Ref: https://github.com/kubean-io/kubean/actions/runs/4921965903/jobs/8792697667

/kind feature

fix by

https://github.com/kubean-io/kubean/pull/719
https://github.com/kubean-io/kubean/pull/721


Not work properly in device

After app uninstall from simulator if I install it again it provide only black layer


Controller Manager not auto-reconnecting

Controller Manager does not auto-reconnect to a PLC.  When reading a value, it retains the value from before the download and will not update.
Current Behavior

After a download to a PLC, tags are no longer read from that PLC.
Expected Behavior

Tags should resume polling from that PLC.
Possible Solution (Optional)

Context

Steps to Reproduce (for bugs only)

Your Environment

Package version (Use npm list - e.g. 1.0.6): 2.6.7
Node Version (Use node --version - e.g. 9.8.0):
Operating System and version:
Controller Type (eg 1756-L83E/B): 1756-L63 / 1756-L73
Controller Firmware (eg 30.11): 16.23 / 30.11

My temporary workaround:
setInterval(async function () {
let tagValues = cm.getAllValues();
let heartbeat = cont.tags.find(o => o.tagname === 'Heartbeat').tag.state.tag;
console.log(heartbeat.value);
if (heartbeat.value == false) {
console.log("Restarting connection...");
cont.connect();
}
heartbeat.value = false;
}, 5000);
In the PLC, I just have a single rung for 'OTE(Heartbeat);'

I was able to duplicate the issue. After power cycling it will reconnect, but after download it doesn't.  I will see if I can figure out a fix.

Thanks Jason.  Glad I was able to find a way to break it.   Haha

New version should fix

Thanks Jason.  I'll give it a shot tomorrow.


Error calling wasm function with complex object as argument

Describe the bug
I came up against an issue when developing a Vite 3 based project that calls a wasm function that passes a complex object (an array of arrays of numeric values) from the JS world into the wasm.
Vite seems to have a problem binding to the JS code generated by wasm-build, which results in the following error message being shown in the browser console:

Uncaught (in promise) TypeError: WebAssembly.instantiate(): Import #0 module="./hello_wasm_bg.js" error: module is not an object or function

I have created an example project to illustrate this.
Please let me know if this is a bug, or if the error is my own.
Many thanks!
Reproduction
https://github.com/grahamdaley/vite-wasm-test
System Info
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1 Pro
    Memory: 175.95 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.19 - ~/.yarn/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
  Browsers:
    Chrome: 105.0.5195.125
    Safari: 16.0
  npmPackages:
    @vitejs/plugin-vue: ^3.1.0 => 3.1.0
    vite: ^3.1.0 => 3.1.3

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[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] 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 vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

wasm-pack build ./src/hello_wasm --target bundler generates a code that uses ESM Integration Proposal for Wasm. Because this proposal is not yet stable, it's not supported by Vite. (This feature request is tracked at #4551.)
Using vite-plugin-wasm or using --target web will work.

I tried using --target web but it resulted in a slightly different error message:
Uncaught (in promise) TypeError: WebAssembly.instantiate(): Import #0 module="wbg" error: module is not an object or function

I would have used vite-plugin-wasm, but it seems it's not suitable for my particular use case, which needs the wasm calls to be made from within a web worker.

For both --target bundler and --target web, you'll need to import the generated JS file instead of wasm file.
This is because wasm-pack generates a glue code and the generated wasm file requires that.
https://github.com/grahamdaley/vite-wasm-test/blob/aab063da86737bf8a4db85cf39002a3ac25e255b/src/components/HelloWorld.vue#L3

That works perfectly! Thank you so much for your help, @sapphi-red!


Add CHANGELOG to the project

I think it would be very useful for all the users to have a CHANGELOG to know well what changes from one version to the next. Paella 6 already included it and it was very nice :)

The document you are looking for is in doc/improvements.md, which is also accessible from the project website:
https://paellaplayer.upv.es/#/doc/improvements.md
In this document only new APIs, modifications to existing APIs and fixes to particularly serious bugs will be published.


Update licese year

Summary
This pull request updates the year in the LICENSE file.

Current coverage is 70.93% (diff: 100%)

Merging #146 into master will not change coverage

@@             master       #146   diff @@
==========================================
  Files           130        130
  Lines          6650       6650
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           4717       4717
  Misses         1933       1933
  Partials          0          0

Powered by Codecov. Last update 1c9941d...188565a


Generate 3d probe-and-validate wrapper functions

With this PR, 3D can now generate, for a given type T, an unverified wrapper calling a probing function f on an address a and then calling the validator for T on the memory area probed by f.
If for instance in MyModule.3d the user writes:
extern probe f

entrypoint probe f 8
typedef struct _T {
  ...
} T;

Then EverParse/3D generates into MyModuleWrapper.c and MyModuleWrapper.h, in addition to the ordinary MyModuleValidateT validator wrapper function, a probe-and-validate wrapper function:
boolean MyModuleValidateTProbef (EVERPARSE_COPY_BUFFER_T probeDest, UINT64 probeAddr);

This probe-and-validate wrapper function takes:

a destination buffer, probeDest, that still needs to be provided by the caller
the address value probeAddr, directly (so no need for an extra “fake input buffer” indirection)

When called, the probe-and-validate wrapper function calls the f probing function and, if probing succeeds, calls the T validator on the probed buffer.
The syntax of the entrypoint probe attribute is:
entrypoint probe probeFunctionName size

where the size argument, giving the number of bytes to probe, is either an integer literal or a global integer variable defined with #define. The value of size must be at most a 32-bit unsigned integer.

Thanks Tahina! A few things we discussed:

[ ] Let's make it (length=8), so that it's more explicit and matches the existing probe syntax.
[ ] It would also be nice if instead of a constant or defined symbol, it could also be sizeof(T)
[ ] The name of the wrapper should be MyModule[f]ValidateT, typically this would produce MyModuleProbeAndCopyValidateT
[ ] Aside from these cosmetic things, it would be great if the generated .h file only includes the probing version of the entrypoint, since the non-probing one would be unsafe to call with a user pointer.


gapic-generator does not understand projects

Many GCP APIs have the (shared) concept of a project, which is at the top of the hierarchy for most GCP resources.
Accordingly, the GAPIC config often has a block that looks like this:
  collections:
  - entity_name: project
    language_overrides:
    - language: csharp
      common_resource_name: Google.Api.Gax.ResourceNames.ProjectName

Generating C# with this block crashes with the error described here: https://github.com/googleapis/google-cloud-dotnet/issues/3423
Generating C# with this block removed (which would be a problem for them; the override matters) crashes with a different error:
ERROR: toplevel: Reference to unknown type "cloudresourcemanager.googleapis.com/Project" on field google.cloud.phishingprotection.v1beta1.ReportPhishingRequest.google.cloud.phishingprotection.v1beta1.ReportPhishingRequest.parent

P0: We either need generating with this YAML block to work correctly in all languages, or we need to be able to remove the block completely and have the generator do the correct thing whenever it encounters a project (if choosing between them, removal is better,  but the P0 is to get this working)...
P1: ...or org, folder, or billing account.

Fixed by #2979.


Initial interfaces

Consists of the initial interfaces that make up this library: BlueprintInterface, BuilderInterface

I like this. This is what I'd do.


JEST - Fail to mock react-native-camera

I am mocking react-native-camera component in react-native-camera.js file under _ mocks _ folder:
import React from 'react';
const constants = {
    Aspect: {},
    BarCodeType: {},
    Type: {},
    CaptureMode: {},
    CaptureTarget: {},
    CaptureQuality: {},
    Orientation: {},
    FlashMode: {},
    TorchMode: {},
};

class Camera extends React.Component {
    static constants = constants;
    render() {
        return null;
    }
}

Camera.constants = constants;
export default Camera;

my package.json is:
{
    "name": "myApp",
    "version": "0.0.1",
    "private": true,
    "scripts": {
        "start": "node node_modules/react-native/local-cli/cli.js start",
        "lint": "eslint src",
        "test": "jest --runInBand",
        "test:coverage": "jest --coverage --runInBand",
        "build:unsigned:apk": "cd android && ./gradlew clean && ./gradlew assembleRelease -console plain"
    },
    "dependencies": {
        "jsrsasign": "^8.0.4",
        "lodash": "^4.17.4",
        "prop-types": "^15.6.0",
        "react": "16.0.0-alpha.12",
        "react-dom": "16.0.0-alpha.12",
        "react-native": "0.48.4",
        "react-native-camera": "^0.10.0",
        "react-native-communications": "^2.2.1",
        "react-native-datepicker": "^1.6.0",
        "react-native-i18n": "^2.0.9",
        "react-native-progress": "^3.4.0",
        "react-native-push-notification": "^3.0.1",
        "react-native-vector-icons": "^4.4.2",
        "react-native-video": "^2.0.0",
        "react-navigation": "^1.0.0-beta.15",
        "react-redux": "^5.0.6",
        "redux": "^3.7.2",
        "redux-thunk": "^2.2.0",
        "reselect": "^3.0.1"
    },
    "devDependencies": {
        "babel-eslint": "8.0.1",
        "babel-jest": "21.2.0",
        "babel-preset-react-native": "4.0.0",
        "enzyme": "^3.1.0",
        "enzyme-adapter-react-16": "^1.0.2",
        "eslint": "4.10.0",
        "eslint-config-airbnb": "16.1.0",
        "eslint-plugin-babel": "4.1.2",
        "eslint-plugin-import": "2.8.0",
        "eslint-plugin-jsx-a11y": "6.0.2",
        "eslint-plugin-react": "7.4.0",
        "jest": "21.2.1",
        "jest-teamcity-reporter": "^0.7.0",
        "react-test-renderer": "16.0.0-alpha.12",
        "redux-mock-store": "^1.3.0"
    },
    "jest": {
        "preset": "react-native",
        "transformIgnorePatterns": [
            "node_modules/(?!(jest-)?react-native|react-navigation)"
        ],
        "setupFiles": [
            "<rootDir>/test/globalFetch.js",
            "<rootDir>/test/jestSetup.js",
            "<rootDir>/__mocks__/react-native-i18n"
        ]
    }
}

I am trying to run a basic test in jest:
import 'react-native';
import React from 'react';
// Note: test renderer must be required after react-native.
import renderer from 'react-test-renderer';
import Index from '../index.android';

import * as mockCamera from '../__mocks__/react-native-camera';
jest.mock('react-native-camera', () => mockCamera);

it('renders correctly', () => {
    const tree = renderer.create(<Index />);
    expect(tree).toMatchSnapshot();
});

I am getting this error message:
Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object. You likely forgot to export your component from the file it's defined in.
at invariant (node_modules/fbjs/lib/invariant.js:42:15) at createFiberFromElementType (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1855:5)
at createFiberFromElement (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:1800:15)
at reconcileSingleElement (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:3172:19)
at reconcileChildFibers (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:3282:37)
at reconcileChildrenAtPriority (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:3925:30)
at reconcileChildren (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:3903:5)
at updateHostRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:4078:7)
at beginWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:4434:16)
at performUnitOfWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:6030:16)

@assafb81
I guess because your index.android.js it's not export component
It just call AppRegistry.registryComponent
My index.android.js
import { AppRegistry } from 'react-native';
import App from './App';
AppRegistry.registerComponent(Appname, () => App);

Change to Import ./App on your test file for test

you should mock react-native-camera to work with jest
example
mocks/react-native-camera.js
const Camera = {};
export default Camera;


fix: VULN-3698 address vulnerability in okio library

PR Description
This is to fix vulnerability (CVE-2023-3635) detected in com.squareup.okio:okio:1.15 library in hashicorp-key-vault modile. More details about the vulnerability here https://avd.aquasec.com/nvd/cve-2023-3635
Fixed Issue(s)

To  fix vulnerability (CVE-2023-3635) com.squareup.okio:okio::3.12.3 library was upgraded to 4.9.2  in hashicorp-key-vault

Documentation

Documentation is not required to be updated

Not required. Was already addressed by another pull request.


Add missing tf.tanh() tests for SparseTensor

More information in comment here. Tested locally.

Can one of the admins verify this patch?


Changing the datepicker value by manually typing date creates issues

Hi,
We have added a datepicker on our webpage which is defaulted to today's date. When I start clearing the date value using keyboard (using backspace button or by start typing the date) , date picker does let me pick the new date value, but does not display the newly selected value in the datepicker. Model changes with new dates selected, but datepicker does not reflect the change.

Hey, thanks for the report. I think I've managed to reproduce the issue too, though with slightly different steps. It seems to be due to the use of defaultValue (itself recently introduced in #58 to fix an issue with Elm overloading on quickly typed input text). The logic in the code seems fine, but it seems like the input's value property is not updating, even though its value attribute is. The property remains stale, and thus picking does not update the text!
This is pretty arcane/strange. I'm not yet sure what causes the property to be retained, even when I try to force keyed to replace the element.
If I revert defaultValue to value, this problem clears up, but I don't want to undo the PR just yet. @mbylstra, if you have a moment, did you run into anything during your investigation of defaultValue that might explain this? Not blaming you for the change or anything; it's a pretty subtle problem :).

Hi, I saw this issue when it was opened and did immediately think PR #58 must have introduced it. However, when I checked out an earlier version locally and rebuilt and tested the example in examples/simple, I was still seeing the problem, so I assumed this was a prior issue. Turns out I must have been looking at the Browser's cached version of #58 :sweat:
I'm happy for you to revert #58 to fix this issue. This seems like a worse issue than the one #58 attempted to solve. I've opened issue #63 to keep track of the dropped characters issue.
It'd be great if there were regression tests, but these problems are so browser specific that something like Browser Stack would be required. Browser Stack is free for open source projects but would likely require considerable effort to set up and maintain. I'll have a look into it though.
I'll see if I can find a better solution for issue #63.

For what it's worth, you can augment the workaround in #58 with the same idea used for resetting value in the original workaround - using a counter that is updated when a date is actually selected, which will the render a new node for the input field, hence re-applying the defaultValue.
This is unlikely to play nice with focus, though. 🤔

I believe this has been fixed in #65. @genericarati do you mind confirming on version 7.2.3?

(Provisionally closing)


Pygments.rb Dependency Docs

jekyll serve threw errors about the Pygments dependency until the gem was installed.

:+1:  Thanks for catching this @TheConnMan. In the long run, I think we should use a Gemfile ala https://github.com/cfpb/regulations-schema/blob/gh-pages/Gemfile. In the meantime, this is certainly needed.


touchtimer: FIX countdown buzz to be in last 5 seconds

The countdown buzz was happening on each minute and not only on the
last 5 seconds

Thanks!


Simplify job names when using matrices

The docs are unclear on if ${{ matrix.env.environment_name }} would be available for job names. If it works in CI, it should also work in deployments.
This is an attempt to simplify

to show

Build and Deploy (cpy)

instead.

Hey! It worked!

To make this interface nicer, I'm tempted to switch it to use / instead of ( ):

Does anyone have an opinion between / and ( )? I'm open to some brief bikeshedding.


add nanoId function to string module

What is 'nanold' function⁉

it's unique identifier like uuid but simpler and more human-readable, example: https://www.npmjs.com/package/nanoid

fakerjs: https://github.com/faker-js/faker/blob/4a8499a1630444ea5b2463cf3e2d687db6980428/src/modules/string/index.ts#L723

Hello, sure go ahead :) assigned


Manually call right-operand version of binary ops to preserve error message

#12454
import tensorflow as tf
x = tf.get_variable('asdfds', shape=[10], dtype=tf.int32)
x*0.5

used to print:
TypeError: unsupported operand type(s) for *: 'Variable' and 'float'

It now prints:
TypeError: Expected int32, got 0.5 of type 'float' instead.

@ppwwyyxx Could you add more test cases?

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

Nagging Reviewer @yifeif, @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @yifeif, @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @yifeif, @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 44 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 31 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @skye: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 46 days with no activity and the awaiting review label has been applied.

@skye Could you PTAL and approve.

I agree with @wt-huang , can you add a test case or two demonstrating the new behavior?

This issue was fixed in 2da8e8c60343d9e833f1c591c54ee2a27c240842 (though not yet made into any official release).


⚠ Bofrost.be has degraded performance

In ee84f40, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1287 ms

Resolved: Bofrost.be performance has improved in f1b6391 after 6 minutes.


Updated toInterval to allow Timing

Updated prevalenceInterval to include abatement date in the prevalence interval

Change looks good and works with existing code replacing the previous temporary function


Fix that db dumps cannot currently be restored as-is

Issue 1) Due to dependency ordering
Specifically: The problem stems from the cached-tsvector columns referencing utility functions, which pg-dump is placing after the table-creation lines in the sql dump.
Another solution to this may be to simply get rid of those auto-generated columns, and use the (slightly modified) indexes for that purpose.
Issue 2) Due to search-path config not getting exported as part of dump

As of 2023-04-03, the dependency-ordering issue did not seem to be a problem; I did a restore from a logical backup just fine without messing with cached-tsvector columns <> table-creation conflicts or the like.


[Dependency] Latest CK build is taking very long time

if we update CK dependency (this line): https://github.com/ROCmSoftwarePlatform/MIOpen/blob/fd143e601ff760e09a7866c161d8a4289f09376f/requirements.txt#L9
to
ROCmSoftwarePlatform/composable_kernel@4e911f3ee05af375ce6e5757eee6a6435f2293c6 -DGPU_TARGETS="gfx900;gfx906;gfx908;gfx940;gfx90a;gfx1030;gfx1100;gfx1101;gfx1102"

the dependency build time increases very significantly.
Even though dependency build is one-time only, CK team needs to take a look at the build profiling. Is it the same issue we have discussed about? i.e. compiler register allocation strategy using eager mode?

Yes, this is compiler issue. Or CK issue at least;)

I think we have a relatively good understanding of what's going on by now.
See the details in the ticket below:
https://ontrack-internal.amd.com/browse/SWDEV-403889
First, the greedy register allocator takes forever to process several int8 instances on all platforms.
Second, on gfx11 this issue is further aggravated by the failure to vectorize many read and write instructions.
Thus, current build times for gfx9/gfx10 architectures are around 40 minutes and around 15 hours for the gfx11 architectures.
The compiler team is looking for fixes to both of these.
Once the issues are fixed, the anticipated build times for each architecture are around 10-12 minutes.
In the meantime, I'm working on adding an option to build CK only for select data types. This would allow us not to build int8 instances on gfx11 architectures and avoid the long build times until the greedy register allocator fix is available.

With the latest changes, when we skip building the tests, examples, ckProfiler, int8 and dl instances, CK builds for all gpu targets in about 30 minutes. Once the compiler fix is available, we can also start building int8 instances with no penalty.


Unable to set up an Azure workspace

System Information:

Model Builder Version: 16.13.10
Visual Studio Version: VS2022 17.3.6 (and 17.4.0)

Describe the bug

On which step of the process did you run into an issue: When trying to select an Azure workspace for Object Detection model training.
Clear description of the problem: When opening the Azure Machine Learning - Create new experiment window, a bunch of error messages pop up, and the window itself if broken to the point where it doesn't accept any user input.

To Reproduce
Steps to reproduce the behavior:

Create a new MBConfig
Select Object Detection
Click on Set up workspace
See error

Expected behavior
Well, for me to be able to set up a workspace.
Screenshots

(Note that I do have a subscription and the buttons do not work.)
Additional context
MLModel1-YCD1Y9.txt

Nvm, it seems like I actually did have to re-enter my credentials, but I'm still leaving this issue open as I'm pretty sure the error messages shouldn't be there.


Can't disable pop-up keyboard in whole app on Android for BasicTextField

How to disable pop-up keyboard in Android, I tried to do it for 2 hours and useless (through manifest and activity), I'm making calculator and I don't need system pop-up keyboard, but I need BasicTextField component due to cursor.

Hum. Can't you disable popup when a physical keyboard attached?

Hum. Can't you disable popup when a physical keyboard attached?

Sure, I wanna disable popup physical keyboard in android BasicTextField to keyboard won't pop up when I click on BasicTextField, but I haven't found this parameter in function

It seems to be unrelated to Compose Multiplatform.
Though using my Google skills I found:

Disable virtual keyboard as system wide setting: https://support.honeywellaidc.com/s/article/CN51-Android-How-to-prevent-virtual-keyboard-from-popping-up

Disable programmatically:
https://stackoverflow.com/questions/1109022/how-to-close-hide-the-android-soft-keyboard-programmatically#:~:text=You can force Android to,window containing your focused view.&text=This will force the keyboard to be hidden in all situations.


Fix followers calling leader-set when using keystone

configure_cdk_addons is only supposed to be called by leaders, but regenerate_cdk_addons was giving followers a back door into it.
The configure_cdk_addons handler runs on every hook anyway. Fix this by removing regenerate_cdk_addons.

won't this delay the configuring of cdk-addons for, at most, 5 minutes?

It shouldn't. When the keystone-policy or keystone-ssl-ca configs change, Juju will immediately run the config-changed hook on all of the kubernetes-master units. That will run all the reactive handlers whose flag conditions are met.
If you look at the flag conditions for the configure_cdk_addons handler:
https://github.com/charmed-kubernetes/charm-kubernetes-master/blob/9ccd758a571034b6a66e6d74e30ff1038559843e/reactive/kubernetes_master.py#L928-L932
You'll see that

On the leader, leadership.is_leader is always set.
In the case we're concerned about, keystone-credentials.available.auth is set. (otherwise, regenerate_cdk_addons would not have run anyway)

That's enough to meet the conditions. So, it'll run on the config-changed hook, using the new config values, without having to wait for a later update-status hook or whatever.

@Cynerva thanks, I always forget that a config change will cause a hooks run. I get caught up in the @when flags and incorrectly think that only things that call out that config will run.


Fix TVM load

Codecov Report

Merging #405 (2f6bea9) into main (ef43692) will decrease coverage by 6.20%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #405      +/-   ##
==========================================
- Coverage   90.76%   84.56%   -6.21%
==========================================
  Files          62       62
  Lines        3757     3763       +6
  Branches      721      723       +2
==========================================
- Hits         3410     3182     -228
- Misses        183      419     +236
+ Partials      164      162       -2

Flag
Coverage Δ

unittests
84.56% <0.00%> (-6.13%)
:arrow_down:

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

Impacted Files
Coverage Δ

hummingbird/ml/_container.py
68.34% <0.00%> (-20.17%)
:arrow_down:

hummingbird/ml/_utils.py
83.96% <ø> (-3.91%)
:arrow_down:

...mmingbird/ml/operator_converters/sparkml/linear.py
42.85% <0.00%> (-57.15%)
:arrow_down:

...bird/ml/operator_converters/sparkml/discretizer.py
47.36% <0.00%> (-42.11%)
:arrow_down:

hummingbird/ml/convert.py
66.82% <0.00%> (-16.83%)
:arrow_down:

hummingbird/ml/_topology.py
70.07% <0.00%> (-14.79%)
:arrow_down:

hummingbird/ml/_parse.py
75.78% <0.00%> (-10.07%)
:arrow_down:

...ml/operator_converters/sparkml/vector_assembler.py
90.00% <0.00%> (-10.00%)
:arrow_down:

...l/operator_converters/_pipeline_implementations.py
60.00% <0.00%> (-10.00%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Iphone - Registering with an email that has a space after the .com. breaks the setting screen

Repro steps

Register using<EMAIL_ADDRESS>'
Go to settings

Expected Result
Everything works, space is trimmed or email validation error is shown and the user has to remove the space themselves while registering.
Actual Result
Every time the user goes to settings, the app closes
System Info

This input is now properly sanitized. Should not happen anymore.


Create CODE_OF_CONDUCT.md

Deploy preview for govuk-react processing.
Building with commit 8fbd6bbd6209df06b9fea9258ab74f927fef3a0c
https://app.netlify.com/sites/govuk-react/deploys/609fdbc44c32ee000787fe00

Codecov Report

Merging #773 (8fbd6bb) into master (a7d0db2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #773   +/-   ##
=======================================
  Coverage   99.30%   99.30%
=======================================
  Files         121      121
  Lines         858      858
  Branches      248      248
=======================================
  Hits          852      852
  Misses          6        6

Continue to review full report at Codecov.

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


Chore/file reorg

This PR renames the PortManager to PortMapper, and reorganises files in preparation for implementing types and components common to the execution engine and bundle server.
See commit log

The change to gitignore was committed in https://github.com/input-output-hk/smart-contract-backend/pull/72/commits/729ce0bc2104037bc459c3318f1e63e6f2c6628e


Part list misses thumbnails

https://library.ldraw.org/tracker/list
misses the column with the thumbnails

This is implemented.


Kubernetes - Use initContainer instead of another container as source volume

It's better doing it that way because it's not necessary to wait for the files to become available (as seen here: https://github.com/SocketCluster/socketcluster/blob/5226c2a/sample/dockerwait.js).
Example of how it would work:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: my-project-scc
spec:
  replicas: 2
  revisionHistoryLimit: 2
  template:
    metadata:
      labels:
        app: my-project-scc
    spec:
      initContainers:
        - name: src-container
          image: myuser/sourceimage
          command:
            - cp
            - '-a'
            - /usr/src/.
            - /usr/dest/
          volumeMounts:
            - mountPath: /usr/dest
              name: src-volume
          resources:
            limits:
              cpu: 10m
              memory: 50Mi
            requests:
              cpu: 10m
              memory: 50Mi
      containers:
        - name: socketcluster
          image: 'socketcluster/socketcluster:v14.3.0'
          ports:
            - containerPort: 8000
          env:
            - name: SCC_STATE_SERVER_HOST
              value: my-project-scc-state
            - name: SCC_INSTANCE_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            - name: SOCKETCLUSTER_WORKER_CONTROLLER
              value: /usr/src/app/worker.js
            - name: SOCKETCLUSTER_MASTER_CONTROLLER
              value: /usr/src/app/server.js
            # ... other envs
          resources:
            limits:
              cpu: 100m
              memory: 360Mi
            requests:
              cpu: 100m
              memory: 360Mi
          livenessProbe:
            httpGet:
              path: /health-check
              port: 8000
            initialDelaySeconds: 300
            timeoutSeconds: 5
          volumeMounts:
            - mountPath: /usr/src/app
              name: src-volume
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: app
                    operator: In
                    values:
                      - my-project-scc
              topologyKey: kubernetes.io/hostname
      volumes:
        - name: src-volume
          emptyDir: {}

The container is only started when the init container has finished. I was using that until recently, having both as normal containers can cause some problems, and having to set the wait timeout to bigger values each time newer dependencies are added.
Recently I've ditched this deployment in favor of building my own socketcluster image with the correct dependencies already installed, since copying node_modules from the image to the volume was taking too long (almost 20 mins). But it's here as a suggestion.

@JCMais Thanks for pointing this out. I'll investigate this solution.

Yea, I need to start using initContainer. I haven't started using it yet. I was going to on my next project. Thanks for the example!


Manual dispatch in DragDropActions#drop()

I noticed you're manually calling the dispatcher in DragDropActions#drop(). https://github.com/gaearon/dnd-core/blob/master/modules/actions/DragDropActions.js#L90
Couldn't you instead dispatch all the dropResults at once? Or, if you need to do each one at a time, call a separate action instead of the raw dispatch method?
So instead of this
targetHandles.forEach((targetHandle, index) => {
  ...
  this.dispatch(dropActionId, { dropResult });
});

you could do this
const dropResults = targetHandles.map((targetHandle, index) => {
  ...
  return { dropResult };
});

return { dropResults };

or this
targetHandles.forEach((targetHandle, index) => {
 ...
 this.dropSingle(dropResult);
});

// elsewhere in DragDropActions class
dropSingle(dropResult) {
  return { dropResult };
}

If neither of these are options, I'd be curious to know why so I can address in Flummox.

Btw I'd be happy to submit a PR if you like.

I want the current drop result to be available in Store on each iteration. When I make that target.drop call in the cycle, it might read from the Store.
I'm not super happy about it. While your second approach could work, I think the problem is me being lazy.
The correct approach would be to let context be aware of the “ephemeral” drop target value so when we call target.drop(context), context.getDropResult() inside it would return the work-in-progress result instead of reading it from the Store. After all such cases are the reason I hid direct Store access behind this context proxy from user code.
When the loop is finished, we will dispatch exactly one drop action. This sounds more solid.

I'm closing because we're going to drop Flummox anyway.


PlaybackPro get the remaining play time and show on button(s)

i would like to have the ability to get the remaining time of actual playing video from PlaybackPro and show it on one button or have the choice to show the minutes on one button and the seconds on another button.
how can i realise this with Companion 2.0 beta?

I'll second that request, I know some others have done this another way but it would be great to have this added into the module.  I know the UDP command is TR from their online documentation but haven't played to get it working.  and when I saw it I forgot to message the poster as to how they did it.

What is the "other way"? I would like to do this, and not just for PBP

Is there anyone planning to work on this, adding variables to this module?

I do hope to implement this feature soon. Just finished updating the module for Companion v3. We should be able to implement feedback from PlaybackPro Plus fairly soon.

i just google this same feature, and hope find any solution and i am a bit disapointed, because already some have this same question in 2019 and we are in 2024, 5 years, i already try do a screen capture with NDI but on mac only have the screen converter that convert all windows and not only the area of interest, please guys add this feature


Service to register plugins, effects and flows.

Hi @JoelBesada @nathanchapman
This is a huge change.
I will wait for the atom v1.17.0 release to release this (will be the version 2 of this package).
This is a major refactor to allow extensibility on some areas. It provides a service for other packages to add plugins, canvas effects and input flows.

Plugin
Plugins can listen on some events by the package:

onChangePane: (editor, editorElement) ->
onNewCursor: (cursor) ->
onInput(cursor, screenPosition, input, data) ->
onComboStartStreak: ->
onComboLevelChange: (newLvl, oldLvl) ->
onComboEndStreak: ->
onComboExclamation: (text) ->
onComboMaxStreak: (maxStreak) ->

plugins have access to a little api that provides the following:
  shakeScreen: (intensity) ->
  playAudio: (audio) ->
  getEditor: ->
  getEditorElement: ->

and a combo api with:
  increase: (n = 1) ->
  decrease: (n = 1) ->
  exclame: (word, type) ->
  resetCounter: ->
  getLevel: ->
  isEnable: ->

The combo now can have many levels as the user configure it. By default: 20, 50, 100, 200 and 500.
Plugins can be enabled/disabled from the settings as other normal configuration.

Flow
The flow decides what effects are on or off given an input.
It uses the inputHandler with some utils:

 getPosition: ->
 isNewLine: ->
 hasDeleted: ->
 hasWritten: ->
 getText: ->
 getDeletedText: ->

and the switcher:
 offAll: ->
 onAll: ->
 off: (code) ->
 on: (code, data) ->

The flow has access to those utils, by default the package provides the default flow (the current one) and a user file based (it search for a file in the user's home).
The user can select the flow with the command activate-power-mode:select-flow

Effect
Is what the canvas renders, it handles the specific spawn of particles (or whatever it needs) and the rendering.
The methods needed for a effect are:

  init: ->
  disable: ->
  spawn: (position, colorGenerate, input, randomSize, conf) ->
  animate: (context) ->

Additionally there is a way to create a particles based effect, it handles most of the particles life cycle.
This object should provide these methods:
 create: (particle) -> # not required
 init: (particle) -> # not required
 isDone: (particle) ->
 update: (particle) ->
 draw: (particle, context) ->

The user can select the effect with the command activate-power-mode:select-effect

Service
With the service provided other packages can register their own effect, flows and plugins:

  registerPlugin: (code, plugin) ->
  registerFlow: (code, flow) ->
  registerEffect: (code, effect) ->
  createParticlesEffect: (particleManager) ->

the package can access to this service by writing on it's package.json:
{
  "consumedServices": {
     "activate-power-mode": {
       "versions": {
         "^1.0.0": "consumeActivatePowerModeServiceV1"
       }
     }
   }
}

If all this is ok, I will make some wiki posts to explain the api and how to register plugins, flows and effects.

Wow is awesome. It has a lot of new features. I will test all of them now.


[PE-D][Tester B] Claim command success message

Small UI issue, the second line "Remaining claim Alex Yeoh has: $4,060" has an extra space before it.

Labels: type.DocumentationBug severity.VeryLow
original: Weiennn/ped#5

Solved


Fix Docker issues and some minor updates.

@JeremyZr  : I see he reverted changes made by you! Anything to say about it?
@tezlopchan : Good job, thanks!

@nootanghimire nothing to declare :)


Expose invocation metering in the SDK.

What
Expose invocation metering in the SDK.
Why
Improving testing UX.
https://github.com/stellar/rs-soroban-sdk/issues/1319
Known limitations
N/A

If set_config is called with turning the value off, when the value is already turned on (should be an easy comparison), panic with an informative message saying that once it is enabled it cannot be disabled.

That makes sense and I've tried to sketch this. But this doesn't pass the semver check, as we're adding a new pub field to a struct, so initialization will be broken. So I'm even more in favor of enabling this by default.

this doesn't pass the semver check, as we're adding a new pub field to a struct

Darn, I forgot about this when I created this struct. In v23 we should change the struct into private fields with functions to modify the state. I created an issue to do that here:

https://github.com/stellar/rs-soroban-sdk/issues/1419

So I'm even more in favor of enabling this by default.

👍🏻

Based on the previous discussion I've enabled this by default, PTAL.
One caveat that I forgot about is that besides budget we also reset all the events between the calls. This makes sense in general and may actually highlight issues people might have had (if an event was expected to happen after a wrong contract call).

I think it's reasonable to treat that like a bug fix. The way it works today is too unspecific as to when events occur.


Improve support for jobs with History

Currently jobs such as IRC and PES-scans are not fully read. I propose to add some variables to help analyse them.

Read indices of accepted geometries
Add variable for energy landscape of accepted geometries
Add coordinates of accepted geometries
Read and store reaction coordinate along accepted geometries

Check the plams implementations:
energy landscape
history property
[history variables]
(https://www.scm.com/doc/plams/interfaces/ams.html#scm.plams.interfaces.adfsuite.ams.AMSResults.get_history_variables)
If your implementations achieve the same thing, I wonder if it is necessary to implement it in tcutility

I prefer to avoid the plams.Results objects as they require loading the job using plams, which in turn requires (I think) the job to be saved as a .dill file. It also requires initializing plams as it requires a jobmanager object. Everytime you initialize plams it will also create a directory for you, so we have to keep track of it and then delete it later. This will basically require us to wrap the whole program in a try/except block, otherwise we might not be able to delete it if the program crashes. Also, we will then have a TCutility result and plams result object, which again requires a lot more bookkeeping for us and loads everything twice.
In any case, we already have support for History variables that is easy to use (see this postscript). But we might implement some plotting functions/drawing of molecules etc. For now I will close this until we want to work on something more specific related to the history variables.


📃: New Project: Drumkit

Drumkit

Tech stack :

Objective : An interactive drumkit that produces sounds of various components of a drum set when interacted by mouse clicks, key presses or screen touch.

Screenshots

Details to Include When Taking the Issue:
Username: Dinkar850
Participant Role: Hacktoberfest

the project has already there


ISPN-5096 Avoid NPE beans when scanning for duplicates

https://issues.jboss.org/browse/ISPN-5096

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8217/vjuranek:ISPN-5096 for 3755b11a54e4c417cd9b0a18a7ffd0221afa00f9
Tests: 11216, 2 failed (2 new), 23 ignored. Build time: 01:51:13
Failed tests detected

(new) TestSuite: org.infinispan.partitionhandling.EntryRetrieverReplPartitionHandlingTest.testRetrievalWhenPartitionIsDegrated

(new) org.infinispan.server.test.query.ManualIndexingIT.testManualIndexing

@vjuranek Thoughts on @danberindei's comments?

Fixes a case which is not supported (two uberjars deployed together), closing.


MacOS External Texture with YUV format render color space should determined by CVPixelBuffer

According to FlutterDarwinExternalTextureMetal.mm Line 251, when skia renders it, the color space was specified to BT.601, which makes external workload (convert to bgra or downsampling to BT.601) for those pixelbuffer with color space BT.709 or BT.2020 or something else.
CVBufferGetAttachment from CVPixelBuffer could get the correct color space, so the render color space should be determined by CVPixelBuffer itself.

cc @cbracken

Turns out I'm hitting this as well in the last few days! Thanks for filing the issue.

@cbracken Happy to hear that you have noticed this issue, is there any plan to fix it?


Help updating bluejeans-gui

I would like to do this myself, but I'm getting some errors.
I fixed the version fetching in https://github.com/NixOS/nixpkgs/pull/140837, but now I am a bit stuck:
$ nix-shell maintainers/scripts/update.nix --argstr package bluejeans-gui

Going to be running update for following packages:
 - bluejeans-<IP_ADDRESS>

Press Enter key to continue...

Running update for:
 - bluejeans-<IP_ADDRESS>: UPDATING ...
 - bluejeans-<IP_ADDRESS>: ERROR

--- SHOWING ERROR LOG FOR bluejeans-<IP_ADDRESS> ----------------------

error: undefined variable 'outPath' at (string):1:86
sed: -e expression #1, char 45: unterminated `s' command

--- SHOWING ERROR LOG FOR bluejeans-<IP_ADDRESS> ----------------------

Packages updated!

No change to the actual package file is seen. I was able to work out that those errors are coming from inside update-source-version but that's as far as I got.
Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name: bluejeans-gui

current version: <IP_ADDRESS>
desired version: <IP_ADDRESS>
Notify maintainers

maintainers: @veprbl (tagging because just merged my bluejeans version fetch PR (https://github.com/NixOS/nixpkgs/pull/140837)) and @ymatsiuk (tagging because seems to have committed to the package recently)
Note for maintainers
Please tag this issue in your PR.

Oh! I thought the ... I saw when checking $version was from something else. Thanks.

I have an oil company to sell


Reason for the recently added shape restriction in MultiHeadAttention

Hello,
Wondering why is there a restriction on the input shape of query and value to have a matching final dimension?
This blocks having cross-attention to a source that has a different shape than query, unless adding an extra projection layer. Given that all input tensors (query, key, value) are immediately projected by dense layers inside MultiHeadAttention, I don't think any restriction on final dims is necessary.
For reference, the pytorch doc for MultiHeadAttention explicitly uses 3 distinct variables to describe expected dimensions for the three tensors. The tensorflow implementation does not enforce such restriction as well.
The restriction is enforced here: https://github.com/keras-team/keras/blob/5aa5f88dc200bbf2cd765d5a213c23c58da48e80/keras/src/layers/attention/multi_head_attention.py#L214-L219
And was added as part of the PR #19973 (in response to the issue #19769)
Thanks

CC @mattdangerw

Hi @aarbabi -
MultiHeadAttention documentation shows regarding shape of query,key and value.
Query  shapes are (batch_size, , key_dim),
key shapes are (batch_size, <key/value dimensions>, key_dim) and
value shapes are (batch_size, <key/value dimensions>, value_dim).
Here you can find description regarding shape of query,key and value arguments.

@mehtamansi29 Thanks for getting back to this.
Looking at the documentation:

This layer first projects query, key and value. These are (effectively) a list of tensors of length num_attention_heads, where the corresponding shapes are (batch_size, , key_dim), (batch_size, <key/value dimensions>, key_dim), (batch_size, <key/value dimensions>, value_dim).

I believe these shapes belong to the tensors after the projection, where key_dim and value_dim are the args passed to the constructor. It makes sense that query and key to have the same dim after the projection, but there shouldn't be any restrictions on the input tensors to MultiHeadAttention.
Hypothetically, even if these shapes were referring to the input tensors to MultiHeadAttention, you can see the documentation is using distinct dims for query and value (key_dim vs value_dim), which contradicts the restriction enforced.


JSON data doesn't populate request if php://input has already been read

In PHP prior to 5.6, you can only read php://input one time.  Thus if your code has read it before an exception is thrown, the request parameters will not be filled in.
I'm unsure of good options.  In my particular use case (Yii2 framework), I can manually edit Bugsnag_Request:;getRequestMetaData to get the raw post body from Yii::$app->request->getRawBody() since that caches it, but that isn't a general solution.

Hi @jcherniak. Sorry for the long wait. https://github.com/bugsnag/bugsnag-php/pull/194 should fix this issue for you.


Wizard should show all signatures on a binary

Or at least notify user that there are multiple sigs

Confirmed, only first certificate is imported which is problematic in some situations.


program crashes upon reaching validation step

Hi,
since IOB-Format doesnt' work yet (at least for me), i tried out the standard way using the datasets you provide on huggingface
Training also aborts with these.
I guess due to mislabeling while importing (data is called "validation" on huffingface and you define it as "valid")
/content/drive/MyDrive/Colab Notebooks/tner/ner_model.py in evaluate(self, dataset, dataset_name, local_dataset, batch_size, dataset_split, cache_dir, cache_file_feature, cache_file_prediction, span_detection_mode, return_ci, unification_by_shared_label, separator)
328             concat_label2id=self.label2id,
329             cache_dir=cache_dir)
--> 330         assert dataset_split in data, f'{dataset_split} is not in {data.keys()}'
331         output = self.predict(
332             inputs=data[dataset_split]['tokens'],
AssertionError: valid is not in dict_keys(['train', 'validation', 'test'])
Started via:
from tner import GridSearcher
searcher = GridSearcher(
checkpoint_dir='./logs/ckpt_test',
dataset="tner/wnut2017",  # either of dataset (huggingface dataset) or local_dataset (custom dataset) should be given
#local_dataset=local_dataset,
model="dbmdz/bert-base-german-cased",
epoch=1,
epoch_partial=1,
n_max_config=1,
batch_size=32,
gradient_accumulation_steps=[4],
crf=[True],
lr=[1e-4, 1e-5],
weight_decay=[None],
random_seed=[42],
lr_warmup_step_ratio=[None],
max_grad_norm=[None],
use_auth_token=True
)
searcher.train()
Best,
Jan

Thanks for catching the error! The GridSearcher https://github.com/asahi417/tner/blob/master/tner/ner_trainer.py#L293 has the input dataset_split_valid, by which you can specify the split for validation. As a default, it was set as valid but as you mentioned, the huggingface dataset format follows validation but not valid so that causes error. I will fix it by set validation as a default, but meanwhile please set it directly (dataset_split_valid='validation).

ah i see. thanks!!


NULL safety error

please add support for the latest null safety feature of flutter ... i am getting a lot's of error

duplicate of #1673


Implement owner argument inference

This allows the use of _ as types of arguments named owner or _owner within #[methods] blocks. Such placeholders will be automatically replaced with TRef<'_, Self::Base, Shared> for convenience.
This should make typing function signatures less tedious, and give new users a sufficiently sane default owner argument type that just works in common use cases: calling methods and passing as arguments. This should also help with the rather frequent confusion new users face when they try to write something that don't extend Node.
The downside is that it makes more things implicit, although it can be argued that owner in godot-rust is close enough to self to make this acceptable. Documentation is added to the #[methods] attribute macro to explain the exact behavior for advanced users.
Draft status: The change itself is simple enough and not really expected to impact #609 a lot, but some opinions on whether this is a good feature would be really helpful.

Closing after gathering feedback. The consensus is that this is too much "magic", and it breaks IDEs too much, which is undesirable.


h264enc: fix h264 HDR comformance issues

Let h264 level equal to max level, in order to support high level
bitrate, 4K encoding for example
As spec, only when bitstream contains 0x000000/0x000001/0x000002/0x000003
need to insert emulation byte 0x03

This patch ties to fix https://github.com/01org/libyami/issues/266 and https://github.com/01org/libyami/issues/265

+1


Dependencies update

Hi,
It seems updating wayland dependencies might be required to work around this issue.
The versions from Cargo.toml are affected whereas master seems to compile cleanly on ARM.

Thank you! I am going to make an update in few minutes.

Thx, once wayland compiles it'll become clear if other crates are still not fixed.
-original message-
Subject: Re: [minesweeper-rs] Dependencies update (#43)
From: Alexander Kuvaev<EMAIL_ADDRESS>Date: 05.01.2016 12:24
Thank you! I am going to make an update in few minutes.

Reply to this email directly or view it on GitHub:
https://github.com/Vinatorul/minesweeper-rs/issues/43#issuecomment-168975926

wayland-sys v0.5.5 fails on nighly

Thx; is there a tool to do that recursively?

@petevine what do you mean under recursively? I've checked versions on crates.io then used cargo update.
There is cargo oudated, but I fogot to use that (:

Recursively meaning if you update one dependency that depends on other updated crates, they would get updated too :)
For some "*" dependencies, cargo update can lead to a broken result.

Recursively meaning if you update one dependency that depends on other updated crates, they would get updated too :)

As I know cargo works so (check diff of my Cargo.lock file from the last pull request).

For some "*" dependencies, cargo update can lead to a broken result.

I think this is rather rare for libs with >100 downloads. Wildcards nice for fast developing, but not for release, and I think anyone who will see them in Cargo.toml -  will make a PR to fix it.

One last nag - wayland-client required fixing on ARM so it needs to be bumped to 0.5.8 again.

After bumping glutin to 0.5.8 and a cargo update, it compiles again.


Change Google Sign In button

Description
Change the Google sign-in button to a broader one.
Current  Screenshots

Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Remove the Facebook button
Change the Google button UI using  https://pub.dev/packages/flutter_signin_button

Additional data
None

@Mohitmadhav
Can you assign this issue for me?

@Mohitmadhav please assign it to me

@phan-dev you can work only on one issue at a time. Read the guidelines given in the README file for more details.
@Sayam06 I'm assigning it to you. And please make sure to submit the PR as per the template.

Hey @Mohitmadhav , I wish to contribute to this project. Please consider me for any future issues :)

Hey @Mohitmadhav, I wish to contribute to this project. Please consider me for any future issues :)

Sure @hrigved-dev, more issues will be created, you can comment and tag me before others,  for getting assigned !!


[Fix #13121] Add new Lint/EmptyStringInsideInterpolation cop.

Fixes #13121.
The new Lint/EmptyStringInsideInterpolation checks for variables being assigned to empty strings inside of string interpolation, and removes this path from conditionals.
Additionally, I extended the Lint/EmptyInterpolation cop to detect basic empty string interpolations, such as "#{''}" and "#{nil}".
this registered an offense in the Lint/Void spec, so I let it autocorrect that.
Currently Lint/EmptyInterpolation does not support cases such as "#{''''}" or  "#{'' + "" '' ""'' + nil.to_s}", although these cases of multiple empty strings as the only content of a string interpolation would presumably be rare.
Admittedly, Lint/EmptyStringInsideInterpolation does not support them either, so I need to at some point find a good way of going about this.
As for now, though, the majority of common occurrences are covered, so I'll work on the more obscure ones in a follow-up PR.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Just realized I forgot to change the description in config/default.yml when copying the block over from the last cop-- would a basic sanity check along the lines of "no two cops have the same description in the configuration" make sense, or is this a mistake other people wouldn't make?
(for what its worth, i did do a quick check locally and no two cops have the same description in the configuration, at least those with one-line descriptions)

This should probably be a style cop. I understand this comes a bit late, but can you open a PR at https://github.com/rubocop/ruby-style-guide/? Both versions seem perfectly acceptable to me (and I do have a strong preference for using empty strings).

Just realized I forgot to change the description in config/default.yml when copying the block over

You're supposed to use rake new_cop[name] (: It does most things for you.

First of all, this is definitely not Lint. Since this is a matter of preference, it falls under Style.
Also, I'm not sure if the rule enforced by this cop is appropriate.
#{cond? ? 'str' : ''} can be considered reasonable in that the result of cond? is always a string. And it would be clear.
#{'str' if cond?} uses the feature where nil becomes an empty string through string interpolation. Some people might prefer this, but I'm not sure if it would be universally accepted.

Ok, I'll move it to Style and open a pull request over at the style guide to see whether this style is preferred or not.

I’d argue that this style is significantly more frequently used and should be enforced.
We strive for consistency. Is there a reason to bother projects/teams that used to the ternary style?

We strive for consistency. Is there a reason to bother projects/teams that used to the ternary style?

I don't really understand what you mean here-- the point of every Style cop in rubocop is to enforce a particular way of programming. 'bothering' projects/teams that are using a different style is what an opinionated linter/formatter does.

Do you think RuboCop is opinionated?

Yeah? Cops like Style/Next, Style/RedundantReturn, Style/StringLiterals are all opinionated, as they're promoting a specific way of writing code as opposed to an valid alternative.
I get that most of them are configurable to support an alternative style, or can just otherwise be disabled, but the default choice of a style is still opinionated. If the issue is that this cop doesn't support an alternative style, I can add that as a configuration option.

We strive to make default styles match the usage, and for this, before picking the default style, we consult existing open codebases, and provide options for styles that are used less frequently. I can’t think of a more democratic way, and I wouldn’t call this “opinionated”.
At least this is the case for rspec-rubocop, -capybara and -factory_bot extensions that I feel responsible for.
There are opposite examples, of course, https://github.com/rubocop/rubocop/pull/11349#issuecomment-1367752612, but I believe this is a rare exception (and an edge case, so I didn’t insist).
Speaking of this cop - I’d suggest to add an alternative style. I don’t insist on doing this in this initial pr, it will be fine in a follow-up, or never, but it’s worth noting our intent of doing so.
And yes, no doubt that many teams still perceive the default RuboCop settings as “the standard”, but it’s not, and we’ve tried to conduct this message in different ways.

I recognize that the default styles match real-world usage and are chosen with consideration-- at the end of the day, if I run rubocop on a codebase for the first time, the default configuration may enforce a style of programming that is different to the one I am currently using. I view that as opinionated, even though there is frequently a way to ensure rubocop follows an individual's preferred style.
At any rate, I believe this cop follows a similar thought process to other Style cops, whether you view that as opinionated or not.
That being said, I'll work on adding an alternative style so it better matches other cops.

I get the point of the suggested cop, but the name seems a bit misleading to me as it seems it only checks empty literals returns in conditionals, which is a much narrower scope than the name of the cop may suggest (especially given how close the name is to the existing Lint check). If I didn't know how the two cops differ, I'd struggle to figure this out from their names alone.

Fair enough-- I'm open to alternative name suggestions, as this was the best I could think of at the moment. What about something like Style/EmptyLiteralInsideInterpolation? Style/EmptyReturnInsideInterpolation?


Model RD CDM v2.0 in an Ontology

Task: Create the ontology for your CDM (Common Data Model).
Steps:

[ ] Similarly to the Local Model Ontology, use Protégé to model the CDM structure.
[ ] Define classes and properties reflecting the structure and data standards of your CDM.
[ ] Save the ontology in Turtle format.

Not using OntoBridge anymore


Update pins.csv to fix incorrect joystick pins

We should probably add the ugfx attach input pin defs to this PR too. (Or get those definitions to use pins.csv)


After the preload file is modified, the *.d.ts file needs automatically generated

This will make the development process more enjoyable

It would be great if you could fix the linter warnings: Strings must use singlequote

It would be great if you could fix the linter warnings: Strings must use singlequote

fixed 🍺！


KV access policy for VMSS, remote KV, improved docs, variable names cleaned up

Summary:

ARM template resource added to give newly provisioned scale set access to read secrets from KV
Terraform templates updated to support Key Vault in a different/remote subscription
Improved docs/usability via updates to README.md, comments in Terraform templates, cleaning up names in templates

Pulling this, as I haven't finished testing across subscriptions.


[CERT-TEST-FAILURE] - TC-BR-4 - Test failed

Feature Area
Other
Test Case
TC-BR-4
Reproduction steps

Bring up the DUT with bridge-app.
Pair the DUT using chip-tool through "onnetwork" transport.
Run the command ./chip-tool powersource read bat-charge-level 1 9

Expected Outcome:

[1663925822.845859][1588:1588] CHIP:DMG:                                         Endpoint = 0x9,
[1663925822.845888][1588:1588] CHIP:DMG:                                         Cluster = 0x2f,
[1663925822.845919][1588:1588] CHIP:DMG:                                         Attribute = 0x0000_000E,
[1663925822.845946][1588:1588] CHIP:DMG:                                 }
[1663925822.845978][1588:1588] CHIP:DMG:
[1663925822.846007][1588:1588] CHIP:DMG:                                 Data = 58,
[1663925822.846035][1588:1588] CHIP:DMG:                         },

Actual Outcome:

691582024.386805][3477:3479] CHIP:DMG: 					Endpoint = 0x9,
[1691582024.386853][3477:3479] CHIP:DMG: 					Cluster = 0x2f,
[1691582024.386901][3477:3479] CHIP:DMG: 					Attribute = 0x0000_000E,
[1691582024.386946][3477:3479] CHIP:DMG: 				}
[1691582024.386998][3477:3479] CHIP:DMG:
[1691582024.387039][3477:3479] CHIP:DMG: 				StatusIB =
[1691582024.387084][3477:3479] CHIP:DMG: 				{
[1691582024.387129][3477:3479] CHIP:DMG: 					status = 0xc3 (UNSUPPORTED_CLUSTER),
[1691582024.387174][3477:3479] CHIP:DMG: 				},

Bug prevalence
Whenever I do this
GitHub hash of the SDK that was being used
367a0c672c18e0137e0162c15b78adbcb039a33a
Platform
raspi
Anything else?
Seems it broke after the PR: https://github.com/project-chip/connectedhomeip/pull/28134

@Survensa it seems that a bridge is not mandated to have a power source. Test plans can validate power source clusters if it exists, however it probably needs to determine first if power source is supported or not.
Could we get some details about what the test plan is expecting?

@andy31415
Test Plan expectations:

Verify whether the Device Under Test (DUT) successfully reads the BatChargeLevel attribute from the Power Source cluster, either from the appropriate endpoint or by receiving updates due to a pre-established subscription.
Confirm that the DUT accurately maintains the battery state of the supported devices listed above.

Note: Prior to the merge of PR: https://github.com/project-chip/connectedhomeip/pull/28134 into the SDK, this step obtains an expected value from the SDK.

What guarantees that "endpoint 9" must have a power source cluster?

Manual checking bridge app seems to indicate to me that cluster 47 is available on endpoint 6 ... however I do not actually know what each of these endpoints are supposed to represent. What are the test assumptions?

> ./out/linux-x64-chip-tool/chip-tool powersource read  bat-charge-level 1 6 --trace-to json:log
....
[1693417708.849289][1253442:1253444] CHIP:ATM:          {                                                                                [105/94601]
[1693417708.849292][1253442:1253444] CHIP:ATM:                  "report_data" :
[1693417708.849296][1253442:1253444] CHIP:ATM:                  {
[1693417708.849300][1253442:1253444] CHIP:ATM:                          "attribute_reports" :
[1693417708.849303][1253442:1253444] CHIP:ATM:                          {
[1693417708.849307][1253442:1253444] CHIP:ATM:                                  "Anonymous<0>" :
[1693417708.849311][1253442:1253444] CHIP:ATM:                                  {
[1693417708.849314][1253442:1253444] CHIP:ATM:                                          "attribute_data" :
[1693417708.849318][1253442:1253444] CHIP:ATM:                                          {
[1693417708.849322][1253442:1253444] CHIP:ATM:                                                  "PowerSource::batChargeLevel" : "58",
[1693417708.849327][1253442:1253444] CHIP:ATM:                                                  "data_version" : "1622213645",
[1693417708.849331][1253442:1253444] CHIP:ATM:                                                  "path" :
[1693417708.849335][1253442:1253444] CHIP:ATM:                                                  {
[1693417708.849339][1253442:1253444] CHIP:ATM:                                                          "attribute_id" : "14 == 'batChargeLevel'",
[1693417708.849343][1253442:1253444] CHIP:ATM:                                                          "cluster_id" : "47 == 'PowerSource'",
[1693417708.849348][1253442:1253444] CHIP:ATM:                                                          "endpoint_id" : "6"
[1693417708.849352][1253442:1253444] CHIP:ATM:                                                  }
[1693417708.849356][1253442:1253444] CHIP:ATM:                                          }
[1693417708.849359][1253442:1253444] CHIP:ATM:                                  }
[1693417708.849363][1253442:1253444] CHIP:ATM:                          },
[1693417708.849370][1253442:1253444] CHIP:ATM:                          "interaction_model_revison" : "10",
[1693417708.849373][1253442:1253444] CHIP:ATM:                          "suppress_response" : "true"
[1693417708.849377][1253442:1253444] CHIP:ATM:                  }
[1693417708.849383][1253442:1253444] CHIP:ATM:          },

so this does work for that endpoint, however it seems unclear to me how we decide what endpoint to test for.

According to the source comments in https://github.com/project-chip/connectedhomeip/blob/master/examples/bridge-app/linux/main.cpp#L967 the existing code expects:

endpoint 3 : a light
endpoint 4,5: temperature sensors
endpoint 6: composed device with temperature sensor and power source (It seems want to test this one!)

call wise it looks to me like we have endpoint 6,7,8 being added here

endpoints 9,10,11,12 are lights that are stated to be for "action clusters tests"

#28134 seems to have removed a previous "endpoint 9" and kept the power source on endpoint 6.
@cecille may know the spec correctness here, but from a test perspective it looks like this test needs to validate endpoint 6 if all we need is to read battery level

Thank you @andy31415


Feat/documentation

Coverage remained the same at 100.0% when pulling 865a3d01aeba67afb733267f78565a9a944127cf on feat/documentation into 48e762b8b41625f2b7025df0bd091d11a83ffea4 on master.

Coverage remained the same at 100.0% when pulling 0523240cc56816f0fbb41d0b429e688ab8396f0a on feat/documentation into 48e762b8b41625f2b7025df0bd091d11a83ffea4 on master.


update README.md

It would be helpful to state that pnpm build needs to be run first before running pnpm dev
The page doesn't load if you don't build first. Took me a while to figure it out.

https://github.com/graphprotocol/docs/pull/407 will fix this issue


My Studio is timing out very often and requires me to login every time.

OrientDB Version: 3.0.0 RC1
Java Version: 1.8
OS: Centos
Studio is timing out very often and requires me to login every time. It's frustrating because it loses all my queries from the input.  The worst behavior is when everything looks fine, you type a query and when you execute, it goes to login page and once logged, the query is lost.  So you have to start all over again.
Regards,
Safwan

Sorry, looks like -Dnetwork.http.sessionExpireTimeout=30000 isn't helping either.  Is there any other configurable setting?

I have one browser instance open. and I switch to work in Java and when I come back, it doesn't say it timed out. I spend time writing a complicated query only to lose it when I click on run.  It's incredibly frustrating to do the work twice.  I started refreshing the page before writing the query so I don't lose my query but unfortunately I'm human and forget.

Hi @luigidellaquila
Are you guys able to reproduce this, I've tried under 2 different browsers. It would really save us time if we can have Studio fixed ASAP.
Thanks,
Safwan

Hi @ShakAttacked
let me check. Do you also shutdown and restart the server?

@ShakAttacked  didnt notice it. we are using snapshot though.
seem this earlier. but looks ok for me.
sorry for joining in the middle.

Hi @maggiolo00 , @careerscale
I'm using the snapshot from the 30th.  I've tried in both chrome and firefox.  I have 3 different problems with Studio.

It times out in less than 15 minutes (maybe 5). hard to tell as I go to code and come back. As I type a query and execute, it takes me to login page.  this is without a restart of the server.
all my queries are lost on refresh, I get this in chrome and firefox so it's not browser related.
it happens when I restart the server. this happens when I work on a plugin and I need to restart to get the plugin changes (I've opened an issue regarding this, if this is a reload without restart).

Thanks,
Safwan


Can press enter after reaching max length

Checklist

[X] This is not covered in the repository examples.
[X] I am using the package latest version.
[X] This is a bug report or an enhancement proposal.

Description
When I reach the maximum character limit, I can still type "enter", other characters are fine.

This was fixed on this release

thanks! I'll give a try.

it seems it isn't fixed.


Feature request:  Support deleting packages older than X days

Would like to suggest a feature where packages can be deleted that are older than X days.
Similar to this action for purging artifacts:
      - uses: kolpav/purge-artifacts-action@v1
        with:
          token: ${{ secrets.GITHUB_TOKEN }}
          expire-in: 7days

Hi @mkrakowitzer,
I think that is a great idea. I will work on adding this feature.

Hi!
It will be nice to have such possibility.
Do you have some ETA for this feature?

@trent-j I was wondering if you had a chance to work on this? Its the only thing stopping us from using this action.

Hi!
Any news on this?

Yes, would like to setup package deletion rule like this:

Keep the N most recent versions, and
keep all versions created in the past Y months.

(and delete all other versions)

Currently I am keeping the 3 lates pre-release packages with:
    min-versions-to-keep: 3
    min-days-to-keep: 7
    delete-only-pre-release-versions: 'true'

I would really love to be able to keep the latest week of packages, eg. by setting:
    min-days-to-keep: 7

Preferably in combination with versions to keep. This should then keep all pre-release packages from the last 7 days, and at a minimum 3 packages. If only two packages are published the last week, one even older packages is kept:
    min-versions-to-keep: 3
    min-days-to-keep: 7
    delete-only-pre-release-versions: 'true'

When looking into this, it seems that timestamp for version/package is not available. The action is using GraphQL to run a query to get repository/packages/edges/node/versions with the properties id and version. There are other fields available, but none for publish timestamp of package.
Will we have to wait until GraphQL implements returning a property for publish timestamp before this issue can be considered?

Any plans to add this support?

+1

@jidicula, does this request seem like a reasonable change that someone could grab and implement?
It does appears as if the logic for delete-oldest-x-number-of-versions-of-a-package has access to created_at for a package (if (a.created_at === b.created_at)) and one would assume that this would make it possible to add logic that could delete anything created after some date.

even just introducing checkboxes for a mass delete would be huge. the web UI is really clunky and deleting the packages can seemingly done individually - after any given deletion, it jumps to the first page and the newest packages... a lot of scrolling and clicking after being warned of 75% storage usage from GitHub automated emails. trying to figure out if there's a smarter way to avoid this...


Attribute Error: Could not find PyAudio; check installation

Hi i am importing PyAudio but throws the error.can someone please help.
Steps to reproduce

(How do you make the issue happen? Does it happen every time you try it?)
(Make sure to go into as much detail as needed to reproduce the issue. Posting your code here can help us resolve the problem much faster!)
(If there are any files, like audio recordings, don't forget to include them.)

Expected behaviour
(What did you expect to happen?)
Actual behaviour
(What happened instead? How is it different from what you expected?)
(If the library threw an exception, paste the full stack trace here)

System information
(Delete all the statements that don't apply.)
My system is . (For example, "Ubuntu 16.04 LTS x64", "Windows 10 x64", or "macOS Sierra".)
My Python version is . (You can check this by running python -V.)
My Pip version is . (You can check this by running pip -V.)
My SpeechRecognition library version is . (You can check this by running python -c "import speech_recognition as sr;print(sr.__version__)".)
My PyAudio library version is  / I don't have PyAudio installed. (You can check this by running python -c "import pyaudio as p;print(p.__version__)".)
My microphones are: (You can check this by running python -c "import speech_recognition as sr;print(sr.Microphone.list_microphone_names())".)
My working microphones are: (You can check this by running python -c "import speech_recognition as sr;print(sr.Microphone.list_working_microphones())".)
I installed PocketSphinx from . (For example, from the Debian repositories, from Homebrew, or from the source code.)

What is the result of running python -c "import PyAudio" ? Also please fill out the system information, as it is really hard to help without that.


🐛 Avoid error on json and default inputs

Referring to an unset var causes unbound variable error. Check if the var is set before we refer to it. Fixes #386.

When is the policy file not set? In the Action, it has to always be there to generate the SARIF results.
Is this some corner case for testing?

It's unset here: https://github.com/ossf/scorecard-action/blob/0b3cf46f654c5617af003e05d307898eeb0b6481/entrypoint.sh#L69-L71 when input results_format is not sarif.

When is the policy file not set? In the Action, it has to always be there to generate the SARIF results.
Is this some corner case for testing?

It's unset here:
https://github.com/ossf/scorecard-action/blob/0b3cf46f654c5617af003e05d307898eeb0b6481/entrypoint.sh#L69-L71
when input results_format is not sarif.

gotcha. Nobody uses this yet, but good catch


Reliably generate mutations while the snapshot is iterating

Reliably generate mutations while the snapshot is iterating in order to test rarely occurring problems. Have added what I believe should be the correct parsing, on the assumption that the DOM changes will subsequently be correctly picked up by mutation events.

The difference between test cases a & b demonstrate different outcomes because of the freezing of childNodes in for (const childN of Array.from(n.childNodes)) — I'm not sure if there's a better way to iterate over child nodes (I imagine this freezing was intentional)
Test case d takes this further to show that it should not be possible to iterate to the #d3 element
The final e test case is the important one as it demonstrates that the snapshot can produce duplicate nodes, in this case #a1 appears twice in the output

I authored https://github.com/rrweb-io/rrweb-snapshot/pull/60 assuming there was something similar to the e test case going on.
But maybe a better solution would be to ensure all __sn attributes are wiped before the start of a snapshot, and ignore any nodes that already have a __sn assigned if we encounter them in the DOM walk, as presumably they have a lower id from earlier in the walk.
Node: The code modifications in snapshot.ts to get these tests to work would need to be removed or somehow only targetted to a special test build.
I'd like to get further input into this before proceeding on fixes for the test case failures I've created in this pull request!

@Yuyz0112 Just to note that it is intentional that the tests are failing for this pull request (in case you are avoiding it for that reason).
I also need some good ideas as to how to target the bit of code which does the eval in https://github.com/rrweb-io/rrweb-snapshot/pull/61/commits/d6b57fcfa09d9cba4e4aa203c42ae8cddc4eb055#diff-75923536d00ea7b9bdbd2a5196a698720893adb4993f502c3d777ca9b51a4df2 so that it only executes in testing?


Lower the 'TestCases' protocol to internal

Lower the access level of the TestCases protocol from @_spi public to internal (implicitly).
Motivation:
Due to some limitations in Swift's type system, we currently need a protocol named TestCases as a workaround to type-erase our sequence of test cases so that it can be constrained to Sendable (see comment). But because the Test.testCases is public, that protocol also needs to match its access level. Since this protocol is just a workaround, we'd rather not expose the protocol and only expose a property returning a Sequence of test case instances on Test.
Modifications:

Add Test._testCases as a private stored property of type (any TestCases)?.
Change Test.testCases to a computed property which conditionally down-casts self._testCases.
Lower TestCases protocol to internal.

Result:
The TestCases protocol is no longer exposed, and the type of the computed Test.testCases property is any Sequence<Test.Case>.
Checklist:

[x] Code and documentation should follow the style of the Style Guide.
[x] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci please test

@swift-ci please test


[MINOR] add in minor perf wins in hudi-utilities and locking related tests

Change Logs

Use a single spark context per class instead of per test for the tests in hudi-utilities
Change lock retries and timeouts to speed up tests with assertions around locks

Impact
Improves test runtime
Risk level
None
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

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

Some results
BEFORE:
hudi-client-common ................................. SUCCESS [01:53 min]
hudi-utilities_2.11 ................................ SUCCESS [07:38 min]
AFTER:
hudi-client-common ................................. SUCCESS [ 13.033 s]
hudi-utilities_2.11 ................................ SUCCESS [06:47 min]

@the-other-tim-brown let's also file a jira under https://issues.apache.org/jira/browse/HUDI-3303? normally need jira for +/- 50 LOC


API error when creating several

Hi,
I've bought the PRO version of chord and integrated it to a web interface where I need to create several chord diagrams. After I've created some diagrams I get thrown an API error exception and need to restart the creation of the diagrams.
Thanks for a beautiful visualization package.

Hello @NilsErlanson
I'm glad you like it!
The error reporting will be better in future, but in the meantime I can try help you navigate this issue. It seems to be an error with the input. Some errors you're receiving are:
TypeError: can only concatenate str (not "list") to str
TypeError: unsupported operand type(s) for /: 'list' and 'int'
If you pop onto the Discord, https://discord.gg/nsezsyb, I can take a look at your input and see if I can spot the issue!

Hello @NilsErlanson
I'm glad you like it!
The error reporting will be better in future, but in the meantime I can try help you navigate this issue. It seems to be an error with the input. Some errors you're receiving are:
TypeError: can only concatenate str (not "list") to str
TypeError: unsupported operand type(s) for /: 'list' and 'int'
If you pop onto the Discord, https://discord.gg/nsezsyb, I can take a look at your input and see if I can spot the issue!


Fix the network stuttering

On the client there is an interpolate that is currently not working. The problem was that the interpolate was not working correctly (actually even worst than that).
So find the problem and solve it!

Could come from the interpolate?
Could come from the computing?
Could come from the timer (most probably).

Done I fixed it on the client side!


Too many modules know about environmental variables

It seems a better idea to have all the methods getting and dealing with VK_API_APP_ID environmental variable in a vk module. The same applies to other environmental variables.

Move some of the methods dealing with tokens out of installation_guide.py.

The problem is in the installation_guide.py.


Auto-completion is overzealous

When writing code the auto-completion functionality is jumping to conclusion that I wish it wouldn't. I do not recall this issue in previous version of RTVS.
Repro:
This would be example code I am trying to compose.
library(devtools)
check("lightgbm")

But the intellisense suggests checkpoint once you have typed check and then when you type ( it will auto complete to checkpoint().
This behavior happens for more than just the check() function. I am currently use v1.0-rc3. (1.0.30302.1431)
Let me know if I can provide any additional information.

When I type

( completes to check. Do you see different list and selection?

Somehow I did not have the default setting on for Intellisense.
Options -> Text Editor -> R -> Advanced -> Intellisense -> Match Partially typed augment name
This option was set to Off and was bold. Switching it to On solved the problem. I am not sure how it got set to Off.

Great, thanks :-)


Common js error while working in remix js

SyntaxError: Named export 'HuePicker' not found. The requested module 'react-color' is a CommonJS module, which may not support all module.exports as named exports.
What can be the work around?
I am using
import pkg from 'react-color';
const { HuePicker } = pkg;

but getting error

I seem to have gotten around this by adding the package to ssr.optimizeDeps section in the vite.config.js
react-router 7.0.2
import path from 'path';

import tsconfigPaths from 'vite-tsconfig-paths';
import { reactRouter } from '@react-router/dev/vite';
import { defineConfig,} from 'vite';

export default defineConfig(({ mode }) => {
  return {
    plugins: [
      reactRouter(),
    ],
    ssr: {
      optimizeDeps: {
        include: [
          'lodash',
          '@mui/icons-material',
          '@mui/material/utils',
          'react-color'
        ],
      },
      noExternal: [
        /^@mui\//,
        'lodash',
        '@mui/icons-material',
        '@mui/material/utils',
        'react-dropzone',
        'react-color',
      ],
    },
  };
});


table 4

In table 4 of the paper, it looks like performance gets worse when adding longlora to the short shift attention. Im confused as to the exact training procedure used? Im guessing the rows with checks only for shift short attention involve fine tuning the full architecture whereas the rows with both longlora and shift short attention apply the shift short attention adjustment and then go straight to lora fine tuning?

eg: Does shift short attention in combination with longlora require full fine tuning (with short shift attention, no lora)? Or is it able to just go straight to longlora with short shift attention?

Hi,
Because both lora training and S^2 attention are both for better efficiency, the degradation on perplexity s not much and acceptable. By default, we use both of them for efficiency.
Regards,
Yukang Chen

Ok thanks. Just to confirm, you can take a stock LLama pretrained model, apply the s^2 attention to it (without any fine tuning), and go directly to training it with Long Lora? I see you can use both, I just didn't know if using both first requires fine tuning the version with just the s^2 and no lora first before then applying lora?

Yes, it is. Thanks for your suggestion. We have not tried no lora first before applying lora. It might be better but a bit complicated.

sorry to bother again, I just wanted to clarify my question..
Does supervised fine tuning require the regular fine tuning before?
Thanks,
Brett

Hi,
Based on my experience, it is no need.
Regards,
Yukang Chen


Tutorials for tskit in other languages (C & Rust)

We have a fully functional short tskit & R tutorial. I wonder if it's worth having a part of the tutorials book on other languages and include a (short) C example and a Rust example? I'm guessing @molpopgen would be the one to do this, if he has any time.

Certainly a C one would be nice. We can adapt some of the content in the C API page.

Hah, for a moment I thought this meant eg in spanish, and wondered why the first spanish tutorial would be about rust.

Cierto en Espagnol. Moi je peux traduire en Français si vous voulez :)

I can do one for the rust interface.  Unfortunately (IMO) I think it has to be a notebook rather than myst-md.  The way one specifies the dependencies for a rust notebook is not allowed in the markdown.  I've know this for a while but haven't had the time to figure out where to file the issue (jupyter-book or the rust kernel authors, or both, or neither).
This is low on the short-term priority list, though.

This is low on the short-term priority list, though.

Yes, absolutely. I only opened this issue so as not to forget it. We could either leave it as an open issue or make a tutorial stub and just fill it with a "todo"

To follow up on this (which some recent Slack posts reminded me of): a literate tutorial for tskit-rust is unlikely unless we start using RMarkdown/knitr.  I recently closed a PR based on mdbook due to the amount of work required.  The current goal is to get a working example for all elements of the public API.  An example is here and the next release will have many more.  But it is slow to get it all done.

For posterity:
---
title: "tskit-rust tutorial"
author: Kevin Thornton / tskit-developers
output: html_document
---

```{r, echo=FALSE}
library(rextendr)
```

# Adding a node to a `TableCollection`.

```{extendr engine.opts = list(dependencies = list(`tskit` = "0.9.0"))}
let mut tables = tskit::TableCollection::new(100.0).unwrap();

// Node flags, birth time, population id, individual id
let node_id = tables.add_node(0, 0.0, tskit::PopulationId::NULL, tskit::IndividualId::NULL).unwrap();

// The type tskit::NodeId can be compared to i32
assert_eq!(node_id, 0);
```


Android PBL 5.0 + compliance / compatibility?

Hello,
@jamesmontemagno
re Msg about Google Play Billing Library
I received this from Google and have implemented the current version of THIS library, yet to be deployed.
We are sending you this reminder as one or more of your apps is still using Play Billing Library (PBL) version 4. By November 1, 2023 version 4 will be deprecated and any updates to existing apps will first require you to migrate to PBL version 5 or newer.
Important notes: If your app is targeting Android 14 or higher, you must update to PBL 5.2.1 or PBL 6.0.1 or higher.
According to your version notes, which I think are dated ...
Android: We now use Google Play Billing Version 4.0!
According the package mngr, Plugin.InAppBilling targets Xamarin.Android.Google.BillingClient 6.0.1
Does Plugin.InAppBilling target Google's Play Billing Library (PBL) 5.2.1 or (PBL) 6.0.1 or higher?
Thank you!

Looks like it already uses Billing Client 6.0?
https://github.com/jamesmontemagno/InAppBillingPlugin/blob/master/src/Plugin.InAppBilling/Plugin.InAppBilling.csproj#L101C29-L101C29
Would be nice if someone can confirm.

@Meekohi  Actually, I was just about to post ...
According to the release notes:
Version 7.0+  - Major Android updates
....
2.) Android: Now using Android Billing v6
....