Updated Advanced Kubernetes Hack with changes from hack delivery

Replaced the application in the Azure DevOps WTH with the one from GitHub


Configure CI/CD

CI/CD configuration complete
When you commit, the github action automatically does the following:

build
unit test
Firebase Deploy


Hexidecimal parsing issue.

Microsoft PowerToys version
0.67.1
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
In PowerToys Run with Calculator plugin enabled:
Enter "0x7FFFFFFF", displays<PHONE_NUMBER>: correct decimal representation.
Enter "0x80000000", displays<PHONE_NUMBER>1562100000: incorrect decimal representation.
Enter "0x7FFFFFFF + 1", displays<PHONE_NUMBER>: correct calculation.
Enter "0x80000000 + 1", displays<PHONE_NUMBER>1562100000: incorrect calculation displayed.
Enter "0x90000000 - 0x10000001", displays<PHONE_NUMBER>1562100000: incorrect calculation displayed.
Enter "0x90000000 - 0x80000000", displays 268435456: correct calculation displayed.
Enter "0x90000000 - 0x80000001", displays 268435456: incorrect calculation displayed.

✔ Expected Behavior
Entering "0x80000000" should display<PHONE_NUMBER>.
❌ Actual Behavior
Entering "0x80000000" actually displays<PHONE_NUMBER>1562100000.
Other Software
No response

This appears to be fixed!


[cleanup] remove unused dep on diem-devtools

Is this still active?

@sblackshear Closing given the inactivity on this. Please re-open and ping me if you want to revive this.


fix: fix all locator examples

replaced all browser.findElement(..) for element(..) to make the API documentation more consistent

When looking @ this PR, can you also please check https://github.com/angular/protractor/issues/4385#issuecomment-315630653 for the broken circleCI?

This makes sense. We are trying to tell our users that these are inherited by the Protractor locator by from selenium-webdriver's By. Also with this change we are telling our users that this can be used by the element API.
I like it. 😄

Tnx, I did a webinar last week and saw this during my demo. It made people confuse, because they now saw different implementations. I think this would be more consistent.

What about the circleCI? Shall I also change that with a PR!

Hmmm... I don't think your changes should cause errors in the test suite. I plan to rerun circle then merge it


Plugin settings are not imported

Hi and first of all: thanks for the great addition to CraftCMS! Much appreciated.
Now I found a small issue with importing plugin settings. I install the https://github.com/groe/craft-sitemap plugin which produces following schema after exporting:
  Sitemap:
    isInstalled: true
    isEnabled: true
    settings:
      sections:
        4:
          changefreq: weekly
          priority: '0.5'
        1:
          changefreq: weekly
          priority: '1.0'

Unfortunately these settings are not importing correctly, it is always importing an empty object to the database. This is even overriding the settings on the other server. It's just strange that the export is running just fine.
Could it be a problem that there are numbers in the schema?
The settings of other plugins which don't have numbers as keys are imported correctly.
Maybe you have an idea whats going wrong? Thanks for your help!

Now I had time to dig into this issue and it turns out, that it's not the fault of schematic. I opened a pull request on the Sitemap plugin to solve this.
see https://github.com/groe/craft-sitemap/pull/4

Great, thanks


[Feature Request] Way to cancel sorting from outside of .on("sortable:start")

Hello, great plugin! Thank you very much for your awesome work.
I have a jQuery event handler for the focus event on a child element inside the each element that is being sorted. I'm attempting to suppress the sorting from within this event handler, because anything longer than a snappy click is triggering the sortable events.
Additionally, I have code executing on completion of the sortable:stop event, but I do not see any way to suppress the event in the case that the order is not changed. There is no reason to make a request to my server if the order did not change. In both of these instances, the event should be suppressed.
Inside my focus event handler, I've tried all of the following (to no avail) to cancel or suppress the sortable events.
$(".sortable-item").on("click focus", "button", function(e) {

	e.preventDefault();
	e.stopPropagation();

	mySortable.dragging = false;

	// ...

});

Is there a way that I can get the current event before sortable:drop is triggered to cancel the sorting? Such as mySortable.event or something?
And can you add functionality to allow easy checking of the pre/post-sorting order? So inside of sortable:stop, perhaps we could add a member to the dragEvent object named something like didReorder as a boolean value? That way, we could just check if (!e.data.dragEvent.didReorder) return false;.
Thanks!

Library version<EMAIL_ADDRESS>Browsers: Using Chrome v72, presumably functions similarly in other major browsers

The only events that supports cancellation within sortable is "SortableStartEvent" and "SortableSortEvent" .
You can use it like event.cancel();
I don't know if this answers your question, because you've only posted part of you're code.

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible or it has been fixed in a newer version.
Please reopen if you still encounter this issue.
Thank you!


Various test improvements to increase coverage and speed things up

Pull Request Description
This PR fixes some typing problems in distribution, speeds MetaIsATest to 20s (previously 80s) by caching the computed values in ValuesGenerator and makes sure there are "polyglot variants" of tests checking the behavior of Meta and TypeOf on JavaScript & other values.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] All code follows the
Java,
All code has been tested:

[x] Unit tests have been written where possible.

There are strange errors like:
 INFO ide_ci::program::command: bashℹ     - [FAILED] should send Get request using fetch [99ms]
 INFO ide_ci::program::command: bashℹ         Reason: An unexpected dataflow error ((Request_Error.Error 'IllegalArgumentException' Nothing)) has been matched (at /runner/_work/enso/enso/test/Tests/src/Network/Http_Spec.enso:57:13-53).

Very strange given we only change ascription (which is ignored) and unit tests (which are unrelated).

There are strange errors like:
  - [FAILED] should send Get request using fetch [99ms]
Reason: An unexpected dataflow error ((Request_Error.Error 'IllegalArgumentException' Nothing))
has been matched (at /runner/_work/enso/enso/test/Tests/src/Network/Http_Spec.enso:57:13-53).

Very strange given we only change ascription (which is ignored) and unit tests (which are unrelated).

This is a global problem with our CI now. Try to add CI: Clean build required label and restart the job. The problem seems to be related to the recent GraalVM upgrade


#1077 Display responses provided in a previous test

This PR fixes this issue, by showing the questions and answers all the time (if they present), even if the test is not completed.

@mbrookeswebdev I can't reproduce that.

@mbrookeswebdev I can't reproduce the issue you mentioned. Please provide a direct link to the page, so I can check. Thanks.

@mbrookeswebdev I can't reproduce the issue you mentioned. Please provide a direct link to the page, so I can check. Thanks.

@lloback I can't reproduce this error now either, so maybe a glitch of some sort.

@mbrookeswebdev check if you need anything else from this PR. Let's move the ticket!

@lloback I wasn't able to reproduce. I can see your example using https://jac-admin-develop--pr1259-feature-1077-display-7jlvq929.web.app/exercises/wdpALbyICL7ZxxN5AQt8/tasks/qualifying-tests/JTx6phqRwUJwroLgkBgR/response/Ls2eoLaM56Lgg1RrXFJb/
But was unable to see answers for those I transfered to a mop up myslef.

But was unable to see answers for those I transfered to a mop up myslef.

Hi @KateMJAC , can you please post the link here of the ones you transferred and did not see the results? Let me investigate.

@lloback the link is: https://jac-admin-develop--pr1259-feature-1077-display-7jlvq929.web.app/exercises/7NEtYLJiv7bels10ANKT/tasks/qualifying-tests/QodQ79B6aRTJXwKh57Pe/response/tDgLOzxuiiZRKtze0ZT5/
Maybe I have done something wrong, but it seems like a simple process.

@lloback the link is: https://jac-admin-develop--pr1259-feature-1077-display-7jlvq929.web.app/exercises/7NEtYLJiv7bels10ANKT/tasks/qualifying-tests/QodQ79B6aRTJXwKh57Pe/response/tDgLOzxuiiZRKtze0ZT5/
Maybe I have done something wrong, but it seems like a simple process.

PLease check this link again, @KateMJAC . Regards.

@KateMJAC do you need anything else from me on this ticket? This is ready to approve and merge.

@KateMJAC and @joy-ade Please check this functionality.

This ticket has been sent to the UTG. We can't merge until we et positive feedback. Update to follow.

@lloback this needs to go to the UTG for positive testing before it can be merged.
The PR review needs to be re-generated to provide it to the UTG.
Tom attempted to regenrate it but an error message flagged.
@joy-ade FYI

We need to generate a new URL for testing. Closing this PR and opening a new one


index.md

header
This section is for learning of markdown that is the ligthweight language to communicate in github

this markdown


Make ReST API error messages more verbose

It would be nice to have HTTP error messages more verbose, for instance, if i would submit a route with non-existing execution type (lest say sync-a), API will return Invalid JSON.
But technically, request body formed correctly, but error in specific field value.
For given case it would be nice to have error message as:
Invalid route type
There are multiple places where such improvement may bring better user experience.

In HEAD, this is handled correctly. See the validation message in the example below:
$ curl -X POST -d '{"route":{"type": "asynca", "path": "/hello-sync2", "image": "iron/hello", "format": "http", "max_concurrency":2 }}' localhost:8080/v1/apps/testapp/routes
{"error":{"message":"validation failure list:\nvalidation failure list:\nInvalid route Type"}}


updated go to version 1.15.7 to fix CVE-2021-3114 and CVE-2021-3115

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

/cherry-pick release-1.4


No PRs in any of organisation repos, greenkeeper is enabled

See repos in https://github.com/JSONScript

Sorry for the late reply. Around the time you opened this issue we had slight problems in our queue, but executed all remaining tasks.
Looking at your PR site it looks like it's working now, so I'm assuming this got solved by now: https://github.com/JSONScript/jsonscript-proxy/pulls.
Thanks for reporting.
Stephan


建议输出图片的格式为png

Stickers Bot "/addsticker" 需要的图片格式为png

Use /finish png instead of /finish.

THX

@victoriqueko thanks , I don't believe this info is stated anywhere else in the readme or instructions when using the bot, it's very useful


issues with upsert and createMany

I create about 700 datasets when processing the results of a capabilities query i.e. getting properties of wms layers.
I am adding layer options into this table:

CREATE TYPE layer_options_field_enum AS enum(
  'wms_format',
  'wms_layer',
  'wms_info_format',
  'wfs_output_format',
  'wfs_layer'
);

CREATE TABLE layer_options(
  layer_option_id text PRIMARY KEY DEFAULT NULL,
  tile_layer_id uuid DEFAULT NULL REFERENCES tile_layers(tile_layer_id) ON DELETE CASCADE ON UPDATE CASCADE,
  vector_layer_id uuid DEFAULT NULL REFERENCES vector_layers(vector_layer_id) ON DELETE CASCADE ON UPDATE CASCADE,
  field layer_options_field_enum DEFAULT NULL,
  value text DEFAULT NULL,
  label text DEFAULT NULL,
  queryable boolean DEFAULT NULL,
  legend_url text DEFAULT NULL
);

I first built the insertions using create, that was before adding the boolean column queryable:
  const layerOptions = layers.map((l) => ({
    layer_option_id: `${row.wms_base_url}/${l.Name}/wms_layer`,
    tile_layer_id: row.tile_layer_id,
    field: 'wms_layer',
    value: l.Name,
    label: l.Title,
    legend_url: l.Style?.[0]?.LegendURL?.[0]?.OnlineResource,
  }))
  for (const l of layerOptions) {
    try {
      await db.layer_options.create({
        data: l,
      })
    } catch (error) {
      console.error('hello, getCapabilitiesData 5, error from creating:', error)
    }
  }

Works (also with the boolean column queryable) but is slow (takes about 30 seconds) due to the 700 datasets. Also: A wms service can have multiple layers, in this case over 700. Every time a single layer is created, the same 700 layer data is requeried. As this data can change (but rarely does), upsert would be preferrable to create.
So I changed the query to use upsert instead. First this worked fine:
  const layerOptions = layers.map((l) => ({
    layer_option_id: `${row.wms_base_url}/${l.Name}/wms_layer`,
    tile_layer_id: row.tile_layer_id,
    field: 'wms_layer',
    value: l.Name,
    label: l.Title,
    legend_url: l.Style?.[0]?.LegendURL?.[0]?.OnlineResource,
  }))
  for (const l of layerOptions) {
    try {
      await db.layer_options.upsert({
        create: l,
        update: l,
        where: {
          layer_option_id: l.layer_option_id,
        },
      })
    } catch (error) {
      console.error(
        'hello, getCapabilitiesData 5, error from upserting:',
        error,
      )
    }
  }

Then I added a boolean queryable to the table:
  const layerOptions = layers.map((l) => ({
    layer_option_id: `${row.wms_base_url}/${l.Name}/wms_layer`,
    tile_layer_id: row.tile_layer_id,
    field: 'wms_layer',
    value: l.Name,
    label: l.Title,
    queryable: l.queryable,
    legend_url: l.Style?.[0]?.LegendURL?.[0]?.OnlineResource,
  }))
  for (const l of layerOptions) {
    try {
      await db.layer_options.upsert({
        create: l,
        update: l,
        where: {
          layer_option_id: l.layer_option_id,
        },
      })
    } catch (error) {
      console.error(
        'hello, getCapabilitiesData 5, error from upserting:',
        error,
      )
    }
  }

BANG, this error occurs:
hello, getCapabilitiesData 5, error from upserting: ZodError: [
  {
    "code": "invalid_union",
    "unionErrors": [
      {
        "issues": [
          {
            "code": "invalid_union",
            "unionErrors": [
              {
                "issues": [
                  {
                    "code": "invalid_type",
                    "expected": "boolean",
                    "received": "number",
                    "path": [
                      "data",
                      "queryable"
                    ],
                    "message": "Expected boolean, received number"
                  }
                ],
                "name": "ZodError"
              },
              {
                "issues": [
                  {
                    "code": "invalid_type",
                    "expected": "object",
                    "received": "number",
                    "path": [
                      "data",
                      "queryable"
                    ],
                    "message": "Expected object, received number"
                  }
                ],
                "name": "ZodError"
              }
            ],
            "path": [
              "data",
              "queryable"
            ],
            "message": "Invalid input"
          },
          {
            "code": "unrecognized_keys",
            "keys": [
              "tile_layer_id"
            ],
            "path": [
              "data"
            ],
            "message": "Unrecognized key(s) in object: 'tile_layer_id'"
          }
        ],
        "name": "ZodError"
      },
      {
        "issues": [
          {
            "code": "invalid_union",
            "unionErrors": [
              {
                "issues": [
                  {
                    "code": "invalid_type",
                    "expected": "boolean",
                    "received": "number",
                    "path": [
                      "data",
                      "queryable"
                    ],
                    "message": "Expected boolean, received number"
                  }
                ],
                "name": "ZodError"
              },
              {
                "issues": [
                  {
                    "code": "invalid_type",
                    "expected": "object",
                    "received": "number",
                    "path": [
                      "data",
                      "queryable"
                    ],
                    "message": "Expected object, received number"
                  }
                ],
                "name": "ZodError"
              }
            ],
            "path": [
              "data",
              "queryable"
            ],
            "message": "Invalid input"
          }
        ],
        "name": "ZodError"
      }
    ],
    "path": [
      "data"
    ],
    "message": "Invalid input"
  }
]
    at get error (index.mjs:538:31)
    at _ZodObject.parse (index.mjs:638:22)
    at validate (validation.ts:14:31)
    at Table._update (table.ts:1258:34)
    at table.ts:1467:23
    at table.ts:569:15
    at Table.fetchIncludes (table.ts:770:14)
    at table.ts:564:23
    at transactionalDB.ts:49:11
    at adapter.ts:186:53

I am not passing numbers to the boolean field, only booleans.
Also, the keys it is not recognizing are defined and as mentioned, it worked when using create.
So I got thinking and decided to first deleteMany, then createMany. Thus circumventing the upsert error. And I was also hoping for it to be a lot faster:
  // 1. deleteMany
  const layerOptionIds = layers.map(
    (l) => `${row.wms_base_url}/${l.Name}/wms_layer`,
  )
  try {
    await db.layer_options.deleteMany({
      where: {
        layer_option_id: {
          in: layerOptionIds,
        },
      },
    })
  } catch (error) {
    console.error('hello, getCapabilitiesData 3, error:', error)
  }
  // 2. createMany
  const layerOptions = layers.map((l) => ({
    layer_option_id: `${row.wms_base_url}/${l.Name}/wms_layer`,
    tile_layer_id: row.tile_layer_id,
    field: 'wms_layer',
    value: l.Name,
    label: l.Title,
    queryable: l.queryable,
    legend_url: l.Style?.[0]?.LegendURL?.[0]?.OnlineResource,
  }))
  try {
    await db.layer_options.createMany({
      data: layerOptions,
    })
  } catch (error) {
    console.error('hello, getCapabilitiesData 6, error:', error)
  }

The deletion part works.
But createMany fails:
hello, getCapabilitiesData 6, error: Error: field value must be a string, number, boolean, null or one of the registered custom value types
    at _class16._sanitizeValue (squel.js:421:19)
    at _class16._setFieldsRows (squel.js:1743:26)
    at _class16.setFieldsRows (squel.js:1864:14)
    at _this32.<computed> [as setFieldsRows] (squel.js:2722:27)
    at Builder.createMany (builder.ts:59:8)
    at Table._createMany (table.ts:537:31)
    at executor.ts:75:7
    at new Promise (<anonymous>)
    at Executor.execute (executor.ts:74:12)
    at Table.createMany (table.ts:224:27)

Hi @barbalex, the issue with upsert may be the same as the one you encounter previously (https://github.com/electric-sql/electric/issues/782). It looks like the boolean value which internally is stored as an integer is not being converted back to a boolean for some reason. Hence, Zod complaining. Will need to check why this is happening and keep you informed.

I'll just piggy-back on this issue as I found (I think) another case where zod is seeing an integer instead of a boolean
I have these two tables:
CREATE TABLE ingredients_photo_uploads (
    id UUID PRIMARY KEY,
    created_at TIMESTAMP WITH TIME ZONE NOT NULL,
    uploaded_at TIMESTAMP WITH TIME ZONE,
    upload_duration_sec FLOAT,
    ai_processing_duration_sec FLOAT,
    photo_url TEXT
);

CREATE TABLE ingredients (
    id UUID PRIMARY KEY,
    name TEXT NOT NULL,
    is_reviewed BOOLEAN NOT NULL,
    fill_level INTEGER NOT NULL,
    is_ground BOOLEAN,
    ingredients_photo_uploads_id UUID,
    FOREIGN KEY (ingredients_photo_uploads_id) REFERENCES ingredients_photo_uploads(id)
);

ALTER TABLE ingredients_photo_uploads ENABLE ELECTRIC;
ALTER TABLE ingredients ENABLE ELECTRIC;

And this query:
db.ingredients_photo_uploads.liveMany({
      orderBy: {
        created_at: `asc`,
      },
      include: {
        ingredients: true,
      },
    })

Which errors with:
ZodError: [
  {
    "code": "invalid_union",
    "unionErrors": [
      {
        "issues": [
          {
            "code": "invalid_type",
            "expected": "boolean",
            "received": "number",
            "path": [
              "is_reviewed"
            ],
            "message": "Expected boolean, received number"
          },
          {
            "code": "invalid_type",
            "expected": "boolean",
            "received": "number",
            "path": [
              "is_ground"
            ],
            "message": "Expected boolean, received number"
          },
          {
            "code": "unrecognized_keys",
            "keys": [
              "ingredients_photo_uploads_id"
            ],
            "path": [],
            "message": "Unrecognized key(s) in object: 'ingredients_photo_uploads_id'"
          }
        ],
        "name": "ZodError"
      },
      {
        "issues": [
          {
            "code": "invalid_type",
            "expected": "boolean",
            "received": "number",
            "path": [
              "is_reviewed"
            ],
            "message": "Expected boolean, received number"
          },
          {
            "code": "invalid_type",
            "expected": "boolean",
            "received": "number",
            "path": [
              "is_ground"
            ],
            "message": "Expected boolean, received number"
          }
        ],
        "name": "ZodError"
      }
    ],
    "path": [],
    "message": "Invalid input"
  }
]
    at get error (index.mjs:538:31)
    at ZodUnion.parse (index.mjs:638:22)
    at nonTransactionalDB.ts:58:27
    at Array.map (<anonymous>)
    at nonTransactionalDB.ts:49:32

I tried today with version 0.9.4 and the errors remain

Hi @barbalex, i've not yet found the time to look into this bug. I hope to find some time soon to investigate further.

@kevin-dp it's not blocking for me, so no Stress

I tried today with electric-sql 0.9.6. Userting now works 😆
But createMany still errors as before.

@barbalex just to confirm - you're getting this error with createMany but you are not getting it when creating the exact same rows with create one by one?

@barbalex just to confirm - you're getting this error with createMany but you are not getting it when creating the exact same rows with create one by one?

Exactly

@barbalex could you check if this issue persists with v0.10.x? I'm wondering whether this is an issue related to https://github.com/electric-sql/electric/issues/1095
If it still persists, is there any chance you could provide the sample dataset with the full data model so I can reproduce?

@msfstef I now tried using electric-sql v0.10.1
upsert works as since 0.9.6
createMany still errors with same error:

Two remarks:

I am chunking the array that is passed into createMany to 500 objects to not create errors due to too many objects

const chunked = chunkArrayWithMinSize(layerOptions, 500)
for (const chunk of chunked) {
  try {
    const chunkResult = await db.layer_options.createMany({ data: chunk })
    console.log('hello, getCapabilitiesData 5a, chunkResult:', chunkResult)
  } catch (error) {
    // field value must be a string, number, boolean, null or one of the registered custom value types
    console.error('hello, getCapabilitiesData 5b, error:', { error, chunk })
  }
}

I know that more than 500 can create an error because createMany works for me in a different table (implemented recently):

const chunked = chunkArrayWithMinSize(occurrences, 500)
for (const chunk of chunked) {
  await db.occurrences.createMany({
    data: chunk,
  })
}

where occurrences are defined as:
CREATE TABLE occurrences(
  occurrence_id uuid PRIMARY KEY DEFAULT NULL,
  account_id uuid DEFAULT NULL REFERENCES accounts(account_id) ON DELETE CASCADE ON UPDATE CASCADE,
  occurrence_import_id uuid DEFAULT NULL REFERENCES occurrence_imports(occurrence_import_id) ON DELETE CASCADE ON UPDATE CASCADE,
  place_id uuid DEFAULT NULL REFERENCES places(place_id) ON DELETE SET NULL ON UPDATE CASCADE,
  not_to_assign boolean DEFAULT NULL,
  comment text DEFAULT NULL,
  data jsonb DEFAULT NULL,
  id_in_source text DEFAULT NULL,
  geometry jsonb DEFAULT NULL,
  label text DEFAULT NULL
);

while layer_options are defined as:
CREATE TYPE layer_options_field_enum AS enum(
  'wms_format',
  'wms_layer',
  'wms_info_format',
  'wfs_output_format',
  'wfs_layer'
);

CREATE TABLE layer_options(
  layer_option_id text PRIMARY KEY DEFAULT NULL,
  account_id uuid DEFAULT NULL REFERENCES accounts(account_id) ON DELETE CASCADE ON UPDATE CASCADE,
  tile_layer_id uuid DEFAULT NULL REFERENCES tile_layers(tile_layer_id) ON DELETE CASCADE ON UPDATE CASCADE,
  vector_layer_id uuid DEFAULT NULL REFERENCES vector_layers(vector_layer_id) ON DELETE CASCADE ON UPDATE CASCADE,
  field layer_options_field_enum DEFAULT NULL,
  value text DEFAULT NULL,
  label text DEFAULT NULL,
  queryable boolean DEFAULT NULL,
  legend_url text DEFAULT NULL
);

Hi @barbalex and @KyleAMathews, i tried reproducing this issue using your examples but didn't manage to reproduce it. I used your exact schemas and in case of Kyle the same query but the issue did not occur. If this is still a problem for you, could you share a reproducible example such that we can further investigate this issue.

I am closing this as I tried again today using electric-sql v0.12.1 and it works


apis: defined Reservation.Spec.AllocateOnce as pointer

Ⅰ. Describe what this PR does
Defined Reservation.Spec.AllocateOnce as pointer.
Previously, the default value of AllocateOnce was set to true, but because of the empty tag, AllocateOnce could not be set to false, which caused problems in Reservation reuse scenarios.
In the previous test, this problem was not exposed because the CRD Schema was not updated into test cluster.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in make test

/approve


There needs to be a ApplyLayout pass

What is the expected enhancement?
The default StochasticSwap pass does not map a circuit from the logical (virtual) representation to the physical representation for running on hardware.  The previous swap_mapper pass used to do this.  As such, there needs to be an ApplyLayout pass that flattens the quantum registers and applies the layout to map to hardware for running on a physical backend.

The other swap mapper passes (BasicSwap and LookaheadSwap) also do not map circuit from the virtual representation to the physical one. We definitely need a function to do this. I think we have at least two options for the solution: 1) creating a new pass (ApplyLayout) as @nonhermitian proposed or 2) providing a utility function. Both solutions have pros and cons. (1) can easily tell when the circuit is changed from virtual to physical to the other passes (by require(ApplyLayout)), but it has difficulty in ensuring to apply the ApplyLayout pass. Leaving it to users of pass manager may not work. Any good idea? (2) can simply impose the responsibility to developers of swap passes, but it has difficulty in telling when the circuit is changed from virtual to physical to the other passes. I guess we can know the change by introducing new interface class PhysicalMappingPass and swap passes implement it and require(PhysicalMappingPass) . So far, I prefer (2). Any better idea for imposing the application of layout, no matter for (1) or (2)?

So, I would say that the mapping from virtual to physical qubits should be explicit, i.e. there is a pass that does this.  This is more in line with the spirit of the transpiler where each pass does a simple task.  There is no reason why a swap mapper should actually do the map from virtual -> physical.  Indeed, one could, for example, just be exploring the characteristics of a swap mapper applied to different topologies without actually intending to run the resulting circuits on a device of that layout.

@nonhermitian can you please write an example here that failed? So it can be used to test the solution

It is hard to get a simple example to work because there are several bugs in the way.  However, here is a QV example:
import numpy as np
from qiskit import *
from qiskit.transpiler import transpile
from qiskit.tools.qi.qi import random_unitary_matrix
from qiskit.mapper import two_qubit_kak
from qiskit.mapper import CouplingMap
from qiskit.extensions.standard import SwapGate
%matplotlib inline

IBMQ.load_accounts()
backend = IBMQ.get_backend('ibmq_16_melbourne')
basis = backend.configuration().to_dict()['basis_gates']
coupling_map = CouplingMap(backend.configuration().to_dict()['coupling_map'])

from qiskit.transpiler.passes import *
from qiskit.transpiler.passes.mapping import *

pm = qiskit.transpiler.PassManager()
pm.append(Unroller(basis))
pm.append(BarrierBeforeFinalMeasurements())
pm.append(DenseLayout(coupling_map))
pm.append(StochasticSwap(coupling_map))
pm.append(Decompose(SwapGate))
pm.append(CXDirection(coupling_map))
pm.append(CXCancellation())
pm.append(Unroller(basis))
pm.append(Optimize1qGates())

def build_qv_circuit(seed, n, depth):
    """Create a quantum program containing model circuits.

    The model circuits consist of layers of Haar random
    elements of SU(4) applied between corresponding pairs
    of qubits in a random bipartition.

    name = leading name of circuits
    n = number of qubits
    depth = ideal depth of each model circuit (over SU(4))

    """
    np.random.seed(seed)
    q = QuantumRegister(n, "q")
    c = ClassicalRegister(n, "c")
    # Create measurement subcircuit
    qc = QuantumCircuit(q,c)
    # For each layer
    for j in range(depth):
        # Generate uniformly random permutation Pj of [0...n-1]
        perm = np.random.permutation(n)
        # For each pair p in Pj, generate Haar random SU(4)
        # Decompose each SU(4) into CNOT + SU(2) and add to Ci
        for k in range(int(np.floor(n/2))):
            qubits = [int(perm[2*k]), int(perm[2*k+1])]
            U = random_unitary_matrix(4)
            for gate in two_qubit_kak(U):
                i0 = qubits[gate["args"][0]]
                if gate["name"] == "cx":
                    i1 = qubits[gate["args"][1]]
                    qc.cx(q[i0], q[i1])
                elif gate["name"] == "u1":
                    qc.u1(gate["params"][2], q[i0])
                elif gate["name"] == "u2":
                    qc.u2(gate["params"][1], gate["params"][2],
                                 q[i0])
                elif gate["name"] == "u3":
                    qc.u3(gate["params"][0], gate["params"][1],
                                 gate["params"][2], q[i0])
                elif gate["name"] == "id":
                    pass  # do nothing
    qc.measure(q,c)
    return qc

qc =  build_qv_circuit(123456, 14, 1)
comp_qc = transpile(qc, backend=backend, pass_manager=pm)

comp_qc will not run on the backend e.g. ibmq_16_melbourne because the qubits are still virtual and have not been mapped to their physical qubits.  Relabeling qubits using the passmanager layout property does the correct mapping pm.property_set._properties['layout']._v2p:
{(QuantumRegister(14, 'q'), 0): 0,
 (QuantumRegister(14, 'q'), 1): 1,
 (QuantumRegister(14, 'q'), 2): 2,
 (QuantumRegister(14, 'q'), 3): 13,
 (QuantumRegister(14, 'q'), 4): 3,
 (QuantumRegister(14, 'q'), 5): 12,
 (QuantumRegister(14, 'q'), 6): 4,
 (QuantumRegister(14, 'q'), 7): 11,
 (QuantumRegister(14, 'q'), 8): 10,
 (QuantumRegister(14, 'q'), 9): 5,
 (QuantumRegister(14, 'q'), 10): 9,
 (QuantumRegister(14, 'q'), 11): 6,
 (QuantumRegister(14, 'q'), 12): 8,
 (QuantumRegister(14, 'q'), 13): 7}

I just talked with with @itoko and I convince him that we dont need an ApplyLayout pass. I think also that was the conclusion with @nonhermitian today (however, the StochasticSwap needs readjustment). Shall we close this issue?

All the work discussed here should be complete or is covered in other issues.


Manully cherrypick for #18030 in 1.4

manual cp of #18030

add mixer mtls ready label only when control plane auth is enabled.

try it on...

revert control plane label.

update isMtlsEnabled criteria

finish the rest checking file content

fix the isMtlsEnabled default true, only false when explicitly set.

add more attempts in fortio/ingress traffic. route takes more time?

add key file checks for probe in sidecar pilot agent

remove hack and correct the sds check condition.

revert change.

update golden and override in mini

fix rbac test by disabling mtls explicitly

And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.

trying to see if re-sync from head of the 1.4 can trigger the new installer test's better luck.

@incfly: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test gencheck_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test gencheck_istio_release-1.4

unit-tests_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test unit-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@incfly: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gencheck_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test gencheck_istio_release-1.4

unit-tests_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test unit-tests_istio_release-1.4

integ-new-install-k8s-tests_istio_release-1.4
c6266e46eec3cb32d4ddc6beb7b47a39609ca5b5
link
/test integ-new-install-k8s-tests_istio_release-1.4

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I believe this PR is a duplicate of #18197

Close as duplicate of https://github.com/istio/istio/pull/18197 which I don't think we should merge either (see comment there)


Token search for datatype ContactPoint differs from specification

FHIR specifies that the fields to use for system|code from ContactPoint are
ContactPoint.use and ContactPoint.value respectively.
Additionally it notes that the ContactPoint.use field should be prepended with http://hl7.org/fhir/contact-point-system/.
This differs from our current implementation which uses ContactPoint.system in place of ContactPoint.use (and without the prepended system).

From https://www.hl7.org/fhir/R4/search.html#token:
At the discretion of the server, token searches on ContactPoint may use special handling, such as ignoring punctuation, performing partial searches etc.

Our new implementation just uses the value and ignores the rest.  Per the spec, this seems within our rights as a server.  Lets consider this one resolved.


Model save only works for Tabular model type.

@avsolatorio Hi!
I have tried to use checkpoints_dir parameter for a relational model and it seems that no checkpoints are saved for this type. Also, in the code I see that only Tabular model type is handled. Is this a bug?
https://github.com/avsolatorio/REaLTabFormer/blob/bf1a38ef8f202372956ac57a363289c505967982/src/realtabformer/realtabformer.py#L1450

Hello @echatzikyriakidis, the checkpoints_dir argument is directly passed to the training arguments of the Transformers trainer, so I'm unsure why you do not see the checkpoints:
https://github.com/avsolatorio/REaLTabFormer/blob/bf1a38ef8f202372956ac57a363289c505967982/src/realtabformer/realtabformer.py#L199
The model itself should be saved, see:
https://github.com/avsolatorio/REaLTabFormer/blob/bf1a38ef8f202372956ac57a363289c505967982/src/realtabformer/realtabformer.py#L1448
The line you're referring to saves the artefacts (checkpoints) generated during the sensitivity mechanism only available to the tabular model.


Make build work on all platforms(most of them)

Some terminal emulators don't seem to like nested commands and ;.

Fixes some issues concerning https://github.com/GoogleChrome/devsummit/issues/44#issuecomment-258186236

I know you are not thinking of making the build work elsewhere anytime soon, but I think it's better that taking any more build related issues. \cc @paullewis

Thanks... again! #heroicwork

And again, please have a look at #34. \cc @paullewis


Add breakdown of activity risk calculation

This is a huge improvement, thanks so much.
I left some suggestions for the strings - in general we want to be referencing the text that they saw / selected rather than the internal enum values (for instance the silent key is exposed as "not talking" so we should use that language in the explanation). It would also be nice to explain a bit about why the choice is good in the explanation card (for instance, "for the airplanes air filtration" rather than "for plane").

Yeah but that makes them really long which makes the breakdown hard to read

Could we improve that with formatting? Maybe one per line?
On Fri, Sep 17, 2021 at 1:42 PM Kathy Garcia @.***>
wrote:

This is a huge improvement, thanks so much.
I left some suggestions for the strings - in general we want to be
referencing the text that they saw / selected rather than the internal enum
values (for instance the silent key is exposed as "not talking" so we
should use that language in the explanation). It would also be nice to
explain a bit about why the choice is good in the explanation card (for
instance, "for the airplanes air filtration" rather than "for plane").
Yeah but that makes them really long which makes the breakdown hard to read
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/microCOVID/microCOVID/pull/1096#issuecomment-922069967,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABM25LPMSXVNQTTEZKU3JDDUCOR5BANCNFSM5DMZ3FRA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Could we improve that with formatting? Maybe one per line?

That would be my suggestion as well. Maybe it just needs to be a series of lines rather than trying to put it all on one line. I think it would be easier to read that way even with the short labels.
So glad his is happening. I think it'll help people who want to understand the underlying model!

Thanks for the contrib here. It looks to have had a good reception, but has outstanding changes requested. This project would be happy to revisit the concerns addressed herein should someone wish to revive the effort. For now, closing as abandoned.


No Show Sneaking After /npc sneak

Hello,
From the tests we have done, when we run the command "/ npc sneak" the message shows that the NPC is sneak but the NPC does not sneak. It's an NPC player like you and me.
We have no error in the console.
This server is running Paper version git-Paper-156 (MC:1.14.4) Implementing API version 1.14.4-R0.1-SNAPSHOT)
Checking version, please wait...
You are 3 version(s) behind

Citizens version 2.0.25-SNAPSHOT (build 1738)
Website: https://www.citizensnpc.co
Author: Fullwall

Denizen version 1.0.6-SNAPSHOT (build 1676-REL)
Author: The DenizenScript Team

Please include your Denizen version
What entity type is the NPC (player, villager, ...?)

It's good

... That confused me, until I realized you edited the main post.
Update Denizen, you're quite far behind: https://ci.citizensnpcs.co/job/Denizen/

We have just tried with the latest version but the result is the same :(

I have test something like that:
/npc sneak
/npc sneak
/npc stand
and I have like anwser "test (npc name) is already standing !'
But the NPC never sneak.

I think it might be client side bug, cause when I join my 1.14.4 server on a 1.14.4 client the NPC doesn't appear to be crouching however when I join my 1.14.4 server on a 1.13.2 client the npc crouches

I have the same problem. I have Minecraft 1.14.4. When i use /npc sneak command there is message that npc is sneaking but npc is still just standing. I have tried several versions of denizen and citizens but it hasn't changed
anything.

The original code for this relied on Bukkit calls... but Spigot appears to have not updated how those calls work for 1.14.x.
I've gone ahead and implemented an NMS module based solution to make it work properly again.

Thank you very much for your work !


musescore: 4.4.1 -> 4.4.2

Marked as a draft, waiting for a fix for #318210 by @orivej .
Description of changes
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@orivej opened separate PRs for fixing different issues with the musescore package, and so these are not included here. Merging since CI is green (besides the Darwin builds which naturally take too long).


PHP Version support

This library (as of 2023-02-27) is still compatible with PHP 7.3.
Soon the support will be drop according to PHP Supported Versions.
The test matrix cannot run using PHP 7.3 since Sunshine PHP (implementation of PSR libraries) support PHP 7.4 or higher.
Close this issue when:

PHP library support is updated to PHP 7.4 or higher.
Someone provide a patch to test using PHP 7.3.

(Even with the option 2, the support for PHP 8.1 or lower will be removed soon)

Related PR: #13


Add a note to readme about project migration

Would be also useful to archive this repo to avoid any confusion.

:+1:

Will need force-merge from @stefanl-st given the failing build (safe since it's only the readme touched)


fix dashboard bugs

Signed-off-by: Ziqi Zhao<EMAIL_ADDRESS>Fixes #539

I will leave this PR to someone with more experience in Grafana to review.
Personally I'd prefer keeping the environment variable, because that allows us to easily change the datasource, but I'm not sure if it is doable.
Anyways, thanks for taking care of that @fatsheep9146!

I will leave this PR to someone with more experience in Grafana to review. Personally I'd prefer keeping the environment variable, because that allows us to easily change the datasource, but I'm not sure if it is doable.
Anyways, thanks for taking care of that @fatsheep9146!

I agree with your opnion about keeping environment variable. But for now, the problem is that the environment variable is not correctly configured which result that the dashboard could not be opened rightly and throwing out an error emplating Failed to upgrade legacy queries Datasource ${DS_PROMETHEUS} was not found.
So I think maybe it's more suitable to use const for now to let user can open the dashboard without failure. And then try to improve the dashboard with configurable datasource variable. =D

Agreed


post: A guide to IPFS connectivity in browsers

Starts with @TheDiscordian's https://github.com/ipfs/ipfs-blog/pull/233 PR and adds the following:

Copy edits (mainly standards from https://docs.ipfs.io/community/contribute/grammar-formatting-and-style/)
Clarity edits

@TheDiscordian Agreed, but alas Forestry is auto-"fixing" this — that said, I'd like to publish a minimally edited version of this content in the IPFS docs (PR forthcoming) and we can use official formatting there 😊

@jessicaschilling I think that sounds like a good idea as well! @autonome and I were thinking both sounded like a good idea, I'm down with whatever works best :+1:

Merged - thanks @TheDiscordian and @autonome! Will name-check you in a related docs PR.


Add a contribution section in readme

For the developers who wish to contribute to pykg2vec, we should let them know how to help/what help we need.

This is done.


wifi shield option on user.py

Is there a way to activate the wifi module calling user.py? Like:
python OpenBCI_Python-master/user.py  --daisy --add csv_collect raw_andrea1_20190715-232901.csv --record-duration 37 --safety-duration 1
I got the error
'OSError: Cannot find OpenBCI port'
So it's referring to the the dongle not the wifi shield. Is there a parameter or a way to switch to the wifishield? Thanks

i got it too.  Has it been solved


html/template: document that it strips comments

What version of Go are you using (go version)?
go1.11.1 (playground)
Does this issue reproduce with the latest release?
Yes.
What did you do?
package main

import (
	"fmt"
	"html/template"
	"os"
)

const templateSrc = `<style>/* one */</style> /* two */ <!-- three -->`

func main() {
	fmt.Println(templateSrc)
	tmpl := template.Must(template.New("").Parse(templateSrc))
	fmt.Println(tmpl.Tree.Root.String())
	tmpl.Execute(os.Stdout, nil)
}

https://play.golang.org/p/WPnEwLYTBkF
What did you expect to see?
Comments preserved in output.
<style>/* one */</style> /* two */ <!-- three -->
<style>/* one */</style> /* two */ <!-- three -->
<style>/* one */</style> /* two */ <!-- three -->

What did you see instead?
Comments are stripped.
<style>/* one */</style> /* two */ <!-- three -->
<style>/* one */</style> /* two */ <!-- three -->
<style> </style> /* two */

This behaviour is apparently intentional (https://github.com/golang/go/issues/14256), but it is surprising and undocumented.  Templates already have their own special comment syntax ({{/* */}}), so i didn't expect that they would gobble up HTML and CSS (and presumably JS) comments as well. This needs to be called out in the documentation, ideally with a rationale and workaround.

If no one is on it, I would like to give it a try

I see this has been silent for a while, @hellozee do you have time to address the comments in cl/148833 ?😊

I did update the patch accordingly, @empijei, please do drop anything that I may have missed, :smile:

It seems this has been quiet. Reminder for @hellozee there are 3 unresolved comments on the patchset for this issue at cl/148833 :smile:


Reloading the map in the same div overlaps with current values

Hi,
Thanks for the great plugin.
We have different booked seats for different time slots. The user can click on each time slot. The data is fetched via ajax from.
The first click shows proper result. However, when we click on the next time slot, the booked seats of previous slots and this slots overlap with each other.
Please suggest what to do.
Thanks

Hi, could you please paste some code snippets so I can try to replicate it?

Hi,
Thank you so much for the quick response.
I am integrating it with Woocommerce (Wordpress).
Link: http://bit.ly/1J9QlhH
To recreate the issue, from the calendar, select the date as 21st. (I have added data for this.)
Now, click on 9:00 pm. It loads few blocked seats for that time slot. If you click on 3:00 am now, it does not refresh the layout. It does not even allow to select the available seats.
If we refresh the page now, and click 3:00 am first, then it shows available seats.
However, I would like to change the behaviour as, it should refresh for each time slot selection or date selection.
If you need FTP details, I can share with you.
Thanks again.

If you want to load a different map every time, then you will need to use different div containers. Using the same div is currently not supported.
Yet if you merely want to mark seats as taken, there's no nead to call .seatChars again, you just use selector metods together with .status()

Hi,
Thank you so much for the direction. Yes, I dont have to load the seat map again. I need to query only booked seat.
sc.find('unavailable').status('available');//to make all the seats available and to flush out previous blocked.
sc.get($var_booked).status('unavailable');//to block the current seats.


Add decompress plugin

Added a new decompression plugin

Thanks 😍
I'll fix CI and tweak code a bit here and there. Most likely today.

What do you think about the following API?
sequence(
  find('dir/*.tar'),
  decompress({ /* options */ }),
  write('extracted/')
)

I see that it's possible to delegate writing functionality to write plugin and even have something like rename or whatever plugins in between (I know that there is a map option in decompress lib itself, but this flow doesn't feel natural in case of Start). Actually the only option we need from decompress is an array of plugins.

Approved! I like this approach.

How do you plan to do it?

Sorry for the long reply. I'll merge this almost as is for now. That idea with write plugin requires a lot more work than expected, and I don't want to block this PR.
In a few words Start is not fully ready to work effectively with binary (probably huge) data the way it works with text files. It's going to be changed soon, I found the elegant solution that needs to be tested.

Published as @start/plugin-unpack 🎉 Please let me know if there are some issues, I'll add real tests later.

Okay!


Amazon Error setting/closing connection: General SSLEngine problem.

When I'm trying to use pyverdict with PostgreSQL I get this error:
py4j.protocol.Py4JJavaError: An error occurred while calling z:org.verdictdb.VerdictContext.fromConnectionString.
: org.verdictdb.exception.VerdictDBDbmsException: [Amazon](600000) Error setting/closing connection: General SSLEngine problem.
        at org.verdictdb.connection.ConcurrentJdbcConnection.<init>(ConcurrentJdbcConnection.java:72)
        at org.verdictdb.connection.ConcurrentJdbcConnection.create(ConcurrentJdbcConnection.java:86)
        at org.verdictdb.VerdictContext.fromConnectionString(VerdictContext.java:229)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:498)
        at py4j.reflection.MethodInvoker.invoke(MethodInvoker.java:244)
        at py4j.reflection.ReflectionEngine.invoke(ReflectionEngine.java:357)
        at py4j.Gateway.invoke(Gateway.java:282)
        at py4j.commands.AbstractCommand.invokeMethod(AbstractCommand.java:132)
        at py4j.commands.CallCommand.execute(CallCommand.java:79)
        at py4j.GatewayConnection.run(GatewayConnection.java:238)
        at java.lang.Thread.run(Thread.java:748)

For some reasons, Redshift's JDBC driver seems to be used instead (of postgres driver). I'll post further updates shortly.

It should work now. Please update by pip install pyverdict --upgrade
>>> import pyverdict
>>> pyverdict.__version__
'<IP_ADDRESS>'
>>> verdict = pyverdict.postgres(host='<IP_ADDRESS>', port=5432, dbname='postgres', user='postgres')
>>> verdict.sql('show schemas')
9 row(s) in the result (0.404 seconds)
                                       schema
0                               verdictdbmeta
1                               verdictdbtemp
2  pyverdict_postgres_datatype_test_schema464
3                          information_schema
4                                      public
5                                  pg_catalog
6                             pg_toast_temp_1
7                                   pg_temp_1
8                                    pg_toast
>>>

Let me close this issue, but please feel free to reopen this if you still experience the same (or closely related) problems.

Hello, I am having this issue, I can not connect to my instance. [HY000][600000] Amazon Error setting/closing connection: General SSLEngine problem.

Let me get back to this in a couple of days. I’m flying back to the
US today.
Yongjoo
On Mon, Jul 22, 2019 at 11:05 AM santfirax<EMAIL_ADDRESS>wrote:

Hello, I am having this issue, I can not connect to my instance.
[HY000][600000] Amazon http://600000 Error setting/closing connection:
General SSLEngine problem.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mozafari/verdictdb/issues/376?email_source=notifications&email_token=AAKBQCQAQYEYO23DBBN6IF3QAUITBA5CNFSM4HSHOUM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OR3UI#issuecomment-513613265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKBQCQNRHEM42XAKQJBJOLQAUITBANCNFSM4HSHOUMQ
.

--
Yongjoo Park, Ph.D.
Research Fellow
Computer Science and Engineering
University of Michigan
2260 Hayward St.
Ann Arbor, MI 48109-2121
Office: 4957 Beyster
Phone:<PHONE_NUMBER>
Website: yongjoopark.com


Add Improved Chase Camera from SpaceDock

This pull request was automatically generated by SpaceDock on behalf of BahamutoD, to add Improved Chase Camera to CKAN.
Mod details:
name = /mod/571/Improved%20Chase%20Camera
author = BahamutoD
abstract = Better chase camera behavior.
license = GPLv3
Homepage = http://forum.kerbalspaceprogram.com/index.php?/topic/72457-10-improved-chase-camera-v151-5415/
description = This plugin gives you the option to make the camera follow your surface velocity vector.
This gives you a better feeling on how your plane is moving, its angle of attack, sideslip, etc.
Press Tab to toggle.
(You can change the key in settings.cfg).
Toggling it off and on will bring it back to the default view angle.
Set autoSnap to true in the config to have it always snap back to default angle.
The default view angle can be changed in the config file as well.
Two modes:

Toggle while in Locked mode: Camera rolls with plane.

Toggle while in Free mode: Camera stays level.

Please direct questions about this pull request to BahamutoD.

Should be fine to merge now.

I removed the old .kerbalstuff file. I trust the override is no longer needed?

Nah, old overrides serve no technical purpose. The only reason to keep them is for reference.


Create test that fully expands all dynatrees and displays all screens

Inspired by issue DISPATCH-751 Clicking entities/connector in stand-alone console prints "Error: [ngModel:numfmt] Expected 1 to be a number"
Check that no errors were printed. This will be bit tricky, because new W3C standardized WebDriver does not have API to simply read browser log. Useful even without this feature, when test is watched by person.

This can be also used to generate up-to-date screenshot gallery for docs. Or for visual diffing.


NdisMMapIoSpace links point to SDV rule rather than function

In the "NdisMoveMemory macro (ndis.h)" article, the "NdisMMapIoSpace" links point to NdisMMapIoSpace rule (ndis), but they should point to NdisMMapIoSpace function (ndis.h).
I did not check whether other articles have the same error.

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

ID: 658062ef-1831-edeb-756b-81fa00ebdf99
Version Independent ID: 76fa06c9-1783-c0ce-c9a8-a420ef8cd6a2
Content: NdisMoveMemory macro (ndis.h) - Windows drivers
Content Source: wdk-ddi-src/content/ndis/nf-ndis-ndismovememory.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @aviviano
Microsoft Alias: amvivian

Hi @KalleOlaviNiemitalo, Thanks for letting us know about this issue. I've updated the links to the NdisMMapIoSpace function in this article as well as others that had the same bug. Appreciate you taking the time to let us know!


Anything wrong with CSVIter?

I have two csv file : feature.csv and label.csv , with only ten samples.
the feature.csv is :

1,1
2,2
3,3
4,4
5,5
6,6
7,7
8,8
9,9
10,10

the label.csv is :

1
2
3
4
5
6
7
8
9
10

I write a python script to load data using CSVIter.
import mxnet as mx
import numpy as np

train = mx.io.CSVIter(
	data_csv="./feature.csv" ,
	label_csv="./label.csv" ,
	data_shape = (2,) ,
	label_shape = (1,) ,
	batch_size = 3
)

for batch in train :
    array = batch.data[0].asnumpy()
    for line in array :
        print ",".join([str(i) for i in line])

train.reset()

for batch in train :
    array = batch.label[0].asnumpy()
    for item in array :
        print item

the output is

1.0,1.0
2.0,2.0
3.0,3.0
4.0,4.0
5.0,5.0
6.0,6.0
7.0,7.0
8.0,8.0
9.0,9.0
10.0,10.0
1.0,1.0
2.0,2.0
3.0
4.0
5.0
6.0
7.0
8.0
9.0
10.0
1.0

it can be seen from the output , there are 12 lines from feature.csv , it is right .
But there are only 9 lines from label.csv and not begin with 1.0.
Are there anything wrong with csvIter or anything bug in my script ?

have you solved your problem? i have the same problem.

This is because by default, the CSVIter has round_batch being True. Which means with batch size 3, and total instance 10, two more examples are consumed at the first round. When you call reset, the call is ignored because the second round has already begun due to the round padding. As a result, you got fewer examples in the second round.

@pluskid thank you very much.
@R1ncy By set round_batch = False , we can get same sample each round.
train = mx.io.CSVIter(
    data_csv="./feature.csv" ,
    label_csv="./label.csv" ,
    data_shape = (2,) ,
    label_shape = (1,) ,
    batch_size = 3 ,
    round_batch = False
)

@Lisz1024 @pluskid  thank you! :)
is there any difference between i set the data_shape=(1,2) and data_shape=(2,)?
i saw "each row data in csv file will be reshaped into the data_shape" on #1204


Feature request: Crafting materials enhacements

Right now crafting materials are nice, but they could use some enhancements for adding extra wood or gem material.

we could use custom material values for blocks and such
planks and string should get oredict whitelist entry fields
the option choose what item gets picked for the Materials and You page on the material
the option to disable head, handle, and/or extra for a material

I don't completely understand what you are suggesting here.  Can you provide an example of how this might be used?

Well, I'm going to try to explain it better.
"we could use custom material values for blocks and such" - This is mostly for wood, logs have a crafting material value of four while planks have a value of one. The pack maker may also want to have gems use the block when crafting tool parts, gems could have nine in a block or four hence the reason for it being customizable.
"planks and string should get oredict whitelist entry fields" - For wood, with the goal of making it one hundred percent clear to the pack creator what to define planks for wood as. Probably not necessary right now, in the future it might be needed to add planks as an extra type of block to make.
"the option choose what item gets picked for the Materials and You page on the material" - This is for if the pack creator wants the logs display on the side of the page, with the meltibilty and tool previews.
"the option to disable head, handle, and/or extra for a material" This is for custom bow string/fletching only materials, but it could be used for a binding, head, or handle only material. Say the pack creator has a material like hemp, manastring, or some kind of leaf thing and they don't want people making tools with it but only bow/arrow parts with it.
I hope I explained what I meant and how these might be used by people in a way so you can understand.

We need to be careful when dealing with the number of items that make the block.  Because you can both melt and cast both items and blocks then it is important that melting and casting values remain constant across both items and blocks.  This gets one level more complex if you want to configure the number of items that make up a block.
I don't really understand your planks/wood/oredict paragraph.  I have only considered this mod for manipulating metals, gems and (more recently) string and leaves.
The item that appears as the "representative item" in Materials and You is the first ingot in the whitelist.  If that does not exist but Gems have been provided then the first Gem is used.  If that does not exist then, in more recent game versions, Tinkers chooses to use the Shard.  This could be configurable in a future version of Infini-TiC.
Any configurable part can be disabled in Infini-TiC by setting all the relevant stats for that part to zero.

I don't think there is anything more to be done here.  Thanks for the feedback.


Does @opentelemetry/instrumentation-express support esm yet?

I'm working on an API service with ESM, and it cannot trace API request path properly by @opentelemetry/instrumentation-express.
It occurs @opentelemetry/instrumentation-express Module express has been loaded before @opentelemetry/instrumentation-express so it might not work, please initialize it before requiring express warning after API service initialized.
In opentelemetry-instrumentation README address limitation of external modules, I'm wondering does @opentelemetry/instrumentation-express support esm yet?
Below is my code example:
index.js
import tracer from "./tracer.js";
import express from "express";

const app = express();

app.use((err, req, res, next) => {
    const activeSpan = tracer.getActiveSpan();
    activeSpan.recordException(err);
    next();
});

app.get("/test", (req, res) => {
    res.send("Hello world");
});

app.listen(3000);

tracer.js
import opentelemetry from "@opentelemetry/sdk-node";

import { diag, trace, DiagConsoleLogger, DiagLogLevel } from '@opentelemetry/api';
import { ExpressInstrumentation } from "@opentelemetry/instrumentation-express";
import { HttpInstrumentation } from "@opentelemetry/instrumentation-http";
import { PgInstrumentation } from '@opentelemetry/instrumentation-pg';
import { getNodeAutoInstrumentations } from "@opentelemetry/auto-instrumentations-node";

import  { Resource } from "@opentelemetry/resources";
import {
    SemanticResourceAttributes,
} from "@opentelemetry/semantic-conventions";
import grpc from "@grpc/grpc-js";
import { CollectorTraceExporter } from "@opentelemetry/exporter-collector-grpc";

// For troubleshooting, set the log level to DiagLogLevel.DEBUG
// diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.INFO);
diag.setLogger(new DiagConsoleLogger(), DiagLogLevel.DEBUG);

const apmConfig = {
    url: process.env.APM_URL,
    serviceName: process.env.APM_SERVICE_NAME,
    podId: process.env.POD_NAME
}

let meta = new grpc.Metadata();
meta.add("x-sls-otel-project", apmConfig.serviceName);
const collectorOptions = {
    url: apmConfig.url,
    metadata: meta,
};

const traceExporter = new CollectorTraceExporter(collectorOptions);

const traceResource = new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: apmConfig.serviceName,
    [SemanticResourceAttributes.K8S_POD_UID]: apmConfig.podId,
})

const traceInstrumentations = [
    new HttpInstrumentation(),
    new PgInstrumentation(),
    new ExpressInstrumentation(),
    getNodeAutoInstrumentations()
]

// SDK configuration and start up
const sdk = new opentelemetry.NodeSDK({
    resource: traceResource,
    traceExporter,
    instrumentations: traceInstrumentations
});

(async () => {
    try {
        await sdk.start();
        console.log('Tracing started.');
    } catch (error) {
        console.error(error);
    }
})();

// For local development to stop the tracing using Control+c
process.on('SIGINT', async () => {
    try {
        await sdk.shutdown();
        console.log('Tracing finished.');
    } catch (error) {
        console.error(error);
    } finally {
        process.exit(0);
    }
});

export default trace;

package.json
{
  "name": "instrumentationproject",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "type": "module",
  "scripts": {
    "start": "node index<EMAIL_ADDRESS>  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@opentelemetry/api": "1.4.1",
    "@opentelemetry/auto-instrumentations-node": "0.36.2",
    "@opentelemetry/exporter-collector": "0.25.0",
    "@opentelemetry/exporter-collector-grpc": "0.25.0",
    "@opentelemetry/exporter-trace-otlp-http": "0.35.1",
    "@opentelemetry/instrumentation": "^0.40.0",
    "@opentelemetry/instrumentation-express": "0.32.3",
    "@opentelemetry/instrumentation-http": "0.40.0",
    "@opentelemetry/instrumentation-pg": "0.34.1",
    "@opentelemetry/node": "0.24.0",
    "@opentelemetry/resources": "1.9.1",
    "@opentelemetry/sdk-node": "0.35.1",
    "@opentelemetry/sdk-trace-node": "1.9.1",
    "@opentelemetry/semantic-conventions": "1.9.1",
    "@opentelemetry/tracing": "0.24.0",
    "express": "^4.18.2"
  }
}

The dashboard result, the trace group name is HTTP GET instead of /test

In commonJS project, the API request path is correct on OpenSearch Dashboard.
Is anything I miss in project setting?  Thanks for your help.

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

ESM instrumentation support was added recently. You will need newer versions of the opentelemetry packages to enable instrumentation for an ESM project. After upgrading the packages, see the section right above where you linked that includes the note for the required flag to pass in (--experimental-loader=@opentelemetry/instrumentation/hook.mjs).
Core components v0.40.0
Express v32.4
Also be sure to check out the upgrade guidelines for some tips on upgrading packages. For example, note the SDK is now synchronous and no longer returns a promise.


Create prisma.yml

Description

A clear and concise summary of the change and which issue (if any) it fixes. Should also include relevant motivation and context.
Resolved or fixed issue:
Affirmation

[ ] My code follows the CONTRIBUTING.md guidelines

Sorry, I made a mistake.


Question: multiple html payload entrypoints

First of all thanks very much for your work on this.
My app currently does not have an ideal architecture, but I'm wondering if there is a way to continue to use offline-plugin regardless. It is not a SPA or app shell architecture, something I am actively working on as well.
At the point of this writing however, we can assume that the server sends static markup for the following three kinds of endpoints:
/ (homepage)
/post/:slug (article or post)
/gallery/:slug (gallery)
Service worker is at /sw.js.
I am able to capture all webpack assets and the homepage html payload with the service worker, and re-serve them when offline, with the following configuration:
new OfflinePlugin({
  // ...
  externals: [
    '/'
  ]
})

I have tried adding additional matches for the other two html payload types, as follows, to no avail:
externals: [
  '/',
  '/post/*',
  '/gallery/*'
]

I have also attempted to add these as ':externals:' to the optional property of the caches configuration. However, this also does not work as I am hoping.
Any possible guidance on this unconventional (and less that ideal) problem? I'd like to see if I can get this working, in parallel with my app shell refactoring, so that one is not dependent on the other.

Hi! I think you architecture is just fine, that's how normal websites are done.
Problem here is that offline-plugin doesn't yet support caching of dynamic URLs. Everyone actually asks about that feature, but unfortunately it isn't done.
What you can do here is add ServiceWorker.entry option and implement such caching manually. Essentially it's just listening to fetch event and responding from cache or not based on request url.

Ha ha, thanks. I'll give that a shot.

I'm digging through closed issues as well. Will continue to do so as well as learn better the internals. However if you can think of any examples at some point, please share! Thanks again.

@jeromecovington I think you may found something useful in this issue: https://github.com/NekR/offline-plugin/issues/64

Yeah, the older issues are giving me a lot to work with. I'll close this and open follow up issues if need be. Thanks.

Sure :-)


DBZ-4737 Fix error when rewinding to oldest archive log SCN

In LogMinerStreamingChangeEventSource, the startScn variable is used
as an exclusive lower bound for log mining sessions. The meaning of this
variable was a little muddled, sometimes (incorrectly) being considered
an inclusive lower bound. This PR aims to rectify that and avoid future
confusion on the matter.

It should not raise any backward compatibility concerns: the meaning of
startScn hasn't changed, I just made it more explicit. And in this
particular instance, I slightly relaxed the existing sanity check because
it was too strict before due to its interpretation of startScn as an
inclusive bound.
Op vr 11 feb. 2022 20:00 schreef Chris Cranford @.***>:

@.**** commented on this pull request.
LGTM, just one comment inline I'd like clarification on.
In
debezium-connector-oracle/src/main/java/io/debezium/connector/oracle/logminer/LogMinerStreamingChangeEventSource.java
https://github.com/debezium/debezium/pull/3230#discussion_r804927119:

           if (!isContinuousMining && startScn.compareTo(firstScn.subtract(Scn.ONE)) < 0) {

               // startScn is the exclusive lower bound, so must be >= (firstScn - 1)

Hi @chanetd https://github.com/chanetd, will this create any type of
upgrade concern for users who already have existing offsets, or will this
be seamless without any data loss?
—
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium/pull/3230#pullrequestreview-880567565,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE2BI2RKL3FFJZTDAAQCBB3U2VMFNANCNFSM5OEPBZFA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Added the ability to add components to multiple selected GameObjects

What I had to do:

Removed the check for a single selection when deciding if the "new" context menu item should be shown
Looped over the SelectedNodes property rather than just SelectedNode. This forced me to track the added nodes so that we could select them later. Selecting them inside the foreach loop would have modified the enumerable.

I checked and verified that this does not overwrite Component's if they already exist on a GameObject.

Didn't have the time for a thorough review yet, but will certainly look into your commits later!
One thing I noticed though was your usage of spaces for indentation: Please change your code to use tabs instead, as specified in the (admittedly short and unpolished) Contribution guide:

Always use Tabs for indentation, but Spaces for alignment.

Referencing issue #231 which is addressed by this.

Sorry about the spaces - my IDE was replacing tabs automatically it seems. Should be fixed now.

I've tested and merged your PR into the master branch. Unfortunately there were some issues in practice (fixed now), which you can read about in my latest commit log.
(That aside, your code is in now and your PR was overall well executed. Properly done in its own branch, small and self contained, well documented, no unnecessary stuff, sticking to the existing style. Makes it a lot easier to handle contributions.)


Navigation within page

Hi there, thank you for this amazing plugin, I found it so much easy to implement quality navigator.
I run into a situation that need to navigate to different page within a page content instead of TabBar icons. I had a look through and did not find the solution, I hope that there is a way to do that
Cheers!

@mrjcka You can do this.setState({ index: 3 }) to navigate to the 3rd page and so on.

Thanks for the answer Satyajit! I wasn't explain well my case but I have found way to work around from your answer.
For anyone who run into the issue, the case is instead of return a  directly through _renderScene (see from repository example), I rendered a view component from different file.
To navigate to different tab, I passed _handleChangeTab into the view component as below and called from inside the View component
import Home from './home'
import Settings from './settings'

_renderScene = ({ route }) => {

    switch (route.key) {
    case '1':
      return <Home changeTab={this._handleChangeTab} />;
    case '2':
      return <Settings changeTab={this._handleChangeTab} />;
    case '3':
      return <View style={[ styles.page, { backgroundColor: '#4caf50' } ]} />;
    default:
      return null;
    }
  };

Then inside the View component, when we need to navigate to different tab/view
this.props.changeTab(3)

@mrjcka Yes, that's the correct solution.


Creating demo.css file

Cleaning up demo css

LGTM.  Would be great if we could figure out how to get all the styles to show up when one clicks on 'Edit in Plunkr'

Would be great if we could figure out how to get all the styles to show up when one clicks on 'Edit in Plunkr'

If we were to put the styles into their own <file> section they would.  The downside of that obviously is that you end up having to repeat similar styles across directives.  Part of me prefers this even though it violated DRY.

LGTM

If we were to put the styles into their own  section they would. The downside of that obviously is that you end up having to repeat similar styles across directives. Part of me prefers this even though it violates DRY.

@erundle thoughts on this?

I personally hate style tags since I feel like it promotes bad practices which is why I created the CSS file but if we don't want to take this route I am OK with it.

I personally hate style tags since I feel like it promotes bad practices which is why I created the CSS file but if we don't want to take this route I am OK with it.

No, I mean putting the css for each component in <file> tags as normal css so they are displayed in plunkr.

I don't think it is worth re-creating all those styles in  just for plunkr.  Everything works in plunkr, it just isn't styled correctly.

I don't think it is worth re-creating all those styles in  just for plunkr. Everything works in plunkr, it just isn't styled correctly.

Yeah, you're probably right that DRY > styles in plunkr.  I created an issue for this (#65) in case we want to try to get these styles in plunk in the future.
@erundle can you prepend "Fixes #48: " to your commit message so the issue will close upon merge and so we have a link between the two?

Commit message updated.


Weird/scary app icon that doesn't match the apps purpose

Hello there, randomly saw this app on the f-droid starting page. Shortly looked at it, but the app icon distracts me from installing it. It's a really angry crocodile. It could be good on something like a Warez forum, but not on an app to privately share files :P.

Hi, why did you close it without even responding? :(

I didn't know if serious or joking.

I am 100% serious. I do realize that sounds silly and sarcastic, but this

looks like
which is the archenemy of the Donkey Kong games.
I would understand that you don't care (I also don't care about some user's requests that I am getting) so no problemo if you don't mind, I just found it sad you didn't respond 😄

I have no attachment to the current icon, and have no desire to seek a replacement. However, if one were provided, it's very likely I would accept without much resistance.

@howeyc @carstenhag I whipped up a little something in Photoshop just now, feel free to use it if you like it.

This is fantastic, I will use it.
Any chance you would be up for creating a "featureGraphic" that shows up in the header portion of the store listing. It's 1024x500 in size.
No pressure, I'm to receive the logo, much appreciated.


Implement CheckCommand tests

Pul request against restructure branch:
https://github.com/MarvinKlemp/deprecation-detector/pull/2


fix: iri_to_uri fails when the argument is a bytestring

This fixes the iri_to_uri method referencing the charset variable before it is ready.

fixes #2708

Checklist:

[X] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[X] Add or update relevant docs, in the docs folder and in code.
[X] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[X] Add .. versionchanged:: entries in any relevant code docs.
[X] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

The current flake8 failures also happen on the main branch, so I'm not sure if this PR is the right place to fix this.

I pushed  fixes for the flake8 errors here, but I'd be happy to split it out to a separate PR if necessary.

Python 3.12 failures are likely due to #2704.

I've hit this too. Thank you for doing this!


Change find command to allow better searches

Changed StringUtil method to check use contains() rather than equalsIgnoreCase() to improve module(s) search
Resolved test failures as a result of change

Minor nit:

Uppercase-d moduleCode variable in ModuleCode so that when user enters add c/cs2103t cr/4, the module code displayed in the GUI would be displayed as "CS2103T", for standardisation purposes

Closes #76

Codecov Report

Merging #77 into master will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #77      +/-   ##
============================================
- Coverage     73.31%   73.27%   -0.05%
  Complexity      424      424
============================================
  Files            76       76
  Lines          1274     1272       -2
  Branches        123      123
============================================
- Hits            934      932       -2
  Misses          302      302
  Partials         38       38

Impacted Files
Coverage Δ
Complexity Δ

...in/java/seedu/address/commons/util/StringUtil.java
94.11% <100.00%> (-0.62%)
7.00 <3.00> (ø)

...in/java/seedu/address/model/module/ModuleCode.java
80.00% <100.00%> (ø)
6.00 <0.00> (ø)

...el/module/ModuleCodeContainsKeywordsPredicate.java
100.00% <100.00%> (ø)
7.00 <1.00> (ø)

Continue to review full report at Codecov.

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


Update Update-SPInfoPathUserFileUrl.md

Fixed example formatting.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Update-SPInfoPathUserFileUrl.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Improve Typography documentation

Summary
Improve Typography documentation examples to make it clear h1 tags should be used semantically, how and in what ways.
💬 Description
This issue should:

Include more code examples
Document the difference between styling and semantic heading elements
Link to when you use different heading elements

💰 Use value
Make it clear to consumers that the HTML heading tags should be used alongside stlying options.

PR Merged, closing ticket :)


CDK Istio readme

Issue #, if available:
Description of changes:
CDK Istio readme with bookinfo example and visualization
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

You need to chain this doc to mkdocs.yaml file so the doc goes to public website.

Mkdocs.yaml link updated.


Tweet text captured till comma (",")

I am trying to pull older tweets for a username, It is able to fetch all the tweets. Only issue is, if the tweet text contains comma (",") it captures it till that point only and continue to next tweet.
Example:
Real tweet: Florida Highway Patrol Troopers are all en route to the Panhandle, from all across the state of Florida.
captured tweet text: Florida Highway Patrol Troopers are all en route to the Panhandle
any idea how to fix this?

you can create a code for remove next characters after "," in the .csv

in TweetManager.py locate following code
txt.replace('# ', '#').replace('@ ', '@')
and replace with this
txt.replace('# ', '#').replace('@ ', '@').replace(',', ';')
This will essentially replace all comma with semicolon. You can use any other character you wish.

The problem is that Exporter.py doesn't escape commas during saving of CSV file:
def receiveBuffer(tweets):
    for t in tweets:
        outputFile.write(('\n%s;%s;%d;%d;"%s";%s;%s;%s;"%s";%s' % (t.username, t.date.strftime("%Y-%m-%d %H:%M"), t.retweets, t.favorites, t.text, t.geo, t.mentions, t.hashtags, t.id, t.permalink)))
    outputFile.flush()
    print('More %d saved on file...\n' % len(tweets))

You can use the corrected version of GetOldTweets (with some other improvements) from https://github.com/Mottl/GetOldTweets3
or use pip install GetOldTweets3 to install it with pip


support proxysql (sidecar mode)

app ---unixsock--> proxysql ---tcp--> tidb

ruby-1  | DEPRECATION WARNING: You didn't set `secret_key_base`. Read the upgrade documentation to learn more about this new config option. (called from env_config at /usr/local/bundle/gems/railties-5.1.7/lib/rails
/application.rb:247)
ruby-1  | Started POST "/graphql" for <IP_ADDRESS> at 2024-02-27 03:24:04 +0000
ruby-1  |    (0.8ms)  SET NAMES utf8mb4,  @@SESSION.sql_mode = CONCAT(CONCAT(@@sql_mode, ',STRICT_ALL_TABLES'), ',NO_AUTO_VALUE_ON_ZERO'),  @@SESSION.sql_auto_is_null = 0, @@SESSION.wait_timeout = 2147483
ruby-1  |
ruby-1  | ActiveRecord::StatementInvalid (Mysql2::Error: Max connect timeout reached while reaching hostgroup 1 after 10000ms: SELECT table_name FROM information_schema.tables WHERE table_schema = database() AND ta
ble_name = 'schema_migrations' AND table_type = 'BASE TABLE'):
ruby-1  |


Introduce new dev branch

Per @niktek's suggestion, we need a branch between master and feature branches. This will allow hotpatching on master if we need it. We start simple and build up. Something like:

master - as is, we'll build/package on update. Manual for now, automated later with CI/CD.
dev (or staging) - we introduce this as the proceeding branch. I don't think we need both yet.

General idea is dev will serve as our merge target. All PRs, etc target this. Updates from dev are merged into master when we're ready to deploy to production. We won't get any more complex than this until we need to.
This will come with updated guidance on the README and Contribution guidelines.
I welcome feedback on this, but expect it to appear tomorrow (US/CST time)

I know these are arbitrary names and opinionated, but my 2 cents (Dollarydoos !).
master never made sense.  We literally use the branch command all the time and branches come off a trunk
We develop in our feature branches, but then attempt to merge multiple features into the staging area.
So my vote is for trunk and staging with all feature branches to originate from staging and staging being the only one that merges to trunk to be tagged as a release.

Ha, <3 Dollarydoos.
Sounds like you've used Subversion in the past?
http://guides.beanstalkapp.com/version-control/branching-best-practices.html
I may be showing revealing some ignorance on my end but this is the first I've heard of this paradigm! Makes the UX part of my brain start throwing some red flags on whether casual contributors will understand this.
As with many things in Skeleton, my inspiration here is Mantine:
https://mantine.dev/pages/contributing/
https://github.com/mantinedev/mantine/branches
Also I'm lazy, so typing dev is shorter :)

Heh, try CVS and then svn shudder
Nah, mainly from Github/Gitlab Flow paradigms:
https://www.gitkraken.com/learn/git/best-practices/git-branch-strategy
https://www.flagship.io/git-branching-strategies/
I do like having that safety net of merging back into staging before some CI/CD shoots it straight out to S3/GitHub Pages.  Our current situation right now seems like a good example - we have docs with A11y content updates, but also a mass rename of all docs pages due to SK.next.409 and the actual Skeleton lib updates that affect the doc functionality in two separate feature branches, but if we were to merge them to trunk before we release the actual package to npm, that wouldn't be cool.  And considering that the testing covers looking at the same pages, it would be a waste of time to do it once for each feature branch to verify when it could be all merged to staging for a final single look over before releasing it in tandem with the npm package.
But then again, we don't have CI/CD yet, so keeping it as simple as possible is fine by me too!

That's interesting. Yeah I think as we continue to grow things will evolve more and change. Given the limited staff and resources we're probably best to go with the simplest option. So we'll use the dev branch as mentioned in the OP. But I would like to read more into this going forward. Thanks for sharing Nik!

The branch is live and includes various updates to the documentation. This includes details for targeting the dev branch for all PRs going forward. I'll echo this info on the Discord as well.


Calling start() seems to exit the program

Alright, this seems pretty strange. I've tried both my own program, and the example program from the documentation. As far as I can tell, the crate just doesn't work. Creating a new Daemonize does seem to work. PID files do get created. But when I call start(), nothing happens.
I tried using a match statement that would print different messages depending on if start() returned an Ok or an Err. What did it print? Absolutely nothing. It's as if the program just cleanly exits when start() is called.
Additionally, the closure specified with privileged_action() doesn't seem to be getting called.
Either I'm right and there's a problem, or I'm wrong and I'm completely misunderstanding how to use this crate. Hopefully you can tell me which one it is.

I'm seeing this also.  Does daemonize perhaps require that it be run as root?

Yes, in the process of daemonizing, the original (foreground) process exits, and a copy of it runs in the background. The background process can't print anything because it is not attached to the terminal -- if it was, it wouldn't be a background process. The foreground process can't keep running because then you would have two instances of your program running, which is probably not what you want.
See:
https://github.com/knsd/daemonize/blob/b617c78abc977d5f1d2b17e0dd3bb6c104701287/src/lib.rs#L347


Add first 3 test cases for Project Sharing

This PR is adding 2 Smoke and 1 Sanity tests for Project Sharing feature coming in v1.27:

ODS-2194
ODS-2201
ODS-2202

TC and KW documentation coming in next commit

Should we fix the Robocop alearts ?

done!

First PR test: 1752. Almost OK, there is a minor issue with a check. Fixed and a new run is going on.
Second PR test: 1753 RUNNING


Needs a dedicated man page

So, pipenv ships with a man page that can be opened with pipenv --man, but that man page has a few issues regarding usability, because it is just built from the sphinx docs.

I don't need any information about how to install pipenv. I already have it. (I don't need user testimonials either.)
It doesn't list the general cli usage at the top, which is one of the most useful sections.
The docs have a couple of links, which don't convert to a man page.
Example files are good, but more useful at the bottom
More, that I don't care to list right now.

Basically, it's not really a man page. It's a user guide in form of a man page.
That said, it's still good that there is something you can access (without an internet connection), but in the current state it's pretty lackluster. Pipenv needs a dedicated man page imho.

@FichteFoll I would agree.  It is an issue we should tackle, but not one that is a priority right now.  Anyone want to submit a PR? :)

that's not how pip works

What does this have to do with pip?

we can't ship a proper man page that works with man, i've looked into it
heavily.
we can improve the "man" functionality, but i'd rather just remove it.
On Tue, Nov 21, 2017 at 8:30 PM, FichteFoll<EMAIL_ADDRESS>wrote:

What does this have to do with pip?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kennethreitz/pipenv/issues/1100#issuecomment-346215330,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHUVTi5COoAUjf4Qy3NIcRgt_XFZ5WSks5s43lLgaJpZM4Qjk5U
.

wouldn't we have to do distro packaging for actual man pages? I've made them before but it was a pain

I was mainly referring to the pipenv --man functionality here, not requesting that the man page is added to the system's database. That would indeed be a task for distro packaging (and certainly not hard for Arch, but I don't know about others).

@kennethreitz I didn't mean we should create a man page, I remember us trying to get it to install a man page and we couldn't.  I just thought about changing the pipenv --man link to look more like a traditional man page instead of the sphinx docs.  As I said though not a priority right now :)

i dont’ think the current —man is harmful

I don't think the issue is about having --man... I think it's more the formatting, content, and sequence of information.
I read this more as a request for improvement of the existing --man output.

We don’t know how to answer the request. If you do, do it for us!

I picked up some troff/groff syntax and proper man page structure over the weekend. Would you prefer writing in groff directly or would you rather have something that compiles to it, like a pod for example (other suggestions welcome).

Just a note that I started working on this, but will probably take another 2 weeks to finish because of a vacation.

So, initially I thought of having everything in a single man page, but eventually I realized that the number of sub commands and their options would become quite cumbersome to maintain and read in a single file. Thus, I propose to have a separate page for each command and one that mentions them all, along with some general usage considerations, examples, file explanations and environment variables. The only "problem" is that this doesn't work well with the --man flag currently. I suppose an argument could be added for that to open a subcommand's page, though.
Would that be okay?

I don’t think there’s anything wrong with big man pages, it’s pretty common. And it’s not that common to split things up. As a user of man pages I’d probably find that annoying


keepalived-vip: fix deprecated NodeLegacyHostIP

Replace NodeLegacyHostIP with NodeInternalIP.  This is required for
keepalived-vip to work on bare metal, since it has no cloud provider to set
ExternalIP on each node resource.

This change is

CI failure is unrelated and fixed by #2707

/retest

This fix worked perfectly against my k8s 1.7 cluster.

@barclaac I'd recommend using https://github.com/aledbf/kube-keepalived-vip instead of the version in contrib.  There is no one in the OWNER file for this project that actually does reviews and @aledbf is the original author and is maintaining his version.

/lgtm

@aledbf If you want to be part of the owners file for keepalived-vip, feel free to send a PR


GCE - Fails on yum repos failing on bastion host

./gcloud on fedora ends up on this error:
Warning: Permanently added 'compute.3888108791522642653' (ECDSA) to the list of known hosts.
ansible-config.yml                                                                                100%  783    13.8KB/s   00:00
Loaded plugins: search-disabled-repos
There are no enabled repos.
Run "yum repolist all" to see the repos you have.
To enable Red Hat Subscription Management repositories:
subscription-manager repos --enable
To enable custom repositories:
yum-config-manager --enable
Connection to <IP_ADDRESS> closed.

issue seemed to be caused by the fact that the gcloud script doesn't handle subscription-manager passwords with special characters. Since this seems to halt the script midway through, it must cause cascading issues with the rest of the setup. Anyhow, pull request submitted that resolves the issue and script seems to complete fine now.