Livereload is trigger prematurely

When grunt-shopify is set up as a watched task with livereload enabled it will do the following:

detect changed file
begin uploading changed file
live reload the browser
finish uploading file

It appears that it is sending some sort of premature completion signal back to grunt-contrib-watch instead of signalling completion when the file is actually done uploading.
Here's the relevant part of Gruntfile.coffee.
shopify:
  options:
    base: "deploy/"
watch:
  configFiles:
    files: ["Gruntfile.coffee"]
    options:
      reload: true
  shopify:
    files: ["deploy/**"]
    tasks: ["shopify"]
    options:
      livereload: true

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Closing this as it works fine with browserSync without any core changes, looks like livereload /grunt has a bunch of discussion on how to resolve this but nothing got decided on from my look? https://github.com/gruntjs/grunt-contrib-watch/issues/156, https://github.com/gruntjs/grunt-contrib-watch/issues/165


Add Touchscreen Plugin

Fixes

Fixed the dead input bug.

(Without this plugin touch inputs will be missed/inaccurate as the mouse position from last frame is used for interacting, but touch inputs teleport the mouse, so that can be a massive difference)

Features

Ability to rotate the camera by dragging on the game view
Ability to zoom the camera by dragging vertically on the minimap
Ability to zoom the minimap by dragging horizonally on the minimap
Ability to scroll various menus by dragging on the menu
Faster right clicking option

Click and hold to open the right click menu as normal on touchscreen, without releasing the click move your finger onto the desired option then release

Video Examples

Before

https://www.youtube.com/watch?v=HEus8rMrut0

After

https://www.youtube.com/watch?v=UGWogZZtLlk

Apologies for the commits post PR opening.
I've cleaned up all the noted issues and added tags.

we don't care about commits, we'd rather you spam commit than spam open/close PRs every change

My feedback for this pr and the other one that is open is the same. Emulating mouse events, trying to time clicks, and fixing events sounds not great maybe in regards to Jagex cheat detection.

Unfortunate.
I don't think there is any way I could achieve a good UX without post-processing the events as I've done.
Even if I somehow managed to receive actual touch events, they would still need to be translated into emulated mouse events.
If that is the final verdict, then I think touchscreen support as a concept is just dead in the water and this PR can be closed.

After discussion, we don't think we can safely support these plugins unfortunately.


Thread support

I would like to propose the attached extension which allows is to work with threads as long as they are created in the current test. This feature depends on bordeaux-threads (actually bordeaux-threads with PR 19) and is thus provided in a separate ASDF system. Another reason for not loading thread support unconditionally is the need for locking when gathering test results which may have a performance impact. The attached implementation is just a proof of concept. I can add tests and improve the code if there is interest in this feature.

Is #23 about the same question or is that about accelerating testing by means of parallelization?

Can you please describe what this patch does in more detail ?

Thanks for the reply.

Can you please describe what this patch does in more detail ?

Sure. Currently, fiveam cannot handle cases like
(5am:test foo
  (bt:make-thread (lambda () (5am:is (= 1 1)))))

because the special bindings and condition handlers for recording results are not established in threads other than the one executing the test body. Another issue is that a multi-threaded scenario requires some form of synchronization.
The patch tries to address cases like the above without introducing a mandatory dependency on bordeaux-threads or always paying for synchronization.

To this end, a new system system, fiveam-and-bordeaux-threads (db0b9c8), arranges for threads spawned in the body of a test to report assertion results to the test execution context of the spawning thread (this delegation should be transitive, but i didn't test that yet).
Realizing this behavior as an optional extension requires a slight change of protocols in the fiveam system, namely making add-result a generic function an adding the generic function call-environment-binding (this is what  	35f529f does).

The interrupt-thread call is a hack for the proof-concept-implementation. It can almost certainly be avoided by arranging the special variables and protocol functions a bit differently.
The patch requires a change in bordeaux-threads (see PR 19) in order to being able to

capture values of special variables in the spawning thread and establishing bindings in the spawned thread
establish condition handlers in the spawned thread

As I wrote before, this is a proof-of-concept and I would clean up the code and add tests if there is a chance of something like this being merged.

I don't think it's a good idea to run assertions in threads. Not in general, and not with the code base of Fiveam, which is geared towards interactive REPL evaluation and uses lots of special variables.
You can already compute values in a thread and run the assertions in the main thread:
(5am:test foo
  (let ((th (bt:make-thread (lambda () 1))))
    (i (= 1 (bt:join-thread th)))))


precomp (git commit d9f61c65d663d0aa03bd60d776ea06e40f07b1fa and 0.4.5) segfaults for this file.

pre compressing this file --
precomp_segfault.zip
with command line --
-cn -oprecomp_tar
segfaults precomp on LInux 64
I tried to get the BT, but the debugging symbols where not there in the binary version and the one that I built from git. I tried changing the CFLAGS and added -ggdb, but the debugging symbols still got stripped. On changing the optimization levels to -O0 for all libraries, solved the problem but of course it's a bad solution.

It's giflib. Disabling it completes the precomp.

try on Win7 64bit.

precomp_segfault.zip : no fault & no gain
-intense precomp_segfault.zip : no fault & no gain
precomp_segfault.tar(extracted from the zip) : no fault
-intense precomp_segfault.tar : fault on 59.82%
-v -intense precomp_segfault.tar : no fault, suggest -zl18,68,69,82,95 -d0
-intense -d0 precomp_segfault.tar : no fault
-intense -d10 precomp_segfault.tar : no fault
-intense -zl18,68,69,82,95 precomp_segfault.tar : fault on 59.82%

Regression from 0.4.5 (where everything works according to a quick test), one of the culprits is a GIF stream at position 1260117 (60.09%), but there seem to be other problems, as the following gives no segfault on my machine (Win7 64bit, Precomp 0.4.6 commit d9f61c6):
precomp -cn -intense -zl18,68,69,82,95 -v -i1254601 -i1244353 -i1237086 -i1162009 -i1146093 -i1138392 precomp_segfault.tar
(it basically ignores several streams before the GIF stream, but not the GIF stream itself)
OTOH, undefined behaviour leads to undefined behaviour, so you never know...

Mine is a Linux machine.

Segfaults 4.5 also.

Debugging with Visual Studio worked good. This way, the error could be isolated to testing a small GIF file (attached). The image is 1x1 pixel, but has no colormap, so that the function EGifPutImageDesc returns an error code - this code was unhandled and led to accessing uninitialized memory.

Thanks.


Fix no-text-outside-Text issue

react-native throws a full-on Error when you pass a string as children to a component which is not  wrapped by a Text component.
We got some mysterious sentry reports about this happening on the Home tab in the latest release and after digging through the changes to all components on the home tab I'm 90% sure this is the culprit.
Trivial change so I'll self-merge, but it's good to be aware that this blah && <Blah /> pattern is very unsafe in react-native when the thing on the left is a string or a number. It's necessary to use blah ?? <Blah /> if you're not concerned about falsey values ("" and 0) or blah ? <Blah /> : null if you are.

Thanks for the tip @ds300! Is there a linting rule we could enable to guard against this?

yeah, I'll add a ticket to the MX backlog to enable it, good suggestion! 👍

I think the rule we'd be looking for is this one: https://palantir.github.io/tslint/rules/strict-boolean-expressions/

@pepopowitz that sounds like fun! I put something in your calendar, feel free to move around if it's not convenient.


Adding notifications completely breaks amplify push (Auth error - Cannot turn MFA functionality ON, once the user pool has been created)

Describe the bug
Adding notifications breaks Auth
Running amplify add notification on an existing amplify project (with auth added previously and configured for MFA) causes the following error on push Cannot turn MFA functionality ON, once the user pool has been created.
See additional context for how to work around it
Amplify CLI Version
4.26.0
To Reproduce

get your project with auth already set up (MFA on)
run amplify add notification
add a new pinpoint project and setup fcm messaging (you will see a message about enabling auth)
amplify push

Project is now broken and won't deploy. It shows the error message Cannot turn MFA functionality ON, once the user pool has been created.
Expected behavior
To be able to publish project
Desktop (please complete the following information):

OS: Mac Catalina
Node Version. v14.4.0

Additional context
Doing a diff on the project for before and after the only significant change I can see is in -cloudformation-template.yml where the following line has changed:
RoleName: !If [ShouldNotCreateEnvResources, 'roarvib2307e0f_sns-role', !Join ['',[ 'sns', !Select [3, !Split ['-', !Ref 'AWS::StackName']], '-', !Ref env]]]

there is an 'undefined' added to the line
RoleName: !If [ShouldNotCreateEnvResources, 'roarvib2307e0f_sns-role', !Join ['',[ 'sns', 'undefined', !Select [3, !Split ['-', !Ref 'AWS::StackName']], '-', !Ref env]]]

If I remove this, then it deploys correctly

Update - This happens with amplify add analytics too!

I figured out what causes this. Adding notifications changes "mfaConfiguration" from "OPTIONAL" to "ON" whether you have set it previously on purpose or not.  You have to change it back to make it work if you have a pre-deployed stack because you cannot make changes to cognito after the fact @akshbhu

Hi @jcbdev
Thanks for reporting this. I am looking into this and soon will provide update regarding this

Hi @jcbdev
I tried to reproduce this issue with latest amplify version (4.27.2)and I was not able to reproduce it. Amplify push was successful with any error.
I also have above line in the auth CFN file :
      RoleName: !If [ShouldNotCreateEnvResources, 'issue54c516322_sns-role', !Join ['',[ 'sns', 'undefined', !Select [3, !Split ['-', !Ref 'AWS::StackName']], '-', !Ref env]]]

Here are my repro steps:

amplify add auth with MFA turned ON and amplify push

amplify add notifications with FCM

Amplify push

Can you try with latest version and see the error is still there  and also if I have missed anything in my repro steps?

Hi @jcbdev
I tried reproducing this issue with the latest CLI 5.0.2 and was unable to do so - can you confirm that this is still an issue you're facing?
I did the following:

amplify add auth, MFA optional, push
amplify add analytics, pinpoint, push
amplify add notification, FCM, push


Add a simple method to inverse the transformation.

Similar to all the transformation in scikit-learn, we also need a inverse-transform in tslearn to help us to know the original time series, especially after the prediction.
It will be similar to sklearn to do:
tssm = TimeSeriesScalerMinMax()
X_train_tf = tssm.fit_transform(X_train)

# After the prediction
preds = tssm.inverse_transform(preds)

Hi @benbenbang ,
I guess the only case where that would make sense is when the task is prediction of next value, right? I'm afraid this would lead to misuse by users not aware of what these transformers do (per-time series rescaling, not dataset-wise rescaling). Would you see another way to do this without this risk of misuse?
Best,
Romain

Hi @rtavenar, pardon, I didn't get what you mean. It I understand well, the code in preprocessing is for an array-like data format which is neither dataframe or matrix. So when people create a new object to do the transformation, it should be only correspond to the time series they applied to. So what do you mean by dataset-wise rescaling? Would you please show me some concrete example?
Thank you.

In sklearn, the normalization happens dataset-wise. E.g. for the MinMaxScaler, they would calculate the minimum and maximum column-wise on the entire dataset (take min and max for each possible variable). In tslearn, the scaling happens per time series, this would mean that you would have to store the min and max for each timeseries in order to apply the inverse transform, and that the order of the time series that get passed to both transform and inverse_transform may not change.

NB: related to #48 btw

Got it, I will check if there's a better way to do so. Thanks.

@rtavenar is there by the way a reason why we should do timeseries-wise scaling instead of dataset-wise? What's the issue with calculating a minimum and maximum based on the entire dataset and scaling all time series based on those values?

The classes in preprocessing are not scikit-learn compatible transformers since they don't implement fit and transform as separate methods. Hence there's no reason to expect an inverse_transform method.


feat: state demand profile interface function

Pull Request doc
Purpose
Create an interface function to simplify generating profiles by state. Also, finished merging the LDV/HDV smart charging functions into one common function.
What the code is doing
This function generates a dictionary of vehicle miles traveled (bev_vmt) for a specific geographic regions within a given state. It then outputs a demand profile for each geographic region. The state function input is also mapped to a census region which loads the appropriate vehicle census data.
Testing
manual testing so far, would like to eventually add an automated integration test
Time estimate
~30min

Looks like
prereise/gather/flexibilitydata/doe/tests/test_bus_data.py::test_get_bus_fips
is failing in PR test workflows


Add Validation and Test Split in pipeline

@khumairraj this is awesome. Did you try running it and making sure from the JSON statistics outputs that it looks right?


Build: Add publishConfig to package.json

Stops us from accidentally publishing to our internal npm server.

Current coverage is 100.00%

Merging #77 into master will not affect coverage as of 48a571d

@@            master     #77   diff @@
======================================
  Files           14      14
  Stmts          119     119
  Branches         0       0
  Methods          0       0
======================================
  Hit            119     119
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 48a571d

Powered by Codecov. Updated on successful CI builds.

LGTM

Merging :ramen:


Can't use Pascal case when declaring a stateless functional component (SFC)

I'm currently having issues declaring SFCs when using the following tslint configuration:
{
  "extends": ["tslint-config-airbnb", "tslint-react", "tslint-config-prettier"]
}

and here is a sample component
import * as React from 'react';

const DummyComponent = () =>
Hello World!
;

export default DummyComponent;

which results in the error
[tslint] variable name must be in lowerCamelCase or UPPER_CASE (variable-name)
const DummyComponent: () => JSX.Element

I know that it is the tslint-config-airbnb causing the issue, but I would have thought that tslint-react would have a rule for Pascal cased SFCs.
I think that this rule is missing. I'd be happy to throw up a PR if that's the case. I just need to read up a bit on creating rules.

For now, I'm doing this, but it's just a hack, as it allows people to write all vars as Pascal case.
{
  "extends": ["tslint-config-airbnb", "tslint-react", "tslint-config-prettier"],
  "rules": {
    // This rule is here for now because of https://github.com/palantir/tslint-react/issues/120
    "variable-name": [true, "ban-keywords", "check-format", "allow-pascal-case"]
  }
}

:+1:

Also running into this. Bump.

Any update on this?

Need some workaround too, to be used in pair with React project. Until then turned this rule off.

Potential solution, would there be any way to allow PascalCase on a Stateless Component if it preceded by the React.RFC
 type?
// will cause an error
const DummyComponent = (props) => {
   return
Hello World!
;
};

// is allowed, as component is now typed
const DummyComponent: React.SFC<DummyComponentProps> = (props) => {
   return
Hello World!
;
};

You can do this:
const dummyComponent = () =>
Hello World!
;

export { dummyComponent as DummyComponent };

I wouldn't limit it to functional components, since it'll complain about any react component assigned to a constant.
import React from 'react';
import styled from 'styled-components';

// Returns a `StyledComponent`.
const StyledBox = styled.div``;
// Returns a `LazyExoticComponent`.
const LazyBox = React.lazy(() => import('./Box'));
// Returns a `MemoExoticComponent`.
const MemoBox = memo(Box);

also happens with React Contexts
https://reactjs.org/docs/context.html
example from the documentation:
const ThemeContext = React.createContext('light');
...
<ThemeContext.Provider value="dark">
   <Toolbar />
</ThemeContext.Provider>
...

I dont know the problem but I found a solution ...
if I use this :
// in ./app.ts
import MyComponent from './components/myComponent';

I get that :
Error : `Misnamed import. Import should be named 'myComponent' but found 'MyComponent'
(import-name)tslint(1)`

even with that :
{
  "extends": ["tslint:recommended", "tslint-config-airbnb", "tslint-config-prettier", "tslint-react"],
  // This rule is here for now because of https://github.com/palantir/tslint-react/issues/120
  "variable-name": [
    true,
    "ban-keywords",
    "check-format",
    "allow-pascal-case",
    "allow-leading-underscore",
    "allow-trailing-underscore"
  ]
}

I dont know if I am doing it right ?
this is my solution :
// in  ./components/myComponent.ts
export const myComponent = props => {
  /* ... using props somewhere in my function ... */
};
// in ./app.ts
import { myComponent as MyComponent } from './components/myComponent';

// or

// in  ./components/myComponent.ts
export default props => {
  /* ... using props somewhere in my function ... */
};
// in ./app.ts
import { default as MyComponent } from './components/myComponent';

Any progress on this? It's kind of a PIA to deal with this in react components.

I think the AirBnb style guy explicitly states why this rule is in effect. You can turn if off if you like:
Class vs React.createClass vs stateless

I don't think type-aware variable naming is going to be added to tslint given the deprecation timeline (#210). Until now we've been happy with allowing pascal case for all variable names, so I consider that a sufficient workaround.


Both YouTube static ads and the TOS violation warning have started showing up again

Updated: Including that "Ad blockers violate YouTube's Terms of Service" is now showing up again as well as static ad images during start/playback of videos.

Script version
v4.0
Describe the bug
Updated Chrome to:  122.0.6261.112 (Official Build) (64-bit)
Ads are now showing up during videos.
The ads aren't the actual videos but a static advertisement that stays up for 5-10 seconds.
It can happen multiple times during a video.
Less than a day later, the "Ad blockers violate YouTube's TOS" message has started coming up. This message stays up while autoplay continues through a list of videos.
A refresh of the browser seems to fix things temporarily.
Expected behavior
The expectation is ads not interrupting playback and definitely to not see the "TOS" message.
That's the whole reason we flocked to this amazing script!
(And an obligatory thanks should be made here b/c without Joel and the other awesome people who help out with this project, we'd be forced to deal with YouTube vids that are 30-50% longer due to ad injections!
Screenshots
Example of ads showing up:

And the TOS screen:

Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 122.0.6261.112

Posted 2 weeks ago.
Still happening...
Updated Chrome today, went to YouTube to play a random song.
Got 2 static ads in a row before the song would play.

And when going to the next video, this shows up:

Help us out, Joel!
¯\_(ツ)_/¯

Which OS are you using? I got the issue on Ubuntu 22.04.4, 5.15.0-56-generic GNU/Linux

Not sure what version it was when I posted this but currently I'm running Windows 10 build 19045.4046
The problem doesn't seem to persist anymore, but it has gone away and come back a few times now.

As a general update, this problem doesn't seem to persist anymore.
It happened a few times after updating Chrome, but I haven't seen a static ad in ~2+ weeks.
Going to close this for now as I can no longer reproduce the problem.


fix(paeckchen-core): estree typings are exposed

estree typings are exposed in the generated paeckchen typings and are therefore not only dev
dependencies

Coverage remained the same at 100.0% when pulling 40dac7fc4a1b59aa7a928118851b06b5d563202d on core/typings into 09668e046f79facc2f936052b441ca2ea4f9afc8 on master.

Coverage remained the same at 100.0% when pulling 5032036c9fd5337290cd7cff87014b7d025eb7f6 on core/typings into 1e2743e26bf7a158314f3c10664f8b99e13129cd on master.


collapsible issue

I'm having troubles with collapsible. The items are displayed, but the JS events are not being triggered. I've got modals etc. on the page already, so the assets are loaded correctly.

            {{topic.name}}
            {{topic.value | number : '1.4-4'}}

details...

@eamonnmag what events are you referring to?
Is it different than the example here? http://angular2-materialize.surge.sh/#/Collapsible

No response. Closing.


fix: hide points outside linear element editor when close enough

An attempt to fix https://github.com/excalidraw/excalidraw/issues/5556
https://user-images.githubusercontent.com/11256141/186395715-4902d17d-2351-440b-9dc7-0a753c1cf391.mp4

[ ] start/end points should always show no matter what:

[ ] IMO we shouldn't hide a point while dragging. In fact, I'd probably not hide points at all until you deselect the element, so there's no points disappearing under your cursor, and you don't get into a place where you can't drag the point away after it gets hidden.

[ ] hidings points should be "stable". Right now it seems to behave "take a segment of two points, if they're too close, hide the one on the right", which results in this behavior where a single point can be hidden/visible based on proximity to prev/next point. I'd make it "every odd-index point is always visible; hide even-index points as needed instead"

[ ] the visible indices should be recalculated on points being added/removed:

should take into account current zoom (as such, visible indices should also be recalculated on zoom change?)

Zooming issue is in prod too so for points inside and outside editor as well, can raise a separate PR for it. As per visible indices, I think its ok not to calculate on zoom change as it could be confusing ?

[ ] dragging invisible points shouldn't be allowed:

[  ] should hide the N-1 point if last two points too close together

[ ] question: should we move points together when dragging a point near to an invisible point(s)?

should we move points together when dragging a point near to an invisible point(s)?
You mean invisible point will be dragged without user knowing about it ? No we shouldn't do that imo.


MessageHeader Decoder issues when Encoding is done with different language.

Hi,
We are trying to create a C++ SBE Decoder application for a message that is being sent on TCP Socket.
The Encoder side application is using Java SBE Encoder and pumping the message onto a TCP socket. (Encoder side uses "wrapAnddApplyHeader" method + other data encoding)
On C++ Decoder application side, we see that MessageHeader is unable to decode the received message. (The message is received correctly over the TCP Socket. Its just that the MessageHeader is not correctly decoded.)
Can anyone please let me know if we can use the C++ codecs for decoding a message that is sent using Java codecs ?
Thank you.

Hi @cyberpower715

Can anyone please let me know if we can use the C++ codecs for decoding a message that is sent using Java codecs ?

yes, you can

@cyberpower715 Yes, it is possible to decode messages in C++ that were encoded in Java and vice versa. Aeron uses C++ SBE codecs for the Aeron Archive client while connecting to the Archive that is written in Java.
For the C++/Java interop you need to ensure that the same schema is used for both languages.


added rethink promise API

RethinkDB optionally returns promise if a callback is not provided. Updated the API for the promise API.

thanks mate!


jxl Version not updated automatically

This version is not updated automatically and is too old it doesn't exists anymore in your chartmuseum
https://github.com/jenkins-x/jxr-versions/blob/bd37f181b2f05d7837780c101caaecfcea81ace3/charts/jx-labs/jxl-boot.yml#L2

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.


Feature/core #81

Better doc!

Codecov Report

Merging #83 into develop will increase coverage by 6.05%.
The diff coverage is 98.96%.

@@             Coverage Diff             @@
##           develop      #83      +/-   ##
===========================================
+ Coverage    92.85%   98.91%   +6.05%
===========================================
  Files           22       31       +9
  Lines          672      919     +247
===========================================
+ Hits           624      909     +285
+ Misses          48       10      -38

Impacted Files
Coverage Δ

...asses/nn/models/classification/alexnet/__init__.py
100.00% <ø> (ø)

glasses/utils/ModuleTransfer.py
100.00% <ø> (ø)

test/test_ResNet.py
100.00% <ø> (ø)

...lasses/nn/models/classification/resnet/__init__.py
94.44% <66.66%> (-0.25%)
:arrow_down:

...ses/nn/models/classification/mobilenet/__init__.py
98.59% <98.59%> (ø)

glasses/nn/blocks/residuals.py
100.00% <100.00%> (ø)

glasses/nn/models/__init__.py
100.00% <100.00%> (ø)

glasses/nn/models/classification/__init__.py
100.00% <100.00%> (ø)

...sses/nn/models/classification/densenet/__init__.py
100.00% <100.00%> (ø)

glasses/nn/models/classification/se/__init__.py
100.00% <100.00%> (+100.00%)
:arrow_up:

... and 27 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 ba50f42...8c82cc3. Read the comment docs.


IsEmpty and IsNotEmpty decorater mixed up?

Hello, I just tried to validate my class with the @IsEmpty and @IsNotEmpty , however I noticed, that these two decoraters do what the other should do. But when validating them manually, they show the correct result.
export function validObject(obj, groups, res): any {
    options.groups = groups;
    let valObj = validate(obj, options);
    valObj.then(errors => {
        if(errors.length > 0) {
            res.status(400).json(errors);
        }
    })
}

yields following result
[
  {
    "value": "test",
    "property": "_name",
    "children": [],
    "constraints": {
      "isEmpty": ""
    }
  },
  {
    "value": "",
    "property": "_accessCode",
    "children": [],
    "constraints": {
      "isNotEmpty": ""
    }
  }
]

With the same request I validated the class inside the constructor manually with new Validator() and printed the result.
         let val = new Validator();
        console.log(`Var name: '${this._name}'`);
        if(val.isEmpty(this._name)) { console.log("isEmpty")    }
        else                        { console.log("isNotEmpty") }

        console.log(`Var access: '${this._accessCode}'`);
        if(val.isNotEmpty(this._accessCode)) { console.log("isNotEmpty") }
        else                                 { console.log("isEmpty")    }

printed result:
Var name: 'test'
isNotEmpty
Var access: ''
isEmpty

Nevermind, after looking deeper into the code, i noticed that i misinterpreted both and that they are both working as intended.


Add Grouped Bar Chart

Overview
Adds the bar chart for grouped responses.
Connects #22
Demo
Many countries

Few countries

Notes
The bars auto-resize to fit the height of the container. We could probably calculate a larger height for the container based on the number of countries/regions included if we'd rather the container grow instead of the items shrink.
Testing Instructions

Select a number of countries or regions
Select a question with a bolded answer (ie 'Head of Household')
The chart should render the data correctly
The chart should show all selected countries

@mmcfarland #1 is fairly easy. but unfortunately, I don't think there's any available way to align the order of the stacks. For some reason, the legend items are explicitly reversed when you use keys, and you can't provide separate keys for the legend and the bar chart. It appears that this was fixed for non-canvas bar charts, so maybe posting an issue to the library would help with this one.


How to handle OverlayActions?

Hi~ @SchabanBo
I tried to set onClose's callback but got type trouble.
actions: OverlayActions(      onClose: () {         // do some thing       }, ),
show below error:
The argument type 'Future Function()' can't be assigned to the parameter type 'Future Function(dynamic)?'
May you provide overlayActions  use case sample ?

I  use below resolve:
onClose: (dynamic value) {
  // do some thing
  return Future.delayed(Duration.zero);
},


Microsoft.VC++2008Redist-x86/x64 Cannot Upgrade

Brief description of your issue
Inability to upgrade Microsoft Visual C++ 2008 Redistributable x86 and x64
ID: Microsoft.VC++2008Redist-x86 Version : 9.0.30729.4148
ID: Microsoft.VC++2008Redist-x64
Version : 9.0.30729.4148
Available : 9.0.30729.6161
Source : winget
Steps to reproduce
have Microsoft VC++ 2008Redist x86 or x64

Run Command : winget upgrade

Output :

C:\Users\pc>winget upgrade
Name                                            Id                           Version        Available      Source
Microsoft Visual C++ 2008 Redistributable - x86 Microsoft.VC++2008Redist-x86 9.0.30729.4148 9.0.30729.6161 winget
Microsoft Visual C++ 2008 Redistributable - x64 Microsoft.VC++2008Redist-x64 9.0.30729.4148 9.0.30729.6161 winget
2 upgrades available.

Run command : winget upgrade --all

Output :

C:\Users\pc>winget upgrade --all
No applicable update found.
same problem using ID
Expected behavior
Specific ID is shown and allows upgrade.
Actual behavior
Endless loop of finding the package.
Environment
Windows Package Manager (Preview) v1.2.3411-preview
Windows: Windows.Desktop v10.0.19044.1415
Package: Microsoft.DesktopAppInstaller v1.17.3411.0

Duplicate of #1413


Failed to load signatures file default.yml: open default.yml: no such file or directory

I get Failed to load signatures file default.yml: open default.yml: no such file or directory when running on an org. I have no problem with the help command.

@Nyon-spec ny Can you try building from the develop branch, I believe this was a know issue and was fixed. f the error still persists in that branch we can tae a look further.
Thanks!

@Nyon-spec I found the issue and fixed it with 74f73938826c8856c6da69f88d982ea01c45aadd


StreamBlock creation via command not working

Hello,
I am just trying to set up some stream blocks programatically and I just faced an error using your instructions in readme. When I connected to the STC and obtained a port handler I tried to create stream block using the command:
sb_handle = stc.create('streamBlock', port_handle)
This ended up with an error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: create() takes 2 positional arguments but 3 were given

Inspecting create() method in stcpythonrest.py I have found that the method works if I use it like this:
sb_handle = stc.create('streamBlock', under=port_handle)
However, this seems to me like kind of bypassing part of create() methods behavior. I am using Python 3.6.8. Am I doing something wrong?

StcPythonRest emulates the native python bindings for the STC automation API so that it can be used as drop-in replacement without requiring changes to existing python code. Looking at the our API documentation, for the native bindings, it looks like the under keyword argument is needed. For StcHttp (what is referred to in the readme), that does not require the under keyword.

Thanks for your reply. I will keep that in my mind. Is it possible to read these nuances somewhere? I  found this one inspecting the code.

The StcHttp module is the one documented in this repository for use as a client. Like I mentioned, StcPythonRest is meant to be a drop-in replacement for our native language bindings so familiarity with the existing Python bindings is somewhat assumed. The native API documentation is available on our support site at https://support.spirent.com/SpirentCSC/SpirentDownloadsAppPage?activeTab=download but will require a login. Chapter 23 of the Automation Programming Guide has the information on the Python API.

Ok, great. I have access to the docs so I will inspect the Python API docs. Cheers!


KMP String Algorithm implementation

Have you read the Contributing Guidelines on Pull Requests?
YES
Description
(Write your answer here.)
Checklist

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

Related Issues or Pull Requests
(Write your answer here.)

@HarshCasper  please review my pull request

@ankitaggarwal23 can you please review my pr

@zhcet19 We don't accept PRs without any corresponding Issue. As It becomes difficult to find issue number.


tests: files update for nocase fix

Ticket
If your pull request is related to a Suricata ticket, please provide
the full URL to the ticket here so this pull request can monitor
changes to the ticket status:
Redmine ticket:

Merged in #1347, thanks!


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 2314 ms

Resolved: Bofrost.lu performance has improved in c9db874 after 35 minutes.


Add field offsets

Inspired by @Sunmish's RACS catalogues, it's good to have some extra (pre-computed) info for the position of a component in a field

Also adding tweaks to imager tempfile behaviour


[SPARK-15112][SQL] Allows query plan schema and encoder schema of a Dataset have different column order

What changes were proposed in this pull request?
This PR fixes two issues that cause the data corruption bug in SPARK-15112:

Dataset.schema should comform to Dataset.resolvedTEncoder.schema rather than the schema of the underlying logical plan
An ExpressionEncoder doesn't require input column order to be the same as column order of its own schema. Essentially, it performs a projection to adjust column order at runtime. This is particularly useful for data sources that support schema evolution, in which cases column order of the merged result schema can be non-deterministic.
Please refer to this JIRA comment for more details.

Optimization rule EmbedSerializerInFilter may produce wrong output column order.
This PR fixes this issue by adding a Project to adjust output column order when necessary.
Please refer to this JIRA comment for more details.

How was this patch tested?
A regression test case is added to DatasetSuite.

Test build #57978 has started for PR 12952 at commit 4ff62e0.

Test build #57980 has started for PR 12952 at commit bd6da7d.

cc @cloud-fan @rxin @yhuai

Test build #57981 has started for PR 12952 at commit a315e52.

Test build #57980 has finished for PR 12952 at commit bd6da7d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57980/
Test FAILed.

Merged build finished. Test FAILed.

Test build #57981 has finished for PR 12952 at commit a315e52.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57981/
Test FAILed.

Test build #57983 has started for PR 12952 at commit 26b7687.

Test build #57983 has finished for PR 12952 at commit 26b7687.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57983/
Test FAILed.

Merged build finished. Test FAILed.

Test build #57978 has finished for PR 12952 at commit 4ff62e0.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/57978/
Test FAILed.

Test build #58002 has started for PR 12952 at commit 9412b9b.

Test build #58002 has finished for PR 12952 at commit 9412b9b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58002/
Test FAILed.

Merged build finished. Test FAILed.

Test build #58133 has started for PR 12952 at commit fd89dcb.

@cloud-fan @marmbrus Just reverted the projection added in Dataset.toDF() because it doesn't handle order of inner nested fields. The behavior of the current PR should be exactly the same as branch-1.6 now.

Test build #58133 has finished for PR 12952 at commit fd89dcb.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58133/
Test FAILed.

Making Dataset.schema conform to Dataset.resolvedTEncoder.schema introduced multiple regression. Seems that Spark 2.0 implicitly assumes that Dataset.resolvedTEncoder.schema is consistent with Dataset.logicalPlan.schema. However, they don't. These two may differ in column ordering (either top-level columns or inner nested fields) and nullability.
Trying to figure out a more consistent fix.

Seems that Spark 2.0 implicitly assumes that Dataset.resolvedTEncoder.schema is consistent with Dataset.logicalPlan.schema

Can you explain more?  Which part of the code is making that assumption?

Test build #58706 has started for PR 12952 at commit 728ea99.

Test build #58706 has finished for PR 12952 at commit 728ea99.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58706/
Test FAILed.

@marmbrus Sorry for the late reply. This issue is a little bit complicated. I made the following (long) summary for explanation and future reference.

Encoders lookup fields by name. Namely, within a Dataset, schema of its encoder and schema of its underlying logical plan may have different field orders. This is true for either top-level fields or inner nested struct fields. Encoders are able to adjust field order at runtime according its own schema by binding expressions by name at analysis time.
We observe that encoders have the following characteristics:

Encoders are somewhat similar to projections as they are able to adjust field orders, but projections only handle top-level fields.
You can't alias encoder field names as they are either hard coded (primitive encoders always have field name "value"), or decided by case class/Java bean field names.

Datasets and encoders in Spark 1.6
In Spark 1.6, for a Dataset ds, we have the following facts:

ds.schema == ds.resolvedTEncoder.schema
ds.toDF().schema == ds.logicalPlan.schema

Together with the two aforementioned characteristics, we have the following inconsistent results under Spark 1.6:

Datasets with a single primitive field
val df1 = sqlContext.range(3)

df1.schema
// StructType(StructField(id,LongType,false))

val ds1 = df1.as[Long]

ds1.toDF().schema

ds1.schema
// StructType(StructField(value,LongType,false))
//                        ~~~~~
//                             Conforms to encoder schema

ds1.printSchema()
// root
// |-- id: long (nullable = false
//     ~~
//       Conforms to logical plan schema as `printSchema()`
//       delegates `toDF().printSchema()`

ds1.show()

// +-----+
// |value|  <-- Conforms to encoder schema
// +-----+
// |    0|
// |    1|
// |    2|
// +-----+

ds1.toDF().schema
// StructType(StructField(id,LongType,false))
//                        ~~
//                          Conforms to logical plan schema

Datasets of case classes
val df2 = Seq("foo" -> 1, "bar" -> 2).toDF("b", "a")

df2.schema
// StructType(
//   StructField(b,StringType,true),
//   StructField(a,IntegerType,false)
// )

case class T(a: Int, b: String)

val ds2 = df2.as[T]

ds2.schema
// StructType(                          (1) Fields reordered by encoder
//   StructField(a,IntegerType,false),
//   StructField(b,StringType,true)
// )

ds2.printSchema()
// root                                 (2) Field order inconsistent with (1)
//  |-- b: string (nullable = true)
//  |-- a: integer (nullable = false)

ds2.show()
// +---+---+
// |  a|  b|
// +---+---+
// |  1|foo|
// |  2|bar|
// +---+---+

ds2.toDF().show()
// +---+---+
// |  b|  a|
// +---+---+
// |foo|  1|
// |bar|  2|
// +---+---+

Conclusions:

It's a bug that ds.schema can be inconsistent with ds.printSchema().

When ds.schema is inconsistent with ds.logicalPlan.schema, we may end up with inconsistent column order and/or inconsistent column names. However:

At least data are always correct.
These inconsistencies don't introduce too much troubles as Dataset in Spark 1.6 has quite limited features.

Issues introduced in Spark 2.0
In Spark 2.0, two issues are closely related to SPARK-15112:

While unifying DataFrame and Dataset API, ds.schema was accidentally changed to ds.logicalPlan.schema instead of ds.resolvedTEncoder.schema
This change fixes inconsistency between ds.schema and ds.printSchema() as now both of them uses logical plan schema.
However, it led to an even worse inconsistency:
val df3 = Seq("foo" -> 1, "bar" -> 2).toDF("b", "a")

df3.show()
// +---+---+
// |  b|  a|
// +---+---+
// |foo|  1|
// |bar|  2|
// +---+---+

case class T(a: Int, b: String)
val ds3 = df3.as[T]

ds3.show()
// +---+---+
// |  b|  a|    <-- Order of field names are is inconsistent
// +---+---+        with field data now.
// |  1|foo|
// |  2|bar|
// +---+---+

This is because ds3.show() uses ds3.schema, which equals to ds3.logicalPlan.schema, to show field names, but field order in data rows are adjusted by encoders.

EmbedSerializerInFilter implicitly assumes that de/serializer pairs don't change field order
The EmbedSerializerInFilter optimization rule may optimize plan fragments like
SerializeFromObject
 Filter
  DeserializeToObject   (1)
   <child-plan>         (2)

into
Filter
 <child-plan>

by embedding the deserializer expression into the Filter condition expression. Namely, when filtering an input row, the new Filter operator always deserializes the input row into a Scala object, and then uses the object as argument to invoke the user-provided Scala predicate function.
The problem here is that, in the original plan fragment, output field order at (1) may differ from field order at (2) because DeserializeToObject may adjust field order using encoder deserialization expressions.
However, in the simplified fragment, Filter.output simply inherits child plan output. But deserialization expressions resolved by encoder still adjust field order as before. Thus Filter may output corrupted data because of wrong input column order.

Fixes tried in this PR and why they don't work
Dataset schema issue
For the first issue, this PR tried to restore behavior of Spark 1.6, namely making ds.schema == ds.resolvedTEncoder.schema again.
This doesn't work because we migrated a lot more operations to Dataset API from DataFrame API, and these operations don't play well with the old Dataset schema constraint. Here are some examples:
Hard coded primitive encoder field name
Primitive encoders (e.g. Encoder[Long] always has only a single field named "value".
spark.range(10).schema
// StructType(StructField(value,LongType,false))
//                        ~~~~~
//                             Conforms to encoder schema

val df4 = Seq(Tuple1("foo")).toDF("str")

df4.schema
// StructType(StructField(str,StringType,true))

df4.as[String].schema
// StructType(StructField(value,StringType,true))
//                        ~~~~~
//                             Conforms to encoder schema

Nullability mismatch
val df5 = Seq.empty[Tuple1[Option[Int]]].toDF("i")
val df6 = Seq.empty[Tuple1[Int]].toDF("i")
val df7 = df5.intersect(df6)

df7.schema
// StructType(StructField(i,IntegerType,true))
//                                      ~~~~

Field i in df7 is expected to be false according to Intersect.output, but is now true because df7.schema is decided by df5.resolvedTEncoder.schema rather than df5.logicalPlan.schema. Thus nullability change made in Intersect is overwritten.
EmbedSerializerInFilter issue
This PR tried to fix this issue by adding a projection in EmbedSerializerInFilter when necessary to adjust field order. However, I soon realized that Project doesn't cover inner nested fields.
Another alternative is never eliminate the de/serializer pair when the pair reorders fields. But this may miss lots of useful optimization opportunities.
Proposed fix
After considering all the aforementioned cases, I think we need to meet the following constraints to fix these issues:

ds.schema should be defined as ds.logicalPlan.schema
ds.resolvedTEncoder.schema and ds.logicalPlan.schema may differ in field names and/or field nullability, but not in data types.

In this way, field names and nullability won't be overwritten by encoder schema, and we don't to worry about issues like the one in EmbedSerializerInFilter.
To do this, we can adjust field order (including inner nested fields) of the logical plan when constructing a Dataset to make sure the order is consistent with encoder.
One tricky stuff in our current encoder design is that, it couples field reordering and Java object de/serialization. I think it's more reasonable to move field reordering into Project. Namely, make Project to be able to handle inner nested fields.
For example, say field a is of type string, and field b is of type STRUCT<b1: INT, b2: STRING>, when feeding a row like
[b: [b2: 'foo', b1: 1], a: 'bar']

to
Project a, b

The projection should output
[a: 'bar', b: [b1: 1, b2: 'foo']]

Note that order of inner fields b1 and b2 is also adjusted accordingly.
There can be several benefits if we can decouple field reordering and Java object de/serialization:

Simplifies encoder implementation as it only needs to handle de/serialization now.
It would be trivial to do the aforementioned logical plan field order adjust when constructing a Dataset
Can be potentially useful for pruning nested fields

@liancheng, thanks for the thorough explanation.  I think I understand the problem now and I agree with the proposed constraints.  A few questions:

One tricky stuff in our current encoder design is that, it couples field reordering and Java object de/serialization. I think it's more reasonable to move field reordering into Project. Namely, make Project to be able to handle inner nested fields.

Are you proposing that was always use a project to copy from one row to another such that the input is in the correct order for the deserializer's constructor?  If so, I worry that that is too expensive.  While its complicated, I think its pretty useful for us to be able to construct objects from an input row, independent of the ordering.

While investigating and fixing this issue, hit several other Dataset / encoder issues along the way, which are included in this umbrella ticket: SPARK-15631
After offline discussion with @marmbrus and @cloud-fan, decided to close this one in favor of a minimum fix that only addresses the typed filter data corruption issue, and then fix other issues that are not that critical in follow-up PRs. See #13362.


fix(material/tabs): use buttons for paginator also tab-header and mdc

This is a follow-up PR to https://github.com/angular/components/pull/14640 / https://github.com/angular/components/commit/e8919bcf4b614fde6f6614fcaaf799b97f9702b5
I think these other templates should be updated to button usage too, so we can keep consistency.
Uses button elements, rather than styled div-s for the paginator buttons. This has the advantage of being more accessible, if we decided to make them focusable, and it stops calling the click listeners when the button is disabled (currently we do some expensive checks in them when we don't have to).

I added button reset styles to mdc with the last commit update (were forgotten before).


add capability of setting location from which check will probe

Without this all probes get set to the default region - NA.
You can also set EU or APAC.  This pull request is just to add the parameter:
probe_filters
It can be set to one of "region: NA", "region: EU", "region: APAC"

looks good, thanks!


v2 Book says Cargo generates main.rs automagically, it does not

This is not a Cargo issue. Cargo is working fine. This is a description of a discrepancy that I have found between Cargo's behavior and the v2 Book.
In section 1.2 the book says:

Cargo has generated a "Hello World!" for you, just like the one we wrote earlier! So that part is the same.

However, running the command cargo new <crate_name> to create a new Cargo project does not, in fact, generate this "Hello World" file. It instead generates a lib.rs that does not compile to an executable, but rather to a variety of library resource files. To clarify:

Expected (according to docs): Cargo generates a main.rs containing Hello World code
Actual: Cargo generates a lib.rs with no "concrete" code at all
Resolution: Update the docs to indicate that Cargo will not, in fact, generate this file

Updated title to better reflect that the issue is with the Book and not with Cargo

Never mind. I did not run the cargo new command with the --bin switch, thus the crate was not created as a binary project, so no main.rs was generated.

Wait, this is still an issue. The book doesn't say to use the --bin flag, so following the book to the letter doesn't work as expected. The book still needs to be updated. The docs Getting Started section is correct though.


Fix syntax highlighting on code pane open/close

Fixed

https://github.com/user-attachments/assets/f37dd0de-c08e-4b92-bcd7-3f0eaab052b9

lol the branch name thank you!


tgt: 1.0.81 -> 1.0.82

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tgt/versions.
meta.description for tgt is: "iSCSI Target daemon with RDMA support"
meta.homepage for tgt is: "https://github.com/fujita/tgt"
meta.changelog for tgt is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/tgtadm had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/tgtimg had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/.tgt-admin-wrapped had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/tgt-admin had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/tgt-setup-lun had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin/tgtd had a zero exit code or showed the expected version
0 of 6 passed binary check by having a zero exit code.
0 of 6 passed binary check by having the new version present in output.
found 1.0.82 with grep in /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82
found 1.0.82 in filename of file in /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82

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

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
tgt

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82
ls -la /nix/store/29a9mg67hlsyahx3kqhc534iia25c4a7-tgt-1.0.82/bin

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

1 package built:

tgt

Maintainer pings
cc @johnazoidberg for testing.

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

1 package built:

tgt

The only change (https://github.com/fujita/tgt/commit/7a2da00cc5109dd4bb376af9bb25d955f27f2593) LGTM, ping me for revert if anything goes wrong.


♪ symbol causing problems

I have repeated issues with punctuation being read aloud whenever it is followed by a music note symbol: ( ♪ ).
This happens whenever a character is singing, such as The Wandering Minstrel, Jehantel (from the Bard questline), and even Tataru when she is humming a tune.
So what I have gotten is:

.♪ : When a verse ends with a period ( . ) directly before a music note symbol ( .♪ ) It reads "(any lyrical line) dot"
～♪ : When a verse ends with a tilde ( ～ ) directly before a music note symbol ( ～♪  ) It reads "(any lyrical line) tilde"
,♪ : When a verse ends with a comma ( , ) directly before a music note symbol ( ,♪) It reads it as "(any lyrical line) comma"
-♪ : When a verse ends with a dash ( - ) directly before a music note symbol ( -♪ ) It reads it as "(any lyrical line) dash"

I think these are the four most common occurrences in which the music note causes the punctuation or other symbol to be read aloud, but there may be more. What I cannot figure out, yet, is how to silence those punctuations from being verbalized when directly followed by a music note symbol without any spaces, as generally the ♪ always comes after punctuation without any spaces.
It can be quite annoying, especially when the song or ditty has multiple lines to it.
Originally posted by @SaphiraGrace in https://github.com/karashiiro/TextToTalk/discussions/62#discussioncomment-8868244

I imagine this should be a simple fix by just ignoring this symbol when parsing text

That's what I thought too but I'm not entirely sure how to write that in a lexicon to be ignored. I'm still a little new to this

It's just an issue with how the plugin reads text, the dev should be able to fix it

Oh, thanks! Cool! I will wait for a solution. Has been a thing as long as I can remember, probably was something that just never got adjusted yet.


Add writeProperty

Hello,
I Added client-side write function for BACnet objects, allowing the server to update the property.
This can be useful for updating the device in the other direction. ;)

@debraysimon nice !  Was it compatible with yabe and another edge-bacnet node-red setup ?
I will merge this request with master and npm when i get the chance over the next week or so. Busy with other things at the moment

Yes @bitpool-dev, I used yabe to develop these functions. So normally it's compatible with the others :)
Ok perfect ;)

Nice. Added to master !


[wip] Flat bundles for each possible entry

[ ] fix tests (dunno why some tests are failing atm)

Danger works again :tada: Tests are still failing though :cry:

Yeah, seems like some problem with jest not hooking into require for whatever reason. Need to dig into this later.

Ok, I think I'v fixed the tests, let's see what CI has to say about that 😉

@philpl @mxstbr the PR is ready for code review 🎉

yarn dev is failing

@maciej-ka good catch, gonna fix it when refactoring the scripts

Ready for another round of code review. I've decided not to introduce possibility of granular builds because it would complex the code quite a bit for imho questionable gains. Let me know what do you think about it.

:heart: how you improved readability of packages.json and rollup config. I should find a moment for an indepth review tonight.

@mxstbr I've checked outputs with and without process shimming - there was no difference. I've removed virtual module resolver few lines above, it also doesn't seem to have any impact. process.env should be replaced in umd bundles (like it is) and process generally shouldnt be used for anything else, so it shouldn't appear nowhere in the bundles.
Still unsure why this was configured though in the first place. I see you changed policy of replacing the process.env just few days ago - this PR will change that again, but I believe it will change it to the more correct usage:

umd bundles should have it replaced
any other bundle, no matter if its es, cjs, targeting react-native or primitives should have it untouched and replacing should be done by the consumer's bundle

Yep, that's the way it was with the last change too except now we have more bundles where it should be left untouched! This LGTM, can we rebase on master? Then I'll publish an alpha release so people can try this.

Ah, yeah, forgot that lib covered most of those builds before. Rebase coming in a minute

Done, no conflicts so it was even quicker ;) Feel free to squash my commits or whatever, im unsure what flow do you like here. Going out for a Christmas party, so won't be able to tweak this in any way myself till tomorrow.

Enjoy the party!!

Gotta merge #1371 into master and then rebase this again first though, otherwise the alpha's going to be broken haha :blush:

Rebased on top of master with #1371, going to publish an alpha 👍

You have push rights to my fork, if you want to rebase yourself

Done, I've published a first version of this as styled-components@alpha! (v2.3.3-0) Going to write a quick post in our community about this so folks can start testing and give feedback whether it works.

https://spectrum.chat/thread/185e0225-20c8-4e21-a12a-1113101bfcc9


[New Feature Request] Add a Brazilian Portuguese profile with my dictionary word file link

Hey @tadashi-aikawa ! I am the discord user who contacted you on the Obsidian Discord Server! See exchange:

As requested, here is my word/dictionary fork that I made that works with your plugin:
https://raw.githubusercontent.com/ThomasEricB/words-pt-uncompressed-with-utf8-txt/master/wordsList.txt
This world file would also fix #281 ! Thank you for your time!

Hi, @ThomasEricB :)
Thanks for creating an issue and following #281 !

@ThomasEricB
I have added it to the documentation 👍
https://tadashi-aikawa.github.io/docs-obsidian-various-complements-plugin/4. Options/4.6. Custom dictionary complement/⚙ Custom dictionary paths/#language-dictionary-file-url


Whatbox uses different Sonarr/Radarr version numbers

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Whatbox uses a custom version of Sonarr/Radarr. So when recylarr tries to do the version detection it does not recognize the version of Sonarr/Radarr.
Sonarr: whatbox-e4c0e80
Radarr: whatbox-9b3770a
Expected Behavior
The profiles and quality profiles sync correctly.
Steps To Reproduce

Run recyclarr against the Whatbox sonarr/radarr.

Environment & Versions
See above

Recyclarr Log File(s)
[13:40:36 DBG] HTTP Request: GET http://REDACTED:19025/api/v3/system/status?apikey=REDACTED
[13:40:36 DBG] HTTP Response: 200 GET http://REDACTED:19025/api/v3/system/status?apikey=REDACTED
[13:40:36 DBG] HTTP Body: {"appName":"Sonarr","instanceName":"Sonarr","version":"<IP_ADDRESS>503","buildTime":"2022-12-25T19:43:34.2377865Z","isDebug":false,"isProduction":true,"isAdmin":false,"isUserInteractive":false,"startupPath":"/usr/share/sonarr","appData":"/home/orbitron/.config/Sonarr","osName":"gentoo","osVersion":"2.9","isMonoRuntime":true,"isMono":true,"isLinux":true,"isOsx":false,"isWindows":false,"mode":"console","branch":"master","authentication":"forms","sqliteVersion":"3.40.1","urlBase":"","runtimeVersion":"<IP_ADDRESS>","runtimeName":"mono","startTime":"2023-01-18T18:42:22.183511Z","packageUpdateMechanism":"builtIn"}
[13:40:36 DBG] Sonarr Version: <IP_ADDRESS>503
[13:40:36 ERR] Exception
Recyclarr.TrashLib.ExceptionTypes.ServiceIncompatibilityException: Release profiles require Sonarr v3. Please use custom_formats instead or use the right version of Sonarr.
at Recyclarr.TrashLib.Services.Sonarr.Capabilities.SonarrCapabilityEnforcer.Check(SonarrConfiguration config) in /home/runner/work/recyclarr/recyclarr/src/Recyclarr.TrashLib/Services/Sonarr/Capabilities/SonarrCapabilityEnforcer.cs:line 34
Configuration YAML
# Configuration specific to Sonarr
sonarr:
    # Set the URL/API Key to your actual instance
  - base_url: http://localhost:19025
    api_key: REDACTED

    # Quality definitions from the guide to sync to Sonarr. Choice: anime, series, hybrid
    quality_definition: series

    # Release profiles from the guide to sync to Sonarr.
    # You can optionally add tags and make negative scores strictly ignored
    release_profiles:
      # Series
      - trash_ids:
          - EBC725268D687D588A20CBC5F97E538B # Low Quality Groups
          - 1B018E0C53EC825085DD911102E2CA36 # Release Sources (Streaming Service)

Sonarr / Radarr Logs
No response

Couple of things wrong with this request:

Whatbox-specific Sonarr/Radarr apps, if they are custom forks (as well as any forks in general) are not supported. Recyclarr only supports the official Radarr and Sonarr applications at the moment.
This is not a defect, but rather a feature request.

If you want to use custom forks of these applications with Recyclarr, it's up to you and the upstream developers to ensure compatibility is identical to that of the official versions. For starters, the version numbers should be the same, since the version numbers are used to determine compatibility.


Fix for Trinket slots?

Heya, first of all great fix, I lost everything i had to water destroying the grave and been annoyed with the gravestones mod since.
Something else I noticed when that happened is that things i had equipped via trinket slots were dropped normally instead of going into the gravestone leaving them vulnerable to despawning or burning.
I dont know much about modding but I assume this is because the gravestones ask for specific inventory slots instead of the whole inventory which is why stuff in trinket slots didn't get saved.

You're right, people on my server have experienced this too. I didn't think of this initially, but that's a good idea and probably within scope of the mod. I'll take a look.

That's funny, the original gravestones mod has a class called TrinketsCompat but I guess it doesn't work?

OMG guys plz fix we have the same issue

Alright sorry it's been a really long time. If this is still an issue, what version of Trinkets are you using?

Can you try version 1.1.0 and let me know if it's still an issue?

I was using Trinkets version 3.7.1 for Fabric 1.20.1. I will try the same setup with 1.1.0 and get back to you.

Thanks! FYI I tested against trinkets 3.7.2, so could you try that if 3.7.1 doesn't work?

I tried tests with all slots filled and with only trinket slots fill and it looks like everything works fine, both with 3.7.2 and 3.7.1. Thanks for the fix, this means 1.20.1 fab is back on the menu for me and another friend!


SingleFrameAllocator and multiple world instances.

Hi again!
For a while I've been running in to an issue with seemingly random crashes when allocating or freeing memory.
I think I've finally tracked it down to having multiple PhysicsWorld instances sharing a SingleFrameAllocator.
I know multiple worlds probably isn't a common use case, but here's what I've found, and potential solutions.
The problem is related to user code being able to cause allocations from the SingleFrameAllocator outside of PhysicsWorld::Update().
There may be multiple things that can trigger this, but most commonly, I'll use setTransform() and then testOverlap() or testCollision() and this will sometimes cause new elements to be added to mLostContactPairs via computeBroadPhase -> removeNonOverlappingPairs -> addLostContactPair.
Usually this is fine, because mLostContactPairs is processed in the next physics update before SingleFrameAllocator is cleared/reallocated.
But if another PhysicsWorld::Update() is called before then, the mLostContactPairs will be invalidated.
Here's an example timeline:
WORLD INSTANCE 1:
  -PhysicsWorld::update()
    -add lost contacts, process and clear lost contacts
    -resetFrameAllocator()
  -user code
    -setTransform(), testOverlap(), causes mLostContactPairs.add() <--------------------------------------------------------

WORLD INSTANCE 2:
  -PhysicsWorld::update()
    -add lost contacts, process and clear lost contacts
    -resetFrameAllocator() <--------------------------------------------------------
  -user code
    -move object, add lost contacts

WORLD INSTANCE 1:
  -PhysicsWorld::update()
    -lost contacts added in previous user code are now potentially being overwritten by other allocations,
      or if the SingleFrameAllocator was resized, they will be in deallocated memory!

Potential solutions:

Always call PhysicsWorld::update() immediately AFTER any user code related to that instance, rather than before which I'm doing.
Have a separate SingleFrameAllocator for each PhysicsWorld instance.
Add a flag to redirect SingleFrameAllocator to a different allocator when outside of PhysicWorld::update()
Remove the resetFrameAllocator() from PhysicWorld::update() and call it manually after all updates are done.

No rush addressing this, I've implemented solution 3 as a workaround.
And apologies if this has been addressed already in develop branch, I haven't dug in deep enough to confirm if it's been fixed there.
Thanks again for your time and this excellent library!

Thanks a lot for taking the time to report this (with all the details). I don't have the time to improve this right now but I will take a look when I have some time.


Enable multisite in schematics

Now to enable auto-config, customer needs just to omit the config for context.baseSite (thanks to https://github.com/SAP/cloud-commerce-spartacus-storefront/issues/1810).
At the same time it's recommended not to have any context config, because it will be overwritten with the one from backend.
So we need a way to omit producing config for context.baseSite in schematics - just to enable auto config of the site.

QA steps:

build local schematics pack
use schematics pack on fresh angular app without defining baseSite

Expected result:
Schematics should apply Spartacus adjustments & omit context property in Storefront configuration


Azure driver: Fix issue #4244

This will fix my issue #4244. We are currently using this for our private Gitlab environment to use the auto scaling feature from Gitlab runner with docker-machine and Microsoft Azure.
Signed-off-by: Mario Kleinsasser<EMAIL_ADDRESS>

@shin Would it be possible for you to check why the travis build failed please? Because the error I in travis is not clear to me and the build of another patch of mine worked without problems. Thank you!

@shin @StefanScherer @nathanleclaire any comments on this from the committers? Is something missing or unclear? Can I do something to get this commited? Thank you!

ping @shin-

Oh, now I see my mistake 😊 ... shin- not shin. 😄 Sorry!

Hi @kleinsasserm , I believe you need to run a gofmt pass on this PR for the Travis tests to pass.

@shin- I wrote you an email offline, because I do not spam the PR. I do not get why the Travis build is complaining about lint, but make lint doesn't. Maybe you can have a look in the next days.

@shin- Can you have a look at my email? I would like to do this PR the correct way, but I need some help here. Anyone else who can have a look at my PR and my mistake(s) 😊 ?

This is what I'm seeing on Travis in terms of linting errors:
drivers/azure/azure.go:393:2: redundant if ...; err != nil check, just return error instead.
drivers/azure/azure.go:436:2: redundant if ...; err != nil check, just return error instead.
drivers/exoscale/exoscale.go:458:2: redundant if ...; err != nil check, just return error instead.
drivers/hyperv/hyperv.go:180:2: redundant if ...; err != nil check, just return error instead.
drivers/vmwarevcloudair/vcloudair.go:448:2: redundant if ...; err != nil check, just return error instead.
drivers/vmwarevsphere/vsphere.go:938:2: redundant if ...; err != nil check, just return error instead.
libmachine/persist/filestore.go:56:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/arch.go:150:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/boot2docker.go:258:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/coreos.go:130:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/debian.go:141:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/rancheros.go:139:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/redhat.go:113:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/redhat.go:181:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/suse.go:205:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/ubuntu_systemd.go:151:2: redundant if ...; err != nil check, just return error instead.
libmachine/provision/ubuntu_upstart.go:160:2: redundant if ...; err != nil check, just return error instead.
make: *** [lint] Error 1
mk/validate.mk:18: recipe for target 'lint' failed
make: *** [build validate] Error 2

None of those seem related to your changes, so I'm guessing they might be caused by an update of the linter that made it stricter. I'll look into fixing those in master when I have some time. Thank you for your patience.

 I just wanted to make sure that it wasn't my mistake :smile:

@kleinsasserm I just merged #4266 , so if you can rebase this PR we should be able to move forward. Thank you for your patience! :+1:

@shin- I've updated the PR. Hopefully it fits the needs and I made it the correct way. I think that this version is more informative too but it "feels" a little bit complicated. Should we log the err at this point as log.Warn? I looked at the code of the other methods but I am not sure. Sorry for the delay, but I was busy in the last days and it took me some time to test this change and to understand the returns in detail. :smiley:

Looks pretty good to me! Thanks for following up, and thank you again for your contribution!

 Thank you!


NoneTypes of labels

Hi I am trying to run the classification tasks. I can successfully run my code at first time. But I get error when I remove the results of first run and rerun the model. The error is:
Adding new problem country_cls, problem type: cls
Adding new problem gender_cls, problem type: cls
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-9-50089851ce6e> in <module>
      4 train_bert_multitask(problem='country_cls&gender_cls', num_gpus=2,
      5                      num_epochs=2, params=params,
----> 6                      problem_type_dict=new_problem_type, processing_fn_dict=new_problem_process_fn_dict)

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/run_bert_multitask.py in train_bert_multitask(problem, num_gpus, num_epochs, model_dir, params, problem_type_dict, processing_fn_dict, model)
    106                 problem_name=new_problem, problem_type=problem_type_dict[new_problem], processing_fn=new_problem_processing_fn)
    107     params.assign_problem(problem, gpu=int(num_gpus),
--> 108                           base_dir=base_dir, dir_name=dir_name)
    109     params.to_json()
    110

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/params.py in assign_problem(self, flag_string, gpu, base_dir, dir_name, is_serve)
    191         self.prepare_dir(base_dir, dir_name, self.problem_list)
    192
--> 193         self.get_data_info(self.problem_list, self.ckpt_dir)
    194
    195         if not is_serve:

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/params.py in get_data_info(self, problem_list, base)
    255
    256                     self.data_num_dict[problem] = len(
--> 257                         list(self.read_data_fn[problem](self, 'train')))
    258                     self.data_num += self.data_num_dict[problem]
    259                 else:

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/data_preprocessing/preproc_decorator.py in wrapper(params, mode)
     13         if os.path.exists(pickle_file) and params.multiprocess:
     14             label_encoder = get_or_make_label_encoder(
---> 15                 params, problem=problem, mode=mode)
     16             return create_single_problem_generator(
     17                 func.__name__,

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/utils.py in get_or_make_label_encoder(params, problem, mode, label_list, zero_class)
    136             label_encoder = LabelEncoder()
    137
--> 138             label_encoder.fit(label_list, zero_class=zero_class)
    139             label_encoder.dump(le_path)
    140         else:

/lustre03/project/6007993/chiyu94/bert-multitask-learning-master/bert_multitask_learning/utils.py in fit(self, y, zero_class)
     28         self.encode_dict = {}
     29         self.decode_dict = {}
---> 30         label_set = set(y)
     31         if zero_class is None:
     32             zero_class = '[PAD]'

TypeError: 'NoneType' object is not iterable

Could you provide the pre-processing function of gender_cls problem? You need to return input_list and target_list from that function.

Here is the pre-processing function:
import json
@preprocessing_fn
def gender_cls(params, mode):
    lines = []
    json_file = open("gender2ind.json")
    gender_to_id = json.load(json_file)

    with tf.gfile.Open("/home/chiyu94/projects/rrg-mageed/chiyu94/apda/data/train_u.tsv", "r") as f:
        reader = csv.reader(f, delimiter="\t")
        lines = []
        i =0
        for line in reader:
            if i == 0:
                i += 1
                continue
            else:
                lines.append(line)
    train_data_no = [tweet[3] for tweet in lines]
    train_labels = [gender_to_id[tweet[2]] for tweet in lines]

    lines = []
    with tf.gfile.Open("dev_u.tsv", "r") as f:
        reader = csv.reader(f, delimiter="\t")
        lines = []
        i =0
        for line in reader:
            if i == 0:
                i += 1
                continue
            else:
                lines.append(line)

    test_data_no = [tweet[3] for tweet in lines]
    test_labels = [gender_to_id[tweet[2]] for tweet in lines]

    label_encoder = get_or_make_label_encoder(params, 'gender_cls', mode, train_labels+test_labels)

    train_data = [tokenizer.tokenize(sent) for sent in train_data_no]
    test_data = [tokenizer.tokenize(sent) for sent in test_data_no]

    if mode == TRAIN:
        input_list = train_data
        target_list = train_labels
    else:
        input_list = test_data
        target_list = test_labels

    return input_list, target_list

You may need to check the value of train_labels+test_labels. Also, you don't need to call get_or_make_label_encoder manually.

I checked the labels what are integers. If I train the two task separately, there isn't issue. But the "NoneType" error come up if I train the two task together.

I fixed the problem, there are some problem with my environment. I have one more question for multitask classification. If my tasks require same input sequence ("problem='country_cls|gender_cls'). In the 'preprocessing_fn' whether I need to define 'input_list' separately.

If my tasks require same input sequence ("problem='country_cls|gender_cls'). In the 'preprocessing_fn' whether I need to define 'input_list' separately.

Yes. BTW, if your tasks shares the same inputs, you can try to chain them using &. But you have to make sure the order of input_list and target_list are the same for two problems. In this way, you should be able to save a few training steps.

Thanks! It means that each task preprocessing_fn should define and return two variables, an input_list and a target_list. But if the tasks share the same input the system will only take one as the input_list, is is correct?

If you use & to chain problems then yes. For example, if you specify problem='country_cls&gender_cls, then at each iteration, the program will check whether the input_list from country_cls and gender_cls are exactly the same. If it's not, an assertion error will be raised.

Gotcha. Thanks very much!!!


Simulate click in javascript button

I want to execute somebutton.click() (some button part of the toolbar) on clicking a custom javascript button.
Is there a function to do that already?

Sorry, I did not quite understand that. Could you elaborate?

Is there a way to click some button in the toolbar (call its click function) from inside the code?


Fix typo in defaults/main.yml

There was a little typo in the snmpd_groups for v2c. That makes the v2c metrics not responding to telegraf snmp pluguin requests when using the default name values.

Build failed, I manually added your PR. Thanks!


Correction at line 398

Removing repeated 'h' to 'x'. PR for the Issue #135

@googlebot I signed it!

@googlebot rescan

CLA bot did not add the label to this PR for some reason, but the CLA signature looks good.


Update nodename label to hostname

Hey
I've been wondering if it would not be a better idea to relabel __journal__hostname into hostname rather than nodename which seems more specific to the Kubernetes node concept.
Would you agree?

That's fair. I'm not sure where nodename came from tbh, I must've copied it from an example. That being said, this is a breaking change. Can put that value in both the nodename and hostname labels going forward to keep it backwards compatible?

That's fair. I'm not sure where nodename came from tbh, I must've copied it from an example. That being said, this is a breaking change. Can put that value in both the nodename and hostname labels going forward to keep it backwards compatible?

I was thinking it would be a breaking change so maybe instead you could add extraRelabelConfigs as a config parameter? I know you can overwrite the default job config but that requires providing a path to a file.
I was hoping to add a relabel statement into the config area of the add on or even provide the entire yaml into additionalScrapeConfigs rather than a file.
What are your thoughts?


quanto compatibility for cpu/disk offload

What does this do ?
This PR is needed for quanto integration in transformers if the user wants to perform cpu/disk offload.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Indexer Can Be Installed as a Helm Sub-Chart for Metacat in Kubernetes

In order to support being deployed as a helm sub chart for metacat k8s deployment (see Metacat issue 1665), indexer needs:

cleanup of hardcoded parameters in yaml templates and values files
code changes to support healthchecks -- liveness & readiness probes
and a placeholder for anything else that is discovered during this process...

That sounds great. Do you have a list of those hardcoded params? I didn't think there were many (any), as we've been able to deploy both locally on RD and on several namespaces of the dev cluster. Let's generate a list of what needs to be de-hardcoded, and it should be straightforward to fix those.

As I work through getting everything up and running, I'm collecting the values I've had to override in a separate yaml file. Most of the overrides are because of the namespace being hardcoded (d1index), and while some of those will always need to be overridden manually, there is scope to auto-configure some of them.
There are also the credentials for rmq and solr that need to be moved to secrets

Done - see branch feature-49-subchart-changes-image-auto-publish, resulting in PRs:
#50
#53
#55
#56
#57
...plus corresponding work in metacat feature-1665-misc-fixes branch


Latest RN 0.69 on iOS: (0,_.scanBarcodes) is not a function

Using the latest RN 0.69, I get the following error on iOS:
Frame Processor threw an error: (0,_.scanBarcodes) is not a function. (In '(0,_.scanBarcodes)(frame,types,options)', '(0,_.scanBarcodes)' is undefined)
In<EMAIL_ADDRESS>(18:73):1:137
    @[native code]
<EMAIL_ADDRESS>(31:33):1:425
    @[native code]

package.json
"react-native-reanimated": "^2.8.0",
"react-native-vision-camera": "^2.13.5",
"vision-camera-code-scanner": "^0.2.0"

I get the same error if I don't use the useScanBarcodes hook, but invoke useFrameProcessor myself:
const frameProcessor = useFrameProcessor((frame) => {
    'worklet';
    const detectedBarcodes = scanBarcodes(frame, types, options);
    runOnJS(setBarcodes)(detectedBarcodes);
  }, []);

I'm also have the same issue, I have created a private package so it can be used across the companies multiple projects.
From my example build it works fine, but when I try to integrate it with the company's project it gives me this error.

Any solution regarding this issue so far guys.

I'm also experiencing this issue

Same problem on Android, haven't tested iOS.

Hello, have you found any solution for the problem?

Hello, have you found any solution for the problem?

Unfortunately not. I don’t see much if any progress being made in this matter either. I think I’m going to have to use the deprecated rn-camera package instead :(

the same issue, any update?

I use this way, it's worked
// Alternatively you can use the underlying function:
//
const frameProcessor = useFrameProcessor((frame) => {
'worklet';
const detectedBarcodes = scanBarcodes(frame, [BarcodeFormat.QR_CODE], { checkInverted: true });
runOnJS(setBarcodes)(detectedBarcodes);
}, []);

I use this way, it's worked
// Alternatively you can use the underlying function:
//
const frameProcessor = useFrameProcessor((frame) => {
'worklet';
const detectedBarcodes = scanBarcodes(frame, [BarcodeFormat.QR_CODE], { checkInverted: true });
runOnJS(setBarcodes)(detectedBarcodes);
}, []);

RN Version?

Aynı sorun, herhangi bir güncelleme var mı?

Getting the same issue. Any update?

I was able to get around this issue by recreating scanBarcodes in my component. The whole thing looks something like this:
import 'react-native-reanimated';
import React, { FunctionComponent, useEffect, useCallback, useRef, useState } from 'react';
import { StyleSheet, Text } from 'react-native';
import { Camera, useCameraDevices, useFrameProcessor } from 'react-native-vision-camera';
import type { Frame } from 'react-native-vision-camera';
import { BarcodeFormat } from 'vision-camera-code-scanner';
import type { CodeScannerOptions, Barcode } from 'vision-camera-code-scanner';
import { runOnJS } from 'react-native-reanimated';

interface Props {
  children: React.ReactNode;
  torch: boolean;
}

export const ScannerCamera: FunctionComponent<Props> = ({ children, torch }) => {
  const devices = useCameraDevices();
  const device = devices.back;
  const camera = useRef<Camera>(null);
  const [barcodes, setBc] = useState<Barcode[]>([]);

  function scanBarcodes(frame: Frame, types: BarcodeFormat[], options?: CodeScannerOptions): Barcode[] {
    'worklet';
    // @ts-ignore
    // eslint-disable-next-line no-undef
    return __scanCodes(frame, types, options);
  }

  const frameProcessor = useFrameProcessor((frame) => {
    'worklet';
    const detectedBarcodes = scanBarcodes(frame, [BarcodeFormat.QR_CODE], { checkInverted: true });
    runOnJS(setBc)(detectedBarcodes);
  }, []);

  const [hasPerms, setPerms] = React.useState(false);
  const [permsGotten, setPermsGotten] = React.useState(false);

  const requestPermissions = useCallback(async () => {
    const permission = await Camera.requestCameraPermission();
    setPerms(permission === 'authorized');
    setPermsGotten(true);
  }, []);

  useEffect(() => {
    void requestPermissions();
  }, [requestPermissions]);

  if (!permsGotten) return <Text>loading</Text>;
  if (device === undefined || !hasPerms) return <Text>no perms</Text>;
  return (
    <>
      <Camera
        ref={camera}
        style={StyleSheet.absoluteFill}
        device={device}
        isActive={true}
        torch={torch ? 'on' : 'off'}
        frameProcessor={frameProcessor}
        frameProcessorFps={5}
      >
        {children}
      </Camera>
      {barcodes.map((barcode, idx) => (
        <Text key={idx} style={styles.barcodeTextURL}>
          {barcode.displayValue}
        </Text>
      ))}
    </>
  );
};

const styles = StyleSheet.create({
  barcodeTextURL: {
    fontSize: 20,
    color: 'white',
    fontWeight: 'bold',
  },
});


XP tracker header disappears when using the "Reset Others" right-click option

It re-appears once new experience is gained (in any skill)

Hmm, just spent about an hour running back commits all the way to when the xptracker was implemented and it looks like this has always been a bug - working on a fix now

EDIT: This IS a regression, I reverted Adam's 3 previous commits for xptracker and it's working properly again

On top of the "reset other" issue, the total experience doesn't recalculate at all after using "reset" - Thoughts on reverting the other 2 commits?


How can it stops the build process on "error"?

having
"build": "yarn run test | webpack --config ./webpack.config.js -p"
and this in webpack
{
  enforce: 'pre',
  test: /\.js$/,
  loader: 'standard-loader',
  exclude: /(node_modules)/,
},

when standard fires an error, why it looks just like a Warning in Webpack?
How can it stops the build process?

I've added an "error": true config to the loader. See docs. Setting this should do what you want.


Add python3-networkmanager

Add python3-networkmanager for all recent ubuntu distributions. Keep python-networkmanager as is.
This is necessary to manipulate the NetworkManager service from ROS2 python nodes.
Package details: https://packages.ubuntu.com/bionic/python3-networkmanager

It's been over a month with no response from the contributor, so I'll close this out for now.  Please feel free to fix the comments from @nuclearsandwich and re-open when you have time.  Thanks for the contribution.


is it possible to use --post-filter to exclude a post from a batch :saved download?

hello,
i ran into an issue that causes a :saved download - instaloader --login=[username] :saved --slide 1 --no-compress-json - to fail in the middle of the process: https://github.com/instaloader/instaloader/issues/2161#issuecomment-2110936294
is it possible to run instaloader using --post-filter to skip the post causing the error? perhaps using the shortcode property?
i tried instaloader --login=[username] :saved --slide 1 --no-compress-json --post-filter="shortcode!=[ShortCode]" but instaloader returned Invalid filter: [ShortCode] not a Post attribute.
any help is greatly appreciated

it looks like there may have been missing quotes around the shortcode. just tried instaloader --login=[username] :saved --slide 1 --no-compress-json --post-filter="shortcode!='[ShortCode]'" and it seems to be working, but it will be a while until it gets to the video that threw the original TypeError: expected string or bytes-like object, got 'NoneType'.


Thoroughly test command lines

Hello @matteobachetti! Thanks for updating the PR.

In the file srttools/core/tests/test_imager.py, following are the PEP8 issues :

Line 675:22: E127 continuation line over-indented for visual indent


@threlte/flex

@threlte/flex
This package will introduce a wrapper for yoga-layout.
Features

<Flex> and <Box> components
Automatically centered anchor if a child is not a <Box> component (DOM anchors are upper-left aligned whereas Three.js object anchors are centered)
Full type support on props
prop setter architecture makes it easy to type props
A class parser can be introduced to use a class-based syntax as opposed to individual props, a parser for tailwind-like classes is included
Slot props and bindings to force a layout reflow
The reflow is batched and will never happen more than once per frame

Examples
The package contains a SvelteKit app with examples located at the route '/', run pnpm dev at packages/flex to get started.
https://github.com/threlte/threlte/assets/46897060/5f381f09-b5aa-4c30-8c9b-f430647a5a57
To Do

[ ] Documentation
[ ] More examples?
[ ] More parsers?

Credits
Some calculations are taken from react-three-flex, thanks.

Because changesets is not allowing us to do an alpha release only for this package, we'll release this into the wild without a documentation. As long as 0.1.0 is not reached this package is considered alpha and likely to break anytime. Use at your own risk.


Can we force/filter the titles to be Titlecaps if it's TITLECAPS

@will-byrne and I worked on a React component implementation of this, but it was so icky, and broke for "eLife Assessments", making it "ELife Assessments". We both agreed this probably needs fixing on import.

@will-byrne and I worked on a React component implementation of this, but it was so icky, and broke for "eLife Assessments", making it "ELife Assessments". We both agreed this probably needs fixing on import.