Don't override default browser shortcuts

This is a...

[ ] Feature Request
[x] Bug Report

Problem:
When I press Ctrl+F, I expect native search dialog for the current page.
Now it focuses on whole-docs search input.
The same result I can get via Google Search site:https://kubernetes.io in another tab if I want.
It's absolutely not user-friendly to override Ctrl+F to search fast some information on a page.

Sorry. Looks like my local keymap config error.


Can't get file upload to work on Heroku

If I run my backend server locally, FineUploaderTraditional does the job perfectly because it is able to find the file in the temporary path.
However, once I push my app to Heroku, it is not able to find the file at the temporary path that look likes this /tmp/plug-1496/multipart-673466-295945-1
I am running an Elixir/Phoenix app.
This is my configuration
  const uploader = new FineUploaderTraditional({       options: {         chunking: {           enabled: true,           concurrent: {             enabled: true           },           success: {             endpoint: UPLOAD_FILE_ENDPOINT           }         },         request: {           endpoint: UPLOAD_FILE_ENDPOINT,           customHeaders: {             'Authorization': 'Bearer ' + token,           },           params: {             roomUuid: roomUuid           }         }       }     })
What might have caused this?

Turned out I have to copy over the temporary file to its destination. I should not simply rename it.


Fix conditioning to allow speech in-filling

There are a few tweaks to conditioning needed to allow speech in-filling as described in the paper to work correctly.

During training, use the un-noised target as the conditioning (aka X_ctx in the paper) instead of the X_t value for the previous timestep in the flow. Without this, the conditioning is noisy and the network can't correctly use the full context to predict the flow for the in-filling portion.

Remove the MLM-style training objective and only use fractional masking for training efficiency, since the target is the final step of the flow based on the X_t intermediate step and not an unmasked version of the input.

Don't mask the input X_t of the flow, since that's basically throwing away information sampled at previous timesteps of the ODE. The network will learn to sample X_ctx and generate in-filled speech where appropriate based on the conditioning mask.

With these changes, I was able to train a model that supports speech in-filling with style transfer at inference time! 🚀

@lucasnewman man... slow 👏

@lucasnewman usually, it is "ability to code", "understand research", "able to tinker and train working models", choose 2. you seem to be headed towards having all 3

@lucasnewman really appreciate your bringing this repository over the finish line. this will be helpful for countless papers down the line

@lucasnewman
Thanks for conversation. I'm sorry to bother you, but could you explain codeline 993?
"cond = default(cond, target)"
I think target is u_t (=x1-x0). x1 is gt-mel or acoustic token, x0 is random noise.
But x_ctx in the paper should be masked gt-mel. (Then, cond is not None in your training code?)


--project-dir with relative paths?

Describe the bug
--project-dir doesn't use relative paths, and I got confused given the error message
Steps To Reproduce
Run a project in a child path; say we have a DBT project in a path called sql under the current one:
$ dbt run --project-dir sql
Running with dbt=0.17.0
Encountered an error while reading the project:
  ERROR: Runtime Error
  no dbt_project.yml found at expected path sql/dbt_project.yml
Encountered an error:
Runtime Error
  Could not run dbt

$ dbt run --project-dir (pwd)/sql
Running with dbt=0.17.0
Found 4 models, 0 tests, 0 snapshots, 0 analyses, 147 macros, 0 operations, 0 seed files, 0 sources

I was doubting my sanity for a second with no dbt_project.yml found at expected path sql/dbt_project.yml
Expected behavior
Use relative paths, or if this is deliberate, don't accept relative paths
The output of dbt --version:
installed version: 0.17.0
   latest version: 0.17.0

Up to date!

Plugins:
  - bigquery: 0.17.0
  - snowflake: 0.17.0
  - redshift: 0.17.0
  - postgres: 0.17.0

The operating system you're using:
MacOS
The output of python --version:
Python 3.7.7

hey @max-sixty - this tripped me up too! See here: https://github.com/fishtown-analytics/dbt/pull/2534#issuecomment-643272603
Let's definitely make relative paths work for --project-dir at some point in the future. This is a pretty tricky part of the codebase - dbt does lots of magic to support running dbt run from a subdir of a dbt project (eg. models/), so it might be a little involved to get this working well. I do think it's worth doing though!

Fixed in #2534


Onnx install issues on newer Python versions

See comment here: https://github.com/onnx/onnx/issues/4376#issuecomment-1237098568
Maybe add some install commands to README

I think #10 solves this. I don't run into any problem with onnx install.


Long messages break the bot

If very long messages are present in the chatlogs that are send to openai for processing, openai api throws error, but it is not caught. The bot does not repspond.

Yes we need some OpenAI error handling when tool selection fails or general the general API is down.  Next we need to be smarter about memory and look for the 2000 character limit in Discord.
Part of the issue is that we added verbose to the persona steering cause his messages were so short.  Now it's biting us since people have been engaging him in longer things and asking for more complicate replies.

I've got something in place to truncate messages at this point


Departure and Return Time

Added flags for departure and return flight times to be used as parameters for the form.
Identified a number of possible improvements which have been documented in both the readme file and inline comments.
Added attributes to the existing argument parsing code.

Hey Kyle,
Many thanks for your contributions. I'm going to close this request, since it seems that you've made more recent changes in #15. I will review those.


Bump the aufs image do 4.x and rename it to docker

Blocked for now. Waiting for a 4.x aufs branch (http://aufs.sourceforge.net)

fixed by https://github.com/scaleway/kernel-tools/pull/162/files ?

Yep :)


Enable running tool on linux

The executable name used on linux was yarn.cmd. This caused an
"Exec format error" when running the tool on linux machines.
This change uses the current platform to decide which executable
name to use, and uses "yarn" on linux systems, otherwise "yarn.cmd"
Reproduced the "Exec Format Error" on Windows Subsystem For Linux (WSL),
using the following cake script:
#addin "nuget:?package=Cake.Yarn&version=0.4.6"
Task("Default").Does(() => { Yarn.Install(); } );
RunTarget("Default");

This script works on windows without any changes.
Verified that the change works correctly on both Windows and Linux.

This should fix #32

Thanks!


[Mgmt SDK] Testproxy migration

https://github.com/Azure/azure-sdk-for-python/issues/31399

/check-enforcer override


added query strings to search for spell levels, classes, and the school

What does this do?
you can query string search for spells based on their spell level and the classes that can use it and the school of magic it is from.
How was it tested?
pulled down the api and executed query strings with the spells api
Is there a Github issue this is resolving?
no it's new functionality and also intellectual curiousity
Here's a fun image for your troubles

@AnonymousICT, looks like CI tests failed. Also, if you're adding new query patterns, can you add Tests/Integration Tests for them as well?

@AnonymousICT I'm also pretty sure you'll need to update the shape in here in order to be able to query against that.


Cannot update modal with multi static select menu with initial options from different option groups with an additional option from a different option group

This is a spin out issue from a follow-up comment from @nikhiltadikonda in #1496.
Given a modal with a block containing a multi select static menu containing options from different option groups, and the menu having initial_options selected from different option groups, such as:
{
  type: 'input',
  block_id: 'interests_select_block',
  label: {
    type: 'plain_text',
    text: 'Label here',
  },
  element: {
    type: 'multi_static_select',
    action_id: 'my-action-id',
    placeholder: {
      type: 'plain_text',
      text: 'Select one or more interests...',
    },
    option_groups: [
      {
        label: {
          type: 'plain_text',
          text: 'DOMESTIC',
        },
        options: [
          {
            text: {
              text: 'Baking',
              type: 'plain_text',
            },
            value: '2',
          },
        ],
      },
      {
        label: {
          type: 'plain_text',
          text: 'OUTDOOR_RECREATION',
        },
        options: [
          {
            text: {
              text: 'Hiking',
              type: 'plain_text',
            },
            value: '1',
          },
          {
            text: {
              text: 'Cycling',
              type: 'plain_text',
            },
            value: '3',
          },
        ],
      },
      {
            label: {
              type: 'plain_text',
              text: 'INDOOR_RECREATION',
            },
            options: [
              {
                text: {
                  text: 'Board Games',
                  type: 'plain_text',
                },
                value: '4',
              },
              {
                text: {
                  text: 'Painting',
                  type: 'plain_text',
                },
                value: '5',
              },
            ],
          },
    ],
    initial_options: [
      {
        text: {
          text: 'Hiking',
          type: 'plain_text',
        },
        value: '1',
      },
      {
        text: {
          text: 'Baking',
          type: 'plain_text',
        },
        value: '2',
      },
    ],
  },
}

..if you configure a bolt app to, for example, listen on the view submissions to this view and call views.update on the view modifying the above block to add an option from a separate option group not in the initial initial_options to the initial_options, the view.update API will respond with a 200 OK, but the modal will not update the static select menu (while updating other parts of the modal if applicable).
In the above blocks, there are three option groups: domestic, indoor and outdoor recreation activities. The initial options contain an option from the domestic and indoor option groups. In the example app below, the views.update call adds an option from the outdoor recreation group, but the initial option addition does not get updated in the view.
Here is a full app reproducing the behaviour (requires adding a /post slash command to your app, and triggering the modal using this slash command):
const { App } = require('@slack/bolt');
const megaview = {
  type: 'modal',
  // View identifier
  callback_id: 'view_1',
  title: {
    type: 'plain_text',
    text: 'Modal title'
  },
  blocks: [
    {
      type: 'input',
      block_id: 'interests_select_block',
      label: {
        type: 'plain_text',
        text: 'Label here',
      },
      element: {
        type: 'multi_static_select',
        action_id: 'my-action-id',
        placeholder: {
          type: 'plain_text',
          text: 'Select one or more interests...',
        },
        option_groups: [
          {
            label: {
              type: 'plain_text',
              text: 'DOMESTIC',
            },
            options: [
              {
                text: {
                  text: 'Baking',
                  type: 'plain_text',
                },
                value: '2',
              },
            ],
          },
          {
            label: {
              type: 'plain_text',
              text: 'OUTDOOR_RECREATION',
            },
            options: [
              {
                text: {
                  text: 'Hiking',
                  type: 'plain_text',
                },
                value: '1',
              },
              {
                text: {
                  text: 'Cycling',
                  type: 'plain_text',
                },
                value: '3',
              },
            ],
          },
          {
            label: {
              type: 'plain_text',
              text: 'INDOOR_RECREATION',
            },
            options: [
              {
                text: {
                  text: 'Board Games',
                  type: 'plain_text',
                },
                value: '4',
              },
              {
                text: {
                  text: 'Painting',
                  type: 'plain_text',
                },
                value: '5',
              },
            ],
          },
        ],
        initial_options: [
          {
            text: {
              text: 'Hiking',
              type: 'plain_text',
            },
            value: '1',
          },
          {
            text: {
              text: 'Baking',
              type: 'plain_text',
            },
            value: '2',
          },
        ],
      },
    },
  ],
  submit: {
    type: 'plain_text',
    text: 'Submit'
  }
};

const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  socketMode: true,
  appToken: process.env.SLACK_APP_TOKEN,
  developerMode: true,
});

app.command('/post', async ({ ack, say, body, client, logger }) => {
  console.log('post coming in');
  // Acknowledge the command request
  await ack();
  try {
    // Call views.open with the built-in client
    const result = await client.views.open({
      // Pass a valid trigger_id within 3 seconds of receiving it
      trigger_id: body.trigger_id,
      // View payload
      view: megaview
    });
  }
  catch (error) {
    console.error(error);
  }
});
app.view('view_1', async ({ ack, body, view, client, logger }) => {
  // Update the view with a new initial_options in it from a different option group
  const updatedview = { ...megaview };
  updatedview.blocks[0].element.initial_options.push({
    text: {
      text: 'Board Games',
      type: 'plain_text',
    },
    value: '4',
  });
  updatedview.title.text = 'Updated modal';
  await ack({
    response_action: 'update',
    view: updatedview
  });
});
(async () => {
  await app.start();
  console.log('⚡ Bolt app started');
})();

Note that the title of the modal in the update call gets updated, so this issue seems to be isolated only to updating the static option group select menu's initial options.

I have filed this with the Block Kit team internally, will keep y'all posted as I hear updates.

@filmaj Thank you for looking into this! I'll be waiting for an update on the fix!

@nikhiltadikonda FYI, the team is working / figuring out a fix. It looks to be a client-side caching issue. One identified workaround thus far, which may work for you, is to remove the block_id of the enclosing block. That seems to force a refresh / cache bust on the client side.
As I hear more about progress on this, I will keep this issue updated.

I get around this by just adding the date/time in milliseconds to the end of the block_id field with a : between the front and back like this
"my_block_id:1691501956868"
and then you can just split the block_id to get the original value.


Need new Korean README with new nimbix trial updates

@hjjo can you update the translated README?

@markstur I've done it :-)

Sorry @hjjo but I just updated the README again. This time we are just cleaning up some new naming and README standard stuff.  This is not as important as the nimbix steps, but it'd be nice to be in sync.


iphone decrption failed

Hi,
Im using ios 17.1.2, and got this issue, could you please help?
Thank you!
Abstract
cant sync on iphone
Expected behaviour

Synchronisation ends with the message Replication completed
Everything synchronised

Actually happened

"Error:Encrypted data corrupted!"
Decryption failed

Reproducing procedure

Configure LiveSync on 2 pcs, both works fine
Open setup url on iphone, nothing happens
set up iphone manually, and get above error.

 I'm also new to the LiveSync plugin.

Have you set up your own HTTP and CouchDB server instead of using Fly.io or IBM Cloudant?

The latest LiveSync plugin is v0.21.5<-v0.19.23 update. But I don't think it matters much this time.

I suspect the SSL configuration may be causing issuees because you can sync between PCs, but not from the iPhone only.
I noticed that the certificate has been set up. Are there any issues with Check database configuration?
Settings for Self-hosted LiveSync.→Remote Database configuration →Check database configuration →Press Check button

As a beginner, this is all I can suggest. I apologize for not being able to help you further.

Hi. I'm also new to the LiveSync plugin.

Have you set up your own HTTP and CouchDB server instead of using Fly.io or IBM Cloudant?
The latest LiveSync plugin is v0.21.5<-v0.19.23 update. But I don't think it matters much this time.
I suspect the SSL configuration may be causing issuees because you can sync between PCs, but not from the iPhone only.
I noticed that the certificate has been set up. Are there any issues with Check database configuration?
Settings for Self-hosted LiveSync.→Remote Database configuration →Check database configuration →Press Check button

As a beginner, this is all I can suggest. I apologize for not being able to help you further.

Hi,
1.Yes, ive set up my own HTTP and CouchDB server
2.Im using  v0.21.5
3.There isnt a "check" button in "remote database configuration.
I apology for the last reply and thank you for your suggestions and willingness to help.

Sorry for the delay.

The following screen appears.

Settings for Self-hosted LiveSync.→Remote Database configuration →Check database configuration →Press Check button

Execution Result

That is all. I wish you good luck.

Yes, I checked and got the same results as you do. Ive tried remove enverything and reinstall, but it doesnt work.
Thank you.

Sorry for being late!
I know that you have configured so, however, would you mind if I ask you to check again if both of your passphrases are the same?
And, also check the use dynamic iteration count is disabled.
However, I am wondering why the set-up URI was not working well.
Has the lockdown mode been enabled by any chance?

Sorry for being late! I know that you have configured so, however, would you mind if I ask you to check again if both of your passphrases are the same? And, also check the use dynamic iteration count is disabled.
However, I am wondering why the set-up URI was not working well. Has the lockdown mode been enabled by any chance?

Hi,
Im sure passphrases are the same.I forgot if ‘use dynamic iteration count’ is disabled.
But i managed to fix this by reinstall and delete all local files
Thank you for your reply.

Sorry for the inconvenience, I am very relieved to hear that the issue has been solved. Thank you for your reporting!


CompactBinary Protocol V2 doesn't work in C#

I updated the Serialization sample to use CBV2 and now it throws a runtime exception. I've seen similar errors with other IDL, but it appears there's some amount of corruption going on with V2.
Code (program.cs):
var writer = new CompactBinaryWriter<OutputBuffer>(output, 2 /* used to be 1 */);

// The first calls to Serialize.To and Deserialize<T>.From can take
// a relatively long time because they generate the de/serializer
// for a given type and protocol.
Serialize.To(writer, src);

var input = new InputBuffer(output.Data);
var reader = new CompactBinaryReader<InputBuffer>(input, 2 /* used to be 1 */);

Exception:

System.IO.InvalidDataException was unhandled
HResult=-2146233087
Message=Invalid type BT_UINT64, expected BT_STRING
Source=Bond
StackTrace:
at Bond.Expressions.ThrowExpression.ThrowInvalidTypeException(BondDataType expectedType, BondDataType actualType)
at lambda_method(Closure , CompactBinaryReader1 )        at Bond.Deserializer1.Deserialize[T](R reader)
at Bond.Deserialize`1.From[R](R reader)
at Examples.Program.Main() in c:\Users\kylemc\Documents\Visual Studio 2013\Projects\serialization\program.cs:line 29
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:

Yes, CBv2 writer is not support in C# at the moment. Reader is supported.

When do you think the CBv2 writer will be supported?

I don't have a specific date at the moment.
For context, what makes CBv2 different from other protocols is that is requires double pass during serialization in order to calculate lengths of nested structs. That's why it requires some additional infrastructure that other protocols don't. That is also why not that many people have been using it (the double pass is an extra cost) so it hasn't been on top of the priority list.


Add PITS Global Data Recovery Services to the list of adopters

What this PR does / why we need it:
This pull request adds new entry in the list of adopters
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 #
N/A
Special notes for your reviewer:
I wish every reviewer a wonderful September with full of happiness!
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: The Boy Scout Rule was considered and applied if needed
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[x] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to the kubevirt-dev was considered

Release note:

N/A

@benjx1990 Nice!
Does this mean that KubeVirt VMs can be backuped with your solution?
/approve

/unapprove
/hold

Awesome, thank
/unhold
/approve
/lgtm

/ok-to-test


No such URL http://central.maven.org

It says in the readme to download the atlasmap jar from a non-existent website: http://central.maven.org

Thanks for reporting - fixed


Make compatible to latest AngularJS Version

The old version is making problem with my latest projects. I think it will be good to change the version of angular from 1.2.10 to minimum 1.3.4.

Hi @asim-qburstian, I just relaxed the dependency requirement from "1.2.10" to "^1.2.10" so "1.3.4" should be covered as well. Let me know if you still encounter any other problems.

Thanks. I will let know if there is any other problem.


[dv] Exclude FSM transitions that can only happen on reset

This flow applies to all blocks that runs with VCS
Need to enable xcelium for this too
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

This is the FSM coverage before this update. (only run a smoke test)
There are many uncovered in Column 8 (other state -> ResetSt)

This runs with the update. Column 8 is all excluded.


Fix card inference bug and support chained cardinality restriction

There is a soundness bug in card inference where we only look at the
rightmost element in the path. So if a filter is on .foo.name, we
check if name has an exclusive constraint on the subject object,
which is wrong.
To avoid this breaking code that relied on this in an unsound way
but could be sound, this is paired with implementation of chained
cardinality restriction on filters.
That is, make select Foo filter .bar.baz = 'key' infer cardinality
AtMostOne if bar and baz both have exclusive constraints.
Previously, it would have been necessary to write
select Foo filter .bar = (select Bar filter .baz = 'key') if you wanted
cardinality One.
Closes #3566.

Oh, though it now occurs to me that improving cardinality inference (to view more things as single) is also a compatibility hazard, since it changes the output shape...

It is, but not fixing this is also bad.

Cherry-picked for 1.2


Keynotfound exception for dialogstate or accessors' states

Whenever I run any dotnet bot samples that involves bot accessors, I get "Keynotfound" exceptions eg:

This was from the multilingual bot.
Any solutions?

Have you put your translation key into the bot?

Yes I have put the translation key in the appsettings file.

@tdurnford, can you please assist?

@piplupnoil
Are you just opening the sample, adding your translation key from your Azure Cognitive Service, building and running the project?

Yes that is what I'm doing

@piplupnoil
What version of the SDK are you using, are you trying to run the most up to date samples, and what platform are you running the samples on (Windos, MacOS, or Linux)? Also, could you provide a stack trace for your issue?
Thanks

@piplupnoil
After looking into the source code, it looks like the error you are seeing is a designed exception. If the key is not present in the dictionary, it will raise the error, and when it is caught, it signals IPropertyAccesor that a default value should be computed. You can take a look at the code here for more details.
Thank you @EricDahlvang for your direction.

Closing as by design, thanks @tdurnford. @piplupnoil, if this does not address your question please let us know.


fmt: feature request: add Error, which corresponds to Errorf as Print corresponds to Printf

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/alandaws"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.9/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.9/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/06/jjq25lws0cbcxv37ns0hb_mm0000gn/T/go-build733634811=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
What did you do?
Nothing, feature request
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
n/a
What did you see instead?
n/a
A common use of fmt.Errorf is to wrap a generic error returned from an upstream library so you can see where it occurred in your code:
x, err := something.DoThing()
if err != nil {
    return nil, fmt.Errorf("Failed to do thing here: %s", err)
}

Concatenation in other variadic functions in fmt seems to be slightly faster than processing format strings, and in the case of wrapping errors, needs less syntax.
I could write:
x, err := something.DoThing()
if err != nil {
    return nil, fmt.Error("Failed to do thing here: ", err)
}

The differences are only marginal, but it does fit with the pattern of a lot of the other functions in fmt, one that's just variadic and one that takes a format string.
Using Dave Cheney's errors.Wrap is possibly a better approach altogether: https://dave.cheney.net/2016/04/27/dont-just-check-errors-handle-them-gracefully
Do people think a fmt.Error function is valuable?

The advantage of fmt.Error over errors.New seems very minor to me.  Just change , to +.

You do have to also change err to err.Error(), but I agree that is equivalent, and only slightly longer.

It's already a little confusing that fmt.Errorf returns an error and log.Errorf prints a line of text to stderr. And .Error means other things in other APIs. Let's not compound this by adding fmt.Error here.

Note that you can already do errors.New(fmt.Sprint(...)) if you really want to avoid the format string.


Figure out why pull approve isn't working and reinstall it

Pull approve isn't acknowledging that people have reviewed branches.  @tfenne has disabled it temporarily until we can figure it out.

It might be because they are changing how public repos are handled...


Problem scanning QR Code

When scanning the QrCode in the terminal in all 6 attempts it does not connect. Tested on normal whatsapp and whatsapp business.
What can I do to fix this?

Solved, just give a full restart on the server :)

we work fine try small window

Ao escanear o QrCode no terminal nas 6 tentativas ele não se conecta. Testado no whatsapp normal e no whatsapp business.
O que posso fazer para esclarecer isso?
@WesleyMarinho
In which environment are you testing the application?

it not work form first time my be in 5 or  7 try or 10

did you solve it friend?


Type definition of the app.all client.

What version of Hono are you using?
4.5.1
What runtime/platform is your app running on?
Deno 1.45.3
What steps can reproduce the bug?

Clone https://github.com/nakasyou/hono-client-app-all
Run deno run --allow-net main.ts
Console shows "Hello ALL!"

What is the expected behavior?
TypeScript should throw the error because there is no method: ALL, so $all is invalid.
What do you see instead?
No response
Additional information
Related: https://github.com/orgs/honojs/discussions/3143
There is the runtime that runtime that can't fetch incorrect methods.

Hi @nakasyou
This is a known issue, but like a bug should be fixed. Thanks.


snapshots: return error if readSnapshot fails

Signed-off-by: Wei Fu<EMAIL_ADDRESS>

Codecov Report

Merging #3819 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3819      +/-   ##
==========================================
+ Coverage   41.98%   41.99%   +0.01%
==========================================
  Files         130      130
  Lines       14577    14577
==========================================
+ Hits         6120     6122       +2
+ Misses       7543     7542       -1
+ Partials      914      913       -1

Flag
Coverage Δ

#linux
45.44% <0%> (+0.01%)
:arrow_up:

#windows
36.94% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

snapshots/storage/bolt.go
55.74% <0%> (ø)
:arrow_up:

snapshots/btrfs/btrfs.go
58.29% <0%> (+0.89%)
:arrow_up:

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 2c1d088...843423e. Read the comment docs.


refined-github on brave

I am using brave browser on Pop!_OS. I can't see the  features (e.g. download folder option etc.) - rather any feature -  while using the extension. I haven't added the personal token (I don't think it is needed for this feature).
Has anyone used this extension on brave and got it to work properly?

Do we need to login to our profile to make it work? I have now added the access token as well (without logging in). Still no signs of download option..

Some features work when you're logged out but we don't support that officially.  Can you post a screenshot of this repo after enabling the extension? Any errors in the console?

If you just need to download folders, you can use https://download-directory.github.io/ directly. RG only adds a link to it

Downloading folders was just one example - other features don't work. I guess I'll use it while logged in.
Thanks.


Synchronize the “administrators” list

Currently, the list of administrators is present in 3 places:

the LDAP group sudo;
Ansible's user data;
the Github “Administrators” team.

I suggest we resync them (by hand, as appropriate) and make the Github team public (the other lists are public anyhow).
Here are the impacted users:

[x] @theepicsnail (dropped by request)
[x] @notnamed (dropped by request)
[ ] cbrooks a.k.a. @connerbrooks (not in the password store)
[ ] viaken a.k.a. @dpflug (not in the password store)
[ ] @deleriux2 (not in Ansible)
[ ] radicalcakes a.k.a. @thenormalsquid (not in Ansible, LDAP or Github)
[ ] @tsoporan (not in Ansible nor Github nor LDAP)
[ ] gscott (not in Ansible nor Github)
[ ] @SaidinWoT (not in Ansible nor LDAP)
[ ] @scjudd (not in Ansible nor LDAP)

I took the liberty of removing notnamed, tsoporan and radicalcakes from the group sudo, since there is no way to contact them (not on Github or IRC).
NOTE: What I'm suggesting here is a one-off, manual thing.  No automation at all,

I think we should do that because:

there should be a clear set of people who have admin access to the infrastructure;
people who are in one of those lists but not all (for historical reasons) are de facto prevented from contributing, and should have all the access needed (if they still wish to contribute);
this makes the whole situation more transparent for users.

I think it should not be automated because:

the set of admins changes infrequently;
the process for adding a new admin is already documented;
automation failure can have catastrophic consequences there.

@hashbang/administrators Follow-up from the discussion in #opers, since it devolved in fairly unrelated directions.

NOTE: What I'm suggesting here is a one-off, manual thing. No automation at all.

I approve, then.

So, those people aren't in Ansible or in the Github team:

[ ] @deleriux2 (not in Ansible)
[x] radicalcakes (not in Ansible nor Github)
[ ] viaken (neither in Ansible nor in Github)
[ ] @theepicsnail (not in Ansible)
[x] notnamed (not in Ansible nor in Github)
[ ] cbrooks (not in Ansible nor Github)
[x] tsoporan (not in Ansible nor Github)
[ ] gscott (not in Ansible nor Github)
[ ] @dpflug (not in Ansible nor LDAP)
[ ] @scjudd (not in Ansible nor LDAP)

I took the liberty of removing notnamed, tsoporan and radicalcakes from the group sudo, since there is no way to contact them (not on Github or IRC).

I took the liberty of removing notnamed, tsoporan and radicalcakes from the group sudo, since there is no way to contact them (not on Github or IRC).

Huh? why can't we contact @tsoporan?

@daurnimator It wasn't autocompleting, so I assumed it was non-existing  :-(

@daurnimator Do you know if notnamed was @notnamed?

Hello yes that notnamed is this notnamed, but you can feel free to sync me out of sudo, Ansible, and Github.

@notnamed Ok, thanks for the confirmation.

I should be on this list. I believe.

@SaidinWoT You already had a pending invite to the “administrators” group on Github.
You can send a PR against admin-tools to add yourself there, and you need to tell me what is your shell user, to add it to the sudo group.

I should be on this list. I believe.

@thenormalsquid  Same punishment as @SaidinWoT : PR to admin-tools  :grin:
We should definitely keep /somewhere/ the mapping from shell name to Github username (and IRC nick?)

@connerbrooks @dpflug Just realised you are missing in the password store too.
Add your key to the list (preferably with a signed commit) and I will re-encrypt the pass db.

@hashbang/administrators Do you think we should set a cut-off date where we remove privileges from people who haven't answered whether they want to keep being part of the admin team?

Until the end of May seems fine.

@ChickenNuggers ACK.  Fine for me

@deleriux2 @scjudd Ping?

Wheeee, 50% done.
Still haven't heard of @deleriux2, @tsoporan or @scjudd
Will prod gscott and @SaidinWoT with a sharp stick.

I'm still down.

Feel free to remove me from the list.

@tsoporan Thanks for the notice.

Dun dun dun.
Since we didn't hear from @deleriux2 and @scjudd before reaching the end of the month, I will just go ahead and remove accesses.

@SaidinWoT @picardrulez Go, go!

@picardrulez @SaidinWoT I would be sad to see the snail race end, but it have been half-a-month past the deadline.

Snail race is best race.
On Jun 18, 2016 10:32 AM, "The Fox in the Shell"<EMAIL_ADDRESS>wrote:

@picardrulez https://github.com/picardrulez @SaidinWoT
https://github.com/SaidinWoT I would be sad to see the snail race end,
but it have been half-a-month past the deadline.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hashbang/hashbang/issues/8#issuecomment-226954632,
or mute the thread
https://github.com/notifications/unsubscribe/AAc3keYQj8QqD_mpvUE6jT0DK2s4K23cks5qNCu7gaJpZM4IQgS_
.

@theepicsnail Snail master race, right?

Congratulations, @picardrulez, you won the snail race!
It would still be pretty cool if you could send the info so that we can add you to the pass db.

@hashbang/administrators Given that picardrulez/gscott is timeout-ing hard, I just dropped his access.
Closing the issue under the assumption that https://github.com/hashbang/admin-tools/issues/33 will be merged.


disaster response messages dataset

Working on tags and read me

Hi @lhoestq  I have updated the code and files. Please if you could check once.
Thank you


[feat]: Migrate individual packages from CIFS

This would enable fast bitcoin syncs (https://github.com/Start9Labs/bitcoind-wrapper/issues/58), easy migrations from other platforms (LND and vaultwarden, for instance), etc. Could also be reversed to allow easy exporting of app data.
I'm picturing a "Migrate from CIFS" OS feature that works similarly to CIFS backup restore but doesn't do any decryption. Instead it just imports data from a particular CIFS network folder, replacing anything in that package's data volume with the contents of the CIFS folder.
As @ProofOfKeags mentioned in the bitcoind issue referenced above, this does seem like something that could be implemented using the actions API; however, I don't believe there's any current way for a package to access CIFS, without some significant changes to the OS. After more thought I've been wondering whether this wouldn't make more sense as a general OS feature rather than individually implementing in each package that needs it.

I think it may actually be preferred to add support for cifs mounts to the Actions API. Then you could create an action for migrating data from external sources.


Saving flow after changing Layout Editor

Don't know if this is a bug or feature request...
When using the layout editor, and saving changes, it is not always clear that a deployment is necessary, because the normal editor 'deploy' button remains un-highlighted, and 'the flows on the server have been updated' popup appears to time-out.
Expected behaviour
When changes have been made, it's fair to expect that the 'deploy' button, would indicate so.

That's because there is no need to do a Deploy. These changes are deployed with the "Save" button in the Dashboard UI.
The population you're dismissing which mentions about the changes being made are as a result of you saving/deploying from the Dashboard UI

That's because there is no need to do a Deploy. These changes are deployed with the "Save" button in the Dashboard UI.
The population you're dismissing which mentions about the changes being made are as a result of you saving/deploying from the Dashboard UI

The warning triangle remains after the 'the flows on the server have been updated' popup has timed out.
So users need to refresh their browser to get rid of it?

I think this may well cause confusion.  Consider this sequence of operation.

From the flow editor, select Layout Editor for a page.  This opens a new browser tab for the layout editor.
Make changes to the layout and Save them, then select Leave Editor.The natural assumption here would be that this would return one to the flow editor, but it does not, it leaves the user in the new tab running the dashboard.
It is not immediately clear how to get back to the flow editor, however, once one does realise that the original flow editor tab is still there one selects that and there the changes made (such as group re-ordering) are not seen, the only indication is the yellow warning triangle warning that the have been changes.  I guess the popup warning has already expired and gone away if one is not prompt about returning the the original tab.
When one does notice the warning and clicks it, the popup reappears, prompting one to review the changes, where in fact all one needs to do is to refresh the page.

I also notice that if one moves widgets about in the dashboard panel and then opens the layout editor without deploying, then further adjust the layout, save it, and return to the flow editor then confusion of the editor can easily ensue.

It is not immediately clear how to get back to the flow editor, however, once one does realise that the original flow editor tab is still there one selects that and there the changes made (such as group re-ordering) are not seen, the only indication is the yellow warning triangle warning that the have been changes. I guess the popup warning has already expired and gone away if one is not prompt about returning the the original tab.

This could be a better workflow. The Edit Layout button changes you're current tab to the Dashboard in edit mode. The "Leave Edit Mode" button then returns to the Editor. I could get on board with that. Also removes the browser session clash on reviewing/merging changes too.
Thoughts @Steve-Mcl

When I took over the great foundation Joe kicked off, I hit an issue with API tokens (similar to the one Paul had recently and probably TBH, there are proabably a bunch more edge cases out there) so I changed the workflow to emit the edits to Node-RED WITHOUT deploying them.  The user had switch back to Node-RED and press "Deploy" to apply the changes. That eliminated the majority of the friction around merging but would have introduced different friction.  To get past that poor UX, in my head, the workfow needed to be something like:

User choses to edit a page - a shading overlay dialog covers Node RED and displays "Dashboard Editing Page xxx"
The page to edit is popped out to a separate window (as it is now)
User goes about edits and eventually saves or exits, which returned the user to Node-RED where they would see an update dialog
The shading dialog would now display the edits that are held in memory (e.g. "Page xxx has undeployed edits") and at this point the user choses to Deploy or Discard the edits.

This meant there would be ZERO back door deploys via API & zero merge issues - everything is handled by the normal Node-RED deploy mechanism.

However, we have what we have & there are some improvements that would ease matters a little.
We could make both the "exit edit" AND the "save changes" buttons drop the user out of edit mode AND return them to the editor by closing the popped out tab. HOWEVER, Node-RED v4x seems to not always display the "Review Changes" and it is not always obvious you need to merge or refresh. That isnt going to change unless we dump the API calls or Node-RED improves how merges are handled.

FWIW, I favour only saving the changes from the editor, and not the layout dashboard.
Having a 'Return to editor' button which closes the layout dashboard, and returns to the editor, where the Deploy button would signify that a deploy is required, would feel more natural to me.
Not sure why 'Review changes' is necessary...
We've just seen what layout changes have been made. Are users really going to use this? It's just something extra to confuse new users IMO.

Having a 'Return to editor' button which closes the layout dashboard, and returns to the editor, where the Deploy button would signify that a deploy is required, would feel more natural to me.

You have also been using NR for years though. A lot of Dashboard users are new, and I didn't like the introduction of the steps:
Edit > Makes Changes > Save > Go to NR Editor > Deploy
So instead went for:
Edit > Make Changes > Save/Deploy
Which I think is more intuitive, especially for new users, and fewer clicks generally to achieve the same thing

Not sure why 'Review changes' is necessary...

Out of our control, that's a core Node-RED behaviour unfortunately

Are users really going to use this?

Are you referring to the Layout Editor entirely here, or the "Review Changes" bit?

Are you referring to the Layout Editor entirely here

No, the Layout Editor is a very welcome update, and should make it easier for users to design & build their layout.
It's the 'Review changes' feature that IMO is not likely to be used, and possibly adds confusion for new users.
We don't 'review changes' when we make changes to the editor flows.

I was "forced" to abandon Dashboard 1.0 because of display problems on WIN 10 & 11 systems.
So I thought it could be a good ocassion an I am now migrating my flows to 2.0 and am disapointed that handling layouts, especially of buttons and text fields, has become very awkward and IMHO clumsy.
I use a NR browser UI for my remote controlled CNC Mill, Laser Cutter and 3D printers running on raspberry Pi Zero W with PC, laptop and smartphone clients. On the laser cutter NR merges TCP serial commands from Lightburn and relays the control streams via raspi serial I/O to and from a marlin stepper controller.
The UI contains job button groups with x+, x-, y+, y-,z+,z-, home, park, pause, resume and so on buttons plus position display and edit fields for XYZ, Speed and Step sizes.
In 1.0 that was no big act. A new button appeared in the assigned groups matrix. I could resize the button after unlocking the size lock and freely move the button to its designated place. Other buttons already placed would move aside, the group automatically growing or shrinking if necessary and the result was done in a few minutes.
In 2.0 creating a XY Jog pad requires adding spacers to fill the open spaces and get the buttons ordered as needed. I can reorder groups but can not change the lay ouf the widgets inside the group.
Am I doing something wrong or is the still a 'construction site'?

I can reorder groups but can not change the layout of the widgets inside the group.

You can, but it needs to be done (at the moment) from the Dashboard sidebar in the Node-RED Editor. We have a pull request open for it, but it requires my attention, and I've not had a chance to give it the time it deserves.
The reason for the layout shifts between D1.0 and D2.0 is heavily linked to responsiveness. We've had many customers complaining that D1.0 wouldn't work on mobile through to desktop, and so the changes we have introduced fix all of that. The disadvantage of this is that you can't now place and element in an empty space, it needs something either side (which we're doing with spacer)


Omitted Dream repetition.

What's in this pull request?

"VERB(Dream)" was repeated twice on line 268 and 269. So I removed the type on 268.
Resolved bug number: (SR-)

N/A

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

A smoke test on macOS does the following:

Builds the compiler incrementally.
Builds the standard library only for macOS. Simulator standard libraries and
device standard libraries are not built.
lldb is not built.
The test and validation-test targets are run only for macOS. The optimized
version of these tests are not run.

A smoke test on Linux does the following:

Builds the compiler incrementally.
Builds the standard library incrementally.
lldb is built incrementally.
The swift test and validation-test targets are run. The optimized version of these
tests are not run.
lldb is tested.

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

"VERB(Dream)" was repeated twice on line 268 and 269. So I removed the type on 268.

Thanks! This is a definite contender for @pepperdog's "commit message of the week".
@swift-ci Please smoke test OS X platform

Wow - somebody actually reads that stuff!


NIFI-6703: Add Stateless NiFi to CLI

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
https://issues.apache.org/jira/browse/NIFI-6703
Users should be able to easily run Stateless NiFi flows from the CLI without docker.
Added stateless bootstrap and nar to nifi-assembly and removed nifi-stateless/nifi-stateless-assembly. nifi-docker/dockermaven-stateless was updated to accommodate this change.
Added a new top level action (stateless) to nifi.sh which runs the "org.apache.nifi.stateless.NiFiStateless" bootstrap class with the provided arguments after extracting nars. Note that this is intentionally synchronous to allow for many stateless flows on the same machine.
Updated stateless-nifi/README.md
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

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

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

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

[ X ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ X ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

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

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

very slick.  just fired up a nifi instance and created a flow.  published it to the nifi registry.  then executed it in stateless-nifi with a simple config.  +1 merging to master


Add NetworkBehaviour Targeted Messages

Currently, "Target" messages get's invoked on every listening behaviour of a given object. A target system that targets a specific behaviour similar to how SyncedVars work should be added and should replace the current Target system.

This will be a full rewrite of the target system

Target messages now target the networkId and the the networkBehaviour.


Scib integration

Using the format from Theis Lab (SCIB)

@aarmey Is this what you were thinking of when integrating our method with their format?

@andrewram4287 can you move over the test code I wrote and try that? That should give you a very good idea of whether your code is working.


Add selftest for cgroup attach

https://github.com/aquasecurity/libbpfgo/pull/196

selftest:

I have no idea how this happened :
https://github.com/aquasecurity/libbpfgo/runs/7815708108?check_suite_focus=true

Maybe we should use make instead of make -j8 in Makefile?:
https://github.com/aquasecurity/libbpfgo/blob/0850b8cf46a9610acbe6b2c8503fb69a88af4243/Makefile#L129-L138

Maybe we should use make instead of make -j8 in Makefile?:
https://github.com/aquasecurity/libbpfgo/blob/0850b8cf46a9610acbe6b2c8503fb69a88af4243/Makefile#L129-L138

Hey @mozillazg, the "-j8" was a way to "accelerate" the libbpf builds by default in most of the envs (even when no number of jobs was informed). If it is causing issue we can remove it for sure (and rely in -j argument).


SAMZA-1689: Add validations before state transitions in ZkBarrierForVersionUpgrade.

Prevent invalid state updations on barrier.

Introduced a additional barrier state NEW.
Add state validations before updating the barrier.
Fix existing TestZkBarrier tests that are disabled and add new tests
to verify the intended behavior.

@prateekm @vjagadish1989 @xinyuiscool
Please take a look when you get a chance.
Verification:
i=0 while [ $i -lt 100 ]; do                 i=expr $i + 1                 ./gradlew clean :samza-core:test -Dtest.single="TestZkBarrierForVersionUpgrade"  >> ~/test-logs_32 done;
Result:
samza: grep -i 'BUILD SUCCESS' ~/test-logs_32 | wc -l
100
samza:  grep -i 'BUILD FAIL' ~/test-logs_32 | wc -l
0


fixedProfileCrash and app can now mved to sd card

Fixes #2260 . app crash when pickingUp image from gallery  e.g.  #2260
Fixes #2304  . App can now moved to sd card  e.g.  #2304 changed manifest for that
Changes: [Permission added for picking image
added

and some code for checking android version in editprofileActivity
Screenshots for the change:

Please break into separate PRs, a PR should only target one issue.
Secondly, there are some stylistic and coding issues, but we'll discuss them when PRs are separated

@iamareebjamal i am new to github so please guide me that how to make seperate pr

@iamareebjamal should  submit a new one for profile crash

@jindalAnuj Please resolve the requested changes

@iamareebjamal sorry i was  busy but will send requested changes in couple of hours

@iamareebjamal i have done the changes in second commit is it ok .I know it was done a long time ago but please review that

closing this and  submitted  #2345  pull request


Add synonyms to  	CHEBI:91736

New synonyms: (2S)-1-(6-Chloro-5-fluoroindol-1-yl)propan-2-amine
Ro-600175, Ro-60-0175
Add new Xref: CID 3045227

Hi Ceri,
As ChEBI:91736 (a 2-star entry) did not have any stereochemistry shown in its structure or name, I have left it as a parent entry for individual enantiomers, but upgraded it to 3-star status.
There is now a new entry (CHEBI:142183) for the (S)-enantiomer, which is classed as is_a CHEBI:91736.
All ChEBI entries are automatically linked to the matching PubChem CIDs, but the linking process takes a while - CHEBI:91736 should have an automatic x-ref to CID3045227 by the end of next month.
Kind regards,
Gareth


Core v2.x Cleanup + 1st Batch of Deprecation Warnings

Jira
N/A
Summary
Updates all of the @bolt/core styles in the old v2.x version of core to point to the v3.x version and output a warning about the upcoming API changes. Also reverts a few component-specific changes in the v2.x version of core to be extra careful that the v2.14 release rolls out smoothly.
How to test
Confirm tests pass as expected.

PR was released with v2.14.0


Updated MDC plan features

Describe your changes
Issue number
#000
Checklist before requesting a review

[ ] The pr title can be used to describe what this pr did in CHANGELOG.md file
[x] I have executed pre-commit on my machine
[x] I have passed pr-check on my machine

Thanks for your cooperation!

@jude-chen could you please resolve the conflicts?
@lonegunmanb - appreciate your review to this PR also. Thanks!

Hi @jude-chen thanks for opening this pr! We're maintaining module_telemetry.tf file automatically in our CI pipeline so you can just ignore this file. As your pr added a lot of code, would you please give us a brief on the goal of this pr? We'd like to assess whether we should accept these features in this module. @elibetito-microsoft will review this pr based on the mdc's perspective, and I'll review this pr based on Terraform module's perspective.

I'm closing this pr since no response from the user, please feel free to reopen it @jude-chen

@lonegunmanb sorry for the delay, I have updated the PR description with the changes I made in this PR. Can you please reopen the PR and review it again? Thanks.


Remove Duplicates in a Sorted Linked List

Allow me to work on this issue in C++

I would like to work on this issue. Will you please assign it to me.

Hi, i want to contribute as a participant of gssoc'21

@sujal111 mentions the language also.

Hi,
Please assign this task to me. I am a GSSoC'21 participant. I can solve the problem using c++.

I want to do it in CPP

Please assign me this I would like to do this in c++.

I am a GSSOC '21 participant.
I wish to contribute a JAVA code for this issue:
My code will have comment lines to make it explanatory and understandable to everyone.
I will be very happy if I am assigned this issue and allowed to work on this.

please assign this task to me in java under GSSOC'21

i like to contribute to this project ...my code will be in java with proper comments and test cases

Hey there!
I'd like to contribute to the project. I want to address and fix this issue. My implementation will be in python with a clean code and documentation. Kindly provide me with this issue.
I'm also a GSSOC'21 participant.

I am GSSOC'21 participant and l would like to work on this problem and would make sure to implement a neat and clean code ,and make it easy to understand using comments.


logocert_api branch: Get_service_ttl (_zconfig.py)

Hi Kelly-san/GCPTeam,
I'm trying the test tool 2.0.
I faced an issue in the testPrinterIdleNoBroadcastPrivet() test.
In the Get_service_ttl() function (_zconfig.py),
it checking service_name and Constants.PRINTER['NAME'] using startswith.
I think that it should be used the partial comparison (such as 'in'), as wait_for_service_add().
Please confirm it.
Regards,
Yoshimi Morita

Hi Yoshimi,
I agree that both of those functions should use have the same comparison strictness.
I have updated Get_service_ttl() to use 'in' instead of 'startswith'.
Please pull from logocert_api to get the this change .
Thanks for trying out the tool!
Kevin

Hi Kevin-san,
I confirm this change, it works well.
I sincerely appreciate your swift action.
This issue was fixed. I will close this.
Regards,
Yoshimi Morita


Don't throw out short polylines

Made the epsilon values smaller for Polylines, Corridors and PolylineVolumes
This forum post reported a problem with the PolylineVolumes

@bagnell does the relative epsilon stuff you put in a while ago come into play here, or is this really just a case of the tolerance not being high enough?
Related question: Do we always render the polyline if there are only two points or do we end up deduping to 1 point and then throwing it out?

@mramato we'll throw it out if the polyline only has two points and the points are almost the same

Fixes #3293

Update CHANGES.md.
@bagnell can you please review?

@bagnell this is ready now.

does the relative epsilon stuff you put in a while ago come into play here

@mramato Yes, it was changed to check the absolute or relative error. Here it would check the relative error. We need to go through and check all of the epsilon values, but I think we are just fixing them as issues come up.

Should there be a constant with a single epsilon defined somewhere that all of the geometry uses?  Should that be user settable?

And is 10 the right answer, or just a random guess?

@mramato 10 is a random guess.  It's probably small enough, but at some point we should probably figure out what's the smallest distance that's still worth rendering.  6 was definitely too big because you can still see things at that size even without being zoomed in all of the way.

Should there be a constant with a single epsilon defined somewhere that all of the geometry uses? Should that be user settable?

I don't think it would need to be user settable, but having a constant somewhere that all of the geometries use is a good idea.  I added a note to #2364


Adding generated protos for now

Ignore this, unless you are comfortable adding this to main. I need this commit reference for getting foundation to work on our build machines

Closing in favor of more recent PR


FSMA-54 fixed Operation not allowed for a result set of type ResultSe…

…t.TYPE_FORWARD_ONLY
Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

This PR is to fix issue with resultset.previous() which is not supported by the driver.
java.sql.SQLException: Operation not allowed for a result set of type ResultSet.TYPE_FORWARD_ONLY.


Expose kinematic bodies to ecs

I really want to use triangle meshes with moving objects... which is only possible if the bodies are kinematic 😄
https://user-images.githubusercontent.com/1371787/220201292-4e39f90b-23af-4fc1-9b09-dd35b46544fa.mp4

Can you clarify what you mean by this?

I want something like dynamic() that flags the body with PxRigidBodyFlag::KINEMATIC called kinematic(). It should create a rigid_kinematic() instead of a rigid_static(), and copy translation()/rotation() to the physx world instead of linear_velocity() and angular_velocity(). I think this is somewhat straight forward, just a tad tedious.


Problems running IDSL.CSA

Hi,
I've been able to get IDSL.IPA to run successfully and as a next step tried to get IDSL.CSA and IDSL.CSA with DIA option to run. However both workflows were unsuccessful.
The error logs were vague in pointing out what exactly the errors were, apart from problems with the input mzMLs. I'll copy them below:
===================================================================================================
mzML/mzXML/netCDF: ~/bolus_i_raw
OUTPUT: ~/bolus_i_ipa/csa_results
---------------------------------------------------------------------------------------------------
Initiated CSA workflow!
2023-03-27 17:08:27 Etc/UTC

CSA0001	yes
CSA0002	no
CSA0003	yes
CSA0004	12
CSA0005	~/bolus_i_raw
CSA0006	NA
CSA0007	All
CSA0008	~/bolus_i_ipa/peaklists
CSA0009	~/bolus_i_ipa/peak_alignment
CSA0010	no
CSA0011	~/bolus_i_ipa/csa_results
CSA0012	alignedtable
CSA0013	0.05
CSA0014	10
CSA0015	12
CSA0016	0.01
CSA0017	100
CSA0018	100
CSA0019	90
CSA0020	0
CSA0021	2
CSA0022	0.9
CSA0023	Name
CSA0024	NO
CSA0025	0.01
CSA0026	0.05
CSA0027	10
CSA0028	TRUE
CSA0029	0.9
CSA0030	0.05
CSA0031	5
CSA0032	3
CSA0033	0.1
CSA0034	0.5
CSA0035	no
CSA0036	0.01
CSA0037	TRUE
CSA0038	0.6
CSA0039	NA
---------------------------------------------------------------------------------------------------
Initiated Composite Spectra Analysis (CSA) by grouping IDSL.IPA peaks on individual peaklists using aligned peak height table correlations!
Initiated subsetting the `alignedPeakHeightTableCorrelationList.Rdata` for each sample! Temporary subsetted data are stored in the `~/bolus_i_ipa/csa_results` folder!
Completed subsetting the `alignedPeakHeightTableCorrelationList.Rdata`!
Individual `.msp` files are stored in the `CSA_MSP` folder!
Individual adduct annotated IDSL.IPA peaklists are stored in `.Rdata` and `.csv` formats in the `CSA_adduct_annotation` folder!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_18.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_08.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_10.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_04.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_16.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_02.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_12.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_06_r.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_14.mzML`!
Problem with `20221002_NUAHyy_20220405_SMic_B3_HILIC_20.mzML`!
No `.msp` file was detected!
---------------------------------------------------------------------------------------------------
The required processing time was `3.09229907194773 mins`
2023-03-27 17:11:33 Etc/UTC

Completed the CSA analysis successfully!
===================================================================================================

===================================================================================================
mzML/mzXML/netCDF:  ~/bolus_i_raw
OUTPUT:  ~/bolus_i_ipa/csa_results
---------------------------------------------------------------------------------------------------
Initiated DIA workflow!
2023-03-27 18:16:39 Etc/UTC

DIA0001	yes
DIA0002	yes
DIA0003	12
DIA0004	~/bolus_i_raw
DIA0005	NA
DIA0006	All
DIA0007	~/bolus_i_ipa/peaklists
DIA0008	~/bolus_i_ipa/peak_alignment
DIA0009	All
DIA0010	no
DIA0011	~/bolus_i_ipa/csa_results
DIA0012	samplemode
DIA0014	400
DIA0015	12
DIA0016	12
DIA0017	0.01
DIA0018	100
DIA0019	100
DIA0020	90
DIA0021	0.9
DIA0022	Name
DIA0023	no
DIA0024	0.01
DIA0025	0.05
DIA0026	10
DIA0027	TRUE
DIA0028	0.9
DIA0013	2
---------------------------------------------------------------------------------------------------
Initiated Data Independent Acquisition (DIA) analysis at ms level = `2` on individual IDSL.IPA peaklists using raw spectra!
Individual `.msp` files are stored in the `DIA_MSP` folder!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_14.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_10.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_08.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_06_r.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_18.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_12.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_04.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_16.mzML`!
No peak was detected for `20221002_NUAHyy_20220405_SMic_B3_HILIC_02.mzML`!
Initiated detecting unique DIA variants!
Problem with loading .msp file --> `NA`!
Problem with loading .msp file --> `DIA_MSP`!
Error in NumPeaks_PrecursorMZ_SpectralEntropy[, 2] :
  subscript out of bounds

Stopped IDSL.CSA workflow!

Could you please help to pinpoint what went wrong? Please let me know if you need the input excels.
Thank you!

My general suggestion for troubleshooting and parameter optimization for all workflows is to turn the EIC generation on to see the performance of the workflow on your data.
errors in CSA
Probably, there are not enough peaks to match EICs, and you got those errors for CSA. You should make sure you have enough peaks in the IDSL.IPA peaks especially when you use the aligned table option for  CSA0012.
errors in DIA
DIA0016 for SWATH data is too low. Please see the wiki tab for SWATH-MS DIA


Issue verifying SHA256 digest in Windows version of Ollama

What is the issue?
Error: digest mismatch, file must be downloaded again: want sha256:xxxxx, got sha256:xxxxx
ollama run phi3:3.3b-mini-4k-instruct-q8_0
OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.41

What is the issue?
Error: digest mismatch, file must be downloaded again: want sha256:xxxxx, got sha256:xxxxx
ollama run phi3:3.3b-mini-4k-instruct-q8_0
OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.41

Please close, vpn network issue


CS: Handle unbound references to @objc optional methods

Mostly a cleanup and refactoring so that the target change fits nicely. The dynamic lookup case needs more work.
Resolves rdar://69761566
@objc protocol P {
  @objc optional func f()
}

let x: (P) -> (() -> Void)? = P.f

@swift-ci please smoke test macOS

CC @beccadax

@swift-ci please smoke test macOS

@swift-ci please smoke test macOS

Awesome, I've been wanting to get rid of buildPropertyWrapperFnThunk by generalizing the thunk-building code in CSApply for a long time! I'll try to take a look tomorrow 🙂

@swift-ci please smoke test macOS

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test source compatibility

Is it worth adding an executable test as well, since there are so many moving parts here?

Do you mean optional methods, or function references in general?

@swift-ci please smoke test

@swift-ci please test source compatibility

@slavapestov Must've been tiring to even skim through all of this, thank you!


tweaks to HCR schema, additional HCR StainTypes and Fluorophores

Issues

it is hard to represent a DAPI stain right now as part of a codebook
rounds are acquired at different times and processed independently, so making the whole HCRSeries the procedure doesn't quite fit. likely the HCR round needs to be the procedure, and the codebook is a reference that follows it along to communicate intention.
classes are not well defined
missing stain types

Reporter
Fill
Nuclear
Registration

missing fluorophores (just check with http://aidc-mfishlightsheet/record-keeper/fluorophores)

yeah, I think DAPI would fall under other_probe, but that still requires a sequence and DAPI probably doesn't have one. Let's fix that
current structure reflects the separate acquisition of rounds. We went back and forth on this before and I still think we need the HCRSeries to be the fundamental procedure. The codebook isn't really a reference so much as the documentation of which channel is what.
need more detail
this also isn't clear.
we can add fluorophores.

remove channel index from OligoProbe

@dyf can we confirm that other fluorophores are being used. I don't see any examples that use fluorophores other than the 3 we already have. I'm reluctant to add to the list unless we are sure we are going to use others.

Reporter and registration are not stain types.
Current list of fluorophores is accurate to what is being used


Bug: Invoke configuration does not support string type when given array

Description
There are type errors when attempting to use a string as the name of a state in the onDone or onError portion for an invoked service, even though this should be considered a perfectly valid configuration, and without typescript functions just fine.
Expected result
The following simple machine should not cause type errors:
import { createMachine } from "xstate";

createMachine({
    invoke: {
        src: () => () => { },
        onDone: [{ target: "a" }, "b"],
    },
    states: {
        a: {},
        b: {},
    },
});

Actual result
Typescript is unhappy:
Type '{ src: () => () => void; onDone: (string | { target: string; })[]; }' is not assignable to type 'SingleOrArray<AnyStateMachine | InvokeConfig<unknown, AnyEventObject>>'.
  Types of property 'onDone' are incompatible.
    Type '(string | { target: string; })[]' is not assignable to type 'string | SingleOrArray<TransitionConfig<unknown, DoneInvokeEvent<any>>>'.
      Type '(string | { target: string; })[]' is not assignable to type 'TransitionConfig<unknown, DoneInvokeEvent<any>>[]'.
        Type 'string | { target: string; }' is not assignable to type 'TransitionConfig<unknown, DoneInvokeEvent<any>>'.
          Type 'string' has no properties in common with type 'TransitionConfig<unknown, DoneInvokeEvent<any>>'.ts(2322)

Reproduction
https://codesandbox.io/s/currying-shadow-8tnshi?file=/src/index.ts
Additional context
Originally reported here: https://github.com/statelyai/xstate-tools/issues/275

This was fixed by https://github.com/statelyai/xstate/pull/3745


Make C++17 compiler required

Team decided it is time to update minimal requirement for C++ compiler to be at least C++17 compliant.
Change in header file (that is used everywhere) makes sure that requirement is enforced.
Also updated workflow to run now tests with new minimal requirements.

These Ubuntu 20.04 commands may be at odds with the C++17 requirement: https://github.com/YosysHQ/yosys/pull/4460/files#diff-7678ac5f848b6f19279c04c8df2c8547cc23e1d2875678f826e929f6153318d1L93-L100

I wonder if I should upgrade CXXRTL to C++17 as well then...

These Ubuntu 20.04 commands may be at odds with the C++17 requirement: https://github.com/YosysHQ/yosys/pull/4460/files#diff-7678ac5f848b6f19279c04c8df2c8547cc23e1d2875678f826e929f6153318d1L93-L100

We're good on Ubuntu 20.04. Tested in docker with the apt install command you linked to:
root@19879717f761:/# clang --version
clang version 10.0.0-4ubuntu1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
root@19879717f761:/# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
root@19879717f761:/# clang -std=c++17 a.cpp
/usr/bin/ld: /usr/bin/../lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crt1.o: in function `_start':
(.text+0x24): undefined reference to `main'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
root@19879717f761:/# clang -std=c++1237 a.cpp
error: invalid value 'c++1237' in '-std=c++1237'

Good. Thanks for the confirmation


Sprint starting 1 day early and ending 1 day early

When we opened Drop Plan this morning for our palning, we noticed that there is a column for sunday march 10th

And the column for friday march 15th is missing.

Our sprint is set to start on monday march 11th and finish friday march 15th

We are on version 2.2.4 and our time zone is Eastern Daylight Time. We moved time forward this past weekend (from saterday march 9th to sunday march 10th)
Edit: A collegue just informed me the issue appeared last friday, when our Drop Plan extension was updated to 2.2.4

Hi @skyrimax ,
We recently changed our time management to fix some other issues - this might be the cause of this bug.
You can disable it in the Project Settings -> Drop Plan Settings -> "Use new time management".
Can you please check this with the new settings and see if it gets better?

Thanks you, it worked! I will close this issue.Thanks for your help.


replaced all litecoin/bitcoin image files with smileycoin image files

Good work! Sorry I didn't see thie pull request, apparently I wasn't watching this repo. There's some xpm images left over---this is pretty much academic since they'd only be used under a linux GUI version. I'll convert the PNGs you made anyway.
Secondly, the about image is a different size to the original, is there a reason for this? I can squish it easily enough, so don't worry about doing it.


combine all bf creds into one method, bfuapasswords()

PL_API_KEY is still there, but in lines 136 and 137 which are grey in the diff


Fix the inline_python_run command

The inline_python_run command was not working. This fixes it, and some other miscellaneous things.

Thanks, looks great!

Do mind creating a new release so that it gets picked up by Package Control?

Done!

I don't think Package Control will like the version you have used; the v prefix to be precise. You will have to change it to conform exactly to [Semantic Versioning] (http://semver.org/).

Yes, I see. Should be fixed now. Thanks again!


tests: stack: add some testcases

Add some testcases for stack source code coverage,
and add a fatal handler function to hand the error
by null parameter.
Signed-off-by: Ningx Zhao<EMAIL_ADDRESS>

@mengxianglinx @enjiamai , please take look at it.

@nashif , could you take look at it, and merge it if you have no comment?

@nashif  , could you take a look at this PR?


Clarify docs for all nested options

I noticed last week that we sometimes "dot-prefix" nested option names with the associated parent or component
The Prototype Kit team are looking into generating documentation from component macro-options.json so this change copies what we did for Radios and Checkboxes conditional to structure all nested options correctly
Accordion

~heading.text~, ~heading.html~ → heading
~summary.text~, ~summary.html~ → summary
~content.text~, ~content.html~ → content

Summary list

~key.text~, ~key.html~ → key
~value.text~, ~value.html~ → value
~actions.text~, ~actions.html~ → actions

Like other nested options, these now show as separate tables (with links) on the Design System website:

We may still want to bring back "dot-prefix" nested object names for readability:

https://github.com/alphagov/govuk-design-system/pull/2892

Rebased with latest main

Thanks @romaricpascal
@claireashworth I've pulled together the same "format" used in both https://github.com/alphagov/govuk-frontend/pull/3878 and https://github.com/alphagov/govuk-frontend/pull/3902
description: If `html` is set, this is not required. The ${child} of each ${parent}. ${description}. If `html` is provided, the `text` option will be ignored.

It's wordy, repetitive, but what we use the most
We should do a follow up once the Design System Nunjucks docs issues Trello board has been reviewed