Failed to connect to docker service

Since yesterday  we are receiving this error:
GetImageHistory failed for ImageName=xxx.azurecr.io/xxx/web/api:1.0.0-dev.34 with unexpected error. Exception=System.Fabric.FabricException: Failed to connect to DockerService at socket '/var/run/docker.sock'. IsDockerServiceManagedBySF=TrueError=System.Net.Internals.SocketExceptionFactory+ExtendedSocketException (0x80004005): Connection refused /var/run/docker.sock
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress so
Completely rebuilding the cluster solved the issue but it just popped up again.
How can we solve this and why does this error suddenly pop up?
We are using Ubuntu 16.04-LTS and running service fabric 7.1.418.1

@brechtvhb Are you able to connect to Docker service using the CLI (e.g. docker ps -a) from the shell prompt?

@brechtvhb @gkhanna79 Hi would u be able to share how did u fix this issue？Thanks.


fix(cargo): fix cargo.toml

@homu r+

:pushpin: Commit a82ea9e has been approved by MichaelHirn

:hourglass: Testing commit a82ea9e with merge 365038b...

:sunny: Test successful - status


Why Wont The MediaNotificationManager Die?

I have this line in my constructor on my page.
 CrossMediaManager.Current.AudioPlayer.StatusChanged += OnStatusChangedHandler;
This is a method in that class.
private void OnStatusChangedHandler(object sender, StatusChangedEventArgs e)
        {
            if (e.Status == Plugin.MediaManager.Abstractions.Enums.MediaPlayerStatus.Stopped)
                audioCleanup();
        }

This is audioCleanup()
        protected void audioCleanup()
        {
            if (CrossMediaManager.Current.AudioPlayer.Status != Plugin.MediaManager.Abstractions.Enums.MediaPlayerStatus.Stopped)
                CrossMediaManager.Current.AudioPlayer.Stop();

            if (CrossMediaManager.Current.MediaNotificationManager != null)
            {
                CrossMediaManager.Current.MediaNotificationManager.StopNotifications();
            }
        }

The media manager notification bar thing at the top disappears and then reappears in a second. Despite there not being any audio playing. I'm testing on Android atm.

I had this exact issue, in my case it was a timer I had setup calling UpdateNotification, which reinitializes the Notification.

@mike-rowley I  don't recall ever having called UpdateNotification. My application generates a sound file based on user input upon a button click. At which point, I generate a .wav and await the media manager to play the sound. That's the extent of it.


Failure to cleanup temp files on Windows machine

On a windows machine, I am occasionally receiving an exception during the file cleanup process in Launcher.js on line 87 for version 0.9.0. This is causing the temp files to remain in their directories.
Error: EPERM: operation not permitted, unlink 'PROJECT_DIRECTORY\node_modules\puppeteer\.dev_profile10\CrashpadMetrics-active.pma'     at Object.fs.unlinkSync (fs.js:1066:18)     at fixWinEPERMSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:210:13)     at rimrafSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:310:28)     at PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:341:5     at Array.forEach (native)     at rmkidsSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:340:26)     at rmdirSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:333:7)     at fixWinEPERMSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:208:5)     at rimrafSync (PROJECT_DIRECTORY\node_modules\rimraf\rimraf.js:310:28)     at ChildProcess.__dirname.launch.chromeProcess.on (PROJECT_DIRECTORY\node_modules\puppeteer\lib\Launcher.js:87:7)
I was able to resolve this problem locally by changing line 17 to
const removeRecursive = require('rimraf');
and changing line 87 to
removeRecursive(userDataDir, (err) => {         if (err) { throw new Error(err); }       });

Thank you for the report!
This should be fixed on tip-of-tree with 271fd093794aeb91b29941a6eea0f1bc7caff2c4 and 11e3343b3d8c5a0cca4cb6abc08c749e71c23233.

How can I update it throught npm?

You can install as:
npm uninstall puppeteer
npm install https://github.com/GoogleChrome/puppeteer/

I was trying just install first but got an error; with uninstall it seems OK (but it will download chromium again).

Hi, thanks, I got v0.9.0, how can I get the version with the commits that fix this bug?

"Thank you for the report!
This should be fixed on tip-of-tree with 271fd09 and 11e3343."

npm install https://github.com/GoogleChrome/puppeteer/ will install the latest status quo.

thanks man

Still getting the error. It's now creating the profile in temp dir but still unable to delete it:
Error: EPERM: operation not permitted, unlink 'C:\Users\<me>\AppData\Local\Temp\puppeteer_dev_profile-gIv5fX\BrowserMetrics-active.pma'

I dug into the code and it seems giving rimraf a timeout of 1s helps:
lib/Launcher.js:101
    function killChromeAndCleanup() {
      helper.removeEventListeners(listeners);
      chromeProcess.kill('SIGKILL');
      // removeSync(userDataDir) // error
      // setTimeout(() => removeSync(userDataDir))  // error
      // setTimeout(() => removeSync(userDataDir), 100)  // error
      setTimeout(() => removeSync(userDataDir), 1000) // no error!
    }

not sure if it's the best solution though.

Now this is the dupe of #298


deserializer isn't distinguish long and double type.

Hello, I'm trying to parsing the Unity Scene file using this library.

left is the original Image and right side is the deserialized and serialized by the library
As you can see in the above image, fileID is long type as I believe, but the deserializer make it as double type.
fileID was<PHONE_NUMBER>477804610 but changed to 1.0580640394778E+18.
So when I serialize it again, the scene file would be corrupted due to those issue. Could you fix it? Thank you so much.
I used this library like below code
    var memory = new ReadOnlyMemory<byte>(Encoding.UTF8.GetBytes(sceneString));
    var collection = YamlSerializer.DeserializeMultipleDocuments<dynamic>(memory).ToList();
    ...

would it be possible to customize deserialize only for the type IYamlFormatter<KeyValuePair<TKey, TValue>> when TKey is string and it is fileID ?

Helo, tanks for the report.
Fixed in #55


Customer Orders DataTable –The finance, marketing, and sales departments want to understand customers better but need the historical data to do so. They want to have a database/pseudo-DB that stores all ofthe customer order information along with the time and date of their orders. [This dataset will grow each time a customer order comes in and is processed (for simulated data this can be thought of a copy of the customer_orders_teamX.csvdata file)]

This issues has been resolved when after the transfer from java to python.


Add Portuguese Language

Thank you for contributing! Portuguese will be shipped with version 2.3.1


[feature] Fix template of Llama2 to match the offical template

close #282

@hiyouga please help to merge


chore: keep export pods v2 commands behind enableExportPodV2 dev config option

This PR adds a dev config option enableExportPodV2 for the enablement of Export Pod V2 commands.
Manually tested this with:

WHEN enableExportPodV2 is undefined or false

[x]  THEN Dendron: Export Pod V2 command should not be visible in command pallet.
[x]  THEN Dendron: Configure Export Pod V2 command should not be visible in command pallet.
[x]  THEN Dendron: Configure Service Connection command should not be visible in command pallet.
[x]  THEN export pod v2 keybinding shortcuts should not run the export v2 commands

WHEN enableExportPodV2 is true

[x]  THEN Dendron: Export Pod V2 command should be visible in command pallet.
[x]  THEN Dendron: Configure Export Pod V2 command should be visible in command pallet.
[x]  THEN Dendron: Configure Service Connection command should be visible in command pallet.
[x]  THEN export pod v2 keybinding shortcuts should execute the export v2 commands.

Telemetry commit lgtm.  @hikchoi - could you re-review the latest command package.json changes and approve if it looks good? Thanks!


[docs] Some fixes to the Link component page

Fixed some typos
Added missing punctuation
Added backticks around window.opener

[x] I have followed (at least) the PR section of the contributing guide.

@kyarik I love the proof-reading you have done on WebFundamentals. If for some reason, you happen to run a similar effort here. I would appreciate if it could be done in batches, rather than in one line pull request changes. Each pull request has an overhead for us, we have to review it.
Anyway, thanks for looking into our documentation :)

@oliviertassinari Sure, if you prefer, I can batch changes related to several pages (rather than one page at a time) as long as they are small (like in this pull request).

@kyarik Thanks


No Random vote in DD

Random vote in DD is not showing up any more it is bugged or disabled

Look into it please, I have a lot to do.

Fixed by Mr. SDK 2e41eec2481fe767e15bc4f6ee7d63269ae3a3e0


fix asset display when asset has no owner

fixes #513

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 4 (25.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 64.982%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

flexmeasures/data/services/sensors.py
1
4
25.0%

Files with Coverage Reduction
New Missed Lines
%

flexmeasures/data/services/sensors.py
1
18.18%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
6480

Relevant Lines:
9362

💛  - Coveralls


Add otion to place menu bar

I noticed that the menu bar, containing <>, Trash folder, new-mail icon etc is located on the bottom of the screen for smartphones, while at the top of the screen for tablets. This is quite uncomfortable, as the 'back' button on the tablet is at the bottom  of the screen as well. So you are moving your hand from bottom to top and vice versa constantly.
Expected behaviour: Have menu bar constantly on the bottom of screen, or have this configurable (all options I tried do not give the desired result....)
K-9 Version: 5.600
Android: 7 & 8
Devices: Samsung Galaxy S7 Edge, Tab-A

Making this configurable is quite a bit of work. And once implemented it's one of those things that make maintenance hard. So we'd like to avoid adding these kinds of features.
We will probably get rid of the < and ´>` actions and instead allow swiping left and right to move to the next/previous message. See #585.
On a tablet you could enable split mode: Global settings > Display > Show split-screen
That will display the message list next to the message view and you won't have to use the back button to get from a message to the list.

@cketti, thanks for your explanations.
First question is WHY are Tablet and Smartphone implemented different. Reducing this to one standard, e.g. menu bar at bottom, should already reduce complexity.
Swiping looks, good, but is already some years in the pipeline....

We use a flag that tells the Android framework to show actions using a "split action bar" on narrow screens. There's no extra work involved for us as app authors.
For phones this means action buttons move from the bottom to the top when switching from portrait to landscape orientation. This is a source of great confusion to some users. Which is why we will get rid of this in the next major version. Actions will always be at the top.

Actions will always be at the top.
Considering the fact that Task Manager, Home- and back button are at the bottom of Android Smartphones, this seems not to be the most ergonomic decision....

Which is why we will get rid of this in the next major version. Actions will always be at the top.

Oh gosh, please don't! Action buttons at the top are terrible. I would really like to be able to have these buttons at the bottom all the time, including tablet view.

Hi, i have a related Problem. I am on Android 9 and k9 5.600. In the Android system settings I can change the size of items (display-extended-display size). When switching from default to small, k9 starts to treat my Nokia 8 like a tablet and moves the actions to the top (always, not just when I turn out to the side). That Alone is very annoying, but since the device is to narrow to display all the action buttons (no matter if held horizontally or vertically) and action buttons that overflow the screen are not accessible in any way, it becomes impossible to reply to an open mail, I have to go back to the list of mails am long click the mail in offer to access the reply button.
This seems to be a bug to me.
It would be a nice fix, if I as a user, could overwrite the flag that you use to determine if you split the actions into top and bottom or not (so I want to overwrite what ever heuristic you are using to determine this flag). Shouldn't be much effort.
Thx for all the great work in k9.
Alex

Yes I agree cannot we have  a choice between one action bar or two
I need the action bar at the bottom in landscape mode

Yes I agree cannot we have  a choice between one action bar or two
I need the action bar at the bottom in landscape mode

Got the K9 upgrade looking for a way to put the actions bar back to the bottom.
On a big smart phone it's a terrible user experience when using one handed. Holding the phone at the bottom it is near impossible to hold it and get your thumb to the top.


column has a 2GB limit

do I read it correctly? column size has a 2GB limit.

There is a limit of 2GB per file. This means that the compressed size of a
column cannot exceed 2GB.
However, you can have more segments if your data size is larger.
-Venky
On Fri, Jun 24, 2016 at 4:24 PM, MubeenAfzal<EMAIL_ADDRESS>wrote:

do I read it correctly? column size has a 2GB limit.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/pinot/issues/232, or mute the thread
https://github.com/notifications/unsubscribe/AIUJl4wzYrBwA25hU6fFonsTjCjQphZ1ks5qPGc7gaJpZM4I-MxQ
.

@MubeenAfzal did that answer your question?


[Parser] Don't report AttrsRequiringFoundation in inactive config block

What's in this pull request?
In Linux, compiling this used to emit an error:
#if os(OSX)
import Foundation
@objc class Foo: NSObject { }
#else
class Foo { }
#endif

error: @objc attribute used without importing module 'Foundation'
@objc class Foo: NSObject { }
~^~~~

While we can silence it with -disable-objc-attr-requires-foundation-module option,
Entirely disabling this diagnosis is not safe for us.

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@jrose-apple Could you review please?

Thanks for looking at this! I'm glad the solution is so simple. Can you also add a test that shows a nested use of @objc, to prove that isInactiveConfigBlock is looking at parent scopes as well? (An @objc method in a non-ObjC class inside a top-level #if would do it.)

We have this tracked internally as rdar://problem/23487944.

@swift-ci Please test and merge

CI failures are unrelated.

Pulling into swift-3.0-preview-1-branch: https://github.com/apple/swift/pull/2705


List several improvements or tutorials on how to edit the decomp

like pokeemerald
where you can replace the engine with that high quality audio mixer
https://github.com/ipatix/gba-hq-mixer/tree/main

Can you clarify which one you mean exactly?

How to edit the decomp for personal/hacking use
How to edit the decomp to improve the codebase, documentation...
I'm assuming it's the first one, but I just want to be sure

the first one, for fixing several vanilla bugs

Yeah, like Project ZM.

also i don't like discord anymore... now i use revolt.chat from now on.


Update QNX toolchain files to QNX 7.1

Brief feature description
The QNX toolchain files in tools/toolchains/qnx are written for QNX 7.0 and need to be updated to QNX 7.1.

How to get the qnx_sdp71_aarch64le.cmake?

Currently there is none. If you have access to QNX you could adjust the files in tools/toolchains/qnx and create a PR.


pull request for e2e test at 11/12/2016 06:56:08

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


The tests are absurdly slow

The tests take too long to run. I don't understand why; they should take mere milliseconds.

How long do they take to run on your machine?

43s wall-clock (1m18s user, presumably across two CPUs?).
For comparison, the analyzer takes 6 seconds (which is also too long).

Sounds like the same issue @apwilson was having with the test harness crawling symlinks.

yeah, though i wasn't able to figure out which version of the test package it's using so i could change it. :-/

Oh hey I did a gclient sync and now it does pick up my hacked copy of test. Now it runs in 6 seconds!

Awesome!
Just for reference, the workaround is this:  https://github.com/apwilson/test/commit/368cf30a5d154d971dba72302f8c3b32a83b2ae7

And for reasons why dart/test don't want to implement that fix, see: https://github.com/dart-lang/test/issues/337


Prompt for deploying SMS Proxy and ask for SMS URL + Credentials

Closing as the project has been refactored and this bug issue no longer applies - please see https://github.com/apigee/openbank#previous-versions


versions: Update Kubernetes, containerd and cri-o

Update supported versions of Kubernetes with its
corresponding CRI implementations:

Kubernetes from 1.10.5 to 1.12.2
cri-o from 1.10 to 1.12.0, commit:
fa540c8e806d28c2cbcd157bdf8acf2b20990ab6 as it is needed
for fixing the devicemapper issues when removing a pod.
More info on this issue, see:
kubernetes-sigs/cri-o#1883
containerd from 1.1.3 to 1.2.0

Fixes: #927.
Signed-off-by: Salvador Fuentes<EMAIL_ADDRESS>

fa540c8e806d28c2cbcd157bdf8acf2b20990ab6 as it is needed
for fixing the devicemapper issues.

Could you add a reference in the commit to what those issues are?

/test
Decided to remove the openshift update as the cluster setup changed and still do not have
it ready, will work it on another PR.
@jodh-intel I added more information on the devicemapper issue.

Thanks @chavafg!
lgtm

Saw this on metrics:
17:59:54 Setting up kubeadm (1.12.2-00) ...
17:59:54
17:59:54 Configuration file '/etc/systemd/system/kubelet.service.d/10-kubeadm.conf'
17:59:54  ==> Modified (by you or by a script) since installation.
17:59:54  ==> Package distributor has shipped an updated version.
17:59:54    What would you like to do about it ?  Your options are:
17:59:54     Y or I  : install the package maintainer's version
17:59:54     N or O  : keep your currently-installed version
17:59:54       D     : show the differences between the versions
17:59:54       Z     : start a shell to examine the situation
17:59:54  The default action is to keep your current version.
17:59:54 *** 10-kubeadm.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package kubeadm (--configure):
17:59:54  end of file on stdin at conffile prompt
17:59:54 Errors were encountered while processing:
17:59:54  kubeadm
17:59:54 E: Sub-process /usr/bin/dpkg returned an error code (1)

thanks @grahamwhaley, I think the best would be to remove/purge the package on the node cleanup. Will add a step on the tests repo.

@grahamwhaley the metrics issue is solved and the metrics passed.

LGTM


go-advices 中文版本

Similar to #6 and look forward to you adding more advices.

Hi, thank you for the contribution, I'll merge your PR after #6

I translate some new advices to zh_CN.


Reproducible Build: kogito-runtime repo

As part of the Apache migration, after adding the required configurations, we need to fully enable the Reproducible Build mechanism in kogito-runtime repo
Current status:

PR submitted: https://github.com/apache/incubator-kie-kogito-runtimes/pull/3393


TS error: Property 'delta' does not exist on type 'CreateChatCompletionResponseChoicesInner'. ts(2339)

Describe the bug
Property 'delta' does not exist on type 'CreateChatCompletionResponseChoicesInner'.ts(2339)

To Reproduce
When streaming, try accessing completion.data.choices?.[0].delta instead of completion.data.choices?.[0].message
Code snippets
No response
OS
macOS v13.1 (22C65)
Node version
node v18.12.1
Library version
openai v3.2.1

We have an upcoming version v4.0.0 that ovehauled our TypeScript types; please give it a try and let us know in the thread whether it suits your needs!


Support for Enable DTMF Settings

Hi,
In the CX UI user can define if the bot accept DTMF input in the current state.
This is not reflected in the bot response. I know that for CCAI clients SDK, the bot response do contains this information.
I would appreciate it if you could reflect this info.
Thanks!

Thank you for providing this feature request for the Dialogflow service. Please file your feature request here on the public issue tracker.


Query issues. Display as catalog. Get path

Work in progress

[x] Store/Issues.elm
Read branch /issues once from Firebase
[x] Component/Catalog.elm
Display a given number of issue slugs. Scroll with buttons Prev/Next
[x] Page.elm
Root component split off from Main.elm
[ ] Main.elm
Preparations for routing: Get initial and changing path of window's URL

@ThomasWeiser everything works as expected.

[x] Sort pages in reverse chronological order
[x] Sort issues on the page in chronological order
[x] "Next" and "Previous" buttons switch pages in correct order
[x] "Next" is disabled on the last and "Previous" — on the first page

Just playing with issues.

@ThomasWeiser if you we are done here, please let me squash commits and merge it.


IDEA for nerdtree

Can you add something like that? https://dl.dropboxusercontent.com/u/5837324/vim-nerdtree.png (directory icons). I use a patched nerdtree

@aliev Yes that is definitely possible. I believe right now I just ignore folders. I will see if I can get something in for this on next release unless you want to try it yourself.

@ryanoasis thank you!


[plugin/datadog] Logging to statsd server

Compiles metrics like Request count, size, Response status and latency and send it to
Datadog statsd server

LGTM

Thank you for your contribution!

Figuring out how to implement a statsd plugin for my company needs, I noticed this PR and issue #624.
What is the difference between this Datadog statsd plugin implantation and a generic statsd plugin implantation? If it is very similar shouldn't we have just one generic statsd plugin with different configurations, i.e. a Datadog configuration?
@thibaultCha @shashiranjan84 @Tieske

It still can be used with any statsd server but it is developed keeping
Datadog in mind as part of business strategy. We will come with a generic
statsd logger too.
On Dec 25, 2015 5:30 AM, "Noam Elfanbaum"<EMAIL_ADDRESS>wrote:

Figuring out how to implement a statsd plugin for my company needs, I
noticed this PR and issue #624.
What is the difference between this Datadog statsd plugin implantation
and a generic statsd plugin implantation? If it is very similar shouldn't
we have just one generic statsd plugin with different configurations, i.e.
a Datadog configuration?
@thibaultCha @shashiranjan84 @Tieske
—
Reply to this email directly or view it on GitHub.

Cool! Another question, are you planning to add a consumer notion in the
plugin? i.e. not just which API the call was directed to but also which
consumer initiated it?
On Fri, Dec 25, 2015, 5:36 PM shashi ranjan<EMAIL_ADDRESS>wrote:

It still can be used with any statsd server but it is developed keeping
Datadog in mind as part of business strategy. We will come with a generic
statsd logger too.
On Dec 25, 2015 5:30 AM, "Noam Elfanbaum"<EMAIL_ADDRESS>wrote:

Figuring out how to implement a statsd plugin for my company needs, I
noticed this PR and issue #624.
What is the difference between this Datadog statsd plugin implantation
and a generic statsd plugin implantation? If it is very similar shouldn't
we have just one generic statsd plugin with different configurations, i.e.
a Datadog configuration?
@thibaultCha @shashiranjan84 @Tieske
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/kong/pull/758#issuecomment-167245742.

--
Noam Elfanbaum
+972-545551680

We will keep making updates to plugin to add new metrics. Meanwhile  I
would advise you to try our another product Galileo for detailed api
analytics. Kong has a plugin for that too.
On Dec 25, 2015 8:14 AM, "Noam Elfanbaum"<EMAIL_ADDRESS>wrote:

Cool! Another question, are you planning to add a consumer notion in the
plugin? i.e. not just which API the call was directed to but also which
consumer initiated it?
On Fri, Dec 25, 2015, 5:36 PM shashi ranjan<EMAIL_ADDRESS>wrote:

It still can be used with any statsd server but it is developed keeping
Datadog in mind as part of business strategy. We will come with a generic
statsd logger too.
On Dec 25, 2015 5:30 AM, "Noam Elfanbaum"<EMAIL_ADDRESS>wrote:

Figuring out how to implement a statsd plugin for my company needs, I
noticed this PR and issue #624.
What is the difference between this Datadog statsd plugin implantation
and a generic statsd plugin implantation? If it is very similar shouldn't
we have just one generic statsd plugin with different configurations,
i.e.
a Datadog configuration?
@thibaultCha @shashiranjan84 @Tieske
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/kong/pull/758#issuecomment-167245742.

--
Noam Elfanbaum
+972-545551680
—
Reply to this email directly or view it on GitHub
https://github.com/Mashape/kong/pull/758#issuecomment-167248284.


Do not use SQLite query for direct graphs.

As seen, recursive query on a tree will produce duplicate data. To fix this it is better to compose the data directly in the program. Another study on the datatype shall be done to finalize it in two categories: internal data and final data. Internal data will be used to sort, group and query information. Final data will be used to render the information to the webpage or other future media.

Use #1 as reference.


disable waterbody execution in pybind/troute test

The t-route waterbody input structure has changed enough that the test input file doesn't conform to the required inputs.  Until the inputs can be fixed, simply disabling the waterbody execution portion of the t-route run will allow the test to still execute a simple routing test via the pybind interface in ngen.
Changes

disable waterbody execution in t-route configuration for pybind/troute test

Testing

Using the correct t-route submodule (#399) should allow the test to pass with this config change.

Todos

Fix the watebody-params.json to conform to latest waterbody/lake definition (and probably create a lakes.json) sorry @mikejohnson51 😄

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (link if applicable)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged / future todos are captured in comments
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[x] Reviewers requested with the Reviewers tool :arrow_right:

Target Environment support

[x] Linux
[x] MacOS

Is there a documented waterbody/lake definition I can look at?

Is there a documented waterbody/lake definition I can look at?

We worked out some things before AGU, I have the example files from HUC01 if that helps?


Asynchronous Restore Requests

Extends the sync protocol to accept a 202 response from the server that is processed in full, and then instructs CommCare to wait for a set amount of time before requesting additional data.
Extends asynchronous tasks to be able to inform dialogs that they should enable/disable cancellation.

One minor comment. Will merge once this PR is mergeable.

@ctsims status of this? no longer mergable and jenny's comment

I need to reconcile this with some changes in the task, will try to get it
fixed up as soon as Simon's side is ready and we can test directly against
HQ.
-Clayton
On Sat, May 9, 2015 at 3:33 PM, wpride<EMAIL_ADDRESS>wrote:

@ctsims https://github.com/ctsims status of this? no longer mergable
and jenny's comment
—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/commcare-odk/pull/142#issuecomment-100506452.

can we close this?

Yeah, I'll do that. It's pointless until HQ will resource their side.
On Fri, Jan 22, 2016 at 10:05 AM, Phillip Mates<EMAIL_ADDRESS>wrote:

can we close this?
—
Reply to this email directly or view it on GitHub
https://github.com/dimagi/commcare-odk/pull/142#issuecomment-173944113.


Error messages contain spurious LF chars, displayed as boxes containing "0010" (MD 4.0.2)

From @rneatherway on April 30, 2013 16:53
Copied from original issue: fsharp/fsharpbinding#153

Not seen that, what version of MD/XS?

Ah, I'm still on 4.0.3
On 1 May 2013, at 16:32, Robin Neatherway<EMAIL_ADDRESS>wrote:

This is with Monodevelop 4.2 on Linux:
—
Reply to this email directly or view it on GitHub.

@rneatherway I guess you mean 4.0.2.
4.1.1 just came out today on the alpha channel.

From @rneatherway on May 1, 2013 20:40
Oops sorry I meant 4.0.2 yes.

From @rneatherway on May 1, 2013 15:32
This is with Monodevelop 4.2 on Linux:

I don't get this on Windows or Osx, Its possible its some upstream issue in linux MonoDevelop.

From @rneatherway on March 25, 2014 13:49
It still happens in 4.2.3. The repro is to put the following in a file of your project:
let x : Map<int,string> = Map.empty
let y = Map.fold x x x

and then try to build.

I wonder if this is still an issue?

Does not occur in 5.x closing now.


[$250] Android – Chat – The keyboard overlap composer box when editing mid-message adding new lines

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:  1.4.82-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4625190
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Log in
Open any chat
Send 5 messages
Long press on the first message and select Edit comment
Add few new lines using Enter key

Expected Result:
The composer is fully visible
Actual Result:
The keyboard overlap composer box
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/6812f54a-353c-45b2-b728-fb373e0c63a8
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01efc5428d2089d69a
Upwork Job ID:<PHONE_NUMBER>813885921
Last Price Increase: 2024-06-13

Issue OwnerCurrent Issue Owner: @suneox

@kadiealexander  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
The issue is reproducible for native android from the steps mentioned in the issue.
In native android app, keyboard overlaps with "edit comment" input.
What is the root cause of that problem?
Since the "edit-comment" Composer is rendered in-place in the reportList, instead of being at fixed at the bottom position unlike "ComposerWithSuggestion" (Send message input), the changes in height of the composer are not known to the reportList, as a result, it's possible to move the composer out of visible area while still being focused.
The reportList is scrolled at the correct position when the composer is first focused, which uses scrollToIndex functionality here, along with combination of InteractionManager and requestAnimationFrame.
What changes do you think we should make in order to solve the problem?

refactor: extract the logic used in above referenced link to a function scrollToActiveCommentComposer.
refactor: use scrollToActiveCommentComposer in  onFocus .
fix: call scrollToActiveCommentComposer in updateDraft here (`onChangeTex callback of the composer) only if the platform is android-native.

Pseudo-code for the change:

   ...
   const scrollToActiveCommentComposer =  useCallback(() => {
        InteractionManager.runAfterInteractions(() => {
            requestAnimationFrame(() => {
                reportScrollManager.scrollToIndex(index, true);
            });
        });
    }, [index, reportScrollManager]);
    ...
    const updateDraft = useCallback(
        (newDraftInput: string) => {
            const isNativeAndroid = getPlatform() === CONST.PLATFORM.ANDROID;
            if (isNativeAndroid && isFocused) {
                scrollToComposer();
            }
    ...
    <Composer
               onFocus={() => {
                                setIsFocused(true);
                                scrollToComposer();
                                ...

What alternative solutions did you explore? (Optional)
alternate solution would be to disable scrolling when the input is active, that way input always stays fixed above keyboard, at the bottom of the view.
not really sure of the feasibility of this.
result video
https://github.com/Expensify/App/assets/172590473/0895ed47-ae9c-4d82-b47d-eaa6161af191

@vaib-contrib bump!

Proposal
Please re-state the problem that we are trying to solve in this issue.
On android scroll doesn't trigger update input position
What is the root cause of that problem?
When composer change layout and input on scroll view have enough space the input field doesn't update the scroll position
What changes do you think we should make in order to solve the problem?
In the ReportActionItemMessageEdit component, when the layout changes on Android, we must trigger a scroll to the currently edited index.
By listen event onLayout at Composer and trigger scrollToComposer when layout change
    <Composer
      multiline
      ....
+     onLayout={() => {
+         if(Platform.OS !== 'android') {
+             return;
+         }
+         console.log(`___________ Layout:Change ___________`);
+         InteractionManager.runAfterInteractions(() => {
+             reportScrollManager.scrollToIndex(index, true);
+         });
+     }}

POC

What alternative solutions did you explore? (Optional)

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0177bfe6ca1fe859f7

@suneox thanks a lot for the feedback on the proposal.
Here's my clarification:

Your root cause analysis is incorrect because scrollToIndex is only called when focused, and this issue does not occur when editing messages near the bottom.

The reason issue is not occurring when the item is at the bottom, could be because of this somewhat related to the react-native's open issue, and we're unintentionally benefiting from it.
However, if you manually scroll the input out of the view, the issue can be reproduced for messages near the end as well.

for items near the end of list
https://github.com/Expensify/App/assets/172590473/d787a783-3514-40fc-b785-4fc88cc07b67

Your main proposal appears to work when triggering scrollToComposer on every update, but this contradicts your RCA

Yes, I was not aware of list-items near end of FlatList apparently being handled differently internally when using FlatList's scrollToIndex, but it's somewhat reproducible for the messages near the end of the list as well, like I mentioned earlier. However, the root cause still is because of the change in composer's dimensions not being taken into account.

and it doesn't make sense to trigger scrolling every time typing

Agreed, reasoning behind using onChangeText was that I just wanted to cover a potentially related corner case when the list is scrolled after keyboard is visible, and then when you type, android scrolls the composer incorrectly (see video).

check here
https://github.com/Expensify/App/assets/172590473/fcb1d35c-307d-4e39-9c98-78e34147a32c

If we don't want to cover this case, we could use composer's `onLayout` callback can be used to detect change in height of composer.

Your alternative solution is not a common pattern for editing and should be tested across all platforms.

Yes, the alternate solution would indeed lead to a larger change. I just wanted to mention in case it's a viable option.

Proposal updated
Add POC video

(Platform.OS !== 'android')

Generally we try to avoid solutions that do this, don't we? Can we handle it via a .android.ts file instead?

> Can we handle it via a .android.ts file instead?
@puneetlath @suneox
Yes, we can do it by creating a libs/ReportActionItemEventHandler/index.android.ts file. Then, move the logic handling the onLayout change into this file to separate the specific logic for Android

@suneox This PR is for this issue. Can you check it?

Payouts due:

[ ] Contributor: $250 @huult
[ ] Contributor+: $250 @suneox

Upwork job is here.

Hi @kadiealexander,  thank you. I accepted your offer on Upwork.


Update the usb module to collect device product ids

This change allows munkireport to collect the product ids from USB devices. An additional column is added to the usb table called product_id. Product ID will be available on the USB listing and on the USB Devices tab for each client. Please shout at me if there are any other changes I need to include.

@tuxudo thanks for the review! I've add the suggested changes.

The USB module has moved here: https://github.com/munkireport/usb


Implement get_reports

This PR implements get_reports, which is used by the Leader to retrieve reports from pending report store when preparing aggregation initialization requests.
Several test cases that checks the functionality of this method are also added.
Ref: #20.

Since reports are stored in buckets of time windows (see BucketInfo), I think it is natural to specify a time interval when selecting such buckets.
If we want to remove Intervals, then we would also need to replace the bucket representation with a different data.
I also don't think it would be a good idea to deviate too much from the specs, as nonces and batch intervals seem to be a center part of managing reports sent from Clients.


[MB-8646] TOO is able to see crating details for MTO service items

Description
Add the description to crating service items and change "Item Dimensions" and "Crate Dimensions" labels to "Item dimensions" and "Crate size".
Reviewer Notes
Did I cover everything needed?
Setup
PARAMS move code has the crating service items, go to the MTO page and you should see the new details.
make server_run
make client_run

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Screenshots

Messages

:book:
:link: MB-8646

  Generated by :no_entry_sign: dangerJS against 7f8ef8ce611bb9470dc64dc1799fe5d5ae660b66

One thing I noticed is that the rejection modal in Zeplin doesn't show the reason (the reason for crating, as provided by the customer). @amanda5iu Can you confirm whether or not the customer reason should show up in the modal?

Here are a couple more differences between this PR and Zeplin:

In Zeplin, the customer reason is not shown for the uncrating service item, but here we are showing it for all crating items.
When rejecting a crating service item, in Zeplin, there is a blank line between the Reason and the Rejection reason, but in this PR, there isn't a blank line.

@monfresh thanks! I added space between the rejection reason and reason, and I've re-asked the two other questions in Slack.


Reactnative: Label support for all the Input elements.

Description
Handled label property for all the Input elements. As per the schema label can be either string, TextBlock, RichTextBlock, and will be inside the input root-level object.
Sample Payload
{         "type": "Input.Number",         "id": "Phone",         "label": {           "type": "TextBlock",           "spacing": "none",           "color" : "warning",           "text": "Phone",           "wrap": true         } },
Microsoft Reviewers: Open in CodeFlow

@vivekvijayakrishnan there are changes to the Label and Input Validation related properties in our upcoming 1.3 schema as part of our July refresh.. The label property published in our docs today is an inadvertent publish. Are you referring to the former or the latter for reference again? @dclaux / @almedina-ms who are shepherding the 1.3 labels + validation changes .. Thanks!

Hi @shalinijoshi19, Thanks for the information. We have added the label property support in input elements as it was not handled in the current react-native renderer. We have gone through the label and validation changes for Input elements on these docs (InputValidation and InputLabel) and will be supporting this in the upcoming release. Please let us know if we have some other docs/links to get more details on these changes. Also, please note that this PR is just to kick start the implementation of these changes and will release only after completing all the changes.


more themes?

whould be great to configure custom background colors like warnings or danger.

This is coming now for sure.
Plus in version 3 u can make your own themes too.


[D3D8]Top Spin 2004: career mode graphics corruptions

Top Spin 2004, default configuration, 1024x768, 1920x1080, 1680x1050 all @ 60 Hz. XP SP2 compatibility mode on, run as admin. Both original and with official game patch.

GPU: nVidia GeForce RTX 3070 8 Gb (but also with a GeForce GTX 750Ti and a GeForce RTX 2080Ti)
Driver: 560.70
DXVK version: 2.4
Windows 10 and 11 latest versions

Apitrace file: https://mega.nz/file/1jZHnb6Z#fUkahYqxAwjGRH74I2sVoBtM2nOCvREDe54kcMan_1s

As you can see there is an issue rendering some poligons: totally missing or with crazy vertex positions only in Career mode, if you try a normal exibition everything renders fine.
I've tried the old D8VK 1.0 with the conf option d3d8.managedBufferPlacement = True and it solves the problem, BUT the game exits after 2-3 minutes of gameplay without a specific error: Windows Event Manager says generically that either Topspin.exe or msvcrt.dll (in C:\Windows\System32) crashed.
Is this a possible regression from D8VK? Where can I find an equivalent conf option for DXVK 2.4 for d3d8.managedBufferPlacement = True?
Thanks in advance for your help,
Nicola

@tomnic79 Hi there. Can you check what happens if you try with d3d9.allowDirectBufferMapping = False

Hi @Blisto91, just tried now: no corruptions during player personalization, but hangs and exits to desktop as soon as I try to save the player, d3d8.dll causing the issue according to windows event manager.

Nah, this app case consistently leak memory right from the start or better to say leak comes from a index buffer, from a second CPU thread...
You probably dont need even to play a game.

Just launch it to this and practically do nothing there - just wait and instead watch how sys mem consistently grows up step by step to about 2GiB limit, then OOM happens of course. It goes out in about 1 minute for me.
Basically it leaks buffers - that is a main bug. You can ignore possible corruptions/glitches that happen afterwards.

as of course there will be weird things since it is leaking.

Not releasing objects doesn't generally cause graphical artifacting, so I'm not sure what you mean here. The two issues are most likely unrelated.

There were many buffer leaks with other apps on a earlier d8vk, but this case seems survived.

Previous leaks were caused by incorrect refcounting, but that doesn't seem to be the case here - or at least not the obvious ones, since refcounts for all d3d8 objects are identical between a dxvk trace and a WineD3D trace. I'll look closer into what's causing the leaks, but since the problem is rather obscure it will probably take a while.
P.S.: As a fun aside, the game outright crashes when attempting to use d3d8to9, with either dxvk or WineD3D.

For me it works with WINED3D, works with d3d8to9 to WINED3D, works with d3d8to9 DXVK's d3d9 on top of that, works with NINE too, etc... no leak nor such corruptions with any of these combinations.

Seems works with whatever, sans not for long on DXVK's d3d8... who knows why, maybe because - it is not nVidia :dancers:

Yes with AMD gpus everything's fine, the problem is with NVIDIA GPUS even in native Windows without any sort of "workaround", that's why I'm trying to use some wrapping to try to solve this issue.

that's why I'm trying to use some wrapping to try to solve this issue on my nVidia based PCs

We'll probably end up applying d3d9.allowDirectBufferMapping = False to address the first issue. As to the memory leak, that might prove a bit more challenging to pinpoint. I don't see any obvious wrongdoings with buffers or anything else.

Yes with AMD gpus everything's fine, the graphics corruptions problem is with nVIDIA GPUS even in native Windows without any sort of "workaround", that's why I'm trying to use some dll wrapping to try to solve this issue on my nVidia based PCs without exchanging GPUs. The freezing problem, generated by the buffer leak, happens only when wrapping with D8VK and DXVK.

Maybe try this build d3d8.zip of d3d8to9 1.9.2 (particular version where game AA is actually working) and also it is helding up index buffer. Since index is leaking, that is my quickest guess.

Yes with AMD gpus everything's fine, the graphics corruptions problem is with nVIDIA GPUS even in native Windows without any sort of "workaround", that's why I'm trying to use some dll wrapping to try to solve this issue on my nVidia based PCs without exchanging GPUs. The freezing problem, generated by the buffer leak, happens only when wrapping with D8VK and DXVK.

Maybe try this build d3d8.zip of d3d8to9 1.9.2 (particular version where game AA is actually working) and also it is helding up index buffer. Since index is leaking, that is my quickest guess. Probably wont work, as you said up there this.

've tried the old D8VK 1.0 with the conf option d3d8.managedBufferPlacement = True and it solves the problem, BUT the game exits after 2-3 minutes of gameplay without a specific error:

But it dont hurt to try... or maybe try to limit app to 1 CPU core. That also might not help, because VK is threaded by design... but again it dont hurt to try. Just to know what triggers it and if anything changes.

With your d3d8.dll version it crashes as soon as I try to create a new player, and if I try to set the affinity to CPU0 only it crashes :(

I dont think that build makes it crash, but probably these leftover temporary files from before crashes.
Think like this about this app if it crashes ONCE it will crash AGAIN... because if it crashes once, then there are leftovers that could make  further crashes. If game happens to crashed once, then remove entire Media\GamePart\Players folder, before running  a game again.

No it crashes the same, even exibition doesn't work anymore with the specific dll provided, nor folder Media\GamePart\Players gets recreated, unless deleting this d3d8.dll

Players folder get recreated, only at the moment right about moment your first screen that you posted.

Just to be clear that I've cleaned all the folders you've said with the d3d8.dll you suggested: https://mega.nz/file/Zv5zUQRY#bVIYjY4jAg-ANOWD_tjMdpYU9DS4RiNzMOwMrrHN9J8
You can also see that when I'm trying to start to play it hangs just before recreating the player.ini file you've just said.
The only way I can play this game at the moment with nVidia cards is with the latest dgVoodoo2 forcing DX12 render pathway (or the software based one, albeit a bit slow @ FHD). Just an issue with the intro videos that are not stretched to fill the screen (other issues if I select "stretch" in directx settings so I can live without intro videos ;) ), with D8VK videos were ok, so I'd have preferred that way.
Anyway, I'll use dgVoodoo2 or the other PCs with AMD cards, thanks for all the efforts till today!!!

Just to be clear that I've cleaned all the folders you've said with the d3d8.dll you suggested: https://mega.nz/file/Zv5zUQRY#bVIYjY4jAg-ANOWD_tjMdpYU9DS4RiNzMOwMrrHN9J8
That looks like breaking on native nvidia d3d9 driver.
And what about that same d3d8.dll, but put there also just DXVK's d3d9.dll too? That is immediately different path as it goes to VK driver

It doesn't crash but players are mostly black, no vertex corruptions nor missing polygons though!

Cool, try helding vertex too... well try all 4 combinations and see if any could make nvidia driver happy there
d3d9_buffers.zip
Again, just do not forget that app requires clean exit, so that it could behave normal next time  So, no crashes, kills, ALT+F4, etc... otherwise consider it to be broken and that require some clean up :dancers:

Only with the d3d8.dll file found in default subfolder in your zip alone the game doesn't crash but players remain mostly black. Otherwise it crashes before creating a new player, just like with the first d3d8.dll you sent me.

In my case work with all dxvk 2.4 files and i dont see any chacrecter rendering issue (amd renoir igpu)

In my case work with all dxvk 2.4 files and i dont see any character rendering issue (amd renoir igpu)

Yes with AMD GPUs no issues at all, we need to solve this problem for nVidia owners

In my case work with all dxvk 2.4 files and i dont see any character rendering issue (amd renoir igpu)

Yes with AMD GPUs no issues at all, we need to solve this problem for nVidia owners

only for give more feedback (amd renoir in this case) and i use new wow64 mode
(./configure --enable-archs=i386,x86_64)

Only with the d3d8.dll file found in the default subfolder of your zip alone the game doesn't crash but players remain mostly black. Otherwise it crashes before creating a new player, just like with the first d3d8.dll you sent me.

That alone could be just some formats issue too. Try running app in a window too, driver might pick some else formats there, depending if app is window or if fulscreen is normal or borderless or exclusive or whatever.
There is no option where user could specify 16 or 32bit, so that could go somewhat random of what driver decide.

I've captured a trace of the demo with WineD3D, however it crashes my Nvidia GPU (Xid 13) on playback with dxvk.
NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 0: 3D HEIGHT CT Violation. Coordinates: (0x2, 0x208)
NVRM: Xid (PCI:0000:01:00): 13, pid='<unknown>', name=<unknown>, Graphics Exception on GPC 3: WIDTH CT Violation. Coordinates: (0x280, 0xd)

Playing it back with WineD3D shows some warning messages, but works fine.
Not entirely sure if this is a problem with apitrace or the game, but I've asked @Blisto91 to try replaying it with Vulkan validation layer enabled, see if that yields anything interesting.

Noticed that dgVoodoo2 (ver 81_3) in d3d12_fl11_0 mode crashes in msvcr71 by running on newest vkd3d-proton, but runs on some earler versions of vkd3d-proton from last year.
Thats cool, so lets bisect this, might yield what is this about here too...


Distribute to Amazon App Store

Describe the solution you'd like
Amazon has an App Store which is the primary store for Kindle Fire devices.  It would be great if we could have support for distributing releases to this app store just like we can for Google Play store.
https://developer.amazon.com/apps-and-games

Thanks for the feature request! I have a proposal for this for some upcoming stores updates. I will keep an eye out on this issue to gage further interests.

I am also looking for this capability.  Any suggestions for a semi automated solution in the interim?


Handle receive-after-close from disBatch

From flatironinstitute/disBatch#18, it appears that the kvs will sometimes be queried after it is closed depending on the timing of the SIGTERM signal.  That's fine; disBatch accounts for broken sockets at this stage by catching socket.error.  But receive-after-close currently triggers an AttributeError on None since the socket is None at this point.  This PR changes that behavior to a socket.error instead, so upstream handlers can meaningfully differentiate this scenario from other sources of AttributeError.
This is just one way to fix the issue; let me know what you think!

Just wanted to report back that I've been running with this PR for several months now, and it seems to have fixed the original issue.

Thanks!

Looks simple and straight-forward to me. Might have to poke Nick to update the disbatch submodule. It looks like there have been other possibly related fixes here since then, too.


cannot resolve class 'ChunkedConverter' from 'HexEncoder'

pub global activate den causes
Precompiling executables...
Failed to precompile den:den:
'package:convert/src/hex/encoder.dart': malformed type: line 20 pos 13: cannot resolve class 'ChunkedConverter' from 'HexEncoder'
    extends ChunkedConverter<List<int>, String, List<int>, String> {
            ^

Dart VM version: 1.24.0-edge.6a575117630f40859b4fc034696e9a14486501d6 (Wed May  3 01:40:41 2017) on "linux_x64"

den doesn't seem to use ChunkedConverter or HexEncoder, at least not directly.
pub cache repair didn't fix it either.

The ChunkedEncoder class has been removed (it was deprecated in 1.17, after being added in 1.16), but it means that you need to depend on package:convert version 2.0 for Dart v 1.24, since convert v1.1.1 uses ChunkedEncoder.
This is complicating versioning because the removal of the deprecated ChunkedEncoder class was technically a breaking change, so to be consistent with semantic versioning, it shouldn't have been able to happen until 2.0, but we are reserving that number for a larger change.
Could we release a patch (or less significant) version of package:convert that changes its SDK requirement to <1.24? (@munificent, @nex3)

we are reserving that number for a larger change

sounds like you are mixing "old-style" versioning with semantic versioning.
Seems like a path into a lot of troubles to me.

Could we release a patch (or less significant) version of package:convert that changes its SDK requirement to <1.24?

You could, but it may not fix the problem. Users of Dart SDK 1.24 or greater would see pub simply skip past that version (correctly, because it doesn't support their SDK) and land them back on the version that claims to work with 1.24 but doesn't actually.
There may not be a very easy solution. 😞 Semantic versioning is a game that only really works when everyone agrees to play by the rules. When you publish a package, its dependencies often permit versions that don't exist yet. They do that based on the assumption that the dependent package won't include breaking changes in those versions. If that turns out to not be true, there isn't a mechanism in place to retroactively narrow the dependency ranges in those previously-published packages.
One option is to publish convert 1.1.2 with a constraint that still allows SDK 1.24. But the package itself is emptied out and replaced with a message saying, "You need to switch to the 2.0.0 version." When users pub upgrade, pub will pick that version and then the users will see their app has a bunch of errors. They have to then manually change their dependency on convert and upgrade to the 2.x line.
Kind of an unpleasant user experience, but it forcibly gets them off the busted 1.x line.

We aren't going to take any actions, so closing.
(Again: sorry about the inconveniences).


Create Sharing Projects System

📝 Changed routes:

/[slug]

(view full size)

And 1 other route:

/api/share

Commit 4dbeec5ef57b5ebaf721d75b0f37f8dced246d65 (https://workshops-hc14aoueu.hackclub.dev).


first expiration  and then Forced to cover BUG!!!!

call price 210.xxx  ＞ margin call orders（expiration  ）
still at  call price 210.xxx  not  110% call price
big bug

The question here actually is, if an expired short is supposed to be margin called ..

another


Export power saving data in CSV and KML output

In the later stages of the pilot, we added power savings data capture in OneBusAway for whether the user had "power savings mode" activated, and a few other related fields.
We should export that data to CSV and KML output with the other data.

Here are the additional fields that we want to export that are currently stored in Firebase under the device-information collection for each document:

isIgnoringBatteryOptimizations
isTalkBackEnabled
isPowerSaveModeEnabled

Per today's meeting, we'll output this data in two  ways:

As an additional field(s) in the current trip CSV output file
As records in a new device-information CSV file

Possible logic:

Retrieve all device information records from Firebase for a given user
Export all records to the new CSV file
As you loop through transition records, do a binary search (or optimize further) to get the device info that was most recently recorded prior to that transition timestamp and output that as new columns in the existing trip CSV output file.

We want to avoid repeatedly querying Firebase for the device information for the same user multiple times.

@welozano PR #14 adds CSV export, but we still need to export this data to KML, so I'm re-opening this. You can modify this method to add the data to the popup balloon when you click on the origin or destination placemark:
https://github.com/CUTR-at-USF/travel-behavior-analysis/blob/master/src/main/java/edu/usf/cutr/tba/io/KmlFileWriter.java#L286


Support two-phase borrows, and other rustup

travis failed. The error is weird though, maybe the span is broken?


http: make connect-udp upgrade case-insensitive

Commit Message:
Per RFC 9110, the Upgrade value comparison should be case-insensitive. The existing implementation used case-sensitive comparison for CONNECT-UDP, so I fixed the bug. Also, I made the upgrade_type config check use case-insensitive comparison for both CONNECT and CONNECT-UDP.
Additional Description:
See  RFC 9110 (https://www.rfc-editor.org/rfc/rfc9110#section-7.8) for the Upgrade value comparison semantics, and https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/network/http_connection_manager/v3/http_connection_manager.proto#envoy-v3-api-field-extensions-filters-network-http-connection-manager-v3-httpconnectionmanager-upgradeconfig-upgrade-type for the correct upgrade_type config check semantics.
Risk Level: Low, this is a bug fix.
Testing: Added a unit test to enforce the correct comparison.
Docs Changes: N/A (Existing documentation is correct)
Release Notes: N/A
Platform Specific Features: N/A

/assign @RyanTheOptimist
Hi Ryan, since you reviewed my connect-udp PR before, can you review this bug fix PR when you are available? Thank you.

@RyanTheOptimist Can you enable the merge again? Thank you.


Codes for Lesson1

This contains all the codes for exercises and activities for Lesson1.

I have committed the codes for Lesson1.


cannot set -basic-auth and other config in config file

Setting -basic-auth, -username and other config in config file of -config-file specified in cli option is not effect.

Fixed in #687


How to use it with libgdx project?

Hi, could you guide me on how to use this with libgdx-based project?
As libgdx project might have several sub-module targeting different platform: desktop, android, ios-moe, etc. Should I put those build.gradle setting under desktop one?
The following is what I've tried.

Put build.gradle setting at the top level.

Configured with mainClassName = "io.wasin.asteroids.desktop.DesktopLauncher".
I got the following error after executing ./gradlew teavmc
haxpors-mbp:asteroids haxpor$ ./gradlew teavmc
Configuration on demand is an incubating feature.
Using already downloaded SDK: /Users/haxpor/.moe/moe-sdk-1.3.6
Changed strategy of configuration ':ios-moe:moeMavenSDK' after it has been resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0
Incremental java compilation is an incubating feature.
:compileJava UP-TO-DATE
:processResources UP-TO-DATE
:classes UP-TO-DATE
:jar
:startScripts
:distTar
:distZip
:assemble
:compileTestJava UP-TO-DATE
:processTestResources UP-TO-DATE
:testClasses UP-TO-DATE
:test UP-TO-DATE
:check UP-TO-DATE
:build
:teavmc FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':teavmc'.
> Can't provide name for method as it was not found: io.wasin.asteroids.desktop.DesktopLauncher.main([Ljava/lang/String;)V

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 12.413 secs

Put setting inside desktop.

With same mainClassName.
I got the following error after executing ./gradlew desktop:teavmc.
haxpors-mbp:asteroids haxpor$ ./gradlew desktop:teavmc
Configuration on demand is an incubating feature.
Using already downloaded SDK: /Users/haxpor/.moe/moe-sdk-1.3.6
Changed strategy of configuration ':ios-moe:moeMavenSDK' after it has been resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 3.0

FAILURE: Build failed with an exception.

* Where:
Build file '/Volumes/Slave/Data/Projects/asteroids/desktop/build.gradle' line: 9

* What went wrong:
A problem occurred evaluating project ':desktop'.
> Cannot add task ':desktop:run' as a task with that name already exists.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 1.849 secs

Any suggestion on how to solve this?

This Gradle plugin is unofficial, TeaVM does not provide Gradle support yet. I'm an author of TeaVM, but I'm not an author of this plugin, so I can't help you. You can ask me personally (info@teavm.org), or publish your question on forum.
Let my try to help with your problem. First, have you tried teavm-libgdx? It's outdated and no more maintained, but you can try to build it and learn it. It's in Maven, but it should not be a problem. I guess it's not that hard to invoke Maven from Gradle, right?

Execution failed for task ':teavmc'.
> Can't provide name for method as it was not found:
io.wasin.asteroids.desktop.DesktopLauncher.main([Ljava/lang/String;)V

Obviously, this means that there's no such class in your project ;-)

This plugin was incorrectly setting the classpath, that's why it was not finding the main class (it can't see it).
I fixed that in this PR: https://github.com/edibleday/teavm-gradle-plugin/pull/5
Hope that the maintainer @n3o59hf will respond (if you don't want to work on this project anymore, let me know and I can take over - I have quite some experience maintaining Gradle plugins, so I can do it for you).

@renatoathaydes I think you can publish it under your own maven group ID?

@renatoathaydes I suggest to redirect everyone to your fork, and make it the maintained version.
Thus I would approve @sriharshachilakapati's suggestion to publish it under your own maven group id.

@renatoathaydes do you mind enabling people to open issues on your fork?

@vic-cw done. I will try to find time to do this.

@renatoathaydes Awesome!!


Release/v0.5.0

Release🎉🎉🎉🎉🎉🎉🎉
Fixes
Frontend WORKS!!!!!!! omg

Change Summary

Additional Notes

Testing Procedure

Related PRs or Issues

Merging this


two functions to get the thickness from top/bot

There are two functions to calculate the thickness from the top and bots: nlmod.mdims.calculate_thickness and get_thickness_from_topbot. They don't do exactly the same thing but should be merged into one function anyway.

One is already deprecated


Test completion enhancements

[ ] any os

tests #6874

FYI - to test against the latest API do the following:

open your extensions package.json file
change the engine.vscode property to *
run npm run postinstall (assuming you have the vscode module as dev-dependency)
undo the engine-version change from step 2


actionlib: 1.11.13-0 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository actionlib to 1.11.13-0:

upstream repository: https://github.com/ros/actionlib.git
release repository: https://github.com/ros-gbp/actionlib-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.6.2
previous version for package: 1.11.12-0

actionlib
* [bugfix] added missing boost/thread/reverse_lock.hpp include (#95 <https://github.com/ros/actionlib/issues/95>)
* Contributors: Robert Haschke

Holding for synchronized release...


In server.js publicPath not working but contentBase does it

Dear,
not sure if it's my mistake or not, but I could not make it work using publicPath; replacing it by contentBase on line 6 of server.js did it for me
Kind regards,
gd

Not sure what the issue was, but I’m glad you resolved it.
Other people don’t seem to have this problem so I’m closing.


process.env.PWD is not set on Windows

follow up for #760. See https://stackoverflow.com/questions/44355912/hoodie-postinstall-failed-process-env-pwd-is-undefined ping @janl

started a PR at https://github.com/hoodiehq/hoodie/pull/765/files which replaces process.env.PWD with process.cwd() which seems to work, I tested it with an example app using npm install hoodiehq/hoodie#763/windows-postinstall-setup-fix (using<EMAIL_ADDRESS>


Support customizing data and time into ISO format

I see that data and time format customization is on the road map. Just want to provide some input regarding this.
It would be great to support ISO 8601 format YYYY-MM[-DDTHH:mm:ss.nnn+ZZ]. An example of this would be 2021-04-18T04:19:35.000. This format is also used by another powerful plugin Dataview:
Data Annotation - Dataview
Therefore, supporting this would provide better integration among plugins.

Added feature to change date time format.
https://github.com/uphy/obsidian-reminder/tree/1.0.5#date-format

Without using the above command, you can change format with settings

That's great news!
I ran a quick test by using the command. However, it did not change the format of existing tasks from @2021-08-31 12:00 to @2021-08-31T12:00. It did change the format in the configuration pane. Is this the desired behaviour?
Another observation is that defining the reminder in the format of @2021-08-31T12:00 did not give me a reminder for the specified task. Does one need to specify the full format like 2021-08-31T12:00:00:000? It would be great if things at the end can be optional, meaning that @2021-08-31T12:00, 2021-08-31T12:00:00 and 2021-08-31T12:00:00:000 would all work.

Oh, it worked for me...

Can you try Scan reminders?

In the latest release, there is a bug not to re-scan on setting update. (it will also be fixed in the next release)

There is no response on my side:

Also, if the date and time format is set as YYYY-MM-DDTHH:mm:ss:SSS, the following setting would not give me a reminder:
- [ ] Task (@2021-09-03T12:00) #ToDoTask #CategoryResearch 📅 2021-09-30
This is also mentioned in my previous comment.

The command Convert reminder time format converts from current format to the selected format.
So you need to set the following setting to YYYY-MM-DD HH:mm before you execute convert command.

This is also mentioned in my previous comment.

Sorry but it is expected behavior.
This plugin uses 2 formats for date time.

date and time
date only

You cannot use different format for date and time format currently.
Why you need multiple representation for time?

So you need to set the following setting to YYYY-MM-DD HH:mm before you execute convert command.

Thanks for the clarification! It works now.
After converting the date and time format, I notice that the modification time of all Markdown notes in my vault has been updated to the time when the conversion command was executed, even for notes that do not have date/time info of any format. Can this be prevented?

Maybe the modification time should only be updated for notes that contain data/time of the format that matches either of the three options, i.e. the Reminder plugin format, Tasks plugin format and the Kanban plugin format.
For notes that have the time info, e.g. 2021-09-05, but not (@2021-09-05), 📅 2021-09-05 or @{2021-09-05}, maybe the date and time info should not be updated, i.e. the modification time of the note should not change?

Why you need multiple representation for time?

I was thinking that the time format of YYYY-MM-DDTHH:mm:ss:SSS is the full format for reminder time the user specifies in the configuration pane. However, sometimes the user may use a shorthand format, e.g. 2021-09-05T12:00, to define a reminder in the notes.

Therefore, it might be helpful the latter format would also give a reminder, although the user set the former format in the configuration.
This is also why I suggested in another issue that maybe two data and time formats can be defined, one for identifying tasks and the other for completing tasks.

Of course, this is not a must-have feature, since might complicate this plugin. 😅

The proposed function will be treated as a separate issue.  This issue will be closed once.


Mass Options

Can we have a selector kind of thing and mass options such as delete selected, download selected

I'd love this!

This feature is included in #82, which should be released soon.


Adds a box width parameter that can be passed to grid detect

Goes some way to #231 but should try again on the beamline
To test

Confirm tests pass

I think given it will be a while before we can test this we review/merge with the idea of checking if we think it will fix the issue and retest next run

Changes look good, but from @rtuck99's comment on #231, I'm not 100% sure if this will work
From my understanding, after doing FGS, Hyperion sets the aperture size based off the bounding box size returned from Zocalo. The bounding box size is in units of box size, but where do we tell Zocalo about the box size?
Also, we should define box size and bbox size somewhere, I got confused about it just now

I agree with this but the bounding box code is also in flux with https://github.com/DiamondLightSource/mx-bluesky/pull/553 at the moment. To avoid merge conflicts on that (already big) PR I have made https://github.com/DiamondLightSource/mx-bluesky/issues/618


High-level spec for Full Node and Snapshots

High Level
Some draft on the snapshots and full node high level specs. Joining them here since they do share some important similarities, and it might help to keep that in mind. They both work on sliding window intervals during syncing, and any table that can be pruned is a candidate for a snapshot file in the end.
Categories (prunable or moveable to snapshots)

Historical: AccountChangeSet / StorageChangeSet / AccountHistory / StorageHistory
Transactions: Transactions / TxSenders / TxLookup / TxHashNumber / TransactionBlock
Receipts

Full Node:

Default pruning. keep data related to the most 256 recent blocks.
Any table which has a BlockNumber or TxNumber as key is a candidate for pruning.
Customization on what are the most recent blocks [ allow keeping none of the block data, apart from state after verifying ]
Each category can be fully pruned (eg. no receipts) if desired so.
Prune levels should allow skipping certain stages (eg. TxSenders / TxLookup )

Snapshots:

Fixed interval. [ Every N blocks, or every N transactions ]
Any table which has a BlockNumber or TxNumber as key is a candidate for moving to static files.
Reproducible snapshots. Should include an option to sync from beginning and let the node create all its own snapshots. They should match existing ones.
Shared through a centralized host and/or p2p
Static file per category or per table
Perfect hashing table for keys
Compressed values (overall dictionary (across 0 - 17M blocks) / per file / or both [double compression])

Syncing

Full node:

Requests block height from CL.
Sync with pruned options. [eg. don't store/calculate changesets until the most recent blocks or receipt or TxSenders etc.].
When approaching a block number close to block_height - 256, recheck latest block height.
Once it reaches the desired height, register process to wake-up register  (more on it below) and sleep.

Snapshots:

??

Tip
Register

Wake-up register [condition -> wake-up registered process (channel) -> execute]

Loop through registered processes
If condition is met, wake-up registered process
Execute. [full-node: clean-up tables | snapshot: move from tables]
Either on success or failure, update the condition with a new one.

Once a block has been handled check wake-up register conditions. [eg. static file waits for an exact block height while full node might execute every N blocks]

Priority

Full node syncing
Wake-up register
Full-node @ tip wake-up process (registration & table clean-up)
Snapshot  @ tip wake-up process (registration & moving table data )
Snapshot syncing

We need to specify in here how this would even work given the current architecture, i.e.:

What assumptions do we make in the stages, tree, and RPC about data availability? (e.g. unwinds assume changesets are available for exec/merkle)
Since we only have one write transaction, how will we periodically delete data from the tables (both for pruning and snapshots) while syncing?
How do we adjust our current database abstraction to work with static files? I assume the static files generated by "snapshots" can also be used by the node as a secondary store for historical data to keep the MDBX database small? This was not mentioned in here, but it should be accounted for

@shekhirin will take this

Data Availability assumptions:

In case of a reorg, we need to have account and storage changesets available up to the reorged block to unwind the execution, hashing and merkle stages. It applies to both pipeline and blockchain tree unwinds. We should be able to find an optimal and safe value for max reorg depth, e.g. 2 epochs = 64 blocks.
CL needs logs (and hence, receipts) available from the block where DepositContract was deployed (or the first deposit was made). It's possible for the CL to operate without these logs if it syncs from the checkpoint. Or, we could leave only deposit transaction receipts which are required for the CL's eth_getLogs to succeed.
Pruning headers and bodies by default is most likely a bad idea, because it affects the network health by being unable to fulfil devp2p peer requests GetBlockHeaders and GetBlockBodies. But having it as a configurable option might be a good idea.

Pruning while syncing (either via pipeline on initial sync and filling a large block range, or via blockchain tree following the CL):

It'd be nice to not require the user to first fully sync the node, and only then allow to prune it.
Also, we want the node to continue syncing and being responsive to RPC requests (with minimally degraded performance) either from CL or the user.
We only have one write transaction, so we need to either:

Switch between syncing new blocks and pruning:

For the pipeline sync, it can work by both:

Splitting the block range into chunks, and pruning between executions
Not persisting any changesets until the desired pruning height

For the blockchain tree, we can prune after processing every new FCU. Since blocks arrive every ~12s, we have some time to prune all the required tables to not get left behind the CL.

Introduce a mechanism similar to this https://medium.com/nethermind-eth/netherminds-full-pruning-is-here-cutting-the-gordian-knot-5e3450f02de9 to regenerate the state trie into a new database, while using the old one for reads.

Interface:

We have a Stage trait with Execute and Unwind methods, which all the stages implement.
Let's extend it with the Prune method. Unlike for the execution and unwinding, we can use the pipeline for pruning during the blockchain tree sync.

Not persisting any changesets until the desired pruning height

I'd recommend avoiding this if we want to support forward syncing in the future, since we can only really do this because backwards sync gives us some sort of guarantee that all historical blocks should be executable with no issues. But if we forward sync, that might not be the case - we may encounter invalid blocks, and in that case we would need to unwind, which relies on changesets. So it would have to be a sliding window, i.e. always save e.g. the last 256 blocks of changesets in execution, and remove any older ones every time we commit.
If we don't want to think about this now, we should at least note it down in the implementation so we remember later

This is a good point.

So it would have to be a sliding window, i.e. always save e.g. the last 256 blocks of changesets in execution, and remove any older ones every time we commit.

It should work, yeah.

Brain dump on what can be pruned and the side effects of it:

Changesets and History can be pruned, it will affect the eth_getStorageAt, eth_getBalanceAt and tracing RPC methods
Transaction Senders can be pruned, it will affect the execution performance
Transaction can be pruned, it will affect the network health
Receipts can be pruned, it will affect the validator ability to startup without a checkpoint + eth_getLogs, eth_getFilterLogs, etc. RPC methods
Transaction Lookup Index can be pruned, it will affect the eth_getTransactionByHash, eth_getTransactionReceipt, debug_getRawTransaction RPC methods as it's used to get the transaction by hash
Plain State can't be pruned
Hashed State and Tries can't be pruned because recalculation takes a lot of time and we need it for the chain to progress

Very nice. @joshieDo @shekhirin:

WDYT about making the transactions table even smaller? How much do we gain if we use a minimal perfect hash function to 'compress' the keys when we put the transactions on a static file?

Avalanche also implemented a bespoke Snap sync mechanism which gossips state diffs (instead of raw state) which avoids the "healing" process of Geth's Snap sync, maybe something to learn here: https://github.com/ava-labs/avalanchego/tree/master/x/sync.

Please ref https://github.com/paradigmxyz/reth/issues/2753 as well for additional ideas


GT not loaded for ai_city data in MOTChallenge format

Hi,
Thank you for your great work with the HOTA metrics.
I've a related issue but this is not about the difference between 9 and 10 values per line (even though I tried to remove one to see if it helps, but it does not).
I tried your script with a GT file from the AICity challenge 2021 and compared it with a pred file they provide, both following the MOT format (attached to this message), but for some unknown reason, the script does not read the GT file, same as if it was empty:
Count: DeepSORT-SSD512-pedestrian  Dets      GT_Dets   IDs       GT_IDs
s01-c003                           14151     0         219       0
COMBINED                           14151     0         219       0

I tried to change some value, indexed by obj_id instead of frame_id, remove one '-1' at the end of each line, checked the encoding and also checked the entire hierarchy of 'trackers' and 'gt' folders.
Finally, I copied a GT file from a MOT sequence (MOT16-train\MOT16-02) and pasted it as it was my own GT file, even if it doesn't match at all... and it reads the GT file correctly:
Count: DeepSORT-SSD512-pedestrian  Dets      GT_Dets   IDs       GT_IDs
s01-c003                           14151     17833     219       54
COMBINED                           14151     17833     219       54

Here's the original GT file of the sequence I want to test:
gt.txt
Here's one of the prediction file:
s01-c003.txt
Thank you in advance for your help.
Originally posted by @JonathanSamelson in https://github.com/JonathonLuiten/TrackEval/issues/23#issuecomment-814948323

Indeed, it's working good now! Thank you!


Your code currently operates one image at a time, is it possible to adjust the batch_size operation? I look forward to hearing from you!

Your code currently operates one image at a time, is it possible to adjust the batch_size operation? I look forward to hearing from you!

Hi @tanlingp ,
In theory, we can of course generate adversarial images in batches. However, since this method currently requires backpropagation through multiple diffusion steps, many intermediate calculation graphs are stored, so even if only a single image is processed, the memory usage is approximately 16GB. Thus with only my current equipment (a single Rtx3090), I'm afraid I am not able to test turning the code into batches.
However, if you have multiple GPUs or more memory, the most straightforward way I recommend is to use multiprocessing to process batches of images. It's easy and doesn't require modifying the core code.
Hope this helps.

Hi @WindVChen,
This article proposes the Segment-wise Forwarding-Backwarding algorithm to address the memory issue in computational graphs, aiming to improve the efficiency of DiffAttack.

Hi @yujinhan98,
Thank you for sharing the article. I appreciate your insight in addressing the memory issue with Segment-wise Forwarding-Backwarding. However, it seems that this approach might prolong the optimization time, which might still fail to speed up the generation of the adversarial examples.
While I haven't delved into all the intricacies of the article, Segment-wise Forwarding-Backwarding seems akin to the commonly used gradient checkpointing trick. This method involves recalculating computational graphs during the backpropagation phase, leading to increased processing time, contingent on the number of checkpoints set.
@tanlingp's intention, I think, is to expedite the generation of adversarial examples by leveraging batch processing. Given the longer processing time per input associated with Segment-wise Forwarding-Backwarding (despite its reduced memory usage), it may not significantly enhance the speed, which is the primary concern here.
Nonetheless, I appreciate your contribution. Many thanks for sharing your insights.
Best regards.


Cannot build

I have tried to build the package with VS2015 and VS2017.
In both cases many errors.
What I am doing wrong?

It compiles using VS2017 if you could attach logs it would help to investigate.

Ok, there is the log
microdot_log.txt

It looks to me that you missing dependencies to take them you should run .paket/restore.bat  we have a guide of how to compile the library, please take a look, https://github.com/gigya/microdot/wiki/Contribution-Guide.

Yes,
========== Build: 17 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
I thought that Restore NuGet packages is enough.
Thank you, it was my mistake.

It an easy mistake to make, we use a paket client tools for nuggets management, that are not integrated into VS by default.

Btw, are there any examples how to use the framework?
What is the best practice?


Add tests to pr 43

/help

@archieai complete-review

/help

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json

docs/models/basics.mdx
docs/quickstart.mdx
docs/scoring/basics.mdx
examples/basic/empiricalrc.json


Google OAuth Error 400: Invalid request

Hello,
authorization URL printed in the terminal leads to an error 400: invalid request, which is shown by a Google OAuth login site:
The out-of-band (OOB) flow has been blocked in order to keep users secure. Follow the Out-of-Band (OOB) flow migration guide linked in the developer docs below to migrate your app to an alternative method.
Request details: redirect_uri=urn:ietf:wg:oauth:2.0:oob

As far as I can read here and here, authentication method used by drivesync is deprecated now.

Same problem here!

Yes, I am also having same issue.

Another confirmation with a recently downloaded drivesync

Any updates? Is there another method?

FWIW I was able to get this to work by editing drive_manager.rb and changing this line:
OOB_URI = 'urn:ietf:wg:oauth:2.0:oob'
to this:
OOB_URI = 'http://localhost'
Then you can run the process for the first time (I am using a derived docker image, so my commands I think are not actually relevant to this particular package) it will generate a google link with a redirect_uri of localhost.  So you open that, auth it, it will redirect to localhost (which I assume is nothing, so your browser should just stop there) and then you can copy out the code param from the URL and paste it in to complete the auth process.

no longer works
"This app is blocked"


Remaining features

Fix capture formatting
Correctly indent with and for special forms
Underscores in large decimals
fun-parens rule
Partially implemented zero-arity-parens rule - only local function calls are covered in this PR.

Perhaps a matter of personal preference, but I'd rather only having one feature per PR.
In my experience small PRs are easier to review and refine, so you're more likely to get good feedback, and less likely to get stuck going back and forth in the review.

Perhaps a matter of personal preference, but I'd rather only having one feature per PR.

In my experience small PRs are easier to review and refine, so you're more likely to get good feedback, and less likely to get stuck going back and forth in the review.

(Other opinions are available) :P

Absolutely agree. Please break up in one PR per feature.

Yes, my bad. Regarding the PR granularity, will do that in the future.

@uohzxela please do break up this PR as well if you can, so reviewing becomes easier and less error-prone for us.

@whatyouhide I'd love to break up this PR. However, it's intermingled with other bug fixes. I'll try to rollback on the zero-arity parens feature in this PR and open a separate PR for it since it is quite poorly implemented.

@lpil Thanks for all your help! 😄
@whatyouhide I'd like to merge this PR in before I start on the fun-parens rule so as to avoid merge conflicts. Let me know if there's anything to be improved.


Presentation 2 submission

Presentation submission for week 11

Can we get some links in the README.md?


Coverage sucks

I don't know why, but I added tests, and coverage went down.
I think it's a bug of llvm profile.

Coverage is now updated on CodeCov https://github.com/swc-project/swc/issues/917
@kdy1 Can you share the components of the project need improved unit test coverage in order of importance here, and add "good first issue" label?
That way, fans of swc who are new to rust may help add tests.

Order by importance:

swc_ecma_parser => lexer
swc_ecma_parser => parser (accepting correct input)
swc_ecma_codegen
swc_ecma_parser => parser (correctness of span)
swc_ecma_transforms => typescript
swc_ecma_transforms => compat
swc_ecma_transforms => proposal
swc_ecma_parser => parser (error recovery)


Resources in inconsistent state

This is from testing alpha.hydroshare.org version 1.2.1
If an error occurs during resource creation the system can end up in an inconsistent state such as illustrated.

I am unable to delete this resource, despite being its owner.
Also resources in this complete state do not show up in the filtering "owned by me", despite showing up in the listing of all resources with me as the owner.

HydroShare Resource Creation Workflows Issues in GitHub: #37, #62, #81

Presumed to be resolved by new resource creation workflow.


appendStartDate not working any more

Is it an actual bug?
Yes
Did you check if the bug has already been reported?
Yes
Describe the bug
Recently the creation data is not saved in new entries any more. In my user-preferences.json I see that "appendStartDate": true is still set.
To Reproduce
Steps to reproduce the behavior:

Set appendStartDate to true
Create new entry
Check if todo.txt contains the creation date.

Do you see any error entries in sleeks developer tools?
Should not be relevant.
Desktop (please complete the following information):

OS: Fedora
Version of sleek: 1.2.8
Source: Flathub

@dlaidig thanks for reporting this. Could you please check, if this feature does work again in https://github.com/ransome1/sleek/releases/tag/v1.2.9-rc.1

I was already about to write that it does not seem to have changed at all. Then I noticed it actually now works when creating issues via the dialog but not when using the "add as todo" button in the search bar (which I end up doing most of the time).

@dlaidig mmhh that's odd, let me look into it again.

Oh, and it totally does seem to break setting priorities in the dialog, either by typing "(A)" manually or by using the controls. The date is put before the priority, and then the priority is interpreted as text. After some iterations of trying to change the priority, I ended up with 2022-11-01 (A) 2022-11-01 (A) 2022-11-01 (A) test issue

I think I have to admit, that fixing this will be an ugly workaround. The root cause for this issue lies is the library, that parses the string into todo.txt objects. There is rewrite of this particular library going on at the moment and as soon as the it has been released, this issue will be fixed. As for now I won't continue working on fixing it, but the solution for this is near.

Glad to see that you are still working on sleek, @ransome1. I'm looking forward to test v2.0 when it is a bit further along.  :)
I think this issue is still very much relevant and should be kept open.

Available in https://github.com/ransome1/sleek/releases/tag/v2.0.0-dev9


Impact of Byte Queue Limit on AVTP

Hi,
I have been reading the IEEE1722 document and have also been experimenting with this implementation of AVTP.
I had also been going through the TC components of the Linux kernel and came across Byte Queue Limit(BQL)(Section 4.10).
I stumbled upon the following thought after reading about BQL:

Would BQL impact the performance of AVTP?

BQL aims to improve the utilisation of the queue by appropriately queuing certain amount of data. AVTP, built on top of TSN(which requires ultra low latency), requires that the latency be bounded and be as low as possible. With BQL, the queuing delay can significantly be reduced as it tries to maintain the queues at the most optimal size, in an attempt to increase the utilisation of the link.

I request all of you to share your thoughts regarding the same.
Thank you in advance!

@vcgomes ^

Yes, in theory, BQL will add a bit of overhead to the transmission path, but from my mental model, the impact should be minor when the transmissions are well behaved, i.e. less or equal to the configured rates (when using CBS, for example).
In the case of less well behaved transmissions you should see increased latency because the packets are being held for longer periods of time, because the transmission queue will be "busy" for longer.
Anyway, it might be worth to disable CONFIG_BQL in your kernel config and do some experiments.


Allow mPCC to serve up Ansible Playbooks/Roles

Rename the "scripts" section to "config management" and add Ansible Playbooks/roles in a similar way to scripts work

Ansible playbooks could actually run from a "script" within the script runner.  This would mean no modification to the jobserver, and would make it modular to add the function to an existing setup.


I forgot that the website and readme needed to be the same

Could you try to resolve the merge conflicts?

I resolved the conflict, I think

The two pages are actually slightly different, and I do want to keep some of the old content that this PR is removing.


Remove golang.org/x/net replace directive

In #16 we bumped golang.org/x/net with a replace directive.
We should remember to remove this to avoid accidentally pinning the version back.

Plan to remove the replace directive in #28 as part of the otel dependency bump.

The replace was removed in 0bf0af78.


Baklava identifies itself as Unknown in React

Describe the bug
Baklava not work in React 16. It identifies itself as "Unknown" component.
Possible: React Lazy Exports
To Reproduce

Upgrade baklava version to 2.0.0-beta.59 from 2.0.0-beta.48

Screenshots

Desktop (please complete the following information):

OS: Mac
Browser [e.g. chrome, safari]: Firefox
Version [e.g. 22]: 59

@muratcorlu With the release of lazily loading baklava components (https://github.com/Trendyol/baklava/pull/320), we were expecting baklava not to work in React 16 and some versions of 17 since they handle React Lazy differently.  We don't have any issues with the 18 though.

I'm trying to debug this. I created a demo with React 16 and TS and apparently managed to run Baklava (beta75) in it without any issues. @Enes5519 can you check this: https://codesandbox.io/s/baklava-in-react-16-ts-ninfd0?file=/src/index.tsx
I feel there is a problem about either TS version or tsconfig.

Can you check if #449 fixes the issue here?


Feature/typescript definition file

summary of changes

added typescript definition file
updated deregisterDependency to take a dependency or string - to make it consistent with getDependency, isDependencyRegistered etc.
updated README
added node types dev dependency

Coverage increased (+0.4%) to 96.789% when pulling a20181f851e5127760ab53322003f05d55a27040 on feature/typescript-definition-file into 04f9c5eccc8353b887299d947b11d6e9e4eb72f8 on develop.


LXD removes LVM block devices on container stop

Required information

Distribution: Ubuntu
Distribution version: 20.04
The output of "lxc info" or if that fails:

Kernel version: 5.4.0-33-generic
LXC version: 4.0.2
LXD version: 4.1
Storage backend in use: dir | lvm

Issue description
I created a container using an LVM storage pool. I need to increase the size of the container. I can stop the container and resize it with lvresize however LXD is removing the block device so I can't run resize2fs. lvchange -a y / does not bring back the block device.
I have libvirt configured to use the same storage pool and block devices are always available whether the virtual machine is on or off.
Steps to reproduce

Create an LVM storage pool
Launch a container which uses the LVM storage pool
Stop the container
Block device is no longer available.

Yes, that's a deliberate change in LXD, we just don't want to keep block devices around as we have systems with thousands of them which then causes all kind of interesting side effects.
As you want to resize your container, just override its size and LXD will do the resizing for you.
lxc config device override NAME root size=50GB or if your container already has its own root device, then use lxc config device set NAME root size 50GB.
If you really must play with the block device directly, running lvchange --activate y --ignoreactivationskip NAME should do it.


feat: support "affinity" and "topologySpreadConstraints" configurations

Description of the change
This PR supports configuring Pod Affinity and Pod TopologySpreadConstraints.
Existing or Associated Issue(s)
None
Additional Information
None
Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[ ] Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
[ ] JSON Schema generated.
[x] List tests pass for Chart using the Chart Testing tool and the ct lint command.

@DimkaGorhover  We're skipping 3 patch verisons? Although this PR seems like a feature which would be a minor version bump

@DimkaGorhover We're skipping 3 patch verisons? Although this PR seems like a feature which would be a minor version bump

Hi, @ChrisJBurns. Thank you for your comment. I bumped the minor version. Pls, take a look
- version: 0.21.3
+ version: 0.22.0

@DimkaGorhover any updates on this?