Build failed in ios while adding google plus

Hi,
I am using both Google plus and firebasex plugin in my project.
Two days before it was worked well.
But now it makes build issue in iOS.
There is no build error is not coming. Just saying failed to install cordova-plugin-firebasex like that.
please provide any suggestion regarding this.
Issue:
Failed to install 'cordova-plugin-firebasex': Error: pod: Command failed with exit code 1 Error output:
Cloning into '/var/folders/zw/0z5j9jrd0ps23m6bn9f93mbm0000gn/T/d20210213-1843-h7guz8'...
Note: switching to '8c5af96d5acebebdabd1752aae5baac52e948c1c'.
 You are in 'detached HEAD' state. You can look around, make experimental
 changes and commit them, and you can discard any commits you make in this
 state without impacting any branches by switching back to a branch.

 If you want to create a new branch to retain commits you create, you may
 do so (now or later) by using -c with the switch command. Example:

   git switch -c <new-branch-name>

 Or undo this operation with:

   git switch -

 Turn off this advice by setting config variable advice.detachedHead to false

downgrading cordova-plugin-googleplus to 8.5.0 works (Using GoogleUtilities (6.7.2)). Version 8.5.1 uses incompatible version of GoogleUtilities (7.2.2).
best regards

The Firebase v6 SDK for iOS implicitly uses GoogleUtilities v6.
This issue will be resolved by v12 of this plugin which will migrate to Firebase v7 SDK for iOS which uses GoogleUtilities v7.


 identified as three spaces

I don't quite understand why <ctrl-a> is identified to be three spaces.

Sorry this took so long to look into. I've drafted an initial fix. Once we've got a release out, I'll ping you to test and confirm it's gone.


metrics defined but never getting set

in collector/metrics.go several metrics are defined and exported but are never getting set
e.g., metrics_ttl and some of the metrics_repl_* metrics
/cc @dcu

also came across some others that are defined but never getting set in other files, don't remember off top of my head


 It's not obvious to me whether the corruption is due to a bug in x/image/draw itself, or in the compiler, runtime, and/or platform.
(CC @mengzhuo)

runtime.makeslice(0x1d6600, 0x11800000064, 0x11800000064)
	/tmp/workdir-host-linux-mipsle-mengzhuo/go/src/runtime/slice.go:103 +0x94 fp=0xc0000bb938 sp=0xc0000bb910 pc=0x71014

That argument is enormously large. It seems it should be 0x64. Maybe it is a compiler bug.

v9 (233) = Arg <int32> {dw} : dw[int32] (dw[int32])
...
v174 (234) = LoadReg <int32> v9 : F2
...
v321 (248) = Copy <int32> v174 : R1
v27 (+248) = MOVWreg <int> v321 : R1 (sources.len[int], sources.cap[int])
...
v234 (+248) = MOVVstore <mem> [16] v2 v27 v233
v180 (+248) = MOVVstore <mem> [24] v2 v27 v234
v30 (248) = CALLstatic <mem> {AuxCall{runtime.makeslice}} [32] v180

It is supposed to call makeslice with len/cap being dw with proper extension. The MOWWreg is supposed to do that. But it has an optimization that if the input is from a LoadReg with proper type, it should be already extended, so it won't extend again. Normally if the LoadReg is loaded into an integer register it is indeed properly extended. But in this case it is loaded into a floating point register (!) (due to another use as floating point) then moved to an integer register, which does not have the proper extension.

@cherrymui, I made a stab at updating the title based on your diagnosis. Does it look accurate? 😅

Thanks. Yeah, it looks right.


fix($rootScope, ngRepeat): accomodate objects resulting from Object.create(null)

Use Object.hasOwnProperty.call when iterating over properties of user-supplied objects.
Allow for objects not inheriting from Object.prototype.

If we want to support this, then the patch looks good, but every single time we change a function call to a call there is a performance implication. Given that this change is in code that is very hot, then I would like to know the opinion of other

If we decide that using call is too expensive, we should definitely update documentation to make it clear that users are expected to supply a hasOwnProperty property for any object watched in scopes or iterated over by ngRepeat.

Hi @HandyAndyShortStack I think something needs to be done. The main issue is that the two places that this PR modifies are super critical, and a minor change can have a big performance change.
Once again, if objects without a prototype are going to be supported, then this looks like the right fix, I just would like other opinions

@petebacondarwin landed a commit which implements this for ngRepeat (https://github.com/angular/angular.js/commit/7ea2c7f36ef854391df3f6b127ad42a2d5cbf1a3), but the didn't land the change for $rootScope(which was also in https://github.com/angular/angular.js/pull/9964.
Afaik, the code in ngRepeat isn't actually that hot, as it is only used for objects. But putting it in the rootScope code is probably a bad idea.

@Narretz, I think @petebacondarwin landed it separately in 20fb626.
Closing as duplicate of #9964 (which has already been "taken care of").

I felt that it was worth the performance impact.


Configuration reload

Closes: #1117
Description

[x] Add ability to parse the configuration from disk at runtime
[x] Perform a diff from the currently loaded configuration and the new one
[x] Spawn or shutdown the appropriate workers based on the configuration changes
[x] Hook up the SIGHUP signal to trigger a config reload
[x] Hook up the SIGUSR1 signal to dump the supervisor state to the console
[x] Fix bug where the client worker for the counterparty client is not spawned when a chain is added

Manual test notes:
https://gist.github.com/ancazamfir/1ece9dadadc4eba70f12add103fc6c93

For contributor use:

[x] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

CI is failing because of this minor security advisory, will fix it by upgrading to prost 0.8 in an another PR.


Camera and Display in one stream

Hi Pedro, how are you? Thanks for the awesome library
I got a question. Is the any way we can combine camera and display in one stream?
Something like this:

Thank you very much

Yes, you can do it using SurfaceFilter. Similar to this but replace MediaPayer with Camera1Manager:
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/blob/master/app/src/main/java/com/pedro/rtpstreamer/openglexample/OpenGlRtmpActivity.java#L260

@pedroSG94 Great. Thank you!


Small typo

[Enter feedback here]
Small typo on
https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-endpoint-api-v2#frequently-asked-questions
.....enable syncing groups larger than 50K withuot any additional configuration......

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

 Thanks.

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

#please-close


10.0.19045.4355 Missing Update?

Current WIN10 Pro is running 10.0.19045.4355 described as 22H2 Technical Preview. Is this the same update as 10.0.19041.4355?
Thank you to all the coders making this project available to support small home GNU FOSS personal networks of devices which occasionally need to help the MS Windows users with an issue.  Cheers

The Windows version is not usually the same as the version of the termsrv.dll -- RDPConf.exe will give you the version of the termsrv.dll that it finds (the one in the normal Windows installation location).  If you have extra copies of termsrv.dll in your path (very unlikely), then it might report on the wrong one.

Thank you, that informed my confusion.  Indeed Win10 OS version 10.0.19045.4355 uses the 10.0.19041.4355 termsrv.dll.
I notice that the basic update.bat file doesn't update the rdpwrapp.ini file. I also downloaded and used the latest rdpwrap autoupdate.bat program, also found here on github.  Everything is now working as expected.

SOLVED


MAC address not saved when modifying a multimedia center

Bug report
Describe the bug
Here is a clear and concise description of what the problem is:

In order to use WOL from my smartphone (OnePlus + LineageOS), I modified an existing but offline multimedia center (MC) by adding its MAC address. Once done, the only options was "Cancel" or "Test". Then I tapped on "Test", which obviously returned an error (as offline).
Then I switched on the MC, went back into "Modify" in Kore for this MC, and saw that the MAC address was not set.
Setup again -> "Test" -> test ok -> but WOL was not functioning.
"Modify" again -> MAC address not set !
Expected Behavior
Here is a clear and concise description of what was expected to happen:

Once the MAC address is set, either offline or online, the MC settings on Kore should be kept.
Actual Behavior

The MAC address is not saved when manually modifying an existing MC.
Possible Fix

Here is a workaround : modifying the name of the MC AND the MAC address fixed the issue.
To Reproduce
Steps to reproduce the behavior:

Add an MC with automatic setting
Modify the MAC address and validate
Go back to "Modify" the MC

Debuglog

The debuglog can be found here:
Screenshots
Here are some links or screenshots to help explain the problem:

Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:

WOL was not working, while the MC was accepting the wake up from other remote software.
Your Environment
Used Operating system:

Mobile device: OnePlus A5000
Android version: v11 (LineageOS)
Kodi version and platform:  v19.3
Kore version: v2.5.3

note: Once the issue is made we require you to update it with new information or Kodi versions should that be required.
Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.

When the Media center is offline, any changes made aren't saved, as they couldn't be checked. That includes the Mac Address.
When the MC is online and you specify a valid Mac Address, it is saved correctly (just tested). Wether it can be used to WoL is another thing, as the MC might not respond to the WoL packed.
When no Mac Address is specified, it currently can't be obtained automatically, given Android's security restrictions, so for WoL to work you need to manually specify the Mac Address, in an online MC.


Overlaying datashader legends on timeseries plots

Is there a way to overlay a legend plot like the ones from this User Guide - Multidimensional plots section. What happens right now is that when you overlay the legend on the timeseries plot you lose the automatic handling of the datetime x axis
I thought it was because the points being used for the column were 0,0 and maybe passing them as the first point of the curve I'm trying to plot would work but I get the following error:
DataError: None of the available storage backends were able to support the supplied data format.

I used something like this
def multitimeplot(pts, y):
    lines = {i: hv.Curve(pts_d[pts[i]], 'timestamp',  y) for i in range(len(pts))}
    overlay = dynspread(datashade(hv.NdOverlay(lines, kdims='k'), aggregator=ds.count_cat('k')))

    color_key = list(enumerate(Sets1to3[0:len(pts)]))
    color_points = hv.NdOverlay({pts[k]: hv.Points(list(pts_d[pts[k]].head(1)[['timestamp', y]].values[0]),
                                                  label=str(pts[k])).opts(style=dict(color=v)) for k, v in color_key})

    return color_points * overlay

@philippjfr @jbednar Any thoughts on this?

We really do need to get some proper legend and colorbar support for datashader plots; it's way overdue (like so many other things...).  But I think you're on the right track here; the fake points that are overlaid need to be valid points for this plot.  Maybe just debug it by trying to overlay a single Point somewhere clearly visible; once that works the NdOverlay of points should be a tiny step from there.

I got this to work with the following code:
hvObj *= hv.NdOverlay({k: hv.Scatter(data_df.head(1), kdims='time', vdims=y, label=str(k)).opts(
    style=dict(color=cmap[i])) for i, k in enumerate(signal_names)})

Used Scatter in place of Points
Selected the first row of my dataset to provide an existing point

This is based on my data structure where

hvObj contains several overlayed datashader objects
data_df is a pandas dataframe containing the raw data and a column containing pd.date_range
cmap is a list of colours
signal_names is a list of strings (legends)


amdgpu crash in new linux kernels slice 5.14.5+

Software information
As far as I understand, all games with dx11 support, while problems with dx9 are not necessary.
What games are currently breaking my system:
Kenshi - In the choice, if I specify my video card with the RadV driver and this will fix the problem, in other cases it writes "Unknown AMD GPU" and the driver kills my system.
Saints Row the Third - Breaks the system
Nier Automata - Breaks the system, but you can select the RadV driver here, although that doesn't fix anything.
Warframe - There were problems for a while, but it fixed on its own
LoL - Fixed on its own.
System information

GPU: Vega 8 in Ryzen 5700U
Driver: Mesa from 20.x.x to 21.2.6
Wine version: 6.19-6.23, lutris version slice 6.0 to 6.21-3(all of builds fshack,GE, protonified)
DXVK version: 1.8.x - 1.9.2
Kernel: 5.14.5+ Before version 5.14.5 there were no problems, now system crash in 5.15.6 version
WM: Sway + Xwayland, In i3/Plasma same problems
System: VoidLinux/ArchLinux same problems

Apitrace file(s)

Put a link here
https://pastebin.com/jCN8jEJU
https://pastebin.com/ePAtQHJ3

I cannot provide dmesg logs because my system freezes and the screen goes blank when I launch the application. I'll try to find a way to capture it somehow soon.
There are no problems in the 5.13.x kernel and now I am using it.

Okay, I found how to fix this problem and realized that it was more likely an amdvlk problem than dxvk. How to make sure nothing dies:
Specify at startup variables for changing the driver to RADV
AMD_VULKAN_ICD = "RADV" VK_ICD_FILENAMES = "/ usr / share / vulkan / icd.d / radeon_icd.i686.json: /usr/share/vulkan/icd.d/radeon_icd.x86_64.json"
The first is needed in order to explicitly say that the settings for RADV are used, the second is needed if (as it was for me), the first did not work.


XML ordering for IndexedEndpoints

Even though XML is an unordered data format we've seen clients rely on explicit ordering for AssertionConsumerService when choosing how they'll respond.
Refine https://github.com/ausaccessfed/saml-service/blob/develop/lib/metadata/saml.rb to sort all IndexedEndpoints by index - https://github.com/ausaccessfed/saml-service/blob/develop/app/models/indexed_endpoint.rb#L7 before outputting them to XML.

Shaun: Sort by [index, id] and knock uncertainty out of it permanently
^ Applicable to duplicate index values for different endpoints/bindings.

Closed by #152


DOC-FIX alluxio\docs\cn\Remote-Logging.md

DOC-FIX alluxio\docs\cn\Remote-Logging.md
2017-10-04-JiangXiNJU

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17098/
Test PASSed.

I have already fixed pull request title

LGTM


[SWP] attempt to remove a workaround for a triton llvm codegen bug

Triton LLVM codegen has a bug where local_loads from #shared to than the mma tile. Remove the workaround.
See https://github.com/triton-lang/triton/pull/3561.
Test case: https://pastebin.com/xxP3cFmy (test.mlir)
Output from running lowering: https://pastebin.com/zyGEenbF
triton-opt test.mlir -tritongpu-pipeline=num-stages=3 --convert-scf-to-cf  --allocate-shared-memory --convert-triton-gpu-to-llvm

@jlebar I am not sure if I am checking the failure correctly, I tried running
triton-opt test.mlir -tritongpu-pipeline=num-stages=3 --convert-scf-to-cf --allocate-shared-memory --convert-triton-gpu-to-llvm
but didn't hit any issue. From https://github.com/triton-lang/triton/pull/3549, sounds like we should hit an assertion.
Thanks!
CC @pawelszczerbuk

From https://github.com/triton-lang/triton/pull/3549, sounds like we should hit an assertion.

I believe that assertion was removed by @Jokeren when he fixed the relevant codepath.

One of our recent PRs may have fixed this problem. Do you have a test case BTW? If so, happy to dig deeper

I am using dont_pipeline_128x1  from test/TritonGPU/loop-pipeline.mlir (https://pastebin.com/xxP3cFmy), if we remove the HACK from the compiler, we will start pipelining the load in the test case, which should trigger the issue of invalid code for local_loads from #shared to #mma layout if the loaded shape is smaller than the mma tile.

I am using dont_pipeline_128x1 from test/TritonGPU/loop-pipeline.mlir (https://pastebin.com/xxP3cFmy), if we remove the HACK from the compiler, we will start pipelining the load in the test case, which should trigger the issue of invalid code for local_loads from #shared to #mma layout if the loaded shape is smaller than the mma tile.

To confirm, are you saying that the bug is triggered at the following IR?
%161 = triton_gpu.convert_layout %151 : tensor<128x1xi32, #blocked> -> tensor<128x1xi32, #mma>

Honestly I'm not sure if constructing an MMA layout greater than the tensor size makes sense?
In theory we could repeat values in registers and threads. Would like to get your thoughts

I am using dont_pipeline_128x1 from test/TritonGPU/loop-pipeline.mlir (https://pastebin.com/xxP3cFmy), if we remove the HACK from the compiler, we will start pipelining the load in the test case, which should trigger the issue of invalid code for local_loads from #shared to #mma layout if the loaded shape is smaller than the mma tile.

To confirm, are you saying that the bug is triggered at the following IR?
%161 = triton_gpu.convert_layout %151 : tensor<128x1xi32, #blocked> -> tensor<128x1xi32, #mma>

https://pastebin.com/eN5HP8XW has the mlir after SWP, if we pipeline the load.
Specifically, this op should trigger the issue
%14 = triton_gpu.local_load %arg5 : !tt.memdesc<128x1xi32, #shared, #triton_gpu.shared_memory, mutable> -> tensor<128x1xi32, #mma>
#mma = #triton_gpu.nvidia_mma<{versionMajor = 2, versionMinor = 0, warpsPerCTA = [4, 1], instrShape = [16, 8]}>
i.e loading a 128x1 tensor for an MMAv2 dot with tile {16,8} is bad because 1 < 8
This is how I understand it from the comments :]

https://github.com/triton-lang/triton/pull/4798
@manman-ren


Add docs for default column values

Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[X] Other (Docs)

Description
This PR adds documentation for default column values for Delta lake added in https://github.com/delta-io/delta/pull/2210.
How was this patch tested?
Docs-only changes.
Does this PR introduce any user-facing changes?
No.

cc @vkorukanti @scottsand-db

Thanks @vkorukanti for your review, please take another look!

lgtm, just one remaining comment

do we need to add a link in https://docs.delta.io/latest/delta-batch.html#create-a-table?

Given this feature is one of those the user can enable when creating a table, having a link or move the content to there helps keep the related content together?

lgtm, just one remaining comment
do we need to add a link in https://docs.delta.io/latest/delta-batch.html#create-a-table?
Given this feature is one of those the user can enable when creating a table, having a link or move the content to there helps keep the related content together?

@vkorukanti Sure, this is done.


Error: GetVersion: Memory access out of bounds

Hello, can you tell me how to fix this error?
Error: GetVersion: Memory access out of bounds
in _UtilsSQLite.getVersion (utils-sqlite.ts:99:29)

@gymprogressive Can you give a bit more explanation on your context (use of jeep-sqlite in browser alone or with @capacitor-community/sqlite). Can you share your example as i cannot reproduce the error

I have the same problem after upgrading from 2.6.3 to 2.7.2.
I get this in browser with @capacitor-community/sqlite 5.7.4 and douring SQLiteDBConnection.open().
It's the same code, only update the dependencies.

@scope-li can you give me a full example so i can test it easily and fix it

@jepiqueau
https://github.com/scope-li/reproducer-jeep-sqlite
Run it with ng serve and you will get the following error on page load:
Error: GetVersion: memory access out of bounds
    at _UtilsSQLite.<anonymous> (jeep-sqlite.entry.js:3899:35)
    at Generator.next (<anonymous>)
    at chunk-ATPMZF2Q.js?v=bc2d8fea:59:61
    at new ZoneAwarePromise (zone.js:2662:25)
    at __async (chunk-ATPMZF2Q.js?v=bc2d8fea:43:10)
    at _UtilsSQLite.getVersion (jeep-sqlite.entry.js:3883:33)
    at Database.<anonymous> (jeep-sqlite.entry.js:5577:56)
    at Generator.next (<anonymous>)
    at fulfilled (chunk-ATPMZF2Q.js?v=bc2d8fea:46:24)
    at _ZoneDelegate.invoke (zone.js:365:28)

@scope-li
I just ran your reproduction repo. To fix the issue, simply update the src/assets/sql-wasm.wasm file by copying the version from node_modules/sql.js/dist/sql-wasm.wasm rebuild and that's all!
For every update from this package, always try this solution first.

Yes, thats solve the problem. Sorry, I forgot the replace of sql-wasm.wasm.
Thanks for your support!

@Yizack @scope-li i am travelling, thanks to provide this advice which solves the issue


Crashing bug on Android Emulator

Steps to reproduce

Check out https://github.com/domesticmouse/codelabs/tree/95bd5ab0c0a1279fcfaa05a1988f5b00161796c7/generate_crossword/step_10
Start Android Emulator, e.g. Pixel 7A Android 14 (API level 34)
Run app

Expected results
App runs
Actual results
App crashes
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
$ flutter run
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
Running Gradle task 'assembleDebug'...                             46.7s
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app-debug.apk...          579ms
Syncing files to device sdk gphone64 arm64...                      105ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

Flutter Doctor output
Doctor output
$ flutter doctor -v
[✓] Flutter (Channel beta, 3.21.0-1.0.pre.2, on macOS 14.4.1 23E224 darwin-arm64, locale en)
    • Flutter version 3.21.0-1.0.pre.2 on channel beta at /Users/brettmorgan/flutter
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision c398442c35 (2 weeks ago), 2024-03-12 22:26:24 -0700
    • Engine revision 0d4f78c952
    • Dart version 3.4.0 (build 3.4.0-190.1.beta)
    • DevTools version 2.33.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/brettmorgan/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.15.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.9+0-17.0.9b1087.7-11185874)

[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 77.0.1
    • Dart plugin version 233.13135.65

[✓] VS Code (version 1.87.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.84.0

[✓] Connected device (4 available)
    • sdk gphone64 arm64 (mobile)     • emulator-5554         • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 14.4.1 23E224 darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 14.4.1 23E224 darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome 123.0.6312.87

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Note, this app does not crash under Flutter 3.19.5 / Dart 3.3.3

Hey Brett! I have been investigating emulator stability in general for the engine and I'd be happy to take a look tomorrow.

Reverting the Runners to code generated by Flutter 3.19.5 - https://github.com/flutter/codelabs/commit/447e2bc18be182015878f94c8193b80701da36d1 - is sufficient for this code to not crash under Flutter 3.21.0-1.0.pre.2 on Android Emulator

Hey Brett! I have been investigating emulator stability in general for the engine and I'd be happy to take a look tomorrow.

Let me know what else I can do to help here. Not having my codelabs crash under Flutter 3.21 would be really neat =)

@domesticmouse Chatted with @jonahwilliams, it's not very obvious but this is a Dart VM crash:

F/libc    ( 7066): Fatal signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0x6f0000006e in tid 7241 (DartWorker), pid 7066 (erate_crossword)

DartWorker is the Dart GC thread. If you're wondering how you have learned this yourself ... it's sort of hard - you can get symbols from a local engine builds or by using the symbolizer bot tool.
Marking P1 and dependency: dart to have the VM team take a look. Thanks for flagging!

  Did not see the crash on any of the arm64 and x64 emulator configurations that I tried.

I tried running it again to see if it was just a flake, but it repro'd for me.
➜  step_10 git:(95bd5ab0) flutter run
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
Running Gradle task 'assembleDebug'...                             31.2s
✓  Built build/app/outputs/flutter-apk/app-debug.apk.
Installing build/app/outputs/flutter-apk/app-debug.apk...        1,511ms
Syncing files to device sdk gphone64 arm64...                      316ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on sdk gphone64 arm64 is available at: http://<IP_ADDRESS>:52450/j0oXfgiv4G4=/
The Flutter DevTools debugger and profiler on sdk gphone64 arm64 is available at:
http://<IP_ADDRESS>:9103?uri=http://<IP_ADDRESS>:52450/j0oXfgiv4G4=/
D/EGL_emulation( 9738): app_time_stats: avg=83.50ms min=4.50ms max=552.73ms count=18
D/EGL_emulation( 9738): app_time_stats: avg=41.85ms min=6.29ms max=341.82ms count=26
D/EGL_emulation( 9738): app_time_stats: avg=26.85ms min=8.15ms max=168.51ms count=42
D/EGL_emulation( 9738): app_time_stats: avg=22.23ms min=2.86ms max=161.91ms count=41
D/EGL_emulation( 9738): app_time_stats: avg=29.80ms min=4.14ms max=166.62ms count=33
D/EGL_emulation( 9738): app_time_stats: avg=19.36ms min=2.00ms max=116.74ms count=42
D/EGL_emulation( 9738): app_time_stats: avg=24.61ms min=7.23ms max=134.08ms count=41
D/EGL_emulation( 9738): app_time_stats: avg=13.19ms min=2.11ms max=77.97ms count=52
D/EGL_emulation( 9738): app_time_stats: avg=14.74ms min=1.57ms max=89.72ms count=52
D/EGL_emulation( 9738): app_time_stats: avg=18.65ms min=2.39ms max=84.79ms count=53
D/EGL_emulation( 9738): app_time_stats: avg=14.80ms min=1.62ms max=81.86ms count=51
D/EGL_emulation( 9738): app_time_stats: avg=21.09ms min=1.90ms max=299.01ms count=51
D/EGL_emulation( 9738): app_time_stats: avg=14.48ms min=1.71ms max=181.21ms count=50
D/EGL_emulation( 9738): app_time_stats: avg=19.40ms min=1.77ms max=196.74ms count=46
D/EGL_emulation( 9738): app_time_stats: avg=15.32ms min=1.72ms max=265.07ms count=50
F/libc    ( 9738): Fatal signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0x6f0000006e in tid 9936 (DartWorker), pid 9738 (erate_crossword)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/sdk_gphone64_arm64/emu64a:14/UE1A.230829.036/11036701:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2024-03-30 07:30:18.154585994+1100
Process uptime: 20s
Cmdline: com.example.generate_crossword
pid: 9738, tid: 9936, name: DartWorker  >>> com.example.generate_crossword <<<
uid: 10191
tagged_addr_ctrl:<PHONE_NUMBER>000001 (PR_TAGGED_ADDR_ENABLE)
pac_enabled_keys:<PHONE_NUMBER>00000f (PR_PAC_APIAKEY, PR_PAC_APIBKEY, PR_PAC_APDAKEY, PR_PAC_APDBKEY)
signal 7 (SIGBUS), code 1 (BUS_ADRALN), fault addr 0x0000006f0000006e
    x0<PHONE_NUMBER>000004  x1  0000006f0000006e  x2  0000006f09880088  x3  0000006f09a80088
    x4<PHONE_NUMBER>000000  x5  00000073f2529084  x6  00000000ffffffff  x7  000122f10001b04b
    x8<PHONE_NUMBER>000001  x9<PHONE_NUMBER>1ffffc  x10 00000070c889efcc  x11 0000006f0988008c
    x12<PHONE_NUMBER>0000c5  x13 000000007fffffff  x14<PHONE_NUMBER>2cfb28  x15<PHONE_NUMBER>74aea2
    x16<PHONE_NUMBER>000001  x17 00000073f247b4e8  x18 00000070bb56e000  x19 0000006f09a80088
    x20 0000006f0998551c  x21 0000006f00000000  x22 b40000731b78f5b0  x23 0000006f0000006f
    x24 0000006f09b00b40  x25 00000070c8b53218  x26<PHONE_NUMBER>000000  x27<PHONE_NUMBER>4c4b40
    x28 00000070c8b65000  x29<PHONE_NUMBER>0003e8
    lr  00000070c889f04c  sp  00000070cb787a40  pc  00000070c8a6f7b0  pst<PHONE_NUMBER>001000
10 total frames
backtrace:
      #00 pc<PHONE_NUMBER>5187b0  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #01 pc<PHONE_NUMBER>348048  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #02 pc<PHONE_NUMBER>2c1b84  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #03 pc<PHONE_NUMBER>348660  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #04 pc<PHONE_NUMBER>348480  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #05 pc<PHONE_NUMBER>322484  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #06 pc<PHONE_NUMBER>3226d4  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #07 pc<PHONE_NUMBER>2b4a94  /data/app/~~3-H3Wi-OAqJut5S6TiqQGQ==/com.example.generate_crossword-_-pFqLDAMSPT9fMJLSc2Cg==/lib/arm64/libflutter.so (BuildId: b6be8ecbe9eeb0f8945f39ad3dfc95a77355adaa)
      #08 pc<PHONE_NUMBER>0cb6a8  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: a87908b48b368e6282bcc9f34bcfc28c)
      #09 pc<PHONE_NUMBER>06821c  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: a87908b48b368e6282bcc9f34bcfc28c)
Lost connection to device.
➜  step_10 git:(95bd5ab0) adb -s emulator-5554 shell getprop ro.build.version.release
14
➜  step_10 git:(95bd5ab0) adb -s emulator-5554 shell getprop ro.build.version.sdk
34

Here are the details from the Android Device Manager:
Properties
avd.ini.displayname              Pixel 7a API 34
avd.ini.encoding                 UTF-8
AvdId                            Pixel_7a_API_34
disk.dataPartition.size<PHONE_NUMBER>
fastboot.chosenSnapshotFile
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot           no
fastboot.forceFastBoot           yes
hw.accelerometer                 yes
hw.arc                           false
hw.audioInput                    yes
hw.battery                       yes
hw.camera.back                   virtualscene
hw.camera.front                  emulated
hw.cpu.ncore                     4
hw.device.hash2                  MD5:437310fd48ee977d023133a2babae359
hw.device.manufacturer           Google
hw.device.name                   pixel_7a
hw.dPad                          no
hw.gps                           yes
hw.gpu.enabled                   yes
hw.gpu.mode                      auto
hw.initialOrientation            Portrait
hw.keyboard                      yes
hw.lcd.density                   420
hw.lcd.height                    2400
hw.lcd.width                     1080
hw.mainKeys                      no
hw.ramSize                       2048
hw.sdCard                        yes
hw.sensors.orientation           yes
hw.sensors.proximity             yes
hw.trackBall                     no
image.androidVersion.api         34
image.sysdir.1                   system-images/android-34/google_apis_playstore/arm64-v8a/
PlayStore.enabled                true
runtime.network.latency          none
runtime.network.speed            full
showDeviceFrame                  yes
skin.dynamic                     yes
tag.display                      Google Play
tag.id                           google_apis_playstore
vm.heapSize                      256

What else can I do to help repro this issue?

//cc @rmacnak-google

I'm not able to reproduce on either Linux X64 (X64 emulator) or Mac ARM64 (ARM64 emulator).
From the disassembly near the stack and the register values, the GC is trying to deference a pointer that looks like the heap base got copied into the lower 32-bits. This might happen if somewhere there is a 64-bit store into an array slot instead of a 32-bit store, i.e., failure to take compressed pointers into account.
x19 0000006f0f700088 last slot
x20 0000006f0f6054fc current slot
x21 0000006f00000000 heap base
x8<PHONE_NUMBER>000001 compressed (clobbered, probably was 6f)
x23 0000006f0000006f decompressed
x1  0000006f0000006e untagged
Ideally, using rr with a watchpoint on the slot would show what corrupted it, but AFAIK rr does not work with Android.
@domesticmouse, could you bisect to find in which commit of Flutter this crash starts happening? If we're lucky it will include some Dart compiler or runtime change where we can find a bad store.

Honest answer, between Cloud Next and Google I/O, I'm currently in negative time.

@domesticmouse we can't make much progress on our side without a clear reproduction, we will wait till you have some time to help us out with this issue.

I should be able to get some time to work on this after Cloud Next next week. Feel free to ping me after the 15th of April if I haven't responded

@domesticmouse any updates, did you find time to look into getting us some reproduction information.

I'll try to make time to bisect this next week.


unable to tag entities in no-whitespace language

Describe the bug
Unable to tag entities in no-whitespace language (e.g. chinese or japanese).
Entity edition window only appers when the whole sentence is selected, however, unlike english, words in chinese are not splited by whitespace, so entities is a sub string of sentence. It seems that botfront only recognize words that is surrounded by whitesapce.
Change project language to chinese and using JiebaTokenizer in nlu pipeline doesn't help.
To Reproduce
Steps to reproduce the behavior:

Go to 'NLU'-'Examples'
tag entites for a non-english sentence
select words, not the whole sentence
See error

Expected behavior
Entity edition window should appear when sub-string of a sentence is selected
Screenshots

Desktop (please complete the following information):

OS: Ubuntu 16.04.
Browser: Chrome 81.0.4044.92
Version: 0.26.0
Run botfront in development mode.

Hi @ningchaoar , thanks for reporting.
Do you know if Rasa supports entities in no-whitespace languages?

Hi, as far as I know, Rasa has two ways to deal with no-whitespace languages:

use tokenizer(JiebaTokenizer for chinese) to do word segmentation, then use bulid-in entity extractor like CRFEntityExtractor or DIETClassifier
or 2. use char-level NER model as a custom component.

Hi @ningchaoar,
You're right. The tagging UI right now depends on spaces to help find natural words. We'll add a no-whitespace language mode in the future. 🙏

@pheel That would be good news to multi-language users, thanks for developing such great platform.

@pheel good to hear^^, any news on this? Thanks~

@yingkai1181 Someone is working on a PR right now!

@pheel nice, our company is really looking forward to this feature~ thx

As you may know, this feature is out!

As you may know, this feature is out!


[Question]: which mirakl sdk version supports "customer_directly_pays_seller" field in OR11 response?

We need to customize invoice export to skip commissions in case of direct seller sales. For that we plan to use "customer_directly_pays_seller" field in OR11 API response. But that field is not present in current 4.10.0 version of Mirakl SDK. What version can we use? Is it safe to upgrade?

Latest 4.36.0 version has it.


Uncaught TypeError: history.listen is not a function

I used redux-persist in my project but there is a error, how can I resolve it?
store.js
import {createStore, combineReducers, applyMiddleware} from 'redux'
import thunkMiddleware from 'redux-thunk'
import logger from 'redux-logger'
import {routerReducer, routerMiddleware, push} from 'react-router-redux'
import createHistory from 'history/createBrowserHistory'
import { persistStore, persistReducer } from 'redux-persist'
import storage from 'redux-persist/es/storage' // default: localStorage if web, AsyncStorage if react-native
import reducers from '../reducers'

const history = createHistory();
const historyRouterMiddleware = routerMiddleware(history);

const middleWares = [thunkMiddleware, historyRouterMiddleware,logger];

const config = {
    key: 'root', // key is required
    storage, // storage is now required
};
let comReducers = combineReducers({
    ...reducers,
    router: routerReducer
});
const persistReducers = persistReducer(config, comReducers);

export default function configureStore () {
    let store = createStore(persistReducers, applyMiddleware(...middleWares));
    let persistor = persistStore(store);

    return { persistor, store }
}

app.js
import React from 'react'
import {Provider} from 'react-redux'

import {ConnectedRouter} from 'react-router-redux'
import {matchRoutes, renderRoutes} from 'react-router-config'
import {Switch} from 'react-router-dom'
import { PersistGate } from 'redux-persist/es/integration/react'
import configureStore from './store'
import routes from './router'

const { persistor, store } = configureStore();
const onBeforeLift = () => {
    // take some action before the gate lifts
};
const App = () => (
    <Provider store={store}>
        <PersistGate
            loading={<div />}
            persistor={persistor}>
            <ConnectedRouter history={history}>
                <Switch>
                    {renderRoutes(routes)}
                </Switch>
            </ConnectedRouter>
        </PersistGate>
    </Provider>
);

export default App

I had resolve my problem ,is my bad .
import React from 'react'
import {Provider} from 'react-redux'

import {ConnectedRouter} from 'react-router-redux'
import {matchRoutes, renderRoutes} from 'react-router-config'
import {Switch} from 'react-router-dom'
import { PersistGate } from 'redux-persist/es/integration/react'
import createHistory from 'history/createBrowserHistory'
const history = createHistory();
import configureStore from './store'
import routes from './router'

const { persistor, store } = configureStore();
const onBeforeLift = () => {
    // take some action before the gate lifts
};
const App = () => (
    <Provider store={store}>
        <PersistGate
            loading={<div />}
            persistor={persistor}>
            <ConnectedRouter history={history}>
                <Switch>
                    {renderRoutes(routes)}
                </Switch>
            </ConnectedRouter>
        </PersistGate>
    </Provider>
);

export default App

when I add const history = createHistory(); in app.js it worked! :)


chore: fix buildifier errors

If so, I think this buildifier-prebuilt approach is probably best, since pre-commit.ci doesn't seem to work
https://github.com/thundergolfer/bazel-mypy-integration/pull/50


Fixed links in footer

In the quest to make the website production-ready, this branch resolves issue #346 and adjusts the links in both the mail and the github images to redirect to the right action

added mailto: to the email link to prevent a 404 error
Before (redirect)

After (redirect)

changed the email url in git link to the makeabilitylabwebsite git repo

Oops, same problem as other PR. These branches should be very simple--branching off of master and performing one and only one fix.  This needs to be fixed (and I imagine your other PRs have similar problems). @johnsonkuang do you understand what I mean?
You want the top block to say:
@johnsonkuang wants to merge 2 commits into master from fix-links-footer
Instead, it says:

Can we close this one since it looks like you resubmitted a PR with fixed branching? https://github.com/jonfroehlich/makeabilitylabwebsite/pull/433

yep
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Jon Froehlich<EMAIL_ADDRESS>Sent: Friday, July 13, 2018 10:16:36 AM
To: jonfroehlich/makeabilitylabwebsite
Cc: johnsonkuang; Mention
Subject: Re: [jonfroehlich/makeabilitylabwebsite] Fixed links in footer (#424)
Can we close this one since it looks like you resubmitted a PR with fixed branching? #433https://github.com/jonfroehlich/makeabilitylabwebsite/pull/433
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/jonfroehlich/makeabilitylabwebsite/pull/424#issuecomment-404897051, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AfdHHJvp3OI1l_k7nSNuDc7_xKfyFdvnks5uGNXzgaJpZM4VLpYK.


feat: add arm docker support

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Build from Dockerfile Fails

Build an image from a Dockerfile
root@m7-osquery-1:~# docker build -t kolide/fleet -f fleet/Dockerfile .
Sending build context to Docker daemon  111.5MB
Step 1/5 : FROM alpine
---> 3fd9065eaf02
Step 2/5 : MAINTAINER Kolide Developers<EMAIL_ADDRESS>---> Using cache
---> c92727989042
Step 3/5 : RUN apk --update add ca-certificates
---> Using cache
---> b8626791c3e2
Step 4/5 : COPY ./build/linux/fleet /usr/bin/fleet
COPY failed: stat /var/lib/docker/tmp/docker-builder943348346/build/linux/fleet: no such file or directory

You need to build fleet first before you can add it to the container. See the appropriate makefile target. https://github.com/kolide/fleet/blob/998e81db6da7aa1cf5f31ffcaa07868ba62036be/Makefile#L179-L182
The Dockerfile copies an existing fleet binary into the container.

Alright i may be missing a step....i'm missing packages is there a command i run before make docker-build-release
root@m7-osquery-1:~/gopath/src/github.com/mygithubname/fleet# make docker-build-release
make: npm: Command not found
GOOS=linux go build -i -o build/linux/fleet -ldflags " -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.appName=fleet -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.version=1.0.6-19-g998e81d -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.branch=master -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.revision=998e81db6da7aa1cf5f31ffcaa07868ba62036be -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.buildDate=2018-02-16T16:13:45Z -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.buildUser=root -X github.com/kolide/fleet/vendor/github.com/kolide/kit/version.goVersion=go1.9.4" ./cmd/fleet
cmd/fleet/prepare.go:9:2: cannot find package "github.com/WatchBeam/clock" in any of:
/usr/local/go/src/github.com/WatchBeam/clock (from $GOROOT)
/root/gopath/src/github.com/WatchBeam/clock (from $GOPATH)
cmd/fleet/serve.go:16:2: cannot find package "github.com/e-dard/netbug" in any of:
/usr/local/go/src/github.com/e-dard/netbug (from $GOROOT)
/root/gopath/src/github.com/e-dard/netbug (from $GOPATH)
cmd/fleet/prepare.go:10:2: cannot find package "github.com/go-kit/kit/log" in any of:
/usr/local/go/src/github.com/go-kit/kit/log (from $GOROOT)
/root/gopath/src/github.com/go-kit/kit/log (from $GOPATH)
cmd/fleet/serve.go:18:2: cannot find package "github.com/go-kit/kit/metrics/prometheus" in any of:
/usr/local/go/src/github.com/go-kit/kit/metrics/prometheus (from $GOROOT)
/root/gopath/src/github.com/go-kit/kit/metrics/prometheus (from $GOPATH)
cmd/fleet/main.go:9:2: cannot find package "github.com/go-sql-driver/mysql" in any of:
/usr/local/go/src/github.com/go-sql-driver/mysql (from $GOROOT)
/root/gopath/src/github.com/go-sql-driver/mysql (from $GOPATH)
cmd/fleet/config_dump.go:6:2: cannot find package "github.com/kolide/fleet/server/config" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/config (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/config (from $GOPATH)
cmd/fleet/prepare.go:12:2: cannot find package "github.com/kolide/fleet/server/datastore/mysql" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/datastore/mysql (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/datastore/mysql (from $GOPATH)
cmd/fleet/serve.go:21:2: cannot find package "github.com/kolide/fleet/server/health" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/health (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/health (from $GOPATH)
cmd/fleet/prepare.go:13:2: cannot find package "github.com/kolide/fleet/server/kolide" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/kolide (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/kolide (from $GOPATH)
cmd/fleet/serve.go:23:2: cannot find package "github.com/kolide/fleet/server/launcher" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/launcher (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/launcher (from $GOPATH)
cmd/fleet/serve.go:24:2: cannot find package "github.com/kolide/fleet/server/mail" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/mail (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/mail (from $GOPATH)
cmd/fleet/prepare.go:14:2: cannot find package "github.com/kolide/fleet/server/pubsub" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/pubsub (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/pubsub (from $GOPATH)
cmd/fleet/prepare.go:15:2: cannot find package "github.com/kolide/fleet/server/service" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/service (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/service (from $GOPATH)
cmd/fleet/serve.go:27:2: cannot find package "github.com/kolide/fleet/server/sso" in any of:
/usr/local/go/src/github.com/kolide/fleet/server/sso (from $GOROOT)
/root/gopath/src/github.com/kolide/fleet/server/sso (from $GOPATH)
cmd/fleet/serve.go:28:2: cannot find package "github.com/kolide/kit/version" in any of:
/usr/local/go/src/github.com/kolide/kit/version (from $GOROOT)
/root/gopath/src/github.com/kolide/kit/version (from $GOPATH)
cmd/fleet/serve.go:29:2: cannot find package "github.com/prometheus/client_golang/prometheus" in any of:
/usr/local/go/src/github.com/prometheus/client_golang/prometheus (from $GOROOT)
/root/gopath/src/github.com/prometheus/client_golang/prometheus (from $GOPATH)
cmd/fleet/serve.go:30:2: cannot find package "github.com/prometheus/client_golang/prometheus/promhttp" in any of:
/usr/local/go/src/github.com/prometheus/client_golang/prometheus/promhttp (from $GOROOT)
/root/gopath/src/github.com/prometheus/client_golang/prometheus/promhttp (from $GOPATH)
cmd/fleet/config_dump.go:8:2: cannot find package "github.com/spf13/cobra" in any of:
/usr/local/go/src/github.com/spf13/cobra (from $GOROOT)
/root/gopath/src/github.com/spf13/cobra (from $GOPATH)
cmd/fleet/serve.go:32:2: cannot find package "google.golang.org/grpc" in any of:
/usr/local/go/src/google.golang.org/grpc (from $GOROOT)
/root/gopath/src/google.golang.org/grpc (from $GOPATH)
cmd/fleet/config_dump.go:9:2: cannot find package "gopkg.in/yaml.v2" in any of:
/usr/local/go/src/gopkg.in/yaml.v2 (from $GOROOT)
/root/gopath/src/gopkg.in/yaml.v2 (from $GOPATH)
Makefile:180: recipe for target 'docker-build-release' failed
make: *** [docker-build-release] Error 1

identical issue here with #>make docker-build-release

I believe this issue should be resolved if GOPATH is configured properly. If anyone needs help with this, please connect with us on osquery Slack.


No module named 'azure.core.tracing.context'

Hey guys,
azure-storage-blob 12.0.0b3  is incompatible with azure-core 1.0.0b4
clean install:
$ pip install azure-storage-blob --pre
Collecting azure-storage-blob
  Using cached https://files.pythonhosted.org/packages/9e/ff/6b4765c781b81f72995442b0c431038ff278aee3e186cbc4497a8f6a639b/azure_storage_blob-12.0.0b3-py2.py3-none-any.whl
Collecting azure-core<2.0.0,>=1.0.0b3 (from azure-storage-blob)
  Using cached https://files.pythonhosted.org/packages/a7/ce/601b03eb5367d95ef7ed6783982a7374d08b86559fda344946b2718cbdd8/azure_core-1.0.0b4-py2.py3-none-any.whl
...
...
Installing collected packages: azure-core, azure-storage-blob
Successfully installed azure-core-1.0.0b4 azure-storage-blob-12.0.0b3

After that if you try to use the package you'll get the following exception:
...
...
    from azure.storage.blob import BlobClient, BlobServiceClient
  File "C:\Users\max\AppData\Local\Programs\Python\Python37\lib\site-packages\azure\storage\blob\__init__.py", line 11, in <module>
    from .blob_client import BlobClient
  File "C:\Users\max\AppData\Local\Programs\Python\Python37\lib\site-packages\azure\storage\blob\blob_client.py", line 25, in <module>
    from ._shared.uploads import IterStreamer
  File "C:\Users\max\AppData\Local\Programs\Python\Python37\lib\site-packages\azure\storage\blob\_shared\uploads.py", line 16, in <module>
    from azure.core.tracing.context import tracing_context
ModuleNotFoundError: No module named 'azure.core.tracing.context'

Temp fix: forcibly install azure-core 1.0.0b3 which is ok. (pip install azure-core==1.0.0b3)

@Fukkei thanks for letting us know! Someone from our team is going to take a look at this cc: @rakshith91

Hi @Fukkei thanks for reporting this issue. We do indeed have breaking changes in the new azure core and as you have identified one will need to revert to the older version of azure core for it.
The latest release of storage is now out which works well with the latest azure core and has more improvements. Please do try it out and let us know

Wow, that was fast.
@mayurid The most recent version azure-storage-blob-12.0.0b4 works flawlessly, thanks a lot!


catchError is not propagating error to parent

Describe the bug
According to the documentation catchError should propagate the error to the parent:
https://github.com/solidjs/solid/blob/46e5e78710cdd9f170a7afd0ddc5311676d3532a/packages/solid/src/reactive/signal.ts#L973
However during my testing I have discovered this is not the case for nested catchError:
  catchError(() => {
    catchError(() => {
      throw "hello"
    }, (err) => {
      console.log("1:", err);
      // throws Uncaught error
      throw err;
    })
  }, (err) => {
    // never throws
    console.log("2:", err)
  })

Your Example Website or App
https://playground.solidjs.com/anonymous/6ed025c5-df61-4655-b971-07ab36c76386
Steps to Reproduce the Bug or Issue
Nest catchError in catchError:
  catchError(() => {
    catchError(() => {
      throw "hello"
    }, (err) => {
      console.log("1:", err);
      // thows Uncaught error
      throw err;
    })
  }, (err) => {
    // never thows
    console.log("2:", err)
  })

Expected behavior
catchError should propagate the error to the parent
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

For comparison, this actually does work when placed outside of a createRoot: https://playground.solidjs.com/anonymous/c2dc01b8-4351-4a9c-aa41-f6d7c7e622a9

Hmm.. we will definitely be changing the behavior around error propagation in 2.0 when things get lazier but this looks the be an oversight. Thank you for the PR.


tests: pin Candlepin version to latest before Java 17

The current way of deploying Candlepin uses an Ansible role that is no more used/supported by the Candlepin project, and thus it is rotting; the recent switch of Candlepin from Java 11 to Java 17 broke with the unmaintained role.
Thus, as very short-term workaround, pin the version of Candlepin to deploy to the commit before the switch to Java 17.

[citest]

OK, things generally work fine, at least from a Candlepin POV.
The issues that shows up are the same that appeared for #84 too, i.e.:

old sub-man in Fedora:

F36 fix: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8aa252fd1a
F37 fix: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fff381197f

wrong D-Bus option for environments in CentOS Stream 8:

fix in redhat_subscription: https://github.com/ansible-collections/community.general/pull/6275

wrong environment selection

Since almost everything is external (either Fedora or the redhat_subscription module in the community.general collection), I'd get this in anyway for now (or at least wait for the Fedora errata), and hopefully at the end of the month we can get a new version of community.general with the fixes there.

fix in redhat_subscription: redhat_subscription: fix D-Bus option for environments on CentOS ansible-collections/community.general#6275

Is this the issue that affects rhel 8.9 as well?

No, the above issue affects only CentOS Stream 8; the failure of RHEL 8.9 is the same for every OS, and it's...

wrong environment selection

... this.

fix in redhat_subscription: redhat_subscription: fix D-Bus option for environments on CentOS ansible-collections/community.general#6275

Is this the issue that affects rhel 8.9 as well?

No, the above issue affects only CentOS Stream 8; the failure of RHEL 8.9 is the same for every OS, and it's...

wrong environment selection

... this.

Every OS except rhel 9.3?


Icon load time optimization

plus basic copy/paste support.
In testing this roughly halves the loading time of the dialog.

related: https://github.com/regolith-linux/ilia/issues/69, https://github.com/regolith-linux/ilia/issues/59, https://github.com/regolith-linux/ilia/issues/55


Can't resolve 'fs' error with cloud-storage-plugin s3 adapter

Link to reproduction
https://github.com/haliacmon/payload-reproduction
Describe the Bug
Getting Module not found: Error: Can't resolve 'fs' error with plugin-cloud-storage and s3-adapter
ERROR in ./node_modules/.pnpm/@payloadcms+plugin-cloud-storage@1.1.1_@aws-sdk+client-s3@3.454.0_@aws-sdk+lib-storage@3.454.0_payload<EMAIL_ADDRESS>140:27-40
Module not found: Error: Can't resolve 'fs' in '...\node_modules\.pnpm\@payloadcms+plugin-cloud-storage@1.1.1_@aws-sdk+client-s3@3.454.0_@aws-sdk+lib-storage@3.454.0_payload@2.1.1\node_modules\@payloadcms\plugin-cloud-storage\dist\adapters\s3'

To Reproduce
1- npx create-payload-app@latest reproduce-error-s3 -t blank --use-pnpm
using postgress
2- pnpm add @payloadcms/plugin-cloud-storage
3- pnpm add @aws-sdk/client-s3 @aws-sdk/lib-storage aws-crt
4- optional. add s3 related variables to .env. Not necessary to reproduce the error.
5- adding build config for plugin-cloud-storage & s3-adapter by instructions. (error happens after step 5)
https://github.com/payloadcms/payload/tree/c10db332cdeb3f702d378b0649be20eb789c13e1/packages/plugin-cloud-storage#s3-adapter
//payload.config.ts
...
import { cloudStorage } from '@payloadcms/plugin-cloud-storage'
import { s3Adapter } from '@payloadcms/plugin-cloud-storage/s3'

const adapter = s3Adapter({
  config: {
    credentials: {
      accessKeyId: process.env.S3_ACCESS_KEY_ID,
      secretAccessKey: process.env.S3_SECRET_ACCESS_KEY,
    },
    region: process.env.S3_REGION,
  },
  bucket: process.env.S3_BUCKET,
})
...

plugins: [
...
    cloudStorage({
      collections: {
        "my-collection-slug": {
          adapter: adapter,
        },
      },
    }),
  ],
...

Payload Version
2.1.1
Adapters and Plugins
db-postgres, plugin-cloud-storage, S3 Adapter

@haliacmon Can you give the beta package a try? pnpm add @payloadcms/plugin-cloud-storage@beta

+1 Webpack 5 also not playing nice on my builds.
I've tried numerous fixes, polyfill libraries, installing fallbacks...
Nothing seems to work and I would love to continue using the cloud storage plugin.

Wondering if we can just back port webpack to v4??

Another note, I tried moving to viteBundler, that was full of errors, though I'd love to move over to that once I have some more time to troubleshoot that.

@denolfe does your fix only address issues with pnpm? I just use npm.

@haliacmon Just published a new beta to try.
@ericuldall We've identified some issues w/ the vite bundler with this package that are yet to be resolved 👍

@denolfe does your fix only address issues with pnpm? I just use npm.

I would not expect any issues w/ npm.

@denolfe well that's good to know, but I can't even get the vite bundler to work on a blank install :-/

@ericuldall Sounds like it warrants a separate issue.

@ericuldall Sounds like it warrants a separate issue.

Yes, I'll tackle that in the main repo when the time comes. For now i'm trying to move fast and just get my webpack build working with gcs again :D

@denolfe Now I get single "Can't resolve 'fs' " error.
I have tried same steps with npm but the result was same.
If there is anything I can do to help diagnose, test etc. let me know.
webpack built 4ac35407a2a750e5e806 in 4227ms
ERROR in ./node_modules/.pnpm/@payloadcms+plugin-cloud-storage@1.1.2-beta.1_@aws-sdk+client-s3@3.454.0_@aws-sdk+lib-storage@3.454.0_payload<EMAIL_ADDRESS>136:49-62
Module not found: Error: Can't resolve 'fs' in 'D:\_code2\Azak\payload-reproduction\node_modules\.pnpm\@payloadcms+plugin-cloud-storage@1.1.2-beta.1_@aws-sdk+client-s3@3.454.0_@aws-sdk+lib-storage@3.454.0_payload@2.1.1\node_modules\@payloadcms\plugin-cloud-storage\dist\adapters\s3'

webpack compiled with 1 error

This is quite confusing as we tested your exact repo to make the fix.

I'm new to payload cms, just started to discover it. I might misunderstand some terminology. I dont have a slug yet... I think.
I just did "npx create-payload-app@latest reproduce-error-s3 -t blank --use-pnpm" and set it up with postgress. then opened localhost:3000 and created admin account. So in the collections I only have "Users" and one user, me/admin. So far zero errors.

but when I tried to confiqure cloud-storage-plugin & S3, I got Can't resolve 'fs' error.

I found a a workaround.
webpack: (config) => {
  config.resolve.fallback.fs = false;

  return config;
},

If I add this to buildConfig() error goes away
export default buildConfig({
  admin: {
    user: Users.slug,
    bundler: webpackBundler(),
    webpack: (config) => {
      config.resolve.fallback.fs = false;

      // if (config.resolve?.fallback)
      // config.resolve.fallback = { ...config.resolve.fallback, fs: false };

      return config;
    },
    // bundler: viteBundler(),
  },

I found a a workaround.
webpack: (config) => {
  config.resolve.fallback.fs = false;

  return config;
},

If I add this to buildConfig() error goes away
export default buildConfig({
  admin: {
    user: Users.slug,
    bundler: webpackBundler(),
    webpack: (config) => {
      config.resolve.fallback.fs = false;

      // This is to get rid of typescript error
      // if (config.resolve?.fallback)
      // config.resolve.fallback = { ...config.resolve.fallback, fs: false };

      return config;
    },
  },
...

Your mileage may vary by disabling those features. I've been trying similar stuff. something else to note if you want to preserve + override the webpack config you can do it like this:
  webpack: (config) => ({
    ...config,
    resolve: {
      ...config.resolve,
      fallback: {
        ...config.resolve.fallback,
        fs: false
      }
    }
  }),

I found a a workaround.
webpack: (config) => {
  config.resolve.fallback.fs = false;

  return config;
},

If I add this to buildConfig() error goes away
export default buildConfig({
  admin: {
    user: Users.slug,
    bundler: webpackBundler(),
    webpack: (config) => {
      config.resolve.fallback.fs = false;

      // This is to get rid of typescript error
      // if (config.resolve?.fallback)
      // config.resolve.fallback = { ...config.resolve.fallback, fs: false };

      return config;
    },
  },
...

thanks this helped me (I bumped into the same problem)

Can confirm I'm also running into this issue.

Using npx create-payload-app@latest with the website demo on MacOS, I was also running into these webpack errors for fs, os, and util (a total of 12 errors, most for fs).
Switching to @payloadcms/plugin-cloud-storage@beta brought this down to a single webpack error: Can't resolve 'fs' in '~/payload-s3/node_modules/@payloadcms/plugin-cloud-storage/dist/adapters/s3.
Adding the fallback object to payload.config.ts allowed me to finally get back into the /admin panel.
  fallback: {
    ...config.resolve.fallback,
    fs: false,
  },

For anyone landing here -
Don't forget to do this:
https://payloadcms.com/docs/upload/overview

For anyone landing here -
Don't forget to do this:
https://payloadcms.com/docs/upload/overview

I've come across this issue as well, I've used the node-polyfill-webpack-plugin package to solve it.
payload.config.ts:
`
...
import { cloudStorage } from "@payloadcms/plugin-cloud-storage";
import { s3Adapter } from "@payloadcms/plugin-cloud-storage/s3";
import NodePolyfillPlugin from "node-polyfill-webpack-plugin";
const s3ad = s3Adapter({
config: {
credentials: {
accessKeyId: process.env.S3_ACCESS_KEY_ID,
secretAccessKey: process.env.S3_SECRET_ACCESS_KEY,
},
region: process.env.S3_REGION,
},
bucket: process.env.S3_BUCKET,
});
export default buildConfig({
admin: {
user: Users.slug,
bundler: webpackBundler(),
webpack: (config) => ({
...config,
plugins: [...config.plugins, new NodePolyfillPlugin()],
}),
},
...
plugins: [
cloudStorage({
collections: {
logos: {
adapter: s3ad,
},
productImages: {
adapter: s3ad,
},
},
}),
],
...
`
here's are my dependencies:
{ ...   "dependencies": {     "@aws-sdk/client-s3": "^3.582.0",     "@aws-sdk/lib-storage": "^3.582.0",     "@payloadcms/bundler-webpack": "^1.0.0",     "@payloadcms/db-postgres": "^0.x",     "@payloadcms/plugin-cloud": "^3.0.0",     "@payloadcms/plugin-cloud-storage": "^1.1.2",     "@payloadcms/richtext-slate": "^1.0.0",     "aws-crt": "^1.21.2",     "cross-env": "^7.0.3",     "dotenv": "^8.2.0",     "express": "^4.19.2",     "node-polyfill-webpack-plugin": "^3.0.0",     "payload": "^2.0.0"   },   "devDependencies": {     "@types/express": "^4.17.9",     "copyfiles": "^2.4.1",     "nodemon": "^2.0.6",     "ts-node": "^9.1.1",     "typescript": "^4.8.4"   } }
here's the upload config of a collection:
... const Logos: CollectionConfig = {   slug: "logos",   upload: {     disableLocalStorage: true,     staticURL: "https://hocv1testingcdn.cloudfront.net",     staticDir: "logos",     mimeTypes: ["image/*"],   }, ...
I haven't done any extensive testing, but the admin panels seems to work perfectly.

Replacing the placeholder 'my-collection-slug' with something that exists like media completely fixed the problem.

@d717an is correct. This issue, as reproduced here, only occurs if there is an invalid plugin-cloud-storage plugin configuration, e.g. an invalid collection slug.
This has now been fixed by https://github.com/payloadcms/payload/pull/6786 which will throw a proper error if the plugin config is invalid! This will now work as expected, as payload is not supposed to start up with this plugin enabled, while its config is invalid. More info in that PR description


fixFix alter column stats without min max value deserialize failure. (#33406)

backport https://github.com/apache/doris/pull/33406

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run feut


Reorder cli commands: fix step printing

Earlier I had deleted the stuff from build_action which enabled step listing with roman build --steps ?, now I added step listing back to build_action.

PR #9 included some *.pyc. I rewrite the history, so the last commit in repo is actually 51ad312701c9a2e73157ff6486e8d7cbbe028a9c and not the one mentioned by github.


Strict file permissions for repository.yaml

Closes #11451

What this PR does / why we need it:
This PR remove read access of  "repository.yaml"  to world
Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

With secret data, shouldn't this be 600?

With secret data, shouldn't this be 600?

I initially started with 600. but later I changed to 640 as per the issue description.

Even if Helm derives the file permissions from the umask, world-readability is probably always too wide

I'll change the permissions to 600 👍


Changed filter-cards font.

Notes for Reviewers

This PR partially fixes #12739

Changed font in filter card tooltips
Before

After

Signed commits

[x] Yes, I signed my commits.

@Pratik-050, instead of joining tomorrow's core team meeting spend that time fixing this.

Closing PR as the approach needs to change.


feat: admin disconnect

@emilbayes the test case you suggested in slack is not viable atm because we do not get two 'connections' in the connections tab. Looks like one per domain. This seems ok to me. However there are two bugs

listKeys does not error after removing connections from the wallet. It appears like the keys have been removed after disconnect though
after disconnecting, if I attempt to reconnect from both instances of the dapp in their respective tabs, one will prompt me to connect again and the other does not.


Support for Universal Analytics

Any plans to support universal analytics? Is this something I should write myself?

Hi @robbiehudson!
Currently there are no plans for this. But if you would be willing to contribute, we would be happy for a pull request.

In what sense does UA differ from what the gem currently supports? Seeing we just started using this gem, and we're on UA, it might be something I'd be inclined to write.
Does it mean there are missing features?


bottom of chart.png shows text rendering issues

In the chart.png when the user is in an area with a long timezone name, the text is rendered incorrectly.  Looks like the area where the timestamp is written is not erased correctly or far enough.
For example:

with the previous commit, the timezone name has been removed and replaced with "%z" which shows the UTC offset instead.  Looks like this:

Still need to check to ensure that "%z" (lowercase) vs "%Z" (uppercase) is supported on Windows.  Google searches are providing conflicting results.

Confirmed the fix on Windows.
Old chart:

New chart:


Authentication issue when trying to process orders

I have everything set up. I run the order generator. I can see the messages hitting the queue. Nothing happens in AKS.
When I look at the k8s tool in Code, the order-processor has a red dot next to it. I'm not sure what to do from there.
I noticed in the YAML that it is pulling the image from your Docker account?
Should I package that in a new container and deploy the image to my ACR?

The service bus connection string does not seem to be valid anymore, can you verify that?

The generator uses send permissions while the message pump uses receive permission. So that is not a guarantee, can you pleasure generate a new one with these permissions please?

Quotes or no quotes around the connection strong on the command line? You example has quotes.

Getting the same result with new key.

Are you sure that the generated base64 representation is correct? (ie no trailing spaces)
The error clearly indicates that it's an authentication issue when trying to start processing the messages

I'm copying it using the portal copy function.
I've tried to stand the Processor up locally, from the command line, outside Docker. I can't get that to run. I keep getting JSON error.

Are you creating the subscription on the queue itself or the namespace? I presume you've verified that you have Receive/Manage permissions?
Does it work in Service Bus Explorer?

On the queue.
Not sure what you mean by verify. I looked at both subscriptions and they both have manage.
I'll try service bus explorer tomorrow.

Hi @rkralston, did you manage to test this? If so, did you get it working?

No. We abandoned KEDA b/c it is considered experimental by MS.

That's fair. For what it's worth, that might change soon.

Please let me know if it does.i am very excited about keda. I think it is a total game changer.
If I had bandwidth, this would be my open source project of choice.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Tom Kerkhove<EMAIL_ADDRESS>Sent: Monday, November 4, 2019 5:29:00 PM
To: kedacore/sample-dotnet-worker-servicebus-queue<EMAIL_ADDRESS>Cc: Keith Ralston<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [kedacore/sample-dotnet-worker-servicebus-queue] Authentication issue when trying to process orders (#8)
That's fair. For what it's worth, that might change soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/kedacore/sample-dotnet-worker-servicebus-queue/issues/8?email_source=notifications&email_token=AAHZELFH47EL2DP5SEI7PGDQSCV3ZA5CNFSM4IQJOC4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDBCLEQ#issuecomment-549594514, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAHZELHFT2B7WQ3UPCMZZD3QSCV3ZANCNFSM4IQJOC4A.

Keda went GA back in november, and is ready for production usage:
https://cloudblogs.microsoft.com/opensource/2019/11/19/keda-1-0-release-kubernetes-based-event-driven-autoscaling/

I just had the same situation. Restarting docker worked


Composed neural networks model from two networks

I am using Keras with Tensorflow to implement my model (M). Lets suppose that I have the following input features F = {x,y, a1, a2, a3, ..., an} I want to build a deep model (M1) using only x and y. Then, the output of (M1) with all the remaining features (a1, a2, ..., an) will be the input of another model (M2).
x,y --> M1 --> z, a1, a2, ..., an --> M2 --> final output
How can I build such model in Keras?

Yes, you need to look into functional models with multiple inputs. There is a section in the docs for this.


Getting actual head observations from actual groundwater wells into pest control file

Hi clever people,
Sorry to use your bug fix zone as a help centre, but....
Which util do I need to use to get all of my head observation time series (and river flux time series) into the pest control file? I think I'm looking for something like PESTGEN. If it's in pyemu I'll use it, otherwise I'll just use boring basic dos PESTGEN.
And on that, did I miss something in the training workshop, or does the Freyberg example notebooks not have any field observations included? I can't find them anywhere in the model files or in the pest file. If not, how can you calculate a phi?

In the class, we generated our own truth field obs and then used pandas to get them in the observation data section in the obsval column.  To do this, you need to workout the obs names that coorespond to the field observations.  Then pandas!

Thanks. I do remember now.

MOD2OBS has a function to interpolate the model heads when observations are between stress periods. Can pyemu also do this, or do I need to use pandas?

"its on the list" - currently pandas.

it's also worth considering what an interpolated (in time) value really means. I tend to align observations to the end of a stress period whenever possible. Just a thought :)

As always, it probably depends on the system and the question being asked. Which is the dominant signal - the summer/winter signal due to pumping and recharge, or the long term decline or rise due to climate, pumping and land use change? How much does it impact model outputs and prediction ranges? If your stress periods were >1yr I suspect not much at all. It would be a nice little paper. I'll add it to my never ending list!


It seems a buggy in linear_solver.cc

Line 469 of linear_solver.cc seems to be a bug.
https://github.com/google/or-tools/blob/554cbccaa95b4c11eced13f145de1bf468e1f919/ortools/linear_solver/linear_solver.cc#L469-L472
I think USE_CBC is correct instead of USE_GUROBI.

Seems to have been fixed internally, on my way to export the fix


[add][cms] "substitute_html" to recommend parts

Coverage decreased (-6.3%) to 78.35% when pulling fdca6f949ba17d47d4442f08c4c0c53b6b937a2f on sunny4381:features/substitute-html-to-recommend-parts into d89912b6b11d83cd12ddc78fb771da19b22b0289 on shirasagi:master.


analyzer: Allow multiple projects per definition file

Change the signature of PackageManager.resolveDependencies to allow
multiple projects per definition file. This is required for package
managers that allow defining multiple projects in a single definition
file, like Gradle or SBT.
This commit only changes the API, support for actually detekting
multiple projects in a single definition file will be added later.

@mnonnenmacher MavenTest seems to fail.


Make debug_nan and debug_uninit work more accurately for matrices

Both were plagued by checking the entirety of the matrix, when in fact
only one element needs to be checked. This is wasteful because it
checks elements that aren't read or written by the op we are checking,
and it can also lead to "false positives", errors about elements that
are not touched by the present op.
Refinement of the debug_nan and debug_uninit cases was by Alex Wells.
LG added comments to clarify the implementation of these functions.
LG also amended the testsuite/debug-uninit to specifically test
arrays, triples, and matrices (checking for true positives and check
against false positives). In the process, he noticed another bug (!)
where float-based arrays were not being correctly initialized with
their uninitialized value sentinels, and thus were not detecting use
of uninitialized values therein, because instead of calling
is_float_based, we called is_floatbased, which excludes arrays.
(The similar names are yet ANOTHER bug, or at least unintended to be
so confusing, and this will be addressed in a separate PR).
Signed-off-by: Larry Gritz<EMAIL_ADDRESS>

LGTM!

LGTM

Typo fixed, thanks for the look-over

Aside: Years ago we started adding "LGTM" as an ordinary comment. But nowadays there is a real "review changes" UI under the "files changed" tab (look in the upper right), where you can click an "approved" button. I think that's how we should do it. (You can still write "LGTM" in those comments if you wish.) If we ever enable to the restriction that merges require an "approval" (as many projects have), that's what it would be looking at, so I think it's a good habit to make.


reCaptcha Thinks MotorCycle is a Bicycle

Not sure if this is the right place to post this, but reCaptcha is seeing motorcycles as bicycles.

Same here, except it was a multiple picture recaptcha, apparently ai is pretty dumb

This still happens often for me.  Are there a bunch of people saying the motorcycles are the bicycles training the A.I. that way?  In my mind, motorcycles are not bicycles.

Repo is just for PHP client issues. This is about the reCAPTCHA service. I can confirm that does not look like a bicycle to me.


Usage example?

Hi,
Could you add usage example to readme please? What can be achieved with this package?
Also, on npm it's published as jupyter-vue, while on github it's named ipyvue. This is a bit confusing.
Thanks in advance!

This package was extracted from https://github.com/mariobuikhuizen/ipyvuetify to serve as a base library for other vue jupyter extensions (https://github.com/mariobuikhuizen/ipyvuedraggable being the first).
I will add more documentation when I have the time. In the meantime you can use the documentation of https://github.com/mariobuikhuizen/ipyvuetify (only using the Html and Template class).
jupyter-vue is the frontend code and can be used with different languages on the backend. For now only a python backend version  is implemented as ipyvue. If a julia version will be made, it will probably  be called jlvue. This is a naming convention in the jupyter community.

First try - the basics seem to be working:
from traitlets import *
import ipyvue as vue

class zir(vue.VueTemplate):

    u_sayhello = Unicode("Hello world!").tag(sync=True)
    lst_green = List(
        [
            "chartreuse",
            "limegreen",
            "lime",
            "forestgreen",
            "green",
            "darkgreen",
            "greenyellow",
            "yellowgreen",
            "springgreen",
            "mediumspringgreen",
            "lightgreen",
            "palegreen",
            "darkseagreen",
            "mediumseagreen",
            "lightseagreen",
            "seagreen",
            "olive",
            "darkolivegreen",
            "olivedrab",
        ]
    ).tag(sync=True)

    template = Unicode(
    """
        <template>

                Vue says '{{u_sayhello}}'

Fifty shades of green

{{colour}}

        </template>
    """
    ).tag(sync=True)

zir()

Couldn't figure out how to include things like data(), computed(), methods(), watcher() etc or scoped css style.
Hmm, maybe doing %%html and importing Vue.js in a script tag might be more straightforward?

Couldn't figure out how to include things like data(), computed(), methods(), watcher() etc or scoped css style.

This is not supported.
The data() and methods: properties are controlled from the python side. The other properties are not supported.  Traitlets are accessible as if they were in data(), methods starting with vue_[name] are accessible as [name] as if they were in methods:
I've adapted your example to include a method:
from traitlets import *
import ipyvue as vue

class zir(vue.VueTemplate):
    selected_colour = Unicode('yellowgreen').tag(sync=True)

    u_sayhello = Unicode("Hello world!").tag(sync=True)
    lst_green = List(
        [
            "chartreuse",
            "limegreen",
            "lime",
            "forestgreen",
            "green",
            "darkgreen",
            "greenyellow",
            "yellowgreen",
            "springgreen",
            "mediumspringgreen",
            "lightgreen",
            "palegreen",
            "darkseagreen",
            "mediumseagreen",
            "lightseagreen",
            "seagreen",
            "olive",
            "darkolivegreen",
            "olivedrab",
        ]
    ).tag(sync=True)

    template = Unicode(
    """
        <template>

                Vue says '{{u_sayhello}}' colour: {{ selected_colour }}

Fifty shades of green

{{colour}}

                <select @change="(event) => on_colour_change(event.target.value)">
                    <option
                        v-for="colour in lst_green"
                        :value="colour"
                        :selected="colour === selected_colour"
                    >{{ colour}}</option>
                </select>

        </template>
    """
    ).tag(sync=True)

    def vue_on_colour_change(self, data):
        self.selected_colour = data

zir()

Hmm, maybe doing %%html and importing Vue.js in a script tag might be more straightforward?

Maybe, I don't know what you're trying to accomplish.