Current Selections not working in Sense November 2018

If I use Sense September 2017 the current Selections show when I make a selection. On Sense Nov 2018 Patch 2 the selections are applied but the current selection component does not rerender. When I change routes the component renders correctly. What do I need to change?

please update to the latest version. All issues on selections and multiple objects should be resolved.
Closing the issue. Please reopen if the problem persists.


Teacher accounts

(edit) Ready

We should restrict user role updates on the server.
We shouldn't create a 2nd trial request for a user.
Creating a teaching account does not login the user afterwards.


_ControllerStream' is not a subtype of type '() => void

════════ Exception caught by widgets library ═══════════════════════════════════════════════════════
The following assertion was thrown building Inicio(dirty, state: _InicioState#1cb5f):
type '_ControllerStream' is not a subtype of type '() => void'
Either the assertion indicates an error in the framework itself, or we should provide substantially more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md
The relevant error-causing widget was:
Inicio file:///C:/desenv/flut/web_services/lib/main.dart:5:9
When the exception was thrown, this was the stack:
#0      _InicioState.build (package:webservices/home.dart:32:37)
#1      StatefulElement.build (package:flutter/src/widgets/framework.dart:4334:27)
#2      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4223:15)
#3      Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
#4      BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2432:33)
...

#0 _InicioState.build (package:webservices/home.dart:32:37)

This is a bug in your code. Please do not open self help issues on the issue tracker


feat: using dbt_ethereum_source as the source of this project.

@onesuper please help me check where else need I to replace it with ref table.

Awesome!

@TalkWIthKeyboard I am going to move the transformation logic of tokens to stg_ethereum_tokens in dbt_ethereum_source.


NuGet issue

Cannot compile "Error occurred while restoring NuGet packages: The operation failed as details for project Confuser.Optimizations.Exports could not be loaded."

I can't reproduktive the issue. There is nothing special about the way NuGet is used and the buildserver is also able to restore everything without any problems.


How to use Inline locally in a component

I do not understand how to use Inline inside a component (not globally).
I am trying something like the following, but it does not work:
<template>

    <inline name="schema"></inline>

</template>

const data = { schema }
// Create a component from given data
const Inline = makeComponent(data)

Thanx for your reply!
But still I cannot get my svg image as a component: everything seems to work, but instead of the image as an output I can only see (in the generated DOM) the url of the .svg imported file.
"schema", inside "data object", seems to contain only the resource url as a string:
data = {schema: "/assets/img/schema.svg"}
<template>

    <inline name="schema"></inline>

</template>

I will investigate further.

Basically the data will be displayed as html:
https://github.com/egoist/vue-inline/blob/dfc9cfb5b01ef044d8eb547d70f550a242c798f8/src/index.js#L15
So you have to import SVG as string with something  like raw-loader

Yes, thank you!


cmd/compile: no stmt flag set for two lines of code that do generate instructions

$ go version
go version go1.17 linux/amd64

it also reproduces on 1.17 windows/amd64 and 1.16.
Reproduction steps:

Compile the tests of package github.com/dolthub/dolt/go/libraries/doltcore/sqle with -gcflags='all=-N -l' (commit d2c3c987593fe82e0571ffd3fda09afd340b4634 will do this)
See the pcln table generated for github.com/dolthub/dolt/go/libraries/doltcore/sqle.NewTestEngine
Lines 120 and 121 have instructions generated but none of them have the stmt flag set

Originally reported as https://github.com/go-delve/delve/issues/2664
cc @dr2chase

It happens in expand calls, not sure of the exact failure yet, other than the statement was hanging off an OpDereference.
To see for yourself:
git clone https://github.com/dolthub/dolt
cd dolt/go/libraries/doltcore/sqle
GOSSADIR=`pwd` GOSSAFUNC=NewTestEngine go test -c -gcflags=all='-N -l' .


question - Torch, not flash

Hi,
I managed to make it torch rather then flash on android,
Anyone knows how to make it work on ios ?
Thanks

Same question.

@arturikoX Hi,
Wonder how you managed to make it torch rather then flash on android. Can you give me a hint on that please?

@nampil
I can build the plugin, I have it working and put it on npm

Or you can put it locally in the plugins folder. I'll send you the code you need to be replaced.

@nampil
you need to replace the toggleFlash method in index.android.ts with:
public toggleFlash(mode?: string) {
    if (this._camera) {
        if (this._camera.getFlashMode() === fancycamera.CameraFlashMode.OFF) {
	    if (mode === 'torch') {
	        this._camera.setFlashMode(fancycamera.CameraFlashMode.TORCH);
	    } else {
	        this._camera.setFlashMode(fancycamera.CameraFlashMode.ON);
	    }
	} else {
	    this._camera.setFlashMode(fancycamera.CameraFlashMode.OFF);
	}
    }
}

and when calling the method toggleFlash pass 'torch' prop

@nampil
you need to replace the toggleFlash method in index.android.ts with:
public toggleFlash(mode?: string) {
    if (this._camera) {
        if (this._camera.getFlashMode() === fancycamera.CameraFlashMode.OFF) {
	    if (mode === 'torch') {
	        this._camera.setFlashMode(fancycamera.CameraFlashMode.TORCH);
	    } else {
	        this._camera.setFlashMode(fancycamera.CameraFlashMode.ON);
	    }
	} else {
	    this._camera.setFlashMode(fancycamera.CameraFlashMode.OFF);
	}
    }
}

and when calling the method toggleFlash pass 'torch' prop

Thanks @Bezlepkin


OLS-1032: Bump-up langchain to 0.2.16

Description
Bump-up langchain to 0.2.16
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[x] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)

Related Tickets & Documents

Related Issue #OLS-1032

/retest

/retest

/retest

/lgtm

/retest

/approve

/override "Red Hat Konflux / lightspeed-service-on-pull-request"
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.11%. Comparing base (3bc1fb5) to head (8434a86).
Report is 38 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1584      +/-   ##
==========================================
- Coverage   94.83%   94.11%   -0.73%
==========================================
  Files          60       60
  Lines        2671     2718      +47
==========================================
+ Hits         2533     2558      +25
- Misses        138      160      +22

see 2 files with indirect coverage changes


Compiler not working

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
run:
npx clear-npx-cache
npx @massalabs/sc-project-initializer@dev init testDir
cd testDir
npm run build

output:
><EMAIL_ADDRESS>build
> npx massa-as-compile

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/massa-as-compile - Not found
npm ERR! 404
npm ERR! 404  'massa-as-compile@*' is not in this registry.
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR!      /Users/aurelienfoucault/.npm/_logs/2023-01-06T14_00_05_309Z-debug-0.log

Expected behavior
A clear and concise description of what you expected to happen.
This should create build folder and put wasm files into.
Versions
The versions of software and packages the bug in present in (massa-as-sdk, toolkit, Thyra, web browser...)
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Additional context
Add any other context about the problem here.
Solution
We decided to extract the package massa-sc-compiler into a new repository: https://github.com/massalabs/massa-sc-compiler

This is a temporary fix to the issue when we created a monorepo. The package relationship with the Toolkit's sc-initializer should be taken into consideration in later stages and most likely reorganized.


Error bundle install CoRM

--- ERROR REPORT TEMPLATE -------------------------------------------------------

What did you do?
I ran the command /usr/local/bin/bundle install

What did you expect to happen?
I expected Bundler to...

What happened instead?
Instead, what actually happened was...

Error details
Errno::EACCES: Permission denied @ rb_sysopen - /home/nhybrow/.bundle/cache/compact_index/rubygems.org.443.29b0360b937aa4d161703e6160654e47/versions
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:44:in `initialize'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:44:in `open'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:44:in `open'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client/updater.rb:44:in `update'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:64:in `update'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/compact_index_client/lib/compact_index_client.rb:55:in `update_and_parse_checksums!'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/fetcher/compact_index.rb:65:in `available?'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/fetcher/compact_index.rb:15:in `call'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/fetcher/compact_index.rb:15:in `block in compact_index_request'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/fetcher.rb:154:in `use_api'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:331:in `block in api_fetchers'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:331:in `select'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:331:in `api_fetchers'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:336:in `block in remote_specs'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/index.rb:10:in `build'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:335:in `remote_specs'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/source/rubygems.rb:82:in `specs'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/lazy_specification.rb:56:in `__materialize__'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/spec_set.rb:91:in `block in materialize'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/spec_set.rb:88:in `map!'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/spec_set.rb:88:in `materialize'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/definition.rb:140:in `specs'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/definition.rb:129:in `resolve_remotely!'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/installer.rb:195:in `resolve_if_need'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/installer.rb:70:in `run'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/installer.rb:22:in `install'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/cli/install.rb:102:in `run'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/cli.rb:175:in `install'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/cli.rb:11:in `start'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/exe/bundle:27:in `block in <top (required)>'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/lib/bundler/friendly_errors.rb:98:in `with_friendly_errors'
  /var/lib/gems/2.3.0/gems/bundler-1.12.3/exe/bundle:19:in `<top (required)>'
  /usr/local/bin/bundle:23:in `load'
  /usr/local/bin/bundle:23:in `<main>'

Environment
Bundler   1.12.3
Rubygems  2.5.1
Ruby      2.3.0p0 (2015-12-25 revision 0) [x86_64-linux-gnu]
GEM_HOME  /var/lib/gems/2.3.0
GEM_PATH  /var/lib/gems/2.3.0:/home/nhybrow/.gem/ruby/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
Git       2.7.4
  Bundler settings

orig_path
Set via BUNDLE_ORIG_PATH: "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
--- TEMPLATE END ----------------------------------------------------------------

The issue seems to be same as #4534


Missing required prop: "itemKey"

Hello, thanks for this wonderful extension, it looks very good, I have been trying the demo and I get this warning:
runtime-core.esm-bundler.js?9e79:38 [Vue warn]: Missing required prop: "itemKey"
at <Draggable list= (2) [{…}, {…}] ghost-class="ghost" onInput=fn  ... >
at <QDraggableTreeNode value= {id: 2, label: 'Good food', children: Array(2)}children: (2) [{…}, {…}]0: {id: 3, label: 'Quality ingredients', children: Array(0)}children: []id: 3label: "Quality ingredients"[[Prototype]]: Object1: {id: 4, label: 'Good recipe', children: Array(0)}children: []id: 4label: "Good recipe"[[Prototype]]: Objectlength: 2[[Prototype]]: Array(0)id: 2label: "Good food"[[Prototype]]: Object onInput=fn group="testsailordgod"  ... >
at <Draggable list= (3) [{…}, {…}, {…}] item-key="name" group="testsailordgod"  ... >
at <QDraggableTreeNode value= {id: 1, label: 'Satisfied customers', children: Array(3)} group="testsailordgod" onInput=fn  ... >
at <QDraggableTree modelValue= [{…}] onUpdate:modelValue=fn data= [{…}]  ... >
at
at <QCardSection class="no-shadow" style= {padding: 0} >
at
at
at
at <BasicExample onVnodeUnmounted=fn ref=Ref< Proxy {…} > >
at
at
at
at <MainLayout onVnodeUnmounted=fn ref=Ref< Proxy {…} > >
at
at
Could you tell me how to solve it?

Which version of Vue are you using?

I am using Vue 3, vue/cli 4.5.13,
I downloaded the demo that is in your Github repository and typed yarn to install the dependencies and then quasar dev.
The demo works fine and does the drag and drop but in the console I get that message, with which version of Vue should it work well?

@francosabin  You are using vuedraggable anywhere in your project?

I'm sorry, it seems that the code is not complete when I paste it, but you can check it in the following link:
https://github.com/SortableJS/vue.draggable.next

Hey,
Please uninstall the current package and re-install it and then try. Let me know if it works or not. I am unable to reproduce the issue on my system. But I have applied a few fixes based on the assumption.
Thanks,

Hello, yes, it works very well, thank you very much and success in your life and family, greetings.


Remove relationships from deleted object

Sometimes deleted object can have too many relationships attached, so maybe it would be better to save only attributes from the deleted model. Hopefully, it is not expected behavior because of some future plans with this package. If it is, sorry for bothering you. 😊

Thank you!


Embedded fix

This seems to work in my fork, but actions have been quite unreliable today so havent done proper testing. Guess we could just revert it if it doesn't help


Remove instanceof checks for Bacon objects

As mentioned many times over Bacon uses instanceof, which does not play well with multiple JS execution contexts.
In our specific case we are testing our Bacon streams using Jest which has its own module loader. This change would allow us to go back to upstream Bacon.
Someone made the point that because Bacon also has some shared global state, preventing complete "purity", we should not fix this. I disagree. With this out the way many simple problems (like our case) will be solved. This problem should be tackled in an iterative way, unless you want to leave it unsolved forever.

cc @gfarrell, sorry for the long wait :squirrel:

@johannhof great to see, thanks for sorting this.

@johannhof / @gfarrell, could you by any chance share an example Jest test case where the current version of Bacon.js doesn't work? I'd definitely be interested in seeing how Bacon (doesn't) work there. My very naïve approach didn't seem to have issues, but I'm likely doing something wrong.

@lautis well we fixed that some time ago by using our own branch but I'll try to dig something up :blush:

For me this seems ok, if this helps people. Is using _isSomething a good/common practise?
I thinks there's still some object equality stuff going on, like comparing to Bacon.noMore which will of course be a different object if there are multiple Bacon instances.

Is using _isSomething a good/common practise?

There is a precedent with moment.isMoment. Instanceof is a bit faster (in theory) than property access, so that might be why it's the preferred method in moment.

@lautis @raimohanska the only other culprits of direct comparison apart from None I could find are Bacon.noMore and Bacon.more, which are defined in reply.coffee as
Bacon.noMore = ["<no-more>"]
Bacon.more = ["<more>"]

Making them strings instead of arrays containing strings would solve the cross-context problem pretty easily. What was the reason of having them as arrays in the first place?
Converting them to
Bacon.noMore = "<no-more>"
Bacon.more = "<more>"

doesn't seem to break the tests.

In any case I amended my commit and leave the rest to you :heart:

Making them strings instead of arrays containing strings would solve the cross-context problem pretty easily. What was the reason of having them as arrays in the first place?

They were originally strings. The implicit return in CoffeeScript means that in some edge cases user input could be interpreted as Bacon.noMore.

They were originally strings. The implicit return in CoffeeScript means that in some edge cases user input could be interpreted as Bacon.noMore.

Wow, was that really a problem? :hushed:

The string was "veggies" (or something like that). Not a big problem, we could have the same pattern for Bacon.(no)More as we have for None.
@johannnhof, did you have time to extract an example from the test suite? The case is a bit different from the usual issue with iframes where it wouldn't be too bad to do explicit transformation of streams.

@lautis One example that hit us early on is mocking streams in your Jest tests (the most common use case for Jest).
We use mocking extensively. We love that (Bacon) streams are so modular that we can just mock all other streams and test each one individually. But mocking streams doesn't work with upstream Bacon.
https://gist.github.com/johannhof/b47fe3ef7d07caf730fe
There are more cases that all have to do with requireing streams from different contexts, but I think this is our major problem.

@johannhof Jest seems to work with the current master version and Jest, but only if you consistently do your requires either within spec/beforeEach or on file-level. This is at least for a similar case as you showed.
If you mix requires (e.g. require Bacon at the top of the file), the suite will explode. Especially Bacon.combineTemplate seems to cause rather very nasty errors. This PR fixes that, but multiple Bacon contexts could cause issues if you're relying on glitch-free updates.
I've made an example project for Bacon/Jest with mocking: https://github.com/lautis/bacon-jest-test

Merged! Still the more/noMore thing to fix.

A simple solution would be to revert to the "good old" way of using strings as noMore/more, so that === equality could be used. Alternatively it would be like if (reply && reply._isNoMore). What do you think?

Well this commit already changed more and noMore to be strings :smile:
I amended the commit, sorry if that wasn't clear, I made a comment above. That said, I think that a magic string is probably the best thing to do and what we have right now sounds pretty good already (we could make it even longer but I think it's fine).
@lautis interesting, thanks for the example, this could indeed work for our use case! But I'd say the PR is still pretty valid because of all the issues in the past. I know it doesn't look too pretty code-wise, but relying on instanceof for core functionality and not just convenience is bound to cause issues like the ones we've already seen.

I'll get me coat...


Constantly requires choosing folder

Thanks, easy to use. One request - Is there a way to have the GUI retain the previous chosen folder when "Open File" - Constantly have to re-choose the same folder every time - maybe RootFolder = Selected Folder and the value will be retained until the GUI is closed.

Yes, I'll try to take a look at this tomorrow and potentially get this done


The Parcel example template should import from ../src and not the build directory

The Parcel example template imports from the package root:
import { Thing } from '../.';

This means that tsdx watch needs to be running in addition to Parcel to do iterative development, which is unnecessary, since importing from ../src works as well and allows getting updates as soon as changes are made.

I didn't write the templates, but that is intentional, the docs even say so.
It's an example, so it uses the same code as a user would. Parcel's build process isn't the same as TSDX's.

It would be useful to have a comment in the template noting this, since it can still be desirable to import from the sources.

Could also use Parcel aliases for ./. Would have to insert the name into both the package.json configuration and the import for that, which is a bit involved.


Ocelot configuration been re-write after IIS pool idle timeout

Hello everyone
Im facing really strange behaviour from Ocelot while im using the great feature for merging multiple configuration files

After Ocelot is been deployed and started(on IIS) for first time is creating automatically ocelot.Production.json file which has exactly the same configurations like ocelot.json file(this file is again created on first start of the application and its contains the merge result of my sub-configurations files) - is there a way Ocelot not to create ocelot.Production.json. Just as remark the Gateway is running on this moment without any problems no matter of the fact that both files (ocelot.Production.json and ocelot.json are exactly the same)
After the IIS pool idle timeout and durring the next request for some reason Ocelot is re-building the ocelot.Production.json and ocelot.json BUT this time it start to return and error that there are duplicated Routes - extremely strange because the files again contains the same configurations
If we are using Administration API to change the configurations on run time and then leave the IIS pool idle timeout on the next request ocelot is will merge again all sub-configurations files which is resulting that changes made from Administration API are deleted

Does any one face this as a problems and if its possbile to provide some guidelines

Hi Nikolay!
Are you still with Ocelot?
You were facing with IIS Gotchas, probably on 99%
Please use self-hosted Kestrel and Docker deployment instead of IIS.
For development environment it is better to host Ocelot app in console.
Good luck!


[Fix-8073] Remedy this issue with the result of the task groups being disordered.

Purpose of the pull request
This PR will close #8073 .

Brief change log
Verify this pull request

This change added tests and can be verified as follows:

Manually verified the change by testing locally.

Codecov Report

Merging #8274 (3c0fd9f) into dev (6be2201) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #8274      +/-   ##
============================================
- Coverage     45.15%   45.15%   -0.01%
  Complexity     3980     3980
============================================
  Files           678      678
  Lines         26343    26343
  Branches       2836     2836
============================================
- Hits          11895    11894       -1
+ Misses        13331    13328       -3
- Partials       1117     1121       +4

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-1.41%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
40.00% <0.00%> (+2.22%)
:arrow_up:

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 6be2201...3c0fd9f. Read the comment docs.


check the app is stationary or moving

Hi,
i want to check the status of the app i.e whether the app is in moving or stationary.
for that i wrote like this
 BackgroundGeolocation.on('stationary', (stationaryLocation) => {       console.log("stationaryLocation:"+JSON.stringify(stationaryLocation))     });
but it is not showing any response , any on please give me suggestions that how to resolve it.

Please respond for it

+1 Same problem here

What is your configuration? Please fill issue template next time.


showcamera program issue

When running the ./showcamera command the program runs and recognizes the camera I have attached (DMK 22AUC03-F) and all the properties can be accessed. However, the screen is black and does not register any images coming through the camera.  There is also the issues of "Error: Could not negotiate format," as well as the error "Error: Device 'dev/video0' is busy."
Has this happened to anyone before and is there a way to fix this?

This is what I am seeing when I run the ./showcamera command

This is what I see when I run the ./showcamera command

Hi again
Try lower frame rates
Try the pipeline
gst-launch-0.10 v4l2src ! video/x-raw-gray ! tisvideobufferfilter ! tis_auto_exposure ! tis_autofocus, auto=1 ! ffmpegcolorspace ! ximagesink
The showcamera sample is quite too complex to narrow down issues.
Now I know, you use an Ubuntu.  So you do not need to answer in issue #99. Which computer model do you use?
However, why do you still use GStreamer 0.10?

Hi again,
I use a MacBook Pro, and I didn't realize I was supposed to use a different GStreamer until now, I will change that.  I am new to setting up this camera.

MacBook pro with Ubuntu Linux?
  The pipeline does not fully work, I have gotten the camera to see gray pixilations when I move it around but no clear image.

Never mind, I am back to the camera having the segmentation core dumped error.  I'm not sure what caused it to fail w like this again

If you use "Parallels", you may have some problems with USB forwarding. I had this often on Mac OXs. It seems, you can not receive all image datablocks from the camera. So lets reduce the frame rate:
gst-launch-0.10 v4l2src ! video/x-raw-gray,width=640,height=480,framerate=15/1 ! tisvideobufferfilter ! tis_auto_exposure ! tis_autofocus, auto=1 ! ffmpegcolorspace ! ximagesink

OK, I used this pipeline but got this error

Seems the device video0 does not exist. So you may disconnect and reconnect the camera.
With
ls /dev/vid*
you will see, whether the camera is "video0" again.

Ok, I've gotten the camera back again after disconnecting it.  It is video0 again and this is what I am seeing.  I can click the start button and it says 'ready' and then I can also click the snap image button and nothing happens.

It is still fragile though, occasionally the segmentation error core dumped comes back.

Well, I wanted you to use the last pipeline I had written for you. The showcamera program is far to complex for checking, whether we can get a live video in your environment.

When I used the pipeline you gave me previously, it did not work as well as the ones I have been using.

OK. How to proceed now?
Other question: Can you use GStreamer 1.0 instead of 0.10? 0.10 is somewhat outdated.
Last point: What exactly do you want to do with the camera and the images? I ask this, because I may can provide a better sample code for you.
Stefan

Closing this issue since we need feedback on Stefans last questions. Please re-open when neccessary.


object of type TrainingInput is not JSON serializable

workflow = InferencePipeline(
    preprocessor=...,
    estimator=...,
    inputs={
        "train":TrainingInput(s3_data="..."),
        "test":TrainingInput(s3_data="...")
    },
    ...
)

When you call execute() it will fail, saying object of type TrainingInput is not JSON serializable

I also received this error


Fix fatal invalid reference for repos have no tags

If a repo (such as is.vim) has no tags , when invoke :PlugUpdate, it will occur fatal invalid reference.
The patch will skip tags check for this case.

Your fix works but the tests fail. Can you update the tests to reflect the new behavior and perhaps use that repo for a new test case?

@janlazo  I am not very familiar with vim script, would you like to help this ?

I don't understand how this helps. Please post the output of :echo g:plugs.

:echo g:plugs output https://gist.github.com/douglarek/f9355d0e6b2f784c99570dc3f6c8c40a

I see 'tag': '' all over which is clearly misconfiguration. You instruct vim-plug to use an empty tag, and vim-plug naturally fails with a proper error message because there is no empty tag. So why do you do it?

Just do not know why empty tag added to g:plugs, I am using space-vim.

Well, then it's a bug of space-vim misusing vim-plug. Please report the problem to space-vim. Thanks.


v8.0.0 - All images and files in filemanager is not visible for administrators (admin is OK)

I went through all the upgrade process from <IP_ADDRESS> to <IP_ADDRESS> and then to 8.0.0
The upgrade from <IP_ADDRESS> to <IP_ADDRESS> went OK
The upgrade from <IP_ADDRESS> to 8.0.0 was a little tricky. I did the manual upgrade where I copy the concrete folder to the server and run the /ccm/system/upgrade command. Here it came up and said that the site was already upgraded to version 8.0.0. It seem that it went through the upgrade without asking to do it.
After the upgrade I have discovered that all files in the file manager is only visible/available for admin (superadmin account). When logged in as a normal administrator, all files in the file manager has gone. But if I uploade new files, only the new files is visible for normal administrators.

Yeah, I can reproduce this as well. The root file manager folder has a certain permission set, which should be reflected in the permissions you see when you go to the File Manager Permissions dashboard page. Those look set right to me – but when i look at the permissions at the file level they don't have any permissions set on them, even though they are inheriting from their file manager node. I'll dig further.

This is severe, I'll expect this to make some confusion! Someone might at first be scared and do something stupid! This should be fixed as fast as possible!

Fixed in the release/8.0.1 branch.


Error trying to delete a source study

I sometimes experience an error when deleting a source study. I am * usually *, able to replicate the error if I follow these steps:

run local.
add new source study.
build local.
try to delete newly added source study.

I'm not certain this is the reason for the error, but perhaps logging out / logging in or something to that effect???
[sourceStudyId]-534da68b99105b55.js:28 Uncaught (in promise) Error: error: update or delete on table "source_studies" violates foreign key constraint "fk_source_datasets_source_study_id" on table "source_datasets"

Can't check right now but my guess as to what might be happening is that the source study has CELLxGENE datasets that get automatically added when the server starts, and then the study can't be deleted alone because that would leave the datasets with references to a source study that doesn't exist; presumably we'll need to update the source study API to delete the associated source datasets as well

Okay testing it a bit I think the above holds up -- I did think briefly that there was some inconsistent behavior in whether a source study with source datasets could be deleted, but I'm thinking now that the ones that didn't error were shared by multiple atlases and so weren't actually deleted (which does check out in the quick follow-up test I did)

Complete


[DOC]: ImportError: cannot import name 'LLM' from 'superduperdb.ext.transformers'

What's wrong?
Hi
Trying to follow this https://docs.superduperdb.com/docs/reusable_snippets/build_llm
with installation everything ok

pip install transformers datasets bitsandbytes accelerate
from superduperdb.ext.transformers import LLM

llm = LLM.from_pretrained("mistralai/Mistral-7B-Instruct-v0.2", load_in_8bit=True, device_map="cuda", identifier="llm", predict_kwargs=dict(max_new_tokens=128))

but receiving this
Python 3.11.6 (main, Oct  2 2023, 13:45:54) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from superduperdb.ext.transformers import LLM
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'LLM' from 'superduperdb.ext.transformers' (/venv/lib/python3.11/site-packages/superduperdb/ext/transformers/__init__.py)

there is also error here: https://docs.superduperdb.com/docs/ai_integrations/transformers/

from superduperdb.ext.transformers import LLM
llm = LLM(model_name_or_path="facebook/opt-350m")
llm.predict_one("What are we having for dinner?")

>> from superduperdb.ext.transformers import LLM
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'LLM' from 'superduperdb.ext.transformers'

How could it be better?
Don't know yet

Hi @YuriyGavrilov - can you try from superduperdb.ext.transformers.model import LLM?
We need to add this to the __init__.py of the subpackage.

@YuriyGavrilov Hi, which version of SuperDuperDB are you using?

@jieguangzhou thx, may be this is a reason. I am using same as default pip install set up, actually don't know but will check it today. Thanx for helping 🙏

@jieguangzhou thx, may be this is a reason. I am using same as default pip install set up, actually don't know but will check it today. Thanx for helping 🙏

Good! If there are any issues, please feel free to ping me and let me know.

used Version: 0.1.1 as pip install suggest.

Hi @YuriyGavrilov
As @jieguangzhou pointed out, the v0.2 will be released soon (hopefully in a couple of days).
After the release, you will be able to install v0.2 using pip install superduperdb.
Until then, you can test v0.2 directly from the repo.
git clone git@github.com:SuperDuperDB/superduperdb.git
cd superduperdb
pip install ./

@fnikolai thanks, will try to install
some interesting finding
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
superduperdb 0.1.1 requires sqlalchemy>=2.0.28, but you have sqlalchemy 2.0.0 which is incompatible.
snowflake-sqlalchemy 1.5.3 requires sqlalchemy<2.0.0,>=1.4.19, but you have sqlalchemy 2.0.0 which is incompatible.

will try to run without snowflake

Right.
The first problem is probably a side-effect from your previous superduperdb installation.
try to do pip uninstall superduperdb and then repeat the steps.
The second problem is related to github requiring ssh to be configured from your side.
You can try using https instead. git clone https://github.com/SuperDuperDB/superduperdb.git

Solved in main.


drop use python<=3.7 syntax

Despite what is mentioned in pyproject.toml that sh supports only python 3.8.x sh code still uses older syntax.
Pass all code over pyupgrade --py38.

Thanks for the contribution!
black tripped over a single line because it wants double quotes: _unicode_methods = set(dir(''))
If you push that change, then I'll merge.

Thank you 😄


Make Form preset entity validation async

Reproduction steps:

Add a ValidateDelegate performing an asynchronous task to a Form Field Step (an http call in my case)
Pre-fill the Step with a value

The form dialog will fail to start.

Thanks!  This was causing a deadlock so it is a good fix.


Fix Prometheus pod scraping regexp

The old regexp does not work. It is already fixed in the prometheus K8s config file: https://github.com/kubernetes/charts/blob/master/stable/prometheus/values.yaml#L914

/ok-to-test

/assign

Thanks for your effort. Closing this in favor of #3961.


Add target(s) for viewing API docs and help files locally

Basically, copying existing tasks and change the --define:RELEASE flag to be --define:DEBUG.
Maybe call the new tasks "Preview___" instead of "Generate___"?

Sorry guys, I don't get it.
@pblasucci Somebody implemented the task GenerateHelpDebug. So calling > build GenerateHelpDebug does the job. But is it possible to set a switch which calls GenerateHelpDebug on >build.cmd and GenerateHelp on >release.cmd?
But that doesn't work
would appreciate if your solution could be implemented. Especially as I fail all the time.
@forki Sorry, I can't find the solution on your page.


Running SSD

Hi!
I've managed to install the custom parsing plugins from the repo, and run the samples successfully.
However, when I try to run use these parsers for a model trained by me on TLT (SSD for person detection), It doesn't seem to show any detection.
Here's my trained model configuration. I'm only listing what's different from the sample configuration.
Architecture: SSD
Input dims: 3x1280x720
Num. classes: 1
I wonder if the plugins must be adapted to the specific configuration of the network (specially regarding the class numbers).

If you are still meeting any error, please create topic with more details in https://forums.developer.nvidia.com/c/accelerated-computing/intelligent-video-analytics/transfer-learning-toolkit/
If no issue now, please ignore my comment.


feat(anvil): RPC Types migration

Motivation
Anvil is the last crate that still has pure ethers types. A result of #6219 will be that the forking backend will use the new alloy providers and RPC types, and therefore we should migrate Anvil to use the new RPC types as a result.
Solution
Migrate Anvil to use the new RPC types.
This PR will be moving a lot as it needs #6219 to be ready before this can even compile, and we'll be adding more RPC types as needed on alloy.

Merging this into #6219 since neither will compile without the other, and then we'll do smaller PRs into #6219 with more localized changes


[TypeScript] - Cannot instantiate MailService class

Issue Summary
When trying to declare a class property as a MailService TypeScript complains that we are using a value as a type
Code Snippet
import { MailService } from '@sendgrid/mail'

export class MyClass {
  mailer: MailService

  constructor() {
    this.mailer = new MailService()
    this.mailer.setApiKey('')
  }
}

Exception/Log
'MailService' refers to a value, but is being used as a type here.
Public property 'mailer' of exported class has or is using private name 'MailService'.

Technical details:

sendgrid-nodejs version: 7.0.1
node version: 10.19

Working on a fix.


[Question] Should removeEventListener in Window interface be similar to addEventListener?

Like this
    removeEventListener<K extends keyof WindowEventMap>(type: K, listener: (this: Window, ev: WindowEventMap[K]) => any, useCapture?: boolean): void;
    removeEventListener(type: string, listener: EventListenerOrEventListenerObject, useCapture?: boolean): void;

The sample in https://github.com/DefinitelyTyped/DefinitelyTyped/pull/17119/files#diff-3eedac065f66664c918123a09e849240R5 is rather useless. why would you call removeEventListener and pass in a new function.
form https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/removeEventListener (emphasis mine)

The EventTarget.removeEventListener() method removes from the EventTarget an event listener previously registered with EventTarget.addEventListener(). The event listener to be removed is identified using a combination of the event type, the event listener function itself, and various optional options that may affect the matching process; see Matching event listeners for removal.

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Missing kernel module netdevsim

Description
The netdevsim kernel module simulates network devices. In contrast to the so-called dummy kind network interfaces, netdevsims are actually virtual devices and not just network interfaces. Kernel netdevsim goes back a long time, before 5.0 IIRC. netdevsim allows testing network interface testing with multiple queues, tc/XDP BPF and limited SR-IOV API aspects, but also PTP devices, without the need for a real physical HW NIC. netdevsims support aspects, dummy network interfaces do not.
In order to run tests relying on netdevsim being available and loadable, please consider adding the following kernel modules to Github runners:

netdevsim
ptp_mock
psample

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[X] Ubuntu 24.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[ ] macOS 14
[ ] macOS 14 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Runner Image
Image: ubuntu-22.04
Version: 20240624.1.0
Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240624.1/images/ubuntu/Ubuntu2204-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240624.1
Is it regression?
no
Expected behavior
modprobe netdevsim succeeds
Actual behavior
modprobe: FATAL: Module netdevsim not found in directory /lib/modules/6.5.0-1022-azure
Repro steps
Have a Github action step:
      - name: netdevsim kmodule
        run: sudo modprobe netdevsim

Hi @thediveo, Thank you for bringing this issue to us, we are investigating on this issue and will update you after our findings.

Hello @thediveo , Thank you for your feature request. We have investigated this feature request and unfortunately, we won't be able to accept it due to security and reliability risks.
All GitHub-owned Ubuntu images use official Azure Ubuntu image as a base image. Official Azure Ubuntu images have Azure-optimized kernel and we are not able to install any kernel modules on our images.

Can you please elaborate how the netdevsim poses a security risk? The Linux kernel developers will be interested.

@thediveo - The security risks associated with enabling the netdevsim module stem primarily from its capability to simulate network devices. While this is useful for development and testing, it can also potentially be exploited in environments where strict control over network interfaces is required.
For instance, netdevsim could be used to create simulated network devices that could bypass certain security policies or be used to interfere with the networking stack in unintended ways. In a multi-tenant environment, where different users share the same infrastructure, this could pose a risk by allowing one tenant to affect the network configuration or performance of another.
Additionally, ensuring the reliability of such a module across all the varied environments in which GitHub Actions run adds complexity, particularly when using an Azure-optimized kernel. Since our images are designed to be broadly applicable and secure across diverse workloads, introducing modules that may not be widely used or tested in these environments increases the potential for unforeseen issues.
Thank you.

Then why you don't have all the other network devices disabled, such as VETH, MACVLAN, et cetera?
Thank you.

@thediveo  - veth and macvlan: These modules are designed to operate within established security boundaries and are generally well-tested for safe use in containerized and virtualized environments. Their use is often tightly controlled and monitored to ensure they do not introduce significant security risks.
netdevsim: This module, due to its capability to simulate various network conditions and devices, presents a broader range of potential misuse or unintended consequences. It could potentially interfere with or disrupt the operation of other networked services if not properly contained.
Thank you, I hope i have answered your question.

Hi @thediveo - Thank you , I am closing this ticket issue. Please feel free to open a new ticket if you face any issues related to the runner images.


New Bug List

The command : refresh_catalogue

" Buy as a gift " in the catalog

Battle Banzai is not working properly

Football is not working properly

Skateboarding is not working

Were bought with " Limited Edition " in the catalog Rare since not counted , for example, the number 10 other sold Number : 10

The Limited Edition furniture there following error : https://gyazo.com/f03ed36d19150badf1704ce9cb21573f

Going to see these bugs.

Please don't Caps.

I find the emulator very great, only the problem is the existence of these few bugs yet

After few hours I have this:

@dm5wg not just you


It would be nice to add a custom modal attributes ?

I would be nice to pass modal height, background color as attributes.

agreed


List of issues with running 2 or more builder pods in a cluster

This issue tracks the current limitations of builder as a clustered system

It uses a filesystem based lockfile to prevent 2 or more git pushes at the same time

In a multi-builder setup, this means that multiple git pushes can in fact happen at the same time
To solve, the lock will need to be distributed

It keeps git repositories on disk and runs pre-receive hooks on them to deploy

In a multi-builder setup, this means that one git push may only have to push a few refs, while another identical git push may have to push all refs. Not the end of the world
To solve, the refs list will need to be moved off of local disk to a shared location (object storage?)

This issue was moved to teamhephy/builder#39


"Spaces" link on prod-preview.openshift.io points to: https://prod-preview.openshift.io/#

See attached screenshot:

Resolved - UI has changed to remove that link.


Extend the 'SimpleContainer' properties in the 'RabbitProperties' with 'receiveTimeout'

As often mentioned in the documentation you should set a receive-timeout in the SMLC if you work with batched messages.
Currently if you want to work with "batched - messages" you can configure this in the properties, but you can not configure the receive-timeout. Therefore you always have to define the SMLC bean yourself and you can't just use the auto configured bean.
My suggestion would be to extend the org.springframework.boot.autoconfigure.amqp.RabbitProperties.SimpleContainer with the property 'receiveTimeout', you have to consider the field in the org.springframework.boot.autoconfigure.amqp.SimpleRabbitListenerContainerFactoryConfigurer.
What do you think about this or did I miss the setting?

What you are talking about is Spring Boot responsibility.
Please, consider to raise this issue exactly over there.
Thanks.

As a work around, you can do something like this...
@Bean
Object cust(SimpleRabbitListenerContainerFactory factory) {
	factory.setReceiveTimeout(5000L);
	factory.setBatchListener(true);
	return null;
}


Migrate to leveraging the tokio-io crate

This commit updates to the most recent versions (released today) of the various
Tokio libraries in use. Namely the tokio_core::io module has now been
deprecated in favor of an external tokio-io crate. This commit pulls in that
crate and uses the AsyncRead + AsyncWrite abstraction instead of Io from
tokio-core.

[ ] The commit messages match the guidelines in https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md#git-commit-guidelines

Thanks for contributing! Unfortunately, I'm here to tell you there were the following style issues with your Pull Request:

Commit: 0dcfd18e51b432f2b20a6345638577fc4256922c
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Ah and I should also mention that I dropped the relay crate while I was at it in favor of futures::unsync, but I can back out that change if you'd prefer.

Thanks for contributing! Unfortunately, I'm here to tell you there were the following style issues with your Pull Request:

Commit: 41fc8dff3360a955693247eee416ba0c5186f5ee
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/hyperium/hyper/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Ok I believe that should handled the blocked read case?

Great, thanks!


Contact subpage

Please move the address from the zip code a line below.

Remove links ("Contact Us") from each step from "Cooperation with 3mdeb" section that simply redirect to the same subpage.

confirmed


Add toArray

I'm not sure whether it is proper type declaration for toArray. but this may facilitates following.
do
  b <- body
  li <- toArray =<< find "li" bi
  texts <- traverse getText li
  traverse log texts

Does toArray return a live array? i.e. if the DOM gets updated after calling toArray, will the result change, or is it safe to assume this returns an immutable snapshot?

I'll add this in the next release, creating a copy of the array to be safe. Thanks!


ENH: add everything necessary to build hkl through conda

gobject-introspection changes pushed through by @tacaswell made this possible, finally. Still required a bunch of different supporting libraries, all of which should be included in this PR (I believe). At least, I can conda install hkl with only my channel in my condarc.
Set GI_TYPELIB_PATH with environment activation scripts. Upon installation, you'll need to deactivate/activate to get that setup properly.
Many of the recipes are based on those from pkgw's repo, but many modifications were necessary along the way - py3cairo with waf was a big pain, for one. Should get around to opening a PR there at some point.
May still be some messiness in here - so take a look before merging.

What's the status of this?

Building/working as far as I know, but no one else has reviewed or tried it.


Confirm lower bounds on shape1 and shape2 parameters in BurrIII3

ie make sure not hitting 0.05 before other shape parameter hits 20

Note that the BurrIII distribution c and k parameters are dependent on the data scaling. This is the cause of the undesirable behavior in Burrlioz, which sometimes results in a different distribution depending on the units (micrograms versus millegrams), for example.

A solution to this is to rescale the data relative to the maximum value for this distribution by default. Suggest this is done by default for the ssd_fit_burrlioz function. How to handle this else-wise needs discussion.

It would be good to know how to set the boundaries for the burrIII with rescaled data. This could potentially be done using a simulation study, based on the three distributions.
Note also a better solution to rescaling is to have an algorithm that determines appropriate smart boundaries given the data range.


[WEB] CORS problem comes when I upgrade from flutter 1 to 2.

Everything was good, then I decided to upgrade to flutter 2. After migration, I found all the network images have an CORS error.
I also added required header to my server side, you may check the response as an example:
https://apitest.food2u.de/media/restaurant_logo/logo_NJAo6Zq.jpg
But I still have this CORS error with network image only, (not on any other dio requests)
Then, I found something interesting.
I use vscode for development. I normally test it by "Launching lib/main.dart on Chrome in debug mode"

It opens a total clean chrome, and all the CORS problems are here.
Then, I opened my normal chrome (with all the history, user info, etc) to the localhost url. Wow, everything works here?!
I am afraid that I am too confused to explain it well. Thanks for understanding.
Here is my flutter doctor -v result:

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.0.1 20B29 darwin-x64, locale en-DE)
    • Flutter version 2.0.4 at /Users/kainann/Documents/flutter
    • Framework revision b1395592de (3 weeks ago), 2021-04-01 14:25:01 -0700
    • Engine revision 2dce47073a
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0-rc2)
    • Android SDK at /Users/kainann/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0-rc2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Community Edition (version 2019.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 90.0.4430.85

Hi @Kainanchen
I can load the image using image.network with your link in chrome launched by Flutter in debug mode

code sample
[✓] Flutter (Channel stable, 2.0.5, on Microsoft Windows [Version 10.0.19042.928], locale en-US)
    • Flutter version 2.0.5 at C:\Users\Taha\Code\flutter_stable
    • Framework revision adc687823a (6 days ago), 2021-04-16 09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at C:\Users\Taha\Code\SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = C:\Users\Taha\Code\SDK
    • Java binary at: C:\Users\Taha\Code\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✓] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.3)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.9.31129.286
    • Windows 10 SDK version 10.0.19041.0

[✓] Android Studio (version 4.1.0)
    • Android Studio at C:\Users\Taha\Code\android-studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[✓] IntelliJ IDEA Community Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.3
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.55.2)
    • VS Code at C:\Users\Taha\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM M025F (mobile)                  • R9ZR205XX0A   • android-arm    • Android 10 (API 29)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 10 (API 29) (emulator)
    • Windows (desktop)                  • windows       • windows-x64    • Microsoft Windows [Version 10.0.19042.928]
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 90.0.4430.85
    • Edge (web)                         • edge          • web-javascript • Microsoft Edge 89.0.774.77

! Doctor found issues in 1 category.

Can you please upgrade to the latest  stable and try again
flutter channel stable
flutter upgrade --force
flutter doctor -v

Thanks for your test!
I guess it is just a problem with my Chrome. It works on another laptop.
I would them try to find what the problem is with my Chrome.


Allow responses to be streamed.

Never expands >8kb responses into memory
It seems less dangerous to avoid closing Response objects than to explode large responses in memory

NetflixOSS » feign » feign-pull-requests #181 SUCCESS
This pull request looks good

NetflixOSS » feign » feign-pull-requests #182 SUCCESS
This pull request looks good

looking good. let me know when you are ready for realz

NetflixOSS » feign » feign-pull-requests #183 SUCCESS
This pull request looks good

Cleaned up the tests, I think we're good to go :-)
Thanks!

NetflixOSS » feign » feign-pull-requests #184 SUCCESS
This pull request looks good

oops one last thing add a note in the CHANGELOG for 8.13
Thanks tons for making a compatible way to address this feature!

nm I'll work this out on the way in

Sorry about that, fell asleep. Thanks for reviewing/merging so quickly!
Any idea when to expect 8.13 to be published to maven?

sorry this never made it out. I've now released it in 8.16.2


Update 4.5 branch with L10N resources files from Transifex 20151120

Open PR before the 4.5.3 release to update the L10N resources files from Transifex to the 4.5 branch.
Merge this PR just before the start of the release process.
cc @bhaisaab

LGTM, thanks @milamberspace


Add Binder badge to Literate tutorials

Related to #400.
https://juliahealth.org/KomaMRI.jl/previews/PR403/

Added Project.toml to gh-pages.
https://github.com/JuliaHealth/KomaMRI.jl/blob/gh-pages/Project.toml


Arm compability: Why in helm chart used bitnami images? I've tried official images and make pods work

Feature Description
There is a problem with bitnami inages used in HELM chart(yes they're still not supported on arm64)
I just changed locally images to official in my deployments and gitea in my local kubernetes 1.24(arm64, debian 11)  started to work.
Images used: gitea/gitea:1.16.8,  docker.io/memcached:latest, docker.io/postgres:12.12-bullseye

So, why in helm chart are used binami images which are x86_64 only?
Screenshots
No response

Please post this on https://gitea.com/gitea/helm-chart


Fix for resource_local_to_scene in arrays.

This fixes #71243, if you download the sample project and run it with this version the arrays are properly local.

Thanks for tackling this! ❤
However, it doesn't seem to fix the issue in the current state. Running the MRP with your PR applied, there still are unduplicated resources, leaving the debug output the same as in the issue description (highlighted):

Your new code seems to be called and duplicating properly, so I'm not sure what's going wrong.

Also, you should likely remove the fixes #... from the description, since it does not handle dictionaries. The issue would automatically close on merge if you keep the wording like this.

Debugging...
I tried adding print_line(vformat("%s from %s to %s", node->get_instance_id(), res->get_instance_id(), local_dupe->get_instance_id())); below the line Ref<Resource> local_dupe
I then changed the MRP to log get_instance_id() and gave each a unique letter in the output:
// [node] from [res] to [local_dupe]
[X] from [A] to [B]
[X] from [C] to [D]
[Y] from [B] to [E]
[Y] from [D] to [F]
pre-modified first ---------
simple:
true	1	[G]
array:
true	2	[E]
true	3	[F]
dict:
true	4	[H]
sub:
true	5	[I]
sub array:
true	6	[J]
sub dict:
true	20	[K]
check first --------- (should be same as above)
simple:
true	1	[G]
array:
true	4	[E]
true	6	[F]
dict:
true	8	[H]
sub:
true	5	[I]
sub array:
true	6	[J]
sub dict:
true	20	[K]
check second --------- (should be *= 2 on each field)
simple:
true	2	[L]
array:
true	4	[E]
true	6	[F]
dict:
true	8	[H]
sub:
true	10	[M]
sub array:
true	12	[N]
sub dict:
true	40	[O]

Note how [Y]'s scene duplicates seem to re-use the resources of [X].

That's strange, as I thought it was working here. I have another test project where this fixed my issues, and the logs for the MRP seem right on my end.
pre-modified first ---------
simple:
true	1	LocalToSceneTests1:<Node#26457670861>
array:
true	2	LocalToSceneTests1:<Node#26457670861>
true	3	LocalToSceneTests1:<Node#26457670861>
dict:
true	4	<Object#null>
sub:
true	5	LocalToSceneTests1:<Node#26457670861>
sub array:
true	6	LocalToSceneTests1:<Node#26457670861>
sub dict:
true	20	LocalToSceneTests1:<Node#26457670861>
check first --------- (should be same as above)
simple:
true	1	LocalToSceneTests1:<Node#26457670861>
array:
true	2	LocalToSceneTests1:<Node#26457670861>
true	3	LocalToSceneTests1:<Node#26457670861>
dict:
true	8	<Object#null>
sub:
true	5	LocalToSceneTests1:<Node#26457670861>
sub array:
true	6	LocalToSceneTests1:<Node#26457670861>
sub dict:
true	20	LocalToSceneTests1:<Node#26457670861>
check second --------- (should be *= 2 on each field)
simple:
true	2	LocalToSceneTests2:<Node#26608665818>
array:
true	4	LocalToSceneTests2:<Node#26608665818>
true	6	LocalToSceneTests2:<Node#26608665818>
dict:
true	8	<Object#null>
sub:
true	10	LocalToSceneTests2:<Node#26608665818>
sub array:
true	12	LocalToSceneTests2:<Node#26608665818>
sub dict:
true	40	LocalToSceneTests2:<Node#26608665818>```

Hmm I redownloaded the MRP and it indeed works as expected now! :tada:
Checked the diff between the two and this change stands out to me:

(left is working, right is broken)
Not sure what happened, or if it's something I unknowingly did 😅

Could you squash the commits? See PR workflow for instructions.

I'm getting a deja vu here.
This only handles resources in arrays, but arrays can be nested. Then there are also Dictionaries, which can use Resources both for keys and values. And they can be nested too. Also I'm not sure if nested resources are handled or if it's for nodes only.
Ultimately we'd end up with a unified method that just scans everything recursively. I remember we have at least 3 of them.
Although that's probably all corner cases. The issue mentions also Dictionaries, so I think this PR could also handle them. It doesn't need to be recursive for now, but it would be nice if the copied code could be moved to some method.

btw I also made a simpler reproduction project: CustomLocalToScene.zip
If all shapes have different size it means the bug is fixed.

This zip is missing the script I think.
I'll try to implement the method you outlined. As for dictionaries, I'm not certain how to tackle it, should I check for object and then dictionary? (pseudo code below)
if (value.get_type() == Variant::OBJECT) {
    if (value.get_type() == Variant::DICTIONARY) {
        // Check for resources in keys and values
    }
}

And yeah, the nesting is certainly an issue, I'll see if I can deal with it too while I'm at it.

As for dictionaries, I'm not certain how to tackle it, should I check for object and then dictionary?

You can get inspired by my PR that tackled the other half of the issue: https://github.com/godotengine/godot/pull/71578
There's a switch-case which handles all cases (including nesting, arrays, dictionary keys and values).

This zip is missing the script I think.

Sorry, here's a fixed one:
CustomLocalTooScene.zip

As for dictionaries, I'm not certain how to tackle it, should I check for object and then dictionary?

Dictionary is not Object.
Also I wouldn't really bother for recursive checking, as it often caused performance problems. For now handling only top level properties is fine I think.

The issue so far is that the resource is always duplicated now, even if it already was. What this does (to my understanding) is that the values get reset every time you open the scene.
For example, I open a scene and set the radius of a CircleShape2D to 125. It is independent from the parent scene, great! When I reopen the scene however it is duplicated again and the radius is reset back to the original value from the parent scene.
void SceneState::setup_local_resource(Ref<Resource>& res, Array& origin_array, const int origin_array_index, const SceneState::NodeData& n, HashMap<Ref<Resource>, Ref<Resource>>& resources_local_to_sub_scene, Node* node, const StringName sname, HashMap<Ref<Resource>, Ref<Resource>>& resources_local_to_scene, int i, Node** ret_nodes, SceneState::GenEditState p_edit_state) const
{
	if (!res->is_local_to_scene()) {
		printf("Resource was not local.\n");
		return;
	}
	if (n.instance >= 0) { // For the root node of a sub-scene, treat it as part of the sub-scene.
		//origin_array[origin_array_index] = get_remap_resource(res, resources_local_to_sub_scene, node->get(snames[nprops[j].name]), node);
		origin_array[origin_array_index] = get_remap_resource(res, resources_local_to_sub_scene, node->get(sname), node);
		printf("Remapping.\n");
	} else {
		HashMap<Ref<Resource>, Ref<Resource>>::Iterator E = resources_local_to_scene.find(res);
		Node* base = i == 0 ? node : ret_nodes[0];
		if (E) {
			origin_array[origin_array_index] = E->value;
			printf("Found original, no change.\n");
		} else if (p_edit_state == GEN_EDIT_STATE_MAIN) {
			// For the main scene, use the resource as is.
			//res->configure_for_local_scene(base, resources_local_to_scene);
			res->duplicate_for_local_scene(base, resources_local_to_scene);
			resources_local_to_scene[res] = res;
			printf("Main scene.\n");
		} else {
			// For instances, a copy must be made.
			Ref<Resource> local_dupe = res->duplicate_for_local_scene(base, resources_local_to_scene);
			resources_local_to_scene[res] = local_dupe;
			origin_array[origin_array_index] = local_dupe;
			printf("Duplicate for local scene.\n");
		}
	}
}

My guess is that somehow it's not finding the resource when it runs this for some reason.
HashMap<Ref<Resource>, Ref<Resource>>::Iterator E = resources_local_to_scene.find(res);
Node* base = i == 0 ? node : ret_nodes[0];

Your test scene works btw, when the nodes are modified at runtime they are properly duplicated, so that's good.

I'm so close, but I can't put together the final line(s) needed. The reason @KoBeWi 's method doesn't work is because the final variant needs to be assigned to value, but we were just assigning it to the Ref previously. I made a version that returns a Ref and assigns it to value and it works now.
I imagine it's the same thing with the array, but despite attempting to assign value to the modified array I still run into the same issues as above. I'm not sure if Arrays have a special way of being assigned though that I might be missing however.
This is my version of your method now btw:
Ref<Resource> SceneState::make_local_resource(Variant& r_value, const SceneState::NodeData& p_node_data, HashMap<Ref<Resource>, Ref<Resource>>& p_resources_local_to_sub_scene, Node* p_node, const StringName p_sname, HashMap<Ref<Resource>, Ref<Resource>>& p_resources_local_to_scene, int p_i, Node** p_ret_nodes, SceneState::GenEditState p_edit_state) const
{
	Ref<Resource> res = r_value;
	if (res.is_null() || !res->is_local_to_scene()) {
		return r_value;
	}

	if (p_node_data.instance >= 0) { // For the root node of a sub-scene, treat it as part of the sub-scene.
		return get_remap_resource(res, p_resources_local_to_sub_scene, p_node->get(p_sname), p_node);
	} else {
		HashMap<Ref<Resource>, Ref<Resource>>::Iterator E = p_resources_local_to_scene.find(res);
		Node* base = p_i == 0 ? p_node : p_ret_nodes[0];
		if (E) {
			return E->value;
		} else if (p_edit_state == GEN_EDIT_STATE_MAIN) { // For the main scene, use the resource as is
			res->configure_for_local_scene(base, p_resources_local_to_scene);
			p_resources_local_to_scene[res] = res;
			return res;
		} else { // For instances, a copy must be made.
			Ref<Resource> local_dupe = res->duplicate_for_local_scene(base, p_resources_local_to_scene);
			p_resources_local_to_scene[res] = local_dupe;
			return local_dupe;
		}
	}
}

Getting more specific: the issue seems to be that the default value for the array is not properly referencing the value from the parent scene:
if (!pinned_props.has(name)) {
    bool is_valid_default = false;
    // FIXME: the default_value is the current value rather than the value in the parent scene
    Variant default_value = PropertyUtils::get_property_default_value(p_node, name, &is_valid_default, &states_stack, true);
        if (is_valid_default && !PropertyUtils::is_property_value_different(value, default_value)) {
            continue;
        }
}

I believe the error is in the PropertyUtils::get_node_states_stack method, but this is getting way over my head unfortunately.

Is this intended to be a work in progress currently? If so you might want to convert it to a draft 🙂

Sorry for needing the workflow to be reset so often, I made sure to check my warnings this time so hopefully the checks pass this time!

Looks better now, but something is wrong with Dictionaries. When you have both key and value local to scene, they double when loading the scene
Also you should remove the commented out code.

Thanks! And congrats for your first merged Godot contribution :tada:


Added an example to read back a module's configuration

ℹ This PR branches from NI\main

[x] This contribution adheres to CONTRIBUTING.md.

TODO: Check the above box with an 'x' indicating you've read and followed CONTRIBUTING.md.
What does this Pull Request accomplish?
Adds an example showing how to read back a module's configuration using Get Slot
Why should this Pull Request be merged?
This example is a requirement from the feature specification for the scan engine custom device scripting
What testing has been done?
Manual testing. Should we create unit tests for the examples to ensure these run without errors?

The example itself looks fine, but the examples build is failing locally for me (and on the build machine). Not sure why.

The example itself looks fine, but the examples build is failing locally for me (and on the build machine). Not sure why.

@rtzoeller I did some quick digging on this, and it looks like the VIs/project are currently linking against scripting calls that are not in this branch's build (or perhaps legacy).

Making sure the repo is clean at that branch, building everything fresh, then forcing a recompile on the VIs seems to get rid of those dependencies, and the VIs executes successfully. However, the build still fails as those missing dependencies show back up when attempting to build.
Selecting two additional exclusions allows the build to succeed, but I'm not sure if that is a valid workaround.

@rtzoeller I did some quick digging on this, and it looks like the VIs/project are currently linking against scripting calls that are not in this branch's build (or perhaps legacy).

Making sure the repo is clean at that branch, building everything fresh, then forcing a recompile on the VIs seems to get rid of those dependencies, and the VIs executes successfully. However, the build still fails as those missing dependencies show back up when attempting to build.
Selecting two additional exclusions allows the build to succeed, but I'm not sure if that is a valid workaround.

@Karl-G1 I did a clean build locally, including clearing out vi.lib and the LabVIEW object cache and I'm still seeing this issue.
@oscarfonloz are you able to build the examples with your change?

@Karl-G1 I did a clean build locally, including clearing out vi.lib and the LabVIEW object cache and I'm still seeing this issue.
@oscarfonloz are you able to build the examples with your change?

Selecting two additional exclusions allows the build to succeed, but I'm not sure if that is a valid workaround.

My litmus test of "what does R+F do?" says that we should not need to select those exclusions.

Selecting two additional exclusions allows the build to succeed, but I'm not sure if that is a valid workaround.

My litmus test of "what does R+F do?" says that we should not need to select those exclusions.

Doing some more digging, it appears that the post-build action is failing with the nondescript error. I will investigate.

Doing some more digging, it appears that the post-build action is failing with the nondescript error. I will investigate.

Thanks @rtzoeller. I did the following experiment and got weird results:

Checkout the branch
Merge with what we currently have in main
Build the scripting distribution
Replace the output in vi.lib, per required by the examples
Open the example

I see an error telling me the classes are broken because of the owning library:

I am unsure of why at this point :(

Thanks @rtzoeller. I did the following experiment and got weird results:

Checkout the branch
Merge with what we currently have in main
Build the scripting distribution
Replace the output in vi.lib, per required by the examples
Open the example

I see an error telling me the classes are broken because of the owning library:

I am unsure of why at this point :(

@Karl-G1 it looks like your solution is the correct one.
The post-build step is failing due to Modules.lvlibp not being copied correctly, since it's in vi.lib. This wasn't an issue for R+F, as while it makes use of packed project libraries, they are not use by the scripting examples (they are engine-only). Although there is an existing example, it doesn't script any specific modules, and as such does not pull the packed project library in as a dependency - which is why the build has succeeded up until now.
@oscarfonloz please check the "Exclude dependent shared libraries" option in the "Additional Exclusions" section of the build specification. That should fix the issue.

@Karl-G1 it looks like your solution is the correct one.
The post-build step is failing due to Modules.lvlibp not being copied correctly, since it's in vi.lib. This wasn't an issue for R+F, as while it makes use of packed project libraries, they are not use by the scripting examples (they are engine-only). Although there is an existing example, it doesn't script any specific modules, and as such does not pull the packed project library in as a dependency - which is why the build has succeeded up until now.
@oscarfonloz please check the "Exclude dependent shared libraries" option in the "Additional Exclusions" section of the build specification. That should fix the issue.

@oscarfonloz I am going to wait to investigate fixing the build until @debryant has another in-flight example ready.

@oscarfonloz I am going to wait to investigate fixing the build until @debryant has another in-flight example ready.

Note that I opted to create a local example subVI that reads the name and mode rather than add such a VI to the API. Waffled on whether to add it to the Example lvlib or not. I could go either way. The VIs in that library are esp needed in a lvlib so that they aren't cross loaded with the same named VI in other example directories.
The changes to the other VIs are caused by a small change to the icon only.

Note that I opted to create a local example subVI that reads the name and mode rather than add such a VI to the API. Waffled on whether to add it to the Example lvlib or not. I could go either way. The VIs in that library are esp needed in a lvlib so that they aren't cross loaded with the same named VI in other example directories.
The changes to the other VIs are caused by a small change to the icon only.

In the documentation Read Configuration with Known Module.vi, the slot numbers are incorrect. The slots in the custom device (as with physical cRIOs) are 1-indexed, but the documentation refers to "slot 0" and "slot 1". These should either be "slot 1" and "slot 2", or "first slot" and "second slot".

In the documentation Read Configuration with Known Module.vi, the slot numbers are incorrect. The slots in the custom device (as with physical cRIOs) are 1-indexed, but the documentation refers to "slot 0" and "slot 1". These should either be "slot 1" and "slot 2", or "first slot" and "second slot".


RFC: Built-in Moti + SVG Integration

It would be nice to do something like this:
import { motify } from 'moti'
import { Rect } from 'react-native-svg'

const MotiRect = motify(Rect)({ isSvg: true })

Then, we could automatically animate SVG props:
<MotiRect
  animate={{
    x: width / 2,
  }}
/>

All SVG props would be animatable there. Let me know if you have any thoughts about this API.
This would bring the benefits of all Moti APIs and its simplicity to SVGs. It would also let you use animate presence with SVG animations.


Move WFI encoding to volume I

WFI is a generic instruction. By defining its encoding in the Unix privileged specs, any other privileged specs will have to redefine it, leading to redundancy and possible inconsistencies.
Similarly to the ECALLand EBREAK encodings defined in volume I, WFI can also be defined in Volume I, with the definition striped from any mode-M, mstatus, etc specifics (the privileged behaviour can be explained in each privileged specs).
Profiles that do not need this feature can implement it as NOP.
And the name 'Interrupt-Management Instructions' is not very inspired. WFI is practically a power management instruction.

We understand the argument that this could have been defined as an unprivileged instruction, with its use modulated by privileged CSRs.  For compatibility we'd define a new UWFI instruction that was unprivileged, but with the same effect, rather than change existing instruction, which has supervisor privilege.

Can this be resolved?

We have a proposal for a WFMI, which as well as being an unprivileged instruction also is different in that it is allowed to continue sleeping while lower-privileged mode interrupt is pending-and-enabled.  This was developed in fast interrupts group and discussed here: https://github.com/riscv/riscv-fast-interrupt/issues/31

Assuming this has been dealt with and can be closed? If not, please reopen.


Add future contracts for NK, IN, TW and HSI

Added Configuration for contracts NK, IN, TW (SGX) and HSI(HKFE)
Description

Added Exchange (SGX and HKFE)
Added contracts in symbol properties
Added contracts trading hours in market-hours file
Added future expiry functions
Added Unit Tests

Motivation and Context
Allows Nikkie 225 Index futures, Nifty Fifty Index futures, MSCI Taiwan Index futures to be traded on SGX and Hang Seng Index futures on HKFe
Requires Documentation Change
No
How Has This Been Tested?
Added unit tests
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[X] My code follows the code style of this project.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.
[ ] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Thanks for suggestion. I will update the pull request with the margin

For conversion to USD for margin, for a period what exchange rate should be considered? Does it need to be exact or any value between the dates could be used. For example for Nikkie 250 (Yen Denominated) from period
19th June 2020 - 25th June 2020  has following values =>  770,000(Maint.), 847,000 (Initial) what exchange rate should be considered ?

I have added margin files for sgx and hkfe exchange.

Margins are in USD. Exchange rate is of the date specified in the file
Margins are rounded to nearest integer


SubSubtable are not always in same order

Tested in tag 1.0.4.
Adding the test case to rust/src/main.rs:
    #[case::subsubtable(
        indoc ! {r#"
    [project]
    [tool.coverage.paths]
    a = 1
    [tool.coverage.report]
    a = 2
    [tool.coverage.run]
    a = 3
    "#},
        indoc ! {r#"
    [project]
    classifiers = [
      "Programming Language :: Python :: 3 :: Only",
      "Programming Language :: Python :: 3.8",
    ]
    [tool.coverage.paths]
    a = 1
    [tool.coverage.report]
    a = 2
    [tool.coverage.run]
    a = 3
    "#},
        2,
        true,
        (3, 8)
    )]

Expected Result:
"tool.coverage.paths", "tool.coverage.report" and "tool.coverage.run" are sorted by the table names.
Actual Result:
The order are quite random. cargo test may pass/fail occasionally.

PR welcome 🤗

PR opened: https://github.com/tox-dev/pyproject-fmt-rust/pull/9

This can probably be closed now


Sticky headers

In my vertical scrolling calendar (similar to example2) I would like to have sticky headers. I've tried using this solution making a custom RecyclerView.ItemDecoration but, with "CalendarAdapter" being internal and not using the "viewType" parameter, I find it really difficult to make it work . Do you have any suggestions in how to implement such a thing? Internal or external to the library I could implement it myself, I'm just seeking some advice.

I played around with example 2 to achieve something like this. Since CalendarView extends from RecyclerView, I added a scroll lister and just updated a view which I put above the weekday texts on the toolbar.
Here's the result:

It's not exactly what I wanted because using the previously mentioned RecyclerView.ItemDecoration the current header gets pushed away from the previous one. But still the result you helped me getting is totally acceptable, so thank you really much.
Here's the result:

.

Glad I was able to help! Closing this now.


Cannot provide oauth2 with a proper config causing crash on Google App Engine

tl;dr; https://godoc.org/golang.org/x/oauth2#Config.Exchange on Google App Engine needs to get a context.Context from appengine.NewContext(request)
Longer: I've tried to deploy an app written as stand alone to GAE, worked fine, but when doing a oauth2 with Fb i'm getting an error. It's reproducible on a local GAE playground. The reason is that a GAE provides own http client and http.DefaultClient is blocked.
For now I'm using a hack:

a tiny middleware before authboss sets context through gorilla.context
a modified version of authboss checks if Context is available

I don't know if it worth fixing, but writing about it to save others time (took me few hours to precisely find the place of error). Maybe  just mention in the documentation.
In general, I think it's worth to consider the Google approach to handlers:
https://godoc.org/golang.org/x/net/context
A solution might be to allow to specify an option (a global in oauth2 subpackage):
var ContextProvider func(req *http.Request) context.Context {
    return oauth2.NoContext
}

It would be easier than refactoring all code to provide third argument.
I've tested, second approach is nicer.
notice, one must import google.golang.org/appengine instead standard appengine

Ok, the above was only a part of problem, the client has to be also provided to oauth2 Callback to fetch profile.

Meditating on this issue, will probably accept the code as is. Just want to be sure about it. It is bringing in another dependency though. And there may be better ways to support GAE.

I'm open for other solutions. The one I've introduced adds x/net/context, although it's not a standard it's widely used among Google's internal/external code.
The Context and client are a request specific objects, they have to be injected on each request. As I didn't want to depend on appengine package, i've decided to go for factory like function and allowing a user to configure it.
I've tested the approach described in first comment, but it was ugly.

This PR was merged.


Question: What is the purpose?

What's the point of bundling .net core together with frontend such as react/angular & webpack? Is it just to ease publication/development? Shouldn't they be mutually exclusive and communicating via. restful api's?
I notice these great boilerplates such as this where you combine both the server-side .net core together with webpack + angular/react for example. Is this to achieve intellisense, easier publication/distribution? Or what exactly is the purpose?
Thanks!

Yeah, it's easier to deploy your app this way, also, how would you test your app if the front-end part comes separately from the backend?


HIVE-26339: HIVE-26047 Related LIKE pattern issues

What changes were proposed in this pull request?

Vectorized LIKE udf is taking proportionately higher time depending on the size of input string in UDF. And, I found a problem with some regular expressions.
Why are the changes needed?

To support filter condition based on input data.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Added testcase as part of PR.

@deniskuzZ I have corrected what you pointed out, so could you please check it?

@ryukobayashi, found bunch of issues, please check below snippet
for (int i = 0; i < length; i++) {
        char n = pattern.charAt(i);
        if (n == '_') { // such as "a_b"
          if (lastChar != '\\') { // such as "a_bc"
            return null;
          } else { // such as "abc\%de%"
            strPattern.append(pattern, beginIndex, i - 1);
            beginIndex = i;
          }
        } else if (n == '%') {
          if (i == 0) { // such as "%abc"
            lastType = UDFLike.PatternType.END;
            beginIndex = 1;

          } else if (i < length - 1) {
            if (lastChar != '\\') { // such as "a%bc"
              lastType = UDFLike.PatternType.CHAINED;
            } else { // such as "a\%bc"
              strPattern.append(pattern, beginIndex, i - 1);
              beginIndex = i;
            }
          } else {
            if (lastChar != '\\') {
              endIndex = length - 1;
              if (lastType == UDFLike.PatternType.END) { // such as "%abc%"
                lastType = UDFLike.PatternType.MIDDLE;
              } else if (lastType != UDFLike.PatternType.CHAINED) {
                lastType = UDFLike.PatternType.BEGIN; // such as "abc%"
              }
            } else { // such as "abc\%"
              strPattern.append(pattern, beginIndex, i - 1);
              beginIndex = i;
              endIndex = length;
            }
          }
        }
        lastChar = n;
      }

      strPattern.append(pattern, beginIndex, endIndex);
      simplePattern = (lastType == UDFLike.PatternType.CHAINED) ? pattern : strPattern.toString();

      return (type == lastType) ? simplePattern : null;

@deniskuzZ

found a bunch of issues, please check if we can replace with the below snippet

I will try it.

looks like we get Complex type only when "_" is present, is that correct?

Yes, it hasn't changed from the original logic.

@deniskuzZ I have fixed it as per your suggestion. But, we did not integrate it with UDFLike because it would require major fixes to the logic. Please let me know if you think it should be fixed.

@deniskuzZ I have fixed it as per your suggestion. But, we did not integrate it with UDFLike because it would require major fixes to the logic. Please let me know if you think it should be fixed.

hi @ryukobayashi, since we directly identify the pattern, why do we need multiple matcher factories, can we have just 1 factory?
public class FilterStringColLikeStringScalar extends AbstractFilterStringColLikeStringScalar {
  private static final long serialVersionUID = 1L;

  private transient final static List<CheckerFactory> checkerFactories = ImmutableList.of(
    pattern -> {
      UDFLikePattern udfLike = UDFLikePattern.matcher(pattern);
      try {
        return udfLike.checker.getConstructor(String.class).newInstance(
          udfLike.format(pattern));
      } catch (Exception e) {
        throw new IllegalArgumentException("unable to initialize Checker");
      }
    });

  public FilterStringColLikeStringScalar() {
    super();
  }

  public FilterStringColLikeStringScalar(int colNum, byte[] likePattern) {
    super(colNum, null);
    super.setPattern(new String(likePattern, StandardCharsets.UTF_8));
  }

  @Override
  protected List<CheckerFactory> getCheckerFactories() {
    return checkerFactories;
  }

  private enum UDFLikePattern {
    BEGIN(BeginChecker.class),
    END(EndChecker.class),
    MIDDLE(MiddleChecker.class),
    NONE(NoneChecker.class),
    CHAINED(ChainedChecker.class),
    COMPLEX(ComplexChecker.class);

    Class<? extends Checker> checker;

    UDFLikePattern(Class<? extends Checker> checker) {
      this.checker = checker;
    }

    private static UDFLikePattern matcher(String pattern) {
      UDFLikePattern lastType = NONE;
      int length = pattern.length();
      char lastChar = 0;

      for (int i = 0; i < length; i++) {
        char n = pattern.charAt(i);
        if (n == '_' && lastChar != '\\') { // such as "a_bc"
          return COMPLEX;
        } else if (n == '%') {
          if (i == 0) { // such as "%abc"
            lastType = END;
          } else if (i < length - 1) {
            if (lastChar != '\\') { // such as "a%bc"
              lastType = CHAINED;
            }
          } else {
            if (lastChar != '\\') {
              if (lastType == END) { // such as "%abc%"
                lastType = MIDDLE;
              } else if (lastType != CHAINED) {
                lastType = BEGIN; // such as "abc%"
              }
            }
          }
        }
        lastChar = n;
      }
      return lastType;
    }

    private String format(String pattern) {
      int startIndex = 0;
      int endIndex = pattern.length();

      switch (this) {
        case BEGIN:
          endIndex--;
          break;
        case END:
          startIndex++;
          break;
        case MIDDLE:
          startIndex++;
          endIndex--;
          break;
        case COMPLEX:
          return "^" + UDFLike.likePatternToRegExp(pattern) + "$";
      }

      return pattern.substring(startIndex, endIndex);
    }
  }
}

@deniskuzZ This is original and I don't know why multiple matcher factories are needed. As you opinion, one factory should be no problem. So, I fixed.

@deniskuzZ This is original and I don't know why multiple matcher factories are needed. As you opinion, one factory should be no problem. So, I fixed.

👍 nice,
1 last thing, I forgot to post it, could we please override format method per enum
private enum UDFLikePattern {
    BEGIN(BeginChecker.class) {
      @Override
      String format(String pattern) {
        return pattern.substring(0, pattern.length() - 1);
      }
    },
    END(EndChecker.class) {
      @Override
      String format(String pattern) {
        return pattern.substring(1);
      }
    },
    MIDDLE(MiddleChecker.class) {
      @Override
      String format(String pattern) {
        return pattern.substring(1, pattern.length() - 1);
      }
    },
    COMPLEX(ComplexChecker.class) {
      @Override
      String format(String pattern) {
        return "^" + UDFLike.likePatternToRegExp(pattern) + "$";
      }
    },
    CHAINED(ChainedChecker.class),
    NONE(NoneChecker.class);

    Class<? extends Checker> checker;

    UDFLikePattern(Class<? extends Checker> checker) {
      this.checker = checker;
    }

    String format(String pattern) {
      return pattern;
    }

@deniskuzZ Thanks for review. I fixed.

@deniskuzZ Thanks! test passed.


Add event projection rebuild failure scenario

Running into some undefined behavior with EventProjection, I assumed that each call to ProjectAsync would be (somewhat) transactional, but it appears to end up in the operations queue as part of a batch when running rebuilds. This can result in an entity previously being created now being unavailable for a follow up handler.

@Hawxy Couple comments:

You'll need to use an identity session in order for that to work at all even in the inline mode. Otherwise there's no magic "find the previously stored document"
Any reason why you're not using an aggregation? That's completely optimized for this kind of thing
I "fixed" the rebuild, but it's going to require a change that will make other event projections slower. I'm iffy


Update revault_net with latest message serialization

We now finally conform to practical-revault!

Really ? :sob:

ACK c99cd52

ACK 5ab9e4e


[ZEPPELIN-2909]. Support shared SparkContext across language in livy interpreter

What is this PR for?
LIVY-194 implement the shared SparkContext across languages, this ticket is trying to integrate this feature.
What type of PR is it?
[ Feature ]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-2909

How should this be tested?
Tested is added
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@prabhjyotsingh Could you help review it ? Thanks

This looks good, with one minor comment, this was one long pending feature missing in Livy a big +1 for adding this functionality.

@felixcheung User don't need to explicitly enable this feature, it is enable by default if user use livy 0.5. As this feature is already implemented in zeppelin's native spark interpreter, livy just try to make the behavior as consistent as zeppelin spark interpreter.

still, I think this feature is distinctive enough that we should document and bring some visibility (even if it just works)

@felixcheung  It is documented here. https://github.com/apache/zeppelin/blame/master/docs/interpreter/livy.md#L219

ok thanks, didn't realize it's been 7 months... :)