Tensorflow (0.11.0) returns error while running training and testing scripts.

Due to some constraint i am using Tensorflow version 0.11.0, which i installed using bellow commands:
export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-0.11.0-cp27-none-linux_x86_64.whl
pip install --ignore-installed --upgrade $TF_BINARY_URL
After installation i am successfully able to import Tensorflow in python:
cvsion@cvsion:~$ python -c 'import tensorflow as tf; print(tf.__version__)'
0.11.0

cvsion@cvsion:~/Deeplearning/DeepTensorFlow/tensorlayer$ python
Python 2.7.12 (default, Dec  4 2017, 14:50:18)
[GCC 5.4.0 20160609] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
>>>

but when i am running my training script its giving error:

Traceback (most recent call last):
File "./testing_nvidia.py", line 8, in
import tensorlayer as tl
File "/home/cvsion/Deeplearning/DeepTensorFlow/tensorlayer/tensorlayer/init.py", line 23, in
from . import distributed
File "/home/cvsion/Deeplearning/DeepTensorFlow/tensorlayer/tensorlayer/distributed.py", line 9, in
from tensorflow.python.training import session_run_hook
ImportError: cannot import name session_run_hook

Any idea to resolve above issue

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce

Have I written custom code = Yes
OS Platform and Distribution=  Ubuntu 16.04
TensorFlow installed from = export TF_BINARY_URL=https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-0.11.0-cp27-none-linux_x86_64.whl
pip install --ignore-installed --upgrade $TF_BINARY_URL
Bazel version= N/A
CUDA/cuDNN version = CUDA 8.0/cuDNN 6.1
GPU model and memory: 12GB
Exact command to reproduce: python ./testing_nvidia.py

I'm sorry, but 0.11.0 is past our support window.

As we do not support 0.11.0 , will be closing this request. Please try latest versions. Thank you.


[ExtendedSplashScreen][Android] Content does not match native splash screen

I'm trying to use the Uno Toolkit's ExtendedSplashScreen control to create an extended splash screen for our app using this
documentation. While I'm now able to display an extended splash screen, it's slightly different from the native splashscreen, causing a jarring transition. I was wondering if you had any guidance for how to make sure the extended splashscreen can match exactly the native splash screen (plus a loading wheel of some kind). This functionality is why we previously used nventive's
ExtendedSplashScreen library.
- @juliecantin on Teams

The video was taken on an emulator running android 11. The sample was created by the Uno wizard, so I imagine it targets the latest version of the SDK. The app I'm having issues with, targets Uno 4 and Android SDK 13

extendedsplash.webm

I also tested the extended splash screen on my physical pixel 6 Android 13 device, and here the extended splash screen doesn't seem to automatically include the native splash screen at all. Recording here (from the same sample app, no change except to make the background of the main page white)

https://github.com/unoplatform/uno.toolkit.ui/assets/4793020/15ad93f6-4f0b-4b24-bd0f-e0e080a5fb4a
Repro app:
extendedsplash.zip

For android 13-14, it says in the documentation that it wont show the native splashscreen image

I hadn't understood that. This makes the control not particularly useful for my app. The bug still exists for Android 11-, though.

For android 13-14, it says in the documentation that it wont show the native splashscreen image.

@nickrandolph are we understanding that correctly? We shouln't be seeing a blank screen on android 12+ though, no?


ksysguard desktop file does not have an Exec line

Issue description
Related to #40915
kbuildsycoca5
kbuildsycoca5 running...
kf5.kservice.services: The desktop entry file "/run/current-system/sw/share/applications/org.kde.systemmonitor.desktop" has Type= "Application" but no Exec line
kf5.kservice.sycoca: Invalid Service :  "/run/current-system/sw/share/applications/org.kde.systemmonitor.desktop"

Steps to reproduce
Run kbuildsycoca5 with ksysguard installed.
Technical details

system: "x86_64-linux"
host os: Linux 4.14.41, NixOS, 18.03.132405.ee80654b526 (Impala)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.0.1
channels(root): "nixos-18.03, nixos-unstable, nixpkgs"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

ksysguard and its corresponding .desktop file exists in two places which is clearly wrong:

plasma-workspace.bin, and
ksysguard

@adisbladis @bkchr

I think this issue is already solved with latest master?

@bkchr Are you referencing #42639

No, I did not read the description correctly...
But with the following pr: https://github.com/NixOS/nixpkgs/pull/43288
It should be really solved ^^

Sounds great, when it's pulled I'll test and close.

@Chiiruno the pull request was merged.

Okay thanks.
I'll test this tomorrow and close.

It works!


When updating exiting cell we get error:  Is a directory

When updating exiting cell we get error:
File "/opt/conda/lib/python3.9/site-packages/jupyterlab_vre/handlers.py", line 181, in post
os.remove(path)
IsADirectoryError: [Errno 21] Is a directory: '/home/jovyan/NaaVRE/cells/fetch-laz-files-23-03-22/.ipynb_checkpoints'

Solved we now only delete files:
        if os.path.exists(cell_path):
            for files in os.listdir(cell_path):
                path = os.path.join(cell_path, files)
                if os.path.isfile(path):
                    os.remove(path)


Broken pre-read links on lessons

Describe the bug
There are broken pre-read links in our lesson pages.
To Reproduce
Steps to reproduce the behavior:

Go to https://wayfair.github.io/awesome-learning/courses/Testing/intro-to-unit-testing/
Click on "5 great reasons for running tests"
See 404

Expected behavior
These links should open new windows to the desired link.

I'm not able to reproduce this one, maybe fixed by https://github.com/wayfair/awesome-learning/pull/13

Looks good now via the fix in #13


[FEATURE] React Painting Game

Description
In this game user can paint or draw whatever he wants using different colors.

Easy to use
can select different shapes
can select different colors
can select width of pen
Complete react game

Screenshots

Additional information
https://github.com/ssitvit/Games-and-Go/assets/119161467/3babf81f-712d-4290-afb6-9a895bb495df

@raj03kumar Please assign me this issue


Replace Argo Events stack with Provider Service component

Closes #359
Tasks

[ ] Remove old VAI eventing server code (argo/providers/vai/eventing_server.go and argo/providers/vai/provider.go)
[ ] Implement http webhook for kfp (same as for vai)
[ ] Write integrated tests (possibly with docker-compose spinning up pubsub)
[ ] Documentation updated

I have a question about the way we've implemented the event processing for providers.
Up until this point, the steps to introduce a new provider (I think) were:

Build a publish a docker image that handles CRUD for resources in the new provider and handles events coming out of the new provider
Deploy a new Provider resource with that provider image specified

What we've basically done in this PR is move the event processing logic for the existing providers to a separate service.
So as far as I can tell, the steps are now:

Build a publish a docker image that handles CRUD for resources in the new provider
Deploy a new Provider resource with that provider image specified
Raise a PR in the KFP Operator repo to extend the provider-service module with eventing logic for the new provider

Questions:

Am I missing something?
If not, do we think this is a problem?


Upgrade workflow

Incorporate trigger on changes to R files.  This will allow to only trigger the setup once a student submits changes to their own scripts.

I found a better way by tangling only the R chunks that include functions. This, and a combination  with another script, allows for the functionality I first wanted


fix: Crash when overwriting builtin with walrus operator (fixes #416)

It appears that check_newvar was called with &e1,  but then new_var was mistakenly called with e, which caused the parser to generate garbage opcodes, leading to crashes.
Added test case to verify this behavior.

Wow, you nailed it. I'm impressed because it was hard to find. I cross-checked with Tasmota bytecode compilation and it does not introduce any regression.
Awesome job!


I am getting this isue. Plz help.

error: Validation failed: No action for key "trainer.weights_save_path" to check its value.

It might be a pytorch_lightning version issue. Cound you try older version of pytorch_lightning and find out which version can run?

Thansk a lot for your prompt response.
Can you plz tell which version of pytorch_lightning have you your in the original code?

I am still waiting

You can refer to some previous reported issue to solve this problem.
https://github.com/PediaMedAI/ViTASD/issues/6

You can refer to some previous reported issue to solve this problem.
#6

okay thanks
But I am still facing this one:
File "/content/ViTASD/train_affectnet.py", line 72, in init
self.model: torch.nn.Module = ResNetASD(
NameError: name 'ResNetASD' is not defined
plz help

https://github.com/PediaMedAI/ViTASD/issues/2#issuecomment-1361149465


Native-like API

While this is definitely a great Lua binding for nuklear, it does feel a bit thin. I wonder if it would be possible to design an API that feels more like a love module than a C wrapper?

Thanks for the input. I've been contemplating one possible solution to this problem: replacing the _begin/_end pairs with a single function that takes a closure as a parameter. This looks especially clean in Moonscript, changing overview.lua to:
checkA = value: false
checkB = value: true
radio = value: "A"
selectA = value: false
selectB = value: true
slider = value: 0.2
progress = value: 1
colorPicker = value: "#ff0000"
property = value: 6
edit = value: "Edit text"
combo = value: 1, items: {"A", "B", "C"}

->
  nk.window "Overview", 100, 100, 600, 450, {"border", "movable", "title"}, ->
    nk.menubar ->
      nk.layout_row "dynamic", 30, 1
      nk.menu "Menu", nil, 120, 90, ->
        nk.layout_row "dynamic", 40, 1
        nk.menu_item "Item A"
        nk.menu_item "Item B"
        nk.menu_item "Item C"
    nk.layout_row "dynamic", 400, 3
    nk.group "Group 1", {"border"}, ->
      nk.layout_row "dynamic", 30, 1
      nk.label "Left label"
      nk.label "Centered label", "centered"
      nk.label "Colored label", "left", "#ff0000"
      nk.tree "tab", "Tree Tab", ->
        nk.tree "node", "Tree Node 1", ->
          nk.label "Label 1"
        nk.tree "node", "Tree Node 2" ->
          nk.label "Label 2"
        nk.spacing 1
        nk.button "Button", ->
          print "Button pressed!"
        nk.spacing 1
        nk.checkbox "Checkbox A", checkA
        nk.checkbox "Checkbox B", checkB
    nk.group "Group 2", {"border"}, ->
      nk.layout_row "dynamic", 30, 1
      nk.label "Radio buttons:"
      nk.layout_row "dynamic", 30, 3
      nk.radio "A", radio
      nk.radio "B", radio
      nk.radio "C", radio
      nk.layout_row "dynamic", 30, 1
      nk.selectable "Selectable A", selectA
      nk.selectable "Selectable B", selectB
      nk.layout_row "dynamic", 30, {.35, .65}
      nk.label "Slider:"
      nk.slider 0, slider, 1, 0.05
      nk.label "Progress:"
      nk.progress progress, 10, true
      nk.spacing(2)
      nk.label "Color picker:"
      nk.button nil, colorPicker.value
      nk.layout_row "dynamic", 90, 1
      nk.color_picker colorPicker
    nk.group "Group 3", {"border"}, ->
      nk.layout_row "dynamic", 30, 1
      nk.property "Property", 0, property, 10, 0.25, 0.05
      nk.spacing 1
      nk.label "Edit:"
      nk.edit "box", edit
      nk.layout_row "dynamic", 5, 1
      nk.spacing 1
      nk.layout_row "dynamic", 30, 1
      nk.label "Combobox:"
      nk.combobox combo, combo.items
      nk.layout_row "dynamic", 5, 1
      nk.spacing 1
      nk.layout_row "dynamic", 30, 1
      nk.tooltip "Test tooltip" if nk.widget_is_hovered!
      x, y, w, h = nk.widget_bounds!
      nk.contextual 100, 100, x, y, w, h, ->
        nk.layout_row "dynamic", 30, 1
        nk.contextual_item "Item A"
        nk.contextual_item "Item B"
      nk.label "Contextual (Right click me)"

This might be one step in the right direction. Are there any suggestions you have?

Well, I will say that LOVE does have some things that open/close already, such as love.graphics.push and love.graphics.pop. I think my first order of business would be to organize the various components into their own namespaces:

love.gui.frame.*
love.gui.layout.*
love.gui.widget.*
etc.

But that might be too much since I believe LOVE's API generally only goes 3 levels deep, and my above suggestion would be 4 levels deep.
Maybe @slime73 has some suggestions?

I guess if you were to go with the LOVE API, you'd want to use camelCase instead of snake_case (much to my own dismay).

I hesitate to use the love.* namespace for anything but official LOVE modules and functions. Making camelCase work would be really simple, though.

Well sure, I am just giving an example. My reasoning here is I think
nuklear would be a good fit as a native LOVE module. It seems small and
simple and intuitive enough, and LOVE reeeeeally needs a GUI module to
round off its main functionality. I've opened a discussion in the LOVE
rep
about this.

Landon Manning
<EMAIL_ADDRESS>On 3 December 2016 at 13:06, Kevin Harrison<EMAIL_ADDRESS>wrote:

I hesitate to use the love.* namespace for anything but official LOVE
modules and functions. Making camelCase work would be really simple, though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/keharriso/love-nuklear/issues/5#issuecomment-264651581,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkB_MgTUhH-WL8PnA6fnO4J1mmJfjQ0ks5rEaGUgaJpZM4LDNgZ
.

GG github :|

The bindings now use camelCase to be consistent with LOVE.

Awesome! <3

It looks like both camelCase and snake_case are working... My code can execute both, and the .so file I built seems to be about twice the size at previous one. Thoughts?

Yes, both cases work - hopefully that's not a problem. As for the binary size, are you sure you are using the same compiler options as before? I uploaded binaries for v1.1 and the size difference seems to be around 10kB.

I had used your build last time. I don't mind if both work if the file size isn't significant.

Yeah, if you used CMake without setting CMAKE_BUILD_TYPE to "Release", then it would make sense that the binaries are much larger. Hopefully the release binaries for v1.1 work for you.

Cool. Any particular reason why you want both snake_case and camelCase?

I don't want to break backwards compatibility needlessly. snake_case is now undocumented and will probably be removed in a future update, but I think it makes sense to wait for a major v2.0 to break compatibility. See also Semantic Versioning.

Fair enough.


mysql can not start

Info:

Docker version ($ docker --version): 18.03.0
Laradock commit ($ git rev-parse HEAD): master
System info (Mac, PC, Linux): Mac
System info disto/version: 10.13.4

@oberoivarun

Is this a blank database? Seems like there is something wrong with your data.

Thanks,the problem has been solved.
I delete .laradock/data/mysql


Info - Compiled CSS

Hi, how do you inject compiled css inside the html? I'm try to achieve the same result but i don't like to much the injection (like gulp-inject)

Hi @equinusocio,
We don't inject css compiled directly to the html.
The way that we have to add css inside the html is the next one:
We have a .PUG file where we make a include from a .CSS file that has been compiled by Gulp from a .SCSS file.
In the "Source" folder you can see the .PUG, .SCSS and .COFFEE files that we use to create the component.
Thank you!

Thank you man.


chore: Automatically merge Dependabot PRs

Codecov Report

Merging #261 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #261   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines          479       479
  Branches        29        29
=========================================
  Hits           479       479

Flag
Coverage Δ

#unittests
100.00% <ø> (ø)

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


ScanRange fails to deal with predicate OR

CREATE TABLE orders (
            order_id BIGINT,
            user_id INTEGER,
            date INTEGER);
CREATE MATERIALIZED VIEW orders_count_by_user AS
SELECT user_id, date, count(*) AS orders_count FROM orders GROUP BY user_id, date;

SELECT * FROM orders_count_by_user WHERE user_id = 'a' or user_id = 'b'

cc @xxchan

Yes, it's far from complete 😇 https://github.com/singularity-data/risingwave/issues/3477

No plan to support more cases recently


Difference between app & ChatGPT web interface?

If I have the app set to use the ChatGPT library, is there any difference between using the app vs using the official ChatGPT web interface? I'm not super familiar with how the API works. I have subscribed to the ChatGPT Plus service, but would prefer to use your app if it's an identical experience.

Hi, actually I'm not sure. You should ask the ChatGPT library creator.
Here is the link:
https://github.com/alfianlosari/ChatGPTSwift
Please update this issue when you have more info on this library :)

Now that library is using the official OpenAI's API so I think it is actually the same thing as the web interface.
If you have more questions or ideas or feedback you can now open threads in the discussion section.
https://github.com/Yoddikko/yoddChatGPT/discussions/categories/ideas


getDocument(...).then is not a function

The following code loads the PDF file successfully from a filepicker into a byte array, but fails PDF.js with

Uncaught TypeError: pdfjsLib.getDocument(...).then is not a function

Code:
<html>
<head>
<script src="https://mozilla.github.io/pdf.js/build/pdf.js"></script>
</head>
<body>
<input type="file" id="file">
</body>
<script>
pdfjsLib.GlobalWorkerOptions.workerSrc = 'https://mozilla.github.io/pdf.js/build/pdf.worker.js';
document.getElementById('file').onchange = function(event) {
    var file = event.target.files[0];
    var fileReader = new FileReader();
    fileReader.onload = function() {
        var typedarray = new Uint8Array(this.result);
        console.log(typedarray);
        pdfjsLib.getDocument(typedarray).then(function(pdf) {
            console.log(pdf);
        });
    };
    fileReader.readAsArrayBuffer(file);
}
</script>
</html>

Mostly coming from the main answer of https://stackoverflow.com/questions/22048395/how-to-open-a-local-pdf-in-pdfjs-using-file-input.
How to make it work?
PS: I have seen a few similar questions like https://github.com/mozilla/pdf.js/issues/9075 closed because they lacked a minimal reproducible example.

As shown in the JSDocs, getDocument returns a PDFDocumentLoadingTask instance: https://github.com/mozilla/pdf.js/blob/8fc1126b5a2b6d2fa0cfa98a061882ef21c1abc9/src/display/api.js#L169-L180
which has a promise property which contains the information you want here:
https://github.com/mozilla/pdf.js/blob/8fc1126b5a2b6d2fa0cfa98a061882ef21c1abc9/src/display/api.js#L453-L459
According to the code/docs quoted above, the following thus works:
  const loadingTask = pdfjsLib.getDocument(/* data here */);
  loadingTask.promise.then(pdfDocument => {
    // The document is loaded here...
  });

Generally speaking, note that linking to code at https://mozilla.github.io/pdf.js/build/ is never a good idea (since those files change with every merge).
Please always use official releases instead, see https://github.com/mozilla/pdf.js/releases
Finally, when opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md

Thanks @Snuffleupagus for your answer. Finally just the .promise. was missing, I'll remember this.
More generally, is it mandatory to use asynchronous code? For example:
pdfjsLib.getDocument(typedarray).promise.then(function(pdf) {
        for (var i = 1; i <= pdf.numPages; i++) {
            pdf.getPage(i).then(function(page) {
                var viewport = page.getViewport({scale: 1});
                var context = canvas.getContext('2d');
                ...

does not work because it would require multiple canvas:

Error: Cannot use the same canvas during multiple render() operations.

Is there a way to use synchronous code instead?
page = pdf.getPage(i);

in replacement of pdf.getPage(i).then(function(page) { is not working.

More generally, is it mandatory to use asynchronous code?

Yes; note also that generally speaking a lot of modern JavaScript code is asynchronous.

does not work because it would require multiple canvas:

Error: Cannot use the same canvas during multiple render() operations.

The solution is simple though, either: create a new canvas for each page, or wait for one page to finish rendering before starting the next one.

Is there a way to use synchronous code instead?

No, for all intents and purposes all PDF.js API-methods are asynchronous at this point in time.

Thanks @Snuffleupagus for your reply. Just to conclude, how would you transform:
for (var i = 1; i <= pdf.numPages; i++) {
        pdf.getPage(i).then(function(page) {
           ...
        });
}

to make it "wait for one page to finish rendering before starting the next one"?


Compose Web Support?

Any plans for Compose Web Support? The big thing about navigating with web is browser url / paths need to be supported.

Could we split it info two steps?

Support for current stack-based approach on a same URL
URL/History API support

@ScottPierce @fmasa  I have completed adding Compose Web support to my fork of voyager, compose_bloc, in js_platform_support branch. I did not merge yet to main because I am still doing some tests.
Now about adding navigation based on url/paths, do you have some ideas of the kind of API you would like?
I was thinking of implementing an api similar to one the most popular flutter libraries:
auto_route or go_router. What do you think?

@beyondeye Thank you for maintaining this project. It's great!
So I think an important part of this is the String / path based navigation. It needs to integrate well for web. In addition though, I think it has benefits beyond just web for other platforms as well. One of the reasons Google has pushed String based navigation for Android, especially in large projects, is its ability to remove at least one layer, and in some case, 2 layers, from build dependency trees, speeding up build times for very large projects.
Typically for applications, when features are developed and compiled independently of one another, there needs to be a gradle module that depends on all the features, and actually creates the navigation tree so they can navigate to one another via Strings. Android has worked around this via reflection + the Android Manifest. The first iteration doesn't need to implement this, but ideally it'd allow for something like this to be implemented in the future (via compiler plugins or perhaps KSP).
Also, once you allow String based navigation, you are 80% of the way there to deep linking. Whatever String based navigation voyager supports for web, it should also support multiplatform deep linking.

@ScottPierce. Thank you for your feedback. It was very helpful. I will start working on string/path based navigation and update about my progress.

@adrielcafe It'd be nice to get official support for this in the main Voyager project.

@ScottPierce @fmasa
Hi all I have completed implementation of path-based navigation in version 0.13.0 of compose_bloc
see the documentation here
It would be very helpful if you could give me some feedback

@beyondeye I'm looking into this now since @adrielcafe has been non-responsive. I'm trying to understand the vision here. Why is it part of compose_bloc, instead of a fork, or even an additional layer on top of voyager?

Good question. When I started working on compose_bloc, my idea was to actually make it an additional library on top of voyager. But voyager development was stale, with several outstanding bugs (related to lifecycle management), so I decided to incorporate a fork of voyager with bugs fixes and improvement inside compose_bloc, with the intention to merge back the code in voyager eventually or at least a part of it. I would like to hear what are @adrielcafe intentions for the future of the project. I think that there are several good design ideas in voyager, but it is falling behind other projects like decompose because it is not maintained, for example in fields like support for web or native platforms. Now speaking specifically about the web platform, lately I have incorporated a fork of router_compose in compose_bloc. In this case the reason is because I don't agree with the design decision of the author of router_compose to integrate routing with the composition. I know that this is the way it is done in the original navigation library for compose  for Android, but I think that it creates an unnecessary coupling between app logic and ui. I discussed about this with router_compose author but he prefers it that way.

@beyondeye It looks like the library maintainer is accepting PRs now.

HI @ScottPierce, A colleague of mine start a routing library, we first tough bring directly to voyager, but after discussing we plan to it be fully multiplatform and generic and also support voyager.
https://github.com/programadorthi/kotlin-routing
We soon should have the first release there, this would bring Path Routing to Voyager.

Already using it. Thanks!


Use generics for event target?

Event and React SyntheticEvent are currently defined as something like:
declare class Event {
    target: EventTarget;

Which means that the exact type of target is not known
var Foo = React.createClass({
    render() {
        return (
            <input type="checkbox" onChange={this._onChange} />
        );
    },

    _onChange(evt: SyntheticEvent): void {
        console.log(evt.target.checked); // Flow error (property 'checked' not found in EventTarget)
    }
})

It seems like this could be solved if Event and SyntheticEvent were generic types, something like:
declare class SyntheticEvent<TElement : EventTarget> {
    target: TElement;

_onChange(evt: SyntheticEvent<HTMLInputElement>): void {
    console.log(evt.target.checked); // Should work since we know that evt.target is HTMLInputElement
}

Any plans here? Working with forms would be much more pleasant with a fix.

We've definitely considered this, but it trades convenience for soundness. Do you think it's worth making the model unsound?
For example,
declare var elem: HTMLElement;
elem.addEventListener("mouseover", (event: Event<HTMLInputElement>) => {
  event.target.value; // event.target isn't necessarily HTMLInputElement here
});

To make this sound, we would need to constrain addEventListener to only accept callbacks that are compatible with the event type, which means enumerating every possible event type and defaulting to something strict.

Do you think it's worth making the model unsound?

Personally I think that it's worth adding, even if it makes the code unsound. I don't think it's any worse than what people would be doing today - Any event handler code today is most likely using a catchall type like Object or any, or the developer is writing their own typedef. For example, in my code I do something like this:
_onChange(evt: {target: {checked: boolean}}): void {
  console.log(evt.target.checked);
}

Also worth mentioning: We've also been chatting a bit about having type-parameter defaults (along the lines of type Event<Target=EventTarget> = ...).
This would let users write something like (event: Event<>) => ... if they want to be strict, or (event: Event<HTMLInputElement>) => ... if the structure of the app is such that the event is definitely always targeting an input element.

FYI, Type param defaults went out in 0.24: https://github.com/facebook/flow/blob/master/Changelog.md#v0240

Closing as this will be addressed in an upcoming release for React. If someone wants to contribute this for DOM events feel free to send a PR 👍

Closing as this will be addressed in an upcoming release for React. If someone wants to contribute this for DOM events feel free to send a PR 👍

Was this ever addressed, and how?

See the docs here: https://flow.org/en/docs/react/events/

To type event handlers you may use the SyntheticEvent<T> types

TL;DR for posterity....
handleChange = (e: SyntheticEvent<HTMLInputElement>) => {
  ...
  this.setState({ checked: e.currentTarget.checked }); // <----  currentTarget is the magic
};


Path merging in RNN-T beam search

Merge log-probability scores (at sequence prob level) when a sequence of IDs match.
Performance was slightly but consistently improved.

Codecov Report

Merging #225 (25fc68b) into master (99c40e0) will increase coverage by 0.07%.
The diff coverage is 82.85%.

@@            Coverage Diff             @@
##           master     #225      +/-   ##
==========================================
+ Coverage   64.50%   64.57%   +0.07%
==========================================
  Files          80       80
  Lines        9651     9654       +3
==========================================
+ Hits         6225     6234       +9
+ Misses       3426     3420       -6

Impacted Files
Coverage Δ

neural_sp/models/lm/gated_convlm.py
10.14% <0.00%> (+0.14%)
:arrow_up:

neural_sp/models/lm/rnnlm.py
91.08% <0.00%> (+1.14%)
:arrow_up:

neural_sp/models/lm/transformer_xl.py
90.44% <50.00%> (+1.00%)
:arrow_up:

neural_sp/models/lm/transformerlm.py
90.41% <50.00%> (+1.07%)
:arrow_up:

neural_sp/models/seq2seq/decoders/beam_search.py
59.57% <88.88%> (+6.94%)
:arrow_up:

...eural_sp/models/seq2seq/decoders/rnn_transducer.py
85.66% <100.00%> (-0.35%)
:arrow_down:

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 99c40e0...25fc68b. Read the comment docs.


ERROR ~ 'com.fasterxml.jackson.core.io.ContentReference com.fasterxml.jackson.dataformat.yaml.YAMLFactory._createContentReference(java.lang.Object)'

Description of the bug
Running 3.12.0 with Nextflow Tower triggers an error also observed with rnafusion workflow.
Command used and terminal output
nextflow run https://github.com/nf-core/rnaseq \
		 -name admiring_rubens \
		 -params-file https://tower.services.biocommons.org.au/api/ephemeral/WqSfsU4_Hk4HlOWt5X52Lg.json \
		 -with-tower https://tower.services.biocommons.org.au/api \
		 -r 3.12.0 \
		 -profile nci_gadi,singularity,test

Relevant files
nf-3usco1CoAgiMmR.log
System information

Nextflow version: Nextflow/23.04.3
Hardware: NCI Gadi HPC
Executor: PBSpro
Container engine: Singularity
OS: Rocky linux 8
nf-core/rnaseq version: 3.12.0

This is a problem with Nextflows Tower plugin and its dependencies and not with the nf-core rnaseq pipeline. Please contact Seqera's support instead.
(Maybe using the nextflow-all binaries could help.)

Thanks Matthias, will chase that up


req path shouldn't be encoded

request(app)
.get('/css/??a.css,b.css')

when request '/css/??a.css,b.css', the path is parsed '/css/?%3Fa.css%2Cz.css=' .
now , i have to pass encoded url like this:
request(app).get('/css/%3F%3Fa.css,b.css')

This is how URL encoding has to work, having two question marks like your example will result in a server treating the first one as the start of the query string, with the second one as the first character of the query string.
You will need to URL encode the question marks if you want them to actually appear in the URL.


Added pitest to the poms. Reports are generated as well.

Resolves #119.

Current coverage is 100% (diff: 100%)

Merging #120 into master will not change coverage

@@           master   #120   diff @@
====================================
  Files          82     82
  Lines        1075   1075
  Methods         0      0
  Messages        0      0
  Branches      188    188
====================================
  Hits         1075   1075
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update b527b34...61d161a

Yep. I think I'll make an issue first to handle them all in general. Any difficult problems that remain can then receive their own issue.


Rename yaml with the product configuration

Rename prod-devel-rcar-s4.yaml to prod-devel-rcar4.yaml as we are going to add support for other gen4 SOCs not only S4. And the current name may be missleading for users.

Ack is added.
No testing is required.
Ready to be merged.

Could you please resolve merge conflicts?

That conflict seems like an issue on the GitHub side, because on my local PC the patch rebased smoothly.
Anyway, I repushed PR, and now GitHub is happy.


Remove old: Kuro.MeryBeta version 3.2.5

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Why are you removing it? It is not 404 Not found?


Potentially dangerous alternative prefix 'minecraft' for various blocks

[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_barrel`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_infesting_leaves`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_infested_leaves`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_crucible`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_crucible_wood`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_sieve`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_waterwheel`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_axle_stone`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_grinder`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.
[09:48:21] [Client thread/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `block_auto_sifter`, expected `exnihilocreatio`. This could be a intended override, but in most cases indicates a broken mod.

This is a long standing legacy issue. Unfortunately fixing it without breaking every existing world's tile entities isn't straight forward.

Uhm RIP I think then.
Maybe in 1.13

It will definitely be fixed in 1.13 or 1.14, whichever ends up being the next version.


chore: Fix Installation complete event not being sent

The problem was that the Mono returned by analyticsService.sendEvent was returned inside a .map call, which, (almost) always results in a bug.
This PR fixes that.

@sharat87 let's merge this?


Update dependency and mapping parameters

Upgrade dependency:
https://github.com/TAMULib/mod-camunda/blob/main/pom.xml#L173
If necessary, update borrowed code that does MARC record instance mapping:
https://github.com/TAMULib/mod-camunda/blob/main/src/main/java/org/folio/rest/utility/MappingUtility.java
Confirm that it uses the same mapping as source record manager in Lotus

This is linked to a merged PR, does this mean that this work has been completed?


How to test from Debian GNU/Linux using g++?

I test any example but the result expected is bad. The library don't recognized.
For example:
Book.cpp:1:10: fatal error: Set: No existe el fichero o el directorio  #include <Set>           ^~~~~ compilation terminated.
Linux 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux

Hello @Villelmo
Here is the feedback shared by the author:
To test the code in other environments, such as Linux, the include directives must be changed to hold small letters only. For instance, #include  must be changed to #include .
Thank you!

The book was removed from the platform O'reilly.


the value obtained is sometimes not appropriate

Refer to this thread on discord
https://discord.com/channels/517647859495993347/1109062231477452820
when i am trying to get value from flagsmith sometimes i got null value sometimes i got correct value

Hi @zidni0192 , I am looking into this issue.
I am able to reproduce the behavior described, but only in the initial value of the variable feature using:
const feature = useFlags(['feature'])
No matter the actual value of the flag in the API, the initial value of the variable feature is always:
{
  enabled: false,
  value: null
}

However, after that initial value, I can see a stable behavior returning the right actual value of the flag.
Could you please confirm if this is also the behavior you can see?

In order to manage the behavior describes in the above comment, you can use useFlagsmithLoading() hook, which will return a LoadingState object as described here and then can use the LoadingState isFetching and/or isLoading to have a consistent feature flag value.
Please notice that there is an issue reported with a special case when using LoadingState and the feature-flag name is not found. Please refer to this issue #182 to follow up on that special case.


problem switching features with waveform view?

In KV, it was the case that ctrl+left click on a channel in the waveform view made that channel's PC1 become the x-axis feature in feature view, whereas ctrl+right made it become the y-axis feature. Now, I think ctrl+left is doing the same thing, but I'm not sure what ctrl+right is doing. The problem is that if you use the "t" feature to make the x-dimension time, there is no way to see PC1 of a desired channel on the y-dimension.
Relatedly, is there a way to choose PC2 or PC3?
And, it would be helpful at some point to have the kind of axis labeling that KV had (nothing more complicated than a channel number and feature number on each axis, would be fine.

I'll fix the ctrl+click issue in waveform view
I can add mouse/keyboard shortcuts to scroll through channels/features. I believe there are such shortcuts in KV -- do you use them? You want the same shortcuts?
Labels are planned #164 but not for the immediate future (maybe for 0.3 or 0.4). Text happens to be extremely difficult to do in OpenGL (it's an active research problem in computer graphics). VisPy implements some of it but I have to integrate it in phy.

I know that @kdharris101 is very keen on replicating the keyboard/mouse shortcuts from KV as much as possible!

good to know! I tend to prefer rethinking things from scratch over copying everything from KV, but I guess the keyboard shortcuts were good enough

I don't think I used the keyboard shortcuts for scrolling through PCs much. I think the way I'd get PC2 was by ctrl+clicking a second time, and the way I'd get PC3 was just clicking the button for it in the feature view (rare).
I don't have any objection to re-thinking! :)

OK this is fixed (in the upcoming PR), now ctrl+click and ctrl+rightclick do what you'd expect. :)

Hi Cyrille,
The reason I would suggest to keep things as they were is just user inertia. (The same reason F1 still means help on windows, 30 years on.)
If things have to change, we should change them (for example 1+click, 2+click). But for anything that can stay the same, why not?
From: Cyrille Rossant<EMAIL_ADDRESS>Sent: 17 June 2015 09:02
To: kwikteam/phy
Cc: Harris, Kenneth
Subject: Re: [phy] problem switching features with waveform view? (#348)
good to know! I tend to prefer rethinking things from scratch over copying everything from KV, but I guess the keyboard shortcuts were good enough
—
Reply to this email directly or view it on GitHubhttps://github.com/kwikteam/phy/issues/348#issuecomment-112706240.

@kdharris101 I agree that keyboard shortcuts are very hard to unlearn and change. But in the case of KV I think they were all good.
Also in the very latest version, 1+click etc have disappeared, because there is a new feature view showing a single plot (like in KV), in addition to the grid view. So I was able to bring back the old KV shortcuts (ctrl+click) instead, which work in that new feature view exclusively.

I wouldn't be opposed to keeping 1+click etc for the feature grid. It
doesn't conflict with ctrl+click for singlefeatureview, does it?
On Wed, Jun 17, 2015 at 11:05 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

@kdharris101 https://github.com/kdharris101 I agree that keyboard
shortcuts are very hard to unlearn and change. But in the case of KV I
think they were all good.
Also in the very latest version, 1+click etc have disappeared, because
there is a new feature view showing a single plot (like in KV), in addition
to the grid view. So I was able to bring back the old KV shortcuts
(ctrl+click) instead, which work in that new feature view exclusively.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/348#issuecomment-112963862.

I don't mind putting it back, but will you ready need it if I implement your proposition for the dimensions in the grid view? in what situations would you want to update manually dimensions in the grid view and not in the simple feature view?

Agreed, I like this feature!
From: nsteinme<EMAIL_ADDRESS>Sent: 18 June 2015 09:46
To: kwikteam/phy
Cc: Harris, Kenneth
Subject: Re: [phy] problem switching features with waveform view? (#348)
I wouldn't be opposed to keeping 1+click etc for the feature grid. It
doesn't conflict with ctrl+click for singlefeatureview, does it?
On Wed, Jun 17, 2015 at 11:05 PM, Cyrille Rossant <notifications<EMAIL_ADDRESS>wrote:

@kdharris101 https://github.com/kdharris101 I agree that keyboard
shortcuts are very hard to unlearn and change. But in the case of KV I
think they were all good.
Also in the very latest version, 1+click etc have disappeared, because
there is a new feature view showing a single plot (like in KV), in addition
to the grid view. So I was able to bring back the old KV shortcuts
(ctrl+click) instead, which work in that new feature view exclusively.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/348#issuecomment-112963862.

—
Reply to this email directly or view it on GitHubhttps://github.com/kwikteam/phy/issues/348#issuecomment-113078958.


VAT Number

HM Government issues VAT numbers, so a form that says "not recognised" is as much use as a chocolate fireguard, sort it MS!

Your marketplace form
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4c0ce426-a720-24d2-35e6-6c63f68e47a8
Version Independent ID: e993bc40-5837-3b76-ea5a-fe07002d3c2c
Content: Create a new SaaS offer for the Microsoft commercial marketplace
Content Source: articles/marketplace/partner-center-portal/create-new-saas-offer.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @dsindona
Microsoft Alias: dsindona

@SwiftDavid Thanks for your comment! We will review and provide an update as appropriate.

@SwiftDavid Could you please describe your issue in detail?

I cannot offer more than I put before. Your form asks me to provide my VAT
number. I am a registered UK company and therefore provide this as HM
Inland Revenue from the UK Government provided it to me, which is 196 0876
64.
But regardless whether I take all the spaces out or not, the
registration page says number format not recognised, or some such.
On Fri, Jun 19, 2020 at 8:01 AM SadiqhAhmed-MSFT<EMAIL_ADDRESS>wrote:

@SwiftDavid https://github.com/SwiftDavid Could you please describe
your issue in detail?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/57356#issuecomment-646473439,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTO7OULJDMNKNZ7DVSYRP3RXMEONANCNFSM4OBRVFPQ
.

@SwiftDavid Can you please share the screenshot of the page that you are referring to?

@dsindona Any thoughts on the query in the previous post?

I'll look into this.

@SwiftDavid where exactly are you encountering this problem /entering the VAT number? Is is related to the article in this issue (creating a SaaS offer) or when you are configuring your Partner Center account. Can you please grab a screenshot of the problem? It would be helpful. Thanks

It is in my Partner Centre Account
On Mon, Jun 22, 2020 at 6:28 PM Dana Sindona<EMAIL_ADDRESS>wrote:

@SwiftDavid https://github.com/SwiftDavid where exactly are you
encountering this problem /entering the VAT number? Is is related to the
article in this issue (creating a SaaS offer) or when you are configuring
your Partner Center account. Can you please grab a screenshot of the
problem? It would be helpful. Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/57356#issuecomment-647669732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTO7OXW7FDQBZA24Y5UJCTRX6ICNANCNFSM4OBRVFPQ
.

@SwiftDavid Hi, it's not enough to know that this happened in your Partner Center account.  Could you please describe your exact task scenario when this issue occurred?  Was it during the account registration? Or were you trying to accomplish some other specific tasks?  Repro steps would be really helpful for us to pinpoint the problem.  Thanks!

I was trying to register, got as far down the page as "enter VAT Number",
and regardless of whatever format I entered it as, it said it was not
recognised.
On Thu, Jun 25, 2020 at 11:03 PM Qian Wen<EMAIL_ADDRESS>wrote:

@SwiftDavid https://github.com/SwiftDavid Hi, it's not enough to know
that this happened in your Partner Center account. Could you please
describe your exact task scenario when this issue occurred? Was it during
the account registration? Or were you trying to accomplish some other
specific tasks? Repro steps would be really helpful for us to pinpoint the
problem. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/57356#issuecomment-649840448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTO7OVRCFSHAZ4OYBAVE7DRYPCTVANCNFSM4OBRVFPQ
.

@SwiftDavid Two questions for you:

Register for which program?
What was the country that was selected? In most cases, VAT ID is optional.

How many programs need your VAT number entering? I note you didn't look up
SwiftERM for Q2 otherwise you would have known it was the UK.
On Fri, Jun 26, 2020 at 5:05 AM Qian Wen<EMAIL_ADDRESS>wrote:

@SwiftDavid https://github.com/SwiftDavid Two questions for you:

Register for which program?
What was the country that was selected? In most cases, VAT ID is
optional.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/57356#issuecomment-649947791,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTO7OVOBAYQBUJ7JAYL4MDRYQM75ANCNFSM4OBRVFPQ
.

Hello @SwiftDavid
I've reviewed this thread. I appreciate your feedback, that will help us improve the commercial marketplace.
If I understand correctly, one of the registration forms in Partner Center did not accept your VAT number. To address this issue, first we need to understand where exactly it occurred - there are many forms in Partner Center. The easiest way to pinpoint the issue would be to see a screenshot of the page where you received the error message. Could you please provide some screenshots?
Otherwise, could you please describe in details the steps that took you to that page?
To receive additional help, please consider asking our Support team at http://aka.ms/marketplacepublishersupport

@SwiftDavid - Following up on this thread to see if you have any updates. If you are still experiencing this issue, we recommend contacting our Support team at http://aka.ms/marketplacepublishersupport for assistance. Thanks!
#please-close


Nested pmap issue on GPU

Running the code with nested pmap/vmap in the reproducer below works with CPU/TPU but fails on GPU. The explicitly specified cpu backend when running pmap seems to be ignored, as there are clearly enough devices available.
Changing
updates_at_idxs = updates[..., None] * rlax.one_hot(indices, num_classes)
to
updates_at_idxs = updates[..., None]
makes things work on GPU as well. Not entirely sure how this is related to the mapped axes though.

Colab reproducer

I've further isolated the error. This fails on GPU:
import chex
import jax
from jax import numpy as jnp

chex.set_n_cpu_devices(4)

print('CPUs:', jax.device_count('cpu'))
print('GPUs:', jax.device_count('gpu'))

def fn(indices):
  return jnp.equal(indices, jnp.arange(3)).astype(jnp.float32)

mapped_fn = jax.pmap(fn, axis_name='i', backend='cpu')
mapped_fn = jax.pmap(mapped_fn, axis_name='j', backend='cpu')

indices = np.array([[[2], [1]], [[0], [0]]])

mapped_fn(indices)

Thanks for the great reproducer! Thanks to that, this just took 2 mins to spot once I ran your repro.