When running app.use(i18n): Argument of type 'I18n<...>' is not assignable to parameter of type 'Plugin<[]>'

Reporting a bug?
I installed vue-i18n in my Vue.js project, which is using TypeScript. After initializing the i18n instance and trying to run .use(i18n) in my application, an error occurs, and I'm unable to use it properly.
Expected behavior
app.use(i18n) should work without type errors.
Reproduction
First:
bun add vue-i18n@latest

Then:
src/i18n/index.ts:
import { createI18n } from 'vue-i18n'
import messagesEnUS from './en-US.json'

type I18nSchema = typeof messagesEnUS

const messages = {
  'en-US': messagesEnUS,
}

export type I18nLocale = keyof typeof messages

export const i18n = createI18n<I18nSchema, I18nLocale>({
  locale: 'en-US',
  fallbackLocale: 'en-US',
  messages,
})

src/main.ts:
import './index.scss'

import { createApp } from 'vue'
import { createPinia } from 'pinia'
import { i18n } from './i18n'
import { router } from './router'
import App from './App.vue'

const pinia = createPinia()
const app = createApp(App)

app.use(pinia)
app.use(i18n)
app.use(router)
app.mount('#app')

System Info
System:
    OS: Linux 6.10 Fedora Linux 40 (KDE Plasma)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i7-1255U
    Memory: 2.25 GB / 7.43 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.17.0 - /usr/bin/node
    Yarn: 1.22.22 - /usr/local/bin/yarn
    npm: 10.8.1 - /usr/local/bin/npm
    bun: 1.1.29 - ~/.bun/bin/bun
  npmPackages:
    @vitejs/plugin-vue: ^5.1.4 => 5.1.4
    @vue/typescript-plugin: ^2.1.6 => 2.1.6
    vite: ^5.4.8 => 5.4.8
    vue: ^3.5.11 => 3.5.10
    vue-router: ^4.4.5 => 4.4.5
    vue-tsc: ^2.1.6 => 2.1.6

Screenshot
No response
Additional context
package.json:
{
  "name": "my-project",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vue-tsc && vite build",
    "preview": "vite preview"
  },
  "dependencies": {
    "@remixicon/vue": "^4.2.0",
    "@vuuui/vue": "^0.1.3",
    "pinia": "^2.2.4",
    "ts-binding": "workspace:*",
    "vue": "^3.5.11",
    "vue-i18n": "^9.14.1",
    "vue-router": "^4.4.5"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.1.4",
    "@vue/typescript-plugin": "^2.1.6",
    "autoprefixer": "^10.4.20",
    "prettier": "^3.3.3",
    "prettier-plugin-css-order": "^2.1.2",
    "sass": "^1.79.4",
    "typescript": "^5.6.2",
    "vite": "^5.4.8",
    "vue-tsc": "^2.1.6"
  }
}

Diagnostics:
src/main.ts:14:9 - error TS2345: Argument of type 'I18n<{ "en-US": LocaleMessage<VueMessageType>; }, { "en-US": DateTimeFormat; }, { "en-US": NumberFormat; }, string, true>' is not assignable to parameter of type 'Plugin<[]>'.
  Type 'I18n<{ "en-US": LocaleMessage<VueMessageType>; }, { "en-US": DateTimeFormat; }, { "en-US": NumberFormat; }, string, true>' is not assignable to type 'FunctionPlugin<[]>'.
    Type 'I18n<{ "en-US": LocaleMessage<VueMessageType>; }, { "en-US": DateTimeFormat; }, { "en-US": NumberFormat; }, string, true>' is not assignable to type '(app: App<any>) => any'.
      Type 'I18n<{ "en-US": LocaleMessage<VueMessageType>; }, { "en-US": DateTimeFormat; }, { "en-US": NumberFormat; }, string, true>' provides no match for the signature '(app: App<any>): any'.

14 app.use(i18n)

Validations

[X] Read the Contributing Guidelines
[X] Read the Documentation
[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 Discussions

@cuikho210
Thank you for your reporting!
Your code snippet is very helpful, but some of the code is missing. As mentioned in the previous comment, I would like you to provide the minimal reproduction code on stackbliz. 🙏

Apologies for the confusion. I rechecked the issue, and it seems the error only occurs in my current project and doesn't appear in a new one. After deleting the bun.lockb and node_modules files, the error disappeared. It seems more like a package conflict rather than an issue with vue-i18n itself. :smile_cat:

When running the build on Jenkins, errors sometimes occur:
Type 'I18n<{ zhCN: { ce_mian: string; chang_mo_zhi: string; chang_shi_guo_cheng: string; cheng_fu_shou: string; cheng_gong_zhan_li: string; chu_shi: string; di_xaxisindex_1_ci: string; dong_zuo_pai_she_wan_cheng_hou_zi_dong_fen_xi: string; ... 112 more ...; zong_fen: string; }; en: { ...; }; }, unknown, unknown, false>' does not match the signature '(app: App<any>, ...options: unknown[]): any'.

However, I cannot reproduce the issue locally.
The same problem also appears with Pinia.
Maybe is a package conflict?
Currently, I am using // @ts-ignore to ignore the error.
Package version:

vue-i18n: 9
typescript: ~5.6.3
vue: ^3.5.12


Expanders need a button on the arrow to assist with the narrator.

Describe the bug
The expander control lacks any information that tells a user using the narrator that they are on an actionable item.  Narrator announces a "group" and if the expander is expanded or not, but not if the user can take an action.
Steps to reproduce the bug

Open the WinUI 3 Gallery
Go to the expander page.
Turn on narrator.
Tab over to an expander.
Narrator read [Title] group [state]

Expected behavior
Narrator announces that the expander can be interacted with.  [title] Group CanExpand(?)  I don't know the best content.
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.5.3: 1.5.240428000
Windows version
No response
Additional context
No response

Thanks for providing this feedback. The Xaml Expander control implements the ExpandCollapse Pattern through UIAutomation. Xaml does not directly control how Narrator (or other assistive technology) describes the control.
In this case it reads out the state of the control as either Collapsed or Expanded.
I will pass along this feedback to the Narrator team to see if they want to be more descriptive in this scenario.


[IME] Do not clear document selection when document loses focus

Before this PR, document selection would be cleared by the IME document interactor whenever the document would lose focus.
This behavior differs from the physical-keyboard document interactor and as shown in #609, it breaks existing functionality.
By removing the clearance of the document selection it solves the issue, but I'm not aware of potential consequences.
Fixes #609.

You said that the behavior is different between physical keyboard and IME. What's the observable difference as a user?
You mentioned that the IME behavior breaks some existing expectations. What are those expectations? Can you add tests for those expectations?


fix(footer): change cypress intercept for translation to use raw data

Related Ticket(s)
No related issue
Description
This is a followup to the cypress e2e tests for Footer. In some cases the sessionStorage isn't being used and the cy.intercept is caught instead. In this case, it should use the raw response from the translation repo.
Changelog
Changed

Changed fixture for translation API to use raw response data

Something is not jiving with the React tests, investigating...

Turns out that Cypress didn't like the setting of sessionStorage, so that was removed and now fully relies on the raw translation fixture.


UI - Org/root part 1 - Navbar update for new Figma design specifications

Organizations index/root have an updated Figma design. The old index and org/root will stay in place so the new page will need to be built. Part 1 is to focus on the new Navbar.

It provides the same basic needs of the current navbar.

At minimum it has the same functionality as the current.
At minimum is as responsive/mobile friendly as the current.
It is a 'partial' and listed in the app/views/layouts/shared folder.
It follows Bootstrap and/or the theme css classes structure. no custom css

No need to create links or routes if they do not exist yet. The goal here is to provide a working component following the new design aspects.
Find the Figma design in the resources section, (knowledge base) of the README figma file

Reviewing


[Distributed] Complete handling of protocol calls and witnesses using adjusted mangling scheme

This adds a number of tests, completes handling of distributed thunk witnesses and also reimplements how we handle distributed var and their accessors.
The commits are not very clean after the macro ones, so best to skim the whole thing. I had some inline questions -- do we need to specifically mangle the distributed getter specially etc

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please smoke test

Sourcekit failure

@swift-ci please smoke test Linux

It might be a good idea to proactively make it dg even though it doesn't create a problem today because of TE appended at the end it's open to misuse in the future.

@xedin this one I think is right but I'll want to do this in a separate PR so we have a separate specific one about the wire protocol change. I think we can pull it off for Swift 6 but need to double check.

@swift-ci please smoke test

Please test windows

@swift-ci please test windows

@swift-ci please build toolchain


Allow .vscode/settings.json per folder without using multi-root workspaces

Specifically we're interested in having the python.defaultInterpreterPath setting to be folder-specific. Right now in our Python monorepo, navigating between projects requires manual switching of the Python interpreter so that the pip packages and imports are recognized by the IDE.
I'm imagining the end state where each project in the monorepo has its .vscode/settings.json file and have VS Code read the settings from that file when a file from that project is open.
More context: Multi-root workspaces won't work here. We're using the Pants build tool. While it's a monorepo, it's more than just several top-level folder smooshed together. There are other metadata files at the top-level so we can't really have a project.code-workspace file because we'll need the . folder to be included and that causes the other folders to be duplicated in the explorer view.
Issues I found that are related but not applicable:

https://github.com/microsoft/vscode/issues/15909
https://github.com/microsoft/vscode/issues/17634
https://github.com/microsoft/vscode/issues/147911

It would be difficult to solve it from Python extension's perspective as this requires us to look for python.defaultInterpreterPath setting in various settings.json files in the workspace folder. If you would still like us to consider it please open a feature request in https://github.com/microsoft/vscode-python/issues.
I'm transferring it back to VSCode as this requires a general solution like https://github.com/microsoft/vscode/issues/15909 IMO.


Ashlar fails if ome.tiff data is float32

In the ome.tiff metadata the pixel type is "float" while numpy conversion is np.float32.
$ ashlar Cycle0.companion.ome Cycle1.companion.ome -c0

Stitching and registering input images
Cycle 0:
    reading Cycle0.companion.ome
WARNING: Stage coordinates' measurement unit is undefined; assuming μm.
    assembling thumbnail 1/439Traceback (most recent call last):
  File "/home/jmamede/anaconda3/envs/tensorflow/bin/ashlar", line 8, in <module>
    sys.exit(main())
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/scripts/ashlar.py", line 212, in main
    return process_single(
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/scripts/ashlar.py", line 243, in process_single
    edge_aligner.run()
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 486, in run
    self.make_thumbnail()
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 497, in make_thumbnail
    self.reader.thumbnail = thumbnail.make_thumbnail(
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/thumbnail.py", line 20, in make_thumbnail
    img = reader.read(c=channel, series=i)
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 431, in read
    img = self.reader.read(series, c)
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 405, in read
    dtype = self.metadata.pixel_dtype
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 304, in pixel_dtype
    return self._pixel_dtypes[self._metadata.getPixelsType(0).value]
KeyError: 'float'

I tried to comment line 405 in reg.py
# dtype = self.metadata.pixel_dtype
to
  dtype = np.float32
and the error goes away.
if I try to do something like
        if dtype == 'float':
            dtype = np.float32
            print('manually changing dtype')

It still fails as the error happens at the moment of the self.metadata_pixel_dtype call.

Same later when appending the mosaic:
Traceback (most recent call last):
  File "/home/jmamede/anaconda3/envs/tensorflow/bin/ashlar", line 8, in <module>
    sys.exit(main())
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/scripts/ashlar.py", line 212, in main
    return process_single(
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/scripts/ashlar.py", line 250, in process_single
    mosaics.append(reg.Mosaic(edge_aligner, mshape, **mosaic_args_final))
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 996, in __init__
    self.dtype = aligner.metadata.pixel_dtype
  File "/home/jmamede/anaconda3/envs/tensorflow/lib/python3.9/site-packages/ashlar/reg.py", line 304, in pixel_dtype
    return self._pixel_dtypes[self._metadata.getPixelsType(0).value]
KeyError: 'float'

Although this made Ashlar go through the pipeline the output is between 0 and 1 and very saturated. I believe is the light correction. I also tried pushing the 'float' be assume to be a uint32 dtype and the same happens.

By modifying line 200-203 to:
class BioformatsMetadata(PlateMetadata):

    _pixel_dtypes = {
        'uint8': np.dtype(np.uint8),
        'uint16': np.dtype(np.uint16),
        'float' : np.dtype(np.ffloat32),
    }

made it go through.
However, the output is between 0 and 1 and very saturated. I believe it to be the light correction. I also tried pushing the 'float' be assume to be a uint32 or uint16 dtype and the same happens.


Scrollable line

Do you want to request a feature or report a bug?
feature/bug
What is the current behavior?
I want make line of editor scroll-able -> css property "white-space: nowrap" and "overflow-x: auto" for line.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
jsfiddle example: https://jsfiddle.net/marcin375/4k3bggmr/6/
When we enter data is alright:

but for example, when editor is empty and we enter 'space' input is empty and I'm not able to enter data:

What is the expected behavior?
Display scroll-x without error.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
"draft-js": "0.10.4"

@marcin3755 I faced with the same issue, did you find some solution?

@marcin3755 @denich
instead of
white-space: nowrap
use
white-space: pre


Made Home Page Responsive

Made Home Page Responsive
Issue : #1
@arpit456jain

Hey @arpit456jain Please review my PR

hey @Atif0604 can u share the video

hey @Atif0604 can u share the video

Yeah Sure

https://user-images.githubusercontent.com/64218887/146637723-6143dce0-d388-4a6c-9378-9bfd79d36c4f.mp4
Here the Video @arpit456jain

cool @Atif0604  i will merge it soon as i got the info about labels of levels

cool @Atif0604 i will merge it soon as i got the info about labels of levels

@arpit456jain you can merge it for now and whenever you get the labels you can label it
as i can move forward for the contribution to the project

sure @Atif0604


add context plug to employee_requests list endpoint

https://github.com/edenlabllc/ehealth.api/issues/791

Changes Unknown when pulling 918d56c70bf73db92eb2f1d53358fa314af131cf on add_context_plug_to_employee_requests#791 into ** on master**.

Changes Unknown when pulling 384d01776a712f27a1d06d19eb4c91f459ebfb5d on add_context_plug_to_employee_requests#791 into ** on master**.

Changes Unknown when pulling 384d01776a712f27a1d06d19eb4c91f459ebfb5d on add_context_plug_to_employee_requests#791 into ** on master**.

Changes Unknown when pulling b007980018ca2e43829bfcc0116bfb2bfe1b317d on add_context_plug_to_employee_requests#791 into ** on master**.


[SPARK-43687][SPARK-43688][SPARK-43689][SPARK-43690][PS] Fix NumOps for Spark Connect

What changes were proposed in this pull request?
This PR proposes to fix NullOps test for pandas API on Spark with Spark Connect.
This includes SPARK-43687, SPARK-43688, SPARK-43689, SPARK-43690 at once, because they are all related similar modifications in single file.
Why are the changes needed?
To support all features for pandas API on Spark with Spark Connect.
Does this PR introduce any user-facing change?
Yes, NumOps.lt,  NumOps.le, NumOps.ge, NumOps.gt are now working as expected on Spark Connect.
How was this patch tested?
Uncomment the UTs, and tested manually.

Merged to master.


[Feature request] Assisted inject in jdk8+ compiled with -parameters not requiring @Assisted

Introduction
I suggest to build a feature into guice that allows, when jdk8+ is used and -parameters flag is used with the compiler, guice can correlate the builder's methods with the right constructor based only on the names of the parameters which get stored in the .class file.
Allowing not requiring @Assisted at all.
It could work like this:
(Disclaimer: I don't know guice internals in detail so I may mention some things wrong. Just point me out and I will fix)
The high level idea works like this:
Proposal
API
I have two possibilities, you may implement both or even suggest an alternative one
Possibility 1
marching by param name is done by (for example):

new FactoryModuleBuilder().withParamNameMatching()

Possibility 2
Change FactoryProvider2's constructor so it can get flags. So far, only has one flag. If matching by param name is enabled (see above how it is set)
Alternatively, add a parameter to AssistedInject telling to match parameter names (E.g. @AssistedInject("MatchInterfaceParamNames"))
Changes
Store param names
Intro
Change Key or TypeLiteral so it also stores the param name when it is present.
Use:

Parameter::isNamePresent()
Method::getParameters gives the wanted Parameter[]

Alternative 1
FactoryProvider2:264 (281 in master branch):

Let the Key also store the names

Alternative 2
FactoryProvider2:259

Change TypeLiteral so it also stores parameter names

Manipulate param names
Manipulation 1
FactoryProvider2:496 (530 in master branch) -> FactoryProvider2.constructorHasMatchingParams:544

before "// If any keys remain and their annotation is Assisted, we can't use it."
If flag (mentioned above) is set and if Keys have parameter names:
-- Try matching the remaining name vs name
--- apply constructorKeys.remove(key) to the ones that matched

Manipulation 2
FactoryProvider2:498 (533 in master branch)

"%s has more than one constructor annotated with @AssistedInject"...
If the flag is active (either from the annotation or the method call), add the text:
"Confirm that you are compiling the code with '-parameters' in a jdk8+ compiler that supports the flag"

I imagine this does not exist. Personally relying on a javac flag for correct behavior here would be a poor experience (you'd get runtime failures based on whether or not you remember the -parameters flag) but you could make a case for it being added. Could you rephrase your initial post as a feature request rather than a question, and include more details about the behavior you'd expect - notably how this should handle -parameters not being specified.

@dimo414 That's my initial proposal with the limited knowledge I have of Guice.
Please comment on it and call for attention to problems I didn't notice.

@dimo414 Do you know if my suggestion can be applied? If so, any predictions?
Or
May I do it?

@ronshapiro Any comments about this?


Task/increase coverage

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
15 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.2%) to 88.439%

Files with Coverage Reduction
New Missed Lines
%

sis_provisioner/models.py
15
74.76%

Totals

Change from base Build<PHONE_NUMBER>:
1.2%

Covered Lines:
459

Relevant Lines:
519

💛  - Coveralls


[PowerRename] Add Filtering Feature

Summary of the Pull Request
Adds filtering feature where you can click on the column headers to see certain type of files.
PR Checklist

[x] Applies to #5026
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[x] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
Current filters

First column cycles between Selected and Flags Applicable filter

Selected: An item is visible if it is checked in the interface.
Flags Applicable: An Item is visible if current flags are applicable to the file.

Second column toggles Should Rename filter on/off

Should Rename: An item is visible if rename operation will be performed on it.

I am not sure about having two filters on first column, removing less desirable would be good. I would appreciate feedback about it.
PowerRename runs bulkier when a filter is on, that is because changing the number of items in the list view performs heavy memory operations. (Performance shouldn't be effected when no filter is selected)

@muratakburak
is it ready for review? If yes, change it from draft to open.

@muratakburak
can you resolve the conflicts and make sure that this warning are fixed before merging to master?
1>D:\git\mehmet\PowerToys\src\modules\powerrename\lib\PowerRenameManager.cpp(179,30): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
1>D:\git\mehmet\PowerToys\src\modules\powerrename\lib\PowerRenameManager.cpp(218,58): warning C4267: 'initializing': conversion from 'size_t' to 'UINT', possible loss of data

2>shcore.lib(api-ms-win-core-featurestaging-l1-1-1.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored
2>shcore.lib(api-ms-win-core-featurestaging-l1-1-0.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored
2>shcore.lib(api-ms-win-shcore-scaling-l1-1-2.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored
2>shcore.lib(api-ms-win-shcore-scaling-l1-1-1.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored
2>shcore.lib(api-ms-win-shcore-scaling-l1-1-0.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored
2>shcore.lib(api-ms-win-shcore-stream-winrt-l1-1-0.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in shlwapi.lib(SHLWAPI.dll); second definition ignored

@muratakburak
when the Search for field is cleared, it would be nice to reset the Preview to show all the files/folders

Some functions were not renamed accordingly causing a build break
https://github.com/microsoft/PowerToys/pull/6017/checks?check_run_id=1023812146


CRIMAP-286 Configure logging and filtering of PII

Description of change
Logs to stdout so other systems can route these logs to final destinations for viewing and long-term archival. For example this is needed to see the logs in Kibana.
Also, added PII parameters to the filter. These are also used by Sentry when reporting exceptions.
Link to relevant ticket
https://dsdmoj.atlassian.net/browse/CRIMAP-286
How to manually test the feature
On local environments this new log stream to stdout can seen and tested by running the app in production mode, or by using docker-compose.
In our k8s namespaces, logs will output to stdout and can be accessed in Kibana.

@timpeat Lograge removes ActionView logging, which also includes rendering times for partials. I think in development these can be quite useful. Additionally, depending on your IDE, these logs are interactive with clickable links to go directly to those files. See below.
The JSON one-liner is suitable for Kibana and similar but is not very human-friendly IMO, thus why I think is best to use it only in production.


Set all media queries to do <=1024px a mobile view

Describe the bug
Some mobile devices how the iPad Pro have this resolution and looks bad that the view have styles for Desktops Screens. Maybe the best is set the media queries to do the mobile view to 1024px.
Screenshots
This views looks bad on one iPad Pro:
The title is not aligned with the subtitle

The chat is not occuping 100% the view width

Expected behavior
This are behaviors that is expected to fix with this change of queries, if don't is fixed only changing the query, please add the needed changes to fix this problems
Checklist

[ ] All screens <= 1024px are considered a Mobile View
[ ] All screens >= 1024px are considered a Tablet View

Additional context
To reproduce please open the deploy page in your browser and open the browser Developer Tools, then click in responsive design view and change the view for the iPad Pro screen
Related issues

#149
#148

I confirm the issue is still present, yet minimal

https://dev--azordev-dasher-user.netlify.app/

In this issue, WHERE we should add the media query? @Katsu08

In this issue, WHERE we should add the media query? @Katsu08

I had think that do the change at all the project. But in general only this changes was mentioned by the client:
https://github.com/Azordev/dasher-user/issues/145
https://github.com/Azordev/dasher-user/issues/149
https://github.com/Azordev/dasher-user/issues/148

check that your tasks have the corresponding labels


OpenAPI3: Fix multipart union part conflict

Problem is that was now trying to create a new declaration for a named union if it was used in multipart and json even though they were the same

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@typespec/openapi3

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/3050/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/3050/


please give me download link of AsyncRAT 0.5.4J

i want to use AsyncRAT 0.5.4J

It was a beta-bugged version. link:
https://github.com/NYAN-x-CAT/AsyncRAT-C-Sharp/archive/7c8a4a3dffb0fcbda1bf323688eab26240cdfd0b.zip


Add 'Show in finder' option in file explorer - 3.X

@impact27 thanks for your contribution.
could you add the Fixes #NNN issue on the description? If there is no available issue open to relate this to, could you create the issue?

@impact27, please merge or rebase with the latest changes in our 3.x branch to fix the errors in CircleCI.

There is #2628 but this is only for OSX

I added the same option to the tabs in the editor. I had to redefine findInFinder as I needed access to self.get_current_filename()

For linux "xdg-open folder" works but I don't know how to select a specific file. No ideas how to do that in windows.

Could somebody test that with windows and linux? It works on mac

@impact27, I did an initial review to your work. Once we finish reviewing your code, we'll test it on Linux and Windows.

Thanks for the changes @impact27! Could you merge again with our 3.x branch to fix another error in CircleCI? Thanks!

I refactor to delete some duplicated code and make it more reusable, and merge it with upstream/3.x


Add logging of exceptions in BatchCalculateChecksumTask

This would make it easier to spot if calculation fails due to e.g. file system issues such as we have experienced on our production server lately.
Remember: no raise, only log!

Done.


Porting changes on perf dash made in Master branch

Some changes that were made in Master, but not in 1.1:
1- Added a constraint in the queries to show vCPU/1krps and memory/1krps only when there is a significant load in the mesh. There could be still a tail at the end of a load period that can be disproportional to the steady state values, but that it will be difficult to eliminate.
2- For istio-proxy cpu and memory, add only the values for the containers that are not in the istio-system namespace (i.e., only the application sidecars), since the others are already counted as part of the telemetry and ingressgateway pods.
3- When calculating memory per ingressgateway, the count of instances would return double the actual number, so added a filter to remove container=POD.
4- Added a text panel with a brief explanation of the charts and how to interpret the data.
Here is a snapshot:
https://snapshot.raintank.io/dashboard/snapshot/0w3SvOo0zgfUwpb5nYXKA66QnVlTpG3f

@wenchenglu please merge.

@jnativio: PR needs rebase.

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

@jnativio @douglas-reid
please ping me for merge once this PR is re-based

Created PR #12049 that includes this one.


ErsatzTV and ffmpeg bogs down the PC and makes it unusable.

I'm running plex and ersatz on a dell Optiplex 7010 running win10. It's an i7 with 4 cores. I'm also running with 16GB of ram. When I play just one show from the DVR guide from the plex app on my roku, or even on plexweb, ersatz/plex just clocks for about 60-120 seconds before it either plays or aborts. I watch the CPU performance and it pegs out at 100% and ffmpeg constantly shows at 70%-95%. On the other hand, when I play the very same show through plex, the CPU utilization is down around 15% or lower. Is there some sort of setting I can use to keep ffmpeg from making the PC unusable for viewing media through ersatz?

Creating a continuous IPTV stream has significantly higher requirements/overhead than streaming a single VOD item to a matching client (Plex has its own clients, ETV has no client).
There are basically two options to reduce CPU use:

Use a GPU for hardware acceleration
Use HLS Direct streaming mode (see docs)

HLS Direct is 100% a hack, but one that works with some clients to use very little CPU. TiviMate on Android is the one that most people use.

Even using hls direct fires something in ffmpeg and bogs down the machine

Note that if you are using Plex as a client, it does not support HLS Direct so ErsatzTV will force the channel to use MPEG-TS streaming mode regardless of the channel configuration.
Try HLS Direct with a client like MPV or TiviMate.

HLS process for channel 2.1 has terminated unsuccessfully with exit code 1: [AVHWDeviceContext @ 000001a389ddbc40] Failed to create Direct3D device Device creation failed: -1313558101. Failed to set value 'qsv=hw:hw,child_device_type=dxva2' for option 'init_hw_device': Unknown error occurred Error parsing global options: Unknown error occurred

@ellisd4 this issue should be fixed on the latest release - ETV now uses Direct3D 11 on Windows (d3d11va instead of dxva2) which should work better in headless environments.


Support output to stdout

In order to use this as a plugin to an internal statistic agent, we need the data to be sent to STDOUT and to not run as a daemon.
Added argument --once that causes the script to run once and then exit.
Added argument --stdout that causes the data to be sent to STDOUT instead of connecting to to GRAPHITE_SERVER.

How is this used such that you'd need stdout output?

I have another daemon that performs the data collection via plugins and handles sending to the proper upstream hosts.  The daemon runs the plugins and consumes the data sent to STDOUT by the plugin.

Due to the requirements unique to your environment, I will not be merging at this time. However, I'll leave this open and welcome any additional feedback from the community at large.

I wouldn't mind having the ability to send to stdout just to get an idea of the number and format of metrics being sent. It seems like this would be helpful debugging options if nothing else. :+1:


Add test for dir segment, truncate from right with whitespace in path

Do not merge! This is not ready yet! This is an attempt to reproduce #308 .
I need to create a PR to execute the tests on travis (although they were green on my local machine).

Still not merging =)

Just confirming that I still have not merged this! ;)

@dritter - Is this worth keeping open or should we close?

Ah. I forgot about this one.. Yep. Closing.


Clarify "Day Reminder" on README

Is your feature request related to a problem? Please describe.
On the README, it states:

The watch only supports all-day reminders. However, if the Google calendar event has a specific time, it will still be used as a day reminder on the watch.

I am not a current casio user so I don't know what a "day reminder" is :) Is this a daily alarm? Or is it a different kind of reminder that exists on the watch, such that there are two reminder types? Or is it something else?
Describe the solution you'd like
I'd like this sentence to be either clarified (day reminder vs daily alarm) or a description of what this really means for the user.

The watch only supports all-day reminders. However, if the Google calendar event has a specific time, it will still be used as a day reminder on the watch. This means that the time information will not be transferred to the phone but will still create an all-day reminder on the watch.

(Is my update correct?)
Describe alternatives you've considered
N/A
Additional context
Thank you for all your hard work :)

PS: If you just give me a thumbs up, I'll make a PR to update the docs according to my suggestion above.

Also... for time-specific reminders, is it possible to append the time itself to the reminder?
"Dinner @ 5pm" for example, could show up as the name of a 5:00pm reminder that has the label of "Dinner"

I'll put of town, and will respond to these in a day or two. The idea of
adding time to the reminder is good, and we can add it.
All your calendar events will show, but you can select up to 5, and these 5
will be sent to the watch.
For automatic time update, the calendar events will also be sent to the
watch as reminders.
The watch can update automatically, as long as the app is running. We did
not make it run forever in the foreground, because it is using too much
battery, but you can use something like MacroDroid to keep it up.
On Wed., Aug. 2, 2023, 12:38 p.m. Blaine Booher, @.***>
wrote:

Also... for time-specific reminders, is it possible to append the time
itself to the reminder?
"Dinner @ 5pm" for example, could show up as the name of a 5:00pm reminder
that has the label of "Dinner"
—
Reply to this email directly, view it on GitHub
https://github.com/izivkov/CasioGShockSmartSync/issues/46#issuecomment-1662563494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7M37TAS4CYX2OCCDR55VLXTJ7B5ANCNFSM6AAAAAA3BRFARI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for the quick response.
In the case of using MacroDroid (good idea) will it automatically select the first 5? Like would there be any kind of manual intervention needed from my end, especially if there are less than 5 reminders for today?

@booherbg : Yes, in automatic mode, the first 5 events will be sent to the phone. In interactive mode, the user can select which events to be sent to the watch, before sending. I though of saving the selection to be used in auto-mode as well, but events can change, so simple selected index will not work. I don't want to overcompensate things.
About the app staying up, and MacroDroid: At one time the app worked like the official Casio app, always keeping a notification on to stay running in the background. While that worked reasonably well, it was very annoying to see the app "always in my face". It also used more battery. So I moved away from this. In general, having user apps run constantly is not the Android way, and is discouraged by Google. Using MacroDroid works somewhat, but for perfect. I have a macro to start the app (If not running) 4 times a day, before the watch updates itself, and it worked, but not perfectly. So, your expectation of start-and-forget mode may not be fully achievable. BTW, I am considering re-introducing the always-run-in-the-background mode with notification for people who want to use it, but I'll make it optional. Most people use the app occasionally to set the time and timer, so they should not be "punished" with shorter battery life and annoying notifications.
Your idea of putting the time in the reminder is a good one, but my only concern is using up characters in an already very small reminder message (I think it is 16 chars). Many of my Google events are already cut-off on the watch. Also, I think the time should be in front of the message, something like "@8:30am: Meeting with John". So, you see 9 characters are used by the time, and the message will be: "@8:30am: Meeting". So, I'll look into it a but further.
By all means, create a PR to update the docs. I see you are a developer, so if you have some ideas on adding features or fixing the app, drop me a line and contribute to the project.

To be clear, the watch 5 has daily alarms, which can be set at specific time.
Also, it has 5 reminders, which can be set at a specific date, without specific time. These reminders are similar to Google's all-day events. They can be repeating on a particular weekday(s), month days, can have start and end date, The Casio reminders are not as advanced as the Google calendar's events. For example you cannot set a reminder on the second Tuesday of the month, but the app tries to implement as many features of the Google calendar as possible. For example, in Google calendar, you can set an event to repeat 4 times, staring on a particular date. Casio does not support that, but the app calculates the end date, and sets the reminder accordingly.
Hope this helps.

Done

Thank you for the great conversation. If I end up with one of these models I'll be sure to give good feedback.

👍
On Tue., Aug. 8, 2023, 1:49 a.m. Blaine Booher, @.***>
wrote:

Thank you for the great conversation. If I end up with one of these models
I'll be sure to give good feedback.
—
Reply to this email directly, view it on GitHub
https://github.com/izivkov/CasioGShockSmartSync/issues/46#issuecomment-1668947642,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7M37QGRJFK6YBAJUTENFLXUHHPXANCNFSM6AAAAAA3BRFARI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


added pr template

corresponds to issue-> #23
@Nivedita967

@Sloth-Panda  This is so long.
Please remove-

Type of change section
How Has This Been Tested?
Screenshots section
In checklist-

Checklist 5
Checklist 6

In the first heading, the spelling of issues is wrong. Please check.

@Sloth-Panda Have you solved this ?

@Nivedita967 Yes making new commit in few minutes

@Nivedita967 I have made the pr you can verify

Please add one section for the language in which the contributor coded.

done @Nivedita967

You have created checklist for languages, but in every pull request, contributor will contribute in only one language mainly. So, I think, leave that section for writing language and remove checklist.

check @Nivedita967

Nice :) Thanx.

Just one thing, In the section of language used, you have commented description.

@Nivedita967

Great :)


Test against nightly Gradle releases

Is your feature request related to a problem? Please describe.
We should prepare additional tests for running the Gradle IntelliJ Plugin against the nightly version of Gradle (currently 8.0).
Gradle provides nightly releases for such purposes as described here: https://gradle.org/nightly/.
Describe the solution you'd like
Such a change would require running additional tests set – next to the 6.8, 6.9.2, and 7.5.1 versions – but against a dedicated branch as it may require adjustments for satisfying breaking changes.
That can be easily achieved with reused workflows.

Implemented with: https://github.com/JetBrains/intellij-platform-gradle-plugin/commit/7b9a38af4760dec2c17c23934d7c6cf566c0b74a


Reserve promise rejections (i.e. async exceptions) for exceptional circumstances

With the browser's native prompt function, pressing cancel doesn't result in an error, but instead a null return value. (Similarly, with the native alert function, hitting escape doesn't result in an error, and with the native confirm function, clicking no doesn't result in an error but instead a false return value.)
I believe this to be the desired behavior. Especially when using the up-coming async/await feature of ES (being used already via Babel), the current swal2 behavior leads to some awkward control-flow...
let result
let error
try {
  result = await swal({
    text: 'What is your favorite color?'
    input: text,
    showCancelButton: true
  })
} catch (_error) {
  error = _error
}
if (error) {
  swal('I did not get your favorite color because "${error}".')
} else {
  swal(`Your favorite color is ${result}.`)
}

The following would be a bit nicer.
const result = await swal({
  text: 'What is your favorite color?'
  input: text,
  showCancelButton: true
})
if (result.dismiss) {
  swal('I did not get your favorite color because "${result.dismiss}".')
} else {
  swal(`Your favorite color is ${result.value}.`)
}

@limonte Would you review a PR adding an option to enable this behavior? Let's call the option rejections and have it default to true?

Please go ahead with a PR :rocket:

Excellent! Using TypeScript, I've already had this problem.
We should also keep that issue somewhere in our mind for the next major, to enable the new behaviour by default (and maybre remove the option and related code).

@limonte @toverux Does the same go with the API for the inputValidator method? It should signal a validation error (which is a user error, not a technical/system error) by resolving with the validation message, rather than rejecting with the validation message, right? A falsy resolution value would signal that validation succeeded.
The control-flow is not as bad here, but I think in principal we should not mix user errors with actual technical/system errors.

It makes it difficult to debug actual errors thrown inside the function. Also, if there are any errors in production, I want them bubbled up to Rollbar error reporting.
Same goes for rejections in preConfirm; I think they should be treated as real errors instead of a user validation message.
That said, to support validations for the "multiple-input" scenario, could we always call the function, even if input option was not provided?

Both of your comments make sense. But for beginning please implement the scope of the initial comment only. After reviewing and testing I will be able to decide what to do next. Thanks @mattbrunetti !

const {dismiss, value: favoriteColor} = await swal({text: 'What is your favorite color?', input: text})
if (dismiss) {
  swal('I did not get your favorite color because "${result.dismiss}".')
} else {
  swal(`Your favorite color is "${favoriteColor}".`)
}

const {value: name} = await swal({text: 'Full name?', input: 'text'})
const {value: location} = await swal(text: 'Location?', input 'text')
await swal(`Hi ${name}, from ${location}!`)

Totally beautiful, readable and maintainable code! Love it!
Go ahead with the PR when you're ready :rocket:

:tada: :tada: :tada: https://github.com/limonte/sweetalert2/releases/tag/v7.0.0

Uncaught SyntaxError: await is only valid in async function

rude answer to rude message: https://gist.github.com/Rich-Harris/0b6f317657f5167663b493c722647221

Fun fact: With Chrome 62 you can execute the above example code in your console.

But otherwise, top-level await is not allowed.


Merge remote-tracking branch 'upstream/stable' into merge_stable

std/regex/internal/tests.d(1054:1)[warn]: A unittest should be annotated with at least @safe or @system
make: *** [style] Error 1

@MartinNowak since two weeks or so, Dscanner enforces that every unittest is annotated with at least  @safe or @system as this is a simple trick to prevent regressions that was forgotten very frequently
https://github.com/dlang/phobos/pull/5166
-> I added @safe to the std.regex unittest

Btw @MartinNowak is there a way the Dlang-Bot could help you with the release process?
-> https://github.com/dlang-bots/dlang-bot/issues/48


[NOTICE] Add NOTICE

Why are the changes needed?

Add NOTICE file in this PRs.
Have a look on other projects, I only see Apache Spark maintains NOTICE-binary in repo, most projects generate it on build process.
For instance,
Apache Flink use shell collect_license_files to collect LICENSE and NOTICE files.
Apache Calcite use gradle plugin vlsi-release-plugins  to manage the whole release process, see build.gradle.kts.
Apache Kafka write gradle scripts to gather LICENSE and NOTICE files, see build.gradle.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #622 (777ca69) into master (998bf08) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #622   +/-   ##
=======================================
  Coverage   79.88%   79.88%
=======================================
  Files         118      118
  Lines        4554     4554
  Branches      549      549
=======================================
  Hits         3638     3638
  Misses        609      609
  Partials      307      307

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 998bf08...777ca69. Read the comment docs.


Update dcp_atomicpolygons

One reviewer required. Addresses issue #274 and one task in #272.
Update the url path to reflect change in the Bytes of the Big Apple server.
Test by running the dataset locally.

tested with 22c has success. Is this the only version we need to test for now?

I haven't tested any of the older versions but might be good to double check if we can do that

@td928 FYI I tested 22b and it doesn't work


Integrating example dataset with pixel, cell, and post clustering

This is for internal use only; if you'd like to open an issue or request a new feature, please open a bug or enhancement issue
Section 1: Design details
Relevant background
After the example dataset is finalized for the segmentation notebook, it needs to integrate seamlessly into pixel and cell clustering.
Design overview
This project will require us to refactor the directory structure of example_dataset. We should have no less than all the required input files for each script, and no extraneous files either.
Design list/flowchart
Because each notebook depends on an increasing number of dependencies, I think it's best to create multiple datasets on Hugging Face. In this way, users can either run the example cohort end-to-end (reusing outputs as inputs along the way, Hugging Face will not overwrite folders if they exist), or run the notebooks individually (which will download an example dataset as it appears at a particular step).
We should have a sample dataset folder for each of the following:

Extracted image data: already on Hugging Face (used by notebooks: 1, 2, 3 and 4)
Segmentation labels: contains the _feature_0.tif files  for each FOV from the sample cohort (used by notebooks: 2, 3, and 4)
Cell table(s): contains a cell_table_size_normalized.csv file from the cohort, this should have consensus labels assigned so it works for both notebooks 3 and 4 (used by notebooks: 3 and 4)
Pixel cluster output (used by notebooks: 3):

data/
└── example_dataset/
    ├── {pixel_cluster_prefix}_pixel_output_dir/
    │   ├── pixel_mat_data
    |   │   ├── fov0.feather
    |   │   ├── fov1.feather
    |   │   ├── ...
    │   ├── {pixel_cluster_prefix}_pixel_channel_avg_meta_cluster.csv
    │   ├── {pixel_cluster_prefix}_pixel_channel_avg_som_cluster.csv
    │   ├── {pixel_cluster_prefix}_cell_clustering_params.json

- Full pixel matrix data with channel expressions, pixel SOM cluster labels, pixel meta cluster labels, segmentation labels, etc. Each FOV has a separate file and is in `.feather` format.
- `pixel_cluster_prefix` is currently set to `'example_cluster'` in the notebooks, consider changing?
- The subset data directory and normalization `.feather` files are not needed for cell clustering.

Because the cell table gets annotated with consensus labels for post clustering, we don't need to store cell_mat_data generated in the cell clustering notebook on Hugging Face.

Required inputs
This is detailed in the above section.
When loading in the required inputs for each notebook, ensure that they are formatted in the structure:
data/
└── example_dataset/
    ├── input_data/
    │   ├── fov0/
    │   │   ├── ...
    │   ├── ...
    ├── segmentation/
    │   ├── deepcell_input/
    │   ├── deepcell_output/
    │   ├── deepcell_visualization/
    │   ├── {pixel_cluster_prefix}_pixel_output_dir/
    │   └── cell_table/

Extracted image data should be placed in input_data. Segmentation labels should be placed in deepcell_output. Cell tables should be placed in cell_table. We can make a separate directory for pixel_output_dir.
Output files
The outputs each notebook produces will be the same as running the example dataset through the entire process as it stands.
Section 2: Implementation details
Once you have completed section 1, please tag the relevant parties and iterate on the initial design details until everyone is satisfied. Then,
proceed to section 2
Control flow
Provide additional, more granular details (if necessary) about how the proposed coding logic will be put together
Milestones and timeline
List each of the major components of the project, and provide an estimated completion date for each one.

After downloading and moving the dataset to the proper data directory we would have:
Extracted Image Data:
data/
└── example_dataset/
    └── segmentation/
        └── deepcell_output/
            ├── fov0_feature_0.tif
            ├── ...
            └── fov10_feature_0.tif

Cell Tables:
data/
└── example_dataset/
    └── segmentation/
        └── cell_tables/
            ├── cell_table_arcsinh_transformed.csv
            └── cell_table_size_normalized.csv

And then for the Hugging Face Dataset, that would require a few more zip files, consisting of the following:
segmentation/
├── fov0_feature_0.tif
├── ...
└── fov10_feature_0.tif

cell_tables/
├── cell_table_arcsinh_transformed.csv
└── cell_table_size_normalized.csv

{pixel_cluster_prefix}_pixel_output_dir/
├── pixel_mat_data/
│   ├── fov0.feather
│   ├── ...
│   └── fov10.feather
├── {pixel_cluster_prefix}_pixel_channel_avg_meta_cluster.csv
├── {pixel_cluster_prefix}_pixel_channel_avg_som_cluster.csv
└── {pixel_cluster_prefix}_cell_clustering_params.json

For the name of the pixel_cluster_prefix, should we name it after the project it's from instead? Also if the pixel_cluster_prefix is already there for the pixel_output_dir do we need it for the som, meta, and cell_clustering_params files?

@srivarra we can, however we need to ensure this makes it into the pixel and cell clustering notebooks so it runs seamlessly.
We should probably update the pixel_cluster_prefix and cell_cluster_prefix vars, as well as the file names we load in prior to cell clustering.
Currently, we do need pixel_cluster_prefix in the som, meta, and cell_clustering_params file names. I agree it's a bit unnecessary since we're already putting them in a folder prefixed with pixel_cluster_prefix. @ngreenwald let us know what you think.

The segmentation and cell_tables folders should be standardized, like you mentioned above, so that they're only present in one spot. Currently, the segmentation example dataset only has the inputs, not the deepcell_output folder. We want the deepcell_output folder to be in the right spot. So if it's annoying to have a separate huggingface dataset with deepcell_output that needs to be copied into the previously created segmentation folder on the user's computer, I think it's fine to just have a single example dataset that contains all of the necessary files that we add to as we create the necessary data for the whole pipeline
You can pick a pixel-cluster prefix that makes sense, and then use that one and update it in the notebooks.
@cliu72 wanted the individual files named with the prefix, I think in case the user re-runs code to avoid overwriting. I don't remember if there was a reorg since then or not, you should check with her

I don't think we need the prefix for all the files - just the prefix on the directory name is fine. I think if a user re-runs code, they can just specify another prefix, which would make a new output directory.

Cool, thanks Candace.
Will you guys tag me in this once you've edited the design doc with all the changes? It would be helpful to have a single overview of the directory structure for all the files.

@srivarra can you check the updated structure to see if that works for HuggingFace?

@alex-l-kong yeah that will work.

@srivarra double checking the process, looks like there's no workaround for needing pixel_mat_data with the SOM and consensus labels added for cell clustering. The only way we can ensure pixel clustering doesn't skip the training steps
and cell clustering runs with the pixel labeled data is to put this in a separate folder.
This can still be easily integrated, as all that's needed is for cell_clustering_params.json to point to the correct paths. Namely, the ones assigned to the pixel_mat_data, pc_chan_avg_som_cluster_name, and pc_chan_avg_meta_cluster_name keys.

So will this reorganization mean that we lose the ability to skip reprocessing the data if it doesn't need to be?

@ngreenwald no, if there are already proper labels assigned to the data, reprocessing will be skipped.
This reorg just ensures that when running the example dataset through pixel and cell clustering, no steps fail or get skipped.


Super ambitious refactor of bundle install (work-in-progress)

Hoping to use gemspec, parse it and use data from there when setting up individfual gem targets and labels.
Not yet working but it's too late :)

Please keep this open for the time being, but this is not getting merged.


package.json repo link

Add github link to the package.json
  ...
  "repository": {
    "type": "git",
    "url": "https://github.com/kunyan/server-side-include"
  ...

fixed in #45


No  *cds_functions.tsv in the output file

phrokka version: v1.2.1
Python version:  2.10.8
Operating System: Linux

Description
I want to use
'./pharokka.py -i /work/hudi/lina/vir/checkv_outputs/LINA00089K_/vir_high_quality.fna -o /work/hudi/lina/vir/pharokka/separa_4/ -t 8 -f'
to get the *cds_functions.tsv.
Actually, it already generate a lot of output files. But it didn't contain this file.
'CARD              cleaned_phanotate.tsv  phanotate_aas_tmp.fasta  pharokka_04102023_151937.log  pharokka_minced_spacers.txt  trnascan_out.gff  vfdb_tmp_dir
CARD_results.tsv  mmseqs                 phanotate_out_tmp.fasta  pharokka_aragorn.txt          tmp_dir                      vfdb
CARD_tmp_dir      mmseqs_results.tsv     phanotate_out.txt        pharokka_minced.gff           top_hits_mmseqs.tsv          vfdb_results.tsv'
It also didn't have error message in the log file
I don't know why.

Hi @diedie9,
First of all I would recommend that you update to v1.3.0 (fixes a bug with the cds_functions.tsv #243).
Secondly, pharokka clearly failed to run - would you be able to upload the log file so I can have a look? I might be able to figure out the error.
George

Hi George,
Thanks for your suggestion.
I got the results that I want after update the version.
Die

Beautiful closing this now.


[BEAM-6876] Cleanup user state in portable Flink Runner

State had to be explicitly cleaned up in user state using timers which fire at
the end of a window. This uses the StatefulDoFnRunner to set timers to clean up
user state at the end of each window.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Java Flink PortableValidatesRunner Streaming

CC @robertwb @angoenka

I can see in the debugger that the clear calls are executed on flinkStateBackend as expected. But to confirm that we are not leaking memory, I need to run something over a meaningful period of time.

I think this should be good to go now.

The effect of cleanup is clearly visible when monitoring the checkpoint size. Without the fix, checkpoint size is climbing fast:

@tweise Great. Do you have these graphs also with the fix applied?

@mxm it's the same graph (job in the middle is without cleanup).

@tweise Ah, that looks perfect then.

Run Java PreCommit

Run Python PreCommit

Run Java PreCommit

Run Java PreCommit


VaadinSharedSecurity cannot access to configured sessionAuthenticationStrategy

When configuring HttpSecurity, VaadinSharedSecurity autowire the sessionAuthenticationStrategy bean, but this is actually not a bean, it's defined internally & always returns null. Please add a note that users need to create a sessionAuthenticationStrategy bean and use it like
http.sessionManagement()
        	.sessionAuthenticationStrategy(sessionAuthenticationStrategy())

This way, VaadinSharedSecurity caches correct sessionAuthenticationStrategy.

Sample application updated, README still not updated.

README updated.


Fixed Primary key import causing compile errors on code gen

While this does change the type to be Table.PrimaryKey, it does solve the issue presented with using Flywheel as indicated in #8

@Tapac these feel like straightforward but essential fixes. Is there anyone we can ping for it?

Completely agree, this pr is from January, more than a half year ago


Add google-analytics to document file

Resources

https://stackoverflow.com/questions/60411351/how-to-use-google-analytics-with-next-js-app
https://github.com/vercel/next.js/blob/canary/examples/with-google-analytics/pages/_document.js

Closes #61

@samarthdave try to run npm run build and figure out why the build is failing


Info in document doesn't match with UI

[Enter feedback here]
The document says "Enable SDK messages and flows included in the solution" but the UI currently says " Enable Plugin steps and flows included in the solution"

Document Details
⚠ Do not edit this section. It is required for lear

n.microsoft.com ➟ GitHub issue linking.

ID: 5a00b4a6-c147-cffa-92c9-5cb183c4ea67
Version Independent ID: 83d7d42c-71f3-1138-318f-5bd252a2ab3b
Content: Import solutions - Power Apps
Content Source: powerapps-docs/maker/data-platform/import-update-export-solutions.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @omarjimz. This issue has been assigned to the doc author for review.

@omarjimz - Thank you for your feedback. You're correct and the article has been updated to reflect the current import UI.
Closing issue.


ISPN-5335 ConfigurationBuilder with custom interceptor leads to shared instance

https://issues.jboss.org/browse/ISPN-5335

Thanks Radim, for Infinispan 8 we need to remove all configuration which refers to instances and only let users pass in classes.

Merged, thanks


release 0.7.27

Codecov Report

Merging #43 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master    #43    +/-   ##
======================================
  Coverage       0%     0%
======================================
  Files         133    136     +3
  Lines        5837   6047   +210
  Branches      578    615    +37
======================================
- Misses       5837   6047   +210

Impacted Files
Coverage Δ

...java/net/mm2d/android/upnp/cds/BrowseResponse.java
0% <ø> (ø)
:arrow_up:

...java/net/mm2d/android/upnp/avt/TransportState.java
0% <ø> (ø)
:arrow_up:

...et/mm2d/dmsexplorer/view/ServerDetailActivity.java
0% <ø> (ø)
:arrow_up:

...java/net/mm2d/android/upnp/cds/BrowseArgument.java
0% <ø> (ø)
:arrow_up:

...a/net/mm2d/android/upnp/AvControlPointManager.java
0% <ø> (ø)
:arrow_up:

...t/mm2d/android/view/TransitionListenerAdapter.java
0% <ø> (ø)
:arrow_up:

...java/net/mm2d/android/upnp/DownloadIconFilter.java
0% <ø> (ø)
:arrow_up:

...rer/view/delegate/ContentListActivityDelegate.java
0% <ø> (ø)
:arrow_up:

...et/mm2d/android/transition/SmilingCurveMotion.java
0% <ø> (ø)
:arrow_up:

...r/viewmodel/helper/MovieActivityPipHelperOreo.java
0% <ø> (ø)
:arrow_up:

... and 62 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 6098d10...c04629f. Read the comment docs.


Editor crash when editing project with a specific GDExtension

Tested versions
4.2 stable with godot-cpp 4.2
System information
Linux Mint 21.3 x86_64
Issue description
When I use gdextension to write my app , I got a crush. This BACKTRACK print looks so special and I could hardly find the reason.

Because it had not entry godot execution I guess this is a bug
And normal crash should be like this:

Steps to reproduce
none
Minimal reproduction project (MRP)
I even can't find the code that cause this error
but I make a copy of my wrong codes and upload it to:
https://github.com/alittlewhitey/MyGDEXTENSION_Bug
I bless it is a truly bug......

Can't test this specifically right now but looking at some of the code this could be related to this:

https://github.com/godotengine/godot-cpp/issues/1326

Can you please show the options you used when building?

This issue does not look like problem I had meet. I just downloaded godot from official website. I just use this Cmakelists with Environment var

This issue does not look like problem I had meet. I just downloaded godot from official website. I just use this Cmakelists with Environment var GalEnvironment as 0.

I had finished code changing.
Now please use
cmake . -DGalEnvironment=0
make
to finish build.
Thanks for your help

Thanks, I got help from others and found that it was a misunderstanding. I will now close this issue.


make footer consistent

@twiecki minor change to make footer consistent with other pages.
I'm going to do the update manually a couple of times next time you change a notebook, and then will automate the pull from your repo.  I just want to do it manually a couple of times before I automate it.  So, let me know.  I'm also subscribed to this repo so hopefully I will get the update when you change an otebook.

Thanks!


Keep up to date with ledatelescope - Alternative

This is an altenative to #10 which pulls in the ibverb-support branch from ledatelescope.  It might be easier to merge.

Wow, seven conflicts on #10 but 22 here.


unable to read external files on macos

Similar to this issue, I am trying to read a local yaml file in rust, i put the file in native_config directory under my project top directory. it works fine on linux however it complains not able to find the file on MacOS. I have tried the following but none of them work.

absolute path to the file.
add the directory and file into macos directory and they can appear in the Resources of the xcode project.
add the directory and file into "Copy Bundles Resources" of the Runner target or native-cdylib target in xcode

Is there any guidance to read external files on MacOS?

IMHO this is a rust problem instead of flutter_rust_bridge problem. Anyway, looks like it is a macos "sandbox" problem?


Passport migration issue

See screenshot.
Issue created from a Mattermost message by @qunabu.

Reproduce make init on develop branch

Refers to https://github.com/EscolaLMS/Core/pull/8

@qunabu bug is temporary fixed by rollback oauth migrations. make init works, however we need to refactor core to make it works with oauth migrations


Marquee: Add fix for alignment of non-scrolling child

This allows for alignment of the child when it fits fully, this is especially useful for when text changes and may or may not fit.
It should work with other child objects, but unit tests should be used to confirm the intended behavior.
This should resolve #295 and I thing would really only be an issue there, so if this needs to be fixed elsewhere let me know.

random question, why does my index.html and keepdir keep getting deleted when I mess with the pixlet code? I just ignore the changes, but is that expected behavior?

@betterengineering you may be in the process of working on this, so sorry if you are! But tidbyt/community#475 won't work if this is also not merged!


Fix authSuccessfull execution on each page refresh

Description
Changes proposed in this pull request:

Fix authSuccessfull execution on each page refresh

We should rename the  event handlers, as they might be confusing for the user.
Because actually the intention was to call it every time the auth data was read and validated ("the user is authenticated"). Include @hardl & beta users

We agreed that this event should be triggered only after successful authentication (not after page reload)


implement theme overrides

Hello!
As stated on other issues, I do really enjoy this theme and I'm using it daily but I'm still not happy with the diffs. I've been thinking that theme overrides should be implemented as other themes do, it's a missing feature within rose pine. The example I copy below does work but I think your theme is coded very nicely so I just give my tip for you to implement it instead of sending a proper PR:
theme.lua:

config.lua:

So then users can make stuff like this on their nvim configs:

i'm not against adding overrides, but until i have time to do so – there are undocumented git groups that you can mess with:
require('rose-pine').setup({
	groups = {
		git_add = 'foam',
		git_change = 'rose',
		git_delete = 'love',
		git_dirty = 'rose',
		git_ignore = 'muted',
		git_merge = 'iris',
		git_rename = 'pine',
		git_stage = 'iris',
		git_text = 'rose',
	}
})

please note, DiffAdd, DiffDelete, and DiffText are blended at 50% opacity which cannot be changed at this time
-- theme.lua code demonstrating blends
DiffAdd = { bg = blend(groups.git_add, p.base, 0.5) },
DiffDelete = { bg = blend(groups.git_delete, p.base, 0.5) },
DiffText = { bg = blend(groups.git_text, p.base, 0.5) },

hope this helps until overrides are added 😌

I did update the theme and I think those groups aren't working. I see all git diffs with black:

I didn't check all the code but I didn't see any re-mapping of the groups table to get the proper hex values from the palette.
As an example:
DiffText = { bg = blend(groups.git_text, p.base, 0.5) }
When it should be something like:
DiffText = { bg = blend(palette[groups.git_text], p.base, 0.5) }
It could work like that or directly mapping the whole groups table to re-write it the whole groups table before using it on theme.lua.

colours should now show for the diffs – there was a regression that caused the colors to not be applied

Just came here to say that diffs (both + and - were showing with a black background now).
Happy to see the update was just waiting for me to pull :grin:


[FEATURE] Neo4J Embedding pom for Java 8

Hi
currently when I compile a java program with the neo4j embedding dependency 0.33.0 I get the following error.
import dev.langchain4j.store.embedding.neo4j.Neo4jEmbeddingStore;
                                            ^
  bad class file: /Users/user/.m2/repository/dev/langchain4j/langchain4j-neo4j/0.33.0/langchain4j-neo4j-0.33.0.jar(dev/langchain4j/store/embedding/neo4j/Neo4jEmbeddingStore.class)
    class file has wrong version 61.0, should be 52.0
    Please remove or make sure it appears in the correct subdirectory of the classpath.

Any chance we can make it available for java 8. The other libraries are also supporting java 8.

@amirkhan-ak-sf java 8 is supported only by Neo4j 3.x which seems to be not supported any more: https://neo4j.com/docs/operations-manual/current/installation/requirements/#deployment-requirements-java
We are using 5.15.0


CP/M Filenames

If you copy standard CP/M .com files on to the SD Card in UPPERCASE, the Aquarius can not see them via AQDIR or AQCOPY. You have to rename the files to lowercase before you can see them within Aquarius CP/M. I have attached a couple of screen shots showing this. Note that the renamed lower case catchum.com and catchu.dat are seen, but the LADDER.COM and LADDER.DAT are not. This was the case with CATCHUM.COM and CATCHUM.DAT until renamed to lower case.

Fixed in V0.20a


test: Enable ccache by default for test runs

Nice to have a test flag for this! But I think to avoid a "broken default" for some users it should be disabled by default. Ccache requires local nix configuration changes before it will work. Then it would also match how it's used for nix-build/nix-shell.
There's also at least a theoretical chance that ccache is too aggressive and gives you old build artefacts, so could be useful to encourage running the final tests without it unless you know you really want to use it :-)

Sure, we can do that.


Add support large object based on file size

In the sample of php-opencloud, I see an example to allow create large object in segments (1GB).
https://github.com/php-opencloud/openstack/blob/master/samples/object_store/v1/objects/create_large_object.php

Thanks for this and apologies for the delay in reviewing this. Looks good to me. Could you update the tests?

OK let me update the test and re-submit again.

Update on this?

@anhphamt The current implementation fails tests with this error
BadMethodCallException: Method Mockery_0_OpenStack_ObjectStore_v1_Models_Container::getObject() does not exist on this mock object
A bit of digging suggests that the implementation might be wrong. The size method is called on the object, but it cannot exist yet as the upload hasn't yet happened.
Further, the createLargeObject support seems to be limited only to streams. Refer excerpt from the openstack v1 container
public function createLargeObject(array $data): Object
    {
        /** @var \Psr\Http\Message\StreamInterface $stream */
        $stream = $data['stream'];

I've tried to change the implementation accordingly but can't get it to work as the getSize method on the Stream results in the private size getting updated which still fails the tests as it is no longer recognized as a correct object.
It would be great if this could be figured out as having this feature would be really nice!

@sausin I will back to this in few days.

:+1:


Different similarity results when using text-embedding-3-small or text-embedding-3-large models

Context / Scenario
For the same document and question, when using text-embedding-3-small or text-embedding-3-large models, similarity returns results with lower relevance than when using text-embedding-ada-002 model.
What happened?
I'm using the code available at https://github.com/marcominerva/KernelMemoryService with SimpleVectorDb. I have imported the file Taggia.pdf, that is the PDF of the Italian Wikipedia page about the town of Taggia, Italy. Then, I have searched for "Quante persone vivono a Taggia?" (in English it is "How many people do live in Taggia?"),
If I use the text-embedding-ada-002, model digging into the source code of SimpleVectorDb,
https://github.com/microsoft/kernel-memory/blob/d127063db78943739397a952c0f19730306bfdab/service/Core/MemoryStorage/DevTools/SimpleVectorDb.cs#L115-L121
I obtain this:

However, if I use text-embedding-3-small (I have of course deleted the previous memories and re-imported the document), with the same question I get:

So, if I have these models I need to change the minRelevance parameter I use for my query. With text-embedding-ada-002, I use a value of 0.75, while with newer models it seems that anything grater than 0.5 is good. Do you agree?
NOTE: I get similar results also with Qdrant.
Importance
edge case
Platform, Language, Versions
Kernel Memory v0.35.240318.1
Relevant log output
No response

I think that's expected behavior. Bigger and newer models capture more details and understand content better. Something that might seem relevant to ada2 might be less relevant to the other models. The opposite can happen too. In general when switching models, it's recommended to "fine tune" also thresholds, prompts and other "semantic" settings. Similar scenarios present with text generation when moving from GPT 3.5 to 4, and to other models. It's similar to changing an image/sound/video compression algorithm at the core of a game, noticing different quality,performance and artifacts, with the need to revisit settings and requirements.
We briefly called this topic last year at //build and the need of a new generation of dev tools to measure AI behavior, it's still early days, with some options for prompts fine tuning. I haven't seen anything for embeddings yet though.

Thank you @dluc for the answer. Now I'm experimenting some weird situations in which a question that had a similarity of 0.79 with text-embedding-ada-002, now has only 0.33 with text-embedding-3-small and 0.27 with text-embedding-3-large, so it is very difficult to set a valid threshold.
Now I'm trying to increment the MaxMatchesCount in the SearchClientConfig and the MaxTokens used by Text Generation.

Thank you @dluc for the answer. Now I'm experimenting some weird situations in which a question that had a similarity of 0.79 with text-embedding-ada-002, now has only 0.33 with text-embedding-3-small and 0.27 with text-embedding-3-large, so it is very difficult to set a valid threshold.
Now I'm trying to increment MaxMatchesCount in the SearchClientConfig and MaxTokens used by Text Generation.

That's a pretty big difference, are the chunks the same?
Looking at the content, which model do you think is "right"? e.g. is the text actually relevant like ada002 says, or not so much as 3-small says?

Yes, chunks are the same. The text is relevant as text-embedding-ada-002 says. For example, among the others I have a chunk that contains something like "and near the town there is Vivaldi Palace, built in 1458", and I ask for "When was the Vivaldi Palace built?":

text-embedding-ada-002 tells me that the chuk have a similarity of 0.79 with my question
text-embedding-3-small returns a similarity of 0.33
text-embedding-3-large returns the lowest 0.27

I have made some other tests. In particular, I tried to change the PdfDecoder.ExtractContent method removing line endings with a space:
string pageContent = (ContentOrderTextExtractor.GetText(page) ?? string.Empty).ReplaceLineEndings(" ");

In this way, of course, chunks change, but with text-embedding-3-small I get a similarity of 0.41 and with text-embedding-3-large I obtain 0.32.


xrdp only binding to ipv6 and not using port settings from ini

Describe the bug
xrdp only binding to ipv6 and not using port settings from ini as the default port setting is passed via cli and trumps settings from the ini
Steps To Reproduce
Steps to reproduce the behavior:

use this gist https://gist.github.com/gotjoshua/3d7c51a76b3d74b213fc86e32cea3935
exclude the systemd section https://gist.github.com/gotjoshua/3d7c51a76b3d74b213fc86e32cea3935#file-configuration-nix-L38-L46
notice that the /etc/xrdp/ files are patched, but the port settings from xrdp.ini is not used

Expected behavior

the port variable ought to be a string and be used to patch the ini (not passed to the cli)

then one could just use ini syntax directly like services.xrdp.port = "tcp://:3389";

the service should use the /etc/xrdp ini files
by default the service should bind to both ipv4 and 6

Screenshots
without the systemd ExecStart patch it only binds ipv6

the ini file is used, via the direct nix store path (rather than /etc/xrdp/

$ sudo systemctl status xrdp.service
● xrdp.service - xrdp daemon
     Loaded: loaded (/etc/systemd/system/xrdp.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-04-17 20:37:42 WEST; 3min 36s ago
    Process: 325011 ExecStartPre=/nix/store/dyf3vgbq1lhpks3qrc4i5zjvaj4xzmv8-unit-script-xrdp-pre-start/bin/xrdp-pre-start (code=exited, status=0/SUCCESS)
   Main PID: 325055 (xrdp)
         IP: 0B in, 0B out
      Tasks: 1 (limit: 76411)
     Memory: 1.0M ()
        CPU: 9ms
     CGroup: /system.slice/xrdp.service
             └─325055 /nix/store/01zd6sxkym5a3aj6miwn2ip1id57bn82-xrdp-<IP_ADDRESS>/bin/xrdp --nodaemon --port 3389 --config /nix/store/l8i6gamqjdn4h0f8n7b6jl69ks7kg0zp-xrdp.conf/xrdp.ini

Apr 17 20:37:42 gotjosh-icase systemd[1]: Starting xrdp daemon...
Apr 17 20:37:42 gotjosh-icase systemd[1]: Started xrdp daemon.

Notify maintainers
@nagy @pennae @chvp
Metadata
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.25, NixOS, 24.05 (Uakari), 24.05.20240406.ff0dbd9`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(gotjosh): `""`
 - nixpkgs: `/nix/store/j10523yhkcc34478azkgcl70yzcx6j2j-source`

I am not a xrdp maintainer

I am not a xrdp maintainer

sorry bout that, i went with the last three commits that touched the file...
found this now
https://search.nixos.org/packages?channel=23.11&show=xrdp&from=0&size=50&sort=relevance&type=packages&query=xrdp
Maintainers
Charlotte Van Petegem<EMAIL_ADDRESS>@chvp are you still an active maintainer?

The section that would need updating is blamed on @lucasew, who is also not a formal maintainer...

I maintain the package, I have not touched the NixOS module yet (and I don't actively use the package anymore).

the port variable ought to be a string and be used to patch the ini (not passed to the cli)

I agree with that but that would require a bigger rewrite of the module. Right now the overrides are for the config files are created in a complicated way and they should be converted to just freeform settings, probably in an ini format.
Could you open a PR for that? Otherwise I would mark this point as wont-fix.

then one could just use ini syntax directly like services.xrdp.port = "tcp://:3389";

please test #315101

the service should use the /etc/xrdp ini files

Yeah true but that falls under my first comment.

4. by default the service should bind to both ipv4 and 6

is also fixed in my PR


Screen did not update when pressing Resume Insulin Delivery following suspend

Describe the bug
During the case where Issue #244 occurred, the user reported that the Resume Insulin Delivery key didn’t appear to be working and so she pressed it multiple times.
Attach a Log
Please see Issue #244 for detailed analysis
To Reproduce
We could not reproduce this issue using either the rPi DASH simulator or with an actual Eros pod.
This appears similar to the intermittent UI freezing issue described in #175.
Expected behavior
The UI should not continue to accept button presses if the display has frozen.
Screenshots
N/A
Setup Information (please complete the following information):
Refer to Issue #244
Technical Details
N/A
Additional context
N/A

If the display / app has frozen, it has frozen. Not sure what the expected behaviour for a frozen app would be other then to be… frozen?

Very likely fixed with the linked PRs, as well as TCD / Trio 1.0.0-dev.
Please re-open, if still remains.


Fix Xcode 15.3 build error on Intel Macs

Fix #536

Any update on getting this merged?

@erikdoe This is preventing us from using it on latest Xcode.

Could you make a new release?

We need the new version. Could you make a new release?

Had hoped to get the visionOS support included. This is not happening fast enough so I have made a release. However, as so often I have issues with CocoaPods. When I try to push the release I get the following error:
➜  ocmock git:(master) pod trunk push --allow-warnings

[!] Found podspec `OCMock.podspec`
Updating spec repo `trunk`
[!] CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/deprecated_podspecs.txt Response: URL using bad/illegal format or missing URL

Any idea what to do here?


comments

Comments:
+ single line
+ multiline
Comments
YAIWR comments can be used to explain the YAIWR code.
YAIWR comments can be used to prevent execution when testing alternative code.
Convention:

Single line comments should start with //
Multi-line comments should start with /* and end with */

Example:
let _a = 4; // let _a = 5;
// let _a = 5;
/*
  multi-line comment here
*/
println(_a);

In this example, the output will be 4.

dependant on https://github.com/softdevteam/pavel.yaiwr/pull/21

A common gotcha with comments is nested comments:
/*
  /*
     ignore this
  */
*/

what should happen?

It will be ignored as expected. \/\*(.|\n)+\*\/ ; should match anything from \* till */.
Added it to my test suite :point_right: 845fb53ace28311af4a04d8549c2b7d348b46242

My regex bring all the boys to the yard :)

No, you're right. My regex will ignore non-comment parts of the program as in your example

I think I will remove the multiline comment then from this PR. All I needed is single-line comments as // to add lang_tester but I got carried away

As the language creator, you can simply say "nested multiline comments are disallowed" :)

I keep on forgetting that I have this power :)

Ok, so as the language creator, I prefer to keep it simple. I'll remove multi-line comment support.
Actually, I will add it to my README backlog

multi-line comment no more :point_right:  74222ea3df8185e61ea7978a8adf727e99b6d9b2

please squash.

squashed :point_right: 1cf9efb0a43a3865b9ebe0d06f1556ff273e9ae6


feat(TDI-40958): update salesforce default endpoint to 44.0

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-40958
What is the new behavior?
default endpoint version to 44.0
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[x] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Pull request test result: success :star:
Sonar results


Update to latest JMH version

Motivation
JMH 1.22 was released recently, we might as well use the latest when running benchmarks.
Summary of changes: https://mail.openjdk.java.net/pipermail/jmh-dev/2019-November/002879.html
Modifications
Update jmh dependencies in microbench module from version 1.21 to 1.22.
Result
Benchmarks run using latest JMH

@netty-bot test this please


How to set emoji as a drawable instead of text?

Problem is that while i am set emoji using setThumbDrawable method the thumb was change but the floating emoji will be same as old default emoji

Well, this is the main issue. It is using getTextBounds and then drawText. I could use drawBitmap, but what would be the getTextBounds equivalent for a drawable?


Fix Pending Bug.

As a temporary solution to #22 (although the field is not intended to be optional) we make the missing field from response optional.

Merging without review because this is somewhat urgent.


Deprecate //sensor/camera/pose

A camera is the only sensor that allows specifying a pose element on top of //sensor/pose. I wonder if there is any utility in this or if it could be depreciated.
I can see how this might be relevant to the idea of specifying that a camera is attached at some position, and origin/center of the lense model has some offset to that. However, I think this case can easily be covered by setting the position of the //sensor to that position and introducing a fixed link from the sensor mount to the lense origin. This is likely a more accurate description anyway since the mount point is connected to a rigid body (the camera casing) which itself is attached to the lense system.
@azeey Would I have to write a dedicated proposal for this, or should this live here?

@scpeters Thanks for the info; that's interesting.
So I assume the advantage of a MultiCameraSensor over multiple Camera sensors on the same link is that you get one topic that publishes messages that aggregate all frames for each camera and that they are guaranteed to be synchronized?

@scpeters Thanks for the info; that's interesting.
So I assume the advantage of a MultiCameraSensor over multiple Camera sensors on the same link is that you get one topic that publishes messages that aggregate all frames for each camera and that they are guaranteed to be synchronized?

yes, exactly. This allows you to have synchronized stereo images, for example

Hm, fair. In that case, do you know the placement rules for //sensor/camera/pose, @scpeters ? I.e., which frame is //sensor/camera/pose @relative_to by default?
Intuitively, I would think //sensor; however, //sensor is actually not frame-bearing (it doesn't create an implicit frame). (If it does, we should add that to the spec somewhere :D) This makes //sensor/camera/pose the only place in the spec where a pose can be specified @relative_to something that is not a frame itself.

I believe the //sensor/camera/pose should be relative to the //sensor/pose by default, and we actually don't currently provide an API for resolving a camera pose if //camera/pose/@relative_to is set. I see two options:

deprecate and then remove //camera/pose/@relative_to. Then //camera/pose would only be relative to //sensor/pose, as //inertial/pose is only relative to its //link/pose
add SemanticPose API to sdf::Camera

I would favor adding SemanticPose API to sdf::Camera, but as @FirefoxMetzger mentioned, that would mean we have to make //sensor an implicit frame. I think the spec would be more consistent if all (even //inertial/pose some day) //pose elements behaved the same way.


Add per storage (partition?) metadata

The storage metadata should contain information on potential compression/encryption/serialization format as well as security related meta information, like an ACL (see #25)

For this, the file format and version need to be changed.
MAGIC[int32]
METADATASIZE[int32]
METADATAHASH[int32]
METADATA[Object]
  DOCUMENTSIZE[int32]
  DOCUMENT[Object]
  ...

The metadata needs to be user customizable and semantics should be like for the index metadata.


Buffer pool

English Only
Please check existing issues first to avoid duplication and answer the questions below before submitting your issue.
Use case(s)
When we are building a query, we can use strings.Builder. But in fact, we should think about reuse the buffer to avoid GC and improve the performance.
Usually, we will use sync.Pool to cache the buffer. But there is a problem that the buffer's capacity may be expanded when it was put back.
For example, the original capacity of buffer is 128, and it means that we can only store 128 bytes. However, we reuse this buffer to build a long query which has more than 128 bytes, e.g. 200 bytes, and then the buffer capacity was expanded to 256 bytes.
If most of the queries only need 50 bytes, it means that we waste a lot memory. A typical solution is avoiding cache big buffer.
Proposed Solution
(Please describe your proposed design/solution, if any)
Alternatives Considered
(Other possible options for solving the problem?)
Additional Context
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
(If you can, link to the line of code that might be helpful to explain the context)

I think we may need multiple pools. For example, one of them store the buffer < 128 bytes, another stores 128-1024 bytes.
If we use one pool, all the buffer in this pool finally will be expanded to the limitation. For example, if we do not store the buffer > 256bytes, all the buffer in this pool are possibly expanded to 256 bytes..

I think we may need multiple pools. For example, one of them store the buffer < 128 bytes, another stores 128-1024 bytes.
If we use one pool, all the buffer in this pool finally will be expanded to the limitation. For example, if we do not store the buffer > 256bytes, all the buffer in this pool are possibly expanded to 256 bytes..

Yes, I think it's necessary. The first version could simply divide pools. In the builder.go file, we return the Query struct, so do we include the size of Args in the calculation? Maybe we can cache the Query.

We don't need to think about the size of Args. We only take SQL into consideration.


fix(io): fix readAll() blocks

Signed-off-by: azjezz<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3209

Relevant Lines:
3209

💛  - Coveralls


Detect the build trigger/type in .csproj

I am wondering if there is any way to distinguish the trigger behind a build within the .csproj?
I ask in particular to dotnet core 2.0. I know that a few of the dotnet commands (dotnet <cmd>) actually trigger builds such as dotnet build and dotnet publish. I feel it would be useful to know what command triggered the build (build/publish) and use that information in a condition for a target.
<Target Name="DebugRunWebpack" BeforeTargets="Build" Condition="'$(BuildTrigger)' != 'publish'">
...
</Target>

If this is not available at the moment is there any workarounds?
Is there any appetite for it to be added in the future?

'$(MSBuildRuntimeType)' == 'Core'" is one thing I an aware of.

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275

This repo is no longer actively monitored. Closing up old issues that have not had activity in while. If this is still an issue, please open a new issue in an appropriate repo listed in microsoft/dotnet#1275


feat: support passing api key

Looks ok. Need to check once if "authorization" should be "Authorization"  here.
metadata.append(('authorization', 'Bearer ' + base64.b64encode(self.api_key)))

Using https://github.com/nvidia-riva/python-clients/pull/53 instead to pass generic metadata.


Upgrade to parcel v2, react 18 for example folder

Current Behavior
Example dir: Use parcel 1, react 16
src and package.json: use react 18
=> sometimes example can't run or has incompatibility issue
Desired Behavior
Both use react 18
Example dir uses parcel v2
Suggested Solution
Update example to

use parcel 2
update @types to use react 18 types
use react createRoot: tps://reactjs.org/link/switch-to-createroot
fix any consequential issues happening

refer pr #1183  for resolution.


Multicorn95 runs seem to have SEGVs import foreign schema

The import schema routine seems to be off by 1.
(gdb) p *routine
$2 = {type = T_FdwRoutine, GetForeignRelSize = 0x7f6d3d74d370 <multicornGetForeignRelSize>, GetForeignPaths = 0x7f6d3d74d300 <multicornGetForeignPaths>,
  GetForeignPlan = 0x7f6d3d74d9e0 <multicornGetForeignPlan>, BeginForeignScan = 0x7f6d3d74db30 <multicornBeginForeignScan>, IterateForeignScan = 0x7f6d3d74d220 <multicornIterateForeignScan>,
  ReScanForeignScan = 0x7f6d3d74c640 <multicornReScanForeignScan>, EndForeignScan = 0x7f6d3d74c700 <multicornEndForeignScan>, GetForeignJoinPaths = 0x0,
  AddForeignUpdateTargets = 0x7f6d3d74d090 <multicornAddForeignUpdateTargets>, PlanForeignModify = 0x7f6d3d74c680 <multicornPlanForeignModify>,
  BeginForeignModify = 0x7f6d3d74cf40 <multicornBeginForeignModify>, ExecForeignInsert = 0x7f6d3d74ce80 <multicornExecForeignInsert>, ExecForeignUpdate = 0x7f6d3d74cc40 <multicornExecForeignUpdate>,
  ExecForeignDelete = 0x7f6d3d74cd50 <multicornExecForeignDelete>, EndForeignModify = 0x7f6d3d74c690 <multicornEndForeignModify>, IsForeignRelUpdatable = 0x0, GetForeignRowMarkType = 0x0,
  RefetchForeignRow = 0x0, RecheckForeignScan = 0x7f6d3d74c630 <multicornExplainForeignScan>, ExplainForeignScan = 0x0, ExplainForeignModify = 0x0,
  AnalyzeForeignTable = 0x7f6d3d74c880 <multicornImportForeignSchema>, ImportForeignSchema = 0x0}

This is probably a mistake with the repo at http://yum.postgresql.org/srpms/9.5/redhat/rhel-7Server-x86_64/
I have rebuilt multicorn95 from 1.3.1 by doing "make release-zip", copy that .zip to ~/rpmbuild/SOURCES/ and changing the spec file version from 1.2.4 to 1.3.1.
Once, I did that the import schema actually works fine without a SEGV.
Hopefully this issue helps someone else who had issues with Multicorn from the PGDG repos.

Thank you for this report, I forwarded it to the PGDG yum repo maintainers:
<EMAIL_ADDRESS>


Migration laravel 9 above version

change migration class for future laravel version 9 to 11
change to class
change some facades in migration files

@tnylea and @emptynick

Hi,
Laravel 10 bug fixes are over since 7th August 2024, PHP Security fixes until February 2025.
Any chance to have this one moving forward?
Thanks in advance!

yes
@jonathanribas
Please  check this line of code in your codebase
https://github.com/thedevdojo/voyager/pull/5801/files
in this line
resources/views/bread/browse.blade.php

@bhargavraviya Better way is to fork and start over there as I think there will be any update for voyager from devdojo. They left voyager and in the new version of their product Wave, they will use Filament. You can see in the branch v.3 of wave, Voyager is not used anymore. We will follow you for the fork to have laravel 11 support.

@bhargavraviya Can we have your fork working for Laravel11?

@bhargavraviya Can we have your fork working for Laravel11?

yes it working on laravel 11
please check this PR #5878

Okay, I will test with your fork
https://github.com/bhargavraviya/voyager/tree/laravel11-migration
Thank you
On Sun, Sep 15, 2024, 15:46 Bhargav Raviya @.***> wrote:

@bhargavraviya https://github.com/bhargavraviya Can we have your fork
working for Laravel11?
yes it working on laravel 11
please check this PR #5878
https://github.com/thedevdojo/voyager/pull/5878
—
Reply to this email directly, view it on GitHub
https://github.com/thedevdojo/voyager/pull/5801#issuecomment-2351364372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ4KMTG7ROTOFEFPYT6BSNTZWUGJVAVCNFSM6AAAAABMZJDUQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJRGM3DIMZXGI
.
You are receiving this because you commented.Message ID:
@.***>


Call other CodeCommit repo/module

Hello,
When i launch an "account customizations" like for example, creation of a VPC i want to call another repo where the module is located in CodeCommit the problem is that the pipeline is 'connected' only in the destination account and therefore do not have the rights to access the repo
is it possible to improve this scenario ?
Thanks

Hey @Menahem1, thank you for this request.
We have a feature request in our backlog to support the use of private repositories and Terraform modules with AFT based on https://github.com/aws-ia/terraform-aws-control_tower_account_factory/issues/42. Please let us know if you have any additional context for us.

Hi @balltrev ,
Thanks, I had not seen, I am closing


[FEATURE] HP colour setting

Could a setting be added to control the colour of the HP bar (change the default green) not just the Temporary and Maximum colours?

Definitely, this feature is in progress.


[Bug]  CRUD field JS Does Not Play Nicely When Sorting Repeatable

Bug report
What I did
I added a rule in a repeatable crud field with a subfield
crud.field('rules').subfield('always_active').onChange(function(field) {
	if (field.value == 1) {
		crud.field('zmanim').subfield('when_to_show', field.rowNumber).hide();
	} else {
		crud.field('zmanim').subfield('when_to_show', field.rowNumber).show();
	}
}).change();

I then added more rows to the repeatable field and rearranged them.
What I expected to happen
Changing "always_active" shows/hides "when_to_show" on the same row.
What happened
Changing "always_active" shows/hides "when_to_show" on a different row.
What I've already tried to fix it
I've tried tweaking the repeatable blade file, but was unable to find the source of the problem. Essentially, when we are creating the rule, we are binding the specific field being edited to a row number. If instead we either bind a row number edited to a row number or if we bind the field to its neighbor, no matter the row - either option should fix it, I just couldn't think of the best way to do that
Is it a bug in the latest version of Backpack?
After I run composer update backpack/crud the bug... is it still there? Yes
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 8.3.2-1+ubuntu22.04.1+deb.sury.org+1 (cli) (built: Jan 20 2024 14:16:40) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.2, Copyright (c) Zend Technologies
with Zend OPcache v8.3.2-1+ubuntu22.04.1+deb.sury.org+1, Copyright (c), by Zend Technologies
with Xdebug v3.3.1, Copyright (c) 2002-2023, by Derick Rethans
LARAVEL VERSION:
<IP_ADDRESS>
BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.3.0
backpack/crud: 6.7.0
backpack/editable-columns: 3.0.1
backpack/generators: v4.0.4
backpack/pro: 2.1.8
backpack/theme-tabler: 1.2.8

Hey @zachweix
Your code works perfectly for me:
crud.field('features').subfield('quantity').onChange(function(field) {
    if (field.value == 0) {
		crud.field('features').subfield('value', field.rowNumber).hide();
	} else {
		crud.field('features').subfield('value', field.rowNumber).show();
	}
}).change();

Remove your custom repeatable field and check again.

Thank you very much!

Hey @zachweix thanks for the report.
I've just fixed this in backpack/crud 6.7.26 and backpack/pro 2.2.13 .
Let me know if you still experiencing issues regarding this 👍
Cheers


Use Debug package to determine free variables.

Fixes #6.
Tim, not sure if you are OK with adding a dependency on Debug. It already has the code to analyze scope so it seemed a shame to rewrite it.

I'm fine with the idea of depending on Debug---a clever idea to look there for tools.
If you want this to work for the 0.3 branch too, this will need to be backported (I can start a branch, or feel free to do so yourself). But honestly I'm fine with just supporting new features on 0.4.
Thanks for doing this!

My pleasure. I'm not particularly motivated to backport, although I'd be willing if there's demand from a 0.3 user.

Sounds good to me, too. You could ask for a beer to go with it :smile:.