Connection ERROR

I've set my own proxy in the config file.
Anyone came into this problem?
openai.error.APIConnectionError: Error communicating with OpenAI: HTTPSConnectionPool(host='api.openai.com', port=443): Max retries exceeded with url: /v1/embeddings (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'api.openai.com'. (_ssl.c:997)")))

We have also encountered this issue before and there is currently no good solution. You can choose a local embedded model to replace the OpenAI interface.

I've set my own proxy in the config file. Anyone came into this problem? openai.error.APIConnectionError: Error communicating with OpenAI: HTTPSConnectionPool(host='api.openai.com', port=443): Max retries exceeded with url: /v1/embeddings (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'api.openai.com'. (_ssl.c:997)")))

Can you take a look at your config settings.If you want to facilitate communication, you can join our WeChat and add my friends

@jianghuyihei I just want to run the example code on my lab server, and the proxy I set is American node. BTW, I've joined the WeChat group, thanks a lot!

@jianghuyihei I just want to run the example code on my lab server, and the proxy I set is American node. BTW, I've joined the WeChat group, thanks a lot!

You can add my friends, and the group leader is me


Mailgun seems abandoned.

@chrismccord are you looking for a new owner? We are glad you put this together, but it would appear the issues and pull requests have been piling up for the last year and the new release on master hasn't been released yet.
We have forked and will continue our own development, but it would be nice to keep in the loop of any future improvements you and the contributors have planned.
Thanks!

Any updates???

Dear @chrismccord if you no longer have time to maintain this package I suggest you transfer the ownership to someone or deprecate it. It's bad karma to leave packages unattended :)

Any update? I think we should try to avoid forking if possible. But we need to maintain this package.

Dear @chrismccord,
Appreciate your generous contribution in this open source project! :-)
Could you update or transfer ownership to a team so that the library can be been improving by the community?

I moved to https://github.com/thoughtbot/bamboo and I suggest you do the same, it's well maintained.


Slightly confused by wording on Readme

Thank you for the work on this plugin.
"Elasticsearch Reindexing Plugin provides a feature to create a new index from an existing index. If you want to add new analyzers or make changes to existing fields, you need to re-create your index."
Does this mean that I am not able to use the reindex feature if the new index has new mappings? Seems like that is where most of the usefulness of this tool would lie no?

elasticsearch decides mappings automatically if you do not create  a target index before reindexing.

It also let's you manually define custom mappings for attributes to prevent errors by guessing. So It seems my question still stands.
Am I not able to use the reindex feature if the I want to set different mappings for specific attributes on the new index?


bug: undercurls applied to notification window

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
macOS 15.1.1
Describe the bug
Using the default config, I'm seeing undercurls in the notification window:

I've seen the other bug describing a similar issue (#271), but this one is slightly different since the undercurls are being applied to the notification directly, not coming from the buffer underneath. I was previously using Noice without this issue happening.
Steps To Reproduce
Unclear, all I did was add snacks.nvim and enable the notifier module.
Expected Behavior
The notification should appear as it does in the documentation.
Repro
No response

That's your colorscheme that needs to be fixed.


Extend insert into to support Parquet backed tables

Which issue does this PR close?
None, but progresses towards the goals of https://github.com/apache/arrow-datafusion/issues/5076 and https://github.com/apache/arrow-datafusion/issues/7079. Follow on to https://github.com/apache/arrow-datafusion/pull/7141 and #7212 .
closes #7036
Rationale for this change
Inserting to parquet backed tables is a common use case. The file format itself does not support appending to an existing file, so only appending new files to a table is supported.
This implementation relies on AsyncArrowWriter to handle coordination between the Parquet serializer and ObjectStore writer. So, the implementation for parquet insert into support diverges a bit from JSON and CSV.
What changes are included in this PR?

Added parquet write config options to ExecutionOptions
Allow specifying parquet schema so empty tables can be created
Move write specific code to write.rs mod
Add test coverage for inserting to parquet table with or without session config changes

Are these changes tested?
Yes.
Are there any user-facing changes?
Inserting to parquet backed tables is possible.

@alamb @metesynnada Interested in your thoughts on the approach here specifically on putting parquet write options in the session config and using AsyncArrowWriter from the parquet crate vs. a custom implementation within DataFusion.

Thanks @devinjdangelo  -- I am sorry I am about to run out of time today, but I plan to review this PR carefully tomorrow


feat(share_plus): Show preview title in iOS share sheet (#190)

Description
Fixes one of the issues reported in #190 where the iOS share sheet would show a blank preview instead of the given text.
Verified working on iOS 14.4, 12.0 simulators
Related Issues
#190 [share_plus] Text not showing in share modal and web opens a new tab to about:blank
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Melos analyze is passing locally for me, but failing here on android_alarm_manager_plus, which I didn't change.
Is there a way to rerun the analyze Github Action?
melos exec
   └> pub publish --dry-run
       └> FAILED (in 1 packages)
           └> android_alarm_manager_plus (with exit code 66)

I triggered a rerun, somehow GH is having this random issues. Code looks good to me but I would like to test it before merging, which I will do in the coming days. Thanks a lot for the contribution!

The formatting was cancelled due to a timeout. You should probably merge main into this branch. I had the same issue on my PR

Got to try this now, thanks for the fix! merging now

Am I correct this shows text instead of subject?
(It works when providing the text parameter, but then if the file is saved to (e. g.) the Apple Files app, it also saves a blank file (and the image I wanna share) with just the text I wanted in the share sheet.)

@TheJulianJES Yes, it currently uses the value of the text parameter as the preview title
Just so we are on the same page, the issue you are experiencing is:
Action 1:

show share sheet with subject parameter set, but no text parameter
save image to Apple Files

Result 1:

share sheet preview title is empty
image is saved to Apple Files

Action 2:

show share sheet with subject parameter and text parameter set
save image to Apple Files

Result 2:

share sheet preview title shows text parameter value
image is saved to Apple Files
blank file is saved to Apple Files containing the text parameter value

What you would expect to happen is:
Action:

show share sheet with subject parameter set, but no text parameter
save image to Apple Files

Result:

share sheet preview title shows subject parameter value
image is saved to Apple Files
(no additional files are saved to Apple Files)

Yep, that's exactly what I would expect :) (Doesn't seem like subject is used anywhere -- at least on iOS?)


Change Set view is slow to load for sets with >10 change units

Possibly a performance issue with rendering.
Consider re-jigging view to master-detail to improve performance and reduce clumsy feel of current.

Fixed as part of a changeset view re-write


Ark schedule --ttl flag not working

Hi All,
I have a k8s cluster where i have deployed ark and have scheduled a backup using
ark schedule create default-ns  --schedule "0 7 * * *" --snapshot-volumes --ttl 5m
the backups are getting expired but the resources of that particular backup i.e snapshots ,backups,none of them are getting deleted.

could you run ark backup describe NAME for one of the backups that you expected to have been deleted?

ark backup describe name gives the output as
Name:         default-ns-20190129042303
Namespace:    heptio-ark
Labels:       ark-schedule=default-ns
ark.heptio.com/storage-location=default
Annotations:
Phase:  Completed
Namespaces:
Included:  default
Excluded:
Resources:
Included:        *
Excluded:
Cluster-scoped:  auto
Label selector:
Snapshot PVs:  true
TTL:  1m0s
Hooks:
Backup Format Version:  1
Started:    2019-01-29 04:23:07 +0000 UTC
Completed:  2019-01-29 04:23:24 +0000 UTC
Expiration:  2019-01-29 04:24:07 +0000 UTC
Validation errors:
Persistent Volumes:

ark schedule create default-ns --schedule="@every 3m" --include-namespaces default --snapshot-volumes --ttl "1m"
i used this command to create the schedule

OK - could you also provide some of the ark server logs (kubectl -n heptio-ark logs deploy/ark) from around the expiration time listed above?

there are not server logs at that time. i even checked the logs at the time of expiration.

OK - could you provide the full logs then?
Also - could you provide the output of kubectl -n heptio-ark get deploy/ark -o yaml?
Also - setting the log-level to debug may provide additional information.  You can find instructions for that on https://heptio.github.io/velero/v0.10.0/troubleshooting, under "Getting ark debug logs".

By full logs do you mean full logs at the time it takes backup? and also do i have to add debug flag in the ark deployment?

logs.txt
these were the logs i found after attaching those flags,
Also this was taken once the schedule exxpired.

@skriss
Any help regarding this problem?

@Sharath52 it would be really helpful if you could provide (please provide all of these outputs, exactly as requested):
kubectl -n heptio-ark get schedule <NAME> -o yaml (for your schedule)
kubectl -n heptio-ark get backup <NAME> -o yaml (for a representative backup created from the above schedule)
kubectl -n heptio-ark describe backup <NAME> (for the same backup as the previous line)
kubectl -n heptio-ark logs deploy/ark covering the full time period from the start of the backup, to past the time where the backup is not properly deleted after expiration.
Since the logs you provided are from a different time than the backup you described, and don't actually capture the execution of the backup or the time period where it should've been expired, I don't have enough information to help.

logs-heptio.pdf
i have provided all the outputs exactly as requested and for that particular schedule.

the controller that detects expired backups and triggers a deletion only runs once per hour - so in the log you provided, it does appear to be running, but you may have to wait up to an hour to see these backups be deleted. Did they (e.g. backup default-ns-20190213100754) eventually delete after an hour or so?

No,i waited a long time ,more than a day maybe.none of the backups are getting deleted.Only when i delete the backups manually the snapshots are getting deleted .But not with Schedule

OK - would you be able to send the logs starting from the same place (time="2019-02-13T10:07:54Z" level=info msg="Creating schedule default-ns" controller=schedule logSource="pkg/controller/schedule_controller.go:104") but continuing for 2 full hours?

i have recreated the deployment,so i might not be getting the logs from that time.I'll create a new schedule and will probably try to send the logs.

@Sharath52 did you get to the bottom of this?
rel. #1215

Closing due to inactivity. Feel free to reopen as needed.


Update Commands.py

Applied the same optimization as the one used in #16
What does this PR do?
Optimization.

Smaller space + better performance! 😄

I'm assuming your tired of the optimizations.

I'm assuming you didn't read my comment on the minimization issue. I'm gonna be creating contribution guidelines eventually btw, if you're gonna pull make sure it's a substantial change. Pulling single-line edits multiple times a day isn't something I want to spend time on

So you want me to make several changes and then pull?


Daemon Optimisation

Maybe the daemon could not try to read the serial device each time we request http://localhost:9101/metrics ?
As it is a slow device, should be better the daemon decide when he read the device and give a cached result ?
I got:

With the following Promotheus config:
scrape_interval: 30s
scrape_timeout is default so 10s ?

If the exporter is very slow in standard mode, I will change the concept and separate the connector from the collector action and adding cache.
In Historical mode on a Rpi Zero, it’s took 2 or 3 seconds.
I will change my linky mode after historical dashboard creation.

Salut,
nice thanks so much !
https://grafana.aquilenet.fr/d/Jk_wOM5Vz/fr-linky-exporter?orgId=1&refresh=1m

Hey,
It's good to see it working :)
A better dashboard version to only Standard mode will appear soon ;)


Updating longhaul to 1.11.0 release

Description
Please explain the changes you've made
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Extended the documentation

Oh! Ok. I will update it to the release version only and find a way to
enforce stable components consistently later.
On Fri, Jun 9, 2023 at 16:51 Artur Souza @.***> wrote:

@.**** requested changes on this pull request.
In .github/workflows/dapr-deploy.yml
https://github.com/dapr/test-infra/pull/176#discussion_r1224901394:

@@ -15,7 +15,7 @@ jobs:
runs-on: ubuntu-latest
env:
DAPR_INSTALL_URL: https://raw.githubusercontent.com/dapr/cli/master/install/install.sh

 DAPR_RUNTIME_VER: 1.11.0-rc.9

 DAPR_RUNTIME_VER: 1.11.0-stablecomponents

It does not work because we don't have control plane with this tag.
—
Reply to this email directly, view it on GitHub
https://github.com/dapr/test-infra/pull/176#pullrequestreview-1473193178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAW4QMV74OE6FZS5KHTYBLXKOZH5ANCNFSM6AAAAAAZBHDX5Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Cheers. Tiago Alves Macambira -- Sent using a smartphone. Disregard typos.

please use latest version here

this PR is now irrelevant, closing.


Miniplayer Expands

Allow users to expand the miniplayer to actually stream the channel in the app.

Should work similar to the YouTube app. Have the streamed channel appear at the top of the screen and when the phone is turned landscape, the video expands to fill the landscape view.

This opens a new activity with any orientation

Will be available through a new dialog button in 1.3.6 / 1.4.0


RuntimeError ：Missing key(s) in state_dict: "bert.embeddings.position_ids".

when I run predict.py,the error happen in loading state_dict for VUPScorer

I have the same question。U solve it?


toggleDrawer does not work when app is first opened

Both DrawerActions.toggleDrawer() and navigation.toggleDrawer() do not work when the app first opens on iOS (works just fine on Android) but when I do a manual reload, the methods I mentioned up above work just fine. When I console log the function in both scenarios (before manually reloading and after) I do get the results back. I have also tried downgrading react-navigation-drawer to 2.2.1 but still got the same results
Here is my function:
  toggleDrawer = () => {
    const {navigation} = this.props;
    console.log('DrawerActions :', DrawerActions.toggleDrawer);
    navigation.dispatch(DrawerActions.toggleDrawer());
  }

Package.json

react-navigation
4.0.10

react-native
0.61.2

react-native-gesture-handler
1.4.1

react-native-reanimated
1.3.0

react-navigation-drawer
2.2.2

Hey it would be nice if you could provide runnable repo. Thanks

My teammate found out the issue, in my AppNavigator I refer to the Dimensions object provided by React Native to set the width of my drawer. On app start the width and height properties are set at 0 for whatever reason (it did not do this prior to upgrading the app a few days ago). When I reload the app I get the correct dimensions and so that is why the drawer worked. This is a separate issue. Thanks for the reply anyways! @pzatorski
Code for reference
const ExploreNavigatorDrawer = createDrawerNavigator(
  {
    ExplorePage: {
      screen: TabNavigator,
      navigationOptions: {header: null},
    },
  },
  {
    drawerPosition: 'right',
    contentComponent: FiltersDrawer,
    drawerLockMode: 'locked-closed',
    drawerWidth: Dimensions.get('window').width * 0.9,
    swipeEnabled: false,
  }
);


Implement GOSS_FILES_STRATEGY for dcgoss

dcgoss lacks GOSS_FILES_STRATEGY. It is not used while readme.md suggest it does.

LGTM, but I didn't test it.
Tagging @fbartels since he is the original author of dcgoss. Can you review these changes?
If he doesn't respond I'll test/merge this later in the week.

Thank you for taking the time to contribute to goss.

@aelsabbahy Thank you, again, for the wonderful library. The cp strategy is required in my case for running goss during CI/CD.
The implementation is a tiny little different from dgoss. With dgoss you first create the container, copy the files and then run it. However, the create subcommand with docker-compose is deprecated and would not work anyhow. Therefore the files are copied after the run command for the container has been called. This is not a problem, because the files in question are the goss files, and they are not needed during the boot of the container.

Makes perfect sense. Thanks for the explanation, been ages since I used docker-compose.

It's especially useful when the container has dependencies to other containers.

Fixed

Thanks for the help

You fixed only the first ;-) $service:/goss also needs to be quoted.

Thanks for the contribution!


DRAFT: Fuzz Warning

Draft
Seeing a lot of this:
/usr/local/lib/python3.7/site-packages/thefuzz/fuzz.py:11: UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning
  warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')

Upgrade the fuzz library or install python-Levenshtein to alleviate the warning, and possibly improve performance.

We are only fuzzy matching a few dozen items so we initially though that there was no need to install the native C implementation. This warning causes enough log pollution that we should see if installing the native helper is simple and robust.


CONFIG(12): Configurando o CORS config.

close #12

Codecov Report

Merging #13 (9771985) into main (7480a4c) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
+ Coverage   94.40%   94.42%   +0.01%
==========================================
  Files          28       28
  Lines         483      484       +1
==========================================
+ Hits          456      457       +1
  Misses         27       27

Impacted Files
Coverage Δ

jornada_milhas/settings.py
91.89% <100.00%> (+0.22%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Search in all files to find matches immediately

Ctrl+Shift+F - Search in all files in opened folder to find matches immediately instead of waiting for us to hit enter - as in IntelliJ

We have looked at this in the past but our search is not fast enough and the tree view on the frontend is also not fast enough to support it.

I guess there is a trade-off between IJ indexing for long in the foreground vs editor being available for use huh...maybe someone needs to come up with a way to do this (indexing) in lo-prio in the bkgrnd


On Mobile Safari (i.e. iPad), it's possible to close the output tab and lose the ability to open it again

Hi,
I noticed that on the iPad in Safari, it's possible to close the output tab, and because of the way that rust.godbolt.org is caching state, it's subsequently impossible to restore the tab, even after refreshing the page.

Thanks for the bug report. A new output window ought to open if you click the far right icon on the editor pane (the bar with the up arrow above it). There may be other issues though, touch support isn't all that great (see #176)

Hi Matt, on desktop that works but on the iPad that button doesn't do anything most of the time.

That's super weird. I don't know what might be going on: I may need a mobile expert (and/or to get deepstreamIO/golden-layout#166 or deepstreamIO/golden-layout#148 fixed too)

As a workaround: If there's a way to clear local storage for a single site on iPads, give that a go. I suspect not though

...or maybe try following a link like this: https://godbolt.org/g/5pZN98 which will hopefully reset it

Thanks; I'll see what I can change on my side. A UI reset seems reasonable.
On Tue, Dec 27, 2016 at 9:54 AM Learn OpenGL ES<EMAIL_ADDRESS>wrote:

I think it is possible but not practical as the UI to do that is really
bad in iOS settings if you have a lot of sites in there.
Opening a private window does work and gives you a clean slate. The link
you attached also works!
I guess for right now a button or link to reset the state would do the
trick?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/mattgodbolt/gcc-explorer/issues/217#issuecomment-269342641,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmsdQIS5heXdNMEbAMUyBJPdQilAZXLks5rMTKHgaJpZM4LVwN_
.

There's now a UI reset in "Help".


debug on Dorsal

this is an initial approach to having debugging information in dorsal.

yes, it uses a console.log and console.timer but is intended for developers.

to turn it on we can just do Dorsal.DEBUG = true

is only affecting the actual _runPlugin and the setTimeout wraping _wireElement function , my idea is deciding where and what should be the next messages.

I think this is a good start. Great work! We could probably do even more to help developers debug issues. We can do that as time goes on though.


✨ install constraint env

install the constraint environment if it doesn't exist
closes #25

Hah cool! Who would've thought that you can just create an instance of an environment and use it

Yeah I'm not sure if the key here was setting app = None or not - but I didn't think this would actually work until I peeked into the virtual environments themselves and ensured everything was being done correctly. Pretty dang neat.

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Revert "Revert "Balder/only rewrite numeric terms for text fields""

Reverts vespa-engine/vespa#29776

@toregge PR, now system test passes.


Prevent deletion of the default stream

As an organization admin, I want the default stream for my organization to be protected from deletion so that it can’t accidentally be deleted.
see discussion on #489.
implementation notes:

[ ] update StreamsController#destroy to check if the stream being deleted is the default, and if so, deny the request. the response code might be 400 or 403, although evidently 423 ("Locked") is also a thing.
[ ] remove the UI option/button to destroy the default stream in views/streams/index.html.erb

Instead of doing the check in the controller, I think we can and should add the check in Ability (and get the UI piece for "free").


Improve Brainfuck comment detection

In brainfuck, if you reach a loop using the '[' and ']' characters and
the current cell has a value of 0, the loop is skipped. This is
sometimes used as a trick to allow for comments containing punctuation
that conflicts with brainfuck commands. For example, you can put the
following at the very beginning of your brainfuck code:
[
This is my comment! I can use all sorts of characters like , and
. which I would not be able to use normally.
]
You can also set the value of the current memory cell before the loop to
0 to force the loop to be skipped. This can be done with the [-] or [+]
loops:
[-][This is another comment, and it has a period and comma.]

Thanks for preparing this! Could you please add an example snippet so this is actually tested?


APIs for implementing supervisor and its configuration file

This changeset describes several interface that an agent must implement
in order to fit itself in the supervisor model.
The basic idea is that:

We implement several of these interfaces as part of the reference
implementation.

Many of those default implementations may work with most agents but
some might be tailored fro OT Collector.

Custom OT collectors or other custom agents may change the
implementations. As long as the interfaces are honored, the rest of the
supervisor should work.

Posting a few more observations that I made while working on this:

On health check: the health check configuration is largely inspired by Kubernetes liveness probe. It currently supports a HTTP probe. However, much like Kubernetes, we can also support a exec-based probe. See https://v1-19.docs.kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

On config specification: currently, the config specification is simplistic: a config file and whether or not it requires a reload-on-change. I think this idea can be expanded to allow for more complex configuration situations where the agent's configuration can be constructed from different sources --- collector, for example, allows configuration to be specified from a file, environment variables or even network. In such cases, it would be good if an endpoint on the collector is exposed from where its effective configuration can be obtained. Similarly, the new configuration can be applied as a PUT on a HTTP endpoint as well? Maybe something like this:

config:
    read:
        # source: file:/opt/opentelemetry-collector/config.yaml
        source: http://localhost:1010/config # GET
        content_type: application/yaml
    write:
        # dest: file:/opt/opentelemetry-collector/config.yaml
        dest: http://localhost:1010/config # PUT
        content_type: application/yaml
    auto_reload: false

On the Identifier: this interface seems a bit awkward. An alternate way of representing this would be for the agent.Agent to implement GetIdentifyingAttrs that returns a []*protobufs.KeyValue. My concern, however, is that the protobufs.KeyValue allows an implementation to ignore specifying service.name or service.instance.id which in-turn can result in some error cycles when communicating with the server which can be avoided. Identifier, on the other hand, forces the implementer to provide an implementation thereby relieving some of those concerns.

On watcher: I wrestled for a while on allowing the watcher to be optional (as suggested in the supervisor doc by @tigrannajaryan) and if the agent is already managed by something like systemd, let it be -- but the more I thought about it, the more it seems that it is best if the supervisor always keeps the agent as its child process and let itself be managed by systemd if needed. In fact, I think we should always do that in OpAMP reference implementation and recommend custom implementations to do the same as well. The reason is that de-coupling the agent and the supervisor allows for poor control and leaves room for race conditions and other problems if the agent can be terminated without the supervisor being aware of it.

I have been thinking about the Supervisor and it seems to me implementing a generic Supervisor such that it has great usability is going to be difficult.
I think we probably want to modify our approach a bit. Instead of building a generic Supervisor we probably want to create a small library with helpers which can be used to create Supervisors and then create an OpenTelemetry Collector-specific Supervisor. After this we will more experience and it may help us understand if we can create a nice, more generic Supervisor.

Closing since the author will not be able to work on this anymore.


Does this library follow a standard MsgPack based standard?

Is there a standard being following here?
I'm asking because I'm making some improvements for my own use, such as improved exception handling, which are changing some parts of the payload being sent back and forth. I'd love to merge them back in, but if there is a standard being followed I don't want to break it.

Actually, I wrote this personal project just for learning asyncio, so feel free to send PR :-)

Awesome. There are a couple of things I've been tweaking and improving on that I'll make a PR for


iotas: 0.1.9 -> 0.1.11

Description of changes
https://gitlab.gnome.org/cheywood/iotas/-/compare/0.1.9...0.1.11?from_project_id=20110&straight=false
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2016


Add Antrea 1.0 blog post

Codecov Report

:exclamation: No coverage uploaded for pull request base (website-with-versioned-docs@3fe241b). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 419e171 differs from pull request most recent head 28129c3. Consider uploading reports for the commit 28129c3 to get more accurate results

@@                      Coverage Diff                       @@
##             website-with-versioned-docs    #2100   +/-   ##
==============================================================
  Coverage                               ?   60.84%
==============================================================
  Files                                  ?      270
  Lines                                  ?    20368
  Branches                               ?        0
==============================================================
  Hits                                   ?    12392
  Misses                                 ?     6691
  Partials                               ?     1285

Flag
Coverage Δ

kind-e2e-tests
51.56% <0.00%> (?)

unit-tests
41.37% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Does not support Integer type more than u127 (u128 and above types throw compilation error)

Aim
Noir language does not support integer types more than u127 (uint 127). Think noir language should support types more than u127, e.g. u128 or u256.
Expected Behavior
struct Signature {
    r: u128,
    s: u128
}
---------------------------------
or
---------------------------------
struct Signature {
    r: u256,
    s: u256
}

Must got through compilation "nargo compile"
Bug
nargo does not compile program with variables which type more than u127 (e.g. first: u128 or first: u256).
I've got structure:
struct Signature {
    r: u128,
    s: u128
}

and nargo compile throw me error like this:
error: Unexpected ,, expected one of bool, comptime, crate, dep, Field, fn, fmtstr, str, &, (, [, integer type, Ident
   ┌─ /home/pal/projects/learn-noir/circuits/src/main.nr:19:12
   │
19 │     r: u128,
   │            -
   │

Nargo version:
nargo 0.16.0 (git version hash: 982380e54bb4d696688522c540f1234734ae2e80, is dirty: false)
To Reproduce

Create structure where varaibale type is u128 or u256
run "nargo compile"

nargo version:
nargo 0.16.0 (git version hash: 982380e54bb4d696688522c540f1234734ae2e80, is dirty: false)
Installation Method
None
Nargo Version
nargo 0.16.0 (git version hash: 982380e54bb4d696688522c540f1234734ae2e80, is dirty: false)
Additional Context
Installation method: noirup
Would you like to submit a PR for this Issue?
No
Support Needs
No response

If you need a value of this size, I'd recommend using a bigint library.


Adding 'disk' option for image field

This allows to use 'disk' option instead or together with 'prefix' option, making things a bit cleaner.

Yup, totally. Thank you @erik-ropez, this looks like a sensible change, that will help people store their assets on S3 Buckets more easily. I've polished and merged it on master. It will be available publicly after the 3.3.11 patch release is tagged (0-3 days).
Thanks, cheers!


Yacc error

I read the issue posting guidelines
error reason describe is follow：
Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/yacc failed with exit code 1
wait  and thanks

Did you try google? This is the first thing that came up http://stackoverflow.com/questions/10373016/command-xcode-app-contents-developer-toolchains-xcodedefault-xctoolchain-usr-bi


fix(objc): call emitMessageToRN method not property

@peggyrayzis You are welcome!! Thanks for your amazing work. 🍻

I just cut a new release with your change to the template 😀
Next time, it would be a huge help if you could please update the Jest snapshot tests! You can run npm run test:update to update the template snapshot. Then, you can commit the new snapshot along with your fix.
I'm going to be refining the contribution process over the next few weeks to include PR templates, CI, and code review automation to better communicate this to everyone.
Thanks again @bduyng & welcome to RNCB! 🎉 🍻

Awesome!!! Can't wait to contribute more to this project and React Native community! I am working on #15 btw :)

Wow thank you!! I was going to tackle this earlier this week but got sidetracked so I'm glad you're working on it 😀
Let me know if you run into any issues or have any questions along the way. I'm happy to pair if you get stuck!

Yes sure will let you know if I need any help. Thanks again @peggyrayzis!!


Upload the Dynamo examples (wiki) to Github

[X] Hello world
[x] Hyperbolic shell

[X] Hello world
[ ] Hyperbolic shell

@xRadne I decided against using the Hyperbolic shell example after all, because Lunchbox for Dynamo is discontinued since 2020. Before this, you could just install it from the Dynamo package manager, however now you have to download the repo and install it that way.
I feel like that's too much for for a discontinued plugin, for an example we won't use that much, but if you feel like this was the wrong call, feel free to veto!

Ok!


[Bug] Parsing of operation list JSON fails if "kind" is not the first field.

When testing the latest version of tzindex (12.0.3 right now) with TezEdge (current develop) we found that it was getting stuck and re-processing the same blocks again and again.
After some investigation @binier found that when parsing the operation list JSON string, some of the work is done manually, and it assumes that "kind" is the first field:
https://github.com/blockwatch-cc/tzindex/blob/091c423a070a5f2bb6b4a931a732b26bee4dd76f/rpc/operations.go#L155-L162
Octez does indeed put "kind" first (but that may not always be true), while TezEdge does not (at least not always). Ideally tzindex shouldn't assume the order of the fields.
Some more data:
Logs from error
2022/04/26 17:42:51.337941 DEBG BLOC crawler: queuing block 1 BLAuTiHQdSCXXhfDvv417JKsM8bYT5tNsrpmWyJiMrMdYJNuoLP q=0
2022/04/26 17:42:51.337980 DEBG BLOC crawler: fetching next block 2
2022/04/26 17:42:51.445860 WARN BLOC crawler: RPC connection error: rpc: unsupported op ""
2022/04/26 17:42:56.447496 DEBG BLOC crawler: fetching next block 1
2022/04/26 17:42:57.362569 DEBG BLOC crawler: queuing block 1 BLAuTiHQdSCXXhfDvv417JKsM8bYT5tNsrpmWyJiMrMdYJNuoLP q=0
2022/04/26 17:42:57.362590 DEBG BLOC crawler: reorg detected at 1. Falling back to crawl mode.
2022/04/26 17:42:58.363752 DEBG BLOC crawler: fetching next block 0
2022/04/26 17:42:58.474112 DEBG BLOC crawler: queuing block 0 BLockGenesisGenesisGenesisGenesisGenesis1db77eJNeJ9 q=0
2022/04/26 17:42:58.474150 DEBG BLOC crawler: fetching next block 1
2022/04/26 17:42:59.241439 DEBG BLOC crawler: queuing block 1 BLAuTiHQdSCXXhfDvv417JKsM8bYT5tNsrpmWyJiMrMdYJNuoLP q=0
2022/04/26 17:42:59.241488 DEBG BLOC crawler: fetching next block 2
2022/04/26 17:42:59.241761 TRCE BLOC Processing block 0 BLockGenesisGenesisGenesisGenesisGenesis1db77eJNeJ9
2022/04/26 17:42:59.264832 DEBG DATA Query: account.init_cache =>
2022/04/26 17:42:59.354937 WARN BLOC crawler: RPC connection error: rpc: unsupported op ""

Data being parsed
[
  {
    "counter": "1",
    "fee": "357",
    "gas_limit": "1000",
    "kind": "reveal",
    "metadata": {
      "balance_updates": [
        {
          "change": "-357",
          "contract": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
          "kind": "contract",
          "origin": "block"
        },
        {
          "category": "fees",
          "change": "357",
          "cycle": 0,
          "delegate": "tz3Q67aMz7gSMiQRcW729sXSfuMtkyAHYfqc",
          "kind": "freezer",
          "origin": "block"
        }
      ],
      "operation_result": {
        "consumed_gas": "1000",
        "consumed_milligas": "1000000",
        "status": "applied"
      }
    },
    "public_key": "edpkubSgCoMjB2a6vPWRNRHfGa6HUFfFyEUKoEQhWC8osnav8QzBdJ",
    "source": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
    "storage_limit": "0"
  },
  {
    "amount": "1000000000000",
    "counter": "2",
    "destination": "tz1cg5EqC3WdZgRSvGJeW328S4KQNrT4jvyv",
    "fee": "310",
    "gas_limit": "1520",
    "kind": "transaction",
    "metadata": {
      "balance_updates": [
        {
          "change": "-310",
          "contract": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
          "kind": "contract",
          "origin": "block"
        },
        {
          "category": "fees",
          "change": "310",
          "cycle": 0,
          "delegate": "tz3Q67aMz7gSMiQRcW729sXSfuMtkyAHYfqc",
          "kind": "freezer",
          "origin": "block"
        }
      ],
      "operation_result": {
        "allocated_destination_contract": true,
        "balance_updates": [
          {
            "change": "-1000000000000",
            "contract": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
            "kind": "contract",
            "origin": "block"
          },
          {
            "change": "1000000000000",
            "contract": "tz1cg5EqC3WdZgRSvGJeW328S4KQNrT4jvyv",
            "kind": "contract",
            "origin": "block"
          },
          {
            "change": "-64250",
            "contract": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
            "kind": "contract",
            "origin": "block"
          }
        ],
        "consumed_gas": "1420",
        "consumed_milligas": "1420000",
        "status": "applied"
      }
    },
    "source": "tz1foxFdz2ieSj8P9YxKYBTEqYbgFXXEeiQY",
    "storage_limit": "277"
  }
]

Closing this because it was fixed upstream + upstream is outdated now.


Done- User registration back end

Registration user Page  - Working Backend
dashboard user Page - fetching current User

approving PR  Refine-User-Registration Branch to Dev Branch


Merge Develop to Master 20210524

Codecov Report

Merging #56 (7446d59) into master (5ae1323) will decrease coverage by 0.52%.
The diff coverage is 80.73%.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
- Coverage   88.73%   88.20%   -0.53%
==========================================
  Files          30       35       +5
  Lines         985     1085     +100
  Branches       98      103       +5
==========================================
+ Hits          874      957      +83
- Misses         88      105      +17
  Partials       23       23

Impacted Files
Coverage Δ

connections/etuovi/services.py
57.14% <40.00%> (-0.93%)
:arrow_down:

connections/oikotie/services.py
45.45% <40.00%> (-0.38%)
:arrow_down:

apartment_application_service/openapi.py
52.17% <52.17%> (ø)

apartment_application_service/settings.py
83.51% <85.71%> (+0.56%)
:arrow_up:

apartment_application_service/urls.py
100.00% <100.00%> (ø)

...management/commands/create_data_transfer_folder.py
100.00% <100.00%> (ø)

users/admin.py
100.00% <100.00%> (ø)

users/api/serializers.py
100.00% <100.00%> (ø)

users/api/views.py
100.00% <100.00%> (ø)

users/models.py
96.96% <100.00%> (+1.13%)
:arrow_up:

... and 6 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 5ae1323...7446d59. Read the comment docs.


Add -d argument description

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Congrats @grbagrbic on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Non-nullable Pointers/References

Are non-nullable pointers and references planned for Vox?

I cant say that they are 10/10 features like slices, so I would need to think about them first. If it is ref like in D, which is only available for foreach and function parameters, then it is 8/10. The only rough point is that ref is not really a type in D, which gives some headache.
Storing non-nullable reference in a struct is definitely tricky, because compiler needs to ensure that it is always initialized properly and it is convenient to the user.
What I can certainly say that I will 100% need something like ref for foreach.

Is it even possible to ensure a pointer is always initialized without some form of automatic gc/refcount or using refcaps/borrowing?

Alloc value on heap
Make a pointer to it
If (goldbach conjecture) free original pointer
Is the second pointer now invalid?

yes, that might be impossible in general (or at least very tough)

Incidentally...
https://github.com/dlang/dmd/blob/3132e116ef35acdb042bf0082df653b5fbf5e042/test/compilable/diag_access_new.d

Is it even possible to ensure a pointer is always initialized without some form of automatic gc/refcount or using refcaps/borrowing?
1. Alloc value on heap

2. Make a pointer to it

3. If (goldbach conjecture) free original value

4. Is the second pointer now invalid?

The solution is to have contract (such as an attribute @notnull) on when pointers and classes can be initialized.


Fix wrong proxy type

Just change proxy from array to object

From the definition here https://github.com/webpack/webpack-dev-server/blob/adeb92e1e37551a6cbf3063942d6c2c7efbdff10/lib/options.json#L292, array is valid as well.

@chenxsan
ive got this error: When proxy in package.json is an object, each context object must have a target property specified as a url string
So I thought its not working, but it looks like this is an problem with vue-cli and not webpack itself, see https://github.com/vuejs/vue-cli/issues/5740


[iOS] Error: ERR_COVER_OPEN

I installed package and run on iOS real device (iPhone 8 Plus - iOS 15.1)
My printer is TM-m30II-H_003805
I initialized and connected successfully to printer.
But when I use function send, it returns ERR_COVER_OPEN.
Below is my code + error

Do you have any idea to fix this bug?
Thank you!

@SpQuyt possibly you didn't close the cover for a paper on your printer?

@SpQuyt possibly you didn't close the cover for a paper on your printer?

Ah my bad. This is the 1st time I use this kind of printer.
After closing cover, I can print now.
Thank you very much for your quick reply! @tr3v3r


Learn assembler puzzle games.

Human resource machine
7 billion humans
TIS-100
Shenzhen I/O

Thanks for the suggestion but we would like to keep only free resources on this list.
If you want to add the rxjs-fruit.com link, please submit a new PR.


microrl drop argument when using multiple spaces in command

When entering a command with two spaces between the arguments, microrl drops the second argument.
For example, the input 123  456.

In the debugger, you can see that argc is 2, but argv only includes the first arguments.

argv is still a valid string, but if you rely on argc to be correct, it could be a problem.

I did see that argv was a double pointer.
I shouldn't program so late...
My apologies for the spam.


Step forward and back outputs

Can you add support for drivers that require forward backward step signals rather than step/direction? I'm not sure if there is a version that can do this.

Being too much effort, I understand. I will attempt to solve this initially by using the step output to trigger an interrupt on change routine in which I pulse appropriate step pins depending on the direction output. in this particular program the esp32 has very little work to do besides from running the stepper so CPU time wouldn't be an issue. If I can't get this to work, I will use some gates to generate the signals.
Thank you for considering this and answering my question.


Saveing feature layer that is created from selected elements

If a layer is built using a set of selected elements from another layer, the layer.featureset.name and featureset.filename remain null. Therefore it is not possible to save the layer. Meaning that featureset.save() raises an exception.
I set those value and was able to save the layer without raising the exception but when I open the same layer it is empty. None of the selected features are in the file.
I would appreciate any help.
Regards,

Can you post your code.

You can replicate the bug using the demo program.
All you need to do is:
Open a shapefile/layer. select some of the elements, while selected right click on the layer name in the legend window and from the selection menu choose create a layer from selected elements. It will build a layer and add it to your legend window which correctly shows all of the elements.
But if you try to save the layer/project you will get the error.

oic.


Add seed blocks for 410,000 to 420,000

This PR adds the seed blocks for 410,000 to 420,000.
The blocks are the result of the omni_getseedblocks call and modified for appropriate formatting.
To test, run Omni Core with and without the seed block filter enabled and check the consensus hash for block 420,000 is identical for both cases.

Awesome, thanks for preparing this!


$scrollTo is not defined on the instance but referenced during render

Hi, I'm using this inside a vue component, when I click my tab that has , the console says $scrollTo is not defined.
I tried to put import Scrollspy from 'vue2-scrollspy'; Vue.use(Scrollspy); in either the vue component or index.js, and nothing works.
I'm new to vueJs, thanks for the help!

See this [example](https://github.com/ibufu/vue2-scrollspy/tree/master/docs/src. And you could show me your code.

Hi, I tried your example but it still doesn't work.
Here's the code in my index.js
import Scrollspy from 'vue2-scrollspy';
Vue.use(Scrollspy);

export default new Vue({
    el: '#root',
    store: store,
    router:router,
    render: h => h(foo)
});

And here's the code in my component:

                        {{aCat}}

0" v-for="aCat in formatCats" v-bind:key="aCat">
                    {{aCat}}

 ...

version of Vue?

On Vue 2.8.2 facing this issue too.

same issue here

sorry I forgot to reply, i was on vue 2.3.4, i ended up using vue-scrollactive

@Huixiong91 I am confused that my demo works on the latest Vue(2.4.4).

https://ibufu.github.io/vue2-scrollspy/
I printed the version of Vue in console.

@ibufu i encountered the same problem, the vue version is the same as yours.The problem is that the the related data is got with ajax.

you should use this.$scrollTo

Was this resolved. I can not get it to work either.


Operation Starseed Quest, The Beagle

Cannot complete quest due to Beagle colliding with space Debree and being sent out into deep space when you travel to it's destination. The ship will be many KM away and still moving away. Trying to reload the map by landing ship and taking off but it keeps colliding and being sent out at light speed.

Game Version
V<IP_ADDRESS>
Language
English (EN)
New Game
No
Reproduction Steps
Play the Starseed quest as normal. Upon reaching the objective of locating the Beagle, travel to it. There is a possibility that it may collide with debre and be sent out at an insane speed. If this does not happen, land and fly off again or quicksave before heading to the destination and repeatingly try to get the bug to happen.

Update: Traveling to a completely different system then traveling back changed the map to have no debree. To replicate bug try going to a different system, land then travel back to the Beagle until you get a tile with debree to send it flying.


Added the Source and License for ApacheOrcDotNet 1.0.0

Type: Missing
Summary:
Added the Source and License for ApacheOrcDotNet 1.0.0
Details:
Source and license data was missing for ApacheOrcDotNet.
Resolution:
Source and license data was added.
License was here: https://github.com/ddrinka/ApacheOrcDotNet/blob/master/LICENSE
Affected definitions:

ApacheOrcDotNet 1.0.0

Woops, misclicked the close button.

@alkent I'm not able to verify that this is the source for this package.
I was not able to find this repo referenced in the package. I was unable to find any source information, at least from my looking. The NuGet package publisher account is different. I could not verify that the NuGet package publisher, 'dhinkebein', is the same as the GitHub user 'ddrinka'.
The source commit ID you provided is from 2021; this version was published in 2020. Maybe I missed it, but I couldn't locate the commit ID for version 1.0.0.
This may be repackaged code that was published for their own use and I am unable to verify if changes were made.
With that, I'm not confident in merging this as the source location information for this package and recommend closing this PR.
Do you agree?

Looking back through the commit history in github, it does not look like it was started from a fork.
If this is the same package, it is the original.
Initial commit * @.*** (github.com)https://github.com/ddrinka/ApacheOrcDotNet/commit/0ca1cc8f3fb1033895ad4909d8e76b355665d8ed
It is described as a port for Apache ORC file format in C#.
I've been given the task to update this information. I cannot close it until I complete it.
The alternative would be to use a different package with full license information. Which doesn't exist.
From: Candice Wright @.>
Sent: Monday, April 4, 2022 8:33 AM
To: clearlydefined/curated-data @.>
Cc: Alex Kent @.>; Mention @.>
Subject: Re: [clearlydefined/curated-data] Added the Source and License for ApacheOrcDotNet 1.0.0 (PR #18724)
@alkenthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Falkent&data=04|01|Alex.Kent%40microsoft.com|a4a4cd20316346cdb55908da165076ea|72f988bf86f141af91ab2d7cd011db47|1|0|637846832099965329|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=deTFQM6lHVbqzZFBgdM2W0nqcDvKqXaPnSQVmfrCxqo%3D&reserved=0 I'm not able to verify that this is the source for this package.
I was not able to find this repo referenced in the package. I was unable to find any source information, at least from my looking. The NuGet package publisher account is different. I could not verify that the NuGet package publisher, 'dhinkebein', is the same as the GitHub user 'ddrinka'.
The source commit ID you provided is from 2021; this version was published in 2020. Maybe I missed it, but I couldn't locate the commit ID for version 1.0.0.
This may be repackaged code that was published for their own use and I am unable to verify if changes were made.
With that, I'm not confident in merging this as the source location information for this package and recommend closing this PR.
Do you agree?

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fclearlydefined%2Fcurated-data%2Fpull%2F18724%23issuecomment-1087707631&data=04|01|Alex.Kent%40microsoft.com|a4a4cd20316346cdb55908da165076ea|72f988bf86f141af91ab2d7cd011db47|1|0|637846832099965329|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=KFQbtkuyGPkigBKieLylVnrIHJYFD%2BDOQnjjth759dw%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJ5ZEDXSZ3JLG7BP7PQI3XLVDMDUNANCNFSM5SG4FCQA&data=04|01|Alex.Kent%40microsoft.com|a4a4cd20316346cdb55908da165076ea|72f988bf86f141af91ab2d7cd011db47|1|0|637846832099965329|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=TkZfLOq8%2F3vwzoZBlh2NiFS29BB6n%2BYXeEmC3YtsyuE%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

Per the above recommendation, closing this PR.  Thank you!


[R&D] Prototype backend on kotlin to get skills in new tech stack

User stories
As an engineer I want to develop a sample project to get skills with a new technology before use this tech stack for a production project
Tech details
Kotlin has been substituting Java in Android native development for 7+ years. It positions itself as a a cross-platform instrument. I am not ready to try it for cross-mobile development, but I would like to use it for back-end development. It is actively used for this and gives an option to leverage customer's mobile engineers for back-end works as well (aka fullstack).
So far I mostly offer backends on NodeJs for its quick prototyping capacity and my recent hands-on experience with this, but enterprise level projects my requires something different (e.g. codebase based on statically typed language).
Official resources might be a right place to start:
~~https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-multiplatform-getting-started.html#next-step~~ (that's about mobile side)
https://kotlinlang.org/lp/server-side/
https://kotlinlang.org/docs/server-overview.html
https://blog.jetbrains.com/kotlin/2020/11/server-side-development-with-kotlin-frameworks-and-libraries/
https://www.toptal.com/kotlin/kotlin-server-side-development

Quick research shown 2000+ vs 40 job opportunities for engineers with experience in Spring vs Ktor. It means it would be difficult to find engineers with ktor experience in the near future. However I like its neat design and tends to pick up it to try work with it in pilot project. Performance and scalability issues are not verified yet.
Importing right package in ktor was an issue.

For prototype aim this user story should be enough:
As a user, I want to scan a barcode and get all information about this machine.


Connected Block Textures

Mod name
Connected Block Textures
Curseforge link
https://www.curseforge.com/minecraft/mc-mods/connected-block-textures
Modrinth link
N/A
Other link
https://github.com/Nuclearfarts/connected-block-textures
What it does
Connects textures in supported resource packs using Optifine format
Why should it be in the modpack
Optifine parity
Why shouldn't it be in the modpack
Missing rendering API, still marked beta
Categories

[ ] Performance optimization
[x] Graphics optimization
[ ] New feature
[x] Optifine parity
[ ] Fixes a bug/dependency

Additional details

Currently doesn't work even with unstable Sodium and Iridium: https://github.com/Nuclearfarts/connected-block-textures/issues/38

1.16 & 1.17 work with these builds https://github.com/HyperCubeMC/connected-block-textures/actions, even though they're not official I think you could probably get CF to review them. Nuclearfarts will not be releasing a working 1.16 build nor a 1.17 update until Quilt Loader releases & won't be doing Fabric Loader releases, so its probably worth going through the trouble.

Yes, that is one way... But maybe the dev is willing to release their own version in CF/MR, if the original really will be delayed for months. I'll see when Indium gets released.


Add a status field to notifications

Change-type: minor
Signed-off-by: Lucian Buzzo<EMAIL_ADDRESS>

@balena-ci retest

@balena-ci I self-certify!


return const struct device * for device_get_binding(const char *name)

Describe the bug
the definition is now "__syscall const struct device *device_get_binding(const char *name);",
which bring many compile warnings as below, and at last, program can't link
warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
37 |     struct device *i2c_dev = device_get_binding(DT_LABEL(I2C2_NODE));
it used to be "__syscall struct device *device_get_binding(const char *name);" and work well in zephyr-2.3
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? STM32F030
What have you tried to diagnose or workaround this issue? compare with before building
...

To Reproduce
Steps to reproduce the behavior:
west build
Expected behavior
A clear and concise description of what you expected to happen.
pass the building
Impact
What impact does this issue have on your progress (e.g., annoyance, showstopper)
Can't continue
Logs and console output
If applicable, add console logs or other types of debug information
e.g Wireshark capture or Logic analyzer capture (upload in zip archive).
copy-and-paste text and put a code fence (```) before and after, to help
explain the issue. (if unable to obtain text log, add a screenshot)
warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
37 |     struct device *i2c_dev = device_get_binding(DT_LABEL(I2C2_NODE));
Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows) Linux
Toolchain (e.g Zephyr SDK, ...) Zephyr SDK
Commit SHA or Version used  zephyr-3.99

Additional context
Add any other context that could be relevant to your issue, such as pin setting,
target configuration, ...

I see, Thanks for the help.


app: grass.scn skybox isn't loading

Grass.scn is throwing this warning.

Thanks! https://github.com/webaverse/skybox-360 was not published but now it is.


Feature Request: Pop-up instead of pop-down on entities in chat

Not sure if bug report or feature request. The title would solve this, but on further experimenting it may be a simpler fix.
Currently if you, for example, right click on a table that is the only text in its message, and its the bottom message in chat, the roll button gets cut off until you scroll down: https://gfycat.com/velvetyspecificacouchi
As you can see, once you've scrolled down once, it fixes itself for a while, but switching tabs away from/back to chat resets it to non-working. BEL is the only active module in that world.

Thanks for your feedback! I'll take a look if and how I can add this.

This behavior is deeply tied to Foundry. It may be possible to change it but a change would imply modification on all context menus in Foundry. I  planned this module to provide a way to easy add more useful context menu on existing entity link, not to change context menu behavior. I prefer not to trick with native Foundry, at least not in this module.

Fair enough, its not hard to work around once you figure it out.


Greaseweazle define com port

Howdy,
I'm having trouble getting flux engine to talk to greaseweazle hardware. I read through the documentation which states to replace the driver on windows, however doing this doesn't result in a COM port being assigned to the greaseweazle, which is how flux engine is told that their is a greaseweazle to talk to.
Using the standard driver, which does get a com port assigned, trying to do anything using fluxengine simply hangs with no errors displayed. I did spot a comment on an issue that the way greaseweazle is handled has been changed from what it was, so not sure if i should just revert to an earlier build, or if this is something that is in the works of being fixed?

The second part of my comment was done with the original driver restored - which is where it hangs and nothing gets printed to the screen at all

it could be an issue with mine as well - but it at least responds to gw info command

This is what happens with mine as well. I've just been using fluxengine version 580 in the meantime, and using greaseweazle 0.22 on bluepill.

does it need replacement driver, or the usb cla?

hmm, looks like 580 doesn't have 1581 or 1541 support on it

I use fluxengine 580 with greaseweazle 0.22 on a blue pill, and I use the replacement WinUSB driver.

If you look in the 'greaseweazle' branch, there should be a version which works on Linux; I'm still trying to make it work on Windows. (Turns out the serial port wasn't being set up correctly.)
If you're still using the old 580 build, 1541 support is called c64 and 1581 support is handled by the standard ibm reader.

yeah, i spotted the 1541 support (though had to dig into the code to find the correct flag for writing 1581. successfully wrote a disk just then.

Okay, this should be actually fixed now, for real. Thanks very much for the report!


styles on null cells

When a cell has no value (NULL in a query result), a style applied to the row or column via set_table_column_properites or set_table_row_properties does not apply to the empty cell. This is most apparent when a background color is part of the style.
I note this with an example in Creating Multiple Row Headers with ExcelGen PL/SQL Spreadsheet Generator near the top of the blog post beneath the screenshot.
I suspect you are addressing an issue with setting the style at the sheet level which causes it to extend the style past the end of the data, but the current behavior seems suboptimal.
I would prefer that the set_table_[row,column]_properties methods recognize the boundaries of the query result  set and set the property on all cells in the orthogonal region populated as a "table", whether an individual cell is populated or not.
A similar problem could happen with put_cell, so a method or parameter option to put a null value such that the background style is applied would be useful. I may be wrong on this one as my own code may have skipped null cells. :)
I could also be wrong on the situation with set_row_properties and set_column_properties. I'm asserting that they set the style for the entire sheet, spreading a background color past the extent of any data. That is my recollection, but I didn't build a test today to prove it.

This happens when the NULL is of string data type (CHAR or VARCHAR2).
It is a side-effect of not generating any cell for NULL string values, which was done on purpose prior v3 to save some space, but not relevant anymore with the introduction of styling everywhere.
The same goes for putStringCell.
I'll fix that in the upcoming version.

Fixed in v3.1.


⚠ ClamAV has degraded performance

In 076cd49, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 79 ms

Resolved: ClamAV performance has improved in 602264a.


Pasting on iPad doesn't work

Bug, feature request, or proposal:
Pasting in an input field doesn't work on an iPad.
What is the expected behavior?
It's supposed to input the text from the clipboard when pasting.
What is the current behavior?
Long pressing on an input field and pressing paste doesn't input the text from the clipboard.
What are the steps to reproduce?

Use an iPad
Go to https://material.angular.io/components/input/overview
Paste text into one of the input fields.

What is the use-case or motivation for changing an existing behavior?
The user should be able to copy text from somewhere and paste it into an input field using material design.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: v5.0.0
Material: v5.0.0-rc0
Typescript: v2.4.2
OS: iOS v11.1.2 (tested on iPad)
Browser: Safari and Chrome
Is there anything else we should know?
I've tested this on an Android phone and that works.

What iOS version are you using?

It's iOS 11.1.2.

@YePpHa It's working fine for me, same iOS version and tested in Safari and Chrome. Have you tried rebooting the device?

I will try that.

I will close this issue. It seems to not be an issue with this library, but something completely different. The pasting is broken on both Safari and Chrome for all input fields and not only the material input fields.
Thank you for your help and sorry for taking up your time regarding this.


Update DockerHub org in Travis config

Pushing API and UI images nightly to https://hub.docker.com/orgs/mlexchange

thanks
/lgtm


CLM-8914 Cart Translations Issue

Closes CLM-8914
Issue: Cart translations were not working in a deployed environment, but did work locally. Video of issue
The issue is with the i18nObject, as it was not picking up all translations. The issue is resolved by using the sourceDefaultNamespace to map translations instead.
I tested this using the Cart component as detailed in the ticket, but also tested the Catalog component to ensure that the translations were still working for other helium components. All looks good in testing.
Please let me know if there is any reason why we should use i18nObject instead of sourceDefaultNamespace.

any way we can add automated test coverage for this? It's fairly critical that translations work, and it sounds like they weren't properly prior to this fix, so it would be good to ensure we don't regress here in the future. I think if we separated out the steps of reading/writing files we could test only the processing step, e.g.
const translations = await readTranslations();
const result = processTranslations(...); // this is what gets tested
await writeTranslations(result);

@chrisvariety Good idea, should I include this in the scope of this ticket, or create a new ticket to handle this?

@AlexONeillTI up to you and @rjschill87, my vote would be to include it in this ticket as we generally prefer to ship code changes with corresponding tests.

@rjschill87
After inspecting the compiled files, the translations are not only prefixed with t, but also 'o', 'p', 'f', and 'i18n' for hydratedContent. I have added these to the parser.parseFuncFromString call.
I have also added the testing that @chrisvariety has requested. This involved splitting the code into three segments:

Reading the data
Processing the translations
Writing the data

If the translations exist, FINAL_TRANSLATIONS is defined and contains all the necessary translations. writeTranslations then writes the results to the translations file.
If the translations do not exist, then FINALTRANSLATIONS = {}, which now throws a new error: "Error('No translations exist!');"
I have tested these changes on https://alexoneilsandbox.thoughtindustries.com/cart.

@rjschill87
Pushed a fix for the former part of https://thoughtindustries.atlassian.net/jira/software/c/projects/CLM/boards/26?modal=detail&selectedIssue=CLM-8914.
The translation keys must be translated directly, rather than passed as a variable. I have moved localizedSortMapping into sort-selector.tsx, as it needs to use the useTranslation hook within a react comp.
Will I leave the constants.tsx file as is, or remove it entirely?

@AlexONeillTI If that was all that was in the constants.tsx file and it's not referenced anywhere else, you can remove it

@rjschill87 Tests are now successfully passing the Github action. Let me know if the coverage of these tests is sufficient.
Note - I added a catch to filePaths.js as there was no error handling in this file.

@rjschill87 We discussed isolating the testing to evaluate the output of npm run update-translations
npm run update translations does two things:

Fetches the translations for the first instance in ti-config.json
Writes ALL the translations to locales/translations.json

To me, this doesn't seem to match the original test coverage, which was based around the processing (including reading and writing to translations.json) of the translations so we can ensure that only the used translations are deployed in the compiled project.
So my question is:
Are we now solely testing the fetch of translations from an instance (which is the testing of npm run update-translations.json)
Are we testing the processing of translations (the current implementation but possibly moved to template-base)
Or are we doing both (essentially testing the entire translation operation of the deploy.js script)?

@AlexONeillTI You're right. I think ideally we'd want to test both, so think the approach would be to have a test that runs npm run update-translations that mocks the request/response for translations, so we can verify the initial locales/translations.json is written correctly.
Then, we can add a new command to the template-base: npm run parse-translations, that runs the parse-translations script as seen in the deploy command: https://github.com/thoughtindustries/helium/blob/12248ec48a121e5c6b129e3810dd1a7ed9b01a7b/tooling/cli/lib/deploy.js#L155
Then write a similar test case that calls the npm run parse-translations and verifies the collected keys from the template-base matches what we'd expect.

I had a sync with Aalto university yesterday and they brought up this translations bug. Is there a possibility of revisiting this to see if it fixes their issue?
@chrisvariety @rjschill87

It would be good to have @rjschill87 take another look at it, it seems like there were a lot of commits added after the previous review.

I have changes implemented and tested locally. When trying to push, I am getting that I don't have permission to push to helium repo.
I have messaged @haddadnj and am waiting for a reply. I will update you here when I have successfully pushed the changes.

@AlexONeillTI fixed your permissions :)

@AlexONeillTI fixed your permissions :)

Thanks Chris!

Review now up to date. Addressed @rjschill87's comment regarding the call to the parserScript here: https://github.com/thoughtindustries/helium/pull/220#discussion_r1757122524
The test suite runs successfully and I also tested the latest changes by deploying an app with the Cart and Dashboard page to my sandbox. Both successfully reflect the translations in locales/translations.json


When I click on an item in the menu, the menu doesn't collapse

So on tablet and mobile, if I open the menu (hamburger button) and then I click on a section, it brings me to the correct section but it doesn't close the menu

we also need to close navigation menu on click outside menu. but it looks not simple in vue (What i found now, we can add custom dirictive or add some dependancies for vue/core to use "ref" on templates).  By vanila JS way easier.


500 Error using _lastUpdated parameter to search count

Describe the bug
FHIR sever with large size database has poor performance and returned 500 Error when searching count with _lastUpdated parameter. 500 Error can stably be reproduced on FHIR server with 1tb database and sometimes happened on 500GB.

FHIR Version?
Stu3/R4/R5
Data provider?
SQL Server
To Reproduce
Steps to reproduce the behavior:
Get https://<name>.fhir.azurehealthcareapis.com?_summary=count&_lastUpdated=lt2022-12-05T02:50:36&_lastUpdated=ge2022-01-01T11:02:05

on FHIR server with large sql database.
Expected behavior
Return resource count.
Actual behavior
500 internal error.
My Debug Process
After debugging locally, I find the original request will be translated and rewrite to a SQL query:
SELECT COUNT_BIG(*)
      FROM dbo.Resource r
      WHERE ResourceSurrogateId < @p0
          AND ResourceSurrogateId >= @p1
          AND ResourceTypeId IN (@p2,@p3,@p4,@p5,@p6,@p7,@p8,@p9,@p10,@p11,@p12,@p13,@p14,@p15,@p16,@p17,@p18,@p19,@p20,@p21,@p22,@p23,@p24,@p25,@p26,@p27,@p28,@p29,@p30,@p31,@p32,@p33,@p34,@p35,@p36,@p37,@p38,@p39,@p40,@p41,@p42,@p43,@p44,@p45,@p46,@p47,@p48,@p49,@p50,@p51,@p52,@p53,@p54,@p55,@p56,@p57,@p58,@p59,@p60,@p61,@p62,@p63,@p64,@p65,@p66,@p67,@p68,@p69,@p70,@p71,@p72,@p73,@p74,@p75,@p76,@p77,@p78,@p79,@p80,@p81,@p82,@p83,@p84,@p85,@p86,@p87,@p88,@p89,@p90,@p91,@p92,@p93,@p94,@p95,@p96,@p97,@p98,@p99,@p100,@p101,@p102,@p103,@p104,@p105,@p106,@p107,@p108,@p109,@p110,@p111,@p112,@p113,@p114,@p115,@p116,@p117,@p118,@p119,@p120,@p121,@p122,@p123,@p124,@p125,@p126,@p127,@p128,@p129,@p130,@p131,@p132,@p133,@p134,@p135,@p136,@p137,@p138,@p139,@p140,@p141,@p142,@p143,@p144,@p145,@p146,@p147)

          AND IsHistory = 0
          AND IsDeleted = 0

The query will add all resource types and there is an inline comment in code :
fhir-server/PartitionEliminationRewriter.cs at main · microsoft/fhir-server (github.com)

It seems make sense since resourceTypeId is partition key in SQL database.
So I did some experiments in SQL server and explore the reason why this "better query plan" still has poor performance which led to 500 Error.
My Experiment
I created a 4T FHIR SQL database using OSS project and compared different queries:

Filter by ResourceSurrogateId and all ResourceTypeId (This is the query plan used by FHIR server. )
Search result:<PHONE_NUMBER>
Time: 6min49s

Only filter by ResourceSurrogateId .
Search result:2427786740
Time:1min10s

Filter by ResourceSurrogateId with one ResourceTypeID
Search result:<PHONE_NUMBER>(half of the previous)
Time: 9.3s

From this set of experiments, we find that:

Query with one resource type has good performance since resource type is partition key.
Enumerate all resource type has unacceptable performance, although query on each resource type is quick, the overall time is much longer than query without resource type.  I guess much overhead is used for parallelization (inner join and aggregate).

According to the experiment, it verified that it's not a good idea to simply enumerate all resource types in the sql query.
I also try to analysis it in theory:
For Resource table, it creates three un-clustered indexes to improve query performance:
IX_Resource_ResourceTypeId_ResourceId
IX_Resource_ResourceTypeId_ResourceId_Version
IX_Resource_ResourceTypeId_ResourceSurrgateId
All of them use ResourceTypeId as the first index key and these indexes will only be used when query parameters include resource type.  To use these indexes, it's reasonable to add resource type in SQL query. But when all resource types are added, all of the improvement of indexes will be offset by poor performance of inner join and aggregate.
At last, I try to build a new index on ResourceSurrogateId, and using this index, the request search count will improve 5-6 times than original search method.
Adding a new index will change the schema of SQL database and may not an only way. I hope my experiment and attempts results can help the team solve this problem and improve the search performance.

#100032. Thanks for reporting the issue @sowu880.


Splunk as non-root user by default for UNIX systems.

This is an enhancement request.
As part of Splunk Enterprise best practices Splunk should run as 'non-root user'. See official splunk documentation http://docs.splunk.com/Documentation/Splunk/7.0.0/Installation/RunSplunkasadifferentornon-rootuser
Code involved: ~/puppet-splunk/manifests/params.pp
 } else {
    $forwarder_dir = pick($forwarder_installdir, '/opt/splunkforwarder')
    $server_dir    = pick($server_installdir, '/opt/splunk')
    $splunk_user   = 'root'
  }

What are you seeing
splunk runs as "root" user by default. Which is against splunk best practices.
What behaviour did you expect instead
The module should create a non-root user (i.e "splunk" user) and run splunk as it.

Hey @jbethmont ,
Thanks for the enhancement request. Here are a couple things we need to figure out first.
1.) What is the default chosen/selected user for splunk when fresh installed.  If this is wrong we should get this fixed up. If the default user on fresh install is not based on splunk best practices I would argue that this should be left alone.  I would think the scenario your describing is for advanced users and might be too restrictive for regular users to figure out.

@TraGicCode The default user on a fresh install is the user that owns the splunk directory and is used to launch the splunk process. So technically it could be any user. But Splunk has the ability to run scripts as scripted inputs on the system. So for security best practices we don't want Splunk to run as root.
I would recommend then that the module creates a "splunk" user by default that will own the directory and run splunk processes. But definitely not "root" by default".
And for the module not to be "too restrictive", the user should be able to override the 'splunk_user' value.


macdjview 0.1.2

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.
[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked that the cask was not already refused in closed issues.

I’ve added interpolation to the url. Please next time do it yourself, @yurikoles. You have been contributing for a good while, you know we always want that.

@vitorgalvao sorry, I was too fast on this PR.


OpsMgr 'Apply Changes' completed but the harbor job on 'Status' tab shows failure

When deploying Harbor Tile at the 1st time, OpsMgr 'Apply Changes' completed but the harbor job on 'Status' tab shows failure. After a time period, the harbor job on 'Status' tab shows success.

The expected behaviour is harbor job is ready to service when 'Apply Changes' completed.
Need to wait for the harbor service to be ready before starting harbor job exits.
cc @steven-zou @reasonerjt

I just found that "wait for harbor service to be ready" doesn't solve the problem.
startHarbor() uses /sbin/start-stop-daemon to launch 'docker-compose up' and write its pid to harbor.pid, then Ops Mgr will detect harbor.pid is alive then consider all jobs (docker and harbor in  our case) finished (rather than waiting for the 'ctl start' to exit), and exit the deployment with success message 'Change Applied'. However, if 'docker-compose up' can not start Harbor service successfully for some reason (I met this case due to MySQL can not start, but didn't find out the cause), the Harbor service will not able to accept requests, although Ops Mgr already reported the harbor deployment succeeded.
To resolve this problem, we might let the start-stop-daemon to save the docker-compose pid to a temp file, and write the pid to the target harbor.pid file after Harbor Service is started successfully.
@reasonerjt @steven-zou

This issue is resolved by these patches. We're running CI to verify this fix.
Use status_check to check Harbor status in harbor job start
https://git.eng.vmware.com/harbor/habo/commit/d7d818ee93daf7cd8d2e7da2fb678247bcab8c3b
Let monit detect the real harbor pid until Harbor Service is running
https://git.eng.vmware.com/harbor/habo/commit/6faba57f524ed75efc27a39def2f42b8c33b218c

Verified in CI.


[CSL-1676] Set keep-alive timer duration to slot duration

Followup to #1852 - fixes TODO.

As mentioned here https://github.com/input-output-hk/cardano-sl/pull/1853#pullrequestreview-84632023 we will need to port that PR to master, and that will probably be a new PR, so we can probably just close this one.


Added setting drawer Italian language support

https://github.com/ant-design/ant-design-pro-layout/pull/228/checks?check_run_id=340288789
fix lint？

great job


Selection Behavior 'replace'

Closes https://github.com/adobe/react-spectrum/issues/2018
Adds selectionBehavior prop which can be toggle or replace. Previously, it was always toggle, this specifically adds replace.
This is added for mouse/touch and keyboard is handled the way it is in Windows where alt + arrows will allow a user to navigate and select a non-contiguous set of items
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

So I think there's a few things that need to happen here:

selectionBehavior = 'replace' and selectOnFocus should be a single option (selectionBehavior is a better name). They should always be applied together, and shouldn't be used separately.
I see that ctrl + alt + arrow keys moves the focus without changing the selection, but I couldn't figure out a way to add the focused item to the selection without replacing it. Should that be ctrl + alt + space key or something?
I think we should wait on having a UI for highlight style before merging this. It shouldn't be possible to have checkboxes with selectionBehavior = replace. Still waiting on spectrum for this, so maybe we can combine your PRs related to this into a single feature branch until then.


Don't support table preview

when write a table in this Edit , it doesn't preview well

Tables
Are
Cool

col 3 is
right-aligned
$1600

col 2 is
centered
$12

zebra stripes
are neat
$1

CommonMark does not support tables.

@mike-ward if it is using pandoc, it should be able to preview tables, right?

Turn on the GitHub Markdown in the options.

cool. That worked.


Overriding built-ins with pathGroups

We are using typescript and have a folder (unfortunately named util) aliased as a search path so we can have imports like import { thing } from 'util/foo';
It appears that import/order is treating util/foo as a "builtin", because it still wants my util/foo import listed before external imports.
I have the order set up like this:
groups: [
                    'builtin',
                    'external',
                    'internal',
                    'parent',
                    'sibling',
                    'index',
                    'object',
                ],

And I defined a pathGroup like this:
                pathGroups: [
                    {
                        pattern: 'util/**',
                        group: 'internal',
                    },

Is there another way I can specify that util is a builtin but util/** is not?

I think I found a solution - set pathGroupsExcludedImportTypes: [], so that builtins (including util) are also considered by the pathGroups rules.

See #1898 as well.


Invalid hook call when executing with @vitest-ui

Describe the bug
Executing tests with UI will lead to invalid hook calls (TypeError: Cannot read properties of null (reading 'useState')). Executing tests without UI will pass.
Reproduction

Reproduction repo: https://github.com/nwi-di/vitest-invalid-hook-call
Clone repo and install dependencies
Run npm run test-ui(will execute vitest with ui flag)

System Info
System:
    OS: macOS 13.4.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 307.59 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 9.5.1 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 115.0.5790.114
    Safari: 16.5.2
  npmPackages:
    @vitejs/plugin-react: ^4.0.3 => 4.0.4
    @vitest/ui: ^0.34.1 => 0.34.1
    vite: ^4.4.5 => 4.4.8
    vitest: ^0.34.1 => 0.34.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Can you try downgrading vitest and @vitest/ui to 0.33.0, 0.34.0 seems to have broken it.

I am facing the same issue, but I actually can get it working with the latest vitest version; issue seems to be actually related to the latest happy-dom version for me.

Can you try downgrading vitest and @vitest/ui to 0.33.0, 0.34.0 seems to have broken it.

Downgrading works as a workaround. Seems to be related to latest version of either vitest or @vitest-ui (guess @vitest-ui as tests running without ui will pass)

Error also occurs using:
vitest --api 9527

... which impacts testing UIs such as the vscode vitest extension.
Downgrading vitest and @vitest/ui both to 0.33.0 works in these cases as well.

@SamuelAlev i love u

Can you try downgrading vitest and @vitest/ui to 0.33.0, 0.34.0 seems to have broken it.

Thank you, @SamuelAlev the downgrading worked here 👋

0.34.2 release from yesterday solves the issue 🙂

Another workaround for now. Add this to your config to disable occasional optimizer. Looks like there is a bug in the implementation that causes inconsistencies when --api or --ui is enabled.
      deps: {
        optimizer: {
          web: {
            enabled: false,
          },
        },
      },


Clean up CaseTransformFunction::constructStatementListLegacy.

This is a follow-up cleanup for https://github.com/apache/pinot/pull/11328.

Codecov Report

Merging #11339 (03ca6f7) into master (f25f3ed) will decrease coverage by 53.82%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #11339       +/-   ##
=============================================
- Coverage     68.46%   14.65%   -53.82%
+ Complexity     6535      494     -6041
=============================================
  Files          2233     2159       -74
  Lines        119952   116775     -3177
  Branches      18191    17738      -453
=============================================
- Hits          82128    17111    -65017
- Misses        31984    98250    +66266
+ Partials       5840     1414     -4426

Flag
Coverage Δ

integration1
?

integration2
?

java-11
?

java-17
14.65% <ø> (-53.66%)
:arrow_down:

java-20
14.65% <ø> (-53.65%)
:arrow_down:

temurin
14.65% <ø> (-53.82%)
:arrow_down:

unittests1
?

unittests2
14.65% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

...ator/transform/function/CaseTransformFunction.java
0.00% <ø> (-38.76%)
:arrow_down:

... and 1709 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Let's not clean it up now. Broker side is just upgraded. If somehow people deploy server first, this query will fail. Let's wait until next release

If somehow people deploy server first

Is this possible? I thought the deployment order was always controller -> broker -> server.

@shenyu0127 Ideally user should not do that, but it would be good to leave longer migration window. Currently broker is still running the old format, so it is safer for server to support both for a release.

Yes, it is safe to only include the broker side change in the next release and check in this PR after next release.
Converted the PR to draft.

@Jackie-Jiang please merge the PR whenever you think is right.


json parsing should be a full fledged parser

Find this line:
SFString oneTransaction = nextTokenClear(contents, '}');
It continually pulls a string off of the contents and parse one at a time. This should be a full fledged parser responding to fieldNames and value and "}" to end record. Should be simple and much faster.

Done.