Couldn't initialise Refgenie

Hi, I installed refgenie through PIP and couldn't initialise the config, an eror occurs in pypiper: ImportError: cannot import name 'LOGGING_CLI_OPTDATA' from 'logmuse'.
Command:
$ refgenie init -c $REFGENIE

Traceback:
Traceback (most recent call last):
  File "/Users/franklinmichael/.local/bin/refgenie", line 10, in <module>
    sys.exit(main())
  File "/Users/franklinmichael/.local/lib/python3.7/site-packages/refgenie/refgenie.py", line 387, in main
    parser = logmuse.add_logging_options(build_argparser())
  File "/Users/franklinmichael/.local/lib/python3.7/site-packages/refgenie/refgenie.py", line 98, in build_argparser
    sps[BUILD_CMD], groups=None, args=["recover", "config", "new-start"])
  File "/Users/franklinmichael/.local/lib/python3.7/site-packages/pypiper/utils.py", line 60, in add_pypiper_args
    argument_groups=groups, arguments=args, use_all_args=all_args)
  File "/Users/franklinmichael/.local/lib/python3.7/site-packages/pypiper/utils.py", line 808, in _determine_args
    from logmuse import LOGGING_CLI_OPTDATA
ImportError: cannot import name 'LOGGING_CLI_OPTDATA' from 'logmuse' (/Users/franklinmichael/.local/lib/python3.7/site-packages/logmuse/__init__.py)

I've tried to reinstall logmuse and pypiper directly from git to see if it the pip module out of date, but they all fail.

thanks for reporting. You are right. This is an incompatibility I introduced in pypiper which relies on the dev version of logmuse, which I failed to release.
I will be able to solve this problem tomorrow. in the meantime you can fix it with
pip install https://github.com/databio/logmuse/archive/docs.zip

you could also fix by downgrading pypiper to the previous version with
pip install piper==0.11.3

Alright this should be fixed now on master. Please re-open if something is amiss.
By the way, we're planning a major release of refgenie in the next few days that will add lots of new features, but will also change the config format, so might want to hold off on getting too many things set up in the current system.


Sequence of .setValue(true) on multiple checkboxes is not stacking inputs checked state

Describe the bug
Sequence of .setValue(true) on multiple input[type="checkbox"]
is not stacking inputs checked state. It works kind of like inputs are of type="radio"
Reproduction
https://github.com/taigabrew/vue-test-utils-bug-247ab5c2
System Info

Operating System: macOS Catalina 10.15.7
Node version: v14.15.1
yarn version: 1.22.4
Installed vue-jest version 5.0.0-alpha.6
Installed @vue/test-utils 2.0.0-beta.10

Hi! Thanks for the reproduction, that was very useful.
This is not going to work, and here's why - there is no parent component listening for update:modelValue in this scenario. Normally you would have something like <multiselect v-model="checkedItems" /> or something. In this case, there is no parent - <Multiselect /> is at the top of the component hierarchy. It's like if you did
import { createApp } from 'vue
const app = createApp(Multiselect)

Basically, mount is a very fancy createApp.
Here are some useful tricks you might like, that hopefully help you and also show off some of the cool features of Vue Test Utils. I can write you tests using the "wrapper" strategy (like I showed you in another issue).
Note it's also possible to get the emitted events of any component using getComponent not just the top level wrapper. Pretty cool. Note I renamed <Multiselect> to <issue-261> when I was debugging, but I used your exact source code.
    it(''works!, async () => {
      const options = [
        { id: 'a', name: 'AAA' },
        { id: 'b', name: 'BBB' },
      ];
      const Wrapper = {
        components: { Issue261 },
        data() {
          return {
            options,
            checked: []
          }
        },
        template: `<issue-261 :options="options" v-model="checked" />`
      }

      const wrapper = mount(Wrapper)

      await wrapper.findAll('input')[0].setValue(true);

      // this is pretty cool
      expect(wrapper.getComponent(Issue261).emitted()['update:modelValue'][0][0]).toEqual(['a']);
      await wrapper.findAll('input')[1].setValue(true);
      expect(wrapper.getComponent(Issue261).emitted()['update:modelValue'][1][0]).toEqual(['a', 'b']);
      // grab `checked` from within `data` using `.vm`
      console.log(wrapper.vm.checked) // ['a', 'b']
    })

Oh! I get it! getComponent is pretty neat.
Thank you!


export CSV by default

https://github.com/ui-libraries/principia/commit/c31fdfd378764b4cb0cbb92f43f4e145addb3712


Implement the entire SCRAM protocol in one helper library

So, this is a work I did a long time ago, in the early summer, that further ahead I've been just trying to rewrite the git history to help making it more reviewable, but no code changes have been introduced ever since. And as October is ending, I just thought it could throw this for the hacktoberfest 😄
How does it work, it is explained in the README as best as I could. How would it look to use it?
Here's a WIP for escalus: https://github.com/esl/escalus/pull/235, which is the simplest version
Here's a WIP for MIM: https://github.com/esl/MongooseIM/compare/master...NelsonVides:scram
One thing I didn't do here is that SCRAM requires user and password to have passed the stringprepping algorithm, but I thought that introducing a stringprepping library as a dependency to this repository would be a bit of a dependency hell, so perhaps it could be a library requirement that these parameters were already stringprepped before being passed here. But I'm not sure about it, perhaps the stringprepping library can be included nevertheless. Looking for opinions.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a0bd7b0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   93.63%
=========================================
  Files             ?        5
  Lines             ?      314
  Branches          ?        0
=========================================
  Hits              ?      294
  Misses            ?       20
  Partials          ?        0

Continue to review full report at Codecov.

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

@NelsonVides: Always in progress?


Returned data should be possibly undefined

The type for the returned data in a useQuery should be potentially undefined to take into account loading and error states.
  const { data } = useQuery(
    getPrices.useQuery(),
  );

@AshotN to confirm:

what version of react-query are you using
what version of TypeScript are you using

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "components/*": ["./components/*"],
      "lib/*": ["./lib/*"]
    },
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "noImplicitAny": false,
    "strictNullChecks": false,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [
      {
        "name": "next"
      }
    ]
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

    "@tanstack/react-query": "^4.28.0",
    "@bufbuild/connect-query": "^0.1.1",

Typescript version: 4.9.4
I'll try to reconfirm the problem as well.

Ah, that's my mistake. I had seen strict: true and glossed over "strictNullChecks": false
Thank you for the help, sorry for the mistake

it's a really easy one to miss!  no worries!  keep us posted on how it goes with Connect-Query.  seriously!  Would love to know how you like it and what things you'd like to see in the future. :)


QScript

In progress PR of QScript. There are a handful of outstanding TODOs. I figure now would be a good time to start looking at the diff in its entirety.

@sellout the build is green now (3/4 passed, with MetadataServiceSpec the culprit). I resolved many of the TODO's, including Traverse, Equal and Show for MapFunc, digForBucket impl complete, NameGen used instead of the same String everywhere, among other things. I also made the normalization-requiring tests pending for the time being so we can merge. Let me know if there is anything else low-hanging that's blocking the merge.

I think this is good to go.

@sellout great! I'll get this in shortly!

 Last updated by [bde80c3...f8c2977][cc-compare]
[cc-base-branch]: https://codecov.io/gh/quasar-analytics/quasar/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/quasar-analytics/quasar/compare/bde80c30447fa7e9621bf40d9c5b2a2b52acd618...f8c297744ff674851c755f62e3236f59777e7252
[cc-pull]: https://codecov.io/gh/quasar-analytics/quasar/pull/1215?src=pr


Add a points member to the Decoded tuple

This is an attempt to address #57 by also including the unmodified
symbol points without breaking compatibility.

Coverage increased (+0.009%) to 98.104% when pulling ac9fbf46936d5bd495a765e472dd88d6addac419 on denvera:master into 833b375c0e84077943b7100cc9dc22a7bd48754b on NaturalHistoryMuseum:master.

Coverage increased (+0.009%) to 98.104% when pulling ac9fbf46936d5bd495a765e472dd88d6addac419 on denvera:master into 833b375c0e84077943b7100cc9dc22a7bd48754b on NaturalHistoryMuseum:master.

It would be nice to include this PR in the main repo. This is a replacement of the old PR #39.


GLES2 CPU-Particles inconsistent lighting

Godot version:
3.2 beta 5
OS/device including version:
Zorin OS 15
Issue description:
Depending on the angle of the camera, CPU-Particles change lighting influence.

Its most noticeable with billboard activated for the material, but it also happens if billboard is disabled.
Steps to reproduce:

Add a light source
Add CPU-Particles

Minimal reproduction project:
ParticlesBug.zip

Looks like it may be the same as https://github.com/godotengine/godot/issues/17542

Done some more digging, this only happens to overlapping meshes, which I think it is more a thing on how GLES2 renders that a bug, feel free to close this issue if this is the case.

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?
I tried the attached project and looks ok, not sure what is the issue.

I suspect is a case of Z fighting. As I commented before I don't think is a bug, but I'm not an expert.

As I commented before I don't think is a bug

So should be fine to close. Doesn't seem like anyone else faced this issue.


No matching export in<EMAIL_ADDRESS>for import "TransportRaceCondition"

I am getting the following error with the frontend when I run using yarn dev:
✘ [ERROR] No matching export in<EMAIL_ADDRESS>for import "TransportRaceCondition"

    node_modules/@ledgerhq/hw-transport/lib-es/Transport.js:74:9:
      74 │ import { TransportRaceCondition, TransportError, StatusCodes, getAltStatusM...
         ╵          ~~~~~~~~~~~~~~~~~~~~~~

The fix listed below here doesn't work for yarn:
https://github.com/anza-xyz/wallet-adapter/pull/949
Someone suggested an alternative fix that I will try:
Goto: node_modules/<EMAIL_ADDRESS>Add line:
export const TransportRaceCondition = createCustomErrorClass("TransportPendingOperation");
This is an open issue for a few weeks, I wonder why nobody else experienced this? I didn't notice this issue in the tutorial video either. I appreciate what you are doing for us Mr Raza!

Hmmm well I added export const TransportRaceCondition = createCustomErrorClass("TransportPendingOperation"); and now when I do yarn dev it starts without compile errors.
I can connect my phantom wallet and it correctly reads the address. It also correctly reads the value of the count in the solana on chain program. But when I click the increment button, nothing happens.
Here is what my dev tools console shows when I click increment:
Error: Invalid arguments: counter not provided.
    at @coral-xyz_anchor.js?v=e1e0dfac:6471:15
    at Array.forEach (<anonymous>)
    at validateAccounts (@coral-xyz_anchor.js?v=e1e0dfac:6466:14)
    at ix (@coral-xyz_anchor.js?v=e1e0dfac:10061:7)
    at MethodsBuilder.txFn [as _txFn] (@coral-xyz_anchor.js?v=e1e0dfac:10123:14)
    at MethodsBuilder.transaction (@coral-xyz_anchor.js?v=e1e0dfac:11240:17)
    at async onClick (increment-button.tsx:17:27)

Also for some reason my background is white not purple like in Mr Raza @AlmostEfficient tutorial video

I reployed my smart contract and all is good.  Thank you again for your amazing videos!

I reployed my smart contract and all is good.  Thank you again for your amazing videos!

can you like, please source what he did that helped you fix this A LOT of people are having this same error and 6 hours later I still can't fix it.

Goto: node_modules/<EMAIL_ADDRESS>
I got you.
Goto<EMAIL_ADDRESS>Add line:
export const TransportRaceCondition = createCustomErrorClass("TransportPendingOperation");
Done

Also, after updating it like stated, i have a weird issue now with the
tsconfig files, tho they are clearly formatted correctly project says they
aren’t.
On Sun, May 19, 2024 at 4:04 AM gameuser1982 @.***>
wrote:

Goto:
<EMAIL_ADDRESS>I got you.
Goto: @.***/errors/lib-es/index.js
Add line:
export const TransportRaceCondition =
createCustomErrorClass("TransportPendingOperation");
Done
—
Reply to this email directly, view it on GitHub
https://github.com/AlmostEfficient/full-stack-solana-dev/issues/3#issuecomment-2119193877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APRPH2LYVI4IXCRUSYSRZYLZDCBM5AVCNFSM6AAAAABH5KSWT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGE4TGOBXG4
.
You are receiving this because you commented.Message ID:
@.***>

@keolamation
I got you.
Goto<EMAIL_ADDRESS>Add line:
export const TransportRaceCondition = createCustomErrorClass("TransportPendingOperation");
Done

also, people keep saying this break on production, I'm making a website ready widget, so I NEED it to not randomly break when customers are trying to connect wallet and buy a token fml.  I am not sure about your production concerns, but that obviously makes me concerned too. I will be dealing with mainnet deployment soon too.  Is there a discord anywhere where we can all like collaborate and try to figure this out?
Because like for real the Solana documentation is sloppy and so is the maintenance of critical repos.

Broskis if you're making a token swap page use the Jupiter terminal embed instead, it's much less work and won't break in prod
https://station.jup.ag/docs/jupiter-terminal/jupiter-terminal
I wish I could be of more help here but I'm currently on vacation without my computer.

Broskis if you're making a token swap page use the Jupiter terminal embed instead, it's much less work and won't break in prod
https://station.jup.ag/docs/jupiter-terminal/jupiter-terminal
I wish I could be of more help here but I'm currently on vacation without my computer.

@AlmostEfficient no worries man! Enjoy your vacation!

Broskis if you're making a token swap page use the Jupiter terminal embed instead, it's much less work and won't break in prod
https://station.jup.ag/docs/jupiter-terminal/jupiter-terminal
I wish I could be of more help here but I'm currently on vacation without my computer.

I'm making a ICO widget. not a token swapper.


[lexical] [lexical-selection] Preserve paragraph styles between lines

This fixes the bug where we don't preserve style attributes like color, font size, background color or any custom styles when creating a new paragraph (press Enter twice).
Heavily inspired by the solution for the formatting: https://github.com/facebook/lexical/pull/5822
I've just extended in the same fashion for the styling.
Closes https://github.com/facebook/lexical/issues/5958
Before:
https://github.com/user-attachments/assets/cea09e27-d979-4017-b36f-8b3f36518fd8
After:
https://github.com/user-attachments/assets/738cc9c9-0f2f-423d-bb97-9f6a0b0148ab

You should be careful of making getStyle and setStyle methods on LexicalElementNode. This can cause conflicts for users who want to upgrade their lexical dependency when they are extending nodes to support importing inline style to them.


Add grayson's bio

Since grayson was previously a collaborator, remove from that list.

perfect! looks great


Pilot log errors when scaling any other deployment

Istio 0.4.0
Hi, when I scale any deployment in my cluster I get approx 50 lines of spam in the istio-pilot log:
ERROR: logging before flag.Parse: W0101 20:49:00.948446       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.949155       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.949664       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.949932       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.950645       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.951217       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:00.959176       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:01.024961       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:01.025876       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:01.026324       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration
ERROR: logging before flag.Parse: W0101 20:49:01.026803       1 resources.go:140] error converting duration (*duration.Duration)(nil), using 0: duration: nil Duration

Any ideas?

@Stono are you still seeing this problem in istio version 0.5.1 or later?

closing until issue can be reproduced in istio 0.5.1 or later


Failed to migrate to dqlite 1.0: No database dump found

Required information

Distribution: Chrome OS
Distribution version: 3.17
The output of "lxc info" or if that fails:

Kernel version: 4.19.106-08245-g9eef371ee83e
LXC version: 3.03
LXD version: 3.17
Storage backend in use: btrfs (5.3.1)

Issue description
Missing global/db.bin blocks lxd from starting - https://bugs.chromium.org/p/chromium/issues/detail?id=1057869
>ls -R
.:
global  global.bak  local.db  local.db.bak

./global:
logs.db  snapshots

./global/snapshots:

./global.bak:
logs.db  snapshots

./global.bak/snapshots:

We've seen a few cases where 1: somehow a user's database dump disappears then 2: this missing dump blocks lxd from even launching, since it tries to migrate, fails, then shuts back down:
2020-02-13 00:57:07.084 6 VM(3)[4662]:   lxd[135]: t=2020-02-13T00:57:02+0000 lvl=info msg="Initializing local database"#012
2020-02-13 00:57:07.084 3 VM(3)[4662]:   lxd[135]: t=2020-02-13T00:57:02+0000 lvl=eror msg="Failed to start the daemon: Failed to migrate to dqlite 1.0: No database dump found"#012
2020-02-13 00:57:07.084 6 VM(3)[4662]:   lxd[135]: t=2020-02-13T00:57:02+0000 lvl=info msg="Starting shutdown sequence"#012

I have a repro case that's in this bad state if there's any more information you need, but haven't been able to turn a working install into this state.
Expected behaviour - 1: the database doesn't disappear, 2: lxd is still able to launch so we or our users can recover their containers e.g. lxd import.
Thanks

So just to be clear, these are users that have been upgrading from some previous LXD version right?
What might have happened is that the last time the previous LXD version was run it did not shutdown cleanly and didn't have chance to dump that db.bin file. If the upgrade was done right at this point, it might produce this error.
The easiest way to fix this would be to 1: restore the global.bak and local.db.bak files to get back to the pre-upgrade state 2: restart the previous LXD binary and shut it down gracefully. 3: retry the upgrade.
As for a broader fix, we might be able to automatically recover from a situation where db.bin is missing by re-generating it, but it could be non-trivial to do.

Probably upgrading from a previous version, haven't confirmed.
Launching the previous LXD binary would be tricky since Chrome OS doesn't support downgrading OS without wiping the machine. Would restoring the previous global.bak and local.db.bak then relaunching current LXD to try the upgrade again not work?
That said, in the one case I got a disk image of there's no db.bin in global.bak either so can't recover that way.
Could something be saving the global db again (e,g, prior to upgrade or if you retry launching) and overwriting global.bak as well?

Probably upgrading from a previous version, haven't confirmed.
Launching the previous LXD binary would be tricky since Chrome OS doesn't support downgrading OS without wiping the machine. Would restoring the previous global.bak and local.db.bak then relaunching current LXD to try the upgrade again not work?

No, it would fail in the same way, since the new binary of LXD would start off from the same state (with a missing db.bin).

That said, in the one case I got a disk image of there's no db.bin in global.bak either so can't recover that way.
Could something be saving the global db again (e,g, prior to upgrade or if you retry launching) and overwriting global.bak as well?

I don't understand this question.

To be clear, db.bin isn't required by LXD at all. In fact, this file isn't read by LXD.
db.bin is a saved view of the database as assembled from Raft. It's useful for debugging purposes but it is not where the data is stored.
What you do need is at least one snapshoft or a set of segments to replay the raft transactions to your current state.
This is LXD 3.17 on ChromeOS. Can you comment on the versions of libraft and libdqlite used in your setup? We did have a bug a few months ago where out of disk space situations could lead to missing files and a broken database, though not quite to the extent displayed here.
It may be worth checking with @freeekanayaka on good versions of those two dependencies to match the LXD version you ship.

Seeing that both the main directory and the backup directory are near empty, I wonder if it wasn't a bad shutdown leading to un-flushed btrfs transactions. LXD would have copied global over to global.bak, then opened the database from global and run the update.
This would have lead to most files being freshly written, so if filesystem writes weren't properly flushed, a filesystem view such as the one you posted in this issue is possible.

Ah, that sounds plausible.

@stgraber I've found that deleting the entire database folder allows lxd to start, then I can lxd import the existing containers. If we're only running containers on the same host is there anything we'd lose when we lxd import the container?
@stgraber Do you have a link to the issue where out-of-disk leads to broken database? A quick github search didn't find it for me. We've seen issues when running out of space e.g. http://crbug/930602 and am curious if it's the same.
@freeekanayaka What versions of raft and dqlite should we be running with lxd 3.17? We use whichever versions are bundled with lxd in in the download at https://linuxcontainers.org/downloads/lxd/lxd-3.17.tar.gz . The timestamp is September 2019.

Thanks,

@feileacan you will loose any daemon configuration, network configuration, profiles, projects and storage volumes. Depending on the use case, that may not be a problem though.
@freeekanayaka may have a link to the out of disk issue we fixed a while back.

@feileacan the out of disk issue is very likely not relevant, since it affected the dqlite 1.x series (for reference here's the top-level PR where the issue was fixed).
Now, the lxd 3.17 tarball does sport dqlite 1.x (didn't check what version exactly, but it doesn't matter), however as far as I can tell the issue has happened because of an unclean shutdown of lxd 3.14 or earlier (which is the last version sporting dqlite 0.x) immediately followed by an upgrade to 3.15 or later (presumably 3.17 in your case).
Unfortunately this is an edge case we don't have a good fix for at the moment, so if you want to restore your state completely the only option would be to restore the state as it was before the upgrade (e.g. with the .bak directories), start 3.14 again (or whatever version you were running before the upgrade), shut it down cleanly and then re-try the upgrade.

@freeekanayaka anything more to do here?

@stgraber I don't think there's anything with a reasonable cost/benefit ratio to do here. The suggested approach is either restart from scratch and use lxd import to restore your containers, or revert to 3.14 restoring the .bak dir and try to shutdown it gracefully then re-do the upgrade.

Ok, since we haven't any more cases of this and 3.14 was quite a while back, let's close this.


Fix transactions on WWCode SV

Mail from Brittani:

(...) Can you please change the following transactions in Silicon Valley's OC https://opencollective.com/wwcodesv Inline image 1:
$1,000 Donation to Silicon Valley from VMWare to $877.50.
$2,000 Donation to Silicon Valley from Tableau to $1,755.00.
$500 Donation to Silicon Valley from Financial Engines to $438.75.

Image on email.

done @nicobarretoOC


Rename specimen -> subject globally

The use of the term specimen is a holdover from a different system.  Right now all use of the term specimen should actually be subject. specimen should be reserved for describing tissue samples.
This is blocked until all of the PRs adding schemas are merged.

Done


Fix documentation and display bugs

Codecov Report

Merging #245 (1095445) into master (d4b2c81) will not change coverage.
The diff coverage is 100.00%.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


docs: Cloudflare R2 should use auto as region

We need to add this in our docs.
create stage my_dataset url='s3://<bucket_name>'
connection=(
    endpoint_url='https://<account_key>.r2.cloudflarestorage.com/'
    access_key_id='<ak>'
    secret_access_key='<sk>'
    region='auto'
);

list @my_dataset;

https://developers.cloudflare.com/r2/data-access/s3-api/api/#bucket-region

For compatibility with tools that do not allow you to specify a region, an empty value and us-east-1 will alias to the auto region.

R2 also allows empty value or us-east-1 as region.

R2 also allows empty value or us-east-1 as region.

 We have to statement this in docs because opendal has a region detect logic like the following:
https://github.com/datafuselabs/opendal/blob/ec25bc294c25f6b1094c40c787ce0bffb9481817/src/services/s3/backend.rs#L508-L608
But R2 doesn't support that logic and will return 400 errors. So we need to add this in docs.
Maybe we could ignore the error during detect_region and return the default us-east-1 as the region?

Already been addressed.


Fixed typo in service-bus-integrate-with-rabbitmq.md

Changed 'fist message' to 'first message'

Learn Build status updates of commit 0cbeced:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 0cbeced:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/service-bus-messaging/service-bus-integrate-with-rabbitmq.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looks good; thanks @apmurali!


Update diagnostic-al190.md

Include the correct format for a Time datatype with an example.  Following a similar text as the one found in diagnostic-al191

You cannot make any edits between the DO_NOT_EDIT tags - this area is solely controlled by the AL language and would be overwritten with the next automatic refresh.
What you can do instead: move your addition into a new Remarks section under the DO_NOT_EDIT area.
For example: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/diagnostics/diagnostic-al305


[FLINK-14902][Connector-JDBC]JDBCTableSource Supports AsyncLookupFunction

What is the purpose of the change
JDBCTableSource supports AsyncLookupFunction for temporal table join
Brief change log

Add JDBCConnection to wrap Connection and PreparedStatement.
2.Add ConnectionManager to manage JDBCConnection.
3.Share JDBCLookupOptions with JDBCLookupFunction and JDBCAsyncLookupFunction
4.ShareJDBCLookupBuilder with JDBCLookupFunction and JDBCAsyncLookupFunction
5.Add JDBCAsyncLookupFunction to support Async lookup JDBC.

Verifying this change
This change added tests and can be verified as follows:
1.JDBCLookupFunctionITCase#test
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

why close this pr，do we have any problem

why close this pr，do we have any problem

For this is a legacy LookupFunction currently, so I close this.


ERAP updater using palletjack

Updates the ERAP feature service and map using github.com/agrc/palletjack for the heavy lifting.

I think it would be nice to update the readme and make the github action successful in this pull request.

Moved to draft pending palletjack completion.
Also, re: CI testing, I'm running into the same problem as with Auditor a while ago. ERA imports palletjack, which imports arcpy, which can't be installed in the CI environment. I've modified the action to just build, no tests. Are you aware of any better work arounds?

mocking would probably be the best solution. try except the import and then supply a mock in the exception handler.

Ok, now that palletjack is up we can push this out. I've implemented a folder rotator to rotate the data folder as needed; I would appreciate a review of this (rotator.py).
Test coverage is low because the tests are focused around the individual methods themselves. The main script just integrates supervisor, palletjack, and rotator.py, which are all individually tested.

Converting to draft while working on google cloud function adventure.

Converting to draft while working on google cloud function adventure.

I might be best to finalize this this pr and open a new one for the function stuff.

I think you're right... it's starting to get messy, branches on branches. Two steps forward and one step back! Riders, away!


Update installation url to match repo url

I also updated the command from asdf plugin-add to asdf plugin add to match the official documentation.
Reference:
https://asdf-vm.com/manage/plugins.html

Thanks for the PR @russellsanborn. We should probably update the CI badge as well.

If you're game to do it real quick that would be great! Thanks!

As a reference, i submitted a PR to update the links in asdf-plugins.
https://github.com/asdf-vm/asdf-plugins/pull/860


Failed to activate the tab-switcher package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.11.1
Electron Version: 0.37.8
System: Mac OS X 10.10.5
Thrown From: tab-switcher package, v1.5.4
Stack Trace
Failed to activate the tab-switcher package
At Arguments to CompositeDisposable.add must have a .dispose() method

TypeError: Arguments to CompositeDisposable.add must have a .dispose() method
    at assertDisposable (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/composite-disposable.js:70:13)
    at CompositeDisposable.module.exports.CompositeDisposable.add (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/composite-disposable.js:43:11)
    at new TabListView (/Users/lneir/.atom/packages/tab-switcher/lib/tab-list-view.coffee:60:17)
    at new TabList (/Users/lneir/.atom/packages/tab-switcher/lib/tab-list.coffee:16:17)
    at Object.TabSwitcher.deserialize (/Users/lneir/.atom/packages/tab-switcher/lib/tab-switcher.coffee:36:34)
    at Object.module.exports.activate (/Users/lneir/.atom/packages/tab-switcher/lib/tab-switcher.coffee:66:19)
    at Package.module.exports.Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:183:20)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:156:32
    at Package.module.exports.Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:92:15)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/package.js:149:26
    at Package.module.exports.Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:146:34)
    at PackageManager.module.exports.PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:538:21)
    at /Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-manager.js:397:31

Commands
     -0:20.6.0 settings-view:check-for-package-updates (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-monokai.theme-one-dark-ui)

Config
{
  "core": {
    "allowPendingPaneItems": false,
    "audioBeep": false,
    "themes": [
      "one-dark-ui",
      "monokai"
    ]
  },
  "tab-switcher": {}
}

Installed Packages
# User
atom-ternjs, v0.15.0 (active)
docblockr, v0.8.5 (active)
editorconfig, v1.4.1 (active)
linter, v1.11.16 (active)
linter-eslint, v7.3.2 (active)
monokai, v0.18.0 (active)
react, v0.16.0 (active)
tab-switcher, v1.5.4 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

I got the same error but worse: Atom freezed and could not do anything at all (just closing the process in Windows 8.1). A full Atom reinstall did not help.
I had to manually delete .atom/packages/tab-switcher and all files inside of .atom/storage. This way atom restarted "normally". Then I reinstalled tab-switcher package.

I can't for the life of me figure out how to repro this, so I'm considering it stale. Perhaps an old Atom bug? Please reopen if you're still having trouble. Thanks!


Implement Managed Identity for the provider authentication

Managed Identity auth for provider and pipelines
Managed identities (MI) provide an automatically managed identity in Microsoft Entra ID. Applications use managed identities to connect to resources that support Microsoft Entra authentication, and to obtain Microsoft Entra tokens, without credentials management.
Consider to use MI to authenticate and create resources with the Power Platform  Terraform provide.
Posible Tasks
•	Implement MI on the provider or investigate if works now.
•	Investigate or implement the “Configure a user-assigned managed identity to trust an external identity provider”, After you configure your user-assigned managed identity to trust an external IdP, configure your external software workload to exchange a token from the external IdP for an access token from Microsoft identity platform. The external workload uses the access token to access Microsoft Entra protected resources without needing to manage secrets (in supported scenarios). To learn more about the token exchange workflow, read about workload identity federation.
•	Evaluate MI considerations and restrictions; Create a trust relationship between a user-assigned managed identity and an external identity provider - Microsoft Entra Workload ID | Microsoft Learn
•	See the feasibility to use MI on Github actions or Azure DevOps pipelines or create issues on the products backlog.
DOD
•	Create Power Platform resources using MI on Dev environment (desktop Plan / apply on local host)
•	Create and document process and QuickStart’s.
•	Create and document a GitHub action that use MI to deploy resources.
•	Create and document and Azure DevOps pipeline that use MI to deploy resources.

@mattdot, this is actually documented here: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/azure-synapse-link-msi

It would indeed be super useful to be able to configure a user-assigned managed identity to trust an external identity provider in Terraform, as per https://learn.microsoft.com/en-us/entra/workload-id/workload-identity-federation-create-trust-user-assigned-managed-identity?pivots=identity-wif-mi-methods-azp (this is only possible for applications right now)


Feature - Filters on classes

Add filters so that a user-input term can result in subsets of information to be printed
Interacts with data structures holding all classes and allows certain classes to be printed.
Requirements

Prompts user to enter if they would like to use a filter
Doesn't allow undefined filters
Directly/Indirectly interacts with the structures holding all the class info
Simple for user to use through terminal

Add your own thoughts and ideas by commenting or implementing within a pull request related to this issue!

@jubuyer I would like to work on this
Please assign this task to me.


Switch contrast to match MNE tutorial

Codecov Report

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

@@           Coverage Diff           @@
##           master     #134   +/-   ##
=======================================
  Coverage   99.00%   99.00%
=======================================
  Files          27       27
  Lines         601      601
=======================================
  Hits          595      595
  Misses          6        6

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 e0decae...6e2c923. Read the comment docs.


[cppad/cpuid] Update to latest version

Describe the pull request

What does your PR fix?
Fixes https://github.com/microsoft/vcpkg/issues/19872#event-5275764601
Fixes https://github.com/microsoft/vcpkg/issues/19873#event-5275764829

No feature need to be tested.

Thanks for the updates!


fix(deps): upgrade octokit dependencies, import them as ESM modules, add required onSecondaryRateLimit handler

Seems to work now!


[DocumentIntelligence] Updated CHANGELOG and added migration guide

Changes to the README and to samples will be included in the next PR.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.AI.DocumentIntelligence


Build with Github CI actions

What's the point of this? Some description would be required.

What's the point of this? Some description would be required.

You master fails on Travis, this was a more recent way to have a faster CI.


Updated UG deleteTask.

DeleteTask description in UG included repetitive pattern.
This commit effectively closes issue #174

Codecov Report

Merging #197 (8029fdb) into master (2d4084d) will increase coverage by 4.94%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #197      +/-   ##
============================================
+ Coverage     55.45%   60.40%   +4.94%
- Complexity      571      615      +44
============================================
  Files           105      105
  Lines          2420     2432      +12
  Branches        318      324       +6
============================================
+ Hits           1342     1469     +127
+ Misses          968      849     -119
- Partials        110      114       +4

Impacted Files
Coverage Δ

...main/java/seedu/address/model/person/TaskList.java
55.17% <0.00%> (+1.72%)
:arrow_up:

...c/main/java/seedu/address/model/person/Person.java
67.59% <0.00%> (+2.77%)
:arrow_up:

src/main/java/seedu/address/model/person/Task.java
91.17% <0.00%> (+5.88%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
70.70% <0.00%> (+8.08%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
75.00% <0.00%> (+13.33%)
:arrow_up:

...in/java/seedu/address/logic/parser/ParserUtil.java
97.29% <0.00%> (+13.51%)
:arrow_up:

...a/seedu/address/model/person/UniquePersonList.java
67.45% <0.00%> (+21.30%)
:arrow_up:

...eedu/address/logic/parser/AssignCommandParser.java
90.47% <0.00%> (+90.47%)
:arrow_up:

...va/seedu/address/logic/commands/AssignCommand.java
90.69% <0.00%> (+90.69%)
:arrow_up:

...odel/person/exceptions/DuplicateTaskException.java
100.00% <0.00%> (+100.00%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


std.container.Array - optimize concatenation

insertBack seems to already reserve space.

It does, but the previous version requires two allocations, whereas mine only one assuming the length is known.


Kubelet failed to boot up

/gke bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
I deploy a workload cluster in Hetzner via Cluster API on GKE cluster.
It starts to deploy the contol-plane and stuck on KubeadmInit. I tried to debug it and found these logs
Unfortunately, an error has occurred:
        timed out waiting for the condition

This error is likely caused by:
        - The kubelet is not running
        - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

kubelet logs say this
Jan 25 20:59:14 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:14.891103    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:14 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:14.991749    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.092887    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.193451    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.294066    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: I0125 20:59:15.317520    3062 kubelet_node_status.go:70] "Attempting to register node" node="sys-cluster-control-plane-59n6g"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.319603    3062 kubelet_node_status.go:92] "Unable to register node with API server" err="Post \"https://142....15:443/api/v1/nodes\": EOF" nod>
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.395179    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.496277    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.597285    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.698296    3062 kubelet.go:2448] "Error getting node" err="node \"sys-cluster-control-plane-59n6g\" not found"
Jan 25 20:59:15 sys-cluster-control-plane-59n6g kubelet[3062]: E0125 20:59:15.707752    3062 controller.go:144] failed to ensure lease exists, will retry in 7s, error: Get "https://142....15:443/apis/coordination.k8s.io/>

What did you expect to happen:
I expect the cluster to be deployed successfully.
Control-plane get passed KubeadmInit stage
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
It happens sometimes and sometimes all good. And I don't get the reason why it's happening
Environment

cluster-api-provider-hetzner version: latest
Kubernetes version: (use kubectl version) 1.25.2 on Hetzner VMs and 1.25.3 on GKE cluster
OS (e.g. from /etc/os-release): I have a cluster on GKE as a management cluster and ubuntu-22.04 on Hetzner VMs

I haven't solved the issue yet. Please, help me :)
If you need more logs, just ping me, I would be happy to share it with you

Did you install the CCM?

Am I supposed to do it before Kubernetes cluster initialization. Cause I have only control plane and Kubernetes initialization failed due to unregistered node, in #cluster-api slack channel said it's the problem with a network layer, but I do not know how to debug it

lol, it's deployed right now. It's so unstable that I cannot even tell what's the root of the cause

lol, it's deployed right now. It's so unstable that I cannot even tell what's the root of the cause

It's deployed 2 times in a row and I honestly do not understand the reason of earlier failures. Could it be the problem from Hetzner side? I use the same template as clusterctl generate cluster, I do not change anything, but from time to time it works and sometimes it fails. Recently, this problem happens more often, so I am wondering, perhaps it's an issue from Hetzner side?

Still no updates on it. So I'll close it for now


Overriding values or inheriting from another plist

We've come across a situation where we have a config that needs to be identical to another one (and stay identical if changes are made) except for one value
Currently I'm using plutil to override the value just before calling configen but this is quite hacky. So I see there are two options:
Allow overriding a key value on the command line, eg:
configen -p "$configLocation" -h "$configDir/Config.map" -n $configName -o "$configDir" --override KEY VALUE
Inheriting from another plist, eg:
baseconfig.plist
<dict>
  <key>KEY1</key>
  <string>VALUE1</string>
  <key>KEY2</key>
  <string>VALUE2</string>
</dict>

config.plist:
<dict>
  <key>:super</key>
  <string>baseconfig.plist</string>
  <key>KEY2</key>
  <string>NEW_VALUE2</string>
</dict>

The key of the base plist being something like :super, :inherit_from or :base etc. But starting with a character like : that makes it an invalid swift variable name.
That way the generated config.swift from config.plist is:
class Config {
  static let KEY1 = "VALUE1"
  static let KEY2 = "NEW_VALUE2"
}

I think the latter plist inheritance option would be preferable as it keeps all the values in the plists and there's no chance of one hiding in a script somewhere. Would this be desirable to implement and create a pull request?

I think it's a good idea, but have you considered having two plist files (and changing the values you want to be different in the other plist file) and switching between them?


Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[ ] Android
[x ] UWP
[ ] watchOS
[ ] tvOS
[ ] Tizen
[ ] .NET Standard

Feature Library

[ x] Core
[ ] BluetoothLE
[ ] Beacons
[ ] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of Library
All
Version of OS(s) listed above with issue
The service funnel will not work for all cases
Steps to Reproduce

Register BLE and Geofencing
Service registration fails

Expected Behavior
Fails
Actual Behavior
Doesn’t fail

Fixed in latest release


[CDAP-17376] Added override metrics methods to fix builds

Added child() and getTags() method overrides for the mock TestingPipelineContext to fix CDAP-17376.

/gcbrun


Field labels are visible for hidden fields

Describe the bug
When some fields are hidden for particular locales, their labels are still visible.
To Reproduce
Steps to reproduce the behavior:

Enable language filter
Hide some locales

Expected behavior
Fields for hidden locales are fully hidden, with labels.
Screenshots

Which versions of Sanity are you using?
@sanity/cli (global)     3.58.0 (up to date)
@sanity/language-filter   4.0.2 (up to date)
@sanity/vision           3.58.0 (up to date)
sanity                   3.58.0 (up to date)

What operating system are you using?
OSX
Which versions of Node.js / npm are you running?
10.5.0
v18.20.1

The same behavior is reported in Sanity Internationalization plugin: https://github.com/sanity-io/sanity-plugin-internationalized-array/issues/42#issuecomment-1721208504

Having the same issue here - @VitaliyPotapov did you manage any workarounds?


[Snyk] Security upgrade setuptools from 40.5.0 to 70.0.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.
Snyk changed the following file(s):

examples/xgboost/requirements.txt

⚠ Warning
```
xgboost 1.6.2 requires scipy, which is not installed.
scikit-learn 1.0.2 requires scipy, which is not installed.
mlflow 1.23.0 requires scipy, which is not installed.
grpcio-tools 1.62.2 has requirement protobuf<5.0dev,>=4.21.6, but you have protobuf 3.20.3.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
</details>

---

> [!IMPORTANT]
>
> - Check the changes in this PR to ensure they won't cause issues with your project.
> - Max score is 1000. Note that the real score may have changed since the PR was raised.
> - This PR was automatically created by Snyk using the credentials of a real user.
> - Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

---

**Note:** _You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs._

For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiJkNGZjNjMxOS05NWU2LTQ3OTItYmY3Yy0wMjZkNTFhYTcyNzkiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6ImQ0ZmM2MzE5LTk1ZTYtNDc5Mi1iZjdjLTAyNmQ1MWFhNzI3OSJ9fQ==" width="0" height="0"/>
🧐 [View latest project report](https://app.snyk.io/org/1.-demo-env/project/968762d1-fca6-4c95-b858-81e5b1705309?utm_source=github-enterprise&utm_medium=referral&page=fix-pr)
📜 [Customise PR templates](https://docs.snyk.io/scan-using-snyk/pull-requests/snyk-fix-pull-or-merge-requests/customize-pr-templates)
🛠 [Adjust project settings](https://app.snyk.io/org/1.-demo-env/project/968762d1-fca6-4c95-b858-81e5b1705309?utm_source=github-enterprise&utm_medium=referral&page=fix-pr/settings)
📚 [Read about Snyk's upgrade logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities)

---

**Learn how to fix vulnerabilities with free interactive lessons:**

🦉 [Improper Control of Generation of Code ('Code Injection')](https://learn.snyk.io/lesson/malicious-code-injection/?loc=fix-pr)

[//]: # 'snyk:metadata:{"customTemplate":{"variablesUsed":[],"fieldsUsed":[]},"dependencies":[{"name":"setuptools","from":"40.5.0","to":"70.0.0"}],"env":"prod","issuesToFix":[{"exploit_maturity":"Proof of Concept","id":"SNYK-PYTHON-SETUPTOOLS-7448482","priority_score":213,"priority_score_factors":[{"name":"confidentiality","value":"high"},{"name":"integrity","value":"high"},{"name":"availability","value":"high"},{"name":"scope","value":"unchanged"},{"name":"exploitCodeMaturity","value":"proofOfConcept"},{"name":"userInteraction","value":"required"},{"name":"privilegesRequired","value":"none"},{"name":"attackComplexity","value":"high"},{"name":"attackVector","value":"network"},{"name":"epss","value":0.01055},{"name":"isTrending","value":false},{"name":"publicationDate","value":"Mon Jul 15 2024 08:51:32 GMT+0000 (Coordinated Universal Time)"},{"name":"isReachable","value":false},{"name":"isTransitive","value":true},{"name":"isMalicious","value":false},{"name":"businessCriticality","value":"high"},{"name":"relativeImportance","value":"high"},{"name":"relativePopularityRank","value":99},{"name":"impact","value":9.79},{"name":"likelihood","value":2.17},{"name":"scoreVersion","value":"V5"}],"severity":"high","title":"Improper Control of Generation of Code ('Code Injection')"}],"prId":"d4fc6319-95e6-4792-bf7c-026d51aa7279","prPublicId":"d4fc6319-95e6-4792-bf7c-026d51aa7279","packageManager":"pip","priorityScoreList":[213],"projectPublicId":"968762d1-fca6-4c95-b858-81e5b1705309","projectUrl":"https://app.snyk.io/org/1.-demo-env/project/968762d1-fca6-4c95-b858-81e5b1705309?utm_source=github-enterprise&utm_medium=referral&page=fix-pr","prType":"fix","templateFieldSources":{"branchName":"default","commitMessage":"default","description":"default","title":"default"},"templateVariants":["updated-fix-title","pr-warning-shown","priorityScore"],"type":"auto","upgrade":[],"vulns":["SNYK-PYTHON-SETUPTOOLS-7448482"],"patch":[],"isBreakingChange":false,"remediationStrategy":"vuln"}'

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)

🎉 Snyk hasn't found any issues so far.
✅ code/snyk check is completed. No issues were found. (View Details)


DPE-3617 add ca chain support

Port of VM PR#396
Fixes #382

No test here? :-(

Since it's a lib, all tests are within the lib owner repo (vm). We can add, but would be duplication


Decide how management pages work online

What
We are testing new pages that allow the user to manage certain aspects of the kit. We should think about how/if they work while the kit is running online.
Why
When the kit is running online, certain changes may not work or be persistent (eg installing an extension)
Who needs to work on this

Developers
Interaction designer
Content designer

Who needs to review this

Developers
Interaction designer
Content designer

Done when

[x] Create designs
[ ] Discuss ideas
[ ] Decide on an approach
[ ] Create a new card for implementation of the agreed solution

High priority as users will be able to make changes that will not be saved.
Needs to be considered next sprint with a view to implementing the solution before the release of v13.

My idea for this is to check if the kit is running in 'test mode' (npm start). If so, Manage Prototype pages would respond with a page with content like (draft):

Manage your prototype
This prototype is running in test mode. This is probably because it is running online.
To manage your prototype it must be running in dev mode.
In the terminal run:
npm run dev

The Password and Clear data pages would be exempt from this, they both work online

That makes sense.  I'll start turning that into a ticket.
P.S. I don't think 'test mode' is the right term for when it's hosted, but that doesn't change what we do with the management pages so we can have that discussion seperately.

I presume we should also hide the Manage your prototype link on the homepage?

@nataliecarey yeh that sounds like a good idea thanks, and in the footer if possible. I wonder if people will be confused that they disappear but we can look at it again if they do


Fix non-critical security Alerts

Vulnerability is only used by development dependencies. Closing the issue as is not a priority at this moment.


BGP CP: Add externalTrafficPolicy: Local support for service announcements

PR #22397 added the ability to announce LoadBalancer IPs of services, but this implementation lacks support for the externalTrafficPolicy field.
The description of this field according to the reference in the k8s docs is:

externalTrafficPolicy describes how nodes distribute service traffic they receive on one of the Service's "externally-facing" addresses (NodePorts, ExternalIPs, and LoadBalancer IPs). If set to "Local", the proxy will configure the service in a way that assumes that external load balancers will take care of balancing the service traffic between nodes, and so each node will deliver traffic only to the node-local endpoints of the service, without masquerading the client source IP. (Traffic mistakenly sent to a node with no endpoints will be dropped.) The default value, "Cluster", uses the standard behavior of routing to all endpoints evenly (possibly modified by topology and other features). Note that traffic sent to an External IP or LoadBalancer IP from within the cluster will always get "Cluster" semantics, but clients sending to a NodePort from within the cluster may need to take traffic policy into account when picking a node.

So if the user sets the externalTrafficPolicy to Local we should assume that ECMP is implemented and configured on the BGP peers according to the wishes of the user and only announce routes with next hops of nodes which have a service-endpoint for the given service.
NOTE: Currently the BGP Control Plane only announces next hops of the nodes with BGP speakers, if the subset of nodes with speakers and service-endpoints don't overlap, no announcement will be made. This should be mentioned in the documentation associated with the feature until the BGP Control Plane is able to produce next-hops for nodes without speakers.

While designing this feature, would it be possible to consider supporting Weighted ECMP over BGP.
This feature has a good description in the FRR documentation, and is supported by most hardware (Cisco, …).
When using Local traffic policy, it should be use to direct more traffic to a node that has multiple pods matching the service.
For instance, with a replica of 3 pods, if a node A has 2 pods, and a node B has 1 pod, 2 third of the traffic should be send to node A and one third to node B.
If can be done by announcing the path from node A with twice the bandwidth of node B.

@Jean-Daniel I can imagine a few scenarios where weighted ECMP can be really useful, thanks for the suggestion, wasn't on my radar yet. I did a quick peek at what we need to do from a BGP perspective to make this work.
Seems that the feature is based on this draft. The draft standard proposed an extended community be used to transfer an indication of link speed which would be encoded as bytes/s in 32-bit IEEE float format in that community.
According to the spec the ratio between the next hop capacities would be used for the weighting in a resolution from 1 to 100.
While there is some overlap in implementation (both features will need to look at the location of service backends), I think weighted ECMP deserves its own issue and incremental PR. For one, I think that weighted ECMP has a place in if the external traffic policy is set to Cluster as well for a number of reasons.
Secondly, announcing "fake" bandwidth information might have some implications. Ideally we would want to use actual bandwidth information from the nodes, just in case a router implementation gets funny ideas about artificially limiting based on this indication, which is additional work. Moreover, we would have to coordinate these fractions over multiple nodes which might be tricky, again work or at least not something we can easily tack onto the current issue.
Please feel free to open a CFP for this though, seems promising.

I would also suggest that weighted ECMP if/when implemented should be an optional feature  as I can imagine not every switch vendor might support this :)

I've been testing the BGP Control Plane service announcement feature in v1.13.0-rc5, but without the externalTrafficPolicy: Local support I won't be able to migrate to it. Are there plans to implement this request in a future version?

IKEA asked what release this would be available. From this thread I understand it will be in 1.14 OSS en CEE releases.

Any progress?

Lack of this feature in some environments also affects using loadbalancer mode: DSR and forced to use SNAT instead. This is a crucial functionality.

Just ran into an issue with this, as I mindlessly set externalTrafficPolicy: Local on a Service and Cilium kept advertising all of my 3 nodes as possible targets for the Service via BGP.
My Router then send the traffic to Node 2, while the Pod with the Service was on Node 3 and thus no traffic could be received.
Having the BGP announcement align with where the Pod is actually scheduled would be very nice.

https://github.com/cilium/cilium/pull/25477

Now we have merged https://github.com/cilium/cilium/pull/25477. Closing.

Just tested with the latest image and I can confirm it works perfectly fine!
kubectl -n gb get pod -o wide -l tier=frontend
NAME                        READY   STATUS    RESTARTS   AGE     IP              NODE       NOMINATED NODE   READINESS GATES
frontend-556f857fb9-7dmq2   1/1     Running   0          6d15h   <IP_ADDRESS>   pi-k8s-3   <none>           <none>**

Leaf203# show ip route <IP_ADDRESS> vrf rpi-k8s:vrf
<IP_ADDRESS>/32, ubest/mbest: 1/0
    *via <IP_ADDRESS>%rpi-k8s:vrf, [20/0], 00:03:19, bgp-65002, external, tag 65003
         recursive next hop: <IP_ADDRESS>/32%rpi-k8s:vrf

kubectl -n gb get pod -o wide -l tier=frontend
NAME                        READY   STATUS    RESTARTS   AGE     IP              NODE       NOMINATED NODE   READINESS GATES
frontend-556f857fb9-7dmq2   1/1     Running   0          6d15h   <IP_ADDRESS>   pi-k8s-3   <none>           <none>
frontend-556f857fb9-b4fhw   1/1     Running   0          12s     <IP_ADDRESS>    pi-k8s-2   <none>           <none>
frontend-556f857fb9-rmf6d   1/1     Running   0          12s     <IP_ADDRESS>   pi-k8s-1   <none>           <none>

Leaf203# show ip route <IP_ADDRESS> vrf rpi-k8s:vrf
IP Route Table for VRF "rpi-k8s:vrf"

<IP_ADDRESS>/32, ubest/mbest: 3/0
    *via <IP_ADDRESS>%rpi-k8s:vrf, [20/0], 00:00:38, bgp-65002, external, tag 65003
         recursive next hop: <IP_ADDRESS>/32%rpi-k8s:vrf
    *via <IP_ADDRESS>%rpi-k8s:vrf, [20/0], 00:00:38, bgp-65002, external, tag 65003
         recursive next hop: <IP_ADDRESS>/32%rpi-k8s:vrf
    *via <IP_ADDRESS>%rpi-k8s:vrf, [20/0], 00:07:10, bgp-65002, external, tag 65003
         recursive next hop: <IP_ADDRESS>/32%rpi-k8s:vrf

Thank you @YutaroHayakawa for working on this feature!

@YutaroHayakawa  Is it safe to assume that this feature by design will work with any LB type (specifically) service? I am trying to understand how this will behave with for e.g GatewayAPI gateway service and same for cilium's integrated ingress controller where essentially attached service i.e cilium-agent is on every node so will the proxy to target backend service will follow this Local policy?

This feature is all about the type: LoadBalancer service VIP advertisement. So, not relevant to NodePort or ClusterIP. I'm not fully sure about the Ingress/GatewayAPI, but if you are using the type: LoadBalancer service to direct traffic from an external client to Ingress/Gateway proxy, then the answer is yes in theory. I don't know if it makes sense to advertise the VIP of the services behind the Ingress/Gateway.

@log1cb0mb If you are talking about the services that are automatically created by Ingress/GatewayAPI (the service to reach the Ingress/Gateway itself), I wouldn't recommend you set externalTrafficPolicy: Local to those services, because they don't have any endpoints, so it just stops advertisement.

Yes, that is exactly what I was after. Those automatic LB services created by GWAPI and Cilium's Ingress controller but makes sense.
I was just trying to confirm if there is a further way to eliminate potential extra hop with those services.


Revert "Extend forms config to be its own object"

This reverts commit 36dc2bb3aa56bd3446475dc9571e30d7eed22535. See Martin's comment: https://github.com/rainerg2000/pat/pull/4#issuecomment-724351669.

no problem, @xylo04 . I have reverted the changes, but it was easier to do it by hand-editing, instead of merging this PR, because I was already in the middle of merging code from la5nta/develop.
I'm rejecting this PR, but the effect is the same.
So, please pull rainerg2000:issue/135-winlink-forms and rebase your new implementation of the auto-form-download.

Got it, thank you!


I have a device similar to i2c interface, but it is not a standard protocol like i2c. What should I do

I need to control the clock and IO data myself

How to independently control SCK and sdio on raspberry pi

The best option is to open a bunch of GPIO ports on the Pi and bit-bang on the clock and data lines through software.

There are examples?

I think GPIO for java  can't do that. SDIO and SCLK  can be control by ndk ?

@jmying The driver for TM1637 displays is bit-banging kind of a I2C protocol over custom GPIOs (using Java), I guess that is exactly what you'll want: https://github.com/androidthings/contrib-drivers/blob/master/tm1637/src/main/java/com/google/android/things/contrib/driver/tm1637/I2cBitBangDevice.java

@nohum thanks ~

Depending on what you mean with "delay" you could either

sleep via SystemClock.sleep(10) (for e.g. 10ms) or
you could register a GpioCallback via PeripheralManager.getInstance().openGpio() to be notified if your GPIO changes (and then do something with that information).

If you go with option one just pay attention that you do not sleep on the main thread as this will stall the whole app.


change behavior to have cmake-build-dir superseed find-cmakelists in …

Seems like I can get both of the behavior :

use cmake-ide-build-dir if defined
use CMakeLists.txt locate based directory, with cmake-opts if cmake-ide-build-dir is not defined, and store the project build-dir in a hashtable (so cmake-ide-build-dir stay not set when switching projects)

I will be off for the next four weeks (work travel and holidays), feel free to asks questions/debug/modification. I will check this at the end of august.

I just see I could use, if defined, cmake-ide-project-dir as a key.


Redirect "releases"  to "releases/"

Fixes #7987

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d143b28843acabb20abe9c90ffb239f8e53b0d19/

LGTM!
On Wed, Aug 12, 2020 at 12:53 PM cockroach-teamcity <
<EMAIL_ADDRESS>wrote:

Online preview:
http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d143b28843acabb20abe9c90ffb239f8e53b0d19/
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/cockroachdb/docs/pull/7989#issuecomment-672991569,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADVMQGFABBLA4PP335WIPELSALCHLANCNFSM4P47HKFQ
.


Moving development away from github

I'm not familiar with Github, but this is my understanding of it (and of OpenSlides) :

It is proprietary/non-free software.
It is owned by Microsoft
At OpenSlides, looking at the list of participants, >90% of contributions seem to be done internally, not by outside contributors

There are probably many other good reasons to move away from Github (poor privacy policy, hosted in the United States, ...) that would become apparent upon further inspection, but these alone ought to be enough.
Alternatives that I can think of : - Gitea (either self-hosted or there are good gratis providers) - Sourcehut (self-hosted or modest fee) - Gitlab (same, even gitlab.com would be better at this point).
I don't understand what business a project financed by a free software company has doing here.
Hopefully this can lead to a collective discussion/decision-making.

I understand the issue. GitHub itself is proprietary.
But OpenSlides is not. The code is free and we also try to provide any help to everybody who wants to use OpenSlides self-hosted. I know that our documentation is not very good at the moment. The active developers are focusing on fixing bugs and implementing new features (of course for paying customers, this is not unusual as we hopefully all agree). Esp- for OpenSlides 4 we try to provide and easy way to install and start OpenSlides self-hosted using the manage tool.
This has all nothing to do with the question whether to work with GitHub (in a public repository) or not. At the moment the policy of GitHub (and Microsoft behind it and even the U.S. jurisdiction) does not prevent us in developing free software and giving everybody access to it. So I propose to say here as long as this platform has the best features for us. That's may opinion here (at the moment).

I agree with @normanjaeckel. I don't see any issue with an OpenSource project hosting its code on Github - in fact, a lot of companies/projects do that; I would even argue it's a very common thing.

+1 for @normanjaeckel and @jsangmeister

There are a number of good reason to develop Free Software on a different platform than Github. (I'm not going into details here, as they are not the main point as I can see it.) The Openslides development happens here out of its history. And it is difficult to move it somewhere else.
If we'd start a new Free Software product's development now, we do it on a different platform, e.g. with heptapod. But moving an existing development process and community is something else. Still we probably propose to move Openslides off github in the future.

as long as this platform has the best features for us.

This is subject to evaluation. It is quite likely from what I know that the gitlab CC based Free Software platforms like heptapod have surpassed Github proprietary feature set for a while now.

in fact, a lot of companies/projects do that; I would even argue it's a very common thing.

Sure, it is a common thing to do, but this is argument does not carry a lot of weight. It was also common to use Microsofts Word for steering resolutions in an assembly, probably still is, but we do propose Openslides which is uncommon.  Saying things like "don't use github for opensource, because its non-free software" it's like saying "don't use an proprietary cpu to compile your opensource-code, because the microcode of your cpu is non-free software".

@YveIce thanks for sharing your view on the matter.
We will try to focus the discussion on the specific arguments of interest to Openslides and its development and user community. And try to avoid too general arguments.


[Feature Request]  be able to disable KBFS when not connected to the internet

I work in environments on a regular basis that has no networking (no WiFI) or no internet (has WiFi but no internet connection).  It would be nice to be able to tell KBFS to be "offline" so it will stop asking for our passcode/phrase every few minutes interrupting whatever we are doing.  I would say I spend 50+% of my time with no internet access.  for instance when I am in an Airplane, on a train, in a Data Center, etc.

Hm, we shouldn't be asking for your passphrase regularly. Please could you run keybase log send and tell us the ID?

log ID = 9394b22bd1fec03fecfa711c
after the latest update to keybase it still does it just not as often as previous version.


shellcode_hash_search.py has some logic errors

Manually executing shellcode_hash_search on IDA7.5 and Python3 shows some logic problems:
In promptForSearchTypes()
if using_ida7api:
            if idaapi.ASKBTN_YES == idaapi.ask_yn(idaapi.ASKBTN_YES, str('Search for DWORD array of hashes?')):
                self.params.searchDwordArray = True
            if idaapi.ASKBTN_YES == idaapi.ask_yn(idaapi.ASKBTN_YES, str('Search for DWORD array of hashes?')):
                self.params.searchDwordArray = True
        else:
            if idc.AskYN(1, str('Search for push argument hash value?')) == 1:
                self.params.searchPushArgs = True
            if idc.AskYN(1, str('Search for DWORD array of hashes?')) == 1:
                self.params.searchDwordArray = True

I presume the first call should ask for push arguments and set searchPushArgs accordingly.
def promptForHashTypes()
hashTypes = self.dbstore.getAllHashTypes()
if len(self.params.hashTypes) == 0:
raise RuntimeError('No hashes selected')
# we used to prompt y/n for each one. too obnoxious, just force all hashes
self.params.hashTypes = hashTypes
This code will always raise an exception as self.params.hashTypes is always 0 in this case
Will do a fork and fix the code and set a pull request if you'd like

closed via #95


Is this package suitable for processing the passcode on the server?

Hi, I saw in the examples that with this package you have to provide correctString parameter. Can I skip it if I do not know the correct password ahead of time and will only know if it was correct or not after I get the response from the server?
For my use case, the ideal behavior would be exactly like screenLockCreate, but without the password confirm, and with a success callback with value param. Is this doable?
Thank you!

@Reyth3
See the same example below.
https://github.com/naoki0719/flutter_screen_lock/blob/f22571640a2b1f038db3cf185bdf18d263e7e7fb/example/lib/main.dart#L288-L298
ElevatedButton(
  onPressed: () => screenLock(
    context: context,
    correctString: 'x' * 5,
    onValidate: (value) async => await Future<bool>.delayed(
      const Duration(milliseconds: 500),
      () => value == '12345',
    ),
  ),
  child: const Text('Callback validation'),
);

The correctString should be a dummy string to set the length of the input.
For example, correctString: 'x' * 5 for 5 characters.
Next, define the necessary onValidate.
In our example, the length is 5 characters, so this callback will be executed after 5 characters are entered.
The value argument contains the input value, so you can validate it remotely or otherwise and return true to close it.


Fail to compile CLI

I can successfully compile the model but fail to compile cli:
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test SUPPORT_CXX17
-- Performing Test SUPPORT_CXX17 - Success
-- Setting default build type to RelWithDebInfo
CMake Error at CMakeLists.txt:47 (add_subdirectory):
  add_subdirectory given source "tvm" which is not an existing directory.

-- system-nameLinux
-- VERSION: 0.2.00
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
CMake Error at CMakeLists.txt:54 (tvm_file_glob):
  Unknown CMake command "tvm_file_glob".

I met the same problem while using mlc_ai_nightly wheel, but I successfully compiled mlc_chat_cli by building tvm-unity from the source(https://github.com/mlc-ai/relax)

I met the same problem while using mlc_ai_nightly wheel, but I successfully compiled mlc_chat_cli by building tvm-unity from the source(https://github.com/mlc-ai/relax) and setting $TVM_HOME

thank you, i'll try this

I met the same problem while using mlc_ai_nightly wheel, but I successfully compiled mlc_chat_cli by building tvm-unity from the source(https://github.com/mlc-ai/relax) and setting $TVM_HOME

I had same issue. This fixed it for me

Please check our documentation on CLI compilation: https://mlc.ai/mlc-llm/docs/tutorials/deploy-models.html#option-2-build-from-source

Please check our documentation on CLI compilation: https://mlc.ai/mlc-llm/docs/tutorials/deploy-models.html#option-2-build-from-source

thank you very much! I will try that!

see code in scripts/prep_deps.sh, just git clone https://github.com/apache/tvm 3rdparty/tvm --branch unity --recursive and export TVM_HOME="${TVM_HOME:-3rdparty/tvm}"

Please check our documentation on CLI compilation: https://mlc.ai/mlc-llm/docs/tutorials/deploy-models.html#option-2-build-from-source

load error?

Hi @YouCii, we restructured the documentation and that link is outdated. Now the CLI compilation instructions is here https://mlc.ai/mlc-llm/docs/deploy/cli.html#option-2-build-mlc-runtime-from-source


Fixing Typos in Readme.md

Just fixing typos...

Duplicate of https://github.com/microsoft/PowerToys/pull/153 and https://github.com/microsoft/PowerToys/pull/214


update copyright statement

Put links to jekyll and theme on "about me" page

https://github.com/logista/btsite2015/commit/a34392449c255da937ccf2cb34d36e2cb6eea9a9


beautifying js arrays - don't want one per line

Any chance to change the behavior of array beautification? I don't want to make them that tall
I want to let them stay in one line or preserve their own existing line formatting

This option does not helped

Please follow the Issue template provided, it is a requirement not a recommendation. For your convience, here it is again: https://github.com/Glavin001/atom-beautify/blob/master/ISSUE_TEMPLATE.md
The most important part being the Gist containing your debugging information. That information would help @prettydiff or myself resolve many questions I will be asking without a tedious back and forth.
I await your debugging information. Thank you.

I will be working this through https://github.com/prettydiff/prettydiff/issues/276
I will have a different similar option for objects.  The goal will be to allow default behavior, always flattened arrays, or never flattened arrays.

This is fixed on the Pretty Diff side.  A new option exists named formatArray.  Please submit a pull request exposing this option to Atom Beautify.
http://prettydiff.com/documentation.xhtml#formatArray

How do I use this in Atom?

@chrisdel101 It should be in the beautifier options for language JavaScript if Pretty Diff is your JavaScript beautifier.

I can't find it. I'm in the Javascript  & JSX settings. This is occuring in JSX at the moment. I couldn't find the format_array or formatarray. U give me a hint? Sorry if I am just not seeing it.

It may not have been added.  The option was one of the last things I added before I halted work on version 2.  @Glavin001 do you remember if this option was added to the config?


add option to skip loading resources from den

#1096  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jlewitt1 and the rest of your teammates on  Graphite


Question Re: QA

Is this available to run on a personal machine and bug-hunt? I'd love to help out with any QA-related stuff — just lmk what y'all need!

Thanks @edouerd but it's almost entirely bugs at this point :)
Once we get a little bit closer to the finish line (even on some basic features), I can send you instructions to access the beta.
THANK YOU!

@broskoski hell yes, good to hear!
Soooo excited for this


Informational: Supermarket influxdb updated to this cookbook

Hi,
I have uploaded 2.6.0 of this cookbook to Chef's Supermarket as "influxdb", thereby replacing the cookbook available at: https://github.com/zeroXten/influxdb-chef which is now deprecated.
The Supermarket URL is https://supermarket.chef.io/cookbooks/influxdb

Closing this, see #23


Removing Unsafe.set_atom_field

Pull Request Description
Introducing Meta.lazy_atom to create an Atom with a hole.
Important Notes
Checklist
Please include the following checklist in your PR:

[ ] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.

Also, do you have any info on the performance impact of this?

Here is a benchmark measuring List.map - 695775b - currently it is not fast and I need to check IGV to find out what can be improved.

I think we are ready to integrate. The only problem is 2-3x slowdown - but I'd like to resolve it later. Right now I feel there are other important issues to focus on.


Windows integration test failures

Failures:

  1) chef-solo when the chef repo has a cookbook with an undeclared dependency should exit with an error
     Failure/Error: expect(result.exitstatus).to eq(0) # For CHEF-5120 this becomes 1

       expected: 0
            got: 3

       (compared using ==)
     # ./spec/integration/solo/solo_spec.rb:120:in `block (3 levels) in <top (required)>'
     # ./spec/spec_helper.rb:303:in `block (2 levels) in <top (required)>'

  2) chef-solo when the chef repo has a cookbook with an incompatible ohai_version should exit with an error
     Failure/Error: expect(result.exitstatus).to eq(1)

       expected: 1
            got: 3

       (compared using ==)
     # ./spec/integration/solo/solo_spec.rb:154:in `block (3 levels) in <top (required)>'
     # ./spec/spec_helper.rb:303:in `block (2 levels) in <top (required)>'

https://buildkite.com/chef/chef-chef-master-omnibus-release/builds/1186#39d32184-68ea-4ff4-a56c-e0821b4b736e

It sounds like this is resolved with our parallelizer fixes


Add more statistics to the benchmark

Codecov Report
Attention: Patch coverage is 84.97217% with 81 lines in your changes missing coverage. Please review.

Project coverage is 77.25%. Comparing base (50d66e0) to head (6706bf7).
Report is 2 commits behind head on main.

Files
Patch %
Lines

...riment/torch_bench/_bash_bench_benchmark_runner.py
48.19%
43 Missing :warning:

...experiment/torch_bench/_bash_bench_model_runner.py
50.00%
24 Missing :warning:

...nt/torch_bench/_bash_bench_benchmark_runner_agg.py
98.67%
5 Missing :warning:

experimental_experiment/bench_run.py
42.85%
4 Missing :warning:

...al_experiment/xoptim/patterns_exp/simple_rotary.py
42.85%
4 Missing :warning:

...erimental_experiment/torch_bench/bash_bench_agg.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #182      +/-   ##
==========================================
- Coverage   77.84%   77.25%   -0.59%
==========================================
  Files         126      128       +2
  Lines       15626    16355     +729
==========================================
+ Hits        12164    12635     +471
- Misses       3462     3720     +258

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Trouble with IFacetHandler.GetFieldValue

@NightOwl888
I found some problems with the method IFacetHandler.GetFieldValue.
Could you check the following test method?
[TestMethod]
public void Test()
{
	Stopwatch stopWatch = new Stopwatch();

	// Create index.
	string indexPath = @"c:\temp\test";
	int numDocs = 10;
	using (Lucene.Net.Store.Directory directory = FSDirectory.Open(new System.IO.DirectoryInfo(indexPath)))
	{
		string text;
		using (IndexWriter modifier = new IndexWriter(directory, new StandardAnalyzer(Lucene.Net.Util.Version.LUCENE_30), true, Lucene.Net.Index.IndexWriter.MaxFieldLength.UNLIMITED))
		{
			for (int i = 0; i < numDocs; i++)
			{
				text = "asisdfowefposjverovn";
				Document doc = new Document();
				doc.Add(new Field("text", text, Field.Store.YES, Field.Index.ANALYZED));
				modifier.AddDocument(doc);
			}
		}
	}

	// Facets.
	IFacetHandler textFacetHandler = new SimpleFacetHandler("text");
	ICollection<IFacetHandler> handlerList = new IFacetHandler[] { textFacetHandler };

	// Open index.
	using (Lucene.Net.Store.Directory idx = FSDirectory.Open(new System.IO.DirectoryInfo(indexPath)))
	{
		using (IndexReader reader = IndexReader.Open(idx, true))
		{
			// Open bobo reader.
			using (BoboIndexReader boboReader = BoboIndexReader.GetInstance(reader, handlerList))
			{
				// Extract text.
				int n = reader.NumDocs();
				for (int i = 0; i < n; i++)
				{
					string field = textFacetHandler.GetFieldValue(boboReader, i);
					Assert.IsFalse(string.IsNullOrEmpty(field));
				}
			}
		}
	}
}

It generates the following error while it retrives the field value System.IndexOutOfRangeException crossed a native/managed boundary.

There are 2 different issues here.
First of all, it says specifically in the documentation that SimpleFacetHandler requires its field to be non-tokenized.
Second, from my understanding facet handlers are designed to be used internally by the BoboBrowser,  not to be called directly. Nearly every use case with BoboBrowse calls BoboBrowser.Browse(). I am not sure exactly what your use case is here, but if you are trying to read back field data from the index, you would need to use Lucene for that. I found this article that demonstrates how to do it.
// Open index.
using (Lucene.Net.Store.Directory idx = FSDirectory.Open(new System.IO.DirectoryInfo(indexPath)))
{
	using (IndexReader reader = IndexReader.Open(idx, true))
	{
		TermEnum terms = reader.Terms(new Term("text"));
		for (Term term = terms.Term; term != null; terms.Next(), term = terms.Term)
		{
			var value = term.Text;
			Console.WriteLine(value);
		}
	}
}

I am testing the fast field retrieval functionality.
From Lucene in action Second Ed.:

Bobo Browse can retrieve the field values for a specific document ID and field name.
With Lucene, a Field with the Store.YES attribute turned on can be stored:
doc.add(new Field("color","red",Store.YES,Index.NOT_ANALYZED_NO_NORMS));
then retrieved via the API:
Document doc = indexReader.document(docid);
String colorVal = doc.get("color");
We devised a test to understand performance better. We created an optimized index
of 1 million documents, each with one field named color with a value to be one of
eight color strings. This was a very optimized scenario for retrieval of stored data
because there was only one segment and much of the data could fit in memory. We
then iterated through the index and retrieved the field value for color. This took
1,250 milliseconds (ms).
Next, we did the same thing, but instead of creating a BoboIndexReader with a
FacetHandler, we built on the indexed data of the color field. We paid a penalty of 133
ms to load the FacetHandler once the index loads, and retrieval time took 41 ms. By
paying a 10 percent penalty once, we boosted the retrieval speed over 3,000 percent.

This functionality was working into the @zhengchun porting independently from the field analysis.

The example from that chapter functions as expected:
public void Test()
{
	Stopwatch stopWatch = new Stopwatch();

	// Create index.
	string indexPath = @"c:\temp\test";
	int numDocs = 10;
	using (Lucene.Net.Store.Directory directory = FSDirectory.Open(new System.IO.DirectoryInfo(indexPath)))
	{
		string text;
		using (IndexWriter modifier = new IndexWriter(directory, new StandardAnalyzer(Lucene.Net.Util.Version.LUCENE_30), true, Lucene.Net.Index.IndexWriter.MaxFieldLength.UNLIMITED))
		{
			for (int i = 0; i < numDocs; i++)
			{
				text = "asisdfowefposjverovn";
				Document doc = new Document();
				doc.Add(new Field("text", text, Field.Store.YES, Field.Index.NOT_ANALYZED_NO_NORMS));
				modifier.AddDocument(doc);
			}
		}
	}

	// Facets.
	IFacetHandler textFacetHandler = new SimpleFacetHandler("text");
	ICollection<IFacetHandler> handlerList = new IFacetHandler[] { textFacetHandler };

	// Open index.
	using (Lucene.Net.Store.Directory idx = FSDirectory.Open(new System.IO.DirectoryInfo(indexPath)))
	{
		using (IndexReader reader = IndexReader.Open(idx, true))
		{
			// Open bobo reader.
			using (BoboIndexReader boboReader = BoboIndexReader.GetInstance(reader, handlerList))
			{
				// Extract text.
				int n = reader.NumDocs();
				for (int i = 0; i < n; i++)
				{
					Document doc = boboReader.Document(i);
					string field = doc.Get("text");
					Assert.IsFalse(string.IsNullOrEmpty(field));
				}
			}
		}
	}
}

I looked through the book, but at no point can I find an example where they are calling the facet handler directly.
However, I spotted the problem with your code. The 3.2.0 BoboIndexReader design has changed in that it now has a collection of subreaders nested within the parent reader. On a single browse request, there is just 1 subreader at index 0. So, you could change your code to:
for (int i = 0; i < n; i++)
{
    string field = textFacetHandler.GetFieldValue(boboReader.SubReaders[0], i);
    Assert.IsFalse(string.IsNullOrEmpty(field));
}

Still, I would recommend calling the Document() method as specified in the book because it will shield you from any future design changes or problems arising from multi-browse requests that have more than one subreader.

Usually, I have more than 1 subreader because my lucene index has many segments.
Could you implement a solution like this? Is it already implemented and it does not work?
Do you know if using the Document() method it is possible to obtain the gain in performance as described in Lucene in Action Second Ed.?

Oh, I just noticed that the SubReaders property is internal, so it cannot be used this way. That was a design decision in Java that was copied over into .NET.
The link you provided is to the original Java source of BoboBrowse 3.2.0, and it corresponds to the GetFieldValue method in this repository. As you can see, it is implemented exactly the same way. But it requires the BoboIndexReader to be a subreader in order to function.
If you have a look at the BoboIndexReader.Document(int) method, you can see how it handles the subreader logic and if the reader itself is a subreader calls GetFieldValues, which must be overridden in the FacetHandler. The exact way it is implemented depends on the facet handler. SimpleFacetHandler looks like this:
public override string[] GetFieldValues(BoboIndexReader reader, int id)
{
	FacetDataCache dataCache = GetFacetData<FacetDataCache>(reader);
	if (dataCache != null)
	{
		return new string[] { dataCache.ValArray.Get(dataCache.OrderArray.Get(id)) };
	}
	return new string[0];
}

As for performance gains over Lucene.Net, you will need to benchmark it for yourself with a similar sample size of 1 million documents and 8 evenly distributed values. There might not be as much of a difference, because of differences in the way that .NET and Java manage memory and data types. But it also depends on how Lucene.Net optimized the field retrieval compared to its Java counterpart.

I made the test and I found that Bobo is much slower than Lucene. Thus, using Document() is not equivalent to GetFieldValue().
For the moment I consider the fast field retrieval not available. This is not a big deal for me, but let me know if you want to improve this aspect of your solution.

Keep in mind, Lucene in Action, Second Edition was published in 2010. BoboBrowse 3.2.0 was released on March 23, 2013. So much of what is in Lucene in Action is out of date with respect to BoboBrowse. BoboBrowse 2.5 was released in mid 2010, so it is difficult to tell if they are basing those results on 2.0 or 2.5.
That said, it is not that surprising that the results are different. I ran a few experiments:

I changed the PredefinedTermListFactory to use a switch case statement instead of Reflection to create the TermXXXLists.
I ran a test to see what would happen if I changed the type of the BoboIndexReader _facetDataMap member variable from IDictionary<string, object> to IDictionary<string, Interface>.
I compared the performance of using a local variable to store an object (as was done in 2.0) with the performance of storing the object in an IDictionary<string, object> in a separate object.

The first two experiments gave no significant performance improvement. The third showed that the way the data cache was stored in 2.0 is about 18x faster to access then the way it is done in 3.2.0.
I also saw that just a single browse operation (the BoboTestCase.TestDate test) calls the method to access the data cache several hundred times (308 in the test), so optimizing it could produce a significant impact on performance. Unfortunately, I was unable to find a method that works faster than the way it is currently done.
Clearly there were some trade offs in the 3.0 design. Access to the centrally located data cache is slower. But putting the cache data in a central location is necessary to support the custom sorting functionality. The dictionary the cache is stored in is also put into a thread-safe wrapper, which again slows things down a bit as a trade for thread safety.
However, performance still seems more than adequate for basic browse scenarios. I haven't run any of the unit tests for BoboBrowse 3.2.0 in Java, which would be a true apples-to-apples comparison, but based on my experiments it looks like it is about as optimized as it can be. I don't see that there is much of a chance to get it running faster than it does without significantly changing the design or compromising thread safety.
But let me know if you find any bottlenecks that could be improved upon.


Update guidelines for guidelines

There are a couple of issues with the meta-guidelines:

Currently, if you want to assign a guideline to a category, you must use an emoji in the guideline header. There are two problems with emoji: they are difficult to work with (try selecting one!), and they can mean different things to different people. The Vite Style Guide uses letters as aliases for categories, and this works well because they're just ASCII characters, and everyone understands that a category ranked A is higher / more important than a category ranked B.
To solve this, we now use letters instead of emoji. We also link that letter to the guideline that lists the categories; this way, if anyone forgets, they can quickly jump there.

The guideline that describes how to present a dichotomy — a non-recommended way to do something and a recommended way to do it — allowed for unclear wording.
To solve this, we propose one way and offers an example people can copy.

Besides these issues, this commit also cleans up some of the wording in the document. The "be empowered" guideline is also removed as it really applies to the entirety of this repo, not just guidelines (it will be added back in another commit).
👉🏻 Rendered version 👈🏻

Still workshopping this :)

This is now ready for review again.