Don't generate SwaggerException

It would be nice that ether there is no export for SwaggerException or parameter how can I set one type excluded from export. This is problem when I'm generating one Angular service per one controller. When I use these services I need to modify generated code by removing export manually from SwaggerException. Problem is that every service has its own SwaggerException. So I cannot use index.ts for exporting services from module. If I set SwaggerException in excludedTypeNames code get broken because there is still parts where SwaggerException is used.
So ether I need way to exclude some types from export list. It could be combination of excludedTypeNames and exportTypes. So list where I can specify which Types I don't want to export.
Other solution is that there is no exception handling in service in first place. (or parameter for this)
And last solution is that you use HttpErrorResponse from @angular/common/http instead of SwaggerException.

You can exclude it with the ExcludedTypeNames setting

As I said.
"If I set SwaggerException in excludedTypeNames code get broken because there is still parts where SwaggerException is used."
So it will exlide SwaggerException

Sorry I acidentally closed this.

This exception is always used by the generated code... with the exclude option you can only disable the generation of the class itself... is the problem that it is trying to export it? If the import of your custom implementation is missing then you need to create an extension code file and add the custom import there

Yes my problem is that SwaggerException is exported always.
One option could be that I can control what classes will not be exported. So it works like exportTypes boolean, but instead of this it would be excludeExportTypes. In that wat SwaggerException will be there but it won't be exported. Configuration could be this.
excludeExportTypes: [ "SwaggerException" ]
Problem is that it is much easier that I can exclude exports than list all exported classess and stuff from service. My Angular library's public_api.ts is looking this.
export * from './lib/services/Configuration-service';
export * from './lib/services/Localization-service';

So if both services will export SwaggerException here will be conflict.
I didn't get this:

If the import of your custom implementation is missing then you need to create an extension code file and add the custom import there

i don't want generate the status code check too ,because the fetch  features do not throw exception when status code like 400,401 。。。i want do the logic in my code #2006

This exception is always used by the generated code...

That's what is being challenged: Why? The very core fundamental of HTTP is the response codes. Why does NSwag assume an exception for everything that is >399, or sometimes worse.. not 200 or 204?
Anyway.. that's what is being asked for here. This is a feature request, not a question. Ability to disable exception generation. We can already wrap responses, and it seems fundamentally broken that this only applies to what NSwag arbitrarily considers a "success".

Why does NSwag assume an exception for everything that is >399, or sometimes worse.. not 200 or 204?

Mainly because C# can only have one return type and we tried to generate idiomatic C# - that's why we assume that everything except 2xx is an exception. This is how the templates work, i.e. we try to abstract away HTTP so that we only have "plain" C# interface - if you don't like you should look at AutoRest which generates more HTTP specific code I think.

        try
        {
            var result = await client.GenerateAsync(parameters.Foo, parameters.Bar);

            return result.StatusCode == (int) HttpStatusCode.OK
                ? result.Result
                : null;
        }
        catch (ApiException)
        {
            return null;
        }

That try {} catch {} is what is clunky when wrapping the responses. Infact I argue it makes the entire feature of wrapping of responses pointless.

Yes, for wrapping of responses it would make sense to not throw exceptions..


To: field does not get changed in Tutorial?

Hi,
I have followed the tutorial for creating plugin.  Everything went as stated in the tutorial.  However when I checked the /tmp/mail.eml file, the To: field did not get changed as shown on the console.
(Haraka/1.0.1) with ESMTP id 2DD04FCA-75EB-454A-9B88-2943321D8767;
Fri, 11 Nov 2011 09:27:00 -0500
Date: Fri, 11 Nov 2011 09:27:00 -0500
To<EMAIL_ADDRESS>From<EMAIL_ADDRESS>Subject: test Fri, 11 Nov 2011 09:27:00 -0500
X-Mailer: swaks v20100211.0 jetmore.org/john/code/swaks/
I am curious what was changed and how does the next phase picks up the change to deliver the mail to the changed address?  Thank you for your help.

See my answer to issue #120.


Typo fix

Fixed a typo.

@dplusplus1024, remember to re-request review from reviewers when ready

@dplusplus1024, remember to re-request review from reviewers when ready

@dplusplus1024, remember to re-request review from reviewers when ready

@dplusplus1024, remember to re-request review from reviewers when ready

@dplusplus1024, remember to re-request review from reviewers when ready

@dplusplus1024, remember to re-request review from reviewers when ready

Replaced by #8375 due to inactivity from original author.


No Servlet Container Info from jolokia info

I try the follow uri:
wget http://localhost:80/jolokia/
response:
{"timestamp":1458205346,"status":200,"request":{"type":"version"},"value":{"protocol":"7.2","config":{"detectorOptions":"{}","canonicalNaming":"true","maxCollectionSize":"0","includeStackTrace":"true","historyMaxEntries":"10","agentId":"<IP_ADDRESS>-6044-1526c3d4-servlet","debug":"false","dispatcherClasses":"org.jolokia.jsr160.Jsr160RequestDispatcher","maxDepth":"15","maxObjects":"0","discoveryEnabled":"false","serializeException":"false","agentType":"servlet","debugMaxEntries":"100"},"agent":"1.3.3","info":{}}}

The info block is empty, why?
Is the a tomcat settings problem?

Hello,
got the same issue.
Environment:

Debian 8.4 Jessie
Tomcat 8.0.14 (installed via apt)
Jolokia 1.3.3 deployed as war-File

The Problem seems to be the pattern in Class jolokia/agent/core/src/main/java/org/jolokia/detector/TomcatDetector.java. This Class evaluates the attribute serverInfo.
In my case serverInfo is set to : "Apache Tomcat/8.0.14 (Debian)"
The Pattern "^\s*([^/]+)\s*/\s*([\d\.]+(-RC\d+)?)" found in TomcatDetector does not match so it returns null.
A fix would be nice because mk_jolokia script from check_mk evaluates productinformation and does container dependend checks if set.
Thanks for your help

Assigned a Pull-Request with changed Regex for this issue.

Sorry, I was too fast (thats not often the case ;-) Thanks for the PR, I'm just pushing a snapshot.
@lgbff what Tomcat are you using ?

tbh, I don't know when I'm going to release 1.3.4, hopefully soon but I don't have much 'material' yet for it.

Thanks for the quick fix. Deleted PR. The release is no problem for me - latest snapshot is all i need.

Quickfix for those who cannot wait until release of 1.3.4:

Create File CATALINA_BASE/lib/org/apache/catalina/util/ServerInfo.properties with Content:
server.info=Apache Tomcat/8.0.14
Restart Tomcat

For details see: https://tomcat.apache.org/tomcat-8.0-doc/security-howto.html#Security_manager

Cool, thx for the tip.
1.3.4-SNAPSHOT has been pushed, please let me know whether it works for you (and reopen the issue if not)


Fix link to secure boot docs

This PR fixes the link in bootloader/README.md to the secure boot documentation on https://www.energietransitiewindesheim.nl/twomes-generic-esp-firmware.

I canceled the workflows, because they don't need to run. I will fix this in another pull request.


Service workspace failed to build

Info:

Docker version ($ docker --version): 1.12.6
Laradock commit ($ git rev-parse HEAD): aa5e8e666683a67a3946b577b2f9293ddf127ced
System (place x between the [ ]):

[ ] Mac
[ ] PC
[x] Linux
Info:

Issue:
I have this problem.
ERROR: Service 'workspace' failed to build: One or more build-args [INSTALL_MSSQL] were not consumed, failing build.

Hi @mrignacio1231
Please upgrade docker version > 1.13
https://github.com/moby/moby/pull/27412

Hi @bestlong How do i do that?

@mrignacio1231 Your OS version is ?

It's 7.1

The problem is in workspace/Dockerfile-71 and php-fpm/Dorckerfile-71 files. They have not mssql installation like as Dockerfile-70,

If you don't need MSSQL,
you can edit workspace/Dockerfils-71 add temporary code befor "Final Touch" section like:
#####################################
# MSSQL (Build pass for Old Docker version)
#####################################
ARG INSTALL_MSSQL=false
ENV INSTALL_MSSQL ${INSTALL_MSSQL}
RUN if [ ${INSTALL_MSSQL} = true ]; then \
    echo 'Just consume INSTALL_MSSQL arg' \
;fi

#
#--------------------------------------------------------------------------
# Final Touch
#--------------------------------------------------------------------------
#

Yes, i did that and work


Fix race condition in io copy

cmd can exit before the io copy finishes
add a wait group so that both stdout and stderr are fully copied
before we exit

Signed-off-by: Natalie Arellano<EMAIL_ADDRESS>

@masterzen @hoenirvili  This fix will allow us to add support for Winrm download to packer. Is there anything you would like us to change?

This looks good to me, I don't see at first glance any adverse effects.


Incomplete install doc

Hello,
I've taken way too long to figure out how to get a docked fabric server working with CrossStitch and Velocity.
It seems that FabricProxy-Lite must have been installed and configured with the velocity secret in order to work, but that doesn't seem to be listed anywhere.
I found a comment in reddit stating that the secret key should be added to the FabricProxy-Lite.toml file.
Perhaps this should be mentioned in the readme, to help beginners like me get by?

CrossStich isn't related to FabricProxy-Lite, it assumes you already have configured forwarding correctly.
If you have not configured forwarding, follow this (or https://github.com/OKTW-Network/FabricProxy-Lite?tab=readme-ov-file#setup):
The velocity secret key is found in the velocity forwarding.secret file (in older version of velocity you may find the secret inside velcoity.toml.
this file:

Then go to your fabric server and paste the contests into the config/FabricProxy-Lite.toml file where I put the red rectangle.


L-06 Test Coverage Gaps

Tests added:

[x] single asset deposit call should revert
[x] multi asset deposit call should revert
[x] setMaxDepositDeviation should work as expected
[x] deposit contains duplicates -> Done in L-01 PR
[x] withdrawal contains duplicates -> Done in L-01 PR
[x] deposit should fail with an unsupported asset
[x] withdrawal should fail with an unsupported asset
[x] deposit should work with any order of the assets
[x] withdrawal should fail when incorrect order
[x] deposit should work with small asset amounts
[x] deposit should fail with too large amounts

Comments on "Suggested Invariants"
These are great points. We are working on this effort separately to achieve a generalized way of testing checkBalance and protocol profitability in cases of strategies utilizing pools (Balancer, Curve or Uniswap). We are primarily focusing on flash loan attacks which could heavily tilt the pool towards one asset, let the transaction (deposit or withdraw) execute and then tilt the pool back (sandwich attack). For now I think we should leave it out of scope for these audit fixes.
Comments on "Absence of Contract-Level Tests (Unit Tests)"
Thanks for these points. There is also an ongoing separate effort to create unit test suite where strategies are tested in a generalized way - testing common strategy behaviours. E.g. approving assets, governance actions, being able to deposit/withdraw only supported assets... For that reason I think this is out of scope for these fixes as well
Audit notes:
Several types of test coverage gaps were identified.
Specific Line Coverage Gaps

In Balancer strategies, lines deposit 1 and deposit 2 are disabled.
setMaxDepositDeviation

Edge Case Gaps

Ensure that both _deposit and _withdraw function as expected or revert when
arguments are in an incorrect order or contain duplicates, unsupported assets, and/or
incorrect amounts. Although the external deposit and withdrawal functions are not
exposed in a way that will enable user inputs, a future change may expose or introduce a
bug with input validation.

Suggested Invariants
-Validate that running checkBalance(address) across all assets, converting the
results to units and summing them up arrives at the same value as checkBalance()
before and after various test scenarios.

Ensure totalValue() remains unchanged by deposits/withdrawals with various
parameters. If it does change, these actions will leak value through rebasing. Although
this is validated in some tests, a more comprehensive validation of the invariant can
catch uncovered edge cases.

Absence of Contract-Level Tests (Unit Tests)
The codebase predominantly depends on fork testing which assesses contract integration,
dependencies, and on-chain state. However, it lacks contract-level (local "unit") tests.
While fork tests are of supreme importance, they do have a number of weaknesses that are
typically addressed via even larger local test suites:

Fork tests require more maintenance due to their reliance on on-chain values (e.g., price
oracles). This makes large and thorough test suites more difficult to maintain.
Fork tests are more difficult to write for edge cases and scenarios that deviate from the
current on-chain state. Thus, they tend to cover edge cases less thoroughly compared to
local test suites.
Fork tests make testing internal logic in an isolated way much more difficult, resulting in
many edge cases in the implementation of base and abstract classes, internal functions,
or internally used libraries being insufficiently covered.
Fork tests are usually slower to run and are thus typically run on CI instead of locally,
extending the length of the development cycle.

Consider creating a comprehensive suite of local tests that are quick to write and run, focusing
on edge cases and internal logic.

Merging this in @DanielVF will apply any fixes in separate branches if required


Packager refuses to finish transfer with react-native-action-button

As soon as I remove the package it works.

I tried to restart the packager, delete node_modules, clear npm cache... nothing helps.

Did you start a new react native app?

Nope, I tried to integrate it to an existing app.
On Jan 10, 2016 19:56, "Yousef Kamawall"<EMAIL_ADDRESS>wrote:

Did you start a new react native app?
—
Reply to this email directly or view it on GitHub
https://github.com/mastermoo/react-native-action-button/issues/22#issuecomment-170374545
.

Can you go into the ActionButton.js file in your node_modules directory and add a semicolon in line 55, right after the propTypes property? Maybe this will fix the issue.

It fixed this issue, now everytime i'm pressing the action button i'm getting the following warning & error:

And while refreshing:

worth to note that none of this errors occur when I remove the action button

My imports:
import React, { Component, View, Text, ProgressBarAndroid, WebView, Platform } from 'react-native';
var ActionButton = require('react-native-action-button'),
  Icon = require('react-native-vector-icons');

My render code:
  render() {
    console.log(this.props);
    var webViewURL = this.props.url + '?source=app';
    return (
      <View style={styles.container}>
        <WebView
          ref="ArticleWebView"
          automaticallyAdjustContentInsets={true}
          style={{flex: 1}}
          url={webViewURL}
          javaScriptEnabled={true}
          startInLoadingState={true}
          renderLoading={this.renderLoadingView}
          scalesPageToFit={true}
          scrollEnabled={true}
          />
        <ActionButton buttonColor="#71bf44">
          <ActionButton.Item buttonColor='#9b59b6' title="שתף" onPress={() => { console.log(this.props) } }>
            <Icon name='android-share-alt' style={styles.actionButtonIcon} />
          </ActionButton.Item>
          <ActionButton.Item buttonColor='#3498db' title="הוסף למועדפים" onPress={() => { console.log(this.state) } }>
            <Icon name='android-star-outline' style={styles.actionButtonIcon} />
          </ActionButton.Item>
          <ActionButton.Item buttonColor='#1abc9c' title="עוד משהו" onPress={() => { console.log(this.state) } }>
            <Icon name="android-done-all" style={styles.actionButtonIcon} />
          </ActionButton.Item>
        </ActionButton>
      </View>
    );
  }


PANIC occurs during bind Insert

Bug Report
What version of KipSQL are you using?
0.0.1-alpha.6
What version of Rust are you using?
❯ rustc -V
rustc 1.76.0-nightly (de686cbc6 2023-12-14)

What's the status of the running?
What did you do?

> 👇👇🏻👇🏼👇🏽👇🏾👇🏿 <
create table blog_1 (id int primary key, title varchar unique, created_at datetime);

+----------------------+
| CREATE TABLE SUCCESS |
+======================+
| blog_1               |
+----------------------+

> 👇👇🏻👇🏼👇🏽👇🏾👇🏿 <
insert into blog_1 (id, title) values (0, 'KipSQL', '2022-10-12 12:22:33');
thread 'main' panicked at /home/jojo/code/open-source/kipsql/src/binder/insert.rs:52:52:
index out of bounds: the len is 2 but the index is 2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

What did you expect to see?
Insert bind fails with error
> 👇👇🏻👇🏼👇🏽👇🏾👇🏿 <
insert into blog_1 (id, title) values (0, 'KipSQL', '2022-10-12 12:22:33');
Oops!: bind error: column count not match, expect 2, got 3

What did you see instead?
PANIC occurs when the number of columns does not match the expression during bind Insert.
> 👇👇🏻👇🏼👇🏽👇🏾👇🏿 <
insert into blog_1 (id, title) values (0, 'KipSQL', '2022-10-12 12:22:33');
thread 'main' panicked at /home/jojo/code/open-source/kipsql/src/binder/insert.rs:52:52:
index out of bounds: the len is 2 but the index is 2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Thank you very much for your contribution, I will put this case in the insert test at the weekend  ref: https://github.com/KipData/kipsql/blob/main/tests/slt/insert.slt


ARTEMIS-1805 fix for broker operations in hawtio

There are few operations, which causes an error while selected in hawtio console under broker/operations. Adding @Operation annotation to these methods fixes an error, but methods are exposed and I am not 100% sure that is correct. I also unified capitalized first letter of methods description.

@stanlyDoge I didn't see that the two methods (sendQueueInfo.. and updateDuplicate...) in ActiveMQServerControl are used anywhere. Could simple deleting them from the interface solve the hawtio error?

@gaohoward Done.

@stanlyDoge you got to remove @Override annotations from ActiveMQServerControlImpl also.

@gaohoward Done.


Square function bug on areas

Description
Using the Square function on areas either by right clicking or using the hotkey Q does not work as expected. There seems to be a delay and does not render until additional actions take place, like adding or deleting nodes, or moving the area. Trying to use the Square option again, is then disabled.
New Building where the Square function was used but did not show the new shape.

When using the Move function, the new shape then displays but leaves behind traces of the nodes.

I was able to reproduce this consistently in Firefox and Chrome.
Version
2.00-alpha.3
What browser are you seeing the problem on? What version are you running?
Firefox v107.0
Steps to reproduce
Create a new building.
Right click or use the Q hotkey to use the Square.
The browser URL at the time you encountered the bug
https://mapwith.ai/rapid-v2-alpha3#background=MAPNIK&datasets=fbRoads,msBuildings&disable_features=points,indoor,landuse,boundaries,rail,pistes,aerialways,past_future&id=w-5&map=19.00/43.41944/-71.95998

Thanks for the report! I'll add a little context here- after squaring the building the first time, RapiD's in-memory representation of the building has been updated to be square. When you right-click again, the square option isn't available because RapiD thinks the shape is square.
This causes understandable user confusion, because RapiD  hasn't redrawn the shape to look square.
If you were to hit the browser reload button and keep your changes, you would see the squared building get rendered correctly.

Update to the update- nope, square has the same bug that circularize, rotate, etc. all have right now. That is, until the fix we just pushed!
Fixed in alpha 3.2 release that just went live.


Create ingestion jobs through moderne-cli instead of seed.groovy

[x] Remove seed.grovy
[x] Document manual settings.xml upload through UI; similar to Maven/Gradle/JDKs
[x] Document configuration values for maven/gradle/jdks
[x] Update README to reflect new column order

Figured to crudely remove the various scripts and pipelines that were in here previously; If needed they can be restored; I've added a v0.0.2 tag & release to be able to quickly see the state before this PR was merged:
https://github.com/moderneinc/jenkins-ingest/releases/tag/v0.0.2


sox: Add option to include opus support

Motivation for this change
Many other distributions include opus support in their sox
distributions. This patch makes such an option, and sets it
to be enabled by default. This works when ogg is disabled as
as well as when ogg is enabled.
Things done

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

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

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

@GrahamcOfBorg build sox


mbedtls_mpi_is_prime fails to identify small prime numbers.

Description

Type: Bug
Priority: Major

Bug
mbed TLS build:
Version: 2.9.0
OS version: Mac OS 10.13.6 (17G65)
Configuration: homebrew
mbedtls_mpi_is_prime often fails to identify small prime numbers over 1000 as prime.
See the attached program, it only finds approximately 1020 prime numbers below 10000, while it should find 1229.
countprimes.txt

I think I see the problem: there's some dodgy logic in mpi_miller_rabin. We have a loop that does this:

Let A = random bignum with as many digits as X.
If A has a larger bit size than X, shift A to the right to make it the same bit size as X
If A is not in the range 1..X-1, try again. But don't retry indefinitely: after 30 unsuccessful tries, return “composite”.

This returns “composite” with non-negligible probability if X-1 is close to the largest smaller power of 2.
I think this function was mostly intended for use in mbedtls_mpi_gen_prime, and there X is random, so the bad case of mbedtls_mpi_is_prime is vanishingly unlikely to happen for numbers of cryptographic size, and a rare false negative doesn't matter anyway. But since mbedtls_mpi_is_prime is a public API, we should fix this bug.
It's impossible to generate a random integer uniformly given only random bits in a given in bounded time. So we either need to accept unbounded time or make the bound and the range coercion more intelligent so that it is truly unlikely to happen no matter what the value of A is, or both.
In addition, the generation of A is not quite uniform. I don't think it matters here, a MR witness doesn't need to be generated uniformly, but if we replaced this conditional shift by an unconditional masking of the high word, it would make the code marginally more efficient and the generator would be uniform.
In addition, A is set to a random value and shifted before this loop, but the resulting value is then ignored because the loop runs at least once.

The comment just above the function says Pseudo-primality test:
Presumably that Pseudo means that the function was intended to fail sometimes, but should be fast in eliminating non-prime numbers.

@irwir Indeed this is a probabilistic test, but the documentation does state that it's a Miller-Rabin test and that the return values are 0 for “probable prime” and NOT_ACCEPTABLE for “not prime”. If it returns 0 for a composite, that's ok (especially for a small composite, MR is inefficient with small numbers), but it must not claim that a prime is composite (or else we need to change the documentation, but I don't think that's the right solution: MR is what people would expect in a crypto library).

@gilles-peskine-arm, thanks
Yes, it is a bug to falsely report "found a non-trivial divisor" when there is none.
By the way, if checked numbers are mostly big, mpi_check_small_factors could implement an early return for values that exceed the last positive element in small_prime array.

The wikipedia article on miller-rabin has a list of witnesses for specfic small number ranges, such that you need to do only a very small number of tests for those numbers.

ARM Internal Ref: IOTSSL-2435


Improper usage of power domain flags for runtime device power management

Describe the bug

In the device runtime power management structure there is a flag ( PM_DEVICE_FLAG_PD_CLAIMED) that keeps track if the device successfully managed to "claim" however this flag is cleared on the first put call and this blocks other suspend calls to the power domain.
To Reproduce

Enable runtime power management on power domain and test_device
ensure usage count of both is 0, test_device is powered off and power domain is suspended
call pm_device_runtime_get(test_device) twice
call pm_device_runtime_put(test_device) twice
the test device will have usage count 0 and the power domain will have usage count 1

Expected behavior

The power domain will power off when all devices attached to it are suspended or usage count 0
Impact

This will break power domain usage if device usage count ever goes above 1 since it will only put the power domain once.
To bypass the issue manual power management of power domains will be needed
Logs and console output

first call to pm_device_runtime_get(test_device)
[00:00:04.307,556]  test_device: Power on device
[00:00:04.307,647]  pm_device: usage count = 1 , from test_device_regulators
[00:00:04.357,971]  pm_device: usage count = 1 , from test_device@0
[00:00:04.357,971]  test_device: Resuming device
second call pm_device_runtime_get(test_device)
[00:00:04.604,064]  pm_device: usage count = 2 , from test_device_regulators
[00:00:04.604,095]  pm_device: usage count = 2 , from test_device@0
first call pm_device_runtime_put(test_device)
[00:00:05.622,314]  pm_device: usage count = 1 , from test_device@0
[00:00:05.622,344]  pm_device: usage count = 1 , from test_device_regulators
second call pm_device_runtime_put(test_device)
[00:00:05.622,406]  pm_device: usage count = 0 , from test_device@0
[00:00:05.636,352]  test_device: Suspending test_device
test_device drops down to 0 usage count and gets properly suspended but the test_domain_regulators are stuck at usage count 1.
Environment (please complete the following information):

OS: Windows
Toolchain NCS 2.6.0
Zephyr 3.5.99

I used this toolchain however I checked the offending code in the main zephyr branch and suspect the issue is still present
Additional context

This can be fixed on either the get side for the power domain by only getting if the flag hasn't been set and not getting the power domain device multiple times.
or on the put side by only clearing the flag if the usage count of the device hits zero.
Ill start working on a unit test to check if this is an issue or that we are doing something wrong with our devices

Wrote a unit test which passed and found that this exact issue was fixed here
Closing since fixed


Fix typo on adb.exe

Description:

Fix typo (from abd.exe to adb.exe)
This typo causes dexcalibur crash on Windows

File changed:

src/DeviceManager.js

Thanks !


Python 3.6: Response always 200

How can python dictate the response code returned by Kubeless?
https://github.com/serverless/serverless-kubeless/issues/180 In this issue there is a field in event.extensions to set the response code, but this key doesn't exist in the python runtime. I've tried adding the field to the event object, but the response code isn't changed. Calling the function results in 200 even though I returned 400.
Any insight will be appreciated.
Thanks

Unfortunately, the field response is not available for the Python runtime. You can find more context here: https://github.com/kubeless/runtimes/issues/28


All Kind tests in CI failed consitently

Describe the bug
All kind tests failed because of same error: docker image antrea/antrea-ubuntu:latest failed to load.
kubectl cluster-info --context kind-kind

Not sure what to do next? 😅 Check out https://kind.sigs.k8s.io/docs/user/quick-start/
deployment.apps/coredns patched
Configuring networks
removing worker nodes kind-worker kind-worker2 from networks  bridge
disconnected worker kind-worker2 from network bridge
disconnected worker kind-worker from network bridge
creating network kind-0 with <IP_ADDRESS>/24
connected worker kind-worker to network kind-0
node kind-worker is ready with ip change to <IP_ADDRESS> with gw <IP_ADDRESS>
connected worker kind-worker2 to network kind-0
node kind-worker2 is ready with ip change to <IP_ADDRESS> with gw <IP_ADDRESS>
current ip   InternalIP:  <IP_ADDRESS>, wait for new node ip <IP_ADDRESS>
load images
loaded image busybox
loaded image nginx
docker image antrea/antrea-ubuntu:latest failed to load
 Test failed cleaning testbed
Deleting cluster "kind" ...
deleted networks kind-0
##[error]Process completed with exit code 1.

Is this an issue you are observing locally as well, or is it specific to CI?
I see that all the CI tests are indeed failing with a "No space left on device" error which occurs when the antrea docker image is loaded into the workers. I wonder if something has changed with the worker VMs used by Github. Maybe they reduced available disk size? I will look into it...

This is a known issue and many users have reported the same problem in the last couple of days: https://github.com/actions/virtual-environments/issues/709. The Github engineering team is working on it and as of a couple hours ago, they started a rollback to the old Ubuntu images: https://github.com/actions/virtual-environments/issues/709#issuecomment-616801148. It seems that on my fork things are already back to normal.
The issue suggests adding apt-get clean to the jobs as a workaround, so even though things seem back to normal, I will open a PR to add this workaround.


Prediction Error from Sklearn classifier module

rasa NLU version (e.g. 0.7.3): 0.8.0a10
Used backend / pipeline (mitie, spacy_sklearn, ...):  ["nlp_mitie", "tokenizer_mitie", "ner_mitie","ner_duckling","ner_synonyms","intent_featurizer_mitie", "intent_classifier_keyword","intent_classifier_sklearn"]
Operating system (windows, osx, ...): Mac OSX 10.11.6
Issue:
The model got trained properly. After running the server and quering, I am getting the below error:
INFO:root:Started http server on port 5000
[2017-04-17 16:31:21,339] ERROR in app: Exception on /parse [POST]
Traceback (most recent call last):
File "/Library/Python/2.7/site-packages/flask/app.py", line 1982, in wsgi_app
response = self.full_dispatch_request()
File "/Library/Python/2.7/site-packages/flask/app.py", line 1614, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/Library/Python/2.7/site-packages/flask/app.py", line 1517, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/Library/Python/2.7/site-packages/flask/app.py", line 1612, in full_dispatch_request
rv = self.dispatch_request()
File "/Library/Python/2.7/site-packages/flask/app.py", line 1598, in dispatch_request
return self.view_functionsrule.endpoint
File "/Users/sourjabanerjee/Documents/rasa/rasa_nlu/rasa_nlu/server.py", line 48, in decorated
return f(*args, **kwargs)
File "/Users/sourjabanerjee/Documents/rasa/rasa_nlu/rasa_nlu/server.py", line 69, in parse_get
response = current_app.data_router.parse(data)
File "rasa_nlu/data_router.py", line 150, in parse
response = model.parse(data['text'])
File "rasa_nlu/model.py", line 285, in parse
updates = component.process(*args)
File "rasa_nlu/classifiers/sklearn_intent_classifier.py", line 97, in process
intent_ids, probabilities = self.predict(X)
File "rasa_nlu/classifiers/sklearn_intent_classifier.py", line 133, in predict
sorted_indices = np.flip(np.argsort(pred_result, axis=1), axis=1)
AttributeError: 'module' object has no attribute 'flip'
<IP_ADDRESS> - - [2017-04-17 16:31:21] "POST /parse HTTP/1.1" 500 412 0.025745

You need at least numpy version 1.12.
We should really think about removing the flip and replacing it with backwards compatible numpy code. @twerkmeister can you have a look at that?


Problem while adding python path for shogun : python interface

As mentioned in https://github.com/shogun-toolbox/docs/blob/master/INTERFACES.md :
The package support to python for shogun is to be enabled by
export PYTHONPATH="path/to/modshogun.py:$PYTHONPATH"
following up to which , I did was :
export PYTHONPATH="/home/saphire/shogun/build/src/interfaces/python/shogun.py:$PYTHONPATH";
but still I get :
Traceback (most recent call last):
File "random_forest_regression.py", line 2, in
from shogun import Math
ModuleNotFoundError: No module named 'shogun'
on executing any .py file in the examples.
also for Interfacing c++
I did the following :
gcc kmeans.cpp -o kmeans -I//home/saphire/shogun/src/shogun/base -lshogun -L//home/saphire/shogun/src/shogun/libshogun.so
kmeans.cpp:1:10: fatal error: shogun/base/init.h: No such file or directory
#include <shogun/base/init.h>
^~~~~~~~~~~~~~~~~~~~
compilation terminated.
but the error !!

This is a standard python path problem. You need to make sure the .py file of the shogun interface in your build folder is in the pythonpath. Best is to print it and compare


Hybrid cache in What's new doc

Description
See https://github.com/dotnet/AspNetCore.Docs/issues/32361#issuecomment-2070480937
Page URL
https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-9.0.md
Document ID
4e75ad25-2c3f-b28e-6a91-ac79a9c683b6
Article author
@Rick-Anderson

Associated WorkItem - 247989

Not sure if this is the same ticket, but we need to think about primary docs for HybridCache, which is fundamentally parallel to IDistributedCache and IMemoryCache, which puts the logical location as /aspnet/core/performance/caching/. Happy to help provide content for this, a lot of which I've already done (see linked comment) - and we also probably want to add a "consider HybridCache to the existing IDistributedCache and IMemoryCache documentation. I don't "docs" a lot, so if someone can advise me on the best way I can start this process, I'd be grateful!


Is it possible to not shut down source VM after cutover command?

Hello, is there a way to not shut down the source VM I migrated to cloud at the end of cutover command?
I see this message.
INFO[0339] Completed migration cycle, shutting down source VM
Thanks for the help! :)

@FlorianBoegl you will need to add this feature yourself or engage our team to request it, however, I wonder what the use case here.

@mnaser sry for late response, usecase ist that we first want to test the migrated VM before its online.
We have issues sometimes after migrating the VM that are not caused by migratekit, its related to our Cloud Provider...
I will close this issue since it would be only a nice to have thing ;)


Guild tab not working

The guild tab is no longer working. It shows up normal now. I really love this feature.

have you enabled it in the settings?

Oh! I never touched the settings tbh so I was confused when it was turned off as default. Thank you and great work! :)


Update for newer async-blobstore

[ch10044]
This just fixes the broken API. It doesn't add support for AAD. Should be easy enough to add in the future.
Depends on slamdata/async-blobstore#41

@rintcius what do you think about merging the core and azure subprojects? That way assembling the plugin works. The launcher is unaffected either way.

🛑 because of snapshots.

[ch10115]


Changed username in documetation from metrika to clickhouse

Since c51801d7762bda374757cf61a062b6c6542762b5 default user and
group names is 'clickhouse'

Can one of the admins verify this patch?

also please change path from /opt/clickhouse to /var/lib/clickhouse

also please change path from /opt/clickhouse to /var/lib/clickhouse
Done


Dcsr.xdebugver reset value

Hi all,
I noticed that in the CSR register module, dcsr.xdebugver is set to XDEBUGVER_NO upon reset, but after reset is over and an explicit write to dcsr occurs, the xdebugver field will then be permanently set to the value of XDEBUGVER_STD for the duration of the simulation.  This seems to contradict with the behavior of the dcsr.prv field, which is set to PRV_LVL_M at reset, as well as whenever a write occurs outside of reset.  Why does this separate reset behavior for xdebugver occur, instead of setting it to XDEBUGVER_STD from reset onwards especially since this field is read-only and stays as a constant?
Thank you!
Udi

HI @udinator ,
thanks for creating the issue. I do not see any reason why dcsr.XDEBUGVER should not be set to XDEBUGVER_STD right at reset. I will create a PR to correct this.
Best Pirmin

Thanks for the fix @vogelpi!


Netlify Deploy Button for Kodadot-app #1397 #7508

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #1397
[x] ## Did your issue had any of the "$" label on it?
[x] My DOT address: Payout

@vikiival it's finally here

Ok


Mail.send() UnauthorizedError

I'm getting an UnauthorizedError when trying to send an email using this client. Anyone have any ideas where I should look?

I'm not sure what the error is here but we hit the same issue and ended up switching to the SendGrid integration documentation at https://sendgrid.com/docs/for-developers/sending-email/django/


Update dev-server.js

fix webpack-dev-server provide own certificate problem

Hi @huijiewei
What's your config?
With the following config, it works in my projects
    devServer: whenDev(() => ({
        https: true,
        pfx: fs.readFileSync(path.resolve("./devtools/https/localhost.pfx")),
        pfxPassphrase: "..."
    })),

https://webpack.js.org/configuration/dev-server/#devserver-https
devServer: {
    https: {
      key: fs.readFileSync('/path/to/server.key'),
      cert: fs.readFileSync('/path/to/server.crt'),
      ca: fs.readFileSync('/path/to/ca.pem'),
    }
  }

Got it! thx

Released as 3.2.2-alpha.0
I will release to latest when I get back from vacation in a few days.


added new util classes and enhanced the row-center class

Description
add some text-align util classes that can be used anywhere and will cut some styling effort
also improved the row-center class for better column alignment
in the second commit I added .stack class to force flex-direction: row; for the mobile
in the third commit I added .fluid class to make the container width full screen

Code sample
new classes are:
- .text-left
- .text-right
- .text-center
- .stack
- .fluid
properties used in .row-center:
- justify-content: center
- text-align: center

Guys I made different commits after this pull request was made and included them in the description

@cjpatoilo hey man, I've seen a lot of PRs passing the tests and getting flags (including this one) so when you will start accepting them?

@KhaledElAnsari For now, I will close this PR. Let me know if you understand the questions.


Depend on spree_core 2.3.0

Hi , facebook like not displayed .

When I point Spree::Config.facebook_app_id = 'YOUR_FACEBOOK_APP_ID'

my email<EMAIL_ADDRESS>Thanks

I assume this PR was an error.


[release/1.3] Bump CRI 1.3 branch

Update 1.3 release branch to sync with CRI release branch

LGTM (non-binding)

Codecov Report

Merging #3998 into release/1.3 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.3    #3998   +/-   ##
============================================
  Coverage        42.31%   42.31%
============================================
  Files              129      129
  Lines            14341    14341
============================================
  Hits              6069     6069
  Misses            7373     7373
  Partials           899      899

Flag
Coverage Δ

#linux
45.83% <ø> (ø)
:arrow_up:

#windows
37.31% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8366042...4e63536. Read the comment docs.


IronJavascript / IronJs

This language will be reestablished?
Better yet will be to have a IronTypescript.

IronJS was something done by someone outside of the DLR/IronPython/IronRuby group. If someone wants to do an IronJS or IronTypescript, they could definitely do that. It is not something that will be done as part of this org.


Search default Gradle build path for classes on agent controller

The default classpath set in agentcontroller.sh doesn't include the default Gradle build path.
Gradle project (and Maven it seems) have default source directories of src/main/java.  Gradle then compiles classes to build/classes/java/main.  It would be helpful to include this in the path that the Agent Controller searches for test classes.
Current workaround I'm using is an action in one of my tasks to copy the class files to the default Maven build directory:
    // copy classes from buildDir/classes/java/main/ to projectDir/target/classes/
    doLast {
        copy {
            from "$buildDir/classes/java/main"
            into "$projectDir/target/classes"
        }
    }

Adding the standard Gradle classes directories to the class path should be an easy thing to do. I will update agent.sh and agent.cmd accordingly.
I wonder if we also have to add a new library directory to the class path. Does Gradle define a default directory where dependencies are copied to? In Maven, for example, that would be "target/dependency".

Qualifier: I am a Gradle novice.
I believe that gradle downloads dependencies to the dependency cache which isn't under the project directory.  This is typically ~/.gradle/caches I believe.  See the link below:
https://docs.gradle.org/current/userguide/dependency_management.html#sec:dependency_cache
As a workaround I was copying the implementation level dependencies to the Maven dependency location with the below task:
task copyRuntimeLibs(type: Copy) {
    from configurations.implementation
    info "$projectDir/target/dependency"
  }

All right, so let's start with the two classes directories. We can add a new library directory anytime if needed. Thanks for your help!


Poetry Update Hangs

Poetry update hangs while trying to install dependencies for MIFC. The stack trace below was stuck on the "exceptiongroup" line for a few days before I hit Ctrl-C. I have tried some of the advice in the following discussion (which shows a similar stack trace) to no avail:
https://github.com/python-poetry/poetry/issues/3352
I'm running Poetry version 1.8.2 on Ubuntu 22.04.4 LTS.
@turbomam or @sujaypatil96, are you able to help with this?
(mifc-py3.10) greg@Ubuntu22:/var/www/html/mifc$ poetry update
Updating dependencies
Resolving dependencies... (8.4s)

Package operations: 134 installs, 1 update, 0 removals

  - Installing six (1.16.0)
  - Installing typing-extensions (4.12.2)
  - Installing annotated-types (0.7.0): Pending...
  - Installing attrs (23.2.0): Pending...
  - Installing certifi (2024.7.4): Pending...
  - Installing charset-normalizer (3.3.2): Pending...
  - Installing exceptiongroup (1.2.1): Pending...
^C
^C^CException ignored in: <module 'threading' from '/usr/lib/python3.10/threading.py'>
Traceback (most recent call last):
  File "/usr/lib/python3.10/threading.py", line 1537, in _shutdown
    atexit_call()
  File "/usr/lib/python3.10/concurrent/futures/thread.py", line 31, in _python_exit
    t.join()
  File "/usr/lib/python3.10/threading.py", line 1096, in join
    self._wait_for_tstate_lock()
  File "/usr/lib/python3.10/threading.py", line 1116, in _wait_for_tstate_lock
    if lock.acquire(block, timeout):
KeyboardInterrupt:
(mifc-py3.10) greg@Ubuntu22:/var/www/html/mifc$

Thanks @GregLyonJIFSAN for posting @turbomam @sujaypatil96 please let me know if you guys might be able to help with this. I'm certainly not the expert in python environment management.

@GregLyonJIFSAN did poetry update every work for you in this repo?

My environment
poetry --version

Poetry (version 1.8.2)

python --version

Python 3.10.13

poetry update worked for me in the last state I left things in and in a fresh checkout of main. Still thinking.

poetry show exceptiongroup

name         : exceptiongroup
version      : 1.2.2
description  : Backport of PEP 654 (exception groups)
required by

pytest >=1.0.0rc8

@turbomam Thanks -- I don't recall poetry update ever working for me for this repo.
I have a different version of exceptiongroup listed:
greg@Ubuntu22:/var/www/html/mifc$ poetry show exceptiongroup
 name         : exceptiongroup
 version      : 1.2.1
 description  : Backport of PEP 654 (exception groups)

required by
 - pytest >=1.0.0rc8

I propose we work on this together in a Zoom meeting

@GregLyonJIFSAN are you using Ubuntu 22 on bare metal, or inside a container/virtualization like WSL, Docker, etc.?

@turbomam I'm running it inside Oracle VirtualBox.

@turbomam is there a good time for a call? I'm free now if that works.

I'll add a Zoom link here in about 5 minutes. I'm going to delete it after the meeting starts.

@turbomam Sounds good, thanks, talk to you soon.

https://go.lbl.gov/mam-lbl-zoom

Thank you so much @turbomam for helping @GregLyonJIFSAN with this! I hope you guys managed to figure some things out.

Hello @turbomam, thanks again for your help on Tuesday. Somewhat duplicating the discussion on the LinkML repository, I found a command on this Stack Overflow page that fixed the problem:
https://stackoverflow.com/questions/74960707/poetry-stuck-in-infinite-install-update
The command is:
poetry config keyring.enabled false
I will go ahead and mark this issue as closed for MIFC since we have a workaround. The issue on the LinkML repository is still open if anyone has any insights into what might be the problem with the keyring.

😂 Glad this is resolved.


Only import selected workload

Currently, the submission_runner takes the WORKLOADS dictionary, e.g.:
https://github.com/mlcommons/algorithmic-efficiency/blob/584769427aceeac2835c055fae40f159d4a415d7/submission_runner.py#L30-L33
And attempts to import every module, replacing the dictionary values of WORKLOADS with the workload class object:
https://github.com/mlcommons/algorithmic-efficiency/blob/584769427aceeac2835c055fae40f159d4a415d7/submission_runner.py#L292-L297
In case of import failures however, the dictionary values are unchanged, and if we attempt to run that workload, we get a less instructive error:
AttributeError: 'dict' object has no attribute 'build_input_queue'

Moreover, since most users will be submitting in one framework, the log will be polluted with many import errors for the other frameworks.
Instead, perhaps we only import the workload selected by FLAGS.workload, and raise an ImportError if fails.
cc: @znado ?

Instead of the current flags, we could ask for the framework and the workload separately. For example
python3 submission_runner.py --framework=jax --workload=mnist --submission_path=...

Depending on the framework flag we can set use_jax_rng and only import the corresponding workloads. At the moment a submitter has to twice state that he uses JAX (once via specifying mnist_jax as the workload and once via the use_jax_rng).
I think this could result in a clearer interface for the submitters and prevent inconsistencies, i.e. when one submitter uses PyTorch with use_jax_rng and another one without use_jax_rng.


[Bug]: Cannot find module 'next/dist/shared/lib/app-router-context.js' with Next.js 13

Summary
Hi, I try to deploy Next.js v13 app to Netflify, the build was success, but the deploy preview url got 500 error, after checking the function, turned there's missing module error.

Tried next build and start locally, no issue
I also tried to deploy to Vercel with same branch, it works. (PR sample)
I've also run clear cache and redeploy but still got 500. https://deploy-preview-12--antonybudianto.netlify.app/

*Posted log on Function log section
Thank you for your support 🙏🏻
Steps to reproduce

Clone https://github.com/antonybudianto/next-antonybudianto
Checkout to dev branch
Deploy to netlify
Got 500 error

A link to a reproduction repository
https://github.com/antonybudianto/next-antonybudianto/
Next Runtime version
4.28.1
More information about your build

[ ] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
No response
Your netlify.toml file
[[plugins]]
package = "@netlify/plugin-nextjs"
Your public/_redirects file

`_redirects`
# Paste content of your `_redirects` file here

Your next.config.js file

`next.config.js`
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: false,
  swcMinify: true,
  experimental: {
    appDir: true,
  },
};

module.exports = nextConfig;

Builds logs (or link to your logs)

Build logs
2:00:30 PM: $ yarn build
2:00:30 PM: yarn run v1.22.19
2:00:30 PM: $ next build
2:00:30 PM: warn  - You have enabled experimental feature (appDir) in next.config.js.
2:00:30 PM: warn  - Experimental features are not covered by semver, and may cause unexpected or broken application behavior. Use at your own risk.
2:00:30 PM: info  - Thank you for testing `appDir` please leave your feedback at https://nextjs.link/app-feedback
2:00:30 PM: warn  - No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
2:00:30 PM: info  - Creating an optimized production build...
2:00:30 PM: info  - Compiled successfully
2:00:30 PM: info  - Linting and checking validity of types...
2:00:30 PM: info  - Collecting page data...
2:00:30 PM: info  - Generating static pages (0/3)
2:00:30 PM: info  - Generating static pages (3/3)
2:00:30 PM: info  - Finalizing page optimization...
2:00:30 PM: Route (app)                                Size     First Load JS
2:00:30 PM: ─ ○ /                                      0 B                0 B
2:00:30 PM: + First Load JS shared by all              66.5 kB
2:00:30 PM:   ├ chunks/main-app-9fbe7621087549d7.js    64.4 kB
2:00:30 PM:   └ chunks/webpack-151ac98db2ceb433.js     2.03 kB
2:00:30 PM: Route (pages)                              Size     First Load JS
2:00:30 PM: ┌   /_app                                  0 B            80.2 kB
2:00:30 PM: └ ○ /404                                   179 B          80.3 kB
2:00:30 PM: + First Load JS shared by all              84 kB
2:00:30 PM:   ├ chunks/main-aa32f7dd722ddf9b.js        77.3 kB
2:00:30 PM:   ├ chunks/pages/_app-01135c343aba8f60.js  821 B
2:00:30 PM:   ├ chunks/webpack-151ac98db2ceb433.js     2.03 kB
2:00:30 PM:   └ css/863675e8e5f4e4bd.css               3.87 kB
2:00:30 PM: ○  (Static)  automatically rendered as static HTML (uses no initial props)
2:00:30 PM: Done in 15.20s.
2:00:30 PM:
2:00:30 PM: (build.command completed in 15.3s)

Function logs

Function logs
Oct 27, 07:20:58 AM: 432e97cc ERROR  Error: Cannot find module 'next/dist/shared/lib/app-router-context.js'Oct 27, 07:20:58 AM: 432e97cc ERROR  Require stack:Oct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/.next/server/app/page.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/node_modules/next/dist/server/require.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/node_modules/next/dist/server/next-server.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/.netlify/functions-internal/___netlify-handler/handlerUtils.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/.netlify/functions-internal/___netlify-handler/___netlify-handler.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/task/___netlify-handler.jsOct 27, 07:20:58 AM: 432e97cc ERROR  - /var/runtime/index.mjsOct 27, 07:20:58 AM: 432e97cc ERROR      at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)

.next JSON files

generated .next JSON files
# Paste file contents here. Please check there isn't any private info in them
# You can either build locally, or download the deploy from Netlify by clicking the arrow next to the deploy time.

Hi. Next 13 is not currently supported by default on Netlify. Support for the pages dir is in the latest runtime, which will be auto-installed by default later today. Support for app dir is experimental, and will require enabling some options. I'll be sharing details very soon.

I see.. also I saw this PR https://github.com/netlify/next-runtime/pull/1638 and tried the alpha release and it works now 😅

Awesome! I'll have a post with more info soon.

By the way, I just noticed that the SPA navigation breaks 😅  but the SSR itself still worked


consider using the frequencies.txt instead of a big stop_times files

according to the GTFS spec it is possible to have a frequencies.txt file which together with the stop_times.txt describes the times at which a trip reaches the stops

When trips are defined in frequencies.txt, the trip planner ignores the absolute values of the arrival_time and departure_time fields for those trips in stop_times.txt. Instead, the stop_times table defines the sequence of stops and the time difference between each stop.

Advantages:

reduce the total amount of of entries that we have in the dummy output
easier for humans to parse/understand since we dont have to scroll over thousands of lines
no need for fancy algorithms to find patterns in the stop_times since it is given by default

Disadvantages:

kamal would have to understand both formats and expand the frequencies at runtime to find the proper trip

Questions:

should we make the frequencies.txt required for kamal? it would probably speed up the routing since we dont need to loop over thousands of stop_times entries

Reference:

https://developers.google.com/transit/gtfs/reference/#frequenciestxt

current info on kamal data distribution: https://github.com/hiposfer/kamal/issues/180

@carocad I know it took me a while to get to this but I'm eventually there :)
This feature falls in the domain of dummy patching a feed and using o2g to basically generate valid GTFS feeds for testing. This is a good thing, however kamal shouldn't rely on something totally random.

This is a good thing, however kamal shouldn't rely on something totally random.

Agree. Making it mandatory is definitely not a good solution. However right now I am developing hive to show the gtfs entities to the users so that they can edit those directly.
The current way of handling stop_times makes it very problematic for a user to edit since it requires editing each entry manually. Since there might be hundreds of those just for a single route, it would be impossible for a user to contribute anything meaningful.
The alternative would be if we use frequencies.txt and let the user edit/add/remove those. Since the frequency immediately affect all trips of that route, it would be much more scalable.
That is actually what I meant by "making it required" .... since from the user perspective it becomes unbearable otherwise :/


None 2 na

changed all NONE in fraction, speciation, and unit to NA. This is performed in autoclean, and is converted in the GetRef functions, as well as the harmonization table
updated harmonization and total N and P tables
updated calculatetotalNP function to include phosphorus

Codecov Report

Merging #324 (e9b85bf) into develop (1eae68e) will decrease coverage by 1.15%.
Report is 3 commits behind head on develop.
The diff coverage is 14.85%.

:exclamation: Current head e9b85bf differs from pull request most recent head c23d072. Consider uploading reports for the commit c23d072 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop     #324      +/-   ##
===========================================
- Coverage    53.47%   52.33%   -1.15%
===========================================
  Files           12       12
  Lines         2573     2652      +79
===========================================
+ Hits          1376     1388      +12
- Misses        1197     1264      +67

Files Changed
Coverage Δ

R/Transformations.R
56.72% <0.00%> (-2.79%)
:arrow_down:

R/Utilities.R
75.49% <7.81%> (-9.42%)
:arrow_down:

R/CensoredDataSuite.R
68.60% <100.00%> (+2.32%)
:arrow_up:

R/GenerateRefTables.R
85.21% <100.00%> (+0.48%)
:arrow_up:

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Cache verification key in CLI

When you go through the zk deploy flow multiple times, it's annoying that the veriffication key is rebuilt every time, which takes 1-2 minutes
Would be nice to cache the veriffication key
TBD: how do we handle cache invalidation / enable rebuilding when it's needed. Ideally, we detect when the vk changed from a quick-to-compute hash of the circuit, but that would require more work on the snarkyjs side.
Some ideas for what we could do now:

never invalidate the cache, expose an explicit --rebuild option to zk deploy
separate compiling into its own command, zk compile, which never uses a cache, and let zk deploy just depend on the output it creates -- that way, rebuilding is always an explicit operation

In what situations would when a dev would need to sit through generating & deploying the same verification key? Only if deploying once to network A (i.e. Testnet) and again to network B (i.e. Mainnet)?

Actually I found an answer: If an error occurs during deployment (i.e. tx relayer unavailable, etc) then it would be convenient to have that cached for when re-trying again.

Yes, anything were you get off the happy path. For example: Something in your code prevents deploy from working, and you want to iterate on that. Like the error that Serhii reported recently, it probably happened in the Mina.transaction block, which is (has to be) after compiling. Then, with every fix you try, you have to wait 2 minutes to see if it works. This is not a theoretical problem, it was a pain for me and there were users in discord complaining about this too.
There are also cases where you break out of the flow even if no error occurs. For example, you get to the point where you have to set the transaction fee, but you are not sure what fee you should use, so you Ctrl-C and do it again later. These things happen all the time.

@bkase to write RFC

We could also store the digest values inside of a digests property or similar, within build.json.

We could also store the digest values inside of a digests property or similar, within build.json. Feels like a natural location given we store other computed values there already.

The only risk is corruption if there are multiple writes at the same time to this file, but as long as we're careful this should work 👍

true, but should be ok b/c we should gather all digests then write to disk once

@ymekuria Looks like we can't use build.json after all because it is clobbered each time deploy is run here: https://github.com/o1-labs/zkapp-cli/blob/e1f89a47c224149129d7339085c1559d991f9fe9/src/lib/deploy.js#L92-L103
But we could add a build/cache.json file and store the cache-related data there. I'd probably just nest both under the smart contract name:
{
  "<smartContractNameA>": {
    "digest": "abc",
    "verificationKey": "abc",
  },
  "<smartContractnameB>": {
    "digest": "abc",
    "verificationKey": "abc",
  }
}

Note that there is a known limitation of build.json, and this caching code by extension, in that we assume all smart contracts in a project have unique names. It's probably acceptable, but we could warn people if their project contains >1 smart contract with the same name; I'll create an issue to track this.

But we could add a build/cache.json file and store the cache-related data there. I'd probably just nest both under the smart contract name:

Good catch about build.json. I like the idea of adding a cache.json file.

@jasongitmail It looks like we can't put cache.json file in the build directory because the directory is emptied every time deploy is run here:
https://github.com/o1-labs/zkapp-cli/blob/e1f89a47c224149129d7339085c1559d991f9fe9/src/lib/deploy.js#L87-L90
We can add the cache.json file to the root of the template at the same level as the config.json and add it to gitignore.

@ymekuria, I think we should just not empty the build directory in that case :D instead we could delete everything in there except cache.json
FWIW, inside keys feels wrong to me, because the verification "key" isn't a key in the usual sense of the term and putting it there would only contribute further to this confusion :D

The keys dir isn't the right location because this is a file that a dev should never really see.
+1 for changing line 88 to delete all files except the cache.json. I'd suggest reading cache.json into memory, empty the dir, and output cache.json again.


Remove link to stale go-search.org engine from results page

The main page says " last updated 419 days ago."
@daviddengcn: Is this number accurate?  Is the crawler coming back?

Yes, it is correct. The current code does not compile (because of dependent package change). It may need some effort to fix it. I cannot guarantee a time of fixing it. Sorry for the inconvenience.

I'll make a try this weekend, and post the result here.

Update: the code on my local machine is good. Will try push to server tommorrow.

The crawling is recovered

Excellent! I'll close this then.

Thanks!


Mser example

this is updated https://github.com/Itseez/opencv/pull/4022
also, normalize the use of cvconfig.h, so that it's always available as "opencv2/cvconfig.h".

ok, looks like it's duplication of https://github.com/Itseez/opencv/pull/4058

I think your solution is better and should be preffered, because it fixes many other samples containing `#include "cvconfig.h". I can remove cvconfig-related commit from my pull request to avoid merging conflict.


Add Submit and SubmitOrNewline editor events

Submit is used to return data unconditionally. This is useful for example if you want compiler to show you where the unclosed paren that doesn't pass validation actually is.
SubmitOrNewline is similar to Enter but inserts a new line if the cursor is not at the end of the buffer. It's useful to insert newlines in the middle of the text when editing.

This also removes unconditional KeyCode::Enter to ReedlineEvent::Enter event mapping and sets it in the keybindings normally (so you can rebind to Submit or SubmitOrNewline)

That sounds like a good idea to decouple some of that hard coded behavior on enter. I will try to take a look if there is stuff that might break. Having the option to explicitly bind it to a separate binding sounds definitely nice, weighing the options in my head of whether we should have all three or a config between  the Enter and SubmitOrNewline behavior

Yes, Enter and SubmitOrNewline usually may be configurable. In Rustyline it's a bool field in enum variant. On the other hand, I don't know if it makes sense to make this variable somewhere in the EditMode, as that would require a special method to configure that (so one more thing to learn), while changing binding sounds obvious and clear to me.
Submit on the other hand has to be a separate, as we, for example, bind Submit on Alt+Return and SubmitOrNewline on Return.

Seems to work fine in my testing! Thanks for the elegant solution!

I will land it as is to allow users to play with it in the next (nushell) release. If we want to make a later breaking change we to the bindings we may bunch it up with other likely changes.


Please publish this extension to the open-vsx.org registry (to support VSCodium)

I would love to use this extension with VSCodium. For that to work, the extension would need to be published to the open-source registry at openvsx. A guide on how to do that can be found here: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
Alternatively, the extension could be added to the publish-extensions repo as a workaround, but that would not be a good long-term solution for reasons described here.
I know it’s a few steps to follow, but please consider this! I’d be very grateful. <3

Feel free to fork it and publish, it won't hurt my feelings

Fortunately, this has already been taken care of a while ago without any steps required from you.


Adding intent causes the app in release builds to throw realmexception

What happened?
I am using a local configuration-based realm and i want to create a scheduled task and add it to my calendar app. For this, i am using android_intent_plus to create an intent. But whenever i add this plugin to a project and build a release apk. The app throws a realm exception.
If I remove the plugin from the project, do flutter clean and build a release apk. The app works fine. is it a plugin issue?
I tried adding the plugin package name to Proguard and tested without any proguard or obfuscation.
Repro steps

Added android intent plus
Built release apk and ran apk on device
the app threw realmexception and whole blank white screen.

Version
3.10.5
What Atlas Services are you using?
Local Database only
What type of application is this?
Flutter Application
Client OS and version
Android 13
Code snippets
No response
Stacktrace of the exception/crash you're getting
realmexception: error opening realm at path ./default.realm. error code: 1018 . message: failed to open file at path './default.realm.lock': read-only file system flutter

Relevant log output
No response

Hi @milindgoel15!
How about changing the path where the Realm is stored? Have you already tried that?
You can set a different location using path parameter of Configuration.local constructor. There is also another approach described here: https://www.mongodb.com/docs/realm/sdk/flutter/realm-database/configure-and-open/#customize-default-configuration
You can also try to set fifoFilesFallbackPath
https://www.mongodb.com/docs/realm/sdk/flutter/realm-database/configure-and-open/#set-custom-fifo-special-files

No, I have not tried it yet. Will do
Do you happen to know or any idea why the realm is getting locked after adding android intent plugin to the project?

Setting a different path is much more difficult with Android 13. Because google doesn't let apps to access external storage. Is there any other workaround to this issue?

@milindgoel15, unfortunately i couldn't reproduce this error. It works for me. Maybe what I do is different from your code. It will be good if you can share some parts of your code. What do you launch with android_intent_plus?
If I understand correctly, you have already the realm file on your device and it is locked by some reason.
In order to keep your user data you can copy the file to another location.
  final String realmPath = "${Configuration.defaultStoragePath}\realm\\";
  if (!Directory(realmPath).existsSync()) {
    Directory(realmPath).createSync();
    File("${Configuration.defaultRealmPath}\\${Configuration.defaultRealmName}").copySync(realmPath);
    Configuration.defaultRealmPath = "$realmPath\\${Configuration.defaultRealmName}";
  }
  final realm = Realm(Configuration.local([Task.schema]));

You can use this as an workaround, but it will be good to know why the files are locked.
Please let me know, if this helped.

@milindgoel15, unfortunately i couldn't reproduce this error. It works for me. Maybe what I do is different from your code. It will be good if you can share some parts of your code. What do you launch with android_intent_plus?

Yes, sure.
Regarding the intent package, whenever i add the package to pubspec.yaml and do a release build, Then only the realm gets locked and throws that realm exception( Even if i don't write any code related to intent). I also tried the add_2_calendar package and its the same exception. So idk whats locking the realm here.
This is my realm service and i am using it with riverpod provider to watch/read changes.
class RealmServices {
  late Realm realm;

  RealmServices() {
    realm = getRealm();
  }

  Realm getRealm() {
    final Configuration config = Configuration.local(
      [
        TodoModel.schema,
        NoteModel.schema,
        FutureModel.schema,
      ],
      schemaVersion: 8,
    );

    return Realm(config);
  }
}

final realmProvider = Provider((ref) => RealmServices());

If I understand correctly, you have already the realm file on your device and it is locked by some reason.

It gets locked if the release build is made with the intent/add_2_calendar package. Otherwise works.

In order to keep your user data you can copy the file to another location.

About this, by default, the file is stored in data/data location which cant be accessed by a normal user. So copying is not possible. I checked the path and its in data/data/packagename/default.realm.

  final String realmPath = "${Configuration.defaultStoragePath}\realm\\";
  if (!Directory(realmPath).existsSync()) {
    Directory(realmPath).createSync();
    File("${Configuration.defaultRealmPath}\\${Configuration.defaultRealmName}").copySync(realmPath);
    Configuration.defaultRealmPath = "$realmPath\\${Configuration.defaultRealmName}";
  }
  final realm = Realm(Configuration.local([Task.schema]));

You can use this as an workaround, but it will be good to know why the files are locked. Please let me know, if this helped.

Will try this soon.
Also, just to note, I tried changing the default path to storage/emulated/0/android/data/packagename/files/ and in the release build with the intent package added, it worked.
So what's locking the realm in the default path?
Could it be that these intent packages work on the condition that the data is stored in local/internal storage instead of a system partition? I hope this is not the case.

Some updates to the previous comment:
For stack trace, i tried:
https://stackoverflow.com/questions/73591769/got-a-stack-frame-from-packagestack-trace-where-a-vm-or-web-frame-was-expected
and after that, it gave this error logs:
The following PathNotFoundException was thrown building Home(dirty, dependencies: [UncontrolledProviderScope], state: _HomeState#9a51d):
ealm\', path = '/data/data/packagename/files/default.realm\default.realm' (OS Error: No such file or directory, errno = 2)

This is after i copied the code you provided.

So I was trying out copying the old data into the new location. I modified the code you provided for copying data as i tested using the android studio to look into the system partition. I found that the realm doesn't use this path: Configuration.defaultStoragePath/realm but uses the /files path.
but it only works in certain conditions. more explained below:
     String appDir = "/storage/emulated/0/Android/data/packagename/files/database.realm";

this is my new dir created using storage permission
    final String storagePath = Configuration.defaultStoragePath; // old path

    if (Directory(storagePath).existsSync()) { // this has to run to successfully copy the old data into new location
      Directory(storagePath).createSync();
      File("$storagePath/default.realm").copySync(appDir);
      Configuration.defaultRealmPath = appDir;
      print('old data copied');
    }

when data is copied, when we try to add new todo or anything, it creates an error:
    Exception has occurred.
RealmException (RealmException: Error opening realm at path /storage/emulated/0/Android/data/packagename/files/database.realm. Error code: 1021 . Message: Failed to memory buffer:Invalid top array size (ref: 2704, array size: 0) file size: 0, read lock size: some(4096), read lock version: some(4))

To prevent error, we have to reverse the check condition to:
if (!Directory(storagePath).existsSync()) { // now it wont run, making the app work to store new data
      Directory(storagePath).createSync();
      File("$storagePath/default.realm").copySync(appDir);
      Configuration.defaultRealmPath = appDir;
      print('old data copied');
    }

we can use the new directory to store new data by providing it in path
    final Configuration config = Configuration.local(
      [
        TodoModel.schema,
        NoteModel.schema,
        FutureModel.schema,
      ],
      schemaVersion: 8,
      path: appDir,
    );
    return Realm(config);
  }

Do you know how to modify this so as to make it only run once?

Some new tests:
i found out the cause of the issue. In the android/build.gradle file, the code where subProjects are written. If you combine the 2 lines into one single subProjects block, the app will start throwing realm exception that it cant open realm. But reversing them back to separate blocks as they were when you create a fresh project fixes it.
I had them combined since the first build until i added this calendar/intent plugins which starts breaking the build. To test this in your end, go to the same file and combine the 2 blocks:
From:
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
    project.evaluationDependsOn(':app')
}

to
subprojects {
    project.buildDir = "${rootProject.buildDir}/${project.name}"
    project.evaluationDependsOn(':app')
}

and the app will stop working in the release build. You will also notice the build generated won't be in the usual location, i.e, android/build/outputs and build/app/outputs/flutter-apk.
Because normally, they are generated in build folders only, not in android.

Hi @milindgoel15!
Thank you very much about this investigation!
Combining both rows under one subprojects really locked the realm file. The good thing is that it is unlocked if you separate the lines again and restart the app. So, you don't have to copy the realm file, right?
I'm glad to hear that it works for you. We will discuss this in the team, but I don't think we can do anything here to fix that. So I think we can close this issue.

Yes, we don't need to copy the realm file now.
Although I was wondering if it is possible to implement a backup and restore function? Will the same method of copying the db file be used for such a purpose? Realm doesn't have any built-in function ig.

You can use realm.writeCopy(newConfig) to backup and restore. It makes a compact copy of the realm to the path of the new configuration. It has more benefits for the cloud synced realms, but could be used also for local realms. You can check all the test cases here.
https://github.com/realm/realm-dart/blob/eb81b957b35e33dcc493c5bcca4ae04281992293/test/realm_test.dart#L1690

You can use realm.writeCopy(newConfig) to backup and restore. It makes a compact copy of the realm to the path of the new configuration. It has more benefits for the cloud synced realms, but could be used also for local realms. You can check all the test cases here.
https://github.com/realm/realm-dart/blob/eb81b957b35e33dcc493c5bcca4ae04281992293/test/realm_test.dart#L1690

Alright thanks.

@milindgoel15
Hii.
I faced the similar issue few weeks back, and the above solution , separating the subprojects did fixed the issue.

According to your error, it's trying to create a directory named ./mongodb-realm which is not some default location folder.

@milindgoel15 I have not written any code to manually create directory or to create files at any specific directory. I even have to specified the base file path.

check your realm config.

Realm Config is fine, since it is working fine in debug mode.

@Shreedhar73 What platform are you running the app on? (OS & version)? Could you tell me the content of config.path after the config is created?
Also, in the future, please to open new issues pointing to old ones, if you believe you experience a similar issue.

@nielsenko

@Shreedhar73 And the content of config.path?

The app doesnt even reach to the point, where I have called Configuration.FlexibleSync
So I cannot get config.path

But if I close the app and restart the app it works fine and the config path here is : /data/data/com.yipl.onlyever/files/mongodb-realm/appID/64af9051276e5ab5f17044b9/default.realm ..

@Shreedhar73 What is appConfiguration.baseFilePath before constructing the App?

If closing the app, and restarting fixed it, can you then reproduce the issue anymore?

@nielsenko  yes next time I do clean installation of the app, same issue occurs.

Does not compute? 😕 Do you have a minimal reproduction, you can send me?

@nielsenko I have not provided the baseFilePath in the appConfiguration but when I print the 'Configuration.defaultRealmPath'
I get , 'default.realm'. and even if I provide the baseFilePath in appConfiguration as Configuration.defaultRealmPath then i get
FileSystemException: Creation failed, path = 'default.realm' (OS Error: Read-only file system, errno = 30)

@Shreedhar73 Yes, something goes wrong when determining the default.
Are you running on an emulator, or a real device?

@nielsenko  Its on real device. Redmi note 10 pro ( Android 13)

Thx, as a work-around you could try taking a dependency on path_provider and specify a suitable baseFilePath when constructing the realm.App.

@nielsenko That worked,  although I am not sure it is the correct way.
Thank you for you time.

@Shreedhar73 I'm trying to reproduce on my end. I don't have a Redmi note 10 pro at hand, and I cannot make it fail on my end. Can I ask you to run this project on your end?
Basically just:
https://github.com/nielsenko/default_path_issue/blob/575af1b928f43cff1b6d7c7a6630d05eb0f05403/lib/main.dart#L1-L46
Hmm, not sure why the code-link preview is not working, anyway it is basically just trying to open a sync'ed realm:
import 'package:flutter/material.dart';
import 'package:realm/realm.dart';

part 'main.g.dart';

@RealmModel()
class _Stuff {
  @PrimaryKey()
  @MapTo('_id')
  late ObjectId id;
}

final app = App(AppConfiguration('evil-app-mggjg'));
final userProvider = () async {
  return app.currentUser ?? await app.logIn(Credentials.anonymous());
}();

final realmProvider = () async {
  return Realm(Configuration.flexibleSync(
    await userProvider,
    [Stuff.schema],
  ));
}();

Future<void> main() async {
  final realm = await realmProvider;
  runApp(MyApp(realm: realm));
}

class MyApp extends StatelessWidget {
  final Realm realm;
  const MyApp({super.key, required this.realm});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Material(
        child: Center(
          child: Text(
            'successfully opened realm at:\n${realm.config.path}}',
          ),
        ),
      ),
    );
  }
}

@nielsenko Sure just give me few minutes

@nielsenko It is working fine. Seems like dependency in my projects are creating the issue.

@Shreedhar73 Could you show your pubspec.yaml?

bloc: ^8.1.1
realm: ^1.0.3
flutter:
sdk: flutter
flutter_bloc: ^8.1.2
flutter_localizations:
sdk: flutter
intl: ^0.18.0
dio: ^5.0.3
get_it: ^7.2.0
google_fonts: ^4.0.4
flutter_html: ^3.0.0-beta.2
url_launcher: ^6.1.10
just_audio: ^0.9.32
auto_route: ^5.0.0
equatable: ^2.0.5
dartz: ^0.10.1
shared_preferences: ^2.0.20
fluttertoast: ^8.2.1
very_good_infinite_list: ^0.7.0
chewie: ^1.4.0
youtube_explode_dart: ^2.0.1
flutter_inappwebview: ^5.7.2+3
cached_network_image: ^3.2.3
google_sign_in: ^6.1.2
flutter_svg: ^2.0.0+1
firebase_auth: ^4.6.2
firebase_core: ^2.13.1
firebase_crashlytics: ^3.3.1
scroll_to_index: ^3.0.1
modal_bottom_sheet: ^3.0.0-pre
visibility_detector: ^0.4.0+2
# markdown_editable_textinput: ^2.2.0
image_picker: ^1.0.2
expandable:
collection:
video_player:
replay_bloc: ^0.2.4
json_serializable: ^6.6.2
workmanager: ^0.5.1
percent_indicator: ^4.2.3
rounded_background_text: ^0.3.0
amplify_storage_s3: ^1.0.1
amplify_flutter: ^1.0.1
amplify_auth_cognito: ^1.0.1
flutter_screenutil: ^5.7.0
google_sign_in_macos:
path: google_sign_in_macos
google_sign_in_platform_interface: ^2.2.0
http:
flutter_markdown: ^0.6.17+1
markdown_widget: ^2.2.0
flutter_math_fork: ^0.7.1
file_selector: ^1.0.0
path_provider: ^2.1.1
desktop_drop: ^0.4.3
fvp: ^0.4.0
wakelock_plus: ^1.1.1
file_picker: ^5.5.0
@nielsenko

I added all of those packages on the newer project with your code and then the issue is reproducing.

Hmm.. I had to update minSdkVersion to 24 on Android to build, but I still don't have any issue on my end (Running on Pixel 7 Pro - Android 14)

With all those packages ?
Removing fvm works on my side .

Yes, I added them all. But maybe my pubspec.lock ended up in a different state.
I also tried on a Pixel 6 Pro with Android 13, still I see no issue.
What version of fvp was in your pubspec.lock

fvp : 0.4.0
realm : 1.4.0

@Shreedhar73 What version of flutter are you running currently?

@nielsenko 3.10.5

@nielsenko Yes so, I think the issue is solved (atleast for my usecase)
Since the OG 'VideoPlayer' doesnt support mac os platform we are using the 'FVP' ,
.
So the registerWith method for me looks as :
 registerWith(     options: {       'platforms': ['macos']     },   );
Currently, the registerWith method was being called after the realmAppConfiguration. (on main) Calling "registerWith" before setting up app configuration fixes my issue.
( but that doesnt gives anything why the issue occured on first place and I have to test it on mac application too, I will let you know tommorow how it goes.)
Thanks Again

Still cannot make it fail on my end.
Tried calling registerWith after realm app configuration. I ensure to use release mode, and always a fresh install, I can not make it fail.
I have pushed a commit with my latest additions to the [default_path_issue(https://github.com/nielsenko/default_path_issue) repo.
Can you make it fail like this on your Redmi?

@nielsenko with realm and fvp on pubsec, your code is working fine on my end.

@nielsenko
I can replicate the issue (8/10 times) when desktop_drop: ^0.4.3 is on pubspec with fvp and realm.

Still no success (or rather failure) on my end. I have added the desktop_drop package in the repo. If you have any other suggestions to changes please open a PR on
Right now I have to move on with other work. Happy we got it working for you, but annoyed that I don't understand why it fails in the first place.
Good luck with your project


fix(ui): Remove icon background in Safari

I noticed that in Safari, you have this weird background color with all of the icons in the site:

This PR is a quick fix to this issue:

Thank you!


[feature] replace googletagmanager to matomo

What's changed?

Checklist

[x]  I have read the Contributing Guide
[x]  I have written the necessary doc or comment.
[x]  I have added the necessary unit tests and all cases have passed.

Add or update API

[x] I have added the necessary e2e tests and all cases have passed.

needs to replace the "siteId"

needs to replace the "siteId"

I have apply for the siteId, not get reponse yet.


Unit test passed:
Test Suites: 1 skipped, 51 passed, 51 of 52 total
Tests:       5 skipped, 230 passed, 235 total
Snapshots:   46 passed, 46 total
Time:        39.91 s
Ran all test suites.
✨  Done in 41.88s.

yarn build
➜  anomaly-detection-kibana-plugin git:(7-10-0-up) ✗ yarn build
yarn run v1.22.10
$ yarn plugin-helpers build && echo Renaming artifact to $npm_package_config_odfe_name-$npm_package_config_odfe_version.zip && mv ./build/$npm_package_config_odfe_name*.zip ./build/$npm_package_config_odfe_name-$npm_package_config_odfe_version.zip
$ node ../../scripts/plugin_helpers build
 info Loaded config file from [/Users/yizheliu/workspace/kibana-7100/kibana/plugins/anomaly-detection-kibana-plugin/.kibana-plugin-helpers.json]
 info deleting the build and target directories
 info running @kbn/optimizer
 │ info initialized, 0 bundles cached
 │ info starting worker [1 bundle]
 │ succ 1 bundles compiled successfully after 41.4 sec
 info copying source into the build and converting with babel

  `@babel/polyfill` is deprecated. Please, use required parts of `core-js`
  and `regenerator-runtime/runtime` separately
 info running yarn to install dependencies
 info compressing plugin into [opendistroAnomalyDetectionKibana-7.10.0.zip]
Renaming artifact to opendistroAnomalyDetectionKibana-<IP_ADDRESS>.zip

Have also installed artifact to binary kibana and done some sanity tests.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Another thing - can you bump the versions for the test workflows? Regarding the e2e test workflow, I've outlined what I think all needs to be changed based on the new naming conventions here. Let me know and I can put out a follow up PR to handle this as well.

Another thing - can you bump the versions for the test workflows? Regarding the e2e test workflow, I've outlined what I think all needs to be changed based on the new naming conventions here. Let me know and I can put out a follow up PR to handle this as well.

Sure. will bump the kibana and ODFE version there.


Empty text childs increase XML file size

// (pseudo code)
xml::node Node = ParentNode.append_child("NewChildNode");
Node.text().set(""); // << create new text-type subchild with no text
// after save document to file we have:
<NewChildNode></NewChildNode>
// but must be (by default output format)
<NewChildNode />
// "virtual" empty text-child lock short form of record

Sure... why is this a problem? It's not clear to me if changing this is worth the benefit, as the application can just not create empty text children.

I have text fields assigned by a template, without checking for empty/filled.
There are many fields in the file and often most of them are empty.
This increases the size of the files by 20-30%, and there are... a lot of files on the disk.
Besides, why leave a mistake when you can do better?

Ok, and it's impractical for your application to check if the field is empty before assigning? What if the field value is purely white space?
I'm not entirely sure where the "mistake" is here. Maybe set() shouldn't even create a PCDATA node, or maybe the library works fine; it's an odd corner case.

THATS not app size of responsibility

This behavior is confusing because:

you create a XML file with empty nodes -> after save with default flags then empty nodes are expanded.
you load that file and save it again with default flags -> empty nodes got compressed.

I found out after comparing files with diff tool.
It is impractical to compare those files using a diff tool.
So in case one wants to have expanded empty nodes then one should use existing format flag format_no_empty_element_tags.
Omitting that flag one would always expect compressed empty nodes.


refactor(client): split lower-jaw to separate files

Checklist:

[x] I have read and followed the contribution guidelines.
[x] 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 #50118

Was the linked issue triaged?

The issue mentioned has not been opened up for contributors yet. Feel free to revisit when the help wanted label has been added.


Feature Request

Do you think you could add support for emi? cause as of right now when you try using the craft button it wont work

well i don't know how EMI works but i'll give it a try

Even if you can't it's still a great mod


Minor code improvements

Only the user's tag is stored when storing a snipe, rather than the entire User object. This decreases ram usage.
Since all of the options fields for slash commands had the same value, I just assigned it to options, then referenced it in each of the commands.
Arguments passed into event functions are now destructured more often. This is opinionated, but I think it results in cleaner code.

If you plan on merging this PR, please add the hacktoberfest topic to this repository first. Thanks!

i need help with this bot i have successsssfully managed run the code but i dont know HOW to use it please add how to use in README.md

i need help with this bot i have successsssfully managed run the code but i dont know HOW to use it please add how to use in README.md