Fatal Exception: com.facebook.react.common.JavascriptException ReferenceError: Property 'until' doesn't exist, js engine: hermes

Description
In Android the app randomly crashing with the below error. Got this in firebase crashlytics dashboard and there is no log to debug and reproduce.
Below are the dependencies.
"@coffeebeanslabs/react-native-inviewport": "^0.2.0",
"@notifee/react-native": "^7.8.2",
"@ptomasroos/react-native-multi-slider": "^2.2.2",
"@react-native-async-storage/async-storage": "^1.23.1",
"@react-native-community/datetimepicker": "^8.2.0",
"@react-native-community/netinfo": "^11.3.2",
"@react-native-firebase/app": "^18.8.0",
"@react-native-firebase/messaging": "^18.8.0",
"@react-navigation/native": "^6.1.17",
"@react-navigation/stack": "^6.4.0",
"deprecated-react-native-prop-types": "^2.2.0",
"lottie-react-native": "^6.7.2",
"moment": "^2.30.1",
"numeral": "^2.0.6",
"prop-types": "^15.8.1",
"react": "18.2.0",
"react-native": "0.74.3",
"react-native-animated-loader": "^1.0.0",
"react-native-blob-util": "^0.19.9",
"react-native-countdown-component": "^2.7.1",
"react-native-detector": "^0.2.3",
"react-native-device-info": "^11.1.0",
"react-native-document-picker": "^9.3.0",
"react-native-dropdown-picker": "^5.4.6",
"react-native-exit-app": "^2.0.0",
"react-native-fast-image": "^8.6.3",
"react-native-file-viewer": "^2.1.5",
"react-native-fs": "^2.20.0",
"react-native-gesture-handler": "^2.17.1",
"react-native-image-pan-zoom": "^2.1.12",
"react-native-image-picker": "^7.1.2",
"react-native-image-slider": "^2.0.3",
"react-native-image-zoom-viewer": "^3.0.1",
"react-native-keyboard-aware-scroll-view": "^0.9.5",
"react-native-linear-gradient": "^2.8.3",
"react-native-modal": "^13.0.1",
"react-native-orientation": "^3.1.3",
"react-native-paper": "^5.12.3",
"react-native-pdf": "^6.7.5",
"react-native-permissions": "^4.1.5",
"react-native-progress-circle": "^2.1.0",
"react-native-safe-area-context": "^4.10.8",
"react-native-screens": "^3.32.0",
"react-native-segmented-control-tab": "^4.0.0",
"react-native-share": "^10.2.1",
"react-native-simple-bottom-sheet": "^1.0.4",
"react-native-simple-modal": "^9.0.1",
"react-native-simple-toast": "^3.3.1",
"react-native-step-indicator": "^1.0.3",
"react-native-svg": "^15.3.0",
"react-native-swiper": "^1.6.0",
"react-native-table-component": "^1.2.2",
"react-native-text-ticker": "^1.14.0",
"react-native-vector-icons": "^10.1.0",
"react-native-video": "^6.3.0",
"react-native-vision-camera": "^3.9.1",
"react-native-webview": "^13.10.5"
Steps to reproduce
Got it in Firebase Crashlytics and Play Store
React Native Version
0.74.3
Affected Platforms
Runtime - Android
Output of npx react-native info
System:
  OS: Windows 10 10.0.17134
  CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700F
  Memory: 4.31 GB / 15.84 GB
Binaries:
  Node:
    version: 20.17.0
    path: C:\Program Files\nodejs\node.EXE
  Yarn: Not Found
  npm:
    version: 10.8.2
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK: Not Found
IDEs:
  Android Studio: AI-241.18034.62.2411.12169540
  Visual Studio: Not Found
Languages:
  Java: 17.0.12
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.3
    wanted: 0.74.3
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Stacktrace or Logs
Fatal Exception: com.facebook.react.common.JavascriptException: ReferenceError: Property 'until' doesn't exist, js engine: hermes, stack:
anonymous@1:998365
anonymous@1:631935
emit@1:65632
emit@1:63340
__callFunction@1:55692
anonymous@1:53992
__guard@1:54951
callFunctionReturnFlushedQueue@1:53950

       at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:65)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
       at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:146)
       at com.facebook.jni.NativeRunnable.run(NativeRunnable.java)
       at android.os.Handler.handleCallback(Handler.java:1013)
       at android.os.Handler.dispatchMessage(Handler.java:101)
       at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
       at android.os.Looper.loopOnce(Looper.java:226)
       at android.os.Looper.loop(Looper.java:328)
       at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:233)
       at java.lang.Thread.run(Thread.java:1012)

Reproducer
No response
Screenshots and Videos

In Android the app randomly crashing with the below error. Got this in firebase crashlytics dashboard and there is no log to debug and reproduce.

The problem is that your app is dying while trying to execute the 'until' function:
Fatal Exception: com.facebook.react.common.JavascriptException: ReferenceError: Property 'until' doesn't exist, js engine: hermes, stack:

That could be coming from your application code or from a 3p library. Without a reproducer we can't help you further. You should seek further support on StackOverflow or create a reproducer.


feat(syn-solidity): add statements and expressions

Cooking for another project and thought why not make a pr request. I gotta do testing and im pretty sure ive missed a few cases. However just going to keep cooking at ethcc and will do cleanup later

when writing rustdoc for the structs, can you reference the corresponding structure in the solidity grammar for each type?

when writing rustdoc for the structs, can you reference the corresponding structure in the solidity grammar for each type?

oooo like this yes

nice - the idea here is to comptime transpile solidity to rust directly w/o jit'ing into any lower level code rigth?

yeah exactly. also a lot more user friendly to work with. I need to write some tests and stuff but super busy with work rn so the progress will be slow for the next little bit. Ik some of the Primitive devs where also interested in doing a paper based off the results not only looking at speed differences but llvm compile difference when comparing to revm.

Hey @Will-Smith11, I have some free time these coming days, do you mind if I pick this up?

Hey @Will-Smith11, I have some free time these coming days, do you mind if I pick this up?

go for it!

@DaniPopes What is left to be done? I have some free time this weekend and want to push this forward?

Not much, the only thing is testing that the parsed output is what we expected, instead of just "it parses". Also operation order might not be entirely correct

Not much, the only thing is testing that the parsed output is what we expected, instead of just "it parses". Also operation order might not be entirely correct

:+1:

@Will-Smith11 would love if you PoC'ed a benchmark comparing Revm+Solidity compiled vs native transpiled with syn-solidity, Im curious how you see this working for e.g. projects like uniswap-v3

Merging for now, will open a few issues with what's missing.


fix: Update user guide for import

Fixes: #800
Here's a quick visual description of import - I think export and user field actions should come later in the doc

Tomo and Paul, will these import/export features be in the version of AtlasMap that Fuse Online 7.3 uses? or maybe the version that Fuse Online 7.4 uses?

Hey Tova -
No - the import/export features are for the AtlasMap standalone - not
Syndesis or Fuse OnLine.  I'm also working on documenting custom field
actions which are also only available in AtlasMap (not Fuse OL/Syndesis).
--Paul
On Mon, Mar 11, 2019 at 2:24 PM TovaCohen<EMAIL_ADDRESS>wrote:

Tomo and Paul, will these import/export features be in the version of
AtlasMap that Fuse Online 7.3 uses? or maybe the version that Fuse Online
7.4 uses?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/atlasmap/atlasmap/pull/822#issuecomment-471662664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC1-LTD9aWCWw-sT2P4S6OprSZXw2aQwks5vVp9lgaJpZM4boxqv
.


Override detected version

The README says that this package will automatically detect a version from package.json- is there a way to overwrite this, maybe a .version('...') method?

There is no API for that. Does the automatic detection not work well enough?

A few reasons a method might be helpful from the top of my head:

Binary distribution: If a CLI is compiled into a binary, it might not have access to the package.json file and therefore, cannot automatically detect the version.
Testing: During testing, it may be necessary to set a specific version for the CLI to simulate different scenarios.
Independent versioning: If there are multiple CLIs in a project, it may be necessary to set versions independently of each other.
Automated versioning: In certain cases, it may be desirable to set the version automatically based on certain conditions, such as a build number or date.

It doesn't seem like it would be too hard to add, would it?

Seems reasonable. I added a .package function in v1.1.0. Thanks for the suggestion.

Thanks!!


Propagate handling of (unsupported) mutually recursive trait declarations

Companion PR of https://github.com/AeneasVerif/charon/pull/160
This PR propagates the extension of mutually recursive traits in Charon, now raising an error in Aeneas during translation as this feature is currently unsupported.
Marking this as draft for now for two reasons:

The error reporting should likely be enhanced with meta information, however, I am not sure how to retrieve it in the current context (hence the temporary use of craise_meta_opt)
As I extended the Charon traits tests with mutually recursive trait declarations, this leads to failures in Aeneas when running make tests. Maybe a better way is to split the Charon test file into what is supported and unsupported in Aeneas?

The tests that are meant for Charon should be put in charon/tests/ui. The tests in tests/ and tests-polonius/ are meant to be soon moved to aeneas.

Marking as ready as the companion PR has been merged in Charon.
@sonmarcho  Let's improve the error message in a follow-up PR.

I created an issue: https://github.com/AeneasVerif/aeneas/issues/176


Pricing Table

I like this pricing table - free CSS - try to use but keep to material theme as well. The dark bit goes well with the APP interface. Inspect the source for the CSS.
https://graygrids.com/demos/snippets/startup-fw-pricing-table/
In addition, this one is also nice: https://shapebootstrap.net/item/1524967-flat-pricing-table-bootstrap-3-0 - attention to detail is something I'd like you to think about more. Notice how the coloured pricing table is bigger.

[ ] Only 3 pricing tables needed
[ ] the 4th one which is currently the enquiry one needs just a small paragraph to contact us for more detail and quotations. This is when it is 100 vehicles or more. text is "Operating a fleet with 100 vehicles or more? We offer bigger and more bespoke plans also. Contact us for more detail"
[ ] Use clean modern large thin typography and highlight keywords in the "4th price paragraph" with abbr tags and code tags creating modern look, feel and attention to ket messages.

Nice looking pricing tables here....
https://www.freshdesignweb.com/free-css-tables/
http://codepen.io/warzone246/pen/yiHns

Use current pricing table. Add two more sections - one is below that spans across detailing up to 100. Then underneath it should be a contact us for "are you operating 100+ vehicles" then contact us directly.


Add call and return clause

Add Cypher clauses to the query builder:

[x] CALL
[x] WITH
[x] UNWIND
[x] RETURN
[x] YIELD
[x] ORDER BY
[x] LIMIT

@g-despot when the code is done (decision about how exactly the object will be called), README.md also has to be updated 😄

@MasterMedo check out this PR when you get the chance so I know if I am going in the right direction with implementing all the missing Cypher queries in the query builder. Still missing: DELETE, LOAD CSV, MERGE, REMOVE, SET and UNION.
I am currently missing an error handling layer and a logic layer to check if the constructed query is following basic Cypher syntax rules.

I gotta admit, I greatly dislike the name G. I think it's better to be explicit. Class names should be self-explanatory. I'd much rather if we'd create a DeclarativeBase class and exposed it's starting properties as objects to be imported e.g.
match = DeclarativeBase().match
merge = DeclarativeBase().merge

.
from gqlalchemy import match, merge

Another idea is to just rename the G object to QueryBuilder or some other better name.


Request for hemibrain atlas maps

Brianna would like to perform quantitive analysis of hemibrains only with Nutil and wonders whether it's possible to implement support for export of hemibrain atlas maps either in QuickNII or VisuAlign (or automatic generation of binary masks to differentitate the two hemispheres). She has a lot of data, and the alternative solution - to manually generate masks with Fiji or something similar - is very time consuming. It would be great to have your input on this @Tevemadar

The current solution to this problem is hemisphere masks generated with QMask. We can close this for now. 04.05.21.


fixes for smi

Signed-off-by: kumarabd<EMAIL_ADDRESS>

One failing check - https://github.com/layer5io/meshery-linkerd/pull/138/checks?check_run_id=1349099257#step:4:26

One failing check - https://github.com/layer5io/meshery-linkerd/pull/138/checks?check_run_id=1349099257#step:4:26
@kumarabd maybe we can use make golangci-lint execution at local environment, may be it can help you out.
https://github.com/layer5io/meshery-linkerd/blob/f2aff92347096940739df3a546b684883e14fe1e/Makefile#L32-L38

Yes @leecalcote I'm currently using that.


exclude sandbox projects from a preview, close #989

Deploy preview for landscape ready!
Built with commit c03431d6be1037c7691c44ef6b7505882dd1ff88
https://deploy-preview-990--landscape.netlify.com

LGTM


Add create_at and updated_at in PR json

Add fields created_at and updated_at in PR json.
Depends on https://github.com/go-gitea/go-sdk/pull/52. Needs vendor update before merge!
Fixes #907

All done please review :)

LGTM

LGTM


Support Remote API v1.17

These just keep coming. :smile:

Indeed.  I've been a bit backlogged lately but I'll do what I can to take a
look and get these nailed down.
On Mon, Feb 16, 2015 at 4:18 PM, Ahmet Alp Balkan<EMAIL_ADDRESS>wrote:

These just keep coming. [image: :smile:]
—
Reply to this email directly or view it on GitHub
https://github.com/ahmetalpbalkan/Docker.DotNet/issues/14.

Fixed with #50


fix heapster reference to master branch

Fix heapster document reference from commit to master branch.
/cc @random-liu

This change is

LGTM


[Python] Add streaming interceptor example

Added the example because there is no Python streaming interceptor example.
This example doesn't include any decent processing and just prints messages. But I think it'd be helpful to tell where to put a certain processing based on the message.
Future work:

Add server streaming (and bidirectional streaming) to hellostreamingworld.proto and expand this example
Add async_streaming to examples/python/interceptors

Verified locally that it works as intended, we'll merge it once all tests passed.

@XuanWang-Amos It doesn't seem failed tests have anything to do with this PR, but could you tell me how to fix them?

Just started another test run, can you help fix sanity tests? You can run scripts locally using command like ./tools/distrib/black_code.sh

@XuanWang-Amos Thank you. Formatted the code.


Use Timeout::Error instead of TimeoutError

This is due to receiving a deprecation warning:
/Users/takiy33/.ghq/github.com/takiy33/Hours/config/initializers/errors.rb:19: warning: constant ::TimeoutError is deprecated

Thanks!

Thank you for merging.


Toupdate

impletation of pre-request

related issue is "Plan to impletation of Per-request logging #3177"


Improvement: Searching speakers based on Organisation and Country.

I would like to work on this.

Sure, @piyush0 , that sounds like a good feature to be implemented


Check what happens if all respawn positions are occupied

If all respawn positions are occupied, the game will probably put two players on the same coordinates. We should probably place them in a random position of the map in that case.

Add limit of players to room = amount of respawn positions

Add limit of players to room = amount of respawn positions


AWKPATH on Windows

Greetings - (love the extension by the way)
I can't seem to figure out how to configure awk.path to get it to pick up my functions on Windows (It may be an issue on Linux, as well, because -- as strange as this may seem -- the one project I have that uses a lot of awk scripts is on my miserable Windows box so I've not had an opportunity to try running this on Linux).
I've set the value to "C:\\\\", "////files" and after seeing intellisense complain that it expects an array, I tried those two values, separately, as a single element in the array.  In all cases, I get a "no such file" error.
I'm happy to poke at the code and submit a pull request, but thought I'd start here in case there was something obvious I'm doing wrong while configuring that.  I do not have $AWKPATH set, because these files are project specific and I don't want them in my system's AWKPATH
Any help is appreciated and thanks for the time and energy you've put into this!

This extension just does syntax highlighting in vscode, that's it. It doesn't run the scripts at all. I think your problem may be elsewhere, unless I misunderstand.

Apologies, I wasn't terribly clear, I'm finding.  What's happening is that the @include statement is showing up with a red squiggly and complaining that it can't find the referenced script.  The script is in the same folder as the awk script that is referencing it and the tools that use this awk script set the AWKPATH variable so that awk can find the script when I run it.
I had assumed that the awk.path configuration item would make vscode-awk extension find that path and eliminate the red error, but now that I'm thinking about it further, it's entirely possible that said configuration value is from another extension ... and based on what you're saying, it's possible that my red underline might be from a different extension.  If that's the case, my apologies!  I won't be able to confirm that until tomorrow since I left my work computer in the office.
Many thanks, anyway, for being one of the extensions I rely on!


refactor: reduce DB lock time by changing trait update logic

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[ ] I have added information to docs/ if required so people know about the feature!
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?
[ ] I have used a Conventional Commit title for this Pull Request

Changes
Instead of lock-update every time, it reads the data, compares the existing and incoming data, and only issues an update when the data actually changes. This strategy drastically reduces unnecessary UPDATE operations and consequently, the chances of lock contention.
Please describe.
How did you test this code?
Unit tests, manually

Please describe.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.86%. Comparing base (90e10cf) to head (ebc5271).
Report is 48 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #3594   +/-   ##
=======================================
  Coverage   95.86%   95.86%
=======================================
  Files        1097     1099    +2
  Lines       34140    34185   +45
=======================================
+ Hits        32727    32771   +44
- Misses       1413     1414    +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@cat5e-inv I also updated the title of the PR to fit our naming conventions.

@cat5e-inv , based on the discussion thread here and the (now released in v1.6.0) work in the kotlin client to expose the bulk traits functionality (See PRs here and here) I am going to close this PR as there are significant concerns about the behaviour that would result from this change.
If you strongly disagree with this, please let me know and we can discuss whether this change could be included but hidden behind some sort of switch perhaps.


fix(hl): use NormalFloat instead of Normal

[x] Have you read CONTRIBUTING.md?

I think NormalFloat is the one to highlight with since it's highlight inside a popup window. I have different backgrounds for a floating window and using Normal looks a bit weird.
Before:

After:

I see CI failed, but it is the same test failing as the one that failed on the latest master, so it's not related to this

What do you think? @lewis6991

Sorry, haven't had a chance to look into this yet. Very busy atm, but will try and get to this when I can

Totally understand!


Regression at commit f1dfe727966f42d6e4a2aa3e6304a4817444f3a7.

Commit f1dfe727966f42d6e4a2aa3e6304a4817444f3a7 cause skyrim main menu show like following.

Revert that commit will return to normal.

Thanks for the clear report. Was looking for some regression testing for that change. I will fix this today.

hm, I was not able to replicate, might be related to the other language you are using however


Online Resize

Hi,
I think you should update the docs to reflect the online resize possibilities:
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/expand-disks#expand-a-disk-partition-and-filesystem
You can change the partition while it's mounted, you may need to reload the partition table using partx or something similar. Also you should mention lvm, the rhel/centos images use that by default and you'd need to pvresize and then lvresize (with -r if you want to automatically run resize2fs)
Also most images use cloud-init -- so you can also use growpart as an abstraction (from cloud-utils-growpart-0.31-1.el8.noarch on rhel8).
Greetings
Klaas

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

ID: 06c61c5a-d9e4-742b-36e5-b9effa33d903
Version Independent ID: cb9dbd59-460d-a1a0-9863-5213d6a1093e
Content: Expand virtual hard disks on a Linux VM - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/expand-disks.md
Service: virtual-machines
Sub-service: disks
GitHub Login: @roygara
Microsoft Alias: rogarana

@Klaas- we'll review your feedback and get back to you shortly. Thanks.

@Klaas-
Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.

@roygara
Can you please check and add your comments on this doc update request as applicable.

#reassign: @ericd-mst-github

#reassign: roygara

@roygara you should also revisit some of my suggestions here since online resize is now GA, especially the growpart usage will make this process much easier.

Thank you @pagienge for applying some of my suggestions via https://github.com/MicrosoftDocs/azure-docs/commit/50b4557525d8dc65d89fb336c074d0f5b5585ed6


toJSON() is not a fuction for a complex object.

Hi, im using the great tool NSWAG with my angular4 app but having a problem with an object cast:

UPDATE: This error starts to occour when I updated from version "nswag": "^8.8.0" to version "nswag": "10.6.0"

In my C# Code i have this class:
 public class CreateTestDto
 {
          public string Name { get; set; }
          public TestDto Test { get; set; }
 }

public class TestDto
{
      public string Description { get; set; }
}`

Then in my Angular4 form Component:
  this.createTest= new CreateTestDto(<CreateTestDto>this.formTest.root.value);
  this.testService.create(this.createTest).subscribe();

The auto-generated nswag code (testService):
     create(createTest: CreateTestDto):  void {
        let url_ = this.baseUrl + "/api/services/CreateTest";
        url_ = url_.replace(/[?&]$/, "");

        const content_ = JSON.stringify(createTest? createTest.toJSON() : null);
      /// etc

On the create method it throws an error when it tries to execute createTest.toJSON(), saing:

this.test.toJSON is not a function.

It seems that when i cast to the createTest  object, only the CreateTestDto gets the __proto__ with the toJSON() method, but the inner TestDto property doesnt, it only maps the Description property and the __proto__ is of type Object.

The parameter of CreateTestDto is of type ICreateTestDto but the properties are not of the interface but require the correct instances, so you need to new ... them too... The properties are just copied into the new instance and thus must be of the correct type (cannot be POJOs)

Why it was working on ^8.8.0 version?

Ah, yes the behavior has changed, as a hack you can use
let x = new CreateTestDto();
x.init(<CreateTestDto>this.formTest.root.value);

but the expected parameter of init() (and the previous ctor) is not the POJO version of the class but the data of the server (i.e. the casing may be different, etc...)

I think this might interest you: https://github.com/RSuter/NJsonSchema/issues/494


Removed support for MRI ruby versions lower than 2.2

ditto

Coverage remained the same at 99.11% when pulling 6e038f91424cfa7068102ed2710838e5ad8ae400 on AlfonsoUceda:master into 4cbeb039a69722fc486c85fa384c2ebfdc546edc on lotus:master.

Coverage decreased (-1.37%) to 97.75% when pulling 6a2ce44d3d6f35bab62dbbfd20ed975bce3fa58c on AlfonsoUceda:master into 4cbeb039a69722fc486c85fa384c2ebfdc546edc on lotus:master.


use meshes from example-robot-data

update tests/baxter_simple.urdf to use meshes provided by example-robot-data instead of hpp-baxter.
This the unit tests in hpp-pinocchio, which depends on example-robot-data and not hpp-baxter:
7/9 Test #1: tconfiguration ...................***Failed    0.39 sec
Running 6 test cases...
unknown location(0): fatal error: in "difference_and_distance": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/tconfiguration.cc(174): last checkpoint: "difference_and_distance" test entry
unknown location(0): fatal error: in "difference_and_integrate": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/tconfiguration.cc(210): last checkpoint: "difference_and_integrate" test entry
unknown location(0): fatal error: in "interpolate_and_integrate": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/tconfiguration.cc(292): last checkpoint: "interpolate_and_integrate" test entry
unknown location(0): fatal error: in "saturation": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/tconfiguration.cc(367): last checkpoint: "saturation" test entry
unknown location(0): fatal error: in "successive_interpolation": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/tconfiguration.cc(401): last checkpoint: "successive_interpolation" test entry

*** 5 failures are detected in the test module "tdevice"

8/9 Test #2: device ...........................***Failed    0.55 sec
Running 4 test cases...
unknown location(0): fatal error: in "unit_test_device": std::invalid_argument: Mesh package://hpp-baxter/meshes/base/pedestal_link_collision.DAE could not be found.
../tests/device.cc(107): last checkpoint

*** 1 failure is detected in the test module "tframe"

It seems reasonable to me.


Feature_Request : Addding more footer classes

Is your feature request related to a problem? Please describe.
I would like to give a suggestion to add more footer classes.
Describe the solution you'd like
I would like to add footer class Explore: Write a review, Traveller's choice, Travel articles, add a Place, seasonal and holiday deals; under Support: How we work, safety resource center.
Describe alternatives you've considered
we may add Connect with us feature also as footer class  : Twitter, youtube, facebook. I thought we have footer classes currently: Support and  Adress  along with Tourguide. Adding more classes and making space even would make ui look more good.
Demo Video/Screenshot (Mandatory )

Are you contributing under any open-source program ?
JWOC'24

@TanushreeBorase You are assigned . you can start working on this issue


Java DTO generation for strict formats is assigning type 'Object' instead of expected type 'String'

Short term at least get the type to reprot as String (as happens for other languages - this is the bug referred to here). Longer term support for strict formats is highly desirable especially for types like dates - this is the enhancement referred to by https://github.com/asyncapi/modelina/issues/533.
Sample yaml:
asyncapi: 2.2.0
info:
title: Example
version: 0.1.0
servers:
production:
url: broker.mycompany.com
protocol: kafka
description: This is "My Company" broker.
qa:
url: broker.mycompany.com
protocol: kafka
description: This is "My Company" broker.
dev:
url: broker.mycompany.com
protocol: kafka
description: This is "My Company" broker.
channels:
user/signedup:
publish:
summary: "Say hello"
operationId: "onSayHello"
message:
$ref: '#/components/messages/hello-msg'
components:
messages:
hello-msg:
  name: "SayHello"
  title: "Say hello"
  description: "Message received when a hello event is raised"
  contentType: "application/json"

  tags:
    - name: "hi"
    - name: "hallo"
    - name: "hola"

  headers:
    type: "object"
    properties:
      correlationId:
        description: "Correlation id set by the application"
        type: string
      applicationInstanceId:
        description: "Unique identifier for a given instance of the publishing application"
        type: string

  payload:
    type: object
    $id: "SayHello"
    additionalProperties: false
    properties:
      name:
        type: string
      sentAt:
        $ref: '#/components/schemas/sent-at'

  correlationId:
    description: "Default correlation id"
    location: "$message.header#/correlationId"

  examples:
    - name: "SimpleSignup"
      summary: "A simple signup example message"
      headers:
        correlationId: "my-correlation-id"
        applicationInstanceId: "my-instance-id"
      payload:
        name: "Joe Borg"
        sentAt: "2020-12-17T09:00:00.000"

schemas:
sent-at:
type: string
description: The date and time a message was sent.
format: datetime
Observed result:

@reuben-tonna-ixaris for the java generator, it is actually already supported. The only problem you are phasing is that you are using the format datetime, when it should be date-time.
With this change, it generates the type java.time.OffsetDateTime. It reason it generates Object is that it is our backup type in case it encounters unrecognized types.
Gonna close this issue down, feel free to reopen if it is still not solved 🙂


Use /opt instead of /usr/local.

fixes #96

LGTM

@cedricziel FYI, php and nginx will be moved to /opt


Unable to install required version of NodeJS

Operating system and version:
Ubuntu 20.04
nvm debug output:

nvm --version: v0.39.1
$SHELL: /bin/bash
$SHLVL: 1
whoami: 'shreedhar'
${HOME}: /home/shreedhar
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)'
uname -a: 'Linux 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
OS version: Ubuntu 20.04.4 LTS
curl: /snap/bin/curl, curl 7.82.0 (x86_64-pc-linux-gnu) libcurl/7.82.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 zstd/1.4.4 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3 libgsasl/1.8.1 OpenLDAP/2.4.49
wget: /usr/bin/wget, GNU Wget 1.20.3 built on linux-gnu.
git: /usr/bin/git, git version 2.25.1
grep: /usr/bin/grep (grep --color=auto), grep (GNU grep) 3.4
awk: /usr/bin/awk, awk: not an option: --version
sed: /usr/bin/sed, sed (GNU sed) 4.7
cut: /usr/bin/cut, cut (GNU coreutils) 8.30
basename: /usr/bin/basename, basename (GNU coreutils) 8.30
rm: /usr/bin/rm, rm (GNU coreutils) 8.30
mkdir: /usr/bin/mkdir, mkdir (GNU coreutils) 8.30
xargs: /usr/bin/xargs, xargs (GNU findutils) 4.7.0
nvm current: system
which node: /usr/bin/node
which iojs:
which npm: /usr/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules

nvm ls output:

->       system
iojs -> N/A (default)
node -> stable (-> N/A) (default)
unstable -> N/A (default)
lts/* -> lts/gallium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.24.1 (-> N/A)
lts/erbium -> v12.22.12 (-> N/A)
lts/fermium -> v14.19.3 (-> N/A)
lts/gallium -> v16.15.0 (-> N/A)

How did you install nvm?

manually installed using scripts provided in Readme given here
What steps did you perform?

nvm install 16

What happened?

Downloading and installing node v16.15.0...
Downloading https://nodejs.org/dist/v16.15.0/node-v16.15.0-linux-x64.tar.xz...
Warning: Failed to create the file
Warning: /home/shreedhar/.nvm/.cache/bin/node-v16.15.0-linux-x64/node-v16.15.0-
Warning: linux-x64.tar.xz: Permission denied
curl: (23) Failure writing output to destination

Binary download from https://nodejs.org/dist/v16.15.0/node-v16.15.0-linux-x64.tar.xz failed, trying source.
grep: /home/shreedhar/.nvm/.cache/bin/node-v16.15.0-linux-x64/node-v16.15.0-linux-x64.tar.xz: No such file or directory
Provided file to checksum does not exist.
Binary download failed, trying source.
Detected that you have 8 CPU core(s)
Running with 7 threads to speed up the build
Downloading https://nodejs.org/dist/v16.15.0/node-v16.15.0.tar.xz...
Warning: Failed to create the file
Warning: /home/shreedhar/.nvm/.cache/src/node-v16.15.0/node-v16.15.0.tar.xz:
Warning: Permission denied
curl: (23) Failure writing output to destination

Binary download from https://nodejs.org/dist/v16.15.0/node-v16.15.0.tar.xz failed, trying source.
grep: /home/shreedhar/.nvm/.cache/src/node-v16.15.0/node-v16.15.0.tar.xz: No such file or directory
Provided file to checksum does not exist.

What did you expect to happen?
Supposed to install NodeJs version 16.
Is there anything in any of your profile files that modifies the PATH?

No

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

*   Trying <IP_ADDRESS>:443...
* Connected to nodejs.org (<IP_ADDRESS>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.nodejs.org
*  start date: Jan 11 00:00:00 2022 GMT
*  expire date: Feb 11 23:59:59 2023 GMT
*  subjectAltName: host "nodejs.org" matched cert's "nodejs.org"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* h2h3 [:method: HEAD]
* h2h3 [:path: /dist/]
* h2h3 [:scheme: https]
* h2h3 [:authority: nodejs.org]
* h2h3 [user-agent: curl/7.82.0]
* h2h3 [accept: */*]
* h2h3 [accept-encoding: deflate, gzip, br, zstd]
* Using Stream ID: 1 (easy handle 0x5569994be380)
> HEAD /dist/ HTTP/2
> Host: nodejs.org
> user-agent: curl/7.82.0
> accept: */*
> accept-encoding: deflate, gzip, br, zstd
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 200
HTTP/2 200
< date: Mon, 23 May 2022 08:40:29 GMT
date: Mon, 23 May 2022 08:40:29 GMT
< content-type: text/html
content-type: text/html
< last-modified: Mon, 23 May 2022 07:05:11 GMT
last-modified: Mon, 23 May 2022 07:05:11 GMT
< cache-control: max-age=14400
cache-control: max-age=14400
< cf-cache-status: HIT
cf-cache-status: HIT
< age: 5456
age: 5456
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< vary: Accept-Encoding
vary: Accept-Encoding
< server: cloudflare
server: cloudflare
< cf-ray: 70fc7cb1294c9fa4-SIN
cf-ray: 70fc7cb1294c9fa4-SIN
< content-encoding: br
content-encoding: br

<
* Connection #0 to host nodejs.org left intact

How did you install curl? I believe snap has a broken one.

See #2771

Thanks, @ljharb for helping. Actually, I have installed Curl using snap. Now changed to apt. #2771  worked for me. Closing the issue.


react_native_assert failure: link_.status != Status::Running && "Surface must not be running."

Description
I recently integrated React Native into my native Swift app, it worked normally with version 0.75.4
But I updated to React Native 0.76.3 to be able to use the new architecture.
After the update, when building, the app crashes with the error: "Surface must not be running".
Steps to reproduce
Integrate with existing Swift App following docs: https://reactnative.dev/docs/integration-with-existing-apps
Upgrade to React 0.76.3: https://react-native-community.github.io/upgrade-helper/?from=0.75.4&to=0.76.3

Clone project: https://github.com/L0NG4R3S/SurfaceErrorRepository
Run yarn start
yarn install && cd ios && pod install
yarn ios or open ReproducerApp.xcworkspace in xcode and run

React Native Version
0.76.3
Affected Platforms
Runtime - iOS
Areas
TurboModule - The New Native Module System
Output of npx react-native info
System:
  OS: macOS 15.1.1
  CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Memory: 227.51 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.7.3
    path: ~/.nvm/versions/node/v21.7.3/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.nvm/versions/node/v21.7.3/bin/yarn
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v21.7.3/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /usr/local/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.2 AI-232.10300.40.2321.11567975
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 16.0.0
    wanted: ^16.0.0
  react:
    installed: 19.0.0
    wanted: 19.0.0
  react-native:
    installed: 0.76.3
    wanted: 0.76.3
  react-native-macos:
    installed: 0.76.4
    wanted: ^0.76.4
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true

Stacktrace or Logs
WARNING: Logging before InitGoogleLogging() is written to STDERR
E1206 09:11:06.964253 89726976 SurfaceHandler.cpp:318] react_native_assert failure: link_.status != Status::Running && "Surface must not be running."
Assertion failed: (link_.status != Status::Running && "Surface must not be running."), function setUIManager, file SurfaceHandler.cpp, line 318.

Reproducer
https://github.com/L0NG4R3S/SurfaceErrorRepository
Screenshots and Videos

But I updated to React Native 0.76.3 to be able to use the new architecture.

I'd suggest you first update to 0.76.3 without the New Architecture and then enable it. Otherwise it will be hard to understand what is causing the failure

I met the same issue, perhaps react native can't support React 19 right now.
But I wonder if there is a roadmap when React Native can fully support React 19.


Feature: add notion and add community

Type of feature
🍕 Feature
Current behavior
I have created a notion page based on my conversation with @BekahHW
Here is the link for it: https://a0m0rajab.notion.site/100-Days-Of-Open-Source-2615e66772e14152897002e348c5f1bc?pvs=4
Plus, I was thinking that it would be nice to have a place where we can add the links to the repos/journals of people who joined the challenge where it would play as a showcase place for them, but I was not sure where should we add this?
It might be as a new total repo or within the highlights.
Suggested solution
No response
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[ ] I agree to follow this project's Contribution Docs

Hey, @a0m0rajab do you want to make a PR to add this into the #100Days docs


A Distilation version of PhoBERT

Hi, I am trying to get a distillation version of PhoBERT.
Is there any pre-trained of it or I have to train myself?
I found  available code to train a distillation versions of transformers-models from tranformers package.
Link: https://github.com/huggingface/transformers/tree/master/examples/research_projects/distillation
I tried, but it doesn't seem to work well with PhoBert, due to some differences in tokenizer.
Any guide for me here. Thanks in advance.

You have to train a distilled version of PhoBERT.
Note that PhoBERT is based on RoBERTa, thus you would need to apply examples w.r.t. RoBERTa distillation. Also, please do word segmentation in the data (e.g. dump.txt) before binarizing it, and when binarizing the data, please select the corresponding PhoBERT tokenizer.


vimPlugins.vim-move: Init at 2019-11-23

Motivation for this change
This is a useful vim plugin.
Things done

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

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

[x] Fits CONTRIBUTING.md.

Do you mind condensing this into #74940
and just knock them all out at once?

Do you mind condensing this into #74940
and just knock them all out at once?

Done.


ADC documentation options for PDG datasets: IWP & water/glacier mask

@ChandiWitharana and Elias, I’d like your opinions regarding how to archive the PDG data and metadata for the IWP and water/glacier clipped datasets. Elias processed the .shp files last week, and Kastan is running the workflow to stage, rasterize, and create the web tiles. We’re processing both these datasets in advance of NNA (prioritizing the IWP dataset), and we’ll have the .shp, .gpkg, and .tif data files archived on the Arctic Data Center.
Matt suggested 2 ways to archive the data:

Which option is best?
As I document each file type, I'll be checking in with you about metadata and authorship questions.

Data Processing Methods:

The water and glacier directory (described as the water and glacier mask in the schematic above) includes shapefiles for: 1) coastal water (to remove polygons that were incorrectly identified as IWP, when in reality it was sea ice) as well as 2) glaciers (to remove polygons that were incorrectly identified as IWP, when in reality it was a glacier). It does not include surface water such as lakes.
glacier shapefile
coastal water shapefile
The reason these files do not include surface water is because MAPLE's processing steps already masked out lakes before the coastal water and glacier mask was applied
Therefore the fully processed files (found on Delta: /scratch/bbki/kastanday/maple_data_xsede_bridges2/glacier_water_cleaned_shp/high_ice) have been cleaned for all 3 types of water (coastal, glaciers, and surface water)

To Do:

[ ] priority before NNA: archive the IWP data package on ADC
[ ] within the water and glacier mask data package on ADC, archive the inland water mask applied by MAPLE in addition to the coastal water and glacier mask used by Elias & team (retrieve this mask from the MAPLE workflow?)

Questions for PDG team
Please provide either answers or links to resources where I can find the following information:
High priority - IWP data

[ ] 1. overall temporal coverage of all processed IWP shapefiles (just year(s) will suffice, months & days are optional)

I can derive this from the shapefilefile names, since the year is included

[ ] 2. overall spatial coverage of all processed IWP files

Northwest and Southeast coordinates for bounding box, or describe the spatial coverage in whatever way is convenient and I'll work from that

[ ] 3. Will we include the term "high ice" in the metadata documentation? Or is this just a term used within the PDG team?
[ ] 4. Authorship information:

names
emails
ORCID's
specifically what data they contributed to (if not all the data types)

[ ] 5. Confirm units are correct for all data attributes

I will provide a link to the draft metadata documentation on ADC as soon as its cleaned up

[ ] 6. Review data package title, abstract, and methods draft

I will provide a link to the draft metadata documentation on ADC as soon as its cleaned up

[ ] 7. explanation for file naming template for shapefiles (example file: GE01_20190805214726_1050010017BFD700_19AUG05214726-M1BS-503537880070_01_P001_u16rf3413_pansh.shp)

this would be something like sensor_YYYYMMDD... and so on

Lower priority - coastal water and glacier mask, MAPLE inland water mask

[ ] 8. overall temporal and spatial coverage of all processed coastal water and glacier data (just year(s) will suffice, months & days are optional)

I found many water masks Elias mentioned he uploaded to Delta along with the shapefiles, in the folders with _water suffix, such as this one: /scratch/bbki/kastanday/maple_data_xsede_bridges2/glacier_water_cleaned_shp/high_ice/alaska/190_191_192_water/WV03_20200828223924_104001005E631B00_20AUG28223924-M1BS-504712637050_01_P001_u16rf3413_pansh/WV03_20200828223924_104001005E631B00_20AUG28223924-M1BS-504712637050_01_P001_u16rf3413_pansh_watermask.tif
some _watermask files are labeled as 2019 and some are 2020, so the temporal coverage for all water masks would be 2019-2020?

[ ] 9. overall temporal and spatial coverage of MAPLE inland water mask (if available?), this may be the same as the temporal/spatial coverage for coastal water and glacier mask and IWP data
[ ] 10. can we retrieve the surface water mask used in the MAPLE workflow?

Either options would be fine by me. I suggest you to implement most effective one. As per the description, it would be Option 2.

Generally temporal coverage of images could fall in between 2001 - 2021. But majority are post 2008 or 2010.
Spatial coverage of ALL processed files generally fall within Arctic Tundra region and confined to low-, medium, and high-ice areas within Tundra. These terms (high, low, medium ) are Brown et al. 1998

@ChandiWitharana Thank you for the feedback.
The Abstract and Methods were drafted for option 1, rather than option 2. We can split the package to go with option 2 if @mbjones thinks option 2 makes more sense as well. That would mean submitting 2 more tickets for a total of 3 repositories published by Monday.

Better we use this link (https://nsidc.org/data/ggd318/versions/2)
Brown, J., O. Ferrians, J. A. Heginbottom, and E. Melnikov. (2002). Circum-Arctic Map of Permafrost and Ground-Ice Conditions, Version 2 [Data Set]. Boulder, Colorado USA. National Snow and Ice Data Center. https://doi.org/10.7265/skbg-kf16. Date Accessed 12-08-2022.

From Anna:

For those attending the AGU both and a comment on the ImageryViewer and the IWP in general: Two permafrost science users have sent us some feedback on the IWP dataset in the public version of the ImageryViewer and they find it hard to assess the quality for the IWP dataset due to the poor resolution of the Bing imagery (and the simple fact that the background imagery in the ImageryViewer does not reflect the original Maxar imagery used in developing the IWP dataset). The Maxar license restrictions prevents us from showing the Maxar imagery to the public (can only be accesses/viewed by NSF Arctic funded researchers). So, two take-aways: 1) The meta-data of the IWP dataset need to contain statistics on the efficiency/accuracy of the algorithm. 2) We need to make it clear somewhere in the ImageryViewer that the background Bing imagery is not what was used to create the datasets shown in the ImageryViewer due to license restrictions of satellite imagery.

[ ] add statistics to metadata package about accruracy of IWP algorithm

⭐ Note ⭐ @julietcohen: @dvirlar2 pre-issued a DOI for the IWP dataset once it is published: doi:10.18739/A2KW57K57

@robyngit Thanks for the DOI. For now, I think we could manually configure the DOI to point at a manually-created landing page for the dataset. Once it is published in the ADC, the DOI would then be updated to point at the ADC landing page. Does that sounds reasonable?

Overview of package entity relationships, with the processing steps we associate with each:
flowchart LR
    A[A. Maxar]-->|MAPLE| B(B. IWP Shapefiles)
    B --> |Staging| C(C. IWP Geopackages)
    C --> |Rasterization| D(D. IWP Geotiffs)
    D --> |Web tiling| E[E. IWP PNGs]
    C --> |3dTiling| F(F. IWP 3DTiles)
    Note[Square boxes\n likely not\n to be archived]

From UConn side, the team would be:
Chandi Witharana (PI), Mahendra R. Udawalpola (Postdoc), Amal S. Perera (Postdoc), Amit Hasan (Graduate student), Elias Manos (Graduate student)

Location: Whats given is fine.

Metadata should be fine

Thanks @ChandiWitharana! What can we include to define what is meant by "high", "medium", and "low" ice regions?

Preliminary thoughts after viewing the latest version of the package:
Title, Abstract, and Keywords:

[ ] The title should include some mention that this is the "High Ice" portion of the IWP overall dataset.
[ ] I'd include an explanation of what "High Ice" means in the context of this dataset. I'd also provide the context of where that definition/delineation comes from (per Chandi's comment above).

[ ] In general I think it'd be a good idea to add a note that there are also medium and low ice versions of the data (and explain those meanings), that we're also planning on making public. Later when we do make those public, we can add links to direct links to them in the abstract, and assign the High Ice dataset can get a new doi at that point. Does that sound like reasonable to you @mbjones?

[ ] For keywords, I'd consider adding: CNN, Convolutional Neural Network, ice wedge polygons, and any others that might be relevant.

I have ideas for how to flesh out the methods section, but I'll get to that later when I have more time.

@dvirlar2 Thank you for the feedback 👍🏼
Regarding your first suggestion: The title does already include "high ice Arctic regions". Would you suggest wording it in a different way or is that sufficient?
Regarding your second suggestion: The Sampling section does already include a short description of what "high ice" means and mentions that there are also medium and low ice regions. "The geographic area sampled is the "high ice" regions of the Arctic, which are those the dataset authors identified to contain a relatively high proportion of ice. The study extent encompasses all high ice regions masked for coastal oceans, glaciers, and surface water. Further additions to this dataset will include "medium ice" and "low ice" regions of the Arctic as well. These regions were classified by less ice content." Perhaps this is not sufficient, or we could put it in a different section so it's more obvious?

I can move the high ice / medium ice / low ice descriptions from the Sampling section to the Abstract, since it seems that is what you are suggesting since that part is all you had time to review so far.

The high/med/low ice distinctions are not that critical - they essentially signal solely the order in which different spatial regions were processed. Its helpful for people to know that the spatial extent of the dataset will grow over time, but the results in each region are the same, and the divisions between the regions are pretty arbitrary.

Given my own confusion reading the dataset title earlier in this thread, and my experience of having a harder time distinguishing between datasets with very similar titles, I would recommend putting changing the title to something along the lines of

"High Ice: Ice wedge polygon detection in satellite imagery from Arctic regions, Permafrost Discovery Gateway, 2001-2021"

That way, the High, Medium, and Low distinctions are more immediately clear to users. Food for thought

List of Orcid IDs:

Elias Manos: https://orcid.org/0000-0002-7350-0116

Need to verify:

Amal S. Perera: https://orcid.org/0000-0003-3683-2098

Still need to include, if desired by person:

Mahendra R. Udawalpola

@dvirlar2 The plan is to update the dataset with new version releases to include all of the high, med, and low ice regions. And we plan to do that soon. So, I think the title should not include that distinction. A proposed title:

"Ice wedge polygon detection in satellite imagery from Pan-Arctic regions, Permafrost Discovery Gateway, 2001-2021"

The ORCiD Daphne suggested for Amal is correct

(1) explanation for file naming template for shapefiles,:
<Image type(P: panchromatic, M: multispectra><DG product type (1b: standard, 2A: georectified)>.shp
(2) What is the NSF award number? Such as "NSF Award 2240912" and any non-NSF funding info
NSF Award No: 1720875, 1722572, 1927872, 1927723, 1927729
(3) What are the ORCiD's for Mahendra R. Udawalpola and Amit Hasan?
Mahendra R. Udawalpola : 0000-0002-3521-1508
Amit Hasan : 0000-0001-8774-0228

@mbjones thank you for clarifying that! I got confused between this ticket and our meeting last week on how the datasets were going to be broken up. I agree with the title you proposed 👍🏽

I've added @julietcohen 's test version onto the production site. ADC people can view it here. I haven't checked yet who has access to the test version, but I can do that at a later date.
From a curation standpoint, I've:

changed the title per Matt's suggestion above to "Ice wedge polygon detection in satellite imagery from Pan-Arctic regions, Permafrost Discovery Gateway, 2001-2021"
edited the abstract to include the full link to where the data will live
Added the publisher information
Added the NSF awards
Added a discipline annotation to the dataset. I added cryology, but I'm contemplating adding data science and soil science. @mbjones , do you have any strong preferences on that?

To-Do:

@julietcohen: I didn't add the actual data object for the add_date_attribute_footprints.py file. Since the other objects are going to be dummy entities, I decided to only keep the metadata for all the files, the script included. If it should be added and immediately downloadable from the dataset landing page, and not where the rest of the data will live, let me know and I'll add it back!
Author List: From my outside perspective, I think the author list should include @mbjones, @robyngit, and @julietcohen for their roles in leadership and data processing. I'm not sure what role other people on the whole PDG group have played, but it would be good to have a discussion on authorship and to get other people's names and information listed before the deadline.

The following is the placeholder filename for the dummy shapefile in the package:
example_GE01_20110826213903_10504100013F3800_11AUG26213903_M1BS_054019163020_01_P001_u16rf3413_pansh.shp

After reading the structure provided by @amalshehan, I have a few questions:

Are there multiple sensors that were used? If so, we should document the acronyms and their meanings.
What's the difference between the acquisition and original timestamp? In the example above, the formats are different but the times are the same.
What's the difference between standard and georectified images? Would the average, "entry level" person interested in permafrost (but not satellites) know the differences?
What is the format for the original image ID? Do we know this?

Regarding Daphne's to-do items above:

The script add_date_attribute_footprints.py was written by me as a post-processing step, and this script should be archived either:

Wherever we archive the other post-processing materials from Chandi's team that are not already pointed to in the methods: the cleaning_data and water_mask directories.
or:
Uploaded to the PermafrostDiscoveryGateway/MAPLE_v3 repo

For the cleaning_data and water_mask directories: We already agreed to make a separate data package for the water masks, since it will likely be a helpful dataset for other purposes outside of the ice wedge polygon dataset post-processing. We haven't decided where to store cleaning_data. This can go in the same repository as the shapefiles, geopackages, and rasters, or it's own data package on the ADC.
I would also add Kastan Day to the list of dataset contributors (for the geopackages and rasters)

Regarding the discipline choices, let's ask @amalshehan and @ChandiWitharana review the proposal with a pointer to the ADCAD vocabulary for choices.

To Do for the IWP metadata package:

[ ] Give Anna Liljedahl access

she said she requested it from the ADC, ORCiD: 0000-0001-7114-6443)

[ ] Suggested by Anna: add the following people to "people and associated parties", and give them editing access if they don't already have it (we might have to find their ORCiD's):

Robyn Thiessen-bock
Matt Jones
Kastan Day
Juliet Cohen
Mikhail Kanevskiy<EMAIL_ADDRESS>Torre Jorgenson<EMAIL_ADDRESS>Howard Epstein<EMAIL_ADDRESS>Benjamin Jones<EMAIL_ADDRESS>Ronald Daanen<EMAIL_ADDRESS>

[ ] add these 2 awards, sent by Anna: 1927720, 2052107

Access to dataset added via ORCIDs:

[X] Anna Liljedahl: https://orcid.org/0000-0001-7114-6443
[X] Robyn Thiessen-bock (has access by default): http://orcid.org/0000-0002-1615-3963
[X] Matt Jones (has access by default): http://orcid.org/0000-0003-0077-4738
[ ] Kastan Day: Might be: https://orcid.org/0000-0002-1989-3406
[X] Juliet Cohen (has access by default): http://orcid.org/0000-0001-8217-4028
[X] Mikhail Kanevskiy: https://orcid.org/0000-0003-0565-0187
[X] Torre Jorgenson: https://orcid.org/0000-0002-9834-8851
[ ] Howard Epstein: Could not find
[X] Benjamin Jones: https://orcid.org/0000-0002-1517-4711
[ ] Ronald Daanen: Might be: https://orcid.org/0000-0001-7511-1491

I also added Chandi to the list of editors. His orcid is already in the dataset.

Thanks Daphne! I emailed Kastan to confirm that's his ORCiD.
You are correct about distinguishing between the Data Set Creator section and the "people and associated parties", sorry to cause confusion there.

ORCID Updates:

Howard confirmed the orcid listed above does belong to him. I can add access to the dataset later today

Kastan also confirmed that ORCiD listed above is his

The following is the placeholder filename for the dummy shapefile in the package: example_GE01_20110826213903_10504100013F3800_11AUG26213903_M1BS_054019163020_01_P001_u16rf3413_pansh.shp
After reading the structure provided by @amalshehan, I have a few questions:

Are there multiple sensors that were used? If so, we should document the acronyms and their meanings.
What's the difference between the acquisition and original timestamp? In the example above, the formats are different but the times are the same.

@dvirlar2 Based on my discussions with @ChandiWitharana we would like to point to PGC data docs for extra details on file naming as the original data was acquired from PGC and the names were maintained as is. If you think that we should document (archive) this I can respond to the specific details you request above.
The PGC data doc I am referring to are
PGC Commercial Satellite Imagery Documentation
PDF: PGC Commercial Satellite Imagery Documentation (umn.edu)

What's the difference between standard and georectified images? Would the average, "entry level" person / early career researcher interested in permafrost (but not satellites) know the differences?

Georectified images are corrected for any geometric distortions that may be present in the original/standard image due to the approach used to acquire the image.

What is the format for the original image ID? Do we know this? No

Regarding the discipline choices, let's ask @amalshehan and @ChandiWitharana review the proposal with a pointer to the ADCAD vocabulary for choices.

@dvirlar2,
Based on discussion with @ChandiWitharana we should add "Data Science" No need to add "Soil Science".
Good to also have Earth Science, Computer Vision, Geo AI, Big Data.

Should verify at some point how Torre Jorgenson wants to be identified in the dataset. Seems he goes by Torre among peers, but is professionally known as Mark. For now I'm putting him down as "M. Torre" in this dataset, and including information based on this recent dataset

Dataset has been finalized from my POV, and I've sent it to Matt and Juliet to review before sending off to others. Can view things here:
Also, I thought I had sent the Academic Ontology for the dataset annotations, but I see that I did not! @amalshehan For context, this ontology is where we pull our "dataset annotations" from. Earlier I had mentioned cryology, soil science, and data science as possible choices. I ended up going with data science and cryology based off of your earlier comments! Let me know if you have any questions 🙂

@julietcohen I rearranged the IWP dataset to streamline the directory structure as we discussed. Here's what I did, and the final file layout:
cd /var/data/10.18739/A2KW57K57/
cd iwp_geopackage_high/
mv staged/gpub020/WGS1984Quad .
mv staged/staging_summary.csv .
mv staged /var/data/submission/pdg/ice-wedge-polygon-data/
cd ../iwp_geotiff_high/
mv geotiff/WGS1984Quad .
mv geotiff/raster_events.csv .
mv geotiff/raster_summary.csv .
mv geotiff/raster_summary_duplicate.csv .
rmdir geotiff
cd ..
tree -L 2 .
.
├── cleaning_materials
│   ├── add_date_attribute_footprints.py
│   └── cleaning_data
├── iwp_geopackage_high
│   ├── staging_summary.csv
│   └── WGS1984Quad
├── iwp_geotiff_high
│   ├── raster_events.csv
│   ├── raster_summary.csv
│   ├── raster_summary_duplicate.csv
│   └── WGS1984Quad
├── iwp_shapefile_detections
│   ├── high
│   ├── low
│   └── medium
└── iwp_shapefile_footprints
    ├── high
    ├── low
    └── medium

I also revised the Mermaid diagram to reflect these changes, and worked a bit on the wording in that diagram:
flowchart LR

    A["Maxar <br> (satellite images)"] -->|MAPLE| B("`**/iwp_shapefile_detections/**
    Format: Shapefile
    Irregularly shaped vector files, one per image`")
    B -->|Create Tiles and <br> Identify Duplicates| C("`**/iwp_geopackage_high/**
    Format: GeoPackage
    Evenly-spaced vector tiles, with duplicates flagged`")
    C -->|Rasterize and remove <br> flagged duplicates| D("`**/iwp_geotiff_high/**
    Format: GeoTIFF
    Evenly-spaced raster tiles, with duplicates removed`")

Edits for next release:

[ ] Make the following change to the sampling description via R, not the web editor. For some reason the changes weren't being retained in the editor (will be filing a bug report about that, and will update this with a link). Sampling description should instead be: "Sampling procedures include collecting satellite imagery via the commercial satellite database at the Polar Geospatial Center, University of Minnesota."
[ ] Include funding from TTAC and ACCESS to represent the high performance computing resources that were used to create this dataset
[ ] Add descriptive entities to the test package for the four csvs listed above: staging_summary.csv, raster_events.csv, raster_summary.csv, raster_summary_duplicate.csv

[ ] copy metadata to production version when we're ready to update it

@dvirlar2 For the IWP mapping the HPC resources used are from TACC allocation DPP20001 and ACCESS allocation DPP190001. Do you need any other details such as the specific systems used?

Kenton provided the following to help fill in the ACCESS / TTAC grant info:
National Science Foundation - Leadership Resource Allocation (LRAC): Harnessing big satel-
lite imagery, deep learning, and high-performance computing resources to map pan-Arctic permafrost
thaw, 2020-2022, 94,000 GPU hours and 180 TB, 37.5 TB Tape on Frontera
National Science Foundation - ACCESS Explore: Permafrost Discovery Gateway Pan-Arctic
Dataset Creation, 2022-2023, 380,000 credits
And the new allocation info is:
National Science Foundation - ACCESS Discover: Permafrost Discovery Gateway Pan-Arctic
Dataset Creation, 2023-2024, 750,000 credits

More info from Kenton, the IBM acknowledgement:
**IBM-Illinois Discovery Accelerator Institute - Scaling Data-Intensive Discovery Workflows on
the Hybrid Cloud, 2021-2023
IBM-Illinois Discovery Accelerator Institute - HDC: A Full-Stack Solution for the Hybrid Cloud
Marrying Data and Compute, 2023-2025**

Thanks @amalshehan and @julietcohen! I think that's all the info I need, but I'll let you know if that changes.

Since this issue has been stagnant for some time, an update:
The "high" ice IWP dataset has been published (https://arcticdata.io/catalog/view/doi%3A10.18739%2FA2KW57K57) and the "low" and "medium" ice portions have been processed (run through the visualization workflow) but not archived at the ADC. All regions are visible on the PDG demo site.
Since one run on Delta processed the high ice (more than half the data), and the other run processed the low and medium ice, deduplication between those 2 tilesets was not executed. This is because the merging steps executes deduplication for gpkg files that were staged on different nodes. Because merging so many files takes days and depletes our Delta credits, it would be best to finish developing the kubernetes and parsl workflow to run on the NCEAS server (or another server, such as Google Cloud Platform) so we can take advantage of fast and powerful hardware without run time limitations, credit limitations, and memory limitations we experience on Delta.
Tickets to describe the progress of the kubernetes workflow are documented in the viz-workfow repo.


upgrade to support dbt-core v1.3.0

Background
The latest release cut for 1.3.0, dbt-core==1.3.0rc2 was published on October 3, 2022 (PyPI | Github). We are targeting releasing the official cut of 1.3.0 in time for the week of October 16 (in time for Coalesce conference).
We're trying to establish a following precedent w.r.t. minor versions:
Partner adapter maintainers release their adapter's minor version within four weeks of the initial RC being released. Given the delay on our side in notifying you, we'd like to set a target date of November 7 (four weeks from today) for maintainers to release their minor version

Timeframe
Date (intended)
Date (Actual)
Event

D - 3 weeks
Sep 21
Oct 10
dbt Labs informs maintainers of upcoming minor release

D - 2 weeks
Sep 28
Sep 28
core 1.3 RC is released

Day D
October 12
Oct 12
core 1.3 official is published

D + 2 weeks
October 26
Nov 7
dbt-adapter 1.3 is published

How to upgrade
https://github.com/dbt-labs/dbt-core/discussions/6011 is an open discussion with more detailed information, and https://github.com/dbt-labs/dbt-core/issues/6040 is for keeping track of the community's progress on releasing 1.2.0
Below is a checklist of work that would enable a successful 1.2.0 release of your adapter.

[ ] Python Models (if applicable)
[ ] Incremental Materialization: cleanup and standardization
[ ] More functional adapter tests to inherit

This issue has been decomposed into the following:
[FUTURE] dbt-core 1.3 upgrade: Support for python models
dbt-core 1.3 upgrade: New functional adapter tests
dbt-core 1.3 upgrade: Incremental mats: more standard and more error-proof
As such, marking as duplicate but leaving open until others are resolved (address or put on roadmap).


#ifdef FIPS_MODE in openssl 1.1.1 !?

diff --git a/crypto/evp/e_aes.c b/crypto/evp/e_aes.c
index 68322e1982..e60d736b9c 100644
--- a/crypto/evp/e_aes.c
+++ b/crypto/evp/e_aes.c
@@ -59,6 +59,12 @@ typedef struct {
const unsigned char iv[16]);
} EVP_AES_XTS_CTX;
+#ifdef FIPS_MODE
+static const int allow_insecure_decrypt = 0;
+#else
+static const int allow_insecure_decrypt = 1;
+#endif
+
typedef struct {
union {
double align;
=======
so far so good but this is not vendor validation
In openssl 1.1.1 FIPS is supported in vendor validation
So I cannot understand code like above in mainstream.
Please ensure correct retrofit (backport) of new functionality .

My mistake merging and not checkout the result closely enough.  I'll fix.

Fixed by #9255


Fix concurrency issue in DebugSections

The debug sections need to be running on the main thread, since they are updating the UI. We're experiencing the effects of this in Ridwell atm where the sections are not updating on change.

This issue is due to mutating the sections property on a background thread in the client code, not with the library.


Refactor MiqExpression#to_ruby CONTAINS

.operands2rubyvalue tries to generalize the problem of generating the "ruby" output for expressions, but in generalizing we lose some important knowledge of the system here: CONTAINS is the only operator that deals with tags. It seems better to me to move this code closer to the only thing that ever needs it.
@miq-bot add-label core, refactoring
@miq-bot assign @gtanzillo

👍


Added Hardik Gohil Portfolio

Portfolio Author

@HardikGohilHLR

Portfolio Link?

https://hardikgohilhlr.tech

GitHub Link:

NA

Tech Stack

Next.js, Firebase, SCSS, TypeScript

Awesome portfolio @HardikGohilHLR 💯 Thanks for adding!

Thanks 🙏🏻


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report

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

@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage        ?   96.59%
=======================================
  Files           ?        9
  Lines           ?      176
  Branches        ?       15
=======================================
  Hits            ?      170
  Misses          ?        6
  Partials        ?        0

Continue to review full report at Codecov.

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


CenterContainer children do not scale to parent

Godot version: 3.2
OS/device including version: Windows 10
Issue description: I have a CenterContainer and a TextureRect as a child to it. When I put both 'Fill' and 'Expand' to the CenterContainer, and mark the child to 'Expand' with 'Keep Aspect', the child ends up becoming a point on the screen. The reason I want this is because the image is actually too big for the screen. The way I fixed this (dirtily) was to replace the CenterContainer with a MarginContainer and set the TextureRect to 'Keep Aspect Centered'. I have attached images below as well as the project, with 2 scenes, one with the bug, called 'MainMenu-Bugged' and the other with the dirty fix. For more context, I was following this, but with a different aspect ratio: https://docs.godotengine.org/en/3.2/getting_started/step_by_step/ui_main_menu.html.
Disclaimer: I am still a beginner at Godot, hence it might be the case that I'm misunderstanding something.
The way I want it:

What happens when I used center container instead:

The project:
ui_main_menu_design.zip

You need to set a rect_min_size in the TextureRect if not it won't know how much space it should take

This is the expected behavior.
You can either untick the "extend" checkbox in the inspector, which will compute a minimum size out of the texture, making it 1:1 texture, or you can keep it this way and set a custom minimum size.

isn't the the definition of extend to take up as much room as it needs?


[request] Add support for actix_multipart's Field for SdkBody::from

Describe the feature
Add the ability to upload data directly to S3 from an actix_multipart Field via a new From trait implementation in SdkBody.
Use Case
Currently there's no obvious way to transfer data from a Field directly to S3 with the AWS Rust SDK. If we were able to do this, it would speed up file uploads by not requiring the file to be fully uploaded to the server as a temporary file before then being sent to S3.
Proposed Solution
Create a new impl for the From trait to allow a Field to be wrapped in an SdkBody. This could then be consumed from ByteStream, allowing for data to be passed through from the user agent to S3 without going through a local temporary file.
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

To do this, you can use SdkBody::from_dyn.
To do this, you'd need to do something like this:
// possibly some pinning required?
struct ActixWrapper(Field)

impl http_body::Body<Data=Bytes, E=Box<dyn Error + Send + Sync> for ActixWrapper {
  // use the `Stream` impl on `Field` to implement `data()` on `http_body::Body`
}

let sdk_body = SdkBody::from_dyn(ActixWrapper(field))


Converting "imgs_mask_test.npy" into image format

Hi Marko,
First of all, thanks for sharing your code in this repository. It has been really useful for the project I am doing: segmentation of skin lesions.
I have run all your code, and I already have the "imgs_mask_test.npy" file but I would like to convert this numpy array file into tiff/png/jpeg images. Do you have a code for doing that?
Thanks in advance.

You could iterate through that array and save each image on disk with imwrite() function. Both OpenCV and scikit-learn have this function, but you should look it up for more details.

Thanks for your quick reply, Marko!
Furthermore, when I create the .npy files with the function data.py, all of them (imgs_test, imgs_train, imgs_train_mask) are empty:
array([[[[0, 0, 0, ..., 0, 0, 0],
[0, 0, 0, ..., 0, 0, 0],
[0, 0, 0, ..., 0, 0, 0],
...,
[0, 0, 0, ..., 0, 0, 0],
[0, 0, 0, ..., 0, 0, 0],
[0, 0, 0, ..., 0, 0, 0]]],
What do you think about it?

I guess that you should rescale the masks from real [0,1] interval (because of the sigmoid activation) to discrete [0,255] integer interval before saving the image.

Thank you for your help.
Finally I am using this file to convert the numpy arrays into images.

import numpy as np
from scipy.misc import toimage, imsave
import os
in_dir = "imgs_train"
in_dir = "imgs_test"
in_dir = "imgs_mask_test"
in_dir = "imgs_mask_train"
images_to_convert_path = './' + in_dir + '.npy'
img_array = np.load(images_to_convert_path)
output_dir = 'binary_image'
these are the selected 'random' 5 images to test
names will be matched by index for now: 1=22, 2=234...
list_of_random_index = [1, 354, 453, 599, 844]
output directory
def ensure_directory_exist(directory_name):
exist_bool = os.path.isdir('./' + directory_name)
if not exist_bool:
os.mkdir(directory_name)
use this to show the image rather than save it, if you want
def show_image(image):
toimage(image).show()
save the image array to a .png file
def plot_image_save_to_file(name, img_cur):
#  ensure a directory is present/build if necessary
save_directory = output_dir  # from global value
ensure_directory_exist(save_directory)
#  build full path and save
file_name = name + '.png'
full_path = os.path.join(save_directory, file_name)
imsave(full_path, img_cur)

convert the numpy array to a int array through .astype('float32')
def convert_numpy_array_to_int_array(img_array):
print(len(img_array))   # will return number of pictures
image_list = []
i = 0
while i < len(img_array):
for photo_indiv in img_array[i]:
image = photo_indiv.astype('float32')
image_list.append(image)
# plot_image_save_to_file("jack", image)
# print(image)
i += 1
return image_list
loop through converted int array and save the image to .png
def convert_int_array_to_png(image_list):
ind_id = 1
for photo_array in image_list:
name = in_dir + '_' + str(ind_id)
plot_image_save_to_file(name, photo_array)
ind_id += 1
create a list of 5 int image array
def get_random_5(img_array_int):
mySet = set()
smaller_list = []
for selected_index in list_of_random_index:
    mySet.add(selected_index)

i = 0
while i < len(img_array_int):
    if i in mySet:
        smaller_list.append(img_array_int[i])
    i += 1

return smaller_list

wrapper to create 5 'random'(spec. gloablly) .png files to view binary mask
def convert_random_5(img_array_int):
smaller_list = get_random_5(img_array_int)
convert_int_array_to_png(smaller_list)
main wrapper
def main():
img_array_int = convert_numpy_array_to_int_array(img_array)
convert_random_5(img_array_int)  # TODO: make sure naming matches
# convert_all_images(img_array_int) # DONT RUN THIS
main()

Cool! Glad you had it worked out ;)

Hey, @iamrosmarin , for the above code by @jocicmarko , did you get the test_masks as images classified and localised correctly? Please let me know. After running the code, the got the imgs_mask_test.npy file. And i converted the .npy to png file.But the test_mask for every test image is shown the same. IS it due to the conversion to image or due to the error in train model?

Hi @MariyaBaby . As far as I know, your imgs_mask_test.npy file should include all numpy arrays of your test images. i.e. for 400 testing images the imgs_mask_test.npy would have 400 numpy arrays (matrices). So I bet you have some error in your train model. I can help you with your code if you want. Just contact me at<EMAIL_ADDRESS>. Cheers.

Hello @iamrosmarin can you explain why in the get_unet(), the merge([UpSampling2D]) is done,? The model why it is created with 10 layers? Can you please explain the model? Thank you so much in advance .. I'm just a beginner in CNN.

Also, @iamrosmarin , @jocicmarko  how's the evaluation done?

hi,thank you for your code.i ran your code ,but had a problem.i really need your help.the mistake is like this:
ValueError: 'arr' does not have a suitable array shape for any mode.

Hi, for me, to see the images in img_mask_test.npy as black and white image, I had to change the function:
convert the numpy array to a int array through .astype('float32')
def convert_numpy_array_to_int_array(img_array):
print(len(img_array))   # will return number of pictures
image_list = []
i = 0
while i < len(img_array):
for photo_indiv in img_array[i]:
image = photo_indiv.astype('float32')
image_list.append(image)
# plot_image_save_to_file("jack", image)
# print(image)
i += 1
return image_list
to:
convert the numpy array to a int array through .astype('float32')
def convert_numpy_array_to_int_array(img_array):
print(len(img_array))   # will return number of pictures
image_list = []
i = 0
while i < len(img_array):
for photo_indiv in img_array[i]:
image = photo_indiv.astype('float32')
image = image*255 # NOTE: for imgs_mask_test, the pixel value should be multiplied by 255
image_list.append(image)
# plot_image_save_to_file("jack", image)
# print(image)
i += 1
return image_list
Hope this help!

hi,  @conanhung .thank you for your code. i tried that,but also got a mistake like this:ValueError: 'arr' does not have a suitable array shape for any mode.do you know how to solve that?thank you!

Can you check if the input .npy is correct? How about its shape?
Also, try this code: https://github.com/conanhung/ultrasound-nerve-segmentation/blob/master/view_mask_test.py
To run the code, you have to install OpenCV 2 with python.

hi, @conanhung  Thank you for your help.I have checked that.The input .npy is (5308,2) which is not (5308,32,32,1)like your input.In fact,I want transform the ".csv" file that I get finally to "tif" or "jpg".Could you please share some code about that?eg,transform the "train_mask.csv"to "tif".

thanks a lot!do you know that how to transform the "train_masks.csv"that the competion offered to "train_mask.jpg"?is there any code to share?thank you very much~

@jocicmarko thanks a lot!do you know that how to transform the "train_masks.csv"that the competion offered to "train_mask.jpg"?is there any code to share?thank you very much~


Authenticator names are being mangled by minification

When using the ual-reactjs-renderer within an application that uses a minification build process, the names of the authenticators are getting mangled and corrupting the local storage value for UALLoggedInAuthType. The value saved in local storage ends up being the minified value (like n) and causes session persistence to break.
This is happening because it's currently using the constructor value which seems to be a valid target for mangling:
https://github.com/EOSIO/ual-reactjs-renderer/blob/0eaaf1ee9b7f941c92a12ee212e8bdcb8621e674/src/components/provider/UALProvider.js#L170
I discovered this bug while debugging why session persistence wasn't functioning within eoscostarica/eos-rate. This is a react-scripts application, which has built-in minification and mangling. If you log in using any authenticator on eosrate.io, you'll see the local storage value of UALLoggedInAuthType being set improperly and the session won't persist.
Perhaps authenticators need to implement a string value of their name which can be used, as opposed to using the constructor's name? I don't know the appropriate solution, but figured I'd raise the issue.

workaround for the minification issue.
assuming you want to know what wallet you are interacting with.
const lynx = new Lynx([exampleNet]);
const ledger = new Ledger([exampleNet]);
const scatter = new Scatter([exampleNet], { appName });
const anchor = new Anchor([exampleNet], { appName });
const tokenPocket = new TokenPocket([exampleNet]);

LynxUser.prototype.UalUserType = "LynxUser";
LedgerUser.prototype.UalUserType = "LedgerUser";
ScatterUser.prototype.UalUserType = "ScatterUser";
AnchorUser.prototype.UalUserType = "AnchorUser";
TokenPocketUser.prototype.UalUserType = "TokenPocketUser";

This was fixed in #95 and released in #96. Please upgrade to v0.3.0: https://www.npmjs.com/package/ual-reactjs-renderer/v/0.3.0

Unfortunately it doesn't look like this fixes the original issue. The new getName interface within 0.3.0 was a step towards a fix, but the usage of the authenticator.constructor.name pattern in these 3 places still caused the UALLoggedInAuthType to get mangled in production builds:
https://github.com/EOSIO/ual-reactjs-renderer/blob/3b78fd7dafbea19b9de95dffd38522a07e8341c7/src/components/provider/UALProvider.js#L169
https://github.com/EOSIO/ual-reactjs-renderer/blob/3b78fd7dafbea19b9de95dffd38522a07e8341c7/src/components/provider/UALProvider.js#L197
https://github.com/EOSIO/ual-reactjs-renderer/blob/3b78fd7dafbea19b9de95dffd38522a07e8341c7/src/components/provider/UALProvider.js#L279
I've submitted a PR which fixes these.

0.3.1 has now been released to fix this: https://www.npmjs.com/package/ual-reactjs-renderer/v/0.3.1

Fixed in #99


NullpointerException when running a query and the dataset is not found

Environment details

BigQuery
OS type and version: Mate Desktop Environment 1.20.1
Java version: Java 8
bigquery version(s): 1.16.0

Steps to reproduce

Running a query when the dataset is not found

Code example
      QueryJobConfiguration dmlQueryConfig = QueryJobConfiguration.newBuilder(dmlQuery).build();

      // Execute the query.
      TableResult result = bigquery.query(dmlQueryConfig);

Stack trace

Any additional information below

Following these steps guarantees the quickest resolution possible.
Thanks!

@emanuelbatista I tested many times with different version but not able reproduce that error which you are getting, and also could you please verify bigquery client version ? because you have mentioned above library version which does not exists in maven central.

@pmakani I have tested to the client 1.61.0. I have seen in the code where the error is thrown and it continues yet to the library's current version in this repository.

@emanuelbatista you can see below example and errors which i am getting when dataset is not exists. if i am doing wrong in below example, could you please provide an example or correct below example so i can reproduce that error ?
public class QueryExample {
  public static void main(String[] args) throws InterruptedException {
    String dmlQuery = "SELECT * FROM test_dataset_123.insert_rows";
    BigQuery bigQuery = BigQueryOptions.getDefaultInstance().getService();
    QueryJobConfiguration dmlQueryConfig = QueryJobConfiguration.newBuilder(dmlQuery).build();

    // Execute the query.
    TableResult result = bigQuery.query(dmlQueryConfig);
    result.iterateAll().forEach(val -> System.out.println(val));
  }
}

Exception in thread "main" com.google.cloud.bigquery.BigQueryException: Not found: Dataset project-xyz:test_dataset_123 was not found in location US
	at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.translate(HttpBigQueryRpc.java:106)
	at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.getQueryResults(HttpBigQueryRpc.java:586)
	at com.google.cloud.bigquery.BigQueryImpl$34.call(BigQueryImpl.java:1208)
	at com.google.cloud.bigquery.BigQueryImpl$34.call(BigQueryImpl.java:1203)
	at com.google.api.gax.retrying.DirectRetryingExecutor.submit(DirectRetryingExecutor.java:105)
	at com.google.cloud.RetryHelper.run(RetryHelper.java:76)
	at com.google.cloud.RetryHelper.runWithRetries(RetryHelper.java:50)
	at com.google.cloud.bigquery.BigQueryImpl.getQueryResults(BigQueryImpl.java:1202)
	at com.google.cloud.bigquery.BigQueryImpl.getQueryResults(BigQueryImpl.java:1186)
	at com.google.cloud.bigquery.Job$1.call(Job.java:329)
	at com.google.cloud.bigquery.Job$1.call(Job.java:326)
	at com.google.api.gax.retrying.DirectRetryingExecutor.submit(DirectRetryingExecutor.java:105)
	at com.google.cloud.RetryHelper.run(RetryHelper.java:76)
	at com.google.cloud.RetryHelper.poll(RetryHelper.java:64)
	at com.google.cloud.bigquery.Job.waitForQueryResults(Job.java:325)
	at com.google.cloud.bigquery.Job.getQueryResults(Job.java:291)
	at com.google.cloud.bigquery.BigQueryImpl.query(BigQueryImpl.java:1173)
	at com.qlogic.QueryExample.main(QueryExample.java:15)
Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException: 404 Not Found
GET https://www.googleapis.com/bigquery/v2/projects/project-xyz/queries/dcaa3caf-e55f-49ad-8e44-c5099fd5a3bc?location=US&maxResults=0
{
  "code" : 404,
  "errors" : [ {
    "domain" : "global",
    "message" : "Not found: Dataset project-xyz:test_dataset_123 was not found in location US",
    "reason" : "notFound"
  } ],
  "message" : "Not found: Dataset project-xyz:test_dataset_123 was not found in location US",
  "status" : "NOT_FOUND"
}
	at com.google.api.client.googleapis.json.GoogleJsonResponseException.from(GoogleJsonResponseException.java:150)
	at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:113)
	at com.google.api.client.googleapis.services.json.AbstractGoogleJsonClientRequest.newExceptionOnError(AbstractGoogleJsonClientRequest.java:40)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest$1.interceptResponse(AbstractGoogleClientRequest.java:444)
	at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:1108)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:542)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:475)
	at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:592)
	at com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.getQueryResults(HttpBigQueryRpc.java:584)
	... 16 more

@pmakani exactly the same way you made, but the behavior to running code was different for me.
When I had running, in com.google.cloud.bigquery.Job.getQueryResults(Job.java:291) wasn't thrown exception as you showed

However, in line 301(file com.goole.cloujd.bigquery.Job) , the function job.getStatus().getExecutionErros() is returning null and when it's inputed as null into  ImmutableList.copyOf is thrown NullPointException.
Another detail, the job.getError() is getting the same error that you described above.


Check and resolve security vulnerabilities in dependencies

Github automatically detected some security vulnerabilities in dependencies.
We need to check the issue and resolve them.

I think we need to determine how to handle the other security issues (https://github.com/cloud-barista/cb-operator/network/alerts) @jihoon-seo


vcs import fails when credentials are needed

Running vcs import with a config file that contains two or more repos that need either:

http login credentials
private key password

does not work as the prompts clobber each other.
Running 0.1.15 from PyPI

vcstool is currently not designed to provide stdin to any of the commands executed. Simply because I don't have a use case for this.
I am not sure how much effort it would be to implement support for user input. I would be happy to review a pull request for this.

Understood. Good to know this is expected behavior.
It is certainly not an easy problem. Just piping stdin in from the user wouldn't be exceptionally useful because you would still have to enter credentials for each repo every time.
For now I'll just change the way I authenticate on remotes.

I will mark this as "wontfix" since I don't intend to work on this. If someone can come up with a pull request implementing this somehow I would be more than happy to review and integrate it.


Android not tracking time spent in app

iOS when tracking pages seems to work correctly, telling me how long I spent in app; however, android tells me I spent 1s in app no matter how long I spent clicking through pages. Can you help?

Time spent on a page is calculated server-side, from one view event to the next:
https://matomo.org/faq/how-to/faq_21158/

No, as in it doesn't work :) not a question this is a bug! For android.

It works for me :tm: :sweat_smile:. Please share a minimal sample project to reproduce the bug.

I think the issue is that we use webviews inside the app, but the webviews are not registering as the same session. Any work around for this?

That's probably it. I'm not sure if you can set the same IDs between both. I have never tried that.
You could track manually tracking pageviews by hooking into WebView callbacks.

Yes, we've done that now, and this will allow us to capture time in app and also pages viewed; however, for more complex functionality like "clicks" and "errors seen" this will be too tricky for us to capture via webview callbacks without lots of work, so we were hoping to keep webview and app code separate but have them register as the same session in the Matamo UI.

That's not a use-case I've explored. You'd probably need to make sure the same IDs are used.
I'm not familiar with the JavaScript tracker. You'll have to dive into the code yourself.

Same Id's used, but registered as two different sessions. Thanks anyway - needs to be resolved in the future because this is one reason why we are moving all of our apps to firebase in the future, because they handle this use case.

This is probably due to https://github.com/matomo-org/matomo/issues/15593 - which should be fixed with the next version.

Ah yes, thank you, it's because of the "two sessions for a unique ID" that the app session (native pages) are registered as only being in the app for one second - if this is resolved then there potentially will be no issue, and we won't have to move to firebase!


autometrics doesn't pick up fastapi routes/handlers

I'm working on a fastapi sample app and have the folowing simple code:
from typing import Union

from fastapi import FastAPI
from autometrics.autometrics import autometrics
from prometheus_client import start_http_server

app = FastAPI()

@autometrics
@app.get("/")
async def read_root():
    do_something()
    return {"Hello": "World"}

start_http_server(8080)

# looking up this function in prometheus works
@autometrics
def do_something():
    print("done")

In this case do_something does get picked up by prometheus (running on 9090) but read_root does not. I don't know if its the chaining/order of the decorators. Changing the order of the decorators in the read_root actually breaks the handler.

This is resolved in the latest version of autometrics, pr


cgroupdriver has wrong default in package

Version: 1.11.3-2
The default cgroupdriver is being set to cgroupfs in the configuration provided by the rpm package. This should in fact be systemd per discussion with @mrunalp. Can we get this modified and rebuilt?
/cc @yuqi-zhang

@lsm5 This is for our rpm builds.

This change has been made on RHEL. I'm guessing we need the same thing on fedora as well?

@lsm5 Yes, we do.

ack, updating the cri-o modules now...

/cc @mike-nguyen

Let us know when this lands

Fixed.


Andrei's comment after review

@jbae11
Few very minor comment (probably, it's too late to make these changes, but consider it):

[ ] Please, consider add one sentence describing what kind of data is in UDB. Probably, it is obvious for experts, but I think it is a good place to mention range of burnup and enrichment to address Reviewer #1 concern. Anyway, try to inject enrichment and burnup range of your training set into the Abstract.
[x] p.3, line 29-30: You already introduced ORIGEN acronym in the Abstract. Do not do this second time.
[x] p.3, Table 1: first row, give it little bit more space.
[x] p.4, line 70: what is 'CLASS'? Give explanation or remove 'in the FCS CLASS' completely.
[x] p.7, lines 114-117: Either have dot in the end of each \item or remove it.
[ ] Table 4: Consider remove all vertical lines needed in this table.

thanks @andrewryh. I reflected the comments with the checkmarks. For the first point, I think the plot should explain the range of data in the UDB. For the last point, I think the vertical lines help separate the actual data (answer), and predictions

thanks @andrewryh. I reflected the comments with the checkmarks. For the first point, I think the plot should explain the range of data in the UDB.
THat is right, but explicitly mentioned in the text (Abstract) would address the reviewer #1 comment.
But the main issues is this: you CANNOR extrapolate results. So, you can make your prediction ONLY withing training set range (Bu 10-70; enrichment 2-5%).  Panelist on yesterday's AI panel mentioned this multiple times. I would state in discussion or conclusions this, and you will automatically drop out questions about export control (because you limit enrichment in the pickle file).

For the last point, I think the vertical lines help separate the actual data (answer), and predictions
Good idea; got it.