Users creating duplicate organizations when submitting expenses

As part of the tax forms process this year, we noticed a bunch of duplicate organizations that were created in the expense flow. Avoiding duplicates there is not only about consistency, it's also a legal issue: if profiles are not grouped, the amounts we compute to decide whether or not we need to send a tax form will be inaccurate.
Example
This profile: https://opencollective.com/belden-industrial-llc
Is also: https://opencollective.com/belden-industrial-llc, https://opencollective.com/belden-industrial-llc2, https://opencollective.com/belden-industrial-ll3
Best solution for this problem
We should look at the flow to understand why these users are not re-using profiles.
@opencollective/design I can share the user info with you if you want to contact him to collect feedback.
MVP
As a quick win, I suggest we show a confirmation when you try to create an organization in the expense flow where the name matches (or is really close to) another organization that you administrate:

An organization with the name {name} already exists. Would you like to use it?
[ Yes ] [ No, create a new organization ]

This is resolved by https://github.com/opencollective/opencollective/issues/7030


Update appveyor config.

As title. Try and pick up more recent versions of dependencies.

Codecov Report

Merging #3021 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3021   +/-   ##
=======================================
  Coverage   85.68%   85.68%
=======================================
  Files         327      327
  Lines       68842    68842
  Branches     7807     7807
=======================================
  Hits        58984    58984
  Misses       8611     8611
  Partials     1247     1247


release 1.1.2 - canguro

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/pangenome branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

The only change of this version: We revert module wfmash to v0.10.4, because the current releases are unstable, not documented, and I don't understand how to set the parameters properly.
It is currently unclear, when a new stable release will become available. People like @baozg or @AndreaGuarracino are  evaluating.

I am praying this is the last release for my evaluations. Else I will go PUFF.


Add GCHeapMallocator

In preparation for the removal of GCAllocator.deallocate and
GCAllocator.reallocate, make that functionality available via a new
allocator with a different name.
Users of GCAllocator that wish to continue using manual @system memory
management instead of automatic @safe memory management can switch to
GCHeapMallocator.
For the rationale behind these changes, see PR #8554 and issue 23318.

CC @CyberShadow @schveiguy
@atilaneves this adds a new symbol

core.exception.AssertError@std/logger/core.d(1905): foo

Looks like a flaky test. Force pushing to retry...

https://github.com/dlang/phobos/pull/8557

Rebased to pick up #8557

Can this be an alias/wrapper underneath? Hard to review this when most likely it's simply a copy-paste of existing code.

@schveiguy Made it a wrapper.

Please see my comments on the other PR.


@contract between @doc and def inhibits ExDoc, ExUnit.DocTest

a_contract_between_doc_and_def/0 below won't get tested or documented, without any warning to that effect:
defmodule NormContractVsDoctest do
  @moduledoc """
  Demonstrates interaction between `@contract` and `@doc`
  """

  use Norm

  @doc """
  Return `:a`.

      iex> a_bare()
      :a
  """
  def a_bare, do: :a

  @doc """
  Return `:a`.

      iex> a_contract_between_doc_and_def()
      :a
  """
  @contract a_contract_between_doc_and_def() :: :a
  def a_contract_between_doc_and_def, do: :a

  @contract a_contract_before_doc() :: :a
  @doc """
  Return `:a`.

      iex> a_contract_before_doc()
      :a
  """
  def a_contract_before_doc, do: :a
end

Strikes me the suppression might not be fixable without help from both, but you might well be in a position to see the @doc above @contract and give warning. Failing that, let me know and I'll raise a PR to document the problem so people don't have to find it in the issues.

Hmm...I've been wondering if we should look at using the @on_definition hook for contracts. I think that would solve both of these problems. We'd be able to check to see if we have a contract attribute (or attributes) set, and we'd still be able to include all of the relevant docs and whatnot. Its probably more work to do it that way but it might result in less surprises for the user. @wojtekmach would probably no more than me since he's spent more time with that code.

on_definition is definitely interesting. I believe it’s used to annotate but not change each definition, but it still might be useful.
So the current approach is for each function to essentially define 2 functions, the inner one (the actual one) and the outer one that ensures the contract and calls super to invoke the inner one. I guess yet another approach is to not introduce separate function but rewrite the body of the function to ensure the contract. That might compose better with other features of the language after all.

On 24 May 2020, at 17:03, Chris Keathley<EMAIL_ADDRESS>wrote:
Hmm...I've been wondering if we should look at using the @on_definition hook for contracts. I think that would solve both of these problems. We'd be able to check to see if we have a contract attribute (or attributes) set, and we'd still be able to include all of the relevant docs and whatnot. Its probably more work to do it that way but it might result in less surprises for the user. @wojtekmach https://github.com/wojtekmach would probably no more than me since he's spent more time with that code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/keathley/norm/issues/80#issuecomment-633244287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASSJ2BAEPIKRFLQAWWCRDRTEZMHANCNFSM4NFUD46Q.

There are two problems with using on_definition:

on_definition is called once per function clause rather than per function as a whole.
The result of the callback that on_definition calls is not used in any way. As such it cannot be used to e.g. insert code into a function (clause), at least not directly.


#77 add tumour koch model to demo project

Fixes #77

Looks great!

@ben18785, can you hit the approve button so I can merge this?

Looks great!

@ben18785, can you hit the approve button so I can merge this?

@martinjrobins cool - I hadn't because I didn't want to stop @DavAug from reviewing this... will merge now

@martinjrobins cool - I hadn't because I didn't want to stop @DavAug from reviewing this... will merge now


[HIVEMALL-103][Spark] Upgrade spark-v2.1.0 to v2.1.1

What changes were proposed in this pull request?
This pr upgraded spark-v2.1.0 to v2.1.1.
What type of PR is it?
Improvement
What is the Jira issue?
https://issues.apache.org/jira/browse/HIVEMALL-103
How was this patch tested?
Existing tests

Coverage remained the same at 38.694% when pulling de9f2ce2d6cefa0228122edaf872e3ad9068a7c0 on maropu:HIVEMALL-103 into e273078982261d7e9eb5cd93cebe1ca8a3c1c5e9 on apache:master.

@maropu LGTM. Could you merge this PR into master?

ok

merged to master.

Thanks!


Forget Password back button click is not redirect to login screen.

Forget Password back button click is not redirect to the login screen. it always shows a white screen.

@mohanajuhi166  can you please provide a call back event for this back button?

@mithlesh6639 thanks for raising the issue.We are currently looking for more contributors to the project so that we can also issues asap. We will have a look

fixed in https://github.com/microsoft/aad_b2c_webview/pull/33


GH3878: Adds support for case sensitive OpenCover filters

Currently, if you try to apply multiple (case-sensitive) filters (with same-ish values) in your cake script like this:
var coverageInclusionFilters = new List<string>
{
   "+[ModuleName*]*",
   "+[moduleName*]*"
};

var openCoverSettings = new OpenCoverSettings();
//rest of the code omitted for clarity

for(var inclusionFilter in coverageInclusionFilters)
{
   openCoverSettings.WithFilter(inclusionFilter);
}

It produces this kind of a filter argument value:
-filter:"+[ModuleName*]*"

containing only the first one from the coverageInclusionFilters list from the code above.
As per https://github.com/opencover/opencover/wiki/Usage#understanding-filters
OpenCover filters are case-sensitive.
This change enables you to apply those kind of filter values.

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

cc @DNikolina

@lynkx your changes have been merged, thanks for your contribution 👍


Dashboard: Ensure the full-size WordPress admin menu is scrollable when the window height is short

Summary
Adds some CSS to enable scrolling when the WordPress admin menu needs it in tablet or desktop mode.
Scroll Bar for Menu when Height is too short

Menu is unchanged in compact mode
The app is completely unusable if the height is this small in both editor and dashboard. Additionally the WordPress menu has a fixed size where a scroll bar would obstruct the icons.

When there is enough vertical clearance, also do nothing

Relevant Technical Choices
These changes are scoped to the WordPress admin menu for dashboard only.
To-do

User-facing changes

Testing Instructions

Visit the dashboard
Resize your browser to have a smaller vertical height
See that you can scroll the WordPress Admin Menu

Why add a scrollbar to the admin menu instead of removing the overflow on the dashboard app itself? Could you perhaps elaborate on that?
I think messing with the WP admin menu in this way is prone to breakage (if WP ever changes the admin menu styling) and does not meet user expectations of having consistent way of accessing the admin menu. (i.e. "Why is there suddenly a scrollbar in my admin menu?!")

Why add a scrollbar to the admin menu instead of removing the overflow on the dashboard app itself? Could you perhaps elaborate on that?
I think messing with the WP admin menu in this way is prone to breakage (if WP ever changes the admin menu styling) and does not meet user expectations of having consistent way of accessing the admin menu. (i.e. "Why is there suddenly a scrollbar in my admin menu?!")

@swissspidy That is a great question! So the dashboard was designed to have a shrinking header and tab bar based on your scroll position on the main content, which requires the container to not have an overflow since we have effectively two scrolling regions. One where the height is calculated by the second's offset.

@swissspidy That is a great question! So the dashboard was designed to have a shrinking header and tab bar based on your scroll position on the main content, which requires the container to not have an overflow since we have effectively two scrolling regions. One where the height is calculated by the second's offset.


Is Intake catalog check in validate_data_sources too strict?

I checked in an updated catalog.yml locally to get the landuse_classification example updated and working.
This raised the following CI error:
% doit validate_data_sources:landuse_classification
.  validate_data_sources:landuse_classification
WARNING: The project has an Intake catalog, it must declare the variable INTAKE_CACHE_DIR in its anaconda-project.yml file and set it to "data".

If the catalog.yml is hosted on s3, this error is not raised - looking at the dodo.py, has_intake_catalog check to see if there is a local catalog.yml:
https://github.com/holoviz-topics/examples/blob/main/dodo.py#L1210-L1217
The data itself is on s3 and by default intake caches the data in ~/.intake/cache:
https://intake.readthedocs.io/en/latest/catalog.html#caching-source-files-locally
Two questions:

IIUC, the INTAKE_CACHE_DIR will cache the data in ./data but why would we require this?
If this is required for local catalog.yml - shouldn't it also apply to the catalog file hosted remotely as well?

I'm primarily asking / trying to understand why we require a custom cache location?
Adding the following passes the test so will do that for now in any case.
variables:
  INTAKE_CACHE_DIR: data

I'd assume that hosting the data in .data/ is needed to make the project self-contained; projects are meant to have everything in one directory so that they can be deleted rather than leaving files strewn across the file system, particular for potentially large datasets and environments. Having it in ./data may also be important for certain workflows we've implemented; not sure.

Here's another error that applies to local catalog.yml but not one that is remotely hosted.
Both of these are not checked if the catalog.yml is hosted on s3. I will move this to s3 once I know where to put it but still question whether we can reduce/remove some of these constraints.
If it's a requirement then I would expect it to be consistently applied to local catalog.yml and the ones hosted on s3. I understand this is most likely because it's easy to check for local catalog.yml. I also don't see an issue with letting intake use the default cache or letting the end user customize it if desired.

The reason for constraining INTAKE_CACHE_DIR to be set to the local data folder is that this was the recommended, but not constrained, rule before I overhauled the infrastructure. See https://examples.pyviz.org/make_project.html#if-using-intake-optional

I made it a hard constraint as:

that's the general pattern I've adopted, constraining to make sure things are as we expect and force users to think more about their examples, their data, etc. Also accepting that such constraints can be released if too hard, but I preferred starting with hard ones.
it made sense to me! As a user I think I prefer to see the data being downloaded in a local folder I have easy access to, instead of in a cache folder I will struggle finding if I'm not used to intake.

Constraints can and should be relaxed if they get in our way, I don't feel this one falls into that category?

Both of these are not checked if the catalog.yml is hosted on s3.

As far as I can see (quick check), the landuse classification example you're updating is the only one that is pointing to a remote catalog. All the other examples that leverage intake seem to be pointing to a local catalog. I believe good practice for us is to have:

local catalogs as we'd be in a bad position if the catalog goes away (the data can go away too but at least the catalog would serve as a reference)
local catalogs that users can easily inspect
test catalogs that replace the original one during the test runs

I believe 1. and 2. can be achieved, the project you're updating being the only one not having a test catalog and its catalog looks like it could just be saved locally:
sources:
  UCMerced_LandUse_all:
    description: Labeled images from UCMerced_LandUse/Images
    origin: http://weegee.vision.ucmerced.edu/datasets/landuse.html
    driver: xarray_image
    cache:
      - argkey: urlpath
        regex: 'earth-data/UCMerced_LandUse'
        type: file
    args:
      urlpath: 's3://earth-data/UCMerced_LandUse/Images/{landuse}/{}{id:2d}.tif'
      storage_options: {'anon': True}
      concat_dim: [id, landuse]
      coerce_shape: [256, 256]

  UCMerced_LandUse_by_landuse:
    description: All images matching given landuse from UCMerced_LandUse/Image.
    origin: http://weegee.vision.ucmerced.edu/datasets/landuse.html
    driver: xarray_image
    cache:
      - argkey: urlpath
        regex: 'earth-data/UCMerced_LandUse'
        type: file
    parameters:
      landuse:
        description: which landuse to collect
        type: str
        default: airplane
    args:
      urlpath: 's3://earth-data/UCMerced_LandUse/Images/{{ landuse }}/{{ landuse }}{id:2d}.tif'
      storage_options: {'anon': True}
      concat_dim: id
      coerce_shape: [256, 256]

  UCMerced_LandUse_by_image:
    description: Image matching given landuse and id from UCMerced_LandUse/Image.
    origin: http://weegee.vision.ucmerced.edu/datasets/landuse.html
    driver: xarray_image
    cache:
      - argkey: urlpath
        regex: 'earth-data/UCMerced_LandUse'
        type: file
    parameters:
      landuse:
        description: which landuse to collect
        type: str
        default: airplane
      id:
        description: which id to collect
        type: int
        default: 0
    args:
      urlpath: "s3://earth-data/UCMerced_LandUse/Images/{{ landuse }}/{{ landuse }}{{ '%02d' % id }}.tif"
      storage_options: {'anon': True}

However, 3. is a bit of a different story. You may have seen that the test_data folder is not an example but contains datasets that are used for testing the projects. There's a very practical reason for relying on test data I believe, which is that some projects rely on datasets that are difficult to get (e.g. very large) and it'd be just too impractical testing them in a CI job, yet you still want to test them so instead you rely on smaller data sets for which the notebooks/apps still run. Another reason I like that I like having test data, and that I think is even superior to the first reason, is that it sort of forces us to collect samples of the original dataset, which means that when the dataset is no longer available (which might happen at some point, who knows!), we still have a way to run the project and we'd be in a much better position for finding a dataset replacement.
Three examples have defined test data when they leverage intake:

https://github.com/holoviz-topics/examples/blob/main/test_data/walker_lake
https://github.com/holoviz-topics/examples/tree/main/test_data/heat_and_trees
https://github.com/holoviz-topics/examples/tree/main/test_data/datashader_dashboard

I quite like how heat_and_trees approaches that, by saving locally samples of the original data (I think). walker_lake approaches it differently, by modifying the catalog to download smaller chunks, which is practical for testing purposes but doesn't cover us if the dataset goes away.
In addition to landuse_classification, 6 projects rely on intake.
./datashader_dashboard/catalog.yml
./seattle_lidar/catalog.yml
./carbon_flux/catalog.yml
./walker_lake/catalog.yml
./landsat_clustering/catalog.yml
./heat_and_trees/catalog.yml

seattle_lidar, carbon_flux and walker_lake are the only ones from that list that do not have test data.
Given there are not so many projects that would need to be updated with respect to their catalog test data, I'm in favor of keeping the constraint. We can see how it goes when we update these projects. Git isn't ideal for storing data and maybe for some of these projects it's just not possible to come up with test data that is small enough. We can, or even should, host them on HoloViz's S3.

Thank you @maximlt - all of these are valid arguments for the hard testing constraints.
As you point out, the landuse example is the only one skipping these tests by hosting the catalog remotely;
which should be corrected by checking in the catalog with the notebooks - it's good to keep the catalog w/ the notebooks as a general rule.
For any new examples, the best practice should be to do the same so the tests and constraints are consistently applied to everything.
Closing this issue but will review our docs and see if an update is needed with the contents of your thoughtful response above. It would be good to add this someplace to our documentation if it isn't already there.


mm.cfg

TraceOutputFileEnable=1
ErrorReportingEnable=1
PolicyFileLog=1
PolicyFileLogAppend=1
TraceOutputFileEnable=1
AS3Verbose=1
TraceOutputBuffered=0
AS3Trace=0

The above is for Flash. It will primarily affect the output window.
Put in home directory.

Done: https://github.com/mhulse/dotfizzles/blob/391fd93f43e37d02c7ffa2d4c07ad14fb9baa618/mm.cfg


Improve time format

Done in https://github.com/macterra/artx-market/commit/c46617dbff4e3479ce73a9a9b2c441aacd7c27eb


ban:

Prerequisites

[X] I havent used any other script which could have caused the ban.

Script Version
latest
Platform
Webapp
Safety Settings
wait time 10-15
pause cycle 8-10
pause for: 30-45S
pause after buy: 2S
Filter Used
Silve German D1
IF China
IF Silver
Additional Information
none

Is it as soft ban or a hardban you got

Regards
Raymond Chan

On 10 Oct 2022, at 2:50 AM, Dezed2022 @.***> wrote:

Is it as soft ban or a hardban you got
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.

You do realize that this code is also available for EA employees to view, and they most likely have a fraud AI that identifies patterns among the users...

This is just a neat experiment at best, don't use it on your main accounts.

EA Terms & Conditions:

You can only access FIFA, FIFA Ultimate Team, and our FIFA servers using an official version of EA SPORTS FIFA, otherwise it breaks our rules. An official version is one that you bought from us or an authorized retailer. You must also use either an unmodified platform or the official FUT Web and FUT Companion Apps to avoid breaking our rules.


Stack's children can override alignment

Stack can specify the alignment for all its children. However each child should be able to override and specified their own position within the Stack.

Fixed


GDScript highlighting breaks on signal token

GDScript view is breaking with this script:

Preliminary Steps
Please confirm you have...

[ ] reviewed How Linguist Works,
[ ] reviewed the Troubleshooting docs,
[ ] considered implementing an override,
[ ] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
I do not know the location that describes the syntax for gdscript, since the atom has no native support for this language.

since the atom has no native support for this language.

Which atom are you talking about?
I think you should read the troubleshooting docs.

The CSharp coloration comes from an atom library, however there is no native coloring library for GDScript syntax, only on github. I can not find the repository to which I can report this bug.

From the Troubleshooting docs:

Linguist detects the language of a file but the actual syntax-highlighting is powered by a set of language grammars which are included in this project as a set of submodules as listed here.

Is the wording unclear? Should we improve it?


Runequest 3rd Edition character Sheet

First Release

Phil,
Here we go again. the Runequest 3 sheet just merged is throwing an error
with a sheet worker:-
tarting up WEB WORKER
sheetsandboxworker.js?20160926:292 SyntaxError: missing ) after argument
list
at eval ()
at messageHandler (sheetsandboxworker.js?20160926:266)
sheetsandboxworker.js?20160926:293 SyntaxError: missing ) after argument
list
at eval ()
at messageHandler (sheetsandboxworker.js?20160926:266)
sheetsandboxworker.js?20160926:250 Starting up WEB WORKER
sheetsandboxworker.js?20160926:292 SyntaxError: missing ) after argument
list
/js/d20/sheetsandboxworker.js?20160926:293 SyntaxError: missing ) after
argument list
at eval ()
at messageHandler (
https://app.roll20.net/js/d20/sheetsandboxworker.js?20160926:266:6)
app.js?1487867137:38 Final page load.
app.js?1487867137:48 Refresh jukebox List!
I copied the source down from Github to make sure I did not commit the
wrong version and used it on a custom sheet.  It did not throw  any errors.
I have know way of finding out what the issue on the live system.
On 1 March 2017 at 03:57, Phil<EMAIL_ADDRESS>wrote:

Merged #2345 https://github.com/Roll20/roll20-character-sheets/pull/2345
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/2345#event-981228095,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIk__UqWc3wBoNNGJuDwnmskkm4XdJbpks5rhOyYgaJpZM4MM0Mg
.

I'm looking into it. I'll let you know when I find something.

Phil,
Thanks.  there are semicolons missing off the end of a bunch of sheet
workers, could this cause it.
On 2 March 2017 at 19:24, Phil<EMAIL_ADDRESS>wrote:

I'm looking into it. I'll let you know when I find something.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/2345#issuecomment-283752861,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIk__X3i2Tr1MjWUK8j3hTxq9pyn19qiks5rhxd3gaJpZM4MM0Mg
.

No, semicolons in JS are actually pretty useless at this point. It just makes it faster for the browser to parse. I figured out the issue, though. You either need to change the file encoding to UTF-8 or remove the "The Aaron Sheet" console logs on 3501+3502. They have special characters that are breaking the eval of the sheet.
As for why it's breaking one way and not the other, I couldn't say for sure. Probably because one is loaded directly from the database and the other is loaded from a file, so one breaks on encoding and the other does not.

Phil,
Thanks I did both to be on the safe side.
On 2 March 2017 at 19:48, Phil<EMAIL_ADDRESS>wrote:

No, semicolons in JS are actually pretty useless at this point. It just
makes it faster for the browser to parse. I figured out the issue, though.
You either need to change the file encoding to UTF-8 or remove the "The
Aaron Sheet" console logs on 3501+3502. They have special characters that
are breaking the eval of the sheet.
As for why it's breaking one way and not the other, I couldn't say for
sure. Probably because one is loaded directly from the database and the
other is loaded from a file, so one breaks on encoding and the other does
not.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/pull/2345#issuecomment-283759446,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIk__erlN9X4hZMV_oVRcguL49q3z5olks5rhxzwgaJpZM4MM0Mg
.


ci: set minimum TF version for test workflows

Summary
This modules requires Terraform 1.4 and higher. Setting test workflow parameters to ensure that tests don't fail due to a lower version being tested.
Issue
https://lacework.atlassian.net/browse/GROW-2760

Looks good. Actually given we are here, can you just drop the 1.4 req and directly bump it to 1.5? It would help us add the run-time check block (https://developer.hashicorp.com/terraform/language/checks) that would help w/ UX.

Bumping to 1.5 per @badass-aoz


Finetune on ETH3D

Hello，Could you please tell me how to set num_steps and lr when finetuning on eth3d？I guess that I should use the pretrained model on sceneflow and retrain it with greyscale sceneflow dataset. Is it right?

num_steps=4000 and lr=1e-5
Yes, we finetuned the raftstereo-sceneflow.pth weights on additional greyscale sceneflow images, specifically using --saturation_range 0 0 --img_gamma 0.5 2.0 0.8 1.2


Implement ERC20 Smart Contract

Working on this, preliminary steps:

Address Literals #233 #239
Nested Dictionaries #94
_varNames #248
Caller Capability groups from dictionaries (comes from keys array #67 )
Fallback Function #174
Nested subscription i.e. arr[1][2] #94?


undefined object. Angular Cli  1.0.0-beta.11-webpack.8

Please provide us with the following information:

OS?  Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Linux, Ubuntu

Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.5.0
os: linux x64

Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
After install/update angular cli as in docs
ng serve

The log given by the failure. Normally this include a stack trace and some
more information.

Cannot read property 'length' of undefined
TypeError: Cannot read property 'length' of undefined
at Object.getWebpackCommonConfig (/home/reneval/.nvm/versions/node/v6.5.0/lib/node_modules/angular-cli/addon/ng2/models/webpack-build-common.ts:23:25)
at new NgCliWebpackConfig (/home/reneval/.nvm/versions/node/v6.5.0/lib/node_modules/angular-cli/addon/ng2/models/webpack-config.ts:13:30)
at Class.run (/home/reneval/.nvm/versions/node/v6.5.0/lib/node_modules/angular-cli/addon/ng2/tasks/serve-webpack.ts:19:22)
at /home/reneval/.nvm/versions/node/v6.5.0/lib/node_modules/angular-cli/addon/ng2/commands/serve.ts:84:26
at process._tickCallback (internal/process/next_tick.js:103:7)

Mention any other details that might be useful.

Basic code was generated with beta.11-webpack.3

I just ran into the same error after incorrectly upgrading to angular-cli version 1.0.0-beta.11-webpack.3 (from 2).
I followed all of the steps carefully at https://github.com/angular/angular-cli#updating-angular-cli and the error went away.
As of today, I had to use<EMAIL_ADDRESS>and not @latest to actually get the latest webpack version. I wonder if you are pulling version 8 from master or some place else..
Be careful to review all files that need to be replaced, modified, or skipped during the re-run of the ng init phase in your existing project.

problem is in, angular-cli/addon...
npm dosn't install it...

I had this same issue. I was able to fix it by adding the line below to the angular-cli.json file.
"scripts": [],

These intermediate versions did not have update steps in between them, so it was easy to get stuff broken. Following the instructions in https://github.com/angular/angular-cli#webpack-update should allow you to update projects correctly.


GPU ran out of memory while training from scratch

I am trying to train TrackRCNN without the pre-trained save model, I did not use the "load" command in "config" files.  But I got GPU ran out of memory and then the program got stuck(as attached picture). How can I solve this issue? Should I reduce batch_size and learning-rate? I am using  GeForce GTX 1080 Titan GPU with 10GB memory.

I have reduced batch size from 8 to 5, still getting the following message :
" 2020-09-02 21:58:58.883299: W tensorflow/core/common_runtime/bfc_allocator.cc:211] Allocator (GPU_0_bfc) ran out of memory trying to allocate 2.25GiB. The caller indicates that this is not a failure, but may mean that there could be performance gains if more memory were available."
Please suggest how to solve this issue. Thanks.

As the message tells you, this warning is nothing to worry about. It will still train. If the program gets killed randomly, you may be running out of RAM, not VRAM

If you are running out of RAM, that would be the memory on your server. Sorry, I am not able to help you with technical issues regarding your server setup.

Closing this for now, please reopen if needed


It does not work with the Gradle

Hi, I tried to enter the code in my Gradle, compiles everything perfectly but when I enter these lines:
Intent filePickerIntent = new Intent(this, FilePickerActivity.class);
filePickerIntent.putIntExtra(FilePicker.REQUEST_CODE, FilePickerActivity.REQUEST_DIRECTORY);
startActivityForResult(filePickerIntent, FilePickerActivity.REQUEST_DIRECTORY);
I get errors on the words and REQUEST_DIRECTORY and filepicker. Why is this happening?
Thanks in advance

What exactly did you put in your cradle script?

*gradle

This:
repositories {
mavenCentral()
}
dependencies {
'com.github.developerpaul123.filepickerlibrary:library:1.0@aar'
}

Try replacing com.github.developerpaul123.filepickerlibrary:library:1.0@aar with:
'com.github.developerpaul123.filepickerlibrary:library:1.+'

I have the same problem, do not change anything. How can I solve it?

Hmm...can you further explain what exactly your error is? If something is highlighted or underlined red what does your IDE say the error is due to?

This is my error. What do you think?

You're constructor for the Intent is incorrect. When you pass in "this" for your context into your intent you're passing in the context of the onClickListener, not the context of the calling activity. It should be:
Intent mIntent = new Intent(CallingActivity.this, FilePickerActivity.class);

ok, but the error on REQUEST_DIRECTORY and FilePicker.REQUEST_CODE?

What errors are you getting with that?

Cannot resolve symbol REQUEST_DIRECTORY and Cannot resolve symbol FilePicker.

Ahh I see. It should be FilePickerActivity.REQUEST_DIRETORY. Theres a typo in the code on the Readme file. Sorry about that.

Forgive me but I do not understand why I can not find it in the class FilePickerActivity: Request_code and Request_directory

They should still be all caps?

I wrote it in capital letters

What was the error? "Could not resolve..." , something like that?

Yes, that error

Then for some reason the project doesn't know what classes you're trying to refer. Which gradle file did you add my library too? The one in the app module or your top level project gradle script?

I added in module.gradle

Hmm...in your top level gradle script (the one for the project) try adding:
allProjects {
repositories {
mavenCentral()
}
}

It does not work either in this way

Hmmm...I'm not really sure what else could be the cause. Maybe trying cleaning your project? Idk anymore.

doesn't work for me too


Downloads coming over as html files

I just downloaded two courses from Udemy. The downloads appeared to download fine but, when I checked the downloads folders, the attachments had not come down. There were a number of html files which, when I opened them, started a download.
Looking in those HTML files, I can see a link to the file:
<   script type="text/javascript">window.location = "https://drive.google.com/uc?export=download&id=1FdGP5Be2vZI-AqjJvNDwyQVw82M3WhJL";<   /script>
I don't know whether this is a recent thing they have started or whether you can do anything about it. For now, I'll have to go through the downloads and pick out these downloads and do them manually.
Using version 1.8.2. Thanks.

Seeing as that the file is on drive.google.com, this would indicate the attachment is not on Udemy's server, but rather the author hosting the files offsite. I can confirm that as of v1.8.2 attachments are downloading just fine.

Perhaps I was unlucky. I signed up to two courses from completely different people (British company and Australian company) and both have the same issue that links are now to google drive locations. Or, perhaps, this is a new UDemy thing to save them space!

I cant find my downloaded folder or content .... It is empty


Logrus Stackdriver Logs

Description
Refactor github-runner-provisioner logging to use logrus for logging - enabling stackdriver parsing of log levels and separating logs between the different levels.
Blast Radius
Minimal - these are logging changes only.
Dependencies and documentation
Documentation

[ ] I have updated user facing documentation.
[ ] I have updated all Runbooks affected by this change.
[ ]  I updated DEVELOPING.md with any dev tricks I used to work on this code efficiently.
[X] My changes do not have any impact on documentation.

Monitoring

[ ] I have verified that any changes to alerts work as expected.
[ ] My changes affect monitoring rules and/or dashboards, and I made sure they didn't break.
[X] My changes do not have any impact on monitoring.

^ only monitoring so far is an uptime check.
External dependencies

[ ] I have validated that dependencies impacted by this change work as expected.
[X] My changes do not impact external dependencies.

Rosie the Robot checklists

[ ] My changes affect one or more Rosie checklists.
[X] My changes do not have any impact on Rosie's checklists.

Testing

[X] I have validated that my changes work as expected.
[ ] My changes do not require testing.

Testing Strategy
Executed repo tests and verified outputs are as expected.
Security

[X] The changes in this PR have been reviewed for security concerns and adherence to security best practices.

Related Issues or corrective actions
Create logs-based alert for the github runner provisioner
Deployment plan
Merge and verify in argo

Can you post an example of how the logs will look like?
I'd like to see if they are structured in a way that can be interpreted by Google properly.
I started documenting this in Notion, in case you want to read about it.

@aosoriodw
{"level":"info","msg":"Started GitHub provisioner. Listening on :8080","time":"2023-04-05T13:04:09-07:00"}
{"level":"error","msg":"Error getting instance information. error getting EC2 instance information. operation error EC2: DescribeInstances, failed to resolve service endpoint, an AWS region is required, but was not found\n","time":"2023-04-05T13:04:09-07:00"}

Looks like I should rename "level" to "severity" based on that page 👀

@aosoriodw Updated:
{"message":"Started GitHub provisioner. Listening on :8080","severity":"info","timestamp":"2023-04-05T13:21:43-07:00"}
{"message":"Error getting instance information. error getting EC2 instance information. operation error EC2: DescribeInstances, failed to resolve service endpoint, an AWS region is required, but was not found\n","severity":"error","timestamp":"2023-04-05T13:21:43-07:00"}

@aosoriodw New log with httpRequest field:
{"httpRequest":{"latency":"5.459µs","referer":"","remoteIp":"<IP_ADDRESS>:61744","requestMethod":"POST","requestSize":8604,"requestUrl":"/github-runner-provisioner/?dry-run=false","status":200,"userAgent":"curl/7.86.0"},"message":"Request received","severity":"info","timestamp":"2023-04-05T16:07:15-07:00"}


Unit default data missing air emissions and protocol gas???

Context
https://www.epa.gov/system/files/documents/2022-06/ECMPS_QA_Reporting_Instructions_0.pdf
According to the reporting instructions unit default data should have air emissions and protocol gas records.
There weren't any tickets in the backlog for this. need to double check with the EPA

Shall be added as part of UI tickets for Unit Default Test Data


Refactor gql construct output storage

Description of changes

Updates the gql construct to work with the new metadata output format. Specifically, each construct now writes it's own block of stack metadata so that constructs can be used in isolation in a CDK project without an Amplify-specific orchestration layer on top. This change refactors the gql construct to use the new shared package @aws-amplify/backend-output-storage for writing output when no output storage strategy is injected into the ctor
CDK / CloudFormation Parameters Changed

One interface has been prefixed with I and a now-unused method was removed from another interface
Issue #, if available

Description of how you validated changes
Unit tests updated and passing
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Any CDK or CloudFormation parameter changes are called out explicitly

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

I'll also want to run e2e tests on this. It looks like the different module types aren't playing nicely together. I just tested in a sample project, and I'm seeing the following error:
><EMAIL_ADDRESS>synth
> cdk synth

proj_path/node_modules/ts-node/dist/index.js:851
            return old(m, filename);
                   ^
Error [ERR_REQUIRE_ESM]: require() of ES Module proj_path/node_modules/<EMAIL_ADDRESS>from<EMAIL_ADDRESS>not supported.
Instead change the require of index.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
    at require.extensions.<computed> [as .js] (proj_path/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (proj_path/node_modules/@aws-amplify/graphql-construct-alpha/lib/amplify-graphql-api.js:10:34)
    at require.extensions.<computed> [as .js] (proj_path/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (proj_path/node_modules/@aws-amplify/graphql-construct-alpha/lib/index.js:4:29)
    at require.extensions.<computed> [as .js] (proj_path/node_modules/ts-node/dist/index.js:851:20)
    at Object.<anonymous> (proj_path/backend/app.ts:7:35)
    at m._compile (proj_path/node_modules/ts-node/dist/index.js:857:29)
    at require.extensions.<computed> [as .ts] (proj_path/node_modules/ts-node/dist/index.js:859:16)
    at phase4 (proj_path/node_modules/ts-node/dist/bin.js:466:20)
    at bootstrap (proj_path/node_modules/ts-node/dist/bin.js:54:12)
    at main (proj_path/node_modules/ts-node/dist/bin.js:33:12)
    at Object.<anonymous> (proj_path/node_modules/ts-node/dist/bin.js:579:5) {
  code: 'ERR_REQUIRE_ESM'
}

Subprocess exited with error 1

Which corresponds to this line const backend_output_storage_1 = require("@aws-amplify/backend-output-storage"); in the source.


disable inject styles in head

Feature Proposal
To be able to disable injection styles in head tag, may by via a global variable
Feature Use Case
Importing styles via apart file
Possible Implementation

The CSS is no longer required and has been removed in  v3. We'll release an alpha version shortly


Unify top level namespace

As I can't see any reasons to set 2 top level namespaces (Todo and ToDo) I assume it's a typo…
Great tutorial by the way 😺

Awesome!
Thanks 😸


Magic Effects Overlay

*** Feature Request ***
Overlay to see opponent's magic effects, such as binds/barrage times.
Exilent Client has this, but I do not see it on their current feature list. A quick snapshot video is here.

Duplicate of #2011 and #2009; the latter may not be implemented as Exilent is not considered a "trusted" client, so we will not necessarily implement features only offered in that client.


The permissions of the volume mounted were accidentally changed to admin

I use the portainer docker lasted (v2.1.1).
1.create a Volume with public permission
2.mount it to a container,(e.g. /test_vol in container)
3.In container, create a file in /test_vol (e.g. testfile.txt)
4.Volume permission change to  admin already.(No change is expected.

in v1.24.1, the permission is no changed.

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
Thnks for raising this, could it possible to share screenshots from both
portainer versions for further analysis

I do it in http://demo.portainer.io/

Ticket update by Bala Natarajan<EMAIL_ADDRESS>Hi
Thanks , its similar to the issue raised . bug
https://github.com/portainer/portainer/issues/4851
requesting to follow this.

@huib-portainer this seems related to the 2.9.0 resolved https://github.com/portainer/portainer/issues/4851
except that there's no "public" access anymore?

Yes that's fixed in 2.9.0.
And what do you mean?

Results in

OH, wow, no, I was looking for the "public" option when I enable Access control.
which is an interesting UX - it'd be simpler to not have the toggle, and instead have 3 options "public, admin, restricted"
basically "public" != "disable access control" until after a user has ad to be taught that those are synonymous in our UI.

I think we need to be careful about nomenclature here as the word "public" can imply "open to the world".


Unrecognized compiler options

Describe the bug
Some compiler options (mostly irrelevant to static analysis) are not recognized by Clang, therefore the analysis fails.
CodeChecker version
6.22.1
To Reproduce

Check out the Linux kernel
Create a .config file by executing e.g. 'make menuconfig', then press 'Save' and 'Exit'
Build the kernel while logging it, e.g.: 'CodeChecker log -o linux.json -b 'make -j4'
Split linux.json to at least 4 equal parts, called 'linux*.json'
Analyze the code: 'CodeChecker analyze1 -o analyzis linux1.json'

Expected behaviour
The analyzers should analyze the code. Instead, the analysis of most files fail because Clang does not recognize some gcc options and CodeCheckers does not remove them:
-mindirect-branch-cs-prefix
-fno-allow-store-data-races
-fsanitize=bound-strict
-ftrivial-auto-var-init=zero
-fno-hoisting
-fsched-pressure
-falign-loops=1
Desktop (please complete the following information)

OS: Ubuntu Linux
Browser: n/a
Version: Distribution version 23.04, kernel version 6.2.0

Additional context

some more:
-fno-lifetime-dse

Also -fmerge-constants

I think that, because of how fast toolchains move, and because this list will only grow, we should get the option to have a file we can point CodeChecker at which will list compilation flags to remove.
Hmm.... maybe some jq black magic preprocessing of compile_commands.json will work?

Okay, a quick-and-dirty Python script to remove unwanted flags. Modify to your needs.
#!/user/bin/env python

import json

TO_REMOVE = (
        '-fmerge-constants',
        '-mindirect-branch-cs-prefix',
        '-fno-allow-store-data-races',
        '-fsanitize=bound-strict',
        '-ftrivial-auto-var-init=zero',
        '-fno-hoisting',
        '-fsched-pressure',
        '-falign-loops=1',
        )

f = open('compile_commands.json', 'r+')
commands = json.load(f)
for sub in TO_REMOVE:
    print(f"Replacing '{sub}'")
    for c in commands:
        c['command'] = c['command'].replace(sub,'')
f.seek(0)
f.truncate()
json.dump(commands, f, indent=4, ensure_ascii=False)

Fixed by #4028

@jaskij The problem is when flags are not to be removed as-is, but transformed. Like a flag that takes two arguments in GCC but only one in Clang. Or a flag with 0 or 1 becoming a no-foo and foo flag, which is still supported in Clang but in that way.
I would much prefer implementing a Clang flag which turns the presence of unknown flags into warnings instead of errors and just using that flag when passing from CodeChecker.

@whisperity unless those flags impact the correctness of your code, I don't see any harm in simply removing them.
That said, nothing is stopping anyone from extending the handling to massage those flags into versions which Clang will accept.

True, @jaskij. My point was that if and when we design a mechanism by which the user can control the filtering of the compilation commands, this must be kept in mind. I do agree with the general idea, having to change the code and rebuild the package isn't the most ergonomic thing here.

@whisperity I do agree that, ultimately, this should be handled by the user within codechecker itself. The existing solution of "manually" removing those files from the compilation database and then pestering maintainers to update the hardcoded filter is suboptimal.


Doesn't compile on latest MSVC 2019 Community edition

https://gist.github.com/lakinwecker/c9b1178d0559b4febcd4c5aeaec7a1ab
Something about the windows includes/defines is not working. I'm not versed enough in windows development to understand why. Hoping it's a simple fix.
I tried adding an #include <wingdi.h> before including this library, as some googling suggests that this is where LPLOGFONTA is defined, but it didn't fix it.

I figured it out. I was compiling with -DNOGDI which prevents wingdi.h from being included properly.  Closing, as this is not a bug in the library. Sorry for the noise.


onefetch: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by onefetch)

Getting this error with a downloaded version of binary 2.2.0 — onefetch_linux_x86-64.zip
OS: Linux Mint 18.3 Sylvia x86_64
> onefetch
onefetch: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.27' not found (required by onefetch)

> ldd --version
ldd (Ubuntu GLIBC 2.23-0ubuntu11) 2.23
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

libc6 2.23 is the default version shipped with Ubuntu 16.04 Xenial.


Fixes #1193 - Set job log created date to use ISO format in JobResult detail view

Fixes: #1193

Set job log created date to use ISO format in JobResult detail view.

Personally I feel like this is maybe overkill - given the vast majority of Jobs should run to completion in a matter of minutes, the YY-MM-DD and timezone portions of the output are mostly noise. What do you think of just setting it to display HH:MM:SS.ssssss instead? We have the JobResult detail at the top of the page showing the overall date and time of the job, after all.

Personally I feel like this is maybe overkill - given the vast majority of Jobs should run to completion in a matter of minutes, the YY-MM-DD and timezone portions of the output are mostly noise. What do you think of just setting it to display HH:MM:SS.ssssss instead? We have the JobResult detail at the top of the page showing the overall date and time of the job, after all.

What you're proposing is H:i:s.u:

I'm thinking split the difference to include the Y-m-d but without the timezone information? Specifically that would be Y-m-d H:i:s.u:


containers doesnt start

hi
when i try to run containers (even hello-world example) it starts for 2 second and then it exits (as show in docker ps -a)
i use command "docker run -d -p 80:80 hello-world"
only "docker run -d -p 80:80 hypriot/rpi-busybox-httpd" seems to work
what do i do wrong?
edit
i tried recompiling my angular app directly on raspberry but it stack on" run npm install"

Hi,
Could be anything. Please provide more details like which versions do you use which hardware etc.
The hello-world does not work on ARMv6 machines like Pi zero out of the box.

Closing due to inactivity


chore: add screen component docs

Description
This PR comes to solve an issue we have when devs create a new screen and do not find any docs on best practices.
This PR does the following:

Add docs on how to create a backbone of a screen with a simple header
Add docs on how to create a backbone of a screen with an animated header
Add docs on how to create a backbone of a screen with an animated header and sticky header
Add docs on how to solve the issue of nested ScrollViews

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

add screen component docs - mounir

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (add screen component docs - mounir)

  Generated by :no_entry_sign: dangerJS against fefb86b5ef03ce816aa6a8a4c833b0a25c9abf5d


Add README for mta

FLPATH-769
Signed-off-by: Roy Golan<EMAIL_ADDRESS>

According the MTA 7 user interface[1] guide there will still be the option to download
html report, but it maybe be disabled by admins, and will require explicitly enabling it.
I'm not sure how critical the report is for users and to the best of my understanding
its more important we would know how to anaylyze that report and conditionally offer move2kube.
See this for more info in https://issues.redhat.com/browse/FLPATH-941
[1] https://access.redhat.com/documentation/en-us/migration_toolkit_for_applications/7.0/html-single/user_interface_guide/index

ping?


2WD URDF has incorrect inertia values for simulation

Need to adjust the inertia values for the 2wd rover pro/zero with respect to castor wheels + body mass?

Done


Afzal

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature
A clear and concise description of what the bug is.
Expected Behavior
A clear and concise description of what you expected to happen.
Use Case
Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Alternatives Considered
Explain what alternative solutions or features you've considered.
Additional Context
Add any other context or screenshots about the feature request here.

Have a question? Please checkout our Slack Community or visit our Slack Archive.

Describe the Feature
A clear and concise description of what the bug is.
Expected Behavior
A clear and concise description of what you expected to happen.
Use Case
Is your feature request related to a problem/challenge you are trying to solve? Please provide some additional context of why this feature or capability will be valuable.
Describe Ideal Solution
A clear and concise description of what you want to happen. If you don't know, that's okay.
Alternatives Considered
Explain what alternative solutions or features you've considered.
Additional Context
Add any other context or screenshots about the feature request here.

15


Update data/releases/schedule.yaml for April 2023 patches

Add release data for the April 2023 patches:

v1.24.13
v1.25.9
v1.26.4

Additionally:

v1.27.1

I also removed April 2023 from the upcoming patch calendar since it already happened.
Note that I left cherryPickDeadline blank on v1.27.1 because I wasn't sure what made sense for that (afaik it was an out-of-band release due to regression in v1.27.0)

Preview site deep links for convenience:

https://deploy-preview-40780--kubernetes-io-main-staging.netlify.app/releases/
https://deploy-preview-40780--kubernetes-io-main-staging.netlify.app/releases/patch-releases/

/retest

/close

/reopen

@xmudrii Could you try to trigger the build again without losing lgtm label using
git commit --amend --no-edit && git push --force-with-lease

I don't think I can do that since I'm not the PR author, but @milas can you please give it a try?


[WIP] Additional debug data

Add more complete and correct debug data. Depends on https://github.com/dotnet/llilc/pull/1082

Correctly handle this pointers on structure methods
Represent base type more accurately
Represent static fields in type index data (symbol records need to exist for this support to work end to end)
Make UserDefinedTypeDescriptor thread safe (by placing a lock around all public api surface, and reducing the public surface to functions intended for use outside of the function)
Add support for Pointer types
Add support for ByRef types
Add support for Method type indices
Add support for MethodID type indices
Tweak name mangling so that it is possible to create a natvis file that allows simple inspection of arrays in the debugger
Natvis file (currently only hooked up to repronative) that will allow inspection of strings/some arrays naturally in the VS debugger

[WIP] as it depends on https://github.com/dotnet/llilc/pull/1082 to be checked in first, and a proper nuget package created.

I just published ObjectWriter with your changes, could you update this PR with the 19 version?
Changes LGTM.


Bring getblock up to date

Missing chainwork and mediantime
On lbcd:
lbcctl getblock ac280c2a68c57707cc1fedbd025782c76cc2679550aa18cc5bd6e3f64c2a2769
{
  "hash": "ac280c2a68c57707cc1fedbd025782c76cc2679550aa18cc5bd6e3f64c2a2769",
  "confirmations": 1,
  "strippedsize": 16191,
  "size": 16227,
  "weight": 64800,
  "height": 1172332,
  "version": 536870912,
  "versionHex": "20000000",
  "merkleroot": "b3717572eb82f625a1de2735fbb119802032d07b59a2c84d25c5d5bcb4a69128",
  "time":<PHONE_NUMBER>,
  "nonce":<PHONE_NUMBER>,
  "bits": "1a009cca",
  "difficulty":<PHONE_NUMBER>097.069,
  "previousblockhash": "9ee97ed1dbaf34fbf40d755ccb9a23b3074e61b1572a8135397a9f6514d741ca",
  "nameclaimroot": "1c6a4517e9254d0becdfc1dd5257b8c66b58899618e9305f1fab57a7054c12cd",
  "nTx": 33,
  "tx": [
    "07c8b6aa16d59f184e6aea71e613b08be52182869b9fdeba422a0dbf47411383",
    "1f0eeaa0480639805849724e835be04f1e041f73ed1f10caceb4db70c7403876",
    "0a999db30bfa1116646347dc8a6c1baf62ae1998c63640f48c33b02117fc1412",
    ...
  ]
}

On lbrycrd:
lbcctl --notls -s $LBRYCRD_NODE getblock ac280c2a68c57707cc1fedbd025782c76cc2679550aa18cc5bd6e3f64c2a2769
{
  "hash": "ac280c2a68c57707cc1fedbd025782c76cc2679550aa18cc5bd6e3f64c2a2769",
  "confirmations": 1,
  "strippedsize": 16191,
  "size": 16227,
  "weight": 64800,
  "height": 1172332,
  "version": 536870912,
  "versionHex": "20000000",
  "merkleroot": "b3717572eb82f625a1de2735fbb119802032d07b59a2c84d25c5d5bcb4a69128",
  "time":<PHONE_NUMBER>,
  "nonce":<PHONE_NUMBER>,
  "bits": "1a009cca",
  "difficulty":<PHONE_NUMBER>097.069,
  "previousblockhash": "9ee97ed1dbaf34fbf40d755ccb9a23b3074e61b1572a8135397a9f6514d741ca",
  "nameclaimroot": "1c6a4517e9254d0becdfc1dd5257b8c66b58899618e9305f1fab57a7054c12cd",
  "nTx": 33,
  "tx": [
    "07c8b6aa16d59f184e6aea71e613b08be52182869b9fdeba422a0dbf47411383",
    "1f0eeaa0480639805849724e835be04f1e041f73ed1f10caceb4db70c7403876",
    "0a999db30bfa1116646347dc8a6c1baf62ae1998c63640f48c33b02117fc1412",
    ...

  ],
  "mediantime":<PHONE_NUMBER>,
  "chainwork": "000000000000000000000000000000000000000000000964a8366f9822316ea1"
}

I was getting worried that chainwork/mediantime had no implementation in "lbcd", but found what I needed here:
https://github.com/lbryio/lbcd/blob/7f9fe4b97058830be58f79e8a54530863d5cd829/blockchain/blockindex.go#L82

Yeah, the mediantime is part of consensus, so it must be existing somewhere.
The chainwork, however, in lbcd currently has different semantics - accounting works since each restart of lbcd, instead of historically accumulated numbers. It works for the chain as it only cares about the relative work between branches, if any, for choosing the one with most work.
Currently, the only known external users of that field is block explorers for displaying information. While it probably won't block any functional integration, still very nice to have if we can reconstruct/calculated the accumulated work at start-up.

All the code I investigate indicates chainwork (workSum) is predictable, and is initialized during the "Loading block index" phase:
https://github.com/lbryio/lbcd/blob/7f9fe4b97058830be58f79e8a54530863d5cd829/blockchain/chainio.go#L1104
initBlockNode() is where the parent workSum is added. This seems consistent across bcd, lbrycrd, and C++ bitcoin.
Maybe there is some separate concept with a similar purpose/name that you are thinking of?

I didn't dig too deep into that last time, so you maybe right, which would be a good news.
You can test against a public lbrycrd instance I setup for validation when you export it to the rpcserver.
lbcctl --notls -s <IP_ADDRESS> -u rpcuser -P rpcpass getblock ac280c2a68c57707cc1fedbd025782c76cc2679550aa18cc5bd6e3f64c2a2769


Added default no-op function for flatmap

Fixes #738
Changes
in datapipe's common functions:

added _no_op_fn definition

in FlatMapperIterDataPipe class

added _no_op_fn method use for default callable use

Waiting for company CLA signature, should be shortly

Unit test added, also I fixed _no_op_fn to always return iterables.


Amend "Advanced settings for shareable links" section

The section "Advanced settings for shareable links" currently says:
"If your external sharing setting for SharePoint is set to allow shareable links (even if external sharing is currently turned off), you can set an expiration time for those links by choosing a value from the Links expire within drop-down list. You can also choose whether shareable links can give people permission to edit shared files and folders."
The explanation given is not complete and also erroneous (the dropdown also gives permission to upload files). It should explain the the three existing configuration options in detail, namely it should include the following information:

Links must expire within this number of days: Links will expire within the given timeframe for all users. If set to zero (0) there is no expiration on links.

Can this be overruled by users?

Files: Can be set to "View" and "View, edit and upload".

"View, edit and upload" should be explained

Folders: Can be set to "View" and "View, edit and upload".

"View, edit and upload" should be explained

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

ID: 40a570bb-2567-565c-e9ff-bf1ccbf38d0e
Version Independent ID: 3d342dea-9dd3-008c-20c6-902452302e95
Content: Manage sharing in OneDrive and SharePoint
Content Source: OneDrive/manage-sharing.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@DennisGaida Thank you for this feedback
I will get this over to the SharePoint team for investigation and updating. Thank you for taking time to make the docs better.
I was able to get this into the backlog for the SharePoint team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

PR #699


Eip 1153

Purpose
EVM PR: https://github.com/Taraxa-project/taraxa-evm/pull/132
Depends on last 2 evm PRs
Fixes https://github.com/Taraxa-project/taraxa-evm/issues/127
How does the solution address the problem

Changes made

same changes as here ? https://github.com/Taraxa-project/taraxa-node/pull/2249

prnet cleaned-up successfully


When creating a cluster if the authentication password is set to empty cluster members cannot join

Currently during cluster setup, if the first node enables password authentication but sets it to empty then other cluster noders are unable to join.
This is easily done during lxd init by just accepting the defaults.
We should enforce that if password authentication is enabled a non-empty password is provided.

@tomponline Interested in working on this but just getting started poking around the codebase. How do you want this implemented? Some target questions:

How is password authentication "enabled" formally for clusters? I didn't see a configuration option during init that seems to explicitly enable password authentication. Is this just a function of whether the trust-password is part of the config?
Where do you see this validation happening? Does it make sense to add it somewhere like https://github.com/lxc/lxd/blob/master/lxd/main_init.go and have an error thrown if the user indicated it's a bootstrap node and is part of a cluster? Similar to the validation/defaulting happening here? https://github.com/lxc/lxd/blob/master/lxd/main_init.go#L133.

@komish so an example of the issue is this:
Setting up node 1 in a new cluster: (just press return when being asked for the trust password for new clients without specifying one).
root@v1:~# lxd init
Would you like to use LXD clustering? (yes/no) [default=no]: yes
What name should be used to identify this node in the cluster? [default=v1]:
What IP address or DNS name should be used to reach this node? [default=<IP_ADDRESS>]:
Are you joining an existing cluster? (yes/no) [default=no]:
Setup password authentication on the cluster? (yes/no) [default=yes]:
Trust password for new clients:
Again:

We would like the validation to reject empty passwords at this stage, as the problem this causes is exemplified below:
Now on node 2, try joining the cluster with an empty trust password:
root@v2:~# lxd init
Would you like to use LXD clustering? (yes/no) [default=no]: yes
What name should be used to identify this node in the cluster? [default=v2]:
What IP address or DNS name should be used to reach this node? [default=<IP_ADDRESS>]:
Are you joining an existing cluster? (yes/no) [default=no]: yes
IP address or FQDN of an existing cluster node: <IP_ADDRESS>
Cluster fingerprint: b54e80cb34ebbd84adc16f40d22613875a4f931836f7c708f10c4ca6a486bae3
You can validate this fingerprint by running "lxc info" locally on an existing node.
Is this the correct fingerprint? (yes/no) [default=no]: yes
Cluster trust password:
All existing data is lost when joining a cluster, continue? (yes/no) [default=no] yes
Error: Failed to setup trust relationship with cluster: Failed to add client cert to cluster: not authorized

The asking this question is here https://github.com/lxc/lxd/blob/master/lxd/main_init_interactive.go#L233

Right, looking at all the places where we use cli.AskPassword or cli.AskPasswordOnce, I think the easy fix for this is to simply make those functions refuse an empty string as a valid value.
So that would be a change directly to shared/cmd/ask.go to make both functions call invalidInput() when provided with an empty string and then have them ask again until they get a non-empty response.

@komish assigning the issue to you for now.

Understood - thanks for the guidance. More to come as I have it!

Just an update that I think I'm almost done with this. Just working on testing changes but I'm fighting pre-installed (via snap) lxd in cloud images of Ubuntu 20.04, and getting my source-built binary in place to test. I'll get more time on it going into the weekend.

@komish if its easier you can built your lxd/lxc go binaries and then move them into the snap temporarily using:
sudo mv lxd /var/snap/lxd/common/lxd.debug
sudo mv lxc /var/snap/lxd/common/lxc.debug
sudo systemctl reload snap.lxd.daemon

Circling back in case anyone finds this discussion helpful in the future. I figured out that I can just run my built lxd binary and then run lxd init and it'll talk to the socket that's generated by lxd, even on a system that has it installed via snap already. That was enough to test the init workflow. 👍
Thanks again for the guidance! More than helpful for someone who hasn't looked at the lxd codebase!


Example lint script not working

What version of Turborepo are you using?
None
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
"lint": "TIMING=1 eslint src/**/*.ts* --fix", does not lint files.
"lint": "TIMING=1 eslint 'src/**/*.ts*' --fix", does lint files.
https://stackoverflow.com/questions/54165756/eslint-glob-is-not-considering-all-directories-recursively
Expected Behavior
Should lint files.
To Reproduce
Just try it.

"lint": "TIMING=1 eslint src --ext .ts,.tsx",
This is probably the best because it's not platform specific and it's recursive.

Could you link to which example you're talking about?


chore: updated dependencies

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.94%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
106

Relevant Lines:
112

💛  - Coveralls


What's the behavior for a Pod with restartPolicy Always when it is in PodFailed?

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
https://github.com/ray-project/kuberay/pull/2217#discussion_r1710635757
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Just my understanding:
If the Failed Pod is not managed by any controller, it will not be automatically rescheduled. In this case, administrator or user intervention is required, such as deleting the Failed Pod and creating a new one, or adjusting cluster and Pod configurations to try and avoid future failures.


HTTP Request node: wrong http exception handling

Current Behavior
When you enable the option "Only send non-2xx responses to Catch node" in an http request node if you get an http exception from server, the node always sends the output message and the catch node never gets the exception.
Expected Behavior
Enabling "Only send non-2xx responses to Catch node" should send message only to catch node
Steps To Reproduce
Try an http request node with "Only send non-2xx responses to Catch node"
Example flow
[
    {
        "id": "c72880672de95bf5",
        "type": "http request",
        "z": "aef408433c5496a0",
        "name": "",
        "method": "POST",
        "ret": "txt",
        "paytoqs": "ignore",
        "url": "https://www.google.it/",
        "tls": "",
        "persist": true,
        "proxy": "",
        "insecureHTTPParser": false,
        "authType": "",
        "senderr": true,
        "headers": [],
        "x": 270,
        "y": 1160,
        "wires": [
            [
                "1537d57cf3ade772"
            ]
        ]
    },
    {
        "id": "1537d57cf3ade772",
        "type": "debug",
        "z": "aef408433c5496a0",
        "name": "debug 9",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "true",
        "targetType": "full",
        "statusVal": "",
        "statusType": "auto",
        "x": 500,
        "y": 1160,
        "wires": []
    },
    {
        "id": "a3b7bf20f113b9de",
        "type": "inject",
        "z": "aef408433c5496a0",
        "name": "",
        "props": [
            {
                "p": "payload"
            },
            {
                "p": "topic",
                "vt": "str"
            }
        ],
        "repeat": "",
        "crontab": "",
        "once": false,
        "onceDelay": 0.1,
        "topic": "",
        "payload": "",
        "payloadType": "date",
        "x": 100,
        "y": 1160,
        "wires": [
            [
                "c72880672de95bf5"
            ]
        ]
    },
    {
        "id": "84d5d28b82cfe4aa",
        "type": "catch",
        "z": "aef408433c5496a0",
        "name": "",
        "scope": [
            "c72880672de95bf5"
        ],
        "uncaught": false,
        "x": 270,
        "y": 1220,
        "wires": [
            [
                "6f440eab87b1b68c"
            ]
        ]
    },
    {
        "id": "6f440eab87b1b68c",
        "type": "debug",
        "z": "aef408433c5496a0",
        "name": "debug 10",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "true",
        "targetType": "full",
        "statusVal": "",
        "statusType": "auto",
        "x": 500,
        "y": 1220,
        "wires": []
    }
]

Environment

Node-RED version: 3.0.2
Node.js version: 16.17.1
npm version: 8.15.0
Platform/OS: MacOS / Ubuntu Linux
Browser: Safari/Chrome/Edge

Also check this issue: https://github.com/node-red/node-red/issues/3082
I see the reason behind setting:
opts.throwHttpErrors = false;

Anyway, we need to change the way exceptions are managed.

This is the relevant comment in the code:
https://github.com/node-red/node-red/blob/32a49a1ef17894b6dd2dd83b5b2450f94ab3a27f/packages/node_modules/%40node-red/nodes/core/network/21-httprequest.js#L629-L633
We didn't make the suggested change in 3.x.
We do need to more clearly define the desired behaviour. I propose the following:

Enable the 'Only send non-2xx responses to Catch node` by default for new HTTP Request nodes (existing nodes keep their same behaviour)
If that option is enabled

any 2xx response will be emitted by the node in the normal manner
anything else (including network level errors) will be logged as an error for a Catch node to handle

That keeps the golden path on the main flow, and allows all errors to be handled via a Catch node. I think that is the most expected behaviour.
As it will be a change in behaviour, we'll have to save it for 4.x - which will be coming fairly soon once 3.1 is out of the way.


docs(tutorial): add more detailed explanation for tutorials

Description
Add detailed explanation to rosbag replay simulation and planning simulation
Add a brief explanation of localization: why we need it and how it works
In the rosbag replay simulation, there should be other modules than localization working but I'm not sure how they work so I added only the explanation of the localization module.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The Reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@kenji-miyake Is there any possibility that we will add more tutorials to this section that are not related to simulations? If not, then perhaps the main page/section could be renamed as "Simulation tutorials" so that the purpose of the page is clear without needing to be explained.

@LalithVipulananthan Thank you for your suggestion. I think it's good!
But even if we rename the title to Simulation tutorials, I think we need some brief introduction sentences at the beginning.

But even if we rename the title to Simulation tutorials, I think we need some brief introduction sentences at the beginning.

@kenji-miyake Noted. I have reworked the page, taking into account some of Ishita-san's changes and my proposal to rename the page to Simulation tutorials. As a result my version is quite different. Should I submit it as a commit to this PR, or submit a new PR instead?

@LalithVipulananthan If the diff is large, I think it's better to create a new PR.

@IshitaTakeshi Do you think that #124 covers the additional detail that you wanted to add in this PR, or is there anything else that you wanted to add?

@LalithVipulananthan  For the contents that should be added to that page, yes.
I need to add a more detailed explanation of the localization module (what it is for and how it works) to the pages introduced in https://github.com/autowarefoundation/autoware-documentation/pull/86 but it should be in another PR.

https://github.com/autowarefoundation/autoware-documentation/pull/124 covers the overview part


Passing type arg to non-generic

Description:
Covers this error
 type T = {};
 var v4: T<string>; // Should error because T is not a generic

Since Type::Alias might be removed I ll delay this PR in order to try and find a solution without relying on matching Type::Alias

I think I can't remove it, but you should never match on it anyway


chore(deps): update all non-major

This PR contains the following updates:

Package
Type
Update
Change

anyhow
dependencies
patch
1.0.78 -> 1.0.79

anyhow
dependencies
patch
1.0.76 -> 1.0.79

async-trait
dependencies
patch
0.1.75 -> 0.1.77

clap
dependencies
patch
4.4.11 -> 4.4.13

rust-embed
dependencies
minor
8.1.0 -> 8.2.0

serde (source)
dependencies
patch
1.0.193 -> 1.0.195

Release Notes

dtolnay/anyhow (anyhow)
v1.0.79
Compare Source

Work around improperly cached build script result by sccache (#340)

dtolnay/async-trait (async-trait)
v0.1.76
Compare Source

Documentation improvements

clap-rs/clap (clap)
v4.4.13
Compare Source
Documentation

Fix link to structopt migration guide

v4.4.12
Compare Source
Performance

Only ask TypedValueParser for possible values if needed

pyros2097/rust-embed (rust-embed)
v8.2.0

Fix naming collisions in macros #230. Thanks to hwittenborn

serde-rs/serde (serde)
v1.0.195
Compare Source

Prevent remote definitions of tuple struct or tuple variant from triggering dead_code warning (#2671)

v1.0.194
Compare Source

Update proc-macro2 to fix caching issue when using a rustc-wrapper such as sccache

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 0.7.0 :tada:
The release is available on:

GitHub release
v0.7.0

Your semantic-release bot :package::rocket:


Update Composer dependencies (2021-12-29-21-12)

Created multidev environment pr-29 for circleci-orb-demo-d82.

Visual regression test passed!
View the visual regression test report


revised version of the Open learning Guide

Would it make sense to add here a revised version of the Open Learning guide by r0g_agency?
Check https://github.com/opencultureagency/Open-Learning-Guide
We could work out a visual of the Open Science related OER available including use cases applied in various regions of the globe

Yes, absolutely! Thanks for this - we'll make sure to include it when production on this module is on :)

let me make sure this get's in :P


Add warning flags to build

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


Turn off the executable bit for .md files and the Dockerfile

Dockerfile does not need to be executable
Markdown files does not need to be executable

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


Add a rollback_ctx field for saving the context of undo log.

Add a rollback_ctx field for saving the context of undo log. such as serializer.

WARN：Incompatible with the old version

Ⅰ. Describe what this PR did

Add rollback_ctx field to table undo_log.
Save context when encode undo log.
Parse context and get serializer before decode undo log.
Add getName and getDefaultContent() of UndoLogParser.

Ⅱ. Does this pull request fix one issue?
#1122

Codecov Report

Merging #1123 into develop will increase coverage by 0.06%.
The diff coverage is 52.23%.

@@              Coverage Diff              @@
##             develop    #1123      +/-   ##
=============================================
+ Coverage      41.83%   41.89%   +0.06%
- Complexity      1361     1374      +13
=============================================
  Files            243      244       +1
  Lines          10141    10191      +50
  Branches        1325     1336      +11
=============================================
+ Hits            4242     4270      +28
- Misses          5351     5364      +13
- Partials         548      557       +9

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/io/seata/common/util/StringUtils.java
26.58% <ø> (+2.53%)
15 <0> (+2)
:arrow_up:

...va/io/seata/rm/datasource/undo/UndoLogManager.java
21.05% <16%> (-1.59%)
8 <0> (ø)

.../datasource/undo/parser/FastjsonUndoLogParser.java
71.42% <33.33%> (ø)
3 <1> (?)

.../io/seata/rm/datasource/undo/UndoLogConstants.java
66.66% <66.66%> (ø)
1 <1> (?)

...ain/java/io/seata/common/util/CollectionUtils.java
50% <76%> (+28.26%)
13 <8> (+8)
:arrow_up:

...seata/rm/datasource/undo/UndoLogParserFactory.java
76.92% <81.81%> (-3.08%)
3 <2> (+2)

...server/store/file/FileTransactionStoreManager.java
45.99% <0%> (-0.35%)
19% <0%> (ø)

Continue to review full report at Codecov.

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

I think it's necessary to consider scalability.
If the default protostaff is found to be defective after 1.0, it will be a troublesome to replace the serialization protocol. The compatibility of existing data should be considered in upgrading.

@slievrly  Do you mean all the undo log must use one serialization type?
I thought about it and I think if we save context to each line can handle the following scenes:

Our user changes their serialization type from json to protostuff, We need to be compatible with historical data
When we add the compress feature, and we can add key/value into this context, need to be compatible with historical data, too.

Is this serialization type better placed in a global file configuration? Instead of putting it on each line of undolog data records.

@ujjboy There is indeed a scene of switching serialization that you said, but the switch requires the user to restart the service, so whether you can ask the user to ensure that the undolog has no data, it seems a waste of each field. In fact, I don't think it is necessary to make a switch configuration because the undolog mechanism should be transparent to the user.

@slievrly

so whether you can ask the user to ensure that the undo log has no data

But how to make sure they have no undo log data?  stop all the system?

it seems a waste of each field

Yes, maybe tens of bytes, but will discharge by better serialization.

In fact, I don't think it is necessary to make a switch configuration because the undolog mechanism should be transparent to the user.

Users can choose a serialization by considering the performance and resource usage, instead of specifying one by the framework. We need to give the user more choices, also user no need to know the detail of undo log mechanism.

I think it is ok, because of the undo log will be deleted later, so store more data is acceptable.

@slievrly

so whether you can ask the user to ensure that the undo log has no data

But how to make sure they have no undo log data? stop all the system?

it seems a waste of each field

Yes, maybe tens of bytes, but will discharge by better serialization.

In fact, I don't think it is necessary to make a switch configuration because the undolog mechanism should be transparent to the user.

Users can choose a serialization by considering the performance and resource usage, instead of specifying one by the framework. We need to give the user more choices, also user no need to know the detail of undo log mechanism.

undolog context is necessary. Currently only useful for the rollback_info field, so whether to put it directly into the rollback_info field, do a general parsing first, parse out the context, and then serialize the rollback_info according to the context.


Cannot load libllama from Mac with Intel CPU

Is the provided libllama.dll only working for Mac with M1 M2 CPU?
Got the following error when trying to load it on Mac with Intel CPU, however it is working fine on Mac with M2 CPU
System.TypeInitializationException: The type initializer for 'LLama.Native.NativeApi' threw an exception.
---> LLama.Exceptions.RuntimeError: The native library cannot be found. It could be one of the following reasons:

No LLamaSharp backend was installed. Please search LLamaSharp.Backend and install one of them.

You are using a device with only CPU but installed cuda backend. Please install cpu backend instead.

The backend is not compatible with your system cuda environment. Please check and fix it. If the environment is expected not to be changed, then consider build llama.cpp from source or submit an issue to LLamaSharp.

One of the dependency of the native library is missed.
at LLama.Native.NativeApi..cctor() in /Users/eddyma/Github/LLamaSharp/LLama/Native/NativeApi.cs:line 36
--- End of inner exception stack trace ---
at LLama.Native.NativeApi.llama_max_devices()
at LLama.Abstractions.TensorSplitsCollection..ctor() in /Users/eddyma/Github/LLamaSharp/LLama/Abstractions/IModelParams.cs:line 111
at LLama.Common.ModelParams..ctor(String modelPath) in /Users/eddyma/Github/LLamaSharp/LLama/Common/ModelParams.cs:line 89
at LLama.WebAPI.Services.StatefulChatService..ctor(IConfiguration configuration) in /Users/eddyma/Github/LLamaSharp/LLama.WebAPI/Services/StatefulChatService.cs:line 19
at System.RuntimeMethodHandle.InvokeMethod(Object target, Span1& arguments, Signature sig, Boolean constructor, Boolean wrapExceptions) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(ServiceCallSite callSite, TArgument argument) at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope) at Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(Type serviceType) at System.Collections.Concurrent.ConcurrentDictionary2.GetOrAdd(TKey key, Func`2 valueFactory)
at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
at Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ServicesModelBinder.BindModelAsync(ModelBindingContext bindingContext)
at Microsoft.AspNetCore.Mvc.ModelBinding.ParameterBinder.BindModelAsync(ActionContext actionContext, IModelBinder modelBinder, IValueProvider valueProvider, ParameterDescriptor parameter, ModelMetadata metadata, Object value, Object container)

Hello. I also have the same issue, and when I asked a question at #58, I received this reply.

Hello. I also have the same issue, and when I asked a question at #58, I received this reply.

thanks for your info, do you have the intel dylib for handy?

I decided to build it myself, for those who need libllama.dylib for Mac Intel, you might try this one
libllama.dylib.zip
Hope this helps
Cheers

@mayuanyang , @nappa0326. I'm not able to test this, but I give a try in this branch to generate Intel binaries. If you can give try to the libllama.dylib generated in the deps binaries that you can download from this run:
https://github.com/SignalRT/LLamaSharp/actions/runs/6754571177#artifacts
The library is in the folder macOS-x86_64:

If this works should be possible to include this in the nuget packages. Let me know if it works.

Hi @SignalRT
I tried both the dylib i built and the one you mentioned from the Action, they both seems loading fine, however i got weird result as screenshot below, any thought?

@mayuanyang  I'm not sure that metal works on Intel CPUs. Theoretically the binary of my compilation should disable METAL, but it seems that it's using metal....
Please try first this solution:
You can explicitly disable GPU inference with the --n-gpu-layers|-ngl 0 command-line argument.
And as second option this solution:
To disable the Metal build at compile time use the LLAMA_NO_METAL=1 flag or the LLAMA_METAL=OFF cmake option.

@SignalRT have tried that, still generate weird output

@mayuanyang . I think that this is not related with the intel library. It's related to the llama.cpp version. I have the same result in arm64 if I build the library with the current version. And it works ok with the version:
https://github.com/ggerganov/llama.cpp/commit/207b51900e15cc7f89763a3bb1c565fe11cbb45d
It seems that the changes in the main.yaml to introduce the build to support macOS Intel works, because it loads and gets the same results that I get with the current llama.cpp
To close this issue If you can build the library from the 207b519 commit id from llama.cpp and check if every thing works find it would help a lot.
It will also help to check it with the Intel build metal works and can be deactivated with the gpu layers. It will help to create the right nuget package to the MacOS intel.

I can confirm that the garbage in the output is related with the changes in latest llama.cpp. I make a PR #249 with the changes in the source code. If you test the intel binaries with this branch it should work ok.

@SignalRT FYI, I manage to compile the llama.cpp on Mac Intel and run it, things seems to be working fine, hope that helps, happy to submit PR for any help if required :)

See #258 which is introducing Intel Mac support. It should be included in the next release (very soon).

@mayuanyang , Please confirm that the current version solve all the issues with OSX Intel.

it is working now, thanks


bug: BufReadPre and BufReadPost autocommand events not triggering

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.9.4 release
Operating system/version
Arch Linux
Describe the bug
When running resession.load on "VimEnter" event like suggested in the docs it seems that events like BufReadPre and BufReadPost are not triggered as they should when files are being loaded into the editor. This breaks plugin lazy loading for file reading, auto commands that the user might have set up when files are read into the buffer, etc.
Steps To Reproduce

run rm -rf .repro to make sure it's a fresh install
run nvim -u repro.lua to instantiate the editor
run :e repro.lua to load a file (see that messages about BufReadPre/BufReadPost happened)
run :q to quite and save the session
run nvim -u repro.lua
run :messages to see that nothing is shown
quit with :q
run nvim -u repro.lua repro.lua to open the file directly
see that messages about BufReadPre/BufReadPost happened

Expected Behavior
When files are read into the editor even when restoring from a session it should trigger the expected autocommand events so that it plays nicely with automations the user has set up such as to load plugins or do an action when files are loaded.
Directory structure
No response
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs { "config", "data", "state", "runtime", "cache" } do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system {
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  }
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "stevearc/resession.nvim",
    config = function()
      require("resession").setup {
        -- add any needed settings here
      }
    end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme "tokyonight"

local resession = require "resession"

vim.api.nvim_create_autocmd("BufReadPre", {
  callback = function() print "BUFREADPRE HAPPENED" end,
})

vim.api.nvim_create_autocmd("BufReadPost", {
  callback = function() print "BUFREADPOST HAPPENED" end,
})

vim.api.nvim_create_autocmd("VimLeavePre", {
  callback = function() resession.save "last" end,
})

vim.api.nvim_create_autocmd("VimEnter", {
  callback = function()
    if vim.fn.argc(-1) == 0 then resession.load("last", { silence_errors = true }) end
  end,
})

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

I also get the same behavior if I remove the "VimEnter" autocmd and just load the session manually with :lua require("resession").load("last") which also doesn't trigger any sort of BufReadPre/BufReadPost autocmd events even though a file has been read

This might be because vim.o.eventignore is set to "all" during loading, I would assume for redraw reasons / because autocmds could trigger something that messes up the layout. Maybe re-enabling autocmds temporarily while loading buffers would solve this? I can make a PR :)

I also experience this issue for
autocmd("VimEnter", {
    desc = "Save restore on enter",
    group = augroup("resession_auto_save", { clear = false }),
    callback = function()
      -- Only load the session if nvim was started with no args
      if vim.fn.argc(-1) == 0 then
        resession.load(get_session_name(), { dir = "dirsession", silence_errors = true, notify = true })

        -- See the bug https://github.com/stevearc/resession.nvim/issues/44
        -- We retirgger all buffers here such that LSPs get attached.
        -- vim.cmd.doautoall "BufReadPost"
      end

      -- Delete the current autocmd.
      return true
    end,
  })

This might be because vim.o.eventignore is set to "all" during loading, I would assume for redraw reasons / because autocmds could trigger something that messes up the layout. Maybe re-enabling autocmds temporarily while loading buffers would solve this? I can make a PR if I find a solution :)
Edit: I can reproduce BufReadPre not triggering (only on the first file opened though), but BufReadPost always seems to work properly.

mark.

mark.

Hacked around for a few minutes, didn't find a solution and it wasn't particularly problematic so I never went back to it, sorry. I can maybe look into it again though.

A decent workaround I've used is to just call
vim.cmd.doautoall "BufReadPost"

Hah yeah that's what I ended up doing as well, added that to my post_load handler though since I do a lot of lazy loading.

https://github.com/gabyx/astronvim/blob/main/autocmds.lua#L52

I believe the issue is with the VimEnter autocommand, it needs to use nested = true (:help autocmd-nested):
vim.api.nvim_create_autocmd("VimEnter", {
  callback = function()
    -- Only load the session if nvim was started with no args
    if vim.fn.argc(-1) == 0 then
      resession.load(get_session_name(), { dir = "dirsession", silence_errors = true })
    end
  end,
  nested = true,
})

Unfortunately if you use your repro.lua to test, it will still appear to fail because resession runs :edit silently when restoring a session (emsg_silent is equivalent to :silent!), which completely suppresses all output:
https://github.com/stevearc/resession.nvim/blob/742aba4998123fc11f490a3aeffe8f550b2cb789/lua/resession/init.lua#L625
With a bit of hackery, we can get the messages to show up:
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs { "config", "data", "state", "runtime", "cache" } do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system {
    "git",
    "clone",
    "--filter=blob:none",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  }
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "stevearc/resession.nvim",
    config = function()
      require("resession").setup {
        -- add any needed settings here
      }
    end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

local function force_print(s)
  -- equivalent to :unsilent echom
  vim.cmd.echom({ args = { vim.fn.string(s) }, mods = { unsilent = true } })
end

vim.cmd.colorscheme "tokyonight"

local resession = require "resession"

vim.api.nvim_create_autocmd("BufReadPre", {
  callback = function() force_print "BUFREADPRE HAPPENED" end,
})

vim.api.nvim_create_autocmd("BufReadPost", {
  callback = function() force_print "BUFREADPOST HAPPENED" end,
})

vim.api.nvim_create_autocmd("VimLeavePre", {
  callback = function() resession.save "last" end,
})

vim.api.nvim_create_autocmd("VimEnter", {
  callback = function()
    if vim.fn.argc(-1) == 0 then resession.load("last", { silence_errors = true }) end
  end,
  nested = true,
})

An easier way is just to compress a file with gzip and observe that it is correctly decompressed (i.e. the gzip plugin's BufReadPost autocmd worked).
Also, with my repro.lua, removing the VimEnter autocmd and doing :lua require("resession").load("last") manually also runs both BufReadPre and BufReadPost correctly.

This worked great @AThePeanut4 ! Thanks for the recommendation and for updating the docs. I have thoroughly tested it and it seems to work perfectly.


integrate github self hosted runners with 1 Password

tried some samples, but i may not have access to create a service account so i can have the service access token.
will be good if someone with 1Password access, can create the service access token and put it in github

        #   uses: 1password/load-secrets-action@v1
        #   with:
        #     export-env: true
        #   env:
        #     OP_SERVICE_ACCOUNT_TOKEN: ${{ secrets.OP_SERVICE_ACCOUNT_TOKEN }}
        #     SERVER_IP: op://opi-lab/tgen1/URL
        #     SERVER_USER: op://opi-lab/tgen1/username
        #     SERVER_PASS: op://opi-lab/tgen1/password