Sylius 1.12.0

This Pull Request aims at making the bundle compatible with Sylius 1.12
I fixed any error I could find but I couldn't run the tests.
To be merged, it would require :

[x]  a clean test run
[x] remove older Sylius versions from composer.json (they can fallback to older releases)

Could anyone help for those 2 points ?

@julienTroopers I create a pull requets on your fork: https://github.com/julienTroopers/RbacPlugin/pull/1

Thanks a lot for your help !

@bigboss86 can you review that please ?

Merged! Thanks!


waitForText with scroll set to true scrolls only first ListView it finds

From<EMAIL_ADDRESS>on September 06, 2011 01:43:13
What steps will reproduce the problem? 1. Create a tabbed activity with a ListView in each tab
2. In the second tab in the list, put "needle" at the end of the list
3. call solo.waitForText("needle", 1, 2000, true)
What is the expected output?
list will scroll down until the match is found
What do you see instead?
list doesn't scroll, and we're stuck in an infinite loop in searchFor (timeout is ignored, opened another bug for that) What version of the product are you using? On what operating system? Robotium 2.5, Android 2.2 (Cyanogen 6). Please provide any additional information below. the reason for that is that the function:
public boolean scroll(int direction)
gets a list of all ListViews on screen, but scrolls only the first.
It should enter a for loop which scrolls all ListViews on screen.
Original issue: http://code.google.com/p/robotium/issues/detail?id=151

From<EMAIL_ADDRESS>on September 06, 2011 01:58:24
A suggested fixed version of scroll:
public boolean scroll(int direction) {
final ArrayList viewList = viewFetcher.getViews(null, true);
final ArrayList listViews = RobotiumUtils.filterViews(ListView.class, viewList);
boolean allFinished = true;
boolean containsScrollViews = false;

if (listViews.size() > 0) {
	containsScrollViews = true;
	for (int i = 0; i \< listViews.size(); i++) {
		allFinished = allFinished && scrollList(ListView.class, i, direction, listViews);
	}
}

final ArrayList<GridView> gridViews = RobotiumUtils.filterViews(GridView.class, viewList);

if (gridViews.size() > 0) {
	containsScrollViews = true;
	allFinished = allFinished && scrollList(GridView.class, 0, direction, gridViews);
}

final ArrayList<ScrollView> scrollViews = RobotiumUtils.filterViews(ScrollView.class, viewList);

if (scrollViews.size() > 0) {
	containsScrollViews = true;
	allFinished = allFinished && scrollScrollView(direction, scrollViews);
}

return allFinished && containsScrollViews;

}
This works for me.

From<EMAIL_ADDRESS>on September 13, 2011 01:28:30
Thanks for this.
Status: Accepted
Owner<EMAIL_ADDRESS>

From<EMAIL_ADDRESS>on November 13, 2011 22:32:31
This is a design choice. Making Robotium search multiple lists introduces issues with list rich applications. One needs to click the correct tab first and then use searchText to search that specific list.
Status: WontFix


fix: add --no-pager option to git command

Description (required)
The previous git command can not work as expected. With no --no-pager option, git command will output the paging result, so execSync can't get the returned result.

After adding the --no-pager option(meanwhile set pretty to %cIand wrap filepath with double quote), we get what we want.

Related issues & labels (optional)

Suggested label: update doc

Thanks for the PR @CaptainOfPhB!
I see what you mean about the pager when using the command in the terminal. However, I found that calling execSync with the git command works without --no-pager, and only in the terminal did I have that issue.
Looking at the new formatting, running execSync with --pretty=%cI, it threw an invalid date error, displaying the last character as a \n, something that doesn't happen with the old argument. Did you have a specific issue with the old formatting?

Thank you for your reply!
The previous command run failed yesterday but worked just now when I tried again. Looks so wired :(
But the filepath should wrap with double quotes or the command will fail if there is blank space in the filename.

Hi @CaptainOfPhB ! Would you please update your suggestion if you think all that's now needed are the double quotes? Then, we can get this merged!  :partying_face:

Thanks for the update! Let's get this merged! :partying_face:


Add common corruptions

Address #40
I parallelized the attacks and I find that it takes ~10 minutes to apply all corruptions to all 1000 test-set images on a single P100 GPU

Once tests pass this looks good.
It's surprising that the models do so well on this task -- it probably says something about how easy the bird-or-bicycle task is.

The README formatting is broken with this commit.

Good catch. Fixed


Feature request | Box Plot Violin Chart

It would be awesome to get something like this

As it is already in WandB
I assume that it should be possible somehow.
Thanks

Hello @BenSpex , thank you for your issue report. Unfortunately, we have shifted directions away from the dashboards / stream table product to a more opinionated solution for LLM debugging and tracing. If you are curious, please checkout our docs at https://wandb.me/weave. As such, I am going to close this ticket as we are unlikely to continue development against this feature set at the moment.


Make the maximum polling backoff configurable

Fixes #1492 by making it possible for users to change the maximum polling backoff duration as a config item on the controller; makes the default a more sensible 20m.

LGTM, once the tests get fixed.


Server Side Pagination

Hi
do you have an example of server side paging? I can't seem to get it to work if the data size is just one page.
Thanks
Rob

+1

+1

+1

Guys, in this demo Demo has an example of the side of the served, and the code is not minified, you can check.


There is no 'south' database module

I am having Django 1.9.6 and django-two-factor-auth==1.3.1
Now i am getting this error..
Please help me to solve this error.
./manage.py syncdb --noinput
There is no South database module 'south.db.sqlite3' for your database. Please either choose a supported database, check for SOUTH_DATABASE_ADAPTER[S] settings, or remove South from INSTALLED_APPS

if i removed or unistall south it will say
ImportError: No module named south
so please give me a solution

If you're using Django 1.9, you don't need to be using south. Remove it from your INSTALLED_APPS in your settings. Also, this repo is for the django debug toolbar. You will be better off asking questions similar to this on StackOverflow.

Thank you for replying


proto cannot install deno in windows.

Powershell log is here.
PowerShell 7.4.1
PS C:\Users\WDAGUtilityAccount> proto install node
⠁ Installing Node.js 21.7.0
[ INFO 2024-03-07 23:25:38.374] proto::commands::install:install  Node.js has been installed to ~\.proto\tools\node\21.7.0!
PS C:\Users\WDAGUtilityAccount> proto install deno
⠁ Installing Deno 1.41.1
⠁ Installing Deno 1.41.1
Error: plugin::http

  × Failed to make HTTP request for https://dl.deno.land/release/v1.41.1/deno-x86_64-pc-windows-msvc.zip.
  ├─▶ error sending request for url (https://dl.deno.land/release/v1.41.1/deno-x86_64-pc-windows-msvc.zip): error
  │   trying to connect: invalid peer certificate: UnknownIssuer
  ├─▶ error trying to connect: invalid peer certificate: UnknownIssuer
  ╰─▶ invalid peer certificate: UnknownIssuer

proto 0.31.3

I was able to install Node.js.
But deno failed.
I can access the URL (https://dl.deno.land/release/v1.41.1/deno-x86_64-pc-windows-msvc.zip) and download the zip file using Edge from the Windows device.

@lazex Are you behind a firewall or intranet or something like that that would block the ssl handshake?
You can try these settings to work around it: https://moonrepo.dev/docs/proto/config#settingshttp

Are you behind a firewall or intranet or something like that that would block the ssl handshake?

No.
But, I use proto inside Windows Sandbox.
Is this relevant?

You can try these settings to work around it: https://moonrepo.dev/docs/proto/config#settingshttp

Thanks.
This works.
[settings.http]
allow-invalid-certs = true


bosh target throws an error

Hi ,
when i set the target to bosh it throws error as below, can some one help ?
i307955@mo-eb106185c:~/cf_nise_installer/nise_bosh$ bosh vms --details
Please choose target first
i307955@mo-eb106185c:~/cf_nise_installer/nise_bosh$ bosh target https://api.<IP_ADDRESS>.xip.io
[WARNING] cannot access director, trying 4 more times...
[WARNING] cannot access director, trying 3 more times...
[WARNING] cannot access director, trying 2 more times...
[WARNING] cannot access director, trying 1 more times...
cannot access director (Connection refused - connect(2) (https://<IP_ADDRESS>:25555))
BRs, Gowrisanakr

This installer doesn't launch a BOSH cluster. It just install a CF cluster using the BOSH artifacts in cf-release. Therefore, it doesn't provide a BOSH endpoint.


'Archive comment' functionality

Hey, this plugin rocks; thanks!
To add on top of it, it would not be that difficult to make an 'Archive block' plugin from this plugin.
I've found all 'Comments' and 'comment' strings in the logseq.js and index.js files of the 'assets' folder and replaced them with 'Archive' and 'archive' so I can run locally this modified version of the plugin, which is basically a 1:1 copy, but some labels are different.
However, just one feature of this 'Archive block' plugin should be different from the original version. Since there's no need to write a comment after archiving a block, the archiving plugin should not create a new blank block, as the 'Comment block' plugin does.
It'd be great if you could post this modified version of the plugin here, which does not create a new blank block, ideally as index.js and logseq.js files, so users interested in this feature could use it without downloading it from the marketplace.
Or, even better, if you like this idea and have time for that, you could create and upload this 'Archive comment' plugin to the marketplace :-)
Thanks!

Ohhh, I forgot to mention in the comment above that opening the right sidebar would also be unnecessary for the 'Archive comment.'

Eventually, in the index.js file, I managed to find this 'if' condition
if (blockRefBlock?.uuid) { await logseq.Editor.openInRightSidebar(blockRefBlock?.uuid);,
which triggers the opening of the right sidebar and creates an empty block. Changing it to 'if not' bypassed both opening the sidebar and creating a new block, so this cheap hack solved both of the issues described in the opening post.
For anyone interested in this modification, the resulting index.js file is attached below as a raw text file.

Attached file: index.txt


[RFC002] Static GProperty Descriptors

Static GProperty Descriptors
RFC
Please see the RFC here: https://github.com/gircore/rfcs/blob/master/rfc-002-static-properties.md
It explains the proposal and some potential solutions.
Summary
To allow Gir.Core be a part of the current C# UI ecosystem, the implementation of GProperties can be done using Static Properties, to match what it's done now using DependencyProperty in other libraries. For that we have the following goals:

Declare GProperties of current Wrappers using Static Properties;
Allow library users to declare GProperties of theirs Subclass using Static Properties;
An high-level API will provide access to the GProperty value, to retrieve and edit it through the corresponding Property Descriptor.
Property Descriptors must know the type (the C# type) of the GProperty;
Property Descriptors must know the type (the C# type) of the GObject in which it will be registered;
Property Descriptors must know the name of the GProperty;
Property Descriptors must know if the GProperty is write-only, read-only, or read-write;
Property Descriptors must allow an easy registration and initialization of the GProperty in the GObject;
Property Descriptors must also describe child GProperties;
All of these points must be implemented in an easy to use, DependencyProperty-like manner.

These goals can lead us to these achievements:

Type System Integration with GObject, as discussed in #46, and described by [RFC001].
Solid MVVM binding model, as discussed in #34, and described by [RFC003].

This looks good to me, we should see how the signals and properties integrate into: https://github.com/gircore/gir.core/pull/52

Good, I will rebase you recent changes on #52 into #58 and try to continue on this way then :-)

One thing I would like to try and keep are strongly typed signal args. It makes the developer experience much nicer as it integrates with intellisense, etc
For example:
class DestroySignalArgs : SignalArgs
{
    string someRelevantArg;
    int someOtherRelevantArg;
}

:+1:
I think you could just try to use the new properties / signals in Window and Button, this is enough for the small quickstart demo.
With this we could check the overall design and decide if this is what we want.

One thing I would like to try and keep are strongly typed signal args. It makes the developer experience much nicer as it integrates with intellisense, etc

Good point, but these ones can be generated? Or they will be hand crafted?

Good point, but these ones can be generated? Or they will be hand crafted?

For the proof of concept we can hand craft them. Later we can try to generate as much as possible if there is no API tradeoff.

@firox263

One thing I would like to try and keep are strongly typed signal args. It makes the developer experience much nicer as it integrates with intellisense, etc

While it will be totally possible to do that, It will break the experimental feature I've added in #58 for the definition of signals callbacks using indexers. If we want theses features together, a possible workaround will be to generate theses indexers at the same time we will generate signal descriptors:
// In the Container class...

// The signal descriptor will need to know the type of the SignalArgs
public static readonly Signal<AddedSignalArgs> AddSignal = Signal<AddedSignalArgs>.Register("add");

// This one need to be generated, or added manually
public EventHandler<AddedSignalArgs> this[Signal<AddedSignalArgs> signal]
{
    set => signal.Connect(this, value, true);
}

I think it's reasonable to generate this automatically. It's definitely possible as we have the necessary type annotations in Gir data.
We should register a normal event handler so we still get the += syntax, and use this inside the indexer.

@firox263 the complete syntax is this:
// The signal descriptor
public static readonly Signal<AddedSignalArgs> AddSignal = Signal<AddedSignalArgs>.Register("add");

// The event handler
public event EventHandler<AddedSignalArgs> Added
{
    add => AddSignal.Connect(this, value, true);
    remove => AddSignal.Disconnect(this, value);
}

// The signal indexer
public EventHandler<AddedSignalArgs> this[Signal<AddedSignalArgs> signal]
{
    set => signal.Connect(this, value, true);
}

But I don't think it's possible use the event handler directly into the indexer 🤔

That's perfectly fine in my opinion. As long as we support the traditional use case of event handlers as well as the indexer, I don't think there's a problem here. Lgtm 👍


VectorTileLayer not working with vite project

I have an app created with vite. Installed this library and I'm trying to use a vector tile to display in the map. I have tried the url used for the example for this library and even from the esri documentation here for vector tiles. Even created another repo where it's just the base template that vite installs (react-javascript)

and it's giving me this main error
Uncaught TypeError: Cannot use 'in' operator to search for '_leaflet_id' in undefined
Things I tried:

esri-leaflet-vector is installed (VectorBasemapLayer works perfectly, VectorTileLayer doesn't)
create vite base app with just this library installed
copied the dependencies versions used in the example (except react (v18.3.1 used) and react-dom (v18.3.1 used))
tried vectortileserver url links from esri documention for vector tiles

help would be apprecitated.

Thank you for reporting this issue (and doing a well-written writeup).
I am able to reproduce this by spinning up an npm create vite reproduce-example-project with react and typescript, installing everything, and trying to use VectorTileLayer.
This is extremely odd.  I have no had this issue when using parcel or webpack.  Let me do some digging and see if I can come up with anything as to why using this library with vite creates this issue.
Have you tried using the "vanilla" version of a VectorTileLayer with Vite?  Does that work?  If that causes the same problem, it helps debug whether the issue in is this wrapper library, or upstream somewhere.

sigh so this problem is very strange indeed.  Looking into it, the author of leaflet answered another person with the same here: Cannot read property '_leaflet_id' of undefined:

This happens when tilelayer variable is undefined at the moment when this line executes. Put a debugger statement there and figure it out, shouldn't be hard.

Digging into the leaflet src code, when the map.removeLayer event fires, if the layer that is being removed doesn't exist, this will happen because of this:
https://github.com/Leaflet/Leaflet/blob/eee1a4aeddd8f7bf6172ea902e32aab97770a470/src/layer/Layer.js#L179

IMO this is a small area where the leaflet src code could probably be improved.  I don't personally understand why removeLayer is firing at all, or why its firing with an undefined layer in this particular use case.  However, a workaround for now is to do this:  in your code, anywhere after importing leaflet, but before using a VectorTileLayer,  add this:
  L.Map.include({
    removeLayer(layer: L.Layer) {
      if (!layer) return this;

      const id = L.Util.stamp(layer);

      if (!this._layers[id]) {
        return this;
      }

      if (this._loaded) {
        layer.onRemove(this);
      }

      delete this._layers[id];

      if (this._loaded) {
        this.fire("layerremove", { layer });
        layer.fire("remove");
      }

      // @ts-expect-error leaflet TS very incomplete
      layer._map = layer._mapToAdd = null;

      return this;
    },
  });

This will overwrite the Map.removeLayer method to not call stamp on smething that is undefined, thereby avoiding the code that would throw an error.
This is a hacky workaround, but it does work.  I am trying to brainstorm why leaflet code would ever get to running Map.removeLayer on something that is undefined, in this case only.  There is something under the hood of react-leaflet with createLayerComponent that may be causing this, but I'm not sure what.
If you are familiar with these things, I'm open to suggestion on what could be going wrong or how to fix it, but for now, at least you have a monkeypatch solution.

Another thought
React 18 renders everything twice when using React.StrictMode, which is a default part of a vite project (ew).  While it can actually help debug problems, in this case, I think the issue is that react is mounting and unmounting the VectorTileLayer too quickly, and the underlying leaflet layer is not being created in time.
Completely separately from the other solution I posted, removing StrictMode solves the problem for me as well.  Perhaps this is not a vite issue, but rather a react-esri-leaflet issue when using strictmode in react 18.

Thanks! removing the strictmode worked (and the previous solution too). I did notice when i ran the preview of (npm run build) by vite, the app ran without errors with the VectorTile line in the code, but the layer was still not added to the map. And running on build preview removes that behavior relating to strict mode...


Large enough pre-images not to create new seeds

Once the preimages in a PreImageCycle are all used, nodes can not enroll again with the same UTXO. So we decided that the number of Pre-Images generated when first enrolling should be large enough that there would unlikely be the need to ever re-enroll with a new pre-image seed. As discussed with the team, 5 million pre-images are created by default in this PR.
This PR has also improved the testing time from the previous PR , so needs only 20% more time for testing compared to the v0.x.x branch. I will improve more about the test time while this PR is being reviewed. The reason why I'm submitting this PR although there's room for improvement is to share the concept the setting seeds for pre-images into PreImageCycles and to get opinions for the concept earlier.
The improved code could be cherry-picked to this PR if there's no confusion.

Note that the best way to make sure this is correct would be to not modify any of the test value: That is, use the 2000th PI in the version (unittest) constructor and related.

I compared the testing time between v0.x.x and this PR by adding a third commit which prints out the testing time of each unit test and will be deleted later. This is the test result.
[Testing time increase between v0.x.x and PR #2291](Testing time increase between v0.x.x and PR #2291).
And I will improve it, which means decrease the testing time, by check the result and the perf report command that @Geod24 suggested and show me how to use.

@Geod24 Could you please look at this error as follows. It occurred by adding the third commit which is just for improving the testing time of agora.node.Ledger module and will be merged into the first commit.
Linking...
To force a rebuild of up-to-date targets, run again with --force.
Running build/agora-unittests
0   agora-unittests                     0x0000000102f68c2b _D4core7runtime9backtraceFNbPPviZi + 75
1   agora-unittests                     0x0000000102f68bba _D4core7runtime18runModuleUnitTestsUZ19unittestSegvHandlerUNbiPSQCk3sys5posix6signal9siginfo_tPvZv + 58
2   libsystem_platform.dylib            0x00007fff6f7db5fd _sigtramp + 29
3   agora-unittests                     0x000000010216957d _D5agora4node6Ledger10TestLedger6__ctorMFSQBo6crypto3Key7KeyPairAxSQCn9consensus4data5BlockQgyCQDpQBcQv6Params15ConsensusParamsS4core4time8DurationCQFq7network5ClockQgZCQGlQGiQGgQGc + 1197
4   agora-unittests                     0x0000000102169eec _D5agora4node6Ledger19__unittest_L1720_C1FZv + 348
5   agora-unittests                     0x000000010218542b _D5agora4node6Ledger10__unittestZ + 11
6   agora-unittests                     0x00000001020421c3 _D5agora4test4Base22customModuleUnitTesterFZ7runTestMFSQCbQByQBwQBuFZ7ModTestZb + 371
7   agora-unittests                     0x000000010204368f _D5agora4test4Base22customModuleUnitTesterFZ13runInParallelMFASQCjQCgQCeQCcFZ7ModTestZ10WorkThread3runMFZv + 63
8   agora-unittests                     0x0000000102f6bfbd _D4core6thread7context8Callable6opCallMFZv + 61
9   agora-unittests                     0x0000000102f6fa69 _D4core6thread10threadbase10ThreadBase3runMFZv + 25
10  agora-unittests                     0x0000000102f6cff5 _D4core6thread8osthread6Thread3runMFZv + 21
11  agora-unittests                     0x0000000102f6d5e8 thread_entryPoint + 200
12  libsystem_pthread.dylib             0x00007fff6f7e7109 _pthread_start + 148
Program exited with code -11

All green. Please review.

LGTM, I think we should raise an issue to not forget about the sleep in the unit test. Also maybe an issue for the suggested rename of parameter in PreImageCycle constructor.

Okay, I will raise issues and find out there's something to do before that.


GUI: "Amount left to select" exceeds total balance when choosing high fee

Doing some testing of Liana tonight, and saw that I can set a fee rate which leads to a wallet balance for "Amount left to select:" that exceeds my total balance.
Screenshot:

Using Liana 0.3 on a Mac

Thanks for the report. It's related to https://github.com/wizardsardine/liana/issues/117. Inputs in the Spend creation flow should be made foolproof.


Add methods for the persistent cache Agent interface

Motivation
About to use it and realized the interface could be simplified since you'd want to utilize the unique check ID in all cases
https://github.com/DataDog/integrations-core/blob/bafe92ce829645b68b69c47f73c2189188d03a42/win32_event_log/datadog_checks/win32_event_log/check.py#L252-L263

I think the key is a good way to not dump everything in a json blob


java.lang.NullPointerException: Attempt to invoke interface method 'float com.patrykandpatrick.vico.core.entry.ChartEntry.getX()' on a null object reference

Describe the bug
Version: 1.9.2 (Unable to try newer versions due to #407)
Usage:
    private val producer = ChartEntryModelProducer()

LaunchedEffect(key1 = Unit) {
    while (true) {
        producer.setEntries(viewModel.dataList)
        delay(500)
    }
}
VicoChart(producer = producer)

@Composable
    fun VicoChart(producer: ChartEntryModelProducer) {
        Chart(
            chart = lineChart(),
            chartModelProducer = producer,
            startAxis = rememberStartAxis(),
            bottomAxis = rememberBottomAxis(),
            diffAnimationSpec = snap()
        ) {
            3F
        }
    }

The dataList is being updated by a flow collector:
f.collect { data ->
    viewModel.dataList.add(FloatEntry(data.t.toFloat()/256F,data.t.toFloat()))
    while (viewModel.dataList.size> BUFFER_SIZE) viewModel.dataList.removeFirst()
}

This issue is not occurring immediately, but after around 10-15s. BUFFER_SIZE=3840
The issue occurs after ~7k data points.
java.lang.NullPointerException: Attempt to invoke interface method 'float com.patrykandpatrick.vico.core.entry.ChartEntry.getX()' on a null object reference
	at com.patrykandpatrick.vico.core.entry.diff.DefaultDiffProcessor.updateProgressMap(DefaultDiffProcessor.kt:101)
	at com.patrykandpatrick.vico.core.entry.diff.DefaultDiffProcessor.setEntries(DefaultDiffProcessor.kt:47)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.setEntries$lambda$1$lambda$0(ChartEntryModelProducer.kt:77)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.$r8$lambda$DLLZQwVnv6C3LZjvqE_A2NZ0Tws(Unknown Source:0)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer$$ExternalSyntheticLambda1.run(Unknown Source:8)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)

Module

[x] compose
[x] views
[ ] compose-m2
[ ] compose-m3
[x] core (select if none of the above apply)

To reproduce
Unsure, try rendering a timeseries data and trim it from the end to a fixed length. Render it every 500ms.
Expected behavior
No error
Screenshots
N/A
Android versions
13
Additional context
N/A

Okay looks like the issue is here:
viewModel.dataList.add(FloatEntry(data.t.toFloat()/256F,data.t.toFloat()))

There seems to be an upper bound in the y axis data here.  Not sure how this is causing an NPE in the end though. I'll see if I can add some error handlers in the coroutine and figure this out.

Update: With this case as well I am facing the same issue after quite a while. I'm not sure what's causing it, and seems hard to reproduce.

in DefaultDiffProcessor.kt:
newEntries
                .getOrNull(i)
                ?.forEach { chartEntry ->
                    map[chartEntry.x] = ChartEntryProgressModel(
                        oldY = map[chartEntry.x]?.oldY,
                        newY = chartEntry.y,
                        temporary = false,
                        chartEntry = chartEntry,
                    )
                }

and i can go upto val maxListSize = maxOf(oldEntries.size, newEntries.size) which seems like a bad idea when paired with .getOrNull(i)
Any clue why this was done this way?
I do not require any animation, can I bypass this diffProcessor? Anything I might be doing wrong? From my code the newEntries and oldEntries should have the same size of BUFFER_SIZE when the error occurs, not sure what is going on.

Yup, let’s talk there until that issue is resolved.

So now the issue I'm facing after upgrading to 1.13.0-alpha.2 is an immediate runtime error after adding a datapoint
java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:1029)
	at java.util.ArrayList$Itr.next(ArrayList.java:982)
	at com.patrykandpatrick.vico.core.entry.ChartEntryExtensionsKt.calculateXGcd(ChartEntryExtensions.kt:98)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getInternalModel(ChartEntryModelProducer.kt:111)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getInternalModel$default(ChartEntryModelProducer.kt:98)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getModel(ChartEntryModelProducer.kt:117)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.setEntries$lambda$1$lambda$0(ChartEntryModelProducer.kt:79)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.$r8$lambda$cF6wz2uV3lXuCajKiOZn2aNYLKc(Unknown Source:0)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer$$ExternalSyntheticLambda2.run(Unknown Source:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1012)

I have also modified diffAnimationSpec = null in the chart constructor.
LMK if I should open a new issue for this.

Looks like I can avoid this by updating the graph like this like I was doing initially:
LaunchedEffect(key1 = Unit) {
    while (true) {
        producer.setEntries(viewModel.dataList)
        delay(500)
    }
}

I had modified the code to update the graph right after fetching the latest values. What should be the right approach here?

Could you check if anything changes when producer.setEntries(viewModel.dataList) is replaced with producer.setEntries(viewModel.dataList.toList())?

No, I've tried that already

Got it. If so, would you be able to provide a full minimal reproducible example? We’ll have to take a closer look.

Sure, I'll create another project and get back

Thanks!

Here: https://github.com/subhashisbhowmik/VicoTestApp
The issue is there after running for around 10 seconds on pixel 7 pro emulator
Notice that I'm updating the values asynchronously
LaunchedEffect(key1 = Unit) {
                        while (true) {
                            launch (Dispatchers.IO){
                                x += 0.02F
                                viewModel.data.add(FloatEntry(x, sin(x * 2 * PI.toFloat())))
                                while (viewModel.data.size > 3080) viewModel.data.removeFirst()
                                producer.setEntries(viewModel.data.toList())
                            }
                            delay(5)
                        }
                    }

This is because my use-case has a callback notifying me when I have a new datapoint, it works fine if I discard the launch.

I was wrong, the error still occurs even in synchronous update, but it just takes a while.
                    LaunchedEffect(key1 = Unit) {
                        while (true) {
                            x += 0.02F
                            viewModel.data.add(FloatEntry(x, sin(x * 2 * PI.toFloat())))
                            while (viewModel.data.size > 3080) viewModel.data.removeFirst()
                            producer.setEntries(viewModel.data.toList())

                            delay(5)
                        }
                    }

FATAL EXCEPTION: pool-2-thread-1
Process: com.test.vicotestapp, PID: 21981
java.util.ConcurrentModificationException
	at java.util.ArrayList$Itr.next(ArrayList.java:860)
	at com.patrykandpatrick.vico.core.entry.ChartEntryExtensionsKt.calculateXGcd(ChartEntryExtensions.kt:98)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getInternalModel(ChartEntryModelProducer.kt:111)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getInternalModel$default(ChartEntryModelProducer.kt:98)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.getModel(ChartEntryModelProducer.kt:117)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.setEntries$lambda$1$lambda$0(ChartEntryModelProducer.kt:79)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer.$r8$lambda$cF6wz2uV3lXuCajKiOZn2aNYLKc(Unknown Source:0)
	at com.patrykandpatrick.vico.core.entry.ChartEntryModelProducer$$ExternalSyntheticLambda2.run(Unknown Source:4)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
	at java.lang.Thread.run(Thread.java:1012)

Thank you, @subhashisbhowmik. We’ve determined where the problem lies and are looking into it. The fix will be included in Vico 1.13.0 Alpha 4.

@patrickmichalik thanks a lot!
My earlier workaround with updating the graph every 100ms also seems to fail at a few rare occasions. Can you help me with either the ETA for alpha 4 or any other workaround?

Since ChartEntryModelProducer is at fault here, you could use the Chart overload that accepts a ChartEntryModel. You can create ChartEntryModels via entryModelOf:
entryModelOf(viewModel.data)

Vico 1.13.0 Alpha 3 comes out today. The ETA for version 1.13.0 Alpha 4 is tomorrow or the day after.

I wanted to share a quick update. The issue turned out to be more complex than we initially thought, so more time was required to resolve it. We now have a fix, and we plan on releasing Vico 1.13.0 Alpha 4 within 24 hours. Apologies for the delay.

@patrickmichalik no worries, I appreciate the effort :)

Vico 1.13.0 Alpha 4 is now available. The problem here was that multiple updates could run at once. ChartEntryModelProducer#setEntries processes updates asynchronously, but there was no mutex in place. We’ve introduced an update rejection mechanism and added several new functions, including ChartEntryModelProducer#setEntriesSuspending, which is perfect for your use case. Once you’ve updated Vico, please try the following.
LaunchedEffect(...) {
    withContext(Dispatchers.Default) {
        while (true) {
            ...
            producer.setEntriesSuspending(viewModel.data).await()
            delay(5)
        }
    }
}

Please note that this would behave differently if you were to launch a new coroutine for each setEntriesSuspending call, similarly to what you did here. Since the loop wouldn’t be suspended, an ever-lengthening queue of updates would form, which is highly undesirable. The key takeaway is that, for frequent updates, one should either ensure that they’re not queueing too many updates (which is achieved above by means of Deferred#await) or allow overlapping updates to be rejected, an example of which you can find below. In this example, withContext is used only because of the infinite loop, and if you were to omit it, there likely wouldn’t be a noticeable performance decrease. This is because setEntries launches a coroutine internally, using Dispatchers.Default by default.
LaunchedEffect(...) {
    withContext(Dispatchers.Default) {
        while (true) {
            ...
            producer.setEntries(viewModel.data)
            delay(5)
        }
    }
}

While testing this, I noticed that the chart flickers intermittently. This is a separate problem, and we’ve just finished preparing a fix, which will be included in Vico 1.13.0 Alpha 5. I’ll let you know when that’s available. If you have any questions or face any issues, please feel free to let me know.

Sounds good. Vico 1.13.0 Alpha 5, which resolves the flickering issue, is now rolling out. I enclose a screen recording.
https://github.com/patrykandpatrick/vico/assets/120058021/d712bb25-c5cb-422c-9304-d60878e0b0c9

I’ll be removing the “bug” label because we now use discussions for everything but bug reports, making the “bug” label redundant. Please rest assured that this doesn’t change anything about the bug report.

This works great! But I'm noticing a different issue mentioned in #374

I’m glad to hear that the problem described here has been resolved. I believe that by now, the solution to the issue described under #374 has been clarified, but if you have any further questions on that topic, let’s continue our conversation there.

Vico 1.13.0 is now out, so I’ll be closing this issue. Thanks!


FIFA 18  "Unknown response. Unable to login" message

I get the "Unknown response. Unable to login" message
I am trying this for FIFA 18

Me too :/ I'm also having the same problem. Please, what is the solution to access the application?

That's because the login flow for FIFA 18 changed quite a bit.
I've been working on a new version and I just got the API working (see this PR. Unfortunately I'm unable to test/compile this Electron project on my machine.

Alright, it's working on my machine now. If @hunterjm accepts the PR we can use this tool again.

Thats great news, hopefully he does!

How can I get it working on my machine? @Mardaneus86

@andresoro Mardaneus86 has a repository called futwebapp-tempermonkey. You can use this for autobuyer directly on fut web app.

@andresoro: I suggest we wait until @hunterjm does the necessary checks and some additional work to prevent you from getting banned before using this tool.
And indeed, if you really want a simple autobuyer in the web app right now (BIN snipe only for now, still in experimental phase), you can check my repo here: https://github.com/Mardaneus86/futwebapp-tampermonkey

do you have any idea as to how long the time frame will be until hunter does the checks and work to get it up and running as it is supposed to?

I've looked at it, but with EA becoming more strict on bans, I am likely going to try building it into the new WebApp directly, since it is no longer flash based.  This should help it look more "human" and overall be much less risky.
I wouldn't feel comfortable releasing the API integration as it stands today, because there is a lot of things EA does that this autobuyer currently does not do.

Thanks for the update @hunterjm. How do you plan to build the autobuyer into the webapp directly. I am interested, because it sounds awesome and efficient way of achieving it.

@hunterjm Hello and thank you,
I just want to know if I will be able to use autobuyer soon?

@Mardaneus86 are any of the feature that you currently have on you web app allow you to buy now snipe?

same issue for connection

Is this project dead then? :-(

"login2  is not constructor"


Add query to find clusters and all neighbors

@ialarmedalien
Adds query to find a gene cluster and its neighbors
Note the base for this PR is djornl-gene-search which is PR #137

FYI tweaked some stuff here to get it to work better based on manual testing


[Feature] Mock Jest assertions that test uploading to Cloudinary

Feature Request
Is your feature request related to a problem? Please describe.
We want to be able to test the functions that upload images to Cloudinary without actually uploading them.
Describe the solution you'd like
Mocking whatever functions need to be mocked in order to prevent uploads while still testing the plugin capability
Additional context
Commented out after updating to test strings for creating tests on https://github.com/colbyfayock/netlify-plugin-cloudinary/pull/30
SSee the following test cases:

should create a Cloudinary URL with delivery type of upload from a local image
should create a Cloudinary URL with delivery type of upload from a remote image

@matiasfha is this considered complete with the work you did already?

I think it does


Implement map, ap, of, chain functions for monad

I've found mistake in my understanding of chain. Code works well but logically my implementation of chain is really concat(>>) :: m a -> m b -> m b function. I try to fix as soon as fully understand chain implementation.

I will write tests which will be examples after merging #98

@DzyubSpirit you can squash and land

Landed in 0c0fda42bedd2143eab2f59e76f3e07cfa308cfd, aaf2a0215fd70c1d1762c8fded3d03fffcee4739


Update USL SDK Assembly versions

Current USDL SDK does not work with the listed DataLake SDK Assemblies.  I updated both Microsoft.Azure.Management.DataLake.Analytics and Microsoft.Azure.Management.DataLake.Store Assembly references..
With these updated references, the PackageDeploymentTool.exe works with a deploycluster command.
With the existing versions, the deployment fails with:
"Deployment failed with Method not found: 'Microsoft.Azure.Management.DataLake.Analytics.IAccountsOperations Microsoft.Azure.Management.DataLake.Analytics.DataLakeAnalyticsAccountManagementClient.get_Accounts()'."
It appears this is caused by an un-versioned USQL SDK reference..

@solidcloudio : Thanks for your contribution! The author, @yanancai, has been notified to review your proposed change.


Add support for Azure Disk Encryption

Is this a BUG REPORT or FEATURE REQUEST? (choose one): FEATURE REQUEST
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) all
Add support for Azure Disk Encryption for all disks used by an ACS cluster.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

ADE is less important than SSE (#748) since SSE enables the customer to supply their own certificates.

+1, Azure Disk Encryption is a frequently asked for feature from the MSFT partner network and it'd be great to see support for this in ACS Engine.

@anhowe anything need to do in the k8s upstream level?

@andyzhangx it may be useful to ensure PVs are setting encrypted disks.  CC @khenidak

@anhowe thx, I will put this work into my backlog.

@andyzhangx I will add this to our planning. Can you file it as an issue in upstream?

see: https://github.com/kubernetes/kubernetes/issues/57070
@khenidak it depends on azure key vault work, right?

No - Encryption is using key vault but does not depend on Kubernetes KMS interfaces. Let us setup sometime to talk about this.

@khenidak Thanks, I have figured out how to do that in upstream, would try to make it feature in v1.10.0

BTW, i have input some design details in https://github.com/kubernetes/kubernetes/issues/57070, feel free to drop some comments here.

If I understand correctly, SSE is already available, but ADE is not available yet in acs-engine, but is possible.  via: https://github.com/kubernetes/kubernetes/issues/57070#issuecomment-354244873 Is that accurate?
If so, is there an ETA for this?

we are not planning to add ADE at the moment. not for v1.11 at least

Hey was curious what is the progress of this still planned for v1.11?
Thanks everyone!

also interested in the progress of ADE - a recent pen test raised medium risk security center issues which included lack of ADE on the acs-engine deployment.


Upgrade MAAS ansible scripts for VM v2

We'll need new ansible scripts to setup K8s instead of CloudStack

In Admin repo


Tag CmdStan 6.0.2 - init file fix

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/8970
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v6.0.2 -m "<description of version>" 43b0cd86fa4898dcb375b08256908a01097c8ed1
git push origin v6.0.2


So 3rd parties may easily use the system, built a sample site that accepts the CDN asset pipeline.

Version 0.1

[ ] investigate how to tag releases in github, add branching and tagging to our CDN build: figure out a cadence
[x] publish to the cdn
[ ] build a simple jekyll example site that takes the cdn components.
[ ] update docs for outside audiences.

Simple site

[x] landing page
[ ] 404
[ ] accessibility statement
[ ] privacy policy (link to)
[ ] contact us
[ ] content page
[ ] grid layout
[ ] open layout
[ ] favicons
[ ] default social shares

Does the simple site has a Form page ?

Does the simple site has a Form page ?

@himaniravella We don't have a form template available yet. In the mean time you can go to the components site and look for the Form section there. https://chicago.github.io/cds-reference/#forms

Hi @mario-duran
Reflecting on this, I believe we'll still need a completely separate repository which references all the CDN assets to test and make sure we have the right work and right items here. I'll update this issue and make a separate one. We can have a 404, accessibility, etc. for this project, but we'll still need aa separate repo people can just clone and use with all its CDN goodness.


2.6.1: Pulsar-Client CLI consume -p Earliest option does not override default subscription position of Latest

Describe the bug
When I use pulsar-client consume and specify the subscription position (either using -p or --subscription-position) as Earliest the client still uses Latest
To Reproduce
In Pulsar 2.6.1
$ ./apache-pulsar-2.6.1/bin/pulsar-client --url pulsar://platform-pulsar-broker:6650 consume -s consumer4a -p Earliest persistent://cogito-dialog/stf/retrieve4
Warning: Nashorn engine is planned to be removed from a future JDK release
22:10:56.807 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ConnectionPool - [[id: 0xc7f51744, L:/<IP_ADDRESS>:52878 - R:platform-pulsar-broker.cogito-saas.svc.cluster.local/<IP_ADDRESS>:6650]] Connected to server
22:10:56.972 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl - Starting Pulsar consumer status recorder with config: {
  "topicNames" : [ "persistent://cogito-dialog/stf/retrieve4" ],
  "topicsPattern" : null,
  "subscriptionName" : "consumer4a",
  "subscriptionType" : "Exclusive",
.
.
.
  "subscriptionInitialPosition" : "Latest",

and
$ ./apache-pulsar-2.6.1/bin/pulsar-client --url pulsar://platform-pulsar-broker:6650 consume -s consumer1 --subscription-position Earliest persistent://cogito-dialog/stf/sometopic
Warning: Nashorn engine is planned to be removed from a future JDK release
22:16:17.871 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ConnectionPool - [[id: 0xc28a8203, L:/<IP_ADDRESS>:58782 - R:platform-pulsar-broker.cogito-saas.svc.cluster.local/<IP_ADDRESS>:6650]] Connected to server
22:16:17.987 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl - Starting Pulsar consumer status recorder with config: {
  "topicNames" : [ "persistent://cogito-dialog/stf/sometopic" ],
  .
.
.
  "subscriptionInitialPosition" : "Latest",

Expected behavior
Subscription Position default is overridden
Screenshots
See above
Desktop (please complete the following information):

OS: Linux
Pulsar: 2.6.1

This problem has been fixed by https://github.com/apache/pulsar/pull/7795

This problem has been fixed by https://github.com/apache/pulsar/pull/7795

@aloyszhang Thanks that's great news - I did search but I guess didn't find it

@aloyszhang Thanks that's great news - I did search but I guess didn't find it


[CT-1946] [Bug] dbt snapshot fails if the last line is a comment

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When making a snapshot and using the check strategy with specified columns (not all), if the last line of your snapshot is a comment, it yields
14:50:11    TrinoUserError(type=USER_ERROR, name=SYNTAX_ERROR, message="line 12:16: mismatched input '<EOF>'. Expecting: ')'", query_id=20230130_145011_02592_b7axv)
because the produced query is:
select * from (
            select col1, col2, col3 from (
select * from iceberg.dbt_robbert.my_table
-- some comment ) subq
        ) as __dbt_sbq
        where false
        limit 0

Check out the -- some comment ) subq line.
Expected Behavior
When making a snapshot and using the check strategy with specified columns (not all), if the last line of your snapshot is a comment, it yields
a working snapshot
because the produced query is:
select * from (
            select col1, col2, col3 from (
select * from iceberg.dbt_robbert.my_table
-- some comment
) subq
        ) as __dbt_sbq
        where false
        limit 0

Check out the ) subq line.
Steps To Reproduce

Configure a snapshot to use check strategy
Configure the snapshot to check_cols=['col1','col2'], not all
Make sure the last line of the snapshot is a -- comment
Run the snapshot

Relevant log output
No response
Environment
- OS: Ubuntu 22.04
- Python: 3.10.6
- dbt: 1.3.2

Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
adapter used: dbt-trino

Thank you for reporting this (and opening a PR!) @RobbertDM
This is similar to this one for incremental models:

https://github.com/dbt-labs/dbt-core/issues/6485

How we should test for this (and similar issues):

[ ] We should add a comment to the end of models in integration tests for snapshots + each of our materialization types + singular and generic tests to catch any regressions in the future

Extremely naive question -- why would these models end in comments? What's a use case? I just find it strange that adding whitespace is apparently a fix here. Not used to seeing that

It's a fair question — but also something we should support. Comments, wherever they are, should work.

We should add a comment to the end of models in integration tests for snapshots + each of our materialization types + singular and generic tests to catch any regressions in the future

During BLG:

We should add a test like this. A model with a comment at the end, every materialization, every incremental_strategy, every adapter, every day of the week.
Neat chat with @colin-rogers-dbt about how we might support property-based or "matrix"-style testing. This feels like a good example, and maybe we'd want to spike an experiment with pytest_matrix

Extremely naive question -- why would these models end in comments? What's a use case? I just find it strange that adding whitespace is apparently a fix here. Not used to seeing that

For me, I had a post_hook that I didn't want to run, but also wanted to keep somewhere. I just moved it to the end of the snapshot and commented it out. That broke things in an unexpected way, and it took me a while to figure out where the problem was. If this is fixed, we prevent people from going through the same struggle in the future.
Whitespace indeed is seldom a fix, but in this case, -- is valid for only one line, so adding whitespace transforms ) subq from a comment to actual code.

Makes total sense. I knew I was just lacking imagination and I appreciate you filling me in!


Fix spurious duplicate symbol in Microsoft.EntityFrameworkCore.Design

Thanks to help from Michal I have discovered that two structurally
different methods on instantiated types can have identical textual
representation as the type / method definition can contain references
to different generic argument indices that just happen to resolve
to the same types in the instantiated entity. Based on Michal's
suggestion I have changed context method formating to use the
NameMangler formatting methods that take care of this issue.
Thanks
Tomas

@dotnet-bot please test this

@dotnet-bot please test OSX10.12 Debug and CoreFX tests

@dotnet-bot please test OSX10.12 Debug and CoreFX tests

@dotnet-bot please test OSX10.12 Debug and CoreFX tests


Generalize the page_preivew template page to allow chaptered content to be included.

Coverage decreased (-0.09%) to 64.655% when pulling b25b6095321eedf84c265d38460cfcd364bbddd4 on master into abd85ffa50d3ffed9f6f359b3252d8187bbcaeef on production.


Highlighting acronyms

Describe the bug
Syntax highlighting issues when writing acronyms in VS Code
To Reproduce
Steps to reproduce the behavior:

Go to VS Code
Build a Concerto model with acronyms as enumerated types
See lack of highlighting

Expected behavior
Acronyms should be highlighted in the same way as any other enumerated type
Screenshots

Desktop (please complete the following information):
VS Code 3
MacOS

Not to my knowledge @rajatrawataku1 - it's yours!

Moving this back to open after 7 days.

can I take this one ?

@whitehawk0011 any progress on this?

@irmerk can i work on this issue?
PS: i have already setup the repo

is there any sample repo to test the extension?

@peterhunn can you please provide the steps to reproduce the bug and give the exact data model to test on? Thanks

@peterhunn can you please provide the steps to reproduce the bug and give the exact data model to test on? Thanks

@adrijshikhar

Go to VS Code
Build a new Concerto model with any enumerated types with a hyphen e.g. CC-BY
See lack of highlighting

I tried to build a new Concerto model with enumerated types with a hyphen, and I noticed one more thing. If the enumerated type does not have a small character, the syntax highlighting does not take place. Is this supposed to happen, or its a bug? Correct me if I am wrong.

I tried to build a new Concerto model with enumerated types with a hyphen, and I noticed one more thing. If the enumerated type does not have a small character, the syntax highlighting does not take place. Is this supposed to happen, or its a bug? Correct me if I am wrong.
@jeromesimeon

I believe this is not a valid CTO File (I don't think the parser allows - in enumerated names. So no I don't believe the lack of highlighting is a bug.
However, there should be a CTO parsing error: we should open an issue about that if it isn't properly reported by the VSCode extension.

Also: lifting this back to the original issue, I don't think this has anything to do with acronyms, just we don't allow - in enums.

The steps to reproduce says, Build a new Concerto model with any enumerated types with a hyphen e.g. CC-BY. Is this different from what I have created? Please correct me if I am wrong.

However, there should be a CTO parsing error: we should open an issue about that if it isn't properly reported by the VSCode extension.
@jeromesimeon I was making changes to a sample Concerto model, then it gave the error. So I thought I should try with a new model. That's why I made a test one.

However, there should be a CTO parsing error: we should open an issue about that if it isn't properly reported by the VSCode extension.
@jeromesimeon I was making changes to a sample Concerto model, then it gave the error. So I thought I should try with a new model. That's why I made a test one.

As I said, I don't think CC-BY is a valid name for enums. We do not need to provide syntax highlighting for those, but we should make sure the error is reported (it seems like it is?).
I would close this issue as "invalid".
@peterhunn Any thoughts about this?

@jeromesimeon if that is the correct technical approach I am fine with that, but would we always want that in models? What would the appropriate delineation b between valid and invalid?

@jeromesimeon if that is the correct technical approach I am fine with that, but would we always want that in models? What would the appropriate delineation b between valid and invalid?

@peterhunn That's a really good question. There is a syntax for CTO models which decides what is valid or invalid. At the moment - is not a valid character in identifiers. So CCBY is ok but CC-BY is not.
This is quite a common since you would quickly get into ambiguities in the logic if you allowed -: would CC-BY be an identifier or mean "CC minus BY" ? Attempting to change that would be something we have to tackle in Concerto itself (and Ergo).
My observation in this issue is that this isn't about syntax highlighting. The syntax highlighter should highlight properly valid models (and clearly indicate errors in the model). I hope that makes sense.

Closing this issue. I will open a new issue around having localizable display names for enums.


Fixing some frontend issues.

Still. the height issue is there. I'll fix this issue.

Issue fixed. Kindly review it.

Issue fixed. Kindly review it.

Thanks for your contribution.
After completion @rahul-choudhury  will review then I'll merge.
So kindly inform when this issues will completely resolved.

looks good 👍

Hey @partha7978 , since we are using yarn in this project so package-lock.json is unnecessary & you are dealing with CSS files only so yarn.lock should not be modified.
So kindly request to you please remove package-lock.json & restore yarn.lock file in your next commit or the final commit.
Thanks

All margin and width issues have been solved.

I removed the package-lock.json and restored the yarn.lock as per your instruction.

Hey @d-shaktiranjan, I tried to fix the width issue on the large screen. you can check and tell me whether it's fixed or not!!

Thanks @partha7978 for your contribution.
😊


Can't Adjust Project in Exercise 0

If the user has just created their Trial account and has no Build Code Projects there is nothing in the Dev Space to edit in Exercise 0. You have to perform Exercise 1 and then come back and do Exercise 0.

Hi Thomas,
I edited the exercise 0 and added the steps to create a dev space and then add extensions to it. Please review.


can't run

os: void linux
shell: zsh
i can run the program and when, i but it on my path, but on runing it nothing done when trying to run the command of verification of install i try to run the command alone it output [].

Sorry for the delayed reply. What is your desktop environment?


Validation errors visible on second visit

I noticed if you try to log in with an incorrect password, navigate away from the login page, and then back to it you'll see the previous validation error for a split second. I first noticed that in my own app but the described behavior can also be observed in the demo app.
Is there any way to fix this?
Cheers

Hey, @martin-ro
That's because Turbo will first show the page from the cache while it fetches a new version of the page, then replaces it. If you don't want certain items to be stored in the cached HTML (such as flash messages), make sure you annotate them with data-turbo-cache="false". You can also manipulate the DOM right before it's cached by listening to the turbo:before-cache and, say, close a modal that is open or remove an invalid CSS class from form elements, things like that. See the docs.

Thanks, data-turbo-cache="false" seems to do the trick in this case.


Use DB Transactions - modify SQL data

Changes

Added more data to the animals table.
Added a species column to the animals table.
Wrote SQL transactions for the data on the animals table as follows:

1.

2. Digimon and Pokemon classification

3. Delete and rollback

4.

5. Animals count

6. Never tried to escape

7. Average weight of animals

8. Most escapes - neutered / unneutered

9. Minimum and maximum weight of each type of animal

10. Average number of escape attempts per animal type of those born between 1990 and 2000

Hi @Owusu-Desmond , if you look at the schema.sql file at the bottom most file, you can see that a new column species is added to the animals table.
I'm not sure if there is anything else there than requires a change. Please confirm.


Strange behavior with aws_health_event and regions

Describe the bug
If I have a connection in aws.spc like so:
connection "my_aws" {
  plugin  = "aws"
  profile = "my-aws"
  regions = ["us-east-1", "us-west-2"]
}

I am able to test the connection by querying for EC2 or RDS instances. Everything works great and I'm very impressed with steampipe so far.
When I query the aws_health_event table
select * from my_aws.aws_health_event
an empty table is returned. The only way I can seem to get this working is to set aws.spc region to be:
regions = ["*"] aka all regions.
now when I run the sql query it will return results. unfortunately both the aws_health_event and aws_health_affected_entity tables will return the region as "global". When I query this api directly from aws using
python / boto3 a proper region is returned. is returning "global" for all events the desired behavior? it seems like a bug.
Also setting my aws.spc to * for regions has an unintended side effect. if I run a simple query for EC2 and RDS instances I will run into error messages since I do not have permissions to regions we do not use.
To summarize:

I need to be able to query the health table while having the correct regions setup in my .spc file.
I need the results of the health table to have the correct region

Steampipe version (steampipe -v)
v0.23.3
Plugin version (steampipe plugin list)
hub.steampipe.io/plugins/turbot/aws@latest 0.145.0

Hello, @wesley-staples,
I apologize for any inconvenience this may have caused.
Based on my understanding, AWS Health is a global service. According to Steampipe's table development standards, for global services or resources, the region column should reflect the value as global. Additionally, every Steampipe table should include a region column.

I need to be able to query the health table while having the correct regions setup in my .spc file.

In the aws_health_event table, we use the DescribeEvents API to list available events. The supported endpoints for this API are us-east-1 and us-east-2. If these regions are set up in the connection config, you should be able to retrieve the relevant results.

I need the results of the health table to have the correct region

I noticed that the API response includes a Region property, which specifies the AWS region where the event occurred. This column wasn't originally included in the table due to a potential naming conflict. However, I've now added a new column named event_region in this PR to populate the Region property from the API response.
Additionally, in the current table setup, the region value can be derived by extracting it from the arn column. For example:

Table: aws_health_event
select
  arn,
  split_part(arn, ':', 4) as event_region
from
  aws_health_event;

Table: aws_health_affected_entity
select
  arn,
  split_part(arn, ':', 4) as entity_region
from
  aws_health_affected_entity;

Note: We have not added any new column to provide region information in the aws_health_affected_entity table because the DescribeAffectedEntities API does not provide any region details in its response.
I hope this update helps you in obtaining the necessary region details.
Thank you!

Thank you for your detailed a fast reply. The split_part suggestion you made works perfectly until the event_region column gets adde to the table. Thanks again for the fast reply.


Frozen caret/pointer/cursor.

With:

Node v4.0.0
Vantage 1.5.1

Below I typed foo with everything going fine...

...I then click the left arrow three times, all the while the caret/pointer/cursor remained still. Whenever I press a key, the input appears where I'd expect but the caret/pointer/cursor remains at the end.

I hope the development with this and Vorpal is working out!

Thanks. Just did a Vorpal update that fixed some of these things, so I should push it to Vantage shortly.


fix(table): add better stateful table default prop checks

Summary

Prevent a a console error from being thrown if a consumer doesn't specify callback actions.

:tada: This PR is included in version 1.20.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.20.2 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


add a CmdFunc function

Here is a little helper function that I would find useful to have in bubbletea:
func CmdFunc(msg tea.Msg) tea.Cmd {
    return func() { return msg }
}

It is very similar to http.HandlerFunc and serves a similar purpose, I think.

Hi there! Curious, what's your use case for this? If it's to send messages to another part of the program (say, up to a "parent" model) you technically wouldn't need to do this since data flows downward.
Also, assuming you meant this, right?
func CmdFunc(msg tea.Msg) tea.Cmd {
    return func() tea.Msg { return msg }
}

@meowgorithm for my first application, my main model contains a stack of models. The idea is that Update and View are delegating the work to the top-most model of the stack, appart from a few navigation messages that allows to push or pop models from the stack.
// Update takes this model and push it on the stack
type OpenMsg tea.Model

// Update removes topmost model from the stack
type CloseMsg struct{}

// some model Foo

func (f Foo) Update(tea.Msg) (tea.Model, tea.Cmd) {

    // some condition where we want to open model Bar
    bar := OpenMsg(Bar{}) // my new model to display
    return CmdFunc(bar) // send the model back to the Update loop
}

As I find myself turning a tea.Model into a tea.Cmd, I thought it would be useful to have this helper function. Now, maybe I'm approaching the problem the wrong way, and I shouldn't have to do that ... In which case I'm eager to be corrected! :)

So logic dictates that you shouldn't need to use a Cmd to simply send data to different parts of your application because that data already exists in the very Update from which you're returning the Cmd.
That said, while this is probably fine to use in practicality (we see it every so often) it does incur an unnecessary loop through the runtime. Because of that, we'd prefer not to include it in the core. In other words, it's techincally an antipattern, and actually a common one seen in The Elm Architecture, the design upon which Bubble Tea is built.

So logic dictates that you shouldn't need to use a Cmd to simply send data to different parts of your application because that data already exists in the very Update from which you're returning the Cmd.

Thanks for your input! I think I oversimplified my example, and in that case CmdFunc is effectively useless. I'll try to do better this time.
// main model
type Main struct {
    stack []tea.Model
}

// first sub-model
type Screen1 struct {}

// second sub-model
type Screen2 struct{}

In Main.Update, messages are passed to the top-most model in the stack, appart from special messages to push/pop models on the stack.
Now, Let's say Screen1 is the top-most model in the stack. Following an event, some code in Screen1.Update creates a Screen2 model which should be pushed to the stack. So, I would say the data exists in Screen1.Update, but not in Main.Update, right?
Or am I creating components, and I should avoid doing that, as ELM's documentation suggests?

Hey @tgirod when you say data I'm assuming you mean Screen2 and all its data?
Typically what you'd want to do here is manage the state of the program in the main model, then change what's being shown from View based on the main model's state. In this case you would want to control the creation of new screens in your main model's Update. If the new Screen2 is created while you're looking at Screen1 don't worry, you can still handle the tea.Msg in the main Update and just trigger the tea.Cmd from your Screen1 Update. I hope this answers your question. Please let me know if not, and I'll be happy to try again :smile:


Enforce Bold Font Style for Noto Sans

Prevents the Regular Font Style being selected when Noto Sans fonts are previously installed.

ty


36 implement inventory unit tests

The tests pass the build tests now just want to merge them into our main feature branch :)

lgtm

0 should probs be the last key and 1 should should be the first. Also if you are open to improving the code to switch I have a few suggestions :)
Instead of having ten switch statements you could instead check if it is a number, that is if keycode is between 7 and 16 (inclusive), and then to set it just adjust these values down to properly align with the indexing of the hotbar. It should be something like -8 off of keycode and then if the keycode pressed was 0 or in this case if keycode is -1 add 9 to it.

Agreed that 0 should be last and 1 should be first, it's a negative UX design choice since 1 is the first key on the keyboard whereas 0 is last.
@adamFittlerUQ any chance you can resolve this?


Fix/invalid calc parsing

This PR adds better handling of invalid calc definitions.

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 4

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2
- Added 7

Complexity increasing per file
==============================
- lib/Sabberworm/CSS/Value/URL.php  2
- lib/Sabberworm/CSS/Value/CalcFunction.php  4

See the complete overview on Codacy


Fix possible race condition in node cleanup

Fixed #92
I was unable to come up with a regression test for this issue. It should be doable though but requires some multithreaded synchronization...

Cool ! Looks like both a good explanation and solution
However, I'm still a bit confused on one point (but maybe/probably it doesn't change anything on how the thing works, and would only make things more complicated). But just to write it out:

the mark_free_when_finished doesn't make sens for AudioParams as they are (and should) never (be) finished until their related AudioNode is dropped
therefore, would it make sens (or be possible) to have a kind of special implementation of ContextRegistration::Drop that wouldn't try to mark_free_when_finished when the AudioParam is dropped (as we know it will be dropped with the AudioNode itself)?

Anyway, beside aesthetic problems, my main concern with this solution is that it could possibly hide another strange unexpected edge-case because nothing can break anymore, so just in case I think it would be nice to just throw some hardcore panic! on the else side.

I see your point, but it would require the AudioContextRegistration to know if they belong to an actual AudioNode or an AudioParam. Therefore we would need to add a boolean is_param or something. To fill that value, the BaseAudioContext::register function needs to be changed to pass that info. This function is user facing (as you need it for custom AudioWorklet implementations), and that would mean the user could set it erroneously. To prevent that, we would need to separate register into register_audio_node and register_audio_param but I think we are overcomplicating stuff now
Not sure if there is a more elegant solution

Ok, that was my impression but I preferred to have your confirmation, no need to overcomplicate things I agree.
(...and ok...

Alright!


swift compile error (custom toolchain)

When I try to build an ios app on Xcode, I get the error below.
Could not parse Swift versions from: Swift version 5.9 (swift-5.9-RELEASE)
I checked the version of custom toolchain.
% /Library/Developer/Toolchains/My.xctoolchain/usr/bin/swift --version
Swift version 5.9 (swift-5.9-RELEASE)
Target: arm64-apple-macosx13.0

Below is the version of the Xcode's original toolchain.
% swift --version
swift-driver version: 1.87.1 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

The options for compiling the toolchain are as follows.
utils/build-script --skip-build-benchmarks --skip-watchos --skip-tvos --swift-darwin-supported-arch=arm64 --sccache --release-debuginfo --swift-disable-dead-stripping --install-destdir=/Users/kei/111/swift/utils/swift-nightly-install --install-llvm --install-swift --install-lldb --install-llbuild --install-swiftpm --install-swift-driver --install-swiftsyntax --install-playgroundsupport --install-sourcekit-lsp --install-swiftformat --install-swiftdocc --build-swift-static-sdk-overlay --darwin-toolchain-display-name=CodeLabyrinth --darwin-toolchain-display-name-short=CodeLabyrinth --darwin-toolchain-name=CodeLabyrinth --darwin-toolchain-version=1.0 --darwin-toolchain-alias=Local --darwin-toolchain-bundle-identifier=CodeLabyrinth --darwin-toolchain-require-use-os-runtime=0 --install-prefix=/Library/Developer/Toolchains/CodeLabyrinth.xctoolchain/usr --install-symroot=/Users/kei/111/swift/utils/swift-nightly-symroot --darwin-install-extract-symbols ‘--swift-install-components=autolink-driver;back-deployment;compiler;clang-resource-dir-symlink;libexec;stdlib;sdk-overlay;static-mirror-lib;toolchain-tools;license;sourcekit-xpc-service;swift-remote-mirror;swift-remote-mirror-headers’ ‘--llvm-install-components=llvm-ar;llvm-cov;llvm-profdata;IndexStore;clang;clang-resource-headers;compiler-rt;clangd;dsymutil;LTO;clang-features-file’ --swift-primary-variant-sdk=IOS --installable-package=/Users/kei/111/swift/utils/CodeLabyrinth.tar.gz --symbols-package=/Users/kei/111/swift/utils/CodeLabyrinth-symbols.tar.gz --build-subdir=buildbot_osx  --ios --tvos --watchos --swift-stdlib-build-type=Release ‘--llvm-targets-to-build=X86;ARM;AArch64’ --swift-darwin-supported-arch “$(uname -m)”

Am I missing something?

Maybe you can try utils/build-toolchain script.

if you use build-script , add "Apple" in version string.

Maybe you can try utils/build-toolchain script.

@WindowsMEMZ Do you happen to know which command in build-toolchain is responsible? We use custom build-script based buildsystem and encountered the exact same issue

complier-vendor=apple is the reason

Maybe you can try utils/build-toolchain script.

@WindowsMEMZ Do you happen to know which command in build-toolchain is responsible? We use custom build-script based buildsystem and encountered the exact same issue
grepping through Swift sourcecode doesn't seem to show where that error comes from or the regex used for the version detection

build-toolchain actually calls the build-script inside. You can open this script by text editor to see how it works.


Please Make the download option work in more cases

There are too many limitations to this feature.
We need to be able to download a report to pbix in most of the cases listed in the "limitation" section:

when originally created in the Power BI service
after deployment (ALM).
Power BI report based on a dataset in one workspace and publish to a different workspace
Not just the original report. Any copy of the report.

The current limitation is really hampering our day-to-day work and I don't quite see the technical hurdles preventing these cases to be covered.
one typical example is a business user has built a set of reports online (because of the convenience and ease of doing so) and now wants the "experts" to integrate all he's done in a managed set of reports. -> everything has to be redone from scratch, which is very inefficient and time consuming.
thank you,
françois.

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

ID: e091669c-6d15-1d87-9d1b-87720f50a908
Version Independent ID: 2989dde3-eef4-28ea-4eec-846efc140735
Content: Download a report from the Power BI service to Power BI Desktop - Power BI
Content Source: powerbi-docs/create-reports/service-export-to-pbix.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @frgaude.
This looks like product feedback or a product question, rather than documentation feedback. You can submit product feedback or feature ideas by going to Power BI Ideas.
You can also engage with the Power BI engineering team by being active in the Power BI Community.


bug: invalid log level causes service check to fail

may appear with a log like:
warning: invalid logging spec 'info"', ignoring it

notice the " there

Tested during #124 but it does not seem to break anything, closing.


added my fav css tools

added some css stats / metric tools

Whoa. Thanks so much @creinartz! A lot of great tools :cocktail:
@andygrunwald motivating people as always.


Add external-dns integration

What does this PR do?
Adds the external-dns integration (grabs the metrics from prometheus)
Motivation
I need to follow the external dns metrics of my kubernetes platform, so instead of having to go to prometheus, I'd rather have everything in Datadog.
Testing Guidelines
It's the standard basic techniques. The check and tests are really simple
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

Thanks for the PR, @davidgibbons! integrations-extras is a community-driven repository for integrations written and maintained outside Datadog. While support is on a best-effort basis, we're happy to help with code reviews and testing. The integrations won't be bundled with the agent, but will be installable on an individual basis.
With that in mind, would you be interested in being the initial maintainer for this integration? You'd be responsible for general code maintenance along with keeping an eye on PRs and issues. There's no specific time or duration commitment, but we do ask you only agree to become the maintainer if you feel it's something you'll be able to do for the foreseeable future. If that sounds good to you, would you mind re-opening this PR on https://github.com/DataDog/integrations-extras?
If you have any questions, let us know.

I'm surprised you guys don't want to have that in integrations-core. That's kind of a really really common k8s tool from the kubernetes incubator @jeremy-lq .
Any specific reason why you don't want that in integrations-core?

@davidgibbons @aerostitch Hello! We have decided to accept this as an official integration and will review this soon.

Hi @davidgibbons, this PR just need a couple of minor changes. Will you have the time to address them?

Hi @davidgibbons, this PR just need a couple of minor changes. Will you have the time to address them?

Hi @davidgibbons, this PR just need a couple of minor changes. Will you have the time to address them?

Sorry about that, updates made.

@davidgibbons Great job! I pushed a small refactor.
Also, I changed the orientation of external_dns.registry.endpoints_total and external_dns.source.endpoints_total from -1 to 0 per https://docs.datadoghq.com/developers/integrations/new_check_howto/#metrics-metadata-file. Do you agree with that or should we change that back?

@ofek  That orientation change makes perfect sense.

Thanks @davidgibbons 💯


mediacheck: trap refactoring

As a followup to PR #2178 this PR fixes the case that in manual runs the cleanup trap would not run.
This PR introduces a variable called $traps that holds function names that will be called by the trap.
One can add and remove functions to the array $traps as needed.

@rsalevsky there are two jt_sync calls, one with ${project},${subproject},${BUILD_NUMBER} and the other with ${JOB_BASE_NAME},${project},${BUILD_NUMBER} - that does not look right - which one is the correct one?

@bmwiedemann Without looking at it I would guess the more recent one but that would be a Trainee task. @nkrinner

https://github.com/SUSE/cloud/commit/c43dc0bde4f7459e0d554c622e8ff2b030e2ec97 achieves the same.
Did you test that the exit code is still propagated? in previous attempts at adding a trap we had the issue that jenkins didn't notice the failure anymore because the overall exit code was always zero.

Closing in favor of PR #2181


Battery issue

When I first got the board, I plugged in USB and played with the demo. I then left it on the clock screen with only the battery connected, to test how long it would run that way. I have a standard 1100mAh lipo battery plugged into the board.
However, after flashing the board with new code, it shuts down when I disconnect USB, even though the battery is plugged in. I've tried a different (identical) battery, and it doesn't work either, though they work in other boards.
With only the battery plugged in, I read around 4V on the 5V pin, and 3.3 on the 3V pins, so the battery is definitely providing power.
I've looked through all of your code and can't find anything related to different behavior when on battery, so I don't think it's a software issue.
Any idea what could be happening?

Hi, excerpt from my LilyGO T-Display S3 startup Repo:
https://github.com/teastainGit/LilyGO-T-display-S3-setup-and-examples
Common problem:
C) Can run on USB power but not battery connector:
Add #define LCDpin 15		// just before the setup and then in setup add:
pinMode(LCDpin, OUTPUT); 	//"triggers the LCD backlight, and enables battery power
digitalWrite(LCDpin, HIGH);)	//on startup"
(LilyGO variously refers to them as "LCD power on" OR "PIN_POWER_ON")
Thanks to user RobLatour for finding this cure for the battery issue!

That solved it! Thank you so much!


Add conditions field to cell status

Add conditions field to cell status

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1fc94b7). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #36   +/-   ##
========================================
  Coverage          ?   58.4%
========================================
  Files             ?       4
  Lines             ?     113
  Branches          ?       0
========================================
  Hits              ?      66
  Misses            ?      47
  Partials          ?       0

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 1fc94b7...3bcab4b. Read the comment docs.


Bugfix: support empty buffers in from_buffers

ak.from_buffers fails to reconstruct an array when the NumpyForm has a zero itemsize. This PR fixes this by only performing a length check if itemsizeis nonzero, and taking the leading dimension from the givenlength`.
Fixes #1007

In principle, the NumpyForm constructor should complain about itemsize <= 0, or even any itemsize that disagrees with the data type. (There are a lot of redundancies in v1 NumpyForm/NumpyArray's dtype handling, in large part because I discovered platform dependencies in the Python buffer's format after development was well underway.) The v2 constructor and from_json don't ask for the itemsize, since it can be derived from dtype.
Form JSON with "itemsize": 0 is not legal, though I suppose the check against it hadn't been implemented.

In principle, the NumpyForm constructor should complain about itemsize <= 0, or even any itemsize that disagrees with the data type. (There are a lot of redundancies in v1 NumpyForm/NumpyArray's dtype handling, in large part because I discovered platform dependencies in the Python buffer's format after development was well underway.) The v2 constructor and from_json don't ask for the itemsize, since it can be derived from dtype.
Form JSON with "itemsize": 0 is not legal, though I suppose the check against it hadn't been implemented.

Ah, I'm not being clear enough in the discussion here - itemsize is referring to the dtype.itemsize, which counts the size of the inner sub array. That can be zero, if any of the inner dims are zero.

If we're talking about a dtype's itemsize because some element in dtype.shape is zero, that's supposed to be captured in the inner_shape. (The inner_shape is exactly the dtype.shape; in other words, the array's shape[1:].)
A zero could be hidden in the inner_shape and could lead to an untested error. It seems you've found one, then.

Yes, this is what I'm talking about. Given that it's legal for NumPy arrays to have such a dtype (or at least, be described by one), the only error here is that we currently implicitly expect the provided buffer to have non-zero length. This assumption fails in the case that to_buffers was called with something like np.zeros((3, 0)).

I think this is ready to ship :rocket:, unless you have any style concerns.

It's totally legal for a NumPy array to have zero size due to a zero-length dimension hidden somewhere in its shape.
Since you've given me the go-ahead and tests pass, I'll merge this now.


gitlab: 15.11.3 -> 15.11.5

Bumping the 15.11 release for now, as GitLab 16 comes with some breaking changes that need to be implemented.
Description of changes
https://about.gitlab.com/releases/2023/05/19/gitlab-15-11-5-released/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I better go to sleep m)

Still needs a backport for 23.05, and ideally also backport whatever is causing the conflict.


Trying to access other libs in release mode

RN Native : 0.59.8
RN Share Extension : 2.0.0
I am trying to send images to my main app using deep linking, it works great in debug but I am having an issue when releasing.
This is the logs I am getting when I trigger the share action :
2019-07-27 21:39:12.937441+0200 MyExShare[40338:9750890] Failed to inherit CoreMedia permissions from 40329: (null) 2019-07-27 21:39:13.411 [error][tid:com.facebook.react.JavaScript] null is not an object (evaluating 'o.SIGN_IN_CANCELLED') 2019-07-27 21:39:13.413575+0200 MyExShare[40338:9750899] null is not an object (evaluating 'o.SIGN_IN_CANCELLED') 2019-07-27 21:39:13.417 [fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: null is not an object (evaluating 'o.SIGN_IN_CANCELLED') 2019-07-27 21:39:13.418 [error][tid:com.facebook.react.JavaScript] Module AppRegistry is not a registered callable module (calling runApplication)
So it looks like it's trying to access react-native-google-signin which I am using in my main app. But I have no idea why it's trying as I thought I separated correctly my entry files. I have a separated share.ios.js file :
import {AppRegistry} from 'react-native'; AppRegistry.registerComponent('MyExShare',() => require('./Share').default)
And this is my Share.js:
import React, { Component } from "react";
import Modal from "react-native-modal";
import ShareExtension from "react-native-share-extension";

import { Text, View, TouchableOpacity, Linking, Alert, Platform } from "react-native";

function JSONtoBase64(json) {
  var Buffer = require("buffer/").Buffer;
  return Buffer.from(JSON.stringify(json)).toString("base64");
}

export default class Share extends Component {
  constructor(props, context) {
    super(props, context);

  }

  async componentDidMount() {
    const data = await ShareExtension.data();
    if (Platform.OS === "ios") {
      const RNFetchBlob = require("rn-fetch-blob").default
      const appGroupPath = await RNFetchBlob.fs.pathForAppGroup("group.org.myapp");
      const filename = data.value.replace(/^.*[\\\/]/, "");
      const destination = `${appGroupPath}/${Math.random().toString(36).substring(7)+filename}`;
      await RNFetchBlob.fs.cp(data.value.replace("file://",''), destination);
      data.value = destination;
      const photos = JSONtoBase64(data);

      ShareExtension.openURL(`myapp://gallery/upload/${photos}`);
    } else {
      const photosAndroid = JSONtoBase64(data);
      Linking.openURL(`myapp://gallery/upload/${photosAndroid}`)
    }
    ShareExtension.close();
  }

  render() {
    return (
      <View/>

    );
  }
}

I have the following libs linked to MyShareEx :

I am trying to understand what makes it work in debug versus release... Is there a difference in the way bundles are generated ?
I'd appreciate any tips :)

@kpfefer were you able to solve this? I'm facing the same issue...
working in debug but causing these errors in release

@kpfefer were you able to solve this? I'm facing the exact same issue.
working on debug but shows these errors in release mode...

@sahildeliwala I was not able to fix it but I chose an other implementation.
In my case I just wanted to redirect to the main app using deep linking and not display anything. So I wrote my own share extension using swift to do that. I am still using this extension to handle Android though.

@kpfefer  can you show example how you did it for ios?

@NikitaPFE I am using this code : https://stackoverflow.com/a/44499222/995349
Just made a few tweaks to it for my personal case (encoding data to base64 and passing it to the URL)

use react-native-file-share-intent


Separate Repo for ADR Website

CC: @GordonBeeming @jernejk
Currently, publishing Log4Brains creates a next.js website which is published to the gh-pages branch.  While this is a simple option, it does open up the possibility of this brain being merged to main in which would be catestrophic.
Acceptance Critieria

Investigate if we should default to a branch or separate repo for the ADR website
If we stick to the current approach, document in the readme how to configure a separate repo for the ADR website.

You can publish to github pages without pushing to a branch - its the new suggested approach.
See more here
https://github.com/actions/deploy-pages
I've done this on my own site also: https://github.com/Hona/VerticalSliceArchitecture.Documentation/blob/main/.github/workflows/deploy.yml


Modify assertion to allow for data sessions

Resolves #516
Signed-off-by: Michael Casadevall<EMAIL_ADDRESS>

Thanks for spotting this! Can you change the check to actually use OWR_IS_SESSION?

Fixed.

Looks like you changed the wrong function?

And this is the part where I bury my head in the sand, and remember the golden rule of don't git commit when tired.

Committed, thanks!


Question: css-loader photon.min.css causes error during browserify

Hello,
I'm trying to integrate react-photonkit in my js app using grunt-browserify. Everything works fine, except one error:
>> Error: Cannot find module '!!./../../../css-loader/index.js!./photon.min.css' from 'D:\Dev\Projects\coaching\yo\node_modules\react-photonkit\dist'

I couldn't find any photon.min.css anywhere, but even adding an empty css file didn't solve the issue.
I'm not at all familiar with the syntax with the exclamation marks, so I don't really know how to investigate.
Something that may be worth noting though is that running npm install doesn't install css-loader module. I tried to install it independently, but with no avail.
Moreover, running "cd ./../../.." from yo\node_modules\react-photonkit\dist goes back to `yo, and not node_modules. Changing that to ./../.. doesn't solve the issue however.
Commenting out the portion about css-loader fixes all issues.
Would you have any pointer that would help me figure out what is happening here?
Thanks for your help,
Sébastien

Sorry for the late replay. :sweat_smile:
I will investigate.

hey... i'm finding the same... can you put together a simple example of using this that doesn't use Electron? I'd love to use this in a new project, but am a bit new to the tooling that surrounds using react, etc. thanks!

This worked for me if I installed it from npm. I was trying to use it from the git repo.
$ npm install react-photonkit

@bradparks
Thank you for the information.
@sebastientromp
As mentioned above, please put a simple project if not solved yet.

and it may get merged, but here's the simple example I had for doing this as a Pull request, in the "example" folder.
https://github.com/react-photonkit/react-photonkit/pull/19

                 if(!content.locals) {

102                 /*      module.hot.accept("!!./../../../css-loader/index.js!./photon.min.css", function() {
103                                 var newContent = require("!!./../../../css-loader/index.js!./photon.min.css");
104                                 if(typeof newContent === 'string') newContent = [[module.id, newContent, '']];
105                                 update(newContent);
106                         });
107                 */}
If I comment these in photon.js ,  the problem looked  like fixed!


preparing 0.93

it's been a month since the last release so it's time to get another release out the door, particularly since there's a new fix in there (#1541)
merged prs in milestone
biggest features that i plan to highlight

label module for typed label selectors via #1539

there are more discussions on future evolutions of this i.e. #1544 but not going to wait for that

prelude for ext trait blanket importing via #1527

i'll prep some release notes herein by tonight, and probably do a release tomorrow.
Highlights

A new core::labels module for creating typed label selectors for  ListParams or WatchParams. Can be constructed with the native LabelSelector, or directly from Selector / Expression. Via #1539.
A new optional prelude module for extension traits to simplify imports. Via #1527

started doing it and it failed half-way through again, this time for a rejection of cargo categories...
error: failed to publish to registry at https://crates.io

Caused by:
  the remote server responded with an error (status 400 Bad Request): The following category slugs are not currently supported on crates.io: configuration

  See https://crates.io/category_slugs for a list of supported slugs.

alright, fixed manually by:

removing the broken category https://github.com/kube-rs/kube/commit/5b3b73d1b8c4020e10269224091710c3541d3e8a
resuming publishing via cargo publish in directories that had not yet published (didn't have to yank anything).
manually sign / annotate a new git tag; https://github.com/kube-rs/kube/releases/tag/0.93.0 since we bailed mid cargo-release

maybe there's an easier way to resume here, but closing for now, release notes will be live in a few minutes.


helm  lifecycle not supported by catalog

What kind of request is this (question/bug/enhancement/feature request):
BUG
Steps to reproduce (least amount of steps as possible):
helm provides the lifecycle hook using annotations. I wrote a chart containing a job to initiate the DB.
the job is with annotations  "helm.sh/hook": "pre-install". it works in helm but it doesn't work in rancher
catalog.
Result:
Other details that may be helpful:
Environment information

RANCHER 2.0.8
Installation option HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):

RKE

Machine type (cloud/VM/metal) and specifications (CPU/memory):

vm

Kubernetes version (use kubectl version): 1.11

Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.0", GitCommit:"0ed33881dc4355495f623c6f22e7dd0b7632b7c0", GitTreeState:"clean", BuildDate:"2018-09-28T15:20:58Z", GoVersion:"go1.11", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Docker (use docker info):

(paste the output here)

Thanks for your report.
Please use v2.1.1
This issue has been fixed in 2.1.1


Removed --with-comment dependency; Fixed approve bug

Fixed a bug where a comment would be added to an MR on approve or
unapprove, even if the MR was already reviewed by the user.
Changed -m and -f behavior so they don't depend on --with-comment to be
used.
Signed-off-by: Lucas Zampieri<EMAIL_ADDRESS>

you know what.. that's my bad. After some IRC discussion I agree with your first version: we should not try to correct user's bad behavior. we just need to make sure an empty filename doesn't break lab (panic) somewhere, but if the user passed an invalid filename the editor should be the one reporting "invalid filename". lab should do what the users asked for.. if that's opening a weird filename, lets try it.
With that said, yeah, feel free to remove the last commit that you added the strings.TrimSpace().
Sorry for that.


pypi package does not include license information

$ pip show python-arango
Name: python-arango
Version: 3.11.0
Summary: Python Driver for ArangoDB
Home-page: https://github.com/joowani/python-arango
Author: Joohwan Oh
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: ~/Library/Python/2.7/lib/python/site-packages
Requires: requests, six

License shows UNKNOWN but the Github repository says MIT license.

It might be possible to put it into the setup.cfg file?
https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files
or as another named arg for the setup() function in setup.py
license="MIT"

Hi @uchuugaka,
I've made the fix in the latest release. Thank you for pointing this out!
Cheers,
Joohwan

verified!
Thanks!


Compile Error when deriving Soars

I am using soa-rs = "0.7.1" and soa-rs-derive = "0.6.0". When I apply the derive macro to a struct:
#[derive(Debug, Soars)]
pub struct Test {
    a: i32,
}

I get the following compile Error:
error[E0053]: method `from_parts` has an incompatible type for trait
  --> src/producer.rs:19:17
   |
19 | #[derive(Debug, Soars)]
   |                 ^^^^^ expected `std::ptr::NonNull<u8>`, found `*mut u8`
   |
   = note: expected signature `unsafe fn(std::ptr::NonNull<u8>, _) -> producer::TestSoaRaw`
              found signature `unsafe fn(*mut u8, _) -> producer::TestSoaRaw`
   = note: this error originates in the derive macro `Soars` (in Nightly builds, run with -Z macro-backtrace for more info)

Thank you for letting me know. I updated soa-rs recently and forgot that I needed to separately publish an update to the derive crate. I just published 0.7.2 that depends on the updated derive crate.


Added Streaming Capability to SageMaker LLMs

This PR adds the ability to declare a Streaming response in the SageMaker LLM by leveraging the invoke_endpoint_with_response_stream capability in boto3. It is heavily based on the AWS Blog Post announcement linked here.
It does not add any additional dependencies since it uses the existing boto3 version.

cc @3coins

@dazajuandaniel This is awesome! Thanks for adding this. I don't have a model setup to test, but code looks good. 🚀
One minor suggestion for a follow up PR, would be nice to move the streaming/non-streaming parts to separate private functions for better readability.

Hey @3coins,
Thanks for approving this PR!
Yes, I agree. I am happy to work on the follow up PR, no issues. I tried to follow the pattern that replicate has.

@baskaryan - please let me know if anything is missing :)

lgtm aside from linting issues. would also be nice to factor out stream implementation into the _stream method defined on parent class, but can also do that in follow up pr

@dazajuandaniel, @3coins - Is this good to be merged ?

@baskaryan
This has been open for a while, is there anything needed to merge this?

@pinak-p I was missing a mypy fix, I've done it now

sorry for the delay, thank you @dazajuandaniel!

Is there any documentation on this? I cant seem to find any.