TypeError: obj is undefined when node is pre-selected

Hi,
I want to display the path of the selected node when the page loads and update the display when the user selects a different node.
I found this code to display the path in a div:
.on('changed.jstree', function (e, data) {
  var path = data.instance.get_path(data.node, '\\');
  $('#event_result').html(path);
});

This works fine except when I have selected a node programmatically - then I get this error:
TypeError: obj is undefined
obj = obj.parents ? obj : this.get_node(obj);

on line 984 - in the first line of the get_path() method.
I am using jsTree version 3.3.2 (the latest I could download).
By "programmatically" I mean that I set the 'selected' attribute in the code I have for populating the jsTree.
Here is the JSON used to populate my test page:
[{"id":1,"parent":"#","text":"Root","state":{"opened":true,"disabled":false,"selected":true}},{"id":123
,"parent":"1","text":"folderA","state":{"opened":false,"disabled":false,"selected":false}},{"id":500
,"parent":"123","text":"Sub Folder A1","state":{"opened":false,"disabled":false,"selected":false}},{"id"
:501,"parent":"123","text":"Sub Folder A2","state":{"opened":false,"disabled":false,"selected":false
}},{"id":124,"parent":"1","text":"folderB","state":{"opened":false,"disabled":false,"selected":false
}}]

Any help would be greatly appreciated.
The script I used to build and populate the tree is here:
        /*
         * Populate a jsTree with JSON data.
         * If the JSON response is empty then empty the tree.
         */
        function buildTree(jsonData) {
            if (jsonData != null
                && typeof jsonData !== 'undefined'
                && jsonData.length > 0) {

                // build the tree
                $('#spanTree').jstree({
                    'core': {
                        'data': jsonData
                    }
                }).on('changed.jstree', function (e, data) {
                    var path = data.instance.get_path(data.node, '\\');
                    $('#event_result').html(path);
                });

            } else {
                $('#spanTree').empty();
            }
        }

Thank You!

Next time please provice a fiddle like this one:
http://jsfiddle.net/DGAF4/1550/
You will see that I replaced data.node with data.selected[0] - you can not depend on data.node being present all the time - initially there is no concrete node that triggered the event.

Ivan,
Thank you so much for your reply.
This does correct the issue I had – of course.
I did create a simple test project to isolate my jsTree test code from the rest of my web app, but I apologize for not providing a jsFiddle.
            BTW – great work on this library!

MCory
From: Ivan Bozhanov<EMAIL_ADDRESS>Sent: Thursday, September 08, 2016 7:30 AM
To: vakata/jstree<EMAIL_ADDRESS>Cc: Michael Cory<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [vakata/jstree] TypeError: obj is undefined when node is pre-selected (#1564)
Next time please provice a fiddle like this one:
http://jsfiddle.net/DGAF4/1550/
You will see that I replaced data.node with data.selected[0] - you can not depend on data.node being present all the time - initially there is no concrete node that triggered the event.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/vakata/jstree/issues/1564#issuecomment-245569533, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVCb-aizFLpfx7OuA3KPhV5ojIgkwZYUks5qn_GzgaJpZM4J3PSN.


Confusing Data-Field name on Web-Page

Hello Huggingface team,
In Dataset GEM/xlsum Data-field : summary is confusing!!! link
While loading data Target is used as a label instead of summary.
Summary on link is confusing and misguiding.
Hope you find this useful and try to update it asap.
Thanks :)
Concern : could you just add the help/bug module on the Huggingface website with a helping mail-id that can help people to contact you easily to solve this kind of issue!!!

Hello,
we are not the huggingface team. We only provide the support for the adapters-transformers library which is based on huggingface transformers. Hence, this issue probably belongs in the huggingface/transformers repository.


what happens if you increase the classifiation count required for retirement on a live project?

I wanted to ask before broaching the P4 science team. I'm not doing any weighting yet, but I think we might want more than 20 classifications per subject. If I bring the project back to development and increase the classification count  to 30 and the make the site back to live will that un-retire subjects that are already retired that had 20 classifications?
Thanks.

As it's currently written raising the limit will not unretire subjects.

So I'd had to use the api to unretire subjects after that step?
It seems like should be a way to do this with the project builder  because there may be times once you've got a much larger sample classified that you find you need more classifications. Should open a separate ticket for that discussion on the front end side?

PS - thanks @edpaget for the info

+1 - This has come up a few times in projects I'm working on.  We try to
overshoot in beta testing to come up with sensible limits, but needs can
change, especially if aggregation algorithms change.
On Monday, August 24, 2015, Meg Schwamb<EMAIL_ADDRESS>wrote:

So I'd had to use the api to unretire subjects after that step?
It seems like should be a way to do this with the project builder because
there may be times once you've got a much larger sample classified that you
find you need more classifications. Should open a separate ticket for that
discussion on the front end side?
—
Reply to this email directly or view it on GitHub
https://github.com/zooniverse/Panoptes/issues/1301#issuecomment-134119421
.

--
Sent from my moderately intelligent phone.

Does anyone actually depend on the current behaviour, or could we just always retrofit the retirement limit?

We could allow changes to the retirement limit to unretire subjects.

agreed, no one depends on the way it currently works. I think we'd have to add some copy / warnings to the front end page stating something about "may result in subjects being un-retired / retired."

That would be great if it's possible to do.

This hasn't been done, but we've made solution much more complicated now that Caesar is in the mix. I don't think we'll get to this anytime soon.


Problems on Windows: sh: docker_compose: not found

Steps for bug replicate:
dsh up

all works good, containers started successfully.
dsh bash

returns error:
sh: docker_compose: not found
Error response from daemon: no such id: bash
Connection to <IP_ADDRESS> closed.

Workaround is:
vagrant ssh -c 'docker exec -it <container_id> bash'

@fat763 I have a fix available now. Can you please test it before I push a release?
In Babun run the following:
B2D_BRANCH=develop dsh install prerequisites
DRUDE_BRANCH=develop dsh self-update

Then try dsh bash again

Thank you, @lmakarov!

This should now be fixed in the develop branch (DRUDE_BRANCH=develop dsh self-update)


Use slog consistently across the project

The logging for registry-stable is consistently using slog. No remaining log usages


Reverse Proxy (Cloudflare Tunnel)

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description

👟 Reproduction steps
Follow the instruction
👀 Expected behavior
SSL Certificate from Cloudflare break it?
😓 Actual Behavior
i see only a whitescreen but if I type status.pryers.net he automatic goes to status.pryers.net/dashboard this is right but i see only this and the website title is correct too.

🐻 Uptime-Kuma Version
1.2.10
💻 Operating System and Arch
Debian (Buster) 86x
🌐 Browser
Chrome
🐋 Docker Version
20.10.09
🟩 NodeJS Version
No response
📝 Relevant log output
No response

i use the Cloudflare tunnel


Dependency on image 0.22 needs updating to 0.23

barcoders depends on image 0.22 (when the image feature is enabled).  Unfortunately 0.22 has a security vulnerability (https://rustsec.org/advisories/RUSTSEC-2020-0073), and fails a cargo audit (meaning so does barcoders.)
The vulnerability is fixed in image 0.23.

@buntine Sorry for pinging, I do understand it's a very rude thing to do, but is there a chance for you to merge this pull request?
I am building a GTK app with your great library and I would like to avoid delivering potential security issue.
Thanks!

see https://github.com/buntine/barcoders/pull/22#issuecomment-2028449494

@timwalls Fixed in #31
This is now safe to close


feat(rust): initial ockam worker API

A replacement PR for #843

I refactored all the changes into two commits because this makes the change much more coherent and atomic. Let me know if there's anything that needs changing in your opinion.

@spacekookie the changes here look good, thank you 🙏
I'll merge this afternoon.
The build failure in unrelated.

Build being fixed here: https://github.com/ockam-network/ockam/pull/861

Merged in https://github.com/ockam-network/ockam/pull/861


Error when querying SHOW CREATE TABLE on system table

Received exception from server (version 21.8.7):
Code: 107. DB::Exception: Received from xxx.xxx.xxx.xxx:pppp. DB::Exception: Cannot open file /xx/xx/xxxx/clickhouse-server/server/store/dca/dcab689e-2871-4b9b-9e46-5b8af5864572/events.sql, errno: 2, strerror: No such file or directory SQLSTATE: 58030.

Code: 107. DB::Exception: Received from xxx.xxx.xxx.xxx:pppp. DB::Exception: Cannot open file /xx/xx/xxxx/clickhouse-server/server/store/dca/dcab689e-2871-4b9b-9e46-5b8af5864572/events.sql, errno: 2, strerror: No such file or directory SQLSTATE: 58030.

it seems like I do not get this error on my local development and docker deployment. @xiaomo728 Can you try this again on the latest version of the master branch?

Can not reproduce it. Please reopen it if you reproduce in the new version.


WFSSL-15: Enabling one-way ssl using elytron with key length < 2048 returns non user friendly error message

The main problem was that the method tcn_Throw just didn't include the real openssl message (so the %s was not filled with the real issue). I have used the standard vsnprintf with a 4096 buffer.
The other problem was that only the first openssl was retrieved instead the full stack. I decided to include the ERR_print_errors openssl method to dump all the stack into a buffer.
Because the messages can be longer now all the buffers have been increased from 256 to 2048.
Besides I have removed the include of the opensslv.h because the version checking should be done at runtime (never at compilation time). This was a mistake and complicates the compilation in windows.
If you prefer to allocate the buffers just let me know but I thought it was easier to respect original idea. The same if you prefer a different size.

The version checking change that was included in this PR probably could have been in a separate PR with its own WFSSL issue since it doesn't appear to be related to WFSSL-15. However, overall, I think this PR looks ok.


Fixes to package.json

Fixes the stuff I mentioned in https://github.com/LeaVerou/awesomplete/commit/4ab426917750a3c9f6bb0a67971e31af11e8769f.

Thanks!


Dependencies are not working

I have a problem with dependencies of this library. I see this error during angular app start.
ERROR in ./node_modules/ngx-international-phone-number/index.js
Module not found: Error: Can't resolve 'google-libphonenumber' in '/Users/jakob/volterra/volterra-ui-components/node_modules/ngx-international-phone-number'

In npm registry page there are no rendered dependencies, I think maybe release was broken or something like this. https://www.npmjs.com/package/ngx-international-phone-number
It can be fixed using explicit install of google-libphonenumber library.

I have the exact same issue.

npm install google-libphonenumber should fix this.

I have the exact same issue.

npm install google-libphonenumber should fix this.

Thanks , its worked for me

npm install google-libphonenumber should fix this.

Thank you its run


Add Ubuntu 24.04 support

Closes #302

This can be rerun on Saturday after we have a ubuntu 24.04 nightly to test with


Crash with accessibility next/prev events and min/max date

Library version 4.0.1.
Steps to reproduce:

Enable TalkBack (or some other accessibility helper with next/previous navigation)
Open up a DatePickerDialog with a minimum date set e.g. to current date
Select first day of current month
Swipe left to move to previous focusable item

Expected:
Invalid dates (before minimum date) should not be focused?
No crash, focus moves e.g. to controls above the month selection view.
Actual:
Invalid dates can be focused with accessibility navigation.
Crash trying to move to previous month that is before minimum date.
java.lang.IllegalArgumentException: Invalid target position
	at androidx.recyclerview.widget.RecyclerView$SmoothScroller.start(RecyclerView.java:11534)
	at androidx.recyclerview.widget.RecyclerView$LayoutManager.startSmoothScroll(RecyclerView.java:8204)
	at androidx.recyclerview.widget.LinearLayoutManager.smoothScrollToPosition$6cefd9a5(LinearLayoutManager.java:451)
	at androidx.recyclerview.widget.RecyclerView.smoothScrollToPosition(RecyclerView.java:1781)
	at com.wdullaer.materialdatetimepicker.date.DayPickerView.goTo$4001730e(DayPickerView.java:228)
	at com.wdullaer.materialdatetimepicker.date.DayPickerView.performAccessibilityAction(DayPickerView.java:422)
	at android.view.AccessibilityInteractionController.performAccessibilityActionUiThread(AccessibilityInteractionController.java:711)

Assuming this crashes the same way with maximum date set respectively; did not try to repro that myself.
This looks a lot like #512 reported earlier.

I don't do a lot of testing with the accessibility features.
While it looks similar to #512 it's probably not the same issue.
I'll take a closer look at this.

I did some experimentation with this and submitted a PR that fixes the issue at least for our case. Not too familiar with the codebase so might have overlooked something but hope it's helpful anyway.

Fixed in v4.1.0


SwipeRefresh bug

Description of error
After clicking the "back" button on the device's navigation bar to go to the previous page of the site and then refresh the page that opens, the page that was opened before clicking "back"opens.
Expected behavior
The current page must be updated.
Devices

Device Name/Option: All devices
Build: All
Android version: 7.1 or higher

Are you sure the back action performed by the webpage is not some asynchronous script? If not, then there surely is some issue else, it's just recording the last dynamic page address.


Xml contentType and equalToXml body

I found that equalToXml converts to wire-mock equalToXml only if there is no specific xml header is placed otherwise converts to xpath matchers.
Example contract
request {
		method 'GET'
		url "/users"
		headers {
			header "Content-Type", "customtype/xml"
		}
		body equalToXml(
                 """<foo><name>Artem</name><jobId>1234567890</jobId</foo>"""
                 )
		response {
			status OK()
		}
	}

Actual generated stub:
...
"bodyPatterns": [
      {
        "matchesXPath": {
          "expression": "/foo/name/text()",
          "equalTo": "Artem"
        }
      },
      {
        "matchesXPath": {
          "expression": "/foo/jobId/text()",
          "equalTo": "1234567890"
        }
      }
    ]
...

Expected generated stub:
...
"bodyPatterns": [
    {
         "equalToXml":"<foo><name>Artem</name><jobId>1234567890</jobId></foo>"
    }
]
...

If remove header Content-Type with xml then everything is ok and equalToXml at the stub as the test should use equalToXml says
I guess the test should use xml matchers when content type ends with xml intersects with should use equalToXml
Or please tell me if I am wrong with equalToXml and XML content type logic

Thanks  for reporting this @hustleone Will have a look at this and get back to you.

Yes. It's a bug. Will wait for your PR then.

There is the same issue with JSON body and json contentType, see PR


chore: bump eui@72

Bump elastic@eui to latest version with some UI adjustment for the changed parts due to the update.
TODO:

[ ]  mute console.error that mentioned in https://github.com/elastic/eui/pull/5920

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2023-01-09T15:39:52.574+0000

Duration: 8 min 59 sec

Steps errors
Expand to view the steps failures

run tests

Took 2 min 31 sec . View more details here
Description: .ci/scripts/run-test-in-docker.sh

:robot: GitHub comments
Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test all : Re-trigger the build for all the stages.


Update command examples to have trailing semicolons

Since version 1.0.9 trailing semicolons are required on commands, whereas before they were optional.
This PR updates all of the examples in the help file to include the semicolon.

The changes in this PR are superseded by PR #17


UI of Villa hotel website

@TusharKesarwani As a part of SSOC'23, I would like to improve the UI of Villa hotel website. Kindly assign this issue to me.

@TusharKesarwani Sir please assign this project as I'm proficient in developing good UI for websites and I am sure to built the best UI for this project.

Sir please assign me this project as i'd like to contribute, Regards

Empower me with the opportunity to take on this project and make a significant impact!

Create a new issue with proper description


Add ability to set tile background colour

It would be great if we could have the facility to specify a colour for a tile, something like this.
{
  "tiles":[
    {
      "screen":<number>,
      "tile":<number>,
      "backgroundColorRgb":{
        "r": <number>,
        "g": <number>,
        "b": <number>
      }
    }
  ]
}

Given the naming convention here, it would make sense to change 'Set icon color' to:
{
  "tiles":[
    {
      "screen":<number>,
      "tile":<number>,
      "iconColorRgb":{
        "r": <number>,
        "g": <number>,
        "b": <number>
      }
    }
  ]
}

this just makes the payloads a little more self explanatory.

The colored tle background would only be visible in OFF state because the ON state is defined as white. Is it that what you want to achieve? If not, please describe what you are looking for.

Yes I think that's ok.


Update console sdk

this commit bump sdk version to 0.0.2
uses new sdk package for webpack and internal apis

/hold cancel

/lgtm


FCFB-35 Pass Completions possibly incorrect

Looking at passing plays in scrimmage between Dekam and loco_pabs the pass completions stat may be off
Filtering on play call of pass with home team in possession, there were 49 such plays and 10 of them are incomplete. So there are at most 39 completions. Add in the couple of turnovers that takes it down to 37 completions. The stat site had 46.
Summary: stat site/json had 46 completions on 49 pass plays for the home team, I count 37 pulling each play.
Not super important currently but probably something to be aware of.

Similar to FCFB-38, I think I fixed this in the backend. Leaving open just in case

Marking as complete, let me know if it pops up again


Support library version configs in app.yaml

The GAE app.yaml documentation says you can configure library versions (https://developers.google.com/appengine/docs/python/config/appconfig), section is titled "Configuring Libraries".
This issue is to add support for that feature.

There is support for versions currently.


Doesn't work with opam-monorepo

As the install runes only lie in the opam file, it's not possible to use this package with opam-monorepo. Would be nice to wrap this into a dune stanza instead.

I pushed a dune file that replicates the behavior of the opam file. Let me know if that works for you 🙂


need to change ranking system

Currently, if three users have the same points, they all share the same rank, for example, rank 4. After these three users, the next rank should be 5, not 7.

my approach to solve this

Schema Modification: Add a rank field to the User model in the database schema.
Automatic Rank Calculation Function: Develop a function that recalculates ranks for all users based on their current points, This function will be triggered whenever a user's points are modified.
Integration with Point Update System: Modify the existing point update logic to call the rank calculation function after any point changes.
Leaderboard API Adjustment: Update the leaderboard API to utilize the new 'rank' field from the database.

In the last in Club Gamma Fronted, we loaded the user rank data from the User model.

go ahead!

/assign

/assign

already assigned to you


ASAP support for storage perf tests

ADO job link for successful execution: https://microsoft.visualstudio.com/LSG/_build/results?buildId=69187275&view=logs&j=9d69b070-e195-5a64-5b70-a85129a61ae5

@SRIKKANTH don't provide internal links in Github.


Add UI to configure interactive window for Environment:

I was trying to set my project's interactive window to use IPython interactive mode, and eventually found out that it was possible if I create a folder under Documents/Visual Studio 15/Python Scripts/<projectName>.  (I first configured my global Anaconda via the UI, then copy-pasted its folder)
While that works fine, it would be nice if that was exposed via the UI.

There's an item for this in the Python Environments window.


Telemtry: post at least once a day

This ensures that people who keep the app running in the background
for days at a time are still counted as active users.

LGTM


Make comparisons of process names case insensitive on windows. On win…

…dows,
foo.exe is the same as Foo.exe is the same as FOO.EXE
What does this PR do?
Makes the check for process name case-insensitive.
Motivation
While working on an unrelated issue, discovered that the process check missed a process that I expected a match.  The process had mixed capitalization, but was specified in the config as lower case.  On windows, those two things are equivalent.

Closing to create a clean PR after rebase


change(db): Optimize RocksDB lookups and inserts

Motivation
This might be faster than binary search lookups:

https://github.com/ZcashFoundation/zebra/actions/runs/2100898949

This is not significantly faster (only 2 minutes less, which could be natural variation).


feat(content): use angular router for internal links

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/analogjs/analog/blob/main/CONTRIBUTING.md#-commit-message-guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Which package are you modifying?

[ ] vite-angular-plugin
[ ] astro-angular
[ ] create-analog
[ ] router
[ ] platform
[x] content

What is the current behavior?

The app will be hard refreshed when the user clicks on the internal link defined in the markdown file.
What is the new behavior?
The app won't be hard refreshed when the user clicks on the internal link defined in the markdown file.
The behavior remains the same for external links, internal links with target="_blank, and links with download attribute.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Thanks Marko!


Train Models Within Kalosm

You should be able to train some models based off of a workflow in Floneum using either burn or candle.
This can be useful to "flatten" a workflow into a model. For example, you could have a workflow that does classification on reddit posts. Initially you build that workflow to use llama2 to recognize certain posts. After you get the workflow working, you can hook up a classifier to learn the task the language model is doing. After running it overnight, you should be able to replace the language model with a much faster, smaller classifier
Initially I would like to just support classifiers because you can train them quickly without a GPU, but in the future we could add fine tuning language models, or image models.

You can now train a classifier in Kalosm. We should support fine tuning models in Kalosm first before we provide an interface in Floneum


make menu entry 'display empty folders' checkable

the user can see the state of self.info.display_empty.
It doesn't actually show the state of self.info.display_empty, so if you want to do checks in toggleDisplayEmpty, you should set toggleEmptyAction.setChecked yourself afterwards

Coverage decreased (-0.15%) when pulling ddec001dd846308e275732dd967bc3a2571b078e on egolus:CheckableMenuEntry into c2f45e1d4571cc7ecfe13edcb40c71be959ef1ac on baudren:devel.

Sorry for forgetting the tests again.
The value of display_empty is saved with QtCore.QSettings and all functions that use display_empty read it from QtCore.QSettings first

Coverage decreased (-0.93%) to 86.04% when pulling 32bbec42ffc59bde13ea7b1e2ebb306f4461b502 on egolus:CheckableMenuEntry into c2f45e1d4571cc7ecfe13edcb40c71be959ef1ac on baudren:devel.


Spam Video ID Submission

Duplicate Links

[X] Yes, I checked that the ID is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=gk3t-2GRD5Y&lc=UgyVvVS3-OgQdRixX_h4AaABAg.9ujVV6X0J_W9ujVghIW4xb
(Optional) Screenshot of comments using the link

(Required) List of the spam video IDs / Links
5qr5xvd_8tu

Duplicate of #452, will be added this next update


Hotfix: Take hardcoded lockup storage amount into account

@evgenykuzyakov may you take a look if I caught all edge cases?


Improve the  server instrumentation

At the moment smithy-rs server does not have great instrumentation coverage.
We should identify key points in the request/response lifecycle to emit events/open spans.
Care MUST be taken to ensure that we do not log anything that could be sensitive.

Something to keep in mind, from https://github.com/awslabs/smithy-rs/pull/2524#issuecomment-1491955247

We should also think about having a mechanism to test that the framework is error logging what we expect it to; error logs are very important.

Doing so seems terribly complicated / janky. On one hand the easiest I've found is leveraging tracing_test; on the other hand, we run integration tests for this binary by spawning a child process via Command::cargo_bin("pokemon-service"), so collecting stdout/stderr might suffice.

This would be an easy thing to test if we had a plugin to generate application binaries using generated SDKs.


[5.5] Runtime/IRGen: Fix async dynamic replacements

Runtime: For async function async function pointers will be stored in dynamic
replacement records.

IRGen: We need to emit a full async suspend sequence when calling the
replacement.

rdar://77072669
rdar://77072724
Cherry-pick of #37038 and #37039

@swift-ci Please test


vyperdatum not compatible with newest vdatum software?

Hello! My name is Josh Alland and I am at the National Hurricane Center. I have been trying to get vyperdatum working on my local laptop. I downloaded the recent version of vdatum first (v4.4.2), but vyperdatum is giving the following error: "OSError: Unable to find version for /Users/jalland/Downloads/vdatum/ in the currently accepted versions: ['vdatum_4.4.1_20220324', 'vdatum_4.3_20210928', 'vdatum_4.2_20210603', 'vdatum_4.1.2_20201203']"
Is there support to have vyperdatum work with the updated version of vdatum? Thank you!

Hi Josh, thanks for letting us know.  I'll need to add support when I get
back to the office.  It honestly might be a few weeks, but I can respond
here to let you know.
On Tue, Aug 16, 2022 at 3:03 PM jalland @.***> wrote:

Hello! My name is Josh Alland and I am at the National Hurricane Center. I
have been trying to get vyperdatum working on my local laptop. I downloaded
the recent version of vdatum first (v4.4.2), but vyperdatum is giving the
following error: "OSError: Unable to find version for
/Users/jalland/Downloads/vdatum/ in the currently accepted versions:
['vdatum_4.4.1_20220324', 'vdatum_4.3_20210928', 'vdatum_4.2_20210603',
'vdatum_4.1.2_20201203']"
Is there support to have vyperdatum work with the updated version of
vdatum? Thank you!
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-ocs-hydrography/vyperdatum/issues/34, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA2JUDVU3LFV4N2ZZBYKC3VZPQXNANCNFSM56W46BYA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: (302) 751-0538
Cell:<PHONE_NUMBER>

Thanks Eric! Tingzhe Si sended me an older version of vdatum that works. However, I am still not able to get vyperdatum to work property. I'm getting an error when trying to run the example code: "Pipeline "+proj=pipeline +step +proj=vgridshift grids=core\xgeoid20b\conuspac.gtx +step +inv +proj=vgridshift grids=VAswchb11_8301\tss.gtx +step +proj=vgridshift grids=VAswchb11_8301\mllw.gtx" for transformation from "[[]]" to "[+proj=pipeline +step +proj=vgridshift grids=core\xgeoid20b\conuspac.gtx +step +inv +proj=vgridshift grids=VAswchb11_8301\tss.gtx +step +proj=vgridshift grids=VAswchb11_8301\mllw.gtx]" in region "VAswchb11_8301" was flagged as invalid.  Missing support files?" and "No valid region found with the specified datum transformation. Unable to perform transformation"
Any idea why this may be?

Believe it means it can't find the grid files.  Can you look in VDatum to
see if all the grids called out in the pipeline string exist?
On Wed, Aug 17, 2022 at 2:12 PM jalland @.***> wrote:

Thanks Eric! Tingzhe Si sended me an older version of vdatum that works.
However, I am still not able to get vyperdatum to work property. I'm
getting an error when trying to run the example code: "Pipeline
"+proj=pipeline +step +proj=vgridshift grids=core\xgeoid20b\conuspac.gtx
+step +inv +proj=vgridshift grids=VAswchb11_8301\tss.gtx +step
+proj=vgridshift grids=VAswchb11_8301\mllw.gtx" for transformation from
"[[]]" to "[+proj=pipeline +step +proj=vgridshift
grids=core\xgeoid20b\conuspac.gtx +step +inv +proj=vgridshift
grids=VAswchb11_8301\tss.gtx +step +proj=vgridshift
grids=VAswchb11_8301\mllw.gtx]" in region "VAswchb11_8301" was flagged as
invalid. Missing support files?" and "No valid region found with the
specified datum transformation. Unable to perform transformation"
Any idea why this may be?
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-ocs-hydrography/vyperdatum/issues/34#issuecomment-1218342781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA2JUBEO7MBHWLL3SIEN5DVZUTPFANCNFSM56W46BYA
.
You are receiving this because you commented.Message ID:
@.***>

--
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: (302) 751-0538
Cell:<PHONE_NUMBER>

I am seeing all of the grids. Could the error be coming in from the
highlighted portion?
"Pipeline

"+proj=pipeline +step +proj=vgridshift grids=core\xgeoid20b\conuspac.gtx
+step +inv +proj=vgridshift grids=VAswchb11_8301\tss.gtx +step
+proj=vgridshift grids=VAswchb11_8301\mllw.gtx" for transformation from
"[[]]" to "[+proj=pipeline +step +proj=vgridshift
grids=core\xgeoid20b\conuspac.gtx +step +inv +proj=vgridshift
grids=VAswchb11_8301\tss.gtx +step +proj=vgridshift
grids=VAswchb11_8301\mllw.gtx]" in region "VAswchb11_8301" was flagged as
invalid. Missing support files?"

On Wed, Aug 17, 2022 at 3:09 PM Eric Younkin @.***>
wrote:

Believe it means it can't find the grid files. Can you look in VDatum to
see if all the grids called out in the pipeline string exist?
On Wed, Aug 17, 2022 at 2:12 PM jalland @.***> wrote:

Thanks Eric! Tingzhe Si sended me an older version of vdatum that works.
However, I am still not able to get vyperdatum to work property. I'm
getting an error when trying to run the example code: "Pipeline
"+proj=pipeline +step +proj=vgridshift grids=core\xgeoid20b\conuspac.gtx
+step +inv +proj=vgridshift grids=VAswchb11_8301\tss.gtx +step
+proj=vgridshift grids=VAswchb11_8301\mllw.gtx" for transformation from
"[[]]" to "[+proj=pipeline +step +proj=vgridshift
grids=core\xgeoid20b\conuspac.gtx +step +inv +proj=vgridshift
grids=VAswchb11_8301\tss.gtx +step +proj=vgridshift
grids=VAswchb11_8301\mllw.gtx]" in region "VAswchb11_8301" was flagged as
invalid. Missing support files?" and "No valid region found with the
specified datum transformation. Unable to perform transformation"
Any idea why this may be?
—
Reply to this email directly, view it on GitHub
<
https://github.com/noaa-ocs-hydrography/vyperdatum/issues/34#issuecomment-1218342781
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AOA2JUBEO7MBHWLL3SIEN5DVZUTPFANCNFSM56W46BYA
.
You are receiving this because you commented.Message ID:
@.***>

--
Eric Younkin
Physical Scientist
NOAA OCS, Hydrographic Systems and Technology Branch
1315 East-West Highway
N/CS11, Room 6604
Silver Spring, MD 20910
Office: (302) 751-0538
Cell:<PHONE_NUMBER>
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-ocs-hydrography/vyperdatum/issues/34#issuecomment-1218391110,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZRZ2BWI57NPAHI7XRMAMLVZU2FPANCNFSM56W46BYA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@jalland Sorry for the delay on this, can you let me know the command you used and the version of Vdatum that you are using to get this message?  I will try and replicate here.

@jalland in addition, I have added support for Vdatum 4.4.2 in vyperdatum 0.1.16 (see https://github.com/noaa-ocs-hydrography/vyperdatum/commit/a9aa34200983faafc54b1833a0bb9937c7647538)

vadtum version 4.4.1. I was following the example script: https://github.com/noaa-ocs-hydrography/vyperdatum
This line gave the error: vp.transform_points(6319, 'mllw', x, y, z=z)


feat!(eks): bump eks installer version

bump EKS installer version
bump providers versions to align them with the EKS provider
relax terraform version constraint so we can update it easily in the future

BREAKING: notice that upgrading terraform provider version requires running some commands for existing clusters.
See PR #221 for instructions.

Note
Leaving the PR as draft until we have the release of the installer.

closing in favour of #326


.MN2 to .MNX doesn't re-gen PICTRES or KEY clauses on DEFINE BAR

ℹ Computer information

VFP version:  VFP9SP2
FoxBin2PRG version: 1.9.73
Last FoxBin2PRG version w/o bug (if available): 1.9.51 (my experience...didn't have interim builds)

📝 Provide detailed reproduction steps (if any)

Generate .MNX from .MN2 files that contain PICTRES or KEY clauses on DEFINE BAR

✔ Expected result
.MNX should have these options defined.
❌ Actual result
.MNX no longer has these options defined.
📷 Config
FoxBin.zip
📷 Screenshots

Menu bars with shortcuts keys like KEY F6, "F6"; are lost.
This problem is caused by the fix I made for https://github.com/fdbozzo/foxbin2prg/issues/80
See sys_men.mn2 key F6 is lost when converted back to mnx
That fix contains a problem.  I send a new foxbin2prg.prg that fixes this problem @lscheffler  can you patch this?
sys_men.mn2.txt
foxbin2prg.prg.txt

Done, Thor is updated


Can't include firebase_database

Steps to Reproduce

Added firebase_database to my pubspec.yaml:
firebase_database: '>=0.1.0'

Updated packages:
flutter packages get

Imported firebase into my app
import 'package:firebase_database/firebase_database.dart';

Attempted to run app
flutter run

Logs
flutter run output:
Running "flutter packages get" in FlutterApp...       0.3s
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...                                0.6s
Resolving dependencies...                             1.0s
Running 'gradlew assembleDebug'...
Note: /home/chris/.pub-cache/hosted/pub.dartlang.org/firebase_database-0.1.0/android/src/main/java/io/flutter/plugins/firebase/database/FirebaseDatabasePlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:packageDebug'.
> !zip.isFile()

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

flutter analyze output:
Analyzing /home/chris/Development/Parakeet/FlutterApp...
No issues found!
Ran in 5.5s

Flutter Doctor
[✓] Flutter (on Linux, locale en_US.UTF-8, channel alpha)
    • Flutter at /home/chris/Development/Atlast/flutter
    • Framework revision b156a0f054 (3 weeks ago), 2017-08-11 22:01:40 -0700
    • Engine revision fef7d827d6
    • Tools Dart version 1.25.0-dev.9.0

[✓] Android toolchain - develop for Android devices (Android SDK 25.0.3)
    • Android SDK at /home/chris/Android/Sdk
    • Platform android-25, build-tools 25.0.3
    • Java binary at: /home/chris/Development/Atlast/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] Android Studio (version 2.3)
    • Android Studio at /home/chris/Development/Atlast/android-studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2)
    • Flutter plugin version 16.0
    • Dart plugin version 172.3968.20

[✓] Connected devices
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 5.1.1 (API 22) (emulator)

Nevermind,
flutter build clean
flutter run
It's now working.

@AnandAron the current version is 1.0.1, it's unlikely such an old version can still be used with other dependencies with more recent versions or a recent Flutter version.
If that doesn't fix your problem please create a new issue with full information (flutter doctor output, ...)
Closed issues are not monitored and comments are easily overlooked.

Sir My Issue
Launching lib/main.dart on Lenovo A6020a40 in debug mode...
Initializing gradle...                                       7.2s
Resolving dependencies...                                   11.4s
Gradle task 'assembleDebug'...
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\firebase_admob-0.6.1+1\android\src\main\java\io\flutter\plugins\firebaseadmob\AdRequestBuilderFactory.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\flutter_webview_plugin-0.2.1+2\android\src\main\java\com\flutter_webview_plugin\WebviewManager.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\flutter.pub-cache\hosted\pub.dartlang.org\flutter_webview_plugin-0.2.1+2\android\src\main\java\com\flutter_webview_plugin\WebviewManager.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Gradle task 'assembleDebug'... Done                         399.2s
Built build\app\outputs\apk\debug\app-debug.apk.
Installing build\app\outputs\apk\app.apk...                     -

Application has stopped
plz solve this

@OfficialSameer  I changed version 0.6.1+1 to 0.5.7. It's working for me


Replace instances of lld with the PRI64d macro for MSVC++ compat

I'm sure there are other things that will stop MSVC++ from compiling but it's best to use the defined macros in this instance either way.

This has been rebased over master. I'd like to confirm it doesn't somehow effect mingw compiling (@mitchellcash)  before merging and I'm still curious if it helps with MSVC++ compiling (though I expect many other errors will occur).

mingw compiling is fine :) can't comment on MSVC++

@mitchellcash someone surely will test MSVC++ eventually, either way I'm in favor of using the macro instead of lld. Just going to double check if I missed any instances of it lol.


Automatic reading of inheritance specified with allOf

How should I read inheritance specified with allOf? Will those things be automatically read or I have to read them by myself?
By example:
components:
  schemas:
    Pet:
      type: object
      required:
        - pet_type
      properties:
        pet_type:
          type: string
      discriminator:
        propertyName: pet_type
    Dog:     # "Dog" is a value for the pet_type property (the discriminator value)
      allOf: # Combines the main `Pet` schema with `Dog`-specific properties
        - $ref: '#/components/schemas/Pet'
        - type: object
          # all other properties specific to a `Dog`
          properties:
            bark:
              type: boolean
            breed:
              type: string
              enum: [Dingo, Husky, Retriever, Shepherd]

Will OpenApiSchema for Dog contain pet_type property?
For me, as a user, one solution is to write my custom extension methods for OpenApiSchema that take inheritance into consideration when iterating some properties for example.

It seems like AllOf is automatically read so I can use it straight away without using ResolveReference:
foreach (var baseSchema in schema.AllOf)
{
    // this line is not needed!
    //var referenceSchema = openApiDocument.ResolveReference(baseSchema.Reference) as OpenApiSchema;
    //referenceSchema.Extensions["x-foo"]

    // this works too!
    var fooExt = referenceSchema.Extensions["x-foo"]
}


password parsing issues with :

If a password has : , it will fail to login

This appears to already be fixed. If it occurs again, please reopen this issue.


Directories created for volumes on boot initialisation, when the corresponding container is not running, causing issues with host applications writing to the directories

I'm having an issue (well, a number of related issues) with containers and volumes. Some of these issues are mentioned elsewhere, but this particular instance is not.
I am running a container to allow execution of a legacy Wordpress Install. As this is on my development system I didn't want to have a separate mysql container, rather just use the mysql container on my host. Therefore I tried runing docker with the following:
docker run -d --name php53 -v /home/sites/example.org/www:/var/www -v /var/run/mysqld/mysqld.sock:/var/run/mysqld/mysqld.sock precise_apache_php53 /usr/sbin/apache2ctl -D FOREGROUND
The issue is with:
-v /var/run/mysqld/mysqld.sock:/var/run/mysqld/mysqld.sock
The purpose being to expose my host mysql server to the container. This worked beautifully, until my development server was rebooted after a power failure. The mysql stopped working.
It seems on reboot that because /var/run/mysqld/mysqld.sock does not exist it's being created by docker even though no container is running (it's also creating it as a directory, but that's a seperate issue: #13121 ).
So, I decided to change the param to
-v /var/run/mysqld:/var/run/mysqld
As /var/run/mysqld is persistent over reboots. However when I do this, having stopped the container before reboot, it appears that mysql still cannot create the socket file in that directory even though the permissions for the directory are correct. I have to issue a
docker rm php53
command before I reboot to stop docker from creating (or taking control of) /var/run/mysqld
This is problematic as I don't believe docker should be doing anything on my local filesystem until I run a container, and the container is not run automatically at boot.
docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64
docker info
Containers: 29
Images: 72
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 130
Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 3.16.0-38-generic
Operating System: Ubuntu 14.10
CPUs: 8
Total Memory: 15.64 GiB
Name: tattve
ID: EKU2:ETU7:MEQA:TLLN:ZJEU:IFDP:36QJ:JLXM:AE66:ZRSG:EMCC:3FZU
WARNING: No swap limit support
uname -a
Linux tattve 3.16.0-38-generic #52-Ubuntu SMP Thu May 7 10:51:21 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Environment
Physical ubuntu 14.10
How Reproducible
I've been able to reproduce the issue with a number of different images running as containers, over numerous reboots. I tracked the issue down to docker by uninstalling it and the issue went away. Upon re-install it started again (presumably because container info was kept through the uninstall)
Steps to Reproduce
On Ubuntu 14.10 or 14.04 with mysql installed from distro .deb files,default configuration

docker run --name bugtest x-v /var/run/mysqld/:/var/run/mysqld/ hello_world
mysql to access the mysql client, will connect to server (though user/password will be needed)
sudo reboot
Upon reboot mysqld will not have started due to the issues with /var/run/mysql
5 mysql will return an error could not connect via /var/run/mysqld/mysqld.sock
docker rm bugtest
reboot
Upon reboot mysqld will have started, mysql will be able to connect

Additional Info
Whilst I'm reporting this issue with mysql as example, I'm simply using that to illustrate a point. The point being that docker seems to be stopping host applications from properly accessing directories which are mapped as volumes, and creating some connection to those directories even when no container is running. I'm not familar enough with Linux Containers to know, but the problem may well be there, rather than docker itself.

Hmm, the only thing docker is doing here is bind-mounting the host dir (and creating it if it doesn't exist).
Have you checked why mysql can't write logs?

It's can't write its sock file, not it's log file, as the dir that docker creates has the wrong permissions  for mysql to write to. That's easy enough to solve in a dockerfile with a chown/chmod.
However the main issue is that docker is creating the host dir at boot, when the docker daemon is executed, even though the container is not running. This seems to me to be the wrong behaviour.

Docker does not do this.
Docker will create the dir at create time, and when it starts the container.

the version of docker i was using at the time did that, otherwise i would not have reported it. I will check with a more recent version, but i am sure it was docker. you might want to try recreating my tests, which i did on vanilla ubuntu from vagrant images, and as my notes say was reproducible.
-- excuse brevity, sent from my phone.

On 15 Sep 2015, at 21:38, Brian Goff<EMAIL_ADDRESS>wrote:
Docker does not do this.
Docker will create the dir at create time, and when it starts the container.
—
Reply to this email directly or view it on GitHub.

I confirm that docker recreates the directory even if the container is not started/running.
It always creates it as root, while my (temporary working) directory should be owned by www-data user.
It's annoying, giving me the obligation to chown/chmod at the server startup in a dirty init script launched after the docker daemon starts.

In any case, the functionality which auto-creates host paths when missing is now deprecated and will be removed in docker 1.11

:+1:

Closing, because https://github.com/docker/docker/issues/16349 was merged

Could we reopen this issue as the auto-create feature was enabled again?


Fixed Error opening data file

Error opening data file /app/.apt/user/share/tesseract-ocr-eng/tessdata/eng.traineddata

Nothing


Update agent pools

Description: Update agent pools for osm-azure pipelines to staging-pool-amd64-mariner-2

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Networking             [ ]
Metrics                [ ]
Security               [ ]
Tests                  [ ]
CI System              [X]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

Abandoning this due to Arc CLI extension validation issue with OSM v1.1 tag format. Will make this change directly to v1.2.


Animation resize will cause stuck.

Maybe we can use _.throttle to change scrollListener to a lazy function?

See comment in PR.


Fix return types in Http

This PR partially reverts https://github.com/thephpleague/uri/commit/abfc6b3937c766ab5847fd93f92a2f1be2105af2
Because the minimum PHP version is 7.2, adding return types is possible and is more explicit.
I noticed this change because we use this package in the test suite of Symfony and we have a static analysis step that fails since the referenced commit has been added.
(reverting to using self instead of static also since the class is final)

Indeed this change was promoted by phpstan results but I was not ok about them tbh that's why it is not yet released in a stable version so I could ponder if it was the correct call. And indeed a revert was going to happen before release

I'm seeing the failures now, they're definitely false-positives...
A quick merge would be appreciated, but I get these failures may slow this down a bit.
Thanks for taking care of this package :)

The revert is now on the master branch with an update in the phpstan.src.neon configuration to prevent the false positives.


FigureExtParsedownPicoPlugin & markdown IDs & definition lists

Pico version: 2.1.0-beta.1
When I use FigureExtParsedownPicoPlugin, elements' IDs in markdown don't be converted to HTML ones.
For example:
## About {#about}

doesn't look in HTML like this:

About

rather, it remains like this:

About {#about}

However, when I remove FigureExtParsedownPicoPlugin, it works properly.
Definition lists have the same problem.
Is it Pico's fault? or Parsedown's, or it is the plugin itself?

It's the Parsedown extension, it's extending from Parsedown, not from ParsedownExtra, consequently you can't use any of ParsedownExtra's features. Try replacing the line
class FigureExtParsedown extends Parsedown {

by
class FigureExtParsedown extends ParsedownExtra {

However, no guarantees, I haven't tested this, Pico 2.1 includes Parsedown 1.8, which changed some internal functions which might break existing Parsedown extensions.

Thanks! It solved the IDs' problem.
However, for definition lists, the problem persists.

Lorem ipsum dolor sit amet
: Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat volutpat.

results in

in Pico 2.1.0-beta.1 when using ParsedownExtra, so it looks like the Parsedown extension somehow prevents ParsedownExtra from properly handling the definition lists. Contact the Parsedown extension's developer.


How to use other port than 8080

I searched through the repo for any config files but couldn't find any. How can I change the startup port form 8080 to something else?
Thanks!

Oh never mind, it is stated in the readme file...


Fix ffi_plugin template so example has lower flutter bound

Flutter example generated as part of plugin generated from ffi_plugin template fails to run with older version of flutter.
So it needs to have lower-bound constraint generated in its pubspec.yaml that matches flutter that is used to generate the project.
Otherwise, user could encounter various compile-time errors when running generated example with older version of flutter.
$ flutter create --template plugin_ffi --platforms linux,windows p
...
$ cat p/example/pubspec.yaml
...
 environment:
  sdk: '>=2.18.0-283.0.dev <3.0.0'
...
$

cc @stuartmorgan

cc @dcharkes

Retitling, as this isn't specific to ffi_plugin; it's the way the application template itself works. (The example is just the app template created inside the plugin template, with a few minor changes.)

Adding some more context, the motivation for this request is that we don't guarantee project-level backwards compatibility in generated applications. I.e., if you make an app with Flutter version X, but try to compile it with Flutter version Y<X, it may not work. This is true not just for Flutter APIs, but the tooling itself.
In particular, there is often tight coupling between generated native build files and the tooling that interacts with them; when we make changes we do migrations to provide backward compatibility with older projects, but the reverse case (new projects with older versions) don't necessarily work. (This happened frequently when desktop was in early stages, for instance, but can happen at any time.)
One complication is the migrators: when a project is auto-migrated by a new version of Flutter, that can cause it to be incompatible with older versions of Flutter, so there's an argument that if we decide to do this, we should also have migrators (optionally) update the min Flutter version.

But isn't the problem with lack of flutter lower bound only a problem for example from ffi_plugin template?
Is there any other template-generated code that requires it?

I'm trying to narrow down description of the error to what I actually experienced.
The build error I saw was specifically on Windows in sample ffi_plugin example code.
D:\a\grpc_cronet\grpc_cronet\example\windows\runner\Runner.rc(76): error RC2127: version WORDs separated by commas expected

Yeah, probably is not ffi-related, but Windows desktop specific instead.

I'm trying to narrow down description of the error to what I actually experienced.

I could provide the exact PR that triggered your case and the scenarios that it happens in; I just haven't because the details are not actually interesting here and I didn't want that to potentially derail discussion.
Our current behavior is that when you flutter create an application (regardless of the template that is or contains that application) you get a project that may or may not build with any given older version of Flutter, and the known-working version is not actually encoded in the project (other than .metadata).
Your proposal is that we instead enforce that application have a minimum version of the version of Flutter they were generated with, so that instead of maybe working fine or maybe getting a random error on one or more platforms at random if someone tries to build with an older version, it will deterministically fail with a clear error message, which would prevent cases like the one you saw.
(Another option is that we could not encode the version, and on any build failure, check .metadata and if it's a hash that's not in the current branch's history, throw a generic "Hey, did you know you're trying to use an older version of Flutter and that's not supported?" error message.)

Yeah, probably is not ffi-related

It is definitely not specific to the FFI template.

but Windows desktop specific instead.

This particular instance was specific to Windows. The general category of failures is not though, and it only makes sense to address in general. The specific PR didn't do anything wrong, or anything fundamentally different from many PRs before it on a variety of platforms.

(Another option is that we could not encode the version, and on any build failure, check .metadata and if it's a hash that's not in the current branch's history, throw a generic "Hey, did you know you're trying to use an older version of Flutter and that's not supported?" error message.)

I think this would be dangerous as the failures won't be limited to build-time only.

Can you provide an example of a non-build-time failure that could result here? All of the cases I can think of where this has happened in the past were build-time.
(Also, keep in mind that if your argument is just "a different version of Flutter could have different runtime behavior than what the author tested", that's true in the other direction too; there's no guarantee that the Dart code of an arbitrary project will work in any given later version of Flutter.)

Can you provide an example of a non-build-time failure that could result here? All of the cases I can think of where this has happened in the past were build-time.

I didn't realize that potential failures of using older Flutter with more recent plugins are guaranteed to be build-time only. Is that what you are saying?
It seems possible to change compilation flags/preprocessor defines used by flutter run that would result in differently generated code, changing program's runtime behavior.

(Also, keep in mind that if your argument is just "a different version of Flutter could have different runtime behavior than what the author tested", that's true in the other direction too; there's no guarantee that the Dart code of an arbitrary project will work in any given later version of Flutter.)

Having flutter version lower/upper boundaries is supposed to solve this.

I didn't realize that potential failures of using older Flutter with more recent plugins are guaranteed to be build-time only.

This is not about plugins though, this is about apps. The interface between plugins and the Flutter build system is narrow, and much more carefully controlled. And as discussed offline, the plugin template already has a minimum Flutter version that corresponds to what the plugin it creates requires.
The problem you had was not that you were trying to use a plugin with an older version of Flutter, it's that you were trying to build an app with an older version of Flutter than the app's template. Per my comments above, the fact the app happened to be the example app of a plugin is irrelevant, it's just the thing you happened to be doing.
App builds are much more deeply tied to the flutter tooling.

Having flutter version lower/upper boundaries is supposed to solve this.

There's no such thing as a Flutter upper bound.


Foundry crashes with arithmetic operation overflow after forge-std dependency update

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (70f4fb5 2022-11-02T00:05:06.592613Z)
What command(s) is the bug in?
forge test
Operating System
Linux
Describe the bug
Hello, after updating forge-std dependency foundry started crashing with arithmetic operation overflow error. The issue is occuring locally on my M1 Macbook as well as in a linux docker container in CI. Here is the code and here is the log of a failing CI pipeline.

I think this is a U256 overflow, @mds1 were there any changes re balance or similar?

@benesjan I believe it's the deal cheatcode that overflows here https://github.com/AztecProtocol/aztec-connect-bridges/blob/f8ef3f8dc5a3c21046d20fa235de6271586cb1a1/src/test/bridges/erc4626/ERC4626.t.sol#L108

There's no changes in forge-std that I can think of that would cause. Though it seems to me like this is a forge error, not a forge-std error. From lines 87-89 of the linked CI job:
The application panicked (crashed).
Message:  arithmetic operation overflow
Location: /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/primitive-types-0.11.1/src/lib.rs:38

If this was a solidity/EVM overflow it wouldn't panic

okay it's the bound here
https://github.com/AztecProtocol/aztec-connect-bridges/blob/f8ef3f8dc5a3c21046d20fa235de6271586cb1a1/src/test/bridges/erc4626/ERC4626.t.sol#L105
if you change the max to type(uint96).max it succeeds, unclear why there's a U256 overflow,
there's no cheatcode involved perhaps this is an issue inside the evm

It seems that the ERC4626Test is failing with overflow error and weirdly it causes forge to crash for me most of the time.  Tried to run it a few times and only once from ~8 runs forge didn't crash.

maybe related to the uint96 value fuzzing
@joshieDo any ideas?

@benesjan have you narrowed down the cause of this, i.e. are you sure it's the forge-std update as mentioned in the original description vs. a certain forge release that introduced this?

I've narrowed this down to these lines
https://github.com/AztecProtocol/aztec-connect-bridges/blob/f8ef3f8dc5a3c21046d20fa235de6271586cb1a1/src/test/bridges/erc4626/ERC4626.t.sol#L56-L57
at least if I comment out the entire testFullFlow test and those two lines then the panic goes away.
 forge test --match-test "testFullFlow" --match-contract "ERC4626"

@mds1 it's not caused by the update but it seems the update makes it more frequent. I think that my test are simply failing with the overflow error and for some reason it causes forge to crash. Sometimes forge doesn't crash and I see that the tests fail with the overflow error. I tried compiling an older forge version (from October 17) and the issue occurs there as well.

the randomness of this is likely related to the fuzz test function's inputs.
Me guess at this point is, that the state changes inside the prank are picked up by the fuzzer (which looks at state) and perhaps the uint96 strategy has a problem with those values.

Hello, this forge bug is still occurring. I have an unrelated example. I introduced a bug in test in this commit which caused overflow in the tested smart contract. This overflow caused forge to crash. Log can be seen in our CI pipeline here.

is it still the same test?

No, it's a different test. Previously it was an ERC4626 bridge test and now it is a TroveBridge test. They are unrelated and don't share basically any code.

sorry, I meant test function

It's a different test function. I run locally the following command and it fails:
forge test --fork-block-number 14970000 -m 'testRedistributionSuccessfulSwap' --fork-url https://mainnet.infura.io/v3/9928b52099854248b3a096be07a6b23c
It is on this PR's branch.
Thanks

thanks,
no fuzz test this time, makes it easier to debug, will have a closer look.

@benesjan found it after I spent some time debugging the test.
there was an edge with deal+transfer that was triggered on revert. fixed in #3767

@mattsse Thanks a ton! This was haunting us for a while 😌 Will close the issue once it gets to a release and I test it.

@mattsse Unfortunately it seems that the issue was not eliminated. The bug occured in our CI pipeline again and there we always install the newest release.

Hello @mattsse, while trying to reproduce the bug I've stumbled upon another one:

After dealing 5 ETH to an address owner's balance suddenly drops to 1 wei.
This is how you should be able to reproduce it:
Checkout the janb/foundry-bug branch and run:
forge test -m testLiquidationFlowWithCollateralToClaim --fork-url https://mainnet.infura.io/v3/9928b52099854248b3a096be07a6b23c --fork-block-number 15977385 -vv
I just executed foundryup so I am using the newest version.

@mattsse
I believe I maybe suffering from the same issue. I have it narrowed down to a much smaller, very simple example. Would it be useful to post that information here? I don't want to clog up the thread unnecessarily.

@mattsse
I believe I maybe suffering from the same issue. I have it narrowed down to a much smaller, very simple example. Would it be useful to post that information here? I don't want to clog up the thread unnecessarily.

yes please, ty!

Below are the test file and the library where I get the overflow. It's the UniswapV3 FullMath library (https://github.com/Uniswap/v3-core/blob/main/contracts/libraries/FullMath.sol), but I copy paste the one I have locally.
I verified that when I simulate a transaction in tenderly, I DO NOT get the same overflow (it errors for a different but expected reason). There is an internal call that replicates the test exactly in the second call to computeSwapStep I believe. The details for this tenderly simulation are:
Contract: https://polygonscan.com/address/0x45dda9cb7c25131df268515131f647d726f50608
Function: swap()
Address: <pick your own, doesn't matter>
bool: true
int256:<PHONE_NUMBER>4
uint256:<PHONE_NUMBER>990871670710978874800773
bytes: 0x
BlockNumber: 33948395
TxIndex: 33948395
From: <shouldn't matter, use 0x2791bca1f2de4661ed88a30c99a7a9449aa84174>
Gas: 8000000
Test File:
// SPDX-License-Identifier: GPL-3.0-or-later
pragma solidity ^0.8.6;

import<EMAIL_ADDRESS>
import '../src/libraries/FullMath.sol';

contract TestOverflow is Test {
    function testOverflow() public {
        uint256 a =<PHONE_NUMBER>57838830346177341558886063651162161152;
        uint256 b =<PHONE_NUMBER>626470956922431708142;
        uint256 denomiator =<PHONE_NUMBER>360498141667901306508915;

        uint x = FullMath.mulDivRoundingUp(a,b,denomiator);
    }
}

Library that oveflows:
// SPDX-License-Identifier: MIT

pragma solidity >=0.4.0 <0.9.0;

/// @title Contains 512-bit math functions
/// @notice Facilitates multiplication and division that can have overflow of an intermediate value without any loss of precision
/// @dev Handles "phantom overflow" i.e., allows multiplication and division where an intermediate value overflows 256 bits
library FullMath {
    /// @notice Calculates floor(a×b÷denominator) with full precision. Throws if result overflows a uint256 or denominator == 0
    /// @param a The multiplicand
    /// @param b The multiplier
    /// @param denominator The divisor
    /// @return result The 256-bit result
    /// @dev Credit to Remco Bloemen under MIT license https://xn--2-umb.com/21/muldiv
    function mulDiv(
        uint256 a,
        uint256 b,
        uint256 denominator
    ) internal view returns (uint256 result) {
        // 512-bit multiply [prod1 prod0] = a * b
        // Compute the product mod 2**256 and mod 2**256 - 1
        // then use the Chinese Remainder Theorem to reconstruct
        // the 512 bit result. The result is stored in two 256
        // variables such that product = prod1 * 2**256 + prod0
        uint256 prod0; // Least significant 256 bits of the product
        uint256 prod1; // Most significant 256 bits of the product
        assembly {
            let mm := mulmod(a, b, not(0))
            prod0 := mul(a, b)
            prod1 := sub(sub(mm, prod0), lt(mm, prod0))
        }

        // Handle non-overflow cases, 256 by 256 division
        if (prod1 == 0) {
            require(denominator > 0);
            assembly {
                result := div(prod0, denominator)
            }
            return result;
        }

        // Make sure the result is less than 2**256.
        // Also prevents denominator == 0
        require(denominator > prod1);

        ///////////////////////////////////////////////
        // 512 by 256 division.
        ///////////////////////////////////////////////

        // Make division exact by subtracting the remainder from [prod1 prod0]
        // Compute remainder using mulmod
        uint256 remainder;
        assembly {
            remainder := mulmod(a, b, denominator)
        }
        // Subtract 256 bit number from 512 bit number
        assembly {
            prod1 := sub(prod1, gt(remainder, prod0))
            prod0 := sub(prod0, remainder)
        }

        // Factor powers of two out of denominator
        // Compute largest power of two divisor of denominator.
        // Always >= 1.
        uint256 twos = uint256(-1*int256(denominator) & int256(denominator));
        // Divide denominator by power of two
        assembly {
            denominator := div(denominator, twos)
        }

        // Divide [prod1 prod0] by the factors of two
        assembly {
            prod0 := div(prod0, twos)
        }
        // Shift in bits from prod1 into prod0. For this we need
        // to flip `twos` such that it is 2**256 / twos.
        // If twos is zero, then it becomes one
        assembly {
            twos := add(div(sub(0, twos), twos), 1)
        }
        prod0 |= prod1 * twos;

        // Invert denominator mod 2**256
        // Now that denominator is an odd number, it has an inverse
        // modulo 2**256 such that denominator * inv = 1 mod 2**256.
        // Compute the inverse by starting with a seed that is correct
        // correct for four bits. That is, denominator * inv = 1 mod 2**4
        uint256 inv = (3 * denominator) ^ 2;
        // Now use Newton-Raphson iteration to improve the precision.
        // Thanks to Hensel's lifting lemma, this also works in modular
        // arithmetic, doubling the correct bits in each step.
        inv *= 2 - denominator * inv; // inverse mod 2**8
        inv *= 2 - denominator * inv; // inverse mod 2**16
        inv *= 2 - denominator * inv; // inverse mod 2**32
        inv *= 2 - denominator * inv; // inverse mod 2**64
        inv *= 2 - denominator * inv; // inverse mod 2**128
        inv *= 2 - denominator * inv; // inverse mod 2**256

        // Because the division is now exact we can divide by multiplying
        // with the modular inverse of denominator. This will give us the
        // correct result modulo 2**256. Since the precoditions guarantee
        // that the outcome is less than 2**256, this is the final result.
        // We don't need to compute the high bits of the result and prod1
        // is no longer required.
        result = prod0 * inv;
        return result;
    }

    /// @notice Calculates ceil(a×b÷denominator) with full precision. Throws if result overflows a uint256 or denominator == 0
    /// @param a The multiplicand
    /// @param b The multiplier
    /// @param denominator The divisor
    /// @return result The 256-bit result
    function mulDivRoundingUp(
        uint256 a,
        uint256 b,
        uint256 denominator
    ) internal view returns (uint256 result) {
        result = mulDiv(a, b, denominator);
        if (mulmod(a, b, denominator) > 0) {
            require(result < type(uint256).max);
            result++;
        }
    }
}

I suppose this could also be a compiler bug due to the fact the local contract is solidity 0.8.13 and the on-chain contract is 0.7.6, but this seems unlikely.

@mattsse
I believe I maybe suffering from the same issue. I have it narrowed down to a much smaller, very simple example. Would it be useful to post that information here? I don't want to clog up the thread unnecessarily.

yes please, ty!

Pasted above

@benesjan it appears either #3688 or 3687 has fixed that, couldn't reproduce on master, but present on nightly

@sprw121 does your code make use of deal cheatcode? of not then this is unrelated, could you please open a separate issue for this, and ideally create a repro repo so I can reproduce this more easily?

@sprw121 does your code make use of deal cheatcode? of not then this is unrelated, could you please open a separate issue for this, and ideally create a repro repo so I can reproduce this more easily?

No cheat code. Yes I can try to put up a repro repo. Let me know if you want me to delete / clean up the comments in this thread.

Hello @mattsse, our CI is now passing without any crashes so you can probably close this issue. Thank you for fixing this 👍

Hi @mattsse — wanted to share that I'm unfortunately running into a similar issue. As far as I can tell, if a test combines the following, it leads to intermittent crashing of foundry:

using a fuzzed uint256 value with the deal cheatcode
expectRevert

When I get a chance, I will try to create a small repro example!

@benesjan, I'm curious if you had to do anything specific to resolve the issue in your code?


There is a situatioin nodejs code has no code-auto-completion

Issue Type: Feature Request
I common the no Code auto-complete position.
I'm not sure if the question is mine or VS,if you can figure out why this happend i would be appreciated.
Thanks~~~
Nodejs - Serv.js
const net = require( 'net' );
const port = 8000;
const hostname = '<IP_ADDRESS>';

// Define two variables, one for counting and one for saving the client
let clients = {};
let clientName = 0;

// createServer
const server = new net.createServer((c)=>{
  c.write('123')
});

server.on('connection', (client) => {

  client.name = ++clientName; // give every client a name
  clients[client.name] = client; // save client to clients
  console.log(client);

  //client.     //The Socket cannot be recognized as a Socket and cannot be automatically completed
  //client.write('hello everybody~~');  //Handwriting,code works

  // for (i in clients){
  //   clients[i].                   //no automatically completed either
  // }

  client.on('data', function (msg) { //Receive messages from customers
    console.log(`client${client.name}Send a message:${msg}`);
  });

  client.on('error', function (e) { //Listen for client exceptions
    console.log('client error' + e);
    client.end();
  });

  client.on( 'close', function () {
    delete clients[client.name];

    console.log(`Client${ client.name }is offline`);
  });

});

server.listen( port,hostname,function () {
  console.log(`Serv runs on：http://${hostname}:${port}`);
});

Nodejs - Client.js
const net = require('net');

const socket = new net.Socket();

const port = 8000;

const hostname = '<IP_ADDRESS>';

socket.setEncoding = 'UTF-8';

socket.connect( port,hostname,function(){
  socket.write('hello AVBody~~');
});

socket.on( 'data', function ( msg ) {
  console.log( msg.toString() );
});

socket.on( 'error', function ( error ) {
  console.log( 'error' + error );
});

socket.on('close',function(){
  console.log('Serv is not alive');
});

VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18362

This has nothing to do with LSP. Looks like a general TS question to me.

This code is incorrect; you are calling new net.createServer(...) but createServer is not a constructor so new should not be used here. After fixing this, I see suggestions working as expected
VS Code will report this problem if you enable type checking in JS files

This code is incorrect; you are calling new net.createServer(...) but createServer is not a constructor so new should not be used here.
I'm so sorry to bring you extra workload

This code is incorrect; you are calling new net.createServer(...) but createServer is not a constructor so new should not be used here. After fixing this, I see suggestions working as expected
VS Code will report this problem if you enable type checking in JS files

and Thanks for your guiding, bro


Including carthage debug symbols into final archive

I've a project with a bunch of framework dependencies managed with Carthage. After archiving the product all internal debug symbols for app and frameworks are included as expected, but Carthage ones are not. Whilst the behaviour is expected, it surely must be a common thing to do? Or not? I couldn't find a simple way doing this in Xcode, is there a way doing it with fastlane?
✅ fastlane environment ✅
Stack

Key
Value

OS
10.11.6

Ruby
2.3.0

Bundler?
false

Git
git version 2.10.2

Installation Source
~/.rubies/ruby-2.3.0/bin/fastlane

Host
Mac OS X 10.11.6 (15G1217)

Ruby Lib Dir
~/.rubies/ruby-2.3.0/lib

OpenSSL Version
OpenSSL 1.0.2e 3 Dec 2015

Is contained
false

Is homebrew
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_GB.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.14.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
1.5.1

CFPropertyList
2.3.5

claide
1.0.1

colored
1.2

nanaimo
0.2.3

xcodeproj
1.4.2

rouge
1.11.1

xcpretty
0.2.4

terminal-notifier
1.7.1

plist
3.2.0

public_suffix
2.0.5

addressable
2.5.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.2

highline
1.7.8

commander
4.4.3

excon
0.54.0

faraday
0.11.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.0.1

gh_inspector
1.0.3

uber
0.0.15

representable
2.3.0

retriable
2.1.0

hurley
0.2

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

jwt
1.5.6

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

httpclient
2.8.3

google-api-client
0.9.26

mini_magick
4.5.1

multi_xml
0.6.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

dotenv
2.2.0

bundler
1.14.3

faraday_middleware
<IP_ADDRESS>

json
2.0.3

io-console
0.4.6

rubyzip
1.2.0

unicode-display_width
1.1.3

terminal-table
1.7.3

generated on: 2017-02-07

@ianbytchek seems to be a problem with carthage itself. maybe this https://github.com/Carthage/Carthage/issues/507#issuecomment-121086252 comment helps.
not sure if this something fastlane could solve!

@hjanuschka I've been pointed in the right direction, thanks for the clue!


Update mock notes to call create_note via the wallet interface

What should be done?
Replace the constants on the mock notes 1 2 to use the wallet interface instead
How should it be done?
The test code should not longer reference a procedure by MAST, but instead use the miden-lib
When is this task done?
When the constant is no longer necessary
Additional context
No response

I suppose the constants for all procedures, except ACCOUNT_ACCOUNT_PROCEDURE_1_MAST_ROOT and ACCOUNT_ACCOUNT_PROCEDURE_2_MAST_ROOT, should eventually be removed

I believe note scripts have been tackled. I tried factoring out the MASM code into an account library in the rest of the tests but hit an unexpected issue which I pinged @bobbinth about last week.

Closed by #856


Retrieve metadata info on new package version

Requirements

[x] Have you ran tests against this code?

Description of the Change

Added a new metadataAppendTarballInfo in git module to append tarball and hash to version metadata package; this should fix the missing tarball url when publishing a new version.
Little refactoring to selectPackageRepository using switch.
In postPackagesVersion do not retrieve the tag parameter anymore since it's not used (I wonder if we should update the documentation to not require this parameter or leave it for compatibility reasons).
Made a new URL parsing process in getPackagesVersionTarball, I hope this fixes the issue in production. @confused-Techie please, test it.

@confused-Techie I see we add a dist property in the response package with a custom tarball url, why? Can't we just pass the tarball_url we append previously?
Fixes #30

And one thing I would like to try and test more, is when we get the tagged data for a new version publish, are we always getting the right one? It looks like from here we would since we are checking it against the version in the package.json

This can be done. In the current state, the latest version is published even when you send a wrong tag, because we only rely on the one inside the package json. I will open an issue to discuss about this.


Allow fingerprinting of generated images

This addon allows resolving the fingerprinted asset path, even when generating the path dynamically: https://github.com/RuslanZavacky/ember-cli-ifa. This could solve the current problem having to turn off fingerprinting for our generated images.
We could either add ifa as a dependency to this addon so it is always available. Or dynamically detect its presence and add support for it when available.

v0.5.0 now supports fingerprinted images :-)

👍🍾👏🚀


Frequent Crashes during reading(Beta r6789)

Steps to reproduce
Nothing special, just normal use
Behavior is observed during reading through pages
Expected behavior
Shouldn't crash and things should load
Beta version though, so it's understandable
Actual behavior
App occasionally crashes during reading
Crash logs

Mihon version
App version: 0.16.5-6789 (standard, 0af90999c, 7, 2024-07-27T21:18:15Z) Android version: 14 (SDK 34; build U1UGS34.23-82-2-2) Device brand: motorola Device manufacturer: motorola Device name: fogos (fogos_g) Device model: moto g34 5G WebView: Android System WebView 127.0.6533.64
Android version
Android 14, stock rom with no OS modifications
Device
Moto G34 5g (Fogos)
Other details
Battery saver is enabled, along with device's "App Battery Usage" feature set to Restrict"
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.5.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

Not sure if it is extension related but if it helps, I was using a MangaDex extension at the time of taking these crash logs

Not sure if it is extension related but if it helps, I was using a MangaDex extension at the time of taking these crash logs
Updated to r6793, will come back with crash logs if it happens again

Please avoid naming extensions both here and on the Discord server since Mihon is not associated with or providing support for extensions,

Not sure if it is extension related but if it helps, I was using a MangaDex extension at the time of taking these crash logs
Updated to r6793, will come back with crash logs if it happens again

Please avoid naming extensions both here and on the Discord server since Mihon is not associated with or providing support for extensions.

My mistake
I have updated my comment, thanks for letting me know.
Thanks a lot for continuing this project, it means a lot to me and the rest of the community and none of us want it to face trouble again.

Similar crash:

Happened in the same way(while reading)
App version: 0.16.5-6793 (standard, de8ef6dad, 7, 2024-08-03T21:19:24Z)
Android version: 14 (SDK 34; build U1UGS34.23-82-2-2)
Device brand: motorola
Device manufacturer: motorola
Device name: fogos (fogos_g)
Device model: moto g34 5G
WebView: Android System WebView 127.0.6533.64

Decoded stack trace:
java.lang.Throwable: java.lang.IndexOutOfBoundsException: Index: 41, Size: 40
        at java.util.ArrayList.rangeCheckForAdd(ArrayList.java:763)
        at java.util.ArrayList.add(ArrayList.java:488)
        at eu.kanade.tachiyomi.ui.reader.viewer.pager.PagerViewerAdapter.setChapters(PagerViewerAdapter.kt:84)
        at eu.kanade.tachiyomi.ui.reader.viewer.pager.PagerViewer.setChaptersInternal(PagerViewer.kt:280)
        at eu.kanade.tachiyomi.ui.reader.viewer.pager.PagerViewer.setChapters(PagerViewer.kt:268)
        at eu.kanade.tachiyomi.ui.reader.ReaderActivity.setChapters(ReaderActivity.kt:599)
        at eu.kanade.tachiyomi.ui.reader.ReaderActivity.access$setChapters(ReaderActivity.kt:103)
        at eu.kanade.tachiyomi.ui.reader.ReaderActivity$onCreate$9.invokeSuspend(ReaderActivity.kt:215)

Corresponding source:
https://github.com/mihonapp/mihon/blob/3f050a83dd0907e0ffb56a1e1833f9de5b10b329/app/src/main/java/eu/kanade/tachiyomi/ui/reader/viewer/pager/PagerViewerAdapter.kt#L78-L85
You can disable "split wide pages" as a workaround before it gets fixed.


Upgrade to graphql-java v8.0

When are you planning to bump the version of graphql-java to v8.0?
Many improvements and bug fixes are very interesting.
Thanks!

As soon as I get a chance. Directive support open up some very interesting possibilities. I'll start the work immediately after 0.9.7 release.

I was intending to release it today, but got tangled. I'll try to finish up tomorrow, but even in the worst case it will be out by weekend.


Question: Creating clusters in different accounts using pcluster from Lambda

What is the suggested way to create a cluster in a different account from a Lambda function?
We currently have a Lambda function (as suggested by this blog post) that can be called to create/delete clusters in account A. We want to be able to provision the resources for the creation of the parallelcluster in a different account (e.g., account B), determined by parameters passed to the Lambda function (in account A). We were thinking of creating a cross-account IAM role in account B that gives permission to account A to create a pcluster in account B. We also know that we can use sts to assume a role in the Lambda function. However, we are not sure what is the recommended way to specify that the pcluster gets created in account B.
Thank you.

Hi @cailinw,
the approach you described is reasonable.
In account B you have to create a role with the ParallelClusterUserPolicy (see https://docs.aws.amazon.com/parallelcluster/latest/ug/iam.html) that will allow to manage the cluster (creation, deletion, etc.). This role should be configured with a "trust relationship" so that the account A can assume it.
The lambda called from the account A will assume that role so that it's able to impersonate the account B.

@lukeseawalker Thank you so much for the response. That should work for us.


[SR-4559] Warn when unapplied reference to a function 'self' is referenced in property initialiser

A fix to warn when unapplied references to a function called 'self' from are referenced unqualified from property initialisers.
Update: have fixed false positive referred to in strikethrough:
I'm having an issue though where my error message still shows when the reference is not unapplied. This is not allowed as it uses an instance method from a non-lazy initialiser, so there is no need for the error message I've added. Not sure how best to fix this as I'm brand new to Swift compiler contributions so any ideas would be much appreciated, I've already added a check for unapplied reference before showing the diagnostic. I'm assuming it technically is still treated as an unapplied reference because you can't call the function from a property initialiser, even though I have included the brackets to call it.

https://bugs.swift.org/browse/SR-4559

@swift-ci smoke test

@swift-ci smoke test

@varungandhi-apple I'm assuming cause I pushed after you did the smoke test the smoke tests haven't run, guessing you need to start them again? thanks for starting them initially

@swift-ci please smoke test

Thank you, @jackgmarch!


PlayerBattleEndEventListener IsDefeatedBanditLike crashes

triggered when beat thugs in a town
* System.NullReferenceException
HResult=0x80004003
Message=Object reference not set to an instance of an object.
Source=KaosesTweaks
StackTrace:
at KaosesTweaks.Event.PlayerBattleEndEventListener.IsDefeatedBanditLike(MapEvent m) in U:\BannerLord\MyMods\KaosesTweaks\KaosesTweaks\Event\PlayerBattleEndEventListener.cs:line 137

fixed 1.0.4


Bio Weekly- UChicago Clincal Collection Metrics

Metrics that we expect to UChicago added to:
Table 1.3: Baseline Clinical Biospecimen Collections by Clinic Location (list out each location)
•	Table 2.2: Baseline Clinical Biospecimen Collection Completeness by Specimen Type
•	Table 2.9: Baseline- Total Blood Tubes Collected Among Clinical Biospecimen Collections
•	Table 2.10: Baseline Blood Tubes Collected Among Clinical Biospecimen Collections by Tube Type
o	Add to footer for UCM: (4) SFH: 2 SST, 1 Heparin, 1 EDTA
•	Table 3.2: Baseline Biospecimen Survey Status Among Clinical Collections
•	Table 3.5: Baseline Biospecimen Survey Completion Time from Clinical Collection Dashboard Entry
•	Table 3.9: Baseline Biospecimen Survey Completion Length (in Minutes) Among Submitted Clinical Surveys (Post-COVID-19 Questions Removal)
•	Table 4.5: Baseline- Time (in Days) from Verification to Clinical Collection Among Participants Verified Before 2/01/2023 (please also add HP and Sanford to this table----thinking this through again, they may have had particiapnts verified before 2/1/2023 that opt for Clincial Collection once they know it is an option)
•	Table 4.6: Baseline- Time (in Days) from Verification to Clinical Collection Among Participants Verified on or After 2/01/2023
•	Table 5.3: Baseline Collection-To-Receipt Time (in Days) Among Clinical Collections
•	 Table 5.4: Baseline Collection-To-Receipt Time (in Days) Among Clinical Collections by Clinic Location (list out each location)
•	Table 5.6: Baseline- Time (in Hours) from Clinical Collection to Receipt by Clinic Location (list out each location)
New Tables/Figures needed:
•New table needed, will be Table 1.9: Baseline Collection Setting Among Biospecimen Collections by Specimen Type, University of Chicago Medicine
• Update needed to: Figure 5.4: Baseline Collection-To-Receipt Time (in Hours), University of Chicago Medicine--make this: Figure 5.4: Baseline Collection-To-Receipt Time (in Hours),  University of Chicago Medicine Research Setting
• New Figure needed, will be 5.5: Baseline Collection-To-Receipt Time (in Hours), University of Chicago Medicine, Clinical Setting
• New Figure needed, will be Figure 6.6: Baseline− Weekly Biospecimen Collections by Collection Setting, University of Chicago Medicine
• New Figure needed, will be Figure 6.8: Baseline- Weekly Clinical Biospecimen Collections by Clinic Location, University of Chicago Medicine
Footnote Updates:
Tables 4.8 and 4.9 add UChicago (and Sanford) to exclusion list with HP
NOTE: UChicago should also be excluded in the QC rule:
a. Custom QC Report (pdf report)
• Rule Bio Metric - Distribution Curves for Research Collection Visit Length #18 and Bio Metric - Weekly Biospecimen Data Tables  #19: IF BioClin_BldOrderPlaced_v1r0/BioClin_UrnOrdPlaced = 1, THEN BioClin_BldOrderPlacdDt_v1r0/BioClin_BldOrderPlacdDt_v1r0 must be populated. HP Excluded.

@KELSEYDOWLING7 Crosswalk for UChicago clinical collection locations is below:
South Loop (location id = 1)
Orland Park (location id = 2)
Kenwood (location id = 3)
River East (location id = 4)
Dearborn Station (location id = 5)

@erincschwartz  I don't think that's right...We already have d_173836415_d_266600170_d_185243482==1,2,3 and d_173836415_d_266600170_d_452847912==1,2,3 for HP locations

@KELSEYDOWLING7 The crosswalk info above is what Nina sent to Madhuri and looking at their first clinical collection, they sent BioClin_SiteBldLocBL_v1r0 = 1 (that collection was at South Loop). Do we need to tell Chicago that they need new designations for their clincal collection locations since HP already took 1,2,3?

@erincschwartz  That's correct, those values are already taken. It looks like the DD was incorrectly updated so I just emailed Rebecca to change that as well

@erincschwartz

Should 2.9 have an updated footnote matching 2.10?

Table 4.5 includes all clinical sites, but there are no matching collections for HP, SF, or UC

(Table 5.3)

Excluded from the QC rules:
"IF BioClin_BldOrderPlaced_v1r0/BioClin_UrnOrdPlaced = 1, THEN BioClin_BldOrderPlacdDt_v1r0/BioClin_BldOrderPlacdDt_v1r0 must be populated. HP Exclude.". Reflected in today's Biospecimen QC

@KELSEYDOWLING7; just reviewed and have a few notes:

Table 2.9 should have updated footnote, please add "UChicago- 4"

Table 2.10 should have updated footnote, please add "(4)UChicago- 2 SST, 1 Heparin, 1 EDTA"

UChicago should not be included in Tables 4.8 or 4.9, can you remove?

The data in 6.6 shown above does not seem right, compared to Figure 6.5 in the prod report (I looked at last week's report). Can you double check this?

Can figure 6.8 be edited to remove all the blank space before 5/20?

@erincschwartz  Thanks for reviewing so quickly

@KELSEYDOWLING7 Everything looks good.
Just checking, in Figure 6.8, I assume Dearborn Stations collection is overed up by the South Loop dot, correct?

@erincschwartz  Great! Yes, Dearborn had 1 on 6/3 but not on 6/10. I can also update the graph to include 0 on the y axis if you want to see that line always continue

@KELSEYDOWLING7 add as-is for now and please work to add the 0 for next automation

@erincschwartz  Right now the only way to set Figure 6.8 to 0 is including all Site locations and having all of them set to 0 until the first collection. Do we want that, or is it ok as is? Once the collections are consistent the lines will be as well (see current Figure 6.13 for example)

@erincschwartz  Please advise on the comment above or if this is good to close as is

@KELSEYDOWLING7 I think we do want the lines to dip down to 0 when there are no collections. We have more data now that weeks have passed and I think that the figure will be more descriptive if we can see the weeks when there weren't any clincal collections at a given location

@erincschwartz Ok that would look like this

@KELSEYDOWLING7, let's go with this so we can see when clincial locations dip down to 0 collections. I imagine as clinical collections ramp up, the figure will look different/better

@erincschwartz  Please let me know if this looked good on Monday's report and this issue is good to close

@KELSEYDOWLING7 UChicago clincal collection metrics look good. Issue is ready to close.


Update aidg-FAQ.md

Added a whole bunch of stuff and edited a few others, please check to see if I have missed anything before committing.

everything looks good to me, great job!


Any interest in a PR to support WASM based clients?

Hey Maintainers,
I have created a fork of tarpc, that supports WASM clients. I'm curious what the apatite is for supporting such a PR, maybe with an experimental feature flag? I have a few forked repos that have it all working end to end, see the links below. The nice thing is that the changes aren't heavy for tarpc. It really is just a few shims for the std::time/tokio::time calls and enabling a dependency feature flag (WASM support for rand crate). The only issue is I'm not sure if the time shim library is being actively maintained, I plan to file an issue with that project and see if they would accept a PR. If they aren't actively maintaining the project I can fork it and maintain it since shims aren't a lot of work and I'd like to explore this approach in a project I'm working on.
Side note: I started this a couple of weeks back, so my code is targeting tarpc 0.22, however I did test it with 0.23 (See the other branch) and it appears to work fine (IE, it compiles). I couldn't test it since my client/server have a dependency that hasn't moved to tokio 0.3 yet.
tarpc fork:
https://github.com/google/tarpc/compare/master...john-hern:wasm_support
Notes: I'll likely move the SystemTimeExt trait/impl into the wasm-timer fork/PR and implement from/into on the SystemTime type.
wasm-timer fork:
https://github.com/tomaka/wasm-timer/compare/master...john-hern:tokioShim
Notes: Nothing interesting here except the reimplementation of tokio's timeout API using the shims.
server/client example.
https://github.com/john-hern/tarpc-wasm-client-tcp-server-example
Notes:
The server is using tokio + ws_stream_tungstenite to create the byte stream/sink over a websocket.
The client is a yew application, using ws_stream_wasm wasm_bindgen (spawn_local).
There are probably some caveats with edge cases. For example, the time shims wont work in a web worker. There is an issue in web-sys to address this. Once it's fixed, it should be possible to use this code in a web worker. Also, since wasms are currently single threaded there are probably some perf concerns. I'm pretty sure other things may pop up.
Thoughts?
*edit: Had the wrong link for the wasm-timer fork.

Hey, this is very cool! I didn't know futures worked on WASM :) I am happy to merge WASM support under a feature flag, especially since it appears to require such minimal changes. I might suggest providing a tarpc::time module facade so that the other modules don't have to have #[cfg(wasm)] scattered about.

Awesome. I'll reach out to the wasm-timer team and see if I can elicit a response. I already updated the branches to add the façade (Good suggestion), and moved over the SystemTime conversation to an into implementation in that crate. I'll circle back in a week or two once I get a better feeling about their ability to support the project long term. I'll update this thread with a link to the issue once I create it for tracking.

Any updates on this? I'd love to be able to have RPC clients in the browser!

Any updates on this? I'd love to be able to have RPC clients in the browser!

@john-hern closing due to inactivity but feel free to reopen if you pick this back up!

FYI, the following patch (to 75b15fe) allows tarpc to compile on wasm32-unknown-unknown now.
diff --git a/Cargo.toml b/Cargo.toml
index c7557d0..3e8109d 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -2,7 +2,7 @@
 resolver = "2"

 members = [
-    "example-service",
+    # "example-service",
     "tarpc",
     "plugins",
 ]
diff --git a/tarpc/Cargo.toml b/tarpc/Cargo.toml
index b2f037b..34255b3 100644
--- a/tarpc/Cargo.toml
+++ b/tarpc/Cargo.toml
@@ -61,6 +61,8 @@ tracing = { version = "0.1", default-features = false, features = [
 tracing-opentelemetry = { version = "0.17.2", default-features = false }
 opentelemetry = { version = "0.17.0", default-features = false }

+[target.wasm32-unknown-unknown.dependencies]
+getrandom = { version = "0.2.7" , features = [ "js" ] }

 [dev-dependencies]
 assert_matches = "1.4"

Note that we're not compiling example-service/ at all since I didn't look into making that wasm-compatible. Also, I haven't actually tried to see if it not only compiles, but it works (since this is Rust, I assume that to be the case).
I have put aside tarpc for now, but I thought I'd share this.


Custom Response Code

New Issue Checklist

[ x ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
flutter / ios

Platform Version
v1.9.1+hotfix.2 / iOS - 12.1

Dio Version
^3.0.2

Android Studio / Xcode Version
XCode - 10.1

Repro rate
100%

Repro with our demo prj
no related content

Demo project link
Can't Provide

Issue Description and Steps
When making a post request using Dio().post() to an api that does not return a standard response code (e.g. 900), the request gets stuck and does not hit a catch block.
Is there any way to handle non-standard response codes?

Same issue, any update on this?


Arrow key navigation is not skipping hidden menu items

Describe the bug
When using the arrow keys (up/down) to navigate the menu (e.g. in combobox), hidden items are not being skipped. This results in combobox making selections that it should not.
To Reproduce
Steps to reproduce the behavior:

Go to the airport example on the combobox demo
Type the letter a
use the arrow keys to navigate up and down the menu
See error

Expected behavior
You should not see skips in the navigation where it looks like you no longer have an "active" menu option.

Confirmed. Type on mke into the airports and hit the arrow key down 5 times and hit enter. You should see yakima air terminal.