[Q] How can I get splicemonitor to decode more than just the first cue?

I have an issue where, when subscribing to an active multicast, only the first SCTE 35 cue gets decoded.
This issue seems unique to this particular provider (Adcuratio), where the first cue comes through and everything after doesn't seem to be recognized as a SCTE-35 message.
Here is an example:
* SCTE 35 Splice Information, TID 252 (0xFC), PID 256 (0x0100)
  Short section, total size: 57 bytes
  - Section 0:
    Protocol version: 0
    Encryption: none
    PTS adjustment: 0x000000000
    CW index: 0x00 (0), tier: 0xFFF (4095)
    Command type: 0x06 (TimeSignal), size: 5 bytes
    Time: 0x0F04CD0E8 (4,031,566,056, 44,795,178 ms)
    - Descriptor 0: SCTE 35 Segmentation (0x02, 2), 30 bytes
      Identifier: 0x43554549 ("CUEI")
      Segmentation event id: 0x00000003, cancel: 0
      Program segmentation: 1, has duration: 1, not restricted: 1
      Segment duration: 10800000
      Segmentation upid type: 0x08 (TI)
      Upid data (8 bytes): 00 00 00 00 02 A6 2B 1C
      Segmentation type id: 0x34 (Provider Placement Opportunity Start)
      Segment number: 1, expected segments: 1
      Sub-segment number: 1, expected sub-segments: 1
    CRC32: 0x3ED8C883 (OK)
GA▒06▒▒▒▒L▒▒ CUE▒▒+4>▒ȃ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒PuTTYGA▒06▒▒▒􈥯 CUE▒▒U4>▒$▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒PuTTY```

Hi @thep0et
Please provide the complete tsp command and, if possible, a partial TS file which reproduces the problem.
I am worried by the garbage which is displayed after the CR.

tsp -I ip {source}@{dest}:{port} -P filter -p 256 -P splicemonitor -a -s 256
This is the command that produced the above result.  I've tried various versions of this command with no luck.  It's always the first cue and then garbage after.  My current working theory is that, somehow, tsp isn't recognizing the package headers as SCTE-35 on subsequent ques, but I can't figure out why.
TS file containing a cue:
https://drive.google.com/file/d/1FLuJs1x38F-UQPfVA3sVoa8n4KIhb1xA/view?usp=sharing

tsp is a transport stream processor, it reads an input and writes to an output, both being defaulted to the standard input and output (to be used in pipes).
You do not specify any output plugin. Therefore, tsp write the binary transport packets to the standard output. The garbage you see on screen is the binary transport stream.
If you do not need the output TS, use -O drop, an output plugin which discards the TS.
Your stream has only one section. If your actual stream contains several SCTE-35 sections, -P splicemonitor -a will display them all.

Apologies.  I probably should have specified that this is just an excerpt of the full command that I'm using.
The full command already uses -O drop to drop the binary ts garbage, outputting as JSON before running it through some other text processing to clean it up before logging.
My issue is that, if I use -O drop, it drops every cue after the first one.  I removed the output so that I could see everything.
In the above capture, each time the word "cue" appears, I should have received another SCTE-35 cue, but it's coming across as more garbage.  The data is the same as if I didn't specify a PID

I should also note, that this is not an in-band stream that I'm monitoring.
These cues are being sent out-of-band for merging.  I'm not sure if that would make a difference.

My issue is that, if I use -O drop, it drops every cue after the first one. I removed the output so that I could see everything.

There is a misunderstanding on how tsp works. This is a chain of plugins. The intermediate plugins such as splicemonitor work exactly the same way regardless of the output plugin downstream. Conversely, the drop output plugin discards all packets at the end of the chain. In no circumstances, the drop output plugin can let one cue pass and drops the others. This is not the way tsp works.
Please provide a full TS file with several cues but for which you see only one.

I will have to capture one which may take some time.
In the meantime, I may have hit upon the issue.  The provider is not incrementing the Continuity Counter in the transport header.
Could this be causing an issue where tsp and/or the plugin is bundling the packets together?

The provider is not incrementing the Continuity Counter in the transport header.
Could this be causing an issue where tsp and/or the plugin is bundling the packets together?

Yes, this is definitely a bug from the provider, a huge bug. This is basic MPEG transport. Their system is simply broken and cannot work with MPEG-compliant receivers.
When the CC is not incremented in a PID, the ISO 13818-1 spec says that the packet is a duplicate of the previous one from the same PID. This is detected by the TSDuck demux and duplicated packets are ignored. Thus, indeed, only the first TS packet is analyzed. All other TS packets on the same PID are considered as duplicated and ignored.

This is exactly the smoking gun I've been looking for for weeks.  I really appreciate the feedback here, it definitely helped and gave me a deeper understanding of how tsp works.
Hopefully I can convince the provider to update their specs.

Hopefully I can convince the provider to update their specs.

Well, the spec is ISO 13818-1 / ITU H.222, this is the "MPEG Bible", the root of all Digital TV standards. If their product is not compliant with this, this is a bug, a huge bug and there is no one to "convince". They must fix it, full stop. Do not hesitate to direct them to this issue.


mvvm

Hi All, what would be the next logical step to implement bindings to my view models?

Bindings work the same, so it shouldn't be any different then what you do in WPF

I tried to bind a button content to a public static string property within another class. It worked in the WPF part of the sample provided but the index.html page didn't render :( JS stops rendering as soon as I add my namespace declaration, say xmlns:local="clr-namespace:SampleApplication" and set the window's DataContext to e.g.: local:MainViewModel

Did you do something like this?
<Button Content="{Binding Source={x:Static local:SomeClass.SomeProperty}}"/>
Unfortunately x:Static markup extension is not implemented yet.
A possible workaround could be to define a static resource
<local:SomeClass x:Key="SomeClassResource" />
and to bind like this
<Button Content="{Binding SomeProperty, Source={StaticResource SomeClassResource}}"/>

Hi yuvaltz. Unfortunately JS won't render if I declare a simple resource:
<Application x:Class="GranularApplication1.App"
                     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
                     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:system="clr-namespace:System;assembly=mscorlib"
                     StartupUri="/GranularApplication1;component/MainWindow.xaml">
    <Application.Resources>
<system:String x:Key="strKey">My String</system:String>
    </Application.Resources>
</Application>

I tried to recreate the above in the granularpad with no luck as it throws an error:
"clr-namespace:System;assembly=mscorlib:String" wasn't found

Could you please confirm if you can reproduce - thanks.

ok, that's an incompatibility, without the assembly=mscorlib part it works (try this example in GranularPad):
    <Grid xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
          xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
          xmlns:system="clr-namespace:System">
        <Grid.Resources>
            <ResourceDictionary>
                <system:String x:Key="myString">Hello</system:String>
            </ResourceDictionary>
        </Grid.Resources>
        <Button Content="{Binding Source={StaticResource myString}}" HorizontalAlignment="Center" VerticalAlignment="Center"/>
    </Grid>

I'll fix it, thanks!

Thanks, yuvaltz. The ultimate goal is to be able to render JS with the following xaml:
<Grid xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
          xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
          xmlns:granularApplication1="clr-namespace:GranularApplication1">
        <Grid.Resources>
            <ResourceDictionary>
                <granularApplication1:MainViewModel x:Key="myKey"/>
            </ResourceDictionary>
        </Grid.Resources>
        <Button Content="{Binding ButtonText, Source={StaticResource myKey}}" HorizontalAlignment="Center" VerticalAlignment="Center"/>
    </Grid>

The above doesn't work at the moment due to this line:
<granularApplication1:MainViewModel x:Key="myKey"/>

JS renders fine as soon as I comment the above line out.

I've just tested it and it seems to work, does it work in the "Wpf hosted" application?
Can you attach your solution so I could have a look?


cmon_exporter floods log with 'getting alarms for .. '

cmon_exporter floods log with 'getting alarms for .. '

fixed in 0.0.8


chore!: upgrade commander to12.1.0

Closes https://github.com/FuelLabs/fuels-ts/issues/2613

Breaking Changes:
This also removes necessity for the -p flag to be passed to the fuels cli.

Thanks for opening this @YaTut1901 , I've converted this to a draft PR. Feel free to re-open once the CI tests are passing.

Worth making the breaking change description a little bit more descriptive:

The shorthand flag (-p) for passing through a path to various fuels CLI commands has been deprecated. Migrate to using the --path flag instead.

do you mean description in PR?


Edit menu fixes

This primarily addresses #1207, stopping "Edit/Select All" from selecting hidden nodes. But it also adds to the GraphGadget API for improving the querying of visible node connections, fixes the "Edit/SelectConnected" menu items to ignore invisible nodes, and adds a bunch of extra useful connection selection items.

As a bonus, I've thrown in #941 (Ctrl+Click to move downstream nodes), since it was trivial following the addition of the new GraphGadget methods.


 Would be nice to upgrade 🙂

Thanks for the heads up! I'll try to do it in the next few weeks. I'm kind of maintaining two branches right now, which might slow down this upgrade, depending on how much is involved.

@tikue I am happy to support a bit here. Should I have a look onto the master branch?

You're more than welcome to have a go at it :)

I think I got most of the required changes on master.
You can have a look here: https://github.com/Urhengulas/tarpc/pull/1

@Urhengulas looks great! I eagerly await your PR ☺

@Urhengulas looks great! I eagerly await your PR ☺

Still need to adapt some tests, but else we should be good 😉

Edit: If you're interested in porting the tokio upgrade to my experimental branch, it's https://github.com/tikue/tarpc/tree/gats

@tikue I will just try to cherry-pick it over. Probably there isn't much more to do there.

@tikue Would it be possible that you publish a 0.22.1 version with tokio 0.3?

Done!

Done! Since it's a breaking change, it needed to be 0.23.

Thanks a lot :D


Development server not auto starting

I am trying to run the react native application through Xcode, however, the development server does not seem to get started automatically. I must always type npm start at the project root before running in Xcode. Where am I going wrong?

What version of xcode are you running?

I am running Xcode 7

Hi @pangers! That's unfortunate. Did you try rebooting your machine? And close any existing terminal window with the dev server running?

This could be a path issue somewhere. Is NPM installed properly? is it globally accessible?

@brentvatne Yep just restarted my machine, with no terminal windows open and I must still run npm start manually before building with Xcode.
@jaygarcia I seem to be able to type npm -v in any directory of my computer so I assume it is globally accesible

There's been also an issue regarding that but I can't find it. Are you running xcodeproj or xcworkspace with Pods? I am on XCode 7 and everything works properly. With Pods, it looks like you may need to copy one script that's responsible for packager to your build settings.
Please check if you have it under Build Phases -> Run Script.

I discovered the problem. One of the directories that the project folder was in had a space in its name. As soon as I removed the space, hitting command + R automatically ran the npm server!

Yes I had faced the same issue. It's because of space in the directory name
"The file /Users/konstantin/Desktop/Test One/TestMe/node_modules/react-native/React/One/TestMe/node_modules/react-native/packager/launchPackager.command does not exist.
Can't start packager automatically
"

May be add double quotes to this line https://github.com/facebook/react-native/blob/91e6c98ecdf5c9116bd894475ce3f3ed601fc5bc/React/React.xcodeproj/project.pbxproj#L576
"$SRCROOT/../packager/launchPackager.command"

+1


Trying to use db_engine.configure_database([User])

Trying to use db_engine.configure_database([User]) but as we need to await it, it cannot be directly run without any async function declared and called. Do you need to create a factory for this?
This is my code:
from config.settings import DB
from logger import logging
from odmantic import AIOEngine
from motor.motor_asyncio import AsyncIOMotorClient
from odmantic.session import AIOSession

from models.user import User

db_client = AsyncIOMotorClient(
    f"mongodb://{quote_plus(DB.user)}:{quote_plus(DB.pass_)}@{DB.host}:{DB.port}"
    if (DB.user and DB.pass_)
    else f"mongodb://{DB.host}:{DB.port}"
)
db_engine = AIOEngine(database=DB.name, client=db_client)

await db_engine.configure_database([User])

Managed to use it with below code:
loop = asyncio.get_event_loop()
if loop and loop.is_running():
    tsk = loop.create_task(db_engine.configure_database([User]))
    tsk.add_done_callback(
        lambda t: print(f"Task done with result={t.result()}  << return val of main()")
    )

But is this the correct approach or any other way is supposed to be used?


Fix not running FxCop on Tests

SonarQubeRunMSCodeAnalysis needs to be set in the categorize target or SonarQubeTestProject won't be set when it runs.

Thanks!

Thanks @jabbera. I've checked in a fix based on this with a couple of additional unit tests (https://github.com/SonarSource/sonar-msbuild-runner/commit/318a08fd9c17466aa495203db264f29531cc6e1f). Thanks for finding the issue and the fix.

I pulled your fix from: https://jira.codehaus.org/browse/SONARMSBRU-26?jql=project %3D SONARMSBRU
Works great. Thanks!

Thanks. Pity I didn't manage to fix it correctly first time ;-)

No worries! Happens to the best of us. The fix I was referring to which isn't merged yet was:
<SonarQubeExclude Condition='$(AssemblyName.EndsWith(".fakes", System.StringComparison.OrdinalIgnoreCase))'>true</SonarQubeExclude>

All the f projects were driving me bananas!


Added examples, improved docs, and changed style of std.traits.QualifierOf

Going to move forward with this.


Add ricardian contract and clauses

Add clauses to include in contract compilation

@leisterfrancisco
I still haven't gotten the contract to build the ABI with Ricardian clauses
eosio-cpp -abigen -R ./affiliate/ricardian -I ./affiliate/include -contract affiliate -o affiliate.wasm ./affiliate/src/affiliate.cpp
Am i missing something?

@leisterfrancisco
I still haven't gotten the contract to build the ABI with Ricardian clauses
eosio-cpp -abigen -R ./affiliate/ricardian -I ./affiliate/include -contract affiliate -o affiliate.wasm ./affiliate/src/affiliate.cpp
Am i missing something?

@xavier506 that is right, just one more thing, check that parent contract folder has affiliate name


Fix device wait in containers

Motivation for this change
It irks me that configuring the network inside the containers works different then outside of the containers. And all because inside the container there is no udev to tell systemd that a network device is already present. The most specific case where the problem bit me is when moving physical interface into the container. With this patch there is finally a way this can work without writing ip-commands by hand.
Based upon the idea from @bosu in #9836 I wrote tests and added code to make network configuration inside containers work the same as outside. There are also new tests for using physical interfaces inside the container, put the physical interface in a bridge, in a bond and in a bond which is put in a bridge.
Things done

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

[ ] NixOS
[ ] OS X
[x] Linux

[x] Fits CONTRIBUTING.md.

LGTM, but needs a rebase to resolve the conflicts. Maybe you could squash a few of the commits?

@fpletz thanks for the review. rebased and a bit of squashing. Also ordered the tests in subtests, was on my todo for this.

Does the container tests are working all properly for you?

@Mic92 Thanks for the catch! the extraVeth test is failing in this PR, but also on last nixos-unstable-small. so there is #19391.
Apart from that, the container tests work here.

Thanks!

This breaks evaluation of nixos tests; I verified by reverting the merge locally. Test case:
$ nix-build nixos/release.nix -A tests.networking.scripted.sit.x86_64-linux --dry-run

@vcunat not within this feature branch (on ubuntu14). But on master. interesting…
see #19464 for a fix.
Gotta set up my own hydra and have it run all release tests on my feature branches…

I currently sit in a train, where I cannot download the test dependencies,
but does the current patch fix the problem?
diff --git a/nixos/modules/tasks/network-interfaces-scripted.nix b/nixos/modules/tasks/network-interfaces-scripted.nix
index 89ee13d..a44a73b 100644
--- a/nixos/modules/tasks/network-interfaces-scripted.nix
+++ b/nixos/modules/tasks/network-interfaces-scripted.nix
@@ -333,7 +333,7 @@ in

         createSitDevice = n: v: nameValuePair "${n}-netdev"
           (let
-            deps = optional (v.dev != null) (deviceDependency v.dev);
+            deps = (optionals (v.dev != null) (deviceDependency v.dev));
           in
           { description = "6-to-4 Tunnel Interface ${n}";
             wantedBy = [ "network-setup.service" (subsystemDevice n) ];

The new systemd-nspawn module still uses the deprecated optionSet function, but this is a different issue.

@Mic92 Yes, I'm afraid that code was written before the deprecation. I can look into it, but I won't have time for it too soon :wink:

The patch certainly fixes evaluation of that particular test.


ApiDataProvider downloading non existent data

Expected Behavior

When using ApiDataProvider it will only download data for valid days and for files that actually exist
Actual Behavior

ApiDataDownloader will download non-existent data and create a zip for it causing issues with Lean reading the data later.
Example 1 SPY Second Data:

For 2008 1/23 & 2/14 there is no data that exists in the web data repository, yet Lean creates files for them and they are both corrupted. Later when Lean goes to read this in a backtest it throws an error.
Example 2 ARQL Minute Data:

After 2020 1/15 ARQL is delisted, yet the ApiDataProvider attempts to download past this point and creates a bunch of corrupted files.
Potential Solution

Source of the problem is not yet definitive so I do not yet have a potential solution.
Reproducing the Problem

Try either of the examples above by:

Get the data on your QuantConnect account
Use ApiDataProvider in config; also include your Api UserID and Key.
Run an Algorithm that would download data for either equity in the example range.

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Think this one is a duplicate of https://github.com/QuantConnect/Lean/issues/4556 ?

Whoops, yup! I'll close this guy out.


Missing Documentation for Database Configuration

Issue
The project lacks documentation for database connection configuration in local environments.
Details
The following database configuration details should be added to README.md or the Get Started guide:

Database: drupal
Username: drupal
Password: drupal
Host: database

Proposed Solution
Update README.md or the Get Started guide with this information to help developers set up their local environments more easily.

I have updated the README.md file to include the necessary database configuration details for setting up local environments, as well as the documentation at dresktop.com.
Thank you very much for the feedback!


Re-export Cow from prelude

Rendered

@rfcbot concern potential-cheese-extension
It occurs to me that eventually we may want to extend 🐄 to support 🥛, 🧀, and eventually 🍕. These are all delicious and it feels reasonable to assume that the community will feel a need for such delectable goods.
Is it possible to future-proof this RFC for these designs?
Furthermore, do we need to resolve whether 🍕 would be compatible with 🍍? It feels like this will be an issue down the road.
I'm reluctant to expand the scope of this RFC so broadly, however, I'd like us to get this right with a holistic design so we don't paint ourselves into a corner in the future.

I'd like to also bring up the fact that we might actually want to implement a Cow trait here instead since many things can derive from it. While @Manishearth has brought up the fact that we might have 🥛, 🧀, and 🍕 we're also excluding a whole list of Cow derived items such as 🍦, 🎂, 🍨, and 🥞 to name a few.

Wouldn't it be better to experiment with this out-of-tree first? Of course the obvious crate name for such an experiment would be "🐄", so crates.io will need to be taught to support Unicode crate names, too. But presumably that's pretty high on the roadmap anyway, so we could use this as an excuse to finally get that done.

This feels like a dangerous step in the direction of emojicode, and I hope the core team will think long and hard before opening this COW (container on wheels).

Can we also export Box with 📦?

I was fooled.

In the 2019 roadmap RFC we said that we would work to achieve:

Key ergonomic improvements

By reexporting 🐄 to the prelude, this clearly happens. As such, let's @rfcbot merge !
However...

Cow::Borrowed would be exported as U+262D HAMMER AND SICKLE, ☭. This is because ownership is theft. No further explanation is required.

This does not feel very readable. Can we use Ⓐ instead?

This does not feel very readable. Can we use Ⓐ instead?

I feel like that should be reserved as a replacement for unsafe though.

I feel like that should be reserved as a replacement for unsafe though.

If we start reserving Unicode identifiers,I think ☢ would be better for marking unsafe code.

As such, let's @rfcbot merge !

It feels like @rfcbot has a bug or something... let's try this again.
@rfcbot merge

If we start reserving Unicode identifiers,I think ☢ would be better for marking unsafe code.

This could be confused as the replacement of std::atomic though, which is pretty safe and efficient.

This could be confused as the replacement of std::atomic though, which is pretty safe and efficient.

There's always ☠ { ... }.
Feels pretty clear.

@rfcbot concern potential-cheese-extension
https://github.com/rust-lang/rfcs/pull/2672#issuecomment-478402150

@rfcbot concern potential-cheese-extension
on behalf of @Manishearth.

Cow::Borrowed would be exported as U+262D HAMMER AND SICKLE, ☭. This is because ownership is theft. No further explanation is required.

This would mean the end of my Rust career and possibly for other people coming from the former Eastern Bloc countries. Law here prohibits the public use and display of symbols of totalitarianism including all communist symbols like red stars, hammer and sickles. If this change goes through I could be punished by custodial arrest just by writing Rust code and publishing it on my public GitHub profile.

Now that it is April the 2nd and the horror of the day that was prior to this relief has subsided, I would like to comment that I actually kinda like the idea of exporting Cow. There are no portability concerns as prelude names are shadowed if another Cow is imported or defined in the scope.

@rfcbot concern no-chance-to-have-this-considered-seriously??!

@xTibor

This would mean the end of my Rust career and possibly for other people coming from the former Eastern Bloc countries. Law here [1] prohibits the public use and display of symbols of totalitarianism including all communist symbols like red stars, hammer and sickles. If this change goes through I could be punished by custodial arrest just by writing Rust code and publishing it on my public GitHub profile.

If it wasn't clear, this whole thread is heavily in jest and we certainly would not use a symbol like that for anything real. That said, it is perhaps worthwhile to remind folks that we're striving to be an inclusive community and want to be thoughtful about the jokes we make, especially around politics and issues with significant historical baggage.

If it wasn't clear...

It was perfectly clear for me, it's just an overdramatized shitpost :)

@nagisa I'd like to see Cow in the prelude as well (under the name Cow). (I don't think we need to re-export the constructors directly, unlike Some; it seems fine and even preferable to write Cow::Borrowed.)
I don't think re-using this thread is a good idea. Would someone like to supply a serious RFC for the re-exporting of Cow from the prelude?

Yeah, I can draft a serious RFC later this week. As it's now April 2 in UTC, I'm going to shut this one down. Thanks for the fun day folks!

@nagisa @joshtriplett @sgrif Perhaps an RFC on the prelude policy?  Right now it seems to be "almost nothing", but I don't know if that's been formalized.  Individual additions might be possible as just PRs if there was a clearer way to make the decision...

(Please take the discussion elsewhere, this RFC is locked)


gtk: more manual stuff 4

Pretty small one

FileChooser::add_choice
PrintSettings::set_page_ranges
EntryBuffer::inserted-text
EntryBuffer::deleted-text

As much as i would like to get this one in before the release. I will definitely not have the time to finish it. So worth moving it to the next milestone

You could also get it into 0.1.1 or so :) It's new API, not something requiring API changes.


for full numpy compatibility: vectorized functions

Thanks for a great plugin! This is very useful.
For ultimate smoothness with the numpy philosphy, it would be great if the fd* functions would operate elementwise over the input arrays including broadcasting, much in the way of functions in the scipy.special module.
For example, this passes a column 2-vector and row 2-vector to the order-n Bessel function, resulting in a matrix of J_5(1), J_5(2), J_6(1), J_6(2)::
>>> from scipy.special import jn
>>> jn(array([[5],[6]]),array([1,2]))
array([[  2.49757730e-04,   7.03962976e-03],
       [  2.09383380e-05,   1.20242897e-03]])

Currently, this is not directly implemented for the fdint functions, however it can be done by wrapping them with numpy's "vectorize" class.
>>> fdk_vec = numpy.vectorize(fdint.fdk)
>>> fdk_vec(array([[5],[6]]),array([1,2]))
array([[<PHONE_NUMBER>8,<PHONE_NUMBER>9],
       [ 1920.6214911 ,  5088.14241086]])

This is unfortunately a bit inefficient in that it essentially performs a for loop in python, rather than a for loop in C.

Thanks for the issue submission, I'm glad you find the package useful!
It would definitely be good more closely match scipy's standards, especially if it can be done without reducing performance, or if performance can be maintained by calling a separate function.
I'm no longer actively using this package, so I can't guarantee a speedy followthrough, but I would be happy to accept a pull request if you (or anyone) would like to take it on themselves

Totally understandable, for now I'll use the vectorize wrapper but if I see performance issues you may see a pull request from my end.
By the way, another thought: in case you don't plan on maintaining the package long-term, it might make sense to integrate it into scipy.special, which lacks F-D integrals and the related polylogarithm. You certainly seem to have implemented a very fast code and I think many python users may be unaware that your package exists. If you're supportive of this idea I can get a feature request going and maybe even implement it myself (would be a good excuse to learn the innards of C+Python+cython). Cheers-

Sounds great on both counts. I'm happy to support your efforts in any way I can.


Nullable arrays

Closes #295

Thank you for working on this!

Thank you for working on this!

No problem. It was an easy fix...once I re-learned all the abstractions. Thanks for the report and PRs


Create a Solr Source Kamelet

It will always use the producer side, but it will be repeat the same query. We could eventually doing something like this, as a consumer directly in component.

Would you happen to have some example? I tried a lot to setup a sink and source connector with Kafka but I still Im struggled with them.

The kamelets related to Solr have been removed. What connector are you using? Camel-kafka-connector? What version? What have you tried?

I have the next set of containers:
3 Kafka brokers
Kafka Connect
schema registry
UI for Apache Kafka
I'm trying to load some data from documents using jcustenborder's spooldir connectors from a fileserver to a kafka topic. Then I want to index topic messages to Druid or Solr. With Apache Kafka druid supervisors API this process was realized. To solr I'm trying to use apache camel kafka sink connector to send data. I configure my topics with the next parameters.
{     "connector.class":"org.apache.camel.kafkaconnector.solrsink.CamelSolrsinkSinkConnector",      "topics":'indexedTopic',     "value.converter.schemas.enable":false,     "camel.kamelet.solr-sink.collection":"test_collection",     "camel.kamelet.solr-sink.servers":"<IP_ADDRESS>:18085",       }
My messages has been stored with the next structure

{ 	"schema": { 		"type": "struct", 		"fields": [ 			{ 				"type": "string", 				"optional": true, 				"field": "LicenseType" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "Breed" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "Color" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "DogName" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "OwnerZip" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "ExpYear" 			}, 			{ 				"type": "string", 				"optional": true, 				"field": "ValidDate" 			} 		], 		"optional": false, 		"name": "com.github.jcustenborder.kafka.connect.model.Value" 	}, 	"payload": { 		"LicenseType": "Dog Individual Spayed Female", 		"Breed": "BICHON FRISE", 		"Color": "WHITE", 		"DogName": "CHLOE", 		"OwnerZip": "15090", 		"ExpYear": "2017", 		"ValidDate": "12/15/2016 9:58" 	} }

I have got error related to data parsing and in the best case Camel connector tried to send data to Solr however it tried to make an atomic update and Solr generated a parsing error. I think that it is related to the nesting in the message data.
my came kafka connect component version is 3.21, my kafka connect image is confluentinc/cp-kafka-connect-base:6.1.0 and my kafka brokers use the latest image (I think that is 7.5.1).


add style for form

📝 Description
I have added some style to the form on the contact site.

[x] I have performed a self-review of my own code.
[x] I'm a contributor in Hacktoberfest'21.


Avoid shutdown threads even if the scheduled jobs are failed.

Resolve #53

Codecov Report

Merging #56 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
- Coverage    90.5%   90.49%   -0.01%
==========================================
  Files          57       57
  Lines        1285     1284       -1
  Branches      105      105
==========================================
- Hits         1163     1162       -1
  Misses        115      115
  Partials        7        7

Impacted Files
Coverage Δ

...der/common/ScheduledExecutorServiceExtension.scala
100% <ø> (ø)
: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 67ac720...80eeb3c. Read the comment docs.


AppStore Distribution signed app does not send crashes

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.3.1
Firebase SDK version:  Firebase/Crashlytics (6.15.0):
Firebase Component: Crashlytics
Component version: 4.0.0-beta.4
Installation method: CocoaPods (select one)

[REQUIRED] Step 2: Describe the problem
We've identified, that after signing the app with AppStore certificate, Firebase Crashlytics stops working. The problem does not occur while signing the app with AdHoc certificate. We are using Apple Distribution Certificate.
The errors we've found in the console:
<Forced crash, re-ran the app>
[Firebase/Crashlytics] Version 4.0.0-beta.4
..
[Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist
[Firebase/Crashlytics][I-CLS000000] Crash reporting could not be initialized
[Firebase/InstanceID][I-IID003014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 "The file “embedded.mobileprovision” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/private/var/containers/Bundle/Application/71738F66-30A3-4D4E-A60E-85F7FB3614AC/X.app/embedded.mobileprovision, NSUnderlyingError=0x282bc5b00 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
I've unzipped the ipa file and:

there is Info.plist, it contains bundle identifier
there is mobileprovision file, looks good.

The app would not even run without files above, so these errors seems like incorrect ones.
Steps to reproduce:

Build the app with AdHoc profile, force a crash - works fine. Crashes are sent to Crashlytics.
Build the app with AppStore profile, distribute via testflight.
Install it from TestFlight, run, force a crash
Re-open the app. Crash should be sent- it is not. Check out logs:
Errors from Step 2 are visible.

Crashlytics, I'm also experiencing same problem. This is sending me the crash report in debug mode, but when I use signing the build and push to TestFlight it is not sending me the report.

Same here 👎

We also have the same problem

Also, seeing the same issue with an app not using CocoaPods installation.

I have tried with both pods and with static framework linking using 6.18.0

For others with the same issue, are you seeing the same log from Crashlytics and InstanceID? Eg:
[Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist
...
[Firebase/InstanceID][I-IID003014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 "The file “embedded.mobileprovision” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/private/var/containers/Bundle/Application/71738F66-30A3-4D4E-A60E-85F7FB3614AC/X.app/embedded.mobileprovision, NSUnderlyingError=0x282bc5b00 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

If this is happening with both Firebase 6.15.0 and 6.18.0, it seems unlikely a code change caused this to happen, since many apps have successfully released to the App Store in that timeframe with Crashlytics. I'm trying to figure out what could have changed with Apple's signing that would cause this. It seems like files in general can't be opened from Crashlytics and InstanceID.

Are there other errors in the logs that indicate an issue with opening files?
Does anyone's app successfully read from the bundle identifier, but see Crashlytics fail to?

@samedson we are using [[NSBundle mainBundle] bundleIdentifier] in our app, and the method seems like working fine. Only Crashlytics has difficulties with accessing this identifier.

@samedson

Are there other errors in the logs that indicate an issue with opening files?

Haven't found any additional errors.

Does anyone's app successfully read from the bundle identifier, but see Crashlytics fail to?

We are reading other files like translations of third party SDK's, so access is working fine. Also  getting [[NSBundle mainBundle] bundleIdentifier] works as expected.

Want to ask a few more questions. I still haven't determined the root cause of the issue - wondering if maybe something changed with the timing of calling [NSBundle mainBundle] in iOS.

How are you initializing Firebase? Is it with a call to [FIRApp configure] in the App Delegate?
Was there some point where Crashlytics stopped working in new versions of your app, or is this the first time you've tried to ship with Crashlytics?

How are you initializing Firebase? Is it with a call to [FIRApp configure] in the App Delegate?

Yes

Was there some point where Crashlytics stopped working in new versions of your app, or is this the first time you've tried to ship with Crashlytics?

A new app under development but on TestFlight.

What is your CocoaPods configuration?

Not using CocoaPods.

@samedson

How are you initializing Firebase? Is it with a call to [FIRApp configure] in the App Delegate?
FirebaseApp.configure() in App Delegate
Was there some point where Crashlytics stopped working in new versions of your app, or is this the first time you've tried to ship with Crashlytics?
We've just tried to migrate from Fabric SDK to Firebase SDK. There were no issues with Fabric SDK, so we've migrated back. Today I've received an email from Google that Fabric services will be held up and running until early May.
What is your CocoaPods configuration?

  pod 'Firebase/Core'
  pod 'Firebase/Messaging'
  pod 'Firebase/RemoteConfig'
  pod 'Firebase/Crashlytics'
  pod 'Firebase/Analytics'

Seems like that issue is connected to this one (also problems with bundle context):
https://github.com/firebase/firebase-ios-sdk/issues/5092

Apologies, but I'm unable to reproduce the issue. Could you provide a project that reproduces the issue (if I build it for App Store distribution)?

From https://github.com/firebase/firebase-ios-sdk/issues/5092, can you try setting FirebaseAppDelegateProxyEnabled to NO in your Info.plist and see if that resolves the issue?

I'm getting exactly the same error:
6.21.0 - [Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist
6.21.0 - [Firebase/Crashlytics][I-CLS000000] Crash reporting could not be initialized
6.21.0 - [Firebase/InstanceID][I-IID003014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 "The file “embedded.mobileprovision” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/private/var/containers/Bundle/Application/6AB4F02F-538A-4D3D-A29F-99FB98CE2532/Aion.app/embedded.mobileprovision, NSUnderlyingError=0x281964090 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

I'm getting exactly the same error:
6.21.0 - [Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist
6.21.0 - [Firebase/Crashlytics][I-CLS000000] Crash reporting could not be initialized
6.21.0 - [Firebase/InstanceID][I-IID003014] Error while reading embedded mobileprovision Error Domain=NSCocoaErrorDomain Code=260 "The file “embedded.mobileprovision” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/private/var/containers/Bundle/Application/6AB4F02F-538A-4D3D-A29F-99FB98CE2532/XXX.app/embedded.mobileprovision, NSUnderlyingError=0x281964090 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}

@Hans92 from https://github.com/firebase/firebase-ios-sdk/issues/5092, have you tried setting FirebaseAppDelegateProxyEnabled to NO in your Info.plist and manually implement the delegate methods, to see if that resolves the issue?

FirebaseAppDelegateProxyEnabled is set to NO. I thought that it could be caused by different Info.plistfilename, but nope, it's not that.
How can I debug this and help you find the issue?

Seeing the same issue with Firebase/Crashlytics 6.22.0.

Some ways folks can help cc @Hans92:

Posting an Xcode project that reproduces the issue. You can also reach out to support and send via that channel.
Before and after Firebase Initialization, printing the bundlepath in a project that reproduces the issue
Trying out other configurations or code setups to see if the issue can be resolved

Questions still remaining:

@pmfon (and others) when you build in Release, but don't ship to TestFlight / App Store, do you see the same logs, An application must have a valid bundle identifier in its Info.plist? You can do this by going to "Edit Scheme" and updating the Run "Build Configuration" to "Release" or "App Store"?
Do folks here have an AppDelegate (or other shared app code) that gets pulled in via a framework by chance? This issue seemed to indicate there were problems with that: https://github.com/firebase/firebase-ios-sdk/issues/5092

Notes thus far:

I've tried reproducing this with an app using Cocoapods and Xcode 11.3.1, but did not reproduce the issue.
Firebase versions affected: 6.15.0, 6.18.0, 6.22.0
Seems that this is an issue regardless of whether Cocoapods or the manually-installed frameworks are used
This code has been in Crashlytics for years (even the Fabric version pre 4.0.0-beta.1 release). At this time I don't believe a change in Crashlytics caused this issue, but it's possible there is code in FirebaseCore or another dependency that is causing this. I don't believe removing the check for bundle ID will resolve this as Crashlytics uses the bundle ID for many other things.

Digging into the code, here's where this check is:

https://github.com/firebase/firebase-ios-sdk/blob/master/Crashlytics/Crashlytics/Controllers/FIRCLSReportManager.m#L526
https://github.com/firebase/firebase-ios-sdk/blob/master/Crashlytics/Crashlytics/Settings/Models/FIRCLSApplicationIdentifierModel.m#L49
https://github.com/firebase/firebase-ios-sdk/blob/master/Crashlytics/Crashlytics/Components/FIRCLSApplication.m#L28
Which just boils down to a call to [[NSBundle mainBundle] bundleIdentifier].
kondratk's comment https://github.com/firebase/firebase-ios-sdk/issues/5020#issuecomment-597545319 indicates that calling [[NSBundle mainBundle] bundleIdentifier] in their app works, just not Crashlytics' call

One solution to "The file “embedded.mobileprovision” couldn’t be opened because there is no such file at https://stackoverflow.com/a/43473088/556617

@samedson
I think it fails at an earlier point. The FIRCLSApplicationIdentifierModel initialiser might return nil. That would cause the An application must have a valid bundle identifier in its Info.plist message.
We were able to reproduce this in the simulator with a release configuration.

@samedson
I think it fails at an earlier point. The FIRCLSApplicationIdentifierModel initialiser might return nil. That would cause the An application must have a valid bundle identifier in its Info.plist message.
We were able to reproduce this in the simulator with a release configuration.

A bit more detail, the dlsym call here is returning NULL
https://github.com/firebase/firebase-ios-sdk/blob/3dc11858ff5bfc8e40bde33dd3fe16b04d215a9a/Crashlytics/Shared/FIRCLSMachO/FIRCLSMachO.m#L258

Great find @pmfon - now to figure out why this will fail in App Store signed apps. Going to do some research

Great find @pmfon - now to figure out why this will fail in App Store signed apps. Going to do some research

Here’s what we found so far

the difference seems to be between debug and release versions (not necessarily signed, since it can be reproduced in the simulator)
disabled striping in the release build and the symbol still can’t be found though it’s in the binary if you check with ‘nm’
only changed the main project settings, the Pods configs were not touched
calling dlsym from the AppDelegate has the same effect
the legacy SDK (integrated with CocoaPods), with the same project configuration, works

Huh I still can't get it to happen on my end - I'm running in "Release" configuration in my Scheme, and have stripping on, but it doesn't reproduce the issue. Hoping to narrow it down to a few settings.
Would you be able to export the build settings that reproduce this (removing any PII - I see bundle IDs and paths in there)?
cd <your-project-directory>
xcodebuild -scheme "<your-app-scheme>" -showBuildSettings

What about the configuration name? I don't use default Debug and Release names but Debug, Release-AppStore and Release-AdHoc.

Right now the main thing that will help me debug this is an xcode project that reproduces the issue.
I don't feel confident in shipping a fix without being able to reproduce the issue because that dlsym call that's returning NULL is important for the Crashlytics SDK to function - skipping the call or some other workaround will cause other negative side effects.
I did try out duplicating the Release configuration with a new name, but did not reproduce the issue.

@samedson
Found it. The project sets Exported Symbols File in Release builds. This file is empty.

That seems to be the problem @pmfon. Reproduced it locally!
Can you try adding __mh_execute_header as a new line to your Exported Symbols File? That fixes the issue in the quickstart.

Gonna close this for now - but feel free to reopen if the following fix doesn't work for you. I've added logging in the SDK to give a clearer error message when this happens.
Fix
For those running into this issue, the fix is:

Find the "Exported Symbols File" setting in your Xcode Build Settings
Open the file that's set for that
Add __mh_execute_header as a newline to that file

@samedson what if I don't have anything in Exported Symbols File and this field is blank?

@Hans92 from what I understand that means your build process is not exporting a symbols file. You should set a filepath in the field in Xcode, and Xcode will generate an exported symbols file there when you build your app.

A newly created project with Xcode 11.3.1 has nothing in Exported Symbols File. Should I create this file somewhere?

This doesn't make any sense.
I have several projects that uses Firebase. Only two are affected by this problem, but none of the projects use an Exported Symbols File.
I've created a new project that's effectively an empty app with Firebase SDK integrated, with no Exported Symbols File set and it's reporting crashes just fine.

Let me clarify:

Crashlytics does not require the Exported Symbols File build setting. Your app will work without it. But if you do set that build setting (for some other reason), you must add __mh_execute_header to the file.
The current understanding is this GitHub issue only impacts apps that have set Exported Symbols File, and do not add __mh_execute_header to it.
If you're finding that your app is impacted by this issue, as indicated by the following log, we need to investigate further and see if there are other build settings that could be causing it.

[Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist

The project related to this issue has nothing in the ‘Exported Symbols File’

Unfortunately, the issue still exists. The same as @Hans92 I don’t use exported symbols file.

@kondratk and @Hans92 are you seeing
[Firebase/Crashlytics][I-CLS000000] An application must have a valid bundle identifier in its Info.plist

in your app's logs? We're currently experiencing a delay in crash processing which may be causing crashes to not appear in console that's unrelated to this issue.
Googlers see outage number 19770

@kondratk @Hans92 the issue could be caused by another build setting or flag which strips that symbol from the binary, such as 'fvisibility' or 'Symbols hidden by default' (or even a run-script phase from another framework). Note that I've never found the 'embedded.mobileprovision' error in my logs.

Symbols hidden by default has a default value in my project.


Add more compilation flags

I think that compile flags for exercises should contain at least '-Wall', maybe '-Wextra' and '-Wpedantic' and even '-Werror'. That would provide students with better diagnostics from the compiler and avoid common mistakes.

I agree with this. It's what we've done on the C track as well. This is the list we use there:
CFLAGS += -g
CFLAGS += -Wall
CFLAGS += -Wextra
CFLAGS += -pedantic
CFLAGS += -Werror

@AlexLeSang would you like to make the change? It should be a change to this line that needs to be changed in every CMakeLists.txt file in the exercises folder.

Do you find -Werror to be a useful teaching tool? Personally I feel that it tends to disrupt one's workflow and it can be frustrating to be at the mercy of a pedantic compiler.
Having said that, it may be more important to force students to resolve all issues. Warnings are easy to ignore, especially if you don't clean the project.

I have no strong opinions on using -Werror here, it's useful for me (usually), and there are not many false positives with just all/extra/pedantic enabled. Generally those flags only pop up things that really should be fixed, or that actually are bugs int he code.
I admittedly don't teach enough to know if it's helpful for beginners, so I am totally open to other opinions.

Thinking over this again, I wonder if I'm projecting my experience with C warnings on to C++. I'm happy to defer to others.
@AlexLeSang are you excited to add this? If so, by all means. If not, I might give it a go myself - I should have time this weekend.

Yes, I am very excited to do this and I will do it this weekend.
In my experience working with less experienced colleagues, it is always better to promote a warning  to an error and pedantic compiler can teach a lot.

@AlexLeSang For sure. Enjoy!

These are now supported in the cmake files. Thanks!


Command Palette input cursor movements don't match character widths

What
In the command palette, characters take varying amounts of space when entered. The input cursors, however, does not always move according to their widths. This is demonstrated in the video.

Comments
The command-palette likely doesn't use mono-space fonts like the editing pane. The cursor may just be configured to move by a fixed unit whenever a character is entered. A solution here may also resolve #687

I believe this is being worked on over in revery-ui/revery#550.

FYI, I'll probably address this in the menu renovation project

This was fixed in #1231 - thanks @fanantoxa !


server: handle heartbeat of the region with peers change

What have you changed? (required)

After TiKV unsafe recover some regions, the region epoch not changed but the peers number have changed, we should update it.
What are the type of the changes (required)?

Bug fix

How has this PR been tested (required)?

Unit tests

LGTM.


Get the value of the additional checkbox?

Hi!
I can't figure out how to get the value of the additional checkbox?
The checkbox is shown just fine if I add a value in the Commerce Manager settings but how do I retrieve it?
In your v2 version you had this:
`public bool IsNewsletterChecked(string orderId)
{
if (orderId == null) throw new ArgumentNullException("orderId");
        var order = FetchOrder(orderId);
        var request = order.GetValue("merchant_requested") as JObject;
        if (request != null)
        {
            return request["additional_checkbox"].ToObject<bool>();
        }
        return false;
    }

`
Maybe I'm just missing something here?
Thanks!
/Kristoffer

I think I found some documentation:
https://developers.klarna.com/api/#checkout-api__order__merchant_requested
I'm happy to fix this but I'm not sure how to use the information. Could someone please guide me?
"merchant_requested": {         "additional_checkbox": false,         "additional_checkboxes": [             {                 "id": "string",                 "checked": false             }         ]     },
Thanks!

In KCO v3 we are using Klarna's library and it doesn't have this feature. Here is what they have:
https://github.com/klarna/kco_rest_dotnet/blob/v2.2/Klarna.Rest/Klarna.Rest/Models/CheckoutOrderData.cs

Now that is strange!
The have settings for adding a checkbox but no way of retrieving the data?!
Do you have any technical contact at Klarna that you use or is it just the normal technical support that you use?
Thanks again!
Skickat från min iPhone
29 aug. 2018 kl. 16:21 skrev Māris Krivtežs <notifications<EMAIL_ADDRESS>In KCO v3 we are using Klarna's library and it doesn't have this feature. Here is what they have:
https://github.com/klarna/kco_rest_dotnet/blob/v2.2/Klarna.Rest/Klarna.Rest/Models/CheckoutOrderData.cs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Geta/Klarna/issues/39#issuecomment-416971281, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQKH8mgO9s0tpcNtT4UMKb5FcOG5XTywks5uVqN5gaJpZM4WNajF.

I have created an issue on Klarna repo.

@mbooh @marisks - Unfortunately Klarna has not been updating the SDK's.  Klarna is reviewing the SDK's and the SDK's will likely be redone (but it will be a new SDK, not an update of these current SDK's).  We don't have committed timelines for the new SDK's at this time.
Unfortunately the best approach is likely for you to directly update your own local SDK copy if necessary to allow retrieving the additional checkbox data.

Perfect, thanks!
Skickat från min iPhone
29 aug. 2018 kl. 16:39 skrev Māris Krivtežs <notifications<EMAIL_ADDRESS>I have created an issue on Klarna repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Geta/Klarna/issues/39#issuecomment-416977551, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQKH8skKak5yFFPJzgCce2KvWxA48q5Aks5uVqeJgaJpZM4WNajF.

Thanks for the update @mbooh - glad you're able to make progress!  I don't believe that the PR will be processed directly as the Klarna team is looking to generate Klarna SDK's with a new process going forward.

Closing because of age.

Closing because of age.


bots: Fix "help" message async in yoda.py and test_yoda.py.

The help message string was modified in yoda.py file to correctly
instruct the user. But the help message string was not modified
accordingly in the test file.

Nice, merged, thanks @abhijeetkaur!


Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method

When running the dgl on multi-gpu, the code (example/dgl/multi_gpu/train_gcn.py) you provide raise an error as the title. Is the version or some other issues? Thanks!

Can you describe in detail how you build the environment and deploy GNNLab?

Thanks to your reply! Yes. I don't use the docker and perform the installation as the README.md on 3090Ti GPU. The software versions in my enviroment are as follows:

CUDA v11.3
DGL v1.0.0
fastgraph v0.2.0
Python v3.7
PyTorch v1.10.1

Did you change the code of GNNLab? I guess you may modify some lines of code to run in 3090. If changes the code, you should make sure no CUDA functions are called before the fork.
And if you give us your original error logs information, it will be more helpful to address this problem.

yeah, I modify smoe lines and I have fixed this bug by use the torch.multiprocessing instead of dgl.multiprocessing, thanks!

Good to know. I'll close this issue as it's solved. You may reopen it if you encounter any further problem.


update packages

:white_check_mark: Build TheIdServer 4.2.1-fix-dependencies1-0172 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/e38576959e by @)


Losing items on death, expected or not?

Not sure if a bug or expected feature but my son and I have lost an item or two when grabbing our items from grave after death, in comparison to the inventories we had before death.    Hard to track what other items may or may not go missing, but usually feels like we got most of our stuff back from the grave but missing a sword and maybe one other thing.  Thought maybe it was a set penalty for death but didn't see a config for that only for XP.  (Un)fortunately I haven't died in a bit but my son is reporting he is still losing an item or two.
So just wondering if we lose our hand held items at death or is this expected?  No trinkets items being used.
Expected behavior
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):

OS: Windows and MacOS clients, linux self-hosted local server.
Minecraft Version: 1.18
Version: 1.1.11

No this is not a feature of the mod. It's a bug. I've had this bug happen to me in my testing and I though I fixed it, but I guess not. I'll be trying to fix this issue within the next few hours. Also if you do find something that should be configurable within the mod, please make a feature request for that. Won't add this as a config however, since as you say it's not exactly easy to track which item it is. (I will if you specificly request it though)
I'll reply here again as soon as it's fixed. Thanks for reporting the bug!

UPDATE: This issue was apparently harder than I thought to replicate. Which version are you playing? You've stated that you play one of the 1.17 versions (1.1.11) in 1.18. The latest 1.18 release is 1.2.5. Please make sure your server mod version is also up to date. In my testing I've tried multiple ways of dying with various inventory layouts and nothing has disappeared. If this is not just because it's an old version, if possible, please try and recreate your sons inventory before he died, and when the inventory equipped before retrieving the grave. If this is not due to an old version, I need screenshots of the conditions of this issue taking place. I'm sorry you're have this issue. I'll try to the best of my abilities to help you

LOL it was 1.2.4 version when I wrote the bug report I quickly checked your last release version prior to the update on your tags here.  It was like 2AM for me.  Verified now I was on 1.2.4  I have updated client and server now to 1.2.5 and I will ask my son and daughter to try and keep track if we lose anything next death.  I try not to die but my son literally kamikazes himself.
Thanks for your reply I have used a few death mods in the past but liked yours for your desire to have a complete full config and options.

Died a couple times now and not seeing the same loss of items.  Not sure if something with 1.2.5 fixed it or some other thing happened but working okay now.  Thank you for following up and sorry for the trouble.


Enable Subscription Manager in NATS Mode

Description
The current implementation of a reconciler for Eventing-CRs checks that all infrastructure for Eventing in NATS mode is set up correctly. With this ticket we need to enable reconciling Subscriptions in NATS mode. As this logic already exists in the current implementation in eventing-controller. The way to migrate the existing logic into the new reconciler is by importing the package of the eventing-controller and reuse it.
Note
The existing logic is imported as a package to avoid code duplication so long as there is still work to be done on the eventing-controller. This ticket is only about starting subscription manager.
Acceptance Criteria:

[ ] reconcile kyma subscription and create nats-infrastructure (stream, consumers, dispatcher)
[ ] existing unit and integration tests should continue to pass as before
[ ] apply the configuration from the eventing CR as defined in the proposal

[ ] Check deletion of CR and recreation.
[ ] Make target to copy subscription and application CRs.
[ ] Test on a vanilla cluster again.


Replace setuptools with scikit-build

It would be interesting to replace setuptools, since the SIMD support from https://github.com/maxbachmann/RapidFuzz/issues/127 would require us to compile parts of the projects with different compiler flags. This would be a lot simpler to implement in CMake. I tried to switch to scikit-build in https://github.com/maxbachmann/RapidFuzz/pull/153. However I did run into issues with PyPy and Python2.7, which I could not resolve. From https://github.com/scikit-build/scikit-build/issues/506 it appears, that PyPy is not really supported well at this point.

FYI, https://iscinumpy.gitlab.io/post/scikit-build-proposal - it's planned (but might depend on funding, which might depend on how many collaborators and use cases are available, etc).

For me scikit-build is definetly a big improvement, since setuptools becomes a pain for non trivial build. I will drop Python2.7 in v2.0.0 and might release it without PyPy wheels if I can not get it to work, since I do not think many users use this library from PyPy. However it would be nice to get PyPy working with scikit-build at some point.
If you need any help testing just let me know.

RapidFuzz is now using scikit-build. For now this requires a workaround for Cython and drops PyPy support. However things should improve when https://github.com/scikit-build/scikit-build/discussions/601 gets implemented.

Feel free to let us know if you have problems!

FYI, with io.open('README.md', 'rt', encoding="utf8") as f: in setup.py -  you don't need io.open anymore with Python 3, regular open is fine. pyupgrade (ideally with pre-commit) will cleanup these sorts of things for you. See https://scikit-hep.org/developer/style

you don't need io.open anymore with Python 3

Thanks for mentioning. This is the first release without Python2.7 support. In fact other than type hints the setup.py is the only pure Python file of the project. I did just try pyupgrade, which successfully transforms io.open to open. However it does not remove the then unused import io statement ...
I am looking forward to writing all of this in the pyproject.toml file and getting rid of setup.py ;)

Feel free to let us know if you have problems!

My problems so far are:

I have problems compiling the project for PyPy on some platforms with scikit-build. I think this was mostly problematic for Windows: https://github.com/maxbachmann/RapidFuzz/runs/4666969968?check_suite_focus=true

Which fails with
     Call Stack (most recent call first):
      C:/Users/runneradmin/AppData/Local/Temp/pip-build-env-j5_mpiwu/overlay/site-packages/cmake/data/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
      C:/Users/runneradmin/AppData/Local/Temp/pip-build-env-j5_mpiwu/overlay/site-packages/cmake/data/share/cmake-3.22/Modules/FindPythonLibs.cmake:310 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
      C:/Users/runneradmin/AppData/Local/Temp/pip-build-env-j5_mpiwu/overlay/site-packages/skbuild/resources/cmake/FindNumPy.cmake:44 (find_package)
      CMakeLists.txt:12 (find_package)

For now I dropped support for PyPy, since it is not used much anyways

I did not manage to add the Cython targets to the top level CMakeLists.txt: https://github.com/maxbachmann/RapidFuzz/blob/main/CMakeLists.txt and had to create one in the subdirectory, so the cython file is found: https://github.com/maxbachmann/RapidFuzz/blob/main/src/CMakeLists.txt. This appears to be a known issue: https://github.com/scikit-build/scikit-build/issues/543 and my current solution works for me (I would prefer being able to write them in the top level CMakeLists.txt in the long run)

Other than this the combination of scikit-build/cibuildwheels/github actions is awesome. They make building binary packages a lot less trouble.


Failed to open HTTP link

Please see to this page.
The URL in the project is http://rjxy.hfut.edu.cn/stumgr. In the GitHub card, it becomes https://lab.lepture.com/github-cards/cards/rjxy.hfut.edu.cn/stumgr. Obviously, there's something wrong with your code.

@hzxie GitHub API returns your homepage as rjxy.hfut.edu.cn/stumgr.

Add http:// prefix to the webpage section of your repo.

@hzxie GitHub API returns your homepage as rjxy.hfut.edu.cn/stumgr.

Add http:// prefix to the webpage section of your repo.


Clear terminal before running tests

Is there a way to clear the terminal and then run the tests? For example, how can I run [clear] and then the test command as usual.
I tried adding  [clear &&] as a Jest command, but that did not work.
Thanks

acutally we are already clearing the terminal before executing the jest command.
https://github.com/firsttris/vscode-jest-runner/blob/master/src/jestRunner.ts#L200

It must be my version then. I'm running VS Code 1.54.3 and Jest Runner 0.4.31. Unfortunately I cannot upgrade VS Code at this time.
Thank you for the quick response.


Disable Backend Deployment when build is triggered

Hi,
I have a use case:
We have 2 instances : A and B.
We always add any new feature or feature extensions in instance B.
Once everything is done and tested then we merge it with instance A.
Suppose, I am working on a new feature on instance B and this new feature requires data model changes. We updated the data model from amplify admin, deployed and take it's pull on our local system using amplify pull command.
Meanwhile, I have to fix an urgent issue on instance A, so I extended a branch C from A and merged C branch to A after fixing the issue.
But, all the data model changes vanished when a new build is triggered on instance A. Reason being, updated backend schema  code was there in branch B but not A and C.
That's why, I want to disable backend deployment on each build trigger. If there's any other way out, please let me know.
Here's the app id : d18qtdhf6c7z65
Region: ap-southeast-2 (Sydney)
Thanks In Advance.!!!

Hi @ParulSharma2622 thanks for your feedback, we're working on adding support for this use case, don't have an ETA to share at the moment but please stay tuned

@ParulSharma2622 we added support for conditional backend builds: https://docs.aws.amazon.com/amplify/latest/userguide/conditional-backends.html


How to handle "OpenAPI enums may only contain unit variants" error?

I have an endpoint where I need to model the payload using enum with data, ie. something like
#[derive(Debug, Enum, Clone, Eq, PartialEq, Deserialize, Serialize)]
pub enum Payload {
    Eq {...},
    Lt {...}
}

Basically similar to serde's enum tag representation as described here https://serde.rs/enum-representations.html.
The problem is the above fails with the following error:
error: Invalid enum variant Eq.
       OpenAPI enums may only contain unit variants.

Is there a way to make this work? Maybe disabling the openapi feature for specific endpoints, which then will allow usage of enums that are not unit variants?

The way I found to get around this is to manually implement Type, ToJSON,  and ParseFromJSON trait instead of #[derive(Enum)]

I believe the correct answer here is to use Union instead of Enum


Exported container doesn't have entrypoint set and also command is missing in helm template

Describe the bug
After exporting an epinio app I tried to import the app by using exported helm chart and image. The resulting pod is in CreateContainerError state most probably due to missing entrypoint set in container manifest or/and missing command/args keys in deployment helm template for the app.
To Reproduce
$ epinio app export app-webui ./
$ docker image import ./app-image.tar thehejik/app-webui
$ docker push thehejik/app-webui
$ mkdir chart
$ tar xvf app-chart.tar.gz -C chart/

Modify values.yaml to use the image and modify the route domain and id:
epinio:
  appName: app-webui-helm
  configpaths: []
  configurations: []
  env: []
  imageURL: thehejik/app-webui
  ingress: null
  replicaCount: 1
  routes:
  - domain: app-webui-helm.<IP_ADDRESS>.omg.howdoi.website
	id: app-webui-helm.<IP_ADDRESS>.omg.howdoi.website
	path: /
  stageID: 55aea1b94d388043
  start: null
  tlsIssuer: epinio-ca
  username: admin

Deploy the app by using the helm chart and image:
helm upgrade --install app-chart-helm ./chart/epinio-application/ --values ./values.yaml

Expected behavior
the app pod is running
Logs
from the describe pod:
Error: failed to generate container "dd2594df4d8c040042feafff171956e8ec32ab87adb728a9768efaa025c1bc0d" spec: failed to generate spec: no command specified

Investigation so far .... Ran an epinio push -n fox -p assets/sample/app, with the image coming out of staging saved to my personal account on docker hub: registry.hub.docker.com/a99k/workspace-fox.
docker inspecting this image shows 12 layers, Cmd: null for all. One of the layers has Entrypoint: "/cnb/process/web".
docker saveing the same into a tarball and digging into the files so obtained shows the same.
After overcoming issues with epinio app export (could not do it with the registry.hub.docker) I get an app-image.tar which is quite similar. It looks like a docker save result with 12 layers, no Cmd's, one /cnb/process/web entrypoint.
The main <hash>.json files are identical across the two downloads, in both name and content.
While the hashes for the layer names themselves are different the tar archives in these layers look similar at first glance, and after sorting them by SHA256 hash definitely shows as identical in content
I conclude that the tarball we got from running epinio app export is materially the same we get from docker pull + docker save commands applied to the image registry.
I currently suspect that the docker image import ./app-image.tar thehejik/app-webui command used in the example might be to blame.
Looking at the output of docker help we seem to have the command pairs export/import, and save/load.
Further looking at the output of docker image help I still see save/load, and import alone.
I will look into the usage of docker load / docker image load.

It works when importing the image with docker load -i ./app-image.tar, otherwise the process from the original description is valid. I changed appName, imageURL, routes and removed env: section (EPINIO_APP_DATA) in values.yaml. The entrypoint of the image is set in my case to: "Entrypoint": [ "/cnb/process/web" ]
Only issue I noticed it that the image has been generated 43y ago (~start of UNIX epoch):
$ docker images
<none>                         <none>                                 33291ed4b860   43 years ago    949MB

So, this looks to be a documentation issue then. Will prepare some words.


Fix bug 220654 Cannot enter breakmode with object on the stack

Issue here is g++ mapped one address to two source lines for the
constructor. What I did is make the line mapping collection
handle that. Since we don't know what the "correct" line is,
it just chooses one, unless the old line is line number 0.

👍

@gregg-miskelly @edumunoz @andrewcrawley @chuckries

@richardstanton


Add email subscription button

Resolves #24
Don't merge this yet. It's unstyled and the mailchimp campaign is not yet done.
Previews:

Currently waiting for a reply from MailChimp because of the following lovely automated emails:

I think we shouldn't be at fault here? Here's the relevant terms and conditions:

Update: I simply created a new account and now it seems fine

Done!
@bash created this wonderful form for us:

Thanks @bash ❤


ABCI kvstore app hangs

What went wrong?
I followed the direction here
Running tendermint-core version: 0.35.9 (also have tried 0.34.21)
Running tendermint-rs on commit: 14fd628e82ae51b9f15c135a6db8870219fe3c33
After booting up tendermint-core I get these logs:
2024-08-19T15:48:55-04:00 INFO starting service impl=multiAppConn module=proxy service=multiAppConn
2024-08-19T15:48:55-04:00 INFO starting service connection=query impl=socketClient module=abci-client service=socketClient
2024-08-19T15:48:55-04:00 INFO starting service connection=snapshot impl=socketClient module=abci-client service=socketClient
2024-08-19T15:48:55-04:00 INFO starting service connection=mempool impl=socketClient module=abci-client service=socketClient
2024-08-19T15:48:55-04:00 INFO starting service connection=consensus impl=socketClient module=abci-client service=socketClient
2024-08-19T15:48:55-04:00 INFO starting service impl=EventBus module=events service=EventBus
2024-08-19T15:48:55-04:00 INFO starting service impl=PubSub module=pubsub service=PubSub
2024-08-19T15:48:55-04:00 INFO starting service impl=IndexerService module=txindex service=IndexerService
2024-08-19T15:48:55-04:00 INFO ABCI Handshake App Info hash="\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00" height=0 module=consensus protocol-version=1 software-version=0.1.0
2024-08-19T15:48:55-04:00 INFO ABCI Replay Blocks appHeight=0 module=consensus stateHeight=0 storeHeight=0
2024-08-19T15:48:55-04:00 INFO Stopping abci.socketClient connection=consensus module=abci-client reason="read message: EOF"
2024-08-19T15:48:55-04:00 INFO stopping service connection=consensus impl=socketClient module=abci-client service=socketClient
2024-08-19T15:48:55-04:00 ERROR consensus connection terminated. Did the application crash? Please restart tendermint err="read message: EOF" module=proxy
fish: Job 1, 'tendermint start' terminated by signal SIGTERM (Polite quit request)

on the ABCI client I recieve an unwrap on None:
thread '<unnamed>' panicked at /Users/armins/Dev/tendermint-rs/abci/src/application.rs:168:45:
called `Option::unwrap()` on a `None` value

It seems like the application is harcoded to work with v38. Is that correct?
Steps to reproduce
Run  cargo run --features="binary kvstore-app client" on the latest commit
Run  tendermint unsafe-reset-all && tendermint start on the versions of tendermint-core listed above
Definition of "done"
What version of tendermint-core is compatible with the ABCI library that is released today?

Working with latest CometBFT. Closed


Please allow preview versions of Az Module

It's not currently possible to specify preview versions of the Az Module, for example 4.0.1-preview.
It would be useful to be able to use preview versions as they often contain features missing in older versions.
2020-02-11T09:40:06.2057740Z ##[section]Starting: Azure PowerShell script: InlineScript
2020-02-11T09:40:06.2182892Z ==============================================================================
2020-02-11T09:40:06.2183001Z Task         : Azure PowerShell
2020-02-11T09:40:06.2183080Z Description  : Run a PowerShell script within an Azure environment
2020-02-11T09:40:06.2183334Z Version      : 5.162.5
2020-02-11T09:40:06.2183958Z Author       : Microsoft Corporation
2020-02-11T09:40:06.2184024Z Help         : [Learn more about this task](https://go.microsoft.com/fwlink/?LinkID=613749)
2020-02-11T09:40:06.2184116Z ==============================================================================
2020-02-11T09:40:07.7218210Z ##[error]The Azure PowerShell version '4.0.2-preview' specified is not in the correct format. Please check the format. An example of correct format is 1.0.1
2020-02-11T09:40:07.7608563Z ##[section]Finishing: Azure PowerShell script: InlineScript

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

ID: fb215324-b1a0-93b5-5022-4bcc7da93bb7
Version Independent ID: 9eb2977b-ac34-9d53-670e-04fa027bc8e4
Content: Azure PowerShell task - Azure Pipelines
Content Source: docs/pipelines/tasks/deploy/azure-powershell.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

Thanks for the suggestion! The product teams aren’t always watching this repository, so to make sure it gets in front of them for triage, please submit your idea here.

Thanks, done: https://developercommunity.visualstudio.com/idea/918712/azure-powershell-task-please-allow-preview-version.html


Intel RealSense L515 Not Detected in RealSense Viewer

I recently purchased an Intel RealSense L515 device. While the device is detected in other camera software, it does not appear in the Add Sources section of the RealSense Viewer. Instead, the following warnings are displayed:

Steps to Reproduce:

Connect the L515 device to the system using a USB 3.0 port.
Open RealSense Viewer.
Check if the device appears under Add Sources.

System Information:
Device Model: Intel RealSense L515
Operating System: Windows 11
Connection Type: USB 3.0
Additional Notes:
The device is recognized and works properly with other camera software, indicating that the issue may be related to the RealSense Viewer or SDK compatibility.

Hi @jayasurya00098  The L515 camera model is no longer supported in recent RealSense SDK and RealSense Viewer versions as it is a retired camera model.  It should be detected if you install version 2.53.1 of the SDK or Viewer, the final version to support L515.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.53.1
You can install this SDK with an automated installer program called Intel.RealSense.SDK-WIN10 (which also works with Windows 11) or just the RealSense Viewer by downloading and running the file Intel.RealSense.Viewer.exe


openshift: 3.10 -> 3.11

Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>Motivation for this change
Bump to latest openshift version. Using go 1.10 instead of 1.9.
Things done

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

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

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

Success on aarch64-linux (full log)
Attempted: openshift
Partial log (click to expand)
warning: GOPATH set to GOROOT (/nix/store/gjgfp0k69kbhz4r4p97qr650z4p2cgnb-go-1.10.3/share/go) has no effect
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0
shrinking /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0/bin/oc
shrinking /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0/bin/openshift
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0/bin
patching script interpreter paths in /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0
checking for references to /build in /nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0...
/nix/store/f9m9hrmpzshhi830jhh61bq1lb5z4pan-openshift-origin-3.11.0

Success on x86_64-linux (full log)
Attempted: openshift
Partial log (click to expand)
warning: GOPATH set to GOROOT (/nix/store/zlav9p2jp91p7vrlv9rbqm1jjmkab5jz-go-1.10.3/share/go) has no effect
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0
shrinking /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0/bin/oc
shrinking /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0/bin/openshift
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0/bin
patching script interpreter paths in /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0
checking for references to /build in /nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0...
/nix/store/4szszfcn27x2pai7z964pgy7sv5yfyqd-openshift-origin-3.11.0

@GrahamcOfBorg build openshift

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: openshift
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: openshift
Partial log (click to expand)
warning: GOPATH set to GOROOT (/nix/store/2jz7z8f6xnx1cv8vr6fmf21y96fg86ri-go-1.11/share/go) has no effect
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0
shrinking /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0/bin/oc
shrinking /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0/bin/openshift
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0/bin
patching script interpreter paths in /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0
checking for references to /build in /nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0...
/nix/store/v6gm2lbfqm2xd58wf1x5fx10p2c15nd7-openshift-origin-3.11.0

Success on x86_64-linux (full log)
Attempted: openshift
Partial log (click to expand)
warning: GOPATH set to GOROOT (/nix/store/g0qnlxjw2qs7rk0aamicy8z3x62pcrx8-go-1.11/share/go) has no effect
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0
shrinking /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0/bin/openshift
shrinking /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0/bin/oc
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0/bin
patching script interpreter paths in /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0
checking for references to /build in /nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0...
/nix/store/76cs1pk62pvqcd11w3v4qkygfnyrfs2d-openshift-origin-3.11.0


refactor: error handling for the schema controller & added global exception handler

What
Refactors the error handling for the schema controller and introduces a global exception handler to improve error management throughout the application.
Why
Improved error handling is crucial for maintaining code quality and ensuring robustness. By refactoring the error handling for the schema controller and adding a global exception handler.
How
Refactored error handling logic in the schema controller to adhere to best practices and improve readability.
Implemented a global exception handler to centrally manage exceptions and streamline error reporting across the application.

Closing this as DCO failed for this PR, raised #130


[BUG] Shuffle read latency is too high when automatic Broadcastjoin is triggered

Env:
spark 3.2.2
celeborn 0.2.1
Question desc:
When spark3 spark.sql.adaptive.autoBroadcastJoinThreshold is turned on, it is found that when automatic Broadcastjoin is triggered, if spark.sql.shuffle.partitions is set relatively large at this time, the broadcast time will be longer
Spark config:
#Dynamic resource
spark.dynamicAllocation.enabled true
spark.dynamicAllocation.minExecutors 1
spark.dynamicAllocation.maxExecutors 500
spark.dynamicAllocation.initialExecutors  2
spark.dynamicAllocation.executorIdleTimeout 120
#Adaptive
spark.shuffle.minNumPartitionsToHighlyCompress 5000
spark.sql.adaptive.enabled         true
spark.sql.adaptive.coalescePartitions.enabled true
spark.sql.adaptive.skewedJoin.enabled true
spark.sql.adaptive.advisoryPartitionSizeInBytes 64M
spark.sql.adaptive.coalescePartitions.minPartitionSize  10M
spark.sql.adaptive.skewJoin.skewedPartitionFactor 2
spark.sql.adaptive.skewJoin.skewedPartitionThresholdInBytes 128M
spark.sql.optimizer.dynamicPartitionPruning.enabled   false
#celeborn
spark.shuffle.service.enabled false
celeborn.shuffle.rangeReadFilter.enabled true
celeborn.shuffle.partitionSplit.mode hard
spark.shuffle.manager org.apache.spark.shuffle.celeborn.RssShuffleManager
spark.celeborn.master.endpoints  xxxxxx
spark.rss.push.data.replicate false
spark.rss.shuffle.writer.mode hash
kyuubi
spark.sql.optimizer.insertRepartitionBeforeWrite.enabled true
spark.sql.optimizer.finalStageConfigIsolation.enabled true
spark.sql.finalStage.adaptive.advisoryPartitionSizeInBytes 256M
spark.sql.finalStage.adaptive.coalescePartitions.minPartitionSize 50M
spark.sql.extensions org.apache.kyuubi.sql.KyuubiSparkSQLExtension,org.apache.kyuubi.plugin.spark.authz.ranger.RangerSparkExtension
reproduce sql
set spark.sql.adaptive.autoBroadcastJoinThreshold=10M;
set spark.sql.autoBroadcastJoinThreshold=-1;
set spark.sql.shuffle.partitions=5000;
select  a.id from
( select id from    range(1,10000) )  a
inner join
(select id  from  range(1,100) )  b  on a.id=b.id
I found that this will be affected by the spark.sql.shuffle.partitions parameter. When the parameter is relatively large, the broadcast process will take longer
Test case:
when spark.sql.shuffle.partitions=10;

when set spark.sql.shuffle.partitions=1000;

when set 5000

I didn't find this problem when I used the native spark3 built-in shuffle

I think it should be caused by too many connections when the partition is too large. I also found a lot of connection creation process from the log as follows

If the shuffle.partitions can be reduced, this problem can be solved, but in complex tasks, both large and small tasks exist. If the setting is too small, it is not very suitable for large tasks

Does increasing celeborn.network.timeout help? The default values is 240s.
https://celeborn.apache.org/docs/0.2.1-incubating/configuration/#network

Is it caused by not disabling spark.sql.adaptive.localShuffleReader.enabled?

Is it caused by not disabling spark.sql.adaptive.localShuffleReader.enabled?

Right, @thomasg19930417 could you turn off spark.sql.adaptive.localShuffleReader.enabled and test again?

After testing, it is indeed caused by this parameter, thank you for your reply @pan3793 @wForget @waitinfuture

After testing, it is indeed caused by this parameter, thank you for your reply @pan3793 @wForget @waitinfuture

We do added comment about this config, maybe we should highlight it more :)

After testing, it is indeed caused by this parameter, thank you for your reply @pan3793 @wForget @waitinfuture

 We do added comment about this config, maybe we should highlight it more :)

This parameter was commented out by my mistake, maybe it was automatically commented out when the shell was copied.


model_zoe_k output off by a decimel point

Hello,
I have been testing model_zoe_k and model_zoe_nk to inference the distance to cars in a parking lot. I measured a distance of 40 meter with my tape measure. model_zoe_k gives me a distance of 3.32 meters to a point on a car, while model_zoe_nk gives me a distance of 28.98 meters to the same point. Seems like the zoe_k model is off by a factor of ten. Is this a configuration issue, because the output depth map looks on point, but the numbers for the zoe_k model are not on the right scale. Can anyone confirm? The pretrained resources load as either ZoeD_M12_k.pt or ZoeD_M12_nk.pt.
Additionally, should I crop my input image before inference for better results? Should I adjust any ZoeDepth parameters for my camera's intrinsic matrix or position above the ground? Thanks.

Hi,
Thanks for your interest in our work. Yes, you should use config_mode="eval" when loading the model for higher metric scale accuracy

Hello,
Thank you for your fast response! config_mode="eval" does seem to produce higher metric scale accuracy. I received using the zoe_nk model a median depth of 47.75 meters to the car that was approximately 40 meters away.
However, the zoe_k model produced a median depth of 4.87 meters using eval mode (with the maximum depth in the depth map being 7.65 meters). Could you help me determine why the depth for this model seems off by a decimal point? Could you check if there is an issue with the zoe_k model config, as this model is better for my use case, and the colorized depth map produces better output than the zoe_nk model.

Hello @whileCoffee @shariqfarooq123.
sorry for troubling you but I need help.
I saw that you were able to inference the distance in meters to objects.
I am trying to do the same thing but I am not sure if I am doing it right or not. This is how I did it.
# load model
conf = get_config("zoedepth_nk", "eval")
model_zoe_nk = build_model(conf)

# inference
depth_numpy = zoe.infer_pil(image)

Is the result from depth_numpy refer to the distance from camera in meters?
And both mode="infer" and mode="eval" gave me the same result, is this the correct way to set config_mode="eval" that you mentioned above?
If you have done differently, can you show me how you did it?
Thank you in advance.


[camera] Migrate to the new embedding

Description
Migrates the camera plugin to the new embedding and adds an example
activity exercising it.
Unlike some of the previous PRs on this, this is the minimal migration
that would land this without adding any tech debt. From previous offline
discussions we'd like to scope these migrations to the bare minimum
required to keep the patches small. See #2114 for a migration combined
with a refactoring.
That said there are still some minor changes to prevent this from adding
additional tech debt, going a little beyond #2118:

#onMethodCall has been split up into its own MethodCallHandlerImpl
class to try and keep CameraPlugin from mixing concerns. Before the
migration, all it was doing was responding to method calls. Now
there's a significant amount of logic just based around responding to
lifecycle events. It still seemed better to split that into a separate
file than to try and manage that logic all in one place.

Other than the above refactorings, the original logic is untouched.
Related Issues
Fixes flutter/flutter#41834.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

@mklim After this merge using the camera plugin on a Note 10+ (and other devices) to stream images is useless. Everything freezes after a couple of seconds moving the camera around. Log shows this:
E/CameraCaptureSession( 5749): Session 1: Exception while stopping repeating:
E/CameraCaptureSession( 5749): android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2435)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl.stopRepeating(CameraDeviceImpl.java:1126)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraCaptureSessionImpl.close(CameraCaptureSessionImpl.java:526)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera.closeCaptureSession(Camera.java:539)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera.close(Camera.java:545)
E/CameraCaptureSession( 5749): 	at io.flutter.plugins.camera.Camera$2.onError(Camera.java:203)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks.notifyError(CameraDeviceImpl.java:1929)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.CameraDeviceImpl$CameraDeviceCallbacks.lambda$Sm85frAzwGZVMAK-NE_gwckYXVQ(Unknown Source:0)
E/CameraCaptureSession( 5749): 	at android.hardware.camera2.impl.-$$Lambda$CameraDeviceImpl$CameraDeviceCallbacks$Sm85frAzwGZVMAK-NE_gwckYXVQ.accept(Unknown Source:8)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.PooledLambdaImpl.doInvoke(PooledLambdaImpl.java:258)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.PooledLambdaImpl.invoke(PooledLambdaImpl.java:182)
E/CameraCaptureSession( 5749): 	at com.android.internal.util.function.pooled.OmniFunction.run(OmniFunction.java:77)
E/CameraCaptureSession( 5749): 	at android.os.Handler.handleCallback(Handler.java:873)
E/CameraCaptureSession( 5749): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/CameraCaptureSession( 5749): 	at android.os.Looper.loop(Looper.java:216)
E/CameraCaptureSession( 5749): 	at android.app.ActivityThread.main(ActivityThread.java:7263)
E/CameraCaptureSession( 5749): 	at java.lang.reflect.Method.invoke(Native Method)
E/CameraCaptureSession( 5749): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
E/CameraCaptureSession( 5749): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
E/BufferQueueProducer( 5749): [ImageReader-1280x720f23m2-5749-1] dequeueBuffer: attempting to exceed the max dequeued buffer count (9)

Thanks for reporting the issue and the stack trace @PerLycke, sorry about the regression. Do you mind also posting steps on how to reproduce the crash? A small test case would help too if the example app isn't enough to cause it.

@mklim Never mind my report, after some additional debugging it seems like it's device specific to the Note 10+, and not connected to this commit in particular. Sorry for the confusion, and keep up the good work.

@PerLycke no problem, thanks for debugging this further too. Looks like the Note 10+ issue is now being tracked at flutter/flutter#43566.


Cannot import static Image URLs

The problem
Importing static Image URLs throws Only static values are allowed inside of stylex.create() call error.
How to reproduce

Steps to reproduce:

Import an image, e.g.

import logo from<EMAIL_ADDRESS>

Create the style with a background image.

const styles = stylex.create({
  logo: {
    backgroundImage: `url("${logo}")`,
  },
});

Use it in the component. e.g.

const Component = () => <div {...stylex.props(styles.logo)} />

Expected behavior
The image to be rendered, and the correct image URL to be inserted into the generated CSS.
Discussion
I understand that in the docs it says:

However, the Webpack plugin should be able to resolve the path to the image (whether that's a Base64 url or otherwise), and the generated CSS should use that string. These are not run-time values and are known at compile time, so it should be possible to import this.
I understand that a workaround can be achieved by doing something like this:
const styles = stylex.create({
  logo: (logoUrl: string) => ({
    backgroundImage: `url("${logoUrl}")`,
 }),
});

But as I said before, these values are known at compile time and thus should be valid values.
Please advise what the recommended way of importing and setting background images in StyleX.
Environment (include versions). Did this work in previous versions?
StyleX version: v0.3.0
StyleX Webpack version: v0.3.0
Node version: v18.17.0
MacOS Sonoma 14.2.1

All styles need to be statically defined in the same file. So this wouldn't normally work.
However, since in this case you're importing an asset and not a file, you're relying on tooling to convert that import into a static string. If this process can be encapsulated as a Babel plugin, you can configure StyleX to resolve the import into a string before stylex tries to compile the file.


Broken as of 6/9/2016?

I installed the extension and it doesnt seem to work:
My user agent:

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36

It's working now, had to just restart the tab a few times. Not sure what the issue was.


Export worker for package @ffmpeg/ffmpeg

This PR adds worker export for package @ffmpeg/ffmpeg.

approved the workflow run, do we know that this export works / i don't think we actually build the worker separately right now...

The worker export files do exist. See https://www.npmjs.com/package/@ffmpeg/ffmpeg?activeTab=code
Currently, I patched the package in my project. And It works well.


Error: cannot insert a left sibling to a token that closes a level

Hi ,
Getting the error, when running a custom Class in ABAP cleaner

Log in the mentioned path "line 4,484: cannot insert a left sibling to a token that closes a level"
Code line 4484

Kindly suggest on how this error can be resolved.

Hi FirdousP,
thanks for reporting this issue – however, I am afraid I would need more context (i.e. more of the surrounding code) to be able to reproduce this error. The error message is indeed a bit odd for this line 4484, because in ABAP clenaer, a "token that closes a level" would typically be a closing parenthesis ")" or brace "}".
Maybe you could try to reduce your code sample to a minimal example that triggers the error? Otherwise, if you don't feel comfortable to post the whole method here, you might as well email it to "abap-cleaner at sap dot com" (which is just received by another SAP colleague and myself).
Kind regards,
Jörg-Michael

Hi FirdousP,
as mentioned, without some more context, I am afraid I can't reproduce this, so closing this issue for now. Please feel free to reopen the issue if you have some example to help reproduce it.
Kind regards,
Jörg-Michael