Policy attachment update

What type of PR is this?
/kind cleanup
/kind documentation
/kind gep
What this PR does / why we need it:
This updates the Policy Attachment documentation as per the discussion in https://docs.google.com/document/d/1p_kmAOmqebX8zyHnXW5I58cD8ZhNX4QNSa_gw8uAYxw/edit?usp=sharing
There's an update to the original GEP, and to the site documentation.

I've pushed another update here, I think the biggest outstanding thing is, of course, naming.
Currently, there are two types of Policy Attachment:

Hierarchical: the original form, with defaults and overrides.
Direct: a simplified form that can only attach to one object (or a small set).

I think that the Hierarchical name is technically correct but too complex and hard to write. (I've spelled it wrong so many times already).
So, we need another name.
Some thoughts:

Direct and Indirect: Simple, basically accurate, but I don't know if it indicates the hierarchical aspect enough.
Direct and Tree: Not great, but it really pushes the hierarchy.
Something else: I'm out of ideas.

I'll reword the site documentation once we've settled on this name.
TODO for the site docs:

[ ] Direct attachment example
[ ] Diagrams that include direct and hierarchical policy attachment
[ ] Better explanation of the differences

Okay, I think I've got all the comments now. PTAL.

/retest

@youngnick any guidance on merge semantics for non scalar type fields within hierarchical policies ?

@arkodg I think that, for hierarchical policies, the merge semantics depend on whether the settings are in defaults or overrides. However, for non-scalar fields, the merge semantics should be more context-dependent than just merging an entire struct into the same struct in another object.
I'll add in what I think here, and see if that makes sense.

I started writing some updates to address @arkodg's feedback, and it got a bit out of hand. I've added a bunch of extra description and examples to further describe:

how interactions between overrides and defaults should work
how fields should be overridden, including for non-scalar fields
when and how merging should be done (it's complicated).

I'm open to discussing if we should simplify this by only allowing one Policy of each Kind to be in effect on any object at once, but I think that it would substantially decrease the usefulness of this pattern.
I've got pretty detailed to try and eliminate edge cases, but you can sum up the rules for Hierarchical Policy interactions like this:

overrides override everything from the top down
defaults set defaults, with more specific beating less specific defaults
If a Policy affects a field inside an object, then that field is the most specific possible value, and so will beat any default from anywhere.

Oh, I've also folded most of the new changes into the doc page as well as the GEP, as I think that it should make the doc page clearer.
Also, I've specifically left the section about adding a sectionName to targetRef alone for now, although I do think we should change it, this PR is big enough already.

Okay, I think I've got both those rounds, thanks @robscott and @howardjohn!
The big change in this last revision is that I picked "Inherited" for the other Policy name, so we now have "Direct" or "Inherited" Policy.

LGTM, since this was a pretty popular PR and just changed I'll let someone else give the official approval though to give some time to review. Ping me if that never happens :slightly_smiling_face:

Thanks for the massive amount of work on this @youngnick! This is a huge step forward for our policy attachment model.
/lgtm


feat: ensure tests behave as expected in ctest

Currently, mtest has tests which knowingly returns a failure, and you as the runner of the tests should know which are correct and which are incorrect. This is not great practice, and causes needless cognitive load.
The implementation i propose still ensures full coverage testing of each macro, but has an internal TEST_FAILING_CASE to flip our run of TEST_CASE for us. This is specifically put in test/test_mtest.c so not to have multiple methods of negating tests, as its requirement is unique to testing macros, and not meant for general use.
Also edited the example for similar reasoning to ensure automated testing will pass as expected. Maybe documentation is better for showing how failing cases work than example/ itself.

Good point and nice solution.
Fixed a small type error. Ready to merge now.


Details about Firefox browser hasnt been provided in any of the tables.However I could successfully logged in FIREFOX browser.

[Enter feedback here]

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

ID: 625bb1b2-81fd-9804-c0b5-3cd2904decd9
Version Independent ID: e4468b05-200e-24ae-75e9-29fb2b3a6ddc
Content: Conditions in Conditional Access policy - Azure Active Directory
Content Source: articles/active-directory/conditional-access/concept-conditional-access-conditions.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

In the another MS docx  https://docs.microsoft.com/en-us/azure/azure-portal/azure-portal-supported-browsers-devices  , firefox is the supported browser. Kindly confirm and modify the page  "https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/concept-conditional-access-conditions"
Also I believe IE is not supported anymore after Mar 31 2021.Kindly update the same .Thank you

#reassign:@MicrosoftGuyJFlo

This doc is being updated in my backlog. We will address this in the update that is planned. #please-close

Hi Team,
How about IE which is no longer supported
On Wed, Jun 2, 2021, 4:42 PM PRMerger15 @.***> wrote:

Closed #76280 https://github.com/MicrosoftDocs/azure-docs/issues/76280.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/76280#event-4832202281,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APPAQHL6NINIJ2RKHILEFKLTQY7O7ANCNFSM456VCYBQ
.


Exporting variables creates Collections per each token set, ignores theme groups

Describe the bug
When exporting variables using "Export styles & variables" in V2.0.1 of the plugin, a variable collections is created for each token set I am exporting from. Each collection has only 1 mode, named after the token set. The variable collection named after my theme groups is not updated.
To Reproduce
Steps to reproduce the behavior:

Click on "Styles and Variables" from the Tokens tab of the plugin
Click on "Export styles and variables"
Check boxes to 'Create and Update' variables, leaving all 'Styles' boxes unchecked
In 'Tokens exported to Figma should:' switch ON 'Update existing style and variable names'
Click "Confirm"
In 'Themes' tab, check 'Select All' themes to export
In 'Token Sets' tab, set my global tokens to be 'Reference Only'. Set component token sets to 'Enabled'.
Click "Confirm"
Click "Export to Figma"

Expected behavior
Expected behavior is well described by video on Tokens Studio Youtube channel of the older version of the plugin, around 7:45. https://youtu.be/AtMVxP0UMII?si=IsksqLgFOIFiEpZw&t=465
I would expect a single Variable Collection in Figma (which already exists and contains tokens) thats named based on my theme groups to be added to/updated. I would expect each variable to correlate to a design token, with a mode correlating to each theme. To my recollection, this is how it functioned prior to 2.0.
Screenshots or Screencasts
Existing variable collection, named after my Theme Groups in Tokens Studio.

Resulting collections when exporting:

In 'Token Sets' tab, set my global tokens to be 'Reference Only'. Set component token sets to 'Enabled'.

Make sure to not use the Token Sets tab, use the Themes tab if you want to use Themes. This should work if you export from there.


Application crash during DialogueRunner Start function (Windows)

What is the current behavior?
Application crashes on launch.
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
1- Build the application on Windows.
2- Launch the application.
3- The application crash; the logs point to the Dialogue Runner Start() function when it tries to create delegates.
What is the expected behavior?
The application does not crash when launched.
Please tell us about your environment:

Yarn Spinner Version: 2.0.2-development
Unity Version: 2021.2.7f1

Other information

Crash Log / Stacktrace:
0x00007FFB52043E3F il2cpp::vm::Type::ConstructDelegate
0x00007FFB520B204D il2cpp::icalls::mscorlib::System::Delegate::CreateDelegate_internal
0x00007FFB4EF9B490 Delegate_CreateDelegate_mE57A1F8CC813EF670D026C17D2D4CFD7C6E3F40A
0x00007FFB4EF9AC05 Delegate_CreateDelegate_mA2E221A01A8B3FBEC4C8A529F3C213C60A3A2C53
0x00007FFB4ED9C5B9 RuntimeMethodInfo_CreateDelegate_m026E9DD922CC53D92EA3A3529A1BC089ABD0B8B9
0x00007FFB51FAD952 ActionManager_GetFunctionRunner_m7BB545776DC22611A918361CC0FCBD07B9EEB7E9
0x00007FFB51FAAD2B ActionManager_FindAllActions_m7DE3020C8F3476B34990442939FD237BC049289A
0x00007FFB51FA6223 ActionManager_AddActionsFromAssemblies_mCC3AC961DB087BA139C9D46E33448CBC7E5514F7
0x00007FFB51FCA62D DialogueRunner_Start_mDB146186494B91F0EEA6C010E6687C8DED346C12
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
More information: We also removed the DialogueRunner script from our scene and the build was not crashing anymore, so it's definitely the culprit. The issue is not present in the Unity Editor.

Just to be sure that the issue wasn't from my project. I downloaded the Choose-Your-Path Game project from the documentation, setup the script so the project was completable and built it for Windows as well. Same issue, it crashes on launch with the same stacktrace.

IL2CPP build on Android crashes too when dialogue is started.

I think this and #163 may be related, they are both looking like IL2CPP build woes.
I am leaving this up for now as I do some more testing, but may close this and open a meta-issue or merge these issues instead if it turns out to be connected.

I have been doing some testing and while I am not an M1 Mac I couldn't get a crash here on il2cpp builds, will have to investigate further, but it looks like it might be trickier than just an il2cpp issue.

This is connected to #163 and while that issue was filed second that one has more details so I will close this one and leave that as the discussion point


Legacy toggling

it doesn't work with Accelix, and possibly other legacies too

Not sure why I had this issue, but Accelix seems to work just fine at the moment. Just tested all the other key bindings, and they work flawlessly! Weird, huh? Marking this issue as closed since I can't reproduce it.

Actually, I can reproduce this issue. Acquire legacies, then /kill yourself. After that toggling won't work.

Might be an issues with UUIDs changing upon death, who knows?

I noticed this as well

Lol accidentally made a new issue for this yesterday. Well I've just done a temporary fix before multiplayer is added so I'm closing it for now.


Version 1.136.0 of TFSAfRM can no longer retrieve External TFS Builds

Hi,
The above version of TFS artifacts for Release Management can no longer connect to an external TFS instance to retrieve a list of build artifacts.
We are running multiple On Prem installations of TFS in separate domains, all running version 15.117.26714.0.
When using v 15.136.0 of TFSAfRM, if you test the connection endpoint from the services tab the connection is verified, but if you create a new artifact link in a release, it can get the list of projects from the remote TFS instance, but it can't get a list of build definitions. Also, if you try to create a release for an existing release definition, it cannot retrieve a list of builds from the remote instance.
We (luckily) have a vsix install file for TFSAfRM v15.106.2 and when that is installed on the same server we can get the list of build definitions and builds without any issues.
Also, because TFS now does automatic updates of the extensions this is being broken automatically every night as it goes off and retrieves the latest (broken) version from your servers. Any way of disabling that would be a good interim work around for this issue.
Thanks,
Ruairi.

@ruairiohagan
Hi Ruairi, can you please let me know the number of build definitions that you have?

Hi @ruairiohagan Thanks for informing that.
We are in the process of rolling out a fix for this. This should be out early next week.
Request you to please wait till that. I will update this thread immediately as the fix is out.
Thanks

Hi @romil07 ,
We have just download version 15.138.0 of TFSAfRM from the marketplace and we're still getting issues.
We are now able to create a new release and select a build version from the remote TFS instance, but if we try to create a new release definition and try to select the build definition from the remote instance, it is still unable to retrieve the list of build definitions from the remote TFS.
Is there anything else we need to do other than reinstalling the latest version of the extension to get this to work?
Thanks!

Hi @ruairiohagan
Can you check this with the latest version which 15.138.1
We updates it yesterday only and you should be unblocked with this update. Please check and update me here.
Thanks

Hi @romil07 ,
We've checked the latest update and it's working fine now, many thanks!


Error when activate theme

Hello,
I followed the doc to install theme, i have the WP-CLI installed too but when i try to activate theme with = wp theme activate my_theme i got following error
"Error: Error establishing a database connection. This either means that the username and password information in your wp-config.php file is incorrect or we can’t contact the database server at localhost. This could mean your host’s database server is down."
My server is not down, i go to the wordpress backend, trying to activate manually theme and i got following error also :
( ! ) Parse error: syntax error, unexpected '}', expecting \\ (T_NS_SEPARATOR) in /app/public/wp-content/themes/starter-theme/src/helpers.php on line 3
Someone can help me?
Thanks

You have pulled old release of the starter. Make sure you have ^2.0.0 versions in your project composer.json file.
It also required to have PHP 7.0+ installed locally before creating a new project with composer create-project tonik/theme command. Clearing composer cache would be helpfull too composer clearcache.

Hello,
Thank you for your response, i have php 7.0 locally, i created with composer create-project tonik/theme command. I followed the doc from the tonik website, it means that docs are not updated?

No, documentation is up to date. You have to have PHP 7+ otherwise composer will install an old release.
Yesterday, I've cleanup release so there should be no problem now. When someone will try to create a project on lower PHP version they should get a notice about the minimum version.

I've error when activate Tonik.
Failed to load resource: the server responded with a status of 404 (Not Found) app.js, app.css, foundations.... I don't understand why, I used npm run dev....

@septk Make sure build script does not return any errors and check if required files are actually outputted inside public/ folder. Additionally, you can validate paths in assets registration in app/Http/assets.php.
I can't tell more without other information from you.

I had the same issue, it only happens when using a backslash on the namespace with the CLI tool. I'll prepare a PR later on.


Compare dagster-based ETL output with non-dagster-based ETL output

Scope:

[x] merge dev into dagster_asset_etl
[ ] write script (potentially using sqlitediff) to compare legacy/dagster pudl.sqlites.

The TABLE_NAME_MAP data structure has changed so we'll need to update how we use it in pudl.extract.ferc1.create_raw_ferc1_assets() and xbrl_metadata_json.

For the TABLE_NAME_MAP stuff - it sounds like

create_raw_ferc1_assets would like just a list of all the dbf and xbrl tables that we could possibly want for transform purposes
ferc1_transform_asset_factory would like some sort of map from cleaned table to all the raw tables it depends on, or we could abandon it and encode all these dependencies manually

Is that right?
Right now, TABLE_NAME_MAP[_FERC1] provides both a list of all the raw tables as well as the dependencies, which I think is kind of nice - you don't have to worry about adding a dependency for a transformation and then forgetting to add that dependency to the extraction process.
On the other hand, I think dagster sort of wants us to store the dependencies in the asset args. I guess we're doing that anyways when we generate the assets from the map, so maybe this is kind of a moot point.
I think the resulting code structure is roughly "fine" either way, and would push, as always, for "shortest path to getting this merge sorted 😅 "

Yeah, I think sticking with the current structure of TABLE_NAME_MAP[_FERC1] makes sense for now. We can change this easily down the line.

Once #2318 is merged into #2104 we can compare the database outputs. I think it makes sense to resolve #2296 prior to comparing the outputs so the ETL runs happen in the same environment and the outputs are accessible in cloud buckets. We can use the sqldiff tool to compare the outputs. Binaries for linux and Mac.

In dagster-asset-etl, we create empty tables in the sqlite database and then populate - this leads to some tables being empty. We should not generate those tables. There are "*_disabled" etl_groups in dev that we can use to do this filtering, though EPA CEMS might be an outlier here as well.

The ten inserts in plant_steam_ferc1 almost certainly come from the spot-fix PR that was merged into dev a few weeks ago, which added ten records to the table.

Just ran the comparison on the dev commit we merged into dagster (31b074e). With this comparison, there are only 2 tables with changes!

plants_entity_eia: 50 changes, 0 inserts, 0 deletes, 15464 unchanged
utilities_entity_eia: 34 changes, 0 inserts, 0 deletes, 13637 unchanged

Looking at these changes, they are all contained to plant_name_eia in the plants_entity_eia table, and utility_name_eia in the utilities_entity_eia. Many of these changes seem to be slight spelling changes, like: Novel Holmquist Solar LLC CSG -> Novel Holmquist Solar LLC. I'll keep investigating to see if I can find where these diffs are coming from, and we'll of course need to do this again once the new dev->dagster merge is complete.

Ran the comparisons again with the updated dagster version. I'm still seeing the same sort of changes in the plants_entity_eia and utilities_entity_eia tables. Otherwise everything else is identical, so I'll continue to investigate these two tables.

The same plants & utilities report varying names from year to year, and we have historically treated them as human readable labels and I think right now we may just be grabbing the most recently reported name, based on some sorted dataframe. So maybe the sorting is happening differently or not at all on one of the two branches?
There are also 2 different potential sources for these names:

The standard harvesting / entity resolution process, which tries to pick the most commonly reported value across all the tables where the field shows up across all years.
The manually assigned PUDL plant & utility IDs, which also include a name. Those would be found in the ID mapping spreadsheets, and can also be looked up in the plants_pudl and utilities_pudl tables in the PUDL DB.

So maybe the plant & utility names are coming from the harvesting process on one branch, and the PUDL plant/util tables in the other?
Also, given how frequently we end up using plant & utility names for record linkage, maybe we should be retaining all permutations that are ever reported so the matches are more robust.
It's a little unsettling that these differences exist, but given these special ambiguities in the source of these names, I don't know that I would consider it a blocking issue.
However, the fact that we rely on these names in multiple record linkage processes means that these differences might have unforeseen consequences, which maybe @cmgosnell and @katie-lamb would be able to speak to more intelligently.

Oh. Also the dagster-nightly-builds outputs aren't actually running nightly. So those are actually likely to be out of date. Let me kick off a run so there's more to look at in the morning.

@jdangerx thanks! I ran the full ETL locally because I didn't want to wait for nightly builds to finish, but I'll use these outputs now.
@zaneselvans I spot checked a bunch of mismatched values, and neither branch consistently match the manually assigned ID's, so it seems something is slightly different in the harvesting process for some reason.

Unrelated to this harvesting issue but we also need to filter out the table schemas that exist in pudl.metadata but don't actually have any data being loaded into the database for them. We should do this before merging into dev so datasette doesn't have a handful of new empty tables:

demand_hourly_pa_ferc714: etl_group=ferc714
entity_types_eia=static_eia_disabled
hourly_emissions_epacems: ur too big for sqlite. etl_group=epacems
plant_parts_eia: etl_group=outputs
respondent_id_ferc714: etl_group=ferc714
retained_earnings_appropriations_ferc1: etl_group=ferc1_disabled
utility_analysis: example output table that should be removed prior to merging into dev
epacems_output: example output table that should be removed prior to merging into dev

Simple solution would be to just filter out these tables when creating pudl_sqlite_io_manager. I think a better solution would be to create a new classmethod for pudl.metadata.Package that returns a package from a list of etl groups.

the utility names are harvested, not grabbed from the pudl mapping sheet. the names in that sheet are purely for the humans.
Are the new EIA enviro association tables that Ella integrated merged into dagster? If not, then it could definitely just be the fact that those new tables had utilities in them and therefor more fodder for the harvesting process.

@zschira the comparison is between the outputs from a particular commit that was on dev and the dagster branch with that commit merged in, right? To avoid potential discrepancies based on the underlying transforms / data.
Given that it's just these name columns that are seeing discrepancies, and the fact the difference only affects about 0.3% of all records in those columns, I think we should declare victory.

@zaneselvans yeah I've been comparing the commit merged into. I still haven't been able to nail down exactly what's going on, so if no one is too worried about it, I agree that we should probably call it good.
I also checked epacems today. I couldn't find a good parquet comparison tool, so I loaded all the data into Dask DataFrames and went year by year loading to pandas and using DataFrame.equals. Using this method I didn't find any discrepancies, so I think we can probably close this issue.

@rousik This is the most recent effort we've made to compare DB outputs from different commits. @zschira would probably be the person to talk to about further automation / generalization for use in CI and/or nightly builds.


feat(app): deployments tab

Design Tweaks
• Capitalize the first letter in these columns: Labels, Status, and Type
• I think we can make Redeploy our Primary button color
• Could turn Ref into a link and only show the string after the last slash ex) cloud-ui:v14 to save space
• Change succeeded to Done to save space
• Make the status column be our pill component, Done = Green pill, Failed = Red Pill, etc...

Another design iteration
• Showing Start Time, End Time and Duration


Move gemmiAtomsForCid to C++

This update moves most of the code in MoorhenMolecule.gemmiAtomsForCid to C++, making the code in MoorhenMolecule more simple. It also removes the need to call delete() for webassembly objects.

Now this update also moves code in MoorhenMolecule.parseSequences to C++


Created and updated docs for 1.27-5

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


DRILL-5811 reduced repeated log messages further.

This reduces the number of messages printed for blocks that are on nodes on which there is no drillbit running. Now the number of messages printed is equal to the number of nodes on which there are blocks that don't have drillbits. For example if there are 6 data nodes and only 2 of those nodes have drill bits, then exactly 4 messages will be printed. This time around I have tested this on my own physical cluster.

@paul-rogers


TypeError: forward() got an unexpected keyword argument 'is_causal'

when i tried use mvts_transformer to SpokenArabicDigits ,  the error occurred

I have the same issue. Have you solved it yet?

您好！我是一名计算机专业的学生，想要学习这份代码但是关于作者发布的关于分类的数据集已经无法打开，如果您方便的话可以加我的联系方式打包一份给我吗

I solved it by adding "**kwargs" to the forward() function in the TransformerBatchNormEncoderLayer class.. this solves the issue that the argument 'is_casual' is no longer expected in the function call.

yes you can basically add , is_causal: bool = None or , **kwargs at the end of forward pass for TransformerBatchNormEncoderLayer

I solved it by adding "**kwargs" to the forward() function in the TransformerBatchNormEncoderLayer class.. this solves the issue that the argument 'is_casual' is no longer expected in the function call.

this resolved the issue.

maybe you could use torch==1.7.1


Upgrade Anvil to 1.1.5

Thank you for the contribution. It was merged directly as a055e9817291c84c986de9d2cb5ba58cc9961375 to keep commit history cleaner. Your contribution is still credited to you.


Two socket systems fail with a deconfigured slave processor.

8.50476|ISTEPS_TRACE|PRESENT> Proc[05]=C000000000000000
...
9.19614|HWAS_I|I>hwasPlatDeconfigGard.C: Get returning 1 GARD Records
9.21550|HWAS_I|I>deconfigGard.C: Deconfiguring Target 00050001, errlEid 0x90000015
...
9.23584|HWAS_I|I>deconfigGard.C: _deconfigureByAssoc BUS Peer: 000F0000
9.23585|HWAS_I|I>deconfigGard.C: Deconfiguring Target 000F0000, errlEid 0x90000015
...
19.51245|ISTEPS_TRACE|Running proc_a_x_pci_dmi_pll_initf HWP on target HUID 00050000
19.53177|FAPI|proc_a_x_pci_dmi_pll_initf.C:
Parameter1, start_XBUS=true
Parameter2, start_ABUS=false
Parameter3, start_PCIE=true
Parameter4, start_DMI=true
...
19.93265|FAPI_I|proc_start_clocks_chiplets.C: proc_start_clocks_chiplets: Entering ...
19.95199|XSCOM|E>XSCOM status error HMER: 00c0050000000000 ,XSComStatus = 5, Addr=8030006
Looks like if the Abus unit is deconfigured (by association) we do not call PLL init for the Abus logic on the master processor.  The very next istep tries to touch the logic still.
We do not see this problem on our multi-node system because we keep all the Abus units "configured" until much later in the IPL.

@dcrowell77 , @sannerd - Any update?

@rjknight actually has a fix in flight

Resolved now?

I think that 102ee037ba001da14eaa754766130558c1e8a0e0 has the fix.


[BUG] return null_pointer_exception if the definition of processor is null when creating or updating a ingest pipeline

Describe the bug
When creating or updating a ingest pipeline by PUT _ingest/pipeline/xx, if the definition of the processor is null, then OpenSearch throws null_pointer_exception with 500 http status code.
To Reproduce
Steps to reproduce the behavior:

Create a ingest pipeline

PUT _ingest/pipeline/x
{
  "processors": [
    {
      "set": null
    }
  ]
}

then you  can see the error:
{
  "error": {
    "root_cause": [
      {
        "type": "null_pointer_exception",
        "reason": "Cannot invoke \"Object.getClass()\" because \"config\" is null"
      }
    ],
    "type": "null_pointer_exception",
    "reason": "Cannot invoke \"Object.getClass()\" because \"config\" is null"
  },
  "status": 500
}

Expected behavior
Validate the definition of the processor, returns 400 bad request error if the definition is null.
Screenshots

Host/Environment (please complete the following information):

OS: [macOS]
Version [2.9]

Does it make sense to create a set processor with a null config?
I agree that a NullPointerException is not ideal, but it should still throw an error, right?

I agree that a NullPointerException is not ideal, but it should still throw an error, right?

Yes, it does exactly that now - an error instead of NPE


Wrap description tags in CDATA

closes #375
This PR wraps all <description> content in <![CDATA[]]>, which was stripped away when full sdf files were generated. All symbols should show up properly on website upon merging.

Verified today:
http://sdformat.org/spec?ver=1.7&elem=collision#contact_category_bitmask


token issue

how and where to place the token?

done! now?

Add tokens.txt file

in tokens.txt how should i paste the token? with these "" or without?

Just add token in series no ""

ok. but after adding the token and hitting "save file", the npm show invalid webhook url. why is it? do you have any idea?

how and where to place the token?

Read the freaking instructions , everything is given there , just paste the plain token , no need of “ “ ,

Just add token in series no ""

ok. but after adding the token and hitting "save file", the npm show invalid webhook url. why is it? do you have any idea?

You have to copy the webhook url and paste it in captcha hook and webhook url , and save it


Headers in Preview are lying

The preview shows only the headers set by postman, not the headers that will actually get sent. Chome adds referer, user-agent and such.
I just lost a whole day of work trying to figure out why a web service wasn't working.

If you click on 'Limitations' (to the right of HTTP request and Curl), there's a popup which says that 'Automatic headers sent by Chrome cannot be previewed'. Chrome sends headers based on the user's settings, cookies, and the Chrome version, and there's no way for us to be aware of these headers in Postman.


Feature Request: Add startLevel prop to control the quality of first video fragment

Is there an existing issue for this?

[X] I have searched the existing issues

Which Mux Elements/Packages does this apply to? Select all that apply
mux-video, mux-video-react, mux-player, mux-player-react
Description
Hey!
A fairly common problem these days is that a stream starts with a lower video quality, and after checking your internet connection, the next segment is generally of better quality. The easiest way to reproduce it is to open any stream on Twitch. This may be fine for long streams, but in the case of a short video, especially when you loop it, it becomes a more serious problem because this low quality fragment remains in the cache.
The current library (hls.js) on which the MUX components are built has a startLevel parameter that allows you to control the quality of the first fragment. Having this capability will help improve the user experience by providing a better quality stream from the start.
This can be a separate prop startLevel, or a general prop, for example hlsConfig, which allows you to override all params in hls.
// React example

<MuxVideo
     src={src}
     startLevel={999} <-- this maximizes the quality of the first fragment
     ...
/>

hls.js API doc - https://github.com/video-dev/hls.js/blob/master/docs/API.md#startlevel
Pull request with the change - https://github.com/muxinc/elements/pull/772
Expected Behavior
Ability to control the quality of the first video fragment through the startLevel property.

I second this! Encountered the exact issue described. I was able to access hls by videoElement.value._hls, but this only works in chrome; in safari, this is undefined

will this be made available anytime soon? I would really appreciate it as well! Thanks ❤

@mjamesCZ the reason for that is that in Safari Mux Player uses Safari's native HLS engine instead of Hls.js (we find it to be slightly better in terms of Quality of Experience that we track with Mux Data)
You can force Safari to use Hls.js by setting prefer-playback="mse". More details about that here
However, @mjamesCZ & @staniwasd we have a new parameter that you might find better, which is:
rendition-order="desc"

What this does is re-order the rendition list to have the highest rendition at the top. Most players (Hls.js included) will start by attempting to play the first rendition in the list. With this setting I think you'll get the desired behavior that you're going for.
The tradeoff is that startup time will be a little worse (because the player has to download, or attempt to download the bigger video), but it seems like that tradeoff is one you're willing to make.

Thank you for the help @dylanjha! Unfortunately, I'm still having problems with this:

prefer-playback="mse" and setting the startLevel manually does the trick, unfortunately, this does not seem to work on iOS, where _hls is undefined and therefore native playback is most likely used
as I'm sourcing the hls manifest from a different provider to MUX, rendition-order="desc" does not seem to be working for me... any ideas? 🙏 this is the .m3u8 file I'm working with (and have control over how it looks, would changing the order there do the same as rendition-order="desc"?):

#EXTM3U
#EXT-X-MEDIA:TYPE=AUDIO,URI="240p/audio/index.m3u8",GROUP-ID="default-audio-group2654984",NAME="stream_0",AUTOSELECT=YES,CHANNELS="2"
#EXT-X-MEDIA:TYPE=AUDIO,URI="360p/audio/index.m3u8",GROUP-ID="default-audio-group2654985",NAME="stream_0",AUTOSELECT=YES,CHANNELS="2"
#EXT-X-MEDIA:TYPE=AUDIO,URI="480p/audio/index.m3u8",GROUP-ID="default-audio-group2654986",NAME="stream_0",AUTOSELECT=YES,CHANNELS="2"
#EXT-X-MEDIA:TYPE=AUDIO,URI="720p/audio/index.m3u8",GROUP-ID="default-audio-group2654987",NAME="stream_0",AUTOSELECT=YES,CHANNELS="2"
#EXT-X-MEDIA:TYPE=AUDIO,URI="1080p/audio/index.m3u8",GROUP-ID="default-audio-group2654988",NAME="stream_0",AUTOSELECT=YES,CHANNELS="2"
#EXT-X-STREAM-INF:BANDWIDTH=322427,AVERAGE-BANDWIDTH=254194,CODECS="avc1.42c01e,mp4a.40.2",RESOLUTION=426x240,FRAME-RATE=30.000,VIDEO-RANGE=SDR,AUDIO="default-audio-group2654984",CLOSED-CAPTIONS=NONE
240p/index.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=670812,AVERAGE-BANDWIDTH=530022,CODECS="avc1.42c01e,mp4a.40.2",RESOLUTION=640x360,FRAME-RATE=30.000,VIDEO-RANGE=SDR,AUDIO="default-audio-group2654985",CLOSED-CAPTIONS=NONE
360p/index.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=1306191,AVERAGE-BANDWIDTH=1039462,CODECS="avc1.42c01e,mp4a.40.2",RESOLUTION=853x480,FRAME-RATE=30.000,VIDEO-RANGE=SDR,AUDIO="default-audio-group2654986",CLOSED-CAPTIONS=NONE
480p/index.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=2548100,AVERAGE-BANDWIDTH=2081178,CODECS="avc1.42c01e,mp4a.40.2",RESOLUTION=1280x720,FRAME-RATE=30.000,VIDEO-RANGE=SDR,AUDIO="default-audio-group2654987",CLOSED-CAPTIONS=NONE
720p/index.m3u8
#EXT-X-STREAM-INF:BANDWIDTH=6838938,AVERAGE-BANDWIDTH=5644006,CODECS="avc1.42c01e,mp4a.40.2",RESOLUTION=1920x1080,FRAME-RATE=30.000,VIDEO-RANGE=SDR,AUDIO="default-audio-group2654988",CLOSED-CAPTIONS=NONE
1080p/index.m3u8

@mjamesCZ unfortunately there's no way to control the equivalent of startLevel on iOS yet because it will always rely on native browser playback instead of Media Source Extensions (which is what Hls.js uses under the hood). Apple has recently added a paired down version, called Managed Media Source to iOS, and Hls.js has even more recently added support for enabling its usage, but we haven't yet added any official way of using that,  since it's pretty new. That said, I'm hoping to squeeze in the unofficial _hlsConfig property I discussed before into a canary release sometime this week 🤞.


Navigation options resolution links to wrong url

Hi,
When I open the docs though this url for Common mistakes there is wrong URL for Navigation options resolution at the end of documentation. It redirects us to an local host url for the page.
Please correct the url there.
Thanks.

hi there. I just changed v2.reactnavigation.org to redirect to reactnavigation.org, where this is resolved. when we release v3 it'll archive the current docs there. thanks!


Some stuff are deprecated.

Use the atom-workspace tag instead of the workspace class.
C:\Users\Abdülhamit\.atom\packages\todo-show\keymaps\show-todo.cson:10:2

Style elements within text editors using the atom-text-editor::shadow selector or the .atom-text-editor.less file extension. If you want to target overlay elements, target them directly or as descendants of atom-overlay elements.
C:\Users\Abdülhamit\.atom\packages\todo-show\stylesheets\show-todo.less:?:?

@jamischarles Do you want me to issue a pull request for this or are you on it? It should only take a few minutes (looks like just a find/replace)

Go for it! Would be happy to merge.
On Thu, Feb 5, 2015 at 1:47 PM Justin Reynard<EMAIL_ADDRESS>wrote:

@jamischarles https://github.com/jamischarles Do you want me to issue a
pull request for this or are you on it? It should only take a few minutes
(looks like just a find/replace)
—
Reply to this email directly or view it on GitHub
https://github.com/jamischarles/atom-todo-show/issues/34#issuecomment-73135876
.

@jamischarles Does this one make sense to you?
Style elements within text editors using the `atom-text-editor::shadow` selector or the `.atom-text-editor.less` file extension. If you want to target overlay elements, target them directly or as descendants of `atom-overlay` elements.

@framerate Look at joefitzgerald/go-plus#132. They had, talked about and fixed the same warning message.

Issued a PR: https://github.com/jamischarles/atom-todo-show/pull/38
Note: I removed some event handlers here:
https://github.com/framerate/atom-todo-show/commit/a3110531a9eeceb8a930f3763c1b209e69f4e2c2#diff-c1bec0e2a183505f86460299897eb228L236
I wasn't sure what they were doing! Please take a look and let me know if they're doing something I may not be using? (they were throwing deprecation errors due to spacepen not having the same exposed handlers as the old atom view)

That looks like it was left over boilerplate. Doesn't appear to affect anything.

Fixed with #38


UL not displayed if speed is under 1kb/s.

Strange, but details view shows it, but not within the main window.

This is by design, I think speeds under 1KB/s are mostly useless since they're almost stalled anyway. If you really want to show speeds less than 1KB/s, perhaps a configuration option for this could be implemented.

Sorry, can't upload image here (something went wrong... ooops), so look here:
http://share.pride-it.net/v/73dc0b14
What is then the reason to display "low" speed in detailed view?

The details view shows the rates per peer, which shows the actual DL/UL rates to help with troubleshooting issues, eg. "Am I actually uploading anything?". The main window shows speeds based on the premise "show rates that are actually useful to know".

I recently changed the details view to also not show speeds under 1KB/s, I can change it to not show speeds that are actually 0 (so users can see if they're actually dl/ul anything)

@zp That's true, forgot about that :smile: Let's keep it as is.


Fix early connection completion on async response filters

Now that response filters can be completed asynchronously, we can no longer rely on finally blocks to complete the connection and call callbacks: we need to register listeners to call them when the response is sent.

@FroMage first of all thanks for the PR. I still have to look at this carefully, however wanted to start by giving an initial feedback. There are many methods whose signature is being changed to add a "Consumer onComplete", still in many cases a lambda that does nothing is passed on that parameter (t -> {}); how about, when possible, keeping methods with the old signature too and delegating to the new ones by passing that "empty" lambda as parameter? That would grant a better backward compatibility and probably make the changeset easier.

I can. But I fear it will distract people from using the onComplete and assume things can be done with finally. But I can.

Well, the fact is that I'd like to backport you stream/reactive changes to a 3.x minor in the next future, to make sure they land in WFLY soon. That's why I'm looking a bit at backward compatibility. But I think I can probably do the changes I suggested on the branch only, and mark the old methods as deprecated ;-)

That's a possibility, just let me know if you want me to add the methods. I can always add them and mark the others as deprecated on master too. That would serve enough as warning IMO.

@FroMage thanks and sorry for the late answer. To me the PR here is fine; to merge it, it has to be rebased, so I've created https://github.com/resteasy/Resteasy/pull/1336, in which I've also added an additional commit for the mentioned backward compatibility methods. Unless you see anything wrong, I'd merge #1336 after a successful Travis CI run.
Thanks again.

+1On 27 Oct 2017 01:52, Alessio Soldano<EMAIL_ADDRESS>wrote:@FroMage thanks and sorry for the late answer. To me the PR here is fine; to merge it, it has to be rebased, so I've created #1336, in which I've also added an additional commit for the mentioned backward compatibility methods. Unless you see anything wrong, I'd merge #1336 after a successful Travis CI run.
Thanks again.
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread.


curl IP/stop does not actually terminate Locust swarms

Expected
Per suggestion in #831, I have a script that starts Locust through a POST request, then terminates Locust through a GET /stop.
There are two issues with this:

Depending on the spawn_rate, calling GET /stop only terminates httpusers that are already spawned. I expected this would terminate the entire test's users.
If you initiate a swarm with a HTTP request, the UI doesn't have a "STOP" button. The only way to terminate that swarm is with a GET /stop.

To repro

curl -XPOST -d "user_count=100&spawn_rate=10" http://$LOADGEN_IP/swarm where user_count/spawn_rate are our custom fields
sleep for 5 seconds, then curl http://$LOADGEN_IP/stop
Notice, after running step 2 UI indicates STATUS: STOPPED, and HTTPResponse is successful:

{
  "message": "Test stopped",
  "success": true
}

However, according to our reliable telemetry, Locust is still swarming

Environment

Locust version: 1.3.1

Interesting. It is possible that this issue arose from making the stopping of user greenlets async.
I think the best way to fix this is to stop the spawning greenlet from runner.stop() before actually stopping user greenlets. Do you agree @heyman ?

I don't have that code fresh in my head (and at the moment don't have time to start digging), but that sounds reasonable to me @cyberw
We should be able to write a test for this I think.

I don't have that code fresh in my head (and at the moment don't have time to start digging), but that sounds reasonable to me @cyberw
We should be able to write a test for this I think.

I'll have a look some time soon.

I'll have a look some time soon.

From my understanding of the codebase, I believe that these problems could be alleviated using synchronisation primitives offered by gevent (e.g. Synchronized queues, Locking primitives). For instance, some events such as start, stop, spawn events could be queued up and locking primitives could be used to ensure that only one of those mutually exclusive events (start and stop are two exclusive events IMO) is happening at a given time. Right now, these greenlets all run concurrently without real knowledge of each others resulting in flaky situations like the one in this issue.

From my understanding of the codebase, I believe that these problems could be alleviated using synchronisation primitives offered by gevent (e.g. Synchronized queues, Locking primitives). For instance, some events such as start, stop, spawn events could be queued up and locking primitives could be used to ensure that only one of those mutually exclusive events (start and stop are two exclusive events IMO) is happening at a given time. Right now, these greenlets all run concurrently without real knowledge of each others resulting in flaky situations like the one in this issue.

I wont have time to look at this, I think... Some else is welcome to try!


Is it possible to change the path defined by $RUN_DIR?

Hi, great work  on guild and I find it very useful!
Currently, since I use a conda environment, my guild runs are stored in
path_conda_env/.guild/runs/${RUN_ID}
Based on my understanding, this path is set by the $RUN_DIR environment variable. Is it possible to change the path defined by $RUN_DIR?

you can look at #170 for a related issue

Perfect, that works! Thanks


Cursor does not move to the next line when the [Enter] button is pressed.

In the flutter quill for web, this issue appears. However the new line gets appended. Cursor remains in the same position.

This is not issue on mobile, right?

Oops, wrong button closing it.

This is not issue on mobile, right?

This issue is from the link you referenced

That is quilljs's issue then.
That library is not something we maintain

That is quilljs's issue then.
That library is not something we maintain

quilljs is pretty stable though. I don't think an issue as basic as this could happen for a stable library. Also of that was the case, then this issue should appear in mobile as well.

So among the following three:

Flutter on mobile
Flutter on web
Quilljs on web

Which does this issue appear?

So among the following three:

Flutter on mobile
Flutter on web
Quilljs on web

Which does this issue appear?

The issue is appearing for the editor in the link you mentioned. Is that created in flutter quill?

No it is not.
It is React-Quill https://www.npmjs.com/package/react-quill

Oh ok.
But if this is your project, you might wanna do something about this problem. Seems pretty serious to me. Maybe open the same issue on the bullet journal repo?
Closing.


Feature request: Model.predict doesn't automatically modify the input data

Ideally, when we predict out on a fitted model, the predict method doesn't automatically modify the input dataset as it does here: https://github.com/ihmeuw-msca/regmod/blob/develop/src/regmod/models/model.py#L621
A proposed alternative:
def predict(df, inplace=True):
    ....
    return_df = pd.DataFrame()
    for i, param_name in enumerate(self.param_names):
        return_df[param_name] = self.params[i].get_param(coefs[i], data)
        if inplace:
            df[param_name] = return_df[param_name]
   return return_df

This way, the same default behavior is provided, but users passing in slices of dataframes or who in general rely on pure functions can also have that behavior enabled optionally.

By the way, happy to do this myself too if Kelsey's busy!


JavaScript Linting Round 2: Add Eslint + Prettier Config Combo to Webpack

TLDR: add Prettier to Bolt to automatically standardize some very basic code formatting in our JavaScript -- line breaks, quotes, and spaces basically.
With the Prettier plugin for VS Code + enabling the editor.formatOnSave config, this makes writing consistently formatted JavaScript that looks good and is easier to read so much easier!

Functionally, this PR makes four "small" changes to Bolt:

Wire up Prettier to be used in conjunction with our current eslint config
Disable two existing eslint config rules we've already had enabled (linebreak and quote rules) in lieu of Prettier's much smarter handling of both of these (there's a few valid instances when we do need to use double quotes / should have code break to the next line to be more readable)
Update our Webpack build config to check / recheck our JavaScript's syntax every time we make a change
Slightly update the verbosity in Pattern Lab's .boltrc config so linting warnings are visible while doing local development (without too much extra noise getting added)

With these 4 changes, the rest of the files updated in this PR address the formatting warnings / errors that get thrown when running a full lint check of the code, without introducing any crazy functional changes in the process 😃

1	Why do we now have both prettier and eslint? There's now more complexity (which, to be clear, is a bad thing-- it's just that much harder to be aware of everything that's going on). But additionally, it means that just because you fix linting errors with Prettier in you IDE (yay!) doesn't mean you don't have linting errors (huh? boo!)

@remydenton as long as we configure things properly, eslint and prettier should be working together on reporting issues in our JS (via one single unified lint command)
So why prettier?
https://prettier.io/docs/en/why-prettier.html

By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles. It is generally accepted that having a common style guide is valuable for a project and team but getting there is a very painful and unrewarding process. People get very emotional around particular ways of writing code and nobody likes spending time writing and receiving nits.

So why choose the "Prettier style guide" over any other random style guide? Because Prettier is the only "style guide" that is fully automatic. Even if Prettier does not format all code 100% the way you'd like, it's worth the "sacrifice" given the unique benefits of Prettier, don't you think?
What’s the difference between Prettier and Eslint?
https://prettier.io/docs/en/comparison.html
Linters have two categories of rules:
Formatting rules: eg:  max-len ,  no-mixed-spaces-and-tabs ,  keyword-spacing ,  comma-style ...
Prettier alleviates the need for this whole category of rules! Prettier is going to reprint the entire program from scratch in a consistent way, so it's not possible for the programmer to make a mistake there anymore :)
Code-quality rules: eg  no-unused-vars ,  no-extra-bind ,  no-implicit-globals ,  prefer-promise-reject-errors ...
Prettier does nothing to help with those kind of rules. They are also the most important ones provided by linters as they are likely to catch real bugs with your code!
^ that’s why eslint is typically used in conjunction with Prettier so you get the best of both worlds

Ah, got it, they are designed to run side-by-side: https://prettier.io/docs/en/eslint.html.  Thanks for bearing with me on the dumb question.
I'm still curious how best to test.  I do see a number of lint-like errors when running npm run bootstrap-- but then no apparent errors when I intentionally introduce issues, like removing the newline from the end of a file.

I'm still curious how best to test. I do see a number of lint-like errors when running npm run bootstrap-- but then no apparent errors when I intentionally introduce issues, like removing the newline from the end of a file.

The two ways this should run (after initially running npm run setup to install the new deps) is either:

via the normal Webpack watch task / recompiles (npm start) in the pattern-lab folder which should lint all the JS files being watched and bundled

by running the npm run lint:js or npm run lint commands in the root of the repo...

Can you try changing one of our component JS files to use double quotes instead of single quotes to see if that triggers something? Lmk if that doesn’t work for ya!

Shoot, got some merge conflicts there-- can I get you to merge this in @sghoweri ?

@remydenton sure can 👍
I'll tackle the merge conflicts + getting the docs on IDE integration for VS Code, PHP Storm and Sublime in just a bit!


Fix/v1.4 revision

Description (개요)

Add missing endpoint docs in engine version 1.4
Translate tables docs from english to korean for ko version
Fix incorrect parameter name in tables docs (schema_name -> schema)

Type of change (작업사항)
Please delete options that are not relevant and check out the type of change.

[x] Tables and query API docs fix

Writing Convention
Make sure to check out the Writing Convention.
Review Process
Review should be conducted by at least two people.

Since the only difference between v1.4 and the v1.4+v1.5 common PR (#209 ) is the lack of search feature in v1.4, we decided to remove the search feature from the common PR, while adding it to the PR to v1.5 only. Thus, this PR is no longer needed.


View's sorting order change changes more than result's order

@hideki, This is #795 all over again.
Tested both with 1.3.1-90 and 1.3.2-4 (couldn't find when the regression happened)
The results show by the query are diferent when the sort order is changed.
For instance:
liveQueryAmostragens.setDescending(false);
liveQueryAmostragens.setStartKey(Arrays.asList(mTalhaoId, null));
liveQueryAmostragens.setEndKey(Arrays.asList(mTalhaoId, new HashMap<String, Object>()));

Gives this list: (all the results in ascending order)

By changing the sort order, (also the order of start and end keys):
liveQueryAmostragens.setDescending(true);
liveQueryAmostragens.setStartKey(Arrays.asList(mTalhaoId, new HashMap<String, Object>()));
liveQueryAmostragens.setEndKey(Arrays.asList(mTalhaoId, null));

Gives this list: (misssing many results)

Hi @vbenso,
Let me clarify the issue. Do you observe the issue of #795 with latest build from master (1.3.1-90)? Can you test your application against 1.3.1 and 1.3.0? Can you observe the problem?
Thanks,
Hideki

@hideki
The problem isn't exactly the same as #795, since the filtering seems to be working fine.
Allow me to present you the problem in detail when testing with 1.4-1, 1.3.1-91 down to 1.3.0-49 gives the same wrong results.
Querying values in descending order gives the following results:

Pay attention to 2 things.
1 - Row[0] shouldn't be there, should be the last.
2 - There are only 23 rows.
Changing the query to ascending order:

1 - Sorting appears correct
2 - There are 27 rows.

Hi @vbenso,
Thank you for detailed information. We will look into the issue soon.


Added ScriptedImporter for .webp extension

This PR slightly changes the package structure (moved existing code to a "Runtime" folder and added an "Editor" folder), and introduces a ScriptedImporter for .webp files that calls the WebP conversion on import and has some minimalistic import options.
It also disables the "auto referenced" option from the existing AsmDef because that avoids conflicts with potential other AsmDefs of the same name (it's a very short name).

Thank you pull request. I didn't notice ScriptedImporter feature. It's cool.
and project doens't opened with unchecked "auto referenced" option .
but your opinion about uncheck "auto referenced" option is also reasonable.
so I will take a time for how handle that

Um... okay I see. That only bring a dependency to make another asmdef. like d25c93a9fb96974f9848c6fce2120a48e056d5b3
I will think more about this after merge that.
anyway thank you adding cool stuff.


farmers delight backstabbing bug

Describe the Bug
backstabbing normally amplifies the damage in your offhand when you hold the knife in your main hand but when the create mod is added it no longer does this
Reproduction Steps
1.get a backstabbing knife in your main hand
2. get a bow in your offhand
3. fire arrow at the back of a mob
4. with create mod it does around 20-30 hp to iron golem (maxed bow)
5. without create mod it does 50-60 hp to iron golem
Expected Result
it would do around 1.5 -2x damage
Screenshots and Videos
No response
Crash Report or Log
No response
Operating System
windows 11
Mod Version
0.5.1f
Minecraft Version
1.20.1
Other Mods
farmers delight 1.4.3
create 0.5.1-d-build.1161+mc1.20.1
fabric api 0.91.1+1.20.1
Additional Context
https://github.com/newhoryzon/farmers-delight-fabric/issues/240

please downgrade fabric api to 0.88.1
does this issue also occur on forge?

this issue does not occur on forge
on forge when the create mod is installed it still does the backstabbing with bow thing

does this issue still occur with the new port?

If this isn't fixed by the new port open a new issue


Twig for SMS

Working on getting this to work with sms sends as well. So far it seems doable.
Wanted to check if this impossible, really hard or already in progress.

Hi @bobsburgers Any updates on this?

Hi @bobsburgers Any updates on this?

Yep i did this pull
https://github.com/Logicify/mautic-advanced-templates-bundle/pull/22


Remote announcements proposed fix - Issue #143

See issue #143 for a description of the problem.
Comments, suggestions and help with testing are very welcome.

Thanks!


Glitches hard over time

I think this screenshot sais everything - every color is messed up now

the green below wasn't a 2 XD

Please fix this, this uno clone is awesome!

any update?

any update?


[#23 & #30]: Initial search screen shows an error message; minor styling issues

Fixes #23
Fixes #30
Also fixes more styling issues (updates margins, paddings for card, etc)


Imrove route selection strategy

Currently a route is selected when an update arrives, based on the metric. This approach is problematic. Most notably, it does not account for the feasibility condition and thus selectes unfeasible routes, creating routing loops. If a route is advertised  by peer A with some metric M, to some node B, it might be that some node C connected to B learns this route from a peer D which is between B and C. This route will have the same seqno, but  a higher metric (or the same in case of a local network). If node A now announces it's route with a higher seqno and increased metric, node B might unselect the route to node A, since it has a route to A via C with lower metric. At this point, we created a routing loop.
According to the RFC, route selection must be run after every feasible update is applied. We also need to consider for every route if it is still feasbile. In practice, we can actually simplify this a little bit.

If the routing table has no route for the prefix, it is installed as the selected route.
If the routing table has a route for a prefix with seqno S and metric M, we apply the same logic as the feasbility check in the RFC:

If the seqno S is higher, install the route from the update as selected route. If the currently selected route is different (i.e. different neighbour), move it to the fallback table.
If the seqno S is equal, and the metric M is strictly smaller, install the route as selected, and if the currently selected route has a different neighbour, move it to the fallback table.
We should also consider broadcasting this update to our peers. After all, new seqno's should be learned as soon as possible.

In case the route is already a fallback route, we update it in place using the same feasibility checks.

This approach guarantees that the best route (feasible and lowest metric) is installed for a prefix at any point in time. After all, the metric can only increase if the seqno increases, and increasing the seqno immediately makes all other routes unfeasible.
The only issue left are retraction updates. When a route is retracted, we should apply the update, and then run a full route selection on the prefix.

According to https://datatracker.ietf.org/doc/html/rfc8966#section-3.6, the seqno increasing should not be the sole metric of switching routes, as this can cause oscillation. This is however problematic, since an unfeasible route must also not be selected, and an increased seqno in an update makes new routes unfeasible. Additionally, since we reply to seqno requests with an update broadcast to all peers, and the aim is to make updates to selected routes be broadcasted themselves, this should be fine in general. After all, if every peer broadcasts the new selected route, it stands to reason that the route with the smallest metric will arrive on the node first, which is the eventual best route regardless. We will thus ignore this for now (in part).


Fix query error message when missing EQ

The error message that is reported when a query is missing the .eq for the hash key is incorrect.
See #60 and #59.

Closed by #89


Support for traffic data by OpenDataCam

https://github.com/opendatacam/opendatacam

OpenDataCam is an open source tool to quantify the world. It quantifies and tracks moving objects with live video analysis. It is designed to be an accessible, affordable and open-source solution to better understand interactions in urban environments.

this entire setup is priced around $150. All software is based on open source components and runs completely locally. The software features a friendly user interface and is currently optimised for detecting and counting traffic participants

A group at CityLAB Berlin is currently evaluating this system for traffic analysis. Could this help to provide realistic traffic data when focussing on one particular crossing within A/B street?
What would be necessary to import and use the data of the camera within A/B street?
Counter history API: https://opendatacam.github.io/opendatacam/apidoc/#api-Recording-Counter_history_(CSV)
Thanks.

I can think of two possible uses.

Validating a traffic model. If we come up with a travel demand model, we could run the simulation and then use the throughput tool on a lane or intersection and see how many different agents pass through at some time. You could then take the same measurements in real life and compare counts. I don't know how to make use of the results. If they match, is it a sign to trust the simulation? If they don't, what action could we take to improve it?

Generating trip demand input. If you have counts around many areas, I could imagine some kind of graph-based algorithm that tries to figure out exact trip start and end-points that roughly match the measured counts along different roads. I don't have any knowledge of this algorithm (beyond a vague memory of somebody talking about this approach), and I'm not promising I could implement it, or that the results would be at all realistic.

Just cleaning up old issues. I'm still not sure how to make use of this kind of data. We're still barely touching the problem of generating travel demand, except for #424. If you have any ideas how to incorporate it, please reopen.


Added power support for the travis.yml file with ppc64le

Added power support for the travis.yml file with ppc64le. This is part of the Ubuntu distribution for ppc64le.
This helps us simplify testing later when distributions are re-building and re-releasing.

Coverage remained the same at 100.0% when pulling 89d73c3564ae0db6360c1f4742ca44d2db45ceef on sreekanth370:master into a69045d0f12752d64310eea365efa015cbfc97c5 on stream-utils:master.

Duplicate of #2


Error using $fetch.create using CJS modules.

I was working in a Nuxt2 app using ohmyfetch in the background with a home-made module, but the Nuxt2 app displays me that the$fetch export has not the method create, so I investigate and I found that the CJS module (what it was imported by Webpack after the bundle process) it not exports the method.
Steps to reproduce the error

Create a new JS proyect with the ohmyfetch dependency.
Create a index.js file with the following content.

const { $fetch } = require('ohmyfetch')

const scopedFetch = $fetch.create({});

Try to run the file.

What I was expected
It should not thrown an error.
Error description
const scopedFetch = $fetch.create({});
                           ^

TypeError: $fetch.create is not a function
    at Object.<anonymous> (/home/bantonio/PhpstormProjects/test-ohmyfetch/index.js:3:28)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

Same here with es module import...
I'm trying to do this:
import { $fetch } from 'ohmyfetch'

const apiFetch = $fetch.create({ baseURL: '/api' })

And error shown in the nuxt console is the same:
 ERROR  ERROR in utils/fetch.ts:3:25                                                                                14:54:08
TS2339: Property 'create' does not exist on type '$Fetch'.
    1 | import { $fetch } from 'ohmyfetch'
    2 |
  > 3 | const apiFetch = $fetch.create({ baseURL: '/api' })

@BrandonlinU I actually got rid of the error by updating the dependency to the latest version. I was on 0.4.8 and updating to 0.4.14 fixed the error.

@jarekcieslak Your solution is correct, your error was because you are using ESM and you don't have the updated version, the create method was introduced in the version 0.4.13, but in my case I am in the version 0.4.14 using CJS modules and because the CJS proxy module does not export a create method Node complains about that.

Working with Vite, with WebPack:
ohmyfetch__WEBPACK_IMPORTED_MODULE_1__.$fetch.create is not a function
import { $fetch } from "ohmyfetch"

export default defineNuxtPlugin(({ $config }) => {

    //@ts-ignore
    globalThis.$fetch = $fetch.create({`
    ...........

Trying in Nuxt Bridge
@BrandonlinU @jarekcieslak
can someone help me pls?

@pi0 I am experiencing the same issue in Nuxt.js 2 using ohmyfetch 0.4.15.
ohmyfetch__WEBPACK_IMPORTED_MODULE_3__.$fetch.create is not a function

Yeah... that will not work. I tried the same way as you, but the CJS proxy use Promises because the ES Module specification says that a module CAN use a top-level await, so you can't be sure that a ES Module does not use Promises, but $fetch.create() is a syncronous method, not a async method just like $fetch() or $fetch.raw(). Try to run your code with my example code and print out the new scoped client: You must see Promise { <pending> } and if you try to use it Node complains about the scoped client is not a function.

@BrandonlinU I tried the change locally by editing the files in node_modules and it works fine for me.

As a workaround you can use ESM version:
const { createFetch } = await import('ohmyfetch')

How would that work?
I tried the following in my nuxt 2 plugin without success:
const { $fetch } = await import('ohmyfetch')
const $api = $fetch.create(defaults)

const { fetch, Headers, createFetch } = await import('ohmyfetch')
const $api = createFetch({ fetch, Headers, defaults })

Another issue is that FetchError is not exported in CJS. Would it be possible to have the same exports for both CJS and ESM?

I also experienced the same problems, tried the same solutions, only to finally detect, that by adding the create to cjs will end up as a promise later...
As I was in a typescript environment, it was even more difficult to find this, as I was using ohmyfetch on client side with esm, and on server side with cjs...
Client and Server both used the same code for the create...
Is there any other possible solution?

@pi0
is there a reason, why the cjs/* import the *,mjs files ?
Would it not be easier, to simply build a cjs version with the following build.config.ts ?
import { defineBuildConfig } from 'unbuild'

export default defineBuildConfig({
  declaration: true,
  rollup: {
    emitCJS: true,
  },
  entries: [
    'src/index',
    'src/node',
    'src/undici'
  ]
})

I believe building it in CJS is the only possible solution afaik, because we cannot load mjs, without being async...

I'm still getting this in 1.0.0 and I'm not sure what the issue is

Possibly same as #198, to which a fix PR has been submitted.


split will move leading or trailing whitespace when sep is whitespace

split will move leading or trailing whitespace when sep is whitespace, so strip() is useless
If sep is not specified or is None, a different splitting algorithm is applied: runs of consecutive whitespace are regarded as a single separator, and the result will contain no empty strings at the start or end if the string has leading or trailing whitespace. Consequently, splitting an empty string or a string consisting of just whitespace with a None separator returns [].
see https://docs.python.org/3/library/stdtypes.html?highlight=split#str.split

Can one of the admins verify this patch?

@tensorflow-jenkins Test this, please.

@biolee can you fix the conflicts?

AFAICS this file is not in tensorflow/tensorflow repository anymore.
Please create a new PR to tensorflow/models repository for this change.


Is there a PropTypes validation shape for the FieldArray fields prop?

In the docs for FieldArray, the fields object is described as a "pseudo-array". Is there a PropTypes validation shape available for this object?
I spotted array already in src/propTypes.js, but it doesn't include all the actions (and includes one not in the docs for fields, called splice). I'm not sure how that one relates to FieldArray.
I'd imagine it would look something like this:
const { /* ... */ number, func, shape } = PropTypes
// ...
  fields: shape({
    forEach: func.isRequired,
    get: func.isRequired,
    getAll: func.isRequired,
    insert: func.isRequired,
    length: number.isRequired,
    map: func.isRequired,
    move: func.isRequired,
    pop: func.isRequired,
    push: func.isRequired,
    remove: func.isRequired,
    removeAll: func.isRequired,
    shift: func.isRequired,
    swap: func.isRequired,
    unshift: func.isRequired
  }),
// ...

Published fix in v7.1.0.


Bevy logo doesn't fit well with GitHub dark themes

How can Bevy's documentation be improved?
In README.md the Bevy logo is shown. However it is barely visible with dark GitHub themes, especially Dimmed Dark.

Maybe it can be adjusted by adding a thin contrast outline (2-3 px) to the letters and the image.

Yeah this has been bothering me for awhile. I'd like for github to give us the ability switch out the svg based on the theme but until then I think the proposed solution is the way to go.

I have submitted a pull request #2288 for this issue.  It would be my 1st contribution ever, so I hope it is accepted.  I did add a thin border to the blackbird, B, E, V, and Y letters.


Create compileElements and add projectInternalView()

Create a new compileElements consumable configuration, intended initially to be used by test suites to create unit-test-like test suites. Eventually, we have plans to migrate the default test suite to use this configuration.
compileElements acts much like apiElements except it provides the "internal view" of a project during compile time instead of the "api view" which projects normally consume during compile-time. This is particularly useful for unit tests, but can also prove useful for writing test fixtures or implementing analytics plugins. By internal view, we mean the entirety of the compile classpath, including api, implementation, compileOnly, and compileOnlyApi.
To implement this, we add a new attribute, CompileView, which is only applicable when resolving a compile classpath -- or in other words, is only applicable when combined with Usage#JAVA_API. We additionally add attribute schema compatibility rules in the jvm-ecosystem plugin to ensure that the current behavior remains consistent -- that is, if the CompileView attribute is not requested, the default vale of the attribute equates to CompileView#JAVA_API, which will resolve apiElements.
This new configuration will not be published. The intention is not to resolve this configuration from outside of the project, though this pattern is not explicitly forbidden. We do not restrict users from doing so, however we do not provide any means, via the DSL, to depend on another project's complete compile view. Power users can accomplish this, if they wish, by manually constructing a dependency with the proper attributes, however this is not encouraged for any known use case.
Re-targeting of https://github.com/gradle/gradle/pull/21830 and https://github.com/gradle/gradle/pull/21697 after reverting them in 7.6 in https://github.com/gradle/gradle/pull/22114

@bot-gradle test qfl

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

One other question: "To implement this, we add a new attribute, CompileView, which is only applicable when resolving a compile classpath -- or in other words, is only applicable when combined with Usage#JAVA_API."  Should this be verified when the attributes are finalized?

One other question: "To implement this, we add a new attribute, CompileView, which is only applicable when resolving a compile classpath -- or in other words, is only applicable when combined with Usage#JAVA_API." Should this be verified when the attributes are finalized?

Unfortunately our attribute schema rules don't allow us to consider more than one attribute at a time. I'm not sure where we would put a check like this, as it should only really be checked when the JVM ecosystem attribute schema is applied.

@bot-gradle test and merge

OK, I've already triggered a build for you.


context vector dimensions are different for data sampled with random policy and those sampled with Bernoulli TS

Context vector dimensions are different for data sampled using uniform random policy and the data sampled using Bernoulli TS.
context vector for the data sampled with Bernoulli TS policy has dimension of 22
whereas context vector for the data sampled with random       policy has dimension of 20
I was not able to find any description on what the missing 2 dimensions in the context vectors sampled with random policy are representing.
What should I do to match their dimensions?

###############################################################################
Codes that I ran:
###############################################################################
from obp.dataset import OpenBanditDataset

dataset_random = OpenBanditDataset(behavior_policy="random", campaign="all")
dataset_bts = OpenBanditDataset(behavior_policy="bts",    campaign="all")
bandit_feedback_random = dataset_random.obtain_batch_bandit_feedback()
bandit_feedback_bts = dataset_bts.obtain_batch_bandit_feedback()

bandit_feedback_random['context'].shape
>> (10000, 20)
bandit_feedback_bts['context'].shape
>> (10000, 22)
###############################################################################

If you don't like the current feature preprocessing for some reason, you can implement your own preprocessing by overriding the "pre_process" function of obp.dataset.OpenBanditDataset.
you can still implement an OPE experiment even if their context dimensions are different (may not be true for OPL experiment though)

If you don't like the default feature preprocessing for some reason, you can implement your own preprocessing by overriding the "pre_process" function of obp.dataset.OpenBanditDataset.

Actually, what I wanted to ask was "are some of the user features only observed in data sampled with Bernoulli TS(BTS)?"
as their are 2 more number of dimensions to describe a context.
I looked into the code where the data-preprocessing is made,
csv files for both random and BTS policies have 4 "user_features" (user_features0, user_features1, user_features2, user_features3) for each user.
And the context dimension is decided by:
number (#) of context dimension = [# of different categories in user_features0 in the loaded samples] + [# of categories in user_features1 in the loaded samples] +[# of categories in user_features2 in the loaded samples] +[# of categories in user_features3 in the loaded samples] - 4
At this point I thought that the number of context dimension for both policies could be same if I load all the data instead of 10000 samples for each policy. I thought that if there are enough number of people, than the number of different categories for each feature would be the same. Otherwise some user features are unseen on the other dataset.
So I tried loading all the data available and found that the number of context dimensions still does not match
`
from obp.dataset import OpenBanditDataset
dataset_bts = OpenBanditDataset(behavior_policy="bts", campaign="all", data_path='./open_bandit_dataset')
bandit_feedback_bts = dataset_bts.obtain_batch_bandit_feedback()
bandit_feedback_bts['context'].shape
(12357200, 27)
dataset_random = OpenBanditDataset(behavior_policy="random", campaign="all", data_path='./open_bandit_dataset')
bandit_feedback_random = dataset_random.obtain_batch_bandit_feedback()
bandit_feedback_random['context'].shape
(1374327, 26)
`

Thank you for clarifying, and you are correct. the random dataset is about 10x smaller than bts data, and may not observe some feature categories. You may want to check this by using, for example, np.unique func

Oh I see
Thanks for the reply!


error during LGBM predict_proba

Hi all..
After long hours of training my model with lightgbm, I just run predict_proba and at first I ran into data_rate_limit in Jupyiter.. then I changed that limit and had to train the model again.. but this time I ran into another error:
Cannot cast array data from dtype('float64') to dtype('<U32') according to the rule 'safe'
can someone help me please?
thanks

Hi @vkocaman
It's nearly impossible to debug without a stack trace. Can you please copy/paste the error message, along with all the other output that could help us debug?
As a general best practice, I like training on a small sample of the dataset (say, 1%) to make sure that things work before training on the entire dataset.
You might also fix this issue by upgrading all of your libraries with pip install --upgrade auto_ml and pip install --upgrade lightgbm.
If that doesn't fix it, could you please also include the output of pip freeze?

here is the complete error message

TypeError                                 Traceback (most recent call last)
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/numpy/core/fromnumeric.py in _wrapfunc(obj, method, *args, **kwds)
56     try:
---> 57         return getattr(obj, method)(*args, **kwds)
58
TypeError: Cannot cast array data from dtype('float64') to dtype('<U32') according to the rule 'safe'
During handling of the above exception, another exception occurred:
TypeError                                 Traceback (most recent call last)
 in ()
----> 1 probs=ml_predictor.predict_proba(df_test)
2 print ("probabilities:",probs)
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/auto_ml/predictor.py in predict_proba(self, prediction_data)
1638         prediction_data = prediction_data.copy()
1639
-> 1640         return self.trained_pipeline.predict_proba(prediction_data)
1641
1642
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/sklearn/utils/metaestimators.py in (*args, **kwargs)
113
114         # lambda, but not partial, allows help() to work with update_wrapper
--> 115         out = lambda *args, **kwargs: self.fn(obj, *args, **kwargs)
116         # update the docstring of the returned function
117         update_wrapper(out, self.fn)
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/sklearn/pipeline.py in predict_proba(self, X)
363         for name, transform in self.steps[:-1]:
364             if transform is not None:
--> 365                 Xt = transform.transform(Xt)
366         return self.steps[-1][-1].predict_proba(Xt)
367
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/auto_ml/DataFrameVectorizer.py in transform(self, X, y)
175
176     def transform(self, X, y=None):
--> 177         return self._transform(X)
178
179     def get_feature_names(self):
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/auto_ml/DataFrameVectorizer.py in _transform(self, X)
145                                 val = '_None'
146
--> 147                             val = self.get('label_encoders')[f].transform([val])
148
149                     # Only include this in our output if it was part of our training data. Silently ignore it otherwise.
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/auto_ml/utils.py in transform(self, y)
182             diff = np.setdiff1d(classes, self.classes_)
183             self.classes_ = np.hstack((self.classes_, diff))
--> 184         return np.searchsorted(self.classes_, y)
185
186 class ExtendedPipeline(Pipeline):
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/numpy/core/fromnumeric.py in searchsorted(a, v, side, sorter)
1073
1074     """
-> 1075     return _wrapfunc(a, 'searchsorted', v, side=side, sorter=sorter)
1076
1077
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/numpy/core/fromnumeric.py in _wrapfunc(obj, method, *args, **kwds)
65     # a downstream library like 'pandas'.
66     except (AttributeError, TypeError):
---> 67         return _wrapit(obj, method, *args, **kwds)
68
69
/Users/vkocaman/anaconda/envs/py36/lib/python3.6/site-packages/numpy/core/fromnumeric.py in _wrapit(obj, method, *args, **kwds)
45     except AttributeError:
46         wrap = None
---> 47     result = getattr(asarray(obj), method)(*args, **kwds)
48     if wrap:
49         if not isinstance(result, mu.ndarray):
TypeError: Cannot cast array data from dtype('float64') to dtype('<U32') according to the rule 'safe'

I already made sure that all packages are up to date as for auto_ml.. and here is the pip freeze
alabaster==0.7.10
anaconda-client==1.6.3
anaconda-navigator==1.6.2
anaconda-project==0.6.0
appnope==0.1.0
appscript==1.0.1
asn1crypto==0.22.0
astroid==1.4.9
astropy==1.3.2
auto-ml==2.7.6
auto-sklearn==0.2.1
Babel==2.4.0
backports.shutil-get-terminal-size==1.0.0
beautifulsoup4==4.6.0
bitarray==0.8.1
blaze==0.10.1
bleach==1.5.0
bokeh==0.12.5
boto==2.46.1
Bottleneck==1.2.1
cffi==1.10.0
chardet==3.0.3
click==6.7
cloudpickle==0.2.2
clyent==1.2.2
colorama==0.3.9
ConfigSpace==0.3.10
contextlib2==0.5.5
cryptography==1.8.1
cycler==0.10.0
Cython==0.27.1
cytoolz==0.8.2
dask==0.14.3
datashape==0.5.4
deap==1.0.2
decorator==4.0.11
dill==<IP_ADDRESS>
distributed==1.16.3
docutils==0.13.1
entrypoints==0.2.2
et-xmlfile==1.0.1
fastcache==1.0.2
Flask==0.12.2
Flask-Cors==3.0.2
gevent==1.2.1
greenlet==0.4.12
h5py==2.7.1
HeapDict==1.0.0
html5lib==0.9999999
idna==2.5
imagesize==0.7.1
ipykernel==4.6.1
ipython==5.3.0
ipython-genutils==0.2.0
ipywidgets==6.0.0
isort==4.2.5
itsdangerous==0.24
jdcal==1.3
jedi==0.10.2
Jinja2==2.9.6
joblib==0.11
jsonschema==2.6.0
jupyter==1.0.0
jupyter-client==5.0.1
jupyter-console==5.1.0
jupyter-core==4.3.0
Keras==2.0.8
lazy-object-proxy==1.2.2
liac-arff==2.1.1
lightgbm==2.0.7
llvmlite==0.18.0
locket==0.2.0
lockfile==0.12.2
lxml==3.7.3
Markdown==2.6.9
MarkupSafe==0.23
matplotlib==2.0.2
mistune==0.7.4
mpmath==0.19
msgpack-python==0.4.8
multipledispatch==0.4.9
multiprocess==0.70.5
navigator-updater==0.1.0
nbconvert==5.1.1
nbformat==4.3.0
networkx==1.11
nltk==3.2.3
nose==1.3.7
notebook==5.0.0
numba==0.33.0
numexpr==2.6.2
numpy==1.13.3
numpydoc==0.6.0
odo==0.5.0
olefile==0.44
openpyxl==2.4.7
packaging==16.8
pandas==0.20.3
pandocfilters==1.4.1
partd==0.3.8
pathlib2==2.2.1
pathos==0.2.1
patsy==0.4.1
pep8==1.7.0
pexpect==4.2.1
pickleshare==0.7.4
Pillow==4.1.1
ply==3.10
pox==0.2.3
ppft==<IP_ADDRESS>.1
prompt-toolkit==1.0.14
protobuf==3.4.0
psutil==5.3.1
ptyprocess==0.5.1
py==1.4.33
pycosat==0.6.2
pycparser==2.17
pycrypto==2.6.1
pycurl==7.43.0
pyflakes==1.5.0
Pygments==2.2.0
pylint==1.6.4
pynisher==0.4.2
pyodbc==4.0.16
pyOpenSSL==17.0.0
pyparsing==2.1.4
pytest==3.0.7
python-dateutil==2.6.1
pytz==2017.2
PyWavelets==0.5.2
PyYAML==3.12
pyzmq==16.0.2
QtAwesome==0.4.4
qtconsole==4.3.0
QtPy==1.2.1
requests==2.14.2
rope-py3k==0.9.4.post1
scikit-image==0.13.0
scikit-learn==0.19.0
scikit-MDR==0.4.4
scipy==0.19.1
seaborn==0.7.1
simplegeneric==0.8.1
singledispatch==<IP_ADDRESS>
six==1.11.0
sklearn==0.0
sklearn-deap2==0.2.1
skrebate==0.3.4
smac==0.6.0
snowballstemmer==1.2.1
sortedcollections==0.5.3
sortedcontainers==1.5.7
Sphinx==1.5.6
sphinx-rtd-theme==0.2.4
spyder==3.1.4
SQLAlchemy==1.1.9
statsmodels==0.8.0
stopit==1.1.1
sympy==1.0
tables==3.3.0
tabulate==0.8.1
tblib==1.3.2
tensorflow==1.3.0
tensorflow-tensorboard==0.1.8
terminado==0.6
testpath==0.3
toolz==0.8.2
tornado==4.5.1
TPOT==0.9.0
tqdm==4.19.1.post1
traitlets==4.3.2
typing==3.6.2
unicodecsv==0.14.1
update-checker==0.16
wcwidth==0.1.7
Werkzeug==0.12.2
widgetsnbextension==2.0.0
wrapt==1.10.10
xlrd==1.0.0
XlsxWriter==0.9.6
xlwings==0.10.4
xlwt==1.2.0
zict==0.1.2

Dear Preston,
Not to train all the model again, is there any other way to pass the best lgbm parameters into model so that I don't need to optimize final model again?

btw, after making sure that all packages are up to date, I just trained 1% of training set.. but no change..

the stack trace helps a lot, thanks!
it looks like you're probably trying to feed in a column of dtype float64 as a categorical column. when we try to convert that to a 32 bit string, it starts throwing an error because of the loss in precision.
my guess is you're probably feeding in some column like user_id or order_id as a categorical column. that would also explain why it takes a while to train. these columns should almost always be ignored, not used as categorical values.
i'll release a patch to handle this later tonight probably, but in the meantime, you can probably handle this yourself by just ignoring any categorical columns that are of dtype float64. or, convert those to a string yourself beforehand, and see if that handles it.

Thanks.. Even though I specified the categorical columns in column descriptions, there was error.. but I just changed the types of float64 columns to int and it produced predict_probas now.. but there were just ones and zeros.. and it's not what I need.. anyway, thank you again..

yeah, that's because lightgbm released a breaking update, without any deprecation warnings. you can use the previous version of lightgbm (v2.0.6), or i'll have a new release ready later tonight that fixes it too.
thanks for filing all the issues!

alright, should be all handled in the latest release (v2.7.7).
if you run into lightgbm issues, and you're on the latest version, let me know. it's running fine for a couple projects i'm working on, and in the test suite, but i'm always open to learning how other people use things.


Fixes application namespace propagation

resolves #5274

Codecov Report

Merging #5278 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5278      +/-   ##
==========================================
- Coverage   40.08%   40.08%   -0.01%
==========================================
  Files        2697     2697
  Lines       81572    81574       +2
  Branches    10923    10924       +1
==========================================
- Hits        32702    32701       -1
  Misses      45945    45945
- Partials     2925     2928       +3

Impacted Files
Coverage Δ

...trap/plugin/request/DefaultRequestTraceWriter.java
0% <0%> (ø)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
90% <0%> (-10%)
:arrow_down:

.../profiler/sender/StandbySpanStreamDataStorage.java
72.88% <0%> (-3.39%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
66.66% <0%> (-3.34%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75% <0%> (-3.13%)
:arrow_down:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
80.59% <0%> (-2.99%)
:arrow_down:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
70.68% <0%> (-1.73%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.61% <0%> (+0.31%)
:arrow_up:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.86% <0%> (+1.38%)
:arrow_up:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
63.82% <0%> (+2.12%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #5278 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5278      +/-   ##
==========================================
- Coverage   40.08%   40.08%   -0.01%
==========================================
  Files        2697     2697
  Lines       81572    81574       +2
  Branches    10923    10924       +1
==========================================
- Hits        32702    32701       -1
  Misses      45945    45945
- Partials     2925     2928       +3

Impacted Files
Coverage Δ

...trap/plugin/request/DefaultRequestTraceWriter.java
0% <0%> (ø)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
90% <0%> (-10%)
:arrow_down:

.../profiler/sender/StandbySpanStreamDataStorage.java
72.88% <0%> (-3.39%)
:arrow_down:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
66.66% <0%> (-3.34%)
:arrow_down:

...tor/metric/datasource/DefaultDataSourceMetric.java
75% <0%> (-3.13%)
:arrow_down:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
80.59% <0%> (-2.99%)
:arrow_down:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
70.68% <0%> (-1.73%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
72.61% <0%> (+0.31%)
:arrow_up:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.86% <0%> (+1.38%)
:arrow_up:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
63.82% <0%> (+2.12%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


[3.5] agency lockup when removing 404ed callbacks and leadership preparation

https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/5929/

Thanks for ignoring my comments, and thanks for not checking return values
@neunhoef @kvahed


Cleanup code and so eliminate warnings.

Motivation:
There were some warning in the resolver-dns code base.
Modifications:

Fix javadocs
Use the base class to call static method.

Result:
Cleaner code.

@trustin PTAL

LGTM

Cherry-picked into 4.1 as b0242585d74f4307cd75e32a5d8f59f45346de45


flask need help frinds kindly help

root@kali:~/SocialFish# ls
CODE_OF_CONDUCT.md  CONTIBUTING.md  core  images  init.py  LICENSE  README.md  requirements.txt  SocialFish.py  templates
root@kali:~/SocialFish# python3 SocialFish.py
Traceback (most recent call last):
File "SocialFish.py", line 3, in
from flask import Flask, request, render_template, jsonify, redirect, g, flash
ModuleNotFoundError: No module named 'flask'

try to install requirements by running this command line :
.
python3 -m pip install -r requirements.txt
.
if it says pip not installed then you should install pip by running :
.
sudo apt install python3-pip

SpookyPatrick brother it says all requirements are satisafied so whats the issue

what is the command are you running to start SocialFish.
if you are running it with sudo, try to run it without.

SpookyPatrick brother i tried  the both python3 and python but still not working thanks brother
i also tried to run it with suso and without sudo but not working waiting for the developer to answer


ES6 Enhanced Object Literals not supported

JSHint with esnext = true doesn't support a dynamic property name in a object literal.
var obj = {
    // __proto__
    __proto__: theProtoObj,
    // Shorthand for ‘handler: handler’
    handler,
    // Methods
    toString() {
     // Super calls
     return "d " + super.toString();
    },
    // Computed (dynamic) property names
    [ 'prop_' + (() => 42)() ]: 42
};

Example from: https://github.com/lukehoban/es6features#enhanced-object-literals

@rwaldron this can be closed now can't it? the example works on the website..

Yes, thanks @lukeapage for the triage


add rate limiter constructor that accepts states

released as 151.0.0-077e375

This is needed for clustering. It allows us to pass


template-url doesn't work with default template

I'm trying to use my custom template and I started with the default template like says documentacion (https://github.com/guylabs/ion-autocomplete/blob/master/src/ion-autocomplete.js#L75) my example is here. http://plnkr.co/edit/Wkgjam?p=info
When trying to load the template at (https://github.com/guylabs/ion-autocomplete/blob/master/src/ion-autocomplete.js#L94)  get the following error:
Syntax Error: Token 'viewModel' is unexpected, expecting [)] at column 37 of the expression [viewModel.getItemValue(selectedItem viewModel.itemViewValueKey)] starting at [viewModel.itemViewValueKey].
Thanks!

Hi,
I just updated the template-url documentation. Can you please have a look at it again and adapt your template?
Thanks and regards,
Guy

Hi @yonsonsal,
any news on this? As I want to release 0.3.1 this week.
Thanks and regards,
Guy

Hi sorry I tohught I had alredy anwsered you but I had an error in github. The example is working properly now. Thanks!

Ok nice!


Not PHP CLI Compatible

This script will not work in PHP scripts executed via the command line. I get an undefined function error.

I just found my system has two separate php.ini files, one for CLI, the other Apache. Just had to add the extension to the CLI ini to fix the issue.


[Server] Update AddBkmkReq to include scrapable

[ ] - The new field should just be a boolean to say if its scrapable.

hello @R-Sandor, could you please assign me this issue? Thanks!


iOS Build Error (dev)

When running npm run ios, the build command keeps failing. I am getting multiple "fatal error: module 'Mapbox' not found" in the logs.
 To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')
warning: Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'LiveChasing' from project 'LiveChasing')

--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:iOS Simulator, id:02436BBA-E56B-436B-B16E-CF09B08B600D, OS:17.4, name:iPhone SE (3rd generation) }
{ platform:iOS Simulator, id:02436BBA-E56B-436B-B16E-CF09B08B600D, OS:17.4, name:iPhone SE (3rd generation) }
** BUILD FAILED **

The following build commands failed:
        CompileC /Users/USER/Library/Developer/Xcode/DerivedData/LiveChasing-echlwoqshkynkjbhpgyozzjvtvvl/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/maplibre-react-native.build/Objects-normal/arm64/RCTMGLVectorSource.o<EMAIL_ADDRESS>normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'maplibre-react-native' from project 'Pods')
(1 failure)

Version(s) affected

Platform: iOS
OS version: iOS 17.4
Device type: iPhone SE (3rd Gen)
Emulator/ Simulator: yes
Development OS: 14.1.1 (23B2082)
maplibre-react-native: Version ^10.0.0-alpha.2
MapLibre GL version: ? This isn't needed?
React Native Version: 0.74.1

Additional context

This also occurs on maplibre-react-native: ^10.0.0-alpha.4, along with version 9 releases.

This was due to the incorrect MapLibre GL Native Version (6 vs 5.13.0). Info on how to set the correct version in the podfile is in the docs.

@Craytor, thanks for reporting back. For others that might be experiencing this issue, was this the proper solution here:
$RNMBGL_Use_SPM = {
  url: "https://github.com/maplibre/maplibre-gl-native-distribution",
  requirement: {
    kind: "upToNextMajorVersion",
    minimumVersion: "5.13.0"
  },
  product_name: "Mapbox"
}

@tyrauber How do I fix it for expo dev builds? I'm on expo SDK 51 (new arch disabled), added the maplibre plugin and I get this error:

hey @corasan, I think I have seen that error come up with conflicting ReactNative versions.  Can you try setting a resolution in package.json for the version you are using and rebuild?

@tyrauber I set the resolution to RN 0.74.2, cleared build cache, prebuilt, and still get this. I must note that at first the error was this:

But then got the no such module 'ExpoModulesCore' error in subsequent builds.

@corasan I'm experiencing the MapLibre not found error as well. I followed the installation instructions for expo, react native version 0.73.6, maplibre-react-native version ^10.0.0-alpha.5. Did you figure it out?

+1
expo 50 sdk


feat: interface for sending commands to terminal

Supercedes #27

Looks good to me. Good to get the feature in main.

Thanks for taking a look.


⚠ ClamAV has degraded performance

In 2e8d673, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 168 ms

Resolved: ClamAV performance has improved in 7aceb95.


TrailingCommaInMultilineFixer - introduction

Resolves https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/4135

@SpacePossum any news about merging this?

Thanks for opening this PR!
I'm not sure if merge the fixer for array declaring and function calling is a good idea.
On your own points:
1 - sounds ok to me
2 - sounds ok to me
3 - see below
4 - see below
5 - for later
please add thios test
<?php
while(
(
(
$a
)
)
) {}`

I'd highly appreciate this feature - what's the status, can I help?

@Wojciechem you can make a review - e.g. proposing more test case and different naming/description if you think some would fit better.

btw, I don't see any test case for method calls, something like:
$obj->method(
    1,
    2,
);

@kubawerlos what do you think about this being 2 separate fixers? I would love to help with this

I think it should be a separate fixer: it requires a minimum version of PHP 7.3.

it requires a minimum version of PHP 7.3.

@erickskrauch only the options function_calls and after_heredoc requires PHP 7.3.

any news?

@grachevko I guess it's waiting for review, so don't hesitate with doing it 😃

Good work. I think another obvious thing to support is for function definitions as well as calls (incuding closures), and also unifying with the list stuff?

@PHP73Migration ruleset needs updating.

Friendly ping @kubawerlos.

Bump! Would love to see this as well. Let me know if I can help.

What is the direction this should go? Single fixer with options for arrays, functions calls and function declarations or seperate fixer for each?
Ping @keradus, @SpacePossum, @julienfalque, @localheinz

it's a shame we didn't managed to get conclusion in over a year.
@kubawerlos , can I ask you to rebase this PR and ensure CI is green? to get this PR finally merged, let's have this feature in a single fixer.

Coverage decreased (-0.003%) to 91.886% when pulling 59433f4252390fc71c7a3b823e3877729ee8a055 on kubawerlos:add-multiline-trailing-comma into 3d7e47c642457df4b49b78583071e648d790526a on FriendsOfPHP:master.

Thank you @kubawerlos.

@kubawerlos , can you drop the deprecated elements at 3.0 line?