Missing broker task attribute 'endpoint' on broker startup / reconciliation

We have hit this issues multiple times where the framework is restarted when brokers are starting up, during reconciliation the framework fails to register an endpoint on that broker as it does not recognise TASK_STARTING as a valid state.
This eventually leaves the broker state as follows when running:
{
    "id": "0",
    ...
    "task": {
        "id": "kafka-0-20a281db-069a-4885-96c2-53a6cc3db252",
        "slaveId": "c30ad8fa-8a52-45fb-bcf0-29e22140c8a3-S24",
        "executorId": "kafka-0-02690702-ae31-415e-8a0d-44d85d9636d1",
        "hostname": "localhost",
        "attributes": {},
        "state": "running"
    },
    ...
}

As the framework knows the hostname and port (from the mesos offer it receives) that the broker will start up on, wouldn't it make sense to add the endpoint initially when launching the task rather than appending to it after the task has started.

Here is an example log sequence when this issue happens:
2017-07-25 22:22:49,770 INFO           TaskReconciler] Reconciling 1/6 state of broker 22, task kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76
2017-07-25 22:22:49,933 INFO      KafkaMesosScheduler] [statusUpdate] kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76 TASK_STARTING slave:#3-S24 reason:REASON_RECONCILIATION message:Reconciliation: Latest task state
2017-07-25 22:22:49,980 WARN   BrokerLifecycleManager] Got unknown state TASK_STARTING for broker 22

2017-07-25 22:27:49,791 INFO           TaskReconciler] Reconciling 2/6 state of broker 22, task kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76
2017-07-25 22:27:49,797 INFO      KafkaMesosScheduler] [statusUpdate] kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76 TASK_STARTING slave:#3-S24 reason:REASON_RECONCILIATION message:Reconciliation: Latest task state
2017-07-25 22:27:49,799 WARN   BrokerLifecycleManager] Got unknown state TASK_STARTING for broker 22
2017-07-25 22:31:26,908 INFO      KafkaMesosScheduler] [statusUpdate] kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76 TASK_RUNNING slave:#3-S24 data: myhost.com:10011
2017-07-25 22:31:26,908 WARN   BrokerLifecycleManager] Got unknown state TASK_RUNNING for broker 22

2017-07-25 22:32:49,795 INFO           TaskReconciler] Reconciling 3/6 state of broker 22, task kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76
2017-07-25 22:32:49,799 INFO      KafkaMesosScheduler] [statusUpdate] kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76 TASK_RUNNING slave:#3-S24 message:Reconciliation: Latest task state
2017-07-25 22:32:49,799 INFO   BrokerLifecycleManager] Finished reconciling of broker 22, task kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76

https://github.com/mesos/kafka/blob/master/src/scala/main/ly/stealth/mesos/kafka/scheduler/BrokerLifecycleManager.scala#L79
Firstly there is no case matching (Reconciling, TaskStarting) state, so reconciliation attempt 1 failed. Secondly when the mesos task changes from TASK_STARTING to TASK_RUNNING during reconciliation attempt 2, the status update containing the endpoint data got ignored (2017-07-25 22:31:26,908) because the status update wasn't triggered by the reconciliation and did not match case Reconciling(broker, TaskRunning(_)). And finally when attempt 3 succeeded it already missed the only chance to get the endpoint data from the previous status update, so the running broker will now have a missing endpoint attribute.
A potential fix could be adding the endpoint when the task was created without the need to read it from the status update:
https://github.com/mesos/kafka/blob/master/src/scala/main/ly/stealth/mesos/kafka/scheduler/mesos/BrokerTaskManager.scala#L84
      val task = Broker.Task(
        id,
        task_.getSlaveId.getValue,
        task_.getExecutor.getExecutorId.getValue,
        offer.getHostname,
        attributes)

      task.endpoint = new Endpoint(task.hostname, reservation.port.toInt)
      task
   }

This is a good catch, and thanks for the investigation.
If I recall, the reason the endpoint isn't set on task creation is to avoid advertising a broker that isn't ready to accept connections yet.
I'm curious if the reconciliation status update contains the endpoint?  If you wanted you could try adding case Reconciling(broker, TaskStarting(_)) => onStarting(broker, status) to the state machine and see if that fixes it.

My concern is that if for whatever reason the status update from the executor failed to be processed by the framework, the endpoint attribute could still end up missing.
2017-07-25 22:31:26,908 INFO      KafkaMesosScheduler] [statusUpdate] kafka-broker-22-c34b93bc-f76a-4595-b40d-486b8e9cfe76 TASK_RUNNING slave:#3-S24 data: myhost.com:10011

Currently the only way to populate the endpoint is to get it from the above message which is only sent once from the executor when a broker become ready. This is very fragile and when it fails the endpoint is lost forever until the broker restart, reconciliation or restarting the framework won't recover the endpoint info.
I think adding the extra match case should work, in addition I'd still like to generate the endpoint on task creation, since clients could look at the state attribute to decide if the broker is ready.


[ENG-761] Log exceptions when running user code

Once logging is merged, top level errors will show in autokitteh.

Closing since #230 will send the error to the session log.


Remove commented out code

Codecov Report
Base: 70.44% // Head: 70.43% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (33c6d9e) compared to base (3863853).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #277      +/-   ##
============================================
- Coverage     70.44%   70.43%   -0.01%
  Complexity      610      610
============================================
  Files            97       97
  Lines          2003     2006       +3
  Branches        236      237       +1
============================================
+ Hits           1411     1413       +2
  Misses          496      496
- Partials         96       97       +1

Impacted Files
Coverage Δ

...c/main/java/seedu/address/model/person/Person.java
84.90% <0.00%> (-1.10%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


mio: don't wake up every second/timer tick when run() is called

Currently run() results in the process waking up every second or every timer
tick if set lower because a timeout is passed to the OS wait function.
This changes the code so that run_once() still uses the timeout, but
run() will instruct the OS to wait forever when there are no timers.
The notify mechanism already uses a pipe for awakening the event loop,
so there should be no need to use a timeout for that.
This saves CPU time and battery, and is generally the correct behavior.
Miscellaneous notes:

We also fix epoll because the maximum timeout supported by the Linux kernel is i32::MAX, not isize::MAX.
We fix next_tick_ms() being truncated from u64 to usize
It requires carllerche/nix-rust#192 to allow specifying no timeout to kevent()
The public API of Poll::poll is changed, but that can be avoided if desired.

The choice of usize-types milliseconds for the timeout is not ideal, but should be good enough for now: epoll_wait() doesn't support any higher resolution, so kernel high-resolution timers would be required for better resolution on Linux and a dedicated API might be needed anyway for those.
NOTE: this introduces a next_timer_ms() function that currently uses the next tick if any timer is present. This is obviously not good and instead it should return the time until the first timer, but I'm not sure if the current timer implementation copes with that. The timer implementation itself seems to have serious problems anyway like no handling for times far in the future and no way to get the first timer in O(1).
Only lightly tested, please review.

As an alternative to these proposed changes, would it make sense to change EventLoopConfig::io_poll_timout_ms to be an Option<usize> rather than just a usize, as it is now? Then you could specify "no timeout" as a configuration option when you construct an event loop.

@dwrensha I thought that the timeout was not observable in the run() case, but there is in fact a tick() callback that is called unconditionally, so indeed it needs to be done as you say.
I pushed a new version that does that. It incompatibly changes both the public API and the default tick, with the rationale that a finite tick should not be used if possible and if it's used the application needs to pick the duration anyway.

Sorry for the delay. I pushed the nix change to master. Would you mind changing Cargo.toml to point to the correct nix rev? If you don't get around to it, I can do it as well.

I changed it and rebased.
Note that while this prevents waking up when there are no timers, it still wakes up every timer tick when there are timers and more work would be required to fix that, which might involve some design decisions on how to evolve the timer code (in particular whether to adopt a cascading timer wheel so that buckets don't have timers for multiple wheel periods).

So, out of curiosity. Is there value in having a tick len vs. just pausing indefinitely?

So, out of curiosity. Is there value in having a tick len vs. just pausing indefinitely?

Now that I think about it, I can't come up with any good reason why the tick length should be configurable. I think pausing indefinitely is the right thing to do.

@dwrensha can confirm.

I'm going to close this in favor of #314 (based on this code, thanks!).
Regarding the timer included with Mio, it is explicitly a very coarse grained timer. The trade off is very efficient timeout registration & cancelation. The implementation is very simple to achieve those goals. There is a little bit of overhead due to the naive wakeup every 100ms & walk until the next tick. However, those are reasonable tradeoffs given the benefits IMO.


Install sceneario manually

Description of Problem or Question
I did a scenario. I send by email to my friend. Where do he have to put the files? What directory?
Valkyrie Version
Attach Save, Quest or Scenario
Saves:
%appdata%/Valkyrie/MoM/Save
%appdata%/Valkyrie/D2E/Save
Quest:
%appdata%/Valkyrie/D2E/Editor
Scenario:
%appdata%/Valkyrie/MoM/Editor

Run a search in your pc seeking
Valkyrie\MoM\Editor\scenario1

Windows:
%apodata%\Valkyrie\MoM\Editor\
Android:
Sdcard/Valkyrie/MoM/Editor
Drop it there, you can use folders under this directory.

@mk1lolo Did you get your answer ? Can I close this ticket ?

Yes! Close. All ok


support CJK(chinese, japanese, Korean)

the old version not support Chinese character.
https://github.com/nsf/termbox-go/issues/71

I think that giving support for CJK should be a more complex, for example, not only view.go but also [1] edit.go should modified to stop assuming that 1 rune == 1 cell. Could you check wrapping, full edition mode, etc.?
Thanks for your contribution :)
[1] https://github.com/jroimartin/gocui/blob/master/edit.go

Closed due to inactivity. Anyway, gocui assumes 1 rune / 1 cell in several places, so this change will need more work. I'll evaluate supporting this when I rewrite the internals to support font colors.


Tensorflow predicts odd results with insufficient GPU memory

Hi all,
I am currently having a problem that, when my code tries to initialize two or more predict instances in a GPU with insufficient memory, instead of throwing an OOM exception, the instances are initialized normally. However, when I try to predict an image with these instances, they produce weird results like [1.0, 0.0, 0.0, …].
Is this a bug when two or more sessions try to race for limited amount of GPU memory?
Please see below for my system information and the exact steps to reproduce the problem. I would very much appreciate it if you could take a look.
Cheers,
Vincent
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution: CentOS Linux release 7.2.1511
TensorFlow installed from (source or binary): official binaries
TensorFlow version (use command below): 1.3.0/ 1.2.0/ 1.1.0
Python version: 2.7.5
CUDA/cuDNN version: CUDA 8.0.61, CUDNN 6.0
GPU model and memory: 1080 Ti (11172MB)
Exact steps to reproduce:

Download and uncompress the file below with two scripts;
Download the official inception_v1 imagenet pretrained model  from http://download.tensorflow.org/models/inception_v1_2016_08_28.tar.gz
Try to occupy most of the memory in the GPU to run on - the exact amount of memory to occupy needs to be carefully tuned to reproduce the problem, in my case, I use pycuda to allocate 10720 out of the 11172MB of my 1080 Ti.
Run test_monitor.py in two separate command prompts, we should see weird results within a few minutes (the scripts stop when encounter such results).

reproduce_code.zip

Thanks for the report and the detailed instructions.
I'm going to close this with the intention of continuing discussion on #14147 which seems similar.

Thanks for the instructions to reproduce.
@yzhwang and @zheng-xq have been investigating some issues with memory allocations and multiple processes and might have some more details here.

Hi @vincentfung13 . Thanks for reporting the issue. We have encountered similar issues internally when two or more processes are running TensorFlow with limited GPU memory. In our case, a simple const tensor or random tensor creation will cause garbage values instead of any OOM error when one process has already taken most GPU memory.
The short answer to the issue is that: it is due to CUDA runtime silently failing to initialize with insufficient GPU memory. It will cause all the CUDA calls afterwards to produce incorrect results, but not fail with errors. We currently have a workaround which is to initialize CUDA runtime before any of our large GPU memory allocation. It should go in within a week. I'm also investigating the reason for the silent failure. I will provide update when I have something to share with you.

Hi @yzhwang @zheng-xq, any updates on this issue? Thanks. :)

Hi @vincentfung13 I've made a commit that should solve the problem: https://github.com/tensorflow/tensorflow/commit/4535bd5df4d077072a8f207146bf4cd051971237 Now each process that runs a TF program will try to initialize CUDA runtime before the giant device memory allocation, and if the remaining memory is insufficient, there should be an error for session creation. Please verify if this solves the problem. Thanks!


Site Export Gets Stuck on "In Progress"

Description
The export wizard gets stuck on the "In Progress" state. I inspected the source code for DotNetNuke.SiteExportImport.dll, and found that the "ExportModulePackage(ExportModule exportModule)" function in "PagesExportService.cs" was passing a null desktop module to "PackageController.Instance.GetExtensionPackage(Null.NullInteger, p => p.PackageID == desktopModule.PackageID)." This was causing an "Object reference not set to an instance of an object exception" to be generated, and no further progress to be made.
For some reason, the "ExportModulePackage(ExportModule exportModule)" is being called for a module that is not present in the "dbo.DesktopModules" table. Therefore, when "DesktopModuleController.GetDesktopModule(desktopModuleId, Null.NullInteger)" is called with this ID, it returns null. Subsequently, the call to "PackageController.Instance.GetExtensionPackage(Null.NullInteger, p => p.PackageID == desktopModule.PackageID)" generates an exception due to a property being accessed on a null object.
I worked around this issue by building a custom "DotNetNuke.SiteExportImport.dll" with the following code for "ExportModulePackage(ExportModule exportModule)":
private int ExportModulePackage(ExportModule exportModule)
    {
        if (!_exportedModuleDefinitions.Contains(exportModule.ModuleDefID))
        {
            var packageZipFile = $"{Globals.ApplicationMapPath}{Constants.ExportFolder}{_exportImportJob.Directory.TrimEnd('\\', '/')}\\{Constants.ExportZipPackages}";
            var moduleDefinition = ModuleDefinitionController.GetModuleDefinitionByID(exportModule.ModuleDefID);
            var desktopModuleId = moduleDefinition.DesktopModuleID; // this ID that is not present in dbo.DesktopModules
            var desktopModule = DesktopModuleController.GetDesktopModule(desktopModuleId, Null.NullInteger); // Because the ID is not present in dbo.DesktopModules, this returns null

            // I added this if statement to prevent GetExtensionPackage from throwing an exception
            if (desktopModule != null)
            {
                var package = PackageController.Instance.GetExtensionPackage(Null.NullInteger, p => p.PackageID == desktopModule.PackageID);
                var filePath = InstallerUtil.GetPackageBackupPath(package);

                if (File.Exists(filePath))
                {
                    var offset = Path.GetDirectoryName(filePath)?.Length + 1;
                    CompressionUtil.AddFileToArchive(filePath, packageZipFile, offset.GetValueOrDefault(0));

                    Repository.CreateItem(new ExportPackage
                    {
                        PackageName = package.Name,
                        Version = package.Version,
                        PackageType = package.PackageType,
                        PackageFileName = InstallerUtil.GetPackageBackupName(package)
                    }, null);

                    _exportedModuleDefinitions.Add(exportModule.ModuleDefID);
                    return 1;
                }
            }
        }
        return 0;
    }

Steps to reproduce

Queue a new export for any page on the site.
Observe that the export routine never completes.

Current result
The export wizard gets stuck, and an incomplete set of files get generated in the "App_Data/ExportImport/<DATE_AND_TIME>" folder. The only files that are present are "export.dnndb" and "export_files.zip".
Expected result
The export wizard should complete the export process. A full set of files should be generated in the "App_Data/ExportImport/<DATE_AND_TIME>" folder. These should include "export.json," "export_db.zip," "export_files.zip," "export_packages.zip," "export_templates.zip," and "export_themes.zip."
Affected version

[ ] 9.2
[x] 9.1.1 <-- This is the version that my site is running, so I don't know if other version are affected.
[ ] 9.1
[ ] 9.0

Affected browser

[x] Chrome <-- I only tested this in Chrome, but I would assume that all other browsers are affected.
[x] Firefox
[x] Safari
[x] Internet Explorer
[x] Edge

I am having this same issue on 9.2. The files generated are:

export.dnndb
export_files.zip
export_packages.zip
export_templates.zip
export_themes.zip
which it generates within a few minutes, then hangs on "In Progress" indefinitely. I haven't inspected it yet.

I am closing this issue assuming this is with a specific module since I was not able to reproduce on the latest version @JTMaher2 if that only happens on the latest version with some specific setup please include detailed steps to reproduce the issue.

@valadas This is still an issue in Evoq Basic 9.3.0 Enterprise Edition: Core-based Licensing (64-bit)
Went through the steps in https://dnnsupport.dnnsoftware.com/hc/en-us/articles/360009692674-Importing-or-Exporting-hangs-at-Submitted-Status with no success.

The only file generated is the export.dnndb

Nothing populates in Export Summary.

Let me know if you need more information.

I'm experiencing this issue as well, and I'm on Evoq 9.6.2. When is DNN planning on fixing this issue?

DNN Platform is currently on version 9.10.2. You may want to open a support ticket with Evoq to see if they have plans to investigate if this bug will continue to affect Evoq customers if they move to the latest version of DNN Platform (and when you can expect an updated version).

Thanks bdukes! I'm in progress of reaching out now.

The solution for me was to add the hostname to the server field in the import-export service. See article for details:
https://dnnsupport.dnnsoftware.com/hc/en-us/articles/360014800899-DNN-Import-Export-stuck-In-Progress-or-fails-with-exception-


Azure - Add Disk, Cog Services, Data Factory and IoT Hub resources

This is super helpful thank you!

This should solve #2564


{GSSOC'23} Add logo to social media

This is a(n):

[ ] Update to an existing Animated Button
[ ] Any Error
[x] Proposal to the Repository
[ ] Documentation / README.md changes

Details:

There is a need to add a logo to the social media. I want to improve the UI of this feature.
Please assign this issue to me.

@thekirti02 I guess there is no need of the UI as we will be changing the landing page!


Install annotations lib using pip

"Properly" install and import the annotations library (instead of just adding it to the path).

For tests to actually pass on Ubuntu 18, we need to fix the annotation library > python3.7 dependency. I will merge for now though because the installation seems to be OK like this.


chore: update preview.yml

close https://github.com/antvis/G2/pull/2997

Pull Request Test Coverage Report for Build 367493157

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 93.426%

Files with Coverage Reduction
New Missed Lines
%

src/chart/controller/gesture.ts
7
82.14%

Totals

Change from base Build 367428857:
-0.07%

Covered Lines:
10509

Relevant Lines:
10914

💛  - Coveralls

@hustcc PTAL


Tune-up for height-map based world generator

Assets can now be loaded in WorldViewer, which now allows for loading the HeightMap world:

Surprisingly, it is by far the slowest world generator of all. I'm not sure why the code was like it was, but it offered many possibilities for performance improvements.
This PR performs a few of them leading to a speed-up of about 20x-50x at equal quality. Moreover, it makes the surface provider independent of chunk size and uses a dynamic scale factor instead. I also lowered the sea level for additional land mass (see the screenshot).
In the default setting, the terrain repeats after 2048 blocks, but biomes/vegetation/etc. is procedural and thus different.

Test this please
(Seeing if the PR builder thing works - might not since it is an existing PR)

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/1/
Jenkins Success Message

Awesome!

Merged, thanks :-)
Didn't have much of a reference point for speed, been a long while since I've been running around in a height map world for any substantial period of time. But I flew around for a few kilometers and the world was keeping up fine.
One issue I noted - I think the change in sea level threw off the level at which grass begins:

If you can find blocks high enough then grass begins normally :-)
The world in general seemed changed scale-wise - it used to be very smooth and gradual about height, now it feels a lot sharper. The tiny stray islands seem to be weirdly contrasted although that could be from just never having seen them before. Didn't seem to start on the "mainland" I'm used to:

Still, it is clearly the height map world with its interesting tectonic features, which is the most important part :-)

Hmm .. that's interesting. You should spawn at the same point as before. Will look into that in the frame of reworking spawning positions.
The scale in height and x/z are configurable now. We could even add the asset name and the sea level to the set of parameter to allow for entirely different worlds.


chore: adding async function for safe execute in instrumentation

Short description of the changes

Adding async function safeExecuteInTheMiddleAsync for instrumentations

Can you provide an example when this would be used? Implementation seems fine to me but I'm not sure I understand the usecase.

Can you provide an example when this would be used? Implementation seems fine to me but I'm not sure I understand the usecase.

Can you provide an example when this would be used? Implementation seems fine to me but I'm not sure I understand the usecase.
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/master/plugins/node/opentelemetry-instrumentation-graphql/src/utils.ts#L360

Can you provide an example when this would be used? Implementation seems fine to me but I'm not sure I understand the usecase.
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/master/plugins/node/opentelemetry-instrumentation-graphql/src/utils.ts#L360


Support for destructuring in function parameters

When using destructuring in function parameters, the current spec of @param is not enough.
For example, it's difficult to write a doc for the following function due to the mismatch between parameters and arguments.
function foo ([a, b], {x: {y: c}}) {
   return a + b + c;
}

foo([1, 2], {x: {y: 3}});  // => 6

This function requires an array as the first argument and an object as the second argument, and defines parameters a, b and c as number.
Here is a quick try to write a doc for the above function with the current spec.
/**
 * @param {Array<number>} array desc.
 * @param {Object} obj
 * @param {Object} obj.x
 * @param {number} obj.x.y desc.
 * @return {number} desc.
 */

But this docs has some problems such as:

The parameters a, b, c are not described.
Using dummy parameter names, array and obj, which are required due to the spec. (it says there must be the name of the documented parameter.)
This doesn't provide information about the fact that the only top 2 elements of an array will be used.

For this kind of ES6-specific problems, it seems that JSDoc has no plan to deal with (providing an workaround or building a new syntax) currently.

JSDoc for destructurings · Issue #987 · jsdoc3/jsdoc

So, I suggest introducing a few breaking changes into @arg and @param:

@arg: Stop treating it as an alias of @param and let @arg describe arguments.

@arg {type} reference_name description.

@param: When using @param along with @arg, @param will indicate parameters referring @arg tags.

@param {type} parameter_name reference_expression description

As an example, the doc for the above function will be:
/**
 * @arg {Array<number>} ref1 desc.
 * @arg {{x: {y: number}}} ref2 desc.
 * @param {number} a ref1[0] desc.
 * @param {number} b ref1[1] desc.
 * @param {number} c ref2.x.y desc.
 * @return {number} desc.
 */

What do you think?

Sorry, ESDoc already supports object destructuring ...

Array destructuring in function parameters is somewhat broken?
warning: signature mismatch: Foo#foo src/test.js#2
1| /**
2|  * @param {Array<number>} coord hoge
3|  * @param {{x: {y: number}}} opts fuga
4|  * @return {number} desc.
5|  */
6| foo([a, b], {x: {y: c}}) {

@nodaguti Hi! Thanks for reporting this issue!
I fix https://github.com/esdoc/esdoc/issues/178#issuecomment-158873923 on master.

I released v0.4.5 that fixed this issue.

@h13i32maru Great job! Thanks!! :beers:


Recently Visited Sites shows empty list (but I have recent sites on sharepoint home)

Category

[X] Question
[ ] Bug
[ ] Enhancement

Expected or Desired Behavior
The recently visited sites webpart should show the same sites as the recent list on the sharepoint home (/_layouts/15/sharepoint.aspx?v=sites).
Observed Behavior
Recently visited sites web part does not display any sites. I have checked the graph endpoint used by the webpart, which does not return sites as well.
Steps to Reproduce
Compare the sites displayed in the recently visited webpart with the recent sites list on SharePoint Home.
Is this a limitation of the graph? Will this change in the near future? Do we have any other options to show the same list of recent sites as on SharePoint Home?
Thank you for your feedback!

@gruering SharePoint doesn't have an API for this, that is why we used Microsoft Graph to retrieve the data. The MS Graph uses other trends and insights to show the recent sites. Insights API is currently still in beta, so is likely to get better in the future.

@estruyf  which is the endpoint you would use for that? I have tested these two:
https://graph.microsoft.com/v1.0/me/insights/used?$filter=ResourceVisualization/Type eq 'spsite'
https://graph.microsoft.com/v1.0/me/insights/used?$filter=ResourceVisualization/Type eq 'web'
The 1st one returns only sites results, but they dont see to be very accurate, 2nd returns many results, not only site but pages, items views etc...
Thanks


Add a constant about whether asserts are enabled

Hello!
Related to https://github.com/dart-lang/sdk/issues/31992
Packages often want to run logic only in debug mode.
There are multiple solutions for it, such as using an assert or using specific Flutter-defined environment variables, but they all have their limitations.

Relying on asserts produces generally poorly readable code. It also cannot be used in the constructor of const objects, such as:
 const Object(
   param: debug ? 'foo' : 'bar',
 );

Relying on Flutter's environment variables solves those concerns ... But they only work in flutter.

Could we maybe instead have Dart offers a constant about whether asserts are enabled?

@mraleph pointed out the following flag here https://github.com/dart-lang/sdk/issues/45378
const bool isAotCompiled = const bool.fromEnvironment('dart.vm.product')

Maybe there's already one for asserts?

There isn't one that works generally across all compilers, and there probably should be.
Something like
const bool.fromEnvironment("dart.flag.asserts_enabled")

We should have a consistent strategy for using the dart. compilation environment namespace, which would make the naming of singing like this trivial.

We can easily expose a const bool assetsEnabled, the only question is where to put it.

Another value of having a built-in constant for this is, we could add an @visibleForDebug annotation to package:meta, for code that must be used only inside asserts/kDebugMode.
Such that we have:
@visibleForDebug
bool fn() {}

void main() {
  fn(); // Warn

  if (kDebugMode) {
    fn(); // OK
  }

  assert(fn()); // OK
}


network crate book chapter

Working on this in #445

will be brain-dumping my thoughts on how the chapter should be structured in the comments here

My current approach is going to be to walk through the flows of interaction with the crate, going from high -> low levels of abstraction.
So the first flow I'll focus on, is how is this crate used to interact with the network? Beginning from where this is invoked in the pipeline (IIUC the StateFetcher struct, but still reading), and walking all the way down the various struct definitions.
Another flow is viewing this from the perspective of a standalone crate, not as a part of a full node - i.e. if one simply wants to connect to the p2p network. Here, I think the entrypoint into the crate is in instantiating a network connection using either NetworkManager or NetworkBuilder

Can you provide more details about the role of the 'StateFetcher' struct in the overall pipeline after reading? @akirillo

Beginning from where this is invoked in the pipeline (IIUC the StateFetcher struct, but still reading), and walking all the way down the various struct definitions.

the mermaid diagrams are currently broken for some reason in the rendered docs.rs, but work in mermaid.live:
https://mermaid.live/edit#pako:eNplUk1PwzAM_SuRT0UqiC3t1FWIAyAEEkgIdmLlEDVmi1iTkqTA2PbfyUc3Nuilsf3e87PlFdSKI5RAyEyzdk4mF5Uk_quVlFhboaRJJpcP5E4YixL1UV-_EqZWH6iX02T3PHrpi69o6_kjvndobHK5ECgtuZUW9Sur0WwlntAYrz9N-tc9k2zmWrwcAibMvE2TB0S9zfwiLLPo-P53mLz2FvoKCcFOeG80cnx8TtZC1qoRcrbeWQq4yO0Rwgofqc7O1H_obgUR3rXcg1tn2ayjTlTsORFlWvYpzXp_zH2Uj8lZQM6Z5AskJhjSca8HwvsLj-I9itwg485FSi4UF7glhYX8HbJVi4XzLLmb72-XQIAUGtQNE9xdzMrTK7BzbLCC0j05028VVHLjcKyz6mkpayit7jCFuJErwdyZNdtkyySUK_iCMh-d5DQf53SYFXSQDUYpLKEsqMvSgtJsmNHxaZFvUvhWyvFPT4rhKMtGNM9oMR64WgrIhVX6Pt5zOOvQ4TkQfMPNDycC-WQ
will add more docs on information flow

@erayack it's a dense read, but I think I'm just about to start diving into how the StateFetcher gets used in the pipeline as I read more about how the FetchClient gets instantiated - I'm still thinking about how low-level this book chapter should go, though
@mattsse the mermaid diagrams were super useful! I know we use them a couple of times throughout the rustdocs and I'm wondering if they should also get pulled into the book, which is meant to be more high-level...
Regardless, I just pushed my current progress on the draft of the doc if you want to check it out (#445)! Still a lot to write and it's got TODOs scattered throughout, but directionally I'm starting with how the network crate's items are consumed in the pipeline and going down the levels of abstraction & the various structs / traits underneath.
If you take a look, lmk what you think!

(would recommend viewing the draft by pulling the branch and running mdbook serve from the root)

#445 merged, closing


Url event by its name

I think there should be a possible more friendly URL for users as domain.com/calendarium/event-name
Is there any way to implement this method?

Sure, but the event.title attribute is not unique, so we will have to add a unique slug field. Then we can call the slug in the URL. We aren't working with thap app at the moment, so pull requests are very welcome.
TO DO:

Add slug field
Create a datamigration, which generates unique slugs from the event's title
Add functions to auto-generate slugs on event creation, if no custom slug has been set
Prepopulate fields in admin.py

Then URLs should look like http://localhost:8000/calendar/party-all-night-vol-two and for a second event with the same title http://localhost:8000/calendar/party-all-night-vol-two-2.


Apollo Client caching information I don't want cached!

Hi there guys!
I am using apollo client for my vue app, but for example this happens:
1 - I login with an account.
2 - Navigate inside a component via vue-router.
3 - A query for a product list gets triggered.
4 - I logout.
5 - I login inside another account. (The queries are fetched by current User ID)
6 - I navigate to the same component via vue-router.
7 - I see the information from the other account for a split second and then the information from the current user appears.
I tried client.resetStore() and client.cache.clear() or client.cache.data.clear().
methods: {
    logout () {
      Object.values(this.$apollo.provider.clients)
        .forEach(client => client.cache.data.clear())
      sessionStorage.clear()
      localStorage.clear()
      this.$store.state.user = null
      this.$store.state.token = null
      this.$store.state.isUserLoggedIn = false
      this.$router.push('/login')
    }
  }

Nothing worked. :)

This sounds like it should be on the apollo-client repo then...

I don't actually know if its apollo client or vue-apollo causing the issue, anyway, I fixed it by emptying the objects and arrays when the component gets deactivated hAHHA


Cirrus and Luci customer testing shards are different

Noticed in https://github.com/flutter/flutter/pull/92906 that

the Cirrus customer testing shard was failing ❌ ,
but the Luci testing shard was passing ✅ .

I thought maybe the Cirrus shard was flaky, so I re-ran it, but it failed consistently.
Cirrus build: https://cirrus-ci.com/task/4572007045005312
Luci build: https://ci.chromium.org/ui/p/flutter/builders/try/Linux customer_testing/25595/overview
It looks like the Luci shard is not running as many tests as the Cirrus shard based on the stdout. There is an error in the Luci build though that may be the cause, filed https://github.com/flutter/flutter/issues/94949 in case it is separate.

Fixes:
https://flutter-review.googlesource.com/c/recipes/+/25660
https://flutter-review.googlesource.com/c/recipes/+/25080


[bug] Contributing page has broken links

Describe the bug
The Contributing.md file has several dead links in the first section
To Reproduce

Go to Contributing.md
Click through either of the links in the first section

Expected behavior
Links should lead to documentation as expected
GUAC version
n/a irrelevant

Thanks for the bug report @lee0c! I believe these got moved to guac-docs. We will fix those!


Estimation of 2.5T Tokens Checkpoint

Hello, do you have an estimation on when the 2.5T Tokens intermediate checkpoint will be ready?
Do you think you will achieve it before x-mas? I am very excited for next to release and can't wait heheh
Anyway, thank you so much for your work! You are contributing an extremely important part in this field!

https://huggingface.co/TinyLlama/TinyLlama-1.1B-intermediate-step-1195k-token-2.5T
Enjoy :)


load terrain shader from project directly

Not great to rely on user copy pasting the shader by hand.
Closes #10

How can i fix it ?
On Thu, Apr 4, 2024 at 1:10 PM Emi @.***> wrote:

Not great to rely on user copy pasting the shader by hand.
Closes #10 https://github.com/ethereumdegen/bevy_mesh_terrain/issues/10
You can view, comment on, or merge this pull request online at:
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18
Commit Summary

f6478d5
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18/commits/f6478d59121cd639707d25e3d3377e4ced4cadf4
load terrain shader from project directly

File Changes
(2 files
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18/files)

M src/lib.rs
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759
(11)
M src/terrain_material.rs
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18/files#diff-3ced24974493147cdeaf93e5a45f8d99a05cfa77ae2d43ba9ddaf3e76caf1e11
(6)

Patch Links:

https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18.patch
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18.diff

—
Reply to this email directly, view it on GitHub
https://github.com/ethereumdegen/bevy_mesh_terrain/pull/18, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPVWL6IFGNPRHH7GZMHC7TY3WCPVAVCNFSM6AAAAABFXVNMOKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDMMBYHAZTMOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This PR already has all the fixes


[Feature Request] PadToSquare: Square Padding to Preserve Aspect Ratios When Resizing Images with Varied Shapes in torchvision.transforms.v2

Closes #8699.

Thanks for your feedback!
After experimenting with the PadToSquare transform and inspecting the learned features, I realized that it might introduce spurious correlations. For instance, if images of a particular class (e.g., airplanes) are predominantly in a specific format (e.g., landscape, where width > height), the transformation could reinforce this bias. Based on these outcomes, I would now advise against including this transformation in torchvision.
A safer approach is likely to use a batch size of 1 and, optionally if required by the model architecture, resize the image to a multiple of the expected dimensions.
If object location annotations are available, images can also be safely cropped using the bounding box coordinates to ensure the object remains within the cropped region. This way, multiple images can be resized together after being cropped and thus be batched.


Add test coverage for multiple listeners (via #66)

https://github.com/4Catalyzer/found-relay/pull/66
To add support for testing multiple ReadyStateRender' I figured to use the same model that I do in apps where I render the instances from previous children.
If there's a better way to do this than changing WidgetParent from a stateless component to a class, please feel free to let me know.
The test works by first testing for a number of render instances, which is 2 given the parent and child containers. Then the component is updated, which will then render the child and a clone of the child. Then the test checks again to see that there are 3 instances of ReadyStateRenderer.

Okay, this is a good start. Ideally it'd be good to have something closer to your original example, though, where the modal is a different route from the "old" one.

I've added a secondary route /:pathName/default and used props.router.push in one of the components to trigger a route change.
However I'm not happy with my solution of patching ServerProtocol.transition to enable the route change. Also in the process of the route change, the existing route seems to have trouble with its props but I believe it's an issue with the test itself because I did not experience this with my own demo. Here's the error:
  console.error node_modules/fbjs/lib/warning.js:35
    Warning: createFragmentSpecResolver: Expected prop `first` to be supplied to `Relay(WidgetChildren)`, but got `undefined`. Pass an explicit `null` if this is intentional.

  console.error node_modules/fbjs/lib/warning.js:35
    Warning: createFragmentSpecResolver: Expected prop `second` to be supplied to `Relay(WidgetChildren)`, but got `undefined`. Pass an explicit `null` if this is intentional.

  console.error node_modules/fbjs/lib/warning.js:35
    Warning: createFragmentSpecResolver: Expected prop `third` to be supplied to `Relay(WidgetChildren)`, but got `undefined`. Pass an explicit `null` if this is intentional.

What would you recommend @taion ?

I'm going to merge this and tweak it a bit on my end.


Can't npm start :  Unable to load plugin 'enhance/arc-plugin-enhance': Cannot find module 'node:fs'

ran npm install to install packages
ran npm start
received the following output

❯ npm start

><EMAIL_ADDRESS>start /Users/westonstewart-tennes/dev/dijondreams/services/enhance-music
> npx enhance dev

Error: Plugin error:
- Unable to load plugin 'enhance/arc-plugin-enhance': Cannot find module 'node:fs'

wondering if there's a recommended node version i should be running?

Node: I was able to fix this by upgrading Node to 18.18.0.  Closing this because i think that's fine but would be great to have a minimum Node version listed!

Glad you got it working @wstewarttennes 👍 -- we'll add that to our list of items when documenting demos like this. Thanks
Just FYI, Node 16 has left maintenance mode and is end-of-life as of Sept 11. Highly recommend updating old apps if at all possible.
https://nodejs.org/en/blog/announcements/nodejs16-eol

@tbeseda we should add an engines section to the package.json.


cinny-desktop: 2.1.3 -> 2.2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cinnyapp/cinny-desktop/releases.
meta.description for cinny-desktop is: "Yet another matrix client for desktop"
meta.homepage for cinny-desktop is: "https://github.com/cinnyapp/cinny-desktop"
meta.changelog for cinny-desktop is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.2.0 with grep in /nix/store/6hf2bpg9594q0gmi4nd1hqwa65hrb2z6-cinny-desktop

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cinny-desktop

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6hf2bpg9594q0gmi4nd1hqwa65hrb2z6-cinny-desktop
ls -la /nix/store/6hf2bpg9594q0gmi4nd1hqwa65hrb2z6-cinny-desktop/bin

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

1 package built:

cinny-desktop

Maintainer pings
cc @aveltras for testing.

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

1 package built:

cinny-desktop


IBD GWAS in gentropy pipline requested by one of the partners

The GWAS in question - https://www.ebi.ac.uk/gwas/publications/37156999
I am currently discussing it with Laura

All studies are in freeze10


[Feature] Add a flag to error if missing

I use this action along with a second step to check if my check failed.
I believe this is a very common use case and users would benefit from a flag.
If this is something you would be amenable to incorporating, please let me know what else I should do to make this easy for you.

CI failed


[MTB] Fixed ci-test script

/assign @JimBugwadia

/retest
/lgtm
/approve

/lgtm
/approve

@Divya063 did you want to take a look at the failing tests?

@rjbez17 The tests are failing as prow doesn't support kind cluster by default. I have filed a PR here - https://github.com/kubernetes/test-infra/pull/19447

/retest

@Divya063 any update on this? It seems your linked PR has been merged.


Divergence

[x] Make the client number configurable
[x] Remove music festival example
[x] Fix ORSet product
[x] Change the way convergence is being tracked right now since it doesn't allow us to observe divergence
[x] Log divergence in the end of ad_counter simulation
[x] Make two test cases peer_to_peer_divergence and client_server_divergence and run them with different number of clients
[x] Allow clients to also disable the ads (and add a third test case for that)
[x] Make a graph: X (client number) and Y (divergence)

I'm not sure why we are getting the transient errors on Travis, but I believe this ready to be merged now.


Fix author argument for Permission Set resource

v0.8.12 produces the following error when running terraform validate if author argument is set for aquasec_permissions_sets:
│ Error: Computed attributes cannot be set
│
│   with module.common.aquasec_permissions_sets.team_contributor,
│   on ../../modules/common/main.tf line 64, in resource "aquasec_permissions_sets" "team_contributor":
│   64:   author = "terraform"
│
│ Computed attributes cannot be set, but a value was set for "author".

Looks like this argument was mistakenly changed from Optional: true to Computed: true in https://github.com/aquasecurity/terraform-provider-aquasec/commit/55dcadc2208bbdbd8c5b0738327125e91ae9cbfb (PR: https://github.com/aquasecurity/terraform-provider-aquasec/pull/144), as the documentation still says that this is an optional argument.
This PR changes the argument back to Optional: true and also reverts the relevant changes in resource_permission_set_test.go

Hi, @sivapalan please run the following command to generate doc on you forked branch:
go run github.com/hashicorp/terraform-plugin-docs/cmd/tfplugindocs
after that please push it.
because you updated the resource schema we can't merge the pr without it.

@yossig-aquasec Updated ✅


too few components after pca

I am very  interested in your excellent work and i can run, but the components are too few, and it displays as follow:
retaining 99.7% of eigenvalues keeps 8 components using thousands pruned meshes only!

I am very interested in your excellent work and i can run, but the components are too few, and it displays as follow:
retaining 99.7% of eigenvalues keeps 8 components using thousands pruned meshes only!

Hi, I'm trying to use this code as well but I'm having trouble installing lsfm with python==3.5. Did you encounter the same problem in the beginning?


S3 webhook feature data feed

:nut_and_bolt: Description: What code changed, and why?
This PR  includes backend api's for data-feed service,
api is created for

Enable and disable for data-feed integration
Test connection

Before saving data-feed integration
After saving data-feed integration, it also includes test connection by secret id(supports both old and new connection)

Add data-feed integration (it includes all integration)
Integration and unit test cases is included

:chains: Related Resources
#5463 #5125
:+1: Definition of Done
All test  cases should pass and api should be working as expected
:athletic_shoe: How to Build and Test the Change
Goto automate folder enter
1. hab studio enter
2. start_all_services
3. rebuild components/automate-gateway
4. rebuild components/data-feed-service/
5. hab pkg install --binlink core/curl -> if you don’t find  curl command in hab studio

how to run integration test cases
1. go inside hab studio
2. source integration/helpers/setup_minio.sh && start_minio_background -> ( setup minio in hab studio)
3. datafeed_run_integration_tests -> (to run integeration test cases)

how to run unit test cases
1. go automate repo
2. go test ./components/data-feed-service/service/*.go (to run unit test cases)

Make sure to check data-feed database
6. chef-automate dev psql postgres
7. \c data_feed_service
8. select * from destinations;
	id  | name | url  |  secret  | services | integration_types | meta_data  | enable
       -----+------+------+----------+----------+-------------------+------------+--------

Now we can run data-feed api's

Add secrets for data-feed integration

request

Storage (S3/Minio)
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/secrets' -d'{"name": "s3","type": "data_feed","data": [{"key":"access_key","value":"access_key_value"},{"key":"secret_access_key", "value":"secret_access_key_value"}]}'

Service Now
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/secrets' -d'{"name": "serviceNOW","type": "data_feed","data":[{"key":"username","value":"admin"},{"key":"password","value":"Password"}]}'

Splunk
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/secrets' -d '{"name": "anyname","type": "data_feed","data": [{"key": "headers","value": "{\"Authorization\":\"Splunk 8a902a02-cc11-41f7-a2fa-e6a4297bd59d\"}"},{"key": "auth_type","value": "header_auth"}]}'

ELK and custom header
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/secrets' -d '{"name": "anyname","type": "data_feed","data": [{"key": "headers","value": "{\"Authorization\":\"Bearer  <token>\"}"},{"key": "auth_type","value": "header_auth"}]}'

response

{"id":"38796b44-1821-4a8a-9002-4d9cd976871f"}

Data-feed integration

Storage (S3) -> add

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destination' -d '{"name": "S3","url":"null","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "S3","integration_types":"Storage","enable": true,"meta_data":[{"key":"bucket","value":"bucket_name"},{"key":"region","value":"us-east-2"}]}'

Response

{"id":"285","name":"S3","url":"null","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"S3","integration_types":"Storage","enable":true,"meta_data":[{"key":"bucket","value":"bucket_name"},{"key":"region","value":"us-east-2"}]}

Storage (Minio) -> add

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destination' -d '{"name": "Minio","url":"http://<IP_ADDRESS>:9000","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "Minio","integration_types":"Storage","enable": true,"meta_data":[{"key":"bucket","value":"bucket_name"}]}'

Response

{"id":"286","name":"Minio","url":"http://<IP_ADDRESS>:9000","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"Minio","integration_types":"Storage","enable":true,"meta_data":[{"key":"bucket","value":"bucket_name"}]}

Webhook (Service Now) -> add

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destination' -d '{"name": "Service Now","url":"https://localhost/api/x_chef_automate/asset","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "Service Now","integration_types":"Webhook","enable": true,"meta_data":[]}'

Response

{"id":"286","name":"Service Now","url":"https://localhost/api/x_chef_automate/asset","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"Service Now","integration_types":"Webhook","enable":true,"meta_data":[]}

Webhook (Splunk) -> add

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destination' -d '{"name": "Splunk","url":"https://localhost","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "Splunk","integration_types":"Webhook","enable": true,"meta_data":[]}'

Response

{"id":"286","name":"Splunk","url":"https://localhost","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"Splunk","integration_types":"Webhook","enable":true,"meta_data":[]}

Webhook (ELK/Custom) -> add

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destination' -d '{"name": "Splunk","url":"https://localhost","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "ELK","integration_types":"Webhook","enable": true,"meta_data":[]}'

Response

{"id":"286","name":"ELK","url":"https://localhost","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"ELK","integration_types":"Webhook","enable":true,"meta_data":[]}

Enable and disable api

Request

Enable
curl -sSkH "api-token: $(get_admin_token)" -X PATCH https://a2-dev.test/api/v0/datafeed/destination/enable/${id} -d'{ "id":"${id}","enable":true}'

Disable
curl -sSkH "api-token: $(get_admin_token)" -X PATCH https://a2-dev.test/api/v0/datafeed/destination/enable/${id} -d'{ "id":"${id}","enable":false}'

Response

{"id": "1972","name": "vendor","url": "http://<IP_ADDRESS>:9000","secret": "54d23262-232a-4c24-af70-f3b729586d3f","services": "Service Now","integration_types": "Webhook","enable": true,"meta_data": []}

Test connection api Before saving data-feed integration

Request

Minio
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d'{"url":"http://<IP_ADDRESS>:9000", "aws": {"access_key":"access_key_value","secret_access_key":"secret_access_key_value","bucket":"bucket_value","region":"us-west-2"}}'

S3
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d'{"url":"null", "aws": {"access_key":"access_key_value","secret_access_key":"secret_access_key_value","bucket":"bucket_value","region":"us-west-2"}}'

ELK,costume headers and Splunk
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d '{"url": "http://<IP_ADDRESS>:8088/services/collector/raw","header": { "value": "{\"Authorization\":\"Splunk 6f01b869-c181-4fb2-a74c-b619e6197a85\",\"bla\":\"dublu\"}"}}'

Response

{"success": true}

Test connection api After saving data-feed integration

Service Now/Splunk (To support old connection)

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d {"url": "https://localhost/api/x_chef_automate/asset","secret_id": {"id": "7ae6dc99-0518-42f6-9949-3617b6c436fb"}}

Service Now/Splunk  (To support new connection -> Webhook)
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d { "url": "http://ec2-13-233-122-5.ap-south-1.compute.amazonaws.com:9000", "secret_id_with_addon": {"id": "e4299bf6-0d5d-490c-9352-c61ff707b455", "services": "Service Now", "integration_types": "Webhook","enable":true,"meta_data": []}}

S3 (To support new connection -> Storage)
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d { "url": "null", "secret_id_with_addon": {"id": "e4299bf6-0d5d-490c-9352-c61ff707b455", "services": "S3", "integration_types": "Storage","enable":true,"meta_data": [{"key": "bucket", "value": "newtest"},{"key": "region", "value": "us-east-2"}]}}

Minio (To support new connection -> Storage)
curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations/test' -d { "url": "http://<IP_ADDRESS>:9000", "secret_id_with_addon": {"id": "e4299bf6-0d5d-490c-9352-c61ff707b455", "services": "Minio", "integration_types": "Storage","enable":true,"meta_data": [{"key": "bucket", "value": "newtest"}]}}

Response

{"success": true}

Update data-feed integration

Request

curl -sSkH "api-token: $(get_admin_token)" -X PATCH 'https://a2-dev.test/api/v0/datafeed/destination/${id}' -d '{"id":286,"name": "Minio","url":"http://<IP_ADDRESS>:9000","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services": "Minio","integration_types":"Storage","enable": false,"meta_data":[{"key":"bucket","value":"bucket_name"}]}'

Response

{"id":"286","name":"Minio","url":"http://<IP_ADDRESS>:9000","secret":"38796b44-1821-4a8a-9002-4d9cd976871f","services":"Minio","integration_types":"Storage","enable":false,"meta_data":[{"key":"bucket","value":"bucket_name"}]}

List data-feed integration

Request

curl -sSkH "api-token: $(get_admin_token)" -X POST 'https://a2-dev.test/api/v0/datafeed/destinations' -d ''

Response

{"destinations": [{"id": "369","name": "S3","url": "null","secret": "ee9bdf41-dd6f-4f92-8f1a-15f46d5b0367","services": "S3","integration_types":"Storage","enable":true,"meta_data": [{"key": "region","value": "us-east-2"},{"key": "bucket","value": "s3.to.elastic.search"}]}]}

List data-feed config

Request

curl -sSkH "api-token: $(get_admin_token)" -X GET 'https://a2-dev.test/api/v0/datafeed/config' -d ''

Response

{"feed_interval": "0.016667","node_batch_size": "50","updated_nodes_only": true,"disable_cidr_filter": true,"cidr_filter": ["<IP_ADDRESS>/0"],"accepted_status_codes": [200,201,202,203,204]}

:white_check_mark: Checklist
All PRs must tick these:

[x] I have read the CONTRIBUTING document.
[x] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[x] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[x] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[x] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[x] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[x] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[x] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

Deleting the package-lock.json from the original repository will cause version issues. Please don't delete it from the repo instead try removing that file from the commit

have resolved the issue of package-lock.json

In List data-feed config response, how why do we get decimal values for feed interval, isn't there a way to get the actual values what we set in the config. Also please indent the proto files properly with 2 spaces instead of 4

I have done changes of instead in proto file and done changes of data-feed config response before I use to only sending hours in feed interval now I am sending whole data
{
    "feed_interval": "1m0s",
    "node_batch_size": "50",
    "updated_nodes_only": true,
    "disable_cidr_filter": true,
    "cidr_filter": [
        "<IP_ADDRESS>/0"
    ],
    "accepted_status_codes": [
        200,
        201,
        202,
        203,
        204
    ]
}

In List data-feed config response, how why do we get decimal values for feed interval, isn't there a way to get the actual values what we set in the config. Also please indent the proto files properly with 2 spaces instead of 4

I have done changes of instead in proto file and done changes of data-feed config response before I use to only sending hours in feed interval now I am sending whole data
{
    "feed_interval": "1m0s",
    "node_batch_size": "50",
    "updated_nodes_only": true,
    "disable_cidr_filter": true,
    "cidr_filter": [
        "<IP_ADDRESS>/0"
    ],
    "accepted_status_codes": [
        200,
        201,
        202,
        203,
        204
    ]
}

Thanks shaik, this looks good

@shaik80 can you confirm this PR changes are working with Existing UI, and existing Data of old data.


First commit new multi-thread component and simple implementation.

Starting from your tutorial Processing data in parallel, I generalized the solution to allow the user to easily create a multi-thread job. Starting from the base structure provided from ForkJoin class, the user must provide the number of threads want create to process the work and the implementation for methods that create the three macro jobs: fork-job, workers-job and join-job. The user could also choose to enable JMX monitoring and provide custom listener.
To simplified the use that match your tutorial, I also created a simple implementation represent into SimplifiedForkJoin class. Here the base operations like dispatch the records in the queues, add and remove Poison records, read and write from the queues are provided out of the box. Extending this class, the user customize the three macro jobs adding new components at each JobBuilder.
At the moment the flow work well but exist two issues:

If I choose to enable JMX monitoring and I create more than four thread, randomically the creation of some JobMonitorProxy fail with this error:
...org.easybatch.core.jmx.JobMonitorProxy run SCHWERWIEGEND: Unable to listen to job monitoring notifications javax.management.InstanceNotFoundException: org.easybatch.core.monitor:name=...
I haven't found a solution.

I haven't found an easily way to create a basic "progress listener" could be enable to show the progress of each workers-job and/or all ForkJoin job.

I saw only in second instance that also you started to develop a branch to introduce this function, you adopt different approach but we share some points. Maybe we can works to merge both solution in one.

Coverage decreased (-3.4%) to 76.966% when pulling 61d556733957be822e9fb588092554600748d7f8 on DanieleS82:feature/forkjoin into a5a0c61c254a3674497c8348d247009bd8112e56 on j-easy:master.

Hi,
Thank you for this PR.
I had the same idea and I was trying to write a similar ForkJoinJob. See the prototype in fork-join-jobs branch here: https://github.com/j-easy/easy-batch/commit/b497b7c9b47754d4806f69e79fb4b8aeb3332dd4
What do you think?
Kr
Mahmoud

Hi,
looking the classes ForkJob, ForkJoinJob and JoinJob, I had the impression that some block of code are very similar, I think this is good. My solution compare to your, enable the user to create Job very flexibility. The good thing of your solution is you think all like a Job, so in theory you can use only one component, also if maybe have no sense, but is possible. My solution is thinked as out of box solution, you implement the class that do always the same three things, split record, process them and merge them. I can also think my solution use your components.
In your solution is missing, at the moment, the possibility to setup a job monitoring, but is easy to do. Remain to check if also your solution have the same problem of my when create multiple monitoring. Correct me if I told someting of wrong.
What do you think?

Hi @DanieleS82 ,
Your solution is also good! Basically you provide a template method for a fork/join job which is nice 👍 My idea was to have 3 basic jobs and compose them to create a fork join job (so every part is a job).
But I will try to address the monitoring issue and get back to you asap.
Kr
Mahmoud

Hi @DanieleS82
As I said here, your idea of a template method is definitely better than having multiple jobs to implement fork/join model.
But since you have based your PR on the tutorial (which uses multiple jobs), your template class uses multiples jobs.
The ideal case is to have a MultiThreadedJob class in Easy Batch in addition to the BatchJob class which implements the fork/join model using a single job.
Hence, I think we can close this PR and see how to implement this class differently.
What do you think?
Kr
Mahmoud

Hi benas,
I agree with you. I'm thinking how to do to improve my solution following your notes. Also because I suspect that the template solution with three jobs is the reason why I have issue whit monitoring function.
For the moment, I proceed to work on this branch.
Kr
Daniele

Hi,
As mentioned previously on this issue  and in issue 299, your idea of a template method with a single job is the right approcach and the retained solution. But since this PR is inspired  by the tutorial in which there are multiple jobs, I'm closing it.
Kr,
Mahmoud


Test

Checklist:

[x] I have read and followed the contribution guidelines.
[ ] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Hey
Please do not make such tests in this repository, instead please make them in your own fork or repository.
Thank you and happy coding.


Support Google Generative AI Provider

Is your feature request related to a problem? Please describe.
Unable to support models other than OpenAI
Describe the solution you'd like
Gemini seems to meet all the requirements
Describe alternatives you've considered
Anthropic also meets the requirements
Additional context
https://sdk.vercel.ai/providers/ai-sdk-providers/google-generative-ai#model-capabilities

Would it be possible to support https://mistral.ai/?

Since Model Capabilities is also checked, support is possible.
https://sdk.vercel.ai/providers/ai-sdk-providers/mistral

I tried it, but some agents are encountering errors.
query-suggestor
APICallError [AI_APICallError]: Function calling with a response mime type: 'application/json' is unsupported
researcher
APICallError [AI_APICallError]: Invalid JSON payload received. Unknown name "maximum" at 'tools.function_declarations[0].parameters.properties[1].value': Cannot find field. Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[0].parameters.properties[1].value': Cannot find field. Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[0].parameters.properties[2].value': Cannot find field.

Thank you for trying !

The gemini-1.5-pro and gemini-1.5-flash models have gone GA, so they were tested again. An error occurs with tool use.
Error: Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[0].parameters.properties[1].value': Cannot find field.
Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[0].parameters.properties[2].value': Cannot find field.
Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[2].parameters.properties[1].value': Cannot find field.
Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[2].parameters.properties[2].value': Cannot find field. [] true

There is no issue when running a simple sample with the google provider. Since the tool use is set directly in researcher, it seems necessary to fix that.

Error: Invalid JSON payload received. Unknown name "default" at 'tools.function_declarations[0].parameters.properties[1].value': Cannot find field.
This error was resolved by modifying the schema.
However, the following error occurs.
query-suggestor
APICallError [AI_APICallError]: Function calling with a response mime type: 'application/json' is unsupported

it is now possible to support https://mistral.ai/


Update Package.resolved with swift-collections-benchmark package

Replace this paragraph with a description of your changes and rationale. Provide links to an existing issue or external references/discussions, if appropriate.
Checklist

[x] I've read the Contribution Guidelines
[x] My contributions are licensed under the Swift license.
[x] I've followed the coding style of the rest of the project.
[ ] I've added tests covering all new code paths my change adds to the project (if appropriate).
[ ] I've added benchmarks covering new functionality (if appropriate).
[x] I've verified that my change does not break any existing tests or introduce unexplained benchmark regressions.
[x] I've updated the documentation if necessary.

This PR makes https://github.com/apple/swift-collections/pull/13 obsolete

@swift-ci test


Discarding two instead of acing one

Crushing Inevitability and Pinned Down
Name of the card for which the bug is reported. Delete if not applicable.
I played both cards in the same shootout and the automaton discarded two dudes instead of acing one.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Do action '...'
Click on '....'
Start shootout '....'
See error

Screenshots
If applicable, add screenshots to help ex

plain your problem.
Additional context
Add any other context about the problem here.

Just pointing out that neither Crushing nor Pinned Down require the targeted dude to be "aced". Each of those cards require a dude to be chosen as a casualty. If both targeted the same dude, as long as that dude was discarded as a casualty along with any other dudes to satisfy covering the casualties cleanly it should be ok.
If the targeted dude with either of those effects wasnt chosen as a casualty at all, then that's a problem.
Not sure if this is relevant or not, but this was also part of the last compendium:
"If multiple effects have been played that claim the first casualty, the player selecting that
casualty can select which applies. Once that first casualty has been chosen, any other
effects currently in play that require a dude to be selected as the first casualty are ignored."


GHC 8.4 package overrides

Motivation for this change
Supply a set of fixes to make more packages buildable with GHC 8.4-alpha2.
Things done

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

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

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

@peti, I believe I have addressed your suggestions.
I can't vouch 100% on the necessity of these overrides, since they are auto-generated, and there's lots of things to keep in mind -- heuristics can only go so far.


How detect offset?

Hello.
I use react-measure to detect dimensions and offset changes in my case.
Main idea: Have a visible list and list of hidden items;
But I have no way to track offset changes.
I created demo: https://codesandbox.io/s/modest-list-omkl0
I have a list like this:
And if add some element:
No one after the new element does not touch onResize callback. Yeah, dimensions stay without changes but bounds (offsets) have been changed.
Any ideas?

Weird! I'm not sure why it's not calling onResize properly 🤔 Everything looks fine in your code. I noticed you are using hooks. You might have better luck with something like use-measure library. I'm hoping to release a hooks version soon that might help here. I'll dig deeper when I get some time. Thanks for filing an issue and putting together a code sample! 🙏

@souporserious thanks for the answer. Use measure-hook it`s a clever idea. Let`s test it!
https://codesandbox.io/s/modest-list-56t7e
Good news - now we know about the change position.
But we have strange behavior - equivalents x values for all items. And the right value obviously.

@cvpcasada can you help me? Maybe I use use-measure wrong?


Add Filter&Alarm !Exists CloudTrail Changes query

Added new query for AWS CloudFormation.
Provide a CloudFormation resource and a resource to ensure that CloudTrail Changes are catched by a log metric filter and an alarm
Closes #1161

Please fix unit tests first @fabioGoncalvesCx

Scan submitted to Checkmarx

Checkmarx SAST - Scan Summary & Details
Cx-SAST Summary
Total of 4 vulnerabilities 0 High 3 Medium 1 Low 0 Info
Violation Summary
 3 Medium
View more details on Checkmarx UI
Cx-SAST Details

Lines
Severity
Category
File
Link

30
Medium
Path_Traversal
cmd/builder/main.go
Checkmarx

80
Medium
Denial_Of_Service_Resource_Exhaustion
test/main_test.go
Checkmarx

52
Medium
Denial_Of_Service_Resource_Exhaustion
pkg/kics/service.go
Checkmarx


Run CI on each PR

Bors is gone.

@LenkaNovak, when this has merged, can you try merging a new PR that removes bors.toml to check that everything works as you would expect?
To merge, you can just click the "Enable auto-merge" button on your PR.

I'll do that, thanks @Sbozzolo

I'll do that, thanks @Sbozzolo

The CI is failing and it seems that there's something wrong in ClimaCoupler. Have you seen this before?

Not until this morning (I was just testing if it's just my own branch but it looks like even the main is affected). It was fine on Friday. I can't reproduce this locally, and checking in my local Manifest (as a test) didn't help. Any idea what's changed? @charleskawczynski @simonbyrne

Not until this morning (I was just testing if it's just my own branch but it looks like even the main is affected). It was fine on Friday. I can't reproduce this locally, and checking in my local Manifest (as a test) didn't help. Any idea what's changed? @charleskawczynski @simonbyrne

Ahh, the ClimaAtmos release is probably the culprit. I'm pinning to Atmos 0.16.2 now.

Not until this morning (I was just testing if it's just my own branch but it looks like even the main is affected). It was fine on Friday. I can't reproduce this locally, and checking in my local Manifest (as a test) didn't help. Any idea what's changed? @charleskawczynski @simonbyrne

Ahh, the ClimaAtmos release is probably the culprit. I'm pinning to Atmos 0.16.2 now.

Hmm, still breaks!

Now that I think about it, for Clima packages we should pin to the specific patch version we've most recently updated to, since patch releases can introduce breaking changes.
Could this failure be due to not having compats for standard library packages?

Now that I think about it, for Clima packages we should pin to the specific patch version we've most recently updated to, since patch releases can introduce breaking changes.
Could this failure be due to not having compats for standard library packages?

Thanks for chiming in, @juliasloan25 ! This is a good point and I agree we should do this. I'm not sure which package is causing this yet though. I've tried to pin all of the major ones and it hasn't worked for me yet... But having cleared my local .julia, I can now reproduce this locally!

Now that I think about it, for Clima packages we should pin to the specific patch version we've most recently updated to, since patch releases can introduce breaking changes.

Patch releases should not introduce breaking changes. If they do, please report them (we should learn to be more mindful about this).
There was at least one mistake on ClimaAtmos side. 0.16.3 should have been breaking because all the cache stuff has changed.

Could this failure be due to not having compats for standard library packages?

No, I think that only affects the registrar.

https://github.com/CliMA/ClimaCoupler.jl/pull/493#issuecomment-1797069509 cc @sriharshakandala

#493 (comment) cc @sriharshakandala

Looks like this was missed. It should have been tagged 0.17 if this was a breaking release!. We can tag 0.17 in the next day or so!


[META] Document Level Alerting

What problem are we solving?
Document returning alerts provides the ability to alert on each document in the index. Additionally the document returning monitor ensures that between monitor executions, there is no gap or overlap in data being monitored. With the existing monitor types in Alerting (Query Level and Bucket Level), we alert on a summarized view on the data, however, we never know which are the specific documents or records in the index that are triggering an alert in the monitor. Document level alerts also solves a common frustration where there are monitoring gaps or data overlaps based on timestamps.  The new monitor type will alert based on each document.  The findings store metadata information to note all the documents that match the trigger conditions into a new index called the Findings index for later reference.
Users want to find the documents that match their fields value to a specific set of predefined values. Predefined values are defined as the rules and are typically in order of 100s to 1000s. One example is - find the log messages whose  field source.address value equals to  <IP_ADDRESS> and field response.status is 401:Access Denied. This type of field level signature detection is common in security detections.
How to set it up
Setting up a document level monitor will be fairly similar to the other existing monitor types. To create a document returning monitor, you can run the following command:
Note - before the release of the feature, the model definition can slightly differ.
POST _plugins/_alerting/monitors
{
  "type": "monitor",
  "monitor_type": "doc_level_monitor",
  "name": "iad-monitor",
  "enabled": true,
  "createdBy": "chip",
  "schedule": {
    "period": {
      "interval": 1,
      "unit": "MINUTES"
    }
  },
  "inputs": [
    {
      "doc_level_input": {
        "description": "windows-powershell",
        "indices": [
          "test-logs"
        ],
        "queries": [
          {
            "id": "sigma-123",
            "query": "region:\"us-west-2\"",
            "tags": [
              "MITRE:8500"
            ],
          },
          {
            "id": "sigma-456",
            "query": "region:\"us-east-1\"",
            "tags": [
              "MITRE:8600"
            ],
          }
        ]
      }
    }
  ],
    "triggers": [ { "document_level_trigger": {
      "name": "test-trigger",
      "severity": "1",
      "condition": {
        "script": {
          "source": "'sigma-123' && !'sigma-456'",
          "lang": "painless"
        }
      },
      "actions": []
  }}]
}

Limitations

If the index is being reindexed, the next few monitor execution runs until after it is reindexed will give incorrect results. After the index is done being reindexed, it will have one last run of incorrect/repeated results. After that, the new data coming to the index will be be monitored correctly by the document returning monitor.

@lezzago This is still going into 2.0?

@lezzago This is still going into 2.0?

@dblock Yes this is going into 2.0

@lezzago What's left to close this issue? If it's documentation, let's close this here?

Closing issue as Document Level Alerting is feature complete for 2.0.


Bug: Select option showing multiple selected

When switching multiple times (3 times) on the options given, this somehow gives me that there are two options were selected, which obviously is wrong. Or maybe I'm just missing something here?

template snippet
        <ion-item *ngIf="eventPhotographers.data.length && !fetchingPhotographers">
          <ion-label padding-top>Photographer</ion-label>
          <ion-select
              [(ngModel)]="photographer.id"
              (ionChange)="onSelectPhotographerChange($event)"
              multiple="false"
              formControlName="user_id">
            <ion-option [value]="eventPhotographer ? eventPhotographer.id: null" *ngFor="let eventPhotographer of eventPhotographers.data">
              {{eventPhotographer.staff.name}}
            </ion-option>
          </ion-select>
        </ion-item>

function snippet
  onSelectPhotographerChange(eventPhotographerId) {
    const selectedPhotographer = this.eventPhotographers.data.find((eventPhotographer) => eventPhotographer.id === eventPhotographerId)
    if (selectedPhotographer) this.teamSignOffForm.patchValue({ user_id: selectedPhotographer.id })
    console.log(this.teamSignOffForm.value)
  }

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Ionic Framework Version: 2.2.0
Ionic CLI Version: 2.1.8
Ionic App Lib Version: 2.1.4
Ionic App Scripts Version: 1.1.4
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 2.6
Node Version: v6.10.3
Xcode version: Not installed

I don't understand why you are setting things in two different ways. Wouldn't it be considerably simpler to simply have [value]="eventPhotographer" on each <ion-option> and forgo the change handler entirely?

Hello,, did you found a solution for that,  I'm facing the same issue.


Cryptodome not installed when it is.

This is under Python 3.10.
steven@HP15:~$ pip3 list
Package                Version
---------------------- -------------
pycryptodome           3.15.0
wyze-sdk               1.6.0

steven@HP15:~$ python3 dowyze.py
Traceback (most recent call last):
  File "/home/steven/dowyze.py", line 2, in <module>
    from wyze_sdk import Client
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/__init__.py", line 3, in <module>
    from .api import Client  # noqa
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/api/__init__.py", line 1, in <module>
    from .client import Client  # noqa
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/api/client.py", line 4, in <module>
    from wyze_sdk.api.base import BaseClient
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/api/base.py", line 6, in <module>
    from wyze_sdk.service import (ApiServiceClient, EarthServiceClient,
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/service/__init__.py", line 1, in <module>
    from .api_service import ApiServiceClient  # noqa
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/service/api_service.py", line 12, in <module>
    from wyze_sdk.signature import RequestVerifier
  File "/home/steven/.local/lib/python3.10/site-packages/wyze_sdk/signature/__init__.py", line 3, in <module>
    from Cryptodome.Cipher import AES
ModuleNotFoundError: No module named 'Cryptodome'

Hey @stevenwbuehler,
I specifically declare pycryptodomex (note the x at the end) in the Pipfile. I don't know too much about these modules, but it does appear that the pycryptodomex dependency calls its modules the same as the other pycryptodome library.
Maybe give that a shot?

That worked. There is also a module called pycrytodome (without the x at the end), so you may to include in your install instructions the correct module to install. :-) Thanks for your quick help!


Amount of Invoices in a Single City

Given the city (prefeitura) X, we would like to have a breakdown of those values:
It's the amount of invoices issued in that city, basically a count from all invoices where competencia = x.

Related to #60

By the graph presented, I'm assuming we also need to filter by month/year and then aggregate those invoices counts by day,  right? To return a list of [(day, count)].

Yes.
Em qui, 18 de jul de 2019 13:07, David Beyda<EMAIL_ADDRESS>escreveu:

By the graph presented, I'm assuming we also need to filter by month/year
and then aggregate those invoices counts by day, right? To return a list of
[(day, count)].
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sdec-brasil/dashboard/issues/61?email_source=notifications&email_token=ACYLJFG6TO5J2MBINOGWXADQACILJA5CNFSM4IAK2EWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2I7J7Q#issuecomment-512881918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYLJFGRX5AYP37QEOWPZXTQACILJANCNFSM4IAK2EWA
.

Yes

Request:
GET /v1/cities/1100015/daily-issuing?month=7&year=2019
Response:
{
    "city": {
        "codigoMunicipio": "1100015",
        "cnpj": "18511471000120",
        "municipio.codigoIbge": "1100015",
        "municipio.nome": "Alta Floresta D'Oeste",
        "municipio.uf": "RO",
        "municipio.nomeRegiao": "Leste Rondoniense",
        "municipio.estado.sigla": "RO",
        "municipio.estado.nome": "Rondônia",
        "municipio.regiao.nomeRegiao": "Leste Rondoniense",
        "municipio.regiao.uf": "RO"
    },
    "dailyIssuing": [
        {
            "dataIncidencia": "2019-05-21",
            "emitedInvoicesCount": 3
        },
        {
            "dataIncidencia": "2019-05-23",
            "emitedInvoicesCount": 4
        },
        {
            "dataIncidencia": "2019-05-25",
            "emitedInvoicesCount": 5
        },
        {
            "dataIncidencia": "2019-05-26",
            "emitedInvoicesCount": 5
        },
        {
            "dataIncidencia": "2019-05-27",
            "emitedInvoicesCount": 2
        },
        {
            "dataIncidencia": "2019-05-28",
            "emitedInvoicesCount": 4
        },
        {
            "dataIncidencia": "2019-05-29",
            "emitedInvoicesCount": 1
        },
        {
            "dataIncidencia": "2019-05-31",
            "emitedInvoicesCount": 6
        }
    ]
}

Note that days with zero invoices are no shown in the query. I suggest that this should be treated in the front-end, since seems like an easy fix. In the backend, we are currently just using Database functions and returning the result. Treating this in the backend would add some overhead to the response time.

off-topic: we need to fix that city endpoint and property names after, it's pretty ugly lol


Baskerville / wandb integration

It occurs to me that there might be issues with logging in to wandb from Baskerville, so if people are using Baskerville for the model validation we might need to create a two step process - run the validation on Baskerville and return then output. Then run the wandb step on that returned output on a personal computer. (It might work fine however)

I tested using the model validation process from Baskerville last week for some optical flow models, and there was no issue running it wandb step


Add support for Vimeo, Soundcloud

Hi, thanks again for writing this. I use it daily as a kind of webradio player (run it on this page - endless music discovery!).
How add would it be to add support for more sites? I was mainly thinking about http://soundcloud.com and http://vimeo.com. If it could be extended to support as many sites as youtube-dl it would be great, although that would certainly be a huge amount of work. Those 2 sites only would make my day.
What do you think?

I just now discovered this, and it's AWESOME. I'd love to see a soundcloud one, if you do end up having a chance.

Unmaintained project, closing.


Trouble installing GUI dependencies with Zsh [SOLVED]

Hi, I ran into a small problem with install this morning and wanted to mention it in case it helps others. I didn't know this, but zsh uses square brackets for pattern matching, so installing the gui dependencies with pip doesn't work. It will work if you put the search in quotes though:
pip install 'cellpose[gui]'
The error that zsh throws is vague... it says no matches found, and I didn't immediately realize it was zsh complaining instead of pip. It may be worth throwing the quotes around the command in the Readme, since it should work even when not using zsh. It's really on me though, I guess I need to learn the full power of my own shell...

Thanks for posting this! We need to add it to the documentation.

thanks! added these instructions to the readme


HHH-10668 - Add SQL dialect for SQLite 3

Thanks for the PR. I'm going to review it.

Hi @gwenn ,
You should discuss the new Dialect with @sebersole. I asked about integrating this Dialect , and this is the response that I got. Basically, you need to add a JIRA issue and then the Dialect is going to be integrated only if there is demand from the community for it.
Vlad

Are there any news about this issue? I am interested in it, too.
I think there actually is demand for this feature, as one can see searching in github.

@luca-vercelli I think you have a very good point. I asked on the mailing list if anyone opposes integrating it, and, otherwise, I'll integrate it this week.

@gwenn As discussed on the mailing list, the only concern is related to Dialect maintainability on the long run.
Are you willing to contribute to the SQLite Dialect to accommodate upcoming features or fixing issues? If you agree, then we can integrate it in hibernate-core.

Sorry,
I didn't reply for several reasons.

For the third point: "The community demands it", I don't see how I can do anything.

For the second point: "Someone or some entity is willing to maintain it long term",
I can help but the current implementation has many limitations (SQLite has a dynamic type system (column declared type does not mean anything except giving an hint on affinity), has a very limited ALTER TABLE command and JDBC drivers are not compliant).
So I am afraid that intractable issues will created.

And I don't think Hwaci will be interested to maintain Java code.

And I have limited internet access from my computer at work, and a single old laptop at home; I am not subscribed to any Hibernate topic. So testing/following the huge Hibernate ORM project is difficult to me.

To sum up, I am afraid you are asking too much of me (or I misunderstood) !

Thanks, @gwenn for your reply. I think we should postpone the integration until the SQLite JDBC Driver is complaint and we have someone to lead this Dialect integration.
Meanwhile, the SQLite Dialect can still be used as a 3rd party API.

Dear @gwenn and @vladmihalcea , I can understand your point, anyway I do not agree with you.
I know that JDBC drivers for SQLite are bad so far, however this is their problem, not Hibernate's.
If you want, I could give "long term support" for this simple class (SQLiteDialect.java), not for JDBC driver. I think issues concerning the drivers must be sent to their developers.
The more, not all features of SQLite can be handled by Hibernate, but this is not a big problem IMHO. For example, Oracle's stored procedures are a great feature which is badly supported by Hibernate, anyway this is not a good reason for removing Oracle's dialect!

@luca-vercelli It's just a matter of resources. The Hibernate ORM is developed by a handful of people that need to work on new features, fix issues, answer questions on our forum and StackOverflow, write documentation, write blog posts, and so on.
We can cover the most common RDBMS you'll find in a typical enterprise system, but our bandwidth is limited. So, when you have limited resources, you need to prioritize, which is exactly the reason why we cannot accept a new Dialect unless there is someone who is willing to take responsibility for it.

If you want, I could give "long term support" for this simple class (SQLiteDialect.java)

That's good news. What we need besides this new dialect class Dialect can be summarized as follows:

a new entry in databases.gradle for sqllite with a typical connection property configuration
a test dependency in libraries.gradle for sqlite-jdbc
in build.gralde, we also need the testRuntime( libraries.sqllite) to include sqlite-jdbc di=uring testing

To test how all tests run on the new SQLite dialect, just run:
> gradle clean test -Pdb=sqllite

where sqllite is actually the key of the entry you added in databases.gradle.
@luca-vercelli Please send me a new Pull Request based on this one that adds the aformentioned changes, and which runs fine on SQLite. Then, I'll tested it and integrate it.


508: Fix focus in MP table/grid with multiple sections

Locations:

Location Attributes and Relationships
Methods
Qualifications
Unit Information

Issue:
When a user collapses then expands the lower sections of the grid (Supplemental Methods), the focus goes to the top most section (methods)

Testing complete, focus now stays on the collapsible elements


Feature Request: Cache instance ids

so you can join ones that are full

I don't this will be useful because if the instance isn't being reported by the API then player count will be inaccurate, so it will just end up being a large list of likely dead instances.

Well, most of the instances in my case were full for some more hours. If i wanted to visit them i always had to write down their ids and use the create new instance button and enter the id then send myself an invite to those

aint this basically what reading output log does? just  find the instance in vrcx game log and just invite yourself back?


How to add pagination to a sidebar inside a single post

At the moment I have a single post page displaying the post. In a sidebar I want to display all posts with a pagination (15 posts per page).
The single post is displayed. And in the sidebar I become 15 posts. But the pagination is not there. I checked the Debug bar but the Array is empty. Is this because it's not allowed? Or i'm doing something wrong? I checked the wiki and used the global $paged, but no success.
single.php
<?php

//sidebar post + pagination
global $paged;
if (!isset($paged) || !$paged){
    $paged = 0;
}

$context = Timber::get_context();

$args = array(
	'post_type' => array('post','feature','decider'),
	'posts_per_page' => 14,
	'orderby' => 'latest'
);

$context['all_posts'] = Timber::get_posts($args);
$context['pagination'] = Timber::get_pagination();

// single post
$post = new TimberPost();
$context['post'] = $post;
$context['acf'] = get_field_objects($data["post"]->ID);

// single post ad
$args_ad = 'post_type=ads&category_name=post-ad&numberposts=1&orderby=latest';
$context['ads_post'] = Timber::get_posts($args_ad);

// search related posts with tags from this post
$tags = $post->tags();
$search_tag = $tags[0];

$templates = array('single-' . $post->ID . '.twig', 'single-' . $post->post_type . '.twig', 'single.twig');
Timber::render($templates, $context);

Somebody sees what I'm doing wrong?

Hi @paul-straetmans - is this still an issue?
Thanks

As this seems inactive I am going to close this for now. If this is still an issue please post it on Stackoverflow under the Timber tag.
Thanks


ServiceBus: Remove line breaks in markdown

Some of our markdown documents have line breaks. They are not necessary for markdown because of workwrap mechanics of markdown renderers. See comment here: https://github.com/Azure/azure-sdk-for-net/pull/13537/files/9aa47b23f7d3b41d7cdb8a46033d4360d5b4c8ba#diff-e36ac6529b4db622a88ab1e3cd8f8825

@MiYanni can you take this one?


WIP implementation of Danksharding

https://notes.ethereum.org/3t5cbN7cQnG6VxjgNMKymA

Notes from a chat with @JustinDrake @dankrad @hwwhww :

Rename "intermediate block" -> "builder block", and the other kind of block can be a "proposer block" (right now there isn't a good term for non-intermediate blocks)
Rename "eth1 signature" to "execution signature"
Add a concept of "hash of a sharded commitment"; only the last 31 bytes should be a hash, the first byte can be a version number. The commitments in the execution layer should be in this version+hash form.

There is some inefficiency, because data is repeated (N hashes in the execution layer, 2N commitments in the consensus layer), but now it's only 33% overhead instead of 50%, and removing this requires too much tight coupling between consensus and execution and risks increasing dev time
Another good reason to do the version-and-hash format on the execution layer is that in the future, we might switch to a different commitment scheme (eg. STARKed Merkle root), and we want to preserve the format of a commitment in that case

The IntermediateBlockBidWithRecipientAddress class could be removed if we move the ethereum_address out into the IntermediateBlockData. But this requires the execution_engine.execute_payload call to take two lists instead of one. It could nevertheless be a net reduction in complexity; worth exploring but not 100% sure.
Add a max number of unprocessed beacon blocks included into a builder block's commitment list, and do a FIFO queue to process them.
Think through the consequences of unprocessed block mechanics for weak subjectivity (maybe no consequences at all if all unprocessed beacon blocks are in the state)
Many things could be simplified quite a bit if we add virtual blocks (auto-generated execution blocks containing zero transactions that get inserted during any builder slot without a real execution block)
There are high capital requirements to requiring the builder to be an active validator. What if we just require the builder to be a non-exited non-slashed (possibly inactive) validator with at least 1 ETH, to reduce capital intensity while preserving enough slashable ETH for anti-DoS purposes? This would mean that it's possible for the proposer to be inactive; need to check that this is ok (probably is)

How attestation works:

Each epoch you get assigned to 2 rows and 2 columns, and you only accept a block if those rows and columns are fully available for all slots since the last slot since you attested for (if we add PoC, this would also be the PoC data)

This ensures that if a block is unavailable (>50% of rows and >50% of columns missing), >75% of all validators would stop voting for that chain

On the fork choice rule:

Current favourite is (block,slot), with equal committees, and a 3/4 proposer boost. (Different committees are less attractive because they lead to favouring the proposer and builder collaborating and publishing the proposer block late to get more MEV)
A backoff scheme can be based on previously muissing slots. It should work like this:

Remove the requirement that the builder block is the next slot (it can be published in any slot as long as there were no beacon blocks in between
Require a number of empty slots between beacon blocks (do not require that the beacon blocks are at fixed block heights)
Base back-off on %age of missing blocks

Need to add previous block root to bid cc: @CarlBeek

[ ] Explore possibility that builders do not need to be bonded by P2P censoring duplicate blocks
[ ] p2p spec for bids: only allow buds that increase by a minimum of 1%
[ ] remove RANDAO from builder blocks

@dankrad is this still relevant or would we instead build full dank-sharding off of 4844 specs?

@dankrad is this still relevant or would we instead build full dank-sharding off of 4844 specs?

4844 only implements a small subset of this. So it seems a bit unnecessary to throw it away only to dig out the old PR when we want to implement full sharding. I suggest I take a couple of day to process the outstanding comments and then we merge it into the sharding directory?

Now ready for merge @djrtwo

Does it make sense to rebase/squash the commits a bit? Or even do "Squash and merge"?