DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_c1fad84c-f212-4036-ab34-87cb4d973266/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_c1fad84c-f212-4036-ab34-87cb4d973266.git

Docs Build status updates of commit 05220c6:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-ServiceAccountCannotAccessRepository] Your repository https://github.com/VSC-Service-Account/docs-archive-test-source has enabled Docs Build service account. It seems that at least one of the accounts, e2ebd2, does not have Read permission to the repo. Please ask your repo admin to grant correct permission to service accounts (refer to this document: https://review.docs.microsoft.com/en-us/engineering/projects/ops/engdocs/how-to-grant-service-account-permission-in-your-repository?branch=master#ops-e2e-ppe) and then retry the build. Don't know who to contact? Refer https://repos.opensource.microsoft.com/VSC-Service-Account/repos/docs-archive-test-source/permissions/ to get admin list of the repo if the repo is in one of the organizations Microsoft owns.

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


Remove deprecation warning

As long as the kivy source code contains templates itself, and this hardcoded exception list is needed, there should be no exceptions logged.
In particular, making your own FileListEntry appears the only way to get around font issues in internationalization.

I disagree, the code is correctly warning you that your modifications will stop working at some point, even though they are the only direct way to achieve what you want via the file chooser api.

I disagree, the code is correctly warning you that your modifications will stop working at some point, even though they are the only direct way to achieve what you want via the file chooser api.

I think as long as you need if name not in <hardcoded list> there should not be a warning.  The first step to deprecation should be for the core code itself to not rely on it, not to hack around it like this.

I agree with @inclement Kivy's core and widget base are two separate independent projects in a way. The code quality in core is much better than the widgets and in many ways we think of our widgets (except the core layouts etc) as demos. IMO we'd even separate kivy's widgets into its own sub-project if we could.
I'm saying this to point out that we made the decision for kivy's core to drop support for templates and that no one should be using it, hence the warning. Our filechooser widget needs to be completely re-written because to be frank, it's fairly crappy. So just because we haven't done that yet doesn't mean we should keep supporting templates, because that is not the correct decision for kivy's core.
The best workaround for you is to suppress these warnings.


Rawhide fails to build automatically.

Rawhide fails to build about half the time, due to a wine conflict (see https://github.com/Ultra980/danora-linux/commit/a6d2fa95d9e7a809dd27d8bc6ce78d54ffb8c94f). This could be an upstream issue, further testing is required.

This is an action that failed. The regular edition did not have this issue.

It seems to only fail on scheduled builds

Ok, the last 2 builds worked.

Bugzilla link

It now seems to work fine, even on scheduled builds.

build-rawhide is failing...Reopening

Wine dependency issue... again... with the same mesa thing... definitely upstream

A similar dependency issue happened to Danora 37 KDE and Rawhide. But not Gnome.

All. Builds. Failed. Same error. Screams internally


ISPN-5905 EntryIterator should only iterate on data container when local

and no loader used
https://issues.jboss.org/browse/ISPN-5095

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8277/wburns:ISPN-5095 for 8812208d3918cffb228afda78edd7aa45825d235
Tests: 11173, 1 failed (0 new), 22 ignored. Build time: 02:23:02
Failed tests detected

(since 22-Dec-2014) org.infinispan.test.integration.as.InfinispanLuceneDirectoryIT

Error message is logged
Build duration (secs) is too large: 8624

Moved out the inner class and also update the commit message as I had transposed to the 0 and the 9.

Pushed, thanks


Roddy dies with stack trace if submission/queue limit of LSF cluster is reached

If more jobs are submitted than allowed for the user, Roddy dies with a stack trace:
A workflow error occurred, try to rollback / abort submitted jobs.
bkill 14843 14844 14848 14849 14850 14852 14856
An unknown / unhandled exception occurred: 'Could not parse raw ID from: 'Group <resUsers>: Pending job threshold reached. Retrying in 60 seconds...''
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager.parseJobID(LSFJobManager.groovy:611)
de.dkfz.roddy.execution.jobs.BatchEuphoriaJobManager.extractAndSetJobResultFromExecutionResult(BatchEuphoriaJobManager.groovy:143)
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager.runJob(LSFJobManager.groovy:148)
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager$runJob.call(Unknown Source)
de.dkfz.roddy.execution.jobs.Job.run(Job.groovy:534)
de.dkfz.roddy.knowledge.methods.GenericMethod.createAndRunSingleJob(GenericMethod.groovy:507)
de.dkfz.roddy.knowledge.methods.GenericMethod._callGenericToolOrToolArray(GenericMethod.groovy:255)
de.dkfz.roddy.knowledge.methods.GenericMethod.callGenericTool(GenericMethod.groovy:50)
de.dkfz.b080.co.files.CoverageTextFile.plot(CoverageTextFile.java:49)
de.dkfz.b080.co.files.CoverageTextFileGroup.plot(CoverageTextFileGroup.java:47)
de.dkfz.b080.co.qcworkflow.QCPipeline.execute(QCPipeline.groovy:90)
de.dkfz.roddy.core.ExecutionContext.execute(ExecutionContext.groovy:625)
de.dkfz.roddy.core.Analysis.executeRun(Analysis.java:397)
de.dkfz.roddy.core.Analysis.executeRun(Analysis.java:341)
de.dkfz.roddy.core.Analysis.rerun(Analysis.java:229)
de.dkfz.roddy.client.cliclient.RoddyCLIClient.rerun(RoddyCLIClient.groovy:513)
de.dkfz.roddy.client.cliclient.RoddyCLIClient.parseStartupMode(RoddyCLIClient.groovy:116)
de.dkfz.roddy.Roddy.parseRoddyStartupModeAndRun(Roddy.java:721)
de.dkfz.roddy.Roddy.startup(Roddy.java:289)
de.dkfz.roddy.Roddy.main(Roddy.java:216)

The reason here is an interaction of Roddy and BE. It seems BE searches for a specific line in the output that is not found. Instead returns the wait-notice above. When s.th. like this happens on the command line upon manual submission, bsub blocks.

That should actually be catched and the jobs should be aborted.. Why does
that not happen?
Am 27. November 2017 1:52:49 nachm. schrieb Philip Reiner Kensche
<EMAIL_ADDRESS>
If more jobs are submitted than allowed for the user, Roddy dies with a
stack trace:
A workflow error occurred, try to rollback / abort submitted jobs.
bkill 14843 14844 14848 14849 14850 14852 14856
An unknown / unhandled exception occurred: 'Could not parse raw ID from:
'Group <resUsers>: Pending job threshold reached. Retrying in 60 seconds...''
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager.parseJobID(LSFJobManager.groovy:611)
de.dkfz.roddy.execution.jobs.BatchEuphoriaJobManager.extractAndSetJobResultFromExecutionResult(BatchEuphoriaJobManager.groovy:143)
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager.runJob(LSFJobManager.groovy:148)
de.dkfz.roddy.execution.jobs.cluster.lsf.LSFJobManager$runJob.call(Unknown
Source)
de.dkfz.roddy.execution.jobs.Job.run(Job.groovy:534)
de.dkfz.roddy.knowledge.methods.GenericMethod.createAndRunSingleJob(GenericMethod.groovy:507)
de.dkfz.roddy.knowledge.methods.GenericMethod._callGenericToolOrToolArray(GenericMethod.groovy:255)
de.dkfz.roddy.knowledge.methods.GenericMethod.callGenericTool(GenericMethod.groovy:50)
de.dkfz.b080.co.files.CoverageTextFile.plot(CoverageTextFile.java:49)
de.dkfz.b080.co.files.CoverageTextFileGroup.plot(CoverageTextFileGroup.java:47)
de.dkfz.b080.co.qcworkflow.QCPipeline.execute(QCPipeline.groovy:90)
de.dkfz.roddy.core.ExecutionContext.execute(ExecutionContext.groovy:625)
de.dkfz.roddy.core.Analysis.executeRun(Analysis.java:397)
de.dkfz.roddy.core.Analysis.executeRun(Analysis.java:341)
de.dkfz.roddy.core.Analysis.rerun(Analysis.java:229)
de.dkfz.roddy.client.cliclient.RoddyCLIClient.rerun(RoddyCLIClient.groovy:513)
de.dkfz.roddy.client.cliclient.RoddyCLIClient.parseStartupMode(RoddyCLIClient.groovy:116)
de.dkfz.roddy.Roddy.parseRoddyStartupModeAndRun(Roddy.java:721)
de.dkfz.roddy.Roddy.startup(Roddy.java:289)
de.dkfz.roddy.Roddy.main(Roddy.java:216)

The reason here is an interaction of Roddy and BE. It seems BE searches for
a specific line in the output that is not found. Instead returns the
wait-notice above. When s.th. like this happens on the command line upon
manual submission, bsub blocks.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/eilslabs/Roddy/issues/161

The job is aborted (bkill). The first problem is not that the handling of the job-failure is not o.k. (although this also is the problem), but that the error actually occurs. Roddy needs to be able to handle full submission queues!

Is it really a Roddy problem? In the end yes, but at first, the error should be catched by the LSF job manager right? The error is there.

I moved it to BE and close it here. BE will need to throw a proper exception, Roddy needs to catch that then.


mrf bug

There's a bug in mrf in bossash such that it reads the same 1k over and over.
I think you want something like 'addr += fbytes' in the loop.

Thanks, fix committed.


[BUG] send log to webhook (discord)

Before submitting a bug report...

[X] This bug wasn't already reported.
(I have checked every bug report on GitHub)

Title

[X] The title is no longer "[BUG] Title" and I edited it with the right error name.

Describe the bug
i added like some issues said -vn to send log to webhook but its saying this:
usage: main.py [-h] [-v] [-l LANG] [-g GEO] [-p PROXY] [-t TOKEN CHAT_ID] [-d DISCORD]
main.py: error: argument -v/--visible: ignored explicit argument 'n'
Copy and paste your error
usage: main.py [-h] [-v] [-l LANG] [-g GEO] [-p PROXY] [-t TOKEN CHAT_ID] [-d DISCORD]
main.py: error: argument -v/--visible: ignored explicit argument 'n'
Screenshots
usage: main.py [-h] [-v] [-l LANG] [-g GEO] [-p PROXY] [-t TOKEN CHAT_ID] [-d DISCORD]
main.py: error: argument -v/--visible: ignored explicit argument 'n'
Value of dashboard variable
not that problem

I believe verbose messages are not enabled in this repo. Someone might have made a fork and enabled the -vn flag for logs to discord. It is saying that because there is an argument for -v, but there is none for -vn.


[bugfix]: subDirLinks iterate bugfix

Subdirectory traversal may mistake the parent path as a subdirectory, resulting in an incorrect video address in the end.

修复了一个子目录遍历的小问题

谢谢


Cannot change any phaser attributes once it is created ie while running?

The feature you'd like
I'd like the phaser attributes (Q, frequency, baseFrequency etc to be settable after the Phaser is construted.
Any alternatives you've considered
It's possible that I'm missing something here or it is possible and I haven't worked out how. The only way I can think from looking at the docs is is of constructing a new Phaser Object whenever the values change, but this doesnt seem like a good idea. It is also possible that this isn't really how the Phaser should work i.e. the values shouldnt be settable. I am not a sound engineer but I am making something for one and he is asking for the above in the module that we're making.
Additional context
I want to add a phaser to a noise component and then edit the noise on the fly -
 noise.current = new Tone.Noise().toDestination();
 noise.current.volume.setValueAtTime(noiseVol, 0)
 phaser.current = new Tone.Phaser(phaserState).toDestination();
 noise.current.connect(phaser);

To do this I need to be able to set these attributes in the UI -
const [phaserState, setPhaserState]  = useState(
{
frequency: 0,
octaves: 0,
baseFreq: 0,
Q: 0,
}
Feature Requests will eventually be closed if inactive

hey - It appears that I might have misunderstood and phasers (or at least ours) doesn't need to edit its settings on the fly. I presume that is why it isn't even possible in tone.js?

This is the error message if i try and edit frequency for example.

Ugh. It's 'phaser.current.frequency.value = newValue' isn't it.

Glad you figured it out! yeah all those audio params need to be set through .value as you mentioned (e.g. phase.frequency.value = 10)
I will look into maybe surfacing a better error for this situation


Not support numColumns > 1

I tried it and found this component doesn't support numColumns > 1. Do you have any plans to support grid draggable in the future? If not, do you have any ideas how to solve it when numColumns = 2？
<FlashDragList
  data={data}
  itemsSize={ITEM_HEIGHT}
  numColumns={2}
  renderItem={renderItem}
  onSort={onSort}
/>

Hello, the component doesn't support numColumns because it's not descending from FlatList.
The support for multiple columns is not in our plans.
I guess implementing it requires changing most of the code.

Thanks for your response. I will try to solve it myself.

Thank you. PRs are welcome and we can also support or suggest the implementation if needed.


Rename containerService.Webook to containerService.Webhook

Fixes: #492
Also adds some missing data sources

The old resource doesn't seem to be marked as deprecated. Do we still not support that?

@mikhailshilkov we do not - can you open an issue in the bridge repo to add that?

@stack72 Opened https://github.com/pulumi/pulumi-terraform-bridge/issues/133

thanks!!


Remove quotes for boolean values in VersatileToolboxSystem

Jenkins probably should have caught that.. @techman83 ref https://github.com/KSP-CKAN/NetKAN/pull/3245

I could build the files with the quotes succesfully using netkan.exe.

@Olympic1 yep, netkan doesn't have the issue, ckan.exe does (which is why it failed netkan-bot's indexing with "Schema validation failed")

@plague006 Ahh, we're assuming that the netkan is producing valid data during testing, but the indexer doesn't want to auto-commit invalid data, so it does a sanity test.


Rounded scope corner

Problem
It would be nice to have a way to configure rounded corner between the vertical scope guide and the underlined first line.

Expected behavior
Instead of the sharp connection between the guides, I envision something like the rounded borders in floating windows.

Yeah would be nice, but it's not possible.
The horizontal line is not a unicode character, it's underline. There is no way to render this differently.
To get corners like the floating window border, there would need to be a whole extra line.

I understand. Thanks anyway!


📺  Also add the virtual_display argument to BackgroundPlotter in pyvistaqt

[ ] Also add the virtual_display argument to BackgroundPlotter in pyvistaqt

Originally posted by @tkoyama010 in https://github.com/pyvista/pyvista/pull/848#issuecomment-665406449

Close by https://github.com/pyvista/pyvista/pull/848#issuecomment-723535988

Close by https://github.com/pyvista/pyvista/pull/848#issuecomment-723535988


sig#811 verify retrigger endpoints existing in frontend or not

Description
To  enhance the functionality for the endcustomer in the frontend we would need to clarify the existance of the endpoints in the frontend.
therefor the attached list should be enhanced by the information if the retrigger is executable via the frontend and if this is the case where this can be found.
based on the results we can then define how we make the missing endpoints accessible to the frontend.
Trigger_Overview_2.xlsx
Acceptance Criteria

[ ] provide a clear answer if an endpoint does exist in the frontend
[ ] provide a clear guidance where the endpoint can be found if he is accessible via the frontend

Additional Information

A retrigger process API access for application registration has been implemented in a generic way here:
https://github.com/eclipse-tractusx/portal-frontend/blob/main/src/features/admin/applicationRequestApiSlice.ts#L274-L280
/api/administration/registration/application/${args.applicationId}/${args.endUrl}

The hook receives two arguments - the application id and end url which is currently one of:
trigger-identity-wallet
retrigger-clearinghouse
override-clearinghouse
trigger-self-description
trigger-bpn?processTypeId=RETRIGGER_BUSINESS_PARTNER_NUMBER_PUSH',
trigger-bpn?processTypeId=RETRIGGER_BUSINESS_PARTNER_NUMBER_PULL',
trigger-bpn?processTypeId=OVERRIDE_BUSINESS_PARTNER_NUMBER',

Currently the only use of this hook is here:
https://github.com/eclipse-tractusx/portal-frontend/blob/main/src/components/shared/basic/ProgressVerificationButton/index.tsx#L220-L231
It's not a complicated task to extend or implement more similar endpoint access points.


Microsoft graph is not pushing any notification even after mail is received in inbox

I used this sample to create subscription for my inbox and notification URL is also successfully verified. But even after receiving mail into my inbox, graph is not posting any notification to URL. Can someone please assist me? Let me know if more info needed.

Not really sure what would cause this if the POST to your app for verification went through, unless you restarted ngrok or something? That would cause the tunnelling URL to change, but the subscription would still be using the old URL.
There's always the possibility that notifications are delayed if something's wrong on the server side (high load, etc.) as well.

closing the issue as it's old. Feel free to re-open with more details if you're still having issues


Allow Symfony 7

Same as #17

#19 solved most of the CI issues, but now I discovered that I need to allow Symfony 7 in facile-it/symfony-functional-testcase!

@starred-gijs are you able to test this PR in your project(s)?

Reviewing the diff, there's no significant difference to grant more testing, I'll proceed with a new minor tag.

Sorry I was not able to test this yesterday. Thanks for your work, very much appreciated!


[feature request] useful export configuration

I am in the process of cloning my work PC.
Export from "File -> Export" exports pretty much nothing.
How do i backup and restore Database configurator option?
Workspace options?
Tools options?
There is nothing.

Hi @wiwwo ,
why do File -> Export doesn't suit you?
You could choose DBeaver - Project and then import it the same way.

Couse the only thing is exported there is "Keyboard shortcuts"

works for me (gif attached). Could you provide steps to reproduce an issue?

Ok! Is there a plave i can go to export (and then import) all settings?

At beginning we have to make justice to DBeaver saying that it is possible to transfer most crucial settings using existing buil-in tools. But it is a hassle.
Most export/import options can be found in File menu.
To transfer connections you have to use export/import of Project
To transfer some settings, incl hotkeys, you have to use export/import of Preferences. It's not clear why there is distinction between Keys preferences and ALL. It gives impression something lacks here. Ie other categories.
To transfer templates however, there is no option in File/Export. But you have to go to Window/Preferences/Editor/SQL Editor/Templates to find export/import option in this location.
To add to that, every part of configuration is stored in different file format.
There are some things cannot be transferred (ie colours of environment). Question is how many other things.
All in all, it makes this experience very inconsistent and cumbersome. Export/Import of DBeaver really deserves the overhaul.
with regards


fix: button: removes focus outline and border style when not in keyboard mode

SUMMARY:
The :focus selector property is not needed. It was reported that the buttons appeared to be stuck in an active state after click. This change removes :focus and defers to .focus-visible:focus-visible, only showing the focused state when using keyboard via the ConfigProvider.
JIRA TASK (Eightfold Employees Only):
ENG-22620
CHANGE TYPE:

[X] Bugfix Pull Request
[ ] Feature Pull Request

TEST COVERAGE:
NA
TEST PLAN:
Pull the PR changes, build storybook and verify focus styles and that they only appear when using keyboard in the ConfigProvider story view.

is this the general approach to focus highlighting we should be using?

Overall, yes - but there may be some slight differences with where the border shows depending on the component (offset inner or outer)

Codecov Report

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

@@           Coverage Diff           @@
##             main     #205   +/-   ##
=======================================
  Coverage        ?   86.95%
=======================================
  Files           ?      207
  Lines           ?     6831
  Branches        ?     2262
=======================================
  Hits            ?     5940
  Misses          ?      877
  Partials        ?       14

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 427bca7...bf6b4b4. Read the comment docs.


Adding 6 more projects to the feed wrt #191

Fixes #191
Added 6 more projects to the feed

[x] Feature enhancement

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.
Close: #191

Hey @SUGAM-ARORA , kindly review the changes


Non-focused statusbar have a strong blue at doom-vibrant and doom-one

I don't like that very much, how I can make that color more soft? Probably is some face attribute, but the correct name would be a nice help.

Thanks. I appreciate the well made themes, this was a long journey until finish here with the doom-themes.

You appear to have a customized mode line. Those blue segments are typically caused by a custom modeline segment that doesn't update itself when the window is no longer selected, which isn't something the theme can necessarily fix.
Do you have your modeline config up somewhere where I can see it?

I fixed with your suggestion, thanks.  I'm closing this since this was fixed, thanks for the quick answer/guide.

Sorry for this, but for some reason this behavior come back. My personal setup is host in ryukinix/dotfiles where I use with the Prelude config for emacs.
My custom.el is that: curl http://ix.io/Fki

A weird thing: thins seems to happen only when I use the daemon of emacs... which is even more bizarre. If attach my frame-session by emacsclient on the daemon I get this issue, but if I call directly /bin/emacs works as expected.

To avoid any pain to setup my environment, you can download here: https://www.dropbox.com/s/zo8g2fsluid65gy/ryukinix-emacs.d.tar.gz?dl=0
As I can seems a problem with a side-effect of loading the zenburn theme before as default of Prelude. Trying reload the theme again at customize-theme (enable doom theme) fix that, but this is a manual fix...

This happens even with the terminal session using the daemon as well. This is really curious for me... which thing can the daemon set or do to get this behavior?
Sorry for all the flood here.

HMMMMMMMM this seems something related to the face-attribute for selection as well!

Ah, I misunderstood your original problem. I am familiar with this issue. The theme has several classes for each face. Meaning the colors are different depending on how many colors your session supports.
If you load the theme while the daemon is loading, the daemon "frame" supports no colors at all, so the theme thinks your display supports the minimum number of colors, and you get these shoddy colors.
The trick is to load the theme when new frames are created, something like:
(defun init-theme (_frame)
  (load-theme 'doom-one t)
  (remove-hook 'after-make-frame-functions 'init-theme))

(if (daemonp)
    (add-hook 'after-make-frame-functions 'init-theme)
  (init-theme))

Unfortunately, I'm about to head out for several hours. I'll expand on this when I return if it isn't sufficient.

https://stackoverflow.com/questions/18904529/after-emacs-deamon-i-can-not-see-new-theme-in-emacsclient-frame-it-works-fr
Yes! Thanks, this fix all my problem. ❤
Sorry again for the flood.


[update_engine] unittest fails to build on googletest

Description
Found when adding CI for update_engine
https://github.com/kinvolk/update_engine/blob/flatcar-master/.github/workflows/c-cpp.yml#L29
make check
[...]
  CXX      src/update_engine/zip_unittest.o
  CXX      src/update_engine/test_http_server.o
  GEN      unittest_key.pub.pem
  GEN      unittest_key2.pub.pem
writing RSA key
writing RSA key
  CXXLD    test_http_server
  CXXLD    update_engine_unittests
/usr/bin/ld: cannot find -lgtest
/usr/bin/ld: cannot find -lgmock
collect2: error: ld returned 1 exit status
Makefile:1178: recipe for target 'update_engine_unittests' failed
make[2]: *** [update_engine_unittests] Error 1
Makefile:1688: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
Makefile:1691: recipe for target 'check' failed
make: *** [check] Error 2

Impact
Not yet automating the unit tests for update_engine
Environment and steps to reproduce

Set-up: this is on ubuntu-18.04 and then review that workflow for all the other steps
Action(s): make  check

Expected behavior
make check to run (and then succeed :wink: )

For the record, I took a look at the CI while fixing https://github.com/kinvolk/Flatcar/issues/388.
We first need to expand the LD_LIBRARY_PATH because librootdev was not found (ldd ./update_engine_unittest): https://github.com/tormath1/update_engine/commit/5552df4e583f6875eafc02bd01063b12c4b2f116
Then we hit a segfault ...
(gdb) bt
#0  0x00007fefe040f2fe in std::_Rb_tree_decrement(std::_Rb_tree_node_base*) () at /lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x000055a1c0262053 in std::_Rb_tree_iterator<std::pair<void const* const, testing::internal::CallReaction> >::operator--() ()
#2  0x000055a1c0261f8d in std::_Rb_tree<void const*, std::pair<void const* const, testing::internal::CallReaction>, std::_Select1st<std::pair<void const* const, testing::internal::CallReaction> >, std::less<void const*>, std::allocator<std::pair<void const* const, testing::internal::CallReaction> > >::_M_get_insert_unique_pos(void const* const&) ()
#3  0x000055a1c025fc9c in std::_Rb_tree<void const*, std::pair<void const* const, testing::internal::CallReaction>, std::_Select1st<std::pair<void const* const, testing::internal::CallReaction> >, std::less<void const*>, std::allocator<std::pair<void const* const, testing::internal::CallReaction> > >::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator<std::pair<void const* const, testing::internal::CallReaction> >, void const* const&) ()
#4  0x000055a1c025d761 in std::_Rb_tree_iterator<std::pair<void const* const, testing::internal::CallReaction> > std::_Rb_tree<void const*, std::pair<void const* const, testing::internal::CallReaction>, std::_Select1st<std::pair<void const* const, testing::internal::CallReaction> >, std::less<void const*>, std::allocator<std::pair<void const* const, testing::internal::CallReaction> > >::_M_emplace_hint_unique<std::piecewise_construct_t const&, std::tuple<void const* const&>, std::tuple<> >(std::_Rb_tree_const_iterator<std::pair<void const* const, testing::internal::CallReaction> >, std::piecewise_construct_t const&, std::tuple<void const* const&>&&, std::tuple<>&&) ()
#5  0x000055a1c025af29 in std::map<void const*, testing::internal::CallReaction, std::less<void const*>, std::allocator<std::pair<void const* const, testing::internal::CallReaction> > >::operator[](void const* const&) ()
#6  0x000055a1c0255158 in testing::(anonymous namespace)::SetReactionOnUninterestingCalls(void const*, testing::internal::CallReaction) ()
#7  0x000055a1c02551c7 in testing::Mock::AllowUninterestingCalls(void const*) ()
#8  0x000055a1c011bfd1 in testing::internal::NiceMockImpl<chromeos_update_engine::PrefsMock>::NiceMockImpl()
    (this=0x55a1c03365a8 <chromeos_update_engine::(anonymous namespace)::mock_system_state+8>) at /usr/local/include/gmock/gmock-nice-strict.h:145
#9  testing::NiceMock<chromeos_update_engine::PrefsMock>::NiceMock() (this=0x55a1c03365a8 <chromeos_update_engine::(anonymous namespace)::mock_system_state+8>)
    at /usr/local/include/gmock/gmock-nice-strict.h:145
#10 chromeos_update_engine::MockSystemState::MockSystemState() (this=0x55a1c03365a0 <chromeos_update_engine::(anonymous namespace)::mock_system_state>)
    at src/update_engine/mock_system_state.cc:14
#11 0x000055a1c0014fbd in __static_initialization_and_destruction_0(int, int) (__priority=65535, __initialize_p=1)
    at src/update_engine/omaha_request_action_unittest.cc:838
#12 0x000055a1c0264b6d in __libc_csu_init ()
#13 0x00007fefdfff5040 in __libc_start_main (main=0x55a1c0005dc0 <main(int, char**)>, argc=1, argv=0x7ffd0f20c4d8, init=
    0x55a1c0264b20 <__libc_csu_init>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd0f20c4c8) at ../csu/libc-start.c:264
#14 0x000055a1c002124e in _start () at src/update_engine/mock_system_state.cc:25

I feel that some refactoring is required to get it working - I also tried to downgrade googletest to v1.8.1 and to pull from the latest commit on master: no more luck.

closed via https://github.com/kinvolk/update_engine/pull/12


Removing default role labels on master nodes

I am trying to remove the default labels from master nodes using kubectl. Custom labels can be set and removed like this without any problems, but those default labels seem like they can not be removed? On agent nodes I can set and remove labels without any issues.
I am using the following command:
kubectl label node k8s-node-1 "node-role.kubernetes.io/control-plane-"
kubectl label node k8s-node-1 "node-role.kubernetes.io/etcd-"

NAME         STATUS   ROLES                       AGE     VERSION
k8s-node-1   Ready    control-plane,etcd,master   21h     v1.21.4+k3s1
k8s-node-2   Ready    control-plane,etcd,master   21h     v1.21.4+k3s1
k8s-node-3   Ready    control-plane,etcd,master   21h     v1.21.4+k3s1
...

I would like to replace the default roles with just master.
System:

Ubuntu 20.04 VM on Proxmox
K3s version v1.21.4+k3s1
3 master cluster with embedded Etcd database.

The etcd, control-plane, and master role labels are managed by the supervisor and cannot be removed. Note that the master role is deprecated and will be removed completely in 1.23; you should start transitioning to control-plane as soon as possible.


No water level for Midea Cube dehumidifier.

Make: Midea
Model: Cube (20 Pint)
Model #: MAD20S1QWT
Some functions seem to work. For example, I can toggle it on and off and it shows the humidity level. However, the water level always reports 0 and I cannot set the target humidity level. As shown below, it reports as 50% -- although I have it set to 30%.

[11/8/2021, 1:02:29 PM] [midea-air] Updating accessory: Dehumidifier_5442 ([device id removed])
[11/8/2021, 1:02:29 PM] [midea-air] [updateValues] Header + Command: 90,90,1,0,89,0,32,0,1,0,0,0,39,36,17,9,13,10,18,20,218,73,0,0,0,16,0,0,0,0,0,0,0,0,0,0,0,0,0,0,170,32,161,0,0,0,0,0,3,3,65,33,0,255,3,0,0,2,0,0,0,0,0,0,0,0,0,0,0,0,11,36,164,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
[11/8/2021, 1:02:29 PM] [midea-air] [MideaPlatform.ts] sendCommand (Intent: [updateValues] (fetch params?) attempt 1/2) success!
[11/8/2021, 1:02:29 PM] [midea-air] [Dehumidifier] Current Humidity is 54
[11/8/2021, 1:02:29 PM] [midea-air] [Dehumidifier] Target humidity is set to 50
[11/8/2021, 1:02:29 PM] [midea-air] [Dehumidifier] Water level is at 0
[11/8/2021, 1:02:29 PM] [midea-air] Power State is set to: true
[11/8/2021, 1:02:29 PM] [midea-air] Operational Mode is set to: 0
[11/8/2021, 1:02:29 PM] [midea-air] Fan Speed is set to: 80
[11/8/2021, 1:02:29 PM] [midea-air] Swing Mode is set to: 2
[11/8/2021, 1:02:29 PM] [midea-air] Eco Mode is set to: false
[11/8/2021, 1:02:29 PM] [midea-air] Turbo Mode is set to: false
[11/8/2021, 1:02:29 PM] [midea-air] Full data is [
'11001000', '1',        '1', '1010000',
'1111111',  '1111111',  '0', '110010',
'0',        '0',        '0', '0',
'0',        '0',        '0', '1100100',
'110110',   '1010010',  '0', '0',
'0',        '0',        '0', '1011',
'1101011',  '10001010', '0', '0',
'0',        '0',        '0', '0',
'0',        '0',        '0', '0',
'0',        '0',        '0', '0',
'0'
]
[11/8/2021, 1:02:29 PM] [midea-air] [updateValues] Sent update command to: 161

I don't have Cube Dehumidifier to test it.

I have similar problems with Midea MDDF-20DEN7 WiFi .On/Off and humidity level works.No mode choice available which makes dehumidifier to work in fan only mode.Water level shows 0 but i think this is due to model not having a choice other than full tank.


separate model variables and obs variables types

Description
Use the new oops::ObsVariables for observations and oops::Variables for model variables.
Issue(s) addressed
Resolves #90
Impact
Resolves compile-time errors due to recent oops changes, alongside an out-of-bounds error in the Increments class.
Checklist

[x] I have updated the unit tests to cover the change
[x] I have linted my code using cpplint
[x] I have run the unit tests
[ ] I have run mo-bundle to check integration with the rest of JEDI and run the unit tests under all environments

I am seeing a lot of mo-bundle issues that don't seem to be related to my change, but might be related to me commenting out all lfric etc libraries:
http://fcm1/cylc-review/view/tsearle?&suite=mobb-oops2591&no_fuzzy_time=0&path=log/job/1/cmake_mo__cray_gnu_debug/01/job.err
changes look straight-forward to me otherwise and unit tests pass. If I get a green light I will push ahead as we really want to fix this up as quickly as possible to be able to run all the comparison tests etc.


Feature/send votes to l1

After the other prs are merged we will need to add a register script for this

Current dependencies on/for this PR:

main

PR #11

PR #15

PR #8

PR #9   👈

This comment was auto-generated by Graphite.


Resource Groups: Emit metrics that could be used by external schedulers

Determine what kind of metrics should be emitted so that external resource schedulers (e.g., HPA, KEDA, etc.) can add or remove compute resources based on demand. For example, external compactor scaling based on compaction queues. Or, scaling the number of ScanServers based on current ScanServer load and number of clients performing scans.

This also relates to idle stop #4076


[SPARK-9216][Streaming] Define KinesisBackedBlockRDDs

For more information see master JIRA: https://issues.apache.org/jira/browse/SPARK-9215
Design Doc: https://docs.google.com/document/d/1k0dl270EnK7uExrsCE7jYw7PYx0YC935uBcxn3p0f58/edit

Merged build triggered.

Merged build started.

@zsxwing @koeninger Can you guys take a look

Test build #37989 has started for   PR 7578 at commit 5da3995.

Test build #37989 has finished for   PR 7578 at commit 5da3995.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #37994 has started for   PR 7578 at commit 4a36096.

Test build #37994 has finished for   PR 7578 at commit 4a36096.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38016 has started for   PR 7578 at commit 575bdbc.

Test build #38016 has finished for   PR 7578 at commit 575bdbc.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #38022 has started for   PR 7578 at commit 8874b70.

Test build #38022 has finished for   PR 7578 at commit 8874b70.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(
    case class Data(topic: Vector, index: Int)
    case class Data(globalTopicTotals: Vector)
    case class VertexData(id: Long, topicWeights: Vector)
    case class EdgeData(srcId: Long, dstId: Long, tokenCounts: Double)

Merged build finished. Test PASSed.

Just some minor comments. Otherwise LGTM.

@zsxwing I made a few changes to add retry logic and timeouts, to make it more robust. Could you take a look, especially the retry logic.

Merged build triggered.

Merged build started.

Test build #38286 has started for   PR 7578 at commit c4f25d2.

Test build #38286 has finished for   PR 7578 at commit c4f25d2.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38290 has started for   PR 7578 at commit 5082a30.

Test build #38290 has finished for   PR 7578 at commit 5082a30.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test PASSed.

LGTM except the minor style issue.

Test build #1193 has started for   PR 7578 at commit 5082a30.

Merged build triggered.

Merged build started.

Test build #38291 has started for   PR 7578 at commit 543d208.

Test build #1193 has finished for   PR 7578 at commit 5082a30.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Test build #38291 has finished for   PR 7578 at commit 543d208.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class SequenceNumberRange(
case class SequenceNumberRanges(ranges: Array[SequenceNumberRange])
class KinesisBackedBlockRDDPartition(
class KinesisBackedBlockRDD(
class KinesisSequenceRangeIterator(

Merged build finished. Test PASSed.

Thanks @zsxwing for reviewing I am going to merge it in master.


SERVER_ERROR object too large for cache

I notice these SERVER_ERROR object too large for cache messages in my logs. Surrounding messages provided for context:
ts=2019-02-08T23:28:02.691831547Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:07.910472747Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:13.118912514Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:20.898754563Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:23.726442295Z caller=images.go:128 component=cluster resource=sftp:deployment/sftp err="getting secret \"myregistrykey\" from namespace \"sftp\": secrets \"myregistrykey\" not found"
ts=2019-02-08T23:28:26.108687709Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:29.117995084Z caller=images.go:17 component=sync-loop msg="polling images"
ts=2019-02-08T23:28:29.153912177Z caller=memcached.go:133 component=memcached err="storing in memcache: memcache: unexpected response line from \"set\": \"SERVER_ERROR object too large for cache\\r\\n\""
ts=2019-02-08T23:28:29.153977173Z caller=warming.go:185 component=warmer canonical_name=index.docker.io/larktech/goldfinch auth="{map[index.docker.io:<registry creds for<EMAIL_ADDRESS>from yoni:secret/myregistrykey>]}" err="writing result to cache: memcache: unexpected response line from \"set\": \"SERVER_ERROR object too large for cache\\r\\n\""
ts=2019-02-08T23:28:30.29245483Z caller=images.go:17 component=sync-loop msg="polling images"
ts=2019-02-08T23:28:32.542390094Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54
ts=2019-02-08T23:28:32.542452133Z caller=images.go:17 component=sync-loop msg="polling images"
ts=2019-02-08T23:28:36.525463416Z caller=loop.go:100 component=sync-loop event=refreshed url=git@dev-gogs-ssh.lark.com:larktech/dev8a-cluster branch=master HEAD=af4b2c59d33aeff278ae855d1004688156101e54

Any idea what this might be about?

Looks like the image metadata goes over the default limit. You could set memcached. maxItemSize=5m and see if it's enough.  https://github.com/weaveworks/flux/pull/1453

@montyz did you get a chance to raise the limit and see if it fixes it?

Tentatively setting this as bug since the default maxItemSize may be too small and require reconsideration.
@montyz assuming that the item size was the culprit, it would be good if you could give us some further information about the image metadata, to understand whether we should change the default value

I was using the straight k8s deployment so I added this -I arg to the memcached args:
    spec:
      containers:
      - name: memcached
        image: memcached:1.4.25
        imagePullPolicy: IfNotPresent
        args:
        - -m 64    # Maximum memory to use, in megabytes. 64MB is default.
        - -p 11211    # Default port, but being explicit is nice.
        - -I 5m
        # - -vv    # Uncomment to get logs of each request and response.
        ports:
        - name: clients
          containerPort: 11211

It took about 10 min but it was able to fetch all the metadata. We have one docker repo with 3241 tags, maybe that was what didn't fit? I don't know what else you might want to know about the image metadata.

the default maxItemSize may be too small and require reconsideration.

It's reasonable and expected to have an image repo with thousands of tags; and each metadata record is on the order of 1k. A default setting of 5m would be OK I reckon.


Implement basic contract deployment

Allow storage and retrieval of string descriptions on the contract.
pushPost: (w/o photo) push post description to contract
buyPost: (w/o photo) retrieve post description from contract

Initial contract deployment (using string description only) was success without extensive testing

70400a21eae9e9d962f044da87a1c43bf4da2feb


[Subtask]: Support Spark 3.4.X

Search before asking

[X] I have searched in the issues and found no similar issues.

Description
Iceberg supports Spark 3.4 from version 1.3.0.
Arctic should also support Spark 3.4 version to facilitate Mixed Format users of Spark 3.4.
Parent issue
#1554
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I am interested in it, but my confusion is that there is a lot of duplicate code here, why not add a public module

I am interested in it, but my confusion is that there is a lot of duplicate code here, why not add a public module

@zyuan2001 yes, and there is an issue tracking this https://github.com/NetEase/arctic/issues/1449, are you interested to submit a PR to solve this?


Error: connect ECONNREFUSED <IP_ADDRESS>:8000

npm run multitaskum:developum

><EMAIL_ADDRESS>multitaskum:developum
> docker compose up -d && vite dev --host

[+] Running 1/0
 ✔ Container database  Started                                                                                0.0s

  VITE v4.5.1  ready in 902 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: http://<IP_ADDRESS>:5173/
  ➜  Network: http://<IP_ADDRESS>:5173/
  ➜  Network: http://<IP_ADDRESS>:5173/
  ➜  press h to show help

I go to http://localhost:5173/ in the browser and see the following:
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: connect ECONNREFUSED <IP_ADDRESS>:8000
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 8000
}

Node.js v18.18.0

BTW, I am on Ubuntu 22.04.3 LTS

Is the database running as well?

How do I verify that?

This error usually means that database instance is not running or is not reachable on <IP_ADDRESS>:8000
You can check what is running on the port 8000 with this cmd: sudo lsof -i:8000
If there is a conflict then you can
kill process by cmd: kill -9
or change ports docker-compose and .env to something else
This error can also happens when network is misconfigurated, or ports are blocked by firewall etc.
Firstly check if there is no conflicts on port 8000 and let me know

the lsof command shows nothing. I tried changing both .env and docker-compose.yml to 8001 but got the same error. Maybe i need to remove my docker image or stop it from running (if it's running already, I am not sure)?
Also, in docker-compose I tried changing the number twice (it shows up twice in one line) and i also tried to only change the first number, but in both cases I got the same error.
 - 8000:8000

That sounds like some kind of problem with Docker. I will suggest to remove SurrealDB container, turn off all others containers (just for testing), and restart docker engine. After restart run: npm run multitaskum:developum again.
Let me know if that helps, if not then let me know if there was running container for surrealdb, if not let me know if SurrealDB container exists at all.

ok. I'll will look up the docker documentation (unless you know what commands I should run) and report back!

I found the docker commands:
systemclt start docker
docker ps
docker stop d728f5ebb68b
docker rm d728f5ebb68b
npm run multitaskum:developum

And it looks like the container is crashing every few seconds:
docker ps
CONTAINER ID   IMAGE                        COMMAND                  CREATED          STATUS                        PORTS     NAMES
d728f5ebb68b   surrealdb/surrealdb:latest   "/surreal start --al…"   17 seconds ago   Restarting (1) 1 second ago             database

I apologize for the late reply, but I don't have constant access to the Internet as I am abroad right now.
I can't reproduce this. I clone repository, run bun install and bun run multitaskum:developum and everything just works.
Please try to change in .env file DB_LOG_LEVEL=INFO to =FULL and check the inside logs of the container by cmd: docker logs <container id>, maybe there will be any helpful information that can help debug this.
With current info I can only guess that there is a problem with read/write access on db folder. So you can check this as well.

I am closing this matter due to insufficient information for replication, and it has also been inactive for over three weeks. Please feel free to reopen it if necessary.


Search fails for tracks without track number

Tracks which don't have a track number in their metadata produce errors with search script when attempting to sort by "trackNumber". The script should either check for the existence of track numbers before sorting, or include a command line switch to sort by something else.

You didn't post the errors you get, song dict of nonworking examples, nor I can't replicate this behavior in the interpreter, at least. Will test with the script itself when I get around to it, but I don't see how it would be different than just doing mc.get_all_songs().sort(key=lambda song: (song.get('artist'), song.get('album'), song.get('trackNumber'))) in the interpreter if the errors you're getting are actually related to the sorting.

Closing this due to lack of response or reproduction.


[$250] IOU –Expense chat doesn't scroll to bottom when send message and create second money request

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.63-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Issue found when executing PR https://github.com/Expensify/App/pull/39685
Action Performed:

Go to https://staging.new.expensify.com/
Log in
Create a new WS
Navigate to WS chat and create a request
Open IOU details
Send a message
Create a request

Expected Result:
Expense chat scroll to bottom when send a message and create second money request
Actual Result:
Expense chat doesn't scroll to bottom when send a message and create second money request
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/49293dbd-48de-4313-9051-0a49d2798fb8
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01cba2ec575ed8acd2
Upwork Job ID:<PHONE_NUMBER>081064448
Last Price Increase: 2024-04-29

Proposal
Please re-state the problem that we are trying to solve in this issue.
IOU –Expense chat doesn't scroll to bottom when send message or money request
What is the root cause of that problem?
Currently we are using shouldEnableAutoScrollToTopThreshold prop to determinate if we should scroll down when new message arrive, but this pretends to use autoscrollTopTopThreshold to do this, at first it seems to be good, but we got the issue when we set the FlatList without this prop, the Flatlist component do not detects the change of this if we add this after a render.
What changes do you think we should make in order to solve the problem?
If we set the autoscrollToTopThreshold to 0 when the shouldEnableAutoScrollToTopThreshold is false, we can control the value of autoscrollToTopThreshold for the FlatList. To do this we can add the next else statement inside the BaseInvertedFlatList component like:
const maintainVisibleContentPosition = useMemo(() => {
        const config: ScrollViewProps['maintainVisibleContentPosition'] = {
            // This needs to be 1 to avoid using loading views as anchors.
            minIndexForVisible: 1,
        };

        if (shouldEnableAutoScrollToTopThreshold) {
            config.autoscrollToTopThreshold = AUTOSCROLL_TO_TOP_THRESHOLD;
        } **else {
            config.autoscrollToTopThreshold = 0;
        }**

        return config;
    }, [shouldEnableAutoScrollToTopThreshold]);

Tests:
Before changes:
https://github.com/Expensify/App/assets/5216036/c7dda455-7422-4d9c-bd4e-4fc7db840913
After changes:
https://github.com/Expensify/App/assets/5216036/99b20b71-6507-4ee7-afe4-750bc1254eca

@hoangzinh thoughts on the proposals so far?

but we got the issue when we set the FlatList without this prop, the Flatlist component do not detects the change of this if we add this after a render.

@samilabud I don't think your RC is correct. Can you check why user just sent a new message but shouldEnableAutoScrollToTopThreshold is false, lead to "we set the FlatList without this prop" as you said above?

Hi, when the reportActionsView load, set a variable to determinate if there are a new message, when the user sent a new message that value is false and later we send that false into the next statement:
const shouldEnableAutoScroll = hasNewestReportAction && (!reportActionID || !isNavigatingToLinkedMessage);
Because of this false value, the FlatList going to take that behavior not matter what we are sending as a message.

Actually, your solution doesn't work in offline mode
Screen.Recording.2024-05-03.at.18.19.58.mp4

when the user sent a new message that value is false

@samilabud If we put a log there, we can see that value would be true after seconds. Can you find a reason for it?

Hey @hoangzinh, as far I can see to determinate if we has a new message we are comparing the last time we synchronized with the server (lastVisibleActionCreated) vs the current time of the last message we sent (reportActions[0]?.created). This cause the next behavior:
If we are online

When the chat render the reportActions[0]?.created match with lastVisibleActionCreated so we got true (for shouldEnableAutoScroll).
When we send a message the lastVisibleActionCreated remains unchanged and reportActions[0]?.created change to the current time, this makes  that shouldEnableAutoScroll switch to false**. (it seems the logic behind is to wait for the server response to do the automatic scroll down)**
After we synchronized with the server (when we got the response that the message was sent) we got a true ( in shouldEnableAutoScroll) because reportActions[0]?.created match with lastVisibleActionCreated match again.

If we are offline

Same as first step when online
Same as second step when online
We are not synchronizing with the server (we don't make any request) the shouldEnableAutoScroll remains false because reportActions[0]?.created is changing to the current time but  lastVisibleActionCreated keeps as the same until we get online again.

As I said in before it seems the logic behind is to wait for the server response to do the automatic scroll down, so maybe this is the expected behavior, except for the error which was reported here.
Please let me know if I should verify deeper or if you have any other suggestion.

When we send a message the lastVisibleActionCreated remains unchanged and reportActions[0]?.created change to the current time

@samilabud I don't think it's correct. Can you check again? I think the auto scroll behavior in chat should work for both online and offline mode.

Yes it is a bit weird and I have checked it again, below a video with the output of the debug log:
https://github.com/Expensify/App/assets/5216036/e88a7d3f-95bc-40e4-9659-b63dd6a84a8b
As you can see the hasNewestReportAction variable when is offline remains false, which means shouldEnableAutoScroll going to be false:
const shouldEnableAutoScroll = hasNewestReportAction && (!reportActionID || !isNavigatingToLinkedMessage);

BTW I have also tested with my mobile phone, the behavior is the same when is offline.

Hi @hoangzinh, thanks for the suggestion, I realized the difference between lastVisibleActionCreated and reportActions[0]?.created is 2.262 seconds before we are synchronized with the server, that is the why we got the false, below the video requested:
https://github.com/Expensify/App/assets/5216036/8998e4eb-aefa-45a7-bcb2-5c9a56032002
So instead of lastVisibleActionCreated remained unchanged is that it is delayed (when offline and also when we send a message online).
When online the lastVisibleActionCreated is 0.263 seconds apart and makes hasNewestReportAction false:

After synchronized (hasNewestReportAction is true):

Anything else please let me know 🙏🏼

As far I can see this difference comes from the optimistic value of lastVisibleActionCreated:

@hoangzinh based of this last comment, I have updated my proposal , please see the alternative part.

@samilabud Because both reportAction and report are all optimistic updated, is it possible to make reportActions[0]?.created === report.lastVisibleActionCreated with no delay?

I'm checking, but today the expensify services are down, maybe tomorrow I can give you an answer.

Hi @samilabud just wanna double check because when I saw your recording above, after you create a money request, it doesn't auto scroll to bottom, does it?

Oh it seems like I did the scroll down with the mouse 😄😳, but yes it was automatically.

Proposal
Updated
(Alternative proposal modified)

we're getting close to the solution

Nice and good news!, thanks for the feedbacks, thanks to them I have learned a lot about how Onyx and Expensify works.

What do you mean with "different render stage of the ReportAction"?

I mean the different calls in different times of each function, I have changed my words in the proposal, please check it out.

2. Can you update your "What is the root cause of that problem?

Root cause updated, thank you!
Proposal
Updated
(I removed the alternative option and left only the one we are working with. )

Hi everyone, I have created the PR, but still waiting for the offer.

Issue not reproducible during KI retests. (First week)

FYI @samilabud the C+ (in this case @hoangzinh) provides the recommendation on who to hire, but you aren't actually hired until an Expensify internal engineer (in this case me) agrees.

FYI @samilabud the C+ (in this case @hoangzinh) provides the recommendation on who to hire, but you aren't actually hired until an Expensify internal engineer (in this case me) agrees.

oh ok, good to know, thanks!

What's the status of the PR @samilabud @hoangzinh?

What's the status of the PR @samilabud @hoangzinh?

Ready to review since: https://github.com/Expensify/App/issues/40594#issuecomment-2106497524

Oh no my bad, was reviewed and waiting for: https://github.com/Expensify/App/issues/40594#issuecomment-2106497524

about the status of the PR.
The PR is ready, and the review was done but my reviewer was questioning about if we can merge this in https://github.com/Expensify/App/pull/42030#issuecomment-2113336521.

I don't pretty sure about the next steps, sorry.

@allroundexperts where do you think we go from here?

Ok @hoangzinh so is any payment needed here? Or was this ultimately solved by a different PR?

Ok seems fair. I've paid @samilabud and sent you an offer @hoangzinh: https://www.upwork.com/nx/wm/offer/102916271
Ping me here when you accept.

Ok all paid. Thanks y'all.


Irrelevant parameters should be added to blacklist in the configuration

The parameters "ajaxcatalog=true" and "skip_ff" should be added to the hard coded list of ignored server parameters: https://github.com/Flagbit/Magento-FACTFinder/blob/master/src/lib/FACTFinderCustom/Configuration.php

Probably it would be the best, if the parameter blacklist is configurable via the UI.


Adds support for optionally showing disclosure arrow buttons

The theme currently doesn't support recursively opening or -closing folders by cmd+shift-clicking the disclosure arrows next to the folders (because they're hidden in the theme). This PR adds an optional setting to show the arrows. It is not to be confused with the predawn_sidebar_arrows option, which essentially just replaces the folder icon with an arrow icon as cmd+shift-clicking these doesn't do anything.
Changes made:

Made new disclosure arrow icons with same stroke width as the file type icons
Remade the close-file icon to match the thickness of the above icon
Documented the new option in README.md
Moved folder icons (@2x versions only) up 1 px to better align with the file name. Didn't need to change the 1x versions as they were already correctly placed

Screenshots:
With Show open files disabled

With Show open files enabled

Well done! Thanks for the help. I'll try to pull these down today and let you know if I have any questions/feedback before merging.

You're welcome, thought i'd share it. Let me know if anything is missing!

@jamiewilson: Any comments thus far?

Unfortunately, no. Haven't had a chance to look at it yet but I should be able to this week. I'll keep you posted.

Ping :)

Hey man, thanks for the reminder! I'm really sorry, but I've got some other things taking priority over this right now. But it shouldn't be too much longer!

Hey man, I made a small change to this PR: hiding disclosure icons when predawn_sidebar_narrow: true is set.
https://github.com/jamiewilson/predawn/commit/dbf6a9fb2e5fa9ba10dbb4f76b93933d908e36c1
If this looks good to you, I'll go ahead and merge to master. Thanks for your patience with this. Sorry it took so long.

Hey @wolthers. Wanted to make sure you saw this.


Update go-jsonnet to v0.18.0

This should add some new functions
See https://github.com/google/jsonnet/releases/tag/v0.18.0

I think we need to discuss on whether we keep parseYaml or use upstream, no?

I think we need to discuss on whether we keep parseYaml or use upstream, no?

Hmm, yeah. Good point

It would be nice if you merge and cut release soon. Some std.functions are long expected. Thank you!

It would be nice if you merge and cut release soon. Some std.functions are long expected. Thank you!

👍 . I was aiming for a release next week

We'll be leaving std.native("parseYaml") for now to not break compatibility


swiper-wrapper的flex属性没有了？

中文用户请注意：

issue 只接受带重现的 bug 报告，请不要用来提业务问题、基础知识问题！不符合要求的 issue 会被直接关闭。
请尽量用英文描述你的 issue，这样能够让尽可能多的人帮到你。
请务必在已关闭的 issues 中寻找你的问题，它极有可能已经被解决。

Got a question?

The issue list of this repo is exclusively for bug reports and feature requests. For simple questions, please use the following resources:

Read the docs: https://vuejs.org/guide/

Look for/ask questions on stack overflow: https://stackoverflow.com/questions/ask?tags=vue.js

Reporting a bug?

Try to search for your issue, it may have already been answered or even fixed in the development branch.

It is required that you clearly describe the steps necessary to reproduce the issue you are running into. Issues with no clear repro steps will not be triaged. If an issue labeled "need repro" receives no further input from the issue author for more than 5 days, it will be closed.

It is recommended that you make a JSFiddle/JSBin/Codepen to demonstrate your issue. You could start with this template that already includes the latest version of Vue.

For potential SSR (Server Side Rendering) issue or bugs that involves build setups, you can create a reproduction repository with steps in the README.

If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.

Have a feature request?

Remove the template from below and provide thoughtful commentary and code samples on what this feature means for your product. What will it allow you to do that you can't do today? How will it make current work-arounds straightforward? What potential bugs and edge cases does it help to avoid? etc. Please keep it product-centric.

BUG REPORT TEMPLATE
Vue.js version and component version
Reproduction Link

A minimal JSBin, JSFiddle, Codepen, or a GitHub repository that can reproduce the bug.
You could start with this template: https://jsfiddle.net/39epgLj0/

Steps to reproduce
What is Expected?
What is actually happening?

是不是插件刚刚更新了？ 我重新 npm install 过。

在github的首页说明没有更改使用方法啊。

使用的版本都是 "vue-awesome-swiper": "^2.5.4",

回滚到 一个月以前的版本也是坏的。   = =。

能不能按照模板规范提一次问题？

问题以解决：  插件目前在npm下载的默认版本是 2.6.2
我以前用的版本是 2.5.4
所以导致结果： swiper 上没有 flex的CSS属性

重新下载 2.5.4版本可以解决

请仔细再仔细阅读 README.md


MTB: Add test for Block use of host networking and ports

https://github.com/kubernetes-sigs/multi-tenancy/blob/master/benchmarks/e2e/tests/block_host_net_ports/README.md

/assign @phoenixking25

closing as the project is being restructured


[CARBONDATA-3423] Validate dictionary for binary data type

it will throw exception if dictionary_include has binary column, it will not throw exception if DICTIONARY_EXCLUDE has binary column
optimize
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
No
[x] Any backward compatibility impacted?
No
[x] Document update required?
yes
[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.
yes
[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
No

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3478/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3681/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11745/

@KanakaKumar @brijoobopanna
Please review it.

LGTM

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3714/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/11780/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/3509/

@KanakaKumar  CI pass, please check.


update TileOrientedBoundingBox debug volume size to match OrientedBoudingBox

Fixes #4581

@austinEng how did you test this?  Did you verify that the 2x2x2 suggestion in #4581 is correct?

The constructor for OrientedBoundingBox takes the halfAxes of the bounding box so I think it's a factor of two off. The documentation notes that Matrix3 argument denotes the transformation matrix for a 2x2x2 bounding box. TileOrientedBoundingBox also takes in the halfAxes so I imagine this would be the same.
BoxOutlineGeometry takes the min and max corners as options and not a scale, so I think corners of (-1,-1,-1) and (1,1,1) would make sense.

Ah, yes!


New build Windows 10 Version 19044.1586 Not Supported

Hi
I updated today to 19044.1586 version and it's not working.
I attach termsrv.dll file
Thanks
termsrv.zip
!

Duplicate of https://github.com/stascorp/rdpwrap/issues/1725


kvstore/allocator: Optimize idpool refresh locking

Avoid holding onto the idPool lock while creating a new idCache
Fixes #5354

This change is

test-me-please

test-me-please

test-me-please


Not working at all since version 1805 of Azure Stack....

Please provide us with the following information:

This issue is for a: (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Attempt to use on Azure Stack 1805 release. As written there are also several dependencies that are omitted from Azure Stack powershell (operations related) that can be installed manually but the main issue is post-1805, multiple issues with upload and retrieval of information on both the Azure Stack and OpsInsight side.

Any log messages given by the failure

Get-AzureRmOperationalInsightsWorkspace : The 'Get-AzureRmOperationalInsightsWorkspace' command
was found in the module 'AzureRM.OperationalInsights', but the module could not be loaded. For
more information, run 'Import-Module AzureRM.OperationalInsights'.
At C:\AZSAdminOMSInt\OpsDataToOMS.ps1:87 char:7

$ws = Get-AzureRmOperationalInsightsWorkspace -ResourceGroupName $OMS ...

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ObjectNotFound: (Get-AzureRmOperationalInsightsWorkspace:String) []
, CommandNotFoundException
FullyQualifiedErrorId : CouldNotAutoloadMatchingModule

No Alerts From  + Rack30
[
{
"ScaleUnitNodeName":  "SAC30-Node01",
"ScaleUnitNodeOperationalStatus":  null,
"ScaleUnitNodeLocation":  "rack30",
"Type":  "ScaleUnitNode",
"TimeStamp":  "/Date(1533829587185)/",
"ScaleUnitNodeandCloudName":  "SAC30-Node01_Rack30",
"CloudName":  "Rack30"
},
{
"ScaleUnitNodeName":  "SAC30-Node02",
"ScaleUnitNodeOperationalStatus":  null,
"ScaleUnitNodeLocation":  "rack30",
"Type":  "ScaleUnitNode",
"TimeStamp":  "/Date(1533829587185)/",
"ScaleUnitNodeandCloudName":  "SAC30-Node02_Rack30",
"CloudName":  "Rack30"
},
{
"ScaleUnitNodeName":  "SAC30-Node03",
"ScaleUnitNodeOperationalStatus":  null,
"ScaleUnitNodeLocation":  "rack30",
"Type":  "ScaleUnitNode",
"TimeStamp":  "/Date(1533829587185)/",
"ScaleUnitNodeandCloudName":  "SAC30-Node03_Rack30",
"CloudName":  "Rack30"
},
{
"ScaleUnitNodeName":  "SAC30-Node04",
"ScaleUnitNodeOperationalStatus":  null,
"ScaleUnitNodeLocation":  "rack30",
"Type":  "ScaleUnitNode",
"TimeStamp":  "/Date(1533829587185)/",
"ScaleUnitNodeandCloudName":  "SAC30-Node04_Rack30",
"CloudName":  "Rack30"
},
{
"Version":  null,
"IPPoolAvail":  null,
"MemoryUsed":  null,
"DiskAvail":  null,
"State":  null,
"Location":  "Rack30",
"Type":  "Capacity",
"MemoryAvail":  null,
"CloudName":  "Rack30",
"DiskUsed":  null,
"IPPoolUsed":  null,
"TimeStamp":  "/Date(1533829587169)/",
"DeploymentGuid":  "706a85ca-abf3-4866-8667-d967bcb68797"
}
]
PS>TerminatingError(Send-OMSAPIIngestionFile): "Cannot bind argument to parameter 'customerId' because it is null."
Send-OMSAPIIngestionFile : Cannot bind argument to parameter 'customerId' because it is null.
At C:\AZSAdminOMSInt\OpsDataToOMS.ps1:233 char:38

Send-OMSAPIIngestionFile -customerId $ws.CustomerId -sharedKey $wskey ...

                                 ~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Send-OMSAPIIngestionFile], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Send-OMSAPIIngestionFile
Send-OMSAPIIngestionFile : Cannot bind argument to parameter 'customerId' because it is null.
At C:\AZSAdminOMSInt\OpsDataToOMS.ps1:233 char:38

Send-OMSAPIIngestionFile -customerId $ws.CustomerId -sharedKey $wskey ...

                                 ~~~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Send-OMSAPIIngestionFile], ParameterBindingValida
tionException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Send-OMSAPIIngestion
File

Expected/desired behavior

This was working great up until 1804.

OS and Version?

Azure Stack version
1.1805.1.47

Versions

1.1805.1.47
Mention any other details that might be useful

Hi hakksaww1 - the files have been updated to reflect a change in a previously broken commandlet. Please download the new InvokeMasterScript.ps1 and MasterScript.ps1 files and try again. Be sure to delete any previous folder named \AZSAdminOMSInt from the C:\ folder. Also remove previously created scheduled tasks from "Task Scheduler"


cherry-pick replace the LOG(FATAL) to throw Exception in query execute layer (#38144)

cherry-pick from master https://github.com/apache/doris/pull/38144

run buildall


App Lost Google Verification Status? aka Can't Add New Google Accounts

It looks like there may be an issue with KeeAnywhere's App Verification status.
The error screen that @ElizaZadura and I encountered in #393 is almost identical to this one that Google says you get if an unverified app exceeds 100 users.

Plus, I had no problem re-authorizing an account I had already added, nor even removing and re-adding the account. But as soon as I deleted KeeAnywhere from my Google Security dashboard I suddenly began having the same problem.
Googling the error message led to this article, which supports the idea that the App is missing a verification.
This Google support page also supports the idea that KeeAnywhere would require verification:

Google verifies projects … if … Your project's OAuth clients request authorization of any sensitive or restricted scopes. …

More info here also:
https://developers.google.com/terms/api-services-user-data-policy#additional_requirements_for_specific_api_scopes
Unfortunately, we use drive  (as discussed in #398 ), which is one of those restricted scope.
https://github.com/Kyrodan/KeeAnywhere/blob/ebeb344177353ad663e1d0270920f7ca057b737c/KeeAnywhere/StorageProviders/GoogleDrive/GoogleDriveHelper.cs#L39
The official list of restricted scopes was not easy to find. I never did find the sensitive list.
I don't remember seeing this screen in the past, which makes me think this app was verified in the past and has somehow lost that status?
Compiling my own copy, with my own test client_id and client_secret (and no other changes) made it so I did not get this issue.
It's also possible that the change suggested in #398, switching the scope to drive.files might help. Even though - as I said in the other issue - I prefer using drive, I admit that drive.files has a chance of working, because it is not in the restricted scopes list, and Google seems to take those extremely seriously.

Hey Mister Keeanywhere, any news about this MAJOR PROBLEM ? this prevents to use your plugin, please do something asap otherwise I can tell you that your plugin is dead !!! wake up, now

Duplicate to #393.


(Draft until #90 is merged) #93 add form generator

This PR adds a generic proc that generates a Box with a List of Widgets for every field in a given object.
Which mostly means for every field in a given <Widget>State.
This autoform was only used in the Scale.nim example for now, other examples shall be updated in a separate PR to keep these small and easily reviewable.
The reasoning for why I chose a generic proc rather than writing a generic viewable I laid out in #93
This PR actually only adds an autoform.nim file, but as this branch is one that branched off the one for  #90 it contains the same changes as that one.
This PR depends on #90 as #90 provides the scale.nim example and that was what I used as reference to implement this.
As per the usual, it's all up for change regardless. Even if I already have #95, I should be able to relatively simply adjust that to whatever we decide here as I'm semi-sure the concept of "take in a state, iterate over it and spit out a widget based on that" will remain.

This needs to be rebased now that https://github.com/can-lehmann/owlkettle/pull/90 is merged.

I'm on it.
Or rather, I'm currently revamping said form generator so that it generates a sidebar based on the changes you made to the Scale Widget.
And as part of that I'm updating accordingly

Okay, this is a first draft that basically recreates the sidebar as before.
Well almost.
I don't really control the order of this one so the marks field is not quite in the middle.
Also I added a DropDown field so you can decide the ScalePosition of a given mark.
My next attempt will be to see if I can't move from a custom toFormField method to something that fully generates a proc like that just from a given type.

@can-lehmann I've got a... let's say first draft working for auto-generating ExpanderRow-Widgets for a given object type T.
I'm honestly not too sure what to make of this.
I can either pretty this up, or we just leave it and instead implement custom toFormField procs for every custom data type we have in a seq.
Might be less of a headache overall because the generic manner of this is starting to get somewhat abstract, but on the other hand having to write your own toFormField for custom data types every time might be repeated effort.
Then again, I don't think this should happen too often.
Thoughts?

I've decided to just move over to the approach where you defined a custom toFormField for every custom type you have.
Generating forms for every normal type in an action Row is way too annoying.

https://github.com/can-lehmann/owlkettle/pull/91#issuecomment-1747218057 also applies here, so I would personally prefer to merge this after the JSON discussion and then move any discussions & changes to https://github.com/can-lehmann/owlkettle/pull/95.

Ohhh merge this into #95 and close this PR? Works for me

Basically, if you tell me now this looks okay I'll merge this branch into #95 and close this PR

Ohhh merge this into https://github.com/can-lehmann/owlkettle/pull/95 and close this PR? Works for me.

Sounds good.


Added Basic Explaination for UIA Providers

Signed-off-by: HIMANSHU BALASAMANTA<EMAIL_ADDRESS>

Hi @Karl-Bridge-Microsoft !
I am a member of UIA team in Accessibility. Will be contributing towards the UIA documentation for next couple of weeks.


Sentry Transactions are missing

We have gained the impression that Sentry Transactions are missing. Especially, the transaction of the WebSocket connection is missing often.

TLDR: See codeocean-terraform!138
When excluding the Sentry Relay (by re-configuring the Sentry Endpoint of Poseidon and CodeOcean to ingest.sentry.io) all transaction are received [1] [2] [3] [4] [5] [6] [7] [8] [9] [10].
When using the Sentry Relay all transaction are received except for the transaction of the WebSocket connection. This transaction is received only in about 10% of the executions [11] [12] [13] [14] [15] [16] [17] [18] [19] [20].
Therefore, we can limit the error to the Sentry Relay. When having a look in the Sentry Relay logs, we have no warnings or errors, but for each transaction the Sentry relay logs the following lines:
2023-08-23T11:02:01.234479Z DEBUG request{method=POST uri=/api/5667283/envelope/ version=HTTP/1.0}: tower_http::trace::on_request: started processing request
2023-08-23T11:02:01.236683Z TRACE request{method=POST uri=/api/5667283/envelope/ version=HTTP/1.0}: relay_server::endpoints::common: queueing envelope
2023-08-23T11:02:01.236752Z DEBUG request{method=POST uri=/api/5667283/envelope/ version=HTTP/1.0}: tower_http::trace::on_response: finished processing request latency=2 ms status=200
2023-08-23T11:02:01.238480Z TRACE relay_server::actors::processor: processing json transaction
2023-08-23T11:02:01.244494Z TRACE relay_server::actors::envelopes: sending envelope to sentry endpoint

The only difference is that for the one successful execution, the log contains 6 transactions, and for the other executions just 5 (AllTransactions - WebSocketMissing). However, the Nginx Log shows that we receive 6 requests for either. The difference: For the cases where the WebSocket Transaction is missing one request has the StatusCode 413 Payload Too Large.
Therefore, it's not the fault of the Sentry Relay this time, but our configuration of the Nginx client_max_body_size (or that we send too much data in our Poseidon spans).

Awesome, thanks for identifying. I merged the branch but haven't deployed the change yet.

I have deployed the change for nginx, so that we can observe it now.

I checked the Sentry transactions and indeed was able to confirm that the newer transactions are complete. Hence, I am closing this issue.


Add stagent hash to attributes file

Added missing stagent (referenced in the README as of previous commit) hash to default attributes file.
Fixed 2x small typo's in README.
🤙 shaka 🤙

As promised...
@1dustindavis 🕶
@erikng 👀

Looks good. Thanks!


Merge stylus

Merges stylus components into a single execution context. This reduces the overhead of parsing and executing nib for each file.

looks good

all looks very good to me. sorry for coming to the party late.


Add ability to dynamically load an RDBC driver

Currently, it is necessary to statically link to all possible RDBC driver implementations that need to be used at runtime but one of the main benefits of ODBC/JDBC is that new drivers can be loaded at runtime, so we need a similar mechanism here.

Would this be a subclass, or would this be something like libdl that implements dynamic loading of shared libs?  I'm not sure if this is supported in Rust, but it's a possible solution.  I would think that if the drivers are lightweight enough, they can all be compiled into a single runtime?

It would need to by dynamic loading of shared libs so that a user can use any driver with a product without having to have a version of the product that is compiled against the driver they want to use.

Does anyone really load JDBC drivers at runtime in practice? I always thought that was an obscure thing to do.

Actually, this is very common in desktop products where the user can add new JDBC drivers through the user interface without the need to restart the application.

I see...  Like crystal reports


Colspan in header generate error

Hi,
Could you take a look at my simple example?
I've colspan in header which generate error: gridItemCell is undefined.
Example:
 var gridViewScroll = null;
        window.onload = function () {
            gridViewScroll = new GridViewScroll({
                elementID: "gvMain",
                widtdh: 400,
                height: 200,
                freezeColumn: true,
                freezeColumnCssClass: "GridViewScrollItemFreeze",
                freezeHeaderRowCount: 1,
                freezeColumnCount: 2
            });
            gridViewScroll.enhance();
        }

				Description

				Values

				desc value

				desc value 1

				 value 1

				desc value 2

				 value 2

is colspan properly supported?

Your cell merger is too complicated, I think there should be no way to use GridViewScroll.

Your cell merge is too complicated, I think there should be no way to use GridViewScroll.

I have the same problem as OP.
How is this too complicated? It looks simpler than the gif in the readme-file.
What would one need to do, in order to make it less complicated?


Support for findDuplicates

Salesforce now has matching rules to determine duplicate entries. These rules are established within the product and could change from time to time. There's a new call, findDuplicates(), that can be used but isn't supported by this toolkit.  Anyone know how to add support??

findDuplicates() was introduced in the SOAP API version 38. This library is at 27. The newest SOAP API version is up to 44.


Introduce type parameters where applicable for xDS classes.

Motivation:
Following the discussion in this comment, incorporating type parameters in xDS classes offers advantages such as improved type safety and enhanced readability. Modifications:

Introduce type parameters where applicable.
Split AbstractResourceNode into AbstractResourceNode and AbstractResourceNodeWithPrimer to accommodate the absence of a primer in the listener.
Rename AbstractResourceHolder to ResourceHolderWithPrimer for consistency due to the absence of a primer in the listener.
Conduct clean-up in some APIs. Result:
Enhanced type safety, improved readability, and a more structured representation in xDS classes.

Thanks for cleaning up!


bad ide

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:13:05.928Z)
OS Version: Darwin x64 16.4.0
Extensions: none

Steps to Reproduce:
1.code
let obj = {     name:'lpf',     age:25 }; console.dir(obj,{colors:true})
2.  can't output answer

Please follow this guide for submitting bugs or feature requests: https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions


Add the possibility to inject a Domain resolver

Introduction
Adding a way to inject the domain resolver into the Host and remove the hardcoded dependency on a specific domain resolver instantiation.
Proposal
The Host constructor and named constructors will be modified to enable the user to supply his/her own Rule object on instantiation so to not rely on the following default construct
Describe the new/upated/fixed feature
see issue

I've league/uri-hostname-parser downloaded as a dependency and my vendor directory is not writable, so the cache used by the default manager created in League\Uri\resolve_domain function throws an exception. How can I change the manager which is being used there?

We will add the following option to the methods

Host::createFromLabels(array $labels, int $encode_type, Rules $resolver = null);
Host::createFromIp(string $ip, Rules $resolver = null);
Host::__construct(string $host = null, Rules $resolver = null);
Host::withResolver(Rules $resolver): static

Backward Incompatible Changes
None. If no Resolver is specified the class will fallback to its current behavior generate a Rules from the Filesystem cache found in the vendor subdirectory if possible and will throws if it is not possible.
Targeted release version
1.7.0
PR Impact
The public API is changed by adding a new optional argument to methods.
Open issues
Would be great if the resolver followed some kind of PSR or common interface to allow other domain resolver like PHP Domain parser or TLDExtract to be used instead of league own implementation.

All right, I've looked at the new implementation and it seems I've bumped on an another issue:
The way Payum uses League's library is following:
$uri = Http::createFromString($requestUri);
$altUri = Http::createFromString($tokenUri);
$modifier = new Normalize();

$newUri = $modifier->process($uri);
$newAltUri = $modifier->process($altUri);

return $newUri->getPath() === $newAltUri->getPath();

There aren't any direct calls to Host or so, but actually Normalize modifier calls HostToAscii which creates the Host instance and I'm looking for the way to tackle it without rewriting half of the URI modifiers.

@pamil OK I get the issue .. again easy to stop but more difficult to solve ... but solvable ... it will mean a 1.7.1 fix thought .
The issue is that the Host on instantiation always perform public suffix resolution which is not always required for instance in your case. I could lazy load this part ... but this would mean rewrite a bit the class so to keep all current tests passing ... I'll look into it next week.
Could you create a separate issue for this as the current issue was already solved. This for me is a independent issue.
Thanks for the report 👍

@pamil all the patches are in place 👍 it was easier than I thought 💯
I've also updated the Uri manipulation package to allow injecting the resolver if needed. This should allow better usage of all the packages.
The only one I can not change is the Uri\resolve_domain function because it would mean BC break .. but again I'm not using it internally anywhere anymore so this also is safe.
So next week all the patches will be release.


signal-cli: 0.11.11 -> 0.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/AsamK/signal-cli/releases.
meta.description for signal-cli is: Command-line and dbus interface for communicating with the Signal messaging service
meta.homepage for signal-cli is: https://github.com/AsamK/signal-cli
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.12.0 with grep in /nix/store/9bw1vlzj4fc5mqrxx9bl1q9jdvmwpfyi-signal-cli-0.12.0
found 0.12.0 in filename of file in /nix/store/9bw1vlzj4fc5mqrxx9bl1q9jdvmwpfyi-signal-cli-0.12.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
scli
signal-cli

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9bw1vlzj4fc5mqrxx9bl1q9jdvmwpfyi-signal-cli-0.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A signal-cli https://github.com/r-ryantm/nixpkgs/archive/75b136a9504243803b47b4924d42906a3c7cc07d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9bw1vlzj4fc5mqrxx9bl1q9jdvmwpfyi-signal-cli-0.12.0
ls -la /nix/store/9bw1vlzj4fc5mqrxx9bl1q9jdvmwpfyi-signal-cli-0.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

scli
signal-cli

Maintainer pings
cc @ivan for testing.

Result of nixpkgs-review pr 250413 run on x86_64-linux 1

2 packages built:

scli
signal-cli


Updates jest to v24 and adapts code/configs

This updates jest to v24 and replaces ts-jest with the needed babel configs.

This might be due to the changes of the transpiling of the tests or the changes to the bundling... IMHO we can merge anyways. Are you ok with that?

yes


Recreating a cluster fails to replace start up script

Version v0.3.0
Repro steps:
Create a cluster with start up command.
Delete MIG
Recreate the cluster with a different start up command.
Script doesn't run and I see the following error in serial console logs:
CommandException: No URLs matched: gs://vakuz-t5-pipeline-test/repro/repro-net-deployment/initializestartup.sh
Mar  3 22:56:37 repro-net-vm-6xl6 google_metadata_script_runner[804]: startup-script: Fri Mar 03 22:56:37 +0000 2023 Error [851]: gsutil reported non-zero exit code fetching gs://vakuz-t5-pipeline-test/repro/repro-net-deployment/initializestartup.sh.  Retrying (9/10)
Mar  3 22:56:37 repro-net-vm-6xl6 google_metadata_script_runner[804]: startup-script: Fri Mar 03 22:56:37 +0000 2023 Info [851]: === start executing runner: repro/repro-net-deployment/initializestartup.sh ===
Mar  3 22:56:37 repro-net-vm-6xl6 google_metadata_script_runner[804]: startup-script: chmod: cannot access '//tmp/initializestartup.sh': No such file or directory
Mar  3 22:56:37 repro-net-vm-6xl6 google_metadata_script_runner[804]: startup-script: Fri Mar 03 22:56:37 +0000 2023 Info [851]: === repro/repro-net-deployment/initializestartup.sh finished with exit_code=1 ===

@abdallag I cannot reproduce this after pulling the latest changes from develop. Are you still seeing this problem?

This is due to terraform bug that HPC toolkit team is trying to fix. For now Please run destroy, change startup script and then run create again.

Fix is implemented by HPC toolkit team. Reopening the bug to implement the right fix.


Add happy path rasa story for selecting a project

Parent: #15

Closed, as this will be handled by the knowledge base server in the future: #69


Disable Summoners Rift Item Sets on ARAM

If anyone knows the keys to use to disable on ARAM, and/or only enable on ARAM, I'd be greatful.
Example item set JSON for those needing.
https://gist.github.com/dustinblackman/f8619cefdbf7dda3f704
EDIT: Required to be done before this feature can be released.
https://github.com/dustinblackman/Championify/issues/23

https://github.com/dustinblackman/Championify/commit/55492e53c13fdcdab2ad526befefd7ebade23fe7


pull request for e2e test at 12/06/2016 04:45:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


Testing for msmtools/GPCCA

@michalk8 , what's the state of the art here?

Haven't started on this yet, will do so soon. Also duplicate of #168, so closing this.


[MAUI/Xamarin.Forms/Both] supported  .NET7？

I cannot use it after installing with nuget.

The maui nuget target .net6 which can be used in .net7

Change the TargetFrameworks of the project.

I have a test today and found that it cannot be used on. NET 7.

which platform ?

Andriod

just tested it on net7.0-android, it works as expected

What do you set after installing the nuget package?
I can run your example.
There is another problem. I run the sample and then slide the contents of the tab with my finger. It will not jump.

sorry this is 2 differents issues, and the second one is a duplicate of an existing enhancement

Thank you for your reply and look forward to your new features.


[REQUEST] Settings for "Skip silence"

First of all, thank you for this great app.
Please make a list of settings for the "Skip silence" option to make the watching experience more suitable for low-volume videos.
The feature doesn't work perfectly with such videos of lectures and vlogs for example.
This project clarifies what I mean.

Can't these be adjusted by user? Or we might have presets.

Source:
https://exoplayer.dev/doc/reference/com/google/android/exoplayer2/audio/SilenceSkippingAudioProcessor.html

Already requested in #17


Remove the BTC address, leave the ERC20 only

Grant Application Checklist

[x] The application template has been copied, renamed ( project_name.md) and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] I have read and acknowledged the Terms and Conditions.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once the first milestone has been accepted.

Thanks. Can you please submit a new invoice that specifies one currency and in which USTD has been fixed to USDT?

I guess we no longer need to merge this, because of https://github.com/w3f/Open-Grants-Program/pull/447. Let me know if this is not the case and I will reopen it.

Ah, sorry. I was confused. Reopened and approved.


Platform labels/Tokens should include icons where possible

Currently, purple for ETH and pink for Kovan and green for ETC are introducing slight confusion to the user.
ETH, ETC have icons already.  I would recommend using these platform icons wherever possible.  That way there are two (2) identifiers; word label + icon.   Building the labels to be able to accommodate icons later when a Kovan/TestRPC label exists.  Also, Tokens would be great to distinguish visually by their icons (see https://coinmarketcap.com/)

Yes, this was in an earlier version of Spectrum, but became annoying to maintain during development (and there are tonnes of icons to get).
💸 x 3 for this, Added as a requirement in of #28.


test: use fs-fixture

:tada: This PR is included in version 4.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make A Better Readme

I added emoji's and a better introduction to make the README.md look nicer.

Thanks!


Server side rendering

Hello, is there a way to render the widget to an image on the server side, maybe with headless flutter?

I am not quite sure what your issue is yet, but we will figure it out.
Just so I know if I understand you correctly, would the following process display your request/problem?

Capturing on the device side
Writing frames on the device side to a local directory
Uploading those image frames files to the server
Server processing of files to video/export format with FFmpeg?

Or, are you requesting support for the web, if so, please refer to this issue, so we can find a solution together. I am available for collaboration if you are invested in extending the Renderplugin for the web.
Otherwise please enlighten me with more details, so I can help you :) PS. I am unfamiliar with headless flutter so far.

I am closing this as a duplicate of #6 . If you think I misunderstood you, please make sure to clarify your issue.


Configurable background image

It will be better if we can setting the background image via props of layout component, so no need to change css file if we want to change the background.

cool, i'm gonna help you

cool, i'm gonna help you

sure thanks

cool, i'm gonna help you

sure thanks

done


Add GitHub workflow checking minimal dependency versions

Problem solved by the enhancement
By accident Struson could depend on a future introduced by a version of a dependency newer than specified in Cargo.toml; users of Struson could then encounter build issues if Cargo's dependency resolution picks the older version (e.g. due to restrictions from other dependencies).
Enhancement description
Consider using Cargo's direct-minimal-versions or https://crates.io/crates/cargo-minimal-versions (or similar).
Alternatives / workarounds

Include this as task in Makefile.toml instead of just in a GitHub workflow
(maybe not worth it because it causes too much overhead for every build)
Do nothing and hope / assume the problem described above is not common enough

Maybe this is not that important, or needed at all, because Dependabot keeps the versions up to date and makes sure Cargo.toml and Cargo.lock are in sync.