Alembic support

Hi, is it possible to use this with alembic?

Hi @kimdre,
Yes it's possible - https://github.com/dorosch/sqlalchemy-timescaledb/blob/master/sqlalchemy_timescaledb/dialect.py#L13

Thanks, do you need to specify the hypertable paramaters manually in the migration? I noticed that when I try to autogenerate a migration these hypertable parameters weren't added/included to the migration file.
E.g. like so:
Parameter
__table_args__ = ({
        'timescaledb_hypertable': {
            'time_column_name': 'timestamp'
        }
    })

Migration
op.create_table(
        TABLE_NAME,
        sa.Column('ts', sa.DateTime),
        sa.Column('col1', sa.String(50)),
        sa.Column('col2', sa.String(50)),
        schema=SCHEMA,
        if_not_exists=True,)

    op.execute(f"SELECT create_hypertable('{SCHEMA}.{TABLE_NAME}', 'ts');")

Actually, there is no such way as the built-in mechanism is used to support hypertables. It is necessary to perform sql command, which is difficult to add in migration, to create a table.
If you have any additional questions, please let me know


Add LocalParsedDatasource

[ch2769]
Depends on #3933

@wemrysi if it's :+1: then I'll do your suggestion separately and not hold up merge for it. The companion object is more in line with the pattern we've been following elsewhere so I'm all for it.


Initial service code gutted from TPS

Contains a status/version endpoint and a db.

Can you add a DEVELOPMENT.md that has instructions for how to run locally?

Is there an equivalent to WSM's ./scripts/write-config.sh ?
How do I start db? (With WSM, it's ./service/local-dev/run_postgres.sh start)
Gradle command for starting Java server
Gradle commands for running tests. WSM puts integration test command in integration/README.md, and non-integration test commands in DEVELOPMENT.md.

I'd like to start a local server and use swagger against it. And run tests.

In lieu of proper documentation (yet), the process should be similar to the other services:

./scripts/write-config.sh is there but looks incomplete? Without access to Broad environments, I can't test most of its functionality
Using the same run_postgres script, but I put it in ./scripts/. Should it be moved to ./service/local-dev/?
./gradlew bootRun
./gradlew build or ./gradlew test
Integration should be the same i.e../gradlew runTest --args="configs/integration/GetStatus.json /tmp/TR" but once again I can't test this :(

In lieu of proper documentation (yet), the process should be similar to the other services:

./scripts/write-config.sh is there but looks incomplete? Without access to Broad environments, I can't test most of its functionality
Using the same run_postgres script, but I put it in ./scripts/. Should it be moved to ./service/local-dev/?
./gradlew bootRun
./gradlew build or ./gradlew test
Integration should be the same i.e../gradlew runTest --args="configs/integration/GetStatus.json /tmp/TR" but once again I can't test this :(

Thanks.
version endpoint has some nulls, is that expected?

When I run ./gradlew test --scan, I get a prompt about TOS:

You can get rid of the prompt with these lines
Here's a build scan from ./gradlew test --scan: https://scans.gradle.com/s/2f6khvlabdazq/tests/overview
No tests were run:

Here's an example of a build scan with tests.
Maybe ./gradlew test --scan isn't the right command?
Doesn't have to be this PR (but can be this PR), there should be unitTest and connectedTest tasks (WSM example).
Let us know when this PR is ready for re-review.

Maybe ./gradlew test --scan isn't the right command?

Hmm, it seems to work ok for me: https://scans.gradle.com/s/z4xdz35mrveeu/tests/overview
I did notice yours is still running with Gradle 7.3.3, so maybe a clean/rebuild could fix it?

Let us know when this PR is ready for re-review.

And will do! Thanks for the comments all.

version endpoint has some nulls, is that expected?

For now yes, as those fields are populated by the release tags on GitHub (which don't exist).

Thank you all for the reviews! :)


idk this issue

File "C:\Users\deadly\AppData\Local\Programs\Python\Python311\Lib\shutil.py", line 622, in _rmtree_unsafe
onerror(os.unlink, fullname, sys.exc_info())
File "C:\Users\deadly\AppData\Local\Programs\Python\Python311\Lib\shutil.py", line 620, in _rmtree_unsafe
os.unlink(fullname)
PermissionError: [WinError 5] Access is denied: 'C:\Users\deadly\AppData\Local\Programs\Python\Python311\Lib\site-packages\~-l\_imaging.cp311-win_amd64.pyd'
WARNING: Ignoring invalid distribution ~ (C:\Users\deadly\AppData\Local\Programs\Python\Python311\Lib\site-packages)
WARNING: Ignoring invalid distribution ~ (C:\Users\deadly\AppData\Local\Programs\Python\Python311\Lib\site-packages)

that's not important and can be ignored. It doesn't affect the install


Peers is not displayed

I have problem creating peer. Peers is not displayed.
I reproduced (Windows OS) in prod repo

I found problem about creation peer in masterbazaar. Peer is long create and there is no reaction

Created several peers. Did not face with this problem. Need to observe, moving to  "in Master Test"

Created peers, all peers were displayed on CC.
Registered,unregistered them.

All the peers created while testings were displayed in cc.
Issue fixed in prod


Detecting breaking type changes against "frozen" queries

Hm, that's a terrible issue title.  Naming things is hard.
Background
We're starting to roll out GraphQL to our native apps.  It's great.  In order to save a few bytes over the wire and protect ourselves from malicious stuff, we went with a "persisted queries" implementation where we stick the actual queries in a DB at build time and just send an identifier to said query over the wire.  This also enables regression testing: we have access to all the queries old apps are making in one place; we can test against the current schema (especially in CI) and see when stuff breaks.  We love this because it lets us move fast and make changes to our schema, and breaking changes get caught by tests before things make it to production.
Quandary
We're basically doing DocumentValidator::validate on all the old queries against the current schema.  This works great for detecting most breaking changes - remove a field that an old app is using, it gets flagged.  Unfortunately it can't check type breakages.  Change an int to a string and it will still validate, but the apps aren't going to have a good time.
This is kind of similar to https://github.com/webonyx/graphql-php/issues/64 but narrower in scope.  We tend not to care about people making breaking changes to the schema - unless it actually breaks a deployed query.
I've looked at the available Utils and I could piece something together with TypeInfo (I'd also need to start capturing type info at app build time and sticking that in DB too).  This seems like it might be something that's of broader interest though - so I'm tossing in an issue to see if anyone else has done something like this before, and/or if there is appetite for baking this into an upstream Util.  Thanks.

Nice approach!
I think you should consider porting findBreakingChanges (as you mentioned the task is similar). One thing we can consider is to add information about type and field to breaking change result.
Then you could take these breaking changes and additionally check them against your deployed queries using Visitor.
It is much easier to maintain stuff that already exists in the reference implementation. But that's just my thoughts on this subject. Maybe there are other ideas?

I think you're right - looking at the js implementation, it's simply a facade for comparing two TypeMaps.  Then the trick is just filtering oldSchema down to the types touched by deployed queries before running the comparison - Visitor would work for that part nicely.

@roippi Any follow-up here or should I close?

We're going to do findBreakingChanges in the nearish future then revisit this.  Seems like the right approach.

I guess we can close this one as well, but let me know if you have anything else in mind regarding this issue.


Various changes

Stronger gitignore file
Cleaned up workspace junk
Travis CI Capacity, this mod, if desired, can now be tested online using Travis CI.

Going to revamp this a bit, and let reformatting be handled by Knight.

Same as in the Gravel Ores PR, after thinking it over I don't believe this mod is big enough to benefit from Travis as its so small it rarely needs commits or builds.
Since the rest is just workspace cleanup, I'll handle that stuff myself in a large commit.


StreamBlock use_json_field=True Migration failure while using custom blocks

Issue Summary
First asked about this in #8989 but it seems like this is a separate issue so creating this new one.
Working to update an older Wagtail installation (originally built around ~v1), and going through all of the updates without trouble, when we got to 3.x that required the use_json_field migration for StreamFields. The migrations try to load a custom Block from wagtail.blocks rather than from the internal library it should be loaded from. We have tried the 3.x branch, and now are up to 4.2.4 trying to build and run these migrations, but the generated migrations fail every time (the error is AttributeError: module 'wagtail.blocks' has no attribute 'CollectionChooserBlock'.
The Page model in question has a StreamField defined by:
    body_content = StreamField(
        [
            ("heading", blocks.CharBlock(form_classname="full title", icon="title")),
            ("paragraph", blocks.RichTextBlock()),
            ("image", ImageChooserBlock(icon="image")),
            ("collection", CollectionBlock()),
        ],
        null=True,
        blank=True,
        use_json_field=True,
    )

The CollectionBlock included is based on an expanded StructBlock that includes a custom ChooserBlock:
class CollectionChooserBlock(blocks.ChooserBlock):
    target_model = Collection
    widget = forms.Select

    # Return the key value for the select field
    def value_for_form(self, value):
        if isinstance(value, self.target_model):
            return value.pk
        else:
            return value

class CollectionBlock(blocks.StructBlock):
    collection = CollectionChooserBlock(
        required=True, help_text="Choose Collection to display"
    )

    class Meta:
        template = "home/blocks/collection_block.html"
        icon = "edit"
        label = "Display Collection"

    def get_context(self, value, parent_context=None):
        context = super().get_context(value, parent_context=parent_context)

        try:
            context["documents"] = (
                get_document_model()
                .objects.filter(collection__name=value["collection"])
                .order_by("title")
            )
        except Exception as e:
            pass

        return context

In turn, the generated migration includes an AlterField as follows:
        migrations.AlterField(
            model_name="contentpage",
            name="body_content",
            field=wagtail.fields.StreamField(
                [
                    (
                        "heading",
                        wagtail.blocks.CharBlock(
                            form_classname="full title", icon="title"
                        ),
                    ),
                    ("paragraph", wagtail.blocks.RichTextBlock()),
                    ("image", wagtail.images.blocks.ImageChooserBlock(icon="image")),
                    (
                        "collection",
                        wagtail.blocks.StructBlock(
                            [
                                (
                                    "collection",
                                    accountability.home.models.blocks.CollectionChooserBlock(
                                        help_text="Choose Collection to display",
                                        required=True,
                                    ),
                                )
                            ]
                        ),
                    ),
                ],
                blank=True,
                null=True,
                use_json_field=True,
            ),
        ),

Except when the new migration is run, the AlterField generates an error like this:
AttributeError: module 'wagtail.blocks' has no attribute 'CollectionChooserBlock'

For some reason the migration is thinking that the CollectionChooserBlock should be coming from wagtail.blocks rather than on the path as defined.
Steps to Reproduce
Building the models/blocks as defined above and generating the migrations to set use_json_field=True
In general, I expected that the migration would migrate the StreamField/StructBlock to the new JsonField.
Technical details

Python version: Python 3.9.16
Django version: Django 3.2.20
Wagtail version: Wagtail 4.2.4
Browser version: You can use Edge 115 (not applicable though)

Having not been able to find a solution for this in the last month, I'm thinking the older sites may need to be recreated from scratch - or at least these elements. Are custom StructBlock/ChooserBlocks still valid for inclusion in a StreamField?

I have the exact same issue, and recreating the page does not help. wagtail 6.0.0

Curiosly, what worked, was editing the migration file and importing my custom block directly.


New Package Request: net-fs/samba-4.12.9-r1

Package name and purpose
Hi, net-fs/samba is already present on Flatcar with the version: 4.11.13-r1 (ebuild). The goal of this issue is to track its update to the latest stable version on Gentoo: 4.12.9-r1.
for Flatcar:

Gentoo ebuild

Impact of adding this package to the Flatcar OS image

The package improves on the following core values:

[x] Secure by default
[x] Always up to date
[ ] Improve container experience
[ ] Operate at scale / automation / telemetry

The package will increase the image size by: TBD MBytes.

I identified three new dependencies for this package:

dev-perl/Parse-Yapp
dev-libs/icu
sys-libs/liburing

This missing dependencies have been added to my fork of portage-stable. PR will come in time with the samba one.

Good work with the missing dependencies! It's a good idea to bundle everything into a single PR.

Thanks for the work.
Samba 4.12.9 is included in Alpha 2783.0.0, and will be available also in other channels.
One remaining issue is that the new dependency libs like icu take some more space in production images.
I am trying to figure out how we can minimize the deps.
Will soon create a new issue about that.


Add support for PBKDF2 private key encryption

#377

I've never encountered anything else. Even pbkdf is not really used, not sure why they are generating these keys.

b.t.w iOS CI is failed

std::variant is not supported until iOS 12 :/


package.json bin has a wrong entry for gherkin-utils

👓 What did you see?
When installing the Gherkin-utils package with Yarn 3.1.1 we get the following error:
1>    Ô×ñ YN0001 : Ôöé error : Invalid filename: "@cucumber/gherkin-utils"
1>        at kr (.yarn\releases\yarn-berry.cjs:312:6878)
1>        at o (.yarn\releases\yarn-berry.cjs:695:5923)
1>        at o (.yarn\releases\yarn-berry.cjs:695:6083)
1>        at o (.yarn\releases\yarn-berry.cjs:695:6083)
1>        at o (.yarn\releases\yarn-berry.cjs:695:6083)
1>        at H6e (.yarn\releases\yarn-berry.cjs:695:6164)
1>        at async T6e (.yarn\releases\yarn-berry.cjs:695:10478)
1>        at async yce.finalizeInstall (.yarn\releases\yarn-berry.cjs:680:26254)
1>        at async Ke.linkEverything (.yarn\releases\yarn-berry.cjs:441:14966)
1>        at async .yarn\releases\yarn-berry.cjs:444:4329
We found other reports of these kind of issues for example: #https://github.com/ngneat/until-destroy/issues/108
So we tried and tested:
changing in the package.json
"bin": {
    "@cucumber/gherkin-utils": "bin/gherkin-utils"
  },

into
"bin": "bin/gherkin-utils",

solves the issue.

I apologize if this question is too basic... but which package.json do you mean? Something that needs to be fixed in cucumber? Or in each person's project?
I am having this error in my project but I don't have anything about bin in my package.json.  I tried just adding "bin": "bin/gherkin-utils", just in case, but the error is not solved.
I would happily keep using yarn1, but when you run yarn install with a new version of yarn it insists in auto updating the project.


Enable user-select on websocket and other realtime message logs

Is your feature request related to a problem? Please describe.
It's very often for someone to select and/or copy the log of some websocket communication for debug purposes, so it should be user-select = text or something similar.
Describe the solution you'd like
Make websocket communication log user-select-able
Describe alternatives you've considered
Directly copy stuff out of developer tool (F12 menu)
Additional context
None

@01010101lzy thank you for opening the issue, I will look into this ^_^

So fast! Thanks!


Move webhooks onto new sharedmain methods

Related to knative/pkg#1007, migrates webhook processes onto new WebhookMain methods in the sharedmain package that will retain the existing behavior for now while we decide how to scale webhooks horizontally.

Proposed Changes

Move webhook main onto WebhookMain methods from knative/pkg#1084

Release Note

NONE

/lgtm
/approve

/lgtm
/approve


Change handling of copy=None defaults for Pandas 2

In Pandas 1, the copy arg always had a default of True, while in Pandas 2 the new copy-on-write mechanism means that copy defaults to None, which indicates "use the global copy_on_write setting". For Beam, copy-on-write should always be true, so just fill in the None defaults with True.

R: @tvalentyn

Are some tests failing on Pandas2 if we don't set it copy=True?
I think I understand the idea of preserving the behavior but also concerned since this will be a difference in defaults b/w Beam and Pandas.
Also, we could call this out in https://beam.apache.org/documentation/dsls/dataframes/differences-from-pandas/ .

So the default in 2 changes to None, and None isnt valid so things break.
I can make it so that populate defaults uses the copy_on_write for that
setting like Pandas uses instead of just true? That is more in line as the
same API.
On Tue, Sep 19, 2023, 6:56 PM tvalentyn @.***> wrote:

Are some tests failing on Pandas2 if we don't set it copy=True?
I think I understand the idea of preserving the behavior but also
concerned since this will be a difference in defaults b/w Beam and Pandas.
Also, we could call this out in
https://beam.apache.org/documentation/dsls/dataframes/differences-from-pandas/
.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/28523#issuecomment-1726648829, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABG4SHYCRPVXBGYR7OODLM3X3IPJRANCNFSM6AAAAAA46AGAKE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Are some tests failing on Pandas2 if we don't set it copy=True?
I think I understand the idea of preserving the behavior but also concerned since this will be a difference in defaults b/w Beam and Pandas.
Also, we could call this out in https://beam.apache.org/documentation/dsls/dataframes/differences-from-pandas/ .

Looking at it again, we don't support copy=False anywhere in Beam. Because it requires memory sharing semantics we can't support.  I don't know if that's worth calling out now because it is no different than ever before.  If you ever specify copy=False currently it will either raise an error or ignore it and copy anyway depending on the function.
Therefore the current PR behavior of setting the default to True makes sense because False never will. It is just before we relied on the default in pandas being True where it is now None.

SGTM, thanks, is this ready to merge or you plan any other changes?

SGTM, thanks, is this ready to merge or you plan any other changes?

Ready to merge


PD: Audit production assets

Review file sizes of assets, sanity check those files

More suggestions for asset cleanup in #3183 comments

Also addressed in #3196

@mcous is this closed now or is there anything else left to do?

As discussed in RL, updated title and description with acceptance criteria


Deletes self-referencing spans in conversion javascript

See #1744

with this change, the javascript doesn't crash anymore.. even if the actual data from #1744 is quite wrong due to 3 spans having constant ids


Migrating from pinia-plugin-persistedstate-2

Describe the bug
I'm currently migrating my app from pinia-plugin-persistedstate-2 to this version since it is no longer maintained. I use it inside of an Electron app and have ipc functions mapped to store methods:
async function getStore(key) {
  return await ipcRenderer.invoke("getStore", key);
}

async function setStore(key, value) {
  return await ipcRenderer.invoke("setStore", key, value);
}

async function deleteStore(key) {
  return await ipcRenderer.invoke("deleteStore", key);
}

(async () => {
  const app = createApp(App);
  const pinia = createPinia();

  pinia.use(
    createPersistedState({
      storage: {
        getItem: async (key) => {
          return getStore(key);
        },
        setItem: async (key, value) => {
          return setStore(key, value);
        },
        removeItem: async (key) => {
          return deleteStore(key);
        },
      },
    }),
  );

and it complains that
  Type 'Promise<any>' is not assignable to type 'string'.ts(2322)

Is that what is mentioned on https://prazdevs.github.io/pinia-plugin-persistedstate/guide/limitations.html?
Reproduction
import { ipcRenderer } from "electron"; import FloatingVue from "floating-vue"; import { createPinia } from "pinia"; import { createPersistedState } from "pinia-plugin-persistedstate"; import { createApp } from "vue"; import App from "./App.vue"; import { i18n } from "./libs/i18n"; import "virtual:uno.css";  async function getStore(key) {   return await ipcRenderer.invoke("getStore", key); }  async function setStore(key, value) {   return await ipcRenderer.invoke("setStore", key, value); }  async function deleteStore(key) {   return await ipcRenderer.invoke("deleteStore", key); }  (async () => {   const app = createApp(App);   const pinia = createPinia();    pinia.use(     createPersistedState({       storage: {         getItem: async (key) => {           return getStore(key);         },         setItem: async (key, value) => {           return setStore(key, value);         },         removeItem: async (key) => {           return deleteStore(key);         },       },     }),   );    app.use(pinia);   app.use(i18n);    app.use(FloatingVue, {     themes: {       "info-tooltip": {         $extend: "tooltip",       },     },   });    app.mount("#app").$nextTick(() => {     postMessage({ payload: "removeLoading" }, "*");   }); })();

System Info
"pinia-plugin-persistedstate": "^3.2.1",#    "pinia": "^2.1.7",

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible of the bug.

The plugin only supports synchronous storages to match pinia's mutation system. This is indeed one of the limitation.

The plugin only supports synchronous storages to match pinia's mutation system. This is indeed one of the limitation.

Can you suggest a migration path for users coming from the abandoned -2 version then?

Well I didnt make the -2.
This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214).
You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

Well I didnt make the -2.
This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214). You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

Oh yeah, I'm aware, I was just wondering if you have a suggestion for a replacement path, I'll look at actions but that looked like I have to have those defined for every store instead of globally, thanks!

Well I didnt make the -2.
This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214). You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

Oh yeah, I'm aware, I was just wondering if you have a suggestion for a replacement path, I'll look at actions but that looked like I have to have those defined for every store instead of globally, thanks!

Would be cool if you could do something like this:
pinia.use(
    createPersistedState({
      actions: {
        getItem: async (key) => {
          return getStore(key);
        },
        setItem: async (key, value) => {
          return setStore(key, value);
        },
        removeItem: async (key) => {
          return deleteStore(key);
        },
      },
    }),
  );

Due to the way the plugin behaves and how pinia handles it, synchronozing data from async sources is out of the scope of the plugin. My advice would be to have calls done on app startup then calling stores to update the data. That would be the safest way without risking race conditions having async calls in sync functions.
Closing this 😌


Initial Flow-Enabled Skeleton Commit

@nmn Please have a look and see what I got right/wrong. I am still figuring it all out, but I followed your suggestions and I think it's in the neighborhood of correct. @jgclark @EduardMe Please edit as you see fit.
BTW, I did also include a couple of dot-files, because I thought you wouldn't want to have people thinking they need to commit the generated script.js and also VSCode needs some tweaking so it doesn't complain so much about Flow.
I look forward to your comments/improvements. Thanks @nmn! This is very cool.

BTW, I toyed with the idea of including some helper functions in with the templates (as I think you guys discussed) -- for things we're all using repeatedly, like dateHelpers.js and interpolation.js and messageFunctions.js...would love to hear how you're thinking of dealing with that (and keeping it updated). I know there has been some discussion. :)

I added the .vscode settings because it took me awhile to figure out why
VSCode was yelling at me about Typescript problems (it was trying to read
the Flow), so I figured out how to turn those checks off and I thought I
would include it as a public service, but I will delete it if you think it
streamlines things.
And I will get rid of that script. Good to know it's unnecessary.
Thanks @nmn!
On Mon, Jun 14, 2021 at 9:20 PM, Naman Goel @.***>
wrote:

@.**** commented on this pull request.
This looks right. Except you accidentally added your .vscode settings.
In .vscode/settings.json
https://github.com/NotePlan/plugins/pull/17#discussion_r651434771:

+{

"typescript.validate.enable": false,
"typescript.suggest.includeAutomaticOptionalChainCompletions": false,
"javascript.validate.enable": false
+}

Can you remove this from your commit? Perhaps add this file to .gitignore
as well.
In np.plugin-flow-skeleton/rollup.config.js
https://github.com/NotePlan/plugins/pull/17#discussion_r651435526:

@@ -0,0 +1,25 @@
+// DO NOT EDIT THIS FILE. IT'S FOR THE SCRIPT PACKAGER!

You no longer need this file if you just use nom run autowatch that one
command automatically does the compiling for you.
But feel free to keep it if you think it adds value. I feel like letting
one script handles everything automatically is simpler to get started with
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NotePlan/plugins/pull/17#pullrequestreview-683541484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEI6VGCWZMGVOFBHBASM63TS3IHPANCNFSM46WHDHMQ
.

Also added UI change to the rollup script. @nmn pls make sure you're comfortable with it.

@nmn just bumping this

Looks good to me.

Yup looks good!

Thanks guys. Very cool stuff @nmn. @jgclark u will release it?
On Mon, Jun 21 2021 at 10:30 AM, Naman Goel @.***>
wrote:

Yup looks good!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NotePlan/plugins/pull/17#issuecomment-865216573, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACEI6VGWNQCGTIE2LAJSRSDTT5ZKLANCNFSM46WHDHMQ
.

If I understand correctly, this doesn't need a release, as its not a plugin. It simply needs to be committed to main. Unfortunately I can't do that from iPad client, as its telling me (rightly or wrongly) that it cannot automatically be merged. Perhaps @nmn could do so instead?

@jgclark I used your .gitignore so there are no merge conflicts. Pls merge this and let's close this PR.
Thanks!

@jgclark @nmn Can you guys pls merge this into main so that I can at least close one of my PRs?
It has been approved by @nmn and has no merge conflicts. Thank you.


Clean procedure

After 1000's of render requests there must be a lot of abandoned tex and pdf files still stored. Is there an easy way to clean them up? This is important especially for the docker.

The renderer will cleanup the temporary folder, see
https://github.com/vsfexperts/LaTeX/blob/544b824d3ab0b121cd8c54b34a953f28a9bdc082/latex-renderer/src/main/java/de/vsfexperts/latex/renderer/LatexRenderJob.java#L36-L46
The archived output (tex, pdf)) is stored in the archive directory/volume. The size of this folder will increase unless you're deleting the archived output periodically. You could use some bind mount and clean the folder via some external script periodically. The render output is immutable, so it makes sense to keep it on the filesystem, so that clients just have to store the uuid in order to identify/retrieve it. The tex file is just in there for debugging purposes (e.g. if the pdf is showing some unexpected layout issues due to unexpected input data).


is executing lua script considered as a blocking use case to use connection pooling?

From the docs, it is saying that for operations like BLPOP or transaction cases, we should not share the connection with multiple threads, otherwise there would be some side effect. I am wondering what are the side effects? And is executing lua script also a use case to use connection pooling?

Lua on its own isn't really blocking. However, it depends on what the Lua script is calling, and whether you're using blocking calls within the Lua script.


React?

While LittleLink has provided a simple to use web site, the way in which it is customized is limited.  I feel like moving to react give us more flexibility and we aren't bound to the original implementation of just static HTML and CSS.

server side rendering + client side rendering
easier to test
not limited to shell scripts
css can be broken up
more control over meta tags and elements
easier to contribute to?
more flexibility on env variables

while making the choice of using a nodejs server has served us well (pun intended) adding react on top of this will give us more tools and a more modern dev stack.

Also, I want to be sure that the API going forward is non breaking.  This means that env variables now will continue to have the same contract and types they did before.  Also, react js just becomes and implementation detail, something that no one using this container needs to know unless they are curious.


Feature: Option to add commit count to baseCode

It would be nice if we could have a function that could add on the number of commits to the baseCode as a way of auto incrementing the versions.
Something like:
ext.commitCount = { ->
    def repo
    def count = 0
    try {
        repo = new FileRepositoryBuilder()
                .readEnvironment()
                .findGitDir(project.projectDir)
                .build()
    } catch (IllegalArgumentException ignore) {
        // No repo found
        return count
    }

    def git = Git.wrap(repo)
    def commits = git.log().call()
    return commits.size()
}

combine this with MMNNPPXX and it will enable constant updates.

You can already do MMNNPPBB to get two digits for the number of commits since the last tag. Does that work?

My bad. I didn't notice that in the readme. I'll try that.

Cool, good luck!


Retry mechanism

Opening for discussion - I believe vault is critical enough infrastructure that clients should have a retry mechanism out of the box.
Relates to https://github.com/spring-projects/spring-vault/issues/504
and
https://github.com/spring-cloud/spring-cloud-vault/issues/236
Due to the similarities (both bootstrap property sources), default retry properties were set to match spring cloud config's defaults (https://cloud.spring.io/spring-cloud-config/multi/multi__spring_cloud_config_client.html#config-client-retry)
I have not added tests - I can/will do so once a maintainer indicates this PR on the right track and has potential to be merged.
Thank you

@pmv Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Adding retry support here seems fine. However, we should not make use of aspect-oriented programming features. Instead, using RetryTemplate directly is much more efficient. Actually, the ideal variant would be a Retry-enabled ClientHttpRequestFactory.

Adding retry support here seems fine. However, we should not make use of aspect-oriented programming features.

Originally I did not until I saw this: https://github.com/spring-cloud/spring-cloud-config/blob/master/spring-cloud-config-client/src/main/java/org/springframework/cloud/config/client/ConfigServiceBootstrapConfiguration.java#L62-L78, and then I modeled my changes after those.  However, I am not set on that particular implementation.

Actually, the ideal variant would be a Retry-enabled ClientHttpRequestFactory.

Pushing an update to that effect.

Let me know if there's any more legwork you'd like me to do for this one - thanks

Let me know if you have any more feedback - I believe suggestions up to this point have been addressed.

Thanks. I want to have a look at this in the upcoming days.

Hi, are there any timelines when retry will be supported? Is there a workaround example how to setup retry for spring-cloud-vault.3.0.3

Right now, we don't have bandwidth to follow up timely.

@mp911de  - It will be great if this can be reviewed and supported for a subsequent release as it could save us from implementing custom retry solutions within every vault client app. Thanks!

Iam agree, it will be be nice if this feature is implemented, the usage of vault for database access is very critical.
Thank you.

Hi guys:
Are you planing to merge this branch? The future seems to be great!
Thanks

Hi
When you plan to merge this ?


Fix broken link in readme.md

Link to docs page for NserviceBus.Testing
Would we prefer updating the link to point to the sample as it was before? This is the updated link for that page:
https://docs.particular.net/samples/unit-testing/

thanks


mountvol X: /s The parameter is incorrect.

The description how to disable Device Guard / System Guard may not be sufficient and doesn't offer ways to detect the state of the system in thet respect.
mountvol X: /s
comes with error"
The parameter is incorrect.
[Enter feedback here]

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

ID: 41c2cb44-269d-3334-019a-726eb5432f1c
Version Independent ID: 251024cc-b818-18c6-a112-4ac0276cb4b1
Content: Manage Windows Defender Credential Guard (Windows 10) - Microsoft 365 Security
Content Source: windows/security/identity-protection/credential-guard/credential-guard-manage.md
Product: w10
Technology: windows
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Please see all the closed issues here in this repository. This "issue" has been discussed for at least 2 years now and the parameter works if you are using the right kind of hardware.
Repository issue search for mountvol X: /s: https://github.com/MicrosoftDocs/windows-itpro-docs/search?q="mountvol+X%3A+%2Fs"&type=Issues

Disabling Windows Defender Credential Guard is not working with Windows 10 1803 #5190 by ealfan was closed on Oct 23 2019
none of this worked - I still am unable to run my virtual machine #4952 by OhiosBatman was closed on Sep 23 2019
Instructions regarding Windows Defender Credential Guard EFI variables do not work #4221 by foxbunny was closed on Jun 23 2019
variable is incorrect #4084 by lengthmin was closed on Jul 24 2019
Command line instructions are incorrect #3234 by RichardRanft was closed on Sep 6 2019
Neither the steps worked and nor the tool worked :-( #3108 by sachinmar was closed on Apr 8 2019
maybe an extra step is mentioned in the doc? #2663 by sasanmcp was closed on Feb 20 2019
Windows Sandbox Enables Windows Defender Credential Guard #2612 by hadeernd was closed on May 7 2019
Instructions for disabling not working... #2569 by darnocian was closed on May 9 2019
Credential guard enabled but not running... #2327 by haseeb1986 was closed on Apr 16 2019
[SOLVED] ERROR!! "The device is not valid as specified" ! #2216 by ahmedbr was closed on Jun 3 2019
**Can't disable Credential Guard #2141 by tomneko was closed on Feb 28 2019
Terminated Credential Guard #1984 by jkd2020-github was closed on Jun 9 2019
DOES NOTHING #1924 by cacodemon9000 was closed on Aug 14 2019
-SOLVED- It doesn't work for me #1915 by 2IRG-FB was closed on Jun 9 2019
Missing parts for VMWARE and HAXM users #1862 by Vahhab was closed on Oct 16, 2018
The parameter is incorrect. #1776 by damian123 was closed on Jun 23 2019
bcdedit missing DISABLE-VBS identity protection security #1623 by mgeatz was closed on Sep 12, 2018
(Solved) Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT) #1556 by DuggerConsulting was closed on Jun 23 2019
Credential Guard via Intune #1400 by tmguinn was closed on Apr 11 2019

@RAJU2529 : Would you like to point @martinvana to some part of the documentation pointing out what the hardware (and BIOS/UEFI) requirements is for the command to work as expected?

@illfated . First of all I want to know , about his laptop or desktop configuration with processor , installed device driver.  Windows 10 os version and edition . Then his entered commands,  and settings he applied

Thanks for the pointers. I guess @illfated directed me to a plenty of bedtime reading ;-)
The system info is:
Dell Inc. Precision T3610
Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
Windows 10 Enterprise 2016 LTSB 64-bit (10.0, Build 14393) (14393.rs1_release.200504-1524)
BIOS Mode is "Legacy" (not UEFI)
The failing command is:
The parameter is incorrect. ```

Dell Inc. Precision T3610
Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
Windows 10 Enterprise 2016 LTSB 64-bit (10.0, Build 14393) (14393.rs1_release.200504-1524)
BIOS Mode is "Legacy" (not UEFI)

I could be mistaken, but I think you need UEFI for virtualization to be able to use the /s parameter (in addition to Hyper-V).
Windows Server 2016 Standard (production) on my workplace, where I am able to run the command with the /s parameter, uses UEFI mode and Hyper-V, so I would assume those are part of the requirements.

@martinvana . You need UEFI mode and windows 10 1803 and later version with professional or enterprise.

Just to add the Windows Server version information from my workplace server, it is as follows:

Windows Server 2016 (Standard) Version 1607 (OS Build 14393.3686)

Thanks to @illfated and @RAJU2529 for the help confirming that the issue is based on the UEFI mode and not related to Windows vintage (as we both run Version 1607).
I can enable Hyper-V and run Docker, disable (reboot) and run VMW but I cannot have Hyper-V enabled and disable Device Guard / System Guard (at least following the procedure using "mountvol X: /s") what is apparently required for latest VMW 15.5.5 which now "should" be able to coexist with Hyper-V for the first time. But that is a different topic. Thanks for the help!


I tried but without success look what I did:

          I tried but without success look what I did:

Class: public sealed class FarmerNameManager : MonoBehaviour, IUserBlobCallbacks2, IUserBlobCallbacksBase
Method: public void CreateFarmerName(string farmerName) { }
#if !BNM_DISABLE_NEW_CLASSES
using namespace BNM::Structures::Mono;
using namespace BNM::Operators;

BNM::LoadClass FarmerNameManagerClass{};
BNM::Method<monoString*> CreateFarmerNameMethod{};

void (*old_CreateFarmerNameA)(BNM::UnityEngine::Object*, monoString*);
void NewCreateFarmerName(BNM::UnityEngine::Object* instance, monoString* originalName) {
    monoString* newNameA = BNM::CreateMonoString("BILL GATES");
    old_CreateFarmerNameA(instance, newNameA);
}

void OnLoaded() {
    using namespace BNM;
    FarmerNameManagerClass = LoadClass(OBFUSCATE_BNM("Assembly-CSharp"), OBFUSCATE_BNM("FarmerNameManager"));
    CreateFarmerNameMethod = FarmerNameManagerClass.GetMethodByName(OBFUSCATE_BNM("CreateFarmerName"), 1);

    InvokeHook(CreateFarmerNameMethod, NewCreateFarmerName, old_CreateFarmerNameA);
}
#endif

 case 14: {
      BNM::AddOnLoadedEvent(OnLoaded);
            break;
        }

Originally posted by @evilmu in https://github.com/ByNameModding/BNM-Android/issues/16#issuecomment-1871620203

There could be many different reasons as to why this isn't working. First of all, did you try other ways to hook the monoString you're trying to mod? I am also seeing CreateFarmerNameMethod method as monoString* but then you're trying to hook it as void.
Try this maybe:
BNM::LoadClass FarmerNameManagerClass{};

// assuming that the function you're trying to hook is a void
// if it is then it will only be called once the method CreateFarmerName is called since you did not use an update method here
void (*old_CreateFarmerNameA)(BNM::UnityEngine::Object*, monoString*);
void NewCreateFarmerName(BNM::UnityEngine::Object* instance, monoString* originalName) {
	// check if instance is not nullptr to avoid crashes(and since you're not hooking a static method):
	if(instance){
    monoString* newNameA = BNM::CreateMonoString("BILL GATES");
    old_CreateFarmerNameA(instance, newNameA);
	}
}

// if the function is a monoString* but you messed up and put it as void then your hook should look like this:
monoString* (*old_CreateFarmerNameA)(BNM::UnityEngine::Object*, monoString*);
monoString* NewCreateFarmerName(BNM::UnityEngine::Object* instance, monoString* originalName) {
	// check if instance is not nullptr to avoid crashes(and since you're not hooking a static method):
	if(instance/*add toggle here if you want to controll it*/){
   // monoString* newNameA = BNM::CreateMonoString("BILL GATES");
   return newNameA;
	}
}

void OnLoaded() {
    using namespace BNM;
    FarmerNameManagerClass = LoadClass(OBFUSCATE_BNM("Assembly-CSharp"), OBFUSCATE_BNM("FarmerNameManager"));

	// same thing:
	    HOOK(FarmerNameManagerClass.GetMethodByName(OBFUSCATE_BNM("CreateFarmerName"), 1), NewCreateFarmerName, old_CreateFarmerNameA);

}

Pode haver muitos motivos diferentes pelos quais isso não está funcionando. Primeiro de tudo, você tentou outras maneiras de conectar o método void que está tentando modificar? CreateFarmerNameMethod é um método void, mas você está tentando fazer BNM::Method<monoString*> CreateFarmerNameMethod{};
Tente isso talvez:
BNM::LoadClass FarmerNameManagerClass{};

// assuming that the function you're trying to hook is a void
// if it is then it will only be called once the method CreateFarmerName is called since you did not use an update method
void (*old_CreateFarmerNameA)(BNM::UnityEngine::Object*, monoString*);
void NewCreateFarmerName(BNM::UnityEngine::Object* instance, monoString* originalName) {
	// check if instance is not nullptr to avoid crashes(and since you're not hooking a static method):
	if(instance){
    monoString* newNameA = BNM::CreateMonoString("BILL GATES");
    old_CreateFarmerNameA(instance, newNameA);
	}
}

void OnLoaded() {
    using namespace BNM;
    FarmerNameManagerClass = LoadClass(OBFUSCATE_BNM("Assembly-CSharp"), OBFUSCATE_BNM("FarmerNameManager"));

	// same thing:
	    HOOK(FarmerNameManagerClass.GetMethodByName(OBFUSCATE_BNM("CreateFarmerName"), 1), NewCreateFarmerName, old_CreateFarmerNameA);

}

Hello Creator1A,
I hope everything is well. I've read your comment, and I'm glad you responded. Could you lend me a hand with this? I haven't been able to fully resolve it yet.
If you can assist me, here is my WhatsApp: +55 43 96518270.
Thank you in advance for your help!
Best regards,
Evilmu

Issue solved and was unrelated to BNM.
Issue was with the hooking code rather than anything related to BNM._


Add upper bound to prevent usage of NumPy 2

NumPy 2 is expected to be released in the near future. For the RAPIDS 24.04 release, we will pin to numpy>=1.23,<2.0a0. This PR adds an upper bound to affected RAPIDS repositories.
xref: https://github.com/rapidsai/build-planning/issues/29

Thanks Bradley! 🙏
Could we add this to wheels too? Looks like it is Conda only atm

Wheels added in d7d067e.

Looks good. Thanks Bradley! 🙏

/merge


feature: swap DB type via env

Slack.
Overview
RocksDB is implemented, but not tested "in the wild".
Changes

Pull the DB type from ENV.

Testing
Hey, If it works, it works.

Coverage decreased (-3.03%) to 78.678% when pulling b8bf998c4bfaebb4fb2a372c26911a168eba18bd on dev_rocksdb into 9a565a368fb3fbeccf260a8960b8ffd24dd68306 on master.


Loading a source code from the Keyboard chip

The Keyboard chip is the only input device equipped in the original Hack computer.
We can use it in order to input arbitrary Brainfuck source code to the interpreter.
However, nobody like to input all characters in the Brainfuck source code via actual keyboard.
It's difficult to input a Brainfuck source code without typos.
Using xdotool may be able to solve this issue and automate that task.

xdotool doesn't work as we expected.
xdotool search --class VMEmulatorMain windowactivate
xdotool type hi

windowactivate fails:
XGetWindowProperty[_NET_WM_DESKTOP] failed (code=1)

Now we are considering to generate a test script (*.tst) which emulates keystrokes in order to load arbitrary source code.

Confirmed that the following test script works well:
//  Load the program.
load Brainfuck,

// Load the Brainfuck program ".+[.+]" which prints characters on the screen.

// First, input the lenght of the Brainfuck program.
set RAM[24576] 54, repeat 100 { vmstep, }  // "6"
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 128, repeat 100 { vmstep, }
set RAM[24576] 0, repeat 100 { vmstep, }

// Then, input ".+[.+]".
set RAM[24576] 46, repeat 100 { vmstep, }  // "."
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 43, repeat 100 { vmstep, }  // "+"
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 91, repeat 100 { vmstep, }  // "["
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 46, repeat 100 { vmstep, }  // "."
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 43, repeat 100 { vmstep, }  // "+"
set RAM[24576] 0, repeat 100 { vmstep, }
set RAM[24576] 93, repeat 100 { vmstep, }  // "]"
set RAM[24576] 0, repeat 100 { vmstep, }

repeat 100000000 {
  vmstep;
}

Using a custom Keyboared class implementation is needed in order to avoid blocking in the following function calls:

Keyboard.readChar
Keyboard.readInt

The functions of the built-in Keyboard class blocks the VMEmulator.  It seems that a call VM command for these functions is processed as a single step.

We tried to load a Brainfuck program by using unused memory area, but it failed unfortunately:
// Load the Brainfuck interpreter.
load Brainfuck,

// Place a String object containing a Brainfuck program to execute at 0x7000.
// In this example, we use the built-in String class.
set RAM[28672] 6,      // String.capacity
set RAM[28673] 28928,  // String.buffer points to 0x7100
set RAM[28674] 6,      // String.length

// Write ".+[.+]" from 0x7100.
set RAM[28928] 46,
set RAM[28929] 43,
set RAM[28930] 91,
set RAM[28931] 46,
set RAM[28932] 43,
set RAM[28933] 93,

// Run the Brainfuck program.
repeat 100000000 {
  vmstep;
}

Found that xdotool search --class VMEmulatorMain doesn't return a correct target window.
xwininfo shows a different window id.
We successfully load a Brainfuck program with the following command at least on my environment:
xdotool windowactivate --sync <window-id> key --delay=200 6 Return
xdotool windowactivate --sync <window-id> type --delay=200 '.+[.+]'

Sending events directly to the target window by using --window doesn't work as we expected.


Support MSVC new preprocessor

Macros are defined in a non standard way.
https://devblogs.microsoft.com/cppblog/msvc-preprocessor-progress-towards-conformance
Fixed versions
#define VA_STRINGIZE(...) DETAIL_VA_STRINGIZE(__VA_ARGS__)
#define DETAILVA_STRINGIZE(...) #__VA_ARGS__

#include <winrt/base.h>

#define WINRT_WRAP(...) (__VA_ARGS__)

#define WINRT_ASSERT_DECLARATION(M, R, ...)  Please upgrade to a newer version of C++/WinRT.

We use the version from SDK.
Is it expected to not use it and consume the headers from this repository directly ?

The version in the SDK is quite old. Builds from the repo are published here:
https://www.nuget.org/packages/Microsoft.Windows.CppWinRT/
If you use Visual Studio, you can simply add a NuGet package reference. This will replace the SDK headers in your include path. Otherwise, you can unzip the NuGet and run cppwinrt.exe to generate headers directly.

I added the nuget but I don't see any header.


Rebuild skl2onnx 1.13 for py311

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8d_u9j1yhy/clone/recipe/meta.yaml:17: pip_install_args: pip install should be run with --no-deps and --no-build-isolation.
WARNING: /tmp/abs_8d_u9j1yhy/clone/recipe/meta.yaml:33: python_build_tool_in_run: The python build tool packaging is in run depends
Errors were found

package scikit-learn-1.0.2-py310h59830a0_1 requires python >=3.10,<3.11.0a0, but none of the providers can be installed.
The recipe has scikit-learn >=0.19,<=1.1.1 but we have python 3.11 support only for scikit-learn  >=1.2.1


Test suite fixes

Mostly test suite related fixed/patches.
Since threads are completely dysfunctional on this branch, it might be worth dropping support for Threads completely (the only other option is to get Threads to behave exactly like fibers - which is probably not worth the time and maintenance).

One note since I don't have time to do a more in-depth review:
1.9.3 is EOL. We should probably test against 2.0.0 instead.

This is merged into the prerelease branch so we can keep working on it there. Looks exciting. We can review the prerelease as a whole, later.

Thanks! I'll need to rebase now...


Prayer Reminder

Is your feature request related to a problem? Please describe.
people often forget to pray and lose connection with god
Describe the solution you'd like.
creating a simple prayer reminder that sends alerts to users for prayers
Describe alternatives you've considered.
Apps could be an alternative but they take a lot of your storage
Add any other context or screenshots about the feature request here.
No response

please assign me this issue

@samarsajad Thank you for providing your insight but it is not required as of now


Resolve issue #1249

This PR resolves #1249 - NPE when test.sh location is not specified in tg yaml

 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.


Not PSR-0 compliant

JSqueeze claims to be PSR-0 (in its composer.json), but it really isn't:
https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
"A fully-qualified namespace and class must have the following structure \<Vendor Name>\(<Namespace>\)*<Class Name>"
that is, at least one level of namespacing is required, a top-level 'Vendor Name'. JSqueeze is a bare class. I'm now in an argument with my downstream package reviewer because our distribution guidelines don't allow us to put libraries directly in /usr/share/php (to avoid mess and conflicts - nothing else is called JSqueeze yet, but just today I found two things called cssmin, for instance...), but if I put it in a subdirectory, nothing will be able to autoload it without patching.

v2.0.0 just released!

v2.0.0 just released!


Support adding mount to running containers

This PR adds hcsshim support to mount host volumes/directories to running windows containers.
HCS supports mounting host volumes/directories to running windows containers by modifying the hcs compute system with ResourcePath of Containers/MappedDirectories. These changes leverage this by extending the hcsTask.Update() function to process and add mounts for running process isolated and hyperV windows containers.

Can we not rely on (*UtilityVM) Share and add an analogous function to internal/hcs.System? Id rather not bring HCS specifics into cmd

what HCS specifics are you referring to? task_hcs.go is already sending ht.c.Modify() modify requests for updating CPU and memory resources.

cc @kharpMSFT

what HCS specifics are you referring to? task_hcs.go is already sending ht.c.Modify() modify requests for updating CPU and memory resources.

the logic in updateWCOWContainerMount; we already have it implemented in uVM code, and (aside for portions of the update and properties/stats code for hcsTask), most of the HCS schema creation logic is pushed to hcsoci or elsewhere instead of in cmd\containerd-shim-runhcs-v1

what HCS specifics are you referring to? task_hcs.go is already sending ht.c.Modify() modify requests for updating CPU and memory resources.

the logic in updateWCOWContainerMount; we already have it implemented in uVM code, and (aside for portions of the update and properties/stats code for hcsTask), most of the HCS schema creation logic is pushed to hcsoci or elsewhere instead of in cmd\containerd-shim-runhcs-v1

The uvm.Share() function seems to be slightly different. It is sending a request with a different resource path type and is also a common code path and is not adding the share to release resource that is being mounted (not sure why this is ) . I think it would be better to have the mounting logic for running containers exclusive to this add-mount logic file as a non-exportable function if possible.

what HCS specifics are you referring to? task_hcs.go is already sending ht.c.Modify() modify requests for updating CPU and memory resources.

the logic in updateWCOWContainerMount; we already have it implemented in uVM code, and (aside for portions of the update and properties/stats code for hcsTask), most of the HCS schema creation logic is pushed to hcsoci or elsewhere instead of in cmd\containerd-shim-runhcs-v1

The uvm.Share() function seems to be slightly different. It is sending a request with a different resource path type and is also a common code path and is not adding the share to release resource that is being mounted (not sure why this is ) . I think it would be better to have the mounting logic for running containers exclusive to this add-mount logic file as a non-exportable function if possible.

@helsaawy  I refactored the code a little to reuse some part of it from uvm.Share() in the second commit of this PR. But no sure this can entirely move out to internal/* though. Let me know what you think


[DOCS] Create and Edit Tiers

Context
https://github.com/opencollective/opencollective/issues/6092

What's changing?

Why are we changing it?

Who does this change impact?

How do users use it?

Is this change optional or mandatory?

Is this change being released incrementally as a beta? What's the schedule?

When will the project be ready for release/complete?

Docs Process

Overview

Changes to be made

Estimate of effort

We've redesigned the process to create and edit tiers. Tiers can be used to provide perks and rewards to supporters, set membership fees, build funding drives, or simply categorise your contributions. The new experience shows a preview of the tier as it will appear on your Collective's profile:
📘 Read more about tiers and goals
📧 Contact support if something isn't working
🙃 Leave feedback below

I completed this


Network driver operation clean failed

Description
When LXD VM is stopped, VNM driver clean opration failed
To Reproduce
Start LXD VM using Netowork with VN_MAD == bridge, then shutdown VM
Expected behavior
VNM clean operation should success
Details

Affected Component: VNM
Hypervisor: LXD
Version: 5.10

Additional context
Fri Nov 29 09:17:56 2019 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: --- Stopping container ---
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Processing disk 0
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Using raw filesystem mapper for /var/lib/one/datastores/105/77/disk.0
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Unmapping disk at /var/lib/lxd/storage-pools/default/containers/one-77/rootfs
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Umounting disk mapped at /dev/loop4
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Unmapping disk at /var/lib/one/datastores/105/77/mapper/disk.1
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: shutdown: Umounting disk mapped at /dev/loop5
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: shutdown.
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vnm/bridge/clean
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: clean: delete_vlan_dev function not implemented.
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: clean: exit
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: clean: ["/var/tmp/one/vnm/vlan.rb:83:in `exit'", "/var/tmp/one/vnm/vlan.rb:83:in `delete_vlan_dev'", "/var/tmp/one/vnm/vlan.rb:120:in `block in deactivate'", "/var/tmp/one/vnm/vnm_driver.rb:81:in `block in process'", "/var/tmp/one/vnm/vm.rb:64:in `block in each_nic'", "/var/tmp/one/vnm/vm.rb:63:in `each'", "/var/tmp/one/vnm/vm.rb:63:in `each_nic'", "/var/tmp/one/vnm/vnm_driver.rb:84:in `process'", "/var/tmp/one/vnm/vlan.rb:95:in `deactivate'", "/var/tmp/one/vnm/bridge/clean:30:in `<main>'"]
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: ExitCode: 1
Fri Nov 29 09:17:59 2019 [Z0][VMM][I]: Failed to execute network driver operation: clean.
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: Error shutting down VM: bridge: -
Fri Nov 29 09:17:59 2019 [Z0][VM][I]: New LCM state is RUNNING

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

I'm not able to reproduce the issue
Fri Nov 29 16:17:03 2019 [Z0][VM][I]: New state is ACTIVE
Fri Nov 29 16:17:03 2019 [Z0][VM][I]: New LCM state is PROLOG
Fri Nov 29 16:17:05 2019 [Z0][VM][I]: New LCM state is BOOT
Fri Nov 29 16:17:05 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/5/deployment.0
Fri Nov 29 16:17:06 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Fri Nov 29 16:17:07 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 16:17:07 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Processing disk 0
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Using qcow2 mapper for /var/lib/one/datastores/0/5/disk.0
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/lxd/storage-pools/default/containers/one-5/rootfs using device /dev/nbd0
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Mounting /dev/nbd0 at /var/lib/lxd/storage-pools/default/containers/one-5/rootfs
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/one/datastores/0/5/mapper/disk.1 using device /dev/loop0
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop0 at /var/lib/one/datastores/0/5/mapper/disk.1
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: deploy: --- Starting container ---
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 16:17:08 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Fri Nov 29 16:17:09 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 16:17:09 2019 [Z0][VMM][I]: Successfully execute network driver operation: post.
Fri Nov 29 16:17:09 2019 [Z0][VM][I]: New LCM state is RUNNING
Fri Nov 29 16:17:14 2019 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: --- Stopping container ---
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Processing disk 0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Using qcow2 mapper for /var/lib/one/datastores/0/5/disk.0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Unmapping disk at /var/lib/lxd/storage-pools/default/containers/one-5/rootfs
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Umounting disk mapped at /dev/nbd0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Unmapping disk at /var/lib/one/datastores/0/5/mapper/disk.1
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: shutdown: Umounting disk mapped at /dev/loop0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: ExitCode: 0
Fri Nov 29 16:17:23 2019 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Fri Nov 29 16:17:23 2019 [Z0][VM][I]: New state is POWEROFF
Fri Nov 29 16:17:23 2019 [Z0][VM][I]: New LCM state is LCM_INIT

Also, it doesn't seem to be LXD related:
019 [Z0][VMM][E]: clean: delete_vlan_dev function not implemented.
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: clean: exit
Fri Nov 29 09:17:59 2019 [Z0][VMM][E]: clean: ["/var/tmp/one/vnm/vlan.rb:83:in `exit'", "/var/tmp/one/vnm/vlan.rb:83:in `delete_vlan_dev'", "/var/tmp/one/vnm/vlan.rb:120:in `block in deactivate'", "/var/tmp/one/vnm/vnm_driver.rb:81:in `block in process'", "/var/tmp/one/vnm/vm.rb:64:in `block in each_nic'", "/var/tmp/one/vnm/vm.rb:63:in `each'", "/var/tmp/one/vnm/vm.rb:63:in `each_nic'", "/var/tmp/one/vnm/vnm_driver.rb:84:in `process'", "/var/tmp/one/vnm/vlan.rb:95:in `deactivate'", "/var/tmp/one/vnm/bridge/clean:30:in `<main>'"]
Fri Nov 29 09:17:59 20

Maybe a bad network hook ?

Probably a bad network hook according to the dummy function being called, not LXD related. We can reopen if needed.

Hi I installed Opennebula 5.10 on Ubuntu 18.4 today.. Then I created a VM on a KVM host and after setting up a VM template and instantiating I installed Ubuntu 18.04 on the VM when trying to shutdown the VM I got these errors... Any idea?
brctl show
bridge name	bridge id		    STP enabled	interfaces
br0		        8000.6a291840844b	no		vlan2
virbr0		8000.5254002b56b1	yes		virbr0-nic

Log output from the VM in Sunstone frontend
Fri Dec 13 01:26:09 2019 [Z0][VM][I]: New state is ACTIVE
Fri Dec 13 01:26:09 2019 [Z0][VM][I]: New LCM state is PROLOG
Fri Dec 13 01:26:46 2019 [Z0][VM][I]: New LCM state is BOOT
Fri Dec 13 01:26:46 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/10/deployment.0
Fri Dec 13 01:26:47 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Fri Dec 13 01:26:48 2019 [Z0][VMM][I]: ExitCode: 0
Fri Dec 13 01:26:48 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Fri Dec 13 01:26:49 2019 [Z0][VMM][I]: ExitCode: 0
Fri Dec 13 01:26:49 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Fri Dec 13 01:26:50 2019 [Z0][VMM][I]: ExitCode: 0
Fri Dec 13 01:26:50 2019 [Z0][VMM][I]: Successfully execute network driver operation: post.
Fri Dec 13 01:26:50 2019 [Z0][VM][I]: New LCM state is RUNNING
Fri Dec 13 01:33:07 2019 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Fri Dec 13 01:33:08 2019 [Z0][VMM][I]: ExitCode: 0
Fri Dec 13 01:33:08 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: cancel.
Fri Dec 13 01:33:09 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vnm/bridge/clean
Fri Dec 13 01:33:09 2019 [Z0][VMM][E]: clean: delete_vlan_dev function not implemented.
Fri Dec 13 01:33:09 2019 [Z0][VMM][E]: clean: exit
Fri Dec 13 01:33:09 2019 [Z0][VMM][E]: clean: ["/var/tmp/one/vnm/vlan.rb:83:in `exit'", "/var/tmp/one/vnm/vlan.rb:83:in `delete_vlan_dev'", "/var/tmp/one/vnm/vlan.rb:120:in `block in deactivate'", "/var/tmp/one/vnm/vnm_driver.rb:81:in `block in process'", "/var/tmp/one/vnm/vm.rb:64:in `block in each_nic'", "/var/tmp/one/vnm/vm.rb:63:in `each'", "/var/tmp/one/vnm/vm.rb:63:in `each_nic'", "/var/tmp/one/vnm/vnm_driver.rb:84:in `process'", "/var/tmp/one/vnm/vlan.rb:95:in `deactivate'", "/var/tmp/one/vnm/bridge/clean:30:in `<main>'"]
Fri Dec 13 01:33:09 2019 [Z0][VMM][I]: ExitCode: 1
Fri Dec 13 01:33:09 2019 [Z0][VMM][I]: Failed to execute network driver operation: clean.
Fri Dec 13 01:33:09 2019 [Z0][VMM][E]: Error canceling VM: bridge: -
Fri Dec 13 01:33:09 2019 [Z0][VM][I]: New LCM state is RUNNING
Fri Dec 13 01:33:09 2019 [Z0][LCM][I]: Fail to shutdown VM. Assuming that the VM is still RUNNING (will poll VM).

And on the host
ip a s
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 46:f1:8d:4a:f1:fb brd ff:ff:ff:ff:ff:ff
    inet xx.xx.xx.xx/22 brd xx.xx.xx.255 scope global dynamic ens3
       valid_lft 2675127sec preferred_lft 2675127sec
    inet6 fe80::44f1:8dff:fe4a:f1fb/64 scope link
       valid_lft forever preferred_lft forever
3: ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 46:f1:8d:4a:f1:fc brd ff:ff:ff:ff:ff:ff
    inet6 fe80::44f1:8dff:fe4a:f1fc/64 scope link
       valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6a:29:18:40:84:4b brd ff:ff:ff:ff:ff:ff
    inet6 fe80::6829:18ff:fe40:844b/64 scope link
       valid_lft forever preferred_lft forever
5: vlan1@ens6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 46:f1:8d:4a:f1:fc brd ff:ff:ff:ff:ff:ff
    inet xx.xx.xx.xx/24 brd xx.xx.xx.255 scope global vlan1
       valid_lft forever preferred_lft forever
    inet6 fe80::44f1:8dff:fe4a:f1fc/64 scope link
       valid_lft forever preferred_lft forever
6: vlan2@ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000
    link/ether 46:f1:8d:4a:f1:fb brd ff:ff:ff:ff:ff:ff
    inet xx.xx.xx.xx/32 scope global vlan2
       valid_lft forever preferred_lft forever
    inet6 fe80::44f1:8dff:fe4a:f1fb/64 scope link
       valid_lft forever preferred_lft forever
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:2b:56:b1 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global virbr0
       valid_lft forever preferred_lft forever
8: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
    link/ether 52:54:00:2b:56:b1 brd ff:ff:ff:ff:ff:ff

Please reopen the issue. I guess

Nice to hear this, I don't have time to prove it is a bug.

The bug happens when virtual network is using VNM_MAD = fw/bridge and keep_empty_bridge isn't true. When this PR got merged it didn't add the extracted function to the NoVLANDriver child class and the deactivate action triggered the dummy VLANDriver function which throws an error.


What does the H matrix represent?

I would like to ask what does the H matrix returned when doing gmc represent?

Thanks for your answer! If I can get the camera's intrinsics matrix and extrinsics matrix, can I directly calculate this warp matrix H?


ci: mark StateCall as flaky

Summary of changes

Changes introduced in this pull request:

Filecoin.StateCall is still flaky. Don't test it until fixed.

Reference issue to close (if applicable)

Closes
Other information and links

Change checklist

[x] I have performed a self-review of my own code,
[x] I have made corresponding changes to the documentation,
[x] I have added tests that prove my fix is effective or that my feature works (if possible),
[x] I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

We can remove the corresponding entry from CHANGELOG as well.


prefersHomeIndicatorAutoHidden throws error on Xcode 8

Hi, version 1.4 and newer is available for Swift 4 and Xcode 9 only, please upgrade Xcode or use older version.


Geolocate the Hundreds and Wapentakes of the 1841 Census.

The conclusion of story #975 was not to let the ideal (the Cambridge University data) get in the way of adequate (enabling 'nearby places' searching in the 1841 census).
Therefore, where the data is available on https://www.wikidata.org/w/index.php?search=wapentake&title=Special%3ASearch&fulltext=1&ns0=1&ns120=1 for wapentakes, and https://en.wikipedia.org/wiki/List_of_hundreds_of_England_and_Wales for hundreds.
Where the hundred/wapentake is not georeference in either list, please take the georeference from the named place (e.g. Charlton - https://en.wikipedia.org/wiki/Hundred_of_Charlton - is not georeferenced, then the place name in the hundred title (e.g. in this case, Charlton) should be used. Typically the place name in the hundred title is the place of the moot hill (or not too far from it), which is typically in the centre of the area, so this use is not going to be far off a more precise centre.
If the hundred/wapentake name does not reference a place in the area - e.g. Amounderness, all we can do is find a map, and pick a fairly central place, e.g. Inskipp and use it's georference.  Being a few miles out won't make a huge difference to the search, and is better than nothing.
Priority is for those which we have transcriptions / imasges to transcribe
Coords need to geolocate new hundreds/wapentakes when starting a new 1841 census, and do for the existing ones when moved to FreeCEN2 (fine while on FreeCE1).  @PatReynolds to ask @geoffj-FUG to update handbooks with this information (email to follow, Geoff).
E2 U6 S8 C2:P18

Pat
The cutover version of the Handbook has this included.
Geoff
From: PatReynolds<EMAIL_ADDRESS>Sent: Tuesday, 10 November 2020 3:59 AM
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: geoffj-FUG<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [FreeUKGen/FreeCENMigration] Geolocate the Hundreds and Wapentakes of the 1841 Census. (#1031)
The conclusion of story #975 https://github.com/FreeUKGen/FreeCENMigration/issues/975  was not to let the ideal (the Cambridge University data) get in the way of adequate (enabling 'nearby places' searching in the 1841 census).
Therefore, where the data is available on https://www.wikidata.org/w/index.php?search=wapentake https://www.wikidata.org/w/index.php?search=wapentake&title=Special%3ASearch&fulltext=1&ns0=1&ns120=1 &title=Special%3ASearch&fulltext=1&ns0=1&ns120=1 for wapentakes, and https://en.wikipedia.org/wiki/List_of_hundreds_of_England_and_Wales for hundreds.
Where the hundred/wapentake is not georeference in either list, please take the georeference from the named place (e.g. Charlton - https://en.wikipedia.org/wiki/Hundred_of_Charlton - is not georeferenced, then the place name in the hundred title (e.g. in this case, Charlton) should be used. Typically the place name in the hundred title is the place of the moot hill (or not too far from it), which is typically in the centre of the area, so this use is not going to be far off a more precise centre.
If the hundred/wapentake name does not reference a place in the area - e.g. Amounderness, all we can do is find a map, and pick a fairly central place, e.g. Inskipp and use it's georference. Being a few miles out won't make a huge difference to the search, and is better than nothing.
Priority is for those which we have transcriptions / imasges to transcribe
Coords need to geolocate new hundreds/wapentakes when starting a new 1841 census, and do for the existing ones when moved to FreeCEN2 (fine while on FreeCE1). @PatReynolds https://github.com/PatReynolds  to ask @geoffj-FUG https://github.com/geoffj-FUG  to update handbooks with this information (email to follow, Geoff).
E2 U6 S8 C2:P18
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/1031 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFPD6KWGIAFLTHX2UPTSPAUV7ANCNFSM4TAXXVFA .  https://github.com/notifications/beacon/AKCPIFLKNEKTK5U4RI2UTFDSPAUV7A5CNFSM4TAXXVFKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4K4JADEQ.gif

Implementing as part of cutover


Highligting logical operator keywords

I may be doing something wrong here, but I am unable to get VSCode to highlight any logical operator keywords in my cpp files. I've found that the and, or, not keywords can be recolored using the keyword.operator scope, however, this also colors other operators, such as =/+/etc..
Similar issue for lua: https://github.com/microsoft/vscode/issues/71504
EDIT: Forgot to mention I'm using the Dark+ theme
The code with a problem is:
if (not a and (b or c)) { ... }

It looks like:

It should look like:
and, or and not should be purple like the preceding if (or some other color).

Try running the ">Developer: Inspect Editor Tokens and Scopes" in the command pallet (cmd/ctrl+P) it'll show you all the scopes then you can get the full name instead of just keyword.operator

there's a scope called keyword.operator.wordlike that is probably the one you want to use. It'll work for operators like sizeof too

Thanks Jeff! Got it working now by specifying keyword.operator.and.cpp, keyword.operator.or.cpp, etc. 🙂
One question though, do you know if there is a reason these keywords don't work out of the box? Or did I just mess up my dev environment somehow maybe?

a reason these keywords don't work out of the box?

The theme just chooses not to highlight operators it sounds like. They might consider that a bug but they could consider it a feature


Bring back Capybara gem so feature specs run

In PR #105, we removed Capybara because it's not in our Gemfile explicitly and #105 removed the last gem depending on Capybara.
Because of this, none of our feature specs run:
1) User visits homepage sees list of redirections
  # Feature specs require the Capybara
  #  (http://github.com/jnicklas/capybara) gem, version 2.2.0 or later.
  #  We recommend version 2.4.0 or later to avoid some deprecation
  #  warnings and have support for `config.expose_dsl_globally =
  #  false`.
  # ./spec/features/user_visits_homepage_spec.rb:4

Therefore, bring back Capybara to run feature specs.

I wish we could make RSpec fail those specs. Oh well.


crash when running script

./emr_cost_calculator.py cluster --region=eu-west-1 --cluster_id=j-GCYS9FTHGE3I
[INFO] Retrieving cost in region eu-west-1
Traceback (most recent call last):
File "./emr_cost_calculator.py", line 266, in
print calc.get_cluster_cost(args.get('--cluster_id'))
File "/usr/local/lib/python2.7/dist-packages/retrying.py", line 49, in wrapped_f
return Retrying(*dargs, **dkw).call(f, *args, **kw)
File "/usr/local/lib/python2.7/dist-packages/retrying.py", line 206, in call
return attempt.get(self._wrap_exception)
File "/usr/local/lib/python2.7/dist-packages/retrying.py", line 247, in get
six.reraise(self.value[0], self.value[1], self.value[2])
File "/usr/local/lib/python2.7/dist-packages/retrying.py", line 200, in call
attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
File "./emr_cost_calculator.py", line 145, in get_cluster_cost
instance_groups = self._get_instance_groups(cluster_id)
File "./emr_cost_calculator.py", line 203, in _get_instance_groups
inst_group.price = prices[group.instancetype]['ec2'] +
KeyError: u'm4.xlarge'

@spetsnaz84 sorry for the late response.
I believe this is happening becuase m4.xlarge is missing from the config.yml file


A seriouse memory leak problem

Hello,
I recently used it to develop my own server program, however, I found that memory consumption is very fast in MultiprocessFTPServer mode.
I suspect it caused by the memory leak.
So, I want to know whether the bug is fixed in Github or not?
The attachment link you provided may be invalid. #263

Sorry for the delay but I'm pretty busy. I will try to take a look at this
issue next week.
On Sat, Nov 25, 2017 at 10:08 AM, Young Yu<EMAIL_ADDRESS>wrote:

Hello,
I recently used it to develop my own server program, however, I found that
memory consumption is very fast in MultiprocessFTPServer mode.
I suspect it caused by the memory leak.
So, I want to know whether the bug is fixed in Github or not?
The attachment link you provided may be invalid. #263
https://github.com/giampaolo/pyftpdlib/issues/263
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/giampaolo/pyftpdlib/issues/449, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAplLCgUlGGgZrhHtnw0n00tuCo2DBEHks5s59khgaJpZM4QqXOS
.

--
Giampaolo - http://grodola.blogspot.com

Closing as duplicate of #447


update gpb deps and travis CI build on Elixir 1.2

update gpb deps to 3.19.0
add Elixir 1.2.0 in Travis build matrix

(for some reason, I did mix test with 43 tests, 9 failures even with a fresh clone on your master)

CI result shows Elixir 1.2 seems not working for current test....

I have rebase your fix to #41, now CI passed

Thanks!


Define default Grid Purchase Order workflow states and related constraints

Moving to Closed after reviewing a draft view of workflow states and constraints with five process SMEs. Integrated feedback into the draft state (workflow) diagrams. As a next step, we'll turn our attention to aligning on how a "version" and/or "draft" object moves through these workflows. Then ensure the Guide-level and Reference-level information sections of the RFC appropriately capture the design.

Moving to Closed after reviewing a draft view of workflow states and constraints with five process SMEs. Integrated feedback into the draft state (workflow) diagrams. As a next step, we'll turn our attention to aligning on how a "version" and/or "draft" object moves through these workflows. Then ensure the Guide-level and Reference-level information sections of the RFC appropriately capture the design.


[#38] Fix sonar.sources attribute in sonar-project.properties

Description
Fix sonar-project.properties in order to be analyzed from sonarqube
Related Issue

Fixes <issue_link>

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Tests only (no source changes)

Checklist:

[x] Code changes
[ ] Unit tests added
[ ] Acceptance tests added

Hey @panagiotisbellias , thanks for your contribution! We're still fixing some CI failures, we will get to your PR soon after.


Split tree builder base from subclasses

The builder.build module was split off from its init for state/behaviour separation but it's still in need of refactoring.
Put the base and the individual builders in separate modules: in fact make build.py a subpackage tree_builders.
Remember to chase down any references in the rest of the library

Chinois will not be affected if the builder.__init__ module namespace is preserved

Completed in 7955220


I want to make footer visually appealing with some social media link along with icons.

The footer is too simple.
I want to make it more visually appealing and user attractive acording to it's color grading.
And also add some social media icons in the footer for better connectivity with users.
NOTE I am the hacktoberfest participant. So please add this label also if assign to me.

Nice one @Suvadip-sana ! Im assigning it to you

@aswathcm29  please assign this issue to me i will create modern sticky footer.
Uploading Vite + React - Brave 2024-09-28 18-21-30 (online-video-cutter.com).mp4…

@aswathcm29  @jahnvisahni31
Thank you!
I start working on it.

@aswathcm29 @jahnvisahni31 Thank you! And also add a point level accordingly and gssoc-etd label as per guidelines Then I will start work on it.

Yes @Suvadip-sana  You can start working

Yes! Thank you.

@aswathcm29 please assign this issue to me i will create modern sticky footer. i will make sure it's matches the theme of project.
https://github.com/user-attachments/assets/16876db7-d3b8-4055-ba2d-25b850e3c94b

Please marege the pull request  with relevant all tags


resolve #98 fix CRLF end of line character

To check files with CRLF character on Linux or Mac:
find . -not -type d -exec file "{}" ";" | grep CRLF

To remove the CR character:
 sed -i -e 's/^M//g' filename

against the wrong branch


COMPRESS-400 : Squashed version of  COMPRESS-400-REDUX.

Add support for extra PAX headers (local and global).
This PR has a single squash commit to simplify final  review
Signed-off-by: Simon Spero<EMAIL_ADDRESS>

Coverage increased (+0.1%) to 84.886% when pulling 8aeaa9c418862fc1d4fb4e166da72a2fac2493dc on sesuncedu:COMPRESS-400-squash into 19e1b02f754a9b7bc969eb17bd52cc36a85c4d74 on apache:master.


elasticsearch_indices_docs_primary metric is missing labels (cluster, es_***_node, etc..)

I'm using v1.0.2 of the exporter and looks like elasticsearch_indices_docs_primary is missing all the "default" labels that we find in other metrics: cluster, es_***_node, host

ping @zwopir 😄

actually, it's not really a bug. The indices metrics are querying
http://<host>:9200/_all/_stats?level=shards.
This endpoint doesn't contain the values for the "default" labels, only the
node_id (some ES internal entity without external meaning). We've
implemented the metric classes as independent prometheus collectors. The
each call different ES API endpoints, each providing a different set of
information, so I don't really see a convenient way to correlate these
collectors without completely rewriting the exporter.
Can you elaborate on your use case so we can find a solution?!

We have multiple Elasticsearch clusters scraped by the same Prometheus server, and we use the cluster label in our queries to isolate the metrics per cluster.
Not having at least the cluster label makes it difficult to easily filter these metrics.
Currently I'm using a PromQL "hack" where I group these metrics with another (node) metric based on the instance label and extract the cluster label from there, it seems to work but was hoping to have these labels natively from the exporter.

ok, I understand. It makes sense. To be honest, setting up a elasticsearch_exporter for each cluster seems like the easiest solution. The collectors that have/need label values from each other are completely independent. So correlating the label values would require some serious refactoring that doesn't make sense from any other point of view.
Maybe excluding the promQL-hack to recorded queries simplifies that usage of these metrics...?!

We are running elasticsearch_exporter on every elastic node, but they are all (nodes from all clusters) defined under the same job because we use Puppet based service discovery to build the targets list.
I already created a recording rule with the query I mentioned and we started using that in our dashboards, so not a big deal, though if this could be somehow fixed on the exporter level it would be stellar.

ok, I understand your use case for the labels. I can't promise a short-term fix for your issue though, but I'll keep it in mind for a next refactoring round.

Hi @dannyk81,
ideas are there for next refactoring round: we'll provided the sub-collectors with an update mechanism that provides the labels that are not know to the specific sub-collector from a update go routine. That routine regularly calls the ES on the / route to retrieve the cluster labels. Doing so, we ensure that

we avoid calling the / route on every scrape in every sub-collector
we avoid configuring static labels
the cluster labels are semi up to date without restarting the exporter

I can't promise to start within the next two weeks, but I wanted you to know there's at least some progress on this issue

Thanks for the update @zwopir! Looking forward for this 😃

Hey @zwopir, just wanted to check if this is still on track?
I see two PRs that seem to be addressing this (#162 & #143), but looks like they are somewhat stale.
Thanks!

the track is still on. I wanted to give #162 the chance to incorporate the requested changes. If I don't receive feedback by tomorrow I'll do it myself.

released: https://github.com/justwatchcom/elasticsearch_exporter/releases/tag/v1.1.0rc1


DCP1 project updates to terra

DCP1 projects were not exported/imported through ingest and the GCP staging area to terra, they were exported from the DSS via another GCP staging area to terra.
This means the data files for DCP1 projects do not exist in the staging area used for export/import to DCP2 and so updates for DCP1 projects do not currently make it to terra.
Options to solve this

improve importer to not require data files
change exporter to not export file descriptors/file metadata if files are not being exported
copy the files from one GCP staging area to the other and rearrange file structure to match new structure
change exporter to export to the other GCP staging areas for DCP1 projects - need file rearrangement in that bucket too
download files from browser, upload and then re-export all data files alongside the metadata
implement full DCP2 updates doc

Discussed with Jeff and Drew from the Broad.
Short term plan - change the exporter to not export file descriptors/file metadata, test in dev before production
Long term plan - implement DCP2 updates spec but scope out some aspects, such as deletions. Timeframe on this tbd
note: for testing in dev - we need to export a project get import, delete the project from the staging area, export update (metadata json only) and ask for import
@aaclan-ebi did I miss anything?

Also noting here the issue on provenance fields that may be affecting other DCP1 datasets https://github.com/ebi-ait/hca-ebi-dev-team/issues/433#issuecomment-877187803

PR needs approval

This change needed for the exporter not to add schema major and minor version fields for metadata using older schema is deployed in prod.
https://gitlab.ebi.ac.uk/hca/ingest-exporter/-/pipelines/199822

When updating a DCP1 dataset, the workaround steps are:

Force set a submission from Complete to Valid

do a PUT request to the commitValid link of the submission

Delete state tracker pod so K8 will create a new pod, this will trigger state tracker's initialisation which will sync its state from Ingest database will allow transition from Valid -> Submitted -> Exporting. If this is not done state tracker will think that the submission is in Complete state and wouldn't set the submission state to the next state.
Click submit button again from the UI and check "Export only metadata" checkbox
or via API by sending a PUT request to submit link with payload ["Export_Metadata"]
After submission is set to Exported. Remove the descriptors and file metadata from Terra staging area. There is a known issue/limitation in importing projects without data files and any file metadata cannot be updated yet. Hopefully, this will be resolved when we implement the DCP2 specs for update in collaboration with Data Import team.

When updating a DCP1 dataset, the workaround steps are:

Force set a submission from Complete to Valid by sending a PUT request to the commitValid link of the submission
Delete state tracker pod so K8 will create a new pod, this will trigger state tracker's initialisation which will sync its state from Ingest database will allow transition from Valid -> Submitted -> Exporting. If this is not done state tracker will think that the submission is in Complete state and wouldn't set the submission state to the next state.
Click submit button again from the UI and check the "Export only metadata" checkbox
or via API by sending a PUT request to submit link with payload ["Export_Metadata"]
After the submission is set to Exported. Remove the descriptors and file metadata from the Terra staging area. There is a known issue/limitation in importing projects without data files and any file metadata cannot be updated yet. Hopefully, this will be resolved when we implement the DCP2 specs for updates in collaboration with the Terra Data Import team.

Trying to do a test run for Tabula Muri's dataset in dev first. There might be other exporter issues and changes needed.


Outdated Azure SLA link

The Azure SLA link under https://docs.microsoft.com/en-us/azure/virtual-machines/windows/overview#manage-availability, targeted to outdated Azure VM SLA - https://azure.microsoft.com/en-us/support/legal/sla/virtual-machines/v1_0/
The latest Azure VM SLA = https://azure.microsoft.com/en-us/support/legal/sla/virtual-machines/v1_6/

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

ID: ff5b5898-88d9-7aec-1516-e157e92564a7
Version Independent ID: f9807092-172c-d8d0-fc7d-17204faea51b
Content: Windows Virtual Machines Overview
Content Source: articles/virtual-machines/windows/overview.md
Service: virtual-machines-windows
GitHub Login: @davidmu1
Microsoft Alias: davidmu

@WootJay Thank you very much for your feedback. We will investigate your inquiry and get back with you.

@WootJay good catch! I have assigned this to the content author to review and update the content as needed.
@davidmu1 please take a look.

@MicahMcKittrick-MSFT: Please assign to @iainfoulds who is now supporting this article.

Thanks, @WootJay . I've updated the link in a PR to point straight to https://azure.microsoft.com/support/legal/sla/virtual-machines/ . This link automatically goes to the latest version of the SLA to minimize future problems. When the PR merges, this issue will automatically close.
#in-process


How to publish to GitHub wiki?

I want to publish my documents to the repository wiki page directly.
My repository is at location https://github.com/funkyidol/CodingNotes
I tried using the clone url for wiki ( https://github.com/funkyidol/CodingNotes.wiki.git) but it keeps giving the error "Could note publish on GitHub"

Hello,
Thanks a lot for your work on stackedit, it's a really great tool.
I used stackedit to publish to github via gh-pages but the sequence diagrams I did do not show properly, I can only see the text and the diagrams don't appear. Is there any way I could have them display properly?
Thanks a lot.


Fix HttpClient.Post error on subsequent call

Description

Replace access to properties with fields in internal methods and code.

Motivation and Context

Fixes nanoFramework/Home#1112.

How Has This Been Tested?

Test using Test Code
Addtional Test using a loop
No memory leaks after multiple post calls to same uri.

  _httpClient.BaseAddress = new Uri("http://httpbin.org/anything");

  for (int i = 1; i < 30; i++)
  {
     var content = new StringContent("{\"someProperty\":\"someValue\"}", Encoding.UTF8, "application/json");
     var result = _httpClient.Post("", content);
     result.EnsureSuccessStatusCode();
     Thread.Sleep(1_000);
   }

Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[x] Bug fix (non-breaking change which fixes an issue with code or algorithm)
[ ] New feature (non-breaking change which adds functionality to code)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project (only if there are changes in source code).
[ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
[ ] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
[ ] I have read the CONTRIBUTING document.
[ ] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
[ ] I have added new tests to cover my changes.

@alberk8 care to review please? 😃

@alberk8 care to review please? 😃

Tested your changes to the code and it works.


Render viewport on demand

Godot version:

OS/device including version:

Issue description:

Steps to reproduce:
Minimal reproduction project:

Sorry, I didn't mean to publish this


fix: disable confirm button until fees are loaded

Try out this version of the Hiro Wallet - download extension builds.

This PR disables the tx confirm button until fee estimations are loaded.

cc/ @kyranjamie @fbwoolf @beguene @He1DAr

Would it make sense to bundle this PR with any other that we have on dev for this and last week and ship on Monday?

Would it make sense to bundle this PR with any other that we have on dev for this and last week and ship on Monday?

I am going to merge this one into dev. There have been a few minor fixes we can release ...maybe I can get the overlapping text one I'm working on now in too. I can make a release PR for Monday.


Update to support 2.13 and Play 2.7.x

Update project to support Scala 2.11 through 2.13.
Update project to support Play Framework 2.7.x.
Update CI configuration and add automatic CI publishing.
Add type annotations to public members and implicits.

forgot to squash before merge, oops

fixed merge in d8b039e2012976b788f7fffb95c315e1c9961836


Tracking issue for Issue 2

Issue 2 will be released end of February 2023. Here is the article list:

[ ] Optimize Rust Binary Search @Folyd
[ ] TBD @xxchan
[ ] TBD @xuanwo
[ ] TBD @wangrunji0408
[ ] TBD @ZhangHanDong
[ ] Interview with Sunli @Folyd
[ ] https://github.com/RustMagazine/rustmagazine/pull/23

Do you have any article or author for Issue 2? Feel free to update the article list above. 😸 @LCrossman @malagant @macko76 @mfrw @dmosc


Create task1.txt

Issue: #2
Kali linux screenshot added

Hey @Suvanwita
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

Kindly make separate pull request to receive points for Task-2. Here you'll only receive 20 points for Task-1

Hey @Suvanwita
Your PR has been merged 🥳🥳 and you have earned 20 points.
Thanks for contributing in OpenCode'24 ✨✨


offending filename should be logged on Malformed UTF-8 error

also, this bug was closed for a bogus reason and should be reopened:  https://github.com/protocool/AckMate/issues/closed#issue/13

At the end of my needs_line_scan method (around line 2597) I changed the end of the method to:
    my $regex = $opt->{regex};
    if ( ! utf8::valid($buffer) ) {
			$buffer = Encode::encode_utf8($buffer);
    }
		return $buffer =~ /$regex/m;

And you have to add 'use utf8;'  to the beginning of the script... does this seem reasonable?

Guys,
thanks for taking the lead on sorting this stuff out.
I've seen someone mention that setting export LC_CTYPE=en_US.UTF-8 in the environment helps.
I'd like to experiment with the various options before merging into AM proper, and at the same time updating AM's version of ack to the latest.
Can any of you point me to files which cause the UTF explosions so I can test against it?
Thanks, Trev

I attempted to add logging there as noted by @jjb above, but the log items did not show up in the output. I can play with it a bit later unless @yyyc514 gets to it first. :)

@yyyc514 solution works for me
@protocool I was getting stung on language files in ext.js

This is basically the same as my patch for the malformed UTF-8 errors, which I posted on #13. I feel like this ticket should just be closed and the patch should be applied. No one has pointed out any issues with it, so I'm not sure why this hasn't been resolved already. I agree that the request in this ticket seems pointless, we don't need logging for the error - we just need it to go away since ack and ackmate shouldn't tell what format our files are supposed to be in.

Correct. I've forked the project and attempted to apply, but the problem, you see, is that ackmate_ack is actually generated from http://github.com/petdance/ack - see: https://github.com/trisweb/AckMate/tree/master/bundle_extras
So it's not exactly simple.

@protocool I wget this file http://www.fiscontex.com.br/legislacao/ICMS/aliquotainternaicms.htm and the problem happens with it. This file seens to be written on Windows FrontPage and have weird windows encoding chars. Hope it helps.


Adds a pinned message to the rooms table

The rooms table will keep track of a single i64 to track a pinned
message for that room. Three associated endpoints have been added to
keep track of this pinned message.
GET pinned_message
Will return the pinned_message_id which should map to the pinned message
to display
POST pin_message
Takes a single i64 corresponding to a message id and updates the room
table to keep record of this message id as a pinned message
DELETE pinned_message
Resets the pinned message in the rooms table to 0 for no pinned message
All endpoints are under authorisation and POSTING and DELETING require
moderator status.

TODO

[ ] Migration code

Waiting for #24, which will handle the DB changes.


Adding simple Notes bot to C# samples

This is a simple bot which can take "Notes" either in 1:1 conversation or Group conversation.

@dolbyarun,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@dolbyarun thank you for the contribution.  For this repository, we have a set of standards we follow (e.g. that there are Node and C# versions of all samples, etc).  Your sample looks valuable, but may not meet the standards for this repository (e.g. a Node version).  You might consider publishing it separately to a new repo.