Unable to collect wrapped bales <IP_ADDRESS>

We seem have have the bug where the UAL was picking up the straw bales fine and now has stopped also tested using the in game Anderson RBM2000 and this provided the error you don't own the bale, using <IP_ADDRESS> of this mod and what logs do you need as its on MP so if server logs i can grap them and copy and paste them here.

In this case - what is the enableCollectingBalesFromMissions setting set to? Is that feature on or off?
When you are trying to collect the bales and you walk up to them in game, does it show that you (or your farm) are the owner of the bales?
The logs that are needed would either be the server logs, or single player logs - which would be even better if you are running the mod with debugMode="true"

First answer when walking up to bales showing no owners like would if bales it myself would show Example Own By : Farm, having looked into settings all turn on.
Log is included and added the xml here but as text file.
log.txt
contract.txt

thank you for the logs, and the explanation. It looks like you are running / hosting a local MP server on your windows machine (not running it from a dedicated server), is that correct?
Your logs call out the following setting:

    enableCollectingBalesFromMissions :: false
which means that you are not allowed to collect bales from missions, which means that the mod is working correctly based on that setting (as intended).

It's also unclear if the correct configuration is being loaded as it appears that the mod is loading your local settings file (which would only change those values for you), which in some way may cause the discrepency between what you "see" and what you are being actually granted,

2024-12-19 18:21   Info: ContractBoost:LOAD :: MODSETTINGS configuration from: C:/Users/petet/Documents/My Games/FarmingSimulator2025/modSettings/ContractBoost.xml | debug: false

That said, the parent issue here may still be #3 or #30 - in that sometimes the server does not accurately reflect the settings set in the config file, or reverts to default settings (which has that setting turned off). I'm working on those issues, but need a dedicated server to do so; i'm waiting for it to spin up.
If you have access to the server, you should be able to either change that setting in-game (through the settings menu, don't forget to save) and / or edit the config file directly via FTP. both changes will require a restart. when you pull up the logs, look for this block:
2024-12-19 18:21   Info: ContractBoost:LOAD :: MODSETTINGS configuration from: C:/Users/petet/Documents/My Games/FarmingSimulator2025/modSettings/ContractBoost.xml | debug: false
2024-12-19 18:21   Info: ContractBoost:LOAD :: config loaded
2024-12-19 18:21   Info:    customMaxPerType:
2024-12-19 18:21   Info:    customRewards:
2024-12-19 18:21   Info:       baleMission :: 3500
2024-12-19 18:21   Info:       baleWrapMission :: 500
2024-12-19 18:21   Info:    debugMode :: false
2024-12-19 18:21   Info:    enableCollectingBalesFromMissions :: false
2024-12-19 18:21   Info:    enableContractValueOverrides :: true
2024-12-19 18:21   Info:    enableFieldworkToolFillItems :: true
2024-12-19 18:21   Info:    enableGrassFromMowingMissions :: true
2024-12-19 18:21   Info:    enableHayFromTedderMissions :: true
2024-12-19 18:21   Info:    enableStonePickingFromMissions :: true
2024-12-19 18:21   Info:    enableStrawFromHarvestMissions :: true
2024-12-19 18:21   Info:    enableSwathingForHarvestMissions :: true
2024-12-19 18:21   Info:    maxContractsOverall :: 50
2024-12-19 18:21   Info:    maxContractsPerFarm :: 10
2024-12-19 18:21   Info:    maxContractsPerType :: 5
2024-12-19 18:21   Info:    rewardFactor :: 1.5
2024-12-19 18:21   Info: ContractBoost :: loaded. debug: off

with that data you can verify very quickly if the setting is not only getting saved properly, but getting loaded from the correct settings file. in this case, it appears that there isn't a config file on the server, but it's defaulting to your local settings file, which may be part of the issue. I'll keep working on it, and let you know if I find anything!

Ok done deep dive on the other server same issue and its because of this

true
true
true
true
true
true
true
true
        **false**
        0.500000
10
5
50

3500
500
400

This from other server same issue and believe because not applying to savegame FS25_ContractBoost.xml

That's what I've been hearing, thank you for the additional data.

Just small update i edited the save game info so currently now saying true, this allow the bales to be pickup but the ownership of the bales still has nothing, this means can't sell or load them as bales into hay barn that i have takes straw bales.

Just small update i edited the save game info so currently now saying true, this allow the bales to be pickup but the ownership of the bales still has nothing, this means can't sell or load them as bales into hay barn that i have takes straw bales.

just to confirm - this is still in MP that it's not working as expected?

Just small update i edited the save game info so currently now saying true, this allow the bales to be pickup but the ownership of the bales still has nothing, this means can't sell or load them as bales into hay barn that i have takes straw bales.

just to confirm - this is still in MP that it's not working as expected?

correct for MP.

Hi @GMNGjoy, i have also various errors when i finished a contract (wrapped bales) and picked up the bales for selling them (before clicking finish on contract's section). Errors when i'm unloading the bales on animal's seller..
2024-12-23 22:36 Error: Can't change money of spectator farm
2024-12-23 22:36 LUA call stack:
=dataS/scripts/FSBaseMission.lua:2720 addMoney
=dataS/scripts/objects/SellingStation.lua:427 sellFillType
=dataS/scripts/objects/SellingStation.lua:387 addFillLevelFromTool
=dataS/scripts/triggers/UnloadTrigger.lua:229 addFillUnitFillLevel
=dataS/scripts/triggers/BaleUnloadTrigger.lua:131 update
=dataS/scripts/network/NetworkNode.lua:164 updateActiveObjects
=dataS/scripts/network/Server.lua:64 update
=dataS/scripts/BaseMission.lua:1017 update
=dataS/scripts/FSBaseMission.lua:1936 update
=dataS/scripts/mission00.lua:658 update
=dataS/scripts/main.lua:1195 update
2024-12-23 22:36 Error: Can't change money of spectator farm
2024-12-23 22:36 LUA call stack:
=dataS/scripts/FSBaseMission.lua:2720 addMoney
=dataS/scripts/objects/SellingStation.lua:427 sellFillType
=dataS/scripts/objects/SellingStation.lua:387 addFillLevelFromTool
=dataS/scripts/triggers/UnloadTrigger.lua:229 addFillUnitFillLevel
=dataS/scripts/triggers/BaleUnloadTrigger.lua:131 update
=dataS/scripts/network/NetworkNode.lua:164 updateActiveObjects
=dataS/scripts/network/Server.lua:64 update
=dataS/scripts/BaseMission.lua:1017 update
=dataS/scripts/FSBaseMission.lua:1936 update
=dataS/scripts/mission00.lua:658 update
=dataS/scripts/main.lua:1195 update
2024-12-23 22:37 Error: Can't change money of spectator farm
2024-12-23 22:37 LUA call stack:
=dataS/scripts/FSBaseMission.lua:2720 addMoney
=dataS/scripts/objects/SellingStation.lua:427 sellFillType
=dataS/scripts/objects/SellingStation.lua:387 addFillLevelFromTool
=dataS/scripts/triggers/UnloadTrigger.lua:229 addFillUnitFillLevel
=dataS/scripts/triggers/BaleUnloadTrigger.lua:131 update
=dataS/scripts/network/NetworkNode.lua:164 updateActiveObjects
=dataS/scripts/network/Server.lua:64 update
=dataS/scripts/BaseMission.lua:1017 update
=dataS/scripts/FSBaseMission.lua:1936 update
=dataS/scripts/mission00.lua:658 update
=dataS/scripts/main.lua:1195 update
2024-12-23 22:37 Error: Can't change money of spectator farm

Add also a videoclip below:
log#2.txt
https://app.screencast.com/v8JUfQYSJHXIJ

Hi, I tried it again, first collecting silage bales from the contracts (and storing them on my farm before collecting the reward and completing the mission), then after collecting the reward and completing the mission, loading them onto the lorry and taking them to the livestock dealer to sell them, always getting the errors below. So with this mod it is not possible to collect bales (especially silage) and then sell them, you have to use them only for animals or otherwise for your farm.
2024-12-25 00:41 Error: Can't change money of spectator farm
2024-12-25 00:41 LUA call stack:
=dataS/scripts/FSBaseMission.lua:2720 addMoney
=dataS/scripts/objects/SellingStation.lua:427 sellFillType
=dataS/scripts/objects/SellingStation.lua:387 addFillLevelFromTool
=dataS/scripts/triggers/UnloadTrigger.lua:229 addFillUnitFillLevel
=dataS/scripts/triggers/BaleUnloadTrigger.lua:131 update
=dataS/scripts/network/NetworkNode.lua:164 updateActiveObjects
=dataS/scripts/network/Server.lua:64 update
=dataS/scripts/BaseMission.lua:1017 update
=dataS/scripts/FSBaseMission.lua:1936 update
=dataS/scripts/mission00.lua:658 update
=dataS/scripts/main.lua:1195 update

Hi @GMNGjoy, with the last update v<IP_ADDRESS> you have fixed also errors from me mentioned above?

above?

Not yet - there was no release posted as it's not working yet. MP support is first, then I'll address the bale issue. I'm getting close with the MP fix, and i have an idea on the reason the bales are having an issue. i've got a few days off work, I'm hoping to get a fix for both out asap.
sorry for the wait, it's the holiday season and family takes priority.

Yes sure, 💯 i only reported the issues and ask why for this errors, take
your time 🙃
Il Gio 26 Dic 2024, 03:31 Gaming Joy | Josh @.***> ha
scritto:

above?
Not yet - there was no release posted as it's not working yet. MP support
is first, then I'll address the bale issue. I'm getting close with the MP
fix, and i have an idea on the reason the bales are having an issue. i've
got a few days off work, I'm hoping to get a fix for both out asap.
sorry for the wait, it's the holiday season and family takes priority.
—
Reply to this email directly, view it on GitHub
https://github.com/GMNGjoy/FS25_ContractBoost/issues/34#issuecomment-2562088496,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A27M5Q2NQAMBYPAQS5IAJFT2HNS73AVCNFSM6AAAAABT5TAQK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSGA4DQNBZGY
.
You are receiving this because you commented.Message ID:
@.***>

above?

Not yet - there was no release posted as it's not working yet. MP support is first, then I'll address the bale issue. I'm getting close with the MP fix, and i have an idea on the reason the bales are having an issue. i've got a few days off work, I'm hoping to get a fix for both out asap.
sorry for the wait, it's the holiday season and family takes priority.

IRL always take first hope you have great Holiday Season with your family :)

Hi @GMNGjoy, now with last update <IP_ADDRESS> i can unload and sell bales of straw and silage without errors, but i have many errors, when i choose different option in settings... Before not having this type of errors...
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 0 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 1 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 2 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 3 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 4 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 5 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:28   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 6 customMaxPerType
2024-12-26 19:28 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 7 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 8 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 9 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 10 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 11 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 12 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 13 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 14 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table
2024-12-26 19:29   Info: FS25_ContractBoost:SETTINGS :: settingChanged table: 0x0000020c4723c088 15 customMaxPerType
2024-12-26 19:29 Error: Running LUA method 'update'.
C:/Users/User/Documents/My Games/FarmingSimulator2025/mods/FS25_ContractBoost/scripts/Settings.lua:36: attempt to index nil with table

@FirenzeIT <IP_ADDRESS> was not an official release, as it was not included on the releases page.
Please do not pull any versions that are not announced as a release - this is an active code repository and individual commits are not intended to be "releases" unless published on the Releases page.

@FirenzeIT <IP_ADDRESS> was not an official release, as it was not included on the releases page.
Please do not pull any versions that are not announced as a release - this is an active code repository and individual commits are not intended to be "releases" unless published on the Releases page.

Ok, so i don't and can't report the errors here?? o.O

Hi, warning with v<IP_ADDRESS> (2024-12-27 12:47   Warning: FS25_ContractBoost:LOAD Could not read ContractBoost settings from either g_currentMission or savegameSettingsFile) it's normal if not have any savegame??

@FirenzeIT <IP_ADDRESS> was not an official release, as it was not included on the releases page.
Please do not pull any versions that are not announced as a release - this is an active code repository and individual commits are not intended to be "releases" unless published on the Releases page.

Ok, so i don't and can't report the errors here?? o.O
A warning with v<IP_ADDRESS>: (2024-12-27 12:47 Warning: FS25_ContractBoost:LOAD Could not read ContractBoost settings from either g_currentMission or savegameSettingsFile) it's normal if not have any savegame??

THAT is not what I said. I welcome bug reports or feature request through GitHub - but ONLY ON RELEASED VERSIONS. Unless it's a version that was released via the Releases page, it's not intended for use. Your post above was on a version that could only have been obtained by manually downloading the repository itself, which I don't want, or support. I ONLY support RELEASED VERSIONS. If I tried to support every commit version, I'd go crazy.
The way that GitHub works is that the "code" itself (the repository) is a place to store "versioned" code. When I'm developing, I'm constantly saving "commits" which are points in time where I think something is ready, but I'm still testing. I don't want, and don't expect anyone to be manually pulling that code, zipping it up for themselves, and then playing with it. Unless it's on the Releases page, please don't touch it.
I only post to the Releases page when something is tested and working as I expect it to. Not before.

A warning with v<IP_ADDRESS>: (2024-12-27 12:47 Warning: FS25_ContractBoost:LOAD Could not read ContractBoost settings from either g_currentMission or savegameSettingsFile) it's normal if not have any savegame??

that is normal, but I'll de-classify it as a warning. This state happens either when you're activating the mod for the first time, or you're upgrading from a older version (pre-<IP_ADDRESS>), or you're connecting to a dedicated server. It just means that the default "location" where the mod gets it's settings from in SP (the savegameSettingsFile, savegame##/FS25_ContractBoost.xml) is not there yet, and it has to figure out what to do next.

Hi @GMNGjoy, ok. However, the silage bales selling, it's fix them soon??

@FirenzeIT I'm looking into it, and don't have an ETA or even know if it's fixable. I'm doing what I can, please be patient and wait for a release. If you'd like to discuss more, or ask other questions - feel free to join my discord; This is an issue tracker, not a discussion forum.
That said, it was a mistake to close this yesterday since it's not fixed yet, I must have clicked the wrong button.

fixed in <IP_ADDRESS>

Hi, very nice works, now when selling the wrapped bales from contracts, it's possible without have any issues/errors/bugs, nice! But i effort a probably other bug: contract bale wrap it's blocked at 99%, without have any bales not wrapped available in the field, it's possible have this chance? Map: Riverbend Springs; Mods: not others than ContractBoost.


required MultipleText are not validating.

Describe the bug
According to SurveyJS behavior, a required MultipleText element should not be valid if all of the text values are null. If any of the MultipleText's text values are non-null, the element should be valid.
Right now, MultipleText elements in flutter_survey_js are considered valid, even if all of the element's text values are null.
To Reproduce
SurveyJs json
{
 "pages": [
  {
   "name": "page1",
   "elements": [
    {
     "type": "multipletext",
     "name": "question1",
     "title": "Multiple text",
     "isRequired": true,
     "items": [
      {
       "name": "text1"
      },
      {
       "name": "text2"
      }
     ]
    }
   ]
  }
 ]
}

SurveyJs answer
{
}

Expected behavior
Submitting the survey without entering values to the MultipleText element should display errors and not submit successfully.
Screenshots
N/a
Desktop (please complete the following information):
N/a
Smartphone (please complete the following information):
Any
Additional context
N/a

I've got this mostly fixed on this branch, but am struggling to make the multipleTextBuilder rebuild to show the error text when validating the form... If anybody knows how to make this work, let me know.

rebase on https://github.com/goxiaoy/flutter_survey_js/commit/d4d72bfbcabb1f1d2a3a9467bd62db5f63509a5a and create a PR please


[Bug]: Sending from ledger created multiple transactions

Issue description
Clicking on Send button created two transactions with the same amount. Obviously, the ledger device prompted twice but due to some reason the send button is being triggered twice on a single click.
Expected behaviour
A single click on Send button should only trigger a single send.
Actual behaviour
A single click on Send button triggered multiple sends.
Can the issue reliably be reproduced?
No
Steps to reproduce the issue

Setup a ledger profile;
Initiate a transaction;
Notice multiple prompts on ledger device.

Diagnostics
No response
Errors
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

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

Hi, is this still an issue in the latest version?

Closing due to inactivity, please reopen if the issue persists in the latest version


Is it available for Apple M1 cpu?

On the laptop with Apple M1 cpu trying to instantiate annoy4s.Annoy and getting java.lang.UnsatisfiedLinkError.
Following the guide on the main page:

sbt compileNative results in:

[info] Loading global plugins from /Users/akabas/.sbt/1.0/plugins
[info] Loading settings for project annoy4s-build from plugins.sbt ...
[info] Loading project definition from /Users/akabas/repos/annoy4s/project
[info] Loading settings for project root from build.sbt ...
[info] Set current project to annoy4s (in build file:/Users/akabas/repos/annoy4s/)
g++ -o /Users/akabas/repos/annoy4s/src/main/resources/darwin/libannoy.dylib -shared -dynamiclib /Users/akabas/repos/annoy4s/src/main/cpp/annoyjava.cpp
In file included from /Users/akabas/repos/annoy4s/src/main/cpp/annoyjava.cpp:15:
/Users/akabas/repos/annoy4s/src/main/cpp/annoylib.h:107:9: warning: Using no AVX instructions [-W#pragma-messages]
#pragma message "Using no AVX instructions"
        ^
1 warning generated.
[success] Total time: 1 s, completed Oct 14, 2022, 2:10:42 PM

sbt test results in:

[error] Uncaught exception when running annoy4s.AnnoySpec: java.lang.UnsatisfiedLinkError: Can't load library: /Users/*******/Library/Caches/JNA/temp/jna4858349749797659803.tmp
[error] sbt.ForkMain$ForkError: java.lang.UnsatisfiedLinkError: Can't load library: /Users/*******/Library/Caches/JNA/temp/jna4858349749797659803.tmp
[error] 	at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2633)
[error] 	at java.base/java.lang.Runtime.load0(Runtime.java:768)
[error] 	at java.base/java.lang.System.load(System.java:1837)
[error] 	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1018)
[error] 	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988)
[error] 	at com.sun.jna.Native.<clinit>(Native.java:195)
[error] 	at annoy4s.Annoy$.<clinit>(Annoy.scala:100)
[error] 	at annoy4s.AnnoySpec.$anonfun$new$1(AnnoySpec.scala:94)
[error] 	at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)

Next sbt publishLocal succeeds, but then java.lang.UnsatisfiedLinkError still persists, so native library is absent.

Looks like the original spotify/annoy does not support Apple M1? What steps should be taken to fix it?
This issue causes scio#4515

How about upgrading JNA to newer version? Sorry I don't have an Apple M1 around to reproduce this.
https://github.com/annoy4s/annoy4s/blob/3744055126d27789f2b64a4d5310318f8d585413/build.sbt#L12

How about upgrading JNA to newer version? Sorry I don't have an Apple M1 around to reproduce this.
https://github.com/annoy4s/annoy4s/blob/3744055126d27789f2b64a4d5310318f8d585413/build.sbt#L12

Wow! Thanks a lot @pishen, it fixes the problem in both annoy4s and scio:
https://github.com/annoy4s/annoy4s/pull/18

@shnapz would you know how we can tweak the build to generate a multi-arch build? At work, our developer machines are x86, ARM (M1) and on production we use x86 or ARM (Gravitron).

@mridang I am not sure about this. Definitely when it is build and published on M1 it works after that PR.
I guess that .travis.yml should be modified for multiple architectures support. @pishen what do you think?

Since the file is located at src/main/resources/darwin/libannoy.dylib for both M1 and non-M1, maybe it's not possible to provide a pre-built library for both cases? Is the libannoy.dylib file generated on M1 machine also working on non-M1 machine after we upgraded JNA?


MINIFI-344: Enabling running as a windows service.

Thank you for submitting a contribution to Apache NiFi - MiNiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with MINIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under minifi-assembly?
[X] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly?

For documentation related changes:

[X] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

This pull request adds the ability to run MiNiFi as a Windows service via Commons Daemon procrun (renamed to minifi.exe in the code). A new WindowsService class provides a wrapper interface for the service calls.

reviewing

Hey @jzonthemtn,
Sorry this has been pending so long, finally got to give it a review.  Could you specify where the exe files came from and/or how they were generated?  Trying to understand possible licensing concerns.
The code and doc changes look good, but have not been able to successfully run on Windows 10 as a service.  I may be doing something silly. I have updated my config as specified in the docs to absolute paths to my minifi directory.  The path in the service listing points correctly to the accessible exe and I can execute it directly (but that also fails).
I get the following dialog after installing and trying to run:

Services
Windows could not start the Apache MiNiFi on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 1.
OK

In minifi.log, the following:

[2017-07-18 10:58:21] [error] [21456] Failed creating java
[2017-07-18 10:58:21] [error] [21456] ServiceStart returned 1

Looking at the System Event Log, I see the corresponding event:

The Apache MiNiFi service terminated with the following service-specific error:
Incorrect function.

No problem, @apiri. The exes are the renamed executables from Commons Daemon procrun. The exes are renamed to match the name of the service per the procrun instructions. Tomcat 8 uses procrun and its Windows zip includes similarly named tomcat8.exe and tomcat8w.exe files.
I will double-check running the service.

It runs as a service for me ok once I set the following properties in bootstrap.conf to absolute paths:
lib.dir=C:\\code\\nifi-minifi\\minifi-assembly\\target\\minifi-0.2.1-SNAPSHOT-bin\\minifi-0.2.1-SNAPSHOT\\lib
conf.dir=C:\\code\\nifi-minifi\\minifi-assembly\\target\\minifi-0.2.1-SNAPSHOT-bin\\minifi-0.2.1-SNAPSHOT\\conf

nifi.minifi.config=C:\\code\\nifi-minifi\\minifi-assembly\\target\\minifi-0.2.1-SNAPSHOT-bin\\minifi-0.2.1-SNAPSHOT\\conf\\config.yml

Hey @jzonthemtn,
Thanks for the updates.  I'll give it another go in the next couple days when I can get in front of a Windows machine again.  I had done full path, but wondering if I forgot to do the double backslashes.  Anyway, will report back soon.

Tried this again in a clean Windows VM environment and had more success.  Changes look good.  Sorry for the delays but will get this merged!

No problem! Awesome to hear. Thanks!


Add boilerplate with multiple indices for shipping to multiple Logs Apps

https://github.com/sematext/logagent-js/blob/ad4bdeff1baa606385124d55ab8d3856354cac4e/bin/logagent-setup.sh#L182
When running sudo logagent-setup -i LOGS_TOKEN we should also generate a section for multiple Elasticsearch endpoints and indices in the logagent.conf to make it easy for the customer to configure if needed. It can all be commented out to begin with. The goal is to have it in the configuration file for easy edits.

Sounds OK to me. @megastef ?

@adnanrahic I think @megastef implemented something like this recently.... maybe in https://github.com/sematext/logagent-js/commit/c697139acd9b90ae2ababe724aa26a6f137e0d07 ?  Or is this only for multiple Receiver URLs?

We have a feature for multiple ES indices as receivers. It's also documented here and here.

You can generate a complete config file with
logagent --writeConfig <filename>

Including this section https://github.com/sematext/logagent-js/blob/master/config/example.yml#L1072-L1097
Shipping to multiple apps does not need https://github.com/sematext/logagent-js/commit/c697139acd9b90ae2ababe724aa26a6f137e0d07 which is for shipping to multiple servers.


[updatecli][githubrelease] Bump version to 1.21.5

[updatecli][githubrelease] Bump version to 1.21.5
Report
Source:
	✔ [gomod] Get version in go.mod format(shell)
	✔ [latestGoVersion] Get Latest Go Release(githubrelease)
	✔ [minor] Get minor version in .go-version(shell)

Condition:
	✔ [dockerTag] Is docker image golang:1.21.5 published(dockerimage)
	✔ [goDefaultVersion-check] Check if defined golang version differs(shell)

Target:
	⚠ [update-go-version] Update .go-version(file)
	⚠ [update-golang.ci] Update .golangci.yml(file)
	⚠ [update-gomod] Update go.mod(file)

Changelog
Click to expand
no GitHub Release found for go1.21.5 on "https://github.com/golang/go"

Remark
This pull request was automatically created using Updatecli.
Please report any issues with this tool here

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 941caf55803457315449ac1fcf89c1e8e4e3f6c5

Failed CI Steps

:buildkite: Lint

:hourglass_flowing_sand: Build in-progress, with failures

Buildkite Build
Commit: 7dc018deecfcc17c6e687ab91e4078e94b52990f

Failed CI Steps

:buildkite: Lint

History

:broken_heart: Build #151 failed 941caf55803457315449ac1fcf89c1e8e4e3f6c5

Needs https://github.com/elastic/elastic-agent-libs/pull/175

:green_heart: Build Succeeded

Buildkite Build
Commit: ee4b687493f991c24bbe52f5290a45351393cae3

History

:broken_heart: Build #154 failed 7dc018deecfcc17c6e687ab91e4078e94b52990f
:broken_heart: Build #151 failed 941caf55803457315449ac1fcf89c1e8e4e3f6c5


Make BuildableReference.blueprintIdentifier a PBXObjectReference

Resolves https://github.com/tuist/xcodeproj/issues/287
Short description 📝
Makes BuildableReference.blueprintIdentifier a PBXObjectReference
Solution 📦
The xml decoding doesn't have access to a context to get the references, so I just created a static var on ProjectDecodingContext, which isn't ideal but it works.

I'm not sure about that approach though. If you don't decode the project before the workspace, you can't get the object from the workspace. That dependency is very implicit and not obvious. I'd rather keep the attribute in the scheme as a string and provide an API to lookup the object in the project:
extension PBXProj {
  fun object(uuid: String) -> PBXObject? {

  }
}

What do you think?

@pepibumur I've removed the shared decoder and just store the string on decoding now. Let me know what you think

@pepibumur are you able to take another look at this?

That looks much better. This is ready to be merged 👍


scalajs support

I thikn scalajs support will be useful for some usecases. As you do not use any jvm dependnecies moving library to cross-project should not be hard.

I will do that in the near future. Thanks for the hint to the plugin. Problem is that sbt-pgp stops to work when including the cross-project plugin. It breaks publishing to maven-central.
You were right though. Scalacrypt compiles without any issues (at first glance) using scala.js.

roblem is that sbt-pgp stops to work when including the cross-project plugin

I personally do not use sbt-pgp, but I can look at your sbt configuration. Crossproject is not an sbt project but a wrapper that creates two sbt projects (one for JVM and one for JS). Try to run sbt-pgp on JVM and JS projects separately and check if it works (if yes, than it will be a matter of aggregating this two projects).
P.S.
I hope you did not forget to update scalatest to the latest milestone to run tests on both scalaJVM/JS
libraryDependencies += "org.scalatest" %%% "scalatest" % "3.0.0-M7"

Pushed changes to branch wip/scalajs-support. Tests are still failing, but i'll try to get it to work soon.

General rule of porting an app to scalajs is to: avoid runtime relfection, check semantic of regex (there are small differences between scalajs and scalajvm) and check all java parts that are used. I noticed
that you have usage of java.security in your code. I am not totally sure that all java.security was ported to scalajs, so it makes sence to check it or ask scalajs core devs about it ( the are active in  https://gitter.im/scala-js/scala-js gitter channel)


info: show locks of a certain file

Close https://github.com/juicedata/juicefs/issues/2625
> ./juicefs info /mnt/jfs/example
/mnt/jfs/example :
  inode: 55
  files: 1
   dirs: 0
 length: 1.56 KiB (1596 Bytes)
   size: 4.00 KiB (4096 Bytes)
   path: /mnt/jfs/example
 objects:
+------------+----------------------------+------+--------+--------+
| chunkIndex |         objectName         | size | offset | length |
+------------+----------------------------+------+--------+--------+
|          0 | myjfs/chunks/0/0/34_0_1596 | 1596 |      0 |   1596 |
+------------+----------------------------+------+--------+--------+
  flocks:
+-----+---------------------+------+
| Sid |        Owner        | Type |
+-----+---------------------+------+
| 49  |<PHONE_NUMBER>199279596 |    W |
+-----+---------------------+------+

Codecov Report
Base: 58.81% // Head: 58.31% // Decreases project coverage by -0.49% :warning:

Coverage data is based on head (547e520) compared to base (56f2f44).
Patch coverage: 27.84% of modified lines in pull request are covered.

:exclamation: Current head 547e520 differs from pull request most recent head c07b106. Consider uploading reports for the commit c07b106 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3001      +/-   ##
==========================================
- Coverage   58.81%   58.31%   -0.50%
==========================================
  Files         141      141
  Lines       24613    24921     +308
==========================================
+ Hits        14476    14533      +57
- Misses       8254     8488     +234
- Partials     1883     1900      +17

Impacted Files
Coverage Δ

pkg/meta/interface.go
45.45% <ø> (ø)

pkg/meta/tkv_lock.go
73.18% <0.00%> (-8.27%)
:arrow_down:

pkg/meta/utils.go
62.76% <0.00%> (-3.53%)
:arrow_down:

cmd/info.go
29.55% <11.11%> (-24.58%)
:arrow_down:

pkg/meta/redis.go
69.03% <15.15%> (-0.77%)
:arrow_down:

pkg/meta/sql.go
63.22% <21.73%> (-0.71%)
:arrow_down:

cmd/status.go
52.85% <30.00%> (-17.88%)
:arrow_down:

pkg/meta/redis_lock.go
68.79% <35.00%> (-5.59%)
:arrow_down:

pkg/meta/sql_lock.go
66.24% <50.00%> (-4.05%)
:arrow_down:

pkg/meta/tkv.go
74.13% <50.00%> (-0.31%)
:arrow_down:

... and 17 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Typo fix in models.py

Typo fix for Crital => Critical

any change in model definitions needs a new migration file.

any change in model definitions needs a new migration file.

Even for a minor Typo fix ?

yes, that's how Django works.

It would also have to be rebased on dev not master.

@SPoint42 in this case it might work if you also update the 0001_initia.py migration.

@SPoint42 in this case it might work if you also update the 0001_initia.py migration.

@SPoint42 I think in this case it might actually be sufficient if you change 0001_initial.py to include the same typo fix.

Hi @SPoint42

@SPoint42 I think in this case it might actually be sufficient if you change 0001_initial.py to include the same typo fix.

Do you want to do that? Cheers.

close by https://github.com/DefectDojo/django-DefectDojo/pull/4024


proposal: Add generic fail package to standard library for error handling

I have been trying out generics for error handling, and I found that it might be a good approach to consider, in stead of changing the language. Therefore I propose adding a new package to the standard library, named "fail", for now, which does such error handling, using fail.Check() and fail.Save() as the main API.
The interesting points about this approach are that error handlers can be defined and reused easily, that even the Check can be reused easily, though a combination of higher order functions, generics and panic/rescue, and that it is all very simple to use and to implement.
The weakest points are the need for Check2, Check3 ... functions for that return more results than just one and an error, although these are relatively rare in Go, that it requires named return values, and the fact that this does use panics behind the scenes, although this can also be seen as a benefit in a sense.
In a later stage then, if deemed necessary, some of these functions could be made built-in functions with the same semantics, but that can be considered after this proposal.
Below is a sketch of how this could work. It was tested only slightly, and probably needs to be improved a lot.
https://go.dev/play/p/jQRLjq-0pw0

import (
	"fail/fail"
	"fmt"
)

func div(a, b int) (int, error) {
	if b == 0 {
		return 0, fmt.Errorf("div: division by 0: %d / %d", a, b)
	}
	return a / b, nil
}

func mod(a, b int) (int, error) {
	if b == 0 {
		return 0, fmt.Errorf("mod: division by 0: %d / %d", a, b)
	}
	return a % b, nil
}

func maths() (r int, rerr error) {
	save := fail.Save(&rerr)
	defer save()
	check := fail.Check[int](fail.Decorate("maths error: %w"), fail.Print())
	r = check(div(12, 3))
	fmt.Printf("%d\n", r)
	r = check(mod(12, 7))
	fmt.Printf("%d\n", r)
	r = check(div(r, 0))
	fmt.Printf("%d\n", r)
	return r, nil
}

func main() {
	defer fail.Save(nil)
	decorator := fail.Decorate("main: error: %w")
	handler := fail.Print()

	fail.Check[int](decorator, handler, fail.Exit(7))(maths())
}
-- go.mod --
module fail
-- fail/fail.go --
package fail

import (
	"fmt"
	"os"
)

// checked are errors that this package can catch with Save or Catch
type checked error

// Check returns a function that will check the results from a function
// which returns (Result, error). If error is nil, Result is returned normally.
// If error not is nil, the handlers will be called one by one.
// If one of the handlers returns nil, the error handling stops and the
// check function will return the zero value of Result.
// Otherwise a panic will be raised which should be handled with
// [Catch] or [Save] .
func Check[Result any](handlers ...func(error) error) func(res Result, err error) Result {
	return func(res Result, err error) Result {
		if err != nil {
			for _, handler := range handlers {
				err = handler(err)
				if err == nil {
					var zero Result
					return zero
				}
			}
			panic(checked(err))
		}
		return res
	}
}

// Check2 returns a function that will check the results from a function
// which returns (Result1, Result2 error). If error is nil, Result1 and Result2
// are returned normally.
// If error not is nil, the handlers will be called one by one.
// If one of the handlers returns nil, the error handling stops and the
// check function will return the zero value of Result.
// Otherwise a panic will be raised which should be handled with
// [Catch] or [Save] .
func Check2[Result1, Result2 any](handlers ...func(error) error) func(res1 Result1, res2 Result2, err error) (Result1, Result2) {
	return func(res1 Result1, res2 Result2, err error) (Result1, Result2) {
		if err != nil {
			for _, handler := range handlers {
				err = handler(err)
				if err == nil {
					var zero1 Result1
					var zero2 Result2
					return zero1, zero2
				}
			}
			panic(checked(err))
		}
		return res1, res2
	}
}

// CheckErr is like Check but in case the function returns only an error
// and no values.
func CheckErr(handlers ...func(error) error) func(err error) {
	return func(err error) {
		if err != nil {
			for _, handler := range handlers {
				err = handler(err)
				if err == nil {
					return
				}
			}
			panic(checked(err))
		}
	}
}

// Catch catches the error in case it was raied by Check().
// Should be used only in a defer clause as follows:
//
// defer func() { err = Catch(recover()) } ()
func Catch(caught any) error {
	aid := caught
	if aid == nil {
		return nil
	}
	if err, ok := aid.(checked); ok {
		return (error)(err)
	}
	// Panic again if not a Checked error
	panic(aid)
}

// Save catches the error if raised by Check.
// I rerr is nil, nothing else happens, if it is not nil, the caught error
// will be stored in rerr
// Should be used only in a defer clase as follows:
// defer Save(&rerr)()
func Save(rerr *error) func() {
	return func() {
		err := Catch(recover())
		if rerr != nil {
			*rerr = err
		}
	}
}

// Print returns an error handler that prints the error message to standard
// error if there is one. Print appends a newline.
func Print() func(err error) error {
	return func(err error) error {
		if err != nil {
			fmt.Fprintf(os.Stderr, "%s\n", err)
		}
		return err
	}
}

// Decorate returns an error handler that decorates the error if there is one.
// The format parameter must be a valid fmt.Printf format,
// which contains a %w.
func Decorate(format string) func(err error) error {
	return func(err error) error {
		if err != nil {
			return fmt.Errorf(format, err)
		}
		return err
	}
}

// Exit returns an error handler that calls os.Exit() if there is an error.
func Exit(exit int) func(err error) error {
	return func(err error) error {
		if err != nil {
			os.Exit(exit)
		}
		return err
	}
}

@gopherbot add error-handling

For a pure library like this we would typically suggest that we try it out as an external package first and see what kind of adoption it gets.

Have you seen @dsnet's try? https://pkg.go.dev/github.com/dsnet/try This seems very similar.

@ianlancetaylor While I would normally agree with https://go.dev/doc/faq#x_in_std, seeing that error handling in Go is a hot topic, which has been looking for a solution for a decade, I am proposing we skip the step of the external package and get started with a design and then try it out in x/ as an experimental package.
I don't really care about the name or the details of the implementation, the idea is to use existing language features including generics to solve the Go error handling problem in a standardized way. Seeing how we now are getting slog for structured logging, which was also long overdue, I think it would be a good idea to cut to the chase, do to speak.
However I would also not object if this proposal were to be put on hold until there are a few similar packages like this.
@carlmjohnson I looked at it and while it is similar, my example has the benefit that the both the check functionand the error handlers are returned as higher order functions and can be reused. And also that I choose for more readable function namea. But one reason I made this proposal is for everyone to help out with the design. What I have is just something I cobbled together in a few hours.

Error handling happens a lot and is required to be efficient almost every time. I don't believe, that generics spread over closures and panics with their stack unwinding is the best tool for the job.

I am proposing we skip the step of the external package and get started with a design and then try it out in x/ as an experimental package.

I think Ian is proposing that you don't skip that step. Something as important as this should be carefully evaluated within a single large project (or company) before it pretends to be a good solution for everyone. There's no need to involve the x/ repos.


Client support for RetryPolicy as options

Considering retry is such a common scenario we should have baked in support on client to support retry for Activity/ChildWorkflow.  Currently consumers try to use off the shelf retry libraries to use within Cadence workflows but they are not going to work due to determinism requirement of workflow code.  Which means it is not allowed to use time.Now but instead to code should use Cadence.Now to make sure it is deterministic.  This requirement means that any retry library should be built using Cadence.Now to make sure it can be used within workflow logic.
One idea is to have Cadence client natively support such a retry library which is exposed as an interceptor using ActivityOptions and ChildWorkflowOptions.  It may be interesting to expose such interceptors as extensions for consumers in case they to extend interceptor chain with custom interceptors of their own.

Retries already covered in client: https://cadenceworkflow.io/docs/03_goclient/06_retries


intellicode does not working on anonymous class method (Java)

when I select “initialValue” method,Intellicode generates these:

Oh！MyGod，what's Wrong?

I can reproduce it, but it's not an IntelliCode issue. After disabling IntelliCode, it's the same.

It's may be VSCode's problem ? Can you solve the problem，It's so  inconvenient

I've created an issue in the correct place, you can track it there.

Okay，Thank you


"Beautified" code is copied and re-inserted at cursor position. (v0.28.11 - Windows 7)

Following update to v0.28.11, running Atom Beautify now causes editor contents to on occasion be copied and re-pasted from the current cursor position.
While not all languages have been tested, this behaviour does appear to take place with both Javascript and HTML files, so it is clear that this issue is not limited to a single language.
Due to the 'erratic' copying behaviour, this issue can break user's code if the result of the issue is not immediately visible (as happened to me yesterday).
This issue is visible on Atom v1.0.6, running on Windows 7 with Atom Beautify v0.28.11. Other configurations have not been tested at this time.

Following update to v0.28.11

What version were you on before? This has only started happening recently?

Due to the 'erratic' copying behaviour, this issue can break user's code

Absolutely, it would.

running Atom Beautify now causes editor contents to on occasion be copied and re-pasted from the current cursor position.

There are other issues that describe this happening, especially when you have selected text with your cursor. Check out a few at https://github.com/Glavin001/atom-beautify/search?utf8=✓&q=duplicate+code&type=Issues
The only way this makes sense is if Atom Beautify is detecting that you have text selected when it attempts to re-apply your beautified code back to your editor. I would recommend doing some debugging yourself -- I have been unable to reproduce this bug since people started experiencing it. First, you should add some additional logging.
See https://github.com/Glavin001/atom-beautify/blob/df569a9f4ed80dc22d4bcd345ba709851067fa16/src/beautify.coffee#L115-L123 for the applicable code.
It would be important and useful to see that Atom Beautify is choosing to setTextInBufferRange instead of simply replacing the entire editor's contents with setText. I would recommend adding logging statements for both of those conditions.
If setText is being called and it is causing this issue where it duplicates your code at the cursor position, then this is an Atom bug, since setText should replace the entire text editor buffer. I doubt this will be the case.
If setTextInBufferRange is being called then the problem is with Atom Beautify detection if the User has currently selected text. See https://github.com/Glavin001/atom-beautify/blob/df569a9f4ed80dc22d4bcd345ba709851067fa16/src/beautify.coffee#L115
for code if not forceEntireFile and isSelection. I would recommend also logging the forceEntireFile and isSelection variables. If this is the case, which I think you will find it is, then it has to do with the code at https://github.com/Glavin001/atom-beautify/blob/df569a9f4ed80dc22d4bcd345ba709851067fa16/src/beautify.coffee#L116 selectedBufferRange = editor.getSelectedBufferRange(), for incorrectly retrieving the selected buffer ranges of your cursor. This means that Atom has detected you have selected text, and is beautifying and replacing the text of only your selected text.
Note that the logic for detecting if a user has selected text and for replacing only the selected areas, is performed in the beautifyCompleted callback. I think this is where the bug could be. Part Atom Beautify bug, part human-error: if the user were to run beautify, then select some text, even accidently, then when the beautification is complete it would then detect if the user has selected text. Since the user originally did not have selected text, it took the entire file and beautified it. See https://github.com/Glavin001/atom-beautify/blob/df569a9f4ed80dc22d4bcd345ba709851067fa16/src/beautify.coffee#L166-L172 for applicable code.
Then when beautifyCompleted, the user had selected text now and it replaced only that text area, with the beautification results of the entire file which was beautified.
Let me know what you think and how the debugging goes. I may look in to improving the current code such the logic for detecting if the user has selected text is outside of the beautifyCompleted callback. If my assumptions are correct, then this will fix this bug. However, if you do not have selected text, and it is calling editor.setText then this is an Atom bug, which would be surprising.

Hi,
My sincere apologies for the delay in getting back to you. After restarting my machine on Friday, I have been trying to replicate the issue I was experiencing, but I have failed to do so.
I have no idea what went wrong, but it seems to have fixed itself following a restart of the PC.
In hindsight, I should have definitely checked this before adding a new GH issue, for which I apologise. - I won't make the same rookie mistake again!
Unless anyone else has reported this issue, I would say this issue can now be closed. Should I experience any of the symptoms again, I will follow the debug instructions first prior to raising another bug.

Update:
One thing that I have noticed this afternoon (but not sure if it is necessarily related) is this:
Take this LESS code:
div.panel {
    padding: 0 !important;
    border: 0 !important;
    margin: 0 !important;
    border-radius: 0 !important;

    > div.panel-heading {
    border: 0 !important;
    background-color: #f3f3f4 !important;
    }
    > div.panel-body {
      padding: 0 !important;
    }
  }

After I run Beautify on it, I get left with this:
  div.panel {
  padding: 0;
  border: 0 !important !important;
  margin: 0;
  border-radius: 0 !important !important;
  > div.panel-heading {
    border: 0 !important;
    background-color: #f3f3f4 !important;
  }
  > div.panel-body {
    padding: 0 !important;
  }
}

(All indentation is exactly as returned by Atom Beautify).
This obviously causes issues with the LESS compiler (e.g. !important !important). If you agree, I will raise this as a new bug.
Thanks

After restarting my machine on Friday, I have been trying to replicate the issue I was experiencing, but I have failed to do so.

I am going to close this issue then.
Glad to hear it is working :smiley:.

For the other problems, please create a new issue, if you are still experiencing it.


JOSS review: main theoretical issue

Dear authors,
Hereby an issue to track the main point raised in my review of the work you have submitted to JOSS. See the review thread here.
First of all, let me congratulate you on the excellent technical state of your package. The documentation, tests, code quality are all top-notch. However, in my opinion an important issue needs to be addressed before the work can be considered for publication in JOSS (note that the editor may disagree!)
The main issue I have is with the statement of need. It is unclear, both in your paper and in your documentation, when I would want / need to use lintsampler.
First, a better description of relevant real-world research situations is needed. It needs to be better than

For a small number of well-studied probability distributions, optimised algorithms exist to draw samples cheaply. However, one often wishes to draw samples from an arbitrary PDF for which no such algorithm is available.

As an external reader, I may disagree with the "a small number of well-studied probability distributions", as there is a large number of probability distributions, which cover a wide range of real-world situations from which sampling is relatively easy to do (e.g., your GMM example which is easy to sample from without lintsampler). What research problem that you envision does not fall within this set of distributions?
Second, and more pertinent: you do clearly contrast your method to more complex methods such as MCMC, but you fail to compare it to simpler methods like importance sampling. Currently, information is lacking: when is your method preferred over simpler methods? Does it scale well in higher dimensions? Is it computationally more efficient? What is the advantage?
# Example of importance sampling
propdist  = uniform(-12, 24) # or normal(0, 4) or student(2) or ...
proposals = propdist.rvs(1000)
weights   = pdf(proposals) # / propdist.pdf(proposals) not needed because uniform!
samples   = np.random.choice(proposals, 1000, p=weights / weights.sum())

In particular, I was curious about whether importance sampling could even be better than lintsampler for the same number of samples. The results from my tests — using the examples from your documentation — indeed seem to indicate that importance sampling with a uniform proposal distribution can perform better in those cases. The advantage will only grow with better proposal distributions. The comparison is available in this GitHub gist.

I agree with @vankesteren's comments here and would also like to see the statement of need clarified - I would also echo @vankesteren point that the technical quality of the package here is great, and it might be that the points were are raising here are out of scope for the JOSS review process.
In

We anticipate lintsampler finding use in many applications in scientific research and other areas underpinned by statistics. In such fields, pseudo-random sampling fulfils a myriad of purposes, such as Monte Carlo integration, Bayesian inference, or the generation of initial conditions for numerical simulations. The linear interpolant sampling algorithm underpinning lintsampler is a simple and effective alternative to existing techniques, and has no publicly available implementation at present.

you state that pseudo-random sampling can be used for purposes such as Monte Carlo integration or Bayesian inference. To my mind the latter is a specialised subset of the former - the end goal of sampling in Bayesian inference is typically to form Monte Carlo estimates of intractable integrals such as posterior expectations or model evidence terms. In the context of estimating integrals, the linear interpolant sampling algorithm implemented in lintsampler, as it relies on some form of tensor product grid on the space being integrated over, I believe will have a computational cost (in terms of the number of evaluations of the integrand / density function)  which scales exponentially in the dimension of the space to achieve a given approximation error. This I think puts linear interpolant sampling in the same computational complexity bracket as numerical quadrature rules for multidimensional integrals based on tensor product grids. Given there are a wide variety of numerical quadrature rules available with well understood numerical convergence properties and a range of Python implementations available, my question would therefore be when / in what sort of problems should a user approximate an integral using linear interpolant sampling rather than a numerical quadrature method?

In response to these comments, we spent some time coming up with a more quantitative treatment of when exactly a user might wish to use lintsampler over an alternative technique. To summarise, we came up with 4 'use cases'. The use cases are distinct, but we nonetheless described a 'real world' scenario (drawn from our own research) that encapsulates all of them at once. We've listed these in the paper's Statement of Need, and also added a page to the docs ('When to use lintsampler) which contains largely the same content.
The four use cases are reflected in the four example notebooks in the docs; we've made this explicit in the paper. We've also updated these notebooks to include some code comparisons with alternative techniques. In particular, notebook 1 in the docs now includes a comparison with importance sampling, and notebook 2 now includes comparisons to both importance sampling and MCMC.
You can see all of these changes in the joss-major branch of the repo. There is an associated PR (#12) which can be merged into main once you have had a chance to review the changes. To see a built version of the edited docs, you can choose joss-major as the 'version' on the readthedocs page (using the interface at the bottom-left corner).
Some more detailed comments responding to some of your points above:

@vankesteren: in the example you wrote up in your gist, importance sampling outperforms lintsampler, but this is because lintsampler is being used with a very coarse grid. If you increase the grid resolution, lintsampler manages to achieve a comparable log-likelihood to importance sampling. This is actually a point in lintsampler's favour, because you can get there without too fine a resolution, and so you can achieve comparable performance to importance sampling with far fewer PDF evaluations. We've written this point up as the first 'use case', and shown this explicitly in the first example notebook.
@matt-graham: We agree with your assessment that the computational cost scales exponentially with the number of dimensions. We've added a 'caveat' in the Statement of Need indicating that lintsampler would rarely be the method of choice for a high-dimensional problem.


RetrieveMultiple Filter is set to FetchXml

There is a bug in the RetrieveOptions:
if (!string.IsNullOrWhiteSpace(Filter))
    query["$filter"] = FetchXml;

It's using the FetchXml parameter instead of Filter.

Thanks!
I'll gather more changes and generate a new nuget version in the coming days.

Hi @RafaelCavazza,
that's great to hear. Any news on the new version? :)
Cheers
Michael


Website Builder Stabilization & Feature Requests

Hey Adam!
I apologize for the continued website builder issues; I'm starting to feel like Navi giving side quests. But unlike Navi, I want to say, "thank you for your help!"

Website Builder Side Quests 🗡
🔥 = High Priority
⚡ = High Impact
🧑🤝🧑 = Highly Requested
🧚 = Wish List
Vickie Specific Bugs

[x] 🔥About Page Body: I don't understand why, but the "body" section of this page will not let me edit it, no matter what I do

[x] See "CTA Buttons - Allow Total/Partial Removal" Styling Issues Below

Stabilization, Guardrails, & General Improvements

[x] 🔥⚡Deploy Delay: It takes a while to see changes after hitting deploy button.
[x] 🔥⚡Caching Issues Whatever's going on with caching being too strong
[ ] ⚡Empty Homepage Protection Warn people if they are about to deploy a website without an index page
[x] ⚡Protect Homepage Slug: Warn people when they change the index page slug
[ ] #41
[x]  ⚡ Add DNS Settings to handle WWW before domain name:   -- Still trying to figure this one out give me a few.
[x] ⚡Domain Documentation Text on Domain Page: Add text and the documentation link to the page. Suggestion Below:
See our documentation for guidance in purchasing and connecting a domain name.

General Styling

[x] 🧑🤝🧑 CTA Buttons - Allow Total Removal: If you delete all the links for the CTA buttons, the white container remains there empty (see below).
No Buttons, Yes Newsletter - If there is a newsletter module, the newsletter should move up to take the currently empty space.

No Buttons, No Email - If there aren't buttons or newsletter module, let's remove the white container.

[x] CTA Buttons - Allow Partial Removal (top or bottom): Adding an option to "Show CTAs only at top of page" and "Show CTAs only at bottom of page" would be helpful if not too difficult.

[x] 🔥 Navigation Alignment: The navigations are centered now instead of left aligned. See screenshot below:

[x] Volunteer Form Button - Right Aligned: The volunteer form button should be left aligned on homepage and volunteer page.

Adam's Note: I disagree! When you submit things, it's in the bottom right. Cancel / delete is in the bottom left. Perhaps just make the button wider?

[ ] ⚡Improved Un-launched Website Lander: When websites haven't been paid for, show this screen (see below). Figma File.

[x] ⚡Improved 404 Error: Navigation, Header Style with Text, Footer. Figma File.

[ ] #42

[ ] #43

[ ] #44

[ ] #45
Example 1 - Homepage About Image -- I wish I could set that to be a tall image instead of square so long text beside it would look better.
Example 2 - When putting an image in the editor, we can current decide an images alignment, but not size. They're often too large on their own.

Page Types

[x] 🔥Hide Donation Page Type: We should hide the donation page type from people for now. We should also only show it to people if they have the "Fundraising" feature flag on if that's possible?

[x] Update Templates Page: I made this simple version for the template page for now. Figma file.

[x] Rename "Home Page" to "Landing Page": People will still be able to use this template if they want, but we don't want them to delete their main home page now. In the future we can create a button for "set this as home page," but for now let's just rename this template to be less confusing.

Home Page

[x] Endorsements Section: Don't show the "For Identification Purposes Only" text if none of the endorsements are for identification purposes only
[ ] 🧚 New Content Modules: New content block that we could add to the homepage.
Ideally with a few options - 1. Just content. 2. Image on right, Content on Left  3. Image on Left, Content on Right.
Ideally that we could move above or below other blocks.

Endorsements

[x] For Identification Only Button: This button currently doesn't do anything. All endorsements are just automatically marked "For Identification Only"

[x] Text-only Endorsements Show Up Twice: When adding a text only endorsements show up on the left and right side. Might as well nix the right side entirely and center the stuff on the left?

[ ] Center endorsements on page

Petitions

[ ] Petitions Data: Where does the data for people who sign petitions go?
[ ] Zip Code Button Not Showing as clicked, but is added to page: Once you've added "zip code" to a petition, it doesn't show as clicked, but it is added on the right side of the page. It's impossible to then remove the zip code from the page.

News

[ ] Article Order Weird: It seems like news articles stack in a weird order not based when they were added or what order they are in the sidebar. See below (records without images) and (records with images)

[ ] Collection Cut Off When Adding New Record: The drop down that lets you select collection is cut off

[x] Article Filters Not Working: Once deployed, the articles don't sort when you click on the categories
See example here: https://example.campaign.win/news--zcn0hbbfgy

closing in favor of standalone tickets 🙏


Individual reported an abnormal payment

http://explorer.gridcoin.asia/tx/f6682b8ce0bd901c748f3a8ea88f44e56ff610178a890b029f2e55f75415e96d
http://explorer.gridcoin.asia/api/getrawtransaction?txid=f6682b8ce0bd901c748f3a8ea88f44e56ff610178a890b029f2e55f75415e96d&decrypt=1
http://www.gridcoin.co/?cpid=42cd7cb96d8cae69169906fa4a52157a
http://www.gridresearchcorp.com/gridcoin/?cpid_dashboard&CPID=42cd7cb96d8cae69169906fa4a52157a
Individual reported his mag jumping from 30 to 360, then received a 7500 GRC DPOR payment which is higher than his expected payouts.

Actual guy that this happened to.
http://puu.sh/qHzXv/c3a552750f.jpg
Returned after 5 months without staking. I had a machine running and had a 20 mag. I started staking a few days ago and doing a few projects. Resent a beacon a day or two ago too. Just a few minutes ago, mag jumped to 360 and I got the three payments seen in pic. Actual mag should be 60.
Thanks.

Here is the debug.log: [https://drive.google.com/open?id=0B23ck3hMqiHaWHFjSklNN09qVUU]
Db.log was empty...
Thanks.

Thanks, well there are a lot of components to this, and fortunately I can see most of what happened and we can try to reconcile this.
The calculation payment amount itself is correct but based on the wrong magnitude.
We can see his last POR block was 169 days ago, and with a prior mag of 20 and a bad reported mag of 360, our system believes he has an average mag within that span of 222, and the GrcMagUnit was .20 at the time.
Thats 169222.20 = 7503.60 grc.  That was taken from the daily kitty, so therefore it was paid in full.
The real issue is, how did we assess his mag at 360?  I assume somehow the neural network pegged him at 360, and he was already in the superblock at 360 before he fired up the machine to stake and thats where the figure came from (prior neural network consensus of 360 in the superblock).  Putting his avg mag at 222 for the block span.
So, Ill have to take a look at the superblock next for anomalys.  There is a high liklihood that if his was off, some other project was calculated too low.  Usually what happens is, if a segment of our researchers download lets say 90% of the project files, and the same network sites are down for the whole group, that would raise the mag up extrordinarily for the projects In the superblock, and down to 0 for the missing projects.  Most likely we had a consensus at the same time, resulting in a bad superblock that day.
Ill look into the superblock.
Thanks for reporting this.
Rob

Looking at the superblock it looks like the problem is it only contains mags for projects:
asteroids@home: 13000 - 2944285.71
atlas@home 1560 - 134000
burp 2960 - 203333.33
giving people huge GRC for those 3 projects... today only (hopefully).
Ill check the neural network to see if its going to stake a good block tomorrow.

Odd, since I haven't crunched for Atlas or Asteroids in months, and not even that much to give me a decent mag then.

Yeah, I see what you mean - Im looking into this superblock deeper.    You dont even have mag on asteroids atlas and burp:
http://cpid.gridcoin.us:5000/get_user.php?cpid=42cd7cb96d8cae69169906fa4a52157a
But, continuing where we left off yesterday, those 3 projects that I posted were the only projects with network averages in the superblock, so I guess what I failed to test next is the problem of missing averages.  IE if we only gathered network averages for 3 projects, would that not drive up the mag for projects other than these 3 (needs to be tested).

I am actually crunching on BURP right now but the mag should be around 35. I'm also crunching on Mindmodeling, GPUGrid, Distributed Data Mining, SZTAKI (no WU yet), and WUProp.
Additionally, my Actual PPD shows to be 539, and my fulfilment % is 748.61 as of right now.

Ok yes, I see BURP on the link I posted 2 messages ago now - thought it was in alphabetical order at first.  Yeah I see avg RAC of 1956 on it.  Anyway to summarize, we somehow had a bad superblock, and with 93% of the projects missing in it, you were assessed with a higher mag on Burp due to the lack of competition.
(Your mag is 60 right now on my external node) if nothing else changes today.  We have half a day left before the new block starts to stake.
Most of the time this problem would have been much less severe if the span wasnt so long between blocks and it happened, but it was.

Updating to say that I just got PoR of ~71 GRC. Mag got cut in half and it seems like NN was counted my projects twice. With a 30 mag, I should get about 6 GRC, so I don't know if the problem is still persisting.
Also, NN still shows my mag as 360 and it got put on the site too: http://www.gridresearchcorp.com/gridcoin/?cpid_dashboard&CPID=42cd7cb96d8cae69169906fa4a52157a
Thanks.

Hi AEM, thanks man.  Well if you want I can show you some of the fields in 'showblock blocknumber' that explain the reward (its an average of your last stake, current stake and duration between).  The 360 being posted on researchcorp is correct - its your last staked block when the magnitude was elevated.  His site has not counted your new stake yet.
What block number did you stake for 71 grc?  You can double click on it to see.
Im planning on chalking this issue up as a bad superblock, a one time occurrence where your payment was elevated due to lack of competition in that particular days emissions.  We can do that after we prove your client stabilizes and the last block shows correctly on RTMs dashboard.

Block number is 641527.
Mag as dropped to 75 but actual PPD is still 544, which I'll assume won't affect me.
Thanks.

Looking at your last 5 POR stakes, it looks like they all occurred within 24 hours of block 640444 and all of them had the 360 magnitude (since they were based on 640444s super block).
Im waiting to see your next POR block, one based on 641973 (the last superblock).  Please post your next POR block # and Ill take a look at it and see if your average mag drops.  Yeah, the PPD will just go down over time, it is used for certain BL, but since you have been researching for such a long period it wont cause any alarms in the payment check function.

Has the superblock recovered? Whilst this was occurring, my neural network window had all the stats compared to only 3 in the staked superblock.

It looks like he got two stakes @75 mag, so I think we are going to be OK:
http://www.gridresearchcorp.com/gridcoin/?cpid_dashboard&CPID=42cd7cb96d8cae69169906fa4a52157a
AEM, does your list rsa look pretty good now , and how do the last 2 PORs look to you?

I haven't gotten any PoR's since I last posted about getting one with 71 GRC. I don't know if you are referring to that one and the one before that that I got for 2.1 GRC, or another two that I cannot see in my client.
Here is my list rsa: ￼ [ { "RSA Report" : "1471994965" }, { "CPID" : "42cd7cb96d8cae69169906fa4a52157a", "PoolMining" : false, "RSA Weight" : 0.00000000, "RSA block count" : 7.00000000, "Last Payment Time" : "08-21-2016 02:54:08", "Earliest Payment Time" : "12-04-2015 06:35:12", "Magnitude" : 75.00000000, "Research Payments (14 days)" : 7613.92000000, "Interest Payments (14 days)" : 11.05000000, "Interest %" : 0.02170149, "Daily Paid" :<PHONE_NUMBER>7, "Expected Earnings (14 days)" :<PHONE_NUMBER>0, "Expected Earnings (Daily)" : 15.00000000, "Fulfillment %" : 3623.26068335, "CPID Lifetime Interest Paid" : 16.70000000, "CPID Lifetime Research Paid" : 11329.57000000, "CPID Lifetime Avg Magnitude" :<PHONE_NUMBER>7, "CPID Lifetime Payments Per Day" : 42.96152793, "Last Blockhash Paid" : "a04214c5e68e4772f05c8600ab0c922ff6aa45556ac3daeadb71e3862a7fbdaa", "Last Block Paid" :<PHONE_NUMBER>0000, "Tx Count" : 75.00000000 }, { "Magnitude Unit (GRC payment per Magnitude per day)" : 0.20000000 } ]

Oh sorry, you are correct, looking a little closer: Your last por stake was 641527 still, which was before our last 2 "normal" superblocks that contain your normal mag of 76 (the superblock After 641527 was 641973.  So I guess we still need to wait a while for you to stake a POR then we can look at it :)

No PoR in 5 days, and I've been staking for 4 days since 16 hours a day. Maybe that lump of GRC made the system think I got my PoR for the next few years?

https://cryptocointalk.com/topic/1331-new-coin-launch-announcement-grc-gridcoin/page-1174#entry222631
Individuals in cryptocointalk have reported the same neural network issue occuring again?

Hi Aem,
Yes looking at the block validator code, yes, the issue is a stake wont be approved til your daily paid drops to 75.  As of a few days ago you had Daily Paid :<PHONE_NUMBER>7, and expected PPD of 15.  Once you drop below 75, it should stake again.  I realize that might take 60 days to water down, but we can leave this issue open until you stake.
GrcTest, when you say "same issue" do you mean we staked a bad superblock today and people have high mags?

@gridcoin I mean users are reporting in the announcement thread that we staked a bad superblock again, one user says he only sees the one project (yoyo@home) in the latest superblock. I have been unable to verify my neural network because attempting to open the neural network window froze my client.
I've ran 'execute syncdpor2' to get an accurate neural network.
Shall we create a separate github issue for superblock inaccuracies rather than posting in this issue?

Yes please open another issue on github.

Here is my latest PoR id: c1383f9cbbd20cd3acb2074d10c5fe33b0cc0ec230b7b597ecbcc9aead6c1de6-000
I got ~410 GRC.
Thanks.

Another 2 PoR's: 1bae00ed0d1a29847f8e31b7d7a7b40bf29da632369563bab9130d0096722bc5-000
10cc149291d5a038368434f58e040103031b96885fde35c5036227f8585f03f8-000
Seems like I'm getting PoR's again.

I also got an abnormal payment which I can not explain:
16fc14628af9d7fa828ff38fb02fc44fb6fe7992931ba211a121d457a2d2655b-000
This is the CPID
http://www.gridresearchcorp.com/gridcoin/?cpid_dashboard&CPID=1a7c8f7bbe5a14b0c1e205af3bd2d3d5


Task101/vep add more mf attribs

Requirements
There is a dependency on merging the PR to ensembl-vep first: https://github.com/Ensembl/ensembl-vep/pull/703 The PR 703 will add new key value pairs to the VEP output which are tested for in ensembl-rest/vep.t
Description
We are adding more keys to the VEP REST endpoint output. We are adding binding_matrix and transcription_factors to a motif_feature_consequences array. So far the tests in vep.t only checked return values for the transcript_consequences array. We are adding tests for motif_feature_consequences and regulatory_feature_consequences arrays.
Use case
Use VEP endpoint to annotate any overlaps with transcripts, regulatory or motif feature. For each overlap we calculate the variant consequence and depending on the feature add additional values.
Benefits
Adding  binding_matrix and transcription_factors information provides more detailed description of the variant motif_feature overlap.
Possible Drawbacks
Users might not be aware that we are returning two new key value pairs which can potentially break parsers.
Testing
Added tests to vep.t to test the expected structure of VEP endpoints.
Changelog
[/vep/*] VEP endpoints updated to contain transcription_factors key for motif_feature_consequences.

https://github.com/Ensembl/ensembl-vep/pull/703 has been merged.

Tests (phenotype_region.t, variation.t, phenotype_gene.t) fail because of a new variation database patch for release 101 which hasn't been applied to the variation rest test database.


Adds flake8 and isort tests to teamcity

This PR adds flake8 and isort tests as steps in teamcity.

@timgraham are the flake8 errors in the output here valid? I thought one of your earlier PR's should have fixed the flake8 errors.

The build seems to be failing with an invalid pointer error from docker-credential-helpers.

I’m not sure about that error(it’s reoccurring consistently), but it doesn’t stop the build — look further down the output at the flake8 errors

Need to cd into the cockroach-django directory. The errors are coming from other files like /docker_root/home/agent/.local/lib/python3.6/site-packages/entrypoints.py

That makes sense. Thanks for the guidance, I've never used these tools before.

I'm going to merge this, please rebase your PR's onto here to get these checks to pass.


Support Local LLM Models。

🚀 The feature
I run a local model by node-llama-cpp。I hope To use it。
Motivation, pitch
I will make another application of end-side large model, using node-llama-cpp to run the end-side large model, hoping to realize the function of RAG.

This is supported from version 0.1.18


Problem with logging in client

Hi! It's ignoring my pressing the authorization button on logging in.
Log:
downlords-faf-client.log
downlords-faf-client.log.2019-08-19.0.gz
Trying whatever it be from http://forums.faforever.com/viewtopic.php?f=3&t=17912:
open the powershell (Windows + R -> powershell -> enter) and type
tracert lobby.faforever.com
Results:

Please help! Reinstalled the client, still it's stuck on that button.

Via your logs i see message like:
Unfortunately, you must currently link your account to Steam in order to play Forged Alliance Forever. You can do so on https://www.faforever.com/account/link
So try to go there and link Steam account to your faf account.

Thx. Hope it is the solution. But it writes:

Sorry, but how to delete other unnecessary old account?

@ChevalierMinor Wait until evening (by CEST), leave some contact on you, maybe join https://discord.gg/97GdKX somebody will help you, or/and make topic on forum  http://forums.faforever.com/viewtopic.php. I'm pretty sure that somebody will appear and help you ;-)

Thank you! ^_^


Find Appointment by patient (name)

completed! can be used to build other features that need this as a building block


Running kuttl e2e testing with Makefile

Fixes #20.
With this PR, we can run the e2e tests using a make test-e2e entry. For running e2e tests, run make install-kuttl, and then make test-e2e.

/lgtm
/approve


about coordinates

How to reproduce

Leaflet version I'm using:1.1.0
Browser (with version) I'm using:chrome
OS/Platform (with version) I'm using:
step 1 Ubuntu
step 2

What behaviour I'm expecting and which behaviour I'm seeing
when i used freeDraw.on('markers', event => { console.log(event.latLngs); });
it shows based on the coordinates of the canvas，and i want to be based on the coordinates of the picture.
how should i do ? thanks!
Minimal example reproducing the issue

[ ] this example is as simple as possible
[ ] this example does not rely on any third party code

Using http://playground-leaflet.rhcloud.com/ or any other jsfiddle-like site.

Hi and thanks for using Leaflet!
Please note that this is our issue tracker, where bugs and feature requests and posted and discussed. For questions on how to use Leaflet and other support, you're better off using stackoverflow or gis.stackexchange.com.


Use SHOW CREATE TABLE to obtain table location

Direct accessing metastore does not work correctly in kerberized
environments.

AC

Released os 179


Error page (404) nested in layout.ejs

When a non existant URL is requested the 404 error page shows which is great. But when I look at the source I see the 404 page nested in the layout page resulting in two nested <html>, <head>, <body>, etc.. tags. This has to be a bug.

This has to be a bug.

Hey @netlander, by default all of your HTML views are served wrapped in layout.ejs.  You can disable layouts and use partials instead.

(See http://sailsjs.org/documentation/reference/configuration/sails-config-views for more info on disabling layouts)


TaskflowAPI._raise_flow_exception() crash when setting longer status than allowed by model

Something I noticed while writing tests for #1948. There is a limit for status length in the LandingZone model, but _raise_flow_exception() does not follow that.
This, or similar behaviour elsewhere in code, MAY be the root cause for #1458 and/or #1894. I'll have to look into it further.
I will also have to rethink the implementation of the maximum status length. Maybe allow for maximum db value in model, truncate when displaying? The status updating is to be revamped anyway, see e.g. #1614.
For now, this obvious bug should be fixed.

The root cause is LandingZone.set_status(). It should not allow status strings longer than what the database allows. Fixing that one for now.

Fixed.


feature-wip new insgestion load

Proposed changes
Issue Number: close #xxx

Could you describe what is the pr doing?

Could you describe what is the pr doing?

I added a description, and for now, the main purpose is to externalize the preprocessing stage of spark load and decouple it from the doris core.
At the same time, some security issues can be reduced by excluding spark dependencies.

great job.

run buildall

run buildall

run buildall

run buildall


[WIP] Functionality to change scoring method of searchlight

Enhancement as discussed in #3475. Aim to support
sl = SearchLight(LogisticRegression(), scoring=roc_auc_score)
score = sl.fit(X, y).score(X, y)

score = cross_val_score(SearchLight(LogisticRegression()), X, y, scoring='roc_auc')

I think the current design won't work, notably because we need to change the type of prediction as a function of the scoring. e.g. if you pass a roc_auc_score, the prediction should be continuous (e.g. predict_proba or decision_function) and not discrete (this is probably the cause of your error). Check how this is handled in sklearn cross_val_score.
Additionally, could you add tests to make sure that this is working:
SearchLight(Ridge(), scoring=my_scorer())
cross_val_score(SearchLight(Ridge()), X, y, scoring=my_scorer())

And once it passes, update the GeneralizationLight too

@kingjr I am not sure what should be done now.

@kaichogami make CIs happy?

@agramfort yes, however I don't know how to solve the issue with `cross_val_score(clf, X, y, scorer='roc_auc').

you cannot obtain more than one value per fold with a sklearn scorer. If you have multiple targets you need a custom scorer that return more than a float
so
cross_val_score(clf, X, y, scorer='roc_auc')
simple cannot work as is.

@agramfort I think there is a confusion between multiple issues:

SearchLight involves multiple scores, so cross_val_score(SearchLight(), scoring='roc_auc') is not viable with the current sklearn API. IMO scoring metrics need not output a float by principle. Confusion matrices are a form of scoring metrics. In any case this debate is not to be discussed here.

We want to be able to parametrize the SearchLight scoring e.g. SearchLight(clf, scoring='roc_auc'). However this involves
i) internally adapting the predict function: if you want to score with an AUC, you need to ensure that the predict function outputs an array of floats (e.g. distance to hyperplan, proba etc) and not of integers.
ii) identifying or handling 2 or multi class problem: i.e. predict_proba generates a y_pred, of shape (n_samples, n_classes), which can therefore not be passed to the sklearn roc_auc scorer. This is an API problem, not an intrinsic one, because we could in principle identify that there are 2 classes and compute the AUC. In case of multiclass, we could compute each auc and return the average AUC. All this should be solved/able at the sklearn level IMO

does using check_scoring function from sklearn help?
see also implementation of make_scorer function.
a sklearn scorer made from a string knows if it needs proba or decision
function or just predict.

@kaichogami how are we doing over here?

@kingjr I haven't touched it after my last comment. I'll look over it again and let you know if I can solve it, in few days.

@kingjr as Alex mentioned we need to design custom scorer to make cross_val_score(clf, X, y, scorer='custom_scorer') work. Or we will have to use it the other way you mentioned i.e, cross_val_score(make_pipeline(SearchLight(Ridge(), scoring=roc_auc_score), X, y). I think using the second option is more viable than creating many custom scorers.
Also as we have used make_scorer it should know whether it requires proba or decision
function or just predict.
Let me know what you think.

+1 for the second option
Le 15 sept. 2016 04:19, "Asish Panda"<EMAIL_ADDRESS>a écrit :

@kingjr https://github.com/kingjr as Alex mentioned we need to design
custom scorer to make cross_val_score(clf, X, y, scorer='custom_scorer')
work. Or we will have to use it the other way you mentioned i.e,
cross_val_score(make_pipeline(SearchLight(Ridge(),
scoring=roc_auc_score), X, y). I think using the second option is more
viable than creating many custom scorers.
Also as we have used make_scorer it should know whether it requires proba
or decision
function or just predict.
Let me know what you think.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3502#issuecomment-247266229,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEp7DFyuxUM0RqRHU3PW7xnUZXGOI4S6ks5qqP-MgaJpZM4JfX2t
.

Apologies @kingjr, the above design wouldn't work as well. We are now returning one value per fold, however we still have an array of score, one float for each estimator and this line does not allow score to be anything other than a float, which makes sense. Error output
Traceback (most recent call last):
  File "/home/kaichogami/codes/dev_mne/env/local/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/kaichogami/codes/dev_mne/mne-python/mne/utils.py", line 791, in dec
    return function(*args, **kwargs)
  File "/home/kaichogami/codes/dev_mne/mne-python/mne/decoding/tests/test_search_light.py", line 66, in test_searchlight
    assert_array_equal(cross_val_score(make_pipeline(sl), X, y), score)
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/cross_validation.py", line 1480, in cross_val_score
    for train, test in cv)
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/externals/joblib/parallel.py", line 800, in __call__
    while self.dispatch_one_batch(iterator):
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/externals/joblib/parallel.py", line 658, in dispatch_one_batch
    self._dispatch(tasks)
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/externals/joblib/parallel.py", line 566, in _dispatch
    job = ImmediateComputeBatch(batch)
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/externals/joblib/parallel.py", line 180, in __init__
    self.results = batch()
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/externals/joblib/parallel.py", line 72, in __call__
    return [func(*args, **kwargs) for func, args, kwargs in self.items]
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/cross_validation.py", line 1593, in _fit_and_score
    test_score = _score(estimator, X_test, y_test, scorer)
  File "/home/kaichogami/codes/dev_mne/scikit-learn/sklearn/cross_validation.py", line 1653, in _score
    % (str(score), type(score)))
ValueError: scoring must return a number, got [ 1.  1.  1.  1.  1.  1.  1.  1.  1.  1.] (<type 'numpy.ndarray'>) instead.

The only solution I can think of is to take average of scores, which could be a parameter in constructor. This should be made true while using with cross_val_score.
`cross_val_score(SearchLight(Ridge(), scoring=roc_auc_score, average=True), X, y)

I think we have to dissociate two problems:

parametrize the scoring within the SearchLight (independently of the cross val score) i.e; SearchLight(LogisiticRegression(), scorer=roc_auc_score); this should be close to what you already wrote

Deal with multiclass AUC: this is outside this PR, and will be addressed in sklearn (https://github.com/scikit-learn/scikit-learn/issues/3298)

make SearchLight compatible with cross_val_score, which expects float scores, not array. I think that may be a broader issue though, as it's similar to i.e. get a confusion matrix in a cross_val_score.

I recommend to solve 1, and leave 2 and 3 for now.

@kingjr I have removed the cross_val_score example and only solved the case 1 as mentioned in your previous comment.
I am not sure what is causing the travis and appveyor error.

Not sure what s going on with Travis. Can you repush with a forced set-upstream?

Pushing again didn't help. Perhaps @Eric89GXL has some idea?

Current coverage is 87.28% (diff: 82.60%)

Merging #3502 into master will increase coverage by <.01%

@@             master      #3502   diff @@
==========================================
  Files           341        341
  Lines         60474      60493    +19
  Methods           0          0
  Messages          0          0
  Branches       9256       9259     +3
==========================================
+ Hits          52784      52802    +18
  Misses         4933       4933
- Partials       2757       2758     +1

Powered by Codecov. Last update 7e09380...e419129

I added the import in the relevant methods rather than using global imports, which solved the nested import issue.

@kingjr please have a look at the changes.
The travis error looks unrelated to the PR changes.

Do you want to give it a look @agramfort ?

LGTM
@kingjr merge if you're happy
fix the docstrings in master if needed or better in your next "privatization" PR

I'll fix the docstring in the "privatizing" PR ;)

Thanks @kaichogami !

@kingjr You are welcome! What is "privatizing" PR that is being talked about?

We re making a release next week, but some of the recent decoding contribs
may be too unstable at the moment. I will temporarily make these changes
private until next week's release and put them back afterwards to give us
another 6 months to ensure the stability of the API.
 What is
"privatizing" PR that is being talked about?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/3502#issuecomment-249463549,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEp7DIdhfjevhPzlmpYltEfx9qIgwZ1iks5qtycIgaJpZM4JfX2t
.


searchapi_google_news example does not implement Search Tools

yarn run start ./src/tools/searchapi_google_news.ts
output:
{
input: "What's happening in Ukraine today?",
output: AIMessage {
lc_serializable: true,
lc_kwargs: {
content: 'As of my last update in early 2023, I cannot provide real-time news updates or current events, including the situation in Ukraine. For the most recent information, please consult a reliable news source or a real-time news service. Here are some general points that might have been relevant up to early 2023...',
additional_kwargs: [Object]
},
lc_namespace: [ 'langchain_core', 'messages' ],
content: 'As of my last update in early 2023, I cannot provide real-time news updates or current events, including the situation in Ukraine. For the most recent information, please consult a reliable news source or a real-time news service. Here are some general points that might have been relevant up to early 2023...',
name: undefined,
additional_kwargs: { function_call: undefined, tool_calls: undefined }
}
}
How to make SearchApi Tools work?

Could you provide a minimal reproducible example that illustrates the problem ? What do you think is wrong and what have you tried ? Sorry to ask these questions but it will let people help you better!

Do you have a valid searchapi api key ?

Do you have a valid searchapi api key ?

Yes, the following example is working fine:
const tool = new SearchApi(process.env.SEARCHAPI_API_KEY, {
engine: "google_news", {
}); const res = await tool.call(
const res = await tool.call("What's happening in Ukraine today?");
console.log(res);
res ==> RFE/RL's Ukraine Live Briefing gives you the latest developments on Russia's ongoing invasion, Western military aid, global reaction,...
My guess is that the problem may be with AgentExecutor.fromAgentAndTools, which you can try by running https://github.com/langchain-ai/langchainjs/blob/main/examples/src/tools/searchapi_ google_news.ts and try


org.junit.Assume failure should ignore test and not fail it

As it's stated in JUnit Assume documentation tests should be ignored and not failed. JUnitParamsRunner behaves differently.

What version of JUnitParams and JUnit are you using, because I cannot reproduce it in the newest version?

Sorry, I've should've been more specific.
junit: 4.12
JUnitParams: 1.1.0
It happens when you use Assume in @Before and not @BeforeClass. JUnit throws MultipleFailureException which wraps multiple exceptions and not just AssumptionViolatedException. I've tested it locally and adding
         } catch (@SuppressWarnings("deprecation") MultipleFailureException e) {
            for (Throwable failure : e.getFailures()) {
                if (failure instanceof AssumptionViolatedException) {
                    eachNotifier.addFailedAssumption((AssumptionViolatedException) failure);
                } else {
                    eachNotifier.addFailure(failure);
                }
            }

in ParameterisedTestMethodRunner.runMethodInvoker fixes it. If you like I can create PR for it later today, but it's somewhat sketchy as MultipleFailureException is deprecated, but JUnit itself still uses it.

We started from Intellij brand new maven project and we added below code
    @RunWith(JUnitParamsRunner.class)
    public class ExampleTest {

        @Before
        public void setUp() throws Exception {
            Assume.assumeFalse(true);
        }

        @Test
        @Parameters("AAA|3")
        public void test(String text, Integer length) throws Exception { }
    }

and our pom.xml file is just
    <dependencies>
        <dependency>
            <groupId>pl.pragmatists</groupId>
            <artifactId>JUnitParams</artifactId>
            <version>1.1.0</version>
        </dependency>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.12</version>
        </dependency>
    </dependencies>

and it works as expected - test is ignored. Can you create pull request in JUnitParams with failing test?

Never mind. I've found that someone in legacy project where it occurred was calling @Before method in @After method and it caused this problem. Sorry about that.


Only the first instance of TestMethodAttribute.Execute returning TestResult[] value is used, not all of them.

Description

When I implement my own TestMethodAttribute, I can override the Execute method and return my own TestResult[]. But every code that calls TestMethodAttribute.Execute only takes the first one.
Can all the results be returned correctly?

Steps to reproduce

Write my own TestMethodAttribute.
return multiple TestResult.
Run UnitTests and review the result.

public override TestResult[] Execute(ITestMethod testMethod)
{
    return new[] { new TestResult(), new TestResult() };
}

Expected behavior

All TestResults should be used, not only the first one.

Actual behavior

Only the first TestResult is used.

Environment

Mstest v2

@walterlv: Thank you for reaching out to us. We already have an issue filed for same. Please follow https://github.com/Microsoft/testfx/issues/358 for the updates.


Make the editor scale according to the amount of code inside.

Currently all editor windows are of a fixed height, though some files have 1 line of code, and others have 30.
Height should scale accordingly.
https://github.com/kirjs/ng2-codelab/blob/f8ac1bdeb9928f3d8435d3250a019c2bdf291d71/src/app/editor/editor.component.ts

Fixed


Question oc

Are your roms oc?
Thanks for sharing your builds

yes, all builds include oc

yes, all builds include oc


Choosing fps for streams

Description
Choosing fps on stream
Expected / Actual behavior
Now that twitch had added the option to pick quality and fps for streams that allows this it would be great with this also implemented in the gui when picking a quality.
So being able to pick 720p@30 fps instead of 60fps for example.
Livestreamer seems to be able to do it already so it should mostly be a matter of adding the new options to the list.

It is not as simple as adding these explicit quality names to the dropdown, because they are not available for every channel. It doesn't make sense having a list of qualities where a selection potentially doesn't match the list of available qualities of a channel. This especially doesn't make sense when having a default quality that's globally defined (or a channel specific default quality).
The quality names you're seeing in the GUI are actually presets for livestreamer with additional fallbacks, so all streams can be viewed, no matter what quality Twitch provides for the specific channel. The presets can be customized in the settings menu since v0.16.0 if you think you need to change them.
https://github.com/bastimeyer/livestreamer-twitch-gui/blob/v0.16.0/src/app/models/LivestreamerQualities.js